*** Bug 137775 has been marked as 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/1900454
Title:
Calc doesn't recalculate formulas on cell content changes
To manage notif
*** Bug 137784 has been marked as 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/1900454
Title:
Calc doesn't recalculate formulas on cell content changes
To manage notif
** Changed in: snapd (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/1858636
Title:
snapd generates incomplete fontconfig caches, result in emoji
re
** Changed in: ubiquity (Ubuntu)
Status: Fix Committed => Triaged
** Summary changed:
- grub-install fails due to no space left on ESP
+ UEFI on Legacy - grub-install fails due to no space left on ESP
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
*** This bug is a duplicate of bug 1901137 ***
https://bugs.launchpad.net/bugs/1901137
** This bug has been marked a duplicate of bug 1901137
grub-install fails due to no space left on ESP
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed t
5.4.71!? Realy? And how long can it take when 5.4.0-55 is available?
Years? OMG That's very bad news for me.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1894017
Title:
Keyboard not working
To man
It also looks like the BIOS is hiding the Intel GPU, which your old Xorg
logs seem to suggest is required to drive the screen, and night light.
Please look in your BIOS to try and re-enable the integrated Intel GPU.
** Package changed: xorg (Ubuntu) => ubuntu
** Changed in: ubuntu
Status:
It looks like the Nvidia driver also is not working for you... Try
removing and reinstalling the Nvidia driver via the 'Additional Drivers'
app.
Failing that, I think this should be merged into one of: bug 1880739,
bug 1890957
--
You received this bug notification because you are a member of Ubu
Your kernel log mentions:
[ 618.131916] i915 :00:02.0: [drm] *ERROR* Atomic update failure on
pipe B (start=36634 end=36635) time 217 us, min 1431, max 1439, scanline
start 1421, end 1440
which I think can only happen in Xorg sessions.
Try selecting 'Ubuntu on Wayland' from the login screen
** Tags added: nvidia
** Package changed: xorg (Ubuntu) => nvidia-graphics-drivers-450
(Ubuntu)
** Also affects: mutter (Ubuntu)
Importance: Undecided
Status: New
** Changed in: mutter (Ubuntu)
Importance: Undecided => High
** Changed in: nvidia-graphics-drivers-450 (Ubuntu)
Imp
** Description changed:
- This bug is for tracking purpose.
+ BugLink: https://bugs.launchpad.net/bugs/1900809
+
+ [Impact]
+ Intel released the sof-firmware v1.6, and in our oem projects, the
+ Dell TGL machines and the machines with soundwire audio need the
+ new firmware, otherwise they will f
Have you tried blacklisting the kernel module "intel_vbtn" as a
workaround?
By the way, on Chuwi Minibook m3-8100Y, "cat
/sys/class/dmi/id/chassis_type" returns "3", so all good in that regard.
Thanks, Hans!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
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/1901563
Title:
Kernel panic - Xorg tainted - i915
To mana
Sounds like this is now also blocked on bug 1802533.
** Bug watch added: gitlab.gnome.org/GNOME/gnome-shell/-/issues #3329
https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/3329
** Also affects: gnome-shell via
https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/3329
Importance: Unknow
** Changed in: virtualbox (Ubuntu)
Status: New => In Progress
** Also affects: virtualbox (Ubuntu Groovy)
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/bu
Given I've been using the same hardware for a couple of years, I doubt
it is a hardware issue. I know hardware decays over time, but it seems
me much more likely this is due to one of the upgrade that apt installed
just before I had this issue for the first time.
I see from /var/log/apt/history.lo
*** This bug is a duplicate of bug 1867668 ***
https://bugs.launchpad.net/bugs/1867668
Hi,
I followed the suggested solution to remove the outdated 'Intel's driver
as per bug 1867668
sudo apt remove xserver-xorg-video-intel
And this resolved the reported issues : corrupted background and t
Public bug reported:
Nut seems to have three systemd units. When nut.conf contains
"mode=netclient", there is a lengthy delay to system startup / shutdown
because nut-driver cannot start/stop (the UPS is remote, so the user
will have either not configured this file, or it will not find an
attached
** Also affects: linux (Ubuntu Groovy)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu Groovy)
Importance: Undecided => Low
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/19
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: systemd (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/1899232
Title:
an
Well it booted fine to the kernel so I'll reassign it there, some mode
setting going wrong ai assume.
** Package changed: grub2 (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
Since there are some discussions about this ticket on other
communication channels, I want to clarify and sum up the situation here:
An installation on a DASD disk that is virtio-attached, like:
virt-install --name focal --memory 2048 --disk
path=/dev/disk/by-path/ccw-0.0.1234 --cdrom ./install_i
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 1901583
and then change the status of the bug to 'Confirmed'.
If, due to the nature
** Attachment added: "virt-install_with_legacy d-i-image.txt"
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1893775/+attachment/5427706/+files/virt-install_with_legacy%20d-i-image.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubun
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: apturl (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/1897298
Title:
apt
We could in theory backport
https://github.com/mariadb/server/commit/5e4b657dd44dce601c91bc77a41f6e382bc32000
to MariaDB 10.3 in Ubuntu, if the Ubuntu 20.04 "release managers" would
allow such a stable update upload.
Somebody would need to step up and champion for it. I don't have the
time to take
** Changed in: linux (Ubuntu)
Importance: Undecided => Low
** Changed in: linux (Ubuntu)
Status: Incomplete => Triaged
** Changed in: linux (Ubuntu Groovy)
Status: New => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subsc
This bug was fixed in the package mariadb-10.3 -
1:10.3.25-0ubuntu0.20.04.1
---
mariadb-10.3 (1:10.3.25-0ubuntu0.20.04.1) focal-security; urgency=medium
* SECURITY UPDATE: New upstream version 10.3.25 includes fixes for the
following security vulnerabilities (LP: #1899500):
Thank you for taking the time to report this bug and helping to make
Ubuntu better. It seems that your bug report is not filed about a
specific source package though, rather it is just filed against Ubuntu
in general. It is important that bug reports be filed about source
packages so that people
** Changed in: linux (Ubuntu Groovy)
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/1891421
Title:
kci_test_encap_fou() in rtnetlink.sh from kselftests/net
Thanks Daniel. I'll try that. I was using Gnome Flashback, but I can
probably get used to this look as well.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1901563
Title:
Kernel panic - Xorg tainted
I might add that the most noticable time-based impact here is on the
shutdown end of things, rather than startup. It does take some time to
fail on startup, but on shutdown it seems to have a 90 second wait
before it fails...
--
You received this bug notification because you are a member of Ubunt
** Changed in: linux-raspi (Ubuntu Groovy)
Importance: Undecided => Medium
** Changed in: linux-raspi (Ubuntu Groovy)
Status: New => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bu
*** This bug is a duplicate of bug 1900683 ***
https://bugs.launchpad.net/bugs/1900683
Yes. It's a bug in the meta package. See #1900683.
** This bug has been marked a duplicate of bug 1900683
Installing wireguard-tools pulls in the generic kernel
--
You received this bug notification be
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: linux-raspi (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/1900683
Title:
** Changed in: linux (Ubuntu Groovy)
Importance: Undecided => Medium
** Changed in: linux (Ubuntu Groovy)
Status: New => 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/1899508
** Package changed: linux-raspi2 (Ubuntu) => linux-raspi (Ubuntu)
** Also affects: bluez (Ubuntu Groovy)
Importance: Undecided
Status: New
** Also affects: pi-bluetooth (Ubuntu Groovy)
Importance: Undecided
Status: New
** Also affects: linux-raspi (Ubuntu Groovy)
Importanc
@Heather Ellworth: I just tried to completely remove libreoffice as you
suggested, then re-enabled Libre Office's PPA, then reinstalled as you
suggested. But to no avail. Libre Office still immediately crashed
whenever I try to create a new or open either a Writer document or a
Calc spreadsheet.
I
PPA:
- firmware: https://launchpad.net/~vicamo/+archive/ubuntu/ppa-1879633
- kernel: https://launchpad.net/~vicamo/+archive/ubuntu/ppa-1879633.1
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1879633
T
@satmandu: buildfix_kernel_5.8.patch is no longer accessible via the link you
mention. Is this the same patch as mentioned here? (002-kernel-5.8.patch)
https://aur.archlinux.org/packages/nvidia-340xx
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscrib
** Changed in: linux-azure (Ubuntu Groovy)
Importance: Undecided => Medium
** Changed in: linux-azure (Ubuntu Groovy)
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.launchpa
In case anyone needs to install the last known binaries that work, I
uploaded a nice overview of the problem and direct links to the Ubuntu
packages here:
https://github.com/alkisg/liveusb/issues/3
** Bug watch added: github.com/alkisg/liveusb/issues #3
https://github.com/alkisg/liveusb/issues
This bug affects compatibility with unison-2.48.4-1+b1 on Debian buster
also.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1875475
Title:
Unison from Ubuntu 20.04 is incompatible with Unison from U
Thank you zwerg2000. I bought a Realtek RTL8192 usb wlan adapter. With
this adapter on Ubuntu 20.10 now association works.
Association fails with a Qualcomm qca6174 hw3.2. This issue is still
present on Ubuntu 20.10. The issue might be in wpasupplicant or the
underlying kernel driver since it is h
=== Verification ===
1. Start qemu using the proposed package:
$ sudo qemu-system-x86_64 -machine none -S -nographic -monitor stdio -serial
null
QEMU 3.1.0 monitor - type 'help' for more information
(qemu) info version
3.1.0Debian 1:3.1+dfsg-2ubuntu3.7~cloud1
2. Run "apt install --re
** Changed in: linux-azure-4.15 (Ubuntu Bionic)
Importance: Undecided => Medium
** Changed in: linux-azure-4.15 (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/
Thanks for the hint. Using the upstream packages
https://download.opensuse.org/repositories/isv:/ownCloud:/desktop/ could
be an alternative, but unfortunately there are no 20.10 packages yet and
these for 20.04 don't work on 20.10 due to dependency issues.
--
You received this bug notification be
Public bug reported:
??
ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: mariadb-server-core-10.3 1:10.3.24+maria~bionic
ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65
Uname: Linux 5.4.0-52-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.10
AptOrdering:
mariadb-server-core-10.3
Public bug reported:
snapd package installs a "/etc/sudoers.d/99-snapd.conf" file.
However, for some (undocumented or poorly documented) reason, files with
dots are ignored by sudo. Thus, "/etc/sudoers.d/99-snapd.conf" is
ignored, but "/etc/sudoers.d/99-snapd" would work.
See: https://askubuntu.
Public bug reported:
With (Dell) Ubuntu 20.04.1 on a Dell XPS 13 9310, after allowing release
upgrades, the process crashed the first time.
```
$ sudo do-release-upgrade
Neue Veröffentlichungen von Ubuntu werden gesucht
Holen:1 Signatur der Aktualisierungsanwendung [819 B]
Hello Balint, or anyone else affected,
Accepted google-compute-engine-oslogin into bionic-proposed. The package
will build now and be available at https://launchpad.net/ubuntu/+source
/google-compute-engine-oslogin/20200925.00-0ubuntu3~18.04.0 in a few
hours, and then in the -proposed repository.
Hello Balint, or anyone else affected,
Accepted google-compute-engine-oslogin into bionic-proposed. The package
will build now and be available at https://launchpad.net/ubuntu/+source
/google-compute-engine-oslogin/20200925.00-0ubuntu3~18.04.0 in a few
hours, and then in the -proposed repository.
Ubiquity tries to re-use ESP if possible.
Given that we booted in Bios mode, I wonder, if ubiquity missdetects the
ESP on the usb/cdrom that installer was booted from, as the one that can
be reused when it really can't.
Whilst looking through the logs, it is not obvious to me, if a sane ESP
i
Hello Steve, or anyone else affected,
Accepted google-compute-engine-oslogin into bionic-proposed. The package
will build now and be available at https://launchpad.net/ubuntu/+source
/google-compute-engine-oslogin/20200925.00-0ubuntu3~18.04.0 in a few
hours, and then in the -proposed repository.
** Attachment removed: "ProcEnviron.txt"
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1901603/+attachment/5427583/+files/ProcEnviron.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.
I'm seeing the same behavior and it's very annoying. I saw this already
on 18.04 and hoped it would be gone in 20.04 but it's still there
(complete new Ubuntu installation).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.
Public bug reported:
Installing 20.04 LTS on a samsung pro SSD and on I5 10400. Hyper-
threading and TPM are disabled.
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: ubiquity 20.04.15.2
ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
Uname: Linux 5.4.0-42-generic x86_64
NonfreeKern
@hui.wang
hello,
Do you know what blocks it?
Thanks,
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1899745
Title:
[SRU] alsa-utils: let alsactl support _boot section defined in ucm
To manage not
I initially saw flickering with Wayland, so i switched to Xorg to check
if it happens also there... and it happens.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1550779
Title:
Black screen flickeri
This was fixed in snapd 2.46. The file is no longer shipped by the snapd
package. Does it still exist in your system?
** Changed in: snapd (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https
Answering my own question:
No, this was the wrong file. I extracted the right one from the gut repository
here:
https://aur.archlinux.org/pkgbase/nvidia-340xx/
Needed to adjust the paths in the .patch file, but now it works.
Attaching the adjusted patch.
--
You received this bug notification be
** Patch added: "patch for kernel-5.8"
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/1896878/+attachment/5427736/+files/0002-kernel-5.8.patch
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs
Hello Steve, or anyone else affected,
Accepted google-compute-engine-oslogin into focal-proposed. The package
will build now and be available at https://launchpad.net/ubuntu/+source
/google-compute-engine-oslogin/20200925.00-0ubuntu3~20.04.0 in a few
hours, and then in the -proposed repository.
P
Hello Balint, or anyone else affected,
Accepted google-compute-engine-oslogin into focal-proposed. The package
will build now and be available at https://launchpad.net/ubuntu/+source
/google-compute-engine-oslogin/20200925.00-0ubuntu3~20.04.0 in a few
hours, and then in the -proposed repository.
/etc/sudoers.d/README pretty clearly states:
# This will cause sudo to read and parse any files in the /etc/sudoers.d
# directory that do not end in '~' or contain a '.' character.
#
i wouldn't call that poorly documented (unless someone deletes the
README file) ...
--
You received this bug no
--- Comment From heinz-werner_se...@de.ibm.com 2020-10-27 06:00 EDT---
Feature request moved to 22.04...
--- Comment From heinz-werner_se...@de.ibm.com 2020-10-27 06:02 EDT---
Mistake: Changed to 21.04 again...
--
You received this bug notification because you are a member of Ubu
Hello Balint, or anyone else affected,
Accepted gce-compute-image-packages into bionic-proposed. The package
will build now and be available at https://launchpad.net/ubuntu/+source
/gce-compute-image-packages/20190801-0ubuntu1~18.04.2 in a few hours,
and then in the -proposed repository.
Please h
Hello Balint, or anyone else affected,
Accepted google-compute-engine-oslogin into focal-proposed. The package
will build now and be available at https://launchpad.net/ubuntu/+source
/google-compute-engine-oslogin/20200925.00-0ubuntu3~20.04.0 in a few
hours, and then in the -proposed repository.
Hello Balint, or anyone else affected,
Accepted gce-compute-image-packages into xenial-proposed. The package
will build now and be available at https://launchpad.net/ubuntu/+source
/gce-compute-image-packages/20190801-0ubuntu1~16.04.2 in a few hours,
and then in the -proposed repository.
Please h
This bug has been pulled in via the backported changelog of google-
compute-engine-oslogin. Let's mark this as 'verification-done' and
perform all the actual verification in LP: #1899629 instead.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Hello Balint, or anyone else affected,
Accepted gce-compute-image-packages into focal-proposed. The package
will build now and be available at https://launchpad.net/ubuntu/+source
/gce-compute-image-packages/20190801-0ubuntu4.2 in a few hours, and then
in the -proposed repository.
Please help us
This bug has been pulled in via the backported changelog of google-
compute-engine-oslogin. Let's mark this as 'verification-done' and
perform all the actual verification in LP: #1899629 instead.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Hello Balint, or anyone else affected,
Accepted google-compute-engine-oslogin into xenial-proposed. The package
will build now and be available at https://launchpad.net/ubuntu/+source
/google-compute-engine-oslogin/20200925.00-0ubuntu3~16.04.0 in a few
hours, and then in the -proposed repository.
Hello Balint, or anyone else affected,
Accepted google-compute-engine-oslogin into xenial-proposed. The package
will build now and be available at https://launchpad.net/ubuntu/+source
/google-compute-engine-oslogin/20200925.00-0ubuntu3~16.04.0 in a few
hours, and then in the -proposed repository.
Hello Steve, or anyone else affected,
Accepted google-compute-engine-oslogin into xenial-proposed. The package
will build now and be available at https://launchpad.net/ubuntu/+source
/google-compute-engine-oslogin/20200925.00-0ubuntu3~16.04.0 in a few
hours, and then in the -proposed repository.
I see a "CasperMD5CheckResult: pass" in your top details... yet the
report still shows IO errors on your install media?
If this was a VM, the problem is often a lack of memory allocated to the
virtual machine.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which i
Could you try on your machine to maybe create a new user and see if it
has the same issue? Could you add the 'journalctl -b 0' log after
triggering the issue?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/b
Thank you for taking the time to report this issue and helping to make
Ubuntu better.
This package failure looks like it was caused by bad ISO download,
corrupted install media, or device failure. eg. look in the logs and
you'll see messages like these :-
Oct 27 09:55:11 ubuntu kernel: [ 401.777
** Tags added: rls-gg-incoming
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1896878
Title:
Doesn't compile for groovy
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubunt
** Changed in: thunderbird (Ubuntu)
Status: Confirmed => 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/1895643
Title:
Backport Thunderbird 78 to 20.04 LTS and 18.04 LTS
To manage
** Tags added: snap
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1901586
Title:
[snap] CA Certificates from /usr/local/share/ca-certificates are not
used
To manage notifications about this bug g
*** This bug is a duplicate of bug 1897754 ***
https://bugs.launchpad.net/bugs/1897754
** This bug has been marked a duplicate of bug 1897754
flameshot: The icon does not appear in the GNOME bar
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscr
(the plugin as package should depends on the binding but we could
probably let gedit recommends the gir so it's installed by default)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1901446
Title:
Add
Thanks for reporting.
Once Ubuntu Hirsute (the current development release) has the intial
toolchain in place, it will automatically sync new packages from Debian
Unstable. This should resolve this issue in a few days.
--
You received this bug notification because you are a member of Ubuntu
Bugs
After adding some random third user, snap removal works again.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1901578
Title:
Cannot remove snap package ubuntu 20.10
To manage notifications about thi
I'm seeing the same problem after a clean install of 20.10 over a pre-
existing home folder.
~ sudo snap remove slack
error: cannot perform the following tasks:
- Save data of snap "slack" in automatic snapshot set #4 (user: lookup userid
1001: no such file or directory)
~ id 1001
id: ‘1001’:
Problem remains in 20.10
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1835024
Title:
Links triggered within most snap apps open in a separate browser
session
To manage notifications about this b
thanks for the update, closing the report
** Changed in: rygel (Ubuntu)
Assignee: Soós Miklós (soosmiki) => (unassigned)
** Changed in: rygel (Ubuntu)
Status: New => Invalid
** Changed in: rygel (Ubuntu)
Importance: Undecided => Low
--
You received this bug notification because
** Changed in: linux (Ubuntu Groovy)
Status: Confirmed => 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/1900847
Title:
Fix non-working Intel NVMe after S3
To manage notificatio
Right, indeed the source is the Debian unmodified one so it would
probably be better to report the issue to the debian tracker directly
** Changed in: gedit (Ubuntu)
Importance: Wishlist => Low
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
Thanks, 0.39 and newer depends on a the new tracker3 service which was
released late in the cycle and didn't let enough time for testing and
ensure quality so it was decided to postpone the update to next cycle
** Changed in: rygel (Ubuntu)
Importance: Undecided => Wishlist
** Changed in: ryge
One suggestion discussed in https://forum.snapcraft.io/t/allow-classic-
confinement-for-postman-agent/19228 is to use a content interface to
allow third-party snaps to write to
~/snap/chromium/common/chromium/NativeMessagingHosts/. Whether it’s a
good idea from a security perspective is open for di
** Summary changed:
- Update for Unicode 13
+ Missing some unicode 13 emojis
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1870794
Title:
Missing some unicode 13 emojis
To manage notifications abo
** Changed in: linux (Ubuntu Groovy)
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/1900088
Title:
Improve descriptions for XFAIL cases in kselftests/net/p
After adding a second user...
~ sudo snap remove slack
error: cannot perform the following tasks:
- Save data of snap "slack" in automatic snapshot set #5 (user: lookup userid
1002: no such file or directory)
I did have a third user for testing out other things.
--
You received this bug notif
Don't know
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1899745
Title:
[SRU] alsa-utils: let alsactl support _boot section defined in ucm
To manage notifications about this bug go to:
https://bugs
For a strictly confined snap such as chromium, /etc/ssl/certs is
provided by the core snap, not by the host system, which explains why
your local CA isn't being recognized.
As a workaround, and to understand better the problem, can you manually
import the certificate from chrome://settings/certifi
** Description changed:
[Impact]
* Sometimes it is not obvious why initrdless boot is generated; when is
it attempted; and when it fails and boots with initrd.
* Improve UX by leaving breadcrumbs and emit messages about initrdless
boot, in more places
[Test Case]
- * Boo
Here's how to resolve the issue:
- put the two patches above into /usr/src/nvidia-340-340.108/patches/
- modify /usr/src/nvidia-340-340.108/dkms.conf:
- remove any PATCH[] lines
- add
```PATCH[0]="kernel-5.7.patch"
PATCH[1]="buildfix_kernel_5.8.patch"```
- dpkg --configure nvidia-340
--
You
Here's how to resolve the issue:
- put the two patches above into /usr/src/nvidia-340-340.108/patches/
- modify /usr/src/nvidia-340-340.108/dkms.conf:
- remove any PATCH[] lines
- add
PATCH[0]="kernel-5.7.patch"
PATCH[1]="0002-kernel-5.8.patch"
- dpkg --configure nvidia-340
--
You re
1 - 100 of 640 matches
Mail list logo
