i found a way to reproduce
- wait for an automatic update manager prompt
- apply the updates (in the dock, the update-manager icon is twisting)
- when its done, close update-manager
- then the error start to appear in syslog
--
You received this bug notification because you are a member of
Confirmed these are actually the same code:
dash-to-dock docking.js line 2036
ubuntu-dock docking.js line 2051
** Also affects: gnome-shell-extension-dashtodock (Ubuntu)
Importance: Undecided
Status: New
** Changed in: gnome-shell-extension-dashtodock (Ubuntu)
Status: New =>
** Summary changed:
- No virtual terminals (CTRL+ALT+F?) when no user logged in; erratic behaviour
when user logged in.
+ No virtual terminals (CTRL+ALT+F?) when no user logged in
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mutter
Any additional procedures to gather more information about the bug?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell-extension-ubuntu-dock in
Ubuntu.
https://bugs.launchpad.net/bugs/1905186
Title:
dock and top bar flashing
** Changed in: dash-to-dock
Status: Unknown => New
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell-extension-ubuntu-dock in
Ubuntu.
https://bugs.launchpad.net/bugs/1905519
Title:
Object St.Bin (0x565425162c80), has
More details about the backlight control can be found in
https://forums.developer.nvidia.com/t/legion-5-no-backlight-control-in-
discrete-graphics-mode/160292/11
If you have any questions please create a topic in the nvidia forums or
open a new bug!
/thread hijack off
--
You received this bug
I can reproduce it but only in:
* GNOME Shell 3.36.4
* KDE Plasma Shell 5.18.5
But in XFCE, LXDE, LXQT, MATE and others ++ works fine
for me.
At first, I've tried to use `sudo chvt 2` for switching form KDE on tty1 to Raw
Console on tty2. After switching to tty2 ++ works as in early
days.
It
Again my apologies to everyone for hijacking this thread, But since
people are asking, and I was able to solve the backlight problem after
days of pain, here are the instructions. Two caveats though:
- you need to have the laptop in "Discrete" mode in the BIOS (in my experience,
Hybrid mode
Please reproduce the problem again, and while it is happening run this
command in a terminal:
xrandr --verbose > xrandr2.txt
and attach the resulting text file.
** Tags added: nvidia regression-update xrandr-scaling
** Summary changed:
- fractional display scale cannot work properly
+
** Package changed: ubuntu => xorg (Ubuntu)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1905648
Title:
[nvidia] fractional display scale cannot work properly
Status in mutter
You have been subscribed to a public bug:
When I switch on fractional scaling, and choose 125%/150%/175%,
everything gets very large. The screen can only display part of the
whole desktop. It is even larger than the 200%-scale.
P.S.
As I remember, the fractional scaling works well in May. But
Other than the exact line number, this looks close to
https://github.com/micheleg/dash-to-dock/issues/1332
** Bug watch added: github.com/micheleg/dash-to-dock/issues #1332
https://github.com/micheleg/dash-to-dock/issues/1332
** Also affects: dash-to-dock via
This is a bug in nautilus-desktop. Unfortunately nautilus-desktop is no
longer shipped and no longer supported in newer versions so this is
unlikely to ever be fixed.
** Package changed: xorg (Ubuntu) => nautilus (Ubuntu)
--
You received this bug notification because you are a member of Desktop
Thank you for taking the time to report this bug and helping to make
Ubuntu better. It sounds like some part of the system has crashed. To
help us find the cause of the crash please follow these steps:
1. Look in /var/crash for crash files and if found run:
ubuntu-bug YOURFILE.crash
Then tell
Please:
1. Attach a copy of your ~/.config/monitors.xml
2. Run this command to automatically gather more info:
apport-collect 1905637
** Tags added: groovy
** Tags added: regression-proposed
** Changed in: mutter (Ubuntu)
Status: New => Incomplete
--
You received this bug
We can't consider a fix unless someone can identify what package, or
specifically what change, actually fixed it.
--
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/1900404
Title:
Yeah I guess I should have expected that, thanks.
** Package changed: gnome-shell (Ubuntu) => gnome-shell-extension-
ubuntu-dock (Ubuntu)
** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu)
Status: Incomplete => New
--
You received this bug notification because you are a member of
This also happens on 20.04.1 LTS. Please fix it there also.
May be same as
https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/issues/1056
** Bug watch added: gitlab.freedesktop.org/pulseaudio/pulseaudio/-/issues #1056
https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/issues/1056
--
Public bug reported:
PulseAudio release 14.0 is now out.
** Affects: pulseaudio (Ubuntu)
Importance: Undecided
Status: New
** Tags: focal groovy hirsute
** Tags added: focal hirsute
** Tags added: groovy
--
You received this bug notification because you are a member of
Well, with this limited dock I can't reproduce the bug because it leaves
the fullscreen.
--
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/1905186
Title:
dock and top bar flashing
*** This bug is a duplicate of bug 1897659 ***
https://bugs.launchpad.net/bugs/1897659
Thank you for taking the time to report this bug and helping to make
Ubuntu better. This particular bug has already been reported and is a
duplicate of bug 1897659, so it is being marked as such. Please
** Information type changed from Private Security to Public
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-screensaver in Ubuntu.
https://bugs.launchpad.net/bugs/1905209
Title:
gnome-screensaver is blocked by an application to
Public bug reported:
I was installing wine on my computer and it was failing:
sudo apt install wine
Reading package lists... Done
Building dependency tree
Reading state information... Done
wine is already the newest version (5.0-3ubuntu1).
You might want to run 'apt --fix-broken install'
Hello Lillian, I suggest running the firmware update tool by hand to see
if there's more information available there:
sudo fwupdmgr update
I'm not sure what to suggest for libreoffice; perhaps
https://askubuntu.com/ would be a place to get more advice on how to
work with imports or exports to
Gnome Shell comes with its own dock which is hidden by default and
appears when you click Activities or press the Windows key.
Please disable Ubuntu Dock in the Extensions app and then tell us if
this bug still occurs.
--
You received this bug notification because you are a member of Desktop
I'm guessing external monitors are probably controlled by the Nvidia
GPU. In that case please try opening the Additional Drivers app and
installing the official Nvidia driver.
** Summary changed:
- On any external monitors, wayland session has a white block on most part of
the screen.
+
** Changed in: gnome-session (Ubuntu)
Status: Incomplete => New
** Changed in: gnome-shell (Ubuntu)
Status: Incomplete => New
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-session in Ubuntu.
It sounds like gnome-shell is frozen/crashed and Xorg is still running.
Please:
1. Remove any gnome-shell extensions you may have installed and log out
and in again.
2. If the problem still happens, check the Extensions app and disable
all extensions. Then log out and in again.
3. If the
Please open a bug with the developers at:
https://gitlab.gnome.org/GNOME/gnome-shell/-/issues
and tell us the new issue ID.
--
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/1905084
It sounds like gnome-shell is frozen/crashed and Xorg is still running.
Please:
1. Remove any gnome-shell extensions you may have installed and log out
and in again.
2. If the problem still happens, check the Extensions app and disable
all extensions. Then log out and in again.
2. If the
** Package changed: xserver-xorg-video-amdgpu (Ubuntu) => linux (Ubuntu)
** Summary changed:
- When entering sleep mode the monitors turn off then immediately turn back on
+ [amdgpu] When entering sleep mode the monitors turn off then immediately turn
back on
** Tags added: amdgpu
--
You
*** This bug is a duplicate of bug 1833855 ***
https://bugs.launchpad.net/bugs/1833855
Thanks. Looks like this is a kernel bug.
** Changed in: linux (Ubuntu)
Status: Incomplete => New
** No longer affects: xserver-xorg-video-intel (Ubuntu)
** Summary changed:
- [intel G33]
*** This bug is a duplicate of bug 1833855 ***
https://bugs.launchpad.net/bugs/1833855
** This bug is no longer a duplicate of bug 1899152
[i915] VGA resolution limited to 1024x768, EDID ignored or missing?
** This bug has been marked a duplicate of bug 1833855
i915: EDID not detected
Please remember drag and drop is not expected to work due to bug
1813441. This bug is only about gnome-shell freezing.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell-extension-desktop-icons in
Ubuntu.
Verified fixed on groovy in libmutter-7-0 version 3.38.1-2ubuntu1
** Tags removed: verification-needed-groovy
** Tags added: verification-done-groovy
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mutter in Ubuntu.
I suspect not many people will have a "3440x1440 21:9" monitor to test
with.
Please follow the instructions in comment #3.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/1895301
It appears the update is being blocked by bug 1878293. Let's see if I
can unblock it...
--
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/1897224
Title:
Graphical snaps can't run in
** Description changed:
- Some games (I tried Portal and Tomb Raider 2013) don't go full screen
- correctly. I tracked down this to a regression on package libmutter-7-0.
- Tee problem occurs with latest version, 3.38.1-2ubuntu1, but when I
+ Some games (I tried using Portal and Tomb Raider 2013,
Public bug reported:
Some games (I tried Portal and Tomb Raider 2013) don't go full screen
correctly. I tracked down this to a regression on package libmutter-7-0.
Tee problem occurs with latest version, 3.38.1-2ubuntu1, but when I
downgrade the package (and also the package gir1.2-mutter-7) to
This bug was fixed in the package libfprint - 1:1.90.3+tod1-0ubuntu2
---
libfprint (1:1.90.3+tod1-0ubuntu2) hirsute; urgency=medium
* debian/gbp.conf: Include debian's GNOME team preferred settings
* debian/patches (upstream cherry-picks):
- Properly handle aes3k devices,
This bug was fixed in the package libfprint - 1:1.90.3+tod1-0ubuntu2
---
libfprint (1:1.90.3+tod1-0ubuntu2) hirsute; urgency=medium
* debian/gbp.conf: Include debian's GNOME team preferred settings
* debian/patches (upstream cherry-picks):
- Properly handle aes3k devices,
This bug was fixed in the package libfprint - 1:1.90.3+tod1-0ubuntu2
---
libfprint (1:1.90.3+tod1-0ubuntu2) hirsute; urgency=medium
* debian/gbp.conf: Include debian's GNOME team preferred settings
* debian/patches (upstream cherry-picks):
- Properly handle aes3k devices,
This bug was fixed in the package libfprint - 1:1.90.3+tod1-0ubuntu2
---
libfprint (1:1.90.3+tod1-0ubuntu2) hirsute; urgency=medium
* debian/gbp.conf: Include debian's GNOME team preferred settings
* debian/patches (upstream cherry-picks):
- Properly handle aes3k devices,
This bug was fixed in the package libfprint - 1:1.90.3+tod1-0ubuntu2
---
libfprint (1:1.90.3+tod1-0ubuntu2) hirsute; urgency=medium
* debian/gbp.conf: Include debian's GNOME team preferred settings
* debian/patches (upstream cherry-picks):
- Properly handle aes3k devices,
*** This bug is a duplicate of bug 858338 ***
https://bugs.launchpad.net/bugs/858338
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: gedit (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Desktop
Updated upstream bug:
https://gitlab.freedesktop.org/geoclue/geoclue/-/issues/136, opened 20
OCT 2020
Looks like the Mozilla MLS maintainer has proposed to deprecate the
default key in order to force downstreams to get their own keys:
>From the linked bug:
"My proposal is to deprecate the
Public bug reported:
Bluetooth stops working after updating to bluez version 5.55-0ubuntu1.1.
/usr/bin/btuart returns "bcm43xx_init Initialization timed out".
Bluetooth is working again if bluez is reverted to version
5.55-0ubuntu1. I don't have any unusual setup like miniuart-bt.
Release:
Here often gnome software cannot update Gitkraken snap, it shows an
error message that Gitkraken uses classic confinement.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-software in Ubuntu.
https://bugs.launchpad.net/bugs/1876879
Public bug reported:
/run/user/1000/doc is a fuse.portal mount point, but statfs() return
EPERM, hence df produces an error message. Maybe statfs() is not
implemented, but it would be good to quieten this down (df even does not
allow me to ignore it, probably because it looks at statfs to find
bug #1886092Thanks, in complain-mode the gpg-agent asks for the passphrase (and
the file opens :-)
So You're right -> bug #1886092
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to libreoffice in Ubuntu.
The forum post also says it might be somehow related to either evdev or
libinput or possibly both.
--
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/1897249
Title:
Scrolling in
Well, that guy probably had a hardware issue, but this is not a hardware
issue. I have tried several mice, all of them are acting the same way.
Also, the fact that not all apllications are affected, and the fact that
not all operating systems are affected at all should make it pretty
clear that
** Also affects: libfprint (Ubuntu Groovy)
Importance: Undecided
Status: New
** Changed in: libfprint (Ubuntu Groovy)
Importance: Undecided => Medium
** Changed in: libfprint (Ubuntu Groovy)
Status: New => In Progress
** Changed in: libfprint (Ubuntu Groovy)
Assignee:
** Also affects: libfprint (Ubuntu Groovy)
Importance: Undecided
Status: New
** Changed in: libfprint (Ubuntu Groovy)
Importance: Undecided => High
** Changed in: libfprint (Ubuntu Groovy)
Status: New => In Progress
** Changed in: libfprint (Ubuntu Groovy)
Assignee:
** Also affects: libfprint (Ubuntu Groovy)
Importance: Undecided
Status: New
** Changed in: libfprint (Ubuntu Groovy)
Importance: Undecided => Low
** Changed in: libfprint (Ubuntu Groovy)
Status: New => In Progress
** Changed in: libfprint (Ubuntu Groovy)
Assignee:
** Also affects: libfprint (Ubuntu Groovy)
Importance: Undecided
Status: New
** Changed in: libfprint (Ubuntu Groovy)
Importance: Undecided => Low
** Changed in: libfprint (Ubuntu Groovy)
Status: New => In Progress
** Changed in: libfprint (Ubuntu Groovy)
Assignee:
** Also affects: libfprint (Ubuntu Groovy)
Importance: Undecided
Status: New
** Changed in: libfprint (Ubuntu Groovy)
Importance: Undecided => Medium
** Changed in: libfprint (Ubuntu Groovy)
Status: New => In Progress
** Changed in: libfprint (Ubuntu Groovy)
Assignee:
The additional rule should probably be:
owner /{dev,run}/shm/wayland.mozilla.ipc.[0-9]* rw,
** Changed in: firefox (Ubuntu)
Assignee: (unassigned) => Olivier Tilloy (osomon)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to
I can reproduce with firefox 83 on Ubuntu 20.04, and I can confirm that
the suggested addition to the apparmor profile fixes the problem.
** Changed in: firefox (Ubuntu)
Status: New => Confirmed
** Changed in: firefox (Ubuntu)
Importance: Undecided => Medium
--
You received this bug
** Summary changed:
- firefox crashes with MOZ_WAYLAND_ENABLE=1
+ firefox crashes with MOZ_ENABLE_WAYLAND=1
** Summary changed:
- firefox crashes with MOZ_ENABLE_WAYLAND=1
+ firefox crashes with MOZ_ENABLE_WAYLAND=1 when apparmor profile is enforced
--
You received this bug notification
My apologies for sidetracking this far trying to explain differences
between discovery and browsing but there seems to be a lot of mixing the
2 as one. The fact that you have "discovered" a server you wish to
"browse" is irrelivant for this bug (afaik you shouldn't have been able
to discover it as
use_vaapi is enabled by default (on amd64 and i386) starting with chromium 88
(currently dev channel).
snaps in the edge channel already have this, as do the bionic builds in
ppa:chromium-team/dev. Chromium depends on a version of libva that's too recent
for xenial, so I have disabled it for
Public bug reported:
[Impact]
On Ubuntu 20.04, with Synaptics fingerprint reader, users can use one
fingerprint to login system, but if users add more fingerprints, they
still can only one of those to login, other fingerprints do not work.
To fix this issue, we need support fingerprint
Public bug reported:
[ Impact ]
Fingerprint devices that we know are not supported, aren't properly put
in power-state mode
[ Test case ]
- Ensure you've a non-supported device from this list:
https://gitlab.freedesktop.org/libfprint/wiki/-/wikis/Unsupported%20Devices#usb-devices
-
** Changed in: firefox (Ubuntu)
Status: Confirmed => 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/1896722
Title:
Mozilla Firefox Multiple Arbitrary Code
Comment #14 in
https://bugs.chromium.org/p/chromium/issues/detail?id=1128405 suggests
that this might be a hardware issue. Are you able to observe the problem
with other mouses?
** Changed in: chromium-browser (Ubuntu)
Status: New => Incomplete
--
You received this bug notification
@Pedro Ribeiro
Same problem. Couldn't manage it to make it work
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xserver-xorg-input-libinput in Ubuntu.
https://bugs.launchpad.net/bugs/1887190
Title:
MSFT Touchpad not working on Lenovo
Can you share the output of running the following command in a terminal?
find ~/.mozilla/firefox -name *.xpi
--
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/1905122
Title:
Public bug reported:
[ Impact ]
[13359.449610] fprintd[355436]: segfault at 0 ip 7ffb9f375385 sp
7ffddc26ba90 error 4 in libfprint-2.so.2.0.0[7ffb9f36+3e000]
See upstream bug:
https://gitlab.freedesktop.org/libfprint/libfprint/-/issues/320
[ Test case ]
Build and run the tests
"does it work without the langpack extension manually installed? the system
package is supposed to be enough to provide the translations..."
I don't know, the language pack is installed automatically, but Firefox starts
in English.
--
You received this bug notification because you are a member
Public bug reported:
[Impact]
* We were advised by Synaptics to upgrade the existing libfprint in the
archive to include sensor support for 0xF9, 0xFC, 0xC2 as highlighted in
the following commits:
https://gitlab.freedesktop.org/libfprint/libfprint/-/commit/31319d9c6fe03f
[Test Case]
* We
As per upstream decision...
** Changed in: libfprint (Ubuntu)
Status: Confirmed => Won't Fix
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to libfprint in Ubuntu.
https://bugs.launchpad.net/bugs/1819406
Title:
Found broken a
If I were to speculate, someone tried to fix the "blocked by env" errors
in Firefox 82, in the process actually making that statement true with
some kind of fail code. In 84 they may have actually fixed whatever the
root problem reporting that message.
--
You received this bug notification
This is now invalid as libfprint changed a lot, open a new bug if
needed.
** Changed in: libfprint (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to libfprint in Ubuntu.
This is should not be an issue anymore as fprintd saves the prints in
/var/lib/fprintd
** Changed in: libfprint (Ubuntu)
Status: Confirmed => Fix Released
** Changed in: fingerprint-gui
Status: Confirmed => Invalid
** Changed in: lightdm
Status: Confirmed => Invalid
--
*** This bug is a duplicate of bug 602071 ***
https://bugs.launchpad.net/bugs/602071
** This bug has been marked a duplicate of bug 602071
[0a5c:5801] Broadcom fingerprint reader not working
--
You received this bug notification because you are a member of Desktop
Packages, which is
** Package changed: ubuntu => xorg (Ubuntu)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1905576
Title:
I cannot drag icons above to a particular region of my desktop
Status in xorg
Drivers requests are upstream issues and as such should be redirected to
the official wiki:
- https://gitlab.freedesktop.org/libfprint/wiki/-/wikis/Unsupported-
Devices
As per this, I'm closing all the requests, I please you to update that
wiki page if needed.
** Changed in: libfprint (Ubuntu)
You have been subscribed to a public bug:
I have two monitors set up, and one is vertical.
Here is a video:
https://cdn.discordapp.com/attachments/653633559206166541/781166447174352936/20201121_133143_1_1.mp4
1. Ubuntu 18.04.5 LTS
2. Not sure what package this is
3. I expected the icon to go
So, this is an issue that depends on device.
For MOH (match-on-host) devices there's no other option than doing this,
however the images are saved in a place where only root can access, so
are safe in a non-compromised system.
For MOC (match-on-chip) this is not the case so the issue is not
** Summary changed:
- Update simple-scan in Ubuntu 20.04 to 3.36.6 (fixes cannot scan a page using
EPSON V39 scanner)
+ Update simple-scan in Ubuntu 20.04 to 3.36.7 (fixes cannot scan a page using
EPSON V39 scanner)
** Description changed:
[ Description ]
GNOME upstream have released a
** Changed in: libfprint (Ubuntu)
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to libfprint in Ubuntu.
https://bugs.launchpad.net/bugs/744310
Title:
[138a:0005] [138a:0008] Fingerprint
** Changed in: libfprint (Ubuntu)
Status: Triaged => Fix Released
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to libfprint in Ubuntu.
https://bugs.launchpad.net/bugs/736793
Title:
[08ff:1680] AuthenTec, Inc. Fingerprint Sensor
** Changed in: libfprint (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to libfprint in Ubuntu.
https://bugs.launchpad.net/bugs/1065493
Title:
The "08ff:168f AuthenTec, Inc. Fingerprint
** Changed in: libfprint (Ubuntu)
Status: Triaged => Fix Released
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to libfprint in Ubuntu.
https://bugs.launchpad.net/bugs/657031
Title:
[08ff:2810] AuthenTec, Inc. AES2810
** Changed in: libfprint (Ubuntu)
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to libfprint in Ubuntu.
https://bugs.launchpad.net/bugs/1101647
Title:
ID 138a:003d Validity Sensors, Inc.
Status in
Drivers requests are upstream issues and as such should be redirected to
the official wiki:
- https://gitlab.freedesktop.org/libfprint/wiki/-/wikis/Unsupported-
Devices
As per this, I'm closing all the requests, I please you to update that
wiki page if needed.
** Changed in: libfprint (Ubuntu)
This should be supported by latest libfprint.
** Changed in: libfprint (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to libfprint in Ubuntu.
https://bugs.launchpad.net/bugs/1835522
Title:
Drivers requests are upstream issues and as such should be redirected to
the official wiki:
- https://gitlab.freedesktop.org/libfprint/wiki/-/wikis/Unsupported-
Devices
As per this, I'm closing all the requests, I please you to update that
wiki page if needed.
** Changed in: libfprint (Ubuntu)
Drivers requests are upstream bugs and as such should be redirected to
the official wiki
- https://gitlab.freedesktop.org/libfprint/wiki/-/wikis/Unsupported-
Devices
As per this, I'm closing all the requests, I please you to update that
wiki page if needed.
** Changed in: libfprint (Ubuntu)
Drivers requests are upstream issues and as such should be redirected to
the official wiki:
- https://gitlab.freedesktop.org/libfprint/wiki/-/wikis/Unsupported-
Devices
As per this, I'm closing all the requests, I please you to update that
wiki page if needed.
** Changed in: libfprint (Ubuntu)
** Changed in: libfprint (Ubuntu)
Status: Triaged => Fix Released
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to libfprint in Ubuntu.
https://bugs.launchpad.net/bugs/1750467
Title:
Backport upstream security fix patch
Status
That panel changed recently so please test it again with the new one.
** Changed in: libfprint (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to libfprint in Ubuntu.
Is this bug filed against the correct package?
--
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/1880198
Title:
Ubuntu as bluetooth speaker - volume on bluetooth client ignored
Would anyone have an idea as to a workaround, or an idea of how I could
debug this problem?
--
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/1880198
Title:
Ubuntu as bluetooth
Libfprint changed enough not to make this bug valid anymore, reopen if
needed but when testing with libfprint 1.90 or older.
** Changed in: libfprint (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to
Excellent, thanks Timo for the feedback. Let's do that, and leave the
bug status set to incomplete, which will make the bug report auto-expire
if nothing happens within the next 60 days.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to
Drivers requests are upstream bugs and as such should be redirected to
the official wiki
- https://gitlab.freedesktop.org/libfprint/wiki/-/wikis/Unsupported-
Devices
As per this, I'm closing all the requests, I please you to update that
wiki page if needed.
** Changed in: libfprint (Ubuntu)
Drivers requests are upstream bugs and as such should be redirected to
the official wiki
- https://gitlab.freedesktop.org/libfprint/wiki/-/wikis/Unsupported-
Devices
As per this, I'm closing all the requests, I please you to update that
wiki page if needed.
** Changed in: libfprint (Ubuntu)
Drivers requests are upstream bugs and as such should be redirected to
the official wiki
- https://gitlab.freedesktop.org/libfprint/wiki/-/wikis/Unsupported-
Devices
As per this, I'm closing all the requests, I please you to update that
wiki page if needed.
** Changed in: libfprint (Ubuntu)
1 - 100 of 157 matches
Mail list logo
