Bug 736626 – PyGIO: GLib: Crash when calling Gio.VolumeMonitor()

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 736626 - PyGIO: GLib: Crash when calling Gio.VolumeMonitor()


Summary:	PyGIO: GLib: Crash when calling Gio.VolumeMonitor()


Status:	RESOLVED DUPLICATE of bug 675581

Product:	glib
Classification:	Platform
Component:	gio
Version:	unspecified
Hardware:	Other Linux

Importance:	Normal normal
Target Milestone:	---
Assigned To:	gtkdev
QA Contact:	gtkdev

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2014-09-13 16:41 UTC by MeanEYE
Modified:	2014-09-14 05:08 UTC

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

Description MeanEYE 2014-09-13 16:41:32 UTC

When calling Gio.VolumeMonitor() instead of Gio.VolumeMonitor.get() from Python using GObject Introspection, Python just crashes with no error displayed.

+ Trace 234090

#0 ??
#1 g_volume_monitor_get_volumes
from /usr/lib/i386-linux-gnu/libgio-2.0.so.0
#2 ffi_call_SYSV
from /usr/lib/i386-linux-gnu/libffi.so.6
#3 ffi_call
from /usr/lib/i386-linux-gnu/libffi.so.6
#4 ??
from /usr/lib/python2.7/dist-packages/gi/_gi.so
#5 ??
from /usr/lib/python2.7/dist-packages/gi/_gi.so
#6 ??
from /usr/lib/python2.7/dist-packages/gi/_gi.so
#7 PyObject_Call
at ../Objects/abstract.c line 2529
#8 do_call
at ../Python/ceval.c line 4239
#9 call_function
at ../Python/ceval.c line 4044
#10 PyEval_EvalFrameEx
at ../Python/ceval.c line 2667
#11 PyEval_EvalCodeEx
at ../Python/ceval.c line 3253
#12 function_call.lto_priv
at ../Objects/funcobject.c line 526
#13 PyObject_Call
#14 instancemethod_call.lto_priv
at ../Objects/classobject.c line 2602
#15 PyObject_Call
#16 PyEval_CallObjectWithKeywords
#17 PyObject_CallObject
at ../Objects/abstract.c line 2517
#18 ??
from /usr/lib/python2.7/dist-packages/gi/_gi.so
#19 ??
from /usr/lib/i386-linux-gnu/libffi.so.6
#20 ??
from /usr/lib/i386-linux-gnu/libffi.so.6
#21 ??
from /lib/i386-linux-gnu/libglib-2.0.so.0
#22 g_main_context_dispatch
from /lib/i386-linux-gnu/libglib-2.0.so.0
#23 ??
from /lib/i386-linux-gnu/libglib-2.0.so.0
#24 g_main_loop_run
from /lib/i386-linux-gnu/libglib-2.0.so.0
#25 gtk_main
from /usr/lib/i386-linux-gnu/libgtk-3.so.0
#26 ffi_call_SYSV
from /usr/lib/i386-linux-gnu/libffi.so.6
#27 ffi_call
from /usr/lib/i386-linux-gnu/libffi.so.6
#28 ??
from /usr/lib/python2.7/dist-packages/gi/_gi.so
#29 ??
from /usr/lib/python2.7/dist-packages/gi/_gi.so
#30 ??
from /usr/lib/python2.7/dist-packages/gi/_gi.so
#31 PyObject_Call
at ../Objects/abstract.c line 2529
#32 do_call
at ../Python/ceval.c line 4239
#33 call_function
at ../Python/ceval.c line 4044
#34 PyEval_EvalFrameEx
at ../Python/ceval.c line 2667
#35 PyEval_EvalCodeEx
at ../Python/ceval.c line 3253
#36 fast_function
at ../Python/ceval.c line 4117
#37 call_function
at ../Python/ceval.c line 4042
#38 PyEval_EvalFrameEx
at ../Python/ceval.c line 2667
#39 PyEval_EvalCodeEx
at ../Python/ceval.c line 3253
#40 PyEval_EvalCode
#41 run_mod.lto_priv
at ../Python/pythonrun.c line 1370
#42 PyRun_FileExFlags
at ../Python/pythonrun.c line 1356
#43 PyRun_SimpleFileExFlags
at ../Python/pythonrun.c line 948
#44 Py_Main
at ../Modules/main.c line 640
#45 main
at ../Modules/python.c line 23

Comment 1 Simon Feltman 2014-09-14 05:08:31 UTC

Marking as dup of bug 675581, also note bug 647731 which specifically mentioned Gio.VolumeMonitor(). The problem is deeper than any specific class in that introspection based bindings need a generic way of knowing if it is safe to create an object with g_object_new().

See also:
https://wiki.gnome.org/Projects/PyGObject/Analysis/Bug675581

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