Caja error.... will not umount without a 45 second delay- solved

bmike1 · 2021-10-29 21:28:24

Whenever I try to unmount a drive caja freezes and I have to force an exit? Is that an error with me? (configuration or something). discobered a coulple of days later that it is delayed by around 45 seconds.

Seth figured out that to fix it Installing https://archlinux.org/packages/community/x86_64/dunst did it.

Last edited by bmike1 (2021-10-31 19:30:49)

Trilby · 2021-10-29 22:25:46

If you were a brand new forum member, I'd highlight how there is no way we can help with this until you provide *some* information like running caja from a terminal to get any error output, or checking logs, or the journal, etc, etc. But you're not that new; you have had a handful of threads on these forums and in several of them you've been very politely encouraged to adjust your posting to our community norms and / or edit posts, titles, etc, and in every case you've completely ignored these requests. And yet you want this community to pay attention to your poorly presented question?

Try harder (on this question, and on going back and fixing your previous posts as has been requested of you by moderators and other community members).

Last edited by Trilby (2021-10-29 22:26:50)

jasonwryan · 2021-10-29 22:50:09

Trilby is, very politely, saying stop being a help vampire.

bmike1 · 2021-10-30 04:36:18

So sorry. I can only remember one time I was told to edit my post to make it conform to forum standards. That was when I was told to edit my subject and add the word solved to it (which I did).

In any case I forgot to run it from the terminal to get any errors. I'm really sorry but I ave a really bad memory from a brain trauma. Any ways; I started caja from a terminal then tried to unmount a drive. Unfortunately it did not produce any errors in the terminal. Actually, when caja was typed in and return was pressed the terminal went to the next line expecting another command. Is that normal with arch? I'm used to needing to type '<command>&' to get that type of behavior.

loqs · 2021-10-30 04:48:08

Please post the system journal for the relevant time period.
How exactly are you trying to umount a drive? Does the umount succeed? Could caja be using anything mounted from that drive?
When caja is frozen what state is its process in?

ps l -C caja

seth · 2021-10-30 06:59:31

On top of #5:

Caja will most likely not spawn a new process this way, but IPC a running process to spawn a new window.
You'll first have to "caja -q" and in doubt "pkill caja; pkill -9 caja" to get rid of running processes.

Also check whether some polkit agent is running:

ps aux | grep polkit

in case caja needs some credentials to unmount the device - which btw. was mounted how exactly?

bmike1 · 2021-10-30 12:19:35

[bmike1@HavensARCH ~]$ ps l -C caja
F UID PID PPID PRI NI VSZ RSS WCHAN STAT TTY TIME COMMAND
0 1000 531 430 20 0 1080832 66316 - Sl ? 0:01 /usr/bi
[bmike1@HavensARCH ~]$ caja
[bmike1@HavensARCH ~]$ ps l -C caja
F UID PID PPID PRI NI VSZ RSS WCHAN STAT TTY TIME COMMAND
0 1000 531 430 20 0 1104688 79396 - Sl ? 0:03 /usr/bi
[bmike1@HavensARCH ~]$ ps l -C caja
F UID PID PPID PRI NI VSZ RSS WCHAN STAT TTY TIME COMMAND
0 1000 531 430 20 0 1096492 79708 - Sl ? 0:03 /usr/bi
[bmike1@HavensARCH ~]$ caja
[bmike1@HavensARCH ~]$ ps aux | grep polkit
polkitd 314 0.1 0.2 2578212 23184 ? Ssl 08:09 0:00 /usr/lib/polkit-1/polkitd --no-debug
bmike1 543 0.0 0.3 228304 26520 ? Sl 08:10 0:00 /usr/lib/mate-polkit/polkit-mate-authentication-agent-1
bmike1 1041 0.0 0.0 6492 2492 pts/0 S+ 08:13 0:00 grep polkit
[bmike1@HavensARCH ~]$

How strange.... caja didn't freeze this time! As for the questions: I auto mount the drives and I umont them by clicking the little eject button in caja.
I'll restart the computer again and retry it.

Last edited by bmike1 (2021-10-30 12:48:38)

bmike1 · 2021-10-30 12:32:53

This time it froze again.
just started computer

