Right, as Ubiquity is not installed in the target system, it cannot
determine the package status/files/version/etc. I'm not keen on running
apt-get update in apport, as that can take a long time (or not work at
all if you are offline), and feels wrong to me. However, we could teach
it to special-case ubiquity to send log files etc. even when ubiquity is
not installed any more.
I don't think we want to try and forge the apt lists in Ubiquity;
creating them should be apt's job the first time the computer is online
in my opinion, so I tentatively set the ubiquity task to wont fix.
** Changed in: ubiquity (Ubuntu)
Status: New => Won't Fix
** Summary changed:
- Cannot file a bug using apport after performing offline installation
+ Cannot file an ubiquity bug using apport after performing offline installation
** Project changed: apport => apport (Ubuntu)
** Changed in: apport (Ubuntu)
Importance: Undecided => Low
** Changed in: apport (Ubuntu)
Status: New => Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1050569
Title:
Cannot file an ubiquity bug using apport after performing offline
installation
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1050569/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
