[Desktop-packages] [Bug 1158296] Re: Systems with AMD 6660 discrete will hang up while doing poweroff and reboot tests by pm_test tool.
** Changed in: fglrx-installer (Ubuntu) Status: New = Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to fglrx-installer in Ubuntu. https://bugs.launchpad.net/bugs/1158296 Title: Systems with AMD 6660 discrete will hang up while doing poweroff and reboot tests by pm_test tool. Status in amd: Incomplete Status in “fglrx-installer” package in Ubuntu: Incomplete Bug description: Steps to Reproduce: 1. GM -B21 image, go through OOBE,boot into OS. 2. Copy pm_test file to Home Folder, open terminal to run sudo python pm_test -r 30 poweroff command. 3. After 20 minutes, find system hang up with backlight off. Oops: Feb 1 14:19:28 sit-HP-Pavilion-15-Notebook-PC kernel: [ 11.080151] Hardware name: HP Pavilion 15 Notebook PC Feb 1 14:19:28 sit-HP-Pavilion-15-Notebook-PC kernel: [ 11.080152] kobject_add_internal failed for msi_irqs with -EEXIST, don't try to register things with the same name in the same directory. Feb 1 14:19:28 sit-HP-Pavilion-15-Notebook-PC kernel: [ 11.080153] Modules linked in: fglrx(PO) amd_iommu_v2 snd_hda_codec_hdmi(O) snd_hda_codec_realtek(O) coretemp kvm ghash_clmulni_intel cryptd joydev hp_wmi sparse_keymap dm_multipath scsi_dh microcode snd_hda_intel(O) snd_hda_codec(O) snd_hwdep hp_accel snd_pcm lis3lv02d input_polldev uvcvideo videobuf2_core videodev videobuf2_vmalloc videobuf2_memops snd_seq_midi snd_rawmidi snd_seq_midi_event snd_seq wmi(O) rfcomm snd_timer snd_seq_device mac_hid psmouse serio_raw i915 snd drm_kms_helper parport_pc bnep drm soundcore i2c_algo_bit ppdev lpc_ich bluetooth video snd_page_alloc mei lp parport binfmt_misc r8169 dm_raid45 xor dm_mirror dm_region_hash dm_log btrfs zlib_deflate libcrc32c [last unloaded: amd_iommu_v2] Feb 1 14:19:28 sit-HP-Pavilion-15-Notebook-PC kernel: [ 11.080177] Pid: 1328, comm: Xorg Tainted: P W O 3.5.0-22-generic #33~precise1-Ubuntu Feb 1 14:19:28 sit-HP-Pavilion-15-Notebook-PC kernel: [ 11.080178] Call Trace: Feb 1 14:19:28 sit-HP-Pavilion-15-Notebook-PC kernel: [ 11.080180] [81052c9f] warn_slowpath_common+0x7f/0xc0 Feb 1 14:19:28 sit-HP-Pavilion-15-Notebook-PC kernel: [ 11.080182] [81052d96] warn_slowpath_fmt+0x46/0x50 Feb 1 14:19:28 sit-HP-Pavilion-15-Notebook-PC kernel: [ 11.080185] [811f8dee] ? release_sysfs_dirent+0x7e/0x100 Feb 1 14:19:28 sit-HP-Pavilion-15-Notebook-PC kernel: [ 11.080187] [81332594] kobject_add_internal+0x1f4/0x210 Feb 1 14:19:28 sit-HP-Pavilion-15-Notebook-PC kernel: [ 11.080189] [81332ac8] ? kobject_set_name+0x38/0x40 Feb 1 14:19:28 sit-HP-Pavilion-15-Notebook-PC kernel: [ 11.080191] [813328a6] kset_register+0x46/0x70 Feb 1 14:19:28 sit-HP-Pavilion-15-Notebook-PC kernel: [ 11.080193] [81332b46] kset_create_and_add+0x76/0xb0 Feb 1 14:19:28 sit-HP-Pavilion-15-Notebook-PC kernel: [ 11.080195] [81373d4e] populate_msi_sysfs+0x2e/0x120 Feb 1 14:19:28 sit-HP-Pavilion-15-Notebook-PC kernel: [ 11.080197] [8137433f] msi_capability_init+0x12f/0x1f0 Feb 1 14:19:28 sit-HP-Pavilion-15-Notebook-PC kernel: [ 11.080199] [81374510] pci_enable_msi_block+0x90/0xe0 Feb 1 14:19:28 sit-HP-Pavilion-15-Notebook-PC kernel: [ 11.080222] [a02d9c93] KCL_RequestMSI+0x13/0x20 [fglrx] Feb 1 14:19:28 sit-HP-Pavilion-15-Notebook-PC kernel: [ 11.080254] [a02fa9ff] IRQMGR_initialize+0x24f/0x380 [fglrx] Feb 1 14:19:28 sit-HP-Pavilion-15-Notebook-PC kernel: [ 11.080285] [a02fa757] ? IRQMGR_alloc_context+0xb7/0x110 [fglrx] Feb 1 14:19:28 sit-HP-Pavilion-15-Notebook-PC kernel: [ 11.080317] [a02f992e] ? irqmgr_wrap_initialize+0x1e/0xb0 [fglrx] Feb 1 14:19:28 sit-HP-Pavilion-15-Notebook-PC kernel: [ 11.080348] [a02fa5c5] ? firegl_irqmgr_init+0x55/0x100 [fglrx] Feb 1 14:19:28 sit-HP-Pavilion-15-Notebook-PC kernel: [ 11.080381] [a030b3ff] ? hal_init_gpu+0x1cf/0x480 [fglrx] Feb 1 14:19:28 sit-HP-Pavilion-15-Notebook-PC kernel: [ 11.080409] [a02e687b] ? firegl_open+0x2db/0x310 [fglrx] Feb 1 14:19:28 sit-HP-Pavilion-15-Notebook-PC kernel: [ 11.080430] [a02d6b27] ? ip_firegl_open+0x17/0x20 [fglrx] Feb 1 14:19:28 sit-HP-Pavilion-15-Notebook-PC kernel: [ 11.080450] [a02d5f7e] ? firegl_stub_open+0xae/0x120 [fglrx] Feb 1 14:19:28 sit-HP-Pavilion-15-Notebook-PC kernel: [ 11.080453] [8118bd92] ? chrdev_open+0xb2/0x1a0 Feb 1 14:19:28 sit-HP-Pavilion-15-Notebook-PC kernel: [ 11.080455] [8118bce0] ? cdev_put+0x30/0x30 Feb 1 14:19:28 sit-HP-Pavilion-15-Notebook-PC kernel: [ 11.080457] [811855ee] ? do_dentry_open+0x22e/0x2b0 Feb 1 14:19:28 sit-HP-Pavilion-15-Notebook-PC kernel: [ 11.080459] [81186b48] ? __dentry_open+0x18/0x70 Feb 1 14:19:28 sit-HP-Pavilion-15-Notebook-PC kernel: [ 11.080461] [81186bdd] ? vfs_open+0x3d/0x40 Feb 1 14:19:28 sit-HP-Pavilion-15-Notebook-PC kernel: [
[Desktop-packages] [Bug 885989] Re: white screen on second monitor when using two xsessions
Hi Alberts, Thanks for that note. Apparently this does not work with hybrid graphics, so I'm going to have to get another machine to test. https://bugs.launchpad.net/ubuntu/+source/fglrx-installer/+bug/1174278 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/885989 Title: white screen on second monitor when using two xsessions Status in Nautilus: Confirmed Status in “nautilus” package in Ubuntu: Triaged Status in “nautilus” source package in Precise: Triaged Bug description: If enable dual head mode (two X screens), the second monitor went white after login with unity or unity-2d. After tracking the gnome- session, it is caused by running nautilus -n for this configuration. And if kill the nautilus process, the desktop showed up normally on second screen. lsb_release -rd Description:Ubuntu 11.10 Release:11.10 apt-cache policy nautilus nautilus: Installed: 1:3.2.1-0ubuntu2 Candidate: 1:3.2.1-0ubuntu2 Version table: *** 1:3.2.1-0ubuntu2 0 500 http://cn.archive.ubuntu.com/ubuntu/ oneiric-updates/main amd64 Packages 100 /var/lib/dpkg/status 1:3.2.0-0ubuntu5 0 500 http://cn.archive.ubuntu.com/ubuntu/ oneiric/main amd64 Packages To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/885989/+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 1186917] Re: [Dell Inspiron 5435] unsupported hardware watermark appears when fglrx installed on 12.04.2
** Changed in: amd Assignee: (unassigned) = Jammy Zhou (jammy-zhou) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to fglrx-installer in Ubuntu. https://bugs.launchpad.net/bugs/1186917 Title: [Dell Inspiron 5435] unsupported hardware watermark appears when fglrx installed on 12.04.2 Status in amd: New Status in “fglrx-installer” package in Ubuntu: Triaged Bug description: trying to enable glx support by installing fglrx, after installed by using jockey, now unity can work properly with glx function normally, however there is an extra watermark on bottom-right corner. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: fglrx (not installed) ProcVersionSignature: Ubuntu 3.5.0-23.35~precise1-generic 3.5.7.2 Uname: Linux 3.5.0-23-generic x86_64 NonfreeKernelModules: fglrx .tmp.unity.support.test.0: ApportVersion: 2.0.1-0ubuntu17.1 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] CompositorRunning: compiz Date: Mon Jun 3 03:59:32 2013 DistUpgraded: Fresh install DistroCodename: precise DistroVariant: ubuntu DkmsStatus: fglrx-experimental-12, 12.100, 3.5.0-23-generic, x86_64: installed GraphicsCard: Advanced Micro Devices [AMD] nee ATI Device [1002:999a] (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:05c6] Subsystem: Dell Device [1028:05c7] InstallationMedia: Ubuntu 12.04.2 LTS Precise Pangolin - Release amd64 (20130213) JockeyStatus: kmod:fglrx_experimental_12 - ATI Fire GL (Proprietary, Enabled, Not in use) xorg:fglrx_experimental_9 - ATI/AMD proprietary FGLRX graphics driver (**experimental** beta) (Proprietary, Disabled, Not in use) MachineType: Dell Inc. Inspiron 5435 MarkForUpload: True ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-23-generic root=UUID=a6892c0c-3a90-4214-9f0a-d3ea9bbe2023 ro quiet splash initcall_debug vt.handoff=7 SourcePackage: fglrx-installer UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/08/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: X19 dmi.board.name: Inspiron 5435 dmi.board.vendor: Dell Inc. dmi.board.version: X19 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvrX19:bd03/08/2013:svnDellInc.:pnInspiron5435:pvrNotSpecified:rvnDellInc.:rnInspiron5435:rvrX19:cvnDellInc.:ct8:cvrNotSpecified: dmi.product.name: Inspiron 5435 dmi.product.version: Not Specified dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.7.12-0ubuntu1 version.fglrx-installer: fglrx-installer N/A version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.39-0ubuntu0.1 version.libgl1-mesa-dri: libgl1-mesa-dri N/A version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A To manage notifications about this bug go to: https://bugs.launchpad.net/amd/+bug/1186917/+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 1041032] Re: An error occurred Location not found after automatically installing the missing gstreamer plugins.
** Changed in: totem (Ubuntu) Status: In Progress = Won't Fix ** Changed in: totem (Ubuntu Quantal) Status: In Progress = Won't Fix -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to totem in Ubuntu. https://bugs.launchpad.net/bugs/1041032 Title: An error occurred Location not found after automatically installing the missing gstreamer plugins. Status in Totem Movie Player: New Status in “totem” package in Ubuntu: Won't Fix Status in “totem” source package in Quantal: Won't Fix Bug description: Ubuntu: 12.04 totem: 3.0.1-0ubuntu21 There is a feature of totem that it can detect the missing gstreamer plugins and install them automatically. It will pop out this message after it finished the installation of gstreamer plugins. However totem will work normally after we reopen it. Reproduce steps: 1. Remove gstreamer0.10-ffmpeg and gstreamer0.10-plugins-ugly if they are installed. 2. Download Wildlife.wmv from http://archive.org/details/Windows7WildlifeSampleVideo 3. Open Wildlife.wmv by totem. Relative to Bug #1041287. To manage notifications about this bug go to: https://bugs.launchpad.net/totem/+bug/1041032/+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've confirmed that these two branches work on a machine with the micmute button. -- 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 “xkeyboard-config” 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 Released Status in “udev” source package in Precise: Fix Released Status in “x11proto-core” source package in Precise: Fix Released Status in “xkeyboard-config” source package in Precise: New 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 “xkeyboard-config” 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)
Fixed released as in bug 1193147. ** Changed in: udev (Ubuntu Precise) Status: New = Fix Released -- 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 “xkeyboard-config” 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 Released Status in “udev” source package in Precise: Fix Released Status in “x11proto-core” source package in Precise: Fix Released Status in “xkeyboard-config” source package in Precise: New 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 “xkeyboard-config” 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)
Subscribed sponsors and submitted the remaining packages for merge requests. -- 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 “xkeyboard-config” 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 Released Status in “udev” source package in Precise: Fix Released Status in “x11proto-core” source package in Precise: Fix Released Status in “xkeyboard-config” source package in Precise: New 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 “xkeyboard-config” 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 1212425] Re: SDK applications require /tmp access with nvidia (should honor TMPDIR)
Nvidia has fixed the problem. The driver has not been publically released yet. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-319 in Ubuntu. https://bugs.launchpad.net/bugs/1212425 Title: SDK applications require /tmp access with nvidia (should honor TMPDIR) Status in “apparmor-easyprof-ubuntu” package in Ubuntu: Fix Released Status in “nvidia-graphics-drivers-319” package in Ubuntu: New Status in “nvidia-graphics-drivers-tegra” package in Ubuntu: New Status in “nvidia-graphics-drivers-tegra3” package in Ubuntu: New Status in “apparmor-easyprof-ubuntu” source package in Saucy: Fix Released Status in “nvidia-graphics-drivers-319” source package in Saucy: New Status in “nvidia-graphics-drivers-tegra” source package in Saucy: New Status in “nvidia-graphics-drivers-tegra3” source package in Saucy: New Bug description: Nvidia desktop users need the following AppArmor permissions to avoid denials: owner /tmp/gl* mrw, But this rule breaks application confinement such that apps are able to tamper with each other. Interestingly, apps still run without the rule, so we can explicitly deny it for now. The use of /tmp is apparently hardcoded and does not honor TMPDIR (application confinement will setup TMPDIR to a private area for the app). strace confirms this: 24603 mkdir(/tmp, 0777) = -1 EEXIST (File exists) 24603 open(/tmp/glBRPYmm, O_RDWR|O_CREAT|O_EXCL, 0600) = -1 EACCES (Permission denied) While the use of O_EXCL is safe, we don't allow access to /tmp for confined apps and libraries/applications should always honor TMPDIR. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor-easyprof-ubuntu/+bug/1212425/+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 have verified by compile testing a version of g-s-d that uses XF86AudioMicMute. -- 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 881526] Re: System freezes, kernel crashes, [fglrx] ASIC hang happened
** Changed in: amd Status: In Progress = Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to fglrx-installer in Ubuntu. https://bugs.launchpad.net/bugs/881526 Title: System freezes, kernel crashes, [fglrx] ASIC hang happened Status in amd: Fix Released Status in AMD fglrx video driver: Won't Fix Status in HWE Next Project: Fix Committed Status in OEM Priority Project: Invalid Status in “fglrx-installer” package in Ubuntu: Confirmed Bug description: The system freezes intermittently and the kernel crashes a few seconds later. This has only happened since upgrading to 11.10. Found the following error in /var/log/kern.log which coincides: Oct 25 14:53:46 lt9630 kernel: [ 737.900416] INFO: rcu_sched_state detected stall on CPU 2 (t=15000 jiffies) Oct 25 14:55:46 lt9630 kernel: [ 857.813946] [fglrx] ASIC hang happened Oct 25 14:55:46 lt9630 kernel: [ 857.813950] Pid: 1149, comm: Xorg Tainted: P C 3.0.0-12-generic #20-Ubuntu Oct 25 14:55:46 lt9630 kernel: [ 857.813951] Call Trace: Oct 25 14:55:46 lt9630 kernel: [ 857.813985] [a00a0d7e] KCL_DEBUG_OsDump+0xe/0x10 [fglrx] Oct 25 14:55:46 lt9630 kernel: [ 857.814003] [a00ae20c] firegl_hardwareHangRecovery+0x1c/0x50 [fglrx] Oct 25 14:55:46 lt9630 kernel: [ 857.814036] [a013ad59] ? _ZN4Asic9WaitUntil15ResetASICIfHungEv+0x9/0x10 [fglrx] Oct 25 14:55:46 lt9630 kernel: [ 857.814068] [a013ad0c] ? _ZN4Asic9WaitUntil15WaitForCompleteEv+0x6c/0xb0 [fglrx] Oct 25 14:55:46 lt9630 kernel: [ 857.814099] [a0135fb4] ? _ZN15ExecutableUnits10CPRingIdleE15idle_WaitMethod12_QS_CP_RING_+0xe4$ Oct 25 14:55:46 lt9630 kernel: [ 857.814127] [a0115acb] ? _ZN10CMMSurfaceD1Ev+0xcb/0xe0 [fglrx] Oct 25 14:55:46 lt9630 kernel: [ 857.814158] [a0135e7b] ? _ZN15ExecutableUnits7PM4idleE15idle_WaitMethod+0x4b/0x90 [fglrx] Oct 25 14:55:46 lt9630 kernel: [ 857.814187] [a012e8f1] ? _ZN15QS_PRIVATE_CORE9QsPM4idleE15idle_WaitMethod+0x31/0x60 [fglrx] Oct 25 14:55:46 lt9630 kernel: [ 857.814215] [a0119d8a] ? _ZN10QS_PRIVATE11synchronizeEv+0x2a/0x30 [fglrx] Oct 25 14:55:46 lt9630 kernel: [ 857.814243] [a01233f5] ? _Z8uCWDDEQCmjjPvjS_+0x3b5/0x10c0 [fglrx] Oct 25 14:55:46 lt9630 kernel: [ 857.814246] [810871ee] ? down+0x2e/0x50 Oct 25 14:55:46 lt9630 kernel: [ 857.814266] [a00cc932] ? firegl_cmmqs_CWDDE_32+0x332/0x440 [fglrx] Oct 25 14:55:46 lt9630 kernel: [ 857.814285] [a00cb260] ? firegl_cmmqs_CWDDE32+0x70/0x100 [fglrx] Oct 25 14:55:46 lt9630 kernel: [ 857.814288] [81282e5a] ? security_capable+0x2a/0x30 Oct 25 14:55:46 lt9630 kernel: [ 857.814306] [a00cb1f0] ? firegl_cmmqs_createdriver+0x170/0x170 [fglrx] Oct 25 14:55:46 lt9630 kernel: [ 857.814322] [a00a9e18] ? firegl_ioctl+0x1e8/0x250 [fglrx] Oct 25 14:55:46 lt9630 kernel: [ 857.814333] [a009a9be] ? ip_firegl_unlocked_ioctl+0xe/0x20 [fglrx] Oct 25 14:55:46 lt9630 kernel: [ 857.814335] [8117939a] ? do_vfs_ioctl+0x8a/0x340 Oct 25 14:55:46 lt9630 kernel: [ 857.814338] [811679ed] ? vfs_read+0x10d/0x180 Oct 25 14:55:46 lt9630 kernel: [ 857.814339] [811796e1] ? sys_ioctl+0x91/0xa0 Oct 25 14:55:46 lt9630 kernel: [ 857.814342] [815f22c2] ? system_call_fastpath+0x16/0x1b Oct 25 14:55:46 lt9630 kernel: [ 857.814345] pubdev:0xa02fd600, num of device:1 , name:fglrx, major 8, minor 88. Oct 25 14:55:46 lt9630 kernel: [ 857.814346] device 0 : 0x88019b85 . Oct 25 14:55:46 lt9630 kernel: [ 857.814345] pubdev:0xa02fd600, num of device:1 , name:fglrx, major 8, minor 88. Oct 25 14:55:46 lt9630 kernel: [ 857.814346] device 0 : 0x88019b85 . Oct 25 14:55:46 lt9630 kernel: [ 857.814348] Asic ID:0x6779, revision:0x3c, MMIOReg:0xc90012b8. Oct 25 14:55:46 lt9630 kernel: [ 857.814349] FB phys addr: 0xc000, MC :0xf, Total FB size :0x4000. Oct 25 14:55:46 lt9630 kernel: [ 857.814351] gart table MC:0xf0f8fd000, Physical:0xcf8fd000, size:0x402000. Oct 25 14:55:46 lt9630 kernel: [ 857.814353] mc_node :FB, total 1 zones Oct 25 14:55:46 lt9630 kernel: [ 857.814354] MC start:0xf, Physical:0xc000, size:0xfd0. Oct 25 14:55:46 lt9630 kernel: [ 857.814356] Mapped heap -- Offset:0x0, size:0xf8fd000, reference count:33, mapping count:0, Oct 25 14:55:46 lt9630 kernel: [ 857.814357] Mapped heap -- Offset:0x0, size:0x100, reference count:1, mapping count:0, Oct 25 14:55:46 lt9630 kernel: [ 857.814359] Mapped heap -- Offset:0xf8fd000, size:0x403000, reference count:1, mapping count:0, Oct 25 14:55:46 lt9630 kernel: [ 857.814360] mc_node :INV_FB, total 1 zones Oct 25 14:55:46 lt9630 kernel: [ 857.814362] MC start:0xf0fd0, Physical:0xcfd0, size:0x3030. Oct
[Desktop-packages] [Bug 408903] Re: Does not handle microphone mute button (KEY_MICMUTE)
Sebastien, Thanks for flipping the tag. As noted in comment #108 , we still need backports of udev, gnome-settings-daemon, and xkeyboard-config to close this bug out. Additionally, this requires a revert of xkeyboard-config that we have in -proposed. I'm not sure how to work that because this is my first verification-failed bug, but I assume I can just revert it. https://code.launchpad.net/~jm-leddy/ubuntu/precise/xkeyboard- config/micmute We have two vendors in addition to Lenovo that have added micmute keys since this bug has been opened, and we're shipping 12.04 as the standard for all oem builds. So this bug has a higher priority now. -- 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 1158296] Re: Systems with AMD 6660 discrete will hang up while doing poweroff and reboot tests by pm_test tool.
** Changed in: amd Status: New = Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to fglrx-installer in Ubuntu. https://bugs.launchpad.net/bugs/1158296 Title: Systems with AMD 6660 discrete will hang up while doing poweroff and reboot tests by pm_test tool. Status in amd: Incomplete Status in “fglrx-installer” package in Ubuntu: New Bug description: Steps to Reproduce: 1. GM -B21 image, go through OOBE,boot into OS. 2. Copy pm_test file to Home Folder, open terminal to run sudo python pm_test -r 30 poweroff command. 3. After 20 minutes, find system hang up with backlight off. Oops: Feb 1 14:19:28 sit-HP-Pavilion-15-Notebook-PC kernel: [ 11.080151] Hardware name: HP Pavilion 15 Notebook PC Feb 1 14:19:28 sit-HP-Pavilion-15-Notebook-PC kernel: [ 11.080152] kobject_add_internal failed for msi_irqs with -EEXIST, don't try to register things with the same name in the same directory. Feb 1 14:19:28 sit-HP-Pavilion-15-Notebook-PC kernel: [ 11.080153] Modules linked in: fglrx(PO) amd_iommu_v2 snd_hda_codec_hdmi(O) snd_hda_codec_realtek(O) coretemp kvm ghash_clmulni_intel cryptd joydev hp_wmi sparse_keymap dm_multipath scsi_dh microcode snd_hda_intel(O) snd_hda_codec(O) snd_hwdep hp_accel snd_pcm lis3lv02d input_polldev uvcvideo videobuf2_core videodev videobuf2_vmalloc videobuf2_memops snd_seq_midi snd_rawmidi snd_seq_midi_event snd_seq wmi(O) rfcomm snd_timer snd_seq_device mac_hid psmouse serio_raw i915 snd drm_kms_helper parport_pc bnep drm soundcore i2c_algo_bit ppdev lpc_ich bluetooth video snd_page_alloc mei lp parport binfmt_misc r8169 dm_raid45 xor dm_mirror dm_region_hash dm_log btrfs zlib_deflate libcrc32c [last unloaded: amd_iommu_v2] Feb 1 14:19:28 sit-HP-Pavilion-15-Notebook-PC kernel: [ 11.080177] Pid: 1328, comm: Xorg Tainted: P W O 3.5.0-22-generic #33~precise1-Ubuntu Feb 1 14:19:28 sit-HP-Pavilion-15-Notebook-PC kernel: [ 11.080178] Call Trace: Feb 1 14:19:28 sit-HP-Pavilion-15-Notebook-PC kernel: [ 11.080180] [81052c9f] warn_slowpath_common+0x7f/0xc0 Feb 1 14:19:28 sit-HP-Pavilion-15-Notebook-PC kernel: [ 11.080182] [81052d96] warn_slowpath_fmt+0x46/0x50 Feb 1 14:19:28 sit-HP-Pavilion-15-Notebook-PC kernel: [ 11.080185] [811f8dee] ? release_sysfs_dirent+0x7e/0x100 Feb 1 14:19:28 sit-HP-Pavilion-15-Notebook-PC kernel: [ 11.080187] [81332594] kobject_add_internal+0x1f4/0x210 Feb 1 14:19:28 sit-HP-Pavilion-15-Notebook-PC kernel: [ 11.080189] [81332ac8] ? kobject_set_name+0x38/0x40 Feb 1 14:19:28 sit-HP-Pavilion-15-Notebook-PC kernel: [ 11.080191] [813328a6] kset_register+0x46/0x70 Feb 1 14:19:28 sit-HP-Pavilion-15-Notebook-PC kernel: [ 11.080193] [81332b46] kset_create_and_add+0x76/0xb0 Feb 1 14:19:28 sit-HP-Pavilion-15-Notebook-PC kernel: [ 11.080195] [81373d4e] populate_msi_sysfs+0x2e/0x120 Feb 1 14:19:28 sit-HP-Pavilion-15-Notebook-PC kernel: [ 11.080197] [8137433f] msi_capability_init+0x12f/0x1f0 Feb 1 14:19:28 sit-HP-Pavilion-15-Notebook-PC kernel: [ 11.080199] [81374510] pci_enable_msi_block+0x90/0xe0 Feb 1 14:19:28 sit-HP-Pavilion-15-Notebook-PC kernel: [ 11.080222] [a02d9c93] KCL_RequestMSI+0x13/0x20 [fglrx] Feb 1 14:19:28 sit-HP-Pavilion-15-Notebook-PC kernel: [ 11.080254] [a02fa9ff] IRQMGR_initialize+0x24f/0x380 [fglrx] Feb 1 14:19:28 sit-HP-Pavilion-15-Notebook-PC kernel: [ 11.080285] [a02fa757] ? IRQMGR_alloc_context+0xb7/0x110 [fglrx] Feb 1 14:19:28 sit-HP-Pavilion-15-Notebook-PC kernel: [ 11.080317] [a02f992e] ? irqmgr_wrap_initialize+0x1e/0xb0 [fglrx] Feb 1 14:19:28 sit-HP-Pavilion-15-Notebook-PC kernel: [ 11.080348] [a02fa5c5] ? firegl_irqmgr_init+0x55/0x100 [fglrx] Feb 1 14:19:28 sit-HP-Pavilion-15-Notebook-PC kernel: [ 11.080381] [a030b3ff] ? hal_init_gpu+0x1cf/0x480 [fglrx] Feb 1 14:19:28 sit-HP-Pavilion-15-Notebook-PC kernel: [ 11.080409] [a02e687b] ? firegl_open+0x2db/0x310 [fglrx] Feb 1 14:19:28 sit-HP-Pavilion-15-Notebook-PC kernel: [ 11.080430] [a02d6b27] ? ip_firegl_open+0x17/0x20 [fglrx] Feb 1 14:19:28 sit-HP-Pavilion-15-Notebook-PC kernel: [ 11.080450] [a02d5f7e] ? firegl_stub_open+0xae/0x120 [fglrx] Feb 1 14:19:28 sit-HP-Pavilion-15-Notebook-PC kernel: [ 11.080453] [8118bd92] ? chrdev_open+0xb2/0x1a0 Feb 1 14:19:28 sit-HP-Pavilion-15-Notebook-PC kernel: [ 11.080455] [8118bce0] ? cdev_put+0x30/0x30 Feb 1 14:19:28 sit-HP-Pavilion-15-Notebook-PC kernel: [ 11.080457] [811855ee] ? do_dentry_open+0x22e/0x2b0 Feb 1 14:19:28 sit-HP-Pavilion-15-Notebook-PC kernel: [ 11.080459] [81186b48] ? __dentry_open+0x18/0x70 Feb 1 14:19:28 sit-HP-Pavilion-15-Notebook-PC kernel: [ 11.080461] [81186bdd] ? vfs_open+0x3d/0x40 Feb 1 14:19:28 sit-HP-Pavilion-15-Notebook-PC kernel: [ 11.080463] [81186d28] ?
[Desktop-packages] [Bug 880079] Re: bluetooth-applet crashes when trying to browse device
** Changed in: gnome-bluetooth (Ubuntu) Status: In Progress = Won't Fix -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-bluetooth in Ubuntu. https://bugs.launchpad.net/bugs/880079 Title: bluetooth-applet crashes when trying to browse device Status in GNOME Bluetooth: Expired Status in OEM Priority Project: Opinion Status in OEM Priority Project oneiric series: Fix Released Status in OEM Priority Project precise series: Invalid Status in OEM Priority Project quantal series: Opinion Status in “gnome-bluetooth” package in Ubuntu: Won't Fix Bug description: When trying to browse a device using the bluetooth applet, it crashes. Steps to reproduce: 1. In the bluetooth applet, choose “Browse files on device...” 2. Select the device and click “Browse” The applet does not crash when using the device submenu “Device → Browse files...”. It still fails to browse. ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: gnome-bluetooth 3.2.0-0ubuntu2 ProcVersionSignature: Ubuntu 3.0.0-12.20-generic 3.0.4 Uname: Linux 3.0.0-12-generic i686 ApportVersion: 1.23-0ubuntu3 Architecture: i386 Date: Sat Oct 22 22:23:40 2011 InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Alpha i386 (20110803.1) SourcePackage: gnome-bluetooth UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-bluetooth/+bug/880079/+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)
** Changed in: libx11 (Ubuntu Precise) Status: New = In Progress -- 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: In Progress 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 1032433] Re: Using WEP 128-bit Passphrase, Ad-hoc connection cannot be established
Franz, 12345 from the server side looks like a 40 bit key (8 bits per character, multiplied by 5 characters). This would explain why it's working when you use that option. In order to be completely sure that it's not a 40 bit key, would you please re-create your server environment with a WEP-128 passphrase of something like '123456'? Thank you. More information here: https://mail.gnome.org/archives/networkmanager- list/2007-December/msg00226.html ** Changed in: network-manager (Ubuntu) Status: Confirmed = Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1032433 Title: Using WEP 128-bit Passphrase, Ad-hoc connection cannot be established Status in OEM Priority Project: New Status in OEM Priority Project precise series: New Status in “network-manager” package in Ubuntu: Incomplete Bug description: When setting up an ad-hoc wifi connection, if choose WEP 128-bit Passphrase, the connection cannot be established. If choose None or WEP 40/128-bit Key, it can be established successfully. Steps to reproduce: 1. Choose Create new Wireless Network in network applet 2. Choose WEP 128-bit Passphrase and create an ad-hoc connection 3. Use another computer to connect the same ad-hoc ESSID 4. The connection cannot be established To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1032433/+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)
We don't any changes to xserver-xorg-input-evdev in order to fix this problem. Marking as Won't Fix. ** Changed in: xserver-xorg-input-evdev (Ubuntu) Status: Triaged = Won't Fix ** Changed in: xserver-xorg-input-evdev (Ubuntu Precise) Status: New = Won't Fix ** Changed in: xserver-xorg-input-evdev (Ubuntu Raring) Status: Triaged = Won't Fix -- 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: New 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)
Thanks Ian, Waiting for it to hit -proposed to test. -- 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: Triaged Status in “gnome-settings-daemon” source package in Precise: New Status in “libx11” source package in Precise: New 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: New 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: 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 1011073] Re: NetworkManager submenus sometimes unpopulated
** Changed in: oem-priority/quantal Status: New = Won't Fix ** Changed in: oem-priority/raring Status: In Progress = Won't Fix -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager-applet in Ubuntu. https://bugs.launchpad.net/bugs/1011073 Title: NetworkManager submenus sometimes unpopulated Status in DBus Menu: New Status in OEM Priority Project: In Progress Status in OEM Priority Project precise series: In Progress Status in OEM Priority Project quantal series: Won't Fix Status in OEM Priority Project raring series: Won't Fix Status in “libdbusmenu” package in Ubuntu: Fix Released Status in “network-manager-applet” package in Ubuntu: Invalid Status in “libdbusmenu” source package in Precise: Fix Committed Status in “network-manager-applet” source package in Precise: Invalid Status in “libdbusmenu” source package in Quantal: Triaged Status in “network-manager-applet” source package in Quantal: Invalid Status in “libdbusmenu” source package in Raring: Fix Committed Status in “network-manager-applet” source package in Raring: Invalid Bug description: [Impact] * Affected applications with a high number of menu updates reach the maximum value allowed for the ID of a menuitem, and rejects further menu changes. Because the application underneath the menu has already removed the underlying actual GtkMenuItem objects, it is impossible to activate the items -- to effect the actions linked to the menuitems. * Some indicators have a relatively high and climbing memory usage due to the way they build menus to be displayed in the panel. [Test Case] * Run nm-applet for a while (multiple days without shutdown, without killing the application), notice whether the menus are still usable. * Run indicators for a while, observe memory usage. [Regression Potential] Indicators with a very high amount of updates may be affected as circling back past the maximum value, if a new menu item is created with an ID still in use by a menuitem that has not been removed yet, neither or only one of the two menu items might be available to be clicked -- this could confuse users or cause error messages to be displayed. Risk is low however since network-manager-gnome (nm-applet) is currently the application with the most menu updates. [Other Info] Submenus in Network Manager are sometimes unusable as they are not populated. This happens both with the list of available networks and with the VPN list. When the bug happens, it occurs for *both* the wireless submenu and the VPN menu. I know there are entries for those submenus as I can see them with other network UI mechanisms. The issue is intermittent. Expected: Dropping down the menu then hovering over the submenu trigger-point (example: More networks) shows the additional expected entries (example: more wifi networks to choose from). Actual: Dropping down the menu and hovering over the submenu trigger displays a submenu but the submenu has nothing in it and is unusable. Ubuntu 12.04 network-manager 0.9.4.0-0ubuntu4.1 Apple Macbook Pro 8,1 03:00.0 Network controller: Broadcom Corporation BCM4331 802.11a/b/g/n (rev 02) 02:00.0 Ethernet controller: Broadcom Corporation NetXtreme BCM57765 Gigabit Ethernet PCIe (rev 10) To manage notifications about this bug go to: https://bugs.launchpad.net/libdbusmenu/+bug/1011073/+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)
Per comment #109, I've added libx11 as a component. Additionally, I'm re-subbing -sponsors so that they will see this request. All we need is a rebuild of the package with the latest x11proto-core. ** Also affects: libx11 (Ubuntu) Importance: Undecided Status: New ** Changed in: libx11 (Ubuntu) Status: New = Confirmed -- 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: Triaged Status in “gnome-settings-daemon” source package in Precise: New Status in “libx11” source package in Precise: New 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: New 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: 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 1011073] Re: NetworkManager submenus sometimes unpopulated
** Tags removed: verification-done ** Tags added: verification-needed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager-applet in Ubuntu. https://bugs.launchpad.net/bugs/1011073 Title: NetworkManager submenus sometimes unpopulated Status in DBus Menu: New Status in OEM Priority Project: In Progress Status in OEM Priority Project precise series: In Progress Status in OEM Priority Project quantal series: New Status in OEM Priority Project raring series: In Progress Status in “libdbusmenu” package in Ubuntu: Fix Released Status in “network-manager-applet” package in Ubuntu: Invalid Status in “libdbusmenu” source package in Precise: Fix Committed Status in “network-manager-applet” source package in Precise: Invalid Status in “libdbusmenu” source package in Quantal: Triaged Status in “network-manager-applet” source package in Quantal: Invalid Status in “libdbusmenu” source package in Raring: Fix Committed Status in “network-manager-applet” source package in Raring: Invalid Bug description: [Impact] * Affected applications with a high number of menu updates reach the maximum value allowed for the ID of a menuitem, and rejects further menu changes. Because the application underneath the menu has already removed the underlying actual GtkMenuItem objects, it is impossible to activate the items -- to effect the actions linked to the menuitems. * Some indicators have a relatively high and climbing memory usage due to the way they build menus to be displayed in the panel. [Test Case] * Run nm-applet for a while (multiple days without shutdown, without killing the application), notice whether the menus are still usable. * Run indicators for a while, observe memory usage. [Regression Potential] Indicators with a very high amount of updates may be affected as circling back past the maximum value, if a new menu item is created with an ID still in use by a menuitem that has not been removed yet, neither or only one of the two menu items might be available to be clicked -- this could confuse users or cause error messages to be displayed. Risk is low however since network-manager-gnome (nm-applet) is currently the application with the most menu updates. [Other Info] Submenus in Network Manager are sometimes unusable as they are not populated. This happens both with the list of available networks and with the VPN list. When the bug happens, it occurs for *both* the wireless submenu and the VPN menu. I know there are entries for those submenus as I can see them with other network UI mechanisms. The issue is intermittent. Expected: Dropping down the menu then hovering over the submenu trigger-point (example: More networks) shows the additional expected entries (example: more wifi networks to choose from). Actual: Dropping down the menu and hovering over the submenu trigger displays a submenu but the submenu has nothing in it and is unusable. Ubuntu 12.04 network-manager 0.9.4.0-0ubuntu4.1 Apple Macbook Pro 8,1 03:00.0 Network controller: Broadcom Corporation BCM4331 802.11a/b/g/n (rev 02) 02:00.0 Ethernet controller: Broadcom Corporation NetXtreme BCM57765 Gigabit Ethernet PCIe (rev 10) To manage notifications about this bug go to: https://bugs.launchpad.net/libdbusmenu/+bug/1011073/+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 951000] Re: disable guest session screen lock using gsettings
** Also affects: oem-priority/precise Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/951000 Title: disable guest session screen lock using gsettings Status in OEM Priority Project: Confirmed Status in OEM Priority Project precise series: New Status in “lightdm” package in Ubuntu: Fix Released Status in “lightdm” source package in Precise: Triaged Status in “lightdm” source package in Raring: Fix Committed Bug description: * Impact: sometime screen locking doesn't get disabled in guest session * Test Case: - log into a guest session - try locking the screen screen locking should be disabled * Impact: check that screen locking is well disabled in guest sessions To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/951000/+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 1011073] Re: NetworkManager submenus sometimes unpopulated
** Tags removed: verification-needed ** Tags added: verification-done -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager-applet in Ubuntu. https://bugs.launchpad.net/bugs/1011073 Title: NetworkManager submenus sometimes unpopulated Status in DBus Menu: New Status in OEM Priority Project: In Progress Status in OEM Priority Project precise series: In Progress Status in OEM Priority Project quantal series: New Status in OEM Priority Project raring series: In Progress Status in “libdbusmenu” package in Ubuntu: Fix Released Status in “network-manager-applet” package in Ubuntu: Invalid Status in “libdbusmenu” source package in Precise: Fix Committed Status in “network-manager-applet” source package in Precise: Invalid Status in “libdbusmenu” source package in Quantal: Triaged Status in “network-manager-applet” source package in Quantal: Invalid Status in “libdbusmenu” source package in Raring: Fix Committed Status in “network-manager-applet” source package in Raring: Invalid Bug description: [Impact] * Affected applications with a high number of menu updates reach the maximum value allowed for the ID of a menuitem, and rejects further menu changes. Because the application underneath the menu has already removed the underlying actual GtkMenuItem objects, it is impossible to activate the items -- to effect the actions linked to the menuitems. * Some indicators have a relatively high and climbing memory usage due to the way they build menus to be displayed in the panel. [Test Case] * Run nm-applet for a while (multiple days without shutdown, without killing the application), notice whether the menus are still usable. * Run indicators for a while, observe memory usage. [Regression Potential] Indicators with a very high amount of updates may be affected as circling back past the maximum value, if a new menu item is created with an ID still in use by a menuitem that has not been removed yet, neither or only one of the two menu items might be available to be clicked -- this could confuse users or cause error messages to be displayed. Risk is low however since network-manager-gnome (nm-applet) is currently the application with the most menu updates. [Other Info] Submenus in Network Manager are sometimes unusable as they are not populated. This happens both with the list of available networks and with the VPN list. When the bug happens, it occurs for *both* the wireless submenu and the VPN menu. I know there are entries for those submenus as I can see them with other network UI mechanisms. The issue is intermittent. Expected: Dropping down the menu then hovering over the submenu trigger-point (example: More networks) shows the additional expected entries (example: more wifi networks to choose from). Actual: Dropping down the menu and hovering over the submenu trigger displays a submenu but the submenu has nothing in it and is unusable. Ubuntu 12.04 network-manager 0.9.4.0-0ubuntu4.1 Apple Macbook Pro 8,1 03:00.0 Network controller: Broadcom Corporation BCM4331 802.11a/b/g/n (rev 02) 02:00.0 Ethernet controller: Broadcom Corporation NetXtreme BCM57765 Gigabit Ethernet PCIe (rev 10) To manage notifications about this bug go to: https://bugs.launchpad.net/libdbusmenu/+bug/1011073/+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)
It's x11proto-core-dev, if you get stuck with that again, you can figure it out by following the link in the call to test the proposed package: https://launchpad.net/ubuntu/+source/x11proto-core/7.0.22-1ubuntu0.1 -- 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 1114872] Re: [hsw backport] kernel oops, Xorg freeze
** Also affects: oem-priority/precise Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to fglrx-installer in Ubuntu. https://bugs.launchpad.net/bugs/1114872 Title: [hsw backport] kernel oops, Xorg freeze Status in The Linux Kernel: Confirmed Status in OEM Priority Project: New Status in OEM Priority Project precise series: New Status in “fglrx-installer” package in Ubuntu: New Status in “linux” package in Ubuntu: Incomplete Status in “xserver-xorg-video-intel” package in Ubuntu: Incomplete Bug description: [ 144.450359] Process Xorg (pid: 2629, threadinfo 880043272000, task 88004094) [ 144.450429] Stack: [ 144.450450] 88006e64 880065bc6800 8800432739a8 a0adb131 [ 144.450530] 8817 8800 8133b4b4 [ 144.450608] 880043273958 0001 882e 43273968 [ 144.450686] Call Trace: [ 144.450734] [a0adb131] haswell_crtc_enable+0x531/0x6d0 [i915_hsw] [ 144.450802] [8133b4b4] ? snprintf+0x34/0x40 [ 144.450870] [a0ae1a67] intel_set_mode+0x6e7/0xa40 [i915_hsw] [ 144.450952] [a0ae25fd] intel_crtc_set_config+0x83d/0x960 [i915_hsw] [ 144.451041] [a01c5d68] drm_mode_setcrtc+0x308/0x560 [drm] [ 144.451118] [a0ad3fb3] ? intel_crtc_gamma_set+0x63/0x70 [i915_hsw] [ 144.451198] [a01b469c] drm_ioctl+0x47c/0x540 [drm] [ 144.451274] [a01c5a60] ? drm_mode_setplane+0x3b0/0x3b0 [drm] [ 144.451339] [8169e709] ? _raw_spin_unlock_bh+0x19/0x20 [ 144.451400] [8119951a] do_vfs_ioctl+0x8a/0x340 [ 144.451454] [81199861] sys_ioctl+0x91/0xa0 [ 144.451505] [816a6e69] system_call_fastpath+0x16/0x1b [ 144.451559] Code: e0 b8 b1 a0 31 c0 e8 16 e6 57 e0 e9 7f fe ff ff 90 55 48 89 e5 53 48 83 ec 08 0f 1f 44 00 00 89 f0 89 d3 48 8b 84 c7 30 22 00 00 8b 90 68 03 00 00 48 8b 07 48 8b 80 48 03 00 00 48 8b 40 08 f6 [ 144.451924] RIP [a0ad475a] assert_fdi_tx+0x1a/0xa0 [i915_hsw] [ 144.452005] RSP 880043273908 [ 144.452038] CR2: 036c ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: xorg 1:7.6+12ubuntu2~ppa10 ProcVersionSignature: Ubuntu 3.5.0-21.32~precise1-generic 3.5.7.1 Uname: Linux 3.5.0-21-generic x86_64 NonfreeKernelModules: fglrx .tmp.unity.support.test.0: ApportVersion: 2.0.1-0ubuntu17 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] CompositorRunning: compiz Date: Sun Feb 3 17:16:40 2013 DistUpgraded: Fresh install DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-watauga2-precise-amd64-norecovery-20121213-1 DistroCodename: precise DistroVariant: ubuntu ExtraDebuggingInterest: Yes, even including gdb or git bisection work if needed GpuHangFrequency: Continuously GpuHangReproducibility: Yes, I can easily reproduce it GpuHangStarted: Immediately after installing this version of Ubuntu GraphicsCard: Intel Corporation Haswell Integrated Graphics Controller [8086:0406] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Intel Corporation Device [8086:2112] Advanced Micro Devices [AMD] nee ATI Device [1002:6611] (prog-if 00 [VGA controller]) Subsystem: Intel Corporation Device [8086:2112] InstallationMedia: Ubuntu 12.04 Precise - Build amd64 LIVE Binary 20121213-14:54 MachineType: Intel Corporation Shark Bay Client platform MarkForUpload: True ProcEnviron: TERM=xterm PATH=(custom, user) LANG=C SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-21-generic root=UUID=31d7b71f-6b0a-4a24-aae5-954441657611 ro text vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/21/2012 dmi.bios.vendor: Intel Corporation dmi.bios.version: HSWLPTU1.86C.0100.R02.1211210527 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: Grays Reef dmi.board.vendor: Intel Corp. dmi.board.version: 3 dmi.chassis.asset.tag: Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnIntelCorporation:bvrHSWLPTU1.86C.0100.R02.1211210527:bd11/21/2012:svnIntelCorporation:pnSharkBayClientplatform:pvr0.1:rvnIntelCorp.:rnGraysReef:rvr3:cvnIntelCorporation:ct9:cvr0.1: dmi.product.name: Shark Bay Client platform dmi.product.version: 0.1 dmi.sys.vendor: Intel Corporation version.compiz: compiz 1:0.9.7.12-0ubuntu1 version.fglrx-installer:
[Desktop-packages] [Bug 408903] Re: Does not handle microphone mute button (KEY_MICMUTE)
Rebuilds were successful! ** Tags removed: verification-needed ** Tags added: verification-done -- 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 1068994] Re: button1 gets stuck after a while
This change looks pretty big, is there any chance that we can SRU this for precise? The reason I ask is because it's a LTS release and we have a fair amount of hardware that is failing here: http://patchwork.freedesktop.org/patch/13650/ -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1068994 Title: button1 gets stuck after a while Status in OEM Priority Project: In Progress Status in OEM Priority Project precise series: In Progress Status in OEM Priority Project raring series: In Progress Status in Ubuntu on the Nexus 7: Confirmed Status in X.Org X server: In Progress Status in “xorg-server” package in Ubuntu: Confirmed Bug description: distro bug 1015183 after using the tablet for a while, the touchscreen fails to register button clicks anymore, since the button appears to be stuck down. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1068994/+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 780602] Re: nm-applet leaks memory
Please refer to to bug 1011073. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager-applet in Ubuntu. https://bugs.launchpad.net/bugs/780602 Title: nm-applet leaks memory Status in OEM Priority Project: Fix Released Status in OEM Priority Project precise series: Fix Released Status in OEM Priority Project quantal series: Fix Released Status in “network-manager-applet” package in Ubuntu: Fix Released Status in “network-manager-applet” source package in Precise: Fix Released Status in “network-manager-applet” source package in Quantal: Fix Released Bug description: The nm-applet embedded in the task bar becomes indeterminestically unresponsive. Clicking on the applet will still show the popup menu, but none of the menu entries respond to mouse clicks. When this happens, the VPN connections and Other networks menus also show up completely empty (only a small menu stub is displayed). It is uncertain what causes this behavior. It was originally thought that the cause was memory leaks in nm-applet: nm-applet leaks memory in a fresh install of Natty, increasing to over 200 Mb in 6-8 hours. However, fixes for the memory leaks failed to resolve the occurrence of the anomalous behavior described above. dbus-monitor shows errors such as the following when clicking a menu item or attempting to access a submenu: error sender=:1.14 - dest=:1.67 error_name=org.gtk.GDBus.UnmappedGError.Quark._LIBDBUSMENU_2dGLIB.Code0 reply_serial=107705 string The IDs supplied '[80846]' do not refer to any menu items we have The errors are returned by bus_event_group or bus_about_to_show_group in libdbusmenu-glib/server.c. -- Stable Release Update Application: [Impact] This issue affects most and any users of nm-applet, especially in environments (such as offices) where the detected wireless networks change a lot, and where roaming can occur frequently. [Test Case] Run nm-applet for multiple hours: - Observe that the VPN Connections submenu still opens and lists connections (if VPN connections are configured) - Observe that the More networks submenu for additional detected wireless networks still opens and lists networks. A common failure case is where such a submenu will open but show an empty list (a piece of menu a few milimeters long). [Regression Potential] Minimal, the fixes have been available for a while in the development release (and in other recent releases) with no regressions; furthermore, this corrects obviously wrong memory handling without changing the effective behavior of the application. Possible issues could be introducing new memory leaks with the changes however, and although the risk is minimal, this could cause the same failure behavior as listed above under [Test Case]. -- ProblemType: Bug DistroRelease: Ubuntu 11.04 Package: network-manager-gnome 0.8.4~git.20110318t152954.9c4c9a0-0ubuntu1 ProcVersionSignature: Ubuntu 2.6.38-9.43-generic-pae 2.6.38.4 Uname: Linux 2.6.38-9-generic-pae i686 NonfreeKernelModules: nvidia Architecture: i386 CRDA: Error: [Errno 2] No such file or directory Date: Tue May 10 11:53:09 2011 EcryptfsInUse: Yes IfupdownConfig: auto lo iface lo inet loopback InstallationMedia: Ubuntu 11.04 Natty Narwhal - Beta i386 (20110413) IpRoute: 192.168.2.0/24 dev eth0 proto kernel scope link src 192.168.2.12 metric 1 169.254.0.0/16 dev eth0 scope link metric 1000 default via 192.168.2.1 dev eth0 proto static Keyfiles: Error: [Errno 2] No such file or directory NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true ProcEnviron: LANGUAGE=en_CA:en PATH=(custom, user) LANG=en_CA.UTF-8 SHELL=/bin/bash SourcePackage: network-manager-applet UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/780602/+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
Re: [Desktop-packages] [Bug 780602] Re: nm-applet leaks memory
On 06/26/2013 07:58 AM, Jamie Boyle wrote: I've had this problem of visible but unresponsive nm-applet in 12.10 and 13.04 (upgraded about a week ago), since removing Windows for 12.10 maybe a year ago. I think this is pretty critical - any normal person would restart the computer every time, so if there's anything not-too- complex I can do to help, let me know. I have WiFi and a 3G card in my Lenovo X220T laptop and spend a lot of time in cafes using public WiFi, but when the WiFi is bad, I change to 3G. I haven't noticed a pattern about what causes the unresponsiveness. Please see Bug 1011073. The problem is fixed in -proposed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager-applet in Ubuntu. https://bugs.launchpad.net/bugs/780602 Title: nm-applet leaks memory Status in OEM Priority Project: Fix Released Status in OEM Priority Project precise series: Fix Released Status in OEM Priority Project quantal series: Fix Released Status in “network-manager-applet” package in Ubuntu: Fix Released Status in “network-manager-applet” source package in Precise: Fix Released Status in “network-manager-applet” source package in Quantal: Fix Released Bug description: The nm-applet embedded in the task bar becomes indeterminestically unresponsive. Clicking on the applet will still show the popup menu, but none of the menu entries respond to mouse clicks. When this happens, the VPN connections and Other networks menus also show up completely empty (only a small menu stub is displayed). It is uncertain what causes this behavior. It was originally thought that the cause was memory leaks in nm-applet: nm-applet leaks memory in a fresh install of Natty, increasing to over 200 Mb in 6-8 hours. However, fixes for the memory leaks failed to resolve the occurrence of the anomalous behavior described above. dbus-monitor shows errors such as the following when clicking a menu item or attempting to access a submenu: error sender=:1.14 - dest=:1.67 error_name=org.gtk.GDBus.UnmappedGError.Quark._LIBDBUSMENU_2dGLIB.Code0 reply_serial=107705 string The IDs supplied '[80846]' do not refer to any menu items we have The errors are returned by bus_event_group or bus_about_to_show_group in libdbusmenu-glib/server.c. -- Stable Release Update Application: [Impact] This issue affects most and any users of nm-applet, especially in environments (such as offices) where the detected wireless networks change a lot, and where roaming can occur frequently. [Test Case] Run nm-applet for multiple hours: - Observe that the VPN Connections submenu still opens and lists connections (if VPN connections are configured) - Observe that the More networks submenu for additional detected wireless networks still opens and lists networks. A common failure case is where such a submenu will open but show an empty list (a piece of menu a few milimeters long). [Regression Potential] Minimal, the fixes have been available for a while in the development release (and in other recent releases) with no regressions; furthermore, this corrects obviously wrong memory handling without changing the effective behavior of the application. Possible issues could be introducing new memory leaks with the changes however, and although the risk is minimal, this could cause the same failure behavior as listed above under [Test Case]. -- ProblemType: Bug DistroRelease: Ubuntu 11.04 Package: network-manager-gnome 0.8.4~git.20110318t152954.9c4c9a0-0ubuntu1 ProcVersionSignature: Ubuntu 2.6.38-9.43-generic-pae 2.6.38.4 Uname: Linux 2.6.38-9-generic-pae i686 NonfreeKernelModules: nvidia Architecture: i386 CRDA: Error: [Errno 2] No such file or directory Date: Tue May 10 11:53:09 2011 EcryptfsInUse: Yes IfupdownConfig: auto lo iface lo inet loopback InstallationMedia: Ubuntu 11.04 Natty Narwhal - Beta i386 (20110413) IpRoute: 192.168.2.0/24 dev eth0 proto kernel scope link src 192.168.2.12 metric 1 169.254.0.0/16 dev eth0 scope link metric 1000 default via 192.168.2.1 dev eth0 proto static Keyfiles: Error: [Errno 2] No such file or directory NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true ProcEnviron: LANGUAGE=en_CA:en PATH=(custom, user) LANG=en_CA.UTF-8 SHELL=/bin/bash SourcePackage: network-manager-applet UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/780602/+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 384105] Re: QQ account disabled because of protocol error in Pidgin and Empathy
** Changed in: pidgin (Ubuntu) Status: Incomplete = Opinion -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pidgin in Ubuntu. https://bugs.launchpad.net/bugs/384105 Title: QQ account disabled because of protocol error in Pidgin and Empathy Status in Chat app, and Telepathy user interface: Unknown Status in Pidgin: Confirmed Status in “pidgin” package in Ubuntu: Opinion Bug description: Binary package hint: pidgin, empathy, telepathy-haze, libpurple It has been over 16 months QQ chat protocol is unusable in linux. Pidgin (libpurple) and Empathy (telepathy-haze) with default settings prevent logging into QQ servers because of protocol incompatibility. Modifying the server version with QQ2008 enables the user to log in only for a very short time (a few hours). As the original reporter stated back in June 2009 and I presonally confirm today October 2010 (Ubuntu Maverick 10.10, default install) Trencent (the QQ provide) disables all user accounts permanently once they are found using an unofficial version of the client. -- The official version of the client linuxqq (available from the official website of QQ) is dated January 2009 and on current versions of Ubuntu crashes after the second sentence typed in and sent to the other party. eva package, another alternative for QQ, is dated back to 2006. Windows QQ does not correctly run under wine. Currently there is no valid alternative to anyone willing to chat using QQ protocol. To manage notifications about this bug go to: https://bugs.launchpad.net/empathy/+bug/384105/+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 1011073] Re: NetworkManager submenus sometimes unpopulated
** Tags added: verification-done-precise -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager-applet in Ubuntu. https://bugs.launchpad.net/bugs/1011073 Title: NetworkManager submenus sometimes unpopulated Status in DBus Menu: New Status in OEM Priority Project: In Progress Status in OEM Priority Project precise series: In Progress Status in OEM Priority Project quantal series: New Status in OEM Priority Project raring series: In Progress Status in “libdbusmenu” package in Ubuntu: Fix Released Status in “network-manager-applet” package in Ubuntu: Invalid Status in “libdbusmenu” source package in Precise: Fix Committed Status in “network-manager-applet” source package in Precise: Invalid Status in “libdbusmenu” source package in Quantal: Triaged Status in “network-manager-applet” source package in Quantal: Invalid Status in “libdbusmenu” source package in Raring: Fix Committed Status in “network-manager-applet” source package in Raring: Invalid Bug description: [Impact] * Affected applications with a high number of menu updates reach the maximum value allowed for the ID of a menuitem, and rejects further menu changes. Because the application underneath the menu has already removed the underlying actual GtkMenuItem objects, it is impossible to activate the items -- to effect the actions linked to the menuitems. * Some indicators have a relatively high and climbing memory usage due to the way they build menus to be displayed in the panel. [Test Case] * Run nm-applet for a while (multiple days without shutdown, without killing the application), notice whether the menus are still usable. * Run indicators for a while, observe memory usage. [Regression Potential] Indicators with a very high amount of updates may be affected as circling back past the maximum value, if a new menu item is created with an ID still in use by a menuitem that has not been removed yet, neither or only one of the two menu items might be available to be clicked -- this could confuse users or cause error messages to be displayed. Risk is low however since network-manager-gnome (nm-applet) is currently the application with the most menu updates. [Other Info] Submenus in Network Manager are sometimes unusable as they are not populated. This happens both with the list of available networks and with the VPN list. When the bug happens, it occurs for *both* the wireless submenu and the VPN menu. I know there are entries for those submenus as I can see them with other network UI mechanisms. The issue is intermittent. Expected: Dropping down the menu then hovering over the submenu trigger-point (example: More networks) shows the additional expected entries (example: more wifi networks to choose from). Actual: Dropping down the menu and hovering over the submenu trigger displays a submenu but the submenu has nothing in it and is unusable. Ubuntu 12.04 network-manager 0.9.4.0-0ubuntu4.1 Apple Macbook Pro 8,1 03:00.0 Network controller: Broadcom Corporation BCM4331 802.11a/b/g/n (rev 02) 02:00.0 Ethernet controller: Broadcom Corporation NetXtreme BCM57765 Gigabit Ethernet PCIe (rev 10) To manage notifications about this bug go to: https://bugs.launchpad.net/libdbusmenu/+bug/1011073/+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)
Hi Lothar, In order to get full functionality, you have got to download x11-proto- core (sounds like that's already done), and then follow steps 3 and 4 from comment 108. If haven't compiled Ubuntu packages from source before, this bug probably isn't the best place to start ;) -- 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 408903] Re: Does not handle microphone mute button (KEY_MICMUTE)
The only way I can think to verify this is to compile against it. I'll try it this afternoon. -- 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 1011073] Re: NetworkManager submenus sometimes unpopulated
I would use a combination of apt-get build-dep and bzr builddeb. You can find more information about bzr builddeb here. Basically just checkout the branch and build it, probably with -uc -us. http://doc.bazaar.canonical.com/plugins/en/builddeb-plugin.html http://jameswestby.net/bzr/builddeb/user_manual/ Rolling back is an issue, since I used the versioning scheme in order to get it merged. Should only be a simple dpkg -r once the real package lands in -updates though. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager-applet in Ubuntu. https://bugs.launchpad.net/bugs/1011073 Title: NetworkManager submenus sometimes unpopulated Status in DBus Menu: New Status in OEM Priority Project: In Progress Status in OEM Priority Project precise series: In Progress Status in OEM Priority Project quantal series: New Status in OEM Priority Project raring series: In Progress Status in “libdbusmenu” package in Ubuntu: Fix Released Status in “network-manager-applet” package in Ubuntu: Invalid Status in “libdbusmenu” source package in Precise: Triaged Status in “network-manager-applet” source package in Precise: Invalid Status in “libdbusmenu” source package in Quantal: Triaged Status in “network-manager-applet” source package in Quantal: Invalid Status in “libdbusmenu” source package in Raring: Triaged Status in “network-manager-applet” source package in Raring: Invalid Bug description: [Impact] * Affected applications with a high number of menu updates reach the maximum value allowed for the ID of a menuitem, and rejects further menu changes. Because the application underneath the menu has already removed the underlying actual GtkMenuItem objects, it is impossible to activate the items -- to effect the actions linked to the menuitems. * Some indicators have a relatively high and climbing memory usage due to the way they build menus to be displayed in the panel. [Test Case] * Run nm-applet for a while (multiple days without shutdown, without killing the application), notice whether the menus are still usable. * Run indicators for a while, observe memory usage. [Regression Potential] Indicators with a very high amount of updates may be affected as circling back past the maximum value, if a new menu item is created with an ID still in use by a menuitem that has not been removed yet, neither or only one of the two menu items might be available to be clicked -- this could confuse users or cause error messages to be displayed. Risk is low however since network-manager-gnome (nm-applet) is currently the application with the most menu updates. [Other Info] Submenus in Network Manager are sometimes unusable as they are not populated. This happens both with the list of available networks and with the VPN list. When the bug happens, it occurs for *both* the wireless submenu and the VPN menu. I know there are entries for those submenus as I can see them with other network UI mechanisms. The issue is intermittent. Expected: Dropping down the menu then hovering over the submenu trigger-point (example: More networks) shows the additional expected entries (example: more wifi networks to choose from). Actual: Dropping down the menu and hovering over the submenu trigger displays a submenu but the submenu has nothing in it and is unusable. Ubuntu 12.04 network-manager 0.9.4.0-0ubuntu4.1 Apple Macbook Pro 8,1 03:00.0 Network controller: Broadcom Corporation BCM4331 802.11a/b/g/n (rev 02) 02:00.0 Ethernet controller: Broadcom Corporation NetXtreme BCM57765 Gigabit Ethernet PCIe (rev 10) To manage notifications about this bug go to: https://bugs.launchpad.net/libdbusmenu/+bug/1011073/+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 1011073] Re: NetworkManager submenus sometimes unpopulated
That should work. Hope this works for you while we wait for the SRU to land. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager-applet in Ubuntu. https://bugs.launchpad.net/bugs/1011073 Title: NetworkManager submenus sometimes unpopulated Status in DBus Menu: New Status in OEM Priority Project: In Progress Status in OEM Priority Project precise series: In Progress Status in OEM Priority Project quantal series: New Status in OEM Priority Project raring series: In Progress Status in “libdbusmenu” package in Ubuntu: Fix Released Status in “network-manager-applet” package in Ubuntu: Invalid Status in “libdbusmenu” source package in Precise: Triaged Status in “network-manager-applet” source package in Precise: Invalid Status in “libdbusmenu” source package in Quantal: Triaged Status in “network-manager-applet” source package in Quantal: Invalid Status in “libdbusmenu” source package in Raring: Triaged Status in “network-manager-applet” source package in Raring: Invalid Bug description: [Impact] * Affected applications with a high number of menu updates reach the maximum value allowed for the ID of a menuitem, and rejects further menu changes. Because the application underneath the menu has already removed the underlying actual GtkMenuItem objects, it is impossible to activate the items -- to effect the actions linked to the menuitems. * Some indicators have a relatively high and climbing memory usage due to the way they build menus to be displayed in the panel. [Test Case] * Run nm-applet for a while (multiple days without shutdown, without killing the application), notice whether the menus are still usable. * Run indicators for a while, observe memory usage. [Regression Potential] Indicators with a very high amount of updates may be affected as circling back past the maximum value, if a new menu item is created with an ID still in use by a menuitem that has not been removed yet, neither or only one of the two menu items might be available to be clicked -- this could confuse users or cause error messages to be displayed. Risk is low however since network-manager-gnome (nm-applet) is currently the application with the most menu updates. [Other Info] Submenus in Network Manager are sometimes unusable as they are not populated. This happens both with the list of available networks and with the VPN list. When the bug happens, it occurs for *both* the wireless submenu and the VPN menu. I know there are entries for those submenus as I can see them with other network UI mechanisms. The issue is intermittent. Expected: Dropping down the menu then hovering over the submenu trigger-point (example: More networks) shows the additional expected entries (example: more wifi networks to choose from). Actual: Dropping down the menu and hovering over the submenu trigger displays a submenu but the submenu has nothing in it and is unusable. Ubuntu 12.04 network-manager 0.9.4.0-0ubuntu4.1 Apple Macbook Pro 8,1 03:00.0 Network controller: Broadcom Corporation BCM4331 802.11a/b/g/n (rev 02) 02:00.0 Ethernet controller: Broadcom Corporation NetXtreme BCM57765 Gigabit Ethernet PCIe (rev 10) To manage notifications about this bug go to: https://bugs.launchpad.net/libdbusmenu/+bug/1011073/+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 1011073] Re: NetworkManager submenus sometimes unpopulated
Bruno, Can you compile the code from my branch above? I've been running this patch for the past week and I haven't seen a reoccurence of the problem. ** Changed in: oem-priority/precise Status: New = In Progress ** Changed in: oem-priority/raring Status: Triaged = In Progress -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager-applet in Ubuntu. https://bugs.launchpad.net/bugs/1011073 Title: NetworkManager submenus sometimes unpopulated Status in DBus Menu: New Status in OEM Priority Project: In Progress Status in OEM Priority Project precise series: In Progress Status in OEM Priority Project quantal series: New Status in OEM Priority Project raring series: In Progress Status in “libdbusmenu” package in Ubuntu: Fix Released Status in “network-manager-applet” package in Ubuntu: Invalid Status in “libdbusmenu” source package in Precise: Triaged Status in “network-manager-applet” source package in Precise: Invalid Status in “libdbusmenu” source package in Quantal: Triaged Status in “network-manager-applet” source package in Quantal: Invalid Status in “libdbusmenu” source package in Raring: Triaged Status in “network-manager-applet” source package in Raring: Invalid Bug description: [Impact] * Affected applications with a high number of menu updates reach the maximum value allowed for the ID of a menuitem, and rejects further menu changes. Because the application underneath the menu has already removed the underlying actual GtkMenuItem objects, it is impossible to activate the items -- to effect the actions linked to the menuitems. * Some indicators have a relatively high and climbing memory usage due to the way they build menus to be displayed in the panel. [Test Case] * Run nm-applet for a while (multiple days without shutdown, without killing the application), notice whether the menus are still usable. * Run indicators for a while, observe memory usage. [Regression Potential] Indicators with a very high amount of updates may be affected as circling back past the maximum value, if a new menu item is created with an ID still in use by a menuitem that has not been removed yet, neither or only one of the two menu items might be available to be clicked -- this could confuse users or cause error messages to be displayed. Risk is low however since network-manager-gnome (nm-applet) is currently the application with the most menu updates. [Other Info] Submenus in Network Manager are sometimes unusable as they are not populated. This happens both with the list of available networks and with the VPN list. When the bug happens, it occurs for *both* the wireless submenu and the VPN menu. I know there are entries for those submenus as I can see them with other network UI mechanisms. The issue is intermittent. Expected: Dropping down the menu then hovering over the submenu trigger-point (example: More networks) shows the additional expected entries (example: more wifi networks to choose from). Actual: Dropping down the menu and hovering over the submenu trigger displays a submenu but the submenu has nothing in it and is unusable. Ubuntu 12.04 network-manager 0.9.4.0-0ubuntu4.1 Apple Macbook Pro 8,1 03:00.0 Network controller: Broadcom Corporation BCM4331 802.11a/b/g/n (rev 02) 02:00.0 Ethernet controller: Broadcom Corporation NetXtreme BCM57765 Gigabit Ethernet PCIe (rev 10) To manage notifications about this bug go to: https://bugs.launchpad.net/libdbusmenu/+bug/1011073/+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 1011073] Re: NetworkManager submenus sometimes unpopulated
** Changed in: oem-priority/raring Status: New = Triaged -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager-applet in Ubuntu. https://bugs.launchpad.net/bugs/1011073 Title: NetworkManager submenus sometimes unpopulated Status in DBus Menu: New Status in OEM Priority Project: Triaged Status in OEM Priority Project precise series: New Status in OEM Priority Project quantal series: New Status in OEM Priority Project raring series: Triaged Status in “libdbusmenu” package in Ubuntu: Fix Released Status in “network-manager-applet” package in Ubuntu: Invalid Status in “libdbusmenu” source package in Precise: Triaged Status in “network-manager-applet” source package in Precise: Invalid Status in “libdbusmenu” source package in Quantal: Triaged Status in “network-manager-applet” source package in Quantal: Invalid Status in “libdbusmenu” source package in Raring: Triaged Status in “network-manager-applet” source package in Raring: Invalid Bug description: [Impact] * Affected applications with a high number of menu updates reach the maximum value allowed for the ID of a menuitem, and rejects further menu changes. Because the application underneath the menu has already removed the underlying actual GtkMenuItem objects, it is impossible to activate the items -- to effect the actions linked to the menuitems. * Some indicators have a relatively high and climbing memory usage due to the way they build menus to be displayed in the panel. [Test Case] * Run nm-applet for a while (multiple days without shutdown, without killing the application), notice whether the menus are still usable. * Run indicators for a while, observe memory usage. [Regression Potential] Indicators with a very high amount of updates may be affected as circling back past the maximum value, if a new menu item is created with an ID still in use by a menuitem that has not been removed yet, neither or only one of the two menu items might be available to be clicked -- this could confuse users or cause error messages to be displayed. Risk is low however since network-manager-gnome (nm-applet) is currently the application with the most menu updates. [Other Info] Submenus in Network Manager are sometimes unusable as they are not populated. This happens both with the list of available networks and with the VPN list. When the bug happens, it occurs for *both* the wireless submenu and the VPN menu. I know there are entries for those submenus as I can see them with other network UI mechanisms. The issue is intermittent. Expected: Dropping down the menu then hovering over the submenu trigger-point (example: More networks) shows the additional expected entries (example: more wifi networks to choose from). Actual: Dropping down the menu and hovering over the submenu trigger displays a submenu but the submenu has nothing in it and is unusable. Ubuntu 12.04 network-manager 0.9.4.0-0ubuntu4.1 Apple Macbook Pro 8,1 03:00.0 Network controller: Broadcom Corporation BCM4331 802.11a/b/g/n (rev 02) 02:00.0 Ethernet controller: Broadcom Corporation NetXtreme BCM57765 Gigabit Ethernet PCIe (rev 10) To manage notifications about this bug go to: https://bugs.launchpad.net/libdbusmenu/+bug/1011073/+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 922968] Re: shouldn't queue a second suspend if the machine is already suspending
Okay, thank you for that information. -- 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/922968 Title: shouldn't queue a second suspend if the machine is already suspending Status in Gnome Powermanager: New Status in OEM Priority Project: Confirmed Status in OEM Priority Project precise series: Confirmed Status in “gnome-settings-daemon” package in Ubuntu: Confirmed Status in “linux” package in Ubuntu: Invalid Status in “gnome-settings-daemon” source package in Precise: Confirmed Status in “linux” source package in Precise: Invalid Bug description: Reproduce: This only triggers when you suspend with (Fn-F4) then quickly close the laptop lid. The power settings are setup such that the laptop lid close will suspend the laptop as well. So we're getting two suspend events in a row. Workaround: Either close the lid to suspend and not use Fn-F4. Or suspend using Fn-F4 then wait a few seconds before closing the lid. Version: Ubuntu 3.2.0-11.19-generic 3.2.1 After suspending the computer using Fn-F4, and for an extended period of time, I then wake the computer up by opening the lid and pressing the 'Fn' key. The computer starts to resume, and I am prompted for my password. Then the computer suspends again, and I have to wake it up again to resume the computer. This is with the computer charged sufficiently, but not plugged into an AC source. In addition I've also confirmed that using pm-suspend and resuming by pressing 'Fn' will still cause the machine to suspend again after resume. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: linux-image-3.2.0-11-generic 3.2.0-11.19 ProcVersionSignature: Ubuntu 3.2.0-11.19-generic 3.2.1 Uname: Linux 3.2.0-11-generic x86_64 AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24. ApportVersion: 1.91-0ubuntu1 Architecture: amd64 ArecordDevices: List of CAPTURE Hardware Devices card 0: PCH [HDA Intel PCH], device 0: CONEXANT Analog [CONEXANT Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: arges 2127 F pulseaudio CRDA: Error: [Errno 2] No such file or directory Card0.Amixer.info: Card hw:0 'PCH'/'HDA Intel PCH at 0xf262 irq 46' Mixer name : 'Intel CougarPoint HDMI' Components : 'HDA:14f1506e,17aa21ce,0012 HDA:80862805,80860101,0010' Controls : 26 Simple ctrls : 8 Card29.Amixer.info: Card hw:29 'ThinkPadEC'/'ThinkPad Console Audio Control at EC reg 0x30, fw unknown' Mixer name : 'ThinkPad EC (unknown)' Components : '' Controls : 1 Simple ctrls : 1 Card29.Amixer.values: Simple mixer control 'Console',0 Capabilities: pswitch pswitch-joined penum Playback channels: Mono Mono: Playback [on] Date: Fri Jan 27 23:00:48 2012 EcryptfsInUse: Yes InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Alpha amd64 (2029.1) MachineType: LENOVO 4177CTO ProcEnviron: PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-11-generic root=UUID=0f84abde-0eb0-405f-a8c6-b09dd4c4dae9 ro quiet splash i915.i915_enable_rc6=1 vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.2.0-11-generic N/A linux-backports-modules-3.2.0-11-generic N/A linux-firmware1.68 SourcePackage: linux StagingDrivers: mei UpgradeStatus: Upgraded to precise on 2011-12-21 (37 days ago) dmi.bios.date: 07/29/2011 dmi.bios.vendor: LENOVO dmi.bios.version: 83ET63WW (1.33 ) dmi.board.asset.tag: Not Available dmi.board.name: 4177CTO dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr83ET63WW(1.33):bd07/29/2011:svnLENOVO:pn4177CTO:pvrThinkPadT420:rvnLENOVO:rn4177CTO:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 4177CTO dmi.product.version: ThinkPad T420 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-power/+bug/922968/+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 922968] Re: shouldn't queue a second suspend if the machine is already suspending
Hi Ryan, Can the same fix be applied to the equivalent packages in precise? If so, I will be requesting that we SRU these changes once upstream agrees to them. -- 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/922968 Title: shouldn't queue a second suspend if the machine is already suspending Status in Gnome Powermanager: New Status in OEM Priority Project: Confirmed Status in OEM Priority Project precise series: Confirmed Status in “gnome-settings-daemon” package in Ubuntu: Confirmed Status in “linux” package in Ubuntu: Invalid Status in “gnome-settings-daemon” source package in Precise: Confirmed Status in “linux” source package in Precise: Invalid Bug description: Reproduce: This only triggers when you suspend with (Fn-F4) then quickly close the laptop lid. The power settings are setup such that the laptop lid close will suspend the laptop as well. So we're getting two suspend events in a row. Workaround: Either close the lid to suspend and not use Fn-F4. Or suspend using Fn-F4 then wait a few seconds before closing the lid. Version: Ubuntu 3.2.0-11.19-generic 3.2.1 After suspending the computer using Fn-F4, and for an extended period of time, I then wake the computer up by opening the lid and pressing the 'Fn' key. The computer starts to resume, and I am prompted for my password. Then the computer suspends again, and I have to wake it up again to resume the computer. This is with the computer charged sufficiently, but not plugged into an AC source. In addition I've also confirmed that using pm-suspend and resuming by pressing 'Fn' will still cause the machine to suspend again after resume. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: linux-image-3.2.0-11-generic 3.2.0-11.19 ProcVersionSignature: Ubuntu 3.2.0-11.19-generic 3.2.1 Uname: Linux 3.2.0-11-generic x86_64 AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24. ApportVersion: 1.91-0ubuntu1 Architecture: amd64 ArecordDevices: List of CAPTURE Hardware Devices card 0: PCH [HDA Intel PCH], device 0: CONEXANT Analog [CONEXANT Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: arges 2127 F pulseaudio CRDA: Error: [Errno 2] No such file or directory Card0.Amixer.info: Card hw:0 'PCH'/'HDA Intel PCH at 0xf262 irq 46' Mixer name : 'Intel CougarPoint HDMI' Components : 'HDA:14f1506e,17aa21ce,0012 HDA:80862805,80860101,0010' Controls : 26 Simple ctrls : 8 Card29.Amixer.info: Card hw:29 'ThinkPadEC'/'ThinkPad Console Audio Control at EC reg 0x30, fw unknown' Mixer name : 'ThinkPad EC (unknown)' Components : '' Controls : 1 Simple ctrls : 1 Card29.Amixer.values: Simple mixer control 'Console',0 Capabilities: pswitch pswitch-joined penum Playback channels: Mono Mono: Playback [on] Date: Fri Jan 27 23:00:48 2012 EcryptfsInUse: Yes InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Alpha amd64 (2029.1) MachineType: LENOVO 4177CTO ProcEnviron: PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-11-generic root=UUID=0f84abde-0eb0-405f-a8c6-b09dd4c4dae9 ro quiet splash i915.i915_enable_rc6=1 vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.2.0-11-generic N/A linux-backports-modules-3.2.0-11-generic N/A linux-firmware1.68 SourcePackage: linux StagingDrivers: mei UpgradeStatus: Upgraded to precise on 2011-12-21 (37 days ago) dmi.bios.date: 07/29/2011 dmi.bios.vendor: LENOVO dmi.bios.version: 83ET63WW (1.33 ) dmi.board.asset.tag: Not Available dmi.board.name: 4177CTO dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr83ET63WW(1.33):bd07/29/2011:svnLENOVO:pn4177CTO:pvrThinkPadT420:rvnLENOVO:rn4177CTO:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 4177CTO dmi.product.version: ThinkPad T420 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-power/+bug/922968/+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)
Okay, Thanks for your help Sebastien. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-input-evdev 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 “xserver-xorg-input-evdev” package in Ubuntu: Triaged Status in “gnome-settings-daemon” source package in Raring: Triaged Status in “udev” source package in Raring: Triaged 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 1011073] Re: NetworkManager submenus sometimes unpopulated
** Also affects: libdbusmenu Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager-applet in Ubuntu. https://bugs.launchpad.net/bugs/1011073 Title: NetworkManager submenus sometimes unpopulated Status in DBus Menu: New Status in OEM Priority Project: New Status in OEM Priority Project precise series: New Status in OEM Priority Project quantal series: New Status in OEM Priority Project raring series: New Status in “libdbusmenu” package in Ubuntu: Fix Released Status in “network-manager-applet” package in Ubuntu: Invalid Status in “libdbusmenu” source package in Precise: Triaged Status in “network-manager-applet” source package in Precise: Invalid Status in “libdbusmenu” source package in Quantal: Triaged Status in “network-manager-applet” source package in Quantal: Invalid Status in “libdbusmenu” source package in Raring: Triaged Status in “network-manager-applet” source package in Raring: Invalid Bug description: [Impact] * Affected applications with a high number of menu updates reach the maximum value allowed for the ID of a menuitem, and rejects further menu changes. Because the application underneath the menu has already removed the underlying actual GtkMenuItem objects, it is impossible to activate the items -- to effect the actions linked to the menuitems. * Some indicators have a relatively high and climbing memory usage due to the way they build menus to be displayed in the panel. [Test Case] * Run nm-applet for a while (multiple days without shutdown, without killing the application), notice whether the menus are still usable. * Run indicators for a while, observe memory usage. [Regression Potential] Indicators with a very high amount of updates may be affected as circling back past the maximum value, if a new menu item is created with an ID still in use by a menuitem that has not been removed yet, neither or only one of the two menu items might be available to be clicked -- this could confuse users or cause error messages to be displayed. Risk is low however since network-manager-gnome (nm-applet) is currently the application with the most menu updates. [Other Info] Submenus in Network Manager are sometimes unusable as they are not populated. This happens both with the list of available networks and with the VPN list. When the bug happens, it occurs for *both* the wireless submenu and the VPN menu. I know there are entries for those submenus as I can see them with other network UI mechanisms. The issue is intermittent. Expected: Dropping down the menu then hovering over the submenu trigger-point (example: More networks) shows the additional expected entries (example: more wifi networks to choose from). Actual: Dropping down the menu and hovering over the submenu trigger displays a submenu but the submenu has nothing in it and is unusable. Ubuntu 12.04 network-manager 0.9.4.0-0ubuntu4.1 Apple Macbook Pro 8,1 03:00.0 Network controller: Broadcom Corporation BCM4331 802.11a/b/g/n (rev 02) 02:00.0 Ethernet controller: Broadcom Corporation NetXtreme BCM57765 Gigabit Ethernet PCIe (rev 10) To manage notifications about this bug go to: https://bugs.launchpad.net/libdbusmenu/+bug/1011073/+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 1011073] Re: NetworkManager submenus sometimes unpopulated
I'm not sure I did this right, I've created a new branch based off the ubuntu project, but I see Mathieu further up did a merge directly against the dbus menu project. Anyway, let me know if this works or if I need to do something else. I'm subscribing -sponsors too. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager-applet in Ubuntu. https://bugs.launchpad.net/bugs/1011073 Title: NetworkManager submenus sometimes unpopulated Status in DBus Menu: New Status in OEM Priority Project: New Status in OEM Priority Project precise series: New Status in OEM Priority Project quantal series: New Status in OEM Priority Project raring series: New Status in “libdbusmenu” package in Ubuntu: Fix Released Status in “network-manager-applet” package in Ubuntu: Invalid Status in “libdbusmenu” source package in Precise: Triaged Status in “network-manager-applet” source package in Precise: Invalid Status in “libdbusmenu” source package in Quantal: Triaged Status in “network-manager-applet” source package in Quantal: Invalid Status in “libdbusmenu” source package in Raring: Triaged Status in “network-manager-applet” source package in Raring: Invalid Bug description: [Impact] * Affected applications with a high number of menu updates reach the maximum value allowed for the ID of a menuitem, and rejects further menu changes. Because the application underneath the menu has already removed the underlying actual GtkMenuItem objects, it is impossible to activate the items -- to effect the actions linked to the menuitems. * Some indicators have a relatively high and climbing memory usage due to the way they build menus to be displayed in the panel. [Test Case] * Run nm-applet for a while (multiple days without shutdown, without killing the application), notice whether the menus are still usable. * Run indicators for a while, observe memory usage. [Regression Potential] Indicators with a very high amount of updates may be affected as circling back past the maximum value, if a new menu item is created with an ID still in use by a menuitem that has not been removed yet, neither or only one of the two menu items might be available to be clicked -- this could confuse users or cause error messages to be displayed. Risk is low however since network-manager-gnome (nm-applet) is currently the application with the most menu updates. [Other Info] Submenus in Network Manager are sometimes unusable as they are not populated. This happens both with the list of available networks and with the VPN list. When the bug happens, it occurs for *both* the wireless submenu and the VPN menu. I know there are entries for those submenus as I can see them with other network UI mechanisms. The issue is intermittent. Expected: Dropping down the menu then hovering over the submenu trigger-point (example: More networks) shows the additional expected entries (example: more wifi networks to choose from). Actual: Dropping down the menu and hovering over the submenu trigger displays a submenu but the submenu has nothing in it and is unusable. Ubuntu 12.04 network-manager 0.9.4.0-0ubuntu4.1 Apple Macbook Pro 8,1 03:00.0 Network controller: Broadcom Corporation BCM4331 802.11a/b/g/n (rev 02) 02:00.0 Ethernet controller: Broadcom Corporation NetXtreme BCM57765 Gigabit Ethernet PCIe (rev 10) To manage notifications about this bug go to: https://bugs.launchpad.net/libdbusmenu/+bug/1011073/+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)
** Description changed: - Ubuntu 9.04 + [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 + request MappingKeyboard, first_keycode 8, count 248 MappingNotify event, serial 34, synthetic NO, window 0x0, - request MappingKeyboard, first_keycode 8, count 247 + 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 + 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 + 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 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-input-evdev 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 “xserver-xorg-input-evdev” package in Ubuntu: Triaged Status in “gnome-settings-daemon” source package in Raring: Triaged Status in “udev” source package in Raring: Triaged 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:
[Desktop-packages] [Bug 408903] Re: Does not handle microphone mute button (KEY_MICMUTE)
Ideally, we get this SRUed to Precise. I've filled out the SRU template. It's just a bit tricky because functionality cross cuts a lot of packages. I've added branches for all of the packages that require code changes. It works something like this: 1) x11-proto gets updated with a new #define 2) install x11proto-core-dev on the build server 3) rebuild libx11 4) update the remaining linked packages: udev, gnome-settings-daemon, xkeyboard-config I've subbed sponsors for some guidance and to get x11-proto updated. Alternately if this is out of scope we can close this bug for precise. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-input-evdev 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 “xserver-xorg-input-evdev” package in Ubuntu: Triaged Status in “gnome-settings-daemon” source package in Raring: Triaged Status in “udev” source package in Raring: Triaged 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 982889] Re: X trying to start before plymouth has finished using the drm driver
** Changed in: oem-priority/precise Status: In Progress = Fix Released ** Changed in: oem-priority Status: In Progress = Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/982889 Title: X trying to start before plymouth has finished using the drm driver Status in OEM Priority Project: Fix Released Status in OEM Priority Project precise series: Fix Released Status in “gdm” package in Ubuntu: Fix Released Status in “kde-workspace” package in Ubuntu: New Status in “lightdm” package in Ubuntu: Fix Released Status in “plymouth” package in Ubuntu: Fix Released Status in “gdm” source package in Precise: New Status in “kde-workspace” source package in Precise: New Status in “lightdm” source package in Precise: Fix Released Status in “plymouth” source package in Precise: Fix Released Status in “gdm” source package in Raring: New Status in “kde-workspace” source package in Raring: New Status in “lightdm” source package in Raring: Fix Released Status in “plymouth” source package in Raring: Fix Released Status in “gdm” source package in Saucy: Fix Released Status in “kde-workspace” source package in Saucy: New Status in “lightdm” source package in Saucy: Fix Released Status in “plymouth” source package in Saucy: Fix Released Bug description: X server fails to start the first time after boot, it works fine when I start it again. Looks like a race condition with intel drm initialization, i guess X tries to start faster than drm driver is initialized so it fails. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: xorg 1:7.6+12ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-23.36-generic 3.2.14 Uname: Linux 3.2.0-23-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.0.1-0ubuntu3 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] CompositorRunning: compiz Date: Mon Apr 16 10:35:28 2012 DistUpgraded: Fresh install DistroCodename: precise DistroVariant: ubuntu ExtraDebuggingInterest: Yes, whatever it takes to get this fixed in Ubuntu GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0102] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. Device [1462:7750] Advanced Micro Devices [AMD] nee ATI Barts XT [ATI Radeon HD 6800 Series] [1002:6738] (prog-if 00 [VGA controller]) Subsystem: Giga-byte Technology Device [1458:21fa] InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Beta amd64 (20120301) MachineType: MSI MS-7750 ProcEnviron: LANGUAGE=en_US:en TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.2.0-23-generic root=/dev/mapper/ssd-ubuntu--precise ro quiet splash SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/25/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: V4.0 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Z68A-G43 (G3) (MS-7750) dmi.board.vendor: MSI dmi.board.version: 1.0 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrV4.0:bd08/25/2011:svnMSI:pnMS-7750:pvr1.0:rvnMSI:rnZ68A-G43(G3)(MS-7750):rvr1.0:cvnMSI:ct3:cvr1.0: dmi.product.name: MS-7750 dmi.product.version: 1.0 dmi.sys.vendor: MSI version.compiz: compiz 1:0.9.7.6-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.32-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 8.0.2-0ubuntu3 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 8.0.2-0ubuntu3 version.xserver-xorg-core: xserver-xorg-core 2:1.11.4-0ubuntu10 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.0-0ubuntu1 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/oem-priority/+bug/982889/+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)
** Changed in: oem-priority/raring Status: Triaged = Won't Fix -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-input-evdev 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 “xserver-xorg-input-evdev” package in Ubuntu: Triaged Status in “gnome-settings-daemon” source package in Raring: Triaged Status in “udev” source package in Raring: Triaged Status in “xserver-xorg-input-evdev” source package in Raring: Triaged Bug description: Ubuntu 9.04 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)
This bug is blocking on resolution of bug 937822. I don't know if I need to revert on top of the -proposed branch or if it's better to just go off the -updates branch of xkeyboard-config. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-input-evdev 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 “xserver-xorg-input-evdev” package in Ubuntu: Triaged Status in “gnome-settings-daemon” source package in Raring: Triaged Status in “udev” source package in Raring: Triaged Status in “xserver-xorg-input-evdev” source package in Raring: Triaged Bug description: Ubuntu 9.04 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 950160] Re: Unity blocks other programs from binding globally to Super+* (* = any key)
** Changed in: oem-priority Importance: Critical = High ** Changed in: oem-priority/precise Importance: Critical = High -- 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/950160 Title: Unity blocks other programs from binding globally to Super+* (* = any key) Status in Compiz: Fix Released Status in Compiz 0.9.8 series: In Progress Status in Compiz Core: Confirmed Status in Gnome Settings Daemon: Fix Released Status in OEM Priority Project: In Progress Status in OEM Priority Project precise series: In Progress Status in Unity: Fix Released Status in Unity 5.0 series: Triaged Status in Unity 6.0 series: In Progress Status in “compiz” package in Ubuntu: Fix Released Status in “gnome-settings-daemon” package in Ubuntu: Fix Released Status in “unity” package in Ubuntu: In Progress Status in “compiz” source package in Precise: Triaged Status in “gnome-settings-daemon” source package in Precise: Fix Released Status in “unity” source package in Precise: Triaged Status in “compiz” source package in Quantal: Triaged Status in “gnome-settings-daemon” source package in Quantal: Fix Released Status in “unity” source package in Quantal: In Progress Bug description: WORKAROUND 1: Run CCSM and under Ubuntu Unity Plugin change the key binding for Key to show the launcher to something else (e.g. Super+U). Then log out and in again. As long as no compiz plugin is bound to the single Super key any more, compiz will no longer block other apps from binding to Super+other_keys. WORKAROUND 2: 1. Write a script or figure out the command to do the action you want. 2. Run ccsm. 3. Enable the Commands plugin 4. In the Commands settings, fill in the command line you want and bind it to key Super+P. Now Unity will run your specified command on Super+P, but still handle the Super key as usual. [Precise SRU Justification] [Impact] Any shortcut with Super, Hyper, Meta virtual modifiers does not work [Test Case] Attach an external monitor to the laptop, press Super+P, it should do the video switch as this function is implemented in gnome-settings-daemon. A patch in comment #12 is now accepted upstream and a test package with that patch is available in comment #14. From the test result, the patch at least fixes Unity-2D. [Regression Potential] The patch is accepted upstream and is also cherry-picked in the gnome-3-4 branch of g-s-d git tree. g-s-d version in Precise is 3.4.2. So the risk of regression should be rather low. [Other] I prepare a debdiff in comment #31 for convenience. I hope the patch can be in both Quantal and Precise. ORIGINAL DESCRIPTION: Using : 12.04 Beta 1, updated. and Unity. In 11.10 clicking: - the function key (Fn) + (F1) allowed to switch between the laptop screen and the external monitor. After upgrading to 12.04 this no more works and instead I get an unexpected behavior: see the video. https://www.youtube.com/watch?v=-vEnrV5TwXo System: Dell XPS 15 L502X ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: ubuntu-sso-client 2.99.90-0ubuntu2 ProcVersionSignature: Ubuntu 3.2.0-18.28-generic 3.2.9 Uname: Linux 3.2.0-18-generic x86_64 ApportVersion: 1.94.1-0ubuntu1 Architecture: amd64 Date: Thu Mar 8 19:18:42 2012 InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Release amd64 (20111012) PackageArchitecture: all SourcePackage: ubuntu-sso-client UpgradeStatus: Upgraded to precise on 2012-03-02 (6 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/compiz/+bug/950160/+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 881526] Re: System freezes, kernel crashes, [fglrx] ASIC hang happened
** Changed in: hwe-next Status: New = Fix Committed ** Changed in: fglrx-installer (Ubuntu) Assignee: (unassigned) = James M. Leddy (jm-leddy) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to fglrx-installer in Ubuntu. https://bugs.launchpad.net/bugs/881526 Title: System freezes, kernel crashes, [fglrx] ASIC hang happened Status in amd: Fix Released Status in AMD fglrx video driver: Won't Fix Status in HWE Next Project: Fix Committed Status in OEM Priority Project: Invalid Status in “fglrx-installer” package in Ubuntu: Confirmed Bug description: The system freezes intermittently and the kernel crashes a few seconds later. This has only happened since upgrading to 11.10. Found the following error in /var/log/kern.log which coincides: Oct 25 14:53:46 lt9630 kernel: [ 737.900416] INFO: rcu_sched_state detected stall on CPU 2 (t=15000 jiffies) Oct 25 14:55:46 lt9630 kernel: [ 857.813946] [fglrx] ASIC hang happened Oct 25 14:55:46 lt9630 kernel: [ 857.813950] Pid: 1149, comm: Xorg Tainted: P C 3.0.0-12-generic #20-Ubuntu Oct 25 14:55:46 lt9630 kernel: [ 857.813951] Call Trace: Oct 25 14:55:46 lt9630 kernel: [ 857.813985] [a00a0d7e] KCL_DEBUG_OsDump+0xe/0x10 [fglrx] Oct 25 14:55:46 lt9630 kernel: [ 857.814003] [a00ae20c] firegl_hardwareHangRecovery+0x1c/0x50 [fglrx] Oct 25 14:55:46 lt9630 kernel: [ 857.814036] [a013ad59] ? _ZN4Asic9WaitUntil15ResetASICIfHungEv+0x9/0x10 [fglrx] Oct 25 14:55:46 lt9630 kernel: [ 857.814068] [a013ad0c] ? _ZN4Asic9WaitUntil15WaitForCompleteEv+0x6c/0xb0 [fglrx] Oct 25 14:55:46 lt9630 kernel: [ 857.814099] [a0135fb4] ? _ZN15ExecutableUnits10CPRingIdleE15idle_WaitMethod12_QS_CP_RING_+0xe4$ Oct 25 14:55:46 lt9630 kernel: [ 857.814127] [a0115acb] ? _ZN10CMMSurfaceD1Ev+0xcb/0xe0 [fglrx] Oct 25 14:55:46 lt9630 kernel: [ 857.814158] [a0135e7b] ? _ZN15ExecutableUnits7PM4idleE15idle_WaitMethod+0x4b/0x90 [fglrx] Oct 25 14:55:46 lt9630 kernel: [ 857.814187] [a012e8f1] ? _ZN15QS_PRIVATE_CORE9QsPM4idleE15idle_WaitMethod+0x31/0x60 [fglrx] Oct 25 14:55:46 lt9630 kernel: [ 857.814215] [a0119d8a] ? _ZN10QS_PRIVATE11synchronizeEv+0x2a/0x30 [fglrx] Oct 25 14:55:46 lt9630 kernel: [ 857.814243] [a01233f5] ? _Z8uCWDDEQCmjjPvjS_+0x3b5/0x10c0 [fglrx] Oct 25 14:55:46 lt9630 kernel: [ 857.814246] [810871ee] ? down+0x2e/0x50 Oct 25 14:55:46 lt9630 kernel: [ 857.814266] [a00cc932] ? firegl_cmmqs_CWDDE_32+0x332/0x440 [fglrx] Oct 25 14:55:46 lt9630 kernel: [ 857.814285] [a00cb260] ? firegl_cmmqs_CWDDE32+0x70/0x100 [fglrx] Oct 25 14:55:46 lt9630 kernel: [ 857.814288] [81282e5a] ? security_capable+0x2a/0x30 Oct 25 14:55:46 lt9630 kernel: [ 857.814306] [a00cb1f0] ? firegl_cmmqs_createdriver+0x170/0x170 [fglrx] Oct 25 14:55:46 lt9630 kernel: [ 857.814322] [a00a9e18] ? firegl_ioctl+0x1e8/0x250 [fglrx] Oct 25 14:55:46 lt9630 kernel: [ 857.814333] [a009a9be] ? ip_firegl_unlocked_ioctl+0xe/0x20 [fglrx] Oct 25 14:55:46 lt9630 kernel: [ 857.814335] [8117939a] ? do_vfs_ioctl+0x8a/0x340 Oct 25 14:55:46 lt9630 kernel: [ 857.814338] [811679ed] ? vfs_read+0x10d/0x180 Oct 25 14:55:46 lt9630 kernel: [ 857.814339] [811796e1] ? sys_ioctl+0x91/0xa0 Oct 25 14:55:46 lt9630 kernel: [ 857.814342] [815f22c2] ? system_call_fastpath+0x16/0x1b Oct 25 14:55:46 lt9630 kernel: [ 857.814345] pubdev:0xa02fd600, num of device:1 , name:fglrx, major 8, minor 88. Oct 25 14:55:46 lt9630 kernel: [ 857.814346] device 0 : 0x88019b85 . Oct 25 14:55:46 lt9630 kernel: [ 857.814345] pubdev:0xa02fd600, num of device:1 , name:fglrx, major 8, minor 88. Oct 25 14:55:46 lt9630 kernel: [ 857.814346] device 0 : 0x88019b85 . Oct 25 14:55:46 lt9630 kernel: [ 857.814348] Asic ID:0x6779, revision:0x3c, MMIOReg:0xc90012b8. Oct 25 14:55:46 lt9630 kernel: [ 857.814349] FB phys addr: 0xc000, MC :0xf, Total FB size :0x4000. Oct 25 14:55:46 lt9630 kernel: [ 857.814351] gart table MC:0xf0f8fd000, Physical:0xcf8fd000, size:0x402000. Oct 25 14:55:46 lt9630 kernel: [ 857.814353] mc_node :FB, total 1 zones Oct 25 14:55:46 lt9630 kernel: [ 857.814354] MC start:0xf, Physical:0xc000, size:0xfd0. Oct 25 14:55:46 lt9630 kernel: [ 857.814356] Mapped heap -- Offset:0x0, size:0xf8fd000, reference count:33, mapping count:0, Oct 25 14:55:46 lt9630 kernel: [ 857.814357] Mapped heap -- Offset:0x0, size:0x100, reference count:1, mapping count:0, Oct 25 14:55:46 lt9630 kernel: [ 857.814359] Mapped heap -- Offset:0xf8fd000, size:0x403000, reference count:1, mapping count:0, Oct 25 14:55:46 lt9630 kernel: [ 857.814360] mc_node :INV_FB, total 1 zones Oct 25 14:55:46
[Desktop-packages] [Bug 1015183] Re: Inconsistent mouse events for Acer T231H multitouch monitor
** Changed in: hwe-next Status: New = In Progress ** Changed in: hwe-next Assignee: (unassigned) = James M. Leddy (jm-leddy) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1015183 Title: Inconsistent mouse events for Acer T231H multitouch monitor Status in HWE Next Project: In Progress Status in X.Org X server: In Progress Status in “xorg-server” package in Ubuntu: In Progress Bug description: I already submitted this at http://askubuntu.com/questions/153043/ but decided to update to the latest development snapshot in order to give that a try and write a proper bug report if the issue persists. It does persist. My setup is a quantal alpha 1, just upgraded from precise, with an Acer T231H multitouch monitor connected to it, as well as an ordinary mouse for testing. The mouse events as X sends them to the applications are inconsitent. This can be debugged using xev. The first touch of the screen is preceeded by a MotionNotify event which already has state 0x100, i.e. left mouse button pressed. After that comes a ButtonPress event, again with state 0x100 although that value should indicate the state of the buttons before the event occurred. The subsequent drag is all right, and the ButtonRelease as well, but the 0x100 bit in the state value will never become zero again. Even if I've got an ordinary mouse connected as well, it will henceforth report every movement as if I were keeping the left mouse button down. The only cure that I could find was restarting the X server. Together with the ButtonPress and ButtonRelease events, this constant bit for left mouse button amounts to an inconsistent reporting of button state. Java applications e.g. will report every move as a drag due to this issue, with severe implications for focus management. This makes using differenent parts of the application almost impossible, as mouse movement will only be reported to the component where the mouse entered the application window. Since reporting at askubuntu, I've run some tests with evtest. The data coming from the event device looks sane enough: BTN_TOUCH events for the first finger, with value 1 for pressed and 0 for released. ABS_MT_TRACKING_ID for all fingers, with a non-negative value for pressed and -1 for released. The grouping into syn groups looks sane as well. So I'd say the kernel driver works as intended, and somewhere from there to the xevent layer, some internal state gets messed up. I'm willing to try out any patches you might propose, be it in an attempt to fix this, or only to gather more information. Expected behaviour: MotionNotify with state 0x000 when dragging the ordinary mouse MotionNotify with state 0x000 for move prior to touch, or no event at all ButtonPress with state 0x000 when touching the screen MotionNotify with state 0x100 while dragging the finger ButtonRelease with state 0x100 when lifting the finger MotionNotify with state 0x000 when dragging the ordinary mouse afterwards Actual behaviour: MotionNotify with state 0x000 when dragging the ordinary mouse before the first touch MotionNotify with state 0x100 for prior to ButtonPress event ButtonPress with state 0x100 when touching the screen MotionNotify with state 0x100 while dragging the finger ButtonRelease with state 0x100 when lifting the finger MotionNotify with state 0x100 when dragging the ordinary mouse afterwards ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: xserver-xorg-input-evdev 1:2.7.0-0ubuntu2 ProcVersionSignature: Ubuntu 3.4.0-5.11-generic 3.4.0 Uname: Linux 3.4.0-5-generic x86_64 ApportVersion: 2.2.3-0ubuntu5 Architecture: amd64 CurrentDmesg: [7.381404] ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready Date: Tue Jun 19 17:56:46 2012 DistUpgraded: 2012-06-19 17:51:23,756 DEBUG enabling apt cron job DistroCodename: quantal DistroVariant: ubuntu InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Release amd64 (20120425) ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.4.0-5-generic root=UUID=88133c52-550c-4c43-9da5-15f180bdb767 ro quiet splash vt.handoff=7 SourcePackage: xserver-xorg-input-evdev UpgradeStatus: Upgraded to quantal on 2012-06-19 (0 days ago) dmi.bios.date: 09/22/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4.6.4 dmi.board.name: AMD HUDSON-M1 dmi.board.vendor: ZOTAC dmi.chassis.type: 3 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4.6.4:bd09/22/2011:svn:pn:pvr:rvnZOTAC:rnAMDHUDSON-M1:rvr:cvn:ct3:cvr: version.compiz: compiz 1:0.9.7.8-0ubuntu3 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.33-1 version.libgl1-mesa-dri: libgl1
[Desktop-packages] [Bug 881526] Re: System freezes, kernel crashes, [fglrx] ASIC hang happened
** Changed in: amd Status: Fix Released = In Progress -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to fglrx-installer in Ubuntu. https://bugs.launchpad.net/bugs/881526 Title: System freezes, kernel crashes, [fglrx] ASIC hang happened Status in amd: In Progress Status in AMD fglrx video driver: Won't Fix Status in HWE Next Project: Fix Committed Status in OEM Priority Project: Invalid Status in “fglrx-installer” package in Ubuntu: Confirmed Bug description: The system freezes intermittently and the kernel crashes a few seconds later. This has only happened since upgrading to 11.10. Found the following error in /var/log/kern.log which coincides: Oct 25 14:53:46 lt9630 kernel: [ 737.900416] INFO: rcu_sched_state detected stall on CPU 2 (t=15000 jiffies) Oct 25 14:55:46 lt9630 kernel: [ 857.813946] [fglrx] ASIC hang happened Oct 25 14:55:46 lt9630 kernel: [ 857.813950] Pid: 1149, comm: Xorg Tainted: P C 3.0.0-12-generic #20-Ubuntu Oct 25 14:55:46 lt9630 kernel: [ 857.813951] Call Trace: Oct 25 14:55:46 lt9630 kernel: [ 857.813985] [a00a0d7e] KCL_DEBUG_OsDump+0xe/0x10 [fglrx] Oct 25 14:55:46 lt9630 kernel: [ 857.814003] [a00ae20c] firegl_hardwareHangRecovery+0x1c/0x50 [fglrx] Oct 25 14:55:46 lt9630 kernel: [ 857.814036] [a013ad59] ? _ZN4Asic9WaitUntil15ResetASICIfHungEv+0x9/0x10 [fglrx] Oct 25 14:55:46 lt9630 kernel: [ 857.814068] [a013ad0c] ? _ZN4Asic9WaitUntil15WaitForCompleteEv+0x6c/0xb0 [fglrx] Oct 25 14:55:46 lt9630 kernel: [ 857.814099] [a0135fb4] ? _ZN15ExecutableUnits10CPRingIdleE15idle_WaitMethod12_QS_CP_RING_+0xe4$ Oct 25 14:55:46 lt9630 kernel: [ 857.814127] [a0115acb] ? _ZN10CMMSurfaceD1Ev+0xcb/0xe0 [fglrx] Oct 25 14:55:46 lt9630 kernel: [ 857.814158] [a0135e7b] ? _ZN15ExecutableUnits7PM4idleE15idle_WaitMethod+0x4b/0x90 [fglrx] Oct 25 14:55:46 lt9630 kernel: [ 857.814187] [a012e8f1] ? _ZN15QS_PRIVATE_CORE9QsPM4idleE15idle_WaitMethod+0x31/0x60 [fglrx] Oct 25 14:55:46 lt9630 kernel: [ 857.814215] [a0119d8a] ? _ZN10QS_PRIVATE11synchronizeEv+0x2a/0x30 [fglrx] Oct 25 14:55:46 lt9630 kernel: [ 857.814243] [a01233f5] ? _Z8uCWDDEQCmjjPvjS_+0x3b5/0x10c0 [fglrx] Oct 25 14:55:46 lt9630 kernel: [ 857.814246] [810871ee] ? down+0x2e/0x50 Oct 25 14:55:46 lt9630 kernel: [ 857.814266] [a00cc932] ? firegl_cmmqs_CWDDE_32+0x332/0x440 [fglrx] Oct 25 14:55:46 lt9630 kernel: [ 857.814285] [a00cb260] ? firegl_cmmqs_CWDDE32+0x70/0x100 [fglrx] Oct 25 14:55:46 lt9630 kernel: [ 857.814288] [81282e5a] ? security_capable+0x2a/0x30 Oct 25 14:55:46 lt9630 kernel: [ 857.814306] [a00cb1f0] ? firegl_cmmqs_createdriver+0x170/0x170 [fglrx] Oct 25 14:55:46 lt9630 kernel: [ 857.814322] [a00a9e18] ? firegl_ioctl+0x1e8/0x250 [fglrx] Oct 25 14:55:46 lt9630 kernel: [ 857.814333] [a009a9be] ? ip_firegl_unlocked_ioctl+0xe/0x20 [fglrx] Oct 25 14:55:46 lt9630 kernel: [ 857.814335] [8117939a] ? do_vfs_ioctl+0x8a/0x340 Oct 25 14:55:46 lt9630 kernel: [ 857.814338] [811679ed] ? vfs_read+0x10d/0x180 Oct 25 14:55:46 lt9630 kernel: [ 857.814339] [811796e1] ? sys_ioctl+0x91/0xa0 Oct 25 14:55:46 lt9630 kernel: [ 857.814342] [815f22c2] ? system_call_fastpath+0x16/0x1b Oct 25 14:55:46 lt9630 kernel: [ 857.814345] pubdev:0xa02fd600, num of device:1 , name:fglrx, major 8, minor 88. Oct 25 14:55:46 lt9630 kernel: [ 857.814346] device 0 : 0x88019b85 . Oct 25 14:55:46 lt9630 kernel: [ 857.814345] pubdev:0xa02fd600, num of device:1 , name:fglrx, major 8, minor 88. Oct 25 14:55:46 lt9630 kernel: [ 857.814346] device 0 : 0x88019b85 . Oct 25 14:55:46 lt9630 kernel: [ 857.814348] Asic ID:0x6779, revision:0x3c, MMIOReg:0xc90012b8. Oct 25 14:55:46 lt9630 kernel: [ 857.814349] FB phys addr: 0xc000, MC :0xf, Total FB size :0x4000. Oct 25 14:55:46 lt9630 kernel: [ 857.814351] gart table MC:0xf0f8fd000, Physical:0xcf8fd000, size:0x402000. Oct 25 14:55:46 lt9630 kernel: [ 857.814353] mc_node :FB, total 1 zones Oct 25 14:55:46 lt9630 kernel: [ 857.814354] MC start:0xf, Physical:0xc000, size:0xfd0. Oct 25 14:55:46 lt9630 kernel: [ 857.814356] Mapped heap -- Offset:0x0, size:0xf8fd000, reference count:33, mapping count:0, Oct 25 14:55:46 lt9630 kernel: [ 857.814357] Mapped heap -- Offset:0x0, size:0x100, reference count:1, mapping count:0, Oct 25 14:55:46 lt9630 kernel: [ 857.814359] Mapped heap -- Offset:0xf8fd000, size:0x403000, reference count:1, mapping count:0, Oct 25 14:55:46 lt9630 kernel: [ 857.814360] mc_node :INV_FB, total 1 zones Oct 25 14:55:46 lt9630 kernel: [ 857.814362] MC start:0xf0fd0, Physical:0xcfd0, size:0x3030. Oct
[Desktop-packages] [Bug 1080514] Re: Click-and-drag in eye of gnome crashes X
** Changed in: hwe-next Assignee: (unassigned) = Timo Aaltonen (tjaalton) ** Changed in: fglrx-installer (Ubuntu) Assignee: (unassigned) = Timo Aaltonen (tjaalton) ** Changed in: amd Assignee: (unassigned) = James M. Leddy (jm-leddy) ** Changed in: amd Assignee: James M. Leddy (jm-leddy) = Jammy Zhou (jammy-zhou) ** Changed in: hwe-next Status: New = Confirmed ** Changed in: amd Status: New = Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to fglrx-installer in Ubuntu. https://bugs.launchpad.net/bugs/1080514 Title: Click-and-drag in eye of gnome crashes X Status in amd: Confirmed Status in HWE Next Project: Confirmed Status in “fglrx-installer” package in Ubuntu: Confirmed Bug description: If I open any image with eog (I tried several different .png and .svg files), then click and drag with the left mouse button inside the window, X immediately crashes and I get taken back to the login screen. If no image file is open, nothing happens. The behaviour is the same in Unity and Xfce. I'm running 64-bit Ubuntu 12.04, fully updated, on a Dell Inspiron 15R 5520 laptop with an AMD Radeon HD 7600M graphics card and the official 64-bit AMD driver (not sure how to tell which version - it was the latest a couple of months ago anyway). xorg's version is 1:7.6+12ubuntu1, and eog's is 3.4.2-0ubuntu1.1. If I redirect the output from eog to a file, I get: (eog:22355): Gdk-WARNING **: eog: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.0. /var/log/Xorg.0.log.old contains the following backtrace: [ 37534.034] (II) fglrx(0): EDID vendor LGD, prod id 826 [ 37534.034] (II) fglrx(0): Printing DDC gathered Modelines: [ 37534.034] (II) fglrx(0): Modeline 1366x768x0.0 76.50 1366 1402 1450 1546 768 771 776 824 -hsync -vsync (49.5 kHz) [ 37534.034] (II) fglrx(0): Modeline 1366x768x0.0 51.00 1366 1402 1450 1564 768 771 776 814 -hsync -vsync (32.6 kHz) [ 37534.113] (II) fglrx(0): EDID vendor LGD, prod id 826 [ 37534.113] (II) fglrx(0): Printing DDC gathered Modelines: [ 37534.113] (II) fglrx(0): Modeline 1366x768x0.0 76.50 1366 1402 1450 1546 768 771 776 824 -hsync -vsync (49.5 kHz) [ 37534.113] (II) fglrx(0): Modeline 1366x768x0.0 51.00 1366 1402 1450 1564 768 771 776 814 -hsync -vsync (32.6 kHz) [ 37536.071] (II) XKB: reuse xkmfile /var/lib/xkb/server-4E634B280B0E5C069EA80E39EF9080F0A8FC0600.xkm [ 37554.682] (II) fglrx(0): EDID vendor LGD, prod id 826 [ 37554.682] (II) fglrx(0): Printing DDC gathered Modelines: [ 37554.682] (II) fglrx(0): Modeline 1366x768x0.0 76.50 1366 1402 1450 1546 768 771 776 824 -hsync -vsync (49.5 kHz) [ 37554.682] (II) fglrx(0): Modeline 1366x768x0.0 51.00 1366 1402 1450 1564 768 771 776 814 -hsync -vsync (32.6 kHz) [ 41235.982] (II) fglrx(0): EDID vendor LGD, prod id 826 [ 41235.982] (II) fglrx(0): Printing DDC gathered Modelines: [ 41235.982] (II) fglrx(0): Modeline 1366x768x0.0 76.50 1366 1402 1450 1546 768 771 776 824 -hsync -vsync (49.5 kHz) [ 41235.982] (II) fglrx(0): Modeline 1366x768x0.0 51.00 1366 1402 1450 1564 768 771 776 814 -hsync -vsync (32.6 kHz) [ 49260.131] Backtrace: [ 49260.131] 0: /usr/bin/X (xorg_backtrace+0x26) [0x7f96c3ba2876] [ 49260.131] 1: /usr/bin/X (0x7f96c3a1a000+0x18c71a) [0x7f96c3ba671a] [ 49260.131] 2: /lib/x86_64-linux-gnu/libpthread.so.0 (0x7f96c2d4+0xfcb0) [0x7f96c2d4fcb0] [ 49260.131] 3: /usr/bin/X (miResolveColor+0x3) [0x7f96c3b7fda3] [ 49260.131] 4: /usr/bin/X (FakeAllocColor+0x62) [0x7f96c3a5ab72] [ 49260.131] 5: /usr/bin/X (0x7f96c3a1a000+0x1779d8) [0x7f96c3b919d8] [ 49260.131] 6: /usr/bin/X (0x7f96c3a1a000+0x1797c1) [0x7f96c3b937c1] [ 49260.131] 7: /usr/bin/X (miPointerUpdateSprite+0x29d) [0x7f96c3b8d93d] [ 49260.131] 8: /usr/bin/X (0x7f96c3a1a000+0x173c2d) [0x7f96c3b8dc2d] [ 49260.131] 9: /usr/bin/X (0x7f96c3a1a000+0xdb9f9) [0x7f96c3af59f9] [ 49260.131] 10: /usr/bin/X (0x7f96c3a1a000+0x1119ca) [0x7f96c3b2b9ca] [ 49260.131] 11: /usr/bin/X (0x7f96c3a1a000+0x560a9) [0x7f96c3a700a9] [ 49260.131] 12: /usr/bin/X (0x7f96c3a1a000+0x5e7a7) [0x7f96c3a787a7] [ 49260.131] 13: /usr/bin/X (0x7f96c3a1a000+0x58000) [0x7f96c3a72000] [ 49260.131] 14: /usr/bin/X (0x7f96c3a1a000+0x126caa) [0x7f96c3b40caa] [ 49260.132] 15: /usr/bin/X (0x7f96c3a1a000+0x4e8a1) [0x7f96c3a688a1] [ 49260.132] 16: /usr/bin/X (0x7f96c3a1a000+0x3d7ba) [0x7f96c3a577ba] [ 49260.132] 17: /lib/x86_64-linux-gnu/libc.so.6 (__libc_start_main+0xed) [0x7f96c1bd176d] [ 49260.132] 18: /usr/bin/X (0x7f96c3a1a000+0x3daad) [0x7f96c3a57aad] [ 49260.132] Segmentation fault at address 0x7f86c55810e6 [ 49260.132] Caught signal 11 (Segmentation fault). Server aborting [ 49260.132] Please consult the The X.Org Foundation support at http://wiki.x.org for help. [ 49260.132] Please also check the log file at /var
[Desktop-packages] [Bug 1061924] Re: Need Antenna quirks for some platforms
** Branch unlinked: lp:~jm-leddy/network-manager/quirk-lenovo-b480 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1061924 Title: Need Antenna quirks for some platforms Status in NetworkManager: New Status in “network-manager” package in Ubuntu: New Status in “udev” package in Ubuntu: Triaged Status in “network-manager” source package in Precise: New Status in “udev” source package in Precise: Confirmed Status in “network-manager” source package in Quantal: New Status in “udev” source package in Quantal: Triaged Bug description: It has recently come to our attention that some laptops, in particular the lenovo b470 machines, have only one antenna. Unfortunately, they have decided to attach the auxilary antenna in the factory and not the main antenna. Udev sounds like the right place to quirk for this. Presently we're using an upstart job, the text of which is : # LenovoBx70eAtherosAntenna.conf # # Lenovo B[45]70e systems with Atheros AR9285 wifi only have one # antenna, but the ath9k driver defaults to using two antennas (Main # for Tx, Aux for Rx). This job reconfigures the driver to use the # main antenna for both Tx and Rx before networking starts. description Fix antenna configuration for Atheros wifi on b470e/b570e start on starting networking task script # only required for Lenovo B470e and B570e dmidecode --string system-version | grep --quiet --line-regex Lenovo B[45]70e || exit 0 # only required for Atheros AR9285 devices lspci -n | grep --quiet --extended-regexp ^[0-9a-f:.]* 0280: 168c:002b || exit 0 # configure the device to use antenna 1 (Main) for both tx and rx iw phy0 set antenna 1 1 end script To manage notifications about this bug go to: https://bugs.launchpad.net/network-manager/+bug/1061924/+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)
Hi Martin, I don't think we should close it just yet. The key still maps to micmute (as you mention), and upstream udev and X and gnome-settings-daemon all agree on f20. I can prepare a bzr branch if it makes things easier. Alternately we could just wait for udev v199 or greater to land in the distro, but I don't consider it closed. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-input-evdev 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: Triaged Status in central project for keyboard configuration: Fix Released Status in “gnome-settings-daemon” package in Ubuntu: Triaged Status in “udev” package in Ubuntu: Invalid Status in “xserver-xorg-input-evdev” package in Ubuntu: Triaged Status in “gnome-settings-daemon” source package in Raring: Triaged Status in “udev” source package in Raring: Invalid Status in “xserver-xorg-input-evdev” source package in Raring: Triaged Bug description: Ubuntu 9.04 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)
Great! Thanks for the clarification. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-input-evdev 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: Triaged 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 “xserver-xorg-input-evdev” package in Ubuntu: Triaged Status in “gnome-settings-daemon” source package in Raring: Triaged Status in “udev” source package in Raring: Triaged Status in “xserver-xorg-input-evdev” source package in Raring: Triaged Bug description: Ubuntu 9.04 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)
We need to SRU udev as well, and ultimately g-s-d so that it actually mutes the volume when it gets this keycode. I'll work on the SRU template since Lenovo would probably like this to work in 12.04 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-input-evdev 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: Triaged Status in central project for keyboard configuration: Fix Released Status in “gnome-settings-daemon” package in Ubuntu: Triaged Status in “udev” package in Ubuntu: Triaged Status in “xserver-xorg-input-evdev” package in Ubuntu: Triaged Status in “gnome-settings-daemon” source package in Raring: Triaged Status in “udev” source package in Raring: Triaged Status in “xserver-xorg-input-evdev” source package in Raring: Triaged Bug description: Ubuntu 9.04 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)
Here is the commit for reference: http://cgit.freedesktop.org/systemd/systemd/commit/keymaps?id=1563c0c35a8005f5b71f04abe32c95d849efb420 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-input-evdev 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: Triaged Status in central project for keyboard configuration: Fix Released Status in “gnome-settings-daemon” package in Ubuntu: Triaged Status in “udev” package in Ubuntu: Triaged Status in “xserver-xorg-input-evdev” package in Ubuntu: Triaged Status in “gnome-settings-daemon” source package in Raring: Triaged Status in “udev” source package in Raring: Triaged Status in “xserver-xorg-input-evdev” source package in Raring: Triaged Bug description: Ubuntu 9.04 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 881526] Re: System freezes, kernel crashes, [fglrx] ASIC hang happened
** Changed in: amd Status: Triaged = Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to fglrx-installer in Ubuntu. https://bugs.launchpad.net/bugs/881526 Title: System freezes, kernel crashes, [fglrx] ASIC hang happened Status in amd: Fix Released Status in AMD fglrx video driver: Won't Fix Status in HWE Next Project: New Status in OEM Priority Project: Invalid Status in “fglrx-installer” package in Ubuntu: Confirmed Bug description: The system freezes intermittently and the kernel crashes a few seconds later. This has only happened since upgrading to 11.10. Found the following error in /var/log/kern.log which coincides: Oct 25 14:53:46 lt9630 kernel: [ 737.900416] INFO: rcu_sched_state detected stall on CPU 2 (t=15000 jiffies) Oct 25 14:55:46 lt9630 kernel: [ 857.813946] [fglrx] ASIC hang happened Oct 25 14:55:46 lt9630 kernel: [ 857.813950] Pid: 1149, comm: Xorg Tainted: P C 3.0.0-12-generic #20-Ubuntu Oct 25 14:55:46 lt9630 kernel: [ 857.813951] Call Trace: Oct 25 14:55:46 lt9630 kernel: [ 857.813985] [a00a0d7e] KCL_DEBUG_OsDump+0xe/0x10 [fglrx] Oct 25 14:55:46 lt9630 kernel: [ 857.814003] [a00ae20c] firegl_hardwareHangRecovery+0x1c/0x50 [fglrx] Oct 25 14:55:46 lt9630 kernel: [ 857.814036] [a013ad59] ? _ZN4Asic9WaitUntil15ResetASICIfHungEv+0x9/0x10 [fglrx] Oct 25 14:55:46 lt9630 kernel: [ 857.814068] [a013ad0c] ? _ZN4Asic9WaitUntil15WaitForCompleteEv+0x6c/0xb0 [fglrx] Oct 25 14:55:46 lt9630 kernel: [ 857.814099] [a0135fb4] ? _ZN15ExecutableUnits10CPRingIdleE15idle_WaitMethod12_QS_CP_RING_+0xe4$ Oct 25 14:55:46 lt9630 kernel: [ 857.814127] [a0115acb] ? _ZN10CMMSurfaceD1Ev+0xcb/0xe0 [fglrx] Oct 25 14:55:46 lt9630 kernel: [ 857.814158] [a0135e7b] ? _ZN15ExecutableUnits7PM4idleE15idle_WaitMethod+0x4b/0x90 [fglrx] Oct 25 14:55:46 lt9630 kernel: [ 857.814187] [a012e8f1] ? _ZN15QS_PRIVATE_CORE9QsPM4idleE15idle_WaitMethod+0x31/0x60 [fglrx] Oct 25 14:55:46 lt9630 kernel: [ 857.814215] [a0119d8a] ? _ZN10QS_PRIVATE11synchronizeEv+0x2a/0x30 [fglrx] Oct 25 14:55:46 lt9630 kernel: [ 857.814243] [a01233f5] ? _Z8uCWDDEQCmjjPvjS_+0x3b5/0x10c0 [fglrx] Oct 25 14:55:46 lt9630 kernel: [ 857.814246] [810871ee] ? down+0x2e/0x50 Oct 25 14:55:46 lt9630 kernel: [ 857.814266] [a00cc932] ? firegl_cmmqs_CWDDE_32+0x332/0x440 [fglrx] Oct 25 14:55:46 lt9630 kernel: [ 857.814285] [a00cb260] ? firegl_cmmqs_CWDDE32+0x70/0x100 [fglrx] Oct 25 14:55:46 lt9630 kernel: [ 857.814288] [81282e5a] ? security_capable+0x2a/0x30 Oct 25 14:55:46 lt9630 kernel: [ 857.814306] [a00cb1f0] ? firegl_cmmqs_createdriver+0x170/0x170 [fglrx] Oct 25 14:55:46 lt9630 kernel: [ 857.814322] [a00a9e18] ? firegl_ioctl+0x1e8/0x250 [fglrx] Oct 25 14:55:46 lt9630 kernel: [ 857.814333] [a009a9be] ? ip_firegl_unlocked_ioctl+0xe/0x20 [fglrx] Oct 25 14:55:46 lt9630 kernel: [ 857.814335] [8117939a] ? do_vfs_ioctl+0x8a/0x340 Oct 25 14:55:46 lt9630 kernel: [ 857.814338] [811679ed] ? vfs_read+0x10d/0x180 Oct 25 14:55:46 lt9630 kernel: [ 857.814339] [811796e1] ? sys_ioctl+0x91/0xa0 Oct 25 14:55:46 lt9630 kernel: [ 857.814342] [815f22c2] ? system_call_fastpath+0x16/0x1b Oct 25 14:55:46 lt9630 kernel: [ 857.814345] pubdev:0xa02fd600, num of device:1 , name:fglrx, major 8, minor 88. Oct 25 14:55:46 lt9630 kernel: [ 857.814346] device 0 : 0x88019b85 . Oct 25 14:55:46 lt9630 kernel: [ 857.814345] pubdev:0xa02fd600, num of device:1 , name:fglrx, major 8, minor 88. Oct 25 14:55:46 lt9630 kernel: [ 857.814346] device 0 : 0x88019b85 . Oct 25 14:55:46 lt9630 kernel: [ 857.814348] Asic ID:0x6779, revision:0x3c, MMIOReg:0xc90012b8. Oct 25 14:55:46 lt9630 kernel: [ 857.814349] FB phys addr: 0xc000, MC :0xf, Total FB size :0x4000. Oct 25 14:55:46 lt9630 kernel: [ 857.814351] gart table MC:0xf0f8fd000, Physical:0xcf8fd000, size:0x402000. Oct 25 14:55:46 lt9630 kernel: [ 857.814353] mc_node :FB, total 1 zones Oct 25 14:55:46 lt9630 kernel: [ 857.814354] MC start:0xf, Physical:0xc000, size:0xfd0. Oct 25 14:55:46 lt9630 kernel: [ 857.814356] Mapped heap -- Offset:0x0, size:0xf8fd000, reference count:33, mapping count:0, Oct 25 14:55:46 lt9630 kernel: [ 857.814357] Mapped heap -- Offset:0x0, size:0x100, reference count:1, mapping count:0, Oct 25 14:55:46 lt9630 kernel: [ 857.814359] Mapped heap -- Offset:0xf8fd000, size:0x403000, reference count:1, mapping count:0, Oct 25 14:55:46 lt9630 kernel: [ 857.814360] mc_node :INV_FB, total 1 zones Oct 25 14:55:46 lt9630 kernel: [ 857.814362] MC start:0xf0fd0, Physical:0xcfd0, size:0x3030. Oct 25 14:55:46
[Desktop-packages] [Bug 881526] Re: System freezes, kernel crashes, [fglrx] ASIC hang happened
** Changed in: hwe-next Assignee: (unassigned) = James M. Leddy (jm-leddy) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to fglrx-installer in Ubuntu. https://bugs.launchpad.net/bugs/881526 Title: System freezes, kernel crashes, [fglrx] ASIC hang happened Status in amd: Triaged Status in AMD fglrx video driver: Won't Fix Status in HWE Next Project: New Status in OEM Priority Project: Invalid Status in “fglrx-installer” package in Ubuntu: Confirmed Bug description: The system freezes intermittently and the kernel crashes a few seconds later. This has only happened since upgrading to 11.10. Found the following error in /var/log/kern.log which coincides: Oct 25 14:53:46 lt9630 kernel: [ 737.900416] INFO: rcu_sched_state detected stall on CPU 2 (t=15000 jiffies) Oct 25 14:55:46 lt9630 kernel: [ 857.813946] [fglrx] ASIC hang happened Oct 25 14:55:46 lt9630 kernel: [ 857.813950] Pid: 1149, comm: Xorg Tainted: P C 3.0.0-12-generic #20-Ubuntu Oct 25 14:55:46 lt9630 kernel: [ 857.813951] Call Trace: Oct 25 14:55:46 lt9630 kernel: [ 857.813985] [a00a0d7e] KCL_DEBUG_OsDump+0xe/0x10 [fglrx] Oct 25 14:55:46 lt9630 kernel: [ 857.814003] [a00ae20c] firegl_hardwareHangRecovery+0x1c/0x50 [fglrx] Oct 25 14:55:46 lt9630 kernel: [ 857.814036] [a013ad59] ? _ZN4Asic9WaitUntil15ResetASICIfHungEv+0x9/0x10 [fglrx] Oct 25 14:55:46 lt9630 kernel: [ 857.814068] [a013ad0c] ? _ZN4Asic9WaitUntil15WaitForCompleteEv+0x6c/0xb0 [fglrx] Oct 25 14:55:46 lt9630 kernel: [ 857.814099] [a0135fb4] ? _ZN15ExecutableUnits10CPRingIdleE15idle_WaitMethod12_QS_CP_RING_+0xe4$ Oct 25 14:55:46 lt9630 kernel: [ 857.814127] [a0115acb] ? _ZN10CMMSurfaceD1Ev+0xcb/0xe0 [fglrx] Oct 25 14:55:46 lt9630 kernel: [ 857.814158] [a0135e7b] ? _ZN15ExecutableUnits7PM4idleE15idle_WaitMethod+0x4b/0x90 [fglrx] Oct 25 14:55:46 lt9630 kernel: [ 857.814187] [a012e8f1] ? _ZN15QS_PRIVATE_CORE9QsPM4idleE15idle_WaitMethod+0x31/0x60 [fglrx] Oct 25 14:55:46 lt9630 kernel: [ 857.814215] [a0119d8a] ? _ZN10QS_PRIVATE11synchronizeEv+0x2a/0x30 [fglrx] Oct 25 14:55:46 lt9630 kernel: [ 857.814243] [a01233f5] ? _Z8uCWDDEQCmjjPvjS_+0x3b5/0x10c0 [fglrx] Oct 25 14:55:46 lt9630 kernel: [ 857.814246] [810871ee] ? down+0x2e/0x50 Oct 25 14:55:46 lt9630 kernel: [ 857.814266] [a00cc932] ? firegl_cmmqs_CWDDE_32+0x332/0x440 [fglrx] Oct 25 14:55:46 lt9630 kernel: [ 857.814285] [a00cb260] ? firegl_cmmqs_CWDDE32+0x70/0x100 [fglrx] Oct 25 14:55:46 lt9630 kernel: [ 857.814288] [81282e5a] ? security_capable+0x2a/0x30 Oct 25 14:55:46 lt9630 kernel: [ 857.814306] [a00cb1f0] ? firegl_cmmqs_createdriver+0x170/0x170 [fglrx] Oct 25 14:55:46 lt9630 kernel: [ 857.814322] [a00a9e18] ? firegl_ioctl+0x1e8/0x250 [fglrx] Oct 25 14:55:46 lt9630 kernel: [ 857.814333] [a009a9be] ? ip_firegl_unlocked_ioctl+0xe/0x20 [fglrx] Oct 25 14:55:46 lt9630 kernel: [ 857.814335] [8117939a] ? do_vfs_ioctl+0x8a/0x340 Oct 25 14:55:46 lt9630 kernel: [ 857.814338] [811679ed] ? vfs_read+0x10d/0x180 Oct 25 14:55:46 lt9630 kernel: [ 857.814339] [811796e1] ? sys_ioctl+0x91/0xa0 Oct 25 14:55:46 lt9630 kernel: [ 857.814342] [815f22c2] ? system_call_fastpath+0x16/0x1b Oct 25 14:55:46 lt9630 kernel: [ 857.814345] pubdev:0xa02fd600, num of device:1 , name:fglrx, major 8, minor 88. Oct 25 14:55:46 lt9630 kernel: [ 857.814346] device 0 : 0x88019b85 . Oct 25 14:55:46 lt9630 kernel: [ 857.814345] pubdev:0xa02fd600, num of device:1 , name:fglrx, major 8, minor 88. Oct 25 14:55:46 lt9630 kernel: [ 857.814346] device 0 : 0x88019b85 . Oct 25 14:55:46 lt9630 kernel: [ 857.814348] Asic ID:0x6779, revision:0x3c, MMIOReg:0xc90012b8. Oct 25 14:55:46 lt9630 kernel: [ 857.814349] FB phys addr: 0xc000, MC :0xf, Total FB size :0x4000. Oct 25 14:55:46 lt9630 kernel: [ 857.814351] gart table MC:0xf0f8fd000, Physical:0xcf8fd000, size:0x402000. Oct 25 14:55:46 lt9630 kernel: [ 857.814353] mc_node :FB, total 1 zones Oct 25 14:55:46 lt9630 kernel: [ 857.814354] MC start:0xf, Physical:0xc000, size:0xfd0. Oct 25 14:55:46 lt9630 kernel: [ 857.814356] Mapped heap -- Offset:0x0, size:0xf8fd000, reference count:33, mapping count:0, Oct 25 14:55:46 lt9630 kernel: [ 857.814357] Mapped heap -- Offset:0x0, size:0x100, reference count:1, mapping count:0, Oct 25 14:55:46 lt9630 kernel: [ 857.814359] Mapped heap -- Offset:0xf8fd000, size:0x403000, reference count:1, mapping count:0, Oct 25 14:55:46 lt9630 kernel: [ 857.814360] mc_node :INV_FB, total 1 zones Oct 25 14:55:46 lt9630 kernel: [ 857.814362] MC start:0xf0fd0, Physical:0xcfd0, size:0x3030
[Desktop-packages] [Bug 408903] Re: Does not handle microphone mute button (KEY_MICMUTE)
Upstream said they were willing to take my patch: https://bugs.freedesktop.org/show_bug.cgi?id=54171 ** Bug watch added: freedesktop.org Bugzilla #54171 https://bugs.freedesktop.org/show_bug.cgi?id=54171 ** Also affects: xkeyboard-config via https://bugs.freedesktop.org/show_bug.cgi?id=54171 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-input-evdev 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: Triaged Status in central project for keyboard configuration: Unknown Status in “gnome-settings-daemon” package in Ubuntu: Triaged Status in “udev” package in Ubuntu: Triaged Status in “xserver-xorg-input-evdev” package in Ubuntu: Triaged Status in “gnome-settings-daemon” source package in Raring: Triaged Status in “udev” source package in Raring: Triaged Status in “xserver-xorg-input-evdev” source package in Raring: Triaged Bug description: Ubuntu 9.04 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 445872] Re: disable-disconnect-notification option ignored
** Changed in: oem-priority/precise Status: Incomplete = Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager-applet in Ubuntu. https://bugs.launchpad.net/bugs/445872 Title: disable-disconnect-notification option ignored Status in OEM Priority Project: Fix Released Status in OEM Priority Project precise series: Fix Released Status in OEM Priority Project quantal series: Fix Released Status in “network-manager-applet” package in Ubuntu: Fix Released Status in “network-manager-applet” source package in Precise: Fix Released Status in “network-manager-applet” source package in Quantal: Fix Released Bug description: [Impact] For OEM's, we offer a video that runs on first boot kick things off. Invariably, nm-applet winds up printing a disconnect notification, which detracts from the quality feeling of the video. We would like to get this working in Ubuntu so for 12.04.2 we can use disable- disconnect-notification instead of our hard-coded workaround. [Test Case] The popups can be disabled by either running the following commands and then restarting or logging off / on: gconftool -s /apps/nm-applet/disable-disconnected-notifications --type=bool true gconftool -s /apps/nm-applet/disable-connected-notifications --type=bool true gconftool -s /apps/nm-applet/suppress-wireless-networks-available = true OR The following can be hard-coded into /var/lib/gconf/debian.mandatory/%gconf.xml ?xml version=1.0? gconf dir name=apps dir name=nm-applet entry name=suppress-wireless-networks-available mtime=1334087625 type=bool value=true/ entry name=disable-connected-notifications mtime=1334087553 type=bool value=true/ entry name=disable-disconnected-notifications mtime=1334087516 type=bool value=true/ /dir /dir /gconf [Regression Potential] Minimal. This change is only 2 changed lines, and we've already released in 12.10 without problems. [Original Description] the gconf key /apps/nm-applet/disable-disconnected-notifications does not disable disconnect notifications, while the other works for connected notifications. ProblemType: Bug Architecture: amd64 CRDA: Error: [Errno 2] No such file or directory Date: Thu Oct 8 00:50:27 2009 DistroRelease: Ubuntu 9.10 Gconf: IfupdownConfig: auto lo iface lo inet loopback IpRoute: 192.168.5.0/24 dev wlan0 proto kernel scope link src 192.168.5.2 metric 2 169.254.0.0/16 dev wlan0 scope link metric 1000 default via 192.168.5.1 dev wlan0 proto static Package: network-manager-gnome 0.8~a~git.20091002t194214.8515a07-0ubuntu1 ProcVersionSignature: Ubuntu 2.6.31-12.40-generic RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: network-manager-applet Uname: Linux 2.6.31-12-generic x86_64 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/445872/+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 771150] Re: [Feature] support the external headphone/microphone jack sensing
Marking released in accordance with comment #16. ** Changed in: oem-priority/precise Status: Incomplete = Fix Released ** Changed in: oem-priority Status: Incomplete = Fix Released ** Changed in: oem-priority/quantal Status: Incomplete = Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/771150 Title: [Feature] support the external headphone/microphone jack sensing Status in OEM Priority Project: Fix Released Status in OEM Priority Project precise series: Fix Released Status in OEM Priority Project quantal series: Fix Released Status in PulseAudio sound server: New Status in “alsa-driver” package in Ubuntu: Fix Released Bug description: The eeepc has a combined hole shared by the external microphone and headphone. Currently the default behaviour in Ubuntu is for headphone. (The music comes from headphone and the internal speaker is muted when plugging the headphone). This bug is intended for discussing and tracking the possibility and practicability of the support both headphone/microphone jack sensing in Linux driver or it is only achievable to support either one. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/771150/+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 445872] Re: disable-disconnect-notification option ignored
** Changed in: oem-priority/precise Status: In Progress = Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager-applet in Ubuntu. https://bugs.launchpad.net/bugs/445872 Title: disable-disconnect-notification option ignored Status in OEM Priority Project: Fix Released Status in OEM Priority Project precise series: Incomplete Status in OEM Priority Project quantal series: Fix Released Status in “network-manager-applet” package in Ubuntu: Fix Released Status in “network-manager-applet” source package in Precise: Fix Committed Status in “network-manager-applet” source package in Quantal: Fix Released Bug description: [Impact] For OEM's, we offer a video that runs on first boot kick things off. Invariably, nm-applet winds up printing a disconnect notification, which detracts from the quality feeling of the video. We would like to get this working in Ubuntu so for 12.04.2 we can use disable- disconnect-notification instead of our hard-coded workaround. [Test Case] The popups can be disabled by either running the following commands and then restarting or logging off / on: gconftool -s /apps/nm-applet/disable-disconnected-notifications --type=bool true gconftool -s /apps/nm-applet/disable-connected-notifications --type=bool true gconftool -s /apps/nm-applet/suppress-wireless-networks-available = true OR The following can be hard-coded into /var/lib/gconf/debian.mandatory/%gconf.xml ?xml version=1.0? gconf dir name=apps dir name=nm-applet entry name=suppress-wireless-networks-available mtime=1334087625 type=bool value=true/ entry name=disable-connected-notifications mtime=1334087553 type=bool value=true/ entry name=disable-disconnected-notifications mtime=1334087516 type=bool value=true/ /dir /dir /gconf [Regression Potential] Minimal. This change is only 2 changed lines, and we've already released in 12.10 without problems. [Original Description] the gconf key /apps/nm-applet/disable-disconnected-notifications does not disable disconnect notifications, while the other works for connected notifications. ProblemType: Bug Architecture: amd64 CRDA: Error: [Errno 2] No such file or directory Date: Thu Oct 8 00:50:27 2009 DistroRelease: Ubuntu 9.10 Gconf: IfupdownConfig: auto lo iface lo inet loopback IpRoute: 192.168.5.0/24 dev wlan0 proto kernel scope link src 192.168.5.2 metric 2 169.254.0.0/16 dev wlan0 scope link metric 1000 default via 192.168.5.1 dev wlan0 proto static Package: network-manager-gnome 0.8~a~git.20091002t194214.8515a07-0ubuntu1 ProcVersionSignature: Ubuntu 2.6.31-12.40-generic RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: network-manager-applet Uname: Linux 2.6.31-12-generic x86_64 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/445872/+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 861171] Re: Shutdown from greeter does nothing when multiple accounts open
Mathieu is fixing this in saucy at the moment. We should have a fix for saucy as well as the SRU shortly. Thanks Mathieu! ** Changed in: unity-greeter (Ubuntu) Assignee: Omer Akram (om26er) = (unassigned) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-session in Ubuntu. https://bugs.launchpad.net/bugs/861171 Title: Shutdown from greeter does nothing when multiple accounts open Status in The Session Menu: Triaged Status in LightDM GTK+ Greeter: Triaged Status in OEM Priority Project: In Progress Status in OEM Priority Project precise series: In Progress Status in Unity Greeter: Triaged Status in “gnome-session” package in Ubuntu: Confirmed Status in “indicator-session” package in Ubuntu: In Progress Status in “policykit” package in Ubuntu: Confirmed Status in “unity-greeter” package in Ubuntu: Invalid Bug description: [Impact] * A user tries to shut down their machine. They get confused because nothing happens when they click shutdown. * If someone else is logged in, they will have to ask that person to Switch User to log in and log out * If someone else is logged in and you don't know the password of the account, you can't shut down [Test Case] * Have two login accounts * Log both people in, via power cog-lock screen-switch user * lock the screen on current account, via power cog-lock screen * get back to lightdm via switch user * log in to an already logged in account, and try to power off the machine [Regression Potential] * It wasn't possible to shutdown at all before * I can't see a case for a regression, since it never worked to begin with [Original Report] Selecting shutdown from the greeter does nothing when multiple accounts are open. This is because the lightdm user (which the greeter runs as) does not have permission to shutdown while sessions are open. Inside a normal session this would just return you to the login screen. The solution is either for the indicator to say not allowed or to run a PolicyKit frontend in the greeter than can get the required permissions to perform the shutdown.s To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-session/+bug/861171/+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 1011073] Re: NetworkManager submenus sometimes unpopulated
** Also affects: libdbusmenu (Ubuntu) Importance: Undecided Status: New ** Changed in: libdbusmenu (Ubuntu) Assignee: (unassigned) = Charles Kerr (charlesk) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager-applet in Ubuntu. https://bugs.launchpad.net/bugs/1011073 Title: NetworkManager submenus sometimes unpopulated Status in OEM Priority Project: New Status in OEM Priority Project precise series: New Status in OEM Priority Project quantal series: New Status in OEM Priority Project raring series: New Status in “libdbusmenu” package in Ubuntu: New Status in “network-manager-applet” package in Ubuntu: Triaged Bug description: Submenus in Network Manager are sometimes unusable as they are not populated. This happens both with the list of available networks and with the VPN list. When the bug happens, it occurs for *both* the wireless submenu and the VPN menu. I know there are entries for those submenus as I can see them with other network UI mechanisms. The issue is intermittent. Expected: Dropping down the menu then hovering over the submenu trigger-point (example: More networks) shows the additional expected entries (example: more wifi networks to choose from). Actual: Dropping down the menu and hovering over the submenu trigger displays a submenu but the submenu has nothing in it and is unusable. Ubuntu 12.04 network-manager 0.9.4.0-0ubuntu4.1 Apple Macbook Pro 8,1 03:00.0 Network controller: Broadcom Corporation BCM4331 802.11a/b/g/n (rev 02) 02:00.0 Ethernet controller: Broadcom Corporation NetXtreme BCM57765 Gigabit Ethernet PCIe (rev 10) To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1011073/+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 780602] Re: nm-applet leaks memory
** Changed in: libdbusmenu (Ubuntu) Status: Confirmed = Invalid ** No longer affects: libdbusmenu (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager-applet in Ubuntu. https://bugs.launchpad.net/bugs/780602 Title: nm-applet leaks memory Status in OEM Priority Project: Fix Released Status in OEM Priority Project precise series: Fix Released Status in OEM Priority Project quantal series: Fix Released Status in “network-manager-applet” package in Ubuntu: Fix Released Status in “network-manager-applet” source package in Precise: Fix Released Status in “network-manager-applet” source package in Quantal: Fix Released Bug description: The nm-applet embedded in the task bar becomes indeterminestically unresponsive. Clicking on the applet will still show the popup menu, but none of the menu entries respond to mouse clicks. When this happens, the VPN connections and Other networks menus also show up completely empty (only a small menu stub is displayed). It is uncertain what causes this behavior. It was originally thought that the cause was memory leaks in nm-applet: nm-applet leaks memory in a fresh install of Natty, increasing to over 200 Mb in 6-8 hours. However, fixes for the memory leaks failed to resolve the occurrence of the anomalous behavior described above. dbus-monitor shows errors such as the following when clicking a menu item or attempting to access a submenu: error sender=:1.14 - dest=:1.67 error_name=org.gtk.GDBus.UnmappedGError.Quark._LIBDBUSMENU_2dGLIB.Code0 reply_serial=107705 string The IDs supplied '[80846]' do not refer to any menu items we have The errors are returned by bus_event_group or bus_about_to_show_group in libdbusmenu-glib/server.c. -- Stable Release Update Application: [Impact] This issue affects most and any users of nm-applet, especially in environments (such as offices) where the detected wireless networks change a lot, and where roaming can occur frequently. [Test Case] Run nm-applet for multiple hours: - Observe that the VPN Connections submenu still opens and lists connections (if VPN connections are configured) - Observe that the More networks submenu for additional detected wireless networks still opens and lists networks. A common failure case is where such a submenu will open but show an empty list (a piece of menu a few milimeters long). [Regression Potential] Minimal, the fixes have been available for a while in the development release (and in other recent releases) with no regressions; furthermore, this corrects obviously wrong memory handling without changing the effective behavior of the application. Possible issues could be introducing new memory leaks with the changes however, and although the risk is minimal, this could cause the same failure behavior as listed above under [Test Case]. -- ProblemType: Bug DistroRelease: Ubuntu 11.04 Package: network-manager-gnome 0.8.4~git.20110318t152954.9c4c9a0-0ubuntu1 ProcVersionSignature: Ubuntu 2.6.38-9.43-generic-pae 2.6.38.4 Uname: Linux 2.6.38-9-generic-pae i686 NonfreeKernelModules: nvidia Architecture: i386 CRDA: Error: [Errno 2] No such file or directory Date: Tue May 10 11:53:09 2011 EcryptfsInUse: Yes IfupdownConfig: auto lo iface lo inet loopback InstallationMedia: Ubuntu 11.04 Natty Narwhal - Beta i386 (20110413) IpRoute: 192.168.2.0/24 dev eth0 proto kernel scope link src 192.168.2.12 metric 1 169.254.0.0/16 dev eth0 scope link metric 1000 default via 192.168.2.1 dev eth0 proto static Keyfiles: Error: [Errno 2] No such file or directory NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true ProcEnviron: LANGUAGE=en_CA:en PATH=(custom, user) LANG=en_CA.UTF-8 SHELL=/bin/bash SourcePackage: network-manager-applet UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/780602/+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 1011073] Re: NetworkManager submenus sometimes unpopulated
Copying some relevant info from cyphermox: We don't need so much additional information anymore from the debug packages. Yes, the information was useful. I was able to write a small python script that reproduces the issue: https://code.launchpad.net/~mathieu-tl/+junk/test-indicator-update Playing with the delays there and the number of updates in a row, you can easily wedge dbusmenu in a matter of about an hour. As far as I'm concerned, this proves that the issue isn't in nm-applet but somewhere in the way that dbusmenu takes care of updates to the menus, but I'm still not quite sure what is wong with it. Any help is of course welcome :) ** Changed in: libdbusmenu (Ubuntu) Status: New = Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager-applet in Ubuntu. https://bugs.launchpad.net/bugs/1011073 Title: NetworkManager submenus sometimes unpopulated Status in OEM Priority Project: New Status in OEM Priority Project precise series: New Status in OEM Priority Project quantal series: New Status in OEM Priority Project raring series: New Status in “libdbusmenu” package in Ubuntu: Confirmed Status in “network-manager-applet” package in Ubuntu: Triaged Bug description: Submenus in Network Manager are sometimes unusable as they are not populated. This happens both with the list of available networks and with the VPN list. When the bug happens, it occurs for *both* the wireless submenu and the VPN menu. I know there are entries for those submenus as I can see them with other network UI mechanisms. The issue is intermittent. Expected: Dropping down the menu then hovering over the submenu trigger-point (example: More networks) shows the additional expected entries (example: more wifi networks to choose from). Actual: Dropping down the menu and hovering over the submenu trigger displays a submenu but the submenu has nothing in it and is unusable. Ubuntu 12.04 network-manager 0.9.4.0-0ubuntu4.1 Apple Macbook Pro 8,1 03:00.0 Network controller: Broadcom Corporation BCM4331 802.11a/b/g/n (rev 02) 02:00.0 Ethernet controller: Broadcom Corporation NetXtreme BCM57765 Gigabit Ethernet PCIe (rev 10) To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1011073/+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 1041032] Re: An error occurred Location not found after automatically installing the missing gstreamer plugins.
We're closing the issue becuase the OEM has decided for now that this is a low priority. ** Changed in: oem-priority Status: Incomplete = Won't Fix ** Changed in: oem-priority/precise Status: Incomplete = Won't Fix -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to totem in Ubuntu. https://bugs.launchpad.net/bugs/1041032 Title: An error occurred Location not found after automatically installing the missing gstreamer plugins. Status in OEM Priority Project: Won't Fix Status in OEM Priority Project precise series: Won't Fix Status in Totem Movie Player: New Status in “totem” package in Ubuntu: In Progress Status in “totem” source package in Quantal: In Progress Bug description: Ubuntu: 12.04 totem: 3.0.1-0ubuntu21 There is a feature of totem that it can detect the missing gstreamer plugins and install them automatically. It will pop out this message after it finished the installation of gstreamer plugins. However totem will work normally after we reopen it. Reproduce steps: 1. Remove gstreamer0.10-ffmpeg and gstreamer0.10-plugins-ugly if they are installed. 2. Download Wildlife.wmv from http://archive.org/details/Windows7WildlifeSampleVideo 3. Open Wildlife.wmv by totem. Relative to Bug #1041287. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1041032/+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 1011073] Re: NetworkManager submenus sometimes unpopulated
** Changed in: libdbusmenu (Ubuntu) Importance: Undecided = High ** Changed in: oem-priority/precise Importance: Undecided = High ** Changed in: oem-priority/quantal Importance: Undecided = High -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager-applet in Ubuntu. https://bugs.launchpad.net/bugs/1011073 Title: NetworkManager submenus sometimes unpopulated Status in OEM Priority Project: New Status in OEM Priority Project precise series: New Status in OEM Priority Project quantal series: New Status in OEM Priority Project raring series: New Status in “libdbusmenu” package in Ubuntu: Confirmed Status in “network-manager-applet” package in Ubuntu: Triaged Bug description: Submenus in Network Manager are sometimes unusable as they are not populated. This happens both with the list of available networks and with the VPN list. When the bug happens, it occurs for *both* the wireless submenu and the VPN menu. I know there are entries for those submenus as I can see them with other network UI mechanisms. The issue is intermittent. Expected: Dropping down the menu then hovering over the submenu trigger-point (example: More networks) shows the additional expected entries (example: more wifi networks to choose from). Actual: Dropping down the menu and hovering over the submenu trigger displays a submenu but the submenu has nothing in it and is unusable. Ubuntu 12.04 network-manager 0.9.4.0-0ubuntu4.1 Apple Macbook Pro 8,1 03:00.0 Network controller: Broadcom Corporation BCM4331 802.11a/b/g/n (rev 02) 02:00.0 Ethernet controller: Broadcom Corporation NetXtreme BCM57765 Gigabit Ethernet PCIe (rev 10) To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1011073/+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 1068994] Re: button1 gets stuck after a while
** Changed in: oem-priority/precise Assignee: (unassigned) = James M. Leddy (jm-leddy) ** Changed in: oem-priority/raring Importance: High = Critical -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1068994 Title: button1 gets stuck after a while Status in OEM Priority Project: In Progress Status in OEM Priority Project precise series: In Progress Status in OEM Priority Project raring series: In Progress Status in Ubuntu on the Nexus 7: Confirmed Status in X.Org X server: In Progress Status in “xorg-server” package in Ubuntu: Confirmed Bug description: distro bug 1015183 after using the tablet for a while, the touchscreen fails to register button clicks anymore, since the button appears to be stuck down. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1068994/+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 885989] Re: white screen on second monitor when using two xsessions
Upstream approval is absolutely required here. In any case, it looks like NautilusDesktopBackground has been removed in 3.7. Would someone that uses multiple screens please try version 3.7 to see if it fixes the problem? And then maybe we can backport the changes and SRU in to the other releases: https://git.gnome.org/browse/nautilus/commit/?id=372c60d3f8590280df23f457a67652adec369697 ** Changed in: nautilus (Ubuntu) Status: Confirmed = Incomplete ** Changed in: nautilus (Ubuntu Precise) Status: Confirmed = Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/885989 Title: white screen on second monitor when using two xsessions Status in Nautilus: Confirmed Status in “nautilus” package in Ubuntu: Incomplete Status in “nautilus” source package in Precise: Incomplete Bug description: If enable dual head mode (two X screens), the second monitor went white after login with unity or unity-2d. After tracking the gnome- session, it is caused by running nautilus -n for this configuration. And if kill the nautilus process, the desktop showed up normally on second screen. lsb_release -rd Description:Ubuntu 11.10 Release:11.10 apt-cache policy nautilus nautilus: Installed: 1:3.2.1-0ubuntu2 Candidate: 1:3.2.1-0ubuntu2 Version table: *** 1:3.2.1-0ubuntu2 0 500 http://cn.archive.ubuntu.com/ubuntu/ oneiric-updates/main amd64 Packages 100 /var/lib/dpkg/status 1:3.2.0-0ubuntu5 0 500 http://cn.archive.ubuntu.com/ubuntu/ oneiric/main amd64 Packages To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/885989/+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 1134028] Re: [Dell Vostro 3560, Inspiron 5520] fglrx does not provide glx for Radeon HD 7600M Series
** Changed in: fglrx-installer (Ubuntu) Assignee: (unassigned) = Alberto Milone (albertomilone) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to fglrx-installer in Ubuntu. https://bugs.launchpad.net/bugs/1134028 Title: [Dell Vostro 3560, Inspiron 5520] fglrx does not provide glx for Radeon HD 7600M Series Status in “fglrx-installer” package in Ubuntu: New Bug description: cid:201202-10402, 201201-10378 There are no glx support with fglrx_experimental_9 for Advanced Micro Devices [AMD] nee ATI Thames XT/GL [Radeon HD 7600M Series] [1002:6840]. Checking unity compatibility by following command: $ /usr/lib/nux/unity_support_test -c -p X Error of failed request: BadRequest (invalid request code or no such operation) Major opcode of failed request: 154 (GLX) Minor opcode of failed request: 19 (X_GLXQueryServerString) Serial number of failed request: 22 Current serial number in output stream: 22 Pacakages that installed by jockey: ii fglrx-amdcccle-experimental-92:9.010-0ubuntu0.3 Catalyst Control Center for the AMD graphics accelerators ii fglrx-experimental-9 2:9.010-0ubuntu0.3 Experimental AMD binary Xorg driver and kernel module rc fglrx-updates2:9.000-0ubuntu0.3 Video driver for the AMD graphics accelerators However it can be fix by using latest stable driver[0] from amd website[1], following this guide: https://help.ubuntu.com/community/BinaryDriverHowto/ATI GLX will be loaded without error. [0]http://www2.ati.com/drivers/linux/amd-driver-installer-catalyst-13.1-linux-x86.x86_64.zip [1]http://support.amd.com/us/gpudownload/linux/Pages/radeon_linux.aspx ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: fglrx (not installed) ProcVersionSignature: Ubuntu 3.5.0-23.35~precise1-generic 3.5.7.2 Uname: Linux 3.5.0-23-generic x86_64 NonfreeKernelModules: fglrx ApportVersion: 2.0.1-0ubuntu17.1 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] CompositorRunning: None Date: Wed Feb 27 01:37:19 2013 DistUpgraded: Fresh install DistroCodename: precise DistroVariant: ubuntu DkmsStatus: fglrx-experimental-9, 9.010, 3.5.0-23-generic, x86_64: installed GraphicsCard: Intel Corporation Ivy Bridge Graphics Controller [8086:0166] (rev 08) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:056e] Advanced Micro Devices [AMD] nee ATI Thames XT/GL [Radeon HD 7600M Series] [1002:6840] (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:056e] InstallationMedia: Ubuntu 12.04.2 LTS Precise Pangolin - Release amd64 (20130213) JockeyStatus: xorg:fglrx_experimental_9 - ATI/AMD proprietary FGLRX graphics driver (**experimental** beta) (Proprietary, Enabled, Not in use) xorg:fglrx_updates - ATI/AMD proprietary FGLRX graphics driver (post-release updates) (Proprietary, Disabled, Not in use) MachineType: Dell Inc. Vostro 3560 MarkForUpload: True ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-23-generic root=UUID=644b13de-02c4-40f5-afa6-3b8cbcf262c9 ro quiet splash initcall_debug vt.handoff=7 SourcePackage: fglrx-installer UnitySupportTest: Error: command ['/usr/lib/nux/unity_support_test', '-p', '-f'] failed with exit code 1: X Error of failed request: BadRequest (invalid request code or no such operation) Major opcode of failed request: 154 (GLX) Minor opcode of failed request: 19 (X_GLXQueryServerString) Serial number of failed request: 22 Current serial number in output stream: 22 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/03/2012 dmi.bios.vendor: Dell Inc. dmi.bios.version: X44 dmi.board.name: 0C05GV dmi.board.vendor: Dell Inc. dmi.board.version: X01 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: X44 dmi.modalias: dmi:bvnDellInc.:bvrX44:bd08/03/2012:svnDellInc.:pnVostro3560:pvrX44:rvnDellInc.:rn0C05GV:rvrX01:cvnDellInc.:ct8:cvrX44: dmi.product.name: Vostro 3560 dmi.product.version: X44 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.7.12-0ubuntu1 version.fglrx-installer: fglrx-installer N/A version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.39-0ubuntu0.1 version.libgl1-mesa-dri: libgl1-mesa-dri N/A version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev:
[Desktop-packages] [Bug 1158296] Re: Systems with AMD 6660 discrete will hang up while doing poweroff and reboot tests by pm_test tool.
AMD has requested more information such as model number etc... -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to fglrx-installer in Ubuntu. https://bugs.launchpad.net/bugs/1158296 Title: Systems with AMD 6660 discrete will hang up while doing poweroff and reboot tests by pm_test tool. Status in amd: New Status in “fglrx-installer” package in Ubuntu: New Bug description: Steps to Reproduce: 1. GM -B21 image, go through OOBE,boot into OS. 2. Copy pm_test file to Home Folder, open terminal to run sudo python pm_test -r 30 poweroff command. 3. After 20 minutes, find system hang up with backlight off. Oops: Feb 1 14:19:28 sit-HP-Pavilion-15-Notebook-PC kernel: [ 11.080151] Hardware name: HP Pavilion 15 Notebook PC Feb 1 14:19:28 sit-HP-Pavilion-15-Notebook-PC kernel: [ 11.080152] kobject_add_internal failed for msi_irqs with -EEXIST, don't try to register things with the same name in the same directory. Feb 1 14:19:28 sit-HP-Pavilion-15-Notebook-PC kernel: [ 11.080153] Modules linked in: fglrx(PO) amd_iommu_v2 snd_hda_codec_hdmi(O) snd_hda_codec_realtek(O) coretemp kvm ghash_clmulni_intel cryptd joydev hp_wmi sparse_keymap dm_multipath scsi_dh microcode snd_hda_intel(O) snd_hda_codec(O) snd_hwdep hp_accel snd_pcm lis3lv02d input_polldev uvcvideo videobuf2_core videodev videobuf2_vmalloc videobuf2_memops snd_seq_midi snd_rawmidi snd_seq_midi_event snd_seq wmi(O) rfcomm snd_timer snd_seq_device mac_hid psmouse serio_raw i915 snd drm_kms_helper parport_pc bnep drm soundcore i2c_algo_bit ppdev lpc_ich bluetooth video snd_page_alloc mei lp parport binfmt_misc r8169 dm_raid45 xor dm_mirror dm_region_hash dm_log btrfs zlib_deflate libcrc32c [last unloaded: amd_iommu_v2] Feb 1 14:19:28 sit-HP-Pavilion-15-Notebook-PC kernel: [ 11.080177] Pid: 1328, comm: Xorg Tainted: P W O 3.5.0-22-generic #33~precise1-Ubuntu Feb 1 14:19:28 sit-HP-Pavilion-15-Notebook-PC kernel: [ 11.080178] Call Trace: Feb 1 14:19:28 sit-HP-Pavilion-15-Notebook-PC kernel: [ 11.080180] [81052c9f] warn_slowpath_common+0x7f/0xc0 Feb 1 14:19:28 sit-HP-Pavilion-15-Notebook-PC kernel: [ 11.080182] [81052d96] warn_slowpath_fmt+0x46/0x50 Feb 1 14:19:28 sit-HP-Pavilion-15-Notebook-PC kernel: [ 11.080185] [811f8dee] ? release_sysfs_dirent+0x7e/0x100 Feb 1 14:19:28 sit-HP-Pavilion-15-Notebook-PC kernel: [ 11.080187] [81332594] kobject_add_internal+0x1f4/0x210 Feb 1 14:19:28 sit-HP-Pavilion-15-Notebook-PC kernel: [ 11.080189] [81332ac8] ? kobject_set_name+0x38/0x40 Feb 1 14:19:28 sit-HP-Pavilion-15-Notebook-PC kernel: [ 11.080191] [813328a6] kset_register+0x46/0x70 Feb 1 14:19:28 sit-HP-Pavilion-15-Notebook-PC kernel: [ 11.080193] [81332b46] kset_create_and_add+0x76/0xb0 Feb 1 14:19:28 sit-HP-Pavilion-15-Notebook-PC kernel: [ 11.080195] [81373d4e] populate_msi_sysfs+0x2e/0x120 Feb 1 14:19:28 sit-HP-Pavilion-15-Notebook-PC kernel: [ 11.080197] [8137433f] msi_capability_init+0x12f/0x1f0 Feb 1 14:19:28 sit-HP-Pavilion-15-Notebook-PC kernel: [ 11.080199] [81374510] pci_enable_msi_block+0x90/0xe0 Feb 1 14:19:28 sit-HP-Pavilion-15-Notebook-PC kernel: [ 11.080222] [a02d9c93] KCL_RequestMSI+0x13/0x20 [fglrx] Feb 1 14:19:28 sit-HP-Pavilion-15-Notebook-PC kernel: [ 11.080254] [a02fa9ff] IRQMGR_initialize+0x24f/0x380 [fglrx] Feb 1 14:19:28 sit-HP-Pavilion-15-Notebook-PC kernel: [ 11.080285] [a02fa757] ? IRQMGR_alloc_context+0xb7/0x110 [fglrx] Feb 1 14:19:28 sit-HP-Pavilion-15-Notebook-PC kernel: [ 11.080317] [a02f992e] ? irqmgr_wrap_initialize+0x1e/0xb0 [fglrx] Feb 1 14:19:28 sit-HP-Pavilion-15-Notebook-PC kernel: [ 11.080348] [a02fa5c5] ? firegl_irqmgr_init+0x55/0x100 [fglrx] Feb 1 14:19:28 sit-HP-Pavilion-15-Notebook-PC kernel: [ 11.080381] [a030b3ff] ? hal_init_gpu+0x1cf/0x480 [fglrx] Feb 1 14:19:28 sit-HP-Pavilion-15-Notebook-PC kernel: [ 11.080409] [a02e687b] ? firegl_open+0x2db/0x310 [fglrx] Feb 1 14:19:28 sit-HP-Pavilion-15-Notebook-PC kernel: [ 11.080430] [a02d6b27] ? ip_firegl_open+0x17/0x20 [fglrx] Feb 1 14:19:28 sit-HP-Pavilion-15-Notebook-PC kernel: [ 11.080450] [a02d5f7e] ? firegl_stub_open+0xae/0x120 [fglrx] Feb 1 14:19:28 sit-HP-Pavilion-15-Notebook-PC kernel: [ 11.080453] [8118bd92] ? chrdev_open+0xb2/0x1a0 Feb 1 14:19:28 sit-HP-Pavilion-15-Notebook-PC kernel: [ 11.080455] [8118bce0] ? cdev_put+0x30/0x30 Feb 1 14:19:28 sit-HP-Pavilion-15-Notebook-PC kernel: [ 11.080457] [811855ee] ? do_dentry_open+0x22e/0x2b0 Feb 1 14:19:28 sit-HP-Pavilion-15-Notebook-PC kernel: [ 11.080459] [81186b48] ? __dentry_open+0x18/0x70 Feb 1 14:19:28 sit-HP-Pavilion-15-Notebook-PC kernel: [ 11.080461] [81186bdd] ? vfs_open+0x3d/0x40 Feb 1 14:19:28 sit-HP-Pavilion-15-Notebook-PC kernel: [ 11.080463]
[Desktop-packages] [Bug 1158297] Re: Unit can not boot into OS with black screen when change graphic mode to Power-saving in AMD CCC and restart on DIS unit.
** Information type changed from Public to Public Security ** Information type changed from Public Security to Private -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to fglrx-installer in Ubuntu. https://bugs.launchpad.net/bugs/1158297 Title: Unit can not boot into OS with black screen when change graphic mode to Power-saving in AMD CCC and restart on DIS unit. Status in amd: New Status in “fglrx-installer” package in Ubuntu: New Bug description: Linux image and OOBE, boot into OS. Open AMD Catalyst Control Center from dash home, click Switchable Graphics table. Select the option Power-saving GPU for improved battery life and apply it. Restart unit, find unit can not boot into OS with black screen. Steps to Reproduce: 1. GM -B21 Linux image and OOBE, boot into OS. 2. Open AMD CCC from dash home, click Switchable Graphics table. 3. Select the option Power-saving GPU for improved battery life and apply it. 4. Restart unit, find unit can not boot into OS with black screen. To manage notifications about this bug go to: https://bugs.launchpad.net/amd/+bug/1158297/+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)
Unfortunately, the patch to gnome-settings-daemon didn't get in soon enough to make the raring release, and we're past feature freeze. But at the same time, we also don't have a new enough x11proto-core to use the XF86MicMute keysym anyway. The first version that works is xproto-7.0.24, released on March 29th, and the latest version debian has is 7.0.23. In any case, I've created a PPA that allows intersted people to try the new functionality present in g-s-d (using F20). Please only proceed if you are confident in what you're doing. If you're using a thinkpad, the first thing you need to do is edit your /lib/udev/keymaps/module-lenovo file so that 'micmute' is 'f20', since we will be using f20 for that key. Other laptops already have proper udev keymap files. The second thing is to make sure keycode 198 is maped to 'F20' as far as X is concerned. This is easily done with xmodmap -e keycode 198 = F20 To make it permant, edit your ~/.Xmodmap file And finally install gnome-settings-daemon from the PPA: https://launchpad.net/~jm-leddy/+archive/micmute https://wiki.archlinux.org/index.php/Xmodmap -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-input-evdev 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: Triaged Status in “gnome-settings-daemon” package in Ubuntu: Triaged Status in “udev” package in Ubuntu: Triaged Status in “xserver-xorg-input-evdev” package in Ubuntu: Triaged Status in “gnome-settings-daemon” source package in Raring: Triaged Status in “udev” source package in Raring: Triaged Status in “xserver-xorg-input-evdev” source package in Raring: Triaged Bug description: Ubuntu 9.04 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 881526] Re: System freezes, kernel crashes, [fglrx] ASIC hang happened
** Tags added: blocks-hwcert-enablement -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to fglrx-installer in Ubuntu. https://bugs.launchpad.net/bugs/881526 Title: System freezes, kernel crashes, [fglrx] ASIC hang happened Status in amd: Triaged Status in AMD fglrx video driver: Won't Fix Status in HWE Next Project: New Status in OEM Priority Project: Invalid Status in “fglrx-installer” package in Ubuntu: Confirmed Bug description: The system freezes intermittently and the kernel crashes a few seconds later. This has only happened since upgrading to 11.10. Found the following error in /var/log/kern.log which coincides: Oct 25 14:53:46 lt9630 kernel: [ 737.900416] INFO: rcu_sched_state detected stall on CPU 2 (t=15000 jiffies) Oct 25 14:55:46 lt9630 kernel: [ 857.813946] [fglrx] ASIC hang happened Oct 25 14:55:46 lt9630 kernel: [ 857.813950] Pid: 1149, comm: Xorg Tainted: P C 3.0.0-12-generic #20-Ubuntu Oct 25 14:55:46 lt9630 kernel: [ 857.813951] Call Trace: Oct 25 14:55:46 lt9630 kernel: [ 857.813985] [a00a0d7e] KCL_DEBUG_OsDump+0xe/0x10 [fglrx] Oct 25 14:55:46 lt9630 kernel: [ 857.814003] [a00ae20c] firegl_hardwareHangRecovery+0x1c/0x50 [fglrx] Oct 25 14:55:46 lt9630 kernel: [ 857.814036] [a013ad59] ? _ZN4Asic9WaitUntil15ResetASICIfHungEv+0x9/0x10 [fglrx] Oct 25 14:55:46 lt9630 kernel: [ 857.814068] [a013ad0c] ? _ZN4Asic9WaitUntil15WaitForCompleteEv+0x6c/0xb0 [fglrx] Oct 25 14:55:46 lt9630 kernel: [ 857.814099] [a0135fb4] ? _ZN15ExecutableUnits10CPRingIdleE15idle_WaitMethod12_QS_CP_RING_+0xe4$ Oct 25 14:55:46 lt9630 kernel: [ 857.814127] [a0115acb] ? _ZN10CMMSurfaceD1Ev+0xcb/0xe0 [fglrx] Oct 25 14:55:46 lt9630 kernel: [ 857.814158] [a0135e7b] ? _ZN15ExecutableUnits7PM4idleE15idle_WaitMethod+0x4b/0x90 [fglrx] Oct 25 14:55:46 lt9630 kernel: [ 857.814187] [a012e8f1] ? _ZN15QS_PRIVATE_CORE9QsPM4idleE15idle_WaitMethod+0x31/0x60 [fglrx] Oct 25 14:55:46 lt9630 kernel: [ 857.814215] [a0119d8a] ? _ZN10QS_PRIVATE11synchronizeEv+0x2a/0x30 [fglrx] Oct 25 14:55:46 lt9630 kernel: [ 857.814243] [a01233f5] ? _Z8uCWDDEQCmjjPvjS_+0x3b5/0x10c0 [fglrx] Oct 25 14:55:46 lt9630 kernel: [ 857.814246] [810871ee] ? down+0x2e/0x50 Oct 25 14:55:46 lt9630 kernel: [ 857.814266] [a00cc932] ? firegl_cmmqs_CWDDE_32+0x332/0x440 [fglrx] Oct 25 14:55:46 lt9630 kernel: [ 857.814285] [a00cb260] ? firegl_cmmqs_CWDDE32+0x70/0x100 [fglrx] Oct 25 14:55:46 lt9630 kernel: [ 857.814288] [81282e5a] ? security_capable+0x2a/0x30 Oct 25 14:55:46 lt9630 kernel: [ 857.814306] [a00cb1f0] ? firegl_cmmqs_createdriver+0x170/0x170 [fglrx] Oct 25 14:55:46 lt9630 kernel: [ 857.814322] [a00a9e18] ? firegl_ioctl+0x1e8/0x250 [fglrx] Oct 25 14:55:46 lt9630 kernel: [ 857.814333] [a009a9be] ? ip_firegl_unlocked_ioctl+0xe/0x20 [fglrx] Oct 25 14:55:46 lt9630 kernel: [ 857.814335] [8117939a] ? do_vfs_ioctl+0x8a/0x340 Oct 25 14:55:46 lt9630 kernel: [ 857.814338] [811679ed] ? vfs_read+0x10d/0x180 Oct 25 14:55:46 lt9630 kernel: [ 857.814339] [811796e1] ? sys_ioctl+0x91/0xa0 Oct 25 14:55:46 lt9630 kernel: [ 857.814342] [815f22c2] ? system_call_fastpath+0x16/0x1b Oct 25 14:55:46 lt9630 kernel: [ 857.814345] pubdev:0xa02fd600, num of device:1 , name:fglrx, major 8, minor 88. Oct 25 14:55:46 lt9630 kernel: [ 857.814346] device 0 : 0x88019b85 . Oct 25 14:55:46 lt9630 kernel: [ 857.814345] pubdev:0xa02fd600, num of device:1 , name:fglrx, major 8, minor 88. Oct 25 14:55:46 lt9630 kernel: [ 857.814346] device 0 : 0x88019b85 . Oct 25 14:55:46 lt9630 kernel: [ 857.814348] Asic ID:0x6779, revision:0x3c, MMIOReg:0xc90012b8. Oct 25 14:55:46 lt9630 kernel: [ 857.814349] FB phys addr: 0xc000, MC :0xf, Total FB size :0x4000. Oct 25 14:55:46 lt9630 kernel: [ 857.814351] gart table MC:0xf0f8fd000, Physical:0xcf8fd000, size:0x402000. Oct 25 14:55:46 lt9630 kernel: [ 857.814353] mc_node :FB, total 1 zones Oct 25 14:55:46 lt9630 kernel: [ 857.814354] MC start:0xf, Physical:0xc000, size:0xfd0. Oct 25 14:55:46 lt9630 kernel: [ 857.814356] Mapped heap -- Offset:0x0, size:0xf8fd000, reference count:33, mapping count:0, Oct 25 14:55:46 lt9630 kernel: [ 857.814357] Mapped heap -- Offset:0x0, size:0x100, reference count:1, mapping count:0, Oct 25 14:55:46 lt9630 kernel: [ 857.814359] Mapped heap -- Offset:0xf8fd000, size:0x403000, reference count:1, mapping count:0, Oct 25 14:55:46 lt9630 kernel: [ 857.814360] mc_node :INV_FB, total 1 zones Oct 25 14:55:46 lt9630 kernel: [ 857.814362] MC start:0xf0fd0, Physical:0xcfd0, size:0x3030. Oct 25 14:55:46 lt9630 kernel: [
[Desktop-packages] [Bug 1071922] Re: double tap does not open folders or files in Nautilus
** Changed in: oem-priority/precise Status: Fix Committed = Fix Released ** Changed in: oem-priority Status: Fix Committed = Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1071922 Title: double tap does not open folders or files in Nautilus Status in Nautilus: Fix Released Status in OEM Priority Project: Fix Released Status in OEM Priority Project precise series: Fix Released Status in OEM Priority Project quantal series: Fix Released Status in Ubuntu on the Nexus 7: Invalid Status in “nautilus” package in Ubuntu: Fix Released Status in “nautilus” source package in Precise: Fix Released Status in “nautilus” source package in Quantal: Won't Fix Status in “nautilus” source package in Raring: Fix Released Bug description: [Impact] Nexus7 and some Dell touch screen devices do not work well with nautilus. This makes browsing files almost impossible in these devices. Further it's frustrating to the user because there is nothing that makes it immediately apparent that [Test Case] 1. Install Ubuntu 2. Double tap to open a folder in nautilus [Regression Potential] Low, this fix just affects touch screen devices. [Original Description] On the Nexus7 device double-tapping does not work in Nautilus. Even single taps are not always registered. In thunar navigating via double tap works fine. The mouse settings panel's double tap timeout test works fine. To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/1071922/+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 1041032] Re: An error occurred Location not found after automatically installing the missing gstreamer plugins.
Hi Pascal, We don't have a patch that fixes the problem yet. Once upstream fixes it we can take their patch back and use that, but Ubuntu engineering doesn't really do development work on Totem. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to totem in Ubuntu. https://bugs.launchpad.net/bugs/1041032 Title: An error occurred Location not found after automatically installing the missing gstreamer plugins. Status in OEM Priority Project: Incomplete Status in OEM Priority Project precise series: Incomplete Status in Totem Movie Player: New Status in “totem” package in Ubuntu: In Progress Status in “totem” source package in Quantal: In Progress Bug description: Ubuntu: 12.04 totem: 3.0.1-0ubuntu21 There is a feature of totem that it can detect the missing gstreamer plugins and install them automatically. It will pop out this message after it finished the installation of gstreamer plugins. However totem will work normally after we reopen it. Reproduce steps: 1. Remove gstreamer0.10-ffmpeg and gstreamer0.10-plugins-ugly if they are installed. 2. Download Wildlife.wmv from http://archive.org/details/Windows7WildlifeSampleVideo 3. Open Wildlife.wmv by totem. Relative to Bug #1041287. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1041032/+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 771150] Re: [Feature] support the external headphone/microphone jack sensing
Hi, To anyone experiencing this issue, you're supposed to actively go into the sound settings and telling the system you plugged a microphone in - on the input tab, there should now be a Microphone or Headset Microphone option that must be selected to activate the mic. Also make sure Headphones are not selected. If you do that, and it still does not work, can you attach alsa-info and pacmd list output? ** Changed in: oem-priority Status: In Progress = Incomplete ** Changed in: oem-priority/precise Status: In Progress = Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/771150 Title: [Feature] support the external headphone/microphone jack sensing Status in OEM Priority Project: Incomplete Status in OEM Priority Project precise series: Incomplete Status in OEM Priority Project quantal series: Incomplete Status in PulseAudio sound server: New Status in “alsa-driver” package in Ubuntu: Fix Released Bug description: The eeepc has a combined hole shared by the external microphone and headphone. Currently the default behaviour in Ubuntu is for headphone. (The music comes from headphone and the internal speaker is muted when plugging the headphone). This bug is intended for discussing and tracking the possibility and practicability of the support both headphone/microphone jack sensing in Linux driver or it is only achievable to support either one. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/771150/+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 982889] Re: X trying to start before plymouth has finished using the drm driver
Moving to High prio in oem-priority since we have a workaround. ** Changed in: oem-priority Assignee: (unassigned) = James M. Leddy (jm-leddy) ** Changed in: oem-priority/precise Assignee: (unassigned) = James M. Leddy (jm-leddy) ** Changed in: oem-priority/precise Importance: Critical = Medium ** Changed in: oem-priority Importance: Critical = High ** Changed in: oem-priority/precise Importance: Medium = High -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/982889 Title: X trying to start before plymouth has finished using the drm driver Status in OEM Priority Project: In Progress Status in OEM Priority Project precise series: In Progress Status in “libdrm” package in Ubuntu: Invalid Status in “lightdm” package in Ubuntu: Triaged Status in “linux” package in Ubuntu: Invalid Status in “plymouth” package in Ubuntu: Confirmed Status in “xorg-server” package in Ubuntu: Fix Released Bug description: X server fails to start the first time after boot, it works fine when I start it again. Looks like a race condition with intel drm initialization, i guess X tries to start faster than drm driver is initialized so it fails. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: xorg 1:7.6+12ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-23.36-generic 3.2.14 Uname: Linux 3.2.0-23-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.0.1-0ubuntu3 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] CompositorRunning: compiz Date: Mon Apr 16 10:35:28 2012 DistUpgraded: Fresh install DistroCodename: precise DistroVariant: ubuntu ExtraDebuggingInterest: Yes, whatever it takes to get this fixed in Ubuntu GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0102] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. Device [1462:7750] Advanced Micro Devices [AMD] nee ATI Barts XT [ATI Radeon HD 6800 Series] [1002:6738] (prog-if 00 [VGA controller]) Subsystem: Giga-byte Technology Device [1458:21fa] InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Beta amd64 (20120301) MachineType: MSI MS-7750 ProcEnviron: LANGUAGE=en_US:en TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.2.0-23-generic root=/dev/mapper/ssd-ubuntu--precise ro quiet splash SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/25/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: V4.0 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Z68A-G43 (G3) (MS-7750) dmi.board.vendor: MSI dmi.board.version: 1.0 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrV4.0:bd08/25/2011:svnMSI:pnMS-7750:pvr1.0:rvnMSI:rnZ68A-G43(G3)(MS-7750):rvr1.0:cvnMSI:ct3:cvr1.0: dmi.product.name: MS-7750 dmi.product.version: 1.0 dmi.sys.vendor: MSI version.compiz: compiz 1:0.9.7.6-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.32-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 8.0.2-0ubuntu3 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 8.0.2-0ubuntu3 version.xserver-xorg-core: xserver-xorg-core 2:1.11.4-0ubuntu10 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.0-0ubuntu1 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/oem-priority/+bug/982889/+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 1011073] Re: NetworkManager submenus sometimes unpopulated
** Also affects: oem-priority Importance: Undecided Status: New ** Changed in: oem-priority Assignee: (unassigned) = James M. Leddy (jm-leddy) ** Changed in: oem-priority Importance: Undecided = High ** Also affects: oem-priority/precise Importance: Undecided Status: New ** Also affects: oem-priority/quantal Importance: Undecided Status: New ** Also affects: oem-priority/raring Importance: High Assignee: James M. Leddy (jm-leddy) Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager-applet in Ubuntu. https://bugs.launchpad.net/bugs/1011073 Title: NetworkManager submenus sometimes unpopulated Status in OEM Priority Project: New Status in OEM Priority Project precise series: New Status in OEM Priority Project quantal series: New Status in OEM Priority Project raring series: New Status in “network-manager-applet” package in Ubuntu: Triaged Bug description: Submenus in Network Manager are sometimes unusable as they are not populated. This happens both with the list of available networks and with the VPN list. When the bug happens, it occurs for *both* the wireless submenu and the VPN menu. I know there are entries for those submenus as I can see them with other network UI mechanisms. The issue is intermittent. Expected: Dropping down the menu then hovering over the submenu trigger-point (example: More networks) shows the additional expected entries (example: more wifi networks to choose from). Actual: Dropping down the menu and hovering over the submenu trigger displays a submenu but the submenu has nothing in it and is unusable. Ubuntu 12.04 network-manager 0.9.4.0-0ubuntu4.1 Apple Macbook Pro 8,1 03:00.0 Network controller: Broadcom Corporation BCM4331 802.11a/b/g/n (rev 02) 02:00.0 Ethernet controller: Broadcom Corporation NetXtreme BCM57765 Gigabit Ethernet PCIe (rev 10) To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1011073/+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)
Looks like this has been upstreamed as well. Since we have not yet explicitly gotten the F20 to be the new XF86MicMute key, upstream g-s-d devs just mapped it to F20 themselves. https://git.gnome.org/browse/gnome-settings-daemon/commit/?id=5cda26ee -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-input-evdev 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: Triaged Status in “gnome-settings-daemon” package in Ubuntu: Triaged Status in “udev” package in Ubuntu: Triaged Status in “xserver-xorg-input-evdev” package in Ubuntu: Triaged Status in “gnome-settings-daemon” source package in Raring: Triaged Status in “udev” source package in Raring: Triaged Status in “xserver-xorg-input-evdev” source package in Raring: Triaged Bug description: Ubuntu 9.04 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 1025508] Re: Some keys in keyboard layout show duplicate character labels
** Changed in: oem-priority/precise Status: Fix Committed = Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libgnomekbd in Ubuntu. https://bugs.launchpad.net/bugs/1025508 Title: Some keys in keyboard layout show duplicate character labels Status in GNOME Control Center: New Status in libgnomekbd: New Status in OEM Priority Project: Fix Released Status in OEM Priority Project precise series: Fix Released Status in OEM Priority Project raring series: Fix Released Status in “gnome-control-center” package in Ubuntu: Invalid Status in “libgnomekbd” package in Ubuntu: Fix Released Status in “gnome-control-center” source package in Precise: New Status in “libgnomekbd” source package in Precise: Fix Released Bug description: * Impact: The keyboard layout chart shows duplicate characters. Issue seems to have started on Ubuntu 12.04 and is present in 12.10. * Steps to reproduce: 1) Select keyboard icon from the launcher at top right of screen 2) Select Show Layout Chart menu item Keyboard layout is displayed the Function keys such as F1 show duplicate characters (i.e. F1 F1) The Numeric pad show duplicate chars for division /, multiplication *, subtraction -, and addition + Expected result: Should show only one instance of the character. * Regression potential: watch that no symbols are missing on the keyboard map drawing To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/1025508/+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 1075411] Re: Multi-monitor - Show garbage after change display mode.
Would have expired on its own but Steve reset the counter :) Set everything to invalid. ** Changed in: oem-priority Status: Incomplete = Invalid ** Changed in: oem-priority/precise Status: Incomplete = Invalid ** Changed in: unity (Ubuntu) Status: Incomplete = Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dp-unity https://bugs.launchpad.net/bugs/1075411 Title: Multi-monitor - Show garbage after change display mode. Status in OEM Priority Project: Invalid Status in OEM Priority Project precise series: Invalid Status in “unity” package in Ubuntu: Invalid Bug description: Connect to HDMI monitor, switch display mode.Find the garbage occurs. Sometimes can reproduce it when change resolutions in system settings/displays windows. Sometimes the internal display and external display always show garbage except change display mode or click keyboard. Steps to Reproduce (1): 1. boot into OS. 2. Connect to HDMI monitor, press F4 hotkey to switch display mode. 3. Find the garbage occurs. Step to Reproduce (2): 1.boot into OS. 2.Connect a monitor to unit. 3.Open system settings/displays. 4.Drag the monitors to set their place and click apply. 5.Garbagr occurs. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1075411/+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 861171] Re: Shutdown from greeter does nothing when multiple accounts open
** Changed in: unity-greeter (Ubuntu) Status: Triaged = Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-session in Ubuntu. https://bugs.launchpad.net/bugs/861171 Title: Shutdown from greeter does nothing when multiple accounts open Status in The Session Menu: Triaged Status in LightDM GTK+ Greeter: Triaged Status in OEM Priority Project: In Progress Status in OEM Priority Project precise series: In Progress Status in Unity Greeter: Triaged Status in “gnome-session” package in Ubuntu: Confirmed Status in “indicator-session” package in Ubuntu: In Progress Status in “policykit” package in Ubuntu: Confirmed Status in “unity-greeter” package in Ubuntu: Invalid Bug description: Selecting shutdown from the greeter does nothing when multiple accounts are open. This is because the lightdm user (which the greeter runs as) does not have permission to shutdown while sessions are open. Inside a normal session this would just return you to the login screen. The solution is either for the indicator to say not allowed or to run a PolicyKit frontend in the greeter than can get the required permissions to perform the shutdown. To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-session/+bug/861171/+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 861171] Re: Shutdown from greeter does nothing when multiple accounts open
** Description changed: - Selecting shutdown from the greeter does nothing when multiple accounts - are open. + [Impact] + + * A user tries to shut down their machine. They get confused because nothing happens +when they click shutdown. + * If someone else is logged in, they will have to ask that person to Switch User to +log in and log out + * If someone else is logged in and you don't know the password of the account, you +can't shut down + + [Test Case] + + * Have two login accounts + * Log both people in, via power cog-lock screen-switch user + * Log out + * log in to an account, and try to power off the machine + + [Regression Potential] + + * It wasn't possible to shutdown at all before + * I can't see a case for a regression, since it never worked to begin with + + [Original Report] + + Selecting shutdown from the greeter does nothing when multiple accounts are open. This is because the lightdm user (which the greeter runs as) does not have permission to shutdown while sessions are open. Inside a normal session this would just return you to the login screen. The solution is either for the indicator to say not allowed or to run a PolicyKit frontend in the greeter than can get the required - permissions to perform the shutdown. + permissions to perform the shutdown.s ** Description changed: [Impact] - * A user tries to shut down their machine. They get confused because nothing happens -when they click shutdown. - * If someone else is logged in, they will have to ask that person to Switch User to -log in and log out - * If someone else is logged in and you don't know the password of the account, you -can't shut down + * A user tries to shut down their machine. They get confused because nothing happens + when they click shutdown. + * If someone else is logged in, they will have to ask that person to Switch User to + log in and log out + * If someone else is logged in and you don't know the password of the account, you + can't shut down [Test Case] - * Have two login accounts - * Log both people in, via power cog-lock screen-switch user - * Log out - * log in to an account, and try to power off the machine + * Have two login accounts + * Log both people in, via power cog-lock screen-switch user + * lock the screen on current account, via power cog-lock screen + * get back to lightdm via switch user + * log in to an already logged in account, and try to power off the machine [Regression Potential] - * It wasn't possible to shutdown at all before - * I can't see a case for a regression, since it never worked to begin with + * It wasn't possible to shutdown at all before + * I can't see a case for a regression, since it never worked to begin with [Original Report] - - Selecting shutdown from the greeter does nothing when multiple accounts are open. + + Selecting shutdown from the greeter does nothing when multiple accounts + are open. This is because the lightdm user (which the greeter runs as) does not have permission to shutdown while sessions are open. Inside a normal session this would just return you to the login screen. The solution is either for the indicator to say not allowed or to run a PolicyKit frontend in the greeter than can get the required permissions to perform the shutdown.s ** Tags added: rls-s-incoming -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-session in Ubuntu. https://bugs.launchpad.net/bugs/861171 Title: Shutdown from greeter does nothing when multiple accounts open Status in The Session Menu: Triaged Status in LightDM GTK+ Greeter: Triaged Status in OEM Priority Project: In Progress Status in OEM Priority Project precise series: In Progress Status in Unity Greeter: Triaged Status in “gnome-session” package in Ubuntu: Confirmed Status in “indicator-session” package in Ubuntu: In Progress Status in “policykit” package in Ubuntu: Confirmed Status in “unity-greeter” package in Ubuntu: Invalid Bug description: [Impact] * A user tries to shut down their machine. They get confused because nothing happens when they click shutdown. * If someone else is logged in, they will have to ask that person to Switch User to log in and log out * If someone else is logged in and you don't know the password of the account, you can't shut down [Test Case] * Have two login accounts * Log both people in, via power cog-lock screen-switch user * lock the screen on current account, via power cog-lock screen * get back to lightdm via switch user * log in to an already logged in account, and try to power off the machine [Regression Potential] * It wasn't possible to shutdown at all before * I can't see a case for a regression, since it never worked to begin with [Original Report] Selecting shutdown
[Desktop-packages] [Bug 408903] Re: Does not handle microphone mute button (KEY_MICMUTE)
** Changed in: oem-priority/precise Status: Won't Fix = Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-input-evdev 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: Triaged Status in “gnome-settings-daemon” package in Ubuntu: Triaged Status in “udev” package in Ubuntu: Triaged Status in “xserver-xorg-input-evdev” package in Ubuntu: Triaged Status in “gnome-settings-daemon” source package in Raring: Triaged Status in “udev” source package in Raring: Triaged Status in “xserver-xorg-input-evdev” source package in Raring: Triaged Bug description: Ubuntu 9.04 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 965895] Re: After boot, NetworkManager indicator menu only shows four entries
verification-done based on comment #67 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager-applet in Ubuntu. https://bugs.launchpad.net/bugs/965895 Title: After boot, NetworkManager indicator menu only shows four entries Status in Ubuntu on the Nexus 7: Triaged Status in “network-manager-applet” package in Ubuntu: Fix Released Status in “network-manager-applet” source package in Precise: Fix Committed Status in “network-manager-applet” source package in Quantal: In Progress Bug description: SRU INFORMATION: see comment 61 After I boot in to the LiveCD environment for Ubuntu 12.04, I click on the NetworkManager icon in the top-right of the screen and it's only showing four items: -- | ✓ Enable Networking | ✓ Enable Wireless | -- | | Connection Information | Edit Connections... -- If I then select the Enable Networking or Enable Wireless option to disable that interface and then re-enable it, then the NetworkManager populates with all the normal menu items (listing of all WiFi SSID, VPN connection, etc.). ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: network-manager 0.9.3.995+git201203152001.04b2a74-0ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-20.32-generic 3.2.12 Uname: Linux 3.2.0-20-generic x86_64 ApportVersion: 1.95-0ubuntu1 Architecture: amd64 CasperVersion: 1.312 Date: Tue Mar 27 03:23:48 2012 IfupdownConfig: auto lo iface lo inet loopback LiveMediaBuild: Ubuntu 12.04 LTS Precise Pangolin - Alpha amd64 (20120325) NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true ProcEnviron: TERM=xterm LANG=en_US.UTF-8 SHELL=/bin/bash RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-nexus7/+bug/965895/+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 982889] Re: X trying to start before plymouth has finished using the drm driver
** Changed in: oem-priority/precise Status: New = In Progress -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/982889 Title: X trying to start before plymouth has finished using the drm driver Status in OEM Priority Project: New Status in OEM Priority Project precise series: In Progress Status in “libdrm” package in Ubuntu: Invalid Status in “lightdm” package in Ubuntu: Triaged Status in “linux” package in Ubuntu: Invalid Status in “plymouth” package in Ubuntu: Confirmed Status in “xorg-server” package in Ubuntu: Fix Released Bug description: X server fails to start the first time after boot, it works fine when I start it again. Looks like a race condition with intel drm initialization, i guess X tries to start faster than drm driver is initialized so it fails. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: xorg 1:7.6+12ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-23.36-generic 3.2.14 Uname: Linux 3.2.0-23-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.0.1-0ubuntu3 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] CompositorRunning: compiz Date: Mon Apr 16 10:35:28 2012 DistUpgraded: Fresh install DistroCodename: precise DistroVariant: ubuntu ExtraDebuggingInterest: Yes, whatever it takes to get this fixed in Ubuntu GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0102] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. Device [1462:7750] Advanced Micro Devices [AMD] nee ATI Barts XT [ATI Radeon HD 6800 Series] [1002:6738] (prog-if 00 [VGA controller]) Subsystem: Giga-byte Technology Device [1458:21fa] InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Beta amd64 (20120301) MachineType: MSI MS-7750 ProcEnviron: LANGUAGE=en_US:en TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.2.0-23-generic root=/dev/mapper/ssd-ubuntu--precise ro quiet splash SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/25/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: V4.0 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Z68A-G43 (G3) (MS-7750) dmi.board.vendor: MSI dmi.board.version: 1.0 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrV4.0:bd08/25/2011:svnMSI:pnMS-7750:pvr1.0:rvnMSI:rnZ68A-G43(G3)(MS-7750):rvr1.0:cvnMSI:ct3:cvr1.0: dmi.product.name: MS-7750 dmi.product.version: 1.0 dmi.sys.vendor: MSI version.compiz: compiz 1:0.9.7.6-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.32-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 8.0.2-0ubuntu3 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 8.0.2-0ubuntu3 version.xserver-xorg-core: xserver-xorg-core 2:1.11.4-0ubuntu10 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.0-0ubuntu1 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/oem-priority/+bug/982889/+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 771150] Re: [Feature] support the external headphone/microphone jack sensing
** Changed in: oem-priority/precise Status: Incomplete = In Progress ** Changed in: oem-priority Assignee: Chris Van Hoof (vanhoof) = James M. Leddy (jm-leddy) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/771150 Title: [Feature] support the external headphone/microphone jack sensing Status in OEM Priority Project: In Progress Status in OEM Priority Project precise series: In Progress Status in OEM Priority Project quantal series: Incomplete Status in PulseAudio sound server: New Status in “alsa-driver” package in Ubuntu: Fix Released Bug description: The eeepc has a combined hole shared by the external microphone and headphone. Currently the default behaviour in Ubuntu is for headphone. (The music comes from headphone and the internal speaker is muted when plugging the headphone). This bug is intended for discussing and tracking the possibility and practicability of the support both headphone/microphone jack sensing in Linux driver or it is only achievable to support either one. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/771150/+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 1071561] Re: [sound-nua] Bluetooth device not listed if change mode to Off
** Changed in: oem-priority Status: Fix Committed = Fix Released ** Changed in: oem-priority/precise Status: Fix Committed = Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1071561 Title: [sound-nua] Bluetooth device not listed if change mode to Off Status in GNOME Control Center: Fix Released Status in OEM Priority Project: Fix Released Status in OEM Priority Project precise series: Fix Released Status in “gnome-control-center” package in Ubuntu: Fix Released Status in “gnome-control-center” source package in Precise: Fix Released Bug description: * Impact: users can turn off bluetooth devices without being able to turn them back on * Test Case: - connect a bluetooth audio device (headset for example) - go to system settings - sound (under Unity) - look at the profiles for the bluetooth device off shouldn't be listed * Regression potential: limited, check that other profiles are listed are they should - I've accidentally changed the operation mode of my Bluetooth phone from A2DP to Off, then the device is removed from the list. Instead, it should be marked as disabled, and kept on list, so I could reactivate it later. To reactivate, I needed to install tdbtools, open tdb file that store this settings (pulseaudio), then remove my device from records. After that, the device was listed again on Sound Settings as A2DP sound output. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/1071561/+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)
** Changed in: oem-priority/precise Importance: Undecided = Medium ** Changed in: oem-priority/precise Assignee: (unassigned) = James M. Leddy (jm-leddy) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-input-evdev 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: Triaged Status in “gnome-settings-daemon” package in Ubuntu: Triaged Status in “udev” package in Ubuntu: Triaged Status in “xserver-xorg-input-evdev” package in Ubuntu: Triaged Status in “gnome-settings-daemon” source package in Raring: Triaged Status in “udev” source package in Raring: Triaged Status in “xserver-xorg-input-evdev” source package in Raring: Triaged Bug description: Ubuntu 9.04 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 1071922] Re: double tap does not open folders or files in Nautilus
** Tags removed: verification-needed ** Tags added: verification-done -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1071922 Title: double tap does not open folders or files in Nautilus Status in Nautilus: Fix Released Status in OEM Priority Project: Fix Committed Status in OEM Priority Project precise series: Fix Committed Status in OEM Priority Project quantal series: Fix Released Status in Ubuntu on the Nexus 7: Invalid Status in “nautilus” package in Ubuntu: Fix Released Status in “nautilus” source package in Precise: Fix Committed Status in “nautilus” source package in Quantal: Won't Fix Status in “nautilus” source package in Raring: Fix Released Bug description: [Impact] Nexus7 and some Dell touch screen devices do not work well with nautilus. This makes browsing files almost impossible in these devices. Further it's frustrating to the user because there is nothing that makes it immediately apparent that [Test Case] 1. Install Ubuntu 2. Double tap to open a folder in nautilus [Regression Potential] Low, this fix just affects touch screen devices. [Original Description] On the Nexus7 device double-tapping does not work in Nautilus. Even single taps are not always registered. In thunar navigating via double tap works fine. The mouse settings panel's double tap timeout test works fine. To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/1071922/+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 1025508] Re: Some keys in keyboard layout show duplicate character labels
Looks right, setting to verification-done. ** Tags removed: verification-needed ** Tags added: verification-done -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libgnomekbd in Ubuntu. https://bugs.launchpad.net/bugs/1025508 Title: Some keys in keyboard layout show duplicate character labels Status in GNOME Control Center: New Status in libgnomekbd: New Status in OEM Priority Project: In Progress Status in OEM Priority Project precise series: In Progress Status in OEM Priority Project raring series: In Progress Status in “gnome-control-center” package in Ubuntu: Invalid Status in “libgnomekbd” package in Ubuntu: Fix Released Status in “gnome-control-center” source package in Precise: New Status in “libgnomekbd” source package in Precise: Fix Committed Bug description: * Impact: The keyboard layout chart shows duplicate characters. Issue seems to have started on Ubuntu 12.04 and is present in 12.10. * Steps to reproduce: 1) Select keyboard icon from the launcher at top right of screen 2) Select Show Layout Chart menu item Keyboard layout is displayed the Function keys such as F1 show duplicate characters (i.e. F1 F1) The Numeric pad show duplicate chars for division /, multiplication *, subtraction -, and addition + Expected result: Should show only one instance of the character. * Regression potential: watch that no symbols are missing on the keyboard map drawing To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/1025508/+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 1025508] Re: Some keys in keyboard layout show duplicate character labels
** Changed in: oem-priority/raring Status: In Progress = Fix Released ** Changed in: oem-priority/precise Status: In Progress = Fix Committed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libgnomekbd in Ubuntu. https://bugs.launchpad.net/bugs/1025508 Title: Some keys in keyboard layout show duplicate character labels Status in GNOME Control Center: New Status in libgnomekbd: New Status in OEM Priority Project: Fix Released Status in OEM Priority Project precise series: Fix Committed Status in OEM Priority Project raring series: Fix Released Status in “gnome-control-center” package in Ubuntu: Invalid Status in “libgnomekbd” package in Ubuntu: Fix Released Status in “gnome-control-center” source package in Precise: New Status in “libgnomekbd” source package in Precise: Fix Committed Bug description: * Impact: The keyboard layout chart shows duplicate characters. Issue seems to have started on Ubuntu 12.04 and is present in 12.10. * Steps to reproduce: 1) Select keyboard icon from the launcher at top right of screen 2) Select Show Layout Chart menu item Keyboard layout is displayed the Function keys such as F1 show duplicate characters (i.e. F1 F1) The Numeric pad show duplicate chars for division /, multiplication *, subtraction -, and addition + Expected result: Should show only one instance of the character. * Regression potential: watch that no symbols are missing on the keyboard map drawing To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/1025508/+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)
** Also affects: oem-priority Importance: Undecided Status: New ** Changed in: oem-priority Assignee: (unassigned) = James M. Leddy (jm-leddy) ** Changed in: oem-priority Importance: Undecided = Medium ** Changed in: oem-priority Status: New = Triaged ** Also affects: oem-priority/precise Importance: Undecided Status: New ** Also affects: oem-priority/raring Importance: Medium Assignee: James M. Leddy (jm-leddy) Status: Triaged ** Changed in: oem-priority/precise Status: New = Won't Fix -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-input-evdev 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: Won't Fix Status in OEM Priority Project raring series: Triaged Status in “gnome-settings-daemon” package in Ubuntu: Triaged Status in “udev” package in Ubuntu: Triaged Status in “xserver-xorg-input-evdev” package in Ubuntu: Triaged Status in “gnome-settings-daemon” source package in Raring: Triaged Status in “udev” source package in Raring: Triaged Status in “xserver-xorg-input-evdev” source package in Raring: Triaged Bug description: Ubuntu 9.04 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 1117730] Re: nm-applet becomes unresponsive to interactions and submenus such as 'VPN Connections' show completely empty
** Changed in: oem-priority/quantal
Importance: Undecided = Medium
** Changed in: oem-priority/precise
Importance: Undecided = Medium
** Changed in: oem-priority/raring
Importance: Undecided = Medium
** Changed in: oem-priority/raring
Assignee: (unassigned) = James M. Leddy (jm-leddy)
** Changed in: oem-priority/precise
Assignee: (unassigned) = James M. Leddy (jm-leddy)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager-applet in Ubuntu.
https://bugs.launchpad.net/bugs/1117730
Title:
nm-applet becomes unresponsive to interactions and submenus such as
'VPN Connections' show completely empty
Status in DBus Menu:
New
Status in OEM Priority Project:
Triaged
Status in OEM Priority Project precise series:
Triaged
Status in OEM Priority Project quantal series:
Triaged
Status in OEM Priority Project raring series:
Triaged
Status in “libdbusmenu” package in Ubuntu:
Triaged
Status in “network-manager-applet” package in Ubuntu:
Confirmed
Bug description:
broken out of bug 780602, because we believe the root cause to be
different. From that bug report:
I experience exactly the same symptoms as the bug report description
has.
After some time nm-applet stops reacting to user input and submenu
entries do not populate. This is with latest 12.10 packages.
I noticed that the indicator tries to get the menu but it fails -
dbus-monitor output below:
method call sender=:1.12 - dest=:1.67 serial=14296
path=/com/canonical/Unity/Panel/Service;
interface=com.canonical.Unity.Panel.Service; member=ShowEntry
string 0x26ef470
uint32 0
int32 1147
int32 24
uint32 1
uint32 1356027813
method return sender=:1.67 - dest=:1.12 reply_serial=14296
method call sender=:1.67 - dest=:1.14 serial=107621
path=/org/ayatana/NotificationItem/nm_applet/Menu;
interface=com.canonical.dbusmenu; member=AboutToShowGroup
array [
int32 80799
]
error sender=:1.14 - dest=:1.67
error_name=org.gtk.GDBus.UnmappedGError.Quark._LIBDBUSMENU_2dGLIB.Code0
reply_serial=107621
string The IDs supplied '[80799]' do not refer to any menu items we have
When some item is clicked (e.g. disconnect for current wifi AP) the following
happens:
signal sender=:1.67 - dest=(null destination) serial=107704
path=/com/canonical/Unity/Panel/Service;
interface=com.canonical.Unity.Panel.Service; member=EntryActivated
string
struct {
int32 0
int32 0
uint32 0
uint32 0
}
method call sender=:1.67 - dest=:1.14 serial=107705
path=/org/ayatana/NotificationItem/nm_applet/Menu;
interface=com.canonical.dbusmenu; member=EventGroup
array [
struct {
int32 80846
string clicked
variant int32 0
uint32 106251172
}
]
error sender=:1.14 - dest=:1.67
error_name=org.gtk.GDBus.UnmappedGError.Quark._LIBDBUSMENU_2dGLIB.Code0
reply_serial=107705
string The IDs supplied '[80846]' do not refer to any menu items we have
So this looks like like dbus menu is losing the IDs or nm-applet is
using the ids that are no longer valid.
To manage notifications about this bug go to:
https://bugs.launchpad.net/libdbusmenu/+bug/1117730/+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 771150] Re: [Feature] support the external headphone/microphone jack sensing
Info from Tim Chen I have tested the mic/headphone jack on Asus x401u. When I plug a headphone, the interface, Microphone and Headphones are shown, and headphone works. When I plug a microphone,the interface, Microphone and Headphones are shown, but the active microphone is the built-in one. If I plug a 4 ring jack into the hole, the interface, Microphone and Headphones are shown, but only headphone is active, the active microphone is still the built-in one. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/771150 Title: [Feature] support the external headphone/microphone jack sensing Status in OEM Priority Project: Incomplete Status in OEM Priority Project precise series: Incomplete Status in OEM Priority Project quantal series: Incomplete Status in PulseAudio sound server: New Status in “alsa-driver” package in Ubuntu: Fix Released Bug description: The eeepc has a combined hole shared by the external microphone and headphone. Currently the default behaviour in Ubuntu is for headphone. (The music comes from headphone and the internal speaker is muted when plugging the headphone). This bug is intended for discussing and tracking the possibility and practicability of the support both headphone/microphone jack sensing in Linux driver or it is only achievable to support either one. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/771150/+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 771150] Re: [Feature] support the external headphone/microphone jack sensing
** Changed in: oem-priority Status: Incomplete = In Progress -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/771150 Title: [Feature] support the external headphone/microphone jack sensing Status in OEM Priority Project: In Progress Status in OEM Priority Project precise series: Incomplete Status in OEM Priority Project quantal series: Incomplete Status in PulseAudio sound server: New Status in “alsa-driver” package in Ubuntu: Fix Released Bug description: The eeepc has a combined hole shared by the external microphone and headphone. Currently the default behaviour in Ubuntu is for headphone. (The music comes from headphone and the internal speaker is muted when plugging the headphone). This bug is intended for discussing and tracking the possibility and practicability of the support both headphone/microphone jack sensing in Linux driver or it is only achievable to support either one. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/771150/+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 1041032] Re: An error occurred Location not found after automatically installing the missing gstreamer plugins.
Straight applying the patch from the upstream version didn't work: bacon-video-widget-gst-0.10.c: In function 'bacon_video_widget_get_property': bacon-video-widget-gst-0.10.c:2994:43: error: 'BaconVideoWidgetPrivate' has no member named 'subtitle_uri' make[4]: *** [libbaconvideowidget_la-bacon-video-widget-gst-0.10.lo] Error 1 make[4]: Leaving directory `/home/james/src/totem-3.0.1/src/backend' make[3]: *** [all-recursive] Error 1 make[3]: Leaving directory `/home/james/src/totem-3.0.1/src' make[2]: *** [all-recursive] Error 1 make[2]: Leaving directory `/home/james/src/totem-3.0.1' make[1]: *** [all] Error 2 make[1]: Leaving directory `/home/james/src/totem-3.0.1' make: *** [debian/stamp-makefile-build] Error 2 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to totem in Ubuntu. https://bugs.launchpad.net/bugs/1041032 Title: An error occurred Location not found after automatically installing the missing gstreamer plugins. Status in OEM Priority Project: Incomplete Status in OEM Priority Project precise series: Incomplete Status in Totem Movie Player: New Status in “totem” package in Ubuntu: In Progress Status in “totem” source package in Quantal: In Progress Bug description: Ubuntu: 12.04 totem: 3.0.1-0ubuntu21 There is a feature of totem that it can detect the missing gstreamer plugins and install them automatically. It will pop out this message after it finished the installation of gstreamer plugins. However totem will work normally after we reopen it. Reproduce steps: 1. Remove gstreamer0.10-ffmpeg and gstreamer0.10-plugins-ugly if they are installed. 2. Download Wildlife.wmv from http://archive.org/details/Windows7WildlifeSampleVideo 3. Open Wildlife.wmv by totem. Relative to Bug #1041287. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1041032/+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 1071922] Re: double tap does not open folders or files in Nautilus
Hi debb1046, is there any chance you would be able to test on precise- proposed? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1071922 Title: double tap does not open folders or files in Nautilus Status in Nautilus: Fix Released Status in OEM Priority Project: Fix Committed Status in OEM Priority Project precise series: Fix Committed Status in OEM Priority Project quantal series: Fix Released Status in Ubuntu on the Nexus 7: Invalid Status in “nautilus” package in Ubuntu: Fix Released Status in “nautilus” source package in Precise: Fix Committed Status in “nautilus” source package in Quantal: Won't Fix Status in “nautilus” source package in Raring: Fix Released Bug description: [Impact] Nexus7 and some Dell touch screen devices do not work well with nautilus. This makes browsing files almost impossible in these devices. Further it's frustrating to the user because there is nothing that makes it immediately apparent that [Test Case] 1. Install Ubuntu 2. Double tap to open a folder in nautilus [Regression Potential] Low, this fix just affects touch screen devices. [Original Description] On the Nexus7 device double-tapping does not work in Nautilus. Even single taps are not always registered. In thunar navigating via double tap works fine. The mouse settings panel's double tap timeout test works fine. To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/1071922/+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
