[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#1034169: libqt5core5a: upgrade to 5.15.8+dfsg-4 stops krunner shortcut from working



Found this:

$ systemctl --user status plasma-krunner
× plasma-krunner.service - KRunner
    Loaded: loaded (/usr/lib/systemd/user/plasma-krunner.service; static)
    Active: failed (Result: signal) since Mon 2023-04-10 21:11:08 CEST; 14s ago
  Duration: 5.239s
   Process: 10623 ExecStart=/usr/bin/krunner (code=killed, signal=SEGV)
  Main PID: 10623 (code=killed, signal=SEGV)
       CPU: 4.176s

apr 10 21:11:03 SAT systemd[3611]: Starting plasma-krunner.service - KRunner...
apr 10 21:11:03 SAT systemd[3611]: Started plasma-krunner.service - KRunner.
apr 10 21:11:08 SAT systemd[3611]: plasma-krunner.service: Main process exited, code=killed, status=11/SEGV
apr 10 21:11:08 SAT systemd[3611]: plasma-krunner.service: Failed with result 'signal'.
apr 10 21:11:08 SAT systemd[3611]: plasma-krunner.service: Consumed 4.176s CPU time.

...

$ gdb /usr/bin/krunner
GNU gdb (Debian 13.1-2) 13.1
Copyright (C) 2023 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-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
<https://www.gnu.org/software/gdb/bugs/>.
Find the GDB manual and other documentation resources online at:
   <http://www.gnu.org/software/gdb/documentation/>.

For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from /usr/bin/krunner...
(No debugging symbols found in /usr/bin/krunner)
(gdb) r
Starting program: /usr/bin/krunner  
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[New Thread 0x7ffff03ff6c0 (LWP 10743)]
[New Thread 0x7fffef9e76c0 (LWP 10744)]
[New Thread 0x7fffeccbe6c0 (LWP 10745)]
[New Thread 0x7fffe67ff6c0 (LWP 10746)]
[New Thread 0x7fffe5ffe6c0 (LWP 10747)]
[New Thread 0x7fffe57fd6c0 (LWP 10748)]
[New Thread 0x7fffe4ffc6c0 (LWP 10749)]
[New Thread 0x7fffd8dff6c0 (LWP 10750)]
[New Thread 0x7fffbbfff6c0 (LWP 10751)]
[New Thread 0x7fffc3fff6c0 (LWP 10752)]
[New Thread 0x7fffc37fe6c0 (LWP 10753)]
[New Thread 0x7fffc2ffd6c0 (LWP 10754)]
[New Thread 0x7fffc27fc6c0 (LWP 10755)]
[New Thread 0x7fffc1ffb6c0 (LWP 10756)]
[New Thread 0x7fffc17fa6c0 (LWP 10757)]
[New Thread 0x7fffc0ff96c0 (LWP 10758)]
[New Thread 0x7fffbb7fe6c0 (LWP 10759)]
[New Thread 0x7fffbaffd6c0 (LWP 10760)]
[New Thread 0x7fffba7fc6c0 (LWP 10761)]
[New Thread 0x7fffb9ffb6c0 (LWP 10762)]
[New Thread 0x7fffb97fa6c0 (LWP 10763)]
[New Thread 0x7fffb8ff96c0 (LWP 10764)]
[Thread 0x7fffb8ff96c0 (LWP 10764) exited]
[New Thread 0x7fffb8ff96c0 (LWP 10765)]
[Thread 0x7fffb8ff96c0 (LWP 10765) exited]
[New Thread 0x7fffb8ff96c0 (LWP 10766)]

Thread 1 "krunner" received signal SIGSEGV, Segmentation fault.
0x00007ffff4a9814a in ?? () from /lib/x86_64-linux-gnu/libdbus-1.so.3
(gdb) bt
#0  0x00007ffff4a9814a in ?? () from /lib/x86_64-linux-gnu/libdbus-1.so.3
#1  0x00007ffff4a982d2 in ?? () from /lib/x86_64-linux-gnu/libdbus-1.so.3
#2  0x00007ffff4a982d2 in ?? () from /lib/x86_64-linux-gnu/libdbus-1.so.3
#3  0x00007ffff4a982d2 in ?? () from /lib/x86_64-linux-gnu/libdbus-1.so.3
#4  0x00007ffff4a98608 in ?? () from /lib/x86_64-linux-gnu/libdbus-1.so.3
#5  0x00007ffff4a98743 in ?? () from /lib/x86_64-linux-gnu/libdbus-1.so.3
#6  0x00007ffff4a98a40 in _dbus_type_reader_set_basic () from /lib/x86_64-linux-gnu/libdbus-1.so.3
#7  0x00007ffff4a9604b in _dbus_header_set_field_basic () from /lib/x86_64-linux-gnu/libdbus-1.so.3
#8  0x00007ffff4a9a92d in ?? () from /lib/x86_64-linux-gnu/libdbus-1.so.3
#9  0x00007ffff4a9c793 in dbus_message_iter_append_basic () from /lib/x86_64-linux-gnu/libdbus-1.so.3
#10 0x00007ffff69c990b in ?? () from /lib/x86_64-linux-gnu/libQt5DBus.so.5
#11 0x00007ffff69cb8f1 in ?? () from /lib/x86_64-linux-gnu/libQt5DBus.so.5
#12 0x00007ffff699e8b0 in ?? () from /lib/x86_64-linux-gnu/libQt5DBus.so.5
#13 0x00007ffff699854d in ?? () from /lib/x86_64-linux-gnu/libQt5DBus.so.5
#14 0x00007ffff699b2a8 in ?? () from /lib/x86_64-linux-gnu/libQt5DBus.so.5
#15 0x00007ffff6986f3b in QDBusConnection::call(QDBusMessage const&, QDBus::CallMode, int) const ()
  from /lib/x86_64-linux-gnu/libQt5DBus.so.5
#16 0x00007ffff69a4000 in ?? () from /lib/x86_64-linux-gnu/libQt5DBus.so.5
#17 0x00007ffff69a6455 in QDBusAbstractInterfaceBase::qt_metacall(QMetaObject::Call, int, void**) ()
  from /lib/x86_64-linux-gnu/libQt5DBus.so.5
#18 0x00007ffff69a65c7 in QDBusAbstractInterface::qt_metacall(QMetaObject::Call, int, void**) ()
  from /lib/x86_64-linux-gnu/libQt5DBus.so.5
#19 0x00007ffff0b886a5 in ?? () from /lib/x86_64-linux-gnu/libQt5XcbQpa.so.5
#20 0x00007ffff5ebebea in QMetaProperty::read(QObject const*) const ()
  from /lib/x86_64-linux-gnu/libQt5Core.so.5
#21 0x00007ffff5ee4bee in QObject::property(char const*) const ()
  from /lib/x86_64-linux-gnu/libQt5Core.so.5
#22 0x00007ffff0b749ca in ?? () from /lib/x86_64-linux-gnu/libQt5XcbQpa.so.5
#23 0x00007ffff0b74fbe in ?? () from /lib/x86_64-linux-gnu/libQt5XcbQpa.so.5
#24 0x00007ffff0ad823e in QXcbIntegration::accessibility() const ()
  from /lib/x86_64-linux-gnu/libQt5XcbQpa.so.5
#25 0x00007ffff6306b6c in QAccessible::isActive() () from /lib/x86_64-linux-gnu/libQt5Gui.so.5
#26 0x00007ffff6306d75 in QAccessible::updateAccessibility(QAccessibleEvent*) ()
  from /lib/x86_64-linux-gnu/libQt5Gui.so.5
#27 0x00007ffff7ae8537 in QQuickAccessibleAttached::QQuickAccessibleAttached(QObject*) ()
  from /lib/x86_64-linux-gnu/libQt5Quick.so.5


Il 10/04/23 20:43, Samuel Thibault ha scritto:
Antonio, le lun. 10 avril 2023 20:40:12 +0200, a ecrit:
I confirm this problem,
Ok, but I'd need a way to reproduce it to be able to fix the change...

Samuel

Reply to: