Bug 4846 - Systemd: shutdown fails intermittently
Summary: Systemd: shutdown fails intermittently
Status: RESOLVED FIXED
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: Cauldron
Hardware: i586 Linux
Priority: Normal major
Target Milestone: ---
Assignee: Mageia Bug Squad
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: 2120
  Show dependency treegraph
 
Reported: 2012-03-07 20:46 CET by diego w
Modified: 2012-03-27 02:38 CEST (History)
2 users (show)

See Also:
Source RPM: systemd-43-2.mga2.src.rpm
CVE:
Status comment:


Attachments

Description diego w 2012-03-07 20:46:30 CET
Description of problem:
with systemd the shutdown (from KDM after landing there due to #4605) will not always succeed.

the system stopps on virtual terminal 1 with message starting dracut or similar
switching to VT2 permits logging in, a halt command freezes the system with a "bright black" screen.


this only happens intermittently and i couldnt find a way to trigger it yet.

Version-Release number of selected component (if applicable):
systemd-43-2.mga2.src.rpm

How reproducible:
intermittent

Steps to Reproduce:
1. shutdown pc from kde
2. shutdown pc from kdm
3. shutdown will not succeed
Comment 1 Manuel Hiebel 2012-03-13 16:52:02 CET
maybe it's a duplicate of bug 4729 or from other one but I don't found them :/

CC: (none) => dmorganec, mageia
Blocks: (none) => 2120

Comment 2 diego w 2012-03-13 21:53:48 CET
its not a pure halt instead of a poweroff

the system still responds to several things.
I can't really tell you to what it responds, but some keypress have some effect, unfortunately not the desired one.

it is quite a rare phenomenon, sometimes it happens on reboot, sometimes on shutdown. 

unfortunately it mostly happens when my wife is using my laptop...

i will try to further confirm.
Comment 3 diego w 2012-03-26 23:58:31 CEST
never happened again... should we close?
Comment 4 Manuel Hiebel 2012-03-27 02:38:51 CEST
yes since you are the reported, thanks

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


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