and it does not happen in r5 ?

Don't know, system no longer is a pristine install. I have been removing packages for testing my normal install.

I can no longer boot runlevel3 with space 3 in gub with default runlevel5 set for systemd boot.  :(

I get:

 Starting /localfailed, see 'systemctl status local.mount/
' for details.
Starting Relabel all filesystems, if necessary aborted because a dependency failed.
Starting Setup link in /boot for running kernel aborted because a dependency failed.
Welcome to emergency mode.

Setting systemd runlevel default to 3 lets me boot without the emergency mode prompt.

It does.

Dec  7 16:29:09 hodgins upowerd[1714]: UPower-Linux-WARNING **: failed to open /etc/crypttab: Failed to open file '/etc/crypttab': No such file or directory

It's a warning only, but it adds clutter to syslog, and the display when
booting without the splash parameter.

Seems this is coming from /usr/lib/upowerd

CC: (none) => davidwhodgins

(In reply to comment #3)

> 
> It's a warning only, but it adds clutter to syslog, and the display when
> booting without the splash parameter.

If the application does not care, why not have the post rpm install do a
 touch /etc/crypttab

In my stupid opinion, there should be no failure, warnings, errors upon a clean install with all updates applied.  :)

It is not going to be obvious to the newbie or casual user if the file needs to be there or not. :(

I agree that the message should not be shown.

I think it is upowerd that should be changed.

Creating the /etc/crypttab file will trigger additional code for anyone
still using sysvinit (take a look at /etc/rc.d/rc.sysinit), so I don't
think creating the file is the right way to fix it.

Thanks for your help, Dave :)

assigning to maintainer

CC: (none) => marja11
Assignee: bugsquad => dmorganec
Source RPM: (none) => upower

large amounts of /var/log/messages with
udisksd[3642]: Error opening /etc/crypttab file: Error reading file '/etc/crypttab': Is a directory (g-file-error-quark, 1)

Source RPM: upower => udisks2-1.92.0-2.mga2.src.rpm

(In reply to comment #7)
> large amounts of /var/log/messages with
> udisksd[3642]: Error opening /etc/crypttab file: Error reading file
> '/etc/crypttab': Is a directory (g-file-error-quark, 1)

reassigning to udisks2 maintainer, then

Assignee: dmorganec => fundawang

Hmm, the fact that is says: 

udisksd[3642]: Error opening /etc/crypttab file: Error reading file
'/etc/crypttab': Is a directory (g-file-error-quark, 1)

Is pretty strange... is /etc/crypttab a directory? If so, why?

Also, I reckon the best approach is just to ensure initscripts provides /etc/crypttab.

Sure the rc.sysinit stuff will do some thing related to it, but that could be modified to be less dumb.

As udisks2 monitors the file for modifications, I think it's simply easier if it exists, at least for now.

Hi,

This bug was filed against cauldron, but we do not have cauldron at the moment.

Please report whether this bug is still valid for Mageia 2.

Thanks :)

Cheers,
marja

Keywords: (none) => NEEDINFO

(In reply to comment #11)

> Please report whether this bug is still valid for Mageia 2.

still valid

Keywords: NEEDINFO => (none)

*** Bug 6455 has been marked as a duplicate of this bug. ***

CC: (none) => crxssi

Please look at the bottom of this mail to see whether you're the assignee of this  bug, if you don't already know whether you are.


If you're the assignee:

We'd like to know for sure whether this bug was assigned correctly. Please change status to ASSIGNED if it is, or put OK on the whiteboard instead.

If you don't have a clue and don't see a way to find out, then please put NEEDHELP on the whiteboard.

Please assign back to Bug Squad or to the correct person to solve this bug if we were wrong to assign it to you, and explain why.

Thanks :)

**************************** 

@ the reporter and persons in the cc of this bug:

If you have any new information that wasn't given before (like this bug being valid for another version of Mageia, too, or it being solved) please tell us.

@ the reporter of this bug

If you didn't reply yet to a request for more information, please do so within two weeks from now.

Thanks all :-D

*** Bug 6992 has been marked as a duplicate of this bug. ***

CC: (none) => guillomovitch

*** Bug 7308 has been marked as a duplicate of this bug. ***

CC: (none) => eeeemail

I fixed this (eventually) by shipping any empty crypttab in initscripts. It feels wrong, but I'd rather things are quiet than worry about it too much!!

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