USB disk not automatically mounted after upgrade to 13.10

I stopped and restarted in debug mode udisksd. The event arrives, then it simply stops and does nothing.
Log from the daemon (inserting another USB stick, so it's sdd now):

14:28:17.122:[5681]:[NOTICE]: Acquired the name org.freedesktop.UDisks2 on the system message bus [main.c:77, on_name_acquired()]
14:28:17.846:[5683]:[INFO]: Housekeeping complete [udiskslinuxprovider.c:973, housekeeping_thread_func()]
14:28:34.725:[5681]:[DEBUG]: uevent add /sys/devices/pci0000:00/0000:00:1c.4/0000:04:00.0/usb3/3-1/3-1:1.0/host12 [udiskslinuxprovider.c:902, udisks_linux_provider_handle_uevent()]
14:28:35.960:[5681]:[DEBUG]: uevent add /sys/devices/pci0000:00/0000:00:1c.4/0000:04:00.0/usb3/3-1/3-1:1.0/host12/target12:0:0 [udiskslinuxprovider.c:902, udisks_linux_provider_handle_uevent()]
14:28:35.961:[5681]:[DEBUG]: uevent add /sys/devices/pci0000:00/0000:00:1c.4/0000:04:00.0/usb3/3-1/3-1:1.0/host12/target12:0:0/12:0:0:0 [udiskslinuxprovider.c:902, udisks_linux_provider_handle_uevent()]
14:28:36.043:[5681]:[DEBUG]: uevent add /sys/devices/pci0000:00/0000:00:1c.4/0000:04:00.0/usb3/3-1/3-1:1.0/host12/target12:0:0/12:0:0:0/block/sdd [udiskslinuxprovider.c:902, udisks_linux_provider_handle_uevent()]
14:28:36.112:[5681]:[DEBUG]: uevent add /sys/devices/pci0000:00/0000:00:1c.4/0000:04:00.0/usb3/3-1/3-1:1.0/host12/target12:0:0/12:0:0:0/block/sdd/sdd1 [udiskslinuxprovider.c:902, udisks_linux_provider_handle_uevent()]

will try to add udisks to this bug report.

And to add mistery, calling the daemon:

% udisksctl mount --block-device /dev/sdc1

will correctly mount the disk and the log says:

14:40:13.601:[7143]:[NOTICE]: Mounted /dev/sdc1 at /media/romano/3861-ECBD on behalf of uid 1153 [udiskslinuxfilesystem.c:1493, handle_mount()]

Status changed to 'Confirmed' because the bug affects multiple users.

I think that the duplicate is not correct. I will investigate more, but:

- I have no error messages whatsoever;
- my installation is ubuntu gnome, i do not have lightdm installed
- policyKit is completely silent when inserting disk
- I have no problem in mounting *manually* the device.

It seems that the upgrade that entered just now:

Upgrade: libsystemd-login0:amd64 (204-0ubuntu18, 204-0ubuntu19), systemd-services:amd64 (204-0ubuntu18, 204-0ubuntu19), libsystemd-daemon0:amd64 (204-0ubuntu18, 204-0ubuntu19), libgudev-1.0-0:amd64 (204-0ubuntu18, 204-0ubuntu19), libpam-systemd:amd64 (204-0ubuntu18, 204-0ubuntu19), udev:amd64 (204-0ubuntu18, 204-0ubuntu19), libunity-scopes-json-def-desktop:amd64 (7.1.2+13.10.20131010-0ubuntu1, 7.1.2+13.10.20131010-0ubuntu2), gir1.2-gudev-1.0:amd64 (204-0ubuntu18, 204-0ubuntu19), libunity-protocol-private0:amd64 (7.1.2+13.10.20131010-0ubuntu1, 7.1.2+13.10.20131010-0ubuntu2), libudev1:amd64 (204-0ubuntu18, 204-0ubuntu19), libudev1:i386 (204-0ubuntu18, 204-0ubuntu19), libsystemd-journal0:amd64 (204-0ubuntu18, 204-0ubuntu19), libunity9:amd64 (7.1.2+13.10.20131010-0ubuntu1, 7.1.2+13.10.20131010-0ubuntu2), gir1.2-unity-5.0:amd64 (7.1.2+13.10.20131010-0ubuntu1, 7.1.2+13.10.20131010-0ubuntu2)

Fixed the problem.

If the other affected person confirm it's gone, I'll mark it at solved, although it would be nice to find if there is a "main" bug o mark this as a duplicate.

Well --- now I have a warning "can't umount because busy" every time I try to umount the device, but it disappear alone after a couple of seconds and it works. So a nuisance more than a bug.

Unfortunately, it happens again. So it's seems is sort of random. Sometime it works, sometime not. If it works one time it works for all the session (at least). After the next reboot, you sometime have automounting working and sometime no.

Added ubuntu-gnome (to check if there is something going on here --- seems that "regular" ubuntu users have no problem). My system is a ubuntu-gnome 13.04 (fresh install) upgraded to 13.10.

Thank you for your bug report, is that issue happening with Ubuntu/Unity or is specific to gnome-shell?

@Sebastien --- thanks.

I am not sure because the machine with 13.10 lacks the installation of Unity --- Really this problem is what is keeping me from upgrading the other laptop (where I have both Unity and Gnome-shell) to 13.10.
I will try to do more test (I do not have the 13.10 laptop with me now); it has to be a problem very specific, otherwise there would be a lot more people screaming ;-)...
The strange thing is that I can mount perfectly the devices as a normal user with

