Skip to main content ↑ ↓
Topic: udiskie has decided not to work (sometime in the past...) (Read 1489 times) previous topic - next topic
0 Members and 1 Guest are viewing this topic.

udiskie has decided not to work (sometime in the past...)

I don't know when this problem occurred as I'm currently rarely using external media on my notebook.

I reinstalled, checked that it was still being called from the ~/.xinitrc  file. Rebooted & such. Really, I don't know why it has decided to fail to operate. I've not made any great changes to my system for a while now?

Any help will be gratefully appreciated. :)

Re: udiskie has decided not to work (sometime in the past...)

Reply #1 –
I've re/moved this post (which was a script that allows me to work around this issue) to the Tutorials & HOWTOs section:

https://forum.artixlinux.org/index.php/topic,452.0.html

[edit:] Its now 2 scripts pm.sh for mounting & pum.sh for unmounting. :)

Re: udiskie has decided not to work (sometime in the past...)

Reply #2 –
I would check the groups your user is assigned to.

EDIT: Actually give directions, lol.

Code: [Select]
[localhost ᒤᕞᕹᓸ]# groups ᒤᕞᕹᓸ
adm disk lp wheel network video audio optical storage scanner power kvm weston-launch ᒤᕞᕹᓸ

So use:

groups username

Re: udiskie has decided not to work (sometime in the past...)

Reply #3 –
@ruby I think my groups are OK

Code: [Select]
lp wheel network video optical storage scanner power users autologin handy

Beyond that in a moment I'll make some edits to my previous post & then copy it over to the Tutorials section & delete the post in this thread. Also, I quite like using this script & pmount (with Worker thrown in to call both pmount/pumount from a couple of buttons - kind of like aliases that you push with a mouse button ;) ).

Re: udiskie has decided not to work (sometime in the past...)

Reply #4 –
@handy

Well, I figured we would start with the usual offender. I doubt being added to the group 'disk' would help. I understand 'adm' 'adbusers' is necessary for android mounting, but again probably not for your needs.

Hmm, could you need systemd-dummy or libsystemd-dummy?

I read others had this issue for gnome-disk-utility and I needed it for E22. Maybe it will help?

udiskie and gvfs-* are working fine over here.

EDIT: Fiddlesticks, wrong name.

Re: udiskie has decided not to work (sometime in the past...)

Reply #5 –
@ruby I already have both of the dummy files installed.

I dunno?  ;)

I removed udiskie from my machine last night, as I'm really quite happy using my pmount script. :D

A lot simpler (lighter) & should be more reliable because of it. The most likely thing I could see going wrong with it is if the python people make changes that upset Joshua's line of python magic that I'm using to put a live cursor on an echoed command line.

I reckon it should be good for some time though... ;)

Re: udiskie has decided not to work (sometime in the past...)

Reply #6 –
I don't know then. Still, if your solution works and you like it, all the more power to you. :) Not to mention you have a lighter system thanks to it.

Maybe the devs will have a better idea of what we are missing for others who run into this problem.

Re: udiskie has decided not to work (sometime in the past...)

Reply #7 –
I think that I may know what has happened. (kind'a)

Since removing udiskie Worker (which uses udisks2) now offers to mount & cd to the mounted USB/ext partition when it is attached or powered on. It used to do this when udiskie was installed & functioning (for years) , but it hasn't been in my recent experiences, until after I removed udiskie & rebooted the machine (overnight).

So,  perhaps an update to Worker or udiskie or some other package(s)? has caused them to get in each others way somehow?

Best I can do. :)

Anyway, now I have Worker (my IT front end interface) doing what it used to do, & I have an alternative with the scripts that are a great backup that I'd be happy to use as my sole means of un/mounting external media.

It gave me something to do for some hours... ;)

(I can't really mark it as solved, as udiskie doesn't work.)

Re: udiskie has decided not to work (sometime in the past...)

Reply #8 –
Handy udisie has not worked under runit or openrc, using a WM  for a while. the work around for me was to add this to startup,  dbus-launch your file manager --desktop -d    then all was fine on DE thing were fine.
I don't know if this helps.

Re: udiskie has decided not to work (sometime in the past...)

Reply #9 –
@mandog Hi mandog, I'm pretty sure that udiskie did work when I installed it. I had the tray icon & all that & I believe I did unmount drives with it. Worker mounts them for me via udisks2.

Anyway, as you likely read in my previous post, since I've removed udiskie, Worker is doing what it used to do (giving me the option to mount; mount & CD; or do nothing to newly connected drives/partitions).

I've just modified Worker to use pmount/pumount by default (haven't tested it yet), if it works it will mean that I can easily highlight a pmounted device in /media & then push a button in Worker to have pumount, unmount it. This will be nice to use with devices that Worker auto-mounts for me.

Anyway, all's good mandog. I'm content with the way my system is functioning at the moment. :)

Re: udiskie has decided not to work (sometime in the past...)

Reply #10 –
Glad your solution works for you, I can't remember when udiskie stopped working but it was at the same time it stopped with obarun not to long ago.
The great thing is if one fix does not work then try the other the great thing about Linux always a work around.
 

Re: udiskie has decided not to work (sometime in the past...)

Reply #11 –
@mandog Yes that is something that suits many of us about the GNU-Linux & BSD systems. You can make your system be more or less just the way that you want it to be. It makes using Windows & especially OS/X feel so confined & limiting (apart from all that secret binary stuff that you can't get at or modify with .config files of some sort).  (I still haven't tested whether pmount works in Worker...)