Thunar 1.6.11 hard locks computer if copying dir on itself

hellogoo · 2017-07-14 23:10:54

I accidentally copied a directory "my_directory" onto itself. It's worth 2GB of data, on an encrypted ext4 container (if that makes any difference).

My computer then hard locked itself, couldn't do anything but hard rebooting. (even the mouse cursor was frozen).

Why is there no fail-safe when doing simple manipulations like that. At least some popup to ask for renaming the directory to something else would have been nice... or just a warning that something is wrong, instead of (what seems to be) an infinite loop somewhere.

I lost some data in the process (unsaved work... not too big of a deal).

Last edited by hellogoo (2017-07-15 00:17:00)

MountainDewManiac · 2017-07-15 00:26:46

I agree that there should be some sort of failsafe to prevent user-instituted screw ups such as the one you mentioned.

However... A good friend of mine is fond of saying that we will never be able to truly construct an idiot-proof anything - because the universe keeps breeding bigger and better idiots. In other words, at what point does the designer's responsibility end and the user's begin? Or at least that's what I think he means.

Hopefully, a simple reboot caused no damage. And it probably didn't, assuming that you are using one of the several journaling file systems for all of the devices/partitions that might have been in use at the time. Unless you were running a mission-critical physics experiment or the like, of course, and ended up having to repeat the experiment from step one (which is entirely possible, I suppose).

I have performed the same basic screw up in the past, although it was on one of Microsoft's OS (Windows 3.11, I think). All I had to do was to delete a lot of duplicate files. Different OS and file manager, though.

I am curious about a few things. You stated that the (original) files in the source directory were two gigabytes in size. Did you have plenty of room in which to create the copies, or might this issue possibly have been aggravated by a disk full error at some point? How long did you wait before rebooting? Are you absolutely positive that the computer was truly "locked up," or might it still have been doing something and just not have accepted user input in any reasonable timespan (IOW, were your CPUs/cores at 100%, the drives thrashing... or was it just quietly sitting there, with no CPU activity, as if it was at idle with nothing running other than the desktop, itself)?

And did you try the usual set of things that are suggested when one's linux OS computer is frozen (or appears to be), such as what is covered here:
https://en.wikibooks.org/wiki/Linux_Guide/Freezes
...or did you simply panic and skip to the very last step (holding down the power button for several seconds, toggling the switch on the back of the power supply (if a desktop or server), or momentarily interrupting the electricity)?

I am merely asking out of curiosity. But the answers to these questions - and, likely as not, more that I don't have the intelligence or knowledge to think of - will help form a better picture of what, exactly, was going on. So it is probably important to answer them and to include the information when you file your bug report on https://bugzilla.xfce.org/ (you are planning on filing a bug report, I assume?).

Regards,
MDM

hellogoo · 2017-07-15 14:39:52

Thanks for the reply.

When I say hard lock up, it's HARD. No way to access a tty, mouse cursor frozen. I admit I never remember the SysRq key sequences so I waited for 5 minutes then smashed the power button. There didn't seem to be much CPU activity judging from the fans, but I can hardly tell because it's a powerful machine (i7-3740QM with 16GB of RAM). I had plenty of space left on the container.

I use i3 window manager, with xfsettingsd for theming purposes mostly. Antergos (Arch Linux based).

I considered reporting bugs in the bug trackers before, because I have so many issues with Thunar. Maybe I'll get around to doing it eventually.

ToZ · 2017-07-15 15:28:27

hellogoo wrote:

I accidentally copied a directory "my_directory" onto itself.

How did you do this with Thunar? If I drag and drop the directory onto itself, nothing happens for me (the action is cancelled). If I select copy/paste, it creates a new folder that is a copy of itself.

You might be able to get some diagnostic info of you run Thunar from a terminal window (just make sure that all running thunar instances, especially the "Thunar --daemon" process are killed first).

Also, Arch has Thunar version 1.6.12 in it's repositories. This version fixed a pretty nasty rename bug. I'm not exactly sure how Antegros works, but check if you can update the package

hellogoo · 2017-07-15 17:32:45

Here what I saw in the syslogs. It's strange that I see several reboots, even though I only rebooted once. Perhaps the system was indeed rebooting (several times, since I hit a lot of key strokes...) but the screen still displayed the last frame in some frame buffer somewhere (I have no idea what I'm talking about):

