The workaround from #71 worked almost perfectly out of the box, I've
only seen 1-2 windows staying under the dock. I probably simply need
bump the delay a bit from the default value.
Thanks a lot @popov895. @ballogy, thanks for working on this with
upstream!
--
You received this bug
** Merge proposal linked:
https://code.launchpad.net/~p-pisati/britney/+git/hints-ubuntu/+merge/461043
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to devhelp in Ubuntu.
https://bugs.launchpad.net/bugs/2046844
Title:
AppArmor
Public bug reported:
Attempting to start Evolution results in "Segmentation fault (core
dumped)". Don't know where the core dump ends up.
The "--disable-eplugin --disable-preview --offline" make no difference
Running under GDB gives:
the solution to not lose the configuration after the reboot :
sudo nano /etc/rc.local
The bash:
#!/bin/bash
# Votre commande ici
sudo sysctl -w kernel.apparmor_restrict_unprivileged_userns=0
sudo chmod +x /etc/rc.local
--
You received this bug notification because you are a member of Ubuntu
This bug was fixed in the package ghostwriter - 23.08.5+ds-0ubuntu1
---
ghostwriter (23.08.5+ds-0ubuntu1) noble; urgency=medium
* New upstream release (23.08.5)
ghostwriter (23.08.4+ds-0ubuntu2) noble; urgency=medium
* Add apparmor profile to fix userns. (LP: #2046844)
--
** Changed in: glib2.0 (Ubuntu)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to glib2.0 in Ubuntu.
https://bugs.launchpad.net/bugs/2053207
Title:
glib requires gobject-introspection >=
Public bug reported:
Hello,
got a crash window debug at GIMP exit with "To help us improve GIMP, you can
report the bug ..." message
There it is
% lsb_release -rd
No LSB modules are available.
Description:Ubuntu 23.10
Release:23.10
% LANG=C apt-cache policy gimp
gimp:
Installed:
You have been subscribed to a public bug by Zalán Hári (zalanhari):
I was an unpatient idiot, and I upgraded from 22.04 to 24.04. Near to
the end of the upgrade, I got an „Oh, no! Something has gone wrong and
the system cannot recover. Call the system administrator” message after
a red FAILED in
Thank you for taking the time to report this bug and helping to make
Ubuntu better.
However, processing it in order to get sufficient information for the
developers failed (it does not generate an useful symbolic stack trace).
This might be caused by some outdated packages which were installed on
Most likely this crash was caused by using new glib at runtime at local testing
"using GLib version 2.79.2 (compiled against version 2.78.0)".
and doesn't occur with packaged version, so that please close this bug report.
--
You received this bug notification because you are a member of Ubuntu
Fix proposed:
https://gitlab.freedesktop.org/plymouth/plymouth/-/merge_requests/307
--
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/2054769
Title:
Boot animation and login screen
It looks like plymouth's threshold for scale 200% is 192 DPI. And gnome-
shell's threshold is 135 DPI. Since my laptop with the bug is 201 DPI it
should be scale 200% for both mutter and plymouth. I think there's a
simple math error in mutter though, leading to 100% being chosen instead
of 200%.
The attachment "library.py" seems to be a patch. If it isn't, please
remove the "patch" flag from the attachment, remove the "patch" tag, and
if you are a member of the ~ubuntu-reviewers, unsubscribe the team.
[This is an automated message performed by a Launchpad user owned by
~brian-murray,
** Changed in: plymouth (Ubuntu)
Status: Opinion => 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/2054769
Title:
Boot animation and login screen use different
(In reply to Michael Catanzaro from comment #62)
> Hi Craig and Thomas (and Emil if you're still around): if you're still
> encountering problems with NVIDIA graphics, please report new a bug and
> leave a comment here linking to the new bug.
My problem was on legacy nvidia driver, and newer
Public bug reported:
Crashed after unlocking session from being away for a couple days.
Crash report ID is c81ddc34-d487-11ee-ba77-fa163e171f02
** Affects: mutter (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Sorry, there is a mistake in my bug report: the critical GTK error
occurs when I close gedit.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gedit in Ubuntu.
https://bugs.launchpad.net/bugs/2055010
Title:
Gedit has an invalid
Turns out we don't need to change mutter at all. I just failed to
understand its complicated scale selection rules. I've proposed a
simplification to mutter anyway:
https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/3616
but it's no longer required to fix this bug.
** Changed in: mutter
Bug driver 470, Nvidia GTX 650
W dniu 26.02.2024 o 04:06, Craig pisze:
> (In reply to Michael Catanzaro from comment #62)
>> Hi Craig and Thomas (and Emil if you're still around): if you're still
>> encountering problems with NVIDIA graphics, please report new a bug and
>> leave a comment here
Public bug reported:
Hello.
I report a bug or supposed to be a bug concerning GIMP. I had worked
with GIMP without pb.
When closing the GIMP session, I got a crash (Refer to reported info
below).
My configuration is Kubuntu 24.04 (Dev) Noble updated daily.
I remain available to provide
20 matches
Mail list logo
