| 2022-05-30 03:00:21 |
Andy Chi |
bug |
|
|
added bug |
| 2022-05-30 03:00:21 |
Andy Chi |
attachment added |
|
sosreport-ubuntu-XPS-9320-2022-05-27-ouxfyjg.tar.xz https://bugs.launchpad.net/bugs/1976204/+attachment/5593674/+files/sosreport-ubuntu-XPS-9320-2022-05-27-ouxfyjg.tar.xz |
|
| 2022-05-30 03:05:49 |
Andy Chi |
bug |
|
|
added subscriber OEM Solutions Group: Engineers |
| 2022-05-30 03:05:52 |
Andy Chi |
tags |
|
oem-priority originate-from-1967530 somerville |
|
| 2022-05-30 03:08:12 |
Andy Chi |
oem-priority: status |
New |
Confirmed |
|
| 2022-05-30 03:08:14 |
Andy Chi |
oem-priority: importance |
Undecided |
Critical |
|
| 2022-05-30 03:08:16 |
Andy Chi |
oem-priority: assignee |
|
Andy Chi (andch) |
|
| 2022-05-30 03:08:52 |
Kai-Chuan Hsieh |
tags |
oem-priority originate-from-1967530 somerville |
jellyfish-edge-staging oem-priority originate-from-1967530 somerville |
|
| 2022-05-30 03:09:20 |
Andy Chi |
attachment added |
|
syslog.log.tar.gz https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1976204/+attachment/5593680/+files/syslog.log.tar.gz |
|
| 2022-06-01 02:29:16 |
Andy Chi |
tags |
jellyfish-edge-staging oem-priority originate-from-1967530 somerville |
apport-collected jammy jellyfish-edge-staging oem-priority originate-from-1967530 somerville wayland-session |
|
| 2022-06-01 02:29:18 |
Andy Chi |
description |
[Summary]
The system will run into freeze if I connect the external monitor through DP/HDMI with dongle DA310 or Docking WD19TB
[Steps to reproduce]
1. Attact DA310 or WD19TB to DUT
2. Cold Boot into OS
3. Plug the DP/HDMI cable to DA310 or WD19TB
4. Check the external monitor has signal
5. Click keyboard or move mouse to check system can work well
[Expected result]
System won't be freeze with external monitor.
[Actual result]
System will be freeze.
It can be recovered after unplug the external monitor sometime.
[gnome-shell stack trace]
五 27 22:12:31 ubuntu-XPS-9320 gnome-shell[1998]: Window manager warning: Overwriting existing binding of keysym 37 with keysym 37 (keycode 10).
五 27 22:12:31 ubuntu-XPS-9320 gnome-shell[1998]: Window manager warning: Overwriting existing binding of keysym 35 with keysym 35 (keycode e).
五 27 22:12:31 ubuntu-XPS-9320 gnome-shell[1998]: Window manager warning: Overwriting existing binding of keysym 33 with keysym 33 (keycode c).
五 27 22:12:31 ubuntu-XPS-9320 gnome-shell[1998]: meta_window_set_stack_position_no_sync: assertion 'window->stack_position >= 0' failed
五 27 22:12:55 ubuntu-XPS-9320 sudo[2916]: ubuntu : TTY=pts/2 ; PWD=/home/ubuntu ; USER=root ; COMMAND=/usr/bin/dmesg
五 27 22:12:55 ubuntu-XPS-9320 sudo[2916]: pam_unix(sudo:session): session opened for user root(uid=0) by ubuntu(uid=1001)
五 27 22:12:55 ubuntu-XPS-9320 sudo[2916]: pam_unix(sudo:session): session closed for user root
五 27 22:12:56 ubuntu-XPS-9320 gnome-shell[1998]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
五 27 22:12:56 ubuntu-XPS-9320 gnome-shell[1998]: == Stack trace for context 0x56156f8f04a0 ==
五 27 22:12:56 ubuntu-XPS-9320 gnome-shell[1998]: == Stack trace for context 0x56156f8f04a0 ==
五 27 22:12:56 ubuntu-XPS-9320 gnome-shell[1998]: The offending signal was window-added on MetaWorkspace 0x56156f916640.
五 27 22:12:56 ubuntu-XPS-9320 gnome-shell[1998]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
五 27 22:12:56 ubuntu-XPS-9320 gnome-shell[1998]: The offending signal was window-added on MetaWorkspace 0x56156f916640.
五 27 22:12:56 ubuntu-XPS-9320 gnome-shell[1998]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
This system is using OLED (3456x2160) panel, and I can't reproduce this issue on FHD panel. |
[Summary]
The system will run into freeze if I connect the external monitor through DP/HDMI with dongle DA310 or Docking WD19TB
[Steps to reproduce]
1. Attact DA310 or WD19TB to DUT
2. Cold Boot into OS
3. Plug the DP/HDMI cable to DA310 or WD19TB
4. Check the external monitor has signal
5. Click keyboard or move mouse to check system can work well
[Expected result]
System won't be freeze with external monitor.
[Actual result]
System will be freeze.
It can be recovered after unplug the external monitor sometime.
[gnome-shell stack trace]
五 27 22:12:31 ubuntu-XPS-9320 gnome-shell[1998]: Window manager warning: Overwriting existing binding of keysym 37 with keysym 37 (keycode 10).
五 27 22:12:31 ubuntu-XPS-9320 gnome-shell[1998]: Window manager warning: Overwriting existing binding of keysym 35 with keysym 35 (keycode e).
五 27 22:12:31 ubuntu-XPS-9320 gnome-shell[1998]: Window manager warning: Overwriting existing binding of keysym 33 with keysym 33 (keycode c).
五 27 22:12:31 ubuntu-XPS-9320 gnome-shell[1998]: meta_window_set_stack_position_no_sync: assertion 'window->stack_position >= 0' failed
五 27 22:12:55 ubuntu-XPS-9320 sudo[2916]: ubuntu : TTY=pts/2 ; PWD=/home/ubuntu ; USER=root ; COMMAND=/usr/bin/dmesg
五 27 22:12:55 ubuntu-XPS-9320 sudo[2916]: pam_unix(sudo:session): session opened for user root(uid=0) by ubuntu(uid=1001)
五 27 22:12:55 ubuntu-XPS-9320 sudo[2916]: pam_unix(sudo:session): session closed for user root
五 27 22:12:56 ubuntu-XPS-9320 gnome-shell[1998]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
五 27 22:12:56 ubuntu-XPS-9320 gnome-shell[1998]: == Stack trace for context 0x56156f8f04a0 ==
五 27 22:12:56 ubuntu-XPS-9320 gnome-shell[1998]: == Stack trace for context 0x56156f8f04a0 ==
五 27 22:12:56 ubuntu-XPS-9320 gnome-shell[1998]: The offending signal was window-added on MetaWorkspace 0x56156f916640.
五 27 22:12:56 ubuntu-XPS-9320 gnome-shell[1998]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
五 27 22:12:56 ubuntu-XPS-9320 gnome-shell[1998]: The offending signal was window-added on MetaWorkspace 0x56156f916640.
五 27 22:12:56 ubuntu-XPS-9320 gnome-shell[1998]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
This system is using OLED (3456x2160) panel, and I can't reproduce this issue on FHD panel.
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu82.1
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
DisplayManager: gdm3
DistroRelease: Ubuntu 22.04
InstallationDate: Installed on 2022-03-17 (75 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220313)
Package: gnome-shell 42.1-0ubuntu0.1
PackageArchitecture: amd64
ProcVersionSignature: Ubuntu 5.15.0-35.36-generic 5.15.35
RelatedPackageVersions: mutter-common 42.0-3ubuntu2
Tags: jammy wayland-session
Uname: Linux 5.15.0-35-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
_MarkForUpload: True |
|
| 2022-06-01 02:29:19 |
Andy Chi |
attachment added |
|
Dependencies.txt https://bugs.launchpad.net/bugs/1976204/+attachment/5594174/+files/Dependencies.txt |
|
| 2022-06-01 02:29:22 |
Andy Chi |
attachment added |
|
GsettingsChanges.txt https://bugs.launchpad.net/bugs/1976204/+attachment/5594175/+files/GsettingsChanges.txt |
|
| 2022-06-01 02:29:24 |
Andy Chi |
attachment added |
|
ProcCpuinfoMinimal.txt https://bugs.launchpad.net/bugs/1976204/+attachment/5594176/+files/ProcCpuinfoMinimal.txt |
|
| 2022-06-01 02:29:35 |
Andy Chi |
attachment added |
|
ProcEnviron.txt https://bugs.launchpad.net/bugs/1976204/+attachment/5594177/+files/ProcEnviron.txt |
|
| 2022-06-01 02:29:38 |
Andy Chi |
attachment added |
|
ShellJournal.txt https://bugs.launchpad.net/bugs/1976204/+attachment/5594178/+files/ShellJournal.txt |
|
| 2022-06-01 07:07:52 |
Andy Chi |
bug task added |
|
gnome-shell-extension-desktop-icons-ng (Ubuntu) |
|
| 2022-06-03 15:26:43 |
Marco Trevisan (Treviño) |
bug |
|
|
added subscriber Marco Trevisan (Treviño) |
| 2022-06-06 08:43:50 |
Andy Chi |
attachment added |
|
20220606-gnome-shell.log.tar.gz https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1976204/+attachment/5595044/+files/20220606-gnome-shell.log.tar.gz |
|
| 2022-06-06 13:09:24 |
Andy Chi |
attachment added |
|
gnome-shell-stack-trace-202206062108.tar.gz https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1976204/+attachment/5595073/+files/gnome-shell-stack-trace-202206062108.tar.gz |
|
| 2022-06-07 16:53:21 |
Marco Trevisan (Treviño) |
bug task added |
|
mutter (Ubuntu) |
|
| 2022-06-08 05:19:28 |
Andy Chi |
description |
[Summary]
The system will run into freeze if I connect the external monitor through DP/HDMI with dongle DA310 or Docking WD19TB
[Steps to reproduce]
1. Attact DA310 or WD19TB to DUT
2. Cold Boot into OS
3. Plug the DP/HDMI cable to DA310 or WD19TB
4. Check the external monitor has signal
5. Click keyboard or move mouse to check system can work well
[Expected result]
System won't be freeze with external monitor.
[Actual result]
System will be freeze.
It can be recovered after unplug the external monitor sometime.
[gnome-shell stack trace]
五 27 22:12:31 ubuntu-XPS-9320 gnome-shell[1998]: Window manager warning: Overwriting existing binding of keysym 37 with keysym 37 (keycode 10).
五 27 22:12:31 ubuntu-XPS-9320 gnome-shell[1998]: Window manager warning: Overwriting existing binding of keysym 35 with keysym 35 (keycode e).
五 27 22:12:31 ubuntu-XPS-9320 gnome-shell[1998]: Window manager warning: Overwriting existing binding of keysym 33 with keysym 33 (keycode c).
五 27 22:12:31 ubuntu-XPS-9320 gnome-shell[1998]: meta_window_set_stack_position_no_sync: assertion 'window->stack_position >= 0' failed
五 27 22:12:55 ubuntu-XPS-9320 sudo[2916]: ubuntu : TTY=pts/2 ; PWD=/home/ubuntu ; USER=root ; COMMAND=/usr/bin/dmesg
五 27 22:12:55 ubuntu-XPS-9320 sudo[2916]: pam_unix(sudo:session): session opened for user root(uid=0) by ubuntu(uid=1001)
五 27 22:12:55 ubuntu-XPS-9320 sudo[2916]: pam_unix(sudo:session): session closed for user root
五 27 22:12:56 ubuntu-XPS-9320 gnome-shell[1998]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
五 27 22:12:56 ubuntu-XPS-9320 gnome-shell[1998]: == Stack trace for context 0x56156f8f04a0 ==
五 27 22:12:56 ubuntu-XPS-9320 gnome-shell[1998]: == Stack trace for context 0x56156f8f04a0 ==
五 27 22:12:56 ubuntu-XPS-9320 gnome-shell[1998]: The offending signal was window-added on MetaWorkspace 0x56156f916640.
五 27 22:12:56 ubuntu-XPS-9320 gnome-shell[1998]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
五 27 22:12:56 ubuntu-XPS-9320 gnome-shell[1998]: The offending signal was window-added on MetaWorkspace 0x56156f916640.
五 27 22:12:56 ubuntu-XPS-9320 gnome-shell[1998]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
This system is using OLED (3456x2160) panel, and I can't reproduce this issue on FHD panel.
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu82.1
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
DisplayManager: gdm3
DistroRelease: Ubuntu 22.04
InstallationDate: Installed on 2022-03-17 (75 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220313)
Package: gnome-shell 42.1-0ubuntu0.1
PackageArchitecture: amd64
ProcVersionSignature: Ubuntu 5.15.0-35.36-generic 5.15.35
RelatedPackageVersions: mutter-common 42.0-3ubuntu2
Tags: jammy wayland-session
Uname: Linux 5.15.0-35-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
_MarkForUpload: True |
[Summary]
The system will run into freeze if I connect the external monitor through DP/HDMI with dongle DA310 or Docking WD19TB
[Steps to reproduce]
1. Attact DA310 or WD19TB to DUT
2. Cold Boot into OS
3. Plug the DP/HDMI cable to DA310 or WD19TB
4. Check the external monitor has signal
5. Click keyboard or move mouse to check system can work well
[Expected result]
System won't be freeze with external monitor.
[Actual result]
Screen will freeze, but ssh can still reach out DUT. Keyboard and mouse
don't work during the screen freeze.
It can be recovered after unplug the external monitor sometime.
[gnome-shell stack trace]
五 27 22:12:31 ubuntu-XPS-9320 gnome-shell[1998]: Window manager warning: Overwriting existing binding of keysym 37 with keysym 37 (keycode 10).
五 27 22:12:31 ubuntu-XPS-9320 gnome-shell[1998]: Window manager warning: Overwriting existing binding of keysym 35 with keysym 35 (keycode e).
五 27 22:12:31 ubuntu-XPS-9320 gnome-shell[1998]: Window manager warning: Overwriting existing binding of keysym 33 with keysym 33 (keycode c).
五 27 22:12:31 ubuntu-XPS-9320 gnome-shell[1998]: meta_window_set_stack_position_no_sync: assertion 'window->stack_position >= 0' failed
五 27 22:12:55 ubuntu-XPS-9320 sudo[2916]: ubuntu : TTY=pts/2 ; PWD=/home/ubuntu ; USER=root ; COMMAND=/usr/bin/dmesg
五 27 22:12:55 ubuntu-XPS-9320 sudo[2916]: pam_unix(sudo:session): session opened for user root(uid=0) by ubuntu(uid=1001)
五 27 22:12:55 ubuntu-XPS-9320 sudo[2916]: pam_unix(sudo:session): session closed for user root
五 27 22:12:56 ubuntu-XPS-9320 gnome-shell[1998]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
五 27 22:12:56 ubuntu-XPS-9320 gnome-shell[1998]: == Stack trace for context 0x56156f8f04a0 ==
五 27 22:12:56 ubuntu-XPS-9320 gnome-shell[1998]: == Stack trace for context 0x56156f8f04a0 ==
五 27 22:12:56 ubuntu-XPS-9320 gnome-shell[1998]: The offending signal was window-added on MetaWorkspace 0x56156f916640.
五 27 22:12:56 ubuntu-XPS-9320 gnome-shell[1998]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
五 27 22:12:56 ubuntu-XPS-9320 gnome-shell[1998]: The offending signal was window-added on MetaWorkspace 0x56156f916640.
五 27 22:12:56 ubuntu-XPS-9320 gnome-shell[1998]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
This system is using OLED (3456x2160) panel, and I can't reproduce this issue on FHD panel.
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu82.1
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
DisplayManager: gdm3
DistroRelease: Ubuntu 22.04
InstallationDate: Installed on 2022-03-17 (75 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220313)
Package: gnome-shell 42.1-0ubuntu0.1
PackageArchitecture: amd64
ProcVersionSignature: Ubuntu 5.15.0-35.36-generic 5.15.35
RelatedPackageVersions: mutter-common 42.0-3ubuntu2
Tags: jammy wayland-session
Uname: Linux 5.15.0-35-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
_MarkForUpload: True |
|
| 2022-06-08 14:33:34 |
Zorro Zhang |
bug |
|
|
added subscriber Zorro Zhang |
| 2022-06-09 06:48:47 |
Daniel van Vugt |
summary |
system freeze and gnome-shell reports multiple stack trace |
System freeze |
|
| 2022-06-09 06:49:38 |
Daniel van Vugt |
bug |
|
|
added subscriber Daniel van Vugt |
| 2022-06-09 07:44:59 |
Andy Chi |
summary |
System freeze |
Screen freeze |
|
| 2022-06-10 04:32:52 |
Andy Chi |
attachment added |
|
dpkg.txt https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1976204/+attachment/5596187/+files/dpkg.txt |
|
| 2022-06-16 06:57:19 |
Andy Chi |
attachment added |
|
sosreport-ubuntu-XPS-13-9310-2022-06-16-cypwmhe.tar.xz https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1976204/+attachment/5597653/+files/sosreport-ubuntu-XPS-13-9310-2022-06-16-cypwmhe.tar.xz |
|
| 2022-06-16 08:33:26 |
Andy Chi |
attachment added |
|
gnome-shell-enable-mutter-20220616.log https://bugs.launchpad.net/oem-priority/+bug/1976204/+attachment/5597671/+files/gnome-shell-enable-mutter-20220616.log |
|
| 2022-06-17 02:36:14 |
Kai-Chuan Hsieh |
bug watch added |
|
https://gitlab.freedesktop.org/drm/intel/-/issues/6101 |
|
| 2022-06-17 02:57:22 |
Daniel van Vugt |
summary |
Screen freeze |
Screen freeze if a 4K monitor is added to a 4K laptop while DING is active |
|
| 2022-06-17 02:57:43 |
Daniel van Vugt |
gnome-shell (Ubuntu): importance |
Undecided |
High |
|
| 2022-06-17 02:57:45 |
Daniel van Vugt |
mutter (Ubuntu): importance |
Undecided |
High |
|
| 2022-06-17 02:57:47 |
Daniel van Vugt |
gnome-shell-extension-desktop-icons-ng (Ubuntu): importance |
Undecided |
High |
|
| 2022-06-17 07:46:09 |
Rex Tsai |
bug |
|
|
added subscriber Rex Tsai |
| 2022-06-21 09:51:34 |
Daniel van Vugt |
gnome-shell (Ubuntu): assignee |
|
Daniel van Vugt (vanvugt) |
|
| 2022-06-21 09:51:37 |
Daniel van Vugt |
mutter (Ubuntu): assignee |
|
Daniel van Vugt (vanvugt) |
|
| 2022-06-21 09:51:40 |
Daniel van Vugt |
gnome-shell (Ubuntu): status |
New |
In Progress |
|
| 2022-06-21 09:51:43 |
Daniel van Vugt |
mutter (Ubuntu): status |
New |
In Progress |
|
| 2022-06-21 13:04:41 |
Andy Chi |
attachment added |
|
gnome-shell-20220621.log https://bugs.launchpad.net/oem-priority/+bug/1976204/+attachment/5598650/+files/gnome-shell-20220621.log |
|
| 2022-06-22 08:57:23 |
Daniel van Vugt |
bug task deleted |
gnome-shell-extension-desktop-icons-ng (Ubuntu) |
|
|
| 2022-06-22 08:59:18 |
Daniel van Vugt |
summary |
Screen freeze if a 4K monitor is added to a 4K laptop while DING is active |
Screen freeze and high CPU when a second monitor of different scaling factor is attached (but only if DING is active) |
|
| 2022-06-23 10:11:01 |
Daniel van Vugt |
bug task added |
|
gnome-shell-extension-desktop-icons-ng (Ubuntu) |
|
| 2022-06-23 10:11:08 |
Daniel van Vugt |
gnome-shell-extension-desktop-icons-ng (Ubuntu): status |
New |
Opinion |
|
| 2022-06-23 10:11:11 |
Daniel van Vugt |
gnome-shell-extension-desktop-icons-ng (Ubuntu): assignee |
|
Daniel van Vugt (vanvugt) |
|
| 2022-06-23 11:14:07 |
Daniel van Vugt |
gnome-shell-extension-desktop-icons-ng (Ubuntu): status |
Opinion |
In Progress |
|
| 2022-06-23 11:14:10 |
Daniel van Vugt |
gnome-shell-extension-desktop-icons-ng (Ubuntu): importance |
Undecided |
High |
|
| 2022-06-23 12:05:24 |
Daniel van Vugt |
bug task deleted |
gnome-shell (Ubuntu) |
|
|
| 2022-06-27 02:59:05 |
Andy Chi |
attachment added |
|
20220627-gnome-shell.log.tar.gz https://bugs.launchpad.net/oem-priority/+bug/1976204/+attachment/5599910/+files/20220627-gnome-shell.log.tar.gz |
|
| 2022-06-27 08:39:27 |
Daniel van Vugt |
tags |
apport-collected jammy jellyfish-edge-staging oem-priority originate-from-1967530 somerville wayland-session |
apport-collected fixed-in-ding-47 fixed-upstream jammy jellyfish-edge-staging oem-priority originate-from-1967530 somerville wayland-session |
|
| 2022-06-27 08:39:39 |
Daniel van Vugt |
gnome-shell-extension-desktop-icons-ng (Ubuntu): status |
In Progress |
Fix Committed |
|
| 2022-06-27 09:30:05 |
Daniel van Vugt |
bug watch added |
|
https://gitlab.gnome.org/GNOME/mutter/-/issues/2333 |
|
| 2022-06-27 09:30:05 |
Daniel van Vugt |
bug task added |
|
mutter |
|
| 2022-06-27 09:39:53 |
Bug Watch Updater |
mutter: status |
Unknown |
New |
|
| 2022-06-28 12:48:39 |
Jeremy Bícha |
nominated for series |
|
Ubuntu Jammy |
|
| 2022-06-28 12:48:39 |
Jeremy Bícha |
bug task added |
|
mutter (Ubuntu Jammy) |
|
| 2022-06-28 12:48:39 |
Jeremy Bícha |
bug task added |
|
gnome-shell-extension-desktop-icons-ng (Ubuntu Jammy) |
|
| 2022-06-28 12:48:50 |
Jeremy Bícha |
gnome-shell-extension-desktop-icons-ng (Ubuntu Jammy): status |
New |
Triaged |
|
| 2022-06-28 12:48:52 |
Jeremy Bícha |
gnome-shell-extension-desktop-icons-ng (Ubuntu Jammy): importance |
Undecided |
High |
|
| 2022-06-28 12:49:02 |
Jeremy Bícha |
gnome-shell-extension-desktop-icons-ng (Ubuntu Jammy): assignee |
|
Sergio Costas (rastersoft-gmail) |
|
| 2022-06-28 13:11:45 |
Jeremy Bícha |
bug task deleted |
mutter (Ubuntu Jammy) |
|
|
| 2022-06-28 13:11:53 |
Jeremy Bícha |
gnome-shell-extension-desktop-icons-ng (Ubuntu Jammy): status |
Triaged |
In Progress |
|
| 2022-06-28 13:16:09 |
Jeremy Bícha |
description |
[Summary]
The system will run into freeze if I connect the external monitor through DP/HDMI with dongle DA310 or Docking WD19TB
[Steps to reproduce]
1. Attact DA310 or WD19TB to DUT
2. Cold Boot into OS
3. Plug the DP/HDMI cable to DA310 or WD19TB
4. Check the external monitor has signal
5. Click keyboard or move mouse to check system can work well
[Expected result]
System won't be freeze with external monitor.
[Actual result]
Screen will freeze, but ssh can still reach out DUT. Keyboard and mouse
don't work during the screen freeze.
It can be recovered after unplug the external monitor sometime.
[gnome-shell stack trace]
五 27 22:12:31 ubuntu-XPS-9320 gnome-shell[1998]: Window manager warning: Overwriting existing binding of keysym 37 with keysym 37 (keycode 10).
五 27 22:12:31 ubuntu-XPS-9320 gnome-shell[1998]: Window manager warning: Overwriting existing binding of keysym 35 with keysym 35 (keycode e).
五 27 22:12:31 ubuntu-XPS-9320 gnome-shell[1998]: Window manager warning: Overwriting existing binding of keysym 33 with keysym 33 (keycode c).
五 27 22:12:31 ubuntu-XPS-9320 gnome-shell[1998]: meta_window_set_stack_position_no_sync: assertion 'window->stack_position >= 0' failed
五 27 22:12:55 ubuntu-XPS-9320 sudo[2916]: ubuntu : TTY=pts/2 ; PWD=/home/ubuntu ; USER=root ; COMMAND=/usr/bin/dmesg
五 27 22:12:55 ubuntu-XPS-9320 sudo[2916]: pam_unix(sudo:session): session opened for user root(uid=0) by ubuntu(uid=1001)
五 27 22:12:55 ubuntu-XPS-9320 sudo[2916]: pam_unix(sudo:session): session closed for user root
五 27 22:12:56 ubuntu-XPS-9320 gnome-shell[1998]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
五 27 22:12:56 ubuntu-XPS-9320 gnome-shell[1998]: == Stack trace for context 0x56156f8f04a0 ==
五 27 22:12:56 ubuntu-XPS-9320 gnome-shell[1998]: == Stack trace for context 0x56156f8f04a0 ==
五 27 22:12:56 ubuntu-XPS-9320 gnome-shell[1998]: The offending signal was window-added on MetaWorkspace 0x56156f916640.
五 27 22:12:56 ubuntu-XPS-9320 gnome-shell[1998]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
五 27 22:12:56 ubuntu-XPS-9320 gnome-shell[1998]: The offending signal was window-added on MetaWorkspace 0x56156f916640.
五 27 22:12:56 ubuntu-XPS-9320 gnome-shell[1998]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
This system is using OLED (3456x2160) panel, and I can't reproduce this issue on FHD panel.
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu82.1
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
DisplayManager: gdm3
DistroRelease: Ubuntu 22.04
InstallationDate: Installed on 2022-03-17 (75 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220313)
Package: gnome-shell 42.1-0ubuntu0.1
PackageArchitecture: amd64
ProcVersionSignature: Ubuntu 5.15.0-35.36-generic 5.15.35
RelatedPackageVersions: mutter-common 42.0-3ubuntu2
Tags: jammy wayland-session
Uname: Linux 5.15.0-35-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
_MarkForUpload: True |
[Summary]
The system will run into freeze if I connect the external monitor through DP/HDMI with dongle DA310 or Docking WD19TB
[Steps to reproduce]
1. Attact DA310 or WD19TB to DUT
2. Cold Boot into OS
3. Plug the DP/HDMI cable to DA310 or WD19TB
4. Check the external monitor has signal
5. Click keyboard or move mouse to check system can work well
[Expected result]
System won't be freeze with external monitor.
[Actual result]
Screen will freeze, but ssh can still reach out DUT. Keyboard and mouse
don't work during the screen freeze.
It can be recovered after unplug the external monitor sometime.
[gnome-shell stack trace]
五 27 22:12:31 ubuntu-XPS-9320 gnome-shell[1998]: Window manager warning: Overwriting existing binding of keysym 37 with keysym 37 (keycode 10).
五 27 22:12:31 ubuntu-XPS-9320 gnome-shell[1998]: Window manager warning: Overwriting existing binding of keysym 35 with keysym 35 (keycode e).
五 27 22:12:31 ubuntu-XPS-9320 gnome-shell[1998]: Window manager warning: Overwriting existing binding of keysym 33 with keysym 33 (keycode c).
五 27 22:12:31 ubuntu-XPS-9320 gnome-shell[1998]: meta_window_set_stack_position_no_sync: assertion 'window->stack_position >= 0' failed
五 27 22:12:55 ubuntu-XPS-9320 sudo[2916]: ubuntu : TTY=pts/2 ; PWD=/home/ubuntu ; USER=root ; COMMAND=/usr/bin/dmesg
五 27 22:12:55 ubuntu-XPS-9320 sudo[2916]: pam_unix(sudo:session): session opened for user root(uid=0) by ubuntu(uid=1001)
五 27 22:12:55 ubuntu-XPS-9320 sudo[2916]: pam_unix(sudo:session): session closed for user root
五 27 22:12:56 ubuntu-XPS-9320 gnome-shell[1998]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
五 27 22:12:56 ubuntu-XPS-9320 gnome-shell[1998]: == Stack trace for context 0x56156f8f04a0 ==
五 27 22:12:56 ubuntu-XPS-9320 gnome-shell[1998]: == Stack trace for context 0x56156f8f04a0 ==
五 27 22:12:56 ubuntu-XPS-9320 gnome-shell[1998]: The offending signal was window-added on MetaWorkspace 0x56156f916640.
五 27 22:12:56 ubuntu-XPS-9320 gnome-shell[1998]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
五 27 22:12:56 ubuntu-XPS-9320 gnome-shell[1998]: The offending signal was window-added on MetaWorkspace 0x56156f916640.
五 27 22:12:56 ubuntu-XPS-9320 gnome-shell[1998]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
This system is using OLED (3456x2160) panel, and I can't reproduce this issue on FHD panel.
[What could go wrong]
This 2 line bugfix maximizes the desktop icons window avoiding an infinite loop. This is a workaround for an apparent bug in mutter but fixing mutter is much more complicated.
The Desktop Icons NG GNOME Shell extension is enabled by default on Ubuntu 22.04 LTS so a bug here could make desktops unusable.
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu82.1
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
DisplayManager: gdm3
DistroRelease: Ubuntu 22.04
InstallationDate: Installed on 2022-03-17 (75 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220313)
Package: gnome-shell 42.1-0ubuntu0.1
PackageArchitecture: amd64
ProcVersionSignature: Ubuntu 5.15.0-35.36-generic 5.15.35
RelatedPackageVersions: mutter-common 42.0-3ubuntu2
Tags: jammy wayland-session
Uname: Linux 5.15.0-35-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
_MarkForUpload: True |
|
| 2022-06-28 15:51:01 |
Brian Murray |
gnome-shell-extension-desktop-icons-ng (Ubuntu Jammy): status |
In Progress |
Fix Committed |
|
| 2022-06-28 15:51:02 |
Brian Murray |
bug |
|
|
added subscriber Ubuntu Stable Release Updates Team |
| 2022-06-28 15:51:04 |
Brian Murray |
bug |
|
|
added subscriber SRU Verification |
| 2022-06-28 15:51:10 |
Brian Murray |
tags |
apport-collected fixed-in-ding-47 fixed-upstream jammy jellyfish-edge-staging oem-priority originate-from-1967530 somerville wayland-session |
apport-collected fixed-in-ding-47 fixed-upstream jammy jellyfish-edge-staging oem-priority originate-from-1967530 somerville verification-needed verification-needed-jammy wayland-session |
|
| 2022-06-28 18:59:17 |
Launchpad Janitor |
gnome-shell-extension-desktop-icons-ng (Ubuntu): status |
Fix Committed |
Fix Released |
|
| 2022-06-29 03:46:26 |
Andy Chi |
tags |
apport-collected fixed-in-ding-47 fixed-upstream jammy jellyfish-edge-staging oem-priority originate-from-1967530 somerville verification-needed verification-needed-jammy wayland-session |
apport-collected fixed-in-ding-47 fixed-upstream jammy jellyfish-edge-staging oem-priority originate-from-1967530 somerville verification-done verification-done-jammy wayland-session |
|
| 2022-07-04 05:10:07 |
Yuan-Chen Cheng |
description |
[Summary]
The system will run into freeze if I connect the external monitor through DP/HDMI with dongle DA310 or Docking WD19TB
[Steps to reproduce]
1. Attact DA310 or WD19TB to DUT
2. Cold Boot into OS
3. Plug the DP/HDMI cable to DA310 or WD19TB
4. Check the external monitor has signal
5. Click keyboard or move mouse to check system can work well
[Expected result]
System won't be freeze with external monitor.
[Actual result]
Screen will freeze, but ssh can still reach out DUT. Keyboard and mouse
don't work during the screen freeze.
It can be recovered after unplug the external monitor sometime.
[gnome-shell stack trace]
五 27 22:12:31 ubuntu-XPS-9320 gnome-shell[1998]: Window manager warning: Overwriting existing binding of keysym 37 with keysym 37 (keycode 10).
五 27 22:12:31 ubuntu-XPS-9320 gnome-shell[1998]: Window manager warning: Overwriting existing binding of keysym 35 with keysym 35 (keycode e).
五 27 22:12:31 ubuntu-XPS-9320 gnome-shell[1998]: Window manager warning: Overwriting existing binding of keysym 33 with keysym 33 (keycode c).
五 27 22:12:31 ubuntu-XPS-9320 gnome-shell[1998]: meta_window_set_stack_position_no_sync: assertion 'window->stack_position >= 0' failed
五 27 22:12:55 ubuntu-XPS-9320 sudo[2916]: ubuntu : TTY=pts/2 ; PWD=/home/ubuntu ; USER=root ; COMMAND=/usr/bin/dmesg
五 27 22:12:55 ubuntu-XPS-9320 sudo[2916]: pam_unix(sudo:session): session opened for user root(uid=0) by ubuntu(uid=1001)
五 27 22:12:55 ubuntu-XPS-9320 sudo[2916]: pam_unix(sudo:session): session closed for user root
五 27 22:12:56 ubuntu-XPS-9320 gnome-shell[1998]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
五 27 22:12:56 ubuntu-XPS-9320 gnome-shell[1998]: == Stack trace for context 0x56156f8f04a0 ==
五 27 22:12:56 ubuntu-XPS-9320 gnome-shell[1998]: == Stack trace for context 0x56156f8f04a0 ==
五 27 22:12:56 ubuntu-XPS-9320 gnome-shell[1998]: The offending signal was window-added on MetaWorkspace 0x56156f916640.
五 27 22:12:56 ubuntu-XPS-9320 gnome-shell[1998]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
五 27 22:12:56 ubuntu-XPS-9320 gnome-shell[1998]: The offending signal was window-added on MetaWorkspace 0x56156f916640.
五 27 22:12:56 ubuntu-XPS-9320 gnome-shell[1998]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
This system is using OLED (3456x2160) panel, and I can't reproduce this issue on FHD panel.
[What could go wrong]
This 2 line bugfix maximizes the desktop icons window avoiding an infinite loop. This is a workaround for an apparent bug in mutter but fixing mutter is much more complicated.
The Desktop Icons NG GNOME Shell extension is enabled by default on Ubuntu 22.04 LTS so a bug here could make desktops unusable.
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu82.1
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
DisplayManager: gdm3
DistroRelease: Ubuntu 22.04
InstallationDate: Installed on 2022-03-17 (75 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220313)
Package: gnome-shell 42.1-0ubuntu0.1
PackageArchitecture: amd64
ProcVersionSignature: Ubuntu 5.15.0-35.36-generic 5.15.35
RelatedPackageVersions: mutter-common 42.0-3ubuntu2
Tags: jammy wayland-session
Uname: Linux 5.15.0-35-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
_MarkForUpload: True |
[Summary]
The system will run into freeze if I connect the external monitor through DP/HDMI with dongle DA310 or Docking WD19TB
Per further check, it will freeze only if the built-in and external display has different scale factors.
[Steps to reproduce]
1. Attact DA310 or WD19TB to DUT
2. Cold Boot into OS
3. Plug the DP/HDMI cable to DA310 or WD19TB
4. Check the external monitor has signal
5. Click keyboard or move mouse to check system can work well
[Expected result]
System won't be freeze with external monitor.
[Actual result]
Screen will freeze, but ssh can still reach out DUT. Keyboard and mouse
don't work during the screen freeze.
It can be recovered after unplug the external monitor sometime.
[gnome-shell stack trace]
五 27 22:12:31 ubuntu-XPS-9320 gnome-shell[1998]: Window manager warning: Overwriting existing binding of keysym 37 with keysym 37 (keycode 10).
五 27 22:12:31 ubuntu-XPS-9320 gnome-shell[1998]: Window manager warning: Overwriting existing binding of keysym 35 with keysym 35 (keycode e).
五 27 22:12:31 ubuntu-XPS-9320 gnome-shell[1998]: Window manager warning: Overwriting existing binding of keysym 33 with keysym 33 (keycode c).
五 27 22:12:31 ubuntu-XPS-9320 gnome-shell[1998]: meta_window_set_stack_position_no_sync: assertion 'window->stack_position >= 0' failed
五 27 22:12:55 ubuntu-XPS-9320 sudo[2916]: ubuntu : TTY=pts/2 ; PWD=/home/ubuntu ; USER=root ; COMMAND=/usr/bin/dmesg
五 27 22:12:55 ubuntu-XPS-9320 sudo[2916]: pam_unix(sudo:session): session opened for user root(uid=0) by ubuntu(uid=1001)
五 27 22:12:55 ubuntu-XPS-9320 sudo[2916]: pam_unix(sudo:session): session closed for user root
五 27 22:12:56 ubuntu-XPS-9320 gnome-shell[1998]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
五 27 22:12:56 ubuntu-XPS-9320 gnome-shell[1998]: == Stack trace for context 0x56156f8f04a0 ==
五 27 22:12:56 ubuntu-XPS-9320 gnome-shell[1998]: == Stack trace for context 0x56156f8f04a0 ==
五 27 22:12:56 ubuntu-XPS-9320 gnome-shell[1998]: The offending signal was window-added on MetaWorkspace 0x56156f916640.
五 27 22:12:56 ubuntu-XPS-9320 gnome-shell[1998]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
五 27 22:12:56 ubuntu-XPS-9320 gnome-shell[1998]: The offending signal was window-added on MetaWorkspace 0x56156f916640.
五 27 22:12:56 ubuntu-XPS-9320 gnome-shell[1998]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
This system is using OLED (3456x2160) panel, and I can't reproduce this issue on FHD panel.
[What could go wrong]
This 2 line bugfix maximizes the desktop icons window avoiding an infinite loop. This is a workaround for an apparent bug in mutter but fixing mutter is much more complicated.
The Desktop Icons NG GNOME Shell extension is enabled by default on Ubuntu 22.04 LTS so a bug here could make desktops unusable.
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu82.1
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
DisplayManager: gdm3
DistroRelease: Ubuntu 22.04
InstallationDate: Installed on 2022-03-17 (75 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220313)
Package: gnome-shell 42.1-0ubuntu0.1
PackageArchitecture: amd64
ProcVersionSignature: Ubuntu 5.15.0-35.36-generic 5.15.35
RelatedPackageVersions: mutter-common 42.0-3ubuntu2
Tags: jammy wayland-session
Uname: Linux 5.15.0-35-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
_MarkForUpload: True |
|
| 2022-07-05 19:52:42 |
Launchpad Janitor |
gnome-shell-extension-desktop-icons-ng (Ubuntu Jammy): status |
Fix Committed |
Fix Released |
|
| 2022-07-05 19:52:47 |
Brian Murray |
removed subscriber Ubuntu Stable Release Updates Team |
|
|
|
| 2022-07-06 06:31:55 |
Andy Chi |
oem-priority: status |
Confirmed |
Fix Committed |
|
| 2022-07-13 07:46:54 |
Daniel van Vugt |
mutter (Ubuntu): assignee |
Daniel van Vugt (vanvugt) |
|
|
| 2022-07-13 07:46:57 |
Daniel van Vugt |
mutter (Ubuntu): importance |
High |
Medium |
|
| 2022-07-13 07:47:00 |
Daniel van Vugt |
mutter (Ubuntu): status |
In Progress |
Triaged |
|
| 2022-09-06 08:19:41 |
Daniel van Vugt |
tags |
apport-collected fixed-in-ding-47 fixed-upstream jammy jellyfish-edge-staging oem-priority originate-from-1967530 somerville verification-done verification-done-jammy wayland-session |
apport-collected fixed-in-ding-47 jammy jellyfish-edge-staging oem-priority originate-from-1967530 somerville verification-done verification-done-jammy wayland-session |
|
| 2023-06-17 05:12:12 |
Andy Chi |
oem-priority: status |
Fix Committed |
Fix Released |
|
