Bug 853399
| Summary: | REGRESSION: FileDialog no longer returns the selected directory | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Johan Vromans <jvromans> | ||||
| Component: | gtk2 | Assignee: | Matthias Clasen <mclasen> | ||||
| Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||
| Severity: | high | Docs Contact: | |||||
| Priority: | high | ||||||
| Version: | 17 | CC: | jpopelka, kalevlember, mclasen, qxc, rdieter | ||||
| Target Milestone: | --- | ||||||
| Target Release: | --- | ||||||
| Hardware: | x86_64 | ||||||
| OS: | Linux | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | gtk2-2.24.18-1.fc18 | Doc Type: | Bug Fix | ||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2013-05-28 01:03:15 UTC | Type: | Bug | ||||
| Regression: | --- | Mount Type: | --- | ||||
| Documentation: | --- | CRM: | |||||
| Verified Versions: | Category: | --- | |||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||
| Embargoed: | |||||||
| Attachments: |
|
||||||
Changed component to gtk2. AFAIK, F17 wxWidgets is still gtk2 based. I've verified that by downgrading gtk2-2.24.11-1 to gtk2-2.24.10-2 the problems disappear. Is it considered normal practice to introduce a bug that renders several application programs inoperable and then fully ignore the bug reports? no it is not. that said, you'll likely have more luck posting upstream, bugzilla.gnome.org It is confirmed this bug appears with Fedora only, other distributions are not affected/work well. So why should one ask for a fix somewhere else? If you want higher chances of getting some sort of response, I'd recommend you consider my advice. it's ultimately up to you, of course. I've always assumed that comments from an organisation like Red Hat / Fedora were more likely to be taken seriously than comments from individual (Gnome) users. There have been a lot of filechooser related fixes upstream. It would be great if you could check whether your issue is fixed. If not, please file a bug upstream at: https://bugzilla.gnome.org/enter_bug.cgi?product=gtk%2B&version=2.24.x I am doing a gtk2 2.24.18 build for Fedora 18; can you give it a try? gtk2-2.24.18-1.fc18 has been submitted as an update for Fedora 18. https://admin.fedoraproject.org/updates/gtk2-2.24.18-1.fc18 Package gtk2-2.24.18-1.fc18: * should fix your issue, * was pushed to the Fedora 18 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing gtk2-2.24.18-1.fc18' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2013-9336/gtk2-2.24.18-1.fc18 then log in and leave karma (feedback). Backported gtk2-2.24.18-1.fc18 to fc17 and verified that the problem is solved. Thanks! gtk2-2.24.18-1.fc18 has been pushed to the Fedora 18 stable repository. If problems still persist, please make note of it in this bug report. |
Created attachment 608495 [details] Program demonstrating the bug Description of problem: Several programs that use Gnome file and directory dialogs stopped working correctly. Version-Release number of selected component (if applicable): Fedora 17 on x86_64 with all updates (the system is updated several times per week). How reproducible: Steps to Reproduce: 1. Run the attached python program. 2. Select a file somewhere. 3. Inspect the result dialog Actual results: For example, when HOME is /home/jv, and the file selected is /home/jv/foo/bar.txt, the results are: path = /home/jv/foo/bar.txt filename = bar.txt directory = /homejv Expected results: path = /home/jv/foo/bar.txt filename = bar.txt directory = /homejv/foo Additional info: Since many programs seem to process the filename and directory, concatenating them if necessary, they end up with the wrong filename. Programs that process the result of GetPath do not have problems. The DirDialog has similar problems. This change was introduced with an update somewhen in the first week(s) of august 2012. Before that time I never noticed anything problematic. After that time several programs started misbehaving to the point of being unusable.