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.
(Posting to many mailing lists for visibility. I apologize if you see
this more times than you'd like.)
You may have already seen my Community Blog post about changing the
Release Readiness meeting process. The meeting has questionable value
in the current state, so I want to make it more useful. We'll do this
by having teams self-report readiness issues on a dedicated wiki
page beginning now. This gives the community time to chip in and
help with areas that need help without waiting until days before the
I invite teams to identify a representative to keep the wiki page up
to date. Update it as your status changes and I'll post help requests
in my weekly CommBlog posts and the FPgM office hours IRC
meeting. The Release Readiness meeting will be shortened to one hour
and will review open concerns instead of polling for teams that may or
may not be there. We will use the logistics mailing list to discuss
issues and make announcements, so I encourage representatives to join
He / Him / His
Senior Program Manager, Fedora & CentOS Stream
A thread on the Fedora Users list (see:
mentioned an instance of Dolphin being started without the user
configuring it as an Autostart item. I do use Autostart to fire up
several Dolphin windows at login, but lately I've been noticing an
extra one that I haven't asked for. A little research shows it
apparently being started by systemd.
Anyone know what's going on?
Q4Wine is a KDE based application, to manage wine prefixes (bottles) and to make easy use of tools that wine offers. It's being developer outside of Fedora, but in the past it was well maintained and it saw regular updates. Sadly, the maintainer has been unable to contribute further, causing Q4Wine to miss some updates.
As of writing, builds fails on Koji because of a QtCore related issue. Since my knowledge of these technologies is limited, I figured it would be best to turn to those who are most experienced with Qt.
I hope this is not the wrong place to ask. If it were possible for any of you to take a look at this precious program, then that would be much appreciated.
Kevin "Eonfge" Degeling
Dear Fedora Experts,
I've just completed the migration of my Linux box from Fedora 23 to 31 but
still have some problems in "importing" my old korganizer, knotes and
I usually use the akonadi to import all of them through the akonadi applet
I was used to find in my system tray (aknoaditray, I suppose) but it seems
that it is not there anymore. At least in my fresh installed Fedora 31.
Do I missed to install something or something has changed with the newest
Currently what it is installed about akonadi is:
rpm -qa | grep -i akonadi
Yesterday I sent out a QA-related proposal that directly affects the
release criteria for KDE x86_64 and Workstation x86_64 and (probably)
aarch64 images. The proposal is attached below and also available in the
test list (including some follow-ups which are recommended to read):
Can you please review that proposal and post your thoughts, if you have
any? (Responding to test list is preferred, so that we can discuss it in a
single place, but responding here is fine as well). Thank you.
---------- Forwarded message ---------
From: Kamil Paral <kparal(a)redhat.com>
Date: Mon, Feb 17, 2020 at 3:20 PM
Subject: proposal: Default application functionality criterion reduction
To: test <test(a)lists.fedoraproject.org>
This proposal intends to reduce the scope of the “*Default application
functionality*” release criterion :
All applications that can be launched using the standard graphical
> mechanism of a release-blocking desktop after a default installation of
> that desktop must start successfully and withstand a basic functionality
*= Background =*
The area which QA is responsible for has been growing and growing in recent
years. We used to have just a single Fedora release with two blocking
desktops (GNOME and KDE). Then Editions got introduced and we started
testing Workstation, Server, Cloud and the KDE Spin. Additional
architectures were introduced (fortunately i386 got obsolete) and we
started testing and blocking on specific images on armhfp and aarch64.
Currently there are 13 release blocking deliverables mentioned on the
ReleaseBlocking page . That list is not complete, though. Fedora CoreOS
became an official edition lately, and even though its release cycle is not
tied to traditional Fedora release cycle (and that’s why it’s not mentioned
on that wiki page), as an official edition QA should care about it as well.
It is the same story with Fedora IoT, another recent release-blocking
addition . Desktop testing is one of the most time-consuming jobs with
the most frequent bug occurrence. Right now, we’re supposed to be fully
testing and blocking on GNOME, KDE and XFCE (although XFCE might get
dropped in favor or aarch64 Workstation ). We cannot test all of this
and honestly claim that we verified basic functionality of all the included
apps on all these desktops. I believe we need to adjust the criterion and
align it closer with reality. In my eyes, it’s better to have a narrower
scope and perform it well than having a large scope and perform it poorly.
*= Proposal =*
Change the criterion to something along these lines:
All applications that can be launched using the standard graphical
> mechanism after a default installation of Fedora Workstation on x86_64
> architecture must start successfully and withstand a basic functionality
> For other release-blocking desktops (on any architecture), the
> requirements only apply to the following types of applications:
> * web browser (e.g. firefox) 
> * file browser (e.g. nautilus)
> * package manager (e.g. gnome-software)
> * image viewer (e.g. eog)
> * document viewer (e.g. evince)
> * text editor (e.g. gedit)
> * archive manager (e.g. file-roller)
> * terminal emulator (e.g. gnome-terminal) 
> * problem reporter (e.g. abrt)
> If there are multiple applications of the same type (e.g. several web
> browsers), only one of them needs to satisfy the requirements.
As you can see, the original criterion was kept for Fedora’s flagship
desktop edition, the one that is most prominent on https://getfedora.org
and probably the one that most newcomers download. We would still verify
everything on Fedora Workstation on x86_64. But any other desktop
(including Workstation on aarch64) would get just reduced criteria, because
we simply can’t ensure the same quality bar for the smaller desktop
editions/spins. There are some high-profile types of applications that I
considered including in the list above, but didn’t in the end:
* word editor (e.g. libreoffice-writer)
* spreadsheet editor (e.g. libreoffice-calc)
* video player (e.g. totem)
* help viewer (e.g. yelp)
I’d like to hear your thoughts on whether they should be included or not.
Of course from an end-user point of view, it would be beneficial. But the
question is whether we as QA can promise their testing. And also whether we
want to block the release e.g. if Gnumeric is broken on armhfp XFCE or if
totem doesn’t work on aarch64. Yes, it’s unpleasant, but people using
alternative desktops and architectures are usually far from beginners. It’s
usually not difficult to install a different application. Also note that
the apps included in x86_64 Workstation will be thoroughly tested so they
should be very likely to work well even on other architectures (minus some
I’d like to target Fedora 32 with this proposal, which means we should
decide on this proposal fast. (I wanted to propose it much sooner, but I
was waiting on clarifications about new release-blocking images and also on
some fesco tickets , some of which is still not clarified; so I’m sorry
about a late proposal).
Please comment, thanks.
 These two are required to work even in Basic release criteria , but
I decided to include them anyway to avoid confusion (“why is the web
browser missing?”), and to make it clear that they need to satisfy the
basic functionality (whereas for Basic release criteria just the barebone
functionality might be deemed enough)
An issue seems to have cropped up with the recent update to kernel 5.5.5-200.
I have the setting for Screen Energy Saving, Switch off after 4 min. The switch off occurs just fine.
However when I move the mouse the screen does come to life but there is no cursor and things
appear frozen. After a few more seconds the screen blinks off/on and everything is OK.
Anyone else seeing this?
The key to getting good answers is to ask good questions.
As part of an ongoing thread on the Evolution list:
it turns out that logging into KDE creates a new session (in the sense
of loginctl(1)) but logging out doesn't terminate it. Thus every time
you log out and in again the number of sessions increases. You can
verify this by running 'loginctl --list-sessions'.
Is this a bug?
When using Dolphin to monitor a directory, I find that modifications
from outside Dolphin, such as creating or deleting files from the
Shell, sometimes don't update the current view until I hit F5. Other
times, the files appear or disappear immediately. Unless my memory is
failing, the F5 never used to be required. What has changed?
I'm currently on dolphin-19.12.1-1.fc31.x86_64 but this has been an
issue for several weeks.