[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 plymouth (Ubuntu) because there has been no activity for 60
days.]
** Changed in: plymouth (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.launchp
See also:
https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1968#note_1275389
--
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/1969422
Title:
gnome-shell crashed with SIGSEGV in
Another duplicate (bug 1987174) shows the crash happening on a hybrid
system with i915+nouveau.
So it doesn't sound as related to AMDGPU as to hybrid systems in general
(open source drivers).
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscrib
No problem. The bug will automatically close after 2 months if no
further comments are added.
--
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/1983175
Title:
In Wayland, can't wake up
Yes this sounds like bug 1969422.
Next time please open a new bug of your own instead of commenting on
closed bugs reported by someone else.
--
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
Indeed - I don't think it is useful to have such information displayed
prominently when there is nothing that user's can do to affect this (in
general) and so this will only cause alarm. Like Marc said, it is then
not useful to display this without offering actionable tasks that a user
an perform t
Public bug reported:
```
GNU Image Manipulation Program version 2.10.30
git-describe: GIMP_2_10_30
Build: unknown rev 0 for linux
# C compiler #
Using built-in specs.
COLLECT_GCC=gcc
COLLECT_LTO_WRAPPER=/usr/lib/gcc/x86_64-linux-gnu/11/lto-wrapper
OFFLOAD_TARGET_
Test suggested by oria on IRC: try "nomodeset" in kernel parameter and
try to reproduce the problem.
After the reboot:
```
$ uname -a
Linux flhpz4 5.15.0-46-generic #49-Ubuntu SMP Thu Aug 4 18:03:25 UTC 2022
x86_64 x86_64 x86_64 GNU/Linux
$ cat /proc/cmdline
BOOT_IMAGE=/boot/vmlinuz-5.15.0-46-g
** Tags added: amdgpu multimonitor
--
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/1987209
Title:
gnome-shell (Wayland) crashes when screen locker activates (jj)
To manage noti
Hi,
Tom Reynolds wrote:
> gnome-shell (Wayland) reproducibly segfaults on this amd64 system
> whenever the no-user-interaction timeout is reached and the screen
> locker kicks in. Not reproducible on Xorg.
This is perfectly summarized.
FYI, the problem doesn't appear if I lock my session manual
Summary from my IRC support session with francois-lafont:
gnome-shell (Wayland) reproducibly segfaults on this amd64 system
whenever the no-user-interaction timeout is reached and the screen
locker kicks in. Not reproducible on Xorg.
This is an amd64 Intel CPU, 2x AMD GPU system, recently upgrade
** Summary changed:
- Automatic lock screen doesn't lock my session but closes it because of a
gnome-shell crash
+ gnome-shell crashes with Wayland when screen locker activates (jj)
** Summary changed:
- gnome-shell crashes with Wayland when screen locker activates (jj)
+ gnome-shell (Wayland)
Same test here but where I have selected "Ubuntu on Xorg" before login,
instead of "Ubuntu". The point is, in that case, my session is locked
and I don't loose my session:
```
Aug 21 18:31:20 flhpz4 systemd[38118]: Reached target Exit the Session.
Aug 21 18:31:20 flhpz4 systemd[1]: user@122.servic
*** This bug is a duplicate of bug 1986985 ***
https://bugs.launchpad.net/bugs/1986985
Thank you for taking the time to report this crash and helping to make
this software better. This particular crash has already been reported
and is a duplicate of bug #1986985, so is being marked as such.
FYI, here is the output of `journalctl -f` (run as root in tyy4) during
the automatic lock screen of my session (of the user flaf) and the
gnome-shell crash:
```
Aug 21 18:11:17 flhpz4 sudo[25344]: pam_unix(sudo:session): session closed for
user root
Aug 21 18:11:17 flhpz4 sudo[25348]: flaf :
Public bug reported:
Hi,
On my Ubuntu 22.04 (migrated from 20.04 few days ago), I have a problem
with the automatic lock screen which doesn't lock my session but closes
it (and all opened applications in my session are closed too of course).
In fact, I think the session is not really closed but t
** Package changed: ubuntu => gdm3 (Ubuntu)
--
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/1987201
Title:
Screen blanking no longer works after Thunderbird "new email" alert
To manag
You have been subscribed to a public bug:
Screen blanking is enabled, set to 10 minutes. Works fine. Launch
thunderbird, with option to display alert when new email arrives. After
receiving new email, thunderbird displays alert. Following this, the
10-minute screen blanking no longer works.
P
I enabled -proposed and updated epiphany-browser to version
42.4-0ubuntu1.
As per test case:
1. www.ubuntu.com loaded correctly
2. Reader mode on markshuttleworth.com worked correctly
3. Installed gstreamer1.0-plugins-bad
4. Played several videos on YouTube - sound and audio ok
I also logged int
The bug is still there even include to Ubuntu 22.10 development branch. The
crash arrive in the same conditions previously mentioned except that using X11
instead Wayland does not fix anything at all.
Crash arrive in both case ! it's time for this bug to disappear ...
--
You received this bug
21 matches
Mail list logo
