Bug 360056 - crash
Summary: crash
Status: RESOLVED DOWNSTREAM
Alias: None
Product: yakuake
Classification: Applications
Component: general (show other bugs)
Version: 3.0.2
Platform: Arch Linux Linux
: NOR crash
Target Milestone: ---
Assignee: Eike Hein
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-03-04 09:59 UTC by ybsar
Modified: 2016-12-27 12:16 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments
backtrace with full debug symbols (4.03 KB, text/plain)
2016-03-14 12:57 UTC, ybsar
Details

Note You need to log in before you can comment on or make changes to this bug.
Description ybsar 2016-03-04 09:59:23 UTC
Description:
yakuake does not run anymore after upgrade (2.9.9-5 -> 3.0.2-1).

Additional info:
* yakuake 3.0.2-1
* kglobalaccel 5.19.0-1
* konsole 15.12.2-1

Steps to reproduce and actual results:
$ yakuake
Couldn't start kglobalaccel from org.kde.kglobalaccel.service: QDBusError("org.freedesktop.DBus.Error.Spawn.ChildSignaled", "Process org.kde.kglobalaccel received signal 6")
Failed to connect to the kglobalaccel daemon QDBusError("org.freedesktop.DBus.Error.NameHasNoOwner", "Could not get owner of name 'org.kde.kglobalaccel': no such name")

$ kglobalaccel5 &
$ yakuake
Segmentation fault (core dumped)


Reproducible: Always
Comment 1 Eike Hein 2016-03-04 10:33:12 UTC
I can't really do anything about this crash report, sorry - your problem is kglobalacceld rather than Yakuake, and a segfault without a backtrace doesn't allow pinpointing the kglobalacceld problem either. I'd suggest going by your distro's KDE packagers to ask if they've heard of kglobalacceld problems in their distro lately.
Comment 2 ybsar 2016-03-05 13:51:31 UTC
I preliminary reported this issue to my distro: https://bugs.archlinux.org/task/48447
A report from KDE crash handler is attached: https://bugs.archlinux.org/task/48447?getfile=13910
Comment 3 ybsar 2016-03-13 10:05:17 UTC
The kglobalacceld thing already occurred with previous version of yakuake - without crash (see the second part of this comment). I just did not paid attention to it beforehand. It is most probably unrelated to the crash. Now, I installed the bug reporting tool drkonqi (via plasma-meta) and I set up my IceWM session to run kdeinit5 and kglobalaccel5 at startup.

New steps to reproduce and actual results (yakuake-3.0.2-2):
----
$ yakuake
KCrash: Application 'yakuake' crashing...
KCrash: Attempting to start /usr/lib/drkonqi from kdeinit
----

Here comes the requested backtrace:
----
(gdb) run
Starting program: /usr/bin/yakuake 
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/usr/lib/libthread_db.so.1".
[New Thread 0x7fffe4938700 (LWP 1042)]

Thread 1 "yakuake" received signal SIGSEGV, Segmentation fault.
0x00007ffff40bc550 in QKeySequence::operator=(QKeySequence const&) ()
   from /usr/lib/libQt5Gui.so.5
(gdb) backtrace 
#0  0x00007ffff40bc550 in QKeySequence::operator=(QKeySequence const&) ()
   from /usr/lib/libQt5Gui.so.5
#1  0x000000000043b0ee in ?? ()
#2  0x000000000043b621 in ?? ()
#3  0x0000000000419ca5 in ?? ()
#4  0x00007ffff3d8efd1 in QObject::event(QEvent*) () from /usr/lib/libQt5Core.so.5
#5  0x00007ffff4694d2b in QWidget::event(QEvent*) () from /usr/lib/libQt5Widgets.so.5
#6  0x00007ffff47ab06b in QMainWindow::event(QEvent*) ()
   from /usr/lib/libQt5Widgets.so.5
#7  0x00007ffff4651fcc in QApplicationPrivate::notify_helper(QObject*, QEvent*) ()
   from /usr/lib/libQt5Widgets.so.5
