Bug 171381

Summary:	gnome-screenshot does not support absolute path
Product:	[Fedora] Fedora	Reporter:	Thomas Zehetbauer <thomasz>
Component:	gnome-utils	Assignee:	Ray Strode [halfline] <rstrode>
Status:	CLOSED CANTFIX	QA Contact:
Severity:	medium	Docs Contact:
Priority:	medium
Version:	6
Target Milestone:	---
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2007-08-14 15:48:24 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Thomas Zehetbauer 2005-10-21 12:05:00 UTC

Using an absolute path like /home/$user/screenshot.png in gnome-screenshot fails
silently. According to strace gnome-screenshot attempts to append this path to
the folder specified, e.g. $HOME/Desktop/home/$user/screenshot.png and fails
because that directory does not exist.

Comment 1 Christian Iseli 2007-01-22 10:20:04 UTC

This report targets the FC3 or FC4 products, which have now been EOL'd.

Could you please check that it still applies to a current Fedora release, and
either update the target product or close it ?

Thanks.

Comment 2 Thomas Zehetbauer 2007-01-22 15:07:10 UTC

The problem persists in
- Fedora Core 6
- gnome-utils-2.16.0-1.fc6.x86_64
- Gnome gnome-panel-screenshot 2.16.0

Comment 3 Ray Strode [halfline] 2007-08-14 15:48:24 UTC

The information we've requested above is required in order
to review this problem report further and diagnose/fix the
issue if it is still present.  Since there haven't been any
updates to the report in quite a long time now after we've
requested additional information, we're assuming the problem
is either no longer present in our current OS release, or
that there is no longer any interest in tracking the problem.

Setting status to CANTFIX, however if you still
experience this problem after updating to our latest Fedora
Core release and are still interested in Red Hat tracking
the issue, and assisting in troubleshooting the problem,
please feel free to provide the information requested above,
and reopen the report.

Thank you in advance.

(this message is mass message)