[bmike1@HavensARCH ~]$ ps l -C caja
F UID PID PPID PRI NI VSZ RSS WCHAN STAT TTY TIME COMMAND
0 1000 963 436 20 0 1089044 65996 - Sl ? 0:01 /usr/bi

start caja

[bmike1@HavensARCH ~]$ ps l -C caja
F UID PID PPID PRI NI VSZ RSS WCHAN STAT TTY TIME COMMAND
0 1000 1056 436 20 0 1104560 80040 - Sl ? 0:03 /usr/bi

stop

[bmike1@HavensARCH ~]$ ps aux | grep polkit
polkitd 311 0.1 0.3 2578212 23988 ? Ssl 08:20 0:00 /usr/lib/polkit-1/polkitd --no-debug
bmike1 548 0.0 0.3 228300 26600 ? Sl 08:20 0:00 /usr/lib/mate-polkit/polkit-mate-authentication-agent-1
bmike1 1429 0.0 0.0 6492 2480 pts/0 R+ 08:25 0:00 grep polkit

start

[bmike1@HavensARCH ~]$ ps aux | grep polkit
polkitd 311 0.1 0.3 2578212 23988 ? Ssl 08:20 0:00 /usr/lib/polkit-1/polkitd --no-debug
bmike1 548 0.0 0.3 228300 26600 ? Sl 08:20 0:00 /usr/lib/mate-polkit/polkit-mate-authentication-agent-1
bmike1 1489 0.0 0.0 6492 2508 pts/0 S+ 08:25 0:00 grep polkit

stop

[bmike1@HavensARCH ~]$ pkill caja; pkill -9 caja

start

[bmike1@HavensARCH ~]$ pkill caja; pkill -9 caja
[bmike1@HavensARCH ~]$

Last edited by bmike1 (2021-10-30 12:58:59)

seth · 2021-10-30 12:59:40

You were supposed to kill caja in order to start an instance from an interactive shell that would (hopefully) not return immediately.
Cause if that doesn't help us, we'd next strace the process to see where it's hanging out while being frozen.

Did you run "ps l -C caja" while it was "frozen"? No listed process is waiting for I/O - what are the symptoms of caja being "frozen"?

bmike1 · 2021-10-30 18:30:56

seth wrote:

You were supposed to kill caja in order to start an instance from an interactive shell that would (hopefully) not return immediately.
Cause if that doesn't help us, we'd next strace the process to see where it's hanging out while being frozen.
Did you run "ps l -C caja" while it was "frozen"? No listed process is waiting for I/O - what are the symptoms of caja being "frozen"?

Starting caja was the first thing I did and it froze. Then ps | -C caja was run. The symptoms are that I can not start another program.. O ha yeah. I forgot to mention that after caja is killed the drive in unmounted.

seth · 2021-10-30 19:09:37

What do you mean by "can not start another program"? You can obviously run ps and kill etc.?

bmike1 · 2021-10-30 20:27:14

well, I can't start another program from the GUI (like gimp or darktable). I can start programs from the terminal though.... hmmm.... that is interesting (just discovered); umounting with caja does happen., only delayed by about 45 seconds.

seth · 2021-10-30 20:29:55

loginctl session-status
echo $DBUS_SESSION_BUS_ADDRESS

loqs · 2021-10-30 20:31:15

Also the journal for a boot please.

bmike1 · 2021-10-30 20:39:26

~]$ sudo loginctl session-status | curl -F 'f:1=<-' ix.io
[sudo] password for bmike1:
http://ix.io/3Dph

then that repeats a bunch of times though I don't know if the repeats are slightly different.

echo $DBUS_SESSION_BUS_ADDRESS
unix:path=/run/user/1000/bus

Last edited by bmike1 (2021-10-30 21:22:20)

bmike1 · 2021-10-30 20:45:20

loqs wrote:

Also the journal for a boot please.

please... how do I get that? 'cat <?>'?

loqs · 2021-10-30 20:48:45

bmike1 wrote:

loqs wrote:
Also the journal for a boot please.
please... how do I get that? 'cat <?>'?

See the link I posted in post #5. See the tip box from pastebin to post the output directly to a pastebin.
Please use code tags for commands and their outputs instead of quote tags.

bmike1 · 2021-10-30 20:55:23

