Bug 1380149
| Summary: | Gnome-disk-utility not responding any mount function for any type of disk | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Onuralp SEZER <thunderbirdtr> |
| Component: | gnome-disk-utility | Assignee: | David King <amigadave> |
| Status: | CLOSED DUPLICATE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 25 | CC: | amigadave, bugzilla, kparal, zeeshanak |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2016-10-04 12:01:30 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Description
Onuralp SEZER
2016-09-28 19:00:03 UTC
Might constitute basic functionality. cc'ing kparal see what he thinks, and maybe he gets around to reproducing it faster than me. I would like to add NTFS/FAT and other type disk also not auto-mount + UI is responding nothing. All I can see is just I plugged a disk and show the size and type of it in "journalctl" but nothing to show about mount or when I opened and click moount in utility This could be bug 1377113. See if you're getting an AVC in the journal near the time you're trying to mount; check the above bug if the AVCs are the same. Or also test by rebooting with enforcing=0. If it still happens, then you should propose this bug as a final blocker. I didn't see any SELinux warning but I disabled, then I tried to mount but now It's not even showing disk anymore on "/dev" that was also happened before Selinux working. Dmesg logs, That's Fedora 25 updated dmesg logs about my external NTFS disk 147.022405] usb 1-3: new high-speed USB device number 7 using ehci-pci [ 147.130390] usb 1-3: device descriptor read/64, error 18 [ 147.341449] usb 1-3: device descriptor read/64, error 18 [ 147.554373] usb 1-3: new high-speed USB device number 8 using ehci-pci [ 147.660312] usb 1-3: device descriptor read/64, error 18 [ 147.868341] usb 1-3: device descriptor read/64, error 18 [ 148.074393] usb 1-3: new high-speed USB device number 9 using ehci-pci [ 148.090564] usb 1-3: Invalid ep0 maxpacket: 9 [ 148.196382] usb 1-3: new high-speed USB device number 10 using ehci-pci [ 148.267968] usb 1-3: Invalid ep0 maxpacket: 9 [ 148.269419] usb usb1-port3: unable to enumerate USB device [ 148.498365] usb 3-1: new full-speed USB device number 6 using uhci_hcd [ 148.622400] usb 3-1: device descriptor read/64, error 18 [ 148.843361] usb 3-1: device descriptor read/64, error 18 [ 149.050360] usb 3-1: new full-speed USB device number 7 using uhci_hcd [ 149.162361] usb 3-1: device descriptor read/64, error 18 [ 149.380435] usb 3-1: device descriptor read/64, error 18 [ 149.586354] usb 3-1: new full-speed USB device number 8 using uhci_hcd [ 149.604281] usb 3-1: Invalid ep0 maxpacket: 9 [ 149.709365] usb 3-1: new full-speed USB device number 9 using uhci_hcd [ 149.725648] usb 3-1: Invalid ep0 maxpacket: 9 [ 149.726649] usb usb3-port1: unable to enumerate USB device But If I plugged to Fedora 24 on the same laptop and same disk; Selinux enable, no config needed just mount and done. [82535.411732] usb-storage 4-2:1.0: USB Mass Storage device detected [82535.412003] scsi host8: usb-storage 4-2:1.0 [82536.414760] scsi 8:0:0:0: Direct-Access WD My Passport 0740 1007 PQ: 0 ANSI: 6 [82536.415187] scsi 8:0:0:1: Enclosure WD SES Device 1007 PQ: 0 ANSI: 6 [82536.428351] sd 8:0:0:0: [sdc] 1953458176 512-byte logical blocks: (1.00 TB/931 GiB) [82536.428357] sd 8:0:0:0: Attached scsi generic sg3 type 0 [82536.428649] sd 8:0:0:0: [sdc] Write Protect is off [82536.428655] sd 8:0:0:0: [sdc] Mode Sense: 47 00 10 08 [82536.428914] sd 8:0:0:0: [sdc] No Caching mode page found [82536.428920] sd 8:0:0:0: [sdc] Assuming drive cache: write through [82536.430845] scsi 8:0:0:1: Attached scsi generic sg4 type 13 [82536.754466] sdc: sdc1 [82536.756190] sd 8:0:0:0: [sdc] Attached SCSI disk [82536.757086] ses 8:0:0:1: Attached Enclosure device In both case I used usb3 but If I use usb2 on F25 , It can show disk probably except one more different warning but disk mounted probably and I can see the content without problem. Warning message ; scsi host2: runtime PM trying to activate child device host2 but parent (1-3:1.0) is not active For testing purpose I installed F25 kernel on F24 system and It was working too so we can also say It is not kernel related problem too. Kernel I used ; 4.8.0-0.rc8.git3.1.fc25.x86_64 After seeing "usb usb3-port1: unable to enumerate USB device", can't this be related to bug 1381039? If it works with USB2 and not with USB3, this doesn't seem to be a gnome-disks issue, or either kernel or some layer above it (udisks, etc). I'd guess kernel, but it is interesting that installing the F25 kernel on F24 system exhibits no such issues. So, I reproduced the issue with gnome-disks in a VM, it really can't unlock LUKS. Journal contains:
Oct 04 07:51:07 localhost.localdomain audit[957]: USER_AVC pid=957 uid=81 auid=4294967295 ses=4294967295 subj=system_u:system_r:system_dbusd_t:s0-s0:c0.c1023 msg='avc: denied { send_msg } for msgtype=method_return dest=:1.35 spid=1011 tpid=1489 scontext=system_u:system_r:policykit_t:s0 tcontext=system_u:system_r:devicekit_t:s0 tclass=dbus
exe="/usr/bin/dbus-daemon" sauid=81 hostname=? addr=? terminal=?'
However, after updating to selinux-policy-3.13.1-216.fc25 the issue disappears. So the main cause is really selinux, and it's already resolved.
I'm going to make this a duplicate of bug 1377113. I suggest filing new bugs about any other issues (usb device enumeration, etc). But I'd wait until https://bodhi.fedoraproject.org/updates/FEDORA-2016-b596fd5579 is pushed stable and a new compose is built with it.
*** This bug has been marked as a duplicate of bug 1377113 ***
|