SoylentNews is people
SoylentNews is powered by your submissions, so send in your scoop. Only 14 submissions in the queue.
SoylentNews
posted by
LaminatorX
on Saturday October 25 2014, @02:41PM
from the whining-is-not-efficacious dept.
from the whining-is-not-efficacious dept.
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?
This discussion has been archived.
No new comments can be posted.
Wine Fails to Launch under Debian Jessie, Just Days before the Freeze Deadline
|
Log In/Create an Account
| Top
| 119 comments
| Search Discussion
The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
You are so boring that when I see you my feet go to sleep.
(Score: 2) by LoRdTAW on Wednesday October 29 2014, @07:01PM
Interesting experience. Chrome has been pretty damn stable for me and this is on multiple systems. AMD, Intel, Windows 7, and Linux. It always works. The only issues I had was the updater crapping itself every once in a rare while but it just fixed itself. One thing to add, I always close Chrome every few days. Not purposely, but after a while I don't have a need to keep it open and I close it.
I think the main allure that got me hooked on Chrome early was the minimal UI and HTML 5 (no more flash for youtube).
(Score: 2) by urza9814 on Thursday October 30 2014, @01:07PM
Yeah, it's actually only on my work system that Chrome does that, but it's damn annoying. After using it for a while it'll enter a state where damn near any link I click causes the whole browser to crash. For some reason I suffered through that for at least a month before finally switching to Firefox. I do use Chromium along with Firefox on my home system and that doesn't have the same problems, although I don't notice it being any *more* stable than Firefox either.
I do suspect part of the problem is that I rarely close my browsers. I even have Firefox in my initrc file. And I have them remember the previously open tabs, so even when I close (or crash) the browser there are still tabs that I've had open probably since I bought my computer (gmail for example). I actually do this with most programs though -- once I open Kate or Chromium or Dolphin, they're not getting closed either until I need to reboot! :)