[Bug 847174] Re: update-manager crashed with TypeError in confirmChanges(): glib.markup_escape_text() takes at most 1 argument (2 given)

Apport retracing service 847174 at bugs.launchpad.net
Sun Sep 11 16:40:25 UTC 2011


*** This bug is a duplicate of bug 832745 ***
    https://bugs.launchpad.net/bugs/832745

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 #842392, 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

** Attachment removed: "Dependencies.txt"
   https://bugs.launchpad.net/bugs/847174/+attachment/2387157/+files/Dependencies.txt

** Attachment removed: "ProcMaps.txt"
   https://bugs.launchpad.net/bugs/847174/+attachment/2387158/+files/ProcMaps.txt

** Attachment removed: "ProcStatus.txt"
   https://bugs.launchpad.net/bugs/847174/+attachment/2387159/+files/ProcStatus.txt

** This bug has been marked a duplicate of bug 832745
   TypeError: glib.markup_escape_text() takes at most 1 argument (2 given)

** Visibility changed to: Public

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to update-manager in Ubuntu.
https://bugs.launchpad.net/bugs/847174

Title:
  update-manager crashed with TypeError in confirmChanges():
  glib.markup_escape_text() takes at most 1 argument (2 given)

Status in “update-manager” package in Ubuntu:
  New

Bug description:
  I upgraded to Oneiric a week or two ago.  Sometime later, I started
  getting notifications about a problem with a system program having
  been detected after logging in.  Usually, when I tried to report that
  problem, apport itself crashed, but after installing some updates
  today, it was apparently able to go through.  The crash data suggests
  that the automated run of update-manager is failing.  I have noticed
  that I have to run update-manager manually if I want to update; the
  crash seems like the most likely cause.

  update-manager does not crash if I run it manually.  There must be
  something different about the automated run that triggers the crash.

  
  Expected behavior:  update-manager runs after login without crashing.

  Observed behavior:  update-manager runs after login, but crashes.

  
  In case it's not in the bug data, apt-cache says I'm running update-manager 1:0.152.17.

  ProblemType: Crash
  DistroRelease: Ubuntu 11.10
  Package: update-manager 1:0.152.17
  ProcVersionSignature: Ubuntu 3.0.0-9.15-generic 3.0.3
  Uname: Linux 3.0.0-9-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 1.22.1-0ubuntu2
  Architecture: amd64
  Date: Sun Sep 11 10:53:59 2011
  ExecutablePath: /usr/bin/update-manager
  InterpreterPath: /usr/bin/python2.7
  PackageArchitecture: all
  ProcCmdline: /usr/bin/python /usr/bin/update-manager --dist-upgrade
  ProcEnviron:
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  PythonArgs: ['/usr/bin/update-manager', '--dist-upgrade']
  SourcePackage: update-manager
  Title: update-manager crashed with TypeError in confirmChanges(): glib.markup_escape_text() takes at most 1 argument (2 given)
  UpgradeStatus: Upgraded to oneiric on 2011-09-11 (0 days ago)
  UserGroups:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/847174/+subscriptions




More information about the foundations-bugs mailing list