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 145893 - eog crash
eog crash
Status: RESOLVED DUPLICATE of bug 146075
Product: eog
Classification: Core
Component: general
unspecified
Other other
: Normal normal
: ---
Assigned To: EOG Maintainers
EOG Maintainers
Depends on:
Blocks:
 
 
Reported: 2004-05-19 18:15 UTC by David Eriksson
Modified: 2004-12-22 21:47 UTC
See Also:
GNOME target: ---
GNOME version: 2.5/2.6



Description David Eriksson 2004-07-08 20:58:21 UTC
Distribution: Fedora Core release 2 (Tettnang)
Package: EOG
Severity: normal
Version: GNOME2.6. unspecified
Gnome-Distributor: Red Hat, Inc
Synopsis: eog crash
Bugzilla-Product: EOG
Bugzilla-Component: general
Bugzilla-Version: unspecified
BugBuddy-GnomeVersion: 2.0 (2.6.0)
Description:
No idea what happened, sorry. 

I'm running a fresh install of Fedora Core 2.


Debugging Information:

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)...[Thread debugging using
libthread_db enabled]
[New Thread -150842720 (LWP 22515)]
[New Thread 15051696 (LWP 22517)]
[Thread debugging using libthread_db enabled]
[New Thread -150842720 (LWP 22515)]
[New Thread 15051696 (LWP 22517)]
[New Thread 26794928 (LWP 22516)]
(no debugging symbols found)...[Thread debugging using libthread_db
enabled]
[New Thread -150842720 (LWP 22515)]
[New Thread 15051696 (LWP 22517)]
(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)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...0x00f6d402 in ?? ()

Thread 3 (Thread 26794928 (LWP 22516))

  • #0 ??
  • #1 __waitpid_nocancel
    from /lib/tls/libpthread.so.0
  • #2 libgnomeui_module_info_get
    from /usr/lib/libgnomeui-2.so.0
  • #3 <signal handler called>
  • #4 ORBit_adaptor_setup
    from /usr/lib/libORBit-2.so.0
  • #5 ORBit_handle_request
    from /usr/lib/libORBit-2.so.0
  • #6 giop_connection_handle_input
    from /usr/lib/libORBit-2.so.0
  • #7 link_connection_set_max_buffer
    from /usr/lib/libORBit-2.so.0
  • #8 link_servers_move_io_T
    from /usr/lib/libORBit-2.so.0
  • #9 g_main_depth
    from /usr/lib/libglib-2.0.so.0
  • #10 g_main_context_dispatch
    from /usr/lib/libglib-2.0.so.0
  • #11 g_main_context_dispatch
    from /usr/lib/libglib-2.0.so.0
  • #12 g_main_loop_run
    from /usr/lib/libglib-2.0.so.0
  • #13 link_thread_io_context
    from /usr/lib/libORBit-2.so.0
  • #14 g_static_private_free
    from /usr/lib/libglib-2.0.so.0
  • #15 start_thread
    from /lib/tls/libpthread.so.0
  • #16 clone
    from /lib/tls/libc.so.6




------- Bug moved to this database by unknown@bugzilla.gnome.org 2004-07-08 16:58 -------


Unknown platform unknown. Setting to default platform "Other".
Unknown milestone "unknown" in product "EOG".
   Setting to default milestone for this product, '---'
Setting to default status "UNCONFIRMED".
Setting qa contact to the default for this product.
   This bug either had no qa contact or an invalid one.

Comment 1 Jens Finke 2004-07-09 07:00:54 UTC
But you can certainly tell us what you did. Did you just start eog and it
crashed? Otherwise it's hard to reproduce it and nearly impossible to fix it.
Comment 2 David Eriksson 2004-07-09 17:07:05 UTC
I'm aware of the lack of information, maybe I would have known more 2004-05-19
when I reported this bug via the bug-buddy. It's a pity it did not enter
Bugzilla until yesterday... :-(

Maybe this is not an eog-specific bug? Take a look at these bugs and the bugs
their duplicates:

bug 146075
bug 146564

They all have this backtrace in common:

  • #3 <signal handler called>
  • #4 ORBit_adaptor_setup
    from /usr/lib/libORBit-2.so.0
  • #5 ORBit_handle_request
    from /usr/lib/libORBit-2.so.0
  • #6 giop_connection_handle_input
    from /usr/lib/libORBit-2.so.0
  • #7 link_connection_set_max_buffer
    from /usr/lib/libORBit-2.so.0
  • #8 link_servers_move_io_T
    from /usr/lib/libORBit-2.so.0
  • #9 g_main_depth
    from /usr/lib/libglib-2.0.so.0
  • #10 g_main_context_dispatch
    from /usr/lib/libglib-2.0.so.0
  • #11 g_main_context_dispatch
    from /usr/lib/libglib-2.0.so.0

Comment 3 David Eriksson 2004-07-09 17:10:21 UTC
Never mind bug 146564, sorry for the confusion. Maybe just resolve this bug as a
duplicate of bug 146075?
Comment 4 Matthew Gatto 2004-09-27 15:45:33 UTC
David: Good catch, thanks.
Comment 5 Matthew Gatto 2004-09-27 15:47:59 UTC

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