The Notify-OSD log should save at least one copy

Bug #397808 reported by Ara Pulido on 2009-07-10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
notify-osd (Ubuntu)
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)

Ara Pulido (ara) on 2009-07-20
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)
Neil J. Patel (njpatel) on 2009-08-18
Changed in notify-osd:
status: New → Confirmed
importance: Undecided → Wishlist
Mirco Müller (macslow) on 2009-10-01
Changed in notify-osd:
assignee: nobody → Mirco Müller (macslow)
John Ledbetter (john-ledbetter) wrote :

Simple fix attached

John Ledbetter (john-ledbetter) wrote :

Apologies, actual fix attached this time.

tags: added: patch
Didier Roche (didrocks) wrote :

Thanks a lot for your patch and work there :)
unsuscribing the sponsor team and asked to upstream (Mirco, assigned here) to directly review it.

Mirco Müller (macslow) wrote :

John, this looks ok. I you can merge-propose it, I'll approve and merge it to trunk.

Sebastien Bacher (seb128) wrote :

John, could you do a merge request for it?

no longer affects: notify-osd
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers