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 499698 - crash in System Log: Wylogowanie/zamykanie sy...
crash in System Log: Wylogowanie/zamykanie sy...
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-11-26 09:46 UTC by orzeszko
Modified: 2009-12-28 14:42 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18


Description orzeszko 2007-11-26 09:46:04 UTC 
Version: 2.18.1

What were you doing when the application crashed?
Wylogowanie/zamykanie systemu
Log out/ shut down system


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.1-21.fc7 #1 SMP Thu Nov 1 21:09:24 EDT 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Fedora

Memory status: size: 40632320 vsize: 40632320 resident: 22024192 share: 14581760 rss: 22024192 rss_rlim: 4294967295
CPU usage: start_time: 1195899533 rtime: 297 utime: 265 stime: 32 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 -1208944928 (LWP 3143)]
(no debugging symbols found)
0x00110402 in __kernel_vsyscall ()

+ Trace 179666

Thread 1 (Thread -1208944928 (LWP 3143))

  • #0 __kernel_vsyscall
  • #1 __waitpid_nocancel
    from /lib/libpthread.so.0
  • #2 gtk_main_quit
    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 gtk_main_quit
    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 gtk_main_quit
    from /usr/lib/libgnomeui-2.so.0
  • #11 _SmcProcessMessage
    from /usr/lib/libSM.so.6
  • #12 IceProcessMessages
    from /usr/lib/libICE.so.6
  • #13 gtk_main_quit
    from /usr/lib/libgnomeui-2.so.0
  • #14 gtk_main_quit
    from /lib/libglib-2.0.so.0
  • #15 g_main_context_dispatch
    from /lib/libglib-2.0.so.0
  • #16 gtk_main_quit
    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 ---------------------
localuser:root being added to access control list
SESSION_MANAGER=local/unix:/tmp/.ICE-unix/3003
** Message: failed to load session from /root/.nautilus/saved-session-69B41T
** (gnome-system-monitor:3142): WARNING **: SELinux was found but is not enabled.
Nie można otworzyć pliku /usr/share/applications/openoffice.org-1.9-writer.desktop z aktywatorem panelu: Nie ma takiego pliku ani katalogu
Nie można otworzyć pliku /usr/share/applications/openoffice.org-1.9-impress.desktop z aktywatorem panelu: Nie ma takiego pliku ani katalogu
Nie można otworzyć pliku /usr/share/applications/openoffice.org-1.9-calc.desktop z aktywatorem panelu: Nie ma takiego pliku ani katalogu
Saving session: gnome-terminal --window-with-profile-internal-id=Default --show-menubar --role=gnome-terminal-3384--1669808228-1195821281 --active --geometry 125x39+0+25 --title root@server:/home/SAMB
--------------------------------------------------
Comment 1 Rob Bradford 2007-11-26 19:35:20 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 ***
Comment 2 Michel Machado 2009-12-28 14:42:42 UTC 
*** Bug 605570 has been marked as a duplicate of this bug. ***