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 517352 - crash in gThumb Image Viewer: I clicked on the gthumb ...
crash in gThumb Image Viewer: I clicked on the gthumb ...
Status: RESOLVED DUPLICATE of bug 364113
Product: gthumb
Classification: Other
Component: general
unspecified
Other All
: High critical
: ---
Assigned To: Paolo Bacchilega
Paolo Bacchilega
Depends on:
Blocks:
 
 
Reported: 2008-02-19 00:47 UTC by Terry
Modified: 2008-02-19 13:18 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18


Description Terry 2008-02-19 00:47:41 UTC 
What were you doing when the application crashed?
I clicked on the gthumb launcher and this bug report came up


Distribution: Fedora release 7 (Moonshine)
Gnome Release: 2.18.3 2007-11-13 (Red Hat, Inc)
BugBuddy Version: 2.18.0

System: Linux 2.6.23.15-80.fc7 #1 SMP Sun Feb 10 17:29:10 EST 2008 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: Permissive
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Clearlooks

Memory status: size: 89415680 vsize: 89415680 resident: 34447360 share: 29974528 rss: 34447360 rss_rlim: 4294967295
CPU usage: start_time: 1203381953 rtime: 30 utime: 26 stime: 4 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100

Backtrace was generated from '/usr/bin/gthumb'

(no debugging symbols found)
Using host libthread_db library "/lib/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1208871200 (LWP 3326)]
[New Thread -1268786288 (LWP 3334)]
[New Thread -1268257904 (LWP 3333)]
[New Thread -1267729520 (LWP 3332)]
[New Thread -1255646320 (LWP 3330)]
[New Thread -1255117936 (LWP 3329)]
(no debugging symbols found)
0x00110402 in __kernel_vsyscall ()

+ Trace 189675

Thread 1 (Thread -1208871200 (LWP 3326))

  • #0 __kernel_vsyscall
  • #1 waitpid
    from /lib/libpthread.so.0
  • #2 ??
    from /usr/lib/libgnomeui-2.so.0
  • #3 <signal handler called>
  • #4 g_string_new
    from /lib/libglib-2.0.so.0
  • #5 gnome_vfs_uri_to_string
    from /usr/lib/libgnomevfs-2.so.0
  • #6 ??
    from /usr/lib/gtk-2.0/2.10.0/filesystems/libgnome-vfs.so
  • #7 ??
    from /usr/lib/libgnomevfs-2.so.0
  • #8 ??
  • #9 ??
  • #10 ??
  • #11 ??
    from /usr/lib/libgnomevfs-2.so.0
  • #12 ??
  • #13 ??
    from /lib/libpthread.so.0
  • #14 ??
  • #15 ??
    from /usr/lib/libgnomevfs-2.so.0
  • #16 ??
  • #17 ??
  • #18 ??
  • #19 g_slice_alloc
    from /lib/libglib-2.0.so.0
  • #0 __kernel_vsyscall 


----------- .xsession-errors (86 sec old) ---------------------
localuser:terry being added to access control list
SESSION_MANAGER=local/unix:/tmp/.ICE-unix/2964
Error: permissions error in pam_timestamp_check
** (nautilus:3081): WARNING **: Possibly invalid new URI 'file:///mnt/sdc11/canon-photos/photo albums/photo album 08/feb 08'
This can cause subtle evils like #48423
--------------------------------------------------
Comment 1 Michael Chudobiak 2008-02-19 13:18:02 UTC 
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.


*** This bug has been marked as a duplicate of 364113 ***