If you open Thunar and try to end the session, the session does not end, and everything hangs, only the Thunar menu remains active. If you close the Thunar window, the session ends immediately. Вывод dmesg - [69659.293901] Thunar[25103]: segfault at 50b7 ip 00007f823c4b01a0 sp 00007ffdc4c4f7d0 error 4 in libgobject-2.0.so.0.5400.2[7f823c47c000+51000]
I cannot reproduce this behavior. How dis you start thunar ? From CLI ? Did you install it on your system ? ( A thunar daemon is launched automatically during startup when installed ) How did you end the seesion ? Logout in console ? Via the application-menu ?
(In reply to alexxcons from comment #1) > Я не могу воспроизвести это поведение. > > Как ты начинаешь тунар ? От CLI ? Вы установили его на своей системе ? > (Демон thunar запускается автоматически при запуске при установке ) > > Как вы закончили сеанс ? Выход из консоли ? Через меню приложения ? I open Thunar, then open the Whisker menu and click on the icon to end the session. I see this error in the ROS operating system Linux Fresh XFCE. Naturally Thunar is installed ....
Just to make sure: You are talking about thunar 1.7.2 ? ( Since something similar was a problem in 1.7.0 and should be fixed in thunar 1.7.2 ) Since 1.7.2 is a development release afaik it should only be packaged in experimental distribution releases. On which distro + distro-version ROS is based on ? I could not find much info about that on the ROS website.
Created attachment 7675 screenshot Thunar
I'm a contributor to ROSA and an assembler of an unofficial version of the Linux ROSA Linux distribution with the XFCE working environment. Here's the link to the group where I host the assembly https://vk.com/xfce_rospo In my build, I decided to use the experimental version of XFCE 4.13 ...
Compile thunar with debug symbols (./autogen.sh --prefix=/usr --enable-debug=yes && make && sudo make install) and try this: pkill -i Thunar gdb thunar # press 'r' and 'enter' Now try to log out, if Thunar segfaults, on the terminal running gdb enter: bt Finally, share with us the backtrace output.
Sorry for not responding for a long time. We run Thunar as gdb thunar, then the log out closes the terminal emulator window, which contains "gdb thunar". So thunar is closed normally and that way we can't trace the bug in ran Thunar as native. We tried to run both "gdb thunar" (in terminal) and Thunar (natively) at the same time. The log out led to a bug. At the same time we couldn't write anything to the terminal emulator window, because it hanged.
You can try from another tty, just run: DISPLAY=:0.0 gdb thunar
(In reply to Andre Miranda from comment #8) > You can try from another tty, just run: > DISPLAY=:0.0 gdb thunar After the release of Thunar 1.8.2 the problem was solved. The session ends successfully with a small delay (probably due to the need to close thunar)