Include logs, monitors.xml and org.gnome.desktop.* settings in the apport-retrace data
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
gnome-shell (Ubuntu) |
Fix Released
|
Medium
|
Marco Trevisan (Treviño) | ||
Disco |
Fix Released
|
Medium
|
Marco Trevisan (Treviño) |
Bug Description
[ Description ]
When the shell crashes missing relevant shell data is not attached.
[ Test case ]
Run:
$ ubuntu-bug --save=
It should return non-empty strings such as:
grep "monitors\
SHELL=/bin/bash
RelatedPackageV
ShellJournal:
-- Logs begin at Fri 2018-11-16 19:45:37 CET, end at Fri 2019-06-28 13:46:01 CEST. --
[306535.951329] tricky gnome-shell[13215]: [AppIndicatorSu
--
UpgradeStatus: Upgraded to disco on 2019-06-20 (8 days ago)
_MarkForUpload: True
monitors.xml:
<monitors version="2">
<configuration>
While monitors.xml: stuff is optional (depending on the presence of the file), the other fields should always be there.
[ Regression potential ]
Nothing know, it won't in anyway affect the shell behavior
---
When a bug is submitted to ubuntu about gnome-shell it would be convenient to have such settings.
Monitors.xml is quite important to understand the configuration for mutter-related crashes, while other desktop settings (to be filtered-out) could be needed too.
Ah, also the logs from
journalctl /usr/bin/
Proposed fix at https:/
description: | updated |
summary: |
- Include monitors.xml and org.gnome.desktop.* settings in the apport- - retrace data + Include logs, monitors.xml and org.gnome.desktop.* settings in the + apport-retrace data |
description: | updated |
Changed in gnome-shell (Ubuntu): | |
assignee: | Didier Roche (didrocks) → nobody |
Changed in gnome-shell (Ubuntu): | |
assignee: | nobody → Marco Trevisan (Treviño) (3v1n0) |
status: | Confirmed → In Progress |
description: | updated |
Changed in gnome-shell (Ubuntu Disco): | |
status: | New → Fix Committed |
importance: | Undecided → Medium |
assignee: | nobody → Marco Trevisan (Treviño) (3v1n0) |
I'm not sure monitors.xml is any more useful than the xrandr output we already get... unless xrandr output is missing from crash bugs?