Bug 5689 - unable to reboot
Summary: unable to reboot
Status: RESOLVED OLD
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: Cauldron
Hardware: x86_64 Linux
Priority: High major
Target Milestone: ---
Assignee: Mageia Bug Squad
QA Contact:
URL:
Whiteboard:
Keywords: NEEDINFO
Depends on:
Blocks:
 
Reported: 2012-04-30 05:52 CEST by Simple
Modified: 2014-05-05 09:54 CEST (History)
3 users (show)

See Also:
Source RPM: initscripts-9.34-20.mga2.src.rpm
CVE:
Status comment:


Attachments

Description Simple 2012-04-30 05:52:57 CEST
Since i have installed Mageia2-beta3 reboot wasnt possible anymore.

When i hit to reboot it leaves  the kde session and then stays in a black sceen forever.

If i hot CRTL+ALT+F1 i can see this:

Starting LSB: Wait for the hotplugged network to be up...

I dont know if this is handled by init-scripts, but its what in POV does, if not please correct.
Comment 1 Manuel Hiebel 2012-04-30 16:22:12 CEST
Is your cauldron updated ? it should be corrected now

Keywords: (none) => NEEDINFO

Comment 2 Simple 2012-04-30 17:07:16 CEST
Ãow instead appearing to start hotplugged network, appears for bluetooth and again i need to press the shutdown button.
Comment 3 Simple 2012-04-30 17:12:11 CEST
Seams there were more packages and now yes, its updated and the problem seams fixed.
But what was the problem, could you describe it

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

Comment 4 Simple 2012-05-01 14:07:30 CEST
This continues being a valid bug after updating all cauldron packages.

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

Comment 5 Manuel Hiebel 2012-05-01 21:54:20 CEST
arf a we have a similar bugs with the pre-rc isos, let's keep the other one

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

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

Comment 6 Simple 2012-05-13 18:41:53 CEST
I dont think this is the same bug as https://bugs.mageia.org/show_bug.cgi?id=5674 since it does not hang when rebooting or turning off the machine, it simply takes tooo long.

I am using cauldron (updated) and its very very annoying when rebooting or turning off the machine to take so so much time...

and it always appears this:
Starting LSB: Wait for the hotplugged network to be up...

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

Comment 7 Manuel Hiebel 2012-05-14 17:03:52 CEST
works fine here, but I have seen this on debian os (squeze)
Comment 8 Marja Van Waes 2012-05-26 13:02:40 CEST
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
Comment 9 Marja Van Waes 2012-08-04 14:15:53 CEST
2 months later, no reply, closing as old.

Please reopen when needed and tell for which version(s) of Mageia this bug is still valid.

If it is valid for both cauldron and Mageia 2, then please put MGA2TOO on the whiteboard and let version remain set to cauldron

Status: REOPENED => RESOLVED
CC: (none) => marja11
Resolution: (none) => OLD

Comment 10 Zen Cuenta 2012-11-25 20:52:30 CET
Still present. I installed Mageia 2 Caldero 64-Bit and after a few reboots this happens. What can I do?

Status: RESOLVED => REOPENED
CC: (none) => sum1one
Resolution: OLD => (none)

Zen Cuenta 2012-11-25 20:53:25 CET

Priority: Normal => High

Comment 11 roelof Wobben 2013-01-07 19:25:00 CET
@Zen : Did you have this problen in KDE ? 
Can you also try of the problem is in another DE like Gnome. 

Does reboot from the konsole work ?

Roelof

CC: (none) => r.wobben

Comment 12 Marja Van Waes 2014-05-05 09:54:02 CEST
Since there are insufficient details provided in this report for us to investigate the issue further, and we have not received feedback to the information we have requested above, we will assume the problem was not reproducible, or has been fixed in one of the updates we have released for the reporter's distribution.

Users who have experienced this problem are encouraged to upgrade to the latest update of their distribution, and if this issue turns out to still be reproducible in the latest update, please reopen this bug with additional information.

Closing as OLD.

Status: REOPENED => RESOLVED
Resolution: (none) => OLD


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