[Kernel-packages] [Bug 1972725] Re: Smart Card Reader (RTS5169 and chipsets) stops working in Ubuntu 22.04
In the linked answer, a proposal to turn on the pcscd service with sudo systemctl start pcscd fixed the issue. Now the question is why that service is not running automatically? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1972725 Title: Smart Card Reader (RTS5169 and chipsets) stops working in Ubuntu 22.04 Status in linux package in Ubuntu: Confirmed Bug description: This chipset from Realtek (card reader) was supported in Ubuntu 18.04 and 20.04. After upgrading to Ubuntu 22.04, the card reader no longer works. The system recognizes 'something' when I plug it in: Bus 003 Device 007: ID 0bda:0165 Realtek Semiconductor Corp. Smart Card Reader Interface Yet when I open the software to read my ID, it says "No card reader found". When I plug in my ID, I'm expecting to see a LED turn on but that doesn't happen in 22.04 anymore (still does in 20.04). This chipset is used in a very common card readers. While it's definitely more than a couple years old, it's still a product that is commonly used. (please see https://answers.launchpad.net/ubuntu/+question/701636 for more information) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CRDA: N/A CasperMD5CheckResult: pass DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-04-22 (18 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) IwConfig: lono wireless extensions. enp3s0no wireless extensions. MachineType: MSI MS-7821 NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-27-generic root=UUID=9c9b89dd-6496-4ec9-974d-fd3b84d8288d ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.15.0-27-generic N/A linux-backports-modules-5.15.0-27-generic N/A linux-firmware 20220329.git681281e4-0ubuntu1 RfKill: Tags: jammy Uname: Linux 5.15.0-27-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 07/21/2014 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: V1.9 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Z87-G45 GAMING (MS-7821) dmi.board.vendor: MSI dmi.board.version: 1.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrV1.9:bd07/21/2014:br4.6:svnMSI:pnMS-7821:pvr1.0:rvnMSI:rnZ87-G45GAMING(MS-7821):rvr1.0:cvnMSI:ct3:cvr1.0:skuTobefilledbyO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7821 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 1.0 dmi.sys.vendor: MSI To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1972725/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1713997] Re: kexec-tools should not ask to handle reboots
Hm, don't you still need kexec-tools installed to reboot with kexec via systemd? I think this bug should be more about asking to reboot using kexec with systemd. The only problem is that for that to work, Ubuntu would need to implement https://systemd.io/BOOT_LOADER_SPECIFICATION/ (or move to boot using systemd-boot instead of grub2 - then the former is gained for free). -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to kexec-tools in Ubuntu. https://bugs.launchpad.net/bugs/1713997 Title: kexec-tools should not ask to handle reboots Status in kexec-tools package in Ubuntu: Confirmed Bug description: Reboots via kexec-tools are only supported on SysV init systems. With systemd the only supported init system by now, kexec-tools should no longer ask (during installation) if reboots should be handled by kexec-tools. There should be no user interaction required when installing the package. $ lsb_release -rd Description: Ubuntu Artful Aardvark (development branch) Release: 17.10 $ apt-cache policy kexec-tools kexec-tools: Installed: 1:2.0.15-0ubuntu1 Candidate: 1:2.0.15-0ubuntu1 Version table: *** 1:2.0.15-0ubuntu1 500 500 http://archive.ubuntu.com/ubuntu artful/main amd64 Packages 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kexec-tools/+bug/1713997/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1615734] Re: Multiple monitors broken
Version of my drivers is 430, it did the same on 390, using the prorietary Nvidia drivers -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-375 in Ubuntu. https://bugs.launchpad.net/bugs/1615734 Title: Multiple monitors broken Status in nvidia-graphics-drivers-361 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-367 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-375 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-384 package in Ubuntu: Confirmed Bug description: I have a Lenovo P50 with Nvidia Optimus (Quadro M1000M), installed with Ubuntu 16.04 and the recommended Nvidia drivers (361.42). I added two external monitors connected to DP sockets in the docking station. I would like to have display shift to those two monitors when the laptop is docked. One monitor has native resolution of 1680x1050 and the other is 1920x1080. The laptop native resolution is 1920x1080. Expected result: laptop monitor shut off, two external monitors running in native resolution, display shared on both monitors (not mirrored). Process: I configured the display using the "Displays" applet in the unity control center. However, pressing "Apply" when changing a specific display setting (such as resolution, location of screen relative to others, turning on/off), results in a long period of darkness, usually followed by display falling back to mirroring of all 3 monitors, using a similar-size screen (either low on all or high on all with the low-res monitor using panning). The applet remains frozen for some time, with the dialog "Is the display ok" open but unresponsive. Later I realized this is because there is another dialog of "Cannot set screen CRTCXXX" hidden under the two above windows, which needs to by ok-ed first. Extra: I also tried setting the display manually with 'xrandr', which lead to a similar result as above - with the "cannot set screen" dialog, and falling back to mirroring. This convinced me that the problem is probably with the nvidia driver and not the higher plumbing. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: nvidia-361 361.42-0ubuntu2 ProcVersionSignature: Ubuntu 4.4.0-34.53-generic 4.4.15 Uname: Linux 4.4.0-34-generic x86_64 NonfreeKernelModules: symap_custom_dkms_x86_64 nvidia_uvm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CurrentDesktop: Unity Date: Mon Aug 22 19:14:55 2016 InstallationDate: Installed on 2016-07-17 (36 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) SourcePackage: nvidia-graphics-drivers-361 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-361/+bug/1615734/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1615734] Re: Multiple monitors broken
Hm, I am on 18.04 on Thinkpad 530 and Mini Dock Plus Series 3 with three monitors and I have a very mild version of this problem. Only after suspend, the two monitors that are connected via the dock flicker (either show screen corruption or repeatedly blank in and blank out). The one connected to laptop's miniDP port works fine. However, I only need to issue xset dpms force standby to make them turn off and then move a mouse to make them turn on again. Another alternative is pressing alt+ctrl+F6 to go to tty6 and then alt+ctrl+F7 to go back to graphical interface. Still inconvenient though. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-375 in Ubuntu. https://bugs.launchpad.net/bugs/1615734 Title: Multiple monitors broken Status in nvidia-graphics-drivers-361 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-367 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-375 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-384 package in Ubuntu: Confirmed Bug description: I have a Lenovo P50 with Nvidia Optimus (Quadro M1000M), installed with Ubuntu 16.04 and the recommended Nvidia drivers (361.42). I added two external monitors connected to DP sockets in the docking station. I would like to have display shift to those two monitors when the laptop is docked. One monitor has native resolution of 1680x1050 and the other is 1920x1080. The laptop native resolution is 1920x1080. Expected result: laptop monitor shut off, two external monitors running in native resolution, display shared on both monitors (not mirrored). Process: I configured the display using the "Displays" applet in the unity control center. However, pressing "Apply" when changing a specific display setting (such as resolution, location of screen relative to others, turning on/off), results in a long period of darkness, usually followed by display falling back to mirroring of all 3 monitors, using a similar-size screen (either low on all or high on all with the low-res monitor using panning). The applet remains frozen for some time, with the dialog "Is the display ok" open but unresponsive. Later I realized this is because there is another dialog of "Cannot set screen CRTCXXX" hidden under the two above windows, which needs to by ok-ed first. Extra: I also tried setting the display manually with 'xrandr', which lead to a similar result as above - with the "cannot set screen" dialog, and falling back to mirroring. This convinced me that the problem is probably with the nvidia driver and not the higher plumbing. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: nvidia-361 361.42-0ubuntu2 ProcVersionSignature: Ubuntu 4.4.0-34.53-generic 4.4.15 Uname: Linux 4.4.0-34-generic x86_64 NonfreeKernelModules: symap_custom_dkms_x86_64 nvidia_uvm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CurrentDesktop: Unity Date: Mon Aug 22 19:14:55 2016 InstallationDate: Installed on 2016-07-17 (36 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) SourcePackage: nvidia-graphics-drivers-361 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-361/+bug/1615734/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
