Dear Maintainer,

*** Reporter, please consider answering these questions, where appropriate ***

   * What led up to the situation?
   * What exactly did you do (or not do) that was effective (or
     ineffective)?
   * What was the outcome of this action?
   * What outcome did you expect instead?

start nextcloud from terminal or click button in GNOME. A window seems to appear, but it doesn't do anything, and
freezes...

See a screenshot that clearly shows the "torn away" pixels from behind where the window used to be (after I move
the window to overlap a white background area on a search page).

This is causing data loss because without nextcloud running on the desktop I have "split brain" between nextcloud
files and local files.

When I run from the command line I get the following output:

2021-01-12 20:43:29:531 [ debug default ]	[ unknown ]:	static bool LibSecretKeyring::findPassword(const QString&, const QString&, QKeychain::JobPrivate*)
2021-01-12 20:43:30:766 [ debug nextcloud.gui.systray ]	[ OCC::Systray::computeWindowReferencePoint ]:	screenRect: QRect(0,0 3840x2160)
2021-01-12 20:43:30:766 [ debug nextcloud.gui.systray ]	[ OCC::Systray::computeWindowReferencePoint ]:	taskbarRect: QRect(0,0 3840x32)
2021-01-12 20:43:30:766 [ debug nextcloud.gui.systray ]	[ OCC::Systray::computeWindowReferencePoint ]:	taskbarScreenEdge: OCC::Systray::TaskBarPosition::Bottom
2021-01-12 20:43:30:766 [ debug nextcloud.gui.systray ]	[ OCC::Systray::computeWindowReferencePoint ]:	trayIconCenter: QPoint(1141,1238)
2021-01-12 20:43:30:766 [ debug nextcloud.gui.systray ]	[ OCC::Systray::computeWindowPosition ]:	taskbarScreenEdge: OCC::Systray::TaskBarPosition::Bottom
2021-01-12 20:43:30:766 [ debug nextcloud.gui.systray ]	[ OCC::Systray::computeWindowPosition ]:	screenRect: QRect(0,0 3840x2160)
2021-01-12 20:43:30:766 [ debug nextcloud.gui.systray ]	[ OCC::Systray::computeWindowPosition ]:	windowRect (reference) QRect(941,1613 401x511)
2021-01-12 20:43:30:766 [ debug nextcloud.gui.systray ]	[ OCC::Systray::computeWindowPosition ]:	windowRect (adjusted ) QRect(941,1613 401x511)
2021-01-12 20:43:30:773 [ debug default ]	[ unknown ]:	static bool LibSecretKeyring::findPassword(const QString&, const QString&, QKeychain::JobPrivate*)
2021-01-12 20:43:30:776 [ debug default ]	[ unknown ]:	static bool LibSecretKeyring::findPassword(const QString&, const QString&, QKeychain::JobPrivate*)
2021-01-12 20:43:30:777 [ debug default ]	[ unknown ]:	static bool LibSecretKeyring::findPassword(const QString&, const QString&, QKeychain::JobPrivate*)
2021-01-12 20:43:30:778 [ debug default ]	[ unknown ]:	static bool LibSecretKeyring::findPassword(const QString&, const QString&, QKeychain::JobPrivate*)
2021-01-12 20:43:30:866 [ debug default ]	[ unknown ]:	static bool LibSecretKeyring::writePassword(const QString&, const QString&, const QString&, QKeychain::JobPrivate::Mode, const QByteArray&, QKeychain::JobPrivate*)
2021-01-12 20:43:31:284 [ debug default ]	[ unknown ]:	static bool LibSecretKeyring::writePassword(const QString&, const QString&, const QString&, QKeychain::JobPrivate::Mode, const QByteArray&, QKeychain::JobPrivate*)
2021-01-12 20:43:31:568 [ debug default ]	[ unknown ]:	static bool LibSecretKeyring::writePassword(const QString&, const QString&, const QString&, QKeychain::JobPrivate::Mode, const QByteArray&, QKeychain::JobPrivate*)
2021-01-12 20:43:31:874 [ debug default ]	[ unknown ]:	static bool LibSecretKeyring::writePassword(const QString&, const QString&, const QString&, QKeychain::JobPrivate::Mode, const QByteArray&, QKeychain::JobPrivate*)
2021-01-12 20:43:32:367 [ debug default ]	[ unknown ]:	static bool LibSecretKeyring::writePassword(const QString&, const QString&, const QString&, QKeychain::JobPrivate::Mode, const QByteArray&, QKeychain::JobPrivate*)
2021-01-12 20:43:32:669 [ debug default ]	[ unknown ]:	static bool LibSecretKeyring::writePassword(const QString&, const QString&, const QString&, QKeychain::JobPrivate::Mode, const QByteArray&, QKeychain::JobPrivate*)
2021-01-12 20:43:32:927 [ debug default ]	[ unknown ]:	static bool LibSecretKeyring::writePassword(const QString&, const QString&, const QString&, QKeychain::JobPrivate::Mode, const QByteArray&, QKeychain::JobPrivate*)
2021-01-12 20:43:33:461 [ debug default ]	[ unknown ]:	static bool LibSecretKeyring::writePassword(const QString&, const QString&, const QString&, QKeychain::JobPrivate::Mode, const QByteArray&, QKeychain::JobPrivate*)
2021-01-12 20:43:33:683 [ debug default ]	[ unknown ]:	static bool LibSecretKeyring::writePassword(const QString&, const QString&, const QString&, QKeychain::JobPrivate::Mode, const QByteArray&, QKeychain::JobPrivate*)



