Suddenly problems trying to "Create Shortcut"

Slimjet bug reports
Post Reply
Kewpycat
Posts: 7
Joined: Mon Jan 14, 2019 1:38 pm

Suddenly problems trying to "Create Shortcut"

Post by Kewpycat » Sat Jun 29, 2019 2:49 pm

Lately I seem to be having a problem with the "Create Shortcut" function (More tools-Create Shortcut)

The shortcut gets created, but does not work. If I click on it, nothing happens (except for a small spinning circle for a few seconds and disappears)

The reason it doesn't work can be seen in the properties. The "Target" is pointing to "chrome_proxy.exe" as in the following example:
"C:\Program Files (x86)\Slimjet\chrome_proxy.exe" --profile-directory=Default --app-id=okkolgldfknecfjnhhglfopimelbaceh

It should point to Slimjet.exe as in the following example: (from an older, working shortcut)
"C:\Program Files (x86)\Slimjet\slimjet.exe" --profile-directory=Default --app-id=bcdaicdlffaahimncapcmjecfmknnnpc

I'm not sure why now the shortcuts are being created with the incorrect path, perhaps I've changed something in Slimjet to cause this? I uninstalled Chrome to see if it helped, but it did not.

I'm on: Version 23.0.5.0 (based on Chromium 74.0.3729.108) (Official Build) (32-bit)

User avatar
oftentired
Posts: 1240
Joined: Tue May 13, 2014 3:14 am

Re: Suddenly problems trying to "Create Shortcut"

Post by oftentired » Sat Jun 29, 2019 5:49 pm

Confirmed. I don't know of a permanent solution, but one can manually replace Chrome-proxy with Slimjet and correct it that way.
For those of you who wear aluminum foil hats, the voices lie, don't believe them!

Running 32 Bit SJ on Win 7 Pro

Kewpycat
Posts: 7
Joined: Mon Jan 14, 2019 1:38 pm

Re: Suddenly problems trying to "Create Shortcut"

Post by Kewpycat » Mon Jul 01, 2019 6:17 am

Looks like the problem is not exclusive to Slimjet.

When trying to research chrome_proxy.exe, I found this in a discussion related to the same problem occuring in the Brave browser:

Additional Information:
EASY FIX BELOW!!!
The shortcut is easily fixed by changing the target from chrome_proxy.exe to brave.exe
Meaning that all you’d have to do is either fix chrome_proxy to properly forward the PWA shortcut, or make the shortcut point to brave.exe on creation.


The above was dated April 18; a month later the discussion was closed with no apparent resolution to the issue. (other than the "fix" mentioned by Oftentired and also in the discussion in the Brave browser forum)

Post Reply