The Notify-OSD log should save at least one copy
Bug #397808 reported by
Ara Pulido
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
notify-osd (Ubuntu) |
Triaged
|
Wishlist
|
Mirco Müller |
Bug Description
Binary package hint: notify-osd
The Notify-OSD log can be very useful when debugging crashing or other application problems.
The problem is that every time that notify-osd daemon starts, the log file is erased and reopen.
So, if notify-osd crashes and then it restarts due to a new notification, there's no way to access the old log. At least a copy of the old one should be saved (something like notify-osd.log.1)
Related branches
tags: | added: testability |
Changed in notify-osd (Ubuntu): | |
importance: | Undecided → Wishlist |
Changed in notify-osd (Ubuntu): | |
status: | New → Triaged |
assignee: | nobody → Mirco Müller (macslow) |
Changed in notify-osd: | |
status: | New → Confirmed |
importance: | Undecided → Wishlist |
Changed in notify-osd: | |
assignee: | nobody → Mirco Müller (macslow) |
tags: | added: patch |
no longer affects: | notify-osd |
To post a comment you must log in.
Simple fix attached