Bug 157496 - message detail "media exception" not very helpfull
Summary: message detail "media exception" not very helpfull
Status: RESOLVED FIXED
Alias: None
Product: SUSE Linux 10.1
Classification: openSUSE
Component: YaST2 (show other bugs)
Version: Beta 6
Hardware: i586 Other
: P5 - None : Enhancement (vote)
Target Milestone: ---
Assignee: Jiri Srain
QA Contact: Klaus Kämpf
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-03-12 18:50 UTC by michel munnix
Modified: 2006-08-08 14:39 UTC (History)
1 user (show)

See Also:
Found By: Other
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---

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

Note You need to log in before you can comment on or make changes to this bug.
Description michel munnix 2006-03-12 18:50:53 UTC 
After beeing told to load CD2, I put CD4 in the drive.
When clicking the button for details, the message is "media exception",
A message like "CD4 is currently loaded, please load CD2" or "read error on /dev/hdc" would be more helpfull.
Comment 1 Michael Gross 2006-03-13 10:30:12 UTC 
indeed

I'm not sure if these messages are getting passed through from the backend. If so, assign it back to us, Jiri.
Comment 2 Jiri Srain 2006-07-24 06:32:32 UTC 
Is this still valid with final version? If it is, can you attach the logs so that I can track the exception?
Comment 3 michel munnix 2006-08-03 12:51:51 UTC 
I rechecked with final, Now it is understandable:
"Media source ... does not contain the desired media" when wrong CD inserted.
"Can'nt mount ..." when media defect on sector 0
"Err 3: Package ... fails integrity check, do you want to retry or abort install" when defect is in rpm files.

In that latest case, if I choose ignore, yast segfaults and installation stops, going to runlevel 5 whithout going through "setting root password, network setup and so on", this leaves the user in the dark. Should I open an other bug for this one ?
Comment 4 Jiri Srain 2006-08-08 14:38:37 UTC 
Yes, please, open another bug and attach logs and if possible, also backtrace. Marking this bug as FIXED.
Comment 5 Jiri Srain 2006-08-08 14:39:42 UTC 
BTW: You might also check whether the bug persists in SLED - if it is fixed there, it is not needed to report another bug - there is no way to fix it for 10.1 anyway, we can fix it only for 10.2.