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 320189 - bug
bug
Status: RESOLVED DUPLICATE of bug 317694
Product: gnome-utils
Classification: Deprecated
Component: logview
2.12.x
Other other
: Normal normal
: ---
Assigned To: gnome-utils Maintainers
gnome-utils Maintainers
Depends on:
Blocks:
 
 
Reported: 2005-10-29 19:29 UTC by fatloach
Modified: 2006-06-20 19:06 UTC
See Also:
GNOME target: ---
GNOME version: 2.11/2.12



Description fatloach 2005-10-29 19:29:35 UTC
From: fatloach <fatloach@gmail.com>
To: submit@bugs.gnome.org
X-Mailer: bug-buddy 2.12.1
Subject: log bug

Distribution: Ubuntu 5.10 (breezy)
Package: gnome-utils
Severity: Normal
Version: GNOME2.12.1 2.12.1
Gnome-Distributor: Ubuntu
Synopsis: log bug
Bugzilla-Product: gnome-utils
Bugzilla-Component: logview
Bugzilla-Version: 2.12.1
BugBuddy-GnomeVersion: 2.0 (2.12.0)
Description:
Description of the crash:


Steps to reproduce the crash:
1. 
2. 
3. 

Expected Results:


How often does this happen?


Additional Information:



Debugging Information:

Backtrace was generated from '/usr/bin/gnome-system-log'

(no debugging symbols found)
Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1".
(no debugging symbols found)
`system-supplied DSO at 0xffffe000' has disappeared; keeping its
symbols.
(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)
[Thread debugging using libthread_db enabled]
[New Thread -1222887744 (LWP 7691)]
(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)
0xffffe410 in __kernel_vsyscall ()

Thread 1 (Thread -1222887744 (LWP 7691))

  • #0 __kernel_vsyscall
  • #1 __waitpid_nocancel
    from /lib/tls/i686/cmov/libpthread.so.0
  • #2 libgnomeui_module_info_get
    from /usr/lib/libgnomeui-2.so.0
  • #3 <signal handler called>
  • #4 __strtouq_internal
    from /lib/tls/i686/cmov/libc.so.6
  • #5 __strtol_internal
    from /lib/tls/i686/cmov/libc.so.6
  • #6 atoi
    from /lib/tls/i686/cmov/libc.so.6
  • #7 handle_row_expansion_cb
  • #8 _gtk_marshal_VOID__BOXED_BOXED
    from /usr/lib/libgtk-x11-2.0.so.0
  • #9 g_closure_invoke
    from /usr/lib/libgobject-2.0.so.0
  • #10 g_signal_stop_emission
    from /usr/lib/libgobject-2.0.so.0
  • #11 g_signal_emit_valist
    from /usr/lib/libgobject-2.0.so.0
  • #12 g_signal_emit
    from /usr/lib/libgobject-2.0.so.0
  • #13 gtk_tree_view_scroll_to_cell
    from /usr/lib/libgtk-x11-2.0.so.0
  • #14 gtk_tree_view_expand_row
    from /usr/lib/libgtk-x11-2.0.so.0
  • #15 logview_draw_log_lines
  • #16 log_repaint
  • #17 logview_select_log
  • #18 logview_version_selector_changed
  • #19 g_cclosure_marshal_VOID__VOID
    from /usr/lib/libgobject-2.0.so.0
  • #20 g_closure_invoke
    from /usr/lib/libgobject-2.0.so.0
  • #21 g_signal_stop_emission
    from /usr/lib/libgobject-2.0.so.0
  • #22 g_signal_emit_valist
    from /usr/lib/libgobject-2.0.so.0
  • #23 g_signal_emit
    from /usr/lib/libgobject-2.0.so.0
  • #24 _gtk_tree_selection_internal_select_node
    from /usr/lib/libgtk-x11-2.0.so.0
  • #25 gtk_tree_selection_select_path
    from /usr/lib/libgtk-x11-2.0.so.0
  • #26 loglist_find_logname
  • #27 main
  • #0 __kernel_vsyscall




------- Bug moved to this database by unknown@gnome.bugs 2005-10-29 19:29 UTC -------


Unknown version 2.12.1 in product gnome-utils.  Setting version to "2.12.x".
The original reporter of this bug does not have
   an account here. Reassigning to the person who moved
   it here, unknown@gnome.bugs.
   Previous reporter was fatloach@gmail.com.

Comment 1 Olivier Le Thanh Duong 2005-10-29 21:08:37 UTC
Thanks for taking the time to report this bug.
This bug report isn't very useful because it doesn't describe the bug well. If
you have time and can still reproduce the bug, please read
http://bugzilla.gnome.org/bug-HOWTO.html and add a description of how to
reproduce this bug.

You'll also need to add a stack trace; please see
http://live.gnome.org/GettingTraces for more information about how to do so.
Comment 2 Elijah Newren 2006-06-20 19:06:23 UTC
No response, but it's a duplicate of bug 317694 anyway (which has been reported to be fixed now)

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