SOLVED: K3b: unable to mount blank DVDs

[vtpup]

I have been trying to find a solution to a problem with K3b and Puppy's Pmount in version 4.1.1.

Basically, an empty DVD (not CD) is alternately probed by Pmount and by K3b in a continuing cycle, and never shows up as an empty media in K3b. Or it does briefly, but then Puppy re-probes it and it disappears from the Burner window in K3b.

I was on the K3b site and just noticed the following promising version update -- bolded text is mine:

27.05.2008 K3b 1.0.5 released

After two weeks without internet connection and hacking on the K3b KDE 4 port I am still not finished. K3b 1.1 (I decided to not increase the major number for the KDE 4 release as it will not have many new features) will again take more time.

In the meantime enjoy this very small bugfix release which fixes three annoyances:

* Fixed CD Copy device selection when starting from the KDE "run" dialog (Bug 151924)
* Fixed HAL mounting (thanks to Ken Milmore)
* Always wait for the drive to become ready before starting verification (this should fix some of the problems with failed verification where K3b claims that no medium is in the drive.)

I hope it does. I've documented the problem in these two threads, but until now, no solution ever presented itself:

http://www.murga-linux.com/puppy/viewtopic.php?t=36473
http://www.murga-linux.com/puppy/viewtopic.php?t=27385

The question now is whether K3b 1.05 will work with the libraries and dependencies already installed, or whether this work will have to be repeated all over again. jcoder has provided a split set of .pets so that the version of k3b can be changed. I'll try to get it going with the 1.05 version.

[MU]

I am not in Puppy 4 at moment.
So just some vague hints.
Puppy 4 has a new uevent system, there is a daemon running checking for new hardware.

Maybe you can stop it.
Type:
ps -ax
to see all processes.
If there is one like
1234 ueventd
then type:
kill 1234
Just use the number you see, no other one!
Maybe you also can use the easier:
killall ueventd

I'm not sure, that the exact name is ueventd, so look for something similar to it. Maybe pup_eventd or so.
As a consequence no more new hardware would be detected automatically in the running session, but that might be ok in many cases.
Mark

[vtpup]

Well, no joy (except for the holidays)---

I uninstalled the K3b 1.04 sfs,, installed the jcoder k3b deps (already had the jcoder libs) and installed through gslapt the k3b 1.05 package.

It opened properly from the terminal. But the cycling problem between K3b and Pmount continues to occur. It happens no matter whether you wait for Pmount to finish probing, after inserting a DVD, before starting K3b, or if you start K3b before inserting a blank DVD.

MU:

Thank you very kindly for your suggestions, and for all your help so far with regards to K3b.

I did try

Code: Select all

ps -ax

, but couldn't find an entry for ueventd

I also tried killall ueventd , but the system reported back that it couldn't because there was no ueventd process running.

Maybe the process has a different name in 4.1.1?

I also tried looking at top while inserting a dvd, and also while starting k3b after inserting a disk.

I should also add that the DVD burner is a USB 2.0 burner.

I don't know if that makes any difference. It is a Sony DVD RW DRX-830U

Although k3b reports it as a DRU-830A. I don't think that makes any difference.

Below is a relevant section from the terminal as K3b recognizes the drive, then initially the blank DVD, then loses it (busy) and tries again. The last few stanzas repeat as long as Pmount and K3b alternately compete for the drive.

Device sr0 is an internal CD Burner.
Device SR1 is the USB external DVD RW

Code: Select all

