| 2011-11-16 02:22:20 |
WenLong FENG |
bug |
|
|
added bug |
| 2011-11-16 02:22:20 |
WenLong FENG |
attachment added |
|
source code https://bugs.launchpad.net/bugs/890947/+attachment/2598345/+files/gdkconfig.cpp |
|
| 2011-11-16 02:37:38 |
dobey |
affects |
ubuntuone-client |
unity (Ubuntu) |
|
| 2011-11-26 01:38:15 |
Bilal Akhtar |
unity: status |
New |
Confirmed |
|
| 2011-11-26 01:38:18 |
Bilal Akhtar |
unity (Ubuntu): status |
New |
Confirmed |
|
| 2011-11-26 01:38:20 |
Bilal Akhtar |
unity: importance |
Undecided |
Low |
|
| 2011-11-26 01:38:23 |
Bilal Akhtar |
unity (Ubuntu): importance |
Undecided |
Low |
|
| 2011-11-29 13:24:53 |
Tom Ellis |
description |
when using unity 3d on ubuntu, after creating a top-level gtk widget, the window manager sends GDK_CONFIGURE with position as (0,0) although I have set the initial position to some different value.
This dose not happen on gnome/unity 2d environment. It will cause seriously issue when we rely on this event to locate our window.
Source code attached, you could compile it and launch it from terminal, the GDK_CONFIGURE event will be printed out. |
= Problem =
After creating a top-level GTK widget, the window manager sends GDK_CONFIGURE with the position as (0,0) even though the initial position is already set to a different value.
= Environment =
* Ubuntu 11.10 (Oneiric) i386
* Unity - 4.22.0-0ubuntu3
This problem not occur under gnome or unity-2d.
= Impact =
This causes issues for applications that rely on this GDK_CONFIGURE to locate their app window.
= Steps to reproduce =
1. Compile gdkconfig.cpp
2. Launch it from a terminal
3. GDK_CONFIGURE event will be printed out
= Original text =
when using unity 3d on ubuntu, after creating a top-level gtk widget, the window manager sends GDK_CONFIGURE with position as (0,0) although I have set the initial position to some different value.
This dose not happen on gnome/unity 2d environment. It will cause seriously issue when we rely on this event to locate our window.
Source code attached, you could compile it and launch it from terminal, the GDK_CONFIGURE event will be printed out. |
|
| 2011-11-29 13:25:04 |
Tom Ellis |
bug |
|
|
added subscriber Tom Ellis |
| 2011-11-29 13:30:51 |
Tom Ellis |
summary |
unity 3d window manager send initial GDK_CONFIGURE event with position as (0,0) |
Unity sends initial GDK_CONFIGURE event with position as (0,0) |
|
| 2011-11-29 17:35:41 |
Tom Ellis |
description |
= Problem =
After creating a top-level GTK widget, the window manager sends GDK_CONFIGURE with the position as (0,0) even though the initial position is already set to a different value.
= Environment =
* Ubuntu 11.10 (Oneiric) i386
* Unity - 4.22.0-0ubuntu3
This problem not occur under gnome or unity-2d.
= Impact =
This causes issues for applications that rely on this GDK_CONFIGURE to locate their app window.
= Steps to reproduce =
1. Compile gdkconfig.cpp
2. Launch it from a terminal
3. GDK_CONFIGURE event will be printed out
= Original text =
when using unity 3d on ubuntu, after creating a top-level gtk widget, the window manager sends GDK_CONFIGURE with position as (0,0) although I have set the initial position to some different value.
This dose not happen on gnome/unity 2d environment. It will cause seriously issue when we rely on this event to locate our window.
Source code attached, you could compile it and launch it from terminal, the GDK_CONFIGURE event will be printed out. |
= Problem =
After creating a top-level GTK widget, the window manager sends GDK_CONFIGURE with the position as (0,0) even though the initial position is already set to a different value.
= Environment =
* Ubuntu 11.10 (Oneiric) i386
* Unity - 4.22.0-0ubuntu3
= Impact =
This causes issues for applications that rely on this GDK_CONFIGURE to locate their app window.
= Steps to reproduce =
1. Compile gdkconfig.cpp
2. Launch it from a terminal
3. Observe output from terminal
4. Click "OK" to launch a new window
5. Observe logs, you should see something like this:
popup window created gdkwindow -- 7063232
GDK_CONFIGURE : window -- 7063232, x -- 250, y -- 250, width -- 200, height -- 200
GDK_CONFIGURE : window -- 7063232, x -- 0, y -- 0, width -- 200, height -- 200
GDK_CONFIGURE : window -- 7063232, x -- 0, y -- 0, width -- 200, height -- 200
GDK_CONFIGURE : window -- 7063232, x -- 0, y -- 0, width -- 200, height -- 200
GDK_CONFIGURE : window -- 7063232, x -- 251, y -- 275, width -- 200, height -- 200
When running under Natty or Unity-2D, GDK_CONFIGURE is never set to 0,0.
= Original text =
when using unity 3d on ubuntu, after creating a top-level gtk widget, the window manager sends GDK_CONFIGURE with position as (0,0) although I have set the initial position to some different value.
This dose not happen on gnome/unity 2d environment. It will cause seriously issue when we rely on this event to locate our window.
Source code attached, you could compile it and launch it from terminal, the GDK_CONFIGURE event will be printed out. |
|
| 2011-11-29 17:38:38 |
Tom Ellis |
description |
= Problem =
After creating a top-level GTK widget, the window manager sends GDK_CONFIGURE with the position as (0,0) even though the initial position is already set to a different value.
= Environment =
* Ubuntu 11.10 (Oneiric) i386
* Unity - 4.22.0-0ubuntu3
= Impact =
This causes issues for applications that rely on this GDK_CONFIGURE to locate their app window.
= Steps to reproduce =
1. Compile gdkconfig.cpp
2. Launch it from a terminal
3. Observe output from terminal
4. Click "OK" to launch a new window
5. Observe logs, you should see something like this:
popup window created gdkwindow -- 7063232
GDK_CONFIGURE : window -- 7063232, x -- 250, y -- 250, width -- 200, height -- 200
GDK_CONFIGURE : window -- 7063232, x -- 0, y -- 0, width -- 200, height -- 200
GDK_CONFIGURE : window -- 7063232, x -- 0, y -- 0, width -- 200, height -- 200
GDK_CONFIGURE : window -- 7063232, x -- 0, y -- 0, width -- 200, height -- 200
GDK_CONFIGURE : window -- 7063232, x -- 251, y -- 275, width -- 200, height -- 200
When running under Natty or Unity-2D, GDK_CONFIGURE is never set to 0,0.
= Original text =
when using unity 3d on ubuntu, after creating a top-level gtk widget, the window manager sends GDK_CONFIGURE with position as (0,0) although I have set the initial position to some different value.
This dose not happen on gnome/unity 2d environment. It will cause seriously issue when we rely on this event to locate our window.
Source code attached, you could compile it and launch it from terminal, the GDK_CONFIGURE event will be printed out. |
= Problem =
After creating a top-level GTK widget, the window manager sends GDK_CONFIGURE with the position as (0,0) even though the initial position is already set to a different value.
= Environment =
* Ubuntu 11.10 (Oneiric) i386
* Unity - 4.22.0-0ubuntu3
= Impact =
This causes issues for applications that rely on this GDK_CONFIGURE to locate their app window.
= Steps to reproduce =
1. Compile gdkconfig.cpp: g++ -o gdktest gdkconfig.cpp `pkg-config --libs gtk+-2.0` `pkg-config --cflags gtk+-2.0`
2. Launch it from a terminal
3. Observe output from terminal
4. Click "OK" to launch a new window
5. Observe logs, you should see something like this:
popup window created gdkwindow -- 7063232
GDK_CONFIGURE : window -- 7063232, x -- 250, y -- 250, width -- 200, height -- 200
GDK_CONFIGURE : window -- 7063232, x -- 0, y -- 0, width -- 200, height -- 200
GDK_CONFIGURE : window -- 7063232, x -- 0, y -- 0, width -- 200, height -- 200
GDK_CONFIGURE : window -- 7063232, x -- 0, y -- 0, width -- 200, height -- 200
GDK_CONFIGURE : window -- 7063232, x -- 251, y -- 275, width -- 200, height -- 200
When running under Natty or Unity-2D, GDK_CONFIGURE is never set to 0,0.
= Original text =
when using unity 3d on ubuntu, after creating a top-level gtk widget, the window manager sends GDK_CONFIGURE with position as (0,0) although I have set the initial position to some different value.
This dose not happen on gnome/unity 2d environment. It will cause seriously issue when we rely on this event to locate our window.
Source code attached, you could compile it and launch it from terminal, the GDK_CONFIGURE event will be printed out. |
|
| 2011-12-12 10:09:44 |
Tom Ellis |
bug |
|
|
added subscriber Sam Spilsbury |
| 2011-12-12 11:51:24 |
Launchpad Janitor |
branch linked |
|
lp:~smspillaz/compiz-core/compiz-core.fix_890947 |
|
| 2011-12-12 11:53:20 |
Sam Spilsbury |
bug task added |
|
compiz |
|
| 2011-12-12 11:53:33 |
Sam Spilsbury |
bug task added |
|
compiz (Ubuntu) |
|
| 2011-12-12 11:53:43 |
Sam Spilsbury |
unity: status |
Confirmed |
Invalid |
|
| 2011-12-12 11:53:46 |
Sam Spilsbury |
compiz (Ubuntu): status |
New |
Invalid |
|
| 2011-12-12 11:53:50 |
Sam Spilsbury |
compiz (Ubuntu): status |
Invalid |
In Progress |
|
| 2011-12-12 11:53:56 |
Sam Spilsbury |
compiz: importance |
Undecided |
Medium |
|
| 2011-12-12 11:53:58 |
Sam Spilsbury |
compiz: assignee |
|
Sam Spilsbury (smspillaz) |
|
| 2011-12-12 11:54:00 |
Sam Spilsbury |
unity: assignee |
|
Sam Spilsbury (smspillaz) |
|
| 2011-12-12 11:54:04 |
Sam Spilsbury |
compiz (Ubuntu): assignee |
|
Sam Spilsbury (smspillaz) |
|
| 2011-12-12 11:54:07 |
Sam Spilsbury |
unity (Ubuntu): assignee |
|
Sam Spilsbury (smspillaz) |
|
| 2011-12-12 11:54:09 |
Sam Spilsbury |
unity (Ubuntu): status |
Confirmed |
Invalid |
|
| 2011-12-12 11:54:29 |
Sam Spilsbury |
bug |
|
|
added subscriber Ubuntu Stable Release Updates Team |
| 2011-12-12 11:57:25 |
Sam Spilsbury |
attachment added |
|
fix_890947.patch https://bugs.launchpad.net/ubuntu/+source/unity/+bug/890947/+attachment/2629428/+files/fix_890947.patch |
|
| 2011-12-12 12:14:23 |
Sam Spilsbury |
description |
= Problem =
After creating a top-level GTK widget, the window manager sends GDK_CONFIGURE with the position as (0,0) even though the initial position is already set to a different value.
= Environment =
* Ubuntu 11.10 (Oneiric) i386
* Unity - 4.22.0-0ubuntu3
= Impact =
This causes issues for applications that rely on this GDK_CONFIGURE to locate their app window.
= Steps to reproduce =
1. Compile gdkconfig.cpp: g++ -o gdktest gdkconfig.cpp `pkg-config --libs gtk+-2.0` `pkg-config --cflags gtk+-2.0`
2. Launch it from a terminal
3. Observe output from terminal
4. Click "OK" to launch a new window
5. Observe logs, you should see something like this:
popup window created gdkwindow -- 7063232
GDK_CONFIGURE : window -- 7063232, x -- 250, y -- 250, width -- 200, height -- 200
GDK_CONFIGURE : window -- 7063232, x -- 0, y -- 0, width -- 200, height -- 200
GDK_CONFIGURE : window -- 7063232, x -- 0, y -- 0, width -- 200, height -- 200
GDK_CONFIGURE : window -- 7063232, x -- 0, y -- 0, width -- 200, height -- 200
GDK_CONFIGURE : window -- 7063232, x -- 251, y -- 275, width -- 200, height -- 200
When running under Natty or Unity-2D, GDK_CONFIGURE is never set to 0,0.
= Original text =
when using unity 3d on ubuntu, after creating a top-level gtk widget, the window manager sends GDK_CONFIGURE with position as (0,0) although I have set the initial position to some different value.
This dose not happen on gnome/unity 2d environment. It will cause seriously issue when we rely on this event to locate our window.
Source code attached, you could compile it and launch it from terminal, the GDK_CONFIGURE event will be printed out. |
= SRU TESTCASE =
Old Behaviour:
1. Run testcase
2. Notice that it reports 2 sets of x and y values of 0,0
Fixed behaviour:
1. Run testacse
2. Notice that it reports 2 sets of x and y values which reflect the actual window position
= Problem =
After creating a top-level GTK widget, the window manager sends GDK_CONFIGURE with the position as (0,0) even though the initial position is already set to a different value.
= Environment =
* Ubuntu 11.10 (Oneiric) i386
* Unity - 4.22.0-0ubuntu3
= Impact =
This causes issues for applications that rely on this GDK_CONFIGURE to locate their app window.
= Steps to reproduce =
1. Compile gdkconfig.cpp: g++ -o gdktest gdkconfig.cpp `pkg-config --libs gtk+-2.0` `pkg-config --cflags gtk+-2.0`
2. Launch it from a terminal
3. Observe output from terminal
4. Click "OK" to launch a new window
5. Observe logs, you should see something like this:
popup window created gdkwindow -- 7063232
GDK_CONFIGURE : window -- 7063232, x -- 250, y -- 250, width -- 200, height -- 200
GDK_CONFIGURE : window -- 7063232, x -- 0, y -- 0, width -- 200, height -- 200
GDK_CONFIGURE : window -- 7063232, x -- 0, y -- 0, width -- 200, height -- 200
GDK_CONFIGURE : window -- 7063232, x -- 0, y -- 0, width -- 200, height -- 200
GDK_CONFIGURE : window -- 7063232, x -- 251, y -- 275, width -- 200, height -- 200
When running under Natty or Unity-2D, GDK_CONFIGURE is never set to 0,0.
= Original text =
when using unity 3d on ubuntu, after creating a top-level gtk widget, the window manager sends GDK_CONFIGURE with position as (0,0) although I have set the initial position to some different value.
This dose not happen on gnome/unity 2d environment. It will cause seriously issue when we rely on this event to locate our window.
Source code attached, you could compile it and launch it from terminal, the GDK_CONFIGURE event will be printed out. |
|
| 2011-12-13 11:00:35 |
Tom Ellis |
attachment added |
|
compiz_0.9.6+bzr20110929-0ubuntu6.1.debdiff https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/890947/+attachment/2631149/+files/compiz_0.9.6%2Bbzr20110929-0ubuntu6.1.debdiff |
|
| 2011-12-15 15:03:54 |
Sebastien Bacher |
nominated for series |
|
Ubuntu Oneiric |
|
| 2011-12-15 15:03:54 |
Sebastien Bacher |
bug task added |
|
compiz (Ubuntu Oneiric) |
|
| 2011-12-15 15:03:54 |
Sebastien Bacher |
bug task added |
|
unity (Ubuntu Oneiric) |
|
| 2011-12-15 18:23:24 |
Launchpad Janitor |
branch linked |
|
lp:~om26er/ubuntu/oneiric/compiz/compiz-sru |
|
| 2012-01-15 09:16:26 |
Omer Akram |
bug task deleted |
unity (Ubuntu) |
|
|
| 2012-01-15 09:16:33 |
Omer Akram |
bug task deleted |
unity (Ubuntu Oneiric) |
|
|
| 2012-01-15 09:16:41 |
Omer Akram |
bug task deleted |
unity |
|
|
| 2012-01-15 09:16:54 |
Omer Akram |
affects |
compiz |
compiz-core |
|
| 2012-01-18 05:45:11 |
Omer Akram |
compiz (Ubuntu): status |
In Progress |
Triaged |
|
| 2012-01-18 05:45:19 |
Omer Akram |
compiz (Ubuntu): status |
Triaged |
Fix Committed |
|
| 2012-01-18 05:45:21 |
Omer Akram |
compiz-core: status |
New |
Fix Committed |
|
| 2012-01-25 02:23:26 |
Daniel van Vugt |
compiz-core: milestone |
|
0.9.7 |
|
| 2012-01-30 02:09:10 |
Chris Halse Rogers |
compiz (Ubuntu Oneiric): status |
New |
Fix Committed |
|
| 2012-01-30 02:09:15 |
Chris Halse Rogers |
bug |
|
|
added subscriber SRU Verification |
| 2012-01-30 02:09:17 |
Chris Halse Rogers |
tags |
|
verification-needed |
|
| 2012-01-30 02:42:24 |
Launchpad Janitor |
branch linked |
|
lp:ubuntu/oneiric-proposed/compiz |
|
| 2012-01-30 17:46:04 |
Colan Schwartz |
bug |
|
|
added subscriber Colan Schwartz |
| 2012-02-06 06:38:11 |
Martin Pitt |
tags |
verification-needed |
verification-done |
|
| 2012-02-14 05:44:23 |
Daniel van Vugt |
compiz (Ubuntu): status |
Fix Committed |
Fix Released |
|
| 2012-02-14 06:19:09 |
Launchpad Janitor |
compiz (Ubuntu Oneiric): status |
Fix Committed |
Fix Released |
|
| 2012-02-16 06:48:23 |
Nobuto Murata |
bug |
|
|
added subscriber Nobuto MURATA |
| 2012-02-16 06:58:44 |
Nobuto Murata |
bug |
|
|
added subscriber Takenori MATSUMOTO |
| 2012-03-03 09:41:22 |
Daniel van Vugt |
compiz-core: status |
Fix Committed |
Fix Released |
|
| 2012-10-15 20:30:22 |
Chris J Arges |
bug |
|
|
added subscriber Sustaining Engineering |
| 2014-02-07 15:45:05 |
Curtis Hovey |
removed subscriber Registry Administrators |
|
|
|
