13.1 xfce fails to display GUI login

English Install/Boot/Login
1

Thinkpad R60e
Intstalled 13.1 xfce yesterday keeping only /home which was from 13.3. All OK. Did not do liveupdate at the time.
Only change I made to system was to add ‘echo disable > /proc/acpi/ibm/bluetooth’ into /etc/init.d/boot.local
Restarted at least once during the day.

This morning it fails to display the graphical login screen.
On the screen 3 lines
Started LSB:X Display Manager
Started Authorisation Manager
Started Modem Manager

On the ctrl-alt-F10 display the last line seems to be an error related to killproc:
killproc: Usage:#102 …

I can log in at a console and have run yast and run live update.

In /var/log/messages I see
systemd[1160]: Failed to open private bus connection: Failed to connect to socket /run/user/0/dbus/user_bus_socket: No such file or directory

Can’t see any errors in Xorg.0.log

I see the other thread ‘gdm is broke’ so this might be related.

2

On 2013-11-21 10:36, daveroyal wrote:
> I see the other thread ‘gdm is broke’ so this might be related.

Are you using gdm? The default for xfce is lightdm

–
Cheers / Saludos,

Carlos E. R.
(from 12.3 x86_64 “Dartmouth” at Telcontar)

3

OP here

This is intermittent and variable in behaviour.

I restarted for the nth time and got the login manager!
I entered the password and … got the login manager again.
I entered the password again and got my desktop, Looked OK.

At this point I looked in the same logs. That killproc error was absent.

The ‘systemd[1160]: Failed to open private bus connection’ was still there (or something v similar - I didn’t examine it carefully)

Rebooted.
Failed again. But differently, on the screen:
Starting SUSEfirewall2 phase …
Starting network manager …

And on the ctrl-alt-F10 display the last line is again
killproc: killproc:Usage:#102 killproc -v] …

Restarted again - slightly different again, ended with
[OK] Started login service
[OK] Started Modem Manager

and the killproc error is there

4

I’m using whatever is the default. So probably not then. Sorry.

5

On 2013-11-21 11:16, daveroyal wrote:
> and the killproc error is there

check syslog to find it in detail, please.

–
Cheers / Saludos,

Carlos E. R.
(from 12.3 x86_64 “Dartmouth” at Telcontar)

6

Encountering the same problem with standard installation of Xfce. Ofc using LightDM.
Will provide logs as soon I have the time for it

7

/var/log/messages:
https://db.tt/KKPiYOXP

8

messages log
message.log - Pastebin.com

boot log
boot.log - Pastebin.com

9

DId you check the download, i.e. check md5sum? Or use the Media Check from the installer?

10

Checked MD5 of d/l and burner checked it before and after burning DVD*

11

checked mine also, everything is ok.

Did a LXDE install in the meantime and everything works. Not what I want though :wink:

12

Some other people had problems with lxdm as well.
Try changing to some other display manager in /etc/sysconfig/displaymanager (xdm should work).

Could be graphics driver related as well.
The shipped intel driver is known to be buggy and causes crashes.
Try the newer one from here (will be released as online update soon):
Index of /repositories/home:/sumski:/bnc847762/openSUSE_13.1

13

Yes, xdm works.
It leaves a little xconsole window open with an error message:
goa[2162]: Error preparing AM: The name org.Freedesktop.Telepathy.AccountManager was not provided by any .service files goa…
It that unexpected?

Any nicer-looking desktop managers I can try?

14

No idea.
But that doesn’t sound critical (especially if you don’t use Telepathy).

Any nicer-looking desktop managers I can try?

Well, there’s kdm, gdm, lxdm that should be included in the distro, and sddm (and likely others) on OBS.
The question is if they are working, or fail just like lightdm.

Did you try to update the intel driver?

15

Installed xf86-video-intel-2.99.906-4.1.i586 (was 2.99.905…)
Reverted to lightdm in /etc/sysconfig/displaymanager
Original problem back
Slightly different stuff on the screen - now ends with Starting Getty on tty1…

16

lxdm works.

17

If it’s a driver problem, I don’t get it why the initial boot(right after installation) works fine or why it works if I use startx trough console as root. LightDM works under this conditions fine.
Sounds more like a authorization problem

18

No. If you run “startx” you don’t use LightDM. Xfce is then started directly.

And the driver problem was just a suspicion.

So apparently only LightDM has a problem on your systems. Possibly related to the error message daveroyal posted in the first post:

systemd[1160]: Failed to open private bus connection: Failed to connect to socket /run/user/0/dbus/user_bus_socket: No such file or directory

(You didn’t mention if you have this as well, and you also didn’t say if another DM works for you)
No idea how to debug this, though. I don’t have any /run/user/xxx/dbus/ folders on my system at all (I’m using KDE and kdm though).
But I can install LightDM later on, to see if it works on my system.

Maybe one if you would want to file a bug report at http://bugzilla.novell.com/ ? (same username/password as here)

19

Yes ofc startx was a mistake on my side.

As stated before I did a LXDE standard install which works fine with LXDM.

And you can clearly see in the logs I provided that I have a similiar/same error

 Failed to open private bus connection: Failed to connect to socket /run/user/1000/dbus/user_bus_socket: No such file or directory

Sry if this sounds a bit arrogant really not my intention. :slight_smile:

Will try a minimal desktop install and add LightDM and Xfce manual later if I have the time.

20

There are several open bugs in 13.1 mentioning lightdm:
https://bugzilla.novell.com/buglist.cgi?query_format=specific&order=relevance+desc&bug_status=__open__&product=openSUSE+13.1&content=lightdm

I’ll raise a new one once I’ve found my way around there, and if I think this is new.