On Friday 18 of July 2014 10:37 Kai Uwe Broulik wrote: > Hi, > > For notifications you could wait for org.freedesktop.Notifications to become > available. We have a similar issue in PowerDevil where the "your battery is > low" notification also spawns an ugly popup ontop of ksplash. >
Yep, that could be a good solution. > I guess same for org.kde.kwalletd? > Not sure about this one, because we have also a fallback when you don't want to use KWallet then we store secrets into a file. Maybe it's time to force using KWallet or store secrets directly to NetworkManager. Jan > Cheers > > Am 18.07.2014 09:06 schrieb Jan Grulich <jgrul...@redhat.com>: > > Hi all, > > > > I would need help with delayed loading of our kded module due two problems > > when it's loaded too early: > > > > 1) When you are automatically connected to a network you will get an old > > notifications (the ugly one putted on top of the screen) because KDE > > notifications are not running at that time. > > > > 2) You can get a password dialog even if you have your password stored in > > KWallet because KWallet is not running when our kded module is asking for > > a > > password. > > > > So far I was checking whether plasma-desktop or plasmashell are on DBus, > > but it doesn't work when you have Plasma Netbook mode or you don't use > > plasma- desktop/plasmashell. The only thing I can think of is load our > > kded module from plasma-nm calling LoadModule using DBus. Another > > approach could be creating own DBus interface from plasma-nm and wait > > until it appears on DBus and then finish initialization of the module > > like we did before with checking plasma-desktop/plasmashell. What do you > > think? Do you have a better idea? > > > > Thanks. > > > > Cheers, > > Jan -- Jan Grulich Red Hat Czech, s.r.o jgrul...@redhat.com _______________________________________________ Plasma-devel mailing list Plasma-devel@kde.org https://mail.kde.org/mailman/listinfo/plasma-devel
