Bug 5298

Summary:	no graphical desktop on lenovo x61s after cauldron install (network)
Product:	Mageia	Reporter:	Herbert Poetzl <herbert>
Component:	RPM Packages	Assignee:	Mageia Bug Squad <bugsquad>
Status:	RESOLVED DUPLICATE	QA Contact:
Severity:	major
Priority:	Normal	CC:	herbert, mageia
Version:	Cauldron
Target Milestone:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Source RPM:		CVE:
Status comment:
Attachments:	/root/drakx/report.bug.gz

Description Herbert Poetzl 2012-04-09 03:37:09 CEST

Description of problem:
after successfully installing Cauldron (labeled mageia2b3) on an x61s lenovo, no graphical desktop is started.

# systemctl restart dm.service
# systemctl status dm.service
prefdm.service - Display Manager
	  Loaded: loaded (/lib/systemd/system/prefdm.service; static)
	  Active: inactive (dead) since Sun, 08 Apr 2012 21:32:29 -0400; 2s ago
	 Process: 3200 ExecStart=/etc/X11/prefdm -nodaemon (code=exited, status=0/SUCCESS)
	  CGroup: name=systemd:/system/prefdm.service


running /etc/X11/prefdm starts up an X-Window login prompt


Version-Release number of selected component (if applicable):
systemd-44-7.mga2

How reproducible:
tried twice, happened each time

Steps to Reproduce:
1. install selecting gnome desktop
2. reboot 1,2,3 times, always the same
3.

Comment 1 Herbert Poetzl 2012-04-09 03:39:41 CEST

Created attachment 1954 [details]
/root/drakx/report.bug.gz

Comment 2 Manuel Hiebel 2012-04-09 09:58:52 CEST

since colin is already on it I close as duplicate if you are agree

*** This bug has been marked as a duplicate of bug 5262 ***

Status: NEW => RESOLVED
Resolution: (none) => DUPLICATE

Comment 3 Colin Guthrie 2012-04-09 12:14:05 CEST

Just to confirm this is the same bug, can you do a "systemctl status dm.service" before trying to restart it?

If it is dead and has never been started, and there are no more jobs in the queue (systemctl list-jobs) and you are on graphical.target (systemctl is-active graphical.target), can you then boot with: "systemd.log_level=debug systemd.log_target=kmsg" on the kernel command line, then attach the /var/log/dmesg file to bug #5262. Please also attach output from "systemctl dump" too.

I mention it here on this bug just in case it's not the same problem, but please attach to the new bug if it is the same problem!

CC: (none) => mageia

Comment 4 Herbert Poetzl 2012-04-09 14:22:58 CEST

> Just to confirm this is the same bug, can you do a "systemctl status
> dm.service" before trying to restart it?

I did yesterday, and it showed almost the same as after the restart, so I didn't bother to add it.

I tried to recreate the issue today, but the install worked fine and the graphical desktop is started (although with the same issues as reported in Bug 5299)

CC: (none) => herbert

Comment 5 Colin Guthrie 2012-04-09 15:08:46 CEST

Almost the same is not the same as the same :p

The problem seems to depend very much on package selection, so it can creep in based on what is installed. If you do manage to reproduce it, please do grab the output requested.

I may as well leave this as a dupe until further notice.