kubuntu-notification-helper 19.10ubuntu4 source package in Ubuntu
Changelog
kubuntu-notification-helper (19.10ubuntu4) noble; urgency=medium * No-change rebuild for CVE-2024-3094 -- Steve Langasek <email address hidden> Sun, 31 Mar 2024 09:11:11 +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.10ubuntu4.tar.xz | 88.7 KiB | 83fd0a1b9c2ca90274fef3d9795be368502c994fa4d1fed318833393d1a0d6ec |
kubuntu-notification-helper_19.10ubuntu4.dsc | 2.0 KiB | a41f82f39ef2e12b6d8a81504106d5f7494677d87fd4b71aeda90fba688c17e5 |
Available diffs
- diff from 19.10ubuntu3 to 19.10ubuntu4 (343 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.