Screenshot tool paints no busy and hand cursor
Bug #659399 reported by
tsg1zzn
This bug affects 4 people
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| gnome-utils |
Fix Released
|
Medium
|
|||
| gnome-screenshot (Ubuntu) |
Triaged
|
Low
|
Unassigned | ||
Bug Description
Binary package hint: gnome-utils
If the cursor is a busy cursor and you take a screenshot, you get the normal cursor on the screenshot.
Also if the pointer is placed on a link the hand cursor is shown on screen, but a regular arrow pointer is included in the captured image.
ProblemType: Bug
DistroRelease: Ubuntu 10.10
Package: gnome-screenshot 2.31.1-0ubuntu1
ProcVersionSign
Uname: Linux 2.6.35-22-generic x86_64
NonfreeKernelMo
Architecture: amd64
Date: Tue Oct 12 20:32:21 2010
ExecutablePath: /usr/bin/
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release Candidate amd64 (20100928)
ProcEnviron:
LANGUAGE=en
LANG=nb_NO.utf8
SHELL=/bin/bash
SourcePackage: gnome-utils
Revision history for this message
| tsg1zzn (tsg1zzn) wrote | #1 |
Revision history for this message
| Sebastien Bacher (seb128) wrote | #2 |
| Changed in gnome-utils (Ubuntu): | |
| importance: | Undecided → Low |
| summary: |
- Screenshot tool paints no busy cursor + Screenshot tool paints no busy and hand cursor |
| description: | updated |
| Changed in gnome-utils: | |
| importance: | Unknown → Low |
| status: | Unknown → New |
| Changed in gnome-utils (Ubuntu): | |
| status: | New → Triaged |
| Changed in gnome-utils: | |
| status: | New → Invalid |
| Changed in gnome-utils: | |
| importance: | Low → Unknown |
| status: | Invalid → Unknown |
| Changed in gnome-utils: | |
| importance: | Unknown → Medium |
| status: | Unknown → New |
| affects: | gnome-utils (Ubuntu) → gnome-screenshot (Ubuntu) |
| Changed in gnome-utils: | |
| status: | New → Confirmed |
| Changed in gnome-utils: | |
| status: | Confirmed → Fix Released |
Revision history for this message
| bojojo@orange.fr (bojojo-orange) wrote | #3 |
To post a comment you must log in.
Thank you for your bug report. The issue is an upstream one and it would be nice if somebody having it could send the bug the to the people writting the software (https:/