You are not logged in.

#1 2020-09-16 17:10:31

zaxmyth
Member
From: Seattle / San Francisco
Registered: 2019-03-25
Posts: 23
Website

Nextcloud client 3.0.1 coredump

After updating to Nextcloud-client 3.0.1 I am getting the following at launch. Before I open a bug I thought I'd check with the forum and see if anybody has ideas here.

2020-09-16 10:02:40:219 [ debug default ]	[ unknown ]:	static bool LibSecretKeyring::findPassword(const QString&, const QString&, QKeychain::JobPrivate*)
2020-09-16 10:02:41:384 [ debug nextcloud.gui.systray ]	[ OCC::Systray::computeWindowReferencePoint ]:	screenRect: QRect(0,0 1920x1080)
2020-09-16 10:02:41:384 [ debug nextcloud.gui.systray ]	[ OCC::Systray::computeWindowReferencePoint ]:	taskbarRect: QRect(0,0 1920x32)
2020-09-16 10:02:41:384 [ debug nextcloud.gui.systray ]	[ OCC::Systray::computeWindowReferencePoint ]:	taskbarScreenEdge: OCC::Systray::TaskBarPosition::Bottom
2020-09-16 10:02:41:384 [ debug nextcloud.gui.systray ]	[ OCC::Systray::computeWindowReferencePoint ]:	trayIconCenter: QPoint(1734,960)
2020-09-16 10:02:41:385 [ debug nextcloud.gui.systray ]	[ OCC::Systray::computeWindowPosition ]:	taskbarScreenEdge: OCC::Systray::TaskBarPosition::Bottom
2020-09-16 10:02:41:385 [ debug nextcloud.gui.systray ]	[ OCC::Systray::computeWindowPosition ]:	screenRect: QRect(0,0 1920x1080)
2020-09-16 10:02:41:385 [ debug nextcloud.gui.systray ]	[ OCC::Systray::computeWindowPosition ]:	windowRect (reference) QRect(1534,533 401x511)
2020-09-16 10:02:41:385 [ debug nextcloud.gui.systray ]	[ OCC::Systray::computeWindowPosition ]:	windowRect (adjusted ) QRect(1515,533 401x511)
2020-09-16 10:02:41:392 [ debug default ]	[ unknown ]:	static bool LibSecretKeyring::findPassword(const QString&, const QString&, QKeychain::JobPrivate*)
2020-09-16 10:02:41:393 [ debug default ]	[ unknown ]:	static bool LibSecretKeyring::findPassword(const QString&, const QString&, QKeychain::JobPrivate*)
2020-09-16 10:02:41:394 [ debug default ]	[ unknown ]:	static bool LibSecretKeyring::findPassword(const QString&, const QString&, QKeychain::JobPrivate*)
2020-09-16 10:02:41:395 [ debug default ]	[ unknown ]:	static bool LibSecretKeyring::findPassword(const QString&, const QString&, QKeychain::JobPrivate*)
2020-09-16 10:02:41:401 [ fatal default ]:	Failed to create OpenGL context for format QSurfaceFormat(version 2.0, options QFlags<QSurfaceFormat::FormatOption>(), depthBufferSize 24, redBufferSize -1, greenBufferSize -1, blueBufferSize -1, alphaBufferSize 8, stencilBufferSize 8, samples -1, swapBehavior QSurfaceFormat::DoubleBuffer, swapInterval 1, colorSpace QSurfaceFormat::DefaultColorSpace, profile  QSurfaceFormat::NoProfile) 
[1]    2157 abort (core dumped)  nextcloud

Offline

#2 2020-09-16 21:32:56

solskog
Member
Registered: 2020-09-05
Posts: 85

Re: Nextcloud client 3.0.1 coredump

I did a fresh install of nextcloud-client and started GUI with no issue.

Repository      : community
Name            : nextcloud-client
Version         : 3.0.1-1
Description     : Nextcloud desktop client
Architecture    : x86_64

