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 ---
Online


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 ---
Online


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 ---
Online


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 ---
Online


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 (2026-10-14 17:45:13)
Offline


I don't think its necessarily an Xfce issue - it may be more related to the supplementary libraries/apps that Xfce relies on (e.g. gvfs/udisks2). What I'm suggesting is that you can try some options to see if they help, or at least help to further diagnose the problem.
The first thing to try would be to comment out the /mnt mounts in your /etc/fstab file and reboot (if nothing changes, you can always uncomment them to return to where you were). This will let gvfs handle the mounting (as opposed to fstab) so we can see if this works better.
Mark solved threads as [SOLVED] to make it easier for others to find solutions.
--- How To Ask For Help | FAQ | Developer Wiki | Community | Contribute ---
Online


Very interesting, and it is a good diagnostic. I'll do it. But wouldn't you know it; they came back normally today.
Added later 13 h 33 min 50 s:
Well, that test was an exercise in frustration. The first thing that happened was that the drive icons were on the desktop but they were not mounted.
Right-click on one and choose to mount caused them all to mount. Except for one. And it was one of the four that always mounted under /mnt.
In trying to mount that one, an error message came up that stated: Failed to mount "Storage"
No object for D-Bus interface
Thunar could not mount it, but Disks could.
This played havoc with my password safe. It did not recognize the pathname where its key file was supposed to be located; it needed that unique location.
I have had some trouble with my CD/DVD drive; it may be failing. Still even when not immediately accessible, it had always showed mounted before and eventually could display its contents. But not now. It could not be mounted, even trying for minutes. It eventually displayed an error message that actually interrupted my attempt to reboot:
Failed to mount "3428"
Error mounting system-managed device /dev/sr0: wrong fs type, bad option, bad superblock on /dev/sr0, missing codepage or helper program or other error.
Go figure. I immediately redid fstab and got it back like it was before.
Offline


I think I just figured it out. The issue of timing is exactly a fundamental factor in this problem. I have five solid state drives (SSDs). One is a NVMe (Non-Volatile Memory Express) drive (M.2 form factor) that is the motherboard-mounted main boot drive of the system; this one always works and does not appear on the desktop. The other four are mounted in a 5.45" hot-swap drive bay.
I believe that the timing issue is associated with those drives in that quad drive bay, and that the bay's circuitry is a little slow to be recognized by the rest of the system. While each one has its own cable from the motherboard, the bay is hot-swapable. This may, in some way, be causing a slight slow-down in recognition. Or at least that appears to be a possibility in some way.
Anyway, that's what I've come up with so far.
Offline
[ Generated in 0.018 seconds, 7 queries executed - Memory usage: 614.3 KiB (Peak: 631.69 KiB) ]