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 443359 - crash in System Log: Restarting
crash in System Log: Restarting
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
: 443379 443994 444005 444988 447338 449189 450317 462664 462924 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2007-06-02 23:01 UTC by arch
Modified: 2007-08-07 20:43 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18



Description arch 2007-06-02 23:01:53 UTC
Version: 2.18.0

What were you doing when the application crashed?
Restarting


Distribution: Fedora release 7 (Moonshine)
Gnome Release: 2.18.0 2007-03-23 (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: Permissive
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Fedora

Memory status: size: 101437440 vsize: 101437440 resident: 15564800 share: 10964992 rss: 15564800 rss_rlim: 4294967295
CPU usage: start_time: 1180821527 rtime: 399 utime: 377 stime: 22 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 -1208523040 (LWP 3583)]
(no debugging symbols found)
0x007b5402 in __kernel_vsyscall ()

Thread 1 (Thread -1208523040 (LWP 3583))

  • #0 __kernel_vsyscall
  • #1 waitpid
    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 (793 sec old) ---------------------
Loading "installonlyn" plugin
(system-config-network-gui:4098): libglade-WARNING **: Error loading image: Failed to open file '/usr/share/system-config-network/netconfpkg/gui/network.xpm': No such file or directory
(system-config-network-gui:4098): libglade-WARNING **: could not convert string to type `GdkPixbuf' for property `logo'
(system-config-network-gui:4098): libglade-WARNING **: Error loading image: Failed to open file '/usr/share/system-config-network/netconfpkg/gui/network.xpm': No such file or directory
(system-config-network-gui:4098): libglade-WARNING **: could not convert string to type `GdkPixbuf' for property `logo'
(system-config-network-gui:4098): libglade-WARNING **: Error loading image: Failed to open file '/usr/share/system-config-network/netconfpkg/gui/network.xpm': No such file or directory
(system-config-network-gui:4098): libglade-WARNING **: could not convert string to type `GdkPixbuf' for property `logo'
warning: rpmts_HdrFromFdno: Header V3 DSA signature: NOKEY, key ID 4f2a6fd2
Importing GPG key 0x4F2A6FD2 "Fedora Project <fedora@redhat.com>" from /etc/pki/rpm-gpg/RPM-GPG-KEY-fedora
--------------------------------------------------
Comment 1 palfrey 2007-06-02 23:38:13 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.
Thanks in advance!
Comment 2 Pedro Villavicencio 2007-06-03 01:18:53 UTC
*** Bug 443379 has been marked as a duplicate of this bug. ***
Comment 3 Pedro Villavicencio 2007-06-04 23:56:37 UTC
*** Bug 444005 has been marked as a duplicate of this bug. ***
Comment 4 Pedro Villavicencio 2007-06-04 23:56:43 UTC
*** Bug 443994 has been marked as a duplicate of this bug. ***
Comment 5 Susana 2007-06-07 22:33:07 UTC
*** Bug 444988 has been marked as a duplicate of this bug. ***
Comment 6 Pedro Villavicencio 2007-06-17 23:21:04 UTC
*** Bug 447338 has been marked as a duplicate of this bug. ***
Comment 7 Pedro Villavicencio 2007-06-20 01:39:53 UTC
*** Bug 449189 has been marked as a duplicate of this bug. ***
Comment 8 Pedro Villavicencio 2007-06-23 21:02:28 UTC
*** Bug 450317 has been marked as a duplicate of this bug. ***
Comment 9 Iestyn Pryce 2007-08-02 17:17:46 UTC
*** Bug 462664 has been marked as a duplicate of this bug. ***
Comment 10 Iestyn Pryce 2007-08-02 21:37:53 UTC
*** Bug 462924 has been marked as a duplicate of this bug. ***
Comment 11 sysadmin 2007-08-02 21:56:43 UTC
I did 
yum install gnome-utils-debuginfo.i386 gnome-utils-devel.i386. It installed all the dependancies.

However, the log from the crash doesn't look to be that much different.

Thoughts?

Skeeter
Comment 12 sysadmin 2007-08-02 23:07:59 UTC
Installed Gnome Devel tools from GUI
Didn't help
installed
 glib2-debuginfo.i386 and gnome-vfs2-debuginfo.i386 from yum

couldn't find debuginfo for gtk2. gtk+ wasn't installed

That didn't add any info to the crash messages either.

Comment 13 Iestyn Pryce 2007-08-07 20:43:29 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 ***