segfault message while closing nextcloud-client through the systray applet

squid-f commented 2 years ago

How to use GitHub

Please use the 👍 reaction to show that you are affected by the same issue.
Please don't comment if you have no relevant information to add. It's just extra noise for everyone subscribed to this issue.
Subscribe to receive notifications on status change and new comments.

Expected behaviour

nextcloud-client shuts down without a segfault message in the journal.

Last lines in $HOME/.config/Nextcloud/logs

2022-02-03 10:57:02:898 [ info nextcloud.sync.database /home/iurt/rpmbuild/BUILD/desktop-3.4.2/src/common/syncjournaldb.cpp:631 ]:  Closing DB "/home/toto/Musique/.sync_c3f2e524e2be.db"
2022-02-03 10:57:02:911 [ debug nextcloud.gui.socketapi /home/iurt/rpmbuild/BUILD/desktop-3.4.2/src/gui/socketapi/socketapi.cpp:296 ]   [ OCC::SocketApi::~SocketApi ]: dtor
2022-02-03 10:57:02:911 [ info nextcloud.gui.socketapi /home/iurt/rpmbuild/BUILD/desktop-3.4.2/src/gui/socketapi/socketapi.cpp:331 ]:   Lost connection  QLocalSocket(0x563deefc8e30)

Actual behaviour

content of journaltctl -f in a terminal:

févr. 03 13:44:41 cbct-desk kernel: nextcloud[2192]: segfault at ffffffffffffffff ip 00007f5c47936a6d sp 00007ffed09d43e8 error 5 in libgobject-2.0.so.0.6600.8[7f5c47911000+2e000]
févr. 03 13:44:41 cbct-desk kernel: Code: 02 48 8d 05 75 3c 02 00 48 8b 34 d8 eb b6 66 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 40 00 48 85 ff 74 4b 48 8b 07 48 85 c0 74 43 <48> 8b 00 48 3d fc 03 00 00 76 18 48 83 e0 fc 0f b6 50 14 45 31 c0

Last lines in $HOME/.config/Nextcloud/logs

2022-02-03 13:44:41:441 [ info nextcloud.sync.database /home/iurt/rpmbuild/BUILD/desktop-3.4.2/src/common/syncjournaldb.cpp:631 ]:  Closing DB "/home/toto/Phone/.sync_aa693ce78ebd.db"
2022-02-03 13:44:41:441 [ debug nextcloud.sync.database /home/iurt/rpmbuild/BUILD/desktop-3.4.2/src/common/syncjournaldb.cpp:246 ]  [ OCC::SyncJournalDb::commitTransaction ]:  No database Transaction to commit

Steps to reproduce

1.Open a terminal window and run journalctl -f 2.Right click on the systray applet of nextcloud-client 3.Click on Exit Nextcloud

It has been reproduced by another user, on another machine using the same system. I have a VM with the same system not exhibiting the issue. It looks like it doesn't happen all the time on my machine, even if it is quite reproducible.

Client configuration

Client version: 3.4.2 (also noticed with 3.3.6)

Operating system: Mageia 8 Linux, Plasma x86_64

OS language: French or Swedish or English

Qt version used by client package (Linux only, see also Settings dialog): 5.15.2

Client package (From Nextcloud or distro) (Linux only): nextcloud-client-3.4.2-1.mga8.x86_64.rpm

Installation path of client: /usr/bin and /usr/share

Server configuration

Nextcloud version: 22.2.3

Storage backend (external storage): n/a

Logs

Please use Gist (https://gist.github.com/) or a similar code paster for longer logs.

Client logfile: segfaut3.4.2.zip Since 3.1: Under the "General" settings, you can click on "Create Debug Archive ..." to pick the location of where the desktop client will export the logs and the database to a zip file. On previous releases: Via the command line: nextcloud --logdebug --logwindow or nextcloud --logdebug --logfile log.txt (See also https://docs.nextcloud.com/desktop/3.0/troubleshooting.html#log-files)
Web server error log: none
Server logfile: nextcloud log (data/nextcloud.log): no info related to the issue

Morganlej commented 2 years ago

I am the other user mentioned, client 3.4.2, Mageia 8, Plasma, x86_64 It probably does not matter, but server version in my case is 21.0.4. Two server instances at owncube.

I now see it does not happen on my wifes laptop, even though it is same Mageia version, Plasma, and installed by same Mageia rpm. One difference i can think of is that it is only syncing with one of the two servers.

Both systems have had several versions of Nextcloud client, but the problematic one is eldest.

github-actions[bot] commented 2 years ago

This bug report did not receive an update in the last 4 weeks. Please take a look again and update the issue with new details, otherwise the issue will be automatically closed in 2 weeks. Thank you!

squid-f commented 2 years ago

This bug report did not receive an update in the last 4 weeks. Please take a look again and update the issue with new details, otherwise the issue will be automatically closed in 2 weeks. Thank you!

Hi. I would be glad to do so, but what else do you need?

github-actions[bot] commented 2 years ago

This bug report did not receive an update in the last 4 weeks. Please take a look again and update the issue with new details, otherwise the issue will be automatically closed in 2 weeks. Thank you!

squid-f commented 2 years ago

Well, same comment, what else do you need? Just let me know.

github-actions[bot] commented 2 years ago

This bug report is getting automatically closed due to no answer since the issue has been staled. Thank you!

nextcloud / desktop