[Desktop-packages] [Bug 1953052] Re: In Jammy sound level reset after reboot
On my desktop after a lot of new updates the sound level is NOT reset at reboot. I see pipewire and pulseaudio are both installed but i don't know if they are active. corrado@corrado-p5-jj-0203:~$ dpkg -l | grep pipewire ii gstreamer1.0-pipewire:amd640.3.45-1 amd64GStreamer 1.0 plugin for the PipeWire multimedia server ii libpipewire-0.3-0:amd640.3.45-1 amd64libraries for the PipeWire multimedia server ii libpipewire-0.3-common 0.3.45-1 all libraries for the PipeWire multimedia server - common files ii libpipewire-0.3-modules:amd64 0.3.45-1 amd64libraries for the PipeWire multimedia server - modules ii pipewire:amd64 0.3.45-1 amd64audio and video processing engine multimedia server ii pipewire-bin 0.3.45-1 amd64PipeWire multimedia server - programs ii pipewire-media-session 0.4.1-2 amd64example session manager for PipeWire corrado@corrado-p5-jj-0203:~$ apt policy pipewire pulseaudio pipewire: Installed: 0.3.45-1 Candidate: 0.3.45-1 Version table: *** 0.3.45-1 500 500 http://archive.ubuntu.com/ubuntu jammy/main amd64 Packages 100 /var/lib/dpkg/status pulseaudio: Installed: 1:15.0+dfsg1-1ubuntu6 Candidate: 1:15.0+dfsg1-1ubuntu6 Version table: *** 1:15.0+dfsg1-1ubuntu6 500 500 http://archive.ubuntu.com/ubuntu jammy/main amd64 Packages 100 /var/lib/dpkg/status corrado@corrado-p5-jj-0203:~$ and from system monitor i see both are active. see attachment ** Attachment added: "Screenshot from 2022-02-18 08-46-29.png" https://bugs.launchpad.net/ubuntu/+source/alsa-utils/+bug/1953052/+attachment/5561750/+files/Screenshot%20from%202022-02-18%2008-46-29.png -- 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/1953052 Title: In Jammy sound level reset after reboot Status in alsa-utils package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Confirmed Bug description: After reboot sound level is reset ignoring the level set in previous session. I manually set the sound output level at next boot the sound is set at a different level (about 70%) Expected: the sound level is persistent across power off/on What happens : sound level is set at a different level (about 70%) Note: this problem does not occur on different partitions of same PC running Ubuntu 20.04 or 21.10 corrado@corrado-p3-jj-1130:~$ apt policy gnome-control-center gnome-control-center: Installed: 1:41.1-1ubuntu1 Candidate: 1:41.1-1ubuntu1 Version table: *** 1:41.1-1ubuntu1 500 500 http://archive.ubuntu.com/ubuntu jammy/main amd64 Packages 100 /var/lib/dpkg/status corrado@corrado-p3-jj-1130:~$ inxi -Fx System:Host: corrado-p3-jj-1130 Kernel: 5.13.0-19-generic x86_64 bits: 64 compiler: gcc v: 11.2.0 Desktop: GNOME 40.5 Distro: Ubuntu 22.04 (Jammy Jellyfish) Machine: Type: Laptop System: Dell product: Inspiron 3793 v: N/A serial: Mobo: Dell model: 0C1PF2 v: A00 serial: UEFI: Dell v: 1.5.0 date: 12/17/2019 Battery: ID-1: BAT0 charge: 13.9 Wh (42.1%) condition: 33.0/42.0 Wh (78.7%) volts: 11.3 min: 11.4 model: SWD-ATL3.618 DELL WJPC403 status: Discharging CPU: Info: Quad Core model: Intel Core i5-1035G1 bits: 64 type: MT MCP arch: Ice Lake rev: 5 cache: L2: 6 MiB flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 19046 Speed: 968 MHz min/max: 400/1000 MHz Core speeds (MHz): 1: 968 2: 710 3: 706 4: 714 5: 966 6: 712 7: 724 8: 821 Graphics: Device-1: Intel Iris Plus Graphics G1 vendor: Dell driver: i915 v: kernel bus-ID: 00:02.0 Device-2: Realtek Integrated_Webcam_HD type: USB driver: uvcvideo bus-ID: 1-6:3 Display: wayland server: X.Org 1.21.1.2 compositor: gnome-shell driver: loaded: i915 note: n/a (using device driver) resolution: 1920x1080~60Hz OpenGL: renderer: Mesa Intel UHD Graphics (ICL GT1) v: 4.6 Mesa 21.2.2 direct render: Yes Audio: Device-1: Intel Ice Lake-LP Smart Sound Audio vendor: Dell driver: snd_hda_intel v: kernel bus-ID: 00:1f.3 Sound Server-1: ALSA v: k5.13.0-19-generic running: yes Sound Server-2: PulseAudio v: 15.0 running: yes Sound Server-3: PipeWire v: 0.3.40 running: yes Network: Device-1: Realtek RTL810xE PCI Express Fast Ethernet vendor: Dell driver: r8169 v: kernel port: 3000 bus-ID: 01:00.0 IF: enp1s0 state: down
[Desktop-packages] [Bug 1953052] Re: In Jammy sound level reset after reboot
Sebastien, if distribution is intended to provide pipewire function for video only, there is no need to install audio parts. At very least 'with-pulse' 'with-jack' and other files directly or transitively enabling 'with-audio' pipewire parts should not be installed so pipewire media session daemon does not get hold of hardware controls. Alternatively, if distribution is intended to provide pulseaudio interface via pipewire, that should be properly switching pulseaudio activation socket to pipewire-pulse, and/or disabling or uninstalling pulseaudio daemon and maybe disabling pulseaudio autospawn in client.conf -- 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/1953052 Title: In Jammy sound level reset after reboot Status in alsa-utils package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Confirmed Bug description: After reboot sound level is reset ignoring the level set in previous session. I manually set the sound output level at next boot the sound is set at a different level (about 70%) Expected: the sound level is persistent across power off/on What happens : sound level is set at a different level (about 70%) Note: this problem does not occur on different partitions of same PC running Ubuntu 20.04 or 21.10 corrado@corrado-p3-jj-1130:~$ apt policy gnome-control-center gnome-control-center: Installed: 1:41.1-1ubuntu1 Candidate: 1:41.1-1ubuntu1 Version table: *** 1:41.1-1ubuntu1 500 500 http://archive.ubuntu.com/ubuntu jammy/main amd64 Packages 100 /var/lib/dpkg/status corrado@corrado-p3-jj-1130:~$ inxi -Fx System:Host: corrado-p3-jj-1130 Kernel: 5.13.0-19-generic x86_64 bits: 64 compiler: gcc v: 11.2.0 Desktop: GNOME 40.5 Distro: Ubuntu 22.04 (Jammy Jellyfish) Machine: Type: Laptop System: Dell product: Inspiron 3793 v: N/A serial: Mobo: Dell model: 0C1PF2 v: A00 serial: UEFI: Dell v: 1.5.0 date: 12/17/2019 Battery: ID-1: BAT0 charge: 13.9 Wh (42.1%) condition: 33.0/42.0 Wh (78.7%) volts: 11.3 min: 11.4 model: SWD-ATL3.618 DELL WJPC403 status: Discharging CPU: Info: Quad Core model: Intel Core i5-1035G1 bits: 64 type: MT MCP arch: Ice Lake rev: 5 cache: L2: 6 MiB flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 19046 Speed: 968 MHz min/max: 400/1000 MHz Core speeds (MHz): 1: 968 2: 710 3: 706 4: 714 5: 966 6: 712 7: 724 8: 821 Graphics: Device-1: Intel Iris Plus Graphics G1 vendor: Dell driver: i915 v: kernel bus-ID: 00:02.0 Device-2: Realtek Integrated_Webcam_HD type: USB driver: uvcvideo bus-ID: 1-6:3 Display: wayland server: X.Org 1.21.1.2 compositor: gnome-shell driver: loaded: i915 note: n/a (using device driver) resolution: 1920x1080~60Hz OpenGL: renderer: Mesa Intel UHD Graphics (ICL GT1) v: 4.6 Mesa 21.2.2 direct render: Yes Audio: Device-1: Intel Ice Lake-LP Smart Sound Audio vendor: Dell driver: snd_hda_intel v: kernel bus-ID: 00:1f.3 Sound Server-1: ALSA v: k5.13.0-19-generic running: yes Sound Server-2: PulseAudio v: 15.0 running: yes Sound Server-3: PipeWire v: 0.3.40 running: yes Network: Device-1: Realtek RTL810xE PCI Express Fast Ethernet vendor: Dell driver: r8169 v: kernel port: 3000 bus-ID: 01:00.0 IF: enp1s0 state: down mac: 98:e7:43:59:19:19 Device-2: Qualcomm Atheros QCA9377 802.11ac Wireless Network Adapter vendor: Dell driver: ath10k_pci v: kernel bus-ID: 02:00.0 IF: wlp2s0 state: up mac: d8:12:65:b8:21:b9 Bluetooth: Device-1: Qualcomm Atheros type: USB driver: btusb v: 0.8 bus-ID: 1-10:4 Report: hciconfig ID: hci0 rfk-id: 0 state: down bt-service: enabled,running rfk-block: hardware: no software: yes address: D8:12:65:B8:21:BA Drives:Local Storage: total: 942.7 GiB used: 11.77 GiB (1.2%) ID-1: /dev/nvme0n1 vendor: Toshiba model: KBG40ZNS512G NVMe KIOXIA 512GB size: 476.94 GiB temp: 24.9 C ID-2: /dev/sda vendor: Crucial model: CT500MX500SSD1 size: 465.76 GiB Partition: ID-1: / size: 46.95 GiB used: 11.73 GiB (25.0%) fs: ext4 dev: /dev/nvme0n1p3 ID-2: /boot/efi size: 246 MiB used: 46.4 MiB (18.9%) fs: vfat dev: /dev/nvme0n1p1 Swap: Alert: No swap data was found. Sensors: System Temperatures: cpu: 27.8 C mobo: N/A Fan Speeds (RPM): cpu: 0 Info: Processes: 263 Uptime: 31m Memory: 15.4 GiB used: 2.45 GiB (15.9%) Init: systemd runlevel: 5 Compilers: gcc: N/A Packages: 1785 Shell: Bash v: 5.1.12 inxi: 3.3.07 corrado@corrado-p3-jj-1130:~$ --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu74 Architecture: amd64
[Desktop-packages] [Bug 1953052] Re: In Jammy sound level reset after reboot
I can confirm that after stopping pipewire temporarily by: $ systemctl --user stop pipewire.socket pipewire.service The volume level is properly recovered across plugging in and out a headset for example, which is good. Both pulseaudio and pipewire are installed out of the box and running if I'm not mistaken. $ apt show pulseaudio |& grep Task: Task: ubuntu-desktop-minimal, ubuntu-desktop, ubuntu-desktop-raspi, kubuntu-desktop, xubuntu-core, xubuntu-desktop, lubuntu-desktop, ubuntustudio-desktop-core, ubuntustudio-desktop, ubuntukylin-desktop, ubuntu-mate-core, ubuntu-mate-desktop, ubuntu-budgie-desktop, ubuntu-budgie-desktop-raspi $ apt show pipewire |& grep Task: Task: ubuntu-desktop-minimal, ubuntu-desktop, ubuntu-desktop-raspi, kubuntu-desktop, xubuntu-core, xubuntu-desktop, lubuntu-desktop, ubuntustudio-desktop-core, ubuntustudio-desktop, ubuntukylin-desktop, ubuntu-mate-core, ubuntu-mate-desktop, ubuntu-budgie-desktop, ubuntu-budgie-desktop-raspi -- 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/1953052 Title: In Jammy sound level reset after reboot Status in alsa-utils package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Confirmed Bug description: After reboot sound level is reset ignoring the level set in previous session. I manually set the sound output level at next boot the sound is set at a different level (about 70%) Expected: the sound level is persistent across power off/on What happens : sound level is set at a different level (about 70%) Note: this problem does not occur on different partitions of same PC running Ubuntu 20.04 or 21.10 corrado@corrado-p3-jj-1130:~$ apt policy gnome-control-center gnome-control-center: Installed: 1:41.1-1ubuntu1 Candidate: 1:41.1-1ubuntu1 Version table: *** 1:41.1-1ubuntu1 500 500 http://archive.ubuntu.com/ubuntu jammy/main amd64 Packages 100 /var/lib/dpkg/status corrado@corrado-p3-jj-1130:~$ inxi -Fx System:Host: corrado-p3-jj-1130 Kernel: 5.13.0-19-generic x86_64 bits: 64 compiler: gcc v: 11.2.0 Desktop: GNOME 40.5 Distro: Ubuntu 22.04 (Jammy Jellyfish) Machine: Type: Laptop System: Dell product: Inspiron 3793 v: N/A serial: Mobo: Dell model: 0C1PF2 v: A00 serial: UEFI: Dell v: 1.5.0 date: 12/17/2019 Battery: ID-1: BAT0 charge: 13.9 Wh (42.1%) condition: 33.0/42.0 Wh (78.7%) volts: 11.3 min: 11.4 model: SWD-ATL3.618 DELL WJPC403 status: Discharging CPU: Info: Quad Core model: Intel Core i5-1035G1 bits: 64 type: MT MCP arch: Ice Lake rev: 5 cache: L2: 6 MiB flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 19046 Speed: 968 MHz min/max: 400/1000 MHz Core speeds (MHz): 1: 968 2: 710 3: 706 4: 714 5: 966 6: 712 7: 724 8: 821 Graphics: Device-1: Intel Iris Plus Graphics G1 vendor: Dell driver: i915 v: kernel bus-ID: 00:02.0 Device-2: Realtek Integrated_Webcam_HD type: USB driver: uvcvideo bus-ID: 1-6:3 Display: wayland server: X.Org 1.21.1.2 compositor: gnome-shell driver: loaded: i915 note: n/a (using device driver) resolution: 1920x1080~60Hz OpenGL: renderer: Mesa Intel UHD Graphics (ICL GT1) v: 4.6 Mesa 21.2.2 direct render: Yes Audio: Device-1: Intel Ice Lake-LP Smart Sound Audio vendor: Dell driver: snd_hda_intel v: kernel bus-ID: 00:1f.3 Sound Server-1: ALSA v: k5.13.0-19-generic running: yes Sound Server-2: PulseAudio v: 15.0 running: yes Sound Server-3: PipeWire v: 0.3.40 running: yes Network: Device-1: Realtek RTL810xE PCI Express Fast Ethernet vendor: Dell driver: r8169 v: kernel port: 3000 bus-ID: 01:00.0 IF: enp1s0 state: down mac: 98:e7:43:59:19:19 Device-2: Qualcomm Atheros QCA9377 802.11ac Wireless Network Adapter vendor: Dell driver: ath10k_pci v: kernel bus-ID: 02:00.0 IF: wlp2s0 state: up mac: d8:12:65:b8:21:b9 Bluetooth: Device-1: Qualcomm Atheros type: USB driver: btusb v: 0.8 bus-ID: 1-10:4 Report: hciconfig ID: hci0 rfk-id: 0 state: down bt-service: enabled,running rfk-block: hardware: no software: yes address: D8:12:65:B8:21:BA Drives:Local Storage: total: 942.7 GiB used: 11.77 GiB (1.2%) ID-1: /dev/nvme0n1 vendor: Toshiba model: KBG40ZNS512G NVMe KIOXIA 512GB size: 476.94 GiB temp: 24.9 C ID-2: /dev/sda vendor: Crucial model: CT500MX500SSD1 size: 465.76 GiB Partition: ID-1: / size: 46.95 GiB used: 11.73 GiB (25.0%) fs: ext4 dev: /dev/nvme0n1p3 ID-2: /boot/efi size: 246 MiB used: 46.4 MiB (18.9%) fs: vfat dev: /dev/nvme0n1p1 Swap: Alert: No swap data was found. Sensors: System Temperatures: cpu: 27.8 C mobo:
[Desktop-packages] [Bug 1618041] Re: Cannot login to Ubuntu One Single Sign-On Account to install Snaps
*** This bug is a duplicate of bug 1616943 *** https://bugs.launchpad.net/bugs/1616943 same here on brand new 20.04 LTS running in VM on HyoerV SSO and Ubuntu One accounts work fine on webs, but Livepatch setup lets me enter SSO initally, then prompts for local admin, before coming back to SSO sign-in screen with incorrect email/password -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1618041 Title: Cannot login to Ubuntu One Single Sign-On Account to install Snaps Status in Ubuntu GNOME: Confirmed Status in gnome-software package in Ubuntu: Confirmed Bug description: I keep getting "Incorrect email or password" even though I know for a fact the email and password are correct. I am able to sign into Ubuntu One just fine on a web browser. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-gnome/+bug/1618041/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1944388] Re: gnome-shell crashed on logout with SIGSEGV in [strlen() from] g_strdup() from g_error_copy() from meta_kms_page_flip_data_discard_in_impl() from g_list_foreach()
** Summary changed: - gnome-shell crashed with SIGSEGV in [strlen() from] g_strdup() from g_error_copy() from meta_kms_page_flip_data_discard_in_impl() from g_list_foreach() + gnome-shell crashed on logout with SIGSEGV in [strlen() from] g_strdup() from g_error_copy() from meta_kms_page_flip_data_discard_in_impl() from g_list_foreach() -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1944388 Title: gnome-shell crashed on logout with SIGSEGV in [strlen() from] g_strdup() from g_error_copy() from meta_kms_page_flip_data_discard_in_impl() from g_list_foreach() Status in Mutter: Unknown Status in gnome-shell package in Ubuntu: Fix Released Status in mutter package in Ubuntu: Confirmed Bug description: gnome-shell crashed with SIGSEGV in g_strdup() ProblemType: Crash DistroRelease: Ubuntu 21.10 Package: gnome-shell 40.2-1ubuntu6 Uname: Linux 5.13.0-16-generic x86_64 ApportVersion: 2.20.11-0ubuntu69 Architecture: amd64 CasperMD5CheckResult: unknown CrashCounter: 1 CurrentDesktop: ubuntu:GNOME Date: Tue Sep 21 02:58:40 2021 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell ProcCmdline: /usr/bin/gnome-shell RelatedPackageVersions: mutter-common 40.2.1-1ubuntu1 Signal: 11 SourcePackage: gnome-shell StacktraceTop: g_strdup () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_error_copy () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () from /lib/x86_64-linux-gnu/libmutter-8.so.0 g_list_foreach () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () from /lib/x86_64-linux-gnu/libmutter-8.so.0 Title: gnome-shell crashed with SIGSEGV in g_strdup() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo wireshark separator: To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1944388/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1944113]
*** Bug 147172 has been marked as a duplicate of this bug. *** -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1944113 Title: Many UI elements (list box, drop down) don't work at all in kf5 environment Status in LibreOffice: Confirmed Status in libreoffice package in Ubuntu: Fix Released Bug description: Many UI elements (list box, drop down) don't work at all in kf5 environment. This makes LO unusable. For example, try to insert a table from standard toolbar in LO Writer – nothing inserted. Same happens with other drop down elements (styles, font family, font size, font color, font highlight, etc). Bug reports at LO's bug tracker: https://bugs.documentfoundation.org/show_bug.cgi?id=144037 https://bugs.documentfoundation.org/show_bug.cgi?id=144562 https://gerrit.libreoffice.org/c/core/+/122116 Operating System: Kubuntu 20.04 KDE Plasma Version: 5.18.5 KDE Frameworks Version: 5.68.0 Qt Version: 5.12.8 Kernel Version: 5.11.0-34-generic OS Type: 64-bit Processors: 4 × Intel® Core™ i5-4310U CPU @ 2.00GHz Memory: 7,7 GiB Version: 7.2.1.2 / LibreOffice Community Build ID: 20(Build:2) CPU threads: 4; OS: Linux 5.11; UI render: default; VCL: kf5 (cairo+xcb) Locale: hu-HU (hu_HU.UTF-8); UI: hu-HU Ubuntu package version: 1:7.2.1~rc2-0ubuntu0.20.04.1~lo3 Calc: threaded To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1944113/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1944113]
Same problem using Debian kde 5.23.5 with wayland. My libreoffice version is 7.3.1. A temporary solution is to set the environment variable QT_QPA_PLATFORM=xcb before running libreoffice. So the command is QT_QPA_PLATFORM=xcb libreoffice. And this will make the program work just fine. Anyway hope the developer fix the issue soon. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1944113 Title: Many UI elements (list box, drop down) don't work at all in kf5 environment Status in LibreOffice: Confirmed Status in libreoffice package in Ubuntu: Fix Released Bug description: Many UI elements (list box, drop down) don't work at all in kf5 environment. This makes LO unusable. For example, try to insert a table from standard toolbar in LO Writer – nothing inserted. Same happens with other drop down elements (styles, font family, font size, font color, font highlight, etc). Bug reports at LO's bug tracker: https://bugs.documentfoundation.org/show_bug.cgi?id=144037 https://bugs.documentfoundation.org/show_bug.cgi?id=144562 https://gerrit.libreoffice.org/c/core/+/122116 Operating System: Kubuntu 20.04 KDE Plasma Version: 5.18.5 KDE Frameworks Version: 5.68.0 Qt Version: 5.12.8 Kernel Version: 5.11.0-34-generic OS Type: 64-bit Processors: 4 × Intel® Core™ i5-4310U CPU @ 2.00GHz Memory: 7,7 GiB Version: 7.2.1.2 / LibreOffice Community Build ID: 20(Build:2) CPU threads: 4; OS: Linux 5.11; UI render: default; VCL: kf5 (cairo+xcb) Locale: hu-HU (hu_HU.UTF-8); UI: hu-HU Ubuntu package version: 1:7.2.1~rc2-0ubuntu0.20.04.1~lo3 Calc: threaded To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1944113/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1960679] Re: Dekstop icon extension can't handle moving icons to a to-be-empty spot
** Changed in: gnome-shell-extension-desktop-icons-ng (Ubuntu) Status: Incomplete => New ** Bug watch added: gitlab.com/rastersoft/desktop-icons-ng/-/issues #208 https://gitlab.com/rastersoft/desktop-icons-ng/-/issues/208 ** Also affects: gnome-shell-extension-desktop-icons-ng via https://gitlab.com/rastersoft/desktop-icons-ng/-/issues/208 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-desktop-icons-ng in Ubuntu. https://bugs.launchpad.net/bugs/1960679 Title: Dekstop icon extension can't handle moving icons to a to-be-empty spot Status in Gnome Shell Extension Desktop Icons Ng: Unknown Status in gnome-shell-extension-desktop-icons-ng package in Ubuntu: New Bug description: You can easily test this by setting up 2 or more icons on the desktop in any way then moving them in such a way that one of the icons will be moved to the spot where another icon currently is, but that other icon is also being moved by the same action to another empty spot. Behaviour: icons that are moved to the spot described above will stay in place Note: it has to do with the order the icons are moved so if you try moving icon 1 where icon 2 currently is and they are both moved correctly, try to move them so that icon 2 is moved where icon 1 is and it will have issues Ubuntu 21.10 Extension 20-0ubuntu3 To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell-extension-desktop-icons-ng/+bug/1960679/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1959888] Re: Wayland sessions can't use external monitors that are connected to an Nvidia GPU with the proprietary driver
While everything is working with the external monitor please run: xrandr > xrandr.txt and attach the resulting text file here. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1959888 Title: Wayland sessions can't use external monitors that are connected to an Nvidia GPU with the proprietary driver Status in mutter package in Ubuntu: Incomplete Bug description: When an external display is connected to my laptop, running Ubuntu 22.04, the display is detected and I am sent to the login screen. After logging in again, the display is not running, although the primary laptop display works fine. The external monitor is looking for connection in that moment, which it never founds. The bug is tested on two Samsung monitors: S24R350FHUXEN and S22F350FHU. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12 Uname: Linux 5.15.0-18-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 495.46 Wed Oct 27 16:31:33 UTC 2021 GCC version: gcc version 11.2.0 (Ubuntu 11.2.0-14ubuntu1) ApportVersion: 2.20.11-0ubuntu76 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Feb 3 13:25:04 2022 DistUpgraded: 2022-01-13 15:37:13,056 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: jammy DistroVariant: ubuntu DkmsStatus: nvidia/495.46, 5.15.0-17-generic, x86_64: installed nvidia/495.46, 5.15.0-18-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation CoffeeLake-H GT2 [UHD Graphics 630] [8086:3e9b] (prog-if 00 [VGA controller]) Subsystem: Dell CoffeeLake-H GT2 [UHD Graphics 630] [1028:086f] Subsystem: Dell GP107M [GeForce GTX 1050 Ti Mobile] [1028:086f] InstallationDate: Installed on 2021-09-09 (146 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) MachineType: Dell Inc. G3 3579 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-18-generic root=UUID=fd3be223-e609-4a8d-97fb-31ee2f754766 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to jammy on 2022-01-13 (20 days ago) dmi.bios.date: 04/20/2021 dmi.bios.release: 1.15 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.15.0 dmi.board.name: 0M5H57 dmi.board.vendor: Dell Inc. dmi.board.version: A05 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.15.0:bd04/20/2021:br1.15:svnDellInc.:pnG33579:pvr:rvnDellInc.:rn0M5H57:rvrA05:cvnDellInc.:ct10:cvr:sku086F: dmi.product.family: GSeries dmi.product.name: G3 3579 dmi.product.sku: 086F dmi.sys.vendor: Dell Inc. nvidia-settings: ERROR: Unable to find display on any available system ERROR: Unable to find display on any available system version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.109-2ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.2-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 21.2.2-1ubuntu1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.14-1ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-1ubuntu2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1959888/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1959888] Re: Wayland sessions can't use external monitors that are connected to an Nvidia GPU with the proprietary driver
That's great, but can you verify it's a Wayland session you're still using? Or has it switched to Xorg? ** Changed in: mutter (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1959888 Title: Wayland sessions can't use external monitors that are connected to an Nvidia GPU with the proprietary driver Status in mutter package in Ubuntu: Incomplete Bug description: When an external display is connected to my laptop, running Ubuntu 22.04, the display is detected and I am sent to the login screen. After logging in again, the display is not running, although the primary laptop display works fine. The external monitor is looking for connection in that moment, which it never founds. The bug is tested on two Samsung monitors: S24R350FHUXEN and S22F350FHU. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12 Uname: Linux 5.15.0-18-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 495.46 Wed Oct 27 16:31:33 UTC 2021 GCC version: gcc version 11.2.0 (Ubuntu 11.2.0-14ubuntu1) ApportVersion: 2.20.11-0ubuntu76 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Feb 3 13:25:04 2022 DistUpgraded: 2022-01-13 15:37:13,056 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: jammy DistroVariant: ubuntu DkmsStatus: nvidia/495.46, 5.15.0-17-generic, x86_64: installed nvidia/495.46, 5.15.0-18-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation CoffeeLake-H GT2 [UHD Graphics 630] [8086:3e9b] (prog-if 00 [VGA controller]) Subsystem: Dell CoffeeLake-H GT2 [UHD Graphics 630] [1028:086f] Subsystem: Dell GP107M [GeForce GTX 1050 Ti Mobile] [1028:086f] InstallationDate: Installed on 2021-09-09 (146 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) MachineType: Dell Inc. G3 3579 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-18-generic root=UUID=fd3be223-e609-4a8d-97fb-31ee2f754766 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to jammy on 2022-01-13 (20 days ago) dmi.bios.date: 04/20/2021 dmi.bios.release: 1.15 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.15.0 dmi.board.name: 0M5H57 dmi.board.vendor: Dell Inc. dmi.board.version: A05 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.15.0:bd04/20/2021:br1.15:svnDellInc.:pnG33579:pvr:rvnDellInc.:rn0M5H57:rvrA05:cvnDellInc.:ct10:cvr:sku086F: dmi.product.family: GSeries dmi.product.name: G3 3579 dmi.product.sku: 086F dmi.sys.vendor: Dell Inc. nvidia-settings: ERROR: Unable to find display on any available system ERROR: Unable to find display on any available system version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.109-2ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.2-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 21.2.2-1ubuntu1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.14-1ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-1ubuntu2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1959888/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[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
[Desktop-packages] [Bug 1947210]
I do not know how to add "Wayland" to the bug summary, nor do I know how to flag this for possible closing. -- 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/1947210 Title: Firefox Snap can't copy or drag in Wayland Status in Mozilla Firefox: Confirmed Status in firefox package in Ubuntu: Fix Released Bug description: I just upgraded to 21.10 Impish which supplies Firefox 93.0-1 via snap. I could not copy and paste to and from the browser. I logged out of Wayland and into Xorg and copy & paste works. Already reported at https://bugzilla.mozilla.org/show_bug.cgi?id=1729901 so it's a known issue. I wanted to report it here so it gets into the Impish release notes or wherever along with the workaround. To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1947210/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1947210]
I am not the bug reporter but I am finding that copy / paste & drag / drop in the Firefox snap is working under Wayland now. The current stable release of the snap of Firefox is 97.0; I don't know when it started working as I was using a .deb version of Firefox under xorg for other reasons. -- 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/1947210 Title: Firefox Snap can't copy or drag in Wayland Status in Mozilla Firefox: Confirmed Status in firefox package in Ubuntu: Fix Released Bug description: I just upgraded to 21.10 Impish which supplies Firefox 93.0-1 via snap. I could not copy and paste to and from the browser. I logged out of Wayland and into Xorg and copy & paste works. Already reported at https://bugzilla.mozilla.org/show_bug.cgi?id=1729901 so it's a known issue. I wanted to report it here so it gets into the Impish release notes or wherever along with the workaround. To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1947210/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1961344] [NEW] Sound works in LIVE cd but not in Installation
Public bug reported: Hello, I am using a Nextbook Flexx 10.1 I have attempted to use multiple fixes described online to no avail. It seems that when using the live mode off of the boot flash drive audio works fine. Alsamixer reports bytcr-rt5640 as sound card. however once installed no audio. alsamixer reports sof-bytcht rt5640 as card selected ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.13.0-30.33~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-30-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: delgadb2 1271 F pulseaudio /dev/snd/controlC0: delgadb2 1271 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Feb 17 12:51:34 2022 InstallationDate: Installed on 2022-02-17 (0 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:rt5640 failed Symptom_Card: Built-in Audio - sof-bytcht rt5640 Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: delgadb2 1271 F pulseaudio /dev/snd/controlC0: delgadb2 1271 F pulseaudio Symptom_Type: No sound at all Title: [SOF - sof-bytcht rt5640, playback] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/09/2015 dmi.bios.release: 18.18 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: NX1015.2.02.017 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: NXM1015BFP dmi.board.vendor: YIFANG dmi.board.version: 1.2 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 0.0 dmi.modalias: dmi:bvnINSYDECorp.:bvrNX1015.2.02.017:bd11/09/2015:br18.18:efr0.0:svnYIFANG:pnNXW101QC232T:pvrType1-TBDbyOEM:rvnYIFANG:rnNXM1015BFP:rvr1.2:cvnChassisManufacturer:ct10:cvrChassisVersion:skuType1-SKU0: dmi.product.family: M1015BFP T10220300 dmi.product.name: NXW101QC232T dmi.product.sku: Type1 - SKU0 dmi.product.version: Type1 - TBD by OEM dmi.sys.vendor: YIFANG ** Affects: alsa-driver (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 alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1961344 Title: Sound works in LIVE cd but not in Installation Status in alsa-driver package in Ubuntu: New Bug description: Hello, I am using a Nextbook Flexx 10.1 I have attempted to use multiple fixes described online to no avail. It seems that when using the live mode off of the boot flash drive audio works fine. Alsamixer reports bytcr-rt5640 as sound card. however once installed no audio. alsamixer reports sof-bytcht rt5640 as card selected ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.13.0-30.33~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-30-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: delgadb2 1271 F pulseaudio /dev/snd/controlC0: delgadb2 1271 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Feb 17 12:51:34 2022 InstallationDate: Installed on 2022-02-17 (0 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:rt5640 failed Symptom_Card: Built-in Audio - sof-bytcht rt5640 Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: delgadb2 1271 F pulseaudio /dev/snd/controlC0: delgadb2 1271 F pulseaudio Symptom_Type: No sound at all Title: [SOF - sof-bytcht rt5640, playback] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/09/2015 dmi.bios.release: 18.18 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: NX1015.2.02.017 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: NXM1015BFP dmi.board.vendor: YIFANG dmi.board.version: 1.2 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 0.0 dmi.modalias:
[Desktop-packages] [Bug 1953052] Re: In Jammy sound level reset after reboot
what's the output of $ dpkg -l | grep pipewire ? -- 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/1953052 Title: In Jammy sound level reset after reboot Status in alsa-utils package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Confirmed Bug description: After reboot sound level is reset ignoring the level set in previous session. I manually set the sound output level at next boot the sound is set at a different level (about 70%) Expected: the sound level is persistent across power off/on What happens : sound level is set at a different level (about 70%) Note: this problem does not occur on different partitions of same PC running Ubuntu 20.04 or 21.10 corrado@corrado-p3-jj-1130:~$ apt policy gnome-control-center gnome-control-center: Installed: 1:41.1-1ubuntu1 Candidate: 1:41.1-1ubuntu1 Version table: *** 1:41.1-1ubuntu1 500 500 http://archive.ubuntu.com/ubuntu jammy/main amd64 Packages 100 /var/lib/dpkg/status corrado@corrado-p3-jj-1130:~$ inxi -Fx System:Host: corrado-p3-jj-1130 Kernel: 5.13.0-19-generic x86_64 bits: 64 compiler: gcc v: 11.2.0 Desktop: GNOME 40.5 Distro: Ubuntu 22.04 (Jammy Jellyfish) Machine: Type: Laptop System: Dell product: Inspiron 3793 v: N/A serial: Mobo: Dell model: 0C1PF2 v: A00 serial: UEFI: Dell v: 1.5.0 date: 12/17/2019 Battery: ID-1: BAT0 charge: 13.9 Wh (42.1%) condition: 33.0/42.0 Wh (78.7%) volts: 11.3 min: 11.4 model: SWD-ATL3.618 DELL WJPC403 status: Discharging CPU: Info: Quad Core model: Intel Core i5-1035G1 bits: 64 type: MT MCP arch: Ice Lake rev: 5 cache: L2: 6 MiB flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 19046 Speed: 968 MHz min/max: 400/1000 MHz Core speeds (MHz): 1: 968 2: 710 3: 706 4: 714 5: 966 6: 712 7: 724 8: 821 Graphics: Device-1: Intel Iris Plus Graphics G1 vendor: Dell driver: i915 v: kernel bus-ID: 00:02.0 Device-2: Realtek Integrated_Webcam_HD type: USB driver: uvcvideo bus-ID: 1-6:3 Display: wayland server: X.Org 1.21.1.2 compositor: gnome-shell driver: loaded: i915 note: n/a (using device driver) resolution: 1920x1080~60Hz OpenGL: renderer: Mesa Intel UHD Graphics (ICL GT1) v: 4.6 Mesa 21.2.2 direct render: Yes Audio: Device-1: Intel Ice Lake-LP Smart Sound Audio vendor: Dell driver: snd_hda_intel v: kernel bus-ID: 00:1f.3 Sound Server-1: ALSA v: k5.13.0-19-generic running: yes Sound Server-2: PulseAudio v: 15.0 running: yes Sound Server-3: PipeWire v: 0.3.40 running: yes Network: Device-1: Realtek RTL810xE PCI Express Fast Ethernet vendor: Dell driver: r8169 v: kernel port: 3000 bus-ID: 01:00.0 IF: enp1s0 state: down mac: 98:e7:43:59:19:19 Device-2: Qualcomm Atheros QCA9377 802.11ac Wireless Network Adapter vendor: Dell driver: ath10k_pci v: kernel bus-ID: 02:00.0 IF: wlp2s0 state: up mac: d8:12:65:b8:21:b9 Bluetooth: Device-1: Qualcomm Atheros type: USB driver: btusb v: 0.8 bus-ID: 1-10:4 Report: hciconfig ID: hci0 rfk-id: 0 state: down bt-service: enabled,running rfk-block: hardware: no software: yes address: D8:12:65:B8:21:BA Drives:Local Storage: total: 942.7 GiB used: 11.77 GiB (1.2%) ID-1: /dev/nvme0n1 vendor: Toshiba model: KBG40ZNS512G NVMe KIOXIA 512GB size: 476.94 GiB temp: 24.9 C ID-2: /dev/sda vendor: Crucial model: CT500MX500SSD1 size: 465.76 GiB Partition: ID-1: / size: 46.95 GiB used: 11.73 GiB (25.0%) fs: ext4 dev: /dev/nvme0n1p3 ID-2: /boot/efi size: 246 MiB used: 46.4 MiB (18.9%) fs: vfat dev: /dev/nvme0n1p1 Swap: Alert: No swap data was found. Sensors: System Temperatures: cpu: 27.8 C mobo: N/A Fan Speeds (RPM): cpu: 0 Info: Processes: 263 Uptime: 31m Memory: 15.4 GiB used: 2.45 GiB (15.9%) Init: systemd runlevel: 5 Compilers: gcc: N/A Packages: 1785 Shell: Bash v: 5.1.12 inxi: 3.3.07 corrado@corrado-p3-jj-1130:~$ --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu74 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2021-11-30 (2 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20211130) Package: gnome-control-center 1:41.1-1ubuntu1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14 Tags: wayland-session jammy Uname: Linux 5.13.0-19-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload:
[Desktop-packages] [Bug 1953052] Re: In Jammy sound level reset after reboot
how can i tell if i have pulseaudio and pipewire activated? -- 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/1953052 Title: In Jammy sound level reset after reboot Status in alsa-utils package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Confirmed Bug description: After reboot sound level is reset ignoring the level set in previous session. I manually set the sound output level at next boot the sound is set at a different level (about 70%) Expected: the sound level is persistent across power off/on What happens : sound level is set at a different level (about 70%) Note: this problem does not occur on different partitions of same PC running Ubuntu 20.04 or 21.10 corrado@corrado-p3-jj-1130:~$ apt policy gnome-control-center gnome-control-center: Installed: 1:41.1-1ubuntu1 Candidate: 1:41.1-1ubuntu1 Version table: *** 1:41.1-1ubuntu1 500 500 http://archive.ubuntu.com/ubuntu jammy/main amd64 Packages 100 /var/lib/dpkg/status corrado@corrado-p3-jj-1130:~$ inxi -Fx System:Host: corrado-p3-jj-1130 Kernel: 5.13.0-19-generic x86_64 bits: 64 compiler: gcc v: 11.2.0 Desktop: GNOME 40.5 Distro: Ubuntu 22.04 (Jammy Jellyfish) Machine: Type: Laptop System: Dell product: Inspiron 3793 v: N/A serial: Mobo: Dell model: 0C1PF2 v: A00 serial: UEFI: Dell v: 1.5.0 date: 12/17/2019 Battery: ID-1: BAT0 charge: 13.9 Wh (42.1%) condition: 33.0/42.0 Wh (78.7%) volts: 11.3 min: 11.4 model: SWD-ATL3.618 DELL WJPC403 status: Discharging CPU: Info: Quad Core model: Intel Core i5-1035G1 bits: 64 type: MT MCP arch: Ice Lake rev: 5 cache: L2: 6 MiB flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 19046 Speed: 968 MHz min/max: 400/1000 MHz Core speeds (MHz): 1: 968 2: 710 3: 706 4: 714 5: 966 6: 712 7: 724 8: 821 Graphics: Device-1: Intel Iris Plus Graphics G1 vendor: Dell driver: i915 v: kernel bus-ID: 00:02.0 Device-2: Realtek Integrated_Webcam_HD type: USB driver: uvcvideo bus-ID: 1-6:3 Display: wayland server: X.Org 1.21.1.2 compositor: gnome-shell driver: loaded: i915 note: n/a (using device driver) resolution: 1920x1080~60Hz OpenGL: renderer: Mesa Intel UHD Graphics (ICL GT1) v: 4.6 Mesa 21.2.2 direct render: Yes Audio: Device-1: Intel Ice Lake-LP Smart Sound Audio vendor: Dell driver: snd_hda_intel v: kernel bus-ID: 00:1f.3 Sound Server-1: ALSA v: k5.13.0-19-generic running: yes Sound Server-2: PulseAudio v: 15.0 running: yes Sound Server-3: PipeWire v: 0.3.40 running: yes Network: Device-1: Realtek RTL810xE PCI Express Fast Ethernet vendor: Dell driver: r8169 v: kernel port: 3000 bus-ID: 01:00.0 IF: enp1s0 state: down mac: 98:e7:43:59:19:19 Device-2: Qualcomm Atheros QCA9377 802.11ac Wireless Network Adapter vendor: Dell driver: ath10k_pci v: kernel bus-ID: 02:00.0 IF: wlp2s0 state: up mac: d8:12:65:b8:21:b9 Bluetooth: Device-1: Qualcomm Atheros type: USB driver: btusb v: 0.8 bus-ID: 1-10:4 Report: hciconfig ID: hci0 rfk-id: 0 state: down bt-service: enabled,running rfk-block: hardware: no software: yes address: D8:12:65:B8:21:BA Drives:Local Storage: total: 942.7 GiB used: 11.77 GiB (1.2%) ID-1: /dev/nvme0n1 vendor: Toshiba model: KBG40ZNS512G NVMe KIOXIA 512GB size: 476.94 GiB temp: 24.9 C ID-2: /dev/sda vendor: Crucial model: CT500MX500SSD1 size: 465.76 GiB Partition: ID-1: / size: 46.95 GiB used: 11.73 GiB (25.0%) fs: ext4 dev: /dev/nvme0n1p3 ID-2: /boot/efi size: 246 MiB used: 46.4 MiB (18.9%) fs: vfat dev: /dev/nvme0n1p1 Swap: Alert: No swap data was found. Sensors: System Temperatures: cpu: 27.8 C mobo: N/A Fan Speeds (RPM): cpu: 0 Info: Processes: 263 Uptime: 31m Memory: 15.4 GiB used: 2.45 GiB (15.9%) Init: systemd runlevel: 5 Compilers: gcc: N/A Packages: 1785 Shell: Bash v: 5.1.12 inxi: 3.3.07 corrado@corrado-p3-jj-1130:~$ --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu74 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2021-11-30 (2 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20211130) Package: gnome-control-center 1:41.1-1ubuntu1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14 Tags: wayland-session jammy Uname: Linux 5.13.0-19-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
[Desktop-packages] [Bug 1961333] [NEW] Netbook display is turned off on login screen on startup
Public bug reported: On the netbook model Positivo Mobo 5800, it was noticed that, on the end of the boot process, the LightDM greeter won't appear and the screen will turn off, disabling the backlight too. To be able to log in to the graphical interface, it's required to go to a tty (for example, tty1) and then back to the LightDM greeter (which is tty7 on this case). When going back to the tty7, it's noticed that there are text still from the boot for a few seconds, until the greeter finally appears. The CPU is an Intel(R) Atom(TM) CPU N2600 @ 1.60GHz, it has a gma500 GPU. While gma500 is limiting, I've not observed this LightDM bug with, for example, the Positivo Mobo 5900, which has the same CPU and same GPU with the same revision and, even when applying the same image to both, the 5900 works while the 5800 fails. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: lightdm 1.30.0-0ubuntu4~20.04.2 ProcVersionSignature: Ubuntu 5.4.0-100.113-generic 5.4.166 Uname: Linux 5.4.0-100-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip Date: Thu Feb 17 15:30:44 2022 ProcEnviron: LANGUAGE=pt_BR:pt:en TERM=xterm-256color PATH=(custom, no user) LANG=pt_BR.UTF-8 SHELL=/bin/bash SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: lightdm (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 lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1961333 Title: Netbook display is turned off on login screen on startup Status in lightdm package in Ubuntu: New Bug description: On the netbook model Positivo Mobo 5800, it was noticed that, on the end of the boot process, the LightDM greeter won't appear and the screen will turn off, disabling the backlight too. To be able to log in to the graphical interface, it's required to go to a tty (for example, tty1) and then back to the LightDM greeter (which is tty7 on this case). When going back to the tty7, it's noticed that there are text still from the boot for a few seconds, until the greeter finally appears. The CPU is an Intel(R) Atom(TM) CPU N2600 @ 1.60GHz, it has a gma500 GPU. While gma500 is limiting, I've not observed this LightDM bug with, for example, the Positivo Mobo 5900, which has the same CPU and same GPU with the same revision and, even when applying the same image to both, the 5900 works while the 5800 fails. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: lightdm 1.30.0-0ubuntu4~20.04.2 ProcVersionSignature: Ubuntu 5.4.0-100.113-generic 5.4.166 Uname: Linux 5.4.0-100-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip Date: Thu Feb 17 15:30:44 2022 ProcEnviron: LANGUAGE=pt_BR:pt:en TERM=xterm-256color PATH=(custom, no user) LANG=pt_BR.UTF-8 SHELL=/bin/bash SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1961333/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1961327] [NEW] Audio drops when switiching applications
Public bug reported: The audio on my laptop drops when I open a new application (or switch to a different one). Sometimes it happens when switching tabs. It does not matter which application is playing audio, the audio usually stops when the application is switched. The typical workaround is to kill pulseaudio and start it again but that requires me to restart the application which is playing the audio. I found a better workaround which is to open PulseAudio Volume Control (pavucontrol) and toggle the profile from "Play HiFi quality music" -> "Off" -> "Play HiFi quality music". ➜ lsb_release -rd Description:Ubuntu 21.10 Release:21.10 ➜ apt-cache policy pulseaudio pulseaudio: Installed: 1:15.0+dfsg1-1ubuntu2.2 Candidate: 1:15.0+dfsg1-1ubuntu2.2 Version table: *** 1:15.0+dfsg1-1ubuntu2.2 500 500 http://ca.archive.ubuntu.com/ubuntu impish-updates/main amd64 Packages 100 /var/lib/dpkg/status 1:15.0+dfsg1-1ubuntu2 500 500 http://ca.archive.ubuntu.com/ubuntu impish/main amd64 Packages ** Affects: pulseaudio (Ubuntu) Importance: Undecided Status: New ** Description changed: The audio on my laptop drops when I open a new application (or switch to a different one). Sometimes it happens when switching tabs. It does not matter which application is playing audio, the audio usually stops when the application is switched. The typical workaround is to kill pulseaudio and start it again but that requires me to restart the application which is playing the audio. I found a better workaround which is to open PulseAudio Volume Control (pavucontrol) and toggle the profile from "Play HiFi quality music" -> "Off" -> "Play HiFi quality music". - - ``` + ` ➜ lsb_release -rd Description: Ubuntu 21.10 Release: 21.10 - ``` + ` - ``` + ` apt-cache policy pulseaudio pulseaudio: - Installed: 1:15.0+dfsg1-1ubuntu2.2 - Candidate: 1:15.0+dfsg1-1ubuntu2.2 - Version table: - *** 1:15.0+dfsg1-1ubuntu2.2 500 - 500 http://ca.archive.ubuntu.com/ubuntu impish-updates/main amd64 Packages - 100 /var/lib/dpkg/status - 1:15.0+dfsg1-1ubuntu2 500 - 500 http://ca.archive.ubuntu.com/ubuntu impish/main amd64 Packages - ``` + Installed: 1:15.0+dfsg1-1ubuntu2.2 + Candidate: 1:15.0+dfsg1-1ubuntu2.2 + Version table: + *** 1:15.0+dfsg1-1ubuntu2.2 500 + 500 http://ca.archive.ubuntu.com/ubuntu impish-updates/main amd64 Packages + 100 /var/lib/dpkg/status + 1:15.0+dfsg1-1ubuntu2 500 + 500 http://ca.archive.ubuntu.com/ubuntu impish/main amd64 Packages + ` ** Description changed: The audio on my laptop drops when I open a new application (or switch to a different one). Sometimes it happens when switching tabs. It does not matter which application is playing audio, the audio usually stops when the application is switched. The typical workaround is to kill pulseaudio and start it again but that requires me to restart the application which is playing the audio. I found a better workaround which is to open PulseAudio Volume Control (pavucontrol) and toggle the profile from "Play HiFi quality music" -> "Off" -> "Play HiFi quality music". - ` + ➜ lsb_release -rd Description: Ubuntu 21.10 Release: 21.10 ` - ` - apt-cache policy pulseaudio + + ➜ apt-cache policy pulseaudio pulseaudio: Installed: 1:15.0+dfsg1-1ubuntu2.2 Candidate: 1:15.0+dfsg1-1ubuntu2.2 Version table: *** 1:15.0+dfsg1-1ubuntu2.2 500 500 http://ca.archive.ubuntu.com/ubuntu impish-updates/main amd64 Packages 100 /var/lib/dpkg/status 1:15.0+dfsg1-1ubuntu2 500 500 http://ca.archive.ubuntu.com/ubuntu impish/main amd64 Packages - ` ** Description changed: The audio on my laptop drops when I open a new application (or switch to a different one). Sometimes it happens when switching tabs. It does not matter which application is playing audio, the audio usually stops when the application is switched. The typical workaround is to kill pulseaudio and start it again but that requires me to restart the application which is playing the audio. I found a better workaround which is to open PulseAudio Volume Control (pavucontrol) and toggle the profile from "Play HiFi quality music" -> "Off" -> "Play HiFi quality music". - ➜ lsb_release -rd Description: Ubuntu 21.10 Release: 21.10 - ` - ➜ apt-cache policy pulseaudio pulseaudio: Installed: 1:15.0+dfsg1-1ubuntu2.2 Candidate: 1:15.0+dfsg1-1ubuntu2.2 Version table: *** 1:15.0+dfsg1-1ubuntu2.2 500 500 http://ca.archive.ubuntu.com/ubuntu impish-updates/main amd64 Packages 100 /var/lib/dpkg/status 1:15.0+dfsg1-1ubuntu2 500 500 http://ca.archive.ubuntu.com/ubuntu impish/main amd64 Packages -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to
[Desktop-packages] [Bug 1953052] Re: In Jammy sound level reset after reboot
Do you have both pulseaudio and pipewire audio enabled simultaneously? At least system log suggests pipewire with session manager is also being activated, this could cause issues if both attempt to restore volumes for some reason. -- 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/1953052 Title: In Jammy sound level reset after reboot Status in alsa-utils package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Confirmed Bug description: After reboot sound level is reset ignoring the level set in previous session. I manually set the sound output level at next boot the sound is set at a different level (about 70%) Expected: the sound level is persistent across power off/on What happens : sound level is set at a different level (about 70%) Note: this problem does not occur on different partitions of same PC running Ubuntu 20.04 or 21.10 corrado@corrado-p3-jj-1130:~$ apt policy gnome-control-center gnome-control-center: Installed: 1:41.1-1ubuntu1 Candidate: 1:41.1-1ubuntu1 Version table: *** 1:41.1-1ubuntu1 500 500 http://archive.ubuntu.com/ubuntu jammy/main amd64 Packages 100 /var/lib/dpkg/status corrado@corrado-p3-jj-1130:~$ inxi -Fx System:Host: corrado-p3-jj-1130 Kernel: 5.13.0-19-generic x86_64 bits: 64 compiler: gcc v: 11.2.0 Desktop: GNOME 40.5 Distro: Ubuntu 22.04 (Jammy Jellyfish) Machine: Type: Laptop System: Dell product: Inspiron 3793 v: N/A serial: Mobo: Dell model: 0C1PF2 v: A00 serial: UEFI: Dell v: 1.5.0 date: 12/17/2019 Battery: ID-1: BAT0 charge: 13.9 Wh (42.1%) condition: 33.0/42.0 Wh (78.7%) volts: 11.3 min: 11.4 model: SWD-ATL3.618 DELL WJPC403 status: Discharging CPU: Info: Quad Core model: Intel Core i5-1035G1 bits: 64 type: MT MCP arch: Ice Lake rev: 5 cache: L2: 6 MiB flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 19046 Speed: 968 MHz min/max: 400/1000 MHz Core speeds (MHz): 1: 968 2: 710 3: 706 4: 714 5: 966 6: 712 7: 724 8: 821 Graphics: Device-1: Intel Iris Plus Graphics G1 vendor: Dell driver: i915 v: kernel bus-ID: 00:02.0 Device-2: Realtek Integrated_Webcam_HD type: USB driver: uvcvideo bus-ID: 1-6:3 Display: wayland server: X.Org 1.21.1.2 compositor: gnome-shell driver: loaded: i915 note: n/a (using device driver) resolution: 1920x1080~60Hz OpenGL: renderer: Mesa Intel UHD Graphics (ICL GT1) v: 4.6 Mesa 21.2.2 direct render: Yes Audio: Device-1: Intel Ice Lake-LP Smart Sound Audio vendor: Dell driver: snd_hda_intel v: kernel bus-ID: 00:1f.3 Sound Server-1: ALSA v: k5.13.0-19-generic running: yes Sound Server-2: PulseAudio v: 15.0 running: yes Sound Server-3: PipeWire v: 0.3.40 running: yes Network: Device-1: Realtek RTL810xE PCI Express Fast Ethernet vendor: Dell driver: r8169 v: kernel port: 3000 bus-ID: 01:00.0 IF: enp1s0 state: down mac: 98:e7:43:59:19:19 Device-2: Qualcomm Atheros QCA9377 802.11ac Wireless Network Adapter vendor: Dell driver: ath10k_pci v: kernel bus-ID: 02:00.0 IF: wlp2s0 state: up mac: d8:12:65:b8:21:b9 Bluetooth: Device-1: Qualcomm Atheros type: USB driver: btusb v: 0.8 bus-ID: 1-10:4 Report: hciconfig ID: hci0 rfk-id: 0 state: down bt-service: enabled,running rfk-block: hardware: no software: yes address: D8:12:65:B8:21:BA Drives:Local Storage: total: 942.7 GiB used: 11.77 GiB (1.2%) ID-1: /dev/nvme0n1 vendor: Toshiba model: KBG40ZNS512G NVMe KIOXIA 512GB size: 476.94 GiB temp: 24.9 C ID-2: /dev/sda vendor: Crucial model: CT500MX500SSD1 size: 465.76 GiB Partition: ID-1: / size: 46.95 GiB used: 11.73 GiB (25.0%) fs: ext4 dev: /dev/nvme0n1p3 ID-2: /boot/efi size: 246 MiB used: 46.4 MiB (18.9%) fs: vfat dev: /dev/nvme0n1p1 Swap: Alert: No swap data was found. Sensors: System Temperatures: cpu: 27.8 C mobo: N/A Fan Speeds (RPM): cpu: 0 Info: Processes: 263 Uptime: 31m Memory: 15.4 GiB used: 2.45 GiB (15.9%) Init: systemd runlevel: 5 Compilers: gcc: N/A Packages: 1785 Shell: Bash v: 5.1.12 inxi: 3.3.07 corrado@corrado-p3-jj-1130:~$ --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu74 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2021-11-30 (2 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20211130) Package: gnome-control-center 1:41.1-1ubuntu1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14 Tags: wayland-session jammy
[Desktop-packages] [Bug 1961303] [NEW] package chromium-browser 1:85.0.4183.83-0ubuntu0.20.04.2 failed to install/upgrade: new chromium-browser package pre-installation script subprocess returned erro
Public bug reported: I tried to install Chromium browser using terminal and I got this error. Description:Ubuntu 20.04.3 LTS Release:20.04 N: Unable to locate package pkgname ProblemType: Package DistroRelease: Ubuntu 20.04 Package: chromium-browser 1:85.0.4183.83-0ubuntu0.20.04.2 ProcVersionSignature: Ubuntu 5.13.0-28.31~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-28-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 AptOrdering: chromium-browser:amd64: Install NULL: ConfigurePending Architecture: amd64 CasperMD5CheckResult: skip Date: Thu Feb 17 16:28:10 2022 Dependencies: ErrorMessage: new chromium-browser package pre-installation script subprocess returned error exit status 10 InstallationDate: Installed on 2022-02-16 (1 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4 RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.6 SourcePackage: chromium-browser Title: package chromium-browser 1:85.0.4183.83-0ubuntu0.20.04.2 failed to install/upgrade: new chromium-browser package pre-installation script subprocess returned error exit status 10 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: chromium-browser (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package focal need-duplicate-check -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1961303 Title: package chromium-browser 1:85.0.4183.83-0ubuntu0.20.04.2 failed to install/upgrade: new chromium-browser package pre-installation script subprocess returned error exit status 10 Status in chromium-browser package in Ubuntu: New Bug description: I tried to install Chromium browser using terminal and I got this error. Description: Ubuntu 20.04.3 LTS Release: 20.04 N: Unable to locate package pkgname ProblemType: Package DistroRelease: Ubuntu 20.04 Package: chromium-browser 1:85.0.4183.83-0ubuntu0.20.04.2 ProcVersionSignature: Ubuntu 5.13.0-28.31~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-28-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 AptOrdering: chromium-browser:amd64: Install NULL: ConfigurePending Architecture: amd64 CasperMD5CheckResult: skip Date: Thu Feb 17 16:28:10 2022 Dependencies: ErrorMessage: new chromium-browser package pre-installation script subprocess returned error exit status 10 InstallationDate: Installed on 2022-02-16 (1 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4 RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.6 SourcePackage: chromium-browser Title: package chromium-browser 1:85.0.4183.83-0ubuntu0.20.04.2 failed to install/upgrade: new chromium-browser package pre-installation script subprocess returned error exit status 10 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1961303/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1957944] Re: CSD do not distinguish focused and unfocused FF windows
At the moment it's "Yaru-dark / Yaru" and the issue remains. I was using a third party theme when I first encountered this. I switched back to Yaru before filing this bug, but about:support was still showing the third party theme. After resetting the theme it's showing "Yaru-dark / Yaru". I did some more testing with a separate login I use for steam and a new FF profile. It seems to only happen when a a FF colorways theme is used. If the default theme is used I am able to see a difference in the titlebar shade (it's too subtle IMO, but I can see it). -- 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/1957944 Title: CSD do not distinguish focused and unfocused FF windows Status in firefox package in Ubuntu: Incomplete Bug description: After the FF 96 upgrade I can't distinguish focused and unfocused FF windows from their client side decorations. Previously the distinction was subtle, but not impossible. The attached image shows two windows, the one on the left has focus. The only way you can tell this is that the scrollbar is faded in the unfocused window. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: firefox 96.0+build2-0ubuntu0.21.10.1 Uname: Linux 5.14.0-051400-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 BuildID: 20220106144528 CasperMD5CheckResult: unknown Channel: Unavailable CurrentDesktop: ubuntu:GNOME Date: Fri Jan 14 13:15:27 2022 DefaultProfileExtensions: extensions.sqlite corrupt or missing DefaultProfileIncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) DefaultProfileLocales: extensions.sqlite corrupt or missing DefaultProfilePrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/firefox/omni.ja:greprefs.js:365 DefaultProfilePrefSources: prefs.js DefaultProfileThemes: extensions.sqlite corrupt or missing ForcedLayersAccel: False IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2019-06-18 (941 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) ProcEnviron: TERM=tmux-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash Profile1Extensions: extensions.sqlite corrupt or missing Profile1IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) Profile1Locales: extensions.sqlite corrupt or missing Profile1PrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/firefox/omni.ja:greprefs.js:365 Profile1PrefSources: prefs.js Profile1Themes: extensions.sqlite corrupt or missing Profile2Extensions: extensions.sqlite corrupt or missing Profile2IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) Profile2Locales: extensions.sqlite corrupt or missing Profile2PrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/firefox/omni.ja:greprefs.js:365 Profile2PrefSources: prefs.js Profile2Themes: extensions.sqlite corrupt or missing Profiles: Profile1 - LastVersion=96.0/20220106144528 (In use) Profile0 (Default) - LastVersion=96.0/20220106144528 (In use) Profile2 - LastVersion=71.0/20191205203726 (Out of date) RebootRequiredPkgs: Error: path contained symlinks. RunningIncompatibleAddons: False SourcePackage: firefox UpgradeStatus: Upgraded to impish on 2021-10-31 (75 days ago) dmi.bios.date: 11/27/2019 dmi.bios.release: 5.14 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P2.90 dmi.board.name: B450M Steel Legend dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP2.90:bd11/27/2019:br5.14:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:skuToBeFilledByO.E.M.:rvnASRock:rnB450MSteelLegend:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1957944/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1959604]
Verified testing the 98.0b2 release candidate on Fedora 35 Workstation.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to thunderbird in Ubuntu.
https://bugs.launchpad.net/bugs/1959604
Title:
[upstream] Thunderbird 91.5.0 regression: writes attachments to /tmp
readable to everyone
Status in Mozilla Thunderbird:
Fix Released
Status in thunderbird package in Ubuntu:
Triaged
Bug description:
thunderbird saves opened attachments to /tmp with permissions
according to umask setting. This was fixed a long time ago with a
protected folder /tmp/mozilla_${USER}0 and was still working correctly
as of version 78.14.0+build1-0ubuntu0.20.04.2. The recent update to
1:91.5.0+build1-0ubuntu0.20.04.1 reintroduced the bug.
Ubuntu 20.04.3 LTS
Kernel release:5.13.0-25-generic
Architecture: x86_64
To manage notifications about this bug go to:
https://bugs.launchpad.net/thunderbird/+bug/1959604/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1959604]
Comment on attachment 9262175
Bug 1753242 - use a tmp subdir for opening temp files. r=darktrojan
[Triage Comment]
Approved for beta
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to thunderbird in Ubuntu.
https://bugs.launchpad.net/bugs/1959604
Title:
[upstream] Thunderbird 91.5.0 regression: writes attachments to /tmp
readable to everyone
Status in Mozilla Thunderbird:
Fix Released
Status in thunderbird package in Ubuntu:
Triaged
Bug description:
thunderbird saves opened attachments to /tmp with permissions
according to umask setting. This was fixed a long time ago with a
protected folder /tmp/mozilla_${USER}0 and was still working correctly
as of version 78.14.0+build1-0ubuntu0.20.04.2. The recent update to
1:91.5.0+build1-0ubuntu0.20.04.1 reintroduced the bug.
Ubuntu 20.04.3 LTS
Kernel release:5.13.0-25-generic
Architecture: x86_64
To manage notifications about this bug go to:
https://bugs.launchpad.net/thunderbird/+bug/1959604/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1959604]
Thunderbird 98.0b2:
https://hg.mozilla.org/releases/comm-beta/rev/c173b2661afc
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to thunderbird in Ubuntu.
https://bugs.launchpad.net/bugs/1959604
Title:
[upstream] Thunderbird 91.5.0 regression: writes attachments to /tmp
readable to everyone
Status in Mozilla Thunderbird:
Fix Released
Status in thunderbird package in Ubuntu:
Triaged
Bug description:
thunderbird saves opened attachments to /tmp with permissions
according to umask setting. This was fixed a long time ago with a
protected folder /tmp/mozilla_${USER}0 and was still working correctly
as of version 78.14.0+build1-0ubuntu0.20.04.2. The recent update to
1:91.5.0+build1-0ubuntu0.20.04.1 reintroduced the bug.
Ubuntu 20.04.3 LTS
Kernel release:5.13.0-25-generic
Architecture: x86_64
To manage notifications about this bug go to:
https://bugs.launchpad.net/thunderbird/+bug/1959604/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1861262] Re: Add message/rfc822 to thunderbird.desktop
Ack, thanks for the detailed rationale Max. Users who come across the issue will indeed appreciate to find an explanation here. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to thunderbird in Ubuntu. https://bugs.launchpad.net/bugs/1861262 Title: Add message/rfc822 to thunderbird.desktop Status in thunderbird package in Ubuntu: Fix Released Bug description: Please add message/rfc822 to thunderbird.desktop: -MimeType=x-scheme-handler/mailto;application/x-xpinstall; +MimeType=x-scheme-handler/mailto;application/x-xpinstall;message/rfc822; It will allow to open *.eml files. I attach an example eml file. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1861262/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1910613] Re: Crash of gnome shell potentially from "JS ERROR: too much recursion" from app indicators
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gnome-shell-extension-appindicator (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-appindicator in Ubuntu. https://bugs.launchpad.net/bugs/1910613 Title: Crash of gnome shell potentially from "JS ERROR: too much recursion" from app indicators Status in gnome-shell-extension-appindicator package in Ubuntu: Confirmed Bug description: What Happened: 1) Have gnome-shell-extensions-appindicator enabled 2) The only running app using the indicator was charmtimetracker ( https://github.com/KDAB/Charm ) 3) At some point usually within 1-2 days of office usage gnome shell crashes 4) Notice "JS ERROR: too much recursion" and then a stacktrace coming from appindicator extension in journalctl What I expected to happen: For gnome-shell not to crash :-) Full logs: - Recursion warnings - https://pastebin.ubuntu.com/p/hfKMmH4Dpx/ - Stack trace - https://pastebin.ubuntu.com/p/2TC6WFVcsG/ Short Summary of Logs: === First sign of incoming crash === Jan 05 17:59:01 MACHINE-NAME gnome-shell[3315]: JS ERROR: too much recursion set active@resource:///org/gnome/shell/ui/popupMenu.js:199:29 _init@resource:///org/gnome/shell/ui/popupMenu.js:104:18 _init@resource:///org/gnome/shell/ui/popupMenu.js:273:15 createItem@/usr/share/gnome-shell/extensions/ubuntu-appindicat...@ubuntu.com/dbusMenu.js:498:29 createItem@/usr/share/gnome-shell/extensions/ubuntu-appindicat...@ubuntu.com/dbusMenu.js:520:60 === This continues many times, last instance is like this === Jan 05 17:59:01 MACHINE-NAME gnome-shell[3315]: JS ERROR: Exception in callback for signal: child-added: too much recursion PopupSubMenu@resource:///org/gnome/shell/ui/popupMenu.js:1017:9 _init@resource:///org/gnome/shell/ui/popupMenu.js:1201:21 createItem@/usr/share/gnome-shell/extensions/ubuntu-appindicat...@ubuntu.com/dbusMenu.js:494:29 createItem@/usr/share/gnome-shell/extensions/ubuntu-appindicat...@ubuntu.com/dbusMenu.js:520:60 === Then there is a stacktrace (shortened repeats) === Jan 05 17:59:01 MACHINE-NAME gnome-shell[3315]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Jan 05 17:59:01 MACHINE-NAME gnome-shell[3315]: The offending signal was notify on StLabel 0x5615bd3eee80. Jan 05 17:59:01 MACHINE-NAME gnome-shell[3315]: == Stack trace for context 0x56159bbee930 == Jan 05 17:59:01 MACHINE-NAME gnome-shell[3315]: #0 7ffca7535bb0 b /usr/share/gnome-shell/extensions/ubuntu-appindicat...@ubuntu.com/dbusMenu.js:620 (1c7e392cc2e0 @ 100) Jan 05 17:59:01 MACHINE-NAME gnome-shell[3315]: #1 7ffca7535c80 b /usr/share/gnome-shell/extensions/ubuntu-appindicat...@ubuntu.com/dbusMenu.js:510 (1c7e392cae98 @ 357) Jan 05 17:59:01 MACHINE-NAME gnome-shell[3315]: #2 5615a5c69340 i /usr/share/gnome-shell/extensions/ubuntu-appindicat...@ubuntu.com/dbusMenu.js:771 (1c7e392cc880 @ 41) Jan 05 17:59:01 MACHINE-NAME gnome-shell[3315]: #3 7ffca7536b70 b self-hosted:1013 (264b03e13e20 @ 492) Jan 05 17:59:01 MACHINE-NAME gnome-shell[3315]: #4 7ffca7536c60 b self-hosted:1013 (264b03e13e20 @ 492) Jan 05 17:59:01 MACHINE-NAME gnome-shell[3315]: #5 7ffca7536d70 b resource:///org/gnome/gjs/modules/core/_signals.js:133 (1c7e392a84c0 @ 427) Jan 05 17:59:01 MACHINE-NAME gnome-shell[3315]: #6 5615a5c69290 i /usr/share/gnome-shell/extensions/ubuntu-appindicat...@ubuntu.com/dbusMenu.js:134 (1c7e392c5c40 @ 74) Jan 05 17:59:01 MACHINE-NAME gnome-shell[3315]: #7 7ffca7537c80 b /usr/share/gnome-shell/extensions/ubuntu-appindicat...@ubuntu.com/dbusMenu.js:365 (1c7e392ca718 @ 837) Jan 05 17:59:01 MACHINE-NAME gnome-shell[3315]: #8 5615a5c690d0 i /usr/share/gnome-shell/extensions/ubuntu-appindicat...@ubuntu.com/dbusMenu.js:326 (1c7e392ca6a0 @ 423) Jan 05 17:59:01 MACHINE-NAME gnome-shell[3315]: #9 7ffca7538970 b self-hosted:1013 (264b03e13e20 @ 492) Jan 05 17:59:01 MACHINE-NAME gnome-shell[3315]: #10 5615a5c69018 i resource:///org/gnome/gjs/modules/core/overrides/Gio.js:132 (2784371926a0 @
[Desktop-packages] [Bug 1957909] Re: NetworkManager connectivity check fails
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: network-manager (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1957909 Title: NetworkManager connectivity check fails Status in network-manager package in Ubuntu: Confirmed Bug description: I randomly receive "No internet connection available" notification, even if my internet connection is stable. (Not the exact term) In /usr/lib/NetworkManager/conf.d/20-connectivity-ubuntu.conf the endpoint http://connectivity-check.ubuntu.com./ is used. I manually pinged the endpoint. I live in europe and the server is located in the US. The latency is about 160ms. Usually I have an approximate latency of 15ms. It is not a problem of my ISP, I receive this notification on different locations in Germany and Switzerland. I propose to use another endpoint or provide another server for the same endpoint for europe. So the DNS servers in europe provide the IP of a server located in europe. The config comes from the package "network-manager-config- connectivity-ubuntu" version 1.32.12-0ubuntu1. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1957909/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1961197] Re: gvfsd hangs: smbXcli_negprot_smb1_done: No compatible protocol selected by server, got no contact to IPC$
It is also impossible to start nautilus. It hangs polling its eventfd. Running in strace it eventually continues to then crash in libfontconfig (might be some memory limit by my strace wrapper, though). -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/1961197 Title: gvfsd hangs on hanging filesystem Status in gvfs package in Ubuntu: New Bug description: This means that no file open dialog works anymore. I needed to restart gvfs-daemon.service twice today in order to attach two files in chrome. There seems to be some issue with samba, but not sure what it's trying to connect to or why it hangs the entire thing. Feb 11 11:03:54 jak-t480s systemd[5652]: Starting Virtual filesystem service... Feb 11 11:03:54 jak-t480s systemd[5652]: Started Virtual filesystem service. Feb 14 12:50:02 jak-t480s gvfsd[1358261]: smbXcli_negprot_smb1_done: No compatible protocol selected by server. Feb 14 12:50:02 jak-t480s gvfsd[1358261]: got no contact to IPC$ Feb 15 15:14:37 jak-t480s systemd[5652]: Stopping Virtual filesystem service... Feb 15 15:14:37 jak-t480s systemd[5652]: Stopped Virtual filesystem service. Feb 15 15:14:37 jak-t480s systemd[5652]: gvfs-daemon.service: Consumed 3.513s CPU time. Feb 15 15:14:37 jak-t480s systemd[5652]: Starting Virtual filesystem service... Feb 15 15:14:37 jak-t480s systemd[5652]: Started Virtual filesystem service. Feb 15 15:14:49 jak-t480s gvfsd[3000571]: smbXcli_negprot_smb1_done: No compatible protocol selected by server. Feb 15 15:14:49 jak-t480s gvfsd[3000571]: got no contact to IPC$ Feb 17 13:02:42 jak-t480s systemd[5652]: Stopping Virtual filesystem service... Feb 17 13:02:42 jak-t480s systemd[5652]: Stopped Virtual filesystem service. Feb 17 13:02:42 jak-t480s systemd[5652]: gvfs-daemon.service: Consumed 6.115s CPU time. Feb 17 13:02:42 jak-t480s systemd[5652]: Starting Virtual filesystem service...
[Desktop-packages] [Bug 1961197] Re: gvfsd hangs: smbXcli_negprot_smb1_done: No compatible protocol selected by server, got no contact to IPC$
Seems this ws all down due to a hanging /keybase FUSE file system, so not as critical a bug as I feared (basically nautilus and desktop portals become unusable when a filesystem hangs). ** Summary changed: - gvfsd hangs: smbXcli_negprot_smb1_done: No compatible protocol selected by server, got no contact to IPC$ + gvfsd hangs on hanging filesystem -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/1961197 Title: gvfsd hangs on hanging filesystem Status in gvfs package in Ubuntu: New Bug description: This means that no file open dialog works anymore. I needed to restart gvfs-daemon.service twice today in order to attach two files in chrome. There seems to be some issue with samba, but not sure what it's trying to connect to or why it hangs the entire thing. Feb 11 11:03:54 jak-t480s systemd[5652]: Starting Virtual filesystem service... Feb 11 11:03:54 jak-t480s systemd[5652]: Started Virtual filesystem service. Feb 14 12:50:02 jak-t480s gvfsd[1358261]: smbXcli_negprot_smb1_done: No compatible protocol selected by server. Feb 14 12:50:02 jak-t480s gvfsd[1358261]: got no contact to IPC$ Feb 15 15:14:37 jak-t480s systemd[5652]: Stopping Virtual filesystem service... Feb 15 15:14:37 jak-t480s systemd[5652]: Stopped Virtual filesystem service. Feb 15 15:14:37 jak-t480s systemd[5652]: gvfs-daemon.service: Consumed 3.513s CPU time. Feb 15 15:14:37 jak-t480s systemd[5652]: Starting Virtual filesystem service... Feb 15 15:14:37 jak-t480s systemd[5652]: Started Virtual filesystem service. Feb 15 15:14:49 jak-t480s gvfsd[3000571]: smbXcli_negprot_smb1_done: No compatible protocol selected by server. Feb 15 15:14:49 jak-t480s gvfsd[3000571]: got no contact to IPC$ Feb 17 13:02:42 jak-t480s systemd[5652]: Stopping Virtual filesystem service... Feb 17 13:02:42 jak-t480s systemd[5652]: Stopped Virtual filesystem service. Feb 17 13:02:42 jak-t480s systemd[5652]: gvfs-daemon.service: Consumed 6.115s CPU time. Feb 17 13:02:42 jak-t480s systemd[5652]:
[Desktop-packages] [Bug 1961197] Re: gvfsd hangs: smbXcli_negprot_smb1_done: No compatible protocol selected by server, got no contact to IPC$
Feb 17 13:16:08 jak-t480s xdg-desktop-por[7549]: The peer-to-peer connection failed: The name :1.1151 was not provided by any .service files. Falling back to the session bus. Your application is probably missing --filesystem=xdg-run/gvfsd privileges. Feb 17 13:16:08 jak-t480s systemd[1]: Starting Hostname Service... Feb 17 13:16:08 jak-t480s xdg-desktop-por[7549]: Failed to fetch network locations: The name :1.1151 was not provided by any .service files -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/1961197 Title: gvfsd hangs on hanging filesystem Status in gvfs package in Ubuntu: New Bug description: This means that no file open dialog works anymore. I needed to restart gvfs-daemon.service twice today in order to attach two files in chrome. There seems to be some issue with samba, but not sure what it's trying to connect to or why it hangs the entire thing. Feb 11 11:03:54 jak-t480s systemd[5652]: Starting Virtual filesystem service... Feb 11 11:03:54 jak-t480s systemd[5652]: Started Virtual filesystem service. Feb 14 12:50:02 jak-t480s gvfsd[1358261]: smbXcli_negprot_smb1_done: No compatible protocol selected by server. Feb 14 12:50:02 jak-t480s gvfsd[1358261]: got no contact to IPC$ Feb 15 15:14:37 jak-t480s systemd[5652]: Stopping Virtual filesystem service... Feb 15 15:14:37 jak-t480s systemd[5652]: Stopped Virtual filesystem service. Feb 15 15:14:37 jak-t480s systemd[5652]: gvfs-daemon.service: Consumed 3.513s CPU time. Feb 15 15:14:37 jak-t480s systemd[5652]: Starting Virtual filesystem service... Feb 15 15:14:37 jak-t480s systemd[5652]: Started Virtual filesystem service. Feb 15 15:14:49 jak-t480s gvfsd[3000571]: smbXcli_negprot_smb1_done: No compatible protocol selected by server. Feb 15 15:14:49 jak-t480s gvfsd[3000571]: got no contact to IPC$ Feb 17 13:02:42 jak-t480s systemd[5652]: Stopping Virtual filesystem service... Feb 17 13:02:42 jak-t480s systemd[5652]: Stopped Virtual filesystem service. Feb 17 13:02:42 jak-t480s systemd[5652]: gvfs-daemon.service: Consumed 6.115s CPU time.
[Desktop-packages] [Bug 1961197] Re: gvfsd hangs: smbXcli_negprot_smb1_done: No compatible protocol selected by server, got no contact to IPC$
I now do not see the error messages, but still have to restart gvfs- daemon before I can attach files / desktop portals open -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/1961197 Title: gvfsd hangs on hanging filesystem Status in gvfs package in Ubuntu: New Bug description: This means that no file open dialog works anymore. I needed to restart gvfs-daemon.service twice today in order to attach two files in chrome. There seems to be some issue with samba, but not sure what it's trying to connect to or why it hangs the entire thing. Feb 11 11:03:54 jak-t480s systemd[5652]: Starting Virtual filesystem service... Feb 11 11:03:54 jak-t480s systemd[5652]: Started Virtual filesystem service. Feb 14 12:50:02 jak-t480s gvfsd[1358261]: smbXcli_negprot_smb1_done: No compatible protocol selected by server. Feb 14 12:50:02 jak-t480s gvfsd[1358261]: got no contact to IPC$ Feb 15 15:14:37 jak-t480s systemd[5652]: Stopping Virtual filesystem service... Feb 15 15:14:37 jak-t480s systemd[5652]: Stopped Virtual filesystem service. Feb 15 15:14:37 jak-t480s systemd[5652]: gvfs-daemon.service: Consumed 3.513s CPU time. Feb 15 15:14:37 jak-t480s systemd[5652]: Starting Virtual filesystem service... Feb 15 15:14:37 jak-t480s systemd[5652]: Started Virtual filesystem service. Feb 15 15:14:49 jak-t480s gvfsd[3000571]: smbXcli_negprot_smb1_done: No compatible protocol selected by server. Feb 15 15:14:49 jak-t480s gvfsd[3000571]: got no contact to IPC$ Feb 17 13:02:42 jak-t480s systemd[5652]: Stopping Virtual filesystem service... Feb 17 13:02:42 jak-t480s systemd[5652]: Stopped Virtual filesystem service. Feb 17 13:02:42 jak-t480s systemd[5652]: gvfs-daemon.service: Consumed 6.115s CPU time. Feb 17 13:02:42 jak-t480s systemd[5652]: Starting Virtual filesystem service...
[Desktop-packages] [Bug 1961197] [NEW] gvfsd hangs on hanging filesystem
Public bug reported: This means that no file open dialog works anymore. I needed to restart gvfs-daemon.service twice today in order to attach two files in chrome. There seems to be some issue with samba, but not sure what it's trying to connect to or why it hangs the entire thing. Feb 11 11:03:54 jak-t480s systemd[5652]: Starting Virtual filesystem service... Feb 11 11:03:54 jak-t480s systemd[5652]: Started Virtual filesystem service. Feb 14 12:50:02 jak-t480s gvfsd[1358261]: smbXcli_negprot_smb1_done: No compatible protocol selected by server. Feb 14 12:50:02 jak-t480s gvfsd[1358261]: got no contact to IPC$ Feb 15 15:14:37 jak-t480s systemd[5652]: Stopping Virtual filesystem service... Feb 15 15:14:37 jak-t480s systemd[5652]: Stopped Virtual filesystem service. Feb 15 15:14:37 jak-t480s systemd[5652]: gvfs-daemon.service: Consumed 3.513s CPU time. Feb 15 15:14:37 jak-t480s systemd[5652]: Starting Virtual filesystem service... Feb 15 15:14:37 jak-t480s systemd[5652]: Started Virtual filesystem service. Feb 15 15:14:49 jak-t480s gvfsd[3000571]: smbXcli_negprot_smb1_done: No compatible protocol selected by server. Feb 15 15:14:49 jak-t480s gvfsd[3000571]: got no contact to IPC$ Feb 17 13:02:42 jak-t480s systemd[5652]: Stopping Virtual filesystem service... Feb 17 13:02:42 jak-t480s systemd[5652]: Stopped Virtual filesystem service. Feb 17 13:02:42 jak-t480s systemd[5652]: gvfs-daemon.service: Consumed 6.115s CPU time. Feb 17 13:02:42 jak-t480s systemd[5652]: Starting Virtual filesystem service... Feb 17 13:02:42 jak-t480s systemd[5652]: Started Virtual filesystem service. Feb 17 13:03:35 jak-t480s systemd[5652]: Stopping Virtual filesystem service...
[Desktop-packages] [Bug 1861262] Re: Add message/rfc822 to thunderbird.desktop
> If I understand correctly, that's not an issue that can be fixed
> by merely updating the desktop file or packaging parameters
> of thunderbird in Ubuntu, it would have to be addressed
> by the upstream project.
I have added a comment to make users (who will face a problem despite a
fix) aware of idiosyncrasy of handling command line options by
thunderbird.
I do not expect that Ubuntu team will ship additional wrapper to deal
with the issue. Those, who desperately need it working, may write a
script that creates a symlink with ".eml" suffix and a desktop file to
open "message/rfc822" files using this script.
I am afraid that security issues might happen because mozilla soft
relies too much on heuristics and does not allow to explicitly express
intention through command line options. It is even impossible to ensure
that nothing following should be considered as options, remaining
arguments are URIs or files ("--" separator for a lot of tools).
Anyway the fix is a step forward. At least files having ".eml" suffix
may be conveniently viewed.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to thunderbird in Ubuntu.
https://bugs.launchpad.net/bugs/1861262
Title:
Add message/rfc822 to thunderbird.desktop
Status in thunderbird package in Ubuntu:
Fix Released
Bug description:
Please add message/rfc822 to thunderbird.desktop:
-MimeType=x-scheme-handler/mailto;application/x-xpinstall;
+MimeType=x-scheme-handler/mailto;application/x-xpinstall;message/rfc822;
It will allow to open *.eml files. I attach an example eml file.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1861262/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1959888] Re: Wayland sessions can't use external monitors that are connected to an Nvidia GPU with the proprietary driver
I'm happy to say that in the current version of the nvidia driver (nvidia-driver-510) the problem seems to be fixed. I can connect external monitor and it works flawlessly. Thank you for the help! -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1959888 Title: Wayland sessions can't use external monitors that are connected to an Nvidia GPU with the proprietary driver Status in mutter package in Ubuntu: New Bug description: When an external display is connected to my laptop, running Ubuntu 22.04, the display is detected and I am sent to the login screen. After logging in again, the display is not running, although the primary laptop display works fine. The external monitor is looking for connection in that moment, which it never founds. The bug is tested on two Samsung monitors: S24R350FHUXEN and S22F350FHU. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12 Uname: Linux 5.15.0-18-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 495.46 Wed Oct 27 16:31:33 UTC 2021 GCC version: gcc version 11.2.0 (Ubuntu 11.2.0-14ubuntu1) ApportVersion: 2.20.11-0ubuntu76 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Feb 3 13:25:04 2022 DistUpgraded: 2022-01-13 15:37:13,056 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: jammy DistroVariant: ubuntu DkmsStatus: nvidia/495.46, 5.15.0-17-generic, x86_64: installed nvidia/495.46, 5.15.0-18-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation CoffeeLake-H GT2 [UHD Graphics 630] [8086:3e9b] (prog-if 00 [VGA controller]) Subsystem: Dell CoffeeLake-H GT2 [UHD Graphics 630] [1028:086f] Subsystem: Dell GP107M [GeForce GTX 1050 Ti Mobile] [1028:086f] InstallationDate: Installed on 2021-09-09 (146 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) MachineType: Dell Inc. G3 3579 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-18-generic root=UUID=fd3be223-e609-4a8d-97fb-31ee2f754766 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to jammy on 2022-01-13 (20 days ago) dmi.bios.date: 04/20/2021 dmi.bios.release: 1.15 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.15.0 dmi.board.name: 0M5H57 dmi.board.vendor: Dell Inc. dmi.board.version: A05 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.15.0:bd04/20/2021:br1.15:svnDellInc.:pnG33579:pvr:rvnDellInc.:rn0M5H57:rvrA05:cvnDellInc.:ct10:cvr:sku086F: dmi.product.family: GSeries dmi.product.name: G3 3579 dmi.product.sku: 086F dmi.sys.vendor: Dell Inc. nvidia-settings: ERROR: Unable to find display on any available system ERROR: Unable to find display on any available system version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.109-2ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.2-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 21.2.2-1ubuntu1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.14-1ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-1ubuntu2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1959888/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1953507] Re: [radeon] jammy live - on adjusting display config; one display is unsuable blocky-mess
I haven't re-tested on my primary box (d960)... yet. I grabbed the latest *daily* of Ubuntu Desktop (2022.02.16) and performed a live QA-test on - dell [optiplex] 780 (c2q-q9400, 8gb, amd/ati cedar radeon hd 5000/6000/7350/8350) and was unable to re-create this issue. Default session on a LIVE run is X.Org as reported using GNOME.Settings.ABOUT which is what I believe was default on d960 (and am yet to confirm). Do note it's identical in specs except for box model; my details being taken from `lshw`. HOWEVER it has different motherboard & external ports, and its video card has HDMI+DVI ports out the back instead of 2xDVI on the 960 thus its not identical. It also has different resolution monitors (two old dell 4:3) I could NOT re-create the issue described in this bug report on this box; including play trying to adjust screen positions in arrangements somewhat akin to how monitors are set on 960 (much of the play using the landscape+portrait orientation as that's how the 780 monitors are; which is different to 2xlandscape on 960, but I did try and re-create using 2xlandscape [gritting my teeth] http://iso.qa.ubuntu.com/qatracker/milestones/429/builds/244481/testcases/1303/results -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-ati in Ubuntu. https://bugs.launchpad.net/bugs/1953507 Title: [radeon] jammy live - on adjusting display config; one display is unsuable blocky-mess Status in xserver-xorg-video-ati package in Ubuntu: New Bug description: ubuntu jammy daily (canary build) live test on - dell optiplex 960 (this is my primary machine; so is normally used for entry of data & not doing the QA-testing). on adjusting the displays to match my setup (six displays; two high & three across; this box uses two in the middle with middle on top row & middle on bottom row).. the top display is still useable, but the bottom is not. This boxes are not perfectly aligned as not all my displays are the exact same size; so top display is slightly to right of bottom display the bottom resembles a digital TV with bad signal, mostly blocky & parts of it flashing (very quickly). it doesn't match the attached picture (as viewable on this box anyway.. my top display; which was LEFT prior to alignment is perfectly readable). ** actual my top display is usable, bottom is not (blocky warped picture) ** expected on adjust displays to match my config; both displays remain usable & readable. ** notes likely related to graphics card & not GNOME. If I recall correctly; this box has an older video card used as it had 2x DVI connections my screens use. My usual install on this box is jammy; but I usually use LXQt/Lubuntu and I don't experience issues.. I also have installed Xubuntu/Xfce & Ubuntu/GNOME so can test the installed OS (where I don't believe I have issue), but my install is somewhat old (artful install upgraded every six months ~30-36 hours after each release) thus is likely heavily modified. ** Picture comments My top display is ~perfect (vertical white bar to left of ubuntu-dock- items I'd not expect, but the color-blocks to the left of the 'install/firefox/thunderbird/files` is NOT visible; only a vertical WHITE bar a few pixels wide to left of the dock appears' rest of top display is perfect. My bottom display is nothing like picture; it's unusable. A mixture of black/white boxes with red/purple bits which would be the picture warped into blocky-components. When I type, I get reactions on this display with the picture changing (mostly the black & white portions which flash, the red/purple bits which are warped indri picture appear to remain static). My phone/camera isn't working, but I've taken a photograph. I didn't anticipate issues in this QA-test (it's past 1AM now) otherwise I'd not have run this QA-test now. ** further comments this is likely a duplicate... I experience this type of reaction on other boxes; likely radeon related but I've yet to look & can't even remember which video card exists in this box (I don't experience issues with the display configuration of the box with identical card to this, but it relates to display setup/config... my other box with this card is landscape+portrait I believe and doesn't have one display above the other; ie. d780; I get these issues when one display is above the other - and only with single orientation (swap top/bottom and issues don't exist)) ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu1 ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14 Uname: Linux 5.13.0-19-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu74 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass
[Desktop-packages] [Bug 1861262] Re: Add message/rfc822 to thunderbird.desktop
Thanks for the additional insights Max. If I understand correctly, that's not an issue that can be fixed by merely updating the desktop file or packaging parameters of thunderbird in Ubuntu, it would have to be addressed by the upstream project. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to thunderbird in Ubuntu. https://bugs.launchpad.net/bugs/1861262 Title: Add message/rfc822 to thunderbird.desktop Status in thunderbird package in Ubuntu: Fix Released Bug description: Please add message/rfc822 to thunderbird.desktop: -MimeType=x-scheme-handler/mailto;application/x-xpinstall; +MimeType=x-scheme-handler/mailto;application/x-xpinstall;message/rfc822; It will allow to open *.eml files. I attach an example eml file. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1861262/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1961010] Re: firefox doesn't let its user control how or when it upgrades
Automatic background updates of firefox are disabled in the Ubuntu
builds (see the `--disable-updater` flag in about:buildconfig). Could it
be that you're running an upstream version instead of the Ubuntu
package?
Note however that apt updates to the Ubuntu package are distributed through the
security pocket, and the default setting is to download and install security
updates automatically.
You can change that setting (`software-properties-gtk --open-tab=2`), but
beware that this will apply to all security updates. Alternatively you could
`apt-mark hold firefox`.
Interrupting users' browsing session is not optimal, but it is a trade-
off for improved security overall.
** Changed in: firefox (Ubuntu)
Status: New => Invalid
--
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
