[Bug 13663] New: GLib-CRITICAL **: g_file_test: assertion 'filename != NULL' failed

classic Classic list List threaded Threaded
3 messages Options
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

[Bug 13663] New: GLib-CRITICAL **: g_file_test: assertion 'filename != NULL' failed

bugzilla-daemon
https://bugzilla.xfce.org/show_bug.cgi?id=13663

            Bug ID: 13663
           Summary: GLib-CRITICAL **: g_file_test: assertion 'filename !=
                    NULL' failed
    Classification: Xfce Core
           Product: Thunar
           Version: 1.6.11
          Hardware: Other
                OS: Linux
            Status: NEW
          Severity: normal
          Priority: Medium
         Component: Core
          Assignee: [hidden email]
          Reporter: [hidden email]
        QA Contact: [hidden email]
                CC: [hidden email], [hidden email]
  Target Milestone: 1.8.0

Created attachment 7184
  --> https://bugzilla.xfce.org/attachment.cgi?id=7184&action=edit
Patch

Recently Thunar started to spam stdout with this message:
GLib-CRITICAL **: g_file_test: assertion 'filename != NULL' failed

Also reported here:
https://forum.manjaro.org/t/testing-update-2017-05-10-kernel-virtualbox-haskell-gnome/23426/7

I'm running Thunar from master (338e6b9) on Arch Linux with gtk 2.24.31 and
glib2 2.52.2.
This problem also affects the gtk3-based Thunar.

Please check if the patch is ok before we push to master.

--
You are receiving this mail because:
You are the assignee for the bug.
_______________________________________________
Xfce-bugs mailing list
[hidden email]
https://mail.xfce.org/mailman/listinfo/xfce-bugs
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

[Bug 13663] GLib-CRITICAL **: g_file_test: assertion 'filename != NULL' failed

bugzilla-daemon
https://bugzilla.xfce.org/show_bug.cgi?id=13663

--- Comment #1 from André Miranda <[hidden email]> ---
Investigating this issue a bit more, I found that a return_if_fail was added to
g_file_test in 2017-04-08[1] and Arch is building the glib package from a
commit of 2017-06-01. Now I know why some guys from Manjaro and I are getting
this message, but I wonder if we should just ignore NULL file paths or fix the
source of problem (if there's one).

1 -
https://git.gnome.org/browse/glib/commit/?id=a5b58da6bf3bb21cbd3d030a369aad330f90f891

--
You are receiving this mail because:
You are the assignee for the bug.
_______________________________________________
Xfce-bugs mailing list
[hidden email]
https://mail.xfce.org/mailman/listinfo/xfce-bugs
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

[Bug 13663] GLib-CRITICAL **: g_file_test: assertion 'filename != NULL' failed

bugzilla-daemon
In reply to this post by bugzilla-daemon
https://bugzilla.xfce.org/show_bug.cgi?id=13663

Andre Miranda <[hidden email]> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
         Resolution|---                         |FIXED
             Status|NEW                         |RESOLVED

--- Comment #2 from Andre Miranda <[hidden email]> ---
Fixed in:
https://git.xfce.org/xfce/thunar/commit/?id=1d39355c9296c2bd09768b974b65e5762e97b192

--
You are receiving this mail because:
You are the assignee for the bug.
_______________________________________________
Xfce-bugs mailing list
[hidden email]
https://mail.xfce.org/mailman/listinfo/xfce-bugs
Loading...