FS#48447 - [yakuake] does not run anymore since 3.0.2-1 upgrade

Attached to Project: Community Packages
Opened by ybsar (ybsar) - Friday, 04 March 2016, 09:36 GMT
Last edited by Antonio Rojas (arojas) - Saturday, 01 April 2017, 11:02 GMT
Task Type Bug Report
Category Packages
Status Closed
Assigned To Felix Yan (felixonmars)
Architecture All
Severity High
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 2
Private No

Details

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 (thus it is not related to  FS#48444 )

Steps to reproduce:
$ 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)

Core file is 19M, cannot attach here.
This task depends upon

Closed by  Antonio Rojas (arojas)
Saturday, 01 April 2017, 11:02 GMT
Reason for closing:  Fixed
Comment by ybsar (ybsar) - Friday, 04 March 2016, 10:00 GMT Comment by Felix Yan (felixonmars) - Friday, 04 March 2016, 14:23 GMT
Please try again with yakuake 3.0.2-2
Comment by John Piel (uberGeek) - Friday, 04 March 2016, 17:24 GMT
Still get segfault with
$ yaourt -Qi yakuake
Name : yakuake
Version : 3.0.2-2
info from KDE crash handler attached.
Thank you.
Comment by ybsar (ybsar) - Saturday, 05 March 2016, 13:47 GMT
Still crashing. Additional info: I am using IceWM as a window manager, no other KDE/Qt application.
Comment by Dezso Janos (rebegin) - Wednesday, 09 March 2016, 08:46 GMT
3.0.2-2 is also crashing here (note: tried yakuake-git and that's also).
I attached my crash report as it contains a bit more information then the one before.
Comment by ybsar (ybsar) - Sunday, 13 March 2016, 10:16 GMT
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 package) 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
----
The backtrace is attached as a file.


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 by ybsar (ybsar) - Thursday, 17 March 2016, 08:43 GMT
After installing kde-base-debug from the qt-debug unofficial repository and installing yakuake-debug from the attached PKGBUILD and yakuake-debug.install files, I obtain the attached backtrace with full debug symbols.
Comment by dannyzen (dannyzen) - Tuesday, 31 May 2016, 02:00 GMT
I also experienced this bug and have reverted back to yakuake-2.9.9-5 in the interim.
Comment by Olivier (ochurlaud) - Monday, 27 June 2016, 08:12 GMT
I tried to reproduce, without success. I'm using Yakuake extensively everyday though.

Could you give the set of options you use? Plus the exact thing you do when the bug is triggered?
Do you have everything date?

Thx
Comment by t0rb3n (t0rb3n) - Tuesday, 27 September 2016, 13:34 GMT
For me, this resolved magically today. I had IgnorePkg'ed yakuake since 2.9.9 due to this bug (host 1). New installation (host 2)---same segfault. Just to reproduce this behaviour, I upgraded host 1 (yakuake 2.9.9->3.0.2-3) and it just worked again. For host 2, I installed extra/konsolepart4, yakuake got running, and I removed konsolepart4 again, yakuake surviving. I hope for everyone with this issue the same bad reproducibility (-:
Comment by t0rb3n (t0rb3n) - Sunday, 02 October 2016, 14:36 GMT
(host 3): Crash report

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.Spawn.ChildSignaled", "Process org.kde.kglobalaccel received signal 6")
Reusing existing ksycoca
Recreating ksycoca file ("$HOME/.cache/ksycoca5_de_oSd7B5HnpSGdlGIGjDS6vaTPBZo=", version 303)
Still in the time dict (i.e. deleted files) ("apps")
Menu "applications-kmenuedit.menu" not found.
Saving
Attempted to re-run an already running session.
Speicherzugriffsfehler (Speicherabzug geschrieben)

persuaded me to install kmenuedit, hence essentially a full KDE destop (though I don't need it): and the segfault vanished. Sounds like unmet dependencies on some KDE-internal library, which isn't covered by the package.
Comment by ybsar (ybsar) - Tuesday, 27 December 2016, 11:56 GMT
It now works flawlessly using a fresh user profile after running kglobalaccel5.
Latest crash occurred in September, thus yakuake-3.0.2-3 did not fix it, it was a dependency issue.
Either (most probably) kglobalaccel updates solved it or some other package installation incidentally fixed it.

Loading...