First of all, please show you are using ntfs-3g. In your syslog, you
should have something like :
Cmdline options: rw,permissions,umask=0022
Mount options: allow_other,default_permissions,subtype=ntfs-3g,rw,fsname= [...]
Are these followed by other errors ?
Then, problems have been
** Also affects: ubuntu-meta (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/2062557
Title:
[FFe] add trace-cmd to standand seed
To manage
** Also affects: ubuntu-meta (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/2062564
Title:
[FFe] Seed pemmican
To manage notifications about
I'm having the same problem, downloading and installing the
containernetworking-plugins provided by @alvinsj fixed it.
I'm guessing podman is not ready for production usage, will have to
revert to docker for our project.
--
You received this bug notification because you are a member of Ubuntu
** Description changed:
[context]
ADSys is a tool designed for administering and implementing Group Policy
Objects (GPOs) from Active Directory on Linux systems. It includes a suite of
services and commands that empower administrators to efficiently manage policy
updates and maintain
** Changed in: adsys (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/2059756
Title:
[SRU] adsys 0.14.1
To manage notifications about this bug go to:
Public bug reported:
[context]
ADSys is a tool designed for administering and implementing Group Policy
Objects (GPOs) from Active Directory on Linux systems. It includes a suite of
services and commands that empower administrators to efficiently manage policy
updates and maintain compliance
** Description changed:
[context]
ADSys is a tool designed for administering and implementing Group Policy
Objects (GPOs) from Active Directory on Linux systems. It includes a suite of
services and commands that empower administrators to efficiently manage policy
updates and maintain
** Description changed:
[context]
ADSys is a tool designed for administering and implementing Group Policy
Objects (GPOs) from Active Directory on Linux systems. It includes a suite of
services and commands that empower administrators to efficiently manage policy
updates and maintain
** Description changed:
[context]
ADSys is a tool designed for administering and implementing Group Policy
Objects (GPOs) from Active Directory on Linux systems. It includes a suite of
services and commands that empower administrators to efficiently manage policy
updates and maintain
** Changed in: adsys (Ubuntu)
Status: Confirmed => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2043376
Title:
adsys cant fetch gpos ubuntu 22.04.3
To manage notifications about
There is a passing run with samba/2:4.19.5+dfsg-1ubuntu1
This could be a flaky test on armhf. I'm closing this report for now and
will look further if it becomes a blocker on this arch in the futur.
** Changed in: adsys (Ubuntu)
Status: New => Won't Fix
--
You received this bug
** Changed in: adsys (Ubuntu)
Assignee: (unassigned) => Gabriel Nagy (gabuscus)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2055300
Title:
DEP8 failures in noble/armhf with samba 4.19.5
To
Public bug reported:
Ubuntu 22.04
logrotate 3.19.0-1ubuntu1.1
Every hour, I receive this wrong message:
Subject:Cron >cd / && run-parts --report
/etc/cron.hourly
/etc/cron.hourly/logrotate:
error: state file /var/lib/logrotate/status is world-readable and thus can be
locked from
Public bug reported:
?
ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: libinput-bin 1.15.5-1ubuntu0.3
ProcVersionSignature: Ubuntu 5.13.0-41.46~20.04.1-generic 5.13.19
Uname: Linux 5.13.0-41-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.24
AptOrdering:
thunderbird-locale-en:amd64:
It's a desktop package that we do not need on riscv64
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1929038
Title:
[SRU] Backport to 20.04 LTS
To manage notifications about this bug go to:
** Changed in: update-manager (Ubuntu)
Status: New => Triaged
** Changed in: update-manager (Ubuntu)
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/1958668
This has been verified a while ago and already deployed in production for
customers.
Marking as verification-done.
** Tags removed: removal-candidate verification-needed verification-needed-focal
** Tags added: verification-done verification-done-focal
--
You received this bug notification
Public bug reported:
No idea
ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: libinput-bin 1.15.5-1ubuntu0.3
ProcVersionSignature: Ubuntu 5.13.0-40.45~20.04.1-generic 5.13.19
Uname: Linux 5.13.0-40-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.23
AptOrdering:
libinput10:amd64:
@geole (post #82)
The file shown is "system compressed", which is the case for most
Windows 10 system files. You need the "system-compressed" plugin to read
it with ntfs-3g, and unfortunately Ubuntu has not packaged it yet.
You can get the source from :
steve - that's a fair point
pinging kernel
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1968612
Title:
Ubuntu 20.04 Cloud Image: missing nfsd.ko module in linux-kvm
To manage notifications about
closing this but please feel free to comment if you have additional
questions or concerns
** Changed in: cloud-images
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
indeed, this image has a minimal kernel
you can either install the generic kernel, or use the full ubuntu server image
which contains the generic kernel, which will have the necessary support
** Also affects: cloud-images
Importance: Undecided
Status: New
** Changed in: linux-meta-kvm
> Same problème with 22.04 Beta Jammy
Which one ?
Your attachment is missing.
Please post the output of the commands described at the bottom of
https://github.com/tuxera/ntfs-3g/wiki/Junctions-Points,-Symbolic-Links-and-Reparse-Points#other-types-of-reparse-points
--
You received this bug
** Also affects: cloud-images
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/1941785
Title:
ec2-hibinit-agent: Add support for IMDSv2
To manage
Public bug reported:
Zsys is in very low maintenance mode (critical bug fixes only) and must be
removed from the LTS.
However ZFS and encrypted ZFS are still available as an installation option but
the package ZSys is not installed.
The ZFS layout remains unchanged.
** Changed in: zsys (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/1967585
Title:
Failed to start ZSYS daemon service (panic: runtime error)
To
A pool compatibility property has been added to ZFS 2.1 but not to the
go binding.
** Changed in: zsys (Ubuntu)
Status: Confirmed => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Summary changed:
- Jammy fails to boot to live session
+ Jammy fails to boot to live session in virt-manager with QXL
** Description changed:
Ubuntu Desktop Jammy 20220405
It fails to boot to the live session in virt-manager and gnome-boxes.
ubiquity-dm starts fine but the live
** Attachment added: "_usr_lib_xorg_Xorg.0.crash"
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1967901/+attachment/5577348/+files/_usr_lib_xorg_Xorg.0.crash
** Description changed:
Ubuntu Desktop Jammy 20220405
It fails to boot to the live session in virt-manager and
** Attachment added: "_usr_bin_gnome-shell.999.crash"
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1967901/+attachment/5577347/+files/_usr_bin_gnome-shell.999.crash
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Attachment added: "journal.log"
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1967901/+attachment/5577346/+files/journal.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1967901
** Attachment added: "debug"
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1967901/+attachment/5577344/+files/debug
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1967901
Title:
Jammy
** Attachment added: "dm"
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1967901/+attachment/5577345/+files/dm
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1967901
Title:
Jammy fails
Public bug reported:
Ubuntu Desktop Jammy 20220405
It fails to boot to the live session in virt-manager and gnome-boxes.
ubiquity-dm starts fine but the live session does. The graphical session keeps
dying. There are crashes of gnome-shell and xorg in /var/crash.
From the journal
avril 05
*** This bug is a duplicate of bug 1967585 ***
https://bugs.launchpad.net/bugs/1967585
** This bug has been marked a duplicate of bug 1967585
Failed to start ZSYS daemon service (panic: runtime error)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
ntu)
Importance: Undecided => Critical
** Changed in: zsys (Ubuntu)
Assignee: (unassigned) => Jean-Baptiste Lallement (jibel)
** Changed in: zsys (Ubuntu)
Milestone: None => ubuntu-22.04
--
You received this bug notification because you are a member of Ubuntu
Bugs, which i
I confirm that adding XB-Task addresses the issue and the package from
the PPA is installed. However, when there is no task defined, the
package from archive should be installed.
** Changed in: livecd-rootfs (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because
Public bug reported:
On an up to date Jammy machine, printing fails and there is the
following apparmor denied message in the journal:
apparmor="DENIED" operation="connect" profile="/usr/sbin/cupsd"
name="/run/systemd/userdb/io.systemd.Machine" pid=892182 comm="cupsd"
requested_mask="w"
** Description changed:
[Availability]
Available on all archs, available starting hirsute. It will be
backported to Focal once an FFe has been accepted.
[Rationale]
We are supporting GPO Active Directory support on ubuntu starting
hirsute. This features allows for an
Public bug reported:
Jammy / software-properties-gtk:
Installed: 0.99.17
When trying to enable a service that is not available the error message
provide no useful information about what went wrong (cf screenshot)
and in the journal:
ubuntu-advantag[1461382]: Failed to parse UA status:
Public bug reported:
On WSL, at the end of a do-release-upgrade, the upgrader proposes to
reboot the machine. Although on WSL it is not possible to reboot due to
the lack of systemd and it ends with an error.
The message at the end should be different if it is running on a system
where systemd
Public bug reported:
After the kernel release 5.13.0-27-generic was installed today, the startup and
shutdown processes finish with white noise screens.
The workaround at startup is to disable "quiet" in /etc/default/grub, variable
GRUB_CMDLINE_LINUX_DEFAULT.
** Description changed:
With systemd v245 as shipped with 20.04, the shutdown sequence does not
use the value of `DefaultTimeoutStopSec` to wait for remaining
processes, it instead uses the compiled in default of 90s.
This is most visible with services that use `KillMode=process`
Public bug reported:
With systemd v245 as shipped with 20.04, the shutdown sequence does not
use the value of `DefaultTimeoutStopSec` to wait for remaining
processes, it instead uses the compiled in default of 90s.
This is most visible with services that use `KillMode=process` (docker,
k8s, k3s,
Nothing to be worried about, this is not a bug and the message is just a
technical warning. The chkdsk conclusion is "Windows has scanned the
file system and found no problems."
Since about 2016, Windows allocates space by chunks of multiple
clusters, but it still correctly processes files
Hi everyone,
small progress report :
I tried the pipewire trick and it didn't work out for me, while it initially
seemed to work: auto switch to the HSP/HPF profile didn't work and after a
manual switch the headset would drop out during a conversation.
I reverted to pulseaudio and invested a
log.000107', 'mysql_upgrade_info', 'binlog.000098',
'jean-desktop.pid', 'binlog.index', 'public_key.pem', 'binlog.000108',
'binlog.99', 'undo_002', 'mysql', 'undo_001', 'server-cert.pem',
'#innodb_temp', 'ca.pem', 'ca-key.pem', 'binlog.000106', 'server-key.pem',
'#ib_16384_0.dblwr', 'performance_schema
Do the following :
sudo mousepad /etc/NetworkManager/NetworkManager.conf
and change :
[ifupdown]
managed=true
The default value is false, but it seems that if when the system starts the
network is not yet ready the applet will not be displayed
if you set the value to true, it solves the
Good. I woke up the laptop after leaving it hooked to the docking and in
sleep the whole night, no issues.
I consider it resolved. Thanks.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1944409
After first reboot with BIOS 1.12.2 all seems fine, the update seems
even to have made the process of hooking up the docking station and
activating the external monitors faster.
After first sleep and wakeup, no battery pinging that I can see with
udevadm monitor, not even at a slow pace (but the
#7 output was already attached there, just grepped for brevity. The
first lines where confusing me though, I've now upgraded the system BIOS
from 1.6.1 to 1.12.2. 1.13 seems available on the official site, I'll
report back ASAP on the results of the upgrade.
--
You received this bug notification
Do you have more than 100 files remembered in session file? We
supposedly have fixed this in 2.3.4, if this is the bug I have in mind.
Are other parameters of session (e.g. window size), correctly
remembered?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
I don't have any BIOS update available; as I said, my laptop (Dell
Latitude 7520) is fully updated.
$ sudo dmidecode -s bios-version
1.6.1
$ fwupdmgr get-updates | grep "Current version" -B2
Devices with no available firmware updates:
• UEFI Device Firmware
• UEFI Device Firmware
• UEFI dbx
No, no workaround. I still have to do the restart at every reboot with
the docking station attached.
My system is fully updated up to yesterday:
$ uname -a
Linux CLIFMI085 5.13.0-1021-oem #25-Ubuntu SMP Thu Dec 2 18:03:51 UTC 2021
x86_64 x86_64 x86_64 GNU/Linux
--
You received this bug
** Changed in: cloud-images
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/1870189
Title:
initramfs does not get loaded
To manage notifications about this
Per coincidence, I worked on this same bug today, as I'm hoping to try
make use of the amdpro legacy OpenCL drivers, which will need amdgpu as
a base.
The issue is Ubuntu is providing newer kernel HWE stacks with amdgpu
driver modules, but failing to keep related Linux firmware packages up
to
Yes, it works perfectly with Xorg.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1952999
Title:
Wayland blocks the microphone of the webcam
To manage notifications about this bug go to:
Public bug reported:
Jammy daily
In the wayland session the microphone of the webcam is no available.
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: libwayland-bin 1.19.0-2build1
ProcVersionSignature: Ubuntu 5.13.0-20.20-generic 5.13.14
Uname: Linux 5.13.0-20-generic x86_64
There is no crash and this is on hardware.
** Tags added: rls-jj-incoming
** Attachment added: "journal.txt.gz"
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1952457/+attachment/5544826/+files/journal.txt.gz
** Changed in: gdm3 (Ubuntu)
Status: Incomplete => Confirmed
**
** Attachment added: "journal.txt.gz"
https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1952930/+attachment/5544680/+files/journal.txt.gz
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
Jammy daily.
*Test Case*
1. Boot to GDM
2. Select an Xorg Session
3. Login
4. Verify that Xorg is running
5. Reboot the machine
6. Check that Xorg session is still selected
7. Login
8. Verify that Xorg is running
*Actual result*
Wayland is running despite Xorg was
** Changed in: cloud-images
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/1580596
Title:
Xenial & bionic vagrant box disk size is too small
To manage
Verification
Mesa 21.0.3-0ubuntu0.3~20.04.4 has been tested on 2 systems and it fixes
the issue. Marking as verification-done.
** Tags removed: verification-needed verification-needed-focal
** Tags added: verification-done verification-done-focal
--
You received this bug notification because
** Changed in: mesa (Ubuntu Focal)
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/1950174
Title:
[SRU] focal: gallium: Reset {d,r}Priv in dri_unbind_context
To
** Description changed:
[Description]
This is a request to backport this fix from mesa 21.1 to focal-updates which
is affecting users of WSL:
https://gitlab.freedesktop.org/mesa/mesa/-/commit/7ff30a0499bd872d77b0f377414bbc03463b9f87
This cached stale pointer is causing various
** Description changed:
[Description]
This is a request to backport this fix from mesa 21.1 to focal-updates which
is affecting users of WSL:
https://gitlab.freedesktop.org/mesa/mesa/-/commit/7ff30a0499bd872d77b0f377414bbc03463b9f87
This cached stale pointer is causing various
** Description changed:
[Description]
This is a request to backport this fix from mesa 21.1 to focal-updates which
is affecting users of WSL:
https://gitlab.freedesktop.org/mesa/mesa/-/commit/7ff30a0499bd872d77b0f377414bbc03463b9f87
This cached stale pointer is causing various
** 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/1950381
Title:
Adding landlock to CONFIG_LSM in 5.13 kernels
To manage
Public bug reported:
Since Landlock[1] is enabled in ubuntu 5.13 kernels[2], I wonder if it
should be added to CONFIG_LSM[3] so that the feature is usable without
having to override the lsm parameter on the kernel command line (and
reboot).
Upstream seems to have it enabled since it was merged
** Description changed:
[Description]
This is a request to backport this fix from mesa 21.1 to focal-updates which
is affecting users of WSL:
https://gitlab.freedesktop.org/mesa/mesa/-/commit/7ff30a0499bd872d77b0f377414bbc03463b9f87
This cached stale pointer is causing various
Public bug reported:
[Description]
This is a request to backport this fix from mesa 21.1 to focal-updates which is
affecting users of WSL:
https://gitlab.freedesktop.org/mesa/mesa/-/commit/7ff30a0499bd872d77b0f377414bbc03463b9f87
This cached stale pointer is causing various chromium
The workaround worked for me but not with the Ubuntu 21.10, I tried
# cd /usr/lib
# sudo ln -s pulse-15.0+dfsg1/ pulse-13.99
But I still have the error
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I see nothing wrong in these file systems. Only the first one has only
0.16% space left (which is 1.6GB), and probably not shrunkable. As you
were able to extract the metadata, all the file systems are proven to be
at least mountable read-only.
--
You received this bug notification because you
When started with option -i, ntfsresize only evaluates the minimal size
needed for the stored data. There may be a subsequent ntfsresize to
actually do some resizing, which might not be run when you kill the
parent process.
--
You received this bug notification because you are a member of Ubuntu
Please report what is hinting at ntfsresize and in what conditions it is
started (such as the file system state) ?
Also please start ntfsresize from command line.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
1) what are the ntfsresize options ?
2) what are the file system metadata (given by "ntfsinfo -fm device-path"
before resizing)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1945011
Title:
kernel
Hello Konstantin,
I see that I never followed up on this bug. Does it still affect you?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1815278
Title:
LyX restores the same cursor position wherever
Public bug reported:
the error window appears when loading the desktop
ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: grub2-common 2.04-1ubuntu26.13
ProcVersionSignature: Ubuntu 5.11.0-38.42~20.04.1-generic 5.11.22
Uname: Linux 5.11.0-38-generic x86_64
ApportVersion:
Same issue for me using latest stable NVidia drivers on 20.04 with
latest 7.2 Libre office snap.
I've noticed that only Calc is affected. Impress and Writer are not
affected.
So there must be some calc specific graphics acceleration method causing
high CPU rendering load.
Unlike the orig bug
@suntao : Did you try the OneDrive plugin from https://jp-
andre.pagesperso-orange.fr/junctions.html#other ?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1728354
Title:
ntfs: unsupported reparse
I seem to have the same issue:
```
histausse@hindley:~$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 20.04.3 LTS
Release:20.04
Codename: focal
histausse@hindley:~$ sudo dpkg -l | grep apt-cacher
ii apt-cacher-ng 3.3.1-2build1
** Changed in: ubuntu-release-upgrader (Ubuntu Hirsute)
Status: Confirmed => Won't Fix
** Changed in: ubuntu-release-upgrader (Ubuntu Impish)
Status: Confirmed => Triaged
** Changed in: ubuntu-release-upgrader (Ubuntu Impish)
Importance: Undecided => High
--
You received this
I've this issue too. What else do you need than @Mario's journal?
** Changed in: gdm3 (Ubuntu)
Status: New => Confirmed
** Changed in: gdm3 (Ubuntu)
Importance: Undecided => High
** Also affects: gdm3 (Ubuntu Impish)
Importance: High
Status: Confirmed
--
You received this
There is also an additional requirement. The package must install
successfully and replace an existing file that would have been created
manually (we had to ship the file on the image for the customer since we
don't have this fix in a package yet)
--
You received this bug notification because
IMHO having the fix in network-dispatcher makes more sense.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1933828
Title:
NTP servers from DHCP are not propagated to timesyncd
To manage
@Seb this fix has to go to focal for a customer project and must land in
the dev release first.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1933828
Title:
NTP servers from DHCP are not propagated
Public bug reported:
The patches introduced for CVE-2021-40438 break existing configs.
For example on Plesk:
https://support.plesk.com/hc/en-us/articles/4407366133906-Website-suddenly-started-to-show-500-error-AH10292-Invalid-proxy-UDS-filename
Upstream pushed some additional fixes for it:
Public bug reported:
My setup:
- Dell Latitude 7520
- Dell WD15 USB C docking station
- Ubuntu 20.04.3
- systemd 245.4-4ubuntu3.13
- uname -a:
Linux CLIFMI085 5.13.0-1012-oem #16-Ubuntu SMP Tue Sep 7 09:23:08 UTC 2021
x86_64 x86_64 x86_64 GNU/Linux
I leave my laptop docked and, after
The server is set via a configuration file. The default config file is
/etc/systemd/timesyncd.conf and it can be overridden by dropping files in
/etc/systemd/timesyncd.conf.d/.
There is a pool of free ntp servers available on https://www.ntppool.org/en/.
To test this fix you also need a DHCP
Closing, as I discovered that the root cause was interference from my
antivirus (Sophos).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1943421
Title:
Error while enabling somerville driver:
** Changed in: linux-oem-5.13 (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/1943421
Title:
Error while enabling somerville driver: package linux-
Public bug reported:
I'm trying to install Ubuntu 20.04.3 on a brand new Dell 7520, which is
equipped with:
* 11th Gen Intel® Core™ i7-1185G7 @ 3.00GHz × 8
* Intel Iris XE GPU (reported as Mesa Intel® Xe Graphics (TGL GT2))
Since on my first try I was getting a lot of SEGFAULTS, I repeated
reboot/shutdown hangs my two odroid-HC4 with kernel
5.13.12-202108261237~focal (2021-08-26)
** Also affects: ubuntu
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
On first boot the spread view shows the first boot wizard and it looks
really weird. Moreover if you click on the right workspace the wizard is
not displayed.
The spread view should be disabled and the wizard should be displayed
full screen immediately.
ProblemType: Bug
** Also affects: network-manager (Ubuntu Focal)
Importance: Undecided
Status: New
** Changed in: network-manager (Ubuntu Focal)
Importance: Undecided => High
** Changed in: network-manager (Ubuntu Focal)
Assignee: (unassigned) => Heather Ellsworth (hellsworth)
--
You received
** Package changed: ubiquity (Ubuntu) => ubuntu
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1940826
Title:
customisation steps do not work for 20.04
To manage notifications about this bug go to:
Public bug reported:
This is a test
** Affects: ubuntu
Importance: Undecided
Status: Invalid
** Changed in: ubuntu
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Thanks for your report.
Could you please describe your testing environment (VM vs HW, HW
configuration, ...)
** Changed in: gnome-shell (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Tags added: rls-ii-incoming
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1933828
Title:
NTP servers from DHCP are not propagated to timesyncd
To manage notifications about this bug go to:
1 - 100 of 39077 matches
Mail list logo