Thank you, sir. I would post it into pastebin but it is so short there is no need:

ps l -C caja>freeze
[bmike1@HavensARCH ~]$ cat freeze
F UID PID PPID PRI NI VSZ RSS WCHAN STAT TTY TIME COMMAND
0 1000 1202 426 20 0 1100600 84452 - Sl ? 0:19 /usr/bin/caja
[bmike1@HavensARCH ~]$

Last edited by bmike1 (2021-10-30 20:57:01)

seth · 2021-10-30 20:56:45

sudo journalctl -b | curl -F 'f:1=<-' ix.io

After caja unmounted a device (after 45 seconds)

bmike1 · 2021-10-30 20:59:50

sudo journalctl -b | curl -F 'f:1=<-' ix.io
[url]http://ix.io/3Dp9[/url]

~]$ sudo loginctl session-status | curl -F 'f:1=<-' ix.io
[sudo] password for bmike1:
http://ix.io/3Dph

Last edited by bmike1 (2021-10-30 21:51:12)

bmike1 · 2021-10-30 22:16:12

[bmike1@HavensARCH ~]$ sudo journalctl --since "5 min ago"
[sudo] password for bmike1: 
Sorry, try again.
[sudo] password for bmike1: 
-- Journal begins at Thu 2021-10-14 00:31:23 EDT, ends at Sat 2021-10-30 18:14:>
Oct 30 18:12:06 HavensARCH dbus-daemon[457]: [session uid=1000 pid=457] Activat>
Oct 30 18:12:06 HavensARCH systemd[1]: run-media-bmike1-NUC\x20Backup.mount: De>
Oct 30 18:12:06 HavensARCH ntfs-3g[623]: Unmounting /dev/sdb1 (NUC Backup)
Oct 30 18:12:06 HavensARCH udisksd[530]: Cleaning up mount point /run/media/bmi>
Oct 30 18:12:06 HavensARCH udisksd[530]: Unmounted /dev/sdb1 on behalf of uid 1>
Oct 30 18:12:06 HavensARCH kernel: sdb: detected capacity change from 240353280>
Oct 30 18:12:42 HavensARCH systemd-networkd[225]: wlan0: Link DOWN
Oct 30 18:12:42 HavensARCH NetworkManager[273]: <info>  [1635631962.6670] devic>
Oct 30 18:12:42 HavensARCH kernel: iwlwifi 0000:02:00.0: Radio type=0x2-0x0-0x0
Oct 30 18:12:42 HavensARCH kernel: iwlwifi 0000:02:00.0: Radio type=0x2-0x0-0x0
Oct 30 18:12:43 HavensARCH systemd-networkd[225]: wlan0: Link UP
Oct 30 18:12:43 HavensARCH NetworkManager[273]: <info>  [1635631963.0289] devic>
Oct 30 18:12:43 HavensARCH NetworkManager[273]: <info>  [1635631963.0841] devic>
Oct 30 18:13:06 HavensARCH plasma_waitforname[1135]: org.kde.knotifications: Wa>
Oct 30 18:13:06 HavensARCH dbus-daemon[457]: [session uid=1000 pid=457] Activat>
Oct 30 18:13:55 HavensARCH sudo[1157]: pam_unix(sudo:auth): authentication fail>
Oct 30 18:13:55 HavensARCH dbus-daemon[272]: [system] Activating via systemd: s>
Oct 30 18:13:55 HavensARCH dbus-daemon[272]: [system] Activation via systemd fa>
Oct 30 18:13:55 HavensARCH sudo[1157]: pam_systemd_home(sudo:auth): systemd-hom>
Oct 30 18:13:55 HavensARCH audit[1157]: USER_AUTH pid=1157 uid=1000 auid=1000 s>
Oct 30 18:13:55 HavensARCH kernel: audit: type=1100 audit(1635632035.395:107): >
Oct 30 18:14:06 HavensARCH audit[1157]: USER_AUTH pid=1157 uid=1000 auid=1000 s>
lines 1-23

seth · 2021-10-31 06:52:35

Don't copy stuff out of the pager, that makes it even more useless.

From the actual journal you pasted before:

