Page 1 of 3 123 LastLast
Results 1 to 10 of 22

Thread: Do D-Bus difficulties prevent KDE login?

  1. #1

    Question Do D-Bus difficulties prevent KDE login?

    I worked with the software "KDE SC 4.12.5" for a while. I dared to apply a few package updates. Unfortunately, I could not log into another KDE desktop session any more suddenly. I guess that this surprise comes from error messages like the following.
    Code:
    …
    klauncher(…) kdemain: No DBUS session-bus found. Check if you have started the DBUS server.
    kdeinit4: Communication error with launcher. Exiting!
    kdmgreet(…)/kdecore (K*TimeZone*): KSystemTimeZones: ktimezoned initialize() D-Bus call failed:  "Not connected to D-Bus server"
    …
    It seems that I can not fix such an annoyance by an update to the software "KDE SC 4.13.2" from the Tumbleweed repository so far. I would appreciate your advices.

  2. #2

    Default Re: Do D-Bus difficulties prevent KDE login?

    Quote Originally Posted by elfring View Post
    I worked with the software "KDE SC 4.12.5" for a while. I dared to apply a few package updates. Unfortunately, I could not log into another KDE desktop session any more suddenly. I guess that this surprise comes from error messages like the following.
    Code:
    …
    klauncher(…) kdemain: No DBUS session-bus found. Check if you have started the DBUS server.
    kdeinit4: Communication error with launcher. Exiting!
    kdmgreet(…)/kdecore (K*TimeZone*): KSystemTimeZones: ktimezoned initialize() D-Bus call failed:  "Not connected to D-Bus server"
    …
    Yes, KDE makes heavy use of D-BUS, so difficulties with it could cause all sort of problems.

    But those "error" messages you post are normal.
    They come from KDM, I have them in kdm.log as well without having any problems.

    It seems that I can not fix such an annoyance by an update to the software "KDE SC 4.13.2" from the Tumbleweed repository so far. I would appreciate your advices.
    Why "from the Tumbleweed repository"? Are you actually using Tumbleweed? Then you are in the wrong sub-forum. Please request the thread to be moved to the Tumbleweed forum (click on the triangle below a post, "Report post").

    How exactly did you upgrade to KDE 4.13?
    What is your repo list?
    Code:
    zypper lr -d
    Can you login to another session? (click at the wrench icon on the login screen to choose one)
    Run "startkde" there and post the output.
    Last edited by wolfi323; 08-Jul-2014 at 07:49.

  3. #3
    Join Date
    Jun 2008
    Location
    Netherlands
    Posts
    24,732

    Default Re: Do D-Bus difficulties prevent KDE login?

    You fail to tell which version of openSUSE you use. But when it is Tumbleweed, you are at the wrong forum. There is a Tumbleweed forum where the other Tumblewed users gather and maybe can help you.

    Do you want me to move this to the Tumbleweed forums (please we do not like double posting, so do not start a new thread with the same problem there).?
    Last edited by hcvv; 08-Jul-2014 at 08:02.
    Henk van Velden

  4. #4

    Question Re: Do D-Bus difficulties prevent KDE login?

    I worked with the software "KDE 4.12.5" on my openSUSE Tumbleweed/13.1 system for a while before I stumbled on a KDM log-in hiccup. (The background picture is displayed as usual. The mouse pointer is displayed after a short delay. But the expected graphical log-in dialogue does not appear.)

    The clarification for my open issue can also be continued in a corresponding Tumbleweed forum.

  5. #5
    Join Date
    Jun 2008
    Location
    Netherlands
    Posts
    24,732

    Default Re: Do D-Bus difficulties prevent KDE login?

    Sorry, I do not understand. Is this a request to move this thread to the Tumbleweed forum or not?
    A simple question IMHO, where a simple answer can be given.
    Henk van Velden

  6. #6

    Default Re: Do D-Bus difficulties prevent KDE login?

    Quote Originally Posted by hcvv View Post
    Sorry, I do not understand.
    I do not really request a move for this discussion thread because it affects more than openSUSE Tumbleweed systems. But I'm still fine if you find an other forum more appropriate.

  7. #7

    Default Re: Do D-Bus difficulties prevent KDE login?

    Quote Originally Posted by elfring View Post
    I do not really request a move for this discussion thread because it affects more than openSUSE Tumbleweed systems.
    Well, apparently it only affects _your_ system(s).
    KDM 4.11.10 (from KDE 4.13.2) works fine here, but I have it from KDE:Current, not Tumbleweed.

    So is this Tumbleweed now or not?
    Or do you have the problem on more than 1 system?

    If it is Tumbleweed, be sure that you use "zypper dup" for updating.

    Do I understand you correctly that you don't get a login screen at all?
    Is there something else in kdm.log that might be interesting?
    As I said, those lines you posted are harmless.

    And /var/log/Xorg.0.log might help as well, and please post the repo list as already requested.

    Can you login to KDE when using a different Login manager? You can set one in /etc/sysconfig/displaymanager, try "xdm" that should be installed in any case.

  8. #8

    Default Re: Do D-Bus difficulties prevent KDE login?

    Oh, and try booting to recovery mode ("Advanced Options" in the boot menu) as well.
    Maybe it's actually a graphics driver issue.
    But I guess you wouldn't see the background picture and mouse cursor in that case.
    Last edited by wolfi323; 08-Jul-2014 at 13:40.

  9. #9

    Question Re: Graphical log-in flaws?

    Quote Originally Posted by wolfi323 View Post
    So is this Tumbleweed now or not?
    My system uses also some software packages from the openSUSE Tumbleweed repository.

    Do I understand you correctly that you don't get a login screen at all?
    Log-ins work as usual in text consoles (VT 1 - 6).

    Is there something else in kdm.log that might be interesting?
    I do not see any other questionable messages there.

    Can you login to KDE when using a different Login manager?
    Unfortunately, no.

    Following display managers do not show a log-in dialogue on my system at the moment.
    • gdm
    • kdm
    • lxdm
    • xdm


    I am curious when I can get them to work again here.

  10. #10

    Lightbulb Re: Confusion because of switching between primary and secondary monitors?

    Quote Originally Posted by wolfi323 View Post
    What is your repo list?
    I discovered in the meantime that these repositories are not really interesting for my use case. I have determined that another technical detail is more important here.

    I tried out a secondary monitor for a few days. This display device was detected by the EDID from a HDMI connection even if it was switched off (no power). The graphical log-in dialogue was displayed there after I activated in an appropriate way.
    The log-in dialogue does not appear on the display device which I treated as my primary monitor before. I can restore the display situation I was used too if I unplug the involved HDMI cable (temporarily).

    I am sorry that I introduced a bit of confusion for the clarification of the handling with multiple LCD monitors.

Page 1 of 3 123 LastLast

Tags for this Thread

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •