Gentoo Forums
Gentoo Forums
Gentoo Forums
Quick Search: in
Program meld does not start anymore
View unanswered posts
View posts from last 24 hours
View posts from last 7 days

 
Reply to topic    Gentoo Forums Forum Index Desktop Environments
View previous topic :: View next topic  
Author Message
222697
n00b
n00b


Joined: 07 May 2010
Posts: 51

PostPosted: Mon Apr 01, 2013 6:27 pm    Post subject: Program meld does not start anymore Reply with quote

Hello,

today I updated my Gentoo (Linux 3.5.7 i686) with

Code:
emerge --sync -q
emerge --update --deep --newuse --verbose --ask world


Went all well. But after update, meld does not start anymore (wanted to use it for merging updated config files). I did also run python-updater, that did not help.

As root:
Code:
# 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/lib/meld/meld/dbus_service.py", line 54, in setup
    bus = dbus.SessionBus()
  File "/usr/lib/python2.7/site-packages/dbus/_dbus.py", line 211, in __new__
    mainloop=mainloop)
  File "/usr/lib/python2.7/site-packages/dbus/_dbus.py", line 100, in __new__
    bus = BusConnection.__new__(subclass, bus_type, mainloop=mainloop)
  File "/usr/lib/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.


As user:
Code:
$ LANG=POSIX LC_ALL=POSIX 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/lib/meld/meld/meldapp.py", line 218, in <module>
    import filediff
  File "/usr/lib/meld/meld/filediff.py", line 60, in <module>
    process_pool = multiprocessing.Pool(None, init_worker, maxtasksperchild=1)
  File "/usr/lib/python2.7/multiprocessing/__init__.py", line 232, in Pool
    return Pool(processes, initializer, initargs, maxtasksperchild)
  File "/usr/lib/python2.7/multiprocessing/pool.py", line 115, in __init__
    self._setup_queues()
  File "/usr/lib/python2.7/multiprocessing/pool.py", line 210, in _setup_queues
    self._inqueue = SimpleQueue()
  File "/usr/lib/python2.7/multiprocessing/queues.py", line 352, in __init__
    self._rlock = Lock()
  File "/usr/lib/python2.7/multiprocessing/synchronize.py", line 147, in __init__
    SemLock.__init__(self, SEMAPHORE, 1, 1)
  File "/usr/lib/python2.7/multiprocessing/synchronize.py", line 75, in __init__
    sl = self._semlock = _multiprocessing.SemLock(kind, value, maxvalue)
OSError: [Errno 13] Permission denied


Code:
$ python -V
Python 2.7.3
$ eselect python list
Available Python interpreters:
  [1]   python2.7 *
  [2]   python3.2


Any idea?
Back to top
View user's profile Send private message
eyoung100
Veteran
Veteran


Joined: 23 Jan 2004
Posts: 1428

PostPosted: Thu Apr 04, 2013 3:59 pm    Post subject: Reply with quote

Code:
eselect python system set 2 <--3.2 has been stable for a longwhile now
python-updater


As a hunch I would say that python 2.7 support has been dropped in meld.
_________________
The Birth and Growth of Science is the Death and Atrophy of Art -- Unknown
Registerd Linux User #363735
Adopt a Post | Strip Comments| Emerge Wrapper
Back to top
View user's profile Send private message
222697
n00b
n00b


Joined: 07 May 2010
Posts: 51

PostPosted: Thu Apr 04, 2013 4:54 pm    Post subject: Reply with quote

eyoung100 wrote:
Code:
eselect python system set 2 <--3.2 has been stable for a longwhile now
python-updater



Thanks, now with root user, meld starts without any problem. But as user i still get:

