[Desktop-packages] [Bug 1691608] Re: Sporadic crackling sound from headphones
[Expired for Ubuntu because there has been no activity for 60 days.] ** Changed in: ubuntu Status: Incomplete => Expired -- 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/1691608 Title: Sporadic crackling sound from headphones Status in Ubuntu: Expired Status in alsa-driver package in Ubuntu: Expired Bug description: Ubuntu 16.04 64 bit HP Pavilion 15-aw077nr (Touch) Laptop Headphones had sporadic crackling sound. More often when volume increases over 30% Laptop has B speakers and headphones worked fine in Win10 before I replaced it with Ubuntu. Output from bash alsa-info.sh command: upload=true=true= !! !!ALSA Information Script v 0.4.64 !! !!Script ran on: Thu May 18 01:25:26 UTC 2017 !!Linux Distribution !!-- Ubuntu 16.04.2 LTS \n \l DISTRIB_ID=Ubuntu DISTRIB_DESCRIPTION="Ubuntu 16.04.2 LTS" NAME="Ubuntu" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Ubuntu 16.04.2 LTS" HOME_URL="http://www.ubuntu.com/; SUPPORT_URL="http://help.ubuntu.com/; BUG_REPORT_URL="http://bugs.launchpad.net/ubuntu/; UBUNTU_CODENAME=xenial !!DMI Information !!--- Manufacturer: HP Product Name: HP Pavilion Notebook Product Version: Firmware Version: F.23 Board Vendor: HP Board Name:81FB !!ACPI Device Status Information !!--- /sys/bus/acpi/devices/ACPI0003:00/status 15 /sys/bus/acpi/devices/ASD0001:00/status15 /sys/bus/acpi/devices/HPQ6001:00/status15 /sys/bus/acpi/devices/HPQ6007:00/status15 /sys/bus/acpi/devices/HPQ8001:00/status15 /sys/bus/acpi/devices/LNXPOWER:00/status 1 /sys/bus/acpi/devices/LNXPOWER:02/status 1 /sys/bus/acpi/devices/LNXPOWER:04/status 1 /sys/bus/acpi/devices/LNXVIDEO:00/status 15 /sys/bus/acpi/devices/MSFT0101:00/status 15 /sys/bus/acpi/devices/PNP0103:00/status15 /sys/bus/acpi/devices/PNP0A08:00/status15 /sys/bus/acpi/devices/PNP0C01:00/status15 /sys/bus/acpi/devices/PNP0C02:02/status15 /sys/bus/acpi/devices/PNP0C0A:00/status31 /sys/bus/acpi/devices/PNP0C0C:00/status11 /sys/bus/acpi/devices/PNP0C0F:00/status11 /sys/bus/acpi/devices/PNP0C0F:01/status11 /sys/bus/acpi/devices/PNP0C0F:02/status11 /sys/bus/acpi/devices/PNP0C0F:03/status11 /sys/bus/acpi/devices/PNP0C0F:04/status11 /sys/bus/acpi/devices/PNP0C0F:05/status11 /sys/bus/acpi/devices/PNP0C0F:06/status11 /sys/bus/acpi/devices/PNP0C0F:07/status11 /sys/bus/acpi/devices/SMB0001:00/status15 /sys/bus/acpi/devices/SYN3226:00/status15 /sys/bus/acpi/devices/device:3b/status 15 !!Kernel Information !!-- Kernel release:4.8.0-52-generic Operating System: GNU/Linux Architecture: x86_64 Processor: x86_64 SMP Enabled: Yes !!ALSA Version !! Driver version: k4.8.0-52-generic Library version:1.0.14 Utilities version: 1.1.0 !!Loaded ALSA modules !!--- snd_hda_intel snd_hda_intel !!Sound Servers on this system !! Pulseaudio: Installed - Yes (/usr/bin/pulseaudio) Running - Yes !!Soundcards recognised by ALSA !!- 0 [HDMI ]: HDA-Intel - HDA ATI HDMI HDA ATI HDMI at 0xfeb64000 irq 39 1 [Generic]: HDA-Intel - HD-Audio Generic HD-Audio Generic at 0xfeb6 irq 40 !!PCI Soundcards installed in the system !!-- 00:01.1 Audio device: Advanced Micro Devices, Inc. [AMD/ATI] Device 15b3 00:09.2 Audio device: Advanced Micro Devices, Inc. [AMD] Device 157a !!Advanced information - PCI Vendor/Device/Subsystem ID's !!--- 00:01.1 0403: 1002:15b3 Subsystem: 103c:81fb -- 00:09.2 0403: 1022:157a Subsystem: 103c:81fb !!Modprobe options (Sound related) !! snd_pcsp: index=-2 snd_usb_audio: index=-2 snd_atiixp_modem: index=-2 snd_intel8x0m: index=-2 snd_via82xx_modem: index=-2 snd_atiixp_modem: index=-2 snd_intel8x0m: index=-2 snd_via82xx_modem: index=-2 snd_usb_audio: index=-2 snd_usb_caiaq: index=-2 snd_usb_ua101: index=-2 snd_usb_us122l: index=-2 snd_usb_usx2y: index=-2 snd_cmipci: mpu_port=0x330 fm_port=0x388 snd_pcsp: index=-2 snd_usb_audio: index=-2 !!Loaded sound module options !!--- !!Module: snd_hda_intel align_buffer_size : -1 bdl_pos_adj :
[Desktop-packages] [Bug 1914289] Re: Nautilus takes ~1 minute to open
[Expired for nautilus (Ubuntu) because there has been no activity for 60 days.] ** Changed in: nautilus (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1914289 Title: Nautilus takes ~1 minute to open Status in nautilus package in Ubuntu: Expired Bug description: Almost every time I try to launch Nautilus – whether via the panel, via the terminal, or by clicking "Open" buttons in programs – it takes close to 1 minute to launch. I have timed it using a watch, and it seems to take between 30 seconds and 1 minute from the relevant button is pressed before Nautilus appears on screen. This has been occurring for months. I think it started occuring after updating to Ubuntu 20.10, but I no longer remember precisely. I guessed it was a known issue that would be fixed, or just an issue specific to my setup, but now I am beginning to wonder whether I am facing some kind of true bug. All my hours of Google-fu and poking around the system has turned up nothing useful. In contrast to e.g. #1886021, there are no error messaged in the terminal that give any hints. Nor are there anything useful in the syslog – at least that I am able to spot. Given how infuriating it is to always have to wait for 30+ seconds to open any file dialog, I am very willing to help debug this. But I have now reached the limits of my (admittedly limited) debugging abilities. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: nautilus 1:3.38.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.8.0-41.46-generic 5.8.18 Uname: Linux 5.8.0-41-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu50.3 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Feb 2 21:00:46 2021 ExecutablePath: /usr/bin/nautilus InstallationDate: Installed on 2018-05-04 (1005 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: nautilus UpgradeStatus: Upgraded to groovy on 2020-11-07 (87 days ago) usr_lib_nautilus: evince3.38.0-1 file-roller 3.38.0-1 nautilus-extension-brasero3.12.2-6ubuntu1 nautilus-extension-gnome-terminal 3.38.0-1ubuntu1.1 nautilus-share0.7.3-2ubuntu3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1914289/+subscriptions -- Mailing list: https://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 1691608] Re: Sporadic crackling sound from headphones
[Expired for alsa-driver (Ubuntu) because there has been no activity for 60 days.] ** Changed in: alsa-driver (Ubuntu) Status: Incomplete => Expired -- 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/1691608 Title: Sporadic crackling sound from headphones Status in Ubuntu: Expired Status in alsa-driver package in Ubuntu: Expired Bug description: Ubuntu 16.04 64 bit HP Pavilion 15-aw077nr (Touch) Laptop Headphones had sporadic crackling sound. More often when volume increases over 30% Laptop has B speakers and headphones worked fine in Win10 before I replaced it with Ubuntu. Output from bash alsa-info.sh command: upload=true=true= !! !!ALSA Information Script v 0.4.64 !! !!Script ran on: Thu May 18 01:25:26 UTC 2017 !!Linux Distribution !!-- Ubuntu 16.04.2 LTS \n \l DISTRIB_ID=Ubuntu DISTRIB_DESCRIPTION="Ubuntu 16.04.2 LTS" NAME="Ubuntu" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Ubuntu 16.04.2 LTS" HOME_URL="http://www.ubuntu.com/; SUPPORT_URL="http://help.ubuntu.com/; BUG_REPORT_URL="http://bugs.launchpad.net/ubuntu/; UBUNTU_CODENAME=xenial !!DMI Information !!--- Manufacturer: HP Product Name: HP Pavilion Notebook Product Version: Firmware Version: F.23 Board Vendor: HP Board Name:81FB !!ACPI Device Status Information !!--- /sys/bus/acpi/devices/ACPI0003:00/status 15 /sys/bus/acpi/devices/ASD0001:00/status15 /sys/bus/acpi/devices/HPQ6001:00/status15 /sys/bus/acpi/devices/HPQ6007:00/status15 /sys/bus/acpi/devices/HPQ8001:00/status15 /sys/bus/acpi/devices/LNXPOWER:00/status 1 /sys/bus/acpi/devices/LNXPOWER:02/status 1 /sys/bus/acpi/devices/LNXPOWER:04/status 1 /sys/bus/acpi/devices/LNXVIDEO:00/status 15 /sys/bus/acpi/devices/MSFT0101:00/status 15 /sys/bus/acpi/devices/PNP0103:00/status15 /sys/bus/acpi/devices/PNP0A08:00/status15 /sys/bus/acpi/devices/PNP0C01:00/status15 /sys/bus/acpi/devices/PNP0C02:02/status15 /sys/bus/acpi/devices/PNP0C0A:00/status31 /sys/bus/acpi/devices/PNP0C0C:00/status11 /sys/bus/acpi/devices/PNP0C0F:00/status11 /sys/bus/acpi/devices/PNP0C0F:01/status11 /sys/bus/acpi/devices/PNP0C0F:02/status11 /sys/bus/acpi/devices/PNP0C0F:03/status11 /sys/bus/acpi/devices/PNP0C0F:04/status11 /sys/bus/acpi/devices/PNP0C0F:05/status11 /sys/bus/acpi/devices/PNP0C0F:06/status11 /sys/bus/acpi/devices/PNP0C0F:07/status11 /sys/bus/acpi/devices/SMB0001:00/status15 /sys/bus/acpi/devices/SYN3226:00/status15 /sys/bus/acpi/devices/device:3b/status 15 !!Kernel Information !!-- Kernel release:4.8.0-52-generic Operating System: GNU/Linux Architecture: x86_64 Processor: x86_64 SMP Enabled: Yes !!ALSA Version !! Driver version: k4.8.0-52-generic Library version:1.0.14 Utilities version: 1.1.0 !!Loaded ALSA modules !!--- snd_hda_intel snd_hda_intel !!Sound Servers on this system !! Pulseaudio: Installed - Yes (/usr/bin/pulseaudio) Running - Yes !!Soundcards recognised by ALSA !!- 0 [HDMI ]: HDA-Intel - HDA ATI HDMI HDA ATI HDMI at 0xfeb64000 irq 39 1 [Generic]: HDA-Intel - HD-Audio Generic HD-Audio Generic at 0xfeb6 irq 40 !!PCI Soundcards installed in the system !!-- 00:01.1 Audio device: Advanced Micro Devices, Inc. [AMD/ATI] Device 15b3 00:09.2 Audio device: Advanced Micro Devices, Inc. [AMD] Device 157a !!Advanced information - PCI Vendor/Device/Subsystem ID's !!--- 00:01.1 0403: 1002:15b3 Subsystem: 103c:81fb -- 00:09.2 0403: 1022:157a Subsystem: 103c:81fb !!Modprobe options (Sound related) !! snd_pcsp: index=-2 snd_usb_audio: index=-2 snd_atiixp_modem: index=-2 snd_intel8x0m: index=-2 snd_via82xx_modem: index=-2 snd_atiixp_modem: index=-2 snd_intel8x0m: index=-2 snd_via82xx_modem: index=-2 snd_usb_audio: index=-2 snd_usb_caiaq: index=-2 snd_usb_ua101: index=-2 snd_usb_us122l: index=-2 snd_usb_usx2y: index=-2 snd_cmipci: mpu_port=0x330 fm_port=0x388 snd_pcsp: index=-2 snd_usb_audio: index=-2 !!Loaded sound module options !!--- !!Module: snd_hda_intel align_buffer_size : -1 bdl_pos_adj :
[Desktop-packages] [Bug 1931563] Re: mozilla thunderbird 78.8.1 crashes on exit / quit almost everytime
[Expired for thunderbird (Ubuntu) because there has been no activity for 60 days.] ** Changed in: thunderbird (Ubuntu) Status: Incomplete => Expired -- 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/1931563 Title: mozilla thunderbird 78.8.1 crashes on exit / quit almost everytime Status in thunderbird package in Ubuntu: Expired Bug description: fossa 20.04.2 thunderbird 78.8.1 2 out of every 3 times i exit / quit mozilla thunderbird i get a crash reporter pop-up. please check the image attachment. i check the box which says ' Tell Mozilla about this crash so they can fix it ' & in the comment box i have been requesting for a fix & am doing this since 3 months now but to no avail hence am reporting this here now. i did search for a similar bug report but was unable to find one. requesting for a solution. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1931563/+subscriptions -- Mailing list: https://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 1910754] Re: package nvidia-340 (not installed) failed to install/upgrade: trying to overwrite '/lib/udev/rules.d/71-nvidia.rules', which is also in package nvidia-kernel-commo
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: nvidia-graphics-drivers-340 (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-340 in Ubuntu. https://bugs.launchpad.net/bugs/1910754 Title: package nvidia-340 (not installed) failed to install/upgrade: trying to overwrite '/lib/udev/rules.d/71-nvidia.rules', which is also in package nvidia-kernel-common-390 390.141-0ubuntu0.20.04.1 Status in nvidia-graphics-drivers-340 package in Ubuntu: Confirmed Bug description: As I don't really know what the cause of the problem is, all the information that I can give is that I installed the updates that were given. Prior to this the graphics were working properly. I can only access a single screen size and if I try to change it I am told that Full Screen is not available in this profile which is marked at present, nvida. if I try to initiate another profile I either get the same message or that profile is not available. I am sorry that I can give you no further information but this is all I know. ProblemType: Package DistroRelease: Ubuntu 20.04 Package: nvidia-340 (not installed) ProcVersionSignature: Ubuntu 5.4.0-54.60-generic 5.4.65 Uname: Linux 5.4.0-54-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 CasperMD5CheckResult: skip Date: Fri Jan 8 12:23:34 2021 DuplicateSignature: package:nvidia-340:(not installed) Unpacking nvidia-340 (340.108-0ubuntu2) ... dpkg: error processing archive /tmp/apt-dpkg-install-kxORBQ/31-nvidia-340_340.108-0ubuntu2_amd64.deb (--unpack): trying to overwrite '/lib/udev/rules.d/71-nvidia.rules', which is also in package nvidia-kernel-common-390 390.141-0ubuntu0.20.04.1 ErrorMessage: trying to overwrite '/lib/udev/rules.d/71-nvidia.rules', which is also in package nvidia-kernel-common-390 390.141-0ubuntu0.20.04.1 InstallationDate: Installed on 2020-07-29 (163 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.2ubuntu0.2 SourcePackage: nvidia-graphics-drivers-340 Title: package nvidia-340 (not installed) failed to install/upgrade: trying to overwrite '/lib/udev/rules.d/71-nvidia.rules', which is also in package nvidia-kernel-common-390 390.141-0ubuntu0.20.04.1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/1910754/+subscriptions -- Mailing list: https://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 1932328] Re: Thunderbird under Wayland does not correctly close (or manage) windows
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-ubuntu-dock in Ubuntu. https://bugs.launchpad.net/bugs/1932328 Title: Thunderbird under Wayland does not correctly close (or manage) windows Status in Mozilla Thunderbird: Unknown Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Confirmed Status in thunderbird package in Ubuntu: Confirmed Bug description: Using Ubuntu 21.04 (Hirsute) that starts in Wayland, by default. Thunderbird version: 78.11.0 with "gnome-support" package. Same problem in safe mode. Description: By default in this context, TB is a Wayland task. When opening a compose windows (or reply or transfer), sending mail apparently close the windows, but gnome shell continue to show multiple "points", as if multiple windows are still active. And after closing TB, it seems maintained in the same state, so it becomes impossible to relaunch it from the desk. But task manager of "looking glass" does not show it and it is possible to launch from terminal. Provisional solution: Modify .desktop file to launch with --display=:0 option, that force to use XWayland interface, as shown by xlsclients (for example). But it is actually a bug under Wayland context, that also badly interfer with many add-ons or extensions. To manage notifications about this bug go to: https://bugs.launchpad.net/thunderbird/+bug/1932328/+subscriptions -- Mailing list: https://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 1932328] Re: Thunderbird under Wayland does not correctly close (or manage) windows
I have managed to reproduce the issue with the upstream build for 78.13.0, downloaded from thunderbird.net, in a fully up-to-date hirsute VM, executed with MOZ_ENABLE_WAYLAND=1. This rules out a packaging problem. ** Also affects: gnome-shell-extension-ubuntu-dock (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to thunderbird in Ubuntu. https://bugs.launchpad.net/bugs/1932328 Title: Thunderbird under Wayland does not correctly close (or manage) windows Status in Mozilla Thunderbird: Unknown Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: New Status in thunderbird package in Ubuntu: Confirmed Bug description: Using Ubuntu 21.04 (Hirsute) that starts in Wayland, by default. Thunderbird version: 78.11.0 with "gnome-support" package. Same problem in safe mode. Description: By default in this context, TB is a Wayland task. When opening a compose windows (or reply or transfer), sending mail apparently close the windows, but gnome shell continue to show multiple "points", as if multiple windows are still active. And after closing TB, it seems maintained in the same state, so it becomes impossible to relaunch it from the desk. But task manager of "looking glass" does not show it and it is possible to launch from terminal. Provisional solution: Modify .desktop file to launch with --display=:0 option, that force to use XWayland interface, as shown by xlsclients (for example). But it is actually a bug under Wayland context, that also badly interfer with many add-ons or extensions. To manage notifications about this bug go to: https://bugs.launchpad.net/thunderbird/+bug/1932328/+subscriptions -- Mailing list: https://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 1932328] Re: Thunderbird under Wayland does not correctly close (or manage) windows
FWIW, I can also observe the issue in a fully up-to-date impish (upcoming 21.10) VM. -- 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/1932328 Title: Thunderbird under Wayland does not correctly close (or manage) windows Status in Mozilla Thunderbird: Unknown Status in thunderbird package in Ubuntu: Confirmed Bug description: Using Ubuntu 21.04 (Hirsute) that starts in Wayland, by default. Thunderbird version: 78.11.0 with "gnome-support" package. Same problem in safe mode. Description: By default in this context, TB is a Wayland task. When opening a compose windows (or reply or transfer), sending mail apparently close the windows, but gnome shell continue to show multiple "points", as if multiple windows are still active. And after closing TB, it seems maintained in the same state, so it becomes impossible to relaunch it from the desk. But task manager of "looking glass" does not show it and it is possible to launch from terminal. Provisional solution: Modify .desktop file to launch with --display=:0 option, that force to use XWayland interface, as shown by xlsclients (for example). But it is actually a bug under Wayland context, that also badly interfer with many add-ons or extensions. To manage notifications about this bug go to: https://bugs.launchpad.net/thunderbird/+bug/1932328/+subscriptions -- Mailing list: https://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 1932328] Re: Thunderbird under Wayland does not correctly close (or manage) windows
Commenting out the line that reads export MOZ_ENABLE_WAYLAND=1 in /usr/lib/thunderbird/thunderbird.sh makes the problem go away, because the application will now run as an XWayland client. -- 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/1932328 Title: Thunderbird under Wayland does not correctly close (or manage) windows Status in Mozilla Thunderbird: Unknown Status in thunderbird package in Ubuntu: Confirmed Bug description: Using Ubuntu 21.04 (Hirsute) that starts in Wayland, by default. Thunderbird version: 78.11.0 with "gnome-support" package. Same problem in safe mode. Description: By default in this context, TB is a Wayland task. When opening a compose windows (or reply or transfer), sending mail apparently close the windows, but gnome shell continue to show multiple "points", as if multiple windows are still active. And after closing TB, it seems maintained in the same state, so it becomes impossible to relaunch it from the desk. But task manager of "looking glass" does not show it and it is possible to launch from terminal. Provisional solution: Modify .desktop file to launch with --display=:0 option, that force to use XWayland interface, as shown by xlsclients (for example). But it is actually a bug under Wayland context, that also badly interfer with many add-ons or extensions. To manage notifications about this bug go to: https://bugs.launchpad.net/thunderbird/+bug/1932328/+subscriptions -- Mailing list: https://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 1938683] Re: Thunderbird still running after being closed
*** This bug is a duplicate of bug 1932328 *** https://bugs.launchpad.net/bugs/1932328 ** This bug has been marked a duplicate of bug 1932328 Thunderbird under Wayland does not correctly close (or manage) windows -- 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/1938683 Title: Thunderbird still running after being closed Status in thunderbird package in Ubuntu: Confirmed Bug description: The "number of windows" indicator in the Ubuntu Dash (the orange dots to the left of the app icon) is not cleared for Thunderbird, when a new e-mail is written in a new window. Ultimately, the indicators stay visible even after Thunderbird is closed completely, and it's no longer possible to launch thunderbird by left-clicking of the dash icon (middle-click works okay). Steps to reproduce: 1. Launch Thunderbird. There is one orange dot to the left of the thunderbird icon. 2. Write an e-mail and close the e-mail window 3. Observe that there are now two orange dots to the left of the thunderbird icon. Please see the screenshot for more details. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: gnome-shell 3.38.4-1ubuntu3~21.04.1 ProcVersionSignature: Ubuntu 5.11.0-25.27-generic 5.11.22 Uname: Linux 5.11.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Mon Aug 2 11:41:47 2021 DisplayManager: gdm3 InstallationDate: Installed on 2021-03-24 (130 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) RelatedPackageVersions: mutter-common 3.38.4-1ubuntu2 SourcePackage: gnome-shell UpgradeStatus: Upgraded to hirsute on 2021-04-23 (101 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1938683/+subscriptions -- Mailing list: https://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 1932328] Re: Thunderbird under Wayland does not correctly close (or manage) windows
** Bug watch added: Mozilla Bugzilla #1724656 https://bugzilla.mozilla.org/show_bug.cgi?id=1724656 ** Also affects: thunderbird via https://bugzilla.mozilla.org/show_bug.cgi?id=1724656 Importance: Unknown Status: Unknown ** Changed in: thunderbird (Ubuntu) Importance: Undecided => High -- 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/1932328 Title: Thunderbird under Wayland does not correctly close (or manage) windows Status in Mozilla Thunderbird: Unknown Status in thunderbird package in Ubuntu: Confirmed Bug description: Using Ubuntu 21.04 (Hirsute) that starts in Wayland, by default. Thunderbird version: 78.11.0 with "gnome-support" package. Same problem in safe mode. Description: By default in this context, TB is a Wayland task. When opening a compose windows (or reply or transfer), sending mail apparently close the windows, but gnome shell continue to show multiple "points", as if multiple windows are still active. And after closing TB, it seems maintained in the same state, so it becomes impossible to relaunch it from the desk. But task manager of "looking glass" does not show it and it is possible to launch from terminal. Provisional solution: Modify .desktop file to launch with --display=:0 option, that force to use XWayland interface, as shown by xlsclients (for example). But it is actually a bug under Wayland context, that also badly interfer with many add-ons or extensions. To manage notifications about this bug go to: https://bugs.launchpad.net/thunderbird/+bug/1932328/+subscriptions -- Mailing list: https://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 1939746] Re: Leaves open window marker on icon in gdm3 favourites sidebar after program has exited
*** This bug is a duplicate of bug 1932328 *** https://bugs.launchpad.net/bugs/1932328 ** This bug has been marked a duplicate of bug 1932328 Thunderbird under Wayland does not correctly close (or manage) windows -- 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/1939746 Title: Leaves open window marker on icon in gdm3 favourites sidebar after program has exited Status in thunderbird package in Ubuntu: New Bug description: Frequently leaves an open window marker on the Thunderbird icon in Gnome Desktop favourites sidebar. This is especially prevalent when the program has been launched as the default email client by some other process. Right clicking on the icon brings up the "New window/Compose New Message/Contacts/Remove from favourites/Quit". This menu is unresponsive and cannot be dismissed. This makes Thunderbird unusable. Ubuntu version is Hirsute. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1939746/+subscriptions -- Mailing list: https://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 1939916] Re: FTBFS 0.99.25-0ubuntu1 error: ‘__builtin_memcpy’ writing 5 bytes into a region of size 0 overflows the destination [-Werror=stringop-overflow=]
Thanks for the investigative work, Athos. As we discussed in private, I'm going to do a sync of sane-airscan from Debian experimental, which contains the patch necessary for this fix. The sync should also close this bug. Cheers. ** Changed in: sane-airscan (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to sane-airscan in Ubuntu. https://bugs.launchpad.net/bugs/1939916 Title: FTBFS 0.99.25-0ubuntu1 error: ‘__builtin_memcpy’ writing 5 bytes into a region of size 0 overflows the destination [-Werror=stringop- overflow=] Status in sane-airscan package in Ubuntu: Fix Released Bug description: https://people.canonical.com/~doko/ftbfs-report/test- rebuild-20210805-impish-impish.html https://launchpadlibrarian.net/552666330/buildlog_ubuntu-impish- amd64.sane-airscan_0.99.25-0ubuntu1_BUILDING.txt.gz In function ‘strcpy’, inlined from ‘trace_open’ at airscan-trace.c:113:5: /usr/include/x86_64-linux-gnu/bits/string_fortified.h:79:10: error: ‘__builtin_memcpy’ writing 5 bytes into a region of size 0 overflows the destination [-Werror=stringop-overflow=] 79 | return __builtin___strcpy_chk (__dest, __src, __glibc_objsize (__dest)); | ^ lto1: all warnings being treated as errors make[2]: *** [/tmp/ccRt7B21.mk:2: /tmp/cc0DKpF3.ltrans0.ltrans.o] Error 1 lto-wrapper: fatal error: make returned 2 exit status compilation terminated. /usr/bin/ld: error: lto-wrapper failed collect2: error: ld returned 1 exit status make[1]: *** [Makefile:167: test-zeroconf] Error 1 Upstream patch is available at https://github.com/alexpevzner/sane- airscan/commit/0b9be6d0c5cce6f8717eae51c218d4e8f967e79b To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sane-airscan/+bug/1939916/+subscriptions -- Mailing list: https://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 1939916] [NEW] FTBFS 0.99.25-0ubuntu1 error: ‘__builtin_memcpy’ writing 5 bytes into a region of size 0 overflows the destination [-Werror=stringop-overflow=]
Public bug reported: https://people.canonical.com/~doko/ftbfs-report/test- rebuild-20210805-impish-impish.html https://launchpadlibrarian.net/552666330/buildlog_ubuntu-impish- amd64.sane-airscan_0.99.25-0ubuntu1_BUILDING.txt.gz In function ‘strcpy’, inlined from ‘trace_open’ at airscan-trace.c:113:5: /usr/include/x86_64-linux-gnu/bits/string_fortified.h:79:10: error: ‘__builtin_memcpy’ writing 5 bytes into a region of size 0 overflows the destination [-Werror=stringop-overflow=] 79 | return __builtin___strcpy_chk (__dest, __src, __glibc_objsize (__dest)); | ^ lto1: all warnings being treated as errors make[2]: *** [/tmp/ccRt7B21.mk:2: /tmp/cc0DKpF3.ltrans0.ltrans.o] Error 1 lto-wrapper: fatal error: make returned 2 exit status compilation terminated. /usr/bin/ld: error: lto-wrapper failed collect2: error: ld returned 1 exit status make[1]: *** [Makefile:167: test-zeroconf] Error 1 Upstream patch is available at https://github.com/alexpevzner/sane- airscan/commit/0b9be6d0c5cce6f8717eae51c218d4e8f967e79b ** Affects: sane-airscan (Ubuntu) Importance: Undecided Assignee: Athos Ribeiro (athos-ribeiro) Status: New ** Tags: ftbfs -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to sane-airscan in Ubuntu. https://bugs.launchpad.net/bugs/1939916 Title: FTBFS 0.99.25-0ubuntu1 error: ‘__builtin_memcpy’ writing 5 bytes into a region of size 0 overflows the destination [-Werror=stringop- overflow=] Status in sane-airscan package in Ubuntu: New Bug description: https://people.canonical.com/~doko/ftbfs-report/test- rebuild-20210805-impish-impish.html https://launchpadlibrarian.net/552666330/buildlog_ubuntu-impish- amd64.sane-airscan_0.99.25-0ubuntu1_BUILDING.txt.gz In function ‘strcpy’, inlined from ‘trace_open’ at airscan-trace.c:113:5: /usr/include/x86_64-linux-gnu/bits/string_fortified.h:79:10: error: ‘__builtin_memcpy’ writing 5 bytes into a region of size 0 overflows the destination [-Werror=stringop-overflow=] 79 | return __builtin___strcpy_chk (__dest, __src, __glibc_objsize (__dest)); | ^ lto1: all warnings being treated as errors make[2]: *** [/tmp/ccRt7B21.mk:2: /tmp/cc0DKpF3.ltrans0.ltrans.o] Error 1 lto-wrapper: fatal error: make returned 2 exit status compilation terminated. /usr/bin/ld: error: lto-wrapper failed collect2: error: ld returned 1 exit status make[1]: *** [Makefile:167: test-zeroconf] Error 1 Upstream patch is available at https://github.com/alexpevzner/sane- airscan/commit/0b9be6d0c5cce6f8717eae51c218d4e8f967e79b To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sane-airscan/+bug/1939916/+subscriptions -- Mailing list: https://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 1939592] Re: Login screen (gdm3) is purple blank after switching userA -> userB -> userA again
** Description changed: Login screen (gdm3) is purple blank after switching userA -> userB -> userA again. Sometimes need to switch 5 times.. but definitely after around 5 times gdm3 breaks (it shows just a blank purple screen with the cursor). ## Workaround Ctrl+Alt+F3 (or F4.. F5...) until I get to the user I need to (and unlock the screensaver there). OR: switch to the console and run "exec sudo systemctl restart gdm3". ("exec" is not necessary but highly desirable from the security point of view, so there won't be a logged in session). ## Workaround 2 To not use gdm3. There are alternatives such as sddm or ligthdm: sudo apt install sddm OR sudo apt install lightdm - Ctrl+Alt+F5 (drop to a console) sudo systemctl stop gdm3 exec sudo systemctl start display-manager - ## Details arno@z390-linux:~$ dpkg -l gdm3 Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ Name Version Architecture Description +++-==-===--= ii gdm3 3.36.3-0ubuntu0.20.04.4 amd64GNOME Display Manager arno@z390-linux:~$ cat /proc/cmdline BOOT_IMAGE=/vmlinuz-5.11.0-25-generic root=UUID=a39515ec-3bed-493b-8286-3904a4aac9de ro quiet splash vt.handoff=7 arno@z390-linux:~$ nvidia-smi Wed Aug 11 16:42:07 2021 +-+ | NVIDIA-SMI 460.91.03Driver Version: 460.91.03CUDA Version: 11.2 | |---+--+--+ | GPU NamePersistence-M| Bus-IdDisp.A | Volatile Uncorr. ECC | | Fan Temp Perf Pwr:Usage/Cap| Memory-Usage | GPU-Util Compute M. | | | | MIG M. | |===+==+==| | 0 GeForce RTX 207... Off | :01:00.0 On | N/A | | 0% 37CP817W / 215W |473MiB / 7979MiB | 1% Default | | | | N/A | +---+--+--+ +-+ | Processes: | | GPU GI CIPID Type Process name GPU Memory | |ID ID Usage | |=| |0 N/A N/A 2211 G /usr/lib/xorg/Xorg 35MiB | |0 N/A N/A 10496 G /usr/lib/xorg/Xorg106MiB | |0 N/A N/A 10626 G /usr/bin/gnome-shell 157MiB | |0 N/A N/A 16828 G /usr/lib/xorg/Xorg 35MiB | |0 N/A N/A 38063 G ...A= --shared-files 80MiB | +-+ ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gdm3 3.36.3-0ubuntu0.20.04.4 ProcVersionSignature: Ubuntu 5.11.0-25.27~20.04.1-generic 5.11.22 Uname: Linux 5.11.0-25-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Aug 11 16:37:35 2021 InstallationDate: Installed on 2020-09-26 (318 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) SourcePackage: gdm3 UpgradeStatus: No upgrade log present (probably fresh install) ** Description changed: Login screen (gdm3) is purple blank after switching userA -> userB -> userA again. Sometimes need to switch 5 times.. but definitely after around 5 times gdm3 breaks (it shows just a blank purple screen with the cursor). ## Workaround Ctrl+Alt+F3 (or F4.. F5...) until I get to the user I need to (and unlock the screensaver there). OR: switch to the console and run "exec sudo systemctl restart gdm3". ("exec" is not necessary but highly desirable from the security point of view, so there won't be a logged in session). ## Workaround 2 To not use gdm3. There are alternatives such as sddm or ligthdm: - - sudo apt install sddm - - OR sudo apt install lightdm Ctrl+Alt+F5 (drop to a console) sudo systemctl stop gdm3 exec sudo systemctl start display-manager ## Details arno@z390-linux:~$ dpkg -l gdm3 Desired=Unknown/Install/Remove/Purge/Hold |
[Desktop-packages] [Bug 1939640] Re: libvpx FTBFS with LTO enabled
** Merge proposal linked: https://code.launchpad.net/~sergiodj/ubuntu/+source/libvpx/+git/libvpx/+merge/407095 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libvpx in Ubuntu. https://bugs.launchpad.net/bugs/1939640 Title: libvpx FTBFS with LTO enabled Status in libvpx package in Ubuntu: Confirmed Status in lto-disabled-list package in Ubuntu: Fix Released Bug description: libvpx FTBFS with LTO enabled on GCC 11, as can be seen here: https://people.canonical.com/~doko/ftbfs-report/test- rebuild-20210805-impish-impish.html#ubuntu-server https://launchpadlibrarian.net/552670245/buildlog_ubuntu-impish- amd64.libvpx_1.9.0-1_BUILDING.txt.gz g++ -Wl,-Bsymbolic-functions -flto=auto -Wl,-z,relro -Wl,-z,now -m64 -o test_libvpx ivfenc.c.o md5_utils.c.o test/active_map_refresh_test.cc.o test/active_map_test.cc.o test/alt_ref_aq_segment_test.cc.o test/altref_test.cc.o test/aq_segment_test.cc.o test/bench.cc.o test/borders_test.cc.o test/byte_alignment_test.cc.o test/config_test.cc.o test/cpu_speed_test.cc.o test/cq_test.cc.o test/decode_api_test.cc.o test/decode_corrupted.cc.o test/decode_svc_test.cc.o test/decode_test_driver.cc.o test/encode_api_test.cc.o test/encode_test_driver.cc.o test/error_resilience_test.cc.o test/external_frame_buffer_test.cc.o test/frame_size_tests.cc.o test/invalid_file_test.cc.o test/keyframe_test.cc.o test/level_test.cc.o test/realtime_test.cc.o test/resize_test.cc.o test/svc_datarate_test.cc.o test/svc_end_to_end_test.cc.o test/svc_test.cc.o test/test_libvpx.cc.o test/test_vector_test.cc.o test/test_vectors.cc.o test/timestamp_test.cc.o test/user_priv_test.cc.o test/vp8_datarate_test.cc.o test/vp9_datarate_test.cc.o test/vp9_end_to_end_test.cc.o test/vp9_ethread_test.cc.o test/vp9_lossless_test.cc.o test/vp9_motion_vector_test.cc.o test/vp9_skip_loopfilter_test.cc.o test/y4m_test.cc.o third_party/libwebm/mkvparser/mkvparser.cc.o third_party/libwebm/mkvparser/mkvreader.cc.o webmdec.cc.o y4menc.c.o y4minput.c.o -L. -lvpx -lgtest -lpthread -lm -lpthread ln -sf libvpx.so.6.3.0 vpx-vp8-vp9-x86_64-linux-v1.9.0/lib/libvpx.so.6 /usr/bin/ld: /tmp/ccsyaUhJ.ltrans0.ltrans.o:(.debug_info+0x1586f): undefined reference to `gtest_all.cc.5c9bdf8f' /usr/bin/ld: /tmp/ccsyaUhJ.ltrans0.ltrans.o:(.debug_info+0x158a5): undefined reference to `gtest_all.cc.5c9bdf8f' /usr/bin/ld: /tmp/ccsyaUhJ.ltrans0.ltrans.o:(.debug_info+0x158b2): undefined reference to `gtest_all.cc.5c9bdf8f' /usr/bin/ld: /tmp/ccsyaUhJ.ltrans0.ltrans.o:(.debug_info+0x158b7): undefined reference to `gtest_all.cc.5c9bdf8f' /usr/bin/ld: /tmp/ccsyaUhJ.ltrans0.ltrans.o:(.debug_info+0x158dd): undefined reference to `gtest_all.cc.5c9bdf8f' /usr/bin/ld: /tmp/ccsyaUhJ.ltrans0.ltrans.o:(.debug_info+0x15903): more undefined references to `gtest_all.cc.5c9bdf8f' follow collect2: error: ld returned 1 exit status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvpx/+bug/1939640/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
Re: [Desktop-packages] [Bug 1939640] Re: libvpx FTBFS with LTO enabled
On Friday, August 13 2021, Graham Inggs wrote: > libvpx was added to the '# packages not in main:' section. > > Please only use lto-disabled-list for packages not in main. Packages in > main should either be fixed or worked around in the package itself. Sorry about that. doko had pinged me about this mistake as well. I have removed libvpx from lto-disabled-list and uploaded the package again. I will fix the issue on libvpx. Thanks, -- Sergio GPG key ID: E92F D0B3 6B14 F1F4 D8E0 EB2F 106D A1C8 C3CB BF14 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libvpx in Ubuntu. https://bugs.launchpad.net/bugs/1939640 Title: libvpx FTBFS with LTO enabled Status in libvpx package in Ubuntu: Confirmed Status in lto-disabled-list package in Ubuntu: Fix Released Bug description: libvpx FTBFS with LTO enabled on GCC 11, as can be seen here: https://people.canonical.com/~doko/ftbfs-report/test- rebuild-20210805-impish-impish.html#ubuntu-server https://launchpadlibrarian.net/552670245/buildlog_ubuntu-impish- amd64.libvpx_1.9.0-1_BUILDING.txt.gz g++ -Wl,-Bsymbolic-functions -flto=auto -Wl,-z,relro -Wl,-z,now -m64 -o test_libvpx ivfenc.c.o md5_utils.c.o test/active_map_refresh_test.cc.o test/active_map_test.cc.o test/alt_ref_aq_segment_test.cc.o test/altref_test.cc.o test/aq_segment_test.cc.o test/bench.cc.o test/borders_test.cc.o test/byte_alignment_test.cc.o test/config_test.cc.o test/cpu_speed_test.cc.o test/cq_test.cc.o test/decode_api_test.cc.o test/decode_corrupted.cc.o test/decode_svc_test.cc.o test/decode_test_driver.cc.o test/encode_api_test.cc.o test/encode_test_driver.cc.o test/error_resilience_test.cc.o test/external_frame_buffer_test.cc.o test/frame_size_tests.cc.o test/invalid_file_test.cc.o test/keyframe_test.cc.o test/level_test.cc.o test/realtime_test.cc.o test/resize_test.cc.o test/svc_datarate_test.cc.o test/svc_end_to_end_test.cc.o test/svc_test.cc.o test/test_libvpx.cc.o test/test_vector_test.cc.o test/test_vectors.cc.o test/timestamp_test.cc.o test/user_priv_test.cc.o test/vp8_datarate_test.cc.o test/vp9_datarate_test.cc.o test/vp9_end_to_end_test.cc.o test/vp9_ethread_test.cc.o test/vp9_lossless_test.cc.o test/vp9_motion_vector_test.cc.o test/vp9_skip_loopfilter_test.cc.o test/y4m_test.cc.o third_party/libwebm/mkvparser/mkvparser.cc.o third_party/libwebm/mkvparser/mkvreader.cc.o webmdec.cc.o y4menc.c.o y4minput.c.o -L. -lvpx -lgtest -lpthread -lm -lpthread ln -sf libvpx.so.6.3.0 vpx-vp8-vp9-x86_64-linux-v1.9.0/lib/libvpx.so.6 /usr/bin/ld: /tmp/ccsyaUhJ.ltrans0.ltrans.o:(.debug_info+0x1586f): undefined reference to `gtest_all.cc.5c9bdf8f' /usr/bin/ld: /tmp/ccsyaUhJ.ltrans0.ltrans.o:(.debug_info+0x158a5): undefined reference to `gtest_all.cc.5c9bdf8f' /usr/bin/ld: /tmp/ccsyaUhJ.ltrans0.ltrans.o:(.debug_info+0x158b2): undefined reference to `gtest_all.cc.5c9bdf8f' /usr/bin/ld: /tmp/ccsyaUhJ.ltrans0.ltrans.o:(.debug_info+0x158b7): undefined reference to `gtest_all.cc.5c9bdf8f' /usr/bin/ld: /tmp/ccsyaUhJ.ltrans0.ltrans.o:(.debug_info+0x158dd): undefined reference to `gtest_all.cc.5c9bdf8f' /usr/bin/ld: /tmp/ccsyaUhJ.ltrans0.ltrans.o:(.debug_info+0x15903): more undefined references to `gtest_all.cc.5c9bdf8f' follow collect2: error: ld returned 1 exit status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvpx/+bug/1939640/+subscriptions -- Mailing list: https://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 1939895] [NEW] The application menu flickers in wayland
Public bug reported: In Ubuntu 21.04 in standard Ubuntu (Wayland) session on maximized Firefox 91 window when clicked on a hamburger menu, the menu starts to flicker. It happens on the DELL Inspiron 15 3000 laptop with the following graphic unit: 01:00.0 Display controller: Advanced Micro Devices, Inc. [AMD/ATI] Jet PRO [Radeon R5 M230 / R7 M260DX / Radeon 520 Mobile] (rev c3) It doesn't flicker on Xorg session, neither on another laptop with Intel graphics. It also doesn't happen when the window is not tied to the right screen edge. ** Affects: firefox (Ubuntu) Importance: Undecided Status: New -- 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/1939895 Title: The application menu flickers in wayland Status in firefox package in Ubuntu: New Bug description: In Ubuntu 21.04 in standard Ubuntu (Wayland) session on maximized Firefox 91 window when clicked on a hamburger menu, the menu starts to flicker. It happens on the DELL Inspiron 15 3000 laptop with the following graphic unit: 01:00.0 Display controller: Advanced Micro Devices, Inc. [AMD/ATI] Jet PRO [Radeon R5 M230 / R7 M260DX / Radeon 520 Mobile] (rev c3) It doesn't flicker on Xorg session, neither on another laptop with Intel graphics. It also doesn't happen when the window is not tied to the right screen edge. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1939895/+subscriptions -- Mailing list: https://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 1025388] Re: Internal mic stops working when plugging in headphones
I'm using Arch linux and have the same problem on my Razer Blade. Similar to https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1025388/comments/44, the solution for me was to turn off the jack detection. However, I went about it similar to what was posted here https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1025388/comments/43 That is, I used hdajackretask, but instead of making the headphone jack not connected, i turned on the advanced override option which revealed a "Jack detection" option under the mic. It was defaulted to Present, but I set it to not present, installed the boot override, and upon restart, both mic options are present and enabled and I can switch between either in pulse audio volume control. -- 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/1025388 Title: Internal mic stops working when plugging in headphones Status in linux package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Confirmed Bug description: I am currently running Quantal and when I plug headphones into my headphone socket (which has an icon of a headset next to it, so I presume it can take some kind of headset), the internal mic on my laptop stops working. If I unplug the headphones the internal mic works as normal. I tried this with two different sets of headphones (one of which has a mic, and the other I think has a mic too). ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: pulseaudio 1:2.0-0ubuntu1 ProcVersionSignature: Ubuntu 3.5.0-4.4-generic 3.5.0-rc6 Uname: Linux 3.5.0-4-generic i686 ApportVersion: 2.3-0ubuntu4 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jono 1860 F pulseaudio /dev/snd/pcmC0D0c: jono 1860 F...m pulseaudio Date: Mon Jul 16 11:01:32 2012 InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release i386 (20120423) ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/06/2011 dmi.bios.vendor: LENOVO dmi.bios.version: 8AET56WW (1.36 ) dmi.board.asset.tag: Not Available dmi.board.name: 4239CTO dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr8AET56WW(1.36):bd12/06/2011:svnLENOVO:pn4239CTO:pvrThinkPadT520:rvnLENOVO:rn4239CTO:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 4239CTO dmi.product.version: ThinkPad T520 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1025388/+subscriptions -- Mailing list: https://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 1911369] Re: [radeon] Horizontal lines of screen corruption after last update.
** Changed in: mesa (Ubuntu) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1911369 Title: [radeon] Horizontal lines of screen corruption after last update. Status in linux package in Ubuntu: Invalid Status in mesa package in Ubuntu: Invalid Bug description: A clean install is fine if I don't take updates. If I do take the updates and reboot then I get heavy video corruption. This just started today. This is a dual boot system. The windows system has no issues. Appears to be software and not a hardware issue. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.8.0-36.40~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-36-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Jan 12 21:18:27 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Tahiti PRO [Radeon HD 7950/8950 OEM / R9 280] [1002:679a] (prog-if 00 [VGA controller]) Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] Tahiti PRO2 [Radeon HD 7950 Boost] [1002:3000] InstallationDate: Installed on 2021-01-13 (0 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: Hewlett-Packard HP Z420 Workstation ProcEnviron: LANGUAGE=en_CA:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_CA.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-36-generic root=UUID=e1d90a30-a65a-46c5-bae3-c39bbf1a4e0e ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/29/2019 dmi.bios.release: 3.96 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: J61 v03.96 dmi.board.name: 1589 dmi.board.vendor: Hewlett-Packard dmi.board.version: 0.00 dmi.chassis.type: 6 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvrJ61v03.96:bd10/29/2019:br3.96:svnHewlett-Packard:pnHPZ420Workstation:pvr:rvnHewlett-Packard:rn1589:rvr0.00:cvnHewlett-Packard:ct6:cvr: dmi.product.family: 103C_53335X G=D dmi.product.name: HP Z420 Workstation dmi.product.sku: D8N02UC#ABA dmi.sys.vendor: Hewlett-Packard version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.1~20.04.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1911369/+subscriptions -- Mailing list: https://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 1930279] Re: [Ivy Bridge] flashing sliced triangles on screen
** Changed in: mesa (Ubuntu) Status: Incomplete => Invalid ** Changed in: linux (Ubuntu) Status: Incomplete => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1930279 Title: [Ivy Bridge] flashing sliced triangles on screen Status in linux package in Ubuntu: Invalid Status in mesa package in Ubuntu: Invalid Bug description: when i did upgrade my ubuntu from 20.04 to 20.10 i have small winking triangles on my screen, they sometimes will appear when i watching a youtube video they will appear on the video's seek bar or when i typing they will appear on selected texts,but the main and most annoying state of it happens when I am playing minecraft,my entire game screen has these little triangles ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: xorg 1:7.7+19ubuntu15 ProcVersionSignature: Ubuntu 5.8.0-53.60-generic 5.8.18 Uname: Linux 5.8.0-53-generic x86_64 ApportVersion: 2.20.11-0ubuntu50.7 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon May 31 18:05:33 2021 DistUpgraded: 2021-05-27 14:18:07,483 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: groovy DistroVariant: ubuntu DkmsStatus: virtualbox, 6.1.16, 5.4.0-73-generic, x86_64: installed virtualbox, 6.1.16, 5.8.0-53-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller [8086:0152] (rev 09) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller [1043:844d] InstallationDate: Installed on 2020-01-10 (507 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-53-generic root=UUID=a5a5279f-cdf5-4129-94fa-8f17f7401833 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to groovy on 2021-05-27 (4 days ago) dmi.bios.date: 03/19/2014 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1204 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: P8H61-M LX R2.0 dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1204:bd03/19/2014:br4.6:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP8H61-MLXR2.0:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.10.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1930279/+subscriptions -- Mailing list: https://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 1912030] Re: Crash unless ffmpeg direct rendering disabled with ATI X1400
does it happen with 21.04 or impish? ** Changed in: mesa (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1912030 Title: Crash unless ffmpeg direct rendering disabled with ATI X1400 Status in mesa package in Ubuntu: Incomplete Bug description: After upgrading to Ubuntu 20.10, VLC started crashing when I tried to play video. I tried changing to different video output methods, but none of them worked. In the past, I remember several methods working fine. In the ffmpeg advanced preferences page, disabling the direct rendering option made video playback work. I thought the vaapi errors VLC reports had something to do with it, but apparently not, because they still happen with successful playback. This is on a Dell Inspiron 6400 with ATI Mobility Radeon X1400, which doesn't support hardware decoding of the H.264 video I'm trying to play. Here's one backtrace: Thread 26 "vlc" received signal SIGSEGV, Segmentation fault. [Switching to Thread 0x7fff880df640 (LWP 11335)] __memcpy_ssse3 () at ../sysdeps/x86_64/multiarch/memcpy-ssse3.S:104 104 ../sysdeps/x86_64/multiarch/memcpy-ssse3.S: No such file or directory. (gdb) bt #0 __memcpy_ssse3 () at ../sysdeps/x86_64/multiarch/memcpy-ssse3.S:104 #1 0x77d03fc2 in picture_CopyPixels () at /usr/lib/x86_64-linux-gnu/libvlccore.so.9 #2 0x77d04016 in picture_Copy () at /usr/lib/x86_64-linux-gnu/libvlccore.so.9 #3 0x77cdf1ea in () at /usr/lib/x86_64-linux-gnu/libvlccore.so.9 #4 0x77ce1438 in () at /usr/lib/x86_64-linux-gnu/libvlccore.so.9 #5 0x77f67590 in start_thread (arg=0x7fff880df640) at pthread_create.c:463 #6 0x77e87223 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Also another: #0 __memcpy_ssse3 () at ../sysdeps/x86_64/multiarch/memcpy-ssse3.S:104 #1 0x7fffc7022bff in () at /usr/lib/x86_64-linux-gnu/dri/r300_dri.so #2 0x7fffc74f1d66 in () at /usr/lib/x86_64-linux-gnu/dri/r300_dri.so #3 0x7fffc6b41317 in () at /usr/lib/x86_64-linux-gnu/dri/r300_dri.so #4 0x7fffc6cb4b07 in () at /usr/lib/x86_64-linux-gnu/dri/r300_dri.so #5 0x7fffc6cb7dcc in () at /usr/lib/x86_64-linux-gnu/dri/r300_dri.so #6 0x7fffc6cbd9d9 in () at /usr/lib/x86_64-linux-gnu/dri/r300_dri.so #7 0x7fff885b2eee in () at /usr/lib/x86_64-linux-gnu/vlc/plugins/video_output/libgles2_plugin.so #8 0x7fff885ad2c5 in () at /usr/lib/x86_64-linux-gnu/vlc/plugins/video_output/libgles2_plugin.so #9 0x7fff885b3cee in () at /usr/lib/x86_64-linux-gnu/vlc/plugins/video_output/libgles2_plugin.so #10 0x77cdf4e6 in () at /usr/lib/x86_64-linux-gnu/libvlccore.so.9 #11 0x77ce1438 in () at /usr/lib/x86_64-linux-gnu/libvlccore.so.9 #12 0x77f67590 in start_thread (arg=0x7fff886bb640) at pthread_create.c:463 #13 0x77e87223 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: vlc 3.0.11.1-2 ProcVersionSignature: Ubuntu 5.8.0-36.40-generic 5.8.18 Uname: Linux 5.8.0-36-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu50.3 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Fri Jan 15 18:46:42 2021 InstallationDate: Installed on 2012-01-19 (3284 days ago) InstallationMedia: Xubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012) SourcePackage: vlc UpgradeStatus: Upgraded to groovy on 2020-10-21 (86 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1912030/+subscriptions -- Mailing list: https://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 1894973] Re: Better default settings for MESA and GALIUM_HUD
** Package changed: mesa (Ubuntu) => ubuntu -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1894973 Title: Better default settings for MESA and GALIUM_HUD Status in Ubuntu: New Bug description: I suggest to put these settings in ubuntu-gaming package or something similar GALLIUM_HUD_VISIBLE=false GALLIUM_HUD_TOGGLE_SIGNAL=10 GALLIUM_HUD_PERIOD=0.1 GALLIUM_HUD=.x10.y200.h80.w300.c240.dfps;.x10.y300.h80.w300.c100cpu+GPU-load:100;.x10.y400.h80.w300requested-VRAM+VRAM-usage References: https://docs.mesa3d.org/envvars.html#gallium-environment-variables To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1894973/+subscriptions -- Mailing list: https://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 1938959] Re: package mesa-va-drivers:amd64 21.0.3-0ubuntu0.2~20.04.1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before att
upgrade got interrupted or something like that ** Changed in: mesa (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1938959 Title: package mesa-va-drivers:amd64 21.0.3-0ubuntu0.2~20.04.1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting a removal Status in mesa package in Ubuntu: Invalid Bug description: ProblemType: Package DistroRelease: Ubuntu 20.04 Package: mesa-va-drivers:amd64 21.0.3-0ubuntu0.2~20.04.1 ProcVersionSignature: Ubuntu 5.11.0-25.27~20.04.1-generic 5.11.22 Uname: Linux 5.11.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip CompositorRunning: None Date: Wed Aug 4 19:47:44 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DpkgTerminalLog: [1mdpkg:[0m error processing package mesa-va-drivers:amd64 (--remove): package is in a very bad inconsistent state; you should reinstall it before attempting a removal [1mdpkg:[0m too many errors, stopping ErrorMessage: package is in a very bad inconsistent state; you should reinstall it before attempting a removal ExtraDebuggingInterest: Yes, including running git bisection searches InstallationDate: Installed on 2020-04-01 (490 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 0781:5567 SanDisk Corp. Cruzer Blade Bus 001 Device 003: ID 045e:0752 Microsoft Corp. Wired Keyboard 400 Bus 001 Device 002: ID 413c:301a Dell Computer Corp. Dell MS116 USB Optical Mouse Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/6p, 5000M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/12p, 480M |__ Port 3: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 1.5M |__ Port 4: Dev 3, If 0, Class=Human Interface Device, Driver=usbhid, 1.5M |__ Port 5: Dev 4, If 0, Class=Mass Storage, Driver=usb-storage, 480M MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-25-generic root=UUID=d7a0cf22-bba9-4c79-89f5-0d805b99da00 ro quiet splash vt.handoff=7 Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.6 SourcePackage: mesa Title: package mesa-va-drivers:amd64 21.0.3-0ubuntu0.2~20.04.1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting a removal UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/24/2019 dmi.bios.release: 5.12 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1208 dmi.board.asset.tag: Default string dmi.board.name: B250 MINING EXPERT dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1208:bd09/24/2019:br5.12:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnB250MININGEXPERT:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.105-3~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.3-0ubuntu0.2~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1~20.04.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1938959/+subscriptions -- Mailing list: https://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 1901694] Re: [radeon] No hardware acceleration on AMD Seymour [Radeon HD 6400M/7400M Series]
assuming this is fixed in a newer release, file a new bug if not ** Changed in: mesa (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1901694 Title: [radeon] No hardware acceleration on AMD Seymour [Radeon HD 6400M/7400M Series] Status in mesa package in Ubuntu: Invalid Bug description: Computer HP EliteBook 8460p. It uses hybrid graphics card. Processor Intel Core i5-2520M CPU @ 2.50GHz × 4; 2nd generation. The system only runs well with llvmpipe (LLVM 6.0, 256 bits) graphic software, AMD Caicos sometimes it's charged too, but the graphic display have problems and don't goes fine or fluid. Maybe there is no support for the processor graphics because It's a little bit old. I don't know how to install AMD proprietary drivers, It maybe solve the problem. I installed Ubuntu 20.04 LTS but don't works, It don't charge any graphic interface, only a black screen. I only uses the system in recovery mode. For that reason I returned to Ubuntu 16.04 LTS but my graphics don't have hardware acceleration, only software acceleration. When I tried to play (Super Tux Kart for example) I expected a berry poor graphic improvement, so I can't play It. Thanks for your time and attention! ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3.1 ProcVersionSignature: Ubuntu 4.15.0-122.124~16.04.1-generic 4.15.18 Uname: Linux 4.15.0-122-generic x86_64 .tmp.unity_support_test.1: ApportVersion: 2.20.1-0ubuntu2.24 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Tue Oct 27 05:47:39 2020 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Seymour [Radeon HD 6400M/7400M Series] [1002:6760] (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Radeon HD 6470M [103c:161e] InstallationDate: Installed on 2020-10-25 (1 days ago) InstallationMedia: Ubuntu 16.04.7 LTS "Xenial Xerus" - Release amd64 (20200806) MachineType: Hewlett-Packard HP EliteBook 8460p ProcEnviron: LANGUAGE=es_CR:es PATH=(custom, no user) LANG=es_CR.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-122-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 Renderer: Software SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/12/2015 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68SCF Ver. F.60 dmi.board.name: 161C dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 97.4E dmi.chassis.asset.tag: IS09189 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr68SCFVer.F.60:bd03/12/2015:svnHewlett-Packard:pnHPEliteBook8460p:pvrA0001D02:rvnHewlett-Packard:rn161C:rvrKBCVersion97.4E:cvnHewlett-Packard:ct10:cvr: dmi.product.family: 103C_5336AN dmi.product.name: HP EliteBook 8460p dmi.product.version: A0001D02 dmi.sys.vendor: Hewlett-Packard version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.91-2~16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~16.04.1 version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A xserver.bootTime: Tue Oct 27 05:43:49 2020 xserver.configfile: default xserver.errors: AIGLX: reverting to software rendering xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.19.6-1ubuntu4.1~16.04.4 xserver.video_driver: radeon To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1901694/+subscriptions -- Mailing list: https://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 1924757] Re: Ubuntu debug mirror is out of sync
I don't know why 20.2.6 build is not available there, but the current backport is, and it's not due to the package anyway but something else ** Changed in: mesa (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1924757 Title: Ubuntu debug mirror is out of sync Status in mesa package in Ubuntu: Fix Released Bug description: lsb_release -rd Description: Ubuntu 20.04.2 LTS Release: 20.04 When using the Ubuntu debug mirror (ddebs.ubuntu.com) and the official mirror (archive.ubuntu.com), it is not possible to install some debug symbols. For example: apt install mesa-vulkan-drivers-dbgsym Reading package lists... Done Building dependency tree Reading state information... Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: mesa-vulkan-drivers-dbgsym : Depends: mesa-vulkan-drivers (= 20.0.4-2ubuntu1) but 20.2.6-0ubuntu0.20.04.1 is to be installed E: Unable to correct problems, you have held broken packages. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1924757/+subscriptions -- Mailing list: https://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 1920067] Re: Xorg with EVDI can't start with Mesa 21.0
*** This bug is a duplicate of bug 1931547 *** https://bugs.launchpad.net/bugs/1931547 ** This bug has been marked a duplicate of bug 1931547 DisplayLink displays are black after Mesa update -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1920067 Title: Xorg with EVDI can't start with Mesa 21.0 Status in mesa package in Ubuntu: New Status in xorg-server package in Ubuntu: New Bug description: As I indicated in a bug report I filed earlier today, https://bugs.launchpad.net/ubuntu/+source/evdi/+bug/1920059, evdi-dkms can no longer compile the evdi kernel module with the 5.11 kernel. So, to work around this, I need to keep using the 5.10 kernel instead. But I can't, because when I boot with the 5.10 kernel this is what shows up in /var/log/Xorg.0.log when gdm3 tries to start up the login screen (note: I have an NVIDIA graphics card, which is why (I believe) Wayland isn't being used here): [ 857.957] (EE) modeset(G0): drmSetMaster failed: Device or resource busy [ 857.957] (EE) Fatal server error: [ 857.957] (EE) AddScreen/ScreenInit failed for gpu driver 0 -1 [ 857.957] (EE) [ 857.957] (EE) Please consult the The X.Org Foundation support at http://wiki.x.org for help. [ 857.957] (EE) Please also check the log file at "/var/log/Xorg.0.log" for additional information. [ 857.957] (EE) [ 858.144] (EE) Server terminated with error (1). Closing log file. This is probably not what you will see in the Xorg.0.log (if any) attached automatically to this bug because I've completely wiped the evdi kernel module from my system since that was the only way I could get a display manager up so I could use ubuntu-bug to submit this bug. Here's what I updated today: 2021-03-18 15:03:26 upgrade sysvinit-utils:amd64 2.96-5ubuntu1 2.96-6ubuntu1 2021-03-18 15:03:27 upgrade cron:amd64 3.0pl1-136ubuntu1 3.0pl1-136ubuntu2 2021-03-18 15:03:28 upgrade gpg-wks-client:amd64 2.2.20-1ubuntu2 2.2.20-1ubuntu3 2021-03-18 15:03:28 upgrade dirmngr:amd64 2.2.20-1ubuntu2 2.2.20-1ubuntu3 2021-03-18 15:03:29 upgrade gpg-wks-server:amd64 2.2.20-1ubuntu2 2.2.20-1ubuntu3 2021-03-18 15:03:29 upgrade gnupg-utils:amd64 2.2.20-1ubuntu2 2.2.20-1ubuntu3 2021-03-18 15:03:29 upgrade gpg-agent:amd64 2.2.20-1ubuntu2 2.2.20-1ubuntu3 2021-03-18 15:03:30 upgrade gpg:amd64 2.2.20-1ubuntu2 2.2.20-1ubuntu3 2021-03-18 15:03:30 upgrade gpgconf:amd64 2.2.20-1ubuntu2 2.2.20-1ubuntu3 2021-03-18 15:03:30 upgrade gnupg-l10n:all 2.2.20-1ubuntu2 2.2.20-1ubuntu3 2021-03-18 15:03:31 upgrade gnupg:all 2.2.20-1ubuntu2 2.2.20-1ubuntu3 2021-03-18 15:03:31 upgrade gpgsm:amd64 2.2.20-1ubuntu2 2.2.20-1ubuntu3 2021-03-18 15:03:31 upgrade gpgv:amd64 2.2.20-1ubuntu2 2.2.20-1ubuntu3 2021-03-18 15:03:32 upgrade libjs-sphinxdoc:all 3.5.1-2 3.5.2-1 2021-03-18 15:03:33 upgrade libnfsidmap2:amd64 0.25-5.1ubuntu2 0.25-6 2021-03-18 15:03:33 install linux-modules-5.11.0-11-generic:amd64 5.11.0-11.12 2021-03-18 15:03:35 install linux-image-5.11.0-11-generic:amd64 5.11.0-11.12 2021-03-18 15:03:36 install linux-modules-extra-5.11.0-11-generic:amd64 5.11.0-11.12 2021-03-18 15:03:40 upgrade linux-generic:amd64 5.10.0.14.16 5.11.0.11.12 2021-03-18 15:03:40 upgrade linux-image-generic:amd64 5.10.0.14.16 5.11.0.11.12 2021-03-18 15:03:41 install linux-headers-5.11.0-11:all 5.11.0-11.12 2021-03-18 15:03:44 install linux-headers-5.11.0-11-generic:amd64 5.11.0-11.12 2021-03-18 15:03:47 upgrade linux-headers-generic:amd64 5.10.0.14.16 5.11.0.11.12 2021-03-18 15:03:47 upgrade linux-libc-dev:amd64 5.10.0-14.15 5.11.0-11.12 2021-03-18 15:03:48 upgrade slack-desktop:amd64 4.13.0 4.14.0 2021-03-18 15:03:52 upgrade xwayland:amd64 2:1.20.10-3ubuntu3 2:21.0.99.902-0ubuntu1 2021-03-18 15:56:42 upgrade at:amd64 3.1.23-1.1ubuntu2 3.1.23-1.1ubuntu3 At first glance I don't understand how any of these could be causing this behavior. Potentially relevant: I had to recompile and reinstall the evdi kernel module while booted into 5.10 because when I install the 5.11 kernel dkms removed the module from 5.10 and then failed to rebuild it because the 5.11 build failed (or something I don't really understand why dkms does what it does *sigh*). I don't see how that should matter because the recompiled version of the module should have been identical, but *shrug*. As noted above, when I remove the evdi kernel modules from /lib/modules and reboot with 5.10 the problem goes away, so this does appear to be an evdi issue. In short: despite the fact that it's not clear how upgrading any of the modules listed above would cause evdi that used to work to suddenly stop working, that appears to be the case. Any advice would be appreciated because now I can't use the displays connected to my DisplayLink hub with either 5.10
[Desktop-packages] [Bug 1782984] Re: Assertion `!xcb_xlib_threads_sequence_lost' failed with multiple applications
** Description changed: + [Impact] + + There is a race in libx11 causing applications to randomly abort. It's + not trivial to reproduce, but there are enough duplicates that this + deserves an SRU to bionic & focal. + + [Fix] + + Backport a commit from upstream: + + From dbb55e1a5e82870466b095097d9e46046680ec25 Mon Sep 17 00:00:00 2001 + From: Frediano Ziglio + Date: Wed, 29 Jan 2020 09:06:54 + + Subject: [PATCH] Fix poll_for_response race condition + + In poll_for_response is it possible that event replies are skipped + and a more up to date message reply is returned. + This will cause next poll_for_event call to fail aborting the program. + + This was proved using some slow ssh tunnel or using some program + to slow down server replies (I used a combination of xtrace and strace). + + How the race happens: + - program enters into poll_for_response; + - poll_for_event is called but the server didn't still send the reply; + - pending_requests is not NULL because we send a request (see call + to append_pending_request in _XSend); + - xcb_poll_for_reply64 is called from poll_for_response; + - xcb_poll_for_reply64 will read from server, at this point + server reply with an event (say sequence N) and the reply to our + last request (say sequence N+1); + - xcb_poll_for_reply64 returns the reply for the request we asked; + - last_request_read is set to N+1 sequence in poll_for_response; + - poll_for_response returns the response to the request; + - poll_for_event is called (for instance from another poll_for_response); + - event with sequence N is retrieved; + - the N sequence is widen, however, as the "new" number computed from + last_request_read is less than N the number is widened to N + 2^32 + (assuming last_request_read is still contained in 32 bit); + - poll_for_event enters the nested if statement as req is NULL; + - we compare the widen N (which now does not fit into 32 bit) with + request (which fits into 32 bit) hitting the throw_thread_fail_assert. + + To avoid the race condition and to avoid the sequence to go back + I check again for new events after getting the response and + return this last event if present saving the reply to return it + later. + + To test the race and the fix it's helpful to add a delay (I used a + "usleep(5000)") before calling xcb_poll_for_reply64. + + Original patch written by Frediano Ziglio, see + https://gitlab.freedesktop.org/xorg/lib/libx11/-/merge_requests/34 + + Reworked primarily for readability by Peter Hutterer, see + https://gitlab.freedesktop.org/xorg/lib/libx11/-/merge_requests/53 + + Signed-off-by: Peter Hutterer + + bionic needs another commit so that the real fix applies. + + [Test case] + + It's a race condition, the SRU sponsor (tjaalton) does not have a test + case for this, but the bug subscribers seem to. + + + [Where things could go wrong] + + In theory there might be a case where a race still happens, but since + this has been upstream for a year now with no follow-up commits, it's + safe to assume that there are no regressions. + + + -- + STEPS TO REPRODUCE == The bug seems to occur when clicking on a file or folder. It is random and difficult to provide clear steps to reproduce. It is, however, a common situation. EXPECTED RESULTS pcmanfm works without problem. ACTUAL RESULTS == All pcmanfm windows become unresponsive, though background processes (e.g. copying) may continue without problem. with the same error message in ~/.cache/lxsession/LXDE/run.log: [xcb] Unknown sequence number while processing queue [xcb] Most likely this is a multi-threaded client and XInitThreads has not been called [xcb] Aborting, sorry about that. pcmanfm: xcb_io.c:259: poll_for_event: Assertion `!xcb_xlib_threads_sequence_lost' failed. ** Message: 19:58:49.267: app.vala:130: pcmanfm exit with this type of exit: 6 ** Message: 19:58:49.268: app.vala:148: Exit not normal, try to reload (note the timestamp on the message will vary) AFFECTED VERSIONS = 1.2.5-3ubuntu1 NOT 1.2.4-1ubuntu0.1 UPSTREAM BUG https://sourceforge.net/p/pcmanfm/bugs/1089/ ADDITIONAL NOTES Other GTK2 file managers (e.g. Thunar) and applications (e.g. GIMP, Leafpad) seem to have the same problems. This is probably at least rooted in a GTK2 bug: https://bugs.launchpad.net/ubuntu/+source/gtk+2.0/+bug/1808710 To further assert this, note that there is a SpaceFM file manager that is available in GTK2 and GTK3. The GTK2 version displays the behavior. The GTK3 version does not. Same with LibreOffice. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libx11 in Ubuntu. https://bugs.launchpad.net/bugs/1782984 Title: Assertion `!xcb_xlib_threads_sequence_lost' failed with multiple applications Status in libx11 package in Ubuntu:
[Desktop-packages] [Bug 1939664] Re: Several potential bugs of memory leak
ok.thank you. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libx11 in Ubuntu. https://bugs.launchpad.net/bugs/1939664 Title: Several potential bugs of memory leak Status in libx11 package in Ubuntu: Invalid Bug description: Ubuntu version: 18.04 libx11-xcb-dev version:1.6.2 Hello,I found some potential bugs in package libx11-xcb-dev,and the microsoft word file in the attachment I uploaded shows the occurrence process of the bug in a graphical way.Would you help me check whether the bugs mentioned below are true? I'm not 100% sure that the bugs I submitted is correct. I hope you don't mind seeing the wrong bug I submitted.Thank you very much for your patience. In file libx11-1.6.2/modules/im/ximcp/imLcPrs.c,defination of parsestringfile,line 733. The statement "tbp=malloc(size);"allocate memory to tbp and in line 733,if select false branch at this statement,tbp will not be freed correctly.the process of this potential bug is shown in figure 1. In file libx11-1.6.2/src/xlibi18n/lcDB.c,defination of f_numeric,line 882. The statement "wordp=malloc(len+1);"allocate memory to wordp and in line 883,if select false branch at this statement,function f_numeric will go on to execute.In line 910,if select false branch at this statement,wordp will not be freed correctly.the process of this potential bug is shown in figure 2. In file libx11-1.6.2/src/xlibi18n/lcDB.c,defination of f_numeric,line 882. The statement "wordp=malloc(len+1);"allocate memory to wordp and in line 883,if select false branch at this statement,function f_numeric will go on to execute.and if select true branch in line 938,flow goto err,In line 989,if select false branch here,wordp will not be freed correctly.the process of this potential bug is shown in figure 3. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libx11/+bug/1939664/+subscriptions -- Mailing list: https://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 1936930] Re: [SRU] libreoffice 7.1.5 for hirsute
Upgraded libreoffice from 1:7.1.4-0ubuntu0.21.04.1 to 1:7.1.5-0ubuntu0.21.04.1 from hirsute-proposed in a clean and up-to-date hirsute amd64 VM, and successfully ran test plan at https://wiki.ubuntu.com/Process/Merges/TestPlans/libreoffice. ** Tags removed: verification-needed verification-needed-hirsute ** Tags added: verification-done verification-done-hirsute -- 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/1936930 Title: [SRU] libreoffice 7.1.5 for hirsute Status in libreoffice package in Ubuntu: Fix Committed Status in libreoffice source package in Hirsute: Fix Committed Bug description: [Impact] * LibreOffice 7.1.5 is in its fifth bugfix release of the 7.1 line: https://wiki.documentfoundation.org/ReleasePlan/7.1#7.1.5_release * Version 7.1.4 is currently released in hirsute. For a list of fixed bugs compared to 7.1.4 see the list of bugs fixed in the release candidates of 7.1.5 (that's a total of 55 bugs): https://wiki.documentfoundation.org/Releases/7.1.5/RC1#List_of_fixed_bugs https://wiki.documentfoundation.org/Releases/7.1.5/RC2#List_of_fixed_bugs * Given the nature of the project, the complexity of the codebase and the high level of quality assurance upstream, it is preferable to SRU a minor release rather than cherry-pick selected bug fixes. [Testing] * Upstream testing. Bugs fixed upstream typically include unit/regression tests, and the release itself is extensively exercised (both in an automated manner and manually). * A recent set of upstream's automated jenkins testing can be found here: https://ci.libreoffice.org/job/gerrit_71/1315/ * More information about the upstream QA testing can be found here: * Automated tests https://wiki.documentfoundation.org/QA/Testing/Automated_Tests * Automated UI tests https://wiki.documentfoundation.org/Development/UITests * Regression tests https://wiki.documentfoundation.org/QA/Testing/Regression_Tests * Feature tests https://wiki.documentfoundation.org/QA/Testing/Feature_Tests * Launchpad testing. The libreoffice packages include autopkgtests that were run and verified as passing. * [amd64] https://autopkgtest.ubuntu.com/results/autopkgtest-hirsute-libreoffice-libreoffice-prereleases/hirsute/amd64/libr/libreoffice/20210721_015954_72804@/log.gz * [arm64] https://autopkgtest.ubuntu.com/results/autopkgtest-hirsute-libreoffice-libreoffice-prereleases/hirsute/arm64/libr/libreoffice/20210720_213917_391df@/log.gz * [armhf] https://autopkgtest.ubuntu.com/results/autopkgtest-hirsute-libreoffice-libreoffice-prereleases/hirsute/armhf/libr/libreoffice/20210720_200245_11c7a@/log.gz * [ppc64el] https://autopkgtest.ubuntu.com/results/autopkgtest-hirsute-libreoffice-libreoffice-prereleases/hirsute/ppc64el/libr/libreoffice/20210720_214546_dc091@/log.gz * [s390x] https://autopkgtest.ubuntu.com/results/autopkgtest-hirsute-libreoffice-libreoffice-prereleases/hirsute/s390x/libr/libreoffice/20210721_003436_1679f@/log.gz * General smoke testing of all the applications in the office suite were carried out by going through the manual testplan as documented by: https://wiki.ubuntu.com/Process/Merges/TestPlans/libreoffice [Regression Potential] * A minor release with a total of 55 bug fixes always carries the potential for introducing regressions, even though it is a bugfix-only release, meaning that no new features were added, and no existing features were removed. * A combination of autopkgtests and careful smoke testing as described above should provide reasonable confidence that no regressions sneaked in. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1936930/+subscriptions -- Mailing list: https://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 1939664] Re: Several potential bugs of memory leak
sorry, I don't have time for that just look at the current upstream source, I'm assuming they're all fixed since... 1.6.2 was released eight years ago ** Changed in: libx11 (Ubuntu) Status: Incomplete => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libx11 in Ubuntu. https://bugs.launchpad.net/bugs/1939664 Title: Several potential bugs of memory leak Status in libx11 package in Ubuntu: Invalid Bug description: Ubuntu version: 18.04 libx11-xcb-dev version:1.6.2 Hello,I found some potential bugs in package libx11-xcb-dev,and the microsoft word file in the attachment I uploaded shows the occurrence process of the bug in a graphical way.Would you help me check whether the bugs mentioned below are true? I'm not 100% sure that the bugs I submitted is correct. I hope you don't mind seeing the wrong bug I submitted.Thank you very much for your patience. In file libx11-1.6.2/modules/im/ximcp/imLcPrs.c,defination of parsestringfile,line 733. The statement "tbp=malloc(size);"allocate memory to tbp and in line 733,if select false branch at this statement,tbp will not be freed correctly.the process of this potential bug is shown in figure 1. In file libx11-1.6.2/src/xlibi18n/lcDB.c,defination of f_numeric,line 882. The statement "wordp=malloc(len+1);"allocate memory to wordp and in line 883,if select false branch at this statement,function f_numeric will go on to execute.In line 910,if select false branch at this statement,wordp will not be freed correctly.the process of this potential bug is shown in figure 2. In file libx11-1.6.2/src/xlibi18n/lcDB.c,defination of f_numeric,line 882. The statement "wordp=malloc(len+1);"allocate memory to wordp and in line 883,if select false branch at this statement,function f_numeric will go on to execute.and if select true branch in line 938,flow goto err,In line 989,if select false branch here,wordp will not be freed correctly.the process of this potential bug is shown in figure 3. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libx11/+bug/1939664/+subscriptions -- Mailing list: https://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 1939664] Re: Several potential bugs of memory leak
It seems that there is a problem with the deployment of my mirror site, resulting in the download of old version 1.6.2, but these bugs may exist in version 1.6.2. I will re analyze the problems in version 1.6.4,but I don't want the my effort in analyzing the source code of version 1.6.2 to be wasted.I just want to confirm whether bugs I submitted are true. Can you help me see the bugs I have submitted that may exist in version 1.6.2?I will very appreciate for that. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libx11 in Ubuntu. https://bugs.launchpad.net/bugs/1939664 Title: Several potential bugs of memory leak Status in libx11 package in Ubuntu: Incomplete Bug description: Ubuntu version: 18.04 libx11-xcb-dev version:1.6.2 Hello,I found some potential bugs in package libx11-xcb-dev,and the microsoft word file in the attachment I uploaded shows the occurrence process of the bug in a graphical way.Would you help me check whether the bugs mentioned below are true? I'm not 100% sure that the bugs I submitted is correct. I hope you don't mind seeing the wrong bug I submitted.Thank you very much for your patience. In file libx11-1.6.2/modules/im/ximcp/imLcPrs.c,defination of parsestringfile,line 733. The statement "tbp=malloc(size);"allocate memory to tbp and in line 733,if select false branch at this statement,tbp will not be freed correctly.the process of this potential bug is shown in figure 1. In file libx11-1.6.2/src/xlibi18n/lcDB.c,defination of f_numeric,line 882. The statement "wordp=malloc(len+1);"allocate memory to wordp and in line 883,if select false branch at this statement,function f_numeric will go on to execute.In line 910,if select false branch at this statement,wordp will not be freed correctly.the process of this potential bug is shown in figure 2. In file libx11-1.6.2/src/xlibi18n/lcDB.c,defination of f_numeric,line 882. The statement "wordp=malloc(len+1);"allocate memory to wordp and in line 883,if select false branch at this statement,function f_numeric will go on to execute.and if select true branch in line 938,flow goto err,In line 989,if select false branch here,wordp will not be freed correctly.the process of this potential bug is shown in figure 3. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libx11/+bug/1939664/+subscriptions -- Mailing list: https://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 1939640] Re: libvpx FTBFS with LTO enabled
libvpx was added to the '# packages not in main:' section. Please only use lto-disabled-list for packages not in main. Packages in main should either be fixed or worked around in the package itself. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libvpx in Ubuntu. https://bugs.launchpad.net/bugs/1939640 Title: libvpx FTBFS with LTO enabled Status in libvpx package in Ubuntu: Confirmed Status in lto-disabled-list package in Ubuntu: Fix Released Bug description: libvpx FTBFS with LTO enabled on GCC 11, as can be seen here: https://people.canonical.com/~doko/ftbfs-report/test- rebuild-20210805-impish-impish.html#ubuntu-server https://launchpadlibrarian.net/552670245/buildlog_ubuntu-impish- amd64.libvpx_1.9.0-1_BUILDING.txt.gz g++ -Wl,-Bsymbolic-functions -flto=auto -Wl,-z,relro -Wl,-z,now -m64 -o test_libvpx ivfenc.c.o md5_utils.c.o test/active_map_refresh_test.cc.o test/active_map_test.cc.o test/alt_ref_aq_segment_test.cc.o test/altref_test.cc.o test/aq_segment_test.cc.o test/bench.cc.o test/borders_test.cc.o test/byte_alignment_test.cc.o test/config_test.cc.o test/cpu_speed_test.cc.o test/cq_test.cc.o test/decode_api_test.cc.o test/decode_corrupted.cc.o test/decode_svc_test.cc.o test/decode_test_driver.cc.o test/encode_api_test.cc.o test/encode_test_driver.cc.o test/error_resilience_test.cc.o test/external_frame_buffer_test.cc.o test/frame_size_tests.cc.o test/invalid_file_test.cc.o test/keyframe_test.cc.o test/level_test.cc.o test/realtime_test.cc.o test/resize_test.cc.o test/svc_datarate_test.cc.o test/svc_end_to_end_test.cc.o test/svc_test.cc.o test/test_libvpx.cc.o test/test_vector_test.cc.o test/test_vectors.cc.o test/timestamp_test.cc.o test/user_priv_test.cc.o test/vp8_datarate_test.cc.o test/vp9_datarate_test.cc.o test/vp9_end_to_end_test.cc.o test/vp9_ethread_test.cc.o test/vp9_lossless_test.cc.o test/vp9_motion_vector_test.cc.o test/vp9_skip_loopfilter_test.cc.o test/y4m_test.cc.o third_party/libwebm/mkvparser/mkvparser.cc.o third_party/libwebm/mkvparser/mkvreader.cc.o webmdec.cc.o y4menc.c.o y4minput.c.o -L. -lvpx -lgtest -lpthread -lm -lpthread ln -sf libvpx.so.6.3.0 vpx-vp8-vp9-x86_64-linux-v1.9.0/lib/libvpx.so.6 /usr/bin/ld: /tmp/ccsyaUhJ.ltrans0.ltrans.o:(.debug_info+0x1586f): undefined reference to `gtest_all.cc.5c9bdf8f' /usr/bin/ld: /tmp/ccsyaUhJ.ltrans0.ltrans.o:(.debug_info+0x158a5): undefined reference to `gtest_all.cc.5c9bdf8f' /usr/bin/ld: /tmp/ccsyaUhJ.ltrans0.ltrans.o:(.debug_info+0x158b2): undefined reference to `gtest_all.cc.5c9bdf8f' /usr/bin/ld: /tmp/ccsyaUhJ.ltrans0.ltrans.o:(.debug_info+0x158b7): undefined reference to `gtest_all.cc.5c9bdf8f' /usr/bin/ld: /tmp/ccsyaUhJ.ltrans0.ltrans.o:(.debug_info+0x158dd): undefined reference to `gtest_all.cc.5c9bdf8f' /usr/bin/ld: /tmp/ccsyaUhJ.ltrans0.ltrans.o:(.debug_info+0x15903): more undefined references to `gtest_all.cc.5c9bdf8f' follow collect2: error: ld returned 1 exit status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvpx/+bug/1939640/+subscriptions -- Mailing list: https://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 1939866] [NEW] Firefox crashes during use
Public bug reported: Using Firefox on Xubuntu 21.04 without Swap on 16GB 4-core i5 4570 HP 600 G1 with HD4600 integrated Intel graphics, while much windows on the main DP to HDMI screen and a youtube video window on another VGA screen. Firefox updated today to a newer version from Ubuntu rpeositories, so it may be connected. Firefox just crashed and didn't try returning back. If any additional info is needed, feel free to ask. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: firefox 91.0+build2-0ubuntu0.21.04.1 ProcVersionSignature: Ubuntu 5.11.0-25.27-generic 5.11.22 Uname: Linux 5.11.0-25-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair AddonCompatCheckDisabled: False ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC3: sima2 27340 F pulseaudio /dev/snd/controlC1: sima2 27340 F pulseaudio /dev/snd/controlC2: sima2 27340 F pulseaudio /dev/snd/controlC0: sima2 27340 F pulseaudio BuildID: 20210804193234 CasperMD5CheckResult: unknown Channel: Unavailable CurrentDesktop: XFCE Date: Fri Aug 13 10:56:09 2021 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:352 DefaultProfileThemes: extensions.sqlite corrupt or missing ForcedLayersAccel: False IfupdownConfig: # ifupdown has been replaced by netplan(5) on this system. See # /etc/netplan for current configuration. # To re-enable ifupdown on this system, you can run: #sudo apt install ifupdown IpRoute: default via 10.42.1.1 dev enp2s0 proto dhcp metric 100 10.42.1.0/24 dev enp2s0 proto kernel scope link src 10.42.1.150 metric 100 169.254.0.0/16 dev virbr0 scope link metric 1000 linkdown 192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1 linkdown Profile0Extensions: extensions.sqlite corrupt or missing Profile0IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) Profile0Locales: extensions.sqlite corrupt or missing Profile0PrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/firefox/omni.ja:greprefs.js:352 Profile0PrefSources: prefs.js Profile0Themes: 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:352 Profile2PrefSources: prefs.js Profile2Themes: extensions.sqlite corrupt or missing Profiles: Profile1 (Default) - LastVersion=None/None (Out of date) Profile0 - LastVersion=91.0/20210804193234 (In use) Profile2 - LastVersion=91.0/20210729185755 (Out of date) RunningIncompatibleAddons: False SourcePackage: firefox UpgradeStatus: Upgraded to hirsute on 2021-05-27 (78 days ago) dmi.bios.date: 02/20/2020 dmi.bios.release: 2.78 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: L01 v02.78 dmi.board.asset.tag: CZC3324SQ4 dmi.board.name: 18E7 dmi.board.vendor: Hewlett-Packard dmi.chassis.asset.tag: CZC3324SQ4 dmi.chassis.type: 6 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvrL01v02.78:bd02/20/2020:br2.78:svnHewlett-Packard:pnHPProDesk600G1TWR:pvr:rvnHewlett-Packard:rn18E7:rvr:cvnHewlett-Packard:ct6:cvr: dmi.product.family: 103C_53307F G=D dmi.product.name: HP ProDesk 600 G1 TWR dmi.product.sku: H5U20ET#ABD dmi.sys.vendor: Hewlett-Packard ** Affects: firefox (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug hirsute -- 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/1939866 Title: Firefox crashes during use Status in firefox package in Ubuntu: New Bug description: Using Firefox on Xubuntu 21.04 without Swap on 16GB 4-core i5 4570 HP 600 G1 with HD4600 integrated Intel graphics, while much windows on the main DP to HDMI screen and a youtube video window on another VGA screen. Firefox updated today to a newer version from Ubuntu rpeositories, so it may be connected. Firefox just crashed and didn't try returning back. If any additional info is needed, feel free to ask. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: firefox 91.0+build2-0ubuntu0.21.04.1 ProcVersionSignature: Ubuntu 5.11.0-25.27-generic 5.11.22 Uname: Linux 5.11.0-25-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair AddonCompatCheckDisabled: False ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64
[Desktop-packages] [Bug 1939858] Re: Bluetooth not working
** Package changed: ubuntu => alsa-driver (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1939858 Title: Bluetooth not working Status in alsa-driver package in Ubuntu: New Bug description: Bluetooth was working but not connecting to speaker but said it was connected. Then today bluetooth not working at all. Description: Ubuntu 20.04.2 LTS Release: 20.04 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.11.0-25.27~20.04.1-generic 5.11.22 Uname: Linux 5.11.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jim1526 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Aug 13 00:51:32 2021 InstallationDate: Installed on 2020-05-25 (444 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Title: Bluetooth sound card not detected UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/03/2019 dmi.bios.release: 5.13 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X712FA.308 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X712FA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrX712FA.308:bd06/03/2019:br5.13:svnASUSTeKCOMPUTERINC.:pnVivoBook_ASUSLaptopX712FA_X712FA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX712FA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: VivoBook dmi.product.name: VivoBook_ASUSLaptop X712FA_X712FA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1939858/+subscriptions -- Mailing list: https://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 1939858] [NEW] Bluetooth not working
You have been subscribed to a public bug: Bluetooth was working but not connecting to speaker but said it was connected. Then today bluetooth not working at all. Description:Ubuntu 20.04.2 LTS Release:20.04 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.11.0-25.27~20.04.1-generic 5.11.22 Uname: Linux 5.11.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jim1526 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Aug 13 00:51:32 2021 InstallationDate: Installed on 2020-05-25 (444 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Title: Bluetooth sound card not detected UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/03/2019 dmi.bios.release: 5.13 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X712FA.308 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X712FA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrX712FA.308:bd06/03/2019:br5.13:svnASUSTeKCOMPUTERINC.:pnVivoBook_ASUSLaptopX712FA_X712FA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX712FA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: VivoBook dmi.product.name: VivoBook_ASUSLaptop X712FA_X712FA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- Bluetooth not working https://bugs.launchpad.net/bugs/1939858 You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. -- Mailing list: https://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 1778983] Re: Resume from suspend on Wayland breaks window positioning
Bug 1927948 is tracking that one. -- 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/1778983 Title: Resume from suspend on Wayland breaks window positioning Status in Mutter: Unknown Status in mutter package in Ubuntu: Confirmed Status in mutter package in Fedora: Unknown Bug description: While on the Xorg session things seem to be mostly correct on Wayland after resume from suspend several things are broken: 1) The session resumes on the 4th virtual desktop independently on where it was before 2) The fullscreen virtualbox session I keep in the fourth desktop now has broken dimensions not covering the whole screen and/or being offset from the screen (a gap on the top showing the background and a covered part at the bottom of the screen) 3) In what may be the same bug the terminal and gedit windows I keep tiled to the right and left of virtual desktop 2 show up with wrong sizes. To fix 2) and 3) I have to do the same thing, take the windows out of tiling/fullscreen and go back, so somewhere the actual state of the windows was lost. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.28.1-0ubuntu2 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Uname: Linux 4.15.0-22-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Jun 27 20:14:45 2018 DisplayManager: gdm3 InstallationDate: Installed on 2018-05-31 (27 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1778983/+subscriptions -- Mailing list: https://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 1939848] Re: 'Synaptics Touchpad' incorrectly detected as PS/2 Generic Mouse in 'Alienware X17 R1' and doesn't work in Pop!_OS 20.04 with all kernels, including latest one 5.13
** Also affects: xserver-xorg-input-libinput (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-input-synaptics in Ubuntu. https://bugs.launchpad.net/bugs/1939848 Title: 'Synaptics Touchpad' incorrectly detected as PS/2 Generic Mouse in 'Alienware X17 R1' and doesn't work in Pop!_OS 20.04 with all kernels, including latest one 5.13.9 . Status in xserver-xorg-input-libinput package in Ubuntu: New Status in xserver-xorg-input-synaptics package in Ubuntu: New Bug description: Installed Pop!_OS 20.04 on my new Alienware X17 R1. The touchpad is detected and can be seen in the xinput as PS/2 Generic Mouse. I upgraded the kernel to see if it would be detected as a touchpad but it still does not. It doesn't work at all no matter what kernel is used. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-libinput/+bug/1939848/+subscriptions -- Mailing list: https://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 1778983] Re: Resume from suspend on Wayland breaks window positioning
See also: https://gitlab.gnome.org/GNOME/mutter/-/issues/1419 ** Bug watch added: gitlab.gnome.org/GNOME/mutter/-/issues #1419 https://gitlab.gnome.org/GNOME/mutter/-/issues/1419 -- 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/1778983 Title: Resume from suspend on Wayland breaks window positioning Status in Mutter: Unknown Status in mutter package in Ubuntu: Confirmed Status in mutter package in Fedora: Unknown Bug description: While on the Xorg session things seem to be mostly correct on Wayland after resume from suspend several things are broken: 1) The session resumes on the 4th virtual desktop independently on where it was before 2) The fullscreen virtualbox session I keep in the fourth desktop now has broken dimensions not covering the whole screen and/or being offset from the screen (a gap on the top showing the background and a covered part at the bottom of the screen) 3) In what may be the same bug the terminal and gedit windows I keep tiled to the right and left of virtual desktop 2 show up with wrong sizes. To fix 2) and 3) I have to do the same thing, take the windows out of tiling/fullscreen and go back, so somewhere the actual state of the windows was lost. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.28.1-0ubuntu2 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Uname: Linux 4.15.0-22-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Jun 27 20:14:45 2018 DisplayManager: gdm3 InstallationDate: Installed on 2018-05-31 (27 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1778983/+subscriptions -- Mailing list: https://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 1295267] Re: Windows change Monitor/Desktop after screen lock
Upstream gnome-shell bug link also moved to bug 1927948. ** Also affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** No longer affects: gnome-shell (Ubuntu) ** Project changed: gnome-shell => ubuntu ** Changed in: ubuntu Importance: Unknown => Undecided ** Changed in: ubuntu Status: Unknown => New ** Changed in: ubuntu Remote watch: gitlab.gnome.org/GNOME/gnome-shell/-/issues #2092 => None ** No longer affects: ubuntu -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1295267 Title: Windows change Monitor/Desktop after screen lock Status in Unity: Fix Released Status in Unity 7.1 series: Fix Released Status in compiz-plugins-main package in Ubuntu: Fix Released Status in unity package in Ubuntu: Triaged Bug description: I run a dual monitor configuration, with one portrait and one landscape. I nearly always have multiple applications open in multiple windows across both monitors and all virtual desktops. When I lock the screen and then unlock, my application windows will move from their original position. Sometimes they are in completely random positions; Other times they seem to get the monitors confused, and rather than being in the top half of the portrait monitor they are on the top half of the landscape monitor; Sometimes it is only a new desktop, but the monitor position is the same; Sometimes it is the same desktop, but on the other monitor. Description: Ubuntu 13.10 Release: 13.10 What I expect to happen: When I unlock my computer, all the windows are in the same position on the same monitor and desktop as I left them. What actually happens: When I unlock my computer, some or all of the windows have been changed to a random position on a random monitor and/or desktop. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1295267/+subscriptions -- Mailing list: https://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 1927948] Re: Windows switch monitor after resuming from sleep
** Also affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Changed in: gnome-shell (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1927948 Title: Windows switch monitor after resuming from sleep Status in GNOME Shell: Unknown Status in Mutter: Unknown Status in gnome-shell package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Bug description: What I expect: Window layout/positioning is identical after resume from sleep. What I observe: After resume from sleep, windows appear on a different monitor than before. I found this possibly relevant GNOME bug: https://gitlab.gnome.org/GNOME/mutter/-/issues/1419 ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: mutter 3.38.4-1ubuntu2 ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 Uname: Linux 5.11.0-16-generic x86_64 ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Mon May 10 13:40:28 2021 InstallationDate: Installed on 2019-12-02 (524 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) SourcePackage: mutter UpgradeStatus: Upgraded to hirsute on 2021-05-05 (4 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1927948/+subscriptions -- Mailing list: https://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 1778983] Re: Resume from suspend on Wayland breaks window positioning
** Description changed: - https://gitlab.gnome.org/GNOME/gnome-shell/issues/380 - - --- - While on the Xorg session things seem to be mostly correct on Wayland after resume from suspend several things are broken: 1) The session resumes on the 4th virtual desktop independently on where it was before 2) The fullscreen virtualbox session I keep in the fourth desktop now has broken dimensions not covering the whole screen and/or being offset from the screen (a gap on the top showing the background and a covered part at the bottom of the screen) 3) In what may be the same bug the terminal and gedit windows I keep tiled to the right and left of virtual desktop 2 show up with wrong sizes. To fix 2) and 3) I have to do the same thing, take the windows out of tiling/fullscreen and go back, so somewhere the actual state of the windows was lost. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.28.1-0ubuntu2 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Uname: Linux 4.15.0-22-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Jun 27 20:14:45 2018 DisplayManager: gdm3 InstallationDate: Installed on 2018-05-31 (27 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) -- 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/1778983 Title: Resume from suspend on Wayland breaks window positioning Status in Mutter: Unknown Status in mutter package in Ubuntu: Confirmed Status in mutter package in Fedora: Unknown Bug description: While on the Xorg session things seem to be mostly correct on Wayland after resume from suspend several things are broken: 1) The session resumes on the 4th virtual desktop independently on where it was before 2) The fullscreen virtualbox session I keep in the fourth desktop now has broken dimensions not covering the whole screen and/or being offset from the screen (a gap on the top showing the background and a covered part at the bottom of the screen) 3) In what may be the same bug the terminal and gedit windows I keep tiled to the right and left of virtual desktop 2 show up with wrong sizes. To fix 2) and 3) I have to do the same thing, take the windows out of tiling/fullscreen and go back, so somewhere the actual state of the windows was lost. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.28.1-0ubuntu2 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Uname: Linux 4.15.0-22-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Jun 27 20:14:45 2018 DisplayManager: gdm3 InstallationDate: Installed on 2018-05-31 (27 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1778983/+subscriptions -- Mailing list: https://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 1792822] Re: Dual monitor not working in 18.04(.1) on a dual-radeon-GPU system
** Tags removed: multi-monitor ** Tags added: multimonitor -- 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/1792822 Title: Dual monitor not working in 18.04(.1) on a dual-radeon-GPU system Status in mutter package in Ubuntu: Confirmed Bug description: Dual monitor setup works fine in 16.04 LTS. Not anymore in 18.04(.1). This renders 18.04 useless. Till this is solved will have to stick with 16.04. i.e. this is a pretty critical bug! After a fresh install from DVD first got a freeze on login screen (live CD will run ubuntu though!). This could be solved by switching to lightdm display manager. (Boo! for GDM that cannot even show a login screen without freezing the system) But one issue remains: the dual monitor setup will not work in 18.04. I can see the mouse move to the second monitor. I can drag windows there (and lose sight of them). I can see the mouse cursor change to click a link. But otherwise there is a completely black screen, or dots / colored fields, but nothing even resembling a program. MB: Gigabyte GA-A75M-UD2H Monitor that works fine: ASUS on Radeon HD 6550D monitor that only shows mouse cursor: benq on Radeon HD 4870 (onboard on the gigabyte motherboard) Note: dual monitor setup did not work with other upgrades after 16.04. I hoped this would be solved with the next LTS update. Not so, to great disappointment! Ubuntu really fails if with new major updates it makes systems fall down. This kind of thing should work FLAWLESS out of the box! How would anyone move to Ubuntu when this kind of thing does not work? Windows is a drama, but at least it has the mere basics working! ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3.1 ProcVersionSignature: Ubuntu 4.4.0-135.161-generic 4.4.140 Uname: Linux 4.4.0-135-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Sun Sep 16 23:09:31 2018 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu DkmsStatus: virtualbox, 5.0.40, 4.4.0-133-generic, x86_64: installed virtualbox, 5.0.40, 4.4.0-134-generic, x86_64: installed virtualbox, 5.0.40, 4.4.0-135-generic, x86_64: installed GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] BeaverCreek [Radeon HD 6550D] [1002:9640] (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd BeaverCreek [Radeon HD 6550D] [1458:d000] Advanced Micro Devices, Inc. [AMD/ATI] RV770 [Radeon HD 4870] [1002:9440] (prog-if 00 [VGA controller]) Subsystem: PC Partner Limited / Sapphire Technology RV770 [Radeon HD 4870] [174b:0851] InstallationDate: Installed on 2016-10-02 (714 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: Gigabyte Technology Co., Ltd. GA-A75M-UD2H ProcEnviron: LANGUAGE=nl_NL PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=nl_NL.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-135-generic root=UUID=a5b3b47d-aa17-4b49-ba9a-eeaefc2556d6 ro quiet splash SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/17/2011 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F6c dmi.board.name: GA-A75M-UD2H dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF6c:bd11/17/2011:svnGigabyteTechnologyCo.,Ltd.:pnGA-A75M-UD2H:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-A75M-UD2H:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: GA-A75M-UD2H dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.91-2~16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~16.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.8 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1.2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 xserver.bootTime: Sun Sep 16 19:34:47 2018 xserver.configfile: default xserver.errors: RADEON(G0):
[Desktop-packages] [Bug 1939664] Re: Several potential bugs of memory leak
also, 18.04 doesn't have 1.6.2 but 2:1.6.4-3ubuntu0.4 which has had several CVE fixes already if you're actually looking at version 1.6.2, then your distro is Ubuntu 14.04, which was EOL two years ago. ** Changed in: libx11 (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libx11 in Ubuntu. https://bugs.launchpad.net/bugs/1939664 Title: Several potential bugs of memory leak Status in libx11 package in Ubuntu: Incomplete Bug description: Ubuntu version: 18.04 libx11-xcb-dev version:1.6.2 Hello,I found some potential bugs in package libx11-xcb-dev,and the microsoft word file in the attachment I uploaded shows the occurrence process of the bug in a graphical way.Would you help me check whether the bugs mentioned below are true? I'm not 100% sure that the bugs I submitted is correct. I hope you don't mind seeing the wrong bug I submitted.Thank you very much for your patience. In file libx11-1.6.2/modules/im/ximcp/imLcPrs.c,defination of parsestringfile,line 733. The statement "tbp=malloc(size);"allocate memory to tbp and in line 733,if select false branch at this statement,tbp will not be freed correctly.the process of this potential bug is shown in figure 1. In file libx11-1.6.2/src/xlibi18n/lcDB.c,defination of f_numeric,line 882. The statement "wordp=malloc(len+1);"allocate memory to wordp and in line 883,if select false branch at this statement,function f_numeric will go on to execute.In line 910,if select false branch at this statement,wordp will not be freed correctly.the process of this potential bug is shown in figure 2. In file libx11-1.6.2/src/xlibi18n/lcDB.c,defination of f_numeric,line 882. The statement "wordp=malloc(len+1);"allocate memory to wordp and in line 883,if select false branch at this statement,function f_numeric will go on to execute.and if select true branch in line 938,flow goto err,In line 989,if select false branch here,wordp will not be freed correctly.the process of this potential bug is shown in figure 3. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libx11/+bug/1939664/+subscriptions -- Mailing list: https://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 1939664] Re: Several potential bugs of memory leak
you should file such bugs upstream too, but first check that the current upstream version is affected: https://gitlab.freedesktop.org/xorg/lib/libx11/ -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libx11 in Ubuntu. https://bugs.launchpad.net/bugs/1939664 Title: Several potential bugs of memory leak Status in libx11 package in Ubuntu: Incomplete Bug description: Ubuntu version: 18.04 libx11-xcb-dev version:1.6.2 Hello,I found some potential bugs in package libx11-xcb-dev,and the microsoft word file in the attachment I uploaded shows the occurrence process of the bug in a graphical way.Would you help me check whether the bugs mentioned below are true? I'm not 100% sure that the bugs I submitted is correct. I hope you don't mind seeing the wrong bug I submitted.Thank you very much for your patience. In file libx11-1.6.2/modules/im/ximcp/imLcPrs.c,defination of parsestringfile,line 733. The statement "tbp=malloc(size);"allocate memory to tbp and in line 733,if select false branch at this statement,tbp will not be freed correctly.the process of this potential bug is shown in figure 1. In file libx11-1.6.2/src/xlibi18n/lcDB.c,defination of f_numeric,line 882. The statement "wordp=malloc(len+1);"allocate memory to wordp and in line 883,if select false branch at this statement,function f_numeric will go on to execute.In line 910,if select false branch at this statement,wordp will not be freed correctly.the process of this potential bug is shown in figure 2. In file libx11-1.6.2/src/xlibi18n/lcDB.c,defination of f_numeric,line 882. The statement "wordp=malloc(len+1);"allocate memory to wordp and in line 883,if select false branch at this statement,function f_numeric will go on to execute.and if select true branch in line 938,flow goto err,In line 989,if select false branch here,wordp will not be freed correctly.the process of this potential bug is shown in figure 3. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libx11/+bug/1939664/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp