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 421621 - logging out (as the root user)
logging out (as the root user)
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
: 452786 464476 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2007-03-22 20:20 UTC by dimagofman
Modified: 2007-08-07 20:41 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18



Description dimagofman 2007-03-22 20:20:20 UTC
Version: 2.18.0

What were you doing when the application crashed?
pressed log out	


Distribution: Fedora release 6.92 (Rawhide)
Gnome Release: 2.18.0 2007-03-20 (Red Hat, Inc)
BugBuddy Version: 2.18.0

System: Linux 2.6.20-1.3003.fc7 #1 SMP Wed Mar 21 18:57:31 EDT 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10299902
Selinux: Permissive
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Echo

Memory status: size: 86401024 vsize: 86401024 resident: 15331328 share: 8830976 rss: 15331328 rss_rlim: 4294967295
CPU usage: start_time: 1174594333 rtime: 419 utime: 379 stime: 40 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 -1208813328 (LWP 2781)]
(no debugging symbols found)
0x00f5f402 in __kernel_vsyscall ()

Thread 1 (Thread -1208813328 (LWP 2781))

  • #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 ---------------------
Repository extras-development is listed more than once in the configuration
Repository extras-development-source is listed more than once in the configuration
Repository updates-testing-debuginfo is listed more than once in the configuration
Repository updates-source is listed more than once in the configuration
Repository extras-development-debuginfo is listed more than once in the configuration
Repository updates-testing is listed more than once in the configuration
Repository extras is listed more than once in the configuration
Repository updates is listed more than once in the configuration
Repository updates-testing-source is listed more than once in the configuration
Repository legacy-testing is listed more than once in the configuration
Repository development-source is listed more than once in the configuration
Repository extras-debuginfo is listed more than once in the configuration
Repository core-debuginfo is listed more than once in the configuration
warning: .dynamic section for "/lib/libasound.so.2" is not at the expected address (wrong library or version mismatch?)
--------------------------------------------------
Comment 1 Susana 2007-03-22 22:45:22 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 Bruno Boaventura 2007-04-24 00:13:25 UTC
Closing this bug report as no further information has been provided. Please feel free to reopen this bug if you can provide the information asked for.
Thanks!
Comment 3 Christian Kirbach 2007-07-01 10:17:08 UTC
dups
Comment 4 Christian Kirbach 2007-07-01 10:17:31 UTC
*** Bug 452786 has been marked as a duplicate of this bug. ***
Comment 5 Christian Kirbach 2007-07-01 10:18: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 and reopen this bug or report a new one. Thanks in advance!
Comment 6 Iestyn Pryce 2007-08-07 20:39:11 UTC
*** Bug 464476 has been marked as a duplicate of this bug. ***
Comment 7 Iestyn Pryce 2007-08-07 20:41:47 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 ***

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