[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-bugs-dist
Subject:    [QtCurve] [Bug 363753] crash-at-exit in QtCurve::Style::disconnectDBus
From:       RJVB via KDE Bugzilla <bugzilla_noreply () kde ! org>
Date:       2016-05-31 21:07:46
Message-ID: bug-363753-17878-lD8ncOO9vK () http ! bugs ! kde ! org/
[Download RAW message or body]

https://bugs.kde.org/show_bug.cgi?id=363753

--- Comment #1 from RJVB <rjvbertin@gmail.com> ---
I asked on the Qt interest ML and got this answer from Thiago Macieira:

> > just like the ctor does when setting up DBus. Is that correct practice or
> > should one somehow cache the result of sessionBus() in order to call it
> > only once?
>  
> It's not correct practice.
>  
> The problem is attempting to use QtDBus during global destruction.
> Apparently QtDBus has already destroyed its internals.
>  
> I can add a few protections for that.

https://codereview.qt-project.org/161056

-- 
You are receiving this mail because:
You are watching all bug changes.=
[prev in list] [next in list] [prev in thread] [next in thread]