k3b crash!!

vredfreak · 2004-12-01 00:54:03

I'm using Arch Linux, 2.6.9 kernel.

I have a cdburner and a dvdburner, which k3b has never had problems recognizing or using on other distros. When I start k3b, it almost immediately crashes. When run from the command line, this is the output.

Any suggestions? Thanks.

k3b: (K3bPluginFactory) creating K3bPluginFactory.
k3b: (K3bPluginFactory) creating K3bPluginFactory.
k3b: (K3bPluginFactory) creating K3bPluginFactory.
k3b: (K3bPluginFactory) creating K3bPluginFactory.
k3b: (K3bPluginFactory) creating K3bPluginFactory.
k3b: (K3bPluginFactory) creating K3bPluginFactory.
k3b: (K3bPluginFactory) creating K3bPluginFactory.
k3b: (K3bExternalBinManager) Cdrecord 2.1 features: gracetime, overburn, cdtext, clone, tao, cuefile, suidroot, plain-atapi, hacked-atapi
k3b: (K3bExternalBinManager) 2 1 -1 seems to be cdrecord version >= 1.11a02, using burnfree instead of burnproof
k3b: (K3bExternalBinManager) seems to be cdrecord version >= 1.11a31, support for Just Link via burnfree driveroption
k3b: /dev/hdd resolved to /dev/ide/host0/bus1/target1/lun0/cd
k3b: /dev/ide/host0/bus1/target1/lun0/cd is block device (64)
k3b: /dev/ide/host0/bus1/target1/lun0/cd seems to be cdrom
k3b: (K3bCdDevice) /dev/ide/host0/bus1/target1/lun0/cd: init()
k3b: (K3bCdDevice) /dev/ide/host0/bus1/target1/lun0/cd: GET_CONFIGURATION length: 164.
k3b: (K3bCdDevice) /dev/ide/host0/bus1/target1/lun0/cd feature: Core
k3b: (K3bCdDevice) /dev/ide/host0/bus1/target1/lun0/cd feature: Morphing
k3b: (K3bCdDevice) /dev/ide/host0/bus1/target1/lun0/cd feature: Removable Medium
k3b: (K3bCdDevice) /dev/ide/host0/bus1/target1/lun0/cd feature: Random Readable
k3b: (K3bCdDevice) /dev/ide/host0/bus1/target1/lun0/cd feature: Multi-Read
k3b: (K3bCdDevice) /dev/ide/host0/bus1/target1/lun0/cd feature: CD Read
k3b: (K3bCdDevice) /dev/ide/host0/bus1/target1/lun0/cd feature: DVD Read
k3b: (K3bCdDevice) /dev/ide/host0/bus1/target1/lun0/cd feature: Incremental Streaming Writable
k3b: (K3bCdDevice) /dev/ide/host0/bus1/target1/lun0/cd feature: Formattable
k3b: (K3bCdDevice) /dev/ide/host0/bus1/target1/lun0/cd feature: Restricted Overwrite
k3b: (K3bCdDevice) /dev/ide/host0/bus1/target1/lun0/cd feature: CD Track At Once
k3b: (K3bCdDevice) /dev/ide/host0/bus1/target1/lun0/cd feature: CD Mastering
k3b: (K3bCdDevice) /dev/ide/host0/bus1/target1/lun0/cd feature: Power Management
k3b: (K3bCdDevice) /dev/ide/host0/bus1/target1/lun0/cd feature: CD Audio analogplay
k3b: (K3bCdDevice) /dev/ide/host0/bus1/target1/lun0/cd feature: Timeout
k3b: (K3bCdDevice) /dev/ide/host0/bus1/target1/lun0/cd feature: DVD-CSS
k3b: (K3bCdDevice) /dev/ide/host0/bus1/target1/lun0/cd feature: Read Time Streaming
k3b: (K3bCdDevice) /dev/ide/host0/bus1/target1/lun0/cd feature: Logical Unit Serial Number
k3b: (K3bCdDevice::CdDevice) /dev/ide/host0/bus1/target1/lun0/cd: dataLen: 60
k3b: (K3bCdDevice::ScsiCommand) failed: fd: 11
k3b: command: MODE SELECT (55)
k3b: errorcode: 38
k3b: sense key: NO SENSE (2)
k3b: asc: 26
k3b: ascq: 0
k3b: (K3bCdDevice::ScsiCommand) failed: fd: 11
k3b: command: READ DVD STRUCTURE (ad)
k3b: errorcode: 38
k3b: sense key: NO SENSE (2)
k3b: asc: 30
k3b: ascq: 2
k3b: (K3bCdDevice::CdDevice) Unable to read DVD structure.
k3b: (K3bCdDevice::CdDevice) /dev/ide/host0/bus1/target1/lun0/cd: Number of supported write speeds via 2A: -1
terminate called after throwing an instance of 'std::bad_alloc'
what(): St9bad_alloc
KCrash: Application 'k3b' crashing...

P.S. This happens as both user and root.

sarah31 · 2004-12-01 02:09:45

what were you trying to do?

I ask because i was trying to use mkisofs to generate a dvd format image last night and despite being able to do so about half a day earlier i was getting seg faults.

vredfreak · 2004-12-01 08:47:21

I was going to burn an audio cd, but it doesn't even make it past the splash screen. I'm not sure, but it seems to be crashing as it tries to read my burners.

Michel · 2004-12-02 14:46:25

Maybe you're using a 2.6.8.x-kernel? Those kernels have problems with burners I believe ...
You can check your kernel-version using the command "uname -a" on the command-line.

