[Dx-packages] [Bug 1329089] Re: g++-4.9 binary incompatibilities with libraries built with g++-4.8
** Branch linked: lp:~vorlon/mir/explicit-gcc-version- and-g++4.9-compatibility -- 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/1329089 Title: g++-4.9 binary incompatibilities with libraries built with g++-4.8 Status in Mir: Fix Committed Status in “dbus-cpp” package in Ubuntu: In Progress Status in “firefox” package in Ubuntu: New Status in “gcc-4.9” package in Ubuntu: Confirmed Status in “gcc-defaults” package in Ubuntu: Fix Released Status in “location-service” package in Ubuntu: Invalid Status in “mir” package in Ubuntu: Triaged Status in “process-cpp” package in Ubuntu: Invalid Status in “qtbase-opensource-src” package in Ubuntu: New Status in “unity” package in Ubuntu: New Status in “unity-scope-click” package in Ubuntu: New Status in “unity-scopes-api” package in Ubuntu: New Status in “unity-scopes-shell” package in Ubuntu: New Status in Debian GNU/Linux: New Bug description: The location-service 0.0.3+14.10.20140512-0ubuntu1 package in utopic, when rebuilt against libdbus-cpp3 3.0.0+14.10.20140604-0ubuntu1 (built with gcc-4.8) and with current gcc-defaults (which makes g++-4.9 the default), fails the package build in its test suite. 2/14 Test #2: acceptance_tests ..***Failed 30.54 sec DBus daemon: unix:abstract=/tmp/dbus-HdW1T5UHNB,guid=188551aa5d797b663dade1425398d71b task-0: Started with PID: 13031 task-0: [==] Running 2 tests from 1 test case. task-0: [--] Global test environment set-up. task-0: [--] 2 tests from LocationServiceStandalone task-0: [ RUN ] LocationServiceStandalone.SessionsReceiveUpdatesViaDBus ** (dbus-test-runner:13025): WARNING **: Timing out at maximum wait of 30 seconds. (dbus-test-runner:13025): libdbustest-CRITICAL **: dbus_test_service_run: assertion 'all_tasks(service, all_tasks_finished_helper)' failed task-0: Shutting down DBus daemon: Shutdown This test suite does *not* fail if either dbus-cpp is rebuilt with g++-4.9, or if location-service is built with g++-4.8. This implies a binary compatibility problem for C++ libraries in g++ 4.9, which is critical to resolve. To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1329089/+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 1329089] Re: g++-4.9 binary incompatibilities with libraries built with g++-4.8
Why don't we just keep utopic on g++-4.8 until 4.9 is no longer experimental? If we rebuild everything for 4.9 while it's still experimental it may well change again, requiring more rebuilds. -- 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/1329089 Title: g++-4.9 binary incompatibilities with libraries built with g++-4.8 Status in Mir: Fix Committed Status in “dbus-cpp” package in Ubuntu: In Progress Status in “firefox” package in Ubuntu: New Status in “gcc-4.9” package in Ubuntu: Confirmed Status in “gcc-defaults” package in Ubuntu: Fix Released Status in “location-service” package in Ubuntu: Invalid Status in “mir” package in Ubuntu: Triaged Status in “process-cpp” package in Ubuntu: Invalid Status in “qtbase-opensource-src” package in Ubuntu: New Status in “unity” package in Ubuntu: New Status in “unity-scope-click” package in Ubuntu: New Status in “unity-scopes-api” package in Ubuntu: New Status in “unity-scopes-shell” package in Ubuntu: New Status in Debian GNU/Linux: New Bug description: The location-service 0.0.3+14.10.20140512-0ubuntu1 package in utopic, when rebuilt against libdbus-cpp3 3.0.0+14.10.20140604-0ubuntu1 (built with gcc-4.8) and with current gcc-defaults (which makes g++-4.9 the default), fails the package build in its test suite. 2/14 Test #2: acceptance_tests ..***Failed 30.54 sec DBus daemon: unix:abstract=/tmp/dbus-HdW1T5UHNB,guid=188551aa5d797b663dade1425398d71b task-0: Started with PID: 13031 task-0: [==] Running 2 tests from 1 test case. task-0: [--] Global test environment set-up. task-0: [--] 2 tests from LocationServiceStandalone task-0: [ RUN ] LocationServiceStandalone.SessionsReceiveUpdatesViaDBus ** (dbus-test-runner:13025): WARNING **: Timing out at maximum wait of 30 seconds. (dbus-test-runner:13025): libdbustest-CRITICAL **: dbus_test_service_run: assertion 'all_tasks(service, all_tasks_finished_helper)' failed task-0: Shutting down DBus daemon: Shutdown This test suite does *not* fail if either dbus-cpp is rebuilt with g++-4.9, or if location-service is built with g++-4.8. This implies a binary compatibility problem for C++ libraries in g++ 4.9, which is critical to resolve. To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1329089/+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 1316265] Re: Maximized Window's Title Bar Does Not Merge into Menu Bar after Performing Super+W (window spread) filtering
Same problem here. I have seen the same behavior described in #7. The title bar problem occurs when I use spread (Super+W), type something until only 1 window appears, and select it (using either keyboard or mouse). This breaks the title bar integration with the top panel for all windows (even those not maximized, visible when I then try to maximize them) EXCEPT for the window that I selected in spread mode. This happens with both global menu and locally integrated menus. The fix is easy for me, though. Just open the spread mode (Super+W) and select any window or press Escape, and the problem is fixed for all windows. Also, I've seen the title in the top bar sometimes appear below the close/minimize/maximize (with locally integrated menus, at least) after using the spread mode. But it's not very consistent (and it's probably a different bug). -- 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/1316265 Title: Maximized Window's Title Bar Does Not Merge into Menu Bar after Performing Super+W (window spread) filtering Status in Unity: Triaged Status in “unity” package in Ubuntu: Triaged Bug description: A maximized application's title bar does not merge into the menu bar once a user has performed Super + W (window slide). Note that if one does not do Super+E, then the bars to merge together. However, once Super+E has been performed, this bug persists for the lifetime of the windowed application. If the application is restarted after doing Super+E, then the bug is gone. Thus, it seems like Super+E introduces this bug for the lifetime of the windowed application. Expected behavior: Maximized window's title bar is merged into menu bar. Observed: Does not occur after Super+W is performed. Try this out using Terminal. ProblemType: BugDistroRelease: Ubuntu 14.04 Package: unity 7.2.0+14.04.20140423-0ubuntu1.2 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 ApportVersion: 2.14.1-0ubuntu3 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Mon May 5 14:48:01 2014 InstallationDate: Installed on 2013-09-08 (239 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424)SourcePackage: unity UpgradeStatus: Upgraded to trusty on 2014-05-04 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1316265/+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 1061852] Re: Unity Application Lens slow to load
This is still a problem in 14.04. It takes a long time for the applications to appear in the dash, when it should be instantaneous. I have noticed that, after login, if I open the Alt+F2 scope (commands scope?), it seem that the applications/commands appear faster there. After that, opening the Dash with the Super key is fast. According to ps aux, the command that is executed when the Alt+F2 scope is opened appears to be: /usr/bin/unity-scope-loader applications/applications.scope applications/scopes.scope commands.scope If I execute this command in a terminal after login, then wait some seconds and open the Dash, the applications show a lot faster (under 2 seconds if the hard drive is not busy). So, a workaround could be to add that command to the startup applications. I'm using this now (I added a delay of 30 seconds), and it seems to work. It crashed after the first reboot, though, but it didn't happen again. As said in #8, I think the applications lens (and the other local ones?) should be preloaded at startup (in a way that doesn't slow down the boot/login process). -- 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/1061852 Title: Unity Application Lens slow to load Status in Unity: Confirmed Status in “unity” package in Ubuntu: Confirmed Bug description: WHAT HAPPENS -- Log into the system Launch the dash with the 'window' key Start typing 'chr'... I see my files appearing in the search results The application lens results appear ~10 - 15 seconds later WHAT IS DESIRABLE --- The application lens results appear immediately Most users would login into the system and launch a web browser Optimal unity experience demands that their browser or mail client shows up in the dash instantaneously Also this behaviour has worsened recently (after upgrade to 12.04) ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: unity 5.16.0-0ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-31.50-generic-pae 3.2.28 Uname: Linux 3.2.0-31-generic-pae i686 ApportVersion: 2.0.1-0ubuntu13 Architecture: i386 CompizPlugins: [core,composite,opengl,decor,resize,commands,place,regex,move,grid,session,snap,vpswitch,imgpng,gnomecompat,mousepoll,put,animation,compiztoolbox,expo,wall,ezoom,workarounds,unitymtgrabhandles,fade,scale,unityshell] Date: Fri Oct 5 01:13:34 2012 EcryptfsInUse: Yes InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Beta i386 (20120328) SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1061852/+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 1311316] Re: After locking screen there is no input field to type password for unlock
I am also having this issue yesterday second time. Use VirtualBox. I have only one monitor and Intel integrated videocard. -- 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/1311316 Title: After locking screen there is no input field to type password for unlock Status in Unity: New Status in “unity” package in Ubuntu: Confirmed Bug description: Sometimes (but not always) after locking the screen there is the situation not having any input field where I can type the password to unlock the session again. The shaded gray area simply does not have the input field. I can't do anything, I have to switch to text console and stop/start lightdm service to cure the problem loosing all of my session :( ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.2.0+14.04.20140416-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic i686 ApportVersion: 2.14.1-0ubuntu3 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Tue Apr 22 22:17:57 2014 InstallationDate: Installed on 2012-03-03 (780 days ago) InstallationMedia: Ubuntu 11.04 Natty Narwhal - Release i386 (20110427.1) SourcePackage: unity UpgradeStatus: Upgraded to trusty on 2013-10-18 (186 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1311316/+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 1324580] Re: alarm will only ring for a minute and stop whether or not the user interacted with it
Marking package indicator-datetime as affected based on the comment by Selene. The snap notification must dismiss the alarm if the user pressed the dismiss button. ** Also affects: indicator-datetime (Ubuntu) Importance: Undecided Status: New ** Changed in: indicator-datetime (Ubuntu) Status: New = Confirmed -- 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/1324580 Title: alarm will only ring for a minute and stop whether or not the user interacted with it Status in Clock application for Ubuntu devices: Confirmed Status in Ubuntu Clock App reboot series: Confirmed Status in “indicator-datetime” package in Ubuntu: Confirmed Bug description: When an alarm goes off, it will ring for only a minute and after that, whether or not the user disabled it, it stays quiet forever more. It would be interesting adding a second or even third ring after the first if the alarm was not properly disabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-clock-app/+bug/1324580/+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 1341550] [NEW] Numpad doesn't work in launcher
Public bug reported: On Ubuntu 14.04, with all updates installed: 1. Start the launcher by hitting super. 2. Type something on the numpad (incl. Enter). 3. Nothing happens. I don't think that this behavior is intended, is it? ** Affects: unity (Ubuntu) Importance: Undecided Status: New ** Description changed: + On Ubuntu 14.04, with all updates installed: + 1. Start the launcher by hitting super. 2. Type something on the numpad (incl. Enter). 3. Nothing happens. I don't think that this behavior is intended, is it? -- 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/1341550 Title: Numpad doesn't work in launcher Status in “unity” package in Ubuntu: New Bug description: On Ubuntu 14.04, with all updates installed: 1. Start the launcher by hitting super. 2. Type something on the numpad (incl. Enter). 3. Nothing happens. I don't think that this behavior is intended, is it? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1341550/+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 1341562] [NEW] indicator-printers not working on Ubuntu 14.04
Public bug reported: This is a regression from bug 1304434 The bug is still there for quite a lot of users including myself. Please can the Ubuntu Dev Team look into this bug again for us please. ** Affects: indicator-printers (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-printers in Ubuntu. https://bugs.launchpad.net/bugs/1341562 Title: indicator-printers not working on Ubuntu 14.04 Status in “indicator-printers” package in Ubuntu: New Bug description: This is a regression from bug 1304434 The bug is still there for quite a lot of users including myself. Please can the Ubuntu Dev Team look into this bug again for us please. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-printers/+bug/1341562/+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 1304434] Re: indicator-printers not working on Ubuntu 14.04
The new bug report number is Bug #1341562 -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-printers in Ubuntu. https://bugs.launchpad.net/bugs/1304434 Title: indicator-printers not working on Ubuntu 14.04 Status in Print Indicator: In Progress Status in “indicator-printers” package in Ubuntu: Fix Released Status in “indicator-printers” source package in Trusty: Fix Released Bug description: [Impact] The panel should have a print indicator as long as there are any print jobs queued or processed. Currently, this indicator never appears, even though printing works fine. This is because the service that listens to CUPS fails to register its D-Bus name (as of revision 68), which results in the panel component not finding the service. The attached branch fixes this by making the service register the name the panel expects. [Test Case] Print a document from any application and check whether the print indicator appears while it is printing. [Regression Potential] Almost none. The print indicator is not working at all right now, and the fix only touches that indicator. [Original Description] even after lates updates still no printer notifications in the panel . I checked and the package indicator-printers is correctly installed and the printer prints without problems. But, there is no notification icons on unity panel. I had no problems at all with 13.10 instead To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-printers/+bug/1304434/+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 1304434] Re: indicator-printers not working on Ubuntu 14.04
Anyone still affected by this bug please put on this new bug report which I've opened because no one on the Ubuntu Dev Team will be receiving updates from this current bug until enough of us report this issue is still happening on a NEW bug report - see comment #30 in this bug report. I hope that someone in ubuntu's dev team will respond. The more of us that say this bug is still affecting us the sooner we'll get help. Thank you. -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-printers in Ubuntu. https://bugs.launchpad.net/bugs/1304434 Title: indicator-printers not working on Ubuntu 14.04 Status in Print Indicator: In Progress Status in “indicator-printers” package in Ubuntu: Fix Released Status in “indicator-printers” source package in Trusty: Fix Released Bug description: [Impact] The panel should have a print indicator as long as there are any print jobs queued or processed. Currently, this indicator never appears, even though printing works fine. This is because the service that listens to CUPS fails to register its D-Bus name (as of revision 68), which results in the panel component not finding the service. The attached branch fixes this by making the service register the name the panel expects. [Test Case] Print a document from any application and check whether the print indicator appears while it is printing. [Regression Potential] Almost none. The print indicator is not working at all right now, and the fix only touches that indicator. [Original Description] even after lates updates still no printer notifications in the panel . I checked and the package indicator-printers is correctly installed and the printer prints without problems. But, there is no notification icons on unity panel. I had no problems at all with 13.10 instead To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-printers/+bug/1304434/+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 1341562] Re: indicator-printers not working on Ubuntu 14.04
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: indicator-printers (Ubuntu) Status: New = Confirmed -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-printers in Ubuntu. https://bugs.launchpad.net/bugs/1341562 Title: indicator-printers not working on Ubuntu 14.04 Status in “indicator-printers” package in Ubuntu: Confirmed Bug description: This is a regression from bug 1304434 The bug is still there for quite a lot of users including myself. Please can the Ubuntu Dev Team look into this bug again for us please. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-printers/+bug/1341562/+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 1292041] Re: Lockscreen doesn't turn off the screen
I still have the same problem described at #30. -- 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/1292041 Title: Lockscreen doesn't turn off the screen Status in OEM Priority Project: Fix Released Status in OEM Priority Project trusty series: Fix Released Status in Unity: Fix Released Status in “gnome-screensaver” package in Ubuntu: Invalid Status in “unity” package in Ubuntu: Fix Released Bug description: The new Unity lock screen doesn't turn off the monitor screen. I can wait as long as 10 minutes after activating the lock screen and the monitor still doesn't trun off. Then when I unlock the screen and don't use mouse or keyboard monitor will turn off (it's about 5 seconds after unlocking). To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1292041/+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 1292041] Vacation reply
-- 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/1292041 Title: Lockscreen doesn't turn off the screen Status in OEM Priority Project: Fix Released Status in OEM Priority Project trusty series: Fix Released Status in Unity: Fix Released Status in “gnome-screensaver” package in Ubuntu: Invalid Status in “unity” package in Ubuntu: Fix Released Bug description: The new Unity lock screen doesn't turn off the monitor screen. I can wait as long as 10 minutes after activating the lock screen and the monitor still doesn't trun off. Then when I unlock the screen and don't use mouse or keyboard monitor will turn off (it's about 5 seconds after unlocking). To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1292041/+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 1341603] [NEW] Missing menus in ubuntu-sdk when appmenu-qt5 is installed
Public bug reported: The menu bar in ubuntu-sdk is completely missing when appmenu-qt5 is installed. This has been tested in both Ubuntu(Default) and AwesomeWM. When using Ubuntu(Default) I pressed alt to open the menu search dialog but was unable to find any menu items. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: appmenu-qt5 0.3.0+14.04.20140415-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 NonfreeKernelModules: fglrx ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 Date: Mon Jul 14 16:23:36 2014 InstallationDate: Installed on 2014-02-13 (150 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140211) SourcePackage: appmenu-qt5 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: appmenu-qt5 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug third-party-packages trusty -- You received this bug notification because you are a member of DX Packages, which is subscribed to appmenu-qt5 in Ubuntu. https://bugs.launchpad.net/bugs/1341603 Title: Missing menus in ubuntu-sdk when appmenu-qt5 is installed Status in “appmenu-qt5” package in Ubuntu: New Bug description: The menu bar in ubuntu-sdk is completely missing when appmenu-qt5 is installed. This has been tested in both Ubuntu(Default) and AwesomeWM. When using Ubuntu(Default) I pressed alt to open the menu search dialog but was unable to find any menu items. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: appmenu-qt5 0.3.0+14.04.20140415-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 NonfreeKernelModules: fglrx ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 Date: Mon Jul 14 16:23:36 2014 InstallationDate: Installed on 2014-02-13 (150 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140211) SourcePackage: appmenu-qt5 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/appmenu-qt5/+bug/1341603/+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 1341603] Re: Missing menus in ubuntu-sdk when appmenu-qt5 is installed
I also have this problem running under Gnome Shell. I'm currently on 14.04, and this happened both before and after I installed with SDK team tools-development PPA. Previously on 12.04, I did not see this problem under Gnome Shell. -- You received this bug notification because you are a member of DX Packages, which is subscribed to appmenu-qt5 in Ubuntu. https://bugs.launchpad.net/bugs/1341603 Title: Missing menus in ubuntu-sdk when appmenu-qt5 is installed Status in “appmenu-qt5” package in Ubuntu: New Bug description: The menu bar in ubuntu-sdk is completely missing when appmenu-qt5 is installed. This has been tested in both Ubuntu(Default) and AwesomeWM. When using Ubuntu(Default) I pressed alt to open the menu search dialog but was unable to find any menu items. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: appmenu-qt5 0.3.0+14.04.20140415-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 NonfreeKernelModules: fglrx ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 Date: Mon Jul 14 16:23:36 2014 InstallationDate: Installed on 2014-02-13 (150 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140211) SourcePackage: appmenu-qt5 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/appmenu-qt5/+bug/1341603/+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 1324580] Re: alarm will only ring for a minute and stop whether or not the user interacted with it
** Changed in: ubuntu-clock-app/reboot Importance: High = Critical -- 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/1324580 Title: alarm will only ring for a minute and stop whether or not the user interacted with it Status in Clock application for Ubuntu devices: Confirmed Status in Ubuntu Clock App reboot series: Confirmed Status in “indicator-datetime” package in Ubuntu: Confirmed Bug description: When an alarm goes off, it will ring for only a minute and after that, whether or not the user disabled it, it stays quiet forever more. It would be interesting adding a second or even third ring after the first if the alarm was not properly disabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-clock-app/+bug/1324580/+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 1341625] Re: compiz crashed with SIGABRT in __libc_message()
*** This bug is a duplicate of bug 1307081 *** https://bugs.launchpad.net/bugs/1307081 Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1307081, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find. ** Attachment removed: CoreDump.gz https://bugs.launchpad.net/bugs/1341625/+attachment/4152324/+files/CoreDump.gz ** Attachment removed: Disassembly.txt https://bugs.launchpad.net/bugs/1341625/+attachment/4152326/+files/Disassembly.txt ** Attachment removed: ProcMaps.txt https://bugs.launchpad.net/bugs/1341625/+attachment/4152328/+files/ProcMaps.txt ** Attachment removed: ProcStatus.txt https://bugs.launchpad.net/bugs/1341625/+attachment/4152329/+files/ProcStatus.txt ** Attachment removed: Registers.txt https://bugs.launchpad.net/bugs/1341625/+attachment/4152330/+files/Registers.txt ** Attachment removed: Stacktrace.txt https://bugs.launchpad.net/bugs/1341625/+attachment/4152331/+files/Stacktrace.txt ** Attachment removed: ThreadStacktrace.txt https://bugs.launchpad.net/bugs/1341625/+attachment/4152332/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of private bug 1307081 ** Information type changed from Private to Public ** Tags removed: need-amd64-retrace -- 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/1341625 Title: compiz crashed with SIGABRT in __libc_message() Status in “unity” package in Ubuntu: New Bug description: Dash sometimes crashes. ProblemType: Crash DistroRelease: Ubuntu 14.10 Package: unity 7.3.0+14.10.20140711-0ubuntu1 ProcVersionSignature: Ubuntu 3.16.0-3.8-generic 3.16.0-rc4 Uname: Linux 3.16.0-3-generic x86_64 ApportVersion: 2.14.4-0ubuntu2 Architecture: amd64 CrashCounter: 1 CurrentDesktop: Unity Date: Mon Jul 14 19:03:31 2014 ExecutablePath: /usr/bin/compiz InstallationDate: Installed on 2014-01-06 (189 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 (20131016.1) ProcCmdline: compiz Signal: 6 SourcePackage: unity StacktraceTop: __libc_message (do_abort=do_abort@entry=2, fmt=fmt@entry=0x7fd3a4515610 *** %s ***: %s terminated\n) at ../sysdeps/posix/libc_fatal.c:175 __GI___fortify_fail (msg=optimized out) at fortify_fail.c:37 longjmp_chk () at ../sysdeps/unix/sysv/linux/x86_64/longjmp_chk.S:100 __longjmp_chk (env=0x1, val=1) at ../setjmp/longjmp.c:38 ?? () from /usr/lib/x86_64-linux-gnu/libfreetype.so.6 Title: compiz crashed with SIGABRT in __libc_message() UpgradeStatus: Upgraded to utopic on 2014-07-07 (6 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1341625/+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 1329089] Re: g++-4.9 binary incompatibilities with libraries built with g++-4.8
On Mon, Jul 14, 2014 at 08:22:04AM -, Daniel van Vugt wrote: Why don't we just keep utopic on g++-4.8 until 4.9 is no longer experimental? 4.9 is not experimental. *C++11 support in gcc upstream* is experimental. There is a single rebuild required here for the move from 4.8 to 4.9, no further rebuilds will be required for ABI changes within gcc 4.9. -- 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/1329089 Title: g++-4.9 binary incompatibilities with libraries built with g++-4.8 Status in Mir: Fix Committed Status in “dbus-cpp” package in Ubuntu: In Progress Status in “firefox” package in Ubuntu: New Status in “gcc-4.9” package in Ubuntu: Confirmed Status in “gcc-defaults” package in Ubuntu: Fix Released Status in “location-service” package in Ubuntu: Invalid Status in “mir” package in Ubuntu: Triaged Status in “process-cpp” package in Ubuntu: Invalid Status in “qtbase-opensource-src” package in Ubuntu: New Status in “unity” package in Ubuntu: New Status in “unity-scope-click” package in Ubuntu: New Status in “unity-scopes-api” package in Ubuntu: New Status in “unity-scopes-shell” package in Ubuntu: New Status in Debian GNU/Linux: New Bug description: The location-service 0.0.3+14.10.20140512-0ubuntu1 package in utopic, when rebuilt against libdbus-cpp3 3.0.0+14.10.20140604-0ubuntu1 (built with gcc-4.8) and with current gcc-defaults (which makes g++-4.9 the default), fails the package build in its test suite. 2/14 Test #2: acceptance_tests ..***Failed 30.54 sec DBus daemon: unix:abstract=/tmp/dbus-HdW1T5UHNB,guid=188551aa5d797b663dade1425398d71b task-0: Started with PID: 13031 task-0: [==] Running 2 tests from 1 test case. task-0: [--] Global test environment set-up. task-0: [--] 2 tests from LocationServiceStandalone task-0: [ RUN ] LocationServiceStandalone.SessionsReceiveUpdatesViaDBus ** (dbus-test-runner:13025): WARNING **: Timing out at maximum wait of 30 seconds. (dbus-test-runner:13025): libdbustest-CRITICAL **: dbus_test_service_run: assertion 'all_tasks(service, all_tasks_finished_helper)' failed task-0: Shutting down DBus daemon: Shutdown This test suite does *not* fail if either dbus-cpp is rebuilt with g++-4.9, or if location-service is built with g++-4.8. This implies a binary compatibility problem for C++ libraries in g++ 4.9, which is critical to resolve. To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1329089/+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 1324580] Re: alarm will only ring for a minute and stop whether or not the user interacted with it
** Changed in: indicator-datetime (Ubuntu) Importance: Undecided = High ** Changed in: indicator-datetime (Ubuntu) Status: Confirmed = Triaged ** 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/1324580 Title: alarm will only ring for a minute and stop whether or not the user interacted with it Status in Clock application for Ubuntu devices: Confirmed Status in Ubuntu Clock App reboot series: Confirmed Status in “indicator-datetime” package in Ubuntu: Triaged Bug description: When an alarm goes off, it will ring for only a minute and after that, whether or not the user disabled it, it stays quiet forever more. It would be interesting adding a second or even third ring after the first if the alarm was not properly disabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-clock-app/+bug/1324580/+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 1228093] Re: Dash content flickers when the touchpad is used to scroll it.
** Branch linked: lp:~3v1n0/nux/horizontal-scroll-delta -- You received this bug notification because you are a member of DX Packages, which is subscribed to nux in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1228093 Title: Dash content flickers when the touchpad is used to scroll it. Status in Nux: In Progress Status in “nux” package in Ubuntu: In Progress Bug description: When the touchpad is used to scroll the dash sometimes scroll down is dected as scroll up and vice versa. Two fingers scroll must be ON! This is because horizontal scrolling is now enabled by default and can't be disabled using g-c-c. To manage notifications about this bug go to: https://bugs.launchpad.net/nux/+bug/1228093/+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 1283065] Re: Use the existing audio stack to play event sounds
This bug was fixed in the package indicator-datetime - 13.10.0+14.10.20140714.1-0ubuntu1 --- indicator-datetime (13.10.0+14.10.20140714.1-0ubuntu1) utopic; urgency=low [ Charles Kerr ] * Use GStreamer's API directly to play sound instead of using libcanberra. (LP: #1283065) -- Ubuntu daily release ps-jenk...@lists.canonical.com Mon, 14 Jul 2014 13:40:44 + ** Changed in: indicator-datetime (Ubuntu) Status: Triaged = 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/1283065 Title: Use the existing audio stack to play event sounds Status in “indicator-datetime” package in Ubuntu: Fix Released Bug description: This merge introduced several new packages in order to produce sounds on calendar events https://code.launchpad.net/~charlesk/indicator-datetime/alarms/+merge/204420 We should rather use existing APIs in QtMultimedia or go directly to the media service in the platform api. - reduce number of packages supported - allow coordination for audio playback from multiple sources - support multiple encoding formats To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1283065/+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 1301160] Re: Gtk-message: Failed to load module unity-gtk-module
14 July 2014 - the bug is still present from terminal almost any app complain about : Failed to load module unity-gtk-module -- 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/1301160 Title: Gtk-message: Failed to load module unity-gtk-module Status in “unity” package in Ubuntu: Confirmed Bug description: Trusty i386, logged as gnome-shell (genuine trusty archive package) Found that error logged into: .cache/upstart/gnome-session-gnome.log Join a strace about unity-gtk-module nb: i really does not know about the package to report against ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.1.2+14.04.20140328.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-21.43-generic 3.13.8 Uname: Linux 3.13.0-21-generic i686 NonfreeKernelModules: nvidia ApportVersion: 2.14-0ubuntu1 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] CurrentDesktop: GNOME Date: Wed Apr 2 07:55:32 2014 InstallationDate: Installed on 2013-10-25 (158 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release i386 (20131021.1) SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1301160/+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 1317869] Re: Keyboard shortcuts overlay does not show up when workspaces are enabled at 1366x768
** Changed in: unity (Ubuntu) Importance: Undecided = Low -- 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/1317869 Title: Keyboard shortcuts overlay does not show up when workspaces are enabled at 1366x768 Status in Unity: Fix Released Status in Unity 7.2 series: In Progress Status in “unity” package in Ubuntu: Fix Released Bug description: My notebook has a 1366x768 screen - it is a very common screen resolution. When I boot Ubuntu 14.04 liveISO the keyboard shortcuts overlay is displayed and works very well - therefore my screen resolution is large enough for it. But after I installed 14.04 on my hard disk, the shortcuts overlay does not show anymore. The attachment is a screenshot of the shortcuts overlay working on the liveISO. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1317869/+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
The problem is gone... I haven't changed anything (or been on this PC much since my original posting actually) and according to the changelogs there hasn't been an update in either Firefox or hud since then. No idea what caused this. -- 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,
[Dx-packages] [Bug 607796] Re: Launcher, Window management - Dragging and holding a selection over an entry in the Launcher should spread out windows belonging to that application
** Description changed: - If the user drags and hold a file over a running application in the - Launcher, all the windows of that application should be shown with the - spread. The user should then be able to drag and drop the file in a - windows in the spread to load the file into that specific window. + [Impact] + If the user drags and hold a file over a running application in the Launcher, all the windows of that application should be shown with the spread. The user should then be able to drag and drop the file in a windows in the spread to load the file into that specific window. + + [Test Case] + 1) Open two windows instances of the same application (say firefox) + 2) Drag a file from the file-manager or the desktop and hover the firefox icon + 3) After one second the firefox icon is hovered, the spread will occur + 4) You should be able to hover one of the firefox windows and it should +show a spinner, after 750ms (by default) the hovered windows should be focused +and raised + 5) You should now be able to drop the content you're dragging (if the selected +application supports that content). + + [Regression Potential] + This codepath was mostly disabled in the current compiz and unity code because it was buggy, so the regression potential is very low, although it might happen that, if some race-condition happens, when closing the scale the launcher might be still painted as if it would be in scale mode (desaturated) even if it's not the case anymore. + + + ### + Bug #727903 needs to be fixed at the same time. --- History: This bug had been previously fixed as buggybutclosed for Unity on 2011-04-18, leaving this function with other bugs: https://bugs.launchpad.net/ayatana-design/+bug/727903 https://bugs.launchpad.net/ayatana-design/+bug/727904 https://bugs.launchpad.net/ayatana-design/+bug/727902 https://bugs.launchpad.net/ayatana-design/+bug/764424 https://bugs.launchpad.net/ayatana-design/+bug/832988 On 2011-10-18, it was reopened for regression in Oneiric. -- 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/607796 Title: Launcher, Window management - Dragging and holding a selection over an entry in the Launcher should spread out windows belonging to that application Status in Ayatana Design: Fix Committed Status in Compiz: Fix Committed Status in Compiz 0.9.11 series: In Progress Status in One Hundred Papercuts: Fix Released Status in Unity: Fix Released Status in Unity 7.2 series: In Progress Status in “compiz” package in Ubuntu: Fix Released Status in “unity” package in Ubuntu: Fix Released Bug description: [Impact] If the user drags and hold a file over a running application in the Launcher, all the windows of that application should be shown with the spread. The user should then be able to drag and drop the file in a windows in the spread to load the file into that specific window. [Test Case] 1) Open two windows instances of the same application (say firefox) 2) Drag a file from the file-manager or the desktop and hover the firefox icon 3) After one second the firefox icon is hovered, the spread will occur 4) You should be able to hover one of the firefox windows and it should show a spinner, after 750ms (by default) the hovered windows should be focused and raised 5) You should now be able to drop the content you're dragging (if the selected application supports that content). [Regression Potential] This codepath was mostly disabled in the current compiz and unity code because it was buggy, so the regression potential is very low, although it might happen that, if some race-condition happens, when closing the scale the launcher might be still painted as if it would be in scale mode (desaturated) even if it's not the case anymore. ### Bug #727903 needs to be fixed at the same time. --- History: This bug had been previously fixed as buggybutclosed for Unity on 2011-04-18, leaving this function with other bugs: https://bugs.launchpad.net/ayatana-design/+bug/727903 https://bugs.launchpad.net/ayatana-design/+bug/727904 https://bugs.launchpad.net/ayatana-design/+bug/727902 https://bugs.launchpad.net/ayatana-design/+bug/764424 https://bugs.launchpad.net/ayatana-design/+bug/832988 On 2011-10-18, it was reopened for regression in Oneiric. To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/607796/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help :
[Dx-packages] [Bug 754580] Re: Cannot move tabs between multiple Firefox or Chromium windows while using Unity unless windows are both unmaximized, unminimized, and visible.
** Description changed: - Binary package hint: unity + [Impact] + It's not possible to drag firefox or chromium tabs to the relative launcher icon in order to select a different window as drop target. + + [Test case] + 1. Open two Chromium or Firefox windows, with two tabs open in each. + 2. Start dragging a browser tab over a browser icon in the Launcher + 3. Unity should displays a spread of the two browser windows + 4. It will be possible to drop the tab in one of the browser windows, +after selecting it in spread. + + [Regression Potential] + As it happened with bug #727902 this codepath was disabled in the past, thus there's basically no regression potential. + + --- With Metacity, one would need only to drag the tab to the bottom bar, mouse-over the destination window, and then release the tab in the newly focused window. There is no equivalent behavior with Unity. Dragging tabs to its bar does nothing. - - Desired resolution: Users should be able to move tabs between browser windows irrespective of window state (minimised, restored or maximised) by dragging and dropping the via the Launcher app spread. - - Use case - 1. User opens two Chromium or Firefox windows, with two tabs open in each. - 2. User starts dragging a browser tab - 3. Unity slides out the Launcher with valid drop receptacles highlighted - 4. User drags the tab over a browser icon in the Launcher - 5. Unity displays a spread of the two browser windows - 6. User continues the drag, and drags and drops the tab into the other browser window - 7. Unity shifts the tab to the other browser window. If this window is minimised it is restored and brought into focus. If this window is maximised or restored it is brought into focus. -- 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/754580 Title: Cannot move tabs between multiple Firefox or Chromium windows while using Unity unless windows are both unmaximized, unminimized, and visible. Status in Ayatana Design: Fix Committed Status in Chromium Browser: New Status in Unity: Fix Released Status in Unity 7.2 series: In Progress Status in “chromium-browser” package in Ubuntu: Triaged Status in “firefox” package in Ubuntu: Invalid Status in “unity” package in Ubuntu: Fix Released Bug description: [Impact] It's not possible to drag firefox or chromium tabs to the relative launcher icon in order to select a different window as drop target. [Test case] 1. Open two Chromium or Firefox windows, with two tabs open in each. 2. Start dragging a browser tab over a browser icon in the Launcher 3. Unity should displays a spread of the two browser windows 4. It will be possible to drop the tab in one of the browser windows, after selecting it in spread. [Regression Potential] As it happened with bug #727902 this codepath was disabled in the past, thus there's basically no regression potential. --- With Metacity, one would need only to drag the tab to the bottom bar, mouse-over the destination window, and then release the tab in the newly focused window. There is no equivalent behavior with Unity. Dragging tabs to its bar does nothing. - Desired resolution: Users should be able to move tabs between browser windows irrespective of window state (minimised, restored or maximised) by dragging and dropping the via the Launcher app spread. To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/754580/+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 741869] Re: Unity/compiz intercepts Super and Alt keypresses from grabbed windows like VMs.
** Description changed: - [Impact]After upgrading from Maverick to Natty, I can no longer use the - Super (windows) key in Virtual Machine Manager. Previously, as long as I - had the Virtual Machine Manager console window in the foreground, I - could press the Super key and the start menu would pop up. Since - upgrading to Natty, this no longer works, and the search box appears in - the upper left. + [Impact] + After upgrading from Maverick to Natty, I can no longer use the Super (windows) key in Virtual Machine Manager. Previously, as long as I had the Virtual Machine Manager console window in the foreground, I could press the Super key and the start menu would pop up. Since upgrading to Natty, this no longer works, and the search box appears in the upper left. Also see bug #934921 [Test Case] (1) Install virtualbox or virt-manager and qemu-system, create and boot a virtual machine (2) while in the virtual machine (and it should grab the keyboard), press the Super key Expected Result: the super key acts inside the VM (check by install unity on it or using xev) Buggy Result: the super key acts in the host and the Unity Dash is displayed [regression Potential]This patch plays with key grabs and ungrabs: the most likely potential for regression is (a) the existing grabs continue and no fix obtains or (2) the grab is not resumed when returning control from the VM and the Super key does not invoke the Unity Dash. -- 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/741869 Title: Unity/compiz intercepts Super and Alt keypresses from grabbed windows like VMs. Status in Ayatana Design: Fix Committed Status in Compiz: Triaged Status in Compiz Core: Triaged Status in OEM Priority Project: Won't Fix Status in OEM Priority Project precise series: Won't Fix Status in Unity: Fix Released Status in Unity 7.2 series: In Progress Status in “compiz” package in Ubuntu: Triaged Status in “unity” package in Ubuntu: Fix Released Bug description: [Impact] After upgrading from Maverick to Natty, I can no longer use the Super (windows) key in Virtual Machine Manager. Previously, as long as I had the Virtual Machine Manager console window in the foreground, I could press the Super key and the start menu would pop up. Since upgrading to Natty, this no longer works, and the search box appears in the upper left. Also see bug #934921 [Test Case] (1) Install virtualbox or virt-manager and qemu-system, create and boot a virtual machine (2) while in the virtual machine (and it should grab the keyboard), press the Super key Expected Result: the super key acts inside the VM (check by install unity on it or using xev) Buggy Result: the super key acts in the host and the Unity Dash is displayed [regression Potential]This patch plays with key grabs and ungrabs: the most likely potential for regression is (a) the existing grabs continue and no fix obtains or (2) the grab is not resumed when returning control from the VM and the Super key does not invoke the Unity Dash. To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/741869/+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 727902] Re: Launcher icon highlighting should not switch off as soon the cursor moves after the app spread appears.
** Description changed: + [Impact] + When dragging a file to an application with multiple windows open and the spread is triggered, any movement of the mouse switches off the selective highlighting and dimming of valid/non-valid drop receptacles. + + [Test Case] + 1) Open two windows instances of the same application (say firefox) + 2) Drag a file from the file-manager or the desktop and hover the firefox icon + 3) After one second the firefox icon is hovered, the spread will occur + 4) Dragging the icon outside the launcher and in the spread area (both over a window or +not) should keep the desaturated icons as they were before. + + [Regression Potential] + Launcher icon might be not saturated again when exiting from spread. + + -- + Description. When a file is dragged and held over a application icon in the Launcher a spread of the app windows appear. The user can then drag and drop the file on to one of the windows to specify the window in which they would like the file to be loaded. The bug is that after the spread appears, any movement of the mouse switches off the selective highlighting and dimming of valid/non-valid drop receptacles. Desired behaviour - The highlighting and dimming of Launcher icons should persist until the user drops the file. - Note that the 'spread when a item is held over a launcher icon' behaviour seems to be broken in the Oneiric final freeze release (nothing happens). -- 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/727902 Title: Launcher icon highlighting should not switch off as soon the cursor moves after the app spread appears. Status in Ayatana Design: Fix Committed Status in Unity: Fix Released Status in Unity 7.2 series: In Progress Status in “unity” package in Ubuntu: Fix Released Bug description: [Impact] When dragging a file to an application with multiple windows open and the spread is triggered, any movement of the mouse switches off the selective highlighting and dimming of valid/non-valid drop receptacles. [Test Case] 1) Open two windows instances of the same application (say firefox) 2) Drag a file from the file-manager or the desktop and hover the firefox icon 3) After one second the firefox icon is hovered, the spread will occur 4) Dragging the icon outside the launcher and in the spread area (both over a window or not) should keep the desaturated icons as they were before. [Regression Potential] Launcher icon might be not saturated again when exiting from spread. -- Description. When a file is dragged and held over a application icon in the Launcher a spread of the app windows appear. The user can then drag and drop the file on to one of the windows to specify the window in which they would like the file to be loaded. The bug is that after the spread appears, any movement of the mouse switches off the selective highlighting and dimming of valid/non-valid drop receptacles. Desired behaviour - The highlighting and dimming of Launcher icons should persist until the user drops the file. - Note that the 'spread when a item is held over a launcher icon' behaviour seems to be broken in the Oneiric final freeze release (nothing happens). To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/727902/+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 839728] Re: Launcher - dragging a item on top of a launcher tile that is a valid drop receptacle in the Launcher should cause that launcher tile to glow
** Description changed: + [Impact] + The drag and drop launcher icons are not correctly marked as targets + + [Test case] + 1) Drag a file a launcher icon + 2) The launcher icon under the mouse pointer should have a glowing tile + + 3) When the mouse pointer leaves the launcher icon area or the mouse is released +the icon should not glow anymore (unless is not an urgent icon). + + + [Regression Potential] + An icon that is not urgent might be left with a glowing tile when leaving the DnD or an urgent icon might not being glowing anymore after leaving the Dnd. + + + - + Launcher - dragging a item on top of a launcher tile that is a valid drop receptacle in the Launcher should cause that launcher tile to glow. This glow only persists as long as the dragged item is directly over the launcher tile, as soon as the dragged item is moved off the launcher tile, the glow should stop. Use cases: - User drags a .png file over the Firefox icon in the Launcher. As soon as the .png file is over the Firefox icon, the firefox icon starts to glow. The user then moves the .png file off the Firefox launcher icon, and the Firefox launcher immediately stops glowing. - User drags a launcher tile from it's position in the launcher to the trash can. As soon as the Launcher tile is above the trash can, the trash can starts to glow. The user then moves the launcher tile off the trash can and the trash can stops glowing. -- 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/839728 Title: Launcher - dragging a item on top of a launcher tile that is a valid drop receptacle in the Launcher should cause that launcher tile to glow Status in Ayatana Design: Fix Committed Status in Unity: Fix Released Status in Unity 7.2 series: In Progress Status in “unity” package in Ubuntu: Fix Released Bug description: [Impact] The drag and drop launcher icons are not correctly marked as targets [Test case] 1) Drag a file a launcher icon 2) The launcher icon under the mouse pointer should have a glowing tile 3) When the mouse pointer leaves the launcher icon area or the mouse is released the icon should not glow anymore (unless is not an urgent icon). [Regression Potential] An icon that is not urgent might be left with a glowing tile when leaving the DnD or an urgent icon might not being glowing anymore after leaving the Dnd. - Launcher - dragging a item on top of a launcher tile that is a valid drop receptacle in the Launcher should cause that launcher tile to glow. This glow only persists as long as the dragged item is directly over the launcher tile, as soon as the dragged item is moved off the launcher tile, the glow should stop. Use cases: - User drags a .png file over the Firefox icon in the Launcher. As soon as the .png file is over the Firefox icon, the firefox icon starts to glow. The user then moves the .png file off the Firefox launcher icon, and the Firefox launcher immediately stops glowing. - User drags a launcher tile from it's position in the launcher to the trash can. As soon as the Launcher tile is above the trash can, the trash can starts to glow. The user then moves the launcher tile off the trash can and the trash can stops glowing. To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/839728/+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 924840] Re: Keyboard shortcuts overlay text too long
** Description changed: + [Inpact] + The shortcut overlay window listes some truncated keybindings and descriptions although there's enough horizontal space to show them all. + + [Test case] + The test case for this bug depends a lot on the locale used and thus there's not an universal way to verify it, this is generally valid for English locale but should apply to others as well: + + 1. In Unity Control Center - Appearance - Behavior enable the workspaces + 2. Hold down the super key unless the shortcut overlay window is not show (if it's +supported, minimum resolution is 1366x768) + 3. Both the keybindings and the descriptions should not be ellipsised if there's enough +horizontal space to present them, for example the Super + Alt + Cursor ke.. +keybinding should be instead Super + Alt + Cursor keys + + [Regression potential] + The view might be too large in some locales and thus not to show at all, although we should generally handle this as it used to be before. + + -- + When I hold down Super I get a popup image detailing the shortcut keys. There are a few issues with this image which I have filed as separate bugs. Workspaces Text too long to fit. I see Super + Alt + Cursor ke.. Which I presume should say Cursor keys -- 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/924840 Title: Keyboard shortcuts overlay text too long Status in Ayatana Design: New Status in Ubuntu Translations: New Status in Unity: Fix Released Status in Unity 7.2 series: In Progress Status in “unity” package in Ubuntu: Fix Released Bug description: [Inpact] The shortcut overlay window listes some truncated keybindings and descriptions although there's enough horizontal space to show them all. [Test case] The test case for this bug depends a lot on the locale used and thus there's not an universal way to verify it, this is generally valid for English locale but should apply to others as well: 1. In Unity Control Center - Appearance - Behavior enable the workspaces 2. Hold down the super key unless the shortcut overlay window is not show (if it's supported, minimum resolution is 1366x768) 3. Both the keybindings and the descriptions should not be ellipsised if there's enough horizontal space to present them, for example the Super + Alt + Cursor ke.. keybinding should be instead Super + Alt + Cursor keys [Regression potential] The view might be too large in some locales and thus not to show at all, although we should generally handle this as it used to be before. -- When I hold down Super I get a popup image detailing the shortcut keys. There are a few issues with this image which I have filed as separate bugs. Workspaces Text too long to fit. I see Super + Alt + Cursor ke.. Which I presume should say Cursor keys To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/924840/+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 1317348] Re: Switcher (Alt-Tab) does not respect monitor-defined scaling factor
** Changed in: unity (Ubuntu) Assignee: (unassigned) = Marco Trevisan (Treviño) (3v1n0) -- 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/1317348 Title: Switcher (Alt-Tab) does not respect monitor-defined scaling factor Status in Unity: Fix Released Status in Unity 7.2 series: In Progress Status in “unity” package in Ubuntu: Fix Released Bug description: [Impact] Unity switcher doesn't get properly scaled on HiDPI monitors. [Test case] 1. From Unity Control Center - Displays - Change the monitor scaling to somewhat different from 1.0 (might be both bigger and smaller, your choice). 2. Open some windows and press Alt+Tab 3. Both Switcher icons, application names and spreaded windows (when pressing down, or right-clicking on an icon) decorations should be scaled to match the selected scaling factor. [Regression potential] The potential of regression is basically none, since we just moved from fixed sizes to relative sizes and unless the scale value is set to an invalid value, this should work as it happens in other unity views that do support scaling currently. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1317348/+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 1317348] Re: Switcher (Alt-Tab) does not respect monitor-defined scaling factor
** Description changed: + [Impact] Unity switcher doesn't get properly scaled on HiDPI monitors. + + [Test case] + 1. From Unity Control Center - Displays - Change the monitor scaling to somewhat +different from 1.0 (might be both bigger and smaller, your choice). + 2. Open some windows and press Alt+Tab + 3. Both Switcher icons, application names and spreaded windows (when pressing down, or +right-clicking on an icon) decorations should be scaled to match the selected +scaling factor. + + [Regression potential] + The potential of regression is basically none, since we just moved from fixed sizes to relative sizes and unless the scale value is set to an invalid value, this should work as it happens in other unity views that do support scaling currently. -- 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/1317348 Title: Switcher (Alt-Tab) does not respect monitor-defined scaling factor Status in Unity: Fix Released Status in Unity 7.2 series: In Progress Status in “unity” package in Ubuntu: Fix Released Bug description: [Impact] Unity switcher doesn't get properly scaled on HiDPI monitors. [Test case] 1. From Unity Control Center - Displays - Change the monitor scaling to somewhat different from 1.0 (might be both bigger and smaller, your choice). 2. Open some windows and press Alt+Tab 3. Both Switcher icons, application names and spreaded windows (when pressing down, or right-clicking on an icon) decorations should be scaled to match the selected scaling factor. In Multi-monitor scenario it should match the scaling factor of the monitor where the view opens (so where the mouse is). [Regression potential]The potential of regression is basically none, since we just moved from fixed sizes to relative sizes and unless the scale value is set to an invalid value, this should work as it happens in other unity views that do support scaling currently. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1317348/+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 1317356] Re: Shortcut hint does not respect monitor scaling factor
** Description changed: + [Impact] The shortcut hint is not properly scaled in HiDPI monitors + + [Test case] + 1. From Unity Control Center - Displays - Change the monitor scaling to somewhat +different from 1.0 (might be both bigger and smaller, your choice; but scaling down is +recommended if your monitor has a small resolution or next point will fail). + 2. Hold Super and keep it pressed unless the shortcut hint won't show up +(note: this might not happen if the monitor resolution is not big enough to contain +all the shortcuts; see point above) + 3. The shortcuts view and all its text should be scaled to match the defined monitor +scaling factor. +In Multi-monitor scenario it should match the scaling factor of the monitor where the +view opens (so where the mouse is). + + + [Regression potential]The potential of regression is basically none, since we just moved from fixed sizes to relative sizes and unless the scale value is set to an invalid value, this should work as it happens in other unity views that do support scaling currently. ** Description changed: [Impact] The shortcut hint is not properly scaled in HiDPI monitors [Test case] 1. From Unity Control Center - Displays - Change the monitor scaling to somewhat -different from 1.0 (might be both bigger and smaller, your choice; but scaling down is -recommended if your monitor has a small resolution or next point will fail). + different from 1.0 (might be both bigger and smaller, your choice; but scaling down is + recommended if your monitor has a small resolution or next point will fail). 2. Hold Super and keep it pressed unless the shortcut hint won't show up -(note: this might not happen if the monitor resolution is not big enough to contain -all the shortcuts; see point above) + (note: this might not happen if the monitor resolution is not big enough to contain + all the shortcuts; see point above) 3. The shortcuts view and all its text should be scaled to match the defined monitor -scaling factor. -In Multi-monitor scenario it should match the scaling factor of the monitor where the -view opens (so where the mouse is). + scaling factor. + In Multi-monitor scenario it should match the scaling factor of the monitor where the + view opens (so where the mouse is). - - [Regression potential]The potential of regression is basically none, since we just moved from fixed sizes to relative sizes and unless the scale value is set to an invalid value, this should work as it happens in other unity views that do support scaling currently. + [Regression potential] + The potential of regression is basically none, since we just moved from fixed sizes to relative sizes and unless the scale value is set to an invalid value, this should work as it happens in other unity views that do support scaling currently. -- 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/1317356 Title: Shortcut hint does not respect monitor scaling factor Status in Unity: Fix Released Status in Unity 7.2 series: In Progress Status in “unity” package in Ubuntu: Fix Released Bug description: [Impact] The shortcut hint is not properly scaled in HiDPI monitors [Test case] 1. From Unity Control Center - Displays - Change the monitor scaling to somewhat different from 1.0 (might be both bigger and smaller, your choice; but scaling down is recommended if your monitor has a small resolution or next point will fail). 2. Hold Super and keep it pressed unless the shortcut hint won't show up (note: this might not happen if the monitor resolution is not big enough to contain all the shortcuts; see point above) 3. The shortcuts view and all its text should be scaled to match the defined monitor scaling factor. In Multi-monitor scenario it should match the scaling factor of the monitor where the view opens (so where the mouse is). [Regression potential] The potential of regression is basically none, since we just moved from fixed sizes to relative sizes and unless the scale value is set to an invalid value, this should work as it happens in other unity views that do support scaling currently. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1317356/+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 1317348] Re: Switcher (Alt-Tab) does not respect monitor-defined scaling factor
** Description changed: [Impact] Unity switcher doesn't get properly scaled on HiDPI monitors. [Test case] 1. From Unity Control Center - Displays - Change the monitor scaling to somewhat -different from 1.0 (might be both bigger and smaller, your choice). + different from 1.0 (might be both bigger and smaller, your choice). 2. Open some windows and press Alt+Tab 3. Both Switcher icons, application names and spreaded windows (when pressing down, or -right-clicking on an icon) decorations should be scaled to match the selected -scaling factor. + right-clicking on an icon) decorations should be scaled to match the selected + scaling factor. +In Multi-monitor scenario it should match the scaling factor of the monitor where the +view opens (so where the mouse is). - [Regression potential] - The potential of regression is basically none, since we just moved from fixed sizes to relative sizes and unless the scale value is set to an invalid value, this should work as it happens in other unity views that do support scaling currently. + [Regression potential]The potential of regression is basically none, + since we just moved from fixed sizes to relative sizes and unless the + scale value is set to an invalid value, this should work as it happens + in other unity views that do support scaling currently. -- 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/1317348 Title: Switcher (Alt-Tab) does not respect monitor-defined scaling factor Status in Unity: Fix Released Status in Unity 7.2 series: In Progress Status in “unity” package in Ubuntu: Fix Released Bug description: [Impact] Unity switcher doesn't get properly scaled on HiDPI monitors. [Test case] 1. From Unity Control Center - Displays - Change the monitor scaling to somewhat different from 1.0 (might be both bigger and smaller, your choice). 2. Open some windows and press Alt+Tab 3. Both Switcher icons, application names and spreaded windows (when pressing down, or right-clicking on an icon) decorations should be scaled to match the selected scaling factor. In Multi-monitor scenario it should match the scaling factor of the monitor where the view opens (so where the mouse is). [Regression potential]The potential of regression is basically none, since we just moved from fixed sizes to relative sizes and unless the scale value is set to an invalid value, this should work as it happens in other unity views that do support scaling currently. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1317348/+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 1317869] Re: Keyboard shortcuts overlay does not show up when workspaces are enabled at 1366x768
** Description changed: + [Impact] + The shortcut hint is not shown when workspaces are enabled in displays with 1366x768 resolution. + + [Test case] + 1. Run unity in a monitor with 1366x768 resolution. + 2. From Unity Control Center - Appearance - Behavior - enable the workspaces + 3. Hold Super and keep it pressed, the shortcut should show up + + [Regression potential] + The potential of regression is basically none, we just resized the view to make sure there's enough space for showing in smaller resolutions. + + + My notebook has a 1366x768 screen - it is a very common screen resolution. When I boot Ubuntu 14.04 liveISO the keyboard shortcuts overlay is displayed and works very well - therefore my screen resolution is large enough for it. But after I installed 14.04 on my hard disk, the shortcuts overlay does not show anymore. The attachment is a screenshot of the shortcuts overlay working on the liveISO. -- 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/1317869 Title: Keyboard shortcuts overlay does not show up when workspaces are enabled at 1366x768 Status in Unity: Fix Released Status in Unity 7.2 series: In Progress Status in “unity” package in Ubuntu: Fix Released Bug description: [Impact] The shortcut hint is not shown when workspaces are enabled in displays with 1366x768 resolution. [Test case] 1. Run unity in a monitor with 1366x768 resolution. 2. From Unity Control Center - Appearance - Behavior - enable the workspaces 3. Hold Super and keep it pressed, the shortcut should show up [Regression potential] The potential of regression is basically none, we just resized the view to make sure there's enough space for showing in smaller resolutions. My notebook has a 1366x768 screen - it is a very common screen resolution. When I boot Ubuntu 14.04 liveISO the keyboard shortcuts overlay is displayed and works very well - therefore my screen resolution is large enough for it. But after I installed 14.04 on my hard disk, the shortcuts overlay does not show anymore. The attachment is a screenshot of the shortcuts overlay working on the liveISO. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1317869/+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 1318997] Re: Provide a way to change alarm sound
** Changed in: indicator-datetime Status: Fix Committed = 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/1318997 Title: Provide a way to change alarm sound Status in The Date and Time Indicator: Fix Released Status in Clock application for Ubuntu devices: New Status in Ubuntu Clock App reboot series: In Progress Status in Ubuntu UX bugs: New Status in “indicator-datetime” package in Ubuntu: Fix Released Bug description: The alarms API provides to way to set different alarm sounds for every alarm. Let's provide that feature to the users so that they can change the alarm sound while creating an alarm. To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-datetime/+bug/1318997/+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 1324580] Re: alarm will only ring for a minute and stop whether or not the user interacted with it
** Branch linked: lp:~charlesk/indicator-datetime/lp-1324580-set-snap- decision-timeout -- 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/1324580 Title: alarm will only ring for a minute and stop whether or not the user interacted with it Status in Clock application for Ubuntu devices: Confirmed Status in Ubuntu Clock App reboot series: Confirmed Status in “indicator-datetime” package in Ubuntu: Triaged Bug description: When an alarm goes off, it will ring for only a minute and after that, whether or not the user disabled it, it stays quiet forever more. It would be interesting adding a second or even third ring after the first if the alarm was not properly disabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-clock-app/+bug/1324580/+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 1329089] Re: g++-4.9 binary incompatibilities with libraries built with g++-4.8
** Also affects: mir/0.4 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/1329089 Title: g++-4.9 binary incompatibilities with libraries built with g++-4.8 Status in Mir: Fix Committed Status in Mir 0.4 series: New Status in “dbus-cpp” package in Ubuntu: In Progress Status in “firefox” package in Ubuntu: New Status in “gcc-4.9” package in Ubuntu: Confirmed Status in “gcc-defaults” package in Ubuntu: Fix Released Status in “location-service” package in Ubuntu: Invalid Status in “mir” package in Ubuntu: Triaged Status in “process-cpp” package in Ubuntu: Invalid Status in “qtbase-opensource-src” package in Ubuntu: New Status in “unity” package in Ubuntu: New Status in “unity-scope-click” package in Ubuntu: New Status in “unity-scopes-api” package in Ubuntu: New Status in “unity-scopes-shell” package in Ubuntu: New Status in Debian GNU/Linux: New Bug description: The location-service 0.0.3+14.10.20140512-0ubuntu1 package in utopic, when rebuilt against libdbus-cpp3 3.0.0+14.10.20140604-0ubuntu1 (built with gcc-4.8) and with current gcc-defaults (which makes g++-4.9 the default), fails the package build in its test suite. 2/14 Test #2: acceptance_tests ..***Failed 30.54 sec DBus daemon: unix:abstract=/tmp/dbus-HdW1T5UHNB,guid=188551aa5d797b663dade1425398d71b task-0: Started with PID: 13031 task-0: [==] Running 2 tests from 1 test case. task-0: [--] Global test environment set-up. task-0: [--] 2 tests from LocationServiceStandalone task-0: [ RUN ] LocationServiceStandalone.SessionsReceiveUpdatesViaDBus ** (dbus-test-runner:13025): WARNING **: Timing out at maximum wait of 30 seconds. (dbus-test-runner:13025): libdbustest-CRITICAL **: dbus_test_service_run: assertion 'all_tasks(service, all_tasks_finished_helper)' failed task-0: Shutting down DBus daemon: Shutdown This test suite does *not* fail if either dbus-cpp is rebuilt with g++-4.9, or if location-service is built with g++-4.8. This implies a binary compatibility problem for C++ libraries in g++ 4.9, which is critical to resolve. To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1329089/+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 1318683] Re: I couldn't set different time zones from system settings or indicator applet complete
[Expired for indicator-datetime (Ubuntu) because there has been no activity for 60 days.] ** Changed in: indicator-datetime (Ubuntu) Status: Incomplete = Expired -- 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/1318683 Title: I couldn't set different time zones from system settings or indicator applet complete Status in “indicator-datetime” package in Ubuntu: Expired Bug description: I couldn't set different time zones from system settings or indicator applet complete I can set different locations when I add clock to my panel, but from system settings there is no clock settings. also, I couldn't set time zones (locations) on indicator applet complete! ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: gnome-session-fallback 3.2.1-0ubuntu8 ProcVersionSignature: Ubuntu 3.11.0-20.35~precise1-generic 3.11.10.6 Uname: Linux 3.11.0-20-generic x86_64 ApportVersion: 2.0.1-0ubuntu17.6 Architecture: amd64 Date: Mon May 12 17:26:09 2014 InstallationMedia: Ubuntu 12.04.4 LTS Precise Pangolin - Release amd64 (20140204) MarkForUpload: True PackageArchitecture: all ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-session UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1318683/+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 1324580] Re: alarm will only ring for a minute and stop whether or not the user interacted with it
** Changed in: indicator-datetime (Ubuntu) Status: Triaged = In Progress -- 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/1324580 Title: alarm will only ring for a minute and stop whether or not the user interacted with it Status in Clock application for Ubuntu devices: Confirmed Status in Ubuntu Clock App reboot series: Confirmed Status in “indicator-datetime” package in Ubuntu: In Progress Bug description: When an alarm goes off, it will ring for only a minute and after that, whether or not the user disabled it, it stays quiet forever more. It would be interesting adding a second or even third ring after the first if the alarm was not properly disabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-clock-app/+bug/1324580/+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
