Read-only access to /usr/local/doc seems fine to me, should be pretty
straight forward to extend the system-package-doc interface to also
allow this directory too, only question would be if it should instead be
a new interface like user-package-doc or something, but we can sort that
out in a PR I
Public bug reported:
On Impish 21.10, gnome-shell freezes up when trying to login,
specifically after I have typed in my password and hit enter. I have
seen this both when logging in after the display shuts itself off after
whatever the automatic timeout is, and also after manually locking the
I mentioned this on the snapcraft forum, but /usr/share/local/ca-
certificates for a strict snap will come from the read-only, static base
snap of the chromium snap.
For classic ubuntu/debian systems running new enough snapd, we will
actually mount /etc/ssl from the host into the strict snaps'
Also I'm not sure I agree with jdstrand's apparmor profile which
includes:
/run/snapd.socket rw,
which I don't think we want to grant to any PDF file opened with evince?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to evince in
** Changed in: snapd
Status: Confirmed => Fix Committed
** Changed in: snapd
Milestone: None => 2.53
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
https://bugs.launchpad.net/bugs/1940467
Title:
** Changed in: snapd
Status: In Progress => Fix Released
** Changed in: snapd
Milestone: None => 2.51
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
https://bugs.launchpad.net/bugs/1919268
Title:
This is because snapd's u2f-devices interface lacks this rule. See my
response here: https://forum.snapcraft.io/t/nitrokey-fido2-does-not-
work-with-chromium-snap/26098/2
** Also affects: snapd
Importance: Undecided
Status: New
** Changed in: snapd
Status: New => Confirmed
**
** Changed in: snapd (Ubuntu)
Assignee: Samuele Pedroni (pedronis) => Ian Johnson (anonymouse67)
** Changed in: snapd (Ubuntu)
Status: Confirmed => In Progress
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-b
** Attachment added: "prevboot.txt"
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1912246/+attachment/5474126/+files/prevboot.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mutter in Ubuntu.
Here's lspci
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/1912246
Title:
[nvidia] gnome-shell freezes randomly
Status in Mutter:
Unknown
Status in mutter package in Ubuntu:
** Attachment added: "lspci.txt"
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1912246/+attachment/5474125/+files/lspci.txt
** Attachment removed: "prevboot.txt"
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1912246/+attachment/5474124/+files/prevboot.txt
--
You received
Here's lspci
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/1912246
Title:
[nvidia] gnome-shell freezes randomly
Status in Mutter:
Unknown
Status in mutter package in Ubuntu:
Okay, so this time when it happened at Sun Mar 7 02:44 AM UTC 2021,
here are the logs. I did not find any crash files in /var/crash, and
there were no results for my whoopsie-id either.
The journalctl output is attached
** Attachment added: "prevboot.txt"
Here's lspci
** Attachment added: "lspci -kv"
https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1912246/+attachment/5471916/+files/lspci.txt
** Changed in: gnome-shell (Ubuntu)
Status: Incomplete => New
** Changed in: gnome-shell-extension-ubuntu-dock
Hey so sorry I missed that you wanted me to run those commands before,
but it happened again this morning and here are the requested logs and
lspci output. Note that I stripped out all the messages from snapd since
I have debug mode enabled and it's extremely noisy, but if you think
snapd could be
So I disabled both ubuntu-dock and the desktop icons extensions and
still see the freezes, here's a log of gnome-shell:
https://pastebin.ubuntu.com/p/CXCfTVtkMJ/
** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu)
Status: Incomplete => New
** Changed in: gnome-shell (Ubuntu)
Public bug reported:
The symptoms here for me are exactly the same as described in
https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-desktop-
icons/+bug/1912246 where after starting up my Groovy system with X11 and
proprietary NVIDIA drivers the desktop session just hangs for a
I think also that this means we should always ask for `snap list --all`
output when debugging these sorts of issues.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
https://bugs.launchpad.net/bugs/1915712
I don't think we could/should warn because we don't know for sure which
content slot should be used, just because the default-provider is
disabled doesn't mean that the user isn't trying to use some other
provider of the content interface.
We could maybe expose some additional property on
Hi, @jl-o, on your system can you run in a terminal and share the
output:
journalctl --no-pager -u snapd
snap changes
for err in $(snap changes | grep Error | awk '{print $1}'); do snap tasks $err;
done
Thanks
** Changed in: snapd (Ubuntu)
Status: New => Incomplete
--
You received
** Changed in: snapd (Ubuntu)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
https://bugs.launchpad.net/bugs/1900679
Title:
[snap] Apparmor audit messages for
)
Status: Incomplete => In Progress
** Changed in: snapd (Ubuntu)
Assignee: (unassigned) => Ian Johnson (anonymouse67)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
https://bugs.launchpad.ne
So I did a bit of looking and it appears that Chromium only calls
sched_setaffinity for it's renderer threads on Android (maybe?). I'm not
super familiar with Chromium source code so it's a bit difficult for me
to tell, but I tried playing videos etc. which might trigger some sort
of rendering
Unfortunately, I seem to be on that version of gnome-shell-extension-
desktop-icons and still experience the freeze when I enable the desktop
icons extension. Here's the dpkg output and gnome-shell logs:
https://pastebin.ubuntu.com/p/yqDTV5KBmC/
** Changed in: gnome-shell-extension-desktop-icons
So indeed after enabling _only_ the Desktop Icon extension I experienced
a freeze. Here are the logs: https://pastebin.ubuntu.com/p/XwJS7N4tF5/
** Changed in: gnome-shell (Ubuntu)
Status: Incomplete => New
--
You received this bug notification because you are a member of Desktop
So after a full day of usage yesterday I did not see the freeze/crash at
all, so it does indeed appear to be caused by one of the extensions
bundled with Ubuntu. Should I try just enabling them one-by-one using
the Extensions app?
I can't remember what all Extensions are enabled by default, but I
Well for the short bit that I've been using the system after disabling
all the extensions through the Extensions app, I have not experienced
any freeze. I will report back after the end of the day if I see any
more freezes though.
Interestingly, after disabling all Extensions, I have no more dock
Hi Daniel, I disabled all of these extensions, and then rebooted the
machine and still a minute or two after logging in again experienced the
freeze. Here are the logs from gnome-shell:
https://pastebin.ubuntu.com/p/YKtMQ2qy4g/
Note, I only disabled the extensions located in ~/.local/share/gnome-
Public bug reported:
I recently upgrading from Focal to Groovy, and use proprietary NVIDIA
drivers with X11 with otherwise standard GNOME, but some extensions
installed. I see frequently errors relating to the dash-to-dock
extension which I'm not sure are related, but I also see that gnome-
shell
The relevant syscall is `sched_setaffinity`, which when used with a
first argument of `0` is allowed in the default policy. Can someone who
is experiencing this bug run an strace to determine what argument
chromium is trying to use with sched_setaffinity ? We allow any
sched_setaffinity arguments
The mentioned fix has been released for some time in stable snapd now,
are folks still seeing invalid caches created by snapd when any snap
refreshes?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
** Changed in: snapd (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to ubuntu-meta in Ubuntu.
https://bugs.launchpad.net/bugs/1895144
Title:
ubuntu-server CET gap analysis
Status in
@osomon,
> $SNAP_DATA/policies is not writable by the snap, so the import of
existing policies won't work.
$SNAP_DATA is by definition writable, so I'm curious what led you to
think that it isn't? If it is showing up as read-only then that would be
a snapd bug. Perhaps you were running as
I'm not sure what the original problem is with this bug, but regarding
the denial messages, that seems specific to the rocketchat-server snap.
Those denial messages could be silenced if the rocketchat-server snap
used (or had connected it the interface is disconnected) network-
observe.
I do not
Public bug reported:
With Ubuntu 20.04, GDM 3.34.1 (bundled with Focal), and the proprietary
NVIDIA drivers, I am unable to use Wayland to login, and can only use
XOrg. Debugging this a little, I found that wayland support is wholesale
disabled when proprietary NVIDIA drivers are used by this
** Description changed:
After installing the candidate/vaapi channel, I still do not get
hardware acceleration for video decoding from my NVIDIA gpu, see:
```
$ LIBVA_MESSAGING_LEVEL=2 snap run chromium
Gtk-Message: 09:07:37.215: Failed to load module "canberra-gtk-module"
Public bug reported:
After installing the candidate/vaapi channel, I still do not get
hardware acceleration for video decoding from my NVIDIA gpu, see:
```
$ LIBVA_MESSAGING_LEVEL=2 snap run chromium
Gtk-Message: 09:07:37.215: Failed to load module "canberra-gtk-module"
Gtk-Message:
Unfortunately we do not have a clear solution to this yet, so I have
unassigned myself from the snapd task and we need more help before we
can continue on this. Although, we have a few options as I detail here:
https://github.com/snapcore/snapd/pull/8856#issuecomment-644784642
I'm not sure what
** Changed in: snapd (Ubuntu)
Assignee: Ian Johnson (anonymouse67) => (unassigned)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
https://bugs.launchpad.net/bugs/1858636
Title:
snapd genera
Also just to clarify, we will regenerate fontconfig cache's on any snap
refresh/install during the link-snap task.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
https://bugs.launchpad.net/bugs/1858636
but this font:
fonts-kiloji
do show up in the cache we generate. The spread test we have for this
functionality was using the latter so we didn't see this bug til now.
** Changed in: snapd (Ubuntu)
Status: New => Confirmed
** Changed in: snapd (Ubuntu)
Assignee: (unassigned) => Ian J
Unfortunately we have no such plans at this time to enable snapd / snaps
to work inside docker containers. We recommend using lxd containers
instead of docker as snaps are officially supported, secure, and tested
to work inside lxd containers.
For a more complete answer about why it is very hard
Thanks folks, this works for me now as well.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/1825593
Title:
Display scale not remembered when X11 Fractional Scaling is enabled
Status
Hi @jean-helou,
The comment you see was referencing this PR:
https://github.com/snapcore/snapd/pull/8289 which unfortunately did not
end up making it into 2.44, however I have confirmed that it is in 2.45,
which should be released soon. If you would like to test out those
changes, please install
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
@osomon, could you point me to an existing forum post or start a new one
summarizing what accesses would be necessary to manage gnome shell
extensions? I couldn't find one searching, but if there's not one we
should open one to try and discuss with snapd architects. Thanks
--
You received this
(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 Desktop
Packages, which is subscribed to mutter in Ubuntu.
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 Desktop
Packages, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/1869042
Title:
[nvidia] fractional monitor scaling fails due
** 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 Desktop
Packages, which
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 Desktop
Packages, which is subscribed
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 Desktop
Packages, which is subscribed to gnome-control-center in Ubuntu.
https://bugs.launchpad.net/bugs/1873266
Title:
[nvidia]
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
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
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
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 Desktop
Packages, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/1869042
Title:
[nvidia] all monitor scaling
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
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
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 Desktop
Packages, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/1292398
Title:
Second screen position isn't saved from one
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
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 Desktop
Packages, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/1869042
Title:
[nvidia] all monitor
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
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 Desktop
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
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
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 Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
@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 Desktop
Packages, which is subscribed to xdg-utils in Ubuntu.
https://bugs.launchpad.net/bugs/1835024
Title:
Links triggered within most snap apps open in a
Ah sorry my apologies I confused LZMA and LZO...
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
https://bugs.launchpad.net/bugs/1847069
Title:
[snap] Chromium snap starts slowly
Status in chromium-browser
@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
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
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 Desktop
Packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1835585
Title:
Xorg doesn't
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
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
76 matches
Mail list logo