Offline

#3 2020-09-17 02:02:56

zaxmyth
Member
From: Seattle / San Francisco
Registered: 2019-03-25
Posts: 23
Website

Re: Nextcloud client 3.0.1 coredump

I just did a

pacman -Rcns nextcloud-client; pacman -S nextcloud-client

and got the same problem :-( Something else must be going on my system.

Offline

#4 2020-09-17 02:26:51

solskog
Member
Registered: 2020-09-05
Posts: 85

Re: Nextcloud client 3.0.1 coredump

Failed to create OpenGL context for format QSurfaceFormat

This seems to be graphic driver related. how about reinstall mesa?

Offline

#5 2020-09-17 04:02:18

loqs
Member
Registered: 2014-03-06
Posts: 11,565

Re: Nextcloud client 3.0.1 coredump

solskog wrote:

Failed to create OpenGL context for format QSurfaceFormat

This seems to be graphic driver related. how about reinstall mesa?

pacman -Qkk mesa

Unless that shows altered files reinstalling mesa will have no effect.

Offline

#6 2020-09-17 13:50:07

zaxmyth
Member
From: Seattle / San Francisco
Registered: 2019-03-25
Posts: 23
Website

Re: Nextcloud client 3.0.1 coredump

@loqs was right.

mesa: 80 total files, 0 altered files

I went ahead and reinstalled anyway, but no luck.

I'm wondering if there is something auth related going on here because of these findPassword related errors in that dump message:

LibSecretKeyring::findPassword

I recently converted my user to systemd-homed so there may be some lingering effect there? I have another Arch system with a normal password user and the latest version of Nextcloud is working fine.

Offline

#7 2020-09-17 13:54:22

interrupt
Member
Registered: 2018-04-08
Posts: 4

Re: Nextcloud client 3.0.1 coredump

Maybe try to reinstall (and recompile) qt5-styleplugins?

Offline

#8 2020-09-17 14:46:22

zaxmyth
Member
From: Seattle / San Francisco
Registered: 2019-03-25
Posts: 23
Website

Re: Nextcloud client 3.0.1 coredump

interrupt wrote:

Maybe try to reinstall (and recompile) qt5-styleplugins?

I don't have qt5-styleplugins installed. I tried installing it but it had no effect.

Offline

#9 2020-09-17 14:49:40

loqs
Member
Registered: 2014-03-06
Posts: 11,565

Re: Nextcloud client 3.0.1 coredump

What is the coredumpctl info for the core dump nextcloud produced?

Last edited by loqs (2020-09-17 14:49:52)

Offline

#10 2020-09-17 22:39:49

zaxmyth
Member
From: Seattle / San Francisco
Registered: 2019-03-25
Posts: 23
Website

Re: Nextcloud client 3.0.1 coredump

Message: Process 30328 (nextcloud) of user 1000 dumped core.
                
                Stack trace of thread 30328:
                #0  0x00007fe62a512615 raise (libc.so.6 + 0x3d615)
                #1  0x00007fe62a4fb862 abort (libc.so.6 + 0x26862)
                #2  0x00007fe62aa6d9ac _ZNK14QMessageLogger5fatalEPKcz (libQt5Core.so.5 + 0x909ac)
                #3  0x00007fe62c4d1a39 _ZN13QSGRenderLoop28handleContextCreationFailureEP12QQuickWindow (libQt5Quick.so.5 + 0x1d3a39)
                #4  0x00007fe62c4d2fa0 n/a (libQt5Quick.so.5 + 0x1d4fa0)
                #5  0x00007fe62c4d479a n/a (libQt5Quick.so.5 + 0x1d679a)
                #6  0x00007fe62b09ea55 _ZN7QWindow5eventEP6QEvent (libQt5Gui.so.5 + 0x146a55)
                #7  0x00007fe62b77f752 _ZN19QApplicationPrivate13notify_helperEP7QObjectP6QEvent (libQt5Widgets.so.5 + 0x15a752)
                #8  0x00007fe62ac90cda _ZN16QCoreApplication15notifyInternal2EP7QObjectP6QEvent (libQt5Core.so.5 + 0x2b3cda)
                #9  0x00007fe62b0938e0 _ZN22QGuiApplicationPrivate18processExposeEventEPN29QWindowSystemInterfacePrivate11ExposeEventE (libQt5Gui.so.5 + 0x13b8e0)
                #10 0x00007fe62b067bac _ZN22QWindowSystemInterface22sendWindowSystemEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE (libQt5Gui.so.5 + 0x10fbac)
                #11 0x00007fe61f707f9c n/a (libQt5XcbQpa.so.5 + 0x5ef9c)
                #12 0x00007fe633da1bfc g_main_context_dispatch (libglib-2.0.so.0 + 0x52bfc)
                #13 0x00007fe633df31f9 n/a (libglib-2.0.so.0 + 0xa41f9)
                #14 0x00007fe633da0421 g_main_context_iteration (libglib-2.0.so.0 + 0x51421)
                #15 0x00007fe62ace9941 _ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE (libQt5Core.so.5 + 0x30c941)
                #16 0x00007fe62ac8f65c _ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE (libQt5Core.so.5 + 0x2b265c)
                #17 0x00007fe62ac97af4 _ZN16QCoreApplication4execEv (libQt5Core.so.5 + 0x2baaf4)
                #18 0x000055952df7932c main (nextcloud + 0xa932c)
                #19 0x00007fe62a4fd152 __libc_start_main (libc.so.6 + 0x28152)
                #20 0x000055952df797ae _start (nextcloud + 0xa97ae)
                
                Stack trace of thread 30330:
                #0  0x00007fe62a5ca46f __poll (libc.so.6 + 0xf546f)
                #1  0x00007fe633df3188 n/a (libglib-2.0.so.0 + 0xa4188)
                #2  0x00007fe633da0421 g_main_context_iteration (libglib-2.0.so.0 + 0x51421)
                #3  0x00007fe633da0472 n/a (libglib-2.0.so.0 + 0x51472)
                #4  0x00007fe633dcea91 n/a (libglib-2.0.so.0 + 0x7fa91)
                #5  0x00007fe629f443e9 start_thread (libpthread.so.0 + 0x93e9)
                #6  0x00007fe62a5d5293 __clone (libc.so.6 + 0x100293)
                
                Stack trace of thread 30329:
                #0  0x00007fe62a5ca46f __poll (libc.so.6 + 0xf546f)
                #1  0x00007fe6273a163b n/a (libxcb.so.1 + 0xc63b)
                #2  0x00007fe6273a337b xcb_wait_for_event (libxcb.so.1 + 0xe37b)
                #3  0x00007fe61f706f61 n/a (libQt5XcbQpa.so.5 + 0x5df61)
                #4  0x00007fe62aaaae8f n/a (libQt5Core.so.5 + 0xcde8f)
                #5  0x00007fe629f443e9 start_thread (libpthread.so.0 + 0x93e9)
                #6  0x00007fe62a5d5293 __clone (libc.so.6 + 0x100293)
                
                Stack trace of thread 30335:
                #0  0x00007fe629f4a9c8 pthread_cond_timedwait@@GLIBC_2.3.2 (libpthread.so.0 + 0xf9c8)
                #1  0x00007fe62aab1058 _ZN14QWaitCondition4waitEP6QMutex14QDeadlineTimer (libQt5Core.so.5 + 0xd4058)
                #2  0x00007fe62aaaefc4 n/a (libQt5Core.so.5 + 0xd1fc4)
                #3  0x00007fe62aaaae8f n/a (libQt5Core.so.5 + 0xcde8f)
                #4  0x00007fe629f443e9 start_thread (libpthread.so.0 + 0x93e9)
                #5  0x00007fe62a5d5293 __clone (libc.so.6 + 0x100293)
                
                Stack trace of thread 30331:
                #0  0x00007fe62a5ca46f __poll (libc.so.6 + 0xf546f)
                #1  0x00007fe633df3188 n/a (libglib-2.0.so.0 + 0xa4188)
                #2  0x00007fe633da1163 g_main_loop_run (libglib-2.0.so.0 + 0x52163)
                #3  0x00007fe633c94fe8 n/a (libgio-2.0.so.0 + 0x101fe8)
                #4  0x00007fe633dcea91 n/a (libglib-2.0.so.0 + 0x7fa91)
                #5  0x00007fe629f443e9 start_thread (libpthread.so.0 + 0x93e9)
                #6  0x00007fe62a5d5293 __clone (libc.so.6 + 0x100293)
                
                Stack trace of thread 30337:
                #0  0x00007fe629f4a9c8 pthread_cond_timedwait@@GLIBC_2.3.2 (libpthread.so.0 + 0xf9c8)
                #1  0x00007fe62aab1058 _ZN14QWaitCondition4waitEP6QMutex14QDeadlineTimer (libQt5Core.so.5 + 0xd4058)
                #2  0x00007fe62aaaefc4 n/a (libQt5Core.so.5 + 0xd1fc4)
                #3  0x00007fe62aaaae8f n/a (libQt5Core.so.5 + 0xcde8f)
                #4  0x00007fe629f443e9 start_thread (libpthread.so.0 + 0x93e9)
                #5  0x00007fe62a5d5293 __clone (libc.so.6 + 0x100293)
                
                Stack trace of thread 30340:
                #0  0x00007fe62a5ca

Offline

#11 2020-09-17 22:44:14

loqs
Member
Registered: 2014-03-06
Posts: 11,565

Re: Nextcloud client 3.0.1 coredump

What is the output of glxinfo? (needs the mesa-demos package)

Offline

#12 2020-09-18 15:56:40

zaxmyth
Member
From: Seattle / San Francisco
Registered: 2019-03-25
Posts: 23
Website

Re: Nextcloud client 3.0.1 coredump

I saved the entire output to a gist here: https://gist.github.com/zachsmith/d6f5c … 6956c9d975

Offline

#13 2020-09-18 16:02:28

zaxmyth
Member
From: Seattle / San Francisco
Registered: 2019-03-25
Posts: 23
Website

Re: Nextcloud client 3.0.1 coredump

I will add though that glxgears fails to run properly so something is wrong... When I run with the NVIDIA driver 450.66-21 I am getting artifacts or a blank window. https://imgur.com/gallery/MiyvKup

Offline

#14 Yesterday 18:58:01

zaxmyth
Member
From: Seattle / San Francisco
Registered: 2019-03-25
Posts: 23
Website

Re: Nextcloud client 3.0.1 coredump

I started having all sorts of issues with my Thinkpad X1E2 with NVIDIA and OpenGL. I have had optimus-manager configured for about 9 months and working correctly. I used the iGPU 99% of the time and only switched to NVIDIA for external monitor support but since I haven't needed that in a long time so I just disabled all NVIDIA support for now. I removed nvidia, nvidia-utils, and optimus-manager, blacklisted nouveau, replaced gpm-prime with gdm, and setup a udev rule to power-off the NVIDIA card entirely. This is a workaround for now and makes my system and Nextcloud usable again but isn't a solution to the problem so I'm not marking this as "solved".

I'll revisit this all again in the future when I need the NVIDIA card for something but until then I'm happy with just disabling it.

If somebody else out there has an actual solution or a better explanation of the underlying problem(s) feel free to share.

Last edited by zaxmyth (Yesterday 18:58:53)

Offline

Board footer

Powered by FluxBB