Bug 300844 - Ubuntu 11.10 instant unresponsive freeze when k3b and audio cd, affects approx. 10% of disks, either type ro or rw, unknown dependencies
Summary: Ubuntu 11.10 instant unresponsive freeze when k3b and audio cd, affects appro...
Status: RESOLVED WORKSFORME
Alias: None
Product: k3b
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: Ubuntu Linux
: NOR critical
Target Milestone: ---
Assignee: k3b developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-05-30 05:31 UTC by cheryljosie
Modified: 2023-02-11 03:52 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description cheryljosie 2012-05-30 05:31:38 UTC
This is a very severe problem. Any time I have a particular cd in the drive and k3b open simultaneously, Ubuntu 11.10 immediately freezes. The system will not respond to anything except the hard reset button. Even the control-sysreq-k interrupt is hung.

This problem has been consistent since the release of 11.10. I have asked for it to be fixed on the ubuntu site and nothing happened.

Approximately 10% of my disks in my collection will cause this problem.

It does not seem to matter if the disk is a commercial read-only disk or if it is a write once disk.

 It does not seem to matter if the disk has any data on it.

The problem is 100% repeatable with a disk that has caused the freeze before, and never happens with a disk that has never caused the freeze.

Since the system immediately freezes, it is impossible to provide any debugging trace. It is also the most serious bug since it renders the entire system instantly dead when it happens.

The system is an Intel desktop motherboard dg965wh

google search
http://www.google.com/search?q=intel+desktop+motherboard&ie=utf-8&oe=utf-8&client=ubuntu&channel=fs#hl=en&client=ubuntu&hs=6oH&channel=fs&sclient=psy-ab&q=intel+desktop+motherboard+dg965wh&oq=intel+desktop+motherboard+dg&aq=2K&aqi=g-K4&aql=&gs_l=serp.1.2.0i30l4.20650.20650.1.26249.1.1.0.0.0.0.202.202.2-1.1.0...0.0.Jc9vg-gkiQo&pbx=1&bav=on.2,or.r_gc.r_pw.r_qf.,cf.osb&fp=4f5aab40f24779d9&biw=989&bih=356

technical spec
http://www.google.com/url?sa=t&rct=j&q=intel%20desktop%20motherboard%20dg965wh&source=web&cd=2&ved=0CIEBEBYwAQ&url=http%3A%2F%2Fdownloadmirror.intel.com%2F15052%2Feng%2FDG965WH_TechProdSpec.pdf&ei=z63FT_miG4X02QXV9MG4AQ&usg=AFQjCNF5MAVhbBM8QTn7NZG

I have two optical drives, one is a sony dvd and the other is a pioneer blu-ray and it does not matter which drive the disk is inserted into, the freeze is still 100% repeatable.

I really like using k3b but I am considering removing it from my system because of this bug. Every time I update my system I cross my fingers but the problem is never fixed.

Thank you for your time.
CherylJosie

I am sorry but this is all the information I can provide unless you instruct me on how to trap a trace to a file in real time before the crash happens so that I can send that to you.

Reproducible: Always

Steps to Reproduce:
1.insert cd
2.start k3b
3.or reverse the order, either way it freezes
Actual Results:  
if k3b is running when a 'bad' disk is inserted, the system freezes after 10 seconds.

if a 'bad' cd is in the drive when k3b is started, the mouse pointer changes to a stopwatch and the splash screen comes up and the system freezes. before the last update, the system froze when the splash screen was completely loaded. after the last update, the system froze while the splash screen was still a black rectangle.

Expected Results:  
not frozen

I am terribly sorry but you will have to instruct me on any additional information you want. I do not have a cpu emulator nor do I know how to use one to trace the system calls. Oh wait, I just remembered that I can run commands under a special execution shell and trap the system calls to a file as well as to a terminal screen, maybe that will shed some light on the problem if I start k3b from the command line with a 'bad' disk in it. I do not remember what the command to start the shell is, do you? I saw it on a web page somewhere about setting file system permissions... maybe I can find it somewhere. I will look...?
Comment 1 Paul Perspectoff 2012-06-12 22:17:49 UTC
This occurs for me whenever Dolphin is open at the same time as k3b. 

It is as if there is no lock for the two packages trying to access the CD/DVD at the same time...
Comment 2 cheryljosie 2012-09-17 19:50:08 UTC
I just updated the entire operating system using smart update on synaptic package manager and the system freeze still happened while ripping my cd library to my hard drive, hanging the system. This time I was listening to a music file on my hard drive using the audacious application, and when the system froze, one second's worth of music kept repeating over and over from the audio output, but otherwise the system was completely unresponsive to everything but the hard reset button.

One change is that my DVD drive burned out. I was hopeful that when one optical drive came out of the system the problem would be fixed but it is still there when I use the Blu Ray. This is why I resumed ripping my audio libray. SoundJuicer seems to get confused with the track numbering and I do not know how to use the CD paranoia settings with it. Actually I do not know how to use the CD paranoia settings with K3B either, and it seems to be broken when set to mode 3, so I just set it to mode 1 and pray that it actually does something, and then my system freezes again anyway.

Is there any priority on this bug? The status is still uncomfirmed even though another user has reported the same problem. I have not backed up my CD library because I have long transcode jobs running on tv shows I recorded with mythtv and if my system freezes and needs reboot once every 10 audio discs that I rip, I will not get any transcoding done.

There are three fields below this window I am typing in and I am not sure what to do with them. They are set by default to

status: uncomfirmed
resolved as: fixed
duplicate of: <blank>

so I am setting the second one to REMIND since I do not know what else to set it to when I post updated info.
Comment 3 Andrew Crouthamel 2018-11-12 02:58:35 UTC
Dear Bug Submitter,

This bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? I am setting the status to NEEDSINFO pending your response, please change the Status back to REPORTED when you respond.

Thank you for helping us make KDE software even better for everyone!
Comment 4 Andrew Crouthamel 2018-11-21 04:41:23 UTC
Dear Bug Submitter,

This is a reminder that this bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? This bug will be moved back to REPORTED Status for manual review later, which may take a while. If you are able to, please lend us a hand.

Thank you for helping us make KDE software even better for everyone!
Comment 5 Justin Zobel 2023-01-12 01:58:17 UTC
Thank you for reporting this issue in KDE software. As it has been a while since this issue was reported, can we please ask you to see if you can reproduce the issue with a recent software version?

If you can reproduce the issue, please change the status to "REPORTED" when replying. Thank you!
Comment 6 Bug Janitor Service 2023-01-27 05:07:14 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 7 Bug Janitor Service 2023-02-11 03:52:04 UTC
This bug has been in NEEDSINFO status with no change for at least
30 days. The bug is now closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!