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 464494 - crash in System Log: nothing, just initiated ...
crash in System Log: nothing, just initiated ...
Status: RESOLVED DUPLICATE of bug 442846
Product: gnome-utils
Classification: Deprecated
Component: logview
2.18.x
Other All
: High critical
: ---
Assigned To: gnome-utils Maintainers
gnome-utils Maintainers
Depends on:
Blocks:
 
 
Reported: 2007-08-07 21:19 UTC by yurii.kantonistov
Modified: 2007-08-08 20:31 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18


Description yurii.kantonistov 2007-08-07 21:19:33 UTC 
Version: 2.18.1

What were you doing when the application crashed?
nothing, just initiated system restart


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.3228.fc7 #1 SMP Tue Jun 12 14:56:37 EDT 2007 x86_64
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: Enforcing
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Fedora

Memory status: size: 278523904 vsize: 278523904 resident: 21262336 share: 15060992 rss: 21262336 rss_rlim: 18446744073709551615
CPU usage: start_time: 1186515841 rtime: 171 utime: 157 stime: 14 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 "/lib64/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 46912496373136 (LWP 3475)]
(no debugging symbols found)
0x000000327e80d865 in waitpid () from /lib64/libpthread.so.0

+ Trace 153571

Thread 1 (Thread 46912496373136 (LWP 3475))

  • #0 waitpid
    from /lib64/libpthread.so.0
  • #1 gtk_main_quit
    from /usr/lib64/libgnomeui-2.so.0
  • #2 <signal handler called>
  • #3 ??
  • #4 _gnome_marshal_BOOLEAN__INT_ENUM_BOOLEAN_ENUM_BOOLEAN
    from /usr/lib64/libgnomeui-2.so.0
  • #5 g_closure_invoke
    from /lib64/libgobject-2.0.so.0
  • #6 gtk_main_quit
    from /lib64/libgobject-2.0.so.0
  • #7 g_signal_emit_valist
    from /lib64/libgobject-2.0.so.0
  • #8 g_signal_emit
    from /lib64/libgobject-2.0.so.0
  • #9 gtk_main_quit
    from /usr/lib64/libgnomeui-2.so.0
  • #10 _SmcProcessMessage
    from /usr/lib64/libSM.so.6
  • #11 IceProcessMessages
    from /usr/lib64/libICE.so.6
  • #12 gtk_main_quit
    from /usr/lib64/libgnomeui-2.so.0
  • #13 g_main_context_dispatch
    from /lib64/libglib-2.0.so.0
  • #14 gtk_main_quit
    from /lib64/libglib-2.0.so.0
  • #15 g_main_loop_run
    from /lib64/libglib-2.0.so.0
  • #16 gtk_main
    from /usr/lib64/libgtk-x11-2.0.so.0
  • #17 main
  • #0 waitpid
    from /lib64/libpthread.so.0 


----------- .xsession-errors ---------------------
AFD changed from -2 to -1
[mpeg4 @ 0x2aaab916eb30]frame skip 8
AFD changed from -2 to -1
AFD changed from -2 to -1
AFD changed from -2 to -1
[mpeg4 @ 0x2aaaad340b30]frame skip 8
[mpeg4 @ 0x2aaaad340b30]frame skip 8
[mpeg4 @ 0x2aaaad340b30]frame skip 8
AFD changed from -2 to -1
Loading /lib/kbd/keymaps/i386/qwerty/us.map.gz
Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x4000003 (Evince Doc)
Window manager warning: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed.
dpy: 0x63b090
evt/error/major/minor: 111/174/1/0
Saving session: gnome-terminal --window-with-profile-internal-id=monochrome --show-menubar --role=gnome-terminal-3506-103747452-1186516133 --active --geometry 139x42+6+31 --title root@EARTH:~ --workin
--------------------------------------------------
Comment 1 Bruno Boaventura 2007-08-08 20:31:41 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 442846 ***