This bug report is being closed due to your last comment. For future
reference you can manage the status of your own bugs by clicking on the
current status in the yellow line and then choosing a new status in the
revealed drop down box. You can learn more about bug statuses at [WWW]
It seems like stopping the old mono-xsp service fails.
I could not reproduce it by installing it from gutsy and stopping it.
Do you have manually edited the init script?
Please attach your current /etc/init.d/mono-xsp.
** Changed in: xsp (Ubuntu)
Sourcepackagename: None = xsp
** Changed in:
It seems like stopping the old mono-xsp service fails.
I could not reproduce it by installing it from gutsy and stopping it.
Do you have manually edited the init script?
Please attach your current /etc/init.d/mono-xsp.
I have not manually edited the init script for mono-xsp (or any of
Managed to fix software index.
1) get PID of offending daemon
sudo ps aux | grep -v grep | grep 'xsp.exe' | cut -c 10-15
2) manually kill offending daemon
3) sudo apt-get update
4) sudo apt-get install -f
Still don't understand why the automated update procedure got me into
the bad
I've thought that the 95 in 95: Syntax error: Bad fd number would
refer to the line number in the init script, but it does not.
--
'Software index is broken' after upgrade from Feisty to Gutsy
https://bugs.launchpad.net/bugs/154992
You received this bug notification because you are a member of