Oct 30 16:19:26 HavensARCH kernel: usb 2-1.1.2: USB disconnect, device number 12
Oct 30 16:19:28 HavensARCH kernel: usb 2-1.1.2: new high-speed USB device number 13 using ehci-pci
Oct 30 16:19:28 HavensARCH kernel: usb 2-1.1.2: New USB device found, idVendor=0781, idProduct=5581, bcdDevice= 1.00
Oct 30 16:19:28 HavensARCH kernel: usb 2-1.1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Oct 30 16:19:28 HavensARCH kernel: usb 2-1.1.2: Product: Ultra
Oct 30 16:19:28 HavensARCH kernel: usb 2-1.1.2: Manufacturer: SanDisk
Oct 30 16:19:28 HavensARCH kernel: usb 2-1.1.2: SerialNumber: 040127e361f1fbc434f7d8298a8b7244a1945ada2fd00aff525c07069a10c1191ed100000000000000000000d8cd36e5ff08b2188155810736a806de
Oct 30 16:19:28 HavensARCH kernel: usb-storage 2-1.1.2:1.0: USB Mass Storage device detected
Oct 30 16:19:28 HavensARCH kernel: scsi host6: usb-storage 2-1.1.2:1.0
Oct 30 16:19:28 HavensARCH mtp-probe[2182]: checking bus 2, device 13: "/sys/devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.1/2-1.1.2"
Oct 30 16:19:28 HavensARCH mtp-probe[2182]: bus: 2, device: 13 was not an MTP device
Oct 30 16:19:28 HavensARCH mtp-probe[2183]: checking bus 2, device 13: "/sys/devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.1/2-1.1.2"
Oct 30 16:19:28 HavensARCH mtp-probe[2183]: bus: 2, device: 13 was not an MTP device
Oct 30 16:19:29 HavensARCH kernel: scsi 6:0:0:0: Direct-Access     SanDisk  Ultra            1.00 PQ: 0 ANSI: 6
Oct 30 16:19:29 HavensARCH kernel: sd 6:0:0:0: [sdb] 240353280 512-byte logical blocks: (123 GB/115 GiB)
Oct 30 16:19:29 HavensARCH kernel: sd 6:0:0:0: [sdb] Write Protect is off
Oct 30 16:19:29 HavensARCH kernel: sd 6:0:0:0: [sdb] Mode Sense: 43 00 00 00
Oct 30 16:19:29 HavensARCH kernel: sd 6:0:0:0: [sdb] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA
Oct 30 16:19:29 HavensARCH kernel:  sdb: sdb1
Oct 30 16:19:29 HavensARCH kernel: sd 6:0:0:0: [sdb] Attached SCSI removable disk
Oct 30 16:19:29 HavensARCH ntfs-3g[2187]: Version 2021.8.22 external FUSE 29
Oct 30 16:19:29 HavensARCH ntfs-3g[2187]: Mounted /dev/sdb1 (Read-Write, label "NUC Backup", NTFS 3.1)
Oct 30 16:19:29 HavensARCH ntfs-3g[2187]: Cmdline options: rw,nodev,nosuid,uid=1000,gid=1000,windows_names,uhelper=udisks2
Oct 30 16:19:29 HavensARCH ntfs-3g[2187]: Mount options: nodev,nosuid,uhelper=udisks2,allow_other,nonempty,relatime,rw,default_permissions,fsname=/dev/sdb1,blkdev,blksize=4096
Oct 30 16:19:29 HavensARCH ntfs-3g[2187]: Global ownership and permissions enforced, configuration type 7
Oct 30 16:19:29 HavensARCH udisksd[504]: Mounted /dev/sdb1 at /run/media/bmike1/NUC Backup on behalf of uid 1000
Oct 30 16:19:34 HavensARCH dbus-daemon[430]: [session uid=1000 pid=430] Activating service name='org.freedesktop.Notifications' requested by ':1.48' (uid=1000 pid=1202 comm="/usr/bin/caja ")
Oct 30 16:19:34 HavensARCH systemd[1]: run-media-bmike1-NUC\x20Backup.mount: Deactivated successfully.
Oct 30 16:19:34 HavensARCH ntfs-3g[2187]: Unmounting /dev/sdb1 (NUC Backup)
Oct 30 16:19:34 HavensARCH udisksd[504]: Cleaning up mount point /run/media/bmike1/NUC Backup (device 8:17 is not mounted)
Oct 30 16:19:34 HavensARCH udisksd[504]: Unmounted /dev/sdb1 on behalf of uid 1000
Oct 30 16:19:35 HavensARCH kernel: sdb: detected capacity change from 240353280 to 0
Oct 30 16:20:00 HavensARCH gvfsd[2037]: Error calling org.gtk.vfs.MonitorClient.Changed(): Timeout was reached (g-io-error-quark, 24)
Oct 30 16:20:34 HavensARCH plasma_waitforname[2200]: org.kde.knotifications: WaitForName: Service was not registered within timeout
Oct 30 16:20:34 HavensARCH dbus-daemon[430]: [session uid=1000 pid=430] Activated service 'org.freedesktop.Notifications' failed: Process org.freedesktop.Notifications exited with status 1
Oct 30 16:21:52 HavensARCH kernel: usb 2-1.1.2: USB disconnect, device number 13
Oct 30 16:21:54 HavensARCH kernel: usb 2-1.1.2: new high-speed USB device number 14 using ehci-pci
Oct 30 16:21:54 HavensARCH kernel: usb 2-1.1.2: New USB device found, idVendor=0781, idProduct=5581, bcdDevice= 1.00
Oct 30 16:21:54 HavensARCH kernel: usb 2-1.1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Oct 30 16:21:54 HavensARCH kernel: usb 2-1.1.2: Product: Ultra
Oct 30 16:21:54 HavensARCH kernel: usb 2-1.1.2: Manufacturer: SanDisk
Oct 30 16:21:54 HavensARCH kernel: usb 2-1.1.2: SerialNumber: 040127e361f1fbc434f7d8298a8b7244a1945ada2fd00aff525c07069a10c1191ed100000000000000000000d8cd36e5ff08b2188155810736a806de
Oct 30 16:21:54 HavensARCH kernel: usb-storage 2-1.1.2:1.0: USB Mass Storage device detected
Oct 30 16:21:54 HavensARCH kernel: scsi host6: usb-storage 2-1.1.2:1.0
Oct 30 16:21:54 HavensARCH mtp-probe[2280]: checking bus 2, device 14: "/sys/devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.1/2-1.1.2"
Oct 30 16:21:54 HavensARCH mtp-probe[2280]: bus: 2, device: 14 was not an MTP device
Oct 30 16:21:54 HavensARCH mtp-probe[2281]: checking bus 2, device 14: "/sys/devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.1/2-1.1.2"
Oct 30 16:21:54 HavensARCH mtp-probe[2281]: bus: 2, device: 14 was not an MTP device
Oct 30 16:21:55 HavensARCH kernel: scsi 6:0:0:0: Direct-Access     SanDisk  Ultra            1.00 PQ: 0 ANSI: 6
Oct 30 16:21:55 HavensARCH kernel: sd 6:0:0:0: [sdb] 240353280 512-byte logical blocks: (123 GB/115 GiB)
Oct 30 16:21:55 HavensARCH kernel: sd 6:0:0:0: [sdb] Write Protect is off
Oct 30 16:21:55 HavensARCH kernel: sd 6:0:0:0: [sdb] Mode Sense: 43 00 00 00
Oct 30 16:21:55 HavensARCH kernel: sd 6:0:0:0: [sdb] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA
Oct 30 16:21:55 HavensARCH kernel:  sdb: sdb1
Oct 30 16:21:55 HavensARCH kernel: sd 6:0:0:0: [sdb] Attached SCSI removable disk
Oct 30 16:21:55 HavensARCH ntfs-3g[2285]: Version 2021.8.22 external FUSE 29
Oct 30 16:21:55 HavensARCH ntfs-3g[2285]: Mounted /dev/sdb1 (Read-Write, label "NUC Backup", NTFS 3.1)
Oct 30 16:21:55 HavensARCH ntfs-3g[2285]: Cmdline options: rw,nodev,nosuid,uid=1000,gid=1000,windows_names,uhelper=udisks2
Oct 30 16:21:55 HavensARCH ntfs-3g[2285]: Mount options: nodev,nosuid,uhelper=udisks2,allow_other,nonempty,relatime,rw,default_permissions,fsname=/dev/sdb1,blkdev,blksize=4096
Oct 30 16:21:55 HavensARCH ntfs-3g[2285]: Global ownership and permissions enforced, configuration type 7
Oct 30 16:21:55 HavensARCH udisksd[504]: Mounted /dev/sdb1 at /run/media/bmike1/NUC Backup on behalf of uid 1000
Oct 30 16:22:01 HavensARCH systemd-networkd[221]: wlan0: Link DOWN
Oct 30 16:22:01 HavensARCH NetworkManager[269]: <info>  [1635625321.6024] device (wlan0): set-hw-addr: set MAC address to F2:77:7A:86:D7:3B (scanning)
Oct 30 16:22:01 HavensARCH kernel: iwlwifi 0000:02:00.0: Radio type=0x2-0x0-0x0
Oct 30 16:22:01 HavensARCH kernel: iwlwifi 0000:02:00.0: Radio type=0x2-0x0-0x0
Oct 30 16:22:01 HavensARCH systemd-networkd[221]: wlan0: Link UP
Oct 30 16:22:01 HavensARCH NetworkManager[269]: <info>  [1635625321.9856] device (wlan0): supplicant interface state: inactive -> disconnected
Oct 30 16:22:01 HavensARCH NetworkManager[269]: <info>  [1635625321.9914] device (wlan0): supplicant interface state: disconnected -> inactive
Oct 30 16:22:02 HavensARCH dbus-daemon[430]: [session uid=1000 pid=430] Activating service name='org.freedesktop.Notifications' requested by ':1.48' (uid=1000 pid=1202 comm="/usr/bin/caja ")
Oct 30 16:22:02 HavensARCH systemd[1]: run-media-bmike1-NUC\x20Backup.mount: Deactivated successfully.
Oct 30 16:22:02 HavensARCH ntfs-3g[2285]: Unmounting /dev/sdb1 (NUC Backup)
Oct 30 16:22:02 HavensARCH udisksd[504]: Cleaning up mount point /run/media/bmike1/NUC Backup (device 8:17 is not mounted)
Oct 30 16:22:02 HavensARCH udisksd[504]: Unmounted /dev/sdb1 on behalf of uid 1000
Oct 30 16:22:02 HavensARCH kernel: sdb: detected capacity change from 240353280 to 0
Oct 30 16:22:27 HavensARCH gvfsd[2037]: Error calling org.gtk.vfs.MonitorClient.Changed(): Timeout was reached (g-io-error-quark, 24)
Oct 30 16:23:01 HavensARCH plasma_waitforname[2294]: org.kde.knotifications: WaitForName: Service was not registered within timeout
Oct 30 16:23:01 HavensARCH dbus-daemon[430]: [session uid=1000 pid=430] Activated service 'org.freedesktop.Notifications' failed: Process org.freedesktop.Notifications exited with status 1

