Are we sure that this is fixed? It seems to still be happening.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1719612
Title:
non-us keyboard layout not setup in initramfs
To manage notifications ab
Public bug reported:
https://github.com/pop-os/pop/issues/370
** Affects: gnome-control-center (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1
Public bug reported:
Occasionally when launching the calendar from the overview, it segfaults
at startup. This does not seem to happen when launched from the
terminal. Logs from journald:
Oct 03 11:37:50 pop-os gnome-calendar[8992]: gtk_widget_get_scale_factor:
assertion 'GTK_IS_WIDGET (widget)'
Details from address sanitizer:
Oct 03 11:46:38 pop-os org.gnome.Calendar[3834]: AddressSanitizer:DEADLYSIGNAL
Oct 03 11:46:38 pop-os org.gnome.Calendar[3834]:
=
Oct 03 11:46:38 pop-os org.gnome.Calendar[3834]: ==11918==ERROR:
Addre
AddressSanitizer:DEADLYSIGNAL
=
==11918==ERROR: AddressSanitizer: SEGV on unknown address 0x0006 (pc
0x7f58b1ab7c7d bp 0x0002 sp 0x7ffd3aad4da0 T0)
==11918==The signal is caused by a READ memory access.
==11918==Hint:
However, it's unknown when the issue is going to be fixed. So for now
I'm carrying it in Pop!_OS 18.04, 19.04, and 19.10 at the moment.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1838329
Title:
C
At System76, we've been carrying this patch for 18.04 and 18.10, to
solve the issue.
** Patch added: "fix_nvidia_suspend.patch"
https://bugs.launchpad.net/gnome-desktop/+bug/1731318/+attachment/5224694/+files/fix_nvidia_suspend.patch
--
You received this bug notification because you are a me
@seb128 I guess that means we'll have to keep carrying the patch
ourselves for bionic in our repos.
Personally, I think you should reconsider it if the desktop is part of
your "Long Term Support".
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
Making a note that we are also carrying this it in the 19.04 (disco)
release now.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1731318
Title:
NVIDIA systems will not suspend with lid close and no e
Public bug reported:
With the package currently proposed for 20.04, NVIDIA systems are
experiencing very small text in GDM and GNOME Shell. Removing x11-Add-
support-for-fractional-scaling-using-Randr.patch fixes it.
** Affects: mutter (Ubuntu)
Importance: Undecided
Status: New
--
We (System76) were able to replicate the issue on most of our NVIDIA
laptops in NVIDIA mode, with the exception of the addw1. We've therefore
repackaged mutter in Pop without the patch, so it's no longer a problem
for us.
You can find screenshots of the problem in this issue:
https://github.com/po
The issue is super small text in all GDM and GNOME Shell elements when
the display is being driven by NVIDIA graphics. The problem is caused by
the patch in the title. If you switch to Intel graphics, the text is
back to normal. If you switch to NVIDIA, the text shrinks down to what
looks like 50%
For what it's worth, the only difference between Ubuntu and Pop
regarding Mutter is that we've removed the xrandr patching causing this
issue. We tested the most recent version of the patch in proposed for
Focal at this time, and the issue still occurs there. Given that it's an
experimental feature
Updating this to state that GNOME has yet to make a decision on how to
approach this, but whatever decision they make will not consist of
sharing an application-specific variable with GDM.
They seem to be hinting that they will create a global variable that
applications can use, but they've yet to
This still occurs in 19.04 with nvidia-driver-418.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1769857
Title:
Vulkan not working if nvidia-drm.modeset=1 is set and gdm3 is used
(Optimus)
To man
Public bug reported:
When the `PrintScrn` key is pressed in GNOME Shell, it takes a
screenshot and writes it to `$HOME/Pictures`, or otherwise falling back
to `$HOME` if that directory is not found. The `gnome-screenshot` tool
does a similar action, but also checks for the existence of the `auto-
Canonical still does not carry this or many other patches we've made for
Pop!_OS to improve NVIDIA support. If you want a better experience for
your hardware, I'd recommend to install Pop!_OS. We've been carrying the
patch you mentioned since 17.10, so it is enabled in both our 18.04 LTS
and 19.04
Public bug reported:
When attempting to rename a .desktop file in Ubuntu 18.04, .desktop is
automatically appended. This causes the .desktop extension to get
duplicated, where renaming `app.desktop` to `app2.desktop` will actually
rename it to `app2.desktop.desktop`. The included patch fixes the i
** Patch removed: ".desktop rename patch for Nautilus"
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1774094/+attachment/5146234/+files/desktop-rename.patch
** Patch added: ".desktop rename patch for Nautilus"
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1774094/+attac
** Summary changed:
- [Patch Included] 3.26.3-0ubuntu4 .desktop extension is duplicated when
renaming a .desktop file
+ [18.04] [3.26.3-0ubuntu4] .desktop extension is duplicated when renaming a
.desktop file
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
GNOME merged the changes for their 3.26 branch, so it's now up to Ubuntu
to make their move for 18.04
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1774094
Title:
[18.04] [3.26.3-0ubuntu4] .desktop
Submitted PR upstream to Nautilus' 3.26 branch:
https://gitlab.gnome.org/GNOME/nautilus/merge_requests/241/diffs
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1774094
Title:
[18.04] [3.26.3-0ubuntu4
This breaks bazel [1], and thus makes it impossible to package
TensorFlow for 18.04.
[1] https://github.com/bazelbuild/bazel/issues/5099
** Bug watch added: github.com/bazelbuild/bazel/issues #5099
https://github.com/bazelbuild/bazel/issues/5099
--
You received this bug notification because
Public bug reported:
On some systems, cryptsetup-based encrypted swap partitions cause
systemd to get stuck at boot. This is a timing-sensitive Heisenbug, so
the rate of occurrence varies from one system to another. Some hardware
will not experience the issue at all, others will only occasionally
Fixed 2 days ago in updated gdm package.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1969121
Title:
System fallback to gdm login screen when hot-plugging a external
monitor in 1st time
To manag
25 matches
Mail list logo