Firefox goes nuts and eats a squirrel

[Josh K]

Binary package hint: firefox-3.0

Ok, I don't have the vaugest idea of what comprizis a bug report, but here goes.
I have an IBM thinkpad t40 with jaunty testing updated to latest packages.
radeon 2500 mobile.

What happens:
I open firefox.
I hover over a link.
the mouse flickers wildly, the news drop-down button on the bookmarks menu rapidly focus-unfocuses
and the little indicator at the bottom of the screen flashes the link at a million milli-noblings a second.
This issue randomly vanishes and reappears.

[feba (febaen)]

Well, that's... bizarre. Have you tried running firefox in a terminal (Applications -> Accessories -> Terminal), and seeing what error messages come up?

[Josh K (terlmann-deactivatedaccount)]

erm, when you run firefox from a teminal it just spawns a new process. I don't know how to run it in a terminal. I'm going to disable my custom themes and see if that fixes it.

[Josh K (terlmann-deactivatedaccount)]

Closing bug, caused by a custom gtk theme.

[Josh K (terlmann-deactivatedaccount)]

cancel that, it's doing it again.

[feba (febaen)]

might be caused by a custom gtk theme messing with something it shouldn't.

[feba (febaen)]

What do you mean spawns a new process? Do you mean it just says something like [1] 55555? Run it as "firefox", not "firefox &". Not while firefox is already running (if it is, 'killall firefox')

[Brian Beaulieu (brian-beaulieu)]

Try running firefox in safe mode as well.
In a terminal: firefox -safe-mode

[Bryce Harrington (bryce)]

Sounds like a dupe of 87043

I can reproduce it only when having more than one tab open.
In firefox --safe-mode, not reproducible.

[Bryce Harrington (bryce)]

I can reproduce it with several different shipped themes, so don't think it has anything to do with the theme.

[Bryce Harrington (bryce)]

Scratch what I said in comment #8; it is definitely reproducible with `firefox --safe-mode`.

313706 is another dupe of this bug.

[Bryce Harrington (bryce)]

312353 looks like the master bug for all these. It's also reported upstream already at https://bugzilla.mozilla.org/show_bug.cgi?id=471091, however there's no activity there. Subbing asac to look into this more.

[Bryce Harrington (bryce)]

dah, inevitably it turns out to be an xorg problem... cleaning up dupes.