Ticket #566 (closed bug: fixed)
Crash at launch : problems with dbus python
| Reported by: | vlaaad | Owned by: | theli |
|---|---|---|---|
| Priority: | critical | Milestone: | 0.6 |
| Component: | Core | Version: | trunk |
| Keywords: | crash launch dbus | Cc: |
Description
I can't get listen 0.5 working. It seems that I have troubles with dbus-python, not sure if it is a bug from your software or in my setup. Here is the backtrace I get with dbus-python 0.71 on ArchLinux? :
/opt/gnome/lib/listen/stock.py:78: DeprecationWarning?: Non-ASCII character '\xc3' in file /opt/gnome/lib/listen/const.py on lin e 117, but no encoding declared; see http://www.python.org/peps/pep-0263.html for details
import const
/opt/gnome/lib/listen/player.py:33: DeprecationWarning?: Non-ASCII character '\xc2' in file /opt/gnome/lib/listen/song.py on lin e 716, but no encoding declared; see http://www.python.org/peps/pep-0263.html for details
from song import sType
No musicbrainz support (musicbrainz2 missing) No iPod support No Audio cd support (musicbrainz2 missing) Registering 'moz.pyloader.1' (libpyloader.so) 17688: assertion failed "i < j" file "dbus-object-tree.c" line 1108 function _dbus_decompose_path
/usr/lib/libdbus-1.so.3 [0xb75b7cde] /usr/lib/libdbus-1.so.3 [0xb75b70c7] /usr/lib/libdbus-1.so.3 [0xb75ab7b7] /usr/lib/libdbus-1.so.3 [0xb759bf47] /usr/lib/libdbus-1.so.3(dbus_connection_register_object_path+0x140) [0xb75844f0] /usr/lib/python2.4/site-packages/dbus/dbus_bindings.so [0xb3ba8f82] /usr/lib/libpython2.4.so.1.0(PyCFunction_Call+0x12a) [0xb7e587aa] /usr/lib/libpython2.4.so.1.0(PyEval?_EvalFrame+0x4c47) [0xb7e93f07] /usr/lib/libpython2.4.so.1.0(PyEval?_EvalCodeEx+0x84a) [0xb7e9502a] /usr/lib/libpython2.4.so.1.0 [0xb7e451d0] /usr/lib/libpython2.4.so.1.0(PyObject?_Call+0x37) [0xb7e2a247] /usr/lib/libpython2.4.so.1.0 [0xb7e31a82] /usr/lib/libpython2.4.so.1.0(PyObject?_Call+0x37) [0xb7e2a247] /usr/lib/libpython2.4.so.1.0(PyEval?_EvalFrame+0x2591) [0xb7e91851] /usr/lib/libpython2.4.so.1.0(PyEval?_EvalCodeEx+0x84a) [0xb7e9502a] /usr/lib/libpython2.4.so.1.0 [0xb7e451d0] /usr/lib/libpython2.4.so.1.0(PyObject?_Call+0x37) [0xb7e2a247] /usr/lib/libpython2.4.so.1.0 [0xb7e31a82] /usr/lib/libpython2.4.so.1.0(PyObject?_Call+0x37) [0xb7e2a247] /usr/lib/libpython2.4.so.1.0 [0xb7e707ee] /usr/lib/libpython2.4.so.1.0 [0xb7e69e25] /usr/lib/libpython2.4.so.1.0(PyObject?_Call+0x37) [0xb7e2a247] /usr/lib/libpython2.4.so.1.0(PyEval?_EvalFrame+0x2591) [0xb7e91851] /usr/lib/libpython2.4.so.1.0(PyEval?_EvalCodeEx+0x84a) [0xb7e9502a] /usr/lib/libpython2.4.so.1.0 [0xb7e451d0] /usr/lib/libpython2.4.so.1.0(PyObject?_Call+0x37) [0xb7e2a247] /usr/lib/libpython2.4.so.1.0 [0xb7e31a82] /usr/lib/libpython2.4.so.1.0(PyObject?_Call+0x37) [0xb7e2a247] /usr/lib/libpython2.4.so.1.0 [0xb7e707ee] /usr/lib/libpython2.4.so.1.0 [0xb7e69e25] /usr/lib/libpython2.4.so.1.0(PyObject?_Call+0x37) [0xb7e2a247] /usr/lib/libpython2.4.so.1.0(PyEval?_EvalFrame+0x2591) [0xb7e91851] /usr/lib/libpython2.4.so.1.0(PyEval?_EvalCodeEx+0x84a) [0xb7e9502a] /usr/lib/libpython2.4.so.1.0 [0xb7e451d0] /usr/lib/libpython2.4.so.1.0(PyObject?_Call+0x37) [0xb7e2a247] /usr/lib/libpython2.4.so.1.0 [0xb7e31a82] /usr/lib/libpython2.4.so.1.0(PyObject?_Call+0x37) [0xb7e2a247] /usr/lib/libpython2.4.so.1.0(PyEval?_CallObjectWithKeywords+0x7b) [0xb7e8e62b] /usr/lib/libpython2.4.so.1.0(PyInstance?_New+0x7a) [0xb7e3572a] /usr/lib/libpython2.4.so.1.0(PyObject?_Call+0x37) [0xb7e2a247] /usr/lib/libpython2.4.so.1.0(PyEval?_EvalFrame+0x2591) [0xb7e91851] /usr/lib/libpython2.4.so.1.0(PyEval?_EvalCodeEx+0x84a) [0xb7e9502a] /usr/lib/libpython2.4.so.1.0(PyEval?_EvalCode+0x55) [0xb7e95095] /usr/lib/libpython2.4.so.1.0(PyRun?_FileExFlags+0xb7) [0xb7eb9b47] /usr/lib/libpython2.4.so.1.0(PyRun?_SimpleFileExFlags+0x1a6) [0xb7eb9d56] /usr/lib/libpython2.4.so.1.0(PyRun?_AnyFileExFlags+0x7a) [0xb7eba02a] /usr/lib/libpython2.4.so.1.0(Py_Main+0xbb1) [0xb7ec03e1] python(main+0x32) [0x80485b2] /lib/libc.so.6(libc_start_main+0xd8) [0xb7bc07c8] python [0x80484f1]
** (bug-buddy:17703): WARNING **: Impossible de charger l'icône pour Déchiffrer le fichier
** (bug-buddy:17703): WARNING **: Impossible de charger l'icône pour Importer une clé
** (bug-buddy:17703): WARNING **: Impossible de charger l'icône pour Ouvrir le dossier
** (bug-buddy:17703): WARNING **: Impossible de charger l'icône pour Vérifier la signature /opt/gnome/libexec/Music Player Listen: No such file or directory. Failed to read a valid object file image from memory.
Thus I wondered, as dbus 1.0.2 is installed on my laptop, if I didn't need a newer version of dbus-python, for instance the last 0.80.1. I had not been luckier :
/opt/gnome/lib/listen/stock.py:78: DeprecationWarning?: Non-ASCII character '\xc3' in file /opt/gnome/lib/listen/const.py on line 117, but no encoding declared; see http://www.python.org/peps/pep-0263.html for details
import const
/opt/gnome/lib/listen/player.py:33: DeprecationWarning?: Non-ASCII character '\xc2' in file /opt/gnome/lib/listen/song.py on line 716, but no encoding declared; see http://www.python.org/peps/pep-0263.html for details
from song import sType
No musicbrainz support (musicbrainz2 missing) No iPod support No Audio cd support (musicbrainz2 missing) Registering 'moz.pyloader.1' (libpyloader.so) Traceback (most recent call last):
File "/opt/gnome/lib/listen/listen.py", line 219, in ?
File "/opt/gnome/lib/listen/listen.py", line 146, in init
self.listen_instance = Listen()
File "/opt/gnome/lib/listen/widget/listen.py", line 121, in init
self.dbus_service = ListenDBus(self,player)
File "/opt/gnome/lib/listen/dbus_manager.py", line 56, in init
dbus.service.Object.init(self, bus_name, object_path)
File "/usr/lib/python2.4/site-packages/dbus/service.py", line 418, in init
self._connection._register_object_path(object_path, self._message_cb, self._unregister_cb)
RuntimeError?: To make asynchronous calls, receive signals or export objects, D-Bus connections must be attached to a main loop by passing mainloop=... to the constructor or calling dbus.set_default_main_loop(...)
A python application which uses dbus like gajim works in both setups, so I would say the problem is in your software. But I might be wrong ;-)
Thanks anyway for this great software !
