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 368901 - crash in About Me: I don't know :D I didn't...
crash in About Me: I don't know :D I didn't...
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
: 371415 374530 376463 380214 386198 388130 388147 394110 397511 398820 402297 402837 404062 404424 404746 405782 408831 411245 411630 412059 418559 419886 420768 421229 423044 423213 432773 432997 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2006-11-01 15:24 UTC by cimarosti
Modified: 2007-11-08 01:47 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16


Attachments
Backtrace generated from '/usr/bin/gnome-about-me' crash (6.72 KB, text/plain)
2007-02-05 21:00 UTC, maurizio
Details

Description cimarosti 2006-11-01 15:24:21 UTC
Version: 2.16.1

What were you doing when the application crashed?
I don't know :D I didn't realise anything crashing


Distribution: Ubuntu 6.10 (edgy)
Gnome Release: 2.16.1 2006-10-02 (Ubuntu)
BugBuddy Version: 2.16.0

Memory status: size: 60256256 vsize: 0 resident: 60256256 share: 0 rss: 14856192 rss_rlim: 0
CPU usage: start_time: 1162394114 rtime: 0 utime: 148 stime: 0 cutime:84 cstime: 0 timeout: 64 it_real_value: 0 frequency: 0

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

(no debugging symbols found)
Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1229108528 (LWP 13668)]
[New Thread -1256678496 (LWP 13676)]
[New Thread -1256326240 (LWP 13671)]
[New Thread -1247933536 (LWP 13669)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

Thread 1 (Thread -1229108528 (LWP 13668))

  • #0 __kernel_vsyscall
  • #1 __waitpid_nocancel
    from /lib/tls/i686/cmov/libpthread.so.0
  • #2 gnome_gtk_module_info_get
    from /usr/lib/libgnomeui-2.so.0
  • #3 <signal handler called>
  • #4 g_io_channel_shutdown
    from /usr/lib/libglib-2.0.so.0
  • #5 eel_alert_dialog_new
  • #6 g_source_is_destroyed
    from /usr/lib/libglib-2.0.so.0
  • #7 g_main_context_dispatch
    from /usr/lib/libglib-2.0.so.0
  • #8 g_main_context_check
    from /usr/lib/libglib-2.0.so.0
  • #9 g_main_loop_run
    from /usr/lib/libglib-2.0.so.0
  • #10 gtk_main
    from /usr/lib/libgtk-x11-2.0.so.0
  • #11 main
  • #0 __kernel_vsyscall

Comment 1 André Klapper 2006-11-06 10:15:57 UTC
*** Bug 371415 has been marked as a duplicate of this bug. ***
Comment 2 André Klapper 2006-11-06 10:16:11 UTC
confirming as per duplicate
Comment 3 Damien Durand 2006-11-13 04:22:48 UTC
*** Bug 374530 has been marked as a duplicate of this bug. ***
Comment 4 André Klapper 2006-11-17 23:10:00 UTC
*** Bug 376463 has been marked as a duplicate of this bug. ***
Comment 5 Susana 2006-11-28 20:12:48 UTC
*** Bug 380214 has been marked as a duplicate of this bug. ***
Comment 6 Bruno Boaventura 2006-12-15 15:49:39 UTC
*** Bug 386198 has been marked as a duplicate of this bug. ***
Comment 7 Sebastien Bacher 2006-12-17 22:59:18 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 8 Sebastien Bacher 2006-12-21 13:52:50 UTC
*** Bug 388147 has been marked as a duplicate of this bug. ***
Comment 9 Susana 2006-12-21 14:08:57 UTC
*** Bug 388130 has been marked as a duplicate of this bug. ***
Comment 10 Gabor Kelemen 2007-01-08 12:54:13 UTC
*** Bug 394110 has been marked as a duplicate of this bug. ***
Comment 11 Susana 2007-01-17 13:31:39 UTC
*** Bug 397511 has been marked as a duplicate of this bug. ***
Comment 12 palfrey 2007-01-20 21:44:41 UTC
*** Bug 398820 has been marked as a duplicate of this bug. ***
Comment 13 Bruno Boaventura 2007-01-30 00:44:37 UTC
*** Bug 402297 has been marked as a duplicate of this bug. ***
Comment 14 Bruno Boaventura 2007-01-31 14:56:06 UTC
*** Bug 402837 has been marked as a duplicate of this bug. ***
Comment 15 Jens Granseuer 2007-02-04 10:26:23 UTC
*** Bug 404062 has been marked as a duplicate of this bug. ***
Comment 16 Jens Granseuer 2007-02-04 21:55:26 UTC
*** Bug 404424 has been marked as a duplicate of this bug. ***
Comment 17 maurizio 2007-02-05 21:00:48 UTC
Created attachment 81955 [details]
Backtrace generated from '/usr/bin/gnome-about-me' crash
Comment 18 maurizio 2007-02-05 21:03:44 UTC
I reproduced the crash
I have clicked on change password button, 
then I have inserted my current password in its field,
Then I have clicked on "Authenticate" button and it has replied to me whit
"Authenticated" 
then I have not inserted any new password (like if I had changed my idea) and I
have clicked on close button.
The program crashed!
I have uploaded a backtrace with debugging symbols
Comment 19 Jens Granseuer 2007-02-05 21:09:29 UTC
*** Bug 404746 has been marked as a duplicate of this bug. ***
Comment 20 dvdmerwe 2007-02-06 19:18:06 UTC
I was also busy with a password change and left the "new password" field blank. Crashed after I submitted.
Comment 21 Jens Granseuer 2007-02-08 16:55:44 UTC
*** Bug 405782 has been marked as a duplicate of this bug. ***
Comment 22 Susana 2007-02-17 13:20:14 UTC
*** Bug 408831 has been marked as a duplicate of this bug. ***
Comment 23 palfrey 2007-02-23 16:10:36 UTC
*** Bug 411245 has been marked as a duplicate of this bug. ***
Comment 24 Bruno Boaventura 2007-02-24 17:54:13 UTC
*** Bug 411630 has been marked as a duplicate of this bug. ***
Comment 25 Susana 2007-02-26 15:55:11 UTC
*** Bug 412059 has been marked as a duplicate of this bug. ***
Comment 26 Jens Granseuer 2007-03-15 21:47:33 UTC
*** Bug 418559 has been marked as a duplicate of this bug. ***
Comment 27 Jens Granseuer 2007-03-19 17:22:19 UTC
*** Bug 419886 has been marked as a duplicate of this bug. ***
Comment 28 Jens Granseuer 2007-03-20 22:54:55 UTC
*** Bug 420768 has been marked as a duplicate of this bug. ***
Comment 29 Jens Granseuer 2007-03-21 21:26:25 UTC
*** Bug 421229 has been marked as a duplicate of this bug. ***
Comment 30 Jens Granseuer 2007-03-26 19:39:24 UTC
*** Bug 423044 has been marked as a duplicate of this bug. ***
Comment 31 Jens Granseuer 2007-03-27 19:27:13 UTC
*** Bug 423213 has been marked as a duplicate of this bug. ***
Comment 32 Pedro Villavicencio 2007-04-24 02:38:49 UTC
*** Bug 432773 has been marked as a duplicate of this bug. ***
Comment 33 Pedro Villavicencio 2007-04-25 02:57:04 UTC
*** Bug 432997 has been marked as a duplicate of this bug. ***
Comment 34 André Klapper 2007-11-08 01:47:17 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!