GNOME Bugzilla – Bug 301094
EOG crashes on one user, works on root
Last modified: 2005-07-15 08:34:11 UTC
Distribution/Version: Red Hat Fedora Core 3 EOG never works, no matter from where it is being started. If started from command-line, this message is printed: (eog:22769): GLib-CRITICAL **: file gutf8.c: line 1537 (g_utf8_validate): assertion `str != NULL' failed Steps to reproduce the crash: 1. Try to start "Eye of GNOME" Expected Results: How often does this happen? Always. Additional Information: Works on root, doesn't work on my user account.
Thanks for the bug report. Without a stack trace from the crash it's very hard to determine what caused it. Can you provide us with one? Please see http://live.gnome.org/GettingTraces for more information on how to do so.
I was sure I attached it... Sorry... Here it is: Backtrace was generated from '/usr/bin/eog' (no debugging symbols found)...Using host libthread_db library "/lib/tls/libthread_db.so.1". (no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...[Thread debugging using libthread_db enabled] [New Thread -151112000 (LWP 22741)] (no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...0x00a997a2 in _dl_sysinfo_int80 () from /lib/ld-linux.so.2
+ Trace 58386
Thread 1 (Thread -151112000 (LWP 22741))
It suddenly works. Haven't change a thing - but today it started working again. Very strange! Thank you for the reading and trying to help, though... Strange thing..! O.R.
*** This bug has been marked as a duplicate of 303272 ***