kubuntu-notification-helper 14.04ubuntu1 source package in Ubuntu
Changelog
kubuntu-notification-helper (14.04ubuntu1) trusty; urgency=low * Fix LP: #1258484 k-n-h does not launch apport -- Jonathan Riddell <email address hidden> Fri, 06 Dec 2013 11:42:58 +0000
Upload details
- Uploaded by:
- Jonathan Riddell
- Uploaded to:
- Trusty
- Original maintainer:
- Kubuntu Members
- Architectures:
- any
- Section:
- kde
- Urgency:
- Low Urgency
See full publishing history Publishing
Series | Published | Component | Section |
---|
Downloads
File | Size | SHA-256 Checksum |
---|---|---|
kubuntu-notification-helper_14.04ubuntu1.tar.xz | 74.2 KiB | a3d9134184966125d0cfac422bd491da1e8e6f07a75777b8727fdc67bb76a39a |
kubuntu-notification-helper_14.04ubuntu1.dsc | 1.3 KiB | 74d960c8a8b3d675bab72c3a6999bfd7c37acf15622d85bb9d604985c07768fd |
Available diffs
- diff from 13.10ubuntu1 to 14.04ubuntu1 (805 bytes)
Binary packages built by this source
- kubuntu-notification-helper: Kubuntu system notification helper
Kubuntu Notification Helper is a daemon that presents various notifications
to the user. It uses the KDE Daemon system as a base and presents the
notifications using the KDE Notification system. It also includes a
System Settings module for configuring the daemon. Kubuntu Notification
Helper is lightweight and fully integrated with KDE.
.
Current features include:
- Notifications for Apport crashes.
- Notifications for upgrade information, when available.
- Notifications for the availability restrictively-licensed packages.
- Notifications for when upgrades require a reboot to complete.
- All notifications can be hidden temporarily or permanently.
- kubuntu-notification-helper-dbg: Kubuntu Notification Helper debugging symbols
This package contains debugging symbols for Kubuntu Notification Helper.
When Kubuntu Notification Helper crashes, in most cases this package is
needed to get a backtrace that is useful for developers. If you have
experienced a Kubuntu Notification Helper crash without this package
installed, please install it, try to reproduce the problem and fill a bug
report with a new backtrace attached.