After fresh install, kdm don't start. I'm waiting after boot. If I go in tty7 I have a message from dbus see bug 197. For start it, I go in tty 2, loggin in root, make: telinit 3 telinit 5 and kdm start. Reproducible: Steps to Reproduce:
Created attachment 47 [details] kdm.log
can you provide the logs of xorg ?
CC: (none) => dmorganec
Created attachment 86 [details] Xorg
Attachment 86 mime type: text/x-log => text/plain
Could you try tty8?
Black screen on tty8 Stef.
CC: (none) => thierry.vignaudAssignee: bugsquad => balcaen.john
Source RPM: (none) => kdm
Could you still reproduce it ?
Every boot, I need to connect to the TTY and after need to do telinit 5 Stef.
Attachment 47 mime type: text/x-log => text/plain
Please try disabling speedboot, by booting with 'speedboot=no'.
Keywords: (none) => NEEDINFO
same issu, need to do telinit 5.
Can you watch the boot messages? does messagebus service get started correctly?
X don't start and I have no information in log ( or I don't find it). I don't know if it's the same problem: https://bugs.mageia.org/show_bug.cgi?id=197 Stef.
You don't have a /var/log/kdm.log ?
instead of doing telinit 5, can you try to startkde from root and see if it starts? If so, then logout it's not safe staying as root :)
CC: (none) => anaselli
I start with the option speedboot=no and nopinit I have at the and only a black screen on all ( tty1 ->8). See the kdm.log Stef.
Created attachment 296 [details] kdm.log
Created attachment 297 [details] Xorg.0.log
If I start without option and at the end do startkde: $Display is not set or cannot connect to the X server. Stef.
(In reply to comment #10) > Can you watch the boot messages? does messagebus service get started correctly? After you boot, go to VT1 (Alt+Ctrl+F1) and as root: service dm status service messagebus status then post the output here.
service dm status Loaded: loaded (/lib/system/dm.service) active: inactive (dead) Cgroup: name=systemd: /system/dm.service service messagebus status Loaded: loaded (/etc/rc.d/init.d/messagebus) Active: active (running) Process:1783 Main Pid: 2150 Stef.
So you're using systemd instead of initscripts and everything break havoc... You should have told us about this There's a reason we still default to initscrits you know...
Priority: Normal => LowSummary: KDM don't start => KDM don't start with systemd
Summary: KDM don't start with systemd => KDM doesn't start with systemd
Created attachment 345 [details] service messagebus status I installed systemd-sysvinit but i'm still not able to reproduce your problem. Also it seems my ouput is quite different from yours cf my file for for messagebus. You don't have any error when systemd is starting ? (start without plymouth for example)
Severity: normal => minor
I'm installing the beta 2 today. I don't arrive to reproduce it. For me it solved. Stef.
Status: NEW => RESOLVEDResolution: (none) => FIXED