[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

Re: F10: could not start ksmserver



2009/2/28 Tarjei Knapstad <tarjei knapstad gmail com>:
> 2009/2/28 Tarjei Knapstad <tarjei knapstad gmail com>:
>> A recent update seems to have botched KDE somehow. When I log in I get
>> an xmessage stating "Could not start ksmserver. Check your
>> installation."
>> If I click OK the window manager dies, but if I just let it sit there
>> I can use my desktop just fine...
>>
>> This started showing today, apparently after last nights updates.
>> These updates included:
>>
>> gdm-user-switch-applet-2.24.1-4.fc10      Fri 27 Feb 2009 22:50:23 CET
>> xorg-x11-drv-evdev-2.1.3-1.fc10                Fri 27 Feb 2009 22:50:22 CET
>> libpng-devel-1.2.35-1.fc10                           Fri 27 Feb 2009
>> 22:50:22 CET
>> pygtk2-libglade-2.13.0-3.fc10                     Fri 27 Feb 2009 22:50:21 CET
>> setup-2.7.4-4.fc10                                        Fri 27 Feb
>> 2009 22:50:20 CET
>> pygtk2-devel-2.13.0-3.fc10                         Fri 27 Feb 2009 22:50:18 CET
>> pygtk2-codegen-2.13.0-3.fc10                   Fri 27 Feb 2009 22:50:17 CET
>> pygtk2-doc-2.13.0-3.fc10                            Fri 27 Feb 2009 22:50:10 CET
>> ntfs-3g-2009.2.1-2.fc10                               Fri 27 Feb 2009
>> 22:50:07 CET
>> libmusicbrainz3-3.0.2-4.fc10                       Fri 27 Feb 2009 22:50:05 CET
>> pygtk2-2.13.0-3.fc10                                   Fri 27 Feb 2009
>> 22:49:59 CET
>> gdm-2.24.1-4.fc10                                      Fri 27 Feb 2009
>> 22:49:19 CET
>> libpng-1.2.35-1.fc10                                    Fri 27 Feb
>> 2009 22:49:04 CET
>>
>> After googling the issue I found a suggestion saying that I should
>> check the perms on my . files in $HOME. Everything seems OK here.
>>
>
> Some additional info: If I try to run ksmserver manually from a shell
> I get this:
>
> Could not register with D-BUS. Aborting.
>
> I have dbus-1.2.4-2.fc10.i386
>

And now it's starting to get really weird. If I restart the X server,
then change to a console (ctrl-alt-f2) and log in and back out again
before logging into X everything's fine... How is that possible..?
(I've repoduced this 4 times just to be sure. Restarting X and logging
back in results in the error message. If I log in and back out from a
console first everything's fine...)

--
Tarjei


[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]