| 2014-11-16 14:14:39 |
Rowan Berkeley |
bug |
|
|
added bug |
| 2014-11-16 14:19:22 |
Rowan Berkeley |
description |
This is new since I upgraded to 14.10, about 60 hours ago. Tested through four sessions. Not affected by any action in destination folder (eg, deleting any existing screenshot files there). Not affected by whether screenshot application or print screen button is used; not affected by whether screenshot is whole screen, desktop or selected area. The whole screen of the first attempt of the session is saved somewhere (I don't know where), and cannot be overwritten for the rest of the session, so new screenshots cannot be made without restarting. If I attempt a selected area of a new screen, I get the corresponding selected area of the first screen of the session, the one which cannot be overwritten. So - the screenshot application is working correctly, except that the first screen saved is being retained throughout the session and cannot be overwritten. And this is completely new since my upgrade to 14.10. |
This is new since I upgraded to 14.10, about 60 hours ago. Tested through four sessions. Not affected by any action in destination folder (eg, deleting any existing screenshot files there). Not affected by whether screenshot application or print screen button is used; not affected by whether screenshot is whole screen, desktop or selected area. The whole screen of the first attempt of the session is saved somewhere (I don't know where), and cannot be overwritten for the rest of the session, so new screenshots cannot be made without restarting. If I attempt a selected area of a new screen, I get the corresponding selected area of the first screen of the session, the one which cannot be overwritten. So - the screenshot application is working correctly, except that the first screen saved is being retained throughout the session and cannot be overwritten. And this is completely new since my upgrade to 14.10.
PS: I have tried the application "Shutter", which performs all screenshot functions in a more elaborate way, and I get the same result, therefore both the basic "gnome-screenshot" and "Shutter" use the same, so to say, image scratchpad to store their screenshots, and for both of them, once written to, this image scratchpad cannot be cleared for new images for the duration of the session thereafter. |
|
| 2014-11-16 14:38:51 |
Rowan Berkeley |
description |
This is new since I upgraded to 14.10, about 60 hours ago. Tested through four sessions. Not affected by any action in destination folder (eg, deleting any existing screenshot files there). Not affected by whether screenshot application or print screen button is used; not affected by whether screenshot is whole screen, desktop or selected area. The whole screen of the first attempt of the session is saved somewhere (I don't know where), and cannot be overwritten for the rest of the session, so new screenshots cannot be made without restarting. If I attempt a selected area of a new screen, I get the corresponding selected area of the first screen of the session, the one which cannot be overwritten. So - the screenshot application is working correctly, except that the first screen saved is being retained throughout the session and cannot be overwritten. And this is completely new since my upgrade to 14.10.
PS: I have tried the application "Shutter", which performs all screenshot functions in a more elaborate way, and I get the same result, therefore both the basic "gnome-screenshot" and "Shutter" use the same, so to say, image scratchpad to store their screenshots, and for both of them, once written to, this image scratchpad cannot be cleared for new images for the duration of the session thereafter. |
This is new since I upgraded to 14.10, about 60 hours ago. Tested through four sessions. Not affected by any action in destination folder (eg, deleting any existing screenshot files there). Not affected by whether screenshot application or print screen button is used; not affected by whether screenshot is whole screen, desktop or selected area. The whole screen of the first attempt of the session is saved somewhere (I don't know where), and cannot be overwritten for the rest of the session, so new screenshots cannot be made without restarting. If I attempt a selected area of a new screen, I get the corresponding selected area of the first screen of the session, the one which cannot be overwritten. So - the screenshot application is working correctly, except that the first screen saved is being retained throughout the session and cannot be overwritten. And this is completely new since my upgrade to 14.10.
PS: I have tried the application "Shutter", which performs all screenshot functions in a more elaborate way, and I get the same result, therefore both the basic "gnome-screenshot" and "Shutter" use the same, so to say, image scratchpad to store their screenshots, and for both of them, once written to, this image scratchpad cannot be cleared for new images for the duration of the session thereafter.
PPS: I see this is comparable to bug #1103847. I do have fglrx, just as in that bug situation. But I am not getting an error report in the terminal, as is reported there. |
|
| 2014-11-18 06:21:18 |
Rowan Berkeley |
description |
This is new since I upgraded to 14.10, about 60 hours ago. Tested through four sessions. Not affected by any action in destination folder (eg, deleting any existing screenshot files there). Not affected by whether screenshot application or print screen button is used; not affected by whether screenshot is whole screen, desktop or selected area. The whole screen of the first attempt of the session is saved somewhere (I don't know where), and cannot be overwritten for the rest of the session, so new screenshots cannot be made without restarting. If I attempt a selected area of a new screen, I get the corresponding selected area of the first screen of the session, the one which cannot be overwritten. So - the screenshot application is working correctly, except that the first screen saved is being retained throughout the session and cannot be overwritten. And this is completely new since my upgrade to 14.10.
PS: I have tried the application "Shutter", which performs all screenshot functions in a more elaborate way, and I get the same result, therefore both the basic "gnome-screenshot" and "Shutter" use the same, so to say, image scratchpad to store their screenshots, and for both of them, once written to, this image scratchpad cannot be cleared for new images for the duration of the session thereafter.
PPS: I see this is comparable to bug #1103847. I do have fglrx, just as in that bug situation. But I am not getting an error report in the terminal, as is reported there. |
This is new since I upgraded to 14.10, about 60 hours ago. Tested through four sessions. Not affected by any action in destination folder (eg, deleting any existing screenshot files there). Not affected by whether screenshot application or print screen button is used; not affected by whether screenshot is whole screen, desktop or selected area. The whole screen of the first attempt of the session is saved somewhere (I don't know where), and cannot be overwritten for the rest of the session, so new screenshots cannot be made without restarting. If I attempt a selected area of a new screen, I get the corresponding selected area of the first screen of the session, the one which cannot be overwritten. So - the screenshot application is working correctly, except that the first screen saved is being retained throughout the session and cannot be overwritten. And this is completely new since my upgrade to 14.10.
PS: I have tried the application "Shutter", which performs all screenshot functions in a more elaborate way, and I get the same result, therefore both the basic "gnome-screenshot" and "Shutter" use the same, so to say, image scratchpad to store their screenshots, and for both of them, once written to, this image scratchpad cannot be cleared for new images for the duration of the session thereafter.
PPS: I see this is comparable to bug #1103847. I do have fglrx, just as in that bug situation. But I am not getting an error report in the terminal, as is reported there.
PPPS: Using Synaptic, I completely removed fglrx (this means in fact fglrx-core 2:14.201-0ububtu2, because this is what was installed by default; the full version of fglrx is not installed by default, and was not present). But problem is persisting. Terminal still does not report any error, so symptomatology is still different to that reported in bug #1103847. |
|
