Re: [gentoo-user] error starting meld
On 4/17/2013 2:14 PM, Joseph wrote: I can not start meld, getting an error: # meld Traceback (most recent call last): File /usr/bin/meld, line 154, in module main() File /usr/bin/meld, line 140, in main already_running, dbus_app = meld.dbus_service.setup(app) File /usr/lib64/meld/meld/dbus_service.py, line 54, in setup bus = dbus.SessionBus() File /usr/lib64/python2.7/site-packages/dbus/_dbus.py, line 211, in __new__ mainloop=mainloop) File /usr/lib64/python2.7/site-packages/dbus/_dbus.py, line 100, in __new__ bus = BusConnection.__new__(subclass, bus_type, mainloop=mainloop) File /usr/lib64/python2.7/site-packages/dbus/bus.py, line 122, in __new__ bus = cls._new_for_bus(address_or_type, mainloop=mainloop) dbus.exceptions.DBusException: org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken. It compiles without any problems. When I try to start it as user, same error: $ meld Traceback (most recent call last): File /usr/bin/meld, line 154, in module main() File /usr/bin/meld, line 136, in main import meld.meldapp File /usr/lib64/meld/meld/meldapp.py, line 218, in module import filediff File /usr/lib64/meld/meld/filediff.py, line 60, in module process_pool = multiprocessing.Pool(None, init_worker, maxtasksperchild=1) File /usr/lib64/python2.7/multiprocessing/__init__.py, line 232, in Pool return Pool(processes, initializer, initargs, maxtasksperchild) File /usr/lib64/python2.7/multiprocessing/pool.py, line 115, in __init__ self._setup_queues() File /usr/lib64/python2.7/multiprocessing/pool.py, line 210, in _setup_queues self._inqueue = SimpleQueue() File /usr/lib64/python2.7/multiprocessing/queues.py, line 352, in __init__ self._rlock = Lock() File /usr/lib64/python2.7/multiprocessing/synchronize.py, line 147, in __init__ SemLock.__init__(self, SEMAPHORE, 1, 1) File /usr/lib64/python2.7/multiprocessing/synchronize.py, line 75, in __init__ sl = self._semlock = _multiprocessing.SemLock(kind, value, maxvalue) OSError: [Errno 13] Permission denied Those are two different errors. The first is: File /usr/lib64/python2.7/site-packages/dbus/bus.py, line 122, in __new__ bus = cls._new_for_bus(address_or_type, mainloop=mainloop) dbus.exceptions.DBusException: org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken. The second is: File /usr/lib64/python2.7/multiprocessing/synchronize.py, line 75, in __init__ sl = self._semlock = _multiprocessing.SemLock(kind, value, maxvalue) OSError: [Errno 13] Permission denied At a first guess, try python-updater as root.
Re: [gentoo-user] error starting meld
On 04/17/13 14:18, Michael Mol wrote: On 4/17/2013 2:14 PM, Joseph wrote: I can not start meld, getting an error: # meld Traceback (most recent call last): File /usr/bin/meld, line 154, in module main() File /usr/bin/meld, line 140, in main already_running, dbus_app = meld.dbus_service.setup(app) File /usr/lib64/meld/meld/dbus_service.py, line 54, in setup bus = dbus.SessionBus() File /usr/lib64/python2.7/site-packages/dbus/_dbus.py, line 211, in __new__ mainloop=mainloop) File /usr/lib64/python2.7/site-packages/dbus/_dbus.py, line 100, in __new__ bus = BusConnection.__new__(subclass, bus_type, mainloop=mainloop) File /usr/lib64/python2.7/site-packages/dbus/bus.py, line 122, in __new__ bus = cls._new_for_bus(address_or_type, mainloop=mainloop) dbus.exceptions.DBusException: org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken. It compiles without any problems. When I try to start it as user, same error: $ meld Traceback (most recent call last): File /usr/bin/meld, line 154, in module main() File /usr/bin/meld, line 136, in main import meld.meldapp File /usr/lib64/meld/meld/meldapp.py, line 218, in module import filediff File /usr/lib64/meld/meld/filediff.py, line 60, in module process_pool = multiprocessing.Pool(None, init_worker, maxtasksperchild=1) File /usr/lib64/python2.7/multiprocessing/__init__.py, line 232, in Pool return Pool(processes, initializer, initargs, maxtasksperchild) File /usr/lib64/python2.7/multiprocessing/pool.py, line 115, in __init__ self._setup_queues() File /usr/lib64/python2.7/multiprocessing/pool.py, line 210, in _setup_queues self._inqueue = SimpleQueue() File /usr/lib64/python2.7/multiprocessing/queues.py, line 352, in __init__ self._rlock = Lock() File /usr/lib64/python2.7/multiprocessing/synchronize.py, line 147, in __init__ SemLock.__init__(self, SEMAPHORE, 1, 1) File /usr/lib64/python2.7/multiprocessing/synchronize.py, line 75, in __init__ sl = self._semlock = _multiprocessing.SemLock(kind, value, maxvalue) OSError: [Errno 13] Permission denied Those are two different errors. The first is: File /usr/lib64/python2.7/site-packages/dbus/bus.py, line 122, in __new__ bus = cls._new_for_bus(address_or_type, mainloop=mainloop) dbus.exceptions.DBusException: org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken. The second is: File /usr/lib64/python2.7/multiprocessing/synchronize.py, line 75, in __init__ sl = self._semlock = _multiprocessing.SemLock(kind, value, maxvalue) OSError: [Errno 13] Permission denied At a first guess, try python-updater as root. I run python-updater it did not help :-/ -- Joseph
Re: [gentoo-user] error starting meld
At a first guess, try python-updater as root. I run python-updater it did not help :-/ Did you restart X after running python-updater?
Re: [gentoo-user] error starting meld
On 04/18/13 11:36, Adam Carter wrote: At a first guess, try python-updater as root. I run python-updater it did not help :-/ Did you restart X after running python-updater? Yes, I rebooted the machine. -- Joseph
