ncmpcpp in artful fails to connect

Bug #1734839 reported by Petter Adsen
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
ncmpcpp (Ubuntu)
New
Undecided
Unassigned

Bug Description

ncmpcpp:
  Installed: 0.7.4-1build3
  Candidate: 0.7.4-1build3
  Version table:
 *** 0.7.4-1build3 500
        500 http://no.archive.ubuntu.com/ubuntu artful/universe amd64 Packages
        100 /var/lib/dpkg/status

When I start ncmpcpp, I am met with the message "ncmpcpp: connection refused", but there is no sign of this in mpd.log on the server. On my zesty machine it works perfectly, even though it is using the same version of the package, and both are using the exact same config file (copied across with scp). Other mpd clients like gmpc works fine from the artful machine.

The really weird thing is that if I launch it with 'ncmpcpp -h hostname -p 6600' it works.

I have double- and triple-checked the config file, including rewriting it all by hand and removing everything non-essential. I also tried upgrading to v0.8.1 from https://launchpad.net/~aguignard/+archive/ubuntu/ppa, but that gives the same result.

The only thing I can think of is that something must have changed from zesty to artful to cause this, but it's beyond me to figure out what. Something in the dependencies (libbost?), maybe.

Should I file this upstream, or is there something else I can try? I really want to avoid switching to another mpd client.

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: ncmpcpp 0.7.4-1build3
ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
Uname: Linux 4.13.0-16-generic x86_64
ApportVersion: 2.20.7-0ubuntu3.5
Architecture: amd64
CurrentDesktop: XFCE
Date: Tue Nov 28 09:56:15 2017
InstallationDate: Installed on 2017-10-18 (40 days ago)
InstallationMedia: Xubuntu 17.10 "Artful Aardvark" - Release amd64 (20171017.1)
SourcePackage: ncmpcpp
UpgradeStatus: No upgrade log present (probably fresh install)

Revision history for this message
Petter Adsen (ducasse) wrote :
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.