[Touch-packages] [Bug 1866347] Re: /usr/share/apport/whoopsie-upload-all:AssertionError:/usr/share/apport/whoopsie-upload-all@168:collect_info:process_report:add_gdb_info:crash_signature_addresses:_ad
This bug was fixed in the package apport - 2.20.11-0ubuntu19 --- apport (2.20.11-0ubuntu19) focal; urgency=medium * apport/report.py: do not return a duplicate signature when we are unable to access ProcMaps as that is necessary to create one. (LP: #1866347) * apport/ui.py: Always allow users to use ubuntu-bug or apport-collect regardless of the Problem Reporting setting as they are manually invoked and not automatically generated like a crash report. (LP: #1814611) -- Brian Murray Mon, 09 Mar 2020 15:18:42 -0700 ** Changed in: apport (Ubuntu) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1866347 Title: /usr/share/apport/whoopsie-upload-all:AssertionError:/usr/share/apport /whoopsie-upload- all@168:collect_info:process_report:add_gdb_info:crash_signature_addresses:_address_to_offset:_build_proc_maps_cache Status in apport package in Ubuntu: Fix Released Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding apport. This problem was most recently seen with package version 2.20.11-0ubuntu17, the problem page at https://errors.ubuntu.com/problem/5cc81a1cde2a921ad2adcc00e2f8d13f2c9f76e8 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1866347/+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 1814611] Re: turning off "Send error reports to Canonical" prevents using ubuntu-bug
This bug was fixed in the package apport - 2.20.11-0ubuntu19 --- apport (2.20.11-0ubuntu19) focal; urgency=medium * apport/report.py: do not return a duplicate signature when we are unable to access ProcMaps as that is necessary to create one. (LP: #1866347) * apport/ui.py: Always allow users to use ubuntu-bug or apport-collect regardless of the Problem Reporting setting as they are manually invoked and not automatically generated like a crash report. (LP: #1814611) -- Brian Murray Mon, 09 Mar 2020 15:18:42 -0700 ** Changed in: apport (Ubuntu) Status: Triaged => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1814611 Title: turning off "Send error reports to Canonical" prevents using ubuntu- bug Status in apport package in Ubuntu: Fix Released Status in apport source package in Bionic: Triaged Status in apport source package in Disco: Triaged Status in apport source package in Eoan: Triaged Bug description: Impact -- apport was modified (bug 1778497) to reduce the number of times people have to respond to crash reports, however the changes introduced a check to see if whoopsie is enabled. That check is done for any type of report, not just crashes, and subsequently people can not use ubuntu-bug to report bugs if whoopsie is disabled which is wrong as whoopsie is only for uploading crashes to the Error Tracker. Test Case - 1) On a system with Gnome installed use the Privacy control panel and set "Send error reports to Canonical" to Off 2) In a terminal run 'ubuntu-bug gnome-terminal' 3) Click "Send" and observe nothing happening (if something does happen confirm that whoopsie is disabled via 'systemctl is-enabled whoopsie' - there may be a bug in the control panel) Original Description Ubuntu 18.04.1 LTS, X11 gnome session. For some reason ubuntu-bug no longer opens a browser window, so it is not possible to enter useful bug detauls, or even know the bug number. After prompting whether or not to Send the report, clicking "Send" just closes appport and nothing else ever happens. The exit status of "ubuntu-bug" is zero. This worked fine before, but it has been many months since I tried to submit a bug. strace shows many stat calls on plausible browser paths, including the one that is correct (/usr/bin/firefox, which returned a successful stat call). I'll attach the trace output from strace -f -o /tmp/strace.log ubuntu-bug apport To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1814611/+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 1780316] Re: netcat-openbsd is in main but netcat-standard has a netcat dummy package
This bug was fixed in the package netcat-openbsd - 1.206-1ubuntu1 --- netcat-openbsd (1.206-1ubuntu1) focal; urgency=medium * Move the netcat transitional package here and have it depend on the preferred netcat-openbsd implementation of netcat, not netcat-traditional. LP: #1780316. -- Steve Langasek Mon, 09 Mar 2020 11:50:15 -0700 ** Changed in: netcat-openbsd (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 netcat-openbsd in Ubuntu. https://bugs.launchpad.net/bugs/1780316 Title: netcat-openbsd is in main but netcat-standard has a netcat dummy package Status in netcat package in Ubuntu: Fix Released Status in netcat-openbsd package in Ubuntu: Fix Released Bug description: For installations that don't have netcat-openbsd somewhere in the seed then any package/user that installs 'netcat' will get 'netcat- standard' from universe rather than 'netcat-openbsd' from main. (One example is the ubuntu-fan package that recommends netcat) Installing the 'netcat' transitional package should provide users a supported package as one exists. Suggested action: * Remove the 'netcat' dummy package from the netcat-standard package * Add a 'netcat' dummy package to the netcat-openbsd package To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/netcat/+bug/1780316/+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 1859754] Re: add ucm to make alsa/sof driver work under PA (variants of Lenovo X1 Carbon 7th, Dell cnl and cml machines)
Install the 19.10 (Eoan) on a Lenovo X1C7 (the machine type dmi string is LENOVO-MFG_GO_ThinkPad-MFG_IN_GO). Enable Pre-released updates (eoan-proposed) in the Software & Updates sudo apt-get update sudo apt install linux-image-5.3.0-40-generic linux-modules-extra-5.3.0-42-generic sudo apt linux-firmware (1.183.4) sudo apt install libasound2 (1.1.9-0ubuntu1.2) blacklist snd_soc_skl and snd_hda_intel in the /etc/modprobe.d/blacklist.conf (after linux-image-5.3.0-43-generic is ready, the blacklist is not needed anymore) reboot open the gnome-sound-setting, we can see speaker from output device and Digital Microphone from input device. I can play sound to speaker and record sound from Microphone. Plug a headset, I can see headphone and headset mic. They all work well and the recording volume is fine too. Plug a hdmi monitor with audio capability, I can see the hdmi audio in the UI, then I can play sound via hdmi monitor. Verified done on Eoan (19.10) ** Tags removed: verification-needed verification-needed-eoan ** Tags added: verification-done verification-done-eoan -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-lib in Ubuntu. https://bugs.launchpad.net/bugs/1859754 Title: add ucm to make alsa/sof driver work under PA (variants of Lenovo X1 Carbon 7th, Dell cnl and cml machines) Status in HWE Next: New Status in alsa-lib package in Ubuntu: Fix Committed Status in alsa-lib source package in Bionic: Fix Committed Status in alsa-lib source package in Eoan: Fix Committed Bug description: This ucm is only for Eoan and Bionic, for focal and future versions, we plan to integrate the ucm2 instead of this ucm, and the ucm2 depends on the alsa-lib-1.2.1 and pluseaudio-v14, the ucm2 is under developing by the community, is not ready yet. [Impact] In the oem project, we have a couple of Lenovo and Dell machines which connect the digital mic to PCH directly, this design needs the new sound driver soc/sof, and this driver can't work under pulseaudio automatically, we need to integrate the ucm for the driver, then the sof dirver could work under pulseaudio and gnome. This ucm is maintained by intel audio team, and it is not upstreamed and will not be upstreamed, since the community is developing the ucm2 which is based on at least alsa-lib-1.2.1 and pulseaudio-v14.0 (still under developing), for bionic and eoan, we have to integrate this ucm since the alsa-lib version is too low. For focal and future version, we are going to integrate the ucm2 after the ucm2 is ready. This ucm is already verified in the oem project, now it is time to put it into the stock ubuntu. [Fix] These ucm files are backported from sof_ucm1 branch of https://github.com/thesofproject/alsa-ucm-conf.git [Test Case] Boot the eoan kernel or oem-osp1-bionic kernel, then check the log of pulseaudio, the ucm files are loaded successfully, then check the gnome-sound-setting, both output and input devices work well. [Regression Risk] Low, just add some new ucm files, and this will not affect other machines, and those new added ucm files are only used by specific machines which enable the sof driver. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1859754/+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 1859754] Re: add ucm to make alsa/sof driver work under PA (variants of Lenovo X1 Carbon 7th, Dell cnl and cml machines)
On a Dell Vostro-5390, install the 18.04 (bionic). Then enable the Pre-released updates (bionic-proposed) in the Software & Updates. sudo apt-get update sudo apt install linux-firmware (1.173.16) sudo apt install linux-image-5.0.0-1042-oem-osp1 (for ubuntu 5.0 kernel, only oem-osp1 supports sof driver). sudo apt install libasound2 (1.1.3-5ubuntu0.4) reboot open the gnome-sound-setting, we can see speaker from output device and Digital Microphone from input device. I can play sound to speaker and record sound from Microphone. Plug a headset, I can see headphone, headset mic and headphone mic. They all work well and the recording volume is fine too. Plug a hdmi monitor with audio capability, I can see the hdmi audio in the UI, then I can play sound via hdmi monitor. Verified done on bionic (18.04). ** Tags removed: verification-needed-bionic ** Tags added: verification-done-bionic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-lib in Ubuntu. https://bugs.launchpad.net/bugs/1859754 Title: add ucm to make alsa/sof driver work under PA (variants of Lenovo X1 Carbon 7th, Dell cnl and cml machines) Status in HWE Next: New Status in alsa-lib package in Ubuntu: Fix Committed Status in alsa-lib source package in Bionic: Fix Committed Status in alsa-lib source package in Eoan: Fix Committed Bug description: This ucm is only for Eoan and Bionic, for focal and future versions, we plan to integrate the ucm2 instead of this ucm, and the ucm2 depends on the alsa-lib-1.2.1 and pluseaudio-v14, the ucm2 is under developing by the community, is not ready yet. [Impact] In the oem project, we have a couple of Lenovo and Dell machines which connect the digital mic to PCH directly, this design needs the new sound driver soc/sof, and this driver can't work under pulseaudio automatically, we need to integrate the ucm for the driver, then the sof dirver could work under pulseaudio and gnome. This ucm is maintained by intel audio team, and it is not upstreamed and will not be upstreamed, since the community is developing the ucm2 which is based on at least alsa-lib-1.2.1 and pulseaudio-v14.0 (still under developing), for bionic and eoan, we have to integrate this ucm since the alsa-lib version is too low. For focal and future version, we are going to integrate the ucm2 after the ucm2 is ready. This ucm is already verified in the oem project, now it is time to put it into the stock ubuntu. [Fix] These ucm files are backported from sof_ucm1 branch of https://github.com/thesofproject/alsa-ucm-conf.git [Test Case] Boot the eoan kernel or oem-osp1-bionic kernel, then check the log of pulseaudio, the ucm files are loaded successfully, then check the gnome-sound-setting, both output and input devices work well. [Regression Risk] Low, just add some new ucm files, and this will not affect other machines, and those new added ucm files are only used by specific machines which enable the sof driver. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1859754/+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 1859754] Re: add ucm to make alsa/sof driver work under PA (variants of Lenovo X1 Carbon 7th, Dell cnl and cml machines)
On a Dell -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-lib in Ubuntu. https://bugs.launchpad.net/bugs/1859754 Title: add ucm to make alsa/sof driver work under PA (variants of Lenovo X1 Carbon 7th, Dell cnl and cml machines) Status in HWE Next: New Status in alsa-lib package in Ubuntu: Fix Committed Status in alsa-lib source package in Bionic: Fix Committed Status in alsa-lib source package in Eoan: Fix Committed Bug description: This ucm is only for Eoan and Bionic, for focal and future versions, we plan to integrate the ucm2 instead of this ucm, and the ucm2 depends on the alsa-lib-1.2.1 and pluseaudio-v14, the ucm2 is under developing by the community, is not ready yet. [Impact] In the oem project, we have a couple of Lenovo and Dell machines which connect the digital mic to PCH directly, this design needs the new sound driver soc/sof, and this driver can't work under pulseaudio automatically, we need to integrate the ucm for the driver, then the sof dirver could work under pulseaudio and gnome. This ucm is maintained by intel audio team, and it is not upstreamed and will not be upstreamed, since the community is developing the ucm2 which is based on at least alsa-lib-1.2.1 and pulseaudio-v14.0 (still under developing), for bionic and eoan, we have to integrate this ucm since the alsa-lib version is too low. For focal and future version, we are going to integrate the ucm2 after the ucm2 is ready. This ucm is already verified in the oem project, now it is time to put it into the stock ubuntu. [Fix] These ucm files are backported from sof_ucm1 branch of https://github.com/thesofproject/alsa-ucm-conf.git [Test Case] Boot the eoan kernel or oem-osp1-bionic kernel, then check the log of pulseaudio, the ucm files are loaded successfully, then check the gnome-sound-setting, both output and input devices work well. [Regression Risk] Low, just add some new ucm files, and this will not affect other machines, and those new added ucm files are only used by specific machines which enable the sof driver. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1859754/+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 1780316] Re: netcat-openbsd is in main but netcat-standard has a netcat dummy package
This bug was fixed in the package netcat - 1.10-41.1ubuntu1 --- netcat (1.10-41.1ubuntu1) focal; urgency=medium * Drop the netcat transitional package, moved to netcat-openbsd in Ubuntu. LP: #1780316. -- Steve Langasek Mon, 09 Mar 2020 11:55:57 -0700 ** Changed in: netcat (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 netcat-openbsd in Ubuntu. https://bugs.launchpad.net/bugs/1780316 Title: netcat-openbsd is in main but netcat-standard has a netcat dummy package Status in netcat package in Ubuntu: Fix Released Status in netcat-openbsd package in Ubuntu: Fix Committed Bug description: For installations that don't have netcat-openbsd somewhere in the seed then any package/user that installs 'netcat' will get 'netcat- standard' from universe rather than 'netcat-openbsd' from main. (One example is the ubuntu-fan package that recommends netcat) Installing the 'netcat' transitional package should provide users a supported package as one exists. Suggested action: * Remove the 'netcat' dummy package from the netcat-standard package * Add a 'netcat' dummy package to the netcat-openbsd package To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/netcat/+bug/1780316/+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 1814611] Re: turning off "Send error reports to Canonical" prevents using ubuntu-bug
** Branch linked: lp:~ubuntu-core-dev/ubuntu/focal/apport/ubuntu -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1814611 Title: turning off "Send error reports to Canonical" prevents using ubuntu- bug Status in apport package in Ubuntu: Triaged Status in apport source package in Bionic: Triaged Status in apport source package in Disco: Triaged Status in apport source package in Eoan: Triaged Bug description: Impact -- apport was modified (bug 1778497) to reduce the number of times people have to respond to crash reports, however the changes introduced a check to see if whoopsie is enabled. That check is done for any type of report, not just crashes, and subsequently people can not use ubuntu-bug to report bugs if whoopsie is disabled which is wrong as whoopsie is only for uploading crashes to the Error Tracker. Test Case - 1) On a system with Gnome installed use the Privacy control panel and set "Send error reports to Canonical" to Off 2) In a terminal run 'ubuntu-bug gnome-terminal' 3) Click "Send" and observe nothing happening (if something does happen confirm that whoopsie is disabled via 'systemctl is-enabled whoopsie' - there may be a bug in the control panel) Original Description Ubuntu 18.04.1 LTS, X11 gnome session. For some reason ubuntu-bug no longer opens a browser window, so it is not possible to enter useful bug detauls, or even know the bug number. After prompting whether or not to Send the report, clicking "Send" just closes appport and nothing else ever happens. The exit status of "ubuntu-bug" is zero. This worked fine before, but it has been many months since I tried to submit a bug. strace shows many stat calls on plausible browser paths, including the one that is correct (/usr/bin/firefox, which returned a successful stat call). I'll attach the trace output from strace -f -o /tmp/strace.log ubuntu-bug apport To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1814611/+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 1866712] [NEW] Graphic glitches with Nvidia 440 on Dell XPS 15 9570
Public bug reported: I am experiencing intermittent graphical glitches. I couldn't find where this had been reported before so please excuse the duplicate if this is a known issue. I tried recording my screen to demonstrate what is happening but, although I am seeing the issue on the desktop, it does not show up in the video. I am using prime-select in intel mode. System:Host: rex Kernel: 5.5.7-050507-generic x86_64 bits: 64 Desktop: Gnome 3.35.91 Distro: Ubuntu 20.04 LTS (Focal Fossa) Machine: Type: Laptop System: Dell product: XPS 15 9570 v: N/A serial: Mobo: Dell model: 0D0T05 v: A00 serial: UEFI: Dell v: 1.15.0 date: 12/25/2019 CPU: Topology: 6-Core model: Intel Core i7-8750H bits: 64 type: MT MCP L2 cache: 9216 KiB Speed: 2057 MHz min/max: 800/4100 MHz Core speeds (MHz): 1: 2112 2: 894 3: 1909 4: 2159 5: 2345 6: 1979 7: 1579 8: 2316 9: 1214 10: 988 11: 2344 12: 929 Graphics: Device-1: Intel UHD Graphics 630 driver: i915 v: kernel Device-2: NVIDIA GP107M [GeForce GTX 1050 Ti Mobile] driver: N/A Display: x11 server: X.Org 1.20.7 driver: modesetting,nvidia unloaded: fbdev,nouveau,vesa resolution: 1920x1080~60Hz OpenGL: renderer: Mesa Intel UHD Graphics 630 (CFL GT2) v: 4.6 Mesa 20.0.0 Audio: Device-1: Intel Cannon Lake PCH cAVS driver: snd_hda_intel Device-2: Texas Instruments PCM2902 Audio Codec type: USB driver: hid-generic,snd-usb-audio,usbhid Sound Server: ALSA v: k5.5.7-050507-generic ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 Uname: Linux 5.5.7-050507-generic x86_64 ApportVersion: 2.20.11-0ubuntu18 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Mar 9 13:20:11 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: nvidia, 440.59, 5.4.0-14-generic, x86_64: installed nvidia, 440.59, 5.5.7-050507-generic, x86_64: installed v4l2loopback, 0.12.3, 5.5.7-050507-generic, x86_64: installed virtualbox, 6.1.4, 5.5.7-050507-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation UHD Graphics 630 (Mobile) [8086:3e9b] (prog-if 00 [VGA controller]) Subsystem: Dell UHD Graphics 630 (Mobile) [1028:087c] InstallationDate: Installed on 2020-03-03 (5 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200303) MachineType: Dell Inc. XPS 15 9570 ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.5.7-050507-generic root=UUID=5490caea-406b-4a4c-afee-178210995fe8 ro quiet splash mem_sleep_default=deep SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/25/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.15.0 dmi.board.name: 0D0T05 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.15.0:bd12/25/2019:svnDellInc.:pnXPS159570:pvr:rvnDellInc.:rn0D0T05:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 15 9570 dmi.product.sku: 087C dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.100-4 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.0-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.0-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.7-2ubuntu2 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+git20190815-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug corruption focal reproducible single-occurrence third-party-packages ubuntu -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1866712 Title: Graphic glitches with Nvidia 440 on Dell XPS 15 9570 Status in xorg package in Ubuntu: New Bug description: I am experiencing intermittent graphical glitches. I couldn't find where this had been reported before so please excuse the duplicate if this is a known issue. I tried recording my screen to demonstrate what is happening but, although I am seeing the issue on the desktop, it does not show up in the video. I am using prime-select in intel mode. System:Host: rex Kernel: 5.5.7-050507-generic x86_64 bits: 64 Desktop: Gnome 3.35.91 Distro: Ubuntu 20.04 LTS (Focal Fossa) Machine: Type: Laptop System: Dell product: XPS 15 9570
Re: [Touch-packages] [Bug 1866625] Re: OverflowError: With Python 3 Gtk.ListStore only accepts 32 Bit Integers.
It works!
On 09.03.20 21:17, Sebastien Bacher wrote:
> COuld you test the upstream workaround and use
> GObject.Value(GObject.TYPE_UINT64, 1330400507426) ?
>
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pygobject in Ubuntu.
https://bugs.launchpad.net/bugs/1866625
Title:
OverflowError: With Python 3 Gtk.ListStore only accepts 32 Bit
Integers.
Status in pygobject package in Ubuntu:
New
Bug description:
import gi
gi.require_version('Gtk', '3.0')
from gi.repository import Gtk
This works in Python 2:
mystore = Gtk.ListStore(long)
mystore.insert_with_valuesv(-1, [1], [long(1330400507426)])
This does not work in Python 3:
mystore = Gtk.ListStore(int)
mystore.insert_with_valuesv(-1, [1], [int(1330400507426)])
OverflowError: Item 0: out of range for int property
lsb_release -rd
Description: Ubuntu 18.04.4 LTS
Release: 18.04
apt-cache policy python3-gi
python3-gi:
Installed: 3.26.1-2ubuntu1
Candidate: 3.26.1-2ubuntu1
Version table:
*** 3.26.1-2ubuntu1 500
500 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64
Packages
100 /var/lib/dpkg/status
3.26.1-2 500
500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages
python3 -V
Python 3.6.9
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pygobject/+bug/1866625/+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 1866625] Re: OverflowError: With Python 3 Gtk.ListStore only accepts 32 Bit Integers.
COuld you test the upstream workaround and use
GObject.Value(GObject.TYPE_UINT64, 1330400507426) ?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pygobject in Ubuntu.
https://bugs.launchpad.net/bugs/1866625
Title:
OverflowError: With Python 3 Gtk.ListStore only accepts 32 Bit
Integers.
Status in pygobject package in Ubuntu:
New
Bug description:
import gi
gi.require_version('Gtk', '3.0')
from gi.repository import Gtk
This works in Python 2:
mystore = Gtk.ListStore(long)
mystore.insert_with_valuesv(-1, [1], [long(1330400507426)])
This does not work in Python 3:
mystore = Gtk.ListStore(int)
mystore.insert_with_valuesv(-1, [1], [int(1330400507426)])
OverflowError: Item 0: out of range for int property
lsb_release -rd
Description: Ubuntu 18.04.4 LTS
Release: 18.04
apt-cache policy python3-gi
python3-gi:
Installed: 3.26.1-2ubuntu1
Candidate: 3.26.1-2ubuntu1
Version table:
*** 3.26.1-2ubuntu1 500
500 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64
Packages
100 /var/lib/dpkg/status
3.26.1-2 500
500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages
python3 -V
Python 3.6.9
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pygobject/+bug/1866625/+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 1865517] Re: cannot log in with long username
for the record I don't find any hard-coded limit on username length in pam. -- 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/1865517 Title: cannot log in with long username Status in util-linux package in Ubuntu: Triaged Bug description: We use ldap authentication with mail addresses as usernames. So usernames are not posix and some are > 32 chars but are working. Some of them fire a bug : When trying to log, it doesn't asks for password, it just wait some seconds then reset to ask username. I can't clearly identify which regex fire the bug or not but this one does "username.lastnamelastnamelastn...@domain.fr" I reproduce it on ubuntu 18.04 and 20.04 daylibuild. In auth.log, that line pops up when bug is started "Mar 2 16:23:14 premier agetty[97945]: checkname failed: Operation not permitted" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1865517/+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 1865517] Re: cannot log in with long username
There is a hard-coded limit of 42 characters in agetty, from util-linux. I don't know why this limit exists, but reassigning there. ** Package changed: pam (Ubuntu) => util-linux (Ubuntu) ** Changed in: util-linux (Ubuntu) Status: Incomplete => Triaged -- 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/1865517 Title: cannot log in with long username Status in util-linux package in Ubuntu: Triaged Bug description: We use ldap authentication with mail addresses as usernames. So usernames are not posix and some are > 32 chars but are working. Some of them fire a bug : When trying to log, it doesn't asks for password, it just wait some seconds then reset to ask username. I can't clearly identify which regex fire the bug or not but this one does "username.lastnamelastnamelastn...@domain.fr" I reproduce it on ubuntu 18.04 and 20.04 daylibuild. In auth.log, that line pops up when bug is started "Mar 2 16:23:14 premier agetty[97945]: checkname failed: Operation not permitted" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1865517/+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 1859754] Autopkgtest regression report (alsa-lib/1.1.9-0ubuntu1.2)
All autopkgtests for the newly accepted alsa-lib (1.1.9-0ubuntu1.2) for eoan have finished running. The following regressions have been reported in tests triggered by the package: openjdk-lts/unknown (i386) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/eoan/update_excuses.html#alsa-lib [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-lib in Ubuntu. https://bugs.launchpad.net/bugs/1859754 Title: add ucm to make alsa/sof driver work under PA (variants of Lenovo X1 Carbon 7th, Dell cnl and cml machines) Status in HWE Next: New Status in alsa-lib package in Ubuntu: Fix Committed Status in alsa-lib source package in Bionic: Fix Committed Status in alsa-lib source package in Eoan: Fix Committed Bug description: This ucm is only for Eoan and Bionic, for focal and future versions, we plan to integrate the ucm2 instead of this ucm, and the ucm2 depends on the alsa-lib-1.2.1 and pluseaudio-v14, the ucm2 is under developing by the community, is not ready yet. [Impact] In the oem project, we have a couple of Lenovo and Dell machines which connect the digital mic to PCH directly, this design needs the new sound driver soc/sof, and this driver can't work under pulseaudio automatically, we need to integrate the ucm for the driver, then the sof dirver could work under pulseaudio and gnome. This ucm is maintained by intel audio team, and it is not upstreamed and will not be upstreamed, since the community is developing the ucm2 which is based on at least alsa-lib-1.2.1 and pulseaudio-v14.0 (still under developing), for bionic and eoan, we have to integrate this ucm since the alsa-lib version is too low. For focal and future version, we are going to integrate the ucm2 after the ucm2 is ready. This ucm is already verified in the oem project, now it is time to put it into the stock ubuntu. [Fix] These ucm files are backported from sof_ucm1 branch of https://github.com/thesofproject/alsa-ucm-conf.git [Test Case] Boot the eoan kernel or oem-osp1-bionic kernel, then check the log of pulseaudio, the ucm files are loaded successfully, then check the gnome-sound-setting, both output and input devices work well. [Regression Risk] Low, just add some new ucm files, and this will not affect other machines, and those new added ucm files are only used by specific machines which enable the sof driver. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1859754/+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 1780316] Re: netcat-openbsd is in main but netcat-standard has a netcat dummy package
** Changed in: netcat (Ubuntu) Status: New => Fix Committed ** Changed in: netcat (Ubuntu) Assignee: (unassigned) => Steve Langasek (vorlon) ** Changed in: netcat-openbsd (Ubuntu) Status: New => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to netcat-openbsd in Ubuntu. https://bugs.launchpad.net/bugs/1780316 Title: netcat-openbsd is in main but netcat-standard has a netcat dummy package Status in netcat package in Ubuntu: Fix Committed Status in netcat-openbsd package in Ubuntu: Fix Committed Bug description: For installations that don't have netcat-openbsd somewhere in the seed then any package/user that installs 'netcat' will get 'netcat- standard' from universe rather than 'netcat-openbsd' from main. (One example is the ubuntu-fan package that recommends netcat) Installing the 'netcat' transitional package should provide users a supported package as one exists. Suggested action: * Remove the 'netcat' dummy package from the netcat-standard package * Add a 'netcat' dummy package to the netcat-openbsd package To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/netcat/+bug/1780316/+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 1866625] Re: OverflowError: With Python 3 Gtk.ListStore only accepts 32 Bit Integers.
I'm not sure what exactly they are really talking about at
https://gitlab.gnome.org/GNOME/pygobject/issues/198.
My FR concerns 3.26.1-2ubuntu1 and at gitlab it is stated "I think it
used to work in 3.26." which
clearly is not the case.
I took a look into the source and in pygi-value.c I found this:
case G_TYPE_INT:
{
glong val = PYGLIB_PyLong_AsLong(obj);
if (val == -1 && PyErr_Occurred ())
return -1;
if (val > G_MAXINT || val < G_MININT) {
PyErr_SetString(PyExc_OverflowError, "out of range for int
property");
return -1;
}
g_value_set_int(value, (gint)val);
break;
}
and a lot of comments like this:
#if PY_VERSION_HEX < 0x0300
[snip]
#endif
To me this means that somebody is/was aware of the fact that some more
work has to be done for
making this stuff compatible to Python 3.
On 09.03.20 14:48, Sebastien Bacher wrote:
> Thank you for your bug report, that seems similar to
> https://gitlab.gnome.org/GNOME/pygobject/issues/198
>
> ** Bug watch added: gitlab.gnome.org/GNOME/pygobject/issues #198
>https://gitlab.gnome.org/GNOME/pygobject/issues/198
>
> ** Changed in: pygobject (Ubuntu)
>Importance: Undecided => Low
>
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pygobject in Ubuntu.
https://bugs.launchpad.net/bugs/1866625
Title:
OverflowError: With Python 3 Gtk.ListStore only accepts 32 Bit
Integers.
Status in pygobject package in Ubuntu:
New
Bug description:
import gi
gi.require_version('Gtk', '3.0')
from gi.repository import Gtk
This works in Python 2:
mystore = Gtk.ListStore(long)
mystore.insert_with_valuesv(-1, [1], [long(1330400507426)])
This does not work in Python 3:
mystore = Gtk.ListStore(int)
mystore.insert_with_valuesv(-1, [1], [int(1330400507426)])
OverflowError: Item 0: out of range for int property
lsb_release -rd
Description: Ubuntu 18.04.4 LTS
Release: 18.04
apt-cache policy python3-gi
python3-gi:
Installed: 3.26.1-2ubuntu1
Candidate: 3.26.1-2ubuntu1
Version table:
*** 3.26.1-2ubuntu1 500
500 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64
Packages
100 /var/lib/dpkg/status
3.26.1-2 500
500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages
python3 -V
Python 3.6.9
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pygobject/+bug/1866625/+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 1866684] [NEW] /usr/share/apport/whoopsie-upload-all:zlib.error:/usr/share/apport/whoopsie-upload-all@168:collect_info:process_report:add_gdb_info:gdb_command:write:read:readinto
*** This bug is a duplicate of bug 1866683 *** https://bugs.launchpad.net/bugs/1866683 Public bug reported: The Ubuntu Error Tracker has been receiving reports about a problem regarding apport. This problem was most recently seen with package version 2.20.11-0ubuntu16, the problem page at https://errors.ubuntu.com/problem/0597078ed49f896ae23c62d7144afc39257efc62 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. ** Affects: apport (Ubuntu) Importance: Undecided Status: New ** Tags: disco eoan focal -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1866684 Title: /usr/share/apport/whoopsie-upload-all:zlib.error:/usr/share/apport /whoopsie-upload- all@168:collect_info:process_report:add_gdb_info:gdb_command:write:read:readinto:read Status in apport package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding apport. This problem was most recently seen with package version 2.20.11-0ubuntu16, the problem page at https://errors.ubuntu.com/problem/0597078ed49f896ae23c62d7144afc39257efc62 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1866684/+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 1866683] Re: /usr/share/apport/whoopsie-upload-all:zlib.error:/usr/share/apport/whoopsie-upload-all@170:collect_info:process_report:add_gdb_info:gdb_command:write:read:readinto:r
Here's the Traceback: Traceback (most recent call last): File "/usr/share/apport/whoopsie-upload-all", line 170, in stamps = collect_info() File "/usr/share/apport/whoopsie-upload-all", line 120, in collect_info res = process_report(r) File "/usr/share/apport/whoopsie-upload-all", line 80, in process_report r.add_gdb_info() File "/usr/lib/python3/dist-packages/apport/report.py", line 736, in add_gdb_info gdb_cmd, environ = self.gdb_command(rootdir, gdb_sandbox) File "/usr/lib/python3/dist-packages/apport/report.py", line 1634, in gdb_command self['CoreDump'].write(f) File "/usr/lib/python3/dist-packages/problem_report.py", line 75, in write block = gz.read(1048576) File "/usr/lib/python3.7/gzip.py", line 276, in read return self._buffer.read(size) File "/usr/lib/python3.7/_compression.py", line 68, in readinto data = self.read(len(byte_view)) File "/usr/lib/python3.7/gzip.py", line 471, in read uncompress = self._decompressor.decompress(buf, size) zlib.error: Error -3 while decompressing data: invalid block type ** Changed in: apport (Ubuntu) Status: New => Triaged ** Changed in: apport (Ubuntu) Importance: Undecided => Medium -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1866683 Title: /usr/share/apport/whoopsie-upload-all:zlib.error:/usr/share/apport /whoopsie-upload- all@170:collect_info:process_report:add_gdb_info:gdb_command:write:read:readinto:read Status in apport package in Ubuntu: Triaged Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding apport. This problem was most recently seen with package version 2.20.11-0ubuntu18, the problem page at https://errors.ubuntu.com/problem/b87ae42c1da6c2ae7d1b6ae04d196a7c2a4b0469 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1866683/+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 1866685] Re: /usr/share/apport/whoopsie-upload-all:zlib.error:/usr/share/apport/whoopsie-upload-all@162:collect_info:process_report:add_gdb_info:gdb_command:write:read:readinto:r
*** This bug is a duplicate of bug 1866683 *** https://bugs.launchpad.net/bugs/1866683 ** This bug has been marked a duplicate of bug 1866683 /usr/share/apport/whoopsie-upload-all:zlib.error:/usr/share/apport/whoopsie-upload-all@170:collect_info:process_report:add_gdb_info:gdb_command:write:read:readinto:read -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1866685 Title: /usr/share/apport/whoopsie-upload-all:zlib.error:/usr/share/apport /whoopsie-upload- all@162:collect_info:process_report:add_gdb_info:gdb_command:write:read:readinto:read Status in apport package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding apport. This problem was most recently seen with package version 2.20.10-0ubuntu20, the problem page at https://errors.ubuntu.com/problem/13e7002962d174da532971a8da59eb963ea11840 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1866685/+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 1866683] [NEW] /usr/share/apport/whoopsie-upload-all:zlib.error:/usr/share/apport/whoopsie-upload-all@170:collect_info:process_report:add_gdb_info:gdb_command:write:read:readinto
Public bug reported: The Ubuntu Error Tracker has been receiving reports about a problem regarding apport. This problem was most recently seen with package version 2.20.11-0ubuntu18, the problem page at https://errors.ubuntu.com/problem/b87ae42c1da6c2ae7d1b6ae04d196a7c2a4b0469 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. ** Affects: apport (Ubuntu) Importance: Medium Status: Triaged ** Tags: eoan focal -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1866683 Title: /usr/share/apport/whoopsie-upload-all:zlib.error:/usr/share/apport /whoopsie-upload- all@170:collect_info:process_report:add_gdb_info:gdb_command:write:read:readinto:read Status in apport package in Ubuntu: Triaged Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding apport. This problem was most recently seen with package version 2.20.11-0ubuntu18, the problem page at https://errors.ubuntu.com/problem/b87ae42c1da6c2ae7d1b6ae04d196a7c2a4b0469 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1866683/+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 1866684] Re: /usr/share/apport/whoopsie-upload-all:zlib.error:/usr/share/apport/whoopsie-upload-all@168:collect_info:process_report:add_gdb_info:gdb_command:write:read:readinto:r
*** This bug is a duplicate of bug 1866683 *** https://bugs.launchpad.net/bugs/1866683 ** This bug has been marked a duplicate of bug 1866683 /usr/share/apport/whoopsie-upload-all:zlib.error:/usr/share/apport/whoopsie-upload-all@170:collect_info:process_report:add_gdb_info:gdb_command:write:read:readinto:read -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1866684 Title: /usr/share/apport/whoopsie-upload-all:zlib.error:/usr/share/apport /whoopsie-upload- all@168:collect_info:process_report:add_gdb_info:gdb_command:write:read:readinto:read Status in apport package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding apport. This problem was most recently seen with package version 2.20.11-0ubuntu16, the problem page at https://errors.ubuntu.com/problem/0597078ed49f896ae23c62d7144afc39257efc62 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1866684/+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 1866685] [NEW] /usr/share/apport/whoopsie-upload-all:zlib.error:/usr/share/apport/whoopsie-upload-all@162:collect_info:process_report:add_gdb_info:gdb_command:write:read:readinto
*** This bug is a duplicate of bug 1866683 *** https://bugs.launchpad.net/bugs/1866683 Public bug reported: The Ubuntu Error Tracker has been receiving reports about a problem regarding apport. This problem was most recently seen with package version 2.20.10-0ubuntu20, the problem page at https://errors.ubuntu.com/problem/13e7002962d174da532971a8da59eb963ea11840 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. ** Affects: apport (Ubuntu) Importance: Undecided Status: New ** Tags: bionic cosmic disco kylin-18.04 zesty -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1866685 Title: /usr/share/apport/whoopsie-upload-all:zlib.error:/usr/share/apport /whoopsie-upload- all@162:collect_info:process_report:add_gdb_info:gdb_command:write:read:readinto:read Status in apport package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding apport. This problem was most recently seen with package version 2.20.10-0ubuntu20, the problem page at https://errors.ubuntu.com/problem/13e7002962d174da532971a8da59eb963ea11840 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1866685/+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 1866682] [NEW] Mute toggles on/off while plugged into the headphone/speaker jack (19.04+)
Public bug reported: I'm on an HP Pavilion dv9000 (https://www.cnet.com/products/hp-pavilion- dv9000/specs/) built many years ago. Whenever I'm using any distro that's based on Ubuntu which was published from Version 19.04 onwards, I've been having a major issue with the mute button toggling on and off whenever I have something plugged into the audio out jack. I know that it's not the fault of XFCE, because I also use the latest version of Manjaro with XFCE on this same computer, and it works fine. I also know it's not any Red Hat-based distro, because I use Stella (which is a remix of CentOS 6) also on this exact same computer, and it also works fine. Qubes, Mageia, and Fedora 31 also work perfectly fine and don't have this issue. My "lsb-release" is: DISTRIB_ID=Ubuntu DISTRIB_RELEASE=19.10 DISTRIB_CODENAME=eoan DISTRIB_DESCRIPTION="Ubuntu 19.10" and "apt-cache policy alsa-utils" outputs: alsa-utils: Installed: 1.1.9-0ubuntu1 Candidate: 1.1.9-0ubuntu1 Version table: *** 1.1.9-0ubuntu1 500 500 http://us.archive.ubuntu.com/ubuntu eoan/main amd64 Packages 100 /var/lib/dpkg/status I've uploaded a short video of the problem that I recorded with my phone here: https://www.youtube.com/watch?v=GXaHXQA-5uQ The problem appears with Kali 2019 and 2020, Peppermint 19.04, Lubuntu 19.04, Xubuntu 19.04, and Sparky 5.10 and 2020.02. I've checked pretty much everything I can think of. There's a log for my ALSA help diagnostics results on my current computer (which works properly with 18.04) at: http://alsa-project.org/db/?f=4859b85cd7fc32e7f01f8df63591b5a43dbf6829 the result output of lspci is: [code]00:00.0 RAM memory: NVIDIA Corporation C51 Host Bridge (rev a2) 00:00.1 RAM memory: NVIDIA Corporation C51 Memory Controller 0 (rev a2) 00:00.2 RAM memory: NVIDIA Corporation C51 Memory Controller 1 (rev a2) 00:00.3 RAM memory: NVIDIA Corporation C51 Memory Controller 5 (rev a2) 00:00.4 RAM memory: NVIDIA Corporation C51 Memory Controller 4 (rev a2) 00:00.5 RAM memory: NVIDIA Corporation C51 Host Bridge (rev a2) 00:00.6 RAM memory: NVIDIA Corporation C51 Memory Controller 3 (rev a2) 00:00.7 RAM memory: NVIDIA Corporation C51 Memory Controller 2 (rev a2) 00:02.0 PCI bridge: NVIDIA Corporation C51 PCI Express Bridge (rev a1) 00:03.0 PCI bridge: NVIDIA Corporation C51 PCI Express Bridge (rev a1) 00:04.0 PCI bridge: NVIDIA Corporation C51 PCI Express Bridge (rev a1) 00:09.0 RAM memory: NVIDIA Corporation MCP51 Host Bridge (rev a2) 00:0a.0 ISA bridge: NVIDIA Corporation MCP51 LPC Bridge (rev a3) 00:0a.1 SMBus: NVIDIA Corporation MCP51 SMBus (rev a3) 00:0a.3 Co-processor: NVIDIA Corporation MCP51 PMU (rev a3) 00:0b.0 USB controller: NVIDIA Corporation MCP51 USB Controller (rev a3) 00:0b.1 USB controller: NVIDIA Corporation MCP51 USB Controller (rev a3) 00:0d.0 IDE interface: NVIDIA Corporation MCP51 IDE (rev f1) 00:0e.0 IDE interface: NVIDIA Corporation MCP51 Serial ATA Controller (rev f1) 00:0f.0 IDE interface: NVIDIA Corporation MCP51 Serial ATA Controller (rev f1) 00:10.0 PCI bridge: NVIDIA Corporation MCP51 PCI Bridge (rev a2) 00:10.1 Audio device: NVIDIA Corporation MCP51 High Definition Audio (rev a2) 00:14.0 Bridge: NVIDIA Corporation MCP51 Ethernet Controller (rev a3) 00:18.0 Host bridge: Advanced Micro Devices, Inc. [AMD] K8 [Athlon64/Opteron] HyperTransport Technology Configuration 00:18.1 Host bridge: Advanced Micro Devices, Inc. [AMD] K8 [Athlon64/Opteron] Address Map 00:18.2 Host bridge: Advanced Micro Devices, Inc. [AMD] K8 [Athlon64/Opteron] DRAM Controller 00:18.3 Host bridge: Advanced Micro Devices, Inc. [AMD] K8 [Athlon64/Opteron] Miscellaneous Control 03:00.0 Network controller: Broadcom Inc. and subsidiaries BCM4311 802.11b/g WLAN (rev 01) 05:00.0 VGA compatible controller: NVIDIA Corporation G73M [GeForce Go 7600] (rev a1) 07:05.0 FireWire (IEEE 1394): Ricoh Co Ltd R5C832 IEEE 1394 Controller 07:05.1 SD Host controller: Ricoh Co Ltd R5C822 SD/SDIO/MMC/MS/MSPro Host Adapter (rev 19) 07:05.2 System peripheral: Ricoh Co Ltd R5C592 Memory Stick Bus Host Adapter (rev 0a) 07:05.3 System peripheral: Ricoh Co Ltd xD-Picture Card Controller (rev 05)[/code] and my output for arecord -l is: [code] List of CAPTURE Hardware Devices card 0: NVidia [HDA NVidia], device 0: CX20549 Analog [CX20549 Analog] Subdevices: 1/1 Subdevice #0: subdevice #0[/code] I've tried reinstalling both PulseAudio and ALSA Mixer, and nothing works. I'm completely lost for ideas. What can I do to solve the problem? Can anybody please help? ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: alsa-utils 1.1.9-0ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-40.32-generic 5.3.18 Uname: Linux 5.3.0-40-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.4 Architecture: amd64 CurrentDesktop: XFCE Date: Mon Mar 9 14:20:07 2020 InstallationDate: Installed on 2020-03-01 (8 days ago) InstallationMedia: Xubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) SourcePackage: alsa-utils UpgradeStatus:
[Touch-packages] [Bug 1866681] [NEW] Mute toggles on/off while plugged into the headphone/speaker jack (19.04+)
Public bug reported: I'm on an HP Pavilion dv9000 (https://www.cnet.com/products/hp-pavilion- dv9000/specs/) built many years ago. Whenever I'm using any distro that's based on Ubuntu which was published from Version 19.04 onwards, I've been having a major issue with the mute button toggling on and off whenever I have something plugged into the audio out jack. I know that it's not the fault of XFCE, because I also use the latest version of Manjaro with XFCE on this same computer, and it works fine. I also know it's not any Red Hat-based distro, because I use Stella (which is a remix of CentOS 6) also on this exact same computer, and it also works fine. Qubes, Mageia, and Fedora 31 also work perfectly fine and don't have this issue. My "lsb-release" is: DISTRIB_ID=Ubuntu DISTRIB_RELEASE=19.10 DISTRIB_CODENAME=eoan DISTRIB_DESCRIPTION="Ubuntu 19.10" and "apt-cache policy pulseaudio" outputs: pulseaudio: Installed: 1:13.0-1ubuntu1.1 Candidate: 1:13.0-1ubuntu1.1 Version table: *** 1:13.0-1ubuntu1.1 500 500 http://us.archive.ubuntu.com/ubuntu eoan-updates/main amd64 Packages 100 /var/lib/dpkg/status 1:13.0-1ubuntu1 500 500 http://us.archive.ubuntu.com/ubuntu eoan/main amd64 Packages I've uploaded a short video of the problem that I recorded with my phone here: https://www.youtube.com/watch?v=GXaHXQA-5uQ The problem appears with Kali 2019 and 2020, Peppermint 19.04, Lubuntu 19.04, Xubuntu 19.04, and Sparky 5.10 and 2020.02. I've checked pretty much everything I can think of. There's a log for my ALSA help diagnostics results on my current computer (which works properly with 18.04) at: http://alsa-project.org/db/?f=4859b85cd7fc32e7f01f8df63591b5a43dbf6829 the result output of lspci is: [code]00:00.0 RAM memory: NVIDIA Corporation C51 Host Bridge (rev a2) 00:00.1 RAM memory: NVIDIA Corporation C51 Memory Controller 0 (rev a2) 00:00.2 RAM memory: NVIDIA Corporation C51 Memory Controller 1 (rev a2) 00:00.3 RAM memory: NVIDIA Corporation C51 Memory Controller 5 (rev a2) 00:00.4 RAM memory: NVIDIA Corporation C51 Memory Controller 4 (rev a2) 00:00.5 RAM memory: NVIDIA Corporation C51 Host Bridge (rev a2) 00:00.6 RAM memory: NVIDIA Corporation C51 Memory Controller 3 (rev a2) 00:00.7 RAM memory: NVIDIA Corporation C51 Memory Controller 2 (rev a2) 00:02.0 PCI bridge: NVIDIA Corporation C51 PCI Express Bridge (rev a1) 00:03.0 PCI bridge: NVIDIA Corporation C51 PCI Express Bridge (rev a1) 00:04.0 PCI bridge: NVIDIA Corporation C51 PCI Express Bridge (rev a1) 00:09.0 RAM memory: NVIDIA Corporation MCP51 Host Bridge (rev a2) 00:0a.0 ISA bridge: NVIDIA Corporation MCP51 LPC Bridge (rev a3) 00:0a.1 SMBus: NVIDIA Corporation MCP51 SMBus (rev a3) 00:0a.3 Co-processor: NVIDIA Corporation MCP51 PMU (rev a3) 00:0b.0 USB controller: NVIDIA Corporation MCP51 USB Controller (rev a3) 00:0b.1 USB controller: NVIDIA Corporation MCP51 USB Controller (rev a3) 00:0d.0 IDE interface: NVIDIA Corporation MCP51 IDE (rev f1) 00:0e.0 IDE interface: NVIDIA Corporation MCP51 Serial ATA Controller (rev f1) 00:0f.0 IDE interface: NVIDIA Corporation MCP51 Serial ATA Controller (rev f1) 00:10.0 PCI bridge: NVIDIA Corporation MCP51 PCI Bridge (rev a2) 00:10.1 Audio device: NVIDIA Corporation MCP51 High Definition Audio (rev a2) 00:14.0 Bridge: NVIDIA Corporation MCP51 Ethernet Controller (rev a3) 00:18.0 Host bridge: Advanced Micro Devices, Inc. [AMD] K8 [Athlon64/Opteron] HyperTransport Technology Configuration 00:18.1 Host bridge: Advanced Micro Devices, Inc. [AMD] K8 [Athlon64/Opteron] Address Map 00:18.2 Host bridge: Advanced Micro Devices, Inc. [AMD] K8 [Athlon64/Opteron] DRAM Controller 00:18.3 Host bridge: Advanced Micro Devices, Inc. [AMD] K8 [Athlon64/Opteron] Miscellaneous Control 03:00.0 Network controller: Broadcom Inc. and subsidiaries BCM4311 802.11b/g WLAN (rev 01) 05:00.0 VGA compatible controller: NVIDIA Corporation G73M [GeForce Go 7600] (rev a1) 07:05.0 FireWire (IEEE 1394): Ricoh Co Ltd R5C832 IEEE 1394 Controller 07:05.1 SD Host controller: Ricoh Co Ltd R5C822 SD/SDIO/MMC/MS/MSPro Host Adapter (rev 19) 07:05.2 System peripheral: Ricoh Co Ltd R5C592 Memory Stick Bus Host Adapter (rev 0a) 07:05.3 System peripheral: Ricoh Co Ltd xD-Picture Card Controller (rev 05)[/code] and my output for arecord -l is: [code] List of CAPTURE Hardware Devices card 0: NVidia [HDA NVidia], device 0: CX20549 Analog [CX20549 Analog] Subdevices: 1/1 Subdevice #0: subdevice #0[/code] I've tried reinstalling both PulseAudio and ALSA Mixer, and nothing works. I'm completely lost for ideas. What can I do to solve the problem? Can anybody please help? ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: pulseaudio 1:13.0-1ubuntu1.1 ProcVersionSignature: Ubuntu 5.3.0-40.32-generic 5.3.18 Uname: Linux 5.3.0-40-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: dudebro 952 F
[Touch-packages] [Bug 1866571] Re: Sync acl 2.2.53-6 (main) from Debian unstable (main)
This bug was fixed in the package acl - 2.2.53-6 Sponsored for Logan Rosen (logan) --- acl (2.2.53-6) unstable; urgency=medium * Redirect stderr to stdout globally in autopkgtests instead of doing that per command. * Enable set -x and -u in autopkgtests. * Add support for cross-compilation to autopkgtests. Closes: #947048 * Update upstream email address. Closes: #949688 * Fix usage of uninitialized variable in getfacl. Closes: #612599 Thanks to Vasily Gurevich . * Switch to Standards-Version 4.5.0 (no changes needed). -- Guillem Jover Sun, 01 Mar 2020 02:06:51 +0100 ** Changed in: acl (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to acl in Ubuntu. https://bugs.launchpad.net/bugs/1866571 Title: Sync acl 2.2.53-6 (main) from Debian unstable (main) Status in acl package in Ubuntu: Fix Released Bug description: Please sync acl 2.2.53-6 (main) from Debian unstable (main) Explanation of the Ubuntu delta and why it can be dropped: * Make autopkgtests cross-test-friendly. This patch was pulled into Debian. Changelog entries since current focal version 2.2.53-5ubuntu1: acl (2.2.53-6) unstable; urgency=medium * Redirect stderr to stdout globally in autopkgtests instead of doing that per command. * Enable set -x and -u in autopkgtests. * Add support for cross-compilation to autopkgtests. Closes: #947048 * Update upstream email address. Closes: #949688 * Fix usage of uninitialized variable in getfacl. Closes: #612599 Thanks to Vasily Gurevich . * Switch to Standards-Version 4.5.0 (no changes needed). -- Guillem Jover Sun, 01 Mar 2020 02:06:51 +0100 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/acl/+bug/1866571/+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 1866570] Re: Sync alsa-lib 1.2.2-2.1 (main) from Debian unstable (main)
This bug was fixed in the package alsa-lib - 1.2.2-2.1 Sponsored for Logan Rosen (logan) --- alsa-lib (1.2.2-2.1) unstable; urgency=medium [ Matthias Klose ] * Non-maintainer upload. [ Sebastien Bacher ] * debian/patches/python3.8.diff: - fix the build with python 3.8 -- Matthias Klose Sat, 07 Mar 2020 19:21:22 +0100 ** Changed in: alsa-lib (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-lib in Ubuntu. https://bugs.launchpad.net/bugs/1866570 Title: Sync alsa-lib 1.2.2-2.1 (main) from Debian unstable (main) Status in alsa-lib package in Ubuntu: Fix Released Bug description: Please sync alsa-lib 1.2.2-2.1 (main) from Debian unstable (main) Explanation of the Ubuntu delta and why it can be dropped: * Resynchronize with Debian * debian/patches/python3.8.diff: - fix the build with python 3.8 The Python 3.8 patch was pulled into Debian. Changelog entries since current focal version 1.2.2-2ubuntu1: alsa-lib (1.2.2-2.1) unstable; urgency=medium [ Matthias Klose ] * Non-maintainer upload. [ Sebastien Bacher ] * debian/patches/python3.8.diff: - fix the build with python 3.8 -- Matthias Klose Sat, 07 Mar 2020 19:21:22 +0100 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-lib/+bug/1866570/+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 1865517] Re: cannot log in with long username
ok, sorry for misreading. will retest here. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pam in Ubuntu. https://bugs.launchpad.net/bugs/1865517 Title: cannot log in with long username Status in pam package in Ubuntu: Incomplete Bug description: We use ldap authentication with mail addresses as usernames. So usernames are not posix and some are > 32 chars but are working. Some of them fire a bug : When trying to log, it doesn't asks for password, it just wait some seconds then reset to ask username. I can't clearly identify which regex fire the bug or not but this one does "username.lastnamelastnamelastn...@domain.fr" I reproduce it on ubuntu 18.04 and 20.04 daylibuild. In auth.log, that line pops up when bug is started "Mar 2 16:23:14 premier agetty[97945]: checkname failed: Operation not permitted" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pam/+bug/1865517/+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 1866628] Re: WiFi connection slows down significantly when Bluetooth headset connected (QCA9377 chip)
thank you for your bug report, looks like a kernel issue rather than a n-m one Could you add a 'journalctl -b 0' log from a session having the issue? ** Package changed: network-manager (Ubuntu) => linux (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1866628 Title: WiFi connection slows down significantly when Bluetooth headset connected (QCA9377 chip) Status in linux package in Ubuntu: New Bug description: STEPS TO REPRODUCE: 1. Connect laptop to internet via WiFi only. 2. Play any HD video on YouTube, etc. 3. Pair Bluetooth headset with laptop. ACTUAL RESULT: Video plays with long interruptions after Bluetooth headset was connected. EXPECTED RESULT: Video plays without interruptions when Bluetooth headset connected. NOTES: Bug reproduces on Ubuntu 18.04 and Ubuntu 19.10. Laptop: Lenovo IdeaPad 330-15IKB (81DE02VHRA). Network chip: QCA9377 https://www.qualcomm.com/products/qca9377 THERE ARE A LOT OF MENTIONS OVER INTERNET OF SAME PROBLEM OF THIS CHIP WITH UBUNTU BUT NO SUCH PROBLEM ON WINDOWS 10. One of them: https://forums.linuxmint.com/viewtopic.php?t=302482 POSSIBLE SOLUTION DESCRIBED HERE: https://askubuntu.com/questions/1097230/ubuntu-18-04-poor-wi-fi-when-connected-with-bluetooth-headphone Driver info in attachment. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1866628/+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 1861645] Re: PC fails to shutdown.
@Prakash, for syslog file, it's under /var/log/syslog. -- 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/1861645 Title: PC fails to shutdown. Status in linux package in Ubuntu: Incomplete Status in systemd package in Ubuntu: New Bug description: I have a pc with Motherboard Gigabyte H370M D3H, Processor Intel Core I3 8100 3.6Ghz 6MbL3, RAM Corsair 16Mb 2400 Hz. I can reboot pc without any problem, but pc is stuck on ubuntu logo when I shutdown. while shutdown keyboard and mouse are turned off but pc remains on. I have to turn the mains power off to shutdown the pc. I think this is a major bug in Ubuntu 19.10. I searched for a solution on the internet but could not find any that works. Kindly help to fix it. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: prakash1438 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.10 InstallationDate: Installed on 2020-01-31 (2 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) IwConfig: lono wireless extensions. eno1 no wireless extensions. Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 093a:2510 Pixart Imaging, Inc. Optical Mouse Bus 001 Device 003: ID 1a2c:0e24 China Resource Semico Co., Ltd USB Keyboard Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Gigabyte Technology Co., Ltd. H370M-D3H Package: systemd 242-7ubuntu3.2 PackageArchitecture: amd64 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-29-generic root=UUID=a883551d-0fff-4cdb-bc6d-d442860a0ec0 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.3.0-29.31-generic 5.3.13 RelatedPackageVersions: linux-restricted-modules-5.3.0-29-generic N/A linux-backports-modules-5.3.0-29-generic N/A linux-firmware1.183.3 RfKill: Tags: eoan Uname: Linux 5.3.0-29-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 03/14/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F12 dmi.board.asset.tag: Default string dmi.board.name: H370M D3H-CF dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF12:bd03/14/2019:svnGigabyteTechnologyCo.,Ltd.:pnH370M-D3H:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnH370MD3H-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: H370M-D3H dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1861645/+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 1866347] Re: /usr/share/apport/whoopsie-upload-all:AssertionError:/usr/share/apport/whoopsie-upload-all@168:collect_info:process_report:add_gdb_info:crash_signature_addresses:_ad
** Branch linked: lp:~ubuntu-core-dev/ubuntu/focal/apport/ubuntu -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1866347 Title: /usr/share/apport/whoopsie-upload-all:AssertionError:/usr/share/apport /whoopsie-upload- all@168:collect_info:process_report:add_gdb_info:crash_signature_addresses:_address_to_offset:_build_proc_maps_cache Status in apport package in Ubuntu: In Progress Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding apport. This problem was most recently seen with package version 2.20.11-0ubuntu17, the problem page at https://errors.ubuntu.com/problem/5cc81a1cde2a921ad2adcc00e2f8d13f2c9f76e8 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1866347/+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 1866314] Re: apt-get update fails on ppc64le virtual machine
This didn't reproduce on the machine which initially showed the problem. So this bug can be closed 'worksforme'. -- 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/1866314 Title: apt-get update fails on ppc64le virtual machine Status in apt package in Ubuntu: New Bug description: I am trying to install Ubuntu 20.04 for ppc64le in a virtual machine. (The host is x86-64 running OpenSUSE Tumbleweed). The install works, but on reboot when I attempt to install updates with 'apt-get update' and 'apt-get upgrade', the update command fails with a segmentation violation. It indicates that core is dumped but I don't see a core dump in my current directory. I will add a screenshot of the problem. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: apt 1.9.7 ProcVersionSignature: Ubuntu 5.4.0-9.12-generic 5.4.3 Uname: Linux 5.4.0-9-generic ppc64le .var.log.platform: Error: [Errno 13] Permission denied: '/var/log/platform' ApportVersion: 2.20.11-0ubuntu15 Architecture: ppc64el Date: Fri Mar 6 08:57:02 2020 InstallationDate: Installed on 2020-03-06 (0 days ago) InstallationMedia: Ubuntu-Server 20.04 LTS "Focal Fossa" - Alpha ppc64el (20200124) ProcLoadAvg: 1.00 0.98 1.72 1/104 2304 ProcLocks: 1: POSIX ADVISORY WRITE 868 00:19:478 0 EOF 2: FLOCK ADVISORY WRITE 832 00:19:506 0 EOF 3: POSIX ADVISORY WRITE 773 00:19:462 0 EOF ProcSwaps: Filename TypeSizeUsedPriority /swapfile file 969536 0 -2 ProcVersion: Linux version 5.4.0-9-generic (buildd@bos02-ppc64el-004) (gcc version 9.2.1 20191130 (Ubuntu 9.2.1-21ubuntu1)) #12-Ubuntu SMP Mon Dec 16 22:32:07 UTC 2019 SourcePackage: apt UpgradeStatus: No upgrade log present (probably fresh install) cpu_cores: Number of cores present = 1 cpu_coreson: Number of cores online = 1 cpu_smt: Error: command ['ppc64_cpu', '--smt'] failed with exit code 255: Machine is not SMT capable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1866314/+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 1866625] Re: OverflowError: With Python 3 Gtk.ListStore only accepts 32 Bit Integers.
Thank you for your bug report, that seems similar to
https://gitlab.gnome.org/GNOME/pygobject/issues/198
** Bug watch added: gitlab.gnome.org/GNOME/pygobject/issues #198
https://gitlab.gnome.org/GNOME/pygobject/issues/198
** Changed in: pygobject (Ubuntu)
Importance: Undecided => Low
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pygobject in Ubuntu.
https://bugs.launchpad.net/bugs/1866625
Title:
OverflowError: With Python 3 Gtk.ListStore only accepts 32 Bit
Integers.
Status in pygobject package in Ubuntu:
New
Bug description:
import gi
gi.require_version('Gtk', '3.0')
from gi.repository import Gtk
This works in Python 2:
mystore = Gtk.ListStore(long)
mystore.insert_with_valuesv(-1, [1], [long(1330400507426)])
This does not work in Python 3:
mystore = Gtk.ListStore(int)
mystore.insert_with_valuesv(-1, [1], [int(1330400507426)])
OverflowError: Item 0: out of range for int property
lsb_release -rd
Description: Ubuntu 18.04.4 LTS
Release: 18.04
apt-cache policy python3-gi
python3-gi:
Installed: 3.26.1-2ubuntu1
Candidate: 3.26.1-2ubuntu1
Version table:
*** 3.26.1-2ubuntu1 500
500 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64
Packages
100 /var/lib/dpkg/status
3.26.1-2 500
500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages
python3 -V
Python 3.6.9
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pygobject/+bug/1866625/+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 1866628] [NEW] WiFi connection slows down significantly when Bluetooth headset connected (QCA9377 chip)
Public bug reported: STEPS TO REPRODUCE: 1. Connect laptop to internet via WiFi only. 2. Play any HD video on YouTube, etc. 3. Pair Bluetooth headset with laptop. ACTUAL RESULT: Video plays with long interruptions after Bluetooth headset was connected. EXPECTED RESULT: Video plays without interruptions when Bluetooth headset connected. NOTES: Bug reproduces on Ubuntu 18.04 and Ubuntu 19.10. Laptop: Lenovo IdeaPad 330-15IKB (81DE02VHRA). Network chip: QCA9377 https://www.qualcomm.com/products/qca9377 THERE ARE A LOT OF MENTIONS OVER INTERNET OF SAME PROBLEM OF THIS CHIP WITH UBUNTU BUT NO SUCH PROBLEM ON WINDOWS 10. One of them: https://forums.linuxmint.com/viewtopic.php?t=302482 POSSIBLE SOLUTION DESCRIBED HERE: https://askubuntu.com/questions/1097230/ubuntu-18-04-poor-wi-fi-when-connected-with-bluetooth-headphone Driver info in attachment. ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New ** Tags: bluetooth headset network qca9377 qualcomm wifi ** Attachment added: "Driver info" https://bugs.launchpad.net/bugs/1866628/+attachment/5334868/+files/bt_bug.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1866628 Title: WiFi connection slows down significantly when Bluetooth headset connected (QCA9377 chip) Status in network-manager package in Ubuntu: New Bug description: STEPS TO REPRODUCE: 1. Connect laptop to internet via WiFi only. 2. Play any HD video on YouTube, etc. 3. Pair Bluetooth headset with laptop. ACTUAL RESULT: Video plays with long interruptions after Bluetooth headset was connected. EXPECTED RESULT: Video plays without interruptions when Bluetooth headset connected. NOTES: Bug reproduces on Ubuntu 18.04 and Ubuntu 19.10. Laptop: Lenovo IdeaPad 330-15IKB (81DE02VHRA). Network chip: QCA9377 https://www.qualcomm.com/products/qca9377 THERE ARE A LOT OF MENTIONS OVER INTERNET OF SAME PROBLEM OF THIS CHIP WITH UBUNTU BUT NO SUCH PROBLEM ON WINDOWS 10. One of them: https://forums.linuxmint.com/viewtopic.php?t=302482 POSSIBLE SOLUTION DESCRIBED HERE: https://askubuntu.com/questions/1097230/ubuntu-18-04-poor-wi-fi-when-connected-with-bluetooth-headphone Driver info in attachment. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1866628/+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 1018622] Re: [SB Live! Platinum CT4760P] No sound
Apologies, I certainly wasn't getting at you or the project, I only found it amusing. Sorry, that I can no longer confirm whether this is still an issue. Honestly, I wouldn't leave this open for ever as it will only make your backlog worse. -- 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/1018622 Title: [SB Live! Platinum CT4760P] No sound Status in alsa-driver package in Ubuntu: Incomplete Bug description: No further information available. Seems to be a common Ubuntu/Debian problem as few distro's produce sound from this card. Had same problems with Debian 32bit installation. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: alsa-base 1.0.25+dfsg-0ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-25.40-generic 3.2.18 Uname: Linux 3.2.0-25-generic x86_64 NonfreeKernelModules: nvidia AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24. ApportVersion: 2.0.1-0ubuntu8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: julian 4547 F pulseaudio Card0.Amixer.info: Card hw:0 'Live'/'SB Live! Platinum [CT4760P] (rev.7, serial:0x80401102) at 0xa000, irq 18' Mixer name : 'SigmaTel STAC9721,23' Components : 'AC97a:83847609' Controls : 217 Simple ctrls : 38 Card1.Amixer.info: Card hw:1 'CK804'/'NVidia CK804 with ALC850 at irq 22' Mixer name : 'Realtek ALC850 rev 0' Components : 'AC97a:414c4790' Controls : 42 Simple ctrls : 27 CurrentDmesg: Error: command ['sh', '-c', 'dmesg | comm -13 --nocheck-order /var/log/dmesg -'] failed with exit code 1: comm: /var/log/dmesg: Permission denied dmesg: write failed: Broken pipe Date: Wed Jun 27 23:09:49 2012 InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425) PackageArchitecture: all ProcEnviron: LANGUAGE=en_GB:en TERM=xterm PATH=(custom, user) LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/29/2006 dmi.bios.vendor: Phoenix Technologies, LTD dmi.bios.version: ASUS A8N-SLI DELUXE ACPI BIOS Revision 1805 dmi.board.name: A8N-SLI DELUXE dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: 1.XX dmi.chassis.asset.tag: 123456789000 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnPhoenixTechnologies,LTD:bvrASUSA8N-SLIDELUXEACPIBIOSRevision1805:bd09/29/2006:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnA8N-SLIDELUXE:rvr1.XX:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1018622/+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 1853150] Re: [20.04 FEAT] OpenSSL: Support for CPACF enhancements - part 1
The s390x ECC assembly pack improvements landed in package openssl version 1.1.1d-2ubuntu4 and we have version 1.1.1d-2ubuntu6 in the focal release pocket, hence changing the status of this ticket to Fix Released. ** Changed in: openssl (Ubuntu) Status: New => Fix Released ** Changed in: ubuntu-z-systems Status: In Progress => Fix Released ** Information type changed from Private to Public -- 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/1853150 Title: [20.04 FEAT] OpenSSL: Support for CPACF enhancements - part 1 Status in Ubuntu on IBM z Systems: Fix Released Status in openssl package in Ubuntu: Fix Released Bug description: openssl - support of CPACF enhancements commit ids (apply bottom to top): s390x assembly pack: cleanse only sensitive fields https://github.com/openssl/openssl/commit/2281be2ed4a7df462677661d30b13826ae6b3e26 s390x assembly pack: fix OPENSSL_s390xcap z15 cpu mask https://github.com/openssl/openssl/commit/ac037dc874a721ca81a33b4314e26cef4a7e8d48 s390x assembly pack: fix msa3 stfle bit detection https://github.com/openssl/openssl/commit/b3681e2641999be6c1f70e66497fe384d683a07e Fix 9bf682f which broke nistp224_method https://github.com/openssl/openssl/commit/653b883b97f72a15d35d21246696881aa65311e2 OPENSSL_s390xcap.pod: list msa9 facility bit (155) https://github.com/openssl/openssl/commit/3ded2288a45d2cc3a27a1b08d29499cbcec52c0e s390x assembly pack: accelerate ECDSA https://github.com/openssl/openssl/commit/58c35587eacba090414522a6506cb86f2d0e91af Enable curve-spefific ECDSA implementations via EC_METHOD https://github.com/openssl/openssl/commit/9bf682f62bd819d2fbceb95eeabd61dd4532240f s390x assembly pack: accelerate scalar multiplication https://github.com/openssl/openssl/commit/1461e66706f24da657d7322706d1165ae515533f s390xcpuid.pl: fix comment https://github.com/openssl/openssl/commit/9baa4d5f4c9f596faba2b3e219b367a09c472d1d s390x assembly pack: update OPENSSL_s390xcap(3) https://github.com/openssl/openssl/pull/9258/commits/bfd2d995f917b5bf248cd8955849eb985f057457 s390x assembly pack: add support for pcc and kma instructions https://github.com/openssl/openssl/pull/9258/commits/f56e1510f6fcee4682dbf4ddc5e04f4a477654d7 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1853150/+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 1853312] Re: [20.04 FEAT] OpenSSL: Support CPACF enhancements - part 2
The s390x ECC assembly pack improvements landed in package openssl version 1.1.1d-2ubuntu4 and we have version 1.1.1d-2ubuntu6 in the focal release pocket, hence changing the status of this ticket to Fix Released. ** Changed in: openssl (Ubuntu) Status: New => Fix Released ** Changed in: ubuntu-z-systems Status: In Progress => Fix Released -- 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/1853312 Title: [20.04 FEAT] OpenSSL: Support CPACF enhancements - part 2 Status in Ubuntu on IBM z Systems: Fix Released Status in openssl package in Ubuntu: Fix Released Bug description: Support new crypto functions and improve security. Backport information will be provided. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1853312/+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 1866616] Re: 2nd display stopped working
Attaching the 2nd display via DisplayPort rather than DVI allows me to use it again, so I happen to have a solution, but not everyone may be so lucky. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1866616 Title: 2nd display stopped working Status in xorg package in Ubuntu: New Bug description: The 2nd display (attached to DVI) has stopped being detected but is used by bios and grub (output ceases once the spinning boot animation starts). I was away for a week but it was working prior to leaving. I've notices that Xorg.0.log shows DVI-D-0 disconnected where the 2nd monitor should be. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18 Uname: Linux 5.4.0-14-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu18 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Mar 9 06:13:23 2020 DistUpgraded: 2020-01-31 09:33:31,151 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Ellesmere [Radeon RX 470/480/570/570X/580/580X/590] [1002:67df] (rev cf) (prog-if 00 [VGA controller]) Subsystem: XFX Pine Group Inc. Radeon RX 470 [1682:9470] InstallationDate: Installed on 2017-04-21 (1052 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Beta amd64 (20170404) MachineType: Micro-Star International Co., Ltd. MS-7A34 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-14-generic root=UUID=1bf886cb-50ea-4487-a660-07d91bbb51fc ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to focal on 2020-01-31 (37 days ago) dmi.bios.date: 01/23/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.M0 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B350 TOMAHAWK (MS-7A34) dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: 1.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.M0:bd01/23/2019:svnMicro-StarInternationalCo.,Ltd.:pnMS-7A34:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnB350TOMAHAWK(MS-7A34):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7A34 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.100-4 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.0-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.0-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.7-2ubuntu2 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+git20190815-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 xserver.bootTime: Mon Oct 15 10:44:00 2018 xserver.configfile: default xserver.errors: open /dev/dri/card0: No such file or directory open /dev/dri/card0: No such file or directory Screen 0 deleted because of no matching config section. xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.20.1-3ubuntu2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1866616/+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 1866303] Re: slapd crash with pwdAccountLockedTime and stacked overlays
** Merge proposal linked: https://code.launchpad.net/~ahasenack/ubuntu/+source/openldap/+git/openldap/+merge/380368 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openldap in Ubuntu. https://bugs.launchpad.net/bugs/1866303 Title: slapd crash with pwdAccountLockedTime and stacked overlays Status in openldap package in Ubuntu: In Progress Status in openldap source package in Xenial: New Status in openldap source package in Bionic: New Status in openldap source package in Disco: New Status in openldap source package in Eoan: New Status in openldap package in Debian: Unknown Bug description: Hello, Please merge openldap 2.4.49+dfsg-2 from Debian unstable to fix an issue in the ppolicy overlay that can crash slapd. Please also consider SRUing the patch after it has had some testing time. Upstream: https://openldap.org/its/?findid=9171 Debian: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=953150 The ingredients for the crash are: 1: ppolicy overlay configured with pwdLockout: TRUE 2. smbk5pwd overlay stacked after ppolicy 3. an account locked out via pwdAccountLockedTime 4. a client binding to the locked-out account and also requesting the ppolicy control The buggy code is not as specific as the above steps, so I suspect there are probably other configurations or steps that can trigger the same crash. I will attach my test script and data for reproducing the crash. Expected output (last lines): [ ok ] Starting OpenLDAP: slapd. slapd running ldap_bind: Invalid credentials (49) slapd running Actual output (last lines): [ ok ] Starting OpenLDAP: slapd. slapd running ldap_bind: Invalid credentials (49) slapd dead To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openldap/+bug/1866303/+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 1866351] Re: package openssh-server 1:7.2p2-4ubuntu2.8 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
Thank you for taking the time to report this bug and helping to make Ubuntu better. Since it seems likely to me that this is a local configuration problem, rather than a bug in Ubuntu, I'm marking this bug as Incomplete. If indeed this is a local configuration problem, you can find pointers to get help for this sort of problem here: http://www.ubuntu.com/support/community Or if you believe that this is really a bug, then you may find it helpful to read "How to report bugs effectively" http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be grateful if you would then provide a more complete description of the problem, explain why you believe this is a bug in Ubuntu rather than a problem specific to your system, and then change the bug status back to New. ** Changed in: openssh (Ubuntu) Status: New => Incomplete -- 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/1866351 Title: package openssh-server 1:7.2p2-4ubuntu2.8 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 Status in openssh package in Ubuntu: Incomplete Bug description: OK Hope it is not too serious a problem ProblemType: Package DistroRelease: Ubuntu 16.04 Package: openssh-server 1:7.2p2-4ubuntu2.8 ProcVersionSignature: Ubuntu 4.4.0-173.203-generic 4.4.208 Uname: Linux 4.4.0-173-generic i686 ApportVersion: 2.20.1-0ubuntu2.21 Architecture: i386 Date: Fri Mar 6 08:22:31 2020 DpkgHistoryLog: Start-Date: 2020-03-06 08:21:40 Commandline: aptdaemon role='role-commit-packages' sender=':1.53' Upgrade: libsasl2-modules-db:i386 (2.1.26.dfsg1-14ubuntu0.1, 2.1.26.dfsg1-14ubuntu0.2), openjdk-8-jre:i386 (8u232-b09-0ubuntu1~16.04.1, 8u242-b08-0ubuntu3~16.04), libsasl2-2:i386 (2.1.26.dfsg1-14ubuntu0.1, 2.1.26.dfsg1-14ubuntu0.2), libsasl2-modules:i386 (2.1.26.dfsg1-14ubuntu0.1, 2.1.26.dfsg1-14ubuntu0.2), firefox-locale-en:i386 (72.0.1+build1-0ubuntu0.16.04.1, 73.0.1+build1-0ubuntu0.16.04.1), openjdk-8-jre-headless:i386 (8u232-b09-0ubuntu1~16.04.1, 8u242-b08-0ubuntu3~16.04), firefox:i386 (72.0.1+build1-0ubuntu0.16.04.1, 73.0.1+build1-0ubuntu0.16.04.1) ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationDate: Installed on 2017-05-18 (1022 days ago) InstallationMedia: Custom 14.04 - Release i386 RelatedPackageVersions: dpkg 1.18.4ubuntu1.6 apt 1.2.32 SourcePackage: openssh Title: package openssh-server 1:7.2p2-4ubuntu2.8 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: Upgraded to xenial on 2018-10-11 (512 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1866351/+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 1866625] [NEW] OverflowError: With Python 3 Gtk.ListStore only accepts 32 Bit Integers.
Public bug reported:
import gi
gi.require_version('Gtk', '3.0')
from gi.repository import Gtk
This works in Python 2:
mystore = Gtk.ListStore(long)
mystore.insert_with_valuesv(-1, [1], [long(1330400507426)])
This does not work in Python 3:
mystore = Gtk.ListStore(int)
mystore.insert_with_valuesv(-1, [1], [int(1330400507426)])
OverflowError: Item 0: out of range for int property
lsb_release -rd
Description:Ubuntu 18.04.4 LTS
Release:18.04
apt-cache policy python3-gi
python3-gi:
Installed: 3.26.1-2ubuntu1
Candidate: 3.26.1-2ubuntu1
Version table:
*** 3.26.1-2ubuntu1 500
500 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages
100 /var/lib/dpkg/status
3.26.1-2 500
500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages
python3 -V
Python 3.6.9
** Affects: pygobject (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pygobject in Ubuntu.
https://bugs.launchpad.net/bugs/1866625
Title:
OverflowError: With Python 3 Gtk.ListStore only accepts 32 Bit
Integers.
Status in pygobject package in Ubuntu:
New
Bug description:
import gi
gi.require_version('Gtk', '3.0')
from gi.repository import Gtk
This works in Python 2:
mystore = Gtk.ListStore(long)
mystore.insert_with_valuesv(-1, [1], [long(1330400507426)])
This does not work in Python 3:
mystore = Gtk.ListStore(int)
mystore.insert_with_valuesv(-1, [1], [int(1330400507426)])
OverflowError: Item 0: out of range for int property
lsb_release -rd
Description: Ubuntu 18.04.4 LTS
Release: 18.04
apt-cache policy python3-gi
python3-gi:
Installed: 3.26.1-2ubuntu1
Candidate: 3.26.1-2ubuntu1
Version table:
*** 3.26.1-2ubuntu1 500
500 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64
Packages
100 /var/lib/dpkg/status
3.26.1-2 500
500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages
python3 -V
Python 3.6.9
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pygobject/+bug/1866625/+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 1866303] Re: slapd crash with pwdAccountLockedTime and stacked overlays
** Tags added: server-next -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openldap in Ubuntu. https://bugs.launchpad.net/bugs/1866303 Title: slapd crash with pwdAccountLockedTime and stacked overlays Status in openldap package in Ubuntu: In Progress Status in openldap source package in Xenial: New Status in openldap source package in Bionic: New Status in openldap source package in Disco: New Status in openldap source package in Eoan: New Status in openldap package in Debian: Unknown Bug description: Hello, Please merge openldap 2.4.49+dfsg-2 from Debian unstable to fix an issue in the ppolicy overlay that can crash slapd. Please also consider SRUing the patch after it has had some testing time. Upstream: https://openldap.org/its/?findid=9171 Debian: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=953150 The ingredients for the crash are: 1: ppolicy overlay configured with pwdLockout: TRUE 2. smbk5pwd overlay stacked after ppolicy 3. an account locked out via pwdAccountLockedTime 4. a client binding to the locked-out account and also requesting the ppolicy control The buggy code is not as specific as the above steps, so I suspect there are probably other configurations or steps that can trigger the same crash. I will attach my test script and data for reproducing the crash. Expected output (last lines): [ ok ] Starting OpenLDAP: slapd. slapd running ldap_bind: Invalid credentials (49) slapd running Actual output (last lines): [ ok ] Starting OpenLDAP: slapd. slapd running ldap_bind: Invalid credentials (49) slapd dead To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openldap/+bug/1866303/+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 1866611] Re: OpenVPN w. SHA1 signed CA broken after upgrade to 1.1.1d-2ubuntu6
This seems to have been caused by the patch 0180-Stop-accepting- certificates-signed-using-SHA1-at-sec.patch. I've re-built 1.1.1c-1ubuntu4 (apt source openssl; cd openssl1.1.1c; dpkg-buildpackage --no-sign; sudo apt install ../libssl1.1_1.1.1c- 1ubuntu4_amd64.deb), which makes my VPN work again. I've tried putting different things into /etc/ssl/openssl.conf, but `CipherString = DEFAULT:@SECLEVEL=0` (or any variation I can think of) makes it work. -- 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/1866611 Title: OpenVPN w. SHA1 signed CA broken after upgrade to 1.1.1d-2ubuntu6 Status in openssl package in Ubuntu: New Bug description: After upgrading openssl on my Focal-install this morning (upgrade openssl:amd64 1.1.1d-2ubuntu3 1.1.1d-2ubuntu6 per /var/log/dpkg.log), my OpenVPN tunnel refuses to connect to our corporate VPN (from /var/log/syslog): corp-laptop nm-openvpn[4688]: VERIFY ERROR: depth=0, error=CA signature digest algorithm too weak: C=DK, ST=None, L=Copenhagen, O=XX, OU=XX, CN=XX, emailAddress=XX corp-laptop nm-openvpn[4688]: OpenSSL: error:1416F086:SSL routines:tls_process_server_certificate:certificate verify failed I'm told we're running a SHA1-signed CA, which we're guessing has been deprecated somewhere between -2ubuntu3 and -2ubuntu6. The changelog for -2ubuntu4 mentions importing some upstream changes, but isn't more specific than that: https://changelogs.ubuntu.com/changelogs/pool/main/o/openssl/openssl_1.1 .1d-2ubuntu4/changelog As a work-around, the internet suggests two work-arounds (neither of which has worked for me): 1) Adding the following to /etc/defaults/openssl: OPTARGS="--tls-cipher DEFAULT:@SECLEVEL=0" 2) Adding the following to /etc/ssl/openssl.conf: CipherString= :@SECLEVEL=1 I also tried rolling back the package, but the old version doesn't seem to be available: $ sudo apt install openssl=1.1.1d-2ubuntu3 ... E: Version '1.1.1d-2ubuntu3' for 'openssl' was not found I am no SSL-expert and would appreciate any pointers to get around this. (Our network-dept. does not have the bandwidth to roll over our CA on short notice, so I will need some other way to move ahead). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1866611/+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 1866616] Re: 2nd display stopped working
The log shows "open /dev/dri/card0: No such file or directory" but it does exist: $ ls -l /dev/dri/card0 crw-rw+ 1 root render 226, 0 Mar 9 06:12 /dev/dri/card0 Unplugging the display from DVI-D-0 and plugging it back in does not result in showing up in xrandr output. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1866616 Title: 2nd display stopped working Status in xorg package in Ubuntu: New Bug description: The 2nd display (attached to DVI) has stopped being detected but is used by bios and grub (output ceases once the spinning boot animation starts). I was away for a week but it was working prior to leaving. I've notices that Xorg.0.log shows DVI-D-0 disconnected where the 2nd monitor should be. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18 Uname: Linux 5.4.0-14-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu18 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Mar 9 06:13:23 2020 DistUpgraded: 2020-01-31 09:33:31,151 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Ellesmere [Radeon RX 470/480/570/570X/580/580X/590] [1002:67df] (rev cf) (prog-if 00 [VGA controller]) Subsystem: XFX Pine Group Inc. Radeon RX 470 [1682:9470] InstallationDate: Installed on 2017-04-21 (1052 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Beta amd64 (20170404) MachineType: Micro-Star International Co., Ltd. MS-7A34 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-14-generic root=UUID=1bf886cb-50ea-4487-a660-07d91bbb51fc ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to focal on 2020-01-31 (37 days ago) dmi.bios.date: 01/23/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.M0 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B350 TOMAHAWK (MS-7A34) dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: 1.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.M0:bd01/23/2019:svnMicro-StarInternationalCo.,Ltd.:pnMS-7A34:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnB350TOMAHAWK(MS-7A34):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7A34 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.100-4 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.0-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.0-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.7-2ubuntu2 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+git20190815-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 xserver.bootTime: Mon Oct 15 10:44:00 2018 xserver.configfile: default xserver.errors: open /dev/dri/card0: No such file or directory open /dev/dri/card0: No such file or directory Screen 0 deleted because of no matching config section. xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.20.1-3ubuntu2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1866616/+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 1866616] [NEW] 2nd display stopped working
Public bug reported: The 2nd display (attached to DVI) has stopped being detected but is used by bios and grub (output ceases once the spinning boot animation starts). I was away for a week but it was working prior to leaving. I've notices that Xorg.0.log shows DVI-D-0 disconnected where the 2nd monitor should be. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18 Uname: Linux 5.4.0-14-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu18 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Mar 9 06:13:23 2020 DistUpgraded: 2020-01-31 09:33:31,151 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Ellesmere [Radeon RX 470/480/570/570X/580/580X/590] [1002:67df] (rev cf) (prog-if 00 [VGA controller]) Subsystem: XFX Pine Group Inc. Radeon RX 470 [1682:9470] InstallationDate: Installed on 2017-04-21 (1052 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Beta amd64 (20170404) MachineType: Micro-Star International Co., Ltd. MS-7A34 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-14-generic root=UUID=1bf886cb-50ea-4487-a660-07d91bbb51fc ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to focal on 2020-01-31 (37 days ago) dmi.bios.date: 01/23/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.M0 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B350 TOMAHAWK (MS-7A34) dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: 1.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.M0:bd01/23/2019:svnMicro-StarInternationalCo.,Ltd.:pnMS-7A34:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnB350TOMAHAWK(MS-7A34):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7A34 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.100-4 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.0-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.0-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.7-2ubuntu2 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+git20190815-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 xserver.bootTime: Mon Oct 15 10:44:00 2018 xserver.configfile: default xserver.errors: open /dev/dri/card0: No such file or directory open /dev/dri/card0: No such file or directory Screen 0 deleted because of no matching config section. xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.20.1-3ubuntu2 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug champagne focal regression reproducible ubuntu ** Description changed: The 2nd display (attached to DVI) has stopped being detected but is used by bios and grub (output ceases once the spinning boot animation starts). I was away for a week but it was working prior to leaving. - I've notices that Xorg.0.log shows fbdev rather than amdgpu in use (as - it had in the past). + I've notices that Xorg.0.log shows DVI-D-0 disconnected where the 2nd + monitor should be. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18 Uname: Linux 5.4.0-14-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu18 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Mar 9 06:13:23 2020 DistUpgraded: 2020-01-31 09:33:31,151 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: - Advanced Micro Devices, Inc. [AMD/ATI] Ellesmere [Radeon RX 470/480/570/570X/580/580X/590] [1002:67df] (rev cf) (prog-if 00 [VGA controller]) -Subsystem: XFX Pine Group Inc. Radeon RX 470 [1682:9470] + Advanced Micro Devices, Inc. [AMD/ATI] Ellesmere [Radeon RX 470/480/570/570X/580/580X/590] [1002:67df] (rev cf) (prog-if 00 [VGA controller]) + Subsystem: XFX Pine Group Inc. Radeon RX 470 [1682:9470] InstallationDate: Installed on 2017-04-21 (1052 days ago) InstallationMedia:
[Touch-packages] [Bug 1866012] Re: depmod ERROR during Setting up linux-modules-5.4.0-17-generic
** Tags added: champagne -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to kmod in Ubuntu. https://bugs.launchpad.net/bugs/1866012 Title: depmod ERROR during Setting up linux-modules-5.4.0-17-generic Status in kmod package in Ubuntu: New Status in linux package in Ubuntu: Invalid Bug description: Steps to reproduce: 1. Deploy Focal on a KVM ndoe, enable proposed 2. Run sudo apt dist-upgrade The console will be flushed with: Setting up libisc1105:amd64 (1:9.11.16+dfsg-3~build1) ... Setting up linux-modules-5.4.0-17-generic (5.4.0-17.21) ... depmod: ERROR: ../libkmod/libkmod.c:515 lookup_builtin_file() could not open builtin file '/lib/modules/5.4.0-17-generic/modules.builtin.bin' depmod: ERROR: ../libkmod/libkmod.c:515 lookup_builtin_file() could not open builtin file '/lib/modules/5.4.0-17-generic/modules.builtin.bin' depmod: ERROR: ../libkmod/libkmod.c:515 lookup_builtin_file() could not open builtin file '/lib/modules/5.4.0-17-generic/modules.builtin.bin' depmod: ERROR: ../libkmod/libkmod.c:515 lookup_builtin_file() could not open builtin file '/lib/modules/5.4.0-17-generic/modules.builtin.bin' depmod: ERROR: ../libkmod/libkmod.c:515 lookup_builtin_file() could not open builtin file '/lib/modules/5.4.0-17-generic/modules.builtin.bin' Setting up apt-utils (1.9.12) ... Setting up libselinux1-dev:amd64 (3.0-1build2) ... Setting up libglib2.0-0:amd64 (2.64.0-1) ... ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-14-generic 5.4.0-14.17 ProcVersionSignature: User Name 5.4.0-14.17-generic 5.4.18 Uname: Linux 5.4.0-14-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Mar 4 08:29 seq crw-rw 1 root audio 116, 33 Mar 4 08:29 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu18 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Wed Mar 4 09:06:42 2020 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Lsusb-t: /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M MachineType: QEMU Standard PC (i440FX + PIIX, 1996) PciMultimedia: ProcFB: 0 cirrusdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-14-generic root=UUID=36e162f3-41b5-4487-a6dc-09ba4e37d3bf ro console=tty1 console=ttyS0 RelatedPackageVersions: linux-restricted-modules-5.4.0-14-generic N/A linux-backports-modules-5.4.0-14-generic N/A linux-firmware1.186 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux-5.4 StagingDrivers: exfat UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: 1.10.2-1ubuntu1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-bionic dmi.modalias: dmi:bvnSeaBIOS:bvr1.10.2-1ubuntu1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-bionic:cvnQEMU:ct1:cvrpc-i440fx-bionic: dmi.product.name: Standard PC (i440FX + PIIX, 1996) dmi.product.version: pc-i440fx-bionic dmi.sys.vendor: QEMU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kmod/+bug/1866012/+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 1866611] [NEW] OpenVPN w. SHA1 signed CA broken after upgrade to 1.1.1d-2ubuntu6
Public bug reported: After upgrading openssl on my Focal-install this morning (upgrade openssl:amd64 1.1.1d-2ubuntu3 1.1.1d-2ubuntu6 per /var/log/dpkg.log), my OpenVPN tunnel refuses to connect to our corporate VPN (from /var/log/syslog): corp-laptop nm-openvpn[4688]: VERIFY ERROR: depth=0, error=CA signature digest algorithm too weak: C=DK, ST=None, L=Copenhagen, O=XX, OU=XX, CN=XX, emailAddress=XX corp-laptop nm-openvpn[4688]: OpenSSL: error:1416F086:SSL routines:tls_process_server_certificate:certificate verify failed I'm told we're running a SHA1-signed CA, which we're guessing has been deprecated somewhere between -2ubuntu3 and -2ubuntu6. The changelog for -2ubuntu4 mentions importing some upstream changes, but isn't more specific than that: https://changelogs.ubuntu.com/changelogs/pool/main/o/openssl/openssl_1.1 .1d-2ubuntu4/changelog As a work-around, the internet suggests two work-arounds (neither of which has worked for me): 1) Adding the following to /etc/defaults/openssl: OPTARGS="--tls-cipher DEFAULT:@SECLEVEL=0" 2) Adding the following to /etc/ssl/openssl.conf: CipherString= :@SECLEVEL=1 I also tried rolling back the package, but the old version doesn't seem to be available: $ sudo apt install openssl=1.1.1d-2ubuntu3 ... E: Version '1.1.1d-2ubuntu3' for 'openssl' was not found I am no SSL-expert and would appreciate any pointers to get around this. (Our network-dept. does not have the bandwidth to roll over our CA on short notice, so I will need some other way to move ahead). ** Affects: openssl (Ubuntu) Importance: Undecided Status: New ** Tags: openvpn sha1 ** Tags added: openvpn ** Tags added: sha1 -- 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/1866611 Title: OpenVPN w. SHA1 signed CA broken after upgrade to 1.1.1d-2ubuntu6 Status in openssl package in Ubuntu: New Bug description: After upgrading openssl on my Focal-install this morning (upgrade openssl:amd64 1.1.1d-2ubuntu3 1.1.1d-2ubuntu6 per /var/log/dpkg.log), my OpenVPN tunnel refuses to connect to our corporate VPN (from /var/log/syslog): corp-laptop nm-openvpn[4688]: VERIFY ERROR: depth=0, error=CA signature digest algorithm too weak: C=DK, ST=None, L=Copenhagen, O=XX, OU=XX, CN=XX, emailAddress=XX corp-laptop nm-openvpn[4688]: OpenSSL: error:1416F086:SSL routines:tls_process_server_certificate:certificate verify failed I'm told we're running a SHA1-signed CA, which we're guessing has been deprecated somewhere between -2ubuntu3 and -2ubuntu6. The changelog for -2ubuntu4 mentions importing some upstream changes, but isn't more specific than that: https://changelogs.ubuntu.com/changelogs/pool/main/o/openssl/openssl_1.1 .1d-2ubuntu4/changelog As a work-around, the internet suggests two work-arounds (neither of which has worked for me): 1) Adding the following to /etc/defaults/openssl: OPTARGS="--tls-cipher DEFAULT:@SECLEVEL=0" 2) Adding the following to /etc/ssl/openssl.conf: CipherString= :@SECLEVEL=1 I also tried rolling back the package, but the old version doesn't seem to be available: $ sudo apt install openssl=1.1.1d-2ubuntu3 ... E: Version '1.1.1d-2ubuntu3' for 'openssl' was not found I am no SSL-expert and would appreciate any pointers to get around this. (Our network-dept. does not have the bandwidth to roll over our CA on short notice, so I will need some other way to move ahead). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1866611/+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 1859754] Re: add ucm to make alsa/sof driver work under PA (variants of Lenovo X1 Carbon 7th, Dell cnl and cml machines)
Hello Hui, or anyone else affected, Accepted alsa-lib into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/alsa- lib/1.1.3-5ubuntu0.4 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-bionic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Tags removed: verification-failed-bionic ** Tags added: verification-needed-bionic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-lib in Ubuntu. https://bugs.launchpad.net/bugs/1859754 Title: add ucm to make alsa/sof driver work under PA (variants of Lenovo X1 Carbon 7th, Dell cnl and cml machines) Status in HWE Next: New Status in alsa-lib package in Ubuntu: Fix Committed Status in alsa-lib source package in Bionic: Fix Committed Status in alsa-lib source package in Eoan: Fix Committed Bug description: This ucm is only for Eoan and Bionic, for focal and future versions, we plan to integrate the ucm2 instead of this ucm, and the ucm2 depends on the alsa-lib-1.2.1 and pluseaudio-v14, the ucm2 is under developing by the community, is not ready yet. [Impact] In the oem project, we have a couple of Lenovo and Dell machines which connect the digital mic to PCH directly, this design needs the new sound driver soc/sof, and this driver can't work under pulseaudio automatically, we need to integrate the ucm for the driver, then the sof dirver could work under pulseaudio and gnome. This ucm is maintained by intel audio team, and it is not upstreamed and will not be upstreamed, since the community is developing the ucm2 which is based on at least alsa-lib-1.2.1 and pulseaudio-v14.0 (still under developing), for bionic and eoan, we have to integrate this ucm since the alsa-lib version is too low. For focal and future version, we are going to integrate the ucm2 after the ucm2 is ready. This ucm is already verified in the oem project, now it is time to put it into the stock ubuntu. [Fix] These ucm files are backported from sof_ucm1 branch of https://github.com/thesofproject/alsa-ucm-conf.git [Test Case] Boot the eoan kernel or oem-osp1-bionic kernel, then check the log of pulseaudio, the ucm files are loaded successfully, then check the gnome-sound-setting, both output and input devices work well. [Regression Risk] Low, just add some new ucm files, and this will not affect other machines, and those new added ucm files are only used by specific machines which enable the sof driver. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1859754/+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 1859754] Re: add ucm to make alsa/sof driver work under PA (variants of Lenovo X1 Carbon 7th, Dell cnl and cml machines)
Hello Hui, or anyone else affected, Accepted alsa-lib into eoan-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/alsa- lib/1.1.9-0ubuntu1.2 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- eoan to verification-done-eoan. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-eoan. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Tags removed: verification-failed verification-failed-eoan ** Tags added: verification-needed verification-needed-eoan -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-lib in Ubuntu. https://bugs.launchpad.net/bugs/1859754 Title: add ucm to make alsa/sof driver work under PA (variants of Lenovo X1 Carbon 7th, Dell cnl and cml machines) Status in HWE Next: New Status in alsa-lib package in Ubuntu: Fix Committed Status in alsa-lib source package in Bionic: Fix Committed Status in alsa-lib source package in Eoan: Fix Committed Bug description: This ucm is only for Eoan and Bionic, for focal and future versions, we plan to integrate the ucm2 instead of this ucm, and the ucm2 depends on the alsa-lib-1.2.1 and pluseaudio-v14, the ucm2 is under developing by the community, is not ready yet. [Impact] In the oem project, we have a couple of Lenovo and Dell machines which connect the digital mic to PCH directly, this design needs the new sound driver soc/sof, and this driver can't work under pulseaudio automatically, we need to integrate the ucm for the driver, then the sof dirver could work under pulseaudio and gnome. This ucm is maintained by intel audio team, and it is not upstreamed and will not be upstreamed, since the community is developing the ucm2 which is based on at least alsa-lib-1.2.1 and pulseaudio-v14.0 (still under developing), for bionic and eoan, we have to integrate this ucm since the alsa-lib version is too low. For focal and future version, we are going to integrate the ucm2 after the ucm2 is ready. This ucm is already verified in the oem project, now it is time to put it into the stock ubuntu. [Fix] These ucm files are backported from sof_ucm1 branch of https://github.com/thesofproject/alsa-ucm-conf.git [Test Case] Boot the eoan kernel or oem-osp1-bionic kernel, then check the log of pulseaudio, the ucm files are loaded successfully, then check the gnome-sound-setting, both output and input devices work well. [Regression Risk] Low, just add some new ucm files, and this will not affect other machines, and those new added ucm files are only used by specific machines which enable the sof driver. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1859754/+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 1862846] Re: Crash and failure installing focal
This bug was fixed in the package util-linux - 2.34-0.1ubuntu2.3
---
util-linux (2.34-0.1ubuntu2.3) eoan; urgency=medium
* d/p/lsblk-force-to-print-PKNAME-for-partition.patch: fix regression
that lsblk doesn't print PKNAME column for partitions (LP: #1862846)
-- Mauricio Faria de Oliveira Thu, 20 Feb 2020
11:13:53 -0300
** Changed in: util-linux (Ubuntu Eoan)
Status: Fix Committed => Fix Released
--
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/1862846
Title:
Crash and failure installing focal
Status in subiquity:
New
Status in curtin package in Ubuntu:
Fix Released
Status in util-linux package in Ubuntu:
Fix Released
Status in curtin source package in Eoan:
Invalid
Status in util-linux source package in Eoan:
Fix Released
Status in curtin source package in Focal:
Fix Released
Status in util-linux source package in Focal:
Fix Released
Status in util-linux package in Debian:
New
Bug description:
[Impact]
* lsblk no longer prints a partition's parent
kernel device name (the wholedisk).
(i.e., 'lsblk -no PKNAME /dev/partition')
* Another impact is the 'removable media' check
always return zero for partitions.
(i.e., 'lsblk -no RM /dev/partition')
* The regression was introduced on v2.34, only
Eoan (v2.34) and later are affected.
Disco (v2.33) and earlier are not affected.
* The regression is fixed in v2.35, in commit
e3bb9bfb76c1 ("lsblk: force to print PKNAME
for partition"); fixes RM for partition too.
[Test Case]
* $ lsblk -no PKNAME /dev/vda1 # partition
* Expected output: vda # wholedisk
* Current output: (nothing)
* $ lsblk -no RM /dev/sdb1 # partition in removable disk
* Expected output: 1 # removable media
* Current output: 0 # not removable media
[Regression Potential]
* Columns that depend on a partition device's
parent device (i.e., seen as 'wholedisk')
could in theory show incorrect values if
another bug is present in v2.34 for that.
* Other usages of 'parent' pointer in the
function have been examined and reported
(e.g. issue w/ removable media column),
and others found to not have issues
(e.g. --merge option, to group multiple
parents of a device, as in RAID.)
[Other Info]
* The impacts to the curtin source package
have been addressed in other way, it no
longer requires util-linux, comment #14.
* util-linux github issue:
https://github.com/karelzak/util-linux/issues/813
[Original Bug Description]
During an install of the daily live image for 20.04 Ubuntu Server, the
installer first crashed and restarted itself, then failed to install
the system.
Attached are the logs left on the install USB key.
To manage notifications about this bug go to:
https://bugs.launchpad.net/subiquity/+bug/1862846/+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 1862846] Update Released
The verification of the Stable Release Update for util-linux has
completed successfully and the package is now being released to
-updates. Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.
--
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/1862846
Title:
Crash and failure installing focal
Status in subiquity:
New
Status in curtin package in Ubuntu:
Fix Released
Status in util-linux package in Ubuntu:
Fix Released
Status in curtin source package in Eoan:
Invalid
Status in util-linux source package in Eoan:
Fix Released
Status in curtin source package in Focal:
Fix Released
Status in util-linux source package in Focal:
Fix Released
Status in util-linux package in Debian:
New
Bug description:
[Impact]
* lsblk no longer prints a partition's parent
kernel device name (the wholedisk).
(i.e., 'lsblk -no PKNAME /dev/partition')
* Another impact is the 'removable media' check
always return zero for partitions.
(i.e., 'lsblk -no RM /dev/partition')
* The regression was introduced on v2.34, only
Eoan (v2.34) and later are affected.
Disco (v2.33) and earlier are not affected.
* The regression is fixed in v2.35, in commit
e3bb9bfb76c1 ("lsblk: force to print PKNAME
for partition"); fixes RM for partition too.
[Test Case]
* $ lsblk -no PKNAME /dev/vda1 # partition
* Expected output: vda # wholedisk
* Current output: (nothing)
* $ lsblk -no RM /dev/sdb1 # partition in removable disk
* Expected output: 1 # removable media
* Current output: 0 # not removable media
[Regression Potential]
* Columns that depend on a partition device's
parent device (i.e., seen as 'wholedisk')
could in theory show incorrect values if
another bug is present in v2.34 for that.
* Other usages of 'parent' pointer in the
function have been examined and reported
(e.g. issue w/ removable media column),
and others found to not have issues
(e.g. --merge option, to group multiple
parents of a device, as in RAID.)
[Other Info]
* The impacts to the curtin source package
have been addressed in other way, it no
longer requires util-linux, comment #14.
* util-linux github issue:
https://github.com/karelzak/util-linux/issues/813
[Original Bug Description]
During an install of the daily live image for 20.04 Ubuntu Server, the
installer first crashed and restarted itself, then failed to install
the system.
Attached are the logs left on the install USB key.
To manage notifications about this bug go to:
https://bugs.launchpad.net/subiquity/+bug/1862846/+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 1866604] [NEW] gdbtui source window does't display Unicode text
Public bug reported:
In Ubuntu 20.04, I discovered that the gdb 9 TUI source code window
doesn't display properly the UTF-8 characters (Chinese, Cyrillic, etc.)
but displays correctly only the ASCII ones. For example, the following
source code
printf("Здравей, свят!\n");
appears in the source code window as
printf("^^P^ ^P^ ^Q^┗↑@^^P^ ^P^ ^P^ ^P^ ^^Q^┗↑╝^^P^ ^Q^ ^Q^ \n");
The command windows is not affected (when I type non-ASCII characters
into it, they appear OK).
Additionally, I found out the following:
(1) This bug was introduced in version 8.3;
(2) It affects only some CPU architectures.
In more detail, I tested version "Debian 8.3.1-1" on two 64-bit machines
with the same version of Debian (bullseye/sid), one with PowerPC, and
the other with SPARC. The bug shows up only on the SPARC machine, not
the PowerPC one. I then built the generic version 8.3.1 on a 64-bit ARM
machine. The bug didn't show up there. And then, I built it on a 64-bit
MIPS (big endian) machine, where the bug did show up. Repeated this with
version 8.3. The bug showed up again. When I built the generic version
8.2.1 on the same MIPS machine, the bug didn't show up. A "diff -u
gdb-8.2.1/gdb/tui gdb-8.3/gdb/tui" shows a lot of changes made in the
TUI code of version 8.3 to add some colourisation to the TUI, and the
bug was probably introduced during this process. Sorry that I can't help
more to isolate the bug. But it's quite strange that it manifests itself
only on x86-64 (as I had found out previously using Ubuntu 20-04), SPARC
and MIPS, but not on ARM and PowerPC. I suppose that because of this, it
will be rather hard to pinpoint.
This bug is similar to the already fixed bug 1275210 where I also
described it but then realised that it has a different origin and is
therefore a different bug, so I report it as a new one now. Someone
already reported this bug as bug 25296 in the gdb Bugzilla which I
confirmed there.
** Affects: gdb (Ubuntu)
Importance: Undecided
Status: New
** Tags: gdb gdbtui utf-8
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gdb in Ubuntu.
https://bugs.launchpad.net/bugs/1866604
Title:
gdbtui source window does't display Unicode text
Status in gdb package in Ubuntu:
New
Bug description:
In Ubuntu 20.04, I discovered that the gdb 9 TUI source code window
doesn't display properly the UTF-8 characters (Chinese, Cyrillic,
etc.) but displays correctly only the ASCII ones. For example, the
following source code
printf("Здравей, свят!\n");
appears in the source code window as
printf("^^P^ ^P^ ^Q^┗↑@^^P^ ^P^ ^P^ ^P^ ^^Q^┗↑╝^^P^ ^Q^ ^Q^ \n");
The command windows is not affected (when I type non-ASCII characters
into it, they appear OK).
Additionally, I found out the following:
(1) This bug was introduced in version 8.3;
(2) It affects only some CPU architectures.
In more detail, I tested version "Debian 8.3.1-1" on two 64-bit
machines with the same version of Debian (bullseye/sid), one with
PowerPC, and the other with SPARC. The bug shows up only on the SPARC
machine, not the PowerPC one. I then built the generic version 8.3.1
on a 64-bit ARM machine. The bug didn't show up there. And then, I
built it on a 64-bit MIPS (big endian) machine, where the bug did show
up. Repeated this with version 8.3. The bug showed up again. When I
built the generic version 8.2.1 on the same MIPS machine, the bug
didn't show up. A "diff -u gdb-8.2.1/gdb/tui gdb-8.3/gdb/tui" shows a
lot of changes made in the TUI code of version 8.3 to add some
colourisation to the TUI, and the bug was probably introduced during
this process. Sorry that I can't help more to isolate the bug. But
it's quite strange that it manifests itself only on x86-64 (as I had
found out previously using Ubuntu 20-04), SPARC and MIPS, but not on
ARM and PowerPC. I suppose that because of this, it will be rather
hard to pinpoint.
This bug is similar to the already fixed bug 1275210 where I also
described it but then realised that it has a different origin and is
therefore a different bug, so I report it as a new one now. Someone
already reported this bug as bug 25296 in the gdb Bugzilla which I
confirmed there.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdb/+bug/1866604/+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 1865517] Re: cannot log in with long username
By the way : user.lastnamelastnamelastn...@domain.fr does not trigger the bug. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pam in Ubuntu. https://bugs.launchpad.net/bugs/1865517 Title: cannot log in with long username Status in pam package in Ubuntu: Incomplete Bug description: We use ldap authentication with mail addresses as usernames. So usernames are not posix and some are > 32 chars but are working. Some of them fire a bug : When trying to log, it doesn't asks for password, it just wait some seconds then reset to ask username. I can't clearly identify which regex fire the bug or not but this one does "username.lastnamelastnamelastn...@domain.fr" I reproduce it on ubuntu 18.04 and 20.04 daylibuild. In auth.log, that line pops up when bug is started "Mar 2 16:23:14 premier agetty[97945]: checkname failed: Operation not permitted" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pam/+bug/1865517/+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 1865517] Re: cannot log in with long username
Just retried with fresh download of this file : http://cdimage.ubuntu.com/daily-live/current/focal-desktop-amd64.iso I confirm that entering on tty3 username.lastnamelastnamelastn...@domain.fr (not just "user.") does trigger the bug. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pam in Ubuntu. https://bugs.launchpad.net/bugs/1865517 Title: cannot log in with long username Status in pam package in Ubuntu: Incomplete Bug description: We use ldap authentication with mail addresses as usernames. So usernames are not posix and some are > 32 chars but are working. Some of them fire a bug : When trying to log, it doesn't asks for password, it just wait some seconds then reset to ask username. I can't clearly identify which regex fire the bug or not but this one does "username.lastnamelastnamelastn...@domain.fr" I reproduce it on ubuntu 18.04 and 20.04 daylibuild. In auth.log, that line pops up when bug is started "Mar 2 16:23:14 premier agetty[97945]: checkname failed: Operation not permitted" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pam/+bug/1865517/+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 1840416] Re: 2.4g wifi connection failed randomly during wpa re-key
per comment 1, the module tested is Network controller [0280]: Qualcomm Atheros QCA6174 802.11ac Wireless Network Adapter [168c:003e] ** Changed in: oem-priority Status: New => Confirmed ** Changed in: oem-priority Importance: Undecided => High -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1840416 Title: 2.4g wifi connection failed randomly during wpa re-key Status in OEM Priority Project: Confirmed Status in network-manager package in Ubuntu: New Bug description: I'm not sure this issue caused by WIFI AP or WIFI module. From log, it looks the tested machine can not get new key from WIFI AP randomly. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: network-manager 1.10.6-2ubuntu1.1 ProcVersionSignature: Ubuntu 4.15.0-1030.35-oem 4.15.18 Uname: Linux 4.15.0-1030-oem x86_64 ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Aug 16 14:51:12 2019 DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-bionic-amd64-20180608-47+italia-whl+X37 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2019-08-14 (2 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20180608-09:38 IpRoute: default via 10.101.46.1 dev wlp2s0 proto dhcp metric 600 10.101.46.0/24 dev wlp2s0 proto kernel scope link src 10.101.46.198 metric 600 169.254.0.0/16 dev wlp2s0 scope link metric 1000 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-con: NAMEUUID TYPE TIMESTAMP TIMESTAMP-REALAUTOCONNECT AUTOCONNECT-PRIORITY READONLY DBUS-PATH ACTIVE DEVICE STATE ACTIVE-PATH SLAVE Canonical-2.4GHz-g f0a4469e-23e9-4899-a498-49a50b3a8e21 wifi 1565938016 廿十九年八月十六日 (週五) 十四時46分56秒 yes 0 no /org/freedesktop/NetworkManager/Settings/1 yes wlp2s0 activated /org/freedesktop/NetworkManager/ActiveConnection/5 -- nmcli-dev: DEVICE TYPE STATE DBUS-PATH CONNECTION CON-UUID CON-PATH wlp2s0 wifi connected /org/freedesktop/NetworkManager/Devices/2 Canonical-2.4GHz-g f0a4469e-23e9-4899-a498-49a50b3a8e21 /org/freedesktop/NetworkManager/ActiveConnection/5 lo loopback unmanaged /org/freedesktop/NetworkManager/Devices/1 -- ---- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.10.6 connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1840416/+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 1757320] Re: Remove Qt 4 from the archive
Removing packages: qt4-x11 4:4.8.7+dfsg-20ubuntu2 in focal libqt4-dbg 4:4.8.7+dfsg-20ubuntu2 in focal amd64 libqt4-dbg 4:4.8.7+dfsg-20ubuntu2 in focal arm64 libqt4-dbg 4:4.8.7+dfsg-20ubuntu2 in focal armhf libqt4-dbg 4:4.8.7+dfsg-20ubuntu2 in focal i386 libqt4-dbg 4:4.8.7+dfsg-20ubuntu2 in focal ppc64el libqt4-dbg 4:4.8.7+dfsg-20ubuntu2 in focal s390x libqt4-dbus 4:4.8.7+dfsg-20ubuntu2 in focal amd64 libqt4-dbus 4:4.8.7+dfsg-20ubuntu2 in focal arm64 libqt4-dbus 4:4.8.7+dfsg-20ubuntu2 in focal armhf libqt4-dbus 4:4.8.7+dfsg-20ubuntu2 in focal i386 libqt4-dbus 4:4.8.7+dfsg-20ubuntu2 in focal ppc64el libqt4-dbus 4:4.8.7+dfsg-20ubuntu2 in focal s390x libqt4-declarative 4:4.8.7+dfsg-20ubuntu2 in focal amd64 libqt4-declarative 4:4.8.7+dfsg-20ubuntu2 in focal arm64 libqt4-declarative 4:4.8.7+dfsg-20ubuntu2 in focal armhf libqt4-declarative 4:4.8.7+dfsg-20ubuntu2 in focal i386 libqt4-declarative 4:4.8.7+dfsg-20ubuntu2 in focal ppc64el libqt4-declarative 4:4.8.7+dfsg-20ubuntu2 in focal s390x libqt4-declarative-folderlistmodel 4:4.8.7+dfsg-20ubuntu2 in focal amd64 libqt4-declarative-folderlistmodel 4:4.8.7+dfsg-20ubuntu2 in focal arm64 libqt4-declarative-folderlistmodel 4:4.8.7+dfsg-20ubuntu2 in focal armhf libqt4-declarative-folderlistmodel 4:4.8.7+dfsg-20ubuntu2 in focal i386 libqt4-declarative-folderlistmodel 4:4.8.7+dfsg-20ubuntu2 in focal ppc64el libqt4-declarative-folderlistmodel 4:4.8.7+dfsg-20ubuntu2 in focal s390x libqt4-declarative-gestures 4:4.8.7+dfsg-20ubuntu2 in focal amd64 libqt4-declarative-gestures 4:4.8.7+dfsg-20ubuntu2 in focal arm64 libqt4-declarative-gestures 4:4.8.7+dfsg-20ubuntu2 in focal armhf libqt4-declarative-gestures 4:4.8.7+dfsg-20ubuntu2 in focal i386 libqt4-declarative-gestures 4:4.8.7+dfsg-20ubuntu2 in focal ppc64el libqt4-declarative-gestures 4:4.8.7+dfsg-20ubuntu2 in focal s390x libqt4-declarative-particles 4:4.8.7+dfsg-20ubuntu2 in focal amd64 libqt4-declarative-particles 4:4.8.7+dfsg-20ubuntu2 in focal arm64 libqt4-declarative-particles 4:4.8.7+dfsg-20ubuntu2 in focal armhf libqt4-declarative-particles 4:4.8.7+dfsg-20ubuntu2 in focal i386 libqt4-declarative-particles 4:4.8.7+dfsg-20ubuntu2 in focal ppc64el libqt4-declarative-particles 4:4.8.7+dfsg-20ubuntu2 in focal s390x libqt4-declarative-shaders 4:4.8.7+dfsg-20ubuntu2 in focal amd64 libqt4-declarative-shaders 4:4.8.7+dfsg-20ubuntu2 in focal arm64 libqt4-declarative-shaders 4:4.8.7+dfsg-20ubuntu2 in focal armhf libqt4-declarative-shaders 4:4.8.7+dfsg-20ubuntu2 in focal i386 libqt4-declarative-shaders 4:4.8.7+dfsg-20ubuntu2 in focal ppc64el libqt4-declarative-shaders 4:4.8.7+dfsg-20ubuntu2 in focal s390x libqt4-designer 4:4.8.7+dfsg-20ubuntu2 in focal amd64 libqt4-designer 4:4.8.7+dfsg-20ubuntu2 in focal arm64 libqt4-designer 4:4.8.7+dfsg-20ubuntu2 in focal armhf libqt4-designer 4:4.8.7+dfsg-20ubuntu2 in focal i386 libqt4-designer 4:4.8.7+dfsg-20ubuntu2 in focal ppc64el libqt4-designer 4:4.8.7+dfsg-20ubuntu2 in focal s390x libqt4-designer-dbg 4:4.8.7+dfsg-20ubuntu2 in focal amd64 libqt4-designer-dbg 4:4.8.7+dfsg-20ubuntu2 in focal arm64 libqt4-designer-dbg 4:4.8.7+dfsg-20ubuntu2 in focal armhf libqt4-designer-dbg 4:4.8.7+dfsg-20ubuntu2 in focal i386 libqt4-designer-dbg 4:4.8.7+dfsg-20ubuntu2 in focal ppc64el libqt4-designer-dbg 4:4.8.7+dfsg-20ubuntu2 in focal s390x libqt4-dev 4:4.8.7+dfsg-20ubuntu2 in focal amd64 libqt4-dev 4:4.8.7+dfsg-20ubuntu2 in focal arm64 libqt4-dev 4:4.8.7+dfsg-20ubuntu2 in focal armhf libqt4-dev 4:4.8.7+dfsg-20ubuntu2 in focal i386 libqt4-dev 4:4.8.7+dfsg-20ubuntu2 in focal ppc64el libqt4-dev 4:4.8.7+dfsg-20ubuntu2 in focal s390x libqt4-dev-bin 4:4.8.7+dfsg-20ubuntu2 in focal amd64 libqt4-dev-bin 4:4.8.7+dfsg-20ubuntu2 in focal arm64 libqt4-dev-bin 4:4.8.7+dfsg-20ubuntu2 in focal armhf libqt4-dev-bin 4:4.8.7+dfsg-20ubuntu2 in focal i386 libqt4-dev-bin 4:4.8.7+dfsg-20ubuntu2 in focal ppc64el libqt4-dev-bin 4:4.8.7+dfsg-20ubuntu2 in focal s390x
