crash files from guest users considered system reports
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
apport (Ubuntu) |
Fix Released
|
Low
|
Martin Pitt | ||
Saucy |
Fix Released
|
Medium
|
Brian Murray |
Bug Description
[Impact]
Users are notified of crashes from guests users indicating that they are system crashes, which they are then unable to report which results in a bad user experience.
[Test Case]
1) log in to your system as your regular user
2) from your session switch to a guest session
3) open a terminal
4) run 'xeyes &'
5) run 'pkill -11 xeyes'
6) wait for a crash dialog
7) switch to your regular session
8) observe a notification regarding a system crash report, click to report it
9) enter your password
10) observe nothing else happens
With the version of apport from saucy-proposed you should not receive a crash notification.
[Regression Potential]
Little as we are explicitly filter on crashes where the username starts with guest.
If a guest user experiences a crash on an Ubuntu system it is reported as a system crash by apport/fileutils.py (because the guest user id is less than 500). Subsequently, a crash notification dialog appears on the guest user's session and on the primary user's session (if they are logged in). However, when you go to actually file the report (as the primary user) nothing happens.
Regardless, I wonder if get_all_
Related branches
tags: | added: saucy |
Changed in apport (Ubuntu): | |
status: | Triaged → In Progress |
description: | updated |
Changed in apport (Ubuntu Saucy): | |
status: | Triaged → In Progress |
assignee: | nobody → Brian Murray (brian-murray) |
The notification is raised by /usr/share/ apport/ apport- checkreports --system.