Hi,
recently I reported a bug as the PowerManager library
was reporting the wrong PowerSaveStatus, Lukas took
a look, saw nothing wrong but proposed a patch, that well
sort of worked. After doing several tests with Apped KDED
module I realized the problem was when the DBus
interface was not availa
> They may be less expensive but I still prefer to cache the value and use
> signals/slots to update it, that is more guaranteed not to cause freeze
> problems.
My proposal is to use *cached* values.
> The current behaviour is different because in some places Solid is using
> asynchronous calls as
Patch done, tested, works pretty well
https://git.reviewboard.kde.org/r/105310/
> I changed it to QDBusReply, which is the equivalent to
> QDBusPendingReply+waitForFinished, and the crash is gone (the link above is
> a diff output showing thatt). The link in your last email states that
> QDBusPend
m.
Diffs
-
solid/solid/powermanagement.cpp 8dc8535
solid/solid/powermanagement_p.h f39815d
Diff: http://git.reviewboard.kde.org/r/105310/diff/
Testing
---
Thanks,
Daniel Nicoletti
___
Kde-hardware-devel mailing list
Kde-hardware-dev
> I mentioned desktop freezes in general, not that particular bug. Hmm I guess
> you created a thread that communicates with dbus and another that does the
> heavy work. Ok, that would be good approach to prevent kded modules from
> blocking kded.
Well there is no heavy work on Apper, so it's just
2012/6/20 Lamarque V. Souza :
> "Heavy work" is just a manner of speaking :-) It's too bad that each module
> should implement such a thread way of doing things. We could add something
> reusable like kded implementing each module as a thread. It should work
> (famous last words).
I thought of that
> Networkmanagement's kded module uses KDialog to get the PIN/PUK codes to
> unlock Gsm modems, which means it also need to be in the main thread, at
> least that part have to be. Most of the kded initialization is done after
> the plasmoid is loaded (there is a signal for that), although I did not
wermanagement.cpp 8dc8535
> solid/solid/powermanagement_p.h f39815d
>
> Diff: http://git.reviewboard.kde.org/r/105310/diff/
>
>
> Testing
> ---
>
>
> Thanks,
>
> Daniel Nicoletti
>
>
___
Kde-hardware-devel mailing list
Kde-hardware-devel@kde.org
https://mail.kde.org/mailman/listinfo/kde-hardware-devel
it has to be done only once.
>
> For the interface, we'll need to wait to 0.2 for sure.
> ___
> Kde-hardware-devel mailing list
> Kde-hardware-devel@kde.org
> https://mail.kde.org/mailman/listinfo/kde-hardware-devel
--
Daniel Nicoletti
KDE Developer - http://dantti.wordpress.com
___
Kde-hardware-devel mailing list
Kde-hardware-devel@kde.org
https://mail.kde.org/mailman/listinfo/kde-hardware-devel
st would for bluedevil to call a DBus activated service like
org.kde.bluetooth_connection, this has the benefit for bluedevil first
check if the interface is available to be activated, and if not disable
the feature. This will even work if both are installed.
Best,
--
Daniel Nicoletti
KDE Deve
gt;
>
> ___
> Kde-hardware-devel mailing list
> Kde-hardware-devel@kde.org
> https://mail.kde.org/mailman/listinfo/kde-hardware-devel
>
>
--
Daniel Nicoletti
KDE Developer - http://dantti.wordpress.com
___
Kde-hardware-devel mailing list
Kde-hardware-devel@kde.org
https://mail.kde.org/mailman/listinfo/kde-hardware-devel
libnm-qt.
>
> Cheers,
> --
> sebas
>
> http://www.kde.org | http://vizZzion.org | GPG Key ID: 9119 0EF9
> ___
> Kde-hardware-devel mailing list
> Kde-hardware-devel@kde.org
> https://mail.kde.org/mailman/listinfo/kd
re-devel@kde.org
>> https://mail.kde.org/mailman/listinfo/kde-hardware-devel
> ___
> Kde-hardware-devel mailing list
> Kde-hardware-devel@kde.org
> https://mail.kde.org/mailman/listinfo/kde-hardware-devel
--
Daniel Nicoletti
KDE Developer - http://dantti.wordpress.com
ing the above proposal,
> otherwise we should discuss another strategy.
>
> Best,
>
> __J
> ___
> Kde-hardware-devel mailing list
> Kde-hardware-devel@kde.org
> https://mail.kde.org/mailman/listinfo/kde-hardware-devel
--
D
Regarding the bug I think the proper
fix is to not pop up when the plasmoid
is created, it's rather annoying to see
it even if you just started your session
with an usb stick.
2014-04-30 17:45 GMT-03:00 Daniel Nicoletti :
> IMHO the icon must be there as most PC's floppy drives
>
15 matches
Mail list logo
