[Bug 1958488] Re: [nvidia][xorg] display hangs on boot LOGO
-- 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/1958488 Title: [nvidia][xorg] display hangs on boot LOGO To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1958488/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1958488] Re: [nvidia][xorg] display hangs on boot LOGO
** Description changed:
+ [Impact]
+
+ * In Ubuntu 20.04 (which using Xorg with proprietary nvidia driver), in some
cases, the nvidia driver will probe later than launching gdm.
+ * If above race condition happens in iGPU + nvidia cases and monitor
connects to dGPU, which will cause gdm starts with wayland as opposed to Xorg.
Which may lead the monitor stuck in black-screen or boot LOGO.
+
+ [Test Plan]
+
+ * The environment:
+ 1. A desktop or workstation which containing an iGPU.
+ 2. Plug a nvidia graphic card to the system and installing proprietary
+ nvidia driver (470 in my case)
+ 3. Attach a monitor to dGPU and leave iGPU connect to nothing.
+ (in my test environment, there is the other ethernet card and TBT4 cards)
+ * Setup a cronjob,
+e.g. @reboot /home/u/test.sh
+ * Have a test script in something like /home/u/test.sh as
+
+ #!/bin/bash
+
+ sleep 20
+ count="$(cat /home/u/count)"
+ count=$((count+1))
+ echo $count | tee /home/u/count
+ journalctl -b | grep -q -i wayland || sudo reboot
+
+ * the system will probably stuck in black-screen or boot LOGO.
+ * Before applying the fix, the fail rate is 6/24 (fail 6 time in 24 runs).
+ * After applying the fix, it got pass within 90 reboot cycles.
+
+ [Where problems could occur]
+ * The patch checkes device/boot_vga with tag "master-of-seat". If a system
without any GPU as boot_vga then it will fall in infinite loop.
+ * I tried to detach all monitors from the system and the boot_vga still
exist (default to use iGPU, the first device found during initialization)
+ * I don't think they will a case which boot_vga doesn't exist in this moment
because:
+ In drivers/gpu/vga/vgaarb.c (linux package)
+ vga_arb_select_default_device() has a fallback function to determine the
boot_vga device to prevent firmware doesn't pass correct efifb to linux-kernel.
+
+ ---
+
Test environment/steps:
1. A desktop or workstation which containing an iGPU.
2. Plug a nvidia graphic card to the system and installing proprietary nvidia
driver (470 in my case)
3. Attach a monitor to dGPU and leave iGPU connect to nothing.
(in my test environment, there is the other ethernet card and TBT4 cards)
4. Reboot system.
Based on:
$ cat /lib/udev/rules.d/61-gdm.rules
# disable Wayland on Hi1710 chipsets
ATTR{vendor}=="0x19e5", ATTR{device}=="0x1711",
RUN+="/usr/lib/gdm3/gdm-disable-wayland"
# disable Wayland when using the proprietary nvidia driver
DRIVER=="nvidia", RUN+="/usr/lib/gdm3/gdm-disable-wayland"
It will disable wayland by default if proprietary nvidia driver load.
But in some race condition cases, the nvidia probe is later than gnome
launches. (The fail rate is 6/24.)
Thus, ubuntu-gdm has a fix for Bug#1794280 to add
"ExecStartPre=@libexecdir@/gdm-wait-for-drm".
-
- The gdm-wait-for-drm is intend to make sure all drm udev devices enumerated
before launching gdm.
+ The gdm-wait-for-drm is intend to make sure all drm udev devices
+ enumerated before launching gdm.
It rely on at least one "master-of-seat" graphic card for gdm but it's not
rigorous enough.
Since most of graphic cards are own "master-of-seat"[1].
In my case, it detects the iGPU is probed but dGPU.
However, the display is attached to dGPU.
We need to make sure the targeted gpu (connecting to monitor) is probe
before launching gdm.
[1] https://www.freedesktop.org/wiki/Software/systemd/multiseat/
/lib/udev/rules.d/71-seat.rules
/lib/udev/rules.d/71-nvidia.rules
** Description changed:
[Impact]
- * In Ubuntu 20.04 (which using Xorg with proprietary nvidia driver), in some
cases, the nvidia driver will probe later than launching gdm.
- * If above race condition happens in iGPU + nvidia cases and monitor
connects to dGPU, which will cause gdm starts with wayland as opposed to Xorg.
Which may lead the monitor stuck in black-screen or boot LOGO.
+ * In Ubuntu 20.04 (which using Xorg with proprietary nvidia driver), in some
cases, the nvidia driver will probe later than launching gdm.
+ * If above race condition happens in iGPU + nvidia cases and monitor
connects to dGPU, which will cause gdm starts with wayland as opposed to Xorg.
Which may lead the monitor stuck in black-screen or boot LOGO.
[Test Plan]
- * The environment:
- 1. A desktop or workstation which containing an iGPU.
- 2. Plug a nvidia graphic card to the system and installing proprietary
- nvidia driver (470 in my case)
- 3. Attach a monitor to dGPU and leave iGPU connect to nothing.
- (in my test environment, there is the other ethernet card and TBT4 cards)
- * Setup a cronjob,
-e.g. @reboot /home/u/test.sh
- * Have a test script in something like /home/u/test.sh as
+ * The environment:
+ 1. A desktop or workstation which containing an iGPU.
+ 2. Plug a nvidia graphic card to the system and installing proprietary
+ nvidia driver (470 in my case)
+ 3. Attach a monitor to dGPU and leave iGPU
[Bug 1958488] Re: [nvidia][xorg] display hangs on boot LOGO
"boot_vga" only exists for PCI device, so this change will make VMs and boards that don't use PCI GFX wait for straight 10 seconds. -- 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/1958488 Title: [nvidia][xorg] display hangs on boot LOGO To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1958488/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1958488] Re: [nvidia][xorg] display hangs on boot LOGO
Note that gnome-shell (which also renders the login screen for gdm) always uses the primary iGPU for rendering regardless of whether some monitors are plugged into a dGPU port. The latter get their framebuffers rendered on the iGPU but copied to the dGPU for output on every frame. This makes sense for the common dual-GPU case of a laptop where you want to be able to connect an external monitor to any port (even if that port is wired to dGPU) while still using the iGPU for efficiency by default. But enough from me. You should propose any patches to https://gitlab.gnome.org/GNOME/gdm/ (or to https://gitlab.gnome.org/GNOME/mutter) to get more authoritative information from the developers. -- 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/1958488 Title: [nvidia][xorg] display hangs on boot LOGO To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1958488/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1958488] Re: [nvidia][xorg] display hangs on boot LOGO
This patch doesn't need to apply to jammy/impish because debian/patches/gdm.rules-Keep-wayland-enabled-in-all-nvidia-configuratio.patch Please let me know if my assumption is incorrect. -- 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/1958488 Title: [nvidia][xorg] display hangs on boot LOGO To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1958488/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1958488] Re: [nvidia][xorg] display hangs on boot LOGO
for focal ** Patch added: "lp1958488_gdm-wait-for-drm_wait_for_boot_vga.debdiff" https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1958488/+attachment/742/+files/lp1958488_gdm-wait-for-drm_wait_for_boot_vga.debdiff ** Tags added: oem-priority originate-from-1956556 sutton ** Changed in: oem-priority Assignee: (unassigned) => jeremyszu (os369510) ** Changed in: oem-priority Importance: Undecided => Critical ** Changed in: oem-priority Status: New => In Progress -- 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/1958488 Title: [nvidia][xorg] display hangs on boot LOGO To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1958488/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1958488] [NEW] [nvidia][xorg] display hangs on boot LOGO
Public bug reported:
Test environment/steps:
1. A desktop or workstation which containing an iGPU.
2. Plug a nvidia graphic card to the system and installing proprietary nvidia
driver (470 in my case)
3. Attach a monitor to dGPU and leave iGPU connect to nothing.
(in my test environment, there is the other ethernet card and TBT4 cards)
4. Reboot system.
Based on:
$ cat /lib/udev/rules.d/61-gdm.rules
# disable Wayland on Hi1710 chipsets
ATTR{vendor}=="0x19e5", ATTR{device}=="0x1711",
RUN+="/usr/lib/gdm3/gdm-disable-wayland"
# disable Wayland when using the proprietary nvidia driver
DRIVER=="nvidia", RUN+="/usr/lib/gdm3/gdm-disable-wayland"
It will disable wayland by default if proprietary nvidia driver load.
But in some race condition cases, the nvidia probe is later than gnome
launches. (The fail rate is 6/24.)
Thus, ubuntu-gdm has a fix for Bug#1794280 to add
"ExecStartPre=@libexecdir@/gdm-wait-for-drm".
The gdm-wait-for-drm is intend to make sure all drm udev devices enumerated
before launching gdm.
It rely on at least one "master-of-seat" graphic card for gdm but it's not
rigorous enough.
Since most of graphic cards are own "master-of-seat"[1].
In my case, it detects the iGPU is probed but dGPU.
However, the display is attached to dGPU.
We need to make sure the targeted gpu (connecting to monitor) is probe
before launching gdm.
[1] https://www.freedesktop.org/wiki/Software/systemd/multiseat/
/lib/udev/rules.d/71-seat.rules
/lib/udev/rules.d/71-nvidia.rules
** Affects: gdm3 (Ubuntu)
Importance: Undecided
Assignee: jeremyszu (os369510)
Status: New
** Changed in: gdm3 (Ubuntu)
Assignee: (unassigned) => jeremyszu (os369510)
** Description changed:
- Test environment:
+ Test environment/steps:
1. A desktop or workstation which containing an iGPU.
2. Plug a nvidia graphic card to the system and installing proprietary nvidia
driver (470 in my case)
3. Attach a monitor to dGPU and leave iGPU connect to nothing.
(in my test environment, there is the other ethernet card and TBT4 cards)
4. Reboot system.
Based on:
- $ cat /lib/udev/rules.d/61-gdm.rules
+ $ cat /lib/udev/rules.d/61-gdm.rules
# disable Wayland on Hi1710 chipsets
ATTR{vendor}=="0x19e5", ATTR{device}=="0x1711",
RUN+="/usr/lib/gdm3/gdm-disable-wayland"
# disable Wayland when using the proprietary nvidia driver
DRIVER=="nvidia", RUN+="/usr/lib/gdm3/gdm-disable-wayland"
It will disable wayland by default if proprietary nvidia driver load.
- But in some race condition cases, the nvidia probe is later than gnome
launches.
+ But in some race condition cases, the nvidia probe is later than gnome
launches. (The fail rate is 6/24.)
Thus, ubuntu-gdm has a fix for Bug#1794280 to add
"ExecStartPre=@libexecdir@/gdm-wait-for-drm".
- The gdm-wait-for-drm is intend to make sure all drm udev devices
- enumerated before launching gdm.
+
+ The gdm-wait-for-drm is intend to make sure all drm udev devices enumerated
before launching gdm.
It rely on at least one "master-of-seat" graphic card for gdm but it's not
rigorous enough.
Since most of graphic cards are own "master-of-seat"[1].
In my case, it detects the iGPU is probed but dGPU.
However, the display is attached to dGPU.
We need to make sure the targeted gpu (connecting to monitor) is probe
before launching gdm.
[1] https://www.freedesktop.org/wiki/Software/systemd/multiseat/
/lib/udev/rules.d/71-seat.rules
/lib/udev/rules.d/71-nvidia.rules
--
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/1958488
Title:
[nvidia][xorg] display hangs on boot LOGO
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1958488/+subscriptions
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1867578] Re: gnome-shell crashed with SIGABRT in __GI_raise() from __GI_abort() from g_assertion_message() from g_assertion_message_expr() from clutter_actor_set_mapped() [assertion failed: (!CLU
Possibly related to https://gitlab.gnome.org/GNOME/gnome- shell/-/issues/4957 ** Bug watch added: gitlab.gnome.org/GNOME/gnome-shell/-/issues #4957 https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/4957 -- 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/1867578 Title: gnome-shell crashed with SIGABRT in __GI_raise() from __GI_abort() from g_assertion_message() from g_assertion_message_expr() from clutter_actor_set_mapped() [assertion failed: (!CLUTTER_ACTOR_IS_MAPPED (self))] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1867578/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1958017] Re: [nvidia] Screen scaling reset every reboot
*** This bug is a duplicate of bug 1942653 *** https://bugs.launchpad.net/bugs/1942653 On second thoughts this is really the same kind of issue as bug 1942653. ** This bug has been marked a duplicate of bug 1942653 RandR fractional scaling patch interferes with manual RandR output scaling -- 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/1958017 Title: [nvidia] Screen scaling reset every reboot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1958017/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1942653] Re: RandR fractional scaling patch interferes with manual RandR output scaling
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 Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1942653 Title: RandR fractional scaling patch interferes with manual RandR output scaling To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1942653/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1952107] Re: Google Contacts API Deprecated
** Tags removed: verification-needed-impish ** Tags added: verification-done-impish -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to evolution in Ubuntu. https://bugs.launchpad.net/bugs/1952107 Title: Google Contacts API Deprecated To manage notifications about this bug go to: https://bugs.launchpad.net/evolution-data-server/+bug/1952107/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1952107] Re: Google Contacts API Deprecated
(... Ubuntu 21.10) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to evolution in Ubuntu. https://bugs.launchpad.net/bugs/1952107 Title: Google Contacts API Deprecated To manage notifications about this bug go to: https://bugs.launchpad.net/evolution-data-server/+bug/1952107/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1952107] Re: Google Contacts API Deprecated
I used proposed-updates today to get the latest evolution, and contact sync works again. So 3.40.4-1ubuntu2 works. (amd64 arch) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to evolution in Ubuntu. https://bugs.launchpad.net/bugs/1952107 Title: Google Contacts API Deprecated To manage notifications about this bug go to: https://bugs.launchpad.net/evolution-data-server/+bug/1952107/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1927100] Re: Slow file dialogs, open and save
I created an (installed) VM of Ubuntu Mate, since that was the original report. My main affected workstation sees long uptimes, many transient podman containers and fuse mounts, temporary files, etc. that are not easily duplicated in a VM--I'm not sure if all/any of that contributes to the hanging. I can at least leave the VM running with a) files in the trash, and b) `gio info trash:///` running in a loop to see if it reproduces at some point. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/1927100 Title: Slow file dialogs, open and save To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1927100/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1958435] [NEW] Icons on Dock get stuck in Dragging Mode
Public bug reported: $ lsb_release -rd Description:Ubuntu 18.04.6 LTS Release:18.04 $ apt-cache policy gnome-shell-extension-ubuntu-dock gnome-shell-extension-ubuntu-dock: Installed: 0.9.1ubuntu18.04.3 Candidate: 0.9.1ubuntu18.04.3 Version table: *** 0.9.1ubuntu18.04.3 500 500 http://us.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 500 http://us.archive.ubuntu.com/ubuntu bionic-updates/main i386 Packages 100 /var/lib/dpkg/status 0.9.1 500 500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages 500 http://us.archive.ubuntu.com/ubuntu bionic/main i386 Packages What I expect to happen: When I drag an icon on the Dock, I expect the dragging to finish once I release the mouse. What happened instead: The icon gets stuck in dragging mode. When my mouse clicks on the icon that was previously dragged, the icon gets stuck to the mouse cursor as if I were dragging it. Related bug reports: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1880764 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-shell-extension-ubuntu-dock 0.9.1ubuntu18.04.3 ProcVersionSignature: Ubuntu 5.4.0-94.106~18.04.1-generic 5.4.157 Uname: Linux 5.4.0-94-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.27 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Jan 19 12:38:15 2022 InstallationDate: Installed on 2019-10-04 (837 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-shell-extension-ubuntu-dock UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-shell-extension-ubuntu-dock (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic ** Description changed: $ lsb_release -rd Description: Ubuntu 18.04.6 LTS Release: 18.04 - $ apt-cache policy gnome-shell-extension-ubuntu-dock + $ apt-cache policy gnome-shell-extension-ubuntu-dock gnome-shell-extension-ubuntu-dock: - Installed: 0.9.1ubuntu18.04.3 - Candidate: 0.9.1ubuntu18.04.3 - Version table: - *** 0.9.1ubuntu18.04.3 500 - 500 http://us.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages - 500 http://us.archive.ubuntu.com/ubuntu bionic-updates/main i386 Packages - 100 /var/lib/dpkg/status - 0.9.1 500 - 500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages - 500 http://us.archive.ubuntu.com/ubuntu bionic/main i386 Packages + Installed: 0.9.1ubuntu18.04.3 + Candidate: 0.9.1ubuntu18.04.3 + Version table: + *** 0.9.1ubuntu18.04.3 500 + 500 http://us.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages + 500 http://us.archive.ubuntu.com/ubuntu bionic-updates/main i386 Packages + 100 /var/lib/dpkg/status + 0.9.1 500 + 500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages + 500 http://us.archive.ubuntu.com/ubuntu bionic/main i386 Packages What I expect to happen: When I drag an icon on the Dock, I expect the dragging to finish once I release the mouse. What happened instead: - The icon gets stuck in dragging mode. When my mouse moves over the icon that was previously dragged, the icon gets stuck to the mouse cursor as if I were dragging it. + The icon gets stuck in dragging mode. When my mouse clicks on the icon that was previously dragged, the icon gets stuck to the mouse cursor as if I were dragging it. Related bug reports: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1880764 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-shell-extension-ubuntu-dock 0.9.1ubuntu18.04.3 ProcVersionSignature: Ubuntu 5.4.0-94.106~18.04.1-generic 5.4.157 Uname: Linux 5.4.0-94-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.27 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Jan 19 12:38:15 2022 InstallationDate: Installed on 2019-10-04 (837 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) PackageArchitecture: all ProcEnviron: - TERM=xterm-256color - PATH=(custom, no user) - XDG_RUNTIME_DIR= - LANG=en_US.UTF-8 - SHELL=/bin/bash + TERM=xterm-256color + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=en_US.UTF-8 + SHELL=/bin/bash SourcePackage: gnome-shell-extension-ubuntu-dock UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell-extension-ubuntu-dock in Ubuntu. https://bugs.launchpad.net/bugs/1958435 Title: Icons on Dock get stuck in Dragging Mode To manage
[Bug 1943849] Re: [FFe] improve the appearance-page in gnome-control-center
Hi @robert.ancell Could you please push a ubuntu-41 branch on the gitlab. So that I can create the MR again for this there. -- 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/1943849 Title: [FFe] improve the appearance-page in gnome-control-center To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1943849/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 738926] Re: Seahorse show a many password
I'm not sure I understand what the problem might be here. So let me ask first if this is still an issue you can reproduce. ** Changed in: seahorse (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to seahorse in Ubuntu. https://bugs.launchpad.net/bugs/738926 Title: Seahorse show a many password To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/seahorse/+bug/738926/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 418436] Re: problems with seahorse in karmic
upstream ticket was closed for lack of response. Is this still an issue that is relevant and present in Ubuntu? ** Changed in: seahorse (Ubuntu) Status: Triaged => Incomplete -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug assignee. https://bugs.launchpad.net/bugs/418436 Title: problems with seahorse in karmic To manage notifications about this bug go to: https://bugs.launchpad.net/seahorse/+bug/418436/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1958398] [NEW] seahorse does not show in HUD for "gpg"
Public bug reported: Seahorse does not show as an option when typing "gpg" in HUD but it should. It is being offered as a choice when typing "password". ** Affects: seahorse (Ubuntu) Importance: Undecided Status: New ** Tags: focal -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to seahorse in Ubuntu. https://bugs.launchpad.net/bugs/1958398 Title: seahorse does not show in HUD for "gpg" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/seahorse/+bug/1958398/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1927100] Re: Slow file dialogs, open and save
Is there nobody using Ubuntu itself who will be able to help test at all? Is anyone willing to fire up an Ubuntu live image to help test it there? If so, maybe it's worth seeing if the race reproduces in a live environment on Ubuntu first? -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/1927100 Title: Slow file dialogs, open and save To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1927100/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1935668] Re: xdg-desktop-portal FTBFS when built with libfuse3-dev
This is fixed in 1.12.1-1ubuntu1: * debian/conrol: - switch to fuse3 * debian/patches/gitlab-use-fuse3.patch: - cherry pick the PR from Trevinho to use fuse3 since it was reviewed by James and wanted for the LTS ** Changed in: xdg-desktop-portal (Ubuntu) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to xdg-desktop-portal in Ubuntu. https://bugs.launchpad.net/bugs/1935668 Title: xdg-desktop-portal FTBFS when built with libfuse3-dev To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xdg-desktop-portal/+bug/1935668/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1958209] Re: Not responding after connecting to a hotpot Hidden Network
apport information ** Tags added: apport-collected focal ** Description changed: Ubuntu 20.04. Steps to reproduce: 1. Run gnome-control-center/Wi-Fi. 2. Connect to a Hidden Network (a hotspot in my case). 3. After connection, click the network settings. What I expect to happen: Get the connection information. What happens: After a few seconds, a box appears with the message: "Settings is not responding", and I have to Force Quit. This happens only after the first time I run gnome-control-center and make the connection. from syslog: Jan 18 09:06:43 moshe gnome-control-c[1863]: cannot register existing type 'WirelessSecurity' Jan 18 09:06:43 moshe gnome-control-c[1863]: g_type_interface_add_prerequisite: assertion 'G_TYPE_IS_INTERFACE (interface_type)' failed Jan 18 09:06:43 moshe gnome-control-c[1863]: g_once_init_leave: assertion 'result != 0' failed Jan 18 09:06:43 moshe gnome-control-c[1863]: ../../../../gtk/gtkliststore.c:434: Invalid type (null) Jan 18 09:06:43 moshe gnome-control-c[1863]: gtk_list_store_insert_with_values: assertion 'GTK_IS_LIST_STORE (list_store)' + --- + ProblemType: Bug + ApportVersion: 2.20.11-0ubuntu27.21 + Architecture: amd64 + CasperMD5CheckResult: skip + CurrentDesktop: ubuntu:GNOME + DistroRelease: Ubuntu 20.04 + InstallationDate: Installed on 2019-04-03 (1021 days ago) + InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) + Package: gnome-control-center 1:3.36.5-0ubuntu3 + PackageArchitecture: amd64 + ProcEnviron: + LANGUAGE=en_IL:en + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=en_IL + SHELL=/bin/bash + ProcVersionSignature: Ubuntu 5.4.0-94.106-generic 5.4.157 + Tags: focal + Uname: Linux 5.4.0-94-generic x86_64 + UpgradeStatus: Upgraded to focal on 2020-08-12 (524 days ago) + UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo wireshark + _MarkForUpload: True ** Attachment added: "Dependencies.txt" https://bugs.launchpad.net/bugs/1958209/+attachment/383/+files/Dependencies.txt -- 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/1958209 Title: Not responding after connecting to a hotpot Hidden Network To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1958209/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1958209] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1958209/+attachment/384/+files/ProcCpuinfoMinimal.txt -- 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/1958209 Title: Not responding after connecting to a hotpot Hidden Network To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1958209/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
