This has been uploaded to Feisty a while ago.
** Changed in: update-notifier (Ubuntu)
Status: Fix Committed => Fix Released
--
Provide GUI access to crash reports from root programs
https://launchpad.net/bugs/62316
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.u
Michael, please merge the attached branch and upload whenever you are
ready with your fixes. Thank you!
** Changed in: update-notifier (Ubuntu)
Status: In Progress => Fix Committed
--
Provide GUI access to crash reports from root programs
https://launchpad.net/bugs/62316
--
ubuntu-bugs
apport (0.38) feisty; urgency=low
.
* Add ./COPYING: GPL license.
* debian/rules: Build POT file again.
* apport/fileutils.py: Add get_all_system_reports() and
get_new_system_reports() and added test cases. Now the test suite can also
be run as root to be able to actually check
** Changed in: apport (Ubuntu)
Status: In Progress => Fix Committed
--
Provide GUI access to crash reports from root programs
https://launchpad.net/bugs/62316
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
apport-checkreports will grow an option to check for system reports, but
the gksu'ing should actually be done from update-notifier.
** Also affects: update-notifier (Ubuntu)
Importance: Undecided
Status: Unconfirmed
** Changed in: update-notifier (Ubuntu)
Importance: Undecided => Wis
This has been discussed on u-devel@, and the consensus was:
* Change apport-checkreports to check for the existence of system
crash reports if the user is in 'admin', and have apport-gtk gksu
itself if there is a system crash report it cannot read. This would
be the safe option, but requ
** Summary changed:
- [Synaptic]No notification and report can only be read/write by root
+ Provide GUI access to crash reports from root programs
--
Provide GUI access to crash reports from root programs
https://launchpad.net/bugs/62316
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
