Bugzilla – Bug 149436
k3b can`t see burn device as user
Last modified: 2007-02-16 09:23:53 UTC
I tested it on two computers x86-32 x86-64 with same result K3b complain about cdrdao #145214 And then do not see any device for reading or writing. Everything work as root.
cdrecord -scanbus outputs something?
$cdrecord -scanbus Cdrecord-Clone 2.01 (i686-suse-linux) Copyright (C) 1995-2004 Jörg Schilling Note: This version is an unofficial (modified) version Note: and therefore may have bugs that are not present in the original. Note: Please send bug reports or support requests to http://www.suse.de/feedback Note: The author of cdrecord should not be bothered with problems in this version. cdrecord: Invalid or incomplete multibyte or wide character. Cannot open SCSI driver. cdrecord: For possible targets try 'cdrecord -scanbus'. Make sure you are root. cdrecord: For possible transport specifiers try 'cdrecord dev=help' $sudo cdrecord -scanbus Cdrecord-Clone 2.01 (i686-suse-linux) Copyright (C) 1995-2004 Jörg Schilling Note: This version is an unofficial (modified) version Note: and therefore may have bugs that are not present in the original. Note: Please send bug reports or support requests to http://www.suse.de/feedba Note: The author of cdrecord should not be bothered with problems in this versn. Linux sg driver version: 3.5.33 Using libscg version 'schily-0.8'. cdrecord: Warning: using inofficial libscg transport code version (okir@suse.dscsi-linux-sg.c-1.83-resmgr-patch '@(#)scsi-linux-sg.c 1.83 04/05/20 Copyrigh1997 J. Schilling'). scsibus0: 0,0,0 0) 'ATA ' 'ST3160827AS ' '3.42' Disk 0,1,0 1) * 0,2,0 2) * 0,3,0 3) * 0,4,0 4) * 0,5,0 5) * 0,6,0 6) * 0,7,0 7) *
looks like a underlying problem
Is it a scsi/sata burner? might be #144843 then. If not please attach output of 'lshal' and 'resmgr dump'.
It is pata burner. I don`t think it is related to bug #144843.
Created attachment 67241 [details] lshal and resmngr dump output
looks like resmgr was started after hal. first boot after install by any chance (#145934)? restarting hal should fix the problem.
rchal restart fix the problem. It isn`t first boot after install But one of duplicite bug of #145934 is also mine :) I
So how to reproduce? We now know the problem but not where it comes from.
I am not sure how to reproduce, but i think this problem will be here again after restart. I will tell you tomorrow.
I reboot today and k3b again not see any device. Is this problem on all computers with 10.1b3 ?
Is this bug fixed in 10.1 final?
On my computer(i386) it look like it is fixed. But on another x86-64 machine this problem persist.
I can't burn DVD because not have ... some memorry(?) sorry my english!
Does this probem still persist? Dir a resmgr restart fix it on the x86-64 machine also?
I cannot reproduce this problem on openSUSE 10.2 (as everything work fine). So i am closing this as WONTFIX