To avoid all of these problems, please just select 'Ubuntu on Xorg' at
the login screen.
** Changed in: gnome-shell (Ubuntu)
Assignee: (unassigned) => Daniel van Vugt (vanvugt)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to
And I suspect the "5-6hz" is just that it managed to allocate some dumb
buffers, but not enough of them to get every frame to the monitor.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
To work around this problem, please log into a Xorg session instead.
** Tags added: hybrid multigpu multimonitor nvidia
** Tags added: nvidia-wayland
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
Actually I think I've seen this before. One of the graphics drivers has
run out of memory:
[ 198.184944] semiauto gnome-shell[2341]: Failed to allocate onscreen
framebuffer for /dev/dri/card1: Failed to create dumb drm buffer: Cannot
allocate memory
[ 198.209428] semiauto gnome-shell[2341]:
Your log is mostly showing bug 1967707 but I think the root cause that
comes before it is:
[ 199.493073] semiauto gnome-shell[2341]: meta_frame_native_release:
assertion '!frame_native->kms_update' failed
--
You received this bug notification because you are a member of Desktop
Packages, which
Public bug reported:
NVIDIA GPU sending out frames to an LG Electronics 27" display.
At the moment, just a single display.
The NVIDIA GPU is available across a Thunderbolt 3 link.
Here is what the Nvidia Drivers are reporting:
beadon@semiauto:~$ nvidia-smi
Mon Jul 10 20:35:25 2023
Were you using Wayland when the freeze happened? Next time it happens,
please reboot and then run:
journalctl -b-1 > prevboot.txt
and attach the resulting text file here.
** Package changed: xorg (Ubuntu) => ubuntu
** Changed in: ubuntu
Status: New => Incomplete
** Tags added:
Public bug reported:
When using the Ubuntu settings app to change displays I was enabling and
disabling displays to see if I could replicate a problem. It appears
that the drivers / setup are OK with 2x displays, but things start to
fall apart when there are 3x displays. 2x displys managed by
One thing I've found is this is a high frequency occurrence with
IntelliJ. I have not seen this issue with the snap versions of Sublime
Text or Firefox. I did experience the issue in the snap version of GIMP
the one time I had it open.
Another interesting effect is that I am unable to resize the
Thanks. The issue sounds like it's in mutter's constraints logic so please
report it at:
https://gitlab.gnome.org/GNOME/mutter/-/issues
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mutter in Ubuntu.
Please also run:
grep . /sys/class/drm/*/status > outputs.txt
and attach the resulting text file here.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/2026754
Title:
Thanks for the bug report. The attached Xorg logs seem to be old, from
last month. Please run this command to collect a fresh log when the
problem is happening:
journalctl -b0 > journal.txt
and attach the resulting text file here.
** Tags added: amdgpu hybrid multigpu multimonitor nvidia
**
Please test without these extensions:
'gsconn...@andyholmes.github.io',
'user-th...@gnome-shell-extensions.gcampax.github.com',
'always-indica...@martin.zurowietz.de'
** Changed in: gnome-shell (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a
Please clarify what the problem is you would like to report. Which log
message are you referring to?
** Package changed: xorg (Ubuntu) => ubuntu
** Changed in: ubuntu
Status: New => Incomplete
--
You received this bug notification because you are a member of Desktop
Packages, which is
It's committed to the git branch 'ubuntu-dock-jammy' but not in proposed
yet.
The desktop team policy of saying 'Fix Committed' before anything is
even in proposed was started by Seb. I wouldn't mind if we revisited
that though because it does confuse other teams and even ourselves.
--
You
my fedora computer has pkexec version 121 which has the --keep-cwd
option. if ubuntu would update pkexec i'm guessing it would have that
option too.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to policykit-1 in Ubuntu.
** Tags removed: need-duplicate-check
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to nvidia-graphics-drivers-340 in Ubuntu.
https://bugs.launchpad.net/bugs/2026611
Title:
package nvidia-340 340.108-0ubuntu5.20.04.2 failed to
*** This bug is a duplicate of bug 2017980 ***
https://bugs.launchpad.net/bugs/2017980
@novhak
Here is the output of "LC_ALL=C apt list --installed 'linux-*'”
Listing... Done
linux-base/jammy,jammy,now 4.5ubuntu9 all [installed,automatic]
*** This bug is a duplicate of bug 2000858 ***
https://bugs.launchpad.net/bugs/2000858
Thank you for taking the time to report this crash and helping to make
this software better. This particular crash has already been reported
and is a duplicate of bug #2000858, so is being marked as such.
** Package changed: ubuntu => xorg (Ubuntu)
--
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/2026733
Title:
EXT4-fs error
Status in xorg package in Ubuntu:
New
Bug description:
Jul
Public bug reported:
I use Asus FA507XI laptop with AMD 7940HS and NVIDIA RTX 4070. When using the
second display via HDMI its picture not updating automatically, but only on
mouse move.
Additionally brightness control is not visible, so I can't change brightness.
ProblemType: Bug
Additional observation:
If I refresh into FF latest/stable, the undesired line
/etc/fonts/conf.d
gets written into ~/snap/firefox/current/.config/fontconfig/fonts.conf.
I suppose the reason is that the snap from that channel is linked to
gnome-3-38-2004 which has not (yet) been updated in this
@Nathan
Thank you for the clarity on the Core20 vs Core22, however, I will still
maintain that had this latest Chromium SNAP been built on Core20, as has
seemingly been until now, we wouldn't be having this dialog.
When Chromium has been built against Core20, I've been able to call
chromium
Interestingly, this also happened once where the right quarter was
clicking through as well. I noticed this when trying to interact with
the title bar buttons (minimize, restore, close) and I ended up clicking
the title bar buttons of the window behind.
--
You received this bug notification
> (I still maintain that if Ubuntu 20.04 LTS is supported until April
> 2025, and its base SNAP is core20, it is not appropriate (if, only
> because of my biased opinion) to build snaps on core22, which, you
> admit, is the base snap core for Ubuntu 22.04)
I think there is a misunderstanding
-- Nathan
The symlink I'm referring to is the *current* in this path:
/snap/chromium/**current**/usr/lib/chromium-browser/chrome
... which is a symlink to build 2529 or, now I have 2497
(I still maintain that if Ubuntu 20.04 LTS is supported until April
2025, and its base SNAP is core20, it
The verification of the Stable Release Update for gnome-shell has
completed successfully and the package is now being released to
-updates. Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you
This bug was fixed in the package gnome-shell - 42.9-0ubuntu2
---
gnome-shell (42.9-0ubuntu2) jammy; urgency=medium
* New upstream release (LP: #2023913)
* debian/control.in: Bump minimum mutter to 42.9
-- Jeremy Bícha Wed, 14 Jun 2023 15:35:33 -0400
** Changed in:
Merged upstream. Will be part of the next Netplan release.
** Also affects: netplan
Importance: Undecided
Status: New
** Changed in: netplan
Status: New => Fix Committed
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to
Public bug reported:
As part of the LTS 22.04.3 release many gnome package updates are
available in the 'proposed' repository. When checking these on a test
machine I noticed that the window raise behavior when clicking on
notifications has regressed for some applications. In 22.04.2 clicking
on
I have dropped the block-proposed-jammy tag since Mutter 42.9 is in
jammy-updates and has fully phased.
I installed gnome-shell 42.9-0ubuntu2 on Ubuntu 22.04 LTS and
successfully completed all 3 test cases.
--
You received this bug notification because you are a member of Desktop
Packages,
** Summary changed:
- error when setting up after upgrading
+ libnetplan integration breaks "cloned-mac-address" special values
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
** Tags removed: block-proposed-jammy verification-needed
verification-needed-jammy
** Tags added: verification-done verification-done-jammy
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
~/snap/firefox/current/.config/fontconfig/fonts.conf was updated
"automatically" on my mantic installation. Not sure which combo of
circumstances made it happen, but I have core22 from the
latest/candidate channel. Then I refreshed firefox (switched form
latest/stable to
** Changed in: dash-to-dock
Status: Unknown => New
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell-extension-ubuntu-dock in
Ubuntu.
https://bugs.launchpad.net/bugs/1934185
Title:
Ubuntu Dock popup menu in top left
I see this bug also affects gnome-shell-extension-ubuntu-dock, but in
jammy-proposed I only see yaru-theme. Is the gnome-shell-extension-
ubuntu-dock package needed for this to go forward?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to
This bug was fixed in the package gnome-desktop - 42.9-0ubuntu1
---
gnome-desktop (42.9-0ubuntu1) jammy; urgency=medium
* New upstream release (LP: #2023923)
* Cherry-pick German translation update from 42.10
-- Jeremy Bícha Wed, 14 Jun 2023 16:42:33 -0400
** Changed in:
This bug was fixed in the package speech-dispatcher - 0.11.1-1ubuntu3
---
speech-dispatcher (0.11.1-1ubuntu3) jammy; urgency=medium
* patches/systemd-socket-activation: Added.
- Enables activating Speech Dispatcher via a Systemd socket, it's needed
for confined clients to
This bug was fixed in the package gjs - 1.72.4-0ubuntu0.22.04.1
---
gjs (1.72.4-0ubuntu0.22.04.1) jammy; urgency=medium
* New upstream stable release (LP: #2023572)
* debian/patches: Drop, they've been all applied upstream
gjs (1.72.3-0ubuntu0.22.04.1) jammy; urgency=medium
*
This bug was fixed in the package libadwaita-1 - 1.1.7-0ubuntu0.22.04.1
---
libadwaita-1 (1.1.7-0ubuntu0.22.04.1) jammy; urgency=medium
* New upstream release (LP: #2023548)
-- Marco Trevisan (Treviño) Mon, 12 Jun 2023
15:07:03 +0200
** Changed in: libadwaita-1 (Ubuntu Jammy)
This bug was fixed in the package gjs - 1.72.4-0ubuntu0.22.04.1
---
gjs (1.72.4-0ubuntu0.22.04.1) jammy; urgency=medium
* New upstream stable release (LP: #2023572)
* debian/patches: Drop, they've been all applied upstream
gjs (1.72.3-0ubuntu0.22.04.1) jammy; urgency=medium
*
The verification of the Stable Release Update for gjs has completed
successfully and the package is now being released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you encounter a
The verification of the Stable Release Update for gjs has completed
successfully and the package is now being released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you encounter a
** Changed in: nvidia-graphics-drivers-535 (Ubuntu)
Status: Triaged => In Progress
** Changed in: ubuntu-drivers-common (Ubuntu)
Status: Confirmed => Triaged
** Changed in: ubuntu-drivers-common (Ubuntu)
Importance: Undecided => High
** Changed in: ubuntu-drivers-common
This bug was fixed in the package speech-dispatcher - 0.11.3-1ubuntu1.1
---
speech-dispatcher (0.11.3-1ubuntu1.1) kinetic; urgency=medium
* patches/systemd-socket-activation: Added.
- Enables activating Speech Dispatcher via a Systemd socket, it's needed
for confined
The laptop comes with a Ryzen 5600H processor and Nvidia GeForce GTX
1650 graphics card.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to alsa-driver in Ubuntu.
https://bugs.launchpad.net/bugs/2026719
Title:
Low Volume 22.04 Realtek
The verification of the Stable Release Update for mesa has completed
successfully and the package is now being released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you encounter a
This bug was fixed in the package mesa - 23.0.4-0ubuntu1~23.04.1
---
mesa (23.0.4-0ubuntu1~23.04.1) lunar; urgency=medium
* New upstream release. (LP: #2021948)
- add a revert for amdgpu which missed 23.0.x branch
-- Timo Aaltonen Fri, 09 Jun 2023 12:53:37 +0300
** Changed
** Also affects: nvidia-graphics-drivers-535 (Ubuntu)
Importance: Undecided
Status: New
** Changed in: nvidia-graphics-drivers-535 (Ubuntu)
Status: New => Triaged
** Changed in: nvidia-graphics-drivers-535 (Ubuntu)
Importance: Undecided => High
** Changed in:
The verification of the Stable Release Update for speech-dispatcher has
completed successfully and the package is now being released to
-updates. Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you
This bug was fixed in the package speech-dispatcher - 0.11.4-2ubuntu0.1
---
speech-dispatcher (0.11.4-2ubuntu0.1) lunar; urgency=medium
* patches/systemd-socket-activation: Added.
- Enables activating Speech Dispatcher via a Systemd socket, it's needed
for confined clients
Public bug reported:
I have dual boot Windows 10, volume is high even at 50%. The same
YouTube video, VLC player, Rhythmbox have poor audio volume even at
100%. Relying on Bluetooth speakers for some media. I tried various GUI
tools, alsa-mixer. The volume is 100%. Looks like something to do with
First of all, sorry for the inconvenience. The problem was caused by
some missing dependencies which were not yet available in the archive.
We are going to look into ways to make the update process more robust.
Thank you for reporting the problem.
** Also affects: linux-restricted-modules
> I am struggling to find any use cases where GNOME's VNC should be
preferred to RDP.
1) Teacher screen broadcasting to students. There, a shared VNC session
is much easier to setup and performs better than separate RDP sessions.
Additionally, encrypting e.g. 10 RDP streams comes with significant
** Changed in: mutter (Ubuntu Lunar)
Status: In Progress => Fix Committed
** Changed in: mutter (Ubuntu Lunar)
Assignee: (unassigned) => Jeremy Bícha (jbicha)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mutter in Ubuntu.
** Changed in: mutter (Ubuntu Lunar)
Status: In Progress => Fix Committed
--
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/2023766
Title:
Mouse cursor stutters over GUI elements
** Package changed: gnome-shell (Ubuntu) => mutter (Ubuntu)
** Changed in: mutter (Ubuntu)
Status: Incomplete => New
** Summary changed:
- New windows have weird behavior on the desktop
+ New windows have confused sizing when monitors are set to different scaling
factors
** Tags added:
It's in proposed:
https://launchpad.net/ubuntu/+source/mutter/44.3-0ubuntu1
** Changed in: mutter (Ubuntu Lunar)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mutter in Ubuntu.
> Does the problem go away if you set both monitors to the same scale?
Indeed, if I set the 3 screens at the same scale (ie 200%) the problem
goes away.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
** Changed in: gnome-shell
Status: Unknown => New
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/2026630
Title:
gnome-shell brings down all running applications when
** Bug watch added: github.com/micheleg/dash-to-dock/issues #2055
https://github.com/micheleg/dash-to-dock/issues/2055
** Also affects: dash-to-dock via
https://github.com/micheleg/dash-to-dock/issues/2055
Importance: Unknown
Status: Unknown
--
You received this bug notification
Thanks for the bug report. Your log seems to be full of the same
recurring gnome-shell log message so please start by deleting all local
unsupported extensions:
cd ~/.local/share/gnome-shell/
rm -rf extensions
and then log in again. If the problem keeps happening after that then
please
That is currently a Snap shortcoming, there is no dependency enforcement
like in Apt. So in general you'd really have to ask. :/
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
This is likely for compatibility. /usr/bin/ is the same (/bin is a
symlink to it) so there might be old software expecting /usr/bin/X11/...
** Changed in: xorg (Ubuntu)
Importance: Undecided => Low
** Changed in: xorg (Ubuntu)
Status: New => Opinion
--
You received this bug
-- Michaelus
> you're saying invoking chromium via a fully qualified, real-path, with
a SNAP-created symbolic link to a actual build directory, is a
"unsupported setup" ?
Yes, running a snap via /snap/chromium/current/usr/lib/chromium-
browser/chrome is unsupported. (I don't know how you
I don't expect GNOME to implement this any time soon. In the meantime
it's worth noting most people either don't experience regular crashes,
or will only experience one recurring crash that causes them the most
grief. So please remember to report all crashes you experience by:
66 matches
Mail list logo
