Thunar abend session abruptly

I have abends that logout my session sometime when clicking on the elive shortcut to open Home folder.

Here is the xession-errors log :

~ ❯❯❯ cat .xsession-errors.old
Xsession: X session started for bt at lundi 6 décembre 2021, 11:58:47 (UTC-0500)
dbus-update-activation-environment: setting DBUS_SESSION_BUS_ADDRESS=unix:path=/run/user/1001/bus
dbus-update-activation-environment: setting DISPLAY=:0
dbus-update-activation-environment: setting XAUTHORITY=/home/bt/.Xauthority
localuser:bt being added to access control list
dbus-update-activation-environment: setting USER=bt
dbus-update-activation-environment: setting XDG_SESSION_TYPE=x11
dbus-update-activation-environment: setting HOME=/home/bt
dbus-update-activation-environment: setting DESKTOP_SESSION=lightdm-xsession
dbus-update-activation-environment: setting XDG_SEAT_PATH=/org/freedesktop/DisplayManager/Seat0
dbus-update-activation-environment: setting DBUS_SESSION_BUS_ADDRESS=unix:path=/run/user/1001/bus
dbus-update-activation-environment: setting LOGNAME=bt
dbus-update-activation-environment: setting XDG_SESSION_CLASS=user
dbus-update-activation-environment: setting PATH=/usr/local/bin:/usr/bin:/bin:/usr/local/games:/usr/games
dbus-update-activation-environment: setting XDG_SESSION_PATH=/org/freedesktop/DisplayManager/Session3
dbus-update-activation-environment: setting XDG_RUNTIME_DIR=/run/user/1001
dbus-update-activation-environment: setting DISPLAY=:0
dbus-update-activation-environment: setting LANG=fr_CA.UTF-8
dbus-update-activation-environment: setting XDG_SESSION_DESKTOP=lightdm-xsession
dbus-update-activation-environment: setting XAUTHORITY=/home/bt/.Xauthority
dbus-update-activation-environment: setting XDG_GREETER_DATA_DIR=/var/lib/lightdm/data/bt
dbus-update-activation-environment: setting SHELL=/bin/zsh
dbus-update-activation-environment: setting GDMSESSION=lightdm-xsession
dbus-update-activation-environment: setting NO_AT_BRIDGE=1
dbus-update-activation-environment: setting GPG_AGENT_INFO=/run/user/1001/gnupg/S.gpg-agent:0:1
dbus-update-activation-environment: setting PWD=/home/bt
dbus-update-activation-environment: setting XDG_DATA_DIRS=/home/bt/.local/share/flatpak/exports/share:/var/lib/flatpak/exports/share:/usr/local/share:/usr/share/xdgeldsk:/usr/share
caching startup.ogg
** Message: 11:58:49.745: couldn't access control socket: /run/user/1001/keyring/control: Aucun fichier ou dossier de ce type
** Message: 11:58:49.756: couldn't access control socket: /run/user/1001/keyring/control: Aucun fichier ou dossier de ce type
** Message: 11:58:49.768: couldn't access control socket: /run/user/1001/keyring/control: Aucun fichier ou dossier de ce type
SSH_AUTH_SOCK=/run/user/1001/keyring/ssh
conky: desktop window (40000d) is subwindow of root window (399)
conky: window type - desktop
conky: drawing to created window (0x1400002)
conky: drawing to double buffer
conky: forked to background, pid is 14101

** (xfce4-clipman:13973): WARNING **: 11:58:49.837: Unable to register GApplication: Un objet est déjà exporté pour l’interface « org.gtk.Application » en « /org/xfce/clipman »

(xfce4-clipman:13973): GLib-GIO-CRITICAL **: 11:58:49.837: g_application_get_is_remote: assertion 'application->priv->is_registered' failed

(xfce4-clipman:13973): GLib-WARNING **: 11:58:49.837: g_set_application_name() called multiple times


(cairo-dock:14061): Gtk-WARNING **: 11:58:49.994: Theme parsing error: <data>:7:1467: The :insensitive pseudo-class is deprecated. Use :disabled instead.

