[Desktop-packages] [Bug 1970291] Re: [nvidia] Secondary monitor performance is slow on an Nvidia hybrid system in Wayland sessions
hope this one merges soon -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1970291 Title: [nvidia] Secondary monitor performance is slow on an Nvidia hybrid system in Wayland sessions Status in GNOME Shell: New Status in Mutter: Fix Released Status in mutter package in Ubuntu: In Progress Bug description: In session with Wayland the Nvidia driver settings do not load. And there is a sluggishness when opening apps, show applications menu, maximize, changing workspace, resize, changing monitor windows etc. When in an Xorg session the Nvidia settings load correctly and the performance is satisfactory. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Uname: Linux 5.15.0-27-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 510.60.02 Wed Mar 16 11:24:05 UTC 2022 GCC version: ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Apr 25 21:18:08 2022 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation CoffeeLake-H GT2 [UHD Graphics 630] [8086:3e9b] (prog-if 00 [VGA controller]) Subsystem: Intel Corporation CoffeeLake-H GT2 [UHD Graphics 630] [8086:2086] NVIDIA Corporation TU116M [GeForce GTX 1660 Ti Mobile] [10de:2191] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Intel Corporation TU116M [GeForce GTX 1660 Ti Mobile] [8086:2086] InstallationDate: Installed on 2022-04-24 (1 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Beta amd64 (20220329.1) MachineType: Avell High Performance A60 MUV ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-27-generic root=UUID=894cb598-7172-481c-a449-3133b8f226e5 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/11/2020 dmi.bios.release: 5.13 dmi.bios.vendor: Intel Corp. dmi.bios.version: QCCFL357.0122.2020.0911.1520 dmi.board.name: Avell High Performance dmi.board.vendor: Avell High Performance dmi.chassis.type: 10 dmi.chassis.vendor: Avell High Performance dmi.chassis.version: 1.0 dmi.ec.firmware.release: 1.25 dmi.modalias: dmi:bvnIntelCorp.:bvrQCCFL357.0122.2020.0911.1520:bd09/11/2020:br5.13:efr1.25:svnAvellHighPerformance:pnA60MUV:pvr:rvnAvellHighPerformance:rnAvellHighPerformance:rvr:cvnAvellHighPerformance:ct10:cvr1.0:skuA60MUV: dmi.product.family: A60 MUV dmi.product.name: A60 MUV dmi.product.sku: A60 MUV dmi.sys.vendor: Avell High Performance version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.110-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.1-1ubuntu2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1970291/+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 2022879] Re: No sound from Woofer speaker of Asus Zephyrus G14 2023
They did not. To my understanding, one that case, the sound are coming off both the tweeter and bass speakers, but the master volume control does not lower the bass speaker volume, so it's a different problem than what we are facing -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/2022879 Title: No sound from Woofer speaker of Asus Zephyrus G14 2023 Status in alsa-driver package in Ubuntu: New Status in pipewire package in Ubuntu: New Bug description: On Asus Zephyrus G14 2023, sound only comes out of the pair of tweeter speaker. The woofer speaker does not produce any sound at all on either on Analog Stereo, Analog Surround 4.0, or 2.1 configurations 1) ┌─[surfer@M5-RGV]-[~] └──╼ $lsb_release -rd No LSB modules are available. Description: Ubuntu 23.04 Release: 23.04 ) 2) ┌─[surfer@M5-RGV]-[~] └──╼ $apt-cache policy pipewire pipewire: Installed: 0.3.65-3 Candidate: 0.3.65-3 Version table: *** 0.3.65-3 500 500 http://id.archive.ubuntu.com/ubuntu lunar/main amd64 Packages 100 /var/lib/dpkg/status 3) The Woofer/rear speaker should produce sound 4) Sound only comes from the pair of tweeter speaker ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: pipewire 0.3.65-3 Uname: Linux 6.3.5-060305-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: GNOME Date: Mon Jun 5 12:33:02 2023 InstallationDate: Installed on 2023-05-31 (4 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= SourcePackage: pipewire UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/2022879/+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 2022881] [NEW] No sound from Woofer speaker of Asus Zephyrus G14 2023
Public bug reported: On Asus Zephyrus G14 2023, sound only comes out of the pair of tweeter speaker. The woofer speaker does not produce any sound at all on either on Analog Stereo, Analog Surround 4.0, or 2.1 configurations 1) ┌─[surfer@M5-RGV]-[~] └──╼ $lsb_release -rd No LSB modules are available. Description: Ubuntu 23.04 Release: 23.04 ) 2) ┌─[surfer@M5-RGV]-[~] └──╼ $apt-cache policy pipewire pipewire: Installed: 0.3.65-3 Candidate: 0.3.65-3 Version table: *** 0.3.65-3 500 500 http://id.archive.ubuntu.com/ubuntu lunar/main amd64 Packages 100 /var/lib/dpkg/status 3) The Woofer/rear speaker should produce sound 4) Sound only comes from the pair of tweeter speaker ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: alsa-base 1.0.25+dfsg-0ubuntu7 Uname: Linux 6.3.5-060305-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: surfer12877 F wireplumber /dev/snd/controlC1: surfer12877 F wireplumber /dev/snd/controlC0: surfer12877 F wireplumber /dev/snd/seq:surfer12875 F pipewire CasperMD5CheckResult: pass CurrentDesktop: GNOME Date: Mon Jun 5 12:47:29 2023 InstallationDate: Installed on 2023-05-31 (4 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418) PackageArchitecture: all ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: alsa-driver Symptom: audio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/23/2023 dmi.bios.release: 5.29 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: GA402XV.301 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: GA402XV dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.ec.firmware.release: 0.39 dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrGA402XV.301:bd03/23/2023:br5.29:efr0.39:svnASUSTeKCOMPUTERINC.:pnROGZephyrusG14GA402XV_GA402XV:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnGA402XV:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:sku: dmi.product.family: "ROG Zephyrus G14" dmi.product.name: ROG Zephyrus G14 GA402XV_GA402XV dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug lunar wayland-session -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/2022881 Title: No sound from Woofer speaker of Asus Zephyrus G14 2023 Status in alsa-driver package in Ubuntu: New Bug description: On Asus Zephyrus G14 2023, sound only comes out of the pair of tweeter speaker. The woofer speaker does not produce any sound at all on either on Analog Stereo, Analog Surround 4.0, or 2.1 configurations 1) ┌─[surfer@M5-RGV]-[~] └──╼ $lsb_release -rd No LSB modules are available. Description: Ubuntu 23.04 Release: 23.04 ) 2) ┌─[surfer@M5-RGV]-[~] └──╼ $apt-cache policy pipewire pipewire: Installed: 0.3.65-3 Candidate: 0.3.65-3 Version table: *** 0.3.65-3 500 500 http://id.archive.ubuntu.com/ubuntu lunar/main amd64 Packages 100 /var/lib/dpkg/status 3) The Woofer/rear speaker should produce sound 4) Sound only comes from the pair of tweeter speaker ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: alsa-base 1.0.25+dfsg-0ubuntu7 Uname: Linux 6.3.5-060305-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: surfer12877 F wireplumber /dev/snd/controlC1: surfer12877 F wireplumber /dev/snd/controlC0: surfer12877 F wireplumber /dev/snd/seq:surfer12875 F pipewire CasperMD5CheckResult: pass CurrentDesktop: GNOME Date: Mon Jun 5 12:47:29 2023 InstallationDate: Installed on 2023-05-31 (4 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418) PackageArchitecture: all ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: alsa-driver Symptom: audio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/23/2023 dmi.bios.release: 5.29 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: GA402XV.301 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: GA402XV dmi.board.vendor:
[Desktop-packages] [Bug 2022880] [NEW] No sound from Woofer speaker of Asus Zephyrus G14 2023
Public bug reported: On Asus Zephyrus G14 2023, sound only comes out of the pair of tweeter speaker. The woofer speaker does not produce any sound at all on either on Analog Stereo, Analog Surround 4.0, or 2.1 configurations ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: alsa-base 1.0.25+dfsg-0ubuntu7 Uname: Linux 6.3.5-060305-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: surfer12877 F wireplumber /dev/snd/controlC1: surfer12877 F wireplumber /dev/snd/controlC0: surfer12877 F wireplumber /dev/snd/seq:surfer12875 F pipewire CasperMD5CheckResult: pass CurrentDesktop: GNOME Date: Mon Jun 5 12:47:29 2023 InstallationDate: Installed on 2023-05-31 (4 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418) PackageArchitecture: all ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: alsa-driver Symptom: audio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/23/2023 dmi.bios.release: 5.29 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: GA402XV.301 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: GA402XV dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.ec.firmware.release: 0.39 dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrGA402XV.301:bd03/23/2023:br5.29:efr0.39:svnASUSTeKCOMPUTERINC.:pnROGZephyrusG14GA402XV_GA402XV:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnGA402XV:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:sku: dmi.product.family: "ROG Zephyrus G14" dmi.product.name: ROG Zephyrus G14 GA402XV_GA402XV dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug lunar wayland-session -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/2022880 Title: No sound from Woofer speaker of Asus Zephyrus G14 2023 Status in alsa-driver package in Ubuntu: New Bug description: On Asus Zephyrus G14 2023, sound only comes out of the pair of tweeter speaker. The woofer speaker does not produce any sound at all on either on Analog Stereo, Analog Surround 4.0, or 2.1 configurations ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: alsa-base 1.0.25+dfsg-0ubuntu7 Uname: Linux 6.3.5-060305-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: surfer12877 F wireplumber /dev/snd/controlC1: surfer12877 F wireplumber /dev/snd/controlC0: surfer12877 F wireplumber /dev/snd/seq:surfer12875 F pipewire CasperMD5CheckResult: pass CurrentDesktop: GNOME Date: Mon Jun 5 12:47:29 2023 InstallationDate: Installed on 2023-05-31 (4 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418) PackageArchitecture: all ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: alsa-driver Symptom: audio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/23/2023 dmi.bios.release: 5.29 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: GA402XV.301 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: GA402XV dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.ec.firmware.release: 0.39 dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrGA402XV.301:bd03/23/2023:br5.29:efr0.39:svnASUSTeKCOMPUTERINC.:pnROGZephyrusG14GA402XV_GA402XV:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnGA402XV:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:sku: dmi.product.family: "ROG Zephyrus G14" dmi.product.name: ROG Zephyrus G14 GA402XV_GA402XV dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/2022880/+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 2022879] [NEW] No sound from Woofer speaker of Asus Zephyrus G14 2023
Public bug reported: On Asus Zephyrus G14 2023, sound only comes out of the pair of tweeter speaker. The woofer speaker does not produce any sound at all on either on Analog Stereo, Analog Surround 4.0, or 2.1 configurations 1) ┌─[surfer@M5-RGV]-[~] └──╼ $lsb_release -rd No LSB modules are available. Description:Ubuntu 23.04 Release:23.04 ) 2) ┌─[surfer@M5-RGV]-[~] └──╼ $apt-cache policy pipewire pipewire: Installed: 0.3.65-3 Candidate: 0.3.65-3 Version table: *** 0.3.65-3 500 500 http://id.archive.ubuntu.com/ubuntu lunar/main amd64 Packages 100 /var/lib/dpkg/status 3) The Woofer/rear speaker should produce sound 4) Sound only comes from the pair of tweeter speaker ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: pipewire 0.3.65-3 Uname: Linux 6.3.5-060305-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: GNOME Date: Mon Jun 5 12:33:02 2023 InstallationDate: Installed on 2023-05-31 (4 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= SourcePackage: pipewire UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: pipewire (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug lunar wayland-session -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pipewire in Ubuntu. https://bugs.launchpad.net/bugs/2022879 Title: No sound from Woofer speaker of Asus Zephyrus G14 2023 Status in pipewire package in Ubuntu: New Bug description: On Asus Zephyrus G14 2023, sound only comes out of the pair of tweeter speaker. The woofer speaker does not produce any sound at all on either on Analog Stereo, Analog Surround 4.0, or 2.1 configurations 1) ┌─[surfer@M5-RGV]-[~] └──╼ $lsb_release -rd No LSB modules are available. Description: Ubuntu 23.04 Release: 23.04 ) 2) ┌─[surfer@M5-RGV]-[~] └──╼ $apt-cache policy pipewire pipewire: Installed: 0.3.65-3 Candidate: 0.3.65-3 Version table: *** 0.3.65-3 500 500 http://id.archive.ubuntu.com/ubuntu lunar/main amd64 Packages 100 /var/lib/dpkg/status 3) The Woofer/rear speaker should produce sound 4) Sound only comes from the pair of tweeter speaker ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: pipewire 0.3.65-3 Uname: Linux 6.3.5-060305-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: GNOME Date: Mon Jun 5 12:33:02 2023 InstallationDate: Installed on 2023-05-31 (4 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= SourcePackage: pipewire UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pipewire/+bug/2022879/+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 1958839] [NEW] mouse not working
Public bug reported: Hi I got a Redragon M808-KS WIRED & WIRELESS mouse and it is working fine in windows. But, when I switch to Ubuntu it is not working and the strange part is the mouse is plug and play type and does not need any particular driver. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.13.0-27.29~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-27-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 470.86 Tue Oct 26 21:55:45 UTC 2021 GCC version: gcc version 9.3.0 (Ubuntu 9.3.0-17ubuntu1~20.04) ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Jan 24 11:47:42 2022 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: nvidia, 470.86, 5.11.0-41-generic, x86_64: installed nvidia, 470.86, 5.13.0-27-generic, x86_64: installed GraphicsCard: Intel Corporation 4th Gen Core Processor Integrated Graphics Controller [8086:0416] (rev 06) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. 4th Gen Core Processor Integrated Graphics Controller [1043:11cd] Subsystem: ASUSTeK Computer Inc. GM107M [GeForce GTX 850M] [1043:11cd] InstallationDate: Installed on 2021-10-21 (94 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) MachineType: ASUSTeK COMPUTER INC. N550JK ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-27-generic root=UUID=01a2cb99-7964-4a0b-a8f4-2b16aa8fdd89 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/23/2014 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: N550JK.204 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: N550JK dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrN550JK.204:bd01/23/2014:br4.6:svnASUSTeKCOMPUTERINC.:pnN550JK:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnN550JK:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:skuASUS-NotebookSKU: dmi.product.family: N dmi.product.name: N550JK dmi.product.sku: ASUS-NotebookSKU dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.105-3~20.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.3-0ubuntu0.3~20.04.5 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1~20.04.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ubuntu -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1958839 Title: mouse not working Status in xorg package in Ubuntu: New Bug description: Hi I got a Redragon M808-KS WIRED & WIRELESS mouse and it is working fine in windows. But, when I switch to Ubuntu it is not working and the strange part is the mouse is plug and play type and does not need any particular driver. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.13.0-27.29~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-27-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 470.86 Tue Oct 26 21:55:45 UTC 2021 GCC version: gcc version 9.3.0 (Ubuntu 9.3.0-17ubuntu1~20.04) ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 BootLog: Error:
[Desktop-packages] [Bug 1891270] Re: Iranian calendar shows in Azerbaijani language
Same here -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-calendar in Ubuntu. https://bugs.launchpad.net/bugs/1891270 Title: Iranian calendar shows in Azerbaijani language Status in gnome-calendar package in Ubuntu: Invalid Status in ubiquity package in Ubuntu: Confirmed Bug description: I already installed Ubuntu 20.04.1 LTS and set location on Iran during installation. After finishing installation successfully, I open the calendar by clicking at the top of the screen (where the clock is shown), I see the calendar with Azerbaijani names for month and weekdays. Such as "آقوست" for August and "جومعه آخشامی" for Thursday. But it should show in Iranian names such as "اوت" for August and "پنجشنبه" for Thursday. Description: Ubuntu 20.04.1 LTS Release: 20.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-calendar/+bug/1891270/+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 1891270] Re: Iranian calendar shows in Azerbaijani language
I have this problem too! -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-calendar in Ubuntu. https://bugs.launchpad.net/bugs/1891270 Title: Iranian calendar shows in Azerbaijani language Status in gnome-calendar package in Ubuntu: Invalid Status in ubiquity package in Ubuntu: Confirmed Bug description: I already installed Ubuntu 20.04.1 LTS and set location on Iran during installation. After finishing installation successfully, I open the calendar by clicking at the top of the screen (where the clock is shown), I see the calendar with Azerbaijani names for month and weekdays. Such as "آقوست" for August and "جومعه آخشامی" for Thursday. But it should show in Iranian names such as "اوت" for August and "پنجشنبه" for Thursday. Description: Ubuntu 20.04.1 LTS Release: 20.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-calendar/+bug/1891270/+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 1904568] [NEW] Noise on screen while using
Public bug reported: When I'm using my laptop, I sometimes see some noises on screen. they're mostly horizontal noise lines in panels (but sometimes on other parts). I attached a picture of the problem. I use Kubuntu 20.10. The problem is present when I connect my laptop to external screen (so it's not monitor's problem). ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: xorg 1:7.7+19ubuntu15 ProcVersionSignature: Ubuntu 5.8.0-28.30-generic 5.8.14 Uname: Linux 5.8.0-28-generic x86_64 ApportVersion: 2.20.11-0ubuntu50.1 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: KDE Date: Tue Nov 17 16:30:07 2020 DistUpgraded: 2020-11-08 22:54:50,746 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: groovy DistroVariant: ubuntu ExtraDebuggingInterest: No GraphicsCard: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. UHD Graphics 620 [1043:1131] Subsystem: ASUSTeK Computer Inc. GM108M [GeForce MX130] [1043:1131] InstallationDate: Installed on 2020-10-02 (45 days ago) InstallationMedia: Kubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: ASUSTeK COMPUTER INC. VivoBook S15 X510UF ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-28-generic root=UUID=2dccc476-4ac0-4ab2-9742-bde2ad020de3 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to groovy on 2020-11-08 (8 days ago) dmi.bios.date: 09/06/2019 dmi.bios.release: 5.12 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X510UF.304 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X510UF dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrX510UF.304:bd09/06/2019:br5.12:svnASUSTeKCOMPUTERINC.:pnVivoBookS15X510UF:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX510UF:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: VivoBook S dmi.product.name: VivoBook S15 X510UF dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.1-1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug groovy ubuntu ** Attachment added: "A picture of the problem" https://bugs.launchpad.net/bugs/1904568/+attachment/5435141/+files/P_20201117_163314_002.jpg -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1904568 Title: Noise on screen while using Status in xorg package in Ubuntu: New Bug description: When I'm using my laptop, I sometimes see some noises on screen. they're mostly horizontal noise lines in panels (but sometimes on other parts). I attached a picture of the problem. I use Kubuntu 20.10. The problem is present when I connect my laptop to external screen (so it's not monitor's problem). ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: xorg 1:7.7+19ubuntu15 ProcVersionSignature: Ubuntu 5.8.0-28.30-generic 5.8.14 Uname: Linux 5.8.0-28-generic x86_64 ApportVersion: 2.20.11-0ubuntu50.1 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: KDE Date: Tue Nov 17 16:30:07 2020 DistUpgraded: 2020-11-08 22:54:50,746 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: groovy DistroVariant: ubuntu ExtraDebuggingInterest: No GraphicsCard: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. UHD Graphics 620 [1043:1131] Subsystem: ASUSTeK Computer Inc. GM108M [GeForce MX130] [1043:1131] InstallationDate: Installed on 2020-10-02 (45 days ago) InstallationMedia: Kubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: ASUSTeK COMPUTER INC. VivoBook S15 X510UF ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-28-generic root=UUID=2dccc476-4ac0-4ab2-9742-bde2ad020de3 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to groovy on 2020-11-08 (8 days ago) dmi.bios.date: 09/06/2019 dmi.bios.release: 5.12 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version:
[Desktop-packages] [Bug 1281588] Re: Disk standby timer is broken
I'm experiencing this bug on Ubuntu 20.04.1 It seems something is trying to access my disk, exactly every 10 minutes. I reported it as a new bug +bug 1899361 -- 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/1281588 Title: Disk standby timer is broken Status in udisks: Fix Released Status in udisks2 package in Ubuntu: Fix Released Status in udisks2 source package in Trusty: Confirmed Bug description: udisks' / gnome-disk-utility's support for the drive standby timer is broken. If the standby timer is set to at least 10 minutes ( which is the minimum on many drives ), every 10 minutes udisks tries to update the smart status of the drive, which resets the standby timer. To manage notifications about this bug go to: https://bugs.launchpad.net/udisks/+bug/1281588/+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 1899361] Re: udisk prevent disk from standby, standby timer is broken
I'm using smartmontools to check my drive every 30 minutes. It has an option to don't check if the drive is standby. Can't they at least do the same? And I had a question. Why does udisks checks smart data? Is it going to notify me if there's a problem, or ... ? P.S. My hard drive model number is TOSHIBA MQ04ABF100 -- 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/1899361 Title: udisk prevent disk from standby, standby timer is broken Status in udisks package in Ubuntu: Confirmed Status in udisks2 package in Ubuntu: Confirmed Bug description: It seems udisks tries to access my HDD every 10 minute. So when I set standby timer less than 10 minutes, It can't go to standby. Probably the disk shouldn't be checked when it's on standby. This bug has been reported before (+bug #1281588) and seems to be fixed, But I'm experiencing this again. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: udisks2 2.8.4-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60 Uname: Linux 5.4.0-48-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.9 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE CustomUdevRuleFiles: wolfram-vernierlink-libusb.rules Date: Sun Oct 11 19:38:48 2020 InstallationDate: Installed on 2020-10-02 (8 days ago) InstallationMedia: Kubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: ASUSTeK COMPUTER INC. VivoBook S15 X510UF ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-48-generic root=UUID=2dccc476-4ac0-4ab2-9742-bde2ad020de3 ro quiet splash vt.handoff=7 SourcePackage: udisks2 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/06/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X510UF.304 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X510UF dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrX510UF.304:bd09/06/2019:svnASUSTeKCOMPUTERINC.:pnVivoBookS15X510UF:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX510UF:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: VivoBook S dmi.product.name: VivoBook S15 X510UF dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/udisks/+bug/1899361/+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 1899361] Re: udisk prevent disk from standby, standby timer is broken
** Description changed: - It seems udisks tries to access my HDD every 10 minute. So when I set standby timer less than 10 minutes, It can't go to standby. - This bug has been reported before (+bug #1281588) and seems to be fixed, But I'm experiencing this again. + It seems udisks tries to access my HDD every 10 minute. So when I set standby timer less than 10 minutes, It can't go to standby. + Probably the disk shouldn't be checked when it's on standby. + + This bug has been reported before (+bug #1281588) and seems to be fixed, + But I'm experiencing this again. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: udisks2 2.8.4-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60 Uname: Linux 5.4.0-48-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.9 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE CustomUdevRuleFiles: wolfram-vernierlink-libusb.rules Date: Sun Oct 11 19:38:48 2020 InstallationDate: Installed on 2020-10-02 (8 days ago) InstallationMedia: Kubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: ASUSTeK COMPUTER INC. VivoBook S15 X510UF ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-48-generic root=UUID=2dccc476-4ac0-4ab2-9742-bde2ad020de3 ro quiet splash vt.handoff=7 SourcePackage: udisks2 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/06/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X510UF.304 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X510UF dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrX510UF.304:bd09/06/2019:svnASUSTeKCOMPUTERINC.:pnVivoBookS15X510UF:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX510UF:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: VivoBook S dmi.product.name: VivoBook S15 X510UF dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. -- 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/1899361 Title: udisk prevent disk from standby, standby timer is broken Status in udisks package in Ubuntu: Confirmed Status in udisks2 package in Ubuntu: Confirmed Bug description: It seems udisks tries to access my HDD every 10 minute. So when I set standby timer less than 10 minutes, It can't go to standby. Probably the disk shouldn't be checked when it's on standby. This bug has been reported before (+bug #1281588) and seems to be fixed, But I'm experiencing this again. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: udisks2 2.8.4-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60 Uname: Linux 5.4.0-48-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.9 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE CustomUdevRuleFiles: wolfram-vernierlink-libusb.rules Date: Sun Oct 11 19:38:48 2020 InstallationDate: Installed on 2020-10-02 (8 days ago) InstallationMedia: Kubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: ASUSTeK COMPUTER INC. VivoBook S15 X510UF ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-48-generic root=UUID=2dccc476-4ac0-4ab2-9742-bde2ad020de3 ro quiet splash vt.handoff=7 SourcePackage: udisks2 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/06/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X510UF.304 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X510UF dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrX510UF.304:bd09/06/2019:svnASUSTeKCOMPUTERINC.:pnVivoBookS15X510UF:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX510UF:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: VivoBook S dmi.product.name: VivoBook S15 X510UF dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/udisks/+bug/1899361/+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 1281588] Re: Disk standby timer is broken
I'm experiencing this bug on Ubuntu 20.04.1 It seems something is trying to access my disk, exactly every 10 minutes. I reported it as a new bug +bug/1899361 -- 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/1281588 Title: Disk standby timer is broken Status in udisks: Fix Released Status in udisks2 package in Ubuntu: Fix Released Status in udisks2 source package in Trusty: Confirmed Bug description: udisks' / gnome-disk-utility's support for the drive standby timer is broken. If the standby timer is set to at least 10 minutes ( which is the minimum on many drives ), every 10 minutes udisks tries to update the smart status of the drive, which resets the standby timer. To manage notifications about this bug go to: https://bugs.launchpad.net/udisks/+bug/1281588/+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 1899361] [NEW] udisk prevent disk from standby, standby timer is broken
Public bug reported: It seems udisks tries to access my HDD every 10 minute. So when I set standby timer less than 10 minutes, It can't go to standby. This bug has been reported before (+bug #1281588) and seems to be fixed, But I'm experiencing this again. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: udisks2 2.8.4-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60 Uname: Linux 5.4.0-48-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.9 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE CustomUdevRuleFiles: wolfram-vernierlink-libusb.rules Date: Sun Oct 11 19:38:48 2020 InstallationDate: Installed on 2020-10-02 (8 days ago) InstallationMedia: Kubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: ASUSTeK COMPUTER INC. VivoBook S15 X510UF ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-48-generic root=UUID=2dccc476-4ac0-4ab2-9742-bde2ad020de3 ro quiet splash vt.handoff=7 SourcePackage: udisks2 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/06/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X510UF.304 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X510UF dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrX510UF.304:bd09/06/2019:svnASUSTeKCOMPUTERINC.:pnVivoBookS15X510UF:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX510UF:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: VivoBook S dmi.product.name: VivoBook S15 X510UF dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. ** Affects: udisks (Ubuntu) Importance: Undecided Status: New ** Affects: udisks2 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ** Also affects: udisks (Ubuntu) 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/1899361 Title: udisk prevent disk from standby, standby timer is broken Status in udisks package in Ubuntu: New Status in udisks2 package in Ubuntu: New Bug description: It seems udisks tries to access my HDD every 10 minute. So when I set standby timer less than 10 minutes, It can't go to standby. This bug has been reported before (+bug #1281588) and seems to be fixed, But I'm experiencing this again. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: udisks2 2.8.4-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60 Uname: Linux 5.4.0-48-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.9 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE CustomUdevRuleFiles: wolfram-vernierlink-libusb.rules Date: Sun Oct 11 19:38:48 2020 InstallationDate: Installed on 2020-10-02 (8 days ago) InstallationMedia: Kubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: ASUSTeK COMPUTER INC. VivoBook S15 X510UF ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-48-generic root=UUID=2dccc476-4ac0-4ab2-9742-bde2ad020de3 ro quiet splash vt.handoff=7 SourcePackage: udisks2 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/06/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X510UF.304 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X510UF dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrX510UF.304:bd09/06/2019:svnASUSTeKCOMPUTERINC.:pnVivoBookS15X510UF:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX510UF:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: VivoBook S dmi.product.name: VivoBook S15 X510UF dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/udisks/+bug/1899361/+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 1281588] Re: Disk standby timer is broken
** Changed in: udisks2 (Ubuntu) Assignee: Phillip Susi (psusi) => (unassigned) -- 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/1281588 Title: Disk standby timer is broken Status in udisks: Fix Released Status in udisks2 package in Ubuntu: Fix Released Status in udisks2 source package in Trusty: Confirmed Bug description: udisks' / gnome-disk-utility's support for the drive standby timer is broken. If the standby timer is set to at least 10 minutes ( which is the minimum on many drives ), every 10 minutes udisks tries to update the smart status of the drive, which resets the standby timer. To manage notifications about this bug go to: https://bugs.launchpad.net/udisks/+bug/1281588/+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 1892723] Re: Evince can't open some pdf files correctly
** Changed in: evince (Ubuntu) Status: Incomplete => New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/1892723 Title: Evince can't open some pdf files correctly Status in evince package in Ubuntu: New Bug description: I have a pdf file which I can't open with evince. When I try to, suddenly window bar hides and it kind of crashs. There's not any problem with the file since it can be opened with other pdf readers. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: evince 3.36.7-0ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Aug 24 17:33:35 2020 InstallationDate: Installed on 2020-08-03 (20 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: evince UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1892723/+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 357315] Re: "There was an error while getting the sharing information"
** Tags added: focal ** Changed in: nautilus-share (Ubuntu) Status: Expired => New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus-share in Ubuntu. https://bugs.launchpad.net/bugs/357315 Title: "There was an error while getting the sharing information" Status in nautilus-share package in Ubuntu: New Bug description: Sometimes I get this message. "There was an error while getting the sharing information" bla bla bla something about samba. I cannot reproduce it because it sometimes occurs. Especially when I right click on a folder and see its properties. My version is Ubuntu 8.10 with all updates. I am new to Linux. Samba is not installed, not running. I am concerned somehow may be it can be a intrusion attempt or something like that? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus-share/+bug/357315/+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 1857539] Re: nautilus crashed with SIGSEGV in widget_needs_widget_path (shutdown?)
I have the same issue. I do have dropbox installed though. But doesn't look like it is because of dropbox. -- 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/1857539 Title: nautilus crashed with SIGSEGV in widget_needs_widget_path (shutdown?) Status in nautilus package in Ubuntu: Triaged Bug description: after turn on pc ProblemType: Crash DistroRelease: Ubuntu 20.04 Package: nautilus 1:3.34.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 Uname: Linux 5.3.0-24-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu15 Architecture: amd64 CrashCounter: 1 CurrentDesktop: ubuntu:GNOME Date: Wed Dec 25 01:52:06 2019 ExecutablePath: /usr/bin/nautilus GsettingsChanges: InstallationDate: Installed on 2019-12-22 (2 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20191221) ProcCmdline: /usr/bin/nautilus --gapplication-service ProcEnviron: SHELL=/bin/bash XDG_RUNTIME_DIR= PATH=(custom, no user) LANG=en_US.UTF-8 SegvAnalysis: Segfault happened at: 0x7f3fb437f962:mov0x380(%rax),%rax PC (0x7f3fb437f962) ok source "0x380(%rax)" (0x0380) not located in a known VMA region (needed readable region)! destination "%rax" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: nautilus StacktraceTop: ?? () from /lib/x86_64-linux-gnu/libgtk-3.so.0 ?? () from /lib/x86_64-linux-gnu/libgtk-3.so.0 ?? () from /lib/x86_64-linux-gnu/libgtk-3.so.0 ?? () from /lib/x86_64-linux-gnu/libgtk-3.so.0 ?? () from /lib/x86_64-linux-gnu/libgtk-3.so.0 Title: nautilus crashed with SIGSEGV UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip libvirt lpadmin lxd plugdev sambashare sudo separator: usr_lib_nautilus: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1857539/+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 1765363] Re: prime-select intel is not powering off the nvidia card
I have this problem on kubuntu 18.04 and ubuntu,kubuntu 20.04 dell inspiron 5110n nvidia gt525m nvidia driver-390 -- 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 1892723] Re: Evince can't open some pdf files correctly
Here's the output log when I try to open the file with Evince via terminal. ** Attachment added: "evince-log.txt" https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1892723/+attachment/5404387/+files/evince-log.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/1892723 Title: Evince can't open some pdf files correctly Status in evince package in Ubuntu: Incomplete Bug description: I have a pdf file which I can't open with evince. When I try to, suddenly window bar hides and it kind of crashs. There's not any problem with the file since it can be opened with other pdf readers. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: evince 3.36.7-0ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Aug 24 17:33:35 2020 InstallationDate: Installed on 2020-08-03 (20 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: evince UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1892723/+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 1892723] [NEW] Evince can't open some pdf files correctly
Public bug reported: I have a pdf file which I can't open with evince. When I try to, suddenly window bar hides and it kind of crashs. There's not any problem with the file since it can be opened with other pdf readers. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: evince 3.36.7-0ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Aug 24 17:33:35 2020 InstallationDate: Installed on 2020-08-03 (20 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: evince UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: evince (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ** Attachment added: "Screenshot from 2020-08-24 17-36-09.png" https://bugs.launchpad.net/bugs/1892723/+attachment/5404150/+files/Screenshot%20from%202020-08-24%2017-36-09.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/1892723 Title: Evince can't open some pdf files correctly Status in evince package in Ubuntu: New Bug description: I have a pdf file which I can't open with evince. When I try to, suddenly window bar hides and it kind of crashs. There's not any problem with the file since it can be opened with other pdf readers. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: evince 3.36.7-0ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Aug 24 17:33:35 2020 InstallationDate: Installed on 2020-08-03 (20 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: evince UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1892723/+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 1891796] [NEW] Screen tearing in web browser or video player
Public bug reported: When I'm scrolling a page in Firefox, I experience some screen tearing. It's also obvious while playing fullscreen videos on Youtube. P.S. I also tested it with this website: https://www.vsynctester.com/ and also this video: https://www.youtube.com/watch?v=0RvIbVmCOxg (while playing in 60fps) ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.6 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Aug 16 15:03:10 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: I just need to know a workaround GraphicsCard: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. UHD Graphics 620 [1043:1131] Subsystem: ASUSTeK Computer Inc. GM108M [GeForce MX130] [1043:1131] InstallationDate: Installed on 2020-08-03 (12 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: ASUSTeK COMPUTER INC. VivoBook S15 X510UF ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic root=UUID=d62ac2f5-71bc-4048-9c6e-2c4749b42d25 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/06/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X510UF.304 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X510UF dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrX510UF.304:bd09/06/2019:svnASUSTeKCOMPUTERINC.:pnVivoBookS15X510UF:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX510UF:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: VivoBook S dmi.product.name: VivoBook S15 X510UF dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ubuntu -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1891796 Title: Screen tearing in web browser or video player Status in xorg package in Ubuntu: New Bug description: When I'm scrolling a page in Firefox, I experience some screen tearing. It's also obvious while playing fullscreen videos on Youtube. P.S. I also tested it with this website: https://www.vsynctester.com/ and also this video: https://www.youtube.com/watch?v=0RvIbVmCOxg (while playing in 60fps) ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.6 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Aug 16 15:03:10 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: I just need to know a workaround GraphicsCard: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. UHD Graphics 620 [1043:1131] Subsystem: ASUSTeK Computer Inc. GM108M [GeForce MX130] [1043:1131] InstallationDate: Installed on 2020-08-03 (12 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: ASUSTeK COMPUTER INC. VivoBook S15 X510UF ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic root=UUID=d62ac2f5-71bc-4048-9c6e-2c4749b42d25 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/06/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X510UF.304 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X510UF dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK
[Desktop-packages] [Bug 1881909] Re: Screen tearing with Nvidia Optimus
** Also affects: nvidia-graphics-drivers-440 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1881909 Title: Screen tearing with Nvidia Optimus Status in mutter package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-390 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-440 package in Ubuntu: Confirmed Bug description: I have screen tearing when using nvidia card with 390 driver, affect browsers such as firefox and chromium also desktop since I have screen tearing when moving window around. I have no such problem when using using 18.04.4 and nvidia card with 390 driver. Intel graphic have no such problem weather in 18.04 or 20.04. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 Uname: Linux 5.4.0-33-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 390.132 Fri Nov 1 00:40:14 PDT 2019 GCC version: ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Jun 3 21:18:49 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0126] (rev 09) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. 2nd Generation Core Processor Family Integrated Graphics Controller [1043:1652] NVIDIA Corporation GF119M [GeForce 610M] [10de:1058] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. GeForce GT 610M [1043:1652] InstallationDate: Installed on 2020-06-01 (1 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: ASUSTeK Computer Inc. K43SD ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-33-generic root=UUID=8f02391a-a313-4598-b702-db7eccd55312 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/10/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: K43SD.208 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: K43SD dmi.board.vendor: ASUSTeK Computer Inc. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK Computer Inc. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrK43SD.208:bd08/10/2012:svnASUSTeKComputerInc.:pnK43SD:pvr1.0:rvnASUSTeKComputerInc.:rnK43SD:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr1.0: dmi.product.family: K dmi.product.name: K43SD dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK Computer Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1881909/+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 1691678] Re: Scrollbars escape the bottom and right side of the Terminal window by 1px
What is the current status of this bug? Can we have any workaround for this bug? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/1691678 Title: Scrollbars escape the bottom and right side of the Terminal window by 1px Status in GNOME Terminal: Fix Released Status in gnome-terminal package in Ubuntu: Triaged Status in gtk+3.0 package in Ubuntu: New Status in yaru-theme package in Ubuntu: Fix Released Bug description: Ubuntu's orange overlay scrollbars escape the bottom of the window during resizing. To reproduce try gnome-shell on artful using the Ambiance theme. Open a Terminal window and resize it vertically, quickly. Notice the bottom of the overlay scrollbar overruns the bottom of the window. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-shell 3.24.2-0ubuntu3 ProcVersionSignature: Ubuntu 4.10.0-20.22-generic 4.10.8 Uname: Linux 4.10.0-20-generic x86_64 ApportVersion: 2.20.5-0ubuntu3 Architecture: amd64 Date: Thu May 18 15:28:33 2017 DisplayManager: lightdm GsettingsChanges: b'org.gnome.shell' b'app-picker-view' b'uint32 1' b'org.gnome.shell' b'favorite-apps' b"['firefox.desktop', 'org.gnome.Terminal.desktop', 'rhythmbox.desktop', 'org.gnome.Nautilus.desktop', 'org.gnome.Software.desktop', 'yelp.desktop']" b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" b'org.gnome.desktop.interface' b'scaling-factor' b'uint32 1' InstallationDate: Installed on 2017-05-03 (15 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170502) SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-terminal/+bug/1691678/+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 1852183] Re: [X11] copy/paste (clipboard) is broken in Ubuntu 19.10 & 20.04 (see comment 93)
You can upgrade only related packages (Taken from https://launchpad.net/ubuntu/+source/mutter/3.36.2-1ubuntu1~20.04.1): mutter mutter-common libmutter-6-0 gir1.2-mutter-6 To rollback, remove proposed packages from your sources.list. Then, run apt-update and install them. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1852183 Title: [X11] copy/paste (clipboard) is broken in Ubuntu 19.10 & 20.04 (see comment 93) Status in LibreOffice: Won't Fix Status in Mutter: Unknown Status in mutter package in Ubuntu: Fix Released Status in mutter source package in Eoan: Triaged Status in mutter source package in Focal: Fix Committed Status in mutter source package in Groovy: Fix Released Bug description: [ Impact ] I'm running LibreOffice 6.3.2.2 on Ubuntu 19.10. In this environment, copy/cut/paste often fails. Specifically, the paste command sometimes does not paste the text that was cut/copied most recently. Instead, it pastes text that was cut/copied at some prior time. [ Test case ] 1. Use use libreoffice writer/calc 2. Copy text around 3. Paste it and ensure it always work [ Regression potential ] Copy/paste won't work as expected, for non-text types - I use LibreOffice Writer a lot, and I now see this problem very often, i.e. many times every day. There is some discussion of the problem here: https://ask.libreoffice.org/en/question/213510/copypaste-issues- libreoffice-calc/ Several posters there say that they are also using Ubuntu 19.10. Ubuntu 19.10 includes Mutter 3.34, which has a new clipboard manager: https://www.phoronix.com/scan.php?page=news_item=GNOME-3.34 -Clipboard-Manager It seems like that could be related. To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1852183/+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 1852183] Re: [X11] copy/paste (clipboard) is broken in Ubuntu 19.10 & 20.04 (see comment 93)
Regarding my previous comment, it seems I must've restarted the process before the upgrade taking effects. After restarting Firefox, I can copy- paste from and into it. For me, the upgrade seems to have solved the issue! -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1852183 Title: [X11] copy/paste (clipboard) is broken in Ubuntu 19.10 & 20.04 (see comment 93) Status in LibreOffice: Won't Fix Status in Mutter: Unknown Status in mutter package in Ubuntu: Fix Released Status in mutter source package in Eoan: Triaged Status in mutter source package in Focal: Fix Committed Status in mutter source package in Groovy: Fix Released Bug description: [ Impact ] I'm running LibreOffice 6.3.2.2 on Ubuntu 19.10. In this environment, copy/cut/paste often fails. Specifically, the paste command sometimes does not paste the text that was cut/copied most recently. Instead, it pastes text that was cut/copied at some prior time. [ Test case ] 1. Use use libreoffice writer/calc 2. Copy text around 3. Paste it and ensure it always work [ Regression potential ] Copy/paste won't work as expected, for non-text types - I use LibreOffice Writer a lot, and I now see this problem very often, i.e. many times every day. There is some discussion of the problem here: https://ask.libreoffice.org/en/question/213510/copypaste-issues- libreoffice-calc/ Several posters there say that they are also using Ubuntu 19.10. Ubuntu 19.10 includes Mutter 3.34, which has a new clipboard manager: https://www.phoronix.com/scan.php?page=news_item=GNOME-3.34 -Clipboard-Manager It seems like that could be related. To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1852183/+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 1852183] Re: [X11] copy/paste (clipboard) is broken in Ubuntu 19.10 & 20.04 (see comment 93)
After upgrading to proposed packages, I can also confirm that unfortunately the bug is still present. But its effects are much less than previous. I copied an image from Telegram and I was unable to paste it in Firefox (in a textbox where I could paste to it usually). However, I could paste it in Telegram itself and also LibreOffice. This also applies to texts. Also copying from Firefox and pasting into anywhere (including Firefox itself) didn't work. Even copying multiple times doesn't make any effect. P.S.: This problem doesn't happen always, but usually. P.S. 2: It seems to me to be a problem with Firefox or whatever it uses. firefox 75.0+build3-0ubuntu1 libreoffice-writer 1:6.4.2-0ubuntu3 gir1.2-mutter-6 3.36.2-1ubuntu1~20.04.1 mutter-common 3.36.2-1ubuntu1~20.04.1 mutter 3.36.2-1ubuntu1~20.04.1 libmutter-6-0 3.36.2-1ubuntu1~20.04.1 Running Ubuntu 20.04 Focal (Linux 5.4.0-26-generic #30-Ubuntu SMP Mon Apr 20 16:58:30 UTC 2020) on a x86_64 hardware. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1852183 Title: [X11] copy/paste (clipboard) is broken in Ubuntu 19.10 & 20.04 (see comment 93) Status in LibreOffice: Won't Fix Status in Mutter: Unknown Status in mutter package in Ubuntu: Fix Released Status in mutter source package in Eoan: Triaged Status in mutter source package in Focal: Fix Committed Status in mutter source package in Groovy: Fix Released Bug description: [ Impact ] I'm running LibreOffice 6.3.2.2 on Ubuntu 19.10. In this environment, copy/cut/paste often fails. Specifically, the paste command sometimes does not paste the text that was cut/copied most recently. Instead, it pastes text that was cut/copied at some prior time. [ Test case ] 1. Use use libreoffice writer/calc 2. Copy text around 3. Paste it and ensure it always work [ Regression potential ] Copy/paste won't work as expected, for non-text types - I use LibreOffice Writer a lot, and I now see this problem very often, i.e. many times every day. There is some discussion of the problem here: https://ask.libreoffice.org/en/question/213510/copypaste-issues- libreoffice-calc/ Several posters there say that they are also using Ubuntu 19.10. Ubuntu 19.10 includes Mutter 3.34, which has a new clipboard manager: https://www.phoronix.com/scan.php?page=news_item=GNOME-3.34 -Clipboard-Manager It seems like that could be related. To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1852183/+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 1691678] Re: Scrollbars escape the bottom and right side of the Terminal window by 1px
It's not an upstream bug. I checked several other distribution with different themes, none of them is affected. Only Ubuntu's gnome-terminal is affected. I don't understand why this simple bug is still around after realizing it was reported 3 years ago! I am retrying to home on Ubuntu after several years of leave, but again annoyed by this bug! The report saying 'fixed released' without any fixes! Please, try to fix these annoying bugs which preventing us to use themes other than default Ones! -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/1691678 Title: Scrollbars escape the bottom and right side of the Terminal window by 1px Status in GNOME Terminal: Fix Released Status in gnome-terminal package in Ubuntu: Confirmed Status in gtk+3.0 package in Ubuntu: Confirmed Status in ubuntu-themes package in Ubuntu: Confirmed Status in yaru-theme package in Ubuntu: Fix Released Bug description: Ubuntu's orange overlay scrollbars escape the bottom of the window during resizing. To reproduce try gnome-shell on artful using the Ambiance theme. Open a Terminal window and resize it vertically, quickly. Notice the bottom of the overlay scrollbar overruns the bottom of the window. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-shell 3.24.2-0ubuntu3 ProcVersionSignature: Ubuntu 4.10.0-20.22-generic 4.10.8 Uname: Linux 4.10.0-20-generic x86_64 ApportVersion: 2.20.5-0ubuntu3 Architecture: amd64 Date: Thu May 18 15:28:33 2017 DisplayManager: lightdm GsettingsChanges: b'org.gnome.shell' b'app-picker-view' b'uint32 1' b'org.gnome.shell' b'favorite-apps' b"['firefox.desktop', 'org.gnome.Terminal.desktop', 'rhythmbox.desktop', 'org.gnome.Nautilus.desktop', 'org.gnome.Software.desktop', 'yelp.desktop']" b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" b'org.gnome.desktop.interface' b'scaling-factor' b'uint32 1' InstallationDate: Installed on 2017-05-03 (15 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170502) SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-terminal/+bug/1691678/+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 1691678] Re: Scrollbars escape the bottom and right side of the Terminal window by 1px
I support the idea in the last para. of @egmont-gmail. If a patch introduce a regression which is worse than the improvement made by the patch, the patch should be dropped. I'm getting tired of Ubuntu fixing something and breaking some other things. Ubuntu LTS was rock solid once upon a time, but for regular users I don't see any point using LTS these days. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/1691678 Title: Scrollbars escape the bottom and right side of the Terminal window by 1px Status in GNOME Terminal: Fix Released Status in gnome-terminal package in Ubuntu: Confirmed Status in gtk+3.0 package in Ubuntu: Confirmed Status in ubuntu-themes package in Ubuntu: Confirmed Status in yaru-theme package in Ubuntu: Fix Released Bug description: Ubuntu's orange overlay scrollbars escape the bottom of the window during resizing. To reproduce try gnome-shell on artful using the Ambiance theme. Open a Terminal window and resize it vertically, quickly. Notice the bottom of the overlay scrollbar overruns the bottom of the window. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-shell 3.24.2-0ubuntu3 ProcVersionSignature: Ubuntu 4.10.0-20.22-generic 4.10.8 Uname: Linux 4.10.0-20-generic x86_64 ApportVersion: 2.20.5-0ubuntu3 Architecture: amd64 Date: Thu May 18 15:28:33 2017 DisplayManager: lightdm GsettingsChanges: b'org.gnome.shell' b'app-picker-view' b'uint32 1' b'org.gnome.shell' b'favorite-apps' b"['firefox.desktop', 'org.gnome.Terminal.desktop', 'rhythmbox.desktop', 'org.gnome.Nautilus.desktop', 'org.gnome.Software.desktop', 'yelp.desktop']" b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" b'org.gnome.desktop.interface' b'scaling-factor' b'uint32 1' InstallationDate: Installed on 2017-05-03 (15 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170502) SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-terminal/+bug/1691678/+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 1691678] Re: Scrollbars escape the bottom and right side of the Terminal window by 1px
What's the current status of this bug? Where is the fix? One of my report is made duplicate to this bug but I think this is much older. I'm using 19.10 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/1691678 Title: Scrollbars escape the bottom and right side of the Terminal window by 1px Status in GNOME Terminal: Fix Released Status in gnome-terminal package in Ubuntu: Confirmed Status in gtk+3.0 package in Ubuntu: Confirmed Status in ubuntu-themes package in Ubuntu: Confirmed Status in yaru-theme package in Ubuntu: Fix Released Bug description: Ubuntu's orange overlay scrollbars escape the bottom of the window during resizing. To reproduce try gnome-shell on artful using the Ambiance theme. Open a Terminal window and resize it vertically, quickly. Notice the bottom of the overlay scrollbar overruns the bottom of the window. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-shell 3.24.2-0ubuntu3 ProcVersionSignature: Ubuntu 4.10.0-20.22-generic 4.10.8 Uname: Linux 4.10.0-20-generic x86_64 ApportVersion: 2.20.5-0ubuntu3 Architecture: amd64 Date: Thu May 18 15:28:33 2017 DisplayManager: lightdm GsettingsChanges: b'org.gnome.shell' b'app-picker-view' b'uint32 1' b'org.gnome.shell' b'favorite-apps' b"['firefox.desktop', 'org.gnome.Terminal.desktop', 'rhythmbox.desktop', 'org.gnome.Nautilus.desktop', 'org.gnome.Software.desktop', 'yelp.desktop']" b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" b'org.gnome.desktop.interface' b'scaling-factor' b'uint32 1' InstallationDate: Installed on 2017-05-03 (15 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170502) SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-terminal/+bug/1691678/+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 1865326] [NEW] extra spaces on right and bottom border of gnome terminal's scrollbar
Public bug reported: On Ubuntu 19.10, On certain themes including the default adwaita theme which is used in vaniall gnome session, there are some extra ugly spaces around the scrollbar of the gnome terminal at right and bottom. I've checked other linux versions with same GNOME version, they don't have it. I've attached a screenshot of that I've asked a question on AskUbuntu site and many suggested to file a bug report https://askubuntu.com/q/1206023/61218 ** Affects: gnome-terminal (Ubuntu) Importance: Undecided Status: New ** Attachment added: "UWj3K.png" https://bugs.launchpad.net/bugs/1865326/+attachment/5332325/+files/UWj3K.png ** Description changed: On Ubuntu 19.10, On certain themes including the default adwaita theme which is used in vaniall gnome session, there are some extra ugly spaces around the scrollbar of the gnome terminal at right and bottom. I've checked other linux versions with same GNOME version, they don't have it. I've attached a screenshot of that + + I've asked a question on AskUbuntu site and many suggested to file a bug + report https://askubuntu.com/q/1206023/61218 ** Summary changed: - extra spaces on right and bottom border of gnome terminal + extra spaces on right and bottom border of gnome terminal's scrollbar -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/1865326 Title: extra spaces on right and bottom border of gnome terminal's scrollbar Status in gnome-terminal package in Ubuntu: New Bug description: On Ubuntu 19.10, On certain themes including the default adwaita theme which is used in vaniall gnome session, there are some extra ugly spaces around the scrollbar of the gnome terminal at right and bottom. I've checked other linux versions with same GNOME version, they don't have it. I've attached a screenshot of that I've asked a question on AskUbuntu site and many suggested to file a bug report https://askubuntu.com/q/1206023/61218 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1865326/+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 1858292] Re: gjs-console crashed with signal 5
** Information type changed from Private to Public -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gjs in Ubuntu. https://bugs.launchpad.net/bugs/1858292 Title: gjs-console crashed with signal 5 Status in gjs package in Ubuntu: New Bug description: gjs-console crashed and gnome-shell crashed with it ProblemType: Crash DistroRelease: Ubuntu 18.04 Package: gjs 1.52.5-0ubuntu18.04.1 ProcVersionSignature: Ubuntu 5.0.0-37.40~18.04.1-generic 5.0.21 Uname: Linux 5.0.0-37-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Jan 4 20:50:08 2020 ExecutablePath: /usr/bin/gjs-console InstallationDate: Installed on 2019-10-06 (90 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) ProcCmdline: gjs /home/username/.local/share/gnome-shell/extensions/gsconn...@andyholmes.github.io/service/daemon.js Signal: 5 SourcePackage: gjs StacktraceTop: () at /usr/lib/libgjs.so.0 gjs_value_from_explicit_array () at /usr/lib/libgjs.so.0 () at /usr/lib/libgjs.so.0 ffi_closure_unix64_inner () at /usr/lib/x86_64-linux-gnu/libffi.so.6 ffi_closure_unix64 () at /usr/lib/x86_64-linux-gnu/libffi.so.6 Title: gjs-console crashed with signal 5 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gjs/+bug/1858292/+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 1856696] [NEW] nautilus crashed with SIGSEGV
Public bug reported: crashed with also gnome-shell crashed ProblemType: Crash DistroRelease: Ubuntu 18.04 Package: nautilus 1:3.26.4-0~ubuntu18.04.4 ProcVersionSignature: Ubuntu 5.0.0-37.40~18.04.1-generic 5.0.21 Uname: Linux 5.0.0-37-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Dec 17 14:30:26 2019 ExecutablePath: /usr/bin/nautilus InstallationDate: Installed on 2019-10-06 (71 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) ProcCmdline: /usr/bin/nautilus --gapplication-service SegvAnalysis: Segfault happened at: 0x7f7c4aeae628: mov0x90(%r14),%rsi PC (0x7f7c4aeae628) ok source "0x90(%r14)" (0x0090) not located in a known VMA region (needed readable region)! destination "%rsi" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: nautilus StacktraceTop: () at /usr/lib/x86_64-linux-gnu/libgdk-3.so.0 () at /usr/lib/x86_64-linux-gnu/libgdk-3.so.0 () at /usr/lib/x86_64-linux-gnu/libgdk-3.so.0 gdk_display_get_event () at /usr/lib/x86_64-linux-gnu/libgdk-3.so.0 () at /usr/lib/x86_64-linux-gnu/libgdk-3.so.0 Title: nautilus crashed with SIGSEGV UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo usr_lib_nautilus: ** Affects: nautilus (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-crash bionic need-amd64-retrace third-party-packages ** Information type changed from Private to Public -- 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/1856696 Title: nautilus crashed with SIGSEGV Status in nautilus package in Ubuntu: New Bug description: crashed with also gnome-shell crashed ProblemType: Crash DistroRelease: Ubuntu 18.04 Package: nautilus 1:3.26.4-0~ubuntu18.04.4 ProcVersionSignature: Ubuntu 5.0.0-37.40~18.04.1-generic 5.0.21 Uname: Linux 5.0.0-37-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Dec 17 14:30:26 2019 ExecutablePath: /usr/bin/nautilus InstallationDate: Installed on 2019-10-06 (71 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) ProcCmdline: /usr/bin/nautilus --gapplication-service SegvAnalysis: Segfault happened at: 0x7f7c4aeae628:mov0x90(%r14),%rsi PC (0x7f7c4aeae628) ok source "0x90(%r14)" (0x0090) not located in a known VMA region (needed readable region)! destination "%rsi" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: nautilus StacktraceTop: () at /usr/lib/x86_64-linux-gnu/libgdk-3.so.0 () at /usr/lib/x86_64-linux-gnu/libgdk-3.so.0 () at /usr/lib/x86_64-linux-gnu/libgdk-3.so.0 gdk_display_get_event () at /usr/lib/x86_64-linux-gnu/libgdk-3.so.0 () at /usr/lib/x86_64-linux-gnu/libgdk-3.so.0 Title: nautilus crashed with SIGSEGV UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo usr_lib_nautilus: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1856696/+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 1851561] [NEW] nautilus crashed with SIGSEGV
Public bug reported: Crashed with Xorg crashed when resume the system from suspend when using dual screen with nvidia-driver ProblemType: Crash DistroRelease: Ubuntu 18.04 Package: nautilus 1:3.26.4-0~ubuntu18.04.4 ProcVersionSignature: Ubuntu 5.0.0-32.34~18.04.2-generic 5.0.21 Uname: Linux 5.0.0-32-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 Date: Mon Nov 4 23:50:06 2019 ExecutablePath: /usr/bin/nautilus InstallationDate: Installed on 2019-10-06 (31 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) ProcCmdline: nautilus --new-window /home/mhizzani/Downloads/Videos/Silicon.Valley.S06E02.1080p.WEB.h264-TBS[TGx] ProcEnviron: Error: [Errno 13] Permission denied: 'environ' SegvAnalysis: Segfault happened at: 0x7efc1581b4a4: mov0x380(%rax),%rax PC (0x7efc1581b4a4) ok source "0x380(%rax)" (0x0380) not located in a known VMA region (needed readable region)! destination "%rax" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: nautilus StacktraceTop: () at /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 () at /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 () at /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 () at /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 () at /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 Title: nautilus crashed with SIGSEGV UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo usr_lib_nautilus: ** Affects: nautilus (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-crash bionic need-amd64-retrace third-party-packages ** Information type changed from Private to Public -- 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/1851561 Title: nautilus crashed with SIGSEGV Status in nautilus package in Ubuntu: New Bug description: Crashed with Xorg crashed when resume the system from suspend when using dual screen with nvidia-driver ProblemType: Crash DistroRelease: Ubuntu 18.04 Package: nautilus 1:3.26.4-0~ubuntu18.04.4 ProcVersionSignature: Ubuntu 5.0.0-32.34~18.04.2-generic 5.0.21 Uname: Linux 5.0.0-32-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 Date: Mon Nov 4 23:50:06 2019 ExecutablePath: /usr/bin/nautilus InstallationDate: Installed on 2019-10-06 (31 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) ProcCmdline: nautilus --new-window /home/mhizzani/Downloads/Videos/Silicon.Valley.S06E02.1080p.WEB.h264-TBS[TGx] ProcEnviron: Error: [Errno 13] Permission denied: 'environ' SegvAnalysis: Segfault happened at: 0x7efc1581b4a4:mov0x380(%rax),%rax PC (0x7efc1581b4a4) ok source "0x380(%rax)" (0x0380) not located in a known VMA region (needed readable region)! destination "%rax" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: nautilus StacktraceTop: () at /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 () at /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 () at /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 () at /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 () at /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 Title: nautilus crashed with SIGSEGV UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo usr_lib_nautilus: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1851561/+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 1846330] [NEW] gnome-shell crashed with SIGSEGV
Public bug reported: When RAM is full gnome-shell crashes ProblemType: Crash DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.28.4-0ubuntu18.04.1 ProcVersionSignature: Ubuntu 4.15.0-64.73-generic 4.15.18 Uname: Linux 4.15.0-64-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 CrashCounter: 1 CurrentDesktop: ubuntu:GNOME Date: Wed Oct 2 14:38:01 2019 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell InstallationDate: Installed on 2019-02-12 (232 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) ProcCmdline: /usr/bin/gnome-shell SegvAnalysis: Segfault happened at: 0x7fe3394e0d24: lock addl $0x1,(%rax) PC (0x7fe3394e0d24) ok source "$0x1" ok destination "(%rax)" (0x) not located in a known VMA region (needed writable region)! SegvReason: writing NULL VMA Signal: 11 SourcePackage: gnome-shell StacktraceTop: () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 Title: gnome-shell crashed with SIGSEGV UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-crash bionic need-amd64-retrace third-party-packages ** Information type changed from Private to Public -- 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/1846330 Title: gnome-shell crashed with SIGSEGV Status in gnome-shell package in Ubuntu: New Bug description: When RAM is full gnome-shell crashes ProblemType: Crash DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.28.4-0ubuntu18.04.1 ProcVersionSignature: Ubuntu 4.15.0-64.73-generic 4.15.18 Uname: Linux 4.15.0-64-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 CrashCounter: 1 CurrentDesktop: ubuntu:GNOME Date: Wed Oct 2 14:38:01 2019 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell InstallationDate: Installed on 2019-02-12 (232 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) ProcCmdline: /usr/bin/gnome-shell SegvAnalysis: Segfault happened at: 0x7fe3394e0d24:lock addl $0x1,(%rax) PC (0x7fe3394e0d24) ok source "$0x1" ok destination "(%rax)" (0x) not located in a known VMA region (needed writable region)! SegvReason: writing NULL VMA Signal: 11 SourcePackage: gnome-shell StacktraceTop: () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 Title: gnome-shell crashed with SIGSEGV UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1846330/+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 1748429] Re: [snap] Libreoffice uses the adwaita gtk theme
Is there any update for this bug? This is unbearably ugly on other Linux distros not having Ambiance etc, especially on KDE -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1748429 Title: [snap] Libreoffice uses the adwaita gtk theme Status in libreoffice package in Ubuntu: Confirmed Bug description: Ubuntu 17.10 Installed the snap via https://forum.snapcraft.io/t/call-for-testing-libreoffice-6-0-0/3917 sudo snap install libreoffice --candidate Libreoffice 6 snap uses adwaita gtk Libreoffice 6 snap uses a hard path to the icon instead of the freedesktop spec To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1748429/+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 1823175] Re: Battery status shows "Estimating..." when fully charged
This problem solved for me after an update for upower package. -- 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/1823175 Title: Battery status shows "Estimating..." when fully charged Status in GNOME Shell: Fix Released Status in gnome-shell package in Ubuntu: Fix Released Status in gnome-shell source package in Bionic: Triaged Status in gnome-shell source package in Cosmic: Triaged Status in gnome-shell source package in Disco: Fix Released Bug description: My battery is fully charged and it shows 100%. When it's connected to charger, Battery symbol changes to battery-missing-symbol. It also shows "Estimating..." for time remaining. I'm using "Asus VivoBook x510uf" My battery status when connected to AC power: $ upower -d Device: /org/freedesktop/UPower/devices/line_power_AC0 native-path: AC0 power supply: yes updated: Thu 04 Apr 2019 08:26:58 PM +0430 (-11482 seconds ago) has history: no has statistics: no line-power warning-level: none online: yes icon-name: 'ac-adapter-symbolic' Device: /org/freedesktop/UPower/devices/battery_BAT0 native-path: BAT0 vendor: ASUSTeK model:ASUS Battery power supply: yes updated: Thu 04 Apr 2019 05:14:53 PM +0430 (43 seconds ago) has history: yes has statistics: yes battery present: yes rechargeable:yes state: pending-charge warning-level: none energy: 40.367 Wh energy-empty:0 Wh energy-full: 40.367 Wh energy-full-design: 43.046 Wh energy-rate: 0 W voltage: 11.55 V percentage: 100% capacity:93.7764% technology: lithium-ion icon-name: 'battery-full-charging-symbolic' History (charge): 15543934180.000 unknown History (rate): 15543934180.000 unknown Device: /org/freedesktop/UPower/devices/DisplayDevice power supply: yes updated: Thu 04 Apr 2019 08:26:58 PM +0430 (-11482 seconds ago) has history: no has statistics: no battery present: yes state: unknown warning-level: none energy: 40.367 Wh energy-full: 40.367 Wh energy-rate: 0 W percentage: 100% icon-name: 'battery-missing-symbolic' Daemon: daemon-version: 0.99.7 on-battery: no lid-is-closed: no lid-is-present: yes critical-action: HybridSleep - ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.28.3-0ubuntu0.18.04.4 ProcVersionSignature: Ubuntu 4.18.0-17.18~18.04.1-generic 4.18.20 Uname: Linux 4.18.0-17-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Apr 4 17:04:22 2019 DisplayManager: gdm3 InstallationDate: Installed on 2019-03-30 (4 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1823175/+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 1823175] Re: Battery status shows "Estimating..." when fully charged
** Changed in: gnome-shell (Ubuntu Bionic) Status: Triaged => Fix Released -- 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/1823175 Title: Battery status shows "Estimating..." when fully charged Status in GNOME Shell: Fix Released Status in gnome-shell package in Ubuntu: Fix Released Status in gnome-shell source package in Bionic: Fix Released Status in gnome-shell source package in Cosmic: Triaged Status in gnome-shell source package in Disco: Fix Released Bug description: My battery is fully charged and it shows 100%. When it's connected to charger, Battery symbol changes to battery-missing-symbol. It also shows "Estimating..." for time remaining. I'm using "Asus VivoBook x510uf" My battery status when connected to AC power: $ upower -d Device: /org/freedesktop/UPower/devices/line_power_AC0 native-path: AC0 power supply: yes updated: Thu 04 Apr 2019 08:26:58 PM +0430 (-11482 seconds ago) has history: no has statistics: no line-power warning-level: none online: yes icon-name: 'ac-adapter-symbolic' Device: /org/freedesktop/UPower/devices/battery_BAT0 native-path: BAT0 vendor: ASUSTeK model:ASUS Battery power supply: yes updated: Thu 04 Apr 2019 05:14:53 PM +0430 (43 seconds ago) has history: yes has statistics: yes battery present: yes rechargeable:yes state: pending-charge warning-level: none energy: 40.367 Wh energy-empty:0 Wh energy-full: 40.367 Wh energy-full-design: 43.046 Wh energy-rate: 0 W voltage: 11.55 V percentage: 100% capacity:93.7764% technology: lithium-ion icon-name: 'battery-full-charging-symbolic' History (charge): 15543934180.000 unknown History (rate): 15543934180.000 unknown Device: /org/freedesktop/UPower/devices/DisplayDevice power supply: yes updated: Thu 04 Apr 2019 08:26:58 PM +0430 (-11482 seconds ago) has history: no has statistics: no battery present: yes state: unknown warning-level: none energy: 40.367 Wh energy-full: 40.367 Wh energy-rate: 0 W percentage: 100% icon-name: 'battery-missing-symbolic' Daemon: daemon-version: 0.99.7 on-battery: no lid-is-closed: no lid-is-present: yes critical-action: HybridSleep - ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.28.3-0ubuntu0.18.04.4 ProcVersionSignature: Ubuntu 4.18.0-17.18~18.04.1-generic 4.18.20 Uname: Linux 4.18.0-17-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Apr 4 17:04:22 2019 DisplayManager: gdm3 InstallationDate: Installed on 2019-03-30 (4 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1823175/+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 1823461] Re: Font hinting lost on chrome like browser
I've tested the fix and it works fine. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to language-selector in Ubuntu. https://bugs.launchpad.net/bugs/1823461 Title: Font hinting lost on chrome like browser Status in language-selector package in Ubuntu: Fix Released Status in language-selector source package in Bionic: Fix Committed Bug description: [Impact] The file for configuring Japanese rendering with Noto fonts does not refer to the font family with sufficient precision, so it may affect rendering with other fonts unintentionally. The proposed upload fixes the issue. [Test Case] The real tests have been reported in comment #6 and #7 of this bug report. To verify that the modified file is properly installed: 1. Install language-selector-common and language-selector-gnome from bionic-proposed 2. Run this command: cat /etc/fonts/conf.avail/69-language-selector-ja.conf | grep 'Noto Sans CJK JP' (should output the line "Noto Sans CJK JP") [Regression Potential] That config file was added specifically for rendering Japanese with Noto fonts, and the modified file has been confirmed by the original author. Hence the regression risk should be low. [Original description] Since Ubuntu 18.04 (maybe from 17.10, I don't remember now), Chrome browsers are horrible to use. Font hintings are not working as expected. There were always some hairy things above the fonts which caused me to abandon Ubuntu. Unfortunately, this bug affected all other Ubuntu derivatives as well. I was forced to use Debian and Manjaro, because nowhere in the Internet I found a solution. I've tested Ubuntu 19.04 again. I removed all of the *.conf file in `/etc/fonts/conf.d` dir and copied Manjaro's configs. The fonts are okay. Further investigating revealed that the culprit was symlink to this file `/etc/fonts/conf.avail/69-language-selector-ja.conf` I opened it and found that on Line no 8, it has this which should instead be since `JP` is language identifier, not family. I manually fixed the file and all is well! I'm attaching two screenshot of chrome browser. Inspect the "Autofill" and "Appearance" word of the chrome setting page screenshot. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/language-selector/+bug/1823461/+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 1823461] Re: Font hinting lost on chrome like browser
I used your proposed modified file and the result was same as fixed. But I can't confirm with Japanese text since I don't use JP. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to language-selector in Ubuntu. https://bugs.launchpad.net/bugs/1823461 Title: Font hinting lost on chrome like browser Status in language-selector package in Ubuntu: Confirmed Bug description: Since Ubuntu 18.04 (maybe from 17.10, I don't remember now), Chrome browsers are horrible to use. Font hintings are not working as expected. There were always some hairy things above the fonts which caused me to abandon Ubuntu. Unfortunately, this bug affected all other Ubuntu derivatives as well. I was forced to use Debian and Manjaro, because nowhere in the Internet I found a solution. I've tested Ubuntu 19.04 again. I removed all of the *.conf file in `/etc/fonts/conf.d` dir and copied Manjaro's configs. The fonts are okay. Further investigating revealed that the culprit was symlink to this file `/etc/fonts/conf.avail/69-language-selector-ja.conf` I opened it and found that on Line no 8, it has this which should instead be since `JP` is language identifier, not family. I manually fixed the file and all is well! I'm attaching two screenshot of chrome browser. Inspect the "Autofill" and "Appearance" word of the chrome setting page screenshot. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/language-selector/+bug/1823461/+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 1823461] Re: Font hinting lost on chrome like browser
Sorry, both of the screenshot were same. Here is the fixed screenshot ** Attachment added: "fixed" https://bugs.launchpad.net/ubuntu/+source/fontconfig/+bug/1823461/+attachment/5253447/+files/fixed.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to fontconfig in Ubuntu. https://bugs.launchpad.net/bugs/1823461 Title: Font hinting lost on chrome like browser Status in fontconfig package in Ubuntu: Confirmed Bug description: Since Ubuntu 18.04 (maybe from 17.10, I don't remember now), Chrome browsers are horrible to use. Font hintings are not working as expected. There were always some hairy things above the fonts which caused me to abandon Ubuntu. Unfortunately, this bug affected all other Ubuntu derivatives as well. I was forced to use Debian and Manjaro, because nowhere in the Internet I found a solution. I've tested Ubuntu 19.04 again. I removed all of the *.conf file in `/etc/fonts/conf.d` dir and copied Manjaro's configs. The fonts are okay. Further investigating revealed that the culprit was symlink to this file `/etc/fonts/conf.avail/69-language-selector-ja.conf` I opened it and found that on Line no 8, it has this which should instead be since `JP` is language identifier, not family. I manually fixed the file and all is well! I'm attaching two screenshot of chrome browser. Inspect the "Autofill" and "Appearance" word of the chrome setting page screenshot. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fontconfig/+bug/1823461/+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 1823461] Re: Font hinting lost on chrome like browser
I couldn't add the fixed screenshot. Here it is ** Attachment added: "problem.png" https://bugs.launchpad.net/ubuntu/+source/fontconfig/+bug/1823461/+attachment/5253395/+files/problem.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to fontconfig in Ubuntu. https://bugs.launchpad.net/bugs/1823461 Title: Font hinting lost on chrome like browser Status in fontconfig package in Ubuntu: New Bug description: Since Ubuntu 18.04 (maybe from 17.10, I don't remember now), Chrome browsers are horrible to use. Font hintings are not working as expected. There were always some hairy things above the fonts which caused me to abandon Ubuntu. Unfortunately, this bug affected all other Ubuntu derivatives as well. I was forced to use Debian and Manjaro, because nowhere in the Internet I found a solution. I've tested Ubuntu 19.04 again. I removed all of the *.conf file in `/etc/fonts/conf.d` dir and copied Manjaro's configs. The fonts are okay. Further investigating revealed that the culprit was symlink to this file `/etc/fonts/conf.avail/69-language-selector-ja.conf` I opened it and found that on Line no 8, it has this which should instead be since `JP` is language identifier, not family. I manually fixed the file and all is well! I'm attaching two screenshot of chrome browser. Inspect the "Autofill" and "Appearance" word of the chrome setting page screenshot. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fontconfig/+bug/1823461/+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 1823461] [NEW] Font hinting lost on chrome like browser
Public bug reported: Since Ubuntu 18.04 (maybe from 17.10, I don't remember now), Chrome browsers are horrible to use. Font hintings are not working as expected. There were always some hairy things above the fonts which caused me to abandon Ubuntu. Unfortunately, this bug affected all other Ubuntu derivatives as well. I was forced to use Debian and Manjaro, because nowhere in the Internet I found a solution. I've tested Ubuntu 19.04 again. I removed all of the *.conf file in `/etc/fonts/conf.d` dir and copied Manjaro's configs. The fonts are okay. Further investigating revealed that the culprit was symlink to this file `/etc/fonts/conf.avail/69-language-selector-ja.conf` I opened it and found that on Line no 8, it has this which should instead be since `JP` is language identifier, not family. I manually fixed the file and all is well! I'm attaching two screenshot of chrome browser. Inspect the "Autofill" and "Appearance" word of the chrome setting page screenshot. ** Affects: fontconfig (Ubuntu) Importance: Undecided Status: New ** Attachment added: "problem" https://bugs.launchpad.net/bugs/1823461/+attachment/5253394/+files/problem.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to fontconfig in Ubuntu. https://bugs.launchpad.net/bugs/1823461 Title: Font hinting lost on chrome like browser Status in fontconfig package in Ubuntu: New Bug description: Since Ubuntu 18.04 (maybe from 17.10, I don't remember now), Chrome browsers are horrible to use. Font hintings are not working as expected. There were always some hairy things above the fonts which caused me to abandon Ubuntu. Unfortunately, this bug affected all other Ubuntu derivatives as well. I was forced to use Debian and Manjaro, because nowhere in the Internet I found a solution. I've tested Ubuntu 19.04 again. I removed all of the *.conf file in `/etc/fonts/conf.d` dir and copied Manjaro's configs. The fonts are okay. Further investigating revealed that the culprit was symlink to this file `/etc/fonts/conf.avail/69-language-selector-ja.conf` I opened it and found that on Line no 8, it has this which should instead be since `JP` is language identifier, not family. I manually fixed the file and all is well! I'm attaching two screenshot of chrome browser. Inspect the "Autofill" and "Appearance" word of the chrome setting page screenshot. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fontconfig/+bug/1823461/+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 1823175] Re: Battery status shows "Estimating..." when fully charged
** Also affects: upower (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to upower in Ubuntu. https://bugs.launchpad.net/bugs/1823175 Title: Battery status shows "Estimating..." when fully charged Status in GNOME Shell: Fix Released Status in gnome-shell package in Ubuntu: Fix Released Status in upower package in Ubuntu: New Status in gnome-shell source package in Bionic: Triaged Status in upower source package in Bionic: New Status in gnome-shell source package in Cosmic: Triaged Status in upower source package in Cosmic: New Status in gnome-shell source package in Disco: Fix Released Status in upower source package in Disco: New Bug description: My battery is fully charged and it shows 100%. When it's connected to charger, Battery symbol changes to battery-missing-symbol. It also shows "Estimating..." for time remaining. I'm using "Asus VivoBook x510uf" My battery status when connected to AC power: $ upower -d Device: /org/freedesktop/UPower/devices/line_power_AC0 native-path: AC0 power supply: yes updated: Thu 04 Apr 2019 08:26:58 PM +0430 (-11482 seconds ago) has history: no has statistics: no line-power warning-level: none online: yes icon-name: 'ac-adapter-symbolic' Device: /org/freedesktop/UPower/devices/battery_BAT0 native-path: BAT0 vendor: ASUSTeK model:ASUS Battery power supply: yes updated: Thu 04 Apr 2019 05:14:53 PM +0430 (43 seconds ago) has history: yes has statistics: yes battery present: yes rechargeable:yes state: pending-charge warning-level: none energy: 40.367 Wh energy-empty:0 Wh energy-full: 40.367 Wh energy-full-design: 43.046 Wh energy-rate: 0 W voltage: 11.55 V percentage: 100% capacity:93.7764% technology: lithium-ion icon-name: 'battery-full-charging-symbolic' History (charge): 15543934180.000 unknown History (rate): 15543934180.000 unknown Device: /org/freedesktop/UPower/devices/DisplayDevice power supply: yes updated: Thu 04 Apr 2019 08:26:58 PM +0430 (-11482 seconds ago) has history: no has statistics: no battery present: yes state: unknown warning-level: none energy: 40.367 Wh energy-full: 40.367 Wh energy-rate: 0 W percentage: 100% icon-name: 'battery-missing-symbolic' Daemon: daemon-version: 0.99.7 on-battery: no lid-is-closed: no lid-is-present: yes critical-action: HybridSleep - ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.28.3-0ubuntu0.18.04.4 ProcVersionSignature: Ubuntu 4.18.0-17.18~18.04.1-generic 4.18.20 Uname: Linux 4.18.0-17-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Apr 4 17:04:22 2019 DisplayManager: gdm3 InstallationDate: Installed on 2019-03-30 (4 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1823175/+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 1823175] Re: Battery status shows "Estimating..." when fully charged
How can I solve it on ubuntu 18.04 LTS? -- 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/1823175 Title: Battery status shows "Estimating..." when fully charged Status in GNOME Shell: Fix Released Status in gnome-shell package in Ubuntu: Fix Released Status in gnome-shell source package in Bionic: Triaged Status in gnome-shell source package in Cosmic: Triaged Status in gnome-shell source package in Disco: Fix Released Bug description: My battery is fully charged and it shows 100%. When it's connected to charger, Battery symbol changes to battery-missing-symbol. It also shows "Estimating..." for time remaining. I'm using "Asus VivoBook x510uf" My battery status when connected to AC power: $ upower -d Device: /org/freedesktop/UPower/devices/line_power_AC0 native-path: AC0 power supply: yes updated: Thu 04 Apr 2019 08:26:58 PM +0430 (-11482 seconds ago) has history: no has statistics: no line-power warning-level: none online: yes icon-name: 'ac-adapter-symbolic' Device: /org/freedesktop/UPower/devices/battery_BAT0 native-path: BAT0 vendor: ASUSTeK model:ASUS Battery power supply: yes updated: Thu 04 Apr 2019 05:14:53 PM +0430 (43 seconds ago) has history: yes has statistics: yes battery present: yes rechargeable:yes state: pending-charge warning-level: none energy: 40.367 Wh energy-empty:0 Wh energy-full: 40.367 Wh energy-full-design: 43.046 Wh energy-rate: 0 W voltage: 11.55 V percentage: 100% capacity:93.7764% technology: lithium-ion icon-name: 'battery-full-charging-symbolic' History (charge): 15543934180.000 unknown History (rate): 15543934180.000 unknown Device: /org/freedesktop/UPower/devices/DisplayDevice power supply: yes updated: Thu 04 Apr 2019 08:26:58 PM +0430 (-11482 seconds ago) has history: no has statistics: no battery present: yes state: unknown warning-level: none energy: 40.367 Wh energy-full: 40.367 Wh energy-rate: 0 W percentage: 100% icon-name: 'battery-missing-symbolic' Daemon: daemon-version: 0.99.7 on-battery: no lid-is-closed: no lid-is-present: yes critical-action: HybridSleep - ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.28.3-0ubuntu0.18.04.4 ProcVersionSignature: Ubuntu 4.18.0-17.18~18.04.1-generic 4.18.20 Uname: Linux 4.18.0-17-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Apr 4 17:04:22 2019 DisplayManager: gdm3 InstallationDate: Installed on 2019-03-30 (4 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1823175/+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 1823175] Re: battery status shows "estimating" when fully charged
I'm not sure which package ** Package changed: gnome-shell (Ubuntu) => ubuntu -- 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/1823175 Title: battery status shows "estimating" when fully charged Status in Ubuntu: New Bug description: My battery is fully charged and it shows 100%. When it's connected to charger, Battery symbol changes to battery-missing-symbol. It also shows "Estimating..." for time remaining. I'm using "Asus VivoBook x510uf" My battery status when connected to AC power: $ upower -d Device: /org/freedesktop/UPower/devices/line_power_AC0 native-path: AC0 power supply: yes updated: Thu 04 Apr 2019 08:26:58 PM +0430 (-11482 seconds ago) has history: no has statistics: no line-power warning-level: none online: yes icon-name: 'ac-adapter-symbolic' Device: /org/freedesktop/UPower/devices/battery_BAT0 native-path: BAT0 vendor: ASUSTeK model:ASUS Battery power supply: yes updated: Thu 04 Apr 2019 05:14:53 PM +0430 (43 seconds ago) has history: yes has statistics: yes battery present: yes rechargeable:yes state: pending-charge warning-level: none energy: 40.367 Wh energy-empty:0 Wh energy-full: 40.367 Wh energy-full-design: 43.046 Wh energy-rate: 0 W voltage: 11.55 V percentage: 100% capacity:93.7764% technology: lithium-ion icon-name: 'battery-full-charging-symbolic' History (charge): 15543934180.000 unknown History (rate): 15543934180.000 unknown Device: /org/freedesktop/UPower/devices/DisplayDevice power supply: yes updated: Thu 04 Apr 2019 08:26:58 PM +0430 (-11482 seconds ago) has history: no has statistics: no battery present: yes state: unknown warning-level: none energy: 40.367 Wh energy-full: 40.367 Wh energy-rate: 0 W percentage: 100% icon-name: 'battery-missing-symbolic' Daemon: daemon-version: 0.99.7 on-battery: no lid-is-closed: no lid-is-present: yes critical-action: HybridSleep - ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.28.3-0ubuntu0.18.04.4 ProcVersionSignature: Ubuntu 4.18.0-17.18~18.04.1-generic 4.18.20 Uname: Linux 4.18.0-17-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Apr 4 17:04:22 2019 DisplayManager: gdm3 InstallationDate: Installed on 2019-03-30 (4 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1823175/+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 1823175] Re: battery status shows "estimating" when fully charged
** Description changed: My battery is fully charged and it shows 100%. When it's connected connected to charger, Battery symbol changes to battery-missing-symbol. It also shows "Estimating..." for time remaining. I'm using "Asus VivoBook x510uf" My battery status when connected to AC power: $ upower -d Device: /org/freedesktop/UPower/devices/line_power_AC0 native-path: AC0 power supply: yes updated: Thu 04 Apr 2019 08:26:58 PM +0430 (-11482 seconds ago) has history: no has statistics: no line-power warning-level: none online: yes icon-name: 'ac-adapter-symbolic' Device: /org/freedesktop/UPower/devices/battery_BAT0 native-path: BAT0 vendor: ASUSTeK model:ASUS Battery power supply: yes updated: Thu 04 Apr 2019 05:14:53 PM +0430 (43 seconds ago) has history: yes has statistics: yes battery present: yes rechargeable:yes state: pending-charge warning-level: none energy: 40.367 Wh energy-empty:0 Wh energy-full: 40.367 Wh energy-full-design: 43.046 Wh energy-rate: 0 W voltage: 11.55 V percentage: 100% capacity:93.7764% technology: lithium-ion icon-name: 'battery-full-charging-symbolic' History (charge): 15543934180.000 unknown History (rate): 15543934180.000 unknown Device: /org/freedesktop/UPower/devices/DisplayDevice power supply: yes updated: Thu 04 Apr 2019 08:26:58 PM +0430 (-11482 seconds ago) has history: no has statistics: no battery present: yes state: unknown warning-level: none energy: 40.367 Wh energy-full: 40.367 Wh energy-rate: 0 W percentage: 100% icon-name: 'battery-missing-symbolic' Daemon: daemon-version: 0.99.7 on-battery: no lid-is-closed: no lid-is-present: yes critical-action: HybridSleep + - + ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.28.3-0ubuntu0.18.04.4 ProcVersionSignature: Ubuntu 4.18.0-17.18~18.04.1-generic 4.18.20 Uname: Linux 4.18.0-17-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Apr 4 17:04:22 2019 DisplayManager: gdm3 InstallationDate: Installed on 2019-03-30 (4 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) ** Description changed: - My battery is fully charged and it shows 100%. When it's connected connected to charger, Battery symbol changes to battery-missing-symbol. It also shows "Estimating..." for time remaining. + My battery is fully charged and it shows 100%. When it's connected to charger, Battery symbol changes to battery-missing-symbol. It also shows "Estimating..." for time remaining. I'm using "Asus VivoBook x510uf" My battery status when connected to AC power: $ upower -d Device: /org/freedesktop/UPower/devices/line_power_AC0 native-path: AC0 power supply: yes updated: Thu 04 Apr 2019 08:26:58 PM +0430 (-11482 seconds ago) has history: no has statistics: no line-power warning-level: none online: yes icon-name: 'ac-adapter-symbolic' Device: /org/freedesktop/UPower/devices/battery_BAT0 native-path: BAT0 vendor: ASUSTeK model:ASUS Battery power supply: yes updated: Thu 04 Apr 2019 05:14:53 PM +0430 (43 seconds ago) has history: yes has statistics: yes battery present: yes rechargeable:yes state: pending-charge warning-level: none energy: 40.367 Wh energy-empty:0 Wh energy-full: 40.367 Wh energy-full-design: 43.046 Wh energy-rate: 0 W voltage: 11.55 V percentage: 100% capacity:93.7764% technology: lithium-ion icon-name: 'battery-full-charging-symbolic' History (charge): 15543934180.000 unknown History (rate): 15543934180.000 unknown Device: /org/freedesktop/UPower/devices/DisplayDevice power supply: yes updated: Thu 04 Apr 2019 08:26:58 PM +0430 (-11482 seconds ago) has
[Desktop-packages] [Bug 1553685] Re: Lenovo Y700-17ISK subwoofer doesn't work
This does not only affect Y700. This affects all Lenovo laptops with subwoofers, y50, y700, y720 etc. Also, Linux supports drivers for hardware that is a lot older, this hardware is only about 2 years old (y720). -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1553685 Title: Lenovo Y700-17ISK subwoofer doesn't work Status in alsa-driver package in Ubuntu: Confirmed Bug description: Lenovo Y700-17ISK (Intel Core i7-6700HQ/RAM 16GB/SSD 512GB/Nvidia GTX960M 4GB) Operating system: Ubuntu 16.04 (xenial-desktop-amd64.iso 04-Mar-2016, kernel 4.4.0-10-generic, nvidia 361.28) Problem: Notebook subwoofer doesn't work. Judging from alsa-info.sh output, there is no pin declared for the bass output by BIOS. Please find a zip file attached: 'alsa-info_hdajackretask-unconnected-pins' ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-10-generic 4.4.0-10.25 ProcVersionSignature: Ubuntu 4.4.0-10.25-generic 4.4.3 Uname: Linux 4.4.0-10-generic x86_64 ApportVersion: 2.20-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: aljosa 1776 F pulseaudio CurrentDesktop: Unity Date: Sun Mar 6 11:02:21 2016 HibernationDevice: RESUME=UUID=ac022671-63df-40ae-bffe-66fff3b35125 InstallationDate: Installed on 2016-03-05 (0 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160304) MachineType: LENOVO 80Q0 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-10-generic.efi.signed root=UUID=aa4325c4-4b4c-4372-b8ca-a66c3e5b2aa6 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-10-generic N/A linux-backports-modules-4.4.0-10-generic N/A linux-firmware1.156 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/31/2016 dmi.bios.vendor: LENOVO dmi.bios.version: CDCN30WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: Allsparks 7A dmi.board.vendor: LENOVO dmi.board.version: NO DPK dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad Y700-17ISK dmi.modalias: dmi:bvnLENOVO:bvrCDCN30WW:bd01/31/2016:svnLENOVO:pn80Q0:pvrLenovoideapadY700-17ISK:rvnLENOVO:rnAllsparks7A:rvrNODPK:cvnLENOVO:ct10:cvrLenovoideapadY700-17ISK: dmi.product.name: 80Q0 dmi.product.version: Lenovo ideapad Y700-17ISK dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1553685/+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 1553685] Re: Lenovo Y700-17ISK subwoofer doesn't work
I really want this solved too. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1553685 Title: Lenovo Y700-17ISK subwoofer doesn't work Status in alsa-driver package in Ubuntu: Confirmed Bug description: Lenovo Y700-17ISK (Intel Core i7-6700HQ/RAM 16GB/SSD 512GB/Nvidia GTX960M 4GB) Operating system: Ubuntu 16.04 (xenial-desktop-amd64.iso 04-Mar-2016, kernel 4.4.0-10-generic, nvidia 361.28) Problem: Notebook subwoofer doesn't work. Judging from alsa-info.sh output, there is no pin declared for the bass output by BIOS. Please find a zip file attached: 'alsa-info_hdajackretask-unconnected-pins' ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-10-generic 4.4.0-10.25 ProcVersionSignature: Ubuntu 4.4.0-10.25-generic 4.4.3 Uname: Linux 4.4.0-10-generic x86_64 ApportVersion: 2.20-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: aljosa 1776 F pulseaudio CurrentDesktop: Unity Date: Sun Mar 6 11:02:21 2016 HibernationDevice: RESUME=UUID=ac022671-63df-40ae-bffe-66fff3b35125 InstallationDate: Installed on 2016-03-05 (0 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160304) MachineType: LENOVO 80Q0 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-10-generic.efi.signed root=UUID=aa4325c4-4b4c-4372-b8ca-a66c3e5b2aa6 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-10-generic N/A linux-backports-modules-4.4.0-10-generic N/A linux-firmware1.156 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/31/2016 dmi.bios.vendor: LENOVO dmi.bios.version: CDCN30WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: Allsparks 7A dmi.board.vendor: LENOVO dmi.board.version: NO DPK dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad Y700-17ISK dmi.modalias: dmi:bvnLENOVO:bvrCDCN30WW:bd01/31/2016:svnLENOVO:pn80Q0:pvrLenovoideapadY700-17ISK:rvnLENOVO:rnAllsparks7A:rvrNODPK:cvnLENOVO:ct10:cvrLenovoideapadY700-17ISK: dmi.product.name: 80Q0 dmi.product.version: Lenovo ideapad Y700-17ISK dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1553685/+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 1807272] [NEW] package libpolkit-backend-1-0:amd64 0.105-14.1 failed to install/upgrade: package libpolkit-backend-1-0:amd64 is not ready for configuration cannot configure (cu
Public bug reported: I install Ubuntu 16.04 two days ago and install package only with synaptic. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: libpolkit-backend-1-0:amd64 0.105-14.1 ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13 Uname: Linux 4.4.0-31-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 Date: Fri Dec 7 00:30:14 2018 DuplicateSignature: package:libpolkit-backend-1-0:amd64:0.105-14.1 Processing triggers for libglib2.0-0:amd64 (2.48.2-0ubuntu4.1) ... dpkg: error processing package libpolkit-backend-1-0:amd64 (--configure): package libpolkit-backend-1-0:amd64 is not ready for configuration ErrorMessage: package libpolkit-backend-1-0:amd64 is not ready for configuration cannot configure (current status 'half-installed') RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.15ubuntu0.2 SourcePackage: policykit-1 Title: package libpolkit-backend-1-0:amd64 0.105-14.1 failed to install/upgrade: package libpolkit-backend-1-0:amd64 is not ready for configuration cannot configure (current status 'half-installed') UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: policykit-1 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package xenial -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to policykit-1 in Ubuntu. https://bugs.launchpad.net/bugs/1807272 Title: package libpolkit-backend-1-0:amd64 0.105-14.1 failed to install/upgrade: package libpolkit-backend-1-0:amd64 is not ready for configuration cannot configure (current status 'half-installed') Status in policykit-1 package in Ubuntu: New Bug description: I install Ubuntu 16.04 two days ago and install package only with synaptic. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: libpolkit-backend-1-0:amd64 0.105-14.1 ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13 Uname: Linux 4.4.0-31-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 Date: Fri Dec 7 00:30:14 2018 DuplicateSignature: package:libpolkit-backend-1-0:amd64:0.105-14.1 Processing triggers for libglib2.0-0:amd64 (2.48.2-0ubuntu4.1) ... dpkg: error processing package libpolkit-backend-1-0:amd64 (--configure): package libpolkit-backend-1-0:amd64 is not ready for configuration ErrorMessage: package libpolkit-backend-1-0:amd64 is not ready for configuration cannot configure (current status 'half-installed') RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.15ubuntu0.2 SourcePackage: policykit-1 Title: package libpolkit-backend-1-0:amd64 0.105-14.1 failed to install/upgrade: package libpolkit-backend-1-0:amd64 is not ready for configuration cannot configure (current status 'half-installed') UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/policykit-1/+bug/1807272/+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 1795965] [NEW] I can see my printer icon but cannot open the icon. And, I cannot print although the printer name is shown.
Public bug reported: When I run $ sudo system-config-printer, the following messages are appeared. Traceback (most recent call last): File "/usr/share/system-config-printer/system-config-printer.py", line 29, in import dbus File "/usr/lib/python3/dist-packages/dbus/__init__.py", line 82, in import dbus.types as types File "/usr/lib/python3/dist-packages/dbus/types.py", line 6, in from _dbus_bindings import ( ModuleNotFoundError: No module named '_dbus_bindings' Error in sys.excepthook: Traceback (most recent call last): File "/usr/lib/python3/dist-packages/apport_python_hook.py", line 63, in apport_excepthook from apport.fileutils import likely_packaged, get_recent_crashes File "/usr/lib/python3/dist-packages/apport/__init__.py", line 5, in from apport.report import Report File "/usr/lib/python3/dist-packages/apport/report.py", line 30, in import apport.fileutils File "/usr/lib/python3/dist-packages/apport/fileutils.py", line 23, in from apport.packaging_impl import impl as packaging File "/usr/lib/python3/dist-packages/apport/packaging_impl.py", line 23, in import apt File "/usr/lib/python3/dist-packages/apt/__init__.py", line 23, in import apt_pkg ModuleNotFoundError: No module named 'apt_pkg' Original exception was: Traceback (most recent call last): File "/usr/share/system-config-printer/system-config-printer.py", line 29, in import dbus File "/usr/lib/python3/dist-packages/dbus/__init__.py", line 82, in import dbus.types as types File "/usr/lib/python3/dist-packages/dbus/types.py", line 6, in from _dbus_bindings import ( ModuleNotFoundError: No module named '_dbus_bindings' ** Affects: system-config-printer (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to system-config-printer in Ubuntu. https://bugs.launchpad.net/bugs/1795965 Title: I can see my printer icon but cannot open the icon. And, I cannot print although the printer name is shown. Status in system-config-printer package in Ubuntu: New Bug description: When I run $ sudo system-config-printer, the following messages are appeared. Traceback (most recent call last): File "/usr/share/system-config-printer/system-config-printer.py", line 29, in import dbus File "/usr/lib/python3/dist-packages/dbus/__init__.py", line 82, in import dbus.types as types File "/usr/lib/python3/dist-packages/dbus/types.py", line 6, in from _dbus_bindings import ( ModuleNotFoundError: No module named '_dbus_bindings' Error in sys.excepthook: Traceback (most recent call last): File "/usr/lib/python3/dist-packages/apport_python_hook.py", line 63, in apport_excepthook from apport.fileutils import likely_packaged, get_recent_crashes File "/usr/lib/python3/dist-packages/apport/__init__.py", line 5, in from apport.report import Report File "/usr/lib/python3/dist-packages/apport/report.py", line 30, in import apport.fileutils File "/usr/lib/python3/dist-packages/apport/fileutils.py", line 23, in from apport.packaging_impl import impl as packaging File "/usr/lib/python3/dist-packages/apport/packaging_impl.py", line 23, in import apt File "/usr/lib/python3/dist-packages/apt/__init__.py", line 23, in import apt_pkg ModuleNotFoundError: No module named 'apt_pkg' Original exception was: Traceback (most recent call last): File "/usr/share/system-config-printer/system-config-printer.py", line 29, in import dbus File "/usr/lib/python3/dist-packages/dbus/__init__.py", line 82, in import dbus.types as types File "/usr/lib/python3/dist-packages/dbus/types.py", line 6, in from _dbus_bindings import ( ModuleNotFoundError: No module named '_dbus_bindings' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/system-config-printer/+bug/1795965/+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 1553685] Re: Lenovo Y700-17ISK subwoofer doesn't work
Post on askubuntu: https://askubuntu.com/questions/1072273/hdajackretask-gives-new-audio- settings-in-alsamixer-but-they-dont-work -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1553685 Title: Lenovo Y700-17ISK subwoofer doesn't work Status in alsa-driver package in Ubuntu: Confirmed Bug description: Lenovo Y700-17ISK (Intel Core i7-6700HQ/RAM 16GB/SSD 512GB/Nvidia GTX960M 4GB) Operating system: Ubuntu 16.04 (xenial-desktop-amd64.iso 04-Mar-2016, kernel 4.4.0-10-generic, nvidia 361.28) Problem: Notebook subwoofer doesn't work. Judging from alsa-info.sh output, there is no pin declared for the bass output by BIOS. Please find a zip file attached: 'alsa-info_hdajackretask-unconnected-pins' ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-10-generic 4.4.0-10.25 ProcVersionSignature: Ubuntu 4.4.0-10.25-generic 4.4.3 Uname: Linux 4.4.0-10-generic x86_64 ApportVersion: 2.20-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: aljosa 1776 F pulseaudio CurrentDesktop: Unity Date: Sun Mar 6 11:02:21 2016 HibernationDevice: RESUME=UUID=ac022671-63df-40ae-bffe-66fff3b35125 InstallationDate: Installed on 2016-03-05 (0 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160304) MachineType: LENOVO 80Q0 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-10-generic.efi.signed root=UUID=aa4325c4-4b4c-4372-b8ca-a66c3e5b2aa6 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-10-generic N/A linux-backports-modules-4.4.0-10-generic N/A linux-firmware1.156 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/31/2016 dmi.bios.vendor: LENOVO dmi.bios.version: CDCN30WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: Allsparks 7A dmi.board.vendor: LENOVO dmi.board.version: NO DPK dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad Y700-17ISK dmi.modalias: dmi:bvnLENOVO:bvrCDCN30WW:bd01/31/2016:svnLENOVO:pn80Q0:pvrLenovoideapadY700-17ISK:rvnLENOVO:rnAllsparks7A:rvrNODPK:cvnLENOVO:ct10:cvrLenovoideapadY700-17ISK: dmi.product.name: 80Q0 dmi.product.version: Lenovo ideapad Y700-17ISK dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1553685/+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 1553685] Re: Lenovo Y700-17ISK subwoofer doesn't work
Can someone from the ALSA team give any update on this please? It is confirmed multiple times that the 0x17 pin seems to be the one for the LFE subwoofer, but turning it on in HDAjackRetask does not work. Perhaps you can give us more information? This bug has been here since 2016.. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1553685 Title: Lenovo Y700-17ISK subwoofer doesn't work Status in alsa-driver package in Ubuntu: Confirmed Bug description: Lenovo Y700-17ISK (Intel Core i7-6700HQ/RAM 16GB/SSD 512GB/Nvidia GTX960M 4GB) Operating system: Ubuntu 16.04 (xenial-desktop-amd64.iso 04-Mar-2016, kernel 4.4.0-10-generic, nvidia 361.28) Problem: Notebook subwoofer doesn't work. Judging from alsa-info.sh output, there is no pin declared for the bass output by BIOS. Please find a zip file attached: 'alsa-info_hdajackretask-unconnected-pins' ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-10-generic 4.4.0-10.25 ProcVersionSignature: Ubuntu 4.4.0-10.25-generic 4.4.3 Uname: Linux 4.4.0-10-generic x86_64 ApportVersion: 2.20-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: aljosa 1776 F pulseaudio CurrentDesktop: Unity Date: Sun Mar 6 11:02:21 2016 HibernationDevice: RESUME=UUID=ac022671-63df-40ae-bffe-66fff3b35125 InstallationDate: Installed on 2016-03-05 (0 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160304) MachineType: LENOVO 80Q0 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-10-generic.efi.signed root=UUID=aa4325c4-4b4c-4372-b8ca-a66c3e5b2aa6 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-10-generic N/A linux-backports-modules-4.4.0-10-generic N/A linux-firmware1.156 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/31/2016 dmi.bios.vendor: LENOVO dmi.bios.version: CDCN30WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: Allsparks 7A dmi.board.vendor: LENOVO dmi.board.version: NO DPK dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad Y700-17ISK dmi.modalias: dmi:bvnLENOVO:bvrCDCN30WW:bd01/31/2016:svnLENOVO:pn80Q0:pvrLenovoideapadY700-17ISK:rvnLENOVO:rnAllsparks7A:rvrNODPK:cvnLENOVO:ct10:cvrLenovoideapadY700-17ISK: dmi.product.name: 80Q0 dmi.product.version: Lenovo ideapad Y700-17ISK dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1553685/+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 1553685] Re: Lenovo Y700-17ISK subwoofer doesn't work
I tried every combination in HDAjackretask, tried all pins, all different kind of combinations with the pins. I even wrote down on paper all the possible combinations for my 3 output pins, 0x14, 0x17 and 0x1b, none of them solved this. They all just bring more sound settings up, but none of them do anything at all. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1553685 Title: Lenovo Y700-17ISK subwoofer doesn't work Status in alsa-driver package in Ubuntu: Confirmed Bug description: Lenovo Y700-17ISK (Intel Core i7-6700HQ/RAM 16GB/SSD 512GB/Nvidia GTX960M 4GB) Operating system: Ubuntu 16.04 (xenial-desktop-amd64.iso 04-Mar-2016, kernel 4.4.0-10-generic, nvidia 361.28) Problem: Notebook subwoofer doesn't work. Judging from alsa-info.sh output, there is no pin declared for the bass output by BIOS. Please find a zip file attached: 'alsa-info_hdajackretask-unconnected-pins' ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-10-generic 4.4.0-10.25 ProcVersionSignature: Ubuntu 4.4.0-10.25-generic 4.4.3 Uname: Linux 4.4.0-10-generic x86_64 ApportVersion: 2.20-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: aljosa 1776 F pulseaudio CurrentDesktop: Unity Date: Sun Mar 6 11:02:21 2016 HibernationDevice: RESUME=UUID=ac022671-63df-40ae-bffe-66fff3b35125 InstallationDate: Installed on 2016-03-05 (0 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160304) MachineType: LENOVO 80Q0 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-10-generic.efi.signed root=UUID=aa4325c4-4b4c-4372-b8ca-a66c3e5b2aa6 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-10-generic N/A linux-backports-modules-4.4.0-10-generic N/A linux-firmware1.156 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/31/2016 dmi.bios.vendor: LENOVO dmi.bios.version: CDCN30WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: Allsparks 7A dmi.board.vendor: LENOVO dmi.board.version: NO DPK dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad Y700-17ISK dmi.modalias: dmi:bvnLENOVO:bvrCDCN30WW:bd01/31/2016:svnLENOVO:pn80Q0:pvrLenovoideapadY700-17ISK:rvnLENOVO:rnAllsparks7A:rvrNODPK:cvnLENOVO:ct10:cvrLenovoideapadY700-17ISK: dmi.product.name: 80Q0 dmi.product.version: Lenovo ideapad Y700-17ISK dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1553685/+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 1553685] Re: Lenovo Y700-17ISK subwoofer doesn't work
I see. Is there still no solution to this? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1553685 Title: Lenovo Y700-17ISK subwoofer doesn't work Status in alsa-driver package in Ubuntu: Confirmed Bug description: Lenovo Y700-17ISK (Intel Core i7-6700HQ/RAM 16GB/SSD 512GB/Nvidia GTX960M 4GB) Operating system: Ubuntu 16.04 (xenial-desktop-amd64.iso 04-Mar-2016, kernel 4.4.0-10-generic, nvidia 361.28) Problem: Notebook subwoofer doesn't work. Judging from alsa-info.sh output, there is no pin declared for the bass output by BIOS. Please find a zip file attached: 'alsa-info_hdajackretask-unconnected-pins' ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-10-generic 4.4.0-10.25 ProcVersionSignature: Ubuntu 4.4.0-10.25-generic 4.4.3 Uname: Linux 4.4.0-10-generic x86_64 ApportVersion: 2.20-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: aljosa 1776 F pulseaudio CurrentDesktop: Unity Date: Sun Mar 6 11:02:21 2016 HibernationDevice: RESUME=UUID=ac022671-63df-40ae-bffe-66fff3b35125 InstallationDate: Installed on 2016-03-05 (0 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160304) MachineType: LENOVO 80Q0 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-10-generic.efi.signed root=UUID=aa4325c4-4b4c-4372-b8ca-a66c3e5b2aa6 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-10-generic N/A linux-backports-modules-4.4.0-10-generic N/A linux-firmware1.156 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/31/2016 dmi.bios.vendor: LENOVO dmi.bios.version: CDCN30WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: Allsparks 7A dmi.board.vendor: LENOVO dmi.board.version: NO DPK dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad Y700-17ISK dmi.modalias: dmi:bvnLENOVO:bvrCDCN30WW:bd01/31/2016:svnLENOVO:pn80Q0:pvrLenovoideapadY700-17ISK:rvnLENOVO:rnAllsparks7A:rvrNODPK:cvnLENOVO:ct10:cvrLenovoideapadY700-17ISK: dmi.product.name: 80Q0 dmi.product.version: Lenovo ideapad Y700-17ISK dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1553685/+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 1553685] Re: Lenovo Y700-17ISK subwoofer doesn't work
2 years and no fix. Seems like our laptops are not meant for Linux. Why is Linux not mainstream on PC they ask. "Year of the Linux desktop", yeah we will keep dreaming. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1553685 Title: Lenovo Y700-17ISK subwoofer doesn't work Status in alsa-driver package in Ubuntu: Confirmed Bug description: Lenovo Y700-17ISK (Intel Core i7-6700HQ/RAM 16GB/SSD 512GB/Nvidia GTX960M 4GB) Operating system: Ubuntu 16.04 (xenial-desktop-amd64.iso 04-Mar-2016, kernel 4.4.0-10-generic, nvidia 361.28) Problem: Notebook subwoofer doesn't work. Judging from alsa-info.sh output, there is no pin declared for the bass output by BIOS. Please find a zip file attached: 'alsa-info_hdajackretask-unconnected-pins' ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-10-generic 4.4.0-10.25 ProcVersionSignature: Ubuntu 4.4.0-10.25-generic 4.4.3 Uname: Linux 4.4.0-10-generic x86_64 ApportVersion: 2.20-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: aljosa 1776 F pulseaudio CurrentDesktop: Unity Date: Sun Mar 6 11:02:21 2016 HibernationDevice: RESUME=UUID=ac022671-63df-40ae-bffe-66fff3b35125 InstallationDate: Installed on 2016-03-05 (0 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160304) MachineType: LENOVO 80Q0 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-10-generic.efi.signed root=UUID=aa4325c4-4b4c-4372-b8ca-a66c3e5b2aa6 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-10-generic N/A linux-backports-modules-4.4.0-10-generic N/A linux-firmware1.156 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/31/2016 dmi.bios.vendor: LENOVO dmi.bios.version: CDCN30WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: Allsparks 7A dmi.board.vendor: LENOVO dmi.board.version: NO DPK dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad Y700-17ISK dmi.modalias: dmi:bvnLENOVO:bvrCDCN30WW:bd01/31/2016:svnLENOVO:pn80Q0:pvrLenovoideapadY700-17ISK:rvnLENOVO:rnAllsparks7A:rvrNODPK:cvnLENOVO:ct10:cvrLenovoideapadY700-17ISK: dmi.product.name: 80Q0 dmi.product.version: Lenovo ideapad Y700-17ISK dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1553685/+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 1553685] Re: Lenovo Y700-17ISK subwoofer doesn't work
I have got the same problem too on Lenovo y720. Speakers sound so tinny, no deep bass at all, and the subwoofer does not works at all. I don't know if it's of any help, but when I install Ubuntu in virtualbox, I suddenly have at least double the amount of audio settings, everything from subwoofer to deep audio, to bass, to high quality audio is working. Alsamixer also got lots of more settings. In the virtualbox, the audio chip for some reason went from Realtek ALC233 (on native ubuntu), to Analog devices AD1980. The sound card went from just intel HDA on native ubuntu, to Intel 82801AA-ICH. Follow my post with pics on askubuntu: https://askubuntu.com/questions/1070640/ubuntu-drivers-in-virtual-machine-different-than-native-ubuntu -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1553685 Title: Lenovo Y700-17ISK subwoofer doesn't work Status in alsa-driver package in Ubuntu: Confirmed Bug description: Lenovo Y700-17ISK (Intel Core i7-6700HQ/RAM 16GB/SSD 512GB/Nvidia GTX960M 4GB) Operating system: Ubuntu 16.04 (xenial-desktop-amd64.iso 04-Mar-2016, kernel 4.4.0-10-generic, nvidia 361.28) Problem: Notebook subwoofer doesn't work. Judging from alsa-info.sh output, there is no pin declared for the bass output by BIOS. Please find a zip file attached: 'alsa-info_hdajackretask-unconnected-pins' ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-10-generic 4.4.0-10.25 ProcVersionSignature: Ubuntu 4.4.0-10.25-generic 4.4.3 Uname: Linux 4.4.0-10-generic x86_64 ApportVersion: 2.20-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: aljosa 1776 F pulseaudio CurrentDesktop: Unity Date: Sun Mar 6 11:02:21 2016 HibernationDevice: RESUME=UUID=ac022671-63df-40ae-bffe-66fff3b35125 InstallationDate: Installed on 2016-03-05 (0 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160304) MachineType: LENOVO 80Q0 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-10-generic.efi.signed root=UUID=aa4325c4-4b4c-4372-b8ca-a66c3e5b2aa6 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-10-generic N/A linux-backports-modules-4.4.0-10-generic N/A linux-firmware1.156 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/31/2016 dmi.bios.vendor: LENOVO dmi.bios.version: CDCN30WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: Allsparks 7A dmi.board.vendor: LENOVO dmi.board.version: NO DPK dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad Y700-17ISK dmi.modalias: dmi:bvnLENOVO:bvrCDCN30WW:bd01/31/2016:svnLENOVO:pn80Q0:pvrLenovoideapadY700-17ISK:rvnLENOVO:rnAllsparks7A:rvrNODPK:cvnLENOVO:ct10:cvrLenovoideapadY700-17ISK: dmi.product.name: 80Q0 dmi.product.version: Lenovo ideapad Y700-17ISK dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1553685/+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 1553685] Re: Lenovo Y700-17ISK subwoofer doesn't work
I have got the same problem too on Lenovo y720. Speakers sound so tinny, no deep bass at all, and the subwoofer does not works at all. I don't know if it's of any help, but when I install Ubuntu in virtualbox, I suddenly have at least double the amount of audio settings, everything from subwoofer to deep audio, to bass, to high quality audio is working. Alsamixer also got lots of more settings. In the virtualbox, the audio chip for some reason went from Realtek ALC233 (on native ubuntu), to Analog devices AD1980. The sound card went from just intel HDA on native ubuntu, to Intel 82801AA-ICH. In the virtualbox, the audio chip for some reason went from Realtek ALC233 (on native ubuntu), to Analog devices AD1980. The sound card went from just intel HDA on native ubuntu, to Intel 82801AA-ICH Follow my post with pics on askubuntu: https://askubuntu.com/questions/1070640/ubuntu-drivers-in-virtual-machine-different-than-native-ubuntu -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1553685 Title: Lenovo Y700-17ISK subwoofer doesn't work Status in alsa-driver package in Ubuntu: Confirmed Bug description: Lenovo Y700-17ISK (Intel Core i7-6700HQ/RAM 16GB/SSD 512GB/Nvidia GTX960M 4GB) Operating system: Ubuntu 16.04 (xenial-desktop-amd64.iso 04-Mar-2016, kernel 4.4.0-10-generic, nvidia 361.28) Problem: Notebook subwoofer doesn't work. Judging from alsa-info.sh output, there is no pin declared for the bass output by BIOS. Please find a zip file attached: 'alsa-info_hdajackretask-unconnected-pins' ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-10-generic 4.4.0-10.25 ProcVersionSignature: Ubuntu 4.4.0-10.25-generic 4.4.3 Uname: Linux 4.4.0-10-generic x86_64 ApportVersion: 2.20-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: aljosa 1776 F pulseaudio CurrentDesktop: Unity Date: Sun Mar 6 11:02:21 2016 HibernationDevice: RESUME=UUID=ac022671-63df-40ae-bffe-66fff3b35125 InstallationDate: Installed on 2016-03-05 (0 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160304) MachineType: LENOVO 80Q0 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-10-generic.efi.signed root=UUID=aa4325c4-4b4c-4372-b8ca-a66c3e5b2aa6 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-10-generic N/A linux-backports-modules-4.4.0-10-generic N/A linux-firmware1.156 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/31/2016 dmi.bios.vendor: LENOVO dmi.bios.version: CDCN30WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: Allsparks 7A dmi.board.vendor: LENOVO dmi.board.version: NO DPK dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad Y700-17ISK dmi.modalias: dmi:bvnLENOVO:bvrCDCN30WW:bd01/31/2016:svnLENOVO:pn80Q0:pvrLenovoideapadY700-17ISK:rvnLENOVO:rnAllsparks7A:rvrNODPK:cvnLENOVO:ct10:cvrLenovoideapadY700-17ISK: dmi.product.name: 80Q0 dmi.product.version: Lenovo ideapad Y700-17ISK dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1553685/+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 1553685] Re: Lenovo Y700-17ISK subwoofer doesn't work
I have got the same problem too on Lenovo y720. Speakers sound so tinny, no deeps bass at all, makes the laptop feel so cheap. Subwoofer does not works at all. I don't know if it's of any help, but when install Ubuntu in virtualbox, I suddenly have at least double the amount of audio settings, everything from subwoofer to deep audio, to bass, to high quality audio is working. Alsamixer also got lots of more settings. In the virtualbox, the audio chip for some reason went from Realtek ALC233 (on native ubuntu), to Analog devices AD1980. The sound card went from just intel HDA on native ubuntu, to Intel 82801AA-ICH. In the virtualbox, the audio chip for some reason went from Realtek ALC233 (on native ubuntu), to Analog devices AD1980. The sound card went from just intel HDA on native ubuntu, to Intel 82801AA-ICH -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1553685 Title: Lenovo Y700-17ISK subwoofer doesn't work Status in alsa-driver package in Ubuntu: Confirmed Bug description: Lenovo Y700-17ISK (Intel Core i7-6700HQ/RAM 16GB/SSD 512GB/Nvidia GTX960M 4GB) Operating system: Ubuntu 16.04 (xenial-desktop-amd64.iso 04-Mar-2016, kernel 4.4.0-10-generic, nvidia 361.28) Problem: Notebook subwoofer doesn't work. Judging from alsa-info.sh output, there is no pin declared for the bass output by BIOS. Please find a zip file attached: 'alsa-info_hdajackretask-unconnected-pins' ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-10-generic 4.4.0-10.25 ProcVersionSignature: Ubuntu 4.4.0-10.25-generic 4.4.3 Uname: Linux 4.4.0-10-generic x86_64 ApportVersion: 2.20-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: aljosa 1776 F pulseaudio CurrentDesktop: Unity Date: Sun Mar 6 11:02:21 2016 HibernationDevice: RESUME=UUID=ac022671-63df-40ae-bffe-66fff3b35125 InstallationDate: Installed on 2016-03-05 (0 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160304) MachineType: LENOVO 80Q0 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-10-generic.efi.signed root=UUID=aa4325c4-4b4c-4372-b8ca-a66c3e5b2aa6 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-10-generic N/A linux-backports-modules-4.4.0-10-generic N/A linux-firmware1.156 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/31/2016 dmi.bios.vendor: LENOVO dmi.bios.version: CDCN30WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: Allsparks 7A dmi.board.vendor: LENOVO dmi.board.version: NO DPK dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad Y700-17ISK dmi.modalias: dmi:bvnLENOVO:bvrCDCN30WW:bd01/31/2016:svnLENOVO:pn80Q0:pvrLenovoideapadY700-17ISK:rvnLENOVO:rnAllsparks7A:rvrNODPK:cvnLENOVO:ct10:cvrLenovoideapadY700-17ISK: dmi.product.name: 80Q0 dmi.product.version: Lenovo ideapad Y700-17ISK dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1553685/+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 1553685] Re: Lenovo Y700-17ISK subwoofer doesn't work
In the virtualbox, the audio chip for some reason went from Realtek ALC233 (on native ubuntu), to Analog devices AD1980. The sound card went from just intel HDA on native ubuntu, to Intel 82801AA-ICH -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1553685 Title: Lenovo Y700-17ISK subwoofer doesn't work Status in alsa-driver package in Ubuntu: Confirmed Bug description: Lenovo Y700-17ISK (Intel Core i7-6700HQ/RAM 16GB/SSD 512GB/Nvidia GTX960M 4GB) Operating system: Ubuntu 16.04 (xenial-desktop-amd64.iso 04-Mar-2016, kernel 4.4.0-10-generic, nvidia 361.28) Problem: Notebook subwoofer doesn't work. Judging from alsa-info.sh output, there is no pin declared for the bass output by BIOS. Please find a zip file attached: 'alsa-info_hdajackretask-unconnected-pins' ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-10-generic 4.4.0-10.25 ProcVersionSignature: Ubuntu 4.4.0-10.25-generic 4.4.3 Uname: Linux 4.4.0-10-generic x86_64 ApportVersion: 2.20-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: aljosa 1776 F pulseaudio CurrentDesktop: Unity Date: Sun Mar 6 11:02:21 2016 HibernationDevice: RESUME=UUID=ac022671-63df-40ae-bffe-66fff3b35125 InstallationDate: Installed on 2016-03-05 (0 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160304) MachineType: LENOVO 80Q0 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-10-generic.efi.signed root=UUID=aa4325c4-4b4c-4372-b8ca-a66c3e5b2aa6 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-10-generic N/A linux-backports-modules-4.4.0-10-generic N/A linux-firmware1.156 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/31/2016 dmi.bios.vendor: LENOVO dmi.bios.version: CDCN30WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: Allsparks 7A dmi.board.vendor: LENOVO dmi.board.version: NO DPK dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad Y700-17ISK dmi.modalias: dmi:bvnLENOVO:bvrCDCN30WW:bd01/31/2016:svnLENOVO:pn80Q0:pvrLenovoideapadY700-17ISK:rvnLENOVO:rnAllsparks7A:rvrNODPK:cvnLENOVO:ct10:cvrLenovoideapadY700-17ISK: dmi.product.name: 80Q0 dmi.product.version: Lenovo ideapad Y700-17ISK dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1553685/+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 1553685] Re: Lenovo Y700-17ISK subwoofer doesn't work
Could it be that Ubuntu install the wrong audio driver for our chipsets? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1553685 Title: Lenovo Y700-17ISK subwoofer doesn't work Status in alsa-driver package in Ubuntu: Confirmed Bug description: Lenovo Y700-17ISK (Intel Core i7-6700HQ/RAM 16GB/SSD 512GB/Nvidia GTX960M 4GB) Operating system: Ubuntu 16.04 (xenial-desktop-amd64.iso 04-Mar-2016, kernel 4.4.0-10-generic, nvidia 361.28) Problem: Notebook subwoofer doesn't work. Judging from alsa-info.sh output, there is no pin declared for the bass output by BIOS. Please find a zip file attached: 'alsa-info_hdajackretask-unconnected-pins' ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-10-generic 4.4.0-10.25 ProcVersionSignature: Ubuntu 4.4.0-10.25-generic 4.4.3 Uname: Linux 4.4.0-10-generic x86_64 ApportVersion: 2.20-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: aljosa 1776 F pulseaudio CurrentDesktop: Unity Date: Sun Mar 6 11:02:21 2016 HibernationDevice: RESUME=UUID=ac022671-63df-40ae-bffe-66fff3b35125 InstallationDate: Installed on 2016-03-05 (0 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160304) MachineType: LENOVO 80Q0 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-10-generic.efi.signed root=UUID=aa4325c4-4b4c-4372-b8ca-a66c3e5b2aa6 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-10-generic N/A linux-backports-modules-4.4.0-10-generic N/A linux-firmware1.156 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/31/2016 dmi.bios.vendor: LENOVO dmi.bios.version: CDCN30WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: Allsparks 7A dmi.board.vendor: LENOVO dmi.board.version: NO DPK dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad Y700-17ISK dmi.modalias: dmi:bvnLENOVO:bvrCDCN30WW:bd01/31/2016:svnLENOVO:pn80Q0:pvrLenovoideapadY700-17ISK:rvnLENOVO:rnAllsparks7A:rvrNODPK:cvnLENOVO:ct10:cvrLenovoideapadY700-17ISK: dmi.product.name: 80Q0 dmi.product.version: Lenovo ideapad Y700-17ISK dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1553685/+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 1553685] Re: Lenovo Y700-17ISK subwoofer doesn't work
I don't know if it's of any help, but when install Ubuntu in virtualbox, I suddenly have at least double the amount of audio settings, everything from subwoofer to deep audio, to bass, to high quality audio is working. Alsamixer also got lots of more settings. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1553685 Title: Lenovo Y700-17ISK subwoofer doesn't work Status in alsa-driver package in Ubuntu: Confirmed Bug description: Lenovo Y700-17ISK (Intel Core i7-6700HQ/RAM 16GB/SSD 512GB/Nvidia GTX960M 4GB) Operating system: Ubuntu 16.04 (xenial-desktop-amd64.iso 04-Mar-2016, kernel 4.4.0-10-generic, nvidia 361.28) Problem: Notebook subwoofer doesn't work. Judging from alsa-info.sh output, there is no pin declared for the bass output by BIOS. Please find a zip file attached: 'alsa-info_hdajackretask-unconnected-pins' ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-10-generic 4.4.0-10.25 ProcVersionSignature: Ubuntu 4.4.0-10.25-generic 4.4.3 Uname: Linux 4.4.0-10-generic x86_64 ApportVersion: 2.20-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: aljosa 1776 F pulseaudio CurrentDesktop: Unity Date: Sun Mar 6 11:02:21 2016 HibernationDevice: RESUME=UUID=ac022671-63df-40ae-bffe-66fff3b35125 InstallationDate: Installed on 2016-03-05 (0 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160304) MachineType: LENOVO 80Q0 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-10-generic.efi.signed root=UUID=aa4325c4-4b4c-4372-b8ca-a66c3e5b2aa6 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-10-generic N/A linux-backports-modules-4.4.0-10-generic N/A linux-firmware1.156 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/31/2016 dmi.bios.vendor: LENOVO dmi.bios.version: CDCN30WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: Allsparks 7A dmi.board.vendor: LENOVO dmi.board.version: NO DPK dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad Y700-17ISK dmi.modalias: dmi:bvnLENOVO:bvrCDCN30WW:bd01/31/2016:svnLENOVO:pn80Q0:pvrLenovoideapadY700-17ISK:rvnLENOVO:rnAllsparks7A:rvrNODPK:cvnLENOVO:ct10:cvrLenovoideapadY700-17ISK: dmi.product.name: 80Q0 dmi.product.version: Lenovo ideapad Y700-17ISK dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1553685/+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 1553685] Re: Lenovo Y700-17ISK subwoofer doesn't work
This should really not me at medium importance. It affects lots of people and it's not a small thing, it's straight up hardware not working. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1553685 Title: Lenovo Y700-17ISK subwoofer doesn't work Status in alsa-driver package in Ubuntu: Confirmed Bug description: Lenovo Y700-17ISK (Intel Core i7-6700HQ/RAM 16GB/SSD 512GB/Nvidia GTX960M 4GB) Operating system: Ubuntu 16.04 (xenial-desktop-amd64.iso 04-Mar-2016, kernel 4.4.0-10-generic, nvidia 361.28) Problem: Notebook subwoofer doesn't work. Judging from alsa-info.sh output, there is no pin declared for the bass output by BIOS. Please find a zip file attached: 'alsa-info_hdajackretask-unconnected-pins' ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-10-generic 4.4.0-10.25 ProcVersionSignature: Ubuntu 4.4.0-10.25-generic 4.4.3 Uname: Linux 4.4.0-10-generic x86_64 ApportVersion: 2.20-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: aljosa 1776 F pulseaudio CurrentDesktop: Unity Date: Sun Mar 6 11:02:21 2016 HibernationDevice: RESUME=UUID=ac022671-63df-40ae-bffe-66fff3b35125 InstallationDate: Installed on 2016-03-05 (0 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160304) MachineType: LENOVO 80Q0 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-10-generic.efi.signed root=UUID=aa4325c4-4b4c-4372-b8ca-a66c3e5b2aa6 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-10-generic N/A linux-backports-modules-4.4.0-10-generic N/A linux-firmware1.156 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/31/2016 dmi.bios.vendor: LENOVO dmi.bios.version: CDCN30WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: Allsparks 7A dmi.board.vendor: LENOVO dmi.board.version: NO DPK dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad Y700-17ISK dmi.modalias: dmi:bvnLENOVO:bvrCDCN30WW:bd01/31/2016:svnLENOVO:pn80Q0:pvrLenovoideapadY700-17ISK:rvnLENOVO:rnAllsparks7A:rvrNODPK:cvnLENOVO:ct10:cvrLenovoideapadY700-17ISK: dmi.product.name: 80Q0 dmi.product.version: Lenovo ideapad Y700-17ISK dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1553685/+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 1553685] Re: Lenovo Y700-17ISK subwoofer doesn't work
I have got the same problem too on Lenovo y720. Speakers sound so tinny, no deeps bass at all, makes the laptop feel so cheap. Subwoofer does not works at all. This problem is the only thing holding me back from using Ubuntu instead of Windows. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1553685 Title: Lenovo Y700-17ISK subwoofer doesn't work Status in alsa-driver package in Ubuntu: Confirmed Bug description: Lenovo Y700-17ISK (Intel Core i7-6700HQ/RAM 16GB/SSD 512GB/Nvidia GTX960M 4GB) Operating system: Ubuntu 16.04 (xenial-desktop-amd64.iso 04-Mar-2016, kernel 4.4.0-10-generic, nvidia 361.28) Problem: Notebook subwoofer doesn't work. Judging from alsa-info.sh output, there is no pin declared for the bass output by BIOS. Please find a zip file attached: 'alsa-info_hdajackretask-unconnected-pins' ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-10-generic 4.4.0-10.25 ProcVersionSignature: Ubuntu 4.4.0-10.25-generic 4.4.3 Uname: Linux 4.4.0-10-generic x86_64 ApportVersion: 2.20-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: aljosa 1776 F pulseaudio CurrentDesktop: Unity Date: Sun Mar 6 11:02:21 2016 HibernationDevice: RESUME=UUID=ac022671-63df-40ae-bffe-66fff3b35125 InstallationDate: Installed on 2016-03-05 (0 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160304) MachineType: LENOVO 80Q0 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-10-generic.efi.signed root=UUID=aa4325c4-4b4c-4372-b8ca-a66c3e5b2aa6 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-10-generic N/A linux-backports-modules-4.4.0-10-generic N/A linux-firmware1.156 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/31/2016 dmi.bios.vendor: LENOVO dmi.bios.version: CDCN30WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: Allsparks 7A dmi.board.vendor: LENOVO dmi.board.version: NO DPK dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad Y700-17ISK dmi.modalias: dmi:bvnLENOVO:bvrCDCN30WW:bd01/31/2016:svnLENOVO:pn80Q0:pvrLenovoideapadY700-17ISK:rvnLENOVO:rnAllsparks7A:rvrNODPK:cvnLENOVO:ct10:cvrLenovoideapadY700-17ISK: dmi.product.name: 80Q0 dmi.product.version: Lenovo ideapad Y700-17ISK dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1553685/+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 1788839] [NEW] nautilus crashed with SIGSEGV in __GI___libc_free()
Public bug reported: The nautilus closed all of a sudden ProblemType: Crash DistroRelease: Ubuntu 18.04 Package: nautilus 1:3.26.3-0ubuntu4 ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18 Uname: Linux 4.15.0-33-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CrashCounter: 1 CurrentDesktop: ubuntu:GNOME Date: Fri Aug 24 13:36:01 2018 ExecutablePath: /usr/bin/nautilus GsettingsChanges: b'org.gnome.nautilus.window-state' b'sidebar-width' b'216' b'org.gnome.nautilus.window-state' b'geometry' b"'960x1011+50+27'" b'org.gnome.nautilus.window-state' b'maximized' b'true' b'org.gnome.nautilus.icon-view' b'default-zoom-level' b"'standard'" b'org.gnome.nautilus.list-view' b'default-column-order' b"['name', 'size', 'type', 'owner', 'group', 'permissions', 'mime_type', 'where', 'date_modified', 'date_modified_with_time', 'date_accessed', 'recency']" ProcCmdline: /usr/bin/nautilus --gapplication-service SegvAnalysis: Segfault happened at: 0x7f69bc07298d <__GI___libc_free+61>:mov -0x8(%rdi),%rsi PC (0x7f69bc07298d) ok source "-0x8(%rdi)" (0x21a8) not located in a known VMA region (needed readable region)! destination "%rsi" ok Stack memory exhausted (SP below stack segment) SegvReason: reading NULL VMA Signal: 11 SourcePackage: nautilus StacktraceTop: __GI___libc_free (mem=0x21b0) at malloc.c:3103 g_mount_spec_unref () at /usr/lib/x86_64-linux-gnu/gvfs/libgvfscommon.so () at /usr/lib/x86_64-linux-gnu/gio/modules/libgvfsdbus.so g_object_unref () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 () Title: nautilus crashed with SIGSEGV in __GI___libc_free() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo usr_lib_nautilus: ** Affects: nautilus (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-crash bionic need-amd64-retrace ** Information type changed from Private to Public -- 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/1788839 Title: nautilus crashed with SIGSEGV in __GI___libc_free() Status in nautilus package in Ubuntu: New Bug description: The nautilus closed all of a sudden ProblemType: Crash DistroRelease: Ubuntu 18.04 Package: nautilus 1:3.26.3-0ubuntu4 ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18 Uname: Linux 4.15.0-33-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CrashCounter: 1 CurrentDesktop: ubuntu:GNOME Date: Fri Aug 24 13:36:01 2018 ExecutablePath: /usr/bin/nautilus GsettingsChanges: b'org.gnome.nautilus.window-state' b'sidebar-width' b'216' b'org.gnome.nautilus.window-state' b'geometry' b"'960x1011+50+27'" b'org.gnome.nautilus.window-state' b'maximized' b'true' b'org.gnome.nautilus.icon-view' b'default-zoom-level' b"'standard'" b'org.gnome.nautilus.list-view' b'default-column-order' b"['name', 'size', 'type', 'owner', 'group', 'permissions', 'mime_type', 'where', 'date_modified', 'date_modified_with_time', 'date_accessed', 'recency']" ProcCmdline: /usr/bin/nautilus --gapplication-service SegvAnalysis: Segfault happened at: 0x7f69bc07298d <__GI___libc_free+61>: mov -0x8(%rdi),%rsi PC (0x7f69bc07298d) ok source "-0x8(%rdi)" (0x21a8) not located in a known VMA region (needed readable region)! destination "%rsi" ok Stack memory exhausted (SP below stack segment) SegvReason: reading NULL VMA Signal: 11 SourcePackage: nautilus StacktraceTop: __GI___libc_free (mem=0x21b0) at malloc.c:3103 g_mount_spec_unref () at /usr/lib/x86_64-linux-gnu/gvfs/libgvfscommon.so () at /usr/lib/x86_64-linux-gnu/gio/modules/libgvfsdbus.so g_object_unref () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 () Title: nautilus crashed with SIGSEGV in __GI___libc_free() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo usr_lib_nautilus: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1788839/+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 1788036] Re: nautilus crashed with SIGSEGV in tcache_get()
** Information type changed from Private to Public -- 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/1788036 Title: nautilus crashed with SIGSEGV in tcache_get() Status in nautilus package in Ubuntu: New Bug description: nautilus closed all of a sudden ProblemType: Crash DistroRelease: Ubuntu 18.04 Package: nautilus 1:3.26.3-0ubuntu4 ProcVersionSignature: Ubuntu 4.15.0-32.35-generic 4.15.18 Uname: Linux 4.15.0-32-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AssertionMessage: double free or corruption (fasttop) CrashCounter: 1 CurrentDesktop: ubuntu:GNOME Date: Mon Aug 20 23:26:18 2018 ExecutablePath: /usr/bin/nautilus GsettingsChanges: b'org.gnome.nautilus.window-state' b'sidebar-width' b'216' b'org.gnome.nautilus.window-state' b'geometry' b"'960x1011+960+27'" b'org.gnome.nautilus.icon-view' b'default-zoom-level' b"'standard'" b'org.gnome.nautilus.list-view' b'default-column-order' b"['name', 'size', 'type', 'owner', 'group', 'permissions', 'mime_type', 'where', 'date_modified', 'date_modified_with_time', 'date_accessed', 'recency']" ProcCmdline: /usr/bin/nautilus --gapplication-service SegvAnalysis: Segfault happened at: 0x7f7f019c1207 <__GI___libc_malloc+407>: mov (%rdx),%rdi PC (0x7f7f019c1207) ok source "(%rdx)" (0x6f73692e) not located in a known VMA region (needed readable region)! destination "%rdi" ok Stack memory exhausted (SP below stack segment) SegvReason: reading unknown VMA Signal: 11 SourcePackage: nautilus StacktraceTop: tcache_get (tc_idx=0) at malloc.c:2943 __GI___libc_malloc (bytes=17) at malloc.c:3050 g_malloc () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 g_strndup () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 g_strsplit () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 Title: nautilus crashed with SIGSEGV in tcache_get() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo usr_lib_nautilus: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1788036/+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 1786650] [NEW] nautilus crashed with SIGSEGV in tcache_get()
Public bug reported: nautilus closed all of a sudden ProblemType: Crash DistroRelease: Ubuntu 18.04 Package: nautilus 1:3.26.3-0ubuntu4 ProcVersionSignature: Ubuntu 4.15.0-30.32-generic 4.15.18 Uname: Linux 4.15.0-30-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CrashCounter: 1 CurrentDesktop: ubuntu:GNOME Date: Sun Aug 12 01:54:19 2018 ExecutablePath: /usr/bin/nautilus GsettingsChanges: b'org.gnome.nautilus.window-state' b'sidebar-width' b'216' b'org.gnome.nautilus.window-state' b'geometry' b"'960x1011+960+27'" b'org.gnome.nautilus.window-state' b'maximized' b'true' b'org.gnome.nautilus.icon-view' b'default-zoom-level' b"'standard'" b'org.gnome.nautilus.list-view' b'default-column-order' b"['name', 'size', 'type', 'owner', 'group', 'permissions', 'mime_type', 'where', 'date_modified', 'date_modified_with_time', 'date_accessed', 'recency']" ProcCmdline: /usr/bin/nautilus --gapplication-service SegvAnalysis: Segfault happened at: 0x7f66a9b7c207 <__GI___libc_malloc+407>: mov (%rdx),%rdi PC (0x7f66a9b7c207) ok source "(%rdx)" (0x1) not located in a known VMA region (needed readable region)! destination "%rdi" ok Stack memory exhausted (SP below stack segment) SegvReason: reading unknown VMA Signal: 11 SourcePackage: nautilus StacktraceTop: tcache_get (tc_idx=0) at malloc.c:2943 __GI___libc_malloc (bytes=1) at malloc.c:3050 g_malloc () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 g_strdup () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 g_strsplit () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 Title: nautilus crashed with SIGSEGV in tcache_get() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo usr_lib_nautilus: ** Affects: nautilus (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-crash bionic need-amd64-retrace ** Information type changed from Private to Public -- 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/1786650 Title: nautilus crashed with SIGSEGV in tcache_get() Status in nautilus package in Ubuntu: New Bug description: nautilus closed all of a sudden ProblemType: Crash DistroRelease: Ubuntu 18.04 Package: nautilus 1:3.26.3-0ubuntu4 ProcVersionSignature: Ubuntu 4.15.0-30.32-generic 4.15.18 Uname: Linux 4.15.0-30-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CrashCounter: 1 CurrentDesktop: ubuntu:GNOME Date: Sun Aug 12 01:54:19 2018 ExecutablePath: /usr/bin/nautilus GsettingsChanges: b'org.gnome.nautilus.window-state' b'sidebar-width' b'216' b'org.gnome.nautilus.window-state' b'geometry' b"'960x1011+960+27'" b'org.gnome.nautilus.window-state' b'maximized' b'true' b'org.gnome.nautilus.icon-view' b'default-zoom-level' b"'standard'" b'org.gnome.nautilus.list-view' b'default-column-order' b"['name', 'size', 'type', 'owner', 'group', 'permissions', 'mime_type', 'where', 'date_modified', 'date_modified_with_time', 'date_accessed', 'recency']" ProcCmdline: /usr/bin/nautilus --gapplication-service SegvAnalysis: Segfault happened at: 0x7f66a9b7c207 <__GI___libc_malloc+407>: mov (%rdx),%rdi PC (0x7f66a9b7c207) ok source "(%rdx)" (0x1) not located in a known VMA region (needed readable region)! destination "%rdi" ok Stack memory exhausted (SP below stack segment) SegvReason: reading unknown VMA Signal: 11 SourcePackage: nautilus StacktraceTop: tcache_get (tc_idx=0) at malloc.c:2943 __GI___libc_malloc (bytes=1) at malloc.c:3050 g_malloc () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 g_strdup () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 g_strsplit () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 Title: nautilus crashed with SIGSEGV in tcache_get() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo usr_lib_nautilus: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1786650/+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 1785122] [NEW] nautilus crashed with SIGSEGV in _int_malloc()
Public bug reported: The nautilus closed all of a sudden ProblemType: Crash DistroRelease: Ubuntu 18.04 Package: nautilus 1:3.26.3-0ubuntu4 ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18 Uname: Linux 4.15.0-29-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CrashCounter: 1 CurrentDesktop: ubuntu:GNOME Date: Thu Aug 2 23:16:25 2018 ExecutablePath: /usr/bin/nautilus GsettingsChanges: b'org.gnome.nautilus.window-state' b'sidebar-width' b'196' b'org.gnome.nautilus.window-state' b'geometry' b"'960x1011+960+27'" b'org.gnome.nautilus.window-state' b'maximized' b'true' b'org.gnome.nautilus.icon-view' b'default-zoom-level' b"'standard'" ProcCmdline: /usr/bin/nautilus --gapplication-service SegvAnalysis: Segfault happened at: 0x7f34073e43c1 <_int_malloc+241>:mov 0x10(%rsi),%r9 PC (0x7f34073e43c1) ok source "0x10(%rsi)" (0x7f33dc01cb0010) not located in a known VMA region (needed readable region)! destination "%r9" ok Stack memory exhausted (SP below stack segment) SegvReason: reading unknown VMA Signal: 11 SourcePackage: nautilus StacktraceTop: _int_malloc (av=av@entry=0x7f33dc20, bytes=bytes@entry=33) at malloc.c:3612 _int_realloc (av=av@entry=0x7f33dc20, oldp=oldp@entry=0x7f33dc042890, oldsize=oldsize@entry=32, nb=nb@entry=48) at malloc.c:4570 __GI___libc_realloc (oldmem=0x7f33dc0428a0, bytes=32) at malloc.c:3230 g_realloc () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 Title: nautilus crashed with SIGSEGV in _int_malloc() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo usr_lib_nautilus: ** Affects: nautilus (Ubuntu) Importance: Medium Status: New ** Tags: amd64 apport-crash bionic ** Information type changed from Private to Public -- 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/1785122 Title: nautilus crashed with SIGSEGV in _int_malloc() Status in nautilus package in Ubuntu: New Bug description: The nautilus closed all of a sudden ProblemType: Crash DistroRelease: Ubuntu 18.04 Package: nautilus 1:3.26.3-0ubuntu4 ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18 Uname: Linux 4.15.0-29-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CrashCounter: 1 CurrentDesktop: ubuntu:GNOME Date: Thu Aug 2 23:16:25 2018 ExecutablePath: /usr/bin/nautilus GsettingsChanges: b'org.gnome.nautilus.window-state' b'sidebar-width' b'196' b'org.gnome.nautilus.window-state' b'geometry' b"'960x1011+960+27'" b'org.gnome.nautilus.window-state' b'maximized' b'true' b'org.gnome.nautilus.icon-view' b'default-zoom-level' b"'standard'" ProcCmdline: /usr/bin/nautilus --gapplication-service SegvAnalysis: Segfault happened at: 0x7f34073e43c1 <_int_malloc+241>: mov 0x10(%rsi),%r9 PC (0x7f34073e43c1) ok source "0x10(%rsi)" (0x7f33dc01cb0010) not located in a known VMA region (needed readable region)! destination "%r9" ok Stack memory exhausted (SP below stack segment) SegvReason: reading unknown VMA Signal: 11 SourcePackage: nautilus StacktraceTop: _int_malloc (av=av@entry=0x7f33dc20, bytes=bytes@entry=33) at malloc.c:3612 _int_realloc (av=av@entry=0x7f33dc20, oldp=oldp@entry=0x7f33dc042890, oldsize=oldsize@entry=32, nb=nb@entry=48) at malloc.c:4570 __GI___libc_realloc (oldmem=0x7f33dc0428a0, bytes=32) at malloc.c:3230 g_realloc () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 Title: nautilus crashed with SIGSEGV in _int_malloc() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo usr_lib_nautilus: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1785122/+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 1781826] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1781826/+attachment/5170434/+files/ProcCpuinfoMinimal.txt -- 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/1781826 Title: System logout when turn off the screen or suspend Ubuntu 18.04 Status in gnome-shell package in Ubuntu: Incomplete Bug description: When turn off the screen or suspend, and resume the system is logged out, this mostly happens with nvidia driver (390 or 396). I noticed that when close the lid and reopen the system is still working and all of a sudden it appears a login screen and when login all programs as killed as it was logged out. And most of times after login it locks and prompts an unlock screen. I tried to switch to nouveau driver and the problem seems not to happen, but that leaves me with a poor performance in terms of graphics. I tried to reset the setting in dconf using dconf-editor to reset the system recursively, at the beginning seems to be solved but it gets back. I need to mention that I faced the same problem when using budgie flavor, I thought that it might be a budgie problem but it appears to be a gnome problem since budgie is based on gnome and on both the problem happens when using Nvidia drivers. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 18.04 NonfreeKernelModules: nvidia_modeset nvidia Package: gnome-shell 3.28.2-0ubuntu0.18.04.1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18 Tags: bionic Uname: Linux 4.15.0-29-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 18.04 NonfreeKernelModules: nvidia_modeset nvidia Package: gnome-shell 3.28.2-0ubuntu0.18.04.1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18 Tags: bionic Uname: Linux 4.15.0-29-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 DisplayManager: gdm3 DistroRelease: Ubuntu 18.04 NonfreeKernelModules: nvidia_modeset nvidia Package: gnome-shell 3.28.2-0ubuntu0.18.04.1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18 Tags: bionic Uname: Linux 4.15.0-29-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1781826/+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 1781826] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1781826/+attachment/5170435/+files/ProcEnviron.txt -- 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/1781826 Title: System logout when turn off the screen or suspend Ubuntu 18.04 Status in gnome-shell package in Ubuntu: Incomplete Bug description: When turn off the screen or suspend, and resume the system is logged out, this mostly happens with nvidia driver (390 or 396). I noticed that when close the lid and reopen the system is still working and all of a sudden it appears a login screen and when login all programs as killed as it was logged out. And most of times after login it locks and prompts an unlock screen. I tried to switch to nouveau driver and the problem seems not to happen, but that leaves me with a poor performance in terms of graphics. I tried to reset the setting in dconf using dconf-editor to reset the system recursively, at the beginning seems to be solved but it gets back. I need to mention that I faced the same problem when using budgie flavor, I thought that it might be a budgie problem but it appears to be a gnome problem since budgie is based on gnome and on both the problem happens when using Nvidia drivers. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 18.04 NonfreeKernelModules: nvidia_modeset nvidia Package: gnome-shell 3.28.2-0ubuntu0.18.04.1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18 Tags: bionic Uname: Linux 4.15.0-29-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 18.04 NonfreeKernelModules: nvidia_modeset nvidia Package: gnome-shell 3.28.2-0ubuntu0.18.04.1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18 Tags: bionic Uname: Linux 4.15.0-29-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 DisplayManager: gdm3 DistroRelease: Ubuntu 18.04 NonfreeKernelModules: nvidia_modeset nvidia Package: gnome-shell 3.28.2-0ubuntu0.18.04.1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18 Tags: bionic Uname: Linux 4.15.0-29-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1781826/+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 1781826] Re: System logout when turn off the screen or suspend Ubuntu 18.04
apport information ** Description changed: When turn off the screen or suspend, and resume the system is logged out, this mostly happens with nvidia driver (390 or 396). I noticed that when close the lid and reopen the system is still working and all of a sudden it appears a login screen and when login all programs as killed as it was logged out. And most of times after login it locks and prompts an unlock screen. I tried to switch to nouveau driver and the problem seems not to happen, but that leaves me with a poor performance in terms of graphics. I tried to reset the setting in dconf using dconf-editor to reset the system recursively, at the beginning seems to be solved but it gets back. I need to mention that I faced the same problem when using budgie flavor, I thought that it might be a budgie problem but it appears to be a gnome problem since budgie is based on gnome and on both the problem happens when using Nvidia drivers. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 18.04 NonfreeKernelModules: nvidia_modeset nvidia Package: gnome-shell 3.28.2-0ubuntu0.18.04.1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18 Tags: bionic Uname: Linux 4.15.0-29-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 18.04 NonfreeKernelModules: nvidia_modeset nvidia Package: gnome-shell 3.28.2-0ubuntu0.18.04.1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18 Tags: bionic Uname: Linux 4.15.0-29-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True + --- + ProblemType: Bug + ApportVersion: 2.20.9-0ubuntu7.2 + Architecture: amd64 + DisplayManager: gdm3 + DistroRelease: Ubuntu 18.04 + NonfreeKernelModules: nvidia_modeset nvidia + Package: gnome-shell 3.28.2-0ubuntu0.18.04.1 + PackageArchitecture: amd64 + ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18 + Tags: bionic + Uname: Linux 4.15.0-29-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: + + _MarkForUpload: True ** Attachment added: "Dependencies.txt" https://bugs.launchpad.net/bugs/1781826/+attachment/5170432/+files/Dependencies.txt -- 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/1781826 Title: System logout when turn off the screen or suspend Ubuntu 18.04 Status in gnome-shell package in Ubuntu: Incomplete Bug description: When turn off the screen or suspend, and resume the system is logged out, this mostly happens with nvidia driver (390 or 396). I noticed that when close the lid and reopen the system is still working and all of a sudden it appears a login screen and when login all programs as killed as it was logged out. And most of times after login it locks and prompts an unlock screen. I tried to switch to nouveau driver and the problem seems not to happen, but that leaves me with a poor performance in terms of graphics. I tried to reset the setting in dconf using dconf-editor to reset the system recursively, at the beginning seems to be solved but it gets back. I need to mention that I faced the same problem when using budgie flavor, I thought that it might be a budgie problem but it appears to be a gnome problem since budgie is based on gnome and on both the problem happens when using Nvidia drivers. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 18.04 NonfreeKernelModules: nvidia_modeset nvidia Package: gnome-shell 3.28.2-0ubuntu0.18.04.1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18 Tags: bionic Uname: Linux 4.15.0-29-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 18.04 NonfreeKernelModules: nvidia_modeset nvidia Package: gnome-shell 3.28.2-0ubuntu0.18.04.1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18 Tags: bionic Uname: Linux 4.15.0-29-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom
[Desktop-packages] [Bug 1781826] GsettingsChanges.txt
apport information ** Attachment added: "GsettingsChanges.txt" https://bugs.launchpad.net/bugs/1781826/+attachment/5170433/+files/GsettingsChanges.txt -- 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/1781826 Title: System logout when turn off the screen or suspend Ubuntu 18.04 Status in gnome-shell package in Ubuntu: Incomplete Bug description: When turn off the screen or suspend, and resume the system is logged out, this mostly happens with nvidia driver (390 or 396). I noticed that when close the lid and reopen the system is still working and all of a sudden it appears a login screen and when login all programs as killed as it was logged out. And most of times after login it locks and prompts an unlock screen. I tried to switch to nouveau driver and the problem seems not to happen, but that leaves me with a poor performance in terms of graphics. I tried to reset the setting in dconf using dconf-editor to reset the system recursively, at the beginning seems to be solved but it gets back. I need to mention that I faced the same problem when using budgie flavor, I thought that it might be a budgie problem but it appears to be a gnome problem since budgie is based on gnome and on both the problem happens when using Nvidia drivers. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 18.04 NonfreeKernelModules: nvidia_modeset nvidia Package: gnome-shell 3.28.2-0ubuntu0.18.04.1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18 Tags: bionic Uname: Linux 4.15.0-29-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 18.04 NonfreeKernelModules: nvidia_modeset nvidia Package: gnome-shell 3.28.2-0ubuntu0.18.04.1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18 Tags: bionic Uname: Linux 4.15.0-29-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 DisplayManager: gdm3 DistroRelease: Ubuntu 18.04 NonfreeKernelModules: nvidia_modeset nvidia Package: gnome-shell 3.28.2-0ubuntu0.18.04.1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18 Tags: bionic Uname: Linux 4.15.0-29-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1781826/+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 1784795] [NEW] Xorg crashed ( logged out when suspend or turn off the screen) with signal 7 in xf86VTEnter()
Public bug reported: When suspend (close the lid) and reopen it (resume) the system crashed and killed the session and prompt to login ( not to unlock) and when logging in all applications are killed (a new session started). ProblemType: Crash DistroRelease: Ubuntu 18.04 Package: xserver-xorg-core 2:1.19.6-1ubuntu4 ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18 Uname: Linux 4.15.0-29-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..03.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:03:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 390.48 Thu Mar 22 00:42:57 PDT 2018 GCC version: gcc version 7.3.0 (Ubuntu 7.3.0-16ubuntu3) ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CrashCounter: 1 Date: Wed Aug 1 10:15:33 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: nvidia, 390.48, 4.15.0-23-generic, x86_64: installed nvidia, 390.48, 4.15.0-29-generic, x86_64: installed ExecutablePath: /usr/lib/xorg/Xorg GraphicsCard: Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Lenovo HD Graphics 620 [17aa:39f1] Subsystem: Lenovo GM108M [GeForce 940MX] [17aa:39f1] MachineType: LENOVO 80SV ProcCmdline: /usr/lib/xorg/Xorg vt2 -displayfd 3 -auth /run/user/1000/gdm/Xauthority -background none -noreset -keeptty -verbose 3 ProcEnviron: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-29-generic root=UUID=d175c9ce-90fb-4afa-b2f7-51f8c3d9a9b6 ro quiet splash vt.handoff=1 Signal: 7 SourcePackage: nvidia-graphics-drivers StacktraceTop: ?? () ?? () xf86VTEnter () ?? () ?? () Title: Xorg crashed with signal 7 in xf86VTEnter() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo dmi.bios.date: 04/09/2018 dmi.bios.vendor: LENOVO dmi.bios.version: 3JCN30WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: Torronto 5C1 dmi.board.vendor: LENOVO dmi.board.version: NO DPK dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad 510-15IKB dmi.modalias: dmi:bvnLENOVO:bvr3JCN30WW:bd04/09/2018:svnLENOVO:pn80SV:pvrLenovoideapad510-15IKB:rvnLENOVO:rnTorronto5C1:rvrNODPK:cvnLENOVO:ct10:cvrLenovoideapad510-15IKB: dmi.product.family: IDEAPAD dmi.product.name: 80SV dmi.product.version: Lenovo ideapad 510-15IKB dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 ** Affects: nvidia-graphics-drivers (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-crash bionic need-amd64-retrace ubuntu ** Information type changed from Private to Public -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers in Ubuntu. https://bugs.launchpad.net/bugs/1784795 Title: Xorg crashed ( logged out when suspend or turn off the screen) with signal 7 in xf86VTEnter() Status in nvidia-graphics-drivers package in Ubuntu: New Bug description: When suspend (close the lid) and reopen it (resume) the system crashed and killed the session and prompt to login ( not to unlock) and when logging in all applications are killed (a new session started). ProblemType: Crash DistroRelease: Ubuntu 18.04 Package: xserver-xorg-core 2:1.19.6-1ubuntu4 ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18 Uname: Linux 4.15.0-29-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..03.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:03:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 390.48 Thu Mar 22 00:42:57 PDT 2018 GCC version: gcc version 7.3.0 (Ubuntu 7.3.0-16ubuntu3) ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CrashCounter: 1 Date: Wed Aug 1 10:15:33 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: nvidia, 390.48, 4.15.0-23-generic, x86_64: installed
[Desktop-packages] [Bug 1781826] GsettingsChanges.txt
apport information ** Attachment added: "GsettingsChanges.txt" https://bugs.launchpad.net/bugs/1781826/+attachment/5166328/+files/GsettingsChanges.txt -- 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/1781826 Title: System logout when turn off the screen or suspend Ubuntu 18.04 Status in gnome-shell package in Ubuntu: Incomplete Bug description: When turn off the screen or suspend, and resume the system is logged out, this mostly happens with nvidia driver (390 or 396). I noticed that when close the lid and reopen the system is still working and all of a sudden it appears a login screen and when login all programs as killed as it was logged out. And most of times after login it locks and prompts an unlock screen. I tried to switch to nouveau driver and the problem seems not to happen, but that leaves me with a poor performance in terms of graphics. I tried to reset the setting in dconf using dconf-editor to reset the system recursively, at the beginning seems to be solved but it gets back. I need to mention that I faced the same problem when using budgie flavor, I thought that it might be a budgie problem but it appears to be a gnome problem since budgie is based on gnome and on both the problem happens when using Nvidia drivers. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 18.04 NonfreeKernelModules: nvidia_modeset nvidia Package: gnome-shell 3.28.2-0ubuntu0.18.04.1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18 Tags: bionic Uname: Linux 4.15.0-29-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 18.04 NonfreeKernelModules: nvidia_modeset nvidia Package: gnome-shell 3.28.2-0ubuntu0.18.04.1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18 Tags: bionic Uname: Linux 4.15.0-29-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1781826/+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 1781826] Re: System logout when turn off the screen or suspend Ubuntu 18.04
apport information ** Tags added: apport-collected bionic ** Description changed: When turn off the screen or suspend, and resume the system is logged out, this mostly happens with nvidia driver (390 or 396). I noticed that when close the lid and reopen the system is still working and all of a sudden it appears a login screen and when login all programs as killed as it was logged out. And most of times after login it locks and prompts an unlock screen. I tried to switch to nouveau driver and the problem seems not to happen, but that leaves me with a poor performance in terms of graphics. I tried to reset the setting in dconf using dconf-editor to reset the system recursively, at the beginning seems to be solved but it gets back. I need to mention that I faced the same problem when using budgie flavor, I thought that it might be a budgie problem but it appears to be a gnome problem since budgie is based on gnome and on both the problem happens when using Nvidia drivers. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 18.04 NonfreeKernelModules: nvidia_modeset nvidia Package: gnome-shell 3.28.2-0ubuntu0.18.04.1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18 Tags: bionic Uname: Linux 4.15.0-29-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True + --- + ProblemType: Bug + ApportVersion: 2.20.9-0ubuntu7.2 + Architecture: amd64 + CurrentDesktop: ubuntu:GNOME + DisplayManager: gdm3 + DistroRelease: Ubuntu 18.04 + NonfreeKernelModules: nvidia_modeset nvidia + Package: gnome-shell 3.28.2-0ubuntu0.18.04.1 + PackageArchitecture: amd64 + ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18 + Tags: bionic + Uname: Linux 4.15.0-29-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo + _MarkForUpload: True ** Attachment added: "Dependencies.txt" https://bugs.launchpad.net/bugs/1781826/+attachment/5166327/+files/Dependencies.txt -- 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/1781826 Title: System logout when turn off the screen or suspend Ubuntu 18.04 Status in gnome-shell package in Ubuntu: Incomplete Bug description: When turn off the screen or suspend, and resume the system is logged out, this mostly happens with nvidia driver (390 or 396). I noticed that when close the lid and reopen the system is still working and all of a sudden it appears a login screen and when login all programs as killed as it was logged out. And most of times after login it locks and prompts an unlock screen. I tried to switch to nouveau driver and the problem seems not to happen, but that leaves me with a poor performance in terms of graphics. I tried to reset the setting in dconf using dconf-editor to reset the system recursively, at the beginning seems to be solved but it gets back. I need to mention that I faced the same problem when using budgie flavor, I thought that it might be a budgie problem but it appears to be a gnome problem since budgie is based on gnome and on both the problem happens when using Nvidia drivers. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 18.04 NonfreeKernelModules: nvidia_modeset nvidia Package: gnome-shell 3.28.2-0ubuntu0.18.04.1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18 Tags: bionic Uname: Linux 4.15.0-29-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 18.04 NonfreeKernelModules: nvidia_modeset nvidia Package: gnome-shell 3.28.2-0ubuntu0.18.04.1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18 Tags: bionic Uname: Linux 4.15.0-29-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1781826/+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 1781826] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1781826/+attachment/5166330/+files/ProcEnviron.txt -- 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/1781826 Title: System logout when turn off the screen or suspend Ubuntu 18.04 Status in gnome-shell package in Ubuntu: Incomplete Bug description: When turn off the screen or suspend, and resume the system is logged out, this mostly happens with nvidia driver (390 or 396). I noticed that when close the lid and reopen the system is still working and all of a sudden it appears a login screen and when login all programs as killed as it was logged out. And most of times after login it locks and prompts an unlock screen. I tried to switch to nouveau driver and the problem seems not to happen, but that leaves me with a poor performance in terms of graphics. I tried to reset the setting in dconf using dconf-editor to reset the system recursively, at the beginning seems to be solved but it gets back. I need to mention that I faced the same problem when using budgie flavor, I thought that it might be a budgie problem but it appears to be a gnome problem since budgie is based on gnome and on both the problem happens when using Nvidia drivers. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 18.04 NonfreeKernelModules: nvidia_modeset nvidia Package: gnome-shell 3.28.2-0ubuntu0.18.04.1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18 Tags: bionic Uname: Linux 4.15.0-29-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 18.04 NonfreeKernelModules: nvidia_modeset nvidia Package: gnome-shell 3.28.2-0ubuntu0.18.04.1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18 Tags: bionic Uname: Linux 4.15.0-29-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1781826/+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 1781826] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1781826/+attachment/5166329/+files/ProcCpuinfoMinimal.txt -- 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/1781826 Title: System logout when turn off the screen or suspend Ubuntu 18.04 Status in gnome-shell package in Ubuntu: Incomplete Bug description: When turn off the screen or suspend, and resume the system is logged out, this mostly happens with nvidia driver (390 or 396). I noticed that when close the lid and reopen the system is still working and all of a sudden it appears a login screen and when login all programs as killed as it was logged out. And most of times after login it locks and prompts an unlock screen. I tried to switch to nouveau driver and the problem seems not to happen, but that leaves me with a poor performance in terms of graphics. I tried to reset the setting in dconf using dconf-editor to reset the system recursively, at the beginning seems to be solved but it gets back. I need to mention that I faced the same problem when using budgie flavor, I thought that it might be a budgie problem but it appears to be a gnome problem since budgie is based on gnome and on both the problem happens when using Nvidia drivers. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 18.04 NonfreeKernelModules: nvidia_modeset nvidia Package: gnome-shell 3.28.2-0ubuntu0.18.04.1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18 Tags: bionic Uname: Linux 4.15.0-29-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 18.04 NonfreeKernelModules: nvidia_modeset nvidia Package: gnome-shell 3.28.2-0ubuntu0.18.04.1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18 Tags: bionic Uname: Linux 4.15.0-29-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1781826/+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 1781826] Re: System logout when turn off the screen or suspend Ubuntu 18.04
I added bug report to nvidia-graphic-drivers the bug report number is 1782882 -- 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/1781826 Title: System logout when turn off the screen or suspend Ubuntu 18.04 Status in gnome-shell package in Ubuntu: Incomplete Bug description: When turn off the screen or suspend, and resume the system is logged out, this mostly happens with nvidia driver (390 or 396). I noticed that when close the lid and reopen the system is still working and all of a sudden it appears a login screen and when login all programs as killed as it was logged out. And most of times after login it locks and prompts an unlock screen. I tried to switch to nouveau driver and the problem seems not to happen, but that leaves me with a poor performance in terms of graphics. I tried to reset the setting in dconf using dconf-editor to reset the system recursively, at the beginning seems to be solved but it gets back. I need to mention that I faced the same problem when using budgie flavor, I thought that it might be a budgie problem but it appears to be a gnome problem since budgie is based on gnome and on both the problem happens when using Nvidia drivers. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 18.04 NonfreeKernelModules: nvidia_modeset nvidia Package: gnome-shell 3.28.2-0ubuntu0.18.04.1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18 Tags: bionic Uname: Linux 4.15.0-29-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1781826/+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 1782882] Re: Xorg crashed (logged out when suspend or turn off the screen) with signal 7 in do_lookup_x()
** Information type changed from Public to Public Security -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers in Ubuntu. https://bugs.launchpad.net/bugs/1782882 Title: Xorg crashed (logged out when suspend or turn off the screen) with signal 7 in do_lookup_x() Status in nvidia-graphics-drivers package in Ubuntu: New Bug description: Xorg crached when using nvidia 390 driver when suspend or turn off the screen, it logs out where the greeting screen says `login` instead of `Unlock` and when enter all applications are closed ( the session was killed). This error happens on Ubuntu 18.04 and Budgie 18.04 ProblemType: Crash DistroRelease: Ubuntu 18.04 Package: xserver-xorg-core 2:1.19.6-1ubuntu4 ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18 Uname: Linux 4.15.0-29-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..03.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:03:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 390.48 Thu Mar 22 00:42:57 PDT 2018 GCC version: gcc version 7.3.0 (Ubuntu 7.3.0-16ubuntu3) ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CrashCounter: 1 Date: Sat Jul 21 12:07:07 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: nvidia, 390.48, 4.15.0-23-generic, x86_64: installed nvidia, 390.48, 4.15.0-29-generic, x86_64: installed ExecutablePath: /usr/lib/xorg/Xorg ExecutableTimestamp: 1523633505 GraphicsCard: Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Lenovo HD Graphics 620 [17aa:39f1] Subsystem: Lenovo GM108M [GeForce 940MX] [17aa:39f1] MachineType: LENOVO 80SV ProcCmdline: /usr/lib/xorg/Xorg vt2 -displayfd 3 -auth /run/user/1000/gdm/Xauthority -background none -noreset -keeptty -verbose 3 ProcCwd: /home/mhizzani ProcEnviron: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-29-generic root=UUID=d175c9ce-90fb-4afa-b2f7-51f8c3d9a9b6 ro quiet splash vt.handoff=1 Signal: 7 SourcePackage: nvidia-graphics-drivers StacktraceTop: do_lookup_x (undef_name=undef_name@entry=0x7ff1adbbcc63 "xf86IDrvMsg", new_hash=new_hash@entry=4135273453, old_hash=old_hash@entry=0x7ffe99573340, ref=0x7ff1adbbc6b8, result=result@entry=0x7ffe99573350, scope=, i=, version=0x0, flags=5, skip=0x0, type_class=1, undef_map=0x55b58ff39d10) at dl-lookup.c:403 _dl_lookup_symbol_x (undef_name=0x7ff1adbbcc63 "xf86IDrvMsg", undef_map=0x55b58ff39d10, ref=ref@entry=0x7ffe995733e8, symbol_scope=0x55b58ff3a068, version=0x0, type_class=type_class@entry=1, flags=5, skip_map=) at dl-lookup.c:813 _dl_fixup (l=, reloc_arg=) at ../elf/dl-runtime.c:112 _dl_runtime_resolve_xsavec () at ../sysdeps/x86_64/dl-trampoline.h:125 ?? () from /usr/lib/xorg/modules/input/libinput_drv.so Title: Xorg crashed with signal 7 in do_lookup_x() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo dmi.bios.date: 04/09/2018 dmi.bios.vendor: LENOVO dmi.bios.version: 3JCN30WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: Torronto 5C1 dmi.board.vendor: LENOVO dmi.board.version: NO DPK dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad 510-15IKB dmi.modalias: dmi:bvnLENOVO:bvr3JCN30WW:bd04/09/2018:svnLENOVO:pn80SV:pvrLenovoideapad510-15IKB:rvnLENOVO:rnTorronto5C1:rvrNODPK:cvnLENOVO:ct10:cvrLenovoideapad510-15IKB: dmi.product.family: IDEAPAD dmi.product.name: 80SV dmi.product.version: Lenovo ideapad 510-15IKB dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers/+bug/1782882/+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 1782882] [NEW] Xorg crashed (logged out when suspend or turn off the screen) with signal 7 in do_lookup_x()
Public bug reported: Xorg crached when using nvidia 390 driver when suspend or turn off the screen, it logs out where the greeting screen says `login` instead of `Unlock` and when enter all applications are closed ( the session was killed). This error happens on Ubuntu 18.04 and Budgie 18.04 ProblemType: Crash DistroRelease: Ubuntu 18.04 Package: xserver-xorg-core 2:1.19.6-1ubuntu4 ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18 Uname: Linux 4.15.0-29-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..03.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:03:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 390.48 Thu Mar 22 00:42:57 PDT 2018 GCC version: gcc version 7.3.0 (Ubuntu 7.3.0-16ubuntu3) ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CrashCounter: 1 Date: Sat Jul 21 12:07:07 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: nvidia, 390.48, 4.15.0-23-generic, x86_64: installed nvidia, 390.48, 4.15.0-29-generic, x86_64: installed ExecutablePath: /usr/lib/xorg/Xorg ExecutableTimestamp: 1523633505 GraphicsCard: Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Lenovo HD Graphics 620 [17aa:39f1] Subsystem: Lenovo GM108M [GeForce 940MX] [17aa:39f1] MachineType: LENOVO 80SV ProcCmdline: /usr/lib/xorg/Xorg vt2 -displayfd 3 -auth /run/user/1000/gdm/Xauthority -background none -noreset -keeptty -verbose 3 ProcCwd: /home/mhizzani ProcEnviron: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-29-generic root=UUID=d175c9ce-90fb-4afa-b2f7-51f8c3d9a9b6 ro quiet splash vt.handoff=1 Signal: 7 SourcePackage: nvidia-graphics-drivers StacktraceTop: do_lookup_x (undef_name=undef_name@entry=0x7ff1adbbcc63 "xf86IDrvMsg", new_hash=new_hash@entry=4135273453, old_hash=old_hash@entry=0x7ffe99573340, ref=0x7ff1adbbc6b8, result=result@entry=0x7ffe99573350, scope=, i=, version=0x0, flags=5, skip=0x0, type_class=1, undef_map=0x55b58ff39d10) at dl-lookup.c:403 _dl_lookup_symbol_x (undef_name=0x7ff1adbbcc63 "xf86IDrvMsg", undef_map=0x55b58ff39d10, ref=ref@entry=0x7ffe995733e8, symbol_scope=0x55b58ff3a068, version=0x0, type_class=type_class@entry=1, flags=5, skip_map=) at dl-lookup.c:813 _dl_fixup (l=, reloc_arg=) at ../elf/dl-runtime.c:112 _dl_runtime_resolve_xsavec () at ../sysdeps/x86_64/dl-trampoline.h:125 ?? () from /usr/lib/xorg/modules/input/libinput_drv.so Title: Xorg crashed with signal 7 in do_lookup_x() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo dmi.bios.date: 04/09/2018 dmi.bios.vendor: LENOVO dmi.bios.version: 3JCN30WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: Torronto 5C1 dmi.board.vendor: LENOVO dmi.board.version: NO DPK dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad 510-15IKB dmi.modalias: dmi:bvnLENOVO:bvr3JCN30WW:bd04/09/2018:svnLENOVO:pn80SV:pvrLenovoideapad510-15IKB:rvnLENOVO:rnTorronto5C1:rvrNODPK:cvnLENOVO:ct10:cvrLenovoideapad510-15IKB: dmi.product.family: IDEAPAD dmi.product.name: 80SV dmi.product.version: Lenovo ideapad 510-15IKB dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 ** Affects: nvidia-graphics-drivers (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-crash bionic need-amd64-retrace ubuntu ** Information type changed from Private to Public -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers in Ubuntu. https://bugs.launchpad.net/bugs/1782882 Title: Xorg crashed (logged out when suspend or turn off the screen) with signal 7 in do_lookup_x() Status in nvidia-graphics-drivers package in Ubuntu: New Bug description: Xorg crached when using nvidia 390 driver when suspend or turn off the screen, it logs out where the greeting screen says `login` instead of `Unlock` and when enter all applications are closed ( the session was killed). This error happens on Ubuntu 18.04 and Budgie 18.04 ProblemType: Crash DistroRelease: Ubuntu 18.04 Package: xserver-xorg-core
[Desktop-packages] [Bug 1781826] Re: System logout when turn off the screen or suspend Ubuntu 18.04
** Tags removed: apport-collected bionic ** Tags added: xorg -- 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/1781826 Title: System logout when turn off the screen or suspend Ubuntu 18.04 Status in gnome-shell package in Ubuntu: Incomplete Bug description: When turn off the screen or suspend, and resume the system is logged out, this mostly happens with nvidia driver (390 or 396). I noticed that when close the lid and reopen the system is still working and all of a sudden it appears a login screen and when login all programs as killed as it was logged out. And most of times after login it locks and prompts an unlock screen. I tried to switch to nouveau driver and the problem seems not to happen, but that leaves me with a poor performance in terms of graphics. I tried to reset the setting in dconf using dconf-editor to reset the system recursively, at the beginning seems to be solved but it gets back. I need to mention that I faced the same problem when using budgie flavor, I thought that it might be a budgie problem but it appears to be a gnome problem since budgie is based on gnome and on both the problem happens when using Nvidia drivers. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 18.04 NonfreeKernelModules: nvidia_modeset nvidia Package: gnome-shell 3.28.2-0ubuntu0.18.04.1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18 Tags: bionic Uname: Linux 4.15.0-29-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1781826/+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 1781826] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1781826/+attachment/5165818/+files/ProcCpuinfoMinimal.txt -- 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/1781826 Title: System logout when turn off the screen or suspend Ubuntu 18.04 Status in gnome-shell package in Ubuntu: Incomplete Bug description: When turn off the screen or suspend, and resume the system is logged out, this mostly happens with nvidia driver (390 or 396). I noticed that when close the lid and reopen the system is still working and all of a sudden it appears a login screen and when login all programs as killed as it was logged out. And most of times after login it locks and prompts an unlock screen. I tried to switch to nouveau driver and the problem seems not to happen, but that leaves me with a poor performance in terms of graphics. I tried to reset the setting in dconf using dconf-editor to reset the system recursively, at the beginning seems to be solved but it gets back. I need to mention that I faced the same problem when using budgie flavor, I thought that it might be a budgie problem but it appears to be a gnome problem since budgie is based on gnome and on both the problem happens when using Nvidia drivers. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 18.04 NonfreeKernelModules: nvidia_modeset nvidia Package: gnome-shell 3.28.2-0ubuntu0.18.04.1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18 Tags: bionic Uname: Linux 4.15.0-29-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1781826/+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 1781826] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1781826/+attachment/5165819/+files/ProcEnviron.txt -- 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/1781826 Title: System logout when turn off the screen or suspend Ubuntu 18.04 Status in gnome-shell package in Ubuntu: Incomplete Bug description: When turn off the screen or suspend, and resume the system is logged out, this mostly happens with nvidia driver (390 or 396). I noticed that when close the lid and reopen the system is still working and all of a sudden it appears a login screen and when login all programs as killed as it was logged out. And most of times after login it locks and prompts an unlock screen. I tried to switch to nouveau driver and the problem seems not to happen, but that leaves me with a poor performance in terms of graphics. I tried to reset the setting in dconf using dconf-editor to reset the system recursively, at the beginning seems to be solved but it gets back. I need to mention that I faced the same problem when using budgie flavor, I thought that it might be a budgie problem but it appears to be a gnome problem since budgie is based on gnome and on both the problem happens when using Nvidia drivers. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 18.04 NonfreeKernelModules: nvidia_modeset nvidia Package: gnome-shell 3.28.2-0ubuntu0.18.04.1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18 Tags: bionic Uname: Linux 4.15.0-29-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1781826/+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 1781826] GsettingsChanges.txt
apport information ** Attachment added: "GsettingsChanges.txt" https://bugs.launchpad.net/bugs/1781826/+attachment/5165817/+files/GsettingsChanges.txt -- 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/1781826 Title: System logout when turn off the screen or suspend Ubuntu 18.04 Status in gnome-shell package in Ubuntu: Incomplete Bug description: When turn off the screen or suspend, and resume the system is logged out, this mostly happens with nvidia driver (390 or 396). I noticed that when close the lid and reopen the system is still working and all of a sudden it appears a login screen and when login all programs as killed as it was logged out. And most of times after login it locks and prompts an unlock screen. I tried to switch to nouveau driver and the problem seems not to happen, but that leaves me with a poor performance in terms of graphics. I tried to reset the setting in dconf using dconf-editor to reset the system recursively, at the beginning seems to be solved but it gets back. I need to mention that I faced the same problem when using budgie flavor, I thought that it might be a budgie problem but it appears to be a gnome problem since budgie is based on gnome and on both the problem happens when using Nvidia drivers. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 18.04 NonfreeKernelModules: nvidia_modeset nvidia Package: gnome-shell 3.28.2-0ubuntu0.18.04.1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18 Tags: bionic Uname: Linux 4.15.0-29-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1781826/+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 1781826] Re: System logout when turn off the screen or suspend Ubuntu 18.04
apport information ** Tags added: apport-collected bionic ** Description changed: When turn off the screen or suspend, and resume the system is logged out, this mostly happens with nvidia driver (390 or 396). I noticed that when close the lid and reopen the system is still working and all of a sudden it appears a login screen and when login all programs as killed as it was logged out. And most of times after login it locks and prompts an unlock screen. I tried to switch to nouveau driver and the problem seems not to happen, but that leaves me with a poor performance in terms of graphics. I tried to reset the setting in dconf using dconf-editor to reset the system recursively, at the beginning seems to be solved but it gets back. - I need to mention that I faced the same problem when using budgie - flavor, I thought that it might be a budgie problem but it appears to be - a gnome problem since budgie is based on gnome and on both the problem - happens when using Nvidia drivers. + I need to mention that I faced the same problem when using budgie flavor, I thought that it might be a budgie problem but it appears to be a gnome problem since budgie is based on gnome and on both the problem happens when using Nvidia drivers. + --- + ProblemType: Bug + ApportVersion: 2.20.9-0ubuntu7.2 + Architecture: amd64 + CurrentDesktop: ubuntu:GNOME + DisplayManager: gdm3 + DistroRelease: Ubuntu 18.04 + NonfreeKernelModules: nvidia_modeset nvidia + Package: gnome-shell 3.28.2-0ubuntu0.18.04.1 + PackageArchitecture: amd64 + ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18 + Tags: bionic + Uname: Linux 4.15.0-29-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo + _MarkForUpload: True ** Attachment added: "Dependencies.txt" https://bugs.launchpad.net/bugs/1781826/+attachment/5165816/+files/Dependencies.txt -- 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/1781826 Title: System logout when turn off the screen or suspend Ubuntu 18.04 Status in gnome-shell package in Ubuntu: Incomplete Bug description: When turn off the screen or suspend, and resume the system is logged out, this mostly happens with nvidia driver (390 or 396). I noticed that when close the lid and reopen the system is still working and all of a sudden it appears a login screen and when login all programs as killed as it was logged out. And most of times after login it locks and prompts an unlock screen. I tried to switch to nouveau driver and the problem seems not to happen, but that leaves me with a poor performance in terms of graphics. I tried to reset the setting in dconf using dconf-editor to reset the system recursively, at the beginning seems to be solved but it gets back. I need to mention that I faced the same problem when using budgie flavor, I thought that it might be a budgie problem but it appears to be a gnome problem since budgie is based on gnome and on both the problem happens when using Nvidia drivers. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 18.04 NonfreeKernelModules: nvidia_modeset nvidia Package: gnome-shell 3.28.2-0ubuntu0.18.04.1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18 Tags: bionic Uname: Linux 4.15.0-29-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1781826/+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 1781826] Re: System logout when turn off the screen or suspend Ubuntu 18.04
** Tags added: gnome-shell-extension -- 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/1781826 Title: System logout when turn off the screen or suspend Ubuntu 18.04 Status in gnome-shell package in Ubuntu: Incomplete Bug description: When turn off the screen or suspend, and resume the system is logged out, this mostly happens with nvidia driver (390 or 396). I noticed that when close the lid and reopen the system is still working and all of a sudden it appears a login screen and when login all programs as killed as it was logged out. And most of times after login it locks and prompts an unlock screen. I tried to switch to nouveau driver and the problem seems not to happen, but that leaves me with a poor performance in terms of graphics. I tried to reset the setting in dconf using dconf-editor to reset the system recursively, at the beginning seems to be solved but it gets back. I need to mention that I faced the same problem when using budgie flavor, I thought that it might be a budgie problem but it appears to be a gnome problem since budgie is based on gnome and on both the problem happens when using Nvidia drivers. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1781826/+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 1781826] Re: System logout when turn off the screen or suspend Ubuntu 18.04
-- Logs begin at Thu 2018-07-12 05:44:49 EEST, end at Sun 2018-07-15 23:57:53 EEST. -- Jul 12 05:45:35 mhizzani-ubuntu gnome-shell[1539]: JS WARNING: [resource:///org/gnome/shell/ui/main.js 340]: reference to undefined property "MetaStage" Jul 12 05:45:35 mhizzani-ubuntu gnome-shell[1539]: JS WARNING: [resource:///org/gnome/shell/ui/layout.js 220]: reference to undefined property "MetaWindowGroup" Jul 12 05:45:35 mhizzani-ubuntu gnome-shell[1539]: JS WARNING: [resource:///org/gnome/shell/ui/osdMonitorLabeler.js 59]: reference to undefined property "MetaDBusDisplayConfigSkeleton" Jul 12 05:45:39 mhizzani-ubuntu gnome-shell[1539]: JS WARNING: [resource:///org/gnome/shell/ui/slider.js 38]: reference to undefined property "CallyActor" Jul 12 05:45:41 mhizzani-ubuntu gnome-shell[1539]: Error setting property 'Powered' on interface org.bluez.Adapter1: GDBus.Error:org.bluez.Error.Blocked: Blocked through rfkill (g-io-error-quark, 36) Jul 12 05:45:41 mhizzani-ubuntu gnome-shell[1539]: Error looking up permission: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.freedesktop.impl.portal.PermissionStore was not provided by any .service files Jul 12 05:45:43 mhizzani-ubuntu gnome-shell[1539]: JS WARNING: [resource:///org/gnome/shell/ui/layout.js 29]: reference to undefined property "MetaWindowX11" -- 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/1781826 Title: System logout when turn off the screen or suspend Ubuntu 18.04 Status in gnome-shell package in Ubuntu: New Bug description: When turn off the screen or suspend, and resume the system is logged out, this mostly happens with nvidia driver (390 or 396). I noticed that when close the lid and reopen the system is still working and all of a sudden it appears a login screen and when login all programs as killed as it was logged out. And most of times after login it locks and prompts an unlock screen. I tried to switch to nouveau driver and the problem seems not to happen, but that leaves me with a poor performance in terms of graphics. I tried to reset the setting in dconf using dconf-editor to reset the system recursively, at the beginning seems to be solved but it gets back. I need to mention that I faced the same problem when using budgie flavor, I thought that it might be a budgie problem but it appears to be a gnome problem since budgie is based on gnome and on both the problem happens when using Nvidia drivers. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1781826/+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 1781826] Re: System logout when turn off the screen or suspend Ubuntu 18.04
** Description changed: When turn off the screen or suspend, and resume the system is logged out, this mostly happens with nvidia driver (390 or 396). I noticed that when close the lid and reopen the system is still working and all of a sudden it appears a login screen and when login all programs as killed - as it was logged out. + as it was logged out. And most of times after login it locks and prompts + an unlock screen. I tried to switch to nouveau driver and the problem seems not to happen, but that leaves me with a poor performance in terms of graphics. I tried to reset the setting in dconf using dconf-editor to reset the system recursively, at the beginning seems to be solved but it gets back. I need to mention that I faced the same problem when using budgie flavor, I thought that it might be a budgie problem but it appears to be a gnome problem since budgie is based on gnome and on both the problem happens when using Nvidia drivers. -- 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/1781826 Title: System logout when turn off the screen or suspend Ubuntu 18.04 Status in gnome-shell package in Ubuntu: New Bug description: When turn off the screen or suspend, and resume the system is logged out, this mostly happens with nvidia driver (390 or 396). I noticed that when close the lid and reopen the system is still working and all of a sudden it appears a login screen and when login all programs as killed as it was logged out. And most of times after login it locks and prompts an unlock screen. I tried to switch to nouveau driver and the problem seems not to happen, but that leaves me with a poor performance in terms of graphics. I tried to reset the setting in dconf using dconf-editor to reset the system recursively, at the beginning seems to be solved but it gets back. I need to mention that I faced the same problem when using budgie flavor, I thought that it might be a budgie problem but it appears to be a gnome problem since budgie is based on gnome and on both the problem happens when using Nvidia drivers. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1781826/+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 1781826] [NEW] System logout when turn off the screen or suspend Ubuntu 18.04
Public bug reported: When turn off the screen or suspend, and resume the system is logged out, this mostly happens with nvidia driver (390 or 396). I noticed that when close the lid and reopen the system is still working and all of a sudden it appears a login screen and when login all programs as killed as it was logged out. And most of times after login it locks and prompts an unlock screen. I tried to switch to nouveau driver and the problem seems not to happen, but that leaves me with a poor performance in terms of graphics. I tried to reset the setting in dconf using dconf-editor to reset the system recursively, at the beginning seems to be solved but it gets back. I need to mention that I faced the same problem when using budgie flavor, I thought that it might be a budgie problem but it appears to be a gnome problem since budgie is based on gnome and on both the problem happens when using Nvidia drivers. ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: suspend-resume ** Tags added: suspend-resume -- 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/1781826 Title: System logout when turn off the screen or suspend Ubuntu 18.04 Status in gnome-shell package in Ubuntu: New Bug description: When turn off the screen or suspend, and resume the system is logged out, this mostly happens with nvidia driver (390 or 396). I noticed that when close the lid and reopen the system is still working and all of a sudden it appears a login screen and when login all programs as killed as it was logged out. And most of times after login it locks and prompts an unlock screen. I tried to switch to nouveau driver and the problem seems not to happen, but that leaves me with a poor performance in terms of graphics. I tried to reset the setting in dconf using dconf-editor to reset the system recursively, at the beginning seems to be solved but it gets back. I need to mention that I faced the same problem when using budgie flavor, I thought that it might be a budgie problem but it appears to be a gnome problem since budgie is based on gnome and on both the problem happens when using Nvidia drivers. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1781826/+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 1666432] Re: Internet drops every few minutes on wired and wireless connection
i also having same problem with wired connection!! ubuntu 16.04.4 -- 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/1666432 Title: Internet drops every few minutes on wired and wireless connection Status in network-manager package in Ubuntu: Confirmed Bug description: Internet drops every 1-30 minutes when connected via wired or wireless (i.e., this is a problem on both wired and wireless) even though connection icon indicates the computer is still connected. Disconnecting and reconnecting via the connection icon resets internet temporarily until the next time. Dropped internet is discovered with "The site can't be reached" screens in Chromium, or error messages when downloading/updating in Terminal, or missing connection in Ubuntu Software app, or stalled syncing in Insync application (occurred even without Insync). Internet drops more frequently on wireless than on wired. It seems to disconnect more frequently with heavier internet use (e.g., downloading multiple files, opening several webpages in quick succession). This is a fresh install (yesterday) of Ubuntu 16.04 on a Dell Inspiron 15 5567 (dual boot). It occurs when running Live CD as well though. Ethernet and wifi both work without randomly disconnecting in Windows 10 on the same machine, and ethernet and wifi work on other machines running Ubuntu and Windows with the same router, so it is not a hardware or router issue. Output from sudo lshw -class network *-network description: Wireless interface product: Wireless 3165 vendor: Intel Corporation physical id: 0 bus info: pci@:02:00.0 logical name: wlp2s0 version: 79 serial: 58:fb:84:55:21:52 width: 64 bits clock: 33MHz capabilities: pm msi pciexpress bus_master cap_list ethernet physical wireless configuration: broadcast=yes driver=iwlwifi driverversion=4.4.0-62-generic firmware=17.352738.0 ip=192.168.1.15 latency=0 link=yes multicast=yes wireless=IEEE 802.11abgn resources: irq:283 memory:df10-df101fff *-network description: Ethernet interface product: RTL8101/2/6E PCI Express Fast/Gigabit Ethernet controller vendor: Realtek Semiconductor Co., Ltd. physical id: 0 bus info: pci@:03:00.0 logical name: enp3s0 version: 07 serial: 18:db:f2:3c:d5:37 size: 10Mbit/s capacity: 100Mbit/s width: 64 bits clock: 33MHz capabilities: pm msi pciexpress msix vpd bus_master cap_list ethernet physical tp mii 10bt 10bt-fd 100bt 100bt-fd autonegotiation configuration: autonegotiation=on broadcast=yes driver=r8169 driverversion=2.3LK-NAPI duplex=half firmware=rtl8106e-1_0.0.1 06/29/12 latency=0 link=no multicast=yes port=MII speed=10Mbit/s resources: irq:279 ioport:d000(size=256) memory:df00-df000fff memory:d030-d0303fff ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: network-manager 1.2.2-0ubuntu0.16.04.3 ProcVersionSignature: Ubuntu 4.4.0-62.83-generic 4.4.40 Uname: Linux 4.4.0-62-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 CurrentDesktop: Unity Date: Tue Feb 21 16:36:55 2017 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2017-02-20 (1 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) IpRoute: default via 192.168.1.1 dev wlp2s0 proto static metric 600 169.254.0.0/16 dev wlp2s0 scope link metric 1000 192.168.1.0/24 dev wlp2s0 proto kernel scope link src 192.168.1.15 metric 600 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-dev: DEVICE TYPE STATEDBUS-PATH CONNECTION CON-UUID CON-PATH wlp2s0 wifi connected/org/freedesktop/NetworkManager/Devices/0 pr500k-9912ec-1 36301ded-0ac5-4a86-9621-87290ef159af /org/freedesktop/NetworkManager/ActiveConnection/5 enp3s0 ethernet unavailable /org/freedesktop/NetworkManager/Devices/1 -- ---- lo loopback unmanaged/org/freedesktop/NetworkManager/Devices/2 -- ---- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.2.2connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to:
[Desktop-packages] [Bug 1666432] Re: Internet drops every few minutes on wired and wireless connection
i also having same problem with wired connection!! ubuntu 16.04.4 -- 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/1666432 Title: Internet drops every few minutes on wired and wireless connection Status in network-manager package in Ubuntu: Confirmed Bug description: Internet drops every 1-30 minutes when connected via wired or wireless (i.e., this is a problem on both wired and wireless) even though connection icon indicates the computer is still connected. Disconnecting and reconnecting via the connection icon resets internet temporarily until the next time. Dropped internet is discovered with "The site can't be reached" screens in Chromium, or error messages when downloading/updating in Terminal, or missing connection in Ubuntu Software app, or stalled syncing in Insync application (occurred even without Insync). Internet drops more frequently on wireless than on wired. It seems to disconnect more frequently with heavier internet use (e.g., downloading multiple files, opening several webpages in quick succession). This is a fresh install (yesterday) of Ubuntu 16.04 on a Dell Inspiron 15 5567 (dual boot). It occurs when running Live CD as well though. Ethernet and wifi both work without randomly disconnecting in Windows 10 on the same machine, and ethernet and wifi work on other machines running Ubuntu and Windows with the same router, so it is not a hardware or router issue. Output from sudo lshw -class network *-network description: Wireless interface product: Wireless 3165 vendor: Intel Corporation physical id: 0 bus info: pci@:02:00.0 logical name: wlp2s0 version: 79 serial: 58:fb:84:55:21:52 width: 64 bits clock: 33MHz capabilities: pm msi pciexpress bus_master cap_list ethernet physical wireless configuration: broadcast=yes driver=iwlwifi driverversion=4.4.0-62-generic firmware=17.352738.0 ip=192.168.1.15 latency=0 link=yes multicast=yes wireless=IEEE 802.11abgn resources: irq:283 memory:df10-df101fff *-network description: Ethernet interface product: RTL8101/2/6E PCI Express Fast/Gigabit Ethernet controller vendor: Realtek Semiconductor Co., Ltd. physical id: 0 bus info: pci@:03:00.0 logical name: enp3s0 version: 07 serial: 18:db:f2:3c:d5:37 size: 10Mbit/s capacity: 100Mbit/s width: 64 bits clock: 33MHz capabilities: pm msi pciexpress msix vpd bus_master cap_list ethernet physical tp mii 10bt 10bt-fd 100bt 100bt-fd autonegotiation configuration: autonegotiation=on broadcast=yes driver=r8169 driverversion=2.3LK-NAPI duplex=half firmware=rtl8106e-1_0.0.1 06/29/12 latency=0 link=no multicast=yes port=MII speed=10Mbit/s resources: irq:279 ioport:d000(size=256) memory:df00-df000fff memory:d030-d0303fff ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: network-manager 1.2.2-0ubuntu0.16.04.3 ProcVersionSignature: Ubuntu 4.4.0-62.83-generic 4.4.40 Uname: Linux 4.4.0-62-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 CurrentDesktop: Unity Date: Tue Feb 21 16:36:55 2017 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2017-02-20 (1 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) IpRoute: default via 192.168.1.1 dev wlp2s0 proto static metric 600 169.254.0.0/16 dev wlp2s0 scope link metric 1000 192.168.1.0/24 dev wlp2s0 proto kernel scope link src 192.168.1.15 metric 600 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-dev: DEVICE TYPE STATEDBUS-PATH CONNECTION CON-UUID CON-PATH wlp2s0 wifi connected/org/freedesktop/NetworkManager/Devices/0 pr500k-9912ec-1 36301ded-0ac5-4a86-9621-87290ef159af /org/freedesktop/NetworkManager/ActiveConnection/5 enp3s0 ethernet unavailable /org/freedesktop/NetworkManager/Devices/1 -- ---- lo loopback unmanaged/org/freedesktop/NetworkManager/Devices/2 -- ---- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.2.2connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to:
[Desktop-packages] [Bug 1773259] Re: Network icon shows busy on Ubuntu MATE 18.04
** Changed in: network-manager-applet (Ubuntu) Status: New => Invalid -- 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/1773259 Title: Network icon shows busy on Ubuntu MATE 18.04 Status in network-manager-applet package in Ubuntu: Invalid Bug description: The network icon of the network-manager-applet sometimes shows "busy", as if it's trying to connect. I have a broadband connection on my desktop, just an ethernet cable plugged in- no wifi. I'm using a DSL/PPoE type of connection profile. Even though I'm able to browse the internet and stream videos perfectly, the icon shows that it's "busy" trying to connect. I'm not sure if this is a bug(of the applet) or not; I do get disconnected once in a while( which doesn't happen on "Windows") here on Ubuntu, which weirdly gets fixed after I go to my "connection profile" and hit "ok" without changing anything, but even then the icon shows busy! I'm using Ubuntu MATE 18.04, with 4.15.0-22-generic kernel. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager-applet/+bug/1773259/+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 1778549] Re: Thunderbird selectable as default web browser
** Changed in: ubuntu-mate Status: New => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to thunderbird in Ubuntu. https://bugs.launchpad.net/bugs/1778549 Title: Thunderbird selectable as default web browser Status in ubuntu-mate: Invalid Status in thunderbird package in Ubuntu: Invalid Bug description: The "Web Browser" section of "Preferred Applications" in UM 18.04 includes Thunderbird as an option. While it can technically display HTML, it is not supposed to be a general-purpose webbrowser. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-mate/+bug/1778549/+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 1778549] Re: Thunderbird selectable as default web browser
Not here- only Chrome and Firefox is shown. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to thunderbird in Ubuntu. https://bugs.launchpad.net/bugs/1778549 Title: Thunderbird selectable as default web browser Status in ubuntu-mate: New Status in thunderbird package in Ubuntu: New Bug description: The "Web Browser" section of "Preferred Applications" in UM 18.04 includes Thunderbird as an option. While it can technically display HTML, it is not supposed to be a general-purpose webbrowser. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-mate/+bug/1778549/+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 1773259] Re: Network icon shows busy on Ubuntu MATE 18.04
** Tags added: 18.04 applet network ** Tags added: amd64 ubuntu-mate -- 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/1773259 Title: Network icon shows busy on Ubuntu MATE 18.04 Status in network-manager-applet package in Ubuntu: New Bug description: The network icon of the network-manager-applet sometimes shows "busy", as if it's trying to connect. I have a broadband connection on my desktop, just an ethernet cable plugged in- no wifi. I'm using a DSL/PPoE type of connection profile. Even though I'm able to browse the internet and stream videos perfectly, the icon shows that it's "busy" trying to connect. I'm not sure if this is a bug(of the applet) or not; I do get disconnected once in a while( which doesn't happen on "Windows") here on Ubuntu, which weirdly gets fixed after I go to my "connection profile" and hit "ok" without changing anything, but even then the icon shows busy! I'm using Ubuntu MATE 18.04, with 4.15.0-22-generic kernel. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager-applet/+bug/1773259/+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 1773259] Re: Network icon shows busy
** Attachment added: "image_of_issue" https://bugs.launchpad.net/ubuntu/+source/network-manager-applet/+bug/1773259/+attachment/5144021/+files/issue.png ** Summary changed: - Network icon shows busy + Network icon shows busy on Ubuntu MATE ** Summary changed: - Network icon shows busy on Ubuntu MATE + Network icon shows busy on Ubuntu MATE 18.04 -- 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/1773259 Title: Network icon shows busy on Ubuntu MATE 18.04 Status in network-manager-applet package in Ubuntu: New Bug description: The network icon of the network-manager-applet sometimes shows "busy", as if it's trying to connect. I have a broadband connection on my desktop, just an ethernet cable plugged in- no wifi. I'm using a DSL/PPoE type of connection profile. Even though I'm able to browse the internet and stream videos perfectly, the icon shows that it's "busy" trying to connect. I'm not sure if this is a bug(of the applet) or not; I do get disconnected once in a while( which doesn't happen on "Windows") here on Ubuntu, which weirdly gets fixed after I go to my "connection profile" and hit "ok" without changing anything, but even then the icon shows busy! I'm using Ubuntu MATE 18.04, with 4.15.0-22-generic kernel. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager-applet/+bug/1773259/+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 1773259] [NEW] Network icon shows busy
Public bug reported: The network icon of the network-manager-applet sometimes shows "busy", as if it's trying to connect. I have a broadband connection on my desktop, just an ethernet cable plugged in- no wifi. I'm using a DSL/PPoE type of connection profile. Even though I'm able to browse the internet and stream videos perfectly, the icon shows that it's "busy" trying to connect. I'm not sure if this is a bug(of the applet) or not; I do get disconnected once in a while( which doesn't happen on "Windows") here on Ubuntu, which weirdly gets fixed after I go to my "connection profile" and hit "ok" without changing anything, but even then the icon shows busy! I'm using Ubuntu MATE 18.04, with 4.15.0-22-generic kernel. ** Affects: network-manager-applet (Ubuntu) Importance: Undecided Status: New ** Tags: bionic ** Tags added: bionic -- 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/1773259 Title: Network icon shows busy Status in network-manager-applet package in Ubuntu: New Bug description: The network icon of the network-manager-applet sometimes shows "busy", as if it's trying to connect. I have a broadband connection on my desktop, just an ethernet cable plugged in- no wifi. I'm using a DSL/PPoE type of connection profile. Even though I'm able to browse the internet and stream videos perfectly, the icon shows that it's "busy" trying to connect. I'm not sure if this is a bug(of the applet) or not; I do get disconnected once in a while( which doesn't happen on "Windows") here on Ubuntu, which weirdly gets fixed after I go to my "connection profile" and hit "ok" without changing anything, but even then the icon shows busy! I'm using Ubuntu MATE 18.04, with 4.15.0-22-generic kernel. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager-applet/+bug/1773259/+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 1735594] Re: [regression] compiz crashes after Mesa upgrade
Proposed update fixed the issue on an old Intel 1st gen Core i5-M450 with integrated Ironlake graphics libgl1-mesa-dri: Installed: 17.2.4-0ubuntu1~16.04.3 Candidate: 17.2.4-0ubuntu1~16.04.3 Version table: *** 17.2.4-0ubuntu1~16.04.3 400 400 http://ir.archive.ubuntu.com/ubuntu xenial-proposed/main amd64 Packages 100 /var/lib/dpkg/status 17.2.4-0ubuntu1~16.04.2 500 500 http://ir.archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages 11.2.0-1ubuntu2 500 500 http://ir.archive.ubuntu.com/ubuntu xenial/main amd64 Packages -- 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/1735594 Title: [regression] compiz crashes after Mesa upgrade Status in mesa package in Ubuntu: Fix Committed Status in mesa source package in Xenial: Fix Committed Status in mesa source package in Artful: Fix Committed Bug description: [Impact] When I use the Unity session I automatically get logged out under these conditions: When I hover with my mouse over any icon of the sidebar. When I press the alt key. When I press the super key. running dmesg after this unwanted logout happens I get following information: compiz[10616]: segfault at 0 ip 7fbca309feeb sp 7fff5f59a4d0 error 4 in i965_dri.so[7fbca2af6000+7e4000] This is caused by a mesa upgrade, which added a patch for bug #1727401. The crasher is reproduced on: - gen4 / gen5 Intel - if using modesetting X driver, like when xserver-xorg-video-intel is not installed, or the HWE stack is installed (xserver-xorg-core-hwe-16.04 defaults to modesetting) [Test case] Log in to Unity, open the dash or try to log out etc. Compiz shouldn't crash. [Regression potential] The backported patches need to be tested, here for regressions and on 1727401 that they fix the original bug (again). Best to test on a wide array of Intel HW: gen4 (965GM/GM45/G45) gen5 (Ironlake) gen6 (Sandy Bridge) gen7 (Bay Trail, Ivy Bridge, Haswell) gen8 (Braswell, Broadwell) gen9 (Apollo Lake, Skylake, Gemini Lake, Kaby Lake, Coffee Lake) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1735594/+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 1743073] [NEW] package libsane1 1.0.27-1~experimental2ubuntu2.1 failed to install/upgrade: trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', which is different from o
Public bug reported: package libsane1 1.0.27-1~experimental2ubuntu2.1 failed to install/upgrade: trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', which is different from other instances of package libsane1:i386 ProblemType: Package DistroRelease: Ubuntu 17.10 Package: libsane1 1.0.27-1~experimental2ubuntu2.1 ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13 Uname: Linux 4.13.0-25-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 Date: Fri Jan 12 20:19:24 2018 DuplicateSignature: package:libsane1:1.0.27-1~experimental2ubuntu2.1 Unpacking libsane1:i386 (1.0.27-1~experimental2ubuntu2.1) ... dpkg: error processing archive /tmp/apt-dpkg-install-IlNQjb/137-libsane1_1.0.27-1~experimental2ubuntu2.1_i386.deb (--unpack): trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', which is different from other instances of package libsane1:i386 ErrorMessage: trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', which is different from other instances of package libsane1:i386 InstallationDate: Installed on 2018-01-12 (0 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1) Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 3.6.3-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 2.7.14-2ubuntu1 RelatedPackageVersions: dpkg 1.18.24ubuntu1 apt 1.5.1 SourcePackage: sane-backends Title: package libsane1 1.0.27-1~experimental2ubuntu2.1 failed to install/upgrade: trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', which is different from other instances of package libsane1:i386 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: sane-backends (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package artful package-conflict -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to sane-backends in Ubuntu. https://bugs.launchpad.net/bugs/1743073 Title: package libsane1 1.0.27-1~experimental2ubuntu2.1 failed to install/upgrade: trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', which is different from other instances of package libsane1:i386 Status in sane-backends package in Ubuntu: New Bug description: package libsane1 1.0.27-1~experimental2ubuntu2.1 failed to install/upgrade: trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', which is different from other instances of package libsane1:i386 ProblemType: Package DistroRelease: Ubuntu 17.10 Package: libsane1 1.0.27-1~experimental2ubuntu2.1 ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13 Uname: Linux 4.13.0-25-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 Date: Fri Jan 12 20:19:24 2018 DuplicateSignature: package:libsane1:1.0.27-1~experimental2ubuntu2.1 Unpacking libsane1:i386 (1.0.27-1~experimental2ubuntu2.1) ... dpkg: error processing archive /tmp/apt-dpkg-install-IlNQjb/137-libsane1_1.0.27-1~experimental2ubuntu2.1_i386.deb (--unpack): trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', which is different from other instances of package libsane1:i386 ErrorMessage: trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', which is different from other instances of package libsane1:i386 InstallationDate: Installed on 2018-01-12 (0 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1) Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 3.6.3-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 2.7.14-2ubuntu1 RelatedPackageVersions: dpkg 1.18.24ubuntu1 apt 1.5.1 SourcePackage: sane-backends Title: package libsane1 1.0.27-1~experimental2ubuntu2.1 failed to install/upgrade: trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', which is different from other instances of package libsane1:i386 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sane-backends/+bug/1743073/+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 1743074] [NEW] package libsane1 1.0.27-1~experimental2ubuntu2.1 failed to install/upgrade: trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', which is different from o
*** This bug is a duplicate of bug 1743073 *** https://bugs.launchpad.net/bugs/1743073 Public bug reported: package libsane1 1.0.27-1~experimental2ubuntu2.1 failed to install/upgrade: trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', which is different from other instances of package libsane1:i386 ProblemType: Package DistroRelease: Ubuntu 17.10 Package: libsane1 1.0.27-1~experimental2ubuntu2.1 ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13 Uname: Linux 4.13.0-25-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 Date: Fri Jan 12 20:19:24 2018 DuplicateSignature: package:libsane1:1.0.27-1~experimental2ubuntu2.1 Unpacking libsane1:i386 (1.0.27-1~experimental2ubuntu2.1) ... dpkg: error processing archive /tmp/apt-dpkg-install-IlNQjb/137-libsane1_1.0.27-1~experimental2ubuntu2.1_i386.deb (--unpack): trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', which is different from other instances of package libsane1:i386 ErrorMessage: trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', which is different from other instances of package libsane1:i386 InstallationDate: Installed on 2018-01-12 (0 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1) Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 3.6.3-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 2.7.14-2ubuntu1 RelatedPackageVersions: dpkg 1.18.24ubuntu1 apt 1.5.1 SourcePackage: sane-backends Title: package libsane1 1.0.27-1~experimental2ubuntu2.1 failed to install/upgrade: trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', which is different from other instances of package libsane1:i386 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: sane-backends (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package artful package-conflict -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to sane-backends in Ubuntu. https://bugs.launchpad.net/bugs/1743074 Title: package libsane1 1.0.27-1~experimental2ubuntu2.1 failed to install/upgrade: trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', which is different from other instances of package libsane1:i386 Status in sane-backends package in Ubuntu: New Bug description: package libsane1 1.0.27-1~experimental2ubuntu2.1 failed to install/upgrade: trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', which is different from other instances of package libsane1:i386 ProblemType: Package DistroRelease: Ubuntu 17.10 Package: libsane1 1.0.27-1~experimental2ubuntu2.1 ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13 Uname: Linux 4.13.0-25-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 Date: Fri Jan 12 20:19:24 2018 DuplicateSignature: package:libsane1:1.0.27-1~experimental2ubuntu2.1 Unpacking libsane1:i386 (1.0.27-1~experimental2ubuntu2.1) ... dpkg: error processing archive /tmp/apt-dpkg-install-IlNQjb/137-libsane1_1.0.27-1~experimental2ubuntu2.1_i386.deb (--unpack): trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', which is different from other instances of package libsane1:i386 ErrorMessage: trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', which is different from other instances of package libsane1:i386 InstallationDate: Installed on 2018-01-12 (0 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1) Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 3.6.3-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 2.7.14-2ubuntu1 RelatedPackageVersions: dpkg 1.18.24ubuntu1 apt 1.5.1 SourcePackage: sane-backends Title: package libsane1 1.0.27-1~experimental2ubuntu2.1 failed to install/upgrade: trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', which is different from other instances of package libsane1:i386 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sane-backends/+bug/1743074/+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
