Default filename for screenshots is problematic
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Gnome Screenshot |
Fix Released
|
Low
|
|||
gnome-screenshot (Ubuntu) |
Fix Released
|
Low
|
Unassigned |
Bug Description
Press "printscreen" and you'll get a default filename of:-
"Screenshot from YYYY-MM-DD HH:MM:SS.png"
Fine for browsing in nautilus and double clicking on, but this format (specifically the colons) has been a bane for me for some time.
1.
Tab completion fails:-
-rw-rw-r-- 1 alan alan 751K Sep 23 01:10 Screenshot from 2012-09-23 01:10:33.png
# tab completion works as far as here
alan@deep-
Screenshot\ from\ 2012-09-21\ 19\:40\:46.png
Screenshot\ from\ 2012-09-23\ 01\:01\:41.png
Screenshot\ from\ 2012-09-23\ 01\:10\:33.png
# get to here and it won't finish the filename off.
alan@deep-
2. scp fails.
alan@deep-
ssh: Could not resolve hostname Screenshot from 2012-09-23 01: Name or service not known
3. Ubuntu one file link in thunderbird fails
See bug 1054803
Whilst I can see an argument for fixing the bugs in all those other applications, wouldn't it make more sense to just not have mad filenames created in the first place.
I propose:-
"Screenshot_
ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: gnome-screenshot 3.4.1-0ubuntu1
ProcVersionSign
Uname: Linux 3.2.0-31-generic x86_64
ApportVersion: 2.0.1-0ubuntu13
Architecture: amd64
Date: Sun Sep 23 01:15:27 2012
EcryptfsInUse: Yes
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425)
SourcePackage: gnome-screenshot
UpgradeStatus: No upgrade log present (probably fresh install)
Changed in gnome-screenshot: | |
importance: | Unknown → Medium |
status: | Unknown → New |
Changed in gnome-screenshot: | |
status: | New → Invalid |
Changed in gnome-screenshot: | |
importance: | Medium → Unknown |
status: | Invalid → Unknown |
Changed in gnome-screenshot: | |
importance: | Unknown → Low |
status: | Unknown → New |
Changed in gnome-screenshot: | |
status: | New → Fix Released |
Status changed to 'Confirmed' because the bug affects multiple users.