Michel

vredfreak · 2004-12-03 00:36:24

Actually, I'm using 2.6.9 kernel. The burning issues with the .8 kernel had something to do with not being able to burn as users other than root. I can't even get k3b to load, as a user or as root.

dp · 2004-12-03 02:16:29

the code for recognizing the drives was rewritten for kernel >2.6.9 and therefore the newest k3b uses new code for detecting drives ... if you tried on your other distros older versions of k3b and it worked, it is most probable this the trouble

from the output, you should start trying to find out, what this means:

k3b: (K3bCdDevice::ScsiCommand) failed: fd: 11
k3b: command: MODE SELECT (55)
k3b: errorcode: 38

and i would recommend, that you contact the k3b guys for this

vredfreak · 2004-12-03 10:52:01

YES!

Thanks for the info. On the k3b homepage it discusses its problems with hardware detection and the .9 kernel. Unfornately, it recommends sticking to 2.6.7 instead of being able to fix the problem with any sure-fire results.

I guess it's time to make a decision: change kernel or quit using k3b.

But I use k3b mostly to burn my dvd's, and they mention the fact that this is also a problem of dvd+rw-tools. That may make my decision a little easier.

Thanks for the help.

Stinky · 2004-12-04 06:28:24

Same problem here. I had to go back to 2.6.7 kernel. At least until I come up with another burning front end I like. I've been using K3B for a couple of years now and have gotten quite use to it. Anybody got any suggestions?

dp · 2004-12-04 16:10:29

Stinky wrote:

Same problem here. I had to go back to 2.6.7 kernel. At least until I come up with another burning front end I like. I've been using K3B for a couple of years now and have gotten quite use to it. Anybody got any suggestions?

best way would be to support k3b-people (e.g. by trying cvs version)

Stinky · 2004-12-04 17:11:43

That's not the worst idea I've heard all day. I think I will.

scarecrow · 2004-12-04 20:14:19

Before going back to 2.6.7 (which ain't such a bad idea after all...) did you try first emptying your CD-trays and running "kcmshell k3bsetup2" as root, and undoing your cdrecord suid root settings?
Or simply open a root console, type
chmod a-s /usr/bin/cdrecord
...and then ignore the message K3B pops up about cdrecord not running suid root.
And of course you can always use CDRDAO for burning CD's, which is not affected.
K3B does work here with 2.6.9 (built from current CVS- some cool new features have been added), although with some annoying quirks.
More than that, burning CD's and DVD's under VMware works perfectly with 2.6.7, while with 2.6.9 you'll create a very nice coaster collection.

vredfreak · 2004-12-04 22:37:57

My problem with the .9 kernel is that k3b won't load (or k3bsetup). It crashes while trying to read my drives (not sure why setup does, though). But as I said earlier, dvd+rw-tools also seems to have this problem with some devices and the .9 kernel, which of course will affect any front-end program that uses it on my system.

Am I off base here? I'm certainly no expert.

Besides, the .7 has never let me down on any distro that I've used it on. For any reason.

Update:

After rereading the info on k3b's website, I am off base on the dvd+rw-tools as that seems to relate only to external devices.

As for my k3b issue, even changing the cdrecord permissions did nothing for me. I also installed Mandrake 10.1 Official (2.6.9 kernel) and get the same problem. The funny thing is that k3b's 2.6.9 kernel problems seem to have something to do with reading scsi, but both of my drives are IDE/ATAPI. I've tried with and without scsi-emulation.

Oh well, I like 2.6.7 anyway. Thinking of giving Aurox a shot on my free disk space to see how I like it.

scarecrow · 2004-12-09 21:17:02

FYI 2.6.9 isn't a disaster, as 2.6.8.X was, but it still has some unresolved issues when coming to CD/DVD burning... more info here:
http://k3b.plainblack.com/index.pl/news2

WillySilly · 2005-01-14 03:10:18

I had the same problem, on 2.6.10, and what i found out is that i had to run k3b as root

colnago · 2005-01-14 03:46:55

I can use k3b w/o being root. It seems much better than with 2.6.8.x and 2.6.9 kernels. Maybe there is a problem with your k3b config that is the issue. Try removing ~/.kde/share/config/k3brc (and k3b.eventsrc)

scarecrow · 2005-01-18 15:58:56

The stock 2.6.10 Arch kernel and K3B 0.11.18 seem to work fine here, either as user or as root. Please check if your (IDE?) burners operate in DMA mode, and not PIO4.

Arch Linux

#1 2004-12-01 00:54:03

k3b crash!!

#2 2004-12-01 02:09:45

Re: k3b crash!!

#3 2004-12-01 08:47:21

Re: k3b crash!!

#4 2004-12-02 14:46:25

Re: k3b crash!!

#5 2004-12-03 00:36:24

Re: k3b crash!!

#6 2004-12-03 02:16:29

Re: k3b crash!!

#7 2004-12-03 10:52:01

Re: k3b crash!!

#8 2004-12-04 06:28:24

Re: k3b crash!!

#9 2004-12-04 16:10:29

Re: k3b crash!!

#10 2004-12-04 17:11:43

Re: k3b crash!!

#11 2004-12-04 20:14:19

Re: k3b crash!!

#12 2004-12-04 22:37:57

Re: k3b crash!!

#13 2004-12-09 21:17:02

Re: k3b crash!!

#14 2005-01-14 03:10:18

Re: k3b crash!!

#15 2005-01-14 03:46:55

Re: k3b crash!!

#16 2005-01-18 15:58:56

Re: k3b crash!!

Board footer