Trying to run F24 KDE Live on a new machine. Never been used before,
it's that new.
Install checks the install medium with no issues but freezes after EDAC
sbridge - Couldn't find mci handler.
This was followed by kvm - disabled in bios. which was fixed by turning
on VT in the bios.
Motherboard is an ASUS X99 Sabertooth with latest BIOS.
Processor is an i7
nVidia Titan X video card using HDMI output or DVI.
Fedora 23 wouldn't even boot due to an X.509 error.
I need to use secure boot as this will be a dual boot with Windows 10
for some games that won't run in a VM.
Right now, I just want to get Fedora running on the machine. I would be
happy with F23.
I have left the machine in this state for almost an hour with no changes.
Downloading basic Fedora now.
I upgraded to Fedora 24 (from Fedora 23) and had two problems:
The upgrade apparently deleted kdm and did not enable sddm as my login
manager, so no graphical login. A "sudo systemctl --force enable
sddm.service" corrected the problem. Oh well, I guess I should not
have continued with kdm so long. :-)
Kmail ignored my settings[*] and created settings as if I never had
any. It _did_ know where my mail was. I had to copy kmail2rc from
~/.kde/share/config to ~/.config .
All is well now.
[*] This is quite irritating since the KDE developers have been doing
this sort of thing with the entire suite over the last several years.
They have shown a complete disdain for users' settings for all of the
KDE desktop applications and environment. It is amazing to me that it
still goes on.
Garry T. Williams
Apologies if you've already seen this note which I previously sent to
the general Fedora list.
I'll be the first to admit that I don't use Fedora in a conventional
way. But it suits me -- or it did until things started misbehaving a few
weeks ago. Now I'm finally disgusted enough to write some notes and hope
for good advice.
I run F23 with the KDE desktop in what used to be called runlevel 3. I
delete rhgb and quiet from /etc/default/grub and start X using startx
because I like to see what happens during boot. I hate systems that try
to hide what is really happening. Once KDE is running, I use eight
desktops with several windows on each one, most of them XTerms with
active SSH sessions to other machines. When I leave my desk, I lock the
screen (using the default KDE locker as configured with System Settings)
but I disable locking based on inactivity. As long as this works, I'm happy.
But it doesn't work reliably for the last few weeks. If I'm away from my
desk for more than a few minutes, the lock screen is frozen when I
return. I can't unlock. I can switch to a different virtual terminal and
kill X, but if I then try to restart X using startx again, it doesn't
come up properly. No windows appear, no panels, and neither the keyboard
nor the mouse do anything except move the cursor. I have to fall back to
When I reboot and startx again, things start up as they should. Except
that all my previous windows are on the first desktop, overlapping like
crazy. Moving them where they should be is very annoying and tedious. I
have to do this at least once per day, sometimes more often. It's not
just a matter of rearranging the windows, I also have to re-establish
all the SSH sessions. And, of course, any active commands that were
running were terminated so I may have some clean-up to do, also.
My machine is completely up-to-date with the latest Fedora. Even the
kernel is up-to-date due to the frequent reboots. The F23 was not an
upgrade, it was originally installed fresh using the workstation image
(but choosing KDE, not Gnome).
The way to configure HiDPI font and icon scaling in KDE has changed at least a couple of times: (Note: Some programs, such as Chromium and Java, ignore all these settings and have to be configured independently.)
1. In the original implementation of HiDPI support for KDE, as documented in blog posts by KDE developer David Edmundson, it was necessary to set both "force font DPI" - for fonts - and "scale display" - for everything else.
2. In January when I first installed Fedora 23, setting both "force font DPI" and "scale display" produced unexpected results - I eventually figured out that in fact, it worked much better if I just set "scale display" to 2.
3. I've since changed jobs and installed Fedora 23 on a new laptop, and with all the updates installed, it's again necessary to set both "force font DPI" and "scale display" for everything to be legible without squinting. But this it's undesirable to set both, because now with both set, most KDE applications have huge fonts. Non-KDE applications like Thunderbird look OK though.
Some possible clues as to why this has changed again:
Clue 1: If I leave "force font DPI" unset, it's actually set to 0 in a config file, and the fonts are really tiny, suggesting that 0 is being interpreted as "very small".
Clue 2: I now get these messages when I run a KDE application from a konsole:
Warning: QT_DEVICE_PIXEL_RATIO is deprecated. Instead use:
QT_AUTO_SCREEN_SCALE_FACTOR to enable platform plugin controlled per-screen factors.
QT_SCREEN_SCALE_FACTORS to set per-screen factors.
QT_SCALE_FACTOR to set the application global scale factor.
So I'm guessing that Qt has been upgraded to a newer version, but KDE hasn't been updated to take account of the changes mentioned above.
Since they are environment variables, it looks like I can set them myself without needing to wait for KDE to be fixed. So how should I set them?
I first posted this to the Fedora list, it then devolved to a nice discussion on NetworkManager. I now believe I should have posted it here first.
I have a number of machines (hardware and VMs) running CentOS 7 and KDE. In all cases firewall-config is not functional.
First, the service check boxes are not functional. When you click on one, it don't change to "checked", and nothing changes on the firewall. However you do see a "Changes applied" in the status bar at the bottom.
Sometimes, if you go to permanent mode and attempt to edit a zone, the whole desktop locks up as soon as you click on the default target dropdown. This only happened twice.
When I run firewall-config from the command line I see the following:
org.freedesktop.DBus.Error.ServiceUnknown: The name org.freedesktop.NetworkManager was not provided by any .service files
(firewall-config:5079): Gtk-CRITICAL **: gtk_tree_view_get_path_at_pos: assertion 'tree_view != NULL' failed
with the second line repeating many times and often while attempting to interact with the GUI.
We don't use NetworkManager except on laptops, and so do not install it. Though we do install NetworkManager-glib, if only because some packages require it.
After seeing a similar bug on the RHEL I also installed NetworkManager-libnm, but that did not make a difference. That RHEL bug also mentioned this problem only occurs on KDE, and not Gnome. And we only install KDE when a GUI is required, or desired.
Is the KDE/Plasma "System Load" calculation of application used memory
Currently on my system the KDE "System Load" panel widget shows 11.3G of
memory used by applications in a 24G memory system. ksysguard is the same.
MemTotal: 24689476 kB
MemFree: 1081276 kB
MemAvailable: 20106752 kB
Buffers: 4722180 kB
Cached: 7071252 kB
SwapCached: 4156 kB
Active: 8374976 kB
Inactive: 6882576 kB
Active(anon): 2623148 kB
Inactive(anon): 1005372 kB
Active(file): 5751828 kB
Inactive(file): 5877204 kB
Unevictable: 32 kB
Mlocked: 32 kB
The "top" program states 4G used which matches the /proc/meminfo. So the
11G seems incorrect...
Dr Terry Barnaby BEAM Ltd
Phone: +44 1454 324512 Northavon Business Center, Dean Rd
Fax: +44 1454 313172 Yate, Bristol, BS37 5NH, UK
Email: terry(a)beam.ltd.uk Web: www.beam.ltd.uk
BEAM for: Instrumentation, Real-Time/Parallel, Hardware/Software, Linux
"Tandems are twice the fun !"
In the past I used krunner to make on-the-fly currency conversion
(alt-f2 -> type "1$" and get Euros or Pounds). Now it seems that this
function doesn't work anymore: I can make other unit conversions
(gallons to liters, meters to miles, etc.) but currency conversion does
Anyone knows why? I cannot find anything in configuration to enable or
On 2016-06-05 16:10:19, kde-request(a)lists.fedoraproject.org wrote:
======quoted message from Florian Sievert <caleb(a)phobeus.de>, subject "Re: Plasma won't wake up after sleep. Black screen with cursor."======
> > At least twice this week when I woke up my system from sleep instead
> > of lock screen I am presented with black screen and cursor. There is
> > no way for me to get back to working system except go to tty and
> > restart sddm or reboot system. Htop doesn't seem to show any obvious
> > culprit. This is highly undesirable as I keep losing my unsaved
> I encouter this as well a few times recently, seems to be related to
> some of the latest updates. For some reason "plasmashell" seems to
> sometimes. This can be pretty painful if krunner is crashed as well
> feels like always...). So try press "ALT+F2" and run "kquitapp
> plasmashell & plasmashall" or try to get into a console and launch the
> command there. After a few seconds the desktop shall be there as
> even tho these crashs are extremly nasty...
Florian's description of "black scrren and cursor" sounds like text
mode, not an x-windows dispaly.
That being said, I don't get that problem, and I never put my system
to the sleep/hibernate state - but I get what sounds like something
simlar in principle at least once per day and often as many as 4-6
times in a day when I unlock the screen.
To me the worst part is when the screen is unlocked and this happens,
there is (of course) no panel, and all I can see is the black screen
with whatever windows were open when I locked the screen. Any windows
which were iconized when I locked it are impossible to get to.
ASIDE: +I don't know whether it's related or not, but frequently
(possibly always, although I don't always keep top running somewhere
to determine whether this is the case) before this happens I'll
notice a krunner process which is using extremely large of amounts
cpu (>100% for more than a few seconds). That causes me to wonder
whether something in krunner gets caught in a loop.
Sometimes I use the same sequence as Florian ("kquitapp plasmashell &
plasmashall") but it doesn't always work.
FWIW I also get FREQUENT error message boxes telling me that this
or that kde component has crashed. Sometimes I believe they have;
however, more often a search of /var/log and/or /var/account/pacct
does not record the crash and I suspect some other glitch in kde5 is
causing a false error message.
I've been using the KDE desktop on virtually every machine where I
have a login for longer than I can remember, and the many glitches in
kde5 make me long for the stability, usefulness, and configurability
william w. austin airedad(a)att.net
"life is just another phase i'm going through. this time, anyway ..."