Code:
$ groups
wheel cron audio cdrom video users kvm
$ LANG=POSIX LC_ALL=POSIX 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/lib/meld/meld/meldapp.py", line 218, in <module>
    import filediff
  File "/usr/lib/meld/meld/filediff.py", line 60, in <module>
    process_pool = multiprocessing.Pool(None, init_worker, maxtasksperchild=1)
  File "/usr/lib/python2.7/multiprocessing/__init__.py", line 232, in Pool
    return Pool(processes, initializer, initargs, maxtasksperchild)
  File "/usr/lib/python2.7/multiprocessing/pool.py", line 115, in __init__
    self._setup_queues()
  File "/usr/lib/python2.7/multiprocessing/pool.py", line 210, in _setup_queues
    self._inqueue = SimpleQueue()
  File "/usr/lib/python2.7/multiprocessing/queues.py", line 352, in __init__
    self._rlock = Lock()
  File "/usr/lib/python2.7/multiprocessing/synchronize.py", line 147, in __init__
    SemLock.__init__(self, SEMAPHORE, 1, 1)
  File "/usr/lib/python2.7/multiprocessing/synchronize.py", line 75, in __init__
    sl = self._semlock = _multiprocessing.SemLock(kind, value, maxvalue)
OSError: [Errno 13] Permission denied
$ python -V
Python 3.2.3

Also re-emerging meld did not help

Hm, now also as root I cannot run meld again:

Code:
# 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/lib/meld/meld/dbus_service.py", line 54, in setup
    bus = dbus.SessionBus()
  File "/usr/lib/python2.7/site-packages/dbus/_dbus.py", line 211, in __new__
    mainloop=mainloop)
  File "/usr/lib/python2.7/site-packages/dbus/_dbus.py", line 100, in __new__
    bus = BusConnection.__new__(subclass, bus_type, mainloop=mainloop)
  File "/usr/lib/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.
Back to top
View user's profile Send private message
eyoung100
Veteran
Veteran


Joined: 23 Jan 2004
Posts: 1428

PostPosted: Thu Apr 04, 2013 6:17 pm    Post subject: Reply with quote

you can't rerun meld unless you kill the process 1st

As Root, Starting meld triggers DBus, DBus takes over etc etc

Running it as a user gives permission Denied, meaning you need to either add yourself to another group or use su.

Trying to rerun it as root causes a dbus error because dbus is still running from the process above.

After seeing what meld is, I can explain the need for su. since meld is a merge tool, if you are trying to edit config files after an emerge with it, you can't because root is the only user with write permission in /etc
_________________
The Birth and Growth of Science is the Death and Atrophy of Art -- Unknown
Registerd Linux User #363735
Adopt a Post | Strip Comments| Emerge Wrapper
Back to top
View user's profile Send private message
222697
n00b
n00b


Joined: 07 May 2010
Posts: 51

PostPosted: Fri Apr 05, 2013 2:35 am    Post subject: Reply with quote

OK the following info was missing: After I could successfully start meld as root but not as user, I did logout from Xfce4 (as user) and login to Xfce4 again (as user). Then starting neither as root nor as user was possible. dbus process is running as user it seems:

Code:
$ ps aux | grep dbus
message+  6015  0.0  0.0   3000  1088 ?        Ss   Apr01   0:00 /usr/bin/dbus-daemon --system
myuser     23274  0.0  0.0   2352   624 ?        S    Apr04   0:00 /usr/bin/ck-launch-session /usr/bin/dbus-launch --exit-with-session /etc/X11/Sessions/Xfce4
myuser     23307  0.0  0.0   3552   504 ?        S    Apr04   0:00 /usr/bin/dbus-launch --exit-with-session /etc/X11/Sessions/Xfce4
myuser     23308  0.0  0.0   3260  1196 ?        Ss   Apr04   0:00 /usr/bin/dbus-daemon --fork --print-pid 6 --print-address 8 --session
myuser     25310  0.0  0.0   4084   804 pts/1    S+   04:26   0:00 grep --colour=auto dbus


So you mean killing dbus process? Sounds not as a optimal solution to me. This was not necessary in the past.
Back to top
View user's profile Send private message
222697
n00b
n00b


Joined: 07 May 2010
Posts: 51

PostPosted: Fri Apr 12, 2013 5:41 pm    Post subject: Reply with quote

Nobody else? Still not solved for me.
Back to top
View user's profile Send private message
wjb
l33t
l33t


Joined: 10 Jul 2005
Posts: 629
Location: Fife, Scotland

PostPosted: Sat Apr 13, 2013 9:54 am    Post subject: Reply with quote

Try switching to root with "su -" rather than "su"
Back to top
View user's profile Send private message
222697
n00b
n00b


Joined: 07 May 2010
Posts: 51

