| 1 |
On 04/17/13 14:18, Michael Mol wrote: |
| 2 |
>On 4/17/2013 2:14 PM, Joseph wrote: |
| 3 |
>> I can not start meld, getting an error: |
| 4 |
>> |
| 5 |
>> # meld Traceback (most recent call last): |
| 6 |
>> File "/usr/bin/meld", line 154, in <module> |
| 7 |
>> main() |
| 8 |
>> File "/usr/bin/meld", line 140, in main |
| 9 |
>> already_running, dbus_app = meld.dbus_service.setup(app) |
| 10 |
>> File "/usr/lib64/meld/meld/dbus_service.py", line 54, in setup |
| 11 |
>> bus = dbus.SessionBus() |
| 12 |
>> File "/usr/lib64/python2.7/site-packages/dbus/_dbus.py", line 211, |
| 13 |
>> in __new__ |
| 14 |
>> mainloop=mainloop) |
| 15 |
>> File "/usr/lib64/python2.7/site-packages/dbus/_dbus.py", line 100, |
| 16 |
>> in __new__ |
| 17 |
>> bus = BusConnection.__new__(subclass, bus_type, mainloop=mainloop) |
| 18 |
>> File "/usr/lib64/python2.7/site-packages/dbus/bus.py", line 122, in |
| 19 |
>> __new__ |
| 20 |
>> bus = cls._new_for_bus(address_or_type, mainloop=mainloop) |
| 21 |
>> dbus.exceptions.DBusException: org.freedesktop.DBus.Error.NoReply: Did |
| 22 |
>> not receive a reply. Possible causes include: the remote application |
| 23 |
>> did not send a reply, the message bus security policy blocked the |
| 24 |
>> reply, the reply timeout expired, or the network connection was broken. |
| 25 |
>> |
| 26 |
>> It compiles without any problems. |
| 27 |
>> When I try to start it as user, same error: |
| 28 |
>> |
| 29 |
>> $ meld Traceback (most recent call last): |
| 30 |
>> File "/usr/bin/meld", line 154, in <module> |
| 31 |
>> main() |
| 32 |
>> File "/usr/bin/meld", line 136, in main |
| 33 |
>> import meld.meldapp |
| 34 |
>> File "/usr/lib64/meld/meld/meldapp.py", line 218, in <module> |
| 35 |
>> import filediff |
| 36 |
>> File "/usr/lib64/meld/meld/filediff.py", line 60, in <module> |
| 37 |
>> process_pool = multiprocessing.Pool(None, init_worker, |
| 38 |
>> maxtasksperchild=1) |
| 39 |
>> File "/usr/lib64/python2.7/multiprocessing/__init__.py", line 232, |
| 40 |
>> in Pool |
| 41 |
>> return Pool(processes, initializer, initargs, maxtasksperchild) |
| 42 |
>> File "/usr/lib64/python2.7/multiprocessing/pool.py", line 115, in |
| 43 |
>> __init__ |
| 44 |
>> self._setup_queues() |
| 45 |
>> File "/usr/lib64/python2.7/multiprocessing/pool.py", line 210, in |
| 46 |
>> _setup_queues |
| 47 |
>> self._inqueue = SimpleQueue() |
| 48 |
>> File "/usr/lib64/python2.7/multiprocessing/queues.py", line 352, in |
| 49 |
>> __init__ |
| 50 |
>> self._rlock = Lock() |
| 51 |
>> File "/usr/lib64/python2.7/multiprocessing/synchronize.py", line |
| 52 |
>> 147, in __init__ |
| 53 |
>> SemLock.__init__(self, SEMAPHORE, 1, 1) |
| 54 |
>> File "/usr/lib64/python2.7/multiprocessing/synchronize.py", line 75, |
| 55 |
>> in __init__ |
| 56 |
>> sl = self._semlock = _multiprocessing.SemLock(kind, value, maxvalue) |
| 57 |
>> OSError: [Errno 13] Permission denied |
| 58 |
>> |
| 59 |
> |
| 60 |
>Those are two different errors. The first is: |
| 61 |
> |
| 62 |
>File "/usr/lib64/python2.7/site-packages/dbus/bus.py", line 122, in __new__ |
| 63 |
> bus = cls._new_for_bus(address_or_type, mainloop=mainloop) |
| 64 |
>dbus.exceptions.DBusException: org.freedesktop.DBus.Error.NoReply: Did |
| 65 |
>not receive a reply. Possible causes include: the remote application did |
| 66 |
>not send a reply, the message bus security policy blocked the reply, the |
| 67 |
>reply timeout expired, or the network connection was broken. |
| 68 |
> |
| 69 |
>The second is: |
| 70 |
> |
| 71 |
> File "/usr/lib64/python2.7/multiprocessing/synchronize.py", line 75, |
| 72 |
>in __init__ |
| 73 |
> sl = self._semlock = _multiprocessing.SemLock(kind, value, maxvalue) |
| 74 |
>OSError: [Errno 13] Permission denied |
| 75 |
> |
| 76 |
> |
| 77 |
>At a first guess, try python-updater as root. |
| 78 |
|
| 79 |
I run "python-updater" it did not help :-/ |
| 80 |
|
| 81 |
|
| 82 |
-- |
| 83 |
Joseph |
Archives