[Touch-packages] [Bug 2062031] [NEW] Periodically Sound intermittantly working on 24.04
Public bug reported: Hello, I have 24.04 development branch on my tower pc and I notice last night sometimes the sound doesnt work I ran journalctl and heres my log Apr 09 22:07:13 Tower-PC kernel: Linux version 6.5.0-27-generic (buildd@lcy02-a> Apr 09 22:07:13 Tower-PC kernel: Command line: BOOT_IMAGE=/boot/vmlinuz-6.5.0-2> Apr 09 22:07:13 Tower-PC kernel: KERNEL supported cpus: Apr 09 22:07:13 Tower-PC kernel: Intel GenuineIntel Apr 09 22:07:13 Tower-PC kernel: AMD AuthenticAMD Apr 09 22:07:13 Tower-PC kernel: Hygon HygonGenuine Apr 09 22:07:13 Tower-PC kernel: Centaur CentaurHauls Apr 09 22:07:13 Tower-PC kernel: zhaoxin Shanghai Apr 09 22:07:13 Tower-PC kernel: BIOS-provided physical RAM map: Apr 09 22:07:13 Tower-PC kernel: BIOS-e820: [mem 0x-0x0> Apr 09 22:07:13 Tower-PC kernel: BIOS-e820: [mem 0x0010-0xb> Apr 09 22:07:13 Tower-PC kernel: BIOS-e820: [mem 0xbae21000-0xb> Apr 09 22:07:13 Tower-PC kernel: BIOS-e820: [mem 0xbb10d000-0xb> Apr 09 22:07:13 Tower-PC kernel: BIOS-e820: [mem 0xbb11d000-0xb> Apr 09 22:07:13 Tower-PC kernel: BIOS-e820: [mem 0xbbe7b000-0xb> Apr 09 22:07:13 Tower-PC kernel: BIOS-e820: [mem 0xbca14000-0xb> Apr 09 22:07:13 Tower-PC kernel: BIOS-e820: [mem 0xbca15000-0xb> Apr 09 22:07:13 Tower-PC kernel: BIOS-e820: [mem 0xbcc18000-0xb> Apr 09 22:07:13 Tower-PC kernel: BIOS-e820: [mem 0xbd043000-0xb> Apr 09 22:07:13 Tower-PC kernel: BIOS-e820: [mem 0xbd7f4000-0xb> I suspect its a pulseaudio issue i had to install it yesterday bc it was a dependancy of another app so i will try uninstalling it. ** Affects: pulseaudio (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/2062031 Title: Periodically Sound intermittantly working on 24.04 Status in pulseaudio package in Ubuntu: New Bug description: Hello, I have 24.04 development branch on my tower pc and I notice last night sometimes the sound doesnt work I ran journalctl and heres my log Apr 09 22:07:13 Tower-PC kernel: Linux version 6.5.0-27-generic (buildd@lcy02-a> Apr 09 22:07:13 Tower-PC kernel: Command line: BOOT_IMAGE=/boot/vmlinuz-6.5.0-2> Apr 09 22:07:13 Tower-PC kernel: KERNEL supported cpus: Apr 09 22:07:13 Tower-PC kernel: Intel GenuineIntel Apr 09 22:07:13 Tower-PC kernel: AMD AuthenticAMD Apr 09 22:07:13 Tower-PC kernel: Hygon HygonGenuine Apr 09 22:07:13 Tower-PC kernel: Centaur CentaurHauls Apr 09 22:07:13 Tower-PC kernel: zhaoxin Shanghai Apr 09 22:07:13 Tower-PC kernel: BIOS-provided physical RAM map: Apr 09 22:07:13 Tower-PC kernel: BIOS-e820: [mem 0x-0x0> Apr 09 22:07:13 Tower-PC kernel: BIOS-e820: [mem 0x0010-0xb> Apr 09 22:07:13 Tower-PC kernel: BIOS-e820: [mem 0xbae21000-0xb> Apr 09 22:07:13 Tower-PC kernel: BIOS-e820: [mem 0xbb10d000-0xb> Apr 09 22:07:13 Tower-PC kernel: BIOS-e820: [mem 0xbb11d000-0xb> Apr 09 22:07:13 Tower-PC kernel: BIOS-e820: [mem 0xbbe7b000-0xb> Apr 09 22:07:13 Tower-PC kernel: BIOS-e820: [mem 0xbca14000-0xb> Apr 09 22:07:13 Tower-PC kernel: BIOS-e820: [mem 0xbca15000-0xb> Apr 09 22:07:13 Tower-PC kernel: BIOS-e820: [mem 0xbcc18000-0xb> Apr 09 22:07:13 Tower-PC kernel: BIOS-e820: [mem 0xbd043000-0xb> Apr 09 22:07:13 Tower-PC kernel: BIOS-e820: [mem 0xbd7f4000-0xb> I suspect its a pulseaudio issue i had to install it yesterday bc it was a dependancy of another app so i will try uninstalling it. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/2062031/+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 2017832] Re: No audio/sound after fresh 23.4 install, only dummy audio
Tried with the oldest and newest kernels available in mainline (6.0.0 and 6.3.0). Same problem. Same ipc errors in dmesg. -- 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/2017832 Title: No audio/sound after fresh 23.4 install, only dummy audio Status in alsa-driver package in Ubuntu: New Bug description: Did a fresh install of 23.4 and there is no working audio. Sound settings only show a "dummy output" audio device. If I plug headphones into the headphone jack, then a device shows up in sound settings: "Headphones - Tiger Lake-LP Smart Sound Technology Audio Controller". Then, if I try "test" and try to test the speakers, I hear nothing. If I open firefox and play a youtube video: 1. If I have headphones plugged in, I hear the audio over the internal speaker, not the headphones. 2. If I do not have the headphones plugged in, I hear nothing (dummy ouput in sound settings). Pipwire appears to be running: steve@steve-chromebook:~$ systemctl --user | grep wire pipewire-pulse.service loaded active running PipeWire PulseAudio pipewire.service loaded active running PipeWire Multimedia Service wireplumber.service loaded active running Multimedia Service Session Manager pipewire-pulse.socket loaded active running PipeWire PulseAudio pipewire.socket loaded active running PipeWire Multimedia System Socket Intel sound drivers appear to be running: $ lsmod | grep snd | grep intel snd_soc_intel_hda_dsp_common20480 1 snd_soc_sof_rt5682 snd_soc_intel_sof_maxim_common20480 1 snd_soc_sof_rt5682 snd_soc_intel_sof_realtek_common24576 1 snd_soc_sof_rt5682 snd_sof_pci_intel_tgl16384 0 snd_sof_intel_hda_common 188416 1 snd_sof_pci_intel_tgl soundwire_intel57344 1 snd_sof_intel_hda_common snd_sof_intel_hda 24576 1 snd_sof_intel_hda_common snd_sof_pci24576 2 snd_sof_intel_hda_common,snd_sof_pci_intel_tgl snd_sof_xtensa_dsp 16384 1 snd_sof_intel_hda_common snd_sof 311296 6 snd_soc_sof_rt5682,snd_sof_pci,snd_sof_intel_hda_common,snd_soc_intel_sof_realtek_common,snd_sof_probes,snd_sof_intel_hda snd_soc_hdac_hda 24576 1 snd_sof_intel_hda_common snd_hda_ext_core 36864 4 snd_sof_intel_hda_common,snd_soc_hdac_hdmi,snd_soc_hdac_hda,snd_sof_intel_hda snd_soc_acpi_intel_match77824 2 snd_sof_intel_hda_common,snd_sof_pci_intel_tgl snd_soc_acpi 16384 2 snd_soc_acpi_intel_match,snd_sof_intel_hda_common soundwire_bus 110592 5 regmap_sdw,soundwire_intel,soundwire_generic_allocation,soundwire_cadence,snd_soc_max98373_sdw snd_hda_intel 61440 0 snd_intel_dspcfg 36864 3 snd_hda_intel,snd_sof,snd_sof_intel_hda_common snd_intel_sdw_acpi 20480 2 snd_sof_intel_hda_common,snd_intel_dspcfg snd_soc_core 417792 16 snd_soc_max98373,snd_soc_sof_rt5682,snd_soc_rt5682,soundwire_intel,snd_sof,snd_sof_intel_hda_common,snd_soc_hdac_hdmi,snd_soc_intel_sof_realtek_common,snd_soc_hdac_hda,snd_soc_max98373_i2c,snd_soc_intel_sof_maxim_common,snd_soc_max98373_sdw,snd_sof_probes,snd_soc_dmic,snd_soc_rt5682s,snd_soc_rt5682_i2c snd_hda_codec 204800 5 snd_hda_codec_hdmi,snd_hda_intel,snd_soc_intel_hda_dsp_common,snd_soc_hdac_hda,snd_sof_intel_hda snd_hda_core 139264 9 snd_hda_codec_hdmi,snd_hda_intel,snd_hda_ext_core,snd_hda_codec,snd_soc_intel_hda_dsp_common,snd_sof_intel_hda_common,snd_soc_hdac_hdmi,snd_soc_hdac_hda,snd_sof_intel_hda snd_pcm 192512 18 snd_hda_codec_hdmi,snd_hda_intel,snd_soc_sof_rt5682,snd_soc_rt5682,snd_hda_codec,soundwire_intel,snd_sof,snd_sof_intel_hda_common,snd_soc_hdac_hdmi,snd_compress,snd_soc_intel_sof_realtek_common,snd_soc_max98373_i2c,snd_soc_core,snd_sof_utils,snd_soc_max98373_sdw,snd_hda_core,snd_soc_rt5682s,snd_pcm_dmaengine snd 135168 18 snd_seq,snd_seq_device,snd_hda_codec_hdmi,snd_hwdep,snd_hda_intel,snd_soc_sof_rt5682,snd_hda_codec,snd_sof,snd_timer,snd_soc_hdac_hdmi,snd_compress,snd_soc_core,snd_pcm,snd_rawmidi Alsa info is here: http://alsa-project.org/db/?f=ea6f792b4f92dd965494ec53df480554c50c4456 This info shows some errors in dmesg, but I have no idea if they are expected or indicate a problem. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: alsa-base
[Touch-packages] [Bug 2017832] Re: No audio/sound after fresh 23.4 install, only dummy audio
Attempted a variety of things that I found on the internet for similar problems: Various options to alsa-base.conf (tried them individually): /etc/modprobe.d/alsa-base.conf options snd-hda-intel model=auto options snd-hda-intel model=generic options snd_sof sof_debug=128 options snd_sof sof_debug=1 (also tried the last 2 in /etc/modprobe.d/sof.conf) Tried these via grub and also via alsa-base.conf options GRUB_CMDLINE_LINUX_DEFAULT="quiet splash snd_hda_intel.dmic_detect=0" or GRUB_CMDLINE_LINUX_DEFAULT="quiet splash snd_intel_dspcfg.dsp_driver=1 (and/or with different values, 0-3) No improvement with any of these experiments. -- 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/2017832 Title: No audio/sound after fresh 23.4 install, only dummy audio Status in alsa-driver package in Ubuntu: New Bug description: Did a fresh install of 23.4 and there is no working audio. Sound settings only show a "dummy output" audio device. If I plug headphones into the headphone jack, then a device shows up in sound settings: "Headphones - Tiger Lake-LP Smart Sound Technology Audio Controller". Then, if I try "test" and try to test the speakers, I hear nothing. If I open firefox and play a youtube video: 1. If I have headphones plugged in, I hear the audio over the internal speaker, not the headphones. 2. If I do not have the headphones plugged in, I hear nothing (dummy ouput in sound settings). Pipwire appears to be running: steve@steve-chromebook:~$ systemctl --user | grep wire pipewire-pulse.service loaded active running PipeWire PulseAudio pipewire.service loaded active running PipeWire Multimedia Service wireplumber.service loaded active running Multimedia Service Session Manager pipewire-pulse.socket loaded active running PipeWire PulseAudio pipewire.socket loaded active running PipeWire Multimedia System Socket Intel sound drivers appear to be running: $ lsmod | grep snd | grep intel snd_soc_intel_hda_dsp_common20480 1 snd_soc_sof_rt5682 snd_soc_intel_sof_maxim_common20480 1 snd_soc_sof_rt5682 snd_soc_intel_sof_realtek_common24576 1 snd_soc_sof_rt5682 snd_sof_pci_intel_tgl16384 0 snd_sof_intel_hda_common 188416 1 snd_sof_pci_intel_tgl soundwire_intel57344 1 snd_sof_intel_hda_common snd_sof_intel_hda 24576 1 snd_sof_intel_hda_common snd_sof_pci24576 2 snd_sof_intel_hda_common,snd_sof_pci_intel_tgl snd_sof_xtensa_dsp 16384 1 snd_sof_intel_hda_common snd_sof 311296 6 snd_soc_sof_rt5682,snd_sof_pci,snd_sof_intel_hda_common,snd_soc_intel_sof_realtek_common,snd_sof_probes,snd_sof_intel_hda snd_soc_hdac_hda 24576 1 snd_sof_intel_hda_common snd_hda_ext_core 36864 4 snd_sof_intel_hda_common,snd_soc_hdac_hdmi,snd_soc_hdac_hda,snd_sof_intel_hda snd_soc_acpi_intel_match77824 2 snd_sof_intel_hda_common,snd_sof_pci_intel_tgl snd_soc_acpi 16384 2 snd_soc_acpi_intel_match,snd_sof_intel_hda_common soundwire_bus 110592 5 regmap_sdw,soundwire_intel,soundwire_generic_allocation,soundwire_cadence,snd_soc_max98373_sdw snd_hda_intel 61440 0 snd_intel_dspcfg 36864 3 snd_hda_intel,snd_sof,snd_sof_intel_hda_common snd_intel_sdw_acpi 20480 2 snd_sof_intel_hda_common,snd_intel_dspcfg snd_soc_core 417792 16 snd_soc_max98373,snd_soc_sof_rt5682,snd_soc_rt5682,soundwire_intel,snd_sof,snd_sof_intel_hda_common,snd_soc_hdac_hdmi,snd_soc_intel_sof_realtek_common,snd_soc_hdac_hda,snd_soc_max98373_i2c,snd_soc_intel_sof_maxim_common,snd_soc_max98373_sdw,snd_sof_probes,snd_soc_dmic,snd_soc_rt5682s,snd_soc_rt5682_i2c snd_hda_codec 204800 5 snd_hda_codec_hdmi,snd_hda_intel,snd_soc_intel_hda_dsp_common,snd_soc_hdac_hda,snd_sof_intel_hda snd_hda_core 139264 9 snd_hda_codec_hdmi,snd_hda_intel,snd_hda_ext_core,snd_hda_codec,snd_soc_intel_hda_dsp_common,snd_sof_intel_hda_common,snd_soc_hdac_hdmi,snd_soc_hdac_hda,snd_sof_intel_hda snd_pcm 192512 18
[Touch-packages] [Bug 2017832] Re: No audio/sound after fresh 23.4 install, only dummy audio
I mean 22.04.2 LTS, not 22.03.2 LTS -- 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/2017832 Title: No audio/sound after fresh 23.4 install, only dummy audio Status in alsa-driver package in Ubuntu: New Bug description: Did a fresh install of 23.4 and there is no working audio. Sound settings only show a "dummy output" audio device. If I plug headphones into the headphone jack, then a device shows up in sound settings: "Headphones - Tiger Lake-LP Smart Sound Technology Audio Controller". Then, if I try "test" and try to test the speakers, I hear nothing. If I open firefox and play a youtube video: 1. If I have headphones plugged in, I hear the audio over the internal speaker, not the headphones. 2. If I do not have the headphones plugged in, I hear nothing (dummy ouput in sound settings). Pipwire appears to be running: steve@steve-chromebook:~$ systemctl --user | grep wire pipewire-pulse.service loaded active running PipeWire PulseAudio pipewire.service loaded active running PipeWire Multimedia Service wireplumber.service loaded active running Multimedia Service Session Manager pipewire-pulse.socket loaded active running PipeWire PulseAudio pipewire.socket loaded active running PipeWire Multimedia System Socket Intel sound drivers appear to be running: $ lsmod | grep snd | grep intel snd_soc_intel_hda_dsp_common20480 1 snd_soc_sof_rt5682 snd_soc_intel_sof_maxim_common20480 1 snd_soc_sof_rt5682 snd_soc_intel_sof_realtek_common24576 1 snd_soc_sof_rt5682 snd_sof_pci_intel_tgl16384 0 snd_sof_intel_hda_common 188416 1 snd_sof_pci_intel_tgl soundwire_intel57344 1 snd_sof_intel_hda_common snd_sof_intel_hda 24576 1 snd_sof_intel_hda_common snd_sof_pci24576 2 snd_sof_intel_hda_common,snd_sof_pci_intel_tgl snd_sof_xtensa_dsp 16384 1 snd_sof_intel_hda_common snd_sof 311296 6 snd_soc_sof_rt5682,snd_sof_pci,snd_sof_intel_hda_common,snd_soc_intel_sof_realtek_common,snd_sof_probes,snd_sof_intel_hda snd_soc_hdac_hda 24576 1 snd_sof_intel_hda_common snd_hda_ext_core 36864 4 snd_sof_intel_hda_common,snd_soc_hdac_hdmi,snd_soc_hdac_hda,snd_sof_intel_hda snd_soc_acpi_intel_match77824 2 snd_sof_intel_hda_common,snd_sof_pci_intel_tgl snd_soc_acpi 16384 2 snd_soc_acpi_intel_match,snd_sof_intel_hda_common soundwire_bus 110592 5 regmap_sdw,soundwire_intel,soundwire_generic_allocation,soundwire_cadence,snd_soc_max98373_sdw snd_hda_intel 61440 0 snd_intel_dspcfg 36864 3 snd_hda_intel,snd_sof,snd_sof_intel_hda_common snd_intel_sdw_acpi 20480 2 snd_sof_intel_hda_common,snd_intel_dspcfg snd_soc_core 417792 16 snd_soc_max98373,snd_soc_sof_rt5682,snd_soc_rt5682,soundwire_intel,snd_sof,snd_sof_intel_hda_common,snd_soc_hdac_hdmi,snd_soc_intel_sof_realtek_common,snd_soc_hdac_hda,snd_soc_max98373_i2c,snd_soc_intel_sof_maxim_common,snd_soc_max98373_sdw,snd_sof_probes,snd_soc_dmic,snd_soc_rt5682s,snd_soc_rt5682_i2c snd_hda_codec 204800 5 snd_hda_codec_hdmi,snd_hda_intel,snd_soc_intel_hda_dsp_common,snd_soc_hdac_hda,snd_sof_intel_hda snd_hda_core 139264 9 snd_hda_codec_hdmi,snd_hda_intel,snd_hda_ext_core,snd_hda_codec,snd_soc_intel_hda_dsp_common,snd_sof_intel_hda_common,snd_soc_hdac_hdmi,snd_soc_hdac_hda,snd_sof_intel_hda snd_pcm 192512 18 snd_hda_codec_hdmi,snd_hda_intel,snd_soc_sof_rt5682,snd_soc_rt5682,snd_hda_codec,soundwire_intel,snd_sof,snd_sof_intel_hda_common,snd_soc_hdac_hdmi,snd_compress,snd_soc_intel_sof_realtek_common,snd_soc_max98373_i2c,snd_soc_core,snd_sof_utils,snd_soc_max98373_sdw,snd_hda_core,snd_soc_rt5682s,snd_pcm_dmaengine snd 135168 18 snd_seq,snd_seq_device,snd_hda_codec_hdmi,snd_hwdep,snd_hda_intel,snd_soc_sof_rt5682,snd_hda_codec,snd_sof,snd_timer,snd_soc_hdac_hdmi,snd_compress,snd_soc_core,snd_pcm,snd_rawmidi Alsa info is here: http://alsa-project.org/db/?f=ea6f792b4f92dd965494ec53df480554c50c4456 This info shows some errors in dmesg, but I have no idea if they are expected or indicate a problem. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: alsa-base 1.0.25+dfsg-0ubuntu7 ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 Uname: Linux
[Touch-packages] [Bug 2017832] Re: No audio/sound after fresh 23.4 install, only dummy audio
Here is the dmesg log from 22.03.2 LTS. The sound works great on that release. There are no tx/HW params/AsoC errors as seen in dmesg with 23.04. [3.608109] sof-audio-pci-intel-tgl :00:1f.3: use msi interrupt mode [3.632029] sof-audio-pci-intel-tgl :00:1f.3: NHLT table not found [3.632076] sof-audio-pci-intel-tgl :00:1f.3: hda codecs found, mask 4 [3.633075] sof-audio-pci-intel-tgl :00:1f.3: Firmware info: version 2:0:0-b678a [3.633080] sof-audio-pci-intel-tgl :00:1f.3: Firmware: ABI 3:20:0 Kernel ABI 3:21:0 [3.633085] sof-audio-pci-intel-tgl :00:1f.3: unknown sof_ext_man header type 3 size 0x30 [3.727188] sof-audio-pci-intel-tgl :00:1f.3: Firmware info: version 2:0:0-b678a [3.727194] sof-audio-pci-intel-tgl :00:1f.3: Firmware: ABI 3:20:0 Kernel ABI 3:21:0 [3.755011] sof-audio-pci-intel-tgl :00:1f.3: Topology: ABI 3:20:0 Kernel ABI 3:21:0 [3.755271] sof_rt5682 tgl_mx98373_rt5682: ASoC: Parent card not yet available, widget card binding deferred [3.806335] snd_hda_codec_hdmi ehdaudio0D2: ASoC: sink widget AIF1TX overwritten [3.806345] snd_hda_codec_hdmi ehdaudio0D2: ASoC: source widget AIF1RX overwritten [3.818001] max98373 i2c-MX98373:00: Reset completed (retry:0) [3.832402] max98373 i2c-MX98373:01: Reset completed (retry:0) [3.859800] input: sof-rt5682 Headset Jack as /devices/pci:00/:00:1f.3/tgl_mx98373_rt5682/sound/card0/input9 [3.859880] input: sof-rt5682 HDMI/DP,pcm=2 as /devices/pci:00/:00:1f.3/tgl_mx98373_rt5682/sound/card0/input10 [3.859946] input: sof-rt5682 HDMI/DP,pcm=3 as /devices/pci:00/:00:1f.3/tgl_mx98373_rt5682/sound/card0/input11 [3.860059] input: sof-rt5682 HDMI/DP,pcm=4 as /devices/pci:00/:00:1f.3/tgl_mx98373_rt5682/sound/card0/input12 [3.860094] input: sof-rt5682 HDMI/DP,pcm=5 as /devices/pci:00/:00:1f.3/tgl_mx98373_rt5682/sound/card0/input13 -- 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/2017832 Title: No audio/sound after fresh 23.4 install, only dummy audio Status in alsa-driver package in Ubuntu: New Bug description: Did a fresh install of 23.4 and there is no working audio. Sound settings only show a "dummy output" audio device. If I plug headphones into the headphone jack, then a device shows up in sound settings: "Headphones - Tiger Lake-LP Smart Sound Technology Audio Controller". Then, if I try "test" and try to test the speakers, I hear nothing. If I open firefox and play a youtube video: 1. If I have headphones plugged in, I hear the audio over the internal speaker, not the headphones. 2. If I do not have the headphones plugged in, I hear nothing (dummy ouput in sound settings). Pipwire appears to be running: steve@steve-chromebook:~$ systemctl --user | grep wire pipewire-pulse.service loaded active running PipeWire PulseAudio pipewire.service loaded active running PipeWire Multimedia Service wireplumber.service loaded active running Multimedia Service Session Manager pipewire-pulse.socket loaded active running PipeWire PulseAudio pipewire.socket loaded active running PipeWire Multimedia System Socket Intel sound drivers appear to be running: $ lsmod | grep snd | grep intel snd_soc_intel_hda_dsp_common20480 1 snd_soc_sof_rt5682 snd_soc_intel_sof_maxim_common20480 1 snd_soc_sof_rt5682 snd_soc_intel_sof_realtek_common24576 1 snd_soc_sof_rt5682 snd_sof_pci_intel_tgl16384 0 snd_sof_intel_hda_common 188416 1 snd_sof_pci_intel_tgl soundwire_intel57344 1 snd_sof_intel_hda_common snd_sof_intel_hda 24576 1 snd_sof_intel_hda_common snd_sof_pci24576 2 snd_sof_intel_hda_common,snd_sof_pci_intel_tgl snd_sof_xtensa_dsp 16384 1 snd_sof_intel_hda_common snd_sof 311296 6 snd_soc_sof_rt5682,snd_sof_pci,snd_sof_intel_hda_common,snd_soc_intel_sof_realtek_common,snd_sof_probes,snd_sof_intel_hda snd_soc_hdac_hda 24576 1 snd_sof_intel_hda_common snd_hda_ext_core 36864 4 snd_sof_intel_hda_common,snd_soc_hdac_hdmi,snd_soc_hdac_hda,snd_sof_intel_hda snd_soc_acpi_intel_match77824 2 snd_sof_intel_hda_common,snd_sof_pci_intel_tgl snd_soc_acpi 16384 2 snd_soc_acpi_intel_match,snd_sof_intel_hda_common soundwire_bus
[Touch-packages] [Bug 2017832] Re: No audio/sound after fresh 23.4 install, only dummy audio
May be worth mentioning that I previously was running 22.04 LTS, and the sound worked just fine on initial install, and through all the updates. -- 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/2017832 Title: No audio/sound after fresh 23.4 install, only dummy audio Status in alsa-driver package in Ubuntu: New Bug description: Did a fresh install of 23.4 and there is no working audio. Sound settings only show a "dummy output" audio device. If I plug headphones into the headphone jack, then a device shows up in sound settings: "Headphones - Tiger Lake-LP Smart Sound Technology Audio Controller". Then, if I try "test" and try to test the speakers, I hear nothing. If I open firefox and play a youtube video: 1. If I have headphones plugged in, I hear the audio over the internal speaker, not the headphones. 2. If I do not have the headphones plugged in, I hear nothing (dummy ouput in sound settings). Pipwire appears to be running: steve@steve-chromebook:~$ systemctl --user | grep wire pipewire-pulse.service loaded active running PipeWire PulseAudio pipewire.service loaded active running PipeWire Multimedia Service wireplumber.service loaded active running Multimedia Service Session Manager pipewire-pulse.socket loaded active running PipeWire PulseAudio pipewire.socket loaded active running PipeWire Multimedia System Socket Intel sound drivers appear to be running: $ lsmod | grep snd | grep intel snd_soc_intel_hda_dsp_common20480 1 snd_soc_sof_rt5682 snd_soc_intel_sof_maxim_common20480 1 snd_soc_sof_rt5682 snd_soc_intel_sof_realtek_common24576 1 snd_soc_sof_rt5682 snd_sof_pci_intel_tgl16384 0 snd_sof_intel_hda_common 188416 1 snd_sof_pci_intel_tgl soundwire_intel57344 1 snd_sof_intel_hda_common snd_sof_intel_hda 24576 1 snd_sof_intel_hda_common snd_sof_pci24576 2 snd_sof_intel_hda_common,snd_sof_pci_intel_tgl snd_sof_xtensa_dsp 16384 1 snd_sof_intel_hda_common snd_sof 311296 6 snd_soc_sof_rt5682,snd_sof_pci,snd_sof_intel_hda_common,snd_soc_intel_sof_realtek_common,snd_sof_probes,snd_sof_intel_hda snd_soc_hdac_hda 24576 1 snd_sof_intel_hda_common snd_hda_ext_core 36864 4 snd_sof_intel_hda_common,snd_soc_hdac_hdmi,snd_soc_hdac_hda,snd_sof_intel_hda snd_soc_acpi_intel_match77824 2 snd_sof_intel_hda_common,snd_sof_pci_intel_tgl snd_soc_acpi 16384 2 snd_soc_acpi_intel_match,snd_sof_intel_hda_common soundwire_bus 110592 5 regmap_sdw,soundwire_intel,soundwire_generic_allocation,soundwire_cadence,snd_soc_max98373_sdw snd_hda_intel 61440 0 snd_intel_dspcfg 36864 3 snd_hda_intel,snd_sof,snd_sof_intel_hda_common snd_intel_sdw_acpi 20480 2 snd_sof_intel_hda_common,snd_intel_dspcfg snd_soc_core 417792 16 snd_soc_max98373,snd_soc_sof_rt5682,snd_soc_rt5682,soundwire_intel,snd_sof,snd_sof_intel_hda_common,snd_soc_hdac_hdmi,snd_soc_intel_sof_realtek_common,snd_soc_hdac_hda,snd_soc_max98373_i2c,snd_soc_intel_sof_maxim_common,snd_soc_max98373_sdw,snd_sof_probes,snd_soc_dmic,snd_soc_rt5682s,snd_soc_rt5682_i2c snd_hda_codec 204800 5 snd_hda_codec_hdmi,snd_hda_intel,snd_soc_intel_hda_dsp_common,snd_soc_hdac_hda,snd_sof_intel_hda snd_hda_core 139264 9 snd_hda_codec_hdmi,snd_hda_intel,snd_hda_ext_core,snd_hda_codec,snd_soc_intel_hda_dsp_common,snd_sof_intel_hda_common,snd_soc_hdac_hdmi,snd_soc_hdac_hda,snd_sof_intel_hda snd_pcm 192512 18 snd_hda_codec_hdmi,snd_hda_intel,snd_soc_sof_rt5682,snd_soc_rt5682,snd_hda_codec,soundwire_intel,snd_sof,snd_sof_intel_hda_common,snd_soc_hdac_hdmi,snd_compress,snd_soc_intel_sof_realtek_common,snd_soc_max98373_i2c,snd_soc_core,snd_sof_utils,snd_soc_max98373_sdw,snd_hda_core,snd_soc_rt5682s,snd_pcm_dmaengine snd 135168 18 snd_seq,snd_seq_device,snd_hda_codec_hdmi,snd_hwdep,snd_hda_intel,snd_soc_sof_rt5682,snd_hda_codec,snd_sof,snd_timer,snd_soc_hdac_hdmi,snd_compress,snd_soc_core,snd_pcm,snd_rawmidi Alsa info is here: http://alsa-project.org/db/?f=ea6f792b4f92dd965494ec53df480554c50c4456 This info shows some errors in dmesg, but I have no idea if they are expected or indicate a problem. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package:
[Touch-packages] [Bug 2017832] [NEW] No audio/sound after fresh 23.4 install, only dummy audio
Public bug reported: Did a fresh install of 23.4 and there is no working audio. Sound settings only show a "dummy output" audio device. If I plug headphones into the headphone jack, then a device shows up in sound settings: "Headphones - Tiger Lake-LP Smart Sound Technology Audio Controller". Then, if I try "test" and try to test the speakers, I hear nothing. If I open firefox and play a youtube video: 1. If I have headphones plugged in, I hear the audio over the internal speaker, not the headphones. 2. If I do not have the headphones plugged in, I hear nothing (dummy ouput in sound settings). Pipwire appears to be running: steve@steve-chromebook:~$ systemctl --user | grep wire pipewire-pulse.service loaded active running PipeWire PulseAudio pipewire.service loaded active running PipeWire Multimedia Service wireplumber.service loaded active running Multimedia Service Session Manager pipewire-pulse.socket loaded active running PipeWire PulseAudio pipewire.socket loaded active running PipeWire Multimedia System Socket Intel sound drivers appear to be running: $ lsmod | grep snd | grep intel snd_soc_intel_hda_dsp_common20480 1 snd_soc_sof_rt5682 snd_soc_intel_sof_maxim_common20480 1 snd_soc_sof_rt5682 snd_soc_intel_sof_realtek_common24576 1 snd_soc_sof_rt5682 snd_sof_pci_intel_tgl16384 0 snd_sof_intel_hda_common 188416 1 snd_sof_pci_intel_tgl soundwire_intel57344 1 snd_sof_intel_hda_common snd_sof_intel_hda 24576 1 snd_sof_intel_hda_common snd_sof_pci24576 2 snd_sof_intel_hda_common,snd_sof_pci_intel_tgl snd_sof_xtensa_dsp 16384 1 snd_sof_intel_hda_common snd_sof 311296 6 snd_soc_sof_rt5682,snd_sof_pci,snd_sof_intel_hda_common,snd_soc_intel_sof_realtek_common,snd_sof_probes,snd_sof_intel_hda snd_soc_hdac_hda 24576 1 snd_sof_intel_hda_common snd_hda_ext_core 36864 4 snd_sof_intel_hda_common,snd_soc_hdac_hdmi,snd_soc_hdac_hda,snd_sof_intel_hda snd_soc_acpi_intel_match77824 2 snd_sof_intel_hda_common,snd_sof_pci_intel_tgl snd_soc_acpi 16384 2 snd_soc_acpi_intel_match,snd_sof_intel_hda_common soundwire_bus 110592 5 regmap_sdw,soundwire_intel,soundwire_generic_allocation,soundwire_cadence,snd_soc_max98373_sdw snd_hda_intel 61440 0 snd_intel_dspcfg 36864 3 snd_hda_intel,snd_sof,snd_sof_intel_hda_common snd_intel_sdw_acpi 20480 2 snd_sof_intel_hda_common,snd_intel_dspcfg snd_soc_core 417792 16 snd_soc_max98373,snd_soc_sof_rt5682,snd_soc_rt5682,soundwire_intel,snd_sof,snd_sof_intel_hda_common,snd_soc_hdac_hdmi,snd_soc_intel_sof_realtek_common,snd_soc_hdac_hda,snd_soc_max98373_i2c,snd_soc_intel_sof_maxim_common,snd_soc_max98373_sdw,snd_sof_probes,snd_soc_dmic,snd_soc_rt5682s,snd_soc_rt5682_i2c snd_hda_codec 204800 5 snd_hda_codec_hdmi,snd_hda_intel,snd_soc_intel_hda_dsp_common,snd_soc_hdac_hda,snd_sof_intel_hda snd_hda_core 139264 9 snd_hda_codec_hdmi,snd_hda_intel,snd_hda_ext_core,snd_hda_codec,snd_soc_intel_hda_dsp_common,snd_sof_intel_hda_common,snd_soc_hdac_hdmi,snd_soc_hdac_hda,snd_sof_intel_hda snd_pcm 192512 18 snd_hda_codec_hdmi,snd_hda_intel,snd_soc_sof_rt5682,snd_soc_rt5682,snd_hda_codec,soundwire_intel,snd_sof,snd_sof_intel_hda_common,snd_soc_hdac_hdmi,snd_compress,snd_soc_intel_sof_realtek_common,snd_soc_max98373_i2c,snd_soc_core,snd_sof_utils,snd_soc_max98373_sdw,snd_hda_core,snd_soc_rt5682s,snd_pcm_dmaengine snd 135168 18 snd_seq,snd_seq_device,snd_hda_codec_hdmi,snd_hwdep,snd_hda_intel,snd_soc_sof_rt5682,snd_hda_codec,snd_sof,snd_timer,snd_soc_hdac_hdmi,snd_compress,snd_soc_core,snd_pcm,snd_rawmidi Alsa info is here: http://alsa-project.org/db/?f=ea6f792b4f92dd965494ec53df480554c50c4456 This info shows some errors in dmesg, but I have no idea if they are expected or indicate a problem. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: alsa-base 1.0.25+dfsg-0ubuntu7 ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 Uname: Linux 6.2.0-20-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: steve 1388 F wireplumber /dev/snd/seq:steve 1385 F pipewire CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Wed Apr 26 20:33:57 2023 InstallationDate: Installed on 2023-04-27 (0 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64
[Touch-packages] [Bug 2009526] Re: "find-dbgsym-packages /usr/bin/gio" command outputs errors
The package name was looked up with this command sequence: stephen@stephen:~$ which gio /usr/bin/gio stephen@stephen:~$ dpkg -S /usr/bin/gio libglib2.0-bin: /usr/bin/gio stephen@stephen:~$ ** Package changed: ubuntu => glib2.0 (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/2009526 Title: "find-dbgsym-packages /usr/bin/gio" command outputs errors Status in debian-goodies package in Ubuntu: New Bug description: I am not sure if this problem is caused by my not doing this right, a bug in gdb, a bug in gio, or a fault in the source libraries server. But after four days no one has an answer to this problem at my thread at: https://stackoverflow.com/questions/75620624/find-dbgsym-packages- usr-bin-gio-command-gets-errors . No one at the #ubuntu IRC channel responded. And so my strong suspicion this is actually a bug. The goal is the ability to step through gio's source code to follow its execution to find out why it is not working for me in my main account (account ID 1000), but does work in other accounts created susequently for testing. To get symbols, and source code, I followed the directions at: https://wiki.ubuntu.com/Debug%20Symbol%20Packages duginfod did not work on my Ubuntu 22.04 system. It was therefore necessary to do a manual download. I followed the directions under the heading "Getting -dbgsym.ddeb packages", and then "Automatic Resolution / Installation of necessary packages", on that page. All went well until the find-dbgsym-packages command. Here is the complete command, and the response I got: stephen@stephen:~$ find-dbgsym-packages /usr/bin/gio dpkg-query: no path found matching pattern /lib/x86_64-linux-gnu/libgmodule-2.0.so.0 W: Cannot find debug package for /lib/x86_64-linux-gnu/libgmodule-2.0.so.0 (991a9f61e69c30ef8ab73761c300ae51249ede63) dpkg-query: no path found matching pattern /lib/x86_64-linux-gnu/libglib-2.0.so.0 W: Cannot find debug package for /lib/x86_64-linux-gnu/libglib-2.0.so.0 (137458a0f7846a084270bf5bb03df075a578db6d) dpkg-query: no path found matching pattern /lib/x86_64-linux-gnu/libgobject-2.0.so.0 W: Cannot find debug package for /lib/x86_64-linux-gnu/libgobject-2.0.so.0 (44f60e584780daaeb1880ead5dd00f12ffd423d2) dpkg-query: no path found matching pattern /lib/x86_64-linux-gnu/libgio-2.0.so.0 W: Cannot find debug package for /lib/x86_64-linux-gnu/libgio-2.0.so.0 (9b52271b63917542ba10ffb8a82b97befd2c238f) dpkg-query: no path found matching pattern /lib/x86_64-linux-gnu/libpcre2-8.so.0 W: Cannot find debug package for /lib/x86_64-linux-gnu/libpcre2-8.so.0 (184a841c55fb7fe5e3873fcda8368c71016cd54c) libblkid1-dbgsym libffi8-dbgsym libglib2.0-bin-dbgsym libmount1-dbgsym libpcre3-dbg libselinux1-dbgsym zlib1g-dbgsym I interpret these errors to mean that the packages the find-dbgsym-packages command is seeking are not found, I think now, due to a bug somewhere. For the details regarding my need to step through code see this thread of mine: https://askubuntu.com/questions/1427431/how-to-set-a-launcher-as-trusted To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/debian-goodies/+bug/2009526/+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 2009564] [NEW] Touchpad disabling while typing does not work
Public bug reported: It makes my laptop much less usable. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.19.0-35.36~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-35-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 525.85.05 Sat Jan 14 00:49:50 UTC 2023 GCC version: gcc version 11.3.0 (Ubuntu 11.3.0-1ubuntu1~22.04) ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Mar 7 00:44:08 2023 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu DkmsStatus: backport-iwlwifi/9858, 5.19.0-32-generic, x86_64: installed (WARNING! Diff between built and installed module!) (WARNING! Diff between built and installed module!) (WARNING! Diff between built and installed module!) (WARNING! Diff between built and installed module!) (WARNING! Diff between built and installed module!) (WARNING! Diff between built and installed module!) backport-iwlwifi/9858, 5.19.0-35-generic, x86_64: installed (WARNING! Diff between built and installed module!) (WARNING! Diff between built and installed module!) (WARNING! Diff between built and installed module!) (WARNING! Diff between built and installed module!) (WARNING! Diff between built and installed module!) (WARNING! Diff between built and installed module!) nvidia/525.85.05, 5.15.0-56-generic, x86_64: installed nvidia/525.85.05, 5.19.0-32-generic, x86_64: installed nvidia/525.85.05, 5.19.0-35-generic, x86_64: installed ExtraDebuggingInterest: I just need to know a workaround GraphicsCard: Intel Corporation Alder Lake-P Integrated Graphics Controller [8086:46a6] (rev 0c) (prog-if 00 [VGA controller]) Subsystem: Razer USA Ltd. Device [1a58:201f] NVIDIA Corporation Device [10de:24e0] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Razer USA Ltd. Device [1a58:201f] InstallationDate: Installed on 2023-01-03 (62 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) MachineType: Razer x Lambda TensorBook (2022) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-35-generic root=UUID=4cd4fe61-a6ef-48c5-acc8-b96e7da91171 ro button.lid_init_state=open i915.enable_fbc=0 quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/29/2022 dmi.bios.release: 1.0 dmi.bios.vendor: Razer dmi.bios.version: 1.00 dmi.board.name: CH580 dmi.board.vendor: Razer x Lambda dmi.board.version: 4 dmi.chassis.type: 10 dmi.chassis.vendor: Razer x Lambda dmi.ec.firmware.release: 1.0 dmi.modalias: dmi:bvnRazer:bvr1.00:bd07/29/2022:br1.0:efr1.0:svnRazerxLambda:pnTensorBook(2022):pvr8.04:rvnRazerxLambda:rnCH580:rvr4:cvnRazerxLambda:ct10:cvr:skuRZ09-0421NEL9: dmi.product.family: 1A58201F Razer x Lambda TensorBook dmi.product.name: TensorBook (2022) dmi.product.sku: RZ09-0421NEL9 dmi.product.version: 8.04 dmi.sys.vendor: Razer x Lambda version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.2.5-0ubuntu0.1~22.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2.7 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy ubuntu wayland-session -- 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/2009564 Title: Touchpad disabling while typing does not work Status in xorg package in Ubuntu: New Bug description: It makes my laptop much less usable. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.19.0-35.36~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-35-generic x86_64 NonfreeKernelModules:
[Touch-packages] [Bug 1954716] Re: rpi nfsroot vers=4 not supported anymore?
Sorry to come back to this, but I'm now trying to netboot Ubuntu 22.04.2, having found the above mentioned work-around for 20.04. Something has changed: I can no longer netboot from NFSv4 by replacing /usr/lib/klibc/bin/nfsmount with an NFSv4-friendly hack. I am now getting the same error messages that nfsmount used to generate, but I have discovered that /usr/lib/klibc/bin/kinit also generates them. So I am guessing that in 22.04 kinit has taken over part of the work the nfsmount performed in 20.04. Any thoughts? I'll try to take a look at kinit tomorrow and see if I can find another work-around. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to klibc in Ubuntu. https://bugs.launchpad.net/bugs/1954716 Title: rpi nfsroot vers=4 not supported anymore? Status in klibc package in Ubuntu: Confirmed Status in linux-raspi package in Ubuntu: Invalid Bug description: I'm running `5.13.0-1011-raspi #13-Ubuntu SMP PREEMPT Fri Nov 19 18:40:23 UTC 2021 aarch64 aarch64 aarch64 GNU/Linux` and have successfully set up netbooting on my RPi 4B (4GB). When I do not specify a `vers=` in cmdline.txt, NFS version 3 is used. I'd like to move to version 4, but unlike the setup described in https://forums.raspberrypi.com/viewtopic.php?p=1751741#p1751741, I cannot get `vers=4` (or any sub-version to work): the console logs `invalid value for vers.` for whatever I try. Current working cmdline.txt: ``` dwc_otg.lpm_enable=0 console=serial0,115200 console=tty1 root=/dev/nfs nfsroot=192.168.3.101:/srv/pinet/root,tcp ro ip=dhcp rootwait fixrtc splash ``` Nonworking cmdline.txt: ``` dwc_otg.lpm_enable=0 console=serial0,115200 console=tty1 root=/dev/nfs nfsroot=192.168.3.101:/srv/pinet/root,tcp,vers=4 ro ip=dhcp rootwait fixrtc splash ``` To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/klibc/+bug/1954716/+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 1954716] rpi nfsroot vers=4 not supported anymore?
And being able to boot from NFSv4 has also made overlayroot work. I just need to go back and ensure that it still doesn’t work with NFSv3, just in case it was fixed by something else... > On 9 Aug 2022, at 13:47, Juerg Haefliger <1954...@bugs.launchpad.net> wrote: > > Please do test the work-around. If indeed NFSv4 solves your overlayfs > problem then that would be another reason for fixing nfsmount. > > We can carry Ubuntu specific fixes if for some reason Debian doesn't > want them but the preferred way is obviously to fix it in Debian so that > it tickles down naturally to Ubuntu (and other Debian based distros). > > I'm looking at it atm but NFS is not my strong suit :-) > > -- > You received this bug notification because you are subscribed to a > duplicate bug report (1983620). > https://bugs.launchpad.net/bugs/1954716 > > Title: > rpi nfsroot vers=4 not supported anymore? > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/klibc/+bug/1954716/+subscriptions > -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to klibc in Ubuntu. https://bugs.launchpad.net/bugs/1954716 Title: rpi nfsroot vers=4 not supported anymore? Status in klibc package in Ubuntu: Confirmed Status in linux-raspi package in Ubuntu: Invalid Bug description: I'm running `5.13.0-1011-raspi #13-Ubuntu SMP PREEMPT Fri Nov 19 18:40:23 UTC 2021 aarch64 aarch64 aarch64 GNU/Linux` and have successfully set up netbooting on my RPi 4B (4GB). When I do not specify a `vers=` in cmdline.txt, NFS version 3 is used. I'd like to move to version 4, but unlike the setup described in https://forums.raspberrypi.com/viewtopic.php?p=1751741#p1751741, I cannot get `vers=4` (or any sub-version to work): the console logs `invalid value for vers.` for whatever I try. Current working cmdline.txt: ``` dwc_otg.lpm_enable=0 console=serial0,115200 console=tty1 root=/dev/nfs nfsroot=192.168.3.101:/srv/pinet/root,tcp ro ip=dhcp rootwait fixrtc splash ``` Nonworking cmdline.txt: ``` dwc_otg.lpm_enable=0 console=serial0,115200 console=tty1 root=/dev/nfs nfsroot=192.168.3.101:/srv/pinet/root,tcp,vers=4 ro ip=dhcp rootwait fixrtc splash ``` To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/klibc/+bug/1954716/+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 1954716] Re: rpi nfsroot vers=4 not supported anymore?
Whilst trying to understand the problem I looked at the source of nfsmount in klibc. Nfsmount has a switch statement in which it checks the value of nfsvers and only proceeds if it is 2 or 3. Given that my version of nfsmount, compiled with klcc, can indeed mount using NFSv4 I suspect that in libc's version the switch statement only needs to be extended with the cases 4, 4.0, 4.1 and 4.2. It's not entirely trivial, but it's hard to understand why it hasn't been done sometime during the last 15 years. I may take a closer look when I've fixed my next bug. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to klibc in Ubuntu. https://bugs.launchpad.net/bugs/1954716 Title: rpi nfsroot vers=4 not supported anymore? Status in klibc package in Ubuntu: Confirmed Status in linux-raspi package in Ubuntu: Invalid Bug description: I'm running `5.13.0-1011-raspi #13-Ubuntu SMP PREEMPT Fri Nov 19 18:40:23 UTC 2021 aarch64 aarch64 aarch64 GNU/Linux` and have successfully set up netbooting on my RPi 4B (4GB). When I do not specify a `vers=` in cmdline.txt, NFS version 3 is used. I'd like to move to version 4, but unlike the setup described in https://forums.raspberrypi.com/viewtopic.php?p=1751741#p1751741, I cannot get `vers=4` (or any sub-version to work): the console logs `invalid value for vers.` for whatever I try. Current working cmdline.txt: ``` dwc_otg.lpm_enable=0 console=serial0,115200 console=tty1 root=/dev/nfs nfsroot=192.168.3.101:/srv/pinet/root,tcp ro ip=dhcp rootwait fixrtc splash ``` Nonworking cmdline.txt: ``` dwc_otg.lpm_enable=0 console=serial0,115200 console=tty1 root=/dev/nfs nfsroot=192.168.3.101:/srv/pinet/root,tcp,vers=4 ro ip=dhcp rootwait fixrtc splash ``` To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/klibc/+bug/1954716/+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 1954716] Re: rpi nfsroot vers=4 not supported anymore?
Done it! I've managed to boot my RPi4 with Ubuntu Jammy off an NFSv4 share using the workaround from https://bugs.debian.org/cgi- bin/bugreport.cgi?bug=409272#14 . I created the file in the attachment and compiled it with klcc. If anyone else wants to use it they'll have to edit the file, put their own share address in, and recompile. I then copied the file to /usr/lib/klibc/bin/nfsmount, replacing the version installed with Ubuntu. After that I ran update-initramfs -u (ignoring the errors - update- initramfs seems blissfully unaware of network booting with NFS of any flavour). After ensuring that /boot/initrd.img did in fact contain my version of nfsmount (lsinitramfs -l /boot/initrd.img) I rebooted the RPi. It came up so cleanly that I thought I must have made a mistake :-) But df -hT showed that the root was mounted with NFSv4. Now for the next problem... :-) ** Attachment added: "a replacement for /usr/lib/klibc/bin/nfsmount to enable NFS booting from NFSv4 share hardwired in file" https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1954716/+attachment/5608460/+files/nfsmount.c -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to klibc in Ubuntu. https://bugs.launchpad.net/bugs/1954716 Title: rpi nfsroot vers=4 not supported anymore? Status in klibc package in Ubuntu: Confirmed Status in linux-raspi package in Ubuntu: Invalid Bug description: I'm running `5.13.0-1011-raspi #13-Ubuntu SMP PREEMPT Fri Nov 19 18:40:23 UTC 2021 aarch64 aarch64 aarch64 GNU/Linux` and have successfully set up netbooting on my RPi 4B (4GB). When I do not specify a `vers=` in cmdline.txt, NFS version 3 is used. I'd like to move to version 4, but unlike the setup described in https://forums.raspberrypi.com/viewtopic.php?p=1751741#p1751741, I cannot get `vers=4` (or any sub-version to work): the console logs `invalid value for vers.` for whatever I try. Current working cmdline.txt: ``` dwc_otg.lpm_enable=0 console=serial0,115200 console=tty1 root=/dev/nfs nfsroot=192.168.3.101:/srv/pinet/root,tcp ro ip=dhcp rootwait fixrtc splash ``` Nonworking cmdline.txt: ``` dwc_otg.lpm_enable=0 console=serial0,115200 console=tty1 root=/dev/nfs nfsroot=192.168.3.101:/srv/pinet/root,tcp,vers=4 ro ip=dhcp rootwait fixrtc splash ``` To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/klibc/+bug/1954716/+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 1954716] Re: rpi nfsroot vers=4 not supported anymore?
Good point: since this is the first bug I have ever actively pursued, this is one of possibly many avenues I should follow. > On 9 Aug 2022, at 19:30, Thorsten Glaser <1954...@bugs.launchpad.net> wrote: > > Have you considered informing klibc upstream? (Granted, save for hpa > that’s basically the Debian maintainers, but they don’t necessarily get > Launchpad bugreports either.) > > -- > You received this bug notification because you are subscribed to a > duplicate bug report (1983620). > https://bugs.launchpad.net/bugs/1954716 > > Title: > rpi nfsroot vers=4 not supported anymore? > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/klibc/+bug/1954716/+subscriptions > -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to klibc in Ubuntu. https://bugs.launchpad.net/bugs/1954716 Title: rpi nfsroot vers=4 not supported anymore? Status in klibc package in Ubuntu: Confirmed Status in linux-raspi package in Ubuntu: Invalid Bug description: I'm running `5.13.0-1011-raspi #13-Ubuntu SMP PREEMPT Fri Nov 19 18:40:23 UTC 2021 aarch64 aarch64 aarch64 GNU/Linux` and have successfully set up netbooting on my RPi 4B (4GB). When I do not specify a `vers=` in cmdline.txt, NFS version 3 is used. I'd like to move to version 4, but unlike the setup described in https://forums.raspberrypi.com/viewtopic.php?p=1751741#p1751741, I cannot get `vers=4` (or any sub-version to work): the console logs `invalid value for vers.` for whatever I try. Current working cmdline.txt: ``` dwc_otg.lpm_enable=0 console=serial0,115200 console=tty1 root=/dev/nfs nfsroot=192.168.3.101:/srv/pinet/root,tcp ro ip=dhcp rootwait fixrtc splash ``` Nonworking cmdline.txt: ``` dwc_otg.lpm_enable=0 console=serial0,115200 console=tty1 root=/dev/nfs nfsroot=192.168.3.101:/srv/pinet/root,tcp,vers=4 ro ip=dhcp rootwait fixrtc splash ``` To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/klibc/+bug/1954716/+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 1954716] Re: rpi nfsroot vers=4 not supported anymore?
I will test the work-around, but I won’t get round to it before the end of the week. > On 9 Aug 2022, at 13:55, Juerg Haefliger <1954...@bugs.launchpad.net> wrote: > > Please do test the work-around. If indeed NFSv4 solves your overlayfs > problem then that would be another reason for fixing nfsmount. > > We can carry Ubuntu specific fixes if for some reason Debian doesn't > want them but the preferred way is obviously to fix it in Debian so that > it tickles down naturally to Ubuntu (and other Debian based distros). > > I'm looking at it atm but NFS is not my strong suit :-) > > -- > You received this bug notification because you are subscribed to a > duplicate bug report (1983620). > https://bugs.launchpad.net/bugs/1954716 > > Title: > rpi nfsroot vers=4 not supported anymore? > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/klibc/+bug/1954716/+subscriptions > -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to klibc in Ubuntu. https://bugs.launchpad.net/bugs/1954716 Title: rpi nfsroot vers=4 not supported anymore? Status in klibc package in Ubuntu: Confirmed Status in linux-raspi package in Ubuntu: Invalid Bug description: I'm running `5.13.0-1011-raspi #13-Ubuntu SMP PREEMPT Fri Nov 19 18:40:23 UTC 2021 aarch64 aarch64 aarch64 GNU/Linux` and have successfully set up netbooting on my RPi 4B (4GB). When I do not specify a `vers=` in cmdline.txt, NFS version 3 is used. I'd like to move to version 4, but unlike the setup described in https://forums.raspberrypi.com/viewtopic.php?p=1751741#p1751741, I cannot get `vers=4` (or any sub-version to work): the console logs `invalid value for vers.` for whatever I try. Current working cmdline.txt: ``` dwc_otg.lpm_enable=0 console=serial0,115200 console=tty1 root=/dev/nfs nfsroot=192.168.3.101:/srv/pinet/root,tcp ro ip=dhcp rootwait fixrtc splash ``` Nonworking cmdline.txt: ``` dwc_otg.lpm_enable=0 console=serial0,115200 console=tty1 root=/dev/nfs nfsroot=192.168.3.101:/srv/pinet/root,tcp,vers=4 ro ip=dhcp rootwait fixrtc splash ``` To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/klibc/+bug/1954716/+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 1954716] Re: rpi nfsroot vers=4 not supported anymore?
Thanks Juerg, you’ve been very helpful. Presumably there is no quick fix for this because of the klibc/glibc thing, so it’s an architectural rather than a programming issue. And it needs to be fixed in Debian rather than in Ubuntu. I’d offer to help but I arrived here after drilling down from a completely different realm and it’s outside my comfort zone. I want to evaluate the work-around against using RaspiOS before deciding how to proceed. Is there any way of crowd-funding bug fixing? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to klibc in Ubuntu. https://bugs.launchpad.net/bugs/1954716 Title: rpi nfsroot vers=4 not supported anymore? Status in klibc package in Ubuntu: Confirmed Status in linux-raspi package in Ubuntu: Invalid Bug description: I'm running `5.13.0-1011-raspi #13-Ubuntu SMP PREEMPT Fri Nov 19 18:40:23 UTC 2021 aarch64 aarch64 aarch64 GNU/Linux` and have successfully set up netbooting on my RPi 4B (4GB). When I do not specify a `vers=` in cmdline.txt, NFS version 3 is used. I'd like to move to version 4, but unlike the setup described in https://forums.raspberrypi.com/viewtopic.php?p=1751741#p1751741, I cannot get `vers=4` (or any sub-version to work): the console logs `invalid value for vers.` for whatever I try. Current working cmdline.txt: ``` dwc_otg.lpm_enable=0 console=serial0,115200 console=tty1 root=/dev/nfs nfsroot=192.168.3.101:/srv/pinet/root,tcp ro ip=dhcp rootwait fixrtc splash ``` Nonworking cmdline.txt: ``` dwc_otg.lpm_enable=0 console=serial0,115200 console=tty1 root=/dev/nfs nfsroot=192.168.3.101:/srv/pinet/root,tcp,vers=4 ro ip=dhcp rootwait fixrtc splash ``` To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/klibc/+bug/1954716/+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 1954716] Re: rpi nfsroot vers=4 not supported anymore?
Thanks, I’ll look at that. I note that this issue is now a confirmed bug. What does that mean in practical terms? Will it be dealt with this week, this month, this year…? I need to be able to boot from NFSv4. If RaspiOS can do that it might make sense for me to move after 15 years from Ubuntu to RaspiOS. I don’t want to, but I’ve already wasted months on this issue. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to klibc in Ubuntu. https://bugs.launchpad.net/bugs/1954716 Title: rpi nfsroot vers=4 not supported anymore? Status in klibc package in Ubuntu: Confirmed Status in linux-raspi package in Ubuntu: Invalid Bug description: I'm running `5.13.0-1011-raspi #13-Ubuntu SMP PREEMPT Fri Nov 19 18:40:23 UTC 2021 aarch64 aarch64 aarch64 GNU/Linux` and have successfully set up netbooting on my RPi 4B (4GB). When I do not specify a `vers=` in cmdline.txt, NFS version 3 is used. I'd like to move to version 4, but unlike the setup described in https://forums.raspberrypi.com/viewtopic.php?p=1751741#p1751741, I cannot get `vers=4` (or any sub-version to work): the console logs `invalid value for vers.` for whatever I try. Current working cmdline.txt: ``` dwc_otg.lpm_enable=0 console=serial0,115200 console=tty1 root=/dev/nfs nfsroot=192.168.3.101:/srv/pinet/root,tcp ro ip=dhcp rootwait fixrtc splash ``` Nonworking cmdline.txt: ``` dwc_otg.lpm_enable=0 console=serial0,115200 console=tty1 root=/dev/nfs nfsroot=192.168.3.101:/srv/pinet/root,tcp,vers=4 ro ip=dhcp rootwait fixrtc splash ``` To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/klibc/+bug/1954716/+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 1954716] Re: rpi nfsroot vers=4 not supported anymore?
The upstream bug is in Debian 11. The current version of RaspiOS, which seems to support booting from NFSv4, is a Debian 11 derivative. That means that RaspiOS has fixed it for Debian 11. Is it possible to copy the RaspiOS solution? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to klibc in Ubuntu. https://bugs.launchpad.net/bugs/1954716 Title: rpi nfsroot vers=4 not supported anymore? Status in klibc package in Ubuntu: Confirmed Status in linux-raspi package in Ubuntu: Invalid Bug description: I'm running `5.13.0-1011-raspi #13-Ubuntu SMP PREEMPT Fri Nov 19 18:40:23 UTC 2021 aarch64 aarch64 aarch64 GNU/Linux` and have successfully set up netbooting on my RPi 4B (4GB). When I do not specify a `vers=` in cmdline.txt, NFS version 3 is used. I'd like to move to version 4, but unlike the setup described in https://forums.raspberrypi.com/viewtopic.php?p=1751741#p1751741, I cannot get `vers=4` (or any sub-version to work): the console logs `invalid value for vers.` for whatever I try. Current working cmdline.txt: ``` dwc_otg.lpm_enable=0 console=serial0,115200 console=tty1 root=/dev/nfs nfsroot=192.168.3.101:/srv/pinet/root,tcp ro ip=dhcp rootwait fixrtc splash ``` Nonworking cmdline.txt: ``` dwc_otg.lpm_enable=0 console=serial0,115200 console=tty1 root=/dev/nfs nfsroot=192.168.3.101:/srv/pinet/root,tcp,vers=4 ro ip=dhcp rootwait fixrtc splash ``` To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/klibc/+bug/1954716/+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 1951491] Re: Can't run snaps: .slice/session-1.scope is not a snap cgroup
I have firefox working. To get it to work I had to disable cgroup. To do this I followed Tim Richardson's instructions at c25. When launched it outputs many permission denied errors which are attached. I do not know what to do about these errors. Before I can use the installation these have to be solved. ** Attachment added: "firefox_launch_permission_denied_errors.txt" https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1951491/+attachment/5604151/+files/firefox_launch_permission_denied_errors.txt -- 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/1951491 Title: Can't run snaps: .slice/session-1.scope is not a snap cgroup Status in X2Go: New Status in snapd package in Ubuntu: Invalid Status in systemd package in Ubuntu: Confirmed Status in x2goserver package in Ubuntu: Confirmed Status in snapd package in Debian: New Bug description: I just upgraded from hirsute to impish using do-release-upgrade. On the upgraded system, I can't run either firefox or chromium (both of which worked fine under hirsute). Both fail with: /user.slice/user-NNN.slice/session-1.scope is not a snap cgroup where NNN is my uid With firefox, I was able to fix the problem with: snap remove --purge firefox apt purge firefox apt install firefox Now firefox works. But I tried the same thing substituting chromium- browser for firefox, and it didn't help: chromium fails with the same error message. I guess there must be something left over from the hirsute version of snapd that isn't getting noticed or cleared by the impish version? Someone suggested this might be related to bug 1850667, but that bug is marked fixed as of a couple months ago, and I just did this upgrade today. Also, it doesn't mention the error message I'm seeing. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: snapd 2.53+21.10ubuntu1 ProcVersionSignature: Ubuntu 5.13.0-21.21-generic 5.13.18 Uname: Linux 5.13.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 CasperMD5CheckResult: unknown Date: Thu Nov 18 18:12:45 2021 InstallationDate: Installed on 2020-04-29 (568 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: snapd UpgradeStatus: Upgraded to impish on 2021-11-18 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/x2go/+bug/1951491/+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 1951491] Re: Can't run snaps: .slice/session-1.scope is not a snap cgroup
I have recently discovered: 1)The global variable XDG_RUNTIME_DIR is not set to anything. 2) There is only one user on this newly installed Ubuntu 22.04 OS. It would be expected the user number for it is 1000. This is verified by the global $UID being set to that number as expected. But the directory /run/user/1000 does not exist. The directory /run/user/ is empty. Included the updated attachment to c47 is the syslog file. -- 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/1951491 Title: Can't run snaps: .slice/session-1.scope is not a snap cgroup Status in X2Go: New Status in snapd package in Ubuntu: Invalid Status in systemd package in Ubuntu: Confirmed Status in x2goserver package in Ubuntu: Confirmed Status in snapd package in Debian: New Bug description: I just upgraded from hirsute to impish using do-release-upgrade. On the upgraded system, I can't run either firefox or chromium (both of which worked fine under hirsute). Both fail with: /user.slice/user-NNN.slice/session-1.scope is not a snap cgroup where NNN is my uid With firefox, I was able to fix the problem with: snap remove --purge firefox apt purge firefox apt install firefox Now firefox works. But I tried the same thing substituting chromium- browser for firefox, and it didn't help: chromium fails with the same error message. I guess there must be something left over from the hirsute version of snapd that isn't getting noticed or cleared by the impish version? Someone suggested this might be related to bug 1850667, but that bug is marked fixed as of a couple months ago, and I just did this upgrade today. Also, it doesn't mention the error message I'm seeing. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: snapd 2.53+21.10ubuntu1 ProcVersionSignature: Ubuntu 5.13.0-21.21-generic 5.13.18 Uname: Linux 5.13.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 CasperMD5CheckResult: unknown Date: Thu Nov 18 18:12:45 2021 InstallationDate: Installed on 2020-04-29 (568 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: snapd UpgradeStatus: Upgraded to impish on 2021-11-18 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/x2go/+bug/1951491/+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 1951491] Re: Can't run snaps: .slice/session-1.scope is not a snap cgroup
** Attachment removed: "Jira 1951491 Attachment 2022-07-13.zip" https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1951491/+attachment/5603023/+files/Jira%201951491%20Attachment%202022-07-13.zip ** Attachment added: "Jira 1951491 Attachment 2022-07-16.zip" https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1951491/+attachment/5603552/+files/Jira%201951491%20Attachment%202022-07-16.zip -- 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/1951491 Title: Can't run snaps: .slice/session-1.scope is not a snap cgroup Status in X2Go: New Status in snapd package in Ubuntu: Invalid Status in systemd package in Ubuntu: Confirmed Status in x2goserver package in Ubuntu: Confirmed Status in snapd package in Debian: New Bug description: I just upgraded from hirsute to impish using do-release-upgrade. On the upgraded system, I can't run either firefox or chromium (both of which worked fine under hirsute). Both fail with: /user.slice/user-NNN.slice/session-1.scope is not a snap cgroup where NNN is my uid With firefox, I was able to fix the problem with: snap remove --purge firefox apt purge firefox apt install firefox Now firefox works. But I tried the same thing substituting chromium- browser for firefox, and it didn't help: chromium fails with the same error message. I guess there must be something left over from the hirsute version of snapd that isn't getting noticed or cleared by the impish version? Someone suggested this might be related to bug 1850667, but that bug is marked fixed as of a couple months ago, and I just did this upgrade today. Also, it doesn't mention the error message I'm seeing. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: snapd 2.53+21.10ubuntu1 ProcVersionSignature: Ubuntu 5.13.0-21.21-generic 5.13.18 Uname: Linux 5.13.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 CasperMD5CheckResult: unknown Date: Thu Nov 18 18:12:45 2021 InstallationDate: Installed on 2020-04-29 (568 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: snapd UpgradeStatus: Upgraded to impish on 2021-11-18 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/x2go/+bug/1951491/+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 1951491] Re: Can't run snaps: .slice/session-1.scope is not a snap cgroup
I too have a very similar error. Only when I attempt to launch firefox remotely by SSH I get this: /system.slice/ssh.service is not a snap cgroup And this when I attempt launch firefox directly on my target computer: WARNING: cannot start document portal: Expected portal at "/run/user/1000/doc", got "/home/stephen/.cache/doc" /system.slice/sddm.service is not a snap cgroup So I edited the three files as recommended by Michael Woods (woodsy) in c44. The result is the target computer boots a dark, blank, monitor screen. Fortunately the OS was nevertheless accessible by SSH, and so I was able to restore the three files, and after doing so, I rebooted and got the expected screen displays. I am not sure I edited those three files correctly, so I attached those edited files to this posting for your review. I also included in the attachment the output from the command: SNAPD_DEBUG=1 snap run firefox I would deeply appreciate any help with this. It is a new computer, and a new Ubuntu installation of mine. ** Attachment added: "Jira 1951491 Attachment 2022-07-13.zip" https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1951491/+attachment/5603023/+files/Jira%201951491%20Attachment%202022-07-13.zip -- 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/1951491 Title: Can't run snaps: .slice/session-1.scope is not a snap cgroup Status in X2Go: New Status in snapd package in Ubuntu: Invalid Status in systemd package in Ubuntu: Confirmed Status in x2goserver package in Ubuntu: Confirmed Status in snapd package in Debian: New Bug description: I just upgraded from hirsute to impish using do-release-upgrade. On the upgraded system, I can't run either firefox or chromium (both of which worked fine under hirsute). Both fail with: /user.slice/user-NNN.slice/session-1.scope is not a snap cgroup where NNN is my uid With firefox, I was able to fix the problem with: snap remove --purge firefox apt purge firefox apt install firefox Now firefox works. But I tried the same thing substituting chromium- browser for firefox, and it didn't help: chromium fails with the same error message. I guess there must be something left over from the hirsute version of snapd that isn't getting noticed or cleared by the impish version? Someone suggested this might be related to bug 1850667, but that bug is marked fixed as of a couple months ago, and I just did this upgrade today. Also, it doesn't mention the error message I'm seeing. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: snapd 2.53+21.10ubuntu1 ProcVersionSignature: Ubuntu 5.13.0-21.21-generic 5.13.18 Uname: Linux 5.13.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 CasperMD5CheckResult: unknown Date: Thu Nov 18 18:12:45 2021 InstallationDate: Installed on 2020-04-29 (568 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: snapd UpgradeStatus: Upgraded to impish on 2021-11-18 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/x2go/+bug/1951491/+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 1891110] Re: Focal ucf need redirect fixes backported to ensure working with config-package-dev
** Patch added: "Patch to resolve Divert issue for Jammy ucf 3.0043" https://bugs.launchpad.net/ubuntu/+source/ucf/+bug/1891110/+attachment/5592489/+files/ucf-3.0043-divert.patch -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ucf in Ubuntu. https://bugs.launchpad.net/bugs/1891110 Title: Focal ucf need redirect fixes backported to ensure working with config-package-dev Status in ucf package in Ubuntu: Fix Released Status in ucf source package in Focal: Incomplete Status in ucf package in Debian: Fix Released Bug description: When using config-package-dev and diverting config files for packages that use ucf to manage installation of their config files, this patch is necessary to ensure config files are correctly diverted. Please apply to upstream Focal UCF package To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ucf/+bug/1891110/+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 1891110] Re: Focal ucf need redirect fixes backported to ensure working with config-package-dev
** Patch added: "Patch for Focal UCF 3.0038" https://bugs.launchpad.net/ubuntu/+source/ucf/+bug/1891110/+attachment/5592488/+files/ucf-3.0038-divert.patch -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ucf in Ubuntu. https://bugs.launchpad.net/bugs/1891110 Title: Focal ucf need redirect fixes backported to ensure working with config-package-dev Status in ucf package in Ubuntu: Fix Released Status in ucf source package in Focal: Incomplete Status in ucf package in Debian: Fix Released Bug description: When using config-package-dev and diverting config files for packages that use ucf to manage installation of their config files, this patch is necessary to ensure config files are correctly diverted. Please apply to upstream Focal UCF package To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ucf/+bug/1891110/+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 1891110] Re: Focal ucf need redirect fixes backported to ensure working with config-package-dev
** Patch removed: "ucf-3.0038-divertfix.patch" https://bugs.launchpad.net/ubuntu/+source/ucf/+bug/1891110/+attachment/5581412/+files/ucf-3.0038-divertfix.patch -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ucf in Ubuntu. https://bugs.launchpad.net/bugs/1891110 Title: Focal ucf need redirect fixes backported to ensure working with config-package-dev Status in ucf package in Ubuntu: Fix Released Status in ucf source package in Focal: Incomplete Status in ucf package in Debian: Fix Released Bug description: When using config-package-dev and diverting config files for packages that use ucf to manage installation of their config files, this patch is necessary to ensure config files are correctly diverted. Please apply to upstream Focal UCF package To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ucf/+bug/1891110/+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 1969989] [NEW] package base-passwd 3.5.52build1 failed to install/upgrade: installed base-passwd package post-installation script subprocess returned error exit status 4
Public bug reported: Crshed during install system is 18.04 upgraded to 20.04 upgrading to 22.04 ProblemType: Package DistroRelease: Ubuntu 22.04 Package: base-passwd 3.5.52build1 ProcVersionSignature: Ubuntu 5.4.0-109.123-generic 5.4.178 Uname: Linux 5.4.0-109-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.23 Architecture: amd64 CasperMD5CheckResult: unknown Date: Fri Apr 22 13:23:57 2022 ErrorMessage: installed base-passwd package post-installation script subprocess returned error exit status 4 InstallationDate: Installed on 2015-04-11 (2568 days ago) InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1) Python3Details: /usr/bin/python3.10, Python 3.10.4, python3-minimal, 3.10.4-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.21.1ubuntu2 apt 2.0.6 SourcePackage: base-passwd Title: package base-passwd 3.5.52build1 failed to install/upgrade: installed base-passwd package post-installation script subprocess returned error exit status 4 UpgradeStatus: Upgraded to jammy on 2022-04-22 (0 days ago) ** Affects: base-passwd (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package jammy need-duplicate-check -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to base-passwd in Ubuntu. https://bugs.launchpad.net/bugs/1969989 Title: package base-passwd 3.5.52build1 failed to install/upgrade: installed base-passwd package post-installation script subprocess returned error exit status 4 Status in base-passwd package in Ubuntu: New Bug description: Crshed during install system is 18.04 upgraded to 20.04 upgrading to 22.04 ProblemType: Package DistroRelease: Ubuntu 22.04 Package: base-passwd 3.5.52build1 ProcVersionSignature: Ubuntu 5.4.0-109.123-generic 5.4.178 Uname: Linux 5.4.0-109-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.23 Architecture: amd64 CasperMD5CheckResult: unknown Date: Fri Apr 22 13:23:57 2022 ErrorMessage: installed base-passwd package post-installation script subprocess returned error exit status 4 InstallationDate: Installed on 2015-04-11 (2568 days ago) InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1) Python3Details: /usr/bin/python3.10, Python 3.10.4, python3-minimal, 3.10.4-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.21.1ubuntu2 apt 2.0.6 SourcePackage: base-passwd Title: package base-passwd 3.5.52build1 failed to install/upgrade: installed base-passwd package post-installation script subprocess returned error exit status 4 UpgradeStatus: Upgraded to jammy on 2022-04-22 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/base-passwd/+bug/1969989/+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 1891110] Re: Focal ucf need redirect fixes backported to ensure working with config-package-dev
[Impact] * Cannot use ucf to install templated configuration when using dpkg-divert with the destination config file * Affects various packages including dovecot and any custom config packages using both config-package-dev and ucf [Test Plan] * Create a config-package-dev based config-packagename.deb to replace existsing config * Include a line in the postinst in the config.deb to install a template for a config file also spcified in the displace file (which is therefore diverted by dpkg-divert) [Where problems could occur] * Any issue with patch may cause issues with packages installing config via ucf (this includes dovecot, openssh-server, php7.4, gdm3) [Other Info] * Tested with config-package-dev rolled config deb package -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ucf in Ubuntu. https://bugs.launchpad.net/bugs/1891110 Title: Focal ucf need redirect fixes backported to ensure working with config-package-dev Status in ucf package in Ubuntu: Fix Released Status in ucf source package in Focal: Incomplete Status in ucf package in Debian: Fix Released Bug description: When using config-package-dev and diverting config files for packages that use ucf to manage installation of their config files, this patch is necessary to ensure config files are correctly diverted. Please apply to upstream Focal UCF package To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ucf/+bug/1891110/+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 1891110] Re: Focal ucf need redirect fixes backported to ensure working with config-package-dev
Divert related fixes from ucf 3.0040 and also from https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=979354 Allows ucf to work when using dpkg-divert or config-package-dev for diverts eg ucf --three-way ucfr Tested and working as expected Note: ucf does not working with --debconf-ok flag (both with and without patch) ** Bug watch added: Debian Bug tracker #979354 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=979354 ** Patch added: "ucf-3.0038-divertfix.patch" https://bugs.launchpad.net/ubuntu/+source/ucf/+bug/1891110/+attachment/5581412/+files/ucf-3.0038-divertfix.patch -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ucf in Ubuntu. https://bugs.launchpad.net/bugs/1891110 Title: Focal ucf need redirect fixes backported to ensure working with config-package-dev Status in ucf package in Ubuntu: Fix Released Status in ucf source package in Focal: Incomplete Status in ucf package in Debian: Fix Released Bug description: When using config-package-dev and diverting config files for packages that use ucf to manage installation of their config files, this patch is necessary to ensure config files are correctly diverted. Please apply to upstream Focal UCF package To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ucf/+bug/1891110/+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 1891110] Re: Focal ucf need redirect fixes backported to ensure working with config-package-dev
** Patch removed: "patches from ucf 3.0040 to fix diversions issue with config-package-dev" https://bugs.launchpad.net/ubuntu/+source/ucf/+bug/1891110/+attachment/5400552/+files/honor-dpkg-diversions-1+2+3.patch -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ucf in Ubuntu. https://bugs.launchpad.net/bugs/1891110 Title: Focal ucf need redirect fixes backported to ensure working with config-package-dev Status in ucf package in Ubuntu: Fix Released Status in ucf source package in Focal: Incomplete Status in ucf package in Debian: Fix Released Bug description: When using config-package-dev and diverting config files for packages that use ucf to manage installation of their config files, this patch is necessary to ensure config files are correctly diverted. Please apply to upstream Focal UCF package To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ucf/+bug/1891110/+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 1868129] Re: I can't attach a writecache to LV
Is there a workaround while this waits? Seems like this is pretty important to me but -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lvm2 in Ubuntu. https://bugs.launchpad.net/bugs/1868129 Title: I can't attach a writecache to LV Status in lvm2 package in Ubuntu: Confirmed Bug description: #lvconvert --type writecache --cachesettings 'low_watermark=0 high_watermark=10 writeback_jobs=2048' --cachevol cache ssd/data WARNING: Unrecognised segment type writecache Invalid argument for --type: writecache Error during parsing of command line. I see that lvm2 package was build without key --with- writecache=internal #lvm version LVM version: 2.03.07(2) (2019-11-30) Library version: 1.02.167 (2019-11-30) Driver version: 4.41.0 Configuration: ./configure --build=x86_64-linux-gnu --prefix=/usr --includedir=${prefix}/include --mandir=${prefix}/share/man --infodir=${prefix}/share/info --sysconfdir=/etc --localstatedir=/var --disable-silent-rules --libdir=${prefix}/lib/x86_64-linux-gnu --libexecdir=${prefix}/lib/x86_64-linux-gnu --runstatedir=/run --disable-maintainer-mode --disable-dependency-tracking --exec-prefix= --bindir=/bin --libdir=/lib/x86_64-linux-gnu --sbindir=/sbin --with-usrlibdir=/usr/lib/x86_64-linux-gnu --with-optimisation=-O2 --with-cache=internal --with-device-uid=0 --with-device-gid=6 --with-device-mode=0660 --with-default-pid-dir=/run --with-default-run-dir=/run/lvm --with-default-locking-dir=/run/lock/lvm --with-thin=internal --with-thin-check=/usr/sbin/thin_check --with-thin-dump=/usr/sbin/thin_dump --with-thin-repair=/usr/sbin/thin_repair --enable-applib --enable-blkid_wiping --enable-cmdlib --enable-dmeventd --enable-dbus-service --enable-lvmlockd-dlm --enable-lvmlockd-sanlock --enable-lvmpolld --enable-notify-dbus --enable-pkgconfig --enable-readline --enable-udev_rules --enable-udev_sync # lsmod | grep dm_writecache dm_writecache 36864 0 #cat /etc/os-release NAME="Ubuntu" VERSION="20.04 LTS (Focal Fossa)" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Ubuntu Focal Fossa (development branch)" VERSION_ID="20.04" HOME_URL="https://www.ubuntu.com/; SUPPORT_URL="https://help.ubuntu.com/; BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/; PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy; VERSION_CODENAME=focal UBUNTU_CODENAME=focal #uname -a Linux sw-sed-ubuntu 5.4.0-18-generic #22-Ubuntu SMP Sat Mar 7 18:13:06 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux #apt info lvm2 Package: lvm2 Version: 2.03.07-1ubuntu1 Priority: optional ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: lvm2 2.03.07-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24 Uname: Linux 5.4.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu20 Architecture: amd64 Date: Thu Mar 19 16:06:17 2020 InstallationDate: Installed on 2020-03-19 (0 days ago) InstallationMedia: Ubuntu-Server 20.04 LTS "Focal Fossa" - Alpha amd64 (20200317) ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash SourcePackage: lvm2 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/1868129/+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 1936975] [NEW] `openssl dhparam` cannot validate named group DH parameters
Public bug reported: Identified on Ubuntu 18.04 /etc/os-release: NAME="Ubuntu" VERSION="18.04.5 LTS (Bionic Beaver)" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Ubuntu 18.04.5 LTS" VERSION_ID="18.04" HOME_URL="https://www.ubuntu.com/; SUPPORT_URL="https://help.ubuntu.com/; BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/; PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy; VERSION_CODENAME=bionic UBUNTU_CODENAME=bionic Steps to reproduce: $ openssl dhparam Actual Results: ``` DH Parameters: (8192 bit) prime: 00:ff:ff:ff:ff:ff:ff:ff:ff:ad:f8:54:58:a2:bb: 4a:9a:af:dc:56:20:27:3d:3c:f1:d8:b9:c5:83:ce: 2d:36:95:a9:e1:36:41:14:64:33:fb:cc:93:9d:ce: 24:9b:3e:f9:7d:2f:e3:63:63:0c:75:d8:f6:81:b2: 02:ae:c4:61:7a:d3:df:1e:d5:d5:fd:65:61:24:33: f5:1f:5f:06:6e:d0:85:63:65:55:3d:ed:1a:f3:b5: 57:13:5e:7f:57:c9:35:98:4f:0c:70:e0:e6:8b:77: e2:a6:89:da:f3:ef:e8:72:1d:f1:58:a1:36:ad:e7: 35:30:ac:ca:4f:48:3a:79:7a:bc:0a:b1:82:b3:24: fb:61:d1:08:a9:4b:b2:c8:e3:fb:b9:6a:da:b7:60: d7:f4:68:1d:4f:42:a3:de:39:4d:f4:ae:56:ed:e7: 63:72:bb:19:0b:07:a7:c8:ee:0a:6d:70:9e:02:fc: e1:cd:f7:e2:ec:c0:34:04:cd:28:34:2f:61:91:72: fe:9c:e9:85:83:ff:8e:4f:12:32:ee:f2:81:83:c3: fe:3b:1b:4c:6f:ad:73:3b:b5:fc:bc:2e:c2:20:05: c5:8e:f1:83:7d:16:83:b2:c6:f3:4a:26:c1:b2:ef: fa:88:6b:42:38:61:1f:cf:dc:de:35:5b:3b:65:19: 03:5b:bc:34:f4:de:f9:9c:02:38:61:b4:6f:c9:d6: e6:c9:07:7a:d9:1d:26:91:f7:f7:ee:59:8c:b0:fa: c1:86:d9:1c:ae:fe:13:09:85:13:92:70:b4:13:0c: 93:bc:43:79:44:f4:fd:44:52:e2:d7:4d:d3:64:f2: e2:1e:71:f5:4b:ff:5c:ae:82:ab:9c:9d:f6:9e:e8: 6d:2b:c5:22:36:3a:0d:ab:c5:21:97:9b:0d:ea:da: 1d:bf:9a:42:d5:c4:48:4e:0a:bc:d0:6b:fa:53:dd: ef:3c:1b:20:ee:3f:d5:9d:7c:25:e4:1d:2b:66:9e: 1e:f1:6e:6f:52:c3:16:4d:f4:fb:79:30:e9:e4:e5: 88:57:b6:ac:7d:5f:42:d6:9f:6d:18:77:63:cf:1d: 55:03:40:04:87:f5:5b:a5:7e:31:cc:7a:71:35:c8: 86:ef:b4:31:8a:ed:6a:1e:01:2d:9e:68:32:a9:07: 60:0a:91:81:30:c4:6d:c7:78:f9:71:ad:00:38:09: 29:99:a3:33:cb:8b:7a:1a:1d:b9:3d:71:40:00:3c: 2a:4e:ce:a9:f9:8d:0a:cc:0a:82:91:cd:ce:c9:7d: cf:8e:c9:b5:5a:7f:88:a4:6b:4d:b5:a8:51:f4:41: 82:e1:c6:8a:00:7e:5e:0d:d9:02:0b:fd:64:b6:45: 03:6c:7a:4e:67:7d:2c:38:53:2a:3a:23:ba:44:42: ca:f5:3e:a6:3b:b4:54:32:9b:76:24:c8:91:7b:dd: 64:b1:c0:fd:4c:b3:8e:8c:33:4c:70:1c:3a:cd:ad: 06:57:fc:cf:ec:71:9b:1f:5c:3e:4e:46:04:1f:38: 81:47:fb:4c:fd:b4:77:a5:24:71:f7:a9:a9:69:10: b8:55:32:2e:db:63:40:d8:a0:0e:f0:92:35:05:11: e3:0a:be:c1:ff:f9:e3:a2:6e:7f:b2:9f:8c:18:30: 23:c3:58:7e:38:da:00:77:d9:b4:76:3e:4e:4b:94: b2:bb:c1:94:c6:65:1e:77:ca:f9:92:ee:aa:c0:23: 2a:28:1b:f6:b3:a7:39:c1:22:61:16:82:0a:e8:db: 58:47:a6:7c:be:f9:c9:09:1b:46:2d:53:8c:d7:2b: 03:74:6a:e7:7f:5e:62:29:2c:31:15:62:a8:46:50: 5d:c8:2d:b8:54:33:8a:e4:9f:52:35:c9:5b:91:17: 8c:cf:2d:d5:ca:ce:f4:03:ec:9d:18:10:c6:27:2b: 04:5b:3b:71:f9:dc:6b:80:d6:3f:dd:4a:8e:9a:db: 1e:69:62:a6:95:26:d4:31:61:c1:a4:1d:57:0d:79: 38:da:d4:a4:0e:32:9c:cf:f4:6a:aa:36:ad:00:4c: f6:00:c8:38:1e:42:5a:31:d9:51:ae:64:fd:b2:3f: ce:c9:50:9d:43:68:7f:eb:69:ed:d1:cc:5e:0b:8c: c3:bd:f6:4b:10:ef:86:b6:31:42:a3:ab:88:29:55: 5b:2f:74:7c:93:26:65:cb:2c:0f:1c:c0:1b:d7:02: 29:38:88:39:d2:af:05:e4:54:50:4a:c7:8b:75:82: 82:28:46:c0:ba:35:c3:5f:5c:59:16:0c:c0:46:fd: 82:51:54:1f:c6:8c:9c:86:b0:22:bb:70:99:87:6a: 46:0e:74:51:a8:a9:31:09:70:3f:ee:1c:21:7e:6c: 38:26:e5:2c:51:aa:69:1e:0e:42:3c:fc:99:e9:e3: 16:50:c1:21:7b:62:48:16:cd:ad:9a:95:f9:d5:b8: 01:94:88:d9:c0:a0:a1:fe:30:75:a5:77:e2:31:83: f8:1d:4a:3f:2f:a4:57:1e:fc:8c:e0:ba:8a:4f:e8: b6:85:5d:fe:72:b0:a6:6e:de:d2:fb:ab:fb:e5:8a: 30:fa:fa:be:1c:5d:71:a8:7e:2f:74:1e:f8:c1:fe: 86:fe:a6:bb:fd:e5:30:67:7f:0d:97:d1:1d:49:f7: a8:44:3d:08:22:e5:06:a9:f4:61:4e:01:1e:2a:94: 83:8f:f8:8c:d6:8c:8b:b7:c5:c6:42:4c:ff:ff:ff: ff:ff:ff:ff:ff generator: 2 (0x2) recommended-private-length: 400 bits WARNING: the g value is not a generator ``` Expected Results: ``` DH Parameters: (8192 bit) prime: 00:ff:ff:ff:ff:ff:ff:ff:ff:ad:f8:54:58:a2:bb: 4a:9a:af:dc:56:20:27:3d:3c:f1:d8:b9:c5:83:ce: 2d:36:95:a9:e1:36:41:14:64:33:fb:cc:93:9d:ce: 24:9b:3e:f9:7d:2f:e3:63:63:0c:75:d8:f6:81:b2:
[Touch-packages] [Bug 1936137] [NEW] package initramfs-tools 0.136ubuntu6.6 failed to install/upgrade: installed initramfs-tools package post-installation script subprocess returned error exit status
Public bug reported: This was automatically generated by my system. ProblemType: Package DistroRelease: Ubuntu 20.04 Package: initramfs-tools 0.136ubuntu6.6 ProcVersionSignature: Ubuntu 5.8.0-53.60~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-53-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip Date: Tue Jul 13 23:41:10 2021 ErrorMessage: installed initramfs-tools package post-installation script subprocess returned error exit status 1 PackageArchitecture: all Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.6 SourcePackage: initramfs-tools Title: package initramfs-tools 0.136ubuntu6.6 failed to install/upgrade: installed initramfs-tools package post-installation script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: initramfs-tools (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package focal -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1936137 Title: package initramfs-tools 0.136ubuntu6.6 failed to install/upgrade: installed initramfs-tools package post-installation script subprocess returned error exit status 1 Status in initramfs-tools package in Ubuntu: New Bug description: This was automatically generated by my system. ProblemType: Package DistroRelease: Ubuntu 20.04 Package: initramfs-tools 0.136ubuntu6.6 ProcVersionSignature: Ubuntu 5.8.0-53.60~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-53-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip Date: Tue Jul 13 23:41:10 2021 ErrorMessage: installed initramfs-tools package post-installation script subprocess returned error exit status 1 PackageArchitecture: all Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.6 SourcePackage: initramfs-tools Title: package initramfs-tools 0.136ubuntu6.6 failed to install/upgrade: installed initramfs-tools package post-installation script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1936137/+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 1821462] Re: Ubuntu 19.04 Desktop:slow boot
Hello Thanks for the email hope you're doing well. Apparently that was a bug in 19.04. I'm on 20.04 and I have exactly no issues. Thank you for the follow-up. I actually barely remember reporting this bug. Steve On June 30, 2021 6:36:30 p.m. Dan Streetman <1821...@bugs.launchpad.net> wrote: > please reopen if this is still an issue > > ** Changed in: systemd (Ubuntu) > Status: Confirmed => Invalid > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1821462 > > Title: > Ubuntu 19.04 Desktop:slow boot > > Status in systemd package in Ubuntu: > Invalid > > Bug description: > Hello, > I have my ubuntu desktop set to boot text only mode. > > it seems a removable hard drive was pplugged into my machine some time ago. > On every boot the boot takes a minute and a half to search to see if that > drive is plugged in. > > I ran systemd-analyze blame > > > Below is my output: > > 37.816s apt-daily.service >2.383s dev-sda4.device >2.381s NetworkManager-wait-online.service >1.198s man-db.service >1.112s dev-loop9.device >1.108s dev-loop8.device >1.098s dev-loop4.device >1.083s dev-loop6.device >1.071s dev-loop10.device >1.057s dev-loop13.device >1.057s dev-loop11.device >1.051s dev-loop7.device >1.051s dev-loop12.device >1.046s dev-loop2.device >1.032s dev-loop14.device >1.024s apt-daily-upgrade.service >1.017s snap-core18-782.mount > 988ms snap-vice\x2djz-22.mount > 983ms snap-gnome\x2dcalculator-260.mount > 949ms dev-loop15.device > 930ms dev-loop3.device > 905ms dev-loop5.device > 901ms dev-loop1.device > 899ms dev-loop0.device > 891ms dev-loop16.device > 878ms snap-gnome\x2d3\x2d26\x2d1604-78.mount > 868ms snap-remmina-2831.mount > 855ms snap-gnome\x2dcharacters-139.mount > 845ms snap-youtube\x2ddl\x2dsnap-1.mount > 844ms dev-loop17.device > 834ms snap-gnome\x2d3\x2d26\x2d1604-74.mount > 824ms snap-gnome\x2d3\x2d28\x2d1804-15.mount > 814ms snap-remmina-2823.mount > 803ms snap-gnome\x2dclocks-85.mount > 798ms snap-gnome\x2dcharacters-206.mount > 793ms snap-core-6350.mount > 783ms snap-core-6531.mount > 776ms udisks2.service > 773ms snap-gnome\x2dlogs-45.mount > 763ms snap-vice\x2djz-20.mount > 753ms snap-gtk\x2dcommon\x2dthemes-1198.mount > 744ms snap-core-6405.mount > 734ms snap-vice\x2djz-19.mount > 733ms snap-gnome\x2dcharacters-124.mount > 725ms snap-gtk\x2dcommon\x2dthemes-1122.mount > 719ms dev-loop18.device > 715ms snap-core18-731.mount > 706ms snap-core18-719.mount > 695ms snap-gnome\x2dcalculator-238.mount > 680ms upower.service > 662ms snap-gnome\x2d3\x2d28\x2d1804-19.mount > 646ms dev-loop19.device > 643ms snap-gtk\x2dcommon\x2dthemes-818.mount > 638ms dev-loop23.device > 626ms snap-gnome\x2dlogs-57.mount > 626ms dev-loop26.device > 610ms snap-gnome\x2dsystem\x2dmonitor-70.mount > 596ms dev-loop21.device > 589ms dev-loop25.device > 587ms dev-loop20.device > 583ms dev-loop24.device > 528ms logrotate.service > 523ms systemd-journal-flush.service > 496ms dev-loop22.device > 491ms dev-loop30.device > 490ms dev-loop27.device > 487ms dev-loop28.device > 433ms networkd-dispatcher.service > 427ms snapd.service > 397ms ModemManager.service > 382ms snap-gnome\x2d3\x2d26\x2d1604-82.mount > 379ms snap-gnome\x2dcalculator-352.mount > 369ms snap-remmina-2819.mount > 362ms snap-gnome\x2d3\x2d28\x2d1804-23.mount > 359ms snap-gnome\x2dsystem\x2dmonitor-57.mount > 340ms accounts-daemon.service > 307ms systemd-logind.service > 281ms keyboard-setup.service > 280ms kmod-static-nodes.service > 261ms dev-hugepages.mount > 260ms avahi-daemon.service > 259ms sys-kernel-debug.mount > 259ms ufw.service > 255ms apport-autoreport.service > 251ms systemd-udev-trigger.service > 242ms systemd-modules-load.service > 232ms systemd-journald.service > 230ms fwupd.service > 206ms apport.service > 196ms dev-mqueue.mount > 194ms apparmor.service > 186ms
[Touch-packages] [Bug 1933023] Re: tc lacks Cake qdisc in 18.04 + HWE 5.4 kernel
** Tags added: upgrade-software-version ** Tags added: iproute2 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to iproute2 in Ubuntu. https://bugs.launchpad.net/bugs/1933023 Title: tc lacks Cake qdisc in 18.04 + HWE 5.4 kernel Status in iproute2 package in Ubuntu: New Bug description: I am using the 5.4 HWE kernel in 18.04, and even though this kernel has the CAKE qdisc, I am unable to use it as the version of tc, which is used to configure it, is too old. Even the backported tc is too old. Can we get the 20.04 iproute2 package, which does support the CAKE qdisc, backported to 18.04 to fix this? P.S. I did try pulling iproute2 directly from 20.04 repos using apt pinning, but then had glibc version incomptibility problems. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/1933023/+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 1933023] Re: tc lacks Cake qdisc in 18.04 + HWE 5.4 kernel
** Description changed: I am using the 5.4 HWE kernel in 18.04, and even though this kernel has the CAKE qdisc, I am unable to use it as the version of tc, which is used to configure it, is too old. Even the backported tc is too old. Can we get the 20.04 iproute2 package, which does support the CAKE qdisc, backported to 18.04 to fix this? + + P.S. I did try pulling iproute2 directly from 20.04 repos using apt + pinning, but then had glibc version incomptibility problems. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to iproute2 in Ubuntu. https://bugs.launchpad.net/bugs/1933023 Title: tc lacks Cake qdisc in 18.04 + HWE 5.4 kernel Status in iproute2 package in Ubuntu: New Bug description: I am using the 5.4 HWE kernel in 18.04, and even though this kernel has the CAKE qdisc, I am unable to use it as the version of tc, which is used to configure it, is too old. Even the backported tc is too old. Can we get the 20.04 iproute2 package, which does support the CAKE qdisc, backported to 18.04 to fix this? P.S. I did try pulling iproute2 directly from 20.04 repos using apt pinning, but then had glibc version incomptibility problems. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/1933023/+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 1933023] [NEW] tc lacks Cake qdisc in 18.04 + HWE 5.4 kernel
Public bug reported: I am using the 5.4 HWE kernel in 18.04, and even though this kernel has the CAKE qdisc, I am unable to use it as the version of tc, which is used to configure it, is too old. Even the backported tc is too old. Can we get the 20.04 iproute2 package, which does support the CAKE qdisc, backported to 18.04 to fix this? ** Affects: iproute2 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to iproute2 in Ubuntu. https://bugs.launchpad.net/bugs/1933023 Title: tc lacks Cake qdisc in 18.04 + HWE 5.4 kernel Status in iproute2 package in Ubuntu: New Bug description: I am using the 5.4 HWE kernel in 18.04, and even though this kernel has the CAKE qdisc, I am unable to use it as the version of tc, which is used to configure it, is too old. Even the backported tc is too old. Can we get the 20.04 iproute2 package, which does support the CAKE qdisc, backported to 18.04 to fix this? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/1933023/+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 1502045] Re: Move from consolekit to logind
** Changed in: solaar (Ubuntu) Status: Triaged => Fix Released -- 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/1502045 Title: Move from consolekit to logind Status in lxdm package in Ubuntu: Fix Released Status in lxsession package in Ubuntu: Fix Released Status in mate-power-manager package in Ubuntu: Fix Released Status in openssh package in Ubuntu: Fix Released Status in polkit-qt-1 package in Ubuntu: Triaged Status in solaar package in Ubuntu: Fix Released Status in sugar package in Ubuntu: Triaged Status in tcosmonitor package in Ubuntu: Fix Released Status in ulatencyd package in Ubuntu: Triaged Status in lxdm package in Debian: Fix Released Status in tcosmonitor package in Debian: Fix Released Bug description: consolekit has been dead upstream for a long time. Ubuntu moved to logind in saucy (13.10), and we don't support consolekit any more. There are a few packages which still depend on it, most notably openssh, lxdm, and lxsession{,-logout}. For Ubuntu 16.04 we really should get rid of CK. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxdm/+bug/1502045/+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 1907510] Re: Apt-get upgrade fails with checksum errors
No joy, same error. -Original Message- >From: Daniel Letzeisen <1907...@bugs.launchpad.net> >Sent: Dec 10, 2020 3:34 AM >To: s...@sprynet.com >Subject: [Bug 1907510] Re: Apt-get upgrade fails with checksum errors > >Probably just a transmission glitch. Clear out the apt cache and try again. >sudo apt-get clean >sudo apt-get update > >Let us know if it works. > >** Package changed: ubuntu => apt (Ubuntu) > >** Changed in: apt (Ubuntu) > Status: New => Incomplete > >-- >You received this bug notification because you are subscribed to the bug >report. >https://bugs.launchpad.net/bugs/1907510 > >Title: > Apt-get upgrade fails with checksum errors > >Status in apt package in Ubuntu: > Incomplete > >Bug description: > scw@ellen:~$ lsb_release -rd > Description:Ubuntu 20.04.1 LTS > Release:20.04 > ? > I expected a number of packages to be upgraded > What I got was this: > > > > > Err:3 http://us.archive.ubuntu.com/ubuntu focal-updates/main amd64 > linux-firmware all 1.187.6 >Hash Sum mismatch >Hashes of expected file: > - > SHA512:b198b64b10643e8515f870c1e8e3edcfec446d1ff82780d50d04b859e14a3448f22ffe1d42a25c73fe8e746e4a764032798d02fdf3287cd8eb378f903d358a59 > - SHA256:9e128cf120150f7165b94edd1ac0e0ab32aa799b427523d98abcfe68030b6e12 > - SHA1:366eb2906eceb6acf17f4db1e6b02f8b4542f2e4 [weak] > - MD5Sum:d6b26be80cf8a51822628cd412202b81 [weak] > - Filesize:99497284 [weak] >Hashes of received file: > - > SHA512:6c842fe3eaaa4148939a8dc59472e4229f221b500ea5c7d506d62b218c3d42b9f352f3ae7dc75fc7c9b9bae743abcfce45e5145cf9a05b976c32fb94e713deba > - SHA256:429e462403f7680d8377d845ab0d1be8b625339d24a440d226d0622af9a56d98 > - SHA1:d506c2bf77b76b5b3e8c008b649a066353dc999f [weak] > - MD5Sum:1f56350abd87c4bc6bb3291f0412cded [weak] > - Filesize:99497284 [weak] >Last modification reported: Thu, 26 Nov 2020 17:18:59 + > Fetched 99.7 MB in 14s (6,967 kB/s) > E: Failed to fetch > http://us.archive.ubuntu.com/ubuntu/pool/main/l/linux-firmware/linux-firmware_1.187.6_all.deb > Hash Sum mismatch > Hashes of expected file: > - > SHA512:b198b64b10643e8515f870c1e8e3edcfec446d1ff82780d50d04b859e14a3448f22ffe1d42a25c73fe8e746e4a764032798d02fdf3287cd8eb378f903d358a59 > - SHA256:9e128cf120150f7165b94edd1ac0e0ab32aa799b427523d98abcfe68030b6e12 > - SHA1:366eb2906eceb6acf17f4db1e6b02f8b4542f2e4 [weak] > - MD5Sum:d6b26be80cf8a51822628cd412202b81 [weak] > - Filesize:99497284 [weak] > Hashes of received file: > - > SHA512:6c842fe3eaaa4148939a8dc59472e4229f221b500ea5c7d506d62b218c3d42b9f352f3ae7dc75fc7c9b9bae743abcfce45e5145cf9a05b976c32fb94e713deba > - SHA256:429e462403f7680d8377d845ab0d1be8b625339d24a440d226d0622af9a56d98 > - SHA1:d506c2bf77b76b5b3e8c008b649a066353dc999f [weak] > - MD5Sum:1f56350abd87c4bc6bb3291f0412cded [weak] > - Filesize:99497284 [weak] > Last modification reported: Thu, 26 Nov 2020 17:18:59 + > >To manage notifications about this bug go to: >https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1907510/+subscriptions -- 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/1907510 Title: Apt-get upgrade fails with checksum errors Status in apt package in Ubuntu: Incomplete Bug description: scw@ellen:~$ lsb_release -rd Description:Ubuntu 20.04.1 LTS Release:20.04 ? I expected a number of packages to be upgraded What I got was this: Err:3 http://us.archive.ubuntu.com/ubuntu focal-updates/main amd64 linux-firmware all 1.187.6 Hash Sum mismatch Hashes of expected file: - SHA512:b198b64b10643e8515f870c1e8e3edcfec446d1ff82780d50d04b859e14a3448f22ffe1d42a25c73fe8e746e4a764032798d02fdf3287cd8eb378f903d358a59 - SHA256:9e128cf120150f7165b94edd1ac0e0ab32aa799b427523d98abcfe68030b6e12 - SHA1:366eb2906eceb6acf17f4db1e6b02f8b4542f2e4 [weak] - MD5Sum:d6b26be80cf8a51822628cd412202b81 [weak] - Filesize:99497284 [weak] Hashes of received file: - SHA512:6c842fe3eaaa4148939a8dc59472e4229f221b500ea5c7d506d62b218c3d42b9f352f3ae7dc75fc7c9b9bae743abcfce45e5145cf9a05b976c32fb94e713deba - SHA256:429e462403f7680d8377d845ab0d1be8b625339d24a440d226d0622af9a56d98 - SHA1:d506c2bf77b76b5b3e8c008b649a066353dc999f [weak] - MD5Sum:1f56350abd87c4bc6bb3291f0412cded [weak] - Filesize:99497284 [weak] Last modification reported: Thu, 26 Nov 2020 17:18:59 + Fetched 99.7 MB in 14s (6,967 kB/s) E: Failed to fetch http://us.archive.ubuntu.com/ubuntu/pool/main/l/linux-firmware/linux-firmware_1.187.6_all.deb Hash Sum mismatch Hashes of expected file: - SHA512:b198b64b10643e8515f870c1e8e3edcfec446d1ff82780d50d04b859e14a3448f22ffe1d42a25c73fe8e746e4a764032798d02fdf3287cd8eb378f903d358a59 - SHA256:9e128cf120150f7165b94edd1ac0e0ab32aa799b427523d98abcfe68030b6e12 -
[Touch-packages] [Bug 1871268] Re: Installation fails due to useless immediate configuration error when "Install Third-Party Drivers" is selected
I can add another "me too" on a Asus K73SV laptop with NVIDIA GeForce GT 540M. With "Install updates during install" and "Install third party drivers" checked I got the error which redirected me here. When I rebooted I was greeted with a black boot screen that not made it into GDM. After installing again but this time without "Install third party drivers" checked the installation worked normally. Immediately was greeted with updates to install, though I had "Install updates during install" still checked. I am very disappointed, especially since this issue has been known for over 8 months. This is the reason I wait some time before installing the new LTS. This should have been fixed in 20.04.1 already. -- 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/1871268 Title: Installation fails due to useless immediate configuration error when "Install Third-Party Drivers" is selected Status in Ubuntu CD Images: Fix Released Status in apt package in Ubuntu: Fix Released Status in apt source package in Bionic: Confirmed Status in apt source package in Focal: Triaged Status in apt source package in Groovy: Triaged Status in apt package in Debian: Unknown Bug description: [Impact] Installations that really succeeded would then fail because APT could not immediately configure a package. Which is a pointless way to fail at that point, because everything did work out anyway. So what we do is change that to a warning. [Test case] Not available right now. Issues can flare up and then disappear again. [Regression potential] It's imaginable that we missed something somewhere and some path that checked for a set error doesn't check it anymore, and we report success when we hit an error, but it seems unlikely. Behavior of --simulate changes. This used to fail before as well, and will now only produce a warning. We don't believe that is a reason of concern. [Groovy SRU] The groovy SRU is a sync of the 2.1.11 micro release from Debian unstable which also incorporates changes to the documentation: A typo fix, replacing focal with groovy in examples, and minor Dutch manual pages translation updates. We do not have test cases for the documentation changes, and we do not consider there to be a huge regression potential. As long as they build, they should be readable - maybe some words are wrong in the translation, who knows. [Original bug report] Test Case 1. Install Ubuntu Desktop on hardware with an nVidia card and select to install 3rd party drivers 2. Proceed with installation The following error message is displayed in /var/log/syslog /plugininstall.py: Verifying downloads ... /plugininstall.py: Failed to find package object for /cdrom//pool/main/g/gcc-defaults/gcc_9.3.0-1ubuntu2_amd64.deb: "Version: '9.3.0-1ubuntu2' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libxcrypt/libcrypt-dev_4.4.10-10ubuntu4_amd64.deb: "Version: '4.4.10-10ubuntu4' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/g/gcc-defaults/g++_9.3.0-1ubuntu2_amd64.deb: "Version: '9.3.0-1ubuntu2' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/z/zlib/zlib1g_1.2.11.dfsg-2ubuntu1_i386.deb: "Version: '1.2.11.dfsg-2ubuntu1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libxau/libxau6_1.0.9-0ubuntu1_i386.deb: "Version: '1.0.9-0ubuntu1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libxdmcp/libxdmcp6_1.1.3-0ubuntu1_i386.deb: "Version: '1.1.3-0ubuntu1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libx11/libx11-6_1.6.9-2ubuntu1_i386.deb: "Version: '1.6.9-2ubuntu1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libxext/libxext6_1.3.4-0ubuntu1_i386.deb: "Version: '1.3.4-0ubuntu1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/l/lm-sensors/libsensors5_3.6.0-2ubuntu1_i386.deb: "Version: '3.6.0-2ubuntu1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libx11/libx11-xcb1_1.6.9-2ubuntu1_i386.deb: "Version: '1.6.9-2ubuntu1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libxdamage/libxdamage1_1.1.5-1_i386.deb: "Version: '1.1.5-1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libxfixes/libxfixes3_5.0.3-1_i386.deb: "Version: '5.0.3-1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libxxf86vm/libxxf86vm1_1.1.4-1build1_i386.deb: "Version: '1.1.4-1build1' not found." /plugininstall.py: Downloads verified successfully ubiquity: Error in function: install
Re: [Touch-packages] [Bug 1539999] Re: Omnikey Cardreader not working
Not still an issue as far as I know but I haven't used the card reader for over 2yrs. Thank you On 2020-10-07 22:28, Joy Latten wrote: > Is this still an issue? Changing to incomplete. > > ** Changed in: pcsc-lite (Ubuntu) > Status: New => Incomplete > > -- > You received this bug notification because you are subscribed to the > bug > report. > https://bugs.launchpad.net/bugs/153 > > Title: > Omnikey Cardreader not working > > Status in pcsc-lite package in Ubuntu: > Incomplete > > Bug description: > On my desktop & sony vaio laptop, Alpha 2 Ubuntu-mate does not start my > usb Omnikey 3121 card reader. > The 3121 is listed in terminal when I perform 'lsusb'. The reader does > work under concurrent devuan 1. I have installed pcscd (which drags in > libccid correctly) & pcsc-tools but this hasn't corrected the problem > even with a reboot. > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/pcsc-lite/+bug/153/+subscriptions -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pcsc-lite in Ubuntu. https://bugs.launchpad.net/bugs/153 Title: Omnikey Cardreader not working Status in pcsc-lite package in Ubuntu: Incomplete Bug description: On my desktop & sony vaio laptop, Alpha 2 Ubuntu-mate does not start my usb Omnikey 3121 card reader. The 3121 is listed in terminal when I perform 'lsusb'. The reader does work under concurrent devuan 1. I have installed pcscd (which drags in libccid correctly) & pcsc-tools but this hasn't corrected the problem even with a reboot. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pcsc-lite/+bug/153/+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 1891110] [NEW] Focal ucf need redirect fixes backported to ensure working with config-package-dev
Public bug reported: When using config-package-dev and diverting config files for packages that use ucf to manage installation of their config files, this patch is necessary to ensure config files are correctly diverted. Please apply to upstream Focal UCF package ** Affects: ucf (Ubuntu) Importance: Undecided Status: New ** Patch added: "patches from ucf 3.0040 to fix diversions issue with config-package-dev" https://bugs.launchpad.net/bugs/1891110/+attachment/5400552/+files/honor-dpkg-diversions-1+2+3.patch -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ucf in Ubuntu. https://bugs.launchpad.net/bugs/1891110 Title: Focal ucf need redirect fixes backported to ensure working with config-package-dev Status in ucf package in Ubuntu: New Bug description: When using config-package-dev and diverting config files for packages that use ucf to manage installation of their config files, this patch is necessary to ensure config files are correctly diverted. Please apply to upstream Focal UCF package To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ucf/+bug/1891110/+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 1883054] Re: Built-in audio device not available until alsa is reloaded
For me, this issue has now been resolved; I assume due to the pulseaudio package updates that I installed yesterday, but it might have been fixed for a few days longer. ** Changed in: alsa-driver (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-driver in Ubuntu. https://bugs.launchpad.net/bugs/1883054 Title: Built-in audio device not available until alsa is reloaded Status in alsa-driver package in Ubuntu: Fix Released Bug description: I had Ubuntu 18.04 installed, running XFCE (Xubuntu session), and audio worked fine, using either the built-in speakers/mic on the laptop or via a USB headset when that was plugged in. However, after upgrading to 20.04, the built-in audio device is no longer available until I run "sudo alsa force-reload". Wthhout that WAR, all I see is a dummy audio device. Luckily the USB headset works fine, if plugged in. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 Uname: Linux 5.4.0-33-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: swarren7664 F pulseaudio /dev/snd/controlC0: swarren7664 F pulseaudio /dev/snd/pcmC0D0c: swarren7664 F...m pulseaudio /dev/snd/pcmC0D0p: swarren7664 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: XFCE Date: Wed Jun 10 23:57:08 2020 InstallationDate: Installed on 2016-03-03 (1561 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160122.2) PackageArchitecture: all SourcePackage: alsa-driver UpgradeStatus: Upgraded to focal on 2020-06-07 (4 days ago) dmi.bios.date: 08/28/2019 dmi.bios.vendor: LENOVO dmi.bios.version: N1DETA6W (2.32 ) dmi.board.asset.tag: Not Available dmi.board.name: 20ERCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN1DETA6W(2.32):bd08/28/2019:svnLENOVO:pn20ERCTO1WW:pvrThinkPadP70:rvnLENOVO:rn20ERCTO1WW:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad P70 dmi.product.name: 20ERCTO1WW dmi.product.sku: LENOVO_MT_20ER_BU_Think_FM_ThinkPad P70 dmi.product.version: ThinkPad P70 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1883054/+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 1883412] Re: 20.04: DNS servers from /etc/network/interfaces not honored by systemd-resolve
Sorry, please ignore my previous comment (comment 6); I'd copied the netplan config from another machine and adjusted all the IPs, but forgot to change the interface name, so the entries were ignored. Basic IP connectivity was working since I have an encrypted volume that's unlocked via the initrd, so the initrd sets up the IP/netmask/gateway, and these simply carried over once the rootfs was mounted; netplan/... didn't clear them out luckily. -- 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/1883412 Title: 20.04: DNS servers from /etc/network/interfaces not honored by systemd-resolve Status in systemd package in Ubuntu: Incomplete Bug description: I have a server that uses /etc/network/interfaces to configure static IP info, including DNS, via /etc/network/interfaces. This worked fine in 16.04 and 18.04. However, when I updated to 20.04 this no longer works; I have to run "systemd-resolve --set-dns=192.168.63.1 --interface=enp3s0" to fix it after every boot. My /etc/network/interfaces is: # Loopback auto lo iface lo inet loopback # enp3s0: LAN (Motherboard) auto enp3s0 iface enp3s0 inet static address 192.168.63.2 netmask 255.255.255.0 network 192.168.63.0 broadcast 192.168.63.255 gateway 192.168.63.1 dns-nameservers 192.168.63.1 iface enp3s0 inet6 static address 2001:470:bb52:63::2/64 netmask 64 # WiFi USB # FIXME: Probably will get renamed on boot #allow-hotplug ethFlashAirWifi #iface ethFlashAirWifi inet manual "systemd-resolve --status" outputs the following beforr I run the WAR command given above: Global LLMNR setting: no MulticastDNS setting: no DNSOverTLS setting: no DNSSEC setting: no DNSSEC supported: no DNSSEC NTA: 10.in-addr.arpa 16.172.in-addr.arpa 168.192.in-addr.arpa 17.172.in-addr.arpa 18.172.in-addr.arpa 19.172.in-addr.arpa 20.172.in-addr.arpa 21.172.in-addr.arpa 22.172.in-addr.arpa 23.172.in-addr.arpa 24.172.in-addr.arpa 25.172.in-addr.arpa 26.172.in-addr.arpa 27.172.in-addr.arpa 28.172.in-addr.arpa 29.172.in-addr.arpa 30.172.in-addr.arpa 31.172.in-addr.arpa corp d.f.ip6.arpa home internal intranet lan local private test Link 4 (tun0) Current Scopes: none DefaultRoute setting: no LLMNR setting: yes MulticastDNS setting: no DNSOverTLS setting: no DNSSEC setting: no DNSSEC supported: no Link 3 (lxcbr0) Current Scopes: none DefaultRoute setting: no LLMNR setting: yes MulticastDNS setting: no DNSOverTLS setting: no DNSSEC setting: no DNSSEC supported: no Link 2 (enp3s0) Current Scopes: none DefaultRoute setting: no LLMNR setting: yes MulticastDNS setting: no DNSOverTLS setting: no DNSSEC setting: no DNSSEC supported: no ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: systemd 245.4-4ubuntu3.1 ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41 Uname: Linux 5.4.0-37-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 CasperMD5CheckResult: skip Date: Sun Jun 14 01:58:10 2020 InstallationDate: Installed on 2016-04-12 (1524 days ago) InstallationMedia: Ubuntu-Server 16.04 LTS "Xenial Xerus" - Beta amd64 (20160408) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-37-generic root=/dev/mapper/severn_vg2016-lv_root ro SourcePackage: systemd UpgradeStatus: Upgraded to focal on 2020-06-14 (0 days ago) dmi.bios.date: 06/18/2010 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P2.40 dmi.board.name: 890GX Extreme3 dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor:
[Touch-packages] [Bug 1883412] Re: 20.04: DNS servers from /etc/network/interfaces not honored by systemd-resolve
Uggh. On a second system that I upgraded 16.04->18.04->20.04, I have netplan installed and a configuration file in place. However, the DNS entry in the netplan config is ignored, so even switching to netplan doesn't fix this bug:-( -- 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/1883412 Title: 20.04: DNS servers from /etc/network/interfaces not honored by systemd-resolve Status in systemd package in Ubuntu: Incomplete Bug description: I have a server that uses /etc/network/interfaces to configure static IP info, including DNS, via /etc/network/interfaces. This worked fine in 16.04 and 18.04. However, when I updated to 20.04 this no longer works; I have to run "systemd-resolve --set-dns=192.168.63.1 --interface=enp3s0" to fix it after every boot. My /etc/network/interfaces is: # Loopback auto lo iface lo inet loopback # enp3s0: LAN (Motherboard) auto enp3s0 iface enp3s0 inet static address 192.168.63.2 netmask 255.255.255.0 network 192.168.63.0 broadcast 192.168.63.255 gateway 192.168.63.1 dns-nameservers 192.168.63.1 iface enp3s0 inet6 static address 2001:470:bb52:63::2/64 netmask 64 # WiFi USB # FIXME: Probably will get renamed on boot #allow-hotplug ethFlashAirWifi #iface ethFlashAirWifi inet manual "systemd-resolve --status" outputs the following beforr I run the WAR command given above: Global LLMNR setting: no MulticastDNS setting: no DNSOverTLS setting: no DNSSEC setting: no DNSSEC supported: no DNSSEC NTA: 10.in-addr.arpa 16.172.in-addr.arpa 168.192.in-addr.arpa 17.172.in-addr.arpa 18.172.in-addr.arpa 19.172.in-addr.arpa 20.172.in-addr.arpa 21.172.in-addr.arpa 22.172.in-addr.arpa 23.172.in-addr.arpa 24.172.in-addr.arpa 25.172.in-addr.arpa 26.172.in-addr.arpa 27.172.in-addr.arpa 28.172.in-addr.arpa 29.172.in-addr.arpa 30.172.in-addr.arpa 31.172.in-addr.arpa corp d.f.ip6.arpa home internal intranet lan local private test Link 4 (tun0) Current Scopes: none DefaultRoute setting: no LLMNR setting: yes MulticastDNS setting: no DNSOverTLS setting: no DNSSEC setting: no DNSSEC supported: no Link 3 (lxcbr0) Current Scopes: none DefaultRoute setting: no LLMNR setting: yes MulticastDNS setting: no DNSOverTLS setting: no DNSSEC setting: no DNSSEC supported: no Link 2 (enp3s0) Current Scopes: none DefaultRoute setting: no LLMNR setting: yes MulticastDNS setting: no DNSOverTLS setting: no DNSSEC setting: no DNSSEC supported: no ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: systemd 245.4-4ubuntu3.1 ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41 Uname: Linux 5.4.0-37-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 CasperMD5CheckResult: skip Date: Sun Jun 14 01:58:10 2020 InstallationDate: Installed on 2016-04-12 (1524 days ago) InstallationMedia: Ubuntu-Server 16.04 LTS "Xenial Xerus" - Beta amd64 (20160408) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-37-generic root=/dev/mapper/severn_vg2016-lv_root ro SourcePackage: systemd UpgradeStatus: Upgraded to focal on 2020-06-14 (0 days ago) dmi.bios.date: 06/18/2010 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P2.40 dmi.board.name: 890GX Extreme3 dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias:
[Touch-packages] [Bug 1883412] Re: 20.04: DNS servers from /etc/network/interfaces not honored by systemd-resolve
The system has resolvconf 1.82 installed. /etc/resolv.conf claims that it's generated by resolvconf, at least after I switched the system to netplan, and I'm pretty sure it did before to. I also have ifupdown 0.8.35ubuntu1 installed. A thought on deprecation: A deprecated package is simply something that isn't suitable for new use. If the package still exists, it must still work correctly; known non-working software shouldn't be shipped. At the point that's no longer possible, it can be removed (hopefully with an automated transition plan in do-release-upgrade). -- 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/1883412 Title: 20.04: DNS servers from /etc/network/interfaces not honored by systemd-resolve Status in systemd package in Ubuntu: Incomplete Bug description: I have a server that uses /etc/network/interfaces to configure static IP info, including DNS, via /etc/network/interfaces. This worked fine in 16.04 and 18.04. However, when I updated to 20.04 this no longer works; I have to run "systemd-resolve --set-dns=192.168.63.1 --interface=enp3s0" to fix it after every boot. My /etc/network/interfaces is: # Loopback auto lo iface lo inet loopback # enp3s0: LAN (Motherboard) auto enp3s0 iface enp3s0 inet static address 192.168.63.2 netmask 255.255.255.0 network 192.168.63.0 broadcast 192.168.63.255 gateway 192.168.63.1 dns-nameservers 192.168.63.1 iface enp3s0 inet6 static address 2001:470:bb52:63::2/64 netmask 64 # WiFi USB # FIXME: Probably will get renamed on boot #allow-hotplug ethFlashAirWifi #iface ethFlashAirWifi inet manual "systemd-resolve --status" outputs the following beforr I run the WAR command given above: Global LLMNR setting: no MulticastDNS setting: no DNSOverTLS setting: no DNSSEC setting: no DNSSEC supported: no DNSSEC NTA: 10.in-addr.arpa 16.172.in-addr.arpa 168.192.in-addr.arpa 17.172.in-addr.arpa 18.172.in-addr.arpa 19.172.in-addr.arpa 20.172.in-addr.arpa 21.172.in-addr.arpa 22.172.in-addr.arpa 23.172.in-addr.arpa 24.172.in-addr.arpa 25.172.in-addr.arpa 26.172.in-addr.arpa 27.172.in-addr.arpa 28.172.in-addr.arpa 29.172.in-addr.arpa 30.172.in-addr.arpa 31.172.in-addr.arpa corp d.f.ip6.arpa home internal intranet lan local private test Link 4 (tun0) Current Scopes: none DefaultRoute setting: no LLMNR setting: yes MulticastDNS setting: no DNSOverTLS setting: no DNSSEC setting: no DNSSEC supported: no Link 3 (lxcbr0) Current Scopes: none DefaultRoute setting: no LLMNR setting: yes MulticastDNS setting: no DNSOverTLS setting: no DNSSEC setting: no DNSSEC supported: no Link 2 (enp3s0) Current Scopes: none DefaultRoute setting: no LLMNR setting: yes MulticastDNS setting: no DNSOverTLS setting: no DNSSEC setting: no DNSSEC supported: no ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: systemd 245.4-4ubuntu3.1 ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41 Uname: Linux 5.4.0-37-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 CasperMD5CheckResult: skip Date: Sun Jun 14 01:58:10 2020 InstallationDate: Installed on 2016-04-12 (1524 days ago) InstallationMedia: Ubuntu-Server 16.04 LTS "Xenial Xerus" - Beta amd64 (20160408) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-37-generic root=/dev/mapper/severn_vg2016-lv_root ro SourcePackage: systemd UpgradeStatus: Upgraded to focal on 2020-06-14 (0 days ago) dmi.bios.date: 06/18/2010 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P2.40 dmi.board.name: 890GX
[Touch-packages] [Bug 1883412] Re: 20.04: DNS servers from /etc/network/interfaces not honored by systemd-resolve
Switching to netplan does avoid this issue, but doesn't directly solve it. -- 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/1883412 Title: 20.04: DNS servers from /etc/network/interfaces not honored by systemd-resolve Status in systemd package in Ubuntu: New Bug description: I have a server that uses /etc/network/interfaces to configure static IP info, including DNS, via /etc/network/interfaces. This worked fine in 16.04 and 18.04. However, when I updated to 20.04 this no longer works; I have to run "systemd-resolve --set-dns=192.168.63.1 --interface=enp3s0" to fix it after every boot. My /etc/network/interfaces is: # Loopback auto lo iface lo inet loopback # enp3s0: LAN (Motherboard) auto enp3s0 iface enp3s0 inet static address 192.168.63.2 netmask 255.255.255.0 network 192.168.63.0 broadcast 192.168.63.255 gateway 192.168.63.1 dns-nameservers 192.168.63.1 iface enp3s0 inet6 static address 2001:470:bb52:63::2/64 netmask 64 # WiFi USB # FIXME: Probably will get renamed on boot #allow-hotplug ethFlashAirWifi #iface ethFlashAirWifi inet manual "systemd-resolve --status" outputs the following beforr I run the WAR command given above: Global LLMNR setting: no MulticastDNS setting: no DNSOverTLS setting: no DNSSEC setting: no DNSSEC supported: no DNSSEC NTA: 10.in-addr.arpa 16.172.in-addr.arpa 168.192.in-addr.arpa 17.172.in-addr.arpa 18.172.in-addr.arpa 19.172.in-addr.arpa 20.172.in-addr.arpa 21.172.in-addr.arpa 22.172.in-addr.arpa 23.172.in-addr.arpa 24.172.in-addr.arpa 25.172.in-addr.arpa 26.172.in-addr.arpa 27.172.in-addr.arpa 28.172.in-addr.arpa 29.172.in-addr.arpa 30.172.in-addr.arpa 31.172.in-addr.arpa corp d.f.ip6.arpa home internal intranet lan local private test Link 4 (tun0) Current Scopes: none DefaultRoute setting: no LLMNR setting: yes MulticastDNS setting: no DNSOverTLS setting: no DNSSEC setting: no DNSSEC supported: no Link 3 (lxcbr0) Current Scopes: none DefaultRoute setting: no LLMNR setting: yes MulticastDNS setting: no DNSOverTLS setting: no DNSSEC setting: no DNSSEC supported: no Link 2 (enp3s0) Current Scopes: none DefaultRoute setting: no LLMNR setting: yes MulticastDNS setting: no DNSOverTLS setting: no DNSSEC setting: no DNSSEC supported: no ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: systemd 245.4-4ubuntu3.1 ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41 Uname: Linux 5.4.0-37-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 CasperMD5CheckResult: skip Date: Sun Jun 14 01:58:10 2020 InstallationDate: Installed on 2016-04-12 (1524 days ago) InstallationMedia: Ubuntu-Server 16.04 LTS "Xenial Xerus" - Beta amd64 (20160408) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-37-generic root=/dev/mapper/severn_vg2016-lv_root ro SourcePackage: systemd UpgradeStatus: Upgraded to focal on 2020-06-14 (0 days ago) dmi.bios.date: 06/18/2010 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P2.40 dmi.board.name: 890GX Extreme3 dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP2.40:bd06/18/2010:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rn890GXExtreme3:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M.
[Touch-packages] [Bug 1879206] Re: cups hplip not install printer
sudo apt purge ippusbxd worked for me (after I tried lots) Thx to Brian in https://answers.launchpad.net/hplip/+question/691227 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1879206 Title: cups hplip not install printer Status in cups package in Ubuntu: Incomplete Status in hplip package in Ubuntu: Incomplete Bug description: After upgrading to Ubuntu 20.04 I can't print anymore. Description: Ubuntu 20.04 LTS Release: 20.04 cups: Installato: 2.3.1-9ubuntu1.1 Candidato: 2.3.1-9ubuntu1.1 Tabella versione: *** 2.3.1-9ubuntu1.1 500 500 http://it.archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu focal-security/main amd64 Packages 100 /var/lib/dpkg/status 2.3.1-9ubuntu1 500 500 http://it.archive.ubuntu.com/ubuntu focal/main amd64 Packages hplip: Installato: 3.20.3+dfsg0-2 Candidato: 3.20.3+dfsg0-2 Tabella versione: *** 3.20.3+dfsg0-2 500 500 http://it.archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status I tried to reinstall the printer, but it is not being re-saved by cups / hplip ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: cups 2.3.1-9ubuntu1.1 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon May 18 02:24:07 2020 InstallationDate: Installed on 2020-05-17 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Lpstat: device for DeskJet_3630: hp:/usb/DeskJet_3630_series?serial=CN8AM7H3230658 MachineType: LENOVO 80G0 Papersize: a4 PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/DeskJet_3630.ppd'] failed with exit code 2: grep: /etc/cups/ppd/DeskJet_3630.ppd: Permission denied ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-29-generic root=UUID=6a8469e0-ecea-4a86-8040-b0caaa938fe4 ro quiet splash vt.handoff=7 SourcePackage: cups UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/18/2014 dmi.bios.vendor: LENOVO dmi.bios.version: A7CN40WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: Lancer 5A6 dmi.board.vendor: LENOVO dmi.board.version: SDK0F82993WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo G50-30 dmi.modalias: dmi:bvnLENOVO:bvrA7CN40WW:bd07/18/2014:svnLENOVO:pn80G0:pvrLenovoG50-30:rvnLENOVO:rnLancer5A6:rvrSDK0F82993WIN:cvnLENOVO:ct10:cvrLenovoG50-30: dmi.product.family: IDEAPAD dmi.product.name: 80G0 dmi.product.sku: LENOVO_MT_80G0_BU_idea_FM_Lenovo G50-30 dmi.product.version: Lenovo G50-30 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1879206/+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 1883412] Re: 20.04: DNS servers from /etc/network/interfaces not honored by systemd-resolve
Oh, and /etc/resolv.conf contains: # Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8) # DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN # 127.0.0.53 is the systemd-resolved stub resolver. # run "systemd-resolve --status" to see details about the actual nameservers. nameserver 127.0.0.53 -- 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/1883412 Title: 20.04: DNS servers from /etc/network/interfaces not honored by systemd-resolve Status in systemd package in Ubuntu: New Bug description: I have a server that uses /etc/network/interfaces to configure static IP info, including DNS, via /etc/network/interfaces. This worked fine in 16.04 and 18.04. However, when I updated to 20.04 this no longer works; I have to run "systemd-resolve --set-dns=192.168.63.1 --interface=enp3s0" to fix it after every boot. My /etc/network/interfaces is: # Loopback auto lo iface lo inet loopback # enp3s0: LAN (Motherboard) auto enp3s0 iface enp3s0 inet static address 192.168.63.2 netmask 255.255.255.0 network 192.168.63.0 broadcast 192.168.63.255 gateway 192.168.63.1 dns-nameservers 192.168.63.1 iface enp3s0 inet6 static address 2001:470:bb52:63::2/64 netmask 64 # WiFi USB # FIXME: Probably will get renamed on boot #allow-hotplug ethFlashAirWifi #iface ethFlashAirWifi inet manual "systemd-resolve --status" outputs the following beforr I run the WAR command given above: Global LLMNR setting: no MulticastDNS setting: no DNSOverTLS setting: no DNSSEC setting: no DNSSEC supported: no DNSSEC NTA: 10.in-addr.arpa 16.172.in-addr.arpa 168.192.in-addr.arpa 17.172.in-addr.arpa 18.172.in-addr.arpa 19.172.in-addr.arpa 20.172.in-addr.arpa 21.172.in-addr.arpa 22.172.in-addr.arpa 23.172.in-addr.arpa 24.172.in-addr.arpa 25.172.in-addr.arpa 26.172.in-addr.arpa 27.172.in-addr.arpa 28.172.in-addr.arpa 29.172.in-addr.arpa 30.172.in-addr.arpa 31.172.in-addr.arpa corp d.f.ip6.arpa home internal intranet lan local private test Link 4 (tun0) Current Scopes: none DefaultRoute setting: no LLMNR setting: yes MulticastDNS setting: no DNSOverTLS setting: no DNSSEC setting: no DNSSEC supported: no Link 3 (lxcbr0) Current Scopes: none DefaultRoute setting: no LLMNR setting: yes MulticastDNS setting: no DNSOverTLS setting: no DNSSEC setting: no DNSSEC supported: no Link 2 (enp3s0) Current Scopes: none DefaultRoute setting: no LLMNR setting: yes MulticastDNS setting: no DNSOverTLS setting: no DNSSEC setting: no DNSSEC supported: no ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: systemd 245.4-4ubuntu3.1 ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41 Uname: Linux 5.4.0-37-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 CasperMD5CheckResult: skip Date: Sun Jun 14 01:58:10 2020 InstallationDate: Installed on 2016-04-12 (1524 days ago) InstallationMedia: Ubuntu-Server 16.04 LTS "Xenial Xerus" - Beta amd64 (20160408) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-37-generic root=/dev/mapper/severn_vg2016-lv_root ro SourcePackage: systemd UpgradeStatus: Upgraded to focal on 2020-06-14 (0 days ago) dmi.bios.date: 06/18/2010 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P2.40 dmi.board.name: 890GX Extreme3 dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias:
[Touch-packages] [Bug 1883412] [NEW] 20.04: DNS servers from /etc/network/interfaces not honored by systemd-resolve
Public bug reported: I have a server that uses /etc/network/interfaces to configure static IP info, including DNS, via /etc/network/interfaces. This worked fine in 16.04 and 18.04. However, when I updated to 20.04 this no longer works; I have to run "systemd-resolve --set-dns=192.168.63.1 --interface=enp3s0" to fix it after every boot. My /etc/network/interfaces is: # Loopback auto lo iface lo inet loopback # enp3s0: LAN (Motherboard) auto enp3s0 iface enp3s0 inet static address 192.168.63.2 netmask 255.255.255.0 network 192.168.63.0 broadcast 192.168.63.255 gateway 192.168.63.1 dns-nameservers 192.168.63.1 iface enp3s0 inet6 static address 2001:470:bb52:63::2/64 netmask 64 # WiFi USB # FIXME: Probably will get renamed on boot #allow-hotplug ethFlashAirWifi #iface ethFlashAirWifi inet manual "systemd-resolve --status" outputs the following beforr I run the WAR command given above: Global LLMNR setting: no MulticastDNS setting: no DNSOverTLS setting: no DNSSEC setting: no DNSSEC supported: no DNSSEC NTA: 10.in-addr.arpa 16.172.in-addr.arpa 168.192.in-addr.arpa 17.172.in-addr.arpa 18.172.in-addr.arpa 19.172.in-addr.arpa 20.172.in-addr.arpa 21.172.in-addr.arpa 22.172.in-addr.arpa 23.172.in-addr.arpa 24.172.in-addr.arpa 25.172.in-addr.arpa 26.172.in-addr.arpa 27.172.in-addr.arpa 28.172.in-addr.arpa 29.172.in-addr.arpa 30.172.in-addr.arpa 31.172.in-addr.arpa corp d.f.ip6.arpa home internal intranet lan local private test Link 4 (tun0) Current Scopes: none DefaultRoute setting: no LLMNR setting: yes MulticastDNS setting: no DNSOverTLS setting: no DNSSEC setting: no DNSSEC supported: no Link 3 (lxcbr0) Current Scopes: none DefaultRoute setting: no LLMNR setting: yes MulticastDNS setting: no DNSOverTLS setting: no DNSSEC setting: no DNSSEC supported: no Link 2 (enp3s0) Current Scopes: none DefaultRoute setting: no LLMNR setting: yes MulticastDNS setting: no DNSOverTLS setting: no DNSSEC setting: no DNSSEC supported: no ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: systemd 245.4-4ubuntu3.1 ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41 Uname: Linux 5.4.0-37-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 CasperMD5CheckResult: skip Date: Sun Jun 14 01:58:10 2020 InstallationDate: Installed on 2016-04-12 (1524 days ago) InstallationMedia: Ubuntu-Server 16.04 LTS "Xenial Xerus" - Beta amd64 (20160408) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-37-generic root=/dev/mapper/severn_vg2016-lv_root ro SourcePackage: systemd UpgradeStatus: Upgraded to focal on 2020-06-14 (0 days ago) dmi.bios.date: 06/18/2010 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P2.40 dmi.board.name: 890GX Extreme3 dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP2.40:bd06/18/2010:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rn890GXExtreme3:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- 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/1883412 Title: 20.04: DNS servers from /etc/network/interfaces not honored by systemd-resolve Status in systemd package in Ubuntu: New Bug description: I have a server that uses /etc/network/interfaces to configure
[Touch-packages] [Bug 1883054] Re: Built-in audio device not available until alsa is reloaded
My headset (which works fine) is USB. Which bug do you believe this is a duplicate of? I did find something similar, but it was on 16.04, and my issue is definitely a regression between 18.04 and 20.04. -- 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/1883054 Title: Built-in audio device not available until alsa is reloaded Status in alsa-driver package in Ubuntu: New Bug description: I had Ubuntu 18.04 installed, running XFCE (Xubuntu session), and audio worked fine, using either the built-in speakers/mic on the laptop or via a USB headset when that was plugged in. However, after upgrading to 20.04, the built-in audio device is no longer available until I run "sudo alsa force-reload". Wthhout that WAR, all I see is a dummy audio device. Luckily the USB headset works fine, if plugged in. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 Uname: Linux 5.4.0-33-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: swarren7664 F pulseaudio /dev/snd/controlC0: swarren7664 F pulseaudio /dev/snd/pcmC0D0c: swarren7664 F...m pulseaudio /dev/snd/pcmC0D0p: swarren7664 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: XFCE Date: Wed Jun 10 23:57:08 2020 InstallationDate: Installed on 2016-03-03 (1561 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160122.2) PackageArchitecture: all SourcePackage: alsa-driver UpgradeStatus: Upgraded to focal on 2020-06-07 (4 days ago) dmi.bios.date: 08/28/2019 dmi.bios.vendor: LENOVO dmi.bios.version: N1DETA6W (2.32 ) dmi.board.asset.tag: Not Available dmi.board.name: 20ERCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN1DETA6W(2.32):bd08/28/2019:svnLENOVO:pn20ERCTO1WW:pvrThinkPadP70:rvnLENOVO:rn20ERCTO1WW:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad P70 dmi.product.name: 20ERCTO1WW dmi.product.sku: LENOVO_MT_20ER_BU_Think_FM_ThinkPad P70 dmi.product.version: ThinkPad P70 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1883054/+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 1883054] Re: Built-in audio device not available until alsa is reloaded
I ran alsa-info before/after running "sudo alsa force-reload" to see if there were any obvious differences in the output. While there are a few differences, nothing really stands out as causing this issue. ** Attachment added: "diff for alsa-info output before/after reloading alsa" https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1883054/+attachment/5382790/+files/alsa-info-diff.txt -- 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/1883054 Title: Built-in audio device not available until alsa is reloaded Status in alsa-driver package in Ubuntu: New Bug description: I had Ubuntu 18.04 installed, running XFCE (Xubuntu session), and audio worked fine, using either the built-in speakers/mic on the laptop or via a USB headset when that was plugged in. However, after upgrading to 20.04, the built-in audio device is no longer available until I run "sudo alsa force-reload". Wthhout that WAR, all I see is a dummy audio device. Luckily the USB headset works fine, if plugged in. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 Uname: Linux 5.4.0-33-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: swarren7664 F pulseaudio /dev/snd/controlC0: swarren7664 F pulseaudio /dev/snd/pcmC0D0c: swarren7664 F...m pulseaudio /dev/snd/pcmC0D0p: swarren7664 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: XFCE Date: Wed Jun 10 23:57:08 2020 InstallationDate: Installed on 2016-03-03 (1561 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160122.2) PackageArchitecture: all SourcePackage: alsa-driver UpgradeStatus: Upgraded to focal on 2020-06-07 (4 days ago) dmi.bios.date: 08/28/2019 dmi.bios.vendor: LENOVO dmi.bios.version: N1DETA6W (2.32 ) dmi.board.asset.tag: Not Available dmi.board.name: 20ERCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN1DETA6W(2.32):bd08/28/2019:svnLENOVO:pn20ERCTO1WW:pvrThinkPadP70:rvnLENOVO:rn20ERCTO1WW:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad P70 dmi.product.name: 20ERCTO1WW dmi.product.sku: LENOVO_MT_20ER_BU_Think_FM_ThinkPad P70 dmi.product.version: ThinkPad P70 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1883054/+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 1883054] [NEW] Built-in audio device not available until alsa is reloaded
Public bug reported: I had Ubuntu 18.04 installed, running XFCE (Xubuntu session), and audio worked fine, using either the built-in speakers/mic on the laptop or via a USB headset when that was plugged in. However, after upgrading to 20.04, the built-in audio device is no longer available until I run "sudo alsa force-reload". Wthhout that WAR, all I see is a dummy audio device. Luckily the USB headset works fine, if plugged in. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 Uname: Linux 5.4.0-33-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: swarren7664 F pulseaudio /dev/snd/controlC0: swarren7664 F pulseaudio /dev/snd/pcmC0D0c: swarren7664 F...m pulseaudio /dev/snd/pcmC0D0p: swarren7664 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: XFCE Date: Wed Jun 10 23:57:08 2020 InstallationDate: Installed on 2016-03-03 (1561 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160122.2) PackageArchitecture: all SourcePackage: alsa-driver UpgradeStatus: Upgraded to focal on 2020-06-07 (4 days ago) dmi.bios.date: 08/28/2019 dmi.bios.vendor: LENOVO dmi.bios.version: N1DETA6W (2.32 ) dmi.board.asset.tag: Not Available dmi.board.name: 20ERCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN1DETA6W(2.32):bd08/28/2019:svnLENOVO:pn20ERCTO1WW:pvrThinkPadP70:rvnLENOVO:rn20ERCTO1WW:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad P70 dmi.product.name: 20ERCTO1WW dmi.product.sku: LENOVO_MT_20ER_BU_Think_FM_ThinkPad P70 dmi.product.version: ThinkPad P70 dmi.sys.vendor: LENOVO ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- 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/1883054 Title: Built-in audio device not available until alsa is reloaded Status in alsa-driver package in Ubuntu: New Bug description: I had Ubuntu 18.04 installed, running XFCE (Xubuntu session), and audio worked fine, using either the built-in speakers/mic on the laptop or via a USB headset when that was plugged in. However, after upgrading to 20.04, the built-in audio device is no longer available until I run "sudo alsa force-reload". Wthhout that WAR, all I see is a dummy audio device. Luckily the USB headset works fine, if plugged in. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 Uname: Linux 5.4.0-33-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: swarren7664 F pulseaudio /dev/snd/controlC0: swarren7664 F pulseaudio /dev/snd/pcmC0D0c: swarren7664 F...m pulseaudio /dev/snd/pcmC0D0p: swarren7664 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: XFCE Date: Wed Jun 10 23:57:08 2020 InstallationDate: Installed on 2016-03-03 (1561 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160122.2) PackageArchitecture: all SourcePackage: alsa-driver UpgradeStatus: Upgraded to focal on 2020-06-07 (4 days ago) dmi.bios.date: 08/28/2019 dmi.bios.vendor: LENOVO dmi.bios.version: N1DETA6W (2.32 ) dmi.board.asset.tag: Not Available dmi.board.name: 20ERCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN1DETA6W(2.32):bd08/28/2019:svnLENOVO:pn20ERCTO1WW:pvrThinkPadP70:rvnLENOVO:rn20ERCTO1WW:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad P70 dmi.product.name: 20ERCTO1WW dmi.product.sku: LENOVO_MT_20ER_BU_Think_FM_ThinkPad P70 dmi.product.version: ThinkPad P70 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1883054/+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 1876962] [NEW] package libxml2:amd64 2.9.4+dfsg1-6.1ubuntu1.3 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting c
Public bug reported: Fresh install of Ubuntu 18.04 ProblemType: Package DistroRelease: Ubuntu 18.04 Package: libxml2:amd64 2.9.4+dfsg1-6.1ubuntu1.3 ProcVersionSignature: Ubuntu 4.15.0-99.100-generic 4.15.18 Uname: Linux 4.15.0-99-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 AptOrdering: python3-distupgrade:amd64: Install python3-update-manager:amd64: Install update-manager-core:amd64: Install update-manager:amd64: Install NULL: ConfigurePending Architecture: amd64 Date: Tue May 5 17:56:48 2020 ErrorMessage: package is in a very bad inconsistent state; you should reinstall it before attempting configuration InstallationDate: Installed on 2020-05-05 (0 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Python3Details: /usr/bin/python3.6, Python 3.6.9, python3-minimal, 3.6.7-1~18.04 PythonDetails: /root/Error: command ['which', 'python'] failed with exit code 1:, Error: [Errno 2] No such file or directory: "/root/Error: command ['which', 'python'] failed with exit code 1:": "/root/Error: command ['which', 'python'] failed with exit code 1:", unpackaged RelatedPackageVersions: dpkg 1.19.0.5ubuntu2.3 apt 1.6.1 SourcePackage: libxml2 Title: package libxml2:amd64 2.9.4+dfsg1-6.1ubuntu1.3 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: libxml2 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package bionic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libxml2 in Ubuntu. https://bugs.launchpad.net/bugs/1876962 Title: package libxml2:amd64 2.9.4+dfsg1-6.1ubuntu1.3 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration Status in libxml2 package in Ubuntu: New Bug description: Fresh install of Ubuntu 18.04 ProblemType: Package DistroRelease: Ubuntu 18.04 Package: libxml2:amd64 2.9.4+dfsg1-6.1ubuntu1.3 ProcVersionSignature: Ubuntu 4.15.0-99.100-generic 4.15.18 Uname: Linux 4.15.0-99-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 AptOrdering: python3-distupgrade:amd64: Install python3-update-manager:amd64: Install update-manager-core:amd64: Install update-manager:amd64: Install NULL: ConfigurePending Architecture: amd64 Date: Tue May 5 17:56:48 2020 ErrorMessage: package is in a very bad inconsistent state; you should reinstall it before attempting configuration InstallationDate: Installed on 2020-05-05 (0 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Python3Details: /usr/bin/python3.6, Python 3.6.9, python3-minimal, 3.6.7-1~18.04 PythonDetails: /root/Error: command ['which', 'python'] failed with exit code 1:, Error: [Errno 2] No such file or directory: "/root/Error: command ['which', 'python'] failed with exit code 1:": "/root/Error: command ['which', 'python'] failed with exit code 1:", unpackaged RelatedPackageVersions: dpkg 1.19.0.5ubuntu2.3 apt 1.6.1 SourcePackage: libxml2 Title: package libxml2:amd64 2.9.4+dfsg1-6.1ubuntu1.3 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libxml2/+bug/1876962/+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 1870876] Re: docker stopped when containerd updated
Maybe a workaround fix could be to restart ubuntu if dependent services had to be stopped to update something? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unattended-upgrades in Ubuntu. https://bugs.launchpad.net/bugs/1870876 Title: docker stopped when containerd updated Status in unattended-upgrades package in Ubuntu: New Bug description: When containerd was updated in my bionic instance it stopped docker then stopped containerd. When it was done updating containerd it brought it back online. docker stayed stopped. 2020-04-03 06:20:32,973 INFO Packages that will be upgraded: apport containerd python3-apport python3-problem-report An eoan installation that didn't have this problem had this line: 2020-04-03 06:06:01,612 INFO Packages that will be upgraded: apport python3-apport python3-problem-report So the main difference is that containerd was updated. At the end of this systemctl --all reported docker as: docker.service loadedinactive dead and containerd as: containerd.service loadedactive running Description: Ubuntu 18.04.4 LTS Release: 18.04 unattended-upgrades: Installed: 1.1ubuntu1.18.04.14 Candidate: 1.1ubuntu1.18.04.14 Version table: *** 1.1ubuntu1.18.04.14 500 500 http://us-central1.gce.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 100 /var/lib/dpkg/status 1.1ubuntu1 500 500 http://us-central1.gce.archive.ubuntu.com/ubuntu bionic/main amd64 Packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1870876/+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 1870876] Re: docker stopped when containerd updated
Here are people who are hit by this except for mysql: https://askubuntu.com/questions/1037285/starting-daily-apt-upgrade-and-clean-activities-stopping-mysql-service -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unattended-upgrades in Ubuntu. https://bugs.launchpad.net/bugs/1870876 Title: docker stopped when containerd updated Status in unattended-upgrades package in Ubuntu: New Bug description: When containerd was updated in my bionic instance it stopped docker then stopped containerd. When it was done updating containerd it brought it back online. docker stayed stopped. 2020-04-03 06:20:32,973 INFO Packages that will be upgraded: apport containerd python3-apport python3-problem-report An eoan installation that didn't have this problem had this line: 2020-04-03 06:06:01,612 INFO Packages that will be upgraded: apport python3-apport python3-problem-report So the main difference is that containerd was updated. At the end of this systemctl --all reported docker as: docker.service loadedinactive dead and containerd as: containerd.service loadedactive running Description: Ubuntu 18.04.4 LTS Release: 18.04 unattended-upgrades: Installed: 1.1ubuntu1.18.04.14 Candidate: 1.1ubuntu1.18.04.14 Version table: *** 1.1ubuntu1.18.04.14 500 500 http://us-central1.gce.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 100 /var/lib/dpkg/status 1.1ubuntu1 500 500 http://us-central1.gce.archive.ubuntu.com/ubuntu bionic/main amd64 Packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1870876/+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 1870876] Re: docker stopped when containerd updated
attaching unattended-upgrades-dpkg.log ** Attachment added: "/var/log/unattended-upgrades/unattended-upgrades-dpkg.log" https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1870876/+attachment/5346860/+files/unattended-upgrades-dpkg.log -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unattended-upgrades in Ubuntu. https://bugs.launchpad.net/bugs/1870876 Title: docker stopped when containerd updated Status in unattended-upgrades package in Ubuntu: New Bug description: When containerd was updated in my bionic instance it stopped docker then stopped containerd. When it was done updating containerd it brought it back online. docker stayed stopped. 2020-04-03 06:20:32,973 INFO Packages that will be upgraded: apport containerd python3-apport python3-problem-report An eoan installation that didn't have this problem had this line: 2020-04-03 06:06:01,612 INFO Packages that will be upgraded: apport python3-apport python3-problem-report So the main difference is that containerd was updated. At the end of this systemctl --all reported docker as: docker.service loadedinactive dead and containerd as: containerd.service loadedactive running Description: Ubuntu 18.04.4 LTS Release: 18.04 unattended-upgrades: Installed: 1.1ubuntu1.18.04.14 Candidate: 1.1ubuntu1.18.04.14 Version table: *** 1.1ubuntu1.18.04.14 500 500 http://us-central1.gce.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 100 /var/lib/dpkg/status 1.1ubuntu1 500 500 http://us-central1.gce.archive.ubuntu.com/ubuntu bionic/main amd64 Packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1870876/+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 1870876] Re: docker stopped when containerd updated
attaching unattended-upgrades.log ** Attachment added: "/var/log/unattended-upgrades/unattended-upgrades.log" https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1870876/+attachment/5346859/+files/unattended-upgrades.log -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unattended-upgrades in Ubuntu. https://bugs.launchpad.net/bugs/1870876 Title: docker stopped when containerd updated Status in unattended-upgrades package in Ubuntu: New Bug description: When containerd was updated in my bionic instance it stopped docker then stopped containerd. When it was done updating containerd it brought it back online. docker stayed stopped. 2020-04-03 06:20:32,973 INFO Packages that will be upgraded: apport containerd python3-apport python3-problem-report An eoan installation that didn't have this problem had this line: 2020-04-03 06:06:01,612 INFO Packages that will be upgraded: apport python3-apport python3-problem-report So the main difference is that containerd was updated. At the end of this systemctl --all reported docker as: docker.service loadedinactive dead and containerd as: containerd.service loadedactive running Description: Ubuntu 18.04.4 LTS Release: 18.04 unattended-upgrades: Installed: 1.1ubuntu1.18.04.14 Candidate: 1.1ubuntu1.18.04.14 Version table: *** 1.1ubuntu1.18.04.14 500 500 http://us-central1.gce.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 100 /var/lib/dpkg/status 1.1ubuntu1 500 500 http://us-central1.gce.archive.ubuntu.com/ubuntu bionic/main amd64 Packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1870876/+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 1870876] [NEW] docker stopped when containerd updated
Public bug reported: When containerd was updated in my bionic instance it stopped docker then stopped containerd. When it was done updating containerd it brought it back online. docker stayed stopped. 2020-04-03 06:20:32,973 INFO Packages that will be upgraded: apport containerd python3-apport python3-problem-report An eoan installation that didn't have this problem had this line: 2020-04-03 06:06:01,612 INFO Packages that will be upgraded: apport python3-apport python3-problem-report So the main difference is that containerd was updated. At the end of this systemctl --all reported docker as: docker.service loadedinactive dead and containerd as: containerd.service loadedactive running Description:Ubuntu 18.04.4 LTS Release:18.04 unattended-upgrades: Installed: 1.1ubuntu1.18.04.14 Candidate: 1.1ubuntu1.18.04.14 Version table: *** 1.1ubuntu1.18.04.14 500 500 http://us-central1.gce.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 100 /var/lib/dpkg/status 1.1ubuntu1 500 500 http://us-central1.gce.archive.ubuntu.com/ubuntu bionic/main amd64 Packages ** Affects: unattended-upgrades (Ubuntu) Importance: Undecided Status: New ** Attachment added: "journalctl --since "2020-04-03 06:33:52" --until "2020-04-03 06:54:50" >journalctl.log" https://bugs.launchpad.net/bugs/1870876/+attachment/5346855/+files/journalctl.log -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unattended-upgrades in Ubuntu. https://bugs.launchpad.net/bugs/1870876 Title: docker stopped when containerd updated Status in unattended-upgrades package in Ubuntu: New Bug description: When containerd was updated in my bionic instance it stopped docker then stopped containerd. When it was done updating containerd it brought it back online. docker stayed stopped. 2020-04-03 06:20:32,973 INFO Packages that will be upgraded: apport containerd python3-apport python3-problem-report An eoan installation that didn't have this problem had this line: 2020-04-03 06:06:01,612 INFO Packages that will be upgraded: apport python3-apport python3-problem-report So the main difference is that containerd was updated. At the end of this systemctl --all reported docker as: docker.service loadedinactive dead and containerd as: containerd.service loadedactive running Description: Ubuntu 18.04.4 LTS Release: 18.04 unattended-upgrades: Installed: 1.1ubuntu1.18.04.14 Candidate: 1.1ubuntu1.18.04.14 Version table: *** 1.1ubuntu1.18.04.14 500 500 http://us-central1.gce.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 100 /var/lib/dpkg/status 1.1ubuntu1 500 500 http://us-central1.gce.archive.ubuntu.com/ubuntu bionic/main amd64 Packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1870876/+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 1788608] Re: wget doesn't support compression, it needs zlib1g-dev
** Changed in: wget (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to wget in Ubuntu. https://bugs.launchpad.net/bugs/1788608 Title: wget doesn't support compression, it needs zlib1g-dev Status in wget package in Ubuntu: Fix Released Status in wget package in Debian: Fix Released Bug description: wget can use zlib1g for a few features, notably --compression support. The Debian package doesn't explicitly build-depend on zlib1g-dev, it gets it via libgnutls28-dev; since the Ubuntu package drops the latter, compression support is lost too. Please consider adding zlib1g-dev. (I've also asked the Debian maintainer to do so, see the linked bug; however the libgnutls28-dev removal in Ubuntu should take this into account IMO.) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wget/+bug/1788608/+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 1846899] Re: X won't start at boot with either nvidia driver
If it helps interpreting the logs: when the log file snapshot was taken, I was of course running the Nouveau drivers, 'cause that's the only way the system works. But the boot attempt immediately preceeding that was with the NVidia 390 drivers installed. -- 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/1846899 Title: X won't start at boot with either nvidia driver Status in xorg package in Ubuntu: New Bug description: The video card is a GeForce GT 730, which worked well with Ubuntu 16.04. After changing to Xubuntu 18.04, I can only run the Nouveau driver and the lack of acceleration is quite noticeable. When I try to enable the "tested" NVidia driver (390), the system never presents a log-in prompt, I just get a colorful display of large blinking gibberish. I have to go to the boot options, go directly to root prompt, and remove the NVidia driver. This make the system usable again, but I'm back to the Nouveau driver. I get similar symptoms with version 340.107 of the NVidia driver. It's a little hard to collect debug information when I can't get to a prompt to look at log files... Suggestions are welcome. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 5.0.0-29.31~18.04.1-generic 5.0.21 Uname: Linux 5.0.0-29-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 CompositorRunning: None Date: Sat Oct 5 13:56:41 2019 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GF108 [GeForce GT 730] [10de:0f02] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ZOTAC International (MCO) Ltd. GF108 [GeForce GT 730] [19da:8199] InstallationDate: Installed on 2019-04-13 (175 days ago) InstallationMedia: Xubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) MachineType: System manufacturer System Product Name ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-29-generic root=UUID=d19b5e72-689e-4877-93dd-0d4bf5f7cc98 ro drm.debug=0xe plymouth:debug SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/07/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4024 dmi.board.asset.tag: Default string dmi.board.name: PRIME X470-PRO dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4024:bd09/07/2018:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEX470-PRO:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97-1ubuntu1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.8-0ubuntu0~18.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.8-0ubuntu0~18.04.2 version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A xserver.bootTime: Sat Oct 5 13:56:03 2019 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1846899/+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 1846899] [NEW] X won't start at boot with either nvidia driver
Public bug reported: The video card is a GeForce GT 730, which worked well with Ubuntu 16.04. After changing to Xubuntu 18.04, I can only run the Nouveau driver and the lack of acceleration is quite noticeable. When I try to enable the "tested" NVidia driver (390), the system never presents a log-in prompt, I just get a colorful display of large blinking gibberish. I have to go to the boot options, go directly to root prompt, and remove the NVidia driver. This make the system usable again, but I'm back to the Nouveau driver. I get similar symptoms with version 340.107 of the NVidia driver. It's a little hard to collect debug information when I can't get to a prompt to look at log files... Suggestions are welcome. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 5.0.0-29.31~18.04.1-generic 5.0.21 Uname: Linux 5.0.0-29-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 CompositorRunning: None Date: Sat Oct 5 13:56:41 2019 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GF108 [GeForce GT 730] [10de:0f02] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ZOTAC International (MCO) Ltd. GF108 [GeForce GT 730] [19da:8199] InstallationDate: Installed on 2019-04-13 (175 days ago) InstallationMedia: Xubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) MachineType: System manufacturer System Product Name ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-29-generic root=UUID=d19b5e72-689e-4877-93dd-0d4bf5f7cc98 ro drm.debug=0xe plymouth:debug SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/07/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4024 dmi.board.asset.tag: Default string dmi.board.name: PRIME X470-PRO dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4024:bd09/07/2018:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEX470-PRO:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97-1ubuntu1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.8-0ubuntu0~18.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.8-0ubuntu0~18.04.2 version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A xserver.bootTime: Sat Oct 5 13:56:03 2019 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic 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/1846899 Title: X won't start at boot with either nvidia driver Status in xorg package in Ubuntu: New Bug description: The video card is a GeForce GT 730, which worked well with Ubuntu 16.04. After changing to Xubuntu 18.04, I can only run the Nouveau driver and the lack of acceleration is quite noticeable. When I try to enable the "tested" NVidia driver (390), the system never presents a log-in prompt, I just get a colorful display of large blinking gibberish. I have to go to the boot options, go directly to root prompt, and remove the NVidia driver. This make the system usable again, but I'm back to the Nouveau driver. I get similar symptoms with version 340.107 of the NVidia driver. It's a little hard to collect debug information when I can't get to a prompt to look at log files... Suggestions are welcome. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 5.0.0-29.31~18.04.1-generic 5.0.21 Uname: Linux 5.0.0-29-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 CompositorRunning: None Date: Sat Oct 5 13:56:41 2019 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GF108 [GeForce GT 730] [10de:0f02] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ZOTAC International (MCO) Ltd. GF108 [GeForce GT 730] [19da:8199] InstallationDate: Installed on 2019-04-13 (175 days ago) InstallationMedia: Xubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210)
[Touch-packages] [Bug 1843479] Re: gzip in Ubuntu Eoan results in Exec format error on WSL1
I tried comparing the binaries with diffoscope, and one difference which jumped out at me is the .plt.sec section which is present in the Eoan binary. This presumably comes from CET (gcc -fcf-protection). There are other differences, less significant IMO; .plt.sec is a likely candidate for something WSL1 might not support. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gzip in Ubuntu. https://bugs.launchpad.net/bugs/1843479 Title: gzip in Ubuntu Eoan results in Exec format error on WSL1 Status in gzip package in Ubuntu: Confirmed Bug description: Summary: Running gzip on WSL1 results in the following error: $ gzip -bash: /bin/gzip: cannot execute binary file: Exec format error What I expect to happen: gzip executes correctly on WSL1. What happens instead: gzip fails with an Exec format error. Notes: I suspect a change in how gzip is being built for Eoan is causing issues with ELF parsing on the WSL1 translation layer. For example: On Disco with gzip 1.9-3: $ file /bin/gzip /bin/gzip: ELF 64-bit LSB pie executable, x86-64, version 1 (SYSV), dynamically linked, interpreter /lib64/ld-linux-x86-64.so.2, for GNU/Linux 3.2.0, BuildID[sha1]=efa859c26eaf8e035efe9a139361e2a60cd17b3e, stripped On Eoan with gzip 1.10-0ubuntu3: $ file /bin/gzip /bin/gzip: ELF 64-bit LSB pie executable, x86-64, version 1 (SYSV), dynamically linked, interpreter /lib64/ld-linux-x86-64.so.2, BuildID[sha1]=bc0f5994544c2a469d04c914bf4bf44b4ded6040, for GNU/Linux 3.2.0, stripped Eoan ships with gzip 1.10, while Disco ships with gzip 1.9, but I do not believe this is an issue in 1.10 because this error does not occur when building gzip from GNU project source on Ubuntu Eoan. Justifications: WSL1 will need to be patched in future Windows builds for this change in ELF. However that patch will likely not be backported to older builds of Windows, including Windows Enterprise/Server 2019. To ensure Eoan can run on current and older builds of Windows Ubuntu should consider looking at how it's building gzip and see if it can be made to 'play nice' until WSL1 can be updated. This was originally reported here: https://github.com/microsoft/WSL/issues/4461 Details: Description:Ubuntu Eoan Ermine (development branch) Release:19.10 gzip: Installed: 1.10-0ubuntu3 Candidate: 1.10-0ubuntu3 Version table: *** 1.10-0ubuntu3 500 500 http://archive.ubuntu.com/ubuntu eoan/main amd64 Packages 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gzip/+bug/1843479/+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 1822075] Re: tooltips and combo boxes in webbrowsers are all garbage in xserver-xorg-video-radeon 1:19.0.0-1
Hi Dan I did not report this bug Steve On August 28, 2019 3:26:09 AM Daniel van Vugt wrote: > Returned in bug 1841718? > > -- > You received this bug notification because you are subscribed to a > duplicate bug report (1821552). > https://bugs.launchpad.net/bugs/1822075 > > Title: > tooltips and combo boxes in webbrowsers are all garbage in xserver- > xorg-video-radeon 1:19.0.0-1 > > Status in gtk+3.0 package in Ubuntu: > Invalid > Status in mesa package in Ubuntu: > Invalid > Status in mutter package in Ubuntu: > Invalid > Status in xserver-xorg-video-ati package in Ubuntu: > Fix Released > > Bug description: > Disco up to date > > With Chrome and Firefox tooltips and combo boxes are all garbage and > make the browser unusable. Cf screenshots. > > Graphics card: > Advanced Micro Devices, Inc. [AMD/ATI] Juniper XT [Radeon HD 5770] > > I tried gtk2 and gtk3 demos and the combo boxes are broken in the same > way. > > I also tried FF as a snap and as a deb and the problem is the same. > > ProblemType: Bug > DistroRelease: Ubuntu 19.04 > Package: gnome-shell 3.32.0-1ubuntu1 > ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0 > Uname: Linux 5.0.0-7-generic x86_64 > NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair > ApportVersion: 2.20.10-0ubuntu23 > Architecture: amd64 > CurrentDesktop: ubuntu:GNOME > Date: Thu Mar 28 11:51:41 2019 > DisplayManager: gdm3 > InstallationDate: Installed on 2014-07-15 (1717 days ago) > InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20140520) > SourcePackage: gnome-shell > UpgradeStatus: Upgraded to disco on 2018-03-24 (368 days ago) > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1822075/+subscriptions -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1822075 Title: tooltips and combo boxes in webbrowsers are all garbage in xserver- xorg-video-radeon 1:19.0.0-1 Status in gtk+3.0 package in Ubuntu: Invalid Status in mesa package in Ubuntu: Invalid Status in mutter package in Ubuntu: Invalid Status in xserver-xorg-video-ati package in Ubuntu: Fix Released Bug description: Disco up to date With Chrome and Firefox tooltips and combo boxes are all garbage and make the browser unusable. Cf screenshots. Graphics card: Advanced Micro Devices, Inc. [AMD/ATI] Juniper XT [Radeon HD 5770] I tried gtk2 and gtk3 demos and the combo boxes are broken in the same way. I also tried FF as a snap and as a deb and the problem is the same. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: gnome-shell 3.32.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0 Uname: Linux 5.0.0-7-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.10-0ubuntu23 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Mar 28 11:51:41 2019 DisplayManager: gdm3 InstallationDate: Installed on 2014-07-15 (1717 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20140520) SourcePackage: gnome-shell UpgradeStatus: Upgraded to disco on 2018-03-24 (368 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1822075/+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 1832919] Re: installed libssl1.1:amd64 package post-installation script subprocess returned error exit status 10
Workaround recovered me as well, thanks! -- 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/1832919 Title: installed libssl1.1:amd64 package post-installation script subprocess returned error exit status 10 Status in openssl package in Ubuntu: Incomplete Bug description: The error happens when trying to configure libssl1.1:amd64 (dpkg --configure -D 2 libssl1.1) dpkg: error processing package libssl1.1:amd64 (--configure): installed libssl1.1:amd64 package post-installation script subprocess returned error exit status 10 D02: post_script_tasks - ensure_diversions D02: post_script_tasks - trig_incorporate D02: check_triggers_cycle pnow=libc-bin:amd64 first Processing triggers for libc-bin (2.27-3ubuntu1) ... D02: post_postinst_tasks - trig_incorporate Errors were encountered while processing: libssl1.1:amd64 [ WORKAROUND TO RECOVER YOUR SYSTEM ] $ sudo dpkg-reconfigure libc6 $ sudo dpkg --configure libssl1.1 [ Reproducer steps ] # DO NOT DO THIS ON PRODUCTION MACHINES # # echo PURGE | debconf-communicate libpam0g:amd64 0 # echo PURGE | debconf-communicate libpam0g 0 # echo PURGE | debconf-communicate libc6:amd64 0 # echo PURGE | debconf-communicate libc6 0 # sh -x /var/lib/dpkg/info/libssl1.1\:amd64.postinst configure 1.1.1 + . /usr/share/debconf/confmodule + [ ! ] + PERL_DL_NONLAZY=1 + export PERL_DL_NONLAZY + [ ] + exec /usr/share/debconf/frontend /var/lib/dpkg/info/libssl1.1:amd64.postinst configure 1.1.1 Checking for services that may need to be restarted...done. Checking for services that may need to be restarted...done. Checking init scripts... # echo $? 10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1832919/+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 1832919] Re: installed libssl1.1:amd64 package post-installation script subprocess returned error exit status 10
Note: My system in question is an x86_64 (Intel CPU) so not sure why AMD packages are showing up here. -- 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/1832919 Title: installed libssl1.1:amd64 package post-installation script subprocess returned error exit status 10 Status in openssl package in Ubuntu: Confirmed Bug description: The error happens when trying to configure libssl1.1:amd64 (dpkg --configure -D 2 libssl1.1) dpkg: error processing package libssl1.1:amd64 (--configure): installed libssl1.1:amd64 package post-installation script subprocess returned error exit status 10 D02: post_script_tasks - ensure_diversions D02: post_script_tasks - trig_incorporate D02: check_triggers_cycle pnow=libc-bin:amd64 first Processing triggers for libc-bin (2.27-3ubuntu1) ... D02: post_postinst_tasks - trig_incorporate Errors were encountered while processing: libssl1.1:amd64 The attempted fix Line #153 of file /var/lib/dpkg/info/libssl1.1\:amd64.postinst - db_get libraries/restart-without-asking + db_get libraries/restart-without-asking || true To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1832919/+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 1832919] Re: installed libssl1.1:amd64 package post-installation script subprocess returned error exit status
During system upgrade: sudo apt-get upgrade Reading package lists... Done Building dependency tree Reading state information... Done Calculating upgrade... Done The following packages will be upgraded: firefox firefox-locale-en gir1.2-xapp-1.0 libxapp1 openssl xapps-common 6 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 1 not fully installed or removed. Need to get 0 B/50.6 MB of archives. After this operation, 106 kB of additional disk space will be used. Do you want to continue? [Y/n] Y Setting up libssl1.1:amd64 (1.1.1-1ubuntu2.1~18.04.2) ... Checking for services that may need to be restarted...done. Checking for services that may need to be restarted...done. Checking init scripts... dpkg: error processing package libssl1.1:amd64 (--configure): installed libssl1.1:amd64 package post-installation script subprocess returned error exit status 10 Errors were encountered while processing: libssl1.1:amd64 E: Sub-process /usr/bin/dpkg returned an error code (1) -- 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/1832919 Title: installed libssl1.1:amd64 package post-installation script subprocess returned error exit status 10 Status in openssl package in Ubuntu: Confirmed Bug description: The error happens when trying to configure libssl1.1:amd64 (dpkg --configure -D 2 libssl1.1) dpkg: error processing package libssl1.1:amd64 (--configure): installed libssl1.1:amd64 package post-installation script subprocess returned error exit status 10 D02: post_script_tasks - ensure_diversions D02: post_script_tasks - trig_incorporate D02: check_triggers_cycle pnow=libc-bin:amd64 first Processing triggers for libc-bin (2.27-3ubuntu1) ... D02: post_postinst_tasks - trig_incorporate Errors were encountered while processing: libssl1.1:amd64 The attempted fix Line #153 of file /var/lib/dpkg/info/libssl1.1\:amd64.postinst - db_get libraries/restart-without-asking + db_get libraries/restart-without-asking || true To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1832919/+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 1829458] Re: [ubuntu 19.04]All .desktop configuration files are not opening in nautilus
Now I've modified this bug report and hopefully waiting for an answer. ** Description changed: - All .desktop configuration files are opening in text editor. Because of - that we can't creat custom shortcuts and having troubles while - application making. Please fix this bug on next update. I have an Ubuntu - 19.04. + Error : Desktop configuration files are not launching from nautilus but its working from desktop. + Occured Error while : made a shortcut and tried to open from nautilus + { + [Desktop Entry] + Name=Install Niram + Exec=/usr/share/niram/NiramStock/install.sh + Type=Application + StartupNotify=true + Comment=Install Stock Niram Theme + Path=/usr/share + Icon=/home/newtron/Documents/NiramStock/20190107_201717.png + } + but it's opening in text editor. Also ubuntu's default examples have this error and showing it as a normal text file. + + What I've expected : On older versions of nautilus and all versions of + nemo it directly opens .desktop files from file manager. + + Now I've modified this bug report and hopefully waiting for an answer. Tanks -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1829458 Title: [ubuntu 19.04]All .desktop configuration files are not opening in nautilus Status in glib2.0 package in Ubuntu: Incomplete Bug description: Error : Desktop configuration files are not launching from nautilus but its working from desktop. Occured Error while : made a shortcut and tried to open from nautilus { [Desktop Entry] Name=Install Niram Exec=/usr/share/niram/NiramStock/install.sh Type=Application StartupNotify=true Comment=Install Stock Niram Theme Path=/usr/share Icon=/home/newtron/Documents/NiramStock/20190107_201717.png } but it's opening in text editor. Also ubuntu's default examples have this error and showing it as a normal text file. What I've expected : On older versions of nautilus and all versions of nemo it directly opens .desktop files from file manager. Now I've modified this bug report and hopefully waiting for an answer. Tanks To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1829458/+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 1829458] Re: [ubuntu 19.04]All .desktop configuration files are not opening in nautilus
** Summary changed: - [ubuntu 19.04]All .desktop configuration files are opening in text editor + [ubuntu 19.04]All .desktop configuration files are not opening in nautilus -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1829458 Title: [ubuntu 19.04]All .desktop configuration files are not opening in nautilus Status in glib2.0 package in Ubuntu: Incomplete Bug description: All .desktop configuration files are opening in text editor. Because of that we can't creat custom shortcuts and having troubles while application making. Please fix this bug on next update. I have an Ubuntu 19.04. Tanks To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1829458/+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 1829458] [NEW] [ubuntu 19.04]All .desktop configuration files are opening in text editor
Public bug reported: All .desktop configuration files are opening in text editor. Because of that we can't creat custom shortcuts and having troubles while application making. Please fix this bug on next update. I have an Ubuntu 19.04. Tanks ** Affects: glib2.0 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1829458 Title: [ubuntu 19.04]All .desktop configuration files are opening in text editor Status in glib2.0 package in Ubuntu: New Bug description: All .desktop configuration files are opening in text editor. Because of that we can't creat custom shortcuts and having troubles while application making. Please fix this bug on next update. I have an Ubuntu 19.04. Tanks To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1829458/+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 1679307] Re: [XPS 15 9560, Realtek ALC3266, Black Headphone Out, Left] No sound at all
I use Ubuntu 18.04 (Linux version 4.15.0-46-generic (buildd@lgw01-amd64-038) (gcc version 7.3.0 (Ubuntu 7.3.0-16ubuntu3)) #49-Ubuntu SMP Wed Feb 6 09:33:07 UTC 2019) and I also have this issue. This command (as given above): alsactl restore does work for me ... until it happens again. And then I just use the command again. It would be nice for this to be resolved. -- 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/1679307 Title: [XPS 15 9560, Realtek ALC3266, Black Headphone Out, Left] No sound at all Status in alsa-driver package in Ubuntu: Invalid Bug description: My speakers are working on my Dell XPS 15 9560. But when I connect headphones to the computer there is no sound at all. Tried different headphones that should work. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.8.0-45.48-generic 4.8.17 Uname: Linux 4.8.0-45-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.3-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: klas 2471 F pulseaudio CurrentDesktop: Unity Date: Mon Apr 3 22:44:05 2017 InstallationDate: Installed on 2017-03-22 (12 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: klas 2471 F pulseaudio Symptom_Jack: Black Headphone Out, Left Symptom_Type: No sound at all Title: [XPS 15 9560, Realtek ALC3266, Black Headphone Out, Left] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/18/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.1.3 dmi.board.name: 05FFDN dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.1.3:bd01/18/2017:svnDellInc.:pnXPS159560:pvr:rvnDellInc.:rn05FFDN:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.name: XPS 15 9560 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1679307/+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 1409872] Re: avahi-0.6.31 doesn't pass Apple conformance test
I posted this on the Avahi Github issue, but I felt it was appropriate here as well: --- I've been researching this issue for my company. We specifically need to pass the mDNS portion of the BCT, so our scope is limited, but I do have some insights. There is a definitely an issue if you are broadcasting a service with the "%h" wildcard as the service name. During the service collision portion, this falls down, but, if you are broadcasting under any other static name, you can get much further. Newer versions of the test seem to require that specific services need to be broadcasted. This is not mentioned in the documentation anywhere, but, if I simple broadcast the _smb._tcp. service with any static name (e.g. "Living Room" or "SMB"), then the mDNS test does pass for BCT 1.5.0. Technically we have to pass the mDNS portion of the test on BCT 1.3.1. With the set up above, we fail one test, and that's because one reply comes back from Avahi too quickly. Interestingly enough, BCT 1.3.3 seems to have addressed the timing issue, allowing slightly better tolerances. I believe the response in question needs to come in between the 250ms and 750ms window, and Avahi appears to come in slightly before that window. In the newer versions of BCT, this isn't an issue. I imagine either BCT 1.3.1 has too tight of tolerances, or isn't sampling improperly. There are actually very strict instructions on setting up the test environment, and I even found that with the strict network set up, it could still potentially fail. You need an AirPort Extreme set up to act as an access point and that is it. No DHCP, no network connection, and crucially, no SMB broadcast if you're using a Time Capsule (this can break the test). The test machine was a MacBook Air running macOS 10.12 and connected via ethernet. The Avahi machine was an Asus laptop running Ubuntu 18.10 (Avahi 0.7) connected via wifi. Everything is link local. This all comes from the "Bonjour Conformance Test for Wi-Fi Alliance Version 0.1" document. We're exploring whether we can actually use the 1.5.0 test, as this would make Avahi simply work in the mDNS portion of the test. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to avahi in Ubuntu. https://bugs.launchpad.net/bugs/1409872 Title: avahi-0.6.31 doesn't pass Apple conformance test Status in Avahi: Unknown Status in avahi package in Ubuntu: Confirmed Bug description: We are working on to support Apple bonjour conformance test-1.3.0 and test fails with avahi version 0.6.31 for test case - SRV PROBING/ANNOUNCEMENTS. This test fails both on IPV4 and IPV6. And the configured network package - dhcpcd-6.6.4. After parsing all logs(wireshark, apple PC and linux PC syslogs), and looks like avahi does not support a particular scenario in which Apple bonjour conformance test looks for. And also confirmed Apple test is inline with the RFC 6762 document for a special use-case(resolving SRV names on power up). Below is the bug description, setup: Apple MAC with Bonjour conformance test - 1.3.0 (latest OS x) Apple airport (latest version) Linux device(PC) (ubuntu 14.04) Configure all above devices to communicate on link local mode. 1) Start avahi bonjour conformance test on APPLE PC and Power ON linux device with avahi-0.6.31 and with _ssh._tcp.local service file 2) First Linux device sends SRV initial probe message on link and followed by apple test sends same SRV (Linux device) question on link, example:(commands on wire shark) Linux Device sends -> Who has "SSH" SRV QM question? Apple Bonjour Conformance Test -> Who has "SSH" SRV QM question? 3) Then after this there is no message from Linux device on network and Apple test expecting new SRV probe message from device. And so conformance test failed, since device couldn't able to send new SRV probe message with new name for service "SSH" 4) After parsing log files found that, avahi-daemon logged service with new name ("SSH #2") in log file and could not publish/probe SRV message on network. Linux device syslog messages, Loading service file /etc/avahi/services/ssh.service Service name conflict for "SSH" (/etc/avahi/services/ssh.service), retrying with "SSH #2). To manage notifications about this bug go to: https://bugs.launchpad.net/avahi/+bug/1409872/+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 1813434] [NEW] package libpolkit-agent-1-0 0.105-20ubuntu0.18.04.4 failed to install/upgrade: unable to sync directory '/var/lib/dpkg/tmp.ci/': Input/output error
Public bug reported: this shows up on startup ProblemType: Package DistroRelease: Ubuntu 18.04 Package: libpolkit-agent-1-0 0.105-20ubuntu0.18.04.4 ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18 Uname: Linux 4.15.0-43-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 Date: Sat Jan 26 18:30:41 2019 DuplicateSignature: package:libpolkit-agent-1-0:0.105-20ubuntu0.18.04.4 Unpacking gir1.2-polkit-1.0 (0.105-20ubuntu0.18.04.4) over (0.105-20ubuntu0.18.04.1) ... dpkg: error processing archive /tmp/apt-dpkg-install-STjm8e/008-libpolkit-agent-1-0_0.105-20ubuntu0.18.04.4_amd64.deb (--unpack): unable to sync directory '/var/lib/dpkg/tmp.ci/': Input/output error ErrorMessage: unable to sync directory '/var/lib/dpkg/tmp.ci/': Input/output error InstallationDate: Installed on 2013-11-13 (1900 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) Python3Details: /usr/bin/python3.6, Python 3.6.7, python3-minimal, 3.6.7-1~18.04 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2.1 apt 1.6.6ubuntu0.1 SourcePackage: policykit-1 Title: package libpolkit-agent-1-0 0.105-20ubuntu0.18.04.4 failed to install/upgrade: unable to sync directory '/var/lib/dpkg/tmp.ci/': Input/output error UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: policykit-1 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package bionic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to policykit-1 in Ubuntu. https://bugs.launchpad.net/bugs/1813434 Title: package libpolkit-agent-1-0 0.105-20ubuntu0.18.04.4 failed to install/upgrade: unable to sync directory '/var/lib/dpkg/tmp.ci/': Input/output error Status in policykit-1 package in Ubuntu: New Bug description: this shows up on startup ProblemType: Package DistroRelease: Ubuntu 18.04 Package: libpolkit-agent-1-0 0.105-20ubuntu0.18.04.4 ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18 Uname: Linux 4.15.0-43-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 Date: Sat Jan 26 18:30:41 2019 DuplicateSignature: package:libpolkit-agent-1-0:0.105-20ubuntu0.18.04.4 Unpacking gir1.2-polkit-1.0 (0.105-20ubuntu0.18.04.4) over (0.105-20ubuntu0.18.04.1) ... dpkg: error processing archive /tmp/apt-dpkg-install-STjm8e/008-libpolkit-agent-1-0_0.105-20ubuntu0.18.04.4_amd64.deb (--unpack): unable to sync directory '/var/lib/dpkg/tmp.ci/': Input/output error ErrorMessage: unable to sync directory '/var/lib/dpkg/tmp.ci/': Input/output error InstallationDate: Installed on 2013-11-13 (1900 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) Python3Details: /usr/bin/python3.6, Python 3.6.7, python3-minimal, 3.6.7-1~18.04 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2.1 apt 1.6.6ubuntu0.1 SourcePackage: policykit-1 Title: package libpolkit-agent-1-0 0.105-20ubuntu0.18.04.4 failed to install/upgrade: unable to sync directory '/var/lib/dpkg/tmp.ci/': Input/output error UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/policykit-1/+bug/1813434/+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 1807262] Re: stein unit tests fail with sqlalchemy.exc.NoSuchTableError: migration_tmp
Steps to reproduce using a Fedora container, courtesy of sean-k-mooney. #create fedora29 docker container or use a fedora 29 host sudo docker run --rm -it fedora bash # recreate bug yum install -y tox git python2-devel libffi-devel make gcc cd ~ git clone http://github.com/openstack/nova cd nova/ tox -e py27 -- test_create_fails_instance #passes dnf list --installed | grep sqlite # shoudl be using 3.24 dnf install -y sqlite tox -e py27 -- test_create_fails_instance # fails -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to sqlite3 in Ubuntu. https://bugs.launchpad.net/bugs/1807262 Title: stein unit tests fail with sqlalchemy.exc.NoSuchTableError: migration_tmp Status in sqlalchemy-migrate: New Status in cinder package in Ubuntu: Fix Released Status in migrate package in Ubuntu: Fix Released Status in nova package in Ubuntu: Fix Released Status in sqlite3 package in Ubuntu: Invalid Bug description: Several tests that use sqlite fail with: "sqlalchemy.exc.NoSuchTableError: migration_tmp". I'm currently hitting this with nova and cinder packages in disco. Note this started sometime after 11/19 when nova 2:19.0.0~b1~git2018111953.3e756ff674-0ubuntu1 was uploaded (and built successfully at the time). After doing some digging this appears to occur with libsqlite3-0 3.26.0-1 but does not occur with libsqlite3-0 3.25.3-1. Here are some more details on that, shown by running a failing unit test from the cinder package: https://paste.ubuntu.com/p/hsnQFQD572/ Update: The test in the paste above also works successfully with libsqlite3-0 3.25.3-2. To manage notifications about this bug go to: https://bugs.launchpad.net/sqlalchemy-migrate/+bug/1807262/+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 1807262] Re: stein unit tests fail with sqlalchemy.exc.NoSuchTableError: migration_tmp
For what it's worth, I'm seeing this issue on Fedora 29 too with SQLite 3.26.0. Downgrading to 3.24.0 resolves things. Time to get some movement on that patch. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to sqlite3 in Ubuntu. https://bugs.launchpad.net/bugs/1807262 Title: stein unit tests fail with sqlalchemy.exc.NoSuchTableError: migration_tmp Status in sqlalchemy-migrate: New Status in cinder package in Ubuntu: Fix Released Status in migrate package in Ubuntu: Fix Released Status in nova package in Ubuntu: Fix Released Status in sqlite3 package in Ubuntu: Invalid Bug description: Several tests that use sqlite fail with: "sqlalchemy.exc.NoSuchTableError: migration_tmp". I'm currently hitting this with nova and cinder packages in disco. Note this started sometime after 11/19 when nova 2:19.0.0~b1~git2018111953.3e756ff674-0ubuntu1 was uploaded (and built successfully at the time). After doing some digging this appears to occur with libsqlite3-0 3.26.0-1 but does not occur with libsqlite3-0 3.25.3-1. Here are some more details on that, shown by running a failing unit test from the cinder package: https://paste.ubuntu.com/p/hsnQFQD572/ Update: The test in the paste above also works successfully with libsqlite3-0 3.25.3-2. To manage notifications about this bug go to: https://bugs.launchpad.net/sqlalchemy-migrate/+bug/1807262/+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 1810444] [NEW] possible gpsim fault
Public bug reported: I was trying unsuccessfully to load gpsim at the time the bug came to my attention ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3.1 ProcVersionSignature: Ubuntu 4.15.0-43.46~16.04.1-generic 4.15.18 Uname: Linux 4.15.0-43-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Thu Jan 3 23:19:47 2019 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Device [8086:22b0] (rev 36) (prog-if 00 [VGA controller]) Subsystem: Intel Corporation Device [8086:7270] InstallationDate: Installed on 2018-12-20 (14 days ago) InstallationMedia: Ubuntu 16.04.5 LTS "Xenial Xerus" - Release amd64 (20180731) MachineType: ADSC Z140C ProcEnviron: LANGUAGE=en_ZA:en PATH=(custom, no user) LANG=en_ZA.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-43-generic root=UUID=2100f5b6-e85f-4f6c-8fd0-da01ce01659d ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/05/2017 dmi.bios.version: WH-BI-14-Y116CR210-CC341-037-C dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Cherry Trail CR dmi.board.vendor: AMI Corporation dmi.board.version: To be filled by O.E.M. dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 10 dmi.chassis.version: To be filled by O.E.M. dmi.modalias: dmi:bvn:bvrWH-BI-14-Y116CR210-CC341-037-C:bd06/05/2017:svnADSC:pnZ140C:pvrTobefilledbyO.E.M.:rvnAMICorporation:rnCherryTrailCR:rvrTobefilledbyO.E.M.:cvn:ct10:cvrTobefilledbyO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: Z140C dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: ADSC version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.91-2~16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~16.04.1 version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A xserver.bootTime: Thu Jan 3 23:17:35 2019 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.19.6-1ubuntu4.1~16.04.2 xserver.video_driver: modeset ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug compiz-0.9 ubuntu xenial -- 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/1810444 Title: possible gpsim fault Status in xorg package in Ubuntu: New Bug description: I was trying unsuccessfully to load gpsim at the time the bug came to my attention ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3.1 ProcVersionSignature: Ubuntu 4.15.0-43.46~16.04.1-generic 4.15.18 Uname: Linux 4.15.0-43-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Thu Jan 3 23:19:47 2019 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Device [8086:22b0] (rev 36) (prog-if 00 [VGA controller]) Subsystem: Intel Corporation Device [8086:7270] InstallationDate: Installed on 2018-12-20 (14 days ago) InstallationMedia: Ubuntu 16.04.5 LTS "Xenial Xerus" - Release amd64 (20180731) MachineType: ADSC Z140C ProcEnviron: LANGUAGE=en_ZA:en PATH=(custom, no user) LANG=en_ZA.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-43-generic root=UUID=2100f5b6-e85f-4f6c-8fd0-da01ce01659d ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/05/2017 dmi.bios.version: WH-BI-14-Y116CR210-CC341-037-C dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Cherry Trail CR dmi.board.vendor: AMI Corporation dmi.board.version: To be filled by O.E.M. dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 10 dmi.chassis.version: To be filled by O.E.M.
[Touch-packages] [Bug 1805820] Re: Dependency error installing fontconfig-dbgsym
It’s a bug in your Dockerfile. You should drop the proposed line. See https://unix.stackexchange.com/q/484875/86440 for details. ** Changed in: fontconfig (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to fontconfig in Ubuntu. https://bugs.launchpad.net/bugs/1805820 Title: Dependency error installing fontconfig-dbgsym Status in fontconfig package in Ubuntu: Invalid Bug description: I am trying to install fontconfig-dbgsym under Ubuntu 18.04 inside Docker, running on Docker for Mac. I use the following Dockerfile: FROM ubuntu:18.04 ENV DEBIAN_FRONTEND=noninteractive RUN apt-get update RUN apt-get install -y ubuntu-dbgsym-keyring lsb-release RUN \ ( \ echo "deb http://ddebs.ubuntu.com $(lsb_release -cs) main restricted universe multiverse"; \ echo "deb http://ddebs.ubuntu.com $(lsb_release -cs)-updates main restricted universe multiverse"; \ echo "deb http://ddebs.ubuntu.com $(lsb_release -cs)-proposed main restricted universe multiverse"; \ ) > /etc/apt/sources.list.d/ddebs.list RUN apt-get update RUN apt-get install -y fontconfig RUN apt-get install -y fontconfig-dbgsym Everything works except the last step, which fails with: Reading package lists... Building dependency tree... Reading state information... Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: fontconfig-dbgsym : Depends: fontconfig (= 2.12.6-0ubuntu2.2) but 2.12.6-0ubuntu2 is to be installed E: Unable to correct problems, you have held broken packages. The command '/bin/sh -c apt-get install -y fontconfig-dbgsym' returned a non-zero code: 100 It complains the dependency `fontconfig=2.12.6-0ubuntu2.2` isn't installed, but it was successfully installed by the previous step. This looks like a bug. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fontconfig/+bug/1805820/+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 1801551] Re: ubuntu does not load the image from swap after hibernation
if anybody can help with making hibernation work on ubuntu 18.04 pls let me know. the bug report is incomplete and I have no idea how to complete it. ** Changed in: initramfs-tools (Ubuntu) Status: Incomplete => Invalid ** Converted to question: https://answers.launchpad.net/ubuntu/+source/initramfs-tools/+question/676281 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1801551 Title: ubuntu does not load the image from swap after hibernation Status in initramfs-tools package in Ubuntu: Invalid Bug description: after upgrading from 16.04 to 18.04 the upgrade messes up the boot process and hibernatation does not work. I hibernate by systemctl hibernate it asks for a password and it seemingly saves the image and shuts down. when I start the computer it does not load the saved image but opens a blank session losing the saved workspace. very inconvenient to start from scratch every time. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1801551/+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 1801551] Re: ubuntu does not load the image from swap after hibernation
cat /etc/fstab # /etc/fstab: static file system information. # # Use 'blkid' to print the universally unique identifier for a # device; this may be used with UUID= as a more robust way to name devices # that works even if disks are added and removed. See fstab(5). # # # / was on /dev/sdb7 during installation UUID=72511ae3-b3b2-40b5-833e-ba6722bec17f / ext4 errors=remount-ro 0 1 # swap was on /dev/sdb6 during installation UUID=5dbf169d-1f88-46c2-a99b-17540bf6801c noneswapsw 0 0 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1801551 Title: ubuntu does not load the image from swap after hibernation Status in initramfs-tools package in Ubuntu: Incomplete Bug description: after upgrading from 16.04 to 18.04 the upgrade messes up the boot process and hibernatation does not work. I hibernate by systemctl hibernate it asks for a password and it seemingly saves the image and shuts down. when I start the computer it does not load the saved image but opens a blank session losing the saved workspace. very inconvenient to start from scratch every time. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1801551/+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 1801551] Re: ubuntu does not load the image from swap after hibernation
Steve, I will be happy to test any specific commands cat: /tmp/initrd/main/conf/conf.d/zz-auto-resume: No such file or directory also I saw other bug reports reporting the same problem see In Progress #332365 I thought that hibernate will dump the workspace onto swap. I think it does that. however the wake up does not load from swap. can you suggest some diagnostic commands? thanks -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1801551 Title: ubuntu does not load the image from swap after hibernation Status in initramfs-tools package in Ubuntu: Incomplete Bug description: after upgrading from 16.04 to 18.04 the upgrade messes up the boot process and hibernatation does not work. I hibernate by systemctl hibernate it asks for a password and it seemingly saves the image and shuts down. when I start the computer it does not load the saved image but opens a blank session losing the saved workspace. very inconvenient to start from scratch every time. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1801551/+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 1774843] Re: apport python exception handler messes up python3.7
As a workaround, I removed the 3.7 sitecustomize.py files: squirrel:~ 0:7> sudo rm /etc/python3.7/sitecustomize.py /usr/lib/python3.7/sitecustomize.py The above files were apparently installed by libpython3.7-minimal: squirrel:~ 0:8> dpkg -S /etc/python3.7/sitecustomize.py /usr/lib/python3.7/sitecustomize.py libpython3.7-minimal:amd64: /etc/python3.7/sitecustomize.py libpython3.7-minimal:amd64: /usr/lib/python3.7/sitecustomize.py -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python-apt in Ubuntu. https://bugs.launchpad.net/bugs/1774843 Title: apport python exception handler messes up python3.7 Status in apport package in Ubuntu: Triaged Status in python-apt package in Ubuntu: Invalid Bug description: it seems apport installs an exception hook whenever running python3. This hook is apparently installed for python3.7 too. This exception handler has a dependency on apt_pkg, which is a binary that is not compatible with python3.7 it seems (you can't import it, see below) As a result, whenever I run a python3.7 script and run into an exception (which happens often when writing code), I get an additional exception in the exception handler + a copy of the original exception, so three stacktraces in total. A solution would be to only install the exception hook for the system python i.e. python3.6 $ lsb_release -rd Description: Ubuntu 18.04 LTS Release: 18.04 apport: 2.20.9-0ubuntu7 python-apt: 1.6.0 python3.7: 3.7.0~b3-1 Demo with a trivial error: $ python3 -c 'print hello' File "", line 1 print hello ^ SyntaxError: Missing parentheses in call to 'print'. Did you mean print(hello)? $ python3.7 -c 'print hello' File "", line 1 print hello ^ SyntaxError: Missing parentheses in call to 'print'. Did you mean print(hello)? Error in sys.excepthook: Traceback (most recent call last): File "/usr/lib/python3/dist-packages/apport_python_hook.py", line 63, in apport_excepthook from apport.fileutils import likely_packaged, get_recent_crashes File "/usr/lib/python3/dist-packages/apport/__init__.py", line 5, in from apport.report import Report File "/usr/lib/python3/dist-packages/apport/report.py", line 30, in import apport.fileutils File "/usr/lib/python3/dist-packages/apport/fileutils.py", line 23, in from apport.packaging_impl import impl as packaging File "/usr/lib/python3/dist-packages/apport/packaging_impl.py", line 24, in import apt File "/usr/lib/python3/dist-packages/apt/__init__.py", line 23, in import apt_pkg ModuleNotFoundError: No module named 'apt_pkg' Original exception was: File "", line 1 print hello ^ SyntaxError: Missing parentheses in call to 'print'. Did you mean print(hello)? Python 3.6.5 (default, Apr 1 2018, 05:46:30) [GCC 7.3.0] on linux Type "help", "copyright", "credits" or "license" for more information. >>> import sys >>> sys.excepthook >>> import apt_pkg >>> apt_pkg.__file__ '/usr/lib/python3/dist-packages/apt_pkg.cpython-36m-x86_64-linux-gnu.so' >>> Python 3.7.0b3 (default, Mar 30 2018, 04:35:22) [GCC 7.3.0] on linux Type "help", "copyright", "credits" or "license" for more information. >>> import sys >>> sys.excepthook >> import apt_pkg Traceback (most recent call last): File "", line 1, in ModuleNotFoundError: No module named 'apt_pkg' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1774843/+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 1788608] [NEW] wget doesn't support compression, it needs zlib1g-dev
Public bug reported: wget can use zlib1g for a few features, notably --compression support. The Debian package doesn't explicitly build-depend on zlib1g-dev, it gets it via libgnutls28-dev; since the Ubuntu package drops the latter, compression support is lost too. Please consider adding zlib1g-dev. (I've also asked the Debian maintainer to do so, see the linked bug; however the libgnutls28-dev removal in Ubuntu should take this into account IMO.) ** Affects: wget (Ubuntu) Importance: Undecided Status: New ** Affects: wget (Debian) Importance: Unknown Status: Unknown ** Bug watch added: Debian Bug tracker #907047 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=907047 ** Also affects: wget (Debian) via https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=907047 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to wget in Ubuntu. https://bugs.launchpad.net/bugs/1788608 Title: wget doesn't support compression, it needs zlib1g-dev Status in wget package in Ubuntu: New Status in wget package in Debian: Unknown Bug description: wget can use zlib1g for a few features, notably --compression support. The Debian package doesn't explicitly build-depend on zlib1g-dev, it gets it via libgnutls28-dev; since the Ubuntu package drops the latter, compression support is lost too. Please consider adding zlib1g-dev. (I've also asked the Debian maintainer to do so, see the linked bug; however the libgnutls28-dev removal in Ubuntu should take this into account IMO.) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wget/+bug/1788608/+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 1787873] [NEW] package hicolor-icon-theme 0.17-2 failed to install/upgrade: triggers looping, abandoned
Public bug reported: Ubuntu 16.04 -> 18.04 ProblemType: Package DistroRelease: Ubuntu 18.04 Package: hicolor-icon-theme 0.17-2 Uname: Linux 4.15.16-041516-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 Date: Fri Aug 17 09:17:18 2018 Dependencies: ErrorMessage: triggers looping, abandoned InstallationDate: Installed on 2016-10-07 (681 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) PackageArchitecture: all Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3ubuntu1 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2 apt 1.6.3 SourcePackage: hicolor-icon-theme Title: package hicolor-icon-theme 0.17-2 failed to install/upgrade: triggers looping, abandoned UpgradeStatus: Upgraded to bionic on 2018-08-20 (0 days ago) ** Affects: hicolor-icon-theme (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package bionic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to hicolor-icon-theme in Ubuntu. https://bugs.launchpad.net/bugs/1787873 Title: package hicolor-icon-theme 0.17-2 failed to install/upgrade: triggers looping, abandoned Status in hicolor-icon-theme package in Ubuntu: New Bug description: Ubuntu 16.04 -> 18.04 ProblemType: Package DistroRelease: Ubuntu 18.04 Package: hicolor-icon-theme 0.17-2 Uname: Linux 4.15.16-041516-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 Date: Fri Aug 17 09:17:18 2018 Dependencies: ErrorMessage: triggers looping, abandoned InstallationDate: Installed on 2016-10-07 (681 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) PackageArchitecture: all Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3ubuntu1 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2 apt 1.6.3 SourcePackage: hicolor-icon-theme Title: package hicolor-icon-theme 0.17-2 failed to install/upgrade: triggers looping, abandoned UpgradeStatus: Upgraded to bionic on 2018-08-20 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/hicolor-icon-theme/+bug/1787873/+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 1710637] Re: Input falls through to gdm3 and terminates the session on Ctrl+C after udevadm trigger is executed under wayland
I've just experienced this problem again. The following packages were just updated (from /var/log/apt/history.log): Start-Date: 2018-07-31 09:48:46 Commandline: aptdaemon role='role-commit-packages' sender=':1.2928' Upgrade: intel-microcode:amd64 (3.20180425.1~ubuntu0.18.04.1, 3.20180425.1~ubuntu0.18.04.2), console-setup-linux:amd64 (1.178ubuntu2.2, 1.178ubuntu2.3), console-setup:amd64 (1.178ubuntu2.2, 1.178ubuntu2.3), libmysqlclient20:amd64 (5.7.22-0ubuntu18.04.1, 5.7.23-0ubuntu0.18.04.1), keyboard-configuration:amd64 (1.178ubuntu2.2, 1.178ubuntu2.3) End-Date: 2018-07-31 09:49:23 -- 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/1710637 Title: Input falls through to gdm3 and terminates the session on Ctrl+C after udevadm trigger is executed under wayland Status in Snappy: Won't Fix Status in console-setup package in Ubuntu: Fix Released Status in gdm3 package in Ubuntu: Invalid Status in gnome-shell package in Ubuntu: Invalid Status in mutter package in Ubuntu: Invalid Status in systemd package in Ubuntu: Invalid Status in console-setup source package in Trusty: New Status in gdm3 source package in Trusty: New Status in gnome-shell source package in Trusty: New Status in mutter source package in Trusty: New Status in systemd source package in Trusty: New Status in console-setup source package in Xenial: New Status in gdm3 source package in Xenial: New Status in gnome-shell source package in Xenial: New Status in mutter source package in Xenial: New Status in systemd source package in Xenial: New Bug description: = Test Cases = Test Case 1: - Login under Wayland (session Ubuntu) - Open a terminal - snap install gimp - Wait until installation finishes successfully - In the terminal window press CTRL+C Result: - Expected: ^C is displayed in the terminal and the prompt is at the start of a new line - Actual: The session is terminated and the login screen is displayed Test Case 2: - Login under Wayland (session Ubuntu) - Open a terminal and type the following command: $ sudo udevadm trigger - In the terminal window press CTRL+C Result - Expected: ^C is displayed in the terminal and the prompt is at the start of a new line - Actual: The session is terminated and the login screen is displayed = Original Description = Multiple times a day I find myself without a session after hitting Ctrl+C in a terminal, it seems the input falls through the Ubuntu/GNOME session and to gdm, which itself decides to terminate. Even worse, when this happens, you can briefly see your login password in plaintext in the virtual terminal. You can see the password however long you want if you stop the gdm service when this happens. I don't have a good way to reproduce, but it seems locking the session with a keyboard shortcut, subsequently unlocking it, maybe suspending, at some point brings this behaviour into the picture, until the session dies with a Ctrl+C. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gdm3 3.24.2-1ubuntu9 ProcVersionSignature: Ubuntu 4.11.0-13.19-generic 4.11.12 Uname: Linux 4.11.0-13-generic x86_64 NonfreeKernelModules: zfs zunicode zavl zcommon znvpair ApportVersion: 2.20.6-0ubuntu5 Architecture: amd64 CurrentDesktop: GNOME Date: Mon Aug 14 15:54:34 2017 InstallationDate: Installed on 2016-05-06 (464 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) SourcePackage: gdm3 UpgradeStatus: Upgraded to artful on 2017-07-19 (25 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/snappy/+bug/1710637/+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 1755863] Re: netbooting the bionic live CD over NFS goes straight to maintenance mode :
I've just checked: a NFS boot image built from the currently released Ubuntu 18.04 still has this bug. I can't see any relevant commits to casper or systemd, either. -- 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/1755863 Title: netbooting the bionic live CD over NFS goes straight to maintenance mode : Status in casper package in Ubuntu: Fix Released Status in systemd package in Ubuntu: Fix Released Bug description: netbooting the bionic live CD[1] over NFS goes straight to maintenance mode : [1] http://cdimage.ubuntu.com/daily-live/current/ # casper.log Begin: Adding live session user... ... dbus-daemon[568]: [session uid=999 pid=568] Activating service name='org.gtk.vfs.Daemon' requested by ':1.0' (uid=999 pid=569 comm="" label="unconfined") dbus-daemon[568]: [session uid=999 pid=568] Successfully activated service 'org.gtk.vfs.Daemon' dbus-daemon[568]: [session uid=999 pid=568] Activating service name='org.gtk.vfs.Metadata' requested by ':1.0' (uid=999 pid=569 comm="" label="unconfined") fuse: device not found, try 'modprobe fuse' first dbus-daemon[568]: [session uid=999 pid=568] Successfully activated service 'org.gtk.vfs.Metadata' (gvfsd-metadata:580): GUdev-CRITICAL **: 16:28:56.270: g_udev_device_has_property: assertion 'G_UDEV_IS_DEVICE (device)' failed (gvfsd-metadata:580): GUdev-CRITICAL **: 16:28:56.270: g_udev_device_has_property: assertion 'G_UDEV_IS_DEVICE (device)' failed A connection to the bus can't be made done. Begin: Setting up init... ... done. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/casper/+bug/1755863/+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 1203718] Re: hud-service is consuming too much recources
This appears to be a problem in Ubuntu 16.04, where hud-service is taking up 2.4 GB of RAM after 27 days on my system. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to hud in Ubuntu. https://bugs.launchpad.net/bugs/1203718 Title: hud-service is consuming too much recources Status in Unity HUD: New Status in hud package in Ubuntu: Confirmed Bug description: For a couple of days now (I assume since recent Unity updates), my Laptop is performing more an more poor throughout the day. First 2-3 hours Unity is running smoothly (Dash, HUD, etc.) Afterwards, opening Dash or HUD and even switching workspaces and starting applications becomes very slow. Sometimes I have to restart lightdm from a tty-console or reboot. Running "top" in a terminal shows that a process called "hud-service" is consuming up to 60% of CPU and RAM resources. My hardware should be perfectly able to cope with 13.04 (Dell Latitude E5420, quad-core, 8GB RAM) and was until about two weeks before. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: unity 7.0.0daily13.04.18~13.04-0ubuntu1 ProcVersionSignature: Ubuntu 3.8.0-26.38-generic 3.8.13.2 Uname: Linux 3.8.0-26-generic x86_64 ApportVersion: 2.9.2-0ubuntu8.1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' Date: Mon Jul 22 13:49:15 2013 InstallationDate: Installed on 2013-04-25 (87 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) MarkForUpload: True ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/hud/+bug/1203718/+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 1762813] [NEW] package util-linux 2.27.1-6ubuntu3.5 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
Public bug reported: Regular software upgrade fails ProblemType: Package DistroRelease: Ubuntu 16.04 Package: util-linux 2.27.1-6ubuntu3.5 ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19 Uname: Linux 4.4.0-38-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.4 Architecture: amd64 Date: Tue Apr 10 20:02:57 2018 ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationDate: Installed on 2015-10-17 (906 days ago) InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.18 SourcePackage: util-linux Title: package util-linux 2.27.1-6ubuntu3.5 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: Upgraded to xenial on 2016-07-30 (619 days ago) ** Affects: util-linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package package-from-proposed xenial -- 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/1762813 Title: package util-linux 2.27.1-6ubuntu3.5 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 Status in util-linux package in Ubuntu: New Bug description: Regular software upgrade fails ProblemType: Package DistroRelease: Ubuntu 16.04 Package: util-linux 2.27.1-6ubuntu3.5 ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19 Uname: Linux 4.4.0-38-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.4 Architecture: amd64 Date: Tue Apr 10 20:02:57 2018 ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationDate: Installed on 2015-10-17 (906 days ago) InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.18 SourcePackage: util-linux Title: package util-linux 2.27.1-6ubuntu3.5 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: Upgraded to xenial on 2016-07-30 (619 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1762813/+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 1756632] [NEW] lightdm crashed with SIGSEGV in _dl_fini()
Public bug reported: Crash occured on boot ProblemType: Crash DistroRelease: Ubuntu 18.04 Package: lightdm 1.25.2-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7 Uname: Linux 4.15.0-10-generic x86_64 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 Date: Sat Mar 17 21:41:53 2018 ExecutablePath: /usr/sbin/lightdm InstallationDate: Installed on 2017-10-24 (144 days ago) InstallationMedia: Xubuntu 17.10 "Artful Aardvark" - Release amd64 (20171017.1) LightdmConfig: [Seat:*] autologin-guest=false autologin-user=skellat autologin-user-timeout=0 ProcCmdline: lightdm --session-child 12 15 ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SegvAnalysis: Segfault happened at: 0x7f4cc21acb3a <_dl_fini+410>: mov0x8(%rax),%r15 PC (0x7f4cc21acb3a) ok source "0x8(%rax)" (0x7f4cbe73ee78) not located in a known VMA region (needed readable region)! destination "%r15" ok SegvReason: reading unknown VMA Signal: 11 SourcePackage: lightdm StacktraceTop: _dl_fini () at dl-fini.c:134 __run_exit_handlers (status=0, listp=0x7f4cc0d19718 <__exit_funcs>, run_list_atexit=run_list_atexit@entry=true, run_dtors=run_dtors@entry=true) at exit.c:108 __GI_exit (status=) at exit.c:139 () () at /lib/x86_64-linux-gnu/libc.so.6 Title: lightdm crashed with SIGSEGV in _dl_fini() UpgradeStatus: Upgraded to bionic on 2018-02-19 (26 days ago) UserGroups: ** Affects: lightdm (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-crash bionic need-amd64-retrace ** 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 lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1756632 Title: lightdm crashed with SIGSEGV in _dl_fini() Status in lightdm package in Ubuntu: New Bug description: Crash occured on boot ProblemType: Crash DistroRelease: Ubuntu 18.04 Package: lightdm 1.25.2-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7 Uname: Linux 4.15.0-10-generic x86_64 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 Date: Sat Mar 17 21:41:53 2018 ExecutablePath: /usr/sbin/lightdm InstallationDate: Installed on 2017-10-24 (144 days ago) InstallationMedia: Xubuntu 17.10 "Artful Aardvark" - Release amd64 (20171017.1) LightdmConfig: [Seat:*] autologin-guest=false autologin-user=skellat autologin-user-timeout=0 ProcCmdline: lightdm --session-child 12 15 ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SegvAnalysis: Segfault happened at: 0x7f4cc21acb3a <_dl_fini+410>: mov0x8(%rax),%r15 PC (0x7f4cc21acb3a) ok source "0x8(%rax)" (0x7f4cbe73ee78) not located in a known VMA region (needed readable region)! destination "%r15" ok SegvReason: reading unknown VMA Signal: 11 SourcePackage: lightdm StacktraceTop: _dl_fini () at dl-fini.c:134 __run_exit_handlers (status=0, listp=0x7f4cc0d19718 <__exit_funcs>, run_list_atexit=run_list_atexit@entry=true, run_dtors=run_dtors@entry=true) at exit.c:108 __GI_exit (status=) at exit.c:139 () () at /lib/x86_64-linux-gnu/libc.so.6 Title: lightdm crashed with SIGSEGV in _dl_fini() UpgradeStatus: Upgraded to bionic on 2018-02-19 (26 days ago) UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1756632/+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 1751892] Re: Unable to set different Scale on different Monitors
Note the missing apply button is also mentioned in #1745440 -- 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/1751892 Title: Unable to set different Scale on different Monitors Status in xorg package in Ubuntu: New Bug description: My laptop screen is 3840x2160 while my external monitor is only 1680x1050. In order for the laptop monitor to be usable I have the scaling set at 200 (this works wonderful). However, when I plug in my external monitor it is scaled up to 200% as well making it unusable. Attempting to scale one to 100 and the other 200 looks to be possible; however, the Apply button keeps appearing and disappearing randomly with no actual effect. It looks like practically you can only set one scale for both monitors even though the UI looks to be letting you do it. I have tried this on Wayland and Xorg with similar results. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: xorg 1:7.7+19ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-36.40-generic 4.13.13 Uname: Linux 4.13.0-36-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Feb 26 15:12:53 2018 DistUpgraded: Fresh install DistroCodename: artful DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation Device [8086:5917] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Device [103c:83b9] InstallationDate: Installed on 2018-02-21 (5 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1) MachineType: HP HP Spectre x360 Convertible 13-ae0xx ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-36-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/23/2018 dmi.bios.vendor: AMI dmi.bios.version: F.14 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 83B9 dmi.board.vendor: HP dmi.board.version: 56.37 dmi.chassis.type: 31 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAMI:bvrF.14:bd01/23/2018:svnHP:pnHPSpectrex360Convertible13-ae0xx:pvr:rvnHP:rn83B9:rvr56.37:cvnHP:ct31:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Spectre dmi.product.name: HP Spectre x360 Convertible 13-ae0xx dmi.sys.vendor: HP version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.83-1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.8-0ubuntu0~17.10.1 version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.8-0ubuntu0~17.10.1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20170309-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1751892/+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 1689825] Re: gnome-keyring not unlocked on xenial when dbus-user-session is installed
After killing and restarting the keyring which fixed Network Manager, then Chromium developed a slow start problem caused by gnome-keyring. smm@laptop ~ $ chromium-browser --enable-logging=stderr ATTENTION: default value of option force_s3tc_enable overridden by environment. Gkr-Message: secret service operation failed: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken. [7981:7981:0314/102437.107901:WARNING:password_store_factory.cc(241)] Using basic (unencrypted) store for password storage. See https://chromium.googlesource.com/chromium/src/+/master/docs/linux_password_storage.md for more information about password storage options. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dbus in Ubuntu. https://bugs.launchpad.net/bugs/1689825 Title: gnome-keyring not unlocked on xenial when dbus-user-session is installed Status in chromium-browser package in Ubuntu: Invalid Status in dbus package in Ubuntu: Triaged Status in flatpak package in Ubuntu: Fix Released Bug description: 1) Release: 16.04.2 2) gnome-keyring: 3.18.3-0ubuntu2 3) Login. gnome-keyring unlocks "login" features including for google chrome 4) gnome-keyring is not unlocked, chrome takes 2 minutes to open and with no secure password features(sync) functioning. For the past couple days, chrome on Ubuntu 16.04 takes a REALLY long time (maybe 2 minutes) to start. Once chrome is started, I am not able to sync and any secure password features are broken. I found out this is due to gnome-keyring not being unlocked at login. There's also no way to unlock the "login" portion of the keyring from the running daemon by default. I have to kill the gnome-keyring process and start without "--login" as a parameter. Then the "login" section shows up which I'm able to unlock. From there chrome starts up instantly but asks the following: Enter password to unlock your login keyring The login keyring did not get unlocked when you logged into your computer After that, all of it's sync and secure features are functional. Starting google-chrome-stable from a command line at boot without running the above workaround shows the following error messages: Gkr-Message: secret service operation failed: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken. Gkr-Message: secret service operation failed: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken. [4364:4393:0510/100407.740292:ERROR:token_service_table.cc(130)] Failed to decrypt token for service AccountId-108842767310111573264 [4364:4445:0510/100407.740292:ERROR:gcm_store_impl.cc(929)] Failed to restore security token. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: gnome-keyring 3.18.3-0ubuntu2 ProcVersionSignature: Ubuntu 4.8.0-52.55~16.04.1-generic 4.8.17 Uname: Linux 4.8.0-52-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 CurrentDesktop: GNOME-Flashback:Unity Date: Wed May 10 09:43:37 2017 SourcePackage: gnome-keyring UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1689825/+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 1689825] Re: gnome-keyring not unlocked on xenial when dbus-user-session is installed
Every time I turn around, I have a no failure related to gnome-keyring. After having Chromium running for a few minutes it hangs again for a minute or so with the same error message: Gkr-Message: secret service operation failed: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken. Keyring may end up making Chromium unusable. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dbus in Ubuntu. https://bugs.launchpad.net/bugs/1689825 Title: gnome-keyring not unlocked on xenial when dbus-user-session is installed Status in chromium-browser package in Ubuntu: Invalid Status in dbus package in Ubuntu: Triaged Status in flatpak package in Ubuntu: Fix Released Bug description: 1) Release: 16.04.2 2) gnome-keyring: 3.18.3-0ubuntu2 3) Login. gnome-keyring unlocks "login" features including for google chrome 4) gnome-keyring is not unlocked, chrome takes 2 minutes to open and with no secure password features(sync) functioning. For the past couple days, chrome on Ubuntu 16.04 takes a REALLY long time (maybe 2 minutes) to start. Once chrome is started, I am not able to sync and any secure password features are broken. I found out this is due to gnome-keyring not being unlocked at login. There's also no way to unlock the "login" portion of the keyring from the running daemon by default. I have to kill the gnome-keyring process and start without "--login" as a parameter. Then the "login" section shows up which I'm able to unlock. From there chrome starts up instantly but asks the following: Enter password to unlock your login keyring The login keyring did not get unlocked when you logged into your computer After that, all of it's sync and secure features are functional. Starting google-chrome-stable from a command line at boot without running the above workaround shows the following error messages: Gkr-Message: secret service operation failed: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken. Gkr-Message: secret service operation failed: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken. [4364:4393:0510/100407.740292:ERROR:token_service_table.cc(130)] Failed to decrypt token for service AccountId-108842767310111573264 [4364:4445:0510/100407.740292:ERROR:gcm_store_impl.cc(929)] Failed to restore security token. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: gnome-keyring 3.18.3-0ubuntu2 ProcVersionSignature: Ubuntu 4.8.0-52.55~16.04.1-generic 4.8.17 Uname: Linux 4.8.0-52-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 CurrentDesktop: GNOME-Flashback:Unity Date: Wed May 10 09:43:37 2017 SourcePackage: gnome-keyring UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1689825/+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 1689825] Re: gnome-keyring not unlocked on xenial when dbus-user-session is installed
Running "chromium-browser --enable-logging=stderr" results in: $ chromium-browser --enable-logging=stderr ATTENTION: default value of option force_s3tc_enable overridden by environment. I'm also running the gnome-keyring-daemon in the foreground and see this message: ** (gnome-keyring-daemon:31165): WARNING **: asked to register item /org/freedesktop/secrets/collection/login/12, but it's already registered ** Message: The Secret Service was already initialized Chromium starts up quickly, but network manager can't access the keyring and hangs for a minute or two before it gives up when I try to connect to a VPN. Then it prompts me for the passwords, as it was unable to retrieve them from gnome-keyring. Killing and restarting the daemon fixes the problem. Every night I suspend my laptop when I go home and find the deamon is hung again the next morning. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dbus in Ubuntu. https://bugs.launchpad.net/bugs/1689825 Title: gnome-keyring not unlocked on xenial when dbus-user-session is installed Status in chromium-browser package in Ubuntu: Invalid Status in dbus package in Ubuntu: Triaged Status in flatpak package in Ubuntu: Fix Released Bug description: 1) Release: 16.04.2 2) gnome-keyring: 3.18.3-0ubuntu2 3) Login. gnome-keyring unlocks "login" features including for google chrome 4) gnome-keyring is not unlocked, chrome takes 2 minutes to open and with no secure password features(sync) functioning. For the past couple days, chrome on Ubuntu 16.04 takes a REALLY long time (maybe 2 minutes) to start. Once chrome is started, I am not able to sync and any secure password features are broken. I found out this is due to gnome-keyring not being unlocked at login. There's also no way to unlock the "login" portion of the keyring from the running daemon by default. I have to kill the gnome-keyring process and start without "--login" as a parameter. Then the "login" section shows up which I'm able to unlock. From there chrome starts up instantly but asks the following: Enter password to unlock your login keyring The login keyring did not get unlocked when you logged into your computer After that, all of it's sync and secure features are functional. Starting google-chrome-stable from a command line at boot without running the above workaround shows the following error messages: Gkr-Message: secret service operation failed: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken. Gkr-Message: secret service operation failed: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken. [4364:4393:0510/100407.740292:ERROR:token_service_table.cc(130)] Failed to decrypt token for service AccountId-108842767310111573264 [4364:4445:0510/100407.740292:ERROR:gcm_store_impl.cc(929)] Failed to restore security token. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: gnome-keyring 3.18.3-0ubuntu2 ProcVersionSignature: Ubuntu 4.8.0-52.55~16.04.1-generic 4.8.17 Uname: Linux 4.8.0-52-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 CurrentDesktop: GNOME-Flashback:Unity Date: Wed May 10 09:43:37 2017 SourcePackage: gnome-keyring UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1689825/+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 1689825] Re: gnome-keyring not unlocked on xenial when dbus-user-session is installed
Olivier: 1) Yes 2) Yes 3) Yes 4) I'll have to log out and/or reboot to get it back into that state. Will post when I get a chance to do that. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dbus in Ubuntu. https://bugs.launchpad.net/bugs/1689825 Title: gnome-keyring not unlocked on xenial when dbus-user-session is installed Status in chromium-browser package in Ubuntu: Invalid Status in dbus package in Ubuntu: Triaged Status in flatpak package in Ubuntu: Fix Released Bug description: 1) Release: 16.04.2 2) gnome-keyring: 3.18.3-0ubuntu2 3) Login. gnome-keyring unlocks "login" features including for google chrome 4) gnome-keyring is not unlocked, chrome takes 2 minutes to open and with no secure password features(sync) functioning. For the past couple days, chrome on Ubuntu 16.04 takes a REALLY long time (maybe 2 minutes) to start. Once chrome is started, I am not able to sync and any secure password features are broken. I found out this is due to gnome-keyring not being unlocked at login. There's also no way to unlock the "login" portion of the keyring from the running daemon by default. I have to kill the gnome-keyring process and start without "--login" as a parameter. Then the "login" section shows up which I'm able to unlock. From there chrome starts up instantly but asks the following: Enter password to unlock your login keyring The login keyring did not get unlocked when you logged into your computer After that, all of it's sync and secure features are functional. Starting google-chrome-stable from a command line at boot without running the above workaround shows the following error messages: Gkr-Message: secret service operation failed: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken. Gkr-Message: secret service operation failed: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken. [4364:4393:0510/100407.740292:ERROR:token_service_table.cc(130)] Failed to decrypt token for service AccountId-108842767310111573264 [4364:4445:0510/100407.740292:ERROR:gcm_store_impl.cc(929)] Failed to restore security token. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: gnome-keyring 3.18.3-0ubuntu2 ProcVersionSignature: Ubuntu 4.8.0-52.55~16.04.1-generic 4.8.17 Uname: Linux 4.8.0-52-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 CurrentDesktop: GNOME-Flashback:Unity Date: Wed May 10 09:43:37 2017 SourcePackage: gnome-keyring UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1689825/+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 1689825] Re: gnome-keyring not unlocked on xenial when dbus-user-session is installed
- I'm seeing slow downs. - I'm not using automatic login. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dbus in Ubuntu. https://bugs.launchpad.net/bugs/1689825 Title: gnome-keyring not unlocked on xenial when dbus-user-session is installed Status in chromium-browser package in Ubuntu: Invalid Status in dbus package in Ubuntu: Triaged Status in flatpak package in Ubuntu: Fix Released Bug description: 1) Release: 16.04.2 2) gnome-keyring: 3.18.3-0ubuntu2 3) Login. gnome-keyring unlocks "login" features including for google chrome 4) gnome-keyring is not unlocked, chrome takes 2 minutes to open and with no secure password features(sync) functioning. For the past couple days, chrome on Ubuntu 16.04 takes a REALLY long time (maybe 2 minutes) to start. Once chrome is started, I am not able to sync and any secure password features are broken. I found out this is due to gnome-keyring not being unlocked at login. There's also no way to unlock the "login" portion of the keyring from the running daemon by default. I have to kill the gnome-keyring process and start without "--login" as a parameter. Then the "login" section shows up which I'm able to unlock. From there chrome starts up instantly but asks the following: Enter password to unlock your login keyring The login keyring did not get unlocked when you logged into your computer After that, all of it's sync and secure features are functional. Starting google-chrome-stable from a command line at boot without running the above workaround shows the following error messages: Gkr-Message: secret service operation failed: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken. Gkr-Message: secret service operation failed: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken. [4364:4393:0510/100407.740292:ERROR:token_service_table.cc(130)] Failed to decrypt token for service AccountId-108842767310111573264 [4364:4445:0510/100407.740292:ERROR:gcm_store_impl.cc(929)] Failed to restore security token. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: gnome-keyring 3.18.3-0ubuntu2 ProcVersionSignature: Ubuntu 4.8.0-52.55~16.04.1-generic 4.8.17 Uname: Linux 4.8.0-52-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 CurrentDesktop: GNOME-Flashback:Unity Date: Wed May 10 09:43:37 2017 SourcePackage: gnome-keyring UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1689825/+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 1689825] Re: gnome-keyring not unlocked on xenial when dbus-user-session is installed
This bug is not resolved. Seeing it under 16.04LTS without dbus-user- session or flatpak installed. smm@laptop /var/log $ sudo apt list --installed |grep dbus-user-session WARNING: apt does not have a stable CLI interface. Use with caution in scripts. smm@laptop /var/log $ sudo apt list --installed |grep flatpak WARNING: apt does not have a stable CLI interface. Use with caution in scripts. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dbus in Ubuntu. https://bugs.launchpad.net/bugs/1689825 Title: gnome-keyring not unlocked on xenial when dbus-user-session is installed Status in chromium-browser package in Ubuntu: Invalid Status in dbus package in Ubuntu: Triaged Status in flatpak package in Ubuntu: Fix Released Bug description: 1) Release: 16.04.2 2) gnome-keyring: 3.18.3-0ubuntu2 3) Login. gnome-keyring unlocks "login" features including for google chrome 4) gnome-keyring is not unlocked, chrome takes 2 minutes to open and with no secure password features(sync) functioning. For the past couple days, chrome on Ubuntu 16.04 takes a REALLY long time (maybe 2 minutes) to start. Once chrome is started, I am not able to sync and any secure password features are broken. I found out this is due to gnome-keyring not being unlocked at login. There's also no way to unlock the "login" portion of the keyring from the running daemon by default. I have to kill the gnome-keyring process and start without "--login" as a parameter. Then the "login" section shows up which I'm able to unlock. From there chrome starts up instantly but asks the following: Enter password to unlock your login keyring The login keyring did not get unlocked when you logged into your computer After that, all of it's sync and secure features are functional. Starting google-chrome-stable from a command line at boot without running the above workaround shows the following error messages: Gkr-Message: secret service operation failed: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken. Gkr-Message: secret service operation failed: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken. [4364:4393:0510/100407.740292:ERROR:token_service_table.cc(130)] Failed to decrypt token for service AccountId-108842767310111573264 [4364:4445:0510/100407.740292:ERROR:gcm_store_impl.cc(929)] Failed to restore security token. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: gnome-keyring 3.18.3-0ubuntu2 ProcVersionSignature: Ubuntu 4.8.0-52.55~16.04.1-generic 4.8.17 Uname: Linux 4.8.0-52-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 CurrentDesktop: GNOME-Flashback:Unity Date: Wed May 10 09:43:37 2017 SourcePackage: gnome-keyring UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1689825/+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 1537528] Re: byobu-config segfault with screen backend
Found this reference to it - https://bugs.debian.org/cgi- bin/bugreport.cgi?bug=837868 ** Bug watch added: Debian Bug tracker #837868 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=837868 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to newt in Ubuntu. https://bugs.launchpad.net/bugs/1537528 Title: byobu-config segfault with screen backend Status in byobu package in Ubuntu: In Progress Status in newt package in Ubuntu: Confirmed Status in byobu package in Debian: New Bug description: When running byobu with the screen backend byobu-config segfaults when trying to open it by pressing F9. Steps to reproduce. 1. Configure byobu to use screen for the backend 2. Press F9 to open the configuration menu 3. The console flashes then returns to your shell window. Running byobu-config manually within a byobu screen session shows it's segfaulting. It does not crash running it outside of screen. byobu: Installed: 5.101-0ubuntu1~wily Candidate: 5.101-0ubuntu1~wily Version table: *** 5.101-0ubuntu1~wily 0 500 http://ppa.launchpad.net/byobu/ppa/ubuntu/ wily/main amd64 Packages 100 /var/lib/dpkg/status 5.97-0ubuntu1 0 500 http://mirror.us.leaseweb.net/ubuntu/ wily/main amd64 Packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/byobu/+bug/1537528/+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 1537528] Re: byobu-config segfault with screen backend
Have same problem on 16.04.4 with byobu package 5.106-0ubuntu1 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to newt in Ubuntu. https://bugs.launchpad.net/bugs/1537528 Title: byobu-config segfault with screen backend Status in byobu package in Ubuntu: In Progress Status in newt package in Ubuntu: Confirmed Status in byobu package in Debian: New Bug description: When running byobu with the screen backend byobu-config segfaults when trying to open it by pressing F9. Steps to reproduce. 1. Configure byobu to use screen for the backend 2. Press F9 to open the configuration menu 3. The console flashes then returns to your shell window. Running byobu-config manually within a byobu screen session shows it's segfaulting. It does not crash running it outside of screen. byobu: Installed: 5.101-0ubuntu1~wily Candidate: 5.101-0ubuntu1~wily Version table: *** 5.101-0ubuntu1~wily 0 500 http://ppa.launchpad.net/byobu/ppa/ubuntu/ wily/main amd64 Packages 100 /var/lib/dpkg/status 5.97-0ubuntu1 0 500 http://mirror.us.leaseweb.net/ubuntu/ wily/main amd64 Packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/byobu/+bug/1537528/+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 1751892] [NEW] Unable to set different Scale on different Monitors
Public bug reported: My laptop screen is 3840x2160 while my external monitor is only 1680x1050. In order for the laptop monitor to be usable I have the scaling set at 200 (this works wonderful). However, when I plug in my external monitor it is scaled up to 200% as well making it unusable. Attempting to scale one to 100 and the other 200 looks to be possible; however, the Apply button keeps appearing and disappearing randomly with no actual effect. It looks like practically you can only set one scale for both monitors even though the UI looks to be letting you do it. I have tried this on Wayland and Xorg with similar results. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: xorg 1:7.7+19ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-36.40-generic 4.13.13 Uname: Linux 4.13.0-36-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Feb 26 15:12:53 2018 DistUpgraded: Fresh install DistroCodename: artful DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation Device [8086:5917] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Device [103c:83b9] InstallationDate: Installed on 2018-02-21 (5 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1) MachineType: HP HP Spectre x360 Convertible 13-ae0xx ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-36-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/23/2018 dmi.bios.vendor: AMI dmi.bios.version: F.14 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 83B9 dmi.board.vendor: HP dmi.board.version: 56.37 dmi.chassis.type: 31 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAMI:bvrF.14:bd01/23/2018:svnHP:pnHPSpectrex360Convertible13-ae0xx:pvr:rvnHP:rn83B9:rvr56.37:cvnHP:ct31:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Spectre dmi.product.name: HP Spectre x360 Convertible 13-ae0xx dmi.sys.vendor: HP version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.83-1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.8-0ubuntu0~17.10.1 version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.8-0ubuntu0~17.10.1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20170309-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug artful 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/1751892 Title: Unable to set different Scale on different Monitors Status in xorg package in Ubuntu: New Bug description: My laptop screen is 3840x2160 while my external monitor is only 1680x1050. In order for the laptop monitor to be usable I have the scaling set at 200 (this works wonderful). However, when I plug in my external monitor it is scaled up to 200% as well making it unusable. Attempting to scale one to 100 and the other 200 looks to be possible; however, the Apply button keeps appearing and disappearing randomly with no actual effect. It looks like practically you can only set one scale for both monitors even though the UI looks to be letting you do it. I have tried this on Wayland and Xorg with similar results. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: xorg 1:7.7+19ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-36.40-generic 4.13.13 Uname: Linux 4.13.0-36-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Feb 26 15:12:53 2018 DistUpgraded: Fresh install DistroCodename: artful DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation Device [8086:5917] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Device [103c:83b9] InstallationDate: Installed on 2018-02-21 (5 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1) MachineType: HP HP Spectre x360 Convertible 13-ae0xx ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine:
[Touch-packages] [Bug 1749597] Re: [aarch64] gas: Error: non-constant expression in ".if" statement
For my own understanding, I'm curious: a) Whether Ubuntu toolchains are usually updated for bugs like this b) Roughly how often toolchain updates are usually released. I suppose you're busy with Spectre stuff right now though? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to binutils in Ubuntu. https://bugs.launchpad.net/bugs/1749597 Title: [aarch64] gas: Error: non-constant expression in ".if" statement Status in binutils: Fix Released Status in binutils package in Ubuntu: New Bug description: gas in binutils 2.26 contains a bug that prevents compilation of ARM Trusted Firmware in particular, or any code that references the "." symbol following a .align statement that specifies explicit padding data. ATF bug report: https://github.com/ARM-software/tf-issues/issues/401 binutils bug report: https://sourceware.org/bugzilla/show_bug.cgi?id=20364 To manage notifications about this bug go to: https://bugs.launchpad.net/binutils/+bug/1749597/+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 1750586] Re: package python-minimal 2.7.12-1~16.04 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
The post installation file /var/lib/dpkg/info/python-minimal.postinst runs the following command: python2.7 -m compileall /usr/share/python/ >/dev/null Running the command manually (without the /dev/null redirect) produces the following error for me: Compiling /usr/share/python/rekall-forensic/lib/python2.7/site-packages/pexpect/async.py ... File "/usr/share/python/rekall-forensic/lib/python2.7/site-packages/pexpect/async.py", line 16 transport, pw = yield from asyncio.get_event_loop()\ ^ SyntaxError: invalid syntax I removed the /usr/share/python/rekall-forensic folder and was able to "apt install -f". Likely a different package is causing you trouble, but try running that command for more information. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python-defaults in Ubuntu. https://bugs.launchpad.net/bugs/1750586 Title: package python-minimal 2.7.12-1~16.04 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 Status in python-defaults package in Ubuntu: Confirmed Bug description: There seems to be a dependency snarl: python-minimal is already the newest version (2.7.12-1~16.04). python-minimal set to manually installed. You might want to run 'apt-get -f install' to correct these: The following packages have unmet dependencies: python : PreDepends: python-minimal (= 2.7.11-1) but 2.7.12-1~16.04 is to be installed python-all : Depends: python (= 2.7.12-1~16.04) but 2.7.11-1 is to be installed python-all-dev : Depends: python (= 2.7.12-1~16.04) but 2.7.11-1 is to be installed Depends: libpython-all-dev (= 2.7.12-1~16.04) but 2.7.11-1 is to be installed python-dev : Depends: python (= 2.7.12-1~16.04) but 2.7.11-1 is to be installed Depends: libpython-dev (= 2.7.12-1~16.04) but 2.7.11-1 is to be installed E: Unmet dependencies. Try 'apt-get -f install' with no packages (or specify a solution). apt-get -f install tries to set up python-minimal (2.7.12-1~16.04) and returns 1. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: python-minimal 2.7.12-1~16.04 ProcVersionSignature: Ubuntu 4.4.0-109.132-generic 4.4.98 Uname: Linux 4.4.0-109-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 Date: Tue Feb 20 08:48:01 2018 DuplicateSignature: package:python-minimal:2.7.12-1~16.04 Setting up python-minimal (2.7.12-1~16.04) ... dpkg: error processing package python-minimal (--configure): subprocess installed post-installation script returned error exit status 1 ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationDate: Installed on 2016-10-23 (484 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) RelatedPackageVersions: dpkg 1.18.4ubuntu1.3 apt 1.2.25 SourcePackage: python-defaults Title: package python-minimal 2.7.12-1~16.04 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-defaults/+bug/1750586/+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 1749597] [NEW] [aarch64] gas: Error: non-constant expression in ".if" statement
Public bug reported: gas in binutils 2.26 contains a bug that prevents compilation of ARM Trusted Firmware in particular, or any code that references the "." symbol following a .align statement that specifies explicit padding data. ATF bug report: https://github.com/ARM-software/tf-issues/issues/401 binutils bug report: https://sourceware.org/bugzilla/show_bug.cgi?id=20364 ** Affects: binutils Importance: Unknown Status: Unknown ** Affects: binutils (Ubuntu) Importance: Undecided Status: New ** Bug watch added: Sourceware.org Bugzilla #20364 https://sourceware.org/bugzilla/show_bug.cgi?id=20364 ** Also affects: binutils via https://sourceware.org/bugzilla/show_bug.cgi?id=20364 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to binutils in Ubuntu. https://bugs.launchpad.net/bugs/1749597 Title: [aarch64] gas: Error: non-constant expression in ".if" statement Status in binutils: Unknown Status in binutils package in Ubuntu: New Bug description: gas in binutils 2.26 contains a bug that prevents compilation of ARM Trusted Firmware in particular, or any code that references the "." symbol following a .align statement that specifies explicit padding data. ATF bug report: https://github.com/ARM-software/tf-issues/issues/401 binutils bug report: https://sourceware.org/bugzilla/show_bug.cgi?id=20364 To manage notifications about this bug go to: https://bugs.launchpad.net/binutils/+bug/1749597/+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