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 happ
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 Ubu
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 Progre
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
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
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.
h
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
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/bug
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
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
(... 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.launch
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/195
** 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
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/194
*** 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
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, w
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
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
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
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
"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
** 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 start
--
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-pr
23 matches
Mail list logo
