I was curious about something. KDE has its own crash handling system.
How does this community track any metrics around code stability if
upstream gets reports? Kontact has segfaulted 20 times on me today.
Each time it says it cannot generate a bug report. Abrtd does not seem
to pick up anything. Shouldn't it? How does this community track
when a recent update suddenly starts making things crash? Kontact was
fine 3 weeks ago. I updated today (3 weeks of patches) and its crashing
all the time to the point its unusable. It won't generate a bug report,
abrtd seems not to notice either.
In KDE System's Settings there's the Color Corrections panel for setting
up monitor profile.
When selecting the display, a warning is displayed saying something like
"Gnome Color Management is needed to calibrate devices". Now, I have
Gnome Color Management installed:
> $ dnf list installed gnome-color-manager
> Pacchetti installati
> gnome-color-manager.x86_64 3.36.0-1.fc32 @fedora
but still the message is displayed. Is something else supposed to be
installed for make it work?
I opened a bug report to have this package upgraded to 1.7.0,
and it's been sitting about a month now. I reached out to the listed
maintainer and he said he hasn't touched the package in over a decade.
I can take ownership if no one else wants it.
choqok 1.7.0 allows for tweets longer than 140 characters and
includes mastodon support.
I am having some issues with kwin using lots of CPU when locked. I am
trying to trace down the issue and found out that there is a service
running and I want to know more about it.
What is Telepathy and why do I need it?
I am also seeing some upstream bugs associated with it and showing up on
one of the machines around here.
From what I see, it is associated with Instant Messaging but I want to
confirm before I remove it.
Hi! I just updated my laptop f31 and after reboot the 2nd desktop color is gone (now is black)
and the Desktop folder is not longer recognized (globally). (but somehow is shown if the Location is set to custom location)
somehow : the .desktop shortcuts are not recognized as applications
Did this happend to anyone? any idea about the reason (and fix)?
Hope everyone is doing well. I'm writing this email to share a few ideas
on how we can make Fedora KDE an even better out-of-the-box experience
than it already is. To put it simply, there are a few eyecandy tweaks to
be made and this would transform the already decent experience.
Since KDE Plasma uses Breeze and the colour scheme can be reflected on
both Qt and GTK applications, the GTK theme, "breeze-gtk" is a good to
have by default. This would make OOTB theming much more consistent and
would eliminate the step of downloading it later.
I think we can use a smoother and cleaner font. The default one /works/
but we can do better. What about using Fira Sans, Roboto or Cantarell?
The first two work really well in Plasma and look nice in GTK
applications too, Cantarell is also good as it is included by default.
Typography is very important, by using a nice font face while keeping it
"free as in freedom", it would improve the overall user experience.
That's about it really. Overall this is a solid distro, if we can
implement these two things, I think the overall experience can be much
improved. I was thinking of proposing the idea of using LibreOffice over
Calligra suite but using them both, I can't complain about the KDE
alternative. Keep it up folks! :)
If I can help with anything, please let me know.
Wow, perfect, thanks. It applied blur right away after enabling the script. That was quick and easy.
Best regards, Alex
‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
On Thursday, July 2, 2020 2:05 PM, Aaron E <pizzadudedotca(a)gmail.com> wrote:
> You can use the third party Kwin script "Force Blur" for this.
> On Thu., Jul. 2, 2020, 7:50 a.m. Alex Gurenko, <agurenko(a)protonmail.com> wrote:
>> Hello everyone, I'm wondering if there is a trick how to enable KDE blur on Yakuake background?
>> I saw in git there were patches for Yakuake back when blur was introduced, but to this day being on latest updates-testing packages by Yakuake still uses old transparency rather than blur.
>> Best regards, Alex
>> kde mailing list -- kde(a)lists.fedoraproject.org
>> To unsubscribe send an email to kde-leave(a)lists.fedoraproject.org
>> Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
>> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
>> List Archives: https://firstname.lastname@example.org
Hello everyone, I'm wondering if there is a trick how to enable KDE blur on Yakuake background?
I saw in git there were patches for Yakuake back when blur was introduced, but to this day being on latest updates-testing packages by Yakuake still uses old transparency rather than blur.
Best regards, Alex
I wanted to ask why plasma-workspace requires plasma-pa? On every big
update I have to remember that I need to delete the pulse executable
to get stuff working again. KDE just works fine with pure alsa. I'm
typically doing packaging on the audio engineering side of Fedora and
I use Fedora for production purposes. I have no interest in spending
time to get pulseaudio work right for every scenario on all computers
I use. There's always a glitch somewhere.
Can we drop the dependency, or, at least, is there a more elegant
workaround I can use to make KDE not spawn pulse? Not sure if I need
to file a bug for this.
Hi KDE team,
Workstation enabled earlyoom by default in Fedora 32. A search of
Bugzilla suggests it has been a pretty well-behaved change. How do we
feel about submitting this as a self-contained change proposal for
Fedora 33 KDE?
He / Him / His
Senior Program Manager, Fedora & CentOS Stream