** Attachment removed: "83762ADFCB793AB2F73E1CF014368CB9.jpg"
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/652916/+attachment/4908271/+files/83762ADFCB793AB2F73E1CF014368CB9.jpg
** Attachment removed: "FB34CD1FA5A787A4F1506F7D297FDBBB.jpg"
https://bugs.launchpad.net/ubuntu/+sour
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: apport (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/652916
Title:
wron
Looking at this bug and bug 897270 it seems odd to me that the
Traceback.txt doesn't appear in the UbiquitySyslog file at all.
Additionally, looking at all the duplicates the latest version of
ubiquity that this (the traceback disconnect) happened in was version
2.6.10 from Natty and 2.7.10 which i
** Changed in: apport (Ubuntu)
Status: Incomplete => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/652916
Title:
wrong bug duplication - ubiquity-dm crashed with ValueError in
** Changed in: ubiquity (Ubuntu)
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/652916
Title:
wrong bug duplication - ubiquity-dm crashed with ValueError in
comm
All duplicates have exactly the same stack trace, so I guess if they are
unrelated issues we need to look at something else to tell them apart.
Colin/Evan, can you please give me some advice what else to look at
here? Should this particular crash be ignored in general? Should we look
at something i
** Changed in: apport (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/652916
Title:
wrong bug duplication - ubiquity-dm crashed with ValueError in
command():