Who’s the bloody moron? (Bug #252094)
Who’s the piece of human shit who changed the status of the most obnoxious bug in Jaunty, mentioned even in the release notes under “Performance regressions on Intel graphics cards”, that is bug #252094, from Confirmed to Invalid?
The idiotic (closed source) Launchpad doesn’t allow to identify the scumbag. Who the fuck is “Bug Watcher Updater”?
Jun 3, 2009 at 23:17
Mister,
I think Hitler could be a piece of human shit but not this poor guy, who just mad a mistake or didn't realized he fuck it up. He didn't kill anybody or did something terrible to be cataloged as a human piece of shit.
I like your rants but sometimes I think you should restrain yourself.
Jun 3, 2009 at 23:41
Yeah,
Ubuntu sometimes has a quirky policy when it comes to bug reports. See for yourself:
https://bugs.launchpad.net/ubuntu/+source/aumix/+bug/145805
Now me, I’m happily using CentOS, because 5.3 finally fixed the nautilus-sendto dependency on libgaim.so.0, which means I can ‘yum groupinstall “GNOME Desktop Environment”‘ just like that.
:o)
Jun 4, 2009 at 02:46
It really is a stinking bug. I’m not using Ubuntu but I’ve tried it. Also had a play with Gentoo stage 3 install and that is *absolutely* crippled (in terms of X) for intel based laptops. I have one machine with GMA855 and one with GMA945. The GMA855 is the lowest of the low in the 3D world but with its 8MB RAM stolen from the system it is still a great performer… on old 2.3 driver and Xorg 1.4.2. It can run Compiz (was amazingly good with Beryl), suspends and resumes without issue, I can play Cube and AssaultCube and other light 3D games. It just does everything right. This is on Debian Squeeze/Sid mixed but it has been impressive for years on everything I tried. Obviously time for upstream to utterly break the drivers and for idiot distributors to unthinkingly pass the shit on to their users like it’s something good. Intel have really dropped the ball with graphics drivers in the last year and Xorg is such a mess that it seems nobody is capable of fixing anything, only breaking that which was rock solid and reliable for years. Fucking idiots. I know I run old versions by using Lenny on some machines but sometimes on the two I have running Squeeze/Sid I wonder that some versions are still some way behind. Then Intel+Xorg work their magic, naive and/or expedient distros looking for scoring cheap points with latest version numbers pass it along and I am bloody pleased that Debian devs don’t pass this shit on without fixing it.
What makes it doubly irritating is that nvidia drivers for latest GPUs were really awful (bad rendering, broken suspend, bad support of HD, high CPU use etc etc) for quite a while but they have really got their act together, with releases and bug fixes arriving at a steady pace…..kind of how an open source project is imagined to be, not a proprietary one. So right now the free open source drivers from intel and Xorg give us broken drivers and stalled development while the 100% proprietary company gives us rapid development, and high quality feature rich drivers. This is not how it’s supposed to be.
After the Vista Ready debacle I have to imagine that MS feel they deserve some payback for pulling Intel’s GPU division out of a deep dark hole. And looking at what is happening with netbook proliferation and MS reaction it doesn’t strike me as a co-incidence that simultaneously Intel loses interest in offering quality drivers for free OS. They owe MS bigtime for keeping them in the game, and so do all the manufacturers who spent a year shipping laptops with low end Intel GMA with a Vista Ready sticker on the box. My suspicion is that it’s payback time.
omg I sound like boycottnovell… must drink beer and relax.
Jun 4, 2009 at 09:36
@elbeto: Yes, he must be a scumbag, because one can't know from the Launchpad bug's page *who* did the change, therefore it was a cowardly action!
Plus, the assignment to freedesktop-bugs #18389 is idiotic and inappropriate.
It's like Ubuntu is trying to deny its most important bug for the 9.04 release!
—
@Niki: It's a whole mess with https://bugzilla.redhat.com/show_bug.cgi?id=250403
From the bug report, it seems it's not closed, but… VERIFIED!
This, for an elementary bug reported on 2007-08-01 and fixed in StartCom Linux AS-5 on 2007-07-10, but ignored by Red Hat!
CentOS seems to have fixed it, which is so unusual for them:
* Tue Mar 10 2009 Karanbir Singh <kbsingh@centos.org> - 0.7-6.el5.centos
- Rebuilding for #2483
That's http://bugs.centos.org/view.php?id=2483
However, RHEL is using ftp://ftp.redhat.com/pub/redhat/linux/enterprise/5Client/en/os/SRPMS/nautilus-sendto-0.7-5.fc6.src.rpm …whereas the bug report added a "Release note" that says: "nautilus-sendto 1.0 in Red Hat Enterprise Linux 5.0 adds the ability to send to
Bluetooth devices, better Pidgin integration, and a number of user interface fixes."
BUT THERE IS NO nautilus-sendto 1.0 in EL5!!!
I feel I am going to *buy* Windows 7.
—
@Takla:
I liked the parts with "Xorg is such a mess that it seems nobody is capable of fixing anything, only breaking that which was rock solid and reliable for years" and "nvidia drivers for latest GPUs were really awful (bad rendering, broken suspend, bad support of HD, high CPU use etc etc) for quite a while but they have really got their act together" => "So right now the free open source drivers from intel and Xorg give us broken drivers and stalled development while the 100% proprietary company gives us rapid development, and high quality feature rich drivers. This is not how it’s supposed to be."
Jun 4, 2009 at 09:45
This makes an inconstancy with https://bugs.launchpad.net/ubuntu/+source/linux/+bug/375070
{linked by http://beranger.org/v3/wordpress/2009/05/11/fix-the-screwed-2630-ubuntu-karmic-kernel/}
which has been already waiting for 4 weeks (though the solution is almost given!! -I was in a similar situation with a bug I could fully fix [a trivial one in my case] : the maintainer was so overworked it took 2 years…. but they did not claim of being human-friendly, of vibrant fora, of satellitical help!!!!
OTOH, I like the color and the care they take to classify/paint UBUgs.
Jun 4, 2009 at 09:54
Scarabée d’Or… that was indeed one of the first bug reports ever
Bug report:
53‡‡†305))6*;4826)4‡.)4‡);806*;48†8¶60))85;1‡
(;:‡*8†83(88)5*†;46(;88*96*?;8)*‡(;485);5*†2:*‡
(;4956*2(5*— 4)8¶8*;4069285);)6†8)4‡‡;1(‡9;480
81;8:8‡1;48†85;4)485†528806*81(‡9;48;88;4(‡?34;
48)4‡;161;:188;‡?;
Resolution:
A good glass in the bishop’s hostel in the devil’s seat forty-one degrees and thirteen minutes northeast and by north main branch seventh limb east side shoot from the left eye of the death’s-head a bee line from the tree through the shot fifty feet out.
Jun 4, 2009 at 12:44
Since we're discussing Launchpad, just take a look at Ubuntu Dapper bugs. I know, the official support for Dapper is getting axed this month, but there are currently 96(!) open CVE bugs; some of them are older than 2 years. OpenSSL, Java, VLC media player, Ruby, Python and a lot of other important software has been wasting bandwidth in the Dapper repositories for years now, just by being there, unpatched. All this shit in a supposedly enterprise-class distro, with 5 year support on servers. Most bugs were also present in Ubuntu releases more recent than Dapper, but they've been closed with WNF since the releases were EOL'd. I swear on Stallman's beard, these people are anxiously waiting to WNF the bugs!
And the user is the only one who loses. Let's take the example of VLC: upstream continuously updates their shit; Ubuntu Dapper is stuck with an old version of VLC; updating VLC is out of the question, since such a feat requires updating half or more of the packages Dapper is made of - this is how dependent on other packages VLC is. Backporting bugfixes is the only rational thing to do, yet it won't happen either because we all know backporting is not for the faint of heart. And Canonical is not Debian.
Fuck Ubuntu and their antics.
Jun 4, 2009 at 14:53
"some of " (UBUgs) "are older than 2 years. " : That is great : they claim they have a good UBUgs manager, what would happen if UBUgs prematurately died?
Jun 5, 2009 at 13:29
Oh well, there is an explanation.
The morons have assigned(?) the Ubuntu Bug 252094 to the freedesktop bug #18389. That bug was opened for openSUSE.
Recently, the guys at freedesktop closed the bug with… NOTOURBUG! Whose bug is it then? Ballmer’s bug?!
This does NOT solve the bug. As long as some given releases of xf86-video-intel are broken, the fact that the latest cvs/git/whatever are better does not invalidate a bug, even less make it NOTOURBUG.
Then, apparently by an automated script, Ubuntu’s Bug 252094 was set to Invalid, because the upstream bug was closed with NOTOURBUG!
IS Jaunty affected by this bug? YES. Then the bug is not Invalid!
Thousands of reports made clear the fact that xf86-video-intel was broken somewhere between version 2.5 and 2.6; additionally, it now depends on specific features in the kernel, which makes the job of the distros tougher. But the Ubuntu guys don’t care.
They keep saying idiocies like this: “There are a lot of reports of improved performance with using 2.6.30rc kernels in combination with newer versions of intel drivers from the x-org edgers PPA’s in Jaunty and Karmic.”
x-org edgers & stuff: if you want your system to still work, *don’t* use such stuff!
*All* the PPAs are UNOFFICIAL packages. Not fixes. Not official updates.
Then, the idiot called Dmitrijs Ledkovs adds: “It was affected on the day of the release, packages from karmic are *official* and have been backported via PPA and do fix the problem. Right now it’s the waiting time to decided what will qualify for SRU. It is Ubuntu policy not to include new versions of software after the release.”
Fuck you, with all your family! PPA are *not* jaunty-backports! Karmic is *not* released, and obviously Jaunty isn’t fixed!
The *official* backports are here:
http://packages.ubuntu.com/jaunty-backports/allpackages
NOTHING to fix this issue. So the bug is valid, not in “day zero” as this idiot claims, but as I am writing this.
With such shitheads, I’LL NEVER USE UBUNTU AGAIN! EVER!
Jun 13, 2009 at 11:49
"NOTOURBUG"
I suppose they have two different repositories :
* our_work (and the glorious bugs will be theirs)
* not_our_work (but the number of packages remains an advertising argument)