View previous topic :: View next topic |
Author |
Message |
cptmorgan Tux's lil' helper
Joined: 28 Jan 2004 Posts: 129 Location: California
|
Posted: Mon May 09, 2005 6:25 pm Post subject: k3b locks ups... amd64 issue ? |
|
|
For some reason when I try to burn a cd image or click burn for any type of cd project, k3b locks up completely. This happens with stable and unstable. Anyone else have these issues? |
|
Back to top |
|
|
robnotts Guru
Joined: 15 Mar 2004 Posts: 405 Location: Nottingham, UK
|
Posted: Mon May 09, 2005 7:28 pm Post subject: |
|
|
Can't say I have... try starting k3b from the command line and dump its output to the console? Might be a clue there.
Check your cflags to see if anything funny is in there?
Rob. _________________ ---
Gentoo Phenom][ X4 955 on AMD790 + Geforce 220GT 8GB/1.75TB (Desktop)
+ MythTV (3xFreeview,1xFreesat HD) on 1080p
Gentoo Turion64 X2 Geforce 6150 2GB/120GB (Laptop) |
|
Back to top |
|
|
cptmorgan Tux's lil' helper
Joined: 28 Jan 2004 Posts: 129 Location: California
|
Posted: Mon May 09, 2005 7:38 pm Post subject: |
|
|
CFLAGS="-march=athlon64 -O2 -pipe"
and k3b doesnt dump anything when the error occurs... i just have to kill the process and restart it but it is reproducible every time |
|
Back to top |
|
|
spielc Guru
Joined: 20 Apr 2004 Posts: 452
|
Posted: Tue May 10, 2005 12:09 pm Post subject: |
|
|
cptmorgan wrote: | CFLAGS="-march=athlon64 -O2 -pipe"
and k3b doesnt dump anything when the error occurs... i just have to kill the process and restart it but it is reproducible every time |
reemerge k3b with the USE-Flag debug enabled and after that start it again from the console it should dump debug msgs now |
|
Back to top |
|
|
cptmorgan Tux's lil' helper
Joined: 28 Jan 2004 Posts: 129 Location: California
|
Posted: Tue May 10, 2005 6:00 pm Post subject: |
|
|
This is what happens when I click burn cd image...
Code: |
k3b: WARNING: KGenericFactory: instance requested but no instance name or about data passed to the constructor!
k3b: (K3b::cutToWidth) not able to cut text to 1!
k3b: linux kernel version: 2.6.11-gentoo-r7
k3b: linux kernel version: 2.6.11-gentoo-r7
k3b: linux kernel version: 2.6.11-gentoo-r7
k3b: linux kernel version: 2.6.11-gentoo-r7
k3b: (K3bCore) System problems:
k3b: - none -
|
And this is what happens when clicking burn after adding 1 song to a audio project...
Code: |
k3b: WARNING: KGenericFactory: instance requested but no instance name or about data passed to the constructor!
k3b: (K3b::cutToWidth) not able to cut text to 1!
k3b: linux kernel version: 2.6.11-gentoo-r7
k3b: linux kernel version: 2.6.11-gentoo-r7
k3b: linux kernel version: 2.6.11-gentoo-r7
k3b: linux kernel version: 2.6.11-gentoo-r7
k3b: (K3bCore) System problems:
k3b: - none -
k3b: (K3bProjectManager) adding doc
kdecore (KAction): WARNING: KActionCollection::KActionCollection( QObject *parent, const char *name, KInstance *instance )
k3b: (K3bDeviceManager) request for empty device!
k3b: (K3bWaveDecoder) /home/cptmorgan/_media_/mp3/archive/10_Ft._Ganja_Plant-Hillside_Airstrip-2001-RAC/01.long_time_ago-rac.mp3: not a RIFF file.
k3b: (K3bFLACDecoder) /home/cptmorgan/_media_/mp3/archive/10_Ft._Ganja_Plant-Hillside_Airstrip-2001-RAC/01.long_time_ago-rac.mp3: not a FLAC file
k3b: (K3bMad::findNextHeader) error: reserved sample frequency value
k3b: (K3bMad) found first header at 4387
k3b: (K3bMad) cleanup at offset: Input file at: 45347 Input file size: 7485149 stream pos: 6894
k3b: (K3bAudioDoc) using K3bMadDecoderFactory for decoding of /home/cptmorgan/_media_/mp3/archive/10_Ft._Ganja_Plant-Hillside_Airstrip-2001-RAC/01.long_time_ago-rac.mp3
k3b: (K3bAudioDoc) slotDetermineTrackStatus()
k3b: (K3bAudioDoc) AudioTrackStatusThread not running.
k3b: (K3bAudioDoc) starting AudioTrackStatusThread for /home/cptmorgan/_media_/mp3/archive/10_Ft._Ganja_Plant-Hillside_Airstrip-2001-RAC/01.long_time_ago-rac.mp3
k3b: (AudioTrackStatusThread) run
k3b: (K3bMad::findNextHeader) error: reserved sample frequency value
k3b: (K3bMad) found first header at 4387
k3b: (K3bMadDecoder::countFrames)
k3b: (K3bMadDecoder) length of track 311.719
k3b: (K3bMad) cleanup at offset: Input file at: 7485149 Input file size: 7485149 stream pos: 7485012
k3b: (K3bMadDecoder::countFrames) end
k3b: (K3bSongManager) Search container: /home/cptmorgan/_media_/mp3/archive/10_Ft._Ganja_Plant-Hillside_Airstrip-2001-RAC
k3b: (K3bSongManager) Search song: 01.long_time_ago-rac.mp3
k3b: No container found!
k3b: (AudioTrackStatusThread) finished
k3b: (K3bThreadJob) waiting for the thread to finish.
k3b: (K3bThreadJob) thread finished.
k3b: (K3bAudioDoc) slotDetermineTrackStatus()
k3b: (K3bAudioDoc) AudioTrackStatusThread not running.
k3b: (K3bAudioDoc) slotDetermineTrackStatus() end
|
Any Ideas ?? |
|
Back to top |
|
|
cptmorgan Tux's lil' helper
Joined: 28 Jan 2004 Posts: 129 Location: California
|
Posted: Tue May 17, 2005 1:15 am Post subject: |
|
|
Sorry for the bump but I havent had any luck with this problem. Ive tried unstable versions on kdelibs qt and k3b with no prevail. Anyone have any ideas? |
|
Back to top |
|
|
longtallugly Tux's lil' helper
Joined: 27 Mar 2003 Posts: 83 Location: iowa
|
Posted: Mon May 23, 2005 12:50 am Post subject: |
|
|
any luck with this yet? i'm having the same problem, and perusing the forums for an answer... |
|
Back to top |
|
|
crazycat l33t
Joined: 26 Aug 2003 Posts: 838 Location: Hamburg, Germany
|
Posted: Mon May 23, 2005 5:18 am Post subject: |
|
|
Can k3b find your devices? Try burning with growisofs. It will probably output more stuff if it's not k3b related. Do you have right permissions on your wirting devices/ have you run k3bsetup? Try also posting in multimedia forum. |
|
Back to top |
|
|
cptmorgan Tux's lil' helper
Joined: 28 Jan 2004 Posts: 129 Location: California
|
Posted: Mon May 23, 2005 5:15 pm Post subject: |
|
|
crazycat wrote: | Can k3b find your devices? Try burning with growisofs. It will probably output more stuff if it's not k3b related. Do you have right permissions on your wirting devices/ have you run k3bsetup? Try also posting in multimedia forum. |
I ended up going back to x86 until amd64 has stronger support.... not just because of k3b but other issues. Hopefully I dont have this problem when I go back to amd64 |
|
Back to top |
|
|
|