View previous topic :: View next topic |
Author |
Message |
Schmock n00b
Joined: 22 Jan 2006 Posts: 22
|
Posted: Tue May 01, 2007 12:02 pm Post subject: [SOLVED]Listen Music Player - dbus problem when run as user |
|
|
Hi!
When I try to start Listen as user, I get the following error:
Code: | Traceback (most recent call last):
File "/usr/lib/listen/listen.py", line 219, in ?
ListenApp()
File "/usr/lib/listen/listen.py", line 146, in __init__
self.listen_instance = Listen()
File "/usr/lib/listen/widget/listen.py", line 120, in __init__
self.notify = Notify(player,self.tray)
File "/usr/lib/listen/widget/notify.py", line 56, in __init__
if dbus_imported and bus and utils.dbus_service_available(bus,interface,True):
File "/usr/lib/listen/utils.py", line 83, in dbus_service_available
bus.start_service_by_name(interface)
File "//usr/lib/python2.4/site-packages/dbus/_dbus.py", line 241, in start_service_by_name
return dbus_bindings.bus_start_service_by_name(self._connection, named_service)
File "dbus_bindings.pyx", line 1737, in dbus_bindings.bus_start_service_by_name
dbus_bindings.DBusException: The name org.freedesktop.Notifications was not provided by any .service files |
I can start Listen when logged in as root, so which permissions do I have to change?
media-sound/listen-0.5
sys-apps/dbus-1.0.2-r2
dev-python/dbus-python-0.80.2
Last edited by Schmock on Wed May 02, 2007 2:18 pm; edited 1 time in total |
|
Back to top |
|
|
bosele Tux's lil' helper
Joined: 02 Apr 2005 Posts: 90
|
Posted: Tue May 01, 2007 1:47 pm Post subject: |
|
|
try masking =dev-python/dbus-python-0.80.2 |
|
Back to top |
|
|
Schmock n00b
Joined: 22 Jan 2006 Posts: 22
|
Posted: Tue May 01, 2007 3:11 pm Post subject: |
|
|
Oh, I forgot to mention that the same problem occurs with the old dbus-python version. |
|
Back to top |
|
|
entombedvirus n00b
Joined: 01 May 2007 Posts: 2
|
Posted: Tue May 01, 2007 5:35 pm Post subject: libnotify seems to solve the problem |
|
|
Hey,
I had the exact same problem on my amd64 system when starting listen. Since the stack trace said that the org.freedesktop.Notifications was not provided by anything, I tried emerging x11-libs/libnotify (0.4.3)
That seemed to fix things.
HTH. |
|
Back to top |
|
|
Schmock n00b
Joined: 22 Jan 2006 Posts: 22
|
Posted: Tue May 01, 2007 5:46 pm Post subject: Re: libnotify seems to solve the problem |
|
|
entombedvirus wrote: | Hey,
I had the exact same problem on my amd64 system when starting listen. Since the stack trace said that the org.freedesktop.Notifications was not provided by anything, I tried emerging x11-libs/libnotify (0.4.3)
That seemed to fix things.
HTH. | Hey,
emerging libnotify solved this, but now I get the following error....
Code: | Traceback (most recent call last):
File "/usr/lib/listen/listen.py", line 219, in ?
ListenApp()
File "/usr/lib/listen/listen.py", line 146, in __init__
self.listen_instance = Listen()
File "/usr/lib/listen/widget/listen.py", line 121, in __init__
self.dbus_service = ListenDBus(self,player)
File "/usr/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 416, 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(...) |
|
|
Back to top |
|
|
bosele Tux's lil' helper
Joined: 02 Apr 2005 Posts: 90
|
|
Back to top |
|
|
entombedvirus n00b
Joined: 01 May 2007 Posts: 2
|
Posted: Wed May 02, 2007 4:42 am Post subject: Are both system and session dbus instances up? |
|
|
Hey,
I'vent gotten that error so I am not completely sure how to fix it. But I would make sure that both the system and session dbus instances are running.
so a
should return something along the lines of
Code: |
4889 ? Ss 0:00 /usr/bin/dbus-daemon --system
6314 ? S 0:00 /usr/bin/dbus-launch --sh-syntax --exit-with-session
6315 ? Ss 0:00 /usr/bin/dbus-daemon --fork --print-pid 4 --print-address 6 --session
6341 ? Ss 0:00 /usr/bin/dbus-daemon --fork --print-pid 4 --print-address 6 --session
6342 ? S 0:00 dbus-launch --exit-with-session
|
things to look out for are the dbus-daemon --system part (which you can start by running:)
Code: |
/etc/init.d/dbus start
|
and a dbus-daemon --session (which you can start by running:)
Code: |
eval `dbus-launch --session --sh-syntax`
|
before you run listen. If that doesnt fix things, could you post the versions number of the following packages:
Code: |
sys-apps/dbus (1.0.2-r2)
dev-python/dbus-python (0.71)
|
The versions that I've are in parenthesis. |
|
Back to top |
|
|
Schmock n00b
Joined: 22 Jan 2006 Posts: 22
|
Posted: Wed May 02, 2007 12:42 pm Post subject: |
|
|
Right, downgrading to dbus-python-0.71 solved the second problem, thank you!
But I'm still wondering why it worked as root... |
|
Back to top |
|
|
RagmaVX n00b
Joined: 16 May 2007 Posts: 5
|
Posted: Wed May 16, 2007 1:57 pm Post subject: Patch on listen's site. |
|
|
I Have had the same problem. I after searching on listen's site for about an hour I found an explication and they even have a patch to fix the problem.
"The problem is that with dbus 0.80.0 the way the python bindings get started changed slightly."
http://www.listen-project.org/ticket/566
Download the patch and:
Code: | patch /usr/lib/listen/dbus_manager.py < PATH_AND_FILENAME_TO_PATCH_DIFF_FILE |
This worked for me.
P.S. This is my first post and i am still very new to linux. loving Gentoo though. And Listen |
|
Back to top |
|
|
adrislayer n00b
Joined: 16 Aug 2005 Posts: 48
|
Posted: Tue Jun 12, 2007 3:27 pm Post subject: |
|
|
thanks you a lot!
it worked for me too |
|
Back to top |
|
|
|