*** End of the template - remove these template lines ***

This sounds not like the fault of nextcloud-desktop and I cannot reproduce it
under a KDE environment. that's why lowering the severity and forward to
gnome-shell.

It also may makes sense to search in the upstream issue tracker if you find a
patch or any explanation: https://github.com/nextcloud/desktop/issues.
Please report back, if you found anything. For me it very hard to track every
issue for different desktop environments, that I do not use myself, so I need
help from your side.

regards,

hefee
2021-01-12
windowRect
windowRect
QString&,
unknown
QString&,

Control: reassign -1 gnome-shell,nextcloud-desktop
Control: found -1 nextcloud-desktop/3.0.1-3
Control: tags -1 + unreproducible moreinfo

I tried installing nextcloud-desktop and connecting it to the test
instance offered by <https://try.nextcloud.com/>, and I couldn't reproduce
this in a GNOME environment either. The original report could have been
a gnome-shell bug, or a nextcloud-desktop bug - we don't really have
any evidence either way - so I'm assigning this to both.

Does this still happen in an up-to-date testing/unstable installation,
or in an up-to-date installation of Debian 11 'bullseye'?

If yes, which gnome-shell version?

If you create a new temporary user account on the same system (so that
the new user does not have any special configuration), can you reproduce
the problem with <https://try.nextcloud.com/> as the new user? If so,
please explain how?

Thanks,
    smcv

it

I can reproduce it here under Gnome / wayland; (Under X, it works.)
I've got a nvidia GPU with nvidia-drivers from non-free, maybe that's another
nvidia issue?

If I start using specifing some QT_OPA_PLATFROM value, eg

QT_QPA_PLATFORM=wayland nextcloud --logfile - --logdebug

it will open the window, however there is something broken with the
event loop or like: If one does not jiggle the mouse over the apps seems
to be stuck. (easily observable using --logdebug... almost no output
when mouse is not over the window and moving, but crazy if moving.
This basically breaks automatic sync, I'm not sure if it syncs at all 
or only a few files every ~5-10 seconds ... Occasionally it emits this:

I can provide more logs on request (on a more private channel), let me know.

Hey,

if it still is valid under the new version 3.4.2, than please get in contact
with upstream: https://github.com/nextcloud/desktop/issues
As it is not an packaging bug on our side.

Please report back the create issue url, to keep track of the upstream bug.
With at the first line of the mail, than BTS will do the rest:

Control: Forwarded -1 <URL>

Regards,

hefee
poll
to
of
etag
run
etag
run
[

Hey,

Is libqt5waylandclient is installed?

that is quite possible. NVIDIA and wayland are not the best friends ;)

Well I run wayland on a daily basis and I don't see the error for the KDE
Plasma desktop with wayland .  Is libqt5waylandclient is installed? Maybe you
can install kde-standard in parallel to your GMOME desktop, to make sure it is
not a missing dependency?

regards,

hefee

Hey,

Is libqt5waylandclient is installed?

that is quite possible. NVIDIA and wayland are not the best friends ;)

Well I run wayland on a daily basis and I don't see the error for the KDE
Plasma desktop with wayland .  Is libqt5waylandclient is installed? Maybe you
can install kde-standard in parallel to your GMOME desktop, to make sure it is
not a missing dependency?

regards,

hefee

The bug still persists in Debian testing as of 23.2.2025



On Mon, 4 Oct 2021 13:42:19 +0100 Simon McVittie <smcv@debian.org> wrote:
reproduce it
forward to
reproduce
been
installation,
that
reproduce

Hello,

I had similar issue on trixie (window missing on gnome, or frozen when
started from a terminal).

I installed kde-standard as sugested be Hefee and nextcloud stared
working fine !

Thanks