Although all of the actions appear in the dialog now, kerneloops still
doesn't seem to work with notify-osd. The apport report is never
generated. It also presents two different dialog boxes, with the same
set of actions, which doesn't look right at all.
--
kerneloops notifications crippled,
With the patches to present a dialog instead of notification, kerneloops
still fails to send the report. There is an apport traceback in the
/var/log/apport.log:
apport (pid 17813) Thu Mar 19 09:57:11 2009: Unhandled exception:
Traceback (most recent call last):
File /usr/share/apport/apport,
After applying your patch from bug 344377, the dialog seems to work
sensibly.
However, the apport integration still doesn't work. I don't get
anything in /var/log/apport.log at all. I've un-duped bug 344813
accordingly, please continue discussion there.
--
kerneloops notifications crippled,
I believe this bug is fixed in the following upload, which has been
accepted into jaunty:
kerneloops (0.12-0ubuntu4) jaunty; urgency=low
[ Ken VanDine ]
* debian/applied-patches/kerneloops-applet.c.patch: Convert notification to
a dialog. Applied inline, since package has no patch
** Changed in: kerneloops (Ubuntu Jaunty)
Status: Fix Committed = Fix Released
--
kerneloops notifications crippled, fails to file
https://bugs.launchpad.net/bugs/340773
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
I've implemented mpt's new dialog in bug 344377 if anyone would like to
review it. Thanks.
--
kerneloops notifications crippled, fails to file
https://bugs.launchpad.net/bugs/340773
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
Cody provided a better dialog box for kerneloops. The patch is attached
to bug 344377.
** Changed in: kerneloops (Ubuntu Jaunty)
Status: Confirmed = Fix Committed
--
kerneloops notifications crippled, fails to file
https://bugs.launchpad.net/bugs/340773
You received this bug notification
This bug was fixed in the package notify-osd - 0.9.3-0ubuntu1
---
notify-osd (0.9.3-0ubuntu1) jaunty; urgency=low
* New upstream version:
- don't crash on download notifications (lp: #332042)
- correctly pass actions to the fallback (lp: #340773)
- correctly namespace
** Changed in: notify-osd (Ubuntu Jaunty)
Importance: Undecided = Low
--
kerneloops notifications crippled, fails to file
https://bugs.launchpad.net/bugs/340773
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing
While the actions are now available, I understand that the body text is
still missing from the fallback alert, which means the kerneloops alert
box still isn't particularly understandable. This is a variation of bug
339020, which should be fixed sometime in the next two weeks.
Meanwhile, I've
I can see why this would cripple the upstream reporting, but why does it
affect apport? It should create a .crash report unconditionally,
without prompting the user, because this is a local operation. apport
itself prompts the user later about whether to report it to Launchpad.
** Tags added:
http://wiki.ubuntu.com/NotificationDevelopmentGuidelines has good
suggestions for how to handle cases like this.
--
kerneloops notifications crippled, fails to file
https://bugs.launchpad.net/bugs/340773
You received this bug notification because you are a member of Ubuntu
Bugs, which is
** Also affects: notify-osd (Ubuntu)
Importance: Undecided
Status: New
--
kerneloops notifications crippled, fails to file
https://bugs.launchpad.net/bugs/340773
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
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
Please note that notify-osd by design doesn't support actions in
notifications. This should be fixed in kerneloops itself, it needs to
check whether the notification daemon implementation actually supports
actions with notify_get_server_caps(). The notification spec does not
guarantee that actions
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.
**
** Description changed:
- 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,
There's a design-shortcoming in the way notify-osd handles the fallback-
dialog. It does not pass additional widgets from a notification to the
fallback dialog. That's the first thing I'll fix. After that I'll write
a patch to kerneloops upstream to use a nice gtk+-dialog, if notify-osd
is found
** Description changed:
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:
The fix in notify-osd is pushed. It was actually only a typo that
prevented the actions to be passed to the fallback dialog.
** Changed in: notify-osd (Ubuntu Jaunty)
Status: New = Fix Committed
--
kerneloops notifications crippled, fails to file
https://bugs.launchpad.net/bugs/340773
Functional notification window.
** Attachment added: kerneloops-notify-good.jpg
http://launchpadlibrarian.net/23735662/kerneloops-notify-good.jpg
--
kerneloops notifications crippled, fails to file
https://bugs.launchpad.net/bugs/340773
You received this bug notification because you are a
For simulating Oops, please see http://people.ubuntu.com/~lieb/kernel-
crasher.tgz. When switching between notification-daemon and notify-osd,
notification-daemon must be explicitly started. Also, the kerneloops-
applet can be restarted to re-attempt crash notifications.
--
kerneloops
This is blocking bug 327819 (the kerneloops MIR) since it makes
kerneloops difficult to test.
** Changed in: notify-osd (Ubuntu Jaunty)
Importance: Undecided = High
Status: New = Confirmed
Target: None = ubuntu-9.04-beta
--
kerneloops notifications crippled, fails to file
Crippled notification window.
** Attachment added: kerneloops-notify-bad.jpg
http://launchpadlibrarian.net/23735670/kerneloops-notify-bad.jpg
--
kerneloops notifications crippled, fails to file
https://bugs.launchpad.net/bugs/340773
You received this bug notification because you are a member
24 matches
Mail list logo
