Well, I couldn't figure out how to disable the ubuntu dock, because I
had not ever used the extensions app before, but I used apt to remove it
and then I could not repeat the behavior, however, I did reinstall it,
and I also could not get it to malfunction. Sorry, I've lost your bug!
Rob
On 1
here are the logs
** Attachment added: "/var/log from guest system"
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1945704/+attachment/5529947/+files/log.tar.gz
** Changed in: gnome-shell (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification becau
I am encountering a similar issue. My system completely shuts down
without any warning while doing nothing resource-intensive. The log just
before shutting down is as follows:
/usr/lib/gdm-x-session[1011]: (EE) client bug: timer event20 debounce:
scheduled expiry is in the past (-0ms), your syste
** Changed in: xrdp (Debian)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to xrdp in Ubuntu.
https://bugs.launchpad.net/bugs/1931225
Title:
0.9.15 is FTFBS on ppc64el and s390x
To manage notificat
This bug should be fixed with
https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/2003
I cannot reproduce the issue anymore when this change is applied on my system.
Can someone initiate that this fix is backported into Ubuntu 21.04?
--
You received this bug notification because you are a me
Would it as such be preferred to open a new bug on this issue? The PPA
was removed from the system yet the issue persists. Another system log
from the system by default is attached.
** Attachment added: "journal on system with default packages"
https://bugs.launchpad.net/ubuntu/+source/gdm3/+b
Similar problem has been detected:
I get a notification for this crash report every time when I log in. It
usually does't happen on a fresh bootup, but it always happens if I log
out to GDM then log back in. Funtionality wise, everything seems to be
working fine despite this happening.
reporter:
The dot, indicating the default is missing
--
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/1945750
Title:
[nvidia] Wayland session fails to start on nvidia-470, falls back to
X11 ins
The attached log shows that Wayland is being used (gnome-shell process
4441).
What makes you think it's not working?
** Summary changed:
- gdm3 do not connect to the right session on 21.10 beta
+ [nvidia] Wayland session fails to start on nvidia-470, falls back to X11
instead
--
You received
I have the very same problem, by using a Keychron K8 keyboard, which is
recognized as an apple hid keyboard.
What i've tried is also to enable/disable fn keys, without success.
```
❯ echo 1 | sudo tee /sys/module/hid_apple/parameters/fnmode
[sudo] password for paolo:
1
~
❯ echo 0 |
We already have bug 1857392 for the first warning.
** Summary changed:
- gnome-shell errors
+ gnome-shell error: Window manager warning: WM_TRANSIENT_FOR window 0x56994b0
for 0x572b45a window override-r>
** Description changed:
- I have two type of errors
-
- gnome-shell[2070]: Window manage
--
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/1945760
Title:
Window manager warning: WM_TRANSIENT_FOR window 0x56994b0 for
0x572b45a window override-redirect is an override-r
Public bug reported:
I have two type of errors
gnome-shell[2070]: Window manager warning: Overwriting existing binding
of keysym 31 with keysym 31 (keycode>
gnome-shell[2070]: Window manager warning: WM_TRANSIENT_FOR window 0x56994b0
for 0x572b45a window override-r>
Ubuntu 20.04
ProblemType
Resurrecting this somewhat.
The solutions suggested above are fine if you only have one monitor, but
immediately cause issues if you have more than one (and they're not
similar in size and resolution).
Here, on two out of my three screens, everything is exactly as I want.
The third one is a littl
** Attachment added: "journalctl"
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1945750/+attachment/5529729/+files/journal1.txt
--
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/1
I rebooted after update and now I have in the list "ubuntu / ubuntu with
Xorg" no dot at all but I connect to wayland as it seem to be the
default now.
same when I close session and reopen it.
** Attachment added: "packages.txt"
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1945750/+att
I wonder if these messages in ShellJournal.txt indicate the issue:
[ 144.246646] t935 gnome-shell[2465]: Can't update stage views actor
dashtodockContainer is on because it needs an allocation.
[ 144.247009] t935 gnome-shell[2465]: Can't update stage views actor
Gjs_ubuntu-dock_ubuntu_com_dock
** Package changed: 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/1945733
Title:
Could not click on any gnome-shell widget...
To manage notific
Sounds like the opposite of bug 1944581. Next time the problem happens
please run:
journalctl -b0 > journal.txt
dpkg -l > packages.txt
and attach the resulting text files here.
Also, in future please use the 'ubuntu-bug' command to open new bugs.
** Tags added: impish
** Changed in: gdm3
You have been subscribed to a public bug:
Gnome-shell would not respond to any click on any of its icons. I'm not
really sure why, but I suspect it had to do with a screen rotation. I
was using Wayland, not X when this happened. I couldn't figure an easy
way out of this situation so I did a ctr
Public bug reported:
I've updated to 21.10 beta to test wayland for nvidia successfully.
Even when the dot is for "ubuntu with wayland" choice, gdm3 launch X11
session
I have to select "ubuntu with wayland" to have the wayland session
** Affects: gdm3 (Ubuntu)
Importance: Undecided
I guess we could make this distinction for users who are in neither of
the adm/sudo groups. But it's a non-trivial enhancement that requires
more detailed design discussion so please report it to the GNOME
developers at https://gitlab.gnome.org/GNOME/gnome-shell/issues and then
tell us the new issu
22 matches
Mail list logo
