recoverable problem crash files created which whoopsie cannot read
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
apport (Ubuntu) |
Invalid
|
High
|
Unassigned |
Bug Description
I've seen it happen that recoverable problems are created that whoopsie has no permission to read and subsequently cannot upload the crash file to the error tracker.
root@ubuntu-
total 380K
-rw-r----- 1 phablet whoopsie 262K Aug 25 14:20 _usr_bin_
-rw-r--r-- 1 phablet nopasswdlogin 0 Aug 25 14:20 _usr_bin_
-rw------- 1 whoopsie nopasswdlogin 0 Aug 25 14:20 _usr_bin_
-rw-r----- 1 phablet nopasswdlogin 93K Aug 25 15:00 _usr_share_
-rw-r--r-- 1 phablet nopasswdlogin 0 Aug 25 15:00 _usr_share_
-rw------- 1 whoopsie nopasswdlogin 0 Aug 25 15:00 _usr_share_
And in /var/log/
Parsing /var/crash/
lib_arm-
^M
(whoopsie:2309): GLib-CRITICAL **: g_mapped_
failed^M
Unable to parse report (/var/crash/
manager_
map report: Failed to open file '/var/crash/
untu.filemanage
pen() failed: Permission denied^M
Changed in apport (Ubuntu): | |
importance: | Undecided → High |
tags: | added: utopic |
Changed in apport (Ubuntu): | |
status: | New → Invalid |
This is reproducable by clicking on any image in the File Manager.
root@ubuntu- phablet: ~# system-image-cli -i touch/utopic- proposed
current build number: 207
device name: mako
channel: ubuntu-
last update: 2014-08-25 10:38:50
version version: 207
version ubuntu: 20140825
version device: 20140811.1