Public bug reported:
The package reported an error.
ProblemType: Package
DistroRelease: Ubuntu 22.04
Package: nvidia-driver-525 525.147.05-0ubuntu2.22.04.1
ProcVersionSignature: Ubuntu 6.5.0-1023.24-oem 6.5.13
Uname: Linux 6.5.0-1023-oem x86_64
NonfreeKernelModules: nvidia_modeset nvidia
Public bug reported:
```
GNU Image Manipulation Program version 2.10.36
git-describe: GIMP_2_10_36
Build: unknown rev 0 for linux
# C compiler #
Using built-in specs.
COLLECT_GCC=gcc
COLLECT_LTO_WRAPPER=/usr/libexec/gcc/x86_64-linux-gnu/13/lto-wrapper
https://github.com/canonical/cloud-init/issues/5114 represents the cache
invalidation issue.
** Bug watch added: github.com/canonical/cloud-init/issues #5114
https://github.com/canonical/cloud-init/issues/5114
--
You received this bug notification because you are a member of Ubuntu
Bugs,
Per the trace in https://bugs.launchpad.net/ubuntu/+source/ubuntu-
advantage-
tools/+bug/2061562/+attachment/5765702/+files/ubuntu_pro_apt_news.txt:
```
Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/uaclient/cli/__init__.py", line 1705, in
wrapper
return
For the simplestreams target, it was discussed and agreed by paelzer,
paride and aciba that it does not require an FFE because:
> In general a change like this would require an FFe, unless it is the
only viable way to fix a (sufficiently high importance) bug. In this
case the bug is
** Description changed:
- TODO
+
https://bugs.launchpad.net/ubuntu/+source/python-s3transfer/+bug/2061750/comments/3
** Changed in: python-s3transfer (Ubuntu)
Assignee: (unassigned) => Alberto Contreras (aciba)
** Changed in: python-s3transfer (Ubuntu)
Status: New => In Pr
New MR including 0.10.1 and tests:
https://code.launchpad.net/~aciba/ubuntu/+source/python-s3transfer/+git/python-s3transfer/+merge/464461
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2061750
Title:
** Merge proposal linked:
https://code.launchpad.net/~aciba/ubuntu/+source/python-s3transfer/+git/python-s3transfer/+merge/464460
** Merge proposal linked:
https://code.launchpad.net/~aciba/ubuntu/+source/python-s3transfer/+git/python-s3transfer/+merge/464461
--
You received this bug
Public bug reported:
TODO
** Affects: python-s3transfer (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2061902
Title:
upgrade to 0.10.1
To
I am working on adding build / autopkg test in
https://code.launchpad.net/~aciba/ubuntu/+source/python-s3transfer/+git/python-s3transfer/+merge/464413
.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I am working on adding build / autopkg tests in
https://code.launchpad.net/~aciba/ubuntu/+source/python-
botocore/+git/python-botocore/+merge/464419
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I am working on adding build / autopkg test in
https://code.launchpad.net/~aciba/ubuntu/+source/python-
boto3/+git/python-boto3/+merge/464411
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2061217
** Summary changed:
- [MIR] python-botocore as dependency of python-s3transfer
+ [MIR] python-botocore as indirect dependency of simplestreams (simplestreams
-> python-boto3 -> python-s3transfer -> python-botocore)
--
You received this bug notification because you are a member of Ubuntu
Bugs,
** Summary changed:
- [MIR] python-s3transfer as dependency of python-boto3
+ [MIR] python-s3transfer as indirect dependency of simplestreams
(simplestreams -> python-boto3 -> python-s3transfer)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
** Description changed:
[Availability]
The package python-boto3 is already in Ubuntu universe.
The package python-boto3 build for the architectures it is designed to work
on.
They build amd64 only (but binary is arch-all)
Link to package:
$ lintian --pedantic python-s3transfer_0.10.0-1.dsc
** Description changed:
- TODO
+ [Availability]
+ The package python-s3transfer is already in Ubuntu universe.
+ The package python-s3transfer build for the architectures it is designed to
work on.
+ They build amd64 only (but binary is
$ lintian --pedantic python-botocore_1.34.46+repack-1.dsc
P: python-botocore source: package-uses-old-debhelper-compat-version 12
P: python-botocore source: silent-on-rules-requiring-root [debian/control]
** Description changed:
- TODO
+ [Availability]
+ The package python-botocore is already in
** Description changed:
[Availability]
- The packages python-boto3, python-s3transfer and python-botocore are already
in Ubuntu universe.
- The packages python-boto3, python-s3transfer and python-botocore build for
the architectures it is designed to work on.
+ The package python-boto3 is
Public bug reported:
TODO
** Affects: python-s3transfer (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2061750
Title:
[MIR]
Public bug reported:
TODO
** Affects: python-botocore (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2061751
Title:
[MIR] python-botocore
** Description changed:
[Availability]
- The package python-boto3 is already in Ubuntu universe.
- The package python-boto3 build for the architectures it is designed to work
on.
- It builds amd64 only (but binary is arch-all)
- Link to package https://launchpad.net/ubuntu/+source/python-boto3
$ lintian --pedantic python-boto3_1.34.46+dfsg-1.dsc
P: python-boto3 source: package-uses-old-debhelper-compat-version 12
P: python-boto3 source: silent-on-rules-requiring-root [debian/contro
$ lintian --pedantic python-s3transfer_0.10.0-1.dsc
$ lintian --pedantic
** Also affects: python-botocore (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2061217
Title:
[MIR] python-boto3
To manage notifications about
python-botocore is a dependency of python-s3transfer thus it has to be
MIRed too per the same reasoning as
https://bugs.launchpad.net/ubuntu/+source/python-
boto3/+bug/2061217/comments/2
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I am going to start working on the MIR template.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2061217
Title:
[MIR] python-boto3
To manage notifications about this bug go to:
DisasteR: difficult to say if it was a change from the cloud-images,
cloud-init or other package without access to the jammy instance. But in
any case, write_files, bootcmd and runcmd are config modules that can
break the system in multiple ways as they give total control to the user
and they have
Hi DisasteR, thanks for attaching the logs.
ssh_pwauth gets handled by the set_passwords config module, which runs
as part of the cloud-config stage.
The problem is that cloud-config and cloud-final stages didn't run
because cloud-init is instructed to be disabled.
Some stanza in your
Hi @DisatesR.
In addition to John's comment, collecting and sharing cloud-init's
logs[1] (making sure no sensitive data is attached) might help us to
triage what's happening.
[1]https://cloudinit.readthedocs.io/en/latest/howto/bugs.html#collect-
logs
--
You received this bug notification
** Changed in: simplestreams (Ubuntu)
Status: New => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2052437
Title:
python-boto: obsolete, replaced by python-boto3
To manage
** Changed in: simplestreams (Ubuntu)
Assignee: (unassigned) => Alberto Contreras (aciba)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2052437
Title:
python-boto: obsolete, replaced by pyt
Thanks for the logs.
The output of `pro security-status --format=json` and the internal error
look correct, so I'm going to mark the ubuntu-advantage-tools bit as
invalid.
It feels like this is something that should be handled and fixed in
update-manager.
*** This bug is a duplicate of bug 2058133 ***
https://bugs.launchpad.net/bugs/2058133
** 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/2058158
Why the patch in https://bugs.launchpad.net/ubuntu/+source/google-guest-
agent/+bug/2057965/comments/5 and Impact description order gga after
cloud-final.service but the merged (temporal) cpc_packaging.extra MRs
order gga after cloud-config.service?
--
You received this bug notification because
** Changed in: ubuntu-advantage-tools (Ubuntu)
Status: New => Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2056779
Title:
Don't offer realtime on Raspberry Pi
To manage
Thanks, Thomas, for reporting this!
Upstream PR fixing this: https://github.com/canonical/cloud-
init/pull/5021
** Changed in: cloud-init (Ubuntu)
Status: New => In Progress
** Changed in: cloud-init (Ubuntu)
Assignee: (unassigned) => Chad Smith (chad.smith)
--
You received this
Attaching subiquity as the installation was driven by it.
** Also affects: subiquity (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2055754
Title:
cloud-init upstream PR adding test coverage for this issue:
https://github.com/canonical/cloud-init/pull/4982
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2055397
Title:
netplan/systemd-networkd:
Attaching cloud-init logs, which include journal logs.
** Attachment added: "cloud-init.tar.gz"
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2055397/+attachment/5750656/+files/cloud-init.tar.gz
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Marking cloud-init as invalid as I think there is no workaround to fix this
issue.
Adding netplan.io for reference and awareness.
After confirmation from systemd-networkd, I wonder if it would be
feasible / reasonable to backport
https://github.com/systemd/systemd/pull/19344 to focal.
--
You
Public bug reported:
Cloud-init introduced a feature to configure policy routing on AWS EC2
instances with multiple NICs in
https://github.com/canonical/cloud-init/commit/0ca5f31043e2d98eab31a43d9dde9bdaef1435cb
targeting v24.1.
Cloud-init generates the following netplan config:
```
$ cat
Hello Nobutu. Thanks again for reporting this.
I have been trying to reproduce the error with no success. I tried some
combinations of:
- In lxd container with [jammy, noble]
- [pro downgrade / upgrade targeting 31.1]
- pro enable / disable
- [pro downgrade / upgrade targeting 31.1]
- apt
*** This bug is a duplicate of bug 1833004 ***
https://bugs.launchpad.net/bugs/1833004
Thanks Islam for reporting this. I'm going to mark this as a duplicate,
as we already have this issue reported as bug 1833004.
** This bug has been marked a duplicate of bug 1833004
Application SNAP is
(Ubuntu)
Assignee: (unassigned) => Alberto Mardegan (mardy)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1778375
Title:
All snap loops are being output for lsblk, blkid, and fdisk -l.
To man
Reproduced with:
```sh
$ lxc launch ubuntu:jammy jj
$ lxc exec jj -- cloud-init status --wait
$ lxc exec jj -- cloud-init --version
/usr/bin/cloud-init 22.1-14-g2e17a0d6-0ubuntu1~22.04.5
$ lxc exec jj -- apt purge -y cloud-init
...
dpkg: warning: while removing cloud-init, directory '/etc/cloud'
** No longer affects: curtin (Ubuntu)
** Also affects: curtin
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1975922
Title:
custom image deploy get
Can you please check (and possibly attach) the machine log for errors.
It's under
/var/snap/maas/common/log/rsyslog/$machine_name/$date/messages
** Changed in: maas
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
** Also affects: curtin (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1975922
Title:
custom image deploy get failed in cmd-curthooks of
Hi Fernando, and thanks for reporting this bug!
If, as you wrote in the bug description, you reproduce it when logging
in with your uername and password, then this bug is not related to bug
1593407, which is about the "guest session" (that is the session for
those users who don't have a login
For the record, I've opened a discussion in the jupiter-notebook forums:
https://github.com/jupyter/notebook/discussions/6436
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1959417
Title:
browsers
Oh, this is interesting! Then, Etienne, my suggestion is the following:
re-enable the snapd.apparmor service, and if that (as I expect) fixes
the bug, let's stop discussing this issue here, and instead open a
separate issue about the service being disabled.
It may be that something went wrong
Oh, thanks Alex, I forgot that we have our own service for loading the
AppArmor profiles of the snaps!
Etienne, could you please show the output of
sudo systemctl status snapd.apparmor
?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Some updates, while I'm still investigating this on a QEMU running
Ubuntu Core 22.
The "snap auto-import" command is only needed on Ubuntu Core systems, so
the plan is to remove the /lib/udev/rules.d/66-snapd-autoimport.rules
from the snapd deb package (and consequently also from the snapd snap).
e analysis by Jiwei Sun is
correct: it's happening because of the added SystemCallFilter entry to
the udev unit file.
** Changed in: snapd
Assignee: (unassigned) => Alberto Mardegan (mardy)
** Changed in: snapd
Importance: Undecided => High
--
You received this bug notifica
*** This bug is a duplicate of bug 1966203 ***
https://bugs.launchpad.net/bugs/1966203
Thanks Nick, indeed! I'm closing this since 1966203 was reported first.
** This bug has been marked a duplicate of bug 1966203
Syslog shows "systemd-udevd[2837]: nvme0n1: Process ... failed with exit
As with the other package, "Architecture" should be set to amd64 only,
since this is for Intel Alder Lake platforms. Other that this, I could
not find any issues with the package.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Changed in: snapd (Ubuntu)
Assignee: (unassigned) => Alberto Mardegan (mardy)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1971955
Title:
systemd-udevd call unshare process w
Maybe "Architecture" should be set to amd64 only, since this is for
Intel Alder Lake platforms. Other that this, I could not find any issues
with the package.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Hi again Vincent :-)
Please ignore the part about adding more attributes to the SystemCallFilter
list; I don't think it's a road we want to follow.
What would be more important for me to know, is whether things work if
you change the RUN line to just
RUN+="/usr/bin/snap auto-import
Thanks Vincent. I think I got some hints: I downloaded the package from
Jammy, I unpacked it and then ran a diff on the systemd unit file for
the udev service (since in the documentation of udev[1] it's written
that programs are executed in a sandbox) from the version in Focal:
==
---
Hi Paul and Laurent, thanks for your bug report. Can you please check
what happens when you manually run tha same commands that you see as
failed?
For example, from Laurent's log:
sudo /usr/lib/snapd/snap-device-helper add snap_brave_brave
/class/video4linux 0:0 && echo ok
Also, if you
Thanks Etienne, this is a bit surprising! Do I understand correctly,
that on the slower machine (where you are seeing this bug) you will not
be able to start firefox until you have run that apparmor_parser
command? Not even if you try starting firefox well after the login?
It's strange, because
Mmm... I'm running out of ideas! Mayve it's something with the
environment?
Vincent, can you try changing the rule to
RUN+="/bin/bash -c 'set > /tmp/set.log'"
and attach set.log here?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Hi Jeffrey and Erik!
You are being heard :-) But this is not an easy task, and the amount of work
required to support the case of home directories nested somewhere deeper inside
/home is very different (read: lower) than that required to support home
directories located elsewhere in the
** Information type changed from Private Security to Public Security
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1973300
Title:
NVIDIA CVE-2022-{28181|28183|28184|28185|28191|28192}
To manage
** Changed in: snapd
Assignee: (unassigned) => Alberto Mardegan (mardy)
** Changed in: snapd
Status: Confirmed => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1776800
Hi Erik, I see now what's the problem (this is specific to your setup --
this probably does not concern other people who commented here): your
home directories are under /staff, whereas currently snaps only support
the traditional /home// scheme.
Please subscribe to
Vincent, maybe the udev rules are running under a user lacking some
privileges?
Can you please try changing the rule to
RUN+="/bin/bash -c 'id > /tmp/id.log'"
and then paste here the output of id.log? (hopefully I didn't mess up
the quoting in the command :-) )
--
You received this bug
Thanks Erik and Andrew for the logs!
It looks like we have more than one bug here:
1) Andrew's logs show that after restarting the snapd service, NFS was
correctly detected and there are no more AppArmor denials on that. But
on Erik's machine, for some reason, that did not happen.
2) Even if
Hi Etienne, can you be a bit more explicit about what is the issue that
you are seeing? What are the services which are not starting?
Also please attach the SVG file generated by "sudo systemd-analyze
plot", it might help us.
--
You received this bug notification because you are a member of
I believe that this is a duplicate of bug 1884299.
A few questions to people affected by this bug:
1) are you using autofs?
2) can you please try running "sudo systemctl restart snapd" after
logging in into your $HOME, and then try running a snap again?
3) If that still fails, can you paste
Hi Vincent, if I understand it correctly, this command scans the
inserted media for snapd assertions and imports them.
It's still not clear to me what's happening: even if you are running on
a classic system, the "auto-import is disabled on classic" is just a
notification and not an error: the
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1959375
Title:
[SRU] Please support group manipulation with "extrausers"
To
Hi Brian,
I finally tested the new packages on Ubuntu Core 18 (with the bionic
packages) and Ubuntu Core 20 (with the focal ones). I first tried to reproduce
the issue in Ubuntu Desktop, by making /etc/groups and /etc/passwd read-only
and indeed I couldn't add my user to a group, but
I've also tested more recent versions than 5.15 from the mainline PPA
(5.16 and 5.17), they all fail to resume.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1967721
Title:
Laptop never resuming
On my laptop
5.13 -> always suspends/resume correctly (battery and power)
5.15 -> always fails to resume (battery and power)
fwupdate doesn't report any update available.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
We did some progress in investigating this, and it appears that a
problem still exists: if the system is using autofs and snapd is started
before any NFS home directory is mounted, snapd will fail to detect the
fact that the system is using autofs (or NFS), and will not grant snap-
confine those
A similar issue was discussed in the forums:
https://forum.snapcraft.io/t/cannot-open-path-of-the-current-working-
directory-permission-denied-bis/28704
If the system is using autofs and snapd is started before any NFS home
directory is mounted, snapd will fail to detect the fact that the system
Hi Vincent, thanks for reporting this. There should be some message
printed by the "snap auto-import" command when it fails.
Can you please try to manually run (as root) the command
/usr/bin/unshare -m /usr/bin/snap auto-import --mount=/dev/nvme0n239
and paste here the output?
** Changed
As per the attachment, I can't really reproduce the problem in my bionic
chroot using the 390 driver from the archive, and Linux 4.15.0-178.187
from the CKT PPA.
** Attachment added: "390-non-failure.txt"
** Summary changed:
- [Sony WI-C310] [Intel Wireless 8260] Bluetooth headset not autoconnecting on
power-on on 21.10
+ [Sony WI-C310] [Intel Wireless 8260] Bluetooth headset not autoconnecting on
power-on on 22.04
--
You received this bug notification because you are a member of Ubuntu
Bugs,
Daniel,
yes I'm using an external monitor via DP. This is the same setup I've
been using for a long time with no issue. I've reverted to the Impish
kernel (mainly because of an other kernel issue preventing
suspend/resume) and that makes the issue disappear.
** Changed in: linux (Ubuntu)
It feels pretty sluggish to use. Not sure if it's a packaging issue or
chromium issue.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1897454
Title:
[snap] Chromium has Wayland support disabled
To
It works for me on 102.0.5005.40 (latest/beta channel) but with the
following GPU error messages:
```
[2005781:2005781:0506/130903.210912:ERROR:gpu_init.cc(481)] Passthrough is not
supported, GL is egl, ANGLE is
WARNING: Kernel has no file descriptor comparison support: Operation not
permitted
** Changed in: linux-restricted-modules (Ubuntu Bionic)
Assignee: (unassigned) => Ian May (ian-may)
** Changed in: linux-restricted-modules (Ubuntu Focal)
Assignee: (unassigned) => Ian May (ian-may)
** Changed in: linux-restricted-modules (Ubuntu Impish)
Assignee: (unassigned) =>
Here I have images that tell the truth about my Eevee and Vulpix cursors
in Snap Apps that DMZ-White appears instead
Using Firefox Snap for the sample
https://i.stack.imgur.com/dtoC0.jpg
https://i.stack.imgur.com/FiZTH.jpg
--
You received this bug notification because you are a member of
** Changed in: nvidia-graphics-drivers-390 (Ubuntu Bionic)
Assignee: (unassigned) => Alberto Milone (albertomilone)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1971479
Title:
ADT fail
Access to the "$HOME/.local/share/fonts/" is provided by the "desktop"
interface. The libreoffice snap should add this interface to its plugs,
and then fonts from this location should become usable.
I'm marking this bug as invalid for snapd (since it does not appear that
we need to do anything
I tested by installing the kernel from impish (linux-
image-5.13.0-40-generic) on jammy, suspend works correctly with that
one.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1967721
Title:
Laptop
** Also affects: snapcraft
Importance: Undecided
Status: New
** Also affects: snapcraft.io
Importance: Undecided
Status: New
** No longer affects: snapcraft.io
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Also affects: firefox (Ubuntu)
Importance: Undecided
Status: New
** No longer affects: firefox (Ubuntu)
** Also affects: snapcraft (Ubuntu)
Importance: Undecided
Status: New
** No longer affects: snapcraft (Ubuntu)
** No longer affects: snapd (Ubuntu)
** Also affects:
Yep cursors are not provided in https://snapcraft.io/gtk-common-themes I
hope that one day the Snap problems with my cursors will be solved
especially when Ubuntu is just Snap and no more APT For now I will use
Flatpak since they respect my cursors until this conflict of my cursors
with Snap and
** Also affects: snapd
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1970265
Title:
My Eevee and Vulpix cursors are not respected in almost all Snap
** Changed in: nvidia-graphics-drivers-510 (Ubuntu)
Status: New => Triaged
** Changed in: nvidia-graphics-drivers-510 (Ubuntu)
Importance: Undecided => High
** Changed in: nvidia-graphics-drivers-510 (Ubuntu)
Assignee: (unassigned) => Alberto Milone (albertomilone)
Public bug reported:
I clarified this and made it clear in
https://askubuntu.com/questions/1373356/no-eevee-cursor-on-snap-programs
Almost all Snap programs (except Blender and Android Studio) don't
recognize my Eevee and Vulpix cursors instead DMZ-White appears and it
looks very ugly with my
This still fails with Chromium 100.0.4896.127 (snap 1967) on 22.04:
$ chromium --enable-features=UseOzonePlatform --ozone-platform=wayland
[261783:261783:0425/123646.322058:ERROR:wayland_connection.cc(209)] Failed to
connect to Wayland display
I upgraded the following to 3.44.0-1ubuntu1 from jammy-proposed:
evolution evolution-common evolution-plugin-bogofilter evolution-plugin-
pstimport evolution-plugins libevolution
I can also confirm I can compose messages and replies.
--
You received this bug notification because you are a
Also, probably related, after the system has entered standby (the power
led pulsates slowly), the fan keeps running for a while. I've never seen
this behavior before with previous releases.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
After force-rebooting the machine and looking at the previous boot dmesg
(journalctl -k -b -1) I noticed this:
Apr 03 23:10:55 arrakis kernel: wlp4s0: deauthenticating from 1e:e8:29:9b:9e:c5
by local choice (Reason: 3=DEAUTH_LEAVING)
Apr 03 23:10:56 arrakis kernel: PM: suspend entry (deep)
Apr
Hi Dave, I did not see any I/O errors from the kernel, but in your first
boot log
(https://errors.ubuntu.com/oops/fa9433d0-c022-11ec-8ae0-fa163e993415)
there are plenty of errors which might be related to missing files:
===
Apr 19 21:46:38 localhost.localdomain pulseaudio[841]: Failed to load
** Changed in: software-properties (Ubuntu)
Assignee: (unassigned) => Alberto Milone (albertomilone)
** Changed in: software-properties (Ubuntu)
Importance: Undecided => High
** Changed in: software-properties (Ubuntu)
Status: Confirmed => In Progress
--
You received
1 - 100 of 17401 matches
Mail list logo
