Just updated from maverick-proposed. The test seems to be working great.
If I run into any other problems with it, I'll post further--for now, it
seems to be working great.
Great work, very much appreciated here.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bu
To add to this bug, when I get this error, it's unclear which
compression job caused it--the dialog provides no feedback as to what
archive file I was trying to create when I received it.
Often, I'll start 2 or 3 compression jobs at once--if I receive this
error after they've all completed, I have
Out of curiosity (and mostly for my education--I don't really know how
these things work), how does the process work for this to get fixed up?
I see on the upstream bug report that someone's attached a patch. How
does that patch make its way into the Ubuntu update process (and what
sort of time fr
I was primarily thinking of a alt+x mneomic-style hotkey, which for the
most part, is unavailable.
I just opened a few gtk programs to see if I could nail down exactly
what I'm thinking of. In a few of them (OO.write and Gimp, for example),
there IS a mnemonic hotkey for "Select File Type". Other
I've always felt, particularly on 15" and 14" laptop screens that
Nautilus' icons were bigger than they were useful.
How can we move this discussion beyond 'here's my preferences'? What's
the best way to approach user testing so this paper cut gets resolved?
--
Nautilus file browser toolbar is c
** Also affects: hundredpapercuts
Importance: Undecided
Status: New
--
gtkfilechooser save/save as dialog not 100% navigable by keyboard
https://bugs.launchpad.net/bugs/388289
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gtk+
Public bug reported:
When saving a file, the save/save as dialog does not offer any obvious
options to select the file format drop down, making navigation of this
dialog purely with the keyboard almost impossible.
Several other bugs are related to this keyboard navigation issue (Bug
#387957 and B
