[Expired for gdm3 (Ubuntu) because there has been no activity for 60
days.]
** Changed in: gdm3 (Ubuntu)
Status: Incomplete => Expired
--
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/b
[Expired for gedit (Ubuntu) because there has been no activity for 60
days.]
** Changed in: gedit (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gedit in Ubuntu.
https://bugs.launchpad.ne
** Also affects: gtk+3.0 (Ubuntu)
Importance: Undecided
Status: 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/1924689
Title:
When changing screen scale in GNOME Xorg,
** Summary changed:
- When changing screen scale in X11, gnome-initial-setup's window shadow should
not be glitched
+ When changing screen scale in GNOME Xorg, gnome-initial-setup's window shadow
should not be glitched
--
You received this bug notification because you are a member of Ubuntu
De
I suggest trying to find a generic app that upstream (Red Hat) will have
as a test case. If you can do that then it should be reported to
https://gitlab.gnome.org/GNOME/mutter/issues
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to mutt
** Summary changed:
- Can see some garbage at the edge of the window after changing scale
+ When changing screen scale in X11, gnome-initial-setup's window shadow can be
glitched
** Summary changed:
- When changing screen scale in X11, gnome-initial-setup's window shadow can be
glitched
+ When
Yes I think it looks like a mutter bug judging by the video.
--
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/1924689
Title:
When changing screen scale in GNOME Xorg, gnome-initial-se
Mutter keeps multiple copies of window-related things, moreso on X11
where the server is a separate process with its own idea of how big a
window is. That also means a window gets resized in multiple processes
at slightly different times. So it's easy to mess up in mutter and get
bugs like this (I
Tried modifying the source code of gnome-initial-setup, found that this
issue cannot be reproduced, if the titlebar of the window (gis-
assistant) is not set in the main (gis-driver) window.
I think this issue can be worked around in gis-assistant, but the root
cause might be either gnome-initial-
** Bug watch added: gitlab.gnome.org/GNOME/gnome-shell/-/issues #3456
https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/3456
** Also affects: gnome-shell via
https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/3456
Importance: Unknown
Status: Unknown
** Changed in: gnome-shell (
** Changed in: gnome-control-center (Ubuntu)
Status: Incomplete => New
** Also affects: mutter (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu.
The affected user cannot reproduce the issue anymore. The new mutter
packages install fine in their environment, and gdm starts every time.
They have since rolled out the new mutter packages to their fleet
without any issues.
I'm going to mark this bug as invalid, as we can't reproduce the issue
a
This is still happening in 21.04, most recently with a repeating
calendar event instance that was canceled over a week ago. The desktop
has been rebooted in the interim.
** Tags added: hirsute
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscri
This bug was fixed in the package evolution-data-server -
3.40.0-1ubuntu1.1
---
evolution-data-server (3.40.0-1ubuntu1.1) hirsute; urgency=medium
* debian/patches/git_icloud_server.patch:
- cherry pick a fix needed for compatibility with the new iCloud
server behaviour (lp
Sure thing, these are all of the entries that happened during a bad
screen wakeup/login interaction. The only things I removed were
irrelevant Slack messages and a random string in the NetworkManager
message I didn't understand.
I'm just now noticing the gdm-password error. It does seem like that
** Changed in: gdm3 (Ubuntu)
Assignee: Romualdo (romualdo2) => (unassigned)
--
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/1845801
Title:
[nvidia] Automatic login fails and then
** Changed in: gdm3 (Ubuntu)
Assignee: jeremyszu (os369510) => Romualdo (romualdo2)
--
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/1845801
Title:
[nvidia] Automatic login fails a
Public bug reported:
When a new Wayland session is created from a login, Alt-tab works as
expected to change windows. After sometime Alt-tab fails to do anything
(super-tab still works to change applications) and the following error
is created in syslog:
gnome-shell[18]: JS ERROR: TypeError:
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: gedit-plugins (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gedit-plugins in Ubuntu.
https://bugs.launchpa
Thanks for looking at this Daniel! It is the same on Wayland and Xorg.
--
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/1933890
Title:
No wacom tablet or stylus discove
I did test this multiple times to get the messages. It has persisted
across restarts too.
--
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/1933889
Title:
Unmounted SD card does not
Sure. I'm attaching the file. The time now is 6:30 a.m. and the bug
report says it was about twelve hours ago (and it might have been 13 or
14 hours ago if I trust my memory more). I don't have an SD card very
handy at this time, but if you wish, I can retrieve one and do the test
again, and giv
Thank you for your bug report, if conky shows the drive then it's not a
nautilus issue
** Package changed: nautilus (Ubuntu) => linux (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to nautilus in Ubuntu.
https://bugs.launchpad.
Thank you for your bug report, was that a one time only issue? Could you
add the 'journalctl -b ' log from that session (n = 0 if you didn't
restart the computer, otherwise = number of restarts) and indicate
around what time you saw the issue?
** Changed in: nautilus (Ubuntu)
Importance: Undeci
Thanks for opening the bug on gitlab and sorry that you got a negative
upstream experience, Andre who replied to you is a bug triager who is
more concerned by seeing numbers going down and tickets closed than by
having issues resolved.
Could you provide a 'journalctl -b 0' log after seeing the iss
** Changed in: oem-priority
Assignee: (unassigned) => Yao Wei (medicalwei)
--
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/1924689
Title:
Can see some garbage at the edge of the
** Changed in: gnome-control-center (Ubuntu)
Importance: Undecided => Low
--
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/1925375
Title:
settings goes after work som
Thank you for your bug report, could you perhaps also submit it upstream
on https://gitlab.gnome.org/GNOME/gnome-system-monitor/-/issues ?
** Changed in: gnome-system-monitor (Ubuntu)
Importance: Undecided => Low
--
You received this bug notification because you are a member of Ubuntu
Desktop
OK, that's what I expected. I suggest that error in Wayland sessions
should be reported as a bug to upstream:
https://gitlab.gnome.org/GNOME/mutter/-/issues
** Changed in: mutter (Ubuntu)
Status: Invalid => New
** Changed in: mutter (Ubuntu)
Status: New => Triaged
--
You recei
Xorg worked after a full power cycle again.
Wayland is still showing the issue and generating the error message of
gnome-shell 1856945 - - Failed to post KMS update: drmModePageFlip on
CRTC 33 failed: Nicht genügend Hauptspeicher verfügbar
Let me know if you need me to do any further diagnostic
30 matches
Mail list logo
