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 515681 - crash in Movie Player:
crash in Movie Player:
Status: RESOLVED DUPLICATE of bug 358891
Product: totem
Classification: Core
Component: general
2.20.x
Other All
: High critical
: ---
Assigned To: General Totem maintainer(s)
General Totem maintainer(s)
Depends on:
Blocks:
 
 
Reported: 2008-02-11 03:58 UTC by tamaruo
Modified: 2008-02-11 11:47 UTC
See Also:
GNOME target: ---
GNOME version: 2.19/2.20



Description tamaruo 2008-02-11 03:58:43 UTC
Version: 2.20.3

What were you doing when the application crashed?



Distribution: Debian lenny/sid
Gnome Release: 2.20.3 2008-01-12 (Debian)
BugBuddy Version: 2.20.1

System: Linux 2.6.22-3-686 #1 SMP Mon Nov 12 08:32:57 UTC 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: gnome

Memory status: size: 62554112 vsize: 62554112 resident: 26865664 share: 14700544 rss: 26865664 rss_rlim: 4294967295
CPU usage: start_time: 1202702309 rtime: 74 utime: 66 stime: 8 cutime:0 cstime: 2 timeout: 0 it_real_value: 0 frequency: 100

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

Using host libthread_db library "/lib/i686/cmov/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread 0xb6d136b0 (LWP 5847)]
[New Thread 0xb550eb90 (LWP 5853)]
[New Thread 0xb608db90 (LWP 5849)]
0xffffe410 in __kernel_vsyscall ()

Thread 2 (Thread 0xb550eb90 (LWP 5853))

  • #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 __kernel_vsyscall
  • #7 raise
    from /lib/i686/cmov/libc.so.6
  • #8 abort
    from /lib/i686/cmov/libc.so.6
  • #9 g_logv
    from /usr/lib/libglib-2.0.so.0
  • #10 g_log
    from /usr/lib/libglib-2.0.so.0
  • #11 g_assert_warning
    from /usr/lib/libglib-2.0.so.0
  • #12 gst_dvd_read_src_create
    at dvdreadsrc.c line 794
  • #13 ??
    from /usr/lib/libgstbase-0.10.so.0
  • #14 ??
  • #15 ??
  • #16 ??


----------- .xsession-errors (155 sec old) ---------------------
ウィンドウ・マネージャの警告: last_user_time (171009200) is greater than comparison timestamp (109378004).  This most likely represents a buggy client sending inaccurate timestamps in me
ウィンドウ・マネージャの警告: 0x26000dd ([debian] -) appears to be one of the offending windows with a timestamp of 171009200.  Working around...

(gnome-terminal:4736): GnomeUI-WARNING **: While connecting to session manager:
Authentication Rejected, reason : None of the authentication protocols specified are supported and host-based authentication failed.
ウィンドウ・マネージャの警告: last_user_time (137717232) is greater than comparison timestamp (109913964).  This most likely represents a buggy client sending inaccurate timestamps in me
ウィンドウ・マネージャの警告: 0x340001f (霞) appears to be one of the offending windows with a timestamp of 137717232.  Working around...
sh: jackd: command not found

(gnome-terminal:5474): GnomeUI-WARNING **: While connecting to session manager:
Authentication Rejected, reason : None of the authentication protocols specified are supported and host-based authentication failed.

(gnome-terminal:5637): GnomeUI-WARNING **: While connecting to session manager:
Authentication Rejected, reason : None of the authentication protocols specified are supported and host-based authentication failed.
/usr/lib/iceweasel/firefox-bin: Symbol `SSL_ImplementedCiphers' has different size in shared object, consider re-linking
--------------------------------------------------
Comment 1 Philip Withnall 2008-02-11 11:47:28 UTC
Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but we are happy to tell you that the problem has already been fixed. It should be solved in the next software version. You may want to check for a software upgrade.


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