[Dx-packages] [Bug 1767468] Re: Upgrade from 16.04 to 18.04, then uninstalling unity disables hardware acceleration
*** This bug is a duplicate of bug 1768610 *** https://bugs.launchpad.net/bugs/1768610 I had these exact same symptoms today with my nVidia GTX 960 after doing a platform upgrade from 17.10 to 18.04. Issue was actually dead simple to fix, the upgrade to 18.04 removed some PPAs (including the graphics drivers), so although the nVidia driver package was present on the system it wasn't getting updates and the system appears to have selected a software only driver to use instead. All I did was uninstall nvidia-390 using apt, re-added the ppa, apt-get updated, then reinstalled nvidia-390 again using apt. Fixed it fine for me. ### sudo apt-get autoremove nvidia-390 sudo add-apt-repository ppa:graphics-drivers/ppa sudo apt-get update sudo apt-get install nvidia-390 ### hope this is useful :) -- 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/1767468 Title: Upgrade from 16.04 to 18.04, then uninstalling unity disables hardware acceleration Status in nux package in Ubuntu: Confirmed Bug description: After upgrading from 16.04 to 18.04 on a very plain Intel Skylake graphics, hardware acceleration is gone. Glxinfo and System Information report 'llvmpipe' (software rasterizer) It is caused by the file /etc/X11/Xsession.d/50_check_unity_support which can be deleted and then this problem goes away. Apparently the problem is that nux-tools is not purged, leaving the above file (also see #1768610). > 00:02.0 VGA compatible controller: Intel Corporation HD Graphics 520 (rev 07) ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: libglvnd0 1.0.0-2ubuntu2 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Apr 27 20:24:48 2018 Dependencies: gcc-8-base 8-20180414-1ubuntu2 libc6 2.27-3ubuntu1 libgcc1 1:8-20180414-1ubuntu2 EcryptfsInUse: Yes InstallationDate: Installed on 2016-04-21 (735 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) SourcePackage: libglvnd UpgradeStatus: Upgraded to bionic on 2018-04-26 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nux/+bug/1767468/+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 1295267] Re: Windows change Monitor/Desktop after screen lock
Below is a fix/workaround/solution that might work for some who are visiting this thread. Short version: Stop using external video adapters and instead use the natively supported connections. Medium version: Ubuntu 14.04 _AND_ 16.04. My problem started when I started using a external video adapter (hpk-481409-001 Displayport to DVI). It was solved by ceasing to use the video adapter and instead using the native connections of both the monitor and PC. Long version: I was running 14.04 on an HP Elitedesk 800 workstation with 2 Display ports and 1 VGA port. I changed monitors and needed to start using an adapter for one of them since they only supported DVI input, the display ports on the PC were internally connected in parallel, and the Display port to DVI cables that I had only mapped the first channel. When the problem started, I thought that it was an Ubuntu update issue and it would resolve itself. I later upgraded from 14.04 to 16.04 and the problem persisted. I tried switching to a heterogeneous monitor configuration like I had before the monitor change, because I thought that it might be a monitor-name identification issue, however this did not fix the problem. I tried using a VGA/Displayport combination (luckily for those reading this I, for some reason, kept the displayport-DVI-adapter connection), and that didn't solve the problem. Then, I simply replaced the displayport-DVI-adapter connection with a simple displayport-DVI cable, and I do not see the problem anymore. If it pops up again I will provide an update. -- You received this bug notification because you are a member of DX Packages, which is subscribed to compiz-plugins-main in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1295267 Title: Windows change Monitor/Desktop after screen lock Status in Unity: Fix Released Status in Unity 7.1 series: Fix Released Status in compiz-plugins-main package in Ubuntu: Fix Released Status in unity package in Ubuntu: Triaged Bug description: I run a dual monitor configuration, with one portrait and one landscape. I nearly always have multiple applications open in multiple windows across both monitors and all virtual desktops. When I lock the screen and then unlock, my application windows will move from their original position. Sometimes they are in completely random positions; Other times they seem to get the monitors confused, and rather than being in the top half of the portrait monitor they are on the top half of the landscape monitor; Sometimes it is only a new desktop, but the monitor position is the same; Sometimes it is the same desktop, but on the other monitor. Description: Ubuntu 13.10 Release: 13.10 What I expect to happen: When I unlock my computer, all the windows are in the same position on the same monitor and desktop as I left them. What actually happens: When I unlock my computer, some or all of the windows have been changed to a random position on a random monitor and/or desktop. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1295267/+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 987060] Re: massive memory leak in unity-panel-service and hud-service when invoking the hud on Firefox profiles with large amounts of bookmarks LTS 12.04 14.04
16.10 have unity-panel-service taking up 3.5 GB of RAM. I've mainly noticed it after resume, as Firefox randomly begins to crash/freeze before the entire system becomes unstable. -- 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/987060 Title: massive memory leak in unity-panel-service and hud-service when invoking the hud on Firefox profiles with large amounts of bookmarks LTS 12.04 14.04 Status in Unity HUD: Confirmed Status in Application Menu Indicator: Confirmed Status in Unity: Won't Fix Status in firefox package in Ubuntu: Incomplete Status in hud package in Ubuntu: Confirmed Status in unity package in Ubuntu: Invalid Status in firefox source package in Xenial: Incomplete Status in hud source package in Xenial: Confirmed Status in unity source package in Xenial: Invalid Bug description: unity-panel-service and hud-service quickly racks up memory and CPU usage until I kill it when invoking the HUD on Firefox. It's taking anywhere from a few minutes to half an hour, but it sometimes makes the system completely unusable. 1. run Firefox 12.0 in the foreground 2. hit Alt to bring up HUD 3. type any text 4. select one proposal from HUD 5. wait for unity-panel-service and hud-service to fill up the remaining RAM and swap space. This is due to a high number of bookmarks in a user profile (hundreds). To manage notifications about this bug go to: https://bugs.launchpad.net/hud/+bug/987060/+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 1390625] Re: mouse cursor gets corrupted
Same here, #51 works for me -- 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/1390625 Title: mouse cursor gets corrupted Status in elementary OS: Confirmed Status in Mesa: New Status in Unity: Invalid Status in unity package in Ubuntu: Invalid Status in xorg-lts-utopic package in Ubuntu: Confirmed Bug description: In Ubuntu 14.10, the mouse cursor graphic gets corrupted under certain occasions. It then looks flipped, sheared or shows fragments of a previous cursor. * when switching the cursor them forth and back in Gnome Tweak Tool * when drag&dropping a document icon Maybe related, the cursor does not always show the correct image scale on a high-dpi display (this was working right in 14.04). For example after login, or when hovering specific areas, or on mouse down to start a drag&drop, the cursor appears 1/4 the expected size. Attached is a photo of a corrupted cursor (whereas a screenshot with Gimp showed the uncorrupted cursor). ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: unity 7.3.1+14.10.20141016-0ubuntu1 ProcVersionSignature: Ubuntu 3.16.0-24.32-generic 3.16.4 Uname: Linux 3.16.0-24-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 BootLog: * Setting up X socket directories... [400G [394G[ OK ] CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Fri Nov 7 22:12:52 2014 DistUpgraded: 2014-11-04 18:35:56,188 DEBUG enabling apt cron job DistroCodename: utopic DistroVariant: ubuntu EcryptfsInUse: Yes GraphicsCard: Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:3978] InstallationDate: Installed on 2014-02-02 (278 days ago) InstallationMedia: Ubuntu-GNOME 14.04 "Trusty Tahr" - Alpha amd64 (20140201) MachineType: LENOVO 20266 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-24-generic.efi.signed root=UUID=4bfb3686-b9f7-487d-81f6-eceb41097ad9 ro quiet splash acpi_backlight=vendor SourcePackage: unity UpgradeStatus: Upgraded to utopic on 2014-11-04 (3 days ago) dmi.bios.date: 10/31/2013 dmi.bios.vendor: LENOVO dmi.bios.version: 76CN31WW dmi.board.asset.tag: No Asset Tag dmi.board.name: Yoga2 dmi.board.vendor: LENOVO dmi.board.version: 31900058STD dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Yoga 2 Pro dmi.modalias: dmi:bvnLENOVO:bvr76CN31WW:bd10/31/2013:svnLENOVO:pn20266:pvrLenovoYoga2Pro:rvnLENOVO:rnYoga2:rvr31900058STD:cvnLENOVO:ct10:cvrLenovoYoga2Pro: dmi.product.name: 20266 dmi.product.version: Lenovo Yoga 2 Pro dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.12+14.10.20140918-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.56-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.3.0-0ubuntu3 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.3.0-0ubuntu3 version.xserver-xorg-core: xserver-xorg-core 2:1.16.0-1ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.4.0-2ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.914-1~exp1ubuntu4 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu2 xserver.bootTime: Fri Nov 7 14:54:59 2014 xserver.configfile: /etc/X11/xorg.conf xserver.errors: [dix] ELAN Touchscreen: unable to find touch point 1 xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 16970 vendor SDC xserver.version: 2:1.16.0-1ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/elementaryos/+bug/1390625/+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 1463243] [NEW] 20KB write to ~/.config/dconf/user on caps lock or num lock
Public bug reported: Whenever I press Caps Lock or Num Lock, a 20KB ~/.config/dconf/user file is written. Someone else already reported this in a question with more details:: https://answers.launchpad.net/ubuntu/+source/d-conf/+question/178204 Ubuntu MATE 15.04 64-bit Linux 3.19.0-18-generic #18-Ubuntu SMP Tue May 19 18:31:35 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux dconf 0.22.0-1 ** Affects: d-conf (Ubuntu) Importance: Undecided Status: New ** Description changed: Whenever I press Caps Lock or Num Lock, a 20KB ~/.config/dconf/user file is written. Someone else already reported this in a question with more details:: https://answers.launchpad.net/ubuntu/+source/d-conf/+question/178204 + + Ubuntu MATE 15.04 64-bit + Linux 3.19.0-18-generic #18-Ubuntu SMP Tue May 19 18:31:35 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux + + dconf 0.22.0-1 -- You received this bug notification because you are a member of DX Packages, which is subscribed to d-conf in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1463243 Title: 20KB write to ~/.config/dconf/user on caps lock or num lock Status in d-conf package in Ubuntu: New Bug description: Whenever I press Caps Lock or Num Lock, a 20KB ~/.config/dconf/user file is written. Someone else already reported this in a question with more details:: https://answers.launchpad.net/ubuntu/+source/d-conf/+question/178204 Ubuntu MATE 15.04 64-bit Linux 3.19.0-18-generic #18-Ubuntu SMP Tue May 19 18:31:35 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux dconf 0.22.0-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/d-conf/+bug/1463243/+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 160311] Re: Resizing windows by grabbing window borders is difficult
Here's a video recording of why 1-pixel grab bars are frustrating: https://www.youtube.com/watch?v=OeOldGSrsOg -- 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/160311 Title: Resizing windows by grabbing window borders is difficult Status in Ayatana Design: Fix Released Status in Decorator for compiz-fusion: New Status in One Hundred Papercuts: Fix Released Status in The Metacity Window Manager: In Progress Status in Ubuntu MATE: New Status in Release Notes for Ubuntu: Fix Released Status in Unity: Fix Released Status in Unity 2D: Invalid Status in light-themes package in Ubuntu: Fix Released Status in unity package in Ubuntu: Confirmed Bug description: This bug is fixed in unity-3d since ubuntu 11.04. It still exists in unity-2d and will never be fixed as unity-2d is no longer supported since ubuntu 12.10 (see comment #343). * This should mostly be fixed for Natty and might get backported to earlier releases as well. For Precise (12.04) this is again broken for unity-2d (as of 17.7.2012 unity-2d 5.12.0-0ubuntu1.1). Note that if the window has a scrollbar, you can grab that to resize the window. If not, you are stuck with the 1px border. Workaround: NONE KNOWN (see comment 320)? * *Blueprint for Natty, Ubuntu 11.04: https://blueprints.edge.launchpad.net/ubuntu/+spec/packageselection- dx-n-resizing-windows Work items1 * Make sure the new resize grip fits in current applications; doesn't interfere with anything. We should make some noise about this during the Natty cycle so people keep their eyes open and file bugs. 2 * Invisible window resize area - around 3px invisible area to allow resize on all sides. * Working grip backported to gtk2 already available in ppa : https://launchpad.net/~bratsche/+archive/gtk * Workaround for Compiz/Unity: Alt+Middlemousebutton resizes a window most comfortably. Workaround: Edit /usr/share/themes/Ambiance/metacity-1/metacity- theme-1.xml. Set the following values in frame_geometry_normal as desired: Binary package hint: metacity - The issue has been an issue for users (especially of large) screens for several releases- Trackpad users seem to be particularly impacted by this- The issue appears to have been significantly aggravated in Lucid by changing the border width from 3 pixels to 1 pixel The window borders in metacity are far too thin to be used for comfortable window resizing, and resize handles are not available in all applications (or even most). In fact, of all the windows I have open right now, not a single one of them has a resize handle. The result is that I get a lot of "misses" when I try to drag a window border, which usually results in my clicking on the wrong window altogether. The best fix for this usability bug is to create an "invisible" region around each non-maximized window about 4px thick that can be used for resizing (in addition to the visible border). Or perhaps there should be a border thickness option on the System > Preferences > Windows dialog (although the default thickness should still be increased considerably). Ideally all windows would also have a resize handle but I realize that these have to be application controlled (at least that seems to be the position of the metacity team). To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/160311/+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 160311] Re: Resizing windows by grabbing window borders is difficult
Adding ubuntu-mate, as its window manager also suffers from 1-pixel wide resize grab areas. This is one of the most immediately frustrating issues of any window manager, and it only gets worse as display pixel densities increase. ** Also affects: ubuntu-mate 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/160311 Title: Resizing windows by grabbing window borders is difficult Status in Ayatana Design: Fix Released Status in Decorator for compiz-fusion: New Status in One Hundred Papercuts: Fix Released Status in The Metacity Window Manager: In Progress Status in Ubuntu MATE: New Status in Release Notes for Ubuntu: Fix Released Status in Unity: Fix Released Status in Unity 2D: Invalid Status in light-themes package in Ubuntu: Fix Released Status in unity package in Ubuntu: Confirmed Bug description: This bug is fixed in unity-3d since ubuntu 11.04. It still exists in unity-2d and will never be fixed as unity-2d is no longer supported since ubuntu 12.10 (see comment #343). * This should mostly be fixed for Natty and might get backported to earlier releases as well. For Precise (12.04) this is again broken for unity-2d (as of 17.7.2012 unity-2d 5.12.0-0ubuntu1.1). Note that if the window has a scrollbar, you can grab that to resize the window. If not, you are stuck with the 1px border. Workaround: NONE KNOWN (see comment 320)? * *Blueprint for Natty, Ubuntu 11.04: https://blueprints.edge.launchpad.net/ubuntu/+spec/packageselection- dx-n-resizing-windows Work items1 * Make sure the new resize grip fits in current applications; doesn't interfere with anything. We should make some noise about this during the Natty cycle so people keep their eyes open and file bugs. 2 * Invisible window resize area - around 3px invisible area to allow resize on all sides. * Working grip backported to gtk2 already available in ppa : https://launchpad.net/~bratsche/+archive/gtk * Workaround for Compiz/Unity: Alt+Middlemousebutton resizes a window most comfortably. Workaround: Edit /usr/share/themes/Ambiance/metacity-1/metacity- theme-1.xml. Set the following values in frame_geometry_normal as desired: Binary package hint: metacity - The issue has been an issue for users (especially of large) screens for several releases- Trackpad users seem to be particularly impacted by this- The issue appears to have been significantly aggravated in Lucid by changing the border width from 3 pixels to 1 pixel The window borders in metacity are far too thin to be used for comfortable window resizing, and resize handles are not available in all applications (or even most). In fact, of all the windows I have open right now, not a single one of them has a resize handle. The result is that I get a lot of "misses" when I try to drag a window border, which usually results in my clicking on the wrong window altogether. The best fix for this usability bug is to create an "invisible" region around each non-maximized window about 4px thick that can be used for resizing (in addition to the visible border). Or perhaps there should be a border thickness option on the System > Preferences > Windows dialog (although the default thickness should still be increased considerably). Ideally all windows would also have a resize handle but I realize that these have to be application controlled (at least that seems to be the position of the metacity team). To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/160311/+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 1397587] [NEW] Volume display does not update when changing default sink
Public bug reported: On my laptop I often have two PulseAudio sinks, the on-board audio (alsa_output.pci-_00_1b.0.analog-stereo) and a Bluetooth speaker (bluez_sink.8C_DE_52_2F_AF_F3). I can choose the default destination for sound output using the "Sound" pane of System Settings, and I can separately change the volume setting of each sink using the "paman" application. When I adjust the volume using the sound menu, it affects the default sink. However, when I change to a different default sink, the sound menu does not update and continues displaying the volume for the previously-selected sink. Only if I change the volume setting for one of the sinks (e.g. using paman) does the sound menu update to show the new volume level. To reproduce: Find a system with more than one sound sink. Launch paman and open the Properties window for each sink. Also open the Sound pane of System Settings. Set one sink to maximum volume and one to minumum. Switch between outputs using Systems Settings, and note that the sound menu does not update to match the different volume settings of the two sinks. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: indicator-sound 12.10.2+14.04.20140401-0ubuntu1 ProcVersionSignature: Ubuntu 3.16.0-25.33~14.04.2-generic 3.16.7 Uname: Linux 3.16.0-25-generic i686 ApportVersion: 2.14.1-0ubuntu3.5 Architecture: i386 CurrentDesktop: Unity Date: Sat Nov 29 19:10:52 2014 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-motts-20100121-3 EcryptfsInUse: Yes InstallationDate: Installed on 2010-06-09 (1634 days ago) InstallationMedia: Ubuntu GNU/Linux 9.10 "Karmic" - Build i386 LIVE Binary 20100121-21:52 SourcePackage: indicator-sound UpgradeStatus: Upgraded to trusty on 2014-08-15 (105 days ago) ** Affects: indicator-sound (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 trusty -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-sound in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1397587 Title: Volume display does not update when changing default sink Status in indicator-sound package in Ubuntu: New Bug description: On my laptop I often have two PulseAudio sinks, the on-board audio (alsa_output.pci-_00_1b.0.analog-stereo) and a Bluetooth speaker (bluez_sink.8C_DE_52_2F_AF_F3). I can choose the default destination for sound output using the "Sound" pane of System Settings, and I can separately change the volume setting of each sink using the "paman" application. When I adjust the volume using the sound menu, it affects the default sink. However, when I change to a different default sink, the sound menu does not update and continues displaying the volume for the previously-selected sink. Only if I change the volume setting for one of the sinks (e.g. using paman) does the sound menu update to show the new volume level. To reproduce: Find a system with more than one sound sink. Launch paman and open the Properties window for each sink. Also open the Sound pane of System Settings. Set one sink to maximum volume and one to minumum. Switch between outputs using Systems Settings, and note that the sound menu does not update to match the different volume settings of the two sinks. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: indicator-sound 12.10.2+14.04.20140401-0ubuntu1 ProcVersionSignature: Ubuntu 3.16.0-25.33~14.04.2-generic 3.16.7 Uname: Linux 3.16.0-25-generic i686 ApportVersion: 2.14.1-0ubuntu3.5 Architecture: i386 CurrentDesktop: Unity Date: Sat Nov 29 19:10:52 2014 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-motts-20100121-3 EcryptfsInUse: Yes InstallationDate: Installed on 2010-06-09 (1634 days ago) InstallationMedia: Ubuntu GNU/Linux 9.10 "Karmic" - Build i386 LIVE Binary 20100121-21:52 SourcePackage: indicator-sound UpgradeStatus: Upgraded to trusty on 2014-08-15 (105 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-sound/+bug/1397587/+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
Sorry, one more thing... I think the correct matepackage is ubuntu- gnome-desktop -- 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: Fix Committed Status in Unity 7.2 series: In Progress Status in “unity” package in Ubuntu: Fix Released 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 1311316] Re: After locking screen there is no input field to type password for unlock
Here's an article with screenshots of how to actually find the icon that lets you choose your "shell": http://www.howtogeek.com/112620/how-to-install-use-gnome-shell-on-ubuntu/ -- 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: Fix Committed Status in Unity 7.2 series: In Progress Status in “unity” package in Ubuntu: Fix Released 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 1311316] Re: After locking screen there is no input field to type password for unlock
I have a workaround for this, use Gnome instead of Unity. It took me a while to realize/figure out that it's pretty painless to just run a different window manager on Ubuntu. I did look at maybe switching to a different lock screen but there was no straightforward way to do that. It turns out you just use apt to install gnome-shell and then from the login screen you have the option to run Gnome instead of Unity (click the little icon on that line with your name when you're logging in to select the window manager you want). The bug makes Unity so inconvenient to use that I was considering switching to another Linux distribution. I don't see any downside to switching to Gnome so far, so this seems like a reasonable workaround until the problem is resolved. Or maybe forever, I don't care about Gnome vs. Unity and Gnome seems to work just fine. -- 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: Fix Committed Status in Unity 7.2 series: In Progress Status in “unity” package in Ubuntu: Fix Released 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 1311316] Re: After locking screen there is no input field to type password for unlock
I've also seen this problem where the input field is missing on one monitor, but not on the other. -- 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: Triaged 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 1332947] Re: HDPI: unity randomly turns on large text in universal access
as of the latest updates published about 2014-09-03, this now happens after every reboot. It used to be just after an update, then you'd turn off large text, and it would be fine. Now, every time I reboot, it turns itself back on. I tried adding /home/ben/.config/autostart/largetextfix.desktop but that did not fix 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/1332947 Title: HDPI: unity randomly turns on large text in universal access Status in Unity: Triaged Status in Unity 7.2 series: Triaged Status in “unity” package in Ubuntu: Triaged Bug description: I have a macbook pro with retina display. In Ubuntu 14.04 64bit, every couple of reboots, the 'large text' option in Universal Access gets switched on upon login. It happens in roughly 1 out of 5 reboots for 1 or more users on the computer. It appears to happen to people with small HighDPI screens. In my case, it's 13 inch at 2560x1600. Another example is 13 inch at 1080p - http://askubuntu.com/questions/453785/large-text-button-in-universal-access-turns-itself-on-after-reboot-ubuntu-14-0 unity: Installed: 7.2.1+14.04.20140513-0ubuntu2 Candidate: 7.2.1+14.04.20140513-0ubuntu2 Version table: *** 7.2.1+14.04.20140513-0ubuntu2 0 500 http://sk.archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 Packages 100 /var/lib/dpkg/status 7.2.0+14.04.20140423-0ubuntu1.2 0 500 http://security.ubuntu.com/ubuntu/ trusty-security/main amd64 Packages 7.2.0+14.04.20140416-0ubuntu1 0 500 http://sk.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages unity-control-center: Installed: 14.04.3+14.04.20140410-0ubuntu1 Candidate: 14.04.3+14.04.20140410-0ubuntu1 Version table: *** 14.04.3+14.04.20140410-0ubuntu1 0 500 http://sk.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages 100 /var/lib/dpkg/status intel iris pro graphics (lspci -vvv): 00:02.0 VGA compatible controller: Intel Corporation Device 0a2e (rev 09) (prog-if 00 [VGA controller]) Subsystem: Apple Inc. Device 011a Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- [disabled] Capabilities: [90] MSI: Enable+ Count=1/1 Maskable- 64bit- Address: fee00018 Data: Capabilities: [d0] Power Management version 2 Flags: PMEClk- DSI+ D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-) Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME- Capabilities: [a4] PCI Advanced Features AFCap: TP+ FLR+ AFCtrl: FLR- AFStatus: TP- Kernel driver in use: i915 To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1332947/+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 998285] Re: Tapping alt-tab switches between windows of the same application sometimes
When Alt+Tab is presented as an application switcher, it MUST ACT AS AN APPLICATION SWITCHER. /steam from ears This is how I, Andreas, and I assume most people new to Unity understand the Alt+Tab and Alt+` behaviour: "Alt+Tab switches to the previously open application. Alt+` switches to the previously open windows within the current application. Multiple invocations of either will switch to the second, third, etc. most recent application / window." The behaviour you are advocating sounds something like this: "Alt+Tab switches to the previously open application. Unless your previous window* is from your current application, in which case it will switch to that. If you press Alt+Tab twice it you will switch to your second most recent application, unless your previous windows is from your current application, in which case it will switch to your most recent application, no matter what your second most recent window was. Alt+` switches to the previous window..." * Alt+Tab is an application switcher, not a window switcher. It is utterly bizarre and the cognitive load associated with tracking how many presses needed to get to each window is ridiculous (and totally unnecessary). Like Andreas, I was convinced that my setup was exhibiting some strange bug that I couldn't reproduce that caused Alt+Tab to fail on unspecified occasions. I've come here today, after years of enduring it, because it still frustrates me. This Ask Ubuntu question[1] indicates that ~16000 people are also surprised by the current behaviour. Over the years, how many of those visitors do you think saw the only viable answer "don't use Unity switcher" and had positive thoughts about Unity? It looks unpolished and lazy and I'm astounded that there is no change 2 years on, while the alternatives fall out of the defaults. (Collective) you must absolutely change the default behaviour and I implore you to make the change a top priority. [1] http://askubuntu.com/questions/133046/can-i-configure-alt-tab-to-always-switch-applications P.S. I'm sorry Marco, that it means breaking your workflow but simplicity must prevail. What you want is a window switcher, not an application switcher. Your exact workflow can remain supported through non-default settings though I put to you that unless the behaviour can be fully explained in one concise sentence, then it doesn't even deserve a place in the GUI. -- 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/998285 Title: Tapping alt-tab switches between windows of the same application sometimes Status in Unity: Won't Fix Status in “unity” package in Ubuntu: Invalid Bug description: Normally, tapping alt-tab switches between applications, and tapping alt-` switches between windows of the front-most application. However, if the two front-most windows are from the same application, then alt- tab will switch between these windows instead, instead of moving to the second-front-most application. Hence, in this case, alt-tab duplicates the action of alt-`. Here is an example: 1) create the stack with two nautilus windows at the top, e.g. Nautilus window 1 (N1), Nautilus window 2 (N2), and Firefox window (F1) (but you can use any applications). Create the stack either by [clicking F1, N2, N1] or [switching to Nautilus with alt-tab, then alt-` to the other Nautilus window]. 2) Tap alt-tab. What happens: I switch to the other nautilus window. What I expected: to switch to the other application (i.e. Firefox). ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: unity 5.12-0ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-24.37-generic 3.2.14 Uname: Linux 3.2.0-24-generic x86_64 ApportVersion: 2.0.1-0ubuntu7 Architecture: amd64 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] Date: Sat May 12 10:17:21 2012 InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012) SourcePackage: unity UpgradeStatus: Upgraded to precise on 2012-04-29 (12 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/998285/+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 1332947] Re: HDPI: unity randomly turns on large text in universal access
confirmed on Lenovo W540 20BH. happened to me a few times after installing updates and rebooting. can set the text size back to normal but my cursor size seems to be very large still. haven't tried troubleshooting the cursor yet -- 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/1332947 Title: HDPI: unity randomly turns on large text in universal access Status in Unity: Triaged Status in Unity 7.2 series: Triaged Status in “unity” package in Ubuntu: Triaged Bug description: I have a macbook pro with retina display. In Ubuntu 14.04 64bit, every couple of reboots, the 'large text' option in Universal Access gets switched on upon login. It happens in roughly 1 out of 5 reboots for 1 or more users on the computer. It appears to happen to people with small HighDPI screens. In my case, it's 13 inch at 2560x1600. Another example is 13 inch at 1080p - http://askubuntu.com/questions/453785/large-text-button-in-universal-access-turns-itself-on-after-reboot-ubuntu-14-0 unity: Installed: 7.2.1+14.04.20140513-0ubuntu2 Candidate: 7.2.1+14.04.20140513-0ubuntu2 Version table: *** 7.2.1+14.04.20140513-0ubuntu2 0 500 http://sk.archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 Packages 100 /var/lib/dpkg/status 7.2.0+14.04.20140423-0ubuntu1.2 0 500 http://security.ubuntu.com/ubuntu/ trusty-security/main amd64 Packages 7.2.0+14.04.20140416-0ubuntu1 0 500 http://sk.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages unity-control-center: Installed: 14.04.3+14.04.20140410-0ubuntu1 Candidate: 14.04.3+14.04.20140410-0ubuntu1 Version table: *** 14.04.3+14.04.20140410-0ubuntu1 0 500 http://sk.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages 100 /var/lib/dpkg/status intel iris pro graphics (lspci -vvv): 00:02.0 VGA compatible controller: Intel Corporation Device 0a2e (rev 09) (prog-if 00 [VGA controller]) Subsystem: Apple Inc. Device 011a Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- [disabled] Capabilities: [90] MSI: Enable+ Count=1/1 Maskable- 64bit- Address: fee00018 Data: Capabilities: [d0] Power Management version 2 Flags: PMEClk- DSI+ D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-) Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME- Capabilities: [a4] PCI Advanced Features AFCap: TP+ FLR+ AFCtrl: FLR- AFStatus: TP- Kernel driver in use: i915 To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1332947/+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 1326788] [NEW] "debian/rules clean" does not clean adequately
Public bug reported: This is a problem in the unity-lens-applications source package. According to Ubuntu policy, the "clean" rule in debian/rules "must undo any effects that the build and binary targets may have had, except that it should leave alone any output files created in the parent directory by a run of a binary target." That target in unity-lens-applications does not do this: root@chickatrice:/tmp# apt-get source unity-lens-applications=7.1.0+13.10.20131011-0ubuntu2 >/dev/null 2>&1 root@chickatrice:/tmp# find unity-lens-applications-7.1.0+13.10.20131011 | wc -l92 root@chickatrice:/tmp# ( cd unity-lens-applications-7.1.0+13.10.20131011 && debian/rules build && debian/rules clean ) >/dev/null 2>&1 root@chickatrice:/tmp# find unity-lens-applications-7.1.0+13.10.20131011 | wc -l103 root@chickatrice:/tmp# rm -r unity* root@chickatrice:/tmp# apt-get source unity-lens-applications=7.1.0+13.10.20131011-0ubuntu2 >/dev/null 2>&1 root@chickatrice:/tmp# find unity-lens-applications-7.1.0+13.10.20131011 > files.before root@chickatrice:/tmp# ( cd unity-lens-applications-7.1.0+13.10.20131011 && debian/rules build && debian/rules clean ) >/dev/null 2>&1 root@chickatrice:/tmp# find unity-lens-applications-7.1.0+13.10.20131011 > files.after root@chickatrice:/tmp# diff files.before files.after | grep '^>' > unity-lens-applications-7.1.0+13.10.20131011/tests/unit/aptd-client.c > unity-lens-applications-7.1.0+13.10.20131011/tests/unit/software-center-data-cache.c > unity-lens-applications-7.1.0+13.10.20131011/tests/unit/xapian-utils.c > unity-lens-applications-7.1.0+13.10.20131011/tests/unit/schemas.c > unity-lens-applications-7.1.0+13.10.20131011/tests/unit/software-center-utils.c > unity-lens-applications-7.1.0+13.10.20131011/tests/unit/software-center-app-details.c > unity-lens-applications-7.1.0+13.10.20131011/tests/unit/utils.c > unity-lens-applications-7.1.0+13.10.20131011/tests/unit/purchase-info-helper.c > unity-lens-applications-7.1.0+13.10.20131011/tests/unit/app-watcher.c > unity-lens-applications-7.1.0+13.10.20131011/data/applications.scope > unity-lens-applications-7.1.0+13.10.20131011/data/scopes.scope It looks like some of the files generating while building are not correctly removed while cleaning. This is a problem if (as I do) you want to convert the package to use the "3.0 (quilt)" source format. The attached patch fixes the problem, but probably more crudely than is acceptable. ** Affects: unity-lens-applications (Ubuntu) Importance: Undecided Status: New ** Patch added: "Crude fix for the problem" https://bugs.launchpad.net/bugs/1326788/+attachment/4125877/+files/mcs-clean -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity-lens-applications in Ubuntu. https://bugs.launchpad.net/bugs/1326788 Title: "debian/rules clean" does not clean adequately Status in “unity-lens-applications” package in Ubuntu: New Bug description: This is a problem in the unity-lens-applications source package. According to Ubuntu policy, the "clean" rule in debian/rules "must undo any effects that the build and binary targets may have had, except that it should leave alone any output files created in the parent directory by a run of a binary target." That target in unity- lens-applications does not do this: root@chickatrice:/tmp# apt-get source unity-lens-applications=7.1.0+13.10.20131011-0ubuntu2 >/dev/null 2>&1 root@chickatrice:/tmp# find unity-lens-applications-7.1.0+13.10.20131011 | wc -l92 root@chickatrice:/tmp# ( cd unity-lens-applications-7.1.0+13.10.20131011 && debian/rules build && debian/rules clean ) >/dev/null 2>&1 root@chickatrice:/tmp# find unity-lens-applications-7.1.0+13.10.20131011 | wc -l103 root@chickatrice:/tmp# rm -r unity* root@chickatrice:/tmp# apt-get source unity-lens-applications=7.1.0+13.10.20131011-0ubuntu2 >/dev/null 2>&1 root@chickatrice:/tmp# find unity-lens-applications-7.1.0+13.10.20131011 > files.before root@chickatrice:/tmp# ( cd unity-lens-applications-7.1.0+13.10.20131011 && debian/rules build && debian/rules clean ) >/dev/null 2>&1 root@chickatrice:/tmp# find unity-lens-applications-7.1.0+13.10.20131011 > files.after root@chickatrice:/tmp# diff files.before files.after | grep '^>' > unity-lens-applications-7.1.0+13.10.20131011/tests/unit/aptd-client.c > unity-lens-applications-7.1.0+13.10.20131011/tests/unit/software-center-data-cache.c > unity-lens-applications-7.1.0+13.10.20131011/tests/unit/xapian-utils.c > unity-lens-applications-7.1.0+13.10.20131011/tests/unit/schemas.c > unity-lens-applications-7.1.0+13.10.20131011/tests/unit/software-center-utils.c > unity-lens-applications-7.1.0+13.10.20131011/tests/unit/software-center-app-details.c > unity-lens-applications-7.1.0+13.10.20131011/tests/unit/utils.c > unity-lens-applications-7.1.0+13.10.20131011/tests/unit/purchase-info-helper.c > unity-lens-applications-7.1.0+13.10.2
[Dx-packages] [Bug 1326788] Re: "debian/rules clean" does not clean adequately
I failed to mention: this problem affects Ubuntu 14.04 LTS. -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity-lens-applications in Ubuntu. https://bugs.launchpad.net/bugs/1326788 Title: "debian/rules clean" does not clean adequately Status in “unity-lens-applications” package in Ubuntu: New Bug description: This is a problem in the unity-lens-applications source package. According to Ubuntu policy, the "clean" rule in debian/rules "must undo any effects that the build and binary targets may have had, except that it should leave alone any output files created in the parent directory by a run of a binary target." That target in unity- lens-applications does not do this: root@chickatrice:/tmp# apt-get source unity-lens-applications=7.1.0+13.10.20131011-0ubuntu2 >/dev/null 2>&1 root@chickatrice:/tmp# find unity-lens-applications-7.1.0+13.10.20131011 | wc -l92 root@chickatrice:/tmp# ( cd unity-lens-applications-7.1.0+13.10.20131011 && debian/rules build && debian/rules clean ) >/dev/null 2>&1 root@chickatrice:/tmp# find unity-lens-applications-7.1.0+13.10.20131011 | wc -l103 root@chickatrice:/tmp# rm -r unity* root@chickatrice:/tmp# apt-get source unity-lens-applications=7.1.0+13.10.20131011-0ubuntu2 >/dev/null 2>&1 root@chickatrice:/tmp# find unity-lens-applications-7.1.0+13.10.20131011 > files.before root@chickatrice:/tmp# ( cd unity-lens-applications-7.1.0+13.10.20131011 && debian/rules build && debian/rules clean ) >/dev/null 2>&1 root@chickatrice:/tmp# find unity-lens-applications-7.1.0+13.10.20131011 > files.after root@chickatrice:/tmp# diff files.before files.after | grep '^>' > unity-lens-applications-7.1.0+13.10.20131011/tests/unit/aptd-client.c > unity-lens-applications-7.1.0+13.10.20131011/tests/unit/software-center-data-cache.c > unity-lens-applications-7.1.0+13.10.20131011/tests/unit/xapian-utils.c > unity-lens-applications-7.1.0+13.10.20131011/tests/unit/schemas.c > unity-lens-applications-7.1.0+13.10.20131011/tests/unit/software-center-utils.c > unity-lens-applications-7.1.0+13.10.20131011/tests/unit/software-center-app-details.c > unity-lens-applications-7.1.0+13.10.20131011/tests/unit/utils.c > unity-lens-applications-7.1.0+13.10.20131011/tests/unit/purchase-info-helper.c > unity-lens-applications-7.1.0+13.10.20131011/tests/unit/app-watcher.c > unity-lens-applications-7.1.0+13.10.20131011/data/applications.scope > unity-lens-applications-7.1.0+13.10.20131011/data/scopes.scope It looks like some of the files generating while building are not correctly removed while cleaning. This is a problem if (as I do) you want to convert the package to use the "3.0 (quilt)" source format. The attached patch fixes the problem, but probably more crudely than is acceptable. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-lens-applications/+bug/1326788/+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 1302302] Re: [regression] Unity now only starts in software rendering mode (i965 Mesa driver can't load)
*** This bug is a duplicate of bug 1302264 *** https://bugs.launchpad.net/bugs/1302264 I have the same problem, also on a relatively new thinkpad, in my case the X1 carbon. I know this is reported as a duplicate of #1302264 but the problems encountered here seem distinct from those reported for that 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/1302302 Title: [regression] Unity now only starts in software rendering mode (i965 Mesa driver can't load) Status in Compiz: New Status in Unity: New Status in “unity” package in Ubuntu: Confirmed Bug description: After updating today Unity only starts in software rendering mode. I can tell because: 1. There's no dash blur. 2. Graphics performance is slow. 3. .xsession-errors says: libGL error: failed to open drm device: Permission denied libGL error: failed to load driver: i965 4. compiz is linked to the software driver: $ pmap `pidof compiz` | grep dri 7f9a1e386000 3256K r-x-- swrast_dri.so 7f9a1e6b4000 2048K - swrast_dri.so 7f9a1e8b4000 60K r swrast_dri.so 7f9a1e8c3000 32K rw--- swrast_dri.so ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.2.0+14.04.20140403-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-22.44-generic 3.13.8 Uname: Linux 3.13.0-22-generic x86_64 .tmp.unity.support.test.1: ApportVersion: 2.14-0ubuntu1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Fri Apr 4 10:46:53 2014 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu GraphicsCard: Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 0b) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:220c] InstallationDate: Installed on 2014-04-03 (0 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Daily amd64 (20140331) MachineType: LENOVO 20AQCTO1WW ProcEnviron: LANGUAGE=en_AU:en TERM=xterm PATH=(custom, no user) LANG=en_AU.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-22-generic.efi.signed root=UUID=a759a4aa-6f67-434e-8f5a-eae13c810c59 ro acpi_backlight=vendor quiet splash vt.handoff=7 SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/10/2013 dmi.bios.vendor: LENOVO dmi.bios.version: GJET67WW (2.17 ) dmi.board.asset.tag: Not Available dmi.board.name: 20AQCTO1WW dmi.board.vendor: LENOVO dmi.board.version: 0B98401 PRO dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrGJET67WW(2.17):bd12/10/2013:svnLENOVO:pn20AQCTO1WW:pvrThinkPadT440s:rvnLENOVO:rn20AQCTO1WW:rvr0B98401PRO:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 20AQCTO1WW dmi.product.version: ThinkPad T440s dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.11+14.04.20140328-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.52-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.0-4ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.0-4ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.15.0-1ubuntu7 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 xserver.bootTime: Fri Apr 4 10:46:12 2014 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id1034 vendor LGD xserver.version: 2:1.15.0-1ubuntu7 To manage notifications about this bug go to: https://bugs.launchpad.net/compiz/+bug/1302302/+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 1301482] Re: ubuntu 14.04 - sound icon is always blocked
I have verified that this is caused by Skype, because the icon immediately turns gray when I close quit Skype. I suspect that this might be a bug in Skype because sometimes it makes a buzzing noise that does not stop until it is restarted. Maybe this bug is related to the that problem. -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-sound in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1301482 Title: ubuntu 14.04 - sound icon is always blocked Status in “indicator-sound” package in Ubuntu: Incomplete Bug description: In Ubuntu 14.04 Whenever the sound is muted the icon is red (so it seems to recognize blocked sound). However there is definitely nothing playing and also pavucontrol, shows that no sound is playing. So it seems to be a bug package: indicator-sound 12.10.2+14.04.20140401-0ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-sound/+bug/1301482/+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 1301482] Re: ubuntu 14.04 - sound icon is always blocked
I have the same problem. I have not tested it, but it seems likely that Skype is causing it for me too. -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-sound in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1301482 Title: ubuntu 14.04 - sound icon is always blocked Status in “indicator-sound” package in Ubuntu: Incomplete Bug description: In Ubuntu 14.04 Whenever the sound is muted the icon is red (so it seems to recognize blocked sound). However there is definitely nothing playing and also pavucontrol, shows that no sound is playing. So it seems to be a bug package: indicator-sound 12.10.2+14.04.20140401-0ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-sound/+bug/1301482/+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 1310316] Re: Text scaling factor changing unexpectedly
I have the same issue on a Vaio with a 1920x1080 screen at 15". Setting the text scale to 1.25 seems to sometimes boot up with the scaling being again and all of the text appearing too large. Also, the mouse cursors are incorrectly scaled in GTK2 applications, varying between controls from a 1.25-scaled cursor to the 1-scale cursor used by GTK3 apps. Most notably, pop-up menus will have the mouse scale change when the pop-up is clicked and when the mouse is moved into the pop-up. -- 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/1310316 Title: Text scaling factor changing unexpectedly Status in “unity” package in Ubuntu: Confirmed Bug description: I have a MacBook pro with a Retina display. I have set the "Scale for menu and title bars" setting (into Settings > Displays) to 1.5 to make the UI looks good on my screen. That works very well. But sometimes, usually after logging, all the fonts of the UI become much bigger. When that happen I open unity tweat tool and notice that the text scaling factor changed to 2.25. If I reset it to 1 the all the fonts go back to normal. The problem does not happen all the time. I would say it happen one time out of three logging. It may also happen when installing applications from the software center. I have yet to find a procedure to reproduce it all the times. 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 x86_64 NonfreeKernelModules: wl nvidia .proc.driver.nvidia.gpus.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 331.38 Wed Jan 8 19:32:30 PST 2014 GCC version: gcc version 4.8.2 (Ubuntu 4.8.2-19ubuntu1) .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Sun Apr 20 18:21:02 2014 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu DkmsStatus: bbswitch, 0.7, 3.13.0-24-generic, x86_64: installed bcmwl, 6.30.223.141+bdcom, 3.13.0-24-generic, x86_64: installed nvidia-331, 331.38, 3.13.0-24-generic, x86_64: installed GraphicsCard: NVIDIA Corporation GK107M [GeForce GT 650M Mac Edition] [10de:0fd5] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Apple Inc. Device [106b:00f2] InstallationDate: Installed on 2014-04-19 (1 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64+mac (20140417) MachineType: Apple Inc. MacBookPro10,1 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-24-generic root=UUID=3d5a4115-5e15-4eca-bd1c-0bee2543a1cb ro quiet splash SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/21/2012 dmi.bios.vendor: Apple Inc. dmi.bios.version: MBP101.88Z.00EE.B03.1212211437 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-C3EC7CD22292981F dmi.board.vendor: Apple Inc. dmi.board.version: MacBookPro10,1 dmi.chassis.type: 10 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-C3EC7CD22292981F dmi.modalias: dmi:bvnAppleInc.:bvrMBP101.88Z.00EE.B03.1212211437:bd12/21/2012:svnAppleInc.:pnMacBookPro10,1:pvr1.0:rvnAppleInc.:rnMac-C3EC7CD22292981F:rvrMacBookPro10,1:cvnAppleInc.:ct10:cvrMac-C3EC7CD22292981F: dmi.product.name: MacBookPro10,1 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. version.compiz: compiz 1:0.9.11+14.04.20140409-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.52-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.0-4ubuntu5 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.0-4ubuntu5 version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 xserver.bootTime: Sun Apr 20 18:04:05 2014 xserver.configfile: default xserver.errors: open /dev/fb0: No such file or directory xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.15.1-0ubuntu2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+sourc
[Dx-packages] [Bug 1281746] [NEW] Duplicated settings menu items.
Public bug reported: When browsing applications using the Unity launcher; through the 'Home' lens, the 'search' function or the 'Applications' lens, shortcuts to the settings menus are duplicated (e.g. Keyboard, Apperance, Brightness & Lock etc.). Ubuntu: Description:Ubuntu Trusty Tahr (development branch) Release:14.04 Unity: Installed: 7.1.2+14.04.20131106.1-0ubuntu4 Candidate: 7.1.2+14.04.20140217-0ubuntu1 Expectation: Only one item per setting menu. What happened instead: Two per each setting item. See screenshot. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.1.2+14.04.20131106.1-0ubuntu4 ProcVersionSignature: Ubuntu 3.13.0-8.28-generic 3.13.2 Uname: Linux 3.13.0-8-generic x86_64 NonfreeKernelModules: nvidia .proc.driver.nvidia.gpus.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 331.38 Wed Jan 8 19:32:30 PST 2014 GCC version: gcc version 4.8.2 (Ubuntu 4.8.2-15ubuntu3) .tmp.unity.support.test.0: ApportVersion: 2.13.2-0ubuntu4 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Tue Feb 18 19:11:16 2014 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu DkmsStatus: bbswitch, 0.7, 3.13.0-8-generic, x86_64: installed nvidia-331, 331.38, 3.13.0-8-generic, x86_64: installed GraphicsCard: NVIDIA Corporation GT216 [GeForce 315] [10de:0a22] (rev a2) (prog-if 00 [VGA controller]) Subsystem: PC Partner Limited / Sapphire Technology Device [174b:1141] InstallationDate: Installed on 2014-02-16 (1 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140216) MachineType: Acer Aspire X3950 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-8-generic root=UUID=65d1309b-61bb-4482-b618-b2e56387022b ro quiet splash SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/13/2010 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P01-A2 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: Aspire X3950 dmi.board.vendor: Acer dmi.chassis.type: 3 dmi.chassis.vendor: Acer dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP01-A2:bd04/13/2010:svnAcer:pnAspireX3950:pvr:rvnAcer:rnAspireX3950:rvr:cvnAcer:ct3:cvr: dmi.product.name: Aspire X3950 dmi.sys.vendor: Acer version.compiz: compiz 1:0.9.10+13.10.20131011-0ubuntu4 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.52-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.0.1-1ubuntu2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.0.1-1ubuntu2 version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A version.xserver-xorg-core: xserver-xorg-core 2:1.15.0-1ubuntu6 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 xserver.bootTime: Tue Feb 18 17:47:42 2014 xserver.configfile: default xserver.devices: inputPower Button KEYBOARD, id 6 inputPower Button KEYBOARD, id 7 inputLogitech USB-PS/2 Optical Mouse MOUSE, id 8 inputAT Translated Set 2 keyboard KEYBOARD, id 9 inputImPS/2 Generic Wheel Mouse MOUSE, id 10 xserver.errors: open /dev/fb0: No such file or directory xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.15.0-1ubuntu6 ** Affects: unity (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug compiz-0.9 third-party-packages trusty ubuntu ** Attachment added: "Screenshot from 2014-02-18 19:18:26.png" https://bugs.launchpad.net/bugs/1281746/+attachment/3985727/+files/Screenshot%20from%202014-02-18%2019%3A18%3A26.png -- 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/1281746 Title: Duplicated settings menu items. Status in “unity” package in Ubuntu: New Bug description: When browsing applications using the Unity launcher; through the 'Home' lens, the 'search' function or the 'Applications' lens, shortcuts to the settings menus are duplicated (e.g. Keyboard, Apperance, Brightness & Lock etc.). Ubuntu: Description: Ubuntu Trusty Tahr (development branch) Release: 14.04 Unity: Installed: 7.1.2+14.04.20131106.1-0ubuntu4 Candidate: 7.1.2+14.04.20140217-0ubuntu1 Expectation: Only one item per setting menu. What happened instead: Two per each setting item. See screenshot.
[Dx-packages] [Bug 1245495] Re: Rhythmbox controls and track info broken
I tried again while Rhytmbox was running but it gives the same output: ben@xameroth:~$ gdbus call --session --dest org.mpris.MediaPlayer2.rhythmbox --object-path /org/mpris/MediaPlayer2 --method org.freedesktop.DBus.Properties.GetAll 'org.mpris.MediaPlayer2.Player' Error: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.mpris.MediaPlayer2.rhythmbox was not provided by any .service files -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-sound in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1245495 Title: Rhythmbox controls and track info broken Status in Sound Menu: Triaged Status in “indicator-sound” package in Ubuntu: Triaged Bug description: A Rhythmbox section appears in the indicator menu as it should but there are several glitches: When RB isn't running > click on the icon in the indicator > RB starts as expected :-) When RB is running > click on the icon in the indicator > RB icon wiggles in launcher but window doesn't come to focus :-( Track info and album art appears in notifications, but is never shown in the sound menu. Regardless of whether RB is running: Sound menu track controls (prev, play/pause, next) do nothing. The play/pause button has a dotted orange ring, which turns to an orange square on mouseover (see screenshots). Ubuntu 13.10 64-bit unity: 7.1.2+13.10.20131014.1-0ubuntu1 indicator-sound: 12.10.2+13.10.20131011-0ubuntu1 rhythmbox: 2.99.1-0ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-sound/+bug/1245495/+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 1245495] Re: Rhythmbox controls and track info broken
All of the problems I reported are continuous, they always happen as described and never function properly. The translucent popup notifications are fine, they show track info and album art as expected. The problem with track info and album art is that it is _never_ displayed in the sound menu since installing 13.10. Here is the output of the command that you asked for: ben@xameroth:~$ gdbus call --session --dest org.mpris.MediaPlayer2.rhythmbox --object-path /org/mpris/MediaPlayer2 --method org.freedesktop.DBus.Properties.GetAll 'org.mpris.MediaPlayer2.Player' Error: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.mpris.MediaPlayer2.rhythmbox was not provided by any .service files Can I provide any more information for you? -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-sound in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1245495 Title: Rhythmbox controls and track info broken Status in Sound Menu: Triaged Status in “indicator-sound” package in Ubuntu: Triaged Bug description: A Rhythmbox section appears in the indicator menu as it should but there are several glitches: When RB isn't running > click on the icon in the indicator > RB starts as expected :-) When RB is running > click on the icon in the indicator > RB icon wiggles in launcher but window doesn't come to focus :-( Track info and album art appears in notifications, but is never shown in the sound menu. Regardless of whether RB is running: Sound menu track controls (prev, play/pause, next) do nothing. The play/pause button has a dotted orange ring, which turns to an orange square on mouseover (see screenshots). Ubuntu 13.10 64-bit unity: 7.1.2+13.10.20131014.1-0ubuntu1 indicator-sound: 12.10.2+13.10.20131011-0ubuntu1 rhythmbox: 2.99.1-0ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-sound/+bug/1245495/+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 1245495] Re: Rhythmbox controls and track info broken
** Attachment added: "mouse over 2" https://bugs.launchpad.net/ubuntu/+source/indicator-sound/+bug/1245495/+attachment/3893746/+files/Screenshot%20from%202013-10-28%2013%3A34%3A44.png ** Description changed: A Rhythmbox section appears in the indicator menu as it should but there - are various glitches: + are several glitches: When RB isn't running > click on the icon in the indicator > RB starts as expected :-) When RB is running > click on the icon in the indicator > RB icon wiggles in launcher but window doesn't come to focus :-( Track info and album art appears in notifications, but is never shown in the sound menu. Regardless of whether RB is running: Sound menu track controls (prev, play/pause, next) do nothing. The play/pause button has a dotted orange ring, which turns to an orange square on mouseover (see screenshots). Ubuntu 13.10 64-bit unity: 7.1.2+13.10.20131014.1-0ubuntu1 indicator-sound: 12.10.2+13.10.20131011-0ubuntu1 rhythmbox: 2.99.1-0ubuntu1 -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-sound in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1245495 Title: Rhythmbox controls and track info broken Status in “indicator-sound” package in Ubuntu: New Bug description: A Rhythmbox section appears in the indicator menu as it should but there are several glitches: When RB isn't running > click on the icon in the indicator > RB starts as expected :-) When RB is running > click on the icon in the indicator > RB icon wiggles in launcher but window doesn't come to focus :-( Track info and album art appears in notifications, but is never shown in the sound menu. Regardless of whether RB is running: Sound menu track controls (prev, play/pause, next) do nothing. The play/pause button has a dotted orange ring, which turns to an orange square on mouseover (see screenshots). Ubuntu 13.10 64-bit unity: 7.1.2+13.10.20131014.1-0ubuntu1 indicator-sound: 12.10.2+13.10.20131011-0ubuntu1 rhythmbox: 2.99.1-0ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-sound/+bug/1245495/+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 1245495] Re: Rhythmbox controls and track info broken
** Attachment added: "mouse over 1" https://bugs.launchpad.net/ubuntu/+source/indicator-sound/+bug/1245495/+attachment/3893745/+files/Screenshot%20from%202013-10-28%2013%3A34%3A30.png -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-sound in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1245495 Title: Rhythmbox controls and track info broken Status in “indicator-sound” package in Ubuntu: New Bug description: A Rhythmbox section appears in the indicator menu as it should but there are several glitches: When RB isn't running > click on the icon in the indicator > RB starts as expected :-) When RB is running > click on the icon in the indicator > RB icon wiggles in launcher but window doesn't come to focus :-( Track info and album art appears in notifications, but is never shown in the sound menu. Regardless of whether RB is running: Sound menu track controls (prev, play/pause, next) do nothing. The play/pause button has a dotted orange ring, which turns to an orange square on mouseover (see screenshots). Ubuntu 13.10 64-bit unity: 7.1.2+13.10.20131014.1-0ubuntu1 indicator-sound: 12.10.2+13.10.20131011-0ubuntu1 rhythmbox: 2.99.1-0ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-sound/+bug/1245495/+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 1245495] [NEW] Rhythmbox controls and track info broken
Public bug reported: A Rhythmbox section appears in the indicator menu as it should but there are several glitches: When RB isn't running > click on the icon in the indicator > RB starts as expected :-) When RB is running > click on the icon in the indicator > RB icon wiggles in launcher but window doesn't come to focus :-( Track info and album art appears in notifications, but is never shown in the sound menu. Regardless of whether RB is running: Sound menu track controls (prev, play/pause, next) do nothing. The play/pause button has a dotted orange ring, which turns to an orange square on mouseover (see screenshots). Ubuntu 13.10 64-bit unity: 7.1.2+13.10.20131014.1-0ubuntu1 indicator-sound: 12.10.2+13.10.20131011-0ubuntu1 rhythmbox: 2.99.1-0ubuntu1 ** Affects: indicator-sound (Ubuntu) Importance: Undecided Status: New ** Tags: controls indicator-sound rhythmbox ** Attachment added: "mouse out" https://bugs.launchpad.net/bugs/1245495/+attachment/3893744/+files/Screenshot%20from%202013-10-28%2013%3A34%3A13.png ** Description changed: A Rhythmbox section appears in the indicator menu as it should but there are various glitches: When RB isn't running > click on the icon in the indicator > RB starts as expected :-) When RB is running > click on the icon in the indicator > RB icon wiggles in launcher but window doesn't come to focus :-( Track info and album art appears in notifications, but is never shown in the sound menu. Regardless of whether RB is running: - Sound menu track controls (prev, play/pause, next) do nothing. + Sound menu track controls (prev, play/pause, next) do nothing. The play/pause button has a dotted orange ring, which turns to an orange square on mouseover (see screenshots). + + Ubuntu 13.10 64-bit + unity: 7.1.2+13.10.20131014.1-0ubuntu1 + indicator-sound: 12.10.2+13.10.20131011-0ubuntu1 + rhythmbox: 2.99.1-0ubuntu1 -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-sound in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1245495 Title: Rhythmbox controls and track info broken Status in “indicator-sound” package in Ubuntu: New Bug description: A Rhythmbox section appears in the indicator menu as it should but there are several glitches: When RB isn't running > click on the icon in the indicator > RB starts as expected :-) When RB is running > click on the icon in the indicator > RB icon wiggles in launcher but window doesn't come to focus :-( Track info and album art appears in notifications, but is never shown in the sound menu. Regardless of whether RB is running: Sound menu track controls (prev, play/pause, next) do nothing. The play/pause button has a dotted orange ring, which turns to an orange square on mouseover (see screenshots). Ubuntu 13.10 64-bit unity: 7.1.2+13.10.20131014.1-0ubuntu1 indicator-sound: 12.10.2+13.10.20131011-0ubuntu1 rhythmbox: 2.99.1-0ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-sound/+bug/1245495/+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 874734] Re: Alt-Backtick Keyboard Shortcut Can Not Be Disabled
The workaround in #6 worked for me, but it is still a 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/874734 Title: Alt-Backtick Keyboard Shortcut Can Not Be Disabled Status in Unity: Expired Status in “unity” package in Ubuntu: Expired Bug description: The 'Alt-Backtick' shortcut for the app switcher is interfering with my other applications. How can I disable this without disabling all of Unity? The Atl-Backtick key combination is commonly used in Emacs, Emacs is rendered unusable with Unity intercepting this key combo. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/874734/+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
