*** This bug is a duplicate of bug 2022851 ***
https://bugs.launchpad.net/bugs/2022851
It seems the same as bug #2022851 which should be fixed with the gtk4
candidate update in lunar-proposed
** This bug has been marked a duplicate of bug 2022851
Nautilus displays invalid directory content
Thank you for your bug report. It sounds like that could be the same
cause than bug #2022851, could you try if the gtk4 update in lunar-
proposed fixes the issue for you?
** Changed in: nautilus (Ubuntu)
Status: Confirmed => Incomplete
--
You received this bug notification because you are
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: gnome-shell (Ubuntu)
Status: New => Confirmed
--
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.ne
** Changed in: gnome-shell (Ubuntu)
Status: New => Triaged
--
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/2013042
Title:
Lock screen wallpaper vanishes (goes black) if a
We've narrowed a related (hopefully the same) issue down to being
introduced in mutter!1968, which is the precursor to triple buffering.
Not triple buffering itself, but part of the same patch.
https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1441#note_1757415
** Changed in: gnome-shell (Ub
*** This bug is a duplicate of bug 2022851 ***
https://bugs.launchpad.net/bugs/2022851
I confirm this is fixed when switching to lunar-proposed. Thank you very
much.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to nautilus in Ubun
Drag and drop crashes are likely to be fixed in the 44.1 update (bug
2012230, bug 2012100). But if you want to debug your particular case
further then please follow:
https://wiki.ubuntu.com/Bugs/Responses#Missing_a_crash_report_or_having_a_.crash_attachment
** Changed in: gnome-shell (Ubuntu)
** Changed in: mutter (Ubuntu)
Status: Won't Fix => Confirmed
** Tags removed: bionic
** Tags added: jammy
--
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/1778983
Title:
Resu
** Tags removed: bionic
** Tags added: focal
** Changed in: mutter (Ubuntu)
Status: Won't Fix => New
--
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/1755501
Title:
GfxBench r
That's a lot of private proprietary bugs. Are you sure you can't close
most of them as duplicates of each other?
--
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/1966635
Title:
can't
*** This bug is a security vulnerability ***
Public security bug reported:
I have no details to provide sorry.
This is a QA test install only.. with packages & VERY MINOR change(s)
having taken place on it ...
ProblemType: Crash
DistroRelease: Ubuntu 23.10
Package: evolution-data-server (not in
Registered to add this comment thanking Eneko and AlfyBoy for their
contributions.
TLDR: It worked !
Background - I had been using Ubunto 18.04 LTS with a gimp with several
python plugins that I use a lot - a contact sheet generator, and a path
distance pixel counter in particular.
The EOL of U
Private bug 2016299 now has more complete stack traces.
--
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/2015386
Title:
NVIDIA quad-GPU system crashes starting Wayland session
To man
The steps to reproduce at the top of this page appear to be independent
of DCV(?). And even if they weren't, then simply verifying the patch is
present would suffice.
We don't want to skip lunar since it's theoretically a generic bug that
could occur without DCV.
--
You received this bug notific
** Tags added: jammy
--
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/2021987
Title:
The gnome session doesn't work when connected via XDMCP
To manage notifications about this bug go t
** Package changed: gnome-shell (Ubuntu) => gtk+3.0 (Ubuntu)
** Also affects: gtk4 (Ubuntu)
Importance: Undecided
Status: New
--
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/
Thanks. Your journal.txt shows gnome-shell is crashing in:
/home/leon/.local/share/gnome-
shell/extensions/topiconsfix@ales...@devnullmail.com
so please delete that extension. It's also not supported here.
** Changed in: gnome-shell (Ubuntu)
Status: Incomplete => Invalid
--
You receive
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
You have been subscribed to a public bug:
In the superior right corner, there are a region (about 5x5 cm2) that
mouse do nothing, mainly in minimize and close butons, but ocouring to
in menus, just in this corner.
Double click in title bar force the restore and then, moving the
software window to
*** This bug is a duplicate of bug 2012388 ***
https://bugs.launchpad.net/bugs/2012388
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 2012388, so it is being marked as such. Please look
Thanks for the bug report. I would usually recommend trying
MUTTER_DEBUG_ENABLE_ATOMIC_KMS=0 to fix this but your logs seem to
suggest that mode is already active.
Please:
1. Try disabling these extensions in case they're having some effect:
'impatie...@gfxmonk.net',
'clipboard-indica...@d
Thanks for the bug report. Please start by deleting all local
extensions:
cd ~/.local/share/gnome-shell/
rm -rf extensions
and then log in again.
If the problem still occurs then please:
1. Look in /var/crash for crash files and if found run:
ubuntu-bug YOURFILE.crash
Then tell us the I
Sounds like https://github.com/micheleg/dash-to-dock/issues/2024 which
is apparently a regression in version 82.
** Bug watch added: github.com/micheleg/dash-to-dock/issues #2024
https://github.com/micheleg/dash-to-dock/issues/2024
** Also affects: dash-to-dock via
https://github.com/michel
You have been subscribed to a public bug:
Steps to reproduce:
* Install fresh Ubuntu 22.04.2 LTS
* Enable RDP and VNC via sharing control panel
* Test RDP and VNC, verify working
* Unplug monitor
* Try RDP. Authenticate, then connection closed with no display
* Try VNC. Authenticate, then
** Package changed: xorg (Ubuntu) => gnome-shell (Ubuntu)
--
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/2022954
Title:
RDP and VNC fail when headless with no monitor (but work
Yeah I know, mentioned in comment #11:
> * I can still reproduce the failure to revert when using the PPA
version 42.5-0ubuntu1vv1 (fractional scaling support removed, so using
integer scaling).
What I was trying to say in comment #16 is not that fractional scaling
was the cause of this bug, but
Oh actually the logs you provided in comment #17 suggest that the
fractional scaling patch is trying to implement the revert using
fractional scaling (which will fail on Xdcv) even when the feature is
disabled. So it sounds like I need to make a new PPA revision that has
both the changes of vv1 and
They are used for different platform of different OEM. The OEM platform
owner tracks specific platform bugs by platform tag in the private bug
and we are not able to share the platform information cross OEM.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, w
> [flatpak search meld] produces 3,010 spurious identical error messages
That's https://github.com/ximion/appstream/issues/384, which is a
libappstream bug that cannot be fixed by a Flatpak change (as much as we
might like to). I contributed a fix which was included in appstream
0.15.3, so this SR
I don't see a report so I presume this is OK to release?
--
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/2015861
Title:
cursor does not track window when dragging between monitors wi
This bug was fixed in the package gnome-shell - 44.1-0ubuntu1
---
gnome-shell (44.1-0ubuntu1) lunar; urgency=medium
[ Jarred Wilson ]
* New upstream release (LP: #2020277, LP: #1968383)
* Drop patches applied in new release
* Rebase patches
[ Jeremy Bicha ]
* Drop patch t
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 encount
This bug was fixed in the package mutter - 44.1-0ubuntu1
---
mutter (44.1-0ubuntu1) lunar; urgency=medium
[ Jeremy Bícha ]
* New upstream release (LP: #2020225, LP: #2012717, LP: #2013216,
LP: #2015861, LP: #2017097)
* debian/libmutter-12-0.symbols: Add new symbols
* Drop
The verification of the Stable Release Update for mutter 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 r
This bug was fixed in the package mutter - 44.1-0ubuntu1
---
mutter (44.1-0ubuntu1) lunar; urgency=medium
[ Jeremy Bícha ]
* New upstream release (LP: #2020225, LP: #2012717, LP: #2013216,
LP: #2015861, LP: #2017097)
* debian/libmutter-12-0.symbols: Add new symbols
* Drop
The verification of the Stable Release Update for mutter 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 r
This bug was fixed in the package mutter - 44.1-0ubuntu1
---
mutter (44.1-0ubuntu1) lunar; urgency=medium
[ Jeremy Bícha ]
* New upstream release (LP: #2020225, LP: #2012717, LP: #2013216,
LP: #2015861, LP: #2017097)
* debian/libmutter-12-0.symbols: Add new symbols
* Drop
The verification of the Stable Release Update for mutter 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 r
This bug was fixed in the package mutter - 44.1-0ubuntu1
---
mutter (44.1-0ubuntu1) lunar; urgency=medium
[ Jeremy Bícha ]
* New upstream release (LP: #2020225, LP: #2012717, LP: #2013216,
LP: #2015861, LP: #2017097)
* debian/libmutter-12-0.symbols: Add new symbols
* Drop
The verification of the Stable Release Update for mutter 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 r
This bug was fixed in the package mutter - 44.1-0ubuntu1
---
mutter (44.1-0ubuntu1) lunar; urgency=medium
[ Jeremy Bícha ]
* New upstream release (LP: #2020225, LP: #2012717, LP: #2013216,
LP: #2015861, LP: #2017097)
* debian/libmutter-12-0.symbols: Add new symbols
* Drop
The verification of the Stable Release Update for mutter 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 r
This bug was fixed in the package mutter - 44.1-0ubuntu1
---
mutter (44.1-0ubuntu1) lunar; urgency=medium
[ Jeremy Bícha ]
* New upstream release (LP: #2020225, LP: #2012717, LP: #2013216,
LP: #2015861, LP: #2017097)
* debian/libmutter-12-0.symbols: Add new symbols
* Drop
The verification of the Stable Release Update for mutter 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 r
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 encount
This bug was fixed in the package gnome-shell - 44.1-0ubuntu1
---
gnome-shell (44.1-0ubuntu1) lunar; urgency=medium
[ Jarred Wilson ]
* New upstream release (LP: #2020277, LP: #1968383)
* Drop patches applied in new release
* Rebase patches
[ Jeremy Bicha ]
* Drop patch t
> Therefore, the crash is fixed even though there is still a remaining
bug.
Does this bug need reopening then, or a new bug filed? I leave that up
to you - setting Incomplete for now since that's better than Fix
Released and this being forgotten.
** Changed in: gnome-shell (Ubuntu Lunar)
S
** Changed in: mutter (Ubuntu Lunar)
Status: Triaged => In Progress
--
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/2022951
Title:
Update mutter to 44.2
To manage notificatio
We are working on getting mutter 44.2 with this update to the triple
buffering patch into Ubuntu 23.04.
I was unable to easily duplicate this crash in my testing so I am not
mentioning this bug in the debian/changelog. We need clear test cases
for bugs in Stable Release Update changelogs.
--
You
** Changed in: mutter (Ubuntu Lunar)
Status: Triaged => In Progress
--
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/2013235
Title:
Drag and Drop not working in Qt-Applications
** Changed in: gnome-shell (Ubuntu Lunar)
Status: Triaged => In Progress
** Description changed:
Impact
--
There is a new bugfix release in the stable 44 series.
https://gitlab.gnome.org/GNOME/gnome-shell/-/blob/44.2/NEWS
Test Case
-
Complete all the non-opt
** Description changed:
Impact
--
There is a new bugfix release in the stable 44 series.
https://gitlab.gnome.org/GNOME/mutter/-/blob/44.2/NEWS
+
+ This is basically a prerequisite for GNOME Shell 44.2 LP: #2022961
Test Case
-
Complete the test case from
https://
This debdiff contains a minimal fix to resolve the noisy assertions (and
potential crash) when searching for AppStream data.
It should be suitable for upload to Jammy.
@tintou, sorry for hijacking the SRU report a bit, in hindsight I should
probably have filed a new one. This should address the m
Public bug reported:
[ Impact ]
* Currently, any application that is using modern AppStream metadata
containing / tags in their description, and that is still using the
deprecated appstream-glib will fail to parse this data.
* Unfortunately, this affects some high-visibility applications now,
@jurgen-schellaert-j I didn't mean to move cursor outside the window, I
meant to move over white space inside the files view, like the white
space between files/folders or beneath files/folders when they don't
cover the entire view. Moving cursor outside nautilus negates the bug.
--
You received
Just to iterate here: this problem only effects X11. It's already fixed
in GTK 4.8.3 and 4.10.1 for Wayland.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to nautilus in Ubuntu.
https://bugs.launchpad.net/bugs/2017716
Title:
Folders
You have been subscribed to a public bug:
Frequently, windows such as the new text editor, or the nautilus file
browser, or modal dialogs seem to have an in valid z-index, i.e. I
cannot click the title bar, and the window is virtually behind
everything. The window also has a flickering halo full
** Changed in: shotwell (Ubuntu)
Status: Triaged => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to shotwell in Ubuntu.
https://bugs.launchpad.net/bugs/1979312
Title:
Shotwell 0.32 released 2023-04-22, please up
** Package changed: ubuntu-meta (Ubuntu) => mutter (Ubuntu)
--
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/2023209
Title:
Windows get wrong z-index and flickering decoration halo
T
** Also affects: gtk4 (Ubuntu)
Importance: Undecided
Status: New
** Changed in: gtk4 (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to nautilus in Ubuntu.
https://bugs.launchpad.net/bug
Hey Marc,
Per your request, bug number is:
#2522
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu.
https://bugs.launchpad.net/bugs/1983778
Title:
Major security issue in Ubuntu Desktop default config -
** Bug watch added: gitlab.gnome.org/GNOME/gnome-control-center/-/issues #2522
https://gitlab.gnome.org/GNOME/gnome-control-center/-/issues/2522
** Also affects: gnome-control-center via
https://gitlab.gnome.org/GNOME/gnome-control-center/-/issues/2522
Importance: Unknown
Status: U
Daniel,
Thanks for chiming in.
I've tried reproducing this bug outside of DCV, but no lucky.
What I tried last is to launch a baremetal instance on AWS (g4dn.metal)
with the same Nvidia GPUs as the instance type where we are consistently
able to reproduce this problem, and then I:
1. Installed
** Changed in: appstream (Ubuntu)
Status: Confirmed => Fix Released
** Changed in: appstream (Ubuntu Jammy)
Status: New => Triaged
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to appstream in Ubuntu.
https://bugs.launchp
** Changed in: gnome-control-center
Status: Unknown => New
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu.
https://bugs.launchpad.net/bugs/1983778
Title:
Major security issue in Ubuntu Desktop
This bug was fixed in the package shotwell - 0.32.1-0ubuntu1
---
shotwell (0.32.1-0ubuntu1) mantic; urgency=medium
[ Jeremy Bícha ]
* New upstream release (LP: #1979312)
* Drop all patches: applied in new release
* debian/control: Switch to libsoup3 and webkit2gtk-4.1
* debi
Hi thank you, I tried but it did not work. I left a message saying:
If it helps, I enabled proposed, updated but the issue is still there.
Maybe I needed to wait some more for the proposed repositories to show
the correct packages?
--
You received this bug notification because you are a member o
*** This bug is a duplicate of bug 2022851 ***
https://bugs.launchpad.net/bugs/2022851
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: nautilus (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubu
I have confirmed the existence of ubuntu/flush-signal-handler-on-udev-
settle.patch in https://launchpad.net/ubuntu/+source/gdm3/44.0-1ubuntu2
which is the best we can do for lunar.
** Tags removed: verification-needed-lunar
** Tags added: verification-done-lunar
--
You received this bug notifi
On second thoughts, patching lunar is unlikely to be useful. So long as
the fix is in mantic for future releases, that's enough.
** Tags removed: verification-done-lunar
** Tags added: verification-needed-lunar
** Changed in: gdm3 (Ubuntu Lunar)
Status: Fix Committed => Won't Fix
** Chang
Thank you for taking the time to report this bug and helping to make
Ubuntu better. Please execute the following command only once, as it
will automatically gather debugging information, in a terminal:
apport-collect 2023209
When reporting bugs in the future please use apport by using 'ubuntu-
Also it sounds like you are describing bug 2013216 and bug 2020674, both
of which have had fixes released in the past week. So please try
updating your system:
sudo apt update
sudo apt full-upgrade
and reboot. The packages you need to get the fixes are:
libmutter-12-0 version 44.1-0ubuntu1
Tracking upstream in https://gitlab.gnome.org/GNOME/mutter/-/issues/2853
** Bug watch added: gitlab.gnome.org/GNOME/mutter/-/issues #2853
https://gitlab.gnome.org/GNOME/mutter/-/issues/2853
** Also affects: mutter via
https://gitlab.gnome.org/GNOME/mutter/-/issues/2853
Importance: Unknow
** Changed in: mutter
Status: Unknown => New
--
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/2015955
Title:
gnome-shell crashed with SIGSEGV in wl_resource_add_destroy_listene
If you are seeing:
error_code 8 request_code 147 (unknown) minor_code 6
then it might be:
https://gitlab.gnome.org/GNOME/mutter/-/issues/2857
** This bug is no longer a duplicate of bug 2014986
gnome-shell crashed with signal 5 [The error was 'BadMatch (invalid
parameter attributes)'.
If you are seeing:
error_code 8 request_code 147 (unknown) minor_code 6
then it might be:
https://gitlab.gnome.org/GNOME/mutter/-/issues/2857
** This bug is no longer a duplicate of bug 2014986
gnome-shell crashed with signal 5 [The error was 'BadMatch (invalid
parameter attributes)'. (
76 matches
Mail list logo
