Comment 72 for bug 130325

OK. I do understand there is a reason for not making the patch, and for
me at least, my linux system is primarily for scientific computations, and
the eye candy is completely gratuitous. But this is also why my preferred
platform is and remains Apple's OS X. I don't have to devote lots of time
and effort to sys administration, like I do with Linux. (I run an academic
scientific research group and have to do most of my own administration.)
I chose Ubuntu because of its comparative simplicity and ease of use, (and
because I was already familiar with the debian package management system
as a maintainer of debian packages for OS X via the Fink project). But it
is hardly seemless, and although I have been using it from the beginning,
more than half of the upgrades have had "show-stopper" glitches. I
realize that this is not Ubuntu's fault, but the bug has been around at
least since January on Fedora Core, according to some of my colleagues, so
it is clear Nvidia is not going to wiggle their collective behinds too
much to fix this.

OS X just works.
Ubuntu is 100% free if your time is of no value.

Bryan Haskins wrote:
> What you describe *is* compiz fusion. And it's not that simple, first
> it's something we added in to fix another issue, second realistically
> it's nvidia at fault... Do I condone us taking the highroad and leaving
> it in so nvidia will fix it's issue... I'm torn. I don't think they'll
> learn anything, but at the same time we shouldn't hack alternate fixes
> for their blunder. This is an upstream patch now, they have to get their
> blob to work with it or it simply... well won't work.
>
> wgscott wrote:
>> Even without Compiz (or Beryl), the same problem arises if you turn
>> desktop effects compositing on (drop shadow on windows and so forth).
>>
>> May I humbly suggest the offending patch simply be removed?
>>
>>
>> ChrisC wrote:
>>
>>> making compiz enabled by default with this issue *regardless* of blame
>>> would be disastrous and could seriously dent efforts to correct bug #1
>>> it could even mean Ubuntu becoming a minor bit player of distros...
>>>
>>> Is this *defiantly* an nvidia bug, are people really sure that there
>>> isnt
>>> a bug with the clipping patch for xorg?
>>>
>>> Can the clipping patch not be altered to take into account nvidia
>>> drivers?
>>>
>>> theres a legacy nvidia an open source nvidia an older nvidia and
>>> an nividia-glx-new driver why not an nvidia-mobile driver too :o)
>>>
>>> enabling compiz by default with this bug could kill Ubuntu.
>>> This needs sorting *well* before November October is only
>>> a few weeks away...
>>>
>>> 3vi1 wrote:
>>>
>>>> I hope nVidia gets on the ball and releases a new driver in time for
>>>> everyone to test before Gutsy final (now that it has been voted that
>>>> Compiz will be enabled by default). If they don't, I think Gutsy
>>>> will
>>>> end up looking very unstable to users unfamiliar with the underlying
>>>> causes.
>>>>
>>>> I have this problem on my 7600GT-based system and it's getting
>>>> annoying
>>>> to switch window managers every time I want to run an OpenGL app. I
>>>> do
>>>> *not* hope the 'buntu maintainers build Xorg without patch 132 as a
>>>> workaround though, as that completely removes all incentive for nVidia
>>>> to fix the real problem.
>>>>
>>>> In answer to Sitsofe's ABI observation, I would think that nVidia
>>>> would
>>>> simply put an item in the release notes indicating that the newer
>>>> driver
>>>> is only for Xorg (insert version # / patch level here) and later. It
>>>> would be up to the repackagers to set dependencies for each version to
>>>> their related Xorg packages.
>>>>
>>>> -J
>>>>
>>>>
>>>>
>>> --
>>> [nvidia-glx] 3D GL apps crash X when using compiz due to unmaked ABI
>>> change (gutsy)
>>> https://bugs.launchpad.net/bugs/130325
>>> You received this bug notification because you are a direct subscriber
>>> of the bug.
>>>
>>>
>>
>>
>
> --
> [nvidia-glx] 3D GL apps crash X when using compiz due to unmaked ABI
> change (gutsy)
> https://bugs.launchpad.net/bugs/130325
> You received this bug notification because you are a direct subscriber
> of the bug.
>