Bug#710115: totem: Totem crashes intermittently when adding a second file to play

[Sébastien]

Hi Paul,

As you requested [1], I tested totem to see if my bug report was similar to this one :

$ totem /usr/share/sounds/gnome/default/alerts/sonar.ogg /usr/share/sounds/gnome/default/alerts/glass.ogg

** (totem:15613): WARNING **: Problem inhibiting the screensaver: GDBus.Error:org.freedesktop.DBus.Error.NameHasNoOwner: Name "org.gnome.SessionManager" does not exist

(totem:15613): Totem-WARNING **: g_file_set_attribute_string failed: Setting attribute metadata::totem::position not supported

** (totem:15613): WARNING **: Problem inhibiting the screensaver: GDBus.Error:org.freedesktop.DBus.Error.NameHasNoOwner: Name "org.gnome.SessionManager" does not exist

(totem:15613): Totem-WARNING **: g_file_set_attribute_string failed: Setting attribute metadata::totem::position not supported

(totem:15613): GLib-GObject-WARNING **: instance of invalid non-instantiatable type `(null)'

(totem:15613): GLib-GObject-CRITICAL **: g_signal_handlers_destroy: assertion `G_TYPE_CHECK_INSTANCE (instance)' failed
Segmentation fault

So I've merged both bugs.

I looked to see if any of the packages totem depends on were upgraded recently (well, from the begining of may) :

2013-05-10 19:48:00 upgrade libatk1.0-0:amd64 2.4.0-2 2.8.0-2

2013-05-09 09:44:26 upgrade libc6:amd64 2.13-38 2.17-1
2013-05-13 21:51:55 upgrade libc6:amd64 2.17-1 2.17-2
2013-05-21 13:35:09 upgrade libc6:amd64 2.17-2 2.17-3

2013-05-06 17:26:06 upgrade libcairo-gobject2:amd64 1.12.2-3 1.12.14-2
2013-05-09 09:46:25 upgrade libcairo-gobject2:amd64 1.12.14-2 1.12.14-3
2013-05-10 19:48:05 upgrade libcairo-gobject2:amd64 1.12.14-3 1.12.14-4

2013-05-06 17:26:05 upgrade libcairo2:amd64 1.12.2-3 1.12.14-2
2013-05-09 09:46:14 upgrade libcairo2:amd64 1.12.14-2 1.12.14-3
2013-05-10 19:48:02 upgrade libcairo2:amd64 1.12.14-3 1.12.14-4

2013-05-09 09:46:30 upgrade libdbus-1-3:amd64 1.6.8-1 1.6.10-1

2013-05-09 09:46:18 upgrade libgirepository-1.0-1:amd64 1.32.1-1 1.36.0-2
2013-05-12 21:34:54 upgrade libgirepository-1.0-1:amd64 1.36.0-2 1.36.0-2+b1

2013-05-09 09:46:24 upgrade libglib2.0-0:amd64 2.33.12+really2.32.4-5 2.36.1-2
2013-05-13 21:52:18 upgrade libglib2.0-0:amd64 2.36.1-2 2.36.1-2build1

2013-05-27 07:40:24 upgrade libgtk-3-0:amd64 3.4.2-6 3.8.2-1

2013-05-23 10:28:07 upgrade libpango1.0-0:amd64 1.30.0-1 1.32.5-5

2013-05-13 21:53:03 upgrade libpeas-1.0-0:amd64 1.4.0-2 1.4.0-2+b1

2013-05-13 21:53:04 upgrade libtotem0:amd64 3.0.1-8 3.0.1-8+b1

2013-05-27 07:18:43 upgrade libx11-6:amd64 2:1.5.0-1 2:1.5.0-1+deb7u1

2013-05-24 17:02:00 upgrade libxrandr2:amd64 2:1.3.2-2 2:1.3.2-2+deb7u1

2013-05-24 17:02:09 upgrade libxtst6:amd64 2:1.2.1-1 2:1.2.1-1+deb7u1

2013-05-24 17:01:28 upgrade libxxf86vm1:amd64 1:1.1.2-1 1:1.1.2-1+deb7u1

2013-05-21 13:49:04 upgrade libpython2.7:amd64 2.7.3-8 2.7.5-4
2013-05-21 13:49:05 upgrade python2.7:amd64 2.7.3-8 2.7.5-4

I'm sorry, but I can't remember when this problem appears, to see which upgrade might be the cause.

Sebastien

[1] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=710105#10