Ubuntu
wine package

Configure Wine application crashed when it was open

Bug #474427 reported by Thiago on 2009-11-04

This bug report is a duplicate of: Bug #447197: Packages with custom /etc/sysctl.d/30-foo.conf files can fail to install: start procps returns exit status 1. Edit Remove

This bug affects 2 people

Affects		Status	Importance	Assigned to	Milestone
	wine (Ubuntu)	Confirmed	Undecided	Unassigned

Bug Description

Binary package hint: wine

Description: Ubuntu 9.10
Release: 9.10

wine:
  Installed: 1.0.1-0ubuntu8
  Candidate: 1.0.1-0ubuntu8
  Version table:
*** 1.0.1-0ubuntu8 0
        500 http://archive.ubuntu.com karmic/universe Packages
        100 /var/lib/dpkg/status

When I tried to open "Configure Wine" application for the first time it crashed.

ProblemType: Package
Architecture: i386
Date: Wed Nov 4 15:04:07 2009
DistroRelease: Ubuntu 9.10
ErrorMessage: subprocess installed post-installation script returned error exit status 255
NonfreeKernelModules: vmnet vmci vmmon
Package: wine 1.0.1-0ubuntu8
ProcVersionSignature: Ubuntu 2.6.31-14.48-generic
SourcePackage: wine
Title: package wine 1.0.1-0ubuntu8 failed to install/upgrade: subprocess installed post-installation script returned error exit status 255
Uname: Linux 2.6.31-14-generic i686

Tags:

Revision history for this message

Thiago (tclahr) wrote on 2009-11-04:

AptOrdering.txt Edit (107 bytes, text/plain; charset="utf-8")
Dependencies.txt Edit (2.2 KiB, text/plain; charset="utf-8")
Dmesg.txt Edit (87.1 KiB, text/plain; charset="utf-8")
DpkgTerminalLog.gz Edit (5.4 KiB, application/x-gzip)

Revision history for this message

Jean-Baptiste Lallement (jibel) wrote on 2010-03-16:

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 447197, 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.