Bug 5159 - prefdm.service error when installed without X
Summary: prefdm.service error when installed without X
Status: RESOLVED FIXED
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: Cauldron
Hardware: x86_64 Linux
Priority: Normal major
Target Milestone: ---
Assignee: Mageia Bug Squad
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: 2120 5184
  Show dependency treegraph
 
Reported: 2012-03-29 14:00 CEST by Kamil Rytarowski
Modified: 2012-04-02 02:10 CEST (History)
2 users (show)

See Also:
Source RPM: systemd
CVE:
Status comment:


Attachments
halt time errors - low quality (593.59 KB, image/jpeg)
2012-03-29 14:06 CEST, Kamil Rytarowski
Details

Description Kamil Rytarowski 2012-03-29 14:00:57 CEST
Description of problem:
Hi!

I'm doing minimal installation (without X Window), and I got double prefdm errors:
1) the first one is at boot time
2) the latter is at halt time

How reproducible:


Steps to Reproduce:
1. network installation (nonfree iso)
2. minimal installation without X
3. see prefdm errors at boot time
4. see prefdm error at halt time
Comment 1 Kamil Rytarowski 2012-03-29 14:03:04 CEST
https://bugs.mageia.org/attachment.cgi?id=1883 boot time errors
Comment 2 Kamil Rytarowski 2012-03-29 14:06:33 CEST
Created attachment 1884 [details]
halt time errors - low quality
Manuel Hiebel 2012-03-29 15:08:03 CEST

CC: (none) => mageia
Blocks: (none) => 2120
Source RPM: (none) => systemd

Comment 3 Kamil Rytarowski 2012-03-30 14:08:12 CEST
The problem with halting is not related to prefdm, but LVM.
/dev/dm-X are my partitions.
Kamil Rytarowski 2012-04-01 22:34:01 CEST

Blocks: (none) => 5184

Comment 4 Colin Guthrie 2012-04-02 00:35:22 CEST
OK, so this isn't an error per-se. The real error is detecting what the default runlevel should be which is really a problem in the installer.

If you don't install X, prefdm should start, fail and then run a failure unit which displays a message about why it failed and then (when you hit a key) switch from graphical.target to multi-user.target (the equiv of switching from runlevel 5 to 3).

The network-up thing should be debugged to work out why it's taking so long (it will need someone suffering from this problem to hack the network-up script to debug it a bit...)

The microcode issue is covered in another bug #4327

The LVM should be shutdown nicely on reboot.. Not sure why it's not :s Does regenerating the initrd help here? The installer will generate a big, generic initrd whereas if run later it will create a lean, hostonly initrd. If possible keep a backup of the big initrd to test again later :)
Comment 5 Kamil Rytarowski 2012-04-02 01:19:11 CEST
(In reply to comment #4)
> The LVM should be shutdown nicely on reboot.. Not sure why it's not :s
Blind guess - encrypted LVM partition?

> Does
> regenerating the initrd help here?

No. I have installed additionally radeon-firmware (it's regenerating initrd), and the problem is still there.
Comment 6 Kamil Rytarowski 2012-04-02 01:22:13 CEST
(In reply to comment #5)
> (In reply to comment #4)
> > The LVM should be shutdown nicely on reboot.. Not sure why it's not :s
> Blind guess - encrypted LVM partition?
> 
And it's trying to umount dm-0 three times... and I can see that there is:
dm-1 /
(dm-2 swap?)
dm-3 /home
Comment 7 Colin Guthrie 2012-04-02 01:24:49 CEST
Ahh it's encrypted? Interesting. Oh right, I didn't see the clone path on this bug :)

Yeah so I'm not sure this particular bug is still needed (as the other issues aside form the LVM are covered elsewhere)

If you agree, please close this one at leisure and we can look into the encrypted problem on #5184

FWIW, it will try and unmount in a loop until nothing can be changed and no more unmounts are possible, but lets keep the comments on the other bug specifically for this.
Comment 8 Dave Hodgins 2012-04-02 01:52:48 CEST
The dm-0 would be the partition that contains the lvm physical volume.

My wag is that a lvm vgchange -a n command is being executed before
the cryptsetup luksClose, so it fails as the device is busy.

CC: (none) => davidwhodgins

Comment 9 Dave Hodgins 2012-04-02 01:54:24 CEST
Keep in mind lvm physical volumes can be on an encrypted partition,
or encrypted partitions can be on lvm (or both).
Comment 10 Kamil Rytarowski 2012-04-02 02:10:06 CEST
Closing for the prefdm part.

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


Note You need to log in before you can comment on or make changes to this bug.