Owncloud client crash on windows 10

morellik · March 1, 2019, 3:46pm

I’ve a strange problem on a windows 10 64bit. Opening the latest client version or the previous one, it crash.
I tried to move the owncloud configuration to create a new one, the client starts, show the windows where ask the server and after few seconds crash. Starting the client with --logwindow and --logfile doesn’t show nothing.
I tried to uninstall and reinstall the client and the testpilot, but nothing, both crashes.

I created a new user and magically the client starts. The strange thing is that if I logout from the new user and I login with the old user, the client starts without problem. If I reboot the machine and I login with the old user, the client crash.

Before backup all old user data to create a new one, someone can help me to solve the problem?

Thanks

michaelstingl · March 1, 2019, 6:16pm

Did you send the crashlog? Could you write the ID you’ve got?

morellik · March 4, 2019, 7:45am

I sent the crash log, but it’s empty

michaelstingl · March 4, 2019, 8:33am

In the crash window, there should be an ID like this:
bp-540f2d01-5db9-71e9-9a90-2157d3a47566

Could you check again and post here?

morellik · March 4, 2019, 10:25am

Sorry, but the crash window is emtpy.

morellik · March 5, 2019, 1:56pm

Other suggestion?
As I already explained the client doesn’t write information about it’s crash.

dmitry · March 5, 2019, 4:32pm

can you start the client from command line with --logdebug?

https://doc.owncloud.com/desktop/advanced_usage/options.html

morellik · March 6, 2019, 10:11am

I tried, but the client crash without message. I tried also to redirect the log but the file is empty.

Another test I tried was to rename OwnCloud folder in AppData\Roaming, but the application crash before write new information in the new OwnCloud folder.

dmitry · March 6, 2019, 10:20am

Having something similar on my hands. Try to disable the auto updater.

https://doc.owncloud.com/desktop/installing.html#disabling-automatic-updates

morellik · March 6, 2019, 10:51am

You are great! It’s seems to work.

dmitry · March 6, 2019, 12:08pm

Can you send us a screenshot of the empty crash reporter?

We are trying to get to the bottom of this

morellik · March 6, 2019, 2:55pm

I’ll send the screenshot tomorrow

morellik · March 8, 2019, 9:57am

I’m sorry but I was unable to reproduce the problem. After I’d installed disabling the auto updater I solved the problem. I tried to uninstall and reinstall the client in the normal way but now it’s working fine. No crash.

I recover the output file I used with --logwindow and --logfile, I hope this help you:

|03-01 15:46:24:196 [ info gui.application ]:|"################## ownCloud locale:[en_US] ui_lang:[] version:[2.5.0 (build 10560)] os:[Windows 10 (10.0)]"|
|---|---|
|03-01 15:46:24:198 [ info gui.application ]:|Using "en_US" translation|
|03-01 15:46:24:223 [ info gui.socketapi ]:|server started, listening at  "\\\\.\\pipe\\ownCloud-luchinat"|
|03-01 15:46:24:223 [ info gui.folder.manager ]:|setting remote poll timer interval to 30000 msec|
|03-01 15:46:24:224 [ info gui.account.manager ]:|Migrate: restoreFromLegacySettings, checking settings group "ownCloud"|
|03-01 15:46:24:224 [ info gui.account.manager ]:|Migrate: checking old config  "C:/Users/luchinat/AppData/Roaming/ownCloud/owncloud.cfg"|
|03-01 15:46:25:355 [ info gui.application ]:|Tray menu workarounds: noabouttoshow: false fakedoubleclick: false showhide: false manualvisibility: false|
|03-01 15:46:25:462 [ info gui.folder.manager ]:|Setup folders from  "C:/Users/luchinat/AppData/Roaming/ownCloud/folders" (migration)|
|03-01 15:46:25:518 [ info sync.clientproxy ]:|Set proxy configuration to use system configuration|
|03-01 15:46:25:571 [ info gui.application ]:|No configured folders yet, starting setup wizard|
|03-01 15:46:26:359 [ info gui.socketapi ]:|New connection QLocalSocket(0x67173b0)|
|03-01 15:46:28:560 [ info gui.updater ]:|Checking for available update|
|03-01 15:46:28:562 [ info sync.accessmanager ]:|2 "" "https://updates.owncloud.com/client/?version=2.5.0.10560&platform=win32&oem=ownCloud&versionsuffix=&msi=true" has X-Request-ID "843f8ea4-47ef-4e63-a921-2649ce2b5e0a"|

Rldeckard · July 7, 2020, 5:48pm

Same thing is happening to me. Here’s the empty report

michaelstingl · July 10, 2020, 9:10am

@Rldeckard better open a new thread. This one is too old.

The ID is needed that is shown on the next screen.

bencgreen · September 3, 2020, 12:01pm

This is happening frequently for various machines in my group - though everything is working fine for me. I shall try disabling the automatic updater - is there any way of reading the crash report to see what the issue actually is?

michaelstingl · September 3, 2020, 12:30pm

@bencgreen do you know the “steps to reproduce” ? Could you start a new topic and provide all information?

bencgreen · September 3, 2020, 1:00pm

Steps to reproduce: ‘Boot PC’ (!). Happens every time they boot. I’ve tried reinstalling the client and doing a repair, removing and adding the account. But I feel like I’m flying blind. Every time I ask them to submit the crash report, but it would be helpful to see a little more info as even a hint of what’s going wrong might help. As I say, it works fine on my PC so the problem presumably isn’t the server but the setup? I can start a new topic - but I’ll try disabling automatic updates first in case it’s that.

bencgreen · September 6, 2020, 10:05am

@michaelstingl I have created a new topic here. I think I’ve tracked down the source of the issue using --logwindow --logdebug.

fenneries · November 18, 2020, 12:51pm

I am a new member and not experienced user.
I have the same problem of the desktop crashing always after having started it. I get the crash log, which I sent many times. When sending the crash report window is often empty, but shows up at the bottom that
cf380b37-d304-457a-b6e1-a83275ef2628
has been sent

I tried to disable the auto updater, but a) I don’t know if I succeded, b) the problem still exists.

Any help or recommendations to solve the problem are welcome.