#8  0x00007ffff46574a6 in QApplication::notify(QObject*, QEvent*) ()
   from /usr/lib/libQt5Widgets.so.5
#9  0x00007ffff3d5f9ab in QCoreApplication::notifyInternal(QObject*, QEvent*) ()
   from /usr/lib/libQt5Core.so.5
#10 0x00007ffff3d61da6 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () from /usr/lib/libQt5Core.so.5
#11 0x00007ffff3db5f33 in ?? () from /usr/lib/libQt5Core.so.5
#12 0x00007fffef726d87 in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0
#13 0x00007fffef726fe0 in ?? () from /usr/lib/libglib-2.0.so.0
#14 0x00007fffef72708c in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0
#15 0x00007ffff3db633f in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQt5Core.so.5
#16 0x00007ffff3d5d37a in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) ()
   from /usr/lib/libQt5Core.so.5
#17 0x00007ffff3d6533c in QCoreApplication::exec() () from /usr/lib/libQt5Core.so.5
#18 0x0000000000415fb5 in ?? ()
#19 0x00007ffff33d6710 in __libc_start_main () from /usr/lib/libc.so.6
#20 0x0000000000416039 in _start ()
----


For the record, downgrading to yakuake-2.9.9-5, without kglobalaccel, there is no crash but it prints the following messages:
----
$ yakuake
QDBusConnection: session D-Bus connection created before QCoreApplication. Application may misbehave.
QDBusConnection: session D-Bus connection created before QCoreApplication. Application may misbehave.
yakuake(1415): Couldn't start kglobalaccel from kglobalaccel.desktop:  "Il est impossible de trouver le service « kglobalaccel.desktop »."
yakuake(1415) KGlobalAccelPrivate::getComponent: Failed to connect to the kglobalaccel daemon QDBusError("org.freedesktop.DBus.Error.NameHasNoOwner", "Could not get owner of name 'org.kde.kglobalaccel': no such name")
yakuake(1415)/kdecore (KLibrary) findLibraryInternal: plugins should not have a 'lib' prefix: "libkonsolepart.so"
yakuake(1415)/konsole Konsole::Session::run: Attempted to re-run an already running session.
----

Using kglobalaccel, yakuake 2.9.9 runs as well:
----
$ kglobalaccel5 
yakuake(1415) KGlobalAccelPrivate::_k_serviceOwnerChanged: detected kglobalaccel restarting, re-registering all shortcut keys
]$ yakuake
QDBusConnection: session D-Bus connection created before QCoreApplication. Application may misbehave.
QDBusConnection: session D-Bus connection created before QCoreApplication. Application may misbehave.
yakuake(2275)/kdecore (KLibrary) findLibraryInternal: plugins should not have a 'lib' prefix: "libkonsolepart.so"
yakuake(2275)/konsole Konsole::Session::run: Attempted to re-run an already running session. 
----
Comment 4 Eike Hein 2016-03-13 10:09:19 UTC
Please install more debug symbols (yakuake, kde frameworks 5, ...) and crash again, there's too many missing hops in the backtrace (the ??? lines) for me to see what's going on.
Comment 5 ybsar 2016-03-14 12:57:52 UTC
Created attachment 97891 [details]
backtrace with full debug symbols
Comment 6 ybsar 2016-03-17 08:47:21 UTC
Backtrace with full debug symbols now provided. I do not have the permission to confirm it, but other Archlinux users have the same crash with both 3.0.2 and Git (Frameworks 5) versions.
Comment 7 Olivier Churlaud 2016-06-08 18:58:27 UTC
I'm with archlinux as well, and I can't reproduce at all.
Yakuake never crashed and I use it a lot. I don't know how to help with that.
Comment 8 ybsar 2016-12-27 12:16:41 UTC
Did you use it without a full KDE installation?  Three other Arch users reported this issue as well.  It now works again on my system, but I can't tell really why. Latest crash occurred in September using the same version of Yakuake, thus it most probably was a dependency issue.