I have 32 bit F23, F24 & F25 installed on an i845G test machine, host gx260.
Plasma seems to work normally, though painfully slowly, on F23. IceWM works
fine on all. F24 was created as a live (DNF) upgrade from F23 last night,
while F25 was created similarly from F23 originally and later F24 many weeks ago.
Deleting the k* files from ~/.config doesn't help with $SUBJECT. Replacing
~/.config with counterparts from F23 or F25 doesn't help, other than getting
Konsole to autostart and thus allow me to do something besides shove the
mouse pointer around. No .xsession-errors is being generated.
https://openqa.fedoraproject.org/tests/14439 shows a similar result.
Tail of ps -A run right before closing F25 session via script run in Konsole
showed as follows:
1277 tty2 00:00:00 mc
1278 ? 00:00:00 cons.saver
1279 pts/0 00:00:00 bash
1297 ? 00:00:00 kworker/0:1
1298 tty3 00:00:00 startx
1320 tty3 00:00:00 xinit
1321 tty3 00:00:02 Xorg
1324 ? 00:00:00 startkde
1333 ? 00:00:00 dbus-launch
1334 ? 00:00:00 dbus-daemon
1347 ? 00:00:00 ssh-agent
1383 ? 00:00:00 start_kdeinit
1384 ? 00:00:00 kdeinit5
1385 ? 00:00:00 klauncher
1388 ? 00:00:01 kded5
1390 ? 00:00:00 kcminit_startup
1405 ? 00:00:01 kglobalaccel5
1407 ? 00:00:00 kwrapper5
1409 ? 00:00:01 ksmserver
1410 ? 00:00:00 kaccess
1415 ? 00:00:00 kactivitymanage
1425 ? 00:00:01 kwin_x11
1426 ? 00:00:00 baloo_file
1429 ? 00:00:02 krunner
1434 ? 00:00:00 kscreen_backend
1439 ? 00:00:05 plasmashell
1449 ? 00:00:00 polkit-kde-auth
1455 ? 00:00:00 xembedsniproxy
1462 ? 00:00:00 kmix
1468 ? 00:00:01 konsole
1477 pts/1 00:00:00 bash
1483 pts/2 00:00:00 bash
1533 ? 00:00:00 drkonqi
1545 ? 00:00:00 kworker/u8:2
1550 pts/1 00:00:00 ps
What, if anything, can I do that might lead to whatever this bug is getting
fixed? I don't see any open BRC bugs that I can recognize as being on point.
This is not the first F24 installation I've had acting similarly. Total F24
installations here, both 32 bit and 64, is upwards of a dozen.
BTW, the restore previous session setting is not producing a restoring of the
Konsole session left open on session close, only an empty desktop.
"The wise are known for their understanding, and pleasant
words are persuasive." Proverbs 16:21 (New Living Translation)
Team OS/2 ** Reg. Linux User #211409 ** a11y rocks!
Felix Miata *** http://fm.no-ip.com/
With the up and coming F24 beta release I wonder if anyone here is using F24
and the PIM suite, specifically Kmail as I "think" that uses Kmail 5
Any comments on how well kmail performs or any issues with it would be
appreciated. If I where to switch/test it would be with IMAP accounts.
Fedora 23 (Twenty Three)
Registered Linux user number #342953
I am using Fedora 24 with the latest updates.
I decided to try kmail again in this computer. I have erased the
previous data, since it corresponds to imap accounts. And I have started
again to add all the missing accounts.
In the process I found out that the default driver is now sqlite3, the
spec file even says that so this is not a surprise. :-)
My problem is that for some imap folders I have to restart the akonadi
server because it loads 100 (exactly 100 messages, not more and not
less) and then it stops. The only way to proceed is to restart the
akonadi server again and it will process another 100 messages and the
This does not happens for every folder, only for some, but for those
the only way to work is to load 100 each time and that can be extremely
boring for large folders.
Any help to solve this issue or at least to temporarily to increase
the 100 messages limit?
I tried to find any documentation on how to do this but I failed. :-(
After the recent update of Phonon and leaving positive karma I have since
noticed a minor problem :-(
The login and log off sound events do not work now and neither do the sound
notifications in KDE Connect. All other notifications AFAICT are OK.
Reverting back to phonon-4.8.3-7.fc23.x86_64 and all is well.
Does anyone else see this?
Fedora 23 (Twenty Three)
Registered Linux user number #342953
Dear fedora kde contributors,
I have recently reopened one of my old Qt projects and found that there
is no debugging output in stdout. After some time I have came to
#1227295. In that ticket is Fedora overriding Qt default settings of
Rex suggested me to open discussion here ratter than opening new ticket
Honestly, I don't see much explanation why you decided for that and I
would like to have opposite configuration (default Qt) in Fedora as
> This is by design. Our users do not want to get spammed with
> debugging output by default. It is easy for developers to enable it.
> (We are also working on packaging the GUI KDE now ships for editing
> qtlogging.ini to make it even easier.)
> I think the only sane distro default for qDebug is globally off
> by default.
In my opinion the debugging messages are normal and expected in output
of any application.
End users usually cannot see those messages, because they are running
application without terminal. I don't see any impact to them.
Some power users may run UI applications from terminal. But what they
expect to see there? Personally, I do that as first step in debugging
of the application.
The fedora is focused also on developers. Every qml tutorial starts
with console.log("hello world"); which suddenly doesn't work on fedora.
Maybe we should disable just part of debugging output to decrease
verbosity similar like Qt does:
Alternatively, we could improve user experience of developers by
changing this configuration during installation of qt5-devel packages.
Jozef Mlich <jmlich83(a)gmail.com>
Given that upstream uses kde-gtk-config now, any objection to EOL'ing kcm-
gtk/xsettings-kde for f24+ ?
Plan (probably) would be for f24+ builds of kde-gtk-config to Obsoletes:
those other items for an upgrade path.
Any comment or objection?
For years, I have been using the kdeforge.repo file,
but since a while, I have been having
difficulties/impossibility to get anything.
I spent the last hour trying to muddle through the
various repo files and I am unable to determine which
is the one to use: kde.repo, kdeforge.repo, kde-
Also, and this is where the problem seems to lie, some
of these repo files refer to the mirrorlist at:
while other of these repo files refer to the location
of the mirrorlist at:
No matter which combination I seem to try, dnf hangs
for ages and then returns and error:
Failed to synchronize cache for repo 'kde-unstable'
Cannot download, all mirrors were already tried
without success, disabling.
So, how do I get this working? Which is the correct
repo file and which is the correct location of the