Bug 501023

This is packagekit.  I wasn't happy about the dialog either.  Lets see what Richard can do.

In my experience it also took a bit too long to show the dialog, and then the search said no fonts matched.  Ideally it should only show the dialog if there exists fonts to install.  And should query that from the local cache (even if it's two months old, who cares?) and be fast...

This bug appears to have been reported against 'rawhide' during the Fedora 11 development cycle.
Changing version to '11'.

More information and reason for this action is here:
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Ping?

-- 
Steven M. Parrish - KDE Triage Master
                  - PackageKit Triager
Fedora Bugzappers volunteer triage team
https://fedoraproject.org/wiki/BugZappers

(In reply to comment #0)
> They should be "No" and "Yes", or else the question should be changed.  

The question was changed.

(In reply to comment #1)
> In my experience it also took a bit too long to show the dialog, and then the
> search said no fonts matched.  Ideally it should only show the dialog if there
> exists fonts to install.  And should query that from the local cache (even if
> it's two months old, who cares?) and be fast...  

Right, so we need some sort of caching. We've got sqlite caches in the daemon for other stuff, so this is no big problem. How do I get a list of all packages that have a :lang=* properties? I'm guessing we have to tweak the API so that we can get all provides of a certain type.

I also think we have to be a bit careful about caching cached data, and maybe should look at why yum takes so long to return results. If we just cache when a search failed, we also have to be careful that a package isn't then added to the repo that we then ignore.

Ideas welcome.

> Ideas welcome.

It should use a GtkInfoBar (ie, the firefox-style yellow box that slides down from the top of the window) rather than a dialog. Less intrusive.

And it should have a higher threshold for deciding when to run. Most of the time I see it, it's because I'm looking at some binary garbage, and it just so happens that 3 consecutive bytes of it form a UTF-8 character in some totally random script. For letters at least, it should only run if there are a few of them in a row, suggesting there's an actual word in that script written there, not just an accidental random character. For non-letters though, that heuristic might not be appropriate (eg, mathematical characters).

(In reply to comment #5)

> It should use a GtkInfoBar (ie, the firefox-style yellow box that slides down
> from the top of the window) rather than a dialog. Less intrusive.

That's not possible since the dialog is shown by the gnome-packagekit process.  I still think a notification bubble kind of thing may make more sense.


> And it should have a higher threshold for deciding when to run. Most of the
> time I see it, it's because I'm looking at some binary garbage, and it just so
> happens that 3 consecutive bytes of it form a UTF-8 character in some totally
> random script. For letters at least, it should only run if there are a few of
> them in a row, suggesting there's an actual word in that script written there,
> not just an accidental random character. For non-letters though, that heuristic
> might not be appropriate (eg, mathematical characters).  

If we only show the dialog if fonts *are* available, it would be a lot less annoying.

Ping?

-- 
Steven M. Parrish - KDE Triage Master
                  - PackageKit Triager
Fedora Bugzappers volunteer triage team
https://fedoraproject.org/wiki/BugZappers

https://bugzilla.gnome.org/show_bug.cgi?id=593424

commit a8113a8b2abe2900b1ab87f3a79c7f1247e0b2a4
Author: Richard Hughes <richard>
Date:   Tue Nov 17 12:49:25 2009 +0000

    Add a GConf key to add program exec names to ignore all DBus requests from. Fixes rh#501023