"grant access" every loging in kde

šŸ“± Desktop & mobile clients šŸ’» Desktop
1

Hello,

i have my two pcs with linux (kde with kwallet manager) the two pcs are set so kwallet is open when loging, nevertheless every time nextcloud does not sync and needs ā€˜grant accessā€™ to it. the client version is 4.0.6dayli.

2

You mentioned Linux + KDE + KWallet and that KWallet is unlocked at login.

However, you didnā€™t specify:

  • Which Linux distribution and version

  • How the Nextcloud client is installed (repo / Flatpak / AppImage / Snap)

  • Whether both machines are using the exact same setup

Those details matter here. Without them, nobody can properly narrow this down.

Also, take a moment to search the forum. Similar ā€œ, kwallet ā€¦grant access on every loginā€ issues have already been discussed multiple times. Thereā€™s a good chance youā€™ll find an existing thread with the same root cause, which might make opening a new topic unnecessary.

Provide the missing details if the existing solutions donā€™t apply, and people can help more effectively.

1 Like
3

Thanks for your answer and recommendations.
the linux distribution and version: tuxedos which is based in ubuntu TUXEDO OS - TUXEDO Computers

the complete info of my system:
Operating System: TUXEDO OS
KDE Plasma Version: 6.5.2
KDE Frameworks Version: 6.19.0
Qt Version: 6.9.2
Kernel Version: 6.14.0-123037-tuxedo (64-bit)
Graphics Platform: X11
Processors: 16 Ɨ 12th Gen IntelĀ® Coreā„¢ i5-12500H
Memory: 64 GiB of RAM (62,5 GiB usable)
Graphics Processor 1: NVIDIA T600 Laptop GPU
Graphics Processor 2: IntelĀ® IrisĀ® Xe Graphics
Manufacturer: Dell Inc.
Product Name: Precision 3571

the nextcloud client is pre installed (and it looks like it is from a tuxedo repo? in version i have 4.0.6~tux1.

yes, both machines are using the exact same setup.

Also, take a moment to search the forum. Similar ā€œ, kwallet ā€¦grant access on every loginā€ issues have already been discussed multiple times. Thereā€™s a good chance youā€™ll find an existing thread with the same root cause, which might make opening a new topic unnecessary.

I will check right now. thanks

4

Maybe or maybe not. tuxedo is, you mentioned above, ubuntu based. Ubuntu use snaps. So it may be both, snap or deb. To check out open a Terminal (named Konsole in KDE) with:

dpkg --get-selections "nextcloud*"

to check its a deb or

snap list

for snaps. Show here the result of the checks.

2 Likes
5

thanks for your answer, they removed by default the snaps (and went with flatpaks) anyway, here is the output of the first command:
dpkg --get-selections "nextcloud*"
nextcloud-desktop install
nextcloud-desktop-common install
nextcloud-desktop-doc install
nextcloud-desktop-l10n install

6

The next logical step would be to test the official upstream AppImage from nextcloud.com.

Not because we assume the TUXEDO build is modified or broken ā€” but simply because the AppImage is the reference build maintained directly by Nextcloud. It removes distro packaging variables from the equation.

If the AppImage does not ask for ā€œgrant accessā€ on every login, then the issue is likely related to how the packaged build interacts with your environment.

If the AppImage behaves exactly the same way, then we can rule packaging out entirely and focus purely on KDE/KWallet/token handling.

Given that similar KDE/KWallet threads have appeared multiple times on this forum, testing the upstream build is usually the cleanest way to narrow this down before digging deeper.

1 Like