I called Thunar through gksu from a terminal window. After finsihing my work (which was successful), I saw error messages in the terminal window: $ gksu thunar (thunar:14004): GLib-CRITICAL **: 15:02:59.044: g_file_test: assertion 'filename != NULL' failed repeating 6 times. Thunar tells about its version: $ thunar --version Thunar 1.6.11 (Xfce 4.12)
Which action or file operation triggered the bug? Ideally, you should use pkexec instead of gksu (deprecated) and test with Thunar 1.8 if possible.
(In reply to Theo Linkspfeifer from comment #1) > Which action or file operation triggered the bug? Closing thunar. There were no error messages when I was actually working with it. So it seems to be just a minor bug since I actually could achieve with thunar what I wanted. Maybe it is something short before closing thunar. > Ideally, you should use pkexec instead of gksu (deprecated) $ pkexec thunar (thunar:19429): GLib-CRITICAL **: 19:27:31.609: g_file_test: assertion 'filename != NULL' failed (thunar:19429): GLib-CRITICAL **: 19:27:31.609: g_file_test: assertion 'filename != NULL' failed (thunar:19429): GLib-CRITICAL **: 19:27:31.609: g_file_test: assertion 'filename != NULL' failed (thunar:19429): GLib-CRITICAL **: 19:27:31.609: g_file_test: assertion 'filename != NULL' failed Well, with pkexec the bug shows up earlier: before I did anything with Thunar, but after I have entered the administrator's password. But then no error message is shown, when I close Thunar ... strange! And the bug has another number. > and test with > Thunar 1.8 if possible. Where do I get Thunar 1.8 without disturbing everything else in the system? Currently I still use Xubuntu 16.04.6 LTS, currently with kernel 4.4.0-154-generic x86_64.
Note: the number in "(thunar:19429)" is the process ID, not a bug number. You would have to either upgrade to Xubuntu 18.04 LTS and use the Xubuntu PPA to obtain the new version, or download the 19.04 ISO and boot into live mode. I tried to reproduce the bug with Thunar 1.8.8 using the Xubuntu 19.10 dev release, but no messages were printed.
My results: * thunar 1.6.17 and 1.6.11 * "thunar": warnings related to xfconf "gksu thunar": GLib-GObject-WARNING: invalid (NULL) pointer instance GLib-GObject-CRITICAL: g_signal_handler_disconnect: assertion 'G_TYPE_CHECK_INSTANCE (instance)' failed "sudo thunar": same as gksu "pkexec thunar": same as gksu * thunar git master * "thunar": warnings related to xfconf "gksu thunar": warnings related to dbus unsuccessful name registration (expected) "sudo thunar": same as gksu "pkexec thunar": same as gksu So I can't reproduce the error. Your options are: - Try Thunar 1.6.17 (via ppa or building from source) - Try Thunar 1.8.x (via ppa or building from source) - Get debug-symbols and run "G_DEBUG=fatal_warnings gksu gdb thunar" to get the backtrace ("r" to run, "bt" to get the backtrace when gdb pauses on the error) Sorry, but the 1.6.11 version is pretty dated (2.5yrs+), many fixes have been backported. After Xfce 4.14 (tomorrow!?), I can't promise to look after Thunar 1.6.x for much longer, so if you can reproduce this error with Thunar 1.8.x and get a backtrace the odds to get this bug fixed will be much higher.
(In reply to Theo Linkspfeifer from comment #3) > Note: the number in "(thunar:19429)" is the process ID, not a bug number. > > You would have to either upgrade to Xubuntu 18.04 LTS and use the Xubuntu > PPA to obtain the new version, or download the 19.04 ISO and boot into live > mode. > > I tried to reproduce the bug with Thunar 1.8.8 using the Xubuntu 19.10 dev > release, but no messages were printed. I looked where I can download a stable version for 64-bit Ubuntu and I came across the current stable release at https://launchpad.net/ubuntu/+archive/primary/+files/thunar_1.8.4-1ubuntu1_amd64.deb. I downloaded the file and tried to install it by a right click and then selecting GDebi. But I got the error message "Fehler, Abhängigkeit nicht erfüllbar: thunar-data(=1.8.4-1ubuntu1)" meaning something like "Error, dependencies can not be satisfied: thunar-data(=1.8.4-1ubuntu1)" Switching to Xubuntu 18.04 is an option which requires quite some time since it is a productive system with quite some non-standard programs. I just succeeded in installing it on an USB stick to start testing some components of it in order to verify if everything will work after upgrading the system. But that costs some time. But I'll try it with the system from the stick.
Now I have version 18.04. But still there is a Gtk-Warning (but thunar works as root as expected): v@v:~$ uname -a Linux W530-SSD 5.0.0-37-generic #40~18.04.1-Ubuntu SMP Thu Nov 14 12:06:39 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux v@v:~$ pkexec thunar (thunar:10384): Gtk-WARNING **: 12:53:47.910: Im Modulpfad »hcengine« konnte keine Themen-Engine gefunden werden, v@v:~$ Perhaps one could mark this bug as resolved in version 18.04. Sometimes error messages or warnings issued when calling a GUI program from a terminal irritate me, especially if I don't understand them and if I can't decide if the causes could prevent the program from working as expected. So perhaps in this case someone should shed some light on what really has to be done if one would want to fulfill the conditions not met here. I have seen the discussion at https://stackoverflow.com/questions/21007052/gtk-warning-unable-to-locate-theme-engine-in-module-path-murrine-error-whi, which had some answers but the question is an old one and definitely pre Xubuntu 18.04 so I dare not to follow the recipes given there as they might install incompatible older software.
> (thunar:10384): Gtk-WARNING **: 12:53:47.910: Im Modulpfad »hcengine« konnte keine Themen-Engine gefunden werden, This is some theming related issue, probably not thnar specific. Possibly you still have some parts of an older gtk2 theme installed ... try to switch to some other theme, and check if the warning still occurs. Officially supported themes are adwaita and greybird. Since you dont get any GLib-CRITICALs more, I will close this
thanks for your explanation. The theme was HighContrast. I switch it to Adwaita and I tried the same thing and then I go no warning.