apport information
** Attachment added: "CRDA.txt"
https://bugs.launchpad.net/bugs/1901779/+attachment/5428127/+files/CRDA.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1901779
Title:
Wirele
apport information
** Attachment added: "RfKill.txt"
https://bugs.launchpad.net/bugs/1901779/+attachment/5428123/+files/RfKill.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1901779
Title:
Wi
apport information
** Attachment added: "PaInfo.txt"
https://bugs.launchpad.net/bugs/1901779/+attachment/5428135/+files/PaInfo.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1901779
Title:
Wi
apport information
** Attachment added: "acpidump.txt"
https://bugs.launchpad.net/bugs/1901779/+attachment/5428143/+files/acpidump.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1901779
Title:
apport information
** Attachment added: "RfKill.txt"
https://bugs.launchpad.net/bugs/1901779/+attachment/5428140/+files/RfKill.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1901779
Title:
Wi
apport information
** Attachment added: "Lsusb-v.txt"
https://bugs.launchpad.net/bugs/1901779/+attachment/5428134/+files/Lsusb-v.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1901779
Title:
apport information
** Attachment added: "IwConfig.txt"
https://bugs.launchpad.net/bugs/1901779/+attachment/5428129/+files/IwConfig.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1901779
Title:
apport information
** Attachment added: "Lsusb-t.txt"
https://bugs.launchpad.net/bugs/1901779/+attachment/5428133/+files/Lsusb-t.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1901779
Title:
apport information
** Attachment added: "AlsaInfo.txt"
https://bugs.launchpad.net/bugs/1901779/+attachment/5428126/+files/AlsaInfo.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1901779
Title:
You have a lot of PPA's in use. See /etc/apt/source.list.d/ for details.
You need to run ppa-purge on them to revert to standard package versions
before attempting to upgrade.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bug
debdiff for SRU focal-ussuri
** Description changed:
When using calico, the vif_type is tap, therefore when the instance is
being created, the method plug_tap() is invoked, which creates the tap
device prior to launching the instance.
That tap device is currently always created without
debdiff for SRU bionic-stein
** Patch added: "bionic-stein.debdiff"
https://bugs.launchpad.net/ubuntu/+source/nova/+bug/1893263/+attachment/5428146/+files/bionic-stein.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https:
debdiff for SRU bionic-train
** Patch added: "bionic-train.debdiff"
https://bugs.launchpad.net/ubuntu/+source/nova/+bug/1893263/+attachment/5428145/+files/bionic-train.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https:
Confirmed this continues on Ubuntu 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/1749961
Title:
xhci_hcd: TRB DMA errors reported with ASMedia ASM1142 USB 3.1
Controller
To manage notifica
Investigating (0) nodejs:amd64 < 10.22.1-1nodesource1 @ii mK Ib >
Broken nodejs:amd64 Depends on python-minimal:amd64
Try removing nodejs package.
** Changed in: ubuntu-release-upgrader (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of U
** Information type changed from Private to Public
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1898784
Title:
do-release-upgrade crashed with AttributeError in calcDistUpgrade():
'DistUpgradeCon
** Description changed:
BugLink: https://bugs.launchpad.net/bugs/1896578
[Impact]
Block discard is very slow on Raid10, which causes common use cases
which invoke block discard, such as mkfs and fstrim operations, to take
a very long time.
For example, on a i3.8xlarge instance
Public bug reported:
Setting up tex-common (6.04ubuntu1) ...
Ignoring /etc/texmf/texmf.d/05TeXMF.cnf during generation of texmf.cnf, please
remove manually!
Ignoring /etc/texmf/texmf.d/15Plain.cnf during generation of texmf.cnf, please
remove manually!
Ignoring /etc/texmf/texmf.d/45TeXinputs.cnf
** Tags added: rls-ff-incoming
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1899372
Title:
update-grub 10_linux_zfs fails when /usr is a separate filesystem
To manage notifications about this bug
Thanks for your report!
Ubuntu uses the locale definitions provided by glibc, and this kind of
request should be made via an upstream bug report:
https://sourceware.org/bugzilla/enter_bug.cgi?product=glibc;component=localedata
If you file such a bug, please include a convincing justification of
Public bug reported:
In focal/universe (Ubuntu 20.04.1 LTS), stunnel4 version 3:5.56-1 has a
build patch named
04-restore-pidfile-default.patch
This patch defines a constant string PIDFILE and uses this constant
string in the lines:
case CMD_SET_DEFAULTS:
new_global_options.pidfile=
Public bug reported:
The current versions of sosreport (3.9 on Bionic and 4.0 on Focal) do
not appear to support passing the --upload-url to a non-Canonical URL,
for example a LAN-side host to collect those sosreports.
sudo sosreport --batch -o pci --upload --upload-
url=https://10.0.1.112/so
Thanks for the bug report, Alexander!
I have a local setup here with an Active Directory running on Windows
Server 2019, and I fired up a Focal VM and tried to reproduce the steps
you mentioned above. In a nutshell, here's what I did:
- realm join mydomain --membership-software=adcli
- Installed
I also applied patch and can confirm it resolves the issue.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1898904
Title:
Calibre crashes at startup with AttributeError: 'NoneType' object has
no at
*** This is an automated message ***
This bug is tagged needs-packaging which identifies it as a request for
a new package in Ubuntu. As a part of the managing needs-packaging bug
reports specification,
https://wiki.ubuntu.com/QATeam/Specs/NeedsPackagingBugs, all needs-
packaging bug reports have
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: rng-tools (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/1887359
Title:
agreed, this is a problem
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1887359
Title:
systemd unit not honors /etc/default/rng-tools
To manage notifications about this bug go to:
https://bugs.laun
Ah, OK. Maybe the previous problem with the snap was because the old
session monitor was still active? Odd.
But glad it worked now!
So yeah, looks like the fixes in 42.3 work for your case, and it's
possible the patches around encrypted & removable drives from 42.3 and
42.4 should be backported t
** Tags added: trusty2xenial
** Tags added: third-party-packages
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1901782
Title:
the upgrade from ubuntu 16.04.12 to last one does'nt work
To manage no
This bug was fixed in the package virtualbox - 6.1.16-dfsg-3
---
virtualbox (6.1.16-dfsg-3) unstable; urgency=medium
* Add patch to support python3.9 (Closes: #972918)
-- Gianfranco Costamagna Tue, 27 Oct 2020
08:28:19 +0100
** Changed in: virtualbox (Ubuntu)
Status: In
Testing systemd 245.4-4ubuntu3.3 on Focal, I can verify that the default
value of the "Cache" directive is "no-negative" in the man page, default
config file, and actual program behaviour.
While doing this, I was reminded that the default value of the "DNSSEC"
directive is "no" in both the default
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 '/sys/class/net/$iface
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 '/sys/class/net/$iface
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 '/sys/class/net/$iface
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 '/sys/class/net/$iface
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 '/sys/class/net/$iface
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 c
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 r
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 r
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 about
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 r
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 r
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 r
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 rec
** 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 pip
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 '/sys/class/net/$ifac
^^^
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
j
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 hibernatio
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 '/sys/class/net/$ifac
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 '/sys/class/net/$ifac
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 '/sys/class/net/$ifac
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 '/sys/class/net/$ifac
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)
** Change
** 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: rls-gg
** 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 t
*** 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 sub
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:
Sound
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
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/
>
> The
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 t
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:
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 below
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.
https://bugs.launchpad.net/bugs/1901
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
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
** Pa
** 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 t
*** 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 look
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 received
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
===
Descr
** 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"
+
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 mi
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 pai
*** 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 raise(
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") f
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 nature
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 x86_64
*** 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 m
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 r
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 notification
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 r
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 bug
** 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 xf
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 c
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")
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 receiv
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 certain
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 c
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
** A
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: 21.
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.
https://bug
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 a
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
Curre
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 encoun
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
Ti
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:
501 - 600 of 640 matches
Mail list logo
