Please attach `journalctl -b -1 -k` from the next boot of system hang.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1848980
Title:
system hangs on suspend
To manage notifications about this bug
** Changed in: kernel-sru-workflow/prepare-package
Status: In Progress => Fix Committed
** Changed in: kernel-sru-workflow/prepare-package
Status: Fix Committed => Fix Released
** Changed in: kernel-sru-workflow/prepare-package-meta
Status: In Progress => Fix Committed
**
Please test latest mainline kernel:
https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.4-rc4/
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1849136
Title:
errors at boot and long boot time
To
Hi Rafael,
thanks for giving it try. We knew it might be complex when we first saw the
changes.
And I consider it wise to - at some point - step back and realize this won't be
SRUable.
I'll summarize what we know about the libvirt portion of this:
## SRUability ##
The changes are rather
Hi @pieq, following your message I launched download of Ubuntu 19.10 image.
I will test with live session as suggested (as I keep my laptop on LTS for the
moment)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Please test latest mainline kernel:
https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.4-rc4/
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1848883
Title:
(Lenovo S130-11IGM) emmc not working in
** 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 --
** Summary changed:
- bionic/linux-raspi2: -proposed tracker
+ bionic/linux-raspi2: 4.15.0-1050.54 -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package
Status: Confirmed => In Progress
** Changed in: kernel-sru-workflow/prepare-package
Assignee: Canonical Kernel
*** This bug is a duplicate of bug 1848790 ***
https://bugs.launchpad.net/bugs/1848790
I built a testing kernel, not only includes the fix for USB host, but
also includes all new patches from
https://github.com/raspberrypi/linux.git rpi-5.3.y branch (about 107
patches).
I tested both arm64
I built a testing kernel, not only includes the fix for USB host, but
also includes all new patches from
https://github.com/raspberrypi/linux.git rpi-5.3.y branch (about 107
patches).
I tested both arm64 and armhf kernels on Pi4 without HDMI monitor,
everything works well.
Could anybody help
** Changed in: kernel-sru-workflow/prepare-package
Status: In Progress => Fix Committed
** Changed in: kernel-sru-workflow/prepare-package
Status: Fix Committed => Fix Released
** Description changed:
This bug will contain status and test results related to a kernel source
(or
** Changed in: kernel-sru-workflow/promote-to-proposed
Status: New => Confirmed
** Tags added: block-proposed-xenial
** Tags added: block-proposed
** Description changed:
This bug will contain status and test results related to a kernel source
(or snap) as stated in the title.
** Changed in: kernel-sru-workflow/promote-to-proposed
Status: New => Confirmed
** Tags added: block-proposed-bionic
** Tags added: block-proposed
** Description changed:
This bug will contain status and test results related to a kernel source
(or snap) as stated in the title.
** Description changed:
[Impact]
* Users have reported the inability to use soundfonts with Carla hosted
synthesizer plugins
* Backporting this to the stable release would fix the problem.
* The upload simply adds libsndfile1-dev as a build dependency.
[Test Case]
Public bug reported:
I tried to change my monospace font to "Noto Sans Mono Bold" in
/etc/fonts/local.conf but that didn't have an effect so I did a little digging.
First I ran
$ sudo fc-cache -f -v && sudo dpkg-reconfigure fontconfig fontconfig-config
Which succeeded, then:
$ fc-list
Confirmed still not working with 19.10 (linux 5.3.0-18-generic) on the
Precision 7530. It's actually even worse: now, I can't even boot. I'm
just shown a black screen.
If I select the Safe graphics boot option, I can boot properly.
Editing the default boot command line to include
** Changed in: kernel-sru-workflow/prepare-package-meta
Status: In Progress => Fix Committed
** Changed in: kernel-sru-workflow/prepare-package-meta
Status: Fix Committed => Fix Released
** Description changed:
This bug will contain status and test results related to a kernel
I ran into this issue (FATAL: password authentication failed for user
"maas") by running the command 'maas-region createadmin --username admin
--password kNab4Q9fSa --email admin@localhost.localdimain' today as
well. I solved the problem in the following way.
1, confirm database_pass is
** Also affects: ubuntu-power-systems
Importance: Undecided
Status: New
** Changed in: ubuntu-power-systems
Assignee: (unassigned) => MAAS (maas)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I have the same issue if I try apt instead of apt-get.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1849253
Title:
apt-get install fails when UNRELATED package list is invalid
To manage
$ apt-cache policy apt
E: Encountered a section with no Package: header
E: Problem with MergeList
/var/lib/apt/lists/adoptopenjdk.jfrog.io_adoptopenjdk_deb_dists_disco_main_binary-amd64_Packages
E: The package lists or status file could not be parsed or opened.
--
You received this bug
Public bug reported:
1) Description: Ubuntu 19.04
Release:19.04
2) unknown (see below)
3) Even when a package list from one source is invalid, I can still apt-get
install and apt-get update packages from other sources, as long as they don't
depend on packages in the bad list.
4) I can't
#1848974 may be a duplicate of this bug.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1849253
Title:
apt-get install fails when UNRELATED package list is invalid
To manage notifications about
[Expired for subdownloader (Ubuntu) because there has been no activity
for 60 days.]
** Changed in: subdownloader (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
[Expired for linux (Ubuntu) because there has been no activity for 60
days.]
** Changed in: linux (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1840514
[Expired for linux (Ubuntu) because there has been no activity for 60
days.]
** Changed in: linux (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1840962
[Expired for vsftpd (Ubuntu) because there has been no activity for 60
days.]
** Changed in: vsftpd (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1840963
** Changed in: kernel-sru-workflow/promote-to-security
Status: New => Confirmed
** 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:
Also keep in mind that the duration of the flicker here depends on the
model of monitor in use.
Some laptops/monitors might be super-fast and not black-out when the
programmed mode changes. But in my experience most will. Sometimes
quickly and sometimes slowly.
--
You received this bug
[Expired for gnome-shell (Ubuntu) because there has been no activity for
60 days.]
** Changed in: gnome-shell (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Changed in: kernel-sru-workflow/promote-to-security
Status: New => Confirmed
** 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:
** 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 --
packages:
No that kernel did not fix the bug :(
** Summary changed:
- CONFIG_FRAMEBUFFER_CONSOLE_DEFERRED_TAKEOVER needed for flickerfree boot
+ i915: Display flickers during "flickerfree" boot (BIOS logo on a black
background)
--
You received this bug notification because you are a member of Ubuntu
$ uname -a
Linux kab 5.3.0-19-generic #20~lp1836858 SMP Fri Oct 18 12:09:47 UTC 2019
x86_64 x86_64 x86_64 GNU/Linux
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1836858
Title:
i915: Display
This has been automatically included in eoan 5.3.0-10.
** Changed in: linux-oem-osp1 (Ubuntu Eoan)
Status: New => Fix Released
** Changed in: linux-oem-osp1 (Ubuntu Eoan)
Status: Fix Released => Fix Committed
--
You received this bug notification because you are a member of
** Changed in: kernel-sru-workflow/promote-to-security
Status: New => Confirmed
** 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:
** Changed in: kernel-sru-workflow/promote-to-security
Status: New => Confirmed
** 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:
** Changed in: kernel-sru-workflow/promote-to-security
Status: New => Confirmed
** 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:
** Changed in: kernel-sru-workflow/promote-to-security
Status: New => Confirmed
** 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:
I've pushed a new version to the same PPA based on 5.3.0-19. Please have
an update and give it a try.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1847921
Title:
"iwlwifi :04:00.0: Microcode
This bug was fixed in the package klibc - 2.0.6-1ubuntu2
---
klibc (2.0.6-1ubuntu2) eoan; urgency=medium
* Fix FTBFS on eoan and later with new linux and gcc (LP: #1843743)
- cf-protection.patch: Disable cf-protection for syscalls stub.
- mman-include.patch: Adjust for
** Also affects: nvidia-graphics-drivers (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/1849214
Title:
"nvidia on-demand" mode does not support
Sorry to drag up a very old bug like this - but this still seems to be
an issue in new ubuntu/debian based distributions. I ran into this issue
when using llvm-strip and it doesn't preserve .ARM.attributes - I have
written a patch against llvm-strip that's being discussed here:
Dropped the bionic task until such time as this becomes a reproducible
and testable bug there.
** No longer affects: mutter (Ubuntu Bionic)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1809407
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: glibc (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/1712938
Title:
I am having the same problem with 19.04 and an Apple Magic Pad.
I have read in the links below that a solution would be to disable the config
HID_BATTERY_STRENGTH. It says: "Rebuild the kernel with
CONFIG_HID_BATTERY_STRENGTH=N and the issue disappears,
along with battery status reporting", but
** Changed in: nginx (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/1743592
Title:
NGINX fails to start/install/upgrade if IPv6 is completely disabled.
To
*** This bug is a duplicate of bug 1849249 ***
https://bugs.launchpad.net/bugs/1849249
** This bug has been marked a duplicate of bug 1849249
gnome-shell crashed with SIGABRT:
mutter:ERROR:../src/core/window.c:4841:set_workspace_state: assertion failed:
(workspace == NULL)
--
You
** Changed in: linux-bluefield (Ubuntu)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1848324
Title:
Integrate Fixes from Mellanox 2019-10-16
To manage
*** This bug is a duplicate of bug 1849249 ***
https://bugs.launchpad.net/bugs/1849249
Public bug reported:
The Ubuntu Error Tracker has been receiving reports about a problem regarding
gnome-shell. This problem was most recently seen with package version
3.34.1-1ubuntu1, the problem page
Thanks for the bug report. Tracking in:
https://errors.ubuntu.com/problem/8317377ffa8b8148baa481d490fd876111eb3c4b
** Summary changed:
- gnome-shell crashed with SIGABRT
+ gnome-shell crashed with SIGABRT:
mutter:ERROR:../src/core/window.c:4841:set_workspace_state: assertion failed:
(workspace
** 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 --
packages:
** Changed in: linux (Ubuntu)
Status: In Progress => Incomplete
** Changed in: ubuntu-power-systems
Status: In Progress => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** 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 --
packages:
Downgraded to 2.02 and everything works again.
Major difference in debug output on 2.02 is the line which says:
2.02:
shim bla bla not available
shim_lock bla bla
linuxefi_secure_validate: 0
2.04:
SecureBoot: 0
SetupMode: 1
secure boot not enabled, not validating bla bla
This issue has been fix in linux-oem 4.15.0-1059.68
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1847063
Title:
Fix non-working Realtek USB ethernet after system resume
To manage notifications
For the sake of testing I've updated to the latest grub from 19.10
(2.04-1ubuntu12) and I can't boot Windows anymore. My exact steps were:
0. Ubuntu 19.10 with grub from 19.04. Everything works
1. Move /etc/grub.d/07_os-prober back to /etc/grub.d/30_os-prober to rule this
change out
2. sudo apt
This issue has been fix in linux-oem 4.15.0-1059.68
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1847063
Title:
Fix non-working Realtek USB ethernet after system resume
To manage notifications
*** This bug is a duplicate of bug 1830961 ***
https://bugs.launchpad.net/bugs/1830961
This bug is already fixed in current Ubuntu versions (see bug 1830961)
The only problem here is that you still have an old kernel installed
that's not compatible with gcc-9. Just uninstall kernel
** Changed in: linux (Ubuntu Eoan)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1848750
Title:
Eoan update: 5.3.7 upstream stable release
To manage
Yeah it sounds like the XPS 9575 is the main model affected. Also
Precision 5530 (comment #14).
** Summary changed:
- [Dell BIOSes dated 27 Mar 2019] laptop keyboard & touchpad not working at gdm
screen after boot
+ [Dell BIOSes dated 27 Mar 2019, XPS 9575, Precision 5530] laptop keyboard &
I installed the final image on this device a couple of times and could
not reproduce the issue.
Marking this as Invalid.
** Changed in: gnome-initial-setup (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
Bug 1839317 looks too similar to ignore the possibility of the same
underlying issue. There's other person there besides me who reports the
same behavior on amd64.
My Windows bootloader is fine.
I can boot Windows using my motherboard's EFI boot menu selector.
I can boot Windows if I downgrade
Also there is one more thing weird. Before I fresh install the 19.10
beta,I used Ubuntu 19.04 which was upgraded from 18.04.There was same
issue at first when I fresh installed 18.04,but then it's gone after
upgrading to 19.04.
--
You received this bug notification because you are a member of
Device: XPS 13 7390
Image: 19.10 Final
Kernel: 5.3.0-19-generic
Mice tested: Logitech M585, Microsoft Designer Mouse
The issue is gone.
@wysiwyg31: could you give it a try? You can boot a live session of
Ubuntu 19.10 on your device and try to pair your Bluetooth mouse.
If it works for you,
Fixed on Dell XPS 13 7390 with 5.3.0-19.
** Tags added: cqa-verified
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1845454
Title:
Kernel panic in tpm_ functions when booting kernel 5.3 in Ubuntu
Posted again with a proper subscription instead of guest post:
https://lists.ubuntu.com/archives/kernel-team/2019-October/104898.html
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1848481
Title:
** Changed in: kernel-sru-workflow/prepare-package
Status: New => Confirmed
** 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:
*** This bug is a duplicate of bug 1743592 ***
https://bugs.launchpad.net/bugs/1743592
** Bug watch added: Debian Bug tracker #942817
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=942817
** Also affects: nginx (Debian) via
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=942817
** Changed in: kernel-sru-workflow/prepare-package
Status: New => Confirmed
** 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:
** Changed in: kernel-sru-workflow/prepare-package
Status: New => Confirmed
** 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:
** Changed in: kernel-sru-workflow/prepare-package
Status: New => Confirmed
** 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:
Debian proposal patch:
https://bugs.debian.org/cgi-bin/bugreport.cgi?att=2;bug=942817;filename=0001-Allow-nginx-to-start-on-ipv6-disabled-system.patch;msg=15
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Changed in: kernel-sru-workflow/prepare-package
Status: New => Confirmed
** 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:
** Changed in: kernel-sru-workflow/prepare-package
Status: New => Confirmed
** 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:
Yes, works fine.
Not sure if it's worth patching the ERR_FILE_NOT_FOUND page - to somehow
explain snap permissions and how to adjust them..
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1849072
Debian bug discussion:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=942817
** Bug watch added: Debian Bug tracker #942817
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=942817
** Also affects: nginx (Debian) via
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=942817
** Changed in: kernel-sru-workflow/prepare-package
Status: New => Confirmed
** 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:
** Changed in: kernel-sru-workflow/prepare-package
Status: New => Confirmed
** 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:
** Changed in: kernel-sru-workflow/prepare-package
Status: New => Confirmed
** 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:
** Tags added: rls-ee-incoming
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1845801
Title:
[nvidia] Automatic login fails and then all subsequent logins fail.
Killing gnome-session-binary fixes
** Package changed: alsa-driver (Ubuntu) => gnome-control-center
(Ubuntu)
** Also affects: gnome-bluetooth (Ubuntu)
Importance: Undecided
Status: New
** Also affects: bluez (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a
** Changed in: kernel-sru-workflow/promote-to-security
Status: New => Confirmed
** 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:
** Changed in: kernel-sru-workflow/promote-to-security
Status: New => Confirmed
** 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:
** Changed in: kernel-sru-workflow/promote-to-security
Status: New => Confirmed
** 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:
I will need to debug this more in detail. If we find it is Xorg giving
us the negative pointer coordinates then it should be fixed there. But
it might just be a mutter bug...
** Tags added: rls-ee-incoming
** Changed in: gnome-shell (Ubuntu)
Assignee: (unassigned) => Daniel van Vugt
** Changed in: kernel-sru-workflow/promote-to-security
Status: New => Confirmed
** 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:
** Changed in: kernel-sru-workflow/prepare-package
Status: New => Confirmed
** 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:
** Changed in: kernel-sru-workflow/prepare-package
Status: In Progress => Fix Committed
** Changed in: kernel-sru-workflow/prepare-package
Status: Fix Committed => Fix Released
** Changed in: kernel-sru-workflow/prepare-package-lrm
Status: In Progress => Fix Committed
**
Thanks for the bug report and screenshot. That does confirm it is
https://gitlab.gnome.org/GNOME/gnome-shell/issues/1649
** Tags added: eoan
** Also affects: gnome-shell via
https://gitlab.gnome.org/GNOME/gnome-shell/issues/1649
Importance: Unknown
Status: Unknown
** Changed in:
Fixed FTB errors.
** Description changed:
[Impact]
- * Users have reported the inability to use soundfonts with Carla hosted
+ * Users have reported the inability to use soundfonts with Carla hosted
synthesizer plugins
- * Backporting this to the stable release would fix the
** 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 --
packages:
*** This bug is a duplicate of bug 1847570 ***
https://bugs.launchpad.net/bugs/1847570
Thank you for taking the time to report this bug and helping to make
Ubuntu better. This particular bug has already been reported and is a
duplicate of bug 1847570, so it is being marked as such. Please
XPS 9575 isn't (currently) available for purchase with Ubuntu. So yes,
it's below the radar for something that is typically tested, tracked, or
fixed from a BIOS or validation team perspective.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Public bug reported:
Kindly see this question in StackExchange:
https://superuser.com/q/1494196/253105
If a busy resource path is passed such as `fusermount -u
/path/to/busy/resource`, fusermount gives the following message:
`fusermount: failed to unmount /home/path/to/busy/resource: Device or
@Christian,
I'm flagging the libvirt SRUs as Opinion. So far I have done quite a lot
cherry-picks and backports identifying all the structures that have
changed and I'm not currently seeing how this can be done as a SRU (even
for Disco). There are quite a few data model changes to how libvirt was
*** This bug is a duplicate of bug 1845801 ***
https://bugs.launchpad.net/bugs/1845801
Thank you for taking the time to report this bug and helping to make
Ubuntu better. This particular bug has already been reported and is a
duplicate of bug 1845801, so it is being marked as such. Please
** Tags added: rls-ff-incoming
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1774843
Title:
apport python exception handler messes up python3.7
To manage notifications about this bug go to:
On Mon, Oct 21, 2019 at 07:57:19PM -, Olivier Tilloy wrote:
> Can you check whether the password-manager-service interface is
> connected?
> snap connections chromium | grep password
Output is:
$ snap connections chromium | grep password
password-manager-service
Thanks but that didn't attach as much info as I had hoped.
Please run:
lspci -k > lspcik.txt
dmesg > dmesg.txt
and then attach the files 'lspcik.txt' and 'dmesg.txt'.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
1 - 100 of 1032 matches
Mail list logo
