dnd pointer lock when dragging tab between two gedit instances
Bug #880962 reported by
Gerd Katzenbeisser
This bug affects 15 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
gedit |
Fix Released
|
Medium
|
|||
gtk+3.0 (Ubuntu) |
Fix Released
|
High
|
Unassigned | ||
Oneiric |
Won't Fix
|
High
|
Unassigned | ||
Precise |
Fix Released
|
High
|
Unassigned |
Bug Description
TESTCASE:
- run gedit from unity (launcher or dash) or from a command line
- open a new tab in that gedit
- open a text file in nautilus (that should open a new gedit dialog rather than adding a tab to the previous one)
- dnd one of the tabs from the first gedit to the second one
-> without the update the cursor locks in dnd mode (go to a vt and stop gedit to get your session back), with the update it doesn't lock
When I start two instances of gedit (for example manual opening and opening a file) and dragging from one tab to the other freezes the complete unity desktop. When i look at the processes i only see one gedit instance running. If i kill it the gui is free.
Changed in unity (Ubuntu Oneiric): | |
status: | Confirmed → Triaged |
Changed in unity (Ubuntu): | |
status: | Confirmed → Triaged |
Changed in gedit (Ubuntu Oneiric): | |
status: | Confirmed → Triaged |
Changed in gedit (Ubuntu): | |
status: | Confirmed → Triaged |
no longer affects: | unity (Ubuntu) |
no longer affects: | unity (Ubuntu Oneiric) |
Changed in gedit: | |
importance: | Unknown → Medium |
status: | Unknown → New |
Changed in gedit: | |
status: | New → Incomplete |
Changed in gedit: | |
status: | Incomplete → Confirmed |
tags: | added: precise rls-mgr-p-tracking |
affects: | gedit (Ubuntu) → gtk+3.0 (Ubuntu) |
Changed in gtk+3.0 (Ubuntu): | |
status: | Triaged → Fix Committed |
Changed in gtk+3.0 (Ubuntu Precise): | |
status: | Triaged → Fix Committed |
description: | updated |
tags: |
added: verification-done removed: verification-needed |
Changed in gedit: | |
status: | Confirmed → Fix Released |
To post a comment you must log in.
Thank you for your bug report, I can confirm the issue there