*** This bug is a duplicate of bug 1766108 ***
https://bugs.launchpad.net/bugs/1766108
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: ayatana-indicator-application (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: ayatana-indicator-power (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
*** This bug is a duplicate of bug 1766108 ***
https://bugs.launchpad.net/bugs/1766108
** This bug has been marked a duplicate of bug 1766108
Battery indicator crashes when unchecking "Show Percentage in Menu Bar"
--
You received this bug notification because you are a member of Ubuntu
Please try 20.04...
Radeon support is much better in newer release.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1830560
Title:
suspend
To manage notifications about this bug go to:
[39.611] (II) AIGLX: Screen 0 is not DRI2 capable
[39.611] (EE) AIGLX: reverting to software rendering
16.04 is just old and you're not getting any (gfx) updates there anymore
at this point
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Public bug reported:
When I command 'sudo apt upgrade', the progress bar stopped at 91%.
A kworker related to grub consumed 100% CPU. (It uses only one CPU. The others
were idle.)
Dmesg message had error about watchdog and it occurred repeatedly.
ProblemType: Package
DistroRelease: Ubuntu
No they're not really. That's just recovery mode, required to log 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/1901342
Title:
Xorg sessions fail to start on Intel Core 2 T5800:
All autopkgtests for the newly accepted alsa-lib (1.2.2-2.1ubuntu2.1) for focal
have finished running.
The following regressions have been reported in tests triggered by the package:
asterisk/1:16.2.1~dfsg-2ubuntu1 (armhf)
Please visit the excuses page listed below and investigate the
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/1901798
Title:
Wireless-9560 limit speed
To manage
** Tags added: xrandr-scaling
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1868207
Title:
Fractional scaling window sizes incorrect after resume from suspend
To manage notifications about this
Please run this command to send us more information about the machine:
apport-collect 1870886
** Tags added: groovy
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1870886
Title:
Window scales to
Still reproducible on Groovy.
It's not a laptop, it's a desktop with single monitor.
Both AMD and Intel GFX have this issue.
** This bug is no longer a duplicate of bug 1868207
Fractional scaling window sizes incorrect after resume from suspend
** Summary changed:
- Window scales to 200%
Public bug reported:
I am having wifi throughput issues.
all other devices that connected to my wireless are getting 150 - 200+ Mbps
download speed.
I have an HP OMEN gaming laptop that cannot get pass 80mbps to download speed.
Can you help me out with how to report this?
ProblemType: Bug
you're using 'nomodeset' boot option which disables things, don't do
that
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1901342
Title:
Xorg sessions fail to start on Intel Core 2 T5800: modeset(0):
Public bug reported:
The upgrade fails at new software channel's stage. It states that
ubuntu-minimal cannot be located.
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: ubuntu-release-upgrader-core 1:20.04.8
ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8
Uname: Linux
** Changed in: gnome-shell (Ubuntu)
Status: Expired => Incomplete
** Changed in: gnome-shell (Ubuntu)
Assignee: (unassigned) => Daniel van Vugt (vanvugt)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
That means the bluetooth controller really wakes up after started a
scanning.
Recent BT 4.0 controllers from Intel or Qualcomm shouldn't have this
bug.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Thank you for taking the time to report this bug and helping to make
Ubuntu better. Reviewing your log files attached to this bug report it
seems that there is a problem with your installation media (CD/DVD).
You can verify the integrity of the Ubuntu ISO files you downloaded by
following the
The attachment "latex_breqn_fix.patch" seems to be a patch. If it
isn't, please remove the "patch" flag from the attachment, remove the
"patch" tag, and if you are a member of the ~ubuntu-reviewers,
unsubscribe the team.
[This is an automated message performed by a Launchpad user owned by
** Description changed:
[Impact]
- * An upstream change in libvirt 6.6 [1] broke logic if creating a pool
-without an explicit yes/now for COW handling.
+ * An upstream change in libvirt 6.6 [1] broke the logic of creating a
+pool without an explicit yes/no for COW handling.
-
[Expired for ubuntu-docs (Ubuntu) because there has been no activity for
60 days.]
** Changed in: ubuntu-docs (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
[Expired for ubiquity (Ubuntu) because there has been no activity for 60
days.]
** Changed in: ubiquity (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
[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.
[Expired for networkd-dispatcher (Ubuntu) because there has been no
activity for 60 days.]
** Changed in: networkd-dispatcher (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Still broken in 5.8.0-26-generic
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1896091
Title:
[i915] Noise-like lines of graphics corruption when moving windows in
Xorg sessions
To manage
It exists in queue
https://launchpad.net/ubuntu/focal/+queue?queue_state=1_text=network,
which is network manager 1.22.10-1ubuntu2.2.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1891632
Title:
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: linux-firmware (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/1893538
@Marco,
What the bluetooth module on your machine? Could you please upload the
vendor ID:device ID like #49?
thx.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1871794
Title:
[Bluetooth] No audio
thunderbird running fine on my ubuntu 20.10! someone else said not
running fine on 20.10 ubuntu mate ...
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1901778
Title:
Thunderbird crashes on start up
There seems to be at least one security issue with the current version
of Python 3.8 in Bionic, which is still 3.8.0.
See: What’s New In Python 3.8 — Python 3.8.6 documentation
https://docs.python.org/release/3.8.6/whatsnew/3.8.html
I.e.: Notable changes in Python 3.8.1
Due to significant
Indeed, declaring that a leading minus sign is "wrong", and parentheses
are "right", for the US locale, is not supported by common usage. Both
are widely used in different contexts, and Ubuntu does not deviate from
the upstream behavior.
We are also certainly not going to change the behavior on
^^^
Is that failure reproducible? And if so, would it not be more related to the
fix for bug 1880250?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1872159
Title:
Boot animation never finishes,
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: python3.6 (Ubuntu Bionic)
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/1866859
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: python3.6 (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/1866859
Title:
Public bug reported:
no idea
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: ubuntu-release-upgrader-core 1:18.04.40
ProcVersionSignature: Ubuntu 4.15.0-122.124-generic 4.15.18
Uname: Linux 4.15.0-122-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.18
Architecture: amd64
CrashDB: ubuntu
The verification of the Stable Release Update for v4l2loopback has
completed successfully and the package is now being released to
-updates. Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you
^^^
Perhaps that systemd test only used to work because it has:
FSCKD_TIMEOUT = 30
which was much bigger than 2 seconds. Now that plymouth also uses 30
seconds, the systemd test might not be reliable and may need its timeout
increased.
If the failure continues to happen after a retry then I
I have this bug in 20.10 (upgraded from 20.04). On shutdown it always
waits for 90 seconds, then it times out and the shutdown proceeds
normally. I have the same log as in:
https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1873550/comments/3
--
You received this bug notification because you
Public bug reported:
[Feature Description]
Running “perf c2c” on ICX always leads to Segment Fault, while same
command works fine on CLX, as attached screenshots show with 5.8-rc6
upstream kernel.
Commit Ids:
1101c872c8c7869c78dc106ae820040f36807eda (v5.9)
Target Kernel: 5.9
Target Release:
Realtek's firmware was approved by upstream at
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-
firmware.git/commit/?id=09e8cfffdecc1f373a82e9456c6cd8810a831288
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
[Feature Description]
enable the feature of SST in kernel config
CONFIG_INTEL_SPEED_SELECT_INTERFACE
Target Release: 20.10
[HW/SW Information]
IceLake Server
[Business Justification]
Function enabling
** Affects: intel
Importance: Undecided
Status: New
**
This sounds like either bug 1896110 or bug 1874578. Do you think?
** Summary changed:
- Xorg freeze
+ Freeze
** Package changed: xorg (Ubuntu) => gnome-shell-extension-ubuntu-dock
(Ubuntu)
** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu)
Status: New => Incomplete
--
You
I have resolve the bug, but testing and releasing is necessary.
In a nutshell, the issue is caused by a clash of macro definitions
between `breqn` and `amsmath`.
According to http://mirror.physik-pool.tu-
berlin.de/pub/CTAN/macros/latex/contrib/breqn/breqn.pdf, Sec. 2 (package
loading), a
Hi Colin, thanks so much for giving this another look. I don't see any
references to trying different zfs_arc_meta_limit* settings here!
I raised zfs_arc_meta_limit_percent from the default 75 to 95 and my
system has been running this ripgrep for four hours without falling to
pieces.
I think we
OK, clarified somewhat now. This bug is back to being about just "no
screens found".
** Summary changed:
- Xorg crashed with SIGABRT in OsAbort() from AbortServer() from FatalError()
from dix_main()
+ Xorg crashed with SIGABRT in OsAbort() from AbortServer() from FatalError("no
screens found")
** Summary changed:
- Xorg crashed with SIGABRT in OsAbort() from AbortServer() from
FatalError("EnterVT failed for screen ...") from xf86VTEnter() from
systemd_logind_vtenter()
+ Xorg crashed with SIGABRT in OsAbort() from AbortServer() from
FatalError("EnterVT failed for screen %d\n") from
It looks like bug 1897530 might cover this but it's unclear. The fix for
that is only in Ubuntu 20.10 so far.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1791981
Title:
[nvidia] X Server session
I can't see any evidence of which Xorg crash this is.
** This bug is no longer a duplicate of bug 1543192
Xorg crashed with SIGABRT in OsAbort() from AbortServer() from FatalError()
from dix_main()
** Changed in: xorg-server (Ubuntu)
Status: New => Incomplete
--
You received this
There's not enough information here to tell which FatalError this is.
** This bug is no longer a duplicate of bug 1543192
Xorg crashed with SIGABRT in OsAbort() from AbortServer() from FatalError()
from dix_main()
** Changed in: xorg-server (Ubuntu)
Status: New => Incomplete
--
You
There's not enough information here to tell which FatalError this is.
** This bug is no longer a duplicate of bug 1543192
Xorg crashed with SIGABRT in OsAbort() from AbortServer() from FatalError()
from dix_main()
** Changed in: xorg-server (Ubuntu)
Status: New => Incomplete
--
You
*** This bug is a duplicate of bug 1543192 ***
https://bugs.launchpad.net/bugs/1543192
** Summary changed:
- Xorg crashed with SIGABRT in OsAbort()
+ Xorg crashed with SIGABRT in OsAbort() from ?? from FatalError("no screens
found")
--
You received this bug notification because you are a
I can't tell *which* FatalError this is.
** This bug is no longer a duplicate of bug 1543192
Xorg crashed with SIGABRT in OsAbort() from AbortServer() from FatalError()
from dix_main()
** Changed in: xorg-server (Ubuntu)
Status: New => Incomplete
--
You received this bug
Public bug reported:
crash during os install. Not sure what else to say. email me with
specific questions, and I'll answer. Thanks!!
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: ubiquity 20.04.15
ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
Uname: Linux 5.4.0-26-generic
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 1889637
and then change the status of the bug to 'Confirmed'.
If, due to the
I think this is the wrong bug for all of those duplicates. There's no
evidence of either of those messages here. I'll see if I can split this
into other bugs...
** Summary changed:
- Xorg crashed with SIGABRT in OsAbort() from AbortServer() from
FatalError("EnterVT failed for gpu screen %d\n")
*** This bug is a duplicate of bug 1813897 ***
https://bugs.launchpad.net/bugs/1813897
** This bug is no longer a duplicate of bug 1543192
Xorg crashed with SIGABRT in OsAbort() from AbortServer() from FatalError()
from dix_main()
** Summary changed:
- Xorg crashed with SIGABRT in
Thank you for reporting this bug to Ubuntu.
Ubuntu GNOME 14.04 (trusty) reached end-of-life on April 28, 2017
https://wiki.ubuntu.com/TrustyTahr/ReleaseNotes/UbuntuGNOME#Support
https://lists.ubuntu.com/archives/ubuntu-gnome/2017-March/004211.html
We appreciate that this bug may be old and you
Ubuntu 14.04 reached end of standard support in April 2019:
https://wiki.ubuntu.com/Releases
If you would like to continue with free support then please update to a
newer Ubuntu version and tell us if the problem still occurs.
If you would like to continue with Ubuntu 14.04 then there is a
Public bug reported:
What happened:
===
I'm using iBus as input "method" with
- Japanese (Anthy) // primary
- German
set up.
I upgraded from ubuntu 20.04 to 20.10.
EXPECTED: No changes regarding input.
ACTUAL: German input method was removed
lsb_release -rd
===
** Summary changed:
- X Server session crash for "No space left on device"
+ X Server session crash with "No space left on device" and then "EnterVT
failed for gpu screen 0"
** Summary changed:
- X Server session crash with "No space left on device" and then "EnterVT
failed for gpu screen 0"
*** This bug is a duplicate of bug 1791981 ***
https://bugs.launchpad.net/bugs/1791981
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 1791981, so it is being marked as such. Please
I spoke too soon. Deep sleep works now, and the touchpad keeps working,
but only - even with the new motherboard - if I keep the NFC *enabled*
in the BIOS. And the trackpoint does not work under Linux. At all. At
any time (at least on my distro) and even with a very recent kernel.
--
You
It appears the Xorg radeon driver is working. It's only 3D that's not
working so that's Mesa.
** Summary changed:
- No hardware aceleration
+ [radeon] No hardware aceleration
** Summary changed:
- [radeon] No hardware aceleration
+ [radeon] No hardware acceleration
** Tags added: radeon
**
** Package changed: 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/1889637
Title:
Raspberry Pi 3B hangs - dev_pm_opp_set_rate: failed to find current
OPP, Failed to get
This change was made by a bot.
** Changed in: linux (Ubuntu)
Status: New => Confirmed
** Tags added: focal
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1901413
Title:
Sound Blaster Audigy
Yep, the detailed mode 2560x1440 is in the EDID returned by the monitor:
Standard Timings: none
Detailed mode: Clock 241.500 MHz, 598 mm x 336 mm
2560 2608 2640 2720 ( 48 32 80)
1440 1443 1448 1481 ( 3 5 33)
+hsync -vsync
VertFreq:
No problem. If there are no more comments after 60 days then the bug
will close automatically.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1901538
Title:
Output Device selection messed (Line Out
I thought gnome-shell started its own agent for ssh on startup? Or did
you configure your system to run the gnupg agent before starting gnome?
Thanks
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Hi Alex,
my problem came back. Is it possible that livepatch has replaced my
working kernel with the broken one again? --Jim
On Thu, 24 Sep 2020, Alex Hung wrote:
> A test kernel with target patches ready for SRU is available @
> https://people.canonical.com/~alexhung/LP1896482/fixes/
>
>
I would like to check to see if the problem is occurring in the kernel
and not just in Xorg. Please run:
grep . /sys/class/drm/*/modes > modes.txt
and then attach the resulting text file here.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
All autopkgtests for the newly accepted qemu (1:2.11+dfsg-1ubuntu7.33) for
bionic have finished running.
The following regressions have been reported in tests triggered by the package:
libvirt/4.0.0-1ubuntu8.17 (i386)
systemd/237-3ubuntu10.42 (ppc64el)
Please visit the excuses page listed
All autopkgtests for the newly accepted systemd (245.4-4ubuntu3.3) for focal
have finished running.
The following regressions have been reported in tests triggered by the package:
linux-hwe-5.8/5.8.0-25.26~20.04.1 (armhf)
python-dbusmock/0.19-1 (armhf)
lxc/1:4.0.2-0ubuntu1 (amd64)
Please visit
All autopkgtests for the newly accepted systemd (245.4-4ubuntu3.3) for focal
have finished running.
The following regressions have been reported in tests triggered by the package:
linux-hwe-5.8/5.8.0-25.26~20.04.1 (armhf)
python-dbusmock/0.19-1 (armhf)
lxc/1:4.0.2-0ubuntu1 (amd64)
Please visit
All autopkgtests for the newly accepted systemd (245.4-4ubuntu3.3) for focal
have finished running.
The following regressions have been reported in tests triggered by the package:
linux-hwe-5.8/5.8.0-25.26~20.04.1 (armhf)
python-dbusmock/0.19-1 (armhf)
lxc/1:4.0.2-0ubuntu1 (amd64)
Please visit
** Changed in: linux (Ubuntu)
Status: Incomplete => New
** Changed in: pulseaudio (Ubuntu)
Status: Incomplete => New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1901413
Title:
All autopkgtests for the newly accepted systemd (245.4-4ubuntu3.3) for focal
have finished running.
The following regressions have been reported in tests triggered by the package:
linux-hwe-5.8/5.8.0-25.26~20.04.1 (armhf)
python-dbusmock/0.19-1 (armhf)
lxc/1:4.0.2-0ubuntu1 (amd64)
Please visit
*** This bug is a duplicate of bug 1872950 ***
https://bugs.launchpad.net/bugs/1872950
** This bug has been marked a duplicate of bug 1872950
Nvidia 340.108 fails to install with kernels 5.5 onward
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
All autopkgtests for the newly accepted systemd (245.4-4ubuntu3.3) for focal
have finished running.
The following regressions have been reported in tests triggered by the package:
linux-hwe-5.8/5.8.0-25.26~20.04.1 (armhf)
python-dbusmock/0.19-1 (armhf)
lxc/1:4.0.2-0ubuntu1 (amd64)
Please visit
** Summary changed:
- Nvidia 340.108 fails to install with kernels 5.5 and 5.6
+ Nvidia 340.108 fails to install with kernels 5.5 onward
** Changed in: nvidia-graphics-drivers-340 (Ubuntu)
Importance: Undecided => High
** Tags added: focal groovy
** Tags removed: focal
** Tags added:
** Changed in: gdm3 (Ubuntu)
Status: Incomplete => New
** Changed in: mutter (Ubuntu)
Status: Incomplete => New
** Changed in: xorg-server (Ubuntu)
Status: Incomplete => New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
The fix was written by upstream, and the downstream fix is being
packaged by Marco. So I'm not involved in either of those.
** Changed in: mutter (Ubuntu)
Status: In Progress => Fix Committed
** Changed in: mutter (Ubuntu)
Assignee: Daniel van Vugt (vanvugt) => (unassigned)
**
This bug was fixed in the package clevis - 12-1ubuntu2.2
---
clevis (12-1ubuntu2.2) focal; urgency=medium
* initramfs: Fix parsing of interface names when bringing the network
back down in local-bottom, which also avoids a mess of "ip: can't find
device
This bug was fixed in the package clevis - 12-1ubuntu2.2
---
clevis (12-1ubuntu2.2) focal; urgency=medium
* initramfs: Fix parsing of interface names when bringing the network
back down in local-bottom, which also avoids a mess of "ip: can't find
device
This bug was fixed in the package clevis - 12-1ubuntu2.2
---
clevis (12-1ubuntu2.2) focal; urgency=medium
* initramfs: Fix parsing of interface names when bringing the network
back down in local-bottom, which also avoids a mess of "ip: can't find
device
This bug was fixed in the package clevis - 12-1ubuntu2.2
---
clevis (12-1ubuntu2.2) focal; urgency=medium
* initramfs: Fix parsing of interface names when bringing the network
back down in local-bottom, which also avoids a mess of "ip: can't find
device
This bug was fixed in the package clevis - 12-1ubuntu2.2
---
clevis (12-1ubuntu2.2) focal; urgency=medium
* initramfs: Fix parsing of interface names when bringing the network
back down in local-bottom, which also avoids a mess of "ip: can't find
device
^^^
I am skeptical that's a real failure. Can someone hit retry?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1872159
Title:
Boot animation never finishes, especially when external monitors (or
Please don't discuss that here. You should open a new bug by running:
ubuntu-bug linux
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1894627
Title:
[nvidia] Web browser distorted after
** No longer affects: xorg-server (Ubuntu)
--
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 flickering and [drm:intel_cpu_fifo_underrun_irq_handler
[i915]] *ERROR* CPU
i just had a bug for 20.10 merged into this one. note that in my case,
this just started happening since upgrading to 20.10, and it happens
with multiple different brands of bluetooth adaptor. as well, if use my
keyboard to open the bluetooth settings panel in gnome, then everything
immediately
The verification of the Stable Release Update for clevis has completed
successfully and the package is now being released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you encounter a
The verification of the Stable Release Update for clevis has completed
successfully and the package is now being released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you encounter a
The verification of the Stable Release Update for clevis has completed
successfully and the package is now being released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you encounter a
This bug is closed. Please open a new bug if you have any problems.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1812430
Title:
intel hd 500 - j3455 no graphic driver
To manage notifications
The verification of the Stable Release Update for clevis has completed
successfully and the package is now being released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you encounter a
The verification of the Stable Release Update for clevis has completed
successfully and the package is now being released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you encounter a
I'm using Acer Swift SF514-52T (Intel 8th Gen Core i5) on Ubuntu 20.10 -
Linux kernel 5.8.
The default configuration has no sound working at all. I believe it uses
the SOF driver (I could be wrong) which doesn't support the Kaby Lake
platform, as the issues for supporting this platform have been
This bug was fixed in the package clevis - 8-1ubuntu0.2
---
clevis (8-1ubuntu0.2) bionic; urgency=medium
* initramfs: Fix parsing of interface names when bringing the network
back down in local-bottom, which also avoids a mess of "ip: can't find
device
This bug was fixed in the package clevis - 8-1ubuntu0.2
---
clevis (8-1ubuntu0.2) bionic; urgency=medium
* initramfs: Fix parsing of interface names when bringing the network
back down in local-bottom, which also avoids a mess of "ip: can't find
device
This bug was fixed in the package clevis - 8-1ubuntu0.2
---
clevis (8-1ubuntu0.2) bionic; urgency=medium
* initramfs: Fix parsing of interface names when bringing the network
back down in local-bottom, which also avoids a mess of "ip: can't find
device
1 - 100 of 646 matches
Mail list logo
