[Desktop-packages] [Bug 1870833] Re: pulseaudio crashed with SIGABRT in pa_alsa_ucm_add_profile_set() from module_alsa_card_LTX_pa__init()
Besides this Whoopsie catch of pulseaudio crashing, the result is that audio doesn't work at all on the system. Settings -> Sound shows no options for the output or input devices, the "Test" button says to click on a speaker to test it but then shows zero speakers, just the icon of a person, etc. I am happy to try daily builds or patched versions on this motherboard if someone wants to try to debug it. (Also, comment #7 says "tracking in (url)" but I as an ordinary user don't seem to have access to that URL. It just shows me a graph of all error reports for all releases. So I can't see if y'all have a workaround that I could try, or want people who get this error to run some diagnostic or anything...) -- 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/1870833 Title: pulseaudio crashed with SIGABRT in pa_alsa_ucm_add_profile_set() from module_alsa_card_LTX_pa__init() Status in PulseAudio: New Status in pulseaudio package in Ubuntu: Triaged Bug description: https://errors.ubuntu.com/problem/468f63163a916557999ec0a7aac3459fa638a2d1 --- gigabyte X370 Gaming 5 main board, Ryzen 1600 16gb ram. I get a black screen on boot of clean install of the Beta 20.04. realised however it has booted, hitting enter then Password then Enter and desktop loads.. Get error concerning Pulse audio crashing. ProblemType: Crash DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu22 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC1', '/dev/snd/hwC1D1', '/dev/snd/hwC1D0', '/dev/snd/pcmC1D4c', '/dev/snd/pcmC1D4p', '/dev/snd/pcmC1D2c', '/dev/snd/pcmC1D1p', '/dev/snd/pcmC1D0c', '/dev/snd/pcmC1D0p', '/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D11p', '/dev/snd/pcmC0D10p', '/dev/snd/pcmC0D9p', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CrashCounter: 1 Date: Sat Apr 4 20:13:21 2020 ExecutablePath: /usr/bin/pulseaudio InstallationDate: Installed on 2020-04-04 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) ProcCmdline: /usr/bin/pulseaudio --daemonize=no ProcEnviron: LANG=en_GB.UTF-8 LANGUAGE=en_GB:en PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Signal: 6 SourcePackage: pulseaudio StacktraceTop: pa_alsa_ucm_add_profile_set () from /usr/lib/pulse-13.99.1/modules/libalsa-util.so module_alsa_card_LTX_pa__init () from /usr/lib/pulse-13.99.1/modules/module-alsa-card.so pa_module_load () from /usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecore-13.99.so ?? () from /usr/lib/pulse-13.99.1/modules/module-udev-detect.so ?? () from /usr/lib/pulse-13.99.1/modules/module-udev-detect.so Title: pulseaudio crashed with SIGABRT in pa_alsa_ucm_add_profile_set() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo dmi.bios.date: 08/01/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F42b dmi.board.asset.tag: Default string dmi.board.name: AX370-Gaming 5 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF42b:bd08/01/2019:svnGigabyteTechnologyCo.,Ltd.:pnAX370-Gaming5:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnAX370-Gaming5:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: AX370-Gaming 5 dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. separator: To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/1870833/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1870833] Re: pulseaudio crashed with SIGABRT in pa_alsa_ucm_add_profile_set() from module_alsa_card_LTX_pa__init()
Just for fun I tried to start it manually. $ pulseaudio --start --log-level=debug --verbose D: [pulseaudio] conf-parser.c: Parsing configuration file '/etc/pulse/client.conf' D: [pulseaudio] conf-parser.c: Failed to open configuration file '/etc/pulse/client.conf.d/01-enable-autospawn.conf': No such file or directory E: [pulseaudio] main.c: Daemon startup failed. And whoopsie pops up with the same old crash. -- 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/1870833 Title: pulseaudio crashed with SIGABRT in pa_alsa_ucm_add_profile_set() from module_alsa_card_LTX_pa__init() Status in PulseAudio: New Status in pulseaudio package in Ubuntu: Triaged Bug description: https://errors.ubuntu.com/problem/468f63163a916557999ec0a7aac3459fa638a2d1 --- gigabyte X370 Gaming 5 main board, Ryzen 1600 16gb ram. I get a black screen on boot of clean install of the Beta 20.04. realised however it has booted, hitting enter then Password then Enter and desktop loads.. Get error concerning Pulse audio crashing. ProblemType: Crash DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu22 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC1', '/dev/snd/hwC1D1', '/dev/snd/hwC1D0', '/dev/snd/pcmC1D4c', '/dev/snd/pcmC1D4p', '/dev/snd/pcmC1D2c', '/dev/snd/pcmC1D1p', '/dev/snd/pcmC1D0c', '/dev/snd/pcmC1D0p', '/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D11p', '/dev/snd/pcmC0D10p', '/dev/snd/pcmC0D9p', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CrashCounter: 1 Date: Sat Apr 4 20:13:21 2020 ExecutablePath: /usr/bin/pulseaudio InstallationDate: Installed on 2020-04-04 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) ProcCmdline: /usr/bin/pulseaudio --daemonize=no ProcEnviron: LANG=en_GB.UTF-8 LANGUAGE=en_GB:en PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Signal: 6 SourcePackage: pulseaudio StacktraceTop: pa_alsa_ucm_add_profile_set () from /usr/lib/pulse-13.99.1/modules/libalsa-util.so module_alsa_card_LTX_pa__init () from /usr/lib/pulse-13.99.1/modules/module-alsa-card.so pa_module_load () from /usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecore-13.99.so ?? () from /usr/lib/pulse-13.99.1/modules/module-udev-detect.so ?? () from /usr/lib/pulse-13.99.1/modules/module-udev-detect.so Title: pulseaudio crashed with SIGABRT in pa_alsa_ucm_add_profile_set() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo dmi.bios.date: 08/01/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F42b dmi.board.asset.tag: Default string dmi.board.name: AX370-Gaming 5 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF42b:bd08/01/2019:svnGigabyteTechnologyCo.,Ltd.:pnAX370-Gaming5:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnAX370-Gaming5:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: AX370-Gaming 5 dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. separator: To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/1870833/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1873398] [NEW] gnome-disks won't do SMART on NVME drive
Public bug reported: I'm running 20.04 beta amd64 Desktop from a USB stick of the live ISO. I opened Disks (gnome-disks) and it sees all my drives, but it won't show SMART stats on my NVME drive (Samsung SSD 970 EVO Plus 500GB). The SMART menu item is greyed out. It works fine on other drives. The NVME has SMART support; it works fine with smartctl -a /dev/nvme0n1 for example. (Though smartctl is not in this live ISO, I have apt-get installed it at another time and tried it; and it works fine in the Ubuntu 18.04 that is installed on this machine.) I've attached a screencast showing the failure. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-disk-utility 3.36.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu22 Architecture: amd64 CasperVersion: 1.442 CurrentDesktop: ubuntu:GNOME Date: Fri Apr 17 07:32:43 2020 ExecutablePath: /usr/bin/gnome-disks LiveMediaBuild: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) ProcEnviron: SHELL=/bin/bash XDG_RUNTIME_DIR= PATH=(custom, no user) LANG=C.UTF-8 SourcePackage: gnome-disk-utility UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-disk-utility (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ** Attachment added: "screencast of Disks failing to show SMART data on NVME drive" https://bugs.launchpad.net/bugs/1873398/+attachment/5355919/+files/Screencast%20from%2004-17-20%2007%3A38%3A22.webm -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-disk-utility in Ubuntu. https://bugs.launchpad.net/bugs/1873398 Title: gnome-disks won't do SMART on NVME drive Status in gnome-disk-utility package in Ubuntu: New Bug description: I'm running 20.04 beta amd64 Desktop from a USB stick of the live ISO. I opened Disks (gnome-disks) and it sees all my drives, but it won't show SMART stats on my NVME drive (Samsung SSD 970 EVO Plus 500GB). The SMART menu item is greyed out. It works fine on other drives. The NVME has SMART support; it works fine with smartctl -a /dev/nvme0n1 for example. (Though smartctl is not in this live ISO, I have apt-get installed it at another time and tried it; and it works fine in the Ubuntu 18.04 that is installed on this machine.) I've attached a screencast showing the failure. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-disk-utility 3.36.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu22 Architecture: amd64 CasperVersion: 1.442 CurrentDesktop: ubuntu:GNOME Date: Fri Apr 17 07:32:43 2020 ExecutablePath: /usr/bin/gnome-disks LiveMediaBuild: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) ProcEnviron: SHELL=/bin/bash XDG_RUNTIME_DIR= PATH=(custom, no user) LANG=C.UTF-8 SourcePackage: gnome-disk-utility UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-disk-utility/+bug/1873398/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1873407] [NEW] totem warns every time: "Drawing a gadget with negative dimensions. Did you forget to allocate a size? (node slider owner GtkScale)
Public bug reported: I am running Ubuntu 20.04 beta amd64 Desktop from the liveCD ISO. Whenever I run totem from a shell window to play a video, I get on stderr: "(totem:13002): Gtk-WARNING **: 07:50:52.916: Drawing a gadget with negative dimensions. Did you forget to allocate a size? (node slider owner GtkScale)" This has also been happening in totem in Ubuntu 18.04.4 LTS for years. I was shocked when I first ran it on 20.04 that apparently nobody else noticed this error. It happens every single time I run totem, as soon as it actually opens a video and starts playing it. For example, I made a screencast for a few seconds (with Ctl-Alt- Shift-R) and then played it from "totem ~/Videos/Screencast*.webm", and this error came out on stderr. If I just run "totem &" the error doesn't come out -- until I select a video from totem's interface. Once I pick one and play it, then the error comes out on the terminal screen where I typed the totem command. Is there supposed to be a slider for scaling the video? That would be a nice feature, but no slider appears, possibly due to this bug... ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: totem 3.34.1-2ubuntu2 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu22 Architecture: amd64 CasperVersion: 1.442 CurrentDesktop: ubuntu:GNOME Date: Fri Apr 17 07:46:58 2020 ExecutablePath: /usr/bin/totem LiveMediaBuild: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) ProcEnviron: SHELL=/bin/bash LANG=C.UTF-8 TERM=xterm-256color XDG_RUNTIME_DIR= PATH=(custom, no user) SourcePackage: totem UpgradeStatus: No upgrade log present (probably fresh install) XorgLog: Error: [Errno 2] No such file or directory: '/var/log/Xorg.0.log' ** Affects: totem (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 totem in Ubuntu. https://bugs.launchpad.net/bugs/1873407 Title: totem warns every time: "Drawing a gadget with negative dimensions. Did you forget to allocate a size? (node slider owner GtkScale) Status in totem package in Ubuntu: New Bug description: I am running Ubuntu 20.04 beta amd64 Desktop from the liveCD ISO. Whenever I run totem from a shell window to play a video, I get on stderr: "(totem:13002): Gtk-WARNING **: 07:50:52.916: Drawing a gadget with negative dimensions. Did you forget to allocate a size? (node slider owner GtkScale)" This has also been happening in totem in Ubuntu 18.04.4 LTS for years. I was shocked when I first ran it on 20.04 that apparently nobody else noticed this error. It happens every single time I run totem, as soon as it actually opens a video and starts playing it. For example, I made a screencast for a few seconds (with Ctl-Alt- Shift-R) and then played it from "totem ~/Videos/Screencast*.webm", and this error came out on stderr. If I just run "totem &" the error doesn't come out -- until I select a video from totem's interface. Once I pick one and play it, then the error comes out on the terminal screen where I typed the totem command. Is there supposed to be a slider for scaling the video? That would be a nice feature, but no slider appears, possibly due to this bug... ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: totem 3.34.1-2ubuntu2 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu22 Architecture: amd64 CasperVersion: 1.442 CurrentDesktop: ubuntu:GNOME Date: Fri Apr 17 07:46:58 2020 ExecutablePath: /usr/bin/totem LiveMediaBuild: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) ProcEnviron: SHELL=/bin/bash LANG=C.UTF-8 TERM=xterm-256color XDG_RUNTIME_DIR= PATH=(custom, no user) SourcePackage: totem UpgradeStatus: No upgrade log present (probably fresh install) XorgLog: Error: [Errno 2] No such file or directory: '/var/log/Xorg.0.log' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/totem/+bug/1873407/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1870833] Re: pulseaudio crashed with SIGABRT in pa_alsa_ucm_add_profile_set() from module_alsa_card_LTX_pa__init()
I forgot to note (and the attachments don't apparently say) that I am also running this on a Gigabyte Aorus GA-AX370-Gaming 5" motherboard. I have an AMD Ryzen 7 2700 Eight-Core Processor, and 16GB of DRAM. I'll enclose dmesg output so you can see what audio chips the kernel found when booting with this 20.04 beta kernel (Linux version 5.4.0-21-generic). Also will include syslog version of dmesg output from an Ubuntu 18.04.4 boot in which the sound works fine. ** Attachment added: "dmesg output from booting this system on 20.04 beta, for audio chip and BIOS audio configuration reports" https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1870833/+attachment/5355970/+files/dmesg-20.04-beta -- 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/1870833 Title: pulseaudio crashed with SIGABRT in pa_alsa_ucm_add_profile_set() from module_alsa_card_LTX_pa__init() Status in PulseAudio: New Status in pulseaudio package in Ubuntu: Triaged Bug description: https://errors.ubuntu.com/problem/468f63163a916557999ec0a7aac3459fa638a2d1 --- gigabyte X370 Gaming 5 main board, Ryzen 1600 16gb ram. I get a black screen on boot of clean install of the Beta 20.04. realised however it has booted, hitting enter then Password then Enter and desktop loads.. Get error concerning Pulse audio crashing. ProblemType: Crash DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu22 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC1', '/dev/snd/hwC1D1', '/dev/snd/hwC1D0', '/dev/snd/pcmC1D4c', '/dev/snd/pcmC1D4p', '/dev/snd/pcmC1D2c', '/dev/snd/pcmC1D1p', '/dev/snd/pcmC1D0c', '/dev/snd/pcmC1D0p', '/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D11p', '/dev/snd/pcmC0D10p', '/dev/snd/pcmC0D9p', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CrashCounter: 1 Date: Sat Apr 4 20:13:21 2020 ExecutablePath: /usr/bin/pulseaudio InstallationDate: Installed on 2020-04-04 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) ProcCmdline: /usr/bin/pulseaudio --daemonize=no ProcEnviron: LANG=en_GB.UTF-8 LANGUAGE=en_GB:en PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Signal: 6 SourcePackage: pulseaudio StacktraceTop: pa_alsa_ucm_add_profile_set () from /usr/lib/pulse-13.99.1/modules/libalsa-util.so module_alsa_card_LTX_pa__init () from /usr/lib/pulse-13.99.1/modules/module-alsa-card.so pa_module_load () from /usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecore-13.99.so ?? () from /usr/lib/pulse-13.99.1/modules/module-udev-detect.so ?? () from /usr/lib/pulse-13.99.1/modules/module-udev-detect.so Title: pulseaudio crashed with SIGABRT in pa_alsa_ucm_add_profile_set() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo dmi.bios.date: 08/01/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F42b dmi.board.asset.tag: Default string dmi.board.name: AX370-Gaming 5 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF42b:bd08/01/2019:svnGigabyteTechnologyCo.,Ltd.:pnAX370-Gaming5:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnAX370-Gaming5:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: AX370-Gaming 5 dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. separator: To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/1870833/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1870833] Re: pulseaudio crashed with SIGABRT in pa_alsa_ucm_add_profile_set() from module_alsa_card_LTX_pa__init()
** Attachment added: "syslog from Ubuntu 18.04.4 from the same system, with working sound and working pulseaudio, in case it helps." https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1870833/+attachment/5355971/+files/syslog-18.04.4 -- 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/1870833 Title: pulseaudio crashed with SIGABRT in pa_alsa_ucm_add_profile_set() from module_alsa_card_LTX_pa__init() Status in PulseAudio: New Status in pulseaudio package in Ubuntu: Triaged Bug description: https://errors.ubuntu.com/problem/468f63163a916557999ec0a7aac3459fa638a2d1 --- gigabyte X370 Gaming 5 main board, Ryzen 1600 16gb ram. I get a black screen on boot of clean install of the Beta 20.04. realised however it has booted, hitting enter then Password then Enter and desktop loads.. Get error concerning Pulse audio crashing. ProblemType: Crash DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu22 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC1', '/dev/snd/hwC1D1', '/dev/snd/hwC1D0', '/dev/snd/pcmC1D4c', '/dev/snd/pcmC1D4p', '/dev/snd/pcmC1D2c', '/dev/snd/pcmC1D1p', '/dev/snd/pcmC1D0c', '/dev/snd/pcmC1D0p', '/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D11p', '/dev/snd/pcmC0D10p', '/dev/snd/pcmC0D9p', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CrashCounter: 1 Date: Sat Apr 4 20:13:21 2020 ExecutablePath: /usr/bin/pulseaudio InstallationDate: Installed on 2020-04-04 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) ProcCmdline: /usr/bin/pulseaudio --daemonize=no ProcEnviron: LANG=en_GB.UTF-8 LANGUAGE=en_GB:en PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Signal: 6 SourcePackage: pulseaudio StacktraceTop: pa_alsa_ucm_add_profile_set () from /usr/lib/pulse-13.99.1/modules/libalsa-util.so module_alsa_card_LTX_pa__init () from /usr/lib/pulse-13.99.1/modules/module-alsa-card.so pa_module_load () from /usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecore-13.99.so ?? () from /usr/lib/pulse-13.99.1/modules/module-udev-detect.so ?? () from /usr/lib/pulse-13.99.1/modules/module-udev-detect.so Title: pulseaudio crashed with SIGABRT in pa_alsa_ucm_add_profile_set() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo dmi.bios.date: 08/01/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F42b dmi.board.asset.tag: Default string dmi.board.name: AX370-Gaming 5 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF42b:bd08/01/2019:svnGigabyteTechnologyCo.,Ltd.:pnAX370-Gaming5:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnAX370-Gaming5:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: AX370-Gaming 5 dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. separator: To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/1870833/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1870833] Re: pulseaudio crashed with SIGABRT in pa_alsa_ucm_add_profile_set() from module_alsa_card_LTX_pa__init()
With the -1ubuntu2 package, I no longer get a crash dump, but the audio is still not working. pulseaudio is aborting. Here is what is in syslog from bootup: Apr 18 01:13:09 shh dbus-daemon[1218]: [system] Activating via systemd: service name='org.freedesktop.RealtimeKit1' unit='rtkit-daemon.service' requested by ':1.31' (uid=122 pid=1443 comm="/usr/bin/pulseaudio --daemonize=no " label="unconfined") ... Apr 18 01:13:10 shh pulseaudio[1443]: W: [pulseaudio] alsa-ucm.c: UCM file does not specify 'PlaybackChannels' or 'CaptureChannels'for device Mic1, assuming stereo duplex. Apr 18 01:13:10 shh pulseaudio[1443]: W: [pulseaudio] alsa-ucm.c: UCM file does not specify 'PlaybackChannels' or 'CaptureChannels'for device Mic2, assuming stereo duplex. Apr 18 01:13:10 shh pulseaudio[1443]: W: [pulseaudio] alsa-ucm.c: UCM file does not specify 'PlaybackChannels' or 'CaptureChannels'for device Line2, assuming stereo duplex. Apr 18 01:13:10 shh pulseaudio[1443]: W: [pulseaudio] alsa-ucm.c: UCM file does not specify 'PlaybackChannels' or 'CaptureChannels'for device Headphones, assuming stereo duplex. Apr 18 01:13:10 shh pulseaudio[1443]: W: [pulseaudio] alsa-ucm.c: UCM file does not specify 'PlaybackChannels' or 'CaptureChannels'for device Line1, assuming stereo duplex. Apr 18 01:13:10 shh pulseaudio[1443]: W: [pulseaudio] alsa-ucm.c: UCM file does not specify 'PlaybackChannels' or 'CaptureChannels'for device Speaker, assuming stereo duplex. Apr 18 01:13:10 shh pulseaudio[1443]: E: [pulseaudio] alsa-ucm.c: Assertion 'jack' failed at modules/alsa/alsa-ucm.c:2158, function device_add_hw_mute_jack(). Aborting. ... Apr 18 01:13:10 shh systemd[1432]: pulseaudio.service: Main process exited, code=dumped, status=6/ABRT Apr 18 01:13:10 shh systemd[1432]: pulseaudio.service: Failed with result 'core-dump'. Apr 18 01:13:10 shh systemd[1432]: Failed to start Sound Service. Apr 18 01:13:10 shh systemd[1432]: Dependency failed for GNOME Sound sample caching handling. Apr 18 01:13:10 shh systemd[1432]: gsd-sound.target: Job gsd-sound.target/start failed with result 'dependency'. ... Apr 18 01:13:10 shh systemd[1432]: pulseaudio.service: Scheduled restart job, restart counter is at 1. ... Apr 18 01:13:10 shh systemd[1432]: Stopped Sound Service. Apr 18 01:13:10 shh systemd[1432]: Starting Sound Service... ... Apr 18 01:13:11 shh pulseaudio[1790]: W: [pulseaudio] pid.c: Stale PID file, overwriting. ... Apr 18 01:13:11 shh pulseaudio[1790]: W: [pulseaudio] alsa-ucm.c: UCM file does not specify 'PlaybackChannels' or 'CaptureChannels'for device Mic1, assuming stereo duplex. Apr 18 01:13:11 shh pulseaudio[1790]: W: [pulseaudio] alsa-ucm.c: UCM file does not specify 'PlaybackChannels' or 'CaptureChannels'for device Mic2, assuming stereo duplex. Apr 18 01:13:11 shh pulseaudio[1790]: W: [pulseaudio] alsa-ucm.c: UCM file does not specify 'PlaybackChannels' or 'CaptureChannels'for device Line2, assuming stereo duplex. Apr 18 01:13:11 shh pulseaudio[1790]: W: [pulseaudio] alsa-ucm.c: UCM file does not specify 'PlaybackChannels' or 'CaptureChannels'for device Headphones, assuming stereo duplex. Apr 18 01:13:11 shh pulseaudio[1790]: W: [pulseaudio] alsa-ucm.c: UCM file does not specify 'PlaybackChannels' or 'CaptureChannels'for device Line1, assuming stereo duplex. Apr 18 01:13:11 shh pulseaudio[1790]: W: [pulseaudio] alsa-ucm.c: UCM file does not specify 'PlaybackChannels' or 'CaptureChannels'for device Speaker, assuming stereo duplex. Apr 18 01:13:11 shh pulseaudio[1790]: E: [pulseaudio] alsa-ucm.c: Assertion 'jack' failed at modules/alsa/alsa-ucm.c:2158, function device_add_hw_mute_jack(). Aborting. Apr 18 01:13:12 shh systemd[1432]: pulseaudio.service: Main process exited, code=dumped, status=6/ABRT Apr 18 01:13:12 shh systemd[1432]: pulseaudio.service: Failed with result 'core-dump'. Apr 18 01:13:12 shh systemd[1432]: Failed to start Sound Service. Apr 18 01:13:12 shh systemd[1432]: Startup finished in 2.727s. Apr 18 01:13:12 shh systemd[1432]: pulseaudio.service: Scheduled restart job, restart counter is at 2. Apr 18 01:13:12 shh systemd[1432]: Stopped Sound Service. Apr 18 01:13:12 shh systemd[1432]: Starting Sound Service... Apr 18 01:13:12 shh rtkit-daemon[1539]: Successfully made thread 1864 of process 1864 owned by '122' high priority at nice level -11. Apr 18 01:13:12 shh rtkit-daemon[1539]: Supervising 1 threads of 1 processes of 1 users. Apr 18 01:13:12 shh pulseaudio[1864]: W: [pulseaudio] pid.c: Stale PID file, overwriting. ... Apr 18 01:13:13 shh pulseaudio[1864]: W: [pulseaudio] alsa-ucm.c: UCM file does not specify 'PlaybackChannels' or 'CaptureChannels'for device Mic1, assuming stereo duplex. Apr 18 01:13:13 shh pulseaudio[1864]: W: [pulseaudio] alsa-ucm.c: UCM file does not specify 'PlaybackChannels' or 'CaptureChannels'for device Mic2, assuming stereo duplex. Apr 18 01:13:13 shh pulseaudio[1864]: W: [pulseaudio] alsa-ucm.c: UCM file does not specify 'PlaybackChannels' or 'Captu
[Desktop-packages] [Bug 1870833] Re: pulseaudio crashed with SIGABRT in pa_alsa_ucm_add_profile_set() from module_alsa_card_LTX_pa__init()
** Attachment added: "Here's the alsa-info output for this system, in case it helps." https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1870833/+attachment/5356402/+files/alsa-info.txt.QsoAGgtfAU -- 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/1870833 Title: pulseaudio crashed with SIGABRT in pa_alsa_ucm_add_profile_set() from module_alsa_card_LTX_pa__init() Status in PulseAudio: New Status in pulseaudio package in Ubuntu: Incomplete Bug description: https://errors.ubuntu.com/problem/468f63163a916557999ec0a7aac3459fa638a2d1 --- gigabyte X370 Gaming 5 main board, Ryzen 1600 16gb ram. I get a black screen on boot of clean install of the Beta 20.04. realised however it has booted, hitting enter then Password then Enter and desktop loads.. Get error concerning Pulse audio crashing. ProblemType: Crash DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu22 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC1', '/dev/snd/hwC1D1', '/dev/snd/hwC1D0', '/dev/snd/pcmC1D4c', '/dev/snd/pcmC1D4p', '/dev/snd/pcmC1D2c', '/dev/snd/pcmC1D1p', '/dev/snd/pcmC1D0c', '/dev/snd/pcmC1D0p', '/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D11p', '/dev/snd/pcmC0D10p', '/dev/snd/pcmC0D9p', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CrashCounter: 1 Date: Sat Apr 4 20:13:21 2020 ExecutablePath: /usr/bin/pulseaudio InstallationDate: Installed on 2020-04-04 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) ProcCmdline: /usr/bin/pulseaudio --daemonize=no ProcEnviron: LANG=en_GB.UTF-8 LANGUAGE=en_GB:en PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Signal: 6 SourcePackage: pulseaudio StacktraceTop: pa_alsa_ucm_add_profile_set () from /usr/lib/pulse-13.99.1/modules/libalsa-util.so module_alsa_card_LTX_pa__init () from /usr/lib/pulse-13.99.1/modules/module-alsa-card.so pa_module_load () from /usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecore-13.99.so ?? () from /usr/lib/pulse-13.99.1/modules/module-udev-detect.so ?? () from /usr/lib/pulse-13.99.1/modules/module-udev-detect.so Title: pulseaudio crashed with SIGABRT in pa_alsa_ucm_add_profile_set() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo dmi.bios.date: 08/01/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F42b dmi.board.asset.tag: Default string dmi.board.name: AX370-Gaming 5 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF42b:bd08/01/2019:svnGigabyteTechnologyCo.,Ltd.:pnAX370-Gaming5:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnAX370-Gaming5:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: AX370-Gaming 5 dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. separator: To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/1870833/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1873630] [NEW] [pulseaudio] alsa-ucm.c: Assertion 'jack' failed at modules/alsa/alsa-ucm.c:2158, function device_add_hw_mute_jack(). Aborting.
Public bug reported: I have a Gigabyte motherboard that gives pulseaudio fits in Ubuntu 20.04 beta. (It worked fine in 18.04.4 LTS.) It produced pulseaudio crashes with bug #1870833 until a proposed fix was brought in from upstream: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/1:13.99.1-1ubuntu2 However, that did not actually make pulseaudio work; now it throws this error and aborts: Apr 18 01:13:10 shh pulseaudio[1443]: E: [pulseaudio] alsa-ucm.c: Assertion 'jack' failed at modules/alsa/alsa-ucm.c:2158, function device_add_hw_mute_jack(). Aborting. It was suggested in the previous bug that I should open a new bug for this. Here you are! ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu2 ProcVersionSignature: Ubuntu 5.4.0-24.28-generic 5.4.30 Uname: Linux 5.4.0-24-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/by-path', '/dev/snd/controlC1', '/dev/snd/hwC1D1', '/dev/snd/hwC1D0', '/dev/snd/pcmC1D4c', '/dev/snd/pcmC1D4p', '/dev/snd/pcmC1D2c', '/dev/snd/pcmC1D1p', '/dev/snd/pcmC1D0c', '/dev/snd/pcmC1D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Apr 19 00:25:26 2020 InstallationDate: Installed on 2020-04-17 (1 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash 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: 01/16/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F25 dmi.board.asset.tag: Default string dmi.board.name: AX370-Gaming 5 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF25:bd01/16/2019:svnGigabyteTechnologyCo.,Ltd.:pnAX370-Gaming5:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnAX370-Gaming5:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: AX370-Gaming 5 dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. ** 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/1873630 Title: [pulseaudio] alsa-ucm.c: Assertion 'jack' failed at modules/alsa/alsa- ucm.c:2158, function device_add_hw_mute_jack(). Aborting. Status in pulseaudio package in Ubuntu: New Bug description: I have a Gigabyte motherboard that gives pulseaudio fits in Ubuntu 20.04 beta. (It worked fine in 18.04.4 LTS.) It produced pulseaudio crashes with bug #1870833 until a proposed fix was brought in from upstream: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/1:13.99.1-1ubuntu2 However, that did not actually make pulseaudio work; now it throws this error and aborts: Apr 18 01:13:10 shh pulseaudio[1443]: E: [pulseaudio] alsa-ucm.c: Assertion 'jack' failed at modules/alsa/alsa-ucm.c:2158, function device_add_hw_mute_jack(). Aborting. It was suggested in the previous bug that I should open a new bug for this. Here you are! ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu2 ProcVersionSignature: Ubuntu 5.4.0-24.28-generic 5.4.30 Uname: Linux 5.4.0-24-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/by-path', '/dev/snd/controlC1', '/dev/snd/hwC1D1', '/dev/snd/hwC1D0', '/dev/snd/pcmC1D4c', '/dev/snd/pcmC1D4p', '/dev/snd/pcmC1D2c', '/dev/snd/pcmC1D1p', '/dev/snd/pcmC1D0c', '/dev/snd/pcmC1D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Apr 19 00:25:26 2020 InstallationDate: Installed on 2020-04-17 (1 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash 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
[Desktop-packages] [Bug 1870833] Re: pulseaudio crashed with SIGABRT in pa_alsa_ucm_add_profile_set() from module_alsa_card_LTX_pa__init()
OK, that's bug #1873630. We don't actually know that this current crasher bug is correctly solved by the above patch, since pulseaudio is not yet working. Perhaps the new bug was there all along, but perhaps it was introduced by this patch being an incomplete fix. -- 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/1870833 Title: pulseaudio crashed with SIGABRT in pa_alsa_ucm_add_profile_set() from module_alsa_card_LTX_pa__init() Status in PulseAudio: New Status in pulseaudio package in Ubuntu: Incomplete Bug description: https://errors.ubuntu.com/problem/468f63163a916557999ec0a7aac3459fa638a2d1 --- gigabyte X370 Gaming 5 main board, Ryzen 1600 16gb ram. I get a black screen on boot of clean install of the Beta 20.04. realised however it has booted, hitting enter then Password then Enter and desktop loads.. Get error concerning Pulse audio crashing. ProblemType: Crash DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu22 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC1', '/dev/snd/hwC1D1', '/dev/snd/hwC1D0', '/dev/snd/pcmC1D4c', '/dev/snd/pcmC1D4p', '/dev/snd/pcmC1D2c', '/dev/snd/pcmC1D1p', '/dev/snd/pcmC1D0c', '/dev/snd/pcmC1D0p', '/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D11p', '/dev/snd/pcmC0D10p', '/dev/snd/pcmC0D9p', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CrashCounter: 1 Date: Sat Apr 4 20:13:21 2020 ExecutablePath: /usr/bin/pulseaudio InstallationDate: Installed on 2020-04-04 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) ProcCmdline: /usr/bin/pulseaudio --daemonize=no ProcEnviron: LANG=en_GB.UTF-8 LANGUAGE=en_GB:en PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Signal: 6 SourcePackage: pulseaudio StacktraceTop: pa_alsa_ucm_add_profile_set () from /usr/lib/pulse-13.99.1/modules/libalsa-util.so module_alsa_card_LTX_pa__init () from /usr/lib/pulse-13.99.1/modules/module-alsa-card.so pa_module_load () from /usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecore-13.99.so ?? () from /usr/lib/pulse-13.99.1/modules/module-udev-detect.so ?? () from /usr/lib/pulse-13.99.1/modules/module-udev-detect.so Title: pulseaudio crashed with SIGABRT in pa_alsa_ucm_add_profile_set() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo dmi.bios.date: 08/01/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F42b dmi.board.asset.tag: Default string dmi.board.name: AX370-Gaming 5 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF42b:bd08/01/2019:svnGigabyteTechnologyCo.,Ltd.:pnAX370-Gaming5:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnAX370-Gaming5:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: AX370-Gaming 5 dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. separator: To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/1870833/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1873630] Re: [pulseaudio] alsa-ucm.c: Assertion 'jack' failed at modules/alsa/alsa-ucm.c:2158, function device_add_hw_mute_jack(). Aborting.
I ran the software updater and noticed that it installed a new pulseaudio: pulseaudio: Installed: 1:13.99.1-1ubuntu3 Candidate: 1:13.99.1-1ubuntu3 After rebooting the system, I'm running this version. You will be happy to learn that pulseaudio doesn't crash with this version, and it shows sound devices in Settings -> Sound, and the speaker test actually plays (once I picked Line Out rather than the default which was Speaker -- my chassis doesn't have a speaker). I am even able to play mp3 and flac music in Totem. I think it's fixed! Thank you! -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1873630 Title: [pulseaudio] alsa-ucm.c: Assertion 'jack' failed at modules/alsa/alsa- ucm.c:2158, function device_add_hw_mute_jack(). Aborting. Status in pulseaudio package in Ubuntu: New Bug description: I have a Gigabyte motherboard that gives pulseaudio fits in Ubuntu 20.04 beta. (It worked fine in 18.04.4 LTS.) It produced pulseaudio crashes with bug #1870833 until a proposed fix was brought in from upstream: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/1:13.99.1-1ubuntu2 However, that did not actually make pulseaudio work; now it throws this error and aborts: Apr 18 01:13:10 shh pulseaudio[1443]: E: [pulseaudio] alsa-ucm.c: Assertion 'jack' failed at modules/alsa/alsa-ucm.c:2158, function device_add_hw_mute_jack(). Aborting. It was suggested in the previous bug that I should open a new bug for this. Here you are! ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu2 ProcVersionSignature: Ubuntu 5.4.0-24.28-generic 5.4.30 Uname: Linux 5.4.0-24-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/by-path', '/dev/snd/controlC1', '/dev/snd/hwC1D1', '/dev/snd/hwC1D0', '/dev/snd/pcmC1D4c', '/dev/snd/pcmC1D4p', '/dev/snd/pcmC1D2c', '/dev/snd/pcmC1D1p', '/dev/snd/pcmC1D0c', '/dev/snd/pcmC1D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Apr 19 00:25:26 2020 InstallationDate: Installed on 2020-04-17 (1 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash 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: 01/16/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F25 dmi.board.asset.tag: Default string dmi.board.name: AX370-Gaming 5 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF25:bd01/16/2019:svnGigabyteTechnologyCo.,Ltd.:pnAX370-Gaming5:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnAX370-Gaming5:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: AX370-Gaming 5 dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1873630/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1870833] Re: pulseaudio crashed with SIGABRT in pa_alsa_ucm_add_profile_set() from module_alsa_card_LTX_pa__init()
I ran the software updater and noticed that it installed a new pulseaudio: pulseaudio: Installed: 1:13.99.1-1ubuntu3 Candidate: 1:13.99.1-1ubuntu3 After rebooting the system, I'm running this version. You will be happy to learn that pulseaudio doesn't crash with this version, and it shows sound devices in Settings -> Sound, and the speaker test actually plays (once I picked Line Out rather than the default which was Speaker -- my chassis doesn't have a speaker). I am even able to play mp3 and flac music in Totem. I think it's fixed! Thank you! -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1870833 Title: pulseaudio crashed with SIGABRT in pa_alsa_ucm_add_profile_set() from module_alsa_card_LTX_pa__init() Status in PulseAudio: New Status in pulseaudio package in Ubuntu: Incomplete Bug description: https://errors.ubuntu.com/problem/468f63163a916557999ec0a7aac3459fa638a2d1 --- gigabyte X370 Gaming 5 main board, Ryzen 1600 16gb ram. I get a black screen on boot of clean install of the Beta 20.04. realised however it has booted, hitting enter then Password then Enter and desktop loads.. Get error concerning Pulse audio crashing. ProblemType: Crash DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu22 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC1', '/dev/snd/hwC1D1', '/dev/snd/hwC1D0', '/dev/snd/pcmC1D4c', '/dev/snd/pcmC1D4p', '/dev/snd/pcmC1D2c', '/dev/snd/pcmC1D1p', '/dev/snd/pcmC1D0c', '/dev/snd/pcmC1D0p', '/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D11p', '/dev/snd/pcmC0D10p', '/dev/snd/pcmC0D9p', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CrashCounter: 1 Date: Sat Apr 4 20:13:21 2020 ExecutablePath: /usr/bin/pulseaudio InstallationDate: Installed on 2020-04-04 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) ProcCmdline: /usr/bin/pulseaudio --daemonize=no ProcEnviron: LANG=en_GB.UTF-8 LANGUAGE=en_GB:en PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Signal: 6 SourcePackage: pulseaudio StacktraceTop: pa_alsa_ucm_add_profile_set () from /usr/lib/pulse-13.99.1/modules/libalsa-util.so module_alsa_card_LTX_pa__init () from /usr/lib/pulse-13.99.1/modules/module-alsa-card.so pa_module_load () from /usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecore-13.99.so ?? () from /usr/lib/pulse-13.99.1/modules/module-udev-detect.so ?? () from /usr/lib/pulse-13.99.1/modules/module-udev-detect.so Title: pulseaudio crashed with SIGABRT in pa_alsa_ucm_add_profile_set() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo dmi.bios.date: 08/01/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F42b dmi.board.asset.tag: Default string dmi.board.name: AX370-Gaming 5 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF42b:bd08/01/2019:svnGigabyteTechnologyCo.,Ltd.:pnAX370-Gaming5:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnAX370-Gaming5:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: AX370-Gaming 5 dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. separator: To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/1870833/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1888088] [NEW] [Lenovo IdeaPad Flex 5 14ARE05] Display won't rotate, nor do fractional scaling
Public bug reported: Opening Settings -> Display and selecting an orientation other than Landscape doesn't work. Similarly, selecting Fractional Scaling and then picking a scale factor has no effect. This is a recently installed Ubuntu 20.04, fully updated, on a recently released laptop/tablet that uses an AMD Ryzen 4500U integrated CPU/GPU. It is possible that the GPU is not being detected by Ubuntu and that is the root cause of the problem. I couldn't find an easy explanation online about how to tell whether a GPU was detected or is in use. I did try running "tlp-stat -g" to get graphics status, but it returns without printing anything except its version number (1.3.1). When I choose an orientation, such as Portrait Right, the setting changes and an "Apply" button appears in the top of the Settings window. When I press it, up pops up a dialog asking whether I want to "Keep these display settings?" with two options, keep or revert. The rest of the screen goes grey behind the dialog box, but I can already see that the "Orientation" setting back in the Settings->Display window has been reverted to "Landscape" without me doing anything. Whether I choose keep or revert, or merely let it time out after 20 seconds, the result remains the same -- the display stays in Landscape mode and the setting that I had made is reverted. Regarding scaling, I can set the display scale to 100% (default) or 200%, successfully. When I turn on the "Fractional Scaling" slider, the graphics around the edge of the screen increase in size (the icons in the left-hand dock, the text in the top bar), but the Scale settings do not change (they remain "100%" and "200%"). However, if I switch to a different setting (for example, "Mouse & Touchpad") and then back to "Displays", the Scale settings have changed. I have included three screenshots (original screen, Fractional Scaling on, and after switching to and from Displays. When I attempt to set a fractional scale such as 125%, the "Apply" button appears in the upper right corner. When I press that, the display does not scale, a pop-up asks if I want to keep or revert the setting, but looking back at the Displays settings, the Scale has already reverted to 100% (as above with the Orientation). The display has been rock-solid before this, but now it started showing artifacts, such as previous copies of the Displays window. I've enclosed a screen shot. Merely taking a screen shot also wiped out parts of the display to white; I took another shot to show that. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 BootLog: CasperMD5CheckResult: skip CompositorRunning: None Date: Sat Jul 18 14:00:38 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Renoir [1002:1636] (rev c3) (prog-if 00 [VGA controller]) Subsystem: Lenovo Renoir [17aa:3f1a] InstallationDate: Installed on 2020-07-16 (1 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: LENOVO 81X2 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-40-generic root=/dev/mapper/vgubuntu-root ro quiet splash acpi_enforce_resources=lax vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/08/2020 dmi.bios.vendor: LENOVO dmi.bios.version: EECN20WW dmi.board.asset.tag: No Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40700 WIN dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: LENOVO dmi.chassis.version: IdeaPad Flex 5 14ARE05 dmi.modalias: dmi:bvnLENOVO:bvrEECN20WW:bd04/08/2020:svnLENOVO:pn81X2:pvrIdeaPadFlex514ARE05:rvnLENOVO:rnLNVNB161216:rvrSDK0J40700WIN:cvnLENOVO:ct31:cvrIdeaPadFlex514ARE05: dmi.product.family: IdeaPad Flex 5 14ARE05 dmi.product.name: 81X2 dmi.product.sku: LENOVO_MT_81X2_BU_idea_FM_IdeaPad Flex 5 14ARE05 dmi.product.version: IdeaPad Flex 5 14ARE05 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ubuntu -- You received this bug notification because you
[Desktop-packages] [Bug 1888088] Re: [Lenovo IdeaPad Flex 5 14ARE05] Display won't rotate, nor do fractional scaling
** Attachment added: "This is my screen just after I slide the Fractional Scaling slider. The icons in the left margin, and the text at the top of the screen, have changed size (despite me not picking any new scale) and nothing else has scaled." https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1888088/+attachment/5393947/+files/Screenshot%20from%202020-07-18%2014-21-41%20-%20fractional%20scaling%20with%20large%20dock%20and%20top%20bar%20but%20nothing%20else%20scaled.png -- 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/1888088 Title: [Lenovo IdeaPad Flex 5 14ARE05] Display won't rotate, nor do fractional scaling Status in xorg package in Ubuntu: New Bug description: Opening Settings -> Display and selecting an orientation other than Landscape doesn't work. Similarly, selecting Fractional Scaling and then picking a scale factor has no effect. This is a recently installed Ubuntu 20.04, fully updated, on a recently released laptop/tablet that uses an AMD Ryzen 4500U integrated CPU/GPU. It is possible that the GPU is not being detected by Ubuntu and that is the root cause of the problem. I couldn't find an easy explanation online about how to tell whether a GPU was detected or is in use. I did try running "tlp-stat -g" to get graphics status, but it returns without printing anything except its version number (1.3.1). When I choose an orientation, such as Portrait Right, the setting changes and an "Apply" button appears in the top of the Settings window. When I press it, up pops up a dialog asking whether I want to "Keep these display settings?" with two options, keep or revert. The rest of the screen goes grey behind the dialog box, but I can already see that the "Orientation" setting back in the Settings->Display window has been reverted to "Landscape" without me doing anything. Whether I choose keep or revert, or merely let it time out after 20 seconds, the result remains the same -- the display stays in Landscape mode and the setting that I had made is reverted. Regarding scaling, I can set the display scale to 100% (default) or 200%, successfully. When I turn on the "Fractional Scaling" slider, the graphics around the edge of the screen increase in size (the icons in the left-hand dock, the text in the top bar), but the Scale settings do not change (they remain "100%" and "200%"). However, if I switch to a different setting (for example, "Mouse & Touchpad") and then back to "Displays", the Scale settings have changed. I have included three screenshots (original screen, Fractional Scaling on, and after switching to and from Displays. When I attempt to set a fractional scale such as 125%, the "Apply" button appears in the upper right corner. When I press that, the display does not scale, a pop-up asks if I want to keep or revert the setting, but looking back at the Displays settings, the Scale has already reverted to 100% (as above with the Orientation). The display has been rock-solid before this, but now it started showing artifacts, such as previous copies of the Displays window. I've enclosed a screen shot. Merely taking a screen shot also wiped out parts of the display to white; I took another shot to show that. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 BootLog: CasperMD5CheckResult: skip CompositorRunning: None Date: Sat Jul 18 14:00:38 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Renoir [1002:1636] (rev c3) (prog-if 00 [VGA controller]) Subsystem: Lenovo Renoir [17aa:3f1a] InstallationDate: Installed on 2020-07-16 (1 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: LENOVO 81X2 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-40-generic root=/dev/mapper/vgubuntu-root ro quiet splash acpi_enforce_resources=lax vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/08/2020 dmi.bios.vendor: LENOVO dmi.bios.version: EECN20WW dmi.board.asset.tag: No Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40700 WIN dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: LENOVO dmi.chassis.version: IdeaPad Flex 5 14ARE05 dmi.modalias: dmi:bvnLENOVO:bvrEECN20WW:bd04/08/2020:svnLENOVO:pn81X2:pvrIdeaPadFlex514ARE05:rvnLENOVO:rnLNVNB161216:rvrSDK0J40700
[Desktop-packages] [Bug 1888088] Re: [Lenovo IdeaPad Flex 5 14ARE05] Display won't rotate, nor do fractional scaling
** Attachment added: "This is my screen before I slide the "Fractional Scaling" slider." https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1888088/+attachment/5393945/+files/Screenshot%20from%202020-07-18%2014-21-25%20-%20before%20fractional%20scaling.png -- 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/1888088 Title: [Lenovo IdeaPad Flex 5 14ARE05] Display won't rotate, nor do fractional scaling Status in xorg package in Ubuntu: New Bug description: Opening Settings -> Display and selecting an orientation other than Landscape doesn't work. Similarly, selecting Fractional Scaling and then picking a scale factor has no effect. This is a recently installed Ubuntu 20.04, fully updated, on a recently released laptop/tablet that uses an AMD Ryzen 4500U integrated CPU/GPU. It is possible that the GPU is not being detected by Ubuntu and that is the root cause of the problem. I couldn't find an easy explanation online about how to tell whether a GPU was detected or is in use. I did try running "tlp-stat -g" to get graphics status, but it returns without printing anything except its version number (1.3.1). When I choose an orientation, such as Portrait Right, the setting changes and an "Apply" button appears in the top of the Settings window. When I press it, up pops up a dialog asking whether I want to "Keep these display settings?" with two options, keep or revert. The rest of the screen goes grey behind the dialog box, but I can already see that the "Orientation" setting back in the Settings->Display window has been reverted to "Landscape" without me doing anything. Whether I choose keep or revert, or merely let it time out after 20 seconds, the result remains the same -- the display stays in Landscape mode and the setting that I had made is reverted. Regarding scaling, I can set the display scale to 100% (default) or 200%, successfully. When I turn on the "Fractional Scaling" slider, the graphics around the edge of the screen increase in size (the icons in the left-hand dock, the text in the top bar), but the Scale settings do not change (they remain "100%" and "200%"). However, if I switch to a different setting (for example, "Mouse & Touchpad") and then back to "Displays", the Scale settings have changed. I have included three screenshots (original screen, Fractional Scaling on, and after switching to and from Displays. When I attempt to set a fractional scale such as 125%, the "Apply" button appears in the upper right corner. When I press that, the display does not scale, a pop-up asks if I want to keep or revert the setting, but looking back at the Displays settings, the Scale has already reverted to 100% (as above with the Orientation). The display has been rock-solid before this, but now it started showing artifacts, such as previous copies of the Displays window. I've enclosed a screen shot. Merely taking a screen shot also wiped out parts of the display to white; I took another shot to show that. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 BootLog: CasperMD5CheckResult: skip CompositorRunning: None Date: Sat Jul 18 14:00:38 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Renoir [1002:1636] (rev c3) (prog-if 00 [VGA controller]) Subsystem: Lenovo Renoir [17aa:3f1a] InstallationDate: Installed on 2020-07-16 (1 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: LENOVO 81X2 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-40-generic root=/dev/mapper/vgubuntu-root ro quiet splash acpi_enforce_resources=lax vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/08/2020 dmi.bios.vendor: LENOVO dmi.bios.version: EECN20WW dmi.board.asset.tag: No Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40700 WIN dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: LENOVO dmi.chassis.version: IdeaPad Flex 5 14ARE05 dmi.modalias: dmi:bvnLENOVO:bvrEECN20WW:bd04/08/2020:svnLENOVO:pn81X2:pvrIdeaPadFlex514ARE05:rvnLENOVO:rnLNVNB161216:rvrSDK0J40700WIN:cvnLENOVO:ct31:cvrIdeaPadFlex514ARE05: dmi.product.family: IdeaPad Flex 5 14ARE05 dmi.product.name: 81X2 dmi.product.sku: LENOVO_MT_81X2_BU_idea_FM_IdeaPad Flex 5 14ARE05 dmi.product.version: IdeaPad Flex 5 14AR
[Desktop-packages] [Bug 1888088] Re: [Lenovo IdeaPad Flex 5 14ARE05] Display won't rotate, nor do fractional scaling
** Attachment added: "This is my screen after I chose "125%" as a fractional scale, then pressed Apply. The pop-up has dimmed the underlying windows, but you can see that the Scale setting in the underlying Displays window has reverted to "100%", and nothing on the screen has changed its scale to 125%." https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1888088/+attachment/5393948/+files/Screenshot%20from%202020-07-18%2014-27-40%20-%20attempted%20125%25%20with%20popup.png -- 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/1888088 Title: [Lenovo IdeaPad Flex 5 14ARE05] Display won't rotate, nor do fractional scaling Status in xorg package in Ubuntu: New Bug description: Opening Settings -> Display and selecting an orientation other than Landscape doesn't work. Similarly, selecting Fractional Scaling and then picking a scale factor has no effect. This is a recently installed Ubuntu 20.04, fully updated, on a recently released laptop/tablet that uses an AMD Ryzen 4500U integrated CPU/GPU. It is possible that the GPU is not being detected by Ubuntu and that is the root cause of the problem. I couldn't find an easy explanation online about how to tell whether a GPU was detected or is in use. I did try running "tlp-stat -g" to get graphics status, but it returns without printing anything except its version number (1.3.1). When I choose an orientation, such as Portrait Right, the setting changes and an "Apply" button appears in the top of the Settings window. When I press it, up pops up a dialog asking whether I want to "Keep these display settings?" with two options, keep or revert. The rest of the screen goes grey behind the dialog box, but I can already see that the "Orientation" setting back in the Settings->Display window has been reverted to "Landscape" without me doing anything. Whether I choose keep or revert, or merely let it time out after 20 seconds, the result remains the same -- the display stays in Landscape mode and the setting that I had made is reverted. Regarding scaling, I can set the display scale to 100% (default) or 200%, successfully. When I turn on the "Fractional Scaling" slider, the graphics around the edge of the screen increase in size (the icons in the left-hand dock, the text in the top bar), but the Scale settings do not change (they remain "100%" and "200%"). However, if I switch to a different setting (for example, "Mouse & Touchpad") and then back to "Displays", the Scale settings have changed. I have included three screenshots (original screen, Fractional Scaling on, and after switching to and from Displays. When I attempt to set a fractional scale such as 125%, the "Apply" button appears in the upper right corner. When I press that, the display does not scale, a pop-up asks if I want to keep or revert the setting, but looking back at the Displays settings, the Scale has already reverted to 100% (as above with the Orientation). The display has been rock-solid before this, but now it started showing artifacts, such as previous copies of the Displays window. I've enclosed a screen shot. Merely taking a screen shot also wiped out parts of the display to white; I took another shot to show that. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 BootLog: CasperMD5CheckResult: skip CompositorRunning: None Date: Sat Jul 18 14:00:38 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Renoir [1002:1636] (rev c3) (prog-if 00 [VGA controller]) Subsystem: Lenovo Renoir [17aa:3f1a] InstallationDate: Installed on 2020-07-16 (1 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: LENOVO 81X2 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-40-generic root=/dev/mapper/vgubuntu-root ro quiet splash acpi_enforce_resources=lax vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/08/2020 dmi.bios.vendor: LENOVO dmi.bios.version: EECN20WW dmi.board.asset.tag: No Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40700 WIN dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: LENOVO dmi.chassis.version: IdeaPad Flex 5 14ARE05 dmi.modalias: dmi:bvnLENOVO:bvrEECN20WW:bd04/08/2020:svnLENOVO:pn81X2:pvrIdeaPadFlex514ARE05:rvnLENOVO:rnLNVNB161216:rvrSDK0J40700
[Desktop-packages] [Bug 1888088] Re: [Lenovo IdeaPad Flex 5 14ARE05] Display won't rotate, nor do fractional scaling
** Description changed: Opening Settings -> Display and selecting an orientation other than Landscape doesn't work. Similarly, selecting Fractional Scaling and then picking a scale factor has no effect. This is a recently installed Ubuntu 20.04, fully updated, on a recently released laptop/tablet that uses an AMD Ryzen 4500U integrated CPU/GPU. It is possible that the GPU is not being detected by Ubuntu and that is the root cause of the problem. I couldn't find an easy explanation online about how to tell whether a GPU was detected or is in use. I did try running "tlp-stat -g" to get graphics status, but it returns without printing anything except its version number (1.3.1). When I choose an orientation, such as Portrait Right, the setting changes and an "Apply" button appears in the top of the Settings window. When I press it, up pops up a dialog asking whether I want to "Keep these display settings?" with two options, keep or revert. The rest of the screen goes grey behind the dialog box, but I can already see that the "Orientation" setting back in the Settings->Display window has been reverted to "Landscape" without me doing anything. Whether I choose keep or revert, or merely let it time out after 20 seconds, the result remains the same -- the display stays in Landscape mode and the setting that I had made is reverted. Regarding scaling, I can set the display scale to 100% (default) or 200%, successfully. When I turn on the "Fractional Scaling" slider, the graphics around the edge of the screen increase in size (the icons in the left-hand dock, the text in the top bar), but the Scale settings do not change (they remain "100%" and "200%"). However, if I switch to a different setting (for example, "Mouse & Touchpad") and then back to "Displays", the Scale settings have changed. I have included three screenshots (original screen, Fractional Scaling on, and after switching to and from Displays. When I attempt to set a fractional scale such as 125%, the "Apply" button appears in the upper right corner. When I press that, the display does not scale, a pop-up asks if I want to keep or revert the setting, but looking back at the Displays settings, the Scale has already reverted to 100% (as above with the Orientation). - The display has been rock-solid before this, but now it started showing artifacts, such as + The display has been rock-solid before this, but now it started showing artifacts, such as previous copies of the Displays window. I've enclosed a screen shot. Merely taking a screen shot also wiped out parts of the display to white; I took another shot to show that. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 BootLog: - + CasperMD5CheckResult: skip CompositorRunning: None Date: Sat Jul 18 14:00:38 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: - Advanced Micro Devices, Inc. [AMD/ATI] Renoir [1002:1636] (rev c3) (prog-if 00 [VGA controller]) -Subsystem: Lenovo Renoir [17aa:3f1a] + Advanced Micro Devices, Inc. [AMD/ATI] Renoir [1002:1636] (rev c3) (prog-if 00 [VGA controller]) + Subsystem: Lenovo Renoir [17aa:3f1a] InstallationDate: Installed on 2020-07-16 (1 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: LENOVO 81X2 ProcEnviron: - TERM=xterm-256color - PATH=(custom, no user) - LANG=en_US.UTF-8 - SHELL=/bin/bash + TERM=xterm-256color + PATH=(custom, no user) + LANG=en_US.UTF-8 + SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-40-generic root=/dev/mapper/vgubuntu-root ro quiet splash acpi_enforce_resources=lax vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/08/2020 dmi.bios.vendor: LENOVO dmi.bios.version: EECN20WW dmi.board.asset.tag: No Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40700 WIN dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: LENOVO dmi.chassis.version: IdeaPad Flex 5 14ARE05 dmi.modalias: dmi:bvnLENOVO:bvrEECN20WW:bd04/08/2020:svnLENOVO:pn81X2:pvrIdeaPadFlex514ARE05:rvnLENOVO:rnLNVNB161216:rvrSDK0J40700WIN:cvnLENOVO:ct31:cvrIdeaPadFlex514ARE05: dmi.product.family: IdeaPad Flex 5 14ARE05 dmi.product.name: 81X2 dmi.product.sku: LENOVO_MT_81X2_BU_idea_FM_IdeaPad Flex 5 14ARE05 dmi.product.version: IdeaPad Flex 5 14ARE05 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A ve
[Desktop-packages] [Bug 1888088] Re: [amdgpu] [Lenovo IdeaPad Flex 5 14ARE05] Display won't rotate, nor do fractional scaling
I found a way to enable the amdgpu support for this hardware in the standard LTS kernel! Based on this comment on a YouTube video reviewing this laptop: https://www.youtube.com/watch?v=FjegdWtHuOE&lc=UgzbtkQw4vuk6ls- 6vF4AaABAg Add "amdgpu.exp_hw_support=1" to the kernel command line in /etc/default/grub, run update-grub, and reboot. This FIXES ALL THE ISSUES that I encountered in this bug. I am running linux-image-5.4.0-42-generic:amd64 (5.4.0-42.46) which is the current LTS kernel. The same poster also recommended turning on this Firefox about:config setting, to avoid screen tearing while playing YouTube videos: layers.acceleration.force-enabled. I have seen reports (comments below that same YouTube video, and elsewhere) that there are small kernel patches in the 5.7 kernels that also fix the screen brightness settings on this hardware. Perhaps a future Ubuntu kernel update can cherry-pick those fixes, and automatically enable the experimental hardware support for this integrated AMD Ryzen 5 4500U CPU/GPU? Would be good for these fixes to get into the Ubuntu 20.04.1 point release, too; these laptops are very fast and cost $600 so they are selling very well. -- 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/1888088 Title: [amdgpu] [Lenovo IdeaPad Flex 5 14ARE05] Display won't rotate, nor do fractional scaling Status in mutter package in Ubuntu: New Status in xserver-xorg-video-amdgpu package in Ubuntu: New Bug description: Opening Settings -> Display and selecting an orientation other than Landscape doesn't work. Similarly, selecting Fractional Scaling and then picking a scale factor has no effect. This is a recently installed Ubuntu 20.04, fully updated, on a recently released laptop/tablet that uses an AMD Ryzen 4500U integrated CPU/GPU. It is possible that the GPU is not being detected by Ubuntu and that is the root cause of the problem. I couldn't find an easy explanation online about how to tell whether a GPU was detected or is in use. I did try running "tlp-stat -g" to get graphics status, but it returns without printing anything except its version number (1.3.1). When I choose an orientation, such as Portrait Right, the setting changes and an "Apply" button appears in the top of the Settings window. When I press it, up pops up a dialog asking whether I want to "Keep these display settings?" with two options, keep or revert. The rest of the screen goes grey behind the dialog box, but I can already see behind the popup that the screen did not change its orientation, and the "Orientation" setting back in the Settings->Display window has been reverted to "Landscape" without me doing it. Whether I choose keep or revert, or merely let it time out after 20 seconds, the result remains the same -- the display stays in Landscape mode and the setting that I had made is reverted. Regarding scaling, I can set the display scale to 100% (default) or 200%, successfully. But when I turn on the "Fractional Scaling" slider, the graphics around the edge of the screen immediately increase in size (the icons in the left-hand dock, the text in the top bar), even though I have not changed the scale setting. I have included two screenshots (original screen, and with Fractional Scaling on). There is also some strangeness about whether sliding the Fractional Scaling slider updates the Scale menu to allow more scales - sometimes it does, sometimes it doesn't. When I attempt to set a fractional scale such as 125%, the "Apply" button appears in the upper right corner. When I press that, the display does not actually scale, and a pop-up asks if I want to keep or revert the setting. But looking back at the Displays settings, the Scale has already reverted to 100% (as above with the Orientation). Screenshot enclosed. The display has been rock-solid before this, but now it started showing artifacts, such as previous copies of the Displays window. I've enclosed a screen shot, which shows checkerboard in the screen locations that (in reality) were displaying prior versions of the window. Hmm, examining that screenshot, it looks like the display DID start occupying 25% more space horizontally and vertically, but something about the video scanning versus the screen updating got out of whack. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 BootLog: CasperMD5CheckResult: skip CompositorRunning: None Date: Sat Jul 18 14:00:38 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [A
[Desktop-packages] [Bug 1961010] Re: firefox doesn't let its user control how or when it upgrades
Added screenshot that happens when this bug is triggered. Firefox
refuses to operate normally after this point, just displaying "Sorry. We
just need to do one small thing to keep going. Firefox has just been
updated in the background. Click Restart Firefox to complete the update.
We will restore all your pages, windows and tabs afterwards, so you can
be on your way quickly." over and over.
** Attachment added: "Screenshot from 2022-02-15 20-06-57.png"
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1961010/+attachment/5561208/+files/Screenshot%20from%202022-02-15%2020-06-57.png
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to firefox in Ubuntu.
https://bugs.launchpad.net/bugs/1961010
Title:
firefox doesn't let its user control how or when it upgrades
Status in firefox package in Ubuntu:
New
Bug description:
The Firefox package does not act like ordinary packages. When it is
running, it forcibly downloads upgraded binary versions of itself and
then forces the user to restart Firefox and run the new version.
There used to be a Firefox setting by which the user could control
this, but it has been deliberately removed.
This is problematic in many ways. The first way is that it undermines
the user's control over their own environment. The essential element
of free software is that users control it, it does not control them.
If there is behavior that is undesirable, they can fix it, not just be
subjected to the arbitrary decisions of a distant corporation. For
example, some users require that they have a copy of the source code
that matches each binary package they are running. Firefox's covert
upgrades undermine this local user policy, installing binaries that
have no local matching source code. Other users may be using plugins
or other applications that do not work with later versions of Firefox.
It is not Firefox's decision when to upgrade -- it is the user's or
system operator's.
The second problem is that restarting one's browser has many side effects.
For example, if one window or tab is in a video conference, forcing a restart
of Firefox ejects the user from their video conference. If a video or audio
file is merely playing in another window or tab, it is
interrupted and not necessarily resumed after restart in the right place.
Cookies and permissions (e.g. for NoScript) are not carried forward after a
restart, when they are set to persist only for one session.
If the Mozilla Corporation has firmly and permanently decided that it
doesn't believe in the freedom of the end-users of its software, then
Ubuntu should ship a patched version that DOES give its end-users
freedom, by restoring the setting to disable automated updates.
Firefox would continue to be able to be updated by the usual update-
manager GUI (which IS under the control of the user), apt-get, or by
the user explicitly installing new versions via dpkg or by building
from source code.
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: firefox 97.0+build2-0ubuntu0.20.04.1
ProcVersionSignature: Ubuntu 5.13.0-28.31~20.04.1-generic 5.13.19
Uname: Linux 5.13.0-28-generic x86_64
AddonCompatCheckDisabled: False
ApportVersion: 2.20.11-0ubuntu27.21
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC2: gnu2520 F pulseaudio
/dev/snd/controlC1: gnu2520 F pulseaudio
/dev/snd/controlC0: gnu2520 F pulseaudio
BuildID: 20220202182137
CasperMD5CheckResult: skip
Channel: Unavailable
CurrentDesktop: ubuntu:GNOME
Date: Tue Feb 15 22:55:07 2022
ForcedLayersAccel: False
IncompatibleExtensions:
Global Menu Bar integration - globalm...@ubuntu.com
English (South Africa) Language Pack - langpack-en...@firefox.mozilla.org
English (GB) Language Pack - langpack-en...@firefox.mozilla.org
Default - {972ce4c6-7e08-4474-a285-3208198ce6fd}
InstallationDate: Installed on 2020-05-04 (652 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
IpRoute:
default via 209.16.159.254 dev enp6s0 proto static metric 100
75.101.100.0/24 dev enp6s0 proto kernel scope link src 75.101.100.46 metric
100
169.254.0.0/16 dev enp6s0 scope link metric 1000
172.17.0.0/16 dev docker0 proto kernel scope link src 172.17.0.1 linkdown
209.16.159.0/24 dev enp6s0 proto kernel scope link src 209.16.159.252 metric
100
MostRecentCrashID: bp-f3d4806a-b277-49a1-b452-902072161127
PrefErrors: Unexpected character ',' before close parenthesis @
/usr/lib/firefox/omni.ja:greprefs.js:365
PrefSources: prefs.js
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=en_US.UTF-8
SHELL=/bin/bash
Profiles: Profile0 (Default) - LastVersion=97.0/20220202182137 (In use)
RunningIncompatibleAddons: True
SourcePackage: firefox
Submitted
[Desktop-packages] [Bug 1961010] [NEW] firefox doesn't let its user control how or when it upgrades
Public bug reported:
The Firefox package does not act like ordinary packages. When it is
running, it forcibly downloads upgraded binary versions of itself and
then forces the user to restart Firefox and run the new version. There
used to be a Firefox setting by which the user could control this, but
it has been deliberately removed.
This is problematic in many ways. The first way is that it undermines
the user's control over their own environment. The essential element of
free software is that users control it, it does not control them. If
there is behavior that is undesirable, they can fix it, not just be
subjected to the arbitrary decisions of a distant corporation. For
example, some users require that they have a copy of the source code
that matches each binary package they are running. Firefox's covert
upgrades undermine this local user policy, installing binaries that have
no local matching source code. Other users may be using plugins or
other applications that do not work with later versions of Firefox. It
is not Firefox's decision when to upgrade -- it is the user's or system
operator's.
The second problem is that restarting one's browser has many side effects. For
example, if one window or tab is in a video conference, forcing a restart of
Firefox ejects the user from their video conference. If a video or audio file
is merely playing in another window or tab, it is
interrupted and not necessarily resumed after restart in the right place.
Cookies and permissions (e.g. for NoScript) are not carried forward after a
restart, when they are set to persist only for one session.
If the Mozilla Corporation has firmly and permanently decided that it
doesn't believe in the freedom of the end-users of its software, then
Ubuntu should ship a patched version that DOES give its end-users
freedom, by restoring the setting to disable automated updates. Firefox
would continue to be able to be updated by the usual update-manager GUI
(which IS under the control of the user), apt-get, or by the user
explicitly installing new versions via dpkg or by building from source
code.
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: firefox 97.0+build2-0ubuntu0.20.04.1
ProcVersionSignature: Ubuntu 5.13.0-28.31~20.04.1-generic 5.13.19
Uname: Linux 5.13.0-28-generic x86_64
AddonCompatCheckDisabled: False
ApportVersion: 2.20.11-0ubuntu27.21
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC2: gnu2520 F pulseaudio
/dev/snd/controlC1: gnu2520 F pulseaudio
/dev/snd/controlC0: gnu2520 F pulseaudio
BuildID: 20220202182137
CasperMD5CheckResult: skip
Channel: Unavailable
CurrentDesktop: ubuntu:GNOME
Date: Tue Feb 15 22:55:07 2022
ForcedLayersAccel: False
IncompatibleExtensions:
Global Menu Bar integration - globalm...@ubuntu.com
English (South Africa) Language Pack - langpack-en...@firefox.mozilla.org
English (GB) Language Pack - langpack-en...@firefox.mozilla.org
Default - {972ce4c6-7e08-4474-a285-3208198ce6fd}
InstallationDate: Installed on 2020-05-04 (652 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
IpRoute:
default via 209.16.159.254 dev enp6s0 proto static metric 100
75.101.100.0/24 dev enp6s0 proto kernel scope link src 75.101.100.46 metric
100
169.254.0.0/16 dev enp6s0 scope link metric 1000
172.17.0.0/16 dev docker0 proto kernel scope link src 172.17.0.1 linkdown
209.16.159.0/24 dev enp6s0 proto kernel scope link src 209.16.159.252 metric
100
MostRecentCrashID: bp-f3d4806a-b277-49a1-b452-902072161127
PrefErrors: Unexpected character ',' before close parenthesis @
/usr/lib/firefox/omni.ja:greprefs.js:365
PrefSources: prefs.js
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=en_US.UTF-8
SHELL=/bin/bash
Profiles: Profile0 (Default) - LastVersion=97.0/20220202182137 (In use)
RunningIncompatibleAddons: True
SourcePackage: firefox
SubmittedCrashIDs:
bp-f3d4806a-b277-49a1-b452-902072161127
bp-4da20c64-dde1-4304-9118-238562160914
bp-16b8bc44-ebd0-46e0-a272-95feb2160908
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 01/16/2019
dmi.bios.release: 5.13
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: F25
dmi.board.asset.tag: Default string
dmi.board.name: AX370-Gaming 5
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.board.version: Default string
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: Default string
dmi.chassis.version: Default string
dmi.modalias:
dmi:bvnAmericanMegatrendsInc.:bvrF25:bd01/16/2019:br5.13:svnGigabyteTechnologyCo.,Ltd.:pnAX370-Gaming5:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnAX370-Gaming5:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring:
dmi.product.family: Default string
dmi.product.name: AX370-Gaming 5
dmi.product.sku: Default string
dmi.product.version: Default string
dmi.sys.vendor: Gigabyte Technology Co., L
[Desktop-packages] [Bug 1961010] Re: firefox doesn't let its user control how or when it upgrades
Thank you. Yes, about:buildconfig shows the --disable-updater flag.
And software-properties-gtk --open-tab=2 showed that the setting for
security updates was to download and install them immediately.
I have changed that setting to only download security updates rather
than to install them immediately. This should allow me to schedule
updates to Firefox when its ongoing continuity is not critical.
(Somehow when I run update-manager, it regularly finds "Security
updates" that have not been immediately applied, even though the setting
was formerly "Download and install immediately". Are "Security updates"
in update-manager different from the "security pocket" that Firefox
updates occur in?
Thank you for the diagnosis.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to firefox in Ubuntu.
https://bugs.launchpad.net/bugs/1961010
Title:
firefox doesn't let its user control how or when it upgrades
Status in firefox package in Ubuntu:
Invalid
Bug description:
The Firefox package does not act like ordinary packages. When it is
running, it forcibly downloads upgraded binary versions of itself and
then forces the user to restart Firefox and run the new version.
There used to be a Firefox setting by which the user could control
this, but it has been deliberately removed.
This is problematic in many ways. The first way is that it undermines
the user's control over their own environment. The essential element
of free software is that users control it, it does not control them.
If there is behavior that is undesirable, they can fix it, not just be
subjected to the arbitrary decisions of a distant corporation. For
example, some users require that they have a copy of the source code
that matches each binary package they are running. Firefox's covert
upgrades undermine this local user policy, installing binaries that
have no local matching source code. Other users may be using plugins
or other applications that do not work with later versions of Firefox.
It is not Firefox's decision when to upgrade -- it is the user's or
system operator's.
The second problem is that restarting one's browser has many side effects.
For example, if one window or tab is in a video conference, forcing a restart
of Firefox ejects the user from their video conference. If a video or audio
file is merely playing in another window or tab, it is
interrupted and not necessarily resumed after restart in the right place.
Cookies and permissions (e.g. for NoScript) are not carried forward after a
restart, when they are set to persist only for one session.
If the Mozilla Corporation has firmly and permanently decided that it
doesn't believe in the freedom of the end-users of its software, then
Ubuntu should ship a patched version that DOES give its end-users
freedom, by restoring the setting to disable automated updates.
Firefox would continue to be able to be updated by the usual update-
manager GUI (which IS under the control of the user), apt-get, or by
the user explicitly installing new versions via dpkg or by building
from source code.
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: firefox 97.0+build2-0ubuntu0.20.04.1
ProcVersionSignature: Ubuntu 5.13.0-28.31~20.04.1-generic 5.13.19
Uname: Linux 5.13.0-28-generic x86_64
AddonCompatCheckDisabled: False
ApportVersion: 2.20.11-0ubuntu27.21
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC2: gnu2520 F pulseaudio
/dev/snd/controlC1: gnu2520 F pulseaudio
/dev/snd/controlC0: gnu2520 F pulseaudio
BuildID: 20220202182137
CasperMD5CheckResult: skip
Channel: Unavailable
CurrentDesktop: ubuntu:GNOME
Date: Tue Feb 15 22:55:07 2022
ForcedLayersAccel: False
IncompatibleExtensions:
Global Menu Bar integration - globalm...@ubuntu.com
English (South Africa) Language Pack - langpack-en...@firefox.mozilla.org
English (GB) Language Pack - langpack-en...@firefox.mozilla.org
Default - {972ce4c6-7e08-4474-a285-3208198ce6fd}
InstallationDate: Installed on 2020-05-04 (652 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
IpRoute:
default via 209.16.159.254 dev enp6s0 proto static metric 100
75.101.100.0/24 dev enp6s0 proto kernel scope link src 75.101.100.46 metric
100
169.254.0.0/16 dev enp6s0 scope link metric 1000
172.17.0.0/16 dev docker0 proto kernel scope link src 172.17.0.1 linkdown
209.16.159.0/24 dev enp6s0 proto kernel scope link src 209.16.159.252 metric
100
MostRecentCrashID: bp-f3d4806a-b277-49a1-b452-902072161127
PrefErrors: Unexpected character ',' before close parenthesis @
/usr/lib/firefox/omni.ja:greprefs.js:365
PrefSources: prefs.js
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=en_US.UTF-8
SHELL=/bin/bash
Profil
[Desktop-packages] [Bug 876107] [NEW] relnotes in 11.10 say to install gnome-panel but it doesn't install
Public bug reported: I hate Unity and am only interested in running new Ubuntu's if I can install gnome. The release notes here: https://wiki.ubuntu.com/OneiricOcelot/ReleaseNotes?action=show&redirect=OneiricOcelot%2FTechnicalOverview say: GNOME 3.2 is included and is a major upgrade from GNOME 2.32 included in Ubuntu 11.04. GNOME Classic is no longer installed by default, but can be enabled after installation completes by installing gnome-panel THIS IS FALSE. It's easy to reproduce. While running the Live image (desktop-i386) from USB stick, I got this result: apt-get install gnome-panel Reading package lists... Done Building dependency tree Reading state information... Done Package gnome-panel is not available, but is referred to by another package. This may mean that the package is missing, has been obsoleted, or is only available from another source E: Package 'gnome-panel' has no installation candidate The same result occurs whether or not I have run "apt-get update". To Fix: (1) Make gnome-panel installable from the repos. AND/OR (2) Change the release notes so that they don't tell people to do things that fail. Best of all would be: (3) Quit with the Not-Invented-Here attitude, don't force the Unity crud on everyone; make a simple way to delete Unity and install Gnome by default (or merely INSTALL it by default, next to Unity, and let people pick it in the login screen). ** Affects: gnome-panel (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-panel in Ubuntu. https://bugs.launchpad.net/bugs/876107 Title: relnotes in 11.10 say to install gnome-panel but it doesn't install Status in “gnome-panel” package in Ubuntu: New Bug description: I hate Unity and am only interested in running new Ubuntu's if I can install gnome. The release notes here: https://wiki.ubuntu.com/OneiricOcelot/ReleaseNotes?action=show&redirect=OneiricOcelot%2FTechnicalOverview say: GNOME 3.2 is included and is a major upgrade from GNOME 2.32 included in Ubuntu 11.04. GNOME Classic is no longer installed by default, but can be enabled after installation completes by installing gnome-panel THIS IS FALSE. It's easy to reproduce. While running the Live image (desktop-i386) from USB stick, I got this result: apt-get install gnome-panel Reading package lists... Done Building dependency tree Reading state information... Done Package gnome-panel is not available, but is referred to by another package. This may mean that the package is missing, has been obsoleted, or is only available from another source E: Package 'gnome-panel' has no installation candidate The same result occurs whether or not I have run "apt-get update". To Fix: (1) Make gnome-panel installable from the repos. AND/OR (2) Change the release notes so that they don't tell people to do things that fail. Best of all would be: (3) Quit with the Not-Invented-Here attitude, don't force the Unity crud on everyone; make a simple way to delete Unity and install Gnome by default (or merely INSTALL it by default, next to Unity, and let people pick it in the login screen). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-panel/+bug/876107/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