Jul 15 00:57:05 clevo systemd[1]: systemd-logind.service: Watchdog timeout (limit 3min)!
Jul 15 00:57:05 clevo systemd[1]: systemd-logind.service: Killing process 753 (systemd-logind) with signal SIGABRT.
Jul 15 00:57:20 clevo dbus-daemon[5555]: Activating service name='org.freedesktop.thumbnails.Cache1'
Jul 15 00:57:20 clevo tumblerd[4002]: Failed to load plugin "tumbler-raw-thumbnailer.so": libopenrawgnome.so.7: cannot open shared object file: No such file or directory
Jul 15 00:57:20 clevo dbus-daemon[5555]: Successfully activated service 'org.freedesktop.thumbnails.Cache1'
Jul 15 00:57:20 clevo tumblerd[4002]: Failed to load plugin "tumbler-odf-thumbnailer.so": libgsf-1.so.114: cannot open shared object file: No such file or directory
Jul 15 00:57:20 clevo systemd[1]: Started Process Core Dump (PID 4015/UID 0).
Jul 15 00:57:21 clevo systemd[1]: systemd-logind.service: Main process exited, code=dumped, status=6/ABRT
Jul 15 00:57:21 clevo systemd[1]: systemd-logind.service: Unit entered failed state.
Jul 15 00:57:21 clevo systemd[1]: systemd-logind.service: Failed with result 'watchdog'.
Jul 15 00:57:21 clevo systemd[1]: systemd-logind.service: Service has no hold-off time, scheduling restart.
Jul 15 00:57:21 clevo systemd[1]: Stopped Login Service.
Jul 15 00:57:21 clevo systemd[1]: Starting Login Service...
Jul 15 00:57:21 clevo systemd[1]: Started Login Service.
Jul 15 00:57:21 clevo systemd-logind[4092]: New seat seat0.
Jul 15 00:57:21 clevo systemd-coredump[4017]: Process 753 (systemd-logind) of user 0 dumped core.

Stack trace of thread 753:
#0 0x00007f021bf26647 sendmsg (libpthread.so.0)
#1 0x00007f021c4665c2 sd_pid_notify_with_fds (libsystemd-shared-232.so)
#2 0x00007f021c38e1f6 sd_event_wait (libsystemd-shared-232.so)
#3 0x00007f021c38e6bb sd_event_run (libsystemd-shared-232.so)
#4 0x000055da1c5e0563 n/a (systemd-logind)

