FileChooserButton forgets file filters

Bug #367285 reported by Helge Stenström
2
Affects Status Importance Assigned to Milestone
PyGTK
Expired
Medium
gtk+2.0 (Ubuntu)
Triaged
Low
Ubuntu Desktop Bugs

Bug Description

A file filer is set to a FileChooserButton. The first time the FileChooserButton is clicked, the filter is there and works. The second time, the filter is gone. This can be confirmed by the FileChooser.list_filters() method, or by the look of the FileChooser dialog.

Expected behavior: The file filter is persistent.
Observed behavior: The file filter disappears after the first activation of the FileChooserButton.

Unknown if this is caused by the "button" or by the FileChooser.

Attached: small demonstration example.
Tested with Ubuntu 8.10 and python-gtk2 version 2.13.0ubuntu8.

Revision history for this message
Helge Stenström (h-stenstrom) wrote :
description: updated
Revision history for this message
Sebastien Bacher (seb128) wrote :

thank you for your bug report, is that specific to pygtk or do you get the same issue in C? should probably be sent to the people writting pygtk on bugzilla.gnome.org

Changed in pygtk (Ubuntu):
assignee: nobody → Ubuntu Desktop Bugs (desktop-bugs)
importance: Undecided → Low
status: New → Incomplete
Revision history for this message
Helge Stenström (h-stenstrom) wrote :

I have not tested on C, because I'm not comfortable with C and compiling stuff. I have not tested with Ubuntu 9.04 either, yet.

Revision history for this message
Sebastien Bacher (seb128) wrote :

changing the bug to NEW but it could be a programmer question rather than a bug

Changed in pygtk (Ubuntu):
status: Incomplete → New
Revision history for this message
Helge Stenström (h-stenstrom) wrote :

I've filed a bug upstream, as proposed. http://bugzilla.gnome.org/show_bug.cgi?id=580321
A comment there is: Cannot reproduce here. This was most likely a GTK+ (not PyGTK) bug that was fixed at some point.

Revision history for this message
Sebastien Bacher (seb128) wrote :

could you try on jaunty?

Changed in pygtk (Ubuntu):
status: New → Triaged
status: Triaged → Incomplete
Changed in pygtk:
status: Unknown → Invalid
Revision history for this message
Helge Stenström (h-stenstrom) wrote :

I have now tried in Ubuntu 9.04 (Jaunty), and the problem remains.

Revision history for this message
Sebastien Bacher (seb128) wrote :

you should comment on the GNOME bug to say that

Revision history for this message
Helge Stenström (h-stenstrom) wrote :

OK, I've told them. But the bug was marked as obsolete, when I had only tested with pygtk 2.13. I don't feel confident that this is not a programmer error, as I am a beginner with gtk programming, and only a python hobbyist. But my demo program is fairly simple. Everything that happens, happens inside gtk.main().
It would be interesting to try on another Linux distribution, and to try on Ubuntu, but in another language.

Revision history for this message
Helge Stenström (h-stenstrom) wrote :

The demo program works as expected on Solaris 8, with Python 2.5.1 and (probably) pygtk 2.10. So it's not a programmer error. Remains to see if the error is in pygtk or in gtk.

Revision history for this message
Helge Stenström (h-stenstrom) wrote :

The demo program is now translated to C, tested on RedHat 4, and it fails. This seems to be a gtk problem.

Revision history for this message
Sebastien Bacher (seb128) wrote :

confirming on jaunty

affects: pygtk (Ubuntu) → gtk+2.0 (Ubuntu)
Changed in gtk+2.0 (Ubuntu):
status: Incomplete → Triaged
affects: gtk+2.0 (Ubuntu) → pygtk (Ubuntu)
affects: pygtk (Ubuntu) → gtk+2.0 (Ubuntu)
affects: gtk+2.0 (Ubuntu) → pygtk (Ubuntu)
affects: pygtk (Ubuntu) → gtk+2.0 (Ubuntu)
Changed in pygtk:
status: Invalid → New
Changed in pygtk:
importance: Unknown → Medium
Changed in pygtk:
status: New → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.