(cairo-dock:14061): Gtk-WARNING **: 11:58:49.994: Theme parsing error: <data>:7:3649: The :inconsistent pseudo-class is deprecated. Use :indeterminate instead.
sh: 1: /usr/lib/x86_64-linux-gnu/cairo-dock/cairo-dock-launcher-API-daemon: not found
Terminal type `unknown' is not defined.
libEGL warning: DRI2: failed to authenticate
ERR<21062>:ecore_evas ../src/modules/ecore_evas/engines/x/ecore_evas_x.c:5382 ecore_evas_gl_x11_options_new_internal() evas_engine_info_set() init engine 'opengl_x11' failed.
## Copy & Paste the below (until EOF) into a terminal, then hit Enter

eina_btlog << EOF
/lib/x86_64-linux-gnu/libeina.so.1	 0x7fc898269f3c 0x7fc89823e000
/lib/x86_64-linux-gnu/libeina.so.1	 0x7fc89826b081 0x7fc89823e000
/lib/x86_64-linux-gnu/libeina.so.1	 0x7fc89826c6a3 0x7fc89823e000
/lib/x86_64-linux-gnu/ecore_evas/engines/x/v-1.25/module.so	 0x7fc88c9272a8 0x7fc88c912000
/lib/x86_64-linux-gnu/ecore_evas/engines/x/v-1.25/module.so	 0x7fc88c9273fb 0x7fc88c912000
/lib/x86_64-linux-gnu/libecore_evas.so.1	 0x7fc897d59662 0x7fc897d42000
/lib/x86_64-linux-gnu/libelementary.so.1	 0x7fc89807e993 0x7fc897d71000
/lib/x86_64-linux-gnu/libelementary.so.1	 0x7fc89807fd62 0x7fc897d71000
/lib/x86_64-linux-gnu/libeo.so.1	 0x7fc8979bdda7 0x7fc8979a9000
/lib/x86_64-linux-gnu/libelementary.so.1	 0x7fc89807bc3c 0x7fc897d71000
/lib/x86_64-linux-gnu/libeo.so.1	 0x7fc8979bdda7 0x7fc8979a9000
/lib/x86_64-linux-gnu/libeo.so.1	 0x7fc8979b7a74 0x7fc8979a9000
/usr/bin/terminology	 0x55da882e38d3 0x55da88285000
/usr/bin/terminology	 0x55da882a418a 0x55da88285000
/usr/bin/terminology	 0x55da882a5e85 0x55da88285000
/usr/bin/terminology	 0x55da8829a6ac 0x55da88285000
/lib/x86_64-linux-gnu/libc.so.60x7fc8979f809b 0x7fc8979d4000
/usr/bin/terminology	 0x55da8829a6ea 0x55da88285000
EOF

ERR<21062>:elementary ../src/lib/elementary/efl_ui_focus_manager_calc.c:1529 _efl_ui_focus_manager_calc_efl_ui_focus_manager_manager_focus_set() Could not fetch a node located at 0x400000048ace
## Copy & Paste the below (until EOF) into a terminal, then hit Enter

eina_btlog << EOF
/lib/x86_64-linux-gnu/libeina.so.1	 0x7fc898269f3c 0x7fc89823e000
/lib/x86_64-linux-gnu/libeina.so.1	 0x7fc89826b081 0x7fc89823e000
/lib/x86_64-linux-gnu/libeina.so.1	 0x7fc89826c6a3 0x7fc89823e000
/lib/x86_64-linux-gnu/libelementary.so.1	 0x7fc8980ac595 0x7fc897d71000
/lib/x86_64-linux-gnu/libelementary.so.1	 0x7fc8980a6abf 0x7fc897d71000
/lib/x86_64-linux-gnu/libelementary.so.1	 0x7fc8980aa546 0x7fc897d71000
/lib/x86_64-linux-gnu/libelementary.so.1	 0x7fc8980a7667 0x7fc897d71000
/usr/bin/terminology	 0x55da882dda03 0x55da88285000
/usr/bin/terminology	 0x55da882e1bfd 0x55da88285000
/lib/x86_64-linux-gnu/libeo.so.1	 0x7fc8979c4b35 0x7fc8979a9000
/lib/x86_64-linux-gnu/libeo.so.1	 0x7fc8979bd077 0x7fc8979a9000
/lib/x86_64-linux-gnu/libelementary.so.1	 0x7fc89807b3d4 0x7fc897d71000
/lib/x86_64-linux-gnu/libecore_evas.so.1	 0x7fc897d551eb 0x7fc897d42000
/lib/x86_64-linux-gnu/ecore_evas/engines/x/v-1.25/module.so	 0x7fc88c91e60c 0x7fc88c912000
/lib/x86_64-linux-gnu/libecore.so.1	 0x7fc8982fca69 0x7fc8982d7000
/lib/x86_64-linux-gnu/libecore.so.1	 0x7fc898305d8f 0x7fc8982d7000
/lib/x86_64-linux-gnu/libecore.so.1	 0x7fc8982fea69 0x7fc8982d7000
/lib/x86_64-linux-gnu/libecore.so.1	 0x7fc8982fd907 0x7fc8982d7000
/lib/x86_64-linux-gnu/libecore.so.1	 0x7fc8982f8b3e 0x7fc8982d7000
/lib/x86_64-linux-gnu/libecore.so.1	 0x7fc8982f9315 0x7fc8982d7000
/lib/x86_64-linux-gnu/libecore.so.1	 0x7fc8982fe8c5 0x7fc8982d7000
/lib/x86_64-linux-gnu/libecore.so.1	 0x7fc8982fdbb7 0x7fc8982d7000
/lib/x86_64-linux-gnu/libecore.so.1	 0x7fc8982f93d7 0x7fc8982d7000
/usr/bin/terminology	 0x55da882a5e8a 0x55da88285000
/usr/bin/terminology	 0x55da8829a6ac 0x55da88285000
/lib/x86_64-linux-gnu/libc.so.60x7fc8979f809b 0x7fc8979d4000
/usr/bin/terminology	 0x55da8829a6ea 0x55da88285000
EOF


(xfce4-clipman:13973): Gdk-CRITICAL **: 12:10:53.536: gdk_window_get_device_position_double: assertion 'GDK_IS_WINDOW (window)' failed

(firefox-esr:21270): dconf-WARNING **: 12:11:23.710: failed to commit changes to dconf: Le délai d’attente est dépassé

(xfce4-clipman:13973): Gdk-CRITICAL **: 12:15:26.814: gdk_window_get_device_position_double: assertion 'GDK_IS_WINDOW (window)' failed
ERR<21062>:efreet_cache ../src/lib/efreet/efreet_cache.c:432 efreet_cache_shutdown() This application has not properly closed all its desktop references!
## Copy & Paste the below (until EOF) into a terminal, then hit Enter

eina_btlog << EOF
/lib/x86_64-linux-gnu/libeina.so.1	 0x7fc898269f3c 0x7fc89823e000
/lib/x86_64-linux-gnu/libeina.so.1	 0x7fc89826b081 0x7fc89823e000
/lib/x86_64-linux-gnu/libeina.so.1	 0x7fc89826c6a3 0x7fc89823e000
/lib/x86_64-linux-gnu/libefreet.so.1	 0x7fc897c24166 0x7fc897c07000
/lib/x86_64-linux-gnu/libefreet.so.1	 0x7fc897c0f433 0x7fc897c07000
/lib/x86_64-linux-gnu/libeio.so.1	 0x7fc897263875 0x7fc897250000
/lib/x86_64-linux-gnu/libelementary.so.1	 0x7fc897fac31d 0x7fc897d71000
/lib/x86_64-linux-gnu/libelementary.so.1	 0x7fc897fac927 0x7fc897d71000
/usr/bin/terminology	 0x55da882a5e33 0x55da88285000
/usr/bin/terminology	 0x55da8829a6ac 0x55da88285000
/lib/x86_64-linux-gnu/libc.so.60x7fc8979f809b 0x7fc8979d4000
/usr/bin/terminology	 0x55da8829a6ea 0x55da88285000
EOF


(xfce4-clipman:13973): GLib-CRITICAL **: 13:59:18.014: Source ID 57 was not found when attempting to remove it
** Message: 13:59:35.847: Initializing MEGAsync extension
Gdk-Message: 13:59:36.106: notification-daemon: Fatal IO error 11 (Ressource temporairement non disponible) on X server :0.0.

Gdk-Message: 13:59:36.106: blueman-applet: Fatal IO error 11 (Ressource temporairement non disponible) on X server :0.0.

Gdk-Message: 13:59:36.106: Thunar: Fatal IO error 104 (Connexion ré-initialisée par le correspondant) on X server :0.0.

Gdk-Message: 13:59:36.106: xfce4-clipman: Fatal IO error 11 (Ressource temporairement non disponible) on X server :0.0.

Gdk-Message: 13:59:36.106: kupfer.py: Fatal IO error 11 (Ressource temporairement non disponible) on X server :0.0.

Gdk-Message: 13:59:36.106: cairo-dock: Fatal IO error 104 (Connexion ré-initialisée par le correspondant) on X server :0.0.

Gdk-Message: 13:59:36.106: polkit-gnome-authentication-agent-1: Fatal IO error 11 (Ressource temporairement non disponible) on X server :0.0.

XIO:  fatal IO error 11 (Resource temporarily unavailable) on X server ":0.0"
      after 11 requests (11 known processed) with 0 events remaining.
XIO:  fatal IO error 11 (Ressource temporairement non disponible) on X server ":0.0"
      after 564520 requests (564518 known processed) with 0 events remaining.
[8715]    0.000000: WindowMatchConfigLoad: No such border: 'LEFT_TITLE'
[8715]    0.000007: WindowMatchConfigLoad: Skip invalid 'LEFT_TITLE_MATCH'
[8715]    0.000009: WindowMatchConfigLoad: No such border: 'LEFT_TITLE'
[8715]    0.000010: WindowMatchConfigLoad: Skip invalid 'LEFT_TITLE_MATCH'
[8715]    0.000011: WindowMatchConfigLoad: No such border: 'LEFT_TITLE'
[8715]    0.000012: WindowMatchConfigLoad: Skip invalid 'LEFT_TITLE_MATCH'
[8715]    0.038996: WindowMatchDecode: No such border: 'SHAPED'
[8715]    0.039000: WindowMatchDecode: No such border: 'FIXED_SIZE'
[8715]    0.039001: WindowMatchDecode: No such border: 'DIALOG'
[8715]    2.545672: root: 0x399: Ignore obsolete event 18
[8715]  338.052294: cli: 0x2800003: Ignore obsolete event 33
[8715]  341.015432: cli: 0x2800003: Ignore obsolete event 33
[8715]  547.359604: cli: 0x2800003: Ignore obsolete event 33
[8715]  595.447161: root: 0x399: Ignore obsolete event 18

I'm booted from a USB SSD drive (/dev/sda)

. Here is my laptop info :

root ~ ❯❯❯ inxi -Faz
System:    Host: EliveOrDead Kernel: 5.10.0-0.bpo.8-amd64 x86_64 bits: 64 Console: tty 0 Distro: Elive 10 3.8.24 (beta)
Machine:   Type: Laptop System: ASUSTeK product: VivoBook_ASUSLaptop X513UA_M513UA v: 1.0 serial: <filter>
           Mobo: ASUSTeK model: X513UA v: 1.0 serial: <filter> UEFI: American Megatrends LLC. v: X513UA.305 date: 03/12/2021
Battery:   ID-1: BAT0 charge: 40.5 Wh condition: 40.5/42.1 Wh (96%)
CPU:       Topology: 8-Core model: AMD Ryzen 7 5700U with Radeon Graphics bits: 64 type: MT MCP family: 17 (23)
           model-id: 68 (104) stepping: 1 microcode: 8608103 L2 cache: 4096 KiB
           Speed: 1397 MHz max: 4370 MHz Core speeds (MHz): 1: 1395 2: 1397 3: 1397 4: 1396 5: 1397 6: 1397 7: 1397 8: 1396
           9: 1397 10: 1396 11: 1397 12: 1397 13: 1397 14: 1404 15: 1397 16: 1396
           Vulnerabilities: Type: itlb_multihit status: Not affected
           Type: l1tf status: Not affected
           Type: mds status: Not affected
           Type: meltdown status: Not affected
           Type: spec_store_bypass mitigation: Speculative Store Bypass disabled via prctl and seccomp
           Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer sanitization
           Type: spectre_v2 mitigation: Full AMD retpoline, IBPB: conditional, IBRS_FW, STIBP: conditional, RSB filling
           Type: srbds status: Not affected
           Type: tsx_async_abort status: Not affected
Graphics:  Device-1: Advanced Micro Devices [AMD/ATI] Lucienne driver: amdgpu v: kernel
           Display: server: X.Org 1.20.4 driver: amdgpu,ati unloaded: fbdev,modesetting,vesa resolution: 1920x1080~60Hz
           OpenGL: renderer: llvmpipe (LLVM 7.0 128 bits) v: 3.3 Mesa 18.3.6
Audio:     Device-1: Advanced Micro Devices [AMD/ATI] Renoir Radeon High Definition Audio driver: snd_hda_intel
           Device-2: Advanced Micro Devices [AMD] Raven/Raven2/FireFlight/Renoir Audio Processor driver: N/A
           Device-3: Advanced Micro Devices [AMD] Family 17h HD Audio driver: snd_hda_intel
           Sound Server: ALSA v: k5.10.0-0.bpo.8-amd64
Network:   Device-1: Intel Wi-Fi 6 AX200 driver: iwlwifi
           IF: wlp1s0 state: up mac: <filter>
Drives:    Local Storage: total: 1.40 TiB used: 18.93 GiB (1.3%)
           ID-1: /dev/nvme0n1 vendor: Western Digital model: PC SN530 SDBPNPZ-1T00-1002 size: 953.87 GiB block size:
           physical: 512 B logical: 512 B
           ID-2: /dev/sda type: USB model: SPCC Sol id State Disk size: 476.94 GiB block size: physical: 512 B logical: 512 B
           ID-3: /dev/sdb type: USB model: USB DISK 2.0 size: 3.73 GiB block size: physical: 512 B logical: 512 B
Partition: ID-1: / raw size: 39.06 GiB size: 38.20 GiB (97.79%) used: 8.77 GiB (23.0%) fs: ext4 block size: 4096 B
           dev: /dev/dm-2
           ID-2: /boot raw size: 420.0 MiB size: 398.7 MiB (94.93%) used: 92.7 MiB (23.2%) fs: ext4 block size: 1024 B
           dev: /dev/sda2
           ID-3: /home raw size: 421.34 GiB size: 413.73 GiB (98.19%) used: 10.06 GiB (2.4%) fs: ext4 block size: 4096 B
           dev: /dev/dm-3
           ID-4: swap-1 size: 15.89 GiB used: 2.8 MiB (0.0%) fs: swap swappiness: 60 (default) cache pressure: 100 (default)
           dev: /dev/dm-1
Sensors:   System Temperatures: cpu: 47.0 C mobo: N/A
           Fan Speeds (RPM): cpu: 2300
Info:      Processes: 320 Uptime: 1d 1h 38m Memory: 15.11 GiB used: 1.38 GiB (9.1%) Shell: zsh inxi: 3.0.32

IMO this ilook more a cairo-dock issue than thunar but I could be wrong. :thinking:

Anyway, I don't use cairo-dock so this one might be one for somebody else.

I have also those messages that come out from time to time :

 (dpkg-preconfigure:30376): dbind-WARNING **: 16:46:28.631: Error retrieving accessibility bus address: org.freedesktop.DBus.Error.ServiceUnknown: The name org.a11y.Bus was not provided by any .service files

(dpkg-preconfigure:30374): dbind-WARNING **: 16:46:28.675: Error retrieving accessibility bus address: org.freedesktop.DBus.Error.ServiceUnknown: The name org.a11y.Bus was not provided by any .service files

It seems the following is a solution :
Error retrieving accessibility bus address

After installing : sudo apt install at-spi2-core

I have logout/login in E16 and thunar doesn't abend each time now.
But it still abend sometime. I have found these messages in the syslog that confirm that cairo-dock is the cause :

[ 5569.264379] efreet_icon_cac[4728]: segfault at 7ffe4381eff8 ip 00007f3d5d0b0fcf sp 00007ffe4381f000 error 6 in libeina.so.1.25.99[7f3d5d099000+5a000]
[ 5569.264388] Code: 37 81 fe ff 4c 8d 05 50 69 06 00 48 8d 0d 2c 8f 04 00 e9 c6 fe ff ff 0f 1f 40 00 41 57 45 89 c2 41 56 4d 89 ce 41 55 49 89 cd <41> 54 49 89 d4 55 89 f5 53 89 fb 48 81 ec 38 08 00 00 64 48 8b 04
[ 6553.711234] efreet_icon_cac[1054]: segfault at 7ffe467faff8 ip 00007f55010befcf sp 00007ffe467fb000 error 6 in libeina.so.1.25.99[7f55010a7000+5a000]
[ 6553.711242] Code: 37 81 fe ff 4c 8d 05 50 69 06 00 48 8d 0d 2c 8f 04 00 e9 c6 fe ff ff 0f 1f 40 00 41 57 45 89 c2 41 56 4d 89 ce 41 55 49 89 cd <41> 54 49 89 d4 55 89 f5 53 89 fb 48 81 ec 38 08 00 00 64 48 8b 04
[ 8919.110651] cairo-dock[26025]: segfault at 29 ip 00005652c36104fa sp 00007ffe83f99970 error 4 in cairo-dock[5652c3600000+31000]
[ 8919.110659] Code: 01 00 e8 19 da ff ff 85 c0 0f 88 31 01 00 00 48 8b 05 ca 22 22 00 48 85 c0 0f 84 09 01 00 00 48 8b 40 20 48 8d 3d be 66 01 00 <48> 8b 40 28 48 8b 30 31 c0 e8 48 bc ff ff 8b 0d 02 27 22 00 85 c9
[ 9481.278097] efreet_icon_cac[19796]: segfault at 7ffdff4caff8 ip 00007f7353004fd7 sp 00007ffdff4cb000 error 6 in libeina.so.1.25.99[7f7352fed000+5a000]
[ 9481.278110] Code: 69 06 00 48 8d 0d 2c 8f 04 00 e9 c6 fe ff ff 0f 1f 40 00 41 57 45 89 c2 41 56 4d 89 ce 41 55 49 89 cd 41 54 49 89 d4 55 89 f5 <53> 89 fb 48 81 ec 38 08 00 00 64 48 8b 04 25 28 00 00 00 48 89 84

I'd say it is half solved for the moment.

You could test and find out whether the issue is there when:

  • you start thunar from the menu (utility => thunar file manager)
    or
  • starting from the cairo-dock menu "places" icon
    or
  • started from inside some another app (a path/link) like a terminal

It does abend by starting thunar from the menu and starting from cairo-dock places.

:sweat:

Ok, as a first .... what does "abend" mean? Freeze?

secondly, from "man thunar":

--daemon
          Do not terminate the Thunar instance when the last window is closed, but keep it running to speed up opening new windows later on. This is the default when spawning
          Thunar as part of the default Xfce session or when using D-Bus activation.

Which might be part of the trouble you're having. :thinking:
OTH most GUI file-managers use this trick.

In another terminal instance you can check out the status of thunar with:
sudo ps -aux |grep thunar
which on my machine with a closed (actually sleping) thunar is:
trianta+ 20156 0.0 0.0 11760 884 pts/4 S+ 09:31 0:00 grep --color=auto thunar
where the "S+" indicates a waiting interruptable process.

Here's some pointers:
https://www.cyberciti.biz/faq/find-out-what-processes-are-running-in-the-background-on-linux/

That's... not Thunar. That's your | grep thunar. I know from experience. You can see that it is grep --color=auto thunar, --color=auto being the aliased to grep IIRC

good point, when opened it's:

trianta+ 30940 10.5  0.5 401816 46428 ?        Sl   15:03   0:00 Thunar /home/triantares/Code

and doesn't show anymore when closed.

I have suspicions about the thunar-megasync extension I have installed with megasync.
If the megasync client is not running since a few seconds thunar will abend when opening.
I used to not start megasync automaticaly at beginning of a new session. I have added megasync-thunar in the startup list now and thunar seems more stable. But I have to wait about 30 secs before opening it if I'm just login in (a delay to let megasync client connecting first).

*** EDIT *** it does not solve the problem. It still abend but not everytime.
PS: by abend I mean I do get kick out of my session and back to login menu.

Ah yes, there's your culprit.
You wont believe how many computers (especially Windows) I've had to troubleshoot for "slowing down" due to auto- syncing with dropbox.
Especially with large systems the CPU usage is enormous when computing the the differences.
It looks like your machine/session is having trouble there.

Next to looking at what might be going wrong you might consider having a smaller workload by auto-syncing only smaller directories and not the whole shebang every time you start-up/connect. :thinking:

By itself "mega-sync" shouldn't need that many resources so there could be something wrong with the extension.
It might be a better idea to use the mega-sync standalone client.

addendum

Considering that megasync as a standalone client or extension is not in any of the Elive or Buster repos: Use it with great care. Stuff like this can and probably will happen when mixing repos.

I'm not so sure that megasync extension is related to the thunar abend.
There is not much work to do to sync the Mega directory it's rather stable and doesn't change other than adding a file from time to time.
I have tried to catch the error by running thunar with the debugger.
But I haven't had any succes to reproduce the problem,
I just doen't abend when I start thunar with gdb ...

I'm still trying to reproduce the problem.

Regards,
BT

It's not about how much change but how big the total size of the batch is. That hash is what gets computed and compared every time it syncs.

1 Like

Isn't only the metadata that is checked to see if any file has changed ?
It shouldn't disturb that much thunar.

On my laptop disk I have GarudaLinux installed (it's arch based).
When I boot on KDE I have megasync working without any problem ?
And on sway desktop I have thunar and thunar-megasync extension working without problem.

I'm just trying to find a logic to this. May be thunar is more fragile under E16 or Enlightenment ???

Regards,
BT

Wouldn't it use hashing?
If it doesn't I'll be shocked. :thinking:

Timestamps can easily be corrupted/modified. Just look at the touch manpage - you can set the modification date!

1 Like

Reading the metadata would take it infinitely longer ..... hashing is CPU intensive for a short while but less of a pain.

It is slightly fragile, especially when it comes to mount-points but I'm more wary of the megasync extension itself considering it wasn't made for Debian and certainly not for Elive.
I think removing it will solve your "issues" with thunar.

I will try it.
:+1:

OK removing thunar-megasync did not solve the problem but removing also thunar-dropbox did.

I had installed the dropbox extension and after removing it all is back to normal.
I didn't remembered that this extension was installed

So both extensions were causing the problem with thunar. Better not use any of them.

Problem solved!

Well dropbox is notorious in my book.
Did you try re-installing megasync and check if that will run without issues now that dropbox is removed?

Yes, I tried to reinstall thunar-megasync extension and it does abend thunar also.
So I uninstalled it. But I kept the megasync client. Alone it doesn't interfere with thunar.
I have stuff that I want to keep on the cloud and Mega is 50Gb storage free. I need it.

The thunar-extension was to direcly interact with the Mega Account from the explorer.
It's not essential and I can live without it.

Thanks :+1:,
Bernard

1 Like