do-release-upgrade crashed with ValueError in update_interface(): could not convert string to float: '0,0000'

Bug #1611450 reported by Cristian Aravena Romero
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
ubuntu-release-upgrader (Ubuntu)
New
Medium
Unassigned

Bug Description

Upgrade and crash.

ProblemType: Crash
DistroRelease: Ubuntu 16.10
Package: ubuntu-release-upgrader-core 1:16.10.3
Uname: Linux 4.8.0-040800rc1-lowlatency x86_64
ApportVersion: 2.20.3-0ubuntu5
Architecture: amd64
CrashCounter: 1
CrashDB: ubuntu
Date: Tue Aug 9 12:23:01 2016
ExecutablePath: /usr/bin/do-release-upgrade
InstallationDate: Installed on 2015-07-26 (380 days ago)
InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Alpha amd64 (20150723)
InterpreterPath: /usr/bin/python3.5
PackageArchitecture: all
ProcCmdline: /usr/bin/python3 /usr/lib/ubuntu-release-upgrader/do-partial-upgrade --frontend=DistUpgradeViewGtk3
PythonArgs: ['/usr/bin/do-release-upgrade', '--frontend=DistUpgradeViewGtk3']
SourcePackage: ubuntu-release-upgrader
Title: do-release-upgrade crashed with ValueError in update_interface(): could not convert string to float: '0,0000'
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:

VarLogDistupgradeTermlog:

Revision history for this message
Cristian Aravena Romero (caravena) wrote :
Revision history for this message
Apport retracing service (apport) wrote : This bug is a duplicate

Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1593869, 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
Changed in ubuntu-release-upgrader (Ubuntu):
importance: Undecided → Medium
information type: Private → Public
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.