Bug 1025947
| Summary: | gnome-screenshot will seg fault if I have a / in filename | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Marcel Ribeiro Dantas <ribeirodantasdm> |
| Component: | gnome-screenshot | Assignee: | Matthias Clasen <mclasen> |
| Status: | CLOSED EOL | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 19 | CC: | ccecchi, mclasen, pinode, tiagomatos |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2015-02-17 18:59:48 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: | |||
|
Description
Marcel Ribeiro Dantas
2013-11-02 12:10:44 UTC
Thanks for reporting about this bug. I don't like how you worded it though. You make it sound like slashes must be prohibited while I think specifying a full path must be allowed. And this is the way I prefer it done. It's quite annoying to browse the directory (quite slow). I want to write something like /tmp/ss.png in the name field. The bug is always reproducible for me Steps to Reproduce: 1. gnome gnome-screenshot --interactive 2. Choose for the name the following value: /tmp/test.png 3. Save pool[30005]: segfault at 0 ip (null) sp 00007f002745dbf8 error 14 in gnome-screenshot[400000+12000] You're right, specifying a full path would be pretty nice. I only meant to write a more general report that regardless of the string being a path or not, the presence of a slash was what [apparently] would make it seg fault. This message is a notice that Fedora 19 is now at end of life. Fedora has stopped maintaining and issuing updates for Fedora 19. It is Fedora's policy to close all bug reports from releases that are no longer maintained. Approximately 4 (four) weeks from now this bug will be closed as EOL if it remains open with a Fedora 'version' of '19'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 19 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. Fedora 19 changed to end-of-life (EOL) status on 2015-01-06. Fedora 19 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed. |