Public bug reported:
The engrampa Archive Manager Manual claims that it can open Stuffit
archives (.sit) but trying to do so gives the "Archive type not
supported." error message. Either fix the software or the manual.
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: engrampa 1.24.0-2
** No longer affects: lxd (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1873004
Title:
lxd interaction blocked until snapd was restarted
To manage notifications about this bug go to:
- Setup snap "snapd" (9721) security profiles (cannot reload udev rules:
exit status 1
Was that when updating a privileged LXD container by any chance?
** Changed in: lxd (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs,
I suspect you probably found a way out of this by now but if not or if
you're hitting this on another system, let me know and I'll sort
something out.
It would have been interesting to see what those symlinks are pointing
to, they may not have been rewritten properly due to the failure partway
** Package changed: lxd (Ubuntu) => snapd (Ubuntu)
** Summary changed:
- package lxd 3.0.3-0ubuntu1~18.04.1 failed to install/upgrade: new lxd package
pre-installation script subprocess returned error exit status 1
+ snapd failure when /home is a symlink
--
You received this bug notification
- Run install hook of "lxd" snap if present (run hook "install":
/var/lib/snapd not root-owned 0:110)
That's a new one I've never seen before. This suggests that directory
ownership for /var/lib/snapd is quite wrong on your system which in turn
causes some snapd actions to fail.
I'll re-assign
- Download snap "snapd" (10492) from channel "stable" (Get
https://canonical-bos01.cdn.snapcraft.io/download-origin/canonical-
lgw01/PMrrV4ml8uWuEUDBT8dSGnKUYbevVhc4_10492.snap?interactive=1=1609376400_22d9f1ee728894ebbb147d6cf985e1b06e1fbccd:
dial tcp 91.189.91.42:443: connect: connection timed
error: unable to contact snap store
This shows the reason for the failure, it's likely the system having
dropped offline at the time or some other kind of networking or
firewalling issues preventing your system from reaching the package
store.
** Changed in: lxd (Ubuntu)
Status: New =>
That's pretty confusing, it shows as if it crashed while trying to test
connectivity with the snap store but this appears to be outside of our
script and is weirdly mixed in with gnome session output.
Did you manage to fully unstick that system and apply all remaining
updates afterwards?
**
error: Unable to connect to the source LXD: Get
"http://unix.socket/1.0": dial unix /var/lib/lxd/unix.socket: connect:
connection refused
This actually suggests a LXD upgrade failure. If this can be reproduce,
the output of `journalctl -u snap.lxd.daemon -n 300` would be quite
useful.
** Changed
The issue with this one is translation handling in the old version of LXD.
The migration script has since been changed to force LANG=C.UTF-8 to avoid such
issues.
** Changed in: lxd (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member
- Setup snap "core" (10577) security profiles (cannot setup udev for
snap "core": cannot reload udev rules: exit status 1
Is that an update running inside of a privileged LXD container by any
chance?
** Changed in: lxd (Ubuntu)
Status: Confirmed => Incomplete
--
You received this bug
** Changed in: lxd (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/1923685
Title:
Unable to deploy LXD VM host on S390X
To manage notifications about this
error: unable to contact snap store
This suggests the system had network connectivity issues at the time of the
upgrade.
Did re-trying the upgrade get you through to the end eventually?
Assuming this is all inside of a container (as your systemd change
suggests), an alternative is to just
- Setup snap "snapd" (12057) security profiles (cannot reload udev
rules: exit status 1
Is this an upgrade running inside of a privileged lxd container by any
chance?
** Changed in: lxd (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of
error: system does not fully support snapd: cannot mount squashfs image using
"squashfs": mount:
/tmp/sanity-mountpoint-913738666: mount failed: Operation not permitted.
This looks odd, snapd should know to use snapfuse in such environments.
Can you show "lxc config show --expanded" of
- Download snap "lxd" (21545) from channel "4.0/stable/ubuntu-20.04"
(download too slow: 0.00 bytes/sec)
This suggests some pretty severe internet issue at the time of the upgrade.
Re-trying later or on a more reliable network may help?
** Changed in: lxd (Ubuntu)
Status: New => Invalid
- Setup snap "snapd" (13170) security profiles (cannot reload udev
rules: exit status 1
Was that a privileged LXD container (security.privileged=true)?
If so, I believe that's a known (and still unfixed) issue with snapd inside
such containers.
** Changed in: lxd (Ubuntu)
Status: New =>
Moving over to snapd as that's hitting during snap installation.
** Package changed: lxd (Ubuntu) => snapd (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1947428
Title:
package lxd
[Expired for ufw (Ubuntu) because there has been no activity for 60
days.]
** Changed in: ufw (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1938005
Since this got updated: the bug persisted until 21.04, at which point it
disappeared, but seemed to be coming back in the last patches to 21.04
(and affecting Calc, this time). I have only just upgraded to 21.10, so
I cannot comment on its current status.
--
You received this bug notification
Public bug reported:
I have a laptop (Dell XPS 13 9300) connected to an external USB-C monitor (Dell
U2719DC).
Ubuntu 21.10 Impish is installed, although this problem existed under Ubuntu
21.04 too.
If I log in using Wayland (the default), the initial window position of
any app is always in
All autopkgtests for the newly accepted linux-meta-azure (5.11.0.1020.21) for
hirsute have finished running.
The following regressions have been reported in tests triggered by the package:
systemd/247.3-3ubuntu3.6 (amd64)
dahdi-linux/1:2.11.1~dfsg-1ubuntu8 (amd64)
Please visit the excuses page
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: libreoffice (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/1888186
Title:
Public bug reported:
The screen brightness is stuck at 50% of the max output and the
brightness controls/slider do nothing at all.
This issue started happening with the nvidia-driver-470 package even
before I upgraded from 21.04, and it doesn't happen with 465. The bug
manifests in both X11 and
** Description changed:
Just did a fresh install. First thing I did was installing nvidia
drivers. Tried wayland session and got a black screen with the boot logo
page. Tried the instructions here:
https://askubuntu.com/questions/1369250/how-do-i-enable-wayland-on-
- ubuntu-21-10-nvidia
Public bug reported:
Just did a fresh install. First thing I did was installing nvidia
drivers. Tried wayland session and got a black screen with the boot logo
page. Tried the instructions here:
https://askubuntu.com/questions/1369250/how-do-i-enable-wayland-on-
ubuntu-21-10-nvidia but didn't cut
Public bug reported:
After upgrading my kernel, directories are left behind in /lib/modules
for previous kernel because with the kernel packaging layout, not all
binary packages are autoremoved:
$ dpkg -S /lib/modules/5.11.0-34-generic
linux-objects-nvidia-460-5.11.0-34-generic:
*** This bug is a duplicate of bug 1930121 ***
https://bugs.launchpad.net/bugs/1930121
Thanks, I'll check it out.
On Fri, Oct 15, 2021, 4:25 PM Grant Orndorff <1946...@bugs.launchpad.net>
wrote:
> *** This bug is a duplicate of bug 1930121 ***
> https://bugs.launchpad.net/bugs/1930121
>
Public bug reported:
I was trying a upgrade on a server from 18.04 to 20.04 but do-release-
upgrade fails when trying to upgrade lxd as the SNAP content site has an
expired/revoked certificate
The error in do-release-upgrade is
==> Installing the LXD snap from the 4.0 track for ubuntu-20.04
I don't know about Ubuntu, but FTBFS under a common locale, which would
include C, is regarded as a release-critical bug, so there is no
"correct" locale, just the one that happens to be standardised across
the Debian and Ubuntu buildds (otherwise, would "FTBFS in pbuilder" be a
bug in pbuilder?
Thank you for taking the time to report this bug and helping to make
Ubuntu better. It seems that your bug report is not filed about a
specific source package though, rather it is just filed against Ubuntu
in general. It is important that bug reports be filed about source
packages so that people
The attachment "allow-setting-pbuilder-build-locale.patch" seems to be a
debdiff. The ubuntu-sponsors team has been subscribed to the bug report
so that they can review and hopefully sponsor the debdiff. If the
attachment isn't a patch, please remove the "patch" flag from the
attachment, remove
** Package changed: ubuntu => ubuntu-meta (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1947415
Title:
A blackscreen is displayed after login.
To manage notifications about this bug go
Adding
i915.fastboot=0
to the kernel params allows booting on these kernels.
(Tested working on a XPS 9575)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1942684
Title:
Kernel 5.14.X / 5.13.14
21.10 is still affected by this issue
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1905142
Title:
[amdgpu] When entering sleep mode the monitors turn off then
immediately turn back on
To manage
Launchpad has imported 23 comments from the remote bug at
https://bugzilla.kernel.org/show_bug.cgi?id=8962.
If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
Launchpad has imported 9 comments from the remote bug at
https://bugzilla.kernel.org/show_bug.cgi?id=9924.
If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
Launchpad has imported 23 comments from the remote bug at
https://bugzilla.kernel.org/show_bug.cgi?id=8962.
If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
Though Windows (and some Kernel version on Arch) did not present that issue,
I got tired and replaced the keyboard FRU 01HX379 with FRU 01HX459 -- good so
far.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I can atest that as of today 10/15/2021 this bug is indeed present. I'm
using OpenSUSE Tumbleweed with kernel "5.14.9-1-default" this annoying
bug for me started arround 2 months ago and it is still present. At
first i thought it was some weird hardware failure but i checked on my
dmesg and i see
Now at Ubuntu 21.10 (impish) and kernel 5.13.0-19, my Ollee (ProTempo)
L116HTN6SPW is "happy".
I wonder about other models with the same wireless device...
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Why is this marked invalid?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1946667
Title:
resolved reports Failed to send hostname reply: Invalid argument
To manage notifications about this bug go
Public bug reported:
The build locale cannot be set with pbuilder and always defaults to "C"
(for both LANG and LC_ALL on Launchpad builds) rather than to "C.UTF-8"
as used by sbuild for all official Debian and Ubuntu builds. This causes
FTBFS of various packages that depend on the correct locale
I was able to solve this on Ubuntu 20.04 by moving to latest qemu 5 using
```
sudo add-apt-repository ppa:jacob/virtualisation (for Ubuntu 20.04)
sudo apt-get update && sudo apt-get install qemu qemu-user qemu-user-static
```
--
You received this bug notification because you are a member of
This looks like a duplicate of this:
https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1906476
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1931660
Title:
PANIC at
The change worked on my PC. The difference has been tested with limited changes
to my userdata, but I try tomorrow with the next set of updates. The current
snapshots are:
bertadmin@VM-Xubuntu-2110:~$ zfs list -t snapshot
NAME USED
Using 5.4.0-1020-bluefield, this Issue as been fixed:
# ifconfig oob_net0
oob_net0: flags=4163 mtu 1500
inet xxx.xxx.xxx.xxx netmask 255.255.255.0 broadcast 192.168.200.255
inet6 prefixlen 64 scopeid 0x20
ether XX:XX:XX:XX:XX:XX txqueuelen 1000 (Ethernet)
RX packets 136 bytes 11177 (11.1 KB)
** Changed in: python
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/1425972
Title:
Firefox no longer supports -remote parameter
To manage notifications about
Launchpad has imported 118 comments from the remote bug at
https://bugzilla.kernel.org/show_bug.cgi?id=9512.
If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
I was able to use basically the same patch used in Impish to fix the
golang-github-containers-buildah build failure in Hirsute, just needed
to do some refresh. Debdiff is attached.
** Patch added: "golang-github-containers-buildah.debdiff"
For golang-github-containers-common in Hirsute, I was able to backport
an upstream patch to fix the build. However, it depends on golang-
github-containers-storage version that I attached in the debdiff above
** Patch added: "golang-github-containers-common.debdiff"
Using 5.4.0-1020-bluefield, this Issue has been fixed:
# ethtool -S oob_net0
NIC statistics:
hw_access_errors: 0
tx_invalid_checksums: 0
tx_small_frames: 3
tx_index_errors: 0
sw_config_errors: 0
sw_access_errors: 0
rx_truncate_errors: 0
rx_mac_errors: 0
Using 5.4.0-1020-bluefield, this Issue has been fixed:
# modinfo mlxbf_gige
filename:
/lib/modules/5.4.0-1020-bluefield/kernel/drivers/net/ethernet/mellanox/mlxbf_gige/mlxbf_gige.ko
version:1.25
** Tags removed: verification-needed-focal
** Tags added: verification-done-focal
--
I'm not that interested in groovy/hirsute, but feel free to play with it
if you *really* wish.
** Patch added: "cinnamon_4.8.6-2ubuntu0.1.debdiff"
https://bugs.launchpad.net/ubuntu/+source/cinnamon/+bug/1919026/+attachment/5533324/+files/cinnamon_4.8.6-2ubuntu0.1.debdiff
--
You received
** Description changed:
- In the user creation dialog if you create a user that already exists (or
- try to), a GLib.Error is thrown and the dialog holds. I will make a
- patch for this.
+ [Impact]
+
+ * In the user creation dialog if you create a user that already exists
+ (or try to), a
Public bug reported:
The touchpad of my Lenovo IdeaPad Flex 3 11ADA05 stopped working after an BIOS
upgrade from FPCN21WW to FPCN24WW. (Here is the changelog of FPCN24WW:
https://download.lenovo.com/consumer/mobiles/fpcn24ww.txt )
The touchpad is no longer detected. It doesn't appear in 'xinput
The attached debdiff fixed the API incompatibility in golang-github-
containers-storage in Hirsute.
** Patch added: "golang-github-containers-storage-hirsute.debdiff"
Norbert
rar:
Installed: (none)
Candidate: 2:5.5.0-1build1
Version table:
2:5.5.0-1build1 500
500 http://us.archive.ubuntu.com/ubuntu focal/multiverse amd64 Packages
unrar:
Installed: 1:5.6.6-2build1
Candidate: 1:5.6.6-2build1
Version table:
*** 1:5.6.6-2build1 500
Well Issue does not appear when you make a clean installation.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1947364
Title:
mt76 module disagrees on a lot
To manage notifications about this bug go
** Description changed:
In the user creation dialog if you create a user that already exists (or
try to), a GLib.Error is thrown and the dialog holds. I will make a
patch for this.
Affected:
Focal - Cinnamon 4.4.8
- Groovy - Cinnamon 4.6.7
- Hirsute - current unstable. Check Debian
Launchpad has imported 16 comments from the remote bug at
https://bugzilla.mozilla.org/show_bug.cgi?id=418271.
If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
For opengcs in Hirsute, the patch used in Impish applied cleanly.
Debdiff attached.
** Patch added: "opengcs-hirsute.debdiff"
https://bugs.launchpad.net/ubuntu/hirsute/+source/golang-github-containers-buildah/+bug/1938908/+attachment/5533318/+files/opengcs-hirsute.debdiff
--
You received
Public bug reported:
Package (even in jellyfish) is outdated. Current version is 0.31.3
https://github.com/digint/btrbk/releases
** Affects: btrbk (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Public bug reported:
A blackscreen is displayed after login. This error happens with Xorg and
Wayland.
The only way to get the ubuntu-desktop to work is login into textmode
and then running startx.
ProblemType: Bug
DistroRelease: Ubuntu 21.10
Package: ubuntu-desktop 1.472
ProcVersionSignature:
Launchpad has imported 128 comments from the remote bug at
https://bugzilla.kernel.org/show_bug.cgi?id=192591.
If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
*** This bug is a duplicate of bug 1930121 ***
https://bugs.launchpad.net/bugs/1930121
This appears to be a duplicate of bug 1930121.
For now, the likely quick fix is to set
PYTHONPATH=/usr/lib/python3/dist-packages
We will release a proper fix in ubuntu-advantage-tools in a coming
release.
The following packages regressed because of a libcontainer API change in
runc:
# Hirsute
- opengcs
- golang-github-containers-storage
- golang-github-containers-common
- golang-github-containers-buildah
# Focal
- opengcs
- golang-github-containers-storage
I'll be adding tasks for each of
golang-github-docker-go-connections is also blocking runc in Hirsute but
the fix is sitting in proposed for a while but should be fixed once the
new version of golang-github-containers-images disabling LTO is
accepted. More info here:
*** This bug is a duplicate of bug 1930121 ***
https://bugs.launchpad.net/bugs/1930121
Thank you for the bug report!
This appears to be a duplicate of bug 1930121.
For now, the likely quick fix is to set
PYTHONPATH=/usr/lib/python3/dist-packages
We will release a proper fix in
*** This bug is a duplicate of bug 1930121 ***
https://bugs.launchpad.net/bugs/1930121
Thank you for the bug report!
This appears to be a duplicate of bug 1930121.
For now, the likely quick fix is to set
PYTHONPATH=/usr/lib/python3/dist-packages
We will release a proper fix in
*** This bug is a duplicate of bug 1930121 ***
https://bugs.launchpad.net/bugs/1930121
** This bug is no longer a duplicate of bug 1938290
package ubuntu-advantage-tools 27.2.2~16.04.1 failed to install/upgrade:
subprocess installed post-installation script returned error exit status 1
**
*** This bug is a duplicate of bug 1930121 ***
https://bugs.launchpad.net/bugs/1930121
This appears to be a duplicate of bug 1930121.
For now, the likely quick fix is to set
PYTHONPATH=/usr/lib/python3/dist-packages
We will release a proper fix in ubuntu-advantage-tools in a coming
release.
*** This bug is a duplicate of bug 1930121 ***
https://bugs.launchpad.net/bugs/1930121
** This bug has been marked a duplicate of bug 1930121
package ubuntu-advantage-tools 27.0.2~18.04.1 - ModuleNotFoundError: No
module named 'uaclient'
--
You received this bug notification because you
*** This bug is a duplicate of bug 1930121 ***
https://bugs.launchpad.net/bugs/1930121
This appears to be a duplicate of bug 1930121.
For now, the likely quick fix is to set
PYTHONPATH=/usr/lib/python3/dist-packages
We will release a proper fix in ubuntu-advantage-tools in a coming
release.
*** This bug is a duplicate of bug 1930121 ***
https://bugs.launchpad.net/bugs/1930121
** This bug is no longer a duplicate of bug 1934077
package ubuntu-advantage-tools 27.1~16.04.1 - ModuleNotFoundError: No module
named 'uaclient' - maybe dup 1930121
** This bug has been marked a
*** This bug is a duplicate of bug 1930121 ***
https://bugs.launchpad.net/bugs/1930121
I'm going to mark this a duplicate of bug 1930121.
For now, the likely quick fix is to set
PYTHONPATH=/usr/lib/python3/dist-packages
We will release a proper fix in ubuntu-advantage-tools in a coming
*** This bug is a duplicate of bug 1930121 ***
https://bugs.launchpad.net/bugs/1930121
In the absence of more information I'm going to mark this a duplicate of
bug 1930121.
For now, the likely quick fix is to set
PYTHONPATH=/usr/lib/python3/dist-packages
We will release a proper fix in
Sorry, the debdiff above is incorrect. The golang-github-containers-
image package in hirsute was uploaded disabling LTO here:
https://bugs.launchpad.net/ubuntu/bionic/+source/golang-github-
containers-image/+bug/1938908/comments/28
Once this is accepted, we will be able to land this update
This is hitting us again while backporting the container stack:
https://bugs.launchpad.net/ubuntu/bionic/+source/golang-github-
containers-image/+bug/1938908
I'll disable LTO to make it build fine on the failing architectures.
Debdiff attached.
** Patch added:
Olivier, I am not sure what is the reasoning here.
That you obviously want to land this in a non-LTS version has nothing to
do with the fact the base product is not ready and that the change was
announced unacceptably late here. The Flutter-based installer is a nice
example. You can obviously
Thanks for the review Sergio, package uploaded.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1938908
Title:
Backport the container stack in Impish
To manage notifications about this bug go to:
The attached debdiff should fix the issue pointed above.
** Patch added: "golang-github-containers-image.debdiff"
https://bugs.launchpad.net/ubuntu/bionic/+source/golang-github-containers-image/+bug/1938908/+attachment/5533309/+files/golang-github-containers-image.debdiff
--
You received
Thanks for the patch, Lucas. LGTM, +1.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1938908
Title:
Backport the container stack in Impish
To manage notifications about this bug go to:
There is a golang-github-containers-image/5.10.3-1ubuntu1 regression in
hirsute which is not directly caused by docker.io but it is blocking it.
The tests are failing only on arm64, ppc64el and s390x due to LTO. The
simple fix here is disabling LTO in this package.
** Also affects:
Hi,
I really do not remember any more how that somehow disappeared. Could
it be that changing the channel at the wifi router could help?
Unfortunately I did not remember that I reported the problem otherwise
I would have immediately reported a possible workaround.
Best regards, Martin.
--
You
** Package changed: ca-certificates (Ubuntu) => ubuntu-release-upgrader
(Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1947394
Title:
package ca-certificates 20210119ubuntu0.21.04.1 failed
** Information type changed from Private Security 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/1947348
Title:
i was installing ubunto on my device than it said my installation is
All autopkgtests for the newly accepted debootstrap (1.0.123ubuntu6.1) for
hirsute have finished running.
The following regressions have been reported in tests triggered by the package:
pbuilder/0.231build1 (arm64, ppc64el, s390x, amd64)
sbuild/0.81.2ubuntu5 (arm64, ppc64el, s390x, amd64)
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: mate-terminal (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/1878457
Public bug reported:
My system completely freezes requiring a hard reset if I do the following:
1. Launch Runelite (Installed using "snap install runelite")
2. Right click on the Runelite icon on the sidebar
3. System freezes
ProblemType: Bug
DistroRelease: Ubuntu 21.10
Package: xorg
Thank you for filing a bug and making cloud-init and Ubuntu better. Can
you run `sudo cloud-init collect-logs` and attach that tarfile to this
bug for ease of triage? Note that cloud-init collect-logs potentially
grabs user-data. If you have sensitive credentials defined in your user-
data, please
> I just found that this problem is not present in Debian testing
Indeed, Xwayland is living on Debian/testing and ibus-daemon is
restarted with --xim by gnome-shell. However xlsclients show only
ibus-x11/gsd-xsettings/gnome-shell only.
Is any X11 related process started and then closed?
--
Thank you Steve, you raise several good points.
1. The excessive nesting.
I agree that it is annoying to read several layers of nested ifs. As an
individual issue, we don't think this is a blocker; however if we decide to
rewrite this function for this SRU for the below reasons, we can use the
Hi,
Thank you for your response.
I think root cause is only one. Its just causing different problems. I
tried connecting other(new) mouse and keyboard but nothing worked.
Also this weird behaviour started exactly when I enabled Livepatch.
On Thu, Oct 14, 2021 at 11:50 AM Daniel van Vugt
Oh!
On the 18.04 machine I actually executed:
`xfce4-session-logout --suspend`
Now realizing this, I'm asking myself if this issue should be closed
since "pm-suspend" isn't supposed to lock, because that's "xflock4" job,
right? :|
Sorry for the noise.
Yet, I hope it may at least point others
Issue still present when attempting to create MIPS guest via virt-
manager, and adding additional environments with same issue (virt-
install and openstack nova leveraging libvirt). Attempts were made
across multiple paths still receiving same error message 'XML error: No
PCI buses available' when
Yesterday evening I upgraded my laptop to Ubuntu 20.10, so today I tried
the same on my HP Elitebook 8460p laptop based on an i5-2520M and there
conky displayed as I expected. Also I had no flickering of top-bar and
Ubuntu dock with VMs or videos in full screen.
By the way that flickering also
Public bug reported:
System: Xubuntu 20.04.3 (64bit)
When suspending my notebook by calling "/usr/sbin/pm-suspend", there is
**no login dialog** after resuming. If I suspend using the graphical
XFCE logout menu, the screen is locked properly.
I've checked on my other 18.04 machine: There,
All autopkgtests for the newly accepted debootstrap (1.0.118ubuntu1.5) for
focal have finished running.
The following regressions have been reported in tests triggered by the package:
piuparts/1.1.1build1 (amd64, s390x, arm64, ppc64el)
docker.io/20.10.7-0ubuntu1~20.04.2 (arm64)
1 - 100 of 293 matches
Mail list logo
