[opensuse] Automount of USB devices stopped working
Hello, after upgrade from 13.1 to 13.2 automounting of USB disks in KDE stopped working. Manual mounting works. KDE sometimes shows prompt for root password. It then allows to mount the disk within KDE. Unmounting then doesn't require root password. Autofs is running (and I haven't touched config files), although „systemctl status autofs.service“ says: „automount[22123]: lookup_init:139: lookup(yp): map auto.master: Local domain name not set“. I don't know how relevant this is for the problem. In KDE Config Centre | Removable devices I have for all devices checked automounting. But it doesn't have any effect... Dmesg shows: [39222.693189] usb 3-3: new high-speed USB device number 16 using xhci_hcd [39222.859722] usb 3-3: New USB device found, idVendor=0951, idProduct=1625 [39222.859729] usb 3-3: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [39222.859732] usb 3-3: Product: DT 101 II [39222.859735] usb 3-3: Manufacturer: Kingston [39222.859737] usb 3-3: SerialNumber: 001372982D3DA9C096330076 [39222.860367] usb-storage 3-3:1.0: USB Mass Storage device detected [39222.860734] scsi18 : usb-storage 3-3:1.0 [39223.863680] scsi 18:0:0:0: Direct-Access Kingston DT 101 II 1.00 PQ: 0 ANSI: 2 [39223.864060] sd 18:0:0:0: Attached scsi generic sg3 type 0 [39223.864444] sd 18:0:0:0: [sdc] 31277056 512-byte logical blocks: (16.0 GB/14.9 GiB) [39223.864813] sd 18:0:0:0: [sdc] Write Protect is off [39223.864821] sd 18:0:0:0: [sdc] Mode Sense: 23 00 00 00 [39223.865160] sd 18:0:0:0: [sdc] No Caching mode page found [39223.865165] sd 18:0:0:0: [sdc] Assuming drive cache: write through [39223.966081] sdc: sdc1 [39223.967376] sd 18:0:0:0: [sdc] Attached SCSI removable disk [39235.643843] usb 3-3: USB disconnect, device number 16 [39243.309729] usb 3-3: new high-speed USB device number 17 using xhci_hcd [39243.474636] usb 3-3: New USB device found, idVendor=125f, idProduct=a93a [39243.474644] usb 3-3: New USB device strings: Mfr=1, Product=3, SerialNumber=2 [39243.474647] usb 3-3: Product: Portable HDD SH93 [39243.474650] usb 3-3: Manufacturer: ADATA [39243.474653] usb 3-3: SerialNumber: SH0190810190 [39243.475207] usb-storage 3-3:1.0: USB Mass Storage device detected [39243.476273] scsi19 : usb-storage 3-3:1.0 [39244.479114] scsi 19:0:0:0: Direct-Access ADATA HDD SH93 PQ: 0 ANSI: 0 [39244.479690] sd 19:0:0:0: Attached scsi generic sg3 type 0 [39244.479695] sd 19:0:0:0: Embedded Enclosure Device [39244.479745] sd 19:0:0:0: [sdc] 1465149168 512-byte logical blocks: (750 GB/698 GiB) [39244.480092] sd 19:0:0:0: Failed to get diagnostic page 0x8000002 [39244.480095] sd 19:0:0:0: Failed to bind enclosure -19 [39244.480251] sd 19:0:0:0: [sdc] Write Protect is off [39244.480256] sd 19:0:0:0: [sdc] Mode Sense: 03 00 00 00 [39244.480456] sd 19:0:0:0: [sdc] No Caching mode page found [39244.480464] sd 19:0:0:0: [sdc] Assuming drive cache: write through [39244.504825] sdc: sdc1 [39244.505877] sd 19:0:0:0: [sdc] Attached SCSI disk [39253.085857] usb 3-3: USB disconnect, device number 17 Any idea what went wrong? Vojtěch -- Vojtěch Zeisek Komunita openSUSE GNU/Linuxu Community of the openSUSE GNU/Linux http://www.opensuse.org/ http://trapa.cz/
Am Montag, 24. November 2014, 15:07:21 schrieb Vojtěch Zeisek:
[...] Autofs is running (and I haven't touched config files), although „systemctl status autofs.service“ says: „automount[22123]: lookup_init:139: lookup(yp): map auto.master: Local domain name not set“. I don't know how relevant this is for the problem. [...]
I do not think autofs is needed or even used by KDE for automounting. It might be unrelated, but autofs and NetworkManager do not play well together using 13.2: http://bugzilla.suse.com/show_bug.cgi?id=905639 So, to rule this out, does "loginctl" show a session for your user? Gruß Jan -- Computers are not intelligent. They only think they are. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Dne Po 24. listopadu 2014 19:45:26, Jan Ritzerfeld napsal(a):
Am Montag, 24. November 2014, 15:07:21 schrieb Vojtěch Zeisek:
[...] Autofs is running (and I haven't touched config files), although „systemctl status autofs.service“ says: „automount[22123]: lookup_init:139: lookup(yp): map auto.master: Local domain name not set“. I don't know how relevant this is for the problem. [...]
I do not think autofs is needed or even used by KDE for automounting. It might be unrelated, but autofs and NetworkManager do not play well together using 13.2: http://bugzilla.suse.com/show_bug.cgi?id=905639 So, to rule this out, does "loginctl" show a session for your user?
Interesting bug... But I keep same settings as in 13.1. I have no exotic settings, no NFS or NIS, nothing like that. I use NetworkManager and it works as usual. The machine is notebook, but I mostly use wired connection. Wifi works. It happens every login. Booting takes just few seconds, no problem here. $ loginctl SESSION UID USER SEAT 1 1000 vojta seat0 1 sessions listed. So this seems to be correct - I'm the only one user logged at the time. I'll try with wicked instead of NetworkManager, but I don't see how those services should be related... All the best, Vojtěch -- Vojtěch Zeisek Komunita openSUSE GNU/Linuxu Community of the openSUSE GNU/Linux http://www.opensuse.org/ http://trapa.cz/
Dne Po 24. listopadu 2014 22:37:50 jste napsal(a):
Dne Po 24. listopadu 2014 19:45:26, Jan Ritzerfeld napsal(a):
Am Montag, 24. November 2014, 15:07:21 schrieb Vojtěch Zeisek:
[...] Autofs is running (and I haven't touched config files), although „systemctl status autofs.service“ says: „automount[22123]: lookup_init:139: lookup(yp): map auto.master: Local domain name not set“. I don't know how relevant this is for the problem. [...]
I do not think autofs is needed or even used by KDE for automounting. It might be unrelated, but autofs and NetworkManager do not play well together using 13.2: http://bugzilla.suse.com/show_bug.cgi?id=905639 So, to rule this out, does "loginctl" show a session for your user?
Interesting bug... But I keep same settings as in 13.1. I have no exotic settings, no NFS or NIS, nothing like that. I use NetworkManager and it works as usual. The machine is notebook, but I mostly use wired connection. Wifi works. It happens every login. Booting takes just few seconds, no problem here. $ loginctl SESSION UID USER SEAT 1 1000 vojta seat0
1 sessions listed. So this seems to be correct - I'm the only one user logged at the time. I'll try with wicked instead of NetworkManager, but I don't see how those services should be related...
The only difference when using wicked is that boot is several times longer. Automounting still doesn't work... V. -- Vojtěch Zeisek Komunita openSUSE GNU/Linuxu Community of the openSUSE GNU/Linux http://www.opensuse.org/ http://trapa.cz/
On 11/25/2014 05:08 AM, Vojtěch Zeisek wrote:
The only difference when using wicked is that boot is several times longer. Automounting still doesn't work...
I previously posted the following but to the wrong thread so you probably didn't notice it. ------------------------------------------------------------- What has changed between 12.2 and 12.3 for * kde's systemsetting -> removable devices * udev rules In 'removable devices' there are settings which may have been reset with the new system and which would turn off the "expected" behaviour: ============================================================= [X] Enable automatic mounting of removable media When this is unchecked, no device automounting of any kind will happen, regardless of anything selected in the Device Overrides section. [ ] Only automatically mount removable media that has been manually mounted before When this is checked, KDE will only automatically mount devices it remembers. A device is “remembered” if it has ever been mounted before; e.g. Plugging in a USB media player to charge is not sufficient to “remember” it. If the files are not accessed, KDE will not automatically mount the player next time it is seen. Once they have been accessed, however, KDE will remember to automatically make the contents accessible to your system. [x] Mount all removable media at login If any removable storage devices are connected to your system when you login to your desktop, KDE will automatically make the contents available to your system for other programs to read. [x] Automatically mount removable media when attached When this is checked, KDE will automatically make the contents of any storage device available to the system when it is plugged in or attached. ========================================================= The first "Enable .." and the last "Automatically..." are key. -- /"\ \ / ASCII Ribbon Campaign X Against HTML Mail / \ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Dne Út 25. listopadu 2014 07:32:35, Anton Aylward napsal(a):
On 11/25/2014 05:08 AM, Vojtěch Zeisek wrote:
The only difference when using wicked is that boot is several times longer. Automounting still doesn't work...
I previously posted the following but to the wrong thread so you probably didn't notice it.
-------------------------------------------------------------
What has changed between 12.2 and 12.3 for
* kde's systemsetting -> removable devices
* udev rules
In 'removable devices' there are settings which may have been reset with the new system and which would turn off the "expected" behaviour:
============================================================= [X] Enable automatic mounting of removable media When this is unchecked, no device automounting of any kind will happen, regardless of anything selected in the Device Overrides section.
[ ] Only automatically mount removable media that has been manually mounted before When this is checked, KDE will only automatically mount devices it remembers. A device is “remembered” if it has ever been mounted before; e.g. Plugging in a USB media player to charge is not sufficient to “remember” it. If the files are not accessed, KDE will not automatically mount the player next time it is seen. Once they have been accessed, however, KDE will remember to automatically make the contents accessible to your system.
[x] Mount all removable media at login If any removable storage devices are connected to your system when you login to your desktop, KDE will automatically make the contents available to your system for other programs to read.
[x] Automatically mount removable media when attached When this is checked, KDE will automatically make the contents of any storage device available to the system when it is plugged in or attached. =========================================================
The first "Enable .." and the last "Automatically..." are key.
Yes, I know this. It is checked. Even particular devices for which automount is checked are not mounted... Could it be udev problem? Where to check it? Thank You, Vojtěch -- Vojtěch Zeisek Komunita openSUSE GNU/Linuxu Community of the openSUSE GNU/Linux http://www.opensuse.org/ http://trapa.cz/
On 11/25/2014 10:20 AM, Vojtěch Zeisek wrote:
Could it be udev problem? Where to check it?
I know little about udev, but I do observer in the logs what happens when a USB device is pluged in or removed and can trace that back to udev rules. What do you see in the logs when you plugin in a USB device? This is what happens whe I do that 2014-11-25T10:37:56.302222-05:00 Mainbox kernel: [317747.130029] usb 1-3: new high-speed USB device number 4 using ehci-pci 2014-11-25T10:37:56.417233-05:00 Mainbox kernel: [317747.245517] usb 1-3: New USB device found, idVendor=1221, idProduct=3234 2014-11-25T10:37:56.417254-05:00 Mainbox kernel: [317747.245523] usb 1-3: New USB device strings: Mfr=1, Product=2, SerialNumber=3 2014-11-25T10:37:56.417256-05:00 Mainbox kernel: [317747.245527] usb 1-3: Product: Flash Disk 2014-11-25T10:37:56.417258-05:00 Mainbox kernel: [317747.245530] usb 1-3: Manufacturer: USB 2.0 2014-11-25T10:37:56.417260-05:00 Mainbox kernel: [317747.245533] usb 1-3: SerialNumber: 4999216001701879 2014-11-25T10:37:56.732845-05:00 Mainbox mtp-probe: checking bus 1, device 4: "/sys/devices/pci0000:00/0000:00:1a.7/usb1/1-3" 2014-11-25T10:37:56.740231-05:00 Mainbox mtp-probe: bus: 1, device: 4 was not an MTP device 2014-11-25T10:37:57.003230-05:00 Mainbox kernel: [317747.831668] usb-storage 1-3:1.0: USB Mass Storage device detected 2014-11-25T10:37:57.004091-05:00 Mainbox kernel: [317747.832297] scsi host8: usb-storage 1-3:1.0 2014-11-25T10:37:57.004099-05:00 Mainbox kernel: [317747.832480] usbcore: registered new interface driver usb-storage 2014-11-25T10:37:58.007244-05:00 Mainbox kernel: [317748.835686] scsi 8:0:0:0: Direct-Access USB 2.0 Flash Disk 2.90 PQ: 0 ANSI: 2 2014-11-25T10:37:58.007273-05:00 Mainbox kernel: [317748.836060] sd 8:0:0:0: Attached scsi generic sg2 type 0 2014-11-25T10:37:58.009219-05:00 Mainbox kernel: [317748.837166] sd 8:0:0:0: [sdb] 15974400 512-byte logical blocks: (8.17 GB/7.61 GiB) 2014-11-25T10:37:58.009239-05:00 Mainbox kernel: [317748.837782] sd 8:0:0:0: [sdb] Write Protect is off 2014-11-25T10:37:58.009241-05:00 Mainbox kernel: [317748.837788] sd 8:0:0:0: [sdb] Mode Sense: 0b 00 00 08 2014-11-25T10:37:58.010207-05:00 Mainbox kernel: [317748.838409] sd 8:0:0:0: [sdb] No Caching mode page found 2014-11-25T10:37:58.010217-05:00 Mainbox kernel: [317748.838414] sd 8:0:0:0: [sdb] Assuming drive cache: write through 2014-11-25T10:37:58.035228-05:00 Mainbox kernel: [317748.863570] sdb: sdb1 2014-11-25T10:37:58.037216-05:00 Mainbox kernel: [317748.865907] sd 8:0:0:0: [sdb] Attached SCSI removable diskdevice fsid 933f8b90-8f90-4c96-9a90-4705d77f0505 devid 1 transid 219 /dev/sdb1 2014-11-25T10:38:01.986570-05:00 Mainbox udisksd[2169]: Mounted /dev/sdb1 at /run/media/anton/933f8b90-8f90-4c96-9a90-4705d77f0505 on behalf of uid 501 I then get the KDE popup of the device notifier on my panel. Yes, lots of settings to fiddle with -- /"\ \ / ASCII Ribbon Campaign X Against HTML Mail / \ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Dne Út 25. listopadu 2014 10:42:39, Anton Aylward napsal(a):
On 11/25/2014 10:20 AM, Vojtěch Zeisek wrote:
Could it be udev problem? Where to check it?
I know little about udev, but I do observer in the logs what happens when a USB device is pluged in or removed and can trace that back to udev rules.
What do you see in the logs when you plugin in a USB device?
This is what happens whe I do that
2014-11-25T10:37:56.302222-05:00 Mainbox kernel: [317747.130029] usb 1-3: new high-speed USB device number 4 using ehci-pci 2014-11-25T10:37:56.417233-05:00 Mainbox kernel: [317747.245517] usb 1-3: New USB device found, idVendor=1221, idProduct=3234 2014-11-25T10:37:56.417254-05:00 Mainbox kernel: [317747.245523] usb 1-3: New USB device strings: Mfr=1, Product=2, SerialNumber=3 2014-11-25T10:37:56.417256-05:00 Mainbox kernel: [317747.245527] usb 1-3: Product: Flash Disk 2014-11-25T10:37:56.417258-05:00 Mainbox kernel: [317747.245530] usb 1-3: Manufacturer: USB 2.0 2014-11-25T10:37:56.417260-05:00 Mainbox kernel: [317747.245533] usb 1-3: SerialNumber: 4999216001701879 2014-11-25T10:37:56.732845-05:00 Mainbox mtp-probe: checking bus 1, device 4: "/sys/devices/pci0000:00/0000:00:1a.7/usb1/1-3" 2014-11-25T10:37:56.740231-05:00 Mainbox mtp-probe: bus: 1, device: 4 was not an MTP device 2014-11-25T10:37:57.003230-05:00 Mainbox kernel: [317747.831668] usb-storage 1-3:1.0: USB Mass Storage device detected 2014-11-25T10:37:57.004091-05:00 Mainbox kernel: [317747.832297] scsi host8: usb-storage 1-3:1.0 2014-11-25T10:37:57.004099-05:00 Mainbox kernel: [317747.832480] usbcore: registered new interface driver usb-storage 2014-11-25T10:37:58.007244-05:00 Mainbox kernel: [317748.835686] scsi 8:0:0:0: Direct-Access USB 2.0 Flash Disk 2.90 PQ: 0 ANSI: 2 2014-11-25T10:37:58.007273-05:00 Mainbox kernel: [317748.836060] sd 8:0:0:0: Attached scsi generic sg2 type 0 2014-11-25T10:37:58.009219-05:00 Mainbox kernel: [317748.837166] sd 8:0:0:0: [sdb] 15974400 512-byte logical blocks: (8.17 GB/7.61 GiB) 2014-11-25T10:37:58.009239-05:00 Mainbox kernel: [317748.837782] sd 8:0:0:0: [sdb] Write Protect is off 2014-11-25T10:37:58.009241-05:00 Mainbox kernel: [317748.837788] sd 8:0:0:0: [sdb] Mode Sense: 0b 00 00 08 2014-11-25T10:37:58.010207-05:00 Mainbox kernel: [317748.838409] sd 8:0:0:0: [sdb] No Caching mode page found 2014-11-25T10:37:58.010217-05:00 Mainbox kernel: [317748.838414] sd 8:0:0:0: [sdb] Assuming drive cache: write through 2014-11-25T10:37:58.035228-05:00 Mainbox kernel: [317748.863570] sdb: sdb1 2014-11-25T10:37:58.037216-05:00 Mainbox kernel: [317748.865907] sd 8:0:0:0: [sdb] Attached SCSI removable diskdevice fsid 933f8b90-8f90-4c96-9a90-4705d77f0505 devid 1 transid 219 /dev/sdb1 2014-11-25T10:38:01.986570-05:00 Mainbox udisksd[2169]: Mounted /dev/sdb1 at /run/media/anton/933f8b90-8f90-4c96-9a90-4705d77f0505 on behalf of uid 501
I then get the KDE popup of the device notifier on my panel.
Yes, lots of settings to fiddle with
$ dmesg | grep sdc [ 2507.755697] sd 6:0:0:0: [sdc] 7886848 512-byte logical blocks: (4.03 GB/3.76 GiB) [ 2507.756286] sd 6:0:0:0: [sdc] Write Protect is off [ 2507.756291] sd 6:0:0:0: [sdc] Mode Sense: 43 00 00 00 [ 2507.756881] sd 6:0:0:0: [sdc] No Caching mode page found [ 2507.756885] sd 6:0:0:0: [sdc] Assuming drive cache: write through [ 2507.760051] sdc: sdc1 [ 2507.762196] sd 6:0:0:0: [sdc] Attached SCSI removable disk [10258.441052] sd 7:0:0:0: [sdc] 15669248 512-byte logical blocks: (8.02 GB/7.47 GiB) [10258.441307] sd 7:0:0:0: [sdc] Write Protect is off [10258.441312] sd 7:0:0:0: [sdc] Mode Sense: 03 00 00 00 [10258.441554] sd 7:0:0:0: [sdc] No Caching mode page found [10258.441557] sd 7:0:0:0: [sdc] Assuming drive cache: write through [10258.444299] sdc: sdc1 sdc2 sdc3 [10258.445959] sd 7:0:0:0: [sdc] Attached SCSI removable disk [12694.515326] sdc: sdc1 sdc2 [12711.649846] sd 8:0:0:0: [sdc] 15669248 512-byte logical blocks: (8.02 GB/7.47 GiB) [12711.650108] sd 8:0:0:0: [sdc] Write Protect is off [12711.650110] sd 8:0:0:0: [sdc] Mode Sense: 03 00 00 00 [12711.650340] sd 8:0:0:0: [sdc] No Caching mode page found [12711.650341] sd 8:0:0:0: [sdc] Assuming drive cache: write through [12711.652950] sdc: sdc1 sdc2 [12711.655029] sd 8:0:0:0: [sdc] Attached SCSI removable disk [13102.846129] sd 9:0:0:0: [sdc] 15669248 512-byte logical blocks: (8.02 GB/7.47 GiB) [13102.846448] sd 9:0:0:0: [sdc] Write Protect is off [13102.846451] sd 9:0:0:0: [sdc] Mode Sense: 03 00 00 00 [13102.846735] sd 9:0:0:0: [sdc] No Caching mode page found [13102.846737] sd 9:0:0:0: [sdc] Assuming drive cache: write through [13102.849727] sdc: sdc1 [13102.851930] sd 9:0:0:0: [sdc] Attached SCSI removable disk [14901.530431] sdc: sdc1 sdc2 [20055.545464] sd 10:0:0:0: [sdc] 31277056 512-byte logical blocks: (16.0 GB/14.9 GiB) [20055.545810] sd 10:0:0:0: [sdc] Write Protect is off [20055.545815] sd 10:0:0:0: [sdc] Mode Sense: 23 00 00 00 [20055.546104] sd 10:0:0:0: [sdc] No Caching mode page found [20055.546109] sd 10:0:0:0: [sdc] Assuming drive cache: write through [20055.646811] sdc: sdc1 [20055.648199] sd 10:0:0:0: [sdc] Attached SCSI removable disk [28121.840450] sd 11:0:0:0: [sdc] 31277056 512-byte logical blocks: (16.0 GB/14.9 GiB) [28121.840867] sd 11:0:0:0: [sdc] Write Protect is off [28121.840872] sd 11:0:0:0: [sdc] Mode Sense: 23 00 00 00 [28121.841197] sd 11:0:0:0: [sdc] No Caching mode page found [28121.841200] sd 11:0:0:0: [sdc] Assuming drive cache: write through [28121.941566] sdc: sdc1 [28121.942661] sd 11:0:0:0: [sdc] Attached SCSI removable dis It appears in KDE notifications as usual, but mounting fails... -- Vojtěch Zeisek Komunita openSUSE GNU/Linuxu Community of the openSUSE GNU/Linux http://www.opensuse.org/ http://trapa.cz/
On 11/25/2014 12:32 PM, Vojtěch Zeisek wrote:
Dne Út 25. listopadu 2014 10:42:39, Anton Aylward napsal(a):
On 11/25/2014 10:20 AM, Vojtěch Zeisek wrote:
Could it be udev problem? Where to check it?
I know little about udev, but I do observer in the logs what happens when a USB device is pluged in or removed and can trace that back to udev rules.
It appears in KDE notifications as usual, but mounting fails...
The key difference between yours and mine seems to be
2014-11-25T10:38:01.986570-05:00 Mainbox udisksd[2169]: Mounted /dev/sdb1 at /run/media/anton/933f8b90-8f90-4c96-9a90-4705d77f0505 on behalf of uid 501
That is BEFORE the KDE Device Notifier popup happens. The message coming from udiskd makes me think that its a udisk issue. Is you udisk daemon -- udiskd -- running? # ps -ef | grep udisk root 2169 1 0 Nov21 ? 00:00:52 /usr/lib/udisks2/udisksd --no-debug # systemctl status udisks2.service udisks2.service - Disk Manager Loaded: loaded (/usr/lib/systemd/system/udisks2.service; static) Active: active (running) since Fri 2014-11-21 18:37:37 EST; 3 days ago Docs: man:udisks(8) Main PID: 2169 (udisksd) CGroup: /system.slice/udisks2.service └─2169 /usr/lib/udisks2/udisksd --no-debug Nov 21 18:37:36 Mainbox systemd[1]: Starting Disk Manager... Nov 21 18:37:37 Mainbox udisksd[2169]: udisks daemon version 2.1.1 starting Nov 21 18:37:37 Mainbox systemd[1]: Started Disk Manager. Nov 21 18:37:37 Mainbox udisksd[2169]: Acquired the name org.freedesktop.UDisks2 on the system message bus Nov 25 10:38:01 Mainbox udisksd[2169]: Mounted /dev/sdb1 at /run/media/anton/933f8b90-8f90-4c96-9a90-4705d77f0505 on behalf of uid 501 So make sure its enabled and active -- /"\ \ / ASCII Ribbon Campaign X Against HTML Mail / \ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
It is really weird... Dne Út 25. listopadu 2014 12:48:09, Anton Aylward napsal(a):
On 11/25/2014 12:32 PM, Vojtěch Zeisek wrote:
Dne Út 25. listopadu 2014 10:42:39, Anton Aylward napsal(a):
On 11/25/2014 10:20 AM, Vojtěch Zeisek wrote: The key difference between yours and mine seems to be
2014-11-25T10:38:01.986570-05:00 Mainbox udisksd[2169]: Mounted /dev/sdb1 at /run/media/anton/933f8b90-8f90-4c96-9a90-4705d77f0505 on behalf of uid 501
That is BEFORE the KDE Device Notifier popup happens.
The message coming from udiskd makes me think that its a udisk issue. Is you udisk daemon -- udiskd -- running?
# ps -ef | grep udisk root 2169 1 0 Nov21 ? 00:00:52 /usr/lib/udisks2/udisksd --no-debug
root 2582 1 0 10:42 ? 00:00:09 /usr/lib/udisks2/udisksd --no-debug
# systemctl status udisks2.service udisks2.service - Disk Manager Loaded: loaded (/usr/lib/systemd/system/udisks2.service; static) Active: active (running) since Fri 2014-11-21 18:37:37 EST; 3 days ago Docs: man:udisks(8) Main PID: 2169 (udisksd) CGroup: /system.slice/udisks2.service └─2169 /usr/lib/udisks2/udisksd --no-debug
Nov 21 18:37:36 Mainbox systemd[1]: Starting Disk Manager... Nov 21 18:37:37 Mainbox udisksd[2169]: udisks daemon version 2.1.1 starting Nov 21 18:37:37 Mainbox systemd[1]: Started Disk Manager. Nov 21 18:37:37 Mainbox udisksd[2169]: Acquired the name org.freedesktop.UDisks2 on the system message bus Nov 25 10:38:01 Mainbox udisksd[2169]: Mounted /dev/sdb1 at /run/media/anton/933f8b90-8f90-4c96-9a90-4705d77f0505 on behalf of uid 501
udisks2.service - Disk Manager Loaded: loaded (/usr/lib/systemd/system/udisks2.service; static) Active: active (running) since Út 2014-11-25 10:42:39 CET; 8h ago Docs: man:udisks(8) Main PID: 2582 (udisksd) CGroup: /system.slice/udisks2.service └─2582 /usr/lib/udisks2/udisksd --no-debug lis 25 10:42:39 veles udisksd[2582]: udisks daemon version 2.1.3 starting lis 25 10:42:39 veles udisksd[2582]: Acquired the name org.freedesktop.UDisks2 on the system message bus
So make sure its enabled and active
This also seems to be correct... zypper se -si udisk S | Name | Type | Version | Arch | Repository --+--------------+---------+-------------+--------+-------------------------- i | libudisks2-0 | package | 2.1.3-2.1.5 | x86_64 | OSS i | udisks2 | package | 2.1.3-2.1.5 | x86_64 | OSS -- Vojtěch Zeisek Komunita openSUSE GNU/Linuxu Community of the openSUSE GNU/Linux http://www.opensuse.org/ http://trapa.cz/
On 11/25/2014 01:01 PM, Vojtěch Zeisek wrote:
This also seems to be correct... zypper se -si udisk
S | Name | Type | Version | Arch | Repository --+--------------+---------+-------------+--------+-------------------------- i | libudisks2-0 | package | 2.1.3-2.1.5 | x86_64 | OSS i | udisks2 | package | 2.1.3-2.1.5 | x86_64 | OSS
And I'm on 2.1.1 since I'm on a 13.1 where it works. So maybe its a change in the udev rules. # udevadm info --attribute-walk /sys/bus/usb/devices looking at device '/bus/usb/devices': KERNEL=="devices" SUBSYSTEM=="subsystem" DRIVER=="" looking at parent device '/bus/usb': KERNELS=="usb" SUBSYSTEMS=="subsystem" DRIVERS=="" ATTRS{drivers_autoprobe}=="1" -- /"\ \ / ASCII Ribbon Campaign X Against HTML Mail / \ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Dne Út 25. listopadu 2014 14:58:08, Anton Aylward napsal(a):
On 11/25/2014 01:01 PM, Vojtěch Zeisek wrote:
This also seems to be correct... zypper se -si udisk
S | Name | Type | Version | Arch | Repository --+--------------+---------+-------------+--------+----------------------- --- i | libudisks2-0 | package | 2.1.3-2.1.5 | x86_64 | OSS i | udisks2 | package | 2.1.3-2.1.5 | x86_64 | OSS
And I'm on 2.1.1 since I'm on a 13.1 where it works.
Yes, in 13.1 it worked without touching it... And on fresh install of 13.2 it also works out of the box...
So maybe its a change in the udev rules.
# udevadm info --attribute-walk /sys/bus/usb/devices
looking at device '/bus/usb/devices': KERNEL=="devices" SUBSYSTEM=="subsystem" DRIVER==""
looking at parent device '/bus/usb': KERNELS=="usb" SUBSYSTEMS=="subsystem" DRIVERS=="" ATTRS{drivers_autoprobe}=="1"
looking at device '/bus/usb/devices': KERNEL=="devices" SUBSYSTEM=="subsystem" DRIVER=="" looking at parent device '/bus/usb': KERNELS=="usb" SUBSYSTEMS=="subsystem" DRIVERS=="" ATTRS{drivers_autoprobe}=="1 It is absolutely same. This is crazy. Why doesn't it work? -- Vojtěch Zeisek Komunita openSUSE GNU/Linuxu Community of the openSUSE GNU/Linux http://www.opensuse.org/ http://trapa.cz/
On 11/25/2014 03:42 PM, Vojtěch Zeisek wrote:
It is absolutely same. This is crazy. Why doesn't it work?
Beats me. This and others ... 13.2 seems 'still in beta'. I'll hold off for a while longer. -- /"\ \ / ASCII Ribbon Campaign X Against HTML Mail / \ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Am Montag, 24. November 2014, 22:37:50 schrieb Vojtěch Zeisek:
Dne Po 24. listopadu 2014 19:45:26, Jan Ritzerfeld napsal(a): [...]
I do not think autofs is needed or even used by KDE for automounting. It might be unrelated, but autofs and NetworkManager do not play well together using 13.2: http://bugzilla.suse.com/show_bug.cgi?id=905639 So, to rule this out, does "loginctl" show a session for your user?
Interesting bug...
Indeed! It took me and other people hours to find out what was wrong.
But I keep same settings as in 13.1.
Me too, and it worked perfectly using 13.1.
[...] 1 sessions listed. So this seems to be correct - I'm the only one user logged at the time.
Yep. When hitting that bug 0 sessions are listed.
I'll try with wicked instead of NetworkManager, but I don't see how those services should be related...
ATM I have no other idea. Sorry!
All the best, Vojtěch
Viele Grüße Jan -- You can't antagonize and influence at the same time. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Monday 24 November 2014 19.45:26 Jan Ritzerfeld wrote:
Am Montag, 24. November 2014, 15:07:21 schrieb Vojtěch Zeisek:
[...] Autofs is running (and I haven't touched config files), although „systemctl status autofs.service“ says: „automount[22123]: lookup_init:139: lookup(yp): map auto.master: Local domain name not set“. I don't know how relevant this is for the problem. [...]
I do not think autofs is needed or even used by KDE for automounting. It might be unrelated, but autofs and NetworkManager do not play well together using 13.2: http://bugzilla.suse.com/show_bug.cgi?id=905639 So, to rule this out, does "loginctl" show a session for your user?
I have applied the workaround described in comment #3 to that bug <https://bugzilla.suse.com/show_bug.cgi?id=905639#c3> to my laptops running openSUSE 13.2 because I noticed login delays/problems after enabling autofs. It did the trick for me - login after boot, and shutdown, work much better now, like it used to under 13.1. \Olav -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 12/1/2014 1:35 PM, Olav Reinert wrote:
On Monday 24 November 2014 19.45:26 Jan Ritzerfeld wrote:
Am Montag, 24. November 2014, 15:07:21 schrieb Vojtěch Zeisek:
[...] Autofs is running (and I haven't touched config files), although „systemctl status autofs.service“ says: „automount[22123]: lookup_init:139: lookup(yp): map auto.master: Local domain name not set“. I don't know how relevant this is for the problem. [...]
I do not think autofs is needed or even used by KDE for automounting. It might be unrelated, but autofs and NetworkManager do not play well together using 13.2: http://bugzilla.suse.com/show_bug.cgi?id=905639 So, to rule this out, does "loginctl" show a session for your user?
I have applied the workaround described in comment #3 to that bug <https://bugzilla.suse.com/show_bug.cgi?id=905639#c3> to my laptops running openSUSE 13.2 because I noticed login delays/problems after enabling autofs.
It did the trick for me - login after boot, and shutdown, work much better now, like it used to under 13.1.
\Olav
Stock FRESH install of 13.2 and KDE4, and I have yet to see any problem whatsoever with Automount and NetworkManager. I've mounted flash drives, Disk Drives in two different models of external cases, with different formats, cameras, Cell Phones, etc. It all works superbly. Not one hiccup. I suggest what people are encountering is remnants of old versions laying around. -- _____________________________________ ---This space for rent--- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Monday 01 December 2014 16.06:01 John Andersen wrote:
On 12/1/2014 1:35 PM, Olav Reinert wrote:
On Monday 24 November 2014 19.45:26 Jan Ritzerfeld wrote:
I do not think autofs is needed or even used by KDE for automounting. It might be unrelated, but autofs and NetworkManager do not play well together using 13.2: http://bugzilla.suse.com/show_bug.cgi?id=905639 So, to rule this out, does "loginctl" show a session for your user?
I have applied the workaround described in comment #3 to that bug <https://bugzilla.suse.com/show_bug.cgi?id=905639#c3> to my laptops running openSUSE 13.2 because I noticed login delays/problems after enabling autofs.
It did the trick for me - login after boot, and shutdown, work much better now, like it used to under 13.1.
\Olav
Stock FRESH install of 13.2 and KDE4, and I have yet to see any problem whatsoever with Automount and NetworkManager. I've mounted flash drives, Disk Drives in two different models of external cases, with different formats, cameras, Cell Phones, etc. It all works superbly.
Not one hiccup. I suggest what people are encountering is remnants of old versions laying around.
I'm also using a fresh install of 13.2 with a KDE4 desktop. Even the $HOME directory is fresh, there's no config junk from previous releases. And mounting USB sticks in KDE works fine for me. However, the original poster suspected a relation between USB automount and autofs. Jan Ritzerfeld replied, saying there is probably no correlation - and I think he's right. Jan also mentioned a bug related to autofs and NetworkManager not working well together. That's the problem which the workaround in the bug report fixes for me. Sorry for taking the thread a bit offtopic. \Olav -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
participants (5)
-
Anton Aylward -
Jan Ritzerfeld -
John Andersen -
Olav Reinert -
Vojtěch Zeisek