As everyone knows, the KDE Plasma desktop is a release-blocking
artifact for Fedora releases. KDE is important to us, and we don't want
to go out the door with it broken.
But, there's a problem that's coming up more and more. One of the
release criteria is that all of the default applications need to have
their basic functionality tested.* This is particularly a problem with
KDE, because the SIG has decided to ship so many applications
(apparently three web browswers, now).
I'd like to propose that we either:
1) significantly reduce the number of default apps to a more managable
2) remove this particular blocking test from KDE in particular.
In either case, it would really be helpful to have more release-time
validation of shipped applications from the KDE sig.
Fedora Project Leader
In another system I get this:
# dnf upgrade
Problem 1: cannot install the best update candidate for package kajongg-16.12.3-2.fc27.noarch
- nothing provides python3-twisted >= 16.6.0 needed by kajongg-17.12.2-2.fc28.noarch
Skipping packages with broken dependencies:
kajongg noarch 17.12.2-2.fc28 fedora 4.7 M
QA is trying to consolidate target sizes for all images built by Fedora into a single document that we can easily check, in a response to one of blocking images being oversize again . The document of choice is this wiki page . In a newly added column, the target size of each release-blocking image will be documented. (It can also contain target sizes of non-blocking images, but our major focus is on the blocking ones, of course). The target size will be a blocker for Fedora Final releases.
The target sizes for KDE image are currently considered  as follows:
KDE Live 2 GB
We'd like you to think over whether this is still correct, decide on new numbers if needed, and then write it down into the document . (If you decide to change it in the future, notifying us at the same time is very appreciated.)
We'd like to avoid the situation when the image goes oversize and the target size is simply bumped, because it adds delays to the release process. So please think ahead and choose a size that you really want to keep and block on it (You can of course also choose to have no=unlimited target size).
QA suggests you choose a 4.7 GB target size (single-layer single-side DVD). The current 2 GB size was chosen probably because 2 GB flash drives were common for giveaways in the past. The technology has moved on and such small sizes are probably not common anymore.
I use the above because my session is fairly complex, involving 6
virtual desktops and a bunch of apps I like to keep open. However some
(but not all) Gnome apps don't remember which desktop they are supposed
to be on. An example of one that works is Evolution, which always
starts up on the correct desktop. A couple that don't are Firefox and
Chrome. This may be because I keep multiple tabs open on several
desktops at once. On restarting the session I get the tabs back, but
all piled up on one desktop, so I then have to move them around.
Is there a work-around for this behaviour, or am I wasting my time even
trying to do something that can't be done?
I can use from time to time an hp x2 pro which has a touchscreen. Installing fedora 27 kde was flawless, everything is working. I was able to use the onscreen board only to unblock the screen. Is it possible to launch it at least manually? Thanks, Enrique.
I would like to ask representatives of Fedora Working Groups and Spins
and Labs SIGs to work with the Fedora Marketing team and solicit
bullet points for the F28 Final release announcement.
Thanks and Regards,
Platform & Fedora Program Manager
Red Hat Czech s.r.o., Purkynova 99/71, 612 45 Brno, Czech Republic
I've just (re)installed Fedora 27 on my laptop and now the Alt-tab
switching between windows doesn't work any more.
If I create a new user it work, so I guess its just to remove a file or
edit one in order to recreate the default behavior. But which one?
Every so often, with no regularity, I get a message at login stating that python3 has crashed and that it has been reported. My question is:
Should I log out and back in to get a session with a working python3 or does python3 restart automatically after a crash? Am I losing functionality by not logging out and back in? If it doesn't restart automatically, can I restart it manually, so that I don't need to log out and back in?