Thanks, yes any failure to install now needs a separate bug report.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/2043915
Title:
Booting into live session results in try/install page
Confirmed fix released in https://cdimage.ubuntu.com/daily-
live/20240116/
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/2043915
Title:
Booting into live session results in try/install
Those issues are unrelated so please log a separate bug report for each
one.
--
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/1970291
Title:
[nvidia] Secondary monitor performance is
Thanks. The only crash similar to that I can find is
https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/5651
Using Wayland instead of Xorg will avoid it.
** Bug watch added: gitlab.gnome.org/GNOME/gnome-shell/-/issues #5651
https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/5651
** Summary
** Changed in: mesa (Ubuntu)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/2043915
Title:
Booting into live session results in try/install
Xorg itself doesn't paint anything, it will start with a black window.
So it's likely to be a Xubuntu bug. Since it can't be reproduced then
let's leave it Incomplete and it will close automatically after two
months of inactivity.
** Package changed: xorg (Ubuntu) => ubuntu
** Changed in: ubuntu
Thanks for the bug report. If you are able to reproduce the crash then
please add MUTTER_SYNC=1 to /etc/environment, reboot and then find out
the new stack trace.
** Summary changed:
- gnome-shell crash while chaing Chromium browser tab
+ gnome-shell crashed with X error 161 (major 152, minor
I think screen sharing is instigated from gnome-shell rather than being
an underlying mutter feature so perhaps report the bug to
https://gitlab.gnome.org/GNOME/gnome-shell/-/issues
But they will likely also want you to check the bug still exists in
GNOME 45 (Ubuntu 23.10).
--
You received this
This is being tracked upstream in:
https://gitlab.freedesktop.org/wayland/wayland-protocols/-/issues/158
** Bug watch added: gitlab.freedesktop.org/wayland/wayland-protocols/-/issues
#158
https://gitlab.freedesktop.org/wayland/wayland-protocols/-/issues/158
** Changed in: wayland (Ubuntu)
Public bug reported:
ver 5.72:
Fix issue with BAP and handling stream IO linking.
Fix issue with BAP and setup of multiple streams per endpoint.
Fix issue with AVDTP and potential incorrect transaction label.
Fix issue with A2DP and handling crash on suspend.
This appears to be a networking or server problem, so likely isn't a bug
we need to track here.
** Package changed: xorg (Ubuntu) => ubuntu
** Changed in: ubuntu
Status: New => Invalid
--
You received this bug notification because you are a member of Desktop
Packages, which is
** Tags added: amdgpu
** Summary changed:
- Video does not output to second monitor
+ [amdgpu] Video does not output to second monitor
** Package changed: xorg (Ubuntu) => linux-hwe-6.5 (Ubuntu)
--
You received this bug notification because you are a member of Desktop
Packages, which is
The automated crash reports seem to suggest the problem stopped
happening around 20.10.
** Changed in: gnome-shell (Ubuntu)
Status: Confirmed => Fix Released
** Changed in: mutter (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a
*** This bug is a duplicate of bug 1961508 ***
https://bugs.launchpad.net/bugs/1961508
Thank you for taking the time to report this bug and helping to make
Ubuntu better. This particular bug has already been reported and is a
duplicate of bug 1961508, so it is being marked as such. Please
** Changed in: plymouth (Ubuntu)
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to plymouth in Ubuntu.
https://bugs.launchpad.net/bugs/2049179
Title:
Plymouth git repo is missing the most
** Affects: plymouth (Ubuntu)
Importance: Undecided
Assignee: Daniel van Vugt (vanvugt)
Status: In Progress
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to plymouth in Ubuntu.
https://bugs.launchpad.net/bugs/2049179
Title
** Changed in: gnome-shell (Ubuntu)
Assignee: Daniel van Vugt (vanvugt) => (unassigned)
** Changed in: gnome-shell (Ubuntu)
Status: In Progress => Triaged
** Changed in: gnome-shell (Ubuntu)
Importance: Medium => High
** Changed in: gnome-shell (Ubuntu)
Status
We think this might have been
https://gitlab.gnome.org/GNOME/mutter/-/issues/3112 for which there is
now a fix in mutter main, coming in 46.beta.
** Bug watch added: gitlab.gnome.org/GNOME/mutter/-/issues #3112
https://gitlab.gnome.org/GNOME/mutter/-/issues/3112
--
You received this bug
The version of Mesa installed: 24.0.0.20231114.1-2088~22.04 is not
supported or provided by Ubuntu. We cannot fix any bugs it causes.
** Package changed: xorg (Ubuntu) => ubuntu
** Changed in: ubuntu
Status: New => Invalid
--
You received this bug notification because you are a member
Without "use system title bar and borders" enabled, this feature is
entirely up to Chrome to implement so please report the bug at
https://bugs.chromium.org/p/chromium/issues/list
** Package changed: mutter (Ubuntu) => ubuntu
** Changed in: ubuntu
Status: New => Invalid
--
You received
See also bug 2049016.
--
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/1922414
Title:
Xorg scripts fail with "has_option: command not found"
Status in Light Display Manager:
Invalid
** Summary changed:
- ssh-agent fails to start (has_option: command not found)
+ Xorg scripts fail with "has_option: command not found"
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
From what I read of overnight discussions, it is believed that Mesa
23.3.3 has a fix. Looks like some kind of GLX protocol breakage happened
in 23.3.0?
** Also affects: mesa (Ubuntu)
Importance: Undecided
Status: New
** Changed in: mesa (Ubuntu)
Status: New => Fix Committed
--
** Bug watch added: github.com/micheleg/dash-to-dock/issues #2142
https://github.com/micheleg/dash-to-dock/issues/2142
** Also affects: dash-to-dock via
https://github.com/micheleg/dash-to-dock/issues/2142
Importance: Unknown
Status: Unknown
--
You received this bug notification
See also:
https://gitlab.freedesktop.org/drm/amd/-/issues/2803
https://gitlab.freedesktop.org/drm/amd/-/issues/1513
** Bug watch added: gitlab.freedesktop.org/drm/amd/-/issues #2803
https://gitlab.freedesktop.org/drm/amd/-/issues/2803
** Bug watch added:
Zooming in on the cursor images in GIMP I find they do contain gradients
- both Yaru and DMZ-Black. Therefore some greyness is correct.
I think the remaining bug here is that either the kernel (amdgpu) or
mutter is under-saturating the cursor plane with an alpha component
below 1.0. That's why I
Ideally please open a new bug for the merge. This bug should remain Fix
Released because we're already past the point in time when it was
released to Noble.
Please also remember to commit proposed changes to
https://git.launchpad.net/~bluetooth/bluez
** Changed in: bluez (Ubuntu)
Status:
** Tags added: noble
--
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/2048931
Title:
[noble] extension pref dialog turns hidden
Status in gnome-shell package in Ubuntu:
New
Bug
** Changed in: mesa (Ubuntu)
Status: Fix Committed => Fix Released
** Tags removed: fixed-in-mesa-23.3
** Tags added: fixed-in-mesa-23.3.0
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mutter in Ubuntu.
** Tags added: noble
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gjs in Ubuntu.
https://bugs.launchpad.net/bugs/2030947
Title:
gnome-shell spams journal with `g_closure_add_invalidate_notifier:
assertion 'closure->n_inotifiers <
Let's let it close automatically... if there are no more comments in two
months.
** Changed in: firefox (Ubuntu)
Status: Confirmed => Incomplete
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to firefox in Ubuntu.
I think starting in overview is the default upstream behaviour and we
only change it in the Ubuntu Dock extension. So it would be the Ubuntu
Dock failing here.
** Package changed: gnome-shell (Ubuntu) => gnome-shell-extension-
ubuntu-dock (Ubuntu)
--
You received this bug notification because
Looks like DBeaver is the main problem. Can you disable that?
** Package changed: gnome-shell (Ubuntu) => ubuntu
--
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/2047696
Title:
** Package changed: gnome-shell (Ubuntu) => mutter (Ubuntu)
** Also affects: mutter via
https://gitlab.gnome.org/GNOME/mutter/-/issues/3106
Importance: Unknown
Status: Unknown
** Changed in: mutter (Ubuntu)
Status: New => Confirmed
--
You received this bug notification
,
Hi Daniel,
Sorry the desktop recording is not smooth but we can see here that the
direction that take these two windows is not straight, there is a
sudden bend.
Just my feeling maybe, but that's not "sleek".
To manage notifications about this bug go to:
https://bugs.launchpad
048460
Title:
[noble] Odd overview animation
Status in GNOME Shell:
Unknown
Status in gnome-shell package in Ubuntu:
New
Bug description:
Hi all,
Hi Daniel,
Sorry the desktop recording is not smooth but we can see here that the
direction that take these two windows is not st
I think the relevant test case here is whether there are any crashes:
3.36.9-0ubuntu0.20.04.2 - 2878 crashes
3.36.9-0ubuntu0.20.04.3 - 0 crashes
So that's almost good enough. We probably just need someone to try
custom calendars in 20.04 like the test case mentions, in case of any
regressions.
This is currently blocked by bug 1915929.
--
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/2042796
Title:
Ubuntu 20.04: Buttons/icons at the edge of the touchscreen don't
respond
top
Packages, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/2048460
Title:
[noble] Odd overview animation
Status in mutter package in Ubuntu:
Incomplete
Bug description:
Hi all,
Hi Daniel,
Sorry the desktop recording is not smooth but we can see h
** Package changed: gnome-shell (Ubuntu) => gnome-shell-extension-
ubuntu-dock (Ubuntu)
--
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/2048448
Title:
Fix verified on mantic using version 45.2-0ubuntu3 and the test case at
the top of the page.
** Tags removed: verification-needed-mantic
** Tags added: verification-done-mantic
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mutter in
Please report the bug at:
https://gitlab.gnome.org/GNOME/mutter/-/issues
** Package changed: xserver-xorg-input-libinput (Ubuntu) => mutter
(Ubuntu)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mutter in Ubuntu.
*** This bug is a duplicate of bug 2043215 ***
https://bugs.launchpad.net/bugs/2043215
We can keep using bug 2043215 for this.
** This bug has been marked a duplicate of bug 2043215
Since upgrading to Ubuntu 23.10, the stylus (pen) does not work in Xorg.
--
You received this bug
The messiness mentioned in comment #7 should be avoidable starting in GNOME 46:
https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/3305
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
** Bug watch added: gitlab.gnome.org/GNOME/mutter/-/issues #230
https://gitlab.gnome.org/GNOME/mutter/-/issues/230
** Changed in: mutter
Status: Fix Released => Unknown
** Changed in: mutter
Remote watch: gitlab.gnome.org/GNOME/mutter/-/issues #1419 =>
** Summary changed:
- Screen crashes in a wierd way
+ [amdgpu] Screen crashes in a weird way
** Tags added: amdgpu
** Package changed: xorg (Ubuntu) => linux (Ubuntu)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
Deleting extensions is the only way forward here, in the absence of any
other ideas.
Local extensions are not officially supported, and are known to cause a
large proportion of gnome-shell bugs.
--
You received this bug notification because you are a member of Desktop
Packages, which is
Actually the issue I'm thinking of might be fixed by
https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/2620 coming in
mutter 46... If not already fixed in the kernel because it looks like
this bug only affects jammy?
--
You received this bug notification because you are a member of Desktop
Thinking about the most common cause of this error I've seen, can anyone
with multiple monitors confirm that it happens more on monitors that the
mouse pointer isn't on?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mutter in Ubuntu.
*** This bug is a duplicate of bug 1968040 ***
https://bugs.launchpad.net/bugs/1968040
Thank you for taking the time to report this bug and helping to make
Ubuntu better. This particular bug has already been reported and is a
duplicate of bug 1968040, so it is being marked as such. Please
** Tags added: nvidia-wayland
--
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/2047144
Title:
Black screen stays forever after inactivity
Status in mutter package in Ubuntu:
** No longer affects: xorg-server (Ubuntu)
--
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/2046224
Title:
[amdgpu] Resolutions lower than max results in corrupted screen
Status
Also your logs do show some very unusual apparently silent crashes. They
may be caused by your custom extensions so please try deleting them:
cd ~/.local/share/gnome-shell/
rm -rf extensions
and then log in again.
** Changed in: gnome-shell (Ubuntu)
Status: New => Incomplete
--
Thank you for taking the time to report this bug and helping to make
Ubuntu better. It sounds like some part of the system has crashed. To
help us find the cause of the crash please follow these steps:
1. Look in /var/crash for crash files and if found run:
ubuntu-bug YOURFILE.crash
Then tell
** Tags added: jammy lunar
--
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/1870454
Title:
gnome-shell crashed with SIGSEGV in meta_monitor_get_outputs
(monitor=0x0) from
If the above commands don't resolve the problem then please run:
gnome-extensions list --enabled
to see what's enabled and try disabling them.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
What is the make and model of the machine? It seems to identify itself
as "Default string".
** Package changed: xorg (Ubuntu) => linux-hwe-6.2 (Ubuntu)
** Changed in: linux-hwe-6.2 (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of
Is it correct to assign this to gnome-shell? Which process is using all
the CPU?
If it is gnome-shell then please start by deleting any local extensions:
cd ~/.local/share/gnome-shell/
rm -rf extensions
and log in again.
** Summary changed:
- Entire system becomes laggy for unknown reason
Only the kernel can crash that hard, so reassigning there.
** Package changed: xorg (Ubuntu) => linux-hwe-6.2 (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/2047388
Title:
** Summary changed:
- Screen brightness
+ [Lenovo IdeaPad Z500] Screen brightness
** Summary changed:
- [Lenovo IdeaPad Z500] Screen brightness
+ [Lenovo IdeaPad Z500] Brightness of the screen is down to minimum and I can't
change it
** Package changed: xorg (Ubuntu) => linux-hwe-6.2 (Ubuntu)
*** This bug is a duplicate of bug 2043956 ***
https://bugs.launchpad.net/bugs/2043956
Thank you for taking the time to report this bug and helping to make
Ubuntu better. This particular bug has already been reported and is a
duplicate of bug 2043956, so it is being marked as such. Please
** Tags added: amdgpu
** Package changed: xorg (Ubuntu) => linux-hwe-6.2 (Ubuntu)
** Summary changed:
- [drm] *ERROR* flip_done timed out
+ [amdgpu][drm] *ERROR* flip_done timed out
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg
Do you have an external monitor plugged in when the bug occurs?
** Package changed: xorg (Ubuntu) => mutter (Ubuntu)
** Tags added: hybrid i915 multigpu nvidia
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mutter in Ubuntu.
Next time the bug occurs, please reboot and then run:
journalctl -b-1 > prevboot.txt
and attach the resulting text file here.
** Changed in: mutter (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Desktop
Packages, which is
Please provide a screenshot or photo of the problem so we have a better
idea of where to direct the bug.
** Tags added: mantic
** Package changed: gnome-desktop (Ubuntu) => ubuntu
** Changed in: ubuntu
Status: New => Incomplete
--
You received this bug notification because you are a
** Package changed: gdm (Ubuntu) => gdm3 (Ubuntu)
** Tags added: ad arm64
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gdm3 in Ubuntu.
https://bugs.launchpad.net/bugs/2046847
Title:
Ubuntu Desktop fails to login with Active
That might be an amdgpu-specific issue. Sadly it doesn't seem common
enough to show up in the top 100 gjs crashes for 22.04:
https://errors.ubuntu.com/?release=Ubuntu%2022.04=gjs=month
It sounds like this bug though:
https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/6747
which is fixed in
Indeed the kernel seems to be crashing in drm graphics code so I'd
recommend trying some newer kernels such as
https://kernel.ubuntu.com/mainline/?C=M;O=D
** Package changed: xorg (Ubuntu) => linux (Ubuntu)
** Tags added: amdgpu dock multimonitor
--
You received this bug notification because
That's odd because 3440x1440 actually has lower bandwidth requirements
(fewer pixels) than 3840x2160. Still, to go above 60Hz you will need
both your HDMI cable and your graphics card to be capable of HDMI 2.1,
not just 2.0.
Please tell us the model of graphics card you are using. If you're just
Thank you for taking the time to report this bug and helping to make
Ubuntu better. It sounds like some part of the system has crashed. To
help us find the cause of the crash please follow these steps:
1. Run these commands:
journalctl -b0 > journal.txt
journalctl -b-1 > prevjournal.txt
Does "screen is too bright" mean the backlight brightness can't be
adjusted?
** Package changed: xorg (Ubuntu) => linux (Ubuntu)
** Changed in: linux (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Desktop
Packages, which is
Please don't use xserver-xorg-video-intel because it's buggy and
deprecated. The default Xorg driver ('modesetting') is the correct
driver.
I will make this bug about the screen being too bright. If you want to
discuss "3rd class video quality" then please open a new bug for that...
** Summary
On laptop screens, non-max resolutions are faked. They should work
obviously, but it's up to the display server and kernel driver to fake
it properly.
Do you experience the same issue in a Wayland session?
** Tags added: amdgpu
** Summary changed:
- Resolutions lower than max results in
The attached files show that the kernel does indeed have an 'nvidia'
driver but it's not being used for some reason. And Xorg, as of Dec 11
at least, does not have any knowledge of an Nvidia card.
Please run:
lspci -k > lspci.txt
journalctl -b0 > journal.txt
and attach the resulting text
Thanks Ladar, that workaround works great for me. Exactly what I needed.
I have a keyboard that _only_ has a right meta key that I often plug in
to my laptop (Kinesis Advantage). My laptop, however, _only_ has a left
meta key.
--
You received this bug notification because you are a member of
It doesn't look like you have a working Nvidia driver installed. Please
try using the 'Additional Drivers' app to install an Nvidia driver.
** Package changed: xorg (Ubuntu) => xorg-server (Ubuntu)
** Changed in: xorg-server (Ubuntu)
Status: New => Incomplete
** Tags added: multimonitor
This is a feature of most terminals and editors. If you're typing then
they expect that hiding the mouse cursor is helpful to not cover any
text.
** Package changed: xorg (Ubuntu) => ubuntu
** Changed in: ubuntu
Status: New => Invalid
--
You received this bug notification because you
Thank you for taking the time to report this bug and helping to make
Ubuntu better. It sounds like some part of the system has crashed. To
help us find the cause of the crash please follow these steps:
1. Look in /var/crash for crash files and if found run:
ubuntu-bug YOURFILE.crash
Then tell
Sound and display coexisting on the same HDMI cable would be a kernel
issue so reassigning...
** Package changed: mutter (Ubuntu) => linux (Ubuntu)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mutter in Ubuntu.
** No longer affects: mutter (Ubuntu)
--
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/2039570
Title:
[amdgpu] Fullscreen in any Wayland / Xwayland window shows a black
screen (no
Yes it looks like the fix here only made it into Ubuntu 22.10 and later.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-session in Ubuntu.
https://bugs.launchpad.net/bugs/1968907
Title:
GLib-GIO-CRITICAL: g_bus_get_sync:
.
** Changed in: mutter (Ubuntu)
Status: Fix Released => Confirmed
** Tags added: jammy
** Changed in: mutter (Ubuntu)
Assignee: Daniel van Vugt (vanvugt) => (unassigned)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mutter in
** Changed in: gnome-control-center (Ubuntu)
Status: Won't Fix => Fix Committed
** Tags added: fixed-in-gnome-control-center-46 fixed-upstream
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-control-center in Ubuntu.
** Changed in: mutter (Ubuntu)
Status: Incomplete => New
--
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/1804568
Title:
[HP Spectre x360 Convertible 13] click position is
** Changed in: gnome-shell (Ubuntu)
Status: In Progress => Fix Committed
** Tags added: fixed-in-gnome-shell-46 fixed-upstream
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
PPAs are not supported, but also the 390 driver is not supported by any
Ubuntu release after 23.04 (which explains why you're using a PPA).
If you require Nvidia driver 390 then please stick to Ubuntu 22.04 where
it is formally supported until April 2032.
** No longer affects: xorg (Ubuntu)
**
Public bug reported:
Release BlueZ 5.71 to noble.
** Affects: bluez (Ubuntu)
Importance: Medium
Assignee: Daniel van Vugt (vanvugt)
Status: Triaged
** Tags: noble
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed
Public bug reported:
Just noticed ```.xsession-errors``` somewhat big with a timestamp from
today.
After checking the log out I mostly see:
```
(caja:2681): GLib-GIO-CRITICAL **: 17:16:08.920: GFileInfo created without
standard::sort-order
(caja:2681): GLib-GIO-CRITICAL **: 17:16:08.920: file
After searching around it seems this problem is both obscure and old:
https://askubuntu.com/questions/1419371/error-during-booting-
ubuntu-22-04-glib-gio-critical
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to glib-networking in Ubuntu.
** Description changed:
[ Impact ]
There is heavy stuttering visible in Firefox with mutter 45.1/45.2 when
kinetic scrolling a non-animated web page with a touchpad. This is a
regression introduced upstream in mutter 45.1 (8f27ebf8).
[ Test Plan ]
0. Find a laptop with a
Proposed fix for 45.2 (we usually go through Debian first because that's where
the patch is maintained):
https://salsa.debian.org/gnome-team/mutter/-/merge_requests/114
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mutter in Ubuntu.
Also verified fixed in mantic using version 45.2-0ubuntu2~really45.0 and
the test case that's now in the Bug Description above.
** Description changed:
[ Impact ]
There is heavy stuttering visible in Firefox with mutter 45.1/45.2 when
kinetic scrolling a non-animated web page with a
** Description changed:
- There is heavy stuttering visible in Firefox with mutter 45.1/45.2. This
- is a regression introduced upstream in mutter 45.1 (8f27ebf8), although
- it only hurts the triple buffering patch so that's where it's fixed:
+ [ Impact ]
+
+ There is heavy stuttering visible
Zenbook,
using Wayland desktop. My system has both Nvidia and AMD graphics, but
Wayland is configured to use the AMD graphics I believe.
#uname -a
Linux daniel-ZenBook 6.5.0-14-generic #14-Ubuntu SMP PREEMPT_DYNAMIC Tue Nov 14
14:59:49 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux
#cat /etc/lsb-release
** Tags removed: regression-proposed
** Tags added: regression-update
--
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/2046360
Title:
Heavy stuttering in Firefox with mutter 45.1/45.2
** Summary changed:
- Heavy stuttering in mutter 45.1/45.2 (especially Firefox)
+ Heavy stuttering in Firefox with mutter 45.1/45.2
** Description changed:
- There is heavy stuttering in mutter 45.1/45.2 (especially Firefox)
-
- This is a regression introduced upstream in mutter 45.1, although
Public bug reported:
There is heavy stuttering in mutter 45.1/45.2 (especially Firefox)
This is a regression introduced upstream in mutter 45.1, although it
only hurts the triple buffering patch so that's where it's fixed:
** Package changed: gnome-shell (Ubuntu) => ubuntu
--
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/2043538
Title:
gnome-shell takes too much ram
Status in Ubuntu:
Incomplete
https://warthogs.atlassian.net/browse/UDENG-1937 will need to be solved
before this can progress.
--
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/2042796
Title:
Ubuntu 20.04:
** Changed in: gnome-shell (Ubuntu Focal)
Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0)
--
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/1915929
Title:
801 - 900 of 35600 matches
Mail list logo
