Bug 668500 – Totem crashes with DBus plugin and a GNOME Shell MPRIS-based extension enabled.

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 668500 - Totem crashes with DBus plugin and a GNOME Shell MPRIS-based extension enabled.


Summary:	Totem crashes with DBus plugin and a GNOME Shell MPRIS-based extension enabled.


Status:	RESOLVED DUPLICATE of bug 666431

Product:	totem
Classification:	Core
Component:	Plugins
Version:	3.2.x
Hardware:	Other Linux

Importance:	High critical
Target Milestone:	---
Assigned To:	General Totem maintainer(s)
QA Contact:	General Totem maintainer(s)

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2012-01-23 14:09 UTC by Reda Lazri
Modified:	2012-02-08 13:14 UTC

See Also:
GNOME target:	---
GNOME version:	---

Description Reda Lazri 2012-01-23 14:09:21 UTC

I tried both extensions: 
https://extensions.gnome.org/extension/55/media-player-indicator/
https://extensions.gnome.org/extension/54/mpris-player-control/

Totem crashes as soon as you open it. Disabling the DBUS plugin in Totem fixes it.

Comment 1 Bastien Nocera 2012-01-23 14:16:00 UTC

Thanks for taking the time to report this bug.
Without a stack trace from the crash it's very hard to determine what caused it.
Can you get us a stack trace? Please see http://live.gnome.org/GettingTraces for more information on how to do so. Thanks in advance!

Comment 2 Reda Lazri 2012-01-23 14:42:25 UTC

+ Trace 229493

#0 __strlen_sse2_bsf
from /lib/libc.so.6
#1 PyString_FromString
from /usr/lib/libpython2.7.so.1.0
#2 ??
from /usr/lib/python2.7/site-packages/gi/_gi.so
#3 ??
from /usr/lib/python2.7/site-packages/gi/_gi.so
#4 ??
from /usr/lib/python2.7/site-packages/gi/_gi.so
#5 PyCFunction_Call
from /usr/lib/libpython2.7.so.1.0
#6 PyEval_EvalFrameEx
from /usr/lib/libpython2.7.so.1.0
#7 PyEval_EvalCodeEx
from /usr/lib/libpython2.7.so.1.0
#8 PyEval_EvalFrameEx
from /usr/lib/libpython2.7.so.1.0
#9 PyEval_EvalFrameEx
from /usr/lib/libpython2.7.so.1.0
#10 PyEval_EvalCodeEx
from /usr/lib/libpython2.7.so.1.0
#11 function_call
from /usr/lib/libpython2.7.so.1.0
#12 PyObject_Call
from /usr/lib/libpython2.7.so.1.0
#13 PyEval_EvalFrameEx
from /usr/lib/libpython2.7.so.1.0
#14 PyEval_EvalCodeEx
from /usr/lib/libpython2.7.so.1.0
#15 function_call
from /usr/lib/libpython2.7.so.1.0
#16 PyObject_Call
from /usr/lib/libpython2.7.so.1.0
#17 instancemethod_call
from /usr/lib/libpython2.7.so.1.0
#18 PyObject_Call
from /usr/lib/libpython2.7.so.1.0
#19 PyObject_CallFunctionObjArgs
from /usr/lib/libpython2.7.so.1.0
#20 ??
from /usr/lib/python2.7/site-packages/_dbus_bindings.so

Comment 3 Philip Withnall 2012-01-23 15:04:38 UTC

Unfortunately that stack trace isn't very useful; a lot of information's missing. Could you install the debug information for Python and PyGObject (see “Installing debugging information packages” on http://live.gnome.org/GettingTraces) and produce another stack trace please? We need one which doesn't have the ‘??’ entries.

Thanks.

Comment 4 Reda Lazri 2012-01-23 15:44:28 UTC

What packages do I need to recompile to clear the ?? from #1 to #3?

+ Trace 229497

#0 PyString_FromString
at Objects/stringobject.c line 121
#1 ??
from /usr/lib/python2.7/site-packages/gi/_gi.so
#2 ??
from /usr/lib/python2.7/site-packages/gi/_gi.so
#3 ??
from /usr/lib/python2.7/site-packages/gi/_gi.so
#4 PyCFunction_Call
at Objects/methodobject.c line 85
#5 ext_do_call
at Python/ceval.c line 4323
#6 PyEval_EvalFrameEx
at Python/ceval.c line 2705
#7 PyEval_EvalCodeEx
at Python/ceval.c line 3253
#8 fast_function
at Python/ceval.c line 4109
#9 call_function
at Python/ceval.c line 4034
#10 PyEval_EvalFrameEx
at Python/ceval.c line 2666
#11 fast_function
at Python/ceval.c line 4099
#12 call_function
at Python/ceval.c line 4034
#13 PyEval_EvalFrameEx
at Python/ceval.c line 2666
#14 PyEval_EvalCodeEx
at Python/ceval.c line 3253
#15 function_call
at Objects/funcobject.c line 526
#16 PyObject_Call
at Objects/abstract.c line 2529
#17 ext_do_call
at Python/ceval.c line 4326
#18 PyEval_EvalFrameEx
at Python/ceval.c line 2705

Comment 5 Bastien Nocera 2012-01-23 21:16:38 UTC

Easy to reproduce here.

$ totem
Gtk-Message: Failed to load module "pk-gtk-module"

(totem:2214): GLib-GObject-CRITICAL **: g_value_get_int: assertion `G_VALUE_HOLDS_INT (value)' failed

(totem:2214): GLib-GObject-CRITICAL **: g_value_get_int: assertion `G_VALUE_HOLDS_INT (value)' failed
Segmentation fault

Philip, didn't we see something like that go by recently?

Comment 6 Philip Withnall 2012-01-23 21:36:50 UTC

(In reply to comment #5)
> Philip, didn't we see something like that go by recently?

Yeah, bug #666677 if you think it's the same one as in this stack trace.

Comment 7 Bastien Nocera 2012-02-08 13:14:53 UTC

Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.

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