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 392303 - crash in System Log: Opening Log Viewer Durin...
crash in System Log: Opening Log Viewer Durin...
Status: RESOLVED DUPLICATE of bug 366458
Product: gnome-utils
Classification: Deprecated
Component: logview
2.16.x
Other All
: High critical
: ---
Assigned To: gnome-utils Maintainers
gnome-utils Maintainers
Depends on:
Blocks:
 
 
Reported: 2007-01-03 13:52 UTC by abdullah_alhamad
Modified: 2007-01-03 18:12 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16


Description abdullah_alhamad 2007-01-03 13:52:53 UTC 
Version: 2.16.0

What were you doing when the application crashed?
Opening Log Viewer During updating software									


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

Memory status: size: 50651136 vsize: 0 resident: 50651136 share: 0 rss: 13549568 rss_rlim: 0
CPU usage: start_time: 1167843070 rtime: 0 utime: 23 stime: 0 cutime:15 cstime: 0 timeout: 8 it_real_value: 0 frequency: 0

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 -1209137456 (LWP 4785)]
(no debugging symbols found)
0x0091f402 in __kernel_vsyscall ()

+ Trace 98999

Thread 1 (Thread -1209137456 (LWP 4785))

  • #0 __kernel_vsyscall
  • #1 __waitpid_nocancel
    from /lib/libpthread.so.0
  • #2 gnome_gtk_module_info_get
    from /usr/lib/libgnomeui-2.so.0
  • #3 <signal handler called>
  • #4 gtk_main_quit
  • #5 gtk_main_quit
  • #6 gtk_main_quit
  • #7 gtk_main_quit
  • #8 gtk_main_quit
  • #9 __libc_start_main
    from /lib/libc.so.6
  • #10 gtk_main_quit
  • #0 __kernel_vsyscall 






Comment 1


Susana





          2007-01-03 18:12:57 UTC
        



Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but the maintainers need more information to fix the bug. Could you please answer the questions in the other report in order to help the developers?


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