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 391772 - crash in About Me: Changed name in "About M...
crash in About Me: Changed name in "About M...
Status: RESOLVED DUPLICATE of bug 364839
Product: gnome-control-center
Classification: Core
Component: [obsolete] about-me
2.17.x
Other All
: High critical
: ---
Assigned To: Control-Center Maintainers
Control-Center Maintainers
Depends on:
Blocks:
 
 
Reported: 2007-01-02 06:14 UTC by Adam Wagner
Modified: 2007-01-02 12:49 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18



Description Adam Wagner 2007-01-02 06:14:40 UTC
Version: 2.17.3

What were you doing when the application crashed?
Changed name in "About Me" preferenced application, and clicked close


Distribution: Fedora Core release 6 (Rawhide)
Gnome Release: 2.17.2 2006-11-07 (Red Hat, Inc)
BugBuddy Version: 2.17.3

System: Linux 2.6.18-1.2868.fc6 #1 SMP Fri Dec 15 17:32:54 EST 2006 i686
X Vendor: The X.Org Foundation
X Vendor Release: 70101000
Selinux: Permissive
Accessibility: Enabled

Memory status: size: 58105856 vsize: 0 resident: 58105856 share: 0 rss: 15298560 rss_rlim: 0
CPU usage: start_time: 1167718351 rtime: 0 utime: 100 stime: 0 cutime:88 cstime: 0 timeout: 12 it_real_value: 0 frequency: 18

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

(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 -1208957232 (LWP 7044)]
[New Thread -1237075056 (LWP 7051)]
[New Thread -1226585200 (LWP 7045)]
(no debugging symbols found)
0x0054c402 in __kernel_vsyscall ()

Thread 1 (Thread -1208957232 (LWP 7044))

  • #0 __kernel_vsyscall
  • #1 waitpid
    from /lib/libpthread.so.0
  • #2 libgnomeui_module_info_get
    from /usr/lib/libgnomeui-2.so.0
  • #3 <signal handler called>
  • #4 strlen
    from /lib/libc.so.6
  • #5 giop_send_buffer_append_string
    from /usr/lib/libORBit-2.so.0
  • #6 ORBit_marshal_value
    from /usr/lib/libORBit-2.so.0
  • #7 ORBit_marshal_value
    from /usr/lib/libORBit-2.so.0
  • #8 ORBit_marshal_any
    from /usr/lib/libORBit-2.so.0
  • #9 ORBit_marshal_value
    from /usr/lib/libORBit-2.so.0
  • #10 ORBit_marshal_value
    from /usr/lib/libORBit-2.so.0
  • #11 ORBit_small_allocbuf
    from /usr/lib/libORBit-2.so.0
  • #12 ORBit_small_invoke_stub
    from /usr/lib/libORBit-2.so.0
  • #13 ORBit_small_invoke_stub_n
    from /usr/lib/libORBit-2.so.0
  • #14 ORBit_c_stub_invoke
    from /usr/lib/libORBit-2.so.0
  • #15 Accessibility_EventListener_notifyEvent
    from /usr/lib/libspi.so.0
  • #16 ??
    from /usr/lib/gtk-2.0/modules/libatk-bridge.so
  • #17 ??
    from /usr/lib/gtk-2.0/modules/libatk-bridge.so
  • #18 exit
    from /lib/libc.so.6
  • #19 __libc_start_main
    from /lib/libc.so.6
  • #20 _start
  • #0 __kernel_vsyscall


----------- .xsession-errors (16454 sec old) ---------------------
compiz: Couldn't bind redirected window 0x620c8e7 to texture
compiz: pixmap 0x18004ff can't be bound to texture
compiz: Couldn't bind redirected window 0x620c8e7 to texture
compiz: pixmap 0x18004ff can't be bound to texture
compiz: Couldn't bind redirected window 0x620c8e7 to texture
compiz: pixmap 0x18004ff can't be bound to texture
compiz: Couldn't bind redirected window 0x620c8e7 to texture
compiz: pixmap 0x18004ff can't be bound to texture
compiz: Couldn't bind redirected window 0x620c8e7 to texture
compiz: pixmap 0x18004ff can't be bound to texture
compiz: Couldn't bind redirected window 0x620c8e7 to texture
compiz: pixmap 0x18004ff can't be bound to texture
compiz: Couldn't bind redirected window 0x620c8e7 to texture
...Too much output, ignoring rest...
--------------------------------------------------
Comment 1 Susana 2007-01-02 12:49:38 UTC
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.


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