Activity log for bug #904040

Date Who What changed Old value New value Message
2011-12-14 01:18:01 Märt Põder bug added bug
2011-12-14 01:19:40 Märt Põder bug task added screenlets
2011-12-14 01:19:56 Märt Põder screenlets: status New Confirmed
2011-12-14 01:20:06 Märt Põder screenlets: importance Undecided High
2011-12-14 01:21:13 Märt Põder description Something during the startup of Unity messes up predefined positions of autostart applications on screen. Debugging the issue resulted that when "DEBUG 2011-12-14 01:51:42 glib <unknown>:0 Setting to primary screen rect: x=0 y=0 w=1280 h=1024" was displayed after the autostart application was started, then at least one of the predefined coordinates (x or y) of autostart application window was messed up (set to default value). The message displayed in ~/.xsession-errors is run from UnityScreen::Relayout in plugins/unityshell/src/unityshell.cpp and it seems that if I run my applications after that, there are no problems. However, this is not expected behaviour from Unity shell, it shouldn't matter when I start my applications, as long as I start them from Ubunty system menu in a normal way. Unity 2D, GNOME3 shell and GNOME3 fallback session are doing fine in this respect. Unity version: 4.24.0-0ubuntu2b1 Something during the startup of Unity messes up predefined positions of autostart applications on screen. Debugging the issue resulted that when "DEBUG 2011-12-14 01:51:42 glib <unknown>:0 Setting to primary screen rect: x=0 y=0 w=1280 h=1024" was displayed after the autostart application was started, then at least one of the predefined coordinates (x or y) of autostart application window was messed up (set to default value). The message displayed in ~/.xsession-errors is run from UnityScreen::Relayout in plugins/unityshell/src/unityshell.cpp and it seems that if I run my applications after that, there are no problems. However, this is not expected behaviour from Unity shell, it shouldn't matter when I start my applications, as long as I start them from Ubunty system menu in a normal way. Unity 2D, GNOME3 shell and GNOME3 fallback session are doing fine in this respect. Unity version: 4.24.0-0ubuntu2b1 See also: https://bugs.launchpad.net/screenlets/+bug/885322
2011-12-14 01:46:20 Märt Põder description Something during the startup of Unity messes up predefined positions of autostart applications on screen. Debugging the issue resulted that when "DEBUG 2011-12-14 01:51:42 glib <unknown>:0 Setting to primary screen rect: x=0 y=0 w=1280 h=1024" was displayed after the autostart application was started, then at least one of the predefined coordinates (x or y) of autostart application window was messed up (set to default value). The message displayed in ~/.xsession-errors is run from UnityScreen::Relayout in plugins/unityshell/src/unityshell.cpp and it seems that if I run my applications after that, there are no problems. However, this is not expected behaviour from Unity shell, it shouldn't matter when I start my applications, as long as I start them from Ubunty system menu in a normal way. Unity 2D, GNOME3 shell and GNOME3 fallback session are doing fine in this respect. Unity version: 4.24.0-0ubuntu2b1 See also: https://bugs.launchpad.net/screenlets/+bug/885322 Something during the startup of Unity messes up predefined positions of autostart applications. Debugging the issue resulted that when "DEBUG 2011-12-14 01:51:42 glib <unknown>:0 Setting to primary screen rect: x=0 y=0 w=1280 h=1024" was displayed after the autostart application was started/displayed, then at least one of the predefined coordinates (x or y) of autostart application window was messed up (set to default value). The message displayed in ~/.xsession-errors is defined in UnityScreen::Relayout in plugins/unityshell/src/unityshell.cpp and it seems that if I run my applications after that message is displayed during Unity startup, there are no problems. However, this is not expected behaviour from Unity shell, it shouldn't matter when exactly I start my applications, as long as I start them from Ubuntu system menu in a normal way. Unity 2D, GNOME3 shell and GNOME3 fallback session are doing fine in this respect. Unity version: 4.24.0-0ubuntu2b1 See also: https://bugs.launchpad.net/screenlets/+bug/885322
2011-12-14 23:41:03 Bilal Akhtar unity: status New Confirmed
2011-12-14 23:41:08 Bilal Akhtar bug task added unity (Ubuntu)
2011-12-14 23:55:13 Bilal Akhtar unity (Ubuntu): status New Confirmed
2012-07-24 08:26:27 Omer Akram unity: status Confirmed Incomplete
2012-07-24 08:26:30 Omer Akram unity (Ubuntu): status Confirmed Incomplete