-
Notifications
You must be signed in to change notification settings - Fork 53
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
python messages about dbus.py and udisks2.py #272
Comments
+1 same here |
I am also facing this, seemingly with mounting rather than unmounting however. My instance is also launched automatically in my sway config, with |
Thanks for reporting. Should be easy to fix. |
- add bash completions for CLI options (thanks @oersen) - updates for translations - added German translation - add bright outlines for wayland icons in dark themes - ignore snap loop devices by default - maintenance on CI workflows - fix KeyError when properties are invalidated multiple times (#272)
- add bash completions for CLI options (thanks @oersen) - updates for translations - added German translation - add bright outlines for wayland icons in dark themes - ignore snap loop devices by default - maintenance on CI workflows - fix KeyError when properties are invalidated multiple times (#272)
Reopening since this error is not actually fixed. Running version 2.5.1.1. Mounting and unmounting works flawless but still this message persists. Running udiskie & without any configuration.
|
Hi @JostBrand. Is it possible that you are still somehow running an old version (local user pip install or something)? Did you do |
you are right ! I think I played with the dangerous break system packages and my shell preferred the pip install over the pacman version. Sorry! |
When I issue the comand "udiskie-umount -d mountpoint" it gives me:
and it does the job (ie. the device is unmounted and powered off).
I'm with udiskie version 2.4.2 on Arch (updated yesterday). Udiskie is lauched when i log in with "udiskie -aNT &" by i3-wm.
The text was updated successfully, but these errors were encountered: