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
Opened by ybsar (ybsar) - Friday, 04 March 2016, 09:36 GMT
Last edited by Antonio Rojas (arojas) - Saturday, 01 April 2017, 11:02 GMT
|
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 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
$ yaourt -Qi yakuake
Name : yakuake
Version : 3.0.2-2
info from KDE crash handler attached.
Thank you.
I attached my crash report as it contains a bit more information then the one before.
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.
----
yakuake-debug.install (0.2 KiB)
yakuake-debug.fullbacktrace.t... (4 KiB)
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
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.
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.