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 535868 - crash in Movie Player: Watching the movie
crash in Movie Player: Watching the movie
Status: RESOLVED DUPLICATE of bug 426990
Product: totem
Classification: Core
Component: general
2.22.x
Other All
: High critical
: ---
Assigned To: General Totem maintainer(s)
General Totem maintainer(s)
Depends on:
Blocks:
 
 
Reported: 2008-05-31 03:10 UTC by dsrawlins
Modified: 2008-05-31 06:08 UTC
See Also:
GNOME target: ---
GNOME version: 2.21/2.22


Description dsrawlins 2008-05-31 03:10:43 UTC 
Version: 2.22.2

What were you doing when the application crashed?
Watching the movie


Distribution: Debian lenny/sid
Gnome Release: 2.22.1 2008-04-08 (Debian)
BugBuddy Version: 2.22.0

System: Linux 2.6.24-1-686 #1 SMP Thu May 8 02:16:39 UTC 2008 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10400090
Selinux: No
Accessibility: Disabled
GTK+ Theme: SphereCrystal
Icon Theme: SphereCrystal

Memory status: size: 165949440 vsize: 165949440 resident: 63774720 share: 15654912 rss: 63774720 rss_rlim: 4294967295
CPU usage: start_time: 1212203138 rtime: 8406 utime: 8075 stime: 331 cutime:5 cstime: 8 timeout: 0 it_real_value: 0 frequency: 100

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

(no debugging symbols found)
Using host libthread_db library "/lib/i686/cmov/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 0xb68ac740 (LWP 15079)]
[New Thread 0xafdffb90 (LWP 15090)]
[New Thread 0xb2282b90 (LWP 15089)]
[New Thread 0xb2aa8b90 (LWP 15088)]
[New Thread 0xb330db90 (LWP 15087)]
[New Thread 0xb3b0eb90 (LWP 15086)]
[New Thread 0xb430fb90 (LWP 15085)]
[New Thread 0xb4b1bb90 (LWP 15084)]
[New Thread 0xb548eb90 (LWP 15083)]
[New Thread 0xb633db90 (LWP 15081)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

+ Trace 199238

Thread 1 (Thread 0xb68ac740 (LWP 15079))

  • #0 __kernel_vsyscall
  • #1 waitpid
    from /lib/i686/cmov/libpthread.so.0
  • #2 g_spawn_sync
    from /usr/lib/libglib-2.0.so.0
  • #3 g_spawn_command_line_sync
    from /usr/lib/libglib-2.0.so.0
  • #4 ??
    from /usr/lib/gtk-2.0/modules/libgnomebreakpad.so
  • #5 <signal handler called>
  • #6 g_type_check_value_holds
    from /usr/lib/libgobject-2.0.so.0
  • #7 gst_value_get_fraction_numerator
    from /usr/lib/libgstreamer-0.10.so.0
  • #8 ??
  • #9 ??
  • #10 ??
  • #11 ??
  • #12 ??
  • #0 __kernel_vsyscall 




----------- .xsession-errors (109 sec old) ---------------------

Original exception was:
/usr/lib/python2.5/site-packages/apt/__init__.py:18: FutureWarning: apt API not stable yet
  warnings.warn("apt API not stable yet", FutureWarning)
/usr/lib/python2.5/site-packages/apt/__init__.py:18: FutureWarning: apt API not stable yet
  warnings.warn("apt API not stable yet", FutureWarning)
error from apt: 'E:Could not get lock /var/lib/dpkg/lock - open (11 Resource temporarily unavailable), E:Unable to lock the administration directory (/var/lib/dpkg/), is another process using it?'
current dist not found in meta-release file
Unhandled exception in thread started by 
Error in sys.excepthook:

Original exception was:
No accelerated IMDCT transform found
No accelerated IMDCT transform found
No accelerated IMDCT transform found
--------------------------------------------------
Comment 1 Philip Withnall 2008-05-31 06:08:10 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 426990 ***