Line apps crashed after update, please help

Questions about Wine on Linux
Locked
michaelbr
Level 2
Level 2
Posts: 25
Joined: Fri Sep 07, 2018 9:16 am

Line apps crashed after update, please help

Post by michaelbr »

Today, after I logged in Line, got a message to update it, I clicked OK and seems to start update, after awhile, it crashed. Tried to remove Wine & winetricks, and reinstall them to no avail (after the reinstall still crashed). How do I fix it? Please note that I'm not that familiar with Wine/winetricks or even Linux, so if you can be kind to explain step by step, it's much appreciated. Thanks.
my system:
Ubuntu 16.04
Wine 4.0~Xenial
winetricks 0.0+20141009+svn1208-2ubuntu1
ps: when I run winetricks --version, got this

Code: Select all

20181203-next
Thanks
jkfloris
Level 12
Level 12
Posts: 3136
Joined: Thu Aug 14, 2014 10:10 am

Re: Line apps crashed after update, please help

Post by jkfloris »

after awhile, it crashed
You could start the program from the command line. Often there are clues what went wrong.
michaelbr
Level 2
Level 2
Posts: 25
Joined: Fri Sep 07, 2018 9:16 am

Re: Line apps crashed after update, please help

Post by michaelbr »

jkfloris wrote: You could start the program from the command line. Often there are clues what went wrong.
Sorry for this dumb question, but where is Line installed? I went to .wine dir in my home, but I can't find it.
jkfloris
Level 12
Level 12
Posts: 3136
Joined: Thu Aug 14, 2014 10:10 am

Re: Line apps crashed after update, please help

Post by jkfloris »

You could find the location in the .desktop shortcut file. Probably it is:

Code: Select all

.wine/drive_c/users/<user name>/Local Settings/Application Data/LINE/bin
michaelbr
Level 2
Level 2
Posts: 25
Joined: Fri Sep 07, 2018 9:16 am

Re: Line apps crashed after update, please help

Post by michaelbr »

jkfloris wrote:You could find the location in the .desktop shortcut file. Probably it is:

Code: Select all

.wine/drive_c/users/<user name>/Local Settings/Application Data/LINE/bin
Thanks jkfloris for the tips, I entered the command and got this back:

Code: Select all

