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.
…
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.
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?
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.
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).?
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.
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.
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.
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.
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.
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.
How do you think about to discuss a bit more the safe usage of different LCD monitors in parallel?
Would you like to point out any display manager adjustments so that the usually preferred monitor will also be “the primary device” for log-in dialogue displays (without temporarily unplugging HDMI cables)?
Will any special settings (like device priority) be needed for a corresponding X server configuration?
You should not “use also some software packages from the openSUSE Tumbleweed repository”!
Either you use Tumbleweed or not.
Installing just some packages from Tumbleweed can easily lead to problems or a broken system.
KScreen is for the user’s display configuration.
It has absolutely no effect for the Login screen.
You would have to change the X configuration, i.e. create an /etc/X11/xorg.conf or create/edit some files in /etc/X11/xorg.conf.d/.
But I have no idea how exactly, as I only have single monitor systems.
IIRC the nvidia driver has an explicit option for telling it which monitor to use, but I would have to search for that. Should be possible to find in the forum.
What card/driver are you using?
Now I am looking for a tool which supports the desired fine-tuning for the display manager in a convenient and safe way. How many tweaks would be valid for the file “/etc/X11/xorg.conf” nowadays?
What card/driver are you using?
My graphic card supports also the connection with two monitors in parallel. I would like to distinguish the primary and secondary device a bit better for the display manager.
If /etc/X11/xorg.conf exists it will be used. If not, the snippets in /etc/X11/xorg.conf.d/ will be used (which is actually just xorg.conf split up in separate files).
Things that are not configured, are tried to be determined automatically.
My graphic card supports also the connection with two monitors in parallel. I would like to distinguish the primary and secondary device a bit better for the display manager.
I do not care how many monitors your card supports.
I wanted to know which card and which driver you use.
Ok then, but it was my strong impression. You took the trouble to quote my text. Thus I assumed that what followed is a comment, an answer or an addition to what I posted. Isn’t that why those quotations are for. Exactly as you use them in your last post?
It is clear to me now. Thanks for the explanation.
