You have been subscribed to a public bug:
launching juk and amarok from xterm window always works. It does not work with
updated kubuntu in a konsole window.
Launching this programs from kde4-kmenu in kubuntu also works. I suspect dbus
problems:
konsole sets some dbus variables:
j...@jfh00:~$ env|grep -i dbus
KONSOLE_DBUS_SERVICE=:1.124
KONSOLE_DBUS_SESSION=/Sessions/1
DBUS_SESSION_BUS_ADDRESS=unix:abstract=/tmp/dbus-yQc77X8gU8,guid=0142e4eaab749be25cb83e494912baf7
j...@jfh00:~$
xterm does not:
j...@jfh00:~$ env |grep -ni dbus
35:DBUS_SESSION_BUS_ADDRESS=unix:abstract=/tmp/dbus-yQc77X8gU8,guid=0142e4eaab749be25cb83e494912baf7
Here is what happens with juk and amarok on konsole:
j...@jfh00:~$ juk
juk(9899): Communication problem with "juk" , it probably crashed.
Error message was: "org.freedesktop.DBus.Error.NoReply" : " "Message did not
receive a reply (timeout by message bus)" "
j...@jfh00:~$ KCrash: Application 'juk' crashing...
sock_file=/home/jfh/.kde/socket-jfh00/kdeinit4__0
amarok
amarok: BEGIN: App::App()
amarok: BEGIN: void App::continueInit()
amarok: BEGIN: EngineController::EngineController()
<unknown program name>(9907)/: Communication problem with "amarok" , it
probably crashed.
Error message was: "org.freedesktop.DBus.Error.NoReply" : " "Message did not
receive a reply (timeout by message bus)" "
j...@jfh00:~$ KCrash: Application 'amarok' crashing...
sock_file=/home/jfh/.kde/socket-jfh00/kdeinit4__0
** Affects: kdebase (Ubuntu)
Importance: Undecided
Status: New
--
launching juk and amarok in konsole vs. xterm
https://bugs.edge.launchpad.net/bugs/294616
You received this bug notification because you are a member of Kubuntu Bugs,
which is subscribed to kdebase in ubuntu.
--
kubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
