Dear Rustom,
thank you for your bug report!
Am Dienstag, den 28.05.2013, 18:10 +0530 schrieb Rustom Mody:
> Package: totem
> Version: 3.0.1-8+b1
> Severity: important
>
> Dear Maintainer,
>
> totem has been recently crashing with segmentation fault (after debian
> upgrade)
> when adding a second file to play. This is somewhat intermittent -- I am not
> sure exactly how to reproduce it.
lately Totem crashes for me too [1] and I wonder if this is related.
Could you please try, if the following crashes for you too?
1. Configure Totem to play in endless loop with Edit and check Repeat
Mode.
2. Open a terminal emulator like GNOME Terminal and open it with two
(more than one) files. (I use the short system sound files, so I do not
need to jump in front.) Below I paste the output I get.
$ LANG=C totem /usr/share/sounds/gnome/default/alerts/sonar.ogg
/usr/share/sounds/gnome/default/alerts/glass.ogg
WARNING: gnome-keyring:: couldn't connect to:
/home/paul/.cache/keyring-T52RZJ/pkcs11: No such file or directory
(totem:658): GLib-GObject-WARNING **: instance of invalid
non-instantiatable type `(null)'
(totem:658): GLib-GObject-CRITICAL **: g_signal_handlers_destroy:
assertion `G_TYPE_CHECK_INSTANCE (instance)' failed
Speicherzugriffsfehler (Speicherabzug geschrieben)
If it does crash for you, please subscribe to the referenced upstream
bug report [1] too.
> -- System Information:
> Debian Release: jessie/sid
> APT prefers testing
> APT policy: (500, 'testing')
> Architecture: i386 (i686)
>
> Kernel: Linux 2.6.32-5-686 (SMP w/2 CPU cores)
Did you not upgrade your Linux kernel yet?
> Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
> Shell: /bin/sh linked to /bin/dash
>
> Versions of packages totem depends on:
> ii gnome-icon-theme 3.4.0-2
> ii gnome-icon-theme-symbolic 3.4.0-2
> ii gstreamer0.10-plugins-base 0.10.36-1.1
> ii gstreamer0.10-plugins-good 0.10.31-3+nmu1
> ii gstreamer0.10-x 0.10.36-1.1
> ii libatk1.0-0 2.8.0-2
> ii libc6 2.17-3
> ii libcairo-gobject2 1.12.14-4
> ii libcairo2 1.12.14-4
> ii libdbus-1-3 1.6.10-1
> ii libdbus-glib-1-2 0.100.2-1
> ii libgdk-pixbuf2.0-0 2.28.1-1
> ii libgirepository-1.0-1 1.36.0-2+b1
> ii libglib2.0-0 2.36.1-2build1
> ii libgstreamer-plugins-base0.10-0 0.10.36-1.1
> ii libgstreamer0.10-0 0.10.36-1.2
> ii libgtk-3-0 3.4.2-6
> ii libnautilus-extension1a 3.4.2-1+build1
> ii libpango1.0-0 1.30.0-1
> ii libpeas-1.0-0 1.4.0-2+b1
> ii libtotem-plparser17 3.4.2-1
> ii libtotem0 3.0.1-8+b1
> ii libx11-6 2:1.5.0-1
> ii libxml2 2.8.0+dfsg1-7+nmu1
> ii libxrandr2 2:1.3.2-2+deb7u1
> ii libxtst6 2:1.2.1-1+deb7u1
> ii libxxf86vm1 1:1.1.2-1+deb7u1
> ii python 2.7.3-5
> ii totem-common 3.0.1-8
>
> Versions of packages totem recommends:
> ii gstreamer0.10-ffmpeg 1:0.10.11-4.1
> ii gstreamer0.10-plugins-bad 0.10.23-7.1
> ii gstreamer0.10-plugins-ugly 0.10.19-2+b2
> ii gstreamer0.10-pulseaudio 0.10.31-3+nmu1
> ii totem-plugins 3.0.1-8+b1
>
> Versions of packages totem suggests:
> pn gnome-codec-install <none>
> ii gstreamer0.10-pulseaudio 0.10.31-3+nmu1
> pn totem-mozilla <none>
Could you check which of these packages above were upgraded on your
system when the crash happened? Only the *build1 packages?
Thanks,
Paul
[1] https://bugzilla.gnome.org/show_bug.cgi?id=701429
signature.asc
Description: This is a digitally signed message part
