driverevent code in module.cpp not ordered

Bug #1282470 reported by Harald Sitter on 2014-02-20
This bug affects 1 person
Affects Status Importance Assigned to Milestone
kubuntu-notification-helper (Ubuntu)
Rohan Garg

Bug Description

    ApportEvent *m_apportEvent;
    HookEvent *m_hookEvent;
    InstallEvent *m_installEvent;
    L10nEvent *m_l10nEvent;
    RebootEvent* m_rebootEvent;

    ConfigWatcher *m_configWatcher;
    InstallDBusWatcher *m_installWatcher;
    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
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package kubuntu-notification-helper - 14.10ubuntu2

kubuntu-notification-helper (14.10ubuntu2) utopic; urgency=medium

  * 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

Changed in kubuntu-notification-helper (Ubuntu):
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers