System settings occasionally crashes when trying to open Brightness page
Bug #1583224 reported by
Andrea Bernabei
This bug affects 2 people
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Canonical System Image |
Incomplete
|
High
|
Bill Filler | ||
| ubuntu-system-settings (Ubuntu) |
Invalid
|
High
|
Ken VanDine | ||
Bug Description
Krillin, rc-proposed, r335
System settings occasionally crashes after selecting "Brightness" in the main view.
Here's what I was doing when it happened:
1) Opened system settings
2) Opened Security&
3) go back to main view
4) open Updates
5) go back
6) Open Brightness again
Crash!
I have a .crash file, see attachments for the content. It contains the threads bt as well :)
The behaviour is similar to #1385467 but I was adviced to open a new bug, for the moment
Revision history for this message
| Andrea Bernabei (faenil) wrote | #1 |
| Changed in ubuntu-system-settings (Ubuntu): | |
| importance: | Undecided → High |
| assignee: | nobody → Ken VanDine (ken-vandine) |
| Changed in canonical-devices-system-image: | |
| assignee: | nobody → Bill Filler (bfiller) |
| milestone: | none → 12 |
| importance: | Undecided → High |
Revision history for this message
| Launchpad Janitor (janitor) wrote | #2 |
| Changed in ubuntu-system-settings (Ubuntu): | |
| status: | New → Confirmed |
| Changed in canonical-devices-system-image: | |
| status: | New → Confirmed |
Revision history for this message
| Ken VanDine (ken-vandine) wrote | #3 |
| Changed in ubuntu-system-settings (Ubuntu): | |
| status: | Confirmed → Invalid |
| Changed in canonical-devices-system-image: | |
| status: | Confirmed → Invalid |
Revision history for this message
| Andrea Bernabei (faenil) wrote | #4 |
Revision history for this message
| Jean-Baptiste Lallement (jibel) wrote | #5 |
| Changed in canonical-devices-system-image: | |
| status: | Invalid → Incomplete |
| Changed in canonical-devices-system-image: | |
| milestone: | 12 → none |
To post a comment you must log in.
Status changed to 'Confirmed' because the bug affects multiple users.