Hi, I ran across this on the OpenSuSE user list. It's also a problem for me at login time; I've been starting Kmail and Konqueror manually because of it. Will the suggestion using systemd, listed at the end, work in Trinity also? TIA, Leslie ---------- Forwarded Message ---------- > Subject: Re: Make Kwallet behave ? > Date: 2022-08-28, 06:43:19 > From: Adam Mizerski <adam@xxxxxxxxxxx> > To: users@xxxxxxxxxxxxxxxxxx > > W dniu 28.08.2022 o 07:19, Nicolas Kovacs pisze: > > Hi, > > > > I've been a KDE user since version 2.x on Slackware more than 20 years > > ago. I really like it for my daily work, but some details are a bit of a > > PITA. Kwallet is one of them. > > > > Here's a few scenarios that happen erratically on my Tumbleweed > > installations. > > > > 1. KDE starts, Kwallet pops up immediately and leaves me about ten > > seconds to type in my very long GPG password. In the background, > > applications that need a password to connect (like OwnCloud) fail and > > have to be restarted. > > > > 2. KDE starts, Wi-Fi tries to connect but fails, OwnCloud asks me for > > the connection password, and after about a minute or so, Kwallet decides > > to pop up too late to the show. > > > > 3. KDE starts, Kwallet pops up, I type in my password fast enough, Wi-Fi > > connects but OwnCloud asks me for the connection password even though > > Kwallet has been opened successfully. > > > > Any idea how I can make Kwallet behave ? > > > > Cheers from the sunny South of France, > > > > Niki > > > > I have the same problem. > > I just had an idea, but it needs some experimenting to check whether it > would work. Recently KDE introduced managing it's services with systemd > [1]. Systemd allows to extend units using "foo.service.d" directories > [2]. Maybe it would be possible to inject a dependency between kwallet > and nextcloud? > > In my case it looks like this: > - kwallet runs under "dbus-:1.2-org.kde.kwalletd5@0.service" > - nextcloud runs under > "app-com.nextcloud.desktopclient.nextcloud-<random_id>.scope". > - both units are "a transient unit file, created programmatically via > the systemd API. Do not edit." > > You can see all systemd units (they form a tree) using "systemctl --user > status". > > I'll try to do some experiments with it. > > [1] https://blog.davidedmundson.co.uk/blog/plasma-and-the-systemd-startup/ > [2] "man systemd.unit" or > https://www.freedesktop.org/software/systemd/man/systemd.unit.html > > Unfortunately it's not a solution, but for the record: > https://github.com/nextcloud/desktop/issues/1011 ------------------------------------------------------- -- Operating System: Linux Distribution: openSUSE Leap 15.4 x86_64 Desktop Environment: Trinity Qt: 3.5.0 TDE: R14.0.12 tde-config: 1.0 ____________________________________________________ tde-devels mailing list -- devels@xxxxxxxxxxxxxxxxxx To unsubscribe send an email to devels-leave@xxxxxxxxxxxxxxxxxx Web mail archive available at https://mail.trinitydesktop.org/mailman3/hyperkitty/list/devels@xxxxxxxxxxxxxxxxxx
