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 510571 - crash in System Log: Shutting down the comput...
crash in System Log: Shutting down the comput...
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: 2008-01-19 09:58 UTC by riccilawhk
Modified: 2008-02-13 10:24 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18


Description riccilawhk 2008-01-19 09:58:27 UTC 
Version: 2.18.1

What were you doing when the application crashed?
Shutting down the computer when at Xwindows.		


Distribution: Fedora release 7 (Moonshine)
Gnome Release: 2.18.3 2007-11-13 (Red Hat, Inc)
BugBuddy Version: 2.18.0

System: Linux 2.6.23.12-52.fc7 #1 SMP Tue Dec 18 21:18:02 EST 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Clearlooks

Memory status: size: 92758016 vsize: 92758016 resident: 40042496 share: 31895552 rss: 40042496 rss_rlim: 4294967295
CPU usage: start_time: 1200735636 rtime: 117 utime: 110 stime: 7 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 -1209018656 (LWP 6517)]
(no debugging symbols found)
0x0012d402 in __kernel_vsyscall ()

+ Trace 185933

Thread 1 (Thread -1209018656 (LWP 6517))

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


----------- .xsession-errors (19 sec old) ---------------------
** Message: Automatic missing codec installation not supported (helper script missing)
kbuildsycoca running...
DCOP Cleaning up dead connections.
Invalid entry (missing '=') at /tmp/kde-root/kconf_updateXUnF7a.tmp:1
Invalid entry (missing '=') at /tmp/kde-root/kconf_updateyeA4cc.tmp:1
Launched ok, pid = 6836
0
0
Window manager warning: Invalid WM_TRANSIENT_FOR window 0x65 specified for 0x4e00040 (Kaffeine 0).
QLayout "unnamed" added to QWidget "unnamed", which already has a layout
Window manager warning: Invalid WM_TRANSIENT_FOR window 0x4e00007 specified for 0x4e00226 (Kaffeine P).
Window manager warning: Invalid WM_TRANSIENT_FOR window 0x4e00007 specified for 0x4e00328 (Kaffeine P).
Window manager warning: Invalid WM_TRANSIENT_FOR window 0x65 specified for 0x4e0036b (xine Error).
closing
gnome-mount 0.6
--------------------------------------------------
Comment 1 Gianluca Borello 2008-02-13 10:24:24 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 442846 ***