[Desktop-packages] [Bug 1765363] Re: prime-select intel is not powering off the nvidia card
On-demand mode does not have this issue. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-prime in Ubuntu. https://bugs.launchpad.net/bugs/1765363 Title: prime-select intel is not powering off the nvidia card Status in nvidia-prime package in Ubuntu: Confirmed Bug description: Right now, it seems that prime-select intel makes sure the nvidia driver is not loaded, as nvidia-settings reports. But my power consumption is > 20W. cat /proc/acpi/bbswitch reports the card is still on. If bbswitch and powertop are reliable, then the nvidia card is still powered. This is a thinkpad w520 in Optimus mode. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: nvidia-prime 0.8.7 ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15 Uname: Linux 4.15.0-15-generic x86_64 ApportVersion: 2.20.9-0ubuntu5 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Apr 19 19:56:21 2018 Dependencies: EcryptfsInUse: Yes InstallationDate: Installed on 2017-12-14 (125 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) PackageArchitecture: all SourcePackage: nvidia-prime UpgradeStatus: Upgraded to bionic on 2018-03-09 (41 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-prime/+bug/1765363/+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 1893719] [NEW] Request for adding support for Synaptics fingerprint reader sensors: 0xE9 and 0xDF
Public bug reported: [Impact] * We were advised by Synaptics to upgrade the existing libfprint in the archive to include sensor support for 0xE9 and 0xDF as highlighted in the following commits: https://gitlab.freedesktop.org/libfprint/libfprint/-/commit/8b64312f4bfee84c8be1eb9763f7fe87ec078a1a [Test Case] * We have several OEM platforms with these Synaptics sensors enabled with Focal and they can be used to validate these changes. [Regression Potential] * Regression potential for an updated libfprint with these new PIDs is low [Other Info] None ** Affects: oem-priority Importance: Low Status: New ** Affects: libfprint (Ubuntu) Importance: Undecided Status: New ** Tags: oem-priority ** Changed in: oem-priority Importance: Undecided => Low ** Also affects: oem-priority/focal Importance: Undecided Status: New ** No longer affects: oem-priority/focal ** Tags added: oem-priority ** Information type changed from Proprietary to Public ** Also affects: libfprint (Ubuntu) Importance: Undecided Status: New ** Description changed: [Impact] - * We were advised by Synaptics to upgrade the existing libfprint in the - archive to include sensor support for 0xE9 and 0xDF: + * We were advised by Synaptics to upgrade the existing libfprint in the + archive to include sensor support for 0xE9 and 0xDF as highlighted in + the following commits: + https://gitlab.freedesktop.org/libfprint/libfprint/-/commit/8b64312f4bfee84c8be1eb9763f7fe87ec078a1a [Test Case] - * We have several OEM platforms with these Synaptics sensors enabled + * We have several OEM platforms with these Synaptics sensors enabled with Focal and they can be used to validate these changes. [Regression Potential] - * Regression potential for an updated libfprint with these new PIDs is + * Regression potential for an updated libfprint with these new PIDs is low [Other Info] - - None + + None ** Summary changed: - Add support for Synaptics fingerprint reader sensors: 0xE9 and 0xDF + Request for adding support for Synaptics fingerprint reader sensors: 0xE9 and 0xDF -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libfprint in Ubuntu. https://bugs.launchpad.net/bugs/1893719 Title: Request for adding support for Synaptics fingerprint reader sensors: 0xE9 and 0xDF Status in OEM Priority Project: New Status in libfprint package in Ubuntu: New Bug description: [Impact] * We were advised by Synaptics to upgrade the existing libfprint in the archive to include sensor support for 0xE9 and 0xDF as highlighted in the following commits: https://gitlab.freedesktop.org/libfprint/libfprint/-/commit/8b64312f4bfee84c8be1eb9763f7fe87ec078a1a [Test Case] * We have several OEM platforms with these Synaptics sensors enabled with Focal and they can be used to validate these changes. [Regression Potential] * Regression potential for an updated libfprint with these new PIDs is low [Other Info] None To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1893719/+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 1881094] Re: Support kernel 5.4 Intel sound driver on bionic
Can we get SRU process for this fix in pulseaudio started as soon as possible? There is one OEM platform which is urgently waiting for it. Thank you. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1881094 Title: Support kernel 5.4 Intel sound driver on bionic Status in OEM Priority Project: New Status in pulseaudio package in Ubuntu: Invalid Status in pulseaudio source package in Bionic: Triaged Bug description: [Impact] * Some Intel platform bionic user audio function will be broken after upgrade to kernel 5.4 * pulseaudio can't find working profile, since card name is changed in kernel 5.4 [Test Case] * install kernel 5.4 and check audio function 1. enable Pre-released updates in Developer Options Software & Updates > Developer Options > Pre-released updates (bionic-proposed) 2. $ sudo apt update 3. $ sudo apt install linux-generic-hwe-18.04-wip 4. $ sudo reboot * install updated linux-firmware and pulseaudio $ sudo add-apt-repository ppa:kchsieh/training $ sudo apt-get update $ sudo apt install linux-firmware $ sudo apt install pulseaudio $ sudo reboot * test items 1. check internal speaker/mic to playback and record audio 2. plug headset and check headset functions 3. plug HDMI from external monitor/TV, and check audio functions 4. 1, 2, 3 works fine after resume from suspend [Regression Potential] * The updated pulseaudio breaks audio function on old kernel [Scope] * Need for bionic only [Bug Discussion] * https://bugs.launchpad.net/timbuktu/+bug/1880632 * MP: https://code.launchpad.net/~kchsieh/pulseaudio/+git/bionic-1880632/+merge/384610 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1881094/+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 1869819] Re: [SRU] System can't detect external headset in the codec of Conexant
@Daniel, when can we expect the this fix in pulseaudio will show up in -updates channel for Bionic? Thanks. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1869819 Title: [SRU] System can't detect external headset in the codec of Conexant Status in OEM Priority Project: Confirmed Status in OEM Priority Project bionic series: New Status in pulseaudio package in Ubuntu: Fix Released Status in pulseaudio source package in Bionic: In Progress Status in pulseaudio source package in Focal: Fix Released Bug description: [Impact] In some hp's devices, there are two audio jacks(one headset and one headphone) in the audio interface which is using the codec of Conexant, and apparently it's not working, the system can't detect the headset in current codec. [Test Case] 1. Insert 4 rings(3 stripes) headset into front audio port (headset icon) 2. Check System Setting->Sound->Output [Expected result] Can detect external headset [Actual result] Only shows internal speaker. External headset microphone was detected. Another front audio port (earphone icon) works fine. [Regression Potential] Low. [Failure rate] 100% [Additional information] system-product-name: HP EliteDesk 800 G5 SFF CPU: Intel(R) Core(TM) i7-9700 CPU @ 3.00GHz (8x) GPU: 00:02.0 VGA compatible controller [0300]: Intel Corporation Device [8086:3e98] (rev 02) OS-version: 18.04 kernel-version: 4.15.0-1065-oem pulseaudio-version: 1:11.1-1ubuntu7.2 Upstream issue: https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/merge_requests/272 Ubuntu-Focal-Source: https://code.launchpad.net/~hugh712/ubuntu/+source/pulseaudio/+git/pulseaudio/+ref/focal-1869819 PPA: https://launchpad.net/~hugh712/+archive/ubuntu/sru-1869819 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1869819/+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 1869819] Re: [SRU] System can't detect external headset in the codec of Conexant
@Jamie, just want to highlight that there is an urgent fix in Bionic to an OEM platform which is waiting for this update to be done before we can land it. It'd be very much appreciated if we can somehow speed up the process. Thank you. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1869819 Title: [SRU] System can't detect external headset in the codec of Conexant Status in OEM Priority Project: Confirmed Status in OEM Priority Project bionic series: New Status in pulseaudio package in Ubuntu: Fix Released Status in pulseaudio source package in Bionic: In Progress Status in pulseaudio source package in Focal: Fix Released Bug description: [Impact] In some hp's devices, there are two audio jacks(one headset and one headphone) in the audio interface which is using the codec of Conexant, and apparently it's not working, the system can't detect the headset in current codec. [Test Case] 1. Insert 4 rings(3 stripes) headset into front audio port (headset icon) 2. Check System Setting->Sound->Output [Expected result] Can detect external headset [Actual result] Only shows internal speaker. External headset microphone was detected. Another front audio port (earphone icon) works fine. [Regression Potential] Low. [Failure rate] 100% [Additional information] system-product-name: HP EliteDesk 800 G5 SFF CPU: Intel(R) Core(TM) i7-9700 CPU @ 3.00GHz (8x) GPU: 00:02.0 VGA compatible controller [0300]: Intel Corporation Device [8086:3e98] (rev 02) OS-version: 18.04 kernel-version: 4.15.0-1065-oem pulseaudio-version: 1:11.1-1ubuntu7.2 Upstream issue: https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/merge_requests/272 Ubuntu-Focal-Source: https://code.launchpad.net/~hugh712/ubuntu/+source/pulseaudio/+git/pulseaudio/+ref/focal-1869819 PPA: https://launchpad.net/~hugh712/+archive/ubuntu/sru-1869819 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1869819/+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 1820323] Re: amdgpu-pro xorg crash
** Attachment added: "make.log while trying to build amdgpu in 4.4.0-143" https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1820323/+attachment/5321036/+files/make.log -- 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/1820323 Title: amdgpu-pro xorg crash Status in xorg-server package in Ubuntu: Invalid Bug description: This is on Precision 3620, Precision 5820, Precision 7820 - systems with AMD bundled for OEM fail to properly boot after update/upgrade. I believe this is related to this issue: https://www.amd.com/en/support/kb/faq/amdgpupro-ubuntu-advisory Since our image contains the amdgpu-pro package we are impacted. Canonical image is not impacted. Various systems (Precision 3420, 3620, 5820, and 7820) are having login issues with AMD GPUs after running system updates on the OEM Ubuntu image. After running sudo apt-get update && apt-get upgrade, the system will exhibit one of a few different behaviors: • Boots to a black screen • Loops at login • Boots to a screen indicating the system has been forced to low graphics mode and hard locks. I have a systems in the lab that exhibits this issue and I don’t know how to get around it. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3.1 ProcVersionSignature: Ubuntu 4.4.0-143.169-generic 4.4.170 Uname: Linux 4.4.0-143-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 BootLog: Scanning for Btrfs filesystems UBUNTU: clean, 267691/28237824 files, 3796147/112924672 blocks CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' Date: Fri Mar 15 13:22:36 2019 DistUpgraded: Fresh install DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-xenial-amd64-20160624-2 DistroCodename: xenial DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Subsystem: Dell Device [1028:06c7] Advanced Micro Devices, Inc. [AMD/ATI] Lexa XT [Radeon PRO WX 2100] [1002:6995] (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:0b0c] InstallationDate: Installed on 2019-03-14 (0 days ago) InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 20160624-10:47 MachineType: Dell Inc. Precision Tower 3420 ProcEnviron: TERM=linux PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-143-generic root=UUID=ced18cfc-68aa-461d-a69d-d482f5880d16 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg crash UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/07/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.11.2 dmi.board.name: 02K9CR dmi.board.vendor: Dell Inc. dmi.board.version: A02 dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.11.2:bd11/07/2018:svnDellInc.:pnPrecisionTower3420:pvr:rvnDellInc.:rn02K9CR:rvrA02:cvnDellInc.:ct3:cvr: dmi.product.name: Precision Tower 3420 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.91-2~16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~16.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.8 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1.2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 xserver.bootTime: Fri Mar 15 13:21:28 2019 xserver.configfile: default xserver.devices: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.18.4-0ubuntu0.8 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1820323/+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 1820323] Re: amdgpu-pro xorg crash
- Original shipping condition: * Dell Farallon + WX2100 * linux-image-4.4.0-36-generic + amdgpu-17.10-429170 - Test procedure: 1. sudo apt install linux-image-4.4.0-xxx-generic linux-headers-4.4.0-xxx-generic 2. reboot Expected behavior System can boot into desktop successfully to the updated kernel Actual behavior Loop at login session - Findings: 1. amdgpu DKMS fails to build exactly between 4.4.0-142(OK) and 4.4.0-143(NG) kernels 2. However, starting from 4.4.0-116 kernel, amdgpu module fails to load with the following error message: amdkcl: version magic '4.4.0-xxx-generic SMP mod_unload modversions' should be '4.4.0-xxx-generic SMP mod_unload modversions retpoline' - In summary, the issue has 2 causes, amdgpu loading error and amdgpu DKMS build error, the former happens in earlier kernel revisions than the latter. -- 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/1820323 Title: amdgpu-pro xorg crash Status in xorg-server package in Ubuntu: Invalid Bug description: This is on Precision 3620, Precision 5820, Precision 7820 - systems with AMD bundled for OEM fail to properly boot after update/upgrade. I believe this is related to this issue: https://www.amd.com/en/support/kb/faq/amdgpupro-ubuntu-advisory Since our image contains the amdgpu-pro package we are impacted. Canonical image is not impacted. Various systems (Precision 3420, 3620, 5820, and 7820) are having login issues with AMD GPUs after running system updates on the OEM Ubuntu image. After running sudo apt-get update && apt-get upgrade, the system will exhibit one of a few different behaviors: • Boots to a black screen • Loops at login • Boots to a screen indicating the system has been forced to low graphics mode and hard locks. I have a systems in the lab that exhibits this issue and I don’t know how to get around it. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3.1 ProcVersionSignature: Ubuntu 4.4.0-143.169-generic 4.4.170 Uname: Linux 4.4.0-143-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 BootLog: Scanning for Btrfs filesystems UBUNTU: clean, 267691/28237824 files, 3796147/112924672 blocks CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' Date: Fri Mar 15 13:22:36 2019 DistUpgraded: Fresh install DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-xenial-amd64-20160624-2 DistroCodename: xenial DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Subsystem: Dell Device [1028:06c7] Advanced Micro Devices, Inc. [AMD/ATI] Lexa XT [Radeon PRO WX 2100] [1002:6995] (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:0b0c] InstallationDate: Installed on 2019-03-14 (0 days ago) InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 20160624-10:47 MachineType: Dell Inc. Precision Tower 3420 ProcEnviron: TERM=linux PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-143-generic root=UUID=ced18cfc-68aa-461d-a69d-d482f5880d16 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg crash UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/07/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.11.2 dmi.board.name: 02K9CR dmi.board.vendor: Dell Inc. dmi.board.version: A02 dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.11.2:bd11/07/2018:svnDellInc.:pnPrecisionTower3420:pvr:rvnDellInc.:rn02K9CR:rvrA02:cvnDellInc.:ct3:cvr: dmi.product.name: Precision Tower 3420 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.91-2~16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~16.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.8 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1.2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 xserver.bootTime: Fri Mar 15 13:21:28 2019 xserver.configfile: default xserver.devices: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.18.4-0ubuntu0.8 To manage notifications about this bug go to:
[Desktop-packages] [Bug 1839016] Re: Suspend process is interrupted by ALT key
** Summary changed: - Suspend is iterrupted by ALT key + Suspend process is interrupted by ALT key -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1839016 Title: Suspend process is interrupted by ALT key Status in OEM Priority Project: New Status in OEM Priority Project bionic series: New Status in gnome-shell package in Ubuntu: Fix Released Bug description: When trying to suspend the system via pressing the power button in the system tray with ALT key pressed, it is possible to interrupt the system to enter sleep mode and fall back to screen lock. While trying to unlock the screen, the system goes to sleep immediately. Gnome-shell is able to suspend the system by drop-down menu in the system tray. By pressing ALT key or long-press the power button until it switches to suspend icon. The system will suspend if it is by the long-press power button, while with ALT key pressed, there is a failure rate that causes the suspend process to be interrupted. The second issue is that if the suspend process is interrupted, the locked screen is shown. While trying to unlock the screen by inputting password, the system will go sleeping after that. STEPS TO REPRODUCE: 1. To suspend system via pressing the power button in the drop-down system tray with ALT key pressed. 2. During system is going to sleep, e.g., screen going dark, emulate a key bounce by pressing ALT key again. RESULTS: The locked screen shows up and goes to sleep after tens of seconds. While trying to unlock screen, system enter suspend after unlocking successfully. EXPECTED RESULTS: The system going to sleep without a problem. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.28.4-0ubuntu18.04.1 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1839016/+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 1821863] Re: Need to add Intel CML related pci-id's
@Timo, tried to upgrade to xorg-server into bionic-proposed and confirmed it fixes a laggy desktop issue found in some OEM CML platforms running on bionic image. ** Tags removed: verification-needed-bionic ** Tags added: verification-done-bionic -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1821863 Title: Need to add Intel CML related pci-id's Status in libdrm package in Ubuntu: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux-oem package in Ubuntu: Fix Released Status in mesa package in Ubuntu: Fix Released Status in xorg-server package in Ubuntu: Fix Released Status in libdrm source package in Bionic: New Status in linux source package in Bionic: Invalid Status in linux-oem source package in Bionic: Fix Released Status in mesa source package in Bionic: Fix Committed Status in xorg-server source package in Bionic: Fix Committed Status in libdrm source package in Disco: Fix Released Status in linux source package in Disco: Fix Released Status in linux-oem source package in Disco: Fix Released Status in mesa source package in Disco: Fix Released Status in xorg-server source package in Disco: Fix Released Bug description: [Impact] Please make it happen in the coming oem-kernel as there will be a flood of Intel Comet Lake (CML) platforms that would need it. Thank you. The same is needed for the rest of the stack. CML is basically another iteration of Skylake/Kabylake/Coffee Lake, and doesn't need other changes than pci-id's and support for the PCH (similar to Cannon point, already supported by the kernel). [Test case] Test that i915 graphics works on CML. [Regression potential] None really, these only add a bunch of new pci-id's across the stack. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libdrm/+bug/1821863/+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 1770271] Re: VegaM support
@Timo,agreed. And we are not seeing any business need to support VegaM in Xenial in near future (if ever.) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1770271 Title: VegaM support Status in amd: New Status in linux package in Ubuntu: Fix Released Status in mesa package in Ubuntu: Fix Released Status in linux source package in Xenial: Won't Fix Status in mesa source package in Xenial: Won't Fix Status in linux source package in Bionic: New Status in mesa source package in Bionic: Fix Committed Bug description: VegaM is a new GPU. Please include support for VegaM in the next LTS (16.04.x and 18.04.x) and non-LTS releases. Kernel support starts here (32 patches): https://patchwork.freedesktop.org/patch/218839/ Mesa support: https://cgit.freedesktop.org/mesa/mesa/commit/?id=d6a66bc8dbcdeed8e87f649bc281de0d60d2f123 https://cgit.freedesktop.org/mesa/mesa/commit/?id=c6f1d360198c52d208645c0ccb5e988cded408e8 https://cgit.freedesktop.org/mesa/mesa/commit/?id=90de03708fa269ad54de881b467f4811e4eef87e To manage notifications about this bug go to: https://bugs.launchpad.net/amd/+bug/1770271/+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 1812357] Re: Mobile Broadband panel still shows "Connected" after removing the SIM card
Thanks for the pointer. A bug was just reported to https://gitlab.gnome.org/GNOME/gnome-control-center/issues as https://gitlab.gnome.org/GNOME/gnome-control-center/issues/351 -- 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/1812357 Title: Mobile Broadband panel still shows "Connected" after removing the SIM card Status in gnome-control-center package in Ubuntu: New Bug description: [Reproduce Steps] 1. Boot to Ubuntu 18.04 desktop and insert a SIM card and make sure can mobile connection could work successfully. 2. Removing the SIM card from the slot. [Result] Expected Result: Mobile Broadband panel should reflect the interruption in network connection and toggle off the "Connected" status Actual Result: Mobile Broadband UI still shows "Connected" even without active network connection To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1812357/+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 1812357] Re: Mobile Broadband panel still shows "Connected" after removing the SIM card
** Attachment added: "Screenshot of an incorrect mobile network status" https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1812357/+attachment/5230203/+files/Ubuntu_WWAN%20Connected.jpg -- 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/1812357 Title: Mobile Broadband panel still shows "Connected" after removing the SIM card Status in gnome-control-center package in Ubuntu: New Bug description: [Reproduce Steps] 1. Boot to Ubuntu 18.04 desktop and insert a SIM card and make sure can mobile connection could work successfully. 2. Removing the SIM card from the slot. [Result] Expected Result: Mobile Broadband panel should reflect the interruption in network connection and toggle off the "Connected" status Actual Result: Mobile Broadband UI still shows "Connected" even without active network connection To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1812357/+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 1812357] [NEW] Mobile Broadband panel still shows "Connected" after removing the SIM card
Public bug reported: [Reproduce Steps] 1. Boot to Ubuntu 18.04 desktop and insert a SIM card and make sure can mobile connection could work successfully. 2. Removing the SIM card from the slot. [Result] Expected Result: Mobile Broadband panel should reflect the interruption in network connection and toggle off the "Connected" status Actual Result: Mobile Broadband UI still shows "Connected" even without active network connection ** Affects: gnome-control-center (Ubuntu) Importance: Undecided Status: New -- 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/1812357 Title: Mobile Broadband panel still shows "Connected" after removing the SIM card Status in gnome-control-center package in Ubuntu: New Bug description: [Reproduce Steps] 1. Boot to Ubuntu 18.04 desktop and insert a SIM card and make sure can mobile connection could work successfully. 2. Removing the SIM card from the slot. [Result] Expected Result: Mobile Broadband panel should reflect the interruption in network connection and toggle off the "Connected" status Actual Result: Mobile Broadband UI still shows "Connected" even without active network connection To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1812357/+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 1789913] Re: X crashes with "randr: falling back to unsynchronized pixmap sharing" when connecting to an external monitor via HDMI (I+A)
Yes, I have tested the package with Bionic on the same Dell Precision 7730 unit and found it works well, too. -- 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/1789913 Title: X crashes with "randr: falling back to unsynchronized pixmap sharing" when connecting to an external monitor via HDMI (I+A) Status in xorg-server package in Ubuntu: Fix Released Status in xorg-server-hwe-16.04 package in Ubuntu: Invalid Status in xorg-server source package in Xenial: Won't Fix Status in xorg-server-hwe-16.04 source package in Xenial: Fix Committed Status in xorg-server source package in Bionic: Fix Committed Status in xorg-server-hwe-16.04 source package in Bionic: Invalid Bug description: [Impact] X server crashes in certain cases on I+A hybrid machines with modesetting+amdgpu drivers. [Test case] Connect an external monitor, check that it doesn't crash X. [Regression potential] This commit was provided by AMD and reviewed by an NVIDIA engineer, and after a few iterations it got applied upstream. We'll test it with many driver combinations (modesetting+amdgpu, m+nvidia, m+m...) to check that they all (still) work. -- Copied from a private bug: - Steps to see the issue: 1. Connect a monitor to UUT via HDMI port Expected Result: Video outputs successfully in the monitor Actual Result: X crashes into a login screen - BIOS: 0.7.3 - AMD driver release: 18.10, 18.20RC8 and 18.20RC9 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1789913/+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 1735134] Re: ModemManager uses a wrong plugin for Dell DW5818/5819
** Also affects: modemmanager Importance: Undecided Status: New ** No longer affects: modemmanager -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to modemmanager in Ubuntu. https://bugs.launchpad.net/bugs/1735134 Title: ModemManager uses a wrong plugin for Dell DW5818/5819 Status in modemmanager package in Ubuntu: New Bug description: Since linux-4.4.0-98, the kernel additionally load gcserial driver for Dell Wireless DW5818/5819. The reason behind it is to support firmware switching and upgrading. However, the change makes ModemManager to use Gobi plugin for this two modules. With Gobi plugin, the modules could establish data links, but it failed to retrieve the signal state. And it caused the mmcli and nm-applet giving wrong signal strength. The modules support the MBIM protocol, so ModemManager should use Dell plugin for these two modules. I have worked out a patch to forbid these two modules in Gobi plugin, and it does work well. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/modemmanager/+bug/1735134/+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 1725190] Re: Please update modemmanager in xenial to the 1.6 series
@sil2100, this backport is to fix the following 2 OEM project issues: https://bugs.launchpad.net/bugs/1693756 -> to better support Sierra DW5815e WWAN module https://bugs.launchpad.net/ubuntu/+source/modemmanager/+bug/1735134 -> to fix incorrect signal strength readings (by modemmanager) for Sierra DW5818 and DW5819 WWAN modules -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to modemmanager in Ubuntu. https://bugs.launchpad.net/bugs/1725190 Title: Please update modemmanager in xenial to the 1.6 series Status in OEM Priority Project: Confirmed Status in modemmanager package in Ubuntu: In Progress Bug description: We would like to upgrade xenial to 1.6 series so it supports the same modems as the modem-manager snap, specifically some new Sierra modems (HL8548 and others from HL series, popular in IoT devices). These are the packages that would need to be updated: libmbim: 1.12.2-2ubuntu1 in xenial, 1.14.0 in snap libqmi: 1.12.6-1 in xenial, 1.16.2 in snap modemmanager: 1.4.12-1ubuntu1 in xenial, 1.6.2 in snap This is also related to bug #1693756 which includes a subset of patches of what would be updated. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1725190/+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 1693756] Re: [Xenial][ DW5816e] to support qmi over mbim which needed for FCC authentication.
** Also affects: modemmanager Importance: Undecided Status: New ** Also affects: oem-priority Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to modemmanager in Ubuntu. https://bugs.launchpad.net/bugs/1693756 Title: [Xenial][ DW5816e] to support qmi over mbim which needed for FCC authentication. Status in ModemManager: New Status in OEM Priority Project: New Status in modemmanager package in Ubuntu: New Bug description: # issue: * wwan card DW5816e[413c:81cc] couldn't be recognized by modemmanager 1.4.12-1ubuntu1 on xenial. - but works well on on Yakkety. # investgation: * in failed case, mmcli -L shows nothing on Xenial with DW5816. Then tried install followed packages from Yakkety ppa on Xenial and wwan card works on 1st boot but failed after 2nd boot sometimes. - libmbim-glib4_1.14.0-1_amd64.deb - libmbim-glib-dev_1.14.0-1_amd64.deb - libmbim-proxy_1.14.0-1_amd64.deb - libmbim-utils_1.14.0-1_amd64.deb - libqmi-glib5_1.16.0-1_amd64.deb - libqmi-proxy_1.16.0-1_amd64.deb * different from ModemManager --debug - In passed case, it received message from /dev/cdc-wdm1 after send "Read max control message size from descriptors file: 4096" , but not happens to failed case. So, it prints "[mm-port-probe.c:261] mm_port_probe_set_result_qcdm(): (tty/ttyS4) port is not QCDM-capable" in failed case. - passed case: http://paste.ubuntu.com/24664908/ - failed case: http://paste.ubuntu.com/24664910/ # Plan: * let the newer version packages could also works well on Xenial. * find out needed patches on newer version packages. * packport needed patches to older version packages on Xenial. # environment information: * modinfo cdc_mbim for original kernel module: http://paste.ubuntu.com/24662359/ - the code /driver/net/usb/cdc_mbim.c is the same between xenial kernel 4.4.0 and yakkety kernel 4.8.0. * uname -r: 4.4.0-73-generic * lsusb -v: http://paste.ubuntu.com/24662332/ FCC authentication reference: * http://lists.infradead.org/pipermail/lede-dev/2016-August/002332.html * https://lists.freedesktop.org/archives/libmbim-devel/2016-April/thread.html#704 To manage notifications about this bug go to: https://bugs.launchpad.net/modemmanager/+bug/1693756/+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 1649763] Re: Dell XPS 15 2016 with Ubuntu 16 Sound HDMI issues
** Also affects: unity-control-center Importance: Undecided Status: New ** No longer affects: unity-control-center ** Also affects: oem-priority Importance: Undecided Status: New ** Changed in: oem-priority Importance: Undecided => Critical -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1649763 Title: Dell XPS 15 2016 with Ubuntu 16 Sound HDMI issues Status in OEM Priority Project: New Status in unity-control-center package in Ubuntu: Confirmed Bug description: This issue is related to sound not working properly on Ubuntu when switching between an external display using HDMI with 4K resolution and the standard laptop display. Issue 1 - Sound only works on laptop when plugged into 4k HDMI display Issue 2 - Sound doesn't work when plugged removed from 4k HDMI display When you plug in a 4k Display that supports sound to the Dell XPS 15 2016 model the sound only works on the laptop. Only when you go to Sound Settings and manually select the HDMI output for sound does the sound start to work on the display itself instead of the laptop. When you unplug the HDMI 4k display the sound doesn't work on the laptop. When you go to the Sound Settings dialog it only shows one output that is selected - if you select the same output thats already selected the sound starts to work again on the laptop. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1649763/+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 1647283] Re: WiFi being detected as ethernet when race condition on renaming for persistent name
@Aron, may we know if the patch suggested in comment#2 already in the NM(1.2) to be used in Xenial? Thanks. -- 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/1647283 Title: WiFi being detected as ethernet when race condition on renaming for persistent name Status in HWE Next: New Status in NetworkManager: Fix Released Status in OEM Priority Project: New Status in OEM Priority Project xenial series: New Status in network-manager package in Ubuntu: Triaged Bug description: Forwarded https://bugzilla.gnome.org/show_bug.cgi?id=775613 Version: NetworkManager 1.4.2 This bug happens after power-on with probability about 1/50. That means we need to reboot about 50 times to get into the buggy situation. "nmcli d" shows the device type is ethernet: DEVICE TYPE STATECONNECTION wlp1s0 ethernet unavailable -- lo loopback unmanaged-- The bug starts from a race condition. But it is not the root cause. I've also attach 2 logs. One is in good situation. Another is in bad situation. This log is generated by applying a "log patch" to network-manager 1.4.2 so we can see more stuff. In the bad situation. The bug starts with race condition. But the race condition is not the root cause. The race condition is: * During the renaming from "wlan0" to "wlp1s0". "wlan0" disappeared. * Inside the NM, it is still using "wlan0" in "_linktype_get_type()". * Since /sys/class/net/wlan0/uevent is disappeared. so the type matching failed in _linktype_get_type(). * Also wifi_utils_is_wifi() failed to because /sys/class/net/wlan0 disappeared. * And finally, devtype and kind are both NULL, so it returns NM_LINK_TYPE_ETHERNET for wlan0. Later, wlan0 is renamed to wlp1s0, and it seems to me that the Object inherit the type so it is still type ethernet. But from the log, I saw _linktype_get_type() is called several times later and return the correct type (wifi). But just, "nmcli d" still shows type ethernet. I'm wondering if we are missing to update the type in the Object created after renaming and re-detecting the type. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1647283/+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 1647283] Re: WiFi being detected as ethernet when race condition on renaming for persistent name
** Also affects: oem-priority Importance: Undecided Status: New ** Changed in: oem-priority Importance: Undecided => Critical ** Also affects: oem-priority/xenial Importance: Undecided Status: New -- 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/1647283 Title: WiFi being detected as ethernet when race condition on renaming for persistent name Status in HWE Next: New Status in NetworkManager: Confirmed Status in OEM Priority Project: New Status in OEM Priority Project xenial series: New Status in network-manager package in Ubuntu: New Bug description: Forwarded https://bugzilla.gnome.org/show_bug.cgi?id=775613 Version: NetworkManager 1.4.2 This bug happens after power-on with probability about 1/50. That means we need to reboot about 50 times to get into the buggy situation. "nmcli d" shows the device type is ethernet: DEVICE TYPE STATECONNECTION wlp1s0 ethernet unavailable -- lo loopback unmanaged-- The bug starts from a race condition. But it is not the root cause. I've also attach 2 logs. One is in good situation. Another is in bad situation. This log is generated by applying a "log patch" to network-manager 1.4.2 so we can see more stuff. In the bad situation. The bug starts with race condition. But the race condition is not the root cause. The race condition is: * During the renaming from "wlan0" to "wlp1s0". "wlan0" disappeared. * Inside the NM, it is still using "wlan0" in "_linktype_get_type()". * Since /sys/class/net/wlan0/uevent is disappeared. so the type matching failed in _linktype_get_type(). * Also wifi_utils_is_wifi() failed to because /sys/class/net/wlan0 disappeared. * And finally, devtype and kind are both NULL, so it returns NM_LINK_TYPE_ETHERNET for wlan0. Later, wlan0 is renamed to wlp1s0, and it seems to me that the Object inherit the type so it is still type ethernet. But from the log, I saw _linktype_get_type() is called several times later and return the correct type (wifi). But just, "nmcli d" still shows type ethernet. I'm wondering if we are missing to update the type in the Object created after renaming and re-detecting the type. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1647283/+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 1578127] Re: Sometimes WLAN detects no SSID after s3
On the Dell platform where this bug was originally reported on, with the latest network manager package, the issue was no longer seen. -- 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/1578127 Title: Sometimes WLAN detects no SSID after s3 Status in NetworkManager: New Status in OEM Priority Project: Incomplete Status in network-manager package in Ubuntu: Incomplete Bug description: [Steps to reproduce] 1. Boot into OS 2. Do s3 a few times 3. Check if wifi is still working after s3 [Expected results] wifi still working correctly after s3 [Actual results] 1. Wifi shows "disconnected" in network-manager (both in applet and from command "nmcli d status") 2. Only one random SSID is displayed in network-manager applet, but wifi connection cannot be established at all with this SSID. Clicking on the SSID results in pop up window in the comment #2 below 3. "nmcli d wifi rescan" does not resolve issue 4. "iwlist [interface] scan" returns nothing and does not reolve issue 5. "nmcli d wifi connect [any SSID that you know should exist]" results in SSID not found and does not resolve issue 6. "sudo service network-manager restart", warm boot, cold boot resolves issue [Details] OS: Xenial based OEM image WLAN module: Marvel [11ab:2b38] network-manager: - 1.2.0-0ubuntu0.16.04.1 (fail rate 1/20~ 1/15) - 1.1.93 (fail rate 1/15) To manage notifications about this bug go to: https://bugs.launchpad.net/network-manager/+bug/1578127/+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 1578127] Re: Sometimes WLAN detects no SSID after s3
Issue was also seen with the NM 1.2 found in the -proposed repository for Xenial. -- 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/1578127 Title: Sometimes WLAN detects no SSID after s3 Status in NetworkManager: New Status in OEM Priority Project: New Status in network-manager package in Ubuntu: New Bug description: [Steps to reproduce] 1. Boot into OS 2. Do s3 a few times 3. Check if wifi is still working after s3 [Expected results] wifi still working correctly after s3 [Actual results] 1. Wifi shows "disconnected" in network-manager (both in applet and from command "nmcli d status") 2. Only one random SSID is displayed in network-manager applet, but wifi connection cannot be established at all with this SSID. Clicking on the SSID results in pop up window in the comment #2 below 3. "nmcli d wifi rescan" does not resolve issue 4. "iwlist [interface] scan" returns nothing and does not reolve issue 5. "nmcli d wifi connect [any SSID that you know should exist]" results in SSID not found and does not resolve issue 6. "sudo service network-manager restart", warm boot, cold boot resolves issue [Details] OS: Xenial based OEM image WLAN module: Marvel [11ab:2b38] network-manager: - 1.2.0-0ubuntu0.16.04.1 (fail rate 1/20~ 1/15) - 1.1.93 (fail rate 1/15) To manage notifications about this bug go to: https://bugs.launchpad.net/network-manager/+bug/1578127/+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 1578127] Re: Sometimes WLAN detects no SSID after s3
syslog when issue happens with NetworkManager 1.2 on Ubuntu 16.04 ** Also affects: network-manager Importance: Undecided Status: New ** Package changed: network-manager (Ubuntu) => oem-priority ** Attachment added: "X08_nm1.2_syslog" https://bugs.launchpad.net/oem-priority/+bug/1578127/+attachment/4655400/+files/X08_nm1.2_syslog -- 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/1578127 Title: Sometimes WLAN detects no SSID after s3 Status in NetworkManager: New Status in OEM Priority Project: New Bug description: [Steps to reproduce] 1. Boot into OS 2. Do s3 a few times 3. Check if wifi is still working after s3 [Expected results] wifi still working correctly after s3 [Actual results] 1. Wifi shows "disconnected" in network-manager (both in applet and from command "nmcli d status") 2. Only one random SSID is displayed in network-manager applet, but wifi connection cannot be established at all with this SSID. Clicking on the SSID results in pop up window in the comment #2 below 3. "nmcli d wifi rescan" does not resolve issue 4. "iwlist [interface] scan" returns nothing and does not reolve issue 5. "nmcli d wifi connect [any SSID that you know should exist]" results in SSID not found and does not resolve issue 6. "sudo service network-manager restart", warm boot, cold boot resolves issue [Details] OS: Xenial based OEM image WLAN module: Marvel [11ab:2b38] network-manager: - 1.2.0-0ubuntu0.16.04.1 (fail rate 1/20~ 1/15) - 1.1.93 (fail rate 1/15) To manage notifications about this bug go to: https://bugs.launchpad.net/network-manager/+bug/1578127/+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 1576011] Re: Sometimes wifi is unusable and detected as wired network
** Also affects: network-manager Importance: Undecided Status: New ** Package changed: network-manager (Ubuntu) => oem-priority -- 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/1576011 Title: Sometimes wifi is unusable and detected as wired network Status in NetworkManager: New Status in OEM Priority Project: New Bug description: * Steps to reproduce: 1. Boot into Ubuntu 2. Check wifi connection in network-manager applet drop-down list * Expected result: A list of available APs should be listed and connection can be established after selecting one AP * Actual result: Sometimes the wifi device is listed as a "Ethernet network", and system will unsuccessfully try to connect to this non-existing ethernet network. * Issue can be resolved by: 1. Warm boot 2. Cold boot 3. sudo service network-manager restart * Wireless module: Marvell Technology Group Ltd. 88W8897 [AVASTAR] 802.11ac Wireless [11ab:2b38] * Network-manager: 1.1.93-0ubuntu3 (Please note that an older network-manager version 1.0.4-0ubuntu10 does not have this issue) * Ubuntu: Xenial To manage notifications about this bug go to: https://bugs.launchpad.net/network-manager/+bug/1576011/+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 1340673] Re: SIM PIN Unlock Required dialog shows up after every resume
** Also affects: network-manager-applet 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/1340673 Title: SIM PIN Unlock Required dialog shows up after every resume Status in Network Manager Applet: New Status in network-manager-applet package in Ubuntu: Confirmed Bug description: Every time I resume after suspend, I get a dialog from nm-applet telling that SIM PIN Unlock Required. I'm running a ThinkPad T420s with a "Lenovo F5562gw" modem, which is an Ericsson device: # lsusb | grep Ericsson Bus 002 Device 005: ID 0bdb:1911 Ericsson Business Mobile Networks BV The first time I got the dialog, I entered the PIN and selected "Automatically unlock this device". Now, every time I resume, I can just Cancel the dialog box, and modem will work. This appears to be an annoying UI problem more than anything else. # lsb_release -v Distributor ID: Ubuntu Description: Ubuntu 14.04 LTS Release: 14.04 Codename: trusty # dpkg -l network-manager-gnome network-manager-gnome 0.9.8.8-0ubuntu4 This problem has persisted since at least 12.04. To manage notifications about this bug go to: https://bugs.launchpad.net/network-manager-applet/+bug/1340673/+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 1571574] Re: 3G icon missing in network-manager-applet
The last known working network-manger-applet is of 1.0.10-1ubuntu1 ** Also affects: network-manager-applet Importance: Undecided Status: New ** Also affects: oem-priority 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/1571574 Title: 3G icon missing in network-manager-applet Status in Network Manager Applet: New Status in OEM Priority Project: New Status in network-manager-applet package in Ubuntu: Confirmed Bug description: After establishing a 3G connection, the icon shown in system tray should be a 3G indicator to indicate that 3G is connected. However, in Xenial there is no 3G icon at all. After 3G connection is established, it remains as the previous icon displayed. (e.g. If no other connection was established before 3G connection was made, then the icon is a "hollow fan shape" after connecting to 3G. If wifi was connected before 3G connection was made, then the icon after 3G connection shows a wifi icon.) network-manager: 1.1.93-0ubuntu3 OS: Xenial daily (2016 Apr. 15) To manage notifications about this bug go to: https://bugs.launchpad.net/network-manager-applet/+bug/1571574/+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 1564156] Re: xenial: invalid opcode when using llvmpipe
** Also affects: mesa Importance: Undecided Status: New ** Package changed: mesa (Ubuntu) => oem-priority -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1564156 Title: xenial: invalid opcode when using llvmpipe Status in Mesa: New Status in OEM Priority Project: New Status in System76: Triaged Bug description: Currently Unity on Xenial is unusable when the llvmpipe software fallback is used, at least on certain hardware. For example, from dmesg: [ 2092.557913] traps: compiz[10155] trap invalid opcode ip:7efc940030d4 sp:7ffccd914ea0 error:0 [ 2093.109485] traps: compiz[10192] trap invalid opcode ip:7f38ac01a0d4 sp:7ffe5ed737e0 error:0 [ 2093.718863] traps: compiz[10212] trap invalid opcode ip:7fe6900010d4 sp:7ffd55804020 error:0 This definitely effects hardware we've tested with NVIDIA 970m and 980m GPUs (when using the nouveau driver), and probably effects others as well. Although strangely, with some NVIDIA 900 series hardware we're not seeing this bug when using the nouveau driver. This will be investigated further. In the current state, it's not possible to install Xenial on effected hardware using recent daily desktop amd64 ISOs. Note this problem exists both when run against mesa 11.1.2-1ubuntu2 in Xenial proper, and when run against mesa 11.2.0~rc4-1ubuntu0.1 from ppa:canonical-x/x-staging. (The later test was done with the System76 imaging system using an image with ppa:canonical-x/x-staging and nvidia-361 pre-installed, then removing nvidia-361 and rebooting). I'm kinda shooting in the dark here, but I did my best to rule out the kernel as a variable: (1) I built and installed the 4.4.0-16 kernel on 15.10, rebooted, and had no problems. (2) On Xenial I tried the 4.5 and 4.6rc1 mainline builds, but they don't fix the problem. I'm not sure the underling bug is in compiz, but I'm filing it against compiz anyway because that's where the dmesg output is pointing me. Other likely culprits include nux, mesa, maybe even llvm, and probably others I'm not thinking of :) Also, I'm positive llvmpipe is being used when this invalid opcode is trapped because I added this to /etc/X11/Xsession.d/50_check_unity_support: /usr/lib/nux/unity_support_test -p > /tmp/compiz-debug.log That way I could figure out what renderer was being used from a VT (as the X session is darn near unusable in this state). To manage notifications about this bug go to: https://bugs.launchpad.net/mesa/+bug/1564156/+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 1567796] Re: It is sometimes unable to found DELL WWAN module.
** Also affects: modemmanager Importance: Undecided Status: New ** Package changed: modemmanager (Ubuntu) => oem-priority ** Summary changed: - It is sometimes unable to found DELL WWAN module. + It is sometimes unable to find DELL WWAN module. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to modemmanager in Ubuntu. https://bugs.launchpad.net/bugs/1567796 Title: It is sometimes unable to find DELL WWAN module. Status in ModemManager: New Status in OEM Priority Project: New Bug description: I have a DELL WWAN module (DW5580) on my platform. Normally it could be detect and used in Ubuntu 16.04 daily image. However it is sometimes unusable and can not be detected. After debugging, we found there is an upstream patch that can fix the issue: https://cgit.freedesktop.org/ModemManager/ModemManager/commit/?id=8a386218690aeff7e2c923a14f91da7bbc046ed2 Please merge the fix to modem manager to fix the issue. Ubuntu Xenial (daily image) Release: 16.04 modemmanager: Installed: 1.4.12-1ubuntu1 Candidate: 1.4.12-1ubuntu1 Version table: *** 1.4.12-1ubuntu1 500 500 http://archive.ubuntu.com/ubuntu xenial/main amd64 Packages 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/modemmanager/+bug/1567796/+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 1562822] Re: Bluetooth Browse Files... not working
** Also affects: unity-control-center Importance: Undecided Status: New ** Also affects: oem-priority Importance: Undecided Status: New ** Changed in: oem-priority Importance: Undecided => Critical -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1562822 Title: Bluetooth Browse Files... not working Status in OEM Priority Project: New Status in Unity Control Center: New Status in unity-control-center package in Ubuntu: New Bug description: Mobile phone: LG L40 Android 4.4.2 1. Connecting to Phone is successful shown. 2. Click on Button "Browse Files... " nothing happen. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: unity-control-center 15.04.0+16.04.20160315-0ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-15.31-generic 4.4.6 Uname: Linux 4.4.0-15-generic x86_64 ApportVersion: 2.20-0ubuntu3 Architecture: amd64 CurrentDesktop: Unity Date: Mon Mar 28 13:31:39 2016 ExecutablePath: /usr/bin/unity-control-center InstallationDate: Installed on 2016-02-04 (52 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160204) SourcePackage: unity-control-center UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1562822/+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 1480217] Re: Nautilus background handling screwed when changing scaling factor.
This issue can not be seen in Ubuntu Vivid. -- 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/1480217 Title: Nautilus background handling screwed when changing scaling factor. Status in OEM Priority Project: New Status in OEM Priority Project trusty series: New Status in nautilus package in Ubuntu: Triaged Bug description: Ubuntu 14.04.2 Reproducible Steps: 1. Login to Unity desktop environment. 2. Change the scale factor to 2 in Displays of System Settings. 3. Logout and login again 3. Change the scale factor to 1 in Displays of System Settings. Expected Result: * The background will work normally. Actual Result: * The background becomes a mess. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1480217/+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 1059872] Re: Error formatting disk using disk utility
** Also affects: dargui Importance: Undecided Status: New ** Also affects: oem-priority Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to udisks2 in Ubuntu. https://bugs.launchpad.net/bugs/1059872 Title: Error formatting disk using disk utility Status in DarGUI - A GUI frontend for DAR utility: New Status in OEM Priority Project: New Status in udisks2 package in Ubuntu: Invalid Status in util-linux package in Ubuntu: Fix Released Status in udisks2 source package in Trusty: Invalid Status in util-linux source package in Trusty: Triaged Status in util-linux package in Debian: Fix Released Bug description: Formatting a SD card using the disk utility fails with an error message Error formatting disk - Error synchronizing after initial wipe: Timed out waiting for object (udisks-error-quark, 0) Steps to repro: Launch the disk utility Plug a SD card into the computer Select the SD card and click on the gears icon at the top right of the application From the drop down menu, select Format Disk maintain the default setting and select Format Acknowledge warnings After format process has been going for a while, the error message shown above pops up Workaround: After selecting the SD card, instead of clicking the gear icon to format, click the partition in the Volumes section. Delete the partition (minus icon) Create a new partition - The underlying problem is that the wipefs tool from util-linux does not work any more. === TEST CASE === $ sudo modprobe scsi_debug dev_size_mb=200 # this creates a new /dev/sdX, usually /dev/sdb; check dmesg! # now create a partition table $ cat EOF | sudo sfdisk /dev/sdb # partition table of /dev/sdb unit: sectors /dev/sdb1 : start= 32, size= 409568, Id=83 /dev/sdb2 : start=0, size=0, Id= 0 /dev/sdb3 : start=0, size=0, Id= 0 /dev/sdb4 : start=0, size=0, Id= 0 EOF # now create an ext4 file system: $ sudo mkfs.ext4 /dev/sdb1 # check contents: $ sudo blkid -p /dev/sdb /dev/sdb1 /dev/sdb: PTTYPE=dos /dev/sdb1: UUID=4bd1c542-a61f-43c4-a7e5-cc50e66e6b5a VERSION=1.0 TYPE=ext4 USAGE=filesystem PART_ENTRY_SCHEME=dos PART_ENTRY_TYPE=0x83 PART_ENTRY_NUMBER=1 PART_ENTRY_OFFSET=32 PART_ENTRY_SIZE=409568 PART_ENTRY_DISK=8:16 # wipe: $ sudo wipefs -a /dev/sdb # now check contents again $ sudo blkid -p /dev/sdb /dev/sdb1 # in the broken case, you will still see a dos partition table and the ext4 partition; in the working case, /dev/sdb won't show anything and /dev/sdb1 does not exist any more ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: udisks 1.0.4-6 ProcVersionSignature: Ubuntu 3.5.0-15.23-generic 3.5.4 Uname: Linux 3.5.0-15-generic x86_64 ApportVersion: 2.6.1-0ubuntu1 Architecture: amd64 CustomUdevRuleFiles: 51-android.rules 51-android.rules~ Date: Mon Oct 1 15:07:46 2012 InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Alpha amd64 (20120720.1) MachineType: FOXCONN NT-A2400NT-A3500 ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-15-generic root=UUID=fcc445e4-9662-47cc-855d-ca17ad1c2a87 ro quiet splash vt.handoff=7 SourcePackage: udisks UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/29/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4.6.4 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: NT-A2400NT-A3500 dmi.board.vendor: FOXCONN dmi.board.version: FAB 1.0 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 4 dmi.chassis.vendor: FOXCONN dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4.6.4:bd03/29/2011:svnFOXCONN:pnNT-A2400NT-A3500:pvrFAB1.0:rvnFOXCONN:rnNT-A2400NT-A3500:rvrFAB1.0:cvnFOXCONN:ct4:cvrToBeFilledByO.E.M.: dmi.product.name: NT-A2400NT-A3500 dmi.product.version: FAB 1.0 dmi.sys.vendor: FOXCONN To manage notifications about this bug go to: https://bugs.launchpad.net/dargui/+bug/1059872/+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 1460982] Re: sound: Testing mono output plays back noise.wav
** Also affects: unity-control-center Importance: Undecided Status: New ** Also affects: oem-priority Importance: Undecided Status: New ** Changed in: oem-priority Importance: Undecided = Medium -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1460982 Title: sound: Testing mono output plays back noise.wav Status in OEM Priority Project: New Status in Unity Control Center: New Status in unity-control-center package in Ubuntu: New Bug description: When having a mono output source, such as BT HFP/HSP, unity-control-center by default plays /usr/share/sounds/freedesktop/stereo/audio-test-signal.oga - which is a sample of noise. This makes it hard to know whether the speaker test works successfully, e g, if the sound output is noisy because of some bug, you will not notice (it's noise either way!). It would be better if the test button was a spoken voice, just like when you test Front Left, Front Right etc. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity-control-center 14.04.3+14.04.20140922-0ubuntu1 ProcVersionSignature: Ubuntu 3.16.0-31.43~14.04.1-generic 3.16.7-ckt5 Uname: Linux 3.16.0-31-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.11 Architecture: amd64 CurrentDesktop: Unity Date: Tue Jun 2 10:53:12 2015 EcryptfsInUse: Yes InstallationDate: Installed on 2014-03-07 (451 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140307) SourcePackage: unity-control-center UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_unity-control-center: deja-dup 30.0-0ubuntu4 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1460982/+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 1412937] Re: Config option to set UNITY_LOW_GFX_MODE=1
** Also affects: oem-priority Importance: Undecided Status: New ** Also affects: oem-priority/trusty Importance: Undecided Status: New -- 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/1412937 Title: Config option to set UNITY_LOW_GFX_MODE=1 Status in OEM Priority Project: New Status in OEM Priority Project trusty series: New Status in Unity: Triaged Status in unity package in Ubuntu: Triaged Bug description: Right now the procedure to turn on low_gfx_mode is https://bugs.launchpad.net/compiz/+bug/1293384/comments/15 sudo -H gedit /usr/share/gnome-session/sessions/ubuntu.session Remove compiz from the RequiredComponents list sudo -H gedit /usr/share/upstart/sessions/unity7.conf: Add these lines after export COMPIZ_CONFIG_PROFILE: env UNITY_LOW_GFX_MODE=1 export UNITY_LOW_GFX_MODE We should add a config option (preferably system wide) to tell Compiz/Unity to go to the LOW_GFX mode regardless of what the hardware says it can do. This will make it easier to setup items like terminal services using Unity. This procedure has helped in at least one case for me, (a machine used by several users remotely using Unity). I can imagine it would also help in multiseat scenarios, etc. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1412937/+subscriptions -- Mailing list: https://launchpad.net/~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 1416005] Re: totem fails to play video if gstreamer-vaapi is installed
** Also affects: oem-priority Importance: Undecided Status: New ** Also affects: oem-priority/trusty Importance: Undecided Status: New ** Changed in: oem-priority/trusty Importance: Undecided = High -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to clutter-gst-2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1416005 Title: totem fails to play video if gstreamer-vaapi is installed Status in OEM Priority Project: New Status in OEM Priority Project trusty series: New Status in clutter-gst-2.0 package in Ubuntu: Confirmed Status in clutter-gst-2.0 package in Debian: New Bug description: If gstreamer-vaapi is installed Totem fails to play anything, and instead just shows an error popup saying GStreamer encountered a general stream error. The app doesn't produce any error msg on the terminal, but shows that vaapi is being used: ... (totem:8470): Grilo-WARNING **: [registry] grl-registry.c:472: Could not open plugins' info directory '/usr/lib/x86_64-linux-gnu/grilo-0.2': Error opening directory '/usr/lib/x86_64-linux-gnu/grilo-0.2': No such file or directory (totem:8470): Totem-WARNING **: Failed to load grilo plugins: All configured plugin paths are invalid libva info: VA-API version 0.37.0 libva info: va_getDriverName() returns 0 libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/i965_drv_video.so libva info: Found init function __vaDriverInit_0_36 libva info: va_openDriver() returns 0 (totem:8470): Gtk-WARNING **: Symbolic icon view-sidebar-symbolic-ltr of size 16 is in an icon theme directory of size 128 ... Gst-launch using vaapidecocde and vaapisink still works properly, using gst-launch-1.0 filesrc location=bbb_sunflower_2160p_60fps_normal.mp4 ! qtdemux ! vaapidecode ! vaapisink takes 6% cpu instead of 300% on my broadwell based laptop. video downloaded from here http://bbb3d.renderfarming.net/download.html To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1416005/+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 997370] Re: Totem does not use the va-api gstreamer backend
** Also affects: oem-priority Importance: Undecided Status: New ** Also affects: oem-priority/trusty Importance: Undecided Status: New ** Changed in: oem-priority/trusty Importance: Undecided = High -- 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/997370 Title: Totem does not use the va-api gstreamer backend Status in OEM Priority Project: New Status in OEM Priority Project trusty series: New Status in Totem Movie Player: Confirmed Status in totem package in Ubuntu: Fix Released Bug description: installing gstreamer -vaapi from ubuntu repos breaks thumbnail generation in nautilus furthermore acceleration does not work in totem - cpu usage is as high as with software rendering. mplayer-vaapi works perfectly on the same system. gst-launch-0.10 -v filesrc location=~/test.mkv ! matroskademux ! vaapidecode ! vaapisink makes it possible to use vaapi via commandline i did not find a way to use vaapi for mpeg4 part 2 video streams. and i wasnt able to find proper values for gstreamer-properties that fix thumbnails and acceleration in totem. id like to share debug information. just tell me what you need. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/997370/+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 1315285] Re: [AMD Richland + Mars] Unable to switch graphics
The working xorg.conf is attached for your reference. ** Attachment added: xorg.conf https://bugs.launchpad.net/ubuntu/+source/fglrx-installer/+bug/1315285/+attachment/4334086/+files/xorg.conf -- 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/1315285 Title: [AMD Richland + Mars] Unable to switch graphics Status in fglrx-installer package in Ubuntu: Incomplete Bug description: Unable to switch in between APU and Discrete GPU. Step to reproduce: Oepn AMD Crystal Control Center, $ sudo amdcccle Expected: Switchable graphics settings menu will shown Actual result: Found no switchable graphics settings Currently found effected: APU: 00:01.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. [AMD/ATI] Richland [Radeon HD 8450G] [1002:9995] with GPU: 01:00.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. [AMD/ATI] Mars [Radeon HD 8670A/8670M/8750M] [1002:6600] ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-24-generic 3.13.0-24.46 [modified: boot/vmlinuz-3.13.0-24-generic] ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 NonfreeKernelModules: fglrx ApportVersion: 2.14.1-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: ubuntu 1562 F pulseaudio /dev/snd/controlC0: ubuntu 1562 F pulseaudio CRDA: country TW: (2402 - 2472 @ 40), (3, 27) (5270 - 5330 @ 40), (3, 17), DFS (5735 - 5815 @ 40), (3, 30) CurrentDesktop: Unity Date: Fri May 2 15:59:50 2014 HibernationDevice: RESUME=UUID=be96939f-ffde-4407-a99e-17beebf60ad5 InstallationDate: Installed on 2014-04-30 (1 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417) MachineType: Hewlett-Packard HP ProBook 445 G1 Notebook PC ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-24-generic root=UUID=58dd6874-a445-4c06-ab93-5be7a08a2c62 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.13.0-24-generic N/A linux-backports-modules-3.13.0-24-generic N/A linux-firmware 1.127 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/05/2013 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68CPE Ver. F.21 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 1950 dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 91.0B dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr68CPEVer.F.21:bd09/05/2013:svnHewlett-Packard:pnHPProBook445G1NotebookPC:pvrA201BC1203:rvnHewlett-Packard:rn1950:rvrKBCVersion91.0B:cvnHewlett-Packard:ct10:cvr: dmi.product.name: HP ProBook 445 G1 Notebook PC dmi.product.version: A201BC1203 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fglrx-installer/+bug/1315285/+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 1410775] Re: [AMD Mullins + Jet XT] The graphic is not switchable with fglrx
AMD Mullings/Beema platforms do not support switchable graphics, this is by design. -- 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/1410775 Title: [AMD Mullins + Jet XT] The graphic is not switchable with fglrx Status in fglrx-installer package in Ubuntu: New Bug description: This laptop got following GPUs: 00:01.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. [AMD/ATI] Mullins [Radeon R2 Graphics] [1002:9852] 01:00.0 Display controller [0380]: Advanced Micro Devices, Inc. [AMD/ATI] Jet XT [Radeon R5 M240] [1002:6664] After system upgraded (trusty, 20150114) and installed the proprietary driver listed in Addional Drivers, the system still tells AMD Radeon(TM) R2 Graphics is in use, but there is no way to switch to the other discrete graphic card. Steps to reproduce: 1. Fresh install 2. Install fglrx(proprietary driver) 3. Go to System Setttings - Details or 4. Open AMD Catalyst Control Center Expected result: The graphic card are expected to be in used by the system. Or Able to switch in between graphic chips Actual result: Unable to switch the graphic and only integrated GPU is using by system. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: fglrx 2:13.350.1-0ubuntu2 ProcVersionSignature: Ubuntu 3.13.0-44.73-generic 3.13.11-ckt12 Uname: Linux 3.13.0-44-generic x86_64 NonfreeKernelModules: fglrx .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.6 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Wed Jan 14 20:02:22 2015 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu DkmsStatus: fglrx, 13.350.1, 3.13.0-44-generic, x86_64: installed GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Mullins [Radeon R2 Graphics] [1002:9852] (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Device [103c:22c2] Subsystem: Hewlett-Packard Company Device [103c:22c2] InstallationDate: Installed on 2015-01-13 (1 days ago) InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 (20140722.2) MachineType: Hewlett-Packard Presario CQ45 Notebook PC ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-44-generic.efi.signed root=UUID=74553f05-2b74-46cc-87d3-537a92c0439a ro quiet splash vt.handoff=7 SourcePackage: fglrx-installer UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/03/2014 dmi.bios.vendor: Insyde dmi.bios.version: B.0A dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 22C2 dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 86.08 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrB.0A:bd04/03/2014:svnHewlett-Packard:pnPresarioCQ45NotebookPC:pvr05A920200:rvnHewlett-Packard:rn22C2:rvrKBCVersion86.08:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.name: Presario CQ45 Notebook PC dmi.product.version: 05A920200 dmi.sys.vendor: Hewlett-Packard version.compiz: compiz 1:0.9.11.3+14.04.20141104-0ubuntu1 version.fglrx-installer: fglrx-installer N/A version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.56-1~ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.2 version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2.6 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3.1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1.3 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 xserver.bootTime: Wed Jan 14 18:44:25 2015 xserver.configfile: /etc/X11/xorg.conf xserver.errors: AIGLX error: failed to open /usr/X11R6/lib64/modules/dri/fglrx_dri.so, error[/usr/X11R6/lib64/modules/dri/fglrx_dri.so: cannot open shared object file: No such file or directory] AIGLX error: failed to open /usr/lib64/dri/fglrx_dri.so, error[/usr/lib64/dri/fglrx_dri.so: cannot open shared object file: No such file or directory] AIGLX error: failed to open /usr/X11R6/lib/modules/dri/fglrx_dri.so, error[/usr/X11R6/lib/modules/dri/fglrx_dri.so: cannot open shared object file: No such file or directory] xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.15.1-0ubuntu2.6 xserver.video_driver: fglrx To manage notifications about this bug go to:
[Desktop-packages] [Bug 1410775] Re: [AMD Mullins + Jet XT] The graphic is not switchable with fglrx
Regarding the (EE) error messages shown in Xorg.0.log, can you give the newer Catalyst driver a try (http://support.amd.com/en- us/download/desktop?os=Linux+x86) to see if it improves the situation? -- 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/1410775 Title: [AMD Mullins + Jet XT] The graphic is not switchable with fglrx Status in fglrx-installer package in Ubuntu: New Bug description: This laptop got following GPUs: 00:01.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. [AMD/ATI] Mullins [Radeon R2 Graphics] [1002:9852] 01:00.0 Display controller [0380]: Advanced Micro Devices, Inc. [AMD/ATI] Jet XT [Radeon R5 M240] [1002:6664] After system upgraded (trusty, 20150114) and installed the proprietary driver listed in Addional Drivers, the system still tells AMD Radeon(TM) R2 Graphics is in use, but there is no way to switch to the other discrete graphic card. Steps to reproduce: 1. Fresh install 2. Install fglrx(proprietary driver) 3. Go to System Setttings - Details or 4. Open AMD Catalyst Control Center Expected result: The graphic card are expected to be in used by the system. Or Able to switch in between graphic chips Actual result: Unable to switch the graphic and only integrated GPU is using by system. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: fglrx 2:13.350.1-0ubuntu2 ProcVersionSignature: Ubuntu 3.13.0-44.73-generic 3.13.11-ckt12 Uname: Linux 3.13.0-44-generic x86_64 NonfreeKernelModules: fglrx .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.6 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Wed Jan 14 20:02:22 2015 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu DkmsStatus: fglrx, 13.350.1, 3.13.0-44-generic, x86_64: installed GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Mullins [Radeon R2 Graphics] [1002:9852] (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Device [103c:22c2] Subsystem: Hewlett-Packard Company Device [103c:22c2] InstallationDate: Installed on 2015-01-13 (1 days ago) InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 (20140722.2) MachineType: Hewlett-Packard Presario CQ45 Notebook PC ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-44-generic.efi.signed root=UUID=74553f05-2b74-46cc-87d3-537a92c0439a ro quiet splash vt.handoff=7 SourcePackage: fglrx-installer UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/03/2014 dmi.bios.vendor: Insyde dmi.bios.version: B.0A dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 22C2 dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 86.08 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrB.0A:bd04/03/2014:svnHewlett-Packard:pnPresarioCQ45NotebookPC:pvr05A920200:rvnHewlett-Packard:rn22C2:rvrKBCVersion86.08:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.name: Presario CQ45 Notebook PC dmi.product.version: 05A920200 dmi.sys.vendor: Hewlett-Packard version.compiz: compiz 1:0.9.11.3+14.04.20141104-0ubuntu1 version.fglrx-installer: fglrx-installer N/A version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.56-1~ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.2 version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2.6 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3.1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1.3 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 xserver.bootTime: Wed Jan 14 18:44:25 2015 xserver.configfile: /etc/X11/xorg.conf xserver.errors: AIGLX error: failed to open /usr/X11R6/lib64/modules/dri/fglrx_dri.so, error[/usr/X11R6/lib64/modules/dri/fglrx_dri.so: cannot open shared object file: No such file or directory] AIGLX error: failed to open /usr/lib64/dri/fglrx_dri.so, error[/usr/lib64/dri/fglrx_dri.so: cannot open shared object file: No such file or directory] AIGLX error: failed to open /usr/X11R6/lib/modules/dri/fglrx_dri.so, error[/usr/X11R6/lib/modules/dri/fglrx_dri.so: cannot open shared object file: No such file or directory] xserver.logfile: /var/log/Xorg.0.log
[Desktop-packages] [Bug 1315285] Re: [AMD Richland + Mars] Unable to switch graphics
According to AMD engineering, the A+A platforms based on Mullings and Beema chipsets do NOT support switchable graphics. It is made clear that in their GUI configuration tool (AMDCCCLE), no such option exists for such platforms. -- 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/1315285 Title: [AMD Richland + Mars] Unable to switch graphics Status in fglrx-installer package in Ubuntu: Triaged Bug description: Unable to switch in between APU and Discrete GPU. Step to reproduce: Oepn AMD Crystal Control Center, $ sudo amdcccle Expected: Switchable graphics settings menu will shown Actual result: Found no switchable graphics settings Currently found effected: APU: 00:01.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. [AMD/ATI] Richland [Radeon HD 8450G] [1002:9995] with GPU: 01:00.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. [AMD/ATI] Mars [Radeon HD 8670A/8670M/8750M] [1002:6600] ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-24-generic 3.13.0-24.46 [modified: boot/vmlinuz-3.13.0-24-generic] ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 NonfreeKernelModules: fglrx ApportVersion: 2.14.1-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: ubuntu 1562 F pulseaudio /dev/snd/controlC0: ubuntu 1562 F pulseaudio CRDA: country TW: (2402 - 2472 @ 40), (3, 27) (5270 - 5330 @ 40), (3, 17), DFS (5735 - 5815 @ 40), (3, 30) CurrentDesktop: Unity Date: Fri May 2 15:59:50 2014 HibernationDevice: RESUME=UUID=be96939f-ffde-4407-a99e-17beebf60ad5 InstallationDate: Installed on 2014-04-30 (1 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417) MachineType: Hewlett-Packard HP ProBook 445 G1 Notebook PC ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-24-generic root=UUID=58dd6874-a445-4c06-ab93-5be7a08a2c62 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.13.0-24-generic N/A linux-backports-modules-3.13.0-24-generic N/A linux-firmware 1.127 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/05/2013 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68CPE Ver. F.21 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 1950 dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 91.0B dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr68CPEVer.F.21:bd09/05/2013:svnHewlett-Packard:pnHPProBook445G1NotebookPC:pvrA201BC1203:rvnHewlett-Packard:rn1950:rvrKBCVersion91.0B:cvnHewlett-Packard:ct10:cvr: dmi.product.name: HP ProBook 445 G1 Notebook PC dmi.product.version: A201BC1203 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fglrx-installer/+bug/1315285/+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 1315285] Re: [AMD Richland + Mars] Unable to switch graphics
And in other AMD A+A platforms such as [AMD Richland + Mars], which this issue was originally reported against, switchable graphics works with the latter Catalyst driver (14.502, earlier drivers may also work but not verified) after disabling gpumanager so that the X configuration is not further overwritten by it. -- 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/1315285 Title: [AMD Richland + Mars] Unable to switch graphics Status in fglrx-installer package in Ubuntu: Triaged Bug description: Unable to switch in between APU and Discrete GPU. Step to reproduce: Oepn AMD Crystal Control Center, $ sudo amdcccle Expected: Switchable graphics settings menu will shown Actual result: Found no switchable graphics settings Currently found effected: APU: 00:01.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. [AMD/ATI] Richland [Radeon HD 8450G] [1002:9995] with GPU: 01:00.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. [AMD/ATI] Mars [Radeon HD 8670A/8670M/8750M] [1002:6600] ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-24-generic 3.13.0-24.46 [modified: boot/vmlinuz-3.13.0-24-generic] ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 NonfreeKernelModules: fglrx ApportVersion: 2.14.1-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: ubuntu 1562 F pulseaudio /dev/snd/controlC0: ubuntu 1562 F pulseaudio CRDA: country TW: (2402 - 2472 @ 40), (3, 27) (5270 - 5330 @ 40), (3, 17), DFS (5735 - 5815 @ 40), (3, 30) CurrentDesktop: Unity Date: Fri May 2 15:59:50 2014 HibernationDevice: RESUME=UUID=be96939f-ffde-4407-a99e-17beebf60ad5 InstallationDate: Installed on 2014-04-30 (1 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417) MachineType: Hewlett-Packard HP ProBook 445 G1 Notebook PC ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-24-generic root=UUID=58dd6874-a445-4c06-ab93-5be7a08a2c62 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.13.0-24-generic N/A linux-backports-modules-3.13.0-24-generic N/A linux-firmware 1.127 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/05/2013 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68CPE Ver. F.21 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 1950 dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 91.0B dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr68CPEVer.F.21:bd09/05/2013:svnHewlett-Packard:pnHPProBook445G1NotebookPC:pvrA201BC1203:rvnHewlett-Packard:rn1950:rvrKBCVersion91.0B:cvnHewlett-Packard:ct10:cvr: dmi.product.name: HP ProBook 445 G1 Notebook PC dmi.product.version: A201BC1203 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fglrx-installer/+bug/1315285/+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 1308954] Re: AMDRadeon HD 8670A/8670M/8690M [1002:6660] System freezes after resume from suspend with fglrx-updates
Please give the AMD Catalyst 14.9 driver a try which was just released recently has seemingly incorporated many bug fixes: http://www2.ati.com/drivers/linux/amd-catalyst-14-9-linux-x86-x86-64.zip -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to fglrx-installer-updates in Ubuntu. https://bugs.launchpad.net/bugs/1308954 Title: AMDRadeon HD 8670A/8670M/8690M [1002:6660] System freezes after resume from suspend with fglrx-updates Status in “fglrx-installer-updates” package in Ubuntu: Confirmed Bug description: CID: 201305-13624 This system would freeze after resume from suspend with fglrx-updates on Trusty dailylive Steps: 1. Install 14.04 Dailylive, and fglrx-updates driver 2. Suspend 3. Wake it up Expected results: * Everything works fine before / after S3 Actual results: * After S3, system freezed in a few seconds, error message could be found in syslog kernel: [ 599.576267] 3[fglrx:firegl_pplib_notify_event] *ERROR* PPLIB: PPLib Notify Event failed! kernel: [ 599.576268] 3[fglrx:firegl_pplib_notify_event] *ERROR* ulEventType = 0002, ulEventData = ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: fglrx-updates 2:13.350.1-0ubuntu2 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 NonfreeKernelModules: fglrx .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Thu Apr 17 16:42:48 2014 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu DkmsStatus: fglrx-updates, 13.350.1, 3.13.0-23-generic, x86_64: installed fglrx-updates, 13.350.1, 3.13.0-24-generic, x86_64: installed fwts-efi-runtime-dkms, 14.03.01, 3.13.0-24-generic, x86_64: installed GraphicsCard: Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Device [103c:2162] Subsystem: Hewlett-Packard Company Device [103c:2162] InstallationDate: Installed on 2014-04-10 (7 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Daily amd64 (20140406) MachineType: Hewlett-Packard HP Pavilion TS 14 Notebook PC ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-24-generic.efi.signed root=UUID=ef6ba3b5-e12b-4029-9d6b-cb1753a88ce5 ro quiet splash vt.handoff=7 SourcePackage: fglrx-installer-updates UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/27/2013 dmi.bios.vendor: Insyde dmi.bios.version: B.09 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 2162 dmi.board.vendor: Hewlett-Packard dmi.board.version: 29.0A dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrB.09:bd05/27/2013:svnHewlett-Packard:pnHPPavilionTS14NotebookPC:pvr089C101630100:rvnHewlett-Packard:rn2162:rvr29.0A:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.name: HP Pavilion TS 14 Notebook PC dmi.product.version: 089C101630100 dmi.sys.vendor: Hewlett-Packard version.compiz: compiz 1:0.9.11+14.04.20140409-0ubuntu1 version.fglrx-installer: fglrx-installer N/A version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.52-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.0-4ubuntu5 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.0-4ubuntu5 version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 xserver.bootTime: Thu Apr 17 16:31:44 2014 xserver.configfile: /etc/X11/xorg.conf xserver.errors: Screen 1 deleted because of no matching config section. AIGLX error: failed to open /usr/X11R6/lib64/modules/dri/fglrx_dri.so, error[/usr/X11R6/lib64/modules/dri/fglrx_dri.so: cannot open shared object file: No such file or directory] AIGLX error: failed to open /usr/lib64/dri/fglrx_dri.so, error[/usr/lib64/dri/fglrx_dri.so: cannot open shared object file: No such file or directory] AIGLX error: failed to open /usr/X11R6/lib/modules/dri/fglrx_dri.so, error[/usr/X11R6/lib/modules/dri/fglrx_dri.so: cannot open shared object file: No such file or directory] xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.15.1-0ubuntu2 xserver.video_driver: fglrx To manage notifications about this
[Desktop-packages] [Bug 1332489] Re: [Dell Inspiron 5547] AMD Radeon R7 M260 [1002:6900] Unable to resume from suspend with fglrx
@Po-Hsu, we would need more info on the system config when the issue is happening. With AMD's fglrx driver installed, can you help make sure what graphics mode (I or A) when the issue happens? To find out which graphics module is in use: aticonfig --pxl To switch to Intel, run the following command and reboot: sudo aticonfig --px-igpu To switch to AMD, run the following command and reboot: sudo aticonfig --px-dgpu Please also include the /var/log/syslog file after failure happens. Thanks. -- 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/1332489 Title: [Dell Inspiron 5547] AMD Radeon R7 M260 [1002:6900] Unable to resume from suspend with fglrx Status in HWE Next Project: New Status in “fglrx-installer” package in Ubuntu: New Status in “fglrx-installer” source package in Trusty: New Bug description: CID: 201401-14542 Dell Inspiron 5547 This system can be suspended, but it cannot resume from suspend with fglrx. (Without the proprietary driver, which means run on the Intel GPU, suspend works fine with it) Steps: 1. Install 14.04 + update (3.13.0-29) + fglrx (2:13.350.1-0ubuntu2) 2. Boot to desktop, suspend it with the option in the power menu 3. Wake it up by pressing the power button Expected result: * Suspend / resume should work. Actual result: * System suspended, but unable to resume properly, it will stuck on the login screen with fan running at full speed. Touchpad and caps Lock LED are not responding Since we will need to test the hybrid graphic feature, and it needs the proprietary driver to switch between the integrated and discrete GPU, I will mark this bug as a blocker. Debugging informatio: ubuntu@201401-14542:~$ cat /proc/acpi/wakeup DeviceS-state Status Sysfs node P0P1S4*disabled LID0S3*enabled EHC1S0*enabled pci::00:1d.0 XHC S0*enabled pci::00:14.0 PXSXS4*disabled RP03S3*disabled pci::00:1c.0 PEGPS4*disabled pci::03:00.0 PEGAS4*disabled PEG0S4*disabled PEGPS4*disabled PEG1S4*disabled PEG2S4*disabled ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-29-generic 3.13.0-29.53 ProcVersionSignature: Ubuntu 3.13.0-29.53-generic 3.13.11.2 Uname: Linux 3.13.0-29-generic x86_64 NonfreeKernelModules: fglrx ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1445 F pulseaudio /dev/snd/controlC1: ubuntu 1445 F pulseaudio CRDA: country TW: (2402 - 2472 @ 40), (3, 27) (5270 - 5330 @ 40), (3, 17), DFS (5735 - 5815 @ 40), (3, 30) CurrentDesktop: Unity Date: Fri Jun 20 06:48:41 2014 HibernationDevice: RESUME=UUID=202f89f5-b720-4ad7-b55e-dce344e24df1 InstallationDate: Installed on 2014-06-20 (0 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417) MachineType: Dell Inc. Inspiron 5547 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-29-generic root=UUID=e692386d-a813-4051-8eb5-b1932c2214d1 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.13.0-29-generic N/A linux-backports-modules-3.13.0-29-generic N/A linux-firmware 1.127.2 SourcePackage: linux StagingDrivers: rts5139 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/12/2014 dmi.bios.vendor: Dell Inc. dmi.bios.version: X18 dmi.board.name: 08KNCD dmi.board.vendor: Dell Inc. dmi.board.version: X01 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: X18 dmi.modalias: dmi:bvnDellInc.:bvrX18:bd02/12/2014:svnDellInc.:pnInspiron5547:pvrX18:rvnDellInc.:rn08KNCD:rvrX01:cvnDellInc.:ct8:cvrX18: dmi.product.name: Inspiron 5547 dmi.product.version: X18 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1332489/+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 1327990] Re: [Dell Inspiron 5447] failed to suspend-resume when using AMD Radeon R7 M260 graphic card [1002:6900]
A similar issue was reported against AMD/ATI [1002:6900] and a beta fglrx driver was posted there: https://bugs.launchpad.net/ubuntu/+source /fglrx-installer/+bug/1332489/comments/3 -- 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/1327990 Title: [Dell Inspiron 5447] failed to suspend-resume when using AMD Radeon R7 M260 graphic card [1002:6900] Status in HWE Next Project: New Status in “fglrx-installer” package in Ubuntu: New Bug description: Dell Inspiron 5447 (CID 201401-14529) on 14.04 Steps to reproduce this bug: 1. install proprietary driver by clicking 'Ubuntu Software Center'--Software sources-- the tab 'Additional Drivers' 2. select the suggested proprietary drivers fglrx or fglrx-updates 3. reboot the system 4. suspend the system by 'sudo rtcwake -s 60 -m mem' or the indicator in the top right of the desktop 5. press power to resume the system if you suspended the system by the indicator Expected result: the system will resume back to work. Actul result: When resuming from suspend, the system will resume back to the stage which shows you the desktop screen, and then freeze. The resume screen looks fine but the system is freezed. Both of fglrx and fglrx-updates have the same issue. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: fglrx (not installed) ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 NonfreeKernelModules: fglrx .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Mon Jun 9 04:15:09 2014 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu DkmsStatus: fglrx-updates, 13.350.1, 3.13.0-24-generic, x86_64: installed fwts-efi-runtime-dkms, 14.03.01, 3.13.0-24-generic, x86_64: installed GraphicsCard: Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 0b) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:0640] InstallationDate: Installed on 2014-06-04 (5 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417) MachineType: Dell Inc. Inspiron 5447 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-24-generic root=UUID=0b1afcfd-68b0-40fa-b708-243e4be4209b ro rootdelay=60 quiet splash initcall_debug vt.handoff=7 SourcePackage: fglrx-installer UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/12/2014 dmi.bios.vendor: Dell Inc. dmi.bios.version: X18 dmi.board.name: 0NGDM1 dmi.board.vendor: Dell Inc. dmi.board.version: X01 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: X18 dmi.modalias: dmi:bvnDellInc.:bvrX18:bd02/12/2014:svnDellInc.:pnInspiron5447:pvrX18:rvnDellInc.:rn0NGDM1:rvrX01:cvnDellInc.:ct8:cvrX18: dmi.product.name: Inspiron 5447 dmi.product.version: X18 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.11+14.04.20140409-0ubuntu1 version.fglrx-installer: fglrx-installer N/A version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.52-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.0-4ubuntu5 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.0-4ubuntu5 version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 xserver.bootTime: Mon Jun 9 02:26:45 2014 xserver.configfile: /etc/X11/xorg.conf xserver.errors: Screen 1 deleted because of no matching config section. xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.15.1-0ubuntu2 xserver.video_driver: fglrx To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1327990/+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 1315285] Re: [AMD Richland + Mars] Unable to switch graphics
@Hugo, all the affected units happened to be called back by ODM at this moment and we will try to collect the logs as requested once we have them back. Thanks. -- 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/1315285 Title: [AMD Richland + Mars] Unable to switch graphics Status in “fglrx-installer” package in Ubuntu: Triaged Bug description: Unable to switch in between APU and Discrete GPU. Step to reproduce: Oepn AMD Crystal Control Center, $ sudo amdcccle Expected: Switchable graphics settings menu will shown Actual result: Found no switchable graphics settings Currently found effected: APU: 00:01.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. [AMD/ATI] Richland [Radeon HD 8450G] [1002:9995] with GPU: 01:00.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. [AMD/ATI] Mars [Radeon HD 8670A/8670M/8750M] [1002:6600] ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-24-generic 3.13.0-24.46 [modified: boot/vmlinuz-3.13.0-24-generic] ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 NonfreeKernelModules: fglrx ApportVersion: 2.14.1-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: ubuntu 1562 F pulseaudio /dev/snd/controlC0: ubuntu 1562 F pulseaudio CRDA: country TW: (2402 - 2472 @ 40), (3, 27) (5270 - 5330 @ 40), (3, 17), DFS (5735 - 5815 @ 40), (3, 30) CurrentDesktop: Unity Date: Fri May 2 15:59:50 2014 HibernationDevice: RESUME=UUID=be96939f-ffde-4407-a99e-17beebf60ad5 InstallationDate: Installed on 2014-04-30 (1 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417) MachineType: Hewlett-Packard HP ProBook 445 G1 Notebook PC ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-24-generic root=UUID=58dd6874-a445-4c06-ab93-5be7a08a2c62 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.13.0-24-generic N/A linux-backports-modules-3.13.0-24-generic N/A linux-firmware 1.127 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/05/2013 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68CPE Ver. F.21 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 1950 dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 91.0B dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr68CPEVer.F.21:bd09/05/2013:svnHewlett-Packard:pnHPProBook445G1NotebookPC:pvrA201BC1203:rvnHewlett-Packard:rn1950:rvrKBCVersion91.0B:cvnHewlett-Packard:ct10:cvr: dmi.product.name: HP ProBook 445 G1 Notebook PC dmi.product.version: A201BC1203 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fglrx-installer/+bug/1315285/+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 1315285] Re: [AMD Richland + Mars] Unable to switch graphics
@Yung, if the Switchable Graphics is enabled in BIOS, the PX mode that AMD referred to should already be there. And according to AMD team, switchable graphics in AMD Richland should just work. Can you help provide more info by going through the following commands: aticonfig --lsa Is the xorg.conf existent? If not, can you run the following command to create one? sudo amdconfig --initial --force --adapter=all Afterwards, please reboot the system and retest this issue. Thank you. -- 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/1315285 Title: [AMD Richland + Mars] Unable to switch graphics Status in “fglrx-installer” package in Ubuntu: Triaged Bug description: Unable to switch in between APU and Discrete GPU. Step to reproduce: Oepn AMD Crystal Control Center, $ sudo amdcccle Expected: Switchable graphics settings menu will shown Actual result: Found no switchable graphics settings Currently found effected: APU: 00:01.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. [AMD/ATI] Richland [Radeon HD 8450G] [1002:9995] with GPU: 01:00.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. [AMD/ATI] Mars [Radeon HD 8670A/8670M/8750M] [1002:6600] ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-24-generic 3.13.0-24.46 [modified: boot/vmlinuz-3.13.0-24-generic] ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 NonfreeKernelModules: fglrx ApportVersion: 2.14.1-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: ubuntu 1562 F pulseaudio /dev/snd/controlC0: ubuntu 1562 F pulseaudio CRDA: country TW: (2402 - 2472 @ 40), (3, 27) (5270 - 5330 @ 40), (3, 17), DFS (5735 - 5815 @ 40), (3, 30) CurrentDesktop: Unity Date: Fri May 2 15:59:50 2014 HibernationDevice: RESUME=UUID=be96939f-ffde-4407-a99e-17beebf60ad5 InstallationDate: Installed on 2014-04-30 (1 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417) MachineType: Hewlett-Packard HP ProBook 445 G1 Notebook PC ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-24-generic root=UUID=58dd6874-a445-4c06-ab93-5be7a08a2c62 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.13.0-24-generic N/A linux-backports-modules-3.13.0-24-generic N/A linux-firmware 1.127 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/05/2013 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68CPE Ver. F.21 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 1950 dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 91.0B dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr68CPEVer.F.21:bd09/05/2013:svnHewlett-Packard:pnHPProBook445G1NotebookPC:pvrA201BC1203:rvnHewlett-Packard:rn1950:rvrKBCVersion91.0B:cvnHewlett-Packard:ct10:cvr: dmi.product.name: HP ProBook 445 G1 Notebook PC dmi.product.version: A201BC1203 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fglrx-installer/+bug/1315285/+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 1262539] Re: Driver for NVIDIA GF117M (GT620M) [10de:1140]
By the way, after installing nvidia-prime, the 331.38 nvidia driver could be successfully loaded and enabled. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-331-updates in Ubuntu. https://bugs.launchpad.net/bugs/1262539 Title: Driver for NVIDIA GF117M (GT620M) [10de:1140] Status in Jockey driver manager: New Status in “nvidia-graphics-drivers-331” package in Ubuntu: Confirmed Status in “nvidia-graphics-drivers-331-updates” package in Ubuntu: New Bug description: CID: 201307-14032 Dell Latitude E5540 According to http://www.nvidia.com/object/linux-display-amd64-319.32-driver.html The video card on this system: 03:00.0 3D controller [0302]: NVIDIA Corporation GF117M [GeForce 610M/710M / GT 620M/625M/630M/720M] [10de:1140] (rev a1) Should be suported by nvidia-319.32, however, the driver was not listed in jockey-gtk unless you install nvidia-319 manually Also, there is no option for turn on/off optimus mode in BIOS. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: nvidia-319 319.32-0ubuntu0.0.1 ProcVersionSignature: Ubuntu 3.8.0-34.49~precise1-generic 3.8.13.12 Uname: Linux 3.8.0-34-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.0.1-0ubuntu17.6 Architecture: amd64 Date: Thu Dec 19 15:36:15 2013 InstallationMedia: Ubuntu 12.04.3 LTS Precise Pangolin - Release amd64 (20130820.1) MarkForUpload: True ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: nvidia-graphics-drivers-319 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/jockey/+bug/1262539/+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 1262539] Re: Driver for NVIDIA GF117M (GT620M) [10de:1140]
Tried to manually install the 331.38 Nvidia driver (available as http://www.nvidia.com/content/DriverDownload- March2009/confirmation.php?url=/XFree86/Linux-x86_64/331.38/NVIDIA- Linux-x86_64-331.38.runlang=ustype=GeForce) on a Dell E5540 unit equipped with Nvidia GT620M GPU, and got the same (EE) Failed to initialize GLX extension (Compatible NVIDIA X driver not found) error in /var/log/Xorg.0.log, too. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-331-updates in Ubuntu. https://bugs.launchpad.net/bugs/1262539 Title: Driver for NVIDIA GF117M (GT620M) [10de:1140] Status in Jockey driver manager: New Status in “nvidia-graphics-drivers-331” package in Ubuntu: Confirmed Status in “nvidia-graphics-drivers-331-updates” package in Ubuntu: New Bug description: CID: 201307-14032 Dell Latitude E5540 According to http://www.nvidia.com/object/linux-display-amd64-319.32-driver.html The video card on this system: 03:00.0 3D controller [0302]: NVIDIA Corporation GF117M [GeForce 610M/710M / GT 620M/625M/630M/720M] [10de:1140] (rev a1) Should be suported by nvidia-319.32, however, the driver was not listed in jockey-gtk unless you install nvidia-319 manually Also, there is no option for turn on/off optimus mode in BIOS. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: nvidia-319 319.32-0ubuntu0.0.1 ProcVersionSignature: Ubuntu 3.8.0-34.49~precise1-generic 3.8.13.12 Uname: Linux 3.8.0-34-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.0.1-0ubuntu17.6 Architecture: amd64 Date: Thu Dec 19 15:36:15 2013 InstallationMedia: Ubuntu 12.04.3 LTS Precise Pangolin - Release amd64 (20130820.1) MarkForUpload: True ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: nvidia-graphics-drivers-319 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/jockey/+bug/1262539/+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 1092509] Re: Can't open photo while record a video then switch to take a photo and take one shot
This is a known issue. The public bug can be found in https://bugs.launchpad.net/ubuntu/+source/cheese/+bug/1092509 Thanks. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cheese in Ubuntu. https://bugs.launchpad.net/bugs/1092509 Title: Can't open photo while record a video then switch to take a photo and take one shot Status in “cheese” package in Ubuntu: New Bug description: Steps to reproduce: 1. Launch Cheese 2. Switch to Video and click take a video to recording 3. Click stop button 4. Click take a video again 5. Click stop 6. Switch back to photo 7. Click take a photo Expected Result: It should be able to open and view this photo Actual Result: 1. It has a photo on the preview column but it doesn't have thumb 2. Double click this photo but it can't be displayed ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: cheese 3.4.1-0ubuntu2.1 ProcVersionSignature: Ubuntu 3.2.0-35.55-generic 3.2.34 Uname: Linux 3.2.0-35-generic x86_64 NonfreeKernelModules: fglrx ApportVersion: 2.0.1-0ubuntu13 Architecture: amd64 Date: Thu Dec 20 05:48:48 2012 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-stella-kyoto-precise-amd64-20121102-0 InstallationMedia: Ubuntu 12.04 Precise - Build amd64 LIVE Binary 20121102-07:42 MachineType: Hewlett-Packard CQ1-3116LA ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash RelatedPackageVersions: cheese3.4.1-0ubuntu2.1 cheese-common 3.4.1-0ubuntu2.1 SourcePackage: cheese UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/16/2012 dmi.bios.vendor: AMI dmi.bios.version: Ay3_806 dmi.board.asset.tag: 5CM2200810 dmi.board.name: 2AF2 dmi.board.vendor: TPV-INVENTA dmi.board.version: A01 dmi.chassis.type: 3 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnAMI:bvrAy3_806:bd08/16/2012:svnHewlett-Packard:pnCQ1-3116LA:pvr:rvnTPV-INVENTA:rn2AF2:rvrA01:cvnHewlett-Packard:ct3:cvr: dmi.product.name: CQ1-3116LA dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cheese/+bug/1092509/+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 841030] Re: Gnome Disk utility error benchmarking
I have tried to benchmark different drive/media combination with the Disk Utility tool. And here is what I have found: 1. Internal DVD/CD drive - same too slow error (has fail rate, but it fails most of the time) 2. External USB DVD/CD drive - too slow error 3. External USB thumb drive - OK 4. External USB hard drive - OK 5. SD card in card reader - OK -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-disk-utility in Ubuntu. https://bugs.launchpad.net/bugs/841030 Title: Gnome Disk utility error benchmarking Status in “gnome-disk-utility” package in Ubuntu: Confirmed Bug description: While trying to benchmark an external USB drive with Start Read-Only Benchmark in benchmark dialog the following error is displayed: Error benchmarking: helper exited with exit code 1: Device /dev/sdd is too slow to benchmark This happens with any external USB storage on system. It does not matter if the drive is SD card, USB stick or HDD. I was searching for bug reports on this problem, but all I found was few forum posts. ProblemType: Bug DistroRelease: Ubuntu 11.04 Package: gnome-disk-utility 2.32.1-0ubuntu4 ProcVersionSignature: Ubuntu 2.6.38-11.48-generic 2.6.38.8 Uname: Linux 2.6.38-11-generic i686 Architecture: i386 Date: Sun Sep 4 16:39:25 2011 ExecutablePath: /usr/bin/palimpsest InstallationMedia: Ubuntu 9.10 Karmic Koala - Release i386 (20091028.5) ProcEnviron: LANGUAGE=en_US:en PATH=(custom, user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-disk-utility UpgradeStatus: Upgraded to natty on 2011-08-14 (21 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-disk-utility/+bug/841030/+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 1102770] [NEW] Voice type in preference settings in Orca Screen Reader does not take effect when applied.
Public bug reported: * The Voice Type Settings in Orca Screen Reader preferences does not take effect when applied. * In Orca Preferences - Voice - Voice Type Settings: Voice Type - select Uppercase, Hyperlink or System, then click Applied - The Voice type would always go back to Default value. ** Affects: gnome-orca (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-orca in Ubuntu. https://bugs.launchpad.net/bugs/1102770 Title: Voice type in preference settings in Orca Screen Reader does not take effect when applied. Status in “gnome-orca” package in Ubuntu: New Bug description: * The Voice Type Settings in Orca Screen Reader preferences does not take effect when applied. * In Orca Preferences - Voice - Voice Type Settings: Voice Type - select Uppercase, Hyperlink or System, then click Applied - The Voice type would always go back to Default value. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-orca/+bug/1102770/+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 1100683] [NEW] The Radioactive effect in 176*144 resolution behaves differently from other resolutions.
Public bug reported: * Ubuntu 12.04 LTS * Cheese v3.4.1 * Report: 1. Launch Cheese and select Radioactive in Effects. 2. In Preferences, change the resolution of Webcam to 176*144 3. The Radioactive effect in 176*144 behaves differently from other resolutions. Please see the attached screenshot for more information. ** Affects: cheese (Ubuntu) Importance: Undecided Status: New ** Attachment added: Radioactive effects in 176*144 https://bugs.launchpad.net/bugs/1100683/+attachment/3485930/+files/Screenshot%20from%202013-01-17%2003_58_03.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cheese in Ubuntu. https://bugs.launchpad.net/bugs/1100683 Title: The Radioactive effect in 176*144 resolution behaves differently from other resolutions. Status in “cheese” package in Ubuntu: New Bug description: * Ubuntu 12.04 LTS * Cheese v3.4.1 * Report: 1. Launch Cheese and select Radioactive in Effects. 2. In Preferences, change the resolution of Webcam to 176*144 3. The Radioactive effect in 176*144 behaves differently from other resolutions. Please see the attached screenshot for more information. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cheese/+bug/1100683/+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 1100683] Re: The Radioactive effect in 176*144 resolution behaves differently from other resolutions.
apport information ** Tags added: apport-collected precise running-unity ** Description changed: * Ubuntu 12.04 LTS * Cheese v3.4.1 * Report: 1. Launch Cheese and select Radioactive in Effects. 2. In Preferences, change the resolution of Webcam to 176*144 3. The Radioactive effect in 176*144 behaves differently from other resolutions. Please see the attached screenshot for more information. + --- + ApportVersion: 2.0.1-0ubuntu13 + Architecture: amd64 + DistributionChannelDescriptor: + # This is a distribution channel descriptor + # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor + canonical-oem-stella-kyoto-precise-amd64-20130114-0 + DistroRelease: Ubuntu 12.04 + InstallationMedia: Ubuntu 12.04 Precise - Build amd64 LIVE Binary 20130114-08:42 + MachineType: Hewlett-Packard DVT-ys002 + NonfreeKernelModules: fglrx + Package: cheese 3.4.1-0ubuntu2.1 + PackageArchitecture: amd64 + ProcEnviron: + LANGUAGE=en_US: + TERM=xterm + PATH=(custom, no user) + LANG=en_US.UTF-8 + SHELL=/bin/bash + ProcVersionSignature: Ubuntu 3.2.0-32.51-generic 3.2.30 + RelatedPackageVersions: + cheese3.4.1-0ubuntu2.1 + cheese-common 3.4.1-0ubuntu2.1 + Tags: precise running-unity + Uname: Linux 3.2.0-32-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo + dmi.bios.date: 01/07/2013 + dmi.bios.vendor: AMI + dmi.bios.version: 3.13H + dmi.board.asset.tag: 4CS247000Z + dmi.board.name: 2AF6 + dmi.board.vendor: Hewlett-Packard + dmi.board.version: 011 + dmi.chassis.type: 3 + dmi.chassis.vendor: Hewlett-Packard + dmi.modalias: dmi:bvnAMI:bvr3.13H:bd01/07/2013:svnHewlett-Packard:pnDVT-ys002:pvr:rvnHewlett-Packard:rn2AF6:rvr011:cvnHewlett-Packard:ct3:cvr: + dmi.product.name: DVT-ys002 + dmi.sys.vendor: Hewlett-Packard ** Attachment added: CheeseDebug.txt.gz https://bugs.launchpad.net/bugs/1100683/+attachment/3485980/+files/CheeseDebug.txt.gz -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cheese in Ubuntu. https://bugs.launchpad.net/bugs/1100683 Title: The Radioactive effect in 176*144 resolution behaves differently from other resolutions. Status in “cheese” package in Ubuntu: New Bug description: * Ubuntu 12.04 LTS * Cheese v3.4.1 * Report: 1. Launch Cheese and select Radioactive in Effects. 2. In Preferences, change the resolution of Webcam to 176*144 3. The Radioactive effect in 176*144 behaves differently from other resolutions. Please see the attached screenshot for more information. --- ApportVersion: 2.0.1-0ubuntu13 Architecture: amd64 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-stella-kyoto-precise-amd64-20130114-0 DistroRelease: Ubuntu 12.04 InstallationMedia: Ubuntu 12.04 Precise - Build amd64 LIVE Binary 20130114-08:42 MachineType: Hewlett-Packard DVT-ys002 NonfreeKernelModules: fglrx Package: cheese 3.4.1-0ubuntu2.1 PackageArchitecture: amd64 ProcEnviron: LANGUAGE=en_US: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 3.2.0-32.51-generic 3.2.30 RelatedPackageVersions: cheese3.4.1-0ubuntu2.1 cheese-common 3.4.1-0ubuntu2.1 Tags: precise running-unity Uname: Linux 3.2.0-32-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo dmi.bios.date: 01/07/2013 dmi.bios.vendor: AMI dmi.bios.version: 3.13H dmi.board.asset.tag: 4CS247000Z dmi.board.name: 2AF6 dmi.board.vendor: Hewlett-Packard dmi.board.version: 011 dmi.chassis.type: 3 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnAMI:bvr3.13H:bd01/07/2013:svnHewlett-Packard:pnDVT-ys002:pvr:rvnHewlett-Packard:rn2AF6:rvr011:cvnHewlett-Packard:ct3:cvr: dmi.product.name: DVT-ys002 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cheese/+bug/1100683/+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 1100683] Dependencies.txt
apport information ** Attachment added: Dependencies.txt https://bugs.launchpad.net/bugs/1100683/+attachment/3485981/+files/Dependencies.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cheese in Ubuntu. https://bugs.launchpad.net/bugs/1100683 Title: The Radioactive effect in 176*144 resolution behaves differently from other resolutions. Status in “cheese” package in Ubuntu: New Bug description: * Ubuntu 12.04 LTS * Cheese v3.4.1 * Report: 1. Launch Cheese and select Radioactive in Effects. 2. In Preferences, change the resolution of Webcam to 176*144 3. The Radioactive effect in 176*144 behaves differently from other resolutions. Please see the attached screenshot for more information. --- ApportVersion: 2.0.1-0ubuntu13 Architecture: amd64 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-stella-kyoto-precise-amd64-20130114-0 DistroRelease: Ubuntu 12.04 InstallationMedia: Ubuntu 12.04 Precise - Build amd64 LIVE Binary 20130114-08:42 MachineType: Hewlett-Packard DVT-ys002 NonfreeKernelModules: fglrx Package: cheese 3.4.1-0ubuntu2.1 PackageArchitecture: amd64 ProcEnviron: LANGUAGE=en_US: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 3.2.0-32.51-generic 3.2.30 RelatedPackageVersions: cheese3.4.1-0ubuntu2.1 cheese-common 3.4.1-0ubuntu2.1 Tags: precise running-unity Uname: Linux 3.2.0-32-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo dmi.bios.date: 01/07/2013 dmi.bios.vendor: AMI dmi.bios.version: 3.13H dmi.board.asset.tag: 4CS247000Z dmi.board.name: 2AF6 dmi.board.vendor: Hewlett-Packard dmi.board.version: 011 dmi.chassis.type: 3 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnAMI:bvr3.13H:bd01/07/2013:svnHewlett-Packard:pnDVT-ys002:pvr:rvnHewlett-Packard:rn2AF6:rvr011:cvnHewlett-Packard:ct3:cvr: dmi.product.name: DVT-ys002 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cheese/+bug/1100683/+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 1100683] lspci.txt
apport information ** Attachment added: lspci.txt https://bugs.launchpad.net/bugs/1100683/+attachment/3485983/+files/lspci.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cheese in Ubuntu. https://bugs.launchpad.net/bugs/1100683 Title: The Radioactive effect in 176*144 resolution behaves differently from other resolutions. Status in “cheese” package in Ubuntu: New Bug description: * Ubuntu 12.04 LTS * Cheese v3.4.1 * Report: 1. Launch Cheese and select Radioactive in Effects. 2. In Preferences, change the resolution of Webcam to 176*144 3. The Radioactive effect in 176*144 behaves differently from other resolutions. Please see the attached screenshot for more information. --- ApportVersion: 2.0.1-0ubuntu13 Architecture: amd64 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-stella-kyoto-precise-amd64-20130114-0 DistroRelease: Ubuntu 12.04 InstallationMedia: Ubuntu 12.04 Precise - Build amd64 LIVE Binary 20130114-08:42 MachineType: Hewlett-Packard DVT-ys002 NonfreeKernelModules: fglrx Package: cheese 3.4.1-0ubuntu2.1 PackageArchitecture: amd64 ProcEnviron: LANGUAGE=en_US: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 3.2.0-32.51-generic 3.2.30 RelatedPackageVersions: cheese3.4.1-0ubuntu2.1 cheese-common 3.4.1-0ubuntu2.1 Tags: precise running-unity Uname: Linux 3.2.0-32-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo dmi.bios.date: 01/07/2013 dmi.bios.vendor: AMI dmi.bios.version: 3.13H dmi.board.asset.tag: 4CS247000Z dmi.board.name: 2AF6 dmi.board.vendor: Hewlett-Packard dmi.board.version: 011 dmi.chassis.type: 3 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnAMI:bvr3.13H:bd01/07/2013:svnHewlett-Packard:pnDVT-ys002:pvr:rvnHewlett-Packard:rn2AF6:rvr011:cvnHewlett-Packard:ct3:cvr: dmi.product.name: DVT-ys002 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cheese/+bug/1100683/+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 1100683] lsusb.txt
apport information ** Attachment added: lsusb.txt https://bugs.launchpad.net/bugs/1100683/+attachment/3485984/+files/lsusb.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cheese in Ubuntu. https://bugs.launchpad.net/bugs/1100683 Title: The Radioactive effect in 176*144 resolution behaves differently from other resolutions. Status in “cheese” package in Ubuntu: New Bug description: * Ubuntu 12.04 LTS * Cheese v3.4.1 * Report: 1. Launch Cheese and select Radioactive in Effects. 2. In Preferences, change the resolution of Webcam to 176*144 3. The Radioactive effect in 176*144 behaves differently from other resolutions. Please see the attached screenshot for more information. --- ApportVersion: 2.0.1-0ubuntu13 Architecture: amd64 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-stella-kyoto-precise-amd64-20130114-0 DistroRelease: Ubuntu 12.04 InstallationMedia: Ubuntu 12.04 Precise - Build amd64 LIVE Binary 20130114-08:42 MachineType: Hewlett-Packard DVT-ys002 NonfreeKernelModules: fglrx Package: cheese 3.4.1-0ubuntu2.1 PackageArchitecture: amd64 ProcEnviron: LANGUAGE=en_US: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 3.2.0-32.51-generic 3.2.30 RelatedPackageVersions: cheese3.4.1-0ubuntu2.1 cheese-common 3.4.1-0ubuntu2.1 Tags: precise running-unity Uname: Linux 3.2.0-32-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo dmi.bios.date: 01/07/2013 dmi.bios.vendor: AMI dmi.bios.version: 3.13H dmi.board.asset.tag: 4CS247000Z dmi.board.name: 2AF6 dmi.board.vendor: Hewlett-Packard dmi.board.version: 011 dmi.chassis.type: 3 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnAMI:bvr3.13H:bd01/07/2013:svnHewlett-Packard:pnDVT-ys002:pvr:rvnHewlett-Packard:rn2AF6:rvr011:cvnHewlett-Packard:ct3:cvr: dmi.product.name: DVT-ys002 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cheese/+bug/1100683/+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 1100683] ProcCpuinfo.txt
apport information ** Attachment added: ProcCpuinfo.txt https://bugs.launchpad.net/bugs/1100683/+attachment/3485982/+files/ProcCpuinfo.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cheese in Ubuntu. https://bugs.launchpad.net/bugs/1100683 Title: The Radioactive effect in 176*144 resolution behaves differently from other resolutions. Status in “cheese” package in Ubuntu: New Bug description: * Ubuntu 12.04 LTS * Cheese v3.4.1 * Report: 1. Launch Cheese and select Radioactive in Effects. 2. In Preferences, change the resolution of Webcam to 176*144 3. The Radioactive effect in 176*144 behaves differently from other resolutions. Please see the attached screenshot for more information. --- ApportVersion: 2.0.1-0ubuntu13 Architecture: amd64 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-stella-kyoto-precise-amd64-20130114-0 DistroRelease: Ubuntu 12.04 InstallationMedia: Ubuntu 12.04 Precise - Build amd64 LIVE Binary 20130114-08:42 MachineType: Hewlett-Packard DVT-ys002 NonfreeKernelModules: fglrx Package: cheese 3.4.1-0ubuntu2.1 PackageArchitecture: amd64 ProcEnviron: LANGUAGE=en_US: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 3.2.0-32.51-generic 3.2.30 RelatedPackageVersions: cheese3.4.1-0ubuntu2.1 cheese-common 3.4.1-0ubuntu2.1 Tags: precise running-unity Uname: Linux 3.2.0-32-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo dmi.bios.date: 01/07/2013 dmi.bios.vendor: AMI dmi.bios.version: 3.13H dmi.board.asset.tag: 4CS247000Z dmi.board.name: 2AF6 dmi.board.vendor: Hewlett-Packard dmi.board.version: 011 dmi.chassis.type: 3 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnAMI:bvr3.13H:bd01/07/2013:svnHewlett-Packard:pnDVT-ys002:pvr:rvnHewlett-Packard:rn2AF6:rvr011:cvnHewlett-Packard:ct3:cvr: dmi.product.name: DVT-ys002 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cheese/+bug/1100683/+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 1098432] [NEW] Shaky display when playing back DVD movies
Public bug reported: [System Info] Mainboard:Guilin AMD A75 CPU:AMD A8-5500 APU with Radeon(tm) HD Graphics ( 3.2GHz ) RAM: Samsung-4G*2 M471B5273DH0-YK0 IGPU:AMD Radeon (TM)HD 8670A DGPU: AMD Radeon HD 7560D Audio:Realtek High Definition Audio LCD Panel: LG LM230WF5-TLF2 NIC:Realtek PCIe FE Family Controller Wireless:Broadcom High Performace Wlan Module Bluetooth:Broadcom Combo Storage Controller:Microsoft Storage Spaces Controller HDD :Seagate 2TB ST2000DM001(FW: HP31) ODD: HLDS BD CT41N(S05NT)(FW:C503) OS Flavor/Revision:Ubuntu 64bit [Steps to reproduce the issue] 1.Boot into Ubuntu 12.04 2. Install required packaging for DVD playback: sudo apt-get install ubuntu-restricted-extras 3.Plug in a DVD movie using Totem 4.Find that playing screen will shake. Please see the attached video for more details. Thank you for your attention. ** Affects: totem (Ubuntu) Importance: Undecided Status: New -- 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/1098432 Title: Shaky display when playing back DVD movies Status in “totem” package in Ubuntu: New Bug description: [System Info] Mainboard:Guilin AMD A75 CPU:AMD A8-5500 APU with Radeon(tm) HD Graphics ( 3.2GHz ) RAM: Samsung-4G*2 M471B5273DH0-YK0 IGPU:AMD Radeon (TM)HD 8670A DGPU: AMD Radeon HD 7560D Audio:Realtek High Definition Audio LCD Panel: LG LM230WF5-TLF2 NIC:Realtek PCIe FE Family Controller Wireless:Broadcom High Performace Wlan Module Bluetooth:Broadcom Combo Storage Controller:Microsoft Storage Spaces Controller HDD :Seagate 2TB ST2000DM001(FW: HP31) ODD: HLDS BD CT41N(S05NT)(FW:C503) OS Flavor/Revision:Ubuntu 64bit [Steps to reproduce the issue] 1.Boot into Ubuntu 12.04 2. Install required packaging for DVD playback: sudo apt-get install ubuntu-restricted-extras 3.Plug in a DVD movie using Totem 4.Find that playing screen will shake. Please see the attached video for more details. Thank you for your attention. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/totem/+bug/1098432/+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 1098432] Re: Shaky display when playing back DVD movies
** Attachment added: video-shaking.MTS https://bugs.launchpad.net/ubuntu/+source/totem/+bug/1098432/+attachment/3479919/+files/video-shaking.MTS -- 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/1098432 Title: Shaky display when playing back DVD movies Status in “totem” package in Ubuntu: New Bug description: [System Info] Mainboard:Guilin AMD A75 CPU:AMD A8-5500 APU with Radeon(tm) HD Graphics ( 3.2GHz ) RAM: Samsung-4G*2 M471B5273DH0-YK0 IGPU:AMD Radeon (TM)HD 8670A DGPU: AMD Radeon HD 7560D Audio:Realtek High Definition Audio LCD Panel: LG LM230WF5-TLF2 NIC:Realtek PCIe FE Family Controller Wireless:Broadcom High Performace Wlan Module Bluetooth:Broadcom Combo Storage Controller:Microsoft Storage Spaces Controller HDD :Seagate 2TB ST2000DM001(FW: HP31) ODD: HLDS BD CT41N(S05NT)(FW:C503) OS Flavor/Revision:Ubuntu 64bit [Steps to reproduce the issue] 1.Boot into Ubuntu 12.04 2. Install required packaging for DVD playback: sudo apt-get install ubuntu-restricted-extras 3.Plug in a DVD movie using Totem 4.Find that playing screen will shake. Please see the attached video for more details. Thank you for your attention. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/totem/+bug/1098432/+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 1057890] [NEW] System allows the only Administrator account to be disabled
Public bug reported: Steps to reproduce this issue: 1. Go to System Settings - User Accounts and notice only one Administrator account exists 2. Unlock making changes to User accounts, go to Login Options and click on Password. 3. In the Action list, select Disable this Account and commit the change. And the system ends up with no Administrator account. ** Affects: gnome-control-center (Ubuntu) Importance: Undecided Status: New -- 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/1057890 Title: System allows the only Administrator account to be disabled Status in “gnome-control-center” package in Ubuntu: New Bug description: Steps to reproduce this issue: 1. Go to System Settings - User Accounts and notice only one Administrator account exists 2. Unlock making changes to User accounts, go to Login Options and click on Password. 3. In the Action list, select Disable this Account and commit the change. And the system ends up with no Administrator account. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1057890/+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 962860] [NEW] The prompt for installing MP3 playback support dialogue box does not fit in a 1024x600 display
Public bug reported: * Ubuntu Release: 12.04 Beta1 * Steps to reproduce it: 1. Click on link to Ubuntu One music store 2. Click on any album link to open up its play list 3. Try to trial play any of the songs in the list Please see the attached screen shots for more information. ** Affects: rhythmbox (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to rhythmbox in Ubuntu. https://bugs.launchpad.net/bugs/962860 Title: The prompt for installing MP3 playback support dialogue box does not fit in a 1024x600 display Status in “rhythmbox” package in Ubuntu: New Bug description: * Ubuntu Release: 12.04 Beta1 * Steps to reproduce it: 1. Click on link to Ubuntu One music store 2. Click on any album link to open up its play list 3. Try to trial play any of the songs in the list Please see the attached screen shots for more information. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/962860/+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 962860] Re: The prompt for installing MP3 playback support dialogue box does not fit in a 1024x600 display
** Attachment added: Screenshot rhythmbox with launcher.png https://bugs.launchpad.net/bugs/962860/+attachment/2920693/+files/Screenshot%20rhythmbox%20with%20launcher.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to rhythmbox in Ubuntu. https://bugs.launchpad.net/bugs/962860 Title: The prompt for installing MP3 playback support dialogue box does not fit in a 1024x600 display Status in “rhythmbox” package in Ubuntu: New Bug description: * Ubuntu Release: 12.04 Beta1 * Steps to reproduce it: 1. Click on link to Ubuntu One music store 2. Click on any album link to open up its play list 3. Try to trial play any of the songs in the list Please see the attached screen shots for more information. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/962860/+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 893851] Re: Brightness adjustment gauge in gnome-control-center screen not responding to brightness hot-keys
Basically, this issue is about the Brightness bar in the Screen utility (please see the attached image) not reflecting the actual screen brightness in real time. ** Attachment added: Screenshot at 2011-12-20 14:31:20.png https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/893851/+attachment/2640824/+files/Screenshot%20at%202011-12-20%2014%3A31%3A20.png -- 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/893851 Title: Brightness adjustment gauge in gnome-control-center screen not responding to brightness hot-keys Status in OEM Priority Project: Incomplete Status in “gnome-control-center” package in Ubuntu: Incomplete Bug description: For systems equipped with hot keys to adjust screen brightness, the brightness gauge in gnome-control-center screen is not responding to brightness hot-key actions. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/893851/+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 893851] [NEW] Brightness adjustment gauge in gnome-control-center screen not responding to brightness hot-keys
Public bug reported: For systems equipped with hot keys to adjust screen brightness, the brightness gauge in gnome-control-center screen is not responding to brightness hot-key actions. ** Affects: gnome-control-center (Ubuntu) Importance: Undecided Status: New -- 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/893851 Title: Brightness adjustment gauge in gnome-control-center screen not responding to brightness hot-keys Status in “gnome-control-center” package in Ubuntu: New Bug description: For systems equipped with hot keys to adjust screen brightness, the brightness gauge in gnome-control-center screen is not responding to brightness hot-key actions. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/893851/+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
