desktop-packages team mailing list archive

[IKT <david@xxxxxxxxxx>]

Pausanias, we get it, here's the issue as I see it and I'll best
'transcribe' it for non-computer scientists ;)

1) 2010-04-09

Stephen makes the original bug report.

2) 2010-05-01

Luke Plant confirms the bug is present in GTK2.0

3) 2010-10-11

Tristan Moody reports the bug upstream with Gnome, as they are the
developers of the GTK software, therefore they are the ones who would be
best equipped to fix it

4) 2010-10-24

André Klapper (A Gnome developer) advises that he can't replicate the
bug, and therefore can't fix the issue. He then requests someone try GTK
2.22.

5) 2010-10-27

Tristan Moody reports that it appears that the bug is fixed in 2.22

--
At this stage there is no patch for the bug, therefore there is nothing to simply throw down the update pipe. This is the issue, if there was a patch for the bug we wouldn't be having this convo, the issue would have been fixed long ago.

But because the Gnome developer couldn't find the bug in 2.0, this bug
never existed in Gnome's world in the first place.

I mean the Gnome Developer (André Klapper) response could have been "don't care, go away" because nobody got anything useful out of it except that the bug they couldn't find is apparently fixed in GTK 2.2
--

6) 2011-11-29

Ikt runs across the bug from reddit :D

--

"If there isn't a regular Ubuntu dev, whether paid or volunteer, who
recognizes how important this bug is, then I give up on Ubuntu."

There's lots of people who do realise how important it is, however
there's a few who don't understand the reason why Ubuntu simply haven't
fixed the bug, I mean it's fixed in 2.22, so just update to 2.22
already!

I think part of the issue is understanding just how big a package GTK
is, and just how unhappy many people would be if Ubuntu sent down the
update and broke the entire desktop, which co-incidentally uses GTK for
the majority of it.

"if you do recognize how important this bug is to fix, but lack the
willingness to put your expertise into use for 2 minutes to follow that
procedure"

That's the problem, it's not a 2 minute fix because there's no patch.

So here are the options since we have no patch:

a) leave as is, a bug that affects a few people, and I mean 'a few' in a
nice way, a bug that affects just 1 person (ie me) sucks (Hi #873016  :)
), and having it effect 30 is worse, but even medium level bugs affect
50%+ of users, and that's not indicated here.

b) send down GTK2.22 as a gigantic update that may break the critical
applications and make 90%+ very unhappy.

That is as is my understanding of the options on the table, if anyone
has any corrections I'm happy to be hear them.

And yes many of us are well aware of the limitations of the linux
desktop and are working on changing this, unfortunately this doesn't
help now :(

Hope this helps. :-)

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gtk+2.0 in Ubuntu.
https://bugs.launchpad.net/bugs/558674

Title:
  Open file dialog malfunctions in lucid

Status in GTK+ GUI Toolkit:
  Fix Released
Status in “gtk+2.0” package in Ubuntu:
  Fix Released
Status in “gtk+2.0” source package in Lucid:
  Confirmed

Bug description:
  Binary package hint: anjuta

  The open file window in firefox or google chrome is selecting the
  wrong file. When I select the file I want to upload the correct
  filename appears in the location field. However when I click on the
  open tab the wrong file gets uploaded normally one that is a couple of
  places wither above or below the selected file in the directory
  listing. This seems to be fairly random. Somtimes the correct file
  gets uploaded, other times a file that is alphabetically close... I
  Hope this is understandable :)

To manage notifications about this bug go to:
https://bugs.launchpad.net/gtk/+bug/558674/+subscriptions