not automounting anymore?! about udiskie HOT 13 CLOSED

Hey,

sorry to hear there are problems. Can you give me some more details, i.e. run udiskie -v and insert your device. What is the output?

Thanks

from udiskie.

DEBUG [2014-07-03 17:22:27,530] udiskie.config: Failed to read config file: [Errno 2] No such file or directory: '/home/user01/.config/udiskie/config.yml'
DEBUG [2014-07-03 17:22:27,535] udiskie.config: Failed to read config file: [Errno 2] No such file or directory: '/home/user01/.config/udiskie/config.json'
DEBUG [2014-07-03 17:22:28,068] udiskie.config: IgnoreDevice(match={'is_block': False}, value=True) created
DEBUG [2014-07-03 17:22:28,068] udiskie.config: IgnoreDevice(match={'is_external': False}, value=True) created
DEBUG [2014-07-03 17:22:28,069] udiskie.config: IgnoreDevice(match={'is_ignored': True}, value=True) created
DEBUG [2014-07-03 17:22:28,076] udiskie.config: IgnoreDevice(match={'is_external': False}, value=True) used for /org/freedesktop/UDisks/devices/sda2
DEBUG [2014-07-03 17:22:28,076] udiskie.config: IgnoreDevice(match={'is_external': False}, value=True) used for /org/freedesktop/UDisks/devices/sda1
DEBUG [2014-07-03 17:22:28,077] udiskie.config: IgnoreDevice(match={'is_external': False}, value=True) used for /org/freedesktop/UDisks/devices/sdb1
DEBUG [2014-07-03 17:22:28,077] udiskie.config: IgnoreDevice(match={'is_external': False}, value=True) used for /org/freedesktop/UDisks/devices/sda
DEBUG [2014-07-03 17:22:28,077] udiskie.config: IgnoreDevice(match={'is_external': False}, value=True) used for /org/freedesktop/UDisks/devices/sda4
DEBUG [2014-07-03 17:22:28,077] udiskie.config: IgnoreDevice(match={'is_external': False}, value=True) used for /org/freedesktop/UDisks/devices/sda5
DEBUG [2014-07-03 17:22:28,078] udiskie.config: IgnoreDevice(match={'is_external': False}, value=True) used for /org/freedesktop/UDisks/devices/sda6
DEBUG [2014-07-03 17:22:28,078] udiskie.config: IgnoreDevice(match={'is_external': False}, value=True) used for /org/freedesktop/UDisks/devices/sda3
DEBUG [2014-07-03 17:22:28,078] udiskie.config: IgnoreDevice(match={'is_external': False}, value=True) used for /org/freedesktop/UDisks/devices/sdb
Traceback (most recent call last):
  File "/usr/lib/python3.4/site-packages/udiskie/dbus.py", line 196, in __call__
    return self._handler(*parameters.unpack())
  File "/usr/lib/python3.4/site-packages/udiskie/udisks1.py", line 595, in _device_added
    self.trigger('device_added', new_state)
  File "/usr/lib/python3.4/site-packages/udiskie/common.py", line 48, in trigger
    handler(*args)
  File "/usr/lib/python3.4/site-packages/udiskie/notify.py", line 124, in device_added
    'drive-removable-media').show()
gi._glib.GError: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.freedesktop.Notifications was not provided by any .service files

from udiskie.

This looks like no libnotify is found on your system.
Run udiskie -Nv to disable notifications, what is the output?

from udiskie.

DEBUG [2014-07-03 17:31:44,237] udiskie.config: Failed to read config file: [Errno 2] No such file or directory: '/home/user01/.config/udiskie/config.yml'
DEBUG [2014-07-03 17:31:44,240] udiskie.config: Failed to read config file: [Errno 2] No such file or directory: '/home/user01/.config/udiskie/config.json'
DEBUG [2014-07-03 17:31:44,787] udiskie.config: IgnoreDevice(match={'is_block': False}, value=True) created
DEBUG [2014-07-03 17:31:44,787] udiskie.config: IgnoreDevice(match={'is_external': False}, value=True) created
DEBUG [2014-07-03 17:31:44,787] udiskie.config: IgnoreDevice(match={'is_ignored': True}, value=True) created
DEBUG [2014-07-03 17:31:44,788] udiskie.config: IgnoreDevice(match={'is_external': False}, value=True) used for /org/freedesktop/UDisks/devices/sda2
DEBUG [2014-07-03 17:31:44,788] udiskie.config: IgnoreDevice(match={'is_external': False}, value=True) used for /org/freedesktop/UDisks/devices/sda1
DEBUG [2014-07-03 17:31:44,788] udiskie.config: IgnoreDevice(match={'is_external': False}, value=True) used for /org/freedesktop/UDisks/devices/sda4
DEBUG [2014-07-03 17:31:44,788] udiskie.config: IgnoreDevice(match={'is_external': False}, value=True) used for /org/freedesktop/UDisks/devices/sda5
DEBUG [2014-07-03 17:31:44,788] udiskie.config: IgnoreDevice(match={'is_external': False}, value=True) used for /org/freedesktop/UDisks/devices/sdb
DEBUG [2014-07-03 17:31:44,788] udiskie.config: IgnoreDevice(match={'is_external': False}, value=True) used for /org/freedesktop/UDisks/devices/sda
DEBUG [2014-07-03 17:31:44,788] udiskie.config: IgnoreDevice(match={'is_external': False}, value=True) used for /org/freedesktop/UDisks/devices/sda3
DEBUG [2014-07-03 17:31:44,789] udiskie.config: IgnoreDevice(match={'is_external': False}, value=True) used for /org/freedesktop/UDisks/devices/sdb1
DEBUG [2014-07-03 17:31:44,789] udiskie.config: IgnoreDevice(match={'is_external': False}, value=True) used for /org/freedesktop/UDisks/devices/sda6
DEBUG [2014-07-03 17:31:50,366] udiskie.mount: mounting /org/freedesktop/UDisks/devices/sdc with {'fstype': 'ntfs', 'options': None}
INFO [2014-07-03 17:31:50,411] udiskie.mount: mounted /org/freedesktop/UDisks/devices/sdc on /media/usb

