notified of crash reports which you do not have permission to read and submit
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
update-notifier (Ubuntu) |
Fix Released
|
High
|
Brian Murray | ||
Saucy |
Fix Released
|
High
|
Brian Murray |
Bug Description
Impact:
Users are notified of crash files for which they do not have permission to read, subsequently they can see odd "permission denied" dialogs which creates an unpleasant experience.
Test Case:
1) Create a second user
2) Log out as your regular user
3) Login as this second user
4) In a terminal run 'xeyes &'
5) In a terminal run 'pkill -11 xeyes'
6) Close resulting crash dialog (do not send it)
7) Log out as second user
8) Log in as your regular user
9) As your regular user install d-feet
10) In a terminal run 'd-feet &'
11) In a terminal run 'pkill -11 d-feet'
12) Close resulting crash dialog (do not send it)
13) Log out
14) In a virtual terminal modify both crash files (xeyes and d-feet) in
/var/crash by adding a second to the Date: field in each crash file. This
causes the upstart job to think they are new again.
15) Log in as your regular user and observe two crash notifications, one will
be for d-feet the other will be a "Permission denied" dialog.
With the package version from -proposed you will only receive one crash
dialog.
Regression Potential:
As this changes the upstart job for crash notification's a fair bit its possible that some crashes will not be reported.
A dialoge message is constantly coming up saying that a problem with ubuntu has occured. When I click send details, another error comes up saying: This problem report is damaged and cannot be processed.
PermissionError(13, 'Permission denied')
No other information is given.
Related branches
- Dennis Kaarsemaker: Pending requested
- Diff: 0 lines
affects: | ubuntu → apport (Ubuntu) |
summary: |
- invalid problem report + notified of crash reports which you do not have permission to read and + submit |
affects: | apport (Ubuntu) → update-notifier (Ubuntu) |
Changed in update-notifier (Ubuntu): | |
status: | New → Triaged |
importance: | Undecided → High |
Changed in update-notifier (Ubuntu): | |
assignee: | nobody → Brian Murray (brian-murray) |
status: | Triaged → In Progress |
Changed in update-notifier (Ubuntu Saucy): | |
status: | New → Triaged |
importance: | Undecided → High |
description: | updated |
description: | updated |
Changed in update-notifier (Ubuntu Saucy): | |
status: | Triaged → In Progress |
assignee: | nobody → Brian Murray (brian-murray) |
tags: |
added: verification-done removed: verification-needed |
Thank you for taking the time to report this bug and helping to make Ubuntu better. It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general. It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it. You can find some hints about determining what package your bug might be about at https:/ /wiki.ubuntu. com/Bugs/ FindRightPackag e. You might also ask for help in the #ubuntu-bugs irc channel on Freenode.
To change the source package that this bug is filed about visit https:/ /bugs.launchpad .net/ubuntu/ +bug/1193509/ +editstatus and add the package name in the text box next to the word Package.
[This is an automated message. I apologize if it reached you inappropriately; please just reply to this message indicating so.]