Yup, it’s working now, thanks @ivaradi! Installed the -dbgsym packages and reproduced the segfault, here’s the gist.
(TBH, I’m just cargo culting from the wiki here, so I have no idea if this result is useful, but I do have a fairly solid way of triggering the issue, so just let me know if I should do something differently.)
Updated client to 3.0.1 and the issue persists.
Selecting ”open main dialog” from the client menu brings up the main dialog.
Selecting ”open main dialog” from the client menu either does not bring up the main dialog, or brings it up only to have it disappear almost immediately. The location of the main dialog, when it does pop up, also seems random: sometimes it pops up in the top left corner of the scereen, sometimes at the center of the screen, sometimes right where the tray menu is.
If I’m quick enough to bring the mouse cursor over the main dialog when it pops up, the window seems to stay, until I take the cursor out of it, at which point the window disappears.
The settings window does still open as normal when selected, and works without issues.
Client version: 3.0.0-20200821.171045.ff175088a-1.0~focal1
Operating system: Ubuntu 20.04, Wayland
OS language: Finnish
Qt version used by client package (Linux only, see also Settings dialog): Don’t know where to find that. The settings dialog only says ”Version 3.0.0 (Ubuntu)” AFAICT.
Client package (From Nextcloud or distro) (Linux only): Don’t understand the question.
Installation path of client: /usr/bin/nextcloud
The client debug log from the time of trying to open the main dialog shows this:
2020-08-28 19:50:04:856 [ debug nextcloud.gui.systray ] [ OCC::Systray::computeWindowReferencePoint ]: screenRect: QRect(0,0 2560x1440)
2020-08-28 19:50:04:856 [ debug nextcloud.gui.systray ] [ OCC::Systray::computeWindowReferencePoint ]: taskbarRect: QRect(0,0 2560x32)
2020-08-28 19:50:04:856 [ debug nextcloud.gui.systray ] [ OCC::Systray::computeWindowReferencePoint ]: taskbarScreenEdge: OCC::Systray::TaskBarPosition::Top
2020-08-28 19:50:04:856 [ debug nextcloud.gui.systray ] [ OCC::Systray::computeWindowReferencePoint ]: trayIconCenter: QPoint(73,507)
2020-08-28 19:50:04:856 [ debug nextcloud.gui.systray ] [ OCC::Systray::computeWindowPosition ]: taskbarScreenEdge: OCC::Systray::TaskBarPosition::Top
2020-08-28 19:50:04:856 [ debug nextcloud.gui.systray ] [ OCC::Systray::computeWindowPosition ]: screenRect: QRect(0,0 2560x1440)
2020-08-28 19:50:04:856 [ debug nextcloud.gui.systray ] [ OCC::Systray::computeWindowPosition ]: windowRect (reference) QRect(-127,36 401x511)
2020-08-28 19:50:04:856 [ debug nextcloud.gui.systray ] [ OCC::Systray::computeWindowPosition ]: windowRect (adjusted ) QRect(4,36 401x511)
2020-08-28 19:50:04:859 [ warning default ]: qrc:/qml/src/gui/tray/UserLine.qml:46: TypeError: Type error
2020-08-28 19:50:04:861 [ warning default ]: qrc:/qml/src/gui/tray/UserLine.qml:46: TypeError: Type error
2020-08-28 19:50:04:863 [ warning default ]: qrc:/qml/src/gui/tray/UserLine.qml:46: TypeError: Type error
2020-08-28 19:50:04:865 [ warning default ]: qrc:/qml/src/gui/tray/UserLine.qml:46: TypeError: Type error
2020-08-28 19:50:04:868 [ info nextcloud.sync.accessmanager ]: 2 "" "https://(MY SERVER URL)/ocs/v2.php/apps/notifications/api/v2/notifications?format=json" has X-Request-ID "b0e242bb-588d-455f-a53d-066d8d0b9f42"
2020-08-28 19:50:04:868 [ debug nextcloud.sync.cookiejar ] [ OCC::CookieJar::cookiesForUrl ]: (REDACTED)
2020-08-28 19:50:04:869 [ info nextcloud.sync.networkjob ]: OCC::JsonApiJob created for "https://(MY SERVER URL)" + "ocs/v2.php/apps/notifications/api/v2/notifications" "OCC::ServerNotificationHandler"
2020-08-28 19:50:04:886 [ warning default ]: qrc:/qml/src/gui/tray/Window.qml:473:17: QML MouseArea: Detected anchors on an item that is managed by a layout. This is undefined behavior; use Layout.alignment instead.
2020-08-28 19:50:04:886 [ warning default ]: qrc:/qml/src/gui/tray/Window.qml:496:17: QML Image: Detected anchors on an item that is managed by a layout. This is undefined behavior; use Layout.alignment instead.
2020-08-28 19:50:04:886 [ warning default ]: qrc:/qml/src/gui/tray/Window.qml:510:17: QML Column: Detected anchors on an item that is managed by a layout. This is undefined behavior; use Layout.alignment instead.
2020-08-28 19:50:04:886 [ warning default ]: qrc:/qml/src/gui/tray/Window.qml:547:17: QML Button: Detected anchors on an item that is managed by a layout. This is undefined behavior; use Layout.alignment instead.
2020-08-28 19:50:04:886 [ warning default ]: qrc:/qml/src/gui/tray/Window.qml:487: ReferenceError: hovered is not defined
Meanwhile, in syslog from the time:
Aug 28 19:50:04 saegusa gnome-shell[4105]: Window manager warning: Invalid WM_TRANSIENT_FOR window 0x4200016 specified for 0x4200014.
Aug 28 19:50:31 saegusa gnome-shell[4105]: Window manager warning: Invalid WM_TRANSIENT_FOR window 0x4200016 specified for 0x4200014.
Aug 28 19:50:35 saegusa gnome-shell[4105]: Window manager warning: Invalid WM_TRANSIENT_FOR window 0x4200016 specified for 0x4200014.
Aug 28 19:50:47 saegusa kernel: [17841.949249] nextcloud[55212]: segfault at ffffffffffffffff ip 00007f2b3b765671 sp 00007ffe18796c78 error 5 in libgobject-2.0.so.0.6400.3[7f2b3b737000+36000]
Aug 28 19:50:47 saegusa kernel: [17841.949258] Code: b5 2c 02 00 48 8b 34 d8 eb b6 66 66 2e 0f 1f 84 00 00Folders for auto upload? I have Camera twice (/storage/emulated/0/DCIM/Camera; once for pictures, the other for videos), OpenCamera (/storage/emulated/0/DCIM/OpenCamera) and Screenshots (/storage/emulated/0/DCIM/Screenshots).
(I only tried OpenCamera briefly, recently, and have since uninstalled it. The issue at hand was present already back when I first got this phone and installed Nextcloud on it, last July.)
I’ve always had auto upload enabled until now, so can’t say whether it’s dependent on that. I could try disabling it next time the issue re-emerges; as dictated by Murphy’s law, I was unable to trigger it just now that I intentionally tried to.
Oh, and I am running Beta (so currently 3.11.0 RC4) of the Nextcloud app. Can’t remember when I enrolled in.
Here’s output from logcat:
03-19 16:33:47.099 20119 20119 E AndroidRuntime: FATAL EXCEPTION: main
03-19 16:33:47.099 20119 20119 E AndroidRuntime: Process: android.process.media, PID: 20119
03-19 16:33:47.099 20119 20119 E AndroidRuntime: java.lang.RuntimeException: Unable to start receiver com.android.providers.media.MediaScannerReceiver: java.lang.StringIndexOutOfBoundsException: length=1; index=-3
03-19 16:33:47.099 20119 20119 E AndroidRuntime: at android.app.ActivityThread.handleReceiver(ActivityThread.java:3619)
03-19 16:33:47.099 20119 20119 E AndroidRuntime: at android.app.ActivityThread.access$1300(ActivityThread.java:237)
03-19 16:33:47.099 20119 20119 E AndroidRuntime: at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1803)
03-19 16:33:47.099 20119 20119 E AndroidRuntime: at android.os.Handler.dispatchMessage(Handler.java:106)
03-19 16:33:47.099 20119 20119 E AndroidRuntime: at android.os.Looper.loop(Looper.java:214)
03-19 16:33:47.099 20119 20119 E AndroidRuntime: at android.app.ActivityThread.main(ActivityThread.java:7078)
03-19 16:33:47.099 20119 20119 E AndroidRuntime: at java.lang.reflect.Method.invoke(Native Method)
03-19 16:33:47.099 20119 20119 E AndroidRuntime: at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:494)
03-19 16:33:47.099 20119 20119 E AndroidRuntime: at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:964)
03-19 16:33:47.099 20119 20119 E AndroidRuntime: Caused by: java.lang.StringIndexOutOfBoundsException: length=1; index=-3
03-19 16:33:47.099 20119 20119 E AndroidRuntime: at java.lang.String.substring(String.java:1995)
03-19 16:33:47.099 20119 20119 E AndroidRuntime: at com.android.providers.media.utils.MPLogger.log(MPLogger.java:118)
03-19 16:33:47.099 20119 20119 E AndroidRuntime: at com.android.providers.media.MediaProvider.call(MediaProvider.java:5073)
03-19 16:33:47.099 20119 20119 E AndroidRuntime: at android.content.ContentProvider$Transport.call(ContentProvider.java:403)
03-19 16:33:47.099 20119 20119 E AndroidRuntime: at android.content.ContentResolver.call(ContentResolver.java:1763)
03-19 16:33:47.099 20119 20119 E AndroidRuntime: at com.android.providers.media.MediaScannerReceiver.logToDb(MediaScannerReceiver.java:139)
03-19 16:33:47.099 20119 20119 E AndroidRuntime: at com.android.providers.media.MediaScannerReceiver.onReceive(MediaScannerReceiver.java:77)
03-19 16:33:47.099 20119 20119 E AndroidRuntime: at android.app.ActivityThread.handleReceiver(ActivityThread.java:3610)
03-19 16:33:47.099 20119 20119 E AndroidRuntime: ... 8 more
The upload process (I think) then dies:
03-19 16:33:47.164 2044 13653 I ActivityManager: Killing 20133:com.nextcloud.client/u0a0 (adj 100): depends on provider com.android.providers.media/.MediaProvider in dying proc android.process.media (adj 100)
I have the same issue on my Samsung Galaxy A9 phone, with ”android.process.media has stopped” appearing for virtually every photo taken (though the uploads seem to still go through). My Samsung Galaxy Tab S5e does not have the same issue, nor do I recall seeing this on any other Android devices (from other manufacturers).
I don’t use alarmapp (to my knowledge, though I’m not sure which app that is).
@juliushaertl Is backporting for docs also done as per the manual? It seems pretty straightforward, so I think I can produce those pull requests too, if needed.
Fix indefinite article before Nextcloud (an->a)
Sorry for necromancing, but because Google seems to like this thread, I just thought I’d add a mention that a check_data_directory_permissions option for config.php has since been implemented (and backported down to NC12), and it allows the admin to turn off the automatic permissions reset (by assigning it false).
This is discouraged however, and ACLs or other means of managing access are still the better option where available.