driverevent code in module.cpp not ordered
Bug #1282470 reported by
Harald Sitter
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| kubuntu-notification-helper (Ubuntu) |
Fix Released
|
Medium
|
Rohan Garg | ||
Bug Description
private:
ApportEvent *m_apportEvent;
HookEvent *m_hookEvent;
InstallEvent *m_installEvent;
L10nEvent *m_l10nEvent;
RebootEvent* m_rebootEvent;
ConfigWatcher *m_configWatcher;
InstallDBus
DriverEvent* m_driverEvent;
^
the event members *and* the init list *and* the actual show() order in module.cpp are alphabetically ordered, DriverEvent is not even though it should.
| Changed in kubuntu-notification-helper (Ubuntu): | |
| milestone: | ubuntu-14.04 → none |
| status: | Triaged → Fix Committed |
Revision history for this message
| Launchpad Janitor (janitor) wrote | #1 |
| Changed in kubuntu-notification-helper (Ubuntu): | |
| status: | Fix Committed → Fix Released |
To post a comment you must log in.
This bug was fixed in the package kubuntu-
---------------
kubuntu-
* Fix a logic error with init handling -> explicitly set the init bool to
true/false, previously it would always be true as a return was missing
-- Harald Sitter <email address hidden> Wed, 25 Jun 2014 10:46:45 +0200