SoylentNews

Wine Fails to Launch under Debian Jessie, Just Days before the Freeze Deadline

posted by LaminatorX on Saturday October 25 2014, @02:41PM   
from the whining-is-not-efficacious dept.

An Anonymous Coward writes:

A grave bug has been introduced into the "wine" package of Debian Jessie, just days before the November 5th freeze deadline. The /usr/bin/wine launch script fails with an "error: unable to find wine executable. this shouldn't happen." message.

Debian has already suffered much unrest lately over the inclusion of systemd, with threats of a fork being issued, along with the possible cancellation of the GNU/kFreeBSD port and the possible dropping of support for the SPARC architecture. After so much strife and disruption, can Debian afford to have such a serious bug affect such a critical package so soon before such a major freeze?

• Shell Scripts And $PATH Shell Scripts And $PATH (Score: 0) by Anonymous Coward on Sunday October 26 2014, @02:33AM

  by Anonymous Coward on Sunday October 26 2014, @02:33AM (#110138)

  Silly users!

  /usr/bin/wine is probably a shell, Perl, or Python script. Test to see like this:

  $ file /usr/bin/wine

  It probably calls an executable that is probably in a version-specific directory, just in case the user wants to maintain multiple versions of wine, say, /usr/local/wine-1.23 ... so the binary executable for wine will probably be something like /usr/local/wine-1.23/bin/wine .

  You could invoke that executable directly, and perhaps run it in the background:

  $ /usr/local/wine-1.23/bin/wine &

  ... or you could take a look at that script, and see if you could figure out what was wrong, and fix it:

  $ grep -i wine /usr/bin/wine
  $ more /usr/bin/wine
  $ sudo vi /usr/bin/wine

  ... it's also possible that there's something wrong with the PATH variable, either locally or in the /usr/bin/wine script.

  The following commands will cast some light on that situation:

  $ echo $PATH
  $ which wine
  $ whereis wine

  If you wish to inspect the PATH variable in the [presumed] /usr/bin/wine script, it's as simple as grepping for it:

  $ grep PATH /usr/bin/wine

  If you see a PATH reference to a version that does not exist or a typographical error in the path to the existing version of wine, that may be your problem. Things like this:

  PATH=$PATH:/usr/local/wine-1.22

  ... when you are running version 1.23, or this:

  PATH=$PATH:/usr/locla/wine-1.23

  ... will surely cause problems.

  At the end of the day it is likely to be something simple.

  The satisfaction you get from identifying and fixing small problems like that will hopefully give you a taste of what we love about open source software, and nudge your UNIX administrative skills up a notch, too - away from being a user who clicks on icons and complains when they don't work.

  With a little bit of luck, maybe you'll get started on writing your own scripts, and start programming.

  ~childo

• Re:Shell Scripts And $PATH (Score: 0) by Anonymous Coward on Sunday October 26 2014, @01:02PM

  by Anonymous Coward on Sunday October 26 2014, @01:02PM (#110226)

  You know, you could have just looked at the patch in the bug report, which would have saved you a lot of speculation and typing.

  Parent