0009:fixme:shcore:SetCurrentProcessExplicitAppUserModelID L"C:\\users\\michael\\Local Settings\\Application Data\\LINE\\bin\\LineLauncher.exe": stub
0009:fixme:toolhelp:CreateToolhelp32Snapshot Unimplemented: heap list snapshot
0009:fixme:toolhelp:CreateToolhelp32Snapshot Unimplemented: heap list snapshot
0009:fixme:toolhelp:CreateToolhelp32Snapshot Unimplemented: heap list snapshot
0009:fixme:ver:GetCurrentPackageId (0x33f584 (nil)): stub
002a:fixme:toolhelp:CreateToolhelp32Snapshot Unimplemented: heap list snapshot
0009:fixme:toolhelp:CreateToolhelp32Snapshot Unimplemented: heap list snapshot
0009:fixme:toolhelp:CreateToolhelp32Snapshot Unimplemented: heap list snapshot
002a:err:winediag:SECUR32_initNTLMSP ntlm_auth was not found or is outdated. Make sure that ntlm_auth >= 3.0.25 is in your path. Usually, you can find it in the winbind package of your distribution.
0009:fixme:toolhelp:CreateToolhelp32Snapshot Unimplemented: heap list snapshot
0009:fixme:toolhelp:CreateToolhelp32Snapshot Unimplemented: heap list snapshot
002a:fixme:msvcp:_Mtx_init_in_situ unknown flags ignored: 2
002a:fixme:msvcp:_Mtx_init_in_situ unknown flags ignored: 2
002a:fixme:msvcp:_Mtx_init_in_situ unknown flags ignored: 2
002a:fixme:msvcp:_Mtx_init_in_situ unknown flags ignored: 2
002a:fixme:msvcp:_Mtx_init_in_situ unknown flags ignored: 2
002a:fixme:msvcp:_Locinfo__Locinfo_ctor_cat_cstr (0x33f008 1 C) semi-stub
002a:fixme:shcore:SetCurrentProcessExplicitAppUserModelID L"C:\\users\\michael\\Local Settings\\Application Data\\LINE\\bin\\LineLauncher.exe": stub
002a:fixme:file:FindFirstFileExW flags not implemented 0x00000002
002b:fixme:ver:GetCurrentPackageId (0x813febc (nil)): stub
0009:fixme:toolhelp:CreateToolhelp32Snapshot Unimplemented: heap list snapshot
002a:fixme:sync:SetWaitableTimerEx (0x154, 0x33f6bc, 0, (nil), (nil), (nil), 32) semi-stub
002a:fixme:win:EnumDisplayDevicesW ((null),0,0x33f284,0x00000000), stub!
002a:fixme:msvcp:_Locinfo__Locinfo_ctor_cat_cstr (0x33f458 1 C) semi-stub
002a:fixme:msvcp:_Mtx_init_in_situ unknown flags ignored: 2
002a:fixme:msvcp:_Mtx_init_in_situ unknown flags ignored: 2
002a:fixme:msvcp:_Mtx_init_in_situ unknown flags ignored: 102
002a:fixme:msvcp:_Locinfo__Locinfo_ctor_cat_cstr (0x3374f8 1 C) semi-stub
002a:fixme:msvcp:_Locinfo__Locinfo_ctor_cat_cstr (0x3372c8 1 C) semi-stub
002a:fixme:msvcp:_Mtx_init_in_situ unknown flags ignored: 2
002a:fixme:msvcp:_Mtx_init_in_situ unknown flags ignored: 2
002a:fixme:msvcp:_Mtx_init_in_situ unknown flags ignored: 102
002a:fixme:msvcp:_Locinfo__Locinfo_ctor_cat_cstr (0x33f108 1 C) semi-stub
002a:fixme:advapi:LsaOpenPolicy ((null),0x33f480,0x00000001,0x33f478) stub
002a:fixme:advapi:LsaClose (0xcafe) stub
0032:fixme:msvcp:_Locinfo__Locinfo_ctor_cat_cstr (0x94ef818 1 C) semi-stub
002a:fixme:toolhelp:CreateToolhelp32Snapshot Unimplemented: heap list snapshot
Thanks
jkfloris
Level 12
Level 12
Posts: 3136
Joined: Thu Aug 14, 2014 10:10 am

Re: Line apps crashed after update, please help

Post by jkfloris »

002a:err:winediag:SECUR32_initNTLMSP ntlm_auth was not found or is outdated. Make sure that ntlm_auth >= 3.0.25 is in your path. Usually, you can find it in the winbind package of your distribution.
I am not sure if it is necessary, but there is no harm in solving this error.

To get the program running, try:

Code: Select all

winetricks vcrun2015
michaelbr
Level 2
Level 2
Posts: 25
Joined: Fri Sep 07, 2018 9:16 am

Re: Line apps crashed after update, please help

Post by michaelbr »

jkfloris wrote:
I am not sure if it is necessary, but there is no harm in solving this error.

To get the program running, try:

Code: Select all

winetricks vcrun2015
@jkfloris, thanks so much for your help, yes this solved the problem. Just curious, why this solved the error? It's not required, is it?
lahmbi5678
Level 7
Level 7
Posts: 823
Joined: Thu Aug 27, 2009 6:23 am

Re: Line apps crashed after update, please help

Post by lahmbi5678 »

Wine's implementation of the VC runtime libraries isn't complete, and sometimes implemented functions aren't 100% correct. In your case it would absolutely be justified to file a bug report, even if it works with a winetricks workaround. Filing bugs like these will help the wine project in the long run.
Locked