[Dx-packages] [Bug 1456241] [NEW] AP failure: unity.tests.test_panel.PanelGrabAreaTests.test_lower_the_maximized_window_works
Public bug reported: Recently, an AP test has started failing consistently: unity.tests.test_panel.PanelGrabAreaTests.test_lower_the_maximized_window_works Need to investigate if a regression has been introduced or if the test needs to be updated to work with a new behavior. ** Affects: unity Importance: Medium Assignee: Christopher Townsend (townsend) Status: Confirmed ** Affects: unity (Ubuntu) Importance: Medium Assignee: Christopher Townsend (townsend) Status: Confirmed ** Also affects: unity (Ubuntu) Importance: Undecided Status: New ** Changed in: unity Status: New = Confirmed ** Changed in: unity (Ubuntu) Status: New = Confirmed ** Changed in: unity Importance: Undecided = Medium ** Changed in: unity (Ubuntu) Importance: Undecided = Medium ** Changed in: unity Assignee: (unassigned) = Christopher Townsend (townsend) ** Changed in: unity (Ubuntu) Assignee: (unassigned) = Christopher Townsend (townsend) ** Changed in: unity Milestone: None = 7.3.3 -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1456241 Title: AP failure: unity.tests.test_panel.PanelGrabAreaTests.test_lower_the_maximized_window_works Status in Unity: Confirmed Status in unity package in Ubuntu: Confirmed Bug description: Recently, an AP test has started failing consistently: unity.tests.test_panel.PanelGrabAreaTests.test_lower_the_maximized_window_works Need to investigate if a regression has been introduced or if the test needs to be updated to work with a new behavior. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1456241/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1456240] [NEW] AP failure: unity.tests.test_panel.PanelIndicatorEntryTests.test_menu_opens_closes_on_click
Public bug reported: Recently, an AP test has started failing consistently: unity.tests.test_panel.PanelIndicatorEntryTests.test_menu_opens_closes_on_click Need to investigate if a regression has been introduced or if the test needs to be updated to work with a new behavior. ** Affects: unity Importance: Medium Assignee: Christopher Townsend (townsend) Status: Confirmed ** Affects: unity (Ubuntu) Importance: Medium Assignee: Christopher Townsend (townsend) Status: Confirmed ** Also affects: unity Importance: Undecided Status: New ** Changed in: unity Status: New = Confirmed ** Changed in: unity (Ubuntu) Status: New = Confirmed ** Changed in: unity Importance: Undecided = Medium ** Changed in: unity (Ubuntu) Importance: Undecided = Medium ** Changed in: unity Assignee: (unassigned) = Christopher Townsend (townsend) ** Changed in: unity (Ubuntu) Assignee: (unassigned) = Christopher Townsend (townsend) ** Changed in: unity Milestone: None = 7.3.3 -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1456240 Title: AP failure: unity.tests.test_panel.PanelIndicatorEntryTests.test_menu_opens_closes_on_click Status in Unity: Confirmed Status in unity package in Ubuntu: Confirmed Bug description: Recently, an AP test has started failing consistently: unity.tests.test_panel.PanelIndicatorEntryTests.test_menu_opens_closes_on_click Need to investigate if a regression has been introduced or if the test needs to be updated to work with a new behavior. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1456240/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1390120] Re: Manually set time and date reverts to Automatically on restart (Ubuntu Phone)
** Also affects: systemd-shim (Ubuntu) Importance: Undecided Status: New ** Changed in: systemd-shim (Ubuntu) Status: New = Confirmed ** Changed in: ubuntu-system-settings (Ubuntu) Status: Confirmed = Invalid -- You received this bug notification because you are a member of DX Packages, which is subscribed to systemd-shim in Ubuntu. https://bugs.launchpad.net/bugs/1390120 Title: Manually set time and date reverts to Automatically on restart (Ubuntu Phone) Status in the base for Ubuntu mobile products: Confirmed Status in systemd package in Ubuntu: Invalid Status in systemd-shim package in Ubuntu: Confirmed Status in ubuntu-system-settings package in Ubuntu: Invalid Bug description: 1a - On OS build #6 (Channel: ubuntu-touch/ubuntu-rtm/14.09), I open Time Date settings and select Manually under Set the time and date: 2a - I set the time manually from Old_Time to New_Time and wait for New_Time to display in the Date Time Indicator at top-right 3a - Then restart Ubuntu Phone and Date Time Indicator shows New_Time for 10 seconds and then reverts to Old_Time 4a - Time Date settings agree with Old_Time and Automatically has been selected under Set the time and date: To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1390120/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1358340] Re: [Indicators] Complete greeter profiles
** Changed in: unity8 (Ubuntu) Assignee: Michael Terry (mterry) = (unassigned) -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-datetime in Ubuntu. Matching subscriptions: dx-packages, dx-packages, dx-packages https://bugs.launchpad.net/bugs/1358340 Title: [Indicators] Complete greeter profiles Status in The Date and Time Indicator: Invalid Status in The Messaging Menu: Fix Released Status in Transfer Indicator: Fix Released Status in Ubuntu UX bugs: Fix Released Status in The Unity 8 shell: Fix Released Status in gsettings-ubuntu-touch-schemas package in Ubuntu: Fix Released Status in indicator-datetime package in Ubuntu: Invalid Status in indicator-messages package in Ubuntu: Fix Released Status in indicator-sound package in Ubuntu: Fix Released Status in indicator-transfer package in Ubuntu: Fix Released Status in ubuntu-system-settings package in Ubuntu: Fix Released Status in unity8 package in Ubuntu: In Progress Status in unity8 package in Ubuntu RTM: New Bug description: A recent change in the interest of security removed access to the indicators when the phone is locked and the greeter is showing. This was an accentual change based on a misunderstanding There had been a plan to support media playback control via the sound indicator. Without this the user must unlock the phone in order to simply pause the music or change songs, etc. Desired resolution: - Revert the change that caused this issue - Add a switch to System Settings to enable security conscious user to switch off Launcher and Greeter access while the phone is locked. This setting should *always* be off by default. https://wiki.ubuntu.com/SecurityAndPrivacySettings#Locking To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-datetime/+bug/1358340/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1456245] [NEW] AP failure: unity.tests.test_quicklist.QuicklistActionTests.test_right_click_opens_quicklist_if_already_open
Public bug reported: Recently, an AP test has started failing consistently: unity.tests.test_quicklist.QuicklistActionTests.test_right_click_opens_quicklist_if_already_open Need to investigate if a regression has been introduced or if the test needs to be updated to work with a new behavior. ** Affects: unity Importance: Medium Assignee: Christopher Townsend (townsend) Status: Confirmed ** Affects: unity (Ubuntu) Importance: Medium Assignee: Christopher Townsend (townsend) Status: Confirmed ** Also affects: unity Importance: Undecided Status: New ** Changed in: unity Status: New = Confirmed ** Changed in: unity (Ubuntu) Status: New = Confirmed ** Changed in: unity Importance: Undecided = Medium ** Changed in: unity (Ubuntu) Importance: Undecided = Medium ** Changed in: unity Assignee: (unassigned) = Christopher Townsend (townsend) ** Changed in: unity (Ubuntu) Assignee: (unassigned) = Christopher Townsend (townsend) ** Changed in: unity Milestone: None = 7.3.3 -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1456245 Title: AP failure: unity.tests.test_quicklist.QuicklistActionTests.test_right_click_opens_quicklist_if_already_open Status in Unity: Confirmed Status in unity package in Ubuntu: Confirmed Bug description: Recently, an AP test has started failing consistently: unity.tests.test_quicklist.QuicklistActionTests.test_right_click_opens_quicklist_if_already_open Need to investigate if a regression has been introduced or if the test needs to be updated to work with a new behavior. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1456245/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1456240] Re: AP failure: unity.tests.test_panel.PanelIndicatorEntryTests.test_menu_opens_closes_on_click
** Changed in: unity Status: Confirmed = In Progress ** Changed in: unity (Ubuntu) Status: Confirmed = In Progress -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1456240 Title: AP failure: unity.tests.test_panel.PanelIndicatorEntryTests.test_menu_opens_closes_on_click Status in Unity: In Progress Status in unity package in Ubuntu: In Progress Bug description: Recently, an AP test has started failing consistently: unity.tests.test_panel.PanelIndicatorEntryTests.test_menu_opens_closes_on_click Need to investigate if a regression has been introduced or if the test needs to be updated to work with a new behavior. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1456240/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1444626] Re: When in Quicklist keynav, using left arrow to exit Quicklist should enter Launcher keynav
** Changed in: unity Status: In Progress = Fix Committed -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1444626 Title: When in Quicklist keynav, using left arrow to exit Quicklist should enter Launcher keynav Status in Unity: Fix Committed Status in Unity 7.2 series: Triaged Status in unity package in Ubuntu: Fix Released Bug description: When using the arrow keys to navigate a Quicklist and using the left arrow key to exit the Quicklist, Launcher keynav should activate and on the icon for which the Quicklist was active. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1444626/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1444113] Re: Opening BFB Quicklist using Launcher keynav doesn't work until moving mouse into the BFB icon
** Changed in: unity Status: In Progress = Fix Committed -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1444113 Title: Opening BFB Quicklist using Launcher keynav doesn't work until moving mouse into the BFB icon Status in Unity: Fix Committed Status in Unity 7.2 series: Triaged Status in unity package in Ubuntu: Fix Released Bug description: When using Launcher keynav to open the BFB Quicklist and selecting a scope to open does not open the Dash until you use the mouse right click Quicklist navigation. Once you use the mouse right click, then keynav works as expected. Steps to reproduce: 1. Start a fresh instance of Unity. 2. *Do not* move the mouse into the BFB, ie Home, icon. 3. Start Launcher keynav by pressing Alt-F1. 4. Arrow to the right to open the BFB Quicklist. 5. Select any Scope to open. Expected results: The selected Scope will open in the Dash. Actual results: The Dash does not open. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1444113/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1445082] Re: While in Launcher keynav, hitting Enter on an icon with multiple windows should open the application Spread
** Changed in: unity Status: In Progress = Fix Committed -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1445082 Title: While in Launcher keynav, hitting Enter on an icon with multiple windows should open the application Spread Status in Unity: Fix Committed Status in Unity 7.2 series: Triaged Status in unity package in Ubuntu: Fix Released Bug description: While in Launcher keynav mode, navigating to an icon that has multiple windows and hitting Enter should open that application's window Spread. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1445082/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1456126] Re: Alarm snooze countdown is not start from the time of tapping on Snooze button
** Project changed: ubuntu-clock-app = indicator-datetime ** Also affects: indicator-datetime (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-datetime in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1456126 Title: Alarm snooze countdown is not start from the time of tapping on Snooze button Status in The Date and Time Indicator: New Status in indicator-datetime package in Ubuntu: New Bug description: $ system-image-cli -i current build number: 42 device name: arale channel: ubuntu-touch/tangxi/devel-proposed last update: 2015-05-15 04:19:20 version version: 42 version device: 1e1b1cebe8900f5b62bed050a5c23a7765e62600d394cba528169d257e6ab36c version custom: 8274419d06b4da1424e7f7339ff2f8276b38951951d8900e148a4fdfce8fba0d Steps to reproduce: 1.Launch Clock app and set Snooze time for 5 minnutes 2.Create a alarm and wait for it to trigger 3.Waiting for more than one minutes, then tap on Snooze 4.Waiting for the alarm rings again 5.Check the real time interval after tap on Snooze Expected results: The time interval is 5 minutes after the time of tapping on Snooze Actual results: The alarm snooze countdown is start from the time of alarm rings To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-datetime/+bug/1456126/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1446165] Re: the skydome effect of the cube plugin doesn't work with unity 7
** Changed in: unity Status: New = Fix Committed ** Changed in: unity Milestone: None = 7.3.3 ** Changed in: unity (Ubuntu) Importance: Undecided = High ** Changed in: unity (Ubuntu) Assignee: (unassigned) = Eleni Maria Stea (hikiko) -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1446165 Title: the skydome effect of the cube plugin doesn't work with unity 7 Status in Compiz: New Status in Unity: Fix Committed Status in unity package in Ubuntu: Fix Released Bug description: when running compiz + unity 7 the skydome doesn't appear correctly (looks like it has a weird transformation) screenshot: https://i.imgur.com/nnj4y1f.jpg To manage notifications about this bug go to: https://bugs.launchpad.net/compiz/+bug/1446165/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1444643] Re: While in Launcher keynav, icon Spread does not work as expected
** Changed in: unity Status: In Progress = Fix Committed -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1444643 Title: While in Launcher keynav, icon Spread does not work as expected Status in Unity: Fix Committed Status in Unity 7.2 series: Triaged Status in unity package in Ubuntu: Fix Released Bug description: While in Launcher keynav mode, if an icon has multiple windows open and one of the windows was last focused, clicking on the icon does not bring up the application Spread, it only focuses the window. The expected behavior would be to open the application Spread if it was the last focused window. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1444643/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1131385] Re: Always on top prevents application spread from working
** Changed in: unity Status: In Progress = Fix Committed ** Also affects: unity/7.2 Importance: Undecided Status: New ** Changed in: unity/7.2 Status: New = Triaged ** Changed in: unity/7.2 Importance: Undecided = Low ** Changed in: unity/7.2 Assignee: (unassigned) = Christopher Townsend (townsend) ** Changed in: unity/7.2 Milestone: None = 7.2.6 -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1131385 Title: Always on top prevents application spread from working Status in Ayatana Design: Invalid Status in Compiz: Invalid Status in Unity: Fix Committed Status in Unity 7.2 series: Triaged Status in unity package in Ubuntu: Fix Released Bug description: Consider you have many windows of the same type open. One method of switching between them is clicking the launcher icon which reveals the application spread. Now you can choose between the windows. This is how it should be. However, the design idea was, if the windows are marked Always on Top there is no need for an application spread, as they are always on top. This is a bug and needs to be changed, because it does not consider minimized windows and therefore prevents switching to those windows. If you have windows of the same application open, some of them minimized and ALL non-minimized windows are marked as Always on top, the application spread does not work anymore, clicking the launcher does nothing. Whether the minimized windows are marked always on top or not does not matter. So the simplest way to reproduce this bug would be: 1.) Open two windows of the same application. 2.) Minimize one and mark the other (non-minimized) as Always on top. 3.) Try to switch to the minimized window using application spread To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/1131385/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1446634] Re: Active windows loses focus after returning from Dash if another Always on top window is present
** Changed in: unity Status: In Progress = Fix Committed -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1446634 Title: Active windows loses focus after returning from Dash if another Always on top window is present Status in Unity: Fix Committed Status in Unity 7.2 series: Triaged Status in unity package in Ubuntu: Fix Released Bug description: Active window looses focus after returning from Dash if Always on top window like VLC is already running. The focus is given to VLC instead of the window on which HUD was invoke. This is very similar to bug #1366583. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1446634/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1052024] Re: BFB Quicklist fails to work when mouse is used to right click and choose an option when Launcher is keynav mode
** Changed in: unity Status: In Progress = Fix Committed -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1052024 Title: BFB Quicklist fails to work when mouse is used to right click and choose an option when Launcher is keynav mode Status in Unity: Fix Committed Status in Unity 7.2 series: Triaged Status in unity package in Ubuntu: Fix Released Bug description: Ubuntu 12.10 Quantal with ppa:unity-team/staging Issue:- Right click using mouse on dash icon in keynav mode fails to exit keynav mode and does not activate the option chosen by the user. Only if the user clicks anywhere on the screen, the chosen option gets activated. For example:- In keynav mode, right click on dash and click on Applications. This will not exit keynav mode and will not open applications lens. Only when the user click somewhere on the screen, keynav mode exits and applications lens is opened. Action: - Press Alt+F1 to enter keynav mode - now right click on dash icon, click on any options in the quicklist ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: unity 6.4.0+bzr2684ubuntu0+778 [origin: LP-PPA-unity-team-staging] ProcVersionSignature: Ubuntu 3.5.0-14.19-generic 3.5.3 Uname: Linux 3.5.0-14-generic i686 ApportVersion: 2.5.1-0ubuntu7 Architecture: i386 CompizPlugins: [core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell] CrashDB: unity Date: Mon Sep 17 16:27:38 2012 InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Alpha i386 (20120713.1) ProcEnviron: LANGUAGE=en_GB:en TERM=xterm PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1052024/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1366583] Re: Active windows loses focus after returning from HUD if another Always on top window is present
** Changed in: unity Status: In Progress = Fix Committed -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1366583 Title: Active windows loses focus after returning from HUD if another Always on top window is present Status in Unity: Fix Committed Status in Unity 7.2 series: Triaged Status in unity package in Ubuntu: Fix Released Bug description: Active window looses focus after returning from HUD if Always on top window like VLC is already running. The focus is given to VLC instead of the window on which HUD was invoke. How to reproduce? 1. Open vlc and set it always on top 2. Open nautilus, try to rename a file using hud 3. As soon as rename option is pressed on hud, nautilus looses its focus and the focus is given to VLC. 4. To rename I have to re-select nautilus ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.2.2+14.04.20140714-0ubuntu1.1 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.3 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity CurrentDmesg: Error: command ['sh', '-c', 'dmesg | comm -13 --nocheck-order /var/log/dmesg -'] failed with exit code 1: comm: /var/log/dmesg: Permission denied Date: Sun Sep 7 23:05:07 2014 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu DkmsStatus: i915-3.15-3.13, 0.01, 3.13.0-19-generic, x86_64: installed i915-3.15-3.13, 0.01, 3.13.0-24-generic, x86_64: installed GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Samsung Electronics Co Ltd Device [144d:c652] InstallationDate: Installed on 2014-04-13 (146 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Beta amd64 (20140326) Lsusb: Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 003: ID 0ac8:c349 Z-Star Microelectronics Corp. Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: SAMSUNG ELECTRONICS CO., LTD. 300E4C/300E5C/300E7C ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-24-generic root=UUID=4a883016-3392-4731-824d-ac87981ccaef ro quiet splash vt.handoff=7 SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/07/2012 dmi.bios.vendor: Phoenix Technologies Ltd. dmi.bios.version: P03RAC dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: NP300E5X-A04IN dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.board.version: FAB1 dmi.chassis.asset.tag: Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnPhoenixTechnologiesLtd.:bvrP03RAC:bd05/07/2012:svnSAMSUNGELECTRONICSCO.,LTD.:pn300E4C/300E5C/300E7C:pvr0.1:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNP300E5X-A04IN:rvrFAB1:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1: dmi.product.name: 300E4C/300E5C/300E7C dmi.product.version: 0.1 dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD. version.compiz: compiz 1:0.9.11.2+14.04.20140714-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.54-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.2.2-0intel1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.2.2-0intel1 version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.911-0intel1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 xserver.bootTime: Sun Sep 7 22:23:30 2014 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id5539 vendor CMO xserver.version: 2:1.15.1-0ubuntu2 To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1366583/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1412937] Re: Config option to set UNITY_LOW_GFX_MODE=1
** Changed in: unity Status: In Progress = Fix Committed -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1412937 Title: Config option to set UNITY_LOW_GFX_MODE=1 Status in OEM Priority Project: New Status in OEM Priority Project trusty series: New Status in Unity: Fix Committed Status in Unity 7.2 series: Triaged Status in unity package in Ubuntu: Fix Released Bug description: Right now the procedure to turn on low_gfx_mode is https://bugs.launchpad.net/compiz/+bug/1293384/comments/15 sudo -H gedit /usr/share/gnome-session/sessions/ubuntu.session Remove compiz from the RequiredComponents list sudo -H gedit /usr/share/upstart/sessions/unity7.conf: Add these lines after export COMPIZ_CONFIG_PROFILE: env UNITY_LOW_GFX_MODE=1 export UNITY_LOW_GFX_MODE We should add a config option (preferably system wide) to tell Compiz/Unity to go to the LOW_GFX mode regardless of what the hardware says it can do. This will make it easier to setup items like terminal services using Unity. This procedure has helped in at least one case for me, (a machine used by several users remotely using Unity). I can imagine it would also help in multiseat scenarios, etc. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1412937/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1300722] Re: hud-service is eating up 100% of one of my CPUs in a poll loop
I'm also experiencing this bug. It started when I was using Chromium. Firefox and gimp was close. No torrent -- You received this bug notification because you are a member of DX Packages, which is subscribed to hud in Ubuntu. https://bugs.launchpad.net/bugs/1300722 Title: hud-service is eating up 100% of one of my CPUs in a poll loop Status in Unity HUD: Confirmed Status in hud package in Ubuntu: In Progress Bug description: hud-service is polling like crazy: Context Switches: PID ProcessVoluntary Involuntary Total Ctxt Sw/Sec Ctxt Sw/Sec Ctxt Sw/Sec 2295 hud-service 46084.6342.94 46127.58 (very high) 2325 hud-service 0.09 0.00 0.09 (very low) 2329 hud-service 0.07 0.00 0.07 (very low) 2340 hud-service 0.05 0.00 0.05 (very low) Total 46084.8442.94 46127.78 File I/O operations: No file I/O operations detected. System calls traced: PID Process Syscall CountRate/Sec 2295 hud-service poll 83 23124.8503 2295 hud-service write10 0.2313 2295 hud-service sendmsg 4 0.0925 2325 hud-service restart_syscall 1 0.0231 2329 hud-service restart_syscall 1 0.0231 2340 hud-service restart_syscall 1 0.0231 Total 100 23125.2435 (gdb) where #0 0x7fda8121cfbd in poll () at ../sysdeps/unix/syscall-template.S:81 #1 0x7fda7f1bb4b8 in ?? () from /lib/x86_64-linux-gnu/libdbus-1.so.3 #2 0x7fda7f1ba3ff in ?? () from /lib/x86_64-linux-gnu/libdbus-1.so.3 #3 0x7fda7f1a49dc in ?? () from /lib/x86_64-linux-gnu/libdbus-1.so.3 #4 0x7fda7f1a5464 in ?? () from /lib/x86_64-linux-gnu/libdbus-1.so.3 #5 0x7fda82ce9e65 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5 #6 0x7fda82d2fc64 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5 #7 0x7fda82d30582 in QDBusPendingCallWatcher::waitForFinished() () from /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5 #8 0x7fda83eb940b in DBusMenuImporter::slotMenuAboutToShow() () from /usr/lib/x86_64-linux-gnu/libdbusmenu-qt5.so.2 #9 0x7fda8435d2a6 in QMetaObject::activate(QObject*, int, int, void**) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #10 0x0045ab3f in hud::service::DBusMenuCollector::openMenu(QMenu*, unsigned int) () #11 0x0045abd8 in hud::service::DBusMenuCollector::openMenu(QMenu*, unsigned int) () #12 0x0045abd8 in hud::service::DBusMenuCollector::openMenu(QMenu*, unsigned int) () #13 0x0045abd8 in hud::service::DBusMenuCollector::openMenu(QMenu*, unsigned int) () #14 0x0045abd8 in hud::service::DBusMenuCollector::openMenu(QMenu*, unsigned int) () #15 0x0045abd8 in hud::service::DBusMenuCollector::openMenu(QMenu*, unsigned int) () #16 0x0045ae8d in hud::service::DBusMenuCollector::activate() () #17 0x00441e43 in hud::service::WindowImpl::activate() () #18 0x00439f6a in hud::service::QueryImpl::updateToken(QSharedPointerhud::service::Window) () #19 0x0043a672 in hud::service::QueryImpl::refresh() () #20 0x0044b115 in ?? () #21 0x7fda8435d2a6 in QMetaObject::activate(QObject*, int, int, void**) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #22 0x0045662a in hud::service::ApplicationListImpl::FocusedWindowChanged(unsigned int, QString const, unsigned int) () #23 0x7fda8435d2a6 in QMetaObject::activate(QObject*, int, int, void**) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #24 0x00467361 in ComCanonicalUnityWindowStackInterface::FocusedWindowChanged(unsigned int, QString const, unsigned int) () #25 0x004678bd in ?? () #26 0x00467c63 in ComCanonicalUnityWindowStackInterface::qt_metacall(QMetaObject::Call, int, void**) () #27 0x7fda82cf180f in ?? () from /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5 #28 0x7fda8435e22e in QObject::event(QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #29 0x7fda823d5c2c in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #30 0x7fda823dadf6 in QApplication::notify(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #31 0x7fda84335c2d in QCoreApplication::notifyInternal(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #32 0x7fda84337e07 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #33 0x7fda84382cd3 in ?? () from
[Dx-packages] [Bug 1052024] Re: BFB Quicklist fails to work when mouse is used to right click and choose an option when Launcher is keynav mode
This bug was fixed in the package unity - 7.3.2+15.10.20150512-0ubuntu1 --- unity (7.3.2+15.10.20150512-0ubuntu1) wily; urgency=medium [ Chris Townsend ] * Add new signal to tell the Launcher to terminate keynav mode and use that signal when a BFB quicklist item is chosen. (LP: #1052024, #1444643) * Add option to enable and disable Unity low graphics mode on the fly in ccsm or via gsettings. (LP: #1412937) * Remove code that is no longer needed and broke opening application spread while in Launcher keynav mode. (LP: #1445082) * Save the active window when showing the Dash so the correct window is focused when hiding the Dash. Fixes issue when Always on Top windows are present. (LP: #1446634) * Save the active window when showing the Hud so the correct window is focused when hiding the Hud. Fixes issue when Always on Top windows are present. (LP: #1366583) * Send signal to ensure the Dash will show when entering keynav mode since the first icon always highlighted is the BFB. (LP: #1444113) * When looking for the top-most valid window in a VP, also check if the window is focused if the window is set to Always on Top. This allows Launcher icon spread to work properly when a window is minimized an Always on Top exists in the group. (LP: #1131385) * When using the left arrow to exit a Quicklist, Launcher keynav is implied and should be active regardless of how the Quicklist was opened. (LP: #1444626) [ Eleni Maria Stea ] * The skydome rendering of the cube plugin was wrong with unity because transformation matrices set by the unityshell plugin were left in the opengl matrix stacks affecting other compiz plugins. Saving the compiz state at the beginning of the unityshell plugin rendering functions and restoring it at the end of them fixes the problem. (LP: #1446165) -- CI Train Bot ci-train-...@canonical.com Tue, 12 May 2015 13:10:15 + ** Changed in: unity (Ubuntu) Status: In Progress = Fix Released -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1052024 Title: BFB Quicklist fails to work when mouse is used to right click and choose an option when Launcher is keynav mode Status in Unity: In Progress Status in Unity 7.2 series: Triaged Status in unity package in Ubuntu: Fix Released Bug description: Ubuntu 12.10 Quantal with ppa:unity-team/staging Issue:- Right click using mouse on dash icon in keynav mode fails to exit keynav mode and does not activate the option chosen by the user. Only if the user clicks anywhere on the screen, the chosen option gets activated. For example:- In keynav mode, right click on dash and click on Applications. This will not exit keynav mode and will not open applications lens. Only when the user click somewhere on the screen, keynav mode exits and applications lens is opened. Action: - Press Alt+F1 to enter keynav mode - now right click on dash icon, click on any options in the quicklist ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: unity 6.4.0+bzr2684ubuntu0+778 [origin: LP-PPA-unity-team-staging] ProcVersionSignature: Ubuntu 3.5.0-14.19-generic 3.5.3 Uname: Linux 3.5.0-14-generic i686 ApportVersion: 2.5.1-0ubuntu7 Architecture: i386 CompizPlugins: [core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell] CrashDB: unity Date: Mon Sep 17 16:27:38 2012 InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Alpha i386 (20120713.1) ProcEnviron: LANGUAGE=en_GB:en TERM=xterm PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1052024/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1131385] Re: Always on top prevents application spread from working
This bug was fixed in the package unity - 7.3.2+15.10.20150512-0ubuntu1 --- unity (7.3.2+15.10.20150512-0ubuntu1) wily; urgency=medium [ Chris Townsend ] * Add new signal to tell the Launcher to terminate keynav mode and use that signal when a BFB quicklist item is chosen. (LP: #1052024, #1444643) * Add option to enable and disable Unity low graphics mode on the fly in ccsm or via gsettings. (LP: #1412937) * Remove code that is no longer needed and broke opening application spread while in Launcher keynav mode. (LP: #1445082) * Save the active window when showing the Dash so the correct window is focused when hiding the Dash. Fixes issue when Always on Top windows are present. (LP: #1446634) * Save the active window when showing the Hud so the correct window is focused when hiding the Hud. Fixes issue when Always on Top windows are present. (LP: #1366583) * Send signal to ensure the Dash will show when entering keynav mode since the first icon always highlighted is the BFB. (LP: #1444113) * When looking for the top-most valid window in a VP, also check if the window is focused if the window is set to Always on Top. This allows Launcher icon spread to work properly when a window is minimized an Always on Top exists in the group. (LP: #1131385) * When using the left arrow to exit a Quicklist, Launcher keynav is implied and should be active regardless of how the Quicklist was opened. (LP: #1444626) [ Eleni Maria Stea ] * The skydome rendering of the cube plugin was wrong with unity because transformation matrices set by the unityshell plugin were left in the opengl matrix stacks affecting other compiz plugins. Saving the compiz state at the beginning of the unityshell plugin rendering functions and restoring it at the end of them fixes the problem. (LP: #1446165) -- CI Train Bot ci-train-...@canonical.com Tue, 12 May 2015 13:10:15 + ** Changed in: unity (Ubuntu) Status: In Progress = Fix Released -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1131385 Title: Always on top prevents application spread from working Status in Ayatana Design: Invalid Status in Compiz: Invalid Status in Unity: In Progress Status in unity package in Ubuntu: Fix Released Bug description: Consider you have many windows of the same type open. One method of switching between them is clicking the launcher icon which reveals the application spread. Now you can choose between the windows. This is how it should be. However, the design idea was, if the windows are marked Always on Top there is no need for an application spread, as they are always on top. This is a bug and needs to be changed, because it does not consider minimized windows and therefore prevents switching to those windows. If you have windows of the same application open, some of them minimized and ALL non-minimized windows are marked as Always on top, the application spread does not work anymore, clicking the launcher does nothing. Whether the minimized windows are marked always on top or not does not matter. So the simplest way to reproduce this bug would be: 1.) Open two windows of the same application. 2.) Minimize one and mark the other (non-minimized) as Always on top. 3.) Try to switch to the minimized window using application spread To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/1131385/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1444113] Re: Opening BFB Quicklist using Launcher keynav doesn't work until moving mouse into the BFB icon
This bug was fixed in the package unity - 7.3.2+15.10.20150512-0ubuntu1 --- unity (7.3.2+15.10.20150512-0ubuntu1) wily; urgency=medium [ Chris Townsend ] * Add new signal to tell the Launcher to terminate keynav mode and use that signal when a BFB quicklist item is chosen. (LP: #1052024, #1444643) * Add option to enable and disable Unity low graphics mode on the fly in ccsm or via gsettings. (LP: #1412937) * Remove code that is no longer needed and broke opening application spread while in Launcher keynav mode. (LP: #1445082) * Save the active window when showing the Dash so the correct window is focused when hiding the Dash. Fixes issue when Always on Top windows are present. (LP: #1446634) * Save the active window when showing the Hud so the correct window is focused when hiding the Hud. Fixes issue when Always on Top windows are present. (LP: #1366583) * Send signal to ensure the Dash will show when entering keynav mode since the first icon always highlighted is the BFB. (LP: #1444113) * When looking for the top-most valid window in a VP, also check if the window is focused if the window is set to Always on Top. This allows Launcher icon spread to work properly when a window is minimized an Always on Top exists in the group. (LP: #1131385) * When using the left arrow to exit a Quicklist, Launcher keynav is implied and should be active regardless of how the Quicklist was opened. (LP: #1444626) [ Eleni Maria Stea ] * The skydome rendering of the cube plugin was wrong with unity because transformation matrices set by the unityshell plugin were left in the opengl matrix stacks affecting other compiz plugins. Saving the compiz state at the beginning of the unityshell plugin rendering functions and restoring it at the end of them fixes the problem. (LP: #1446165) -- CI Train Bot ci-train-...@canonical.com Tue, 12 May 2015 13:10:15 + ** Changed in: unity (Ubuntu) Status: In Progress = Fix Released -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1444113 Title: Opening BFB Quicklist using Launcher keynav doesn't work until moving mouse into the BFB icon Status in Unity: In Progress Status in Unity 7.2 series: Triaged Status in unity package in Ubuntu: Fix Released Bug description: When using Launcher keynav to open the BFB Quicklist and selecting a scope to open does not open the Dash until you use the mouse right click Quicklist navigation. Once you use the mouse right click, then keynav works as expected. Steps to reproduce: 1. Start a fresh instance of Unity. 2. *Do not* move the mouse into the BFB, ie Home, icon. 3. Start Launcher keynav by pressing Alt-F1. 4. Arrow to the right to open the BFB Quicklist. 5. Select any Scope to open. Expected results: The selected Scope will open in the Dash. Actual results: The Dash does not open. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1444113/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1366583] Re: Active windows loses focus after returning from HUD if another Always on top window is present
This bug was fixed in the package unity - 7.3.2+15.10.20150512-0ubuntu1 --- unity (7.3.2+15.10.20150512-0ubuntu1) wily; urgency=medium [ Chris Townsend ] * Add new signal to tell the Launcher to terminate keynav mode and use that signal when a BFB quicklist item is chosen. (LP: #1052024, #1444643) * Add option to enable and disable Unity low graphics mode on the fly in ccsm or via gsettings. (LP: #1412937) * Remove code that is no longer needed and broke opening application spread while in Launcher keynav mode. (LP: #1445082) * Save the active window when showing the Dash so the correct window is focused when hiding the Dash. Fixes issue when Always on Top windows are present. (LP: #1446634) * Save the active window when showing the Hud so the correct window is focused when hiding the Hud. Fixes issue when Always on Top windows are present. (LP: #1366583) * Send signal to ensure the Dash will show when entering keynav mode since the first icon always highlighted is the BFB. (LP: #1444113) * When looking for the top-most valid window in a VP, also check if the window is focused if the window is set to Always on Top. This allows Launcher icon spread to work properly when a window is minimized an Always on Top exists in the group. (LP: #1131385) * When using the left arrow to exit a Quicklist, Launcher keynav is implied and should be active regardless of how the Quicklist was opened. (LP: #1444626) [ Eleni Maria Stea ] * The skydome rendering of the cube plugin was wrong with unity because transformation matrices set by the unityshell plugin were left in the opengl matrix stacks affecting other compiz plugins. Saving the compiz state at the beginning of the unityshell plugin rendering functions and restoring it at the end of them fixes the problem. (LP: #1446165) -- CI Train Bot ci-train-...@canonical.com Tue, 12 May 2015 13:10:15 + ** Changed in: unity (Ubuntu) Status: In Progress = Fix Released -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1366583 Title: Active windows loses focus after returning from HUD if another Always on top window is present Status in Unity: In Progress Status in Unity 7.2 series: Triaged Status in unity package in Ubuntu: Fix Released Bug description: Active window looses focus after returning from HUD if Always on top window like VLC is already running. The focus is given to VLC instead of the window on which HUD was invoke. How to reproduce? 1. Open vlc and set it always on top 2. Open nautilus, try to rename a file using hud 3. As soon as rename option is pressed on hud, nautilus looses its focus and the focus is given to VLC. 4. To rename I have to re-select nautilus ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.2.2+14.04.20140714-0ubuntu1.1 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.3 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity CurrentDmesg: Error: command ['sh', '-c', 'dmesg | comm -13 --nocheck-order /var/log/dmesg -'] failed with exit code 1: comm: /var/log/dmesg: Permission denied Date: Sun Sep 7 23:05:07 2014 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu DkmsStatus: i915-3.15-3.13, 0.01, 3.13.0-19-generic, x86_64: installed i915-3.15-3.13, 0.01, 3.13.0-24-generic, x86_64: installed GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Samsung Electronics Co Ltd Device [144d:c652] InstallationDate: Installed on 2014-04-13 (146 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Beta amd64 (20140326) Lsusb: Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 003: ID 0ac8:c349 Z-Star Microelectronics Corp. Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: SAMSUNG ELECTRONICS CO., LTD. 300E4C/300E5C/300E7C ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-24-generic root=UUID=4a883016-3392-4731-824d-ac87981ccaef ro quiet splash vt.handoff=7 SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/07/2012 dmi.bios.vendor: Phoenix Technologies Ltd. dmi.bios.version: P03RAC
[Dx-packages] [Bug 1412937] Re: Config option to set UNITY_LOW_GFX_MODE=1
This bug was fixed in the package unity - 7.3.2+15.10.20150512-0ubuntu1 --- unity (7.3.2+15.10.20150512-0ubuntu1) wily; urgency=medium [ Chris Townsend ] * Add new signal to tell the Launcher to terminate keynav mode and use that signal when a BFB quicklist item is chosen. (LP: #1052024, #1444643) * Add option to enable and disable Unity low graphics mode on the fly in ccsm or via gsettings. (LP: #1412937) * Remove code that is no longer needed and broke opening application spread while in Launcher keynav mode. (LP: #1445082) * Save the active window when showing the Dash so the correct window is focused when hiding the Dash. Fixes issue when Always on Top windows are present. (LP: #1446634) * Save the active window when showing the Hud so the correct window is focused when hiding the Hud. Fixes issue when Always on Top windows are present. (LP: #1366583) * Send signal to ensure the Dash will show when entering keynav mode since the first icon always highlighted is the BFB. (LP: #1444113) * When looking for the top-most valid window in a VP, also check if the window is focused if the window is set to Always on Top. This allows Launcher icon spread to work properly when a window is minimized an Always on Top exists in the group. (LP: #1131385) * When using the left arrow to exit a Quicklist, Launcher keynav is implied and should be active regardless of how the Quicklist was opened. (LP: #1444626) [ Eleni Maria Stea ] * The skydome rendering of the cube plugin was wrong with unity because transformation matrices set by the unityshell plugin were left in the opengl matrix stacks affecting other compiz plugins. Saving the compiz state at the beginning of the unityshell plugin rendering functions and restoring it at the end of them fixes the problem. (LP: #1446165) -- CI Train Bot ci-train-...@canonical.com Tue, 12 May 2015 13:10:15 + ** Changed in: unity (Ubuntu) Status: In Progress = Fix Released -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1412937 Title: Config option to set UNITY_LOW_GFX_MODE=1 Status in OEM Priority Project: New Status in OEM Priority Project trusty series: New Status in Unity: In Progress Status in Unity 7.2 series: Triaged Status in unity package in Ubuntu: Fix Released Bug description: Right now the procedure to turn on low_gfx_mode is https://bugs.launchpad.net/compiz/+bug/1293384/comments/15 sudo -H gedit /usr/share/gnome-session/sessions/ubuntu.session Remove compiz from the RequiredComponents list sudo -H gedit /usr/share/upstart/sessions/unity7.conf: Add these lines after export COMPIZ_CONFIG_PROFILE: env UNITY_LOW_GFX_MODE=1 export UNITY_LOW_GFX_MODE We should add a config option (preferably system wide) to tell Compiz/Unity to go to the LOW_GFX mode regardless of what the hardware says it can do. This will make it easier to setup items like terminal services using Unity. This procedure has helped in at least one case for me, (a machine used by several users remotely using Unity). I can imagine it would also help in multiseat scenarios, etc. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1412937/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1445082] Re: While in Launcher keynav, hitting Enter on an icon with multiple windows should open the application Spread
This bug was fixed in the package unity - 7.3.2+15.10.20150512-0ubuntu1 --- unity (7.3.2+15.10.20150512-0ubuntu1) wily; urgency=medium [ Chris Townsend ] * Add new signal to tell the Launcher to terminate keynav mode and use that signal when a BFB quicklist item is chosen. (LP: #1052024, #1444643) * Add option to enable and disable Unity low graphics mode on the fly in ccsm or via gsettings. (LP: #1412937) * Remove code that is no longer needed and broke opening application spread while in Launcher keynav mode. (LP: #1445082) * Save the active window when showing the Dash so the correct window is focused when hiding the Dash. Fixes issue when Always on Top windows are present. (LP: #1446634) * Save the active window when showing the Hud so the correct window is focused when hiding the Hud. Fixes issue when Always on Top windows are present. (LP: #1366583) * Send signal to ensure the Dash will show when entering keynav mode since the first icon always highlighted is the BFB. (LP: #1444113) * When looking for the top-most valid window in a VP, also check if the window is focused if the window is set to Always on Top. This allows Launcher icon spread to work properly when a window is minimized an Always on Top exists in the group. (LP: #1131385) * When using the left arrow to exit a Quicklist, Launcher keynav is implied and should be active regardless of how the Quicklist was opened. (LP: #1444626) [ Eleni Maria Stea ] * The skydome rendering of the cube plugin was wrong with unity because transformation matrices set by the unityshell plugin were left in the opengl matrix stacks affecting other compiz plugins. Saving the compiz state at the beginning of the unityshell plugin rendering functions and restoring it at the end of them fixes the problem. (LP: #1446165) -- CI Train Bot ci-train-...@canonical.com Tue, 12 May 2015 13:10:15 + ** Changed in: unity (Ubuntu) Status: In Progress = Fix Released -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1445082 Title: While in Launcher keynav, hitting Enter on an icon with multiple windows should open the application Spread Status in Unity: In Progress Status in Unity 7.2 series: Triaged Status in unity package in Ubuntu: Fix Released Bug description: While in Launcher keynav mode, navigating to an icon that has multiple windows and hitting Enter should open that application's window Spread. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1445082/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1444643] Re: While in Launcher keynav, icon Spread does not work as expected
This bug was fixed in the package unity - 7.3.2+15.10.20150512-0ubuntu1 --- unity (7.3.2+15.10.20150512-0ubuntu1) wily; urgency=medium [ Chris Townsend ] * Add new signal to tell the Launcher to terminate keynav mode and use that signal when a BFB quicklist item is chosen. (LP: #1052024, #1444643) * Add option to enable and disable Unity low graphics mode on the fly in ccsm or via gsettings. (LP: #1412937) * Remove code that is no longer needed and broke opening application spread while in Launcher keynav mode. (LP: #1445082) * Save the active window when showing the Dash so the correct window is focused when hiding the Dash. Fixes issue when Always on Top windows are present. (LP: #1446634) * Save the active window when showing the Hud so the correct window is focused when hiding the Hud. Fixes issue when Always on Top windows are present. (LP: #1366583) * Send signal to ensure the Dash will show when entering keynav mode since the first icon always highlighted is the BFB. (LP: #1444113) * When looking for the top-most valid window in a VP, also check if the window is focused if the window is set to Always on Top. This allows Launcher icon spread to work properly when a window is minimized an Always on Top exists in the group. (LP: #1131385) * When using the left arrow to exit a Quicklist, Launcher keynav is implied and should be active regardless of how the Quicklist was opened. (LP: #1444626) [ Eleni Maria Stea ] * The skydome rendering of the cube plugin was wrong with unity because transformation matrices set by the unityshell plugin were left in the opengl matrix stacks affecting other compiz plugins. Saving the compiz state at the beginning of the unityshell plugin rendering functions and restoring it at the end of them fixes the problem. (LP: #1446165) -- CI Train Bot ci-train-...@canonical.com Tue, 12 May 2015 13:10:15 + ** Changed in: unity (Ubuntu) Status: In Progress = Fix Released -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1444643 Title: While in Launcher keynav, icon Spread does not work as expected Status in Unity: In Progress Status in Unity 7.2 series: Triaged Status in unity package in Ubuntu: Fix Released Bug description: While in Launcher keynav mode, if an icon has multiple windows open and one of the windows was last focused, clicking on the icon does not bring up the application Spread, it only focuses the window. The expected behavior would be to open the application Spread if it was the last focused window. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1444643/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1444626] Re: When in Quicklist keynav, using left arrow to exit Quicklist should enter Launcher keynav
This bug was fixed in the package unity - 7.3.2+15.10.20150512-0ubuntu1 --- unity (7.3.2+15.10.20150512-0ubuntu1) wily; urgency=medium [ Chris Townsend ] * Add new signal to tell the Launcher to terminate keynav mode and use that signal when a BFB quicklist item is chosen. (LP: #1052024, #1444643) * Add option to enable and disable Unity low graphics mode on the fly in ccsm or via gsettings. (LP: #1412937) * Remove code that is no longer needed and broke opening application spread while in Launcher keynav mode. (LP: #1445082) * Save the active window when showing the Dash so the correct window is focused when hiding the Dash. Fixes issue when Always on Top windows are present. (LP: #1446634) * Save the active window when showing the Hud so the correct window is focused when hiding the Hud. Fixes issue when Always on Top windows are present. (LP: #1366583) * Send signal to ensure the Dash will show when entering keynav mode since the first icon always highlighted is the BFB. (LP: #1444113) * When looking for the top-most valid window in a VP, also check if the window is focused if the window is set to Always on Top. This allows Launcher icon spread to work properly when a window is minimized an Always on Top exists in the group. (LP: #1131385) * When using the left arrow to exit a Quicklist, Launcher keynav is implied and should be active regardless of how the Quicklist was opened. (LP: #1444626) [ Eleni Maria Stea ] * The skydome rendering of the cube plugin was wrong with unity because transformation matrices set by the unityshell plugin were left in the opengl matrix stacks affecting other compiz plugins. Saving the compiz state at the beginning of the unityshell plugin rendering functions and restoring it at the end of them fixes the problem. (LP: #1446165) -- CI Train Bot ci-train-...@canonical.com Tue, 12 May 2015 13:10:15 + ** Changed in: unity (Ubuntu) Status: In Progress = Fix Released -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1444626 Title: When in Quicklist keynav, using left arrow to exit Quicklist should enter Launcher keynav Status in Unity: In Progress Status in Unity 7.2 series: Triaged Status in unity package in Ubuntu: Fix Released Bug description: When using the arrow keys to navigate a Quicklist and using the left arrow key to exit the Quicklist, Launcher keynav should activate and on the icon for which the Quicklist was active. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1444626/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1446165] Re: the skydome effect of the cube plugin doesn't work with unity 7
This bug was fixed in the package unity - 7.3.2+15.10.20150512-0ubuntu1 --- unity (7.3.2+15.10.20150512-0ubuntu1) wily; urgency=medium [ Chris Townsend ] * Add new signal to tell the Launcher to terminate keynav mode and use that signal when a BFB quicklist item is chosen. (LP: #1052024, #1444643) * Add option to enable and disable Unity low graphics mode on the fly in ccsm or via gsettings. (LP: #1412937) * Remove code that is no longer needed and broke opening application spread while in Launcher keynav mode. (LP: #1445082) * Save the active window when showing the Dash so the correct window is focused when hiding the Dash. Fixes issue when Always on Top windows are present. (LP: #1446634) * Save the active window when showing the Hud so the correct window is focused when hiding the Hud. Fixes issue when Always on Top windows are present. (LP: #1366583) * Send signal to ensure the Dash will show when entering keynav mode since the first icon always highlighted is the BFB. (LP: #1444113) * When looking for the top-most valid window in a VP, also check if the window is focused if the window is set to Always on Top. This allows Launcher icon spread to work properly when a window is minimized an Always on Top exists in the group. (LP: #1131385) * When using the left arrow to exit a Quicklist, Launcher keynav is implied and should be active regardless of how the Quicklist was opened. (LP: #1444626) [ Eleni Maria Stea ] * The skydome rendering of the cube plugin was wrong with unity because transformation matrices set by the unityshell plugin were left in the opengl matrix stacks affecting other compiz plugins. Saving the compiz state at the beginning of the unityshell plugin rendering functions and restoring it at the end of them fixes the problem. (LP: #1446165) -- CI Train Bot ci-train-...@canonical.com Tue, 12 May 2015 13:10:15 + ** Changed in: unity (Ubuntu) Status: New = Fix Released -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1446165 Title: the skydome effect of the cube plugin doesn't work with unity 7 Status in Compiz: New Status in Unity: New Status in unity package in Ubuntu: Fix Released Bug description: when running compiz + unity 7 the skydome doesn't appear correctly (looks like it has a weird transformation) screenshot: https://i.imgur.com/nnj4y1f.jpg To manage notifications about this bug go to: https://bugs.launchpad.net/compiz/+bug/1446165/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1329048] Re: Shouldn't stop listing events until they are over
Tin, yes, this is covered by the same design change I suggested for bug 1302004. https://wiki.ubuntu.com/TimeAndDate?action=diffrev2=100rev1=99 If an event hasn't started yet, its start time should be shown, for example 7:00 PM; if it has started but not finished, its end time should be shown, for example ends 9:20 PM. -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-datetime in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1329048 Title: Shouldn't stop listing events until they are over Status in indicator-datetime package in Ubuntu: Confirmed Bug description: Using current utopic, events are dropped from the list when they start, wouldn't it make sense to list as well the ongoing ones (if you are looking to the menu 3 minutes after a meeting started you might still be interested in joining it for example) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1329048/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1446634] Re: Active windows loses focus after returning from Dash if another Always on top window is present
This bug was fixed in the package unity - 7.3.2+15.10.20150512-0ubuntu1 --- unity (7.3.2+15.10.20150512-0ubuntu1) wily; urgency=medium [ Chris Townsend ] * Add new signal to tell the Launcher to terminate keynav mode and use that signal when a BFB quicklist item is chosen. (LP: #1052024, #1444643) * Add option to enable and disable Unity low graphics mode on the fly in ccsm or via gsettings. (LP: #1412937) * Remove code that is no longer needed and broke opening application spread while in Launcher keynav mode. (LP: #1445082) * Save the active window when showing the Dash so the correct window is focused when hiding the Dash. Fixes issue when Always on Top windows are present. (LP: #1446634) * Save the active window when showing the Hud so the correct window is focused when hiding the Hud. Fixes issue when Always on Top windows are present. (LP: #1366583) * Send signal to ensure the Dash will show when entering keynav mode since the first icon always highlighted is the BFB. (LP: #1444113) * When looking for the top-most valid window in a VP, also check if the window is focused if the window is set to Always on Top. This allows Launcher icon spread to work properly when a window is minimized an Always on Top exists in the group. (LP: #1131385) * When using the left arrow to exit a Quicklist, Launcher keynav is implied and should be active regardless of how the Quicklist was opened. (LP: #1444626) [ Eleni Maria Stea ] * The skydome rendering of the cube plugin was wrong with unity because transformation matrices set by the unityshell plugin were left in the opengl matrix stacks affecting other compiz plugins. Saving the compiz state at the beginning of the unityshell plugin rendering functions and restoring it at the end of them fixes the problem. (LP: #1446165) -- CI Train Bot ci-train-...@canonical.com Tue, 12 May 2015 13:10:15 + ** Changed in: unity (Ubuntu) Status: In Progress = Fix Released -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1446634 Title: Active windows loses focus after returning from Dash if another Always on top window is present Status in Unity: In Progress Status in Unity 7.2 series: Triaged Status in unity package in Ubuntu: Fix Released Bug description: Active window looses focus after returning from Dash if Always on top window like VLC is already running. The focus is given to VLC instead of the window on which HUD was invoke. This is very similar to bug #1366583. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1446634/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1456240] Re: AP failure: unity.tests.test_panel.PanelIndicatorEntryTests.test_menu_opens_closes_on_click
After some investigation, this seems to be some issue in the Panel or Menus. I can reproduce this by hand. If the menu is opened and the mouse pointer is between halfway and below on the Panel, then the menu does not close on click for some reason. -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1456240 Title: AP failure: unity.tests.test_panel.PanelIndicatorEntryTests.test_menu_opens_closes_on_click Status in Unity: In Progress Status in unity package in Ubuntu: In Progress Bug description: Recently, an AP test has started failing consistently: unity.tests.test_panel.PanelIndicatorEntryTests.test_menu_opens_closes_on_click Need to investigate if a regression has been introduced or if the test needs to be updated to work with a new behavior. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1456240/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1456281] [NEW] Alarms not going off in ubuntu-touch/rc-proposed/bq-aquaris.en
Public bug reported: This ticket is to track a missing alarm issue that seems to have started showing up between May 15 and 18th. in #unity-api, mzanetti reports that alarms on a ubuntu-touch/rc- proposed/bq-aquaris.en are not showing up at the right time; rather, they're skewed by timezone. He's in UTC+2 and set a 6:30 alarm that didn't go off until 8:30. Alesage in Orlando is also reporting missing alarms when he tests on arale. When I test on a fresh flash of ubuntu-touch/rc-proposed/bq-aquaris.en (r9) I'm seeing the same behavior rerported by mzanetti. What's really odd though is when I apt-get source that version of indicator-datetime and run it myself, things work correctly. Alarms also working correctly on mako 15.10 r199. ** Affects: indicator-datetime (Ubuntu) Importance: Undecided Assignee: Charles Kerr (charlesk) Status: In Progress ** Changed in: indicator-datetime (Ubuntu) Status: New = In Progress ** Changed in: indicator-datetime (Ubuntu) Assignee: (unassigned) = Charles Kerr (charlesk) -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-datetime in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1456281 Title: Alarms not going off in ubuntu-touch/rc-proposed/bq-aquaris.en Status in indicator-datetime package in Ubuntu: In Progress Bug description: This ticket is to track a missing alarm issue that seems to have started showing up between May 15 and 18th. in #unity-api, mzanetti reports that alarms on a ubuntu-touch/rc- proposed/bq-aquaris.en are not showing up at the right time; rather, they're skewed by timezone. He's in UTC+2 and set a 6:30 alarm that didn't go off until 8:30. Alesage in Orlando is also reporting missing alarms when he tests on arale. When I test on a fresh flash of ubuntu-touch/rc-proposed/bq-aquaris.en (r9) I'm seeing the same behavior rerported by mzanetti. What's really odd though is when I apt-get source that version of indicator-datetime and run it myself, things work correctly. Alarms also working correctly on mako 15.10 r199. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1456281/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1456281] Re: Alarms not going off in ubuntu-touch/rc-proposed/bq-aquaris.en
Confirmed this is happening in the 15.04 branch but not the 15.10 branch. -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-datetime in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1456281 Title: Alarms not going off in ubuntu-touch/rc-proposed/bq-aquaris.en Status in indicator-datetime package in Ubuntu: In Progress Bug description: This ticket is to track a missing alarm issue that seems to have started showing up between May 15 and 18th. in #unity-api, mzanetti reports that alarms on a ubuntu-touch/rc- proposed/bq-aquaris.en are not showing up at the right time; rather, they're skewed by timezone. He's in UTC+2 and set a 6:30 alarm that didn't go off until 8:30. Alesage in Orlando is also reporting missing alarms when he tests on arale. When I test on a fresh flash of ubuntu-touch/rc-proposed/bq-aquaris.en (r9) I'm seeing the same behavior rerported by mzanetti. What's really odd though is when I apt-get source that version of indicator-datetime and run it myself, things work correctly. Alarms also working correctly on mako 15.10 r199. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1456281/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1390120] Re: Manually set time and date reverts to Automatically on restart (Ubuntu Phone)
** Changed in: systemd-shim (Ubuntu) Importance: Undecided = High -- You received this bug notification because you are a member of DX Packages, which is subscribed to systemd-shim in Ubuntu. https://bugs.launchpad.net/bugs/1390120 Title: Manually set time and date reverts to Automatically on restart (Ubuntu Phone) Status in the base for Ubuntu mobile products: Confirmed Status in systemd package in Ubuntu: Invalid Status in systemd-shim package in Ubuntu: Confirmed Status in ubuntu-system-settings package in Ubuntu: Invalid Bug description: 1a - On OS build #6 (Channel: ubuntu-touch/ubuntu-rtm/14.09), I open Time Date settings and select Manually under Set the time and date: 2a - I set the time manually from Old_Time to New_Time and wait for New_Time to display in the Date Time Indicator at top-right 3a - Then restart Ubuntu Phone and Date Time Indicator shows New_Time for 10 seconds and then reverts to Old_Time 4a - Time Date settings agree with Old_Time and Automatically has been selected under Set the time and date: To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1390120/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1456241] Re: AP failure: unity.tests.test_panel.PanelGrabAreaTests.test_lower_the_maximized_window_works
After some investigation, this is due to gsettings-desktop-schemas changing the default of org.gnome.desktop.wm.preferences action-middle- click-titlebar to none whereas it used to be lower. We need to either distro patch gsettings-desktop-schemas to set the default to lower, have Unity do something to set it, or decide to leave it as none and remove the AP test. -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1456241 Title: AP failure: unity.tests.test_panel.PanelGrabAreaTests.test_lower_the_maximized_window_works Status in Unity: Confirmed Status in unity package in Ubuntu: Confirmed Bug description: Recently, an AP test has started failing consistently: unity.tests.test_panel.PanelGrabAreaTests.test_lower_the_maximized_window_works Need to investigate if a regression has been introduced or if the test needs to be updated to work with a new behavior. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1456241/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1100546] Re: Power indicator favours 'not present' mouse over laptop battery level
@Gerry Boland, I am fan of your solution! This can't be this hard to implement!! -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-power in Ubuntu. https://bugs.launchpad.net/bugs/1100546 Title: Power indicator favours 'not present' mouse over laptop battery level Status in The Power Indicator: Triaged Status in indicator-power package in Ubuntu: Triaged Bug description: The power indicator shows the battery level for cordless mice and keyboards, even when it cannot identify the battery level. This is a problem as it seems to favour showing a not present mouse status over the laptop battery level in the top bar. I haven't done a good job of explaining it, so check out the screenshot - it will explain all :) Basically, the laptop battery should be shown in the top bar if the mouse/keyboard is not present. Also hiding the mouse and keyboard when the battery level is unknown would also be useful too :) ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: indicator-power 12.10.6daily12.11.21.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.8.0-0.3-generic 3.8.0-rc3 Uname: Linux 3.8.0-0-generic x86_64 ApportVersion: 2.8-0ubuntu1 Architecture: amd64 Date: Thu Jan 17 10:11:16 2013 InstallationDate: Installed on 2012-12-14 (33 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Alpha amd64 (20121214) MarkForUpload: True SourcePackage: indicator-power UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-power/+bug/1100546/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1100546] Re: Power indicator favours 'not present' mouse over laptop battery level
Does anybody know, where to find the source code for that? -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-power in Ubuntu. https://bugs.launchpad.net/bugs/1100546 Title: Power indicator favours 'not present' mouse over laptop battery level Status in The Power Indicator: Triaged Status in indicator-power package in Ubuntu: Triaged Bug description: The power indicator shows the battery level for cordless mice and keyboards, even when it cannot identify the battery level. This is a problem as it seems to favour showing a not present mouse status over the laptop battery level in the top bar. I haven't done a good job of explaining it, so check out the screenshot - it will explain all :) Basically, the laptop battery should be shown in the top bar if the mouse/keyboard is not present. Also hiding the mouse and keyboard when the battery level is unknown would also be useful too :) ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: indicator-power 12.10.6daily12.11.21.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.8.0-0.3-generic 3.8.0-rc3 Uname: Linux 3.8.0-0-generic x86_64 ApportVersion: 2.8-0ubuntu1 Architecture: amd64 Date: Thu Jan 17 10:11:16 2013 InstallationDate: Installed on 2012-12-14 (33 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Alpha amd64 (20121214) MarkForUpload: True SourcePackage: indicator-power UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-power/+bug/1100546/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1456240] Re: AP failure: unity.tests.test_panel.PanelIndicatorEntryTests.test_menu_opens_closes_on_click
After some discussion w/ Marco, he determined that this is some issue in Gtk3. Adding that package as affected too. ** Also affects: gtk+3.0 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1456240 Title: AP failure: unity.tests.test_panel.PanelIndicatorEntryTests.test_menu_opens_closes_on_click Status in Unity: In Progress Status in gtk+3.0 package in Ubuntu: New Status in unity package in Ubuntu: In Progress Bug description: Recently, an AP test has started failing consistently: unity.tests.test_panel.PanelIndicatorEntryTests.test_menu_opens_closes_on_click Need to investigate if a regression has been introduced or if the test needs to be updated to work with a new behavior. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1456240/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1100546] Re: Power indicator favours 'not present' mouse over laptop battery level
Ok, I am sorry for that question! Mea culpa... -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-power in Ubuntu. https://bugs.launchpad.net/bugs/1100546 Title: Power indicator favours 'not present' mouse over laptop battery level Status in The Power Indicator: Triaged Status in indicator-power package in Ubuntu: Triaged Bug description: The power indicator shows the battery level for cordless mice and keyboards, even when it cannot identify the battery level. This is a problem as it seems to favour showing a not present mouse status over the laptop battery level in the top bar. I haven't done a good job of explaining it, so check out the screenshot - it will explain all :) Basically, the laptop battery should be shown in the top bar if the mouse/keyboard is not present. Also hiding the mouse and keyboard when the battery level is unknown would also be useful too :) ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: indicator-power 12.10.6daily12.11.21.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.8.0-0.3-generic 3.8.0-rc3 Uname: Linux 3.8.0-0-generic x86_64 ApportVersion: 2.8-0ubuntu1 Architecture: amd64 Date: Thu Jan 17 10:11:16 2013 InstallationDate: Installed on 2012-12-14 (33 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Alpha amd64 (20121214) MarkForUpload: True SourcePackage: indicator-power UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-power/+bug/1100546/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1427795] Re: the lock screen/log out window is stuck rendering desktop unusable
Can you still reproduce this bug? ** Changed in: unity Status: New = Incomplete ** Changed in: unity (Ubuntu) Status: New = Incomplete ** Tags added: lockscreen -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1427795 Title: the lock screen/log out window is stuck rendering desktop unusable Status in Unity: Incomplete Status in unity package in Ubuntu: Incomplete Bug description: After locking the screen via ctrl-alt-del, upon unlocking it, the Hi $user, you have open files that you might want to save before logging out is stuck in the middle of the screen. It will not close or allow typing in any window. The only way out is to kill the X server or reboot the machine losing all open work. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.2.4+14.04.20141217-0ubuntu1 ProcVersionSignature: Ubuntu 3.16.0-31.41~14.04.1-generic 3.16.7-ckt5 Uname: Linux 3.16.0-31-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.7 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Tue Mar 3 12:56:29 2015 InstallationDate: Installed on 2015-02-23 (8 days ago) InstallationMedia: Ubuntu 14.04.2 LTS Trusty Tahr - Release amd64 (20150218.1) SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1427795/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1453491] Re: Lockscreen will not unlock on the first try if the password has a capital letter as the first letter after the system resumes from suspend
Which version of Ubuntu are you running? If it's 15.04, then it's most likely due to your touchpad driver removal. If it's 14.04 or 14.10, then it's probably bug #1308265. -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1453491 Title: Lockscreen will not unlock on the first try if the password has a capital letter as the first letter after the system resumes from suspend Status in Unity: New Status in unity package in Ubuntu: New Bug description: If my password has a capital letter, or any character that requires the shift key, as the first character in my password, then the lockscreen will not unlock on the first try after the system resumes from suspend. It will unlock at the second try. How to reproduce: 1. Change your password to: Ubuntu 2. Suspend your machine 3. Resume your machine 4. Enter your password 5. The lockscreen will not unlock 6. Enter your password again and your lockscreen will unlock To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1453491/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
Re: [Dx-packages] [Bug 1453491] Re: Lockscreen will not unlock on the first try if the password has a capital letter as the first letter after the system resumes from suspend
I've experienced it on all versions. Yes, I got around the bug in 15.04 by changing the touchpad removal script. Thanks. Hugh On Mon, May 18, 2015 at 1:15 PM, Christopher Townsend christopher.towns...@canonical.com wrote: Which version of Ubuntu are you running? If it's 15.04, then it's most likely due to your touchpad driver removal. If it's 14.04 or 14.10, then it's probably bug #1308265. -- You received this bug notification because you are subscribed to the bug report. https://bugs.launchpad.net/bugs/1453491 Title: Lockscreen will not unlock on the first try if the password has a capital letter as the first letter after the system resumes from suspend Status in Unity: New Status in unity package in Ubuntu: New Bug description: If my password has a capital letter, or any character that requires the shift key, as the first character in my password, then the lockscreen will not unlock on the first try after the system resumes from suspend. It will unlock at the second try. How to reproduce: 1. Change your password to: Ubuntu 2. Suspend your machine 3. Resume your machine 4. Enter your password 5. The lockscreen will not unlock 6. Enter your password again and your lockscreen will unlock To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1453491/+subscriptions -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1453491 Title: Lockscreen will not unlock on the first try if the password has a capital letter as the first letter after the system resumes from suspend Status in Unity: New Status in unity package in Ubuntu: New Bug description: If my password has a capital letter, or any character that requires the shift key, as the first character in my password, then the lockscreen will not unlock on the first try after the system resumes from suspend. It will unlock at the second try. How to reproduce: 1. Change your password to: Ubuntu 2. Suspend your machine 3. Resume your machine 4. Enter your password 5. The lockscreen will not unlock 6. Enter your password again and your lockscreen will unlock To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1453491/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1427795] Re: the lock screen/log out window is stuck rendering desktop unusable
After running into several other situations where one of these logout/lock screen dialogs got wedged and I had to reboot, and after losing all my work several times because the default ctrl-alt-del action is to log out rather than lock the screen as it has been in Windows forever, I just set ctrl-alt-del to lock the screen with no prompts or dialogs. So I guess you can close this though I still think this area of ubuntu is poorly implemented -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1427795 Title: the lock screen/log out window is stuck rendering desktop unusable Status in Unity: Incomplete Status in unity package in Ubuntu: Incomplete Bug description: After locking the screen via ctrl-alt-del, upon unlocking it, the Hi $user, you have open files that you might want to save before logging out is stuck in the middle of the screen. It will not close or allow typing in any window. The only way out is to kill the X server or reboot the machine losing all open work. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.2.4+14.04.20141217-0ubuntu1 ProcVersionSignature: Ubuntu 3.16.0-31.41~14.04.1-generic 3.16.7-ckt5 Uname: Linux 3.16.0-31-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.7 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Tue Mar 3 12:56:29 2015 InstallationDate: Installed on 2015-02-23 (8 days ago) InstallationMedia: Ubuntu 14.04.2 LTS Trusty Tahr - Release amd64 (20150218.1) SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1427795/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1426519] Re: Need a mechanism for specifying what happens when an ical menuitem is clicked
This bug was fixed in the package qtorganizer5-eds -
0.1.1+15.04.20150508.2-0ubuntu1
---
qtorganizer5-eds (0.1.1+15.04.20150508.2-0ubuntu1) vivid; urgency=medium
[ CI Train Bot ]
* New rebuild forced.
[ Renato Araujo Oliveira Filho ]
* Added a new extra metadata property in collection (read-only
property). (LP: #1347836)
* Avoid filter or sort results if not necessary.
* Implemented support for extended details. (LP: #1426519)
* Optimize query by filtering collections related with the current
query.
* Removed missing debug.
* Revert wrong commit.
* Save a trigger for reminders with with secondsBeforeStart equals 0.
(LP: #1440878)
-- CI Train Bot ci-train-...@canonical.com Fri, 08 May 2015 20:01:44
+
** Changed in: qtorganizer5-eds (Ubuntu)
Status: New = Fix Released
--
You received this bug notification because you are a member of DX
Packages, which is subscribed to indicator-datetime in Ubuntu.
Matching subscriptions: dx-packages
https://bugs.launchpad.net/bugs/1426519
Title:
Need a mechanism for specifying what happens when an ical menuitem is
clicked
Status in Calendar application for Ubuntu devices:
In Progress
Status in Clock application for Ubuntu devices:
New
Status in indicator-datetime package in Ubuntu:
Confirmed
Status in qtorganizer5-eds package in Ubuntu:
Fix Released
Status in reminders-app package in Ubuntu:
Confirmed
Status in indicator-datetime source package in Vivid:
New
Status in qtorganizer5-eds source package in Vivid:
New
Bug description:
indicator-datetime needs a way to dispatch an arbitrary URL when a
user clicks on an ical event menuitem.
In practice, datetime currently has clock-app hardwired for
dispatching alarms (dispatch_url('appid://com.ubuntu.clock/clock
/current-user-version')) and calendar-app for everything else
(dispatch_url('appid://com.ubuntu.calendar/calendar/current-user-
version')).
There are two use cases that can be supported by datetime handling the
URL property http://www.kanzaki.com/docs/ical/url.html:
(1) Clicking on an alarm menuitem opens up clock-app to that specific
alarm, rather than to clock-app's main page. Clock-app could specify
the information it needs in the URL, then open the right page when
passed that information later. indicator-datetime would act as a
simple pass-through.
(2) non-calendar, non-alarm items such as from the reminders app as
requested by mzanetti. The pattern would be the same as clock-app:
Reminders would add whatever URL it wants, then datetime would act as
a simple pass-through. This is preferable to adding more special cases
to indicator-datetime.
See also related bug https://bugs.launchpad.net/ubuntu/+source
/indicator-datetime/+bug/1431384 which discusses abstracting out the
icon shown in ical events' menuitems
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-calendar-app/+bug/1426519/+subscriptions
--
Mailing list: https://launchpad.net/~dx-packages
Post to : dx-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~dx-packages
More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1456241] Re: AP failure: unity.tests.test_panel.PanelGrabAreaTests.test_lower_the_maximized_window_works
** Also affects: gsettings-desktop-schemas (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1456241 Title: AP failure: unity.tests.test_panel.PanelGrabAreaTests.test_lower_the_maximized_window_works Status in Unity: Confirmed Status in gsettings-desktop-schemas package in Ubuntu: New Status in unity package in Ubuntu: Confirmed Bug description: Recently, an AP test has started failing consistently: unity.tests.test_panel.PanelGrabAreaTests.test_lower_the_maximized_window_works Need to investigate if a regression has been introduced or if the test needs to be updated to work with a new behavior. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1456241/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1451613] Re: Unity/compiz crashes when locking screen
Can anyone reproduce this on 15.04? -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1451613 Title: Unity/compiz crashes when locking screen Status in Unity: New Status in unity package in Ubuntu: Confirmed Bug description: Since a recent update (around April 29th), sometimes (approximately once a day) when I lock my computer screen (CTRL+L or using system menu) the computer freeze for a while (2 to 30 seconds) before showing the login screen. Then when I try to unlock the screen I need to enter my password twice (with no error message after the first try). Once logged in, all applications are closed. Uptime is still running (since no reboot) and services too (with no interruption). Looking at the apport.log file (see attached) it seems that when I try to lock the screen, compiz crashes. I've attached the compiz crash file too (_usr_bin_compiz.1000.crash) but without the 100Mo data of base64 core dumb… I'm using Ubuntu 14.04 AMD64. Graphics drivers: nvidia-331.113 (tested) To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1451613/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1453491] Re: Lockscreen will not unlock on the first try if the password has a capital letter as the first letter after the system resumes from suspend
** Also affects: unity Importance: Undecided Status: New ** Tags added: lockscreen -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1453491 Title: Lockscreen will not unlock on the first try if the password has a capital letter as the first letter after the system resumes from suspend Status in Unity: New Status in unity package in Ubuntu: New Bug description: If my password has a capital letter, or any character that requires the shift key, as the first character in my password, then the lockscreen will not unlock on the first try after the system resumes from suspend. It will unlock at the second try. How to reproduce: 1. Change your password to: Ubuntu 2. Suspend your machine 3. Resume your machine 4. Enter your password 5. The lockscreen will not unlock 6. Enter your password again and your lockscreen will unlock To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1453491/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1382861] Re: Auto brightness toggle sometimes doesn't appear in power indicator
** Changed in: canonical-devices-system-image Status: Confirmed = In Progress -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-power in Ubuntu. https://bugs.launchpad.net/bugs/1382861 Title: Auto brightness toggle sometimes doesn't appear in power indicator Status in the base for Ubuntu mobile products: In Progress Status in indicator-power package in Ubuntu: Fix Released Status in indicator-power source package in Vivid: New Bug description: On build #5 in the ubuntu-touch/ubuntu-rtm/devel channel, the auto brightness toggle is sometimes missing in the power indicator. Sometimes everything is fine and sometimes it's simply not there. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1382861/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1438754] Re: Backlight cannot be adjusted at lock screen
Works fine here? Can you still reproduce this? ** Also affects: unity (Ubuntu) Importance: Undecided Status: New ** Changed in: unity Status: New = Incomplete ** Changed in: unity (Ubuntu) Status: New = Incomplete ** Tags added: lockscreen -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1438754 Title: Backlight cannot be adjusted at lock screen Status in Unity: Incomplete Status in unity package in Ubuntu: Incomplete Bug description: This affects 14.04 LTS. I haven't tried any more recent versions. When the screen is locked, it is not possible to use the Fn+Brightness up/down keys. If I am using an external monitor, then I turn down the backlight brightness to zero. I often use my laptop at the office with an external monitor and the backlight turned off. When I come home and resume, the backlight is off and I cannot switch it on to see the login prompt. Steps to reproduce 1. Set backlight brightness to off using Fn+brightness down 2. Lock computer with Super+L 3. Attempt to increase brightness with Fn+brightness up Expected results: Backlight switches on, and Lock/login screen becomes visible Actual results: Backlight remains off and Lock/login screen is not visible This is a regression in 14.04 LTS since the 14.04 release. I can't remember when this started happening, but it's been at least a few weeks. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1438754/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1451613] Re: Unity/compiz crashes when locking screen
** Tags added: lockscreen -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1451613 Title: Unity/compiz crashes when locking screen Status in Unity: New Status in unity package in Ubuntu: Confirmed Bug description: Since a recent update (around April 29th), sometimes (approximately once a day) when I lock my computer screen (CTRL+L or using system menu) the computer freeze for a while (2 to 30 seconds) before showing the login screen. Then when I try to unlock the screen I need to enter my password twice (with no error message after the first try). Once logged in, all applications are closed. Uptime is still running (since no reboot) and services too (with no interruption). Looking at the apport.log file (see attached) it seems that when I try to lock the screen, compiz crashes. I've attached the compiz crash file too (_usr_bin_compiz.1000.crash) but without the 100Mo data of base64 core dumb… I'm using Ubuntu 14.04 AMD64. Graphics drivers: nvidia-331.113 (tested) To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1451613/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1456241] Re: AP failure: unity.tests.test_panel.PanelGrabAreaTests.test_lower_the_maximized_window_works
** Package changed: gsettings-desktop-schemas (Ubuntu) = ubuntu- settings (Ubuntu) ** Summary changed: - AP failure: unity.tests.test_panel.PanelGrabAreaTests.test_lower_the_maximized_window_works + org.gnome.desktop.wm.preferences action-middle-click-titlebar no longer defaults to 'lower' ** Changed in: ubuntu-settings (Ubuntu) Status: New = In Progress ** Changed in: ubuntu-settings (Ubuntu) Importance: Undecided = Medium ** Changed in: ubuntu-settings (Ubuntu) Assignee: (unassigned) = Christopher Townsend (townsend) ** No longer affects: unity (Ubuntu) ** Changed in: unity Status: Confirmed = Invalid ** Changed in: unity Milestone: 7.3.3 = None ** Changed in: unity Assignee: Christopher Townsend (townsend) = (unassigned) -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1456241 Title: org.gnome.desktop.wm.preferences action-middle-click-titlebar no longer defaults to 'lower' Status in Unity: Invalid Status in ubuntu-settings package in Ubuntu: In Progress Bug description: Recently, an AP test has started failing consistently: unity.tests.test_panel.PanelGrabAreaTests.test_lower_the_maximized_window_works Need to investigate if a regression has been introduced or if the test needs to be updated to work with a new behavior. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1456241/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1456347] Re: Possibility to set the last active alarm from the quick menu
Thanks for the bug report. By the clock quick settings menu, I presume the indicator that you swipe from the top to bottom. If that's the case, let me redirect this bug report to the correct project. ** Also affects: indicator-datetime (Ubuntu) Importance: Undecided Status: New ** Also affects: ubuntu-ux Importance: Undecided Status: New ** No longer affects: ubuntu-clock-app -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-datetime in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1456347 Title: Possibility to set the last active alarm from the quick menu Status in Ubuntu UX bugs: New Status in indicator-datetime package in Ubuntu: New Bug description: When I set the alarm I want to do this quickly and not wait for the clock app to open. Bug 1362548 already reports this problem. A even quicker option would be to have the alarm item always in the clock quick settings menu and to be able to set the last active alarm with a simple on off switch. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1456347/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1314095] Re: Unity Lockscreen in 14.04 can't unlock when using LDAP account
** Also affects: nss-pam-ldapd (Ubuntu Utopic) Importance: Undecided Status: New ** Also affects: unity (Ubuntu Utopic) Importance: Undecided Status: New ** Also affects: nss-pam-ldapd (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: unity (Ubuntu Trusty) Importance: Undecided Status: New ** Changed in: nss-pam-ldapd (Ubuntu Utopic) Status: New = Fix Released ** Changed in: nss-pam-ldapd (Ubuntu) Status: Confirmed = Fix Released ** Changed in: unity (Ubuntu Trusty) Status: New = Invalid ** Changed in: unity (Ubuntu Utopic) Status: New = Invalid -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1314095 Title: Unity Lockscreen in 14.04 can't unlock when using LDAP account Status in Unity: Invalid Status in nss-pam-ldapd package in Ubuntu: Fix Released Status in unity package in Ubuntu: Invalid Status in nss-pam-ldapd source package in Trusty: New Status in unity source package in Trusty: Invalid Status in nss-pam-ldapd source package in Utopic: Fix Released Status in unity source package in Utopic: Invalid Status in nss-pam-ldapd package in Debian: Fix Released Bug description: SRU justification: [Impact] * Summary: in Trusty, when libnss-ldapd is used, LDAP users are not able to unlock the Unity lockscreen. Utopic and later are not affected. Some workarounds are listed in comment #29. * nslcd in Trusty and earlier does not permit unprivileged users to read shadow entries. When invoked by the Unity lockscreen, running as the logged-in user, pam_unix returns PAM_AUTHINFO_UNAVAIL in pam_acct_mgmt when it tries to get password expiry information from shadow. This leads to an authorization failure, so Unity refuses to unlock the screen. pam_ldap is not consulted for pam_acct_mgmt after pam_unix fails because its rule is in the Additional section. * In Utopic and later, nslcd returns partial shadow entries to unprivileged users. This is enough for the expiry check in pam_unix to succeed, so the screen can be unlocked. See http://bugs.debian.org/706913 for a discussion of the upstream fix. * This proposed SRU backports the upstream solution to Trusty's nslcd. This is a change of behaviour for shadow queries from unprivileged users, compared to the current package. An alternative, more targeted fix would be to change Unity to ignore AUTHINFO_UNAVAIL results from pam_acct_mgmt, like gnome-screensaver already does (see comment #29). The nslcd change is a more general fix for not just Unity, but any PAM-using program run by an unprivileged user. [Test Case] * Install and configure libnss-ldapd. Ensure ldap is enabled for at least the passwd and shadow services in /etc/nsswitch.conf. * Log into Unity as an LDAP user, lock the screen, and then try to unlock it again. [Regression Potential] * The patch is minimal, was written by the upstream author, and was backported (adjusting for whitespace changes) to Trusty. The change has already been released in Utopic and will be included in Debian Jessie as well. * Regression testing should include checking that shadow queries, both by name and for listing all users, are unchanged when issued as root. [Other Info] * Packages for testing are available in ppa:rtandy/lp1314095 Original description: My setup is: Ubuntu 14.04 LTS, ldap accounts, krb5 authentication, Lightdm, Unity session ldap+krb5 is configured using nss-ldapd and nslcd. It works fine. getent passwd and getent shadow works fine. I am able to login in console without any problems. I was able to login in lightdm. Then I used the lock screen. I could not disable the lock screen using my password. I rebooted my computer. Now: After logging in through lightdm, the unity lockscreen locks the screen immediately and I can not disable it using my password. From my short inspection of auth.log and unix_chkpwd sources it seems, that unix_chkpwd works fine when called from lightdm and fails to get user info when called from unity lockscreen. lsb_release -rd Description: Ubuntu 14.04 LTS Release: 14.04 apt-cache policy unity lightdm libpam-modules unity: Installed: 7.2.0+14.04.20140416-0ubuntu1 Candidate: 7.2.0+14.04.20140416-0ubuntu1 Version table: *** 7.2.0+14.04.20140416-0ubuntu1 0 500 http://archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages 100 /var/lib/dpkg/status lightdm: Installed: 1.10.0-0ubuntu3 Candidate: 1.10.0-0ubuntu3 Version table: *** 1.10.0-0ubuntu3 0 500 http://archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages 100 /var/lib/dpkg/status libpam-modules: Installed: 1.1.8-1ubuntu2 Candidate: 1.1.8-1ubuntu2 Version table: ***
