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 446186 - crash in Movie Player: opening totem
crash in Movie Player: opening totem
Status: RESOLVED DUPLICATE of bug 385438
Product: totem
Classification: Core
Component: general
2.16.x
Other All
: High critical
: ---
Assigned To: General Totem maintainer(s)
General Totem maintainer(s)
Depends on:
Blocks:
 
 
Reported: 2007-06-11 01:48 UTC by smulloni
Modified: 2007-06-12 02:25 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16


Description smulloni 2007-06-11 01:48:10 UTC 
Version: 2.16.4

What were you doing when the application crashed?
opening totem


Distribution: Gentoo Base System release 1.12.9
Gnome Release: 2.16.2 2007-02-26 (Gentoo)
BugBuddy Version: 2.16.0

Memory status: size: 127139840 vsize: 0 resident: 127139840 share: 0 rss: 27869184 rss_rlim: 0
CPU usage: start_time: 1181526447 rtime: 0 utime: 153 stime: 0 cutime:136 cstime: 0 timeout: 17 it_real_value: 0 frequency: 0

Backtrace was generated from '/usr/bin/totem'

(no debugging symbols found)
Using host libthread_db library "/lib/tls/libthread_db.so.1".
(no debugging symbols found)
`system-supplied DSO at 0xffffe000' has disappeared; keeping its symbols.
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1226533200 (LWP 14306)]
[New Thread -1314067568 (LWP 14324)]
[New Thread -1305674864 (LWP 14323)]
[New Thread -1295393904 (LWP 14322)]
[New Thread -1282901104 (LWP 14321)]
[New Thread -1274508400 (LWP 14320)]
[New Thread -1266115696 (LWP 14317)]
[New Thread -1249547376 (LWP 14316)]
0xffffe410 in __kernel_vsyscall ()

+ Trace 139903







Comment 1


Pedro Villavicencio





          2007-06-12 02:25:16 UTC
        



Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but the maintainers need more information to fix the bug. Could you please answer the questions in the other report in order to help the developers?


*** This bug has been marked as a duplicate of 385438 ***