You are not logged in.


Okay, so that fixed gvfs/udisks. Try restarting the desktop to see if it helps:
xfdesktop -Q
xfdesktop &Mark solved threads as [SOLVED] to make it easier for others to find solutions.
--- How To Ask For Help | FAQ | Developer Wiki | Community | Contribute ---
Offline


The first command returned the prompt and messed up my ability to change workspaces. The second one returned the drive icons to their place on the desktop.
Looks like the problem was diagnosed correctly by you and appears to be a timing issue. What do we do now to permanently fix that timing for the next and subsequent boots?
Offline


Looks like the problem was diagnosed correctly by you and appears to be a timing issue. What do we do now to permanently fix that timing for the next and subsequent boots?
It looks like in your log file, that dbus is starting udisks2. Lets force udisks2 to start on boot by itself so that it doesn't rely on dbus to start (in case there is a delay there). Run this command:
sudo systemctl enable udisks2.service...then reboot. See if this resolves the issue.
Mark solved threads as [SOLVED] to make it easier for others to find solutions.
--- How To Ask For Help | FAQ | Developer Wiki | Community | Contribute ---
Offline


Okay, but I won't right now because it takes awhile, and because we would not know right away anyway because of the nature of the problem being hit or miss in the past.
But thank you. I will try over the next few days to see if all is good and then report back.
Thanks for all your good diagnostic help. Much appreciated.
Added later 4 h 01 min 26 s:
BTW, Thunar still does not see the drives. I will see if they appear after reboot, but would have thought they would show up after the desktop displayed them.
Thanks.
Offline


I'm experiencing this now.
Thunar 4.20.8
Not sure how to diagnose this as I don't have systemd
Offline


I'm experiencing this now.
Thunar 4.20.8
Not sure how to diagnose this as I don't have systemd
With whichever init system you are using, make sure that the udisks2 service/init starts before gvfs/gio.
Mark solved threads as [SOLVED] to make it easier for others to find solutions.
--- How To Ask For Help | FAQ | Developer Wiki | Community | Contribute ---
Offline


It was working and then it stopped this AM. Not sure what to do now. The drives are mounted under /mnt but not showing under Thunar. My 120GB did not show up at all. Looked into Disks, and found it there. Went ahead and mounted it and then Thunar saw it.
Offline


Add /usr/libexec/udisks2/udisksd --replace &
at the end of the /etc/rc.d/rc.local file and rebootRestarted then plugged in drive and it appeared.
Will update if anything changes
Offline


It was working and then it stopped this AM. Not sure what to do now. The drives are mounted under /mnt but not showing under Thunar. My 120GB did not show up at all. Looked into Disks, and found it there. Went ahead and mounted it and then Thunar saw it.
Try commenting out the entries in /etc/fstab and seeing if gvfs itself can mount these devices for you (you may need to click on them to mount them).
The second option would be to mount them to /media and not /mnt - I read somewhere that /mnt is not to be used for permanent mounts like this (it is for temporary mounts only by admins). Make sure you first create the /media folder.
Mark solved threads as [SOLVED] to make it easier for others to find solutions.
--- How To Ask For Help | FAQ | Developer Wiki | Community | Contribute ---
Offline


Thanks, ToZ.
The drives are already mounted under /mnt. My cdrom always goes to /media, so it always exists.
The idea of selecting where drives are mounted seems counterintuitive to the normal use of the OS (Debian 12). I am not understanding what I should be doing that others don't, or why.
Is there a suggestion that other processes can or should handling the automatic mounting of drives? I wish I knew more about the underlying operation(s) of the OS.
BTW, isn't this still a Xfce environment issue?
Last edited by KitchM (Today 17:45:13)
Offline
[ Generated in 0.011 seconds, 7 queries executed - Memory usage: 580.32 KiB (Peak: 597.3 KiB) ]