You are not logged in.
Not really sure how often, it seems random. I'd say they do it about 50% of the time. Hoping for a fix It has been going on since I installed Arch a month or two ago I figure.
"I refuse to be part of a society that encourages the rampant abuse of its own language." ~ BM
Offline
"Search" is your friend I replied to a similar post 3 days ago -> http://bbs.archlinux.org/viewtopic.php?id=95002
Ryzen 9 5950X, X570S Aorus Pro AX, RX 6600, Arch x86_64
Offline
I did google around a bit, and I found plenty of similar but not relevant problems.
Fun and games with mkinitcpio does seem to be the cure though. At least it hasn't done it to me since the last I rebooted after doing that ... Anyhow, thank you fabertawe.
"I refuse to be part of a society that encourages the rampant abuse of its own language." ~ BM
Offline
Well to be fair I sometimes find it difficult wading through pages and pages of search results looking for that elusive needle. I always try the search here first. Hope it's fixed for you now.
Ryzen 9 5950X, X570S Aorus Pro AX, RX 6600, Arch x86_64
Offline
Apparently the problem remains
"I refuse to be part of a society that encourages the rampant abuse of its own language." ~ BM
Offline
This thread may be ancient, but it's mine and it still isn't solved and giving me more trouble than ever before ... anybody have any new ideas?
"I refuse to be part of a society that encourages the rampant abuse of its own language." ~ BM
Offline
You need to give more information, please.
What DE or WM are you using? What app or apps are you using when the unwanted disk drawer action happens?
Does it occur only after burning, or after any action? Is it only with audio CDs or does it happen with data CDs?
Does 'eject' from the command line give the same behavior?
Last edited by thisoldman (2011-02-21 10:58:24)
Offline
You need to give more information, please.
What DE or WM are you using? What app or apps are you using when the unwanted disk drawer action happens?
Does it occur only after burning, or after any action? Is it only with audio CDs or does it happen with data CDs?
Does 'eject' from the command line give the same behavior?
I figured this, but I didn't know what information to give, but its always just a question away right?
KDE. Usually none, as I tend to eject after I'm finished doing something. It doesn't generally happen after burning if it happens after burning at all.
I don't generally try to eject them if I haven't done anything with them, so I'm not sure. Mostly been handling video DVDs lately, but I've had plenty of issues with other disks in the past if my memory serves me correctly ... though I forget if it was with data CDs, audio CDs, or both.
eject from the command line gives this behavior, as does reaching down and pushing the button.
"I refuse to be part of a society that encourages the rampant abuse of its own language." ~ BM
Offline
It may be a bit of a radical solution (I haven't found anything simpler yet) but in fixing a problem I've been having with the latest udev I also resolved the auto-retract/double eject issues that I've been having for a least the same length of time: https://bbs.archlinux.org/viewtopic.php … 47#p894147
So far, everything works. Even brasero...I can sit here ejecting the drive, closing it with the mount command, ejecting it again ad nauseam.
Offline
It may be a bit of a radical solution (I haven't found anything simpler yet) but in fixing a problem I've been having with the latest udev I also resolved the auto-retract/double eject issues that I've been having for a least the same length of time: https://bbs.archlinux.org/viewtopic.php … 47#p894147
So far, everything works. Even brasero...I can sit here ejecting the drive, closing it with the mount command, ejecting it again ad nauseam.
Sounds very promising - I'll give it a try as soon as I can. It probably isn't a coincidence that my drives are all Samsungs ... SH-223F and SH-S203B.
"I refuse to be part of a society that encourages the rampant abuse of its own language." ~ BM
Offline
Didn't work for me afterall
"I refuse to be part of a society that encourages the rampant abuse of its own language." ~ BM
Offline
I had the same problem and I have found that it is somehow related to udisks-daemon.
If I kill this daemon, everything works fine, but I couldn't find who starts this daemon.
It seems that it is started by dbus automaticaly and it is relate to gtk-gnome environment.
This explains why this hits the kde users occasionaly, and gnome/xcfe users regulary.
Anyway, researching the internet for the solution, I have fount this thread:
http://bugs.gentoo.org/show_bug.cgi?id=319829
and it makes me to review my mkinitcpio.conf file and when I changed the line:
HOOKS="base udev autodetect ide sata filesystems"
into
HOOKS="base udev autodetect sata filesystems"
everything worked perfect.
So give it a try!
Regards.
Offline
And if that fails then there's https://bugs.launchpad.net/ubuntu/+sour … bug/283316. Basically, try running
sysctl -w dev.cdrom.autoclose=0
as root. If it works then add
dev.cdrom.autoclose=0
to /etc/sysctl.conf.
Offline
The sysctl fix helped somewhat, it seems. I'm still having it happen but considerably less frequently.
Something odd I've noticed though, is that sometimes when I push the button to close one of the drives, if I have multiple open then a different one might retract instead. Weird eh?
Last edited by dwidmann (2011-02-26 12:16:02)
"I refuse to be part of a society that encourages the rampant abuse of its own language." ~ BM
Offline
I see also the problem here with auto-close of my DVD drive immediately after pressed the open button.
The sysctl fix helped here also.
So, bug confirmed. Is it due to kernel, udev or hal? All current updates applied.
linux 3.2.5-1
udev 180-1
hal 0.5.14-6
Offline
Not trolling, just commenting:
The sysctl fix worked for me. Thanks.
@k0Do:
udev has been replaced as of early June, so it's not there.
Offline