View previous topic :: View next topic |
Author |
Message |
lonex Tux's lil' helper
Joined: 22 Aug 2004 Posts: 109 Location: Karlsruhe, Germany
|
Posted: Mon Nov 04, 2024 3:47 pm Post subject: [solved] Can't start nextcloud-client anymore |
|
|
Hello,
I have been using nextcloud-client in the past to sync files to my nextcloud instance.
Today I noticed that its tray icon was missing, so I tried to start it manually. Still not working.
When I start it from the command line, it shows a segfault directly after start, and in dmesg it prints the following:
Code: | [ 9803.413903] nextcloud[30903]: segfault at 8 ip 00007f4ebccae594 sp 00007ffde9425a98 error 4 in libQt5Core.so.5.15.14[7f4ebca77000+2de000] likely on CPU 8 (core 0, socket 0)
[ 9803.413917] Code: 01 01 f6 0f b6 51 20 89 d0 83 e2 fd d0 e8 09 f2 83 e0 01 88 51 20 c3 90 66 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 00 f3 0f 1e fa <48> 8b 47 08 48 8b 40 38 48 8b 40 38 c3 66 66 2e 0f 1f 84 00 00 00 |
I already tried to rebuild nextcloud-client and also qtcore, but it still does not change this behaviour.
The system has been fully updated today, and revdep-rebuild also shows no problems.
Any other ideas that I could follow up to fix this?
Last edited by lonex on Tue Nov 05, 2024 10:44 am; edited 1 time in total |
|
Back to top |
|
|
lonex Tux's lil' helper
Joined: 22 Aug 2004 Posts: 109 Location: Karlsruhe, Germany
|
|
Back to top |
|
|
Hu Administrator
Joined: 06 Mar 2007 Posts: 22853
|
Posted: Tue Nov 05, 2024 1:33 pm Post subject: |
|
|
In my opinion, it is premature to mark this thread as solved.
First, there is no explanation for why LTO does not work. LTO should work, though it may require fixes upstream to reach that point. I see nothing in the linked Github issue that diagnoses the root cause or attempts to fix the crash.
Second, until LTO does work, it would be nice to have the ebuild disable LTO so that users cannot build a known-broken configuration. I see no reference here to a Gentoo bug report for this. However, on searching, I found net-misc/nextcloud-client-3.12.3: segmentation fault when LTO is enabled, which may or may not be the same problem. This thread does not specify the faulting version, nor provide a backtrace to confirm that it is the same fault. |
|
Back to top |
|
|
|
|
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum
|
|