[Desktop-packages] [Bug 1855660] [NEW] Strong Lag while Copy-Pasting Files
Public bug reported: When I Copy-Paste a file Using Nautilus , The whole system will lag , such that , even the cursor moves after 3 secs . ProblemType: Bug DistroRelease: Ubuntu 19.10 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 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Dec 9 12:28:27 2019 GsettingsChanges: b'org.gnome.nautilus.preferences' b'default-folder-viewer' b"'list-view'" InstallationDate: Installed on 2019-12-06 (2 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN SHELL=/bin/bash SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: ** Affects: nautilus (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug eoan -- 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/1855660 Title: Strong Lag while Copy-Pasting Files Status in nautilus package in Ubuntu: New Bug description: When I Copy-Paste a file Using Nautilus , The whole system will lag , such that , even the cursor moves after 3 secs . ProblemType: Bug DistroRelease: Ubuntu 19.10 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 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Dec 9 12:28:27 2019 GsettingsChanges: b'org.gnome.nautilus.preferences' b'default-folder-viewer' b"'list-view'" InstallationDate: Installed on 2019-12-06 (2 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN SHELL=/bin/bash SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1855660/+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 1855402] Re: [TGL] mesa support
keep it as 20.04. TigerLake PV is planned in 2020'May, this will miss 20.04 release. if all features for 3D go into 20.04, that will be good. If not, just move them to 20.10. -- 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/1855402 Title: [TGL] mesa support Status in intel: New Status in mesa package in Ubuntu: New Bug description: Description: this feature tracks the updates of mesa 3d for TGL support. We will update the commitid list as necessary Target Release: 20.04 Target version: TBD To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1855402/+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 1855647] Re: When an ISO image is loaded, could you show a disc with a ISO tag at the bottom of the disc?
** Tags added: eoan ** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu) Importance: Undecided => Wishlist -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-ubuntu-dock in Ubuntu. https://bugs.launchpad.net/bugs/1855647 Title: When an ISO image is loaded, could you show a disc with a ISO tag at the bottom of the disc? Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: New Bug description: 1) Ubuntu 19.10 2) Dock 3) When an ISO image is loaded, a disc with ISO tag would be displayed on the dock. 4) A disc drive was displayed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1855647/+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 1855647] [NEW] When an ISO image is loaded, could you show a disc with a ISO tag at the bottom of the disc?
Public bug reported: 1) Ubuntu 19.10 2) Dock 3) When an ISO image is loaded, a disc with ISO tag would be displayed on the dock. 4) A disc drive was displayed. ** Affects: gnome-shell-extension-ubuntu-dock (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-ubuntu-dock in Ubuntu. https://bugs.launchpad.net/bugs/1855647 Title: When an ISO image is loaded, could you show a disc with a ISO tag at the bottom of the disc? Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: New Bug description: 1) Ubuntu 19.10 2) Dock 3) When an ISO image is loaded, a disc with ISO tag would be displayed on the dock. 4) A disc drive was displayed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1855647/+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 1798440] Re: passwords and keys crashes on entering zero password in 18.10
[Expired for seahorse (Ubuntu) because there has been no activity for 60 days.] ** Changed in: seahorse (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to seahorse in Ubuntu. https://bugs.launchpad.net/bugs/1798440 Title: passwords and keys crashes on entering zero password in 18.10 Status in seahorse package in Ubuntu: Expired Bug description: Entering a blank login password crashes Passwords and Keys without saving ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: gnome-terminal 3.30.1-1ubuntu1 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 Uname: Linux 4.18.0-10-generic x86_64 ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Oct 17 13:35:57 2018 ExecutablePath: /usr/lib/gnome-terminal/gnome-terminal-server InstallationDate: Installed on 2018-08-12 (66 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: gnome-terminal UpgradeStatus: Upgraded to cosmic on 2018-10-17 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/seahorse/+bug/1798440/+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 1847426] Re: WebKitWebProcess crashed with signal 7
[Expired for webkit2gtk (Ubuntu) because there has been no activity for 60 days.] ** Changed in: webkit2gtk (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to webkit2gtk in Ubuntu. https://bugs.launchpad.net/bugs/1847426 Title: WebKitWebProcess crashed with signal 7 Status in webkit2gtk package in Ubuntu: Expired Bug description: the process ran out of disk space ProblemType: Crash DistroRelease: Ubuntu 18.04 Package: libwebkit2gtk-4.0-37 2.24.4-0ubuntu0.18.04.1 ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18 Uname: Linux 4.15.0-38-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Oct 9 06:35:51 2019 ExecutablePath: /usr/lib/x86_64-linux-gnu/webkit2gtk-4.0/WebKitWebProcess InstallationDate: Installed on 2017-10-13 (725 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Beta amd64 (20171012) ProcCmdline: /usr/lib/x86_64-linux-gnu/webkit2gtk-4.0/WebKitWebProcess 5 25 Signal: 7 SourcePackage: webkit2gtk StacktraceTop: () at /usr/lib/x86_64-linux-gnu/dri/i965_dri.so () at /usr/lib/x86_64-linux-gnu/dri/i965_dri.so () at /usr/lib/x86_64-linux-gnu/dri/i965_dri.so () at /usr/lib/x86_64-linux-gnu/libwebkit2gtk-4.0.so.37 () at /usr/lib/x86_64-linux-gnu/libwebkit2gtk-4.0.so.37 Title: WebKitWebProcess crashed with signal 7 UpgradeStatus: Upgraded to bionic on 2018-06-25 (470 days ago) UserGroups: adm cdrom dialout dip kvm libvirt lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/webkit2gtk/+bug/1847426/+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 1711079] Re: Mobile bradband doesnt work after suspend/logout
[Expired for mobile-broadband-provider-info (Ubuntu) because there has been no activity for 60 days.] ** Changed in: mobile-broadband-provider-info (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mobile-broadband-provider-info in Ubuntu. https://bugs.launchpad.net/bugs/1711079 Title: Mobile bradband doesnt work after suspend/logout Status in mobile-broadband-provider-info package in Ubuntu: Expired Bug description: When I turn on my laptop (HP EliteBook Folio 9470m), I can use my sim card internet, but when I log in after my laptop was suspended, I can not connect to network again. I need to restart it to connect again. Ubuntu version 16.04 LTS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mobile-broadband-provider-info/+bug/1711079/+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 1796554] Re: seahorse crashed with SIGSEGV in g_variant_unref()
[Expired for seahorse (Ubuntu) because there has been no activity for 60 days.] ** Changed in: seahorse (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to seahorse in Ubuntu. https://bugs.launchpad.net/bugs/1796554 Title: seahorse crashed with SIGSEGV in g_variant_unref() Status in seahorse package in Ubuntu: Expired Bug description: crash after pw changed ProblemType: Crash DistroRelease: Ubuntu 18.10 Package: seahorse 3.30-1 ProcVersionSignature: Ubuntu 4.18.0-8.9-generic 4.18.7 Uname: Linux 4.18.0-8-generic x86_64 ApportVersion: 2.20.10-0ubuntu11 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Oct 7 11:43:55 2018 ExecutablePath: /usr/bin/seahorse InstallationDate: Installed on 2018-10-04 (2 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Beta amd64 (20180927) ProcCmdline: /usr/bin/seahorse --gapplication-service ProcEnviron: SHELL=/bin/bash XDG_RUNTIME_DIR= PATH=(custom, no user) LANGUAGE=en_GB:en LANG=en_GB.UTF-8 SegvAnalysis: Segfault happened at: 0x7f27b08238c5 :mov 0x24(%rdi),%eax PC (0x7f27b08238c5) ok source "0x24(%rdi)" (0x983a3ef4) not located in a known VMA region (needed readable region)! destination "%eax" ok SegvReason: reading unknown VMA Signal: 11 SourcePackage: seahorse StacktraceTop: g_variant_unref () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () g_simple_async_result_complete () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libsecret-1.so.0 g_simple_async_result_complete () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 Title: seahorse crashed with SIGSEGV in g_variant_unref() 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/seahorse/+bug/1796554/+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 1854864] Re: "Dock" is used instead of "Dash"
Windows calls it the "Task Bar". MacOS calls it the "Dock". Why not call it the "Dash"? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1854864 Title: "Dock" is used instead of "Dash" Status in gnome-control-center package in Ubuntu: Opinion Bug description: Ubuntu 19.10 1) Open Settings app. The word "Dock" is displayed as an option. 2) The word "Dash" should have been displayed instead of "Dock". The "Visual overview of Gnome" in the "Ubuntu Desktop Guide" refers to the icon bar as the "Dash". 3) The word "Dock" was displayed instead of "Dash". To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1854864/+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 1855584] Re: [Hasee NH50_70_55_58_ED, EDQ] pulseaudio: sometimes generate eternal white noise even reboot to Windows OS
> #19 I tried the two kernel. For now. And have another problem, maybe not important. 樂 5.3.0-24-ubuntu (current) 5.4.2-mainline On the beginning, speaker never works. Headphone have only two volume: 0 and 100 (unable to change volume). I removed '/var/lib/alsa/*' and '~/.config/pulse/*'. 1st reboot: pulseaudio not work. 2nd/3rd reboot: pulseaudio started. The volume is init value. 1st VLC play: speaker and headphone works. When changing volume, the music lags and lags and repeats. 2nd/3rd VLC play: volume changing becomes smooth. Everything just works. (The two kernels have the same behavior above.) But... The noise problem is random, keep watching. -- 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/1855584 Title: [Hasee NH50_70_55_58_ED,EDQ] pulseaudio: sometimes generate eternal white noise even reboot to Windows OS Status in alsa-driver package in Ubuntu: New Status in linux package in Ubuntu: Incomplete Status in pulseaudio package in Ubuntu: New Bug description: This problem seems begin from ubuntu 19.04. Sometimes after login, headphone outputs white noise only, speaker does not work. Nothing can play music with the noise. The noise is impossible to stop except POWEROFF the PC. Rebooting cannot stop it, the noise keeps even reboot into Windows OS. In Windows OS, headphone still white noise, after unplugging headphone, the speaker does not work, too. It works fine in Windows OS. If I remove pulseaudio, only use ALSA. It also works stable. (But now... firefox do not support ALSA, chromium-snap do not support ALSA too...) It seems pulseaudio killed the sound card... The problem appears randomly, I do not know how to reproduce. sorry... ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.0-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-0ubuntu13 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: aya5434 F pulseaudio /dev/snd/controlC0: aya5434 F pulseaudio Date: Sun Dec 8 19:51:02 2019 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/16/2018 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 1.07.05RHZX1 dmi.board.asset.tag: Tag 12345 dmi.board.name: NH50_70_55_58_ED,EDQ dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.modalias: dmi:bvnINSYDECorp.:bvr1.07.05RHZX1:bd11/16/2018:svnHASEEComputer:pnNH50_70_55_58_ED,EDQ:pvrNotApplicable:rvnNotebook:rnNH50_70_55_58_ED,EDQ:rvrNotApplicable:cvnNotebook:ct10:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: NH50_70_55_58_ED,EDQ dmi.product.sku: Not Applicable dmi.product.version: Not Applicable dmi.sys.vendor: HASEE Computer --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu13 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: aya1796 F pulseaudio /dev/snd/controlC1: aya1796 F pulseaudio DistroRelease: Ubuntu 20.04 MachineType: HASEE Computer NH50_70_55_58_ED,EDQ NonfreeKernelModules: nvidia_modeset nvidia Package: pulseaudio 1:13.0-1ubuntu1 PackageArchitecture: amd64 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-24-generic root=UUID=deda3529-9822-4f34-9103-f54a6a63d681 ro ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.3.0-24-generic N/A linux-backports-modules-5.3.0-24-generic N/A linux-firmware1.184 Tags: focal Uname: Linux 5.3.0-24-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 11/16/2018 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 1.07.05RHZX1 dmi.board.asset.tag: Tag 12345 dmi.board.name: NH50_70_55_58_ED,EDQ dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.modalias: dmi:bvnINSYDECorp.:bvr1.07.05RHZX1:bd11/16/2018:svnHASEEComputer:pnNH50_70_55_58_ED,EDQ:pvrNotApplicable:rvnNotebook:rnNH50_70_55_58_ED,EDQ:rvrNotApplicable:cvnNotebook:ct10:cvrN/A: dmi.product.family: Not Applicable
[Desktop-packages] [Bug 1855644] [NEW] Move "Default Applications" to "Applications" screen.
Public bug reported: 1) Ubuntu 19.10 2) 1:3.34.1-1ubuntu2 3) Display "Default Applications" on the Application screen. 4) "Default Applications" is not displayed on the Application screen. ** Affects: gnome-control-center (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1855644 Title: Move "Default Applications" to "Applications" screen. Status in gnome-control-center package in Ubuntu: New Bug description: 1) Ubuntu 19.10 2) 1:3.34.1-1ubuntu2 3) Display "Default Applications" on the Application screen. 4) "Default Applications" is not displayed on the Application screen. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1855644/+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 1853440] Re: Volume either 0 or 100% on Lenovo X1 Carbon G7
Could you try linux-oem-osp1 kernel? -- 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/1853440 Title: Volume either 0 or 100% on Lenovo X1 Carbon G7 Status in gnome-shell package in Ubuntu: Incomplete Status in linux package in Ubuntu: Incomplete Bug description: Volume increasing or decreasing doesn't work. I can only toggle sound on (= 100%) and off (= 0%). What I found out is that the Master channel seems to have no effect for volume adjustments, but the PCM channel does. If the sound is muted, PCM is set to 0 and therefore the sound is toggled off, but when I increase the sound a bit, PCM jumps straight to 100, causing the speakers to be very load. I have attached alsa-info output. System environment: Pop!_OS 19.10 Release: 19.10 Alsa-Version: alsa-base: 1.0.25 Sound Card: HDA-Intel Codec: Realtek ALC285 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CurrentDesktop: pop:GNOME DisplayManager: gdm3 DistroRelease: Pop!_OS 19.10 Package: linux PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.3.0-22.24+system76~1573659475~19.10~26b2022-generic 5.3.7 RelatedPackageVersions: mutter-common 3.34.1+git20191107-1ubuntu1~19.10.1pop0~1573683812~19.10~50e928a Tags: third-party-packages eoan Uname: Linux 5.3.0-22-generic x86_64 UnreportableReason: This is not an official Pop!_OS package. Please remove any third party package and try again. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1853440/+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 1855584] Re: [Hasee NH50_70_55_58_ED, EDQ] pulseaudio: sometimes generate eternal white noise even reboot to Windows OS
> #2 It is not a typo. The problem goes half a year. I remember it was fine in 18.04 and 18.10. Also, before headphone becomes white noise, the speaker does a very very short time of "PA!" sound, like a bomb. I will try the new kernel for days and reply. :) -- 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/1855584 Title: [Hasee NH50_70_55_58_ED,EDQ] pulseaudio: sometimes generate eternal white noise even reboot to Windows OS Status in alsa-driver package in Ubuntu: New Status in linux package in Ubuntu: Incomplete Status in pulseaudio package in Ubuntu: New Bug description: This problem seems begin from ubuntu 19.04. Sometimes after login, headphone outputs white noise only, speaker does not work. Nothing can play music with the noise. The noise is impossible to stop except POWEROFF the PC. Rebooting cannot stop it, the noise keeps even reboot into Windows OS. In Windows OS, headphone still white noise, after unplugging headphone, the speaker does not work, too. It works fine in Windows OS. If I remove pulseaudio, only use ALSA. It also works stable. (But now... firefox do not support ALSA, chromium-snap do not support ALSA too...) It seems pulseaudio killed the sound card... The problem appears randomly, I do not know how to reproduce. sorry... ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.0-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-0ubuntu13 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: aya5434 F pulseaudio /dev/snd/controlC0: aya5434 F pulseaudio Date: Sun Dec 8 19:51:02 2019 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/16/2018 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 1.07.05RHZX1 dmi.board.asset.tag: Tag 12345 dmi.board.name: NH50_70_55_58_ED,EDQ dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.modalias: dmi:bvnINSYDECorp.:bvr1.07.05RHZX1:bd11/16/2018:svnHASEEComputer:pnNH50_70_55_58_ED,EDQ:pvrNotApplicable:rvnNotebook:rnNH50_70_55_58_ED,EDQ:rvrNotApplicable:cvnNotebook:ct10:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: NH50_70_55_58_ED,EDQ dmi.product.sku: Not Applicable dmi.product.version: Not Applicable dmi.sys.vendor: HASEE Computer --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu13 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: aya1796 F pulseaudio /dev/snd/controlC1: aya1796 F pulseaudio DistroRelease: Ubuntu 20.04 MachineType: HASEE Computer NH50_70_55_58_ED,EDQ NonfreeKernelModules: nvidia_modeset nvidia Package: pulseaudio 1:13.0-1ubuntu1 PackageArchitecture: amd64 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-24-generic root=UUID=deda3529-9822-4f34-9103-f54a6a63d681 ro ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.3.0-24-generic N/A linux-backports-modules-5.3.0-24-generic N/A linux-firmware1.184 Tags: focal Uname: Linux 5.3.0-24-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 11/16/2018 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 1.07.05RHZX1 dmi.board.asset.tag: Tag 12345 dmi.board.name: NH50_70_55_58_ED,EDQ dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.modalias: dmi:bvnINSYDECorp.:bvr1.07.05RHZX1:bd11/16/2018:svnHASEEComputer:pnNH50_70_55_58_ED,EDQ:pvrNotApplicable:rvnNotebook:rnNH50_70_55_58_ED,EDQ:rvrNotApplicable:cvnNotebook:ct10:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: NH50_70_55_58_ED,EDQ dmi.product.sku: Not Applicable dmi.product.version: Not Applicable dmi.sys.vendor: HASEE Computer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1855584/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe :
[Desktop-packages] [Bug 1855584] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1855584/+attachment/5310930/+files/WifiSyslog.txt -- 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/1855584 Title: [Hasee NH50_70_55_58_ED,EDQ] pulseaudio: sometimes generate eternal white noise even reboot to Windows OS Status in alsa-driver package in Ubuntu: New Status in linux package in Ubuntu: Incomplete Status in pulseaudio package in Ubuntu: New Bug description: This problem seems begin from ubuntu 19.04. Sometimes after login, headphone outputs white noise only, speaker does not work. Nothing can play music with the noise. The noise is impossible to stop except POWEROFF the PC. Rebooting cannot stop it, the noise keeps even reboot into Windows OS. In Windows OS, headphone still white noise, after unplugging headphone, the speaker does not work, too. It works fine in Windows OS. If I remove pulseaudio, only use ALSA. It also works stable. (But now... firefox do not support ALSA, chromium-snap do not support ALSA too...) It seems pulseaudio killed the sound card... The problem appears randomly, I do not know how to reproduce. sorry... ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.0-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-0ubuntu13 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: aya5434 F pulseaudio /dev/snd/controlC0: aya5434 F pulseaudio Date: Sun Dec 8 19:51:02 2019 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/16/2018 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 1.07.05RHZX1 dmi.board.asset.tag: Tag 12345 dmi.board.name: NH50_70_55_58_ED,EDQ dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.modalias: dmi:bvnINSYDECorp.:bvr1.07.05RHZX1:bd11/16/2018:svnHASEEComputer:pnNH50_70_55_58_ED,EDQ:pvrNotApplicable:rvnNotebook:rnNH50_70_55_58_ED,EDQ:rvrNotApplicable:cvnNotebook:ct10:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: NH50_70_55_58_ED,EDQ dmi.product.sku: Not Applicable dmi.product.version: Not Applicable dmi.sys.vendor: HASEE Computer --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu13 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: aya1796 F pulseaudio /dev/snd/controlC1: aya1796 F pulseaudio DistroRelease: Ubuntu 20.04 MachineType: HASEE Computer NH50_70_55_58_ED,EDQ NonfreeKernelModules: nvidia_modeset nvidia Package: pulseaudio 1:13.0-1ubuntu1 PackageArchitecture: amd64 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-24-generic root=UUID=deda3529-9822-4f34-9103-f54a6a63d681 ro ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.3.0-24-generic N/A linux-backports-modules-5.3.0-24-generic N/A linux-firmware1.184 Tags: focal Uname: Linux 5.3.0-24-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 11/16/2018 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 1.07.05RHZX1 dmi.board.asset.tag: Tag 12345 dmi.board.name: NH50_70_55_58_ED,EDQ dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.modalias: dmi:bvnINSYDECorp.:bvr1.07.05RHZX1:bd11/16/2018:svnHASEEComputer:pnNH50_70_55_58_ED,EDQ:pvrNotApplicable:rvnNotebook:rnNH50_70_55_58_ED,EDQ:rvrNotApplicable:cvnNotebook:ct10:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: NH50_70_55_58_ED,EDQ dmi.product.sku: Not Applicable dmi.product.version: Not Applicable dmi.sys.vendor: HASEE Computer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1855584/+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 1855584] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1855584/+attachment/5310929/+files/UdevDb.txt -- 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/1855584 Title: [Hasee NH50_70_55_58_ED,EDQ] pulseaudio: sometimes generate eternal white noise even reboot to Windows OS Status in alsa-driver package in Ubuntu: New Status in linux package in Ubuntu: Incomplete Status in pulseaudio package in Ubuntu: New Bug description: This problem seems begin from ubuntu 19.04. Sometimes after login, headphone outputs white noise only, speaker does not work. Nothing can play music with the noise. The noise is impossible to stop except POWEROFF the PC. Rebooting cannot stop it, the noise keeps even reboot into Windows OS. In Windows OS, headphone still white noise, after unplugging headphone, the speaker does not work, too. It works fine in Windows OS. If I remove pulseaudio, only use ALSA. It also works stable. (But now... firefox do not support ALSA, chromium-snap do not support ALSA too...) It seems pulseaudio killed the sound card... The problem appears randomly, I do not know how to reproduce. sorry... ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.0-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-0ubuntu13 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: aya5434 F pulseaudio /dev/snd/controlC0: aya5434 F pulseaudio Date: Sun Dec 8 19:51:02 2019 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/16/2018 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 1.07.05RHZX1 dmi.board.asset.tag: Tag 12345 dmi.board.name: NH50_70_55_58_ED,EDQ dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.modalias: dmi:bvnINSYDECorp.:bvr1.07.05RHZX1:bd11/16/2018:svnHASEEComputer:pnNH50_70_55_58_ED,EDQ:pvrNotApplicable:rvnNotebook:rnNH50_70_55_58_ED,EDQ:rvrNotApplicable:cvnNotebook:ct10:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: NH50_70_55_58_ED,EDQ dmi.product.sku: Not Applicable dmi.product.version: Not Applicable dmi.sys.vendor: HASEE Computer --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu13 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: aya1796 F pulseaudio /dev/snd/controlC1: aya1796 F pulseaudio DistroRelease: Ubuntu 20.04 MachineType: HASEE Computer NH50_70_55_58_ED,EDQ NonfreeKernelModules: nvidia_modeset nvidia Package: pulseaudio 1:13.0-1ubuntu1 PackageArchitecture: amd64 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-24-generic root=UUID=deda3529-9822-4f34-9103-f54a6a63d681 ro ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.3.0-24-generic N/A linux-backports-modules-5.3.0-24-generic N/A linux-firmware1.184 Tags: focal Uname: Linux 5.3.0-24-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 11/16/2018 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 1.07.05RHZX1 dmi.board.asset.tag: Tag 12345 dmi.board.name: NH50_70_55_58_ED,EDQ dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.modalias: dmi:bvnINSYDECorp.:bvr1.07.05RHZX1:bd11/16/2018:svnHASEEComputer:pnNH50_70_55_58_ED,EDQ:pvrNotApplicable:rvnNotebook:rnNH50_70_55_58_ED,EDQ:rvrNotApplicable:cvnNotebook:ct10:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: NH50_70_55_58_ED,EDQ dmi.product.sku: Not Applicable dmi.product.version: Not Applicable dmi.sys.vendor: HASEE Computer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1855584/+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 1855584] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1855584/+attachment/5310922/+files/Lsusb.txt -- 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/1855584 Title: [Hasee NH50_70_55_58_ED,EDQ] pulseaudio: sometimes generate eternal white noise even reboot to Windows OS Status in alsa-driver package in Ubuntu: New Status in linux package in Ubuntu: Incomplete Status in pulseaudio package in Ubuntu: New Bug description: This problem seems begin from ubuntu 19.04. Sometimes after login, headphone outputs white noise only, speaker does not work. Nothing can play music with the noise. The noise is impossible to stop except POWEROFF the PC. Rebooting cannot stop it, the noise keeps even reboot into Windows OS. In Windows OS, headphone still white noise, after unplugging headphone, the speaker does not work, too. It works fine in Windows OS. If I remove pulseaudio, only use ALSA. It also works stable. (But now... firefox do not support ALSA, chromium-snap do not support ALSA too...) It seems pulseaudio killed the sound card... The problem appears randomly, I do not know how to reproduce. sorry... ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.0-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-0ubuntu13 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: aya5434 F pulseaudio /dev/snd/controlC0: aya5434 F pulseaudio Date: Sun Dec 8 19:51:02 2019 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/16/2018 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 1.07.05RHZX1 dmi.board.asset.tag: Tag 12345 dmi.board.name: NH50_70_55_58_ED,EDQ dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.modalias: dmi:bvnINSYDECorp.:bvr1.07.05RHZX1:bd11/16/2018:svnHASEEComputer:pnNH50_70_55_58_ED,EDQ:pvrNotApplicable:rvnNotebook:rnNH50_70_55_58_ED,EDQ:rvrNotApplicable:cvnNotebook:ct10:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: NH50_70_55_58_ED,EDQ dmi.product.sku: Not Applicable dmi.product.version: Not Applicable dmi.sys.vendor: HASEE Computer --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu13 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: aya1796 F pulseaudio /dev/snd/controlC1: aya1796 F pulseaudio DistroRelease: Ubuntu 20.04 MachineType: HASEE Computer NH50_70_55_58_ED,EDQ NonfreeKernelModules: nvidia_modeset nvidia Package: pulseaudio 1:13.0-1ubuntu1 PackageArchitecture: amd64 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-24-generic root=UUID=deda3529-9822-4f34-9103-f54a6a63d681 ro ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.3.0-24-generic N/A linux-backports-modules-5.3.0-24-generic N/A linux-firmware1.184 Tags: focal Uname: Linux 5.3.0-24-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 11/16/2018 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 1.07.05RHZX1 dmi.board.asset.tag: Tag 12345 dmi.board.name: NH50_70_55_58_ED,EDQ dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.modalias: dmi:bvnINSYDECorp.:bvr1.07.05RHZX1:bd11/16/2018:svnHASEEComputer:pnNH50_70_55_58_ED,EDQ:pvrNotApplicable:rvnNotebook:rnNH50_70_55_58_ED,EDQ:rvrNotApplicable:cvnNotebook:ct10:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: NH50_70_55_58_ED,EDQ dmi.product.sku: Not Applicable dmi.product.version: Not Applicable dmi.sys.vendor: HASEE Computer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1855584/+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 1855584] RfKill.txt
apport information ** Attachment added: "RfKill.txt" https://bugs.launchpad.net/bugs/1855584/+attachment/5310928/+files/RfKill.txt -- 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/1855584 Title: [Hasee NH50_70_55_58_ED,EDQ] pulseaudio: sometimes generate eternal white noise even reboot to Windows OS Status in alsa-driver package in Ubuntu: New Status in linux package in Ubuntu: Incomplete Status in pulseaudio package in Ubuntu: New Bug description: This problem seems begin from ubuntu 19.04. Sometimes after login, headphone outputs white noise only, speaker does not work. Nothing can play music with the noise. The noise is impossible to stop except POWEROFF the PC. Rebooting cannot stop it, the noise keeps even reboot into Windows OS. In Windows OS, headphone still white noise, after unplugging headphone, the speaker does not work, too. It works fine in Windows OS. If I remove pulseaudio, only use ALSA. It also works stable. (But now... firefox do not support ALSA, chromium-snap do not support ALSA too...) It seems pulseaudio killed the sound card... The problem appears randomly, I do not know how to reproduce. sorry... ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.0-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-0ubuntu13 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: aya5434 F pulseaudio /dev/snd/controlC0: aya5434 F pulseaudio Date: Sun Dec 8 19:51:02 2019 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/16/2018 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 1.07.05RHZX1 dmi.board.asset.tag: Tag 12345 dmi.board.name: NH50_70_55_58_ED,EDQ dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.modalias: dmi:bvnINSYDECorp.:bvr1.07.05RHZX1:bd11/16/2018:svnHASEEComputer:pnNH50_70_55_58_ED,EDQ:pvrNotApplicable:rvnNotebook:rnNH50_70_55_58_ED,EDQ:rvrNotApplicable:cvnNotebook:ct10:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: NH50_70_55_58_ED,EDQ dmi.product.sku: Not Applicable dmi.product.version: Not Applicable dmi.sys.vendor: HASEE Computer --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu13 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: aya1796 F pulseaudio /dev/snd/controlC1: aya1796 F pulseaudio DistroRelease: Ubuntu 20.04 MachineType: HASEE Computer NH50_70_55_58_ED,EDQ NonfreeKernelModules: nvidia_modeset nvidia Package: pulseaudio 1:13.0-1ubuntu1 PackageArchitecture: amd64 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-24-generic root=UUID=deda3529-9822-4f34-9103-f54a6a63d681 ro ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.3.0-24-generic N/A linux-backports-modules-5.3.0-24-generic N/A linux-firmware1.184 Tags: focal Uname: Linux 5.3.0-24-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 11/16/2018 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 1.07.05RHZX1 dmi.board.asset.tag: Tag 12345 dmi.board.name: NH50_70_55_58_ED,EDQ dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.modalias: dmi:bvnINSYDECorp.:bvr1.07.05RHZX1:bd11/16/2018:svnHASEEComputer:pnNH50_70_55_58_ED,EDQ:pvrNotApplicable:rvnNotebook:rnNH50_70_55_58_ED,EDQ:rvrNotApplicable:cvnNotebook:ct10:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: NH50_70_55_58_ED,EDQ dmi.product.sku: Not Applicable dmi.product.version: Not Applicable dmi.sys.vendor: HASEE Computer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1855584/+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 1855584] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1855584/+attachment/5310923/+files/ProcCpuinfoMinimal.txt -- 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/1855584 Title: [Hasee NH50_70_55_58_ED,EDQ] pulseaudio: sometimes generate eternal white noise even reboot to Windows OS Status in alsa-driver package in Ubuntu: New Status in linux package in Ubuntu: Incomplete Status in pulseaudio package in Ubuntu: New Bug description: This problem seems begin from ubuntu 19.04. Sometimes after login, headphone outputs white noise only, speaker does not work. Nothing can play music with the noise. The noise is impossible to stop except POWEROFF the PC. Rebooting cannot stop it, the noise keeps even reboot into Windows OS. In Windows OS, headphone still white noise, after unplugging headphone, the speaker does not work, too. It works fine in Windows OS. If I remove pulseaudio, only use ALSA. It also works stable. (But now... firefox do not support ALSA, chromium-snap do not support ALSA too...) It seems pulseaudio killed the sound card... The problem appears randomly, I do not know how to reproduce. sorry... ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.0-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-0ubuntu13 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: aya5434 F pulseaudio /dev/snd/controlC0: aya5434 F pulseaudio Date: Sun Dec 8 19:51:02 2019 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/16/2018 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 1.07.05RHZX1 dmi.board.asset.tag: Tag 12345 dmi.board.name: NH50_70_55_58_ED,EDQ dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.modalias: dmi:bvnINSYDECorp.:bvr1.07.05RHZX1:bd11/16/2018:svnHASEEComputer:pnNH50_70_55_58_ED,EDQ:pvrNotApplicable:rvnNotebook:rnNH50_70_55_58_ED,EDQ:rvrNotApplicable:cvnNotebook:ct10:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: NH50_70_55_58_ED,EDQ dmi.product.sku: Not Applicable dmi.product.version: Not Applicable dmi.sys.vendor: HASEE Computer --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu13 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: aya1796 F pulseaudio /dev/snd/controlC1: aya1796 F pulseaudio DistroRelease: Ubuntu 20.04 MachineType: HASEE Computer NH50_70_55_58_ED,EDQ NonfreeKernelModules: nvidia_modeset nvidia Package: pulseaudio 1:13.0-1ubuntu1 PackageArchitecture: amd64 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-24-generic root=UUID=deda3529-9822-4f34-9103-f54a6a63d681 ro ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.3.0-24-generic N/A linux-backports-modules-5.3.0-24-generic N/A linux-firmware1.184 Tags: focal Uname: Linux 5.3.0-24-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 11/16/2018 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 1.07.05RHZX1 dmi.board.asset.tag: Tag 12345 dmi.board.name: NH50_70_55_58_ED,EDQ dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.modalias: dmi:bvnINSYDECorp.:bvr1.07.05RHZX1:bd11/16/2018:svnHASEEComputer:pnNH50_70_55_58_ED,EDQ:pvrNotApplicable:rvnNotebook:rnNH50_70_55_58_ED,EDQ:rvrNotApplicable:cvnNotebook:ct10:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: NH50_70_55_58_ED,EDQ dmi.product.sku: Not Applicable dmi.product.version: Not Applicable dmi.sys.vendor: HASEE Computer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1855584/+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 1855584] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1855584/+attachment/5310927/+files/ProcModules.txt -- 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/1855584 Title: [Hasee NH50_70_55_58_ED,EDQ] pulseaudio: sometimes generate eternal white noise even reboot to Windows OS Status in alsa-driver package in Ubuntu: New Status in linux package in Ubuntu: Incomplete Status in pulseaudio package in Ubuntu: New Bug description: This problem seems begin from ubuntu 19.04. Sometimes after login, headphone outputs white noise only, speaker does not work. Nothing can play music with the noise. The noise is impossible to stop except POWEROFF the PC. Rebooting cannot stop it, the noise keeps even reboot into Windows OS. In Windows OS, headphone still white noise, after unplugging headphone, the speaker does not work, too. It works fine in Windows OS. If I remove pulseaudio, only use ALSA. It also works stable. (But now... firefox do not support ALSA, chromium-snap do not support ALSA too...) It seems pulseaudio killed the sound card... The problem appears randomly, I do not know how to reproduce. sorry... ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.0-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-0ubuntu13 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: aya5434 F pulseaudio /dev/snd/controlC0: aya5434 F pulseaudio Date: Sun Dec 8 19:51:02 2019 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/16/2018 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 1.07.05RHZX1 dmi.board.asset.tag: Tag 12345 dmi.board.name: NH50_70_55_58_ED,EDQ dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.modalias: dmi:bvnINSYDECorp.:bvr1.07.05RHZX1:bd11/16/2018:svnHASEEComputer:pnNH50_70_55_58_ED,EDQ:pvrNotApplicable:rvnNotebook:rnNH50_70_55_58_ED,EDQ:rvrNotApplicable:cvnNotebook:ct10:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: NH50_70_55_58_ED,EDQ dmi.product.sku: Not Applicable dmi.product.version: Not Applicable dmi.sys.vendor: HASEE Computer --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu13 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: aya1796 F pulseaudio /dev/snd/controlC1: aya1796 F pulseaudio DistroRelease: Ubuntu 20.04 MachineType: HASEE Computer NH50_70_55_58_ED,EDQ NonfreeKernelModules: nvidia_modeset nvidia Package: pulseaudio 1:13.0-1ubuntu1 PackageArchitecture: amd64 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-24-generic root=UUID=deda3529-9822-4f34-9103-f54a6a63d681 ro ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.3.0-24-generic N/A linux-backports-modules-5.3.0-24-generic N/A linux-firmware1.184 Tags: focal Uname: Linux 5.3.0-24-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 11/16/2018 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 1.07.05RHZX1 dmi.board.asset.tag: Tag 12345 dmi.board.name: NH50_70_55_58_ED,EDQ dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.modalias: dmi:bvnINSYDECorp.:bvr1.07.05RHZX1:bd11/16/2018:svnHASEEComputer:pnNH50_70_55_58_ED,EDQ:pvrNotApplicable:rvnNotebook:rnNH50_70_55_58_ED,EDQ:rvrNotApplicable:cvnNotebook:ct10:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: NH50_70_55_58_ED,EDQ dmi.product.sku: Not Applicable dmi.product.version: Not Applicable dmi.sys.vendor: HASEE Computer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1855584/+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 1855584] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1855584/+attachment/5310924/+files/ProcEnviron.txt -- 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/1855584 Title: [Hasee NH50_70_55_58_ED,EDQ] pulseaudio: sometimes generate eternal white noise even reboot to Windows OS Status in alsa-driver package in Ubuntu: New Status in linux package in Ubuntu: Incomplete Status in pulseaudio package in Ubuntu: New Bug description: This problem seems begin from ubuntu 19.04. Sometimes after login, headphone outputs white noise only, speaker does not work. Nothing can play music with the noise. The noise is impossible to stop except POWEROFF the PC. Rebooting cannot stop it, the noise keeps even reboot into Windows OS. In Windows OS, headphone still white noise, after unplugging headphone, the speaker does not work, too. It works fine in Windows OS. If I remove pulseaudio, only use ALSA. It also works stable. (But now... firefox do not support ALSA, chromium-snap do not support ALSA too...) It seems pulseaudio killed the sound card... The problem appears randomly, I do not know how to reproduce. sorry... ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.0-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-0ubuntu13 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: aya5434 F pulseaudio /dev/snd/controlC0: aya5434 F pulseaudio Date: Sun Dec 8 19:51:02 2019 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/16/2018 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 1.07.05RHZX1 dmi.board.asset.tag: Tag 12345 dmi.board.name: NH50_70_55_58_ED,EDQ dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.modalias: dmi:bvnINSYDECorp.:bvr1.07.05RHZX1:bd11/16/2018:svnHASEEComputer:pnNH50_70_55_58_ED,EDQ:pvrNotApplicable:rvnNotebook:rnNH50_70_55_58_ED,EDQ:rvrNotApplicable:cvnNotebook:ct10:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: NH50_70_55_58_ED,EDQ dmi.product.sku: Not Applicable dmi.product.version: Not Applicable dmi.sys.vendor: HASEE Computer --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu13 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: aya1796 F pulseaudio /dev/snd/controlC1: aya1796 F pulseaudio DistroRelease: Ubuntu 20.04 MachineType: HASEE Computer NH50_70_55_58_ED,EDQ NonfreeKernelModules: nvidia_modeset nvidia Package: pulseaudio 1:13.0-1ubuntu1 PackageArchitecture: amd64 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-24-generic root=UUID=deda3529-9822-4f34-9103-f54a6a63d681 ro ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.3.0-24-generic N/A linux-backports-modules-5.3.0-24-generic N/A linux-firmware1.184 Tags: focal Uname: Linux 5.3.0-24-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 11/16/2018 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 1.07.05RHZX1 dmi.board.asset.tag: Tag 12345 dmi.board.name: NH50_70_55_58_ED,EDQ dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.modalias: dmi:bvnINSYDECorp.:bvr1.07.05RHZX1:bd11/16/2018:svnHASEEComputer:pnNH50_70_55_58_ED,EDQ:pvrNotApplicable:rvnNotebook:rnNH50_70_55_58_ED,EDQ:rvrNotApplicable:cvnNotebook:ct10:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: NH50_70_55_58_ED,EDQ dmi.product.sku: Not Applicable dmi.product.version: Not Applicable dmi.sys.vendor: HASEE Computer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1855584/+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 1855584] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1855584/+attachment/5310925/+files/ProcInterrupts.txt -- 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/1855584 Title: [Hasee NH50_70_55_58_ED,EDQ] pulseaudio: sometimes generate eternal white noise even reboot to Windows OS Status in alsa-driver package in Ubuntu: New Status in linux package in Ubuntu: Incomplete Status in pulseaudio package in Ubuntu: New Bug description: This problem seems begin from ubuntu 19.04. Sometimes after login, headphone outputs white noise only, speaker does not work. Nothing can play music with the noise. The noise is impossible to stop except POWEROFF the PC. Rebooting cannot stop it, the noise keeps even reboot into Windows OS. In Windows OS, headphone still white noise, after unplugging headphone, the speaker does not work, too. It works fine in Windows OS. If I remove pulseaudio, only use ALSA. It also works stable. (But now... firefox do not support ALSA, chromium-snap do not support ALSA too...) It seems pulseaudio killed the sound card... The problem appears randomly, I do not know how to reproduce. sorry... ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.0-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-0ubuntu13 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: aya5434 F pulseaudio /dev/snd/controlC0: aya5434 F pulseaudio Date: Sun Dec 8 19:51:02 2019 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/16/2018 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 1.07.05RHZX1 dmi.board.asset.tag: Tag 12345 dmi.board.name: NH50_70_55_58_ED,EDQ dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.modalias: dmi:bvnINSYDECorp.:bvr1.07.05RHZX1:bd11/16/2018:svnHASEEComputer:pnNH50_70_55_58_ED,EDQ:pvrNotApplicable:rvnNotebook:rnNH50_70_55_58_ED,EDQ:rvrNotApplicable:cvnNotebook:ct10:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: NH50_70_55_58_ED,EDQ dmi.product.sku: Not Applicable dmi.product.version: Not Applicable dmi.sys.vendor: HASEE Computer --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu13 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: aya1796 F pulseaudio /dev/snd/controlC1: aya1796 F pulseaudio DistroRelease: Ubuntu 20.04 MachineType: HASEE Computer NH50_70_55_58_ED,EDQ NonfreeKernelModules: nvidia_modeset nvidia Package: pulseaudio 1:13.0-1ubuntu1 PackageArchitecture: amd64 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-24-generic root=UUID=deda3529-9822-4f34-9103-f54a6a63d681 ro ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.3.0-24-generic N/A linux-backports-modules-5.3.0-24-generic N/A linux-firmware1.184 Tags: focal Uname: Linux 5.3.0-24-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 11/16/2018 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 1.07.05RHZX1 dmi.board.asset.tag: Tag 12345 dmi.board.name: NH50_70_55_58_ED,EDQ dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.modalias: dmi:bvnINSYDECorp.:bvr1.07.05RHZX1:bd11/16/2018:svnHASEEComputer:pnNH50_70_55_58_ED,EDQ:pvrNotApplicable:rvnNotebook:rnNH50_70_55_58_ED,EDQ:rvrNotApplicable:cvnNotebook:ct10:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: NH50_70_55_58_ED,EDQ dmi.product.sku: Not Applicable dmi.product.version: Not Applicable dmi.sys.vendor: HASEE Computer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1855584/+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 1855584] Dependencies.txt
apport information ** Attachment added: "Dependencies.txt" https://bugs.launchpad.net/bugs/1855584/+attachment/5310919/+files/Dependencies.txt -- 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/1855584 Title: [Hasee NH50_70_55_58_ED,EDQ] pulseaudio: sometimes generate eternal white noise even reboot to Windows OS Status in alsa-driver package in Ubuntu: New Status in linux package in Ubuntu: Incomplete Status in pulseaudio package in Ubuntu: New Bug description: This problem seems begin from ubuntu 19.04. Sometimes after login, headphone outputs white noise only, speaker does not work. Nothing can play music with the noise. The noise is impossible to stop except POWEROFF the PC. Rebooting cannot stop it, the noise keeps even reboot into Windows OS. In Windows OS, headphone still white noise, after unplugging headphone, the speaker does not work, too. It works fine in Windows OS. If I remove pulseaudio, only use ALSA. It also works stable. (But now... firefox do not support ALSA, chromium-snap do not support ALSA too...) It seems pulseaudio killed the sound card... The problem appears randomly, I do not know how to reproduce. sorry... ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.0-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-0ubuntu13 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: aya5434 F pulseaudio /dev/snd/controlC0: aya5434 F pulseaudio Date: Sun Dec 8 19:51:02 2019 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/16/2018 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 1.07.05RHZX1 dmi.board.asset.tag: Tag 12345 dmi.board.name: NH50_70_55_58_ED,EDQ dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.modalias: dmi:bvnINSYDECorp.:bvr1.07.05RHZX1:bd11/16/2018:svnHASEEComputer:pnNH50_70_55_58_ED,EDQ:pvrNotApplicable:rvnNotebook:rnNH50_70_55_58_ED,EDQ:rvrNotApplicable:cvnNotebook:ct10:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: NH50_70_55_58_ED,EDQ dmi.product.sku: Not Applicable dmi.product.version: Not Applicable dmi.sys.vendor: HASEE Computer --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu13 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: aya1796 F pulseaudio /dev/snd/controlC1: aya1796 F pulseaudio DistroRelease: Ubuntu 20.04 MachineType: HASEE Computer NH50_70_55_58_ED,EDQ NonfreeKernelModules: nvidia_modeset nvidia Package: pulseaudio 1:13.0-1ubuntu1 PackageArchitecture: amd64 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-24-generic root=UUID=deda3529-9822-4f34-9103-f54a6a63d681 ro ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.3.0-24-generic N/A linux-backports-modules-5.3.0-24-generic N/A linux-firmware1.184 Tags: focal Uname: Linux 5.3.0-24-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 11/16/2018 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 1.07.05RHZX1 dmi.board.asset.tag: Tag 12345 dmi.board.name: NH50_70_55_58_ED,EDQ dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.modalias: dmi:bvnINSYDECorp.:bvr1.07.05RHZX1:bd11/16/2018:svnHASEEComputer:pnNH50_70_55_58_ED,EDQ:pvrNotApplicable:rvnNotebook:rnNH50_70_55_58_ED,EDQ:rvrNotApplicable:cvnNotebook:ct10:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: NH50_70_55_58_ED,EDQ dmi.product.sku: Not Applicable dmi.product.version: Not Applicable dmi.sys.vendor: HASEE Computer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1855584/+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 1855584] IwConfig.txt
apport information ** Attachment added: "IwConfig.txt" https://bugs.launchpad.net/bugs/1855584/+attachment/5310920/+files/IwConfig.txt -- 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/1855584 Title: [Hasee NH50_70_55_58_ED,EDQ] pulseaudio: sometimes generate eternal white noise even reboot to Windows OS Status in alsa-driver package in Ubuntu: New Status in linux package in Ubuntu: Incomplete Status in pulseaudio package in Ubuntu: New Bug description: This problem seems begin from ubuntu 19.04. Sometimes after login, headphone outputs white noise only, speaker does not work. Nothing can play music with the noise. The noise is impossible to stop except POWEROFF the PC. Rebooting cannot stop it, the noise keeps even reboot into Windows OS. In Windows OS, headphone still white noise, after unplugging headphone, the speaker does not work, too. It works fine in Windows OS. If I remove pulseaudio, only use ALSA. It also works stable. (But now... firefox do not support ALSA, chromium-snap do not support ALSA too...) It seems pulseaudio killed the sound card... The problem appears randomly, I do not know how to reproduce. sorry... ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.0-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-0ubuntu13 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: aya5434 F pulseaudio /dev/snd/controlC0: aya5434 F pulseaudio Date: Sun Dec 8 19:51:02 2019 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/16/2018 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 1.07.05RHZX1 dmi.board.asset.tag: Tag 12345 dmi.board.name: NH50_70_55_58_ED,EDQ dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.modalias: dmi:bvnINSYDECorp.:bvr1.07.05RHZX1:bd11/16/2018:svnHASEEComputer:pnNH50_70_55_58_ED,EDQ:pvrNotApplicable:rvnNotebook:rnNH50_70_55_58_ED,EDQ:rvrNotApplicable:cvnNotebook:ct10:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: NH50_70_55_58_ED,EDQ dmi.product.sku: Not Applicable dmi.product.version: Not Applicable dmi.sys.vendor: HASEE Computer --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu13 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: aya1796 F pulseaudio /dev/snd/controlC1: aya1796 F pulseaudio DistroRelease: Ubuntu 20.04 MachineType: HASEE Computer NH50_70_55_58_ED,EDQ NonfreeKernelModules: nvidia_modeset nvidia Package: pulseaudio 1:13.0-1ubuntu1 PackageArchitecture: amd64 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-24-generic root=UUID=deda3529-9822-4f34-9103-f54a6a63d681 ro ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.3.0-24-generic N/A linux-backports-modules-5.3.0-24-generic N/A linux-firmware1.184 Tags: focal Uname: Linux 5.3.0-24-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 11/16/2018 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 1.07.05RHZX1 dmi.board.asset.tag: Tag 12345 dmi.board.name: NH50_70_55_58_ED,EDQ dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.modalias: dmi:bvnINSYDECorp.:bvr1.07.05RHZX1:bd11/16/2018:svnHASEEComputer:pnNH50_70_55_58_ED,EDQ:pvrNotApplicable:rvnNotebook:rnNH50_70_55_58_ED,EDQ:rvrNotApplicable:cvnNotebook:ct10:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: NH50_70_55_58_ED,EDQ dmi.product.sku: Not Applicable dmi.product.version: Not Applicable dmi.sys.vendor: HASEE Computer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1855584/+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 1855584] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1855584/+attachment/5310921/+files/Lspci.txt -- 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/1855584 Title: [Hasee NH50_70_55_58_ED,EDQ] pulseaudio: sometimes generate eternal white noise even reboot to Windows OS Status in alsa-driver package in Ubuntu: New Status in linux package in Ubuntu: Incomplete Status in pulseaudio package in Ubuntu: New Bug description: This problem seems begin from ubuntu 19.04. Sometimes after login, headphone outputs white noise only, speaker does not work. Nothing can play music with the noise. The noise is impossible to stop except POWEROFF the PC. Rebooting cannot stop it, the noise keeps even reboot into Windows OS. In Windows OS, headphone still white noise, after unplugging headphone, the speaker does not work, too. It works fine in Windows OS. If I remove pulseaudio, only use ALSA. It also works stable. (But now... firefox do not support ALSA, chromium-snap do not support ALSA too...) It seems pulseaudio killed the sound card... The problem appears randomly, I do not know how to reproduce. sorry... ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.0-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-0ubuntu13 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: aya5434 F pulseaudio /dev/snd/controlC0: aya5434 F pulseaudio Date: Sun Dec 8 19:51:02 2019 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/16/2018 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 1.07.05RHZX1 dmi.board.asset.tag: Tag 12345 dmi.board.name: NH50_70_55_58_ED,EDQ dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.modalias: dmi:bvnINSYDECorp.:bvr1.07.05RHZX1:bd11/16/2018:svnHASEEComputer:pnNH50_70_55_58_ED,EDQ:pvrNotApplicable:rvnNotebook:rnNH50_70_55_58_ED,EDQ:rvrNotApplicable:cvnNotebook:ct10:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: NH50_70_55_58_ED,EDQ dmi.product.sku: Not Applicable dmi.product.version: Not Applicable dmi.sys.vendor: HASEE Computer --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu13 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: aya1796 F pulseaudio /dev/snd/controlC1: aya1796 F pulseaudio DistroRelease: Ubuntu 20.04 MachineType: HASEE Computer NH50_70_55_58_ED,EDQ NonfreeKernelModules: nvidia_modeset nvidia Package: pulseaudio 1:13.0-1ubuntu1 PackageArchitecture: amd64 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-24-generic root=UUID=deda3529-9822-4f34-9103-f54a6a63d681 ro ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.3.0-24-generic N/A linux-backports-modules-5.3.0-24-generic N/A linux-firmware1.184 Tags: focal Uname: Linux 5.3.0-24-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 11/16/2018 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 1.07.05RHZX1 dmi.board.asset.tag: Tag 12345 dmi.board.name: NH50_70_55_58_ED,EDQ dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.modalias: dmi:bvnINSYDECorp.:bvr1.07.05RHZX1:bd11/16/2018:svnHASEEComputer:pnNH50_70_55_58_ED,EDQ:pvrNotApplicable:rvnNotebook:rnNH50_70_55_58_ED,EDQ:rvrNotApplicable:cvnNotebook:ct10:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: NH50_70_55_58_ED,EDQ dmi.product.sku: Not Applicable dmi.product.version: Not Applicable dmi.sys.vendor: HASEE Computer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1855584/+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 1855584] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1855584/+attachment/5310918/+files/CurrentDmesg.txt -- 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/1855584 Title: [Hasee NH50_70_55_58_ED,EDQ] pulseaudio: sometimes generate eternal white noise even reboot to Windows OS Status in alsa-driver package in Ubuntu: New Status in linux package in Ubuntu: Incomplete Status in pulseaudio package in Ubuntu: New Bug description: This problem seems begin from ubuntu 19.04. Sometimes after login, headphone outputs white noise only, speaker does not work. Nothing can play music with the noise. The noise is impossible to stop except POWEROFF the PC. Rebooting cannot stop it, the noise keeps even reboot into Windows OS. In Windows OS, headphone still white noise, after unplugging headphone, the speaker does not work, too. It works fine in Windows OS. If I remove pulseaudio, only use ALSA. It also works stable. (But now... firefox do not support ALSA, chromium-snap do not support ALSA too...) It seems pulseaudio killed the sound card... The problem appears randomly, I do not know how to reproduce. sorry... ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.0-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-0ubuntu13 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: aya5434 F pulseaudio /dev/snd/controlC0: aya5434 F pulseaudio Date: Sun Dec 8 19:51:02 2019 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/16/2018 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 1.07.05RHZX1 dmi.board.asset.tag: Tag 12345 dmi.board.name: NH50_70_55_58_ED,EDQ dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.modalias: dmi:bvnINSYDECorp.:bvr1.07.05RHZX1:bd11/16/2018:svnHASEEComputer:pnNH50_70_55_58_ED,EDQ:pvrNotApplicable:rvnNotebook:rnNH50_70_55_58_ED,EDQ:rvrNotApplicable:cvnNotebook:ct10:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: NH50_70_55_58_ED,EDQ dmi.product.sku: Not Applicable dmi.product.version: Not Applicable dmi.sys.vendor: HASEE Computer --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu13 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: aya1796 F pulseaudio /dev/snd/controlC1: aya1796 F pulseaudio DistroRelease: Ubuntu 20.04 MachineType: HASEE Computer NH50_70_55_58_ED,EDQ NonfreeKernelModules: nvidia_modeset nvidia Package: pulseaudio 1:13.0-1ubuntu1 PackageArchitecture: amd64 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-24-generic root=UUID=deda3529-9822-4f34-9103-f54a6a63d681 ro ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.3.0-24-generic N/A linux-backports-modules-5.3.0-24-generic N/A linux-firmware1.184 Tags: focal Uname: Linux 5.3.0-24-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 11/16/2018 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 1.07.05RHZX1 dmi.board.asset.tag: Tag 12345 dmi.board.name: NH50_70_55_58_ED,EDQ dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.modalias: dmi:bvnINSYDECorp.:bvr1.07.05RHZX1:bd11/16/2018:svnHASEEComputer:pnNH50_70_55_58_ED,EDQ:pvrNotApplicable:rvnNotebook:rnNH50_70_55_58_ED,EDQ:rvrNotApplicable:cvnNotebook:ct10:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: NH50_70_55_58_ED,EDQ dmi.product.sku: Not Applicable dmi.product.version: Not Applicable dmi.sys.vendor: HASEE Computer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1855584/+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 1855584] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1855584/+attachment/5310917/+files/CRDA.txt -- 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/1855584 Title: [Hasee NH50_70_55_58_ED,EDQ] pulseaudio: sometimes generate eternal white noise even reboot to Windows OS Status in alsa-driver package in Ubuntu: New Status in linux package in Ubuntu: Incomplete Status in pulseaudio package in Ubuntu: New Bug description: This problem seems begin from ubuntu 19.04. Sometimes after login, headphone outputs white noise only, speaker does not work. Nothing can play music with the noise. The noise is impossible to stop except POWEROFF the PC. Rebooting cannot stop it, the noise keeps even reboot into Windows OS. In Windows OS, headphone still white noise, after unplugging headphone, the speaker does not work, too. It works fine in Windows OS. If I remove pulseaudio, only use ALSA. It also works stable. (But now... firefox do not support ALSA, chromium-snap do not support ALSA too...) It seems pulseaudio killed the sound card... The problem appears randomly, I do not know how to reproduce. sorry... ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.0-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-0ubuntu13 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: aya5434 F pulseaudio /dev/snd/controlC0: aya5434 F pulseaudio Date: Sun Dec 8 19:51:02 2019 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/16/2018 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 1.07.05RHZX1 dmi.board.asset.tag: Tag 12345 dmi.board.name: NH50_70_55_58_ED,EDQ dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.modalias: dmi:bvnINSYDECorp.:bvr1.07.05RHZX1:bd11/16/2018:svnHASEEComputer:pnNH50_70_55_58_ED,EDQ:pvrNotApplicable:rvnNotebook:rnNH50_70_55_58_ED,EDQ:rvrNotApplicable:cvnNotebook:ct10:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: NH50_70_55_58_ED,EDQ dmi.product.sku: Not Applicable dmi.product.version: Not Applicable dmi.sys.vendor: HASEE Computer --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu13 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: aya1796 F pulseaudio /dev/snd/controlC1: aya1796 F pulseaudio DistroRelease: Ubuntu 20.04 MachineType: HASEE Computer NH50_70_55_58_ED,EDQ NonfreeKernelModules: nvidia_modeset nvidia Package: pulseaudio 1:13.0-1ubuntu1 PackageArchitecture: amd64 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-24-generic root=UUID=deda3529-9822-4f34-9103-f54a6a63d681 ro ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.3.0-24-generic N/A linux-backports-modules-5.3.0-24-generic N/A linux-firmware1.184 Tags: focal Uname: Linux 5.3.0-24-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 11/16/2018 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 1.07.05RHZX1 dmi.board.asset.tag: Tag 12345 dmi.board.name: NH50_70_55_58_ED,EDQ dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.modalias: dmi:bvnINSYDECorp.:bvr1.07.05RHZX1:bd11/16/2018:svnHASEEComputer:pnNH50_70_55_58_ED,EDQ:pvrNotApplicable:rvnNotebook:rnNH50_70_55_58_ED,EDQ:rvrNotApplicable:cvnNotebook:ct10:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: NH50_70_55_58_ED,EDQ dmi.product.sku: Not Applicable dmi.product.version: Not Applicable dmi.sys.vendor: HASEE Computer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1855584/+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 1855584] Re: [Hasee NH50_70_55_58_ED, EDQ] pulseaudio: sometimes generate eternal white noise even reboot to Windows OS
apport information ** Tags added: apport-collected ** Description changed: This problem seems begin from ubuntu 19.04. Sometimes after login, headphone outputs white noise only, speaker does not work. Nothing can play music with the noise. The noise is impossible to stop except POWEROFF the PC. Rebooting cannot stop it, the noise keeps even reboot into Windows OS. In Windows OS, headphone still white noise, after unplugging headphone, the speaker does not work, too. It works fine in Windows OS. If I remove pulseaudio, only use ALSA. It also works stable. (But now... firefox do not support ALSA, chromium-snap do not support ALSA too...) It seems pulseaudio killed the sound card... The problem appears randomly, I do not know how to reproduce. sorry... ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.0-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-0ubuntu13 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: aya5434 F pulseaudio /dev/snd/controlC0: aya5434 F pulseaudio Date: Sun Dec 8 19:51:02 2019 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/16/2018 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 1.07.05RHZX1 dmi.board.asset.tag: Tag 12345 dmi.board.name: NH50_70_55_58_ED,EDQ dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.modalias: dmi:bvnINSYDECorp.:bvr1.07.05RHZX1:bd11/16/2018:svnHASEEComputer:pnNH50_70_55_58_ED,EDQ:pvrNotApplicable:rvnNotebook:rnNH50_70_55_58_ED,EDQ:rvrNotApplicable:cvnNotebook:ct10:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: NH50_70_55_58_ED,EDQ dmi.product.sku: Not Applicable dmi.product.version: Not Applicable dmi.sys.vendor: HASEE Computer + --- + ProblemType: Bug + ApportVersion: 2.20.11-0ubuntu13 + Architecture: amd64 + AudioDevicesInUse: + USERPID ACCESS COMMAND + /dev/snd/controlC0: aya1796 F pulseaudio + /dev/snd/controlC1: aya1796 F pulseaudio + DistroRelease: Ubuntu 20.04 + MachineType: HASEE Computer NH50_70_55_58_ED,EDQ + NonfreeKernelModules: nvidia_modeset nvidia + Package: pulseaudio 1:13.0-1ubuntu1 + PackageArchitecture: amd64 + ProcFB: 0 i915drmfb + ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-24-generic root=UUID=deda3529-9822-4f34-9103-f54a6a63d681 ro + ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 + PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. + RelatedPackageVersions: + linux-restricted-modules-5.3.0-24-generic N/A + linux-backports-modules-5.3.0-24-generic N/A + linux-firmware1.184 + Tags: focal + Uname: Linux 5.3.0-24-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: + + _MarkForUpload: True + dmi.bios.date: 11/16/2018 + dmi.bios.vendor: INSYDE Corp. + dmi.bios.version: 1.07.05RHZX1 + dmi.board.asset.tag: Tag 12345 + dmi.board.name: NH50_70_55_58_ED,EDQ + dmi.board.vendor: Notebook + dmi.board.version: Not Applicable + dmi.chassis.asset.tag: No Asset Tag + dmi.chassis.type: 10 + dmi.chassis.vendor: Notebook + dmi.chassis.version: N/A + dmi.modalias: dmi:bvnINSYDECorp.:bvr1.07.05RHZX1:bd11/16/2018:svnHASEEComputer:pnNH50_70_55_58_ED,EDQ:pvrNotApplicable:rvnNotebook:rnNH50_70_55_58_ED,EDQ:rvrNotApplicable:cvnNotebook:ct10:cvrN/A: + dmi.product.family: Not Applicable + dmi.product.name: NH50_70_55_58_ED,EDQ + dmi.product.sku: Not Applicable + dmi.product.version: Not Applicable + dmi.sys.vendor: HASEE Computer ** Attachment added: "AlsaInfo.txt" https://bugs.launchpad.net/bugs/1855584/+attachment/5310916/+files/AlsaInfo.txt -- 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/1855584 Title: [Hasee NH50_70_55_58_ED,EDQ] pulseaudio: sometimes generate eternal white noise even reboot to Windows OS Status in alsa-driver package in Ubuntu: New Status in linux package in Ubuntu: Incomplete Status in pulseaudio package in Ubuntu: New Bug description: This problem seems begin from ubuntu 19.04. Sometimes after login, headphone outputs white noise only, speaker does not work. Nothing can play music with the noise. The noise is impossible to stop except POWEROFF the PC. Rebooting cannot stop it, the noise keeps even reboot into Windows OS. In Windows
[Desktop-packages] [Bug 1854877] Re: External HDMI display not working with Intel GPU, only works with Nvidia
** Changed in: xorg-server (Ubuntu) Status: Incomplete => New ** Summary changed: - External HDMI display not working with Intel GPU, only works with Nvidia + [Asus UX580] External HDMI display not working with Intel GPU, only works with Nvidia -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1854877 Title: [Asus UX580] External HDMI display not working with Intel GPU, only works with Nvidia Status in xorg-server package in Ubuntu: New Bug description: I have Asus UX580 laptop with intel and nvidia 1050 video cards under Ubuntu 19.10. For some reason dual monitor setup with external monitor via HDMI only works if I switch to Nvidia only. If I select Intel GPU or "on-demand" in Nvidia server settings HDMI out is not working at all - xrandr shows HDMI out disconnected. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 19.10 InstallationDate: Installed on 2019-10-29 (38 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) NonfreeKernelModules: nvidia_modeset nvidia Package: gnome-shell 3.34.1+git20191024-1ubuntu1~19.10.1 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 5.3.0-23.25-generic 5.3.7 RelatedPackageVersions: mutter-common 3.34.1+git20191107-1ubuntu1~19.10.1 Tags: eoan Uname: Linux 5.3.0-23-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1854877/+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 1855613] Re: Xorg froze and put the system in a soft-lock after I turned off Wi-Fi and turned it back on.
** Package changed: xorg (Ubuntu) => ubuntu ** Changed in: ubuntu Status: New => Incomplete -- 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/1855613 Title: Xorg froze and put the system in a soft-lock after I turned off Wi-Fi and turned it back on. Status in Ubuntu: Incomplete Bug description: This issue occurred at around 1:51 PM, EDT. When I was shutting down Wi-Fi but then immediately turning it back on while I had terminal open, the machine froze into a soft-lock, and I was forced to open a tty session and restart the computer. Description: Ubuntu 18.04.3 LTS Release: 18.04 xorg: Installed: 1:7.7+19ubuntu7.1 Candidate: 1:7.7+19ubuntu7.1 Version table: *** 1:7.7+19ubuntu7.1 500 500 http://us.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 100 /var/lib/dpkg/status 1:7.7+19ubuntu7 500 500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 5.0.0-37.40~18.04.1-generic 5.0.21 Uname: Linux 5.0.0-37-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Dec 8 14:17:56 2019 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Caicos [Radeon HD 6450/7450/8450 / R5 230 OEM] [1002:6779] (prog-if 00 [VGA controller]) Subsystem: XFX Pine Group Inc. Caicos [Radeon HD 6450/7450/8450 / R5 230 OEM] [1682:3207] MachineType: Gateway DX4860 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-37-generic root=UUID=3c16de60-443d-4ba1-baee-e0f3153202c0 ro quiet splash vt.handoff=1 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/01/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P02-A1 dmi.board.name: IPISB-VR dmi.board.vendor: Gateway dmi.board.version: 1.01 dmi.chassis.type: 3 dmi.chassis.vendor: Gateway dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP02-A1:bd08/01/2011:svnGateway:pnDX4860:pvr:rvnGateway:rnIPISB-VR:rvr1.01:cvnGateway:ct3:cvr: dmi.product.family: Gateway Desktop dmi.product.name: DX4860 dmi.sys.vendor: Gateway version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97-1ubuntu1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.8-0ubuntu0~18.04.3 version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.8-0ubuntu0~18.04.3 version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1855613/+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 1855608] Re: Dell XPS 13 7390 screen corruption in 18.04 LTS, 19.04 and 19.10 on Intel Comet Lake
** Summary changed: - Dell XPS 13 7390 screen corruption in 18.04 LTS, 19.04 and 19.10 + Dell XPS 13 7390 screen corruption in 18.04 LTS, 19.04 and 19.10 on Intel Comet Lake ** Package changed: xorg (Ubuntu) => linux (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/1855608 Title: Dell XPS 13 7390 screen corruption in 18.04 LTS, 19.04 and 19.10 on Intel Comet Lake Status in linux package in Ubuntu: New Bug description: I just received a new Dell XPS 13 7390 laptop. With factory preinstalled Ubuntu Linux 18.04 LTS and the Dell OEM kernel, graphics was severely distorted. The display would constantly flicker with areas of the display staying black or showing patterns of square color blocks. Booting in recovery mode worked, though and I was able to install all updates for preinstalled 18.04 LTS with the OEM kernel. Problems in non-recovery mode persisted after installing all updates. I then updated to Ubuntu 19.04 and changed to "generic" linux kernel image without success: Problem persisted, only recovery mode was usable. I updated once more to 19.10 again without any success. From the perhaps related bug #1849947 I tried latest drm-tip kernel from https://kernel.ubuntu.com/~kernel-ppa/mainline/ drm-tip kernel solves the issue for first boot, but after resuming from suspend, the same issues display issues occur. Kernel images I tried: - linux-image-4.15.0-1065-oem - on Ubuntu 18.04 LTS, corrupted graphics output without "nomodeset" - linux-image-5.0.0-37-generic - on Ubuntu 19.04, corrupted graphics output without "nomodeset" - linux-image-5.3.0-24-generic - on Ubuntu 19.10, corrupted graphics output without "nomodeset" - linux-image-unsigned-5.4.0-994-generic - on Ubuntu 19.10, corrupted graphics output after resuming from suspend ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 Uname: Linux 5.4.0-994-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Dec 8 18:51:15 2019 DistUpgraded: 2019-12-07 22:36:44,841 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process “./xorg_fix_proprietary.py” (No such file or directory) (8)) DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-bionic-amd64-20180608-47+beaver-three-eyed-raven+X92 DistroCodename: eoan DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Device [8086:9b41] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:0962] InstallationDate: Installed on 2019-11-25 (13 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20180608-09:38 MachineType: Dell Inc. XPS 13 7390 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-994-generic root=UUID=45745b59-5aff-4246-94d2-34fe9ae5012f ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to eoan on 2019-12-07 (0 days ago) dmi.bios.date: 11/08/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.3.1 dmi.board.name: 0G2D0W dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.3.1:bd11/08/2019:svnDellInc.:pnXPS137390:pvr:rvnDellInc.:rn0G2D0W:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 7390 dmi.product.sku: 0962 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.99-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.1-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-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/linux/+bug/1855608/+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 1855613] Re: Xorg froze and put the system in a soft-lock after I turned off Wi-Fi and turned it back on.
Next time the problem happens, please force a reboot and then run: journalctl -b-1 > prevboot.txt and send us the file 'prevboot.txt'. -- 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/1855613 Title: Xorg froze and put the system in a soft-lock after I turned off Wi-Fi and turned it back on. Status in xorg package in Ubuntu: New Bug description: This issue occurred at around 1:51 PM, EDT. When I was shutting down Wi-Fi but then immediately turning it back on while I had terminal open, the machine froze into a soft-lock, and I was forced to open a tty session and restart the computer. Description: Ubuntu 18.04.3 LTS Release: 18.04 xorg: Installed: 1:7.7+19ubuntu7.1 Candidate: 1:7.7+19ubuntu7.1 Version table: *** 1:7.7+19ubuntu7.1 500 500 http://us.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 100 /var/lib/dpkg/status 1:7.7+19ubuntu7 500 500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 5.0.0-37.40~18.04.1-generic 5.0.21 Uname: Linux 5.0.0-37-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Dec 8 14:17:56 2019 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Caicos [Radeon HD 6450/7450/8450 / R5 230 OEM] [1002:6779] (prog-if 00 [VGA controller]) Subsystem: XFX Pine Group Inc. Caicos [Radeon HD 6450/7450/8450 / R5 230 OEM] [1682:3207] MachineType: Gateway DX4860 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-37-generic root=UUID=3c16de60-443d-4ba1-baee-e0f3153202c0 ro quiet splash vt.handoff=1 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/01/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P02-A1 dmi.board.name: IPISB-VR dmi.board.vendor: Gateway dmi.board.version: 1.01 dmi.chassis.type: 3 dmi.chassis.vendor: Gateway dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP02-A1:bd08/01/2011:svnGateway:pnDX4860:pvr:rvnGateway:rnIPISB-VR:rvr1.01:cvnGateway:ct3:cvr: dmi.product.family: Gateway Desktop dmi.product.name: DX4860 dmi.sys.vendor: Gateway version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97-1ubuntu1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.8-0ubuntu0~18.04.3 version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.8-0ubuntu0~18.04.3 version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1855613/+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 1853094] Re: Screen tearing in xorg gnome session on Latitude 7480 with WD19TB Thunderbolt dock
** Attachment added: "lspci -k" https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1853094/+attachment/5310908/+files/lspcik.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1853094 Title: Screen tearing in xorg gnome session on Latitude 7480 with WD19TB Thunderbolt dock Status in xorg-server package in Ubuntu: Incomplete Bug description: I have the WD19TB Thunderbolt dock connected to a Dell Latitude 7480 laptop with two external displays. The laptop itself is closed (internal display is not used). In a gnome xorg session, there is severe tearing on parts of the screen when dragging windows or scrolling content. Under a wayland session there is no screen tearing, but I have keyboard key repetition problems which make this mostly unusable day- to-day (https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1849405). I can supply short phone videos of tearing occurring on the screens if required. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: mutter 3.28.4-0ubuntu18.04.2 ProcVersionSignature: Ubuntu 5.0.0-36.39~18.04.1-generic 5.0.21 Uname: Linux 5.0.0-36-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 CurrentDesktop: GNOME Date: Tue Nov 19 14:02:09 2019 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_AU.UTF-8 SHELL=/bin/bash SourcePackage: mutter UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1853094/+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 1855521] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window: apport-collect 1855521 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1855521 Title: [Dell Inspiron 5490] Internal microphone not detected Status in alsa-driver package in Ubuntu: New Status in linux package in Ubuntu: Incomplete Bug description: No input device available for selection. Output of dmesg | grep snd: [2.247186] snd_hda_intel :00:1f.3: enabling device ( -> 0002) [2.372911] snd_hda_intel :00:1f.3: bound :00:02.0 (ops i915_audio_component_bind_ops [i915]) [2.532497] snd_hda_codec_realtek hdaudioC0D0: autoconfig for ALC3204: line_outs=1 (0x14/0x0/0x0/0x0/0x0) type:speaker [2.532499] snd_hda_codec_realtek hdaudioC0D0:speaker_outs=0 (0x0/0x0/0x0/0x0/0x0) [2.532500] snd_hda_codec_realtek hdaudioC0D0:hp_outs=1 (0x21/0x0/0x0/0x0/0x0) [2.532501] snd_hda_codec_realtek hdaudioC0D0:mono: mono_out=0x0 [2.532502] snd_hda_codec_realtek hdaudioC0D0:inputs: [2.532503] snd_hda_codec_realtek hdaudioC0D0: Headphone Mic=0x1a [2.532504] snd_hda_codec_realtek hdaudioC0D0: Headset Mic=0x19 --- Alsamixer checked for mutes, all OK. Internal mic not present. Cannot remap using hdajackretask due to error tee: /sys/class/sound/hwC0D0/reconfig: Device or resource busy. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 Uname: Linux 5.3.0-24-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: tom3754 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sat Dec 7 08:10:21 2019 InstallationDate: Installed on 2019-12-06 (0 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Title: PCI/internal sound card not detected UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/30/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.3.0 dmi.board.name: 0012KY dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.3.0:bd10/30/2019:svnDellInc.:pnInspiron5490:pvr:rvnDellInc.:rn0012KY:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Inspiron dmi.product.name: Inspiron 5490 dmi.product.sku: 0955 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1855521/+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 1854877] Re: External HDMI display not working with Intel GPU, only works with Nvidia
attached xorg.log. Thanks for the explanation. However I do think that since both Windows 10 and Ubuntu use same Nvidia driver, and Windows can handle HDMI with Intel GPU only, then Ubuntu should be able to do the same. ** Attachment added: "xorg.log" https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1854877/+attachment/5310911/+files/Xorg.0.log -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1854877 Title: External HDMI display not working with Intel GPU, only works with Nvidia Status in xorg-server package in Ubuntu: Incomplete Bug description: I have Asus UX580 laptop with intel and nvidia 1050 video cards under Ubuntu 19.10. For some reason dual monitor setup with external monitor via HDMI only works if I switch to Nvidia only. If I select Intel GPU or "on-demand" in Nvidia server settings HDMI out is not working at all - xrandr shows HDMI out disconnected. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 19.10 InstallationDate: Installed on 2019-10-29 (38 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) NonfreeKernelModules: nvidia_modeset nvidia Package: gnome-shell 3.34.1+git20191024-1ubuntu1~19.10.1 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 5.3.0-23.25-generic 5.3.7 RelatedPackageVersions: mutter-common 3.34.1+git20191107-1ubuntu1~19.10.1 Tags: eoan Uname: Linux 5.3.0-23-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1854877/+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 1853094] Re: Screen tearing in xorg gnome session on Latitude 7480 with WD19TB Thunderbolt dock
** Attachment added: "Xorg.0.log" https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1853094/+attachment/5310910/+files/Xorg.0.log -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1853094 Title: Screen tearing in xorg gnome session on Latitude 7480 with WD19TB Thunderbolt dock Status in xorg-server package in Ubuntu: Incomplete Bug description: I have the WD19TB Thunderbolt dock connected to a Dell Latitude 7480 laptop with two external displays. The laptop itself is closed (internal display is not used). In a gnome xorg session, there is severe tearing on parts of the screen when dragging windows or scrolling content. Under a wayland session there is no screen tearing, but I have keyboard key repetition problems which make this mostly unusable day- to-day (https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1849405). I can supply short phone videos of tearing occurring on the screens if required. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: mutter 3.28.4-0ubuntu18.04.2 ProcVersionSignature: Ubuntu 5.0.0-36.39~18.04.1-generic 5.0.21 Uname: Linux 5.0.0-36-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 CurrentDesktop: GNOME Date: Tue Nov 19 14:02:09 2019 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_AU.UTF-8 SHELL=/bin/bash SourcePackage: mutter UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1853094/+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 1855584] Re: [Hasee NH50_70_55_58_ED, EDQ] pulseaudio: sometimes generate eternal white noise even reboot to Windows OS
Also, please try a newer kernel like: https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.4.2/ -- 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/1855584 Title: [Hasee NH50_70_55_58_ED,EDQ] pulseaudio: sometimes generate eternal white noise even reboot to Windows OS Status in alsa-driver package in Ubuntu: New Status in linux package in Ubuntu: Incomplete Status in pulseaudio package in Ubuntu: New Bug description: This problem seems begin from ubuntu 19.04. Sometimes after login, headphone outputs white noise only, speaker does not work. Nothing can play music with the noise. The noise is impossible to stop except POWEROFF the PC. Rebooting cannot stop it, the noise keeps even reboot into Windows OS. In Windows OS, headphone still white noise, after unplugging headphone, the speaker does not work, too. It works fine in Windows OS. If I remove pulseaudio, only use ALSA. It also works stable. (But now... firefox do not support ALSA, chromium-snap do not support ALSA too...) It seems pulseaudio killed the sound card... The problem appears randomly, I do not know how to reproduce. sorry... ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.0-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-0ubuntu13 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: aya5434 F pulseaudio /dev/snd/controlC0: aya5434 F pulseaudio Date: Sun Dec 8 19:51:02 2019 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/16/2018 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 1.07.05RHZX1 dmi.board.asset.tag: Tag 12345 dmi.board.name: NH50_70_55_58_ED,EDQ dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.modalias: dmi:bvnINSYDECorp.:bvr1.07.05RHZX1:bd11/16/2018:svnHASEEComputer:pnNH50_70_55_58_ED,EDQ:pvrNotApplicable:rvnNotebook:rnNH50_70_55_58_ED,EDQ:rvrNotApplicable:cvnNotebook:ct10:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: NH50_70_55_58_ED,EDQ dmi.product.sku: Not Applicable dmi.product.version: Not Applicable dmi.sys.vendor: HASEE Computer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1855584/+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 1855584] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window: apport-collect 1855584 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1855584 Title: [Hasee NH50_70_55_58_ED,EDQ] pulseaudio: sometimes generate eternal white noise even reboot to Windows OS Status in alsa-driver package in Ubuntu: New Status in linux package in Ubuntu: Incomplete Status in pulseaudio package in Ubuntu: New Bug description: This problem seems begin from ubuntu 19.04. Sometimes after login, headphone outputs white noise only, speaker does not work. Nothing can play music with the noise. The noise is impossible to stop except POWEROFF the PC. Rebooting cannot stop it, the noise keeps even reboot into Windows OS. In Windows OS, headphone still white noise, after unplugging headphone, the speaker does not work, too. It works fine in Windows OS. If I remove pulseaudio, only use ALSA. It also works stable. (But now... firefox do not support ALSA, chromium-snap do not support ALSA too...) It seems pulseaudio killed the sound card... The problem appears randomly, I do not know how to reproduce. sorry... ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.0-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-0ubuntu13 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: aya5434 F pulseaudio /dev/snd/controlC0: aya5434 F pulseaudio Date: Sun Dec 8 19:51:02 2019 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/16/2018 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 1.07.05RHZX1 dmi.board.asset.tag: Tag 12345 dmi.board.name: NH50_70_55_58_ED,EDQ dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.modalias: dmi:bvnINSYDECorp.:bvr1.07.05RHZX1:bd11/16/2018:svnHASEEComputer:pnNH50_70_55_58_ED,EDQ:pvrNotApplicable:rvnNotebook:rnNH50_70_55_58_ED,EDQ:rvrNotApplicable:cvnNotebook:ct10:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: NH50_70_55_58_ED,EDQ dmi.product.sku: Not Applicable dmi.product.version: Not Applicable dmi.sys.vendor: HASEE Computer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1855584/+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 1855584] Re: [Hasee NH50_70_55_58_ED, EDQ] pulseaudio: sometimes generate eternal white noise even reboot to Windows OS
You say the problem began around 19.04 and you are now running 20.04. Is that correct or a typo? ** Summary changed: - pulseaudio: sometimes generate eternal white noise even reboot to Windows OS + [Hasee NH50_70_55_58_ED,EDQ] pulseaudio: sometimes generate eternal white noise even reboot to Windows OS ** Also affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Also affects: linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1855584 Title: [Hasee NH50_70_55_58_ED,EDQ] pulseaudio: sometimes generate eternal white noise even reboot to Windows OS Status in alsa-driver package in Ubuntu: New Status in linux package in Ubuntu: Incomplete Status in pulseaudio package in Ubuntu: New Bug description: This problem seems begin from ubuntu 19.04. Sometimes after login, headphone outputs white noise only, speaker does not work. Nothing can play music with the noise. The noise is impossible to stop except POWEROFF the PC. Rebooting cannot stop it, the noise keeps even reboot into Windows OS. In Windows OS, headphone still white noise, after unplugging headphone, the speaker does not work, too. It works fine in Windows OS. If I remove pulseaudio, only use ALSA. It also works stable. (But now... firefox do not support ALSA, chromium-snap do not support ALSA too...) It seems pulseaudio killed the sound card... The problem appears randomly, I do not know how to reproduce. sorry... ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.0-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-0ubuntu13 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: aya5434 F pulseaudio /dev/snd/controlC0: aya5434 F pulseaudio Date: Sun Dec 8 19:51:02 2019 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/16/2018 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 1.07.05RHZX1 dmi.board.asset.tag: Tag 12345 dmi.board.name: NH50_70_55_58_ED,EDQ dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.modalias: dmi:bvnINSYDECorp.:bvr1.07.05RHZX1:bd11/16/2018:svnHASEEComputer:pnNH50_70_55_58_ED,EDQ:pvrNotApplicable:rvnNotebook:rnNH50_70_55_58_ED,EDQ:rvrNotApplicable:cvnNotebook:ct10:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: NH50_70_55_58_ED,EDQ dmi.product.sku: Not Applicable dmi.product.version: Not Applicable dmi.sys.vendor: HASEE Computer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1855584/+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 1855570] Re: xdg-desktop-por: Could not get window list: Timeout was reached
Thank you for taking the time to report this bug and helping to make Ubuntu better. Please execute the following command only once, as it will automatically gather debugging information, in a terminal: apport-collect 1855570 When reporting bugs in the future please use apport by using 'ubuntu- bug' and the name of the package affected. You can learn more about this functionality at https://wiki.ubuntu.com/ReportingBugs. ** Tags added: focal ** Summary changed: - xdg-desktop-por: Could not get window list: Timeout was reached + No Gnome is showing up in Ubuntu 20.04 ** Package changed: xorg (Ubuntu) => gnome-shell (Ubuntu) ** Changed in: gnome-shell (Ubuntu) Status: New => Incomplete ** Summary changed: - No Gnome is showing up in Ubuntu 20.04 + [nouveau][conroe] No Gnome is showing up in Ubuntu 20.04 ** Tags added: nouveau -- 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/1855570 Title: [nouveau][conroe] No Gnome is showing up in Ubuntu 20.04 Status in gnome-shell package in Ubuntu: Incomplete Bug description: Just freshly installed Ubuntu 20.04 on a bare metal Desktop disk partition (for testing purpose only): While booting there is no Gnome showing up. Checking syslog for error's there are these messages ... Dec 8 07:51:43 deblnxsrv100 xdg-desktop-por[1287]: Failed to get application states: GDBus.Error:org.freedesktop.portal.Error.Failed: Could not get window list: Timeout was reached Dec 8 07:51:43 deblnxsrv100 at-spi-bus-launcher[1245]: X connection to :0 broken (explicit kill or server shutdown). Dec 8 07:51:44 deblnxsrv100 gsd-wacom[1522]: gsd-wacom: Fatal IO error 11 (Resource temporarily unavailable) on X server :0. Dec 8 07:51:44 deblnxsrv100 gsd-xsettings[1538]: gsd-xsettings: Fatal IO error 11 (Resource temporarily unavailable) on X server :0. Dec 8 07:51:44 deblnxsrv100 systemd[]: gsd-xsettings.service: Main process exited, code=exited, status=1/FAILURE Dec 8 07:51:44 deblnxsrv100 systemd[]: gsd-xsettings.service: Failed with result 'exit-code'. Dec 8 07:51:44 deblnxsrv100 systemd[]: gsd-xsettings.service: Triggering OnFailure= dependencies. Dec 8 07:51:44 deblnxsrv100 systemd[]: Stopped target GNOME XSettings. Dec 8 07:51:44 deblnxsrv100 systemd[]: Started GNOME Session Failed lockdown screen (user). Dec 8 07:51:44 deblnxsrv100 systemd[]: Reached target GNOME Session Failed. Dec 8 07:51:44 deblnxsrv100 update-notifier[1815]: update-notifier: Fatal IO error 11 (Resource temporarily unavailable) on X server :0. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1855570/+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 1855583] Re: blinking kubuntu logo
Xorg appears to be running so reassigning to KDE. ** Package changed: xorg (Ubuntu) => kubuntu-meta (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/1855583 Title: blinking kubuntu logo Status in kubuntu-meta package in Ubuntu: New Bug description: Not able to boot ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 5.0.0-37.40~18.04.1-generic 5.0.21 Uname: Linux 5.0.0-37-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: KDE Date: Sun Dec 8 17:23:00 2019 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: I just need to know a workaround GraphicsCard: Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a06] (rev 0b) (prog-if 00 [VGA controller]) Subsystem: Dell Haswell-ULT Integrated Graphics Controller [1028:0651] InstallationDate: Installed on 2019-11-27 (10 days ago) InstallationMedia: Kubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) MachineType: Dell Inc. Inspiron 3542 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-37-generic root=UUID=e11edfe1-8c7e-4e23-bdd2-9f56d67cda03 ro quiet splash SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/13/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: A12 dmi.board.name: 0FKWR5 dmi.board.vendor: Dell Inc. dmi.board.version: A12 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvrA12:bd05/13/2016:svnDellInc.:pnInspiron3542:pvrNotSpecified:rvnDellInc.:rn0FKWR5:rvrA12:cvnDellInc.:ct8:cvrNotSpecified: dmi.product.name: Inspiron 3542 dmi.product.sku: 0651 dmi.product.version: Not Specified dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97-1ubuntu1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.8-0ubuntu0~18.04.3 version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.8-0ubuntu0~18.04.3 version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kubuntu-meta/+bug/1855583/+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 1855565] Re: After resuming from lockscreen and/or suspend, taskbar, dock, and screen fonts are messed up
This looks related to your Nvidia driver version 440, which is not from Ubuntu and not supported by us... Please try downgrading your Nvidia driver to a supported version like 435. ** Package changed: xorg (Ubuntu) => ubuntu ** Changed in: ubuntu Status: New => Incomplete -- 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/1855565 Title: After resuming from lockscreen and/or suspend, taskbar, dock, and screen fonts are messed up Status in Ubuntu: Incomplete Bug description: After waking from suspend, the taskbar fonts are unreadable, as are the fonts used on the dock and on the icons on the desktop. The only cure I can find is to reboot. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.3.0-22.24+system76~1573659475~19.10~26b2022~dev-generic 5.3.7 Uname: Linux 5.3.0-22-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair 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.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 440.31 Sun Oct 27 02:19:35 UTC 2019 GCC version: gcc version 9.2.1 20191008 (Ubuntu 9.2.1-9ubuntu2) .tmp.unity_support_test.0: ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CompizPlugins: [core,composite,opengl,decor,grid,move,compiztoolbox,gnomecompat,imgpng,resize,imgjpeg,regex,vpswitch,unitymtgrabhandles,snap,place,mousepoll,session,screenshot,resizeinfo,thumbnail,wall,animation,workarounds,expo,ezoom,staticswitcher,fade,scale,unityshell,dbus] CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Dec 7 17:26:22 2019 DistUpgraded: 2019-11-14 14:45:51,508 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: eoan DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GM204M [GeForce GTX 980M] [10de:1617] (rev a1) (prog-if 00 [VGA controller]) Subsystem: CLEVO/KAPOK Computer GM204M [GeForce GTX 980M] [1558:7703] InstallationDate: Installed on 2017-11-01 (766 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) MachineType: System76, Inc. Serval WS ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-22-generic root=UUID=fbf9e88e-c136-41b5-91a1-0848d0d8427a ro quiet splash snd_hda_intel.probe_mask=1 vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to eoan on 2019-11-14 (23 days ago) dmi.bios.date: 07/11/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.05.10RSA1 dmi.board.asset.tag: Tag 12345 dmi.board.name: Serval WS dmi.board.vendor: System76, Inc. dmi.board.version: serw9 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: System76, Inc. dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.05.10RSA1:bd07/11/2016:svnSystem76,Inc.:pnServalWS:pvrserw9:rvnSystem76,Inc.:rnServalWS:rvrserw9:cvnSystem76,Inc.:ct10:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: Serval WS dmi.product.sku: Not Applicable dmi.product.version: serw9 dmi.sys.vendor: System76, Inc. version.compiz: compiz 1:0.9.14.0+19.10.20190918-0ubuntu1 version.libdrm2: libdrm2 2.4.99-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.1-1ubuntu1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-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/+bug/1855565/+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 1849249] Re: gnome-shell crashed with SIGABRT: mutter:ERROR:../src/core/window.c:4841:set_workspace_state: assertion failed: (workspace == NULL)
I updated the description to note that the text being searched for is not found in the document (which is the case of course for an empty document). ** Description changed: https://errors.ubuntu.com/problem/8317377ffa8b8148baa481d490fd876111eb3c4b gnome-shell crashes with this bug every time that: * I am editing a file in geany * I open the Find window (CTRL-F) and it opens on another monitor - * I type in some text in the find window and press ENTER (or click the Next button) + * I type in some un-findable text in the find window and press ENTER (or click the Next button) + + The system beeps to indicate that the text isn't found, but then + crashes. Note especially that the find window must be on the other monitor - if it's on the same monitor as geany, gnome-shell doesn't crash. (Note: I originally thought that if I moved the find window to the other window and then searched, gnome-shell crashed, but I think what happens is a) I open the window, b) I move it, search for something, and it works, c) I close it and re-open it - it then opens on the other monitor and searching will crash gnome-shell.) gnome-shell restarts, but the crash causes data loss, as most of the running applications don't reappear when it restarts. In case it's relevant, I have a laptop screen set at 2048x1152 and an external monitor configured to be above it at 2560x1440. ProblemType: Crash DistroRelease: Ubuntu 19.10 Package: gnome-shell 3.34.1-1ubuntu1 Uname: Linux 5.4.0-050400rc4-generic x86_64 ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Oct 22 10:37:36 2019 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell ExecutableTimestamp: 1570619894 InstallationDate: Installed on 2019-07-01 (112 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190606) ProcCmdline: /usr/bin/gnome-shell ProcCwd: /home/rocko ProcEnviron: LANG=en_AU.UTF-8 LANGUAGE=en_AU:en PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= RelatedPackageVersions: mutter-common 3.34.1-1ubuntu1 Signal: 6 SourcePackage: gnome-shell StacktraceTop: () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_assertion_message_expr () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 () at /lib/x86_64-linux-gnu/libmutter-5.so.0 () at /lib/x86_64-linux-gnu/libmutter-5.so.0 () at /lib/x86_64-linux-gnu/libmutter-5.so.0 Title: gnome-shell crashed with SIGABRT UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: sudo separator: -- 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/1849249 Title: gnome-shell crashed with SIGABRT: mutter:ERROR:../src/core/window.c:4841:set_workspace_state: assertion failed: (workspace == NULL) Status in gnome-shell package in Ubuntu: Confirmed Bug description: https://errors.ubuntu.com/problem/8317377ffa8b8148baa481d490fd876111eb3c4b gnome-shell crashes with this bug every time that: * I am editing a file in geany * I open the Find window (CTRL-F) and it opens on another monitor * I type in some un-findable text in the find window and press ENTER (or click the Next button) The system beeps to indicate that the text isn't found, but then crashes. Note especially that the find window must be on the other monitor - if it's on the same monitor as geany, gnome-shell doesn't crash. (Note: I originally thought that if I moved the find window to the other window and then searched, gnome-shell crashed, but I think what happens is a) I open the window, b) I move it, search for something, and it works, c) I close it and re-open it - it then opens on the other monitor and searching will crash gnome-shell.) gnome-shell restarts, but the crash causes data loss, as most of the running applications don't reappear when it restarts. In case it's relevant, I have a laptop screen set at 2048x1152 and an external monitor configured to be above it at 2560x1440. ProblemType: Crash DistroRelease: Ubuntu 19.10 Package: gnome-shell 3.34.1-1ubuntu1 Uname: Linux 5.4.0-050400rc4-generic x86_64 ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Oct 22 10:37:36 2019 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell ExecutableTimestamp: 1570619894 InstallationDate: Installed on 2019-07-01 (112 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190606) ProcCmdline: /usr/bin/gnome-shell ProcCwd: /home/rocko ProcEnviron: LANG=en_AU.UTF-8 LANGUAGE=en_AU:en PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= RelatedPackageVersions: mutter-common 3.34.1-1ubuntu1 Signal: 6 SourcePackage: gnome-shell StacktraceTop: () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_assertion_message_expr ()
[Desktop-packages] [Bug 1855534] Re: UI irresponsive Object Clutter.Actor , has been already deallocated
Thank you for taking the time to report this bug and helping to make Ubuntu better. Please execute the following command only once, as it will automatically gather debugging information, in a terminal: apport-collect 1855534 When reporting bugs in the future please use apport by using 'ubuntu- bug' and the name of the package affected. You can learn more about this functionality at https://wiki.ubuntu.com/ReportingBugs. ** Changed in: gnome-shell (Ubuntu) Status: New => Incomplete -- 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/1855534 Title: UI irresponsive Object Clutter.Actor , has been already deallocated Status in gnome-shell package in Ubuntu: Incomplete Bug description: We are using GNOME Shell 3.30.2 and the UI become irresponsible until a reboot several times a week with the following continuously logs in journalctl. If it can help, it is used as a kiosk with chromium started fullscreen and an hdmi/usb touchscreen ( https://www.amazon.fr/gp/product/B07MRL2FWT/ref=ppx_yo_dt_b_search_asin_title?ie=UTF8=1 ) $ xinput list ⎡ Virtual core pointerid=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointer id=4[slave pointer (2)] ⎜ ↳ xwayland-touch:15 id=7[slave pointer (2)] ⎣ Virtual core keyboard id=3[master keyboard (2)] ↳ Virtual core XTEST keyboard id=5[slave keyboard (3)] ↳ xwayland-keyboard:15id=6[slave keyboard (3) Is there: - a way to fix it? - a workaround (disabling something) to avoid it déc. 06 20:10:35 myhostname gnome-shell[563]: Object Clutter.Actor (0x55cdb066c440), has been already deallocated — impossible to access it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs. déc. 06 20:10:35 myhostname gnome-shell[563]: ../../../gobject/gsignal.c:2641: instance '0x55cdb00047a0' has no handler with id '101431' déc. 06 20:10:35 myhostname gnome-shell[563]: Object Clutter.Actor (0x55cdb066c440), has been already deallocated — impossible to access it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs. déc. 06 20:10:35 myhostname org.gnome.Shell.desktop[563]: == Stack trace for context 0x55cdae05c280 == déc. 06 20:10:35 myhostname org.gnome.Shell.desktop[563]: #0 7fffba689f60 b resource:///org/gnome/shell/ui/windowManager.js:1931 (7fae0402d310 @ 114) déc. 06 20:10:35 myhostname org.gnome.Shell.desktop[563]: #1 7fffba68a030 b resource:///org/gnome/gjs/modules/_legacy.js:82 (7fae046b0b80 @ 71) déc. 06 20:10:35 myhostname org.gnome.Shell.desktop[563]: #2 7fffba68a0e0 b resource:///org/gnome/shell/ui/tweener.js:112 (7fae046d9040 @ 37) déc. 06 20:10:35 myhostname org.gnome.Shell.desktop[563]: #3 7fffba68a1a0 b resource:///org/gnome/gjs/modules/tweener/tweener.js:208 (7fae046db9d0 @ 54) déc. 06 20:10:35 myhostname org.gnome.Shell.desktop[563]: #4 7fffba68a2f0 b resource:///org/gnome/gjs/modules/tweener/tweener.js:342 (7fae046dba60 @ 1742) déc. 06 20:10:35 myhostname org.gnome.Shell.desktop[563]: #5 7fffba68a3a0 b resource:///org/gnome/gjs/modules/tweener/tweener.js:355 (7fae046dbaf0 @ 100) déc. 06 20:10:35 myhostname org.gnome.Shell.desktop[563]: #6 7fffba68a430 b resource:///org/gnome/gjs/modules/tweener/tweener.js:370 (7fae046dbb80 @ 10) déc. 06 20:10:35 myhostname org.gnome.Shell.desktop[563]: #7 7fffba68a4b0 I resource:///org/gnome/gjs/modules/signals.js:128 (7fae046c18b0 @ 386) déc. 06 20:10:35 myhostname org.gnome.Shell.desktop[563]: #8 7fffba68a560 b resource:///org/gnome/shell/ui/tweener.js:244 (7fae046d99d0 @ 159) déc. 06 20:10:35 myhostname org.gnome.Shell.desktop[563]: #9 7fffba68a630 b resource:///org/gnome/gjs/modules/_legacy.js:82 (7fae046b0b80 @ 71) déc. 06 20:10:35 myhostname org.gnome.Shell.desktop[563]: #10 7fffba68a6d0 b resource:///org/gnome/shell/ui/tweener.js:219 (7fae046d9940 @ 15) déc. 06 20:10:35 myhostname gnome-shell[563]: ../../../gobject/gsignal.c:2641: instance '0x55cdb00047a0' has no handler with id '101431' déc. 06 20:10:35 myhostname gnome-shell[563]: Object Clutter.Actor (0x55cdb066c440), has been already deallocated — impossible to access it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs. déc. 06 20:10:35 myhostname org.gnome.Shell.desktop[563]: == Stack trace for context 0x55cdae05c280 == déc. 06 20:10:35 myhostname org.gnome.Shell.desktop[563]: #0 7fffba689f60 b resource:///org/gnome/shell/ui/windowManager.js:1931 (7fae0402d310 @ 114) déc. 06 20:10:35
[Desktop-packages] [Bug 1854877] Re: External HDMI display not working with Intel GPU, only works with Nvidia
Can you please attach $HOME/.local/share/xorg/Xorg.0.log ? ** Changed in: xorg-server (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1854877 Title: External HDMI display not working with Intel GPU, only works with Nvidia Status in xorg-server package in Ubuntu: Incomplete Bug description: I have Asus UX580 laptop with intel and nvidia 1050 video cards under Ubuntu 19.10. For some reason dual monitor setup with external monitor via HDMI only works if I switch to Nvidia only. If I select Intel GPU or "on-demand" in Nvidia server settings HDMI out is not working at all - xrandr shows HDMI out disconnected. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 19.10 InstallationDate: Installed on 2019-10-29 (38 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) NonfreeKernelModules: nvidia_modeset nvidia Package: gnome-shell 3.34.1+git20191024-1ubuntu1~19.10.1 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 5.3.0-23.25-generic 5.3.7 RelatedPackageVersions: mutter-common 3.34.1+git20191107-1ubuntu1~19.10.1 Tags: eoan Uname: Linux 5.3.0-23-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1854877/+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 1854877] Re: External HDMI display not working with Intel GPU, only works with Nvidia
I'm not sure Windows is telling you the full truth there. Even if you tell it to prefer the Intel GPU it can't get around the fact that on most hybrid laptops if there's only one HDMI port then it will be physically wired to the secondary GPU, not Intel. Even if the Intel GPU was doing the work Nvidia would usually be handling the port itself. ** Summary changed: - External HDMI display not working with Intel GPU + External HDMI display not working with Intel GPU, only works with Nvidia ** Package changed: gnome-shell (Ubuntu) => xorg-server (Ubuntu) ** Changed in: xorg-server (Ubuntu) Status: Incomplete => New -- 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/1854877 Title: External HDMI display not working with Intel GPU, only works with Nvidia Status in xorg-server package in Ubuntu: Incomplete Bug description: I have Asus UX580 laptop with intel and nvidia 1050 video cards under Ubuntu 19.10. For some reason dual monitor setup with external monitor via HDMI only works if I switch to Nvidia only. If I select Intel GPU or "on-demand" in Nvidia server settings HDMI out is not working at all - xrandr shows HDMI out disconnected. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 19.10 InstallationDate: Installed on 2019-10-29 (38 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) NonfreeKernelModules: nvidia_modeset nvidia Package: gnome-shell 3.34.1+git20191024-1ubuntu1~19.10.1 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 5.3.0-23.25-generic 5.3.7 RelatedPackageVersions: mutter-common 3.34.1+git20191107-1ubuntu1~19.10.1 Tags: eoan Uname: Linux 5.3.0-23-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1854877/+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 1855402] Re: [TGL] mesa support
** Description changed: Description: this feature tracks the updates of mesa 3d for TGL support. We will update the commitid list as necessary - Target Release: 20.10 + Target Release: 20.04 Target version: TBD ** Tags removed: intel-upkg-20.10 ** Tags added: intel-upkg-20.04 -- 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/1855402 Title: [TGL] mesa support Status in intel: New Status in mesa package in Ubuntu: New Bug description: Description: this feature tracks the updates of mesa 3d for TGL support. We will update the commitid list as necessary Target Release: 20.04 Target version: TBD To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1855402/+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 1855521] Re: [Dell Inspiron 5490] Internal microphone not detected
** Summary changed: - Internal microphone not detected + [Dell Inspiron 5490] Internal microphone not detected ** Also affects: linux (Ubuntu) Importance: Undecided Status: New -- 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/1855521 Title: [Dell Inspiron 5490] Internal microphone not detected Status in alsa-driver package in Ubuntu: New Status in linux package in Ubuntu: New Bug description: No input device available for selection. Output of dmesg | grep snd: [2.247186] snd_hda_intel :00:1f.3: enabling device ( -> 0002) [2.372911] snd_hda_intel :00:1f.3: bound :00:02.0 (ops i915_audio_component_bind_ops [i915]) [2.532497] snd_hda_codec_realtek hdaudioC0D0: autoconfig for ALC3204: line_outs=1 (0x14/0x0/0x0/0x0/0x0) type:speaker [2.532499] snd_hda_codec_realtek hdaudioC0D0:speaker_outs=0 (0x0/0x0/0x0/0x0/0x0) [2.532500] snd_hda_codec_realtek hdaudioC0D0:hp_outs=1 (0x21/0x0/0x0/0x0/0x0) [2.532501] snd_hda_codec_realtek hdaudioC0D0:mono: mono_out=0x0 [2.532502] snd_hda_codec_realtek hdaudioC0D0:inputs: [2.532503] snd_hda_codec_realtek hdaudioC0D0: Headphone Mic=0x1a [2.532504] snd_hda_codec_realtek hdaudioC0D0: Headset Mic=0x19 --- Alsamixer checked for mutes, all OK. Internal mic not present. Cannot remap using hdajackretask due to error tee: /sys/class/sound/hwC0D0/reconfig: Device or resource busy. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 Uname: Linux 5.3.0-24-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: tom3754 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sat Dec 7 08:10:21 2019 InstallationDate: Installed on 2019-12-06 (0 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Title: PCI/internal sound card not detected UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/30/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.3.0 dmi.board.name: 0012KY dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.3.0:bd10/30/2019:svnDellInc.:pnInspiron5490:pvr:rvnDellInc.:rn0012KY:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Inspiron dmi.product.name: Inspiron 5490 dmi.product.sku: 0955 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1855521/+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 1854664] Re: Allow a user to select among a full screen app menu, bottom of the screen horizontal app menu with left/right arrows, or a vertical app menu with up/down arrows lo
Thanks. I like your design mockups, particularly the vertical bar. I think this is worth suggesting to the Gnome Shell developers so please open a bug requesting the feature at: https://gitlab.gnome.org/GNOME/gnome-shell/issues -- 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/1854664 Title: Allow a user to select among a full screen app menu, bottom of the screen horizontal app menu with left/right arrows, or a vertical app menu with up/down arrows located next to the dash. Status in gnome-shell package in Ubuntu: Incomplete Bug description: Ubuntu 19.10 1. In the Settings app, Dock(Dash) screen, there should be an "Application Menu Style" option. The user could select: Full screen, Horizontal, or Vertical. 2. The ability to choose the application menu style. I would prefer a horizontal applications menu. 3. A full screen application menu is the only option. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1854664/+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 1854531] Re: [radeon] Ubuntu fails to run Xorg the first reboot after I set WaylandEnabled to false in gdm3's custom.conf (AMD Caicos)
Please try installing a newer kernel like https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.4.2/ ** Changed in: gdm3 (Ubuntu) Status: New => Incomplete ** Changed in: linux (Ubuntu) Status: New => Incomplete ** Changed in: xorg-server (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1854531 Title: [radeon] Ubuntu fails to run Xorg the first reboot after I set WaylandEnabled to false in gdm3's custom.conf (AMD Caicos) Status in gdm3 package in Ubuntu: Incomplete Status in linux package in Ubuntu: Incomplete Status in xorg-server package in Ubuntu: Incomplete Bug description: Whenever I set Wayland to false in Gnome Display Manager's custom.conf file and then reboot, I still see the same scrambled graphics on the machine as if it were using Wayland. Rebooting the machine a SECOND time resolves the issue. However, I should not have to reboot twice for the new setting to take effect. Steps to Reproduce: 1. When the machine boots up with scrambled graphics, press Control+Alt+F3 2. Log into the machine using the tty session and run "sudo editor /etc/gdm3/custom.conf 3. Set Wayland to false and reboot 4. Notice after reboot the same scrambled graphics appear until the user reboots again Expected Results: Gnome Display Manager runs xorg and xorg shows the correct graphics for the machine. Actual Results: Graphics are scrambled and settings do not appear to take effect until next reboot. This issue occurred right before 12:45 PM, EDT, on November 29, 2019. Description: Ubuntu 18.04.3 LTS Release: 18.04 xorg: Installed: 1:7.7+19ubuntu7.1 Candidate: 1:7.7+19ubuntu7.1 Version table: *** 1:7.7+19ubuntu7.1 500 500 http://us.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 100 /var/lib/dpkg/status 1:7.7+19ubuntu7 500 500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages gdm3: Installed: 3.28.3-0ubuntu18.04.4 Candidate: 3.28.3-0ubuntu18.04.4 Version table: *** 3.28.3-0ubuntu18.04.4 500 500 http://us.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 Packages 100 /var/lib/dpkg/status 3.28.0-0ubuntu1 500 500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-70.79-generic 4.15.18 Uname: Linux 4.15.0-70-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Nov 29 12:39:33 2019 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Caicos [Radeon HD 6450/7450/8450 / R5 230 OEM] [1002:6779] (prog-if 00 [VGA controller]) Subsystem: XFX Pine Group Inc. Caicos [Radeon HD 6450/7450/8450 / R5 230 OEM] [1682:3207] MachineType: Gateway DX4860 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-70-generic root=UUID=751019b9-8693-494c-ad69-17ddf9e51235 ro splash quiet vt.handoff=1 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/01/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P02-A1 dmi.board.name: IPISB-VR dmi.board.vendor: Gateway dmi.board.version: 1.01 dmi.chassis.type: 3 dmi.chassis.vendor: Gateway dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP02-A1:bd08/01/2011:svnGateway:pnDX4860:pvr:rvnGateway:rnIPISB-VR:rvr1.01:cvnGateway:ct3:cvr: dmi.product.family: Gateway Desktop dmi.product.name: DX4860 dmi.sys.vendor: Gateway version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97-1ubuntu1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.8-0ubuntu0~18.04.3 version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.8-0ubuntu0~18.04.3 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.3 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 --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 DistroRelease: Ubuntu 18.04 Package: xorg-server PackageArchitecture: amd64 ProcEnviron: TERM=linux PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash
[Desktop-packages] [Bug 1854531] Re: [radeon] Ubuntu fails to run Xorg the first reboot after I set WaylandEnabled to false in gdm3's custom.conf
I feel this is going to be closely related to bug 1775881. Maybe if it's a kernel bug then it can affect both Wayland and Xorg. Just one more often than the other. ** Summary changed: - [radeon] Ubuntu fails to run Xorg the first reboot after I set WaylandEnabled to false in gdm3's custom.conf + [radeon] Ubuntu fails to run Xorg the first reboot after I set WaylandEnabled to false in gdm3's custom.conf (AMD Caicos) ** Also affects: linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1854531 Title: [radeon] Ubuntu fails to run Xorg the first reboot after I set WaylandEnabled to false in gdm3's custom.conf (AMD Caicos) Status in gdm3 package in Ubuntu: Incomplete Status in linux package in Ubuntu: Incomplete Status in xorg-server package in Ubuntu: Incomplete Bug description: Whenever I set Wayland to false in Gnome Display Manager's custom.conf file and then reboot, I still see the same scrambled graphics on the machine as if it were using Wayland. Rebooting the machine a SECOND time resolves the issue. However, I should not have to reboot twice for the new setting to take effect. Steps to Reproduce: 1. When the machine boots up with scrambled graphics, press Control+Alt+F3 2. Log into the machine using the tty session and run "sudo editor /etc/gdm3/custom.conf 3. Set Wayland to false and reboot 4. Notice after reboot the same scrambled graphics appear until the user reboots again Expected Results: Gnome Display Manager runs xorg and xorg shows the correct graphics for the machine. Actual Results: Graphics are scrambled and settings do not appear to take effect until next reboot. This issue occurred right before 12:45 PM, EDT, on November 29, 2019. Description: Ubuntu 18.04.3 LTS Release: 18.04 xorg: Installed: 1:7.7+19ubuntu7.1 Candidate: 1:7.7+19ubuntu7.1 Version table: *** 1:7.7+19ubuntu7.1 500 500 http://us.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 100 /var/lib/dpkg/status 1:7.7+19ubuntu7 500 500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages gdm3: Installed: 3.28.3-0ubuntu18.04.4 Candidate: 3.28.3-0ubuntu18.04.4 Version table: *** 3.28.3-0ubuntu18.04.4 500 500 http://us.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 Packages 100 /var/lib/dpkg/status 3.28.0-0ubuntu1 500 500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-70.79-generic 4.15.18 Uname: Linux 4.15.0-70-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Nov 29 12:39:33 2019 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Caicos [Radeon HD 6450/7450/8450 / R5 230 OEM] [1002:6779] (prog-if 00 [VGA controller]) Subsystem: XFX Pine Group Inc. Caicos [Radeon HD 6450/7450/8450 / R5 230 OEM] [1682:3207] MachineType: Gateway DX4860 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-70-generic root=UUID=751019b9-8693-494c-ad69-17ddf9e51235 ro splash quiet vt.handoff=1 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/01/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P02-A1 dmi.board.name: IPISB-VR dmi.board.vendor: Gateway dmi.board.version: 1.01 dmi.chassis.type: 3 dmi.chassis.vendor: Gateway dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP02-A1:bd08/01/2011:svnGateway:pnDX4860:pvr:rvnGateway:rnIPISB-VR:rvr1.01:cvnGateway:ct3:cvr: dmi.product.family: Gateway Desktop dmi.product.name: DX4860 dmi.sys.vendor: Gateway version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97-1ubuntu1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.8-0ubuntu0~18.04.3 version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.8-0ubuntu0~18.04.3 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.3 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 --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64
[Desktop-packages] [Bug 1852101] Re: Monitors keep turning on when in power saving mode, every time.
Regardless, does the screen stay dark indefinitely while the peripherals are unplugged? And does plugging them back in successfully wake it up? -- 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/1852101 Title: Monitors keep turning on when in power saving mode, every time. Status in gnome-shell package in Ubuntu: Incomplete Bug description: Whenever I lock my computer, or it goes into power saving mode automatically, the monitors turn back on and show the lock screen a few seconds later. This has persisted now for about a year, has persisted across multiple upgrades (18.10, 19.04, 19.10) as well as complete hardware replacement (CPU intel -> AMD, GPU nVidia -> AMD). So I'm convinced this is a software bug. The first line in logging that I can find that seems to trigger this is: "gnome-shell[1967]: ../../../gobject/gsignal.c:2647: instance '0x55daa50a2920' has no handler with id '145952'" I update my system regularly, so this looks to either be a regression, or uncaught bug. I don't know if other things are causing this, but that's the first line (based on time) that is reported when it turns the monitors back on. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-shell 3.34.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1 Uname: Linux 5.3.0-19-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Nov 11 09:40:42 2019 DisplayManager: gdm3 InstallationDate: Installed on 2019-03-08 (247 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) RelatedPackageVersions: mutter-common 3.34.1-1ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to eoan on 2019-11-05 (5 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1852101/+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 1851322] Re: VPN auto-connect is not working
** Also affects: gnome-shell via https://gitlab.gnome.org/GNOME/gnome-shell/issues/2008 Importance: Unknown Status: Unknown ** Changed in: gnome-shell (Ubuntu) Importance: Low => Medium ** Changed in: gnome-shell (Ubuntu) Status: Incomplete => Confirmed -- 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/1851322 Title: VPN auto-connect is not working Status in GNOME Shell: Unknown Status in gnome-shell package in Ubuntu: Confirmed Bug description: Hi, This is a duplicate of bug: https://bugs.launchpad.net/network-manager/+bug/1718931 It is marked as fixed, but the feature is still broken for me. I configured my Wifi connection to automatically connect to a VPN, but it only works if I manually connect to the Wifi via NetworkManager. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: network-manager 1.20.4-2ubuntu2 ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1 Uname: Linux 5.3.0-19-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu8.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Nov 5 04:07:00 2019 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2019-09-26 (39 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.20.4 connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1851322/+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 1851528] Re: JS ERROR: TypeError: malformed UTF-8 character sequence at offset 0 and segfault in _filterKeybinding:windowManager.js:1825 from invoke_handler() from process_even
OK, incomplete then. I have detached https://gitlab.gnome.org/GNOME /gnome-shell/issues/1870 so that the bug can expire if there is still no news in 60 days. ** Changed in: gnome-shell (Ubuntu) Status: Triaged => Incomplete ** Project changed: gnome-shell => ubuntu ** Changed in: ubuntu Importance: Unknown => Undecided ** Changed in: ubuntu Remote watch: gitlab.gnome.org/GNOME/gnome-shell/issues #1870 => None ** No longer affects: ubuntu ** Bug watch removed: gitlab.gnome.org/GNOME/gnome-shell/issues #1870 https://gitlab.gnome.org/GNOME/gnome-shell/issues/1870 -- 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/1851528 Title: JS ERROR: TypeError: malformed UTF-8 character sequence at offset 0 and segfault in _filterKeybinding:windowManager.js:1825 from invoke_handler() from process_event() from process_special_modifier_key() Status in gnome-shell package in Ubuntu: Incomplete Bug description: I was trying to bring my Firefox window to front by pressing Super+2 (it's my second pinned launcher), and gnome-shell crashed. journalctl shows this: lapkr. 06 16:38:58 blynas gnome-shell[3417]: JS ERROR: TypeError: malformed UTF-8 character sequence at offset 0 _filterKeybinding@resource:///org/gnome/shell/ui/windowManager.js:1825:43 lapkr. 06 16:38:58 blynas gnome-shell[3417]: GNOME Shell crashed with signal 11 lapkr. 06 16:38:58 blynas gnome-shell[3417]: == Stack trace for context 0x56068fb2e3e0 == I have a crash dump in /var/crash/, but apport thinks it's unreportable because my rygel was out of date. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1851528/+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 1853094] Re: Screen tearing in xorg gnome session on Latitude 7480 with WD19TB Thunderbolt dock
Note that tearing on all-but-one monitor in Xorg sessions is expected. It's an unfortunate feature of Xorg with DRI2. If you can convince the system to use DRI3 and TearFree then that avoids it. But that feature also doesn't exist for all graphics drivers. Please run: lspci -k > lspcik.txt and attach 'lspcik.txt' as well as your $HOME/.local/share/xorg/Xorg.0.log ** Changed in: xorg-server (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1853094 Title: Screen tearing in xorg gnome session on Latitude 7480 with WD19TB Thunderbolt dock Status in xorg-server package in Ubuntu: Incomplete Bug description: I have the WD19TB Thunderbolt dock connected to a Dell Latitude 7480 laptop with two external displays. The laptop itself is closed (internal display is not used). In a gnome xorg session, there is severe tearing on parts of the screen when dragging windows or scrolling content. Under a wayland session there is no screen tearing, but I have keyboard key repetition problems which make this mostly unusable day- to-day (https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1849405). I can supply short phone videos of tearing occurring on the screens if required. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: mutter 3.28.4-0ubuntu18.04.2 ProcVersionSignature: Ubuntu 5.0.0-36.39~18.04.1-generic 5.0.21 Uname: Linux 5.0.0-36-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 CurrentDesktop: GNOME Date: Tue Nov 19 14:02:09 2019 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_AU.UTF-8 SHELL=/bin/bash SourcePackage: mutter UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1853094/+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 1846398] Re: Fractional scaling has significant visible tearing in Xorg sessions
Sorry Matt, I have now reopened bug 1853094 for you. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1846398 Title: Fractional scaling has significant visible tearing in Xorg sessions Status in X.Org X server: New Status in xorg-server package in Ubuntu: Confirmed Bug description: On my laptop, fractional scaling seems fine, including watching a YouTube video. It has a quad HD display. Enabling fractional scaling on my desktop which is attached to a single 4k display, fractional scaling isn't usable. The video appears to be constantly refreshing and not using the same acceleration as if I just run at 100% or 200%. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-shell 3.34.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-13.14-generic 5.3.0 Uname: Linux 5.3.0-13-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Oct 2 14:23:33 2019 DisplayManager: gdm3 InstallationDate: Installed on 2018-07-24 (435 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180724) ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 3.34.0-3ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to eoan on 2019-07-19 (74 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/xorg-server/+bug/1846398/+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 1775881] Status changed to Confirmed
This change was made by a bot. ** Changed in: linux (Ubuntu) Status: New => Confirmed -- 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/1775881 Title: [radeon] Wayland sessions including the login screen are just static noise on AMD Caicos Status in gdm3 package in Ubuntu: New Status in linux package in Ubuntu: Confirmed Status in mutter package in Ubuntu: New Bug description: Ubuntu Version 18.04 LTS gdm3: Installed: 3.28.0-0ubuntu1 500 Package name: /etc/gdm3 Whenever I boot Ubuntu following installation from the official install ISO, the boot screen appears, but the login manager appears as static, scrambled graphics, making me unable to login without opening the VT and installing lightdm and switching to that login manager. Expected Results: Login manager appears with login field, background, and menu while I am able to find, click, and enter information into the login text fields. Actual Results: Scrambled noise appeared on my screen and I am unable to leave without force-shutting down my Gateway PC, or opening a VT and installing lightdm, rebooting afterwards. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gdm3 3.28.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Uname: Linux 4.15.0-22-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 Date: Fri Jun 8 11:41:23 2018 InstallationDate: Installed on 2018-06-07 (1 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) ProcEnviron: TERM=linux PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gdm3 UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 Package: mutter PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 4.15.0-70.79-generic 4.15.18 Tags: bionic Uname: Linux 4.15.0-70-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True mtime.conffile..etc.gdm3.custom.conf: 2019-11-29T12:32:53.022462 --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 DistroRelease: Ubuntu 18.04 Package: mutter PackageArchitecture: amd64 ProcEnviron: TERM=linux PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 4.15.0-70.79-generic 4.15.18 Tags: bionic Uname: Linux 4.15.0-70-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True mtime.conffile..etc.gdm3.custom.conf: 2019-11-29T13:14:23.686888 --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 DistroRelease: Ubuntu 18.04 Package: mutter PackageArchitecture: amd64 ProcEnviron: TERM=linux PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 5.0.0-37.40~18.04.1-generic 5.0.21 Tags: bionic Uname: Linux 5.0.0-37-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True mtime.conffile..etc.gdm3.custom.conf: 2019-12-08T13:34:15.689391 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1775881/+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 1853094] Re: Screen tearing in xorg gnome session on Latitude 7480 with WD19TB Thunderbolt dock
** This bug is no longer a duplicate of bug 1846398 Fractional scaling has significant visible tearing in Xorg sessions -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1853094 Title: Screen tearing in xorg gnome session on Latitude 7480 with WD19TB Thunderbolt dock Status in xorg-server package in Ubuntu: Incomplete Bug description: I have the WD19TB Thunderbolt dock connected to a Dell Latitude 7480 laptop with two external displays. The laptop itself is closed (internal display is not used). In a gnome xorg session, there is severe tearing on parts of the screen when dragging windows or scrolling content. Under a wayland session there is no screen tearing, but I have keyboard key repetition problems which make this mostly unusable day- to-day (https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1849405). I can supply short phone videos of tearing occurring on the screens if required. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: mutter 3.28.4-0ubuntu18.04.2 ProcVersionSignature: Ubuntu 5.0.0-36.39~18.04.1-generic 5.0.21 Uname: Linux 5.0.0-36-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 CurrentDesktop: GNOME Date: Tue Nov 19 14:02:09 2019 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_AU.UTF-8 SHELL=/bin/bash SourcePackage: mutter UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1853094/+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 1775881] Re: [radeon] Wayland sessions including the login screen are just static noise on AMD Caicos
** Summary changed: - [radeon] Wayland sessions including the login screen are just static noise + [radeon] Wayland sessions including the login screen are just static noise on AMD Caicos ** Also affects: linux (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/1775881 Title: [radeon] Wayland sessions including the login screen are just static noise on AMD Caicos Status in gdm3 package in Ubuntu: New Status in linux package in Ubuntu: Confirmed Status in mutter package in Ubuntu: New Bug description: Ubuntu Version 18.04 LTS gdm3: Installed: 3.28.0-0ubuntu1 500 Package name: /etc/gdm3 Whenever I boot Ubuntu following installation from the official install ISO, the boot screen appears, but the login manager appears as static, scrambled graphics, making me unable to login without opening the VT and installing lightdm and switching to that login manager. Expected Results: Login manager appears with login field, background, and menu while I am able to find, click, and enter information into the login text fields. Actual Results: Scrambled noise appeared on my screen and I am unable to leave without force-shutting down my Gateway PC, or opening a VT and installing lightdm, rebooting afterwards. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gdm3 3.28.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Uname: Linux 4.15.0-22-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 Date: Fri Jun 8 11:41:23 2018 InstallationDate: Installed on 2018-06-07 (1 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) ProcEnviron: TERM=linux PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gdm3 UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 Package: mutter PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 4.15.0-70.79-generic 4.15.18 Tags: bionic Uname: Linux 4.15.0-70-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True mtime.conffile..etc.gdm3.custom.conf: 2019-11-29T12:32:53.022462 --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 DistroRelease: Ubuntu 18.04 Package: mutter PackageArchitecture: amd64 ProcEnviron: TERM=linux PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 4.15.0-70.79-generic 4.15.18 Tags: bionic Uname: Linux 4.15.0-70-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True mtime.conffile..etc.gdm3.custom.conf: 2019-11-29T13:14:23.686888 --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 DistroRelease: Ubuntu 18.04 Package: mutter PackageArchitecture: amd64 ProcEnviron: TERM=linux PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 5.0.0-37.40~18.04.1-generic 5.0.21 Tags: bionic Uname: Linux 5.0.0-37-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True mtime.conffile..etc.gdm3.custom.conf: 2019-12-08T13:34:15.689391 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1775881/+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 1736011] Re: CRITICAL: Unable to create a DBus proxy for GnomeScreensaver: Error calling StartServiceByName for org.gnome.ScreenSaver: GDBus.Error:org.freedesktop.DBus.Error.Sp
** Tags removed: artful ** Tags added: focal -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-session in Ubuntu. https://bugs.launchpad.net/bugs/1736011 Title: CRITICAL: Unable to create a DBus proxy for GnomeScreensaver: Error calling StartServiceByName for org.gnome.ScreenSaver: GDBus.Error:org.freedesktop.DBus.Error.Spawn.ChildExited: Process org.gnome.ScreenSaver exited with status 1 Status in gnome-session package in Ubuntu: Confirmed Bug description: That error is logged: org.gnome.ScreenSaver[1081]: Unable to init server: Could not connect: Connection refused then: gnome-session[895]: gnome-session-binary[895]: CRITICAL: Unable to create a DBus proxy for GnomeScreensaver: Error calling StartServiceByName for org.gnome.ScreenSaver: GDBus.Error:org.freedesktop.DBus.Error.Spawn.ChildExited: Process org.gnome.ScreenSaver exited with status 1 oem@ubuntu:~$ localectl System Locale: LANG=en_US.UTF-8 VC Keymap: n/a X11 Layout: fr X11 Model: pc105 X11 Variant: oss So, with googling help (https://bbs.archlinux.org/viewtopic.php?id=180103), i've edited /etc/locale-gen (as user) and uncommented the line: fr_FR.UTF-8 and then ran 'sudo locale-gen' and finally rebooted. But the error is still logged after reboot: either i need to set also 'VC Keymap', but how ?, or it is related to the vte version actually used (and need an upgrade) (https://bugs.launchpad.net/ubuntu/+source/vte2.91/+bug/1721412) ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-session 3.26.1-0ubuntu7 ProcVersionSignature: Ubuntu 4.13.0-18.21-generic 4.13.13 Uname: Linux 4.13.0-18-generic x86_64 ApportVersion: 2.20.8-0ubuntu2 Architecture: amd64 CurrentDesktop: GNOME Date: Sun Dec 3 17:17:45 2017 EcryptfsInUse: Yes ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-session UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1736011/+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 1855555] Re: CA0132: Only stereo with Creative Soundblaster ZxR
** Tags added: disco eoan -- 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/185 Title: CA0132: Only stereo with Creative Soundblaster ZxR Status in alsa-driver package in Ubuntu: New Bug description: I have a 5.1 sound system that is connected via three 3.5 mm audio cables with my Sound Blaster ZxR: Front Left, Center, Front Right, Rear Left, Rear Right, LFE I only get sound from "Front Left"/"Front Right". All other speakers don't make a sound. I tested Ubuntu 19.04, Ubuntu 19.10, Manjaro 18.10, different Kernels and the Sound Blaster Patch from reddit, nothing helped. After all these tests, I started again with a fresh Ubuntu 19.10 installation with this output from "alsa information script": http://alsa- project.org/db/?f=c9d4adfbc5441c4975b6e6c7a6fb3cbfc201158a Only thing that I did was changing the default audio device to my ZxR. Otherwise my NVIDIA graphics card is selected. I did that with ~/.asoundrc: defaults.ctl.!card "Creative" defaults.pcm.!card "Creative" defaults.timer.!card "Creative" Interestingly I decided to install Windows 10 on my second drive in dual boot mode. I noticed that when I start Windows all speakers are working. Then I reboot to Ubuntu and all speakers are working, too. This effect will vanish if I shut down my PC and start directly to Ubuntu. So something happens on Windows that is kept while rebooting to Ubuntu.. I already reported this issue at bugzilla.kernel.org: https://bugzilla.kernel.org/show_bug.cgi?id=205315 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/185/+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 1855628] [NEW] Ubuntu keeps having resolution issues and disconnects from the network after I wake it up from sleep
Public bug reported: Whenever I wake the computer up from sleep, the computer no longer connects to the Internet without my having to go into Settings and turn Wi-Fi off and then back on again. Please address this issue. Thank you! network-manager: Installed: 1.10.6-2ubuntu1.2 Candidate: 1.10.6-2ubuntu1.2 Version table: *** 1.10.6-2ubuntu1.2 500 500 http://us.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 100 /var/lib/dpkg/status 1.10.6-2ubuntu1.1 500 500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 Packages 1.10.6-2ubuntu1 500 500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages Description:Ubuntu 18.04.3 LTS Release:18.04 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: network-manager 1.10.6-2ubuntu1.2 ProcVersionSignature: Ubuntu 5.0.0-37.40~18.04.1-generic 5.0.21 Uname: Linux 5.0.0-37-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Dec 8 19:51:31 2019 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback IpRoute: default via 192.168.1.1 dev wlp3s0 proto dhcp metric 600 169.254.0.0/16 dev wlp3s0 scope link metric 1000 192.168.1.0/24 dev wlp3s0 proto kernel scope link src 192.168.1.33 metric 600 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-con: NAMEUUID TYPE TIMESTAMP TIMESTAMP-REAL AUTOCONNECT AUTOCONNECT-PRIORITY READONLY DBUS-PATH ACTIVE DEVICE STATE ACTIVE-PATH SLAVE NETGEAR18 64704ba2-aba5-44de-ad4a-7d0de569815b wifi 1575852612 Sun 08 Dec 2019 07:50:12 PM EST yes 0 no /org/freedesktop/NetworkManager/Settings/1 yes wlp3s0 activated /org/freedesktop/NetworkManager/ActiveConnection/1 -- Wired connection 1 28634e82-4c1c-3a61-b152-3bd92aaa6992 ethernet 1575852610 Sun 08 Dec 2019 07:50:10 PM EST yes 4294966297no /org/freedesktop/NetworkManager/Settings/2 no -- -- -- -- nmcli-dev: DEVICE TYPE STATEDBUS-PATH CONNECTION CON-UUID CON-PATH wlp3s0 wifi connected/org/freedesktop/NetworkManager/Devices/3 NETGEAR18 64704ba2-aba5-44de-ad4a-7d0de569815b /org/freedesktop/NetworkManager/ActiveConnection/1 enp4s0 ethernet unavailable /org/freedesktop/NetworkManager/Devices/2 -- ---- lo loopback unmanaged/org/freedesktop/NetworkManager/Devices/1 -- ---- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.10.6 connected started full enabled enabled enabled enabled enabled ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- 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/1855628 Title: Ubuntu keeps having resolution issues and disconnects from the network after I wake it up from sleep Status in network-manager package in Ubuntu: New Bug description: Whenever I wake the computer up from sleep, the computer no longer connects to the Internet without my having to go into Settings and turn Wi-Fi off and then back on again. Please address this issue. Thank you! network-manager: Installed: 1.10.6-2ubuntu1.2 Candidate: 1.10.6-2ubuntu1.2 Version table: *** 1.10.6-2ubuntu1.2 500 500 http://us.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 100 /var/lib/dpkg/status 1.10.6-2ubuntu1.1 500 500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 Packages 1.10.6-2ubuntu1 500 500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages Description: Ubuntu 18.04.3 LTS Release: 18.04 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: network-manager 1.10.6-2ubuntu1.2 ProcVersionSignature: Ubuntu 5.0.0-37.40~18.04.1-generic 5.0.21 Uname: Linux 5.0.0-37-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64
[Desktop-packages] [Bug 1855626] [NEW] All sound halts for one minute at midnight on Mondays
Public bug reported: Every week, on Monday at 00:00 all sound halts until the clock turns to 00:01. (Note as I often get confused with midnight/midday notations, I am referring to the minute after Sunday 23:59). When this happened the rhythmbox process had been running for more than a day, and I do not know if this happens if rhythmbox was launched on Sunday. I can confirm at the very least that this happened twice when the process was started on the previous Wednesday, and once on the previous Friday at 12:12. This bug happened to me many more times, but I did not check the process' information those times. The song timer stops during this minute. The last time this happened the song skipped a minute when it resumed, but from what I remember of the previous times the song had started off where it stopped (I could remember wrong though). The only difference I can think of between the last occurrence and the previous ones would be that I did not use any buttons this time around. What I expected to happen: The current song keeps playing What happened instead: The song halted for one minute Steps to reproduce: #1 Open Rhythmbox (if possible not on Sunday) #2 Wait for Sunday #3 Start listening to music before Sunday 23:59:59 #4 Wait for Monday 00:00 while music is still playing The song will stop until 00:01 ``` $ lsb_release -rd Description:Ubuntu 18.04.3 LTS Release:18.04 $ apt-cache policy rhythmbox rhythmbox: Installed: 3.4.2-4ubuntu1 Candidate: 3.4.2-4ubuntu1 Version table: *** 3.4.2-4ubuntu1 500 500 http://fr.archive.ubuntu.com/ubuntu bionic/main amd64 Packages 100 /var/lib/dpkg/status ``` Processor: Intel® Core™ i7-6600U CPU @ 2.60GHz × 4 GNOME: 3.28.2 ** Affects: rhythmbox (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to rhythmbox in Ubuntu. https://bugs.launchpad.net/bugs/1855626 Title: All sound halts for one minute at midnight on Mondays Status in rhythmbox package in Ubuntu: New Bug description: Every week, on Monday at 00:00 all sound halts until the clock turns to 00:01. (Note as I often get confused with midnight/midday notations, I am referring to the minute after Sunday 23:59). When this happened the rhythmbox process had been running for more than a day, and I do not know if this happens if rhythmbox was launched on Sunday. I can confirm at the very least that this happened twice when the process was started on the previous Wednesday, and once on the previous Friday at 12:12. This bug happened to me many more times, but I did not check the process' information those times. The song timer stops during this minute. The last time this happened the song skipped a minute when it resumed, but from what I remember of the previous times the song had started off where it stopped (I could remember wrong though). The only difference I can think of between the last occurrence and the previous ones would be that I did not use any buttons this time around. What I expected to happen: The current song keeps playing What happened instead: The song halted for one minute Steps to reproduce: #1 Open Rhythmbox (if possible not on Sunday) #2 Wait for Sunday #3 Start listening to music before Sunday 23:59:59 #4 Wait for Monday 00:00 while music is still playing The song will stop until 00:01 ``` $ lsb_release -rd Description: Ubuntu 18.04.3 LTS Release: 18.04 $ apt-cache policy rhythmbox rhythmbox: Installed: 3.4.2-4ubuntu1 Candidate: 3.4.2-4ubuntu1 Version table: *** 3.4.2-4ubuntu1 500 500 http://fr.archive.ubuntu.com/ubuntu bionic/main amd64 Packages 100 /var/lib/dpkg/status ``` Processor: Intel® Core™ i7-6600U CPU @ 2.60GHz × 4 GNOME: 3.28.2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/1855626/+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 1855625] [NEW] ISO icon does not match other icons
Public bug reported: 1) Ubuntu 19.10 2) 1:3.34.1-1ubuntu1 3) The default "folder" icon does not match the icon in the files pane and the icon on the dock. 4) The three icons should match. ** Affects: nautilus (Ubuntu) Importance: Undecided Status: New ** Attachment added: "file_app.png" https://bugs.launchpad.net/bugs/1855625/+attachment/5310883/+files/file_app.png -- 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/1855625 Title: ISO icon does not match other icons Status in nautilus package in Ubuntu: New Bug description: 1) Ubuntu 19.10 2) 1:3.34.1-1ubuntu1 3) The default "folder" icon does not match the icon in the files pane and the icon on the dock. 4) The three icons should match. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1855625/+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 1855615] [NEW] Device colour profiles - on / off button not working Ubuntu 18.04.3LTS
Public bug reported: I've been trying to calibrate my printer in Ubuntu 18.04.3LTS with gnome-control-center: Installed: 1:3.28.2-0ubuntu0.18.04.5 Candidate: 1:3.28.2-0ubuntu0.18.04.5 Version table: *** 1:3.28.2-0ubuntu0.18.04.5 500 The least documented part of printer profiling is printing the target. Every guide says turn off printer profile calibration, but no-one tells you how. Through trial, error and a lot of paper and ink it seems to me as though the on / off button next to the printer description does nothing. If the user deletes all existing profiles the field reads Not calibrated and no button is displayed, though on a reboot this changes to a button showing colour management (CMS) on and two default profiles are displayed (default RGB and default grey) with RGB selected. The output of these two states is identical. If the setting is default RGB profile with no others loaded, then changing Cups in a browser to Colour Correction: uncorrected refreshes the state to Not Calibrated, though this is the only time I could force this. Setting Cups to Colour Correction: high accuracy does result in an altered output from the printer. I am guessing this is no colour profiling being applied. However if Cups Colour Correction: uncorrected is set, and a profile is loaded in Device Colour Profiles the output from the printer is the same whether or not the CMS on /off button is pressed. I think this is the result of the profile applied by Device Colour Profiles in either case. Similarly, using Cups Colour Correction: High Accuracy and a profile loaded in Device Colour Profiles, the printer output is the same whether or not the CMS on /off button is pressed, though the output is different from the preceding example. I presume this is the result of two colour transformations being carried out. The attached images of my printer output should hopefully help explain this situation. ** Affects: gnome-control-center (Ubuntu) Importance: Undecided Status: New ** Attachment added: "A series of jpgs showing the process" https://bugs.launchpad.net/bugs/1855615/+attachment/5310861/+files/printer%20output%20pictures.zip -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1855615 Title: Device colour profiles - on / off button not working Ubuntu 18.04.3LTS Status in gnome-control-center package in Ubuntu: New Bug description: I've been trying to calibrate my printer in Ubuntu 18.04.3LTS with gnome-control-center: Installed: 1:3.28.2-0ubuntu0.18.04.5 Candidate: 1:3.28.2-0ubuntu0.18.04.5 Version table: *** 1:3.28.2-0ubuntu0.18.04.5 500 The least documented part of printer profiling is printing the target. Every guide says turn off printer profile calibration, but no-one tells you how. Through trial, error and a lot of paper and ink it seems to me as though the on / off button next to the printer description does nothing. If the user deletes all existing profiles the field reads Not calibrated and no button is displayed, though on a reboot this changes to a button showing colour management (CMS) on and two default profiles are displayed (default RGB and default grey) with RGB selected. The output of these two states is identical. If the setting is default RGB profile with no others loaded, then changing Cups in a browser to Colour Correction: uncorrected refreshes the state to Not Calibrated, though this is the only time I could force this. Setting Cups to Colour Correction: high accuracy does result in an altered output from the printer. I am guessing this is no colour profiling being applied. However if Cups Colour Correction: uncorrected is set, and a profile is loaded in Device Colour Profiles the output from the printer is the same whether or not the CMS on /off button is pressed. I think this is the result of the profile applied by Device Colour Profiles in either case. Similarly, using Cups Colour Correction: High Accuracy and a profile loaded in Device Colour Profiles, the printer output is the same whether or not the CMS on /off button is pressed, though the output is different from the preceding example. I presume this is the result of two colour transformations being carried out. The attached images of my printer output should hopefully help explain this situation. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1855615/+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 1855594] Re: Sync chromium 78.0.3904.108-1 (universe) from Debian unstable (main)
This is a request to sync a new source package from Debian, independently of the chromium-browser source, which only exists in Ubuntu and not in Debian. I don't think the chromium-browser source works here, it has to remain as it is after 20.04 LTS for the transition to the chromium snap to fully happen. ** Package changed: chromium-browser (Ubuntu) => ubuntu -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1855594 Title: Sync chromium 78.0.3904.108-1 (universe) from Debian unstable (main) Status in Ubuntu: New Bug description: Please sync chromium 78.0.3904.108-1 (universe) from Debian unstable (main) Now that the other chromium-browser source package in Ubuntu is just a transitional dummy package to the chromium snap, I guess we can now sync the Debian chromium package. This gives the community a chance to maintain a deb chromium package in Ubuntu independent from the snap one. All changelog entries: chromium (78.0.3904.108-1) unstable; urgency=medium * New upstream security release. - CVE-2019-13723: Use-after-free in Bluetooth. Reported by Yuxiang Li - CVE-2019-13724: Out-of-bounds in Bluetooth. Reported by Yuxiang Li * Disable vaapi on armhf (closes: #944627). -- Michael Gilbert Wed, 20 Nov 2019 23:46:06 + chromium (78.0.3904.97-1) unstable; urgency=medium * New upstream security release. * Enable vaapi (closes: #940074). * Fix crash during profile manager shutdown. * Drop libglewmx-dev build dependency (closes: #941050). -- Michael Gilbert Sat, 09 Nov 2019 03:33:52 + chromium (78.0.3904.87-1) unstable; urgency=medium * New upstream stable release. - CVE-2019-5869: Use-after-free in Blink. Reported by Zhe Jin - CVE-2019-5870: Use-after-free in media. Reported by Guang Gong - CVE-2019-5871: Heap overflow in Skia. Reported by Anonymous - CVE-2019-5872: Use-after-free in Mojo. Reported by Zhe Jin - CVE-2019-5874: External URIs may trigger other browsers. Reported by James Lee - CVE-2019-5875: URL bar spoof. Reported by Khalil Zhani - CVE-2019-5876: Use-after-free in media. Reported by Man Yue Mo - CVE-2019-5877: Out-of-bounds access in V8. Reported by Guang Gong - CVE-2019-5878: Use-after-free in V8. Reported by Guang Gong - CVE-2019-5879: Extensions can read some local files. Reported by Jinseo Kim - CVE-2019-5880: SameSite cookie bypass. Reported by Jun Kokatsu - CVE-2019-13659: URL spoof. Reported by Lnyas Zhang - CVE-2019-13660: Full screen notification overlap. Reported by Wenxu Wu - CVE-2019-13661: Full screen notification spoof. Reported by Wenxu Wu - CVE-2019-13662: CSP bypass. Reported by David Erceg - CVE-2019-13663: IDN spoof. Reported by Lnyas Zhang - CVE-2019-13664: CSRF bypass. Reported by thomas "zemnmez" shadwell - CVE-2019-13665: Multiple file download protection bypass. Reported by Jun Kokatsu - CVE-2019-13666: Side channel using storage size estimate. Reported by Tom Van Goethem - CVE-2019-13667: URI bar spoof when using external app URIs. Reported by Khalil Zhani - CVE-2019-13668: Global window leak via console. Reported by David Erceg - CVE-2019-13669: HTTP authentication spoof. Reported by Khalil Zhani - CVE-2019-13670: V8 memory corruption in regex. Reported by Guang Gong - CVE-2019-13671: Dialog box fails to show origin. Reported by xisigr - CVE-2019-13673: Cross-origin information leak using devtools. Reported by David Erceg - CVE-2019-13674: IDN spoofing. Reported by Khalil Zhani - CVE-2019-13675: Extensions can be disabled by trailing slash. Reported by Jun Kokatsu - CVE-2019-13676: Google URI shown for certificate warning. Reported by Wenxu Wu - CVE-2019-13677: Chrome web store origin needs to be isolated. Reported by Jun Kokatsu - CVE-2019-13678: Download dialog spoofing. Reported by Ronni Skansing - CVE-2019-13679: User gesture needed for printing. Reported by Conrad Irwin - CVE-2019-13680: IP address spoofing to servers. Reported by Thijs Alkemade - CVE-2019-13681: Bypass on download restrictions. Reported by David Erceg - CVE-2019-13682: Site isolation bypass. Reported by Jun Kokatsu - CVE-2019-13683: Exceptions leaked by devtools. Reported by David Erceg - CVE-2019-13685: Use-after-free in UI. Reported by Khalil Zhani - CVE-2019-13686: Use-after-free in offline pages. Reported by Brendon - CVE-2019-13687: Use-after-free in media. Reported by Man Yue Mo - CVE-2019-13688: Use-after-free in media. Reported by Man Yue Mo Tiszka - CVE-2019-13691: Omnibox spoof. Reported by David Erceg - CVE-2019-13692: SOP bypass.
[Desktop-packages] [Bug 1855613] [NEW] Xorg froze and put the system in a soft-lock after I turned off Wi-Fi and turned it back on.
Public bug reported: This issue occurred at around 1:51 PM, EDT. When I was shutting down Wi-Fi but then immediately turning it back on while I had terminal open, the machine froze into a soft-lock, and I was forced to open a tty session and restart the computer. Description: Ubuntu 18.04.3 LTS Release: 18.04 xorg: Installed: 1:7.7+19ubuntu7.1 Candidate: 1:7.7+19ubuntu7.1 Version table: *** 1:7.7+19ubuntu7.1 500 500 http://us.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 100 /var/lib/dpkg/status 1:7.7+19ubuntu7 500 500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 5.0.0-37.40~18.04.1-generic 5.0.21 Uname: Linux 5.0.0-37-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Dec 8 14:17:56 2019 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Caicos [Radeon HD 6450/7450/8450 / R5 230 OEM] [1002:6779] (prog-if 00 [VGA controller]) Subsystem: XFX Pine Group Inc. Caicos [Radeon HD 6450/7450/8450 / R5 230 OEM] [1682:3207] MachineType: Gateway DX4860 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-37-generic root=UUID=3c16de60-443d-4ba1-baee-e0f3153202c0 ro quiet splash vt.handoff=1 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/01/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P02-A1 dmi.board.name: IPISB-VR dmi.board.vendor: Gateway dmi.board.version: 1.01 dmi.chassis.type: 3 dmi.chassis.vendor: Gateway dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP02-A1:bd08/01/2011:svnGateway:pnDX4860:pvr:rvnGateway:rnIPISB-VR:rvr1.01:cvnGateway:ct3:cvr: dmi.product.family: Gateway Desktop dmi.product.name: DX4860 dmi.sys.vendor: Gateway version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97-1ubuntu1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.8-0ubuntu0~18.04.3 version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.8-0ubuntu0~18.04.3 version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic ubuntu ** Attachment added: "dmesg.txt" https://bugs.launchpad.net/bugs/1855613/+attachment/5310832/+files/dmesg.txt -- 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/1855613 Title: Xorg froze and put the system in a soft-lock after I turned off Wi-Fi and turned it back on. Status in xorg package in Ubuntu: New Bug description: This issue occurred at around 1:51 PM, EDT. When I was shutting down Wi-Fi but then immediately turning it back on while I had terminal open, the machine froze into a soft-lock, and I was forced to open a tty session and restart the computer. Description: Ubuntu 18.04.3 LTS Release: 18.04 xorg: Installed: 1:7.7+19ubuntu7.1 Candidate: 1:7.7+19ubuntu7.1 Version table: *** 1:7.7+19ubuntu7.1 500 500 http://us.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 100 /var/lib/dpkg/status 1:7.7+19ubuntu7 500 500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 5.0.0-37.40~18.04.1-generic 5.0.21 Uname: Linux 5.0.0-37-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Dec 8 14:17:56 2019 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Caicos [Radeon HD 6450/7450/8450 / R5 230 OEM] [1002:6779] (prog-if 00 [VGA controller]) Subsystem: XFX Pine Group Inc. Caicos [Radeon HD 6450/7450/8450 / R5 230 OEM] [1682:3207] MachineType: Gateway DX4860 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-37-generic root=UUID=3c16de60-443d-4ba1-baee-e0f3153202c0 ro quiet splash vt.handoff=1 SourcePackage: xorg UpgradeStatus: No upgrade log present
[Desktop-packages] [Bug 1775881] modified.conffile..etc.gdm3.custom.conf.txt
apport information ** Attachment added: "modified.conffile..etc.gdm3.custom.conf.txt" https://bugs.launchpad.net/bugs/1775881/+attachment/5310808/+files/modified.conffile..etc.gdm3.custom.conf.txt -- 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/1775881 Title: [radeon] Wayland sessions including the login screen are just static noise Status in gdm3 package in Ubuntu: New Status in mutter package in Ubuntu: New Bug description: Ubuntu Version 18.04 LTS gdm3: Installed: 3.28.0-0ubuntu1 500 Package name: /etc/gdm3 Whenever I boot Ubuntu following installation from the official install ISO, the boot screen appears, but the login manager appears as static, scrambled graphics, making me unable to login without opening the VT and installing lightdm and switching to that login manager. Expected Results: Login manager appears with login field, background, and menu while I am able to find, click, and enter information into the login text fields. Actual Results: Scrambled noise appeared on my screen and I am unable to leave without force-shutting down my Gateway PC, or opening a VT and installing lightdm, rebooting afterwards. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gdm3 3.28.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Uname: Linux 4.15.0-22-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 Date: Fri Jun 8 11:41:23 2018 InstallationDate: Installed on 2018-06-07 (1 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) ProcEnviron: TERM=linux PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gdm3 UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 Package: mutter PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 4.15.0-70.79-generic 4.15.18 Tags: bionic Uname: Linux 4.15.0-70-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True mtime.conffile..etc.gdm3.custom.conf: 2019-11-29T12:32:53.022462 --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 DistroRelease: Ubuntu 18.04 Package: mutter PackageArchitecture: amd64 ProcEnviron: TERM=linux PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 4.15.0-70.79-generic 4.15.18 Tags: bionic Uname: Linux 4.15.0-70-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True mtime.conffile..etc.gdm3.custom.conf: 2019-11-29T13:14:23.686888 --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 DistroRelease: Ubuntu 18.04 Package: mutter PackageArchitecture: amd64 ProcEnviron: TERM=linux PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 5.0.0-37.40~18.04.1-generic 5.0.21 Tags: bionic Uname: Linux 5.0.0-37-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True mtime.conffile..etc.gdm3.custom.conf: 2019-12-08T13:34:15.689391 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1775881/+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 1775881] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1775881/+attachment/5310807/+files/ProcCpuinfoMinimal.txt -- 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/1775881 Title: [radeon] Wayland sessions including the login screen are just static noise Status in gdm3 package in Ubuntu: New Status in mutter package in Ubuntu: New Bug description: Ubuntu Version 18.04 LTS gdm3: Installed: 3.28.0-0ubuntu1 500 Package name: /etc/gdm3 Whenever I boot Ubuntu following installation from the official install ISO, the boot screen appears, but the login manager appears as static, scrambled graphics, making me unable to login without opening the VT and installing lightdm and switching to that login manager. Expected Results: Login manager appears with login field, background, and menu while I am able to find, click, and enter information into the login text fields. Actual Results: Scrambled noise appeared on my screen and I am unable to leave without force-shutting down my Gateway PC, or opening a VT and installing lightdm, rebooting afterwards. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gdm3 3.28.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Uname: Linux 4.15.0-22-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 Date: Fri Jun 8 11:41:23 2018 InstallationDate: Installed on 2018-06-07 (1 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) ProcEnviron: TERM=linux PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gdm3 UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 Package: mutter PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 4.15.0-70.79-generic 4.15.18 Tags: bionic Uname: Linux 4.15.0-70-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True mtime.conffile..etc.gdm3.custom.conf: 2019-11-29T12:32:53.022462 --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 DistroRelease: Ubuntu 18.04 Package: mutter PackageArchitecture: amd64 ProcEnviron: TERM=linux PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 4.15.0-70.79-generic 4.15.18 Tags: bionic Uname: Linux 4.15.0-70-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True mtime.conffile..etc.gdm3.custom.conf: 2019-11-29T13:14:23.686888 --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 DistroRelease: Ubuntu 18.04 Package: mutter PackageArchitecture: amd64 ProcEnviron: TERM=linux PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 5.0.0-37.40~18.04.1-generic 5.0.21 Tags: bionic Uname: Linux 5.0.0-37-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True mtime.conffile..etc.gdm3.custom.conf: 2019-12-08T13:34:15.689391 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1775881/+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 1775881] Re: [radeon] Wayland sessions including the login screen are just static noise
apport information ** Description changed: Ubuntu Version 18.04 LTS gdm3: Installed: 3.28.0-0ubuntu1 500 Package name: /etc/gdm3 Whenever I boot Ubuntu following installation from the official install ISO, the boot screen appears, but the login manager appears as static, scrambled graphics, making me unable to login without opening the VT and installing lightdm and switching to that login manager. Expected Results: Login manager appears with login field, background, and menu while I am able to find, click, and enter information into the login text fields. Actual Results: Scrambled noise appeared on my screen and I am unable to leave without force-shutting down my Gateway PC, or opening a VT and installing lightdm, rebooting afterwards. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gdm3 3.28.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Uname: Linux 4.15.0-22-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 Date: Fri Jun 8 11:41:23 2018 InstallationDate: Installed on 2018-06-07 (1 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) ProcEnviron: TERM=linux PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gdm3 UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 Package: mutter PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 4.15.0-70.79-generic 4.15.18 Tags: bionic Uname: Linux 4.15.0-70-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True mtime.conffile..etc.gdm3.custom.conf: 2019-11-29T12:32:53.022462 --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 DistroRelease: Ubuntu 18.04 Package: mutter PackageArchitecture: amd64 ProcEnviron: TERM=linux PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 4.15.0-70.79-generic 4.15.18 Tags: bionic Uname: Linux 4.15.0-70-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True mtime.conffile..etc.gdm3.custom.conf: 2019-11-29T13:14:23.686888 + --- + ProblemType: Bug + ApportVersion: 2.20.9-0ubuntu7.9 + Architecture: amd64 + DistroRelease: Ubuntu 18.04 + Package: mutter + PackageArchitecture: amd64 + ProcEnviron: + TERM=linux + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=en_US.UTF-8 + SHELL=/bin/bash + ProcVersionSignature: Ubuntu 5.0.0-37.40~18.04.1-generic 5.0.21 + Tags: bionic + Uname: Linux 5.0.0-37-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo + _MarkForUpload: True + mtime.conffile..etc.gdm3.custom.conf: 2019-12-08T13:34:15.689391 ** Attachment added: "Dependencies.txt" https://bugs.launchpad.net/bugs/1775881/+attachment/5310806/+files/Dependencies.txt -- 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/1775881 Title: [radeon] Wayland sessions including the login screen are just static noise Status in gdm3 package in Ubuntu: New Status in mutter package in Ubuntu: New Bug description: Ubuntu Version 18.04 LTS gdm3: Installed: 3.28.0-0ubuntu1 500 Package name: /etc/gdm3 Whenever I boot Ubuntu following installation from the official install ISO, the boot screen appears, but the login manager appears as static, scrambled graphics, making me unable to login without opening the VT and installing lightdm and switching to that login manager. Expected Results: Login manager appears with login field, background, and menu while I am able to find, click, and enter information into the login text fields. Actual Results: Scrambled noise appeared on my screen and I am unable to leave without force-shutting down my Gateway PC, or opening a VT and installing lightdm, rebooting afterwards. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gdm3 3.28.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Uname: Linux 4.15.0-22-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 Date: Fri Jun 8 11:41:23 2018 InstallationDate: Installed on 2018-06-07 (1 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) ProcEnviron: TERM=linux PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8
[Desktop-packages] [Bug 1854531] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1854531/+attachment/5310784/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1854531 Title: [radeon] Ubuntu fails to run Xorg the first reboot after I set WaylandEnabled to false in gdm3's custom.conf Status in gdm3 package in Ubuntu: New Status in xorg-server package in Ubuntu: New Bug description: Whenever I set Wayland to false in Gnome Display Manager's custom.conf file and then reboot, I still see the same scrambled graphics on the machine as if it were using Wayland. Rebooting the machine a SECOND time resolves the issue. However, I should not have to reboot twice for the new setting to take effect. Steps to Reproduce: 1. When the machine boots up with scrambled graphics, press Control+Alt+F3 2. Log into the machine using the tty session and run "sudo editor /etc/gdm3/custom.conf 3. Set Wayland to false and reboot 4. Notice after reboot the same scrambled graphics appear until the user reboots again Expected Results: Gnome Display Manager runs xorg and xorg shows the correct graphics for the machine. Actual Results: Graphics are scrambled and settings do not appear to take effect until next reboot. This issue occurred right before 12:45 PM, EDT, on November 29, 2019. Description: Ubuntu 18.04.3 LTS Release: 18.04 xorg: Installed: 1:7.7+19ubuntu7.1 Candidate: 1:7.7+19ubuntu7.1 Version table: *** 1:7.7+19ubuntu7.1 500 500 http://us.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 100 /var/lib/dpkg/status 1:7.7+19ubuntu7 500 500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages gdm3: Installed: 3.28.3-0ubuntu18.04.4 Candidate: 3.28.3-0ubuntu18.04.4 Version table: *** 3.28.3-0ubuntu18.04.4 500 500 http://us.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 Packages 100 /var/lib/dpkg/status 3.28.0-0ubuntu1 500 500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-70.79-generic 4.15.18 Uname: Linux 4.15.0-70-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Nov 29 12:39:33 2019 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Caicos [Radeon HD 6450/7450/8450 / R5 230 OEM] [1002:6779] (prog-if 00 [VGA controller]) Subsystem: XFX Pine Group Inc. Caicos [Radeon HD 6450/7450/8450 / R5 230 OEM] [1682:3207] MachineType: Gateway DX4860 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-70-generic root=UUID=751019b9-8693-494c-ad69-17ddf9e51235 ro splash quiet vt.handoff=1 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/01/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P02-A1 dmi.board.name: IPISB-VR dmi.board.vendor: Gateway dmi.board.version: 1.01 dmi.chassis.type: 3 dmi.chassis.vendor: Gateway dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP02-A1:bd08/01/2011:svnGateway:pnDX4860:pvr:rvnGateway:rnIPISB-VR:rvr1.01:cvnGateway:ct3:cvr: dmi.product.family: Gateway Desktop dmi.product.name: DX4860 dmi.sys.vendor: Gateway version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97-1ubuntu1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.8-0ubuntu0~18.04.3 version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.8-0ubuntu0~18.04.3 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.3 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 --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 DistroRelease: Ubuntu 18.04 Package: xorg-server PackageArchitecture: amd64 ProcEnviron: TERM=linux PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 5.0.0-37.40~18.04.1-generic 5.0.21 Tags: bionic Uname: Linux 5.0.0-37-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev
[Desktop-packages] [Bug 1854531] modified.conffile..etc.gdm3.custom.conf.txt
apport information ** Attachment added: "modified.conffile..etc.gdm3.custom.conf.txt" https://bugs.launchpad.net/bugs/1854531/+attachment/5310785/+files/modified.conffile..etc.gdm3.custom.conf.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1854531 Title: [radeon] Ubuntu fails to run Xorg the first reboot after I set WaylandEnabled to false in gdm3's custom.conf Status in gdm3 package in Ubuntu: New Status in xorg-server package in Ubuntu: New Bug description: Whenever I set Wayland to false in Gnome Display Manager's custom.conf file and then reboot, I still see the same scrambled graphics on the machine as if it were using Wayland. Rebooting the machine a SECOND time resolves the issue. However, I should not have to reboot twice for the new setting to take effect. Steps to Reproduce: 1. When the machine boots up with scrambled graphics, press Control+Alt+F3 2. Log into the machine using the tty session and run "sudo editor /etc/gdm3/custom.conf 3. Set Wayland to false and reboot 4. Notice after reboot the same scrambled graphics appear until the user reboots again Expected Results: Gnome Display Manager runs xorg and xorg shows the correct graphics for the machine. Actual Results: Graphics are scrambled and settings do not appear to take effect until next reboot. This issue occurred right before 12:45 PM, EDT, on November 29, 2019. Description: Ubuntu 18.04.3 LTS Release: 18.04 xorg: Installed: 1:7.7+19ubuntu7.1 Candidate: 1:7.7+19ubuntu7.1 Version table: *** 1:7.7+19ubuntu7.1 500 500 http://us.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 100 /var/lib/dpkg/status 1:7.7+19ubuntu7 500 500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages gdm3: Installed: 3.28.3-0ubuntu18.04.4 Candidate: 3.28.3-0ubuntu18.04.4 Version table: *** 3.28.3-0ubuntu18.04.4 500 500 http://us.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 Packages 100 /var/lib/dpkg/status 3.28.0-0ubuntu1 500 500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-70.79-generic 4.15.18 Uname: Linux 4.15.0-70-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Nov 29 12:39:33 2019 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Caicos [Radeon HD 6450/7450/8450 / R5 230 OEM] [1002:6779] (prog-if 00 [VGA controller]) Subsystem: XFX Pine Group Inc. Caicos [Radeon HD 6450/7450/8450 / R5 230 OEM] [1682:3207] MachineType: Gateway DX4860 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-70-generic root=UUID=751019b9-8693-494c-ad69-17ddf9e51235 ro splash quiet vt.handoff=1 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/01/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P02-A1 dmi.board.name: IPISB-VR dmi.board.vendor: Gateway dmi.board.version: 1.01 dmi.chassis.type: 3 dmi.chassis.vendor: Gateway dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP02-A1:bd08/01/2011:svnGateway:pnDX4860:pvr:rvnGateway:rnIPISB-VR:rvr1.01:cvnGateway:ct3:cvr: dmi.product.family: Gateway Desktop dmi.product.name: DX4860 dmi.sys.vendor: Gateway version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97-1ubuntu1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.8-0ubuntu0~18.04.3 version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.8-0ubuntu0~18.04.3 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.3 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 --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 DistroRelease: Ubuntu 18.04 Package: xorg-server PackageArchitecture: amd64 ProcEnviron: TERM=linux PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 5.0.0-37.40~18.04.1-generic 5.0.21 Tags: bionic Uname: Linux 5.0.0-37-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install)
[Desktop-packages] [Bug 1854531] Re: [radeon] Ubuntu fails to run Xorg the first reboot after I set WaylandEnabled to false in gdm3's custom.conf
apport information ** Tags added: apport-collected ** Description changed: Whenever I set Wayland to false in Gnome Display Manager's custom.conf file and then reboot, I still see the same scrambled graphics on the machine as if it were using Wayland. Rebooting the machine a SECOND time resolves the issue. However, I should not have to reboot twice for the new setting to take effect. Steps to Reproduce: 1. When the machine boots up with scrambled graphics, press Control+Alt+F3 2. Log into the machine using the tty session and run "sudo editor /etc/gdm3/custom.conf 3. Set Wayland to false and reboot 4. Notice after reboot the same scrambled graphics appear until the user reboots again Expected Results: Gnome Display Manager runs xorg and xorg shows the correct graphics for the machine. Actual Results: Graphics are scrambled and settings do not appear to take effect until next reboot. This issue occurred right before 12:45 PM, EDT, on November 29, 2019. Description: Ubuntu 18.04.3 LTS Release: 18.04 xorg: Installed: 1:7.7+19ubuntu7.1 Candidate: 1:7.7+19ubuntu7.1 Version table: *** 1:7.7+19ubuntu7.1 500 500 http://us.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 100 /var/lib/dpkg/status 1:7.7+19ubuntu7 500 500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages gdm3: Installed: 3.28.3-0ubuntu18.04.4 Candidate: 3.28.3-0ubuntu18.04.4 Version table: *** 3.28.3-0ubuntu18.04.4 500 500 http://us.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 Packages 100 /var/lib/dpkg/status 3.28.0-0ubuntu1 500 500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-70.79-generic 4.15.18 Uname: Linux 4.15.0-70-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Nov 29 12:39:33 2019 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Caicos [Radeon HD 6450/7450/8450 / R5 230 OEM] [1002:6779] (prog-if 00 [VGA controller]) Subsystem: XFX Pine Group Inc. Caicos [Radeon HD 6450/7450/8450 / R5 230 OEM] [1682:3207] MachineType: Gateway DX4860 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-70-generic root=UUID=751019b9-8693-494c-ad69-17ddf9e51235 ro splash quiet vt.handoff=1 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/01/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P02-A1 dmi.board.name: IPISB-VR dmi.board.vendor: Gateway dmi.board.version: 1.01 dmi.chassis.type: 3 dmi.chassis.vendor: Gateway dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP02-A1:bd08/01/2011:svnGateway:pnDX4860:pvr:rvnGateway:rnIPISB-VR:rvr1.01:cvnGateway:ct3:cvr: dmi.product.family: Gateway Desktop dmi.product.name: DX4860 dmi.sys.vendor: Gateway version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97-1ubuntu1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.8-0ubuntu0~18.04.3 version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.8-0ubuntu0~18.04.3 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.3 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 + --- + ProblemType: Bug + ApportVersion: 2.20.9-0ubuntu7.9 + Architecture: amd64 + DistroRelease: Ubuntu 18.04 + Package: xorg-server + PackageArchitecture: amd64 + ProcEnviron: + TERM=linux + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=en_US.UTF-8 + SHELL=/bin/bash + ProcVersionSignature: Ubuntu 5.0.0-37.40~18.04.1-generic 5.0.21 + Tags: bionic + Uname: Linux 5.0.0-37-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo + _MarkForUpload: True + mtime.conffile..etc.gdm3.custom.conf: 2019-12-06T15:29:15.074253 ** Attachment added: "Dependencies.txt" https://bugs.launchpad.net/bugs/1854531/+attachment/5310783/+files/Dependencies.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1854531 Title: [radeon] Ubuntu fails to run Xorg the first
[Desktop-packages] [Bug 1855608] [NEW] Dell XPS 13 7390 screen corruption in 18.04 LTS, 19.04 and 19.10
Public bug reported: I just received a new Dell XPS 13 7390 laptop. With factory preinstalled Ubuntu Linux 18.04 LTS and the Dell OEM kernel, graphics was severely distorted. The display would constantly flicker with areas of the display staying black or showing patterns of square color blocks. Booting in recovery mode worked, though and I was able to install all updates for preinstalled 18.04 LTS with the OEM kernel. Problems in non- recovery mode persisted after installing all updates. I then updated to Ubuntu 19.04 and changed to "generic" linux kernel image without success: Problem persisted, only recovery mode was usable. I updated once more to 19.10 again without any success. >From the perhaps related bug #1849947 I tried latest drm-tip kernel from https://kernel.ubuntu.com/~kernel-ppa/mainline/ drm-tip kernel solves the issue for first boot, but after resuming from suspend, the same issues display issues occur. Kernel images I tried: - linux-image-4.15.0-1065-oem - on Ubuntu 18.04 LTS, corrupted graphics output without "nomodeset" - linux-image-5.0.0-37-generic - on Ubuntu 19.04, corrupted graphics output without "nomodeset" - linux-image-5.3.0-24-generic - on Ubuntu 19.10, corrupted graphics output without "nomodeset" - linux-image-unsigned-5.4.0-994-generic - on Ubuntu 19.10, corrupted graphics output after resuming from suspend ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 Uname: Linux 5.4.0-994-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Dec 8 18:51:15 2019 DistUpgraded: 2019-12-07 22:36:44,841 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process “./xorg_fix_proprietary.py” (No such file or directory) (8)) DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-bionic-amd64-20180608-47+beaver-three-eyed-raven+X92 DistroCodename: eoan DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Device [8086:9b41] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:0962] InstallationDate: Installed on 2019-11-25 (13 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20180608-09:38 MachineType: Dell Inc. XPS 13 7390 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-994-generic root=UUID=45745b59-5aff-4246-94d2-34fe9ae5012f ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to eoan on 2019-12-07 (0 days ago) dmi.bios.date: 11/08/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.3.1 dmi.board.name: 0G2D0W dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.3.1:bd11/08/2019:svnDellInc.:pnXPS137390:pvr:rvnDellInc.:rn0G2D0W:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 7390 dmi.product.sku: 0962 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.99-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.1-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-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 corruption eoan third-party-packages ubuntu ** Attachment added: "Picture taken after booting linux-image-5.3.0-24-generic kernel on Ubuntu 19.10" https://bugs.launchpad.net/bugs/1855608/+attachment/5310765/+files/IMG_20191208_181821455.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/1855608 Title: Dell XPS 13 7390 screen corruption in 18.04 LTS, 19.04 and 19.10 Status in xorg package in Ubuntu: New Bug description: I just received a new Dell XPS 13 7390 laptop. With factory preinstalled Ubuntu Linux 18.04 LTS and the Dell OEM kernel, graphics was severely distorted. The display would constantly flicker with areas of the display staying black or showing patterns of square color blocks. Booting in recovery mode worked, though and I was able to install all updates for preinstalled 18.04 LTS with the OEM kernel. Problems in non-recovery mode persisted after installing all updates. I then updated to Ubuntu 19.04 and changed to "generic" linux kernel image
[Desktop-packages] [Bug 1851322] Re: VPN auto-connect is not working
@Daniel bug reported upstream: https://gitlab.gnome.org/GNOME/gnome-shell/issues/2008 It seems that today, even manually triggering the VPN connection doesn't work anymore. If you don't set "store password for all users" for the VPN credentials, the connection will fails. ** Bug watch added: gitlab.gnome.org/GNOME/gnome-shell/issues #2008 https://gitlab.gnome.org/GNOME/gnome-shell/issues/2008 -- 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/1851322 Title: VPN auto-connect is not working Status in gnome-shell package in Ubuntu: Incomplete Bug description: Hi, This is a duplicate of bug: https://bugs.launchpad.net/network-manager/+bug/1718931 It is marked as fixed, but the feature is still broken for me. I configured my Wifi connection to automatically connect to a VPN, but it only works if I manually connect to the Wifi via NetworkManager. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: network-manager 1.20.4-2ubuntu2 ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1 Uname: Linux 5.3.0-19-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu8.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Nov 5 04:07:00 2019 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2019-09-26 (39 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.20.4 connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1851322/+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 1855596] Re: NULL ptr dereference in TextSelectionPainter::hasGlyphLessFont() with certain PDF
The attachment "Fixes a possible NULL ptr dereference in TextSelectionPainter::hasGlyphLessFont()" seems to be a patch. If it isn't, please remove the "patch" flag from the attachment, remove the "patch" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team. [This is an automated message performed by a Launchpad user owned by ~brian-murray, for any issues please contact him.] ** Tags added: patch -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to poppler in Ubuntu. https://bugs.launchpad.net/bugs/1855596 Title: NULL ptr dereference in TextSelectionPainter::hasGlyphLessFont() with certain PDF Status in poppler package in Ubuntu: New Bug description: When viewing a certain PDF (which I unfortunately can't share) using evince, a see a crash in libpoppler90. It's a NULL pointer dereference in TextSelectionPainter::hasGlyphLessFont(), because in this certain PDF, for whatever reason, sel->word->getFontName(0) may return NULL. Attached you'll find a proposed patch increasing the robustness in this case. Cheers, Enrik To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/poppler/+bug/1855596/+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 1855596] [NEW] NULL ptr dereference in TextSelectionPainter::hasGlyphLessFont() with certain PDF
Public bug reported: When viewing a certain PDF (which I unfortunately can't share) using evince, a see a crash in libpoppler90. It's a NULL pointer dereference in TextSelectionPainter::hasGlyphLessFont(), because in this certain PDF, for whatever reason, sel->word->getFontName(0) may return NULL. Attached you'll find a proposed patch increasing the robustness in this case. Cheers, Enrik ** Affects: poppler (Ubuntu) Importance: Undecided Status: New ** Patch added: "Fixes a possible NULL ptr dereference in TextSelectionPainter::hasGlyphLessFont()" https://bugs.launchpad.net/bugs/1855596/+attachment/5310742/+files/fix_null_ptr_derefence_in_TextSelectionPainter_hasGlyphLessFont.patch -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to poppler in Ubuntu. https://bugs.launchpad.net/bugs/1855596 Title: NULL ptr dereference in TextSelectionPainter::hasGlyphLessFont() with certain PDF Status in poppler package in Ubuntu: New Bug description: When viewing a certain PDF (which I unfortunately can't share) using evince, a see a crash in libpoppler90. It's a NULL pointer dereference in TextSelectionPainter::hasGlyphLessFont(), because in this certain PDF, for whatever reason, sel->word->getFontName(0) may return NULL. Attached you'll find a proposed patch increasing the robustness in this case. Cheers, Enrik To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/poppler/+bug/1855596/+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 1848741] Re: [amdgpu] Ubuntu 19.10 horizontal graphics corruption on AMD Ryzen 2500u (Raven Ridge)
Confirming that comment #23 also solved my problem on a B450 I Aorus Pro Wifi ITX motherboard with Ryzen 5 3400G. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-amdgpu in Ubuntu. https://bugs.launchpad.net/bugs/1848741 Title: [amdgpu] Ubuntu 19.10 horizontal graphics corruption on AMD Ryzen 2500u (Raven Ridge) Status in linux package in Ubuntu: Confirmed Status in xserver-xorg-video-amdgpu package in Ubuntu: Confirmed Bug description: I have graphics artefacts: screan tearing, pieces of the previous window appear in the newly opened window. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 19.10 InstallationDate: Installed on 2019-09-08 (42 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) Package: gnome-shell 3.34.1-1ubuntu1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1 RelatedPackageVersions: mutter-common 3.34.1-1ubuntu1 Tags: eoan Uname: Linux 5.3.0-18-generic x86_64 UpgradeStatus: Upgraded to eoan on 2019-10-17 (3 days ago) UserGroups: adm cdrom dip docker input lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1848741/+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 1855595] [NEW] CUPS fails to print to autodetected printers because of cups-browsed error
Public bug reported: When trying to autodetected IPP printers, print job stays in queue. lpstat -l: HP_LaserJet_CM1415fn_44A808_-23 erik 30720 So 08 Dez 2019 15:50:20 CET Status: No suitable destination host found by cups-browsed. Alarme: resources-are-not-ready in Warteschlange eingereiht für HP_LaserJet_CM1415fn_44A808_ Removing the print job, restarting cups-browsed with `service cups- browsed restart` followed by `service cups restart` enables printing for one print job; the next one fails again with the same issue. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: cups-browsed 1.25.13-1 ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 Uname: Linux 5.3.0-24-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu13 Architecture: amd64 CurrentDesktop: LXQt Date: Sun Dec 8 16:06:02 2019 InstallationDate: Installed on 2019-10-19 (50 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20191019) Lpstat: device for HP_LaserJet_CM1415fn_44A808_: implicitclass://HP_LaserJet_CM1415fn_44A808_/ device for Samsung_C48x_Series_SEC84251900EE44_: implicitclass://Samsung_C48x_Series_SEC84251900EE44_/ MachineType: Dell Inc. Latitude E6530 Papersize: a4 PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/HP_LaserJet_CM1415fn_44A808_.ppd', '/etc/cups/ppd/Samsung_C48x_Series_SEC84251900EE44_.ppd'] failed with exit code 2: grep: /etc/cups/ppd/HP_LaserJet_CM1415fn_44A808_.ppd: Permission denied grep: /etc/cups/ppd/Samsung_C48x_Series_SEC84251900EE44_.ppd: Permission denied ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_utwd0l@/vmlinuz-5.3.0-24-generic root=ZFS=rpool/ROOT/ubuntu_utwd0l ro quiet splash vt.handoff=1 SourcePackage: cups-filters UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/30/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: A22 dmi.board.name: 07Y85M dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA22:bd11/30/2018:svnDellInc.:pnLatitudeE6530:pvr01:rvnDellInc.:rn07Y85M:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E6530 dmi.product.sku: Latitude E6530 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. ** Affects: cups-filters (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cups-filters in Ubuntu. https://bugs.launchpad.net/bugs/1855595 Title: CUPS fails to print to autodetected printers because of cups-browsed error Status in cups-filters package in Ubuntu: New Bug description: When trying to autodetected IPP printers, print job stays in queue. lpstat -l: HP_LaserJet_CM1415fn_44A808_-23 erik 30720 So 08 Dez 2019 15:50:20 CET Status: No suitable destination host found by cups-browsed. Alarme: resources-are-not-ready in Warteschlange eingereiht für HP_LaserJet_CM1415fn_44A808_ Removing the print job, restarting cups-browsed with `service cups- browsed restart` followed by `service cups restart` enables printing for one print job; the next one fails again with the same issue. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: cups-browsed 1.25.13-1 ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 Uname: Linux 5.3.0-24-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu13 Architecture: amd64 CurrentDesktop: LXQt Date: Sun Dec 8 16:06:02 2019 InstallationDate: Installed on 2019-10-19 (50 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20191019) Lpstat: device for HP_LaserJet_CM1415fn_44A808_: implicitclass://HP_LaserJet_CM1415fn_44A808_/ device for Samsung_C48x_Series_SEC84251900EE44_: implicitclass://Samsung_C48x_Series_SEC84251900EE44_/ MachineType: Dell Inc. Latitude E6530 Papersize: a4 PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/HP_LaserJet_CM1415fn_44A808_.ppd', '/etc/cups/ppd/Samsung_C48x_Series_SEC84251900EE44_.ppd'] failed with exit code 2: grep: /etc/cups/ppd/HP_LaserJet_CM1415fn_44A808_.ppd: Permission denied grep: /etc/cups/ppd/Samsung_C48x_Series_SEC84251900EE44_.ppd: Permission denied ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_utwd0l@/vmlinuz-5.3.0-24-generic root=ZFS=rpool/ROOT/ubuntu_utwd0l ro quiet splash vt.handoff=1 SourcePackage: cups-filters UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/30/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: A22 dmi.board.name: 07Y85M dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias:
[Desktop-packages] [Bug 1855594] Re: Sync chromium 78.0.3904.108-1 (universe) from Debian unstable (main)
** Package changed: ubuntu => chromium-browser (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1855594 Title: Sync chromium 78.0.3904.108-1 (universe) from Debian unstable (main) Status in chromium-browser package in Ubuntu: New Bug description: Please sync chromium 78.0.3904.108-1 (universe) from Debian unstable (main) Now that the other chromium-browser source package in Ubuntu is just a transitional dummy package to the chromium snap, I guess we can now sync the Debian chromium package. This gives the community a chance to maintain a deb chromium package in Ubuntu independent from the snap one. All changelog entries: chromium (78.0.3904.108-1) unstable; urgency=medium * New upstream security release. - CVE-2019-13723: Use-after-free in Bluetooth. Reported by Yuxiang Li - CVE-2019-13724: Out-of-bounds in Bluetooth. Reported by Yuxiang Li * Disable vaapi on armhf (closes: #944627). -- Michael Gilbert Wed, 20 Nov 2019 23:46:06 + chromium (78.0.3904.97-1) unstable; urgency=medium * New upstream security release. * Enable vaapi (closes: #940074). * Fix crash during profile manager shutdown. * Drop libglewmx-dev build dependency (closes: #941050). -- Michael Gilbert Sat, 09 Nov 2019 03:33:52 + chromium (78.0.3904.87-1) unstable; urgency=medium * New upstream stable release. - CVE-2019-5869: Use-after-free in Blink. Reported by Zhe Jin - CVE-2019-5870: Use-after-free in media. Reported by Guang Gong - CVE-2019-5871: Heap overflow in Skia. Reported by Anonymous - CVE-2019-5872: Use-after-free in Mojo. Reported by Zhe Jin - CVE-2019-5874: External URIs may trigger other browsers. Reported by James Lee - CVE-2019-5875: URL bar spoof. Reported by Khalil Zhani - CVE-2019-5876: Use-after-free in media. Reported by Man Yue Mo - CVE-2019-5877: Out-of-bounds access in V8. Reported by Guang Gong - CVE-2019-5878: Use-after-free in V8. Reported by Guang Gong - CVE-2019-5879: Extensions can read some local files. Reported by Jinseo Kim - CVE-2019-5880: SameSite cookie bypass. Reported by Jun Kokatsu - CVE-2019-13659: URL spoof. Reported by Lnyas Zhang - CVE-2019-13660: Full screen notification overlap. Reported by Wenxu Wu - CVE-2019-13661: Full screen notification spoof. Reported by Wenxu Wu - CVE-2019-13662: CSP bypass. Reported by David Erceg - CVE-2019-13663: IDN spoof. Reported by Lnyas Zhang - CVE-2019-13664: CSRF bypass. Reported by thomas "zemnmez" shadwell - CVE-2019-13665: Multiple file download protection bypass. Reported by Jun Kokatsu - CVE-2019-13666: Side channel using storage size estimate. Reported by Tom Van Goethem - CVE-2019-13667: URI bar spoof when using external app URIs. Reported by Khalil Zhani - CVE-2019-13668: Global window leak via console. Reported by David Erceg - CVE-2019-13669: HTTP authentication spoof. Reported by Khalil Zhani - CVE-2019-13670: V8 memory corruption in regex. Reported by Guang Gong - CVE-2019-13671: Dialog box fails to show origin. Reported by xisigr - CVE-2019-13673: Cross-origin information leak using devtools. Reported by David Erceg - CVE-2019-13674: IDN spoofing. Reported by Khalil Zhani - CVE-2019-13675: Extensions can be disabled by trailing slash. Reported by Jun Kokatsu - CVE-2019-13676: Google URI shown for certificate warning. Reported by Wenxu Wu - CVE-2019-13677: Chrome web store origin needs to be isolated. Reported by Jun Kokatsu - CVE-2019-13678: Download dialog spoofing. Reported by Ronni Skansing - CVE-2019-13679: User gesture needed for printing. Reported by Conrad Irwin - CVE-2019-13680: IP address spoofing to servers. Reported by Thijs Alkemade - CVE-2019-13681: Bypass on download restrictions. Reported by David Erceg - CVE-2019-13682: Site isolation bypass. Reported by Jun Kokatsu - CVE-2019-13683: Exceptions leaked by devtools. Reported by David Erceg - CVE-2019-13685: Use-after-free in UI. Reported by Khalil Zhani - CVE-2019-13686: Use-after-free in offline pages. Reported by Brendon - CVE-2019-13687: Use-after-free in media. Reported by Man Yue Mo - CVE-2019-13688: Use-after-free in media. Reported by Man Yue Mo Tiszka - CVE-2019-13691: Omnibox spoof. Reported by David Erceg - CVE-2019-13692: SOP bypass. Reported by Jun Kokatsu - CVE-2019-13693: Use-after-free in IndexedDB. Reported by Guang Gong - CVE-2019-13694: Use-after-free in WebRTC. Reported by banananapenguin - CVE-2019-13695: Use-after-free in audio. Reported by Man Yue Mo - CVE-2019-13696:
[Desktop-packages] [Bug 1855594] [NEW] Sync chromium 78.0.3904.108-1 (universe) from Debian unstable (main)
You have been subscribed to a public bug: Please sync chromium 78.0.3904.108-1 (universe) from Debian unstable (main) Now that the other chromium-browser source package in Ubuntu is just a transitional dummy package to the chromium snap, I guess we can now sync the Debian chromium package. This gives the community a chance to maintain a deb chromium package in Ubuntu independent from the snap one. All changelog entries: chromium (78.0.3904.108-1) unstable; urgency=medium * New upstream security release. - CVE-2019-13723: Use-after-free in Bluetooth. Reported by Yuxiang Li - CVE-2019-13724: Out-of-bounds in Bluetooth. Reported by Yuxiang Li * Disable vaapi on armhf (closes: #944627). -- Michael Gilbert Wed, 20 Nov 2019 23:46:06 + chromium (78.0.3904.97-1) unstable; urgency=medium * New upstream security release. * Enable vaapi (closes: #940074). * Fix crash during profile manager shutdown. * Drop libglewmx-dev build dependency (closes: #941050). -- Michael Gilbert Sat, 09 Nov 2019 03:33:52 + chromium (78.0.3904.87-1) unstable; urgency=medium * New upstream stable release. - CVE-2019-5869: Use-after-free in Blink. Reported by Zhe Jin - CVE-2019-5870: Use-after-free in media. Reported by Guang Gong - CVE-2019-5871: Heap overflow in Skia. Reported by Anonymous - CVE-2019-5872: Use-after-free in Mojo. Reported by Zhe Jin - CVE-2019-5874: External URIs may trigger other browsers. Reported by James Lee - CVE-2019-5875: URL bar spoof. Reported by Khalil Zhani - CVE-2019-5876: Use-after-free in media. Reported by Man Yue Mo - CVE-2019-5877: Out-of-bounds access in V8. Reported by Guang Gong - CVE-2019-5878: Use-after-free in V8. Reported by Guang Gong - CVE-2019-5879: Extensions can read some local files. Reported by Jinseo Kim - CVE-2019-5880: SameSite cookie bypass. Reported by Jun Kokatsu - CVE-2019-13659: URL spoof. Reported by Lnyas Zhang - CVE-2019-13660: Full screen notification overlap. Reported by Wenxu Wu - CVE-2019-13661: Full screen notification spoof. Reported by Wenxu Wu - CVE-2019-13662: CSP bypass. Reported by David Erceg - CVE-2019-13663: IDN spoof. Reported by Lnyas Zhang - CVE-2019-13664: CSRF bypass. Reported by thomas "zemnmez" shadwell - CVE-2019-13665: Multiple file download protection bypass. Reported by Jun Kokatsu - CVE-2019-13666: Side channel using storage size estimate. Reported by Tom Van Goethem - CVE-2019-13667: URI bar spoof when using external app URIs. Reported by Khalil Zhani - CVE-2019-13668: Global window leak via console. Reported by David Erceg - CVE-2019-13669: HTTP authentication spoof. Reported by Khalil Zhani - CVE-2019-13670: V8 memory corruption in regex. Reported by Guang Gong - CVE-2019-13671: Dialog box fails to show origin. Reported by xisigr - CVE-2019-13673: Cross-origin information leak using devtools. Reported by David Erceg - CVE-2019-13674: IDN spoofing. Reported by Khalil Zhani - CVE-2019-13675: Extensions can be disabled by trailing slash. Reported by Jun Kokatsu - CVE-2019-13676: Google URI shown for certificate warning. Reported by Wenxu Wu - CVE-2019-13677: Chrome web store origin needs to be isolated. Reported by Jun Kokatsu - CVE-2019-13678: Download dialog spoofing. Reported by Ronni Skansing - CVE-2019-13679: User gesture needed for printing. Reported by Conrad Irwin - CVE-2019-13680: IP address spoofing to servers. Reported by Thijs Alkemade - CVE-2019-13681: Bypass on download restrictions. Reported by David Erceg - CVE-2019-13682: Site isolation bypass. Reported by Jun Kokatsu - CVE-2019-13683: Exceptions leaked by devtools. Reported by David Erceg - CVE-2019-13685: Use-after-free in UI. Reported by Khalil Zhani - CVE-2019-13686: Use-after-free in offline pages. Reported by Brendon - CVE-2019-13687: Use-after-free in media. Reported by Man Yue Mo - CVE-2019-13688: Use-after-free in media. Reported by Man Yue Mo Tiszka - CVE-2019-13691: Omnibox spoof. Reported by David Erceg - CVE-2019-13692: SOP bypass. Reported by Jun Kokatsu - CVE-2019-13693: Use-after-free in IndexedDB. Reported by Guang Gong - CVE-2019-13694: Use-after-free in WebRTC. Reported by banananapenguin - CVE-2019-13695: Use-after-free in audio. Reported by Man Yue Mo - CVE-2019-13696: Use-after-free in V8. Reported by Guang Gong - CVE-2019-13697: Cross-origin size leak. Reported by Luan Herrera - CVE-2019-13699: Use-after-free in media. Reported by Man Yue Mo - CVE-2019-13700: Buffer overrun in Blink. Reported by Man Yue Mo - CVE-2019-13701: URL spoof in navigation. Reported by David Erceg - CVE-2019-13702: Privilege elevation in Installer. Reported by Phillip Langlois and Edward Torkington - CVE-2019-13703: URL bar spoofing. Reported by Khalil Zhani
[Desktop-packages] [Bug 1855593] [NEW] /usr/lib/tracker/tracker-miner-fs:6:g_assertion_message:g_assertion_message_expr:file_tree_lookup:tracker_file_system_get_file:_insert_store_info
Public bug reported: The Ubuntu Error Tracker has been receiving reports about a problem regarding tracker-miners. This problem was most recently seen with package version 2.3.1-1, the problem page at https://errors.ubuntu.com/problem/3083afc6df2bc2d8300a561c1858a0db0f0d5e95 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. ** Affects: tracker-miners (Ubuntu) Importance: Undecided Status: New ** Tags: bionic cosmic disco eoan focal kylin-18.04 kylin-19.10 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to tracker-miners in Ubuntu. https://bugs.launchpad.net/bugs/1855593 Title: /usr/lib/tracker/tracker-miner- fs:6:g_assertion_message:g_assertion_message_expr:file_tree_lookup:tracker_file_system_get_file:_insert_store_info Status in tracker-miners package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding tracker-miners. This problem was most recently seen with package version 2.3.1-1, the problem page at https://errors.ubuntu.com/problem/3083afc6df2bc2d8300a561c1858a0db0f0d5e95 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tracker-miners/+bug/1855593/+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 1854954] Re: Black screen on login
Resolved, see here: https://devtalk.nvidia.com/default/topic/1067986/linux/nvidia- driver-340-017-gives-black-screen-after-login-on- ubuntu-19-10/post/5409430/#5409430 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-340 in Ubuntu. https://bugs.launchpad.net/bugs/1854954 Title: Black screen on login Status in nvidia-graphics-drivers-340 package in Ubuntu: New Bug description: I am running Ubuntu 19.10 with NVIDIA Geforce 310. Output of `lspci | grep "VGA"`: 01:00.0 VGA compatible controller: NVIDIA Corporation GT218 [GeForce 310] (rev a2) I installed Ubuntu from USB with "install third party graphics" enabled and auto login turned off. When the computer restarted, I get the Gnome login screen but after login its just a black screen. Once I get the black screen, the computer is unusable (cannot even open another TTY) and I have to hard reboot the system. However when I get to the login screen I can open TTY2 and then if I `sudo apt remove nvidia*` then I can restart and use Nouveau drivers. I have tried disabling Wayland but if I reinstall the drivers at any point using `sudo ubuntu-drivers autoinstall` then I have the same issue again ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: nvidia-340 (not installed) ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 Uname: Linux 5.3.0-24-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CurrentDesktop: GNOME Date: Tue Dec 3 14:35:23 2019 InstallationDate: Installed on 2019-12-03 (0 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: nvidia-graphics-drivers-340 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/1854954/+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 1853440] ShellJournal.txt
apport information ** Attachment added: "ShellJournal.txt" https://bugs.launchpad.net/bugs/1853440/+attachment/5310725/+files/ShellJournal.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/1853440 Title: Volume either 0 or 100% on Lenovo X1 Carbon G7 Status in gnome-shell package in Ubuntu: Incomplete Status in linux package in Ubuntu: Incomplete Bug description: Volume increasing or decreasing doesn't work. I can only toggle sound on (= 100%) and off (= 0%). What I found out is that the Master channel seems to have no effect for volume adjustments, but the PCM channel does. If the sound is muted, PCM is set to 0 and therefore the sound is toggled off, but when I increase the sound a bit, PCM jumps straight to 100, causing the speakers to be very load. I have attached alsa-info output. System environment: Pop!_OS 19.10 Release: 19.10 Alsa-Version: alsa-base: 1.0.25 Sound Card: HDA-Intel Codec: Realtek ALC285 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CurrentDesktop: pop:GNOME DisplayManager: gdm3 DistroRelease: Pop!_OS 19.10 Package: linux PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.3.0-22.24+system76~1573659475~19.10~26b2022-generic 5.3.7 RelatedPackageVersions: mutter-common 3.34.1+git20191107-1ubuntu1~19.10.1pop0~1573683812~19.10~50e928a Tags: third-party-packages eoan Uname: Linux 5.3.0-22-generic x86_64 UnreportableReason: This is not an official Pop!_OS package. Please remove any third party package and try again. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1853440/+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 1853440] GsettingsChanges.txt
apport information ** Attachment added: "GsettingsChanges.txt" https://bugs.launchpad.net/bugs/1853440/+attachment/5310722/+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/1853440 Title: Volume either 0 or 100% on Lenovo X1 Carbon G7 Status in gnome-shell package in Ubuntu: Incomplete Status in linux package in Ubuntu: Incomplete Bug description: Volume increasing or decreasing doesn't work. I can only toggle sound on (= 100%) and off (= 0%). What I found out is that the Master channel seems to have no effect for volume adjustments, but the PCM channel does. If the sound is muted, PCM is set to 0 and therefore the sound is toggled off, but when I increase the sound a bit, PCM jumps straight to 100, causing the speakers to be very load. I have attached alsa-info output. System environment: Pop!_OS 19.10 Release: 19.10 Alsa-Version: alsa-base: 1.0.25 Sound Card: HDA-Intel Codec: Realtek ALC285 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CurrentDesktop: pop:GNOME DisplayManager: gdm3 DistroRelease: Pop!_OS 19.10 Package: linux PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.3.0-22.24+system76~1573659475~19.10~26b2022-generic 5.3.7 RelatedPackageVersions: mutter-common 3.34.1+git20191107-1ubuntu1~19.10.1pop0~1573683812~19.10~50e928a Tags: third-party-packages eoan Uname: Linux 5.3.0-22-generic x86_64 UnreportableReason: This is not an official Pop!_OS package. Please remove any third party package and try again. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1853440/+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 1853440] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1853440/+attachment/5310724/+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/1853440 Title: Volume either 0 or 100% on Lenovo X1 Carbon G7 Status in gnome-shell package in Ubuntu: Incomplete Status in linux package in Ubuntu: Incomplete Bug description: Volume increasing or decreasing doesn't work. I can only toggle sound on (= 100%) and off (= 0%). What I found out is that the Master channel seems to have no effect for volume adjustments, but the PCM channel does. If the sound is muted, PCM is set to 0 and therefore the sound is toggled off, but when I increase the sound a bit, PCM jumps straight to 100, causing the speakers to be very load. I have attached alsa-info output. System environment: Pop!_OS 19.10 Release: 19.10 Alsa-Version: alsa-base: 1.0.25 Sound Card: HDA-Intel Codec: Realtek ALC285 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CurrentDesktop: pop:GNOME DisplayManager: gdm3 DistroRelease: Pop!_OS 19.10 Package: linux PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.3.0-22.24+system76~1573659475~19.10~26b2022-generic 5.3.7 RelatedPackageVersions: mutter-common 3.34.1+git20191107-1ubuntu1~19.10.1pop0~1573683812~19.10~50e928a Tags: third-party-packages eoan Uname: Linux 5.3.0-22-generic x86_64 UnreportableReason: This is not an official Pop!_OS package. Please remove any third party package and try again. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1853440/+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 1853440] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1853440/+attachment/5310723/+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/1853440 Title: Volume either 0 or 100% on Lenovo X1 Carbon G7 Status in gnome-shell package in Ubuntu: Incomplete Status in linux package in Ubuntu: Incomplete Bug description: Volume increasing or decreasing doesn't work. I can only toggle sound on (= 100%) and off (= 0%). What I found out is that the Master channel seems to have no effect for volume adjustments, but the PCM channel does. If the sound is muted, PCM is set to 0 and therefore the sound is toggled off, but when I increase the sound a bit, PCM jumps straight to 100, causing the speakers to be very load. I have attached alsa-info output. System environment: Pop!_OS 19.10 Release: 19.10 Alsa-Version: alsa-base: 1.0.25 Sound Card: HDA-Intel Codec: Realtek ALC285 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CurrentDesktop: pop:GNOME DisplayManager: gdm3 DistroRelease: Pop!_OS 19.10 Package: linux PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.3.0-22.24+system76~1573659475~19.10~26b2022-generic 5.3.7 RelatedPackageVersions: mutter-common 3.34.1+git20191107-1ubuntu1~19.10.1pop0~1573683812~19.10~50e928a Tags: third-party-packages eoan Uname: Linux 5.3.0-22-generic x86_64 UnreportableReason: This is not an official Pop!_OS package. Please remove any third party package and try again. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1853440/+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 1853440] Re: Volume either 0 or 100% on Lenovo X1 Carbon G7
apport information ** Tags added: apport-collected third-party-packages ** Description changed: Volume increasing or decreasing doesn't work. I can only toggle sound on (= 100%) and off (= 0%). What I found out is that the Master channel seems to have no effect for volume adjustments, but the PCM channel does. If the sound is muted, PCM is set to 0 and therefore the sound is toggled off, but when I increase the sound a bit, PCM jumps straight to 100, causing the speakers to be very load. I have attached alsa-info output. System environment: Pop!_OS 19.10 Release: 19.10 Alsa-Version: alsa-base: 1.0.25 Sound Card: HDA-Intel Codec: Realtek ALC285 + --- + ProblemType: Bug + ApportVersion: 2.20.11-0ubuntu8.2 + Architecture: amd64 + CurrentDesktop: pop:GNOME + DisplayManager: gdm3 + DistroRelease: Pop!_OS 19.10 + Package: linux + PackageArchitecture: amd64 + ProcVersionSignature: Ubuntu 5.3.0-22.24+system76~1573659475~19.10~26b2022-generic 5.3.7 + RelatedPackageVersions: mutter-common 3.34.1+git20191107-1ubuntu1~19.10.1pop0~1573683812~19.10~50e928a + Tags: third-party-packages eoan + Uname: Linux 5.3.0-22-generic x86_64 + UnreportableReason: This is not an official Pop!_OS package. Please remove any third party package and try again. + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm sudo + _MarkForUpload: True ** Attachment added: "Dependencies.txt" https://bugs.launchpad.net/bugs/1853440/+attachment/5310721/+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/1853440 Title: Volume either 0 or 100% on Lenovo X1 Carbon G7 Status in gnome-shell package in Ubuntu: Incomplete Status in linux package in Ubuntu: Incomplete Bug description: Volume increasing or decreasing doesn't work. I can only toggle sound on (= 100%) and off (= 0%). What I found out is that the Master channel seems to have no effect for volume adjustments, but the PCM channel does. If the sound is muted, PCM is set to 0 and therefore the sound is toggled off, but when I increase the sound a bit, PCM jumps straight to 100, causing the speakers to be very load. I have attached alsa-info output. System environment: Pop!_OS 19.10 Release: 19.10 Alsa-Version: alsa-base: 1.0.25 Sound Card: HDA-Intel Codec: Realtek ALC285 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CurrentDesktop: pop:GNOME DisplayManager: gdm3 DistroRelease: Pop!_OS 19.10 Package: linux PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.3.0-22.24+system76~1573659475~19.10~26b2022-generic 5.3.7 RelatedPackageVersions: mutter-common 3.34.1+git20191107-1ubuntu1~19.10.1pop0~1573683812~19.10~50e928a Tags: third-party-packages eoan Uname: Linux 5.3.0-22-generic x86_64 UnreportableReason: This is not an official Pop!_OS package. Please remove any third party package and try again. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1853440/+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 1855591] [NEW] Option --version displays UNKNOWN
Public bug reported: One would expect to see rygel's version when calling it with the --version option. Instead "UNKNOWN" is displayed ``` # rygel --version Rygel UNKNOWN ``` -- # lsb_release -rd Description:Ubuntu 19.10 Release:19.10 # apt-cache policy rygel rygel: Installed: 0.38.1-2ubuntu3.3 Candidate: 0.38.1-2ubuntu3.3 Version table: *** 0.38.1-2ubuntu3.3 500 500 http://ro-mirrors.evowise.com/ubuntu eoan-updates/main amd64 Packages 500 http://ro-mirrors.evowise.com/ubuntu eoan-security/main amd64 Packages 100 /var/lib/dpkg/status 0.38.1-2ubuntu3 500 500 http://ro-mirrors.evowise.com/ubuntu eoan/main amd64 Packages ** Affects: rygel (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to rygel in Ubuntu. https://bugs.launchpad.net/bugs/1855591 Title: Option --version displays UNKNOWN Status in rygel package in Ubuntu: New Bug description: One would expect to see rygel's version when calling it with the --version option. Instead "UNKNOWN" is displayed ``` # rygel --version Rygel UNKNOWN ``` -- # lsb_release -rd Description:Ubuntu 19.10 Release:19.10 # apt-cache policy rygel rygel: Installed: 0.38.1-2ubuntu3.3 Candidate: 0.38.1-2ubuntu3.3 Version table: *** 0.38.1-2ubuntu3.3 500 500 http://ro-mirrors.evowise.com/ubuntu eoan-updates/main amd64 Packages 500 http://ro-mirrors.evowise.com/ubuntu eoan-security/main amd64 Packages 100 /var/lib/dpkg/status 0.38.1-2ubuntu3 500 500 http://ro-mirrors.evowise.com/ubuntu eoan/main amd64 Packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rygel/+bug/1855591/+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 1736011] Re: CRITICAL: Unable to create a DBus proxy for GnomeScreensaver: Error calling StartServiceByName for org.gnome.ScreenSaver: GDBus.Error:org.freedesktop.DBus.Error.Sp
So I still see this bug on several machines here that runs Ubuntu 20.04 with Gnome Flashback. And I suspects this bug causes Updatemanager to fail sometimes when the system autostarts it while the screensaver is activated. (The program is running minimized, but unable to unminimize. You have to close/kill it and manually start it) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-session in Ubuntu. https://bugs.launchpad.net/bugs/1736011 Title: CRITICAL: Unable to create a DBus proxy for GnomeScreensaver: Error calling StartServiceByName for org.gnome.ScreenSaver: GDBus.Error:org.freedesktop.DBus.Error.Spawn.ChildExited: Process org.gnome.ScreenSaver exited with status 1 Status in gnome-session package in Ubuntu: Confirmed Bug description: That error is logged: org.gnome.ScreenSaver[1081]: Unable to init server: Could not connect: Connection refused then: gnome-session[895]: gnome-session-binary[895]: CRITICAL: Unable to create a DBus proxy for GnomeScreensaver: Error calling StartServiceByName for org.gnome.ScreenSaver: GDBus.Error:org.freedesktop.DBus.Error.Spawn.ChildExited: Process org.gnome.ScreenSaver exited with status 1 oem@ubuntu:~$ localectl System Locale: LANG=en_US.UTF-8 VC Keymap: n/a X11 Layout: fr X11 Model: pc105 X11 Variant: oss So, with googling help (https://bbs.archlinux.org/viewtopic.php?id=180103), i've edited /etc/locale-gen (as user) and uncommented the line: fr_FR.UTF-8 and then ran 'sudo locale-gen' and finally rebooted. But the error is still logged after reboot: either i need to set also 'VC Keymap', but how ?, or it is related to the vte version actually used (and need an upgrade) (https://bugs.launchpad.net/ubuntu/+source/vte2.91/+bug/1721412) ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-session 3.26.1-0ubuntu7 ProcVersionSignature: Ubuntu 4.13.0-18.21-generic 4.13.13 Uname: Linux 4.13.0-18-generic x86_64 ApportVersion: 2.20.8-0ubuntu2 Architecture: amd64 CurrentDesktop: GNOME Date: Sun Dec 3 17:17:45 2017 EcryptfsInUse: Yes ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-session UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1736011/+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 1855584] [NEW] pulseaudio: sometimes generate eternal white noise even reboot to Windows OS
Public bug reported: This problem seems begin from ubuntu 19.04. Sometimes after login, headphone outputs white noise only, speaker does not work. Nothing can play music with the noise. The noise is impossible to stop except POWEROFF the PC. Rebooting cannot stop it, the noise keeps even reboot into Windows OS. In Windows OS, headphone still white noise, after unplugging headphone, the speaker does not work, too. It works fine in Windows OS. If I remove pulseaudio, only use ALSA. It also works stable. (But now... firefox do not support ALSA, chromium-snap do not support ALSA too...) It seems pulseaudio killed the sound card... The problem appears randomly, I do not know how to reproduce. sorry... ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.0-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-0ubuntu13 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: aya5434 F pulseaudio /dev/snd/controlC0: aya5434 F pulseaudio Date: Sun Dec 8 19:51:02 2019 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/16/2018 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 1.07.05RHZX1 dmi.board.asset.tag: Tag 12345 dmi.board.name: NH50_70_55_58_ED,EDQ dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.modalias: dmi:bvnINSYDECorp.:bvr1.07.05RHZX1:bd11/16/2018:svnHASEEComputer:pnNH50_70_55_58_ED,EDQ:pvrNotApplicable:rvnNotebook:rnNH50_70_55_58_ED,EDQ:rvrNotApplicable:cvnNotebook:ct10:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: NH50_70_55_58_ED,EDQ dmi.product.sku: Not Applicable dmi.product.version: Not Applicable dmi.sys.vendor: HASEE Computer ** Affects: pulseaudio (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1855584 Title: pulseaudio: sometimes generate eternal white noise even reboot to Windows OS Status in pulseaudio package in Ubuntu: New Bug description: This problem seems begin from ubuntu 19.04. Sometimes after login, headphone outputs white noise only, speaker does not work. Nothing can play music with the noise. The noise is impossible to stop except POWEROFF the PC. Rebooting cannot stop it, the noise keeps even reboot into Windows OS. In Windows OS, headphone still white noise, after unplugging headphone, the speaker does not work, too. It works fine in Windows OS. If I remove pulseaudio, only use ALSA. It also works stable. (But now... firefox do not support ALSA, chromium-snap do not support ALSA too...) It seems pulseaudio killed the sound card... The problem appears randomly, I do not know how to reproduce. sorry... ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.0-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-0ubuntu13 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: aya5434 F pulseaudio /dev/snd/controlC0: aya5434 F pulseaudio Date: Sun Dec 8 19:51:02 2019 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/16/2018 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 1.07.05RHZX1 dmi.board.asset.tag: Tag 12345 dmi.board.name: NH50_70_55_58_ED,EDQ dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.modalias: dmi:bvnINSYDECorp.:bvr1.07.05RHZX1:bd11/16/2018:svnHASEEComputer:pnNH50_70_55_58_ED,EDQ:pvrNotApplicable:rvnNotebook:rnNH50_70_55_58_ED,EDQ:rvrNotApplicable:cvnNotebook:ct10:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: NH50_70_55_58_ED,EDQ dmi.product.sku: Not Applicable dmi.product.version: Not Applicable dmi.sys.vendor: HASEE Computer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1855584/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe :
[Desktop-packages] [Bug 1855586] [NEW] Feature request: allow toggling between airplane mode/bluetooth/wifi/both
Public bug reported: When pressing the monitor config key, one can switch between internal/external/mirror/join It would be nice to have something analagous for airplane/wifi/bluetooth/both, maybe after a long press ** Affects: gnome-control-center (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1855586 Title: Feature request: allow toggling between airplane mode/bluetooth/wifi/both Status in gnome-control-center package in Ubuntu: New Bug description: When pressing the monitor config key, one can switch between internal/external/mirror/join It would be nice to have something analagous for airplane/wifi/bluetooth/both, maybe after a long press To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1855586/+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 1855583] [NEW] blinking kubuntu logo
Public bug reported: Not able to boot ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 5.0.0-37.40~18.04.1-generic 5.0.21 Uname: Linux 5.0.0-37-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: KDE Date: Sun Dec 8 17:23:00 2019 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: I just need to know a workaround GraphicsCard: Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a06] (rev 0b) (prog-if 00 [VGA controller]) Subsystem: Dell Haswell-ULT Integrated Graphics Controller [1028:0651] InstallationDate: Installed on 2019-11-27 (10 days ago) InstallationMedia: Kubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) MachineType: Dell Inc. Inspiron 3542 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-37-generic root=UUID=e11edfe1-8c7e-4e23-bdd2-9f56d67cda03 ro quiet splash SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/13/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: A12 dmi.board.name: 0FKWR5 dmi.board.vendor: Dell Inc. dmi.board.version: A12 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvrA12:bd05/13/2016:svnDellInc.:pnInspiron3542:pvrNotSpecified:rvnDellInc.:rn0FKWR5:rvrA12:cvnDellInc.:ct8:cvrNotSpecified: dmi.product.name: Inspiron 3542 dmi.product.sku: 0651 dmi.product.version: Not Specified dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97-1ubuntu1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.8-0ubuntu0~18.04.3 version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.8-0ubuntu0~18.04.3 version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic 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/1855583 Title: blinking kubuntu logo Status in xorg package in Ubuntu: New Bug description: Not able to boot ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 5.0.0-37.40~18.04.1-generic 5.0.21 Uname: Linux 5.0.0-37-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: KDE Date: Sun Dec 8 17:23:00 2019 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: I just need to know a workaround GraphicsCard: Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a06] (rev 0b) (prog-if 00 [VGA controller]) Subsystem: Dell Haswell-ULT Integrated Graphics Controller [1028:0651] InstallationDate: Installed on 2019-11-27 (10 days ago) InstallationMedia: Kubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) MachineType: Dell Inc. Inspiron 3542 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-37-generic root=UUID=e11edfe1-8c7e-4e23-bdd2-9f56d67cda03 ro quiet splash SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/13/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: A12 dmi.board.name: 0FKWR5 dmi.board.vendor: Dell Inc. dmi.board.version: A12 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvrA12:bd05/13/2016:svnDellInc.:pnInspiron3542:pvrNotSpecified:rvnDellInc.:rn0FKWR5:rvrA12:cvnDellInc.:ct8:cvrNotSpecified: dmi.product.name: Inspiron 3542 dmi.product.sku: 0651 dmi.product.version: Not Specified dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97-1ubuntu1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.8-0ubuntu0~18.04.3 version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.8-0ubuntu0~18.04.3 version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1855583/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe :
[Desktop-packages] [Bug 1855581] [NEW] cannot select menu entry via keyboard
Public bug reported: when I hit F10 and then start cursors down I expect some kind of visual confirmation of the menu entry I am to activate, but there is nothing highlighted. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: evince 3.28.4-0ubuntu1.2 ProcVersionSignature: Ubuntu 4.15.0-1065.75-oem 4.15.18 Uname: Linux 4.15.0-1065-oem x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Dec 8 11:50:26 2019 DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-bionic-amd64-20180608-47+beaver-three-eyed-raven+X92 InstallationDate: Installed on 2019-11-16 (22 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20180608-09:38 SourcePackage: evince UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: evince (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- 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/1855581 Title: cannot select menu entry via keyboard Status in evince package in Ubuntu: New Bug description: when I hit F10 and then start cursors down I expect some kind of visual confirmation of the menu entry I am to activate, but there is nothing highlighted. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: evince 3.28.4-0ubuntu1.2 ProcVersionSignature: Ubuntu 4.15.0-1065.75-oem 4.15.18 Uname: Linux 4.15.0-1065-oem x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Dec 8 11:50:26 2019 DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-bionic-amd64-20180608-47+beaver-three-eyed-raven+X92 InstallationDate: Installed on 2019-11-16 (22 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20180608-09:38 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/1855581/+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 1855580] [NEW] cannot multi select files in icon view
Public bug reported: open Nautilus left-click a file using keyboard, I try SHIFT + cursor to extend selection, but that doesn't work keyboard works fine in list view mode. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: nautilus 1:3.26.4-0~ubuntu18.04.4 ProcVersionSignature: Ubuntu 4.15.0-1065.75-oem 4.15.18 Uname: Linux 4.15.0-1065-oem x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Dec 8 11:43:45 2019 DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-bionic-amd64-20180608-47+beaver-three-eyed-raven+X92 InstallationDate: Installed on 2019-11-16 (22 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20180608-09:38 SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: ** Affects: nautilus (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- 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/1855580 Title: cannot multi select files in icon view Status in nautilus package in Ubuntu: New Bug description: open Nautilus left-click a file using keyboard, I try SHIFT + cursor to extend selection, but that doesn't work keyboard works fine in list view mode. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: nautilus 1:3.26.4-0~ubuntu18.04.4 ProcVersionSignature: Ubuntu 4.15.0-1065.75-oem 4.15.18 Uname: Linux 4.15.0-1065-oem x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Dec 8 11:43:45 2019 DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-bionic-amd64-20180608-47+beaver-three-eyed-raven+X92 InstallationDate: Installed on 2019-11-16 (22 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20180608-09:38 SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1855580/+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 1853374] Re: pulseaudio disables GP107GL output every so often
Just in case it was a driver issue (affecting two different chipsets...) I can report that it's still behaving like this with version 5.3.0-24.26 of the kernel. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1853374 Title: pulseaudio disables GP107GL output every so often Status in pulseaudio package in Ubuntu: New Bug description: Since upgrading to 19.10, the sound output on this PC stops. Looking at the volume control's 'sound settings', the GP107GL High Definition Audio Controller (digital stereo HMDI 2 output) is disabled. Doing pluseaudio -k restores it. Possibly relevant from syslog: Nov 18 07:48:51 example kernel: [42392.063211] snd_hda_codec_hdmi hdaudioC0D0: HDMI: invalid ELD data byte 3 Nov 18 07:51:04 example kernel: [42524.900935] snd_hda_codec_hdmi hdaudioC0D0: HDMI: invalid ELD data byte 2 Nov 18 08:05:23 example kernel: [43383.465647] snd_hda_codec_hdmi hdaudioC0D0: HDMI: invalid ELD data byte 3 Nov 18 09:34:08 example kernel: [48708.806452] snd_hda_codec_hdmi hdaudioC0D0: HDMI: invalid ELD data byte 4 Nov 18 13:32:46 example kernel: [63026.605375] snd_hda_codec_hdmi hdaudioC0D0: HDMI: invalid ELD data byte 3 Nov 18 13:34:13 example kernel: [63114.281953] snd_hda_codec_hdmi hdaudioC0D0: HDMI: invalid ELD data byte 3 Nov 18 13:34:40 example kernel: [63141.350110] snd_hda_codec_hdmi hdaudioC0D0: HDMI: invalid ELD data byte 2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1853374/+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 1845046] Re: Bluetooth headphones/speaker default to low quality headset mode and fails to switch to A2DP when selected
I have the same problem with Sony wh-1000xm3 and Ubuntu 19.10. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1845046 Title: Bluetooth headphones/speaker default to low quality headset mode and fails to switch to A2DP when selected Status in bluez package in Ubuntu: Confirmed Status in gnome-control-center package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Confirmed Bug description: Whenever I turn on my headphones theyll connect to my computer but im able to hear the input audio from my microphone and low quality output audio. I have to disconnect the headphones in the bluetooth devices and reconnect for it to fix the problem. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: pulseaudio 1:11.1-1ubuntu7.2 ProcVersionSignature: Ubuntu 5.0.0-29.31~18.04.1-generic 5.0.21 Uname: Linux 5.0.0-29-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: litleck1398 F pulseaudio /dev/snd/controlC0: litleck1398 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Mon Sep 23 17:07:59 2019 InstallationDate: Installed on 2019-09-22 (0 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio Symptom: audio Symptom_Card: WH-1000XM3 Symptom_Type: High background noise, or volume is too low Title: [WH-1000XM3, playback] Background noise or low volume UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/12/2019 dmi.bios.vendor: Alienware dmi.bios.version: 1.0.19 dmi.board.name: 01NYPT dmi.board.vendor: Alienware dmi.board.version: A00 dmi.chassis.type: 3 dmi.chassis.vendor: Alienware dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnAlienware:bvr1.0.19:bd02/12/2019:svnAlienware:pnAlienwareAuroraR5:pvr1.0.19:rvnAlienware:rn01NYPT:rvrA00:cvnAlienware:ct3:cvrNotSpecified: dmi.product.family: Alienware dmi.product.name: Alienware Aurora R5 dmi.product.sku: 0729 dmi.product.version: 1.0.19 dmi.sys.vendor: Alienware To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1845046/+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 1851528] Re: JS ERROR: TypeError: malformed UTF-8 character sequence at offset 0 and segfault in _filterKeybinding:windowManager.js:1825 from invoke_handler() from process_even
Unfortunately I was unable to reproduce the bug. -- 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/1851528 Title: JS ERROR: TypeError: malformed UTF-8 character sequence at offset 0 and segfault in _filterKeybinding:windowManager.js:1825 from invoke_handler() from process_event() from process_special_modifier_key() Status in GNOME Shell: New Status in gnome-shell package in Ubuntu: Triaged Bug description: I was trying to bring my Firefox window to front by pressing Super+2 (it's my second pinned launcher), and gnome-shell crashed. journalctl shows this: lapkr. 06 16:38:58 blynas gnome-shell[3417]: JS ERROR: TypeError: malformed UTF-8 character sequence at offset 0 _filterKeybinding@resource:///org/gnome/shell/ui/windowManager.js:1825:43 lapkr. 06 16:38:58 blynas gnome-shell[3417]: GNOME Shell crashed with signal 11 lapkr. 06 16:38:58 blynas gnome-shell[3417]: == Stack trace for context 0x56068fb2e3e0 == I have a crash dump in /var/crash/, but apport thinks it's unreportable because my rygel was out of date. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1851528/+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 1855576] [NEW] Changing character case when renaming doesn't persist
Public bug reported: Ubuntu 19.10 nautilus version: 1:3.34.1-1ubuntu1 Upon pressing F2 to rename a file, if delete one of the characters and replace it with the same character, but a different case, and you click rename, the changes should save. Instead they get discarded E.g. renaming foo.c -> Foo.c keeps it as foo.c instead of renaming it to Foo.c ProblemType: Bug DistroRelease: Ubuntu 19.10 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-0ubuntu8.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Dec 8 11:16:24 2019 GsettingsChanges: b'org.gnome.nautilus.window-state' b'sidebar-width' b'187' b'org.gnome.nautilus.window-state' b'initial-size' b'(655, 700)' b'org.gnome.nautilus.window-state' b'maximized' b'true' InstallationDate: Installed on 2019-10-30 (38 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) ProcEnviron: LANGUAGE=en_ZA:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_ZA.UTF-8 SHELL=/bin/bash SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: ** Affects: nautilus (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug eoan -- 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/1855576 Title: Changing character case when renaming doesn't persist Status in nautilus package in Ubuntu: New Bug description: Ubuntu 19.10 nautilus version: 1:3.34.1-1ubuntu1 Upon pressing F2 to rename a file, if delete one of the characters and replace it with the same character, but a different case, and you click rename, the changes should save. Instead they get discarded E.g. renaming foo.c -> Foo.c keeps it as foo.c instead of renaming it to Foo.c ProblemType: Bug DistroRelease: Ubuntu 19.10 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-0ubuntu8.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Dec 8 11:16:24 2019 GsettingsChanges: b'org.gnome.nautilus.window-state' b'sidebar-width' b'187' b'org.gnome.nautilus.window-state' b'initial-size' b'(655, 700)' b'org.gnome.nautilus.window-state' b'maximized' b'true' InstallationDate: Installed on 2019-10-30 (38 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) ProcEnviron: LANGUAGE=en_ZA:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_ZA.UTF-8 SHELL=/bin/bash SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1855576/+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 1855570] Re: xdg-desktop-por: Could not get window list: Timeout was reached
** Attachment added: "Ubuntu 20.04 Xorg 0 log by FvB" https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1855570/+attachment/5310649/+files/Xorg.0.log ** Description changed: - Just installed Ubuntu 20.04 (for testing purpose only): While booting - there is no Gnome showing up. Checking syslog there are these messages - ... + Just freshly installed Ubuntu 20.04 on a bare metal Desktop (for testing + purpose only): While booting there is no Gnome showing up. Checking + syslog there are these messages ... Dec 8 07:51:43 deblnxsrv100 xdg-desktop-por[1287]: Failed to get application states: GDBus.Error:org.freedesktop.portal.Error.Failed: Could not get window list: Timeout was reached Dec 8 07:51:43 deblnxsrv100 at-spi-bus-launcher[1245]: X connection to :0 broken (explicit kill or server shutdown). Dec 8 07:51:44 deblnxsrv100 gsd-wacom[1522]: gsd-wacom: Fatal IO error 11 (Resource temporarily unavailable) on X server :0. Dec 8 07:51:44 deblnxsrv100 gsd-xsettings[1538]: gsd-xsettings: Fatal IO error 11 (Resource temporarily unavailable) on X server :0. Dec 8 07:51:44 deblnxsrv100 systemd[]: gsd-xsettings.service: Main process exited, code=exited, status=1/FAILURE Dec 8 07:51:44 deblnxsrv100 systemd[]: gsd-xsettings.service: Failed with result 'exit-code'. Dec 8 07:51:44 deblnxsrv100 systemd[]: gsd-xsettings.service: Triggering OnFailure= dependencies. Dec 8 07:51:44 deblnxsrv100 systemd[]: Stopped target GNOME XSettings. Dec 8 07:51:44 deblnxsrv100 systemd[]: Started GNOME Session Failed lockdown screen (user). Dec 8 07:51:44 deblnxsrv100 systemd[]: Reached target GNOME Session Failed. Dec 8 07:51:44 deblnxsrv100 update-notifier[1815]: update-notifier: Fatal IO error 11 (Resource temporarily unavailable) on X server :0. ** Description changed: - Just freshly installed Ubuntu 20.04 on a bare metal Desktop (for testing - purpose only): While booting there is no Gnome showing up. Checking - syslog there are these messages ... + Just freshly installed Ubuntu 20.04 on a bare metal Desktop disk + partition (for testing purpose only): While booting there is no Gnome + showing up. Checking syslog there are these messages ... Dec 8 07:51:43 deblnxsrv100 xdg-desktop-por[1287]: Failed to get application states: GDBus.Error:org.freedesktop.portal.Error.Failed: Could not get window list: Timeout was reached Dec 8 07:51:43 deblnxsrv100 at-spi-bus-launcher[1245]: X connection to :0 broken (explicit kill or server shutdown). Dec 8 07:51:44 deblnxsrv100 gsd-wacom[1522]: gsd-wacom: Fatal IO error 11 (Resource temporarily unavailable) on X server :0. Dec 8 07:51:44 deblnxsrv100 gsd-xsettings[1538]: gsd-xsettings: Fatal IO error 11 (Resource temporarily unavailable) on X server :0. Dec 8 07:51:44 deblnxsrv100 systemd[]: gsd-xsettings.service: Main process exited, code=exited, status=1/FAILURE Dec 8 07:51:44 deblnxsrv100 systemd[]: gsd-xsettings.service: Failed with result 'exit-code'. Dec 8 07:51:44 deblnxsrv100 systemd[]: gsd-xsettings.service: Triggering OnFailure= dependencies. Dec 8 07:51:44 deblnxsrv100 systemd[]: Stopped target GNOME XSettings. Dec 8 07:51:44 deblnxsrv100 systemd[]: Started GNOME Session Failed lockdown screen (user). Dec 8 07:51:44 deblnxsrv100 systemd[]: Reached target GNOME Session Failed. Dec 8 07:51:44 deblnxsrv100 update-notifier[1815]: update-notifier: Fatal IO error 11 (Resource temporarily unavailable) on X server :0. ** Description changed: Just freshly installed Ubuntu 20.04 on a bare metal Desktop disk partition (for testing purpose only): While booting there is no Gnome - showing up. Checking syslog there are these messages ... + showing up. Checking syslog for error's there are these messages ... Dec 8 07:51:43 deblnxsrv100 xdg-desktop-por[1287]: Failed to get application states: GDBus.Error:org.freedesktop.portal.Error.Failed: Could not get window list: Timeout was reached Dec 8 07:51:43 deblnxsrv100 at-spi-bus-launcher[1245]: X connection to :0 broken (explicit kill or server shutdown). Dec 8 07:51:44 deblnxsrv100 gsd-wacom[1522]: gsd-wacom: Fatal IO error 11 (Resource temporarily unavailable) on X server :0. Dec 8 07:51:44 deblnxsrv100 gsd-xsettings[1538]: gsd-xsettings: Fatal IO error 11 (Resource temporarily unavailable) on X server :0. Dec 8 07:51:44 deblnxsrv100 systemd[]: gsd-xsettings.service: Main process exited, code=exited, status=1/FAILURE Dec 8 07:51:44 deblnxsrv100 systemd[]: gsd-xsettings.service: Failed with result 'exit-code'. Dec 8 07:51:44 deblnxsrv100 systemd[]: gsd-xsettings.service: Triggering OnFailure= dependencies. Dec 8 07:51:44 deblnxsrv100 systemd[]: Stopped target GNOME XSettings. Dec 8 07:51:44 deblnxsrv100 systemd[]: Started GNOME Session Failed lockdown screen (user). Dec 8 07:51:44 deblnxsrv100 systemd[]: Reached target GNOME Session
[Desktop-packages] [Bug 1855570] Re: xdg-desktop-por: Could not get window list: Timeout was reached
** Attachment added: "Ubuntu 20.04 gpu-manager by FvB" https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1855570/+attachment/5310648/+files/gpu-manager.log -- 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/1855570 Title: xdg-desktop-por: Could not get window list: Timeout was reached Status in xorg package in Ubuntu: New Bug description: Just freshly installed Ubuntu 20.04 on a bare metal Desktop disk partition (for testing purpose only): While booting there is no Gnome showing up. Checking syslog for error's there are these messages ... Dec 8 07:51:43 deblnxsrv100 xdg-desktop-por[1287]: Failed to get application states: GDBus.Error:org.freedesktop.portal.Error.Failed: Could not get window list: Timeout was reached Dec 8 07:51:43 deblnxsrv100 at-spi-bus-launcher[1245]: X connection to :0 broken (explicit kill or server shutdown). Dec 8 07:51:44 deblnxsrv100 gsd-wacom[1522]: gsd-wacom: Fatal IO error 11 (Resource temporarily unavailable) on X server :0. Dec 8 07:51:44 deblnxsrv100 gsd-xsettings[1538]: gsd-xsettings: Fatal IO error 11 (Resource temporarily unavailable) on X server :0. Dec 8 07:51:44 deblnxsrv100 systemd[]: gsd-xsettings.service: Main process exited, code=exited, status=1/FAILURE Dec 8 07:51:44 deblnxsrv100 systemd[]: gsd-xsettings.service: Failed with result 'exit-code'. Dec 8 07:51:44 deblnxsrv100 systemd[]: gsd-xsettings.service: Triggering OnFailure= dependencies. Dec 8 07:51:44 deblnxsrv100 systemd[]: Stopped target GNOME XSettings. Dec 8 07:51:44 deblnxsrv100 systemd[]: Started GNOME Session Failed lockdown screen (user). Dec 8 07:51:44 deblnxsrv100 systemd[]: Reached target GNOME Session Failed. Dec 8 07:51:44 deblnxsrv100 update-notifier[1815]: update-notifier: Fatal IO error 11 (Resource temporarily unavailable) on X server :0. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1855570/+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
