[apport] gnome-panel crashed with SIGSEGV in _IO_default_xsputn()

Bug #91275 reported by Quim Calpe
2
Affects Status Importance Assigned to Milestone
gnome-panel (Ubuntu)
Invalid
Medium
Ubuntu Desktop Bugs

Bug Description

Binary package hint: gnome-panel

Desktop effects enabled, just logged in when crashed, feisty up-to-date

ProblemType: Crash
Architecture: i386
Date: Sun Mar 11 02:50:36 2007
DistroRelease: Ubuntu 7.04
ExecutablePath: /usr/bin/gnome-panel
Package: gnome-panel 2.17.92-0ubuntu4
PackageArchitecture: i386
ProcCmdline: gnome-panel --sm-client-id default1
ProcCwd: /home/quim
ProcEnviron:
 PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/bin/X11:/usr/games
 SHELL=/bin/bash
Signal: 11
SourcePackage: gnome-panel
StacktraceTop:
 ?? () from /lib/tls/i686/cmov/libc.so.6
 ?? () from /usr/lib/libgobject-2.0.so.0
 _IO_default_xsputn () from /lib/tls/i686/cmov/libc.so.6
 malloc () from /lib/tls/i686/cmov/libc.so.6
 _gdk_xsettings_setting_copy ()
Uname: Linux ubuntu 2.6.20-9-generic #2 SMP Mon Feb 26 03:01:44 UTC 2007 i686 GNU/Linux
UserGroups: adm audio cdrom dialout dip fax floppy gdm plugdev root scanner tape

Revision history for this message
Quim Calpe (quimcalpe) wrote :
Revision history for this message
Sebastien Bacher (seb128) wrote :

Thanks for your bug report. The crash looks like a memory corruption. Could you try to get a valgrind log for it? (you can follow the instructions from https://wiki.ubuntu.com/Valgrind for that)

Changed in gnome-panel:
assignee: nobody → desktop-bugs
importance: Undecided → Medium
status: Unconfirmed → Needs Info
Revision history for this message
Quim Calpe (quimcalpe) wrote :

Couldn't reproduce the bug this morning... I still attach the valgrind log in case you find it useful

Thanks

Revision history for this message
Sebastien Bacher (seb128) wrote :

The log has no error. Closign the bug for now, could you reopen if you can get a log when it's crashing?

Changed in gnome-panel:
status: Needs Info → Rejected
Revision history for this message
Quim Calpe (quimcalpe) wrote :

No problem

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.