Ubuntu
update-manager package

check-new-release-gtk crashed with IOError in _buildMetaReleaseFile() when homedir is not writable.

Bug #704045 reported by Daniel Richard G. on 2011-01-17

This bug report is a duplicate of: Bug #686091: check-new-release-gtk crashed with IOError in _buildMetaReleaseFile(). Edit Remove

This bug affects 1 person

Affects		Status	Importance	Assigned to	Milestone
	update-manager (Ubuntu)	Confirmed	Low	Unassigned

Bug Description

Binary package hint: update-manager

I see this crash on a system in which my home directory is served out of AFS. The crash occurs when my Kerberos authentication has expired, and thus $HOME is inaccessible with EACCES.

ProblemType: Crash
DistroRelease: Ubuntu 10.10
Package: update-manager 1:0.142.20
ProcVersionSignature: Ubuntu 2.6.35-24.42-generic 2.6.35.8
Uname: Linux 2.6.35-24-generic x86_64
NonfreeKernelModules: openafs
Architecture: amd64
Date: Sun Jan 16 15:28:53 2011
ExecutablePath: /usr/lib/update-manager/check-new-release-gtk
InterpreterPath: /usr/bin/python2.6
PackageArchitecture: all
ProcCmdline: /usr/bin/python2.6 /usr/lib/update-manager/check-new-release-gtk
ProcEnviron:
PATH=(custom, no user)
LANG=en_US.UTF-8
SHELL=/bin/bash
PythonArgs: ['/usr/lib/update-manager/check-new-release-gtk']
SourcePackage: update-manager
Title: check-new-release-gtk crashed with IOError in _buildMetaReleaseFile()
UserGroups: adm audio cdrom dialout floppy plugdev video

Tags:

Revision history for this message

Daniel Richard G. (skunk) wrote on 2011-01-17:

Traceback.txt Edit (786 bytes, text/plain; charset="utf-8")

visibility:

private → public

Revision history for this message

Jean-Baptiste Lallement (jibel) wrote on 2011-01-17:

I confirm this but I'm not sure that the bug is valid because the failure is intended since we can't neither write to the global location nor to the home directory.

I'll let the developer decide whether the status is invalid or if there is another option.

summary:	check-new-release-gtk crashed with IOError in _buildMetaReleaseFile() + when homedir is not writable.
Changed in update-manager (Ubuntu):
importance:	Undecided → Low
status:	New → Confirmed

Revision history for this message

Daniel Richard G. (skunk) wrote on 2011-01-17:

Well, the program can at least give up gracefully in that scenario, rather than crashing.

There have been occasions in the past where update-manager apparently ran multiple times without homedir access, and I would come back to my workstation in the morning and find literally dozens of Apport dialogs for u-m sitting on top of one another.

Revision history for this message

Apport retracing service (apport) wrote on 2011-01-25: This bug is a duplicate

Thank you for taking the time to report this crash and helping to make Ubuntu better. This particular crash has already been reported and is a duplicate of bug #686091, so 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.

tags:

removed: need-duplicate-check