No the gsettings did not help, also not after a reboot.
--
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/1947187
Title:
[amdgpu] Graphics corruption during modal dialog dimming on
I just found that this problem is not present in Debian testing, even if
they have the same version of both mutter and ibus. Something seems to
make Xwayland start at login, and hence ibus-x11 is also running.
That speaks against using im-config to work around it, since im-config
is used by both
Does this work around the problem?
gsettings set org.gnome.mutter attach-modal-dialogs false
** Tags added: amdgpu
** Summary changed:
- Running in xorg unreadable firefox password request
+ [amdgpu] Graphics corruption during modal dialog dimming
** Package changed: xorg (Ubuntu) => mutter
This is almost certainly a bug in conky, since countless other apps
support Wayland sessions just fine. Reassigning.
** Package changed: wayland (Ubuntu) => mutter (Ubuntu)
** Summary changed:
- Wayland does not initially display conky output
+ GNOME on Wayland does not initially display conky
You have been subscribed to a public bug:
If I use xorg and Firefox asks for the master password that small window
is unreadable and distorted. See the screenshot. If I type in the
password blindly everything is working again. The problem does not exist
with Wayland, but that one has another
You have been subscribed to a public bug:
Starting Ubuntu with wayland does not initially display the .conkyrc
file. Only after a change in that file, conky restarts the display and
.conkyrc is displayed. Conky has been started according to the system
monitor. I doubled the time before starting
Thanks! That one was waiting for sponsorship almost nine months.
--
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/1898005
Title:
gnome-shell crashed with SIGABRT in
Thanks Karsten, it works!
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to evince in Ubuntu.
https://bugs.launchpad.net/bugs/1915910
Title:
evince does not print
To manage notifications about this bug go to:
$ dput
gnome-shell-extension-desktop-icons_20.04.0-3\~ubuntu20.04.4_source.changes
Trying to upload package to ubuntu
Checking signature on .changes
gpg:
/tmp/pkgs/focal/gnome-shell-extension-desktop-icons_20.04.0-3~ubuntu20.04.4_source.changes:
Valid signature from 1E918B66765B3E31
Checking
I sponsored the patch in comment #28 after updating the changelog as
some new versions of that package came out.
--
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/1898005
Title:
This has been fixed on the GNOME side. Can we have this backported?
I'm willing to do the backport, if it will get merged.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-settings-daemon in Ubuntu.
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 Ubuntu
Desktop Bugs, which is subscribed to nautilus in Ubuntu.
I am facing the exact same error in the exact same configuration
$ lsb_release -rd
Description:Ubuntu 20.04.3 LTS
Release:20.04
$ apt-cache policy nautilus
nautilus:
Installed: 1:3.36.3-0ubuntu1
Candidate: 1:3.36.3-0ubuntu1
Version table:
*** 1:3.36.3-0ubuntu1 500
500
> When that reaches Debian, there is a risk that Ubuntu's desktop team
won't accept to keep mozc in main (and on the ISO).
I think so too. Unfortunately the Qt renderer and Gtk renderer seem to
be exclusive at the moment. We still need Gtk renderer.
> > However ibus-x11 process is doubled, it is
On 2021-10-14 15:43, Ikuya Awashiro wrote:
>> It would be good if any of you could submit an upstream GNOME issue.
> I think it is not mutter or gnome-shell issue but ibus-mozc issue.
> ibus-mozc should work under wayland session.
> Latest Mozc renderer was completely re-written.
>
Upstream proposed a fix in
https://gitlab.gnome.org/GNOME/gdm/-/merge_requests/160 and describe the
crash as being an issue when neither wayland nor xorg is working. Could
someone describe in which kind of setup they encounter the error?
--
You received this bug notification because you are a
** Changed in: gdm3 (Ubuntu)
Milestone: ubuntu-21.10 => impish-updates
--
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/1945061
Title:
gdm3 crashed with SIGSEGV in
Hi Gunnar,
> In the meantime im-config is the natural package for a workaround.
This PPA:
It works for me. Thank you for your quick response!
However ibus-x11 process is doubled, it is ok?
PIDPGID SID TTY STAT TIME COMMAND
140014001400 ?Ssl0:00
Thank you for your comments!
> However to reproduce this behaviour, you need to reboot on twice, isn't it?
Yes. You are right. Always right.
> It would be good if any of you could submit an upstream GNOME issue.
I think it is not mutter or gnome-shell issue but ibus-mozc issue.
ibus-mozc should
** Package changed: ubuntu => gnome-shell-extension-ubuntu-dock (Ubuntu)
--
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/1947149
Title:
dock auto-hide off
You have been subscribed to a public bug:
When the dock is set to "Auto-hide the Dock" = Off, the dock will un-
hide when logging on. Both on boot and after locking the user. This
causes any open full-screen windows to move and resize as needed.
1) The release of Ubuntu you are using, via
*** This bug is a duplicate of bug 1871262 ***
https://bugs.launchpad.net/bugs/1871262
Your system log ends with:
[ 327.514699] ozmodiar gnome-shell[3502]:
meta_window_set_stack_position_no_sync: assertion
'window->stack_position >= 0' failed
So yes I think bug 1871262 is appropriate even
** Summary changed:
-
/usr/bin/gnome-shell:11:XRRGetCrtcInfo:update_outputs:_cogl_xlib_renderer_connect:_cogl_winsys_renderer_connect:connect_custom_winsys
+ gnome-shell crashed with SIGSEGV in XRRGetCrtcInfo() from update_outputs()
from _cogl_xlib_renderer_connect() from
Public bug reported:
The Ubuntu Error Tracker has been receiving reports about a problem regarding
gnome-shell. This problem was most recently seen with package version
40.5-1ubuntu2, the problem page at
https://errors.ubuntu.com/problem/2acefc8fc5476d2f02ae266fe5892dd8bffc1fed
contains more
** Changed in: gnome-shell (Ubuntu)
Status: Incomplete => Fix Released
--
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/1936826
Title:
gnome-shell crashed with SIGSEGV in
** Summary changed:
-
/usr/bin/gnome-shell:11:js::gc::Cell::storeBuffer:JSObject::writeBarrierPost:js::InternalBarrierMethods:js::InternalBarrierMethods:js::BarrierMethods
+ gnome-shell crashed with SIGSEGV in
js::gc::Cell::storeBuffer:JSObject::writeBarrierPost from
js::InternalBarrierMethods
Public bug reported:
The Ubuntu Error Tracker has been receiving reports about a problem regarding
gnome-shell. This problem was most recently seen with package version
40.5-1ubuntu2, the problem page at
https://errors.ubuntu.com/problem/22d9d466c0128fadf2a5a14e35cac37531875d1e
contains more
*** This bug is a duplicate of bug 1871262 ***
https://bugs.launchpad.net/bugs/1871262
Are you sure about duplicate status? This is a new issue I'm
experiencing with 21.10, and the reproduction steps are different (I see
nothing in the other bug about display hotplug).
--
You received this
Memory in gnome-shell does not get freed quickly because of JavaScript
garbage collection. Memory usage will tend to grow slowly and plateau.
Significant drops are rare, but I would not consider it a leak unless
you see growth continuing above 500MB. Starting at 200MB is normal.
If you are still
I switch off all the extensions except for Ubuntu ones. Every
lock/unlock action raises the memory usage by ~10MB until it reaches
~280MB. Super-A (app overview) raised further the usage.
After a while something happend (Not lock/unlock or Super-A) and now the
memory usage of gnome-shell is 302MB
The Precise Pangolin has reached end of life, so this bug will not be
fixed for that release
** Changed in: compiz (Ubuntu Precise)
Status: Confirmed => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to nautilus in
The Precise Pangolin has reached end of life, so this bug will not be
fixed for that release
** Changed in: gtk+3.0 (Ubuntu Precise)
Status: Confirmed => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gtk+3.0 in
The Precise Pangolin has reached end of life, so this bug will not be
fixed for that release
** Changed in: gnome-settings-daemon (Ubuntu Precise)
Status: Confirmed => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to
The Precise Pangolin has reached end of life, so this bug will not be
fixed for that release
** Changed in: libtasn1-3 (Ubuntu Precise)
Status: Triaged => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gtk+2.0 in
The Precise Pangolin has reached end of life, so this bug will not be
fixed for that release
** Changed in: evince (Ubuntu Precise)
Status: Confirmed => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to evince in
The Precise Pangolin has reached end of life, so this bug will not be
fixed for that release
** Changed in: gnome-control-center (Ubuntu Precise)
Status: Triaged => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to
The Precise Pangolin has reached end of life, so this bug will not be
fixed for that release
** Changed in: pygobject (Ubuntu Precise)
Status: Fix Committed => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to
The Precise Pangolin has reached end of life, so this bug will not be
fixed for that release
** Changed in: libjpeg-turbo (Ubuntu Precise)
Status: Triaged => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to eog in
The Precise Pangolin has reached end of life, so this bug will not be
fixed for that release
** Changed in: gnome-settings-daemon (Ubuntu Precise)
Status: Confirmed => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to
The Precise Pangolin has reached end of life, so this bug will not be
fixed for that release
** Changed in: linux (Ubuntu Precise)
Status: Incomplete => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-session
The Precise Pangolin has reached end of life, so this bug will not be
fixed for that release
** Changed in: gnome-settings-daemon (Ubuntu Precise)
Status: Confirmed => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to
The Precise Pangolin has reached end of life, so this bug will not be
fixed for that release
** Changed in: yelp (Ubuntu Precise)
Status: New => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to yelp in Ubuntu.
42 matches
Mail list logo
