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 406214 - crash in About Me: open gnome-about-me
crash in About Me: open gnome-about-me
Status: RESOLVED INCOMPLETE
Product: gnome-control-center
Classification: Core
Component: [obsolete] about-me
2.16.x
Other All
: High critical
: ---
Assigned To: Control-Center Maintainers
Control-Center Maintainers
: 406401 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2007-02-09 21:26 UTC by dondc
Modified: 2007-06-06 00:21 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16



Description dondc 2007-02-09 21:26:45 UTC
Version: 2.16.3

What were you doing when the application crashed?
open gnome-about-me


Distribution: Unknown
Gnome Release: 2.16.3 2007-02-05 (FreeBSD GNOME Project)
BugBuddy Version: 2.16.1

System: FreeBSD 6.2-RELEASE FreeBSD 6.2-RELEASE #6: Sun Jan 28 21:54:29 CET 2007     dondc@dual.virTual.lan:/usr/src/sys/i386/compile/DUALKERN i386
X Vendor: The X.Org Foundation
X Vendor Release: 60899903
Selinux: No
Accessibility: Disabled

Memory status: size: 3170304 vsize: 0 resident: 3170304 share: 0 rss: 21786624 rss_rlim: 0
CPU usage: start_time: -885241742 rtime: 272657 utime: 1424691 stime: 0 cutime:1424691 cstime: 0 timeout: 253117 it_real_value: 0 frequency: 0

Backtrace was generated from '/usr/local/bin/gnome-about-me'

(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...[New Thread 0x8312400 (runnable)]
[New Thread 0x829da00 (runnable)]
[New Thread 0x829d800 (runnable)]
[New Thread 0x829d600 (LWP 100182)]
[New Thread 0x805d000 (runnable)]
[New LWP 100201]
(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...[Switching to LWP 100201]
0x293234f7 in pthread_testcancel () from /lib/libpthread.so.2

Thread 6 (LWP 100201)

  • #0 pthread_testcancel
    from /lib/libpthread.so.2
  • #1 pthread_mutexattr_init
    from /lib/libpthread.so.2
  • #2 ??


----------- .xsession-errors ---------------------
(gnome-about-me:3940): -properties-WARNING **: e_book_get_self: Es gab keine in GConf gespeicherte Self-Contact-Benutzerkennung
/home/dondc/.gtkrc-2.0:2: Include-Datei konnte nicht gefunden werden: ».gtkrc-2.0-scrollbar_cog«
** (bug-buddy:3946): WARNING **: Failed to connect to the FAM server: (null)
** (bug-buddy:3946): WARNING **: Symbol für Bonobo-Komponenten-Browser konnte nicht geladen werden
** (bug-buddy:3946): WARNING **: Symbol für Menüeditor konnte nicht geladen werden
** (bug-buddy:3946): WARNING **: Symbol für Ordner öffnen konnte nicht geladen werden
warning: Unable to get location for thread creation breakpoint: generic error
/usr/local/share/gnome/bug-buddy/gdb-cmd:2: Error in sourced command file:
Previous frame inner to this frame (corrupt stack?)
--------------------------------------------------
Comment 1 Thomas Wood 2007-02-10 00:23:45 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. 
Comment 2 dondc 2007-02-10 13:06:15 UTC
chrash of, open gnome-about-me and chance passwd, is this bug.
Comment 3 Jens Granseuer 2007-02-10 13:29:44 UTC
Sorry, but we need a stacktrace with debugging symbols to be able to do anything about this problem. Please follow the instructions given in comment #1 to obtain one and attach it to this bug.

German:
Wir benötigen einen Trace mit Debugging-Symbolen, um das Problem beheben zu können. Wie man dies macht, ist unter dem Link in comment #1 oder http://live.gnome.org/GettingTraces/DistroSpecificInstructions beschrieben.
Danke.
Comment 4 dondc 2007-02-10 14:32:06 UTC
in processing, recompile my system!

thx,
danny
Comment 5 Jens Granseuer 2007-02-10 14:52:34 UTC
*** Bug 406401 has been marked as a duplicate of this bug. ***
Comment 6 Jens Granseuer 2007-02-10 14:56:02 UTC
Please only reopen bugs if you have actually provided the info asked for. Thanks.

The new trace in bug 406401 has a bit more info than the old one, but still no debugging info. Which packages did you recompile with debugging symbols? You'll need at least control-center, glib, and gtk+.
Comment 7 Diego Escalante Urrelo (not reading bugmail) 2007-06-06 00:21:26 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!

(Since bugzilla policy for bad_stacktrace is now to mark as INCOMPLETE. Mass
changing all of these. Search for "dieguito-doing-incomplete-spam" to delete
all this from your inbox.)