package noip2 2.1.7-7ubuntu1 failed to install/upgrade:

Bug #239741 reported by Nathan Adams
This bug report is a duplicate of:  Bug #222408: Error during Hardy install. Edit Remove
4
Affects Status Importance Assigned to Milestone
no-ip (Ubuntu)
Incomplete
Undecided
Unassigned

Bug Description

Binary package hint: no-ip

The following error messages were generated:

--error msg 1---------------------------------------

Could not install 'noip2'

subprocess post-installation script returned error exist status 1

--error msg 2---------------------------------------

Could not install 'no-ip'

dependency problems - leaving unconfigured

--error msg 3---------------------------------------

Invalid problem report

This problem report does not apply to a package program. (/usr/lib/firefox/firefox-bin)

Generation complete.
 * Reloading GNOME Display Manager configuration...
 * Changes will take effect when all current X sessions have ended.
   ...done.

Processing triggers for libc6 ...
ldconfig deferred processing now taking place
Processing triggers for initramfs-tools ...
update-initramfs: Generating /boot/initrd.img-2.6.24-18-generic
Errors were encountered while processing:
 noip2
 no-ip
Traceback (most recent call last):
  File "logging/__init__.py", line 753, in emit
    self.flush()
  File "logging/__init__.py", line 731, in flush
    self.stream.flush()
IOError: [Errno 9] Bad file descriptor
Traceback (most recent call last):
  File "logging/__init__.py", line 753, in emit
    self.flush()
  File "logging/__init__.py", line 731, in flush
    self.stream.flush()
IOError: [Errno 9] Bad file descriptor
Traceback (most recent call last):
  File "logging/__init__.py", line 753, in emit
    self.flush()
  File "logging/__init__.py", line 731, in flush
    self.stream.flush()
IOError: [Errno 9] Bad file descriptor

ProblemType: Package
Architecture: amd64
Date: Fri Jun 13 08:35:33 2008
DistroRelease: Ubuntu 8.04
ErrorMessage:
 ErrorMessage: subprocess post-installation script returned error exit status 1
NonfreeKernelModules: nvidia
Package: noip2 2.1.7-7ubuntu1
PackageArchitecture: amd64
SourcePackage: no-ip
Title: package noip2 2.1.7-7ubuntu1 failed to install/upgrade:
Uname: Linux 2.6.22-14-generic x86_64

Revision history for this message
Nathan Adams (nadams) wrote :
Revision history for this message
Nathan Adams (nadams) wrote :
Revision history for this message
Nathan Adams (nadams) wrote :
Revision history for this message
Nathan Adams (nadams) wrote :

nate@nereidum:$ sudo dpkg --configure -a
[sudo] password for nate:
Setting up noip2 (2.1.7-7ubuntu1) ...
 Both -u and -p options must be used together.
dpkg: error processing noip2 (--configure):
 subprocess post-installation script returned error exit status 1
dpkg: dependency problems prevent configuration of no-ip:
 no-ip depends on noip2; however:
  Package noip2 is not configured yet.
dpkg: error processing no-ip (--configure):
 dependency problems - leaving unconfigured
Errors were encountered while processing:
 noip2
 no-ip

Revision history for this message
Nathan Adams (nadams) wrote :

See also bug #239743

Revision history for this message
Nathan Adams (nadams) wrote :

I removed 'noip2' and 'no-ip' via the Synaptic Package Manager and then successfully re-ran the dpkg command above.

I'm going to attempt to reboot now. If I don't post here again in the next hour... catastrophe. :(

Revision history for this message
Dimitrios Symeonidis (azimout) wrote :

It seems that the problem is this:
"no-ip depends on noip2; however: Package noip2 is not configured yet."

no-ip is a transitional package for noip2, so it can safely be removed. The upgrade process should remove it...

Revision history for this message
Nathan Adams (nadams) wrote :

The reboot went fine; all is well.

As a temporary work-around, I would consider having the upgrade program uninstall no-ip and noip2 if detected. It would, of course, need to notify the user.

Revision history for this message
Cesare Tirabassi (norsetto) wrote :

>Both -u and -p options must be used together

The program was not configured correctly, probably a blank username or password (see bug 222408).

Changed in no-ip:
status: New → Incomplete
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers