This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
bionic' to 'verification-done-bionic'. If the problem still exists,
change the tag
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
groovy' to 'verification-done-groovy'. If the problem still exists,
change the tag
Thank you for using Ubuntu and taking the time to report a bug. Your
report should contain, at a minimum, the following information so we can
better find the source of the bug and work to resolve it.
Submitting the bug about the proper source package is essential. For
help see
Thanks for taking the time to report this bug and helping to make Ubuntu
better. We appreciate the difficulties you are facing, but this appears
to be a "regular" (non-security) bug. I have unmarked it as a security
issue since this bug does not show evidence of allowing attackers to
cross
Note that meet + chrome is unusable with auto_switch=2 and bose QC35 II.
I only managed to make it work once when initially investigating the
option. I haven't been able to make a single google meet call with
chrome ever since I activated that option, I must regularly start
firefox specifically
Public bug reported:
I am running 3 monitors under wayland.
2x 1440p monitors at 1x scale (one of these is my primary display)
1x 4k laptop at 2x scale
The majority apps seem to not get correct scaling on the 2x display.
gnome-control-center is the one that seems to work correctly. Things
like
Actually it does kind of look like this might have been bug 1897765.
Anyway, if the problem returns then please comment here and we can
reopen it.
** No longer affects: mutter
** Changed in: mutter (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notification because you
Hey Daniel! I can't reproduce the issue anymore. So maybe it was related
to one of the fixed bugs.
--
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/1908878
Title:
[nvidia] gnome shell
The assertion failure might not even be in st_bin_get_preferred_width at
all. That might be a red herring caused by lack of debug symbols.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: nvidia-graphics-drivers-340 (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to nvidia-graphics-drivers-340 in
Incomplete because we don't have any line number info, any log messages
telling us what the assertion is, or any test case.
We're left to guess, and my guess is either:
* An inlined function with an explicit assertion; or
* One of these macros:
StBinPrivate *priv =
The issue is being tracked in bug 1913672.
--
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/1897765
Title:
gnome-shell crashed with signal 5 in g_log("Error in freeze/thaw
https://errors.ubuntu.com/problem/4f12318421d8c95c357e2db953aa75b2cdcacdfa
https://errors.ubuntu.com/problem/0b6c9d77c0cae16f6672a684255ddd3dde92aabc
https://errors.ubuntu.com/problem/0447ee3910962f0195cdad658227957b305b14e2
** Summary changed:
-
*** This bug is a duplicate of bug 1913672 ***
https://bugs.launchpad.net/bugs/1913672
** This bug has been marked a duplicate of bug 1913672
/usr/bin/gnome-shell:6:g_assertion_message:g_assertion_message_expr:st_bin_get_preferred_width:g_hash_table_lookup:signal_emit_unlocked_R
--
You
*** This bug is a duplicate of bug 1913672 ***
https://bugs.launchpad.net/bugs/1913672
** This bug has been marked a duplicate of bug 1913672
/usr/bin/gnome-shell:6:g_assertion_message:g_assertion_message_expr:st_bin_get_preferred_width:g_hash_table_lookup:signal_emit_unlocked_R
--
You
Public bug reported:
The Ubuntu Error Tracker has been receiving reports about a problem regarding
gnome-shell. This problem was most recently seen with package version
3.38.2-1ubuntu1~20.10.1, the problem page at
https://errors.ubuntu.com/problem/4f12318421d8c95c357e2db953aa75b2cdcacdfa
*** This bug is a duplicate of bug 1913672 ***
https://bugs.launchpad.net/bugs/1913672
Public bug reported:
The Ubuntu Error Tracker has been receiving reports about a problem regarding
gnome-shell. This problem was most recently seen with package version
3.38.2-1ubuntu1~20.10.1, the
I don't know the answer but will pass it on. Thanks for pointing that
out...
https://people.canonical.com/~ubuntu-archive/phased-updates.html
https://askubuntu.com/q/1311421
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in
My guess is that it's because there have been some automated crash
reports associated with the updates, so the phasing stopped. This is
normal and we need to explain how/why each one is not a regression.
--
You received this bug notification because you are a member of Desktop
Packages, which is
*** This bug is a duplicate of bug 1913672 ***
https://bugs.launchpad.net/bugs/1913672
Public bug reported:
The Ubuntu Error Tracker has been receiving reports about a problem regarding
gnome-shell. This problem was most recently seen with package version
3.38.2-1ubuntu1~20.10.1, the
Command line apt users may not notice, but the fix has been phased out
the day it was released on updates, and the percentile has been
remaining at 0% since then.
As a consequence, update-manager users won't get the update. Is it
wanted behaviour (i.e. a manual, explicit phase-out), or is there
[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 Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
[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 gnome-shell in Ubuntu.
[Expired for xorg-server (Ubuntu) because there has been no activity for
60 days.]
** Changed in: xorg-server (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg-server in Ubuntu.
[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 Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
Oh actually maybe upstream already answered that:
https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/issues/637
--
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/508522
I think the right answer is to ask upstream first so we don't have to
carry more customizations which we don't understand as well as they do.
And someone already did:
https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/issues/81
So for the moment we are waiting on a reply.
** Bug watch
I think we can exclude actual crashes here. Although you did experience
bug 1897765 in the past, that should be fixed now.
Next is to figure out which freeze it is:
"MetaSyncRing: Sync object is not ready"
or
"Failed to grab accelerators:
** No longer affects: mutter
** Summary changed:
- [nvidia] gnome shell freezes for a couple of seconds, then it restarts (maybe
it crashes?)
+ [nvidia] gnome shell freezes for a couple of seconds
** Changed in: mutter (Ubuntu)
Status: Incomplete => New
** Also affects: mutter via
*** This bug is a duplicate of bug 1856032 ***
https://bugs.launchpad.net/bugs/1856032
Although you're probably using the Ubuntu Dock, which would make it a
duplicate of bug 1856032. If that's not correct then please follow the
steps in comment #1.
** This bug has been marked a duplicate of
*** This bug is a duplicate of bug 1856032 ***
https://bugs.launchpad.net/bugs/1856032
Please:
1. Attach a screenshot of the problem so we can see which dock you mean;
and
2. Run this command to automatically gather more system info:
apport-collect 1913662
In future please try to use
Thanks for the bug report. It appears the affected monitor is connected
to the Nvidia GPU, but your system doesn't seem to have the Nvidia
driver loaded properly. This might be an installation issue or it might
be an incompatibility between needing 'modeset' enabled for the amdgpu
driver, and
Here's the decoded EDID of the affected monitor on HDMI-1-0:
EDID version: 1.3
Manufacturer: BNQ Model 30926 Serial Number 21573
Made in week 3 of 2015
Digital display
Maximum image size: 53 cm x 30 cm
Gamma: 2.20
DPMS levels: Off
RGB color display
Default (sRGB) color space is primary color
Instead of waiting for a fix to be released you can actually hack it
into your /usr/share/gnome-shell/extensions/auto-move-windows@gnome-
shell-extensions.gcampax.github.com/extension.js
@@ -72,7 +72,7 @@ class WindowMover {
}
_moveWindow(window, workspaceNum) {
-if
There is also a general fix for gnome-shell proposed here:
https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1692
** Package changed: gnome-shell (Ubuntu) => mutter (Ubuntu)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to
Bugs are never closed "randomly". Only those that are:
* Fixed; or
* Don't have enough information and the reporter fails to respond to
questions for 60+ days; or
* Aren't immediately reproducible, and have no evidence of affecting a
currently supported release, and the user fails to respond
Public bug reported:
jlquinn@cerberus:~/Videos$ lsb_release -rd
Description:Ubuntu 20.04.1 LTS
Release:20.04
jlquinn@cerberus:~/Videos$ apt-cache policy gnome-shell
gnome-shell:
Installed: 3.36.4-1ubuntu1~20.04.2
Candidate: 3.36.4-1ubuntu1~20.04.2
Version table:
***
Having the clock at the right end of the top bar would not only solve
the problem, but also give more (needed) space to those
icons/AppIndicators.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell-extension-appindicator in
I just tried this now on a freshly installed Ubuntu 20.04 with kernel
5.8.0-41-generic and it works great in both Gnome and in Chromium. Happy
to mark this resolved.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to alsa-driver in Ubuntu.
Public bug reported:
$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 20.04.1 LTS
Release:20.04
Codename: focal
$ apt-cache policy firefox
firefox:
Installed: 84.0.2+build1-0ubuntu0.20.04.1
Candidate: 84.0.2+build1-0ubuntu0.20.04.1
Public bug reported:
Ghostscript 9.50 exhibits bug 701894 (fix the '--' and co options) which
causes (eg) ocrfeeder to fail to load PDF files: an input file specified
using the "... -- filename ..." command line syntax has no read
permission in the GS interpreter.
This commit fixes it:
(Sorry for #43, wrong bug/thread - but yes, the same goes for .p12 at
the versions stated.)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-keyring in Ubuntu.
https://bugs.launchpad.net/bugs/1771880
Title:
Seahorse unable to
** Also affects: ubuntu-drivers-common (Ubuntu Groovy)
Importance: Undecided
Status: New
** Changed in: ubuntu-drivers-common (Ubuntu Groovy)
Status: New => Triaged
** Changed in: ubuntu-drivers-common (Ubuntu Groovy)
Importance: Undecided => High
--
You received this bug
Still unable to import openssh-formatted RSA PRIVATE KEYs on Ubuntu
20.04.1 LTS / Gnome 3.36.8 / Seahorse 3.36-1
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-keyring in Ubuntu.
https://bugs.launchpad.net/bugs/1771880
Title:
xnox suggests using $XDG_RUNTIMEDIR which is /run/user/1000 and
writable.
Also using 'with open' would be better.
** Also affects: ubuntu-drivers-common (Ubuntu Focal)
Importance: Undecided
Status: New
** Changed in: ubuntu-drivers-common (Ubuntu)
Status: New => Triaged
**
Public bug reported:
That's all
ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: tex-common 6.13
ProcVersionSignature: Ubuntu 5.4.0-64.72-generic 5.4.78
Uname: Linux 5.4.0-64-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.14
AptOrdering:
linux-modules-extra-5.4.0-60-generic:amd64:
Here's the Traceback:
Traceback (most recent call last):
File "/usr/bin/ubuntu-drivers", line 480, in
greet()
File "/usr/lib/python3/dist-packages/click/core.py", line 829, in __call__
return self.main(*args, **kwargs)
File "/usr/lib/python3/dist-packages/click/core.py", line 782,
This is affecting me in a fresh Ubuntu 18.04 installation. Thank's for
the temporary solution, @Ernst.
Here is a related question (made 9 months prior to this bug report
openning) on the TeX StackExchange website:
https://tex.stackexchange.com/questions/431244/texdoc-does-not-work-
Public bug reported:
The Ubuntu Error Tracker has been receiving reports about a problem
regarding ubuntu-drivers-common. This problem was most recently seen
with package version 1:0.8.6.3~0.20.10.1, the problem page at
https://errors.ubuntu.com/problem/a5320fbf71298787ff2595cc2b8227783b068dae
** Summary changed:
- Closing upon moving file to bookmarked folder
+ Closing by itself upon moving file to bookmarked folder
** Description changed:
Problem encountered not before Ubuntu update 18.04.latest to 20.04.2.
Prerequisites:
Few folders are bookmarked to side bar.
Move a
Public bug reported:
Problem encountered not before Ubuntu update 18.04.latest to 20.04.2.
Prerequisites:
Few folders are bookmarked to side bar.
Move a file from folder in Nautilus window to one of bookmarked folders, do it
by drag and drop.
When dragging over bookmark of move destination
Related to #1911649
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to firefox in Ubuntu.
https://bugs.launchpad.net/bugs/1913570
Title:
Firefox not opening file chooser dialog for importing certificates
Status in firefox package in
Public bug reported:
1) Ubuntu version: Ubuntu 20.04.1 LTS
2) Package version: yaru-theme-gtk version 20.04.10.1
For example when hovering over an item in the left panel of Gnome Files,
a tooltip is displayed.
When yaru-theme-gtk version 20.04.6 is installed, the background color
of the
Sorry, I switched distros. I'm on Fedora now. I see Vincent reproduced
it. Can you please collect the bug info Vincent?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to firefox in Ubuntu.
https://bugs.launchpad.net/bugs/1908082
Title:
This bug was fixed in the package wpa - 2:2.9-1ubuntu10
---
wpa (2:2.9-1ubuntu10) hirsute; urgency=medium
* debian/patches/git_dbus_bridge.patch
- Allow changing an interface bridge via D-Bus (lp: #1893563)
[ Andrej Shadura ]
* Security fix: CVE-2020-12695.
A
This bug was fixed in the package wpa - 2:2.9-1ubuntu10
---
wpa (2:2.9-1ubuntu10) hirsute; urgency=medium
* debian/patches/git_dbus_bridge.patch
- Allow changing an interface bridge via D-Bus (lp: #1893563)
[ Andrej Shadura ]
* Security fix: CVE-2020-12695.
A
Thank you for your bug report, that's a bug to report to popOS or
upstream (https://gitlab.freedesktop.org/pulseaudio/pulseaudio/) though
since you aren't using Ubuntu
** Package changed: systemd (Ubuntu) => pulseaudio (Ubuntu)
** Changed in: pulseaudio (Ubuntu)
Importance: Undecided => Low
Any progress on this?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to ubuntu-meta in Ubuntu.
https://bugs.launchpad.net/bugs/1886314
Title:
preinstall `earlyoom` by default
Status in ubuntu-meta package in Ubuntu:
New
Bug
** Changed in: ubuntu-meta (Ubuntu)
Status: New => Incomplete
** Changed in: ubuntu-meta (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to ubuntu-meta in Ubuntu.
** Changed in: ubuntu-meta (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to ubuntu-meta in Ubuntu.
https://bugs.launchpad.net/bugs/1884932
Title:
Install pulseaudio-module-gsettings by default
** Changed in: software-properties (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to software-properties in Ubuntu.
https://bugs.launchpad.net/bugs/1882500
Title:
software-properties-qt: add
You have been subscribed to a public bug:
Ubuntu 20.10 (PopOS on a custom Skylake generation server, not System76)
Problem started occurring after upgrade from Ubuntu 20.04 to Ubuntu
20.10 PopOS. System never experienced this problem before that upgrade
and it's a 5 year old server.
Pulseaudio
All autopkgtests for the newly accepted ubuntu-drivers-common
(1:0.8.6.3~0.18.04.1) for bionic have finished running.
The following regressions have been reported in tests triggered by the package:
software-properties/0.96.24.32.14 (amd64)
Please visit the excuses page listed below and
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
xenial' to 'verification-done-xenial'. If the problem still exists,
change the tag
Hello Alberto, or anyone else affected,
Accepted nvidia-prime into bionic-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/nvidia-
prime/0.8.15.3~0.18.04.1 in a few hours, and then in the -proposed
repository.
Please help us by testing this new
Hello Alberto, or anyone else affected,
Accepted ubuntu-drivers-common into bionic-proposed. The package will
build now and be available at https://launchpad.net/ubuntu/+source
/ubuntu-drivers-common/1:0.8.6.3~0.18.04.1 in a few hours, and then in
the -proposed repository.
Please help us by
** Changed in: libffi (Ubuntu)
Status: Fix Committed => Fix Released
** Changed in: libffi (Ubuntu Focal)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pygobject in Ubuntu.
the symbols got updated since, we are probably not going to investigate
why they changed at this point so closing
** Changed in: poppler (Ubuntu)
Status: New => Invalid
** Changed in: poppler (Ubuntu)
Assignee: Dimitri John Ledkov (xnox) => (unassigned)
--
You received this bug
Note: also scanimage gives 'out of memory'
corrado@corrado-x6-hh-0122:~$ scanimage -L
device `escl:http://127.0.0.1:6' is a HP DeskJet 2600 series [665032] (USB)
flatbed scanner
device `hpaio:/usb/DeskJet_2600_series?serial=CN0569B27006PS' is a
Hewlett-Packard DeskJet_2600_series all-in-one
** Description changed:
xrandr
Screen 0: minimum 320 x 200, current 3840 x 1080, maximum 16384 x 16384
eDP connected primary 1920x1080+0+0 (normal left inverted right x axis y
axis) 344mm x 194mm
-1920x1080 59.93*+ 39.99
-1680x1050 59.93
-1280x1024 59.93
-
Public bug reported:
xrandr
Screen 0: minimum 320 x 200, current 3840 x 1080, maximum 16384 x 16384
eDP connected primary 1920x1080+0+0 (normal left inverted right x axis y axis)
344mm x 194mm
1920x1080 59.93*+ 39.99
1680x1050 59.93
1280x1024 59.93
1440x900
** Changed in: libdeflate (Ubuntu Hirsute)
Assignee: Sebastien Bacher (seb128) => (unassigned)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to tiff in Ubuntu.
https://bugs.launchpad.net/bugs/1908502
Title:
[MIR] libdeflate
Thanks for the patch Paolo, I uploaded to hirsute now
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to wpa in Ubuntu.
https://bugs.launchpad.net/bugs/1912609
Title:
mac80211_hwsim: hostapd fails to start with S1G band
Status in wpa
This bug was fixed in the package libfprint -
1:1.90.2+tod1-0ubuntu1~20.04.4
---
libfprint (1:1.90.2+tod1-0ubuntu1~20.04.4) focal; urgency=medium
* debian/patches:
- image-device: Delay completion until deactivation (LP: #1897613)
- Support more synaptics devices PIDs (LP:
This bug was fixed in the package libfprint -
1:1.90.2+tod1-0ubuntu1~20.04.4
---
libfprint (1:1.90.2+tod1-0ubuntu1~20.04.4) focal; urgency=medium
* debian/patches:
- image-device: Delay completion until deactivation (LP: #1897613)
- Support more synaptics devices PIDs (LP:
This bug was fixed in the package libfprint -
1:1.90.2+tod1-0ubuntu1~20.04.4
---
libfprint (1:1.90.2+tod1-0ubuntu1~20.04.4) focal; urgency=medium
* debian/patches:
- image-device: Delay completion until deactivation (LP: #1897613)
- Support more synaptics devices PIDs (LP:
This bug was fixed in the package libfprint -
1:1.90.2+tod1-0ubuntu1~20.04.4
---
libfprint (1:1.90.2+tod1-0ubuntu1~20.04.4) focal; urgency=medium
* debian/patches:
- image-device: Delay completion until deactivation (LP: #1897613)
- Support more synaptics devices PIDs (LP:
This bug was fixed in the package libfprint -
1:1.90.2+tod1-0ubuntu1~20.04.4
---
libfprint (1:1.90.2+tod1-0ubuntu1~20.04.4) focal; urgency=medium
* debian/patches:
- image-device: Delay completion until deactivation (LP: #1897613)
- Support more synaptics devices PIDs (LP:
This bug was fixed in the package libfprint -
1:1.90.2+tod1-0ubuntu1~20.04.4
---
libfprint (1:1.90.2+tod1-0ubuntu1~20.04.4) focal; urgency=medium
* debian/patches:
- image-device: Delay completion until deactivation (LP: #1897613)
- Support more synaptics devices PIDs (LP:
This bug was fixed in the package libfprint -
1:1.90.3+tod1-0ubuntu2~20.10.2
---
libfprint (1:1.90.3+tod1-0ubuntu2~20.10.2) groovy; urgency=medium
* debian/patches:
- image-device: Delay completion until deactivation (LP: #1897613)
- Support more synaptics devices PIDs (LP:
This bug was fixed in the package libfprint -
1:1.90.3+tod1-0ubuntu2~20.10.2
---
libfprint (1:1.90.3+tod1-0ubuntu2~20.10.2) groovy; urgency=medium
* debian/patches:
- image-device: Delay completion until deactivation (LP: #1897613)
- Support more synaptics devices PIDs (LP:
This bug was fixed in the package libfprint -
1:1.90.3+tod1-0ubuntu2~20.10.2
---
libfprint (1:1.90.3+tod1-0ubuntu2~20.10.2) groovy; urgency=medium
* debian/patches:
- image-device: Delay completion until deactivation (LP: #1897613)
- Support more synaptics devices PIDs (LP:
This bug was fixed in the package libfprint -
1:1.90.3+tod1-0ubuntu2~20.10.2
---
libfprint (1:1.90.3+tod1-0ubuntu2~20.10.2) groovy; urgency=medium
* debian/patches:
- image-device: Delay completion until deactivation (LP: #1897613)
- Support more synaptics devices PIDs (LP:
This bug was fixed in the package libfprint -
1:1.90.3+tod1-0ubuntu2~20.10.2
---
libfprint (1:1.90.3+tod1-0ubuntu2~20.10.2) groovy; urgency=medium
* debian/patches:
- image-device: Delay completion until deactivation (LP: #1897613)
- Support more synaptics devices PIDs (LP:
This bug was fixed in the package libfprint -
1:1.90.3+tod1-0ubuntu2~20.10.2
---
libfprint (1:1.90.3+tod1-0ubuntu2~20.10.2) groovy; urgency=medium
* debian/patches:
- image-device: Delay completion until deactivation (LP: #1897613)
- Support more synaptics devices PIDs (LP:
Public bug reported:
[impact]
'add-apt-repository -s' should enable deb-src for all existing repos,
but doesn't
[test case]
root@sp-g:~# add-apt-repository -sL
deb http://archive.ubuntu.com/ubuntu groovy restricted universe multiverse main
deb http://archive.ubuntu.com/ubuntu groovy-updates
Public bug reported:
I have been writing an .xlsx file using java POI from InteliJ.
Rendering the sheet does not reflect the cell-styles which have been
applied.
The sheet is absolutely as expected in Excel (on Windows 10) and
OpenOffice on Ubuntu 20.04
ProblemType: Bug
DistroRelease: Ubuntu
** Changed in: wpa (Ubuntu)
Status: New => Fix Committed
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to wpa in Ubuntu.
https://bugs.launchpad.net/bugs/1893563
Title:
netplan: can't login to ap mode with psk
Status in
** Changed in: wpa (Ubuntu Hirsute)
Importance: Undecided => High
** Changed in: wpa (Ubuntu Hirsute)
Status: New => Fix Committed
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to wpa in Ubuntu.
This bug was fixed in the package glib2.0 - 2.64.6-1~ubuntu20.04.1
---
glib2.0 (2.64.6-1~ubuntu20.04.1) focal; urgency=medium
[ Iain Lane ]
* New upstream release (LP: #1907433), fixing bugs:
- Ensure g_subprocess_communicate_async() never blocks
- Fix large writes in
The verification of the Stable Release Update for glib2.0 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
Thanks for taking the time to report this bug and helping to make Ubuntu
better. This is not a bug, but rather expected behavior:
https://wiki.ubuntu.com/SecurityTeam/FAQ#gnome-keyring
Please feel free to report any other bugs you may find.
** Information type changed from Private Security to
On Mon, Jan 25, 2021 at 07:03:55PM -, Adam Felson wrote:
>Before I grab'n'build 5.11, I'd like to know if my issue is similar.
>I have a lenovo ideapad 730s.
>The touchpad works fine for pointing, single, double and triple clicks.
>I have tried both the synaptics and libinput drivers. It's
Hi Mauricio,
unfortunately I've upgraded to Focal Fossa since then and the bug is not
present in this version of Ubuntu.
--
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/1838152
On Thu, Jan 21, 2021 at 01:05:48PM -, Joe Zhou wrote:
>Lenovo R7000P Laptop. Sadly, still not a good solution. The touch pad
>now works with kernel 5.11.0, but it has problem with Nvidia GPU and the
>brightness control is not working. I can have Nvidia GPU working and
>manually do some fixes
Hi Luka/@zapduke,
Can you test/verify bionic-proposed?
Thanks!
--
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/1838152
Title:
gnome-shell freezes on notification arrival (fixed
On 2021-01-28 04:58, Daniel van Vugt wrote:
> Any bug reported through the ideal means of 'ubuntu-bug' or from
> errors.ubuntu.com will get the tags automatically.
Ah, ok.
> As for people who don't like the process, that's OK. I find about one
> in 400 bugs receive a complaint from affected
** Changed in: snapd (Ubuntu)
Status: In Progress => Fix Committed
--
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/1900679
Title:
[snap] Apparmor audit messages for
** Attachment added: "lspci.txt"
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1903986/+attachment/5457751/+files/lspci.txt
** Changed in: gnome-shell (Ubuntu)
Status: Incomplete => New
--
You received this bug notification because you are a member of Desktop
Packages,
Today after 25 days without a freeze Ubuntu froze when I was in remote desktop
using Remmina.
- mouse pointer disappeared
- music running on Ubuntu was playing normaly
- I did ctrl+alt+f3 like suggested in #38 and kill remmina process with "kill
-9 " but Ubuntu was still frozen when I switched
1 - 100 of 111 matches
Mail list logo
