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 404102 - crash in gThumb Image Viewer: searching within g-Thumb...
crash in gThumb Image Viewer: searching within g-Thumb...
Status: RESOLVED FIXED
Product: gthumb
Classification: Other
Component: general
unspecified
Other All
: High critical
: ---
Assigned To: Paolo Bacchilega
Paolo Bacchilega
: 404179 409767 426251 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2007-02-03 22:32 UTC by Trevor Lupton
Modified: 2007-04-04 14:58 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16



Description Trevor Lupton 2007-02-03 22:32:21 UTC
What were you doing when the application crashed?
searching within g-Thumb via smb


Distribution: Fedora Core release 6 (Zod)
Gnome Release: 2.16.0 2006-09-04 (Red Hat, Inc)
BugBuddy Version: 2.16.0

System: Linux 2.6.19-1.2895.fc6 #1 SMP Wed Jan 10 19:28:18 EST 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 70101000
Selinux: Enforcing
Accessibility: Disabled
----------- .xsession-errors ---------------------
This is normally a bug in some application using the D-Bus library.
process 3387: arguments to dbus_pending_call_unref() were incorrect, assertion "pending != NULL" failed in file dbus-pending-call.c line 563.
This is normally a bug in some application using the D-Bus library.
(nautilus:3387): Gtk-CRITICAL **: gtk_window_realize_icon: assertion `info->icon_pixmap == NULL' failed
process 3387: arguments to dbus_pending_call_get_completed() were incorrect, assertion "pending != NULL" failed in file dbus-pending-call.c line 650.
This is normally a bug in some application using the D-Bus library.
process 3387: arguments to dbus_pending_call_steal_reply() were incorrect, assertion "pending != NULL" failed in file dbus-pending-call.c line 673.
This is normally a bug in some application using the D-Bus library.
process 3387: arguments to dbus_pending_call_unref() were incorrect, assertion "pending != NULL" failed in file dbus-pending-call.c line 563.
This is normally a bug in some application using the D-Bus library.
** (bug-buddy:7292): WARNING **: Couldn't load icon for Open Folder
** (bug-buddy:7345): WARNING **: Couldn't load icon for Open Folder
--------------------------------------------------

Memory status: size: 289226752 vsize: 0 resident: 289226752 share: 0 rss: 25100288 rss_rlim: 0
CPU usage: start_time: 1170541694 rtime: 0 utime: 357 stime: 0 cutime:332 cstime: 0 timeout: 25 it_real_value: 0 frequency: 0

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 -1209010480 (LWP 7310)]
[New Thread -1504863344 (LWP 7326)]
[New Thread -1494373488 (LWP 7325)]
[New Thread -1483883632 (LWP 7324)]
[New Thread -1473393776 (LWP 7323)]
[New Thread -1378976880 (LWP 7313)]
[New Thread -1263555696 (LWP 7312)]
(no debugging symbols found)
0x00ac1402 in __kernel_vsyscall ()

Thread 1 (Thread -1209010480 (LWP 7310))

  • #0 __kernel_vsyscall
  • #1 waitpid
    from /lib/libpthread.so.0
  • #2 gnome_gtk_module_info_get
    from /usr/lib/libgnomeui-2.so.0
  • #3 <signal handler called>
  • #4 g_cclosure_marshal_VOID__BOOLEAN
    from /usr/lib/libgtk-x11-2.0.so.0
  • #5 g_cclosure_marshal_VOID__BOOLEAN
    from /usr/lib/libgtk-x11-2.0.so.0
  • #6 g_cclosure_marshal_VOID__BOOLEAN
    from /usr/lib/libgtk-x11-2.0.so.0
  • #7 gtk_file_chooser_button_new
    from /usr/lib/libgtk-x11-2.0.so.0
  • #8 g_cclosure_marshal_VOID__VOID
    from /lib/libgobject-2.0.so.0
  • #9 g_closure_invoke
    from /lib/libgobject-2.0.so.0
  • #10 g_signal_chain_from_overridden
    from /lib/libgobject-2.0.so.0
  • #11 g_signal_emitv
    from /lib/libgobject-2.0.so.0
  • #12 gtk_bin_get_child
    from /usr/lib/libgtk-x11-2.0.so.0
  • #13 gtk_bin_get_child
    from /usr/lib/libgtk-x11-2.0.so.0
  • #14 gtk_bin_get_child
    from /usr/lib/libgtk-x11-2.0.so.0
  • #15 gtk_bindings_activate_event
    from /usr/lib/libgtk-x11-2.0.so.0
  • #16 gtk_widget_freeze_child_notify
    from /usr/lib/libgtk-x11-2.0.so.0
  • #17 gtk_entry_set_text
    from /usr/lib/libgtk-x11-2.0.so.0
  • #18 gtk_marshal_BOOLEAN__VOID
    from /usr/lib/libgtk-x11-2.0.so.0
  • #19 g_value_set_static_boxed
    from /lib/libgobject-2.0.so.0
  • #20 g_closure_invoke
    from /lib/libgobject-2.0.so.0
  • #21 g_signal_chain_from_overridden
    from /lib/libgobject-2.0.so.0
  • #22 g_signal_emit_valist
    from /lib/libgobject-2.0.so.0
  • #23 g_signal_emit
    from /lib/libgobject-2.0.so.0
  • #24 gtk_widget_get_default_style
    from /usr/lib/libgtk-x11-2.0.so.0
  • #25 gtk_window_propagate_key_event
    from /usr/lib/libgtk-x11-2.0.so.0
  • #26 gtk_window_activate_key
    from /usr/lib/libgtk-x11-2.0.so.0
  • #27 gtk_marshal_BOOLEAN__VOID
    from /usr/lib/libgtk-x11-2.0.so.0
  • #28 g_value_set_static_boxed
    from /lib/libgobject-2.0.so.0
  • #29 g_closure_invoke
    from /lib/libgobject-2.0.so.0
  • #30 g_signal_chain_from_overridden
    from /lib/libgobject-2.0.so.0
  • #31 g_signal_emit_valist
    from /lib/libgobject-2.0.so.0
  • #32 g_signal_emit
    from /lib/libgobject-2.0.so.0
  • #33 gtk_widget_get_default_style
    from /usr/lib/libgtk-x11-2.0.so.0
  • #34 gtk_propagate_event
    from /usr/lib/libgtk-x11-2.0.so.0
  • #35 gtk_main_do_event
    from /usr/lib/libgtk-x11-2.0.so.0
  • #36 gdk_add_client_message_filter
    from /usr/lib/libgdk-x11-2.0.so.0
  • #37 g_main_context_dispatch
    from /lib/libglib-2.0.so.0
  • #38 g_main_context_check
    from /lib/libglib-2.0.so.0
  • #39 g_main_loop_run
    from /lib/libglib-2.0.so.0
  • #40 gtk_main
    from /usr/lib/libgtk-x11-2.0.so.0
  • #41 main
  • #0 __kernel_vsyscall

Comment 1 Michael Chudobiak 2007-02-04 10:20:30 UTC
*** Bug 404179 has been marked as a duplicate of this bug. ***
Comment 2 Michael Chudobiak 2007-02-15 18:10:26 UTC
Could you clarify what you were doing when this crash occurred, and how the smb share was being used? (Was it mounted with mount -t smb, or were you browsing using the file chooser, or....)

The released versions of gThumb (2.9.1 and earlier) do not fully support gnome-vfs for browsing remote shares. The development version in svn does.

- Mike
Comment 3 tech 2007-02-19 23:26:36 UTC
I'm sorry, I can't recall any more precisely what it was I was up to when the crash occurred.  It is likely that I was browsing a Windows XP shared folder across the network.  I've been using the computer that experienced the crash for evaluating distributions and have made so many changes (and had so many problems) that I no longer remember any particular incident with useful clarity.

Thank you for your work,
Ben
Comment 4 Trevor Lupton 2007-02-20 00:54:49 UTC
(In reply to comment #2)
> Could you clarify what you were doing when this crash occurred, and how the smb
> share was being used? (Was it mounted with mount -t smb, or were you browsing
> using the file chooser, or....)
> 
> The released versions of gThumb (2.9.1 and earlier) do not fully support
> gnome-vfs for browsing remote shares. The development version in svn does.
> 
> - Mike
> 

Hi Mike

It was not mounted. My memory is of browsing from the "other" option from the location bar. From there typing the smb share into "location", eg smb://ls-300g-01/share/pictures (a share on a Buffalo Link Station network storage drive. At that point crashing happened. However, I can not now replicate the problem! I do take the Fedora updates on a regular basis - mabe something has changed? Currently gThunb is at 2.7.8

Hope this helps

Trevor
Comment 5 Michael Chudobiak 2007-02-20 12:44:00 UTC
Trevor,

Full "smb://" support was only introduced as of 2.9.2, which was released yesterday. It isn't surprising that 2.7.x crashed when accessing smb.

If you need smb support, try installing 2.9.2:

http://ftp.gnome.org/pub/gnome/sources/gthumb/2.9/

- Mike
Comment 6 palfrey 2007-02-21 13:42:51 UTC
*** Bug 409767 has been marked as a duplicate of this bug. ***
Comment 7 Michael Chudobiak 2007-04-04 14:58:23 UTC
*** Bug 426251 has been marked as a duplicate of this bug. ***