Current gtk+ has a critical bug crashing apps, please upgrade gtk+.

Thanks for your bug. Without describing your issue nor a way to get it nor a pointing to upstream your bug is not really useful. Maybe you could give some information about it?

Hello,
Dialogs get hanged and unresponsive on close, if they contain file
chooser buttons.
This is a known gtk+ bug which was fixed last night.
I don't know the bug id of it in gnome bugzilla.
I know it from gtk+ irc, one of the leading developers of gtk+ told me
he jist fixed it.
I encountered this problem when developing an application with
GtkFileChooserButton, and went to gtk+ irc for help, and then told
that's a known bug just fixed in cvs.
Today several people have the same problem and also ask for help on irc.
This will block edgy release, if the fix doesn't go into ubuntu since
it break several gnome apps, such as.... evince?? (not sure, another
developer told me that)

On 9/30/06, Sebastien Bacher <email address hidden> wrote:
> Thanks for your bug. Without describing your issue nor a way to get it
> nor a pointing to upstream your bug is not really useful. Maybe you
> could give some information about it?
>
> ** Changed in: gtk+2.0 (Ubuntu)
> Importance: Undecided => Medium
> Assignee: (unassigned) => Ubuntu Desktop Bugs
> Status: Unconfirmed => Needs Info
>
> --
> Current gtk+ has a critical bug crashing apps, please upgrade gtk+.
> https://launchpad.net/bugs/63107
>

could you describe a situation where is happens, like:
- run evince
- open properties
- close evince

1. run evince
2. File/Open
3. Press Cancel to close the dialog.
4. Say bye bye to your evince.
5. pkill evince to kill the unresponsive app.

On 9/30/06, Sebastien Bacher <email address hidden> wrote:
> could you describe a situation where is happens, like:
> - run evince
> - open properties
> - close evince
>
> --
> Current gtk+ has a critical bug crashing apps, please upgrade gtk+.
> https://launchpad.net/bugs/63107
>

upstream bug (fixed) from bug #63191

not the same issue, the lock is fixed by http://cvs.gnome.org/viewcvs/gtk%2B/gtk/gtkfilesystemunix.c?r1=1.79&r2=1.80

that evince testcase doesn't bug on my desktop

note that 2.10.4 is the current version, there is no new version to upgrade to

OK, I provide another example.
Download and install this app:
http://pcmanfm.sourceforge.net/
There are ubuntu packages in download area.
After you get it installed, open the preference dialog. (Edit/Preference)
Then, press cancel., and the dialog hangs.
This problem doesn't exist on ubuntu dapper and debian sid.
It's not the bug of my app since it works well on other distros.
Thanks.

On 10/1/06, Sebastien Bacher <email address hidden> wrote:
> not the same issue, the lock is fixed by
> http://cvs.gnome.org/viewcvs/gtk%2B/gtk/gtkfilesystemunix.c?r1=1.79&r2=1.80
>
>
> ** Changed in: gtk+2.0 (Ubuntu)
> Status: Confirmed => Fix Committed
>
> --
> Current gtk+ has a critical bug crashing apps, please upgrade gtk+.
> https://launchpad.net/bugs/63107
>

This upload fixes the issue:

" gtk+2.0 (2.10.4-0ubuntu2) edgy; urgency=low
 .
   * debian/patches/007_password_char.patch:
     - patch update based on the version from fedora
   * debian/patches/009_stop_blinking_cursor_for_energy_save.patch:
     - upstream backport shipped with the fedora package,
       "Stop cursor blinking after a while, to save energy"
   * debian/patches/090_from_cvs_fix_filechooser_crasher.patch:
     - patch from CVS, fix a filechooser crasher on NULL base_path
       (Ubuntu: #63191)
   * debian/patches/091_from_cvs_fix_deadlock_fileselector_issue.patch:
     - patch from CVS, fix a deadlock fileselector issue (Ubuntu: #63107)"

Note there are 2 different backends of gtk file chooser.
One is gtk+, the other is gnome-vfs.
This can be set via gconf-editor.
I'm not sure which one ubuntu uses, and I have no idea which one is corrupted.
Please contact gtk+ developers for further info.
The fix was just commited 2 days ago, so there is no new release of gtk+ now.
Maybe there should be patches for 2 10.4.
gtk+ 2.10 series is not stable, and not yet very suitable for production use.
So I'm worried about the stability of edgy, since it'll be release soon.

On 10/1/06, Sebastien Bacher <email address hidden> wrote:
> note that 2.10.4 is the current version, there is no new version to
> upgrade to
>
> --
> Current gtk+ has a critical bug crashing apps, please upgrade gtk+.
> https://launchpad.net/bugs/63107
>

there is no need to be worried, we still have several weeks to fix bugs and regression like that crasher are usually fixed quickly. Your bug is not really optimal for several reason:
- the subject doesn't describe the bug clearly
- the description mentions there is a bug without any clear description of what the bug does and how to get it happening
- why are the "*" to "*last night*" useful for? Pointing that we are some hours late on CVS? Do you know any distribution shipping non-tarballs version? If that's to point to maintainer they are slow to do their job that's probably not the case and there is no need to force on that point
- you ask "Please upgrade gtk+ to the latest version" where the package is the uptodate version, there is no new version to upgrade to

We appreciate your enthousiast to try getting that issue fixed though. Maybe you can think about that next time you open a bug to make it easier to deal with by the maintainers. Ubuntu gets a lot of bug and having to ask several questions to understand what your issue is makes the job non-optimal for people working on it. Anyway the bug should be fixed now, let we know if it works for you

It works now.
Previously I haven't get the latest ubuntu package because of the
delay between official site and mirrors.
After upgrade to the latest version of gtk+ from ubuntu official repo,
it's fixed.
That debian patch seems to fix another issue; however, it's related to
this one, so both of them are fixed.
Thanks. It works now. (2.10.4ubuntu2)

On 10/1/06, Sebastien Bacher <email address hidden> wrote:
> there is no need to be worried, we still have several weeks to fix bugs and regression like that crasher are usually fixed quickly. Your bug is not really optimal for several reason:
> - the subject doesn't describe the bug clearly
> - the description mentions there is a bug without any clear description of what the bug does and how to get it happening
> - why are the "*" to "*last night*" useful for? Pointing that we are some hours late on CVS? Do you know any distribution shipping non-tarballs version? If that's to point to maintainer they are slow to do their job that's probably not the case and there is no need to force on that point
> - you ask "Please upgrade gtk+ to the latest version" where the package is the uptodate version, there is no new version to upgrade to
>
> We appreciate your enthousiast to try getting that issue fixed though.
> Maybe you can think about that next time you open a bug to make it
> easier to deal with by the maintainers. Ubuntu gets a lot of bug and
> having to ask several questions to understand what your issue is makes
> the job non-optimal for people working on it. Anyway the bug should be
> fixed now, let we know if it works for you
>
> --
> Current gtk+ has a critical bug crashing apps, please upgrade gtk+.
> https://launchpad.net/bugs/63107
>