Wow. This was fast. Thanks man. But I cant remember that i ever installed (or uninstalled) libnotify. On two of my arch machines. Weird.

Thanks again! :)

EDIT
libnotify IS/WAS installed (libnotify 0.7.6-1)

from udiskie.

Did you run udiskie with --suppress (or -s) before? I renamed the command line options in version 1.0.0 for more consistency. Sorry, if this messed you up. Anyway, I'm glad it is working now.

Otherwise, if you did receive notifications before, we can try to figure out, why this is not working with the new notification backend.

from udiskie.

I never received notifications. To be honest I have no idea how they should look like. Neither did I use the --suppress flag. But according to your help -s is not --suppress but --smart-tray! (Which I havent used either.) I do start udiskie via my .xinit with udiskie &. I think I will just change it to udiskie -N & since I dont need tray or notification.

On the other hand if this is a problem I am keen to help you. So if I can provide more information about that topic just let me know.

from udiskie.

Before 1.0.0 the option was called -s, now it is -N. I was just asking if the renaming of command line parameter caused this problem.

If this is not really a problem for you, I will leave it at that for now. But just out of curiosity, which window manager are you using?

from udiskie.

Ahh, ok, I get it!
And no, its no problem at all - but I think this may be an ArchLinux Problem. So maybe more people will come crying for help! ;)
i3wm - you are right, this may be the cause for the "no notification" problem.

Great work btw. hanks!

from udiskie.

By the way: I doubt this is a distribution related problem, since I am running arch too. I have no problems receiving notifications on awesome (and I tried with mate as well). Maybe you have no notification daemon installed (such as dunst, mate-notification-daemon, notify-osd).

Best regards,

Thomas

from udiskie.

That is true, I have no notification daemon installed. But the problem is not that I didnt get notifications, but that udieskie seems not to automount if it cant send notifications. That is weird because it worked before, and I have never had any notification daemon installed.

Long story short: udiskie (on my system) does not automount if it cant send a notification.

from udiskie.

This is not surprising since your output shows that an exception was raised (before the automount handler gets invoked). In previous version of udiskie another libnotify binding was used, which probably just didn't raise an exception if no service was found.

EDIT: This probably stems from the newly introduced 'device_added' notification. This is shown in the same mainloop iteration as the automount handler is invoked and can therefore break it if raising an exception.

from udiskie.

My devices aren't getting automounted anymore: I'd suspect that I'm making a stupid mistake, but I haven't intentionally made any intentional changes (not that this excuses me). Here is the diagnostic help that occurs to me:

Linux linux-2lle.suse 4.4.165-81-default #1 SMP Mon Dec 3 07:47:23 UTC 2018 (0bfc9ed) x86_64 x86_64 x86_64 GNU/Linux
Traceback (most recent call last):
File "/usr/bin/udiskie", line 6, in
from udiskie.cli import Daemon
File "/usr/lib/python3.4/site-packages/udiskie/cli.py", line 211
async def _start_async_tasks(self):
^
SyntaxError: invalid syntax
processor : 0
vendor_id : GenuineIntel
cpu family : 6
model : 23
model name : Intel(R) Core(TM)2 Duo CPU P7350 @ 2.00GHz
stepping : 6
microcode : 0x60f
cpu MHz : 2000.000
cache size : 3072 KB
physical id : 0
siblings : 2
core id : 0
cpu cores : 2
apicid : 0
initial apicid : 0
fpu : yes
fpu_exception : yes
cpuid level : 10
wp : yes
flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx lm constant_tsc arch_perfmon pebs bts rep_good nopl aperfmperf eagerfpu pni dtes64 monitor ds_cpl est tm2 ssse3 cx16 xtpr pdcm sse4_1 lahf_lm dtherm kaiser
bugs : cpu_meltdown spectre_v1 spectre_v2 spec_store_bypass l1tf
bogomips : 3990.00
clflush size : 64
cache_alignment : 64
address sizes : 36 bits physical, 48 bits virtual
power management:

processor : 1
vendor_id : GenuineIntel
cpu family : 6
model : 23
model name : Intel(R) Core(TM)2 Duo CPU P7350 @ 2.00GHz
stepping : 6
microcode : 0x60f
cpu MHz : 800.000
cache size : 3072 KB
physical id : 0
siblings : 2
core id : 1
cpu cores : 2
apicid : 1
initial apicid : 1
fpu : yes
fpu_exception : yes
cpuid level : 10
wp : yes
flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx lm constant_tsc arch_perfmon pebs bts rep_good nopl aperfmperf eagerfpu pni dtes64 monitor ds_cpl est tm2 ssse3 cx16 xtpr pdcm sse4_1 lahf_lm dtherm kaiser
bugs : cpu_meltdown spectre_v1 spectre_v2 spec_store_bypass l1tf
bogomips : 3990.00
clflush size : 64
cache_alignment : 64
address sizes : 36 bits physical, 48 bits virtual
power management:

from udiskie.

Hey, your exception shows that you're using python 3.4 with a udiskie version that requires 3.5+. I did not post an official release with this backward breakage so far, so I assume you either installed it manually from github or you should notify your package maintainer about the package being broken.

from udiskie.