After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 347400 - GIMP crashes on File/Open
GIMP crashes on File/Open
Status: RESOLVED DUPLICATE of bug 347066
Product: GIMP
Classification: Other
Component: User Interface
2.3.x
Other All
: Normal critical
: ---
Assigned To: GIMP Bugs
GIMP Bugs
Depends on:
Blocks:
 
 
Reported: 2006-07-13 13:40 UTC by Christian Stangier
Modified: 2008-01-15 14:07 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Christian Stangier 2006-07-13 13:40:38 UTC 
Steps to reproduce:
1. Click on File/Open
2. Cccrash.


Stack trace:
Gtk-CRITICAL **: gtk_file_system_path_to_uri: assertion `path != NULL' failed
aborting...
gimp: terminated: Aborted


Program received signal SIG33, Real-time event 33.

+ Trace 69301

Thread NaN (LWP 18971)

  • #0 __kernel_vsyscall
  • #1 pthread_cond_wait
    from /lib/tls/libpthread.so.0
  • #2 g_async_queue_push_sorted
    from /usr/lib/libglib-2.0.so.0
  • #3 g_thread_pool_free
    from /usr/lib/libglib-2.0.so.0
  • #4 g_static_private_free
    from /usr/lib/libglib-2.0.so.0
  • #5 start_thread
    from /lib/tls/libpthread.so.0
  • #6 clone
    from /lib/tls/libc.so.6 

Other information:
Comment 1 Sven Neumann 2006-07-13 14:05:25 UTC 
Let me guess, you are running gimp with G_DEBUG=fatal-warnings and you hit an otherwise harmless assertion in GTK+ 2.10. Can you explain to me why you are filing a critical bug-report against GIMP then?


*** This bug has been marked as a duplicate of 347066 ***
Comment 2 Christian Stangier 2006-07-13 14:21:20 UTC 
Nope, you guessed wrong: G_DEBUG is fatal_criticals.
I was reporting this because it only occurs in GIMP. The gtk-filechooser is fine in every other application.
Comment 3 Sven Neumann 2006-07-15 16:07:13 UTC 
If there's a warning with GTK+ 2.10 but not with GTK+ 2.8, that's still a GTK+ bug then.