Creating the .config folder and file works fine (for me anyway). Think
there may be some confusion as to the pathing - the .config folder
SHOULD be /home/username/,config - but, it's NOT. The command
//.config, at least in my case, is referring to a non-existent folder -
specifically /.config
Just now: libxml2, libhogweed5, libnettle7 wrongly grouped, firefox-locale-en
wrongly ungrouped
all three wrongly grouped have i386 packages that are ungrouped
update-manager version 1:20.04.10.7
** Attachment added: "libxml2, libhogweed5, libnettle7 wrongly grouped,
firefox-locale-en wrongly
** No longer affects: linux (Ubuntu Impish)
** No longer affects: linux-oem-5.10 (Ubuntu Impish)
** Changed in: linux (Ubuntu Hirsute)
Status: New => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Attachment added: "screenshot of working gdm on AWS"
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1930359/+attachment/5505412/+files/Screenshot%20from%202021-06-18%2013-40-15.png
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
I spent some time attempting to reproduce on AWS today, using a
g4dn.xlarge instance, which has a Nvidia Tesla T4 GPU, which supports
GRID.
I installed ubuntu-desktop-minimal and rebooted, and gdm started fine
with mutter 3.36.9-0ubuntu0.20.04.1. I confirmed this by looking at the
instance
** Tags removed: need-amd64-retrace
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1932387
Title:
tumblerd crashed with SIGSEGV in vaPutImage()
To manage notifications about this bug go to:
Public bug reported:
Crash was reported after I exited a directory of images while using
Thunar.
ProblemType: Crash
DistroRelease: Ubuntu 21.10
Package: tumbler 4.16.0-1
ProcVersionSignature: Ubuntu 5.11.0-18.19+21.10.1-generic 5.11.17
Uname: Linux 5.11.0-18-generic x86_64
ApportVersion:
[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.
** Package changed: ubiquity (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/1932378
Title:
My CPU fan in max speed after ubuntu unsuspended
To manage notifications about
???
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1932378
Title:
My CPU fan in max speed after ubuntu unsuspended
To manage notifications about this bug go to:
** Package changed: ubuntu => ubiquity (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1932378
Title:
My CPU fan in max speed after ubuntu unsuspended
To manage notifications about this bug
Public bug reported:
My CPU fan in max speed after ubuntu unsuspended:
When I put ubuntu to suspend mode, and come back to it to unsuspend, the fan
runs at max "noisy" and I have to restart to get things back to normal.
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: ubiquity (not
** Tags added: originate-from-1932230
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1909734
Title:
TPM PCR checking will fail if the all characters are 0
To manage notifications about this bug go
Public bug reported:
firstly bluetooth services is somehow dead. to make it work we need to
disable the hardware for some time so that in power settings both wifi
and bluetooth is turned off and them enable it again for bluetooth to
work. and after that if bluetooth is connected automatically
** No longer affects: linux-oem-5.10 (Ubuntu Focal)
** Also affects: linux (Ubuntu Focal)
Importance: Undecided
Status: New
** Also affects: linux-oem-5.10 (Ubuntu Focal)
Importance: Undecided
Status: New
** Changed in: linux-oem-5.10 (Ubuntu Focal)
Status: New => In
** Tags added: originate-from-1931964
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1930910
Title:
Fix micmute hotkeys on HP ProBooks
To manage notifications about this bug go to:
This bug was fixed in the package gnome-desktop3 - 3.38.5-1ubuntu3
---
gnome-desktop3 (3.38.5-1ubuntu3) impish; urgency=medium
[ David Mohammed ]
* d/p/git_revert_draw_background.patch:
- Drop patch since gnome-settings-schemas v40 has removed the
draw_background key
** Changed in: binutils (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/1927070
Title:
stack-overflow on GNU libiberty/rust-demangle.c:1024
** Description changed:
[Impact]
After hot-plug the Ethernet cable, the status of Ethernet is always down.
[Fix]
Because ASPM is enabled on RTL8106E, the link change interrupt can't be fired
immediately.
Must wait a long time to get the link change interrupt.
After discuss with
** Description changed:
[Impact]
After hot-plug the Ethernet cable, the status of Ethernet is always down.
[Fix]
Because ASPM is enabled on RTL8106E, the link change interrupt can't be fired
immediately.
- Need to wait a long time to get the link change interrupt.
- Introduce a
** Changed in: linux (Ubuntu Hirsute)
Status: Confirmed => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1931147
Title:
Fix non-working GPU on Some HP desktops
To manage
I found this article from Martin Stransky:
https://mastransky.wordpress.com/2019/01/08/fedora-firefox-heads-to-
updates-with-pgo-lto/
It appears Fedora's Firefox package is build with PGO. Is Ubuntu's .DEB
package built with PGO as well?
There's also this documentation from Mozilla:
This can be found on generic 4.15.0-145.149 as well
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Summary changed:
- cfs_bandwidth01 in sched from ubuntu_ltp_stable failed on B-azure-4.15
+ cfs_bandwidth01 in sched from ubuntu_ltp_stable failed on B-4.15
--
We verified on the DL360 Gen10 plus and Apollo 4200 Gen10 Plus with
onboard Intel NIC. The SUT installed OS is from the ubuntu-18.04.4
-server-amd64.iso. Since the OS is not able to boot, there is no info
for the "uname -a" command.
Actually, I don't think the command can fix the issue because
This is a problem with openvswitch packages so adding Ubuntu/openvswitch
and cloud-archive for some bug tracking. Corresponding Ubuntu release is
well out of support and so is cloud-archive, but users could run into
this on upgrade from Queens->Rocky
** Also affects: openvswitch (Ubuntu)
** Changed in: bind9 (Ubuntu)
Assignee: (unassigned) => Athos Ribeiro (athos-ribeiro)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1899902
Title:
systemd unit service file does not wait for
** Also affects: linux (Ubuntu Impish)
Importance: Undecided
Status: New
** Also affects: linux-oem-5.10 (Ubuntu Impish)
Importance: Undecided
Status: Invalid
** Changed in: linux (Ubuntu Impish)
Assignee: (unassigned) => koba (kobako)
** Changed in: linux (Ubuntu
All autopkgtests for the newly accepted apt (2.2.4ubuntu0.1) for hirsute have
finished running.
The following regressions have been reported in tests triggered by the package:
ubuntu-advantage-tools/unknown (amd64, ppc64el, s390x, armhf)
reprotest/0.7.16 (arm64)
Please visit the excuses page
All autopkgtests for the newly accepted apt (2.2.4ubuntu0.1) for hirsute have
finished running.
The following regressions have been reported in tests triggered by the package:
ubuntu-advantage-tools/unknown (amd64, ppc64el, s390x, armhf)
reprotest/0.7.16 (arm64)
Please visit the excuses page
All autopkgtests for the newly accepted apt (2.2.4ubuntu0.1) for hirsute have
finished running.
The following regressions have been reported in tests triggered by the package:
ubuntu-advantage-tools/unknown (amd64, ppc64el, s390x, armhf)
reprotest/0.7.16 (arm64)
Please visit the excuses page
All autopkgtests for the newly accepted apt (2.2.4ubuntu0.1) for hirsute have
finished running.
The following regressions have been reported in tests triggered by the package:
ubuntu-advantage-tools/unknown (amd64, ppc64el, s390x, armhf)
reprotest/0.7.16 (arm64)
Please visit the excuses page
Thank you for taking the time to report this bug and helping to make
Ubuntu better.
Bug reporting is about finding & fixing problems thus preventing future
users from hitting the same bug.
I suspect a Support site would be more appropriate, eg.
https://answers.launchpad.net/ubuntu. You can also
All autopkgtests for the newly accepted apt (2.2.4ubuntu0.1) for hirsute have
finished running.
The following regressions have been reported in tests triggered by the package:
ubuntu-advantage-tools/unknown (amd64, ppc64el, s390x, armhf)
reprotest/0.7.16 (arm64)
Please visit the excuses page
All autopkgtests for the newly accepted apt (2.0.6) for focal have finished
running.
The following regressions have been reported in tests triggered by the package:
reprotest/0.7.14 (ppc64el)
apport/2.20.11-0ubuntu27.18 (amd64)
Please visit the excuses page listed below and investigate the
@tom-horsley
It's alright. Glad to see I'm not the only one with this "wonky" state.
Hard term to search on. I just retested on:
```
Linux 5.8.0-55-generic #62~20.04.1-Ubuntu SMP Wed Jun 2 08:55:04 UTC 2021
x86_64 x86_64 x86_64 GNU/Linux
```
... this morning and it still repeats.
Please make
All autopkgtests for the newly accepted apt (2.0.6) for focal have finished
running.
The following regressions have been reported in tests triggered by the package:
reprotest/0.7.14 (ppc64el)
apport/2.20.11-0ubuntu27.18 (amd64)
Please visit the excuses page listed below and investigate the
All autopkgtests for the newly accepted apt (2.0.6) for focal have finished
running.
The following regressions have been reported in tests triggered by the package:
reprotest/0.7.14 (ppc64el)
apport/2.20.11-0ubuntu27.18 (amd64)
Please visit the excuses page listed below and investigate the
All autopkgtests for the newly accepted apt (2.0.6) for focal have finished
running.
The following regressions have been reported in tests triggered by the package:
reprotest/0.7.14 (ppc64el)
apport/2.20.11-0ubuntu27.18 (amd64)
Please visit the excuses page listed below and investigate the
I am curious to know what is the use case for using IPv6 as opposed to
just IPv4? Also what server and network adapter are you using? Also
what kernel version are you using? Please paste the output of uname -a?
On the Iscsi target can you type the following command and retry?
sudo tgtadm
Public bug reported:
1) The release of Ubuntu you are using, via 'lsb_release -rd'
Description:Ubuntu Impish Indri (development branch)
Release:21.10
2) The version of the package you are using, via 'apt-cache policy pkgname'
libkf5i18n-dev:
Installed: 5.83.0-0ubuntu1
Candidate:
** Tags added: patch
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1932367
Title:
Pixel format change broken for Elgato Cam Link 4K
To manage notifications about this bug go to:
Thanks for looking at this @William - sorry to nitpick but I wonder if
rewriting the test as follows could make it a bit easier to parse (at
least for me I find this version easier to grok what is being tested
for):
if (*name < '1' || *name > '9')
--
You received this bug notification because
Looks like the bug I just added at
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1932360 is a
duplicate of this which I didn't find in any searches before I added it.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
I've tried downloading the nvidia drives and all i'm getting are errors.
ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: nvidia-340 (not installed)
ProcVersionSignature: Ubuntu 5.8.0-55.62~20.04.1-generic 5.8.18
Uname: Linux 5.8.0-55-generic x86_64
ApportVersion:
Problem fixed for me on Ubuntu 20.04 after Kernel upgrade to 5.4.0-74.
But the quality of sound (in and out) is really poor.
--
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]
That is good. and you could also try 21.04, the 5.11.0-20-generic kernel
should work on your machine too.
** Changed in: alsa-driver (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Looking at the build logs (https://launchpadlibrarian.net/543881602
/buildlog_ubuntu-impish-amd64.breezy_3.2.0+bzr7543-1_BUILDING.txt.gz)
I'm actually seeing a lot of issues regarding plugins.
test_plugins.TestDisablePlugin.test_partial_imports FAIL4ms
log: {{{
1138.617 loading
I tested 5.8.0-57.64~20.04.1 proposed on Focal, and it appears to be
working fine. Thank you for the fix.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1926030
Title:
IR Remote Keys Repeat Many
** Tags added: ftbfs
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1932313
Title:
Breezy 3.2.0+bzr7543-1 FTBFS
To manage notifications about this bug go to:
While breezy doesn't currently build from source this bug is old and was
taken care of so I'm marking it Fix Released.
** Changed in: breezy (Ubuntu)
Status: New => Fix Released
** Changed in: breezy-debian (Ubuntu)
Status: New => Fix Released
--
You received this bug
All autopkgtests for the newly accepted apt (1.6.14) for bionic have finished
running.
The following regressions have been reported in tests triggered by the package:
apport/2.20.9-0ubuntu7.24 (amd64)
Please visit the excuses page listed below and investigate the failures,
proceeding
All autopkgtests for the newly accepted apt (1.6.14) for bionic have finished
running.
The following regressions have been reported in tests triggered by the package:
apport/2.20.9-0ubuntu7.24 (amd64)
Please visit the excuses page listed below and investigate the failures,
proceeding
All autopkgtests for the newly accepted apt (1.6.14) for bionic have finished
running.
The following regressions have been reported in tests triggered by the package:
apport/2.20.9-0ubuntu7.24 (amd64)
Please visit the excuses page listed below and investigate the failures,
proceeding
All autopkgtests for the newly accepted apt (1.6.14) for bionic have finished
running.
The following regressions have been reported in tests triggered by the package:
apport/2.20.9-0ubuntu7.24 (amd64)
Please visit the excuses page listed below and investigate the failures,
proceeding
this actually make ubuntu much insecure because you have to run most
tools with sudo and normally those tools recommend user NOT to run it
with root. Other distros are still readable by normal user and they
harden it via selinux.
--
You received this bug notification because you are a member of
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: sbuild (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/1906970
Title:
*** This bug is a duplicate of bug 1906970 ***
https://bugs.launchpad.net/bugs/1906970
Your assessment was correct.
Commenting out "search ." and then installing Postfix resulted in a
successful install.
I'm just not sure fixing it like this is the right way though.
I have and ubuntu
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: postfix (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/1906970
Title:
*** This bug is a duplicate of bug 1922353 ***
https://bugs.launchpad.net/bugs/1922353
isn't it because you long press on the super?
then you can long press again on the super to disable this mode.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
isn't it because you long press on the super?
then you can long press again on the super to disable this mode.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1922353
Title:
Overview sometimes fails
While not rate limiting there is a solution to make the DENIAL messages
go away. Adding an explicit denial rule to the profile will tell
apparmor this is a known DENIAL that doesn't need to be audited.
deny ptrace read,
--
You received this bug notification because you are a member of Ubuntu
Ah, that explains that.
Would you mind adding tests for a few more usernames?
0root
0
00
0.0
0x0
0-0
0_0
0.o
0xo
0-o
0_o
Thanks
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1927078
Title:
Don't
Hi Seth,
That's great, thank you for the update (and for the link to the Trello
board; I wasn't aware of it!).
Cheers!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1926321
Title:
[MIR] telegraf
See also https://github.com/snapcrafters/discord/issues/23 -- there may
be some other advice buried in there on how to deal with the deluge
while also not giving discord permission to see all the processes you're
running.
Thanks
** Bug watch added: github.com/snapcrafters/discord/issues #23
FWIW, I don't believe that the commit referenced in comment #9 is
related to the problem, unless there's a race condition introduced by
the added delay. Looking at that commit, the code will try harder to
make sure that the device in the namespace exists before proceeding on
as it did before. The
This is a blocker for using JDK 16 (release 16 March 2021) along with
Maven on 20.04.
This will also be a blocker for the next LTS Java 17 release in
September 2021
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Seeing this failure on Focal now too.
Also seeing a similar problem on Bionic armhf which I'm wondering if it's
related to this failure. Bug 1932368
Difference is the test failing on Bionic is boot-smoke
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Hello Sergio, it's not forgotten, but it is currently behind backuppc-
rsync and fence-agents in the server queue https://trello.com/b/EGj5Msfo
/security-mir-backlog
Thanks
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
The Elgato Cam Link 4K HDMI video capture card reports to support three
different pixel formats, where the first format depends on the connected
HDMI device.
```
$ v4l2-ctl -d /dev/video0 --list-formats-ext
ioctl: VIDIOC_ENUM_FMT
Type: Video Capture
[0]:
Public bug reported:
This is a scripted bug report about ADT failures while running systemd
tests for linux/4.15.0-145.149 on bionic. Whether this is caused by the
dep8 tests of the tested source or the kernel has yet to be determined.
Possibly similar to Bug 1931088 (boot-and-services tests
I upgraded yesterday from 20.10 to 21.04.
In 20.10 I had trouble pairing with my current headphones (Havit 162) - I had
to repair through the terminal.
Now, in 21.04, the repairing works in the GUI.
However, today I turned off the bluetooth in the GUI and when I tried to
turn it on again the
Public bug reported:
Per https://github.com/free-
sm/geonkick/commit/0ec36f4ef9b37053e0feb60937112c247ca3b310 the code for
redkite is now included in geonkick, which is the only project that was
using it.
As such, since redkite was only used by geonkick, redkite now has no use
being a separate
Attached is a patch that disallows fully numeric usernames while still
allowing usernames such as 91jawn-smith.
** Patch added: "Disallow Fully Numeric Patch"
https://bugs.launchpad.net/ubuntu/+source/shadow/+bug/1927078/+attachment/5505363/+files/lp1927078_fully_numeric.debdiff
--
You
My Ubuntu 20.04 which uses the HWE kernel has recently updated to the
following kernel version:
$ uname -a
Linux len 5.8.0-55-generic #62~20.04.1-Ubuntu SMP Wed Jun 2 08:55:04 UTC 2021
x86_64 x86_64 x86_64 GNU/Linux
I can confirm that the Fn Lock LED is working properly now. It looks
like the
The socks.c code shows that cURL does not even attempt DNS resolution on
SOCKS4a. Strictly speaking, the SOCKS4a spec expects apps to /attempt/
DNS resolution before contacting the socks server. I won't complain on
this point though because the status quo is favorable to Tor users (as
it
My usrmerge fatal error after upgrading to 21.04:
FATAL ERROR:
Both /bin/journalctl and /usr/bin/journalctl exist.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1924850
Title:
package usrmerge
I attempted to verify.
Verification summary - inconclusive
Steps performed
1. Create container - lxc launch images:ubuntu/hirsute
2. do steps 1 & 2 in https://wiki.ubuntu.com/QATeam/PerformingSRUVerification
$ dpkg -l apt
[...]
ii apt2.2.3amd64commandline package
Public bug reported:
Ubuntu 18.04.05 LTS AMD64 was what I was trying to install.
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: ubiquity 18.04.14.15
ProcVersionSignature: Ubuntu 5.4.0-42.46~18.04.1-generic 5.4.44
Uname: Linux 5.4.0-42-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.16
@Seth that very incorrect comment is actually part of block of upstream
code that is commented out. It doesn't apply to the more relaxed Debian
username scheme.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Hello . . .
I stand corrected. The newest kernel install generated sound devices. I
may have to keep 5.13rc.
aplay -l
List of PLAYBACK Hardware Devices
card 0: sofsoundwire [sof-soundwire], device 0: Headphone (*) []
Subdevices: 1/1
Subdevice #0: subdevice #0
card 0: sofsoundwire
No, I think we cannot gather much more data and logs than we already did.
(Except the ude rules themselves, but they will not change with a kernel
update.)
I am relatively confident that this is not an netplan issue since I verified
the files in /run/systemd/network/ and the look good and fit
Apologies, I promoted this one along with https://bugs.launchpad.net
/cloud-archive/ussuri/+bug/1782517. I've reached out to Pedro to see if
he happens to have testing underway.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Changed in: cloud-images
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/1895104
Title:
It hangs during booting after deploy cloud image(.ova) and upgrade
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: systemd (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1931088
Title:
*** This bug is a duplicate of bug 1931088 ***
https://bugs.launchpad.net/bugs/1931088
Public bug reported:
This is a scripted bug report about ADT failures while running systemd
tests for linux/5.4.0-76.85 on focal. Whether this is caused by the dep8
tests of the tested source or the kernel
Public bug reported:
On intel nuc used as media server running ubuntu 20.04, the IR remote
broke in kernel 5.8.0-55. Running ir-keytable -t shows that a single IR
button press spews key down codes forever, and never does a key up.
Going back to kernel 5.8.0-48 makes the remote work properly
Agreed, and I can now reproduce this failure locally. Tracking in
https://github.com/dankamongmen/notcurses/issues/1784. Thanks!
** Bug watch added: github.com/dankamongmen/notcurses/issues #1784
https://github.com/dankamongmen/notcurses/issues/1784
--
You received this bug notification
** Merge proposal linked:
https://code.launchpad.net/~kajiya/livecd-rootfs/+git/livecd-rootfs/+merge/404339
** Changed in: cloud-images
Assignee: (unassigned) => Chloé Smith (kajiya)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
I can recreate this issue with many other applications, not limited to
intellij. From my experience, this has much more to do with timing.
Order of operations for recreation that I tested with only firefox open:
1. Make any program doc/stick to the bottom of the screen (easiest way to do
this is
Public bug reported:
SRU Justification
Impact:
The upstream process for stable tree updates is quite similar
in scope to the Ubuntu SRU process, e.g., each patch has to
demonstrably fix a bug, and each patch is vetted by upstream
by originating either directly
** Summary changed:
- Mouse wheel not interpreted correctly when using external display
+ Mouse events not interpreted correctly when using external display
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
7 years later, I have this bug in Hirsute ! (or at least the same symptoms: I
click on a mailto link and a window named “close Thunderbird” appears, with the
message :
“Thunderbird is already running, but is not responding. To use Thunderbird, you
must first close the existing Thunderbird
Sounds like software-center NOT ubuntu-release-upgrader package
** Also affects: software-center (Ubuntu)
Importance: Undecided
Status: New
** No longer affects: software-center (Ubuntu)
** Package changed: ubuntu-release-upgrader (Ubuntu) => software-center
(Ubuntu)
--
You received
This bug was fixed in the package php-doctrine-bundle - 2.2.3-1ubuntu1
---
php-doctrine-bundle (2.2.3-1ubuntu1) impish; urgency=medium
* Rebuild w/ PHP 8.0.
* d/rules: Temporarily disable testsuite to allow sidestepping
circular build dependency on php-twig (and its
This bug was fixed in the package lto-disabled-list - 11
---
lto-disabled-list (11) impish; urgency=medium
* Change golang-github-mattn-go-sqlite3 to arch any (LP: #1931881)
-- Dave Jones Mon, 14 Jun 2021 16:31:25
+0100
** Changed in: lto-disabled-list (Ubuntu)
Status:
** Changed in: cloud-archive/ussuri
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/1782517
Title:
Failed to recover stopped instance
To manage
Observed in H/KVM, cycle sru-20210531 .
[...]
10:04:03 DEBUG| [stdout] PASS: PV IPIs testing^M
10:04:05 DEBUG| [stdout] PASS: nmi-after-sti^M
10:04:15 DEBUG| [stdout] FAIL: multiple nmi^M
10:04:31 DEBUG| [stdout] PASS: pending nmi^M
10:04:31 DEBUG| [stdout] PASS: APIC LVT timer one shot^M
[...]
Observed in H/KVM, cycle sru-20210531.
** Summary changed:
- memory in ubuntu_kvm_unit_tests fails
+ memory in ubuntu_kvm_unit_tests fails (clflushopt / cwlb ABSENT)
** Tags added: 5.11 hirsute kvm
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
This bug was fixed in the package neutron - 2:13.0.7-0ubuntu1~cloud6
---
neutron (2:13.0.7-0ubuntu1~cloud6) bionic-rocky; urgency=medium
.
* Backport fix for TCP checksum issue (LP: #1832021)
- d/p/0001-Workaround-for-TCP-checksum-issue-with-ovs-dpdk-and-.patch
** Changed
The verification of the Stable Release Update for neutron has completed
successfully and the package has now been released to -updates. In the
event that you encounter a regression using the package from -updates
please report a new bug using ubuntu-bug and tag the bug report
regression-update so
1 - 100 of 356 matches
Mail list logo
