After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 167083 - Totem crash on close (segfault) and doesn't play video and graphic effects
Totem crash on close (segfault) and doesn't play video and graphic effects
Status: RESOLVED INCOMPLETE
Product: totem
Classification: Core
Component: general
unspecified
Other All
: Normal minor
: ---
Assigned To: General Totem maintainer(s)
General Totem maintainer(s)
Depends on:
Blocks:
 
 
Reported: 2005-02-11 15:45 UTC by Riccardo
Modified: 2005-05-22 16:32 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Riccardo 2005-02-11 15:45:32 UTC
Please describe the problem:
Totem start up correctly, but it doesn't play video and graphic effects.
When closing it, a Segmentation fault box appears.

Steps to reproduce:
1. I open Totem
2. I open a audio file
3. Totem reproduces it but doesn't show graphic effects
3b. If I open a video file, Totem reproduces just audio
4. When I close Totem a Segmentation fault box appears.

Actual results:
Totem doesn't show video file and graphic effects.
A Segmentation fault box appears.

Expected results:
Totem'd close correctly and play video file and graphic effects.

Does this happen every time?
Yes, it does.

Other information:
This is the tracing of segfault with gdb.

(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...[Thread debugging using libthread_db enabled]
[New Thread 1089003232 (LWP 5756)]
[New Thread 1105890224 (LWP 5760)]
[New Thread 1114319792 (LWP 5761)]
[New Thread 1122982832 (LWP 5762)]
[New Thread 1135623088 (LWP 5764)]
[New Thread 1148115888 (LWP 5765)]
[New Thread 1158396848 (LWP 5766)]
[New Thread 1166789552 (LWP 5770)]

Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 1089003232 (LWP 5756)]
0x40d5944b in strlen () from /lib/tls/libc.so.6
(gdb)
Comment 1 Bastien Nocera 2005-02-17 22:04:46 UTC
Which version of Totem are you using? Which backend is used (see the about box)?
Comment 2 Riccardo 2005-02-18 14:02:09 UTC
The Totem's version is 0.99.9, but it happens with other version, too. 
The backend is xine-lib. 
Comment 3 Bastien Nocera 2005-02-18 14:27:54 UTC
Could you gather a decent backtrace of the crash (type "bt" and "threads apply
all bt" in gdb)? Otherwise, there's no way of knowing where this strlen was
called from.
Comment 4 Riccardo 2005-02-18 14:59:34 UTC
This is the report of "bt" like user: 
 
Starting program: /usr/bin/totem 
(no debugging symbols found)...(no debugging symbols found)... 
(no debugging symbols found)...(no debugging symbols found)... 
(no debugging symbols found)...(no debugging symbols found)... 
(no debugging symbols found)...(no debugging symbols found)... 
(no debugging symbols found)...(no debugging symbols found)... 
(no debugging symbols found)...(no debugging symbols found)... 
(no debugging symbols found)...(no debugging symbols found)... 
(no debugging symbols found)...(no debugging symbols found)... 
(no debugging symbols found)...(no debugging symbols found)... 
(no debugging symbols found)...(no debugging symbols found)... 
(no debugging symbols found)...(no debugging symbols found)... 
(no debugging symbols found)...(no debugging symbols found)... 
(no debugging symbols found)...(no debugging symbols found)... 
(no debugging symbols found)...[Thread debugging using libthread_db enabled] 
[New Thread 1089003232 (LWP 5040)] 
[New Thread 1105828784 (LWP 5043)] 
[New Thread 1114258352 (LWP 5044)] 
[New Thread 1122921392 (LWP 5045)] 
[New Thread 1135561648 (LWP 5046)] 
[New Thread 1148054448 (LWP 5047)] 
[New Thread 1158335408 (LWP 5048)] 
[New Thread 1166728112 (LWP 5052)] 
bt 
 
And this is like root: 
 
(no debugging symbols found)...(no debugging symbols found)... 
(no debugging symbols found)...(no debugging symbols found)... 
(no debugging symbols found)...(no debugging symbols found)... 
(no debugging symbols found)...(no debugging symbols found)... 
(no debugging symbols found)...(no debugging symbols found)... 
(no debugging symbols found)...(no debugging symbols found)... 
(no debugging symbols found)...(no debugging symbols found)... 
(no debugging symbols found)...(no debugging symbols found)... 
(no debugging symbols found)...(no debugging symbols found)... 
(no debugging symbols found)...(no debugging symbols found)... 
(no debugging symbols found)...(no debugging symbols found)... 
(no debugging symbols found)...(no debugging symbols found)... 
(no debugging symbols found)...(no debugging symbols found)... 
(no debugging symbols found)...[Thread debugging using libthread_db enabled] 
[New Thread 1089003232 (LWP 5124)] 
Detaching after fork from child process 5127. 
[New Thread 1105898416 (LWP 5129)] 
[New Thread 1114327984 (LWP 5130)] 
[New Thread 1122991024 (LWP 5131)] 
[New Thread 1135631280 (LWP 5132)] 
[New Thread 1148124080 (LWP 5133)] 
[New Thread 1158405040 (LWP 5134)] 
[New Thread 1166797744 (LWP 5138)] 
bt 
 
This is the report of "threads apply all bt" like user: 
 
Starting program: /usr/bin/totem 
(no debugging symbols found)...(no debugging symbols found)... 
(no debugging symbols found)...(no debugging symbols found)... 
(no debugging symbols found)...(no debugging symbols found)... 
(no debugging symbols found)...(no debugging symbols found)... 
(no debugging symbols found)...(no debugging symbols found)... 
(no debugging symbols found)...(no debugging symbols found)... 
(no debugging symbols found)...(no debugging symbols found)... 
(no debugging symbols found)...(no debugging symbols found)... 
(no debugging symbols found)...(no debugging symbols found)... 
(no debugging symbols found)...(no debugging symbols found)... 
(no debugging symbols found)...(no debugging symbols found)... 
(no debugging symbols found)...(no debugging symbols found)... 
(no debugging symbols found)...(no debugging symbols found)... 
(no debugging symbols found)...[Thread debugging using libthread_db enabled] 
[New Thread 1089003232 (LWP 5179)] 
[New Thread 1105828784 (LWP 5182)] 
[New Thread 1114258352 (LWP 5183)] 
[New Thread 1122921392 (LWP 5184)] 
[New Thread 1135561648 (LWP 5185)] 
[New Thread 1148054448 (LWP 5186)] 
[New Thread 1158335408 (LWP 5187)] 
[New Thread 1166728112 (LWP 5191)] 
threads apply all bt 
 
And this is like root: 
 
(no debugging symbols found)...(no debugging symbols found)... 
(no debugging symbols found)...(no debugging symbols found)... 
(no debugging symbols found)...(no debugging symbols found)... 
(no debugging symbols found)...(no debugging symbols found)... 
(no debugging symbols found)...(no debugging symbols found)... 
(no debugging symbols found)...(no debugging symbols found)... 
(no debugging symbols found)...(no debugging symbols found)... 
(no debugging symbols found)...(no debugging symbols found)... 
(no debugging symbols found)...(no debugging symbols found)... 
(no debugging symbols found)...(no debugging symbols found)... 
(no debugging symbols found)...(no debugging symbols found)... 
(no debugging symbols found)...(no debugging symbols found)... 
(no debugging symbols found)...(no debugging symbols found)... 
(no debugging symbols found)...[Thread debugging using libthread_db enabled] 
[New Thread 1089003232 (LWP 5232)] 
Detaching after fork from child process 5235. 
[New Thread 1105898416 (LWP 5237)] 
[New Thread 1114327984 (LWP 5238)] 
[New Thread 1122991024 (LWP 5239)] 
[New Thread 1135631280 (LWP 5240)] 
[New Thread 1148124080 (LWP 5241)] 
[New Thread 1158405040 (LWP 5242)] 
[New Thread 1166797744 (LWP 5246)] 
threads apply all bt 
 
Comment 5 Bastien Nocera 2005-02-18 15:04:17 UTC
Hmm, you're supposed to type those when you get the gdb prompt back, after a
segmentation fault.
See http://bugzilla.gnome.org/getting-traces.cgi and
http://fedora.linux.duke.edu/wiki/index.cgi/StackTraces for details.
Comment 6 Vidar Hauge 2005-05-22 16:32:06 UTC
No response--closing; feel free to reopen if you can provide the requested
information.