Bug 4670 - 2_b1: Unit autovt@tty6.service failed to load: File exists. in runlevel 3
Summary: 2_b1: Unit autovt@tty6.service failed to load: File exists. in runlevel 3
Status: RESOLVED FIXED
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: Cauldron
Hardware: x86_64 Linux
Priority: Normal normal
Target Milestone: ---
Assignee: Mageia Bug Squad
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-02-24 07:38 CET by Bit Twister
Modified: 2012-02-25 13:15 CET (History)
0 users

See Also:
Source RPM: systemd-40-3.mga2.src.rpm
CVE:
Status comment:


Attachments

Description Bit Twister 2012-02-24 07:38:56 CET
Description of problem:

Snippet from /var/log/messages
Feb 23 23:04:20 cauldron  systemd-logind[498]: Failed to start unit: 

Unit autovt@tty6.service failed to load: File exists.
Unit autovt@tty5.service failed to load: File exists.
Unit autovt@tty4.service failed to load: File exists.
Unit autovt@tty3.service failed to load: File exists.
Unit autovt@tty2.service failed to load: File exists.
See system logs and 'systemctl status autovt@tty6.service' for details.


# systemctl status autovt@tty6.service
autovt@tty6.service
          Loaded: error (Reason: File exists)
          Active: inactive (dead)

Happens in my Mandriva 2011 VirtualBox guest and on my Mageia testbed system.

Version-Release number of selected component (if applicable):


How reproducible:   Intermittent


Steps to Reproduce:
1. clean install beta1 + updates
2. set runlevel 3 as default boot
3. remove splash=silent from /boot/grub/menu.lst
4. reboot
5. grep Failed /var/log/messages
Comment 1 Manuel Hiebel 2012-02-24 23:58:13 CET
Hi, can you reproduce with systemd 43 ?
Comment 2 Bit Twister 2012-02-25 13:15:53 CET
(In reply to comment #1)
> Hi, 

and a hello to you. :)

> can you reproduce with systemd 43 ?

No, but it was intermittent in old version.

I'll go ahead and resolve this bug and reopen if it happens again.

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


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