As of late last week, the Linux Client 2.4.2 has started throwing a SegFault on startup (when starting on the command line). Previously, I had noticed issues with automatic startup, but it had been starting manually. Previously running for years.
Seeing an error on /usr/share/applications/owncloud.desktop in the journal, … it appears to be looking for owncloud.desktop;5a0b469d - might that be related?
Cannot confirm that it is actually a Bug, as the same client runs on other machines just fine. Just looking for a way to isolate the problem - tried a clean install today (after deleting the config in ~/.local/owncloud), but same problem.
If you think that is the best place to post, however, I can.
i don’t think that is a reasonable explanation for your statement. If you do some research on the topic “Segmentation fault” then you might find the information that this is just a generic error which can tons of different reasons why those are happening.
Even i have limited experience on this topic i highly doubt that a “Segmentation fault” happened two years ago has the same reason / is the same problem / issue like today. You can even get segmentation faults if the memory of your PC is damages or if there is an issue on your operating system itself.
Just blaming the devs about something which probably not even has any justification doesn’t help anyone.
I have just installed OwnCloud Client 2.4.2 on OpenSUSE Leap 15, and I get a segmentation fault every time it starts.
Nov 19 19:36:40 coalriver.simsnc.org kernel: owncloud[4737]: segfault at 0 ip 0000559f61a0f97e sp 00007ffcbe5ca8f0 error 4 in owncloud[559f6190a000+263000]