[Touch-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 Ubuntu Touch seeded 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 :
[Touch-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 Ubuntu Touch seeded 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
[Touch-packages] [Bug 1886790] Re: lxc 3.0.3-0ubuntu1~18.04.1 ADT test failure with B/5.4 kernels (device_add_remove_test)
Observed on bionic:linux-azure-5.4 5.4.0-1056.58~18.04.1 . ** Changed in: lxc (Ubuntu) Status: Fix Released => In Progress -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1886790 Title: lxc 3.0.3-0ubuntu1~18.04.1 ADT test failure with B/5.4 kernels (device_add_remove_test) Status in ubuntu-kernel-tests: New Status in lxc package in Ubuntu: In Progress Status in lxc source package in Bionic: Confirmed Bug description: Testing failed on: amd64: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic/bionic/amd64/l/lxc/20200706_183234_ca65f@/log.gz arm64: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic/bionic/arm64/l/lxc/20200706_172136_71b68@/log.gz ppc64el: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic/bionic/ppc64el/l/lxc/20200706_191938_cedac@/log.gz s390x: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic/bionic/s390x/l/lxc/20200706_163359_98d4d@/log.gz The failing test seems to be: FAIL: lxc-tests: lxc-test-device-add-remove (0s) --- Adding /dev/network_latency to the container (device_add_remove_test) failed... --- This is a regression from the 4.15/5.3 to 5.4 kernels in Bionic. Note that this testcase is successful on Focal with the same kernel version. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1886790/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1309658] Re: apt.conf man page should indicate # is also used for comments
This bug was fixed in the package apt - 2.3.7 --- apt (2.3.7) experimental; urgency=medium [ David Kalnischkies ] * Use full item description in broken repo error * Store size from volatile sources for already installed versions * Restore dpkg::chroot-directory functionality [ Dillon Brock ] * apt.conf(5): indicate # is also used for comments (LP: #1309658) [ Julian Andres Klode ] * Check sources.list could be parsed before adding volatile files (Closes: #990518) * pkgAcqIndex::CommonFailed: Set StatIdle before calling Init() * Implement exponential backoff between retries - acquire: Automatically reduce select() timeout as needed - Properly convert PulseInterval to timeval - Add support for a maximum delay and testing of delay - tests (retry-downloads): Avoid delay in second test -- Julian Andres Klode Thu, 29 Jul 2021 16:59:39 +0200 ** Changed in: apt (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1309658 Title: apt.conf man page should indicate # is also used for comments Status in apt package in Ubuntu: Fix Released Bug description: According to apt.conf(5) man page, the only valid comments in apt config files are: "Lines starting with // are treated as comments (ignored), as well as all text between /* and */, just like C/C++ comments." There are comments in debian/apt.conf.autoremove (/etc/apt/apt.conf.d/01autoremove) that start with '#' which breaks other tools like augeas that follow strictly the definition of comments in apt.conf's man page and rely on it to function properly. 1) Description:Ubuntu 14.04 LTS Release:14.04 2) apt: Installed: 1.0.1ubuntu2 Candidate: 1.0.1ubuntu2 Version table: *** 1.0.1ubuntu2 0 500 http://us.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages 100 /var/lib/dpkg/status The file can be patched by running: $ sed -i "s/#/\/\//" apt.conf.autoremove To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1309658/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1939544] Re: Merge the 1.1.1k version from Debian
** Changed in: openssl (Ubuntu) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssl in Ubuntu. https://bugs.launchpad.net/bugs/1939544 Title: Merge the 1.1.1k version from Debian Status in openssl package in Ubuntu: Fix Committed Bug description: Impish currently ships with a version based on the upstream 1.1.1j, while Debian bullseye/sid has 1.1.1k. Let's merge! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1939544/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1934147] Re: systemd leaks abandoned session scopes
** Changed in: systemd (Ubuntu Impish)
Assignee: Dan Streetman (ddstreet) => Heather Lemon (hypothetical-lemon)
** Changed in: systemd (Ubuntu Hirsute)
Assignee: Dan Streetman (ddstreet) => Heather Lemon (hypothetical-lemon)
** Changed in: systemd (Ubuntu Groovy)
Assignee: Dan Streetman (ddstreet) => (unassigned)
** Changed in: systemd (Ubuntu Focal)
Assignee: Dan Streetman (ddstreet) => Heather Lemon (hypothetical-lemon)
** Changed in: systemd (Ubuntu Bionic)
Assignee: Dan Streetman (ddstreet) => Heather Lemon (hypothetical-lemon)
** Changed in: systemd (Ubuntu Groovy)
Status: In Progress => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1934147
Title:
systemd leaks abandoned session scopes
Status in snapd:
New
Status in systemd:
New
Status in systemd package in Ubuntu:
In Progress
Status in systemd source package in Bionic:
Confirmed
Status in systemd source package in Focal:
In Progress
Status in systemd source package in Groovy:
Won't Fix
Status in systemd source package in Hirsute:
In Progress
Status in systemd source package in Impish:
In Progress
Bug description:
[impact]
systemd may leak sessions, leaving empty cgroups around as well as
abandoned session scopes.
[test case]
on a system where the user has a ssh key that allows noninteractive
login to localhost, and also has noninteractive sudo, run:
$ for i in {1..100}; do sudo -b -i -u ubuntu ssh localhost -- sleep 1;
done; for i in {1..20}; do echo 'Reloading...'; sudo systemctl daemon-
reload; done
check the sessions to see there have been leaked sessions:
$ loginctl list-sessions
SESSION UID USER SEAT TTY
1 1000 ubuntu ttyS0
350 1000 ubuntu
351 1000 ubuntu
360 1000 ubuntu
...
to verify the sessions were leaked, clear them out with:
$ echo '' | sudo tee
/sys/fs/cgroup/unified/user.slice/user-1000.slice/session-*.scope/cgroup.events
that should result in all the leaked sessions being cleaned up.
[regression potential]
issues during systemd pid1 reexec/reload, or issues while cleaning up
sessions, including leaking sessions/cgroups
[scope]
this is needed for all releases
upstream bug linked above, and upstream PR:
https://github.com/systemd/systemd/pull/20199
[original description]
On a system that is monitored via telegraf I found many abandoned
systemd session which I believe are created by a potential race where
systemd is reloading unit files and at the same time a user is
connecting to the system via ssh or is executing the su command.
The simple reproducer
$ for i in {1..100}; do sleep 0.2; ssh localhost sudo systemctl
daemon-reload & ssh localhost sleep 1 & done
Wait > 1 second
$ jobs -p | xargs --verbose --no-run-if-empty kill -KILL
To clean out STOPPED jobs and
$ systemctl status --all 2> /dev/null | grep --before-context 3
abandoned
will produce something similar to
│ ├─ 175 su - ubuntu
│ ├─ 178 -su
│ ├─62375 systemctl status --all
│ └─62376 grep --color=auto --before-context 3 abandoned
--
● session-273.scope - Session 273 of user ubuntu
Loaded: loaded (/run/systemd/transient/session-273.scope; transient)
Transient: yes
Active: active (abandoned) since Wed 2021-06-30 13:32:03 UTC; 4min 7s ago
--
● session-274.scope - Session 274 of user ubuntu
Loaded: loaded (/run/systemd/transient/session-274.scope; transient)
Transient: yes
Active: active (abandoned) since Wed 2021-06-30 13:32:03 UTC; 4min 7s ago
--
● session-30.scope - Session 30 of user ubuntu
Loaded: loaded (/run/systemd/transient/session-30.scope; transient)
Transient: yes
Active: active (abandoned) since Wed 2021-06-30 10:05:56 UTC; 3h 30min ago
--
● session-302.scope - Session 302 of user ubuntu
Loaded: loaded (/run/systemd/transient/session-302.scope; transient)
Transient: yes
Active: active (abandoned) since Wed 2021-06-30 13:32:04 UTC; 4min 6s ago
--
│ ├─ 175 su - ubuntu
│ ├─ 178 -su
│ ├─62375 systemctl status --all
│ └─62376 grep --color=auto --before-context 3 abandoned
The system in question is running Bionic, systemd-237-3ubuntu10.48
To manage notifications about this bug go to:
https://bugs.launchpad.net/snapd/+bug/1934147/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1939861] Re: dpdk: ppc64el autopkgtest regressed in release
The hint has been merged. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to util-linux in Ubuntu. https://bugs.launchpad.net/bugs/1939861 Title: dpdk: ppc64el autopkgtest regressed in release Status in dpdk package in Ubuntu: Triaged Status in glibc package in Ubuntu: New Status in pexpect package in Ubuntu: New Status in util-linux package in Ubuntu: New Status in zlib package in Ubuntu: New Bug description: dpkg's autopkgtest on ppc64el has regressed in release [1]. This currently blocks pexpect/8.0-2ubuntu1 from migrating to -release. [1] https://autopkgtest.ubuntu.com/packages/dpdk/impish/ppc64el To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dpdk/+bug/1939861/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-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 Ubuntu Touch seeded 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/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
Re: [Touch-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 Ubuntu Touch seeded 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/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-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 Ubuntu Touch seeded 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/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-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 Ubuntu Touch seeded 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/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-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 Ubuntu Touch seeded 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/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-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 Ubuntu Touch seeded 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/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-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 Ubuntu Touch seeded 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/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-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 attem
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 Ubuntu Touch seeded 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/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-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 Ubuntu Touch seeded 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/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-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 Ubuntu Touch seeded 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/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-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 Ubuntu Touch seeded packages, which is subscribed to mesa 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
[Touch-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 Ubuntu Touch seeded 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
[Touch-packages] [Bug 1939664] Re: Several potential bugs of memory leak
ok.thank you. -- You received this bug notification because you are a member of Ubuntu Touch seeded 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/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-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 Ubuntu Touch seeded 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/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-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 Ubuntu Touch seeded 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/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-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 Ubuntu Touch seeded 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/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1939861] Re: dpdk: ppc64el autopkgtest regressed in release
** Also affects: glibc (Ubuntu) Importance: Undecided Status: New ** Also affects: util-linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to zlib in Ubuntu. https://bugs.launchpad.net/bugs/1939861 Title: dpdk: ppc64el autopkgtest regressed in release Status in dpdk package in Ubuntu: Triaged Status in glibc package in Ubuntu: New Status in pexpect package in Ubuntu: New Status in util-linux package in Ubuntu: New Status in zlib package in Ubuntu: New Bug description: dpkg's autopkgtest on ppc64el has regressed in release [1]. This currently blocks pexpect/8.0-2ubuntu1 from migrating to -release. [1] https://autopkgtest.ubuntu.com/packages/dpdk/impish/ppc64el To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dpdk/+bug/1939861/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1939861] Re: dpdk: ppc64el autopkgtest regressed in release
Will do! In the meantime, I submitted a MP to hint the autopkgtest failure: https://code.launchpad.net/~ginggs/britney/+git/hints- ubuntu/+merge/407058 ** Also affects: zlib (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to zlib in Ubuntu. https://bugs.launchpad.net/bugs/1939861 Title: dpdk: ppc64el autopkgtest regressed in release Status in dpdk package in Ubuntu: Triaged Status in pexpect package in Ubuntu: New Status in zlib package in Ubuntu: New Bug description: dpkg's autopkgtest on ppc64el has regressed in release [1]. This currently blocks pexpect/8.0-2ubuntu1 from migrating to -release. [1] https://autopkgtest.ubuntu.com/packages/dpdk/impish/ppc64el To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dpdk/+bug/1939861/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1939413] Re: /usr/lib/aarch64-linux-gnu/libprotobuf.a’ generated with LTO version 9.2 instead of the expected 11.0
** Changed in: protobuf (Ubuntu) Status: Fix Committed => New ** Changed in: protobuf (Ubuntu) Assignee: Gunnar Hjalmarsson (gunnarhj) => Matthias Klose (doko) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to protobuf in Ubuntu. https://bugs.launchpad.net/bugs/1939413 Title: /usr/lib/aarch64-linux-gnu/libprotobuf.a’ generated with LTO version 9.2 instead of the expected 11.0 Status in mozc package in Ubuntu: Invalid Status in protobuf package in Ubuntu: New Bug description: When trying to build package mozc for arm64 the following error popped up: lto1: fatal error: bytecode stream in file ‘/usr/lib/aarch64-linux- gnu/libprotobuf.a’ generated with LTO version 9.2 instead of the expected 11.0 Why does the library contain LTO information at all? Best regards Heinrich To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mozc/+bug/1939413/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1939858] Re: Bluetooth not working
** Package changed: ubuntu => alsa-driver (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded 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/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-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 Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1939409] Re: merge e2fsprogs 1.46.3-1 from Debian: s390x fails in test f_baddotdir
e2fsprogs - 1.46.3-1ubuntu2 is available in ppa:xypron/merge-from-debian -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to e2fsprogs in Ubuntu. https://bugs.launchpad.net/bugs/1939409 Title: merge e2fsprogs 1.46.3-1 from Debian: s390x fails in test f_baddotdir Status in e2fsprogs package in Ubuntu: New Bug description: e2fsprogs 1.46.3-1ubuntu1 is in proposed. Architecture s390x fail in test f_baddotdir. The test image was changed with the new release. Next step should be analyzing the error on a s390x virtual machine. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/e2fsprogs/+bug/1939409/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1939409] Re: merge e2fsprogs 1.46.3-1 from Debian: s390x fails in test f_baddotdir
** Patch added: "e2fsprogs_1.46.3-1ubuntu2.debdiff" https://bugs.launchpad.net/ubuntu/+source/e2fsprogs/+bug/1939409/+attachment/5517712/+files/e2fsprogs_1.46.3-1ubuntu2.debdiff -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to e2fsprogs in Ubuntu. https://bugs.launchpad.net/bugs/1939409 Title: merge e2fsprogs 1.46.3-1 from Debian: s390x fails in test f_baddotdir Status in e2fsprogs package in Ubuntu: New Bug description: e2fsprogs 1.46.3-1ubuntu1 is in proposed. Architecture s390x fail in test f_baddotdir. The test image was changed with the new release. Next step should be analyzing the error on a s390x virtual machine. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/e2fsprogs/+bug/1939409/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1939857] [NEW] package openssh-server 1:7.6p1-4ubuntu0.5 failed to install/upgrade: installed openssh-server package post-installation script subprocess returned error exit statu
Public bug reported: ¯\_(ツ)_/¯ ProblemType: Package DistroRelease: Ubuntu 18.04 Package: openssh-server 1:7.6p1-4ubuntu0.5 ProcVersionSignature: Ubuntu 4.15.0-147.151-generic 4.15.18 Uname: Linux 4.15.0-147-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.24 Architecture: amd64 Date: Fri Aug 13 08:12:44 2021 ErrorMessage: installed openssh-server package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2014-05-30 (2631 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) Python3Details: /usr/bin/python3.6, Python 3.6.9, python3-minimal, 3.6.7-1~18.04 PythonDetails: /usr/bin/python2.7, Python 2.7.17, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2.3 apt 1.6.14 SourcePackage: openssh Title: package openssh-server 1:7.6p1-4ubuntu0.5 failed to install/upgrade: installed openssh-server package post-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to bionic on 2019-01-28 (927 days ago) ** Affects: openssh (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package bionic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/1939857 Title: package openssh-server 1:7.6p1-4ubuntu0.5 failed to install/upgrade: installed openssh-server package post-installation script subprocess returned error exit status 1 Status in openssh package in Ubuntu: New Bug description: ¯\_(ツ)_/¯ ProblemType: Package DistroRelease: Ubuntu 18.04 Package: openssh-server 1:7.6p1-4ubuntu0.5 ProcVersionSignature: Ubuntu 4.15.0-147.151-generic 4.15.18 Uname: Linux 4.15.0-147-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.24 Architecture: amd64 Date: Fri Aug 13 08:12:44 2021 ErrorMessage: installed openssh-server package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2014-05-30 (2631 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) Python3Details: /usr/bin/python3.6, Python 3.6.9, python3-minimal, 3.6.7-1~18.04 PythonDetails: /usr/bin/python2.7, Python 2.7.17, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2.3 apt 1.6.14 SourcePackage: openssh Title: package openssh-server 1:7.6p1-4ubuntu0.5 failed to install/upgrade: installed openssh-server package post-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to bionic on 2019-01-28 (927 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1939857/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-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 Ubuntu Touch seeded 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/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-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 Ubuntu Touch seeded 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/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
