[Desktop-packages] [Bug 934189] Re: desktop focus interferes with conky
Thanks for the hint, GrouchyGaijin. I could also wipe the problem with a window rule in ccsm (compizconfig settings manager). I added class=conky in the 'No focus' field on the 'Matches' tab of the 'Window Rules' module. The window's class name may differ depending on the personal conky configuration. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to compiz in Ubuntu. https://bugs.launchpad.net/bugs/934189 Title: desktop focus interferes with conky Status in compiz package in Ubuntu: Confirmed Status in compiz package in Arch Linux: New Bug description: Have conky specs: own_window yes own_window_class Conky own_window_type normal own_window_transparent yes own_window_hints undecorated,below,sticky,skip_taskbar,skip_pager Open an application (e.g. gedit or system-settings) and close it again, desktop doesn't automatically take focus. User needs to left click on conky window to focus desktop in order to invoke shortcuts to switch workspaces (ctrl+alt+arrow) or alt+f2. own_window_type desktop doesn't help. Alternativeley open and close the dash with super allows shortcuts to switch workspaces. After latest updates above workarounds don't help any longer. Now there is no option to make shortcuts invoke their functions. ## This was fixed in Oneiric bug 871277 #7. ## Monitoring bug 953089 since the description of 4) meets exactly latest behaviour here, except 'If no program is visible on the screen'. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: compiz 1:0.9.7.0~bzr2995-0ubuntu4 ProcVersionSignature: Ubuntu 3.2.0-16.25-generic 3.2.6 Uname: Linux 3.2.0-16-generic x86_64 NonfreeKernelModules: wl .tmp.unity.support.test.0: ApportVersion: 1.91-0ubuntu1 Architecture: amd64 CompizPlugins: [core,composite,opengl,compiztoolbox,decor,imgpng,obs,gnomecompat,snap,screenshot,regex,grid,resize,move,animation,place,mousepoll,session,winrules,workarounds,wall,expo,fade,ezoom,scale,unityshell] CompositorRunning: compiz Date: Fri Feb 17 14:14:07 2012 DistUpgraded: Fresh install DistroCodename: precise DistroVariant: ubuntu DkmsStatus: bcmwl, 5.100.82.38+bdcom, 3.2.0-14-generic, x86_64: installed bcmwl, 5.100.82.38+bdcom, 3.2.0-15-generic, x86_64: installed bcmwl, 5.100.82.38+bdcom, 3.2.0-16-generic, x86_64: installed GraphicsCard: Advanced Micro Devices [AMD] nee ATI RS880M [Mobility Radeon HD 4200 Series] [1002:9712] (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Device [103c:1475] InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Alpha amd64 (2029.1) MachineType: Hewlett-Packard HP 625 PackageArchitecture: all ProcEnviron: PATH=(custom, no user) LANG=de_DE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-16-generic root=UUID=bab9ac13-843a-4289-a0f2-b254b2dda7d3 ro SourcePackage: compiz UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/07/2010 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68DVA Ver. F.06 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 1475 dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 72.0E dmi.chassis.asset.tag: CNU1080QP1 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr68DVAVer.F.06:bd12/07/2010:svnHewlett-Packard:pnHP625:pvr:rvnHewlett-Packard:rn1475:rvrKBCVersion72.0E:cvnHewlett-Packard:ct10:cvr: dmi.product.name: HP 625 dmi.sys.vendor: Hewlett-Packard version.compiz: compiz 1:0.9.7.0~bzr2995-0ubuntu4 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.30-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 8.0~rc2-0ubuntu5 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 8.0~rc2-0ubuntu5 version.xserver-xorg-core: xserver-xorg-core 2:1.11.4-0ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.6.99.901+git20120126-0ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:6.14.99~git20111219.aacbd629-0ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.17.0-1ubuntu4 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:0.0.16+git20111201+b5534a1-1build2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/934189/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1366165] Re: No hybrid GPU and this error appears: Failed to spawn hybrid-gfx main process: unable to execute: No such file or directory
I am also affected after upgrading from 12.04.5 to 14.04.1. My system's facts sheet is as follows: - Lenovo T410i - Linux ubuntu 3.13.0-32-generic #57-Ubuntu SMP Tue Jul 15 03:51:08 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux - NVIDIA Corporation GT218M [NVS 3100M] (rev a2) (prog-if 00 [VGA controller]) Error log in /var/log/syslog contains at least the following messages: init: Failed to spawn hybrid-gfx main process: unable to execute: No such file or directory init: nvidia-prime main process (…) terminated with status 127 init: lightdm main process terminated with status 1 init: plymouth-ready (startup) main process (…) terminated with status 1 init: failsafe-x main process (…) terminated with status 127 The greeter won't show up, lightdm fails to start automatically and manually (via sudo service lightdm start) respectively. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-drivers-common in Ubuntu. https://bugs.launchpad.net/bugs/1366165 Title: No hybrid GPU and this error appears: Failed to spawn hybrid-gfx main process: unable to execute: No such file or directory Status in ubuntu-drivers-common package in Ubuntu: Confirmed Bug description: I have an nVidia 9800GT GPU and a Core 2 Duo CPU. Still, I get errors during startup: 32.281097] init: Failed to spawn hybrid-gfx main process: unable to execute: No such file or director ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: ubuntu-drivers-common 1:0.2.91.6 ProcVersionSignature: Ubuntu 3.13.0-35.62-generic 3.13.11.6 Uname: Linux 3.13.0-35-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu3.3 Architecture: amd64 Date: Fri Sep 5 18:31:30 2014 InstallationDate: Installed on 2012-03-26 (892 days ago) InstallationMedia: Mythbuntu 11.10 Oneiric Ocelot - Release amd64 (20111012) SourcePackage: ubuntu-drivers-common UpgradeStatus: Upgraded to trusty on 2014-07-20 (47 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/1366165/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 879838] Re: Keyboard Layout Germany Neo 2: Mod4 does not work if used as secondary keyboard layout
I am affected by this bug on Precise. I can confirm the bug description as a whole. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xkeyboard-config in Ubuntu. https://bugs.launchpad.net/bugs/879838 Title: Keyboard Layout Germany Neo 2: Mod4 does not work if used as secondary keyboard layout Status in “xkeyboard-config” package in Ubuntu: Confirmed Bug description: If Neo 2 is used as secondary keyboard layout, Layer 4 and 6 (that is, Mod4) don't work. To reproduce this bug, do the following: 1: Neo 2 as primary keyboard layout - start gnome-keyboard-properties - Click Add... - Select Country: Germany and Variants: Germany Neo 2 - Select Germany Neo 2 and move it to the top of the list. Try to use Neo Layer 4 or 6. E.g. type the number 4 which is Mod4 and n in Neo ( and j in standard German QWERTZ layout) or move the cursor left using Mod4 and i (AltGr and s in QWERTZ layot). Works as expected. 2: Neo as secondary layout - Now add Germany Eliminate dead keys to the list and move it to the top - Use Neo 2 as secondary layout - Click Options and select Scroll lock (or any other) as Key(s) to change layout Now switch to Neo using the selected key and try to type 4 or move the curser as above. Instead of Neo Layer 4 or 6 you will have Layer 1/3 (that is, you will be typing an n instead of a 4 and an i instead of moving the cursor left). Choosing other keys for layout change or turning the compose key on/off does not change anything. Neither does applying Neo 2 as primary layout system wide and using Germany Eliminate dead keys with Neo 2 as a secondary keyboard layout as local user. Applying the patch suggested on neo-layout.org for a similar problem (http://wiki.neo-layout.org/ticket/174) does not have any effect. Description: Ubuntu 11.04 Release: 11.04 xkb-data: 2.1-1ubuntu3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xkeyboard-config/+bug/879838/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 408903] Re: Does not handle microphone mute button (KEY_MICMUTE)
I installed libx11-6 from precise-proposed but can't verify the included bugfix. Apart from that, is there any other relevant package that has to be updated? I have the following (latest) versions installed: gnome-settings-daemon: 3.4.2-0ubuntu0.6.2 libx11-6: 2:1.4.99.1-0ubuntu2.2 udev: 175-0ubuntu9.4 xkb-data: 2.5-1ubuntu1.3 xkb-data-i18n: 2.5-1ubuntu1.3 Of course the affected Precise system is up to date as of today. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to x11proto-core in Ubuntu. https://bugs.launchpad.net/bugs/408903 Title: Does not handle microphone mute button (KEY_MICMUTE) Status in OEM Priority Project: Triaged Status in OEM Priority Project precise series: Confirmed Status in OEM Priority Project raring series: Won't Fix Status in central project for keyboard configuration: Fix Released Status in “gnome-settings-daemon” package in Ubuntu: Triaged Status in “libx11” package in Ubuntu: Confirmed Status in “udev” package in Ubuntu: Fix Released Status in “x11proto-core” package in Ubuntu: New Status in “xserver-xorg-input-evdev” package in Ubuntu: Won't Fix Status in “gnome-settings-daemon” source package in Precise: New Status in “libx11” source package in Precise: Fix Committed Status in “udev” source package in Precise: New Status in “x11proto-core” source package in Precise: Fix Released Status in “xserver-xorg-input-evdev” source package in Precise: Won't Fix Status in “gnome-settings-daemon” source package in Raring: Triaged Status in “libx11” source package in Raring: New Status in “udev” source package in Raring: Triaged Status in “x11proto-core” source package in Raring: New Status in “xserver-xorg-input-evdev” source package in Raring: Won't Fix Bug description: [Impact] * People buying thinkpad hardware are not able to use a mic mute key, that comes with their machine [Test Case] * Press mic mute key * Observe that nothing happens [Regression Potential] * Very low. This is very isolated code. All it does is add functionality. In fact there are very few deletions in the diffs. * There is an existing acpi solution, that's already been mentioned in this bug. I'm not sure how these users would be affected once the upgrade hits, but it was never released as an official fix. [Original Report] Pressing the new microphone mute button does not do anything. It should toggle the mute on the current capture device and toggle an led that is part of the button. acpi_listen output: ibm/hotkey HKEY 0080 101b xev output: MappingNotify event, serial 34, synthetic NO, window 0x0, request MappingKeyboard, first_keycode 8, count 248 MappingNotify event, serial 34, synthetic NO, window 0x0, request MappingKeyboard, first_keycode 8, count 247 KeyPress event, serial 34, synthetic NO, window 0x341, root 0x118, subw 0x0, time 10334714, (317,-162), root:(322,207), state 0x0, keycode 248 (keysym 0x0, NoSymbol), same_screen YES, XLookupString gives 0 bytes: XmbLookupString gives 0 bytes: XFilterEvent returns: False KeyRelease event, serial 34, synthetic NO, window 0x341, root 0x118, subw 0x0, time 10334714, (317,-162), root:(322,207), state 0x0, keycode 248 (keysym 0x0, NoSymbol), same_screen YES, XLookupString gives 0 bytes: XFilterEvent returns: False To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/408903/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 408903] Re: Does not handle microphone mute button (KEY_MICMUTE)
Is it possible for me to test the above fixes (g-s-d, x11-proto-core, udev, xkeyboard-config) on precise? I just built x11-proto-core from proposed but apparently the package alone doesn't fix the bug for me. I also have to admit that I'm not familiar with inter-distribution fixes and how to apply them to my distribution, be it Ubuntu or Debian. Thanks in advance. :) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to x11proto-core in Ubuntu. https://bugs.launchpad.net/bugs/408903 Title: Does not handle microphone mute button (KEY_MICMUTE) Status in OEM Priority Project: Triaged Status in OEM Priority Project precise series: Confirmed Status in OEM Priority Project raring series: Won't Fix Status in central project for keyboard configuration: Fix Released Status in “gnome-settings-daemon” package in Ubuntu: Triaged Status in “udev” package in Ubuntu: Fix Released Status in “x11proto-core” package in Ubuntu: New Status in “xserver-xorg-input-evdev” package in Ubuntu: Triaged Status in “gnome-settings-daemon” source package in Precise: New Status in “udev” source package in Precise: New Status in “x11proto-core” source package in Precise: Fix Committed Status in “xserver-xorg-input-evdev” source package in Precise: New Status in “gnome-settings-daemon” source package in Raring: Triaged Status in “udev” source package in Raring: Triaged Status in “x11proto-core” source package in Raring: New Status in “xserver-xorg-input-evdev” source package in Raring: Triaged Bug description: [Impact] * People buying thinkpad hardware are not able to use a mic mute key, that comes with their machine [Test Case] * Press mic mute key * Observe that nothing happens [Regression Potential] * Very low. This is very isolated code. All it does is add functionality. In fact there are very few deletions in the diffs. * There is an existing acpi solution, that's already been mentioned in this bug. I'm not sure how these users would be affected once the upgrade hits, but it was never released as an official fix. [Original Report] Pressing the new microphone mute button does not do anything. It should toggle the mute on the current capture device and toggle an led that is part of the button. acpi_listen output: ibm/hotkey HKEY 0080 101b xev output: MappingNotify event, serial 34, synthetic NO, window 0x0, request MappingKeyboard, first_keycode 8, count 248 MappingNotify event, serial 34, synthetic NO, window 0x0, request MappingKeyboard, first_keycode 8, count 247 KeyPress event, serial 34, synthetic NO, window 0x341, root 0x118, subw 0x0, time 10334714, (317,-162), root:(322,207), state 0x0, keycode 248 (keysym 0x0, NoSymbol), same_screen YES, XLookupString gives 0 bytes: XmbLookupString gives 0 bytes: XFilterEvent returns: False KeyRelease event, serial 34, synthetic NO, window 0x341, root 0x118, subw 0x0, time 10334714, (317,-162), root:(322,207), state 0x0, keycode 248 (keysym 0x0, NoSymbol), same_screen YES, XLookupString gives 0 bytes: XFilterEvent returns: False To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/408903/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1096810] Re: Loosing cursor blinking when switching viewport either on Unity or Openbox
I am also affected. I don't use several viewports but I use Compiz's keybinding for Show desktop. Once, using this shortcut, the desktop was shown and brought back the terminal's cursors stops blinking and can't be revived. Changing the above mentioned dconf settings doesn't help, neither cursor-blink-time nor cursor-blink-timeout. System: Ubuntu 12.04.2 LTS (precise) Relevant packages: compiz 1:0.9.7.12-0ubuntu1 gnome-session-fallback 3.2.1-0ubuntu8 gnome-terminal 3.4.1.1-0ubuntu1 lightdm 1.2.3-0ubuntu2.1 linux-image-generic-lts-quantal 3.5.0.32.39 nvidia-current 304.88-0ubuntu0.0.2 xorg 1:7.6+12ubuntu2 xserver-xorg-core-lts-quantal 2:1.13.0-0ubuntu6.1~precise3 xserver-xorg-lts-quantal 1:7.7+1ubuntu4~precise1 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/1096810 Title: Loosing cursor blinking when switching viewport either on Unity or Openbox Status in “gnome-terminal” package in Ubuntu: Confirmed Bug description: When I switch viewport (virtual desktop) and I've got a focussed or unfocussed gnome-terminal open, it (most of the times but not always) looses the blinking cursor. When I've on the shell, then it's lost, when I'm on Vim I need to move and exit insert mode to see the cursor again. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: gnome-terminal 3.6.0-0ubuntu1 ProcVersionSignature: Ubuntu 3.5.0-21.32-generic 3.5.7.1 Uname: Linux 3.5.0-21-generic x86_64 ApportVersion: 2.6.1-0ubuntu9 Architecture: amd64 Date: Mon Jan 7 09:53:14 2013 InstallationDate: Installed on 2013-01-06 (0 days ago) InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Release amd64 (20121017.5) MarkForUpload: True ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_GB.UTF-8 SHELL=/bin/zsh SourcePackage: gnome-terminal UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1096810/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 694910] Re: Regression: patch to bug 539477 breaks Super+P keybindings
I don't understand why bug #539477 has been fixed at the cost of an unknown but definitely unaffected majority of users who don't use hardware that implemented strange Microsoft standards. I hope it's possible to revert the fix for #539477 and commit a new fix that is less intervening. What about adding an option to the keyboard settings in Gnome Control Center? Since I extensively use Super in combination with several keys (read: letters), p being only one out of many, I patched gnome-settings- daemon by removing the Superp shortcut, and created my own deb package. Though I could refrain from using Superp, I can't prevent my fingers from accidentally hitting said shortcut. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/694910 Title: Regression: patch to bug 539477 breaks Super+P keybindings Status in Gnome Settings Daemon: Won't Fix Status in “gnome-settings-daemon” package in Ubuntu: Confirmed Bug description: Binary package hint: gnome-settings-daemon The current patch to bug 539477 breaks the super+p keybinding for all user applications when running gnone-settings-daemon. This behavior is hard-coded, not discoverable, and not configurable. The workaround is to disable parts of xrandr such that screen switching is no longer possible. The patch has been checked in and released as a bugfix to Ubuntu 10.10, causing regressions in several applications. For more details, see https://bugs.launchpad.net/ubuntu/+source/linux/+bug/539477/ particularly https://bugs.launchpad.net/ubuntu/+source/linux/+bug/539477/comments/68 and immediately above. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-settings-daemon/+bug/694910/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
