[Bug 1864282] [NEW] loader error
Public bug reported: no information on why or where to install the grub-installer, several failed attempts ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: ubiquity 18.04.14.12 ProcVersionSignature: Ubuntu 5.0.0-23.24~18.04.1-generic 5.0.15 Uname: Linux 5.0.0-23-generic i686 ApportVersion: 2.20.9-0ubuntu7.7 Architecture: i386 Date: Sat Feb 22 00:49:13 2020 InstallCmdLine: BOOT_IMAGE=/AIO/Files/Linux/lubuntu-18.04.3-desktop-i386/casper/vmlinuz file=/AIO/Files/Linux/lubuntu-18.04.3-desktop-i386/preseed/lubuntu.seed boot=casper live-media-path=/AIO/Files/Linux/lubuntu-18.04.3-desktop-i386/casper/ persistent persistent-path=/AIO/Files/Linux/lubuntu-18.04.3-desktop-i386/ cdrom-detect/try-usb=true noprompt floppy.allowed_drive_mask=0 ignore_uuid only-ubiquity quiet splash --- ProcEnviron: LANGUAGE=en_CA.UTF-8 PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_CA.UTF-8 LC_NUMERIC=C.UTF-8 SourcePackage: grub-installer UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: grub-installer (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug bionic i386 lubuntu ubiquity-18.04.14.12 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1864282 Title: loader error To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub-installer/+bug/1864282/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1863825] Re: 20.04 apt update of python 3.8 gives errors
We can reproduce following command: $ sudo py3compile -p python3-apport -V 3.0- /usr/lib/python3.8/subprocess.py:838: RuntimeWarning: line buffering (buffering=1) isn't supported in binary mode, the default buffer size will be used self.stdin = io.open(p2cwrite, 'wb', bufsize) py3comipe set "bufsize=1" for subprocess.Popen(): https://salsa.debian.org/cpython- team/python3-defaults/blob/master/py3compile#L132-133 process = Popen(cmd, bufsize=1, shell=True, stdin=PIPE, close_fds=True) However newer python (from 3.8?) warn on buffering=1. * https://github.com/python/cpython/commit/a2670565d8f5c502388378aba1fe73023fd8c8d4 * https://bugs.python.org/issue32236 ** Bug watch added: Python Roundup #32236 http://bugs.python.org/issue32236 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1863825 Title: 20.04 apt update of python 3.8 gives errors To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python3-defaults/+bug/1863825/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1863414] Re: Have many "/usr/lib/python3.8/subprocess.py:838: RuntimeWarning: line buffering (buffering=1) isn't supported in binary mode, the default buffer size will be used" on simple APT usag
We can reproduce following command: $ sudo py3compile -p python3-apport -V 3.0- /usr/lib/python3.8/subprocess.py:838: RuntimeWarning: line buffering (buffering=1) isn't supported in binary mode, the default buffer size will be used self.stdin = io.open(p2cwrite, 'wb', bufsize) py3comipe set "bufsize=1" for subprocess.Popen(): https://salsa.debian.org/cpython-team/python3-defaults/blob/master/py3compile#L132-133 process = Popen(cmd, bufsize=1, shell=True, stdin=PIPE, close_fds=True) However newer python (from 3.8?) warn on buffering=1. * https://github.com/python/cpython/commit/a2670565d8f5c502388378aba1fe73023fd8c8d4 * https://bugs.python.org/issue32236 ** Bug watch added: Python Roundup #32236 http://bugs.python.org/issue32236 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1863414 Title: Have many "/usr/lib/python3.8/subprocess.py:838: RuntimeWarning: line buffering (buffering=1) isn't supported in binary mode, the default buffer size will be used" on simple APT usage To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python3.8/+bug/1863414/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1863414] Re: Have many "/usr/lib/python3.8/subprocess.py:838: RuntimeWarning: line buffering (buffering=1) isn't supported in binary mode, the default buffer size will be used" on simple APT usag
sorry, i commented to wrong ticket. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1863414 Title: Have many "/usr/lib/python3.8/subprocess.py:838: RuntimeWarning: line buffering (buffering=1) isn't supported in binary mode, the default buffer size will be used" on simple APT usage To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python3.8/+bug/1863414/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1864162] Re: Don't install snap programs.
Another test: root@ubuntu:~/vlc-new-snap# sudo snap ack vlc_1397.assert root@ubuntu:~/vlc-new-snap# sudo snap install vlc_1397.snap error: too early for operation, device model not yet acknowledged root@ubuntu:~/vlc-new-snap# -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1864162 Title: Don't install snap programs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1864162/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1864162] Re: Don't install snap programs.
Thank you, sorry but I will not give launchpad access to my private data. I often use the live version of ubuntu focal fossa. I update it often. I also have a pendrive the version of 24-01-2020 in case of problems to compare the difference between the execution of the most recent version and that of 24-01-2020. See you. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1864162 Title: Don't install snap programs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1864162/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1864283] [NEW] extract_upstream_tarball fails
Public bug reported:
I am trying to use recipes in lanchpad and my very simple recipe fails.
Version: git-build-recipe 0.3.6~git201906051340.ff11471~ubuntu16.04.1
https://launchpadlibrarian.net/466083953/buildlog.txt.gz
Traceback (most recent call last):
File "/usr/bin/git-build-recipe", line 9, in
load_entry_point('git-build-recipe==0.1', 'console_scripts',
'git-build-recipe')()
File "/usr/lib/python3/dist-packages/gitbuildrecipe/main.py", line 164, in
main
package_version.upstream_version, working_basedir)
File "/usr/lib/python3/dist-packages/gitbuildrecipe/deb_util.py", line 74, in
extract_upstream_tarball
cwd=path)
File "/usr/lib/python3.5/subprocess.py", line 581, in check_call
raise CalledProcessError(retcode, cmd)
https://code.launchpad.net/~phpmyadmin/+recipe/phpmyadmin-daily
# git-build-recipe format 0.4 deb-version {debupstream}-0~{revtime}
lp:phpmyadmin ubuntu-ppa
I see no reason for this crash
Mirror: https://code.launchpad.net/~phpmyadmin/phpmyadmin/+git
/phpmyadmin-debian/+ref/ubuntu-ppa
Source: https://salsa.debian.org/phpmyadmin-team/phpmyadmin/tree/ubuntu-
ppa
The file exists on https://salsa.debian.org/phpmyadmin-
team/phpmyadmin/tree/pristine-tar
** Affects: git-build-recipe (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1864283
Title:
extract_upstream_tarball fails
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/git-build-recipe/+bug/1864283/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1805230] Re: Caja crashed while emptying trash
Bug is not invalid. Ubuntu coders just ignore their bugs and focus on screwing up the next release. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1805230 Title: Caja crashed while emptying trash To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-mate/+bug/1805230/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1864283] Re: extract_upstream_tarball fails
Changing recipe to
# git-build-recipe format 0.4 deb-version {debupstream}
Fixed the issue, but still if applicable fix your code
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1864283
Title:
extract_upstream_tarball fails
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/git-build-recipe/+bug/1864283/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1859277] Re: Please support riscv64 with {cow,p}builder-dist
See also https://code.launchpad.net/~misterc/ubuntu-dev-tools/+git
/ubuntu-dev-tools/+merge/379692 to add mips64el, hppa and x32 as well.
Maybe that could get merged and we could get a new release?
Thanks again,
** Changed in: ubuntu-dev-tools (Ubuntu)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1859277
Title:
Please support riscv64 with {cow,p}builder-dist
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-dev-tools/+bug/1859277/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1859277] Re: Please support riscv64 with {cow,p}builder-dist
Pardon me, I just saw that the fix for riscv64 was already released.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1859277
Title:
Please support riscv64 with {cow,p}builder-dist
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-dev-tools/+bug/1859277/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1864061] Re: PCI/internal sound card not detected
We need to backport the this commint, this is already backported to 5.4
focal kernel, but it is not in the eoan kernel yet:
commit 8ce1cbd6ce0b1bda0c980c64fee4c1e1378355f1
Author: Jaroslav Kysela
Date: Wed Jan 22 20:07:52 2020 +0100
ASoC: topology: fix soc_tplg_fe_link_create() - link->dobj initialization
order
The code which checks the return value for snd_soc_add_dai_link() call
in soc_tplg_fe_link_create() moved the snd_soc_add_dai_link() call before
link->dobj members initialization.
While it does not affect the latest kernels, the old soc-core.c code
in the stable kernels is affected. The snd_soc_add_dai_link() function uses
the link->dobj.type member to check, if the link structure is valid.
Reorder the link->dobj initialization to make things work again.
It's harmless for the recent code (and the structure should be properly
initialized before other calls anyway).
The problem is in stable linux-5.4.y since version 5.4.11 when the
upstream commit 76d270364932 was applied.
Fixes: 76d270364932 ("ASoC: topology: Check return value for
snd_soc_add_dai_link()")
Cc: Dragos Tarcatu
Cc: Pierre-Louis Bossart
Cc: Ranjani Sridharan
Cc: Mark Brown
Cc:
Signed-off-by: Jaroslav Kysela
Link: https://lore.kernel.org/r/20200122190752.3081016-1-pe...@perex.cz
Signed-off-by: Mark Brown
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1864061
Title:
PCI/internal sound card not detected
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1864061/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1596381] Re: [X555UA, Realtek ALC256, Mic, Internal] No sound at all
I have the same problem on Asus Zenbook UX430UA (Realtek ALC295) in Ubuntu 18.04 with 5.3.0-40-generic linux kernel version. Comment #8 fix's worked for me but now I get the same volume level from my laptop speakers with 1% volume level, than the one I get with 100% volume level. The only thing that I can change from volume controls is that with 0% volume level, the speakers are muted. I have tried with "options snd-hda-intel model=auto,laptop-dmic" but I get the expected behaviour with model=auto (speakers works great but no audio recording from laptop microphone). With "options snd-hda-intel model=laptop-dmic,auto" I get the same behaviour that the one I get with "model=laptop-dmic" only (microphone working but volume control doing nothing). I thought this was fixed, but maybe I'm doing something wrong. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1596381 Title: [X555UA, Realtek ALC256, Mic, Internal] No sound at all To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1596381/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1864284] [NEW] r8152 init may take up to 40 seconds at initialization with Dell WD19/WD19DC during hotplug
Public bug reported: TBD ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-5.0.0-1037-oem-osp1 5.0.0-1037.42 ProcVersionSignature: Ubuntu 5.0.0-1037.42-oem-osp1 5.0.21 Uname: Linux 5.0.0-1037-oem-osp1 x86_64 ApportVersion: 2.20.9-0ubuntu7.11 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: u 2014 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sat Feb 22 04:07:20 2020 DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-bionic-amd64-20180608-47+beaver-hodor+X95 InstallationDate: Installed on 2020-01-16 (37 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20180608-09:38 IwConfig: enp1s0no wireless extensions. enxd8d090035306 no wireless extensions. lono wireless extensions. MachineType: Dell Inc. Latitude 3310 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-1037-oem-osp1 root=UUID=1ad036ce-aa29-4d5e-8692-d980d1a7140f ro "dyndbg=file drivers/usb/* +pt" log_buf_len=32M ignore_loglevel usbcore.quirks=0bda:0487:k RelatedPackageVersions: linux-restricted-modules-5.0.0-1037-oem-osp1 N/A linux-backports-modules-5.0.0-1037-oem-osp1 N/A linux-firmware 1.173.15 SourcePackage: linux-oem-osp1 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/07/2020 dmi.bios.vendor: Dell Inc. dmi.bios.version: 99.51.2[V2 AMI] dmi.board.vendor: Dell Inc. dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr99.51.2[V2AMI]:bd01/07/2020:svnDellInc.:pnLatitude3310:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr: dmi.product.family: Latitude dmi.product.name: Latitude 3310 dmi.product.sku: 0A13 dmi.sys.vendor: Dell Inc. ** Affects: hwe-next Importance: Undecided Status: New ** Affects: linux-oem-osp1 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic oem-priority originate-from-1859932 somerville -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1864284 Title: r8152 init may take up to 40 seconds at initialization with Dell WD19/WD19DC during hotplug To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1864284/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1864284] Re: r8152 init may take up to 40 seconds at initialization with Dell WD19/WD19DC during hotplug
** Attachment added: "Lsusb-t.txt" https://bugs.launchpad.net/ubuntu/+source/linux-oem-osp1/+bug/1864284/+attachment/5330224/+files/Lsusb-t.txt ** Tags added: oem-priority originate-from-1859932 somerville -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1864284 Title: r8152 init may take up to 40 seconds at initialization with Dell WD19/WD19DC during hotplug To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1864284/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1864061] Re: PCI/internal sound card not detected
** Description changed: The sof-pci-dev and snd-soc-skl all contains the same pciid, if the soc-skl is loaded ahead of sof-pci-dev, the sof driver will not work anymore, in the oem project, we manually put the soc-skl in the blacklist. From kernel-5.4 (focal kernel), the driver soc-skl is disabled by default, and there is no users report any issues on it. So let us disable soc-skl in the eoan and osp1 kernel too. The patch for eoan kernel doesn't remove the modules because looks like the abi folder are not controlled by git. This will break the modulecheck, so if this patch could be merged, please help remove those modules: snd-soc-skl snd-soc-skl-ipc snd-soc-skl-ssp-clk [Impact] If soc-skl driver is loaded ahead of sof driver, the sof could not work anymore, we need to blacklist the soc-skl manually [Fix] Like the focal kernel, we disable the soc_skl driver in the kernel config [Test Case] Tested on Lenovo and Dell machines which has dmic, the sof driver could be loaded successfully. Tested on the machinces without the dmic, the legacy hda driver worked well as before. [Regression Risk] Low, Focal kernel and mainine-5.5, 5.6-rc kernel all disabled this dirver; and We have not met a machine need the soc_skl driver yet; and Intel claim that the sof could replace the soc_skl driver. + + + In the -41 kernel, we introduced a patch from stable kernel, that + make the sof driver crash, and there is a fix patch in the 5.6-rc1, + and this fix patch is already in the stable and is merged to focal + kernel, now we backport this patch to Eoan kernel if -42 doesn't + introduce this fix patch from stable. + + The patch introduced the crash: + commit 063821115e02229d5fd3de31bad270d5e30aeb41 + Author: Dragos Tarcatu + Date: Mon Dec 9 18:39:38 2019 -0600 + + ASoC: topology: Check return value for snd_soc_add_dai_link() + + BugLink: https://bugs.launchpad.net/bugs/1861929 + + [ Upstream commit 76d2703649321c296df7ec0dafd50add96215de4 ] + + snd_soc_add_dai_link() might fail. This situation occurs for + instance in a very specific use case where a PCM device and a + Back End DAI link are given identical names in the topology. + When this happens, soc_new_pcm_runtime() fails and then + snd_soc_add_dai_link() returns -ENOMEM when called from + soc_tplg_fe_link_create(). Because of that, the link will not + get added into the card list, so any attempt to remove it later + ends up in a panic. + + Fix that by checking the return status and free the memory in case + of an error. + + Reviewed-by: Ranjani Sridharan + Signed-off-by: Dragos Tarcatu + Signed-off-by: Pierre-Louis Bossart + Link: https://lore.kernel.org/r/20191210003939.15752-2-pierre-louis.boss...@linux.intel.com + Signed-off-by: Mark Brown + Signed-off-by: Sasha Levin + Signed-off-by: Kamal Mostafa + Signed-off-by: Khalid Elmously + + + [Impact] + During the boot, the sof driver crash because the hdmi_pcm_list + is not initialized before it is used. + + [Fix] + This bug is fixed in the mainline kernel v5.6-rc1, now backport + this patch to ubuntu kernel + + [Test Case] + Boot the -41 kernel with this patch added. + blacklist the snd_soc_skl + the kernel can boot successfully, and sof driver worked well + + [Regression Risk] + Low, the patches are backported from upstream kernel, and I tested + this patch on Lenovo and Dell dmic machines. Focal kernel already + has this patch and works well. + + Probably a kernel bug. The sound card isn't detected in 5.3.0-41-generic Booting 5.3.0-40-generic does work. The relevant dmesg message is: [9.845441] skl_hda_dsp_generic skl_hda_dsp_generic: Unsupported HDAudio/iDisp configuration found [9.845447] skl_hda_dsp_generic: probe of skl_hda_dsp_generic failed with error -22 ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.3.0-41.33-generic 5.3.18 Uname: Linux 5.3.0-41-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.4 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: ubuntu:GNOME Date: Thu Feb 20 16:46:21 2020 InstallationDate: Installed on 2019-10-07 (136 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Title: PCI/internal sound card not detected UpgradeStatus: Upgraded to eoan on 2019-11-19 (93 days ago) dmi.bios.date: 01/15/2020 dmi.bios.vendor: LENOVO dmi.bios.version: N2HET44W (1.27 ) dmi.board.asset.tag: Not Available dmi.board.name: 20QDCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO d
[Bug 1861109] Re: xenial/linux-cascade: 4.4.0-1014.16 -proposed tracker
** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1861122 packages: main: linux-cascade meta: linux-meta-cascade signed: linux-signed-cascade phase: Ready for Promote to Proposed phase-changed: Friday, 21. February 2020 21:16 UTC reason: - promote-to-proposed: Pending -- ready for review + promote-to-proposed: Stalled -- ready for review trackers: xenial/linux-cascade/cascade-kernel: bug 1861108 variant: debs -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1861109 Title: xenial/linux-cascade: 4.4.0-1014.16 -proposed tracker To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1861109/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1864286] Re: thunar crashed with SIGSEGV
*** This bug is a duplicate of bug 1758577 *** https://bugs.launchpad.net/bugs/1758577 Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1758577, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find. ** Attachment removed: "CoreDump.gz" https://bugs.launchpad.net/bugs/1864286/+attachment/5330231/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1864286/+attachment/5330233/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1864286/+attachment/5330236/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1864286/+attachment/5330237/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1864286/+attachment/5330238/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1864286/+attachment/5330239/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1864286/+attachment/5330240/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of private bug 1758577 ** Information type changed from Private to Public ** Tags removed: need-amd64-retrace -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1864286 Title: thunar crashed with SIGSEGV To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thunar/+bug/1864286/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1864061] Re: PCI/internal sound card not detected
Loading the old driver, also seems to fixed my problems with suspend and resume. Thanks for the information you've given so quickly. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1864061 Title: PCI/internal sound card not detected To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1864061/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1864061] Re: PCI/internal sound card not detected
> Please add "options snd-hda-intel dmic_detect=0" in the /etc/modprobe.d/alsa-base.conf, then the legacy hda driver will work as before. Can confirm. This works. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1864061 Title: PCI/internal sound card not detected To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1864061/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1864284] Re: r8152 init may take up to 40 seconds at initialization with Dell WD19/WD19DC during hotplug
** Also affects: linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1864284 Title: r8152 init may take up to 40 seconds at initialization with Dell WD19/WD19DC during hotplug To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1864284/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1864284] Status changed to Confirmed
This change was made by a bot. ** Changed in: linux (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1864284 Title: r8152 init may take up to 40 seconds at initialization with Dell WD19/WD19DC during hotplug To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1864284/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1864287] [NEW] pulseaudio still trying to reproduce audio to HDMI without the HDMI cable connected
Public bug reported: Yesterday I was using the HDMI cable to duplicate the monitor in the tv and play sound with the tv by selecting HDMI exit sound in ubuntu settings. With the pc turned off I removed the HDMI from the tv but ubuntu doesn't automatically set the exit sound to the default till in the settings there is only that option and till I selected it, ubuntu was still trying to reproduce the audio via HDMI... Also rebooting the system the problem persists. Also by reloading pulseaudio the problem persists. The only solution was installing a third-party program to switch correctly to the default audio exit... lsb_release -rd: Description:Ubuntu 18.04.3 LTS Release:18.04 apt-cache policy pulseaudio: pulseaudio: Installato: 1:11.1-1ubuntu7.2 Candidato: 1:11.1-1ubuntu7.4 Tabella versione: 1:11.1-1ubuntu7.4 500 500 http://it.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages *** 1:11.1-1ubuntu7.2 100 100 /var/lib/dpkg/status 1:11.1-1ubuntu7 500 500 http://it.archive.ubuntu.com/ubuntu bionic/main amd64 Packages ** Affects: pulseaudio (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1864287 Title: pulseaudio still trying to reproduce audio to HDMI without the HDMI cable connected To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1864287/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1862053] Re: Compiler gets stuck (or extremely slow) on ppc64el
reverted the work-around in ghostscript ** Changed in: ghostscript (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1862053 Title: Compiler gets stuck (or extremely slow) on ppc64el To manage notifications about this bug go to: https://bugs.launchpad.net/gcc/+bug/1862053/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1864288] [NEW] No boot after an update.
Public bug reported: After an update, my computer will no longer boot. I only see a black screen. No grub menu. After a couple of forced restarts, the file system gets corrupt. This happens both on XUbuntu 18.04.4 and 19.10. I am not sure if it had something to do with RAM upgrade or was it just a coincidence that I replaced a 4GB RAM module for an 8GB module and the next day my computer would not boot after an update. With clean install to any version everything works fine. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: ubuntu-release-upgrader-core 1:18.04.37 [origin: unknown] ProcVersionSignature: Ubuntu 5.3.0-28.30~18.04.1-generic 5.3.13 Uname: Linux 5.3.0-28-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 CrashDB: ubuntu CurrentDesktop: XFCE Date: Sat Feb 22 10:57:29 2020 InstallationDate: Installed on 2020-02-22 (0 days ago) InstallationMedia: Xubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 (20200203.1) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: dist-update UpgradeStatus: No upgrade log present (fresh install) as update crashes. ** Affects: ubuntu-release-upgrader (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic dist-upgrade third-party-packages ** Description changed: - After an update, my computer will no longer boot. I only see a black screen. No grub menu. After a couple of forced restarts, the file system gets corrupt. This happens both on XUbuntu 18.04.4 and 19.10. + After an update, my computer will no longer boot. I only see a black screen. No grub menu. After a couple of forced restarts, the file system gets corrupt. This happens both on XUbuntu 18.04.4 and 19.10. I am not sure if it had something to do with RAM upgrade or was it just a coincidence that I replaced a 4GB RAM module for an 8GB module and the next day my computer would not boot after an update. With clean install to any version everything works fine. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: ubuntu-release-upgrader-core 1:18.04.37 [origin: unknown] ProcVersionSignature: Ubuntu 5.3.0-28.30~18.04.1-generic 5.3.13 Uname: Linux 5.3.0-28-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 CrashDB: ubuntu CurrentDesktop: XFCE Date: Sat Feb 22 10:57:29 2020 InstallationDate: Installed on 2020-02-22 (0 days ago) InstallationMedia: Xubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 (20200203.1) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader - Symptom: dist-upgrade - UpgradeStatus: No upgrade log present (probably fresh install) + Symptom: dist-update + UpgradeStatus: No upgrade log present (fresh install) as update crashes. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1864288 Title: No boot after an update. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1864288/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1863116] Re: debian/rules editconfigs does not work on s390x to change s390x only configs
currently we don't build any cross compilers on s390x. Is this a scenario which is needed? We do that on ppc64el, given that you actually can buy even some workstations. and if needed, which targets should be supported? ** Changed in: ubuntu-z-systems Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1863116 Title: debian/rules editconfigs does not work on s390x to change s390x only configs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1863116/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1864288] Re: No boot after an update.
** Description changed: After an update, my computer will no longer boot. I only see a black screen. No grub menu. After a couple of forced restarts, the file system gets corrupt. This happens both on XUbuntu 18.04.4 and 19.10. - I am not sure if it had something to do with RAM upgrade or was it just a coincidence that I replaced a 4GB RAM module for an 8GB module and the next day my computer would not boot after an update. With clean install to any version everything works fine. + I am not sure if it had something to do with RAM upgrade or was it just a coincidence that I replaced a 4GB RAM module for an 8GB module and the next day my computer would not boot after an update. With clean install to any version everything works fine. It might be of some significance to know that my Assus VivoBook with Ryzen3 CPU has 4GB somewhere embedded and a separate 4GB module in the SODIMM slot, so it reports 8GB of RAM. After upgrading the RAM module to 8GB, it reports 12GB of RAM. I no longer had the patience to test if this would happen with the old 4GB module. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: ubuntu-release-upgrader-core 1:18.04.37 [origin: unknown] ProcVersionSignature: Ubuntu 5.3.0-28.30~18.04.1-generic 5.3.13 Uname: Linux 5.3.0-28-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 CrashDB: ubuntu CurrentDesktop: XFCE Date: Sat Feb 22 10:57:29 2020 InstallationDate: Installed on 2020-02-22 (0 days ago) InstallationMedia: Xubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 (20200203.1) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: dist-update UpgradeStatus: No upgrade log present (fresh install) as update crashes. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1864288 Title: No boot after an update. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1864288/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1752091] Re: gvfsd-metadata[1703]: g_udev_device_has_property: assertion 'G_UDEV_IS_DEVICE (device)' failed
In my case, the bug apparead when I mounted an encfs volume andf began to navigate on it Linux Mint 19.3 (based on Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1752091 Title: gvfsd-metadata[1703]: g_udev_device_has_property: assertion 'G_UDEV_IS_DEVICE (device)' failed To manage notifications about this bug go to: https://bugs.launchpad.net/gvfs/+bug/1752091/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1864178] Re: Rhythmbox crashes when trying to connect to iPhone
upstream bug https://gitlab.gnome.org/GNOME/rhythmbox/issues/1760 ** Bug watch added: gitlab.gnome.org/GNOME/rhythmbox/issues #1760 https://gitlab.gnome.org/GNOME/rhythmbox/issues/1760 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1864178 Title: Rhythmbox crashes when trying to connect to iPhone To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/1864178/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1485325] Re: Progress bar for do-release-upgrade
+1 A config option to print progress more often will be great indeed! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1485325 Title: Progress bar for do-release-upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/update-manager-core/+bug/1485325/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1864288] Re: No boot after an update.
Thank you for taking the time to report this issue and helping to make Ubuntu better. The ubuntu-release-upgrader package is used when you run `do-release- upgrade` and move from 18.04 to 18.10, or in the future from 18.04 to 20.04 (future because it won't work yet as is enabled after 20.04.1 is released). I see no evidence of either of those release-upgrades occurring, so the package could be changed to 'linux' >From your description, and with your machine I'd be looking at your hardware. Have you run a complete memtest on your system? ** Package changed: ubuntu-release-upgrader (Ubuntu) => linux (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1864288 Title: No boot after an update. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1864288/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1864288] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window: apport-collect 1864288 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1864288 Title: No boot after an update. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1864288/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1596381] Re: [X555UA, Realtek ALC256, Mic, Internal] No sound at all
I was able to solve the control volume thing but the root problem still there. If someone gets to this point I will show you my solution. I realized (in alsamixer) that I was able to change the speakers volume controlling PCM device instead of Master one. So I searched about that and found that you can make pulseaudio to control another device. All the information is in here: https://askubuntu.com/questions/15069/how- do-i-change-the-way-ubuntu-adjusts-my-volume-mixer-levels However, I think this should be fixed. Thank you for your help ^^ -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1596381 Title: [X555UA, Realtek ALC256, Mic, Internal] No sound at all To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1596381/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1864162] Re: Don't install snap programs.
The problem occurs as soon as the computer is started then with the basic software that uses focal fossa. I believe it can be easily replicated without adding further information. With the ISO of 24-01-2020 there are no particular problems. I found the problem with the versions from 16 / 20-02-2020 (approximately) and I also tried the one of 21-02-2020 which finds the same defect. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1864162 Title: Don't install snap programs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1864162/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1864288] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1864288/+attachment/5330246/+files/CRDA.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1864288 Title: No boot after an update. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1864288/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1864288] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1864288/+attachment/5330247/+files/CurrentDmesg.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1864288 Title: No boot after an update. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1864288/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1864288] IwConfig.txt
apport information ** Attachment added: "IwConfig.txt" https://bugs.launchpad.net/bugs/1864288/+attachment/5330248/+files/IwConfig.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1864288 Title: No boot after an update. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1864288/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1864288] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1864288/+attachment/5330255/+files/ProcModules.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1864288 Title: No boot after an update. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1864288/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1864288] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1864288/+attachment/5330249/+files/Lspci.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1864288 Title: No boot after an update. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1864288/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1864288] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1864288/+attachment/5330254/+files/ProcInterrupts.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1864288 Title: No boot after an update. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1864288/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1864288] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1864288/+attachment/5330251/+files/ProcCpuinfo.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1864288 Title: No boot after an update. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1864288/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1864288] AlsaInfo.txt
apport information ** Attachment added: "AlsaInfo.txt" https://bugs.launchpad.net/bugs/1864288/+attachment/5330260/+files/AlsaInfo.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1864288 Title: No boot after an update. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1864288/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1864288] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1864288/+attachment/5330252/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1864288 Title: No boot after an update. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1864288/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1864288] Re: No boot after an update.
apport information ** Tags added: apport-collected ** Description changed: After an update, my computer will no longer boot. I only see a black screen. No grub menu. After a couple of forced restarts, the file system gets corrupt. This happens both on XUbuntu 18.04.4 and 19.10. I am not sure if it had something to do with RAM upgrade or was it just a coincidence that I replaced a 4GB RAM module for an 8GB module and the next day my computer would not boot after an update. With clean install to any version everything works fine. It might be of some significance to know that my Assus VivoBook with Ryzen3 CPU has 4GB somewhere embedded and a separate 4GB module in the SODIMM slot, so it reports 8GB of RAM. After upgrading the RAM module to 8GB, it reports 12GB of RAM. I no longer had the patience to test if this would happen with the old 4GB module. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: ubuntu-release-upgrader-core 1:18.04.37 [origin: unknown] ProcVersionSignature: Ubuntu 5.3.0-28.30~18.04.1-generic 5.3.13 Uname: Linux 5.3.0-28-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 CrashDB: ubuntu CurrentDesktop: XFCE Date: Sat Feb 22 10:57:29 2020 InstallationDate: Installed on 2020-02-22 (0 days ago) InstallationMedia: Xubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 (20200203.1) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: dist-update UpgradeStatus: No upgrade log present (fresh install) as update crashes. + --- + ProblemType: Bug + ApportVersion: 2.20.9-0ubuntu7.9 + Architecture: amd64 + AudioDevicesInUse: + USERPID ACCESS COMMAND + /dev/snd/controlC1: rada 1170 F pulseaudio + /dev/snd/controlC0: rada 1170 F pulseaudio + CurrentDesktop: XFCE + DistroRelease: Ubuntu 18.04 + InstallationDate: Installed on 2020-02-22 (0 days ago) + InstallationMedia: Xubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 (20200203.1) + MachineType: ASUSTeK COMPUTER INC. VivoBook_ASUSLaptop X512DA_X512DA + Package: linux (not installed) + ProcFB: 0 amdgpudrmfb + ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-28-generic root=UUID=8beff811-d0c3-4481-97d4-7ca7073f066b ro quiet splash vt.handoff=1 + ProcVersionSignature: Ubuntu 5.3.0-28.30~18.04.1-generic 5.3.13 + RelatedPackageVersions: + linux-restricted-modules-5.3.0-28-generic N/A + linux-backports-modules-5.3.0-28-generic N/A + linux-firmware1.173.14 + Tags: bionic + Uname: Linux 5.3.0-28-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo + _MarkForUpload: True + dmi.bios.date: 03/08/2019 + dmi.bios.vendor: American Megatrends Inc. + dmi.bios.version: X512DA.302 + dmi.board.asset.tag: ATN12345678901234567 + dmi.board.name: X512DA + dmi.board.vendor: ASUSTeK COMPUTER INC. + dmi.board.version: 1.0 + dmi.chassis.asset.tag: No Asset Tag + dmi.chassis.type: 10 + dmi.chassis.vendor: ASUSTeK COMPUTER INC. + dmi.chassis.version: 1.0 + dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrX512DA.302:bd03/08/2019:svnASUSTeKCOMPUTERINC.:pnVivoBook_ASUSLaptopX512DA_X512DA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX512DA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: + dmi.product.family: VivoBook + dmi.product.name: VivoBook_ASUSLaptop X512DA_X512DA + dmi.product.version: 1.0 + dmi.sys.vendor: ASUSTeK COMPUTER INC. ** Attachment added: "AlsaInfo.txt" https://bugs.launchpad.net/bugs/1864288/+attachment/5330245/+files/AlsaInfo.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1864288 Title: No boot after an update. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1864288/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1864288] RfKill.txt
apport information ** Attachment added: "RfKill.txt" https://bugs.launchpad.net/bugs/1864288/+attachment/5330257/+files/RfKill.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1864288 Title: No boot after an update. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1864288/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1864288] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1864288/+attachment/5330259/+files/WifiSyslog.txt ** Description changed: After an update, my computer will no longer boot. I only see a black screen. No grub menu. After a couple of forced restarts, the file system gets corrupt. This happens both on XUbuntu 18.04.4 and 19.10. I am not sure if it had something to do with RAM upgrade or was it just a coincidence that I replaced a 4GB RAM module for an 8GB module and the next day my computer would not boot after an update. With clean install to any version everything works fine. It might be of some significance to know that my Assus VivoBook with Ryzen3 CPU has 4GB somewhere embedded and a separate 4GB module in the SODIMM slot, so it reports 8GB of RAM. After upgrading the RAM module to 8GB, it reports 12GB of RAM. I no longer had the patience to test if this would happen with the old 4GB module. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: ubuntu-release-upgrader-core 1:18.04.37 [origin: unknown] ProcVersionSignature: Ubuntu 5.3.0-28.30~18.04.1-generic 5.3.13 Uname: Linux 5.3.0-28-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 CrashDB: ubuntu CurrentDesktop: XFCE Date: Sat Feb 22 10:57:29 2020 InstallationDate: Installed on 2020-02-22 (0 days ago) InstallationMedia: Xubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 (20200203.1) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: dist-update UpgradeStatus: No upgrade log present (fresh install) as update crashes. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: rada 1170 F pulseaudio /dev/snd/controlC0: rada 1170 F pulseaudio CurrentDesktop: XFCE DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2020-02-22 (0 days ago) InstallationMedia: Xubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 (20200203.1) MachineType: ASUSTeK COMPUTER INC. VivoBook_ASUSLaptop X512DA_X512DA Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-28-generic root=UUID=8beff811-d0c3-4481-97d4-7ca7073f066b ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.3.0-28.30~18.04.1-generic 5.3.13 RelatedPackageVersions: linux-restricted-modules-5.3.0-28-generic N/A linux-backports-modules-5.3.0-28-generic N/A linux-firmware1.173.14 Tags: bionic Uname: Linux 5.3.0-28-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 03/08/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X512DA.302 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X512DA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrX512DA.302:bd03/08/2019:svnASUSTeKCOMPUTERINC.:pnVivoBook_ASUSLaptopX512DA_X512DA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX512DA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: VivoBook dmi.product.name: VivoBook_ASUSLaptop X512DA_X512DA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. + --- + ProblemType: Bug + ApportVersion: 2.20.9-0ubuntu7.9 + Architecture: amd64 + AudioDevicesInUse: + USERPID ACCESS COMMAND + /dev/snd/controlC1: rada 1170 F pulseaudio + /dev/snd/controlC0: rada 1170 F pulseaudio + CurrentDesktop: XFCE + DistroRelease: Ubuntu 18.04 + InstallationDate: Installed on 2020-02-22 (0 days ago) + InstallationMedia: Xubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 (20200203.1) + MachineType: ASUSTeK COMPUTER INC. VivoBook_ASUSLaptop X512DA_X512DA + Package: linux (not installed) + ProcFB: 0 amdgpudrmfb + ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-28-generic root=UUID=8beff811-d0c3-4481-97d4-7ca7073f066b ro quiet splash vt.handoff=1 + ProcVersionSignature: Ubuntu 5.3.0-28.30~18.04.1-generic 5.3.13 + RelatedPackageVersions: + linux-restricted-modules-5.3.0-28-generic N/A + linux-backports-modules-5.3.0-28-generic N/A + linux-firmware1.173.14 + Tags: bionic + Uname: Linux 5.3.0-28-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo + _MarkForUpload: True + dmi.bios.date: 03/08/2019 + dmi.bios.vendor: American Megatrends Inc. + dmi.bios.version: X512DA.302 + dmi.board.asset.tag: ATN12345678901234567 + dmi.board.name: X512DA + dmi.board.vendor: ASUSTeK COMPUTER INC. + dmi.board.version: 1.0 + dmi.chassis.asset.tag: No Asset Tag + dmi.chassis.type: 1
[Bug 1864288] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1864288/+attachment/5330258/+files/UdevDb.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1864288 Title: No boot after an update. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1864288/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1864288] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1864288/+attachment/5330253/+files/ProcEnviron.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1864288 Title: No boot after an update. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1864288/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1864288] IwConfig.txt
apport information ** Attachment added: "IwConfig.txt" https://bugs.launchpad.net/bugs/1864288/+attachment/5330263/+files/IwConfig.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1864288 Title: No boot after an update. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1864288/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1864288] PulseList.txt
apport information ** Attachment added: "PulseList.txt" https://bugs.launchpad.net/bugs/1864288/+attachment/5330256/+files/PulseList.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1864288 Title: No boot after an update. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1864288/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1864288] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1864288/+attachment/5330250/+files/Lsusb.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1864288 Title: No boot after an update. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1864288/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1864288] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1864288/+attachment/5330264/+files/Lspci.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1864288 Title: No boot after an update. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1864288/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1864288] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1864288/+attachment/5330268/+files/ProcEnviron.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1864288 Title: No boot after an update. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1864288/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1864288] PulseList.txt
apport information ** Attachment added: "PulseList.txt" https://bugs.launchpad.net/bugs/1864288/+attachment/5330271/+files/PulseList.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1864288 Title: No boot after an update. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1864288/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1864288] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1864288/+attachment/5330261/+files/CRDA.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1864288 Title: No boot after an update. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1864288/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1864288] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1864288/+attachment/5330267/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1864288 Title: No boot after an update. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1864288/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1864288] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1864288/+attachment/5330266/+files/ProcCpuinfo.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1864288 Title: No boot after an update. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1864288/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1864288] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1864288/+attachment/5330262/+files/CurrentDmesg.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1864288 Title: No boot after an update. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1864288/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1864288] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1864288/+attachment/5330265/+files/Lsusb.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1864288 Title: No boot after an update. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1864288/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1864288] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1864288/+attachment/5330274/+files/WifiSyslog.txt ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1864288 Title: No boot after an update. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1864288/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1864288] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1864288/+attachment/5330270/+files/ProcModules.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1864288 Title: No boot after an update. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1864288/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1864288] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1864288/+attachment/5330269/+files/ProcInterrupts.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1864288 Title: No boot after an update. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1864288/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1864288] RfKill.txt
apport information ** Attachment added: "RfKill.txt" https://bugs.launchpad.net/bugs/1864288/+attachment/5330272/+files/RfKill.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1864288 Title: No boot after an update. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1864288/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1864288] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1864288/+attachment/5330273/+files/UdevDb.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1864288 Title: No boot after an update. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1864288/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1864252] Re: preseeded snap installs fail in images
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: livecd-rootfs (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1864252 Title: preseeded snap installs fail in images To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/1864252/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1864162] Re: Don't install snap programs.
*** This bug is a duplicate of bug 1864252 *** https://bugs.launchpad.net/bugs/1864252 ** This bug has been marked a duplicate of bug 1864252 preseeded snap installs fail in images -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1864162 Title: Don't install snap programs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1864162/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1864290] Re: FTBFS on python2 removal
Upstream of mozc package doesn't prepare to support python3 yet. I attach patch which just use "/usr/bin/python2" instead of "/usr/bin/python" on build package. Could you sponsor it? ** Patch added: "workaround_python2_removal.debdiff" https://bugs.launchpad.net/ubuntu/+source/mozc/+bug/1864290/+attachment/5330275/+files/workaround_python2_removal.debdiff ** Changed in: mozc (Ubuntu) Status: New => In Progress -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1864290 Title: FTBFS on python2 removal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mozc/+bug/1864290/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1864290] [NEW] FTBFS on python2 removal
Public bug reported: mozc cannot build current focal because /usr/bin/python is removed. https://launchpad.net/ubuntu/+source/mozc/2.23.2815.102+dfsg-8build1 INFO: Running: ninja -v -C out_linux/Release ibus_mozc mozc_emacs_helper mozc_server mozc_renderer fcitx-mozc uim-mozc ninja: Entering directory `out_linux/Release' [1/629] cd ../../usage_stats; python ../build_tools/protoc_wrapper.py "--project_root=.." "--protoc_command=protoc" "--proto=usage_stats.proto" "--cpp_out=../out_linux/Release/gen/proto_out" FAILED: gen/proto_out/usage_stats/usage_stats.pb.h gen/proto_out/usage_stats/usage_stats.pb.cc cd ../../usage_stats; python ../build_tools/protoc_wrapper.py "--project_root=.." "--protoc_command=protoc" "--proto=usage_stats.proto" "--cpp_out=../out_linux/Release/gen/proto_out" /bin/sh: 1: python: not found ** Affects: mozc (Ubuntu) Importance: Undecided Status: In Progress -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1864290 Title: FTBFS on python2 removal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mozc/+bug/1864290/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1863825] Re: 20.04 apt update of python 3.8 gives errors
*** This bug is a duplicate of bug 1863414 *** https://bugs.launchpad.net/bugs/1863414 ** This bug has been marked a duplicate of bug 1863414 Have many "/usr/lib/python3.8/subprocess.py:838: RuntimeWarning: line buffering (buffering=1) isn't supported in binary mode, the default buffer size will be used" on simple APT usage -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1863825 Title: 20.04 apt update of python 3.8 gives errors To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python3-defaults/+bug/1863825/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1863831] Re: python3.8 upgrade 20.04 multiple warnings/errors
*** This bug is a duplicate of bug 1863414 *** https://bugs.launchpad.net/bugs/1863414 ** This bug has been marked a duplicate of bug 1863414 Have many "/usr/lib/python3.8/subprocess.py:838: RuntimeWarning: line buffering (buffering=1) isn't supported in binary mode, the default buffer size will be used" on simple APT usage -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1863831 Title: python3.8 upgrade 20.04 multiple warnings/errors To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1863831/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1864293] [NEW] Booting 5.4.0-14 drops to initramfs shell on machine with LVM and full disk encryption
Public bug reported: Ubuntu Mate 20.04 dev release, upgraded from 19.10. LVM/disk encrypion had been set up from the 19.10 installer and had been working perfectly. Today, when I try to boot, the splash screen stalls at the throbber and doesn't open a prompt for my encryption key. After a minute or so it drops to the initramfs shell. Rebooting without "silent splash" on the cmdline shows that `/dev/mapper/vgubuntu--mate-root` cannot be found, and running `ls /dev/mapper` outputs only `control`. Rebooting with the 5.4.0-12 kernel works without any problems. I've added `mitigations=off` to my default boot flags some time ago, if that's relevant? ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-14-generic 5.4.0-14.17 ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8 Uname: Linux 5.4.0-12-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu17 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: neil 3193 F pulseaudio CurrentDesktop: MATE Date: Sat Feb 22 12:29:27 2020 InstallationDate: Installed on 2019-10-11 (133 days ago) InstallationMedia: Ubuntu-MATE 19.10 "Eoan Ermine" - Beta amd64 (20190926.2) MachineType: LENOVO 2325A39 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-12-generic root=/dev/mapper/vgubuntu--mate-root ro quiet splash mitigations=off RelatedPackageVersions: linux-restricted-modules-5.4.0-12-generic N/A linux-backports-modules-5.4.0-12-generic N/A linux-firmware1.186 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux-5.4 UpgradeStatus: Upgraded to focal on 2020-02-07 (15 days ago) dmi.bios.date: 06/19/2018 dmi.bios.vendor: LENOVO dmi.bios.version: G2ETB3WW (2.73 ) dmi.board.asset.tag: Not Available dmi.board.name: 2325A39 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrG2ETB3WW(2.73):bd06/19/2018:svnLENOVO:pn2325A39:pvrThinkPadX230:rvnLENOVO:rn2325A39:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad X230 dmi.product.name: 2325A39 dmi.product.sku: LENOVO_MT_2325 dmi.product.version: ThinkPad X230 dmi.sys.vendor: LENOVO ** Affects: linux-5.4 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1864293 Title: Booting 5.4.0-14 drops to initramfs shell on machine with LVM and full disk encryption To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-5.4/+bug/1864293/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1864293] Re: Booting 5.4.0-14 drops to initramfs shell on machine with LVM and full disk encryption
** Summary changed: - Booting 5.4.0-14 drops to initramfs shell on machine with LVM and fudd disk encryption + Booting 5.4.0-14 drops to initramfs shell on machine with LVM and full disk encryption -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1864293 Title: Booting 5.4.0-14 drops to initramfs shell on machine with LVM and full disk encryption To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-5.4/+bug/1864293/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1862215] Re: Failure to boot with LVM + encrypted root disk
Oddly, I've just had this on 5.4.0-14, whereas 5.4.0-12 works perfectly. Maybe something is messed up in initramfs generation? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1862215 Title: Failure to boot with LVM + encrypted root disk To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-5.4/+bug/1862215/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1862215] Re: Failure to boot with LVM + encrypted root disk
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: linux-5.4 (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1862215 Title: Failure to boot with LVM + encrypted root disk To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-5.4/+bug/1862215/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1864293] Re: Booting 5.4.0-14 drops to initramfs shell on machine with LVM and full disk encryption
*** This bug is a duplicate of bug 1862215 *** https://bugs.launchpad.net/bugs/1862215 ** This bug has been marked a duplicate of bug 1862215 Failure to boot with LVM + encrypted root disk -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1864293 Title: Booting 5.4.0-14 drops to initramfs shell on machine with LVM and full disk encryption To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-5.4/+bug/1864293/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1863414] Re: Have many "/usr/lib/python3.8/subprocess.py:838: RuntimeWarning: line buffering (buffering=1) isn't supported in binary mode, the default buffer size will be used" on simple APT usag
** Also affects: python3-defaults (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1863414 Title: Have many "/usr/lib/python3.8/subprocess.py:838: RuntimeWarning: line buffering (buffering=1) isn't supported in binary mode, the default buffer size will be used" on simple APT usage To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python3-defaults/+bug/1863414/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1863414] Re: Have many "/usr/lib/python3.8/subprocess.py:838: RuntimeWarning: line buffering (buffering=1) isn't supported in binary mode, the default buffer size will be used" on simple APT usag
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: python3-defaults (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1863414 Title: Have many "/usr/lib/python3.8/subprocess.py:838: RuntimeWarning: line buffering (buffering=1) isn't supported in binary mode, the default buffer size will be used" on simple APT usage To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python3-defaults/+bug/1863414/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1833065] Re: Intel WiFi (CNVi) module has no function on Comet Lake [8086:02f0]
I'm seeing this problem on linux 5.3.0-40-generic but with a different error log: [ 98.743076] iwlwifi :00:14.3: TLV_FW_FSEQ_VERSION: FSEQ Version: 43.2.23.17 [ 98.743079] iwlwifi :00:14.3: Found debug destination: EXTERNAL_DRAM [ 98.743080] iwlwifi :00:14.3: Found debug configuration: 0 [ 98.743277] iwlwifi :00:14.3: loaded firmware version 48.13675109.0 op_mode iwlmvm [ 98.789706] iwlwifi :00:14.3: Detected Intel(R) Wireless-AC 9560, REV=0x354 [ 98.796641] iwlwifi :00:14.3: Applying debug destination EXTERNAL_DRAM [ 98.797136] iwlwifi :00:14.3: Allocated 0x0040 bytes for firmware monitor. [ 99.804515] iwlwifi :00:14.3: Collecting data: trigger 15 fired. [ 99.804588] iwlwifi :00:14.3: Start IWL Error Log Dump: [ 99.804590] iwlwifi :00:14.3: Status: 0x, count: -1954858323 [ 99.804591] iwlwifi :00:14.3: Loaded firmware version: 48.13675109.0 [ 99.804592] iwlwifi :00:14.3: 0x26D769CE | ADVANCED_SYSASSERT [ 99.804593] iwlwifi :00:14.3: 0x1AD012CA | trm_hw_status0 [ 99.804594] iwlwifi :00:14.3: 0xFC94AD42 | trm_hw_status1 [ 99.804595] iwlwifi :00:14.3: 0x67BA92B1 | branchlink2 [ 99.804595] iwlwifi :00:14.3: 0x22CDF757 | interruptlink1 [ 99.804596] iwlwifi :00:14.3: 0x461C6C04 | interruptlink2 [ 99.804597] iwlwifi :00:14.3: 0xA7A9DF46 | data1 [ 99.804598] iwlwifi :00:14.3: 0x9842E652 | data2 [ 99.804598] iwlwifi :00:14.3: 0x8A8131D1 | data3 [ 99.804599] iwlwifi :00:14.3: 0x02ED2D8A | beacon time [ 99.804600] iwlwifi :00:14.3: 0x94023DEC | tsf low [ 99.804600] iwlwifi :00:14.3: 0xDA3FE4C7 | tsf hi [ 99.804601] iwlwifi :00:14.3: 0x734269F5 | time gp1 [ 99.804602] iwlwifi :00:14.3: 0xC611C271 | time gp2 [ 99.804603] iwlwifi :00:14.3: 0x615B3F67 | uCode revision type [ 99.804603] iwlwifi :00:14.3: 0x4404C0DF | uCode version major [ 99.804604] iwlwifi :00:14.3: 0x528219F3 | uCode version minor [ 99.804605] iwlwifi :00:14.3: 0x35C57CDC | hw version [ 99.804605] iwlwifi :00:14.3: 0x2AC20D01 | board version [ 99.804606] iwlwifi :00:14.3: 0xDD85CB00 | hcmd [ 99.804607] iwlwifi :00:14.3: 0x5E16FD9E | isr0 [ 99.804608] iwlwifi :00:14.3: 0x3F3FFEEF | isr1 [ 99.804608] iwlwifi :00:14.3: 0x954E1E05 | isr2 [ 99.804609] iwlwifi :00:14.3: 0x0D660BC0 | isr3 [ 99.804610] iwlwifi :00:14.3: 0x398FFD8C | isr4 [ 99.804610] iwlwifi :00:14.3: 0xF3A3EC53 | last cmd Id [ 99.804611] iwlwifi :00:14.3: 0x046CA3B9 | wait_event [ 99.804612] iwlwifi :00:14.3: 0x1D70E4DB | l2p_control [ 99.804612] iwlwifi :00:14.3: 0x09D518A7 | l2p_duration [ 99.804613] iwlwifi :00:14.3: 0xD586D9C8 | l2p_mhvalid [ 99.804614] iwlwifi :00:14.3: 0x20AA0718 | l2p_addr_match [ 99.804615] iwlwifi :00:14.3: 0xCEA91061 | lmpm_pmg_sel [ 99.804615] iwlwifi :00:14.3: 0x2B584FE3 | timestamp [ 99.804616] iwlwifi :00:14.3: 0xDCEFA7E5 | flow_handler [ 99.804648] iwlwifi :00:14.3: Start IWL Error Log Dump: [ 99.804649] iwlwifi :00:14.3: Status: 0x, count: 7 [ 99.804649] iwlwifi :00:14.3: 0x201013F1 | ADVANCED_SYSASSERT [ 99.804650] iwlwifi :00:14.3: 0x | umac branchlink1 [ 99.804651] iwlwifi :00:14.3: 0xC008CF5C | umac branchlink2 [ 99.804652] iwlwifi :00:14.3: 0x | umac interruptlink1 [ 99.804652] iwlwifi :00:14.3: 0x | umac interruptlink2 [ 99.804653] iwlwifi :00:14.3: 0x0003 | umac data1 [ 99.804654] iwlwifi :00:14.3: 0x2302 | umac data2 [ 99.804654] iwlwifi :00:14.3: 0x01300202 | umac data3 [ 99.804655] iwlwifi :00:14.3: 0x0030 | umac major [ 99.804656] iwlwifi :00:14.3: 0x13675109 | umac minor [ 99.804657] iwlwifi :00:14.3: 0x5C8A | frame pointer [ 99.804657] iwlwifi :00:14.3: 0xC0887F58 | stack pointer [ 99.804658] iwlwifi :00:14.3: 0x | last host cmd [ 99.804659] iwlwifi :00:14.3: 0x | isr status reg [ 99.804672] iwlwifi :00:14.3: Fseq Registers: [ 99.804674] iwlwifi :00:14.3: 0x0003 | FSEQ_ERROR_CODE [ 99.804676] iwlwifi :00:14.3: 0x8026 | FSEQ_TOP_INIT_VERSION [ 99.804678] iwlwifi :00:14.3: 0x80020006 | FSEQ_CNVIO_INIT_VERSION [ 99.804681] iwlwifi :00:14.3: 0xA384 | FSEQ_OTP_VERSION [ 99.804683] iwlwifi :00:14.3: 0xFD00C708 | FSEQ_TOP_CONTENT_VERSION [ 99.804685] iwlwifi :00:14.3: 0x4552414E | FSEQ_ALIVE_TOKEN [ 99.804687] iwlwifi :00:14.3: 0x2302 | FSEQ_CNVI_ID [ 99.804690] iwlwifi :00:14.3: 0x01300202 | FSEQ_CNVR_ID [ 99.804692] iwlwifi :00:14.3: 0x2302 | CNVI_AUX_MISC_CHIP [ 99.804696] iwlwifi :00:14.3: 0x01300202 | CNVR_AUX_MISC_CHIP [ 99.804701] iwlwifi :00:14.3: 0x485B | CNVR_SCU_SD_REGS_SD_REG_DIG_DCDC_VTRIM [ 99.804735] iwlwifi :00:14.3: 0xA5A5A5A2 | CNVR_SCU_SD_REGS_SD_REG_ACTIVE_VDIG_MIRROR [ 99.804763] iw
[Bug 1188569] Re: [SRU]Some keyboard shortcuts randomly stop working
Hello together, I am running Ubuntu 18.04 with the Unity DE. In my case only the keyboard shortcut for changing the input-language is affected. Changing input-method to "none" solves the problem only until waking from the next suspend. The keyboard shortcut stops working after that. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1188569 Title: [SRU]Some keyboard shortcuts randomly stop working To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1188569/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1864298] [NEW] Modsecurity apache warning: ModSecurity: APR compiled version="1.6.2"; loaded version="1.6.3"
Public bug reported: Based on the question https://answers.launchpad.net/ubuntu/+source/modsecurity-apache/+question/685839 reported by user https://launchpad.net/~zhobbes: == Recently started seeing the following message appear in modsecurity logs when Apache2 restarted: ModSecurity for Apache/2.9.2 (http://www.modsecurity.org/) configured. ModSecurity: APR compiled version="1.6.2"; loaded version="1.6.3" ModSecurity: Loaded APR do not match with compiled! config: 18.04LTS with repo-installed apache2 (2.4.29) and libapache2 -mod-security2. Updates via auto/livepatch. Does libapache2-mod-security2 in bionic repo need to be re-compiled? = ** Affects: modsecurity-apache (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1864298 Title: Modsecurity apache warning: ModSecurity: APR compiled version="1.6.2"; loaded version="1.6.3" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/modsecurity-apache/+bug/1864298/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1863273] Re: bionic/linux-azure-5.3: 5.3.0-1014.15~18.04.1 -proposed tracker
** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1863274 packages: lrm: linux-restricted-modules-azure-5.3 main: linux-azure-5.3 meta: linux-meta-azure-5.3 signed: linux-signed-azure-5.3 phase: Testing phase-changed: Thursday, 20. February 2020 14:57 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Ongoing -- testing in progress regression-testing: Ongoing -- testing in progress - security-signoff: Pending -- waiting for signoff + security-signoff: Stalled -- waiting for signoff stakeholder-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress variant: debs -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1863273 Title: bionic/linux-azure-5.3: 5.3.0-1014.15~18.04.1 -proposed tracker To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1863273/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1863996] Re: bionic/linux-oem-osp1: 5.0.0-1040.45 -proposed tracker
** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1861192 packages: lrm: linux-restricted-modules-oem-osp1 main: linux-oem-osp1 meta: linux-meta-oem-osp1 signed: linux-signed-oem-osp1 phase: Signoff phase-changed: Friday, 21. February 2020 23:05 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: promote-to-updates: Holding -- security signoff not verified - security-signoff: Pending -- waiting for signoff + security-signoff: Stalled -- waiting for signoff variant: debs -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1863996 Title: bionic/linux-oem-osp1: 5.0.0-1040.45 -proposed tracker To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1863996/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1864299] [NEW] "Report a bug" link doesn't do what you think it does
Public bug reported: I want to report a bug, so. 1. I search for "ubuntu bug tracker" and find https://bugs.launchpad.net/ubuntu 2. I log in to https://bugs.launchpad.net/ubuntu 3. I look for a "file new bug report" button. I find the "Report a bug" text. 4. Instead of being taken to a page where I can just report a bug and get on with my work, I get taken to a page the length of a short novel filled with information I mostly already know and won't read as I've been a developer and a bug reporter for 15 years and wrote my own guides on reporting bugs effectively. I wasn't looking for documentation on how to report bugs, I was trying to report a bug. Solution: Add clear, easy to find "report a bug" button on bug tracker's main page which actually lets someone report a bug. Add another button for documentation on how to report bugs. ** Affects: launchpad Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1864299 Title: "Report a bug" link doesn't do what you think it does To manage notifications about this bug go to: https://bugs.launchpad.net/launchpad/+bug/1864299/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1864301] [NEW] Resizing LibreOffice style window causes Gnome-Shell to freeze for 10 seconds
Public bug reported: When I open LibreOffce Writer and decides to resize the Style window on the right of the screen (press F11 to toggle this window), Gnome-Shell completely freezes for a few seconds. I already rebooted and it's 100% reproducible. I initially reported this bug on Gnome-Shell Gitlab: https://gitlab.gnome.org/GNOME/gnome-shell/issues/2225#note_715411 You can find more info there (journalctl logs) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1864301 Title: Resizing LibreOffice style window causes Gnome-Shell to freeze for 10 seconds To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1864301/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1864301] Re: Resizing LibreOffice style window causes Gnome-Shell to freeze for 10 seconds
System info: Ubuntu 19.10 gnome-shell: 3.34.1+git20191024-1ubuntu1~19.10.1 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1864301 Title: Resizing LibreOffice style window causes Gnome-Shell to freeze for 10 seconds To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1864301/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1864299] Re: "Report a bug" link doesn't do what you think it does
** Package changed: ubuntu => launchpad -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1864299 Title: "Report a bug" link doesn't do what you think it does To manage notifications about this bug go to: https://bugs.launchpad.net/launchpad/+bug/1864299/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1864300] [NEW] Bump RawTherapee to 5.8
Public bug reported: Please bump RawTherapee to version 5.8, released on 2020-02-04. http://rawtherapee.com/downloads/5.8/ See "News Relevant to Package Maintainers" in the link above. ** Affects: rawtherapee (Ubuntu) Importance: Undecided Status: New ** Tags: upgrade-software-version ** Description changed: - This can probably be closed, as RawTherapee-3.0.0 is from 2011 and - RawTherapee is currently on version 5.8. + Please bump RawTherapee to version 5.8, released on 2020-02-04. + http://rawtherapee.com/downloads/5.8/ + See "News Relevant to Package Maintainers" in the link above. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1864300 Title: Bump RawTherapee to 5.8 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rawtherapee/+bug/1864300/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1864300] Re: Bump RawTherapee to 5.8
** Package changed: ubuntu => rawtherapee (Ubuntu) ** Tags added: upgrade-software-version -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1864300 Title: Bump RawTherapee to 5.8 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rawtherapee/+bug/1864300/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1864298] Re: Modsecurity apache warning: ModSecurity: APR compiled version="1.6.2"; loaded version="1.6.3"
** Tags added: bionic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1864298 Title: Modsecurity apache warning: ModSecurity: APR compiled version="1.6.2"; loaded version="1.6.3" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/modsecurity-apache/+bug/1864298/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1859545] Re: Sticky keys repeat indefinitely unless if pressed again
Good news! Using QEMU version 4.2.0 (Debian 1:4.2-3ubuntu1), I'm no longer able to reproduce this bug, key repeat is working properly. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1859545 Title: Sticky keys repeat indefinitely unless if pressed again To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1859545/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1851188] Re: Failed to create a partition table - install failed
This bug was fixed in the package calamares - 3.2.19-0ubuntu1 --- calamares (3.2.19-0ubuntu1) focal; urgency=medium * New upstream release. * Improved partition handling with kpmcore (LP: #1851188) -- Dan Simmons Sat, 22 Feb 2020 08:16:53 -0500 ** Changed in: calamares (Ubuntu) Status: Triaged => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1851188 Title: Failed to create a partition table - install failed To manage notifications about this bug go to: https://bugs.launchpad.net/calamares/+bug/1851188/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1864300] Re: Bump RawTherapee to 5.8
** Bug watch added: Debian Bug tracker #951841 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=951841 ** Also affects: rawtherapee (Debian) via https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=951841 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1864300 Title: Bump RawTherapee to 5.8 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rawtherapee/+bug/1864300/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1851188] Re: Failed to create a partition table - install failed
I want to add upstream calls this presumed fixed. I still have my doubts. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1851188 Title: Failed to create a partition table - install failed To manage notifications about this bug go to: https://bugs.launchpad.net/calamares/+bug/1851188/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1848064] Re: /usr/share/apport/whoopsie-upload-all:PermissionError:/usr/share/apport/whoopsie-upload-all@168:collect_info:process_report
** Branch linked: lp:~ubuntu-core-dev/ubuntu/focal/apport/ubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1848064 Title: /usr/share/apport/whoopsie-upload- all:PermissionError:/usr/share/apport/whoopsie-upload- all@168:collect_info:process_report To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1848064/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1833435] Re: RFC: Add url/urls/mirrors attribute for product items
Can anyone take a look at this, please? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1833435 Title: RFC: Add url/urls/mirrors attribute for product items To manage notifications about this bug go to: https://bugs.launchpad.net/simplestreams/+bug/1833435/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1863310] Re: bionic/linux-snapdragon: 4.15.0-1073.80 -proposed tracker
** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1863350 packages: main: linux-snapdragon meta: linux-meta-snapdragon phase: Testing phase-changed: Thursday, 20. February 2020 15:46 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Ongoing -- testing in progress certification-testing: Ongoing -- testing in progress - security-signoff: Pending -- waiting for signoff + security-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: bionic/linux-snapdragon/dragonboard-kernel: bug 1863308 variant: debs -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1863310 Title: bionic/linux-snapdragon: 4.15.0-1073.80 -proposed tracker To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1863310/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1864303] [NEW] Removing the e1000e module causes a crash
Public bug reported: I have a Lenovo x1 Carbon Gen5 and when it initially came out if you left the onboard NIC (e1000e) module loaded it would suck CPU/battery life so I have it removed in rc.local on boot. In 5.4 (also happens on 5.4.0.15.18 which I'm running from proposed right now), this is what happens when the module is unloaded: [ 608.979789] e1000e :00:1f.6 enp0s31f6: removed PHC [ 609.008352] [ cut here ] [ 609.008353] kernel BUG at drivers/pci/msi.c:375! [ 609.008358] invalid opcode: [#1] SMP PTI [ 609.008359] CPU: 0 PID: 6829 Comm: rmmod Tainted: P O 5.4.0-15-generic #18-Ubuntu [ 609.008360] Hardware name: LENOVO 20HRCTO1WW/20HRCTO1WW, BIOS N1MET59W (1.44 ) 11/25/2019 [ 609.008364] RIP: 0010:free_msi_irqs+0x17d/0x1b0 [ 609.008365] Code: 84 df fe ff ff 45 31 f6 eb 11 41 83 c6 01 44 39 73 14 0f 86 cc fe ff ff 8b 7b 10 44 01 f7 e8 ea c3 b6 ff 48 83 78 70 00 74 e0 <0f> 0b 49 8d b5 b0 00 00 00 e8 b5 7d b7 ff e9 cd fe ff ff 49 8b 78 [ 609.008366] RSP: 0018:a7d2072f7d40 EFLAGS: 00010286 [ 609.008367] RAX: 8bc9bfb49e00 RBX: 8bc9ad69c720 RCX: [ 609.008368] RDX: RSI: 0084 RDI: a9e65980 [ 609.008369] RBP: a7d2072f7d70 R08: 8bc9bb564db0 R09: 8bc9bb564df8 [ 609.008369] R10: R11: a9e65988 R12: 8bc9cb5272c0 [ 609.008370] R13: 8bc9cb527000 R14: R15: dead0100 [ 609.008371] FS: 7f188f1f9500() GS:8bc9ce20() knlGS: [ 609.008372] CS: 0010 DS: ES: CR0: 80050033 [ 609.008373] CR2: 7f6d1a6af060 CR3: 00046d9f8006 CR4: 003606f0 [ 609.008373] Call Trace: [ 609.008376] pci_disable_msi+0x100/0x130 [ 609.008385] e1000e_reset_interrupt_capability+0x52/0x60 [e1000e] [ 609.008389] e1000_remove+0xc4/0x180 [e1000e] [ 609.008391] pci_device_remove+0x3e/0xb0 [ 609.008394] device_release_driver_internal+0xf0/0x1d0 [ 609.008396] driver_detach+0x4c/0x8f [ 609.008397] bus_remove_driver+0x5c/0xd0 [ 609.008399] driver_unregister+0x31/0x50 [ 609.008400] pci_unregister_driver+0x40/0x90 [ 609.008405] e1000_exit_module+0x10/0x3c1 [e1000e] [ 609.008407] __x64_sys_delete_module+0x147/0x2b0 [ 609.008409] ? exit_to_usermode_loop+0xea/0x160 [ 609.008411] do_syscall_64+0x57/0x190 [ 609.008413] entry_SYSCALL_64_after_hwframe+0x44/0xa9 [ 609.008414] RIP: 0033:0x7f188f345c9b [ 609.008416] Code: 73 01 c3 48 8b 0d f5 71 0c 00 f7 d8 64 89 01 48 83 c8 ff c3 66 2e 0f 1f 84 00 00 00 00 00 90 f3 0f 1e fa b8 b0 00 00 00 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d c5 71 0c 00 f7 d8 64 89 01 48 [ 609.008416] RSP: 002b:7fffc8d32e68 EFLAGS: 0206 ORIG_RAX: 00b0 [ 609.008418] RAX: ffda RBX: 561e1a391790 RCX: 7f188f345c9b [ 609.008419] RDX: 000a RSI: 0800 RDI: 561e1a3917f8 [ 609.008420] RBP: 7fffc8d32ec8 R08: R09: [ 609.008420] R10: 7f188f3c1ac0 R11: 0206 R12: 7fffc8d33090 [ 609.008422] R13: 7fffc8d3474a R14: 561e1a3912a0 R15: 561e1a391790 [ 609.008424] Modules linked in: thunderbolt rfcomm xfrm_user xfrm_algo l2tp_ppp l2tp_netlink l2tp_core ip6_udp_tunnel udp_tunnel pppox ccm xt_comment xt_CHECKSUM xt_MASQUERADE ip6table_mangle ip6table_nat dummy iptable_mangle iptable_nat nf_tables nfnetlink bridge stp llc cmac algif_hash algif_skcipher af_alg bnep zfs(PO) zunicode(PO) zavl(PO) icp(PO) zcommon(PO) znvpair(PO) spl(O) zlua(PO) joydev intel_rapl_msr mei_hdcp nls_iso8859_1 snd_seq_midi snd_seq_midi_event snd_hda_codec_hdmi snd_hda_codec_conexant snd_hda_codec_generic intel_rapl_common x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel snd_hda_intel snd_rawmidi kvm snd_intel_nhlt snd_hda_codec intel_cstate rmi_smbus intel_rapl_perf snd_hda_core snd_hwdep iwlmvm rmi_core mac80211 uvcvideo input_leds videobuf2_vmalloc videobuf2_memops btusb btrtl snd_pcm libarc4 serio_raw snd_seq btbcm intel_wmi_thunderbolt videobuf2_v4l2 btintel videobuf2_common wmi_bmof thinkpad_acpi bluetooth videodev nvram snd_seq_device ledtrig_audio [ 609.008447] iwlwifi mc snd_timer rtsx_pci_ms ecdh_generic ecc cfg80211 memstick snd mei_me ucsi_acpi typec_ucsi intel_xhci_usb_role_switch mei roles intel_pch_thermal typec soundcore acpi_pad mac_hid nf_log_ipv6 ip6t_REJECT nf_reject_ipv6 xt_hl ip6t_rt nf_log_ipv4 nf_log_common ipt_REJECT nf_reject_ipv4 xt_LOG xt_limit xt_addrtype xt_tcpudp xt_conntrack ip6table_filter ip6_tables nf_conntrack_netbios_ns nf_conntrack_broadcast nf_nat_ftp sch_fq_codel nf_nat nf_conntrack_ftp nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 parport_pc iptable_filter bpfilter ppdev lp parport ip_tables x_tables autofs4 btrfs xor zstd_compress raid6_pq libcrc32c dm_crypt crct10dif_pclmul crc32_pclmul ghash_clmulni_intel i915 rtsx_pci_sdmmc i2c_algo_bit drm_kms_helper syscopyarea sysfillrect sysimg
[Bug 1864303] Re: Removing the e1000e module causes a crash
** Changed in: linux-5.4 (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1864303 Title: Removing the e1000e module causes a crash To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-5.4/+bug/1864303/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1863311] Re: xenial/linux-aws: 4.4.0-1103.114 -proposed tracker
** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1863338 packages: main: linux-aws meta: linux-meta-aws phase: Testing phase-changed: Thursday, 20. February 2020 16:32 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Ongoing -- testing in progress regression-testing: Ongoing -- testing in progress - security-signoff: Pending -- waiting for signoff + security-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: xenial/linux-aws/aws-kernel: bug 1863309 variant: debs -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1863311 Title: xenial/linux-aws: 4.4.0-1103.114 -proposed tracker To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1863311/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1864300] Re: Bump RawTherapee to 5.8
** Changed in: rawtherapee (Debian) Status: Unknown => New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1864300 Title: Bump RawTherapee to 5.8 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rawtherapee/+bug/1864300/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
