kubuntu-notification-helper 19.10ubuntu3 source package in Ubuntu
Changelog
kubuntu-notification-helper (19.10ubuntu3) noble; urgency=medium * No-change rebuild against libqt5core5t64 -- Steve Langasek <email address hidden> Fri, 15 Mar 2024 05:29:01 +0000
Upload details
- Uploaded by:
- Steve Langasek
- Uploaded to:
- Noble
- Original maintainer:
- Kubuntu Members
- Architectures:
- any
- Section:
- kde
- Urgency:
- Medium Urgency
See full publishing history Publishing
Series | Published | Component | Section |
---|
Downloads
File | Size | SHA-256 Checksum |
---|---|---|
kubuntu-notification-helper_19.10ubuntu3.tar.xz | 88.7 KiB | 06114d1686084bc2d16d084a4b7c7230b61313539b32fe8a34132045c6bd187f |
kubuntu-notification-helper_19.10ubuntu3.dsc | 2.0 KiB | 5a349f6d00f7f753f72cb3a3df5a996de3c98269a0c6b82f85d107032f23cdc7 |
Available diffs
- diff from 19.10ubuntu2 to 19.10ubuntu3 (361 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.