Bug 11650 - harddrake can cause the boot to lock if it tries to download an rpm
Summary: harddrake can cause the boot to lock if it tries to download an rpm
Status: RESOLVED INVALID
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: Cauldron
Hardware: All Linux
Priority: Normal major
Target Milestone: ---
Assignee: Thierry Vignaud
QA Contact:
URL:
Whiteboard:
Keywords: Triaged
Depends on:
Blocks:
 
Reported: 2013-11-11 20:25 CET by Joseph Wang
Modified: 2015-04-27 10:56 CEST (History)
2 users (show)

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

Attachments
Add an attachment (proposed patch, testcase, etc.)

Description Joseph Wang 2013-11-11 20:25:03 CET 
Description of problem:

/usr/share/harddrake/service_harddrake can cause the boot to lock up.  This can occur when harddrake wants to download an rpm for fglrx but the network has not been activated.

service_harddrake should have a time-out which continues the boot after 60 seconds with a notice that the hardware load has been timed out




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

Any


How reproducible:


Steps to Reproduce:
1. set urpmi to do a network download
2. downgrade fglrx
3. boot and disconnect machine from network


Reproducible: 

Steps to Reproduce:
Joseph Wang 2013-11-11 20:25:46 CET

Severity: normal => major

Manuel Hiebel 2013-12-22 13:17:53 CET

Keywords: (none) => Triaged
Assignee: bugsquad => thierry.vignaud
Source RPM: harddrake-15.72-1.mga4 => drakxtools

Comment 1 Thierry Vignaud 2013-12-22 13:25:48 CET 
CCing blino as he did fixes regarding this in the old days

CC: (none) => mageia, thierry.vignaud

Comment 2 Thierry Vignaud 2013-12-22 13:33:07 CET 
Actually harddrake already has a 2mn timeout...
Comment 3 Samuel Verschelde 2015-04-23 13:59:05 CEST 
Closing as INVALID per comment #2. Please reopen if needed.

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

Comment 4 Thierry Vignaud 2015-04-27 10:56:04 CEST 
Well, that depends on whether Joseph was describing a theoretical issue or something he has seen.
@Joseph: please reopen if you saw it
Note You need to log in before you can comment on or make changes to this bug.