I think I've filed this as a bug before - but it was a long time ago and I don't recall where I filed it, so trying again. Essentially the problem is this - I have some code which analyses some data, and produces a large number of output files. Sometimes, and only sometimes, if thunar is open and the current directory is set to where those output files will be created, when I run my code, thunar crashes. The thunar window goes grey, and then a prompt appears telling me that thunar has stopped responding. Sorry I didn't put much effort into fixing this last time, but I would really like to get this sorted, because this issue has plagued me for about 4 years now. (I don't want to change desktop env just to get away from this problem as obviously xfce is great.) I'm hoping perhaps an experienced dev could assign to this issue, perhaps we can exchange email addresses - I can give you my postgrad institution one so you can look up who I am and then perhaps we can exchange phone numbers and get this issue sorted. I think this will be necessary, because I haven't found any way to re-produce the bug other than using the very specific combination of software that I am using. Who knows, it may not even be specifically an xfce/thunar problem. It might be an issue on a deeper OS level, I don't know. I also haven't heard of anyone else having this problem before, so I don't think it's a known about issue (other than I did report it probably 2 years ago). It's probably literally just me who has the problem, although I can ask some of my colleagues.
Thanks for reporting ! First of all, which thunar version do you use ? If it is outdated, please try to reproduce with an up to date version (1.8.9) or (1.8.10). Possibly the bug got fixed meanwhile. In order to work on a fix, it would be required to: a) Have a reproducer or at least: b) Have a backtrace of the crash. Check this page for details on how to produce a backtrace: https://docs.xfce.org/contribute/bugs/start
(In reply to alexxcons from comment #1) > Thanks for reporting ! > > First of all, which thunar version do you use ? > > If it is outdated, please try to reproduce with an up to date version > (1.8.9) or (1.8.10). Possibly the bug got fixed meanwhile. > > In order to work on a fix, it would be required to: > a) Have a reproducer > or at least: > b) Have a backtrace of the crash. > > Check this page for details on how to produce a backtrace: > https://docs.xfce.org/contribute/bugs/start Hi thanks for this - how can I check the version?
(In reply to hyper-nova from comment #2) > Hi thanks for this - how can I check the version? help --> about or "thunar --version" in an console
(In reply to alexxcons from comment #3) > (In reply to hyper-nova from comment #2) > > Hi thanks for this - how can I check the version? > help --> about or "thunar --version" in an console Great thanks, here's the result Thunar 1.6.11 (Xfce 4.12) Copyright (c) 2004-2015 The Thunar development team. All rights reserved. Written by Benedikt Meurer <benny@xfce.org>. Please report bugs to <http://bugzilla.xfce.org/>. How can I upgrade my system, either the entire of xfce or just thunar? I'm currently running debian 9. Seems like something that should be fairly easy but I've tried to find the answer to this before and didn't get anywhere. Thanks for the help so far
(In reply to hyper-nova from comment #4) > (In reply to alexxcons from comment #3) > > (In reply to hyper-nova from comment #2) > > > Hi thanks for this - how can I check the version? > > help --> about or "thunar --version" in an console > > Great thanks, here's the result > > Thunar 1.6.11 (Xfce 4.12) > > Copyright (c) 2004-2015 > The Thunar development team. All rights reserved. > > Written by Benedikt Meurer <benny@xfce.org>. > > Please report bugs to <http://bugzilla.xfce.org/>. > > How can I upgrade my system, either the entire of xfce or just thunar? I'm > currently running debian 9. Seems like something that should be fairly easy > but I've tried to find the answer to this before and didn't get anywhere. > > Thanks for the help so far You are using a thunar version from 2017 ... so changes are good that your bug got fixed meanwhile. So you have different options: 1.) Upgrade to debian 10, which is the current stable version (see here: https://de.wikipedia.org/wiki/Debian) That I would advice you in any case, since sooner or later you anyhow need to upgrade in order to get security fixes. This would bring you thunar 1.8.4 (and possibly more recent bugfix versions over time) Here some manual: https://phoenixnap.com/kb/how-to-upgrade-debian-9-stretch-to-debian-10-buster ... there are many others out there. 2.) Compile thunar master (or 1.8.10) from source: sudo apt-get install automake gcc git clone https://git.xfce.org/xfce/thunar cd thunar ./autogen.sh <Here you need to add all missing development packages (packagename-dev). Autogen will telll you which are needed> make -j4 ./thunar/thunar -q; ./thunar/thunar (This will quit the current thunar and run the self-build thunar without installing it to the system)
Hi again, and sorry for the delay. So far this is all I have been able to find (thunar:3768): thunar-WARNING **: Content type loading failed for read_data.cpp~: Error when getting information for file '/home/user/read_data.cpp~': No such file or directory read_data.cpp~ is a temporary file created by gvim. When gvim exits, I think it is removed. I am not completely sure if this explains the crash, because I don't think it crashes only when I am working with gvim. I think it is this in combination with running my executable which causes the crash. I will investigate further.
No, doesn't look like that is anything to do with it. Just closes all instances of vim and ran my program. It causes thunar to crash again, and no output was printed to the terminal. I think it is causing thunar to hang for some reason. I can perhaps try running it with gdb?
Unfortunately not enough debugging info to be able to debug this properly. #0 syscall () at ../sysdeps/unix/sysv/linux/x86_64/syscall.S:38 #1 0x00007ffff4b8695c in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x000055555558f186 in ?? () #3 0x00007fffeff9b038 in ffi_call_unix64 () from /usr/lib/x86_64-linux-gnu/libffi.so.6 #4 0x00007fffeff9aa9a in ffi_call () from /usr/lib/x86_64-linux-gnu/libffi.so.6 #5 0x00007ffff4e1bc8a in g_cclosure_marshal_generic_va () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 #6 0x00007ffff4e1b1a4 in ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 #7 0x00007ffff4e358cd in g_signal_emit_valist () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 #8 0x00007ffff4e35fbf in g_signal_emit () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 #9 0x00007ffff5142b49 in ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 #10 0x00007ffff4b417f7 in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #11 0x00007ffff4b41a60 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #12 0x00007ffff4b41d82 in g_main_loop_run () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #13 0x00007ffff6a1b3b7 in gtk_main () from /usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0 ---Type <return> to continue, or q <return> to quit--- #14 0x0000555555574a6b in ?? () #15 0x00007ffff455b2e1 in __libc_start_main (main=0x555555574640, argc=1, argv=0x7fffffffe288, init=<optimized out>, fini=<optimized out>, rtld_fini=<optimized out>, stack_end=0x7fffffffe278) at ../csu/libc-start.c:291 #16 0x0000555555574bba in ?? ()
Returning to another suggestion - sorry to obfuscate the issue. Downloaded the latest version with git. Can't compile with autogen, issue is: checking for exo-2 >= 0.12.0... not found *** The required package exo-2 was not found on your system. *** Please install exo-2 (atleast version 0.12.0) or adjust *** the PKG_CONFIG_PATH environment variable if you *** installed the package in a nonstandard prefix so that *** pkg-config is able to find it. Searched online and found this page https://tracker.debian.org/pkg/exo https://packages.debian.org/unstable/libexo-2-dev sudo apt install libexo-2-dev Reading package lists... Done Building dependency tree Reading state information... Done E: Unable to locate package libexo-2-dev Any ideas why my debian 9 install cannot find libexo-2-dev? Is this package only available in debian 10 perhaps? Is there anything I can do about this without upgrading to debian 10. I don't want to go though a full dist-upgrade, in case I break something.
Just noticed it says "buster" on that second page. Guess this is a new package for debian 10.
> Any ideas why my debian 9 install cannot find libexo-2-dev? Is this package only available in debian 10 perhaps? Yes, only available in debian 10 and above: https://packages.debian.org/buster/libexo-2-0 You could install exo from source instead: https://git.xfce.org/xfce/exo And build + install the exo-0.12.8 tag ... or you might want to use the xfce docker container: https://hub.docker.com/r/schuellerf/xfce-test (I never tried, though I heard it works fine)
Ok cheers for the info. I'm a bit tight on time, so what I will do is order a backup disk. Run a backup. Then try and move to Debian 10. That has got to be the simplest solution. I will keep this thread updated. Will take a couple of days to do this of course. Thanks!
Probably the best solution, since you anyhow will need to do so sooner or later .. and having a backup always is a good idea :)
-- GitLab Migration Automatic Message -- This bug has been migrated to xfce.org's GitLab instance and has been closed from further activity. You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.xfce.org/xfce/thunar/-/issues/271. Please create an account or use an existing account on one of our supported OAuth providers. If you want to fork to submit patches and merge requests please continue reading here: https://docs.xfce.org/contribute/dev/git/start#gitlab_forks_and_merge_requests Also feel free to reach out to us on the mailing list https://mail.xfce.org/mailman/listinfo/xfce4-dev