Public bug reported:
Export nvfs register and unregister functions as
GPL
On linux kernel 6.6 and above, __symbol_get() on the registration functions
from nvidia-fs was failing as a GPL modules are no longer allowed to
__symbol_get() on non-gpl exported symbols. This change fixes that issue.
Public bug reported:
NVIDIA patches April 17 - May 31, 2024
** Affects: linux-nvidia-tegra (Ubuntu)
Importance: Undecided
Status: New
** Affects: linux-nvidia-tegra-igx (Ubuntu)
Importance: Undecided
Status: New
** Also affects: linux-nvidia-tegra (Ubuntu)
Public bug reported:
The TPM SPI transfer mechanism uses MAX_SPI_FRAMESIZE for computing the
maximum transfer length and the size of the transfer buffer. As such, it
does not account for the 4 bytes of header that prepends the SPI data
frame. This can result in out-of-bounds
Public bug reported:
There are systems in production that don't have firmware that supports
coresight_etm4x. Instead of removing completely, blacklist
coresight_etm4x so systems with the correct firmware can use the module.
** Affects: linux-nvidia (Ubuntu)
Importance: Undecided
Public bug reported:
A new version of the nvidia-fs driver is out, make the changes to the
noble:linux-nvidia kernel sources to pull that version into the build.
** Affects: linux-nvidia (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you
Public bug reported:
While calculating the hardware interrupt number for a MSI interrupt, the
higher bits (i.e. from bit-5 onwards a.k.a domain_nr >= 32) of the PCI
domain number gets truncated because of the shifted value casting to return
type of pci_domain_nr() which is 'int'.
Public bug reported:
The controller has several register bits describing access control
information for a given GPIO pin. When SCR_SEC_[R|W]EN is unset, it
means we have full read/write access to all the registers for given GPIO
pin. When SCR_SEC[R|W]EN is set, it means we need to further check
I encountered the same issue recently and attempted to build systemd from
source and patch the retry behavior from #24906, but I failed to make it work.
Instead, I modified systemd-cryptsetup-generator to include retry behavior into
the generated unit files for the encrypted volumes, which has
Public bug reported:
PROBLEM:
While trying to monitor the ipc group for using perf-stat tool, despite it
being supported, I get the following errors:
$ sudo perf list | grep ipc
ipc
ipc_rate
retired_ipc
spec_ipc
$ sudo -S perf stat -a -M ipc -- sudo -S stress-ng --cpu 0 -t 10s
Error:
This does appear to fix the issue for me on 22.4.04 LTS
sudo add-apt-repository ppa:vanvugt/mutter
sudo apt update
Then upgrade mutter-common, libmutter-10-0 and gir1.1-mutter-10 (I'm not
certain if all 3 of these are required or not).
This will get you version 42.9-0ubuntu7
Reboot !! (required)
** Also affects: linux-nvidia-tegra (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/2061900
Title:
apply NVIDIA patches April 6-16, 2024
To
Public bug reported:
Apply NVIDIA patches April 6-16, 2024:
NVIDIA: SAUCE: phy: xusb: Disable USB2 tracking for T234
https://git-master.nvidia.com/r/c/3rdparty/canonical/linux-jammy/+/3115016
NVIDIA: SAUCE: enable handling of macronix block protection
Fixed by linux 6.5.0-27.28
** Changed in: linux (Ubuntu)
Status: New => 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/2048942
Title:
Openvswitch matching broken for nat packets
Public bug reported:
There are a number of configuration options that were set in the 5.15.
and 6.5 nvidia kernels. When the 6.8 based linux-nvidia kernel was
created those config options were not brought forward. This patch set
brings them into the 6.8 kernel.
** Affects: linux-nvidia (Ubuntu)
Public bug reported:
NVIDIA patches Mar 22 - April 5, 2024.
NVIDIA tracking details
soc/tegra: fuse: Remove security_mode fuse from keepout list
https://git-master.nvidia.com/r/c/3rdparty/canonical/linux-jammy/+/3107228
soc/tegra: fuse: Update Tegra234 nvmem keepout list
Public bug reported:
GDS enables a direct data path for direct memory access (DMA) transfers
between GPU memory and storage, which avoids a bounce buffer through the
CPU. This direct path increases system bandwidth and decreases the
latency and utilization load on the CPU.
This functionality has
** Changed in: linux-nvidia-6.5 (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/2059178
Title:
Pull request to fully enable nvidia-fs NVMe support
To manage
Public bug reported:
This pull request addresses a missing patch which fully enables GDS
functionality using NVMe devices.
** Affects: linux-nvidia-6.5 (Ubuntu)
Importance: Undecided
Status: Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs,
Public bug reported:
The SD card is being observed to get corrupted after some number of
reboots, e.g. often in the neighborhood of 10-50 iterations.
** Affects: linux-nvidia-tegra (Ubuntu)
Importance: Undecided
Status: New
** Affects: linux-nvidia-tegra-igx (Ubuntu)
Public bug reported:
Apply patches to linux-nvidia-tegra (for use in both linux-nvidia-tegra
and linux-nvida-tegra-igx).
** Affects: linux-nvidia-tegra (Ubuntu)
Importance: Undecided
Status: New
** Affects: linux-nvidia-tegra-igx (Ubuntu)
Importance: Undecided
The above crash was happening with large downloads of img files or git
clones of large repositories (Ubuntu kernels) over wifi. I have changed
to hard wired ethernet and I've not been able to reproduce it. With Wifi
it's been very reproduceable.
--
You received this bug notification because you
Public bug reported:
Apply patches to linux-nvidia-tegra (for use in both linux-nvidia-tegra
and linux-nvida-tegra-igx).
** Affects: linux-nvidia-tegra (Ubuntu)
Importance: Undecided
Status: New
** Affects: linux-nvidia-tegra-igx (Ubuntu)
Importance: Undecided
Public bug reported:
Mar 7 19:07:10 ripper kernel: [9.873519] UBSAN: array-index-out-of-bounds
in
/build/linux-hwe-6.5-YpKOvT/linux-hwe-6.5-6.5.0/drivers/gpu/drm/amd/amdgpu/../pm/powerplay/hwmgr/smu7_hwmgr.c:3676:4
Mar 7 19:07:10 ripper kernel: [9.873531] index 7 is out of range for
Public bug reported:
Apply patches to linux-nvidia-tegra (for use in both linux-nvidia-tegra
and linux-nvida-tegra-igx).
** Affects: linux-nvidia-tegra (Ubuntu)
Importance: Undecided
Status: New
** Affects: linux-nvidia-tegra-igx (Ubuntu)
Importance: Undecided
Public bug reported:
The current calculation of min_free_kbytes only uses ZONE_DMA and
ZONE_NORMAL pages,but the ZONE_MOVABLE zone->_watermark[WMARK_MIN] will
also divide part of min_free_kbytes.This will cause the min watermark of
ZONE_NORMAL to be too small in the presence of
Public bug reported:
Apply patches to linux-nvidia-tegra (for use in both linux-nvidia-tegra
and linux-nvida-tegra-igx).
** Affects: linux-nvidia-tegra (Ubuntu)
Importance: Undecided
Status: New
** Affects: linux-nvidia-tegra-igx (Ubuntu)
Importance: Undecided
Public bug reported:
[ 1918.995157] watchdog: BUG: soft lockup - CPU#0 stuck for 1725s! [kswapd0:42]
[ 1919.002366] Modules linked in: raid10 raid456 libcrc32c async_raid6_recov
async_memcpy async_pq async_xor xor xor_neon async_tx raid6_pq raid1 raid0
multipath linear scsi_dh_alua scsi_dh_emc
Public bug reported:
Coresight PMU driver didn't reject events meant for other PMUs.
This caused some of the Core PMU events disappearing from
the output of "perf list". In addition, trying to run e.g.
$ perf stat -e r2 sleep 1
made Coresight PMU driver to handle the
Public bug reported:
This series enables detection of ACPI based TRBE devices via a stand alone
purpose built representative platform device. But as a pre-requisite this
changes coresight_platform_data structure assignment for the TRBE device.
** Affects: linux-nvidia-6.5 (Ubuntu)
After testing kernel 5.18.0 from mainline, the issue does appear
resolved -- the system will boot with "pci=nocrs" and the touchpad,
touchscreen function.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
This bug is still present in xvfb 2:1.20.13-1ubuntu1~20.04.2. It
prevents us from using `xvfb-run` when we need to disambiguate STDOUT
and STDERR.
I'm not familiar with the problem of autopkgtests, but is this still an
issue? Can autopkgtests be fixed?
If we're an impasse, does it make sense
** Description changed:
lsb_release -rd
Description: Ubuntu 21.10
Release: 21.10
- apt-cache policy tripwire
+ apt-cache policy tripwire
tripwire:
Installed: 2.4.3.7-3
Candidate: 2.4.3.7-3
Version table:
*** 2.4.3.7-3 500
500
UPDATE: suddenly jEmboss started with no errors, thanks guys!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1968178
Title:
Jemboss 6.6.0+dfsg-9ubuntu1 failed to launch
To manage notifications
After a clean install of Ubuntu 22.04, I have the same issue on an Acer
Spin 5 SP513-54N-74V2. Installing and booting into kernel 5.13.19 works
fine and resolves the issue. With kernel 5.15 and no "pci=nocrs," the
error seems to be i2c_designware: failed to claim resource.
--
You received this
Public bug reported:
Audio was working yesterday. I turned on my computer today and the only
output device is Dummy Output.
Running aplay -l output is aplay: device_list:276: no soundcards found.
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: alsa-base 1.0.25+dfsg-0ubuntu5
** Description changed:
lsb_release -rd
Description: Ubuntu 21.10
Release: 21.10
- apt-cache policy tripwire
+ apt-cache policy tripwire
tripwire:
- Installed: 2.4.3.7-3
- Candidate: 2.4.3.7-3
- Version table:
- *** 2.4.3.7-3 500
- 500
Public bug reported:
lsb_release -rd
Description: Ubuntu 21.10
Release: 21.10
apt-cache policy tripwire
tripwire:
Installed: 2.4.3.7-3
Candidate: 2.4.3.7-3
Version table:
*** 2.4.3.7-3 500
500 http://ca.archive.ubuntu.com/ubuntu impish/universe amd64 Packages
100
to continue? [Y/n]
and when I launch it fails:
java -version
openjdk version "11.0.14.1" 2022-02-08
OpenJDK Runtime Environment (build 11.0.14.1+1-Ubuntu-0ubuntu1.20.04)
OpenJDK 64-Bit Server VM (build 11.0.14.1+1-Ubuntu-0ubuntu1.20.04, mixed mode,
sharing)
brad@rudy:/etc/emboss$ je
** Package changed: ubuntu => xfce4-screensaver (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1958934
Title:
laptop does not respond to keyboard or mouse input
To manage notifications
If xfce screensaver lock screen is disabled, the issue goes away. When
enabled it comes back
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1958934
Title:
laptop does not respond to keyboard or
from suspend. I
can still get to a terminal with Ctl-Fn-Alt-F1.
I see this in kern.log at about the time of the issue:
Jan 24 11:54:58 brad-dell kernel: [14615.288956] PM: suspend exit
Jan 24 11:55:02 brad-dell kernel: [14619.411849] wlp0s20f3: authenticate with
9c:3d:cf:71:af:77
Jan 24 11:55:02
I think this has been fixed by updating the OS to Xubuntu 21.10 (&
associated kernel) & the Bios to 1.3.0. I also had to keep the sleep
mode in s2idle
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
kage: linux-image-5.11.0-41-generic 5.11.0-41.45
ProcVersionSignature: Ubuntu 5.11.0-41.45-generic 5.11.22
Uname: Linux 5.11.0-41-generic x86_64
ApportVersion: 2.20.11-0ubuntu65.4
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: brad 1280 F pulsea
** Changed in: linux-raspi (Ubuntu)
Assignee: (unassigned) => Juerg Haefliger (juergh)
** Changed in: linux-raspi (Ubuntu)
Importance: Undecided => High
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
We get this for free with the move to a 5.13 based focal:linux-intel kernel.
** Changed in: intel
Status: New => Invalid
** Changed in: linux-intel (Ubuntu)
Status: In Progress => Invalid
** Changed in: intel
Assignee: (unassigned) => Brad Figg (brad-figg)
*
This commit already exists in the focal:linux-intel intel-5.13-next.
** Changed in: intel
Status: New => Fix Committed
** Changed in: intel
Assignee: (unassigned) => Brad Figg (brad-figg)
--
You received this bug notification because you are a member of Ubuntu
Bugs,
** Tags added: lookout-canyon
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1938678
Title:
[intel] [tgl-h][iotg] [hwe-tpm] Ubuntu Core hangs during bootup on
TGL-H
To manage notifications about
** Summary changed:
- EHL board does not support soft reboot
+ [ehl] board does not support soft reboot
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1938408
Title:
[ehl] board does not support
** Summary changed:
- Shutdown hangs on EHL board
+ [ehl] Shutdown hangs on board
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1938413
Title:
[ehl] Shutdown hangs on board
To manage
** Changed in: intel
Status: New => Fix Committed
** Tags added: lookout-canyon
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1938413
Title:
Shutdown hangs on EHL board
To manage
** Changed in: intel
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/1929902
Title:
[EHL] enable USB-dw3
To manage notifications about this bug go to:
** Changed in: intel
Status: New => Fix Committed
** Tags added: lookout-canyon
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1938408
Title:
EHL board does not support soft reboot
To
Thanks sincerely for the detailed response.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1939449
Title:
Ubuntu Pro UA fails to enable fips-updates on 20.04
To manage notifications about this bug
Searching AWS marketplace I see that for Ubuntu 18, there are:
- Ubuntu Pro FIPS 18.04 LTS (offered by Canonical Group Ltd)
- Ubuntu Pro 18.04 LTS (offered by Amazon Web Services)
But for Ubuntu 20.04, a "Pro FIPS" variety does not exist, only Ubuntu
Pro 20.04 LTS.
This is confusing from a user
Public bug reported:
Using AWS AMI: ami-0193aa0a9df84a08b
Attempting to enable fips-updates with the ua command line tool fails
with error that apt "Unable to locate package ubuntu-aws-fips."
Canonical has told me directly 20.04 is now FIPS 140-2 Level 1
certified.
Output:
See upstream cmake issue:
https://gitlab.kitware.com/cmake/cmake/-/issues/20568
** Bug watch added: gitlab.kitware.com/cmake/cmake/-/issues #20568
https://gitlab.kitware.com/cmake/cmake/-/issues/20568
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Can someone point me to where you can download the previous version?
rpcbind_0.2.3-0.6ubuntu0.18.04.1_amd64.deb
I can't locate it.
Brad
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1931507
Title
systemd[1]: Starting RPC bind portmap service...
Thank you.
Brad Zoltick
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1931507
Title:
rpcbind failing on 0.2.3-0.6ubuntu0.18.04.2
To manage
ks again and
> good luck!
>
> ** Changed in: ubuntu-release-upgrader (Ubuntu)
> Status: New => Incomplete
>
> ** Tags added: lp-1928397
>
--
Brad Smart
mailto:bsmar...@afo.net
Home Phone: 734-971-7425
GVoice: 516-277-6278 (text and voice mail)
--
You receive
Public bug reported:
root@myubuntu:/var/log/dist-upgrade# grep -i broken apt.log
Starting pkgProblemResolver with broken count: 0
Starting 2 pkgProblemResolver with broken count: 0
Starting pkgProblemResolver with broken count: 28
Starting 2 pkgProblemResolver with broken count: 28
Broken
*** This bug is a duplicate of bug 1883089 ***
https://bugs.launchpad.net/bugs/1883089
As the fix this was a duplicate of has been abandoned, can this still be
addressed somehow? Is there anything I can do to move this forward?
--
You received this bug notification because you are a member
Public bug reported:
On the Raspberry Pi 400 the Night Light mode for the display seems to
have no effect. The display remains the same bright colour even when
the night light filter is enabled.
ProblemType: Bug
DistroRelease: Ubuntu 20.10
Package: xorg 1:7.7+19ubuntu15
ProcVersionSignature:
** Changed in: linux (Ubuntu Focal)
Importance: Undecided => Critical
** Changed in: linux (Ubuntu)
Importance: Undecided => Critical
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1912752
My /var/log/dist-upgrade/main.log ends:
2021-02-06 22:02:23,299 WARNING Can't mark 'ubuntu-desktop' for upgrade
(E:Error, pkgProblemResolver::Resolve generated breaks, this may be
caused by held packages.)
Am I supposed to somehow remove/disable ubuntu-desktop before I can
upgrade?
--
You
Public bug reported:
While attempting to upgrade (with the GUI) I get this error message:
"
Could not calculate the upgrade
An unresolvable problem occurred while calculating the upgrade.
If none of this applies, then please report this bug using the command
'ubuntu-bug
I've been having the same issue since building a new system a couple
months ago. The frequency is inconsistent, but rarely happens more than
once per day. Sometimes I'll lose my keyboard mid-sentence, and other
times I won't be able to unlock the system in the morning.
Oddly, my USB mouse (a
Thank you for resolving this well before Let's Encrypt's brownouts!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1893274
Title:
Certbot will stop working for 23,847 users with upcoming Let's
Testing this is pretty tricky because it's specific to the setup of
Let's Encrypt's production ACMEv1 endpoint which no longer lets people
create accounts or obtain certificates for new domains and we hardcoded
the server URL.
The way I'd test it is:
1. Obtain a real, trusted certificate from
> Brad, I'd appreciate your review wrt. your comment in
https://bugs.launchpad.net/ubuntu/+source/python-certbot-
nginx/+bug/1875471/comments/8 please. AIUI, I'm not breaking python-
certbot-apache itself, just its tests, right? In other words, with my
proposed fix I'm just moving a test fail
The following evaluation was done in early May
In summary, EDR is brand new in upstream kernels and to my
knowledge has not been exercised in-house at Canonical, and
Based on this evaluation we have no plans at this time to backport these
patches to the Focal 5.4 kernel.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1885030
Title:
[Intel] Add Error Disconnect
These commits are in the 20.04 release kernel.
** Changed in: linux (Ubuntu)
Status: Triaged => Fix Released
** Changed in: intel
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
This commit is in the released 20.04 kernel
** Changed in: linux (Ubuntu)
Status: Triaged => Fix Released
** Changed in: intel
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Changed in: linux (Ubuntu)
Status: Incomplete => Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1842142
Title:
[EHL][OSE] SPI implementation
To manage notifications about this bug
** Changed in: linux (Ubuntu)
Status: Incomplete => Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1842107
Title:
[EHL][OSE] I2C implementation
To manage notifications about this bug
Thanks again for quickly helping with this issue everyone.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1875471
Title:
python3-certbot-nginx is incompatible with its dependencies
To manage
Works for me as of latest version. :)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1876296
Title:
Broken CURL operations
To manage notifications about this bug go to:
I agree with comment #4.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1747499
Title:
98-reboot-required and Interaction with livepatch
To manage notifications about this bug go to:
I tested the proposed package successfully without any issues.
I also examined the changes to our upstream files included in the
package they are what I expected. It's our 0.40.0 certbot-nginx package
with one test change backported from a newer version.
--
You received this bug notification
The package I tested was python3-certbot-nginx 0.40.0-0ubuntu0.1.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1875471
Title:
python3-certbot-nginx is incompatible with its dependencies
To manage
Same problem here, I submitted a diff bug report, but this was what I
was getting at. It's interesting because it doesn't appear on this
version in other distros.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Fantastic! Thanks again Andreas.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1875471
Title:
python3-certbot-nginx is incompatible with its dependencies
To manage notifications about this bug go
To offer one other option based on my previous comments while trying to
keep things simple, I think in the short term you could also go with:
d) Update just python-certbot-nginx to 0.40.0 and apply this patch to
python-certbot-nginx's tests:
I think changing the build-dep to python3-idna << 2.9 is acceptable. It
looks like we hit a similar problem with the last SRU and I described
the problem and how to fix the specific issue at the time at
https://bugs.launchpad.net/ubuntu/+source/python-
acme/+bug/1836823/comments/23.
In this case,
Thanks a lot for quickly working on this issue Andreas.
Applying that commit to python-certbot 0.40.0-1 in addition to the
python-certbot-nginx changes would fix both python-certbot and python-
certbot-nginx's tests, however, it would break python-certbot-apache in
normal usage outside of tests
At the risk of sending the discussion in this issue off topic, I looked
into other potential problems with the Certbot packages in Focal/Groovy
since they've been being held back. I'm happy to move this discussion
somewhere else if people prefer.
In the current state in Focal/Groovy, the tests we
Public bug reported:
This issue only affects version 0.39.0-1 of the python-certbot-nginx
package in Ubuntu 20.04.
To reproduce the problem, install python3-certbot-nginx and run a
command like:
sudo certbot -d example.org --agree-tos --staging --register-unsafely-
without-email --nginx
This
Public bug reported:
Dub cannot find dependencies at https://code.dlang.org this is the main
registry.
Works fine using the snap package 'dub'. Issue doesn't appear on 18.04 using a
different version of dub. Version of dub downloaded from https://dlang.org/
works. I expect it to resolve
I believe if got the exfat-fuse filesystem when I installed exfat-tools
in order to mkexfatfs.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1862028
Title:
Focal uses the exfat fuse filesystem even
If I take the exfat flashdrive to a 20.04 system that does not have
exfat-utils/exfat-fuse on it, it works exactly as I expect and mounts as
an exfat filesystem.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
exfat-utils that is
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1862028
Title:
Focal uses the exfat fuse filesystem even though there is support in
the kernel
To manage notifications about
Not really no. Between this bug and
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1853008
I was forced to remove chromium-browser and snapd from my system
entirely and switch to the Google chrome binaries. Snap was also
causing other issues on my system since for some reason
Public bug reported:
Running Ubuntu 19.10 and the chromium-browser
79.0.3945.79-0ubuntu0.19.10.2 package
I am unable to use my microphone with sites that support it, such as
discord.
I can hear audio from websites like Youtube, but sites that want to use
my microphone fail to do so, even though
Public bug reported:
I created an extensive report here:
https://gitlab.gnome.org/GNOME/mutter/issues/1087
Basically if you have a portrait mode monitor that has a larger vertical
resolution than the primary monitor, the primary monitor appears to
place the overview previews as if it had that
Wow. This is all remarkably chill for a bug that boils down to "Chrome
can't launch external apps". I just started a new job and I'm trying to
set up ubuntu 19.10 as my primary desktop and I'm being blocked by this.
Both slack and zoom fail to launch because of this. It also means that
apps
** Tags added: champagne
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1862028
Title:
Focal uses the exfat fuse filesystem even though there is support in
the kernel
To manage notifications
** Package changed: linux-5.4 (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/1864303
Title:
Removing the e1000e module causes a crash
To manage notifications about this
** Package changed: linux-meta-hwe (Ubuntu) => linux-hwe (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1862682
Title:
iSCSI-target: Deleting a LUN hangs in the kernel
To manage
If we think that single patch is a solution then can we get a test
kernel with that patch made available for confirmation and then get that
submitted so it can go into a official 20.04 kernel?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Public bug reported:
When a storage device formatted with exfat is automatically mounted on a
system it is mounted with a fuse filesystem instead of a native, kernel
filesystem. The kernel now has support for exfat.
** Affects: linux (Ubuntu)
Importance: Undecided
Status: New
**
1 - 100 of 93839 matches
Mail list logo