Ubuntu
notify-sharp package

package libnotify0.4-cil 0.4.0~r3032-2ubuntu1 failed to install/upgrade: Paket libnotify0.4-cil ist schon installiert und konfiguriert

Bug #632799 reported by Nils Kunkel on 2010-09-08

This bug report is a duplicate of: Bug #541595: [Master] package failed to install/upgrade: package is already installed and configured. Edit Remove

This bug affects 1 person

Affects		Status	Importance	Assigned to	Milestone
	notify-sharp (Ubuntu)	New	Undecided	Unassigned

Bug Description

Problem came after the using of "Rechner Hausmeister"

ProblemType: Package
DistroRelease: Ubuntu 10.04
Package: libnotify0.4-cil 0.4.0~r3032-2ubuntu1
ProcVersionSignature: Ubuntu 2.6.32-22.36-generic 2.6.32.11+drm33.2
Uname: Linux 2.6.32-22-generic x86_64
NonfreeKernelModules: fglrx
Architecture: amd64
Date: Wed Sep 8 02:04:54 2010
ErrorMessage: Paket libnotify0.4-cil ist schon installiert und konfiguriert
InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release amd64 (20100429)
PackageArchitecture: all
SourcePackage: notify-sharp
Title: package libnotify0.4-cil 0.4.0~r3032-2ubuntu1 failed to install/upgrade: Paket libnotify0.4-cil ist schon installiert und konfiguriert

Tags:

Revision history for this message

Nils Kunkel (nilskunkel3) wrote on 2010-09-08:

AptOrdering.txt Edit (327 bytes, text/plain; charset="utf-8")
Dependencies.txt Edit (2.8 KiB, text/plain; charset="utf-8")
Df.txt Edit (460 bytes, text/plain; charset="utf-8")
Dmesg.txt Edit (59.2 KiB, text/plain; charset="utf-8")
DpkgTerminalLog.txt Edit (25.6 KiB, text/plain; charset="utf-8")

Brian Murray (brian-murray) on 2010-09-09

affects:

ubuntu → notify-sharp (Ubuntu)

Revision history for this message

Brian Murray (brian-murray) wrote on 2011-07-27:

Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 541595, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.