apport information
** Attachment added: "monitors.xml.txt"
https://bugs.launchpad.net/bugs/1997142/+attachment/5631554/+files/monitors.xml.txt
** Description changed:
When using a Wayland session with kernel 5.15.0-53-generic gnome-shell
may sometimes crash and restart. This happened to
apport information
** Attachment added: "ShellJournal.txt"
https://bugs.launchpad.net/bugs/1997142/+attachment/5631553/+files/ShellJournal.txt
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
apport information
** Attachment added: "ProcEnviron.txt"
https://bugs.launchpad.net/bugs/1997142/+attachment/5631552/+files/ProcEnviron.txt
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/1997142/+attachment/5631551/+files/ProcCpuinfoMinimal.txt
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
apport information
** Attachment added: "GsettingsChanges.txt"
https://bugs.launchpad.net/bugs/1997142/+attachment/5631550/+files/GsettingsChanges.txt
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
apport information
** Attachment added: "Dependencies.txt"
https://bugs.launchpad.net/bugs/1997142/+attachment/5631549/+files/Dependencies.txt
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
Public bug reported:
When using a Wayland session with kernel 5.15.0-53-generic gnome-shell
may sometimes crash and restart. This happened to me when using a
chromium-based browser (Brave).
➜ ~ uname -r
5.15.0-53-generic
➜ ~ printenv XDG_SESSION_TYPE
wayland
The issue does not happen on the
apport information
** Attachment added: "ShellJournal.txt"
https://bugs.launchpad.net/bugs/1995207/+attachment/5627854/+files/ShellJournal.txt
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
apport information
** Attachment added: "ProcEnviron.txt"
https://bugs.launchpad.net/bugs/1995207/+attachment/5627853/+files/ProcEnviron.txt
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/1995207/+attachment/5627852/+files/ProcCpuinfoMinimal.txt
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
apport information
** Attachment added: "GsettingsChanges.txt"
https://bugs.launchpad.net/bugs/1995207/+attachment/5627851/+files/GsettingsChanges.txt
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
apport information
** Attachment added: "Dependencies.txt"
https://bugs.launchpad.net/bugs/1995207/+attachment/5627850/+files/Dependencies.txt
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
Public bug reported:
Gnome shell crashed while I was doing web browsing.
A crash report was also submitted via apport. This is a fresh install of
Ubuntu 22.10.
~$ uname -r
5.19.0-23-generic
HW: 21D4000HUS with integrated graphics in Ryzen 7 PRO 6850H and AMD
Radeon RX 6500M discrete card (AMD
Hi Daniel,
I submitted a new crash dump via `ubuntu-bug`:
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1863142
I'm going to set the status for this one to "New" as I provided the info
but maybe it should be duplicated to the new bug.
** Changed in: xorg-server (Ubuntu)
Public bug reported:
I observed the following on Eoan as well with nvidia drivers older than
440.
1) a windows 10 VM running in a qemu-kvm VM: pc-q35-3.1 machine type,
QXL + SPICE:
2) When a host is booted with `prime-select intel` observing
I see, thanks for the clarification.
I will need to read through other cases as well.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gdm3 in Ubuntu.
https://bugs.launchpad.net/bugs/1862531
Title:
[focal] Wayland session is not
Hi Daniel, thank you for the quick response and prior work.
I think the upstream check for the nvidia driver in 61-gdm.rules is too
broad to be useful as the nvidia driver might be loaded for other
reasons (e.g. CUDA usage or hw accelerated video encoding/decoding while
nvidia-drm.ko is
Public bug reported:
A Wayland session present at /usr/share/wayland-sessions/ubuntu-
wayland.desktop is not displayed at the login screen when a system has
an iGPU (Intel) and dGPU (Nvidia) and Intel iGPU is used:
prime-select query
intel
Only sessions at /usr/share/xsessions are present.
➜
Public bug reported:
Scenario: a server is available via LAN from which content is played
back via SFTP (ssh, gvfs).
After some time (could be an hour) rhythmbox hangs and a window comes up
suggesting that you can either wait or terminate rhythmbox.
There are no network interruptions that would
A bit odd that I cannot reproduce this on a fresh 18.04 installation on
the same system.
https://paste.ubuntu.com/p/PqYBPfvvKr/
--
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/1764137
Also, the setup in comment #7 was tested with 4.17-rc4 and 4.17-rc5.
--
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/1764137
Title:
[bionic][beta][nvidia] gnome-shell high CPU
apport information
** Attachment added: "ProcEnviron.txt"
https://bugs.launchpad.net/bugs/1764137/+attachment/5116801/+files/ProcEnviron.txt
** Description changed:
I am experiencing 60% - 200% CPU utilization after an upgrade from
ubuntu artful to bionic.
Pretty much any drawing
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/1764137/+attachment/5116800/+files/ProcCpuinfoMinimal.txt
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
apport information
** Tags added: apport-collected
** Description changed:
I am experiencing 60% - 200% CPU utilization after an upgrade from
ubuntu artful to bionic.
Pretty much any drawing results in a sluggish behavior due to high CPU
utilization.
The same combination of
Public bug reported:
I am experiencing 60% - 200% CPU utilization after an upgrade from
ubuntu artful to bionic.
Pretty much any drawing results in a sluggish behavior due to high CPU
utilization.
The same combination of kernel/drivers did not result in the issue on
17.10 so gnome-shell seems a
** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu)
Status: Expired => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell-extension-ubuntu-dock
in Ubuntu.
https://bugs.launchpad.net/bugs/1717599
Title:
Chris, out of curiosity, do you have a dual-monitor setup?
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1726538
For me it works fine with a laptop monitor disabled + single monitor as
a primary.
--
You received this bug notification because you are a member of Ubuntu
Desktop
Hmm, for my installation upgraded from 17.04 it got fixed - I no longer
experience the issue.
--
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/1716341
Title:
Settings for
Public bug reported:
On-boot message in the log:
окт 15 01:50:32 blade gnome-shell[6314]: Some code accessed the property
'discreteGpuAvailable' on the module 'appDisplay'. That property was
defined with 'let' or 'const' inside the module. This was previously
supported, but is not correct
Seems to be fixed after the last update:
dpkg -l
http://paste.ubuntu.com/25741586/
Thanks a lot!
--
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/1723048
Title:
gnome-shell crashed
Forgot to add, #6 is about this scenario
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1722000 from
a duplicated bug.
I can now change scaling to 200% on an external monitor and gnome shell
doesn't crash.
--
You received this bug notification because you are a member of Ubuntu
This used to work before recent a update of several distro packages.
Currently settings are not applied and everything falls back to "Join
displays" instead of "Single Display".
---
After debugging that a little bit more I can see that the bug is not
triggered if I do not change scaling from
Public bug reported:
Attached screenshots for "before applying" and after.
ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: gnome-shell 3.26.1-0ubuntu1
ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3
Uname: Linux 4.13.0-12-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_drm
** Attachment added: "After"
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1722000/+attachment/4964664/+files/after.png
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
This used to work before recent a update of several distro packages.
Currently settings are not applied and everything falls back to "Join
displays" instead of "Single Display"
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to
Public bug reported:
Just opened http://gnomepomodoro.org/ app. CPU spiked (judging by my
laptop's fans) and I got a partial UI freeze for about a second or so
followed by a dock redraw.
Multiple app open/close sequences do not seem to trigger that but I had
this a couple of times already. Not
Public bug reported:
Two scenarios:
1. alt + tab
2. windows key + window selection
Top and left bars are problematic in the first case - there is an offset
after alt-tab is done (see the attachment).
Haven't tested Intel Graphics or Intel Graphics + Wayland yet but I
suspect it's going to be
Public bug reported:
Surprisingly, when I launched meld as a difftool and later suspended it
my session got frozen: my mouse was moving but clicks and keyboard
presses did not have any effect, there was an empty rectangle on my
screen on top of one of the windows. The only thing I could do was to
38 matches
Mail list logo