/dev/sr1 resolved to /dev/sr1
(K3bDevice::DeviceManager) dev /dev/sr1 already found
/dev/scd0 resolved to /dev/scd0
(K3bDevice::DeviceManager) dev /dev/scd0 already found
(K3bDevice::DeviceManager) found config entry for devicetype: SONY DVD RW DRU-83          0A
(K3bDevice::DeviceManager) found config entry for devicetype: HL-DT-ST RW/DVD GC          C-4240N
k3b: (K3bCdrecordProgram) could not start /usr/local/sbin
k3b: (K3bMkisofsProgram) could not start /usr/local/sbin
k3b: (K3bCdrecordProgram) could not start /opt/schily/bin
k3b: (K3bMkisofsProgram) could not start /opt/schily/bin
k3b: (K3bCdrecordProgram) could not start /usr/lib/qt/bin
k3b: (K3bMkisofsProgram) could not start /usr/lib/qt/bin
k3b: (K3bExternalBinManager) Cdrecord 1.1.6 features: wodim, gracetime, overburn          , cdtext, clone, tao, cuefile, xamix, plain-atapi, hacked-atapi, short-track-raw          , audio-stdin, burnfree
Devices:
------------------------------
Blockdevice:    /dev/sr1
Generic device: /dev/sg2
Vendor:         SONY
Description:    DVD RW DRU-830A
Version:        SS25
Write speed:    0
Profiles:       DVD-ROM, DVD-R Sequential, DVD-R Dual Layer Sequential, DVD-R Du          al Layer Jump, DVD-RAM, DVD-RW Restricted Overwrite, DVD-RW Sequential, DVD+RW,           DVD+R, DVD+R Dual Layer, CD-ROM, CD-R, CD-RW
Read Cap:       DVD-ROM, DVD-R, DVD-R Sequential, DVD-R Dual Layer, DVD-R Dual L          ayer Sequential, DVD-R Dual Layer Jump, DVD-RW, DVD-RW Restricted Overwrite, DVD          -RW Sequential, DVD+RW, DVD+R, DVD+RW Dual Layer, DVD+R Dual Layer, CD-ROM, CD-R          , CD-RW
Write Cap:      DVD-R, DVD-R Sequential, DVD-R Dual Layer, DVD-R Dual Layer Sequ          ential, DVD-R Dual Layer Jump, DVD-RW, DVD-RW Restricted Overwrite, DVD-RW Seque          ntial, DVD+RW, DVD+R, DVD+R Dual Layer, CD-R, CD-RW
Writing modes:  SAO, TAO, RAW, SAO/R96P, SAO/R96R, RAW/R16, RAW/R96P, RAW/R96R,           Restricted Overwrite, Layer Jump
Reader aliases: /dev/sr1, /dev/scd1
------------------------------
Blockdevice:    /dev/scd0
Generic device: /dev/sg1
Vendor:         HL-DT-ST
Description:    RW/DVD GCC-4240N
Version:        0211
Write speed:    0
Profiles:       DVD-ROM, CD-ROM, CD-R, CD-RW
Read Cap:       DVD-ROM, CD-ROM, CD-R, CD-RW
Write Cap:      CD-R, CD-RW
Writing modes:  SAO, TAO, RAW, SAO/R96P, SAO/R96R, RAW/R16, RAW/R96P, RAW/R96R
Reader aliases: /dev/scd0
------------------------------
k3b: (K3bAudioServer::findOutputPlugin) could not find output plugin arts
kdecore (KAction): WARNING: KActionCollection::operator+=(): function is severel          y deprecated.
k3b: (K3bFileTreeView::addCdDeviceBranches)
k3b: (K3bFileTreeView::addCdDeviceBranches) done
k3b: (K3bFileTreeView::addCdDeviceBranches)
k3b: (K3bFileTreeView::addCdDeviceBranches) done
First sec data area: 43:41:33 (LBA 196608) (402653184
Last sec data area: 00:00:00 (LBA 0) (0 Bytes)
Last sec layer 1: 00:00:00 (LBA 0) (0 Bytes)
Layer 1 length: 00:00:01 (LBA 1) (2048 Bytes)
Layer 2 length: 00:00:00 (LBA 0) (0 Bytes)
k3b: (K3bMedium) found medium:
k3b: =====================================================
DiskInfo:
Mediatype:       DVD-R Sequential
Current Profile: DVD-R Sequential
Disk state:      empty
Empty:           1
Rewritable:      0
Appendable:      0
Sessions:        0
Tracks:          0
Layers:          1
Capacity:        510:46:46 (LBA 2298496) (4707319808 Bytes)
Remaining size:  510:46:46 (LBA 2298496) (4707319808 Bytes)
Used Size:       00:00:00 (LBA 0) (0 Bytes)
k3b: =====================================================
(K3bDevice::ScsiCommand) failed:
                           command:    GET PERFORMANCE (ac)
                           errorcode:  70
                           sense key:  NOT READY (2)
                           asc:        4
                           ascq:       1
(K3bDevice::Device) /dev/sr1: GET PERFORMANCE length det failed.
(K3bDevice::Device) /dev/sr1:  Number of supported write speeds via 2A: 0
First sec data area: 43:41:33 (LBA 196608) (402653184
Last sec data area: 00:00:00 (LBA 0) (0 Bytes)
Last sec layer 1: 00:00:00 (LBA 0) (0 Bytes)
Layer 1 length: 00:00:01 (LBA 1) (2048 Bytes)
Layer 2 length: 00:00:00 (LBA 0) (0 Bytes)
k3b: (K3bMedium) found medium:
k3b: =====================================================
DiskInfo:
Mediatype:       DVD-R Sequential
Current Profile: DVD-R Sequential
Disk state:      empty
Empty:           1
Rewritable:      0
Appendable:      0
Sessions:        0
Tracks:          0
Layers:          1
Capacity:        510:46:46 (LBA 2298496) (4707319808 Bytes)
Remaining size:  510:46:46 (LBA 2298496) (4707319808 Bytes)
Used Size:       00:00:00 (LBA 0) (0 Bytes)
k3b: =====================================================
(K3bDevice::ScsiCommand) failed:
                           command:    GET PERFORMANCE (ac)
                           errorcode:  70
                           sense key:  NOT READY (2)
                           asc:        4
                           ascq:       1
(K3bDevice::Device) /dev/sr1: GET PERFORMANCE length det failed.
(K3bDevice::Device) /dev/sr1:  Number of supported write speeds via 2A: 0
First sec data area: 43:41:33 (LBA 196608) (402653184
Last sec data area: 00:00:00 (LBA 0) (0 Bytes)
Last sec layer 1: 00:00:00 (LBA 0) (0 Bytes)
Layer 1 length: 00:00:01 (LBA 1) (2048 Bytes)
Layer 2 length: 00:00:00 (LBA 0) (0 Bytes)
k3b: (K3bMedium) found medium:
k3b: =====================================================
(snip) 

Thanks for any assistance.

[vtpup]

MU, would this be the name of uevent?

19157 tty1 S 0:08 /bin/sh /sbin/pup_event_frontend_d

(EDIT: I just tried "kill 19157" and then started K3b, and inserted a blank DVD. The bad behavior continued exactly as before.

However, the PMount graphical screen and warning message to wait while probing did not appear. So it looks like the Pmount script has been stopped -- I'm not sure why K3b doesn't now work properly.)

Well if not, here's the full list of processes:

Code: Select all

# ps -ax
Warning: bad ps syntax, perhaps a bogus '-'? See http://procps.sf.net/faq.html
  PID TTY      STAT   TIME COMMAND
    1 ?        Ss     0:00 init
    2 ?        S<     0:00 [kthreadd]
    3 ?        S<     0:00 [ksoftirqd/0]
    4 ?        S<     0:00 [events/0]
    5 ?        S<     0:00 [khelper]
   60 ?        S<     0:00 [kblockd/0]
   62 ?        S<     0:00 [kacpid]
   63 ?        S<     0:00 [kacpi_notify]
  145 ?        S<     0:00 [ata/0]
  146 ?        S<     0:00 [ata_aux]
  149 ?        S<     0:00 [kseriod]
  178 ?        S      0:00 [pdflush]
  179 ?        S      0:00 [pdflush]
  180 ?        S<     0:00 [kswapd0]
  181 ?        S<     0:00 [aio/0]
  831 ?        S<     0:00 [scsi_eh_0]
  833 ?        S<     0:00 [scsi_eh_1]
  912 ?        S<     0:00 [kpsmoused]
  956 ?        S<     0:00 [pccardd]
  961 ?        S<     0:00 [pccardd]
  983 ?        S<     0:00 [ksuspend_usbd]
  989 ?        S<     0:00 [khubd]
 1043 ?        S<     0:00 [aufsd]
 1044 ?        S<     0:00 [aufsd]
 1045 ?        S<     0:00 [aufsd]
 1046 ?        S<     0:00 [aufsd]
 1416 ?        S<     0:00 [kjournald]
 1433 ?        S<     0:02 [loop1]
 1518 ?        S<     0:00 [loop0]
 1655 ?        S<     0:00 [loop4]
 1662 ?        S<     0:00 [loop5]
 1669 ?        S<     0:00 [loop6]
 4324 tty1     S      0:00 /bin/sh /usr/bin/mozilla
 4343 tty1     S      0:00 /bin/sh /usr/lib/seamonkey-1.1.11/run-mozilla.sh /usr/lib/seamo
 4348 tty1     Sl     3:43 /usr/lib/seamonkey-1.1.11/seamonkey-bin
 9885 ?        S<     0:00 [scsi_eh_3]
 9886 ?        S<     0:00 [usb-storage]
15226 ?        S<s    0:00 /sbin/udevd --daemon
17087 ?        Ss     0:00 syslogd -m 0
17110 ?        Ss     0:00 klogd
17445 ?        S<     0:00 [rt61pci]
17982 tty1     S      0:02 /usr/bin/mrxvt
17983 pts/0    Ss     0:00 bash
18087 tty1     Ss+    0:00 /bin/sh /usr/X11R7/bin/xwin
18088 tty2     Ss+    0:00 /sbin/getty 38400 tty2
18148 ?        Ss     0:00 /usr/sbin/cupsd
18321 ?        Ss     0:00 /usr/bin/vmnet-bridge -s 6 -d /var/run/vmnet-bridge-0.pid -n 0
18848 ?        Ss     0:00 wpa_supplicant -i wlan0 -D wext -c /etc/network-wizard/wireless
18966 ?        Ss     0:00 /usr/bin/vmnet-dhcpd -s 6 -cf /etc/vmware/vmnet1/dhcpd/dhcpd.co
18972 ?        Ss     0:00 /usr/bin/vmnet-netifup -s 6 -d /var/run/vmnet-netifup-vmnet1.pi
18974 ?        Ss     0:00 /usr/bin/vmnet-dhcpd -s 6 -cf /etc/vmware/vmnet8/dhcpd/dhcpd.co
18976 ?        Ss     0:00 /usr/bin/vmnet-natd -s 6 -d /var/run/vmnet-natd-8.pid -m /var/r
18982 ?        Ss     0:00 /usr/bin/vmnet-netifup -s 6 -d /var/run/vmnet-netifup-vmnet8.pi
19107 tty1     S+     0:00 /usr/X11R7/bin/xinit /root/.xinitrc -- -br -nolisten tcp
19108 tty3     S<s+   1:46 X :0 -br -nolisten tcp
19131 tty1     S      0:01 jwm
19157 tty1     S      0:09 /bin/sh /sbin/pup_event_frontend_d
19179 tty1     S      0:03 /usr/local/apps/ROX-Filer/ROX-Filer -p /root/Choices/ROX-Filer/
19184 tty1     S      0:00 absvolume -bg #dddddd
19187 tty1     S      0:00 xload -nolabel -fg red -hl white -bg #dddddd
19189 tty1     S      0:00 freememapplet
19191 tty1     S      0:06 asapm -u 4
19194 tty1     S      0:06 blinky -bg #dddddd
26326 tty1     S      0:00 /usr/bin/inotifywait -e modify --format %w /tmp/pup_event_sizef
30218 tty1     Z      0:00 [jwm] <defunct>
32344 tty1     S      0:00 sleep 2
32345 pts/0    R+     0:00 ps-FULL -ax

[MU]

yes, that was the correct process.
When it is stopped, you now can exclude, that 2 programs simultaneously access the drive.
But I don't know, why it still will not work.
Did you try, if pburn works?

I have no big experience with burners.
If you get similar errors in pburn, maybe zigbert can help you.
He has more experience in reading those error messages.
Mark

[vtpup]

Thank you Mark for narrowing down the possibilities for me.

Using PBurn, I did try to insert a blank DVD into the external USB burner and it didn't recognize the medium using a USB 2 Port. I also have USB 1.1 ports, and it did seem to recognize the disk. I haven't tried a burn yet, but USB 1.1 is not a good option for DVDs since they are four and a half Gigs.

EDIT:

The section in blue below is incorrect. The problem is NOT due to a hardware or USB power issue. I had forgotten that I tried the exact same hardware on Muppy, and ran K3b there with no problems getting K3b to recognize a blank DVD disk.

I am wondering if the USB power is adequate on the USB 2 ports. I'm buying a USB Y cable (which increases the power available to a device through the USB line) and will test with that when it arrives.

K3b would not work on either port. But perhaps it will when the new cable arrives.

The USB 2 ports are on a PCMCIA (Cardbus) adapter card. The USB 1.1 ports are on the laptop itself (A Thinkpad T30). It is possible that the adapter card isn't providing enough power to the USB ports.

It would be helpful if someone else can either confirm (or not) the problem I have with K3b in accepting blank DVD media on some other computer with some other hardware setup.

If others don't have the problem with Puppy 4.1.1, then this may just boil down to a hardware problem on my own computer involving the USB adapter..

Thanks again for your help, Mark.

[vtpup]

New clues and weirdness with Puppy:

I have noticed that even good burned CD's and DVDs were not being properly mounted by Pmount even in my onboard CD/DVDrom. This is the built in one, not the USB burner. I couldn't even open up the Puppy 4.1.1 CD.

To check everything out, I loaded up Muppy from CD. It worked perfectly. I was able to open K3b, load a blank DVD, into the USB burner. I was able also to read any data disk I had (DVD or CD) in my onboard drive.

I then rebooted and booted up the Puppy 4.1.1 CD in pfix=ram. The same drive that PMount reported it couldn't read booted up fine after the Bios post screen. So the drive and CD were fine. It is clearly something wrong with the frugal installed puppy.

While in the pfix=ram system, I tested out both drives with a number of CDs and everything worked well. So I thought that maybe I had some kind of system corruption on the frugal installed version.

I therefore decided to simulate a version upgrade with pfix=clean, in order to clean up any system files that might be wrong or damaged.

Pfix=clean gives the message that you are doing a simulated upggrade, but below that gives a somewhat confusing message that it is upgrading from version 410 to 411. I have version 411 installed, so that doesn't make a lot of sense.

Anyway the system continued upgrading and then brought up the desktop, as normal. However I found that I couldn't go online. I had to redo the network configuration wizard. This also didn't work, because none of the wireless card drivers would work, or could even be found.

BUT, one thing that DID work was K3b (it recognized blank DVDs) and my internal drive worked perfectly as well. So I thought I had solved my problems, and merely needed to get network working and everything would be all set.

I decided that maybe I needed to reboot to get network access, and yes this worked perfectly. I did not have to run the Network Connection wizard -- all settings and drivers had been restored, and I was automatically connected.

HOWEVER, K3b had reverted to its old behavior, and again, my onboard CDrom was refusing to even read the puppy 4.1.1 cd.

So can someone explain THAT kind of behavior? I am totally confused by Puppy 4.1.1 at this point.

[mikeb]

Have you tried running from the command line to see what feedback there is launching and inserting a disk......I wonder about how puppy allocates default dvd, cd, cdrom,burner...just a thouht that occured from your last post.. There used to be a wizard for setting this up.

Certainly seems related to puppy 4.11...anything in the 4.111 bug thread?

regards

mike

[vtpup]

Thanks Mike,

I did a number of additional tests, with various versions of Puppy, in both pfix=ram, boot from CD, and boot from HD.

I won't bore you with the details but the upshot was, boots from CD worked generally better with the internal drive than boots from HD.

The final conclusion after booting 4.1.1, 4.1.1 retro, and 4.1.2 was that the retro version worked perfectly, and the later kernel in all versions showed the same problems with K3b and the external USB burner.

Usually booting from CD worked okay with the internal CD/DVDrom. Boots from HD did not work well with it at all.

I therefore deleted the existing pup411 sfs file from my hard drive, and booted the 4.1.1 retro CD. I then did a pfix=purge. Rebooted and hopefully I now have a clean 4.1.1 retro version on HD.

I rebooted again and had to restore some settings that the purge operation knocked out. But it looks like my data is all there as well as installed programs. I've got to be a little careful with these because some, like VMWare Player were configured for the later kernel.

A side benefit seems to be that Wine is running with seemingly more stability -- particularly in terms of window management. I haven't had time to check this out>

I had no idea this laptop was going to need the retro version, as I have been running the later kernel for over a month continuously. And as I said, when booted from CD or run from CD with pfix=ram, there were no obvious problems. The laptop is a Thinkpad T30 1.8ghz Pent 4.

But from the flakiness of CD/DVD drive mounts it seems in retrospect that it should have been more apparent.

By the way, the explanation for the weirdness experienced in my last post was due to the fact that the CD I booted off of was a retro
411, even though I thought it was a standard 411. And the system I had on the HD was a standard version.

Unfortunately both have the same filename: pup_411.sfs so they are indistinguishable if you forget to label a CD. I was able to determin that the CD in question was a retro, by doing a properties on the file, and checking the date against a known retro 411 and a known standard 411.

I would like to put in a strong suggestion to whoever eventually continues Puppy development that these two different versions include in their filenames something to distinguish them!

Anyway, for anyone who also has similar experiences with CD/DVD mounting problems, whether with K3b or not, try a retro version of Puppy.

It is still undetermined whether the problems with the later kernel are simply related to my laptop and drives, or whether they hold for later hardware as well. The interim solution in either case seems to be to drop back to an earlier kernel with Puppy.

[mikeb]

Well stunning piece of detective work....I wonder if this kernel/hardware issue needs mentioning in the bugs forum as it seems a bit strange that you would be having problems with what is a fairly recent laptop and a similar vintage kernel ,and as you mention other things like mounting and wine seem a bit flakey too.

ermn.... happy burning

mike

[vtpup]

Well thanks Mike, though it was less than stunning to forget to label a CD.

On the other hand, accidentally booting a retro CD on a non-retro frugal install was what suddenly caused K3b to work -- and eventually led to the discovery that the older kernel was required to properly work with the cd/dvd drives, both internal, and external. At least on my computer.

If I'd labeled it, I probably would never have tried the retro version -- so sure was I that I didn't need it.

And I can confirm also that Wine version 1.17 definitely works perfectly with a version of Mailwasher I have used for years, while the new kernel Puppy crashed Wine with the same software if you even looked at it wrong.

With the later kernel, the "desktop" flickered noticeably, and if I tried to resize it or move it I crashed. The redraws were messed up and I'd get screen artifacts after working with the program for even a short time.

But under the 4.1.1 retro version, everything was stable and worked without a hitch, just as it had for the last 4 years. Same program, same Wine version, just the difference between the retro and the new version of Puppy 4.1.1. On my computer at least.

I don't know whether this really constitutes a bug because the term "later computer" isn't well defined -- I suppose a 1.8 Ghz pent 4 Thinkpad T30 machine could be considered by some to be an "older" computer, and thus would be expected to use the retro version. I think of it as my own "top of the line" machine

On the other hand, if somebody else with a "newer" computer has similar problems, we could then chalk it up to either a "bug" in Puppy's Pmount routine, or even possibly a bad kernel choice to base Puppy on.

I'm reluctant to say something is a bug right now, if mine is the only computer it has affected in this way. Maybe someone else will find this thread and report another case of the disease, and we can then move it to the bug threads.


ps.

I've been enjoying burning CDs and DVDs of all sorts without a coaster in the carload, using k3b on both the internal and external drives, lately.

Just burned and installed the 4.1.2 retro, as a matter of fact.

OT: Retro killed my LinNWin startup incidentally. I spent a couple of days scratching my head over PSUBDIR addition and removal in menu.lst, and moving the puppy files into and out of subdirectories, until the lightbulb finally clicked on and I changed a reference from sda5 to hda5 in another place in menu.lst. I think I looked at that entry a hundred times without thinking anything was wrong.

Retro uses the hd terminology for ide drives, while the later Linux kernel calls them sd, even if they aren't serial or scsi or whatever the "s" means. Seems like a pointless Linux change, and I'm sure my problem has been repeated many thousands of times elsewhere.

[mikeb]

I think you deserve the golden patience with linux award .

I had similar headaches with gtk 2 versions...older puppies with older software works just fine.

I'm sure at some point the latest software becomes stable but for me 'new' is not always better at least in the beginning.
Glad you can burn now...I use k3b all the time without a hitch.

Hope you had a cool Christmas

regards

Mike

[vtpup]

I hate to reopen this one, but it just occurred to me that there may be another solution to this problem. I personally solved it by switching over from a standard to a retro version (old kernel) on my T30 Thinkpad. Currently Puppy version 4.1.2 retro.

However, poking around tonight in the menu I opened the Puppy Event Manager and noticed that under the "Icon Handler" tab you could uncheck auto-detection of target application.

I wonder if this would have solved the problem with K3b and Pmount fighting for access to a blank DVD?

I have no way of checking this, as I'm fully switched over to the retro version now, and it would take a ton of work to go back. But if someone else is experiencing the symptoms I did, it is something to try out before switching to retro as a solution.

It may not make any difference -- I did notice some other dvd drive problems unrelated to K3b as well back then, and this Event Manager change therefore might not have affected those.

Anyway, just thought I would mention it.