gnome screen shot behaves strange on zesty unity8
Bug #1668428 reported by
kevin gunn
This bug report is a duplicate of:
Bug #1674477: gnome screenshot gtk-mir crashes on taking the shot under Mir.
Edit
Remove
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Canonical System Image |
New
|
High
|
Stephen M. Webb | ||
| gtk+3.0 (Ubuntu) |
New
|
High
|
William Hua | ||
| xorg-server (Ubuntu) |
New
|
High
|
Daniel van Vugt | ||
Bug Description
Updated Mar 20 zesty, clean u8 exploration
gnome screenshot will seemingly quit, and will not capture the desired screen
to repro:
1) launch screenshot app from the app drawer
2) make indications to take a screenshot ( i selected custom area to select)
3) "take screenshot"
result: application bail out, in the instance of "select area" case, it will take a screen shot in the instance of "full screen".
expected: get a screen shot of desired and the application should remain on screen.
I suspect this is due to screenshot's reliance on X and our use of Xmir not being completely worked out in terms of what the applications perception of the screen vs it's own window is.
| tags: | added: gtk-mir xmir |
Revision history for this message
| Daniel van Vugt (vanvugt) wrote | #1 |
| affects: | xorg-server (Ubuntu) → unity8 (Ubuntu) |
| tags: | removed: xmir |
| Changed in canonical-devices-system-image: | |
| status: | New → Incomplete |
| Changed in gtk+3.0 (Ubuntu): | |
| status: | New → Incomplete |
| Changed in unity8 (Ubuntu): | |
| status: | New → Incomplete |
| tags: | added: unity8-desktop |
| Changed in canonical-devices-system-image: | |
| milestone: | none → u8c-1 |
| assignee: | nobody → kevin gunn (kgunn72) |
| importance: | Undecided → High |
| summary: |
- gnome screen shot full lock up on zesty uniyt8 + gnome screen shot full lock up on zesty unity8 |
| summary: |
- gnome screen shot full lock up on zesty unity8 + gnome screen shot behaves strange on zesty unity8 |
| Changed in canonical-devices-system-image: | |
| status: | Incomplete → New |
| Changed in gtk+3.0 (Ubuntu): | |
| status: | Incomplete → New |
| no longer affects: | unity8 (Ubuntu) |
| Changed in gtk+3.0 (Ubuntu): | |
| importance: | Undecided → High |
| Changed in xorg-server (Ubuntu): | |
| importance: | Undecided → High |
Revision history for this message
| kevin gunn (kgunn72) wrote | #2 |
| description: | updated |
| Changed in canonical-devices-system-image: | |
| assignee: | kevin gunn (kgunn72) → Stephen M. Webb (bregma) |
| Changed in gtk+3.0 (Ubuntu): | |
| assignee: | nobody → William Hua (attente) |
| Changed in xorg-server (Ubuntu): | |
| assignee: | nobody → Daniel van Vugt (vanvugt) |
To post a comment you must log in.
The windowing oddity looks like bug 1665286.
I can't reproduce a "complete lock up" though. When that happens what does your unity8.log show?