# Nextcloud linux client loops creating keyring

**URL:** <https://help.nextcloud.com/t/nextcloud-linux-client-loops-creating-keyring/65472>\
**Category:** 💻 Desktop\
**Tags:** github\_issue\_required\
**Created:** [December 3, 2019, 9:18am UTC](https://help.nextcloud.com/t/nextcloud-linux-client-loops-creating-keyring/65472 "2019-12-03T09:18:29Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![kab00m](https://help.nextcloud.com/user_avatar/help.nextcloud.com/kab00m/32/19486_2.png) [@kab00m](https://help.nextcloud.com/u/kab00m)\
**Post date:** [December 3, 2019, 9:18am UTC](https://help.nextcloud.com/t/nextcloud-linux-client-loops-creating-keyring/65472/1 "2019-12-03T09:18:29Z")

</div>

Greetings,

I am using simple desktop based on IceWM and Xorg. I was using it with Nextcloud client 2.5 and Fedora 25 and i was logged in cloud by password and it was using gnome-keyring to save it. That was fine.

Now I have installed Fedora 31 and Nextcloud client 2.6.1 (from repo). When I try to login via new login mechanism - I get infinite keyring creation dialog. That means when nextcloud client starts it asks for creation of new keyring named “Default” two times. I can either enter password or cancel it. When browser opens with authorizing link - client is logged in and window with keyring creation appears again. It will continue opening when i enter password or cancel it. It will not stop opening until client is running and is also blocking work in other windows.

I moved out .config/Nextcloud and .local/share/keyring folders and this do not change anything. Also I found that keyring is never actually created.

What I may do for further investigation?

Client output mention a problem:  
Fontconfig warning: “/usr/share/fontconfig/conf.avail/05-reset-dirs-sample.conf”, line 6: unknown element “reset-dirs”  
[87488:87488:1203/120429.160206:FATAL:memory\_linux.cc(37)] Out of memory.  
–2019-12-03 12:04:29-- [https://clients2.google.com/cr/report](https://clients2.google.com/cr/report)

But I don’t see if that matters, because I have lot of free memory on PC and this happens only on client start.

Logdebug not show any significant errors, except

| [OCC::AbstractNetworkJob::slotFinished | QNetworkReply::ContentNotFoundError “Server replied “404 Not Found” to “POST [https://cloud.xxx.ru/index.php/login/v2/poll](https://cloud.xxx.ru/index.php/login/v2/poll)”” QVariant(int, 404) |
| --- | --- |
| [OCC::WebFlowCredentials::stillValid | QNetworkReply::ContentNotFoundError |
| [OCC::WebFlowCredentials::stillValid | “Error transferring [https://cloud.xxx.ru/index.php/login/v2/poll](https://cloud.xxx.ru/index.php/login/v2/poll) - server replied: Not Found” |

I have installed 2.5.3 from older FC31 release and it works fine.

---

<div class="post-metadata">

**Author:** ![tflidd](https://help.nextcloud.com/letter_avatar/tflidd/32/6_22734026db12803ebb3e059622ac3534.png) [@tflidd](https://help.nextcloud.com/u/tflidd)\
**Post date:** [December 6, 2019, 2:55pm UTC](https://help.nextcloud.com/t/nextcloud-linux-client-loops-creating-keyring/65472/2 "2019-12-06T14:55:26Z")

</div>

If this pops up directly after an update, you can directly contact the developers.  
Please report this to the bugtracker: [https://github.com/nextcloud/desktop/issues](https://github.com/nextcloud/desktop/issues)

---

<div class="post-metadata">

**Author:** ![wwe](https://help.nextcloud.com/user_avatar/help.nextcloud.com/wwe/32/72963_2.png) [@wwe](https://help.nextcloud.com/u/wwe)\
**Post date:** [December 14, 2024, 5:19pm UTC](https://help.nextcloud.com/t/nextcloud-linux-client-loops-creating-keyring/65472/3 "2024-12-14T17:19:24Z")

</div>



---

<div class="post-metadata">

**Author:** ![wwe](https://help.nextcloud.com/user_avatar/help.nextcloud.com/wwe/32/72963_2.png) [@wwe](https://help.nextcloud.com/u/wwe)\
**Post date:** [December 14, 2024, 5:19pm UTC](https://help.nextcloud.com/t/nextcloud-linux-client-loops-creating-keyring/65472/4 "2024-12-14T17:19:25Z")

</div>


