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 307458 - Gnome Control Center Crash
Gnome Control Center Crash
Status: VERIFIED INCOMPLETE
Product: gnome-control-center
Classification: Core
Component: general
unspecified
Other other
: Normal normal
: ---
Assigned To: GDM maintainers
GDM maintainers
Depends on:
Blocks:
 
 
Reported: 2005-06-13 05:01 UTC by Joe Bratton
Modified: 2009-08-15 18:40 UTC
See Also:
GNOME target: ---
GNOME version: 2.9/2.10



Description Joe Bratton 2005-06-13 05:01:18 UTC
Distribution: Debian 3.1
Package: gdm
Severity: normal
Version: GNOME2.10.1 unspecified
Gnome-Distributor: Debian
Synopsis: Gnome Control Center Crash
Bugzilla-Product: gdm
Bugzilla-Component: general
Bugzilla-Version: unspecified
BugBuddy-GnomeVersion: 2.0 (2.8.1)
Description:
Description of the crash:
Attempted to start app and immediatley got error message	

Steps to reproduce the crash:
1. simply attempt to start the GCC
2. 
3. 

Expected Results:
GCC would load

How often does this happen?
every time I try to load

Additional Information:
probably some issue in my setup but I thought I'd pass it along


Debugging Information:

Backtrace was generated from '/usr/bin/gnome-control-center'

(no debugging symbols found)
Using host libthread_db library "/lib/tls/libthread_db.so.1".
(no debugging symbols found)
`system-supplied DSO at 0xffffe000' has disappeared; keeping its
symbols.
(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)
[Thread debugging using libthread_db enabled]
[New Thread -1215331680 (LWP 8685)]
(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)
0x4117e53e in __waitpid_nocancel () from /lib/tls/libpthread.so.0

Thread 1 (Thread -1215331680 (LWP 8685))

  • #0 __waitpid_nocancel
    from /lib/tls/libpthread.so.0
  • #1 libgnomeui_module_info_get
    from /usr/lib/libgnomeui-2.so.0
  • #2 <signal handler called>
  • #3 gnome_vfs_uri_to_string
    from /usr/lib/libgnomevfs-2.so.0
  • #4 capplet_dir_new
  • #5 get_root_capplet_dir
  • #6 main
  • #0 __waitpid_nocancel
    from /lib/tls/libpthread.so.0




------- Bug moved to this database by unknown@bugzilla.gnome.org 2005-06-13 05:01 UTC -------

Comment 1 Christian Kirbach 2005-06-13 08:47:39 UTC
unique stack trace.
Comment 2 Vincent Noel 2005-06-21 18:22:10 UTC
*** Bug 307931 has been marked as a duplicate of this bug. ***
Comment 3 Sebastien Bacher 2005-07-07 20:51:57 UTC
Thanks for the bug report. Unfortunately, that stack trace is not very useful in
determining the cause of the crash. Can you get us one with debugging symbols?
Please see http://live.gnome.org/GettingTraces for more information on how to do so.
Comment 4 Christian Kirbach 2005-09-12 09:28:34 UTC
No response from anyone. Marking INCOMPLETE.

Feel free to reopen and add more comments.
Comment 5 Joe Bratton 2005-09-12 12:20:12 UTC
I believe this, along with many other problems I was having, was due to a memory
corruption issue.  I had a 512mb simm in a 256mb slot and since removing it all
crashes and file system corruption have gone away.

Sorry for wasted time on the issue.