« Return to Thread: [Cooker] KDE4 wont start after last nights install

Re: [Cooker] KDE4 wont start after last nights install

by Steve Morris-5 :: Rate this Message:

Fabrice Facorat wrote:

> 2008/5/15 Steve Morris <samorris@...>:
>
>> Having finished installing what appears to be all the associated kde4
>> packages, when I now attempt to start kde4 from kdm4, the kde startup cycle
>> through all the splash screen animations and then drops back to kdm4. I have
>> looked in syslog and there are no kde messages whatsoever. How do I debug
>> this issue. Also the kdm4 theme I was using before the migration, has been
>> replaced since the migration process, why?
>>
>
> kill remaining kded4 and gam_server process.
> Should be fixed shortly by uptream. maybe in 4.0.74
>
>

Fabrice, my problem is slightly different from other peoples kde4

reported issues. I am not trying to restart kde4, I am trying to start
kde4 for the first time in a session after a cold boot. I have had to
boot into kde3 to check things, and found that yes gam_server exists but
cannot be killed and kded4 does not exist, but kde4 will still not
start. I thought that the migration was moving kde4 away from the
/opt/kde4 structure, but I am still seeing lots of applications within
this structure. BTW as of last night I think I am running 4.0.74 of kde4
which hasn't resolved anything.
I have tried to start krusader in root mode (I thought this was
kde3/kde4 independent, but looking at the file contents it is obviously
not) under kde3 and it failed to run, producing error messages which may
go a long way towards explaining why kde4 won't run. These messages are
as follows:

Cannot connect to the D-BUS session bus.
To start it, run:
eval `dbus-launch --auto-syntax`
DBus Error: org.freedesktop.DBus.Error.Disconnected, Not connected to
D-BUS server
krusader(11439) KToolInvocation::klauncher: klauncher not running...
launching kdeinit
Link points to "/tmp/ksocket-root"
Error: "/root/.kde4/socket-development.geelong.highton.org.au" points to
"/tmp/ksocket-root" instead of "/root/tmp/ksocket-root".
Creating link /root/.kde4/socket-development.geelong.highton.org.au.
Created link from
"/root/.kde4/socket-development.geelong.highton.org.au" to
"/root/tmp/ksocket-root"
kdeinit4: preparing to launch /usr/lib/kde4/libexec/klauncher
kdeinit4: Launched KLauncher, pid = 11445 result = 0
klauncher(11445) kdemain: No DBUS session-bus found. Check if you have
started the DBUS server.
kdeinit4: Communication error with launcher. Exiting!
krusader(11439): Couldn't start knotify from knotify4.desktop:
"KLauncher could not be reached via D-Bus. Error when calling
start_service_by_desktop_path:
empty
"

krusader(11439) KNotification::~KNotification: 0
krusader(11439) UserAction::UserAction: Initialisising useractions...
krusader(11439) UserAction::UserAction: 10 useractions read.
krusader(11439)/kio (KSycoca) KSycocaPrivate::openDatabase: Trying to
open ksycoca from "/var/tmp/kdecache-root/ksycoca4"
krusader(11439)/kio (KSycoca) KSycocaPrivate::openDatabase: Could not
open ksycoca
krusader(11439)/kio (KSycoca) KSycocaPrivate::openDatabase: Trying to
open ksycoca from "/var/tmp/kdecache-root/ksycoca4"
krusader(11439)/kio (KSycoca) KSycocaPrivate::openDatabase: Could not
open ksycoca
krusader(11439)/kio (KSycoca) KSycocaPrivate::checkDatabase: We have no
database.... launching kdeinit
krusader(11439) KToolInvocation::klauncher: klauncher not running...
launching kdeinit
kdeinit4: preparing to launch /usr/lib/kde4/libexec/klauncher
kdeinit4: Launched KLauncher, pid = 11528 result = 0
klauncher(11528) kdemain: No DBUS session-bus found. Check if you have
started the DBUS server.
kdeinit4: Communication error with launcher. Exiting!

regards,
Steve

>
>

[samorris.vcf]

begin:vcard fn:Steve Morris n:Morris;Steve email;internet:samorris@... x-mozilla-html:TRUE version:2.1 end:vcard

« Return to Thread: [Cooker] KDE4 wont start after last nights install