After updating from F29 to F30, I now find that dnfdragora is running
in my KDE/Plasma session. I prefer to update my system from the command
line, so would like to inhibit this, but I don't see where it's being
It's not among the Autostart apps, and 'systemctl|grep dnfdragora'
A hint would be welcome.
I got a crash with kontact/kmail with the latest updates applied:
It seems that the latest code triggers an assert in the malloc (I left this
same information in the icu at bodhi).
My workaround for the moment was to downgrade libicu to the previous version,
For reference I get this:
$ gdb /usr/bin/kontact
GNU gdb (GDB) Fedora 184.108.40.20690424-24.fc30
Copyright (C) 2019 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
Type "show copying" and "show warranty" for details.
This GDB was configured as "x86_64-redhat-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
Find the GDB manual and other documentation resources online at:
For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from /usr/bin/kontact...
(No debugging symbols found in /usr/bin/kontact)
Missing separate debuginfos, use: dnf debuginfo-install
Starting program: /usr/bin/kontact
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib64/libthread_db.so.1".
[New Thread 0x7fffdc50d700 (LWP 5259)]
[New Thread 0x7fffda873700 (LWP 5260)]
[New Thread 0x7fffd8c34700 (LWP 5261)]
kontact: malloc.c:2389: sysmalloc: Assertion `(old_top == initial_top (av) &&
old_size == 0) || ((unsigned long) (old_size) >= MINSIZE && prev_inuse
(old_top) && ((unsigned long) old_end & (pagesize - 1)) == 0)' failed.
Thread 1 "kontact" received signal SIGABRT, Aborted.
0x00007ffff6750eb5 in raise () from /lib64/libc.so.6
#0 0x00007ffff6750eb5 in raise () from /lib64/libc.so.6
#1 0x00007ffff673b895 in abort () from /lib64/libc.so.6
#2 0x00007ffff679a5f9 in __malloc_assert () from /lib64/libc.so.6
#3 0x00007ffff679c7af in sysmalloc () from /lib64/libc.so.6
#4 0x00007ffff679db75 in _int_malloc () from /lib64/libc.so.6
#5 0x00007ffff679ed3f in malloc () from /lib64/libc.so.6
#6 0x00007ffff5014e44 in icu_63::UnicodeSet::ensureBufferCapacity(int) ()
#7 0x00007ffff50156cc in icu_63::UnicodeSet::add(int const*, int, signed
char) () from /lib64/libicuuc.so.63
#8 0x00007ffff50159eb in icu_63::UnicodeSet::addAll(icu_63::UnicodeSet
const&) () from /lib64/libicuuc.so.63
#9 0x00007ffff501137f in
icu_63::SymbolTable const*, icu_63::UnicodeString&, unsigned int,
icu_63::UnicodeSet& (icu_63::UnicodeSet::*)(int), int, UErrorCode&) () from /
#10 0x00007ffff5011a2d in
icu_63::ParsePosition&, icu_63::SymbolTable const*, UErrorCode&) ()
#11 0x00007ffff5011af8 in
icu_63::UnicodeSet::applyPattern(icu_63::UnicodeString const&, UErrorCode&) ()
#12 0x00007ffff5011bfb in icu_63::UnicodeSet::UnicodeSet(icu_63::UnicodeString
const&, UErrorCode&) () from /lib64/libicuuc.so.63
#13 0x00007fffef5bf928 in ?? () from /lib64/libQt5WebEngineCore.so.5
#14 0x00007fffef5bfa3e in ?? () from /lib64/libQt5WebEngineCore.so.5
#15 0x00007fffef5bfa8f in ?? () from /lib64/libQt5WebEngineCore.so.5
#16 0x00007fffef6ee76b in ?? () from /lib64/libQt5WebEngineCore.so.5
#17 0x00007fffef6ee94e in ?? () from /lib64/libQt5WebEngineCore.so.5
#18 0x00007fffef6ef20c in ?? () from /lib64/libQt5WebEngineCore.so.5
#19 0x00007fffef6ef2b2 in ?? () from /lib64/libQt5WebEngineCore.so.5
#20 0x00007fffed38ab3b in ?? () from /lib64/libQt5WebEngineCore.so.5
#21 0x00007fffef6f16d3 in ?? () from /lib64/libQt5WebEngineCore.so.5
#22 0x00007fffed3387bd in ?? () from /lib64/libQt5WebEngineCore.so.5
#23 0x00007fffeef10692 in ?? () from /lib64/libQt5WebEngineCore.so.5
#24 0x00007fffed3a4143 in ?? () from /lib64/libQt5WebEngineCore.so.5
#25 0x00007fffed3a53f4 in ?? () from /lib64/libQt5WebEngineCore.so.5
#26 0x00007ffff6088d77 in ?? () from /lib64/libQt5WebEngineWidgets.so.5
#27 0x00007ffff60899e3 in QWebEnginePage::QWebEnginePage(QObject*) () from /
#28 0x00007ffff7f4d36f in ?? () from /lib64/libkontactprivate.so.5
#29 0x00007ffff7f4d72c in ?? () from /lib64/libkontactprivate.so.5
#30 0x00007ffff7f4e533 in Kontact::MainWindow::initAboutScreen() () from /
#31 0x00007ffff7f551cf in Kontact::MainWindow::initWidgets() () from /lib64/
#32 0x00007ffff7f553ab in Kontact::MainWindow::initGUI() () from /lib64/
#33 0x00007ffff7f57085 in Kontact::MainWindow::MainWindow() () from /lib64/
#34 0x000055555555adc2 in ?? ()
#35 0x00007ffff7f26d55 in
KontactInterface::PimUniqueApplication::start(QStringList const&, bool) ()
#36 0x0000555555559be8 in ?? ()
#37 0x00007ffff673cf33 in __libc_start_main () from /lib64/libc.so.6
#38 0x000055555555a4ee in _start ()
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,