41335

[fany]

Binary package hint: totem

symbol lookup error in libtotem-properties-page.so"
86265 MASTER firefox crash [@totemScriptablePlugin::~totemScriptablePlugin]
85976 [apport] totem-plugin-viewer crashed with SIGSEGV in _start()
85112 Firefox crashes after watching embedded video (undefined symbol: NS_CStringContainerInit)
80801 totem-gstreamer crash on idle machine
43589 [totem-gstreamer] wont play vcd for "unknown reason"
41335 DVD playing is not working correctly with totem-gstreamer
41099 [dapper][totem-xine] when I try to change connection speed it crashes
35229 totem-xine crash on logo (workaround inside)
21110 totem-xine mozilla plugin make firefox crash

ProblemType: Bug
Architecture: i386
Date: Thu Jul 26 08:28:06 2007
DistroRelease: Ubuntu 7.04
ExecutablePath: /usr/bin/totem
Package: totem-gstreamer 2.18.1-0ubuntu3
PackageArchitecture: i386
ProcCmdline: totem
ProcCwd: /home/fany
ProcEnviron:
 LANGUAGE=cs_CZ:cs:en_GB:en
 PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
 LANG=cs_CZ.UTF-8
 SHELL=/bin/bash
SourcePackage: totem
Uname: Linux fany-desktop 2.6.20-16-generic #2 SMP Thu Jun 7 20:19:32 UTC 2007 i686 GNU/Linux

[Kees Cook (kees)]

Thanks for taking the time to report this bug and helping to make Ubuntu better. I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find.

[Sebastien Bacher (seb128)]

Thanks for taking the time to report this bug. Unfortunately we can't fix it, because your description didn't include enough information. You may find it helpful to read "How to report bugs effectively" <http://www.chiark.greenend.org.uk/~sgtatham/bugs.html>. We'd be grateful if you would then provide a more complete description of the problem.

 We have instructions on debugging some types of problems. <http://wiki.ubuntu.com/DebuggingProcedures> Thanks!

[Pedro Villavicencio (pedro)]

We are closing this bug report as it lacks the information, described in the previous comments, we need to investigate the problem further. However, please reopen it if you can give us the missing information and don't hesitate to submit bug reports in the future.