** Changed in: docker (Ubuntu)
Assignee: (unassigned) => Ian Johnson (anonymouse67)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1814896
Title:
upgrade Docker snap to 18.09.1
To man
This affects a new snap we uploaded with license metadata to the store
around December 2018. We uploaded the snap and used the snap store
description editor to choose "Other Open Source" software and it shows
up as "Proprietary" in gnome-software.
--
You received this bug notification because
Public bug reported:
On Ubuntu 18.04.2 LTS Desktop, after running out of space on my disk, my
system was unable to finish booting and I had to go into recovery mode
and remove a number of files before the system would boot. After doing
so I discovered that now the apparmor.service systemd unit
FWIW this could be a snapd bug, because while my system was unable to
boot, I disabled all the snaps I had installed except the core snap, and
then after being able to reboot I now re-enable all the snaps and see
some warnings:
May 25 17:32:16 systemd[1]: Starting AppArmor initialization...
May
So I ran your snippet to determine which profiles weren't loaded and the
only one which wasn't loaded was:
```
$ sudo cat /sys/kernel/security/apparmor/profiles | awk '{ print $1 }' >
/tmp/foo ; sudo apparmor_parser -N /etc/apparmor.d/
/var/lib/snapd/apparmor/profiles/ >> /tmp/foo ; sort
Yes, certainly use the profile for whatever you can use it for. Would
you like me to edit the description on this bug to reflect the actual
underlying cause here or should I just close this and file a new bug for
the memory usage of this profile? I'm no expert here but I think 15.4 GB
memory usage
Ah actually, if I move that profile out of the way, then `systemctl
start apparmor` starts immediately. So the issue must be with that
profile being too large (and indeed it is 4-5 MB).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Well I tried restarting AppArmor using `systemctl start apparmor` while
running `dmesg -w -k` and got the following log:
https://pastebin.ubuntu.com/p/98zXMsr6Sy/ I don't see a stack trace for
apparmor itself, just for chrome and pulseaudio.
Is there anyway to have apparmor.service show what
@Jamie yes this was generated by snapd, the original snapcraft.yaml is
attached.
And also yes I fully understand this was an atypical usage of layouts, I
was experimenting with using layouts to make it seem to a snap
application that an additional package was installed in the base snap. I
How would you recommend I go about checking which profiles are actually
loaded and which profiles are reported as loaded? I have this from aa-
status: https://pastebin.ubuntu.com/p/c2FbrndDzs/
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
** Summary changed:
- apparmor fails to start with no parser errors
+ apparmor uses excessive memory leading to oom kill
** Description changed:
+ When attempting to load the profile from comment #7, apparmor uses
+ excessive amounts of memory leading to being killed by the OOM killer
+ and
Public bug reported:
I'm not sure if this is an Xorg issue or something else, but basically I
have enabled fractional scaling in my Disco Dingo install and upon
rebooting the scaling and the layout of the monitors is forgotten. I
have 2 identical Samsung monitors + 1 LG monitor where the LG and 1
I've seen this inside an Ubuntu 18.04 lxd container with a poor internet
connection as well. apt is version 1.6.11.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1375405
Title:
Impossible download
Yes, adding security.nesting works with the lxd snap inside a lxd
container running with the lxd snap. Closing as Fix Released in this
case, thanks @stgraber for the pointer
** Changed in: snapd
Status: New => Fix Released
** Changed in: snapd (Ubuntu)
Status: New => Fix Released
The `snap interfaces` command has now been deprecated and the `snap
connections` is now the command to use to inspect interface connections.
I cannot reproduce the issue in this bug with the `snap connections`
command, so I'm closing this.
** Changed in: snapd (Ubuntu)
Status: New => Fix
Does `snapctl set` during a hook still cause the installation of a snap
to hang for you? I cannot reproduce this behavior with snapd 2.42.
Also have you seen the new documentation for hooks at
https://snapcraft.io/docs/supported-snap-hooks ? If you would like
changes made to that documentation,
Where is the blank line? I don't quite understand what is empty here.
Also this is from an old snapd so unless it's reproducible with a newer
one I'm inclined to close this bug.
** Changed in: snapd (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are
The `snap interfaces` command is deprecated, and instead the `snap
connections` command should be used. The `snap connections` command does
auto-complete in this case. See:
```
$ GO_FLAGS_COMPLETION=1 snap connections go
go
```
** Changed in: snapd (Ubuntu)
Status: New => Confirmed
**
Actually, the content for snap try is bind-mounted (or at least it is
now, I'm not sure if that was the case when this was first reported or
not I think it has always been that way but I'm not sure).
You should still be able to edit files in the prime (or whatever dir is
bind-mounted from `snap
This at least fails more nicely with the lxd snap:
https://pastebin.ubuntu.com/p/djwrN5nxjT/
I see the following denial in the journal:
Sep 25 18:17:24 kernel: audit: type=1400 audit(1569453444.560:27044):
apparmor="DENIED" operation="mount" info="failed flags match" error=-13
I should also specify - I can ssh into the lxc container and lxc fails
in the same way as with `lxc shell ...`
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1777017
Title:
snap install lxd doesn't
** Changed in: docker (Ubuntu)
Assignee: Ian Johnson (anonymouse67) => (unassigned)
** Changed in: docker (Ubuntu)
Assignee: (unassigned) => Tianon Gravi (tianon)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Also affects: docker (Ubuntu)
Importance: Undecided
Status: New
** Changed in: docker (Ubuntu)
Assignee: (unassigned) => Tianon Gravi (tianon)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
On the same system on a different disk I have Ubuntu 18.04 Desktop
installed which does not have 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/1835585
Title:
Xorg doesn't remember
Ah sorry my apologies I confused LZMA and LZO...
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1847069
Title:
[snap] Chromium snap starts slowly
To manage notifications about this bug go to:
@lorenz-x note that all snaps today actually use XZ compression, not
LZMA. I did some investigation into which compression option would give
the best performance for snaps on the snapcraft forum at
https://forum.snapcraft.io/t/squashfs-performance-effect-on-snap-
startup-time/13920. We would
I am unable to reproduce this with the classic slack snap and core
stable (2.42.1) on Ubuntu 19.04. I don't believe that zyga's patch has
been released yet although it is merged so one could test on edge
channel of core/snapd.
--
You received this bug notification because you are a member of
@jdstrand, what is the resolution to this bug and
https://bugs.launchpad.net/snap-confine/+bug/1620442?
Is it that snapd should create /run/user/0 on behalf of the snap when it
doesn't exist, or is it the case that XDG_RUNTIME_DIR should be set to
`/run/user/0/snap.$SNAP_NAME` instead? Or both
@paal-andreassen do you have firefox installed as a snap or as a deb?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1835024
Title:
Links triggered within most snap apps open in a separate browser
It is possible, I don't know if there was a store outage during that
time, but it's possible. Without more detail it's hard to say though.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1848658
Title:
This seems like a snap specific issue and not a general snapd issue. I
would suggest contacting the author of the snap, see:
```
$ snap info python38 | grep contact
```
** Changed in: snapd (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member
What shows up with `SNAPD_DEBUG=1 snap run go get -u ...`?
Also are there any denials in the system journal at the time of the
segfault? i.e. `journalctl -e --no-pager -k`?
** Changed in: snapd (Ubuntu)
Status: New => Incomplete
** Changed in: snapd (Ubuntu Bionic)
Status: New =>
What does `snap changes` show here?
Also what does `snap known serial` show on this machine?
Typically that error is for when a device has not yet communicated with
the snap store to get a serial assertion, and thus can't install snaps.
Perhaps this device does not have network access to the
>From the dpkg terminal log I see this:
```
rm: das Entfernen von '/var/snap' ist nicht möglich: Das Gerät oder die
Ressource ist belegt
```
which google translate tells me means:
```
rm: the removal of `/var/snap` is not possible: The device or resource is busy
```
It looks like this system
I can reproduce the issue with my GTX Titan X, proprietary nvidia
drivers at 418 and Ubuntu 19.04 with snapd master. Same error messages
** Changed in: snapd
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Note that this has been reported on the forum before at
https://forum.snapcraft.io/t/classic-confinement-on-atom-yet-still-getting-denials/4956
and
https://forum.snapcraft.io/t/snapd-2-32-breaks-live-server-installer/4597
--
You received this bug notification because you are a member of Ubuntu
This is now handled properly, in the case where the snap is classic it
is shown as such, and in the case where the snap is not classic, it
cannot be installed in classic confinement. See for example a classic
snap installed:
```
$ snap info go | grep installed
installed:1.12.9
Multiple speedups for snapd seeding have been implemented since this was
first filed, can you confirm that you still see slow snapd seeding on
boot without any snaps installed on the system?
Also @mpathy, the issue surrounding gnome-calculator being slow to start is a
separate issue that has
** Changed in: snapd (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/1664445
Title:
No warning/error when removing dependency
To manage notifications about
This is because the ubuntu-image snap is not published for arm64.
Transferring to the ubuntu-image project for them to comment on
publishing the ubuntu-image snap for arm64.
** Also affects: ubuntu-image
Importance: Undecided
Status: New
** Changed in: snapd (Ubuntu)
Status: New
I don't think we have such a capability right now in snapd. If you
locally modify the snap-confine profile, it will be rewritten on at
least core refreshes (and reboots as well if I'm not mistaken), so it
sounds like we need some mechanism to specify additional rules to be
included in the
Is this still a problem with snaps in a more recent Ubuntu version and a
more recent snapd version?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1757303
Title:
Snap apps don't support input method
I suspect you've been able to resolve this, sorry we never got back to you
about it.
I'm closing it as "Won't fix", because we didn't do anything about this, but if
you're still stuck there's probably a cause for this that isn't necessarily
snapd itself and we can probably figure it out.
Again,
*** This bug is a duplicate of bug 1828500 ***
https://bugs.launchpad.net/bugs/1828500
Closing as duplicate of https://bugs.launchpad.net/ubuntu/+source
/livecd-rootfs/+bug/1828500
** This bug has been marked a duplicate of bug 1828500
snapd fails always in Optimised Ubuntu Desktop
I suspect you've been able to resolve this, sorry we never got back to you
about it.
I'm closing it as "Won't fix", because we didn't do anything about this, but if
you're still stuck there's probably a cause for this that isn't necessarily
snapd itself and we can probably figure it out.
Again,
I suspect you've been able to resolve this, sorry we never got back to you
about it.
I'm closing it as "Won't fix", because we didn't do anything about this, but if
you're still stuck there's probably a cause for this that isn't necessarily
snapd itself and we can probably figure it out.
Again,
I'm assign Pawel here as he has been working on some first-boot speed
improvements for cloud images specifically. Also, since this was
reported we now have `snap debug timings` command, which would be really
useful to look at for slow first boot. For a first-boot, the first snap
change is always
(Ubuntu)
Assignee: (unassigned) => Ian Johnson (anonymouse67)
** Changed in: snapd (Ubuntu)
Importance: Undecided => Low
** Changed in: snapd (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is s
I tried building your snaps with snapcraft to reproduce the issue, but
unfortunately the vault-snap is missing a consul binary from the consul-
dir part. Can you update the snapcraft.yaml sources and try this with a
more recent snapd? I suspect this bug has been fixed as a number of
mount
I tried building your snaps with snapcraft to reproduce the issue, but
unfortunately the vault-snap is missing a consul binary from the consul-
dir part. Can you update the snapcraft.yaml sources and try this with a
more recent snapd? I suspect this bug has been fixed as a number of
mount
** Changed in: snapd (Ubuntu)
Importance: Undecided => Wishlist
** Changed in: snapd (Ubuntu)
Assignee: (unassigned) => Michael Vogt (mvo)
** Changed in: snapd (Ubuntu)
Status: New => Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
I can see the use case here, but I tend to agree with @ogra that it is
not as useful as for debs and the sheer quantity of the output will make
it difficult to actually do anything useful with the output. Setting as
wishlist for now, if there are additional use cases for this feature,
please feel
Is this still an issue for you?
What is the output of `snap version`?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1757326
Title:
snaps can't see network
To manage notifications about this bug
*** This bug is a duplicate of bug 1864113 ***
https://bugs.launchpad.net/bugs/1864113
** This bug has been marked a duplicate of bug 1864113
snapd.seeded.service never starts
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Changed in: snapd (Ubuntu)
Importance: Undecided => High
** Changed in: snapd (Ubuntu)
Assignee: (unassigned) => Ian Johnson (anonymouse67)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.ne
How are these images built? Are they built with the tooling from livecd-
rootfs?
The issue here is that there are no assertions in the image @
/var/lib/snapd/assertions, but I'm not sure what's writing these seeds
so I can't say for sure that this bug is from livecd-rootfs.
If this image is
** Changed in: snapd (Ubuntu)
Importance: Undecided => High
** Changed in: snapd (Ubuntu)
Assignee: (unassigned) => Ian Johnson (anonymouse67)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.ne
Sure, perhaps it's not from that particular bug, but my question still
remains about how these images are built? Are they using livecd-rootfs
to seed the snaps? If so this is not a snapd bug, and is instead a
livecd-rootfs bug.
IMHO this is only a snapd bug if the seed was created with the `snap
** Also affects: livecd-rootfs (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/1864113
Title:
snapd.seeded.service never starts
To manage
Just to be clear, the messages:
```
snapd.failure.service is a disabled or a static unit, not starting it.
snapd.snap-repair.service is a disabled or a static unit, not starting it.
```
are normal and harmless.
--
You received this bug notification because you are a member of Ubuntu
Bugs,
I'll take a look at measuring this with snapd $SOON
** Changed in: snapd
Assignee: (unassigned) => Ian Johnson (anonymouse67)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1861177
Ti
The docker snap cannot access directories that start with a "." in the
home folder. This is a generic security mechanism for all snaps. I'd
recommend moving the directory out of ~/.wp-env to somewhere like ~/wp-
env or allow configuring this somehow.
As such, closing this as WontFix for snapd.
The store bug here is specifically about the snapd snap currently having
`type: app` and not properly supporting transitioning the type to `type:
snapd`.
Samuele will discuss this with the store team about how to move forward
on that front.
--
You received this bug notification because you are
Steve, the pc-kernel snap is also published for armhf and arm64 (though
it appears the arm64 was never published to 18/stable, only
18/candidate).
Though it's unclear if this request for UC16 or UC18?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
This is fixed on snapd master and will be "released" with snapd 2.44.
** Changed in: snapd
Milestone: None => 2.44
** Changed in: snapd
Importance: Undecided => High
** Changed in: snapd
Status: In Progress => Fix Committed
--
You received this bug notification because you are a
Note that if you are on focal, you may still not get this fix if you
have the edge channel of the core/snapd snaps installed, as snapd will
re-exec into that channel, and the edge channel currently is lagging
behind the debian package of snapd. We expect the edge channel to be
properly rebuilt
Note that the reason this doesn't work is partially due to
https://bugs.launchpad.net/snapcraft/+bug/1857019, which prevents the
snapd snap snapcraft.yaml from being updated to "modern snapcraft". If
that bug was fixed we could update the snapd snapcraft.yaml to modern
and it would "just work".
Hi,
The firefox snap plugs both the unity7 interface and the x11 interface.
For historical reasons, the unity7 interface grants access to parts of
the x11 interface because unity is based on X, and so to deny firefox
access to all things X, you also need to disconnect the unity7
interface. On my
Jamie, is this still an issue? I'm inclined to close this since the
apparmor bug seems to have been released a long time ago.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1413410
Title:
Unable to
Public bug reported:
The pi-kernel snap is now available for arm64 and armhf, however the
store page still says:
```
The Canonical Raspberry PI armhf kernel
```
we should probably just drop armhf and de-capitalize the "I" in PI.
** Affects: linux-raspi2 (Ubuntu)
Importance: Undecided
It is still unfortunately happening to me, but I also have a new
permutation of this, my machine also happens to suffer from
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1292398, so when I
boot up my machine the incorrect monitor layout is present, and I find
that if I first set the main
Just to clarify, I still see this bug with Focal and X11 and nvidia
drivers
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1292398
Title:
Second screen position isn't saved from one session to
I should point out that the behavior in comment #9 happens when I am
using the nvidia 440 drivers.
I still cannot use fractional scaling with the nvidia drivers
successfully under any ordering, but I can at least use 200% scaling if
I set it first, then set the main monitor it works.
--
You
Daniel, I filed that issue as
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1873266
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1869042
Title:
[nvidia] all monitor scaling fails due to
Public bug reported:
After booting with nvidia drivers, if I change which monitor is the main
one first, then change the scaling from 100% to 200%, it works. But
doing this in the inverse direction, by first setting the scaling and
then changing the main monitor, it fails and the screens go
Hi, can you paste logs for snapd from an affected boot? i.e. run
journalctl -e --no-pager -b -1 -u snapd
if the issue happened for you on the previous boot.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Hi, can you explain more what the problem is that you see with this and
more details on how to reproduce the issue?
** Changed in: initramfs-tools-ubuntu-core (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Is this perhaps a duplicate of
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1869750 ?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1869042
Title:
[nvidia] all monitor scaling fails due to
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/1873266/+attachment/5356137/+files/ProcCpuinfoMinimal.txt
** Changed in: mutter (Ubuntu)
Status: Incomplete => Opinion
** Changed in: mutter (Ubuntu)
Status: Opinion => New
--
apport information
** Tags added: apport-collected focal package-from-proposed
** Description changed:
After booting with nvidia drivers, if I change which monitor is the main
one first, then change the scaling from 100% to 200%, it works. But
doing this in the inverse direction, by first
Attaching monitors.xml since it doesn't seem that apport picked it up
** Attachment added: "~/.config/monitors.xml from my system"
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1869042/+attachment/5341610/+files/monitors.xml
--
You received this bug notification because you are a
Public bug reported:
After an upgrade with focal-proposed this morning, I am unable to set
any scaling for any of my monitors without the monitor turning blank for
15 seconds and reverting to 100% scaling.
I am using X11 with gnome and proprietary nvidia drivers on Focal. I
have 3 monitors
FWIW, if I switch to using the noveau driver and then login via Wayland,
I can enable fractional scaling through Settings and that is successful,
but unfortunately then all the text in some apps becomes rather blurry.
--
You received this bug notification because you are a member of Ubuntu
Bugs,
Actually after testing this out, I was able to use fractional scaling
with X11 again by using the nouveau driver instead of the proprietary
nvidia driver, which on my machine is at nvidia-440. This is a
sufficient work-around for me, it's unfortunate I can't use the
proprietary nvidia driver with
Oddly enough I was able to get 200% scaling to work randomly by not
quite lining up all the monitors and offsetting them from each other in
the settings window.
Is there anything I could try manually to unbreak the situation or is
there a debian package I could downgrade to in order to get
Denial on UC20 VM:
Apr 06 13:11:35 ubuntu kernel: audit: type=1400
audit(1586178695.710:59): apparmor="DENIED" operation="open"
profile="snap.docker.dockerd" name="/system-data/var/snap/docker/common
/var-lib-
I noticed that this same denial happens on UC20 on amd64 VM with kernel
5.4.0-20-generic, so perhaps this is just a new kernel behavior, and the
linux-raspi2 kernel has newer patches than all the other UC18 kernels we
have available.
--
You received this bug notification because you are a member
Hi Daniel, I tried your instructions and there is no difference between
~/.config/monitors.xml and monitors-before.xml. Both files specify the
desired configuration, but upon logging in the monitors are in the wrong
configuration.
Let me know if there's anything else I can try to help debug this
It would be nice to have this if only for our spread tests in snapd
around failed reboots.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1467553
Title:
automatic reboot fails with zero size kernel,
** Summary changed:
- [nvidia] cannot change main monitor after setting scaling for monitors
+ [nvidia] with x11 fractional scaling enabled, cannot change main monitor
after setting scaling for monitors
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Also, if I disable Fractional Scaling, it now works to use/apply these
settings in any order
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1873266
Title:
[nvidia] cannot change main monitor after
Yes, 'Fractional Scaling' is enabled, sorry I should have specified. I
am unable to actually use fractional scaling however due to
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1869042
** Changed in: mutter (Ubuntu)
Status: Incomplete => New
--
You received this bug notification
Okay, so now looking back at this bug, I see that when I have Focal with
X11 and the 440 nvidia drivers enabled, I can set scaling to integer
multiples without problems, but enabling fractional scaling and then
using a fractional scaling results in the black screen problem mentioned
in this bug as
Daniel, I just turned off fractional scaling and I no longer have this
problem, so for me at least with nvidia drivers and focal, I don't see
this bug and instead see 1825593 as you mentioned.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Hi folks, the change that @osomon referenced is available in the snapd
snap beta channel, can you try the following to see if you are able to
open zoom links from the chromium snap now:
```
snap install snapd --beta || snap refresh snapd --beta
```
I tested this on Ubuntu 20.04 and snapd 2.44.5
Daniel, it sounds then like you are saying this is a duplicate of
1873403?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1869042
Title:
[nvidia] fractional monitor scaling fails due to overlapping
(the issues here originally were that the screens go black and that I
couldn't set the main monitor after changing scaling, for which I filed
1873266, as per your request)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
This issue does appear to be specific to using the snapd snap, since the
snapd.failure unit is the service that gets triggered after the snapd
service proper fails to exit gracefully.
If someone does hit this again, it would be useful to see output from
snap changes
ASAP after the slowdown
I can't seem to assign this bug to Dimitri, but as per
https://github.com/snapcore/core20/issues/48, Dimitri should be
preparing a libseccomp 2.4.2 SRU.
** Bug watch added: github.com/snapcore/core20/issues #48
https://github.com/snapcore/core20/issues/48
--
You received this bug
Hi, thanks for reporting, does the same problem happen if you use `snap
install --unicode=never --color=never insomnia` ?
If it does still panic, can you try the following:
id=$(snap install hello-world --no-wait)
until snap changes | grep -P "^$id\s+Done"; do echo snap changes | grep -P
1 - 100 of 289 matches
Mail list logo
