Obex folders not correctly displayed in the file chooser
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| gvfs |
Fix Released
|
High
|
|||
| gvfs (Ubuntu) |
Fix Released
|
Low
|
Ubuntu Desktop Bugs | ||
| Hardy |
Invalid
|
Low
|
Ubuntu Desktop Bugs | ||
| libgnomeui (Ubuntu) |
Fix Released
|
Medium
|
Ubuntu Desktop Bugs | ||
| Hardy |
Fix Released
|
Medium
|
Ubuntu Desktop Bugs | ||
Bug Description
Binary package hint: gvfs
As I first wrote as a comment in Bug #196770, before being asked to submit another bug report:
.... However, perhaps on a related issue, if you open an obex device, for instance my Nokia S60 device, in the gtk file chooser, I can only see a folder with no name, where instead it should have been C: . I do not have any other bluetooth devices, and so it I cannot verify whether this is caused by the colon, or some other issue. This makes it impossible to browse obex bluetooth devices in the filechooser, and of course, the opening of them.
I note this bug on Ubuntu 8.04 (with the lastest updates applied as of yesterday).
I have attached as screenshot of the file chooser (from gedit, just in case that makes a difference - I know that it has been ported to gvfs). Notice that the folder name is null, and that if you double click on it, it either crashes or freezes the file chooser (and thus the parent application). This folder SHOULD be named "C:", and it does come up in nautilus.
Kind Regards,
Matthew
Related branches
| Matthew Wardrop (mister.wardrop) wrote | #1 |
| Pedro Villavicencio (pedro) wrote | #2 |
| Changed in gvfs: | |
| assignee: | nobody → desktop-bugs |
| importance: | Undecided → Low |
| status: | New → Incomplete |
| Matthew Wardrop (mister.wardrop) wrote | #3 |
| Changed in gvfs: | |
| status: | Incomplete → New |
| Sebastien Bacher (seb128) wrote | #4 |
| Changed in gvfs: | |
| status: | New → Triaged |
| Changed in gvfs: | |
| status: | Unknown → New |
| Sebastien Bacher (seb128) wrote | #5 |
| Changed in gvfs: | |
| status: | Triaged → Fix Committed |
| Changed in gvfs: | |
| status: | New → Fix Released |
| Sebastien Bacher (seb128) wrote | #6 |
| Changed in libgnomeui: | |
| assignee: | nobody → desktop-bugs |
| importance: | Undecided → Medium |
| status: | New → Fix Committed |
| Changed in gvfs: | |
| assignee: | nobody → desktop-bugs |
| importance: | Undecided → Low |
| status: | New → Invalid |
| Changed in libgnomeui: | |
| assignee: | nobody → desktop-bugs |
| importance: | Undecided → Medium |
| status: | New → Confirmed |
| Martin Pitt (pitti) wrote | #7 |
| Changed in libgnomeui: | |
| status: | Confirmed → Fix Committed |
| Sebastien Bacher (seb128) wrote | #8 |
| Changed in libgnomeui: | |
| status: | Fix Committed → Fix Released |
| Sebastien Bacher (seb128) wrote | #9 |
| Changed in gvfs: | |
| status: | Fix Committed → Fix Released |
| Martin Pitt (pitti) wrote | #10 |
| Changed in libgnomeui: | |
| status: | Fix Committed → Fix Released |
| Changed in gvfs: | |
| importance: | Unknown → High |
still an issue with latest packages?