[Desktop-packages] [Bug 1918880] Re: pulseaudio threaded-ml suspend issue
Please check that you haven't enabled: realtime-scheduling = yes in /etc/pulse/daemon.conf. And if the problem continues to occur after that then please report it to the developers at: https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/issues and tell us the new issue ID. ** Changed in: pulseaudio (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1918880 Title: pulseaudio threaded-ml suspend issue Status in pulseaudio package in Ubuntu: Incomplete Bug description: My laptop failed to suspend overnight and was unresponsive when I opened it back up. This is on Ubuntu 20.04.2 LTS with kernel 5.6.0-1048-oem and pulseaudio:amd64/focal-updates 1:13.99.1-1ubuntu3.10 uptodate. In syslog, I found a stream of suspend attempts with pulseaudio-related issues repeating in a 40s cycle, so reporting this as a PA issue. Mar 12 00:08:31 churn systemd[1]: Reached target Sleep. Mar 12 00:08:31 churn upowerd[1698]: Could not acquire inhibitor lock: GDBus.Error:org.freedesktop.login1.OperationInProgress: The operation inhibition has been requested for is already running Mar 12 00:08:31 churn systemd[1]: Starting Suspend... Mar 12 00:08:31 churn ModemManager[1427]: [sleep-monitor] inhibit failed: GDBus.Error:org.freedesktop.login1.OperationInProgress: The operation inhibition has been requested for is already running Mar 12 00:08:31 churn kernel: [883904.845262] iwlwifi :00:14.3: Applying debug destination EXTERNAL_DRAM Mar 12 00:08:31 churn ModemManager[1427]: Couldn't check support for device '/sys/devices/pci:00/:00:14.3': Device support check task already available for device '/sys/devices/pci:00/:00:14.3' Mar 12 00:08:31 churn systemd-sleep[516395]: Suspending system... Mar 12 00:08:31 churn kernel: [883904.853576] PM: suspend entry (s2idle) Mar 12 00:08:51 churn kernel: [883904.856917] Filesystems sync: 0.003 seconds Mar 12 00:08:51 churn kernel: [883904.857284] Freezing user space processes ... Mar 12 00:08:51 churn kernel: [883904.991749] iwlwifi :00:14.3: FW already configured (0) - re-configuring Mar 12 00:08:51 churn kernel: [883924.868069] Freezing of tasks failed after 20.010 seconds (1 tasks refusing to freeze, wq_busy=0): Mar 12 00:08:51 churn kernel: [883924.868160] threaded-ml D0 3306 2128 0x80004326 Mar 12 00:08:51 churn kernel: [883924.868166] Call Trace: Mar 12 00:08:51 churn kernel: [883924.868183] __schedule+0x2d8/0x760 Mar 12 00:08:51 churn kernel: [883924.868188] schedule+0x55/0xc0 Mar 12 00:08:51 churn kernel: [883924.868195] do_exit.cold+0x9f/0xb5 Mar 12 00:08:51 churn kernel: [883924.868200] rewind_stack_do_exit+0x17/0x20 Mar 12 00:08:51 churn kernel: [883924.868205] RIP: 0033:0x7fc8a96ebcb9 Mar 12 00:08:51 churn kernel: [883924.868216] Code: Bad RIP value. Mar 12 00:08:51 churn kernel: [883924.868219] RSP: 002b:7fc899504850 EFLAGS: 0293 ORIG_RAX: 0007 Mar 12 00:08:51 churn kernel: [883924.868223] RAX: fdfc RBX: 208bbe357f60 RCX: 7fc8a96ebcb9 Mar 12 00:08:51 churn kernel: [883924.868225] RDX: 7530 RSI: 0003 RDI: 208bbe357f60 Mar 12 00:08:51 churn kernel: [883924.868227] RBP: 0003 R08: R09: 1587756a Mar 12 00:08:51 churn kernel: [883924.868229] R10: 0f90 R11: 0293 R12: 7530 Mar 12 00:08:51 churn kernel: [883924.868231] R13: 7530 R14: 208bbe3285d0 R15: 7fff6f13d440 Mar 12 00:08:51 churn kernel: [883924.868427] OOM killer enabled. Mar 12 00:08:51 churn rtkit-daemon[1608]: The canary thread is apparently starving. Taking action. Mar 12 00:08:51 churn NetworkManager[1297]: [1615504131.1026] device (p2p-dev-wlp0s20f3): state change: unmanaged -> unavailable (reason 'managed', sys-iface-state: 'managed') Mar 12 00:08:51 churn rtkit-daemon[1608]: Demoting known real-time threads. Mar 12 00:08:51 churn NetworkManager[1297]: [1615504131.1036] manager: NetworkManager state is now DISCONNECTED Mar 12 00:08:51 churn rtkit-daemon[1608]: Demoted 0 threads. Mar 12 00:08:51 churn NetworkManager[1297]: [1615504131.1039] manager: sleep: sleep requested (sleeping: no enabled: yes) Mar 12 00:08:51 churn NetworkManager[1297]: [1615504131.1039] device (wlp0s20f3): state change: unavailable -> unmanaged (reason 'sleeping', sys-iface-state: 'managed') Mar 12 00:08:51 churn pulseaudio[2134]: q overrun, queuing locally Mar 12 00:08:51 churn kernel: [883924.868429] Restarting tasks ... done. Mar 12 00:08:51 churn pulseaudio[2134]: message repeated 4 times: [ q overrun, queuing locally] Mar 12 00:08:51 churn NetworkManager[1297]: [1615504131.1245] device (p2p-dev-wlp0s20f3): state change: unavailable -> unmanaged (reason 'sleeping',
[Desktop-packages] [Bug 1918738] Re: Regression: Onscreen Keyboard Backspace, Enter and Capitalize do not work
Thanks Daniel, great work as always! Confirmed that downgrading to gjs 1.67.2-1 and libgjs0g 1.67.2-1 solves the problem. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gjs in Ubuntu. https://bugs.launchpad.net/bugs/1918738 Title: Regression: Onscreen Keyboard Backspace, Enter and Capitalize do not work Status in gjs package in Ubuntu: In Progress Status in gnome-shell package in Ubuntu: In Progress Bug description: Title pretty much says it all: I'm testing Ubuntu Hirsute (21.04), fully upgraded as of today (Gnome-shell 3.38.3) and the osk keys for Backspace, Enter and Capitalize as well as for collapsing the keyboard do not work. Pressing them just does nothing. Related logs in jouralctl output: _press@resource:///org/gnome/shell/ui/keyboard.js:337:39 _makeKey/<@resource:///org/gnome/shell/ui/keyboard.js:464:22 Mär 11 23:06:02 pc gnome-shell[15039]: JS ERROR: Error: Argument wc: value is out of range for uint32 _getKeyval@resource:///org/gnome/shell/ui/keyboard.js:330:24 _release@resource:///org/gnome/shell/ui/keyboard.js:370:36 _makeKey/<@resource:///org/gnome/shell/ui/keyboard.js:468:22 Mär 11 23:06:03 pc gnome-shell[15039]: JS ERROR: Error: Argument wc: value is out of range for uint32 _getKeyval@resource:///org/gnome/shell/ui/keyboard.js:330:24 _press@resource:///org/gnome/shell/ui/keyboard.js:337:39 _makeKey/<@resource:///org/gnome/shell/ui/keyboard.js:464:22 Mär 11 23:06:03 pc gnome-shell[15039]: JS ERROR: Error: Argument wc: value is out of range for uint32 _getKeyval@resource:///org/gnome/shell/ui/keyboard.js:330:24 _release@resource:///org/gnome/shell/ui/keyboard.js:370:36 _makeKey/<@resource:///org/gnome/shell/ui/keyboard.js:468:22 Mär 11 23:06:04 pc gnome-shell[15039]: JS ERROR: Error: Argument wc: value is out of range for uint32 _getKeyval@resource:///org/gnome/shell/ui/keyboard.js:330:24 _press@resource:///org/gnome/shell/ui/keyboard.js:337:39 _makeKey/<@resource:///org/gnome/shell/ui/keyboard.js:464:22 Mär 11 23:06:04 pc gnome-shell[15039]: JS ERROR: Error: Argument wc: value is out of range for uint32 _getKeyval@resource:///org/gnome/shell/ui/keyboard.js:330:24 _release@resource:///org/gnome/shell/ui/keyboard.js:370:36 _makeKey/<@resource:///org/gnome/shell/ui/keyboard.js:468:22 Mär 11 23:06:04 pc gnome-shell[15039]: JS ERROR: Error: Argument wc: value is out of range for uint32 _getKeyval@resource:///org/gnome/shell/ui/keyboard.js:330:24 _press@resource:///org/gnome/shell/ui/keyboard.js:337:39 _makeKey/<@resource:///org/gnome/shell/ui/keyboard.js:464:22 Mär 11 23:06:04 pc gnome-shell[15039]: JS ERROR: Error: Argument wc: value is out of range for uint32 _getKeyval@resource:///org/gnome/shell/ui/keyboard.js:330:24 _release@resource:///org/gnome/shell/ui/keyboard.js:370:36 _makeKey/<@resource:///org/gnome/shell/ui/keyboard.js:468:22 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gjs/+bug/1918738/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1918880] [NEW] pulseaudio threaded-ml suspend issue
Public bug reported: My laptop failed to suspend overnight and was unresponsive when I opened it back up. This is on Ubuntu 20.04.2 LTS with kernel 5.6.0-1048-oem and pulseaudio:amd64/focal-updates 1:13.99.1-1ubuntu3.10 uptodate. In syslog, I found a stream of suspend attempts with pulseaudio-related issues repeating in a 40s cycle, so reporting this as a PA issue. Mar 12 00:08:31 churn systemd[1]: Reached target Sleep. Mar 12 00:08:31 churn upowerd[1698]: Could not acquire inhibitor lock: GDBus.Error:org.freedesktop.login1.OperationInProgress: The operation inhibition has been requested for is already running Mar 12 00:08:31 churn systemd[1]: Starting Suspend... Mar 12 00:08:31 churn ModemManager[1427]: [sleep-monitor] inhibit failed: GDBus.Error:org.freedesktop.login1.OperationInProgress: The operation inhibition has been requested for is already running Mar 12 00:08:31 churn kernel: [883904.845262] iwlwifi :00:14.3: Applying debug destination EXTERNAL_DRAM Mar 12 00:08:31 churn ModemManager[1427]: Couldn't check support for device '/sys/devices/pci:00/:00:14.3': Device support check task already available for device '/sys/devices/pci:00/:00:14.3' Mar 12 00:08:31 churn systemd-sleep[516395]: Suspending system... Mar 12 00:08:31 churn kernel: [883904.853576] PM: suspend entry (s2idle) Mar 12 00:08:51 churn kernel: [883904.856917] Filesystems sync: 0.003 seconds Mar 12 00:08:51 churn kernel: [883904.857284] Freezing user space processes ... Mar 12 00:08:51 churn kernel: [883904.991749] iwlwifi :00:14.3: FW already configured (0) - re-configuring Mar 12 00:08:51 churn kernel: [883924.868069] Freezing of tasks failed after 20.010 seconds (1 tasks refusing to freeze, wq_busy=0): Mar 12 00:08:51 churn kernel: [883924.868160] threaded-ml D0 3306 2128 0x80004326 Mar 12 00:08:51 churn kernel: [883924.868166] Call Trace: Mar 12 00:08:51 churn kernel: [883924.868183] __schedule+0x2d8/0x760 Mar 12 00:08:51 churn kernel: [883924.868188] schedule+0x55/0xc0 Mar 12 00:08:51 churn kernel: [883924.868195] do_exit.cold+0x9f/0xb5 Mar 12 00:08:51 churn kernel: [883924.868200] rewind_stack_do_exit+0x17/0x20 Mar 12 00:08:51 churn kernel: [883924.868205] RIP: 0033:0x7fc8a96ebcb9 Mar 12 00:08:51 churn kernel: [883924.868216] Code: Bad RIP value. Mar 12 00:08:51 churn kernel: [883924.868219] RSP: 002b:7fc899504850 EFLAGS: 0293 ORIG_RAX: 0007 Mar 12 00:08:51 churn kernel: [883924.868223] RAX: fdfc RBX: 208bbe357f60 RCX: 7fc8a96ebcb9 Mar 12 00:08:51 churn kernel: [883924.868225] RDX: 7530 RSI: 0003 RDI: 208bbe357f60 Mar 12 00:08:51 churn kernel: [883924.868227] RBP: 0003 R08: R09: 1587756a Mar 12 00:08:51 churn kernel: [883924.868229] R10: 0f90 R11: 0293 R12: 7530 Mar 12 00:08:51 churn kernel: [883924.868231] R13: 7530 R14: 208bbe3285d0 R15: 7fff6f13d440 Mar 12 00:08:51 churn kernel: [883924.868427] OOM killer enabled. Mar 12 00:08:51 churn rtkit-daemon[1608]: The canary thread is apparently starving. Taking action. Mar 12 00:08:51 churn NetworkManager[1297]: [1615504131.1026] device (p2p-dev-wlp0s20f3): state change: unmanaged -> unavailable (reason 'managed', sys-iface-state: 'managed') Mar 12 00:08:51 churn rtkit-daemon[1608]: Demoting known real-time threads. Mar 12 00:08:51 churn NetworkManager[1297]: [1615504131.1036] manager: NetworkManager state is now DISCONNECTED Mar 12 00:08:51 churn rtkit-daemon[1608]: Demoted 0 threads. Mar 12 00:08:51 churn NetworkManager[1297]: [1615504131.1039] manager: sleep: sleep requested (sleeping: no enabled: yes) Mar 12 00:08:51 churn NetworkManager[1297]: [1615504131.1039] device (wlp0s20f3): state change: unavailable -> unmanaged (reason 'sleeping', sys-iface-state: 'managed') Mar 12 00:08:51 churn pulseaudio[2134]: q overrun, queuing locally Mar 12 00:08:51 churn kernel: [883924.868429] Restarting tasks ... done. Mar 12 00:08:51 churn pulseaudio[2134]: message repeated 4 times: [ q overrun, queuing locally] Mar 12 00:08:51 churn NetworkManager[1297]: [1615504131.1245] device (p2p-dev-wlp0s20f3): state change: unavailable -> unmanaged (reason 'sleeping', sys-iface-state: 'managed') Mar 12 00:08:51 churn NetworkManager[1297]: [1615504131.1247] manager: NetworkManager state is now ASLEEP Mar 12 00:08:51 churn kernel: [883924.916329] PM: suspend exit Mar 12 00:08:51 churn kernel: [883924.916367] PM: suspend entry (s2idle) Mar 12 00:08:51 churn kernel: [883924.922458] Filesystems sync: 0.006 seconds Mar 12 00:09:11 churn kernel: [883924.932177] Freezing user space processes ... Mar 12 00:09:11 churn kernel: [883944.944348] Freezing of tasks failed after 20.012 seconds (1 tasks refusing to freeze, wq_busy=0): Mar 12 00:09:11 churn kernel: [883944.93] threaded-ml D0 3306 2128 0x80004326 Mar 12 00:09:11 churn kernel: [883944.944450] Call
[Desktop-packages] [Bug 1918738] Re: Regression: Onscreen Keyboard Backspace, Enter and Capitalize do not work
Fix proposed to gnome-shell: https://gitlab.gnome.org/GNOME/gnome- shell/-/merge_requests/1758 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gjs in Ubuntu. https://bugs.launchpad.net/bugs/1918738 Title: Regression: Onscreen Keyboard Backspace, Enter and Capitalize do not work Status in gjs package in Ubuntu: In Progress Status in gnome-shell package in Ubuntu: In Progress Bug description: Title pretty much says it all: I'm testing Ubuntu Hirsute (21.04), fully upgraded as of today (Gnome-shell 3.38.3) and the osk keys for Backspace, Enter and Capitalize as well as for collapsing the keyboard do not work. Pressing them just does nothing. Related logs in jouralctl output: _press@resource:///org/gnome/shell/ui/keyboard.js:337:39 _makeKey/<@resource:///org/gnome/shell/ui/keyboard.js:464:22 Mär 11 23:06:02 pc gnome-shell[15039]: JS ERROR: Error: Argument wc: value is out of range for uint32 _getKeyval@resource:///org/gnome/shell/ui/keyboard.js:330:24 _release@resource:///org/gnome/shell/ui/keyboard.js:370:36 _makeKey/<@resource:///org/gnome/shell/ui/keyboard.js:468:22 Mär 11 23:06:03 pc gnome-shell[15039]: JS ERROR: Error: Argument wc: value is out of range for uint32 _getKeyval@resource:///org/gnome/shell/ui/keyboard.js:330:24 _press@resource:///org/gnome/shell/ui/keyboard.js:337:39 _makeKey/<@resource:///org/gnome/shell/ui/keyboard.js:464:22 Mär 11 23:06:03 pc gnome-shell[15039]: JS ERROR: Error: Argument wc: value is out of range for uint32 _getKeyval@resource:///org/gnome/shell/ui/keyboard.js:330:24 _release@resource:///org/gnome/shell/ui/keyboard.js:370:36 _makeKey/<@resource:///org/gnome/shell/ui/keyboard.js:468:22 Mär 11 23:06:04 pc gnome-shell[15039]: JS ERROR: Error: Argument wc: value is out of range for uint32 _getKeyval@resource:///org/gnome/shell/ui/keyboard.js:330:24 _press@resource:///org/gnome/shell/ui/keyboard.js:337:39 _makeKey/<@resource:///org/gnome/shell/ui/keyboard.js:464:22 Mär 11 23:06:04 pc gnome-shell[15039]: JS ERROR: Error: Argument wc: value is out of range for uint32 _getKeyval@resource:///org/gnome/shell/ui/keyboard.js:330:24 _release@resource:///org/gnome/shell/ui/keyboard.js:370:36 _makeKey/<@resource:///org/gnome/shell/ui/keyboard.js:468:22 Mär 11 23:06:04 pc gnome-shell[15039]: JS ERROR: Error: Argument wc: value is out of range for uint32 _getKeyval@resource:///org/gnome/shell/ui/keyboard.js:330:24 _press@resource:///org/gnome/shell/ui/keyboard.js:337:39 _makeKey/<@resource:///org/gnome/shell/ui/keyboard.js:464:22 Mär 11 23:06:04 pc gnome-shell[15039]: JS ERROR: Error: Argument wc: value is out of range for uint32 _getKeyval@resource:///org/gnome/shell/ui/keyboard.js:330:24 _release@resource:///org/gnome/shell/ui/keyboard.js:370:36 _makeKey/<@resource:///org/gnome/shell/ui/keyboard.js:468:22 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gjs/+bug/1918738/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1918738] Re: Regression: Onscreen Keyboard Backspace, Enter and Capitalize do not work
** Changed in: gnome-shell (Ubuntu) Assignee: (unassigned) => Daniel van Vugt (vanvugt) ** Changed in: gnome-shell (Ubuntu) Status: Triaged => In Progress -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gjs in Ubuntu. https://bugs.launchpad.net/bugs/1918738 Title: Regression: Onscreen Keyboard Backspace, Enter and Capitalize do not work Status in gjs package in Ubuntu: In Progress Status in gnome-shell package in Ubuntu: In Progress Bug description: Title pretty much says it all: I'm testing Ubuntu Hirsute (21.04), fully upgraded as of today (Gnome-shell 3.38.3) and the osk keys for Backspace, Enter and Capitalize as well as for collapsing the keyboard do not work. Pressing them just does nothing. Related logs in jouralctl output: _press@resource:///org/gnome/shell/ui/keyboard.js:337:39 _makeKey/<@resource:///org/gnome/shell/ui/keyboard.js:464:22 Mär 11 23:06:02 pc gnome-shell[15039]: JS ERROR: Error: Argument wc: value is out of range for uint32 _getKeyval@resource:///org/gnome/shell/ui/keyboard.js:330:24 _release@resource:///org/gnome/shell/ui/keyboard.js:370:36 _makeKey/<@resource:///org/gnome/shell/ui/keyboard.js:468:22 Mär 11 23:06:03 pc gnome-shell[15039]: JS ERROR: Error: Argument wc: value is out of range for uint32 _getKeyval@resource:///org/gnome/shell/ui/keyboard.js:330:24 _press@resource:///org/gnome/shell/ui/keyboard.js:337:39 _makeKey/<@resource:///org/gnome/shell/ui/keyboard.js:464:22 Mär 11 23:06:03 pc gnome-shell[15039]: JS ERROR: Error: Argument wc: value is out of range for uint32 _getKeyval@resource:///org/gnome/shell/ui/keyboard.js:330:24 _release@resource:///org/gnome/shell/ui/keyboard.js:370:36 _makeKey/<@resource:///org/gnome/shell/ui/keyboard.js:468:22 Mär 11 23:06:04 pc gnome-shell[15039]: JS ERROR: Error: Argument wc: value is out of range for uint32 _getKeyval@resource:///org/gnome/shell/ui/keyboard.js:330:24 _press@resource:///org/gnome/shell/ui/keyboard.js:337:39 _makeKey/<@resource:///org/gnome/shell/ui/keyboard.js:464:22 Mär 11 23:06:04 pc gnome-shell[15039]: JS ERROR: Error: Argument wc: value is out of range for uint32 _getKeyval@resource:///org/gnome/shell/ui/keyboard.js:330:24 _release@resource:///org/gnome/shell/ui/keyboard.js:370:36 _makeKey/<@resource:///org/gnome/shell/ui/keyboard.js:468:22 Mär 11 23:06:04 pc gnome-shell[15039]: JS ERROR: Error: Argument wc: value is out of range for uint32 _getKeyval@resource:///org/gnome/shell/ui/keyboard.js:330:24 _press@resource:///org/gnome/shell/ui/keyboard.js:337:39 _makeKey/<@resource:///org/gnome/shell/ui/keyboard.js:464:22 Mär 11 23:06:04 pc gnome-shell[15039]: JS ERROR: Error: Argument wc: value is out of range for uint32 _getKeyval@resource:///org/gnome/shell/ui/keyboard.js:330:24 _release@resource:///org/gnome/shell/ui/keyboard.js:370:36 _makeKey/<@resource:///org/gnome/shell/ui/keyboard.js:468:22 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gjs/+bug/1918738/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1918874] [NEW] Application icons superposed to open windows
Public bug reported: Click on 'Show Applications' the icons of the applications appear but the windows of the applications does not disappear so the icons are hidden. problem happens with both sessions Xorg and Wayland after last updates see attached picture ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: nautilus 1:3.38.2-1ubuntu1 ProcVersionSignature: Ubuntu 5.10.0-14.15-generic 5.10.11 Uname: Linux 5.10.0-14-generic x86_64 ApportVersion: 2.20.11-0ubuntu60 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Fri Mar 12 07:36:41 2021 GsettingsChanges: b'org.gnome.nautilus.window-state' b'initial-size' b'(1288, 663)' b'org.gnome.nautilus.list-view' b'default-column-order' b"['name', 'size', 'type', 'owner', 'group', 'permissions', 'where', 'date_modified', 'date_modified_with_time', 'date_accessed', 'recency', 'starred', 'detailed_type']" InstallationDate: Installed on 2021-02-28 (11 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Alpha amd64 (20210228) SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: evince3.39.2-1 file-roller 3.38.0-1 nautilus-extension-gnome-terminal 3.38.1-1ubuntu1 nautilus-share0.7.3-2ubuntu3 ** Affects: nautilus (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug hirsute wayland-session ** Attachment added: "Screenshot from 2021-03-12 07-27-19.png" https://bugs.launchpad.net/bugs/1918874/+attachment/5476023/+files/Screenshot%20from%202021-03-12%2007-27-19.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1918874 Title: Application icons superposed to open windows Status in nautilus package in Ubuntu: New Bug description: Click on 'Show Applications' the icons of the applications appear but the windows of the applications does not disappear so the icons are hidden. problem happens with both sessions Xorg and Wayland after last updates see attached picture ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: nautilus 1:3.38.2-1ubuntu1 ProcVersionSignature: Ubuntu 5.10.0-14.15-generic 5.10.11 Uname: Linux 5.10.0-14-generic x86_64 ApportVersion: 2.20.11-0ubuntu60 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Fri Mar 12 07:36:41 2021 GsettingsChanges: b'org.gnome.nautilus.window-state' b'initial-size' b'(1288, 663)' b'org.gnome.nautilus.list-view' b'default-column-order' b"['name', 'size', 'type', 'owner', 'group', 'permissions', 'where', 'date_modified', 'date_modified_with_time', 'date_accessed', 'recency', 'starred', 'detailed_type']" InstallationDate: Installed on 2021-02-28 (11 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Alpha amd64 (20210228) SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: evince3.39.2-1 file-roller 3.38.0-1 nautilus-extension-gnome-terminal 3.38.1-1ubuntu1 nautilus-share0.7.3-2ubuntu3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1918874/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1918666] Re: Cannot close the modal "Connect to Wifi" window to return to desktop
Fix proposed for gnome-shell: https://gitlab.gnome.org/GNOME/gnome- shell/-/merge_requests/1757 ** Changed in: gnome-shell (Ubuntu) Assignee: (unassigned) => Daniel van Vugt (vanvugt) ** Changed in: gnome-shell (Ubuntu) Status: Triaged => In Progress -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gjs in Ubuntu. https://bugs.launchpad.net/bugs/1918666 Title: Cannot close the modal "Connect to Wifi" window to return to desktop Status in gjs package in Ubuntu: In Progress Status in gnome-shell package in Ubuntu: In Progress Bug description: When I select the task bar menu, click on the Wifi and select "Select to network", a modal window appears that allows me to select a Wifi network. After I have clicked on one of the networks, normally, when I click Cancel or Connect, the modal window disappears and returns me to the desktop. With the current gnome-shell, this modal window persists and I cannot access the desktop - this is both in Wayland and in X. Connect doesn't seem to work - it's like the buttons are no longer accepting clicks. The ESC key also doesn't do anything. (If I don't click on a network, the ESC key does work, and so does Cancel.) I think I once managed to get Alt-Ctrl-F1 to bring back the GDM login window, but the modal window was still there when I went back into the desktop. Alt-F2 didn't work so I couldn't try re-starting gnome-shell. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: gnome-shell 3.38.3-3ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-11.12-generic 5.11.0 Uname: Linux 5.11.0-11-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu60 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Thu Mar 11 20:35:24 2021 DisplayManager: gdm3 RelatedPackageVersions: mutter-common 3.38.3-3ubuntu2 SourcePackage: gnome-shell UpgradeStatus: Upgraded to hirsute on 2021-02-24 (15 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gjs/+bug/1918666/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1918855] Re: Xorg xserver got signal 6 to abort
After two times pass for using mesa lib in ppa:oibaf/graphics-drivers, I reproduce the x server stop error with different stacktrace: Mar 12 12:43:12 stress-ng: memory (MB): total 15729.63, free 152.17, shared 43.86, buffer 0.36, swap 2048.00, free swap 0.01 Mar 12 12:43:12 /usr/lib/gdm3/gdm-x-session[1949]: (EE) Mar 12 12:43:12 /usr/lib/gdm3/gdm-x-session[1949]: (EE) Backtrace: Mar 12 12:43:12 /usr/lib/gdm3/gdm-x-session[1949]: (EE) 0: /usr/lib/xorg/Xorg (OsLookupColor+0x13c) [0x55d66e90159c] Mar 12 12:43:12 /usr/lib/gdm3/gdm-x-session[1949]: (EE) 1: /lib/x86_64-linux-gnu/libpthread.so.0 (funlockfile+0x60) [0x7f5f95cc941f] Mar 12 12:43:12 /usr/lib/gdm3/gdm-x-session[1949]: (EE) 2: /lib/x86_64-linux-gnu/libc.so.6 (gsignal+0xcb) [0x7f5f95b0618b] Mar 12 12:43:12 /usr/lib/gdm3/gdm-x-session[1949]: (EE) 3: /lib/x86_64-linux-gnu/libc.so.6 (abort+0x12b) [0x7f5f95ae5859] Mar 12 12:43:12 /usr/lib/gdm3/gdm-x-session[1949]: (EE) unw_get_proc_name failed: no unwind info found [-10] Mar 12 12:43:12 /usr/lib/gdm3/gdm-x-session[1949]: (EE) 4: /usr/lib/x86_64-linux-gnu/dri/iris_dri.so (?+0x0) [0x7f5f939fd665] Mar 12 12:43:12 /usr/lib/gdm3/gdm-x-session[1949]: (EE) 5: /usr/lib/x86_64-linux-gnu/dri/iris_dri.so (nouveau_drm_screen_create+0x29a098) [0x7f5f948c5d08] Mar 12 12:43:12 /usr/lib/gdm3/gdm-x-session[1949]: (EE) 6: /usr/lib/x86_64-linux-gnu/dri/iris_dri.so (__driDriverGetExtensions_zink+0x7cf0d) [0x7f5f93b0214d] Mar 12 12:43:12 /usr/lib/gdm3/gdm-x-session[1949]: (EE) 7: /usr/lib/xorg/Xorg (present_register_complete_notify+0x673) [0x55d66e87dcf3] Mar 12 12:43:12 /usr/lib/gdm3/gdm-x-session[1949]: (EE) 8: /usr/lib/xorg/Xorg (present_register_complete_notify+0x1fd9) [0x55d66e880ee9] Mar 12 12:43:12 /usr/lib/gdm3/gdm-x-session[1949]: (EE) 9: /usr/lib/xorg/Xorg (present_register_complete_notify+0x809) [0x55d66e87e069] Mar 12 12:43:12 /usr/lib/gdm3/gdm-x-session[1949]: (EE) 10: /usr/lib/xorg/Xorg (present_register_complete_notify+0x845) [0x55d66e87e105] Mar 12 12:43:12 /usr/lib/gdm3/gdm-x-session[1949]: (EE) 11: /usr/lib/xorg/Xorg (TimerSet+0x180) [0x55d66e8fabd0] Mar 12 12:43:12 /usr/lib/gdm3/gdm-x-session[1949]: (EE) 12: /usr/lib/xorg/Xorg (TimerSet+0x1e8) [0x55d66e8fac88] Mar 12 12:43:12 /usr/lib/gdm3/gdm-x-session[1949]: (EE) 13: /usr/lib/xorg/Xorg (WaitForSomething+0x235) [0x55d66e8fad25] Mar 12 12:43:12 /usr/lib/gdm3/gdm-x-session[1949]: (EE) 14: /usr/lib/xorg/Xorg (SendErrorToClient+0x117) [0x55d66e79fcf7] Mar 12 12:43:12 /usr/lib/gdm3/gdm-x-session[1949]: (EE) 15: /usr/lib/xorg/Xorg (InitFonts+0x3b4) [0x55d66e7a3fc4] Mar 12 12:43:12 /usr/lib/gdm3/gdm-x-session[1949]: (EE) 16: /lib/x86_64-linux-gnu/libc.so.6 (__libc_start_main+0xf3) [0x7f5f95ae70b3] Mar 12 12:43:12 /usr/lib/gdm3/gdm-x-session[1949]: (EE) 17: /usr/lib/xorg/Xorg (_start+0x2e) [0x55d66e78da2e] Mar 12 12:43:12 /usr/lib/gdm3/gdm-x-session[1949]: (EE) Mar 12 12:43:12 /usr/lib/gdm3/gdm-x-session[1949]: (EE) Mar 12 12:43:12 /usr/lib/gdm3/gdm-x-session[1949]: Fatal server error: Mar 12 12:43:12 /usr/lib/gdm3/gdm-x-session[1949]: (EE) Caught signal 6 (Aborted). Server aborting The detail log is in lp:1917692. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1918855 Title: Xorg xserver got signal 6 to abort Status in OEM Priority Project: New Status in mesa package in Ubuntu: New Bug description: I run checkbox job com.canonical.certification::memory/memory_stress_ng on focal, and the xserver stops unexpectedly with the following stacktrace: /usr/lib/gdm3/gdm-x-session[1425]: (EE) 0: /usr/lib/xorg/Xorg (OsLookupColor+0x13c) [0x5619f3a4d59c] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 1: /lib/x86_64-linux-gnu/libpthread.so.0 (funlockfile+0x60) [0x7fae4786741f] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 2: /lib/x86_64-linux-gnu/libc.so.6 (gsignal+0xcb) [0x7fae476a418b] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 3: /lib/x86_64-linux-gnu/libc.so.6 (abort+0x12b) [0x7fae47683859] /usr/lib/gdm3/gdm-x-session[1425]: (EE) unw_get_proc_name failed: no unwind info found [-10] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 4: /usr/lib/x86_64-linux-gnu/dri/iris_dri.so (?+0x0) [0x7fae457d7aec] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 5: /usr/lib/x86_64-linux-gnu/dri/iris_dri.so (nouveau_drm_screen_create+0x25c8ec) [0x7fae46529c9c] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 6: /usr/lib/x86_64-linux-gnu/dri/iris_dri.so (__driDriverGetExtensions_zink+0x2561d) [0x7fae4582c74d] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 7: /usr/lib/xorg/modules/libglamoregl.so (glamor_destroy_pixmap+0x150) [0x7fae47007480] /usr/lib/gdm3/gdm-x-session[1425]: (EE) unw_get_proc_name failed: no unwind info found [-10] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 8: /usr/lib/xorg/modules/drivers/modesetting_drv.so (?+0x0) [0x7fae47040a30] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 9: /usr/lib/xorg/Xorg (BlockHandler+0xa5) [0x5619f38f0995] /usr/l
[Desktop-packages] [Bug 1918738] Re: Regression: Onscreen Keyboard Backspace, Enter and Capitalize do not work
The workaround is to reinstall the older version of gjs: https://launchpad.net/ubuntu/+source/gjs/1.67.2-1/+build/21079029 ** Tags added: osk -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gjs in Ubuntu. https://bugs.launchpad.net/bugs/1918738 Title: Regression: Onscreen Keyboard Backspace, Enter and Capitalize do not work Status in gjs package in Ubuntu: In Progress Status in gnome-shell package in Ubuntu: Triaged Bug description: Title pretty much says it all: I'm testing Ubuntu Hirsute (21.04), fully upgraded as of today (Gnome-shell 3.38.3) and the osk keys for Backspace, Enter and Capitalize as well as for collapsing the keyboard do not work. Pressing them just does nothing. Related logs in jouralctl output: _press@resource:///org/gnome/shell/ui/keyboard.js:337:39 _makeKey/<@resource:///org/gnome/shell/ui/keyboard.js:464:22 Mär 11 23:06:02 pc gnome-shell[15039]: JS ERROR: Error: Argument wc: value is out of range for uint32 _getKeyval@resource:///org/gnome/shell/ui/keyboard.js:330:24 _release@resource:///org/gnome/shell/ui/keyboard.js:370:36 _makeKey/<@resource:///org/gnome/shell/ui/keyboard.js:468:22 Mär 11 23:06:03 pc gnome-shell[15039]: JS ERROR: Error: Argument wc: value is out of range for uint32 _getKeyval@resource:///org/gnome/shell/ui/keyboard.js:330:24 _press@resource:///org/gnome/shell/ui/keyboard.js:337:39 _makeKey/<@resource:///org/gnome/shell/ui/keyboard.js:464:22 Mär 11 23:06:03 pc gnome-shell[15039]: JS ERROR: Error: Argument wc: value is out of range for uint32 _getKeyval@resource:///org/gnome/shell/ui/keyboard.js:330:24 _release@resource:///org/gnome/shell/ui/keyboard.js:370:36 _makeKey/<@resource:///org/gnome/shell/ui/keyboard.js:468:22 Mär 11 23:06:04 pc gnome-shell[15039]: JS ERROR: Error: Argument wc: value is out of range for uint32 _getKeyval@resource:///org/gnome/shell/ui/keyboard.js:330:24 _press@resource:///org/gnome/shell/ui/keyboard.js:337:39 _makeKey/<@resource:///org/gnome/shell/ui/keyboard.js:464:22 Mär 11 23:06:04 pc gnome-shell[15039]: JS ERROR: Error: Argument wc: value is out of range for uint32 _getKeyval@resource:///org/gnome/shell/ui/keyboard.js:330:24 _release@resource:///org/gnome/shell/ui/keyboard.js:370:36 _makeKey/<@resource:///org/gnome/shell/ui/keyboard.js:468:22 Mär 11 23:06:04 pc gnome-shell[15039]: JS ERROR: Error: Argument wc: value is out of range for uint32 _getKeyval@resource:///org/gnome/shell/ui/keyboard.js:330:24 _press@resource:///org/gnome/shell/ui/keyboard.js:337:39 _makeKey/<@resource:///org/gnome/shell/ui/keyboard.js:464:22 Mär 11 23:06:04 pc gnome-shell[15039]: JS ERROR: Error: Argument wc: value is out of range for uint32 _getKeyval@resource:///org/gnome/shell/ui/keyboard.js:330:24 _release@resource:///org/gnome/shell/ui/keyboard.js:370:36 _makeKey/<@resource:///org/gnome/shell/ui/keyboard.js:468:22 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gjs/+bug/1918738/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1873411] Re: steam installs generic Desktop icons for games that require an explicit 'Allow Launching'
[Expired for gnome-shell-extension-desktop-icons (Ubuntu) because there has been no activity for 60 days.] ** Changed in: gnome-shell-extension-desktop-icons (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-desktop-icons in Ubuntu. https://bugs.launchpad.net/bugs/1873411 Title: steam installs generic Desktop icons for games that require an explicit 'Allow Launching' Status in gnome-shell-extension-desktop-icons package in Ubuntu: Expired Bug description: The 1.0.0.61-2ubuntu3 steam package installs a steam which creates generic icons on the Desktop for games. These Desktop game icons open in gedit rather than launching when double clicked. One has to explicitly right-click on the icon and select 'Allow Launching' for the Desktop icons that steam creates upon game installation to become usable for launching. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-desktop-icons/+bug/1873411/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1905287] Re: Phantom mouse wheel events without user input
[Expired for libinput (Ubuntu) because there has been no activity for 60 days.] ** Changed in: libinput (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1905287 Title: Phantom mouse wheel events without user input Status in libinput package in Ubuntu: Expired Status in linux package in Ubuntu: Expired Status in mutter package in Ubuntu: Expired Bug description: This doesn't occur with Firefox. But it occurs with Chrome AND gnome- terminal. What happens is that if I have more than one tab in focus, it moves to the last tabs by itself. Here is a screen capture of what happens. I am running ubuntu 18.04.5 LTS, i have never had this issue before. Issue started happening since yesterday. This morning I applied my updates hoping that this will fix it, but even then nothing happened. I have known this to happen in another older laptop running an older version of ubuntu as well. journalctl -f gives me ths following: ``` Nov 23 15:28:36 xxxmymachinenamexxx gnome-shell[4051]: pushModal: invocation of begin_modal failed ``` Note that this error entry from the journalctl does not always appear when the tabs cycle through like in the video, might be unrelated. My graphics card is: lspci |grep VGA ``` 00:02.0 VGA compatible controller: Intel Corporation HD Graphics 530 (rev 06) ``` I thought initially it might be some key that is being pressed, so i ran screenkey when this happens, there was no key appearing, so it does not seem that this is a key being pressed. I tail -f /var/log/syslog and /var/log/Xorg.0.log when i click on the tabs and it does this weirdness, nothing happens. So i don't have much information to give on this issue. Please get in touch with me if you want any information. I cannot push all my logs since it is a professional laptop. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libinput/+bug/1905287/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1905287] Re: Phantom mouse wheel events without user input
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1905287 Title: Phantom mouse wheel events without user input Status in libinput package in Ubuntu: Expired Status in linux package in Ubuntu: Expired Status in mutter package in Ubuntu: Expired Bug description: This doesn't occur with Firefox. But it occurs with Chrome AND gnome- terminal. What happens is that if I have more than one tab in focus, it moves to the last tabs by itself. Here is a screen capture of what happens. I am running ubuntu 18.04.5 LTS, i have never had this issue before. Issue started happening since yesterday. This morning I applied my updates hoping that this will fix it, but even then nothing happened. I have known this to happen in another older laptop running an older version of ubuntu as well. journalctl -f gives me ths following: ``` Nov 23 15:28:36 xxxmymachinenamexxx gnome-shell[4051]: pushModal: invocation of begin_modal failed ``` Note that this error entry from the journalctl does not always appear when the tabs cycle through like in the video, might be unrelated. My graphics card is: lspci |grep VGA ``` 00:02.0 VGA compatible controller: Intel Corporation HD Graphics 530 (rev 06) ``` I thought initially it might be some key that is being pressed, so i ran screenkey when this happens, there was no key appearing, so it does not seem that this is a key being pressed. I tail -f /var/log/syslog and /var/log/Xorg.0.log when i click on the tabs and it does this weirdness, nothing happens. So i don't have much information to give on this issue. Please get in touch with me if you want any information. I cannot push all my logs since it is a professional laptop. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libinput/+bug/1905287/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1905287] Re: Phantom mouse wheel events without user input
[Expired for mutter (Ubuntu) because there has been no activity for 60 days.] ** Changed in: mutter (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1905287 Title: Phantom mouse wheel events without user input Status in libinput package in Ubuntu: Expired Status in linux package in Ubuntu: Expired Status in mutter package in Ubuntu: Expired Bug description: This doesn't occur with Firefox. But it occurs with Chrome AND gnome- terminal. What happens is that if I have more than one tab in focus, it moves to the last tabs by itself. Here is a screen capture of what happens. I am running ubuntu 18.04.5 LTS, i have never had this issue before. Issue started happening since yesterday. This morning I applied my updates hoping that this will fix it, but even then nothing happened. I have known this to happen in another older laptop running an older version of ubuntu as well. journalctl -f gives me ths following: ``` Nov 23 15:28:36 xxxmymachinenamexxx gnome-shell[4051]: pushModal: invocation of begin_modal failed ``` Note that this error entry from the journalctl does not always appear when the tabs cycle through like in the video, might be unrelated. My graphics card is: lspci |grep VGA ``` 00:02.0 VGA compatible controller: Intel Corporation HD Graphics 530 (rev 06) ``` I thought initially it might be some key that is being pressed, so i ran screenkey when this happens, there was no key appearing, so it does not seem that this is a key being pressed. I tail -f /var/log/syslog and /var/log/Xorg.0.log when i click on the tabs and it does this weirdness, nothing happens. So i don't have much information to give on this issue. Please get in touch with me if you want any information. I cannot push all my logs since it is a professional laptop. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libinput/+bug/1905287/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1918666] Re: Cannot close the modal "Connect to Wifi" window to return to desktop
Since these bugs are going to keep occuring in different places, and the eventual fixes for gnome-shell for each will be different, I have separated out bug 1918738 again. The short term fix for hirsute should still be https://salsa.debian.org /gnome-team/gjs/-/merge_requests/17 ** Summary changed: - Shell regressions in gjs 1.67.2-2 starting with "JS ERROR: Error: Argument : value is out of range for uint32" + Cannot close the modal "Connect to Wifi" window to return to desktop ** Also affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Changed in: gnome-shell (Ubuntu) Importance: Undecided => Critical ** Changed in: gnome-shell (Ubuntu) Status: New => Triaged -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gjs in Ubuntu. https://bugs.launchpad.net/bugs/1918666 Title: Cannot close the modal "Connect to Wifi" window to return to desktop Status in gjs package in Ubuntu: In Progress Status in gnome-shell package in Ubuntu: Triaged Bug description: When I select the task bar menu, click on the Wifi and select "Select to network", a modal window appears that allows me to select a Wifi network. After I have clicked on one of the networks, normally, when I click Cancel or Connect, the modal window disappears and returns me to the desktop. With the current gnome-shell, this modal window persists and I cannot access the desktop - this is both in Wayland and in X. Connect doesn't seem to work - it's like the buttons are no longer accepting clicks. The ESC key also doesn't do anything. (If I don't click on a network, the ESC key does work, and so does Cancel.) I think I once managed to get Alt-Ctrl-F1 to bring back the GDM login window, but the modal window was still there when I went back into the desktop. Alt-F2 didn't work so I couldn't try re-starting gnome-shell. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: gnome-shell 3.38.3-3ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-11.12-generic 5.11.0 Uname: Linux 5.11.0-11-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu60 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Thu Mar 11 20:35:24 2021 DisplayManager: gdm3 RelatedPackageVersions: mutter-common 3.38.3-3ubuntu2 SourcePackage: gnome-shell UpgradeStatus: Upgraded to hirsute on 2021-02-24 (15 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gjs/+bug/1918666/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1918738] Re: Regression: Onscreen Keyboard Backspace, Enter and Capitalize do not work
Fix proposed: https://salsa.debian.org/gnome- team/gjs/-/merge_requests/17 ** This bug is no longer a duplicate of bug 1918666 Cannot close the modal "Connect to Wifi" window to return to desktop ** Also affects: gjs (Ubuntu) Importance: Undecided Status: New ** Changed in: gjs (Ubuntu) Assignee: (unassigned) => Daniel van Vugt (vanvugt) ** Changed in: gjs (Ubuntu) Importance: Undecided => High ** Changed in: gjs (Ubuntu) Status: New => In Progress ** Changed in: gnome-shell (Ubuntu) Status: New => Triaged ** Tags added: regression-release -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1918738 Title: Regression: Onscreen Keyboard Backspace, Enter and Capitalize do not work Status in gjs package in Ubuntu: In Progress Status in gnome-shell package in Ubuntu: Triaged Bug description: Title pretty much says it all: I'm testing Ubuntu Hirsute (21.04), fully upgraded as of today (Gnome-shell 3.38.3) and the osk keys for Backspace, Enter and Capitalize as well as for collapsing the keyboard do not work. Pressing them just does nothing. Related logs in jouralctl output: _press@resource:///org/gnome/shell/ui/keyboard.js:337:39 _makeKey/<@resource:///org/gnome/shell/ui/keyboard.js:464:22 Mär 11 23:06:02 pc gnome-shell[15039]: JS ERROR: Error: Argument wc: value is out of range for uint32 _getKeyval@resource:///org/gnome/shell/ui/keyboard.js:330:24 _release@resource:///org/gnome/shell/ui/keyboard.js:370:36 _makeKey/<@resource:///org/gnome/shell/ui/keyboard.js:468:22 Mär 11 23:06:03 pc gnome-shell[15039]: JS ERROR: Error: Argument wc: value is out of range for uint32 _getKeyval@resource:///org/gnome/shell/ui/keyboard.js:330:24 _press@resource:///org/gnome/shell/ui/keyboard.js:337:39 _makeKey/<@resource:///org/gnome/shell/ui/keyboard.js:464:22 Mär 11 23:06:03 pc gnome-shell[15039]: JS ERROR: Error: Argument wc: value is out of range for uint32 _getKeyval@resource:///org/gnome/shell/ui/keyboard.js:330:24 _release@resource:///org/gnome/shell/ui/keyboard.js:370:36 _makeKey/<@resource:///org/gnome/shell/ui/keyboard.js:468:22 Mär 11 23:06:04 pc gnome-shell[15039]: JS ERROR: Error: Argument wc: value is out of range for uint32 _getKeyval@resource:///org/gnome/shell/ui/keyboard.js:330:24 _press@resource:///org/gnome/shell/ui/keyboard.js:337:39 _makeKey/<@resource:///org/gnome/shell/ui/keyboard.js:464:22 Mär 11 23:06:04 pc gnome-shell[15039]: JS ERROR: Error: Argument wc: value is out of range for uint32 _getKeyval@resource:///org/gnome/shell/ui/keyboard.js:330:24 _release@resource:///org/gnome/shell/ui/keyboard.js:370:36 _makeKey/<@resource:///org/gnome/shell/ui/keyboard.js:468:22 Mär 11 23:06:04 pc gnome-shell[15039]: JS ERROR: Error: Argument wc: value is out of range for uint32 _getKeyval@resource:///org/gnome/shell/ui/keyboard.js:330:24 _press@resource:///org/gnome/shell/ui/keyboard.js:337:39 _makeKey/<@resource:///org/gnome/shell/ui/keyboard.js:464:22 Mär 11 23:06:04 pc gnome-shell[15039]: JS ERROR: Error: Argument wc: value is out of range for uint32 _getKeyval@resource:///org/gnome/shell/ui/keyboard.js:330:24 _release@resource:///org/gnome/shell/ui/keyboard.js:370:36 _makeKey/<@resource:///org/gnome/shell/ui/keyboard.js:468:22 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gjs/+bug/1918738/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1918666] Re: Shell regressions in gjs 1.67.2-2 starting with "JS ERROR: Error: Argument : value is out of range for uint32"
Also the offending change in gjs 1.67.2-2 is a feature, not a bug fix. So it probably shouldn't have happened at all after feature freeze. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gjs in Ubuntu. https://bugs.launchpad.net/bugs/1918666 Title: Shell regressions in gjs 1.67.2-2 starting with "JS ERROR: Error: Argument : value is out of range for uint32" Status in gjs package in Ubuntu: In Progress Bug description: When I select the task bar menu, click on the Wifi and select "Select to network", a modal window appears that allows me to select a Wifi network. After I have clicked on one of the networks, normally, when I click Cancel or Connect, the modal window disappears and returns me to the desktop. With the current gnome-shell, this modal window persists and I cannot access the desktop - this is both in Wayland and in X. Connect doesn't seem to work - it's like the buttons are no longer accepting clicks. The ESC key also doesn't do anything. (If I don't click on a network, the ESC key does work, and so does Cancel.) I think I once managed to get Alt-Ctrl-F1 to bring back the GDM login window, but the modal window was still there when I went back into the desktop. Alt-F2 didn't work so I couldn't try re-starting gnome-shell. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: gnome-shell 3.38.3-3ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-11.12-generic 5.11.0 Uname: Linux 5.11.0-11-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu60 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Thu Mar 11 20:35:24 2021 DisplayManager: gdm3 RelatedPackageVersions: mutter-common 3.38.3-3ubuntu2 SourcePackage: gnome-shell UpgradeStatus: Upgraded to hirsute on 2021-02-24 (15 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gjs/+bug/1918666/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1918666] Re: Shell regressions in gjs 1.67.2-2 starting with "JS ERROR: Error: Argument : value is out of range for uint32"
Fixed: https://salsa.debian.org/gnome-team/gjs/-/merge_requests/17 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gjs in Ubuntu. https://bugs.launchpad.net/bugs/1918666 Title: Shell regressions in gjs 1.67.2-2 starting with "JS ERROR: Error: Argument : value is out of range for uint32" Status in gjs package in Ubuntu: In Progress Bug description: When I select the task bar menu, click on the Wifi and select "Select to network", a modal window appears that allows me to select a Wifi network. After I have clicked on one of the networks, normally, when I click Cancel or Connect, the modal window disappears and returns me to the desktop. With the current gnome-shell, this modal window persists and I cannot access the desktop - this is both in Wayland and in X. Connect doesn't seem to work - it's like the buttons are no longer accepting clicks. The ESC key also doesn't do anything. (If I don't click on a network, the ESC key does work, and so does Cancel.) I think I once managed to get Alt-Ctrl-F1 to bring back the GDM login window, but the modal window was still there when I went back into the desktop. Alt-F2 didn't work so I couldn't try re-starting gnome-shell. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: gnome-shell 3.38.3-3ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-11.12-generic 5.11.0 Uname: Linux 5.11.0-11-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu60 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Thu Mar 11 20:35:24 2021 DisplayManager: gdm3 RelatedPackageVersions: mutter-common 3.38.3-3ubuntu2 SourcePackage: gnome-shell UpgradeStatus: Upgraded to hirsute on 2021-02-24 (15 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gjs/+bug/1918666/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1918666] Re: Shell regressions in gjs 1.67.2-2 starting with "JS ERROR: Error: Argument : value is out of range for uint32"
The associated fixes for gnome-shell should be proposed upstream for GNOME 40/41. ** Also affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Changed in: gnome-shell (Ubuntu) Importance: Undecided => Critical ** Changed in: gnome-shell (Ubuntu) Status: New => Triaged ** No longer affects: gnome-shell (Ubuntu) ** Changed in: gjs (Ubuntu) Assignee: Marco Trevisan (Treviño) (3v1n0) => Daniel van Vugt (vanvugt) ** Changed in: gjs (Ubuntu) Status: Triaged => In Progress -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gjs in Ubuntu. https://bugs.launchpad.net/bugs/1918666 Title: Shell regressions in gjs 1.67.2-2 starting with "JS ERROR: Error: Argument : value is out of range for uint32" Status in gjs package in Ubuntu: In Progress Bug description: When I select the task bar menu, click on the Wifi and select "Select to network", a modal window appears that allows me to select a Wifi network. After I have clicked on one of the networks, normally, when I click Cancel or Connect, the modal window disappears and returns me to the desktop. With the current gnome-shell, this modal window persists and I cannot access the desktop - this is both in Wayland and in X. Connect doesn't seem to work - it's like the buttons are no longer accepting clicks. The ESC key also doesn't do anything. (If I don't click on a network, the ESC key does work, and so does Cancel.) I think I once managed to get Alt-Ctrl-F1 to bring back the GDM login window, but the modal window was still there when I went back into the desktop. Alt-F2 didn't work so I couldn't try re-starting gnome-shell. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: gnome-shell 3.38.3-3ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-11.12-generic 5.11.0 Uname: Linux 5.11.0-11-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu60 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Thu Mar 11 20:35:24 2021 DisplayManager: gdm3 RelatedPackageVersions: mutter-common 3.38.3-3ubuntu2 SourcePackage: gnome-shell UpgradeStatus: Upgraded to hirsute on 2021-02-24 (15 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gjs/+bug/1918666/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1918666] Re: Shell regressions in gjs 1.67.2-2 starting with "JS ERROR: Error: Argument : value is out of range for uint32"
The same change also landed in gjs upstream an hour ago: https://gitlab.gnome.org/GNOME/gjs/-/merge_requests/583 For hirsute however we should probably revert it. Because we're going to keep finding places in gnome-shell that now fail with the error checking for some time to come. And while that happens, random parts of the shell will break. So the new error checking is not something we should introduce right now at the end of the cycle. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gjs in Ubuntu. https://bugs.launchpad.net/bugs/1918666 Title: Shell regressions in gjs 1.67.2-2 starting with "JS ERROR: Error: Argument : value is out of range for uint32" Status in gjs package in Ubuntu: Triaged Bug description: When I select the task bar menu, click on the Wifi and select "Select to network", a modal window appears that allows me to select a Wifi network. After I have clicked on one of the networks, normally, when I click Cancel or Connect, the modal window disappears and returns me to the desktop. With the current gnome-shell, this modal window persists and I cannot access the desktop - this is both in Wayland and in X. Connect doesn't seem to work - it's like the buttons are no longer accepting clicks. The ESC key also doesn't do anything. (If I don't click on a network, the ESC key does work, and so does Cancel.) I think I once managed to get Alt-Ctrl-F1 to bring back the GDM login window, but the modal window was still there when I went back into the desktop. Alt-F2 didn't work so I couldn't try re-starting gnome-shell. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: gnome-shell 3.38.3-3ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-11.12-generic 5.11.0 Uname: Linux 5.11.0-11-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu60 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Thu Mar 11 20:35:24 2021 DisplayManager: gdm3 RelatedPackageVersions: mutter-common 3.38.3-3ubuntu2 SourcePackage: gnome-shell UpgradeStatus: Upgraded to hirsute on 2021-02-24 (15 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gjs/+bug/1918666/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1918855] Re: Xorg xserver got signal 6 to abort
I follow the upstream bug to install obiaf ppa's mesa lib and run the test for two times, then I can get pass successfully for both run. I plan to run the test three times to make sure the edge mesa lib can really solve the problem, because the issue seems happens randomly. ** Description changed: I run checkbox job com.canonical.certification::memory/memory_stress_ng on focal, and the xserver stops unexpectedly with the following stacktrace: /usr/lib/gdm3/gdm-x-session[1425]: (EE) 0: /usr/lib/xorg/Xorg (OsLookupColor+0x13c) [0x5619f3a4d59c] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 1: /lib/x86_64-linux-gnu/libpthread.so.0 (funlockfile+0x60) [0x7fae4786741f] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 2: /lib/x86_64-linux-gnu/libc.so.6 (gsignal+0xcb) [0x7fae476a418b] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 3: /lib/x86_64-linux-gnu/libc.so.6 (abort+0x12b) [0x7fae47683859] /usr/lib/gdm3/gdm-x-session[1425]: (EE) unw_get_proc_name failed: no unwind info found [-10] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 4: /usr/lib/x86_64-linux-gnu/dri/iris_dri.so (?+0x0) [0x7fae457d7aec] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 5: /usr/lib/x86_64-linux-gnu/dri/iris_dri.so (nouveau_drm_screen_create+0x25c8ec) [0x7fae46529c9c] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 6: /usr/lib/x86_64-linux-gnu/dri/iris_dri.so (__driDriverGetExtensions_zink+0x2561d) [0x7fae4582c74d] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 7: /usr/lib/xorg/modules/libglamoregl.so (glamor_destroy_pixmap+0x150) [0x7fae47007480] /usr/lib/gdm3/gdm-x-session[1425]: (EE) unw_get_proc_name failed: no unwind info found [-10] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 8: /usr/lib/xorg/modules/drivers/modesetting_drv.so (?+0x0) [0x7fae47040a30] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 9: /usr/lib/xorg/Xorg (BlockHandler+0xa5) [0x5619f38f0995] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 10: /usr/lib/xorg/Xorg (WaitForSomething+0x122) [0x5619f3a46c12] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 11: /usr/lib/xorg/Xorg (SendErrorToClient+0x117) [0x5619f38ebcf7] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 12: /usr/lib/xorg/Xorg (InitFonts+0x3b4) [0x5619f38effc4] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 13: /lib/x86_64-linux-gnu/libc.so.6 (__libc_start_main+0xf3) [0x7fae476850b3] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 14: /usr/lib/xorg/Xorg (_start+0x2e) [0x5619f38d9a2e] More info: - I searched the Internet and got a bug with similar issue: + I searched the Internet and got a bug with the same stacktrace: https://gitlab.freedesktop.org/mesa/mesa/-/issues/3468 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1918855 Title: Xorg xserver got signal 6 to abort Status in OEM Priority Project: New Status in mesa package in Ubuntu: New Bug description: I run checkbox job com.canonical.certification::memory/memory_stress_ng on focal, and the xserver stops unexpectedly with the following stacktrace: /usr/lib/gdm3/gdm-x-session[1425]: (EE) 0: /usr/lib/xorg/Xorg (OsLookupColor+0x13c) [0x5619f3a4d59c] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 1: /lib/x86_64-linux-gnu/libpthread.so.0 (funlockfile+0x60) [0x7fae4786741f] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 2: /lib/x86_64-linux-gnu/libc.so.6 (gsignal+0xcb) [0x7fae476a418b] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 3: /lib/x86_64-linux-gnu/libc.so.6 (abort+0x12b) [0x7fae47683859] /usr/lib/gdm3/gdm-x-session[1425]: (EE) unw_get_proc_name failed: no unwind info found [-10] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 4: /usr/lib/x86_64-linux-gnu/dri/iris_dri.so (?+0x0) [0x7fae457d7aec] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 5: /usr/lib/x86_64-linux-gnu/dri/iris_dri.so (nouveau_drm_screen_create+0x25c8ec) [0x7fae46529c9c] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 6: /usr/lib/x86_64-linux-gnu/dri/iris_dri.so (__driDriverGetExtensions_zink+0x2561d) [0x7fae4582c74d] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 7: /usr/lib/xorg/modules/libglamoregl.so (glamor_destroy_pixmap+0x150) [0x7fae47007480] /usr/lib/gdm3/gdm-x-session[1425]: (EE) unw_get_proc_name failed: no unwind info found [-10] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 8: /usr/lib/xorg/modules/drivers/modesetting_drv.so (?+0x0) [0x7fae47040a30] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 9: /usr/lib/xorg/Xorg (BlockHandler+0xa5) [0x5619f38f0995] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 10: /usr/lib/xorg/Xorg (WaitForSomething+0x122) [0x5619f3a46c12] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 11: /usr/lib/xorg/Xorg (SendErrorToClient+0x117) [0x5619f38ebcf7] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 12: /usr/lib/xorg/Xorg (InitFonts+0x3b4) [0x5619f38effc4] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 13: /lib/x86_64-linux-gnu/libc.so.6 (__libc_start_main+0xf3) [0x7fae476850b3] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 14: /usr/lib/xorg/Xorg (_start+0x2e) [0x5619f38d9a2e] More info: I searched
[Desktop-packages] [Bug 1918855] [NEW] Xorg xserver got signal 6 to abort
Public bug reported: I run checkbox job com.canonical.certification::memory/memory_stress_ng on focal, and the xserver stops unexpectedly with the following stacktrace: /usr/lib/gdm3/gdm-x-session[1425]: (EE) 0: /usr/lib/xorg/Xorg (OsLookupColor+0x13c) [0x5619f3a4d59c] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 1: /lib/x86_64-linux-gnu/libpthread.so.0 (funlockfile+0x60) [0x7fae4786741f] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 2: /lib/x86_64-linux-gnu/libc.so.6 (gsignal+0xcb) [0x7fae476a418b] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 3: /lib/x86_64-linux-gnu/libc.so.6 (abort+0x12b) [0x7fae47683859] /usr/lib/gdm3/gdm-x-session[1425]: (EE) unw_get_proc_name failed: no unwind info found [-10] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 4: /usr/lib/x86_64-linux-gnu/dri/iris_dri.so (?+0x0) [0x7fae457d7aec] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 5: /usr/lib/x86_64-linux-gnu/dri/iris_dri.so (nouveau_drm_screen_create+0x25c8ec) [0x7fae46529c9c] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 6: /usr/lib/x86_64-linux-gnu/dri/iris_dri.so (__driDriverGetExtensions_zink+0x2561d) [0x7fae4582c74d] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 7: /usr/lib/xorg/modules/libglamoregl.so (glamor_destroy_pixmap+0x150) [0x7fae47007480] /usr/lib/gdm3/gdm-x-session[1425]: (EE) unw_get_proc_name failed: no unwind info found [-10] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 8: /usr/lib/xorg/modules/drivers/modesetting_drv.so (?+0x0) [0x7fae47040a30] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 9: /usr/lib/xorg/Xorg (BlockHandler+0xa5) [0x5619f38f0995] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 10: /usr/lib/xorg/Xorg (WaitForSomething+0x122) [0x5619f3a46c12] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 11: /usr/lib/xorg/Xorg (SendErrorToClient+0x117) [0x5619f38ebcf7] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 12: /usr/lib/xorg/Xorg (InitFonts+0x3b4) [0x5619f38effc4] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 13: /lib/x86_64-linux-gnu/libc.so.6 (__libc_start_main+0xf3) [0x7fae476850b3] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 14: /usr/lib/xorg/Xorg (_start+0x2e) [0x5619f38d9a2e] More info: I searched the Internet and got a bug with the same stacktrace: https://gitlab.freedesktop.org/mesa/mesa/-/issues/3468 ** Affects: oem-priority Importance: Undecided Status: New ** Affects: mesa (Ubuntu) Importance: Undecided Status: New ** Tags: oem-priority originate-from-1917692 somerville ** Tags added: oem-priority originate-from-1917692 somerville ** Description changed: - I run checkbox job com.canonical.certification::memory/memory_stress_ng, - and the xserver stops unexpectedly with the following stacktrace: + I run checkbox job com.canonical.certification::memory/memory_stress_ng + on focal, and the xserver stops unexpectedly with the following + stacktrace: /usr/lib/gdm3/gdm-x-session[1425]: (EE) 0: /usr/lib/xorg/Xorg (OsLookupColor+0x13c) [0x5619f3a4d59c] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 1: /lib/x86_64-linux-gnu/libpthread.so.0 (funlockfile+0x60) [0x7fae4786741f] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 2: /lib/x86_64-linux-gnu/libc.so.6 (gsignal+0xcb) [0x7fae476a418b] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 3: /lib/x86_64-linux-gnu/libc.so.6 (abort+0x12b) [0x7fae47683859] /usr/lib/gdm3/gdm-x-session[1425]: (EE) unw_get_proc_name failed: no unwind info found [-10] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 4: /usr/lib/x86_64-linux-gnu/dri/iris_dri.so (?+0x0) [0x7fae457d7aec] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 5: /usr/lib/x86_64-linux-gnu/dri/iris_dri.so (nouveau_drm_screen_create+0x25c8ec) [0x7fae46529c9c] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 6: /usr/lib/x86_64-linux-gnu/dri/iris_dri.so (__driDriverGetExtensions_zink+0x2561d) [0x7fae4582c74d] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 7: /usr/lib/xorg/modules/libglamoregl.so (glamor_destroy_pixmap+0x150) [0x7fae47007480] /usr/lib/gdm3/gdm-x-session[1425]: (EE) unw_get_proc_name failed: no unwind info found [-10] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 8: /usr/lib/xorg/modules/drivers/modesetting_drv.so (?+0x0) [0x7fae47040a30] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 9: /usr/lib/xorg/Xorg (BlockHandler+0xa5) [0x5619f38f0995] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 10: /usr/lib/xorg/Xorg (WaitForSomething+0x122) [0x5619f3a46c12] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 11: /usr/lib/xorg/Xorg (SendErrorToClient+0x117) [0x5619f38ebcf7] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 12: /usr/lib/xorg/Xorg (InitFonts+0x3b4) [0x5619f38effc4] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 13: /lib/x86_64-linux-gnu/libc.so.6 (__libc_start_main+0xf3) [0x7fae476850b3] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 14: /usr/lib/xorg/Xorg (_start+0x2e) [0x5619f38d9a2e] More info: I searched the Internet and got a bug with similar issue: https://gitlab.freedesktop.org/mesa/mesa/-/issues/3468 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.
[Desktop-packages] [Bug 1918852] Re: menu list more pages tham exist
*** This bug is a duplicate of bug 1889102 *** https://bugs.launchpad.net/bugs/1889102 Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 1889102, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find. ** This bug has been marked a duplicate of bug 1889102 [ubuntu-dock] App grid has too many page dots on right -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1918852 Title: menu list more pages tham exist Status in xorg package in Ubuntu: New Bug description: List marks of menu show more tham have ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-66.74-generic 5.4.86 Uname: Linux 5.4.0-66-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 BootLog: Error: [Errno 13] Permissão negada: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Mar 11 23:22:13 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: virtualbox, 6.1.16, 5.4.0-65-generic, x86_64: installed virtualbox, 6.1.16, 5.4.0-66-generic, x86_64: installed ExtraDebuggingInterest: I just need to know a workaround GraphicsCard: Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company HD Graphics 620 [103c:831e] InstallationDate: Installed on 2020-01-16 (420 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0bda:b006 Realtek Semiconductor Corp. Bluetooth Radio Bus 001 Device 002: ID 1bcf:2c9b Sunplus Innovation Technology Inc. HP TrueVision HD Camera Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP 246 G6 Notebook PC ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-66-generic root=UUID=5bf2ac1a-8132-4552-9a85-3223b6e84d64 ro quiet splash pcie_aspm=off vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/10/2017 dmi.bios.vendor: Insyde dmi.bios.version: F.10 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 831E dmi.board.vendor: HP dmi.board.version: 17.30 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.10:bd05/10/2017:svnHP:pnHP246G6NotebookPC:pvrType1ProductConfigId:rvnHP:rn831E:rvr17.30:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5336AN HP 200 dmi.product.name: HP 246 G6 Notebook PC dmi.product.sku: 2NE40LA#AC4 dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.2.6-0ubuntu0.20.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1918852/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1918852] Re: menu list more pages tham exist
** Attachment added: "Captura de tela de 2021-03-11 23-20-34.png" https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1918852/+attachment/5475971/+files/Captura%20de%20tela%20de%202021-03-11%2023-20-34.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1918852 Title: menu list more pages tham exist Status in xorg package in Ubuntu: New Bug description: List marks of menu show more tham have ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-66.74-generic 5.4.86 Uname: Linux 5.4.0-66-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 BootLog: Error: [Errno 13] Permissão negada: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Mar 11 23:22:13 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: virtualbox, 6.1.16, 5.4.0-65-generic, x86_64: installed virtualbox, 6.1.16, 5.4.0-66-generic, x86_64: installed ExtraDebuggingInterest: I just need to know a workaround GraphicsCard: Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company HD Graphics 620 [103c:831e] InstallationDate: Installed on 2020-01-16 (420 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0bda:b006 Realtek Semiconductor Corp. Bluetooth Radio Bus 001 Device 002: ID 1bcf:2c9b Sunplus Innovation Technology Inc. HP TrueVision HD Camera Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP 246 G6 Notebook PC ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-66-generic root=UUID=5bf2ac1a-8132-4552-9a85-3223b6e84d64 ro quiet splash pcie_aspm=off vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/10/2017 dmi.bios.vendor: Insyde dmi.bios.version: F.10 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 831E dmi.board.vendor: HP dmi.board.version: 17.30 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.10:bd05/10/2017:svnHP:pnHP246G6NotebookPC:pvrType1ProductConfigId:rvnHP:rn831E:rvr17.30:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5336AN HP 200 dmi.product.name: HP 246 G6 Notebook PC dmi.product.sku: 2NE40LA#AC4 dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.2.6-0ubuntu0.20.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1918852/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1918852] [NEW] menu list more pages tham exist
Public bug reported: List marks of menu show more tham have ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-66.74-generic 5.4.86 Uname: Linux 5.4.0-66-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 BootLog: Error: [Errno 13] Permissão negada: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Mar 11 23:22:13 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: virtualbox, 6.1.16, 5.4.0-65-generic, x86_64: installed virtualbox, 6.1.16, 5.4.0-66-generic, x86_64: installed ExtraDebuggingInterest: I just need to know a workaround GraphicsCard: Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company HD Graphics 620 [103c:831e] InstallationDate: Installed on 2020-01-16 (420 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0bda:b006 Realtek Semiconductor Corp. Bluetooth Radio Bus 001 Device 002: ID 1bcf:2c9b Sunplus Innovation Technology Inc. HP TrueVision HD Camera Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP 246 G6 Notebook PC ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-66-generic root=UUID=5bf2ac1a-8132-4552-9a85-3223b6e84d64 ro quiet splash pcie_aspm=off vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/10/2017 dmi.bios.vendor: Insyde dmi.bios.version: F.10 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 831E dmi.board.vendor: HP dmi.board.version: 17.30 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.10:bd05/10/2017:svnHP:pnHP246G6NotebookPC:pvrType1ProductConfigId:rvnHP:rn831E:rvr17.30:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5336AN HP 200 dmi.product.name: HP 246 G6 Notebook PC dmi.product.sku: 2NE40LA#AC4 dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.2.6-0ubuntu0.20.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ubuntu -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1918852 Title: menu list more pages tham exist Status in xorg package in Ubuntu: New Bug description: List marks of menu show more tham have ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-66.74-generic 5.4.86 Uname: Linux 5.4.0-66-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 BootLog: Error: [Errno 13] Permissão negada: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Mar 11 23:22:13 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: virtualbox, 6.1.16, 5.4.0-65-generic, x86_64: installed virtualbox, 6.1.16, 5.4.0-66-generic, x86_64: installed ExtraDebuggingInterest: I just need to know a workaround GraphicsCard: Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company HD Graphics 620 [103c:831e] InstallationDate: Installed on 2020-01-16 (420 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0bda:b006 Realtek Semiconductor Corp. Bluetooth Radio Bus 001 Device 002: ID 1bcf:2c9b Sunplus Innovation Technology Inc. HP TrueVision HD Camera Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP 246 G6 Notebook PC ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-66-generic root=UUID=5bf2ac1a-8132-4552-9a85-3223b6e84d64 ro quiet splash pcie_aspm=off vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/10/2017 dmi.bios.vendor: Insyde dmi.bios.version: F.10 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 831E dmi.board.vendor:
[Desktop-packages] [Bug 1918739] Re: Gnome-shell got stuck and produces a plethora of error log messages to syslog file
*** This bug is a duplicate of bug 1908429 *** https://bugs.launchpad.net/bugs/1908429 Thanks for the bug report. Since most bugs are caused by third party extensions, removing them from the equation is the first thing to try. Please uninstall or disable (via the Extensions app): 'compiz-alike-windows-eff...@hermes83.github.com' If the problem still happens after that then it would seem to be a duplicate of bug 1908429. I will mark it as such now. ** This bug has been marked a duplicate of bug 1908429 gnome-shell fills syslog: Attempting to run a JS callback during garbage collection. This is most likely caused by destroying a Clutter actor or GTK widget with ::destroy signal connected, or using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked. The offending callback was SourceFunc(). -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1918739 Title: Gnome-shell got stuck and produces a plethora of error log messages to syslog file Status in gnome-shell package in Ubuntu: New Bug description: This is the message in syslog file: мар 11 09:34:43 hpz gnome-shell[2689]: == Stack trace for context 0x5563584e4900 == мар 11 09:34:43 hpz gnome-shell[2689]: == Stack trace for context 0x5563584e4900 == мар 11 09:34:43 hpz gnome-shell[2689]: == Stack trace for context 0x5563584e4900 == мар 11 09:34:43 hpz gnome-shell[2689]: == Stack trace for context 0x5563584e4900 == мар 11 09:34:43 hpz gnome-shell[2689]: == Stack trace for context 0x5563584e4900 == мар 11 09:34:43 hpz gnome-shell[2689]: == Stack trace for context 0x5563584e4900 == мар 11 09:34:43 hpz gnome-shell[2689]: == Stack trace for context 0x5563584e4900 == мар 11 09:34:43 hpz gnome-shell[2689]: == Stack trace for context 0x5563584e4900 == мар 11 09:34:44 hpz gnome-shell[2689]: Attempting to run a JS callback during garbage collection. This is most likely caused by destroying a Clutter actor or GTK widget with ::destroy signal connected, or using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked. мар 11 09:34:44 hpz systemd-journald[377]: Suppressed 496051 messages from user@1000.service мар 11 09:34:44 hpz gnome-shell[2689]: The offending callback was SourceFunc(). мар 11 09:34:44 hpz gnome-shell[2689]: Attempting to run a JS callback during garbage collection. This is most likely caused by destroying a Clutter actor or GTK widget with ::destroy signal connected, or using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked. мар 11 09:34:44 hpz gnome-shell[2689]: The offending callback was SourceFunc(). мар 11 09:34:44 hpz gnome-shell[2689]: Attempting to run a JS callback during garbage collection. This is most likely caused by destroying a Clutter actor or GTK widget with ::destroy signal connected, or using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked. мар 11 09:34:44 hpz gnome-shell[2689]: The offending callback was SourceFunc(). мар 11 09:34:44 hpz gnome-shell[2689]: Attempting to run a JS callback during garbage collection. This is most likely caused by destroying a Clutter actor or GTK widget with ::destroy signal connected, or using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked. мар 11 09:34:44 hpz gnome-shell[2689]: The offending callback was SourceFunc(). мар 11 09:34:44 hpz gnome-shell[2689]: Attempting to run a JS callback during garbage collection. This is most likely caused by destroying a Clutter actor or GTK widget with ::destroy signal connected, or using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked. мар 11 09:34:44 hpz gnome-shell[2689]: The offending callback was SourceFunc(). мар 11 09:34:44 hpz gnome-shell[2689]: Attempting to run a JS callback during garbage collection. This is most likely caused by destroying a Clutter actor or GTK widget with ::destroy signal connected, or using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked. мар 11 09:34:44 hpz gnome-shell[2689]: The offending callback was SourceFunc(). ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.4-1ubuntu1~20.04.2 ProcVersionSignature: Ubuntu 5.8.0-44.50~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-44-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Mar 11 23:17:11 2021 DisplayManager: gdm3 InstallationDate: Installed on 2020-10-17 (145 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Foca
[Desktop-packages] [Bug 1905519] Re: Object St.Bin (0x565425162c80), has been already deallocated — impossible to set any property on it. This might be caused by the object having been destroyed from
** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu) Importance: Undecided => High ** Summary changed: - Object St.Bin (0x565425162c80), has been already deallocated — impossible to set any property on it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs. + Syslog is flooded with Object St.Bin (0x565425162c80), has been already deallocated — impossible to set any property on it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs. ** Changed in: gnome-shell-extension-dashtodock (Ubuntu) Importance: Undecided => High -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-ubuntu-dock in Ubuntu. https://bugs.launchpad.net/bugs/1905519 Title: Syslog is flooded with Object St.Bin (0x565425162c80), has been already deallocated — impossible to set any property on it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs. Status in Dash to dock: New Status in gnome-shell-extension-dashtodock package in Ubuntu: Confirmed Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Confirmed Bug description: The syslog is full of these messages, continuously written all day long Nov 25 07:46:42 pc1 gnome-shell[2980]: Object St.Bin (0x565425162c80), has been already deallocated — impossible to set any property on it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs. Nov 25 07:46:42 pc1 gnome-shell[2980]: == Stack trace for context 0x56541fffb220 == Nov 25 07:46:42 pc1 gnome-shell[2980]: #0 7ffddbfa1940 b /usr/share/gnome-shell/extensions/ubuntu-d...@ubuntu.com/docking.js:2051 (1839cb6a2420 @ 208) ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: gnome-shell-extension-ubuntu-dock 68ubuntu20.10.1 ProcVersionSignature: Ubuntu 5.8.0-29.31-generic 5.8.14 Uname: Linux 5.8.0-29-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu50.1 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Nov 25 07:42:45 2020 InstallationDate: Installed on 2014-06-03 (2366 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) PackageArchitecture: all SourcePackage: gnome-shell-extension-ubuntu-dock UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/dash-to-dock/+bug/1905519/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1918666] Re: Cannot close the modal "Connect to Wifi" window to return to desktop
Seems to be a regression in gjs 1.67.2-2 and downgrading to the previous version fixes it for me: https://launchpad.net/ubuntu/+source/gjs/1.67.2-1/+build/21079029 ** Also affects: gjs (Ubuntu) Importance: Undecided Status: New ** Summary changed: - Cannot close the modal "Connect to Wifi" window to return to desktop + [regression] Shell regressions in 1.67.2-2 starting with "JS ERROR: Error: Argument : value is out of range for uint32" ** Changed in: gjs (Ubuntu) Importance: Undecided => Critical ** Changed in: gjs (Ubuntu) Status: New => Triaged ** No longer affects: gnome-shell (Ubuntu) ** Changed in: gjs (Ubuntu) Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0) ** Summary changed: - [regression] Shell regressions in 1.67.2-2 starting with "JS ERROR: Error: Argument : value is out of range for uint32" + Shell regressions in 1.67.2-2 starting with "JS ERROR: Error: Argument : value is out of range for uint32" ** Tags added: regression-release ** Summary changed: - Shell regressions in 1.67.2-2 starting with "JS ERROR: Error: Argument : value is out of range for uint32" + Shell regressions in gjs 1.67.2-2 starting with "JS ERROR: Error: Argument : value is out of range for uint32" -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1918666 Title: Shell regressions in gjs 1.67.2-2 starting with "JS ERROR: Error: Argument : value is out of range for uint32" Status in gjs package in Ubuntu: Triaged Bug description: When I select the task bar menu, click on the Wifi and select "Select to network", a modal window appears that allows me to select a Wifi network. After I have clicked on one of the networks, normally, when I click Cancel or Connect, the modal window disappears and returns me to the desktop. With the current gnome-shell, this modal window persists and I cannot access the desktop - this is both in Wayland and in X. Connect doesn't seem to work - it's like the buttons are no longer accepting clicks. The ESC key also doesn't do anything. (If I don't click on a network, the ESC key does work, and so does Cancel.) I think I once managed to get Alt-Ctrl-F1 to bring back the GDM login window, but the modal window was still there when I went back into the desktop. Alt-F2 didn't work so I couldn't try re-starting gnome-shell. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: gnome-shell 3.38.3-3ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-11.12-generic 5.11.0 Uname: Linux 5.11.0-11-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu60 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Thu Mar 11 20:35:24 2021 DisplayManager: gdm3 RelatedPackageVersions: mutter-common 3.38.3-3ubuntu2 SourcePackage: gnome-shell UpgradeStatus: Upgraded to hirsute on 2021-02-24 (15 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gjs/+bug/1918666/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1918738] Re: Regression: Onscreen Keyboard Backspace, Enter and Capitalize do not work
*** This bug is a duplicate of bug 1918666 *** https://bugs.launchpad.net/bugs/1918666 Thanks for the bug report. I've generalized bug 1918666 to cover this. ** This bug has been marked a duplicate of bug 1918666 Shell regressions in 1.67.2-2 starting with "JS ERROR: Error: Argument : value is out of range for uint32" -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1918738 Title: Regression: Onscreen Keyboard Backspace, Enter and Capitalize do not work Status in gnome-shell package in Ubuntu: New Bug description: Title pretty much says it all: I'm testing Ubuntu Hirsute (21.04), fully upgraded as of today (Gnome-shell 3.38.3) and the osk keys for Backspace, Enter and Capitalize as well as for collapsing the keyboard do not work. Pressing them just does nothing. Related logs in jouralctl output: _press@resource:///org/gnome/shell/ui/keyboard.js:337:39 _makeKey/<@resource:///org/gnome/shell/ui/keyboard.js:464:22 Mär 11 23:06:02 pc gnome-shell[15039]: JS ERROR: Error: Argument wc: value is out of range for uint32 _getKeyval@resource:///org/gnome/shell/ui/keyboard.js:330:24 _release@resource:///org/gnome/shell/ui/keyboard.js:370:36 _makeKey/<@resource:///org/gnome/shell/ui/keyboard.js:468:22 Mär 11 23:06:03 pc gnome-shell[15039]: JS ERROR: Error: Argument wc: value is out of range for uint32 _getKeyval@resource:///org/gnome/shell/ui/keyboard.js:330:24 _press@resource:///org/gnome/shell/ui/keyboard.js:337:39 _makeKey/<@resource:///org/gnome/shell/ui/keyboard.js:464:22 Mär 11 23:06:03 pc gnome-shell[15039]: JS ERROR: Error: Argument wc: value is out of range for uint32 _getKeyval@resource:///org/gnome/shell/ui/keyboard.js:330:24 _release@resource:///org/gnome/shell/ui/keyboard.js:370:36 _makeKey/<@resource:///org/gnome/shell/ui/keyboard.js:468:22 Mär 11 23:06:04 pc gnome-shell[15039]: JS ERROR: Error: Argument wc: value is out of range for uint32 _getKeyval@resource:///org/gnome/shell/ui/keyboard.js:330:24 _press@resource:///org/gnome/shell/ui/keyboard.js:337:39 _makeKey/<@resource:///org/gnome/shell/ui/keyboard.js:464:22 Mär 11 23:06:04 pc gnome-shell[15039]: JS ERROR: Error: Argument wc: value is out of range for uint32 _getKeyval@resource:///org/gnome/shell/ui/keyboard.js:330:24 _release@resource:///org/gnome/shell/ui/keyboard.js:370:36 _makeKey/<@resource:///org/gnome/shell/ui/keyboard.js:468:22 Mär 11 23:06:04 pc gnome-shell[15039]: JS ERROR: Error: Argument wc: value is out of range for uint32 _getKeyval@resource:///org/gnome/shell/ui/keyboard.js:330:24 _press@resource:///org/gnome/shell/ui/keyboard.js:337:39 _makeKey/<@resource:///org/gnome/shell/ui/keyboard.js:464:22 Mär 11 23:06:04 pc gnome-shell[15039]: JS ERROR: Error: Argument wc: value is out of range for uint32 _getKeyval@resource:///org/gnome/shell/ui/keyboard.js:330:24 _release@resource:///org/gnome/shell/ui/keyboard.js:370:36 _makeKey/<@resource:///org/gnome/shell/ui/keyboard.js:468:22 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1918738/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1918738] Re: Regression: Onscreen Keyboard Backspace, Enter and Capitalize do not work
*** This bug is a duplicate of bug 1918666 *** https://bugs.launchpad.net/bugs/1918666 ** Changed in: gnome-shell (Ubuntu) Importance: Undecided => High -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1918738 Title: Regression: Onscreen Keyboard Backspace, Enter and Capitalize do not work Status in gnome-shell package in Ubuntu: New Bug description: Title pretty much says it all: I'm testing Ubuntu Hirsute (21.04), fully upgraded as of today (Gnome-shell 3.38.3) and the osk keys for Backspace, Enter and Capitalize as well as for collapsing the keyboard do not work. Pressing them just does nothing. Related logs in jouralctl output: _press@resource:///org/gnome/shell/ui/keyboard.js:337:39 _makeKey/<@resource:///org/gnome/shell/ui/keyboard.js:464:22 Mär 11 23:06:02 pc gnome-shell[15039]: JS ERROR: Error: Argument wc: value is out of range for uint32 _getKeyval@resource:///org/gnome/shell/ui/keyboard.js:330:24 _release@resource:///org/gnome/shell/ui/keyboard.js:370:36 _makeKey/<@resource:///org/gnome/shell/ui/keyboard.js:468:22 Mär 11 23:06:03 pc gnome-shell[15039]: JS ERROR: Error: Argument wc: value is out of range for uint32 _getKeyval@resource:///org/gnome/shell/ui/keyboard.js:330:24 _press@resource:///org/gnome/shell/ui/keyboard.js:337:39 _makeKey/<@resource:///org/gnome/shell/ui/keyboard.js:464:22 Mär 11 23:06:03 pc gnome-shell[15039]: JS ERROR: Error: Argument wc: value is out of range for uint32 _getKeyval@resource:///org/gnome/shell/ui/keyboard.js:330:24 _release@resource:///org/gnome/shell/ui/keyboard.js:370:36 _makeKey/<@resource:///org/gnome/shell/ui/keyboard.js:468:22 Mär 11 23:06:04 pc gnome-shell[15039]: JS ERROR: Error: Argument wc: value is out of range for uint32 _getKeyval@resource:///org/gnome/shell/ui/keyboard.js:330:24 _press@resource:///org/gnome/shell/ui/keyboard.js:337:39 _makeKey/<@resource:///org/gnome/shell/ui/keyboard.js:464:22 Mär 11 23:06:04 pc gnome-shell[15039]: JS ERROR: Error: Argument wc: value is out of range for uint32 _getKeyval@resource:///org/gnome/shell/ui/keyboard.js:330:24 _release@resource:///org/gnome/shell/ui/keyboard.js:370:36 _makeKey/<@resource:///org/gnome/shell/ui/keyboard.js:468:22 Mär 11 23:06:04 pc gnome-shell[15039]: JS ERROR: Error: Argument wc: value is out of range for uint32 _getKeyval@resource:///org/gnome/shell/ui/keyboard.js:330:24 _press@resource:///org/gnome/shell/ui/keyboard.js:337:39 _makeKey/<@resource:///org/gnome/shell/ui/keyboard.js:464:22 Mär 11 23:06:04 pc gnome-shell[15039]: JS ERROR: Error: Argument wc: value is out of range for uint32 _getKeyval@resource:///org/gnome/shell/ui/keyboard.js:330:24 _release@resource:///org/gnome/shell/ui/keyboard.js:370:36 _makeKey/<@resource:///org/gnome/shell/ui/keyboard.js:468:22 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1918738/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1918666] Re: Cannot close the modal "Connect to Wifi" window to return to desktop
Slightly similar to bug 1918738. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1918666 Title: Cannot close the modal "Connect to Wifi" window to return to desktop Status in gnome-shell package in Ubuntu: Confirmed Bug description: When I select the task bar menu, click on the Wifi and select "Select to network", a modal window appears that allows me to select a Wifi network. After I have clicked on one of the networks, normally, when I click Cancel or Connect, the modal window disappears and returns me to the desktop. With the current gnome-shell, this modal window persists and I cannot access the desktop - this is both in Wayland and in X. Connect doesn't seem to work - it's like the buttons are no longer accepting clicks. The ESC key also doesn't do anything. (If I don't click on a network, the ESC key does work, and so does Cancel.) I think I once managed to get Alt-Ctrl-F1 to bring back the GDM login window, but the modal window was still there when I went back into the desktop. Alt-F2 didn't work so I couldn't try re-starting gnome-shell. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: gnome-shell 3.38.3-3ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-11.12-generic 5.11.0 Uname: Linux 5.11.0-11-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu60 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Thu Mar 11 20:35:24 2021 DisplayManager: gdm3 RelatedPackageVersions: mutter-common 3.38.3-3ubuntu2 SourcePackage: gnome-shell UpgradeStatus: Upgraded to hirsute on 2021-02-24 (15 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1918666/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1918666] Re: Cannot close the modal "Connect to Wifi" window to return to desktop
Confirmed and I notice: Mar 12 10:04:40 kab gnome-shell[1586]: JS ERROR: Error: Argument timestamp: value is out of range for uint32 popModal@resource:///org/gnome/shell/ui/main.js:637:12 popModal@resource:///org/gnome/shell/ui/modalDialog.js:205:14 close@resource:///org/gnome/shell/ui/modalDialog.js:178:14 ... Mar 12 10:04:46 kab gnome-shell[1586]: pushModal: invocation of begin_modal failed ** Tags added: rls-hh-incoming ** Changed in: gnome-shell (Ubuntu) Importance: Undecided => Critical -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1918666 Title: Cannot close the modal "Connect to Wifi" window to return to desktop Status in gnome-shell package in Ubuntu: Confirmed Bug description: When I select the task bar menu, click on the Wifi and select "Select to network", a modal window appears that allows me to select a Wifi network. After I have clicked on one of the networks, normally, when I click Cancel or Connect, the modal window disappears and returns me to the desktop. With the current gnome-shell, this modal window persists and I cannot access the desktop - this is both in Wayland and in X. Connect doesn't seem to work - it's like the buttons are no longer accepting clicks. The ESC key also doesn't do anything. (If I don't click on a network, the ESC key does work, and so does Cancel.) I think I once managed to get Alt-Ctrl-F1 to bring back the GDM login window, but the modal window was still there when I went back into the desktop. Alt-F2 didn't work so I couldn't try re-starting gnome-shell. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: gnome-shell 3.38.3-3ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-11.12-generic 5.11.0 Uname: Linux 5.11.0-11-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu60 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Thu Mar 11 20:35:24 2021 DisplayManager: gdm3 RelatedPackageVersions: mutter-common 3.38.3-3ubuntu2 SourcePackage: gnome-shell UpgradeStatus: Upgraded to hirsute on 2021-02-24 (15 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1918666/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1918666] Re: Cannot close the modal "Connect to Wifi" window to return to desktop
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gnome-shell (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1918666 Title: Cannot close the modal "Connect to Wifi" window to return to desktop Status in gnome-shell package in Ubuntu: Confirmed Bug description: When I select the task bar menu, click on the Wifi and select "Select to network", a modal window appears that allows me to select a Wifi network. After I have clicked on one of the networks, normally, when I click Cancel or Connect, the modal window disappears and returns me to the desktop. With the current gnome-shell, this modal window persists and I cannot access the desktop - this is both in Wayland and in X. Connect doesn't seem to work - it's like the buttons are no longer accepting clicks. The ESC key also doesn't do anything. (If I don't click on a network, the ESC key does work, and so does Cancel.) I think I once managed to get Alt-Ctrl-F1 to bring back the GDM login window, but the modal window was still there when I went back into the desktop. Alt-F2 didn't work so I couldn't try re-starting gnome-shell. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: gnome-shell 3.38.3-3ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-11.12-generic 5.11.0 Uname: Linux 5.11.0-11-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu60 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Thu Mar 11 20:35:24 2021 DisplayManager: gdm3 RelatedPackageVersions: mutter-common 3.38.3-3ubuntu2 SourcePackage: gnome-shell UpgradeStatus: Upgraded to hirsute on 2021-02-24 (15 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1918666/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1918658] Re: Display glitches when showing context menu
I've occasionally seen the same problem in multiple compositors with multiple different GPUs over the past 10 years. This seems like some kind of Xorg compositing race/failure. ** Tags added: nvidia ** Summary changed: - Display glitches when showing context menu + [nvidia] Display glitches when showing context menu ** Package changed: xorg (Ubuntu) => mutter (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1918658 Title: [nvidia] Display glitches when showing context menu Status in mutter package in Ubuntu: New Bug description: I am using Android Studio to develop Applications. When i have lots of windows opened and i try to open a context menu or write code, it shows a frame of some applications that are below the current window. In the video it is more clear. I don't know if this is a problem related to Ubuntu or Android Studio but it is very noisy. In this case it is clear that the frame shown belongs to the Arduino window that is open under it. Sometimes i can see frames of my wallpaper (when i don't have any window under it) or others. This problem doesn't happen with other programs (for now). ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.8.0-44.50~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-44-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: [Errno 21] È una directory: '/proc/driver/nvidia/capabilities/gpu0' .proc.driver.nvidia.capabilities.mig: Error: [Errno 21] È una directory: '/proc/driver/nvidia/capabilities/mig' .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] È una directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 460.39 Thu Jan 21 21:54:06 UTC 2021 GCC version: gcc version 9.3.0 (Ubuntu 9.3.0-17ubuntu1~20.04) ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 BootLog: Error: [Errno 13] Permesso negato: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Mar 11 13:07:11 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: nvidia, 460.39, 5.8.0-43-generic, x86_64: installed nvidia, 460.39, 5.8.0-44-generic, x86_64: installed virtualbox, 6.1.16, 5.8.0-44-generic, x86_64: installed GraphicsCard: NVIDIA Corporation GP104 [GeForce GTX 1080] [10de:1b80] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] GP104 [GeForce GTX 1080] [1462:3362] InstallationDate: Installed on 2021-01-17 (52 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: Micro-Star International Co., Ltd. MS-7B45 ProcEnviron: LANGUAGE=it PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-44-generic root=UUID=34f5f1d0-f244-447f-8b6b-1ec5c14fe8f6 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/05/2020 dmi.bios.release: 5.12 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: A.B0 dmi.board.asset.tag: Default string dmi.board.name: Z370 GAMING PRO CARBON (MS-7B45) dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: 2.0 dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: 2.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrA.B0:bd06/05/2020:br5.12:svnMicro-StarInternationalCo.,Ltd.:pnMS-7B45:pvr2.0:rvnMicro-StarInternationalCo.,Ltd.:rnZ370GAMINGPROCARBON(MS-7B45):rvr2.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr2.0: dmi.product.family: Default string dmi.product.name: MS-7B45 dmi.product.sku: Default string dmi.product.version: 2.0 dmi.sys.vendor: Micro-Star International Co., Ltd. version.compiz: compiz 1:0.9.14.1+20.04.20200211-0ubuntu1 version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage n
[Desktop-packages] [Bug 1918619] Re: [i915] Horizontal noise-like screen corruption (Gen9 Kaby Lake)
Though this is also reminiscent of bug 1896091. ** Changed in: mesa (Ubuntu) Status: Confirmed => New ** Changed in: mutter (Ubuntu) Status: Confirmed => New ** Tags added: i915 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1918619 Title: [i915] Horizontal noise-like screen corruption (Gen9 Kaby Lake) Status in linux-hwe-5.8 package in Ubuntu: New Status in mesa package in Ubuntu: New Status in mutter package in Ubuntu: New Bug description: I use to press Alt+Tab to switch between windows (or frames, whatever) and I noticed today that when I switch to another window the up bar blinks. I already had a display problem once, so I knew it was better with a external video. EDIT: I remember having this problem a year ago perhaps, and it disappear if I reboot my computer. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.8.0-44.50~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-44-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Mar 11 10:45:08 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Lenovo HD Graphics 620 [17aa:39e9] InstallationDate: Installed on 2020-11-15 (115 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: LENOVO 80V0 ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-44-generic root=UUID=2342b448-1302-426d-9afd-b40fd298cdab ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/03/2018 dmi.bios.release: 2.20 dmi.bios.vendor: LENOVO dmi.bios.version: 3PCN20WW(V2.04) dmi.board.asset.tag: NO Asset Tag dmi.board.name: Lenovo ideapad 510S-13IKB dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad 510S-13IKB dmi.ec.firmware.release: 2.20 dmi.modalias: dmi:bvnLENOVO:bvr3PCN20WW(V2.04):bd07/03/2018:br2.20:efr2.20:svnLENOVO:pn80V0:pvrLenovoideapad510S-13IKB:rvnLENOVO:rnLenovoideapad510S-13IKB:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrLenovoideapad510S-13IKB: dmi.product.family: IDEAPAD dmi.product.name: 80V0 dmi.product.sku: LENOVO_MT_80V0_BU_idea_FM_Lenovo ideapad 510S-13IKB dmi.product.version: Lenovo ideapad 510S-13IKB dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.2.6-0ubuntu0.20.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.8/+bug/1918619/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1918619] Re: [i915] Horizontal noise-like screen corruption (Gen9 Kaby Lake)
Please try some different kernel versions and tell us if any of them do or don't have the same bug: https://kernel.ubuntu.com/~kernel-ppa/mainline/?C=M;O=D -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1918619 Title: [i915] Horizontal noise-like screen corruption (Gen9 Kaby Lake) Status in linux-hwe-5.8 package in Ubuntu: New Status in mesa package in Ubuntu: New Status in mutter package in Ubuntu: New Bug description: I use to press Alt+Tab to switch between windows (or frames, whatever) and I noticed today that when I switch to another window the up bar blinks. I already had a display problem once, so I knew it was better with a external video. EDIT: I remember having this problem a year ago perhaps, and it disappear if I reboot my computer. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.8.0-44.50~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-44-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Mar 11 10:45:08 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Lenovo HD Graphics 620 [17aa:39e9] InstallationDate: Installed on 2020-11-15 (115 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: LENOVO 80V0 ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-44-generic root=UUID=2342b448-1302-426d-9afd-b40fd298cdab ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/03/2018 dmi.bios.release: 2.20 dmi.bios.vendor: LENOVO dmi.bios.version: 3PCN20WW(V2.04) dmi.board.asset.tag: NO Asset Tag dmi.board.name: Lenovo ideapad 510S-13IKB dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad 510S-13IKB dmi.ec.firmware.release: 2.20 dmi.modalias: dmi:bvnLENOVO:bvr3PCN20WW(V2.04):bd07/03/2018:br2.20:efr2.20:svnLENOVO:pn80V0:pvrLenovoideapad510S-13IKB:rvnLENOVO:rnLenovoideapad510S-13IKB:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrLenovoideapad510S-13IKB: dmi.product.family: IDEAPAD dmi.product.name: 80V0 dmi.product.sku: LENOVO_MT_80V0_BU_idea_FM_Lenovo ideapad 510S-13IKB dmi.product.version: Lenovo ideapad 510S-13IKB dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.2.6-0ubuntu0.20.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.8/+bug/1918619/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1918619] Re: [i915] Horizontal noise-like screen corruption (Gen9 Kaby Lake)
A similar issue was reported against radeon (bug 1911369) so maybe it's a problem with Mesa 20.2.6. ** Package changed: linux-signed-hwe-5.8 (Ubuntu) => linux-hwe-5.8 (Ubuntu) ** Changed in: linux-hwe-5.8 (Ubuntu) Status: Confirmed => New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1918619 Title: [i915] Horizontal noise-like screen corruption (Gen9 Kaby Lake) Status in linux-hwe-5.8 package in Ubuntu: New Status in mesa package in Ubuntu: New Status in mutter package in Ubuntu: New Bug description: I use to press Alt+Tab to switch between windows (or frames, whatever) and I noticed today that when I switch to another window the up bar blinks. I already had a display problem once, so I knew it was better with a external video. EDIT: I remember having this problem a year ago perhaps, and it disappear if I reboot my computer. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.8.0-44.50~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-44-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Mar 11 10:45:08 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Lenovo HD Graphics 620 [17aa:39e9] InstallationDate: Installed on 2020-11-15 (115 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: LENOVO 80V0 ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-44-generic root=UUID=2342b448-1302-426d-9afd-b40fd298cdab ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/03/2018 dmi.bios.release: 2.20 dmi.bios.vendor: LENOVO dmi.bios.version: 3PCN20WW(V2.04) dmi.board.asset.tag: NO Asset Tag dmi.board.name: Lenovo ideapad 510S-13IKB dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad 510S-13IKB dmi.ec.firmware.release: 2.20 dmi.modalias: dmi:bvnLENOVO:bvr3PCN20WW(V2.04):bd07/03/2018:br2.20:efr2.20:svnLENOVO:pn80V0:pvrLenovoideapad510S-13IKB:rvnLENOVO:rnLenovoideapad510S-13IKB:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrLenovoideapad510S-13IKB: dmi.product.family: IDEAPAD dmi.product.name: 80V0 dmi.product.sku: LENOVO_MT_80V0_BU_idea_FM_Lenovo ideapad 510S-13IKB dmi.product.version: Lenovo ideapad 510S-13IKB dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.2.6-0ubuntu0.20.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.8/+bug/1918619/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1918619] Re: [i915] Horizontal noise-like screen corruption (Gen9 Kaby Lake)
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: linux-signed-hwe-5.8 (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1918619 Title: [i915] Horizontal noise-like screen corruption (Gen9 Kaby Lake) Status in linux-signed-hwe-5.8 package in Ubuntu: Confirmed Status in mesa package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Bug description: I use to press Alt+Tab to switch between windows (or frames, whatever) and I noticed today that when I switch to another window the up bar blinks. I already had a display problem once, so I knew it was better with a external video. EDIT: I remember having this problem a year ago perhaps, and it disappear if I reboot my computer. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.8.0-44.50~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-44-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Mar 11 10:45:08 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Lenovo HD Graphics 620 [17aa:39e9] InstallationDate: Installed on 2020-11-15 (115 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: LENOVO 80V0 ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-44-generic root=UUID=2342b448-1302-426d-9afd-b40fd298cdab ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/03/2018 dmi.bios.release: 2.20 dmi.bios.vendor: LENOVO dmi.bios.version: 3PCN20WW(V2.04) dmi.board.asset.tag: NO Asset Tag dmi.board.name: Lenovo ideapad 510S-13IKB dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad 510S-13IKB dmi.ec.firmware.release: 2.20 dmi.modalias: dmi:bvnLENOVO:bvr3PCN20WW(V2.04):bd07/03/2018:br2.20:efr2.20:svnLENOVO:pn80V0:pvrLenovoideapad510S-13IKB:rvnLENOVO:rnLenovoideapad510S-13IKB:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrLenovoideapad510S-13IKB: dmi.product.family: IDEAPAD dmi.product.name: 80V0 dmi.product.sku: LENOVO_MT_80V0_BU_idea_FM_Lenovo ideapad 510S-13IKB dmi.product.version: Lenovo ideapad 510S-13IKB dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.2.6-0ubuntu0.20.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.8/+bug/1918619/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1911369] Re: [radeon] Horizontal lines of screen corruption after last update.
OK, I won't bother Norm with any more questions because comment #7 :) Instead I'll move this to bug 1918619. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1911369 Title: [radeon] Horizontal lines of screen corruption after last update. Status in linux package in Ubuntu: Invalid Status in mesa package in Ubuntu: Confirmed Bug description: A clean install is fine if I don't take updates. If I do take the updates and reboot then I get heavy video corruption. This just started today. This is a dual boot system. The windows system has no issues. Appears to be software and not a hardware issue. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.8.0-36.40~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-36-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Jan 12 21:18:27 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Tahiti PRO [Radeon HD 7950/8950 OEM / R9 280] [1002:679a] (prog-if 00 [VGA controller]) Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] Tahiti PRO2 [Radeon HD 7950 Boost] [1002:3000] InstallationDate: Installed on 2021-01-13 (0 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: Hewlett-Packard HP Z420 Workstation ProcEnviron: LANGUAGE=en_CA:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_CA.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-36-generic root=UUID=e1d90a30-a65a-46c5-bae3-c39bbf1a4e0e ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/29/2019 dmi.bios.release: 3.96 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: J61 v03.96 dmi.board.name: 1589 dmi.board.vendor: Hewlett-Packard dmi.board.version: 0.00 dmi.chassis.type: 6 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvrJ61v03.96:bd10/29/2019:br3.96:svnHewlett-Packard:pnHPZ420Workstation:pvr:rvnHewlett-Packard:rn1589:rvr0.00:cvnHewlett-Packard:ct6:cvr: dmi.product.family: 103C_53335X G=D dmi.product.name: HP Z420 Workstation dmi.product.sku: D8N02UC#ABA dmi.sys.vendor: Hewlett-Packard version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.1~20.04.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1911369/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1918619] Re: [i915] Horizontal noise-like screen corruption (Gen9 Kaby Lake)
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: mutter (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1918619 Title: [i915] Horizontal noise-like screen corruption (Gen9 Kaby Lake) Status in linux-signed-hwe-5.8 package in Ubuntu: Confirmed Status in mesa package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Bug description: I use to press Alt+Tab to switch between windows (or frames, whatever) and I noticed today that when I switch to another window the up bar blinks. I already had a display problem once, so I knew it was better with a external video. EDIT: I remember having this problem a year ago perhaps, and it disappear if I reboot my computer. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.8.0-44.50~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-44-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Mar 11 10:45:08 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Lenovo HD Graphics 620 [17aa:39e9] InstallationDate: Installed on 2020-11-15 (115 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: LENOVO 80V0 ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-44-generic root=UUID=2342b448-1302-426d-9afd-b40fd298cdab ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/03/2018 dmi.bios.release: 2.20 dmi.bios.vendor: LENOVO dmi.bios.version: 3PCN20WW(V2.04) dmi.board.asset.tag: NO Asset Tag dmi.board.name: Lenovo ideapad 510S-13IKB dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad 510S-13IKB dmi.ec.firmware.release: 2.20 dmi.modalias: dmi:bvnLENOVO:bvr3PCN20WW(V2.04):bd07/03/2018:br2.20:efr2.20:svnLENOVO:pn80V0:pvrLenovoideapad510S-13IKB:rvnLENOVO:rnLenovoideapad510S-13IKB:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrLenovoideapad510S-13IKB: dmi.product.family: IDEAPAD dmi.product.name: 80V0 dmi.product.sku: LENOVO_MT_80V0_BU_idea_FM_Lenovo ideapad 510S-13IKB dmi.product.version: Lenovo ideapad 510S-13IKB dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.2.6-0ubuntu0.20.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.8/+bug/1918619/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1918619] Re: [i915] Horizontal noise-like screen corruption (Gen9 Kaby Lake)
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: mesa (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1918619 Title: [i915] Horizontal noise-like screen corruption (Gen9 Kaby Lake) Status in linux-signed-hwe-5.8 package in Ubuntu: Confirmed Status in mesa package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Bug description: I use to press Alt+Tab to switch between windows (or frames, whatever) and I noticed today that when I switch to another window the up bar blinks. I already had a display problem once, so I knew it was better with a external video. EDIT: I remember having this problem a year ago perhaps, and it disappear if I reboot my computer. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.8.0-44.50~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-44-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Mar 11 10:45:08 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Lenovo HD Graphics 620 [17aa:39e9] InstallationDate: Installed on 2020-11-15 (115 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: LENOVO 80V0 ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-44-generic root=UUID=2342b448-1302-426d-9afd-b40fd298cdab ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/03/2018 dmi.bios.release: 2.20 dmi.bios.vendor: LENOVO dmi.bios.version: 3PCN20WW(V2.04) dmi.board.asset.tag: NO Asset Tag dmi.board.name: Lenovo ideapad 510S-13IKB dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad 510S-13IKB dmi.ec.firmware.release: 2.20 dmi.modalias: dmi:bvnLENOVO:bvr3PCN20WW(V2.04):bd07/03/2018:br2.20:efr2.20:svnLENOVO:pn80V0:pvrLenovoideapad510S-13IKB:rvnLENOVO:rnLenovoideapad510S-13IKB:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrLenovoideapad510S-13IKB: dmi.product.family: IDEAPAD dmi.product.name: 80V0 dmi.product.sku: LENOVO_MT_80V0_BU_idea_FM_Lenovo ideapad 510S-13IKB dmi.product.version: Lenovo ideapad 510S-13IKB dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.2.6-0ubuntu0.20.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.8/+bug/1918619/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1918619] Re: Horizontal noise-like corruption
** Summary changed: - Kind of slowly refresh + Horizontal noise-like corruption ** Package changed: xorg (Ubuntu) => mutter (Ubuntu) ** Summary changed: - Horizontal noise-like corruption + [i915] Horizontal noise-like screen corruption ** Also affects: linux-signed-hwe-5.8 (Ubuntu) Importance: Undecided Status: New ** Summary changed: - [i915] Horizontal noise-like screen corruption + [i915] Horizontal noise-like screen corruption (Gen9 Kaby Lake) ** Also affects: mesa (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1918619 Title: [i915] Horizontal noise-like screen corruption (Gen9 Kaby Lake) Status in linux-signed-hwe-5.8 package in Ubuntu: Confirmed Status in mesa package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Bug description: I use to press Alt+Tab to switch between windows (or frames, whatever) and I noticed today that when I switch to another window the up bar blinks. I already had a display problem once, so I knew it was better with a external video. EDIT: I remember having this problem a year ago perhaps, and it disappear if I reboot my computer. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.8.0-44.50~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-44-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Mar 11 10:45:08 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Lenovo HD Graphics 620 [17aa:39e9] InstallationDate: Installed on 2020-11-15 (115 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: LENOVO 80V0 ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-44-generic root=UUID=2342b448-1302-426d-9afd-b40fd298cdab ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/03/2018 dmi.bios.release: 2.20 dmi.bios.vendor: LENOVO dmi.bios.version: 3PCN20WW(V2.04) dmi.board.asset.tag: NO Asset Tag dmi.board.name: Lenovo ideapad 510S-13IKB dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad 510S-13IKB dmi.ec.firmware.release: 2.20 dmi.modalias: dmi:bvnLENOVO:bvr3PCN20WW(V2.04):bd07/03/2018:br2.20:efr2.20:svnLENOVO:pn80V0:pvrLenovoideapad510S-13IKB:rvnLENOVO:rnLenovoideapad510S-13IKB:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrLenovoideapad510S-13IKB: dmi.product.family: IDEAPAD dmi.product.name: 80V0 dmi.product.sku: LENOVO_MT_80V0_BU_idea_FM_Lenovo ideapad 510S-13IKB dmi.product.version: Lenovo ideapad 510S-13IKB dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.2.6-0ubuntu0.20.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.8/+bug/1918619/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1918613] Re: [FFe] GDM background configurable with gsettings
** Bug watch added: gitlab.gnome.org/GNOME/gnome-shell/-/issues #680 https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/680 ** Also affects: gnome-shell via https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/680 Importance: Unknown Status: Unknown ** Bug watch added: gitlab.gnome.org/GNOME/gdm/-/issues #684 https://gitlab.gnome.org/GNOME/gdm/-/issues/684 ** Also affects: gdm via https://gitlab.gnome.org/GNOME/gdm/-/issues/684 Importance: Unknown Status: Unknown ** Tags added: hirsute patch -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1918613 Title: [FFe] GDM background configurable with gsettings Status in gdm: Unknown Status in GNOME Shell: Unknown Status in gnome-shell package in Ubuntu: New Bug description: [Description] Customization of the greeter is a requirement from Corporate customers. Currently the background (plain color or image) of the greeter is hard coded in the style embedded in the theme. Customizing this background requires to extract the style sheet from gnome-shell gresource file, modify it manually, recompile and deploy the new gresource, and add an alternative to it. This feature adds 4 gsettings keys to make the background of the greeter configurable via gsettings. The default value defined the in the theme is used for keys that are not set. [Rationale] Corporate customers use LTS releases. This changeset needs to land in hirsute before it can be SRUd into prior Ubuntu LTS releases. So we would like to submit this FFe to get it into Hirsute first. [Risks] The changeset is minimal, isolated and can be easily reverted. In case of error in the code, GDM will fail to load and it will be immediately visible. [Build] Builds and tested successfully locally. Besides the updated JS is not compiled as part of build. [Upstream Issue] https://gitlab.gnome.org/GNOME/gdm/-/issues/684 To manage notifications about this bug go to: https://bugs.launchpad.net/gdm/+bug/1918613/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1682542] Re: Add support for top bars on all monitors to allow for multi-monitor support in primary extensions - apps-menu, places-menu, topbar, etc
I depend on having the clock displayed on *every* monitor I'm working with, so not having the top bar on secondary displays is a major no-no, IMHO. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1682542 Title: Add support for top bars on all monitors to allow for multi-monitor support in primary extensions - apps-menu, places-menu, topbar, etc Status in GNOME Shell: Incomplete Status in gnome-shell package in Ubuntu: Triaged Bug description: This issue will effectively be a regression in desktop usage once Ubuntu switches from Unity to Gnome Shell. Gnome Shell does not work well with multiple monitors unlike every other desktop environment except Budgie, which is switching away from GTK/Gnome to Qt with Budgie 11 due out in the next month or two. I reported it upstream last month but it does not appear to have much traction at the moment. https://bugzilla.gnome.org/show_bug.cgi?id=780078 " It would be nice if the primary included gnome-shell extensions, eg apps-menu and places-menu (and by extension the topbar) supported multi-monitor similar to how the bottom bar 'window-list' currently does. This was easy to achieve on Gnome 2 and now via MATE (out of the box) but there does not appear to be any way to do this with Gnome 3. This also leads to there not being a way to do this via 'Gnome Classic'. Even Windows finally (in W10) does this better out of the box than Gnome 3. BTW - Intel has supported IGP triple head since Ivy Bridge (2012) so it is very cheap to deploy a triple head system (~ $200 for 3 1080p monitors). AMD supports up to quad head in their IGPs. This has been blocking me from moving to Gnome 3 since its release and I finally decided to write a bug report about it. I have had all multi-monitor systems since prior to 2004. " And see comments #11 and #14 from Florian. " No, you don't want that in the extensions. Each extension is separate, so what you are asking for here is that apps-menu and places-menu *both* add top bars to non-primary monitors. We are definitely not going to add two or more stacked panels at the top. What you probably want instead is an option in gnome-shell to put top bars on non-primary monitors, and the aforementioned extensions to handle that case. " " Well, we've established what you want, but that doesn't necessarily mean that we'll implement it. So far the reasoning seems to be: - you really want the feature - GNOME 2 / Windows has it Unlike the case of the window list, nothing in the top bar (except for the app menu to some extent) is tied to a particular monitor, so there's a much weaker case here IMHO. (I'll also note that this wouldn't be a "cheap" option, but require work on lots of details throughout the stack - we'd need to figure out the overview (only include the activities button on the primary monitor? or allow an overview on any monitor?), get API to control the brightness of a particular monitor (rather than the built-in one), don't use "the monitor with the top bar" as indicator for the primary monitor in Settings, ...) " To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1682542/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1918482] Re: Update for GHSA-xgh4-387p-hqpp
** Bug watch added: Debian Bug tracker #984859 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=984859 ** Also affects: flatpak (Debian) via https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=984859 Importance: Unknown Status: Unknown ** Changed in: flatpak (Ubuntu) Importance: Undecided => High ** Changed in: flatpak (Ubuntu Bionic) Importance: Undecided => High ** Changed in: flatpak (Ubuntu Focal) Importance: Undecided => High ** Changed in: flatpak (Ubuntu Groovy) Importance: Undecided => High -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to flatpak in Ubuntu. https://bugs.launchpad.net/bugs/1918482 Title: Update for GHSA-xgh4-387p-hqpp Status in flatpak package in Ubuntu: Fix Released Status in flatpak source package in Bionic: In Progress Status in flatpak source package in Focal: In Progress Status in flatpak source package in Groovy: In Progress Status in flatpak package in Debian: Unknown Bug description: [Links] https://github.com/flatpak/flatpak/security/advisories/GHSA-xgh4-387p-hqpp https://github.com/flatpak/flatpak/pull/4156 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=984859 https://security-tracker.debian.org/tracker/CVE-2021-21381 [Impact] Versions in Ubuntu right now: Hirsute: 1.10.1-4 Groovy: 1.8.2-1ubuntu0.1 Focal: 1.6.5-0ubuntu0.2 Bionic: 1.0.9-0ubuntu0.2 Affected versions: >= 0.9.4 Patched versions: >= 1.10.2 [Test Case] No test case has been mentioned yet, but in the patches there are changes/additions to the unit tests. [Regression Potential] Flatpak has a test suite, which is run on build across all relevant architectures and passes. There is also a manual test plan https://wiki.ubuntu.com/Process/Merges/TestPlan/flatpak . Flatpak has autopkgtests enabled http://autopkgtest.ubuntu.com/packages/f/flatpak . Regression potential is low, and upstream is very responsive to any issues raised. [Other information] Sandbox escape via special tokens in .desktop file (flatpak#4146) Flatpak since 0.9.4 has a vulnerability in the "file forwarding" feature which can be used by an attacker to gain access to files that would not ordinarily be allowed by the app's permissions. Impact By putting the special tokens @@ and/or @@u in the Exec field of a Flatpak app's .desktop file, a malicious app publisher can trick flatpak into behaving as though the user had chosen to open a target file with their Flatpak app, which automatically makes that file available to the Flatpak app. A minimal solution is the first commit "Disallow @@ and @@U usage in desktop files". The follow-up commits "dir: Reserve the whole @@ prefix" and "dir: Refuse to export .desktop files with suspicious uses of @@ tokens" are recommended, but not strictly required. Workarounds Avoid installing Flatpak apps from untrusted sources, or check the contents of the exported .desktop files in exports/share/applications/*.desktop (typically ~/.local/share/flatpak/exports/share/applications/*.desktop and /var/lib/flatpak/exports/share/applications/*.desktop) to make sure that literal filenames do not follow @@ or @@u. References Acknowledgements Thanks to @AntonLydike for reporting this issue, and @refi64 for providing the initial solution. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/flatpak/+bug/1918482/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1179524] Re: Bad colors with RDP connection
I would say this is still unfixed, I still have this issue on 20.10 and 21.04 ** Attachment added: "Screenshot from 2021-03-11 23-45-23.png" https://bugs.launchpad.net/ubuntu/+source/remmina/+bug/1179524/+attachment/5475936/+files/Screenshot%20from%202021-03-11%2023-45-23.png ** Changed in: remmina (Ubuntu) Status: Invalid => New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to remmina in Ubuntu. https://bugs.launchpad.net/bugs/1179524 Title: Bad colors with RDP connection Status in remmina package in Ubuntu: New Bug description: Ubuntu 13.04 remmina (1.0.0-4ubuntu2) I've used Remmina for quite a while and been fairly pleased with it. After upgrading to 13.04 however the colors coming from my Win7 machine are all messed up. Its as if they were inverted or otherwise skewed. White is white and black is black, but the "Start" button looks weird and sun bursty and most of the colors just seem wrong. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/remmina/+bug/1179524/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1918739] [NEW] Gnome-shell got stuck and produces a plethora of error log messages to syslog file
Public bug reported: This is the message in syslog file: мар 11 09:34:43 hpz gnome-shell[2689]: == Stack trace for context 0x5563584e4900 == мар 11 09:34:43 hpz gnome-shell[2689]: == Stack trace for context 0x5563584e4900 == мар 11 09:34:43 hpz gnome-shell[2689]: == Stack trace for context 0x5563584e4900 == мар 11 09:34:43 hpz gnome-shell[2689]: == Stack trace for context 0x5563584e4900 == мар 11 09:34:43 hpz gnome-shell[2689]: == Stack trace for context 0x5563584e4900 == мар 11 09:34:43 hpz gnome-shell[2689]: == Stack trace for context 0x5563584e4900 == мар 11 09:34:43 hpz gnome-shell[2689]: == Stack trace for context 0x5563584e4900 == мар 11 09:34:43 hpz gnome-shell[2689]: == Stack trace for context 0x5563584e4900 == мар 11 09:34:44 hpz gnome-shell[2689]: Attempting to run a JS callback during garbage collection. This is most likely caused by destroying a Clutter actor or GTK widget with ::destroy signal connected, or using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked. мар 11 09:34:44 hpz systemd-journald[377]: Suppressed 496051 messages from user@1000.service мар 11 09:34:44 hpz gnome-shell[2689]: The offending callback was SourceFunc(). мар 11 09:34:44 hpz gnome-shell[2689]: Attempting to run a JS callback during garbage collection. This is most likely caused by destroying a Clutter actor or GTK widget with ::destroy signal connected, or using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked. мар 11 09:34:44 hpz gnome-shell[2689]: The offending callback was SourceFunc(). мар 11 09:34:44 hpz gnome-shell[2689]: Attempting to run a JS callback during garbage collection. This is most likely caused by destroying a Clutter actor or GTK widget with ::destroy signal connected, or using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked. мар 11 09:34:44 hpz gnome-shell[2689]: The offending callback was SourceFunc(). мар 11 09:34:44 hpz gnome-shell[2689]: Attempting to run a JS callback during garbage collection. This is most likely caused by destroying a Clutter actor or GTK widget with ::destroy signal connected, or using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked. мар 11 09:34:44 hpz gnome-shell[2689]: The offending callback was SourceFunc(). мар 11 09:34:44 hpz gnome-shell[2689]: Attempting to run a JS callback during garbage collection. This is most likely caused by destroying a Clutter actor or GTK widget with ::destroy signal connected, or using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked. мар 11 09:34:44 hpz gnome-shell[2689]: The offending callback was SourceFunc(). мар 11 09:34:44 hpz gnome-shell[2689]: Attempting to run a JS callback during garbage collection. This is most likely caused by destroying a Clutter actor or GTK widget with ::destroy signal connected, or using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked. мар 11 09:34:44 hpz gnome-shell[2689]: The offending callback was SourceFunc(). ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.4-1ubuntu1~20.04.2 ProcVersionSignature: Ubuntu 5.8.0-44.50~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-44-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Mar 11 23:17:11 2021 DisplayManager: gdm3 InstallationDate: Installed on 2020-10-17 (145 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) RelatedPackageVersions: mutter-common 3.36.7+git20201123-0.20.04.1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1918739 Title: Gnome-shell got stuck and produces a plethora of error log messages to syslog file Status in gnome-shell package in Ubuntu: New Bug description: This is the message in syslog file: мар 11 09:34:43 hpz gnome-shell[2689]: == Stack trace for context 0x5563584e4900 == мар 11 09:34:43 hpz gnome-shell[2689]: == Stack trace for context 0x5563584e4900 == мар 11 09:34:43 hpz gnome-shell[2689]: == Stack trace for context 0x5563584e4900 == мар 11 09:34:43 hpz gnome-shell[2689]: == Stack trace for context 0x5563584e4900 == мар 11 09:34:43 hpz gnome-shell[2689]: == Stack trace for context 0x5563584e4900 == мар 11 09:34:43 hpz gnome-shell[2689]: == Stack trace for context 0x5563584e4900 == мар 11 09:34:43 hpz gnome-shell[2689]: == Stack trace f
[Desktop-packages] [Bug 1918738] [NEW] Regression: Onscreen Keyboard Backspace, Enter and Capitalize do not work
Public bug reported: Title pretty much says it all: I'm testing Ubuntu Hirsute (21.04), fully upgraded as of today (Gnome-shell 3.38.3) and the osk keys for Backspace, Enter and Capitalize as well as for collapsing the keyboard do not work. Pressing them just does nothing. Related logs in jouralctl output: _press@resource:///org/gnome/shell/ui/keyboard.js:337:39 _makeKey/<@resource:///org/gnome/shell/ui/keyboard.js:464:22 Mär 11 23:06:02 pc gnome-shell[15039]: JS ERROR: Error: Argument wc: value is out of range for uint32 _getKeyval@resource:///org/gnome/shell/ui/keyboard.js:330:24 _release@resource:///org/gnome/shell/ui/keyboard.js:370:36 _makeKey/<@resource:///org/gnome/shell/ui/keyboard.js:468:22 Mär 11 23:06:03 pc gnome-shell[15039]: JS ERROR: Error: Argument wc: value is out of range for uint32 _getKeyval@resource:///org/gnome/shell/ui/keyboard.js:330:24 _press@resource:///org/gnome/shell/ui/keyboard.js:337:39 _makeKey/<@resource:///org/gnome/shell/ui/keyboard.js:464:22 Mär 11 23:06:03 pc gnome-shell[15039]: JS ERROR: Error: Argument wc: value is out of range for uint32 _getKeyval@resource:///org/gnome/shell/ui/keyboard.js:330:24 _release@resource:///org/gnome/shell/ui/keyboard.js:370:36 _makeKey/<@resource:///org/gnome/shell/ui/keyboard.js:468:22 Mär 11 23:06:04 pc gnome-shell[15039]: JS ERROR: Error: Argument wc: value is out of range for uint32 _getKeyval@resource:///org/gnome/shell/ui/keyboard.js:330:24 _press@resource:///org/gnome/shell/ui/keyboard.js:337:39 _makeKey/<@resource:///org/gnome/shell/ui/keyboard.js:464:22 Mär 11 23:06:04 pc gnome-shell[15039]: JS ERROR: Error: Argument wc: value is out of range for uint32 _getKeyval@resource:///org/gnome/shell/ui/keyboard.js:330:24 _release@resource:///org/gnome/shell/ui/keyboard.js:370:36 _makeKey/<@resource:///org/gnome/shell/ui/keyboard.js:468:22 Mär 11 23:06:04 pc gnome-shell[15039]: JS ERROR: Error: Argument wc: value is out of range for uint32 _getKeyval@resource:///org/gnome/shell/ui/keyboard.js:330:24 _press@resource:///org/gnome/shell/ui/keyboard.js:337:39 _makeKey/<@resource:///org/gnome/shell/ui/keyboard.js:464:22 Mär 11 23:06:04 pc gnome-shell[15039]: JS ERROR: Error: Argument wc: value is out of range for uint32 _getKeyval@resource:///org/gnome/shell/ui/keyboard.js:330:24 _release@resource:///org/gnome/shell/ui/keyboard.js:370:36 _makeKey/<@resource:///org/gnome/shell/ui/keyboard.js:468:22 ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: hirsute ** Tags added: hirsute ** Description changed: - Title pretty much says it all: I'm testing Ubuntu Hirsute (21.04), fully upgraded as of today (Gnome-shell 3.38.3) and the osk keys for Backspace, Enter and Capitalize do not work. Pressing them just does nothing. + Title pretty much says it all: I'm testing Ubuntu Hirsute (21.04), fully upgraded as of today (Gnome-shell 3.38.3) and the osk keys for Backspace, Enter and Capitalize as well as for collapsing the keyboard do not work. Pressing them just does nothing. Related logs in jouralctl output: - _press@resource:///org/gnome/shell/ui/keyboard.js:337:39 - _makeKey/<@resource:///org/gnome/shell/ui/keyboard.js:464:22 + _press@resource:///org/gnome/shell/ui/keyboard.js:337:39 + _makeKey/<@resource:///org/gnome/shell/ui/keyboard.js:464:22 Mär 11 23:06:02 pc gnome-shell[15039]: JS ERROR: Error: Argument wc: value is out of range for uint32 - _getKeyval@resource:///org/gnome/shell/ui/keyboard.js:330:24 - _release@resource:///org/gnome/shell/ui/keyboard.js:370:36 - _makeKey/<@resource:///org/gnome/shell/ui/keyboard.js:468:22 + _getKeyval@resource:///org/gnome/shell/ui/keyboard.js:330:24 + _releas
[Desktop-packages] [Bug 1918729] Re: please sync qpdf 10.3.1-1 from debian experimental
Makes sense. Hopefully ubuntu is looking either at only the supported architectures or only the ones that it uses itself. In the former case, looks like everything's built but mips64el which appears to be building now, so hopefully it's not much longer. If I'm lucky, 10.2.0 and 10.3.0 won't make it into anyone's releases. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to qpdf in Ubuntu. https://bugs.launchpad.net/bugs/1918729 Title: please sync qpdf 10.3.1-1 from debian experimental Status in qpdf package in Ubuntu: In Progress Bug description: 10.3.1 includes a very small but important fix to a bug that would cause qpdf 10.3.0 to reject certain valid files when splitting pages. I also added a check for exceptions that will make future bugs of this type (if any) just generate warnings instead of blocking the whole operations in hopes of not needing to do any emergency releases any time soon even if this wasn't the "last bug." To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qpdf/+bug/1918729/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1918729] Re: please sync qpdf 10.3.1-1 from debian experimental
When you get the "Accepted" message from Debian shortly after your upload the build servers start to build the package for all supported architectures and for Debian these are many. It can take hours until they are all built, especially the exotic ones, and it seems that Ubuntu only sees the new release of a package when all architectures at Debian are done. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to qpdf in Ubuntu. https://bugs.launchpad.net/bugs/1918729 Title: please sync qpdf 10.3.1-1 from debian experimental Status in qpdf package in Ubuntu: In Progress Bug description: 10.3.1 includes a very small but important fix to a bug that would cause qpdf 10.3.0 to reject certain valid files when splitting pages. I also added a check for exceptions that will make future bugs of this type (if any) just generate warnings instead of blocking the whole operations in hopes of not needing to do any emergency releases any time soon even if this wasn't the "last bug." To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qpdf/+bug/1918729/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1918729] Re: please sync qpdf 10.3.1-1 from debian experimental
Thanks. I don't know if there's a way for me to know when your utility can find it. I wait until I get the email from debian that the package has been accepted before posting this, but apparently that's not quite enough. Eventually debian will release, Ubuntu will release, and automatic syncs will resume. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to qpdf in Ubuntu. https://bugs.launchpad.net/bugs/1918729 Title: please sync qpdf 10.3.1-1 from debian experimental Status in qpdf package in Ubuntu: In Progress Bug description: 10.3.1 includes a very small but important fix to a bug that would cause qpdf 10.3.0 to reject certain valid files when splitting pages. I also added a check for exceptions that will make future bugs of this type (if any) just generate warnings instead of blocking the whole operations in hopes of not needing to do any emergency releases any time soon even if this wasn't the "last bug." To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qpdf/+bug/1918729/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1916786] Re: weak dependency to libreoffice-sdbc-hsqldb
My last comment was incorrect. https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1918308 is a different issue altogether. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1916786 Title: weak dependency to libreoffice-sdbc-hsqldb Status in libreoffice package in Ubuntu: Triaged Bug description: The user can't create a new Base file with the wizard if the libreoffice-sdbc-hsqldb package isn't installed. The package libreoffice-base-drivers has only a "suggests" dependency to libreoffice-sdbc-hsqldb. It should have a "depends" dependency. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: libreoffice-base-drivers 1:6.4.6-0ubuntu0.20.04.1 ProcVersionSignature: Ubuntu 5.4.0-66.74-generic 5.4.86 Uname: Linux 5.4.0-66-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: XFCE Date: Wed Feb 24 18:32:22 2021 InstallationDate: Installed on 2020-10-12 (134 days ago) InstallationMedia: Xubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) SourcePackage: libreoffice UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.logrotate.d.apport: 2021-02-03T16:41:54.752959 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1916786/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1918308] Re: Upgrading liblibreoffice-java pulls openjdk/jre on ISOs
My last comment needs to be amended to say that if you install the "libreoffice" meta package (that is not seeded on the ISO), *then* it pulls in jre. If you only apt-update on a live disk, then jre is not pulled in. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1918308 Title: Upgrading liblibreoffice-java pulls openjdk/jre on ISOs Status in libreoffice package in Ubuntu: In Progress Bug description: Upgrading liblibreoffice-java (7.0.4 -> 7.1.1) in hirsute drags in the ure-jave/jdk/jre. Build log: https://launchpadlibrarian.net/527002812/buildlog_ubuntu_hirsute_amd64_ubuntu_BUILDING.txt.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1918308/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1918482] Re: Update for GHSA-xgh4-387p-hqpp
Hirsute now contains 1.10.2-1 with the fix, so I am marking it as fixed released. ** Changed in: flatpak (Ubuntu) Status: In Progress => Fix Released ** Description changed: [Links] https://github.com/flatpak/flatpak/security/advisories/GHSA-xgh4-387p-hqpp https://github.com/flatpak/flatpak/pull/4156 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=984859 + https://security-tracker.debian.org/tracker/CVE-2021-21381 [Impact] Versions in Ubuntu right now: Hirsute: 1.10.1-4 Groovy: 1.8.2-1ubuntu0.1 Focal: 1.6.5-0ubuntu0.2 Bionic: 1.0.9-0ubuntu0.2 Affected versions: >= 0.9.4 Patched versions: >= 1.10.2 [Test Case] No test case has been mentioned yet, but in the patches there are changes/additions to the unit tests. [Regression Potential] Flatpak has a test suite, which is run on build across all relevant architectures and passes. There is also a manual test plan https://wiki.ubuntu.com/Process/Merges/TestPlan/flatpak . Flatpak has autopkgtests enabled http://autopkgtest.ubuntu.com/packages/f/flatpak . Regression potential is low, and upstream is very responsive to any issues raised. [Other information] Sandbox escape via special tokens in .desktop file (flatpak#4146) Flatpak since 0.9.4 has a vulnerability in the "file forwarding" feature which can be used by an attacker to gain access to files that would not ordinarily be allowed by the app's permissions. Impact By putting the special tokens @@ and/or @@u in the Exec field of a Flatpak app's .desktop file, a malicious app publisher can trick flatpak into behaving as though the user had chosen to open a target file with their Flatpak app, which automatically makes that file available to the Flatpak app. A minimal solution is the first commit "Disallow @@ and @@U usage in desktop files". The follow-up commits "dir: Reserve the whole @@ prefix" and "dir: Refuse to export .desktop files with suspicious uses of @@ tokens" are recommended, but not strictly required. Workarounds Avoid installing Flatpak apps from untrusted sources, or check the contents of the exported .desktop files in exports/share/applications/*.desktop (typically ~/.local/share/flatpak/exports/share/applications/*.desktop and /var/lib/flatpak/exports/share/applications/*.desktop) to make sure that literal filenames do not follow @@ or @@u. References Acknowledgements Thanks to @AntonLydike for reporting this issue, and @refi64 for providing the initial solution. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to flatpak in Ubuntu. https://bugs.launchpad.net/bugs/1918482 Title: Update for GHSA-xgh4-387p-hqpp Status in flatpak package in Ubuntu: Fix Released Status in flatpak source package in Bionic: In Progress Status in flatpak source package in Focal: In Progress Status in flatpak source package in Groovy: In Progress Bug description: [Links] https://github.com/flatpak/flatpak/security/advisories/GHSA-xgh4-387p-hqpp https://github.com/flatpak/flatpak/pull/4156 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=984859 https://security-tracker.debian.org/tracker/CVE-2021-21381 [Impact] Versions in Ubuntu right now: Hirsute: 1.10.1-4 Groovy: 1.8.2-1ubuntu0.1 Focal: 1.6.5-0ubuntu0.2 Bionic: 1.0.9-0ubuntu0.2 Affected versions: >= 0.9.4 Patched versions: >= 1.10.2 [Test Case] No test case has been mentioned yet, but in the patches there are changes/additions to the unit tests. [Regression Potential] Flatpak has a test suite, which is run on build across all relevant architectures and passes. There is also a manual test plan https://wiki.ubuntu.com/Process/Merges/TestPlan/flatpak . Flatpak has autopkgtests enabled http://autopkgtest.ubuntu.com/packages/f/flatpak . Regression potential is low, and upstream is very responsive to any issues raised. [Other information] Sandbox escape via special tokens in .desktop file (flatpak#4146) Flatpak since 0.9.4 has a vulnerability in the "file forwarding" feature which can be used by an attacker to gain access to files that would not ordinarily be allowed by the app's permissions. Impact By putting the special tokens @@ and/or @@u in the Exec field of a Flatpak app's .desktop file, a malicious app publisher can trick flatpak into behaving as though the user had chosen to open a target file with their Flatpak app, which automatically makes that file available to the Flatpak app. A minimal solution is the first commit "Disallow @@ and @@U usage in desktop files". The follow-up commits "dir: Reserve the whole @@ prefix" and "dir: Refuse to export .desktop files with suspicious uses of @@ tokens" are recommended, but not strictly required. Workarounds Avoid installing Flatpak apps from untrusted sources, or check the contents of
[Desktop-packages] [Bug 1918729] Re: please sync qpdf 10.3.1-1 from debian experimental
CUPS Snap is updated to QPDF 10.3.1 now. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to qpdf in Ubuntu. https://bugs.launchpad.net/bugs/1918729 Title: please sync qpdf 10.3.1-1 from debian experimental Status in qpdf package in Ubuntu: In Progress Bug description: 10.3.1 includes a very small but important fix to a bug that would cause qpdf 10.3.0 to reject certain valid files when splitting pages. I also added a check for exceptions that will make future bugs of this type (if any) just generate warnings instead of blocking the whole operations in hopes of not needing to do any emergency releases any time soon even if this wasn't the "last bug." To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qpdf/+bug/1918729/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1913353] Re: [SRU] libreoffice 7.0.5 for groovy
** Description changed: [Impact] * LibreOffice 7.0.5 is in its fifth bugfix release of the 7.0 line: https://wiki.documentfoundation.org/ReleasePlan/7.0#7.0.5_release - * Version 7.0.3 is currently released in groovy. For a list of fixed bugs compared to 7.0.3 see the list of bugs fixed in the release candidates of 7.0.4 and 7.0.5 (that's a total of 114 bugs for 7.0.4 + for 7.0.5): + * Version 7.0.3 is currently released in groovy. For a list of fixed bugs compared to 7.0.3 see the list of bugs fixed in the release candidates of 7.0.4 and 7.0.5 (that's a total of 114 bugs for 7.0.4 + 104 for 7.0.5): https://wiki.documentfoundation.org/Releases/7.0.4/RC1#List_of_fixed_bugs https://wiki.documentfoundation.org/Releases/7.0.4/RC2#List_of_fixed_bugs https://wiki.documentfoundation.org/Releases/7.0.5/RC1#List_of_fixed_bugs https://wiki.documentfoundation.org/Releases/7.0.5/RC2#List_of_fixed_bugs * Given the nature of the project, the complexity of the codebase and the high level of quality assurance upstream, it is preferable to SRU a minor release rather than cherry-pick selected bug fixes. [Testing] * Upstream testing. Bugs fixed upstream typically include unit/regression tests, and the release itself is extensively exercised (both in an automated manner and manually). * A recent set of upstream's automated jenkins testing can be found here: https://ci.libreoffice.org/job/gerrit_linux_gcc_release/82662/console * More information about the upstream QA testing can be found here: * Automated tests - https://wiki.documentfoundation.org/QA/Testing/Automated_Tests * Automated UI tests - https://wiki.documentfoundation.org/Development/UITests * Regression tests - https://wiki.documentfoundation.org/QA/Testing/Regression_Tests * Feature tests - https://wiki.documentfoundation.org/QA/Testing/Feature_Tests * Launchpad testing. The libreoffice packages include autopkgtests that were run and verified as passing. * [amd64] * [arm64] * [armhf] * [ppc64el] * [s390x] * General smoke testing of all the applications in the office suite were carried out by going through the manual testplan as documented by: https://wiki.ubuntu.com/Process/Merges/TestPlans/libreoffice [Regression Potential] - * A minor release with a total of bug fixes always carries the + * A minor release with a total of 218 bug fixes always carries the potential for introducing regressions, even though it is a bugfix-only release, meaning that no new features were added, and no existing features were removed. * A combination of autopkgtests and careful smoke testing as described above should provide reasonable confidence that no regressions sneaked in. ** Description changed: [Impact] * LibreOffice 7.0.5 is in its fifth bugfix release of the 7.0 line: https://wiki.documentfoundation.org/ReleasePlan/7.0#7.0.5_release * Version 7.0.3 is currently released in groovy. For a list of fixed bugs compared to 7.0.3 see the list of bugs fixed in the release candidates of 7.0.4 and 7.0.5 (that's a total of 114 bugs for 7.0.4 + 104 for 7.0.5): https://wiki.documentfoundation.org/Releases/7.0.4/RC1#List_of_fixed_bugs https://wiki.documentfoundation.org/Releases/7.0.4/RC2#List_of_fixed_bugs https://wiki.documentfoundation.org/Releases/7.0.5/RC1#List_of_fixed_bugs https://wiki.documentfoundation.org/Releases/7.0.5/RC2#List_of_fixed_bugs * Given the nature of the project, the complexity of the codebase and the high level of quality assurance upstream, it is preferable to SRU a minor release rather than cherry-pick selected bug fixes. [Testing] * Upstream testing. Bugs fixed upstream typically include unit/regression tests, and the release itself is extensively exercised (both in an automated manner and manually). * A recent set of upstream's automated jenkins testing can be found here: https://ci.libreoffice.org/job/gerrit_linux_gcc_release/82662/console * More information about the upstream QA testing can be found here: - * Automated tests - https://wiki.documentfoundation.org/QA/Testing/Automated_Tests - * Automated UI tests - https://wiki.documentfoundation.org/Development/UITests - * Regression tests - https://wiki.documentfoundation.org/QA/Testing/Regression_Tests - * Feature tests - https://wiki.documentfoundation.org/QA/Testing/Feature_Tests + * Automated tests + https://wiki.documentfoundation.org/QA/Testing/Automated_Tests + * Automated UI tests + https://wiki.documentfoundation.org/Development/UITests + * Regression tests + https://wiki.documentfoundation.org/QA/Testing/Regression_Tests + * Feature tests + https://wiki.documentfoundation.org/QA/Testing/Feature_Tests * Launchpad testing. The libreoffice
[Desktop-packages] [Bug 1915562] Re: [snap] Libreoffice not loading installed fonts
** Summary changed: - Libreoffice not loading installed fonts + [snap] Libreoffice not loading installed fonts -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1915562 Title: [snap] Libreoffice not loading installed fonts Status in libreoffice package in Ubuntu: New Bug description: I've downloaded news fonts to be used on LibreOffice when I try to use them, the fonts are not loading ProblemType: Bug DistroRelease: Ubuntu 20.04 ProcVersionSignature: Ubuntu 5.8.0-43.49~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-43-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Feb 12 22:58:17 2021 InstallationDate: Installed on 2020-10-15 (120 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Snap: libreoffice 7.0.4.2 (latest/stable) SnapSource: ubuntu/+source/libreoffice UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1915562/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1918729] Re: please sync qpdf 10.3.1-1 from debian experimental
OK, I will sync it as soon as Debian has built it so far that our sync utility finds it. ** Changed in: qpdf (Ubuntu) Status: New => In Progress -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to qpdf in Ubuntu. https://bugs.launchpad.net/bugs/1918729 Title: please sync qpdf 10.3.1-1 from debian experimental Status in qpdf package in Ubuntu: In Progress Bug description: 10.3.1 includes a very small but important fix to a bug that would cause qpdf 10.3.0 to reject certain valid files when splitting pages. I also added a check for exceptions that will make future bugs of this type (if any) just generate warnings instead of blocking the whole operations in hopes of not needing to do any emergency releases any time soon even if this wasn't the "last bug." To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qpdf/+bug/1918729/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1906684] Re: [SRU] libreoffice 6.4.7 for Focal
** Description changed: [Impact] - * LibreOffice 6.4.7 is in its seventh bug-fix release of the 6.4 branch. - Version 6.4.6 is currently in focal. + * LibreOffice 6.4.7 is in its seventh bug-fix release of the 6.4 line: + https://wiki.documentfoundation.org/ReleasePlan/6.4#6.4.7_release - For a list of fixed bugs compared to 6.4.6 see the list of bugs fixed in the two release candidates: + * Version 6.4.6 is currently released in focal. For a list of fixed bugs compared to 6.4.6 see the list of bugs fixed in the two release candidates: https://wiki.documentfoundation.org/Releases/6.4.7/RC1 https://wiki.documentfoundation.org/Releases/6.4.7/RC2 (that's a total of 72 bugs) * Given the nature of the project, the complexity of the codebase and the high level of quality assurance upstream, it is preferable to SRU a minor release rather than cherry-pick selected bug fixes. + [Testing] - [Test Case] + * Upstream testing. Bugs fixed upstream typically include + unit/regression tests, and the release itself is extensively exercised + (both in an automated manner and manually). - * No specific test case, bugs fixed upstream hopefully come with - unit/regression tests, and the release itself is extensively exercised - upstream (both in an automated manner and manually) by a community of - testers. Each minor release normally goes through two release - candidates. + * A recent set of upstream's automated jenkins testing can be found here: + https://ci.libreoffice.org/job/gerrit_64/1808/ - * The libreoffice packages include autopkgtests, those should be run and - verified to pass. + * More information about the upstream QA testing can be found here: + * Automated tests + https://wiki.documentfoundation.org/QA/Testing/Automated_Tests + * Automated UI tests + https://wiki.documentfoundation.org/Development/UITests + * Regression tests + https://wiki.documentfoundation.org/QA/Testing/Regression_Tests + * Feature tests + https://wiki.documentfoundation.org/QA/Testing/Feature_Tests - * General smoke testing of all the applications in the office suite - should be carried out. + * Launchpad testing. The libreoffice packages include autopkgtests that + were run and verified as passing. + * [amd64] https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-focal-ricotz-ppa/focal/amd64/libr/libreoffice/20210310_155918_ee47e@/log.gz + * [arm64] https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-focal-ricotz-ppa/focal/arm64/libr/libreoffice/20210310_200818_ee47e@/log.gz + * [armhf] https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-focal-ricotz-ppa/focal/armhf/libr/libreoffice/20210310_174648_abb49@/log.gz + * [ppc64el] https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-focal-ricotz-ppa/focal/ppc64el/libr/libreoffice/20210310_165457_abb49@/log.gz + * [s390x] https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-focal-ricotz-ppa/focal/s390x/libr/libreoffice/20210310_160307_abb49@/log.gz + + * General smoke testing of all the applications in the office suite were + carried out by going through the manual testplan as documented by: + https://wiki.ubuntu.com/Process/Merges/TestPlans/libreoffice [Regression Potential] * A minor release with a total of 72 bug fixes always carries the potential for introducing regressions, even though it is a bug-fix-only release, meaning that no new features were added, and no existing features were removed. * A combination of autopkgtests and careful smoke testing as described above should provide reasonable confidence that no regressions sneaked in. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1906684 Title: [SRU] libreoffice 6.4.7 for Focal Status in libreoffice package in Ubuntu: In Progress Bug description: [Impact] * LibreOffice 6.4.7 is in its seventh bug-fix release of the 6.4 line: https://wiki.documentfoundation.org/ReleasePlan/6.4#6.4.7_release * Version 6.4.6 is currently released in focal. For a list of fixed bugs compared to 6.4.6 see the list of bugs fixed in the two release candidates: https://wiki.documentfoundation.org/Releases/6.4.7/RC1 https://wiki.documentfoundation.org/Releases/6.4.7/RC2 (that's a total of 72 bugs) * Given the nature of the project, the complexity of the codebase and the high level of quality assurance upstream, it is preferable to SRU a minor release rather than cherry-pick selected bug fixes. [Testing] * Upstream testing. Bugs fixed upstream typically include unit/regression tests, a
[Desktop-packages] [Bug 1918729] [NEW] please sync qpdf 10.3.1-1 from debian experimental
Public bug reported: 10.3.1 includes a very small but important fix to a bug that would cause qpdf 10.3.0 to reject certain valid files when splitting pages. I also added a check for exceptions that will make future bugs of this type (if any) just generate warnings instead of blocking the whole operations in hopes of not needing to do any emergency releases any time soon even if this wasn't the "last bug." ** Affects: qpdf (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to qpdf in Ubuntu. https://bugs.launchpad.net/bugs/1918729 Title: please sync qpdf 10.3.1-1 from debian experimental Status in qpdf package in Ubuntu: New Bug description: 10.3.1 includes a very small but important fix to a bug that would cause qpdf 10.3.0 to reject certain valid files when splitting pages. I also added a check for exceptions that will make future bugs of this type (if any) just generate warnings instead of blocking the whole operations in hopes of not needing to do any emergency releases any time soon even if this wasn't the "last bug." To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qpdf/+bug/1918729/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1918725] Re: Ubuntu 21.04 QA Test - Nautilus Crashed during live session
This bug has been reported on the Ubuntu ISO testing tracker. A list of all reports related to this bug can be found here: http://iso.qa.ubuntu.com/qatracker/reports/bugs/1918725 ** Tags added: iso-testing -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1918725 Title: Ubuntu 21.04 QA Test - Nautilus Crashed during live session Status in nautilus package in Ubuntu: New Bug description: During live OS testing Nautilus crashed during the opening of the live desktop. Apport started and info could not be sent. Had a warning: Nautilus is old and out of date. I restarted Apport for this bug report. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: nautilus 1:3.38.2-1ubuntu1 ProcVersionSignature: Ubuntu 5.10.0-14.15-generic 5.10.11 Uname: Linux 5.10.0-14-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu60 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.460 CurrentDesktop: ubuntu:GNOME Date: Thu Mar 11 19:06:23 2021 GsettingsChanges: b'org.gnome.nautilus.window-state' b'maximized' b'true' LiveMediaBuild: Ubuntu 21.04 "Hirsute Hippo" - Alpha amd64 (20210311) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: evince3.39.2-1 file-roller 3.38.0-1 nautilus-extension-gnome-terminal 3.38.1-1ubuntu1 nautilus-share0.7.3-2ubuntu3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1918725/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1915677] Re: [ snap ] libreoffice-style-* packages are missing ?
** Changed in: libreoffice (Ubuntu) Status: New => In Progress ** Changed in: libreoffice (Ubuntu) Importance: Wishlist => High ** Changed in: libreoffice (Ubuntu) Assignee: (unassigned) => Heather Ellsworth (hellsworth) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1915677 Title: [ snap ] libreoffice-style-* packages are missing ? Status in libreoffice package in Ubuntu: In Progress Bug description: Hi, trying LibreOffice 7 as a snap on UbuntuBudgie 20.04. I generally use dark gtk theme style system wide - and some are available as snap ( Adapta ). I often use Papirus icons set - and those are also ( partly ) available as snap ( through Adpata gtk theme ). I can't see if the same choice exists while using LO as a snap : I can find some icons theme ( elementary, colibre, breeze, and so on ) but they all look designed for global light gtk themes. In other words icons in my LO are black on black. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1915677/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1918725] [NEW] Ubuntu 21.04 QA Test - Nautilus Crashed during live session
Public bug reported: During live OS testing Nautilus crashed during the opening of the live desktop. Apport started and info could not be sent. Had a warning: Nautilus is old and out of date. I restarted Apport for this bug report. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: nautilus 1:3.38.2-1ubuntu1 ProcVersionSignature: Ubuntu 5.10.0-14.15-generic 5.10.11 Uname: Linux 5.10.0-14-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu60 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.460 CurrentDesktop: ubuntu:GNOME Date: Thu Mar 11 19:06:23 2021 GsettingsChanges: b'org.gnome.nautilus.window-state' b'maximized' b'true' LiveMediaBuild: Ubuntu 21.04 "Hirsute Hippo" - Alpha amd64 (20210311) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: evince3.39.2-1 file-roller 3.38.0-1 nautilus-extension-gnome-terminal 3.38.1-1ubuntu1 nautilus-share0.7.3-2ubuntu3 ** Affects: nautilus (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug hirsute -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1918725 Title: Ubuntu 21.04 QA Test - Nautilus Crashed during live session Status in nautilus package in Ubuntu: New Bug description: During live OS testing Nautilus crashed during the opening of the live desktop. Apport started and info could not be sent. Had a warning: Nautilus is old and out of date. I restarted Apport for this bug report. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: nautilus 1:3.38.2-1ubuntu1 ProcVersionSignature: Ubuntu 5.10.0-14.15-generic 5.10.11 Uname: Linux 5.10.0-14-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu60 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.460 CurrentDesktop: ubuntu:GNOME Date: Thu Mar 11 19:06:23 2021 GsettingsChanges: b'org.gnome.nautilus.window-state' b'maximized' b'true' LiveMediaBuild: Ubuntu 21.04 "Hirsute Hippo" - Alpha amd64 (20210311) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: evince3.39.2-1 file-roller 3.38.0-1 nautilus-extension-gnome-terminal 3.38.1-1ubuntu1 nautilus-share0.7.3-2ubuntu3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1918725/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1915887] Re: systemd spams the syslog about lack of native systemd unit file
** Description changed: + [impact] + + systemd spams journal with log messages + + [test case] + + see journalctl output and search for msgs similar to those listed in + original description below + + [regression potential] + + any regession would likely result in logs incorrectly not logged when + detecting a problem such as lack of native unit file, or using /var/run. + + [scope] + + this is needed in f/g + + this is fixed upstream with commit https://salsa.debian.org/systemd- + team/systemd/-/commit/0c6d90f783093fc255e529f8a33b2ed2a8e6c2d6 from + debian, which is included in 247.3-2 and later so this is fixed in + hirsute already (in -proposed package). + + these log messages aren't present in b or earlier so aren't needed in + x/b + + [original description] + systemd in hirsute spams the syslog file several times per second about services lacking native systemd unit files. Two things should happen. 1) a systemd unit file ought to be created 2) systemd should be slowed down with regards to these messages Feb 17 02:02:48 ubuntu-devel kernel: [ 289.794825] systemd-sysv-generator[7105]: SysV service '/etc/init.d/n2n' lacks a native systemd unit file. Automatically generating a unit file for compatibility. Please update package to include a native systemd unit file, in order to make it more safe and robust. Feb 17 02:02:49 ubuntu-devel kernel: [ 290.165351] systemd-sysv-generator[7126]: SysV service '/etc/init.d/n2n' lacks a native systemd unit file. Automatically generating a unit file for compatibility. Please update package to include a native systemd unit file, in order to make it more safe and robust. Feb 17 02:02:49 ubuntu-devel kernel: [ 291.111278] systemd-sysv-generator[7170]: SysV service '/etc/init.d/n2n' lacks a native systemd unit file. Automatically generating a unit file for compatibility. Please update package to include a native systemd unit file, in order to make it more safe and robust. Feb 17 02:02:50 ubuntu-devel kernel: [ 291.507164] systemd-sysv-generator[7199]: SysV service '/etc/init.d/n2n' lacks a native systemd unit file. Automatically generating a unit file for compatibility. Please update package to include a native systemd unit file, in order to make it more safe and robust. Feb 17 02:05:57 ubuntu-devel kernel: [ 478.386062] systemd-sysv-generator[9909]: SysV service '/etc/init.d/fam' lacks a native systemd unit file. Automatically generating a unit file for compatibility. Please update package to include a native systemd unit file, in order to make it more safe and robust. Feb 17 02:05:57 ubuntu-devel kernel: [ 478.386321] systemd-sysv-generator[9909]: SysV service '/etc/init.d/xl2tpd' lacks a native systemd unit file. Automatically generating a unit file for compatibility. Please update package to include a native systemd unit file, in order to make it more safe and robust. Feb 17 02:05:57 ubuntu-devel kernel: [ 478.386742] systemd-sysv-generator[9909]: SysV service '/etc/init.d/ipfm' lacks a native systemd unit file. Automatically generating a unit file for compatibility. Please update package to include a native systemd unit file, in order to make it more safe and robust. Feb 17 02:05:57 ubuntu-devel kernel: [ 478.386767] systemd-sysv-generator[9909]: SysV service '/etc/init.d/shadowsocks' lacks a native systemd unit file. Automatically generating a unit file for compatibility. Please update package to include a native systemd unit file, in order to make it more safe and robust. Feb 17 02:05:57 ubuntu-devel kernel: [ 478.387281] systemd-sysv-generator[9909]: SysV service '/etc/init.d/virtualbox' lacks a native systemd unit file. Automatically generating a unit file for compatibility. Please update package to include a native systemd unit file, in order to make it more safe and robust. Feb 17 02:05:57 ubuntu-devel kernel: [ 478.388931] systemd-sysv-generator[9909]: SysV service '/etc/init.d/sysfsutils' lacks a native systemd unit file. Automatically generating a unit file for compatibility. Please update package to include a native systemd unit file, in order to make it more safe and robust. Feb 17 02:05:57 ubuntu-devel kernel: [ 478.388955] systemd-sysv-generator[9909]: SysV service '/etc/init.d/apport' lacks a native systemd unit file. Automatically generating a unit file for compatibility. Please update package to include a native systemd unit file, in order to make it more safe and robust. Feb 17 02:05:57 ubuntu-devel kernel: [ 478.389412] systemd-sysv-generator[9909]: SysV service '/etc/init.d/freeradius' lacks a native systemd unit file. Automatically generating a unit file for compatibility. Please update package to include a native systemd unit file, in order to make it more safe and robust. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to sysfsutils in Ubuntu. https://bugs.launchpad.net/bugs/191
[Desktop-packages] [Bug 1916272] Re: Patch prefer_pthreads breaks Eclipse
Thanks Sebastien. Further investigation allowed us to identify a race condition. It happened to be observed less without the patch but it was still present. We were able to identify it to be specific to Eclipse. ** Changed in: webkit2gtk (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to webkit2gtk in Ubuntu. https://bugs.launchpad.net/bugs/1916272 Title: Patch prefer_pthreads breaks Eclipse Status in webkit2gtk package in Ubuntu: Invalid Bug description: There is a patch in the Debian/Ubuntu specific build: debian/patches/prefer_pthread.patch I've identified this patch to be problematic. It causes deadlocks/freezes of the Eclipse UI. Building webkit2gtk without this patch makes Eclipse happy. https://bugs.eclipse.org/567881 https://gist.github.com/guw/30bc8b14756e364c3d158fababbbd62d It seems that this change was introduced to fix a problem on a very specific architecture. https://salsa.debian.org/webkit-team/webkit/-/commit/5d1dec1e544b1277e1b97ccf80de647ba9e4465b The patch should likely by targeted to that specific architecture only. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/webkit2gtk/+bug/1916272/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1918578] Re: Chromium Crashes When Triggering File Dialog
Can you please share the output of the following commands? snap list snap connections chromium ** Changed in: chromium-browser (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1918578 Title: Chromium Crashes When Triggering File Dialog Status in chromium-browser package in Ubuntu: Incomplete Bug description: I've installed Chromium via Snap. Chromium seems to crash any time it triggers a native file dialog. This can be replicated by doing "Save file as", "Save image as" or simply doing CTRL+O to open a local web page. I've launched it from the terminal to see if it has any prints. Here's what I've got *before* the crash: ```plain /home/erayerdin/snap/chromium/common/.cache/gio-modules/libdconfsettings.so: cannot open shared object file: No such file or directory Failed to load module: /home/erayerdin/snap/chromium/common/.cache/gio-modules/libdconfsettings.so /home/erayerdin/snap/chromium/common/.cache/gio-modules/libgiognomeproxy.so: cannot open shared object file: No such file or directory Failed to load module: /home/erayerdin/snap/chromium/common/.cache/gio-modules/libgiognomeproxy.so /home/erayerdin/snap/chromium/common/.cache/gio-modules/libgiolibproxy.so: cannot open shared object file: No such file or directory Failed to load module: /home/erayerdin/snap/chromium/common/.cache/gio-modules/libgiolibproxy.so /home/erayerdin/snap/chromium/common/.cache/gio-modules/libgiognutls.so: cannot open shared object file: No such file or directory Failed to load module: /home/erayerdin/snap/chromium/common/.cache/gio-modules/libgiognutls.so Gtk-Message: 08:07:49.139: Failed to load module "appmenu-gtk-module" (chrome:6811): Gtk-WARNING **: 08:07:52.019: /snap/chromium/1514 /gnome-platform/usr/lib/x86_64-linux-gnu/gtk-3.0/3.0.0/immodules/im- ibus.so: cannot open shared object file: No such file or directory (chrome:6811): Gtk-WARNING **: 08:07:52.019: Loading IM context type 'ibus' failed (chrome:6811): Gtk-WARNING **: 08:07:57.896: Could not load a pixbuf from icon theme. This may indicate that pixbuf loaders or the mime database could not be found. ``` Here's what I've got *when* it crashed: ```plain Gtk:ERROR:../../../../gtk/gtkiconhelper.c:494:ensure_surface_for_gicon: assertion failed (error == NULL): Failed to load /snap/chromium/1506/data-dir/icons/Adwaita/16x16/status/image-missing.png: Unable to load image-loading module: /snap/chromium/1514/gnome-platform/usr/lib/x86_64-linux-gnu/gdk-pixbuf-2.0/2.10.0/loaders/libpixbufloader-png.so: /snap/chromium/1514/gnome-platform/usr/lib/x86_64-linux-gnu/gdk-pixbuf-2.0/2.10.0/loaders/libpixbufloader-png.so: cannot open shared object file: No such file or directory (gdk-pixbuf-error-quark, 5) Aborted (core dumped) ``` What is the issue here? How can I resolve this? *** # Environment - Kubuntu 20.04.2 - Chromium 89.0.4389.72 (Official Build) snap (64-bit) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1918578/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1908930] Re: libwebkit2gtk-4.0-37 missing files break epiphany
Thank you for your bug report. Could you give detailled steps to trigger the issue? Did it start after an upgrade? ** Changed in: webkit2gtk (Ubuntu) Importance: Undecided => High ** Changed in: webkit2gtk (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to webkit2gtk in Ubuntu. https://bugs.launchpad.net/bugs/1908930 Title: libwebkit2gtk-4.0-37 missing files break epiphany Status in webkit2gtk package in Ubuntu: Incomplete Bug description: libwebkit2gtk-4.0-37 version 2.30.3-0ubuntu0.18.04.1 comes without WebKitPluginProcess (should be under /usr/lib/x86_64-linux- gnu/webkit2gtk-4.0). Similarly /usr/lib/x86_64-linux- gnu/webkit2gtk-4.0/WebKitStorageProcess is missing. If I try to follow a link to a pdf file in epiphany (epiphany-browser 3.28.1-1ubuntu1) it crashes. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/webkit2gtk/+bug/1908930/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1916272] Re: Patch prefer_pthreads breaks Eclipse
Thank you for your bug report, is there any chance you could report the issue to Debian since the patch comes from there? ** Changed in: webkit2gtk (Ubuntu) Importance: Undecided => High -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to webkit2gtk in Ubuntu. https://bugs.launchpad.net/bugs/1916272 Title: Patch prefer_pthreads breaks Eclipse Status in webkit2gtk package in Ubuntu: New Bug description: There is a patch in the Debian/Ubuntu specific build: debian/patches/prefer_pthread.patch I've identified this patch to be problematic. It causes deadlocks/freezes of the Eclipse UI. Building webkit2gtk without this patch makes Eclipse happy. https://bugs.eclipse.org/567881 https://gist.github.com/guw/30bc8b14756e364c3d158fababbbd62d It seems that this change was introduced to fix a problem on a very specific architecture. https://salsa.debian.org/webkit-team/webkit/-/commit/5d1dec1e544b1277e1b97ccf80de647ba9e4465b The patch should likely by targeted to that specific architecture only. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/webkit2gtk/+bug/1916272/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1851621] Re: [snap] No KDE file dialogs
I am using Kubuntu 20.10 and this is affecting me as well. It's very weird to have to use Gtk file picker in KDE plasma. I wouldn't mind an additional 60 MB to have this fixed. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1851621 Title: [snap] No KDE file dialogs Status in chromium-browser package in Ubuntu: Confirmed Bug description: I upgraded from kubuntu 19.04 to 19.10 and noticed that chromium does not integrate anymore. Plasma integration Fails to connect to the native host (suggested google solutions didn't work), Kubuntu mouse pointers change to ugly ones (I bellive GTK fallback), no kde file dialog when opening/saving files. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1851621/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1918336] Re: Sync gnome-remote-desktop 0.1.9-5 (main) from Debian unstable (main)
This bug was fixed in the package gnome-remote-desktop - 0.1.9-5 Sponsored for fossfreedom (fossfreedom) --- gnome-remote-desktop (0.1.9-5) unstable; urgency=medium * Team upload [ David Mohammed ] * debian/control: add budgie-desktop as an alternate for gnome-shell (Closes: #982937) -- Simon McVittie Tue, 09 Mar 2021 10:31:04 + ** Changed in: gnome-remote-desktop (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-remote-desktop in Ubuntu. https://bugs.launchpad.net/bugs/1918336 Title: Sync gnome-remote-desktop 0.1.9-5 (main) from Debian unstable (main) Status in gnome-remote-desktop package in Ubuntu: Fix Released Bug description: Please sync gnome-remote-desktop 0.1.9-5 (main) from Debian unstable (main) Changelog entries since current hirsute version 0.1.9-4build1: gnome-remote-desktop (0.1.9-5) unstable; urgency=medium * Team upload [ David Mohammed ] * debian/control: add budgie-desktop as an alternate for gnome-shell (Closes: #982937) -- Simon McVittie Tue, 09 Mar 2021 10:31:04 + To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-remote-desktop/+bug/1918336/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 844582] Re: "Invalid argument" when trying to scan
I then tried the next suggestion:
scanimage -x 210 --mode=Color --resolution=300 --batch
and this succeeded. If I attach the '--log=' option to this command
line, will that generate any useful information?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to sane-backends in Ubuntu.
https://bugs.launchpad.net/bugs/844582
Title:
"Invalid argument" when trying to scan
Status in gscan2pdf package in Ubuntu:
Invalid
Status in sane-backends package in Ubuntu:
Opinion
Bug description:
I'm using a Fujitsu M3091DCd scanner with SANE. From the command line
it works more or less well with Ubuntu.
I can't use it with gscan2pdf v0.9.31, but gscan2pdf works with
another scanner.
All I get is a meaningless "Invalid argument" when I hit the scan
button.
When I start gscan2pdf from the command line I see these lines
appearing when I hit the scan button:
Error running process: Died at (eval 39) line 7.
$device->start;
$shash{$sane_thread}{status} = $Sane::STATUS+0;
if ($Sane::STATUS != SANE_STATUS_GOOD) {
print "$prog_name: sane_start: $Sane::STATUS\n" if $debug;
$shash{$sane_thread}{go} = 0;
die; # quickest way out of the eval block
}
my $path = $shash{$sane_thread}{data};
if (not open($fh, ">", $path)) {
$device->cancel;
$shash{$sane_thread}{status} = SANE_STATUS_ACCESS_DENIED;
$shash{$sane_thread}{go} = 0;
die; # quickest way out of the eval block
}
scan_page($device, $fh);
$shash{$sane_thread}{status} = $Sane::STATUS+0;
close $fh;
printf "Scanned page %s.", $path if $debug;
printf " (scanner status = %d)\n", $Sane::STATUS if $debug;
$shash{$sane_thread}{status} = $Sane::STATUS+0;
$shash{$sane_thread}{go} = 0;
ProblemType: Bug
DistroRelease: Ubuntu 11.04
Package: gscan2pdf 0.9.31-2
ProcVersionSignature: Ubuntu 2.6.38-11.48-generic 2.6.38.8
Uname: Linux 2.6.38-11-generic x86_64
NonfreeKernelModules: fglrx
Architecture: amd64
Date: Thu Sep 8 09:44:25 2011
PackageArchitecture: all
ProcEnviron:
LANGUAGE=
PATH=(custom, no username)
LANG=en_US.UTF-8
SHELL=/bin/bash
SourcePackage: gscan2pdf
UpgradeStatus: Upgraded to natty on 2011-06-01 (98 days ago)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gscan2pdf/+bug/844582/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 844582] Re: "Invalid argument" when trying to scan
Apologies for the slow response. Please find attached the requested log
file.
** Attachment added: "The requested file, 'log.xz'."
https://bugs.launchpad.net/ubuntu/+source/gscan2pdf/+bug/844582/+attachment/5475860/+files/log.xz
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to sane-backends in Ubuntu.
https://bugs.launchpad.net/bugs/844582
Title:
"Invalid argument" when trying to scan
Status in gscan2pdf package in Ubuntu:
Invalid
Status in sane-backends package in Ubuntu:
Opinion
Bug description:
I'm using a Fujitsu M3091DCd scanner with SANE. From the command line
it works more or less well with Ubuntu.
I can't use it with gscan2pdf v0.9.31, but gscan2pdf works with
another scanner.
All I get is a meaningless "Invalid argument" when I hit the scan
button.
When I start gscan2pdf from the command line I see these lines
appearing when I hit the scan button:
Error running process: Died at (eval 39) line 7.
$device->start;
$shash{$sane_thread}{status} = $Sane::STATUS+0;
if ($Sane::STATUS != SANE_STATUS_GOOD) {
print "$prog_name: sane_start: $Sane::STATUS\n" if $debug;
$shash{$sane_thread}{go} = 0;
die; # quickest way out of the eval block
}
my $path = $shash{$sane_thread}{data};
if (not open($fh, ">", $path)) {
$device->cancel;
$shash{$sane_thread}{status} = SANE_STATUS_ACCESS_DENIED;
$shash{$sane_thread}{go} = 0;
die; # quickest way out of the eval block
}
scan_page($device, $fh);
$shash{$sane_thread}{status} = $Sane::STATUS+0;
close $fh;
printf "Scanned page %s.", $path if $debug;
printf " (scanner status = %d)\n", $Sane::STATUS if $debug;
$shash{$sane_thread}{status} = $Sane::STATUS+0;
$shash{$sane_thread}{go} = 0;
ProblemType: Bug
DistroRelease: Ubuntu 11.04
Package: gscan2pdf 0.9.31-2
ProcVersionSignature: Ubuntu 2.6.38-11.48-generic 2.6.38.8
Uname: Linux 2.6.38-11-generic x86_64
NonfreeKernelModules: fglrx
Architecture: amd64
Date: Thu Sep 8 09:44:25 2011
PackageArchitecture: all
ProcEnviron:
LANGUAGE=
PATH=(custom, no username)
LANG=en_US.UTF-8
SHELL=/bin/bash
SourcePackage: gscan2pdf
UpgradeStatus: Upgraded to natty on 2011-06-01 (98 days ago)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gscan2pdf/+bug/844582/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1918613] Re: [FFe] GDM background configurable with gsettings
Having the schema in GDM was our initial proposal but you told us that it would be better to do it the way we just proposed and do it in an independent schema as long as it is not yet accepted upsteam. In both cases there will be a migration *if* something similar is ever implemented in gnome-shell. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1918613 Title: [FFe] GDM background configurable with gsettings Status in gnome-shell package in Ubuntu: New Bug description: [Description] Customization of the greeter is a requirement from Corporate customers. Currently the background (plain color or image) of the greeter is hard coded in the style embedded in the theme. Customizing this background requires to extract the style sheet from gnome-shell gresource file, modify it manually, recompile and deploy the new gresource, and add an alternative to it. This feature adds 4 gsettings keys to make the background of the greeter configurable via gsettings. The default value defined the in the theme is used for keys that are not set. [Rationale] Corporate customers use LTS releases. This changeset needs to land in hirsute before it can be SRUd into prior Ubuntu LTS releases. So we would like to submit this FFe to get it into Hirsute first. [Risks] The changeset is minimal, isolated and can be easily reverted. In case of error in the code, GDM will fail to load and it will be immediately visible. [Build] Builds and tested successfully locally. Besides the updated JS is not compiled as part of build. [Upstream Issue] https://gitlab.gnome.org/GNOME/gdm/-/issues/684 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1918613/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1918613] Re: [FFe] GDM background configurable with gsettings
Not sure if the gsettings schema change should be part of gdm though, as if this will ever be upstreamed that's where it will belong. Indeed, it will makes the FFe a bit more complex and cause more changes though, but we'd get there anyways when (if) we'll have to migrate to gnome keys. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1918613 Title: [FFe] GDM background configurable with gsettings Status in gnome-shell package in Ubuntu: New Bug description: [Description] Customization of the greeter is a requirement from Corporate customers. Currently the background (plain color or image) of the greeter is hard coded in the style embedded in the theme. Customizing this background requires to extract the style sheet from gnome-shell gresource file, modify it manually, recompile and deploy the new gresource, and add an alternative to it. This feature adds 4 gsettings keys to make the background of the greeter configurable via gsettings. The default value defined the in the theme is used for keys that are not set. [Rationale] Corporate customers use LTS releases. This changeset needs to land in hirsute before it can be SRUd into prior Ubuntu LTS releases. So we would like to submit this FFe to get it into Hirsute first. [Risks] The changeset is minimal, isolated and can be easily reverted. In case of error in the code, GDM will fail to load and it will be immediately visible. [Build] Builds and tested successfully locally. Besides the updated JS is not compiled as part of build. [Upstream Issue] https://gitlab.gnome.org/GNOME/gdm/-/issues/684 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1918613/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1918666] Re: Cannot close the modal "Connect to Wifi" window to return to desktop
** Description changed: When I select the task bar menu, click on the Wifi and select "Select to network", a modal window appears that allows me to select a Wifi network. - Normally, when I click Cancel or Connect, the modal window disappears - and returns me to the desktop. + After I have clicked on one of the networks, normally, when I click + Cancel or Connect, the modal window disappears and returns me to the + desktop. With the current gnome-shell, this modal window persists and I cannot - access the desktop - this is both in Wayland and in X. + access the desktop - this is both in Wayland and in X. Connect doesn't + seem to work - it's like the buttons are no longer accepting clicks. The + ESC key also doesn't do anything. (If I don't click on a network, the + ESC key does work, and so does Cancel.) I think I once managed to get Alt-Ctrl-F1 to bring back the GDM login window, but the modal window was still there when I went back into the desktop. Alt-F2 didn't work so I couldn't try re-starting gnome-shell. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: gnome-shell 3.38.3-3ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-11.12-generic 5.11.0 Uname: Linux 5.11.0-11-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu60 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Thu Mar 11 20:35:24 2021 DisplayManager: gdm3 RelatedPackageVersions: mutter-common 3.38.3-3ubuntu2 SourcePackage: gnome-shell UpgradeStatus: Upgraded to hirsute on 2021-02-24 (15 days ago) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1918666 Title: Cannot close the modal "Connect to Wifi" window to return to desktop Status in gnome-shell package in Ubuntu: New Bug description: When I select the task bar menu, click on the Wifi and select "Select to network", a modal window appears that allows me to select a Wifi network. After I have clicked on one of the networks, normally, when I click Cancel or Connect, the modal window disappears and returns me to the desktop. With the current gnome-shell, this modal window persists and I cannot access the desktop - this is both in Wayland and in X. Connect doesn't seem to work - it's like the buttons are no longer accepting clicks. The ESC key also doesn't do anything. (If I don't click on a network, the ESC key does work, and so does Cancel.) I think I once managed to get Alt-Ctrl-F1 to bring back the GDM login window, but the modal window was still there when I went back into the desktop. Alt-F2 didn't work so I couldn't try re-starting gnome-shell. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: gnome-shell 3.38.3-3ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-11.12-generic 5.11.0 Uname: Linux 5.11.0-11-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu60 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Thu Mar 11 20:35:24 2021 DisplayManager: gdm3 RelatedPackageVersions: mutter-common 3.38.3-3ubuntu2 SourcePackage: gnome-shell UpgradeStatus: Upgraded to hirsute on 2021-02-24 (15 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1918666/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1918666] [NEW] Cannot close the modal "Connect to Wifi" window to return to desktop
Public bug reported: When I select the task bar menu, click on the Wifi and select "Select to network", a modal window appears that allows me to select a Wifi network. After I have clicked on one of the networks, normally, when I click Cancel or Connect, the modal window disappears and returns me to the desktop. With the current gnome-shell, this modal window persists and I cannot access the desktop - this is both in Wayland and in X. Connect doesn't seem to work - it's like the buttons are no longer accepting clicks. The ESC key also doesn't do anything. (If I don't click on a network, the ESC key does work, and so does Cancel.) I think I once managed to get Alt-Ctrl-F1 to bring back the GDM login window, but the modal window was still there when I went back into the desktop. Alt-F2 didn't work so I couldn't try re-starting gnome-shell. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: gnome-shell 3.38.3-3ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-11.12-generic 5.11.0 Uname: Linux 5.11.0-11-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu60 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Thu Mar 11 20:35:24 2021 DisplayManager: gdm3 RelatedPackageVersions: mutter-common 3.38.3-3ubuntu2 SourcePackage: gnome-shell UpgradeStatus: Upgraded to hirsute on 2021-02-24 (15 days ago) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug hirsute wayland-session -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1918666 Title: Cannot close the modal "Connect to Wifi" window to return to desktop Status in gnome-shell package in Ubuntu: New Bug description: When I select the task bar menu, click on the Wifi and select "Select to network", a modal window appears that allows me to select a Wifi network. After I have clicked on one of the networks, normally, when I click Cancel or Connect, the modal window disappears and returns me to the desktop. With the current gnome-shell, this modal window persists and I cannot access the desktop - this is both in Wayland and in X. Connect doesn't seem to work - it's like the buttons are no longer accepting clicks. The ESC key also doesn't do anything. (If I don't click on a network, the ESC key does work, and so does Cancel.) I think I once managed to get Alt-Ctrl-F1 to bring back the GDM login window, but the modal window was still there when I went back into the desktop. Alt-F2 didn't work so I couldn't try re-starting gnome-shell. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: gnome-shell 3.38.3-3ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-11.12-generic 5.11.0 Uname: Linux 5.11.0-11-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu60 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Thu Mar 11 20:35:24 2021 DisplayManager: gdm3 RelatedPackageVersions: mutter-common 3.38.3-3ubuntu2 SourcePackage: gnome-shell UpgradeStatus: Upgraded to hirsute on 2021-02-24 (15 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1918666/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1918658] [NEW] Display glitches when showing context menu
Public bug reported: I am using Android Studio to develop Applications. When i have lots of windows opened and i try to open a context menu or write code, it shows a frame of some applications that are below the current window. In the video it is more clear. I don't know if this is a problem related to Ubuntu or Android Studio but it is very noisy. In this case it is clear that the frame shown belongs to the Arduino window that is open under it. Sometimes i can see frames of my wallpaper (when i don't have any window under it) or others. This problem doesn't happen with other programs (for now). ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.8.0-44.50~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-44-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: [Errno 21] È una directory: '/proc/driver/nvidia/capabilities/gpu0' .proc.driver.nvidia.capabilities.mig: Error: [Errno 21] È una directory: '/proc/driver/nvidia/capabilities/mig' .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] È una directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 460.39 Thu Jan 21 21:54:06 UTC 2021 GCC version: gcc version 9.3.0 (Ubuntu 9.3.0-17ubuntu1~20.04) ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 BootLog: Error: [Errno 13] Permesso negato: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Mar 11 13:07:11 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: nvidia, 460.39, 5.8.0-43-generic, x86_64: installed nvidia, 460.39, 5.8.0-44-generic, x86_64: installed virtualbox, 6.1.16, 5.8.0-44-generic, x86_64: installed GraphicsCard: NVIDIA Corporation GP104 [GeForce GTX 1080] [10de:1b80] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] GP104 [GeForce GTX 1080] [1462:3362] InstallationDate: Installed on 2021-01-17 (52 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: Micro-Star International Co., Ltd. MS-7B45 ProcEnviron: LANGUAGE=it PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-44-generic root=UUID=34f5f1d0-f244-447f-8b6b-1ec5c14fe8f6 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/05/2020 dmi.bios.release: 5.12 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: A.B0 dmi.board.asset.tag: Default string dmi.board.name: Z370 GAMING PRO CARBON (MS-7B45) dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: 2.0 dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: 2.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrA.B0:bd06/05/2020:br5.12:svnMicro-StarInternationalCo.,Ltd.:pnMS-7B45:pvr2.0:rvnMicro-StarInternationalCo.,Ltd.:rnZ370GAMINGPROCARBON(MS-7B45):rvr2.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr2.0: dmi.product.family: Default string dmi.product.name: MS-7B45 dmi.product.sku: Default string dmi.product.version: 2.0 dmi.sys.vendor: Micro-Star International Co., Ltd. version.compiz: compiz 1:0.9.14.1+20.04.20200211-0ubuntu1 version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ubuntu ** Attachment added: "A video of this glitch" https://bugs.launchpad.net/bugs/1918658/+attachment/5475814/+files/2021-03-11_13-05-40.mov -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1918658 Title: Display glitches when showing context menu Status in xorg package in Ubuntu: New Bug description: I am using Android Studio to develop Applications. When i have lots of windows opened and i try to open a context menu or write code, it shows a frame of some applications that are below the current window. In the video it is more clear. I don't know if this is a problem
[Desktop-packages] [Bug 1915887] Re: systemd spams the syslog about lack of native systemd unit file
Also: setting all the other tasks to Invalid as there's noting wrong with them; the issue (and the fix) belong to systemd. ** Changed in: apport (Ubuntu) Status: Incomplete => Invalid ** Changed in: systemd (Ubuntu) Importance: Undecided => Low ** Changed in: fam (Ubuntu) Status: Incomplete => Invalid ** Changed in: freeradius (Ubuntu) Status: Incomplete => Invalid ** Changed in: ipfm (Ubuntu) Status: Incomplete => Invalid ** Changed in: n2n (Ubuntu) Status: Incomplete => Invalid ** Changed in: pfm (Ubuntu) Status: Incomplete => Invalid ** Changed in: shadowsocks (Ubuntu) Status: Incomplete => Invalid ** Changed in: sysfsutils (Ubuntu) Status: Incomplete => Invalid ** Changed in: virtualbox (Ubuntu) Status: Incomplete => Invalid ** Changed in: xl2tpd (Ubuntu) Status: Incomplete => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to sysfsutils in Ubuntu. https://bugs.launchpad.net/bugs/1915887 Title: systemd spams the syslog about lack of native systemd unit file Status in apport package in Ubuntu: Invalid Status in fam package in Ubuntu: Invalid Status in freeradius package in Ubuntu: Invalid Status in ipfm package in Ubuntu: Invalid Status in n2n package in Ubuntu: Invalid Status in pfm package in Ubuntu: Invalid Status in shadowsocks package in Ubuntu: Invalid Status in sysfsutils package in Ubuntu: Invalid Status in systemd package in Ubuntu: Fix Committed Status in virtualbox package in Ubuntu: Invalid Status in xl2tpd package in Ubuntu: Invalid Status in systemd package in Debian: Fix Released Bug description: systemd in hirsute spams the syslog file several times per second about services lacking native systemd unit files. Two things should happen. 1) a systemd unit file ought to be created 2) systemd should be slowed down with regards to these messages Feb 17 02:02:48 ubuntu-devel kernel: [ 289.794825] systemd-sysv-generator[7105]: SysV service '/etc/init.d/n2n' lacks a native systemd unit file. Automatically generating a unit file for compatibility. Please update package to include a native systemd unit file, in order to make it more safe and robust. Feb 17 02:02:49 ubuntu-devel kernel: [ 290.165351] systemd-sysv-generator[7126]: SysV service '/etc/init.d/n2n' lacks a native systemd unit file. Automatically generating a unit file for compatibility. Please update package to include a native systemd unit file, in order to make it more safe and robust. Feb 17 02:02:49 ubuntu-devel kernel: [ 291.111278] systemd-sysv-generator[7170]: SysV service '/etc/init.d/n2n' lacks a native systemd unit file. Automatically generating a unit file for compatibility. Please update package to include a native systemd unit file, in order to make it more safe and robust. Feb 17 02:02:50 ubuntu-devel kernel: [ 291.507164] systemd-sysv-generator[7199]: SysV service '/etc/init.d/n2n' lacks a native systemd unit file. Automatically generating a unit file for compatibility. Please update package to include a native systemd unit file, in order to make it more safe and robust. Feb 17 02:05:57 ubuntu-devel kernel: [ 478.386062] systemd-sysv-generator[9909]: SysV service '/etc/init.d/fam' lacks a native systemd unit file. Automatically generating a unit file for compatibility. Please update package to include a native systemd unit file, in order to make it more safe and robust. Feb 17 02:05:57 ubuntu-devel kernel: [ 478.386321] systemd-sysv-generator[9909]: SysV service '/etc/init.d/xl2tpd' lacks a native systemd unit file. Automatically generating a unit file for compatibility. Please update package to include a native systemd unit file, in order to make it more safe and robust. Feb 17 02:05:57 ubuntu-devel kernel: [ 478.386742] systemd-sysv-generator[9909]: SysV service '/etc/init.d/ipfm' lacks a native systemd unit file. Automatically generating a unit file for compatibility. Please update package to include a native systemd unit file, in order to make it more safe and robust. Feb 17 02:05:57 ubuntu-devel kernel: [ 478.386767] systemd-sysv-generator[9909]: SysV service '/etc/init.d/shadowsocks' lacks a native systemd unit file. Automatically generating a unit file for compatibility. Please update package to include a native systemd unit file, in order to make it more safe and robust. Feb 17 02:05:57 ubuntu-devel kernel: [ 478.387281] systemd-sysv-generator[9909]: SysV service '/etc/init.d/virtualbox' lacks a native systemd unit file. Automatically generating a unit file for compatibility. Please update package to include a native systemd unit file, in order to make it more safe and robust. Feb 17 02:05:57 ubuntu-devel kernel: [ 478.388931] systemd-sysv-generator[9909]: SysV service '/etc/init.d/sysfsutils' lacks a native systemd unit file. Automatically generating a unit
[Desktop-packages] [Bug 1915887] Re: systemd spams the syslog about lack of native systemd unit file
Fixed in Debian with the introduction of a new quilt patch: https://salsa.debian.org/systemd- team/systemd/-/commit/0c6d90f783093fc255e529f8a33b2ed2a8e6c2d6 Counting this as Fix Committed. ** Changed in: systemd (Ubuntu) Status: Incomplete => Fix Committed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to sysfsutils in Ubuntu. https://bugs.launchpad.net/bugs/1915887 Title: systemd spams the syslog about lack of native systemd unit file Status in apport package in Ubuntu: Invalid Status in fam package in Ubuntu: Invalid Status in freeradius package in Ubuntu: Invalid Status in ipfm package in Ubuntu: Invalid Status in n2n package in Ubuntu: Invalid Status in pfm package in Ubuntu: Invalid Status in shadowsocks package in Ubuntu: Invalid Status in sysfsutils package in Ubuntu: Invalid Status in systemd package in Ubuntu: Fix Committed Status in virtualbox package in Ubuntu: Invalid Status in xl2tpd package in Ubuntu: Invalid Status in systemd package in Debian: Fix Released Bug description: systemd in hirsute spams the syslog file several times per second about services lacking native systemd unit files. Two things should happen. 1) a systemd unit file ought to be created 2) systemd should be slowed down with regards to these messages Feb 17 02:02:48 ubuntu-devel kernel: [ 289.794825] systemd-sysv-generator[7105]: SysV service '/etc/init.d/n2n' lacks a native systemd unit file. Automatically generating a unit file for compatibility. Please update package to include a native systemd unit file, in order to make it more safe and robust. Feb 17 02:02:49 ubuntu-devel kernel: [ 290.165351] systemd-sysv-generator[7126]: SysV service '/etc/init.d/n2n' lacks a native systemd unit file. Automatically generating a unit file for compatibility. Please update package to include a native systemd unit file, in order to make it more safe and robust. Feb 17 02:02:49 ubuntu-devel kernel: [ 291.111278] systemd-sysv-generator[7170]: SysV service '/etc/init.d/n2n' lacks a native systemd unit file. Automatically generating a unit file for compatibility. Please update package to include a native systemd unit file, in order to make it more safe and robust. Feb 17 02:02:50 ubuntu-devel kernel: [ 291.507164] systemd-sysv-generator[7199]: SysV service '/etc/init.d/n2n' lacks a native systemd unit file. Automatically generating a unit file for compatibility. Please update package to include a native systemd unit file, in order to make it more safe and robust. Feb 17 02:05:57 ubuntu-devel kernel: [ 478.386062] systemd-sysv-generator[9909]: SysV service '/etc/init.d/fam' lacks a native systemd unit file. Automatically generating a unit file for compatibility. Please update package to include a native systemd unit file, in order to make it more safe and robust. Feb 17 02:05:57 ubuntu-devel kernel: [ 478.386321] systemd-sysv-generator[9909]: SysV service '/etc/init.d/xl2tpd' lacks a native systemd unit file. Automatically generating a unit file for compatibility. Please update package to include a native systemd unit file, in order to make it more safe and robust. Feb 17 02:05:57 ubuntu-devel kernel: [ 478.386742] systemd-sysv-generator[9909]: SysV service '/etc/init.d/ipfm' lacks a native systemd unit file. Automatically generating a unit file for compatibility. Please update package to include a native systemd unit file, in order to make it more safe and robust. Feb 17 02:05:57 ubuntu-devel kernel: [ 478.386767] systemd-sysv-generator[9909]: SysV service '/etc/init.d/shadowsocks' lacks a native systemd unit file. Automatically generating a unit file for compatibility. Please update package to include a native systemd unit file, in order to make it more safe and robust. Feb 17 02:05:57 ubuntu-devel kernel: [ 478.387281] systemd-sysv-generator[9909]: SysV service '/etc/init.d/virtualbox' lacks a native systemd unit file. Automatically generating a unit file for compatibility. Please update package to include a native systemd unit file, in order to make it more safe and robust. Feb 17 02:05:57 ubuntu-devel kernel: [ 478.388931] systemd-sysv-generator[9909]: SysV service '/etc/init.d/sysfsutils' lacks a native systemd unit file. Automatically generating a unit file for compatibility. Please update package to include a native systemd unit file, in order to make it more safe and robust. Feb 17 02:05:57 ubuntu-devel kernel: [ 478.388955] systemd-sysv-generator[9909]: SysV service '/etc/init.d/apport' lacks a native systemd unit file. Automatically generating a unit file for compatibility. Please update package to include a native systemd unit file, in order to make it more safe and robust. Feb 17 02:05:57 ubuntu-devel kernel: [ 478.389412] systemd-sysv-generator[9909]: SysV service '/etc/init.d/freeradius' lacks a native systemd unit file. Automatically g
[Desktop-packages] [Bug 1918613] Re: [FFe] GDM background configurable with gsettings
** Description changed: [Description] Customization of the greeter is a requirement from Corporate customers. Currently the background (plain color or image) of the greeter is hard coded in the style embedded in the theme. Customizing this background requires to extract the style sheet from gnome-shell gresource file, modify it manually, recompile and deploy the new gresource, and add an alternative to it. This feature adds 4 gsettings keys to make the background of the greeter configurable via gsettings. The default value defined the in the theme is used for keys that are not set. [Rationale] Corporate customers use LTS releases. This changeset needs to land in hirsute before it can be SRUd into prior Ubuntu LTS releases. So we would like to submit this FFe to get it into Hirsute first. [Risks] The changeset is minimal, isolated and can be easily reverted. In case of error in the code, GDM will fail to load and it will be immediately visible. [Build] Builds and tested successfully locally. Besides the updated JS is not compiled as part of build. + + [Upstream Issue] + https://gitlab.gnome.org/GNOME/gdm/-/issues/684 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1918613 Title: [FFe] GDM background configurable with gsettings Status in gnome-shell package in Ubuntu: New Bug description: [Description] Customization of the greeter is a requirement from Corporate customers. Currently the background (plain color or image) of the greeter is hard coded in the style embedded in the theme. Customizing this background requires to extract the style sheet from gnome-shell gresource file, modify it manually, recompile and deploy the new gresource, and add an alternative to it. This feature adds 4 gsettings keys to make the background of the greeter configurable via gsettings. The default value defined the in the theme is used for keys that are not set. [Rationale] Corporate customers use LTS releases. This changeset needs to land in hirsute before it can be SRUd into prior Ubuntu LTS releases. So we would like to submit this FFe to get it into Hirsute first. [Risks] The changeset is minimal, isolated and can be easily reverted. In case of error in the code, GDM will fail to load and it will be immediately visible. [Build] Builds and tested successfully locally. Besides the updated JS is not compiled as part of build. [Upstream Issue] https://gitlab.gnome.org/GNOME/gdm/-/issues/684 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1918613/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1918643] [NEW] package libjpeg-progs 8c-2ubuntu7 failed to install/upgrade: a tentar sobre-escrever '/usr/bin/cjpeg', que também está no pacote libjpeg-turbo-progs 1.1.90+svn73
Public bug reported: This warning appears when I call some apps, Terminal included (yes, I'm working in a desktop environment) ProblemType: Package DistroRelease: Ubuntu 20.10 Package: libjpeg-progs 8c-2ubuntu7 ProcVersionSignature: Ubuntu 5.8.0-44.50-generic 5.8.18 Uname: Linux 5.8.0-44-generic x86_64 ApportVersion: 2.20.11-0ubuntu50.5 AptOrdering: libjpeg9:amd64: Install libjpeg-progs:amd64: Install NULL: ConfigurePending Architecture: amd64 CasperMD5CheckResult: skip Date: Thu Mar 11 06:50:08 2021 ErrorMessage: a tentar sobre-escrever '/usr/bin/cjpeg', que também está no pacote libjpeg-turbo-progs 1.1.90+svn733-0ubuntu4.1 InstallationDate: Installed on 2021-03-09 (1 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) Python3Details: /usr/bin/python3.8, Python 3.8.6, python3-minimal, 3.8.6-0ubuntu1 PythonDetails: N/A RelatedPackageVersions: dpkg 1.20.5ubuntu2 apt 2.1.10ubuntu0.2 SourcePackage: libjpeg8-empty Title: package libjpeg-progs 8c-2ubuntu7 failed to install/upgrade: a tentar sobre-escrever '/usr/bin/cjpeg', que também está no pacote libjpeg-turbo-progs 1.1.90+svn733-0ubuntu4.1 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: libjpeg8-empty (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package groovy -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libjpeg8-empty in Ubuntu. https://bugs.launchpad.net/bugs/1918643 Title: package libjpeg-progs 8c-2ubuntu7 failed to install/upgrade: a tentar sobre-escrever '/usr/bin/cjpeg', que também está no pacote libjpeg- turbo-progs 1.1.90+svn733-0ubuntu4.1 Status in libjpeg8-empty package in Ubuntu: New Bug description: This warning appears when I call some apps, Terminal included (yes, I'm working in a desktop environment) ProblemType: Package DistroRelease: Ubuntu 20.10 Package: libjpeg-progs 8c-2ubuntu7 ProcVersionSignature: Ubuntu 5.8.0-44.50-generic 5.8.18 Uname: Linux 5.8.0-44-generic x86_64 ApportVersion: 2.20.11-0ubuntu50.5 AptOrdering: libjpeg9:amd64: Install libjpeg-progs:amd64: Install NULL: ConfigurePending Architecture: amd64 CasperMD5CheckResult: skip Date: Thu Mar 11 06:50:08 2021 ErrorMessage: a tentar sobre-escrever '/usr/bin/cjpeg', que também está no pacote libjpeg-turbo-progs 1.1.90+svn733-0ubuntu4.1 InstallationDate: Installed on 2021-03-09 (1 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) Python3Details: /usr/bin/python3.8, Python 3.8.6, python3-minimal, 3.8.6-0ubuntu1 PythonDetails: N/A RelatedPackageVersions: dpkg 1.20.5ubuntu2 apt 2.1.10ubuntu0.2 SourcePackage: libjpeg8-empty Title: package libjpeg-progs 8c-2ubuntu7 failed to install/upgrade: a tentar sobre-escrever '/usr/bin/cjpeg', que também está no pacote libjpeg-turbo-progs 1.1.90+svn733-0ubuntu4.1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libjpeg8-empty/+bug/1918643/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1918497] Re: connect to one shared folder error package
Thank you for your bug report. * which packages did you upgrade? * how do you try to connect? * what error do you get exactly? (could take a screenshot showing it) ** Changed in: nautilus (Ubuntu) Importance: Undecided => Low ** Changed in: nautilus (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1918497 Title: connect to one shared folder error package Status in nautilus package in Ubuntu: Incomplete Bug description: when I had upgraded package I can't connect to my folder in my NAS. (All machine have the last ubuntu.) In another computer with old package I can see all file in a shared folder but when I have compiled 'apt upgrade' if I try to open the folder the computer return me a error ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: nautilus 1:3.38.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.8.0-44.50-generic 5.8.18 Uname: Linux 5.8.0-44-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu50.5 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Mar 10 23:08:05 2021 ExecutablePath: /usr/bin/nautilus GsettingsChanges: b'org.gnome.nautilus.window-state' b'sidebar-width' b'222' b'org.gnome.nautilus.window-state' b'initial-size' b'(1011, 597)' b'org.gnome.nautilus.preferences' b'default-folder-viewer' b"'list-view'" InstallationDate: Installed on 2021-03-06 (3 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) ProcEnviron: SHELL=/bin/bash XDG_RUNTIME_DIR= PATH=(custom, no user) LANG=it_IT.UTF-8 SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: evince3.38.0-1 file-roller 3.38.0-1 nautilus-extension-gnome-terminal 3.38.0-1ubuntu1.1 nautilus-share0.7.3-2ubuntu3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1918497/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1918619] Re: Kind of slowly refresh
Actually there is more, as it's shown on this other video. The same problem happens when “there is a display event”…? Like when my mouse go over an element, even if I can't click on it. ** Attachment added: "VID_20210311_105952.mp4" https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1918619/+attachment/5475721/+files/VID_20210311_105952.mp4 ** Description changed: I use to press Alt+Tab to switch between windows (or frames, whatever) and I noticed today that when I switch to another window the up bar blinks. I already had a display problem once, so I knew it was better with a external video. + + EDIT: I remember having this problem a year ago perhaps, and it + disappear if I reboot my computer. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.8.0-44.50~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-44-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Mar 11 10:45:08 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: - Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA controller]) -Subsystem: Lenovo HD Graphics 620 [17aa:39e9] + Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA controller]) + Subsystem: Lenovo HD Graphics 620 [17aa:39e9] InstallationDate: Installed on 2020-11-15 (115 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: LENOVO 80V0 ProcEnviron: - PATH=(custom, no user) - XDG_RUNTIME_DIR= - LANG=fr_FR.UTF-8 - SHELL=/bin/bash + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=fr_FR.UTF-8 + SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-44-generic root=UUID=2342b448-1302-426d-9afd-b40fd298cdab ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/03/2018 dmi.bios.release: 2.20 dmi.bios.vendor: LENOVO dmi.bios.version: 3PCN20WW(V2.04) dmi.board.asset.tag: NO Asset Tag dmi.board.name: Lenovo ideapad 510S-13IKB dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad 510S-13IKB dmi.ec.firmware.release: 2.20 dmi.modalias: dmi:bvnLENOVO:bvr3PCN20WW(V2.04):bd07/03/2018:br2.20:efr2.20:svnLENOVO:pn80V0:pvrLenovoideapad510S-13IKB:rvnLENOVO:rnLenovoideapad510S-13IKB:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrLenovoideapad510S-13IKB: dmi.product.family: IDEAPAD dmi.product.name: 80V0 dmi.product.sku: LENOVO_MT_80V0_BU_idea_FM_Lenovo ideapad 510S-13IKB dmi.product.version: Lenovo ideapad 510S-13IKB dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.2.6-0ubuntu0.20.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1918619 Title: Kind of slowly refresh Status in xorg package in Ubuntu: New Bug description: I use to press Alt+Tab to switch between windows (or frames, whatever) and I noticed today that when I switch to another window the up bar blinks. I already had a display problem once, so I knew it was better with a external video. EDIT: I remember having this problem a year ago perhaps, and it disappear if I reboot my computer. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.8.0-44.50~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-44-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Mar 11 10:45:08 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Lenovo HD Graphics 620 [17aa:39e9] InstallationDate: Installed on 2020-11-15 (115 days ago) InstallationMedia: Ubuntu
[Desktop-packages] [Bug 1918619] [NEW] Kind of slowly refresh
Public bug reported: I use to press Alt+Tab to switch between windows (or frames, whatever) and I noticed today that when I switch to another window the up bar blinks. I already had a display problem once, so I knew it was better with a external video. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.8.0-44.50~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-44-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Mar 11 10:45:08 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Lenovo HD Graphics 620 [17aa:39e9] InstallationDate: Installed on 2020-11-15 (115 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: LENOVO 80V0 ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-44-generic root=UUID=2342b448-1302-426d-9afd-b40fd298cdab ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/03/2018 dmi.bios.release: 2.20 dmi.bios.vendor: LENOVO dmi.bios.version: 3PCN20WW(V2.04) dmi.board.asset.tag: NO Asset Tag dmi.board.name: Lenovo ideapad 510S-13IKB dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad 510S-13IKB dmi.ec.firmware.release: 2.20 dmi.modalias: dmi:bvnLENOVO:bvr3PCN20WW(V2.04):bd07/03/2018:br2.20:efr2.20:svnLENOVO:pn80V0:pvrLenovoideapad510S-13IKB:rvnLENOVO:rnLenovoideapad510S-13IKB:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrLenovoideapad510S-13IKB: dmi.product.family: IDEAPAD dmi.product.name: 80V0 dmi.product.sku: LENOVO_MT_80V0_BU_idea_FM_Lenovo ideapad 510S-13IKB dmi.product.version: Lenovo ideapad 510S-13IKB dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.2.6-0ubuntu0.20.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug corruption focal ubuntu ** Attachment added: "sample of the problem" https://bugs.launchpad.net/bugs/1918619/+attachment/5475701/+files/VID_20210311_104202.mp4 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1918619 Title: Kind of slowly refresh Status in xorg package in Ubuntu: New Bug description: I use to press Alt+Tab to switch between windows (or frames, whatever) and I noticed today that when I switch to another window the up bar blinks. I already had a display problem once, so I knew it was better with a external video. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.8.0-44.50~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-44-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Mar 11 10:45:08 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Lenovo HD Graphics 620 [17aa:39e9] InstallationDate: Installed on 2020-11-15 (115 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: LENOVO 80V0 ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-44-generic root=UUID=2342b448-1302-426d-9afd-b40fd298cdab ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/03/2018 dmi.bios.release: 2.20 dmi.bios.vendor: LENOVO dmi.bios.version: 3PCN20WW(V2.04) dmi.board.asset.tag: NO Asset Tag dmi.board.name: Lenovo ideapad 510S-13IKB dmi.board.vendor: LENOVO d
[Desktop-packages] [Bug 1904583] Re: SRU: Backport the latest developments on drivers detection and hybrid graphics
Also, once the FTBFS is resolved, this is still blocked on LP: #1915003. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-prime in Ubuntu. https://bugs.launchpad.net/bugs/1904583 Title: SRU: Backport the latest developments on drivers detection and hybrid graphics Status in OEM Priority Project: Confirmed Status in nvidia-prime package in Ubuntu: Fix Released Status in ubuntu-drivers-common package in Ubuntu: Fix Released Status in nvidia-prime source package in Bionic: Fix Committed Status in ubuntu-drivers-common source package in Bionic: Fix Committed Status in nvidia-prime source package in Focal: Fix Released Status in ubuntu-drivers-common source package in Focal: Fix Released Status in nvidia-prime source package in Groovy: Fix Released Status in ubuntu-drivers-common source package in Groovy: Fix Released Bug description: As we introduced the "-server" NVIDIA drivers, and the concept of "LTSB" (Long Term Support Branch) and "NFB" (New Feature Branch) releases, the detection logic behind ubuntu-drivers needs an update to make the correct choices for the user. The introduction of the NVIDIA 450 series, also added runtime power management, which greatly improves user experience on systems with hybrid graphics, and allows greater power savings. When supported, on- demand mode and runtime power management are the default. Both gpu- manager and ubuntu-drivers in ubuntu drivers common, and the tools in the nvidia-prime package need updating as a result. The nvidia-prime package also has a change to fix a problem where /lib/udev/rules.d/50-pm-nvidia.rules was left behind, after a system upgrade 20.04 LTS (focal) to 20.10 (groovy), and yet prime-select had lost the ability to remove the udev rules file, leaving the end user with no means to re-enable his/her Nvidia GPU. Only the components in Ubuntu 20.10 require a fairly small diff for the backport. The rest is a direct sync of the 1:0.8.6.3 release in 21.04. [Impact] * The ubuntu-drivers tool might install the wrong driver, or, in some cases, crash, if the new -server drivers are available. * The new runtime power management can't be used even when the hardware (Turing GPUs or newer) supports it. * We want to the default drivers to be Long Term support releases. Users may still pick different drivers manually. [Fix] * The code in Ubuntu 21.04 includes essential bug fixes, and more test cases in the test suite, to make sure that driver installation is more robust, and more accurate (LTSB vs NFB releases, and non-server vs -server releases). * ubuntu-drivers, gpu-manager, and prime-select now all support runtime power management. [Test Case] Install ubuntu-drivers-common and nvidia-prime from proposed, and check the following: 1) ubuntu-drivers debug 2) Make sure no nvidia driver is installed (sudo apt-get --purge remove '*nvidia*', and try installing an nvidia driver with "sudo ubuntu-drivers install" 3) Reboot your system 4) [optional] If you are running on a hybrid laptop, you can check if your system supports runtime power management: sudo prime-select on-demand (if you are already in "on-demand" mode, select "intel" mode first, then try "on-demand" again) 5) If you followed step 4, reboot again 6) Attach your /var/log/gpu-manager.log [Regression Risk] Medium, while this code includes many fixes, it needs careful testing. == Changes == Only the components in Ubuntu 20.10 require a fairly small diff for the backport. The rest is a direct sync of the 1:0.8.6.3 release in 21.04. == Ubuntu 20.10 == ubuntu-drivers-common (1:0.8.6.3~0.20.10.1) groovy; urgency=medium * UbuntuDrivers/detect.py, tests/test_ubuntu_drivers.py: - Prefer LTSB releases over NFB ones for non gpgpu cases too. * gpu-manager.c: - Make it possible to force runtimepm by creating the /etc/u-d-c-nvidia-runtimepm-override file. - Make on-demand default on nvidia >= 450, when no previous settings are available. nvidia-prime (0.8.15.3~0.20.10.1) groovy; urgency=medium * debian/postinst.in: - Remove obsolete udev rules (LP: #1904583). * debian/rules: - Add postinst file to the autoclean target. * prime-select: - Do not try to apply any changes unless an integrated GPU is available. == Ubuntu 20.04 == ubuntu-drivers-common (1:0.8.6.3~0.20.04.1) focal; urgency=medium * Backport 1:0.8.6.3 (LP: #1904583). nvidia-prime (0.8.15.3~0.20.04.1) focal; urgency=medium [ Alberto Milone ] * prime-select: - Enable runtimepm in on-demand mode if supported (LP: #1895855). - Disable workaround for on-demand mode. - Enable KMS if runtimepm is supported. * debian/postinst.in: - Remove obsolete udev rules in the postinst too. * debian/rules: - Ad
[Desktop-packages] [Bug 1915003] Re: SRU: Always update the initramfs when changing power profile
Can we get this verified? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-prime in Ubuntu. https://bugs.launchpad.net/bugs/1915003 Title: SRU: Always update the initramfs when changing power profile Status in NVIDIA Drivers Ubuntu: New Status in OEM Priority Project: Triaged Status in nvidia-prime package in Ubuntu: Fix Released Status in nvidia-settings package in Ubuntu: Fix Released Status in nvidia-prime source package in Bionic: Fix Committed Status in nvidia-settings source package in Bionic: Fix Committed Status in nvidia-prime source package in Focal: Fix Released Status in nvidia-settings source package in Focal: Fix Released Status in nvidia-prime source package in Groovy: Fix Released Status in nvidia-settings source package in Groovy: Fix Released Bug description: Since we introduced support for dynamic power management, on systems with hybrid graphics (LP: #1904583), the need to load drivers with different options has become more evident. We need to make sure that the files in the initramfs are in sync with the current user selection. This is also a chance to update the old nvidia-settings release in the archive. [Impact] * If the modules list is not in sync with the selected power profile, users may experience a black screen or increased power consumption. * Updating the initramfs can take a few seconds, and we need to provide users with some form of visual feedback. [Fix] * The prime-select tool shoud update the initramfs when switching between power profiles, and provide visual feedback. * The nvidia-settings panel should provide a progress dialog, since profile switching would otherwise freeze the UI until update-initramfs completes. [Test Case] Make sure a supported nvidia driver is installed (450, 460), then install nvidia-prime and nvidia-settings from proposed, and check the following: 1) prime-select query (to check your current profile) 2) sudo prime-select on-demand (or "intel", or "nvidia", depending on your current power profile) 3) Check that the operation completes successfully. 4) Reboot your system 5) Launch the nvidia-setting panel. 6) Select a different profile from the PRIME tab, and check that a progress dialog is correctly displayed. 7) Close the nvidia-settings panel, and reboot. [Regression Risk] Medium, while the changes in prime-select are trivial, nvidia-settings needs careful testing. To manage notifications about this bug go to: https://bugs.launchpad.net/nvidia-drivers-ubuntu/+bug/1915003/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1916594] Re: Xorg freeze
** Changed in: xorg-server (Ubuntu) Status: Incomplete => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1916594 Title: Xorg freeze Status in xorg-server package in Ubuntu: Invalid Bug description: I have several problems in usage of ubuntu and I guess it's a display server or grub problem. First, my system freezes sometimes and it required hard reboot and I used chrome and several programming tools in this moments(and i didn't run any hi performance computing jobs). Second, i have a continuous problem with booting in my machine. it means, my system cannot enter GUI session directly(The cursor just blinks in black screen). It requires to switch to console session and re-enter to GUI(with ALT F1, F2) and I am using LG laptop and I guess it's a problem from graphic driver. I hope it can be resolved soon. Thanks(from south Korea user). ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.8.0-43.49~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-43-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: [Errno 21] 디렉터리입니다: '/proc/driver/nvidia/capabilities/gpu0' .proc.driver.nvidia.capabilities.mig: Error: [Errno 21] 디렉터리입니다: '/proc/driver/nvidia/capabilities/mig' .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] 디렉터리입니다: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 460.32.03 Sun Dec 27 19:00:34 UTC 2020 GCC version: gcc version 9.3.0 (Ubuntu 9.3.0-17ubuntu1~20.04) ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 BootLog: Error: [Errno 13] 허가 거부: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Feb 23 20:40:22 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: nvidia, 460.32.03, 5.8.0-41-generic, x86_64: installed nvidia, 460.32.03, 5.8.0-43-generic, x86_64: installed ExtraDebuggingInterest: Yes GpuHangFrequency: Very infrequently GraphicsCard: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller]) Subsystem: LG Electronics, Inc. UHD Graphics 620 [1854:0304] InstallationDate: Installed on 2021-01-26 (27 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 0cf3:e300 Qualcomm Atheros Communications Bus 001 Device 003: ID 0408:50c0 Quanta Computer, Inc. USB HD Webcam Bus 001 Device 002: ID 25a7:fa67 CX 2.4G Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LG Electronics 15UD480-KX70K ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-43-generic root=UUID=c1380f53-21a5-44dd-811f-ca31d34355b0 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/02/2018 dmi.bios.release: 2.24 dmi.bios.version: GP224 dmi.board.asset.tag: No Asset Tag dmi.board.name: 15U480 dmi.board.vendor: Quanta dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.ec.firmware.release: 1.4 dmi.modalias: dmi:bvn:bvrGP224:bd07/02/2018:br2.24:efr1.4:svnLGElectronics:pn15UD480-KX70K:pvr:rvnQuanta:rn15U480:rvr:cvn:ct10:cvr: dmi.product.family: U Series dmi.product.name: 15UD480-KX70K dmi.sys.vendor: LG Electronics version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1916594/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1918613] [NEW] [FFe] GDM background configurable with gsettings
Public bug reported: [Description] Customization of the greeter is a requirement from Corporate customers. Currently the background (plain color or image) of the greeter is hard coded in the style embedded in the theme. Customizing this background requires to extract the style sheet from gnome-shell gresource file, modify it manually, recompile and deploy the new gresource, and add an alternative to it. This feature adds 4 gsettings keys to make the background of the greeter configurable via gsettings. The default value defined the in the theme is used for keys that are not set. [Rationale] Corporate customers use LTS releases. This changeset needs to land in hirsute before it can be SRUd into prior Ubuntu LTS releases. So we would like to submit this FFe to get it into Hirsute first. [Risks] The changeset is minimal, isolated and can be easily reverted. In case of error in the code, GDM will fail to load and it will be immediately visible. [Build] Builds and tested successfully locally. Besides the updated JS is not compiled as part of build. ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1918613 Title: [FFe] GDM background configurable with gsettings Status in gnome-shell package in Ubuntu: New Bug description: [Description] Customization of the greeter is a requirement from Corporate customers. Currently the background (plain color or image) of the greeter is hard coded in the style embedded in the theme. Customizing this background requires to extract the style sheet from gnome-shell gresource file, modify it manually, recompile and deploy the new gresource, and add an alternative to it. This feature adds 4 gsettings keys to make the background of the greeter configurable via gsettings. The default value defined the in the theme is used for keys that are not set. [Rationale] Corporate customers use LTS releases. This changeset needs to land in hirsute before it can be SRUd into prior Ubuntu LTS releases. So we would like to submit this FFe to get it into Hirsute first. [Risks] The changeset is minimal, isolated and can be easily reverted. In case of error in the code, GDM will fail to load and it will be immediately visible. [Build] Builds and tested successfully locally. Besides the updated JS is not compiled as part of build. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1918613/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1918613] Re: [FFe] GDM background configurable with gsettings
-- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1918613 Title: [FFe] GDM background configurable with gsettings Status in gnome-shell package in Ubuntu: New Bug description: [Description] Customization of the greeter is a requirement from Corporate customers. Currently the background (plain color or image) of the greeter is hard coded in the style embedded in the theme. Customizing this background requires to extract the style sheet from gnome-shell gresource file, modify it manually, recompile and deploy the new gresource, and add an alternative to it. This feature adds 4 gsettings keys to make the background of the greeter configurable via gsettings. The default value defined the in the theme is used for keys that are not set. [Rationale] Corporate customers use LTS releases. This changeset needs to land in hirsute before it can be SRUd into prior Ubuntu LTS releases. So we would like to submit this FFe to get it into Hirsute first. [Risks] The changeset is minimal, isolated and can be easily reverted. In case of error in the code, GDM will fail to load and it will be immediately visible. [Build] Builds and tested successfully locally. Besides the updated JS is not compiled as part of build. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1918613/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1918613] Re: [FFe] GDM background configurable with gsettings
** Patch added: "gnome-shell_3.38.3-3ubuntu1_3.38.3-3ubuntu2.debdiff" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1918613/+attachment/5475698/+files/gnome-shell_3.38.3-3ubuntu1_3.38.3-3ubuntu2.debdiff ** Description changed: [Description] Customization of the greeter is a requirement from Corporate customers. Currently the background (plain color or image) of the greeter is hard coded in the style embedded in the theme. Customizing this background requires to extract the style sheet from gnome-shell gresource file, modify it manually, recompile and deploy the new gresource, and add an alternative to it. This feature adds 4 gsettings keys to make the background of the greeter configurable via gsettings. The default value defined the in the theme is used for keys that are not set. [Rationale] Corporate customers use LTS releases. This changeset needs to land in hirsute before it can be SRUd into prior Ubuntu LTS releases. So we would like to submit this FFe to get it into Hirsute first. [Risks] The changeset is minimal, isolated and can be easily reverted. In case of error in the code, GDM will fail to load and it will be immediately visible. + + [Build] + Builds and tested successfully locally. + Besides the updated JS is not compiled as part of build. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1918613 Title: [FFe] GDM background configurable with gsettings Status in gnome-shell package in Ubuntu: New Bug description: [Description] Customization of the greeter is a requirement from Corporate customers. Currently the background (plain color or image) of the greeter is hard coded in the style embedded in the theme. Customizing this background requires to extract the style sheet from gnome-shell gresource file, modify it manually, recompile and deploy the new gresource, and add an alternative to it. This feature adds 4 gsettings keys to make the background of the greeter configurable via gsettings. The default value defined the in the theme is used for keys that are not set. [Rationale] Corporate customers use LTS releases. This changeset needs to land in hirsute before it can be SRUd into prior Ubuntu LTS releases. So we would like to submit this FFe to get it into Hirsute first. [Risks] The changeset is minimal, isolated and can be easily reverted. In case of error in the code, GDM will fail to load and it will be immediately visible. [Build] Builds and tested successfully locally. Besides the updated JS is not compiled as part of build. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1918613/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1916594] Re: Xorg freeze
My symptoms seem to be gone. thank you -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1916594 Title: Xorg freeze Status in xorg-server package in Ubuntu: Incomplete Bug description: I have several problems in usage of ubuntu and I guess it's a display server or grub problem. First, my system freezes sometimes and it required hard reboot and I used chrome and several programming tools in this moments(and i didn't run any hi performance computing jobs). Second, i have a continuous problem with booting in my machine. it means, my system cannot enter GUI session directly(The cursor just blinks in black screen). It requires to switch to console session and re-enter to GUI(with ALT F1, F2) and I am using LG laptop and I guess it's a problem from graphic driver. I hope it can be resolved soon. Thanks(from south Korea user). ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.8.0-43.49~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-43-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: [Errno 21] 디렉터리입니다: '/proc/driver/nvidia/capabilities/gpu0' .proc.driver.nvidia.capabilities.mig: Error: [Errno 21] 디렉터리입니다: '/proc/driver/nvidia/capabilities/mig' .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] 디렉터리입니다: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 460.32.03 Sun Dec 27 19:00:34 UTC 2020 GCC version: gcc version 9.3.0 (Ubuntu 9.3.0-17ubuntu1~20.04) ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 BootLog: Error: [Errno 13] 허가 거부: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Feb 23 20:40:22 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: nvidia, 460.32.03, 5.8.0-41-generic, x86_64: installed nvidia, 460.32.03, 5.8.0-43-generic, x86_64: installed ExtraDebuggingInterest: Yes GpuHangFrequency: Very infrequently GraphicsCard: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller]) Subsystem: LG Electronics, Inc. UHD Graphics 620 [1854:0304] InstallationDate: Installed on 2021-01-26 (27 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 0cf3:e300 Qualcomm Atheros Communications Bus 001 Device 003: ID 0408:50c0 Quanta Computer, Inc. USB HD Webcam Bus 001 Device 002: ID 25a7:fa67 CX 2.4G Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LG Electronics 15UD480-KX70K ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-43-generic root=UUID=c1380f53-21a5-44dd-811f-ca31d34355b0 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/02/2018 dmi.bios.release: 2.24 dmi.bios.version: GP224 dmi.board.asset.tag: No Asset Tag dmi.board.name: 15U480 dmi.board.vendor: Quanta dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.ec.firmware.release: 1.4 dmi.modalias: dmi:bvn:bvrGP224:bd07/02/2018:br2.24:efr1.4:svnLGElectronics:pn15UD480-KX70K:pvr:rvnQuanta:rn15U480:rvr:cvn:ct10:cvr: dmi.product.family: U Series dmi.product.name: 15UD480-KX70K dmi.sys.vendor: LG Electronics version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1916594/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1880405] Re: Unresponsive GUI and journal flooded with: JS ERROR: TypeError: null has no properties _onFocusChanged@resource:///org/gnome/shell/ui/closeDialog.js:135:9
Only in 21.04 at the moment. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1880405 Title: Unresponsive GUI and journal flooded with: JS ERROR: TypeError: null has no properties _onFocusChanged@resource:///org/gnome/shell/ui/closeDialog.js:135:9 Status in GNOME Shell: Unknown Status in mutter package in Ubuntu: Fix Released Status in mutter source package in Hirsute: Fix Released Bug description: [ Impact ] Shell becomes slow and unresponsive flooding journal with JS errors [ Test case ] 1. Resize the terminal to use half the screen (using CMD+LEFT) 2. switch it to fullscreen (F11) and back (F11) 3. Repeat this some number of times ensure we don't end up in a loop with 100% CPU usage. 4. Ensure that it's still possible to get window focus and the UI is responsive. [ Regression potential ] Events are ignored for windows which are still visible. --- O.k. it is an old Lenovo thinkpad T410. However, in 18.04, 19.04 and 19.10 I did face these problems. The sometimes I have to wait 10 seconds to see if a window reacts or not. It is hard to use. Installiert: 3.36.1-5ubuntu2 Installationskandidat: 3.36.2-1ubuntu1~20.04.1 Versionstabelle: 3.36.2-1ubuntu1~20.04.1 500 500 http://it.archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages *** 3.36.1-5ubuntu2 100 100 /var/lib/dpkg/status 3.36.1-5ubuntu1 500 500 http://it.archive.ubuntu.com/ubuntu focal/main amd64 Packages ProblemType: BugDistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.1-5ubuntu2 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: GNOME-Classic:GNOME Date: Sun May 24 15:43:34 2020 DisplayManager: gdm3 InstallationDate: Installed on 2020-02-05 (109 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) RelatedPackageVersions: mutter-common 3.36.2-1ubuntu1~20.04.1SourcePackage: gnome-shell UpgradeStatus: Upgraded to focal on 2020-05-08 (15 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1880405/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1880405] Re: Unresponsive GUI and journal flooded with: JS ERROR: TypeError: null has no properties _onFocusChanged@resource:///org/gnome/shell/ui/closeDialog.js:135:9
Is the fix available in 20.04 LTS, or just 20.10 only? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1880405 Title: Unresponsive GUI and journal flooded with: JS ERROR: TypeError: null has no properties _onFocusChanged@resource:///org/gnome/shell/ui/closeDialog.js:135:9 Status in GNOME Shell: Unknown Status in mutter package in Ubuntu: Fix Released Status in mutter source package in Hirsute: Fix Released Bug description: [ Impact ] Shell becomes slow and unresponsive flooding journal with JS errors [ Test case ] 1. Resize the terminal to use half the screen (using CMD+LEFT) 2. switch it to fullscreen (F11) and back (F11) 3. Repeat this some number of times ensure we don't end up in a loop with 100% CPU usage. 4. Ensure that it's still possible to get window focus and the UI is responsive. [ Regression potential ] Events are ignored for windows which are still visible. --- O.k. it is an old Lenovo thinkpad T410. However, in 18.04, 19.04 and 19.10 I did face these problems. The sometimes I have to wait 10 seconds to see if a window reacts or not. It is hard to use. Installiert: 3.36.1-5ubuntu2 Installationskandidat: 3.36.2-1ubuntu1~20.04.1 Versionstabelle: 3.36.2-1ubuntu1~20.04.1 500 500 http://it.archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages *** 3.36.1-5ubuntu2 100 100 /var/lib/dpkg/status 3.36.1-5ubuntu1 500 500 http://it.archive.ubuntu.com/ubuntu focal/main amd64 Packages ProblemType: BugDistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.1-5ubuntu2 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: GNOME-Classic:GNOME Date: Sun May 24 15:43:34 2020 DisplayManager: gdm3 InstallationDate: Installed on 2020-02-05 (109 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) RelatedPackageVersions: mutter-common 3.36.2-1ubuntu1~20.04.1SourcePackage: gnome-shell UpgradeStatus: Upgraded to focal on 2020-05-08 (15 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1880405/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
