Bug 620722 – crash in gThumb: Just pressed the import ...

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 620722 - crash in gThumb: Just pressed the import ...


Summary:	crash in gThumb: Just pressed the import ...


Status:	RESOLVED DUPLICATE of bug 620559

Product:	gthumb
Classification:	Other
Component:	general
Version:	2.11.x
Hardware:	Other All

Importance:	Normal critical
Target Milestone:	---
Assigned To:	Paolo Bacchilega
QA Contact:	Paolo Bacchilega

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2010-06-06 07:20 UTC by bcsaba
Modified:	2010-06-06 13:54 UTC

See Also:
GNOME target:	---
GNOME version:	2.29/2.30

Description bcsaba 2010-06-06 07:20:36 UTC

Version: 2.11.3

What were you doing when the application crashed?
Just pressed the import photos button


Distribution: Debian squeeze/sid
Gnome Release: 2.30.0 2010-04-26 (Debian)
BugBuddy Version: 2.30.0

System: Linux 2.6.32-trunk-amd64 #1 SMP Sun Jan 10 22:40:40 UTC 2010 x86_64
X Vendor: The X.Org Foundation
X Vendor Release: 10707000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Industrial
Icon Theme: gnome
GTK+ Modules: gnomebreakpad, canberra-gtk-module

Memory status: size: 541310976 vsize: 541310976 resident: 17412096 share: 13193216 rss: 17412096 rss_rlim: 18446744073709551615
CPU usage: start_time: 1275808792 rtime: 9 utime: 8 stime: 1 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100

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

[Thread debugging using libthread_db enabled]
[New Thread 0x7fd48c8fd710 (LWP 16968)]
[New Thread 0x7fd48c97e710 (LWP 16967)]
[New Thread 0x7fd48c9ff710 (LWP 16966)]
[New Thread 0x7fd48ca80710 (LWP 16965)]
[New Thread 0x7fd48cd15710 (LWP 16964)]
0x00007fd4a87b6b4d in __libc_waitpid (pid=16969, 
    stat_loc=<value optimized out>, options=0)
    at ../sysdeps/unix/sysv/linux/waitpid.c:41
	in ../sysdeps/unix/sysv/linux/waitpid.c

+ Trace 222268

Thread 1 (Thread 0x7fd4ac8d67c0 (LWP 16963))

#0 __libc_waitpid
at ../sysdeps/unix/sysv/linux/waitpid.c line 41
#1 IA__g_spawn_sync
at /tmp/buildd/glib2.0-2.24.1/glib/gspawn.c line 386
#2 IA__g_spawn_command_line_sync
at /tmp/buildd/glib2.0-2.24.1/glib/gspawn.c line 700
#3 ??
from /usr/lib/gtk-2.0/modules/libgnomebreakpad.so
#4 <signal handler called>
#5 IA__g_file_get_path
at /tmp/buildd/glib2.0-2.24.1/gio/gfile.c line 451
#6 ??
#7 gth_icon_cache_get_pixbuf
#8 _gth_browser_add_file_menu_item_full
#9 ??
#10 ??
#11 gth_browser_new
#12 ??
#13 ??
#14 main

A debugging session is active.

	Inferior 1 [process 16963] will be detached.

Quit anyway? (y or n) [answered Y; input not from terminal]


---- Critical and fatal warnings logged during execution ----

** GLib-GIO **: g_file_get_path: assertion `G_IS_FILE (file)' failed 
** GLib-GObject **: g_object_unref: assertion `G_IS_OBJECT (object)' failed 


----------- .xsession-errors (33595 sec old) ---------------------
(exe:25142): Gdk-WARNING **: XID collision, trouble ahead
(exe:25142): Gdk-WARNING **: XID collision, trouble ahead
(exe:25142): Gdk-WARNING **: XID collision, trouble ahead
** (gnome-system-monitor:25241): WARNING **: SELinux was found but is not enabled.
[24142:24142:99983582670:ERROR:chrome/browser/sync/profile_sync_service.cc(347)] Unrecoverable error detected -- ProfileSyncService unusable.
(exe:12762): Gdk-WARNING **: XID collision, trouble ahead
[12657:12657:171563319193:ERROR:chrome/browser/sync/profile_sync_service.cc(347)] Unrecoverable error detected -- ProfileSyncService unusable.
(evolution-alarm-notify:4886): evolution-alarm-notify-WARNING **: alarm.c:252: Requested removal of nonexistent alarm!
--------------------------------------------------

Comment 1 Akhil Laddha 2010-06-06 13:54:11 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 bug 620559 ***