1. Are we taking about "will not umount" or "will not umount this one specific device that shows up over and over again in the journal (SanDisk Ultra/"NUC Backup"/NTFS 3.1)?
2. From the subsequent errors, try to install and run https://archlinux.org/packages/community/x86_64/dunst/ and try again
3. Why is plasma-workspace installed? (Ok, because you want to log into plasma as well) and why is plasma_waitforname running (drawn in by kdeconnectd? didn't show up in the session status)?

bmike1 · 2021-10-31 19:19:54

1- Please explain not copying things out of the pager so I (hopefully) don't do it again.

2- We were talking about it not umounting any external drive without the eternal pause.

3- Installing https://archlinux.org/packages/community/x86_64/dunst did it! Thank you so much. How did you figure that out? I ask so I can learn how to figure out any subsequent problems I may (undoubtedly) have.

4- Plasma-workspace is installed because when I installed Arch I installed it with Mate desktop but after decided I wanted to run it with kde so I installed kde.? And plasma_waitforname is probably running for the same reason. I decided I wanted to do kde because for the past 20ish years I have run linux with Mate and I wanted to try something new.

seth · 2021-10-31 20:11:28

1. A pager is eg. "less" and journalctl uses it to allow you to navigate loooooong texts in the console.
When you copy-and-paste from it, the text gets truncated (because the pager limits it to the terminal size and allows you to navigate the visible part w/ eg. the arrow keys)

3.

Oct 30 16:22:02 HavensARCH udisksd[504]: Unmounted /dev/sdb1 on behalf of uid 1000

The device is actually unmounted now (immediately)

Oct 30 16:22:27 HavensARCH gvfsd[2037]: Error calling org.gtk.vfs.MonitorClient.Changed(): Timeout was reached (g-io-error-quark, 24)
Oct 30 16:23:01 HavensARCH plasma_waitforname[2294]: org.kde.knotifications: WaitForName: Service was not registered within timeout
Oct 30 16:23:01 HavensARCH dbus-daemon[430]: [session uid=1000 pid=430] Activated service 'org.freedesktop.Notifications' failed: Process org.freedesktop.Notifications exited with status 1

25 seconds later (which is the default dbus timeout) gvfsd times out and the other messages suggest that it failed to call/activate a notification service.
Having written a shitton of clumsy code, I know what dumb stuff you can find in other peoples code and in this case, from the messages and the symptoms, deduced that there's a synchronous dbus call in the caja GUI code (what is dumb/lazy) and since we already figured that the session bus is ok, it's because there simply is no notification service.
Dunst is one that will get the job done - mate has probably its own, though.

Edit: Please always remember to mark resolved threads by editing your initial posts subject - so others will know that there's no task left, but maybe a solution to find.
Thanks.

Last edited by seth (2021-10-31 20:11:50)

loqs · 2021-10-31 20:31:01

seth wrote:

25 seconds later (which is the default dbus timeout) gvfsd times out and the other messages suggest that it failed to call/activate a notification service.

Possibly https://gitlab.gnome.org/GNOME/libnotif … ion.c#L671

Arch Linux

#1 2021-10-29 21:28:24

Caja error.... will not umount without a 45 second delay- solved

#2 2021-10-29 22:25:46

Re: Caja error.... will not umount without a 45 second delay- solved

#3 2021-10-29 22:50:09

Re: Caja error.... will not umount without a 45 second delay- solved

#4 2021-10-30 04:36:18

Re: Caja error.... will not umount without a 45 second delay- solved

#5 2021-10-30 04:48:08

Re: Caja error.... will not umount without a 45 second delay- solved

#6 2021-10-30 06:59:31

Re: Caja error.... will not umount without a 45 second delay- solved

#7 2021-10-30 12:19:35

Re: Caja error.... will not umount without a 45 second delay- solved

#8 2021-10-30 12:32:53

Re: Caja error.... will not umount without a 45 second delay- solved

#9 2021-10-30 12:59:40

Re: Caja error.... will not umount without a 45 second delay- solved

#10 2021-10-30 18:30:56

Re: Caja error.... will not umount without a 45 second delay- solved

#11 2021-10-30 19:09:37

Re: Caja error.... will not umount without a 45 second delay- solved

#12 2021-10-30 20:27:14

Re: Caja error.... will not umount without a 45 second delay- solved

#13 2021-10-30 20:29:55

Re: Caja error.... will not umount without a 45 second delay- solved

#14 2021-10-30 20:31:15

Re: Caja error.... will not umount without a 45 second delay- solved

#15 2021-10-30 20:39:26

Re: Caja error.... will not umount without a 45 second delay- solved

#16 2021-10-30 20:45:20

Re: Caja error.... will not umount without a 45 second delay- solved

#17 2021-10-30 20:48:45

Re: Caja error.... will not umount without a 45 second delay- solved

#18 2021-10-30 20:55:23

Re: Caja error.... will not umount without a 45 second delay- solved

#19 2021-10-30 20:56:45

Re: Caja error.... will not umount without a 45 second delay- solved

#20 2021-10-30 20:59:50

Re: Caja error.... will not umount without a 45 second delay- solved

#21 2021-10-30 22:16:12

Re: Caja error.... will not umount without a 45 second delay- solved

#22 2021-10-31 06:52:35

Re: Caja error.... will not umount without a 45 second delay- solved

#23 2021-10-31 19:19:54

Re: Caja error.... will not umount without a 45 second delay- solved

#24 2021-10-31 20:11:28

Re: Caja error.... will not umount without a 45 second delay- solved

#25 2021-10-31 20:31:01

Re: Caja error.... will not umount without a 45 second delay- solved

Board footer