Summary: | Persistence in the remote desktop portal does not work across reboots | ||
---|---|---|---|
Product: | [Plasma] xdg-desktop-portal-kde | Reporter: | Prajna Sariputra <putr4.s> |
Component: | general | Assignee: | Plasma Bugs List <plasma-bugs> |
Status: | CONFIRMED --- | ||
Severity: | normal | CC: | 0vinoth0kumar0, aleixpol, benjiwiebe14, dashonwwIII, dinkonin, drokergeek, jgrulich, kdebugs, kdebug_volle, mundolibre, nate, nicolas.fella, sitter, the.real.samuel.jimenez, unblended_icing552 |
Priority: | NOR | Keywords: | qt6, usability |
Version: | git-master | ||
Target Milestone: | --- | ||
Platform: | Compiled Sources | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: |
Description
Prajna Sariputra
2024-01-23 16:23:45 UTC
*** Bug 480435 has been marked as a duplicate of this bug. *** I'm not only having the issue of it not being persistent, but the permission dialog doesn't always show up. I believe this occurs when restarting plasmashell in some instances and not when rebooting though. (In reply to Dashon from comment #2) > I'm not only having the issue of it not being persistent, but the permission > dialog doesn't always show up. I believe this occurs when restarting > plasmashell in some instances and not when rebooting though. After further testing, it definitely survives plasmashell restarting, but I know sometimes when it starts working. I would open the system tray and end the permission for it. Hoping that it would pop up again the next time I tried to use it. Thus fixing the problem. Whenever it stops working, I can usually get it to work again and give me the popup again by killing the kdeconnectd process and starting again. Oh, if you're using KDE Connect and you're stopping the remote control session via the system tray icon then I think that's actually a problem from the KDE Connect side, I don't think it has support for automatically restarting the remote control session if the user stopped it manually at the moment, so KDE Connect will just try (and fail) to use the old cancelled session, and you won't see a notification or permissions dialog until you restart kdeconnectd and try using remote input again. (In reply to Prajna Sariputra from comment #4) > Oh, if you're using KDE Connect and you're stopping the remote control > session via the system tray icon then I think that's actually a problem from > the KDE Connect side, I don't think it has support for automatically > restarting the remote control session if the user stopped it manually at the > moment, so KDE Connect will just try (and fail) to use the old cancelled > session, and you won't see a notification or permissions dialog until you > restart kdeconnectd and try using remote input again. Ok, so I definitely shouldn't do that anymore. Now all that is left to solve is why it stops working sometimes. |