We are currently migrating Bugzilla to GitHub issues.
Any changes made to the bug tracker now will be lost, so please do not post new bugs or make changes to them.
When we're done, all bug URLs will redirect to their equivalent location on the new bug tracker.

But something suggests its a SDL problem

http://www.mit.edu/course/6/6.115/src/sdl/SDL-1.2.9/docs.html

1.2.8 they hadn't even known how to produce a mouse that works! - and 1.2.8 was deemed 'stable'
was fixed in 1.2.8


it's a critical bug in my opinion, just as critical as the inverted mouse on mac osx

but it could be debian that is using too old stable libs too?

Here are my versions:
ii  libsdl-image1.2:i386                 1.2.12-2                           i386         Image loading library for Simple DirectMedia Layer 1.2, libraries
ii  libsdl-mixer1.2:i386                 1.2.12-3                           i386         Mixer library for Simple DirectMedia Layer 1.2, libraries
ii  libsdl-net1.2:i386                   1.2.8-2                            i386         Network library for Simple DirectMedia Layer 1.2, libraries
ii  libsdl-sound1.2:i386                 1.0.3-6                            i386         Sound library for Simple DirectMedia Layer 1.2, libraries
ii  libsdl-ttf2.0-0:i386                 2.0.11-2                           i386         TrueType Font library for Simple DirectMedia Layer 1.2, libraries
ii  libsdl1.2-dev                        1.2.15-5                           i386         Simple DirectMedia Layer development files
ii  libsdl1.2debian:i386                 1.2.15-5                           i386         Simple DirectMedia Layer


I just think it is not a good idea to give people the suggestion SDL is 'stable', and then the mouse is totally broken
It has been broken at least since 1.2.8 , which should have been a stable release?

Many people use SDL 1.2 and rely on it as being stable
but then the mouse is totally broken

So I think this is a critical bug

I can attest to seeing this problem myself at least since 2010 (5 years now)

on 3-5 different debian stable systems


I experience Problems in these programs:
ioquake3 (icculus quake3 older versions/any version which uses sd1.2)
aprquake2
fs-uae , amiga emulator for linux
protracker23 - tracker for linux
Doom for SDL (many ports..)


Aprquake2 even had an inverted mouse also... was even more broken
seems to be the 1.2.8 bug in osx that was on linux too...

I rarely find a SDL program that works in fullscreen


It seems the problem is in my SDL1.2 lib, that is buggy
even though it should be STABLE

so critical bug?

Sorry for all the 'swearing' ;-) , I got in a bad mood from this bug, it really annoys me badly each time, and I've seen this bug for at least 5 years now

Nothing worse than a broken mouse across 5+ programs

I like SDL just like I do with ALSA; but it seems there are some great problems with both at times..

but not 100% sure this is an SDL problem yet, might not be, I'm trying to figure out by upgrading my debian right now


that it is broken across so many programs definitely seems to suggest a lib problem, but could be debian that uses old libs too

The problem is not recognized officially in your ChangeLogs, thats what bothers me too

Changed severity to Major, since it definitely looks like a bug in SDL (90% sure)

I'm upgrading my debian to test, currently on oldstable while stable is out


It should still be stable, since oldstable used only stable SDL libs.
So that is why it is a major problem with SDL, if it is a SDL  bug, mousepointer bugs are bad... makes the whole program unuseable


and should definitely be stable when the lib says it is! - but doesn't seem to be stable at all, problem is there 100% of the time

I can't reproduce this problem here, but SDL 1.2 is obsolete in any case; we've rewritten all of this code for SDL 2.0, so moving to that will likely fix your problem better for a number of reasons.

--ryan.

 
Shame it shouldn't get resolved, there are like 20 other topics with this problem! confirming it is a bug in SDL
 
i just upgraded to newest stable debian , problem is still there for me
 
maybe the bug is only on certain machineS?
 
I have had this bug on 4-5 machines now, so just closing the bug like this makes no sense... unless you dont care of course


- 20 other bugs like this one here
- big problem with mousepointer in osx in same 1.2.12 version (which should be stable!)
- its a severe bug


so it really shouldn't be closed, but whatever if you have rewritten it all

it is still a stable bug, 1.2.12 should be stable
but it isn't! - so a severe bug

See all the other bug reports.... they are the same as mine

What should debian stable users do, they run 1.2.12 ?

Maybe its an issue from upgrading, since I had a person test it and he didn't have the problem...

I still have it on 1.2.12 version..
newest debian stable, which should be very stable, debian is known for being stable

but it seems your lib is the only thing that is broken there


and reinstall may fix it, but on the other hand I have had 3-4 other machines with this problem, happens in many programs
seems the SDL lib


will you just tell debian stable group to just throw out 1.2.12 ? because its obsolete?

then they need a MAJOR version upgrade in their repos

looking for answer

change prio to normal, since it seems you cannot replicate it you say

(In reply to Michael Ole Olsen from comment #6)
> - big problem with mousepointer in osx in same 1.2.12 version (which should
> be stable!)

SDL 1.2.15 is the most recent bugfix release of SDL 1.2 – so SDL 1.2.12 is 3 bugfix releases out-of-date compared to the latest stable version of SDL 1.2.

(In reply to Michael Ole Olsen from comment #7)
> What should debian stable users do, they run 1.2.12 ?

Under those conditions, my recommendation would be to stop using Debian Stable.

Running something as old as 1.2.12 is not stability, it's a liability. 1.2.15 is the last stable build of 1.2. 1.2.12 is _eight years_ old on the 1.2 branch and many many many fixes went into 1.2 since then.

I don't know if this is an SDL bug, but it doesn't happen here, even with 1.2, and I haven't gotten this bug report from the thousands of users of SDL 1.2 that played games I shipped over a decade with it. I don't know what to tell you about it.

Also, as I said, we aren't working on 1.2 any more; we are focused on 2.0 now. If you can track down the bug to SDL 1.2, send Debian a patch to include with their package, but 1.2 is obsolete and we will not be spending engineering resources on it.

Also, please, don't write four more comments in reply; I get an email for each of these and it's getting out of control.

--ryan.