When attaching or automounting external firewire hard drive, system prompts for root password. Device chown is set to non-root user. F17 did not have this issue. udisks2, not udisks.
Created attachment 76255 [details] udisks2 dump
System is Fedora 18 udisks2-2.0.1-1.fc18.x86_64 https://bugzilla.redhat.com/show_bug.cgi?id=909010
(In reply to comment #1) > Created attachment 76255 [details] > udisks2 dump For some reason udisks does not know about /dev/sdb, /dev/sdc, /dev/sdd so this is why the root password is requested. Please attach the output of the command 'udevadm info --export-db' run as root. My guess is that there's something wrong with the firewire drivers but can't tell without more information.
Also, if you're using selinux, please try putting it in permissive mode. I can't fix bugs in the selinux stuff and it tends to interact badly with things it shouldn't.
Created attachment 76287 [details] udevadm
(In reply to comment #5) > Created attachment 76287 [details] > udevadm Yeah, look at /dev/sdb, a lot of information is missing and that's why this is happening. Looking at the RH bug comment 10 - https://bugzilla.redhat.com/show_bug.cgi?id=909010#c10 - it definitely looks like selinux is interfering. Please do try with selinux in permissive mode and see if the problems go away. It would also help if you could include debug info. From a root shell, just do # udisksd --no-replace and include the error/warning messages when hotplugging the device. Thanks.
(In reply to comment #6) > (In reply to comment #5) > > Created attachment 76287 [details] > > udevadm > > Yeah, look at /dev/sdb, a lot of information is missing and that's why this > is happening. Looking at the RH bug comment 10 - > https://bugzilla.redhat.com/show_bug.cgi?id=909010#c10 - it definitely looks > like selinux is interfering. Please do try with selinux in permissive mode > and see if the problems go away. > > It would also help if you could include debug info. From a root shell, just > do > > # udisksd --no-replace > > and include the error/warning messages when hotplugging the device. Thanks. I don't have udisksd: bash: udisksd: command not found
(In reply to comment #7) > (In reply to comment #6) > > (In reply to comment #5) > > > Created attachment 76287 [details] > > > udevadm > > > > Yeah, look at /dev/sdb, a lot of information is missing and that's why this > > is happening. Looking at the RH bug comment 10 - > > https://bugzilla.redhat.com/show_bug.cgi?id=909010#c10 - it definitely looks > > like selinux is interfering. Please do try with selinux in permissive mode > > and see if the problems go away. > > > > It would also help if you could include debug info. From a root shell, just > > do > > > > # udisksd --no-replace > > > > and include the error/warning messages when hotplugging the device. Thanks. > > I don't have udisksd: > > bash: udisksd: command not found It's in /usr/lib/udisks2/udisksd I think (use things like 'rpm -ql udisks2|grep udisksd' to find out in the future). But, as I said, I'm more interested in knowing if it works in selinux permissive mode. Just run 'setenforce 0' as root and try hotplugging the device to find out.
After talking to the udev maintainer on IM, he pointed me to this bug https://bugzilla.redhat.com/show_bug.cgi?id=909826 which explains the problem that you're also seeing. So this is a problem with selinux, closing NOTOURBUG. In the future, before filing a bug upstream, please always try to see if the bug happens with selinux turned off. If it doesn't, the bug is with selinux or fedora. Thanks.
(In reply to comment #9) > After talking to the udev maintainer on IM, he pointed me to this bug > > https://bugzilla.redhat.com/show_bug.cgi?id=909826 > > which explains the problem that you're also seeing. So this is a problem > with selinux, closing NOTOURBUG. In the future, before filing a bug > upstream, please always try to see if the bug happens with selinux turned > off. If it doesn't, the bug is with selinux or fedora. Thanks. I set selinux to permissive mode and the firewire hdd issue persists. Suggestions. I don't get the errors from bug 909826 too. Only that one time. Suggestions?
(In reply to comment #10) > (In reply to comment #9) > > After talking to the udev maintainer on IM, he pointed me to this bug > > > > https://bugzilla.redhat.com/show_bug.cgi?id=909826 > > > > which explains the problem that you're also seeing. So this is a problem > > with selinux, closing NOTOURBUG. In the future, before filing a bug > > upstream, please always try to see if the bug happens with selinux turned > > off. If it doesn't, the bug is with selinux or fedora. Thanks. > > I set selinux to permissive mode and the firewire hdd issue persists. > Suggestions. I don't get the errors from bug 909826 too. Only that one > time. Suggestions? I'm sorry permissive mode didn't fix it, sometimes selinux interferes even in permissive mode and sometimes even too when turned off completely. In this case the problem is that udev drops an uevent on the floor because libselinux returns an error. I would wait for the bugfix to selinux and systemd/udev referenced in https://bugzilla.redhat.com/show_bug.cgi?id=909826 to land and try again. I wish there was something I could do to help but the problem really isn't in udisks cf. https://bugzilla.redhat.com/show_bug.cgi?id=909010#c10
(In reply to comment #11) > (In reply to comment #10) > > (In reply to comment #9) > > > After talking to the udev maintainer on IM, he pointed me to this bug > > > > > > https://bugzilla.redhat.com/show_bug.cgi?id=909826 > > > > > > which explains the problem that you're also seeing. So this is a problem > > > with selinux, closing NOTOURBUG. In the future, before filing a bug > > > upstream, please always try to see if the bug happens with selinux turned > > > off. If it doesn't, the bug is with selinux or fedora. Thanks. > > > > I set selinux to permissive mode and the firewire hdd issue persists. > > Suggestions. I don't get the errors from bug 909826 too. Only that one > > time. Suggestions? > > I'm sorry permissive mode didn't fix it, sometimes selinux interferes even > in permissive mode and sometimes even too when turned off completely. In > this case the problem is that udev drops an uevent on the floor because > libselinux returns an error. I would wait for the bugfix to selinux and > systemd/udev referenced in > https://bugzilla.redhat.com/show_bug.cgi?id=909826 to land and try again. > > I wish there was something I could do to help but the problem really isn't > in udisks cf. https://bugzilla.redhat.com/show_bug.cgi?id=909010#c10 David, The firewire issue is definitely udisks2 related. What can be done to fix it? The usb issue is completely separate.
(In reply to comment #12) > The firewire issue is definitely udisks2 related. What can be done to fix > it? The usb issue is completely separate. I wouldn't be so sure that it's "definitely udisks2 related" - in fact, I think it's not. I need the output of 'udisksctl dump' [1] on a system where the selinux bug you ran into earlier has been fixed. Generally see http://www.freedesktop.org/wiki/Software/udisks for how to best report bugs and what information to include.
Created attachment 76722 [details] udisksctl monitor
Created attachment 76723 [details] gvfs-mount -oi
Created attachment 76724 [details] udisksctl dump
Created attachment 76725 [details] udevadm info --export-db
Created attachment 76726 [details] mountinfo
(In reply to comment #13) > (In reply to comment #12) > > The firewire issue is definitely udisks2 related. What can be done to fix > > it? The usb issue is completely separate. > > I wouldn't be so sure that it's "definitely udisks2 related" - in fact, I > think it's not. I need the output of 'udisksctl dump' [1] on a system where > the selinux bug you ran into earlier has been fixed. Generally see > http://www.freedesktop.org/wiki/Software/udisks for how to best report bugs > and what information to include. The selinux bug has been fixed. I followed the link guide and uploaded everything that pertained to my issue. udisks2-2.0.1-1.fc18.x86_64 gvfs-1.14.2-3.fc18.x86_64 libatasmart-0.19-3.fc18.x86_64
(In reply to comment #16) > Created attachment 76724 [details] > udisksctl dump This is very useful and immediately helped solve the problem. This patch should fix it: http://cgit.freedesktop.org/udisks/commit/?id=b841e30a98459816dfc49a735d3db4355a88edcd This patch will be in udisks 2.1.1. For Fedora, I would suggest asking the Fedora maintainer to include it in the relevant versions. Thanks.
(In reply to comment #20) > (In reply to comment #16) > > Created attachment 76724 [details] > > udisksctl dump > > This is very useful and immediately helped solve the problem. This patch > should fix it: > > http://cgit.freedesktop.org/udisks/commit/ > ?id=b841e30a98459816dfc49a735d3db4355a88edcd > > This patch will be in udisks 2.1.1. For Fedora, I would suggest asking the > Fedora maintainer to include it in the relevant versions. Thanks. Thanks David for all your help.
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.