| 2009-03-10 21:34:58 |
Kees Cook |
bug |
|
|
added bug |
| 2009-03-10 21:35:36 |
Kees Cook |
bug |
|
|
added attachment 'kerneloops-notify-good.jpg' (kerneloops-notify-good.jpg) |
| 2009-03-10 21:36:03 |
Kees Cook |
bug |
|
|
added attachment 'kerneloops-notify-bad.jpg' (kerneloops-notify-bad.jpg) |
| 2009-03-10 21:41:42 |
Kees Cook |
notify-osd: status |
New |
Confirmed |
|
| 2009-03-10 21:41:42 |
Kees Cook |
notify-osd: importance |
Undecided |
High |
|
| 2009-03-10 21:41:42 |
Kees Cook |
notify-osd: statusexplanation |
|
This is blocking bug 327819 (the kerneloops MIR) since it makes kerneloops difficult to test. |
|
| 2009-03-10 21:41:42 |
Kees Cook |
notify-osd: milestone |
|
ubuntu-9.04-beta |
|
| 2009-03-10 21:42:41 |
Kees Cook |
bug |
|
|
added subscriber Brian Murray |
| 2009-03-10 21:42:53 |
Kees Cook |
bug |
|
|
added subscriber Matt Zimmerman |
| 2009-03-10 21:43:16 |
Kees Cook |
bug |
|
|
added subscriber Tim Gardner |
| 2009-03-11 10:41:36 |
Martin Pitt |
notify-osd: bugtargetdisplayname |
notify-osd (Ubuntu Jaunty) |
kerneloops (Ubuntu Jaunty) |
|
| 2009-03-11 10:41:36 |
Martin Pitt |
notify-osd: bugtargetname |
notify-osd (Ubuntu Jaunty) |
kerneloops (Ubuntu Jaunty) |
|
| 2009-03-11 10:41:36 |
Martin Pitt |
notify-osd: statusexplanation |
This is blocking bug 327819 (the kerneloops MIR) since it makes kerneloops difficult to test. |
|
|
| 2009-03-11 10:41:36 |
Martin Pitt |
notify-osd: title |
Bug #340773 in notify-osd (Ubuntu Jaunty): "kerneloops notifications crippled, fails to file" |
Bug #340773 in kerneloops (Ubuntu Jaunty): "kerneloops notifications crippled, fails to file" |
|
| 2009-03-11 14:38:15 |
Matthew Paul Thomas |
bug |
|
|
assigned to notify-osd (Ubuntu) |
| 2009-03-11 14:47:04 |
Mirco Müller |
notify-osd: status |
New |
Invalid |
|
| 2009-03-11 14:47:04 |
Mirco Müller |
notify-osd: assignee |
|
macslow |
|
| 2009-03-11 14:47:04 |
Mirco Müller |
notify-osd: statusexplanation |
|
kerneloops is not using libnotify according to the spec (jaunty one and galago one). Thus I mark this bug-report as invalid. To get examples (in C, C# and Python) and guidelines for how to design the patch to kerneloops to use notifications correctly be sure to check https://wiki.ubuntu.com/NotificationDevelopmentGuidelines https://wiki.ubuntu.com/NotificationDesignGuidelines. |
|
| 2009-03-11 14:53:11 |
Matthew Paul Thomas |
description |
Binary package hint: notify-osd
The notification window from kerneloops is crippled by notify-osd, which means kernel crashes are neither being reported upstream nor being passed to apport for LP filing. Attaching the window when using notification-daemon, and the window when using notify-osd... |
The notification window from kerneloops is crippled by notify-osd, which means kernel crashes are neither being reported upstream nor being passed to apport for LP filing.
The functions that should be available: http://launchpadlibrarian.net/23735662/kerneloops-notify-good.jpg
What actually happens: http://launchpadlibrarian.net/23735670/kerneloops-notify-bad.jpg
This is a high-importance bug in Notify OSD: as shown in <https://wiki.ubuntu.com/NotifyOSD#org.freedesktop.Notifications.Notify>, fallback alert boxes should be showing all the actions that were supplied to the notification, not just two of them.
It is also something that should be fixed in kerneloops: As mentioned in <https://wiki.ubuntu.com/NotifyOSD#kerneloops>, kerneloops should be using a custom alert box anyway rather than a notification. (This would improve on the fallback alert in that it would no longer have an "OK" button that did nothing exactly like the "Cancel" button.) |
|
| 2009-03-11 15:00:46 |
Matthew Paul Thomas |
notify-osd: status |
Invalid |
New |
|
| 2009-03-11 15:00:46 |
Matthew Paul Thomas |
notify-osd: statusexplanation |
kerneloops is not using libnotify according to the spec (jaunty one and galago one). Thus I mark this bug-report as invalid. To get examples (in C, C# and Python) and guidelines for how to design the patch to kerneloops to use notifications correctly be sure to check https://wiki.ubuntu.com/NotificationDevelopmentGuidelines https://wiki.ubuntu.com/NotificationDesignGuidelines. |
Mirco, this is a bug in Notify OSD regardless of whether kerneloops is checking the capabilities correctly. As long as Notify OSD makes kerneloops useless, it'll also be making useless a chunk of the other unknown applications for which Notify OSD has fallback alert boxes in the first place. |
|
| 2009-03-11 17:29:55 |
Matthew Paul Thomas |
description |
The notification window from kerneloops is crippled by notify-osd, which means kernel crashes are neither being reported upstream nor being passed to apport for LP filing.
The functions that should be available: http://launchpadlibrarian.net/23735662/kerneloops-notify-good.jpg
What actually happens: http://launchpadlibrarian.net/23735670/kerneloops-notify-bad.jpg
This is a high-importance bug in Notify OSD: as shown in <https://wiki.ubuntu.com/NotifyOSD#org.freedesktop.Notifications.Notify>, fallback alert boxes should be showing all the actions that were supplied to the notification, not just two of them.
It is also something that should be fixed in kerneloops: As mentioned in <https://wiki.ubuntu.com/NotifyOSD#kerneloops>, kerneloops should be using a custom alert box anyway rather than a notification. (This would improve on the fallback alert in that it would no longer have an "OK" button that did nothing exactly like the "Cancel" button.) |
The notification window from kerneloops is crippled by notify-osd, which means kernel crashes are neither being reported upstream nor being passed to apport for LP filing.
The functions that should be available: http://launchpadlibrarian.net/23735662/kerneloops-notify-good.jpg
What actually happens: http://launchpadlibrarian.net/23735670/kerneloops-notify-bad.jpg
This is a high-importance bug in Notify OSD: as described in <https://wiki.ubuntu.com/NotifyOSD#org.freedesktop.Notifications.Notify>, "Any other actions should be supplied as buttons for the alert", and "If body is supplied, the system should sanitize it, concatenate it with the summary with a blank line between them, and use the combination as the text of the alert".
It is also something that should be fixed in kerneloops: As mentioned in <https://wiki.ubuntu.com/NotifyOSD#kerneloops>, kerneloops should be using a custom alert box anyway rather than a notification. (This would improve on the fallback alert in that it would no longer have an "OK" button that did nothing exactly like the "Cancel" button.) |
|
| 2009-03-11 17:34:59 |
Mirco Müller |
notify-osd: status |
New |
Fix Committed |
|
| 2009-03-11 17:34:59 |
Mirco Müller |
notify-osd: statusexplanation |
Mirco, this is a bug in Notify OSD regardless of whether kerneloops is checking the capabilities correctly. As long as Notify OSD makes kerneloops useless, it'll also be making useless a chunk of the other unknown applications for which Notify OSD has fallback alert boxes in the first place. |
|
|
| 2009-03-13 14:37:44 |
Sebastien Bacher |
notify-osd: importance |
Undecided |
Low |
|
| 2009-03-13 14:40:07 |
Launchpad Janitor |
notify-osd: status |
Fix Committed |
Fix Released |
|
| 2009-03-18 15:38:20 |
David Barth |
kerneloops: status |
Confirmed |
Fix Committed |
|
| 2009-03-18 15:38:20 |
David Barth |
kerneloops: statusexplanation |
|
Cody provided a better dialog box for kerneloops. The patch is attached to bug 344377. |
|
| 2009-03-20 01:26:01 |
Steve Langasek |
kerneloops: status |
Fix Committed |
Fix Released |
|
| 2009-03-20 01:26:01 |
Steve Langasek |
kerneloops: statusexplanation |
Cody provided a better dialog box for kerneloops. The patch is attached to bug 344377. |
|
|
| 2009-07-10 04:57:07 |
Launchpad Janitor |
branch linked |
|
lp:ubuntu/karmic/notify-osd |
|
