Bug 154023 - Doesn't verify CD, then refuses to quit/close (either thru windowing system or 'quit' in file menu)
Summary: Doesn't verify CD, then refuses to quit/close (either thru windowing system o...
Status: RESOLVED UNMAINTAINED
Alias: None
Product: k3b
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: Ubuntu Linux
: NOR normal
Target Milestone: ---
Assignee: Sebastian Trueg
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-12-14 12:32 UTC by Josh Rosenbluh
Modified: 2010-03-16 16:05 UTC (History)
0 users

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 Josh Rosenbluh 2007-12-14 12:32:07 UTC
Version:           1.0.3 (using KDE KDE 3.5.8)
Installed from:    Ubuntu Packages
Compiler:          Gutsy 
OS:                Linux

After writing data CD, K3b ejects disc and then loads it. It usually does not do a verification, although I suspect that may be due to GNOME (although I would think it would still be possible to read the disc). I am unable to write a second disc and the only way for me to close K3b so I can restart it is to kill the process, since the UI is not responsive to requests to quit, but the rest of the interface works fine.

I recognize that people have filed bug reports in the past relating to this sort of behavior, but the only one that seems similar was from 2005 and referred to an older version at the time. If I could figure out a way to prevent K3b (or the drive) from ejecting the CD before verification, that would be a great workaround.
Comment 1 Ziffler 2008-07-02 12:58:06 UTC
I have had a similar experience with verify.

The data DVD burned successfully and the DVD is ejected.  Then it hangs. The DVD is not re-loaded and manual reload does not help; k3b just hangs.

Platform: k3b 1.0.4 KDE 3.5.9 ubuntu 8.04 on i386
Comment 2 Ziffler 2008-07-02 13:02:25 UTC
Please ignore my previous comment. Wrong bug!
Comment 3 markuss 2010-03-16 16:05:34 UTC
In an attempt to clean up old bugs that are not valid for K3b 2.0 (=KDE SC 4.x port) anymore, this is now being marked as UNMAINTAINED.
If this bug is still valid for 2.0, please reopen it.