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
scr
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 Ubuntu
Desktop Bugs, which is subscribed to evince in U
** 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 Ubuntu
Desktop Bugs, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/
** 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 Ubuntu
Desktop Bugs, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/1912246
Title:
[nvidia] gnome-shell freezes randomly
To manage notifications about this bug go to:
https://bugs.launchpa
Here's lspci
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/1912246
Title:
[nvidia] gnome-shell freezes randomly
To manage notifications about this bug go to:
https://bugs.launchpa
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"
https://bugs.launchpad.net/ubuntu/+s
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 (U
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)
S
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 minut
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 Ubuntu
Desktop Bu
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
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 rule
Thanks folks, this works for me now as well.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/1825593
Title:
Display scale not remembered when X11 Fractional Scaling is enabled
To ma
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
Desktop Bugs, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/1869042
Title:
[nvidia] fractional monitor scaling fails du
(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
Desktop Bugs, which is subscribed to mutter in Ubunt
** 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
Desktop Bugs, 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 Ubuntu
Desktop Bugs, which is subscrib
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
Desktop Bugs, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/1873266
Title:
[nvidia] cannot change mai
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 b
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 i
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
--
You
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 Ubuntu
Desktop Bugs, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/1869042
Title:
[nvidia] all monitor scalin
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 black.
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 rece
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
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1292398
Title:
Second screen position isn't saved fro
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 m
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
Desktop Bugs, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/1869042
Title:
[nvidia] all monitor sca
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 f
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
Deskto
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 scaling
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 mem
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 attach
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
Desktop Bug
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 you
42 matches
Mail list logo
