If I boot the live USB of the KDE / Fedora 30 the gui quickly freezes
up requiring a reboot.
But if I boot the regular F30 Workstation / Gnome version I can
install and use (at least Gnome) fine.
Any suggestions on where to start looking, or what to bugzilla?
I know that RHEL8 isn't out yet, but I'd like to run KDE on my RHEL8
Beta. Even if it's just the basic KDE desktop.
I'm fine building it myself, but I'm having a hard time figuring out
the rebuild flow.
If I (or anyone) were to rebuild KDE for RHEL8, where do I start? and
then what's next?
There are base QT5 packages in RHEL8 beta. Do you think I would need
to rebuild QT5? Or just start with RHEL8's QT5 packages.
Yesterday I have installed the latest F30 from the KDE Live media onto
my laptop, and so far it works great. The only problem I have is the
functionality of the "menu" key (sitting in between the AltGr and
right Ctrl keys on my keyboard).
Apparently, pressing that key gives a popup menu at the position of the
mouse pointer, as if I have pressed the right mouse button. In my
usecase, this behavior is useless (I use two-finger tap on the
touchpad to invoke that menu), so I want to reassign the menu key to do
something else (such as opening the KDE application menu or whatever
However, if I try to assign that key to any shortcut, instead of
capturing the keypress, the popup menu appears instead.
My google-fu failed me, since searching for anything involving "menu
key" brings up a bunch of hits describing how to assign some key
to open a menu, instead of talking about the menu key.
The only relevant suggestion I found was to reassign the keycode of the
menu key to some nonexisting regular key like F13, using xmodmap. But
this seems to be a kludge, and I'm wondering if there is a "proper" way
in Plasma to configure the behavior of the menu key.
This issue is a reappearance of an old bug  from 2008, which seems to
have been resolved in 2015, but apparently regressed again in the
On F30, I am trying again kde on wayland. This time, it seems to be quite
usable! I need the virtual screens, and I'm happy to see this feature is
Unfortunately, I also need x2goclient, which segfaults on kde wayland
client. So I guess I'll have to wait some more.
I've gone several rounds trying to install Fedora 30 (KDE Spin) on a new
LG Gram 17 laptop. It seems that either it needs a windows driver to
make the trackpad work, or it a Microsoft linux bomb. The trackpad works
while in windows setup mode but when I boot the Fedora Live cd the
trackpad no longer works.
Also the live cd won't even boot unless I set acpi=off
Thanks in advance
For the very first time, I did not do a clean install: I used the dnf system-upgrade method successfully. I notice, after a few hours of use, that:
- Plasma on Wayland results in a black screen. First, the desktop background appeared, then it went to black as a Korganizer to-do appeared that I dismissed and then the screen went black again. After a long wait, nothing happened. The mouse pointer worked, but no plasma desktop.
- Plasma on Xorg works as in Fedora 29, when doing a fresh boot. However, when resuming from suspend, a black screen results, requiring a reboot. I have only tried this one time so far, so I do not know if it is repeatable.
I am having trouble getting qDebug() output displayed in the
'application output' tab in Qt Creator.
I am aware of the need to explicitly enable Qt message logging and have
the following in my ~/.config/QtProject/qtlogging.ini:
But even with this, Qt Creator does not show any qDebug() messages. I am
getting these messages if I run the application from Konsole. Just not
in Qt creator.
Any Idea on what can be done to fix this?
I'm on Fedora 29, Qt 5.11.3, Qt Creator v4.7.2.
Thanks and regards,