[Bug 1777708] Re: Desktop briefly becomes unresponsive when typing on 2 keyboards at the same time in Xorg sessions
** Summary changed: - Desktop briefly becomes unresponsive when typing on 2 keyboards at the same time + Desktop briefly becomes unresponsive when typing on 2 keyboards at the same time in Xorg sessions -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/108 Title: Desktop briefly becomes unresponsive when typing on 2 keyboards at the same time in Xorg sessions To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/108/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1931018] Re: Keyboard layout switch freezes
I'm guessing this is related to bug 108, even if you only have one keyboard. It sounds related. ** Package changed: xorg (Ubuntu) => mutter (Ubuntu) ** Tags added: i18n -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1931018 Title: Keyboard layout switch freezes To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1931018/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1931018] [NEW] Keyboard layout switch freezes
You have been subscribed to a public bug: Hi! I have problem with slow keyboard layout switching between Russian and English layouts. In ubuntu 16.04-20.04 :) gsettings get org.gnome.desktop.wm.keybindings switch-input-source ['XF86Keyboard'] But in gnome-tweak-tool I set as key for layout switching caps-lock. It is work, but when I switch from en to ru, fast, and when ru to en, I have delay ~1s. And in gnome-tweak-tool I see caps-lock as keyboard key for switching, and in gsettings is XF86Keyboard or some time ago super+space. When I try to set in gsettings some other keys (as super+space), they worked fast, but in gnome-tweak-tool caps-lock work slooow. And all this keys work in one time, this is strange. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 Uname: Linux 5.12.0-8.5-liquorix-amd64 x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file. .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.80 Fri May 7 06:55:54 UTC 2021 GCC version: gcc version 9.3.0 (Ubuntu 9.3.0-17ubuntu1~20.04) ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 BootLog: Error: [Errno 13] Отказано в доступе: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME CurrentDmesg: Error: command ['dmesg'] failed with exit code 1: dmesg: read kernel buffer failed: Operation not permitted Date: Sun Jun 6 15:58:43 2021 DistUpgraded: 2020-12-05 22:39:51,673 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (g-exec-error-quark: Не удалось выполнить процесс-потомок «./xorg_fix_proprietary.py» (Нет такого файла или каталога) (8)) DistroCodename: focal DistroVariant: ubuntu DkmsStatus: nvidia, 460.80, 5.11.0-18.1-liquorix-amd64, x86_64: installed nvidia, 460.80, 5.12.0-8.5-liquorix-amd64, x86_64: installed nvidia, 460.80, 5.12.0-9.2-liquorix-amd64, x86_64: installed GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: CLEVO/KAPOK Computer 3rd Gen Core processor Graphics Controller [1558:2701] NVIDIA Corporation GK107M [GeForce GT 640M] [10de:0fd2] (rev a1) (prog-if 00 [VGA controller]) InstallationDate: Installed on 2018-06-28 (1073 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: CLEVO CO. W250ENQ / W270ENQ ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ru_RU.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: audit=0 intel_pstate=disable BOOT_IMAGE=/boot/vmlinuz-5.12.0-8.5-liquorix-amd64 root=UUID=3f1a1990-8bad-49d1-970e-87308d8cd521 ro quiet splash nouveau.runpm=0 zswap.enabled=0 vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: Upgraded to focal on 2020-12-05 (182 days ago) dmi.bios.date: 04/03/2012 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4.6.5 dmi.board.asset.tag: Tag 12345 dmi.board.name: W250ENQ / W270ENQ dmi.board.vendor: CLEVO CO. dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd04/03/2012:br4.6:svnCLEVOCO.:pnW250ENQ/W270ENQ:pvrNotApplicable:rvnCLEVOCO.:rnW250ENQ/W270ENQ:rvrNotApplicable:cvnNoEnclosure:ct9:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: W250ENQ / W270ENQ dmi.product.sku: Not Applicable dmi.product.version: Not Applicable dmi.sys.vendor: CLEVO CO. modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 mtime.conffile..etc.default.apport: 2020-06-08T10:33:29.519300 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.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.2 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: mutter (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug false-gpu-hang focal freeze third-party-packages ubuntu -- Keyboard layout switch
[Bug 1890772] Re: No signal on 4K 60Hz DisplayPort monitor by default, until "max bpc" is lowered to 8
This should also fix the problem for some people in Wayland sessions: https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1834 It is in mutter release 40.1 and future release 3.38.5. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1890772 Title: No signal on 4K 60Hz DisplayPort monitor by default, until "max bpc" is lowered to 8 To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/1890772/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1851992] Re: Lock screen not locking upon resume (org.gnome.desktop.lockdown disable-lock-screen set to true for some reason)
Jose, that looks like a different problem. Please open a new bug by running: ubuntu-bug gnome-shell -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1851992 Title: Lock screen not locking upon resume (org.gnome.desktop.lockdown disable-lock-screen set to true for some reason) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1851992/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1883174] Re: Some (or all) desktop icons are missing
Ubuntu 21.04 does not use the package this bug is about, it uses a different extension for desktop icons. So that's why the behaviour in 21.04 is different to previous releases. Unfortunately for API reasons we are unable to backport the same extension from 21.04 to 20.04. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell-extension-desktop-icons in Ubuntu. https://bugs.launchpad.net/bugs/1883174 Title: Some (or all) desktop icons are missing To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell-extension-desktop-icons/+bug/1883174/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1834967] Re: Windows in Activities might be partially off screen
A similar problem can be seen in 21.04 as a result of bug 1922353. To make sure you're not just seeing bug 1922353 check that you can still interact with the windows. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1834967 Title: Windows in Activities might be partially off screen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-dock/+bug/1834967/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1892484] Re: Screen Sharing option is missing in 20.10, but exists in 20.04.
This is happening again with ubuntu 21.04. I have vino installed. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1892484 Title: Screen Sharing option is missing in 20.10, but exists in 20.04. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1892484/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1929304] Re: file-roller / gnome archive manager fails to extract
This bug was fixed in the package gnome-autoar - 0.2.3-1ubuntu0.4 --- gnome-autoar (0.2.3-1ubuntu0.4) bionic-security; urgency=medium * SECURITY REGRESSION: Fix extracting one-file archives (LP: #1929304) - debian/patches/fix_one_file_archives.patch: don't create en empty folder when extracting with nautilus in gnome-autoar/autoar-extractor.c. - debian/patches/fix_one_file_archives2.patch: prevent redundant path name handling for equal prefixes in gnome-autoar/autoar-extractor.c. -- Marc Deslauriers Fri, 04 Jun 2021 07:03:33 -0400 -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-autoar in Ubuntu. https://bugs.launchpad.net/bugs/1929304 Title: file-roller / gnome archive manager fails to extract To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-autoar/+bug/1929304/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1929304] Re: file-roller / gnome archive manager fails to extract
This bug was fixed in the package gnome-autoar - 0.2.3-2ubuntu0.4 --- gnome-autoar (0.2.3-2ubuntu0.4) focal-security; urgency=medium * SECURITY REGRESSION: Fix extracting one-file archives (LP: #1929304) - debian/patches/fix_one_file_archives.patch: don't create en empty folder when extracting with nautilus in gnome-autoar/autoar-extractor.c. - debian/patches/fix_one_file_archives2.patch: prevent redundant path name handling for equal prefixes in gnome-autoar/autoar-extractor.c. -- Marc Deslauriers Fri, 04 Jun 2021 07:03:08 -0400 ** Changed in: gnome-autoar (Ubuntu Bionic) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-autoar in Ubuntu. https://bugs.launchpad.net/bugs/1929304 Title: file-roller / gnome archive manager fails to extract To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-autoar/+bug/1929304/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1929304] Re: file-roller / gnome archive manager fails to extract
This bug was fixed in the package gnome-autoar - 0.2.4-2ubuntu0.4 --- gnome-autoar (0.2.4-2ubuntu0.4) groovy-security; urgency=medium * SECURITY REGRESSION: Fix extracting one-file archives (LP: #1929304) - debian/patches/fix_one_file_archives.patch: don't create en empty folder when extracting with nautilus in gnome-autoar/autoar-extractor.c. - debian/patches/fix_one_file_archives2.patch: prevent redundant path name handling for equal prefixes in gnome-autoar/autoar-extractor.c. -- Marc Deslauriers Fri, 04 Jun 2021 07:02:45 -0400 ** Changed in: gnome-autoar (Ubuntu Focal) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-autoar in Ubuntu. https://bugs.launchpad.net/bugs/1929304 Title: file-roller / gnome archive manager fails to extract To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-autoar/+bug/1929304/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1929304] Re: file-roller / gnome archive manager fails to extract
This bug was fixed in the package gnome-autoar - 0.3.1-1ubuntu0.1 --- gnome-autoar (0.3.1-1ubuntu0.1) hirsute-security; urgency=medium * SECURITY REGRESSION: Fix extracting one-file archives (LP: #1929304) - debian/patches/fix_one_file_archives.patch: don't create en empty folder when extracting with nautilus in gnome-autoar/autoar-extractor.c. - debian/patches/fix_one_file_archives2.patch: prevent redundant path name handling for equal prefixes in gnome-autoar/autoar-extractor.c. -- Marc Deslauriers Fri, 04 Jun 2021 06:58:43 -0400 ** Changed in: gnome-autoar (Ubuntu Hirsute) Status: In Progress => Fix Released ** Changed in: gnome-autoar (Ubuntu Groovy) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-autoar in Ubuntu. https://bugs.launchpad.net/bugs/1929304 Title: file-roller / gnome archive manager fails to extract To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-autoar/+bug/1929304/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1851992] Re: Lock screen not locking upon resume (org.gnome.desktop.lockdown disable-lock-screen set to true for some reason)
Additional note: Executing the gnome-screensaver-command -l command gets the following error: ** (gnome-screensaver-command:40447): WARNING **: 17:41:00.408: unable to send message: Timeout was reached ** Message: 17:41:00.408: Did not receive a reply from the screensaver. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1851992 Title: Lock screen not locking upon resume (org.gnome.desktop.lockdown disable-lock-screen set to true for some reason) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1851992/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1851992] Re: Lock screen not locking upon resume (org.gnome.desktop.lockdown disable-lock-screen set to true for some reason)
Hi, I am facing this same issue. In order to not have a duplicate of the issue, I am reporting it as a comment under the very same bug. I have tried the following: gsettings set org.gnome.desktop.lockdown disable-lock-screen true But it is still not working. What can I do in this case? I am on Ubuntu 20.04.2 LTS -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1851992 Title: Lock screen not locking upon resume (org.gnome.desktop.lockdown disable-lock-screen set to true for some reason) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1851992/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1906877] Re: diagnostics panel can leave automatic crash reporting enabled
This bug was fixed in the package gnome-control-center - 1:3.36.5-0ubuntu2 --- gnome-control-center (1:3.36.5-0ubuntu2) focal; urgency=medium [ Marco Trevisan (Treviño) ] * git-user-accounts-Use-newly-designed-fingerprint-enroll-dialo.patch: Correctly handle errors on fingerprint enroll dialog (LP: #1915174) [ Brian Murray ] * 0016-diagnostics-Add-Whoopsie-support.patch: ensure that we always perform the call to automatically report crashes so that it will be turned off if "never" is chosen. (LP: #1906877) -- Sebastien Bacher Tue, 06 Apr 2021 16:01:31 +0200 ** Changed in: gnome-control-center (Ubuntu Focal) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1906877 Title: diagnostics panel can leave automatic crash reporting enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1906877/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1915174] Update Released
The verification of the Stable Release Update for gnome-control-center has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1915174 Title: Fingerprint enrollment error stops user to be able to enroll again To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1915174/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1915174] Re: Fingerprint enrollment error stops user to be able to enroll again
This bug was fixed in the package gnome-control-center - 1:3.36.5-0ubuntu2 --- gnome-control-center (1:3.36.5-0ubuntu2) focal; urgency=medium [ Marco Trevisan (Treviño) ] * git-user-accounts-Use-newly-designed-fingerprint-enroll-dialo.patch: Correctly handle errors on fingerprint enroll dialog (LP: #1915174) [ Brian Murray ] * 0016-diagnostics-Add-Whoopsie-support.patch: ensure that we always perform the call to automatically report crashes so that it will be turned off if "never" is chosen. (LP: #1906877) -- Sebastien Bacher Tue, 06 Apr 2021 16:01:31 +0200 ** Changed in: gnome-control-center (Ubuntu Focal) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1915174 Title: Fingerprint enrollment error stops user to be able to enroll again To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1915174/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1931088] Re: boot-and-services tests fails in impish on armhf (248.3)
As I said I tried to recreate this, but it worked. It was fine under Focal/5.4.0-53-generic Host with the Impish-armhf container. Upgrading the host to impish it Impish/5.11.0-16-generic still works fine. It seems it only fails in autopkgtest infrastructure, not sure why yet :-/ -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/1931088 Title: boot-and-services tests fails in impish on armhf (248.3) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/1931088/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1931088] [NEW] boot-and-services tests fails in impish on armhf (248.3)
Public bug reported: Systemd 248.3-1ubuntu1 is rather new, but had 5 successful tests on armhf before now slipping into a bad mode. Now it seems all tests failed in boot-and-services by hanging until killed by VirtSubproc.Timeout of autokgtest. The last [1] test log has a bit more, it shows a python stack overflow ``` VirtSubproc.Timeout Fatal Python error: Cannot recover from stack overflow. Python runtime state: initialized Current thread 0x7f108e840740 (most recent call first): File "/home/ubuntu/autopkgtest/lib/adtlog.py", line 36 in log File "/home/ubuntu/autopkgtest/lib/adtlog.py", line 86 in debug File "/home/ubuntu/autopkgtest/lib/adt_testbed.py", line 472 in send File "/home/ubuntu/autopkgtest/lib/adt_testbed.py", line 521 in command ``` I have seen a bunch of packages including even gdm3 and glibc being blocked by that so I wanted to at least track down the issue until we can put it on someones task list to resolve. No one replied to my pings yet, but maybe that means someone is already debugging this and had enabled some debugging? By running the same in armhf container on arm64 VM on canonistack I've seen no issues. The test worked fine and had no hang/issues. root@systemd-test-fail:~/systemd-248.3# ./debian/tests/boot-and-services lxc 1 test_profile (__main__.AppArmorTest) AppArmor confined unit ... skipped 'fails on armhf testbeds, see LP: #1842352' test_help (__main__.CLITest) --help works and succeeds ... ok test_invalid_option (__main__.CLITest) Calling with invalid option fails ... ok test_version (__main__.CLITest) --version works and succeeds ... ok test_cpushares (__main__.CgroupsTest) service with CPUShares ... ok test_simple (__main__.CgroupsTest) simple service ... ok test_bash_crash (__main__.CoredumpTest) ... skipped 'systemd-coredump does not work in containers' test_log_for_service (__main__.JournalTest) ... ok test_no_options (__main__.JournalTest) ... ok test_boot (__main__.NspawnTest) ... skipped 'nspawn does not work in most containers' test_service (__main__.NspawnTest) ... skipped 'nspawn does not work in most containers' test_failing (__main__.SeccompTest) ... ok test_0_init (__main__.ServicesTest) Verify that init is systemd ... ok test_cron (__main__.ServicesTest) ... ok test_dbus (__main__.ServicesTest) ... ok test_gdm3 (__main__.ServicesTest) ... skipped 'gdm3 not found' test_logind (__main__.ServicesTest) ... ok test_network_manager (__main__.ServicesTest) ... ok test_no_failed (__main__.ServicesTest) No failed units ... ok test_rsyslog (__main__.ServicesTest) ... ok test_tmp_cleanup (__main__.ServicesTest) ... ok test_tmp_mount (__main__.ServicesTest) ... ok test_udev (__main__.ServicesTest) ... skipped 'udev does not work in containers' -- Ran 23 tests in 5.589s OK (skipped=6) So I can not reproduce this on canonistack, but it blocks autopkgtests of various packages pretty reproducibly :-/ [1]: https://autopkgtest.ubuntu.com/results/autopkgtest- impish/impish/armhf/s/systemd/20210604_081326_d4319@/log.gz ** Affects: dnsmasq (Ubuntu) Importance: Undecided Status: Incomplete ** Affects: gdm3 (Ubuntu) Importance: Undecided Status: Incomplete ** Affects: glibc (Ubuntu) Importance: Undecided Status: Incomplete ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Tags: update-excuse ** Tags added: update-excuse ** Also affects: gdm3 (Ubuntu) Importance: Undecided Status: New ** Also affects: glibc (Ubuntu) Importance: Undecided Status: New ** Also affects: dnsmasq (Ubuntu) Importance: Undecided Status: New ** Changed in: dnsmasq (Ubuntu) Status: New => Incomplete ** Changed in: gdm3 (Ubuntu) Status: New => Incomplete ** Changed in: glibc (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/1931088 Title: boot-and-services tests fails in impish on armhf (248.3) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/1931088/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1931088] Re: boot-and-services tests fails in impish on armhf (248.3)
I was adding a few of the blocked packages as incomplete tasks to have this bug update-excuse show up in excuses. Right now until we know better I'd consider this a systemd issue. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/1931088 Title: boot-and-services tests fails in impish on armhf (248.3) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/1931088/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1901060] Re: Using gnome-control-center to configure two wired connections is unreliable
[Expired for gnome-control-center (Ubuntu) because there has been no activity for 60 days.] ** Changed in: gnome-control-center (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1901060 Title: Using gnome-control-center to configure two wired connections is unreliable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1901060/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1922911] Re: gnome-shell flooding the syslog
[Expired for gnome-shell (Ubuntu) because there has been no activity for 60 days.] ** Changed in: gnome-shell (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1922911 Title: gnome-shell flooding the syslog To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1922911/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1922437] Re: login into desktop is stuttering on wayland
[Expired for gnome-shell (Ubuntu) because there has been no activity for 60 days.] ** Changed in: gnome-shell (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1922437 Title: login into desktop is stuttering on wayland To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1922437/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1922353] Re: Overview sometimes fails to appear or disappear in gnome-shell 3.38
This package fixed the bug for me. Thank you :-) gnome-shell 3.38.4-1ubuntu3~21.04.1 I randomly pressed the "Super" key and clicked on one of the apps displayed. It works like it should and therefore fixes the problem. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1922353 Title: Overview sometimes fails to appear or disappear in gnome-shell 3.38 To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1922353/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1922353] Re: Overview sometimes fails to appear or disappear in gnome-shell 3.38
Confirming that gnome-shell 3.38.4-1ubuntu3~21.04.1 resolves the issue. Thank you for your work, it is much appreciated. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1922353 Title: Overview sometimes fails to appear or disappear in gnome-shell 3.38 To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1922353/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1901330] Re: Desktop freezes when trying to move icon to new position.
[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 Ubuntu Desktop Bugs, which is subscribed to gnome-shell-extension-desktop-icons in Ubuntu. https://bugs.launchpad.net/bugs/1901330 Title: Desktop freezes when trying to move icon to new position. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-desktop-icons/+bug/1901330/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
