twistd crashed with CannotListenError in startListening()

[Blake Munro]

I currently have 2x 22" Dell widescreen flat panels with an Nvidia 9600GT video card.

I have configured Twinview. All of a sudden after running an apt-get upgrade one day this bug has been occurring, and my 2nd monitor is no longer working (even though it shows it as being configured and enabled in nvidia-settings).

I am running Jaunty Alpha 6 + all updates that have been released since then, so I guess I am running Jaunty Beta now.

blake@starmax:~$ lsb_release -rd
Description: Ubuntu jaunty (development branch)
Release: 9.04

I have no further information at this time but am happy to provide it if requested.

ProblemType: Crash
Architecture: amd64
DistroRelease: Ubuntu 9.04
ExecutablePath: /usr/bin/twistd
InterpreterPath: /usr/bin/python2.6
NonfreeKernelModules: nvidia
Package: python-twisted-core 8.2.0-1ubuntu1
PackageArchitecture: all
ProcAttrCurrent: unconfined
ProcCmdline: apt-proxy /usr/bin/twistd --originalname --pidfile=/var/run/apt-proxy//apt-proxy.pid --rundir=/var/run/apt-proxy/ --python=/usr/sbin/apt-proxy --logfile=/var/log/apt-proxy.log --no_save
ProcEnviron: PATH=(custom, no user)
PythonArgs: ['/usr/bin/twistd', '--originalname', '--pidfile=/var/run/apt-proxy//apt-proxy.pid', '--rundir=/var/run/apt-proxy/', '--python=/usr/sbin/apt-proxy', '--logfile=/var/log/apt-proxy.log', '--no_save']
SourcePackage: twisted
Title: twistd crashed with CannotListenError in startListening()
Uname: Linux 2.6.28-11-generic x86_64
UserGroups: mythtv

[Blake Munro (blake-munro)]

I just noticed after submitting this bug that there were a bunch of errors with apt-proxy. I have uninstalled apt-proxy for now (since I had not had time to correctly configure it anyway just yet) and monitor the error to see if it keeps happening or not.

[Blake Munro (blake-munro)]

After uninstalling apt-proxy and restarting my PC, the problem seems to have gone away completely. I will continue to monitor however and advise if it comes back.

Can anyone else who uses TwinView (and nvidia-settings) confirm this bug by installing apt-proxy and restarting their PC? You don't need to configure apt-proxy nor should it interfere with anything else, but it would be good just to test to see if there is a conflict between the two packages.

I had planned to set up apt-proxy but if it is going to cause graphics issues then I'd like to get to the root cause of the conflicts/bugs so that both applications can be run on the same machine.

Thanks

[Blake Munro (blake-munro)]

After a bit of quick research it appears that apt-proxy uses a default TCP port of 9999. Can anyone confirm if and why my Nvidia graphics card would be likely to be trying to use that port as well in order to run TwinView?

At least I know now that if I want to run apt-proxy, I need to configure it to a different port, eg 9998 so it does not conflict.

[Brian Murray (brian-murray)]

The port already being used shouldn't cause a crash.