update-manager crashed with SystemExit in exit(): 0

Bug #1203919 reported by Antonio Carlos Santos Galvão
22
This bug affects 2 people
Affects Status Importance Assigned to Milestone
update-manager (Ubuntu)
Fix Released
High
Unassigned
Saucy
Won't Fix
High
Brian Murray

Bug Description

[Impact]
update-manager crashes with SystemExit in exit(): 0.

[Test Case]
Check the errors bucket for this problem, which occurs regularly on Ubuntu 13.10, and see whether or not the error is occurring with the new version of the package.

https://errors.ubuntu.com/problem/2291bc498b77630208b36aca9955c9bf31ae34a2

[Regression Potential]
Adds a defensive if statement to check for None, the fallthrough is to exit the function in the error case.

Original Report
===============
ao encerrar a sessão, da erros diversos inclusive no update-manager.

ProblemType: CrashDistroRelease: Ubuntu 13.10
Package: update-manager 1:0.189
ProcVersionSignature: Ubuntu 3.10.0-4.13-generic 3.10.1
Uname: Linux 3.10.0-4-generic x86_64
ApportVersion: 2.11-0ubuntu1
Architecture: amd64
CrashCounter: 1
Date: Sun Jul 21 14:34:33 2013
ExecutablePath: /usr/bin/update-manager
ExecutableTimestamp: 1373609354
GsettingsChanges:
 b'com.ubuntu.update-manager' b'first-run' b'false'
 b'com.ubuntu.update-manager' b'launch-time' b'1374427853'
InterpreterPath: /usr/bin/python3.3
MarkForUpload: True
PackageArchitecture: all
ProcCmdline: /usr/bin/python3 /usr/bin/update-manager --no-update --no-focus-on-map
ProcCwd: /home/galvao
ProcEnviron:
 LANGUAGE=pt_BR:pt:en
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=pt_BR.UTF-8
 SHELL=/bin/bash
PythonArgs: ['/usr/bin/update-manager', '--no-update', '--no-focus-on-map']SourcePackage: update-manager
Title: update-manager crashed with SystemExit in exit(): 0
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

Related branches

Revision history for this message
Antonio Carlos Santos Galvão (ancasaga) wrote :
tags: removed: need-duplicate-check
Changed in update-manager (Ubuntu):
importance: Undecided → Medium
Revision history for this message
Sebastien Bacher (seb128) wrote :

Thank you for your bug report, that report matches the error bucket on https://errors.ubuntu.com/problem/2291bc498b77630208b36aca9955c9bf31ae34a2

information type: Private → Public
Changed in update-manager (Ubuntu):
importance: Medium → High
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package update-manager - 1:0.196.3

---------------
update-manager (1:0.196.3) trusty; urgency=low

  [ Sebastien Bacher ]
  * lp:~seb128/update-manager/check-none-controller
    - Check for controller being None before using it (this was
      accidentally dropped in a previous refactoring).
    - LP: #1203919
 -- Barry Warsaw <email address hidden> Tue, 10 Dec 2013 17:15:04 -0500

Changed in update-manager (Ubuntu):
status: New → Fix Released
Revision history for this message
Brian Murray (brian-murray) wrote :

This seems worth SRU'ing based off the number of Saucy users affected.

Changed in update-manager (Ubuntu Saucy):
status: New → Triaged
importance: Undecided → High
description: updated
Changed in update-manager (Ubuntu Saucy):
assignee: nobody → Brian Murray (brian-murray)
status: Triaged → In Progress
Revision history for this message
Chris J Arges (arges) wrote : Please test proposed package

Hello Antonio, or anyone else affected,

Accepted update-manager into saucy-proposed. The package will build now and be available at http://launchpad.net/ubuntu/+source/update-manager/1:0.194.2 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance!

description: updated
Changed in update-manager (Ubuntu Saucy):
status: In Progress → Fix Committed
tags: added: verification-needed
Revision history for this message
Rolf Leggewie (r0lf) wrote :

saucy has seen the end of its life and is no longer receiving any updates. Marking the saucy task for this ticket as "Won't Fix".

Changed in update-manager (Ubuntu Saucy):
status: Fix Committed → Won't Fix
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.