2008/11/18 Rick Stevens
<ricks@nerd.com>
cornel panceac wrote:
2008/11/17 Tom Horsley <tom.horsley@att.net>
On Mon, 17 Nov 2008 06:50:46 -0600
Rex Dieter <rdieter@math.unl.edu> wrote:
This is still the aging https://bugzilla.redhat.com/440343 problem.
Yes, would be wonderfully nice if a kernel hacker or maintainer would
ever
at least comment.
I'm not convinced it is the kernel anymore. After all, the F10 preview
can now tell that there is no media in the drive without waiting forever,
so it seems like at least some aspects of the drive status are fixed with
the latest drivers, yet k3b is still not functional, so this may be
entirely a k3b issue at this point (though it would still be nice to
know what the heck is going on).
maybe hal ....
cd-burner (yes, a Gnome thing) just to isolate it? If those tools
behave the same way, then I'd look deeper in the OS (hal, etc.).
brasero ejects the disk and then fails wit: "the media can't be ejected" . see attached file.
btw, hal is not managing the device because of powertop etc.
we also must not forget that the same system behaves differently in apparently same conditions, just like when anaconda is unable to select the same disk as the first disk on the system, on two successive tries.
Considering that KDE is still in flux a bit I'd lean towards k3b having
issues rather than the underlying system, but I'm not going to be
pedantic about it since I don't have F10 running anywhere just yet and I
rarely use KDE anyway. Divide and conquer.
----------------------------------------------------------------------
- Rick Stevens, Systems Engineer ricks@nerd.com -
- AIM/Skype: therps2 ICQ: 22643734 Yahoo: origrps2 -
- -
- To iterate is human, to recurse, divine. -
----------------------------------------------------------------------
--