; Status in libppd source package in Oracular:
> New
>
> Bug description:
> This bug is to track the vulnerabilities in the cups and associated
> packages.
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/cups/+bug/20
** Changed in: cups (Ubuntu Noble)
Assignee: (unassigned) => Kevin bush (akjk32002)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to cups in Ubuntu.
https://bugs.launchpad.net/bugs/2082335
Title:
Sept 2024 security issue track
I have been testing those packages (described in bug 2025006) from
noble-proposed for a week now, and so far I haven't seen the issue any
more.
Usually it happened at least once a week, so I am carefully optimistic.
I'd have to not see the issue for a bit longer to be completely
convinced it's fix
: nvidia_uvm nvidia
AddonCompatCheckDisabled: False
ApportVersion: 2.20.11-0ubuntu27.27
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: kevin 1172 F pulseaudio
BuildID: 20240819150008
CasperMD5CheckResult: skip
Channel: Unavailable
Date: Wed Aug 28 07
Public bug reported:
During the kerenl SRU testing, I found that the DGX A100 station kept
showing error messages from nouveau in dmesg as follows. These numerous
kernel error messages crippled the system and made it unresponsive.
[ 2265.721452] nouveau :07:00.0: disp: ctrl 0080
[ 2265.72
Perhaps related to this issue, I have also noticed that sometimes when I
(re)boot my computer in the evening when Night Light is in an early
stage, it remains stuck in that initial level of orange set after boot,
and it doesn't gradually increase like it should do. Disabling and
enabling Night Ligh
Further research indicates that `webkit2gtk-4.0` is legacy and removed
on purpose, which I fully understand, and bringing it back might not be
a practical operation.
My project (GlobalProtect-openconnect) uses Tauri 1.x, which depends on
`webkit2gtk-4.0`. Tauri started to use `webkit2gtk-4.1` in 2
I'm experiencing the same issue. Will we be adding these packages back?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to webkit2gtk in Ubuntu.
https://bugs.launchpad.net/bugs/2061914
Title:
libjavascriptcoregtk-4.0-18 seems to be missin
** Also affects: linux-intel-iotg-5.15 (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/2056383
Title:
Audio turned to dummy outp
@Francis
I've confirmed that the DUT has already used the latest ubuntu-drivers from
proposed.
Setting up ubuntu-drivers-common (1:0.9.0~0.20.04.8) ...
But it doesn't seem to solve the issue. Please check following messages.
+ _run sudo ubuntu-drivers devices
+ ssh -t -o StrictHostKeyChecking=n
I've just tested the latest snap from the beta channel (2751). I deleted
~/.chromium-browser.init, and I can confirm that the webcam works fine
now in the default configuration. VAAPI is also still functional
according to intel_gpu_top.
Thanks!
--
You received this bug notification because you a
Sure, no problem.
Could you by any chance do a new build for the beta channel with this
fix included? Then I can test if the webcam still works in the default
configuration, without the ~/.chromium-browser.init file.
--
You received this bug notification because you are a member of Desktop
Packa
Public bug reported:
Looking at https://discourse.ubuntu.com/t/an-overview-of-hardware-
acceleration-in-chromium/36672, a couple of flags are added for beta and
edge channel builds of Chromium to enable VAAPI.
You may want to remove the flag --video-capture-use-gpu-memory-buffer
from the builds,
This bug must have been introduced between Ubuntu 18.04 and 18.10.
It doesn't happen with Ubuntu 18.04 which shipped with Firefox 59. It
first appeared in Ubuntu 18.10 which comes with Firefox 63.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscr
** Tags added: cert-sru
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/2051068
Title:
GUI crashed after installed proposed package libegl-mesa0
Status in mesa package in Ubuntu:
Confi
I was also able to download the upgrade per Jeremy Bicha's instructions,
which seems to have resolved the issue for me as well. (Again,
mutter=45.2-0ubuntu3, on Ubuntu 23.10.)
Thanks again to all involved! (Also, my thanks, and an apology, to
Gonzalo Rodríguez Carrera. I neglected to thank you spe
First, thank you to Jeremy Bicha and Steve Langasek, and anyone else
involved in bringing the update to mutter.
I've been trying for the past few days to install the update. I enabled
-proposed, but every time I try to install the newer version of mutter
(whether directly by the version name, or b
Per the reply to my initial comment, I've changed the filing to reflect
the possibility that it's related to the mutter package, as that was the
one that fixed the problem previously.
** Package changed: ubuntu => mutter (Ubuntu)
--
You received this bug notification because you are a member of
I encountered this exact problem a few weeks back (Ubuntu 23.10, Wacom
Intuos CTH-680) but it was fixed by installing mutter 45.2-0ubuntu1, as
indicated. However, this morning, the exact issue reappeared. I tried
updating to the latest version of mutter (45.2-0ubuntu2~really45.0) via
aptitude, but
Public bug reported:
During the SRU testing, I found some of machines installed the wrong
version of Nvidia driver.
They shouldn't install nvidia-driver-535-server-open on a desktop.
Please have a look, thanks.
If you want to have more information, please let me know.
+ _run sudo ubuntu-drive
es: wl
AddonCompatCheckDisabled: False
ApportVersion: 2.20.11-0ubuntu27.26
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: kevin 2226 F pulseaudio
/dev/snd/controlC1: kevin 2226 F pulseaudio
BuildID: 20230424110519
CasperMD5CheckResult: skip
C
Here is an example of a website where this bug causes dashes not to
show:
https://www.dontexist.de/
Firefox on Ubuntu incorrectly renders "MediaWiki-Startseite" as
"MediaWiki Startseite". Other browsers and Firefox on other OSes
correctly render "MediaWiki-Startseite".
--
You received this bug
Public bug reported:
The attached HTML file should be rendered as two lines of text, one with
dashes between the words and one with spaces. However, Firefox renders
the file with no dashes whatsoever. Instead of dashes, it shows double-
width spaces.
The HTML renders correctly if lang="de-x-forma
Public bug reported:
since the upadating to Ubuntu 22.04.2 LTS, i have no sounds from
internet. Sound works from Rhythm box software or videos. I also don't
have "system" sound. The audio device is not detected
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: pulseaudio 1:15.99.1+dfsg1-1ubun
** Changed in: alsa-driver (Ubuntu)
Assignee: (unassigned) => Kai-Heng Feng (kaihengfeng)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to alsa-driver in Ubuntu.
https://bugs.launchpad.net/bugs/2007798
Title:
[Inspiron 7590, Realte
Public bug reported:
[Summary]
During the kernel SRU testing on focal-hwe, I found the audio output of some
machines are broken.
I've tested some of machine on Jammy using same kernel(5.15.0-66-generic) and
haven't seen this happened.
The volume bars in settings react to what sound is played co
You can download the necessary deb's and install them on *buntu 22.10.
Make sure you have dkms installed first.
There is a download link at the bottom of each of the pages below. The
order of them does matter in order to satisfy the dependencies. Going in
this order worked for me:
- https://pack
There are also patches available at
https://github.com/warpme/minimyth2/tree/master/script/nvidia/nvidia-340.108/files.
This repo has some history vs. the if-not-true-then-false site.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to nvidia
Public bug reported:
During the SRU testing, I found a dependency issue when running "ubuntu-drivers
install".
Although OEM image has preloaded nvidia driver already, but when user want to
install newer version of nvidia driver will hit this issue.
Using 202002-27718 as an example, after instal
The only upstream bug that seems potentially related is
https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/issues/1024
. But that's more about ensuring that WPA auth has completed before
starting the DHCP renewal, and it's not clear to me how blocking ICMP
could avoid that problem. So
I have the same symptoms on Ubuntu 22.04.1 on a 12th-gen Framework
laptop with Intel Wi-Fi 6 AX210/AX211/AX411 160MHz (rev 1a) device.
Every time wpa-supplicant chooses to associate with a different BSSID
(of the same SSID), the interface ends up being given a new IP address
by the DHCP server (usu
Also having the same issue with X-Rite|Colormunki-Display on Ubuntu
22.04.01
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-control-center in Ubuntu.
https://bugs.launchpad.net/bugs/1719143
Title:
Unable to calibrate monitors th
I don't know if it's my KDE Plasma login or what, but I am still getting the
"Thunderbird is already running, but is not responding. To use Thunderbird, you
must first close the existing Thunderbird process, restart your device, or use
a different profile." error when running "snap run thunderbi
Thanks.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to thunderbird in Ubuntu.
https://bugs.launchpad.net/bugs/1980839
Title:
thunderbird -compose returns error since the 102 snap update?
Status in thunderbird package in Ubuntu:
Fix
It now works in the stable version of the Thunderbird snap, but doesn't
in the beta version (106.0b5). Will it be fixed in the beta?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to thunderbird in Ubuntu.
https://bugs.launchpad.net/bugs/19
** Package changed: ubuntu => gnome-power-manager (Ubuntu)
** Summary changed:
- wakeup file is ignored
+ suspend wakeup file is ignored
** Description changed:
- Writing "disabled" to wakeup file is not working:
+ Writing "disabled" to wakeup file is ignored after suspend.
sudo sh -c "ech
I am beginning to wonder if this is more of a local to me problem as I have
just installed the flatpak beta version of Thunderbird 102 and get the same
error message that Thunderbird is already running.
I will try the tar ball version next.
--
You received this bug notification because you are
I don't know how this might help, but I followed the instructions to download
and un-squash the version 102.0.1 of thunderbird to my home folder, cd'd into
the squashfs-root folder and ran thunderbird using ./thunderbird -p which
picked up my current profile from the ~/.thunderbird directory.
>
It's fixed upstream as well now:
https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/commit/6920b6ceb1c2e7856ad76e118ee5b4dd36130735
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launch
kevin@arcadia:~$ apt info network-manager
Package: network-manager
Version: 1.36.6-0ubuntu2
kevin@arcadia:~$ apt info libnm0
Package: libnm0
Version: 1.36.6-0ubuntu2
I have installed network-manager and libnm0 version 1.36.6-0ubuntu2 from
jammy-proposed. After connecting to a network with both
This seems to restore previous behaviour yes.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1977619
Title:
NetworkManager 1.36.6 no longer prefers DHCPv6 addresses over SLAAC
Unfortunately I was not tracking jammy-proposed, so I only found out
about this bug when it entered jammy-updates.
I don't think my configuration is that exotic to be honest. Many
companies use DHCPv6 servers giving out static leases, and many
companies use firewalls to restrict incoming (SSH) con
@seb128 What is the plan for the network-manager package in Ubuntu
jammy-updates? Is it to be left broken until upstream fixes this bug?
Because I think that the problem this last version introduces is a lot
bigger than the problem(s) it solves. Therefore I would say that it can
be defended to upl
** Summary changed:
- NetworkManager 1.36.6 orders IPv6 addresses incorrectly
+ NetworkManager 1.36.6 no longer prefers DHCPv6 addresses over SLAAC
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.l
** Description changed:
Situation:
- My network has both DHCPv6 and SLAAC for IPv6. From a privacy
+ My network has both DHCPv6 and SLAAC (autoconf) for IPv6. From a privacy
perspective, for readability reasons and for network management
policies, DHCPv6 should *always* be preferred over
** Description changed:
Situation:
My network has both DHCPv6 and SLAAC for IPv6. From a privacy
perspective, for readability reasons and for network management
policies, DHCPv6 should *always* be preferred over SLAAC addresses when
available. And according to RFC 6724, the smaller /1
** Description changed:
- My network has both DHCPv6 and SLAAC for IPv6. From both a privacy
- perspective and readability reasons, DHCPv6 should *always* be preferred
- over SLAAC addresses when available. And according to RFC 6724 the
- smaller /128 scope of the DHCPv6 address should be chosen o
** Description changed:
My network has both DHCPv6 and SLAAC for IPv6. From both a privacy
perspective and readability reasons, DHCPv6 should *always* be preferred
over SLAAC addresses when available. And according to RFC 6724 the
smaller /128 scope of the DHCPv6 address should be chosen o
** Description changed:
My network has both DHCPv6 and SLAAC for IPv6. From both a privacy
perspective and readability reasons, DHCPv6 should *always* be preferred
- over SLAAC addresses when available.
+ over SLAAC addresses when available. And according to RFC 6724 the
+ smaller /128 scope o
** Description changed:
My network has both DHCPv6 and SLAAC for IPv6. From both a privacy
perspective and readability reasons, DHCPv6 should *always* be preferred
over SLAAC addresses when available.
NetworkManager has always been able to adhere to that by simply setting
ip6.privacy=
** Tags added: regression-update
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1977619
Title:
NetworkManager 1.36.6 orders IPv6 addresses incorrectly
Status in network-manag
** Description changed:
My network has both DHCPv6 and SLAAC for IPv6. From both a privacy
perspective and readability reasons, DHCPv6 should *always* be preferred
over SLAAC addresses when available.
NetworkManager has always been able to adhere to that by simply setting
- ip6.privacy=
@seb128 I have created a new bug report with links to the upstream
commits. The core of the issue is that IPv6 addresses are now being
added in the wrong order, so the kernel prefers SLAAC addresses over
DHCPv6 addresses, which should be the other way around.
As this is a breaking change in source
** Description changed:
My network has both DHCPv6 and SLAAC for IPv6. From both a privacy
perspective and readability reasons, DHCPv6 should *always* be preferred
over SLAAC addresses when available.
NetworkManager has always been able to adhere to that by simply setting
ip6.privacy=
** Description changed:
My network has both DHCPv6 and SLAAC for IPv6. From both a privacy
perspective and readability reasons, DHCPv6 should *always* be preferred
over SLAAC addresses when available.
NetworkManager has always been able to adhere to that by simply setting
ip6.privacy=
** Description changed:
My network has both DHCPv6 and SLAAC for IPv6. From both a privacy
perspective and readability reasons, DHCPv6 should *always* be preferred
over SLAAC addresses when available.
NetworkManager has always been able to adhere to that by simply setting
ip6.privacy=
** Tags added: jammy
** Description changed:
My network has both DHCPv6 and SLAAC for IPv6. From both a privacy
perspective and readability reasons, DHCPv6 should *always* be preferred
over SLAAC addresses when available.
NetworkManager has always been able to adhere to that by simply
I guess these commits are relevant:
https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/commit/c631aa48f034ade2b5cb97ccc4462d56d80174e7
https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/commit/257221d1986b56cbb2e329fcc74a2daca145b7aa
Bottom line: addresses are now being a
Comparing the output of `ip -6 a`, you can see that the dynamic
addresses are no longer at the top of the list, where they should be.
Before (network-manager 1.36.4):
2: eno0: mtu 1500 state UP qlen 1000
inet6 2a10:3781:::bd0/128 scope global dynamic noprefixroute
valid_lft 43193
** Description changed:
My network has both DHCPv6 and SLAAC for IPv6. From both a privacy
perspective and readability reasons, DHCPv6 should *always* be preferred
over SLAAC addresses when available.
NetworkManager has always been able to adhere to that by simply setting
ip6.privacy=
Looking at the changelog of 1.38.0:
* Fix bug setting priority for IP addresses.
https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/blob/nm-1-38/NEWS
So it looks like Ubuntu just introduced that bug by upgrading to 1.36.6.
Please either backport it from 1.38.0 or revert to 1.36.4.
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1977619
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1974428
Title:
Update to the current 1.36 stable version
** Description changed:
My network has both DHCPv6 and SLAAC for IPv6. From both a privacy
perspective and readability reasons, DHCPv6 should *always* be preferred
over SLAAC addresses when available.
NetworkManager has always been able to adhere to that by simply setting
ip6.privacy=
Public bug reported:
My network has both DHCPv6 and SLAAC for IPv6. From both a privacy
perspective and readability reasons, DHCPv6 should *always* be preferred
over SLAAC addresses when available.
NetworkManager has always been able to adhere to that by simply setting
ip6.privacy=0 for the conne
All of a sudden SLAAC addresses are preferred over DHCPv6 addresses,
which should not be happening. Setting ip6.privacy=0 no longer helps,
nor does setting net.ipv6.conf.all.use_tempaddr = 0 with sysctl.
--
You received this bug notification because you are a member of Desktop
Packages, which is
Thanks for the reply! Reported upstream here:
https://gitlab.gnome.org/GNOME/gnome-control-center/-/issues/1860
And patch submitted here: https://gitlab.gnome.org/GNOME/gnome-control-
center/-/merge_requests/1328
** Bug watch added: gitlab.gnome.org/GNOME/gnome-control-center/-/issues #1860
ht
Public bug reported:
In Ubuntu 20.04, I was able to set Left Ctrl as my Compose key using
gnome-tweaks. I just upgraded to 22.04, where the Compose key settings
have been removed from gnome-tweaks and moved into control-center, but
Left Ctrl is not in the list of options for Compose.
I was able t
Public bug reported:
After updating gdm3 from 42.0-1ubuntu2 to 42.0-1ubuntu4 in jammy, it no
longer shows any sessions in the bottom-right corner. When I log in, I
am dropped into an X11 session, with no way to switch to Wayland.
Downgrading the gdm3, gir1.2-gdm-1.0 and libgdm1 packages to
42.0-1
Copy/paste works for me, but drag/drop does not. I can't even rearrange
tabs or bookmarks.
--
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/1947210
Title:
Firefox Snap can't copy&paste
** Also affects: gnome-shell
Importance: Undecided
Status: New
** No longer affects: gnome-shell
** Also affects: gnome-shell (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to
This video shows that what I observed.
** Attachment added: "IMG_6015.mp4"
https://bugs.launchpad.net/ubuntu/+source/xwayland/+bug/1967452/+attachment/5575459/+files/IMG_6015.mp4
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xwayl
Public bug reported:
[Reproduce steps]
1. Install jammy beta.
2. Install nvidia-driver by ubuntu-driver install
3. Suspend the system by clicking the button at the upper right corner.
[Expected result]
Should re-enter to desktop.
[Actual result]
Screen keep blinking and don't show the desktop
Public bug reported:
Graphics option in About pane shows "llvmpipe (LLVM 12.0.0, 256 bits)"
$ lspci | grep -E 'VGA|Display'
00:02.0 VGA compatible controller: Intel Corporation UHD Graphics (rev 05)
$ glxinfo -B
name of display: :1
display: :1 screen: 0
direct rendering: Yes
Extended renderer i
Public bug reported:
I installed Ubuntu 21.10 on my laptop (Lenovo Yoga Slim 14 ARE 05 - AMD
Ryzen 4700 - 1§ GB RAM - 512 GB SSD). Every time I close the lid or let
the laptop go to suspend the system doesn't resume. Clicking the mouse
or pushing the keys doesn't resume the OS.
The only way to re
Upstream bug: https://bugzilla.mozilla.org/show_bug.cgi?id=1745098
Likely caused by this change:
https://bugzilla.mozilla.org/show_bug.cgi?id=1737068
** Bug watch added: Mozilla Bugzilla #1745098
https://bugzilla.mozilla.org/show_bug.cgi?id=1745098
** Bug watch added: Mozilla Bugzilla #173706
** Description changed:
I have a couple of ThinkPads with old Intel GMA X4500 graphics. Since
- the update to Firefox 95, it's been verry laggy; especially noticeable
+ the update to Firefox 95, it's been very laggy; especially noticeable
while scrolling, for instance on about:support.
St
I have also tested the tarball releases from
https://www.mozilla.org/firefox/
The problems are identical with those releases. I tested 94.0.2, 95.0,
96.0b2 and 97.0a1.
I ran all of them with `MOZ_ENABLE_WAYLAND=1`.
94.0.2 works perfectly fine, and all the other releases show lag while
scrolling,
iKey is already present with a very similar line, so
this is merely a case of a missing rule.
It would be very nice if support for the Nitrokey FIDO2 could be
upstreamed.
More background here: https://support.nitrokey.com/t/nitrokey-
fido2-funktioniert-nicht-mit-firefox-und-chromiu
Public bug reported:
I have a couple of ThinkPads with old Intel GMA X4500 graphics. Since
the update to Firefox 95, it's been verry laggy; especially noticeable
while scrolling, for instance on about:support.
Strangely, the bug is less present when the browser window is smaller. A
maximized wind
I noticed that both the Firefox and Chromium snaps do work in Debian 11,
which uses an older xdg-desktop-portal than Ubuntu 22.04. I wondered
what would happen if I'd install xdg-desktop-portal and xdg-desktop-
portal-gtk 1.8 from 21.10 in 22.04, and it turns out that this fixes it.
So I guess tha
@vanvugt Are you sure it works?
I'm currently testing Ubuntu 22.04 (completely updated as of writing)
with the 94.0.2-2 Firefox snap. When I go to https://meet.jit.si/ and
click the screen sharing button, I can only select "Use operating system
settings". When I do that, nothing happens. I don't g
Reported here:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=996474
** Bug watch added: Debian Bug tracker #996474
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=996474
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to libical
Public bug reported:
The libical-dev package on Ubuntu 21.10 (impish) does not provide CMake
config files.
% dpkg -L libical-dev | grep cmake
... returns nothing.
As of today:
# Packages file listings on 20.04, 20.10
The package provides CMake config files in:
```
/usr/lib/x86_64-linux-gnu/cm
This still affects me on my Pinebook Pro. Are there any plans to
backport this to focal?
--
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/1915929
Title:
gnome-shell-calendar-server
Public bug reported:
Just installed ubuntu 20.04 and the screen has been flickering all
through. tried applying the ubuntu on Wayland solution but no change.
Please help with a solution on workaround for this.
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: xorg 1:7.7+19ubuntu14
ProcVersion
Key is already present with a very similar line, so
this is merely a case of a missing rule.
It would be very nice if support for the Nitrokey FIDO2 could be
upstreamed.
More background here: https://support.nitrokey.com/t/nitrokey-
fido2-funktioniert-nicht-mit-firefox-und-chromium-u
present with a very similar line, so this
is merely a case of a missing rule.
It would be very nice if support for the Nitrokey FIDO2 could be
upstreamed.
More background here: https://support.nitrokey.com/t/nitrokey-
fido2-funktioniert-nicht-mit-firefox-und-chromium-unter
e if support for the Nitrokey FIDO2 could be
upstreamed.
More background here: https://support.nitrokey.com/t/nitrokey-
fido2-funktioniert-nicht-mit-firefox-und-chromium-unter-
ubuntu-20-04/2651
Also hereby the required fluff:
kevin@vanadium:~$ lsb_release -rd
Description:Ubuntu 20.04.2 LTS
Re
** Changed in: firefox (Ubuntu)
Status: New => Fix Released
--
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/1936647
Title:
right-click popups transparent after upgrade to Firefo
Issue no longer present in 90.0.2.
--
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/1936647
Title:
right-click popups transparent after upgrade to Firefox 90
Status in firefox package
Public bug reported:
Upon upgrade to Firefox 90, right-click popups appear transparent.
I am using the Blackbird gtk theme. If I switch to Adwaita-dark, the problem
goes away.
I encountered this issue on another system with the direct download from
Mozilla, so this is likely an upstream issue, b
I recently updated to 20.04.1 and experienced a similar issue as
described in comment #3.
To reproduce the issue:
1) Enable "Locate Pointer" in Settings -> Universal Access -> Pointing &
Clicking
2) Open Firefox, go to https://duckduckgo.com
3) Enter search text, e.g. "test test test"
4) Click i
Public bug reported:
package instaLL ERROR
ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: libsane 1.0.29-0ubuntu5.1
ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
Uname: Linux 5.4.0-42-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.8
Architecture: amd64
CasperMD5CheckResult:
Public bug reported:
Video of bug: https://youtu.be/O0__VNN9G_o
At 0:11 in the video you see old web browser data showing up in my
program.
At 0:19 when I close a window in my program the texture for my piano key letters
flicker. By luck the texture for my keys sometimes flickers to stuff previo
Will this be in the next stable channel snap update?
--
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/1868117
Title:
[snap] Adapt chromium user agent to avoid "not supported br
I can confirm that setting org.gnome.desktop.privacy remember-app-usage
to false, and thus removing the Frequent / All buttons, also works
around this problem.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell-extension-ubuntu-d
I think part of the culprit may be that the Frequent / All buttons on
the bottom are pushed downwards when opening an app folder on a 1366x768
display, causing the grid to re-align. This doesn't happen on 1280x800
or 1680x1050, where the bugs related to the many dots on the right or
the shell locki
This is definitely resolution related. I am unable to reproduce this on
my X200's and T400's (1280x800) or T500's (1680x1050), but it hits me
every time on my X220's (1366x768).
I also tried gnome-shell-extension-ubuntu-dock 68 from focal-proposed,
but that does not help at all. Setting org.gnome.
Just chiming in to say that I am experiencing this problem on a fresh
install of Kubuntu 20.04. I previously experienced it on a forced
upgrade from 19.10->20.04; I thought perhaps the upgrade process was too
premature so I wiped and started fresh. Still broken. Sometimes it
works, sometimes it doe
+1
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1838151
Title:
Poor quality audio with modern Bluetooth headsets in HSP/HFP. Missing
wide band speech support.
Status in Pulse
1 - 100 of 841 matches
Mail list logo
