[Python-apps-team] Bug#673336: sonata: KDE launch fails to connect to mpd on local socket
Jonathan Lane
jonathan.w.lane at gmail.com
Thu May 17 22:10:55 UTC 2012
Package: sonata
Version: 1.6.2.1-5
Severity: normal
Dear Maintainer,
I have mpd configured to run as my own user account, running on a local
socket within $HOME. When I launch Sonata from a terminal, or from a
window manager's built in launch feature (Window Maker and e17,
specifically), it connects properly. When launched from KDE's "Kickoff"
start menu or its equivalent of the window managers' run dialogues,
Sonata fails to connect, and even selecting the default connection
profile through the right-click menu, which works in every other window
manager I've tried, does not work in KDE, even with the "--profile=1"
flag. When I launch Sonata from Konsole within KDE, it still works
properly. This bug is filed against Sonata because it appears to be
inheriting its profiles incorrectly.
Jonathan Lane
-- System Information:
Debian Release: wheezy/sid
APT prefers unstable
APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 3.2.0-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages sonata depends on:
ii python 2.7.2-10
ii python-dbus 0.84.0-3
ii python-gtk2 2.24.0-3
ii python-mpd 0.3.0-4
ii python2.6 2.6.7-4
ii python2.7 2.7.3~rc2-2.1
Versions of packages sonata recommends:
ii python-eggtrayicon 2.25.3-11
ii python-tagpy 0.94.8-3+b1
Versions of packages sonata suggests:
pn python-mmkeys <none>
-- no debconf information
More information about the Python-apps-team
mailing list