Xephyr crashed with SIGSEGV in free()

Bug #130769 reported by Sergio K. Hernandez
8
Affects Status Importance Assigned to Milestone
xorg-server (Ubuntu)
Invalid
Medium
Unassigned

Bug Description

Kubuntu Gutsy Tribe
I was runnig KDE4 and the crash occurs.
Apparently no particular reason makes the crash.

ProblemType: Crash
Architecture: i386
Date: Mon Aug 6 17:31:52 2007
DistroRelease: Ubuntu 7.10
ExecutablePath: /usr/bin/Xephyr
NonfreeKernelModules: cdrom
Package: xserver-xephyr 2:1.3.0.0.dfsg-6ubuntu3
PackageArchitecture: i386
ProcCmdline: Xephyr :1
ProcCwd: /home/oscar
ProcEnviron:
 SHELL=/bin/bash
 PATH=/usr/lib/kde4/bin/:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
 LANG=es_MX.UTF-8
 LANGUAGE=es_MX:es
Signal: 11
SourcePackage: xorg-server
StacktraceTop:
 ?? ()
 ?? ()
 free () from /lib/tls/i686/cmov/libc.so.6
 ?? ()
 ?? ()
Title: Xephyr crashed with SIGSEGV in free()
Uname: Linux prueba 2.6.22-9-generic #1 SMP Fri Aug 3 00:50:37 GMT 2007 i686 GNU/Linux
UserGroups: adm admin audio cdrom dialout dip floppy lpadmin netdev plugdev powerdev scanner video

Revision history for this message
Sergio K. Hernandez (info-geex) wrote :
Revision history for this message
Apport retracing service (apport) wrote : Symbolic stack trace

StacktraceTop:?? ()
?? ()
����D () from /lib/tls/i686/cmov/libc.so.6
?? ()
?? ()

Revision history for this message
Apport retracing service (apport) wrote : Symbolic threaded stack trace
Revision history for this message
Apport retracing service (apport) wrote : Stack trace with source code
Changed in xorg-server:
importance: Undecided → Medium
Revision history for this message
Bryce Harrington (bryce) wrote :

Unfortunately the automatically collected info did not include a usable backtrace. Please install the debug symbol package for xserver.

Also, can you please provide the following data?

1. Detailed steps to recreate the crash
2. /var/log/Xorg.0.log from after the crash
3. output of lspci -vvnn
4. /etc/X11/xorg.conf

Changed in xorg-server:
status: New → Incomplete
Revision history for this message
wolfger (wolfger) wrote :

Over 3 months with no response. We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!

Changed in xorg-server:
status: Incomplete → Invalid
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.