298754 - Save As window flickers Mozilla freezes

Status: RESOLVED FIXED

(Core Graveyard :: GFX: Gtk, defect)

Description

[Mariusz Wodzicki]

User-Agent:       Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.8) Gecko/20050513 Fedora/1.7.8-1.3.1
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.8) Gecko/20050513 Fedora/1.7.8-1.3.1

Save Link Target opens the Save As Window.
Click on `Save in folder' and then click on
the directory name WHOSE NAME IS LONGER THAN
the box showing its name.

If the directory is empty, then the pop up
window opened up by the `Save in folder' dialog
flickers, mozilla freezes. Clicking `Cancel'
or trying to kill the window doesn't work.

I must go to a terminal window and kill the
whole mozilla process


Reproducible: Always

Steps to Reproduce:
1. Described above
2.
3.

Actual Results:  
I had this several times today. It happens everytime
I do the above.

Expected Results:  
This problem is very specific but very annoying. I
experienced it many times while saving sensitive
data (scientific articles) that I access from
commercial publisher's paid subscription pages.

This problem happens irrespective of which
publisher's articles I am dowloading

Comment 1

[Andrew Schultz]

this would be http://bugzilla.gnome.org/show_bug.cgi?id=154007

the bug affects gtk versions < 2.6, so anything but the latest distros get hit
by this

==> Gtk although there's probably nothing that can be done here

Comment 2

[Gervase Markham [:gerv]]

This is an automated message, with ID "auto-resolve01".

This bug has had no comments for a long time. Statistically, we have found that
bug reports that have not been confirmed by a second user after three months are
highly unlikely to be the source of a fix to the code.

While your input is very important to us, our resources are limited and so we
are asking for your help in focussing our efforts. If you can still reproduce
this problem in the latest version of the product (see below for how to obtain a
copy) or, for feature requests, if it's not present in the latest version and
you still believe we should implement it, please visit the URL of this bug
(given at the top of this mail) and add a comment to that effect, giving more
reproduction information if you have it.

If it is not a problem any longer, you need take no action. If this bug is not
changed in any way in the next two weeks, it will be automatically resolved.
Thank you for your help in this matter.

The latest beta releases can be obtained from:
Firefox:     http://www.mozilla.org/projects/firefox/
Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html
Seamonkey:   http://www.mozilla.org/projects/seamonkey/

Comment 3

[Hideo Oshima]

Is this the same problem as bug 290071?

Comment 4

[Boris Zbarsky [:bzbarsky]]

> ==> Gtk although there's probably nothing that can be done here

Sure there is.  We can not use the GTK2 filepicker unless the GTK version is at least GTK 2.6.

This sounds like a serious enough issue that we should consider not shipping 1.8 with it...  Chris, could you please take a look at fixing this?

Comment 5

[Scott MacGregor]

Did we not use the GTK file picker in 1.0.x and that's why it works there? Or was this broken for 1.0.x too?

Comment 6

[Asa Dotzler [:asa]]

If there's a near-zero risk patch, please nominate this to block rc2 and we might take it as a ride-along fix if we're forced to do another release.

Comment 7

[Boris Zbarsky [:bzbarsky]]

The patch would be to just up the required GTK2 version to use the GTK2 filepicker to whatever version of GTK2 is not buggy.

Of course whether we're willing to do that is a separate issue; I'm not qualified to judge (especially since I personally don't use the GTK2 filepicker at all, so in the end there's a severe case of not caring one whit on my end).

Comment 8

[Mike Connor [:mconnor]]

caillon says he doesn't care, the place to fix would be here: http://lxr.mozilla.org/mozilla/source/widget/src/gtk2/nsWidgetFactory.cpp#95 

Comment 9

[Christopher Aillon (sabbatical, not receiving bugmail)]

Resolving this; the required version is now 2.6.3