No Wine cmds run at all after updating Bluesound Controller

Questions about Wine on Linux
Locked
randys
Newbie
Newbie
Posts: 3
Joined: Tue Jul 28, 2015 11:34 am

No Wine cmds run at all after updating Bluesound Controller

Post by randys »

I've seriously messed up my system as far as Wine is concerned, and have no idea how to undo this...

I am running Wine 1:1.7.44-0ubuntu1 on Xubuntu 14.04.2. Until this morning, I was using it to run the Bluesound Controller Windows app version 1.6.0 build 177. This setup was working perfectly until I installed the new version of the Bluesound Controller, 1.8.0 build 210. When I tried to launch the new version, nothing happened.

When I launched it via winefile, I was able to see a list of error messages appear in the command prompt window that lead me to believe that it was having trouble finding two dll files, namely msvcp120.dll and msvcr120.dll. In an attempt to fix this, I copied these two files from a Windows 7 install that I have on another machine into Wine's System32 directory. This seemed to make problems worse. I could no longer launch winefile in a terminal window. When I attempted to do so, the application simply exited without any error messages and returned to the prompt.

In a bit of a panic, I uninstalled Wine using the Ubuntu Software Center, deleted the .wine folder from my home directory, rebooted and reinstalled Wine. I still could not run any Wine utilities.

After a couple of repeated uninstalls and reinstalls, I was able to get wine uninstaller to run, but with errors. It actually displayed the graphical interface, which I used to install the Bluesound controller again. It still didn't work, and now I'm back to the point where no Wine utilities will run. I can't even get winedbg to return anything.

For a while, I was able to run winecfg only the first time after a fresh install and got a message back saying that it created the needed subdirectories of .wine. After this, it would not run again. I could not get it to launch the graphical interface. Now, I can't even get it to do that.

At this point, Typing any of the following commands gets me the same results, namely nothing but a new prompt:

winecfg
wine winecfg
winefile
wine winefile
wine uninstaller
winedbg
winedbg winecfg
winedbg winefile

I would love to post some debugging info, but I don't know how to get any without winedbg. Can someone please help me figure out where to start? I'm desperate, and at this point, can only think of wiping my hard drive an reinstalling Ubuntu.

Thanks,

Randy
User avatar
dimesio
Moderator
Moderator
Posts: 13367
Joined: Tue Mar 25, 2008 10:30 pm

Re: No Wine cmds run at all after updating Bluesound Control

Post by dimesio »

It sounds like you messed up your wineprefix by trying to upgrade the software. Uninstalling and reinstalling Wine won't help with that, because it doesn't touch existing wineprefixes. You need to delete the wineprefix (default is ~/.wine) and reinstall your app to a clean one.
ebstauffer
Newbie
Newbie
Posts: 2
Joined: Tue Jul 28, 2015 12:54 pm

Re: No Wine cmds run at all after updating Bluesound Control

Post by ebstauffer »

Did you by chance run a system update this morning? See my earlier post. As you, I am totally dead in the water.
User avatar
dimesio
Moderator
Moderator
Posts: 13367
Joined: Tue Mar 25, 2008 10:30 pm

Re: No Wine cmds run at all after updating Bluesound Control

Post by dimesio »

ebstauffer wrote:Did you by chance run a system update this morning? See my earlier post. As you, I am totally dead in the water.
Yes, that could be the problem.

Reported here: https://bugs.winehq.org/show_bug.cgi?id=38982
Upstream bug: https://launchpad.net/bugs/1478844

Downgrade your kernel until Ubuntu fixes it.
randys
Newbie
Newbie
Posts: 3
Joined: Tue Jul 28, 2015 11:34 am

Re: No Wine cmds run at all after updating Bluesound Control

Post by randys »

Thank you extremely!!! Downgrading my kernel has made Wine work again. Now, if I can just get this new version of my Windows software working...

...later on...

With the help of winetricks, installing the VC++ 2013 redistributable package has fixed my original problem. My Bluesound is happy again :D
Locked