PostPosted: Sat Apr 13, 2013 3:00 pm    Post subject: Reply with quote

wjb wrote:
Try switching to root with "su -" rather than "su"


Thanks, with that I can start meld as root. Unfortunateley not as user- but that's better than nothing.
Back to top
View user's profile Send private message
wjb
l33t
l33t


Joined: 10 Jul 2005
Posts: 629
Location: Fife, Scotland

PostPosted: Sat Apr 13, 2013 9:23 pm    Post subject: Reply with quote

It works ok in my user account but googling this lot:
Quote:
sl = self._semlock = _multiprocessing.SemLock(kind, value, maxvalue)
OSError: [Errno 13] Permission denied


=> user needs R/W access to /dev/shm required for semaphores to work

I seem to have full access:
Quote:
$ ls -ld /dev/shm
drwxrwxrwt 2 root root 40 2013-04-13 10:49 /dev/shm
Back to top
View user's profile Send private message
222697
n00b
n00b


Joined: 07 May 2010
Posts: 51

PostPosted: Mon Apr 15, 2013 3:55 pm    Post subject: Reply with quote

Me to:
Code:
$ ls -ld /dev/shm
drwxrwxrwt 2 root root 40 15. Apr 17:45 /dev/shm
Back to top
View user's profile Send private message
Joseph_sys
Advocate
Advocate


Joined: 08 Jun 2004
Posts: 2712
Location: Edmonton, AB

PostPosted: Wed Apr 17, 2013 6:22 pm    Post subject: Reply with quote

I'm stuck with the same problem.
Did anybody post a bug about it?
Back to top
View user's profile Send private message
Joseph_sys
Advocate
Advocate


Joined: 08 Jun 2004
Posts: 2712
Location: Edmonton, AB

PostPosted: Fri Apr 19, 2013 12:46 am    Post subject: Reply with quote

I downgraded to dev-util/meld-1.6.0 and this problem went away.

There is a bug about it:
https://bugs.gentoo.org/show_bug.cgi?id=452930
Back to top
View user's profile Send private message
thens
n00b
n00b


Joined: 07 Apr 2012
Posts: 12

PostPosted: Fri Apr 19, 2013 6:55 pm    Post subject: Reply with quote

Hmm, strange, I'm using xfce-4.10 with meld-1.7 (i686 as well as amd64) and I have no problems whatsoever..
I could check certain configurations/settings on my machine if you want me to.
Ahh, my user is in the following groups:
Code:
wheel cdrom video kvm cdrw usb users vboxusers pulse pulse-access plugdev vlock thens

and I haven't changed dbus/policykit settings.
Back to top
View user's profile Send private message
Joseph_sys
Advocate
Advocate


Joined: 08 Jun 2004
Posts: 2712
Location: Edmonton, AB

PostPosted: Fri Apr 19, 2013 7:02 pm    Post subject: Reply with quote

thens wrote:
Hmm, strange, I'm using xfce-4.10 with meld-1.7 (i686 as well as amd64) and I have no problems whatsoever..
I could check certain configurations/settings on my machine if you want me to.
Ahh, my user is in the following groups:
Code:
wheel cdrom video kvm cdrw usb users vboxusers pulse pulse-access plugdev vlock thens

and I haven't changed dbus/policykit settings.


Did you test meld as user or root?
1.7 was working OK as root but it wouldn't start as user.
Back to top
View user's profile Send private message
thens
n00b
n00b


Joined: 07 Apr 2012
Posts: 12

PostPosted: Fri Apr 19, 2013 7:03 pm    Post subject: Reply with quote

Works fine while starting meld as user.
Back to top
View user's profile Send private message
wjb
l33t
l33t


Joined: 10 Jul 2005
Posts: 629
Location: Fife, Scotland

PostPosted: Sun Jul 21, 2013 8:56 am    Post subject: Reply with quote

Just noticed that meld seems to start OK in root if you clear one of the DBUS envs first:
Code:
# unset DBUS_SESSION_BUS_ADDRESS
Back to top
View user's profile Send private message
Display posts from previous:   
Reply to topic    Gentoo Forums Forum Index Desktop Environments All times are GMT
Page 1 of 1

 
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum