[Bug 1905519] Re: Object St.Bin (0x565425162c80), has been already deallocated — impossible to set any property on it. This might be caused by the object having been destroyed from C code using someth
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 => Confirmed ** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell-extension-ubuntu-dock in Ubuntu. https://bugs.launchpad.net/bugs/1905519 Title: Object St.Bin (0x565425162c80), has been already deallocated — impossible to set any property on it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs. To manage notifications about this bug go to: https://bugs.launchpad.net/dash-to-dock/+bug/1905519/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1758512] Re: No virtual terminals (CTRL+ALT+F?) when no user logged in
** 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 Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1758512 Title: No virtual terminals (CTRL+ALT+F?) when no user logged in To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1758512/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1758512] Re: No virtual terminals (CTRL+ALT+F?) when no user logged in; erratic behaviour when user logged in.
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 doesn't depends on video drivers or kernel flags and etc. For my laptop I've got the same for nvidia:455.38 and for i915, with modeset and with nomodset, with GFX grub mode and without. But I guess, this is not a system or hardware problem, because there are no any troubles with small environments. So after some research I found, that you can use `sudo kbd_mode`. So for me `sudo kbd_mode -af` works fine without reboot. * Laptop: DellXps 15 9570 4K Touch * Operating System: Kubuntu 20.04 * Kernel Version: 5.8.0-7630-generic #32~1605108853~20.04~8bcf10e~dev-Ubuntu (from system76) * OS Type: 64-bit * Processors: 12 × Intel® Core™ i7-8750H CPU @ 2.20GHz * Memory: 15,4 Gib Unfortunately I cannot find `DontVTSwitch` option in xorg.conf-like all-over the system, as was said for example here: * https://unix.stackexchange.com/questions/34158/rebinding-disabling-ctrlaltf-virtual-terminal-console-switching I think it'll be better solution. The solution of Fredrik Öhrström (oehrstroem) also sounds great. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1758512 Title: No virtual terminals (CTRL+ALT+F?) when no user logged in; erratic behaviour when user logged in. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1758512/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1905648] Re: fractional display scale cannot work properly
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 + [nvidia] fractional display scale cannot work properly ** Package changed: xorg (Ubuntu) => mutter (Ubuntu) ** Changed in: mutter (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1905648 Title: [nvidia] fractional display scale cannot work properly To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1905648/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1905648] [NEW] [nvidia] fractional display scale cannot work properly
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 after a update in May (forgot the exact date), fractional scaling cannot work properly anymore. After that update, I can just use 200% scale setting. I'm so sorry to report this bug so late. Also, I tested both with only the builtin screen and with an external monitor in 'Join Display' mode. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-54.60-generic 5.4.65 Uname: Linux 5.4.0-54-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/capabilities/gpu0' .proc.driver.nvidia.capabilities.mig: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/capabilities/mig' .proc.driver.nvidia.gpus..02.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:02:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 450.80.02 Wed Sep 23 01:13:39 UTC 2020 GCC version: gcc version 9.3.0 (Ubuntu 9.3.0-17ubuntu1~20.04) ApportVersion: 2.20.11-0ubuntu27.13 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Nov 26 09:54:20 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: nvidia, 450.80.02, 5.4.0-53-generic, x86_64: installed nvidia, 450.80.02, 5.4.0-54-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation UHD Graphics 620 (Whiskey Lake) [8086:3ea0] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Huawei Technologies Co., Ltd. UHD Graphics 620 (Whiskey Lake) [19e5:3e0c] Subsystem: Huawei Technologies Co., Ltd. GP108M [GeForce MX250] [19e5:3e0c] InstallationDate: Installed on 2020-05-02 (207 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 13d3:56db IMC Networks ov9734_azurewave_camera Bus 001 Device 002: ID 046d:c077 Logitech, Inc. M105 Optical Mouse Bus 001 Device 004: ID 8087:0aaa Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HUAWEI HBL-WX9 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-54-generic root=UUID=b1d9a025-3f1d-4fad-844f-c4e836944847 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/12/2019 dmi.bios.vendor: HUAWEI dmi.bios.version: 1.09 dmi.board.asset.tag: NULL dmi.board.name: HBL-WX9-PCB dmi.board.vendor: HUAWEI dmi.board.version: M1130 dmi.chassis.asset.tag: NULL dmi.chassis.type: 10 dmi.chassis.vendor: HUAWEI dmi.chassis.version: M1130 dmi.modalias: dmi:bvnHUAWEI:bvr1.09:bd08/12/2019:svnHUAWEI:pnHBL-WX9:pvrM1130:rvnHUAWEI:rnHBL-WX9-PCB:rvrM1130:cvnHUAWEI:ct10:cvrM1130: dmi.product.family: MagicBook dmi.product.name: HBL-WX9 dmi.product.sku: C233 dmi.product.version: M1130 dmi.sys.vendor: HUAWEI version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: mutter (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal nvidia regression-update resolution ubuntu xrandr-scaling -- [nvidia] fractional display scale cannot work properly https://bugs.launchpad.net/bugs/1905648 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1905519] Re: Object St.Bin (0x565425162c80), has been already deallocated — impossible to set any property on it. This might be caused by the object having been destroyed from C code using someth
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 https://github.com/micheleg/dash-to-dock/issues/1332 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell-extension-ubuntu-dock in Ubuntu. https://bugs.launchpad.net/bugs/1905519 Title: Object St.Bin (0x565425162c80), has been already deallocated — impossible to set any property on it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs. To manage notifications about this bug go to: https://bugs.launchpad.net/dash-to-dock/+bug/1905519/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1905576] Re: I cannot drag icons above to a particular region of my desktop
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 Ubuntu Desktop Bugs, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1905576 Title: I cannot drag icons above to a particular region of my desktop To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1905576/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1905637] Re: Games don't go full screen correctly with new version of libmutter
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 notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1905637 Title: Games don't go full screen correctly with new version of libmutter To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1905637/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1905576] [NEW] I cannot drag icons above to a particular region of my desktop
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 where I dragged it 4. The x-axis position was the same, but the y-axis position always gets set to a certain height whenever I drag above that height (I think this has to do with the top of my other display). ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 5.4.0-54.60~18.04.1-generic 5.4.65 Uname: Linux 5.4.0-54-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/capabilities/gpu0' .proc.driver.nvidia.capabilities.mig: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/capabilities/mig' .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 450.80.02 Wed Sep 23 01:13:39 UTC 2020 GCC version: gcc version 7.5.0 (Ubuntu 7.5.0-3ubuntu1~18.04) ApportVersion: 2.20.9-0ubuntu7.20 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Nov 25 09:20:33 2020 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: nvidia, 450.80.02, 5.4.0-53-generic, x86_64: installed nvidia, 450.80.02, 5.4.0-54-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation Device [10de:1e81] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Device [1043:8738] InstallationDate: Installed on 2020-10-12 (44 days ago) InstallationMedia: Ubuntu 18.04.5 LTS "Bionic Beaver" - Release amd64 (20200806.1) MachineType: Micro-Star International Co., Ltd. MS-7B12 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-54-generic root=UUID=321ae9a5-66cd-481d-b940-0f3c32a130c4 ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/30/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.71 dmi.board.asset.tag: Default string dmi.board.name: MEG Z390 ACE (MS-7B12) dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: 1.0 dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.71:bd10/30/2019:svnMicro-StarInternationalCo.,Ltd.:pnMS-7B12:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMEGZ390ACE(MS-7B12):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0: dmi.product.family: Default string dmi.product.name: MS-7B12 dmi.product.sku: Default string dmi.product.version: 1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.8-0ubuntu1~18.04.1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A ** Affects: nautilus (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic ubuntu -- I cannot drag icons above to a particular region of my desktop https://bugs.launchpad.net/bugs/1905576 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to nautilus in Ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1905186] Re: dock and top bar flashing non-stop at fullscreen
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 Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1905186 Title: dock and top bar flashing non-stop at fullscreen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1905186/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1905186] Re: dock and top bar flashing non-stop at fullscreen
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 Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1905186 Title: dock and top bar flashing non-stop at fullscreen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1905186/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1905209] Re: gnome-screensaver is blocked by an application to lock screen
** Information type changed from Private Security to Public -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-screensaver in Ubuntu. https://bugs.launchpad.net/bugs/1905209 Title: gnome-screensaver is blocked by an application to lock screen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-screensaver/+bug/1905209/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1905546] Re: Gnome Shell freezes randomly
*** 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 look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find. ** This bug has been marked a duplicate of bug 1897659 Kernel crash in nvidia_modeset hangs the whole graphic system (page allocation failure) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1905546 Title: Gnome Shell freezes randomly To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1905546/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1905186] Re: dock and top bar flashing non-stop at fullscreen
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 Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1905186 Title: dock and top bar flashing non-stop at fullscreen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1905186/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1905270] Re: [amdgpu] [nouveau] On any external monitors, wayland session has a white block on most part of the screen.
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. + [amdgpu] [nouveau] On any external monitors, wayland session has a white block on most part of the screen. ** Tags added: amdgpu nouveau ** Summary changed: - [amdgpu] [nouveau] On any external monitors, wayland session has a white block on most part of the screen. + [HP OMEN Laptop 15-en0xxx] [amdgpu] [nouveau] On any external monitors, wayland session has a white block on most part of the screen. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1905270 Title: [HP OMEN Laptop 15-en0xxx] [amdgpu] [nouveau] On any external monitors, wayland session has a white block on most part of the screen. To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1905270/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1904474] Re: Black/purple screen after booting Ubuntu
** 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 Ubuntu Desktop Bugs, which is subscribed to gnome-session in Ubuntu. https://bugs.launchpad.net/bugs/1904474 Title: Black/purple screen after booting Ubuntu To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1904474/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1904671] Re: After a certain amount of time after the session is launched, mouse clicks are no longer accepted
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 problem still happens, please follow these steps: https://wiki.ubuntu.com/Bugs/Responses#Missing_a_crash_report_or_having_a_.crash_attachment ** Package changed: xorg (Ubuntu) => gnome-shell (Ubuntu) ** Changed in: gnome-shell (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1904671 Title: After a certain amount of time after the session is launched, mouse clicks are no longer accepted To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1904671/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1905084] Re: Fractional scaling of external monitor and monitor positioning are lost when switching between single- and extended-display modes using the keyboard
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 Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1905084 Title: Fractional scaling of external monitor and monitor positioning are lost when switching between single- and extended-display modes using the keyboard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1905084/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1904671] [NEW] After a certain amount of time after the session is launched, mouse clicks are no longer accepted
You have been subscribed to a public bug: X11, Wayland, the Gnome Desktop does not recognize mouse clicks and drags after several tens of minutes after launching. However, it does recognize the movement of the mouse cursor. [How To Reploduce] 1. login in a Gnome session. 2. launch some applications. 3. use it for a few dozen minutes. 4. attempt to click and drag with a mouse or other pointing device. [Actual Result] I can no longer select mouse click application windows, activity buttons, dashes, etc. [Expect Result] I will accept mouse clicks until the end of the session, and possibly hope that the event is executed when the click is made. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: ubuntu-release-upgrader-core 1:20.10.13 ProcVersionSignature: Ubuntu 5.8.0-28.30-lowlatency 5.8.14 Uname: Linux 5.8.0-28-lowlatency x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu50.1 Architecture: amd64 CasperMD5CheckResult: skip CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Wed Nov 18 13:29:28 2020 InstallationDate: Installed on 2018-05-20 (913 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ja_JP.UTF-8 SHELL=/usr/bin/fish RebootRequiredPkgs: gnome-shell linux-image-5.8.0-29-lowlatency linux-base linux-image-5.8.0-29-generic linux-base SourcePackage: ubuntu-release-upgrader Symptom: dist-upgrade UpgradeStatus: Upgraded to groovy on 2020-10-25 (23 days ago) VarLogDistupgradeAptclonesystemstate.tar.gz: Error: command ['pkexec', 'cat', '/var/log/dist-upgrade/apt-clone_system_state.tar.gz'] failed with exit code 126: Error executing command as another user: Request dismissed VarLogDistupgradeApttermlog: Error: [Errno 13] 許可がありません: '/var/log/dist-upgrade/apt-term.log' VarLogDistupgradeTermlog: ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: Incomplete ** Tags: amd64 apport-bug dist-upgrade groovy -- After a certain amount of time after the session is launched, mouse clicks are no longer accepted https://bugs.launchpad.net/bugs/1904671 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1898462] Re: [groovy] Drag and drop files from Desktop to Nautilus freezes gnome-shell
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 Ubuntu Desktop Bugs, which is subscribed to gnome-shell-extension-desktop-icons in Ubuntu. https://bugs.launchpad.net/bugs/1898462 Title: [groovy] Drag and drop files from Desktop to Nautilus freezes gnome- shell To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-desktop-icons/+bug/1898462/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1878293] Re: xterm resize is wonky
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 Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1878293 Title: xterm resize is wonky To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1878293/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1897224] Re: Graphical snaps can't run in Gnome 3.38 Wayland sessions (can't open X display)
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 Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1897224 Title: Graphical snaps can't run in Gnome 3.38 Wayland sessions (can't open X display) To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1897224/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1905637] Re: Games don't go full screen correctly with new version of libmutter
** 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, both native + games) don't go full screen correctly (even configured for it). I + tracked down the problem to a regression on package libmutter-7-0. The + problem occurs with latest version, 3.38.1-2ubuntu1, but when I downgrade the package (and also the package gir1.2-mutter-7) to - 3.38.1-1ubuntu1 all works correctly. + 3.38.1-1ubuntu1 the gomes went full screen normally. I'm using Ubuntu 20.10. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1905637 Title: Games don't go full screen correctly with new version of libmutter To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1905637/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1905637] [NEW] Games don't go full screen correctly with new version of libmutter
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 3.38.1-1ubuntu1 all works correctly. I'm using Ubuntu 20.10. ** Affects: mutter (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1905637 Title: Games don't go full screen correctly with new version of libmutter To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1905637/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1897613] Re: fprint hangs after first finger scan (fprintd-enroll) with AES3500
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, resubmitting commands. This also needs proper commands cancellation (LP: #1897613) - Add support for new Synaptics devices IDs (LP: #1905593) - Fix vfs301 verification using device pointer on callbacks (LP: #1905597) - Ensure we do not waste power for unsupported devices (LP: #1905603) - Add identification support to synaptics driver. It allows to unlock / log-in with any finger. (LP: #1905600) -- Marco Trevisan (Treviño) Wed, 25 Nov 2020 19:18:20 +0100 ** Changed in: libfprint (Ubuntu) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to libfprint in Ubuntu. https://bugs.launchpad.net/bugs/1897613 Title: fprint hangs after first finger scan (fprintd-enroll) with AES3500 To manage notifications about this bug go to: https://bugs.launchpad.net/libfprint/+bug/1897613/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1905593] Re: Support synaptics devices 0xF9, 0xFC, 0xC2
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, resubmitting commands. This also needs proper commands cancellation (LP: #1897613) - Add support for new Synaptics devices IDs (LP: #1905593) - Fix vfs301 verification using device pointer on callbacks (LP: #1905597) - Ensure we do not waste power for unsupported devices (LP: #1905603) - Add identification support to synaptics driver. It allows to unlock / log-in with any finger. (LP: #1905600) -- Marco Trevisan (Treviño) Wed, 25 Nov 2020 19:18:20 +0100 ** Changed in: libfprint (Ubuntu) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to libfprint in Ubuntu. https://bugs.launchpad.net/bugs/1905593 Title: Support synaptics devices 0xF9, 0xFC, 0xC2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libfprint/+bug/1905593/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1905597] Re: Device using vfs301 driver crashes during verification
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, resubmitting commands. This also needs proper commands cancellation (LP: #1897613) - Add support for new Synaptics devices IDs (LP: #1905593) - Fix vfs301 verification using device pointer on callbacks (LP: #1905597) - Ensure we do not waste power for unsupported devices (LP: #1905603) - Add identification support to synaptics driver. It allows to unlock / log-in with any finger. (LP: #1905600) -- Marco Trevisan (Treviño) Wed, 25 Nov 2020 19:18:20 +0100 ** Changed in: libfprint (Ubuntu) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to libfprint in Ubuntu. https://bugs.launchpad.net/bugs/1905597 Title: Device using vfs301 driver crashes during verification To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libfprint/+bug/1905597/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1905600] Re: Support fingerprint identification in the driver of Synaptics fingerprint reader
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, resubmitting commands. This also needs proper commands cancellation (LP: #1897613) - Add support for new Synaptics devices IDs (LP: #1905593) - Fix vfs301 verification using device pointer on callbacks (LP: #1905597) - Ensure we do not waste power for unsupported devices (LP: #1905603) - Add identification support to synaptics driver. It allows to unlock / log-in with any finger. (LP: #1905600) -- Marco Trevisan (Treviño) Wed, 25 Nov 2020 19:18:20 +0100 ** Changed in: libfprint (Ubuntu) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to libfprint in Ubuntu. https://bugs.launchpad.net/bugs/1905600 Title: Support fingerprint identification in the driver of Synaptics fingerprint reader To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1905600/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1905603] Re: Unsupported USB devices are using power even if not used
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, resubmitting commands. This also needs proper commands cancellation (LP: #1897613) - Add support for new Synaptics devices IDs (LP: #1905593) - Fix vfs301 verification using device pointer on callbacks (LP: #1905597) - Ensure we do not waste power for unsupported devices (LP: #1905603) - Add identification support to synaptics driver. It allows to unlock / log-in with any finger. (LP: #1905600) -- Marco Trevisan (Treviño) Wed, 25 Nov 2020 19:18:20 +0100 ** Changed in: libfprint (Ubuntu) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to libfprint in Ubuntu. https://bugs.launchpad.net/bugs/1905603 Title: Unsupported USB devices are using power even if not used To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libfprint/+bug/1905603/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 887845] Re: New search function sucks
*** 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 Ubuntu Desktop Bugs, which is subscribed to gedit in Ubuntu. https://bugs.launchpad.net/bugs/887845 Title: New search function sucks To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/887845/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1876879] Re: gnome-software cannot install classic snaps if a channel is selected
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 Ubuntu Desktop Bugs, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1876879 Title: gnome-software cannot install classic snaps if a channel is selected To manage notifications about this bug go to: https://bugs.launchpad.net/snap-store-desktop/+bug/1876879/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1905623] [NEW] df: /run/user/1000/doc: Operation not permitted
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 out fs type, so my fs type ignoring doesn't work). ** Affects: xdg-desktop-portal (Ubuntu) Importance: Low Status: New ** Changed in: xdg-desktop-portal (Ubuntu) Importance: Undecided => Low -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to xdg-desktop-portal in Ubuntu. https://bugs.launchpad.net/bugs/1905623 Title: df: /run/user/1000/doc: Operation not permitted To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xdg-desktop-portal/+bug/1905623/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1897613] Re: fprint hangs after first finger scan (fprintd-enroll) with AES3500
** 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: (unassigned) => Marco Trevisan (Treviño) (3v1n0) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to libfprint in Ubuntu. https://bugs.launchpad.net/bugs/1897613 Title: fprint hangs after first finger scan (fprintd-enroll) with AES3500 To manage notifications about this bug go to: https://bugs.launchpad.net/libfprint/+bug/1897613/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1905593] Re: Support synaptics devices 0xF9, 0xFC, 0xC2
** 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: (unassigned) => Marco Trevisan (Treviño) (3v1n0) ** Also affects: libfprint (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: libfprint (Ubuntu Focal) Importance: Undecided => Medium ** Changed in: libfprint (Ubuntu Focal) Status: New => In Progress ** Changed in: libfprint (Ubuntu Focal) Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to libfprint in Ubuntu. https://bugs.launchpad.net/bugs/1905593 Title: Support synaptics devices 0xF9, 0xFC, 0xC2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libfprint/+bug/1905593/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1905597] Re: Device using vfs301 driver crashes during verification
** 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: (unassigned) => Marco Trevisan (Treviño) (3v1n0) ** Also affects: libfprint (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: libfprint (Ubuntu Focal) Importance: Undecided => Low ** Changed in: libfprint (Ubuntu Focal) Status: New => In Progress ** Changed in: libfprint (Ubuntu Focal) Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to libfprint in Ubuntu. https://bugs.launchpad.net/bugs/1905597 Title: Device using vfs301 driver crashes during verification To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libfprint/+bug/1905597/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1905600] Re: Support fingerprint identification in the driver of Synaptics fingerprint reader
** 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: (unassigned) => Marco Trevisan (Treviño) (3v1n0) ** Also affects: libfprint (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: libfprint (Ubuntu Focal) Importance: Undecided => High ** Changed in: libfprint (Ubuntu Focal) Status: New => In Progress ** Changed in: libfprint (Ubuntu Focal) Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to libfprint in Ubuntu. https://bugs.launchpad.net/bugs/1905600 Title: Support fingerprint identification in the driver of Synaptics fingerprint reader To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1905600/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1905603] Re: Unsupported USB devices are using power even if not used
** 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: (unassigned) => Marco Trevisan (Treviño) (3v1n0) ** Also affects: libfprint (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: libfprint (Ubuntu Focal) Importance: Undecided => Medium ** Changed in: libfprint (Ubuntu Focal) Status: New => In Progress ** Changed in: libfprint (Ubuntu Focal) Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to libfprint in Ubuntu. https://bugs.launchpad.net/bugs/1905603 Title: Unsupported USB devices are using power even if not used To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libfprint/+bug/1905603/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1828107] Re: gvfs can't list shares from smb servers that disabled SMB1
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 there are currently no working mechanisms to do so in LTS versions judging from the open bug reports). If however you are experiencing a crash whilst attempting to browse a share of the discovered host, that is relevant and is to do with the way SMB protocol versions themselves are being handled. WRT the rest of the discussion: SMBv1 leveraged NetBios to do discovery, (as did WINS which was a fallback discovery method). With SMBv1 removed/disabled, all of the NetBios discovery is also removed/disabled. Therefore, a discovery protocol is needed. Enter WSD. SMBv2 and SMBv3 use WSD to discover hosts on the network, (incidentally WSD was designed for SMBv2 during the development of Vista to remove the dependancy on NetBios). If you know the address of a host serving SMBv2 or SMBv3 already (via WSD, any other discovery protocol, off by heart), you can just do an SMB request against that address: smbclient --list=<> --user=Anonymous -N >The discoverability and connectivity works when the process is terminated and >restarted. Clearly this is achievable. > Yes, netbios was used previously, but clearly after killing the process I can > reach them without SMB v1, just not after the first boot. This is still probably nothing more than a cached entry, start-up check of previously known hosts, or initial broadcast. Some of which may or may not be unintentional from a security perspective, so as @seb128 said, file another bug report against them if you so wish. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/1828107 Title: gvfs can't list shares from smb servers that disabled SMB1 To manage notifications about this bug go to: https://bugs.launchpad.net/gvfs/+bug/1828107/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1905600] [NEW] Support fingerprint identification in the driver of Synaptics fingerprint reader
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 identification in the driver of Synaptics fingerprint reader, by backport this libfprint commit to Focal: https://gitlab.freedesktop.org/libfprint/libfprint/commit/e27b65c9 [Test Case] I tried backport the commit above to libfprint (1:1.90.2+tod1-0ubuntu1~20.04.2) in Focal and tested on 3 ThinkPads(both use the 06cb:00bd Synaptics fingerprint reader), the multiple fingerprints works well. We have other OEM platforms with Synaptics fingerprint reader, we can use it to validate the changes if needed. [Regression Potential] the commit comes from Synaptics' engineer, just affects one file: libfprint/drivers/synaptics/synaptics.c, and only add identification support in that file, so the regression potential should be low. ** Affects: oem-priority Importance: High Assignee: Shengyao Xue (xueshengyao) Status: In Progress ** Affects: libfprint (Ubuntu) Importance: High Assignee: Marco Trevisan (Treviño) (3v1n0) Status: In Progress ** Tags: oem-priority originate-from-1903502 sutton ** Changed in: oem-priority Importance: Undecided => High ** Changed in: oem-priority Assignee: (unassigned) => Shengyao Xue (xueshengyao) ** Also affects: libfprint (Ubuntu) Importance: Undecided Status: New ** Changed in: oem-priority Status: New => In Progress -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to libfprint in Ubuntu. https://bugs.launchpad.net/bugs/1905600 Title: Support fingerprint identification in the driver of Synaptics fingerprint reader To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1905600/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1905603] [NEW] Unsupported USB devices are using power even if not used
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 - Ensure the device stays in power-save mode: - You can use powertop, or follow this [1] [ Regression potential ] A device that is supported or used by another tool may be put in power- save mode [1] https://web.archive.org/web/20120420112755/http://www.lesswatts.org/projects /devices-power-management/usb.php ** Affects: libfprint (Ubuntu) Importance: Medium Assignee: Marco Trevisan (Treviño) (3v1n0) Status: In Progress -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to libfprint in Ubuntu. https://bugs.launchpad.net/bugs/1905603 Title: Unsupported USB devices are using power even if not used To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libfprint/+bug/1905603/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1905597] [NEW] Device using vfs301 driver crashes during verification
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 included into libfprint to ensure this doesn't happen anymore as the upstream sources include an umockdev based device that simulates the actual device interaction for enroll an verification Otherwise: user testing [ Regression potential ] Capture doesn't happen properly ** Affects: libfprint (Ubuntu) Importance: Low Assignee: Marco Trevisan (Treviño) (3v1n0) Status: In Progress -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to libfprint in Ubuntu. https://bugs.launchpad.net/bugs/1905597 Title: Device using vfs301 driver crashes during verification To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libfprint/+bug/1905597/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1905593] [NEW] Support synaptics devices 0xF9, 0xFC, 0xC2
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 have several OEM platforms with these Synaptics sensors enabled with Focal and they can be used to validate these changes. [Regression Potential] * Regression potential for an updated libfprint with these new PIDs is low [Other Info] ** Affects: libfprint (Ubuntu) Importance: Medium Assignee: Marco Trevisan (Treviño) (3v1n0) Status: In Progress -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to libfprint in Ubuntu. https://bugs.launchpad.net/bugs/1905593 Title: Support synaptics devices 0xF9, 0xFC, 0xC2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libfprint/+bug/1905593/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1819406] Re: Found broken a feature for fingerprint image obfuscation
As per upstream decision... ** Changed in: libfprint (Ubuntu) Status: Confirmed => Won't Fix -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to libfprint in Ubuntu. https://bugs.launchpad.net/bugs/1819406 Title: Found broken a feature for fingerprint image obfuscation To manage notifications about this bug go to: https://bugs.launchpad.net/libfprint/+bug/1819406/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1653000] Re: Assertion crash with Validity VFS301
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 Ubuntu Desktop Bugs, which is subscribed to libfprint in Ubuntu. https://bugs.launchpad.net/bugs/1653000 Title: Assertion crash with Validity VFS301 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libfprint/+bug/1653000/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 998367] Re: fingerprint login can't access encrypted home user account
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 -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to libfprint in Ubuntu. https://bugs.launchpad.net/bugs/998367 Title: fingerprint login can't access encrypted home user account To manage notifications about this bug go to: https://bugs.launchpad.net/fingerprint-gui/+bug/998367/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1029551] Re: Dell Fingerprint
*** 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 Ubuntu Desktop Bugs, which is subscribed to libfprint in Ubuntu. https://bugs.launchpad.net/bugs/1029551 Title: Dell Fingerprint To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libfprint/+bug/1029551/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1811368] Re: Elan touchpad fingerprint reader is not recognized by ubuntu 18.10 and 20.04
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) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to libfprint in Ubuntu. https://bugs.launchpad.net/bugs/1811368 Title: Elan touchpad fingerprint reader is not recognized by ubuntu 18.10 and 20.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libfprint/+bug/1811368/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1818938] Re: Found storing user fingerprints as raw image files
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 valid. As per this, I think we can close the issue. ** Changed in: libfprint (Ubuntu) Status: Triaged => Won't Fix -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to libfprint in Ubuntu. https://bugs.launchpad.net/bugs/1818938 Title: Found storing user fingerprints as raw image files To manage notifications about this bug go to: https://bugs.launchpad.net/libfprint/+bug/1818938/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 657031] Re: [08ff:2810] AuthenTec, Inc. AES2810 fingerprint reader not recognized (worked in 10.04)
** Changed in: libfprint (Ubuntu) Status: Triaged => Fix Released -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to libfprint in Ubuntu. https://bugs.launchpad.net/bugs/657031 Title: [08ff:2810] AuthenTec, Inc. AES2810 fingerprint reader not recognized (worked in 10.04) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-release-notes/+bug/657031/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 736793] Re: [08ff:1680] AuthenTec, Inc. Fingerprint Sensor doesn't work
** Changed in: libfprint (Ubuntu) Status: Triaged => Fix Released -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to libfprint in Ubuntu. https://bugs.launchpad.net/bugs/736793 Title: [08ff:1680] AuthenTec, Inc. Fingerprint Sensor doesn't work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libfprint/+bug/736793/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 744310] Re: [138a:0005] [138a:0008] Fingerprint Validity reader devices VFS301 and VFS300 not recognized.
** Changed in: libfprint (Ubuntu) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to libfprint in Ubuntu. https://bugs.launchpad.net/bugs/744310 Title: [138a:0005] [138a:0008] Fingerprint Validity reader devices VFS301 and VFS300 not recognized. To manage notifications about this bug go to: https://bugs.launchpad.net/fingerprint-gui/+bug/744310/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1065493] Re: The "08ff:168f AuthenTec, Inc. Fingerprint Sensor does not work on Ubuntu 12.04
** Changed in: libfprint (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to libfprint in Ubuntu. https://bugs.launchpad.net/bugs/1065493 Title: The "08ff:168f AuthenTec, Inc. Fingerprint Sensor does not work on Ubuntu 12.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libfprint/+bug/1065493/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1101647] Re: ID 138a:003d Validity Sensors, Inc.
** Changed in: libfprint (Ubuntu) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to libfprint in Ubuntu. https://bugs.launchpad.net/bugs/1101647 Title: ID 138a:003d Validity Sensors, Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libfprint/+bug/1101647/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1641290] Re: [04f3:0903] Elan Microelectronics Corp fingerprint reader not recognised
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) Status: Confirmed => Invalid ** Changed in: libfprint (Ubuntu) Status: Invalid => Fix Released -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to libfprint in Ubuntu. https://bugs.launchpad.net/bugs/1641290 Title: [04f3:0903] Elan Microelectronics Corp fingerprint reader not recognised To manage notifications about this bug go to: https://bugs.launchpad.net/libfprint/+bug/1641290/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1835522] Re: 04f3:0c03 Elan Microelectronics Corp. is not recognized
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 Ubuntu Desktop Bugs, which is subscribed to libfprint in Ubuntu. https://bugs.launchpad.net/bugs/1835522 Title: 04f3:0c03 Elan Microelectronics Corp. is not recognized To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libfprint/+bug/1835522/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1839012] Re: Asus A407Ma
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) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to libfprint in Ubuntu. https://bugs.launchpad.net/bugs/1839012 Title: Asus A407Ma To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libfprint/+bug/1839012/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 602071] Re: [0a5c:5801] Broadcom fingerprint reader not working
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) Status: Triaged => Invalid -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to libfprint in Ubuntu. https://bugs.launchpad.net/bugs/602071 Title: [0a5c:5801] Broadcom fingerprint reader not working To manage notifications about this bug go to: https://bugs.launchpad.net/libfprint/+bug/602071/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1051032] Re: [138a:003c] Validity VFS471 Fingerprint Reader not recognized
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) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to libfprint in Ubuntu. https://bugs.launchpad.net/bugs/1051032 Title: [138a:003c] Validity VFS471 Fingerprint Reader not recognized To manage notifications about this bug go to: https://bugs.launchpad.net/libfprint/+bug/1051032/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1750467] Re: Backport upstream security fix patch
** Changed in: libfprint (Ubuntu) Status: Triaged => Fix Released -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to libfprint in Ubuntu. https://bugs.launchpad.net/bugs/1750467 Title: Backport upstream security fix patch To manage notifications about this bug go to: https://bugs.launchpad.net/libfprint/+bug/1750467/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1859811] Re: Fingerprint enrollment wizard doesn't work
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 Ubuntu Desktop Bugs, which is subscribed to libfprint in Ubuntu. https://bugs.launchpad.net/bugs/1859811 Title: Fingerprint enrollment wizard doesn't work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libfprint/+bug/1859811/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 318397] Re: [08ff:1600] AES1600 fingerprint reader: gdm segfaults sometimes using libfprint (finger print authentification)
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 Ubuntu Desktop Bugs, which is subscribed to libfprint in Ubuntu. https://bugs.launchpad.net/bugs/318397 Title: [08ff:1600] AES1600 fingerprint reader: gdm segfaults sometimes using libfprint (finger print authentification) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libfprint/+bug/318397/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 745505] Re: [138a:0007] VFS451 fingerprint reader not recognized
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) Status: Triaged => Invalid -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to libfprint in Ubuntu. https://bugs.launchpad.net/bugs/745505 Title: [138a:0007] VFS451 fingerprint reader not recognized To manage notifications about this bug go to: https://bugs.launchpad.net/fingerprint-gui/+bug/745505/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1743479] Re: [138a:0097] Validity sensor driver request
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) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to libfprint in Ubuntu. https://bugs.launchpad.net/bugs/1743479 Title: [138a:0097] Validity sensor driver request To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libfprint/+bug/1743479/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1809425] Re: [06cb:009a] Validity / Synaptic driver request
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) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to libfprint in Ubuntu. https://bugs.launchpad.net/bugs/1809425 Title: [06cb:009a] Validity / Synaptic driver request To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libfprint/+bug/1809425/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1857338] Re: GIMP Crash during Launching
*** This bug is a duplicate of bug 1857254 *** https://bugs.launchpad.net/bugs/1857254 Hello there! Don't install Gimp 2.10.20. On Ubuntu Software Manager select snap/store > latest/edge > 2.10.22 and install it -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gimp in Ubuntu. https://bugs.launchpad.net/bugs/1857338 Title: GIMP Crash during Launching To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gimp/+bug/1857338/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1876502] Re: Elan Microelectronics Corp fingerprint reader not recognized
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) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to libfprint in Ubuntu. https://bugs.launchpad.net/bugs/1876502 Title: Elan Microelectronics Corp fingerprint reader not recognized To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libfprint/+bug/1876502/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1885167] Re: 27c6:55a4 Goodix FingerPrint on Lenovo Thinkbook 14-IIL and 15-IIL not found
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) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to libfprint in Ubuntu. https://bugs.launchpad.net/bugs/1885167 Title: 27c6:55a4 Goodix FingerPrint on Lenovo Thinkbook 14-IIL and 15-IIL not found To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libfprint/+bug/1885167/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1397067] Re: ID 138a:003f Validity Sensors, Inc. on HP EliteBook 840G1
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) Status: Confirmed => Won't Fix ** Changed in: libfprint (Ubuntu) Status: Won't Fix => Invalid -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to libfprint in Ubuntu. https://bugs.launchpad.net/bugs/1397067 Title: ID 138a:003f Validity Sensors, Inc. on HP EliteBook 840G1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libfprint/+bug/1397067/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1519272] Re: [138a:0010] Please support Validity Sensors reader
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) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to libfprint in Ubuntu. https://bugs.launchpad.net/bugs/1519272 Title: [138a:0010] Please support Validity Sensors reader To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libfprint/+bug/1519272/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1382165] Re: [138a:0017] Please support Validity Sensors reader
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) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to libfprint in Ubuntu. https://bugs.launchpad.net/bugs/1382165 Title: [138a:0017] Please support Validity Sensors reader To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libfprint/+bug/1382165/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1619589] Re: [138a:0090] Validity Sensors fingerprint reader not recognized
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) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to libfprint in Ubuntu. https://bugs.launchpad.net/bugs/1619589 Title: [138a:0090] Validity Sensors fingerprint reader not recognized To manage notifications about this bug go to: https://bugs.launchpad.net/libfprint/+bug/1619589/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1715112] Re: [138a:0091] Please support Validity Sensors reader
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) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to libfprint in Ubuntu. https://bugs.launchpad.net/bugs/1715112 Title: [138a:0091] Please support Validity Sensors reader To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libfprint/+bug/1715112/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1828107] Re: gvfs can't list shares from smb servers that disabled SMB1
I don't use Windows for serving SMB, I was simply linking the reason for deprecation. FreeNAS, and other non-windows systems serve SMB v2 and higher for network shares, and WSD is not present, relevant, or desired in those configurations. WSD is not the solution, nor replacement, and SMB v2 and v3 have existed for longer than WSD. Yes, netbios was used previously, but clearly after killing the process I can reach them without SMB v1, just not after the first boot. And just because that's the workaround, does not make it warrant another thread... -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/1828107 Title: gvfs can't list shares from smb servers that disabled SMB1 To manage notifications about this bug go to: https://bugs.launchpad.net/gvfs/+bug/1828107/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1857338] Re: GIMP Crash during Launching
*** This bug is a duplicate of bug 1857254 *** https://bugs.launchpad.net/bugs/1857254 OMG! Back to windows to use Gimp! -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gimp in Ubuntu. https://bugs.launchpad.net/bugs/1857338 Title: GIMP Crash during Launching To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gimp/+bug/1857338/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1828107] Re: gvfs can't list shares from smb servers that disabled SMB1
In the very same article you linked: https://docs.microsoft.com/en-us /windows-server/storage/file-server/troubleshoot/smbv1-not-installed-by- default-in-windows With SMBv1 being removed, Network Browser (which depended on SMBv1) was removed, all of which relied on NetBios being used for discovery. (Hence, NetBios is dead, long live NetBios). Microsoft's replacement for NetBios discovery is *drumroll please*: WSD. I'm completely speculating here but: Your initial start up effect is probably gvfsd-smbd doing something like a Browser Tree scan of last known hosts. This actively goes to the host asking about available protocols, shares etc. This is NOT discovery. You could argue "well if it already knew about it, how does it lose it?" and that is a fair question, to which the answer might well be "Don't want to do an expensive back n forth poll, would rather use a discovery protocol", and now we are back to the discussion of needing a discovery protocol: WSD. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/1828107 Title: gvfs can't list shares from smb servers that disabled SMB1 To manage notifications about this bug go to: https://bugs.launchpad.net/gvfs/+bug/1828107/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1828107] Re: gvfs can't list shares from smb servers that disabled SMB1
> I can browse to my SMB shares just by killing and restarting the gvfsd-smbd process you should register a new bug then because that's not what that one is about, quoting the title 'gvfs can't list shares from smb servers that disabled SMB1' -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/1828107 Title: gvfs can't list shares from smb servers that disabled SMB1 To manage notifications about this bug go to: https://bugs.launchpad.net/gvfs/+bug/1828107/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1828107] Re: gvfs can't list shares from smb servers that disabled SMB1
Um, no. Microsoft did not deprecate SMB v1 for WSD, they did it because it has a blatant security flaw in it : https://techcommunity.microsoft.com/t5/storage-at-microsoft/stop-using- smb1/ba-p/425858 Furthermore, SMB v2 and v3.x has been out for years, as modern implementations of the protocol, _not_ WSD. And again, I can browse to my SMB shares just by killing and restarting the gvfsd-smbd process, so clearly this has nothing to do with WSD at all, since that's not in play in my environment at all (I know this because my FreeNAS system doesn't serve WSD). -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/1828107 Title: gvfs can't list shares from smb servers that disabled SMB1 To manage notifications about this bug go to: https://bugs.launchpad.net/gvfs/+bug/1828107/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1828107] Re: gvfs can't list shares from smb servers that disabled SMB1
Not to put too fine a point on it, but actually that is exactly what this requires. Microsoft phased out the SMBv1 protocol, (NetBios is dead, long live NetBios), in favour of their new protocol: Web Services Dynamic Discovery (WSD). There has been a lot of discussion and work as to exactly HOW WSD should be implemented for SAMBA and gvfs and what to do in future if Microsoft do another flip of the switch. Granted this has taken a lot of time, but as previously mentioned, all of this discussion and development is dependent on people gratuitously handing over their free time. If you want up to date support and to demand for things to be done, might I politely suggest you fork out for a Red Hat enterprise subscription. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/1828107 Title: gvfs can't list shares from smb servers that disabled SMB1 To manage notifications about this bug go to: https://bugs.launchpad.net/gvfs/+bug/1828107/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1828107] Re: gvfs can't list shares from smb servers that disabled SMB1
There's no way the solution to this is implementing a new protocol to replace SMB, that would be absurd. The discoverability and connectivity works when the process is terminated and restarted. Clearly this is achievable. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/1828107 Title: gvfs can't list shares from smb servers that disabled SMB1 To manage notifications about this bug go to: https://bugs.launchpad.net/gvfs/+bug/1828107/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1905100] Re: Cover art not shown for file which has a cover art
I'm uploading the journalctl log from the current session now, because i just tagged a file called "Akcent - Special Girl (One Love).m4a" and it doesn't have a thumbnail shown by Nautilus. ** Attachment added: "journal.txt" https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1905100/+attachment/5437887/+files/journal.txt -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1905100 Title: Cover art not shown for file which has a cover art To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1905100/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1897224] Re: Graphical snaps can't run in Gnome 3.38 Wayland sessions (can't open X display)
Is it possible to say (approximately) when the update will come to regular Groovy release? -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1897224 Title: Graphical snaps can't run in Gnome 3.38 Wayland sessions (can't open X display) To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1897224/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1766230] Re: Strange window matching behaviour between Slack and Chrome
Same issue in Ubuntu 20.10 with Slack and Brave browser -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1766230 Title: Strange window matching behaviour between Slack and Chrome To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1766230/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1905546] [NEW] Gnome Shell freezes randomly
Public bug reported: Description is almost the same as https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1807534 Ubuntu 18.04.5 LTS, all packages up to date gnome-shell 3.28.4-0ubuntu18.04.3 Sometimes gnome-shell freezes. I can move the mouse pointer, but the rest of the UI is completely frozen and does not react to mouse clicks or keystrokes. If I try to change login session with Ctrl-Alt-F1, I can login but the screen remains black. I generally manage to "unfreeze" gnome-shell by switching to a virtual console and typing "killall -3 gnome-shell" dmesg shows a page allocation failure in gnome-shell, cf attached file. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.28.4-0ubuntu18.04.3 ProcVersionSignature: Ubuntu 5.4.0-54.60~18.04.1-generic 5.4.65 Uname: Linux 5.4.0-54-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.20 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Nov 25 11:10:35 2020 DisplayManager: gdm3 InstallationDate: Installed on 2020-02-21 (278 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic third-party-packages ** Attachment added: "extract of dmesg covering 2 gnome-shell freezes" https://bugs.launchpad.net/bugs/1905546/+attachment/5437817/+files/dmesg.txt -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1905546 Title: Gnome Shell freezes randomly To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1905546/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1898462] Re: [groovy] Drag and drop files from Desktop to Nautilus freezes gnome-shell
** Tags added: rls-gg-incoming -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell-extension-desktop-icons in Ubuntu. https://bugs.launchpad.net/bugs/1898462 Title: [groovy] Drag and drop files from Desktop to Nautilus freezes gnome- shell To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-desktop-icons/+bug/1898462/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1828107] Re: gvfs can't list shares from smb servers that disabled SMB1
The bug isn't ignored but implementing a new protocol is not trivial, also you are commenting on the wrong place, Ubuntu isn't writting that software. Stating that volunteers or companies not doing work for you for free is unacceptable is probably not going to bring you far though... On the bug status, see https://wiki.ubuntu.com/Bugs/Bug%20statuses Triaged is used to describe issues which are understood, there is an inprogress for work that has started ** Changed in: gvfs (Ubuntu) Importance: Medium => High -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/1828107 Title: gvfs can't list shares from smb servers that disabled SMB1 To manage notifications about this bug go to: https://bugs.launchpad.net/gvfs/+bug/1828107/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1855318] Re: autofs tries to find .xdg-volume-info and autorun.inf
** Changed in: gvfs (Ubuntu) Status: Confirmed => Triaged ** Changed in: gvfs (Ubuntu) Importance: Undecided => Low ** Also affects: gvfs via https://gitlab.gnome.org/GNOME/gvfs/-/issues/287 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/1855318 Title: autofs tries to find .xdg-volume-info and autorun.inf To manage notifications about this bug go to: https://bugs.launchpad.net/gvfs/+bug/1855318/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