Stack trace of thread 753:
#0 0x00007f021bf26647 sendmsg (libpthread.so.0)
#1 0x00007f021c4665c2 sd_pid_notify_with_fds (libsystemd-shared-232.so)
#2 0x00007f021c38e1f6 sd_event_wait (libsystemd-shared-232.so)
#3 0x00007f021c38e6bb sd_event_run (libsystemd-shared-232.so)
#4 0x000055da1c5e0563 n/a (systemd-logind)
#5 0x00007f021bb9043a __libc_start_main (libc.so.6)
#6 0x000055da1c5e2a9a n/a (systemd-logind)
Jul 15 00:57:21 clevo systemd-logind[4092]: Watching system buttons on /dev/input/event5 (Power Button)
Jul 15 00:57:21 clevo systemd-logind[4092]: Watching system buttons on /dev/input/event6 (Video Bus)
Jul 15 00:57:21 clevo systemd-logind[4092]: Watching system buttons on /dev/input/event7 (Video Bus)
Jul 15 00:57:21 clevo systemd-logind[4092]: Watching system buttons on /dev/input/event4 (Power Button)
Jul 15 00:57:21 clevo systemd-logind[4092]: Watching system buttons on /dev/input/event2 (Lid Switch)
Jul 15 00:57:21 clevo systemd-logind[4092]: Watching system buttons on /dev/input/event3 (Sleep Button)
Jul 15 00:57:21 clevo systemd-logind[4092]: New session c4 of user hellogoo.
Jul 15 00:57:21 clevo systemd-logind[4092]: New session c2 of user hellogoo.
Jul 15 00:57:21 clevo systemd-logind[4092]: New session c3 of user hellogoo.
Jul 15 00:58:32 clevo kernel: sysrq: SysRq : HELP : loglevel(0-9) reboot(b) crash(c) terminate-all-tasks(e) memory-full-oom-kill(f) kill-all-tasks(i) thaw-filesystems(j) sak(
-- Reboot --

Jul 15 00:57:20 clevo systemd[1]: Started Process Core Dump (PID 4015/UID 0).
Jul 15 00:57:21 clevo systemd[1]: systemd-logind.service: Main process exited, code=dumped, status=6/ABRT
Jul 15 00:57:21 clevo systemd[1]: systemd-logind.service: Unit entered failed state.
Jul 15 00:57:21 clevo systemd[1]: systemd-logind.service: Failed with result 'watchdog'.
Jul 15 00:57:21 clevo systemd[1]: systemd-logind.service: Service has no hold-off time, scheduling restart.
Jul 15 00:57:21 clevo systemd[1]: Stopped Login Service.
Jul 15 00:57:21 clevo systemd[1]: Starting Login Service...
Jul 15 00:57:21 clevo systemd[1]: Started Login Service.
Jul 15 00:57:21 clevo systemd-logind[4092]: New seat seat0.
Jul 15 00:57:21 clevo systemd-coredump[4017]: Process 753 (systemd-logind) of user 0 dumped core.

Stack trace of thread 753:
#0 0x00007f021bf26647 sendmsg (libpthread.so.0)
#1 0x00007f021c4665c2 sd_pid_notify_with_fds (libsystemd-shared-232.so)
#2 0x00007f021c38e1f6 sd_event_wait (libsystemd-shared-232.so)
#3 0x00007f021c38e6bb sd_event_run (libsystemd-shared-232.so)
#4 0x000055da1c5e0563 n/a (systemd-logind)
#5 0x00007f021bb9043a __libc_start_main (libc.so.6)
#6 0x000055da1c5e2a9a n/a (systemd-logind)
Jul 15 00:57:21 clevo systemd-logind[4092]: Watching system buttons on /dev/input/event5 (Power Button)
Jul 15 00:57:21 clevo systemd-logind[4092]: Watching system buttons on /dev/input/event6 (Video Bus)
Jul 15 00:57:21 clevo systemd-logind[4092]: Watching system buttons on /dev/input/event7 (Video Bus)
Jul 15 00:57:21 clevo systemd-logind[4092]: Watching system buttons on /dev/input/event4 (Power Button)
Jul 15 00:57:21 clevo systemd-logind[4092]: Watching system buttons on /dev/input/event2 (Lid Switch)
Jul 15 00:57:21 clevo systemd-logind[4092]: Watching system buttons on /dev/input/event3 (Sleep Button)
Jul 15 00:57:21 clevo systemd-logind[4092]: New session c4 of user hellogoo.
Jul 15 00:57:21 clevo systemd-logind[4092]: New session c2 of user hellogoo.
Jul 15 00:57:21 clevo systemd-logind[4092]: New session c3 of user hellogoo.
Jul 15 00:58:32 clevo kernel: sysrq: SysRq : HELP : loglevel(0-9) reboot(b) crash(c) terminate-all-tasks(e) memory-full-oom-kill(f) kill-all-tasks(i) thaw-filesystems(j) sak(
-- Reboot --

It goes on for several "Reboot" with systemd-logind crashing (although I never noticed that) until the actual (effective?) reboot.
As you can see not much from Thunar itself, so I'm clueless.

I tried copying a test directory in Thunar and it worked as intended, no crash. So perhaps it's related to something else. No clue.

I'll update to 1.6.12 and hope it never happens again.

Last edited by hellogoo (2017-07-15 17:40:02)

ToZ · 2017-07-15 17:55:06

I don't think this is a thunar issue - something else is causing the crash on your system.

Also, you might want to install the libgsf and libopenraw packages to get more thumbnail coverage.

Xfce Forum

Sub domains

#1 2017-07-14 23:10:54

Thunar 1.6.11 hard locks computer if copying dir on itself

#2 2017-07-15 00:26:46

Re: Thunar 1.6.11 hard locks computer if copying dir on itself

#3 2017-07-15 14:39:52

Re: Thunar 1.6.11 hard locks computer if copying dir on itself

#4 2017-07-15 15:28:27

Re: Thunar 1.6.11 hard locks computer if copying dir on itself

#5 2017-07-15 17:32:45

Re: Thunar 1.6.11 hard locks computer if copying dir on itself

#6 2017-07-15 17:55:06

Re: Thunar 1.6.11 hard locks computer if copying dir on itself

Board footer