totem crashed with SIGSEGV in _xcb_conn_wait()

Bug #981779 reported by Fabio Marconi
12
This bug affects 1 person
Affects Status Importance Assigned to Milestone
totem (Ubuntu)
Expired
Medium
Unassigned

Bug Description

Hello
I was adjusting the audio level with the control in totem and it crash.
Thanks
Fabio
---
Ubuntu Bug Squad volunteer triager
http://wiki.ubuntu.com/BugSquad

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: totem 3.0.1-0ubuntu21
ProcVersionSignature: Ubuntu 3.2.0-23.36-generic 3.2.14
Uname: Linux 3.2.0-23-generic x86_64
ApportVersion: 2.0.1-0ubuntu3
Architecture: amd64
Date: Sat Apr 14 20:04:04 2012
ExecutablePath: /usr/bin/totem
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
ProcCmdline: totem /home/username/Scaricati/Th3\ 0rph4n4g3/CD1.avi
SegvAnalysis:
 Segfault happened at: 0x7f0b6ede17e9 <_xcb_conn_wait+9>: push %rbp
 PC (0x7f0b6ede17e9) ok
 source "%rbp" ok
 destination "(%rsp)" (0x7fff00178000) not located in a known VMA region (needed writable region)!
 Stack memory exhausted (SP below stack segment)
SegvReason: writing unknown VMA
Signal: 11
SourcePackage: totem
StacktraceTop:
 _xcb_conn_wait (c=0x7f0b77388c50, cond=0x7f0b77389d20, vector=0x7fff00178028, count=0x7fff00178024) at ../../src/xcb_conn.c:357
 _xcb_out_send (c=0x7f0b77388c50, vector=0x7fff001780a0, count=3) at ../../src/xcb_out.c:345
 xcb_writev (c=0x7f0b77388c50, vector=<optimized out>, count=<optimized out>, requests=2) at ../../src/xcb_out.c:293
 _XSend () from /usr/lib/x86_64-linux-gnu/libX11.so.6
 _XFlush () from /usr/lib/x86_64-linux-gnu/libX11.so.6
Title: totem crashed with SIGSEGV in _xcb_conn_wait()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm admin audio cdrom dialout lpadmin plugdev sambashare

Revision history for this message
Fabio Marconi (fabiomarconi) wrote :
visibility: private → public
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 _xcb_conn_wait (c=0x7f0b77388c50, cond=0x7f0b77389d20, vector=0x7fff00178028, count=0x7fff00178024) at ../../src/xcb_conn.c:357
 _xcb_out_send (c=0x7f0b77388c50, vector=0x7fff001780a0, count=3) at ../../src/xcb_out.c:345
 xcb_writev (c=0x7f0b77388c50, vector=<optimized out>, count=<optimized out>, requests=2) at ../../src/xcb_out.c:293
 _XSend (dpy=0x7f0b77387a00, data=<optimized out>, size=<optimized out>) at ../../src/xcb_io.c:494
 _XFlush (dpy=0x7f0b77387a00) at ../../src/xcb_io.c:511

Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
Changed in totem (Ubuntu):
importance: Undecided → Medium
tags: removed: need-amd64-retrace
Revision history for this message
Walter Garcia-Fontes (walter-garcia) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. We are sorry that we do not always have the capacity to look at all reported bugs in a timely manner. There have been many changes in Ubuntu since that time you reported the bug and your problem may have been fixed with some of the updates. It would help us a lot if you could test it on a currently supported Ubuntu version. When you test it and it is still an issue, kindly upload the updated logs by running apport-collect <bug #> and any other logs that are relevant for this particular issue.

Changed in totem (Ubuntu):
status: New → Incomplete
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for totem (Ubuntu) because there has been no activity for 60 days.]

Changed in totem (Ubuntu):
status: Incomplete → Expired
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.