On Sat, Jun 1, 2013 at 2:56 PM, wrote: > >> Which front end are you using? > > It was q4wine > >> message should pop up via >> xmessage, and if not it will be dumped to stdout. So if your front >> end is preventing that, the issue should be fixed there. > > Unfortunately, missing files already cause errors during the frontend > configuration process, > before any actual attempt to execute the wine "binary". > > Thus, the idea of letting the packet managment script provide the message.
Or having the front end fix their assumptions. Please consider filing a bug against q4wine. Best wishes, Mike -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
