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 449164 - crash in System Log: I was clicking on an apa...
crash in System Log: I was clicking on an apa...
Status: RESOLVED DUPLICATE of bug 355887
Product: gnome-utils
Classification: Deprecated
Component: logview
2.18.x
Other All
: High critical
: ---
Assigned To: gnome-utils Maintainers
gnome-utils Maintainers
: 452817 454925 459224 461318 464638 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2007-06-19 15:36 UTC by rchamberland
Modified: 2007-09-25 18:44 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18


Description rchamberland 2007-06-19 15:36:30 UTC 
Version: 2.18.1

What were you doing when the application crashed?
I was clicking on an apache access log name to see log entries.


Distribution: Fedora release 7 (Moonshine)
Gnome Release: 2.18.2 2007-05-28 (Red Hat, Inc)
BugBuddy Version: 2.18.0

System: Linux 2.6.21-1.3194.fc7 #1 SMP Wed May 23 22:35:01 EDT 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: Enforcing
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Fedora

Memory status: size: 100425728 vsize: 100425728 resident: 12996608 share: 9396224 rss: 12996608 rss_rlim: 4294967295
CPU usage: start_time: 1181741786 rtime: 3787 utime: 3692 stime: 95 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100

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

(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 -1209030944 (LWP 3176)]
(no debugging symbols found)
0x00474402 in __kernel_vsyscall ()

+ Trace 142176

Thread 1 (Thread -1209030944 (LWP 3176))

  • #0 __kernel_vsyscall
  • #1 waitpid
    from /lib/libpthread.so.0
  • #2 gtk_main_quit
    from /usr/lib/libgnomeui-2.so.0
  • #3 <signal handler called>
  • #4 strrchr
    from /lib/libc.so.6
  • #5 logview_repaint
  • #6 logview_select_log
  • #7 ??
  • #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 gtk_main_quit
    from /lib/libgobject-2.0.so.0
  • #11 g_signal_emit_valist
    from /lib/libgobject-2.0.so.0
  • #12 g_signal_emit
    from /lib/libgobject-2.0.so.0
  • #13 gtk_main_quit
    from /usr/lib/libgtk-x11-2.0.so.0
  • #14 gtk_main_quit
    from /usr/lib/libgtk-x11-2.0.so.0
  • #15 gtk_main_quit
    from /usr/lib/libgtk-x11-2.0.so.0
  • #16 gtk_main_quit
    from /usr/lib/libgtk-x11-2.0.so.0
  • #17 gtk_main_quit
    from /lib/libgobject-2.0.so.0
  • #18 g_closure_invoke
    from /lib/libgobject-2.0.so.0
  • #19 gtk_main_quit
    from /lib/libgobject-2.0.so.0
  • #20 g_signal_emit_valist
    from /lib/libgobject-2.0.so.0
  • #21 g_signal_emit
    from /lib/libgobject-2.0.so.0
  • #22 gtk_main_quit
    from /usr/lib/libgtk-x11-2.0.so.0
  • #23 gtk_propagate_event
    from /usr/lib/libgtk-x11-2.0.so.0
  • #24 gtk_main_do_event
    from /usr/lib/libgtk-x11-2.0.so.0
  • #25 gtk_main_quit
    from /usr/lib/libgdk-x11-2.0.so.0
  • #26 g_main_context_dispatch
    from /lib/libglib-2.0.so.0
  • #27 gtk_main_quit
    from /lib/libglib-2.0.so.0
  • #28 g_main_loop_run
    from /lib/libglib-2.0.so.0
  • #29 gtk_main
    from /usr/lib/libgtk-x11-2.0.so.0
  • #30 main
  • #0 __kernel_vsyscall 






Comment 1


Pedro Villavicencio





          2007-06-20 01:41:16 UTC
        



Thanks for taking the time to report this bug.
Unfortunately, that stack trace is missing some elements that will help a lot to solve the problem, so it will be hard for the developers to fix that crash. Can you get us a stack trace with debugging symbols? Please see http://live.gnome.org/GettingTraces for more information on how to do so and reopen this bug or report a new one. Thanks in advance!







Comment 2


Teppo Turtiainen





          2007-07-11 19:59:39 UTC
        



*** Bug 452817 has been marked as a duplicate of this bug. ***






Comment 3


Teppo Turtiainen





          2007-07-11 19:59:50 UTC
        



*** Bug 454925 has been marked as a duplicate of this bug. ***






Comment 4


Pedro Villavicencio





          2007-07-27 00:28:22 UTC
        



*** Bug 459224 has been marked as a duplicate of this bug. ***






Comment 5


Pedro Villavicencio





          2007-07-29 14:21:53 UTC
        



*** Bug 461318 has been marked as a duplicate of this bug. ***






Comment 6


Bruno Boaventura





          2007-08-08 20:33:08 UTC
        



*** Bug 464638 has been marked as a duplicate of this bug. ***






Comment 7


Emmanuele Bassi (:ebassi)





          2007-09-25 18:44:27 UTC
        



Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but we are happy to tell you that the problem has already been fixed. It should be solved in the next software version. You may want to check for a software upgrade.


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