[Bug 181330] slow window, missing DBUS from remote KDE4 window
Manuel Amador (Rudd-O)
rudd-o at rudd-o.com
Tue Jul 14 23:50:24 BST 2009
https://bugs.kde.org/show_bug.cgi?id=181330
Manuel Amador (Rudd-O) <rudd-o at rudd-o.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |rudd-o at rudd-o.com
--- Comment #1 from Manuel Amador (Rudd-O) <rudd-o rudd-o com> 2009-07-15 00:50:22 ---
I have the EXACT same problem trying to run a KDE 4 app. I'm using KDE 4.2 in
Kubuntu on the machine where I run the app.
ssh -X machine
ksystemlog &
(bunch of brain farts from the application)
kdeinit4: preparing to launch /usr/lib/kde4/libexec/klauncher
kdeinit4: preparing to launch /usr/bin/kded4
KDE Daemon (kded) already running.
kdeinit4: preparing to launch /usr/bin/kbuildsycoca4
kbuildsycoca4 running...
ksystemlog(4764) KToolInvocation::klauncher: klauncher not running... launching
kdeinit
kdeinit4: Shutting down running client.
klauncher: Exiting on signal 15
kdeinit4: preparing to launch /usr/lib/kde4/libexec/klauncher
kdeinit4: preparing to launch /usr/bin/kded4
KDE Daemon (kded) already running.
kdeinit4: preparing to launch /usr/bin/kbuildsycoca4
kbuildsycoca4 running...
ksystemlog(4764): couldn't create slave: "No se puede dialogar con klauncher:
Not connected to D-Bus server"
ksystemlog(4764) KToolInvocation::klauncher: klauncher not running... launching
kdeinit
kdeinit4: Shutting down running client.
klauncher: Exiting on signal 15
kdeinit4: preparing to launch /usr/lib/kde4/libexec/klauncher
kdeinit4: preparing to launch /usr/bin/kded4
KDE Daemon (kded) already running.
kdeinit4: preparing to launch /usr/bin/kbuildsycoca4
kbuildsycoca4 running...
ksystemlog(4764) KToolInvocation::klauncher: klauncher not running... launching
kdeinit
kdeinit4: Shutting down running client.
klauncher: Exiting on signal 15
kdeinit4: preparing to launch /usr/lib/kde4/libexec/klauncher
kdeinit4: preparing to launch /usr/bin/kded4
KDE Daemon (kded) already running.
kdeinit4: preparing to launch /usr/bin/kbuildsycoca4
kbuildsycoca4 running...
ksystemlog(4764): couldn't create slave: "No se puede dialogar con klauncher:
Not connected to D-Bus server"
*poof* error.
The application itself does open (though it sends tens of megabytes of data
through the LAN, so it's UNUSABLE). HOWEVER, when any button or menu in the
application attempts to open a file open dialog box, the brain fart diarrhea
starts again on the console, and after 20 seconds I get an empty file open
dialog with a modal error box saying "Could not open slave -- Could not talk to
klauncher".
What happened to KDE? Doing this was a routine thing in KDE 3, guys.
Please confirm this bug, because it is still present today.
--
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
More information about the Unassigned-bugs
mailing list