Forum Home
Press F1
 
Thread ID: 147481 2018-12-28 04:32:00 One for the Linux – Mint – Cinnamon Gurus. B.M. (505) Press F1
Post ID Timestamp Content User
1456929 2018-12-28 04:32:00 Overview: I’ve been given a couple of Laptops that have been replaced by later models.

Both had Windows 10 installed which I was told was working OK but which I chose to unceremoniously ditch.

Now seeing I have only ever used Mint 18 – Cinnamon, I thought I’d put different versions on different machines to try out.

Machine #1 installed Mint 18.1 and everything worked fine including Programmes written for Windows.

Machine #2 installed Mint 18.2 and the Mint side of things worked fine but a Windows programme I wanted didn’t, and removing and reinstalling the subject programme, and Wine, didn’t fix the problem.

I then installed Mint 18.3 alongside 18.2 but exactly the same problem.

Soooo, I thought I’d install from my original Disk Mint 18 alongside 18.3 and 18.2.

Again the Mint programme worked fine, but the one written for Windows didn’t, although it looked like it installed ok.

Wine was installed on by way of Synaptic Packet Manager on all versions.

Moving along.

The Windows programme I want to get working is PicPick, which is a neat little programme that can take screenshots, edit pictures, (Resize, Crop, Rotate, Flip, Insert Text, etc and save in various formats).

Possible Clues.

Here is a Screenshot of the Error Message I get when trying to open the programme. (Taken with “Screenshot” which comes with Mint)

9271

And here is the command line taken from the Icon.

env WINEPREFIX="/home/bob/.wine" wine C:\\windows\\command\\start.exe /Unix /home/bob/.wine/dosdevices/c:/users/Public/Desktop/PicPick.lnk

And Here is the result of inserting that command line into the Terminal.

bob@bob-HP-ProBook-6550b ~ $ env WINEPREFIX="/home/bob/.wine" wine C:\\windows\\command\\start.exe /Unix /home/bob/.wine/dosdevices/c:/users/Public/Desktop/PicPick.lnk
fixme:exec:SHELL_execute flags ignored: 0x00000100
fixme:exec:SHELL_execute flags ignored: 0x00004100
bob@bob-HP-ProBook-6550b ~ $ fixme:wtsapi:WTSRegisterSessionNotification Stub 0x10084 0x00000000
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.
fixme:time:GetDynamicTimeZoneInformation (0x33fbd3) stub!
fixme:wincodecs:PngDecoder_Block_GetCount 0x194e30,0x33fad8: stub
fixme:wincodecs:PngDecoder_Block_GetCount 0x1975d8,0x33f938: stub
fixme:wincodecs:PngDecoder_Block_GetCount 0x197658,0x33f938: stub
fixme:wincodecs:PngDecoder_Block_GetCount 0x25395b8,0x33f838: stub
wine: Unhandled exception 0x0eedfade in thread 25 at address 0xffffffff:0x7b83935c (thread 0025), starting debugger...
err:seh:setup_exception_record stack overflow 824 bytes in thread 0025 eip 7bc3f662 esp 00240ff8 stack 0x240000-0x241000-0x340000
Process of pid=0024 has terminated
No process loaded, cannot execute 'echo Modules:'
Cannot get info on module while no process is loaded
No process loaded, cannot execute 'echo Threads:'
process tid prio (all id:s are in hex)
0000000e services.exe
0000001e 0
0000001d 0
00000018 0
00000016 0
00000014 0
00000010 0
0000000f 0
00000012 winedevice.exe
0000001c 0
00000019 0
00000017 0
00000013 0
0000001a plugplay.exe
00000020 0
0000001f 0
0000001b 0
00000021 explorer.exe
00000023 0
00000022 0
winedbg: Internal crash at 0x7ed0aeb5

Too confusing for me but someone may get a clue from it. :)
B.M. (505)
1456930 2018-12-28 05:29:00 Are they similar specs as in processors, graphics etc? gary67 (56)
1456931 2018-12-28 06:28:00 Make sure that ntlm_auth >= 3.0.25 is in your path. Usually, you can find it in the winbind package of your distribution
This looks to be the relevant bit - you have winbind installed?
fred_fish (15241)
1456932 2018-12-28 06:55:00 This looks to be the relevant bit - you have winbind installed?

No Fred, not installed but available.

I'll check the working computers and if it's installed on them I'll take it from there.

Thanks.
B.M. (505)
1456933 2018-12-28 07:32:00 Unfortunatly Fred winbind is not installed on either working machine.

The machine giving the problem is a HP ProBook 6550b.
B.M. (505)
1456934 2018-12-28 19:03:00 Now seeing I have only ever used Mint 18 – Cinnamon, I thought I’d put different versions on different machines to try out.

The Windows programme I want to get working is PicPick,



Why? There is very little difference between those versions of Mint.
If you went 16, 18 or such maybe.
But 18.whatever?


Dunno about the error but:

alternativeto.net

I do this now, plenty of choices so I can't be bothered with trying to make Win stuff work anymore.
piroska (17583)
1456935 2018-12-28 20:26:00 Why? There is very little difference between those versions of Mint.
If you went 16, 18 or such maybe.
But 18.whatever?


Dunno about the error but:

alternativeto.net

I do this now, plenty of choices so I can't be bothered with trying to make Win stuff work anymore.

Well, I just like to see for myself just what the difference is between the different versions.

I have absolutely no intention of fixing Mint 18 on my Main Computer which isn’t broken and runs all my windows programmes fine. (With the exception of a home security programme which has been assigned an old Win XP computer of its own.)

As for the link, I have tried most of those just for fun and a lot are discontinued and none could get near PicPick for versatility.

My guess is there is just one file missing but which one.

Actually, as I type this, I wonder if we have a different kernel problem?

How do you check the Kernel Version that’s installed?
B.M. (505)
1456936 2018-12-28 20:37:00 Actually, as I type this, I wonder if we have a different kernel problem?

How do you check the Kernel Version that’s installed? Found this : itsfoss.com


As for the link, I have tried most of those just for fun and a lot are discontinued and none could get near PicPick for versatility. Yep, sometimes you just have a program, that no matter what else comes along you like to use. Got several like that, the newer ones simply dont do some tasks. :)
wainuitech (129)
1456937 2018-12-29 05:24:00 Found this : itsfoss.com

Interesting link that Wainui. :thumbs:

Well I first checked my main Desktop and the Kernel there was:

4.4.0-36-generic #55-Ubuntu

I then went to the Laptop with three different Distro’s installed and none working with PicPick, and it was:

4.4.0-21-generic #37-Ubuntu

I then went off to the second Laptop with just 18.1 installed and working fine with PicPick and bugger me days if it didn’t have the exact same Kernel as the Laptop with 3 Distro’s installed, none of which will work with PicPick.

Looks like another bright idea bites the dust. :D
B.M. (505)
1456938 2018-12-29 06:17:00 Doing some reading up on this, seems there have been a few problems with the latest Wine and some 18.X versions of Mint.

As an experiment, loaded Mint 19.1 into a VM, installed Playonlinux, then from within linux downloaded Picpick, instead of saving told it to open with Playon linux, and bingo, right away Picpick installed & opened and worked.

Ya gotta try these things ya know :nerd: one thing in IT -- NEVER assume anything will work because the moment you do it will make a bloody lair of you :D

Might be time to try a newer version of Mint B.M. ;) Go onnnnn, give it a go, you know you really want to :D

Heres the VM: PicPick Icon Bottom right hand corner 4rd in (excluding the time)-- Rainbow ((((

9274
wainuitech (129)
1 2