I am currently in Fedora 25, KDE (live) and Anaconda crashes when I open
it. I tried to report a bug but by default it has set my default language
to Hindi (because I'm from India). Now I can speak Hindi fluently and can
read it fine, but reporting a bug in Hindi, and not being able to change it
is quite frustrating.
Now I don't have a problem with Hindi whatsoever, but wouldn't it be better
to have the default language set to English anyway, and then give the user
the option to change it, if they want to?
I've been having problems with my Bluetooth mouse for a long time now.
My PC has a dongle and BT randomly disconnects when I reboot or even
return from hibernation or suspend. I've put "hciconfig hci0 up" in an
rc.local script to try to force it but even that only works some of the
However aside from all that, I've now noticed that it frequently
disconnects even if I log out of Plasma and back in again. This means I
have to keep an extra mouse around just to activate it.
This is ridiculous. Is anyone else seeing a similar problem?
The first Kannolo ISOs ever are now available for download.
Kannolo is an installable graphical Fedora Remix without GTK+, based on the
KDE Plasma Desktop workspace and the Calamares installer. About the name: A
"torta fedora" is a Sicilian cake. A "cannolo" is a similar Sicilian sweet
with a different shape. The 'K' stands for "KDE".
There is currently a version based on the upstream release 25, and a version
based on the upstream release 24, both with all updates up to 2016-12-15.
Only x86_64 images are available at this time.
You can find more information and screenshots at:
You can find these (and eventually future) releases in the Files section:
Future release announcements will be posted on:
I am unable to start multiple Qt Creator instances on Fedora 25. If I
start one instance, subsequent invokations seem to start the program but
no window comes up. I can see the second instance running in KSysGuard,
taking up 25% CPU. Even if I close the first instance, the second one
won't come up.
But if I then try to start it again, it comes up fine. But if I try to
get one more instance running, that won't come up. I end up with one
more Qt Creator process with 25% CPU utilisation.
Anybody else seeing this?
Thanks and regards,
The situation is this.... I have a dual monitor setup. One on HDMI the other on DP.
Once in a while the monitor on DP won't restore have being switched off by the "Energy
Savings" settings. There are several ways I've found to get it back.
1. Disconnect/reconnect the cable.
3. Disable/Enable the monitor in "System Settings". But this turns out to be multi-step
process since at one point the monitors will combine in the display and I need to move
them apart otherwise I just get a duplicate monitors. Not a big deal....just a pain.
So, can anyone take a stab at what a command line entry would be for option #3 above?
You're Welcome Zachary Quinto
Good morning friends. I have recently deployed F25 KDE (currently Plasma 5.8.4, Frameworks 5.27.0, Qt 5.7.0, Kernel 4.8.11-300) in my machine. A fresh install, not an upgrade. Over the past couple of days I attempted to run specific applications that demand root privileges through the provision of the root password. Examples include KDE Partition Manager and KUser. When I open them, I'm prompted with the root password input window (as expected), type it and... nothing happens! Apps simple do not open! Can you guys shed some light on what might be happening? Many thanks in advance!
I just ran an upgrade on my system from F24 to F25.
Now, usually after five minutes but sometimes in less than one minute,
the entire task bar freezes.
If I don't hurry up and start the applications I want to run, I cannot
start anything else.
I tried rebooting to the last known good (F24) kernel. No joy.
What's going on here? If I don't solve the problem soon, I'll have to
abandon this system and fall back to a Windows laptop to guard my e-mail.
In F25 the SDDM no longer shows a list of users when NIS (ypbind) is
enabled and also it does not default to the last user logged in. kdm
appears to be the same (with UserList=true in /etc/kde/kdm/kdmrc).
Is this a bug or a new feature (maybe to handle the case where you don't
want all users listed on a networked system) ?
I've used KDE for years and never had a serious issue. Yesterday
(11/19) morning I did a "dnf update" and updated to the latest available
patches (I do this every 2-3 weeks or so). Nothing relayed to KDE was
updated as far as I could tell, but the kernel was updated from 4.8.4 to
4.8.7. Upon rebooting after the update, I got the sddm login screen as
usual. I entered my name and password as usual. The KDE starting
splash screen appeared as usual.
After that is when the unusual happened. I got a blank screen. No
panels (I have one along the bottom), no icons, no initial konsole
window. Using Alt-Tab showed the konsole window but I could not bring
it to the current screen. The mouse was active. I noticed a faint
white line at the left edge. Clicking on it with my mouse and dragging
it to the right expanded what was my konsole window. Apparently it was
off screen to the left.
I rebooted on the older 4.8.4 kernel and all was fine. I removed and
reinstalled the 4.8.7 kernel. That did not help. (This morning a newer
4.8.8 kernel and I tried that but it behaved the same as with the 4.8.7
Thinking that perhaps something buried in my home directory might be
causing this, I created a new user. That new user had the exact same
issues. I also looked in ~.xsession-errors. Nothing there that
indicated any problem. Nothing in /var/log/Xorg.0.log, either. I
didn't see anything in the recent archives of this list.
Anyone else seen this issue? I'm out of ideas at this time. I'll keep
running the older 4.8.4 kernel since that works.
I'll be glad to supply any additional information anyone thinks might help.
Thanks for any help or suggestions
When Plasma 5.8.3 and kf5-kio-core-5.27.0-1.fc24.x86_64 arrived into
F24, I started experiencing
"the process for file procotol is dead unexpectedly"
error messages when opening file picker in Qt based applications.
I opened bugreport  and then I started trying to retrieve debuginfos.
I installed kdebugsettings, enabled the KIO debug messages, but I don't
see any message related to the crash in both ~/.xsession-errors and
journalctl. I attach
~/.config/QtProject/qtlogging.ini at URL