Bug 109235 – hal-0.4.7 breaks cdrecord

• Status: RESOLVED FIXED
• Product: Gentoo Linux

[Description frank 2005-10-13 17:57:28 UTC]

if the hald daemon is running cdrecord fails to burn indicating the device as   
scsibus/target/lun and makes k3b unusable (see this thread: 
http://forums.gentoo.org/viewtopic-p-2305967.html).   
dunno if it depends somehow on my hardware, however upgrading to hal-0.4.8  
solves the problem, so i think it's time to unmask it... 

Reproducible: Always
Steps to Reproduce:
1. 
2.  
3.

[Comment 1 Luis Medinas (RETIRED) 2005-10-15 20:03:46 UTC]

well i'm using hal 0.5.4 i can't reproduce this problem.
It's up to the hal maintainer to it mark stable.

[Comment 2 frank 2005-10-17 06:50:45 UTC]

again: just version 0.4.7 and below are affected, 0.4.8 works fine... 

[Comment 3 Luis Medinas (RETIRED) 2005-11-02 07:01:53 UTC]

gentopia any news on this ?

[Comment 4 Saleem Abdulrasool (RETIRED) 2005-11-28 10:40:57 UTC]

Created a request to mark 0.5.4 stable in portage.

[Comment 5 Doug Goldstein (RETIRED) 2005-12-29 22:41:17 UTC]

metalgod: the issue is marking 0.4.8 as stable by all ARCHES. Not Gentopia's responsiblity. The attached bug should really request 0.4.8 be marked stable first before we go for the new API.

Technically this issue is fixed. The new issue is getting the ARCH teams to mark hal-0.4.8 stable.

[Comment 6 Luis Medinas (RETIRED) 2005-12-30 03:10:22 UTC]

Thanks Doug i'll mark it stable on amd64 asap

Frank if you still have this issue with this newer hal please reopen the bug.

[Comment 7 frank 2005-12-30 04:24:40 UTC]

in the meantime i've upgraded to hal 5.5.1 (because of kde 3.5) and i'm not expeiencing any issue with cdrecord, it just works ;)