The permissions in the CrashReports: field in the description are
correct. The only way that I see this could happen is that a new crash
report is being generated by a background apport instance (which will
set the file to permissions zero while writing), while the first report
is being processed. I'm afraid I cannot do much more in this case than
just aborting gracefully.
** Changed in: apport (Ubuntu)
Status: Confirmed => Triaged
** Changed in: apport (Ubuntu)
Importance: High => Low
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/949196
Title:
apport-gtk crashed with IOError in thread_collect_info(): [Errno 13]
Access denied: '/var/crash/_usr_bin_nautilus-actions-config-
tool.1000.crash'
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/949196/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
