totem crashed with SIGSEGV

Bug #1062244 reported by lostprophet
14
This bug affects 2 people
Affects Status Importance Assigned to Milestone
totem (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

totem crashes as soon as is i want to start it...

Fontconfig warning: "/etc/fonts/conf.d/65-culmus.conf", line 12: Having multiple values in <test> isn't supported and may not works as expected
Fontconfig warning: "/etc/fonts/conf.d/65-culmus.conf", line 34: Having multiple values in <test> isn't supported and may not works as expected
Fontconfig warning: "/etc/fonts/conf.d/65-culmus.conf", line 44: Having multiple values in <test> isn't supported and may not works as expected
Fontconfig warning: "/etc/fonts/conf.d/65-culmus.conf", line 55: Having multiple values in <test> isn't supported and may not works as expected
Fontconfig warning: "/etc/fonts/conf.d/65-culmus.conf", line 66: Having multiple values in <test> isn't supported and may not works as expected
Fontconfig warning: "/etc/fonts/conf.d/65-culmus.conf", line 77: Having multiple values in <test> isn't supported and may not works as expected
Fontconfig warning: "/etc/fonts/conf.d/65-culmus.conf", line 89: Having multiple values in <test> isn't supported and may not works as expected
Fontconfig warning: "/etc/fonts/conf.d/65-culmus.conf", line 101: Having multiple values in <test> isn't supported and may not works as expected
Fontconfig warning: "/etc/fonts/conf.d/65-culmus.conf", line 111: Having multiple values in <test> isn't supported and may not works as expected
NVIDIA: API mismatch: the NVIDIA kernel module has version 304.43,
but this NVIDIA driver component has version 304.51. Please make
sure that the kernel module and all NVIDIA driver components
have the same version.
NVIDIA: API mismatch: the NVIDIA kernel module has version 304.43,
but this NVIDIA driver component has version 304.51. Please make
sure that the kernel module and all NVIDIA driver components
have the same version.
Speicherzugriffsfehler (Speicherabzug geschrieben)

ProblemType: Crash
DistroRelease: Ubuntu 12.10
Package: totem 3.4.3-0ubuntu4
ProcVersionSignature: Ubuntu 3.5.0-16.25-generic 3.5.4
Uname: Linux 3.5.0-16-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.6.1-0ubuntu1
Architecture: amd64
CrashCounter: 1
Date: Fri Oct 5 14:27:34 2012
Disassembly: => 0x0: Cannot access memory at address 0x0
ExecutablePath: /usr/bin/totem
ProcCmdline: totem /home/username/Videos/Serien/The\ Big\ Bang\ Theory/Season\ 6/BBT.602.avi
SegvAnalysis:
 Segfault happened at: 0x0: Cannot access memory at address 0x0
 PC (0x00000000) not located in a known VMA region (needed executable region)!
SegvReason: executing NULL VMA
Signal: 11
SourcePackage: totem
StacktraceTop:
 ?? ()
 ?? ()
 ?? ()
 ?? ()
 ?? ()
Title: totem crashed with SIGSEGV
UpgradeStatus: Upgraded to quantal on 2012-09-21 (13 days ago)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare vboxusers

Revision history for this message
lostprophet (matze-spam1) wrote :
visibility: private → public
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 ?? ()
 ?? ()
 ?? ()
 ?? ()
 ?? ()

Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Revision history for this message
Apport retracing service (apport) wrote : StacktraceSource.txt
Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
Changed in totem (Ubuntu):
status: New → Invalid
Revision history for this message
Apport retracing service (apport) wrote : Crash report cannot be processed

Thank you for your report!

However, processing it in order to get sufficient information for the
developers failed (it does not generate a useful symbolic stack trace). This
might be caused by some outdated packages which were installed on your system
at the time of the report:

outdated debug symbol package for libcdparanoia0: package version 3.10.2+debian-11 dbgsym version 3.10.2+debian-10ubuntu1
libxcomposite1 version 1:0.4.3-2build1 required, but 1:0.4.3-2build2 is available
libudev0 version 175-0ubuntu11 required, but 175-0ubuntu12 is available
outdated debug symbol package for libjack-jackd2-0: package version 1.9.8~dfsg.4+20120529git007cdc37-2ubuntu1 dbgsym version 1.9.8~dfsg.1-1ubuntu1
libltdl7 version 2.4.2-1ubuntu1 required, but 2.4.2-1ubuntu2 is available
outdated debug symbol package for libtxc-dxtn-s2tc0: package version 0~git20110809-3 dbgsym version 0~git20110809-2.1
libxfixes3 version 1:5.0-4ubuntu4 required, but 1:5.0-4ubuntu5 is available
libxklavier16 version 5.2.1-1ubuntu1 required, but 5.2.1-1ubuntu2 is available
libxdamage1 version 1:1.1.3-2build1 required, but 1:1.1.3-2build2 is available
outdated debug symbol package for libecryptfs0: package version 100-0ubuntu1 dbgsym version 96-0ubuntu3
outdated debug symbol package for libstdc++6: package version 4.7.2-2ubuntu1 dbgsym version 4.6.3-1ubuntu5
udev version 175-0ubuntu11 required, but 175-0ubuntu12 is available
outdated debug symbol package for initscripts: package version 2.88dsf-13.10ubuntu13 dbgsym version 2.88dsf-13.10ubuntu11.1
outdated debug symbol package for usbutils: package version 1:005-3 dbgsym version 1:005-1
libgudev-1.0-0 version 1:175-0ubuntu11 required, but 1:175-0ubuntu12 is available
libvisual-0.4-plugins version 0.4.0.dfsg.1-7 required, but 0.4.0.dfsg.1-7build1 is available
outdated debug symbol package for gvfs-libs: package version 1.14.0-0ubuntu4 dbgsym version 1.14.0-0ubuntu3

Please upgrade your system to the latest package versions. If you still
encounter the crash, please file a new report.

Thank you for your understanding, and sorry for the inconvenience!

tags: removed: need-amd64-retrace
Revision history for this message
CBrider (zaknafien13) wrote :

I had the same problem. I ended up doing

sudo apt-get install --reinstall nvidia-current

and

sudo dpkg-reconfigure nvidia-current

Totem still did not work immediately. After a reboot, it was working again. I am not sure if both are required.

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.