udisksctl mount --block-device /dev/sdc2

so it seems that something is failing in the chain from udev (which register the disk correctly) to whatever agent is supposed to mount it on my behalf. If you can give some hint on where to look for logs, errors or how to run all the chain in debug mode, I will try to shed some light.

Hi,

I would like to report the same problem.
I tried the same commands as Romano:

udisksctl mount --block-device /dev/sdc1
udisks --mount /dev/sdc1

and was able to mount my drive manually.

If I insert my android phone this does mount automatically.

Please let me know if you need more information.

@Alexander: do you have a Ubuntu/Unity or Ubuntu/Gnome?

...I hate launchpad when you cannot edit your last post... I mean --- is your installation a "vanilla" Ubuntu, with Unity, or you have installed an Ubuntu Gnome distro? Imy case is the second one.

The issue is an Eisenbug ( http://en.wikipedia.org/wiki/Heisenbug ). In this moment my disk has been mounted perfectly and automatically (both partitions). The messages are:

SYS: Oct 23 15:02:22 samsung-romano kernel: [10752.645573] usb 3-1: new high-speed USB device number 2 using xhci_hcd
SYS: Oct 23 15:02:22 samsung-romano kernel: [10752.666699] usb 3-1: New USB device found, idVendor=059b, idProduct=0470
SYS: Oct 23 15:02:22 samsung-romano kernel: [10752.666708] usb 3-1: New USB device strings: Mfr=10, Product=11, SerialNumber=5
SYS: Oct 23 15:02:22 samsung-romano kernel: [10752.666714] usb 3-1: Product: Storage
SYS: Oct 23 15:02:22 samsung-romano kernel: [10752.666719] usb 3-1: Manufacturer: Iomega
SYS: Oct 23 15:02:22 samsung-romano kernel: [10752.666723] usb 3-1: SerialNumber: 6E34633FFFFF
SYS: Oct 23 15:02:22 samsung-romano mtp-probe: checking bus 3, device 2: "/sys/devices/pci0000:00/0000:00:1c.4/0000:04:00.0/usb3/3-1"
SYS: Oct 23 15:02:22 samsung-romano mtp-probe: bus: 3, device: 2 was not an MTP device
SYS: Oct 23 15:02:22 samsung-romano kernel: [10752.745152] Initializing USB Mass Storage driver...
SYS: Oct 23 15:02:22 samsung-romano kernel: [10752.745565] scsi6 : usb-storage 3-1:1.0
SYS: Oct 23 15:02:22 samsung-romano kernel: [10752.745780] usbcore: registered new interface driver usb-storage
SYS: Oct 23 15:02:22 samsung-romano kernel: [10752.745787] USB Mass Storage support registered.
SYS: Oct 23 15:02:23 samsung-romano kernel: [10753.787137] scsi 6:0:0:0: Direct-Access ST950032 5AS PQ: 0 ANSI: 2 CCS
SYS: Oct 23 15:02:23 samsung-romano kernel: [10753.788991] sd 6:0:0:0: Attached scsi generic sg3 type 0
SYS: Oct 23 15:02:23 samsung-romano kernel: [10753.789931] sd 6:0:0:0: [sdc] 976773168 512-byte logical blocks: (500 GB/465 GiB)
SYS: Oct 23 15:02:23 samsung-romano kernel: [10753.791825] sd 6:0:0:0: [sdc] Write Protect is off
SYS: Oct 23 15:02:23 samsung-romano kernel: [10753.791837] sd 6:0:0:0: [sdc] Mode Sense: 28 00 00 00
SYS: Oct 23 15:02:23 samsung-romano kernel: [10753.792962] sd 6:0:0:0: [sdc] No Caching mode page present
SYS: Oct 23 15:02:23 samsung-romano kernel: [10753.792975] sd 6:0:0:0: [sdc] Assuming drive cache: write through
SYS: Oct 23 15:02:23 samsung-romano kernel: [10753.795535] sd 6:0:0:0: [sdc] No Caching mode page present
SYS: Oct 23 15:02:23 samsung-romano kernel: [10753.795544] sd 6:0:0:0: [sdc] Assuming drive cache: write through
SYS: Oct 23 15:02:23 samsung-romano kernel: [10753.862304] sdc: sdc1 sdc2
SYS: Oct 23 15:02:23 samsung-romano kernel: [10753.865773] sd 6:0:0:0: [sdc] No Caching mode page present
SYS: Oct 23 15:02:23 samsung-romano kernel: [10753.865784] sd 6:0:0:0: [sdc] Assuming drive cache: write through
SYS: Oct 23 15:02:23 samsung-romano kernel: [10753.865792] sd 6:0:0:0: [sdc] Attached SCSI disk
SYS: Oct 23 15:02:24 samsung-romano dbus[703]: [system] Activating service name='org.freedesktop.hostname1' (using servicehelper)
SYS: Oct 23 15:02:24 samsung-romano dbus[703]: [system] Successfully activated service 'org.freedesktop.hostname1'
SYS: Oct 23 15:02:25 samsung-romano udisksd[2497]: Mounted /dev/sdc2 at /media/romano/movlin on behalf of uid 1153
SYS: Oct 23 15:...

...and u(n)mounted without any glitch. Next boot, who knows...

No need to wait for the next boot. After four hours, inserted again the same disk, no automounting. At least not in the three minutes I have waited before mounting it manually.

@Romano,

To be honest I am not sure what I have.
I have been upgrading this laptop over the years starting from ubuntu 8.

So far I have not been able to automount my disk however. I noticed in dmesg it says the following:

FAT-fs (sdc1): Volume was not properly unmounted. Some data may be corrupt. Please run fsck.

So I ran fsck and also I mounted and cleanly unmounted the disk on a windows machine but still no luck.
Here is the latest dmesg:

[ 168.040074] usb 2-5: new high-speed USB device number 4 using ehci-pci
[ 168.173241] usb 2-5: New USB device found, idVendor=04e8, idProduct=1f03
[ 168.173248] usb 2-5: New USB device strings: Mfr=1, Product=11, SerialNumber=3
[ 168.173253] usb 2-5: Product: Samsung S2 Portable
[ 168.173256] usb 2-5: Manufacturer: JMicron
[ 168.173259] usb 2-5: SerialNumber: 0000002CE093105015B4
[ 168.217769] usb-storage 2-5:1.0: USB Mass Storage device detected
[ 168.217885] scsi5 : usb-storage 2-5:1.0
[ 168.217999] usbcore: registered new interface driver usb-storage
[ 169.258437] scsi 5:0:0:0: Direct-Access Samsung S2 Portable PQ: 0 ANSI: 2 CCS
[ 169.259035] sd 5:0:0:0: Attached scsi generic sg3 type 0
[ 169.267360] sd 5:0:0:0: [sdc] 625142448 512-byte logical blocks: (320 GB/298 GiB)
[ 169.268880] sd 5:0:0:0: [sdc] Write Protect is off
[ 169.268887] sd 5:0:0:0: [sdc] Mode Sense: 28 00 00 00
[ 169.270154] sd 5:0:0:0: [sdc] No Caching mode page found
[ 169.270163] sd 5:0:0:0: [sdc] Assuming drive cache: write through
[ 169.273779] sd 5:0:0:0: [sdc] No Caching mode page found
[ 169.273787] sd 5:0:0:0: [sdc] Assuming drive cache: write through
[ 169.303060] sdc: sdc1
[ 169.306276] sd 5:0:0:0: [sdc] No Caching mode page found
[ 169.306285] sd 5:0:0:0: [sdc] Assuming drive cache: write through
[ 169.306293] sd 5:0:0:0: [sdc] Attached SCSI disk
[ 186.308242] FAT-fs (sdc1): Volume was not properly unmounted. Some data may be corrupt. Please run fsck.

I tried reinstalling udisk2 using synaptic but I get the following error.
No idea if this error already occured during the upgrade.

(Reading database ... 311315 files and directories currently installed.)
Preparing to replace udisks2 2.1.0-4 (using .../udisks2_2.1.0-4_i386.deb) ...
Unpacking replacement udisks2 ...
Processing triggers for man-db ...
Setting up udisks2 (2.1.0-4) ...

(process:12774): GLib-GObject-WARNING **: invalid (NULL) pointer instance

(process:12774): GLib-GObject-CRITICAL **: g_signal_handlers_disconnect_matched: assertion 'G_TYPE_CHECK_INSTANCE (instance)' failed

(process:12774): GLib-GObject-WARNING **: invalid (NULL) pointer instance

(process:12774): GLib-GObject-CRITICAL **: g_signal_handlers_disconnect_matched: assertion 'G_TYPE_CHECK_INSTANCE (instance)' failed

(process:12774): GLib-GObject-WARNING **: invalid (NULL) pointer instance

(process:12774): GLib-GObject-CRITICAL **: g_signal_handlers_disconnect_matched: assertion 'G_TYPE_CHECK_INSTANCE (instance)' failed

(process:12774): GLib-GObject-WARNING **: invalid (NULL) pointer instance

(process:12774): GLib-GObject-CRITICAL **: g_signal_handlers_disconnect_matched: assertion 'G_TYPE_CHECK_INSTANCE (instance)' failed

(process:12774): GLib-GObject-WARNING **: invalid (NULL) pointer instance

(process:12774): GLib-GObject-CRITICAL **: g_signal_handlers_disconnect_matched: assertion 'G_TYPE_CHECK_INSTANCE (instance)' failed

(process:12774): GLib-GObject-CRITICAL **: g_object_unref: assertion 'G_IS_OBJECT (object)' failed
Error connecting to the udisks daemon: Error calling StartServiceByName for org.freedesktop.UDisks2: GDBus.Error:org.freedesktop.DBus.Error.TimedOut: Activation of org.freedesktop.UDisks2 timed out

Coud this be the underlying cause of the problem?

@Alexander: no idea. :-|

I can confirm that killing and restarting daemons can give you problem if you don't logout and login again... for example, restarting gnome-shell sometime makes shutdown/reboot form the menu impossible.

Quite lost...

I have dome more tests, but I could not find the conditions under which it worked some days ago.
Summarizing, no automatic mount of USB drives. Anyone can give some hint on debugging it?

I would like to say that after an update 3 days ago I no longer have the problems anymore. I have tried multiple times to mount and unmount with some reboots in between.
@Romano: I hope you get your problems resolved soon.

After the upgrade it worked for me during a couple of days. Then it stopped again... and is still not working.

Is anyone having the issue under unity or is that gnome-shell specific? Could you attach the ~/.cache/upstart/gnome-settings-daemon.log when that's happening?

Tried right now --- this boot/login it is working, and I have the following in ~/.cache/upstart/gnome-settings-daemon.log

(gnome-settings-daemon:1896): color-plugin-WARNING **: failed to connect to device: Failed to connect to missing device /org/freedesktop/ColorManager/devices/cups_PDF

...and nothing more. (Is this file flushed all the time or I am supposed to enter/exit the session?)

I have the saved file from yesterday (I suppose, it seems that file there are rotated) when the automounting did not work. The content is attached.

Hope this helps. I will try to check the log file when the problem surfaces again.

Have similar issue, automount doesn't work but can mount device manually. Ubuntu 13.10 UNITY

could somebody run "gvfs-mount -o", connect the device and copy the log there?

Today is a no-working day. I still am not able to determine a pattern for when it works and when no...

Done:

(0)samsung-romano:~% gvfs-mount -o

(gvfs-mount:10000): GVFS-RemoteVolumeMonitor-WARNING **: remote volume monitor with dbus name org.gtk.Private.UDisks2VolumeMonitor is not supported
Monitoring events. Press Ctrl+C to quit.

Nothing happens when I connect my disk. In the syslog I have the disk detected:

SYS: Nov 7 16:47:53 samsung-romano kernel: [11768.047108] usb 3-1: new high-speed USB device number 3 using xhci_hcd
SYS: Nov 7 16:47:53 samsung-romano kernel: [11768.076016] usb 3-1: New USB device found, idVendor=059b, idProduct=0470
SYS: Nov 7 16:47:53 samsung-romano kernel: [11768.076027] usb 3-1: New USB device strings: Mfr=10, Product=11, SerialNumber=5
SYS: Nov 7 16:47:53 samsung-romano kernel: [11768.076033] usb 3-1: Product: Storage
SYS: Nov 7 16:47:53 samsung-romano kernel: [11768.076038] usb 3-1: Manufacturer: Iomega
SYS: Nov 7 16:47:53 samsung-romano kernel: [11768.076042] usb 3-1: SerialNumber: 6E34633FFFFF
SYS: Nov 7 16:47:53 samsung-romano kernel: [11768.078192] scsi7 : usb-storage 3-1:1.0
SYS: Nov 7 16:47:53 samsung-romano mtp-probe: checking bus 3, device 3: "/sys/devices/pci0000:00/0000:00:1c.4/0000:04:00.0/usb3/3-1"
SYS: Nov 7 16:47:53 samsung-romano mtp-probe: bus: 3, device: 3 was not an MTP device
SYS: Nov 7 16:47:54 samsung-romano kernel: [11769.116539] scsi 7:0:0:0: Direct-Access ST950032 5AS PQ: 0 ANSI: 2 CCS
SYS: Nov 7 16:47:54 samsung-romano kernel: [11769.118070] sd 7:0:0:0: Attached scsi generic sg3 type 0
SYS: Nov 7 16:47:54 samsung-romano kernel: [11769.118415] sd 7:0:0:0: [sdc] 976773168 512-byte logical blocks: (500 GB/465 GiB)
SYS: Nov 7 16:47:54 samsung-romano kernel: [11769.119367] sd 7:0:0:0: [sdc] Write Protect is off
SYS: Nov 7 16:47:54 samsung-romano kernel: [11769.119381] sd 7:0:0:0: [sdc] Mode Sense: 28 00 00 00
SYS: Nov 7 16:47:54 samsung-romano kernel: [11769.120297] sd 7:0:0:0: [sdc] No Caching mode page present
SYS: Nov 7 16:47:54 samsung-romano kernel: [11769.120305] sd 7:0:0:0: [sdc] Assuming drive cache: write through
SYS: Nov 7 16:47:54 samsung-romano kernel: [11769.123622] sd 7:0:0:0: [sdc] No Caching mode page present
SYS: Nov 7 16:47:54 samsung-romano kernel: [11769.123631] sd 7:0:0:0: [sdc] Assuming drive cache: write through
SYS: Nov 7 16:47:54 samsung-romano kernel: [11769.189055] sdc: sdc1 sdc2
SYS: Nov 7 16:47:54 samsung-romano kernel: [11769.191958] sd 7:0:0:0: [sdc] No Caching mode page present
SYS: Nov 7 16:47:54 samsung-romano kernel: [11769.191969] sd 7:0:0:0: [sdc] Assuming drive cache: write through
SYS: Nov 7 16:47:54 samsung-romano kernel: [11769.191977] sd 7:0:0:0: [sdc] Attached SCSI disk

There is something really strange going on here. After the test above, I logged out. Next, on the login screen (gdm here), there wasn't my name-icon. I logged in by using "not listed here..." option.
Login was much faster than normal now, and the automount is working this time.

(0)samsung-romano:~% gvfs-mount -o
Monitoring events. Press Ctrl+C to quit.
Drive connected: 'ST9500325AS'
Drive changed: 'ST9500325AS'
Drive changed: 'ST9500325AS'
Volume added: 'IOMEGA'
Volume added: 'movlin'
Volume changed: 'movlin'
Mount added: 'movlin'
Volume changed: 'IOMEGA'
Mount added: 'IOMEGA'

So the main difference from gvfs-mount -o is the error:

(gvfs-mount:10000): GVFS-RemoteVolumeMonitor-WARNING **: remote volume monitor with dbus name org.gtk.Private.UDisks2VolumeMonitor is not supported

which happens when the automount is *not* working.

 The issue you are reporting is an upstream one and it would be nice if somebody having it could send the bug to the developers of the software by following the instructions at https://wiki.ubuntu.com/Bugs/Upstream/GNOME. If you have done so, please tell us the number of the upstream bug (or the link), so we can add a bugwatch that will inform us about its status. Thanks in advance.

Reported upstream --- I hope it helps.

Status changed to 'Confirmed' because the bug affects multiple users.

This also affects me.
I have a brand new installation of plain Xubuntu 13.10 (XFCE) with no Unity or Gnome.

Like the other commenters dmesg reports that udisks recognise the drive correctly, and I can mount it manually with udisksctrl mount -b /dev/sdb1 but it doesn't mount automatically. Not even the same drive twice in the same session.

[169444.283673] usb 3-6: new high-speed USB device number 13 using xhci_hcd
[169444.321253] usb 3-6: New USB device found, idVendor=0939, idProduct=0b15
[169444.321260] usb 3-6: New USB device strings: Mfr=2, Product=3, SerialNumber=1
[169444.321265] usb 3-6: Product: StorE HDD
[169444.321269] usb 3-6: Manufacturer: Toshiba
[169444.321273] usb 3-6: SerialNumber: 2010122931CF
[169444.323003] usb-storage 3-6:1.0: USB Mass Storage device detected
[169444.323084] scsi13 : usb-storage 3-6:1.0
[169446.491233] scsi 13:0:0:0: Direct-Access Toshiba StorE HDD 0000 PQ: 0 ANSI: 4
[169446.491653] sd 13:0:0:0: Attached scsi generic sg2 type 0
[169446.495383] sd 13:0:0:0: [sdb] 625142448 512-byte logical blocks: (320 GB/298 GiB)
[169446.501667] sd 13:0:0:0: [sdb] Write Protect is off
[169446.501674] sd 13:0:0:0: [sdb] Mode Sense: 38 00 00 00
[169446.507951] sd 13:0:0:0: [sdb] No Caching mode page found
[169446.507959] sd 13:0:0:0: [sdb] Assuming drive cache: write through
[169446.521256] sd 13:0:0:0: [sdb] No Caching mode page found
[169446.521265] sd 13:0:0:0: [sdb] Assuming drive cache: write through
[169446.545609] sdb: sdb1
[169446.559319] sd 13:0:0:0: [sdb] No Caching mode page found
[169446.559330] sd 13:0:0:0: [sdb] Assuming drive cache: write through
[169446.559337] sd 13:0:0:0: [sdb] Attached SCSI disk
chris@xenon:~/Pictures$ udisksctl mount -b /dev/sdb1
Mounted /dev/sdb1 at /media/chris/USB-HDD.

I also have this problem and if it is the same bug I have narrowed it down to "lightdm".

I am using Mint 17 (based on Ubuntu 14.04). Mint's default login manager is "mdm" (fork of gdm). With it, usb devices are auto-mounted just fine when plugged in.

When I install lightdm and choose it as the login manager, after reboot then devices *do not auto-mount anymore*. Just as the previous poster, the dmesg output shows that the device is correctly found and attached, but not mounted. When I click on the device in Nautilus or Nemo, it will then mount just fine, but it needs this manual interaction.

If I then uninstall lightdm, choosing mdm again as the display manager, upon reboot the auto-mounting of usb devices works just fine again.

So.... it must be something in lightdm for me. A udev rule not finishing somehow triggered by lightdm? An upstart trigger involving lightdm that hangs things up? Any advice on where to look from here appreciated.

@romano-giannetti I see now that you indicate you are not using lightdm. Can you confirm your login manager? If so we may have a different problem, but everything else seems identical.

I can confirm that when it happened to me, I had gdm as login manager and not lightdm.

Since the upgrade to 14.04, it happened just one time in one laptop (solved by login/logout) with Ubuntu Gnome, and never in my other laptop which has Xubuntu.

So for me it is happening now very rarely; last time I seen it was more than a month ago --- I can't remember. My guess is that the DBUS connection between udidskd and the desktop get lost, or stuck. Probably related to the DM, yes. Would not be surprising if lightdm and gdm share some bug.