[Desktop-packages] [Bug 1910709] Re: DKMS linux-headers-5.8.0-34-generic update brokes nvidia-340
I'll upload the groovy version to focal ** Changed in: nvidia-graphics-drivers-340 (Ubuntu Focal) Assignee: Alberto Milone (albertomilone) => Timo Aaltonen (tjaalton) ** Description changed: + [Impact] + nvidia-340 dkms fails to build against the current HWE kernel in focal, regressing the user experience. + + [Test case] + Install the update, check that the dkms builds and works. + + [Where things could go wrong] + The changes only add support for newer kernels so that the module can build, and it's identical to what's in groovy. In theory it could break the build against 5.4 but that's highly unlikely. + + + -- + Last linux kernel update "linux-headers-5.8.0-34-generic" broke nvidia-340 driver and Desktop access. In make log: [...] echo >&2; \ echo >&2 " ERROR: Kernel configuration is invalid."; \ echo >&2 " include/generated/autoconf.h or include/config/auto.conf are missing.";\ echo >&2 " Run 'make oldconfig && make prepare' on kernel src to fix it.";\ - echo >&2 ; + echo >&2 ; [...] Full DKMS log file attacked. - --- + --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-11-04 (64 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: Gigabyte Technology Co., Ltd. H81M-D3H NonfreeKernelModules: nvidia Package: linux (not installed) ProcEnviron: - TERM=xterm-256color - PATH=(custom, no user) - XDG_RUNTIME_DIR= - LANG=es_ES.UTF-8 - SHELL=/bin/bash + TERM=xterm-256color + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=es_ES.UTF-8 + SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-59-generic root=UUID=b0ed05d5-7921-451b-b62c-773b97eeca2f ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-59.65-generic 5.4.78 RelatedPackageVersions: - linux-restricted-modules-5.4.0-59-generic N/A - linux-backports-modules-5.4.0-59-generic N/A - linux-firmware1.187.7 + linux-restricted-modules-5.4.0-59-generic N/A + linux-backports-modules-5.4.0-59-generic N/A + linux-firmware1.187.7 RfKill: - 0: phy0: Wireless LAN - Soft blocked: no - Hard blocked: no + 0: phy0: Wireless LAN + Soft blocked: no + Hard blocked: no Tags: focal Uname: Linux 5.4.0-59-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: sudo WifiSyslog: - + _MarkForUpload: True dmi.bios.date: 01/20/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F2 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H81M-D3H dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF2:bd01/20/2014:svnGigabyteTechnologyCo.,Ltd.:pnH81M-D3H:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnH81M-D3H:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: H81M-D3H dmi.product.sku: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. - --- + --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-11-04 (64 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: Gigabyte Technology Co., Ltd. H81M-D3H NonfreeKernelModules: nvidia Package: linux (not installed) ProcEnviron: - TERM=xterm-256color - PATH=(custom, no user) - LANG=es_ES.UTF-8 - SHELL=/bin/bash + TERM=xterm-256color + PATH=(custom, no user) + LANG=es_ES.UTF-8 + SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-59-generic root=UUID=b0ed05d5-7921-451b-b62c-773b97eeca2f ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-59.65-generic 5.4.78 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.4.0-59-generic N/A - linux-backports-modules-5.4.0-59-generic N/A - linux-firmware1.187.7 + linux-restricted-modules-5.4.0-59-generic N/A + linux-backports-modules-5.4.0-59-generic N/A + linux-firmware1.187.7 RfKill: - 0: phy0: Wireless LAN - Soft blocked: no - Hard blocked: no + 0: phy0: Wireless LAN + Soft blocked: no + Hard blocked: no
[Desktop-packages] [Bug 1909463] Re: Libreoffice crashed when saving certain documents as docx, doc
Patch available, will be included in 7.0.5 - https://bugs.documentfoundation.org/show_bug.cgi?id=139580#c3 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1909463 Title: Libreoffice crashed when saving certain documents as docx, doc Status in libreoffice package in Ubuntu: New Bug description: Libreoffice crashed when saving certain documents as docx, doc. test.odt attached. Also tested with libreoffice 7.0.4 from ppa, issue present. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: libreoffice 1:6.4.6-0ubuntu0.20.04.1 ProcVersionSignature: Ubuntu 5.4.0-54.60-generic 5.4.65 Uname: Linux 5.4.0-54-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Dec 28 12:27:55 2020 SourcePackage: libreoffice UpgradeStatus: Upgraded to focal on 2020-05-08 (234 days ago) modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 mtime.conffile..etc.default.apport: 2018-04-04T09:25:22.888039 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1909463/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1911614] Re: Ubuntu 20.04 and 20.04.1 images use linux-generic-hwe-20.04 instead of linux-generic
Thank you for taking the time to report this bug and helping to make Ubuntu better. If you look at the Ubuntu 20.04 LTS (focal fossa) release notes you'll see https://wiki.ubuntu.com/FocalFossa/ReleaseNotes "Ubuntu Desktop flavour now always tracks HWE kernel (hardware enablement). It means that from 20.04.2 release Ubuntu Desktop will gain new major kernel versions every 6 months through to summer of 2022." You haven't indicated if you're talking Ubuntu Desktop, if so that was announced & is expected behavior (at least as I understand it). Please execute the following command only once, as it will automatically gather debugging information, in a terminal: apport-collect 1911614 When reporting bugs in the future please use apport by using 'ubuntu- bug' and the name of the package affected. You can learn more about this functionality at https://wiki.ubuntu.com/ReportingBugs. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1911614 Title: Ubuntu 20.04 and 20.04.1 images use linux-generic-hwe-20.04 instead of linux-generic Status in ubuntu-meta package in Ubuntu: New Bug description: Just as the title says, the 20.04 and 20.04.1 images use the HWE version of linux-generic resulting in upgrades to the 5.8 series kernel. This seems to effect Ubuntu only, or I should say I checked the Kubuntu, Ubuntu Mate, Xubuntu, and Lubuntu iso manifests which all correctly list linux-generic. Also HWE is not truly complete without the accompanying HWE Xstack. I checked all the documentation I could find and this was clearly not intentional. In fact the manifest for Ubuntu Focal Beta still used linux-generic, so this got messed up some time between April 3, 2020 and April 23, 2020. Here's just one example of the documentation for kernel support in Focal LTS: https://ubuntu.com/about/release-cycle#ubuntu-kernel-release-cycle Installations performed with 20.04 and 20.04.1 media were supposed to remain on the 5.4 series kernel throughout Focal's 5 year lifespan as had been the case since HWE was introduced. The first step in fixing this needs to be stopping fresh installs of Focal using the 20.04 and 20.04.1 media from immediately upgrading to the 5.8 series kernel. It might be a little tricky to revert users from 5.8 to 5.4, but there have been reports of breakage, particularly concerning Broadcom wifi drivers and some graphics problems. But the graphics problems could also be exacerbated by the lack of the matching HWE Xstack? At any rate it's a bug. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1911614/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1911614] [NEW] Ubuntu 20.04 and 20.04.1 images use linux-generic-hwe-20.04 instead of linux-generic
Public bug reported: Just as the title says, the 20.04 and 20.04.1 images use the HWE version of linux-generic resulting in upgrades to the 5.8 series kernel. This seems to effect Ubuntu only, or I should say I checked the Kubuntu, Ubuntu Mate, Xubuntu, and Lubuntu iso manifests which all correctly list linux-generic. Also HWE is not truly complete without the accompanying HWE Xstack. I checked all the documentation I could find and this was clearly not intentional. In fact the manifest for Ubuntu Focal Beta still used linux-generic, so this got messed up some time between April 3, 2020 and April 23, 2020. Here's just one example of the documentation for kernel support in Focal LTS: https://ubuntu.com/about/release-cycle#ubuntu-kernel-release-cycle Installations performed with 20.04 and 20.04.1 media were supposed to remain on the 5.4 series kernel throughout Focal's 5 year lifespan as had been the case since HWE was introduced. The first step in fixing this needs to be stopping fresh installs of Focal using the 20.04 and 20.04.1 media from immediately upgrading to the 5.8 series kernel. It might be a little tricky to revert users from 5.8 to 5.4, but there have been reports of breakage, particularly concerning Broadcom wifi drivers and some graphics problems. But the graphics problems could also be exacerbated by the lack of the matching HWE Xstack? At any rate it's a bug. ** Affects: ubuntu-meta (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1911614 Title: Ubuntu 20.04 and 20.04.1 images use linux-generic-hwe-20.04 instead of linux-generic Status in ubuntu-meta package in Ubuntu: New Bug description: Just as the title says, the 20.04 and 20.04.1 images use the HWE version of linux-generic resulting in upgrades to the 5.8 series kernel. This seems to effect Ubuntu only, or I should say I checked the Kubuntu, Ubuntu Mate, Xubuntu, and Lubuntu iso manifests which all correctly list linux-generic. Also HWE is not truly complete without the accompanying HWE Xstack. I checked all the documentation I could find and this was clearly not intentional. In fact the manifest for Ubuntu Focal Beta still used linux-generic, so this got messed up some time between April 3, 2020 and April 23, 2020. Here's just one example of the documentation for kernel support in Focal LTS: https://ubuntu.com/about/release-cycle#ubuntu-kernel-release-cycle Installations performed with 20.04 and 20.04.1 media were supposed to remain on the 5.4 series kernel throughout Focal's 5 year lifespan as had been the case since HWE was introduced. The first step in fixing this needs to be stopping fresh installs of Focal using the 20.04 and 20.04.1 media from immediately upgrading to the 5.8 series kernel. It might be a little tricky to revert users from 5.8 to 5.4, but there have been reports of breakage, particularly concerning Broadcom wifi drivers and some graphics problems. But the graphics problems could also be exacerbated by the lack of the matching HWE Xstack? At any rate it's a bug. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1911614/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1910709] Re: DKMS linux-headers-5.8.0-34-generic update brokes nvidia-340
@ihler [and same comment may apply to others...] How have you ended up with -hwe kernel getting installed anyhow? Default behaviour of particular install iso image? Because clicked some option somewhere? Some sort of 'unintended/accident' and only later found the consequence of k5.8 auto-installing? Using a non-standard ubuntu install image? This situation will need investigating as we don't want similar mess occurring in another 6months when following HWE kernel goes into 18.04.3 and so-on!... I'd prefer that 20.04.2 provided users option to install with kernel 5.4LTS and stay there for older hardware. I note, ubuntu-derivative LinuxMint have decided to do this and not by-default follow the HWE chain, but providing an initial -edge image with kernel 5.8 for those who really need it. May be better that those on older hardware move back to LTS 5.4 kernel and not keep following HWE? May be that legacy drivers can still be bought forward to further HWE kernels all the way to the final HWE series...? We will see, I guess, but I'd like to see these breakages/messes avoided ongoing. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-340 in Ubuntu. https://bugs.launchpad.net/bugs/1910709 Title: DKMS linux-headers-5.8.0-34-generic update brokes nvidia-340 Status in nvidia-graphics-drivers-340 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-340 source package in Focal: Confirmed Bug description: Last linux kernel update "linux-headers-5.8.0-34-generic" broke nvidia-340 driver and Desktop access. In make log: [...] echo >&2; \ echo >&2 " ERROR: Kernel configuration is invalid."; \ echo >&2 " include/generated/autoconf.h or include/config/auto.conf are missing.";\ echo >&2 " Run 'make oldconfig && make prepare' on kernel src to fix it.";\ echo >&2 ; [...] Full DKMS log file attacked. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-11-04 (64 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: Gigabyte Technology Co., Ltd. H81M-D3H NonfreeKernelModules: nvidia Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=es_ES.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-59-generic root=UUID=b0ed05d5-7921-451b-b62c-773b97eeca2f ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-59.65-generic 5.4.78 RelatedPackageVersions: linux-restricted-modules-5.4.0-59-generic N/A linux-backports-modules-5.4.0-59-generic N/A linux-firmware1.187.7 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: focal Uname: Linux 5.4.0-59-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: sudo WifiSyslog: _MarkForUpload: True dmi.bios.date: 01/20/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F2 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H81M-D3H dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF2:bd01/20/2014:svnGigabyteTechnologyCo.,Ltd.:pnH81M-D3H:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnH81M-D3H:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: H81M-D3H dmi.product.sku: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-11-04 (64 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: Gigabyte Technology Co., Ltd. H81M-D3H NonfreeKernelModules: nvidia Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=es_ES.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-59-generic root=UUID=b0ed05d5-7921-451b-b62c-773b97eeca2f ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-59.65-generic 5.4.78 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-res
[Desktop-packages] [Bug 1908167] Re: [SRU] pulseaudio: the headset-mic or heapdhone-mic could not be selected automatically if there is no internal mic
@Robie, The Hirsute doesn't have this regression since I cherry-picked the upstream patch to Hirsute, all needed patches are in the Hirsute already. But for groovy and focal, the patch can't be applied to them without changing, so I backported the patch to groovy and focal, the regression is introduced when backporting. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1908167 Title: [SRU] pulseaudio: the headset-mic or heapdhone-mic could not be selected automatically if there is no internal mic Status in HWE Next: New Status in OEM Priority Project: New Status in pulseaudio package in Ubuntu: Fix Released Status in pulseaudio source package in Focal: Fix Committed Status in pulseaudio source package in Groovy: Fix Committed Status in pulseaudio source package in Hirsute: Fix Released Bug description: [Impact] On the Dell AIO machines, there is no internal mic, after plugging a headset, users expect the headset-mic or headphone-mic could be selected automatically. But with the current rule, the headset-mic/headphone-mic will not be selected automatically and even users manually select them, they will not show up in the gnome sound setting, and users could not record sound by headset-mic/headphone-mic. [Fix] backport a patch from pulseaudio mergerequest, the patch is going to be merged to pulseaudio 14.1. This patch could be backported to hirsute without any change, but need to be changed if backport it to groovy and focal. [Test] With the old pulseaudio (prior to 1:13.99.1-1ubuntu3.10), plugging in a headset to the problematic Dell AIO machine will not automatically select headset-mic/headphone-mic, and they also do not show up in Gnome sound settings, leading to failure to record any sound. With the new proposed package, on those Dell AIO, plug a headset, open the gnome sound setting, the headset-mic is selected automatically, use the headset-mic to record the sound, the sound could be recorded and the sound quality is good. [Where problems could occur] This patch could change the policy of audio device switching, it will not affect all audio devices, but only the devices which has AVAIL_UNKNOWN available status, that means it has possibility to introduce the regression on headphone-mic ,headset-mic, internal mic and internal speaker's switching since they all has AVAIL_UNKNOWN status. For example, after unpluging the headset, the input device will not switch to internal mic automatically or after unplug the headphone, the output device will not switch to internal speaker automatically. But this possibility is very low, we have tested the patch on many Dell and Lenovo machines, all worked well. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1908167/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1895643] Re: Backport Thunderbird 78 to 20.04 LTS and 18.04 LTS
@osomon: I'd also kindly ask for more information on what's blocking this update. Thunderbird version 68 - which is the standard mail solution shipping with Ubuntu 20.04 right now - is over 6.5 months old. The upstream version got numerous security fixes over the last half year. Doesn't feel good to have to rely on software for communications that stopped getting updates for such a long time. I really don't want to be pushy, because I know Ubuntu is free software, but I'd like to express my worries that this for many users important question (current versions of browser and mail) doesn't have the focus it should have. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to thunderbird in Ubuntu. https://bugs.launchpad.net/bugs/1895643 Title: Backport Thunderbird 78 to 20.04 LTS and 18.04 LTS Status in thunderbird package in Ubuntu: Fix Released Status in thunderbird source package in Bionic: Triaged Status in thunderbird source package in Focal: Fix Committed Status in thunderbird source package in Groovy: Fix Released Bug description: Upstream Thunderbird version 78.2.2 should be a candidate for backporting to stable Ubuntu releases. I've successfully built 78.2.1 against both with forcing nodejs version (20.04, 18.04) and disabling AV1 support due to too old nasm (18.04). Attaching debdiffs here. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1895643/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1910709] Re: DKMS linux-headers-5.8.0-34-generic update brokes nvidia-340
@ubuntu-iremonger You, sir, are a gentleman and a scholar. Your deb file resolves the issue for me. Thanks for putting in all the effort! -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-340 in Ubuntu. https://bugs.launchpad.net/bugs/1910709 Title: DKMS linux-headers-5.8.0-34-generic update brokes nvidia-340 Status in nvidia-graphics-drivers-340 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-340 source package in Focal: Confirmed Bug description: Last linux kernel update "linux-headers-5.8.0-34-generic" broke nvidia-340 driver and Desktop access. In make log: [...] echo >&2; \ echo >&2 " ERROR: Kernel configuration is invalid."; \ echo >&2 " include/generated/autoconf.h or include/config/auto.conf are missing.";\ echo >&2 " Run 'make oldconfig && make prepare' on kernel src to fix it.";\ echo >&2 ; [...] Full DKMS log file attacked. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-11-04 (64 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: Gigabyte Technology Co., Ltd. H81M-D3H NonfreeKernelModules: nvidia Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=es_ES.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-59-generic root=UUID=b0ed05d5-7921-451b-b62c-773b97eeca2f ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-59.65-generic 5.4.78 RelatedPackageVersions: linux-restricted-modules-5.4.0-59-generic N/A linux-backports-modules-5.4.0-59-generic N/A linux-firmware1.187.7 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: focal Uname: Linux 5.4.0-59-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: sudo WifiSyslog: _MarkForUpload: True dmi.bios.date: 01/20/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F2 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H81M-D3H dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF2:bd01/20/2014:svnGigabyteTechnologyCo.,Ltd.:pnH81M-D3H:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnH81M-D3H:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: H81M-D3H dmi.product.sku: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-11-04 (64 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: Gigabyte Technology Co., Ltd. H81M-D3H NonfreeKernelModules: nvidia Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=es_ES.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-59-generic root=UUID=b0ed05d5-7921-451b-b62c-773b97eeca2f ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-59.65-generic 5.4.78 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.4.0-59-generic N/A linux-backports-modules-5.4.0-59-generic N/A linux-firmware1.187.7 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: focal Uname: Linux 5.4.0-59-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 01/20/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F2 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H81M-D3H dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF2:bd01/20/2014:svnGigabyteTechnologyCo.,Ltd.:pnH81M-D3H:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnH81M-D3H:r
[Desktop-packages] [Bug 1910709] Re: DKMS linux-headers-5.8.0-34-generic update brokes nvidia-340
Also: For those stuck without Nvidia working on k5.8 -- simple short- term thing to do, is hold down SHIFT at system startup (exact timing depends upon system) to get to the GRUB boot-menu, and then select "Advanced options for Ubuntu" (or thereabouts) submenu and then you should be able to boot from the latest 5.4 kernel you should still have installed. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-340 in Ubuntu. https://bugs.launchpad.net/bugs/1910709 Title: DKMS linux-headers-5.8.0-34-generic update brokes nvidia-340 Status in nvidia-graphics-drivers-340 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-340 source package in Focal: Confirmed Bug description: Last linux kernel update "linux-headers-5.8.0-34-generic" broke nvidia-340 driver and Desktop access. In make log: [...] echo >&2; \ echo >&2 " ERROR: Kernel configuration is invalid."; \ echo >&2 " include/generated/autoconf.h or include/config/auto.conf are missing.";\ echo >&2 " Run 'make oldconfig && make prepare' on kernel src to fix it.";\ echo >&2 ; [...] Full DKMS log file attacked. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-11-04 (64 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: Gigabyte Technology Co., Ltd. H81M-D3H NonfreeKernelModules: nvidia Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=es_ES.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-59-generic root=UUID=b0ed05d5-7921-451b-b62c-773b97eeca2f ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-59.65-generic 5.4.78 RelatedPackageVersions: linux-restricted-modules-5.4.0-59-generic N/A linux-backports-modules-5.4.0-59-generic N/A linux-firmware1.187.7 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: focal Uname: Linux 5.4.0-59-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: sudo WifiSyslog: _MarkForUpload: True dmi.bios.date: 01/20/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F2 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H81M-D3H dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF2:bd01/20/2014:svnGigabyteTechnologyCo.,Ltd.:pnH81M-D3H:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnH81M-D3H:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: H81M-D3H dmi.product.sku: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-11-04 (64 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: Gigabyte Technology Co., Ltd. H81M-D3H NonfreeKernelModules: nvidia Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=es_ES.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-59-generic root=UUID=b0ed05d5-7921-451b-b62c-773b97eeca2f ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-59.65-generic 5.4.78 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.4.0-59-generic N/A linux-backports-modules-5.4.0-59-generic N/A linux-firmware1.187.7 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: focal Uname: Linux 5.4.0-59-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 01/20/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F2 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H81M-D3H dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
[Desktop-packages] [Bug 1909941] Re: xdg-email changes break simple-scan email functionality
Have verified that on 16.04, simple-scan to email now works again following the reversion of the original fix. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xdg-utils in Ubuntu. https://bugs.launchpad.net/bugs/1909941 Title: xdg-email changes break simple-scan email functionality Status in xdg-utils package in Ubuntu: Confirmed Bug description: Observed on 16.04 to 20.04 xdg-email no longer actions "-attach filename" arguments when running thunderbird following recent security fixes to protect against malicious use from browser ( https://security-tracker.debian.org/tracker/CVE-2020-27748 and https://ubuntu.com/security/CVE-2020-27748 ) This breaks simple-scan "send by email" functionality and other applications too. https://gitlab.gnome.org/GNOME/simple-scan/-/issues/216 https://forums.linuxmint.com/viewtopic.php?f=208&t=336053 https://gitlab.freedesktop.org/xdg/xdg-utils/-/merge_requests/28 (see comments) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xdg-utils/+bug/1909941/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1910709] Re: DKMS linux-headers-5.8.0-34-generic update brokes nvidia-340
For what its' worth, I built the nvidia-340_340.108-0ubuntu5 package (includes patches to go up to kernel 5.9 apparently) on Focal20.04 -- just using the groovy-updates version and renumbering it back to 20.04.0test0 instead of a 20.10. version. The full source and set of debs is here:- https://www.iremonger.me.uk/noidx/nvidia-340-focal/ You only seem to need the 'nvidia-340' deb [ https://www.iremonger.me.uk/noidx/nvidia-340-focal/nvidia-340_340.108-0ubuntu5.20.04.0test0_amd64.deb ] for basic usage of the driver, but the full set of debs and source package is provided above. This appears to solve the build and install problem on 20.04 based system, with ubuntu kernel 5.8 series installed. By all means use and test this if you like, I hope ubuntu-devs will put the same or equivalent into focal-proposed and focal-updates very soon!. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-340 in Ubuntu. https://bugs.launchpad.net/bugs/1910709 Title: DKMS linux-headers-5.8.0-34-generic update brokes nvidia-340 Status in nvidia-graphics-drivers-340 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-340 source package in Focal: Confirmed Bug description: Last linux kernel update "linux-headers-5.8.0-34-generic" broke nvidia-340 driver and Desktop access. In make log: [...] echo >&2; \ echo >&2 " ERROR: Kernel configuration is invalid."; \ echo >&2 " include/generated/autoconf.h or include/config/auto.conf are missing.";\ echo >&2 " Run 'make oldconfig && make prepare' on kernel src to fix it.";\ echo >&2 ; [...] Full DKMS log file attacked. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-11-04 (64 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: Gigabyte Technology Co., Ltd. H81M-D3H NonfreeKernelModules: nvidia Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=es_ES.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-59-generic root=UUID=b0ed05d5-7921-451b-b62c-773b97eeca2f ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-59.65-generic 5.4.78 RelatedPackageVersions: linux-restricted-modules-5.4.0-59-generic N/A linux-backports-modules-5.4.0-59-generic N/A linux-firmware1.187.7 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: focal Uname: Linux 5.4.0-59-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: sudo WifiSyslog: _MarkForUpload: True dmi.bios.date: 01/20/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F2 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H81M-D3H dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF2:bd01/20/2014:svnGigabyteTechnologyCo.,Ltd.:pnH81M-D3H:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnH81M-D3H:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: H81M-D3H dmi.product.sku: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-11-04 (64 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: Gigabyte Technology Co., Ltd. H81M-D3H NonfreeKernelModules: nvidia Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=es_ES.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-59-generic root=UUID=b0ed05d5-7921-451b-b62c-773b97eeca2f ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-59.65-generic 5.4.78 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.4.0-59-generic N/A linux-backports-modules-5.4.0-59-generic N/A linux-firmware1.187.7 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: focal Uname: Linux 5
[Desktop-packages] [Bug 1910709] Re: DKMS linux-headers-5.8.0-34-generic update brokes nvidia-340
similar dpkg versions as everyone else (e.g., linux- headers-5.8.0-36-generic) lspci: NVIDIA Corporation GT200 [GeForce GTX 295] I can't get nouveau to provide graphics either, so I am currently stuck with text only. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-340 in Ubuntu. https://bugs.launchpad.net/bugs/1910709 Title: DKMS linux-headers-5.8.0-34-generic update brokes nvidia-340 Status in nvidia-graphics-drivers-340 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-340 source package in Focal: Confirmed Bug description: Last linux kernel update "linux-headers-5.8.0-34-generic" broke nvidia-340 driver and Desktop access. In make log: [...] echo >&2; \ echo >&2 " ERROR: Kernel configuration is invalid."; \ echo >&2 " include/generated/autoconf.h or include/config/auto.conf are missing.";\ echo >&2 " Run 'make oldconfig && make prepare' on kernel src to fix it.";\ echo >&2 ; [...] Full DKMS log file attacked. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-11-04 (64 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: Gigabyte Technology Co., Ltd. H81M-D3H NonfreeKernelModules: nvidia Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=es_ES.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-59-generic root=UUID=b0ed05d5-7921-451b-b62c-773b97eeca2f ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-59.65-generic 5.4.78 RelatedPackageVersions: linux-restricted-modules-5.4.0-59-generic N/A linux-backports-modules-5.4.0-59-generic N/A linux-firmware1.187.7 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: focal Uname: Linux 5.4.0-59-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: sudo WifiSyslog: _MarkForUpload: True dmi.bios.date: 01/20/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F2 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H81M-D3H dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF2:bd01/20/2014:svnGigabyteTechnologyCo.,Ltd.:pnH81M-D3H:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnH81M-D3H:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: H81M-D3H dmi.product.sku: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-11-04 (64 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: Gigabyte Technology Co., Ltd. H81M-D3H NonfreeKernelModules: nvidia Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=es_ES.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-59-generic root=UUID=b0ed05d5-7921-451b-b62c-773b97eeca2f ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-59.65-generic 5.4.78 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.4.0-59-generic N/A linux-backports-modules-5.4.0-59-generic N/A linux-firmware1.187.7 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: focal Uname: Linux 5.4.0-59-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 01/20/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F2 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H81M-D3H dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF2:bd01/20/2014:svnGigabyteTechnologyCo.,Lt
[Desktop-packages] [Bug 1873052] Re: Showing two cursors after login
Marco's workaround in #7 works for me. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1873052 Title: Showing two cursors after login Status in gnome-shell package in Ubuntu: Confirmed Status in linux package in Ubuntu: Fix Released Status in mutter package in Ubuntu: Confirmed Status in xorg-server package in Ubuntu: In Progress Status in gnome-shell source package in Focal: Confirmed Status in linux source package in Focal: Confirmed Status in mutter source package in Focal: Confirmed Status in xorg-server source package in Focal: Confirmed Bug description: Showing two cursors after login to ubuntu-desktop. One cursor moves and is scaled, and one is stationary mid screen and not scaled. The moving cursor does not appear on screenshots, making it difficult to upload a screenshot. Previously reported: https://gitlab.gnome.org/GNOME/mutter/issues/904 https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1827428 Package: mutter 3.36.1-3ubuntu1 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.1-4ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu26 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Apr 15 20:06:53 2020 DisplayManager: gdm3 RelatedPackageVersions: mutter-common 3.36.1-3ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to focal on 2020-03-31 (15 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1873052/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1873052] Re: Showing two cursors after login
Happens to me in up to date GG using amdgpu for xorg session with fractional scaling. The mouse pointer in gdm gets stuck at the beginning of the session. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1873052 Title: Showing two cursors after login Status in gnome-shell package in Ubuntu: Confirmed Status in linux package in Ubuntu: Fix Released Status in mutter package in Ubuntu: Confirmed Status in xorg-server package in Ubuntu: In Progress Status in gnome-shell source package in Focal: Confirmed Status in linux source package in Focal: Confirmed Status in mutter source package in Focal: Confirmed Status in xorg-server source package in Focal: Confirmed Bug description: Showing two cursors after login to ubuntu-desktop. One cursor moves and is scaled, and one is stationary mid screen and not scaled. The moving cursor does not appear on screenshots, making it difficult to upload a screenshot. Previously reported: https://gitlab.gnome.org/GNOME/mutter/issues/904 https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1827428 Package: mutter 3.36.1-3ubuntu1 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.1-4ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu26 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Apr 15 20:06:53 2020 DisplayManager: gdm3 RelatedPackageVersions: mutter-common 3.36.1-3ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to focal on 2020-03-31 (15 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1873052/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1910598] Re: Ejecting a Blanc CD/DVD/BluRay-R disk writes to it.
Here it is ** Attachment added: "journalctl.log" https://bugs.launchpad.net/ubuntu/+source/caja/+bug/1910598/+attachment/5452757/+files/journalctl.log -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to udisks2 in Ubuntu. https://bugs.launchpad.net/bugs/1910598 Title: Ejecting a Blanc CD/DVD/BluRay-R disk writes to it. Status in caja package in Ubuntu: New Status in udisks2 package in Ubuntu: Incomplete Bug description: I used the "eject" contextual menu on the icon of a blank Bluray-R on the caja desktop, and I got a message saying that I need to wait for data to be written on the disc before being able to remove it safely (same message as when trying to eject an usb stick, when some data syncing is left to be done). Afterwards, when I tried to burn data to it, the app (k3b) told that the disc was not empty thus not writeable. This bug cost me a brand new Bluray-R M-Disc of 100GB, which is a quite pricey medium. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: caja 1.20.2-4ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-129.132-generic 4.15.18 Uname: Linux 4.15.0-129-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.21 Architecture: amd64 CurrentDesktop: MATE Date: Thu Jan 7 22:42:25 2021 SourcePackage: caja UpgradeStatus: Upgraded to bionic on 2019-02-16 (691 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/caja/+bug/1910598/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1911236] Re: emacs FTBFS on s390x because of a failing unit test
** Summary changed:
- emacs 27.1 FTBFS in hirsute on s390x because of a failing unit test
+ emacs FTBFS on s390x because of a failing unit test
** Also affects: emacs (Ubuntu Groovy)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to emacs in Ubuntu.
https://bugs.launchpad.net/bugs/1911236
Title:
emacs FTBFS on s390x because of a failing unit test
Status in emacs package in Ubuntu:
New
Status in emacs source package in Groovy:
New
Bug description:
As a follow up to bug #1911209, the following test is failing reliably
on s390x only:
Running 6 tests (2021-01-12 15:32:18+, selector `(not (or (tag
:expensive-test) (tag :unstable)))')
passed 1/6 lcms-ciecam02-gold (0.000133 sec)
Test lcms-cri-cam02-ucs backtrace:
signal(ert-test-failed (((should (eql 0.0 (lcms-cam02-ucs '(0.5 0.5
ert-fail(((should (eql 0.0 (lcms-cam02-ucs '(0.5 0.5 0.5) '(0.5 0.5
#f(compiled-function () #)()
ert--run-test-internal(#s(ert--test-execution-info :test #s(ert-test
ert-run-test(#s(ert-test :name lcms-cri-cam02-ucs :documentation "Te
ert-run-or-rerun-test(#s(ert--stats :selector (not (or (tag :expensi
ert-run-tests((not (or (tag :expensive-test) (tag :unstable))) #f(co
ert-run-tests-batch((not (or (tag :expensive-test) (tag :unstable)))
ert-run-tests-batch-and-exit((not (or (tag :expensive-test) (tag :un
eval((ert-run-tests-batch-and-exit '(not (or (tag :expensive-test) (
command-line-1(("-L" ":/<>/emacs-27.1+1/debian/build
command-line()
normal-top-level()
Test lcms-cri-cam02-ucs condition:
(ert-test-failed
((should
(eql 0.0
(lcms-cam02-ucs ... ...)))
:form
(eql 0.0 3.4662020221023775e-16)
:value nil))
FAILED 2/6 lcms-cri-cam02-ucs (0.000129 sec)
passed 3/6 lcms-dE-cam02-ucs-silver (0.80 sec)
passed 4/6 lcms-jmh->cam02-ucs-silver (0.53 sec)
passed 5/6 lcms-roundtrip (0.68 sec)
passed 6/6 lcms-whitepoint (0.56 sec)
Ran 6 tests, 5 results as expected, 1 unexpected (2021-01-12
15:32:18+, 0.088409 sec)
1 unexpected results:
FAILED lcms-cri-cam02-ucs
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/emacs/+bug/1911236/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1410618] Re: MacBook Air 6, 2 TRRS Headset Mic Not Working
Unfortunately I was never able to solve this. It appears the Windows issue (referenced above) remains as well. Maybe an examination of the Apple/OSX driver (if that's even possible) would lead to a solution here. As a work-around I purchased a small USB sound card and plugged into that. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1410618 Title: MacBook Air 6,2 TRRS Headset Mic Not Working Status in alsa-driver package in Ubuntu: Confirmed Bug description: Hello, I'm running Ubuntu Gnome 14.04 on a new MacBookAir6,2 with the Cirrus Logic CS4208 and would love to get the microphone part of the TRRS connector working. Mac OS picks up and utilizes the TRRS headset mic without issue so I know the hardware is a go. With the headset plugged in, running sudo hdajacksensetest -a results in: Pin 0x05 ( Digital Out, HDMI): present = No Pin 0x06 ( Digital Out, HDMI): present = No Pin 0x07 ( Digital Out, HDMI): present = No AlsaInfo output here: http://www.alsa-project.org/db/?f=cabc8cab44d308c8a3898c66d48d9be4fc5ccf83 I opened up hdajackretask to find four pins: Green Headphone Pin ID: 0x10 Headphone Internal Speaker Pin ID: 0x12 Internal speaker Pink Mic Pin ID: 0x18 Not connected Internal Mic Pin ID: 0x1c Internal mic Unplugging and replugging the headset changes the Output device in sound settings from Headphones to Speakers so that works, but nothing in the input tab ever changes. It always lists two devices: Internal Microphone and Microphone. Both of these seem to actually be the internal microphone in the mac - either works without the headset connected at all. So I'm not really sure how to proceed from here, but I'd be happy to run whatever diagnostic tests might prove useful and/or even contribute code toward a fix - but I just have no idea where to start. Is it as simple as just finding the right pin and telling the system to use it as a microphone? Similar bug report here: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/950494 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1410618/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1909941] Re: xdg-email changes break simple-scan email functionality
@dikiy-evrej I don't think that the recent change was in Thunderbird. The recent change here was to drop the attach= parameter from the mailto URL passed to Thunderbird, so that if you click a malicious mailto link in e.g. Chrome, it can't trick you into sending arbitrary files. Problem was that xdg-email parses its command line arguments - supplied by e.g. simple-scan - and converts them to a mailto URL with attach= parameter - which it then drops before calling TB. My hack in the simple-scan bug above is to only drop the attach parameter if the caller is Chrome or Chromium as those are the browsers used in my environment, but a better fix is required... -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xdg-utils in Ubuntu. https://bugs.launchpad.net/bugs/1909941 Title: xdg-email changes break simple-scan email functionality Status in xdg-utils package in Ubuntu: Confirmed Bug description: Observed on 16.04 to 20.04 xdg-email no longer actions "-attach filename" arguments when running thunderbird following recent security fixes to protect against malicious use from browser ( https://security-tracker.debian.org/tracker/CVE-2020-27748 and https://ubuntu.com/security/CVE-2020-27748 ) This breaks simple-scan "send by email" functionality and other applications too. https://gitlab.gnome.org/GNOME/simple-scan/-/issues/216 https://forums.linuxmint.com/viewtopic.php?f=208&t=336053 https://gitlab.freedesktop.org/xdg/xdg-utils/-/merge_requests/28 (see comments) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xdg-utils/+bug/1909941/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1909941] Re: xdg-email changes break simple-scan email functionality
seems, that support of attach was removed from thunderbird and claws- mail of security reasons. So xdg-email needs to change the command line to invoke an e-mail-Program -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xdg-utils in Ubuntu. https://bugs.launchpad.net/bugs/1909941 Title: xdg-email changes break simple-scan email functionality Status in xdg-utils package in Ubuntu: Confirmed Bug description: Observed on 16.04 to 20.04 xdg-email no longer actions "-attach filename" arguments when running thunderbird following recent security fixes to protect against malicious use from browser ( https://security-tracker.debian.org/tracker/CVE-2020-27748 and https://ubuntu.com/security/CVE-2020-27748 ) This breaks simple-scan "send by email" functionality and other applications too. https://gitlab.gnome.org/GNOME/simple-scan/-/issues/216 https://forums.linuxmint.com/viewtopic.php?f=208&t=336053 https://gitlab.freedesktop.org/xdg/xdg-utils/-/merge_requests/28 (see comments) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xdg-utils/+bug/1909941/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1909941] Re: xdg-email changes break simple-scan email functionality
I figured out, that claws-mail cant handle the command claws-mail --compose "mailto:?attach=/home/dik/tmp/file.key"; -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xdg-utils in Ubuntu. https://bugs.launchpad.net/bugs/1909941 Title: xdg-email changes break simple-scan email functionality Status in xdg-utils package in Ubuntu: Confirmed Bug description: Observed on 16.04 to 20.04 xdg-email no longer actions "-attach filename" arguments when running thunderbird following recent security fixes to protect against malicious use from browser ( https://security-tracker.debian.org/tracker/CVE-2020-27748 and https://ubuntu.com/security/CVE-2020-27748 ) This breaks simple-scan "send by email" functionality and other applications too. https://gitlab.gnome.org/GNOME/simple-scan/-/issues/216 https://forums.linuxmint.com/viewtopic.php?f=208&t=336053 https://gitlab.freedesktop.org/xdg/xdg-utils/-/merge_requests/28 (see comments) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xdg-utils/+bug/1909941/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1909941] Re: xdg-email changes break simple-scan email functionality
XDG_CURRENT_DESKTOP is set to i3, But under MATE I have this problem too. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xdg-utils in Ubuntu. https://bugs.launchpad.net/bugs/1909941 Title: xdg-email changes break simple-scan email functionality Status in xdg-utils package in Ubuntu: Confirmed Bug description: Observed on 16.04 to 20.04 xdg-email no longer actions "-attach filename" arguments when running thunderbird following recent security fixes to protect against malicious use from browser ( https://security-tracker.debian.org/tracker/CVE-2020-27748 and https://ubuntu.com/security/CVE-2020-27748 ) This breaks simple-scan "send by email" functionality and other applications too. https://gitlab.gnome.org/GNOME/simple-scan/-/issues/216 https://forums.linuxmint.com/viewtopic.php?f=208&t=336053 https://gitlab.freedesktop.org/xdg/xdg-utils/-/merge_requests/28 (see comments) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xdg-utils/+bug/1909941/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1908167] Re: [SRU] pulseaudio: the headset-mic or heapdhone-mic could not be selected automatically if there is no internal mic
I asked on IRC for confirmation that the regression fix has landed in Hirsute. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1908167 Title: [SRU] pulseaudio: the headset-mic or heapdhone-mic could not be selected automatically if there is no internal mic Status in HWE Next: New Status in OEM Priority Project: New Status in pulseaudio package in Ubuntu: Fix Released Status in pulseaudio source package in Focal: Fix Committed Status in pulseaudio source package in Groovy: Fix Committed Status in pulseaudio source package in Hirsute: Fix Released Bug description: [Impact] On the Dell AIO machines, there is no internal mic, after plugging a headset, users expect the headset-mic or headphone-mic could be selected automatically. But with the current rule, the headset-mic/headphone-mic will not be selected automatically and even users manually select them, they will not show up in the gnome sound setting, and users could not record sound by headset-mic/headphone-mic. [Fix] backport a patch from pulseaudio mergerequest, the patch is going to be merged to pulseaudio 14.1. This patch could be backported to hirsute without any change, but need to be changed if backport it to groovy and focal. [Test] With the old pulseaudio (prior to 1:13.99.1-1ubuntu3.10), plugging in a headset to the problematic Dell AIO machine will not automatically select headset-mic/headphone-mic, and they also do not show up in Gnome sound settings, leading to failure to record any sound. With the new proposed package, on those Dell AIO, plug a headset, open the gnome sound setting, the headset-mic is selected automatically, use the headset-mic to record the sound, the sound could be recorded and the sound quality is good. [Where problems could occur] This patch could change the policy of audio device switching, it will not affect all audio devices, but only the devices which has AVAIL_UNKNOWN available status, that means it has possibility to introduce the regression on headphone-mic ,headset-mic, internal mic and internal speaker's switching since they all has AVAIL_UNKNOWN status. For example, after unpluging the headset, the input device will not switch to internal mic automatically or after unplug the headphone, the output device will not switch to internal speaker automatically. But this possibility is very low, we have tested the patch on many Dell and Lenovo machines, all worked well. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1908167/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1725618] Re: pulseaudio crashed with SIGABRT in pa_mainloop_dispatch()
*** This bug is a duplicate of bug 1366819 *** https://bugs.launchpad.net/bugs/1366819 Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: pulseaudio (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1725618 Title: pulseaudio crashed with SIGABRT in pa_mainloop_dispatch() Status in pulseaudio package in Ubuntu: Confirmed Bug description: Watching youtube videos in firefox triggers this error and either the whole browser or just the one tab to crash. Everything works fine in chromium. Clicking through the "encountered an error" dialogue created this bug ProblemType: Crash DistroRelease: Ubuntu 17.10 Package: pulseaudio 1:10.0-2ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-16.19-lowlatency 4.13.4 Uname: Linux 4.13.0-16-lowlatency x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC1D0p: geoff 2344 F...m pulseaudio /dev/snd/controlC1: geoff 2344 F pulseaudio /dev/snd/controlC0: geoff 2344 F pulseaudio CrashCounter: 1 CurrentDesktop: XFCE Date: Sat Oct 21 20:40:18 2017 EcryptfsInUse: Yes ExecutablePath: /usr/bin/pulseaudio InstallationDate: Installed on 2014-09-23 (1123 days ago) InstallationMedia: Xubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.2) ProcCmdline: /usr/bin/pulseaudio --start --log-target=syslog Signal: 6 SourcePackage: pulseaudio StacktraceTop: ?? () from /usr/lib/pulse-10.0/modules/module-stream-restore.so ?? () from /usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecore-10.0.so pa_mainloop_dispatch () from /usr/lib/x86_64-linux-gnu/libpulse.so.0 pa_mainloop_iterate () from /usr/lib/x86_64-linux-gnu/libpulse.so.0 pa_mainloop_run () from /usr/lib/x86_64-linux-gnu/libpulse.so.0 Title: pulseaudio crashed with SIGABRT in pa_mainloop_dispatch() UpgradeStatus: Upgraded to artful on 2017-10-21 (0 days ago) UserGroups: adm cdrom dialout dip docker lpadmin plugdev sambashare sudo vboxusers www-data dmi.bios.date: 07/17/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: G750JS.208 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: G750JS dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrG750JS.208:bd07/17/2014:svnASUSTeKCOMPUTERINC.:pnG750JS:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnG750JS:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: G dmi.product.name: G750JS dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1725618/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1910709] Re: DKMS linux-headers-5.8.0-34-generic update brokes nvidia-340
Lenovo T510 on Ubuntu 20.04.1 LTS, dpkg and lspci output. ** Attachment added: "dpkg and lspci output" https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/1910709/+attachment/5452726/+files/dpkg_lspci.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-340 in Ubuntu. https://bugs.launchpad.net/bugs/1910709 Title: DKMS linux-headers-5.8.0-34-generic update brokes nvidia-340 Status in nvidia-graphics-drivers-340 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-340 source package in Focal: Confirmed Bug description: Last linux kernel update "linux-headers-5.8.0-34-generic" broke nvidia-340 driver and Desktop access. In make log: [...] echo >&2; \ echo >&2 " ERROR: Kernel configuration is invalid."; \ echo >&2 " include/generated/autoconf.h or include/config/auto.conf are missing.";\ echo >&2 " Run 'make oldconfig && make prepare' on kernel src to fix it.";\ echo >&2 ; [...] Full DKMS log file attacked. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-11-04 (64 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: Gigabyte Technology Co., Ltd. H81M-D3H NonfreeKernelModules: nvidia Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=es_ES.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-59-generic root=UUID=b0ed05d5-7921-451b-b62c-773b97eeca2f ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-59.65-generic 5.4.78 RelatedPackageVersions: linux-restricted-modules-5.4.0-59-generic N/A linux-backports-modules-5.4.0-59-generic N/A linux-firmware1.187.7 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: focal Uname: Linux 5.4.0-59-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: sudo WifiSyslog: _MarkForUpload: True dmi.bios.date: 01/20/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F2 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H81M-D3H dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF2:bd01/20/2014:svnGigabyteTechnologyCo.,Ltd.:pnH81M-D3H:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnH81M-D3H:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: H81M-D3H dmi.product.sku: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-11-04 (64 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: Gigabyte Technology Co., Ltd. H81M-D3H NonfreeKernelModules: nvidia Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=es_ES.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-59-generic root=UUID=b0ed05d5-7921-451b-b62c-773b97eeca2f ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-59.65-generic 5.4.78 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.4.0-59-generic N/A linux-backports-modules-5.4.0-59-generic N/A linux-firmware1.187.7 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: focal Uname: Linux 5.4.0-59-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 01/20/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F2 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H81M-D3H dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF2:bd01/20/2014:svnGigabyteTe
[Desktop-packages] [Bug 1895643] Re: Backport Thunderbird 78 to 20.04 LTS and 18.04 LTS
https://www.mozilla.org/en-US/security/advisories/mfsa2021-02/ -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to thunderbird in Ubuntu. https://bugs.launchpad.net/bugs/1895643 Title: Backport Thunderbird 78 to 20.04 LTS and 18.04 LTS Status in thunderbird package in Ubuntu: Fix Released Status in thunderbird source package in Bionic: Triaged Status in thunderbird source package in Focal: Fix Committed Status in thunderbird source package in Groovy: Fix Released Bug description: Upstream Thunderbird version 78.2.2 should be a candidate for backporting to stable Ubuntu releases. I've successfully built 78.2.1 against both with forcing nodejs version (20.04, 18.04) and disabling AV1 support due to too old nasm (18.04). Attaching debdiffs here. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1895643/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1908167] Re: [SRU] pulseaudio: the headset-mic or heapdhone-mic could not be selected automatically if there is no internal mic
** Description changed: [Impact] On the Dell AIO machines, there is no internal mic, after plugging a headset, users expect the headset-mic or headphone-mic could be selected automatically. But with the current rule, the headset-mic/headphone-mic will not be selected automatically and even users manually select them, they will not show up in the gnome sound setting, and users could not record sound by headset-mic/headphone-mic. [Fix] backport a patch from pulseaudio mergerequest, the patch is going to be merged to pulseaudio 14.1. This patch could be backported to hirsute without any change, but need to be changed if backport it to groovy and focal. [Test] - On those Dell AIO, plug a headset, open the gnome sound setting, the headset-mic is selected automatically, use the headset-mic to record the sound, the sound could be recorded and the sound quality is good. + With the old pulseaudio (prior to 1:13.99.1-1ubuntu3.10), plugging in a headset to the problematic Dell AIO machine will not automatically select headset-mic/headphone-mic, and they also do not show up in Gnome sound settings, leading to failure to record any sound. + + With the new proposed package, on those Dell AIO, plug a headset, open + the gnome sound setting, the headset-mic is selected automatically, use + the headset-mic to record the sound, the sound could be recorded and the + sound quality is good. [Where problems could occur] This patch could change the policy of audio device switching, it will not affect all audio devices, but only the devices which has AVAIL_UNKNOWN available status, that means it has possibility to introduce the regression on headphone-mic ,headset-mic, internal mic and internal speaker's switching since they all has AVAIL_UNKNOWN status. For example, after unpluging the headset, the input device will not switch to internal mic automatically or after unplug the headphone, the output device will not switch to internal speaker automatically. But this possibility is very low, we have tested the patch on many Dell and Lenovo machines, all worked well. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1908167 Title: [SRU] pulseaudio: the headset-mic or heapdhone-mic could not be selected automatically if there is no internal mic Status in HWE Next: New Status in OEM Priority Project: New Status in pulseaudio package in Ubuntu: Fix Released Status in pulseaudio source package in Focal: Fix Committed Status in pulseaudio source package in Groovy: Fix Committed Status in pulseaudio source package in Hirsute: Fix Released Bug description: [Impact] On the Dell AIO machines, there is no internal mic, after plugging a headset, users expect the headset-mic or headphone-mic could be selected automatically. But with the current rule, the headset-mic/headphone-mic will not be selected automatically and even users manually select them, they will not show up in the gnome sound setting, and users could not record sound by headset-mic/headphone-mic. [Fix] backport a patch from pulseaudio mergerequest, the patch is going to be merged to pulseaudio 14.1. This patch could be backported to hirsute without any change, but need to be changed if backport it to groovy and focal. [Test] With the old pulseaudio (prior to 1:13.99.1-1ubuntu3.10), plugging in a headset to the problematic Dell AIO machine will not automatically select headset-mic/headphone-mic, and they also do not show up in Gnome sound settings, leading to failure to record any sound. With the new proposed package, on those Dell AIO, plug a headset, open the gnome sound setting, the headset-mic is selected automatically, use the headset-mic to record the sound, the sound could be recorded and the sound quality is good. [Where problems could occur] This patch could change the policy of audio device switching, it will not affect all audio devices, but only the devices which has AVAIL_UNKNOWN available status, that means it has possibility to introduce the regression on headphone-mic ,headset-mic, internal mic and internal speaker's switching since they all has AVAIL_UNKNOWN status. For example, after unpluging the headset, the input device will not switch to internal mic automatically or after unplug the headphone, the output device will not switch to internal speaker automatically. But this possibility is very low, we have tested the patch on many Dell and Lenovo machines, all worked well. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1908167/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 47751]
This was fixed via bug 1425874. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/47751 Title: Dos problem with marquee tag Status in Mozilla Firefox: Invalid Status in firefox package in Ubuntu: Won't Fix Status in firefox-3.0 package in Ubuntu: Won't Fix Bug description: Hi, as also reported on securityfocus at http://www.securityfocus.com/archive/1/435373/30/0/threaded using this kind of html page: Credit to n00b.. Firefox uses all the cpu resources and it becames not usable. I've tested it in ubuntu dapper (upgraded from flight 6) on amd64 (firefox is at version 1.5.0.3) To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/47751/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 47751]
This doesn't happen with our new Marquee implementation. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/47751 Title: Dos problem with marquee tag Status in Mozilla Firefox: Invalid Status in firefox package in Ubuntu: Won't Fix Status in firefox-3.0 package in Ubuntu: Won't Fix Bug description: Hi, as also reported on securityfocus at http://www.securityfocus.com/archive/1/435373/30/0/threaded using this kind of html page: Credit to n00b.. Firefox uses all the cpu resources and it becames not usable. I've tested it in ubuntu dapper (upgraded from flight 6) on amd64 (firefox is at version 1.5.0.3) To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/47751/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 47751] Re: Dos problem with marquee tag
** Changed in: firefox Status: Confirmed => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/47751 Title: Dos problem with marquee tag Status in Mozilla Firefox: Invalid Status in firefox package in Ubuntu: Won't Fix Status in firefox-3.0 package in Ubuntu: Won't Fix Bug description: Hi, as also reported on securityfocus at http://www.securityfocus.com/archive/1/435373/30/0/threaded using this kind of html page: Credit to n00b.. Firefox uses all the cpu resources and it becames not usable. I've tested it in ubuntu dapper (upgraded from flight 6) on amd64 (firefox is at version 1.5.0.3) To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/47751/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1911441] Re: Bluetooth headphones and microphone not detected
** Package changed: ubuntu => alsa-driver (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1911441 Title: Bluetooth headphones and microphone not detected Status in alsa-driver package in Ubuntu: New Bug description: Trouble when connecting paired bluetooth headphones on Ubuntu 20.04. The bluetooth headphones can be paired, but not connected. ``` $ bluetoothctl # scan on Discovery started [CHG] Controller F0:85:C1:FF:BD:A8 Discovering: yes [NEW] Device FC:58:FA:CF:D0:01 BT-1100 # scan off Discovery stopped [CHG] Controller F0:85:C1:FF:BD:A8 Discovering: no [CHG] Device FC:58:FA:CF:D0:01 RSSI is nil # devices Device FC:58:FA:CF:D0:01 BT-1100 # pair FC:58:FA:CF:D0:01 Attempting to pair with FC:58:FA:CF:D0:01 [CHG] Device FC:58:FA:CF:D0:01 Connected: yes [CHG] Device FC:58:FA:CF:D0:01 Connected: no [CHG] Device FC:58:FA:CF:D0:01 Connected: yes [CHG] Device FC:58:FA:CF:D0:01 UUIDs: 1108--1000-8000-00805f9b34fb [CHG] Device FC:58:FA:CF:D0:01 UUIDs: 110b--1000-8000-00805f9b34fb [CHG] Device FC:58:FA:CF:D0:01 UUIDs: 110e--1000-8000-00805f9b34fb [CHG] Device FC:58:FA:CF:D0:01 UUIDs: 111e--1000-8000-00805f9b34fb [CHG] Device FC:58:FA:CF:D0:01 ServicesResolved: yes [CHG] Device FC:58:FA:CF:D0:01 Paired: yes Pairing successful [CHG] Device FC:58:FA:CF:D0:01 ServicesResolved: no [CHG] Device FC:58:FA:CF:D0:01 Connected: no # connect FC:58:FA:CF:D0:01 Attempting to connect to FC:58:FA:CF:D0:01 [CHG] Device FC:58:FA:CF:D0:01 Connected: yes [CHG] Device FC:58:FA:CF:D0:01 Connected: no Failed to connect: org.bluez.Error.Failed [CHG] Device FC:58:FA:CF:D0:01 Connected: yes [CHG] Device FC:58:FA:CF:D0:01 Connected: no ``` Logs: ``` Jan 05 00:59:00 host1 bluetoothd[536]: Unable to get connect data for Headset Voice gateway: getpeername: Transport endpoint is not connected (107) Jan 05 00:59:02 host1 bluetoothd[536]: connect error: Connection reset by peer (104) Jan 05 00:59:37 host1 bluetoothd[536]: connect error: Connection reset by peer (104) ``` Pulseaudio configs: ``` $ grep -P '(bluetooth|bluez)' /etc/pulse/default.pa /etc/pulse/system.pa /etc/pulse/default.pa:#.ifexists module-bluetooth-policy.so /etc/pulse/default.pa:load-module module-bluetooth-policy /etc/pulse/default.pa:#.ifexists module-bluetooth-discover.so /etc/pulse/default.pa:load-module module-bluetooth-discover /etc/pulse/system.pa:load-module module-bluez5-device /etc/pulse/system.pa:load-module module-bluez5-discover ``` Packages installed: ``` $ dpkg -l | grep -P '(bluetooth|bluez)' ii blueman 2.1.2-1ubuntu0.2 amd64Graphical bluetooth manager ii bluez5.53-0ubuntu3 amd64Bluetooth tools and daemons ii bluez-obexd 5.53-0ubuntu3 amd64bluez obex daemon ii bluez-tools 2.0~20170911.0.7cb788c-2build1 amd64Set of tools to manage Bluetooth devices for linux ii libbluetooth3:amd64 5.53-0ubuntu3 amd64Library to use the BlueZ Linux Bluetooth stack ii pulseaudio-module-bluetooth 1:13.99.1-1ubuntu3.8 amd64Bluetooth module for PulseAudio sound server ``` ``` $ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 20.04.1 LTS Release:20.04 Codename: focal $ uname -a Linux host1 5.4.0-59-generic #65-Ubuntu SMP Thu Dec 10 12:01:51 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux ``` Please help. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-60.67-generic 5.4.78 Uname: Linux 5.4.0-60-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 AudioDevicesInUse: Error: [Errno 2] No such file or directory: 'fuser' CasperMD5CheckResult: skip Date: Wed Jan 13 17:18:39 2021 PackageArchitecture: all ProcEnviron: TERM=st-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Title: Bluetooth sound card not detected UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/14/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 8.17 dmi.board.asset.tag: Default string dmi.board.name: CITI E202 ES2002EW dmi.board.vendor: Digma dmi.board.version: 1.0 dmi.chassis.asset.tag: Default string dmi.chassis.type: 31 dmi.chassis.vendor: Digma dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr8.17:bd03/14/2018
[Desktop-packages] [Bug 1911441] [NEW] Bluetooth headphones and microphone not detected
You have been subscribed to a public bug: Trouble when connecting paired bluetooth headphones on Ubuntu 20.04. The bluetooth headphones can be paired, but not connected. ``` $ bluetoothctl # scan on Discovery started [CHG] Controller F0:85:C1:FF:BD:A8 Discovering: yes [NEW] Device FC:58:FA:CF:D0:01 BT-1100 # scan off Discovery stopped [CHG] Controller F0:85:C1:FF:BD:A8 Discovering: no [CHG] Device FC:58:FA:CF:D0:01 RSSI is nil # devices Device FC:58:FA:CF:D0:01 BT-1100 # pair FC:58:FA:CF:D0:01 Attempting to pair with FC:58:FA:CF:D0:01 [CHG] Device FC:58:FA:CF:D0:01 Connected: yes [CHG] Device FC:58:FA:CF:D0:01 Connected: no [CHG] Device FC:58:FA:CF:D0:01 Connected: yes [CHG] Device FC:58:FA:CF:D0:01 UUIDs: 1108--1000-8000-00805f9b34fb [CHG] Device FC:58:FA:CF:D0:01 UUIDs: 110b--1000-8000-00805f9b34fb [CHG] Device FC:58:FA:CF:D0:01 UUIDs: 110e--1000-8000-00805f9b34fb [CHG] Device FC:58:FA:CF:D0:01 UUIDs: 111e--1000-8000-00805f9b34fb [CHG] Device FC:58:FA:CF:D0:01 ServicesResolved: yes [CHG] Device FC:58:FA:CF:D0:01 Paired: yes Pairing successful [CHG] Device FC:58:FA:CF:D0:01 ServicesResolved: no [CHG] Device FC:58:FA:CF:D0:01 Connected: no # connect FC:58:FA:CF:D0:01 Attempting to connect to FC:58:FA:CF:D0:01 [CHG] Device FC:58:FA:CF:D0:01 Connected: yes [CHG] Device FC:58:FA:CF:D0:01 Connected: no Failed to connect: org.bluez.Error.Failed [CHG] Device FC:58:FA:CF:D0:01 Connected: yes [CHG] Device FC:58:FA:CF:D0:01 Connected: no ``` Logs: ``` Jan 05 00:59:00 host1 bluetoothd[536]: Unable to get connect data for Headset Voice gateway: getpeername: Transport endpoint is not connected (107) Jan 05 00:59:02 host1 bluetoothd[536]: connect error: Connection reset by peer (104) Jan 05 00:59:37 host1 bluetoothd[536]: connect error: Connection reset by peer (104) ``` Pulseaudio configs: ``` $ grep -P '(bluetooth|bluez)' /etc/pulse/default.pa /etc/pulse/system.pa /etc/pulse/default.pa:#.ifexists module-bluetooth-policy.so /etc/pulse/default.pa:load-module module-bluetooth-policy /etc/pulse/default.pa:#.ifexists module-bluetooth-discover.so /etc/pulse/default.pa:load-module module-bluetooth-discover /etc/pulse/system.pa:load-module module-bluez5-device /etc/pulse/system.pa:load-module module-bluez5-discover ``` Packages installed: ``` $ dpkg -l | grep -P '(bluetooth|bluez)' ii blueman 2.1.2-1ubuntu0.2 amd64Graphical bluetooth manager ii bluez5.53-0ubuntu3 amd64Bluetooth tools and daemons ii bluez-obexd 5.53-0ubuntu3 amd64bluez obex daemon ii bluez-tools 2.0~20170911.0.7cb788c-2build1 amd64Set of tools to manage Bluetooth devices for linux ii libbluetooth3:amd64 5.53-0ubuntu3 amd64Library to use the BlueZ Linux Bluetooth stack ii pulseaudio-module-bluetooth 1:13.99.1-1ubuntu3.8 amd64Bluetooth module for PulseAudio sound server ``` ``` $ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 20.04.1 LTS Release:20.04 Codename: focal $ uname -a Linux host1 5.4.0-59-generic #65-Ubuntu SMP Thu Dec 10 12:01:51 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux ``` Please help. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-60.67-generic 5.4.78 Uname: Linux 5.4.0-60-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 AudioDevicesInUse: Error: [Errno 2] No such file or directory: 'fuser' CasperMD5CheckResult: skip Date: Wed Jan 13 17:18:39 2021 PackageArchitecture: all ProcEnviron: TERM=st-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Title: Bluetooth sound card not detected UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/14/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 8.17 dmi.board.asset.tag: Default string dmi.board.name: CITI E202 ES2002EW dmi.board.vendor: Digma dmi.board.version: 1.0 dmi.chassis.asset.tag: Default string dmi.chassis.type: 31 dmi.chassis.vendor: Digma dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr8.17:bd03/14/2018:svnDigma:pnCITIE202ES2002EW:pvrDefaultstring:rvnDigma:rnCITIE202ES2002EW:rvr1.0:cvnDigma:ct31:cvrDefaultstring: dmi.product.family: EMI30P3S6M22L18B320T4C00W1H2G0G3A1C2P1C0D0C1801M0N1X1WOS dmi.product.name: CITI E202 ES2002EW dmi.product.sku: 20180313288 dmi.product.version: Default string dmi.sys.vendor: Digma ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- Bluetooth headphones and microphone not detected https://bugs.launchpad.net/bugs/19
[Desktop-packages] [Bug 1908502] Re: [MIR] libtiff5 dependency on libdeflate0
** Also affects: tiff (Ubuntu Hirsute) Importance: Undecided Assignee: Olivier Tilloy (osomon) Status: Confirmed ** Also affects: libdeflate (Ubuntu Hirsute) Importance: Undecided Status: Incomplete ** Tags removed: rls-hh-incoming -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to tiff in Ubuntu. https://bugs.launchpad.net/bugs/1908502 Title: [MIR] libtiff5 dependency on libdeflate0 Status in libdeflate package in Ubuntu: Incomplete Status in tiff package in Ubuntu: Confirmed Status in libdeflate source package in Hirsute: Incomplete Status in tiff source package in Hirsute: Confirmed Bug description: tiff 4.1.0+git201212-1 enabled deflate support, adding libdeflate0 as a dependency to libtiff5, making the package uninstallable. Therefor I uploaded 4.1.0+git201212-1ubuntu1 disabling the deflate support to make libtiff5 installable again. Either this package stays this way, or it needs a MIR for libdeflate. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libdeflate/+bug/1908502/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 254488] Re: DNS is not updated when using preshared key
Sure. Have no idea whether it still actual. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager-openvpn in Ubuntu. https://bugs.launchpad.net/bugs/254488 Title: DNS is not updated when using preshared key Status in network-manager-openvpn package in Ubuntu: New Bug description: Binary package hint: network-manager-openvpn Installed network-manager-openvpn 0.3.2svn2342-1ubuntu4 (ubuntu 7.10 "gutsy") In preshared key mode openvpn doesn't pass dns options (or, better to say, "--push" mechanism doesn't work). So, it's necessary to add to "Edit VPN connection" dialog parameters for DNS servers and domain name when "Pre-shared key" is selected. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager-openvpn/+bug/254488/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1911369] Re: [radeon] Horizontal lines of screen corruption after last update.
tried an older kernel. No change. 5.4.0-42-generic ** Attachment added: "screen_corruption.png" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1911369/+attachment/5452713/+files/screen_corruption.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1911369 Title: [radeon] Horizontal lines of screen corruption after last update. Status in linux package in Ubuntu: Confirmed Status in mesa package in Ubuntu: New Bug description: A clean install is fine if I don't take updates. If I do take the updates and reboot then I get heavy video corruption. This just started today. This is a dual boot system. The windows system has no issues. Appears to be software and not a hardware issue. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.8.0-36.40~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-36-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Jan 12 21:18:27 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Tahiti PRO [Radeon HD 7950/8950 OEM / R9 280] [1002:679a] (prog-if 00 [VGA controller]) Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] Tahiti PRO2 [Radeon HD 7950 Boost] [1002:3000] InstallationDate: Installed on 2021-01-13 (0 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: Hewlett-Packard HP Z420 Workstation ProcEnviron: LANGUAGE=en_CA:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_CA.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-36-generic root=UUID=e1d90a30-a65a-46c5-bae3-c39bbf1a4e0e ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/29/2019 dmi.bios.release: 3.96 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: J61 v03.96 dmi.board.name: 1589 dmi.board.vendor: Hewlett-Packard dmi.board.version: 0.00 dmi.chassis.type: 6 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvrJ61v03.96:bd10/29/2019:br3.96:svnHewlett-Packard:pnHPZ420Workstation:pvr:rvnHewlett-Packard:rn1589:rvr0.00:cvnHewlett-Packard:ct6:cvr: dmi.product.family: 103C_53335X G=D dmi.product.name: HP Z420 Workstation dmi.product.sku: D8N02UC#ABA dmi.sys.vendor: Hewlett-Packard version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.1~20.04.1 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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1911369/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1841826] Re: Going to sleep instead of logging in while lid closed & external display
Here are a few more observations on this login sleep issue ('it') :
- not 100% of the time, does this occur
- I experimented with the input devices (logitech) enumerated before / after
login and saw no change/impact on it from that activity
- I have seen it on a reboot, without any state change on the closed lid
- I have seen it when starting up with the lid open (once in a while I power it
up and don't immediately close the lid, ending up with 3 displays including the
panel), after closing the lid to return to 2 display mode, and logging in, it
has occurred again
- I have seen it after powering up, leaving the computer idle for 15min at
loging screen, and then login only to have it occur
- The dead giveaway for me visually, is that my wifi icon is missing or
immediately disaappears as I login, a signal to me the sleep process has
started.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-settings-daemon in Ubuntu.
https://bugs.launchpad.net/bugs/1841826
Title:
Going to sleep instead of logging in while lid closed & external
display
Status in gnome-settings-daemon package in Ubuntu:
Confirmed
Status in gnome-shell package in Ubuntu:
Confirmed
Status in mutter package in Ubuntu:
Confirmed
Bug description:
I have the above described problem, which seems to be very similar to
bug #1716160
- laptop is in docking station and 2 monitors are connected (HDMI,
DVI)
- If the lid is closed and I boot the laptop I can input my
credentials in the login screen and after hitting ENTER the laptop
goes to sleep
- If I then press the power button of the docking station the laptop
wakes up and goes straight to the ubuntu environment w/o any user
identification
The device is a Lenovo T420 with classic docking station. Ubuntu
18.04.3 LTS. Internal graphics Intel integrated grafics and dedicated
Nvidia Quadro NVS 4200M with propriety driver 390.116. Behavior
independent of the graphics used.
I do not know what to do now since the latest state of bug #1716160 is
"fix released" and so I guess it should be part of the ubuntu version
I use?
Thank you very much.
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: gnome-shell 3.28.4-0ubuntu18.04.1
ProcVersionSignature: Ubuntu 5.0.0-25.26~18.04.1-generic 5.0.18
Uname: Linux 5.0.0-25-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.9-0ubuntu7.7
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Wed Aug 28 20:10:15 2019
DisplayManager: gdm3
GsettingsChanges:
b'org.gnome.shell' b'app-picker-view' b'uint32 1'
b'org.gnome.shell' b'favorite-apps' redacted by apport
b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
b'org.gnome.desktop.interface' b'show-battery-percentage' b'true'
b'org.gnome.desktop.interface' b'clock-show-date' b'true'
InstallationDate: Installed on 2019-08-13 (14 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=de_DE.UTF-8
SHELL=/bin/bash
SourcePackage: gnome-shell
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1841826/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1881142] Re: Installation on clean 20.04 LTS system results in "/usr/lib/udev/rules.d/60-libifd-cyberjack6.rules:6 Unknown group 'pcscd', ignoring"
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: pcsc-cyberjack (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pcsc-lite in Ubuntu. https://bugs.launchpad.net/bugs/1881142 Title: Installation on clean 20.04 LTS system results in "/usr/lib/udev/rules.d/60-libifd-cyberjack6.rules:6 Unknown group 'pcscd', ignoring" Status in pcsc-cyberjack package in Ubuntu: Confirmed Status in pcsc-lite package in Ubuntu: Confirmed Bug description: Steps to reproduce: 1. Have Ubuntu 20.04 LTS installed 2. Install "libifd-cyberjack6" package 3. Reload udev Expected results: * log contains no errors or warnings Actual results: * log contains messages: May 28 18:03:19 focal systemd[1]: Stopping udev Kernel Device Manager... May 28 18:03:19 focal systemd[1]: systemd-udevd.service: Succeeded. May 28 18:03:19 focal systemd[1]: Stopped udev Kernel Device Manager. May 28 18:03:19 focal systemd[1]: Starting udev Kernel Device Manager... May 28 18:03:19 focal systemd-udevd[11464]: /usr/lib/udev/rules.d/60-libifd-cyberjack6.rules:6 Unknown group 'pcscd', ignoring May 28 18:03:19 focal systemd-udevd[11464]: /usr/lib/udev/rules.d/60-libifd-cyberjack6.rules:7 Unknown group 'pcscd', ignoring May 28 18:03:19 focal systemd-udevd[11464]: /usr/lib/udev/rules.d/60-libifd-cyberjack6.rules:8 Unknown group 'pcscd', ignoring May 28 18:03:19 focal systemd-udevd[11464]: /usr/lib/udev/rules.d/60-libifd-cyberjack6.rules:9 Unknown group 'pcscd', ignoring May 28 18:03:19 focal systemd-udevd[11464]: /usr/lib/udev/rules.d/60-libifd-cyberjack6.rules:10 Unknown group 'pcscd', ignoring May 28 18:03:19 focal systemd-udevd[11464]: /usr/lib/udev/rules.d/60-libifd-cyberjack6.rules:11 Unknown group 'pcscd', ignoring May 28 18:03:19 focal systemd-udevd[11464]: /usr/lib/udev/rules.d/60-libifd-cyberjack6.rules:12 Unknown group 'pcscd', ignoring May 28 18:03:19 focal systemd-udevd[11464]: /usr/lib/udev/rules.d/60-libifd-cyberjack6.rules:13 Unknown group 'pcscd', ignoring May 28 18:03:19 focal systemd-udevd[11464]: /usr/lib/udev/rules.d/60-libifd-cyberjack6.rules:14 Unknown group 'pcscd', ignoring May 28 18:03:19 focal systemd-udevd[11464]: /usr/lib/udev/rules.d/60-libifd-cyberjack6.rules:15 Unknown group 'pcscd', ignoring May 28 18:03:19 focal systemd-udevd[11464]: /usr/lib/udev/rules.d/60-libifd-cyberjack6.rules:16 Unknown group 'pcscd', ignoring May 28 18:03:19 focal systemd-udevd[11464]: /usr/lib/udev/rules.d/60-libifd-cyberjack6.rules:17 Unknown group 'pcscd', ignoring May 28 18:03:19 focal systemd-udevd[11464]: /usr/lib/udev/rules.d/60-libifd-cyberjack6.rules:18 Unknown group 'pcscd', ignoring May 28 18:03:19 focal systemd-udevd[11464]: /usr/lib/udev/rules.d/60-libifd-cyberjack6.rules:19 Unknown group 'pcscd', ignoring May 28 18:03:19 focal systemd-udevd[11464]: /usr/lib/udev/rules.d/60-libifd-cyberjack6.rules:20 Unknown group 'pcscd', ignoring May 28 18:03:19 focal systemd-udevd[11464]: /usr/lib/udev/rules.d/60-libifd-cyberjack6.rules:21 Unknown group 'pcscd', ignoring May 28 18:03:19 focal systemd-udevd[11464]: /usr/lib/udev/rules.d/60-libifd-cyberjack6.rules:22 Unknown group 'pcscd', ignoring May 28 18:03:19 focal systemd-udevd[11464]: /usr/lib/udev/rules.d/60-libifd-cyberjack6.rules:23 Unknown group 'pcscd', ignoring May 28 18:03:19 focal systemd-udevd[11464]: /usr/lib/udev/rules.d/60-libifd-cyberjack6.rules:24 Unknown group 'pcscd', ignoring May 28 18:03:19 focal systemd[1]: Started udev Kernel Device Manager. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: libifd-cyberjack6 3.99.5final.sp13+dfsg-2build1 ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Uname: Linux 5.4.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: MATE Date: Thu May 28 18:06:52 2020 InstallationDate: Installed on 2020-04-23 (34 days ago) InstallationMedia: Ubuntu-MATE 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: pcsc-cyberjack UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pcsc-cyberjack/+bug/1881142/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1881142] Re: Installation on clean 20.04 LTS system results in "/usr/lib/udev/rules.d/60-libifd-cyberjack6.rules:6 Unknown group 'pcscd', ignoring"
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: pcsc-lite (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pcsc-lite in Ubuntu. https://bugs.launchpad.net/bugs/1881142 Title: Installation on clean 20.04 LTS system results in "/usr/lib/udev/rules.d/60-libifd-cyberjack6.rules:6 Unknown group 'pcscd', ignoring" Status in pcsc-cyberjack package in Ubuntu: Confirmed Status in pcsc-lite package in Ubuntu: Confirmed Bug description: Steps to reproduce: 1. Have Ubuntu 20.04 LTS installed 2. Install "libifd-cyberjack6" package 3. Reload udev Expected results: * log contains no errors or warnings Actual results: * log contains messages: May 28 18:03:19 focal systemd[1]: Stopping udev Kernel Device Manager... May 28 18:03:19 focal systemd[1]: systemd-udevd.service: Succeeded. May 28 18:03:19 focal systemd[1]: Stopped udev Kernel Device Manager. May 28 18:03:19 focal systemd[1]: Starting udev Kernel Device Manager... May 28 18:03:19 focal systemd-udevd[11464]: /usr/lib/udev/rules.d/60-libifd-cyberjack6.rules:6 Unknown group 'pcscd', ignoring May 28 18:03:19 focal systemd-udevd[11464]: /usr/lib/udev/rules.d/60-libifd-cyberjack6.rules:7 Unknown group 'pcscd', ignoring May 28 18:03:19 focal systemd-udevd[11464]: /usr/lib/udev/rules.d/60-libifd-cyberjack6.rules:8 Unknown group 'pcscd', ignoring May 28 18:03:19 focal systemd-udevd[11464]: /usr/lib/udev/rules.d/60-libifd-cyberjack6.rules:9 Unknown group 'pcscd', ignoring May 28 18:03:19 focal systemd-udevd[11464]: /usr/lib/udev/rules.d/60-libifd-cyberjack6.rules:10 Unknown group 'pcscd', ignoring May 28 18:03:19 focal systemd-udevd[11464]: /usr/lib/udev/rules.d/60-libifd-cyberjack6.rules:11 Unknown group 'pcscd', ignoring May 28 18:03:19 focal systemd-udevd[11464]: /usr/lib/udev/rules.d/60-libifd-cyberjack6.rules:12 Unknown group 'pcscd', ignoring May 28 18:03:19 focal systemd-udevd[11464]: /usr/lib/udev/rules.d/60-libifd-cyberjack6.rules:13 Unknown group 'pcscd', ignoring May 28 18:03:19 focal systemd-udevd[11464]: /usr/lib/udev/rules.d/60-libifd-cyberjack6.rules:14 Unknown group 'pcscd', ignoring May 28 18:03:19 focal systemd-udevd[11464]: /usr/lib/udev/rules.d/60-libifd-cyberjack6.rules:15 Unknown group 'pcscd', ignoring May 28 18:03:19 focal systemd-udevd[11464]: /usr/lib/udev/rules.d/60-libifd-cyberjack6.rules:16 Unknown group 'pcscd', ignoring May 28 18:03:19 focal systemd-udevd[11464]: /usr/lib/udev/rules.d/60-libifd-cyberjack6.rules:17 Unknown group 'pcscd', ignoring May 28 18:03:19 focal systemd-udevd[11464]: /usr/lib/udev/rules.d/60-libifd-cyberjack6.rules:18 Unknown group 'pcscd', ignoring May 28 18:03:19 focal systemd-udevd[11464]: /usr/lib/udev/rules.d/60-libifd-cyberjack6.rules:19 Unknown group 'pcscd', ignoring May 28 18:03:19 focal systemd-udevd[11464]: /usr/lib/udev/rules.d/60-libifd-cyberjack6.rules:20 Unknown group 'pcscd', ignoring May 28 18:03:19 focal systemd-udevd[11464]: /usr/lib/udev/rules.d/60-libifd-cyberjack6.rules:21 Unknown group 'pcscd', ignoring May 28 18:03:19 focal systemd-udevd[11464]: /usr/lib/udev/rules.d/60-libifd-cyberjack6.rules:22 Unknown group 'pcscd', ignoring May 28 18:03:19 focal systemd-udevd[11464]: /usr/lib/udev/rules.d/60-libifd-cyberjack6.rules:23 Unknown group 'pcscd', ignoring May 28 18:03:19 focal systemd-udevd[11464]: /usr/lib/udev/rules.d/60-libifd-cyberjack6.rules:24 Unknown group 'pcscd', ignoring May 28 18:03:19 focal systemd[1]: Started udev Kernel Device Manager. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: libifd-cyberjack6 3.99.5final.sp13+dfsg-2build1 ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Uname: Linux 5.4.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: MATE Date: Thu May 28 18:06:52 2020 InstallationDate: Installed on 2020-04-23 (34 days ago) InstallationMedia: Ubuntu-MATE 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: pcsc-cyberjack UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pcsc-cyberjack/+bug/1881142/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 708675] Re: There should be an option NOT to store passphrase for openvpn key
please close storing password is optional in network-manager-openvpn 1.8.12-2 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager-openvpn in Ubuntu. https://bugs.launchpad.net/bugs/708675 Title: There should be an option NOT to store passphrase for openvpn key Status in network-manager-openvpn package in Ubuntu: New Bug description: Binary package hint: network-manager-openvpn When configuring an OpenVPN connection the "OK"-button (With a danish locale it says "Anvend", I don't know what it says in other languages), until you've entered the passphrase for your private key, and if I enter a wrong passphrase, the conection just doesn't work. That's bad, and I know it stored in encrypted by gnome-keyring, but I prefer not having it stored at all (and I know that just makes be more vulnerable to people watching me type the passphrase, but I prefer that risk - and generally consider gnome-keyring to be evil). ProblemType: Bug DistroRelease: Ubuntu 10.10 Package: network-manager-openvpn-gnome 0.8.1+git.20100810t173015.1711d04-0ubuntu1 ProcVersionSignature: Ubuntu 2.6.35-24.42-generic 2.6.35.8 Uname: Linux 2.6.35-24-generic x86_64 Architecture: amd64 Date: Thu Jan 27 15:55:12 2011 ProcEnviron: LANG=da_DK SHELL=/bin/zsh SourcePackage: network-manager-openvpn To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager-openvpn/+bug/708675/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1530439] Re: Add OpenVPN option --tls-version-max
Please close. maximum TLS version is present in network-manager-openvpn/groovy 1.8.12-2. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager-openvpn in Ubuntu. https://bugs.launchpad.net/bugs/1530439 Title: Add OpenVPN option --tls-version-max Status in network-manager-openvpn package in Ubuntu: New Bug description: The attached patch adds support for the OpenVPN option --tls-version- max to network-manager-openvpn 0.9.10.0. Successfully tested on Ubuntu 15.10 (Wily Werewolf). Find the new option here: >> Button "Edit" >> Tab "VPN" >> Button "Advanced" >> Tab "TLS Authentication" >> Check box and drop-down menu "Set maximum TLS version" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager-openvpn/+bug/1530439/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1910912] Re: Settings not applied to USB touchpad and keyboard
This bug has been fixed with mutter (3.36.7+git20201123-0.20.04.1) ** Changed in: gnome-settings-daemon (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1910912 Title: Settings not applied to USB touchpad and keyboard Status in gnome-settings-daemon package in Ubuntu: Fix Released Bug description: Bug originated after doing a 18.04.5 LTS to 20.04.1 LTS upgrade. The settings from gnome-control-center are not getting applied for external USB devices. For a USB touchpad I've spotted this with the following: org.gnome.desktop.peripherals.touchpad tap-and-drag org.gnome.desktop.peripherals.touchpad tap-to-click For a USB keyboard I've observed this for the input language. I have EN and BG as input languages, but if I plug in an external I can only type in EN (the default language). The fix for both is to go in gnome control center (or gsettings) and do a toggle. I've made a small screencast to demonstrate the issue. https://drive.google.com/file/d/1mP92waNjUmU3rYB6FaHgyow0WzXOItLd/view The system is a Dell XPS 9550 and the Touchpad is a Logitech T650 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-settings-daemon 3.36.1-0ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-60.67-generic 5.4.78 Uname: Linux 5.4.0-60-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Jan 10 17:05:31 2021 InstallationDate: Installed on 2016-04-29 (1716 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) SourcePackage: gnome-settings-daemon UpgradeStatus: Upgraded to focal on 2020-09-29 (102 days ago) modified.conffile..etc.apport.crashdb.conf: [modified] mtime.conffile..etc.apport.crashdb.conf: 2019-01-22T11:19:11.812508 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1910912/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 254488] Re: DNS is not updated when using preshared key
Can we close this as wont-fix. It is 12years old. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager-openvpn in Ubuntu. https://bugs.launchpad.net/bugs/254488 Title: DNS is not updated when using preshared key Status in network-manager-openvpn package in Ubuntu: New Bug description: Binary package hint: network-manager-openvpn Installed network-manager-openvpn 0.3.2svn2342-1ubuntu4 (ubuntu 7.10 "gutsy") In preshared key mode openvpn doesn't pass dns options (or, better to say, "--push" mechanism doesn't work). So, it's necessary to add to "Edit VPN connection" dialog parameters for DNS servers and domain name when "Pre-shared key" is selected. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager-openvpn/+bug/254488/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1726124] Re: DNS domain search paths not updated when VPN started
Still an issue in 20.10 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1726124 Title: DNS domain search paths not updated when VPN started Status in network-manager package in Ubuntu: Confirmed Status in network-manager-openvpn package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Confirmed Bug description: I connect to work with openvpn through network-manager-openvpn. I'm selecting automatic (DHCP) to get an IP address, and "Use this connection only for resources on its network" to support split tunneling. In the last few versions of Ubuntu I used, this all worked fine. In Ubuntu 17.10 (fresh install, not upgrade) I can access hosts on both my VPN network and the internet, BUT I have to use FQDN for my VPN network hosts: the updates to the DNS search path provided by my VPN DHCP server are never being applied. Investigating the system I see that /etc/resolv.conf is pointing to /run/systemd/resolve/stub-resolv.conf and that resolv.conf does not have any of the VPN's search path settings in it: # This file is managed by man:systemd-resolved(8). Do not edit. # # 127.0.0.53 is the systemd-resolved stub resolver. # run "systemd-resolve --status" to see details about the actual nameservers. nameserver 127.0.0.53 search home In previous versions of Ubuntu, where NetworkManager controlled the resolver not systemd, /etc/resolv.conf pointed to /run/NetworkManager/resolv.conf and there was a local dnsmasq instance that managed all the complexity. In Ubuntu 17.10 when I look in /run/NetworkManager/resolv.conf file, I see that the search paths ARE properly updated there: $ cat /run/NetworkManager/resolv.conf # Generated by NetworkManager search internal.mycorp.com other.mycorp.com home nameserver 127.0.1.1 However this file isn't being used, and also there's no dnsmasq running on the system so if I switch my /etc/resolv.conf to point to this file instead, then all lookups fail. Strangely, if I look at the systemd-resolv status I see that in theory systemd-resolve does seem to know about the proper search paths: $ systemd-resolve --status ... Link 3 (tun0) Current Scopes: DNS LLMNR/IPv4 LLMNR/IPv6 LLMNR setting: yes MulticastDNS setting: no DNSSEC setting: no DNSSEC supported: no DNS Servers: 10.3.0.10 10.8.42.2 DNS Domain: ~internal.mycorp.com ~other.mycorp.com but for whatever reason the search domains are not getting put into the resolv.conf file: $ host mydesk ;; connection timed out; no servers could be reached $ host mydesk.internal.mycorp.com mydesk.internal.mycorp.com has address 10.8.37.74 (BTW, the timeout in the failed attempt above takes 10s: it is SUPER frustrating when all your host lookups are taking that long just to fail). ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: systemd 234-2ubuntu12 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CurrentDesktop: GNOME Date: Sun Oct 22 15:08:57 2017 InstallationDate: Installed on 2017-10-21 (1 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) MachineType: System manufacturer System Product Name ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-16-generic root=UUID=4384306c-5fed-4b48-97a6-a6d594c4f72b ro quiet splash vt.handoff=7 SourcePackage: systemd SystemdDelta: [EXTENDED] /lib/systemd/system/rc-local.service → /lib/systemd/system/rc-local.service.d/debian.conf [EXTENDED] /lib/systemd/system/user@.service → /lib/systemd/system/user@.service.d/timeout.conf 2 overridden configuration files found. UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/02/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2101 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: M5A78L-M/USB3 dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2101:bd12/02/2014:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM5A78L-M/USB3:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about
[Desktop-packages] [Bug 1410618] Re: MacBook Air 6, 2 TRRS Headset Mic Not Working
The problem is still present in Ubuntu 20.10 :( -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1410618 Title: MacBook Air 6,2 TRRS Headset Mic Not Working Status in alsa-driver package in Ubuntu: Confirmed Bug description: Hello, I'm running Ubuntu Gnome 14.04 on a new MacBookAir6,2 with the Cirrus Logic CS4208 and would love to get the microphone part of the TRRS connector working. Mac OS picks up and utilizes the TRRS headset mic without issue so I know the hardware is a go. With the headset plugged in, running sudo hdajacksensetest -a results in: Pin 0x05 ( Digital Out, HDMI): present = No Pin 0x06 ( Digital Out, HDMI): present = No Pin 0x07 ( Digital Out, HDMI): present = No AlsaInfo output here: http://www.alsa-project.org/db/?f=cabc8cab44d308c8a3898c66d48d9be4fc5ccf83 I opened up hdajackretask to find four pins: Green Headphone Pin ID: 0x10 Headphone Internal Speaker Pin ID: 0x12 Internal speaker Pink Mic Pin ID: 0x18 Not connected Internal Mic Pin ID: 0x1c Internal mic Unplugging and replugging the headset changes the Output device in sound settings from Headphones to Speakers so that works, but nothing in the input tab ever changes. It always lists two devices: Internal Microphone and Microphone. Both of these seem to actually be the internal microphone in the mac - either works without the headset connected at all. So I'm not really sure how to proceed from here, but I'd be happy to run whatever diagnostic tests might prove useful and/or even contribute code toward a fix - but I just have no idea where to start. Is it as simple as just finding the right pin and telling the system to use it as a microphone? Similar bug report here: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/950494 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1410618/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1908921] Re: No system tray detected by hp-systray
I am also affected. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-appindicator in Ubuntu. https://bugs.launchpad.net/bugs/1908921 Title: No system tray detected by hp-systray Status in gnome-shell-extension-appindicator package in Ubuntu: Confirmed Bug description: I have hp-systray -x as one of the startup applications when I login. This app exits with the following error: HPLIP Status service No system tray detected on this system. Unable to start, exiting. Once logged in, if I start hp-systray -x from the terminal it works fine. This started happening after updating gnome-shell-extension- appindicator from version 33-1 to version 33.1-0ubuntu0.20.04.1. Thanks ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell-extension-appindicator 33.1-0ubuntu0.20.04.1 ProcVersionSignature: Ubuntu 5.4.0-58.64-generic 5.4.73 Uname: Linux 5.4.0-58-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Dec 21 11:41:23 2020 EcryptfsInUse: Yes InstallationDate: Installed on 2016-06-10 (1655 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) PackageArchitecture: all SourcePackage: gnome-shell-extension-appindicator UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-appindicator/+bug/1908921/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1910537] Re: HDMI audio not working on Blackmagic Design ATEM Mini Pro ISO (video mixer)
> Please try running this command: > xrandr --output HDMI-1 --set audio on > If it still doesn't work then try logging in again after that. Neither did help... -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1910537 Title: HDMI audio not working on Blackmagic Design ATEM Mini Pro ISO (video mixer) Status in pulseaudio package in Ubuntu: Incomplete Bug description: This is a complicated thing. I have a very specific problem with audio output on HDMI. I want to use an older notebook with Lubuntu 20.04 as a video source for libreoffice slides, videos etc. to feed them over HDMI into a Blackmagic Design ATEM Mini Pro ISO (video mixer) as one input. Configured on the desktop just like a second screen or beamer. Video works well and rock-stable, no problem at all. But not audio. Although I carefully configured audio with pavucontrol to be directed to the HDMI output, the ATEM switcher does not recognize it as an audio source (like when connecting a digital camera) and does not receive or indicate any audio input. Note: But when I use the very same computer, same HDMI cable, same video with a cheap chinese portable LCD screen with speakers (i.e. pull the cable from the ATEM and plug it into the screen) it immediately starts playing both video and audio. So there is evidence that the ubuntu notebook definitely passes it's sound to HDMI and there's really an audio signal on the HDMI. I've opened a bug at Blackmagic Design, and got their reply that they can't help and have never heard of such a problem before. Their guess is that the linux notebook is not setting EDID configuration correctly and thus not recognized by the ATEM, while the cheap LCD screen propably does not care about EDID and just plays everything, therefore a wrong EDID information would not matter. Although I have decades of experience with Linux, I am not too familiar with details of HDMI and the internals of the X11 driver, so I'm not sure where to start debugging, not even, whether this is a problem of Xorg/X11 or pulseaudio. I've checked this with another notebook with much more recent (intel) hardware, which offers dozens of HDMI audio options in the pavucontrol selection menu, but same problem: Video works, but the ATEM does not recognize it as a audio source. Blackmagic Design (they're good in Windows and MacOS, but not Linux) recommended to use an edid manager, whatever this means. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-58.64-generic 5.4.73 Uname: Linux 5.4.0-58-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: LXQt Date: Thu Jan 7 13:16:26 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DpkgLog: ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0106] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] 2nd Generation Core Processor Family Integrated Graphics Controller [1025:0742] InstallationDate: Installed on 2020-05-16 (235 days ago) InstallationMedia: Lubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Lsusb: Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 003: ID 04f2:b336 Chicony Electronics Co., Ltd Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Acer AO756 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-58-generic root=UUID=a69345e2-b61e-4d25-baab-b23f75273af6 ro quiet cryptdevice=UUID=d132b97b-f47a-4432-88b5-42aca187b9ff:luks-d132b97b-f47a-4432-88b5-42aca187b9ff root=/dev/mapper/luks-d132b97b-f47a-4432-88b5-42aca187b9ff resume=/dev/mapper/luks-d132b97b-f47a-4432-88b5-42aca187b9ff splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/19/2012 dmi.bios.vendor: Acer dmi.bios.version: V1.05 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: Mimic dmi.board.vendor: Acer dmi.board.version: Type2 - Board Version dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V1.05 dmi.modalias: dmi:bvnAcer:bvrV1.05:bd07/19/2012:svnAcer:pnAO756:pvrV1.05:rvnAcer:rnMimic:rvrType2-BoardVersion:cvnAcer:ct10:cvrV1.05: dmi.product.family: Type1Family dmi.product.name: AO756 dmi.product.sku: Type1Sku0 dmi.product.version: V1.05 dmi.sys.vendor: Acer version.compiz: compiz N/A
[Desktop-packages] [Bug 1910709] Re: DKMS linux-headers-5.8.0-34-generic update brokes nvidia-340
#37 ** Attachment added: "dpkg & lscpi from two PC" https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/1910709/+attachment/5452699/+files/info.zip -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-340 in Ubuntu. https://bugs.launchpad.net/bugs/1910709 Title: DKMS linux-headers-5.8.0-34-generic update brokes nvidia-340 Status in nvidia-graphics-drivers-340 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-340 source package in Focal: Confirmed Bug description: Last linux kernel update "linux-headers-5.8.0-34-generic" broke nvidia-340 driver and Desktop access. In make log: [...] echo >&2; \ echo >&2 " ERROR: Kernel configuration is invalid."; \ echo >&2 " include/generated/autoconf.h or include/config/auto.conf are missing.";\ echo >&2 " Run 'make oldconfig && make prepare' on kernel src to fix it.";\ echo >&2 ; [...] Full DKMS log file attacked. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-11-04 (64 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: Gigabyte Technology Co., Ltd. H81M-D3H NonfreeKernelModules: nvidia Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=es_ES.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-59-generic root=UUID=b0ed05d5-7921-451b-b62c-773b97eeca2f ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-59.65-generic 5.4.78 RelatedPackageVersions: linux-restricted-modules-5.4.0-59-generic N/A linux-backports-modules-5.4.0-59-generic N/A linux-firmware1.187.7 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: focal Uname: Linux 5.4.0-59-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: sudo WifiSyslog: _MarkForUpload: True dmi.bios.date: 01/20/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F2 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H81M-D3H dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF2:bd01/20/2014:svnGigabyteTechnologyCo.,Ltd.:pnH81M-D3H:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnH81M-D3H:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: H81M-D3H dmi.product.sku: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-11-04 (64 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: Gigabyte Technology Co., Ltd. H81M-D3H NonfreeKernelModules: nvidia Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=es_ES.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-59-generic root=UUID=b0ed05d5-7921-451b-b62c-773b97eeca2f ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-59.65-generic 5.4.78 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.4.0-59-generic N/A linux-backports-modules-5.4.0-59-generic N/A linux-firmware1.187.7 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: focal Uname: Linux 5.4.0-59-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 01/20/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F2 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H81M-D3H dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF2:bd01/20/2014:svnGigabyteTechnologyCo.,Ltd.:pnH81M-D3H:pvrTobefilledbyO.E.M.:rvnGig
[Desktop-packages] [Bug 1910709] Re: DKMS linux-headers-5.8.0-34-generic update brokes nvidia-340
I am experiencing the same problem, my card is: 01:00.0 VGA compatible controller: NVIDIA Corporation GT216GLM [Quadro FX 880M] (rev a2) (prog-if 00 [VGA controller]) DeviceName: 0 Subsystem: Hewlett-Packard Company GT216GLM [Quadro FX 880M] Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- Kernel driver in use: nouveau Kernel modules: nvidiafb, nouveau Currently running nouveau driver but rather i'd have the NVIDIA 340 driver. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-340 in Ubuntu. https://bugs.launchpad.net/bugs/1910709 Title: DKMS linux-headers-5.8.0-34-generic update brokes nvidia-340 Status in nvidia-graphics-drivers-340 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-340 source package in Focal: Confirmed Bug description: Last linux kernel update "linux-headers-5.8.0-34-generic" broke nvidia-340 driver and Desktop access. In make log: [...] echo >&2; \ echo >&2 " ERROR: Kernel configuration is invalid."; \ echo >&2 " include/generated/autoconf.h or include/config/auto.conf are missing.";\ echo >&2 " Run 'make oldconfig && make prepare' on kernel src to fix it.";\ echo >&2 ; [...] Full DKMS log file attacked. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-11-04 (64 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: Gigabyte Technology Co., Ltd. H81M-D3H NonfreeKernelModules: nvidia Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=es_ES.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-59-generic root=UUID=b0ed05d5-7921-451b-b62c-773b97eeca2f ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-59.65-generic 5.4.78 RelatedPackageVersions: linux-restricted-modules-5.4.0-59-generic N/A linux-backports-modules-5.4.0-59-generic N/A linux-firmware1.187.7 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: focal Uname: Linux 5.4.0-59-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: sudo WifiSyslog: _MarkForUpload: True dmi.bios.date: 01/20/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F2 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H81M-D3H dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF2:bd01/20/2014:svnGigabyteTechnologyCo.,Ltd.:pnH81M-D3H:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnH81M-D3H:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: H81M-D3H dmi.product.sku: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-11-04 (64 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: Gigabyte Technology Co., Ltd. H81M-D3H NonfreeKernelModules: nvidia Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=es_ES.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-59-generic root=UUID=b0ed05d5-7921-451b-b62c-773b97eeca2f ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-59.65-generic 5.4.78 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.4.0-59-generic N/A linux-backports-modules-5.4.0-59-generic N/A linux-firmware1.187.7 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: focal Uname: Linux 5.4.0-59-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 01/20/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F2 dmi.board.asset.tag:
[Desktop-packages] [Bug 1911379] Re: [SRU] wslu 3.2.1-0ubuntu2
** No longer affects: wslu (Ubuntu Focal) ** Description changed: [Impact] - For groovy/hirsute, - this affects wslu 3.x which, when tries to start with a clean environment after upgrade, the terminal will throw `rm: file not found` error. - - For focal, - it is proposed to be updated from 2.x to 3.x in 20.10/21.04 circle. + this affects wslu 3.x which, when tries to start with a clean + environment after upgrade, the terminal will throw `rm: file not found` + error. [Test Case] - - For groovy/hirsute: * Install Ubuntu 20.10 to WSL. * run any wslu tools (like wslfetch) * Verify that there is no `rm -rf` error. - For focal: - - * Follow the testing process outlined in https://wiki.ubuntu.com/wslu-Updates - * Run the autopktest in a WSL environment. - * View the result of the test, with 7 Windows Explorer open and 3 webpage open on the default browzer. - [Regression Potential] - - For groovy/hirsute: This patch will try to remove ~/.config/wslu/ to order to reset to default state (especially when first upgrade to latest wslu). Potential regressions would be a result of ~/.config/wslu/ not being cleaned properly. - - For focal: - - This is a large version update from 2.x to 3.x. according to the - previous process merging to groovy on bug LP: #1895525, there is no - clear issue. Potential regressions would be a result of badly generated - ~/.config/wslu/. ** Summary changed: - [SRU] wslu 3.2.1-0ubuntu2 + [SRU] wslu 3.2.1-0ubuntu2 to hirsute and groovy -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to wslu in Ubuntu. https://bugs.launchpad.net/bugs/1911379 Title: [SRU] wslu 3.2.1-0ubuntu2 to hirsute and groovy Status in wslu package in Ubuntu: New Status in wslu source package in Groovy: New Status in wslu source package in Hirsute: New Bug description: [Impact] this affects wslu 3.x which, when tries to start with a clean environment after upgrade, the terminal will throw `rm: file not found` error. [Test Case] * Install Ubuntu 20.10 to WSL. * run any wslu tools (like wslfetch) * Verify that there is no `rm -rf` error. [Regression Potential] This patch will try to remove ~/.config/wslu/ to order to reset to default state (especially when first upgrade to latest wslu). Potential regressions would be a result of ~/.config/wslu/ not being cleaned properly. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wslu/+bug/1911379/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1911432] [NEW] [SRU] wslu 3.2.1-0ubuntu1 to focal
Public bug reported: [Impact] it is proposed to be updated from 2.x to 3.x in 20.10/21.04 circle. The detailed impact can be found on LP: #1895525. [Test Case] * Follow the testing process outlined in https://wiki.ubuntu.com/wslu-Updates * Run the autopktest in a WSL environment. * View the result of the test, with 7 Windows Explorer open and 3 webpage open on the default browzer. [Regression Potential] This is a large version update from 2.x to 3.x. according to the previous process merging to groovy on bug LP: #1895525, there is no clear issue. Potential regressions would be a result of badly generated ~/.config/wslu/. ** Affects: wslu (Ubuntu) Importance: Undecided Status: New ** Affects: wslu (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: wslu (Ubuntu Focal) Importance: Undecided Status: New ** Summary changed: - [SRU] wslu 3.2.1-0ubuntu to focal + [SRU] wslu 3.2.1-0ubuntu1 to focal -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to wslu in Ubuntu. https://bugs.launchpad.net/bugs/1911432 Title: [SRU] wslu 3.2.1-0ubuntu1 to focal Status in wslu package in Ubuntu: New Status in wslu source package in Focal: New Bug description: [Impact] it is proposed to be updated from 2.x to 3.x in 20.10/21.04 circle. The detailed impact can be found on LP: #1895525. [Test Case] * Follow the testing process outlined in https://wiki.ubuntu.com/wslu-Updates * Run the autopktest in a WSL environment. * View the result of the test, with 7 Windows Explorer open and 3 webpage open on the default browzer. [Regression Potential] This is a large version update from 2.x to 3.x. according to the previous process merging to groovy on bug LP: #1895525, there is no clear issue. Potential regressions would be a result of badly generated ~/.config/wslu/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wslu/+bug/1911432/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1911379] Re: [SRU] wslu 3.2.1-0ubuntu2
** Description changed: [Impact] - This affects wslu 3.x which, when tries to start with a clean - environment after upgrade, the terminal will throw `rm: file not found` - error. + For groovy/hirsute, + this affects wslu 3.x which, when tries to start with a clean environment after upgrade, the terminal will throw `rm: file not found` error. + + For focal, + it is proposed to be updated from 2.x to 3.x in 20.10/21.04 circle. [Test Case] - * Install Ubuntu 20.10 to WSL. - * run any wslu tools (like wslfetch) - * Verify that there is no `rm -rf` error. + For groovy/hirsute: + + * Install Ubuntu 20.10 to WSL. + * run any wslu tools (like wslfetch) + * Verify that there is no `rm -rf` error. + + For focal: + + * Follow the testing process outlined in https://wiki.ubuntu.com/wslu-Updates + * Run the autopktest in a WSL environment where the user name contains space. + * View the result of the test, with 7 Windows Explorer open and 3 webpage open on the default browzer. + [Regression Potential] + + For groovy/hirsute: This patch will try to remove ~/.config/wslu/ to order to reset to default state (especially when first upgrade to latest wslu). Potential regressions would be a result of ~/.config/wslu/ not being cleaned properly. + + For focal: + + This is a large version update from 2.x to 3.x. according to the + previous process merging to groovy on bug LP: #1895525, there is no + clear issue. Potential regressions would be a result of badly generated + ~/.config/wslu/. ** Description changed: [Impact] For groovy/hirsute, this affects wslu 3.x which, when tries to start with a clean environment after upgrade, the terminal will throw `rm: file not found` error. - For focal, + For focal, it is proposed to be updated from 2.x to 3.x in 20.10/21.04 circle. [Test Case] For groovy/hirsute: * Install Ubuntu 20.10 to WSL. * run any wslu tools (like wslfetch) * Verify that there is no `rm -rf` error. For focal: - * Follow the testing process outlined in https://wiki.ubuntu.com/wslu-Updates - * Run the autopktest in a WSL environment where the user name contains space. - * View the result of the test, with 7 Windows Explorer open and 3 webpage open on the default browzer. - + * Follow the testing process outlined in https://wiki.ubuntu.com/wslu-Updates + * Run the autopktest in a WSL environment. + * View the result of the test, with 7 Windows Explorer open and 3 webpage open on the default browzer. [Regression Potential] For groovy/hirsute: This patch will try to remove ~/.config/wslu/ to order to reset to default state (especially when first upgrade to latest wslu). Potential regressions would be a result of ~/.config/wslu/ not being cleaned properly. For focal: This is a large version update from 2.x to 3.x. according to the previous process merging to groovy on bug LP: #1895525, there is no clear issue. Potential regressions would be a result of badly generated ~/.config/wslu/. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to wslu in Ubuntu. https://bugs.launchpad.net/bugs/1911379 Title: [SRU] wslu 3.2.1-0ubuntu2 Status in wslu package in Ubuntu: New Status in wslu source package in Focal: New Status in wslu source package in Groovy: New Status in wslu source package in Hirsute: New Bug description: [Impact] For groovy/hirsute, this affects wslu 3.x which, when tries to start with a clean environment after upgrade, the terminal will throw `rm: file not found` error. For focal, it is proposed to be updated from 2.x to 3.x in 20.10/21.04 circle. [Test Case] For groovy/hirsute: * Install Ubuntu 20.10 to WSL. * run any wslu tools (like wslfetch) * Verify that there is no `rm -rf` error. For focal: * Follow the testing process outlined in https://wiki.ubuntu.com/wslu-Updates * Run the autopktest in a WSL environment. * View the result of the test, with 7 Windows Explorer open and 3 webpage open on the default browzer. [Regression Potential] For groovy/hirsute: This patch will try to remove ~/.config/wslu/ to order to reset to default state (especially when first upgrade to latest wslu). Potential regressions would be a result of ~/.config/wslu/ not being cleaned properly. For focal: This is a large version update from 2.x to 3.x. according to the previous process merging to groovy on bug LP: #1895525, there is no clear issue. Potential regressions would be a result of badly generated ~/.config/wslu/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wslu/+bug/1911379/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1181666] Re: gnome-shell randomly blocks mouse clicks from working in app windows
Today I had the same issue on archlinux with kernel 5.9.14 and gnome shell 3.38.2, it happend right after taking an areal screenshot with gnome-screenshot while in fullscreen, after that when I hovered windows bar and the side dock the cursor became the classic cross you see while taking screenshots and left/right clicking didn't give any result. gnome-screenshot was called by a keyboard shortcut. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1181666 Title: gnome-shell randomly blocks mouse clicks from working in app windows Status in GNOME Shell: Confirmed Status in Ubuntu GNOME: Confirmed Status in gnome-shell package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Bug description: Under GNOME 3, the use of the mouse-click stops occasionally, though I can still move the mouse around and can still click on items in the Activities screen and the top-bar. I can use alt-tab to cycle windows and can still type into already- active textboxes in windows, but I cannot click within the windows, and the mouse is not picked up at all by the windows. I can open the alt-f2 "run command" dialogue, but cannot type into it. The workaround I'm using is to open terminal (ctrl-alt-T) and run "gnome-shell -r", and restarting that command every time I have the problem again. Please ask if there's anything I forgot to mention. ADDITIONAL: The error tends to happen randomly, but it seems to happen upon opening a new window, changing windows, closing windows, or opening the activities pane (whether a change of window is thus instigated or not) ADDITIONAL 2: (sorry, it's early) The other workaround is to log out and to log in again, but that is also less than ideal ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: gnome-shell 3.6.3.1-0ubuntu6 ProcVersionSignature: Ubuntu 3.8.0-22.33-generic 3.8.11 Uname: Linux 3.8.0-22-generic x86_64 ApportVersion: 2.9.2-0ubuntu8 Architecture: amd64 Date: Sun May 19 07:02:18 2013 DisplayManager: gdm GsettingsChanges: b'org.gnome.desktop.interface' b'clock-show-date' b'true' b'org.gnome.desktop.interface' b'clock-show-seconds' b'true' b'org.gnome.desktop.interface' b'document-font-name' b"'Sans 10'" b'org.gnome.desktop.interface' b'font-name' b"'Cantarell 10'" b'org.gnome.desktop.interface' b'monospace-font-name' b"'Ubuntu Mono 12'" InstallationDate: Installed on 2013-05-04 (14 days ago) InstallationMedia: Ubuntu-GNOME 13.04 "Raring Ringtail" - Release amd64 (20130424) MarkForUpload: True ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1181666/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1911379] Re: [SRU] wslu 3.2.1-0ubuntu2
** Changed in: wslu (Ubuntu Hirsute) Status: Incomplete => New ** Description changed: - ~~~ - This is a placeholder issue since wslu 3.2.1-0ubuntu2 is not yet merged. - ~~~ - [Impact] - * The wslu package is a set of settings and utilities to integrate - Ubuntu running in WSL to the host Windows 10 system. The wslu package is - shipped in the Ubuntu Microsoft Store apps and in the downloadable WSL - tarballs for supported Ubuntu releases with the intent of providing - uniformly complete integration across all supported Ubuntu releases and - the way of ensuring consistent behavior is back-porting full upstream - releases with minimal changes. - + This affects wslu 3.x which, when tries to start with a clean + environment after upgrade, the terminal will throw `rm: file not found` + error. [Test Case] - * Follow the testing process outlined in https://wiki.ubuntu.com/wslu-Updates - * Run the autopktest in a WSL environment where the user name contains space. - * Verify the other individual bugs fixed by the SRU. + * Install Ubuntu 20.10 to WSL. + * run any wslu tools (like wslfetch) + * Verify that there is no `rm -rf` error. [Regression Potential] - * Compared to wslu 3.2.1-0ubuntu1, there is only one fix that address a - remove error. + This patch will try to remove ~/.config/wslu/ to order to reset to + default state (especially when first upgrade to latest wslu). Potential + regressions would be a result of ~/.config/wslu/ not being cleaned + properly. ** Merge proposal linked: https://code.launchpad.net/~callmepk/ubuntu/+source/wslu/+git/wslu/+merge/396223 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to wslu in Ubuntu. https://bugs.launchpad.net/bugs/1911379 Title: [SRU] wslu 3.2.1-0ubuntu2 Status in wslu package in Ubuntu: New Status in wslu source package in Focal: New Status in wslu source package in Groovy: New Status in wslu source package in Hirsute: New Bug description: [Impact] This affects wslu 3.x which, when tries to start with a clean environment after upgrade, the terminal will throw `rm: file not found` error. [Test Case] * Install Ubuntu 20.10 to WSL. * run any wslu tools (like wslfetch) * Verify that there is no `rm -rf` error. [Regression Potential] This patch will try to remove ~/.config/wslu/ to order to reset to default state (especially when first upgrade to latest wslu). Potential regressions would be a result of ~/.config/wslu/ not being cleaned properly. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wslu/+bug/1911379/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1910709] Re: DKMS linux-headers-5.8.0-34-generic update brokes nvidia-340
Thank you Dimitri, here is the output: eliseo@eliseo-desktop:~$ dpkg-query -W | grep -e linux -e nvidia binutils-x86-64-linux-gnu 2.34-6ubuntu1 console-setup-linux 1.194ubuntu3 libselinux1:amd64 3.0-1build2 linux-base 4.5ubuntu3.1 linux-firmware 1.187.7 linux-generic-hwe-20.04 5.8.0.36.40~20.04.21 linux-headers-5.4.0-59 5.4.0-59.65 linux-headers-5.4.0-59-generic 5.4.0-59.65 linux-headers-5.8.0-34-generic 5.8.0-34.37~20.04.2 linux-headers-5.8.0-36-generic 5.8.0-36.40~20.04.1 linux-headers-generic-hwe-20.04 5.8.0.36.40~20.04.21 linux-hwe-5.8-headers-5.8.0-34 5.8.0-34.37~20.04.2 linux-hwe-5.8-headers-5.8.0-36 5.8.0-36.40~20.04.1 linux-image-5.4.0-26-generic 5.4.0-26.30 linux-image-5.4.0-33-generic 5.4.0-33.37 linux-image-5.4.0-37-generic 5.4.0-37.41 linux-image-5.4.0-39-generic 5.4.0-39.43 linux-image-5.4.0-40-generic 5.4.0-40.44 linux-image-5.4.0-42-generic 5.4.0-42.46 linux-image-5.4.0-45-generic 5.4.0-45.49 linux-image-5.4.0-47-generic 5.4.0-47.51 linux-image-5.4.0-48-generic 5.4.0-48.52 linux-image-5.4.0-51-generic 5.4.0-51.56 linux-image-5.4.0-52-generic 5.4.0-52.57 linux-image-5.4.0-53-generic 5.4.0-53.59 linux-image-5.4.0-54-generic 5.4.0-54.60 linux-image-5.4.0-56-generic 5.4.0-56.62 linux-image-5.4.0-58-generic 5.4.0-58.64 linux-image-5.4.0-59-generic 5.4.0-59.65 linux-image-5.8.0-34-generic 5.8.0-34.37~20.04.2 linux-image-5.8.0-36-generic 5.8.0-36.40~20.04.1 linux-image-generic-hwe-20.04 5.8.0.36.40~20.04.21 linux-libc-dev:amd64 5.4.0-60.67 linux-modules-5.4.0-26-generic 5.4.0-26.30 linux-modules-5.4.0-33-generic 5.4.0-33.37 linux-modules-5.4.0-37-generic 5.4.0-37.41 linux-modules-5.4.0-39-generic 5.4.0-39.43 linux-modules-5.4.0-40-generic 5.4.0-40.44 linux-modules-5.4.0-42-generic 5.4.0-42.46 linux-modules-5.4.0-45-generic 5.4.0-45.49 linux-modules-5.4.0-47-generic 5.4.0-47.51 linux-modules-5.4.0-48-generic 5.4.0-48.52 linux-modules-5.4.0-51-generic 5.4.0-51.56 linux-modules-5.4.0-52-generic 5.4.0-52.57 linux-modules-5.4.0-53-generic 5.4.0-53.59 linux-modules-5.4.0-54-generic 5.4.0-54.60 linux-modules-5.4.0-56-generic 5.4.0-56.62 linux-modules-5.4.0-58-generic 5.4.0-58.64 linux-modules-5.4.0-59-generic 5.4.0-59.65 linux-modules-5.8.0-34-generic 5.8.0-34.37~20.04.2 linux-modules-5.8.0-36-generic 5.8.0-36.40~20.04.1 linux-modules-extra-5.4.0-26-generic 5.4.0-26.30 linux-modules-extra-5.4.0-33-generic 5.4.0-33.37 linux-modules-extra-5.4.0-37-generic 5.4.0-37.41 linux-modules-extra-5.4.0-39-generic 5.4.0-39.43 linux-modules-extra-5.4.0-40-generic 5.4.0-40.44 linux-modules-extra-5.4.0-42-generic 5.4.0-42.46 linux-modules-extra-5.4.0-45-generic 5.4.0-45.49 linux-modules-extra-5.4.0-47-generic 5.4.0-47.51 linux-modules-extra-5.4.0-48-generic 5.4.0-48.52 linux-modules-extra-5.4.0-51-generic 5.4.0-51.56 linux-modules-extra-5.4.0-52-generic 5.4.0-52.57 linux-modules-extra-5.4.0-53-generic 5.4.0-53.59 linux-modules-extra-5.4.0-54-generic 5.4.0-54.60 linux-modules-extra-5.4.0-56-generic 5.4.0-56.62 linux-modules-extra-5.4.0-58-generic 5.4.0-58.64 linux-modules-extra-5.4.0-59-generic 5.4.0-59.65 linux-modules-extra-5.8.0-34-generic 5.8.0-34.37~20.04.2 linux-modules-extra-5.8.0-36-generic 5.8.0-36.40~20.04.1 linux-sound-base 1.0.25+dfsg-0ubuntu5 nvidia-340 340.108-0ubuntu2 nvidia-opencl-icd-340 340.108-0ubuntu2 nvidia-settings 440.82-0ubuntu0.20.04.1 pptp-linux 1.10.0-1build1 syslinux 3:6.04~git20190206.bf6db5b4+dfsg1-2 syslinux-common 3:6.04~git20190206.bf6db5b4+dfsg1-2 syslinux-legacy 2:3.63+dfsg-2ubuntu9 util-linux 2.34-0.1ubuntu9.1 eliseo@eliseo-desktop:~$ lspci -vvv . 01:00.0 VGA compatible controller: NVIDIA Corporation G98 [GeForce 8400 GS Rev. 2] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ZOTAC International (MCO) Ltd. G98 [GeForce 8400 GS Rev. 2] Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- Kernel driver in use: nvidia Kernel modules: nvidiafb, nouveau, nvidia -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-340 in Ubuntu. https://bugs.launchpad.net/bugs/1910709 Title: DKMS linux-headers-5.8.0-34-generic update brokes nvidia-340 Status in nvidia-graphics-drivers-340 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-340 source package in Focal: Confirmed Bug description: Last linux kernel update "linux-headers-5.8.0-34-generic" broke nvidia-340 driver and Desktop access. In make log: [...] echo >&2; \ echo >&2 " ERROR: Kernel configuration is invalid."; \ echo >&2 " include/generated/autoconf.h or include/config/auto.conf are missing.";\ echo >&2 " Run 'make oldconfig && make prepare' on kernel src to fix it.";\ echo >&2 ; [...] Full DKMS log file attack
[Desktop-packages] [Bug 1627564] Re: Debconf crash due to assertion failure in ensure_surface_for_gicon [gtkiconhelper.c:493] (when png loader is missing/during upgrades)
> OTOH I think there is an easy fix for GTK+ to always include an
"image-missing" icon at compile time
I'm sorry, it's not that easy. A PNG icon is indeed included, and it
gets found properly (also from the actual icon theme; that is a
dependency of GTK). The problem is the ability to load PNGs *at all* is
not available sometimes during the middle of dist-upgrades.
I think extending that test program in Debconf (referred to in the IRC
log above) to do a bit more work - trying to load an icon - might make
the fallback trigger in this case too.
e.g:
my $window = Gtk3::Window->new('toplevel');
my $icontheme = Gtk3::IconTheme::get_default;
my $icon = $icontheme->load_icon('image-missing', 32, []);
If you manually remove '/usr/lib/*/gdk-pixbuf-2.0/2.10.0/loaders.cache'
(suggest doing this in a VM) then you can reproduce this by extracting
the program out of Debconf.
** Changed in: gtk+3.0 (Ubuntu)
Status: New => Invalid
** Changed in: gtk+3.0 (Ubuntu Focal)
Status: New => Invalid
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gtk+3.0 in Ubuntu.
https://bugs.launchpad.net/bugs/1627564
Title:
Debconf crash due to assertion failure in ensure_surface_for_gicon
[gtkiconhelper.c:493] (when png loader is missing/during upgrades)
Status in debconf package in Ubuntu:
Confirmed
Status in gtk+3.0 package in Ubuntu:
Invalid
Status in debconf source package in Focal:
Confirmed
Status in gtk+3.0 source package in Focal:
Invalid
Bug description:
https://errors.ubuntu.com/problem/2b11576fed59ad23c640bc85a266cc82ec30a689
https://errors.ubuntu.com/problem/9d612b3f25168e76adb91fa4eedc301ffa632383
---
bubble opened up indicating there was a failure during the latest
update.
ProblemType: Crash
DistroRelease: Ubuntu 16.10
Package: lightdm-gtk-greeter 2.0.1-2ubuntu4
ProcVersionSignature: Ubuntu 4.8.0-16.17-generic 4.8.0-rc7
Uname: Linux 4.4.0-9136-generic i686
ApportVersion: 2.20.3-0ubuntu7
Architecture: i386
Date: Sun Sep 25 20:37:06 2016
ExecutablePath: /usr/sbin/lightdm-gtk-greeter
InstallationDate: Installed on 2016-08-04 (52 days ago)
InstallationMedia: Lubuntu 16.10 "Yakkety Yak" - Alpha i386 (20160727)
ProcCmdline: /usr/sbin/lightdm-gtk-greeter
ProcEnviron:
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=en_US.UTF-8
SHELL=/bin/false
Signal: 6
SourcePackage: lightdm-gtk-greeter
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:
modified.conffile..etc.lightdm.lightdm-gtk-greeter.conf:
[greeter]
theme-name = Lubuntu-dark-panel
mtime.conffile..etc.lightdm.lightdm-gtk-greeter.conf:
2016-08-14T22:33:57.293011
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/debconf/+bug/1627564/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1910709] Re: DKMS linux-headers-5.8.0-34-generic update brokes nvidia-340
It would be very helpful to know which nvidia card you have and which packages you have installed. Output of something like: dpkg-query -W | grep -e linux -e nvidia and lspci -vvv -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-340 in Ubuntu. https://bugs.launchpad.net/bugs/1910709 Title: DKMS linux-headers-5.8.0-34-generic update brokes nvidia-340 Status in nvidia-graphics-drivers-340 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-340 source package in Focal: Confirmed Bug description: Last linux kernel update "linux-headers-5.8.0-34-generic" broke nvidia-340 driver and Desktop access. In make log: [...] echo >&2; \ echo >&2 " ERROR: Kernel configuration is invalid."; \ echo >&2 " include/generated/autoconf.h or include/config/auto.conf are missing.";\ echo >&2 " Run 'make oldconfig && make prepare' on kernel src to fix it.";\ echo >&2 ; [...] Full DKMS log file attacked. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-11-04 (64 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: Gigabyte Technology Co., Ltd. H81M-D3H NonfreeKernelModules: nvidia Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=es_ES.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-59-generic root=UUID=b0ed05d5-7921-451b-b62c-773b97eeca2f ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-59.65-generic 5.4.78 RelatedPackageVersions: linux-restricted-modules-5.4.0-59-generic N/A linux-backports-modules-5.4.0-59-generic N/A linux-firmware1.187.7 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: focal Uname: Linux 5.4.0-59-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: sudo WifiSyslog: _MarkForUpload: True dmi.bios.date: 01/20/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F2 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H81M-D3H dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF2:bd01/20/2014:svnGigabyteTechnologyCo.,Ltd.:pnH81M-D3H:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnH81M-D3H:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: H81M-D3H dmi.product.sku: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-11-04 (64 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: Gigabyte Technology Co., Ltd. H81M-D3H NonfreeKernelModules: nvidia Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=es_ES.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-59-generic root=UUID=b0ed05d5-7921-451b-b62c-773b97eeca2f ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-59.65-generic 5.4.78 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.4.0-59-generic N/A linux-backports-modules-5.4.0-59-generic N/A linux-firmware1.187.7 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: focal Uname: Linux 5.4.0-59-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 01/20/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F2 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H81M-D3H dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF2:bd01/20/2014:svnGigabyteTechnologyCo.,Ltd.:pnH81M-D3H:pvrTobefilledbyO.E.M
[Desktop-packages] [Bug 1909463] Re: Libreoffice crashed when saving certain documents as docx, doc
Filled upstream bug - https://bugs.documentfoundation.org/show_bug.cgi?id=139580 ** Bug watch added: Document Foundation Bugzilla #139580 https://bugs.documentfoundation.org/show_bug.cgi?id=139580 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1909463 Title: Libreoffice crashed when saving certain documents as docx, doc Status in libreoffice package in Ubuntu: New Bug description: Libreoffice crashed when saving certain documents as docx, doc. test.odt attached. Also tested with libreoffice 7.0.4 from ppa, issue present. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: libreoffice 1:6.4.6-0ubuntu0.20.04.1 ProcVersionSignature: Ubuntu 5.4.0-54.60-generic 5.4.65 Uname: Linux 5.4.0-54-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Dec 28 12:27:55 2020 SourcePackage: libreoffice UpgradeStatus: Upgraded to focal on 2020-05-08 (234 days ago) modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 mtime.conffile..etc.default.apport: 2018-04-04T09:25:22.888039 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1909463/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1911407] Re: desktop UI unresponsive
1. Do you mean logging in or unlocking the screen? 2. After you have logged in, please run: journalctl -b0 > journal.txt lspci -kv > lspci.txt and attach the resulting text files here. ** Changed in: gnome-shell (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1911407 Title: desktop UI unresponsive Status in gnome-shell package in Ubuntu: Incomplete Bug description: Trying to log in screen shows time with seconds hit space bar 8-10 seconds pass before I see log in window I see that gnome-shell spiked my quadcore to 100% ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.4-1ubuntu1~20.04.2 ProcVersionSignature: Ubuntu 5.4.0-60.67-generic 5.4.78 Uname: Linux 5.4.0-60-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Jan 13 11:24:07 2021 DisplayManager: gdm3 InstallationDate: Installed on 2015-08-23 (1969 days ago) InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) RelatedPackageVersions: mutter-common 3.36.7+git20201123-0.20.04.1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to focal on 2021-01-09 (4 days ago) modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 mtime.conffile..etc.default.apport: 2021-01-13T09:36:03.851337 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1911407/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1904793] Re: upower abruptly thinks battery has gone to 1% and hibernates
Thanks! ** Changed in: upower (Ubuntu) Importance: Undecided => Low ** Changed in: upower (Ubuntu) Status: New => Triaged ** Also affects: upower via https://gitlab.freedesktop.org/upower/upower/-/issues/136 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to upower in Ubuntu. https://bugs.launchpad.net/bugs/1904793 Title: upower abruptly thinks battery has gone to 1% and hibernates Status in Upower: Unknown Status in upower package in Ubuntu: Triaged Bug description: Whenever I go on battery after 20-30 minutes upower will very abruptly think my battery is at 1% and force my laptop to hibernate. This seems to happen at random times, I've seen it when my battery was reported to be 90%, 76%, 45%, 25%, etc. If I try to resume Ubuntu locks up forcing me to hard reset the machine. I suspect this is because upower thinks my battery is still at 1% when its not. My laptops firmware correctly reports the battery level and shows that I have plenty of power remaining. The last few times this happened I kept powertop up which shows that I do have plenty of power even when upower thinks I have none. Essentially this makes my laptop unusable on battery. Laptop: Lenovo X1 Carbon Extreme Gen 2 ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: upower 0.99.11-2 ProcVersionSignature: Ubuntu 5.8.0-29.31-generic 5.8.14 Uname: Linux 5.8.0-29-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu50.1 Architecture: amd64 CasperMD5CheckResult: skip Date: Wed Nov 18 13:59:24 2020 InstallationDate: Installed on 2019-12-29 (325 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20191220) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: upower UpgradeStatus: Upgraded to groovy on 2020-10-23 (25 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/upower/+bug/1904793/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1910709] Re: DKMS linux-headers-5.8.0-34-generic update brokes nvidia-340
** Changed in: nvidia-graphics-drivers-340 (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-340 in Ubuntu. https://bugs.launchpad.net/bugs/1910709 Title: DKMS linux-headers-5.8.0-34-generic update brokes nvidia-340 Status in nvidia-graphics-drivers-340 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-340 source package in Focal: Confirmed Bug description: Last linux kernel update "linux-headers-5.8.0-34-generic" broke nvidia-340 driver and Desktop access. In make log: [...] echo >&2; \ echo >&2 " ERROR: Kernel configuration is invalid."; \ echo >&2 " include/generated/autoconf.h or include/config/auto.conf are missing.";\ echo >&2 " Run 'make oldconfig && make prepare' on kernel src to fix it.";\ echo >&2 ; [...] Full DKMS log file attacked. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-11-04 (64 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: Gigabyte Technology Co., Ltd. H81M-D3H NonfreeKernelModules: nvidia Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=es_ES.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-59-generic root=UUID=b0ed05d5-7921-451b-b62c-773b97eeca2f ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-59.65-generic 5.4.78 RelatedPackageVersions: linux-restricted-modules-5.4.0-59-generic N/A linux-backports-modules-5.4.0-59-generic N/A linux-firmware1.187.7 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: focal Uname: Linux 5.4.0-59-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: sudo WifiSyslog: _MarkForUpload: True dmi.bios.date: 01/20/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F2 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H81M-D3H dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF2:bd01/20/2014:svnGigabyteTechnologyCo.,Ltd.:pnH81M-D3H:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnH81M-D3H:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: H81M-D3H dmi.product.sku: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-11-04 (64 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: Gigabyte Technology Co., Ltd. H81M-D3H NonfreeKernelModules: nvidia Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=es_ES.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-59-generic root=UUID=b0ed05d5-7921-451b-b62c-773b97eeca2f ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-59.65-generic 5.4.78 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.4.0-59-generic N/A linux-backports-modules-5.4.0-59-generic N/A linux-firmware1.187.7 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: focal Uname: Linux 5.4.0-59-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 01/20/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F2 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H81M-D3H dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF2:bd01/20/2014:svnGigabyteTechnologyCo.,Ltd.:pnH81M-D3H:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnH81M-D3H:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFil
[Desktop-packages] [Bug 1911407] [NEW] desktop UI unresponsive
Public bug reported: Trying to log in screen shows time with seconds hit space bar 8-10 seconds pass before I see log in window I see that gnome-shell spiked my quadcore to 100% ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.4-1ubuntu1~20.04.2 ProcVersionSignature: Ubuntu 5.4.0-60.67-generic 5.4.78 Uname: Linux 5.4.0-60-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Jan 13 11:24:07 2021 DisplayManager: gdm3 InstallationDate: Installed on 2015-08-23 (1969 days ago) InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) RelatedPackageVersions: mutter-common 3.36.7+git20201123-0.20.04.1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to focal on 2021-01-09 (4 days ago) modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 mtime.conffile..etc.default.apport: 2021-01-13T09:36:03.851337 ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1911407 Title: desktop UI unresponsive Status in gnome-shell package in Ubuntu: New Bug description: Trying to log in screen shows time with seconds hit space bar 8-10 seconds pass before I see log in window I see that gnome-shell spiked my quadcore to 100% ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.4-1ubuntu1~20.04.2 ProcVersionSignature: Ubuntu 5.4.0-60.67-generic 5.4.78 Uname: Linux 5.4.0-60-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Jan 13 11:24:07 2021 DisplayManager: gdm3 InstallationDate: Installed on 2015-08-23 (1969 days ago) InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) RelatedPackageVersions: mutter-common 3.36.7+git20201123-0.20.04.1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to focal on 2021-01-09 (4 days ago) modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 mtime.conffile..etc.default.apport: 2021-01-13T09:36:03.851337 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1911407/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1907121] Re: simple-scan unable to connect scanner HP 2630
I have again the same problem after recent updates.
term.log and history.log of the updates are in attachment
corrado@corrado-x6-hh-1214:~$ simple-scan --debug
[+0,00s] DEBUG: simple-scan.vala:2012: Starting simple-scan 3.38.1, PID=7368
[+0,00s] DEBUG: unsetenv() is not thread-safe and should not be used after
threads are created
[+0,01s] DEBUG: _g_io_module_get_default: Found default implementation dconf
(DConfSettingsBackend) for ‘gsettings-backend’
[+0,03s] DEBUG: app-window.vala:1990: Loading state from
/home/corrado/.cache/simple-scan/state
[+0,03s] DEBUG: app-window.vala:1969: Restoring window to 735x734 pixels
[+0,07s] DEBUG: scanner.vala:1548: sane_init () -> SANE_STATUS_GOOD
[+0,07s] DEBUG: scanner.vala:1554: SANE version 1.0.31
[+0,07s] DEBUG: scanner.vala:1615: Requesting redetection of scan devices
[+0,07s] DEBUG: scanner.vala:828: Processing request
[+0,44s] DEBUG: app-window.vala:2065: Saving state to
/home/corrado/.cache/simple-scan/state
[+7,66s] DEBUG: scanner.vala:341: sane_get_devices () -> SANE_STATUS_GOOD
[+7,66s] DEBUG: scanner.vala:353: Device: name="escl:http://127.0.0.1:6";
vendor="HP" model="DeskJet 2600 series [665032] (USB)" type="flatbed scanner"
[+7,66s] DEBUG: scanner.vala:353: Device:
name="hpaio:/usb/DeskJet_2600_series?serial=CN0569B27006PS"
vendor="Hewlett-Packard" model="DeskJet_2600_series" type="all-in-one"
[+7,98s] DEBUG: app-window.vala:2065: Saving state to
/home/corrado/.cache/simple-scan/state
[+10,77s] DEBUG: simple-scan.vala:1817: Requesting scan at 300 dpi from device
'escl:http://127.0.0.1:6'
[+10,77s] DEBUG: scanner.vala:1683: Scanner.scan
("escl:http://127.0.0.1:6";, dpi=300, scan_mode=ScanMode.COLOR, depth=8,
type=single, paper_width=0, paper_height=0, brightness=0, contrast=0,
delay=3000ms)
[+10,77s] DEBUG: scanner.vala:828: Processing request
[+10,77s] DEBUG: scanner.vala:889: sane_open ("escl:http://127.0.0.1:6";) ->
SANE_STATUS_NO_MEM
[+10,77s] WARNING: scanner.vala:893: Unable to open device: Out of memory
[+11,63s] DEBUG: app-window.vala:2065: Saving state to
/home/corrado/.cache/simple-scan/state
[+258,16s] DEBUG: app-window.vala:2065: Saving state to
/home/corrado/.cache/simple-scan/state
[+263,04s] DEBUG: autosave-manager.vala:201: Deleting autosave records
[+263,04s] DEBUG: scanner.vala:1711: Stopping scan thread
[+263,04s] DEBUG: scanner.vala:828: Processing request
[+263,05s] DEBUG: scanner.vala:1722: sane_exit ()
corrado@corrado-x6-hh-1214:~$
** Attachment added: "logs.zip"
https://bugs.launchpad.net/ubuntu/+source/simple-scan/+bug/1907121/+attachment/5452644/+files/logs.zip
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to simple-scan in Ubuntu.
https://bugs.launchpad.net/bugs/1907121
Title:
simple-scan unable to connect scanner HP 2630
Status in simple-scan package in Ubuntu:
New
Bug description:
simple-scan says: "Ready to scan" but when i click on "scan" it fails to scan
with a message "unable to connect to scanner"
corrado@corrado-x4-focal:~$ scanimage -L
device `hpaio:/usb/DeskJet_2600_series?serial=CN0569B27006PS' is a
Hewlett-Packard DeskJet_2600_series all-in-one
corrado@corrado-x4-focal:~$ apt policy simple-scan
simple-scan:
Installed: 3.36.3-0ubuntu0.20.04.0
Candidate: 3.36.3-0ubuntu0.20.04.0
Version table:
*** 3.36.3-0ubuntu0.20.04.0 500
500 http://archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages
100 /var/lib/dpkg/status
3.36.0-0ubuntu1 500
500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages
corrado@corrado-x4-focal:~$ inxi -Fx
System:Host: corrado-x4-focal Kernel: 5.4.0-56-generic x86_64 bits: 64
compiler: gcc v: 9.3.0 Desktop: Gnome 3.36.4
Distro: Ubuntu 20.04.1 LTS (Focal Fossa)
Machine: Type: Desktop Mobo: ASRock model: H110M-G/M.2 serial:
UEFI: American Megatrends v: P1.10
date: 05/11/2017
CPU: Topology: Dual Core model: Intel Core i3-7100 bits: 64 type: MT
MCP arch: Kaby Lake rev: 9 L2 cache: 3072 KiB
flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
bogomips: 31199
Speed: 801 MHz min/max: 800/3900 MHz Core speeds (MHz): 1: 800 2:
800 3: 800 4: 800
Graphics: Device-1: Intel HD Graphics 630 vendor: ASRock driver: i915 v:
kernel bus ID: 00:02.0
Display: x11 server: X.Org 1.20.8 driver: i915 resolution:
1920x1080~60Hz
OpenGL: renderer: Mesa Intel HD Graphics 630 (KBL GT2) v: 4.6 Mesa
20.0.8 direct render: Yes
Audio: Device-1: Intel 100 Series/C230 Series Family HD Audio vendor:
ASRock driver: snd_hda_intel v: kernel
bus ID: 00:1f.3
Device-2: Logitech QuickCam Pro 9000 type: USB driver:
snd-usb-audio,uvcvideo bus ID: 1-2:3
Sound Server: ALSA v: k5.4.0-56-generic
Network: Device-1: Intel Ethernet I219-V vendor: ASRock driver: e1000e v:
3.2.6-k port: f040 bu
[Desktop-packages] [Bug 1907121] acpidump.txt
apport information ** Attachment added: "acpidump.txt" https://bugs.launchpad.net/bugs/1907121/+attachment/5452638/+files/acpidump.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to simple-scan in Ubuntu. https://bugs.launchpad.net/bugs/1907121 Title: simple-scan unable to connect scanner HP 2630 Status in simple-scan package in Ubuntu: New Bug description: simple-scan says: "Ready to scan" but when i click on "scan" it fails to scan with a message "unable to connect to scanner" corrado@corrado-x4-focal:~$ scanimage -L device `hpaio:/usb/DeskJet_2600_series?serial=CN0569B27006PS' is a Hewlett-Packard DeskJet_2600_series all-in-one corrado@corrado-x4-focal:~$ apt policy simple-scan simple-scan: Installed: 3.36.3-0ubuntu0.20.04.0 Candidate: 3.36.3-0ubuntu0.20.04.0 Version table: *** 3.36.3-0ubuntu0.20.04.0 500 500 http://archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 100 /var/lib/dpkg/status 3.36.0-0ubuntu1 500 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages corrado@corrado-x4-focal:~$ inxi -Fx System:Host: corrado-x4-focal Kernel: 5.4.0-56-generic x86_64 bits: 64 compiler: gcc v: 9.3.0 Desktop: Gnome 3.36.4 Distro: Ubuntu 20.04.1 LTS (Focal Fossa) Machine: Type: Desktop Mobo: ASRock model: H110M-G/M.2 serial: UEFI: American Megatrends v: P1.10 date: 05/11/2017 CPU: Topology: Dual Core model: Intel Core i3-7100 bits: 64 type: MT MCP arch: Kaby Lake rev: 9 L2 cache: 3072 KiB flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 31199 Speed: 801 MHz min/max: 800/3900 MHz Core speeds (MHz): 1: 800 2: 800 3: 800 4: 800 Graphics: Device-1: Intel HD Graphics 630 vendor: ASRock driver: i915 v: kernel bus ID: 00:02.0 Display: x11 server: X.Org 1.20.8 driver: i915 resolution: 1920x1080~60Hz OpenGL: renderer: Mesa Intel HD Graphics 630 (KBL GT2) v: 4.6 Mesa 20.0.8 direct render: Yes Audio: Device-1: Intel 100 Series/C230 Series Family HD Audio vendor: ASRock driver: snd_hda_intel v: kernel bus ID: 00:1f.3 Device-2: Logitech QuickCam Pro 9000 type: USB driver: snd-usb-audio,uvcvideo bus ID: 1-2:3 Sound Server: ALSA v: k5.4.0-56-generic Network: Device-1: Intel Ethernet I219-V vendor: ASRock driver: e1000e v: 3.2.6-k port: f040 bus ID: 00:1f.6 IF: enp0s31f6 state: up speed: 100 Mbps duplex: full mac: 70:85:c2:44:7b:86 Drives:Local Storage: total: 2.05 TiB used: 19.43 GiB (0.9%) ID-1: /dev/nvme0n1 vendor: Kingston model: SKC2000M8250G size: 232.89 GiB ID-2: /dev/sda vendor: Toshiba model: DT01ACA100 size: 931.51 GiB ID-3: /dev/sdb vendor: Hitachi model: HDS721010CLA332 size: 931.51 GiB Partition: ID-1: / size: 31.25 GiB used: 19.42 GiB (62.2%) fs: ext4 dev: /dev/nvme0n1p4 ID-2: swap-1 size: 8.00 GiB used: 0 KiB (0.0%) fs: swap dev: /dev/sda2 Sensors: System Temperatures: cpu: 27.0 C mobo: 31.0 C Fan Speeds (RPM): fan-1: 0 fan-2: 2276 fan-3: 0 fan-4: 2216 fan-5: 0 fan-6: 0 Voltages: 12v: N/A 5v: N/A 3.3v: 3.42 vbat: 3.15 Info: Processes: 227 Uptime: 36m Memory: 7.48 GiB used: 1.59 GiB (21.2%) Init: systemd runlevel: 5 Compilers: gcc: 9.3.0 Shell: bash v: 5.0.17 inxi: 3.0.38 corrado@corrado-x4-focal:~$ ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: simple-scan 3.36.3-0ubuntu0.20.04.0 ProcVersionSignature: Ubuntu 5.4.0-56.62-generic 5.4.73 Uname: Linux 5.4.0-56-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.13 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Dec 7 17:16:02 2020 ExecutablePath: /usr/bin/simple-scan InstallationDate: Installed on 2020-04-29 (222 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-56-generic root=UUID=8a3753b1-5036-49b8-98d8-8b5c3eb01c74 ro quiet splash SimpleScanLog: SourcePackage: simple-scan UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/11/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.10 dmi.board.name: H110M-G/M.2 dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP1.10:bd05/11/2017:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnH110M-G/M.2:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.pr
[Desktop-packages] [Bug 1907121] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1907121/+attachment/5452632/+files/ProcCpuinfo.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to simple-scan in Ubuntu. https://bugs.launchpad.net/bugs/1907121 Title: simple-scan unable to connect scanner HP 2630 Status in simple-scan package in Ubuntu: New Bug description: simple-scan says: "Ready to scan" but when i click on "scan" it fails to scan with a message "unable to connect to scanner" corrado@corrado-x4-focal:~$ scanimage -L device `hpaio:/usb/DeskJet_2600_series?serial=CN0569B27006PS' is a Hewlett-Packard DeskJet_2600_series all-in-one corrado@corrado-x4-focal:~$ apt policy simple-scan simple-scan: Installed: 3.36.3-0ubuntu0.20.04.0 Candidate: 3.36.3-0ubuntu0.20.04.0 Version table: *** 3.36.3-0ubuntu0.20.04.0 500 500 http://archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 100 /var/lib/dpkg/status 3.36.0-0ubuntu1 500 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages corrado@corrado-x4-focal:~$ inxi -Fx System:Host: corrado-x4-focal Kernel: 5.4.0-56-generic x86_64 bits: 64 compiler: gcc v: 9.3.0 Desktop: Gnome 3.36.4 Distro: Ubuntu 20.04.1 LTS (Focal Fossa) Machine: Type: Desktop Mobo: ASRock model: H110M-G/M.2 serial: UEFI: American Megatrends v: P1.10 date: 05/11/2017 CPU: Topology: Dual Core model: Intel Core i3-7100 bits: 64 type: MT MCP arch: Kaby Lake rev: 9 L2 cache: 3072 KiB flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 31199 Speed: 801 MHz min/max: 800/3900 MHz Core speeds (MHz): 1: 800 2: 800 3: 800 4: 800 Graphics: Device-1: Intel HD Graphics 630 vendor: ASRock driver: i915 v: kernel bus ID: 00:02.0 Display: x11 server: X.Org 1.20.8 driver: i915 resolution: 1920x1080~60Hz OpenGL: renderer: Mesa Intel HD Graphics 630 (KBL GT2) v: 4.6 Mesa 20.0.8 direct render: Yes Audio: Device-1: Intel 100 Series/C230 Series Family HD Audio vendor: ASRock driver: snd_hda_intel v: kernel bus ID: 00:1f.3 Device-2: Logitech QuickCam Pro 9000 type: USB driver: snd-usb-audio,uvcvideo bus ID: 1-2:3 Sound Server: ALSA v: k5.4.0-56-generic Network: Device-1: Intel Ethernet I219-V vendor: ASRock driver: e1000e v: 3.2.6-k port: f040 bus ID: 00:1f.6 IF: enp0s31f6 state: up speed: 100 Mbps duplex: full mac: 70:85:c2:44:7b:86 Drives:Local Storage: total: 2.05 TiB used: 19.43 GiB (0.9%) ID-1: /dev/nvme0n1 vendor: Kingston model: SKC2000M8250G size: 232.89 GiB ID-2: /dev/sda vendor: Toshiba model: DT01ACA100 size: 931.51 GiB ID-3: /dev/sdb vendor: Hitachi model: HDS721010CLA332 size: 931.51 GiB Partition: ID-1: / size: 31.25 GiB used: 19.42 GiB (62.2%) fs: ext4 dev: /dev/nvme0n1p4 ID-2: swap-1 size: 8.00 GiB used: 0 KiB (0.0%) fs: swap dev: /dev/sda2 Sensors: System Temperatures: cpu: 27.0 C mobo: 31.0 C Fan Speeds (RPM): fan-1: 0 fan-2: 2276 fan-3: 0 fan-4: 2216 fan-5: 0 fan-6: 0 Voltages: 12v: N/A 5v: N/A 3.3v: 3.42 vbat: 3.15 Info: Processes: 227 Uptime: 36m Memory: 7.48 GiB used: 1.59 GiB (21.2%) Init: systemd runlevel: 5 Compilers: gcc: 9.3.0 Shell: bash v: 5.0.17 inxi: 3.0.38 corrado@corrado-x4-focal:~$ ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: simple-scan 3.36.3-0ubuntu0.20.04.0 ProcVersionSignature: Ubuntu 5.4.0-56.62-generic 5.4.73 Uname: Linux 5.4.0-56-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.13 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Dec 7 17:16:02 2020 ExecutablePath: /usr/bin/simple-scan InstallationDate: Installed on 2020-04-29 (222 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-56-generic root=UUID=8a3753b1-5036-49b8-98d8-8b5c3eb01c74 ro quiet splash SimpleScanLog: SourcePackage: simple-scan UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/11/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.10 dmi.board.name: H110M-G/M.2 dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP1.10:bd05/11/2017:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnH110M-G/M.2:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M.
[Desktop-packages] [Bug 1907121] Dependencies.txt
apport information ** Attachment added: "Dependencies.txt" https://bugs.launchpad.net/bugs/1907121/+attachment/5452625/+files/Dependencies.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to simple-scan in Ubuntu. https://bugs.launchpad.net/bugs/1907121 Title: simple-scan unable to connect scanner HP 2630 Status in simple-scan package in Ubuntu: New Bug description: simple-scan says: "Ready to scan" but when i click on "scan" it fails to scan with a message "unable to connect to scanner" corrado@corrado-x4-focal:~$ scanimage -L device `hpaio:/usb/DeskJet_2600_series?serial=CN0569B27006PS' is a Hewlett-Packard DeskJet_2600_series all-in-one corrado@corrado-x4-focal:~$ apt policy simple-scan simple-scan: Installed: 3.36.3-0ubuntu0.20.04.0 Candidate: 3.36.3-0ubuntu0.20.04.0 Version table: *** 3.36.3-0ubuntu0.20.04.0 500 500 http://archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 100 /var/lib/dpkg/status 3.36.0-0ubuntu1 500 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages corrado@corrado-x4-focal:~$ inxi -Fx System:Host: corrado-x4-focal Kernel: 5.4.0-56-generic x86_64 bits: 64 compiler: gcc v: 9.3.0 Desktop: Gnome 3.36.4 Distro: Ubuntu 20.04.1 LTS (Focal Fossa) Machine: Type: Desktop Mobo: ASRock model: H110M-G/M.2 serial: UEFI: American Megatrends v: P1.10 date: 05/11/2017 CPU: Topology: Dual Core model: Intel Core i3-7100 bits: 64 type: MT MCP arch: Kaby Lake rev: 9 L2 cache: 3072 KiB flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 31199 Speed: 801 MHz min/max: 800/3900 MHz Core speeds (MHz): 1: 800 2: 800 3: 800 4: 800 Graphics: Device-1: Intel HD Graphics 630 vendor: ASRock driver: i915 v: kernel bus ID: 00:02.0 Display: x11 server: X.Org 1.20.8 driver: i915 resolution: 1920x1080~60Hz OpenGL: renderer: Mesa Intel HD Graphics 630 (KBL GT2) v: 4.6 Mesa 20.0.8 direct render: Yes Audio: Device-1: Intel 100 Series/C230 Series Family HD Audio vendor: ASRock driver: snd_hda_intel v: kernel bus ID: 00:1f.3 Device-2: Logitech QuickCam Pro 9000 type: USB driver: snd-usb-audio,uvcvideo bus ID: 1-2:3 Sound Server: ALSA v: k5.4.0-56-generic Network: Device-1: Intel Ethernet I219-V vendor: ASRock driver: e1000e v: 3.2.6-k port: f040 bus ID: 00:1f.6 IF: enp0s31f6 state: up speed: 100 Mbps duplex: full mac: 70:85:c2:44:7b:86 Drives:Local Storage: total: 2.05 TiB used: 19.43 GiB (0.9%) ID-1: /dev/nvme0n1 vendor: Kingston model: SKC2000M8250G size: 232.89 GiB ID-2: /dev/sda vendor: Toshiba model: DT01ACA100 size: 931.51 GiB ID-3: /dev/sdb vendor: Hitachi model: HDS721010CLA332 size: 931.51 GiB Partition: ID-1: / size: 31.25 GiB used: 19.42 GiB (62.2%) fs: ext4 dev: /dev/nvme0n1p4 ID-2: swap-1 size: 8.00 GiB used: 0 KiB (0.0%) fs: swap dev: /dev/sda2 Sensors: System Temperatures: cpu: 27.0 C mobo: 31.0 C Fan Speeds (RPM): fan-1: 0 fan-2: 2276 fan-3: 0 fan-4: 2216 fan-5: 0 fan-6: 0 Voltages: 12v: N/A 5v: N/A 3.3v: 3.42 vbat: 3.15 Info: Processes: 227 Uptime: 36m Memory: 7.48 GiB used: 1.59 GiB (21.2%) Init: systemd runlevel: 5 Compilers: gcc: 9.3.0 Shell: bash v: 5.0.17 inxi: 3.0.38 corrado@corrado-x4-focal:~$ ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: simple-scan 3.36.3-0ubuntu0.20.04.0 ProcVersionSignature: Ubuntu 5.4.0-56.62-generic 5.4.73 Uname: Linux 5.4.0-56-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.13 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Dec 7 17:16:02 2020 ExecutablePath: /usr/bin/simple-scan InstallationDate: Installed on 2020-04-29 (222 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-56-generic root=UUID=8a3753b1-5036-49b8-98d8-8b5c3eb01c74 ro quiet splash SimpleScanLog: SourcePackage: simple-scan UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/11/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.10 dmi.board.name: H110M-G/M.2 dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP1.10:bd05/11/2017:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnH110M-G/M.2:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M.
[Desktop-packages] [Bug 1907121] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1907121/+attachment/5452634/+files/ProcEnviron.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to simple-scan in Ubuntu. https://bugs.launchpad.net/bugs/1907121 Title: simple-scan unable to connect scanner HP 2630 Status in simple-scan package in Ubuntu: New Bug description: simple-scan says: "Ready to scan" but when i click on "scan" it fails to scan with a message "unable to connect to scanner" corrado@corrado-x4-focal:~$ scanimage -L device `hpaio:/usb/DeskJet_2600_series?serial=CN0569B27006PS' is a Hewlett-Packard DeskJet_2600_series all-in-one corrado@corrado-x4-focal:~$ apt policy simple-scan simple-scan: Installed: 3.36.3-0ubuntu0.20.04.0 Candidate: 3.36.3-0ubuntu0.20.04.0 Version table: *** 3.36.3-0ubuntu0.20.04.0 500 500 http://archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 100 /var/lib/dpkg/status 3.36.0-0ubuntu1 500 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages corrado@corrado-x4-focal:~$ inxi -Fx System:Host: corrado-x4-focal Kernel: 5.4.0-56-generic x86_64 bits: 64 compiler: gcc v: 9.3.0 Desktop: Gnome 3.36.4 Distro: Ubuntu 20.04.1 LTS (Focal Fossa) Machine: Type: Desktop Mobo: ASRock model: H110M-G/M.2 serial: UEFI: American Megatrends v: P1.10 date: 05/11/2017 CPU: Topology: Dual Core model: Intel Core i3-7100 bits: 64 type: MT MCP arch: Kaby Lake rev: 9 L2 cache: 3072 KiB flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 31199 Speed: 801 MHz min/max: 800/3900 MHz Core speeds (MHz): 1: 800 2: 800 3: 800 4: 800 Graphics: Device-1: Intel HD Graphics 630 vendor: ASRock driver: i915 v: kernel bus ID: 00:02.0 Display: x11 server: X.Org 1.20.8 driver: i915 resolution: 1920x1080~60Hz OpenGL: renderer: Mesa Intel HD Graphics 630 (KBL GT2) v: 4.6 Mesa 20.0.8 direct render: Yes Audio: Device-1: Intel 100 Series/C230 Series Family HD Audio vendor: ASRock driver: snd_hda_intel v: kernel bus ID: 00:1f.3 Device-2: Logitech QuickCam Pro 9000 type: USB driver: snd-usb-audio,uvcvideo bus ID: 1-2:3 Sound Server: ALSA v: k5.4.0-56-generic Network: Device-1: Intel Ethernet I219-V vendor: ASRock driver: e1000e v: 3.2.6-k port: f040 bus ID: 00:1f.6 IF: enp0s31f6 state: up speed: 100 Mbps duplex: full mac: 70:85:c2:44:7b:86 Drives:Local Storage: total: 2.05 TiB used: 19.43 GiB (0.9%) ID-1: /dev/nvme0n1 vendor: Kingston model: SKC2000M8250G size: 232.89 GiB ID-2: /dev/sda vendor: Toshiba model: DT01ACA100 size: 931.51 GiB ID-3: /dev/sdb vendor: Hitachi model: HDS721010CLA332 size: 931.51 GiB Partition: ID-1: / size: 31.25 GiB used: 19.42 GiB (62.2%) fs: ext4 dev: /dev/nvme0n1p4 ID-2: swap-1 size: 8.00 GiB used: 0 KiB (0.0%) fs: swap dev: /dev/sda2 Sensors: System Temperatures: cpu: 27.0 C mobo: 31.0 C Fan Speeds (RPM): fan-1: 0 fan-2: 2276 fan-3: 0 fan-4: 2216 fan-5: 0 fan-6: 0 Voltages: 12v: N/A 5v: N/A 3.3v: 3.42 vbat: 3.15 Info: Processes: 227 Uptime: 36m Memory: 7.48 GiB used: 1.59 GiB (21.2%) Init: systemd runlevel: 5 Compilers: gcc: 9.3.0 Shell: bash v: 5.0.17 inxi: 3.0.38 corrado@corrado-x4-focal:~$ ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: simple-scan 3.36.3-0ubuntu0.20.04.0 ProcVersionSignature: Ubuntu 5.4.0-56.62-generic 5.4.73 Uname: Linux 5.4.0-56-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.13 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Dec 7 17:16:02 2020 ExecutablePath: /usr/bin/simple-scan InstallationDate: Installed on 2020-04-29 (222 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-56-generic root=UUID=8a3753b1-5036-49b8-98d8-8b5c3eb01c74 ro quiet splash SimpleScanLog: SourcePackage: simple-scan UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/11/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.10 dmi.board.name: H110M-G/M.2 dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP1.10:bd05/11/2017:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnH110M-G/M.2:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M.
[Desktop-packages] [Bug 1907121] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1907121/+attachment/5452635/+files/ProcInterrupts.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to simple-scan in Ubuntu. https://bugs.launchpad.net/bugs/1907121 Title: simple-scan unable to connect scanner HP 2630 Status in simple-scan package in Ubuntu: New Bug description: simple-scan says: "Ready to scan" but when i click on "scan" it fails to scan with a message "unable to connect to scanner" corrado@corrado-x4-focal:~$ scanimage -L device `hpaio:/usb/DeskJet_2600_series?serial=CN0569B27006PS' is a Hewlett-Packard DeskJet_2600_series all-in-one corrado@corrado-x4-focal:~$ apt policy simple-scan simple-scan: Installed: 3.36.3-0ubuntu0.20.04.0 Candidate: 3.36.3-0ubuntu0.20.04.0 Version table: *** 3.36.3-0ubuntu0.20.04.0 500 500 http://archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 100 /var/lib/dpkg/status 3.36.0-0ubuntu1 500 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages corrado@corrado-x4-focal:~$ inxi -Fx System:Host: corrado-x4-focal Kernel: 5.4.0-56-generic x86_64 bits: 64 compiler: gcc v: 9.3.0 Desktop: Gnome 3.36.4 Distro: Ubuntu 20.04.1 LTS (Focal Fossa) Machine: Type: Desktop Mobo: ASRock model: H110M-G/M.2 serial: UEFI: American Megatrends v: P1.10 date: 05/11/2017 CPU: Topology: Dual Core model: Intel Core i3-7100 bits: 64 type: MT MCP arch: Kaby Lake rev: 9 L2 cache: 3072 KiB flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 31199 Speed: 801 MHz min/max: 800/3900 MHz Core speeds (MHz): 1: 800 2: 800 3: 800 4: 800 Graphics: Device-1: Intel HD Graphics 630 vendor: ASRock driver: i915 v: kernel bus ID: 00:02.0 Display: x11 server: X.Org 1.20.8 driver: i915 resolution: 1920x1080~60Hz OpenGL: renderer: Mesa Intel HD Graphics 630 (KBL GT2) v: 4.6 Mesa 20.0.8 direct render: Yes Audio: Device-1: Intel 100 Series/C230 Series Family HD Audio vendor: ASRock driver: snd_hda_intel v: kernel bus ID: 00:1f.3 Device-2: Logitech QuickCam Pro 9000 type: USB driver: snd-usb-audio,uvcvideo bus ID: 1-2:3 Sound Server: ALSA v: k5.4.0-56-generic Network: Device-1: Intel Ethernet I219-V vendor: ASRock driver: e1000e v: 3.2.6-k port: f040 bus ID: 00:1f.6 IF: enp0s31f6 state: up speed: 100 Mbps duplex: full mac: 70:85:c2:44:7b:86 Drives:Local Storage: total: 2.05 TiB used: 19.43 GiB (0.9%) ID-1: /dev/nvme0n1 vendor: Kingston model: SKC2000M8250G size: 232.89 GiB ID-2: /dev/sda vendor: Toshiba model: DT01ACA100 size: 931.51 GiB ID-3: /dev/sdb vendor: Hitachi model: HDS721010CLA332 size: 931.51 GiB Partition: ID-1: / size: 31.25 GiB used: 19.42 GiB (62.2%) fs: ext4 dev: /dev/nvme0n1p4 ID-2: swap-1 size: 8.00 GiB used: 0 KiB (0.0%) fs: swap dev: /dev/sda2 Sensors: System Temperatures: cpu: 27.0 C mobo: 31.0 C Fan Speeds (RPM): fan-1: 0 fan-2: 2276 fan-3: 0 fan-4: 2216 fan-5: 0 fan-6: 0 Voltages: 12v: N/A 5v: N/A 3.3v: 3.42 vbat: 3.15 Info: Processes: 227 Uptime: 36m Memory: 7.48 GiB used: 1.59 GiB (21.2%) Init: systemd runlevel: 5 Compilers: gcc: 9.3.0 Shell: bash v: 5.0.17 inxi: 3.0.38 corrado@corrado-x4-focal:~$ ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: simple-scan 3.36.3-0ubuntu0.20.04.0 ProcVersionSignature: Ubuntu 5.4.0-56.62-generic 5.4.73 Uname: Linux 5.4.0-56-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.13 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Dec 7 17:16:02 2020 ExecutablePath: /usr/bin/simple-scan InstallationDate: Installed on 2020-04-29 (222 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-56-generic root=UUID=8a3753b1-5036-49b8-98d8-8b5c3eb01c74 ro quiet splash SimpleScanLog: SourcePackage: simple-scan UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/11/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.10 dmi.board.name: H110M-G/M.2 dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP1.10:bd05/11/2017:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnH110M-G/M.2:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E
[Desktop-packages] [Bug 1907121] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1907121/+attachment/5452629/+files/Lsusb.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to simple-scan in Ubuntu. https://bugs.launchpad.net/bugs/1907121 Title: simple-scan unable to connect scanner HP 2630 Status in simple-scan package in Ubuntu: New Bug description: simple-scan says: "Ready to scan" but when i click on "scan" it fails to scan with a message "unable to connect to scanner" corrado@corrado-x4-focal:~$ scanimage -L device `hpaio:/usb/DeskJet_2600_series?serial=CN0569B27006PS' is a Hewlett-Packard DeskJet_2600_series all-in-one corrado@corrado-x4-focal:~$ apt policy simple-scan simple-scan: Installed: 3.36.3-0ubuntu0.20.04.0 Candidate: 3.36.3-0ubuntu0.20.04.0 Version table: *** 3.36.3-0ubuntu0.20.04.0 500 500 http://archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 100 /var/lib/dpkg/status 3.36.0-0ubuntu1 500 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages corrado@corrado-x4-focal:~$ inxi -Fx System:Host: corrado-x4-focal Kernel: 5.4.0-56-generic x86_64 bits: 64 compiler: gcc v: 9.3.0 Desktop: Gnome 3.36.4 Distro: Ubuntu 20.04.1 LTS (Focal Fossa) Machine: Type: Desktop Mobo: ASRock model: H110M-G/M.2 serial: UEFI: American Megatrends v: P1.10 date: 05/11/2017 CPU: Topology: Dual Core model: Intel Core i3-7100 bits: 64 type: MT MCP arch: Kaby Lake rev: 9 L2 cache: 3072 KiB flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 31199 Speed: 801 MHz min/max: 800/3900 MHz Core speeds (MHz): 1: 800 2: 800 3: 800 4: 800 Graphics: Device-1: Intel HD Graphics 630 vendor: ASRock driver: i915 v: kernel bus ID: 00:02.0 Display: x11 server: X.Org 1.20.8 driver: i915 resolution: 1920x1080~60Hz OpenGL: renderer: Mesa Intel HD Graphics 630 (KBL GT2) v: 4.6 Mesa 20.0.8 direct render: Yes Audio: Device-1: Intel 100 Series/C230 Series Family HD Audio vendor: ASRock driver: snd_hda_intel v: kernel bus ID: 00:1f.3 Device-2: Logitech QuickCam Pro 9000 type: USB driver: snd-usb-audio,uvcvideo bus ID: 1-2:3 Sound Server: ALSA v: k5.4.0-56-generic Network: Device-1: Intel Ethernet I219-V vendor: ASRock driver: e1000e v: 3.2.6-k port: f040 bus ID: 00:1f.6 IF: enp0s31f6 state: up speed: 100 Mbps duplex: full mac: 70:85:c2:44:7b:86 Drives:Local Storage: total: 2.05 TiB used: 19.43 GiB (0.9%) ID-1: /dev/nvme0n1 vendor: Kingston model: SKC2000M8250G size: 232.89 GiB ID-2: /dev/sda vendor: Toshiba model: DT01ACA100 size: 931.51 GiB ID-3: /dev/sdb vendor: Hitachi model: HDS721010CLA332 size: 931.51 GiB Partition: ID-1: / size: 31.25 GiB used: 19.42 GiB (62.2%) fs: ext4 dev: /dev/nvme0n1p4 ID-2: swap-1 size: 8.00 GiB used: 0 KiB (0.0%) fs: swap dev: /dev/sda2 Sensors: System Temperatures: cpu: 27.0 C mobo: 31.0 C Fan Speeds (RPM): fan-1: 0 fan-2: 2276 fan-3: 0 fan-4: 2216 fan-5: 0 fan-6: 0 Voltages: 12v: N/A 5v: N/A 3.3v: 3.42 vbat: 3.15 Info: Processes: 227 Uptime: 36m Memory: 7.48 GiB used: 1.59 GiB (21.2%) Init: systemd runlevel: 5 Compilers: gcc: 9.3.0 Shell: bash v: 5.0.17 inxi: 3.0.38 corrado@corrado-x4-focal:~$ ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: simple-scan 3.36.3-0ubuntu0.20.04.0 ProcVersionSignature: Ubuntu 5.4.0-56.62-generic 5.4.73 Uname: Linux 5.4.0-56-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.13 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Dec 7 17:16:02 2020 ExecutablePath: /usr/bin/simple-scan InstallationDate: Installed on 2020-04-29 (222 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-56-generic root=UUID=8a3753b1-5036-49b8-98d8-8b5c3eb01c74 ro quiet splash SimpleScanLog: SourcePackage: simple-scan UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/11/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.10 dmi.board.name: H110M-G/M.2 dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP1.10:bd05/11/2017:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnH110M-G/M.2:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.s
[Desktop-packages] [Bug 1907121] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1907121/+attachment/5452637/+files/UdevDb.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to simple-scan in Ubuntu. https://bugs.launchpad.net/bugs/1907121 Title: simple-scan unable to connect scanner HP 2630 Status in simple-scan package in Ubuntu: New Bug description: simple-scan says: "Ready to scan" but when i click on "scan" it fails to scan with a message "unable to connect to scanner" corrado@corrado-x4-focal:~$ scanimage -L device `hpaio:/usb/DeskJet_2600_series?serial=CN0569B27006PS' is a Hewlett-Packard DeskJet_2600_series all-in-one corrado@corrado-x4-focal:~$ apt policy simple-scan simple-scan: Installed: 3.36.3-0ubuntu0.20.04.0 Candidate: 3.36.3-0ubuntu0.20.04.0 Version table: *** 3.36.3-0ubuntu0.20.04.0 500 500 http://archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 100 /var/lib/dpkg/status 3.36.0-0ubuntu1 500 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages corrado@corrado-x4-focal:~$ inxi -Fx System:Host: corrado-x4-focal Kernel: 5.4.0-56-generic x86_64 bits: 64 compiler: gcc v: 9.3.0 Desktop: Gnome 3.36.4 Distro: Ubuntu 20.04.1 LTS (Focal Fossa) Machine: Type: Desktop Mobo: ASRock model: H110M-G/M.2 serial: UEFI: American Megatrends v: P1.10 date: 05/11/2017 CPU: Topology: Dual Core model: Intel Core i3-7100 bits: 64 type: MT MCP arch: Kaby Lake rev: 9 L2 cache: 3072 KiB flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 31199 Speed: 801 MHz min/max: 800/3900 MHz Core speeds (MHz): 1: 800 2: 800 3: 800 4: 800 Graphics: Device-1: Intel HD Graphics 630 vendor: ASRock driver: i915 v: kernel bus ID: 00:02.0 Display: x11 server: X.Org 1.20.8 driver: i915 resolution: 1920x1080~60Hz OpenGL: renderer: Mesa Intel HD Graphics 630 (KBL GT2) v: 4.6 Mesa 20.0.8 direct render: Yes Audio: Device-1: Intel 100 Series/C230 Series Family HD Audio vendor: ASRock driver: snd_hda_intel v: kernel bus ID: 00:1f.3 Device-2: Logitech QuickCam Pro 9000 type: USB driver: snd-usb-audio,uvcvideo bus ID: 1-2:3 Sound Server: ALSA v: k5.4.0-56-generic Network: Device-1: Intel Ethernet I219-V vendor: ASRock driver: e1000e v: 3.2.6-k port: f040 bus ID: 00:1f.6 IF: enp0s31f6 state: up speed: 100 Mbps duplex: full mac: 70:85:c2:44:7b:86 Drives:Local Storage: total: 2.05 TiB used: 19.43 GiB (0.9%) ID-1: /dev/nvme0n1 vendor: Kingston model: SKC2000M8250G size: 232.89 GiB ID-2: /dev/sda vendor: Toshiba model: DT01ACA100 size: 931.51 GiB ID-3: /dev/sdb vendor: Hitachi model: HDS721010CLA332 size: 931.51 GiB Partition: ID-1: / size: 31.25 GiB used: 19.42 GiB (62.2%) fs: ext4 dev: /dev/nvme0n1p4 ID-2: swap-1 size: 8.00 GiB used: 0 KiB (0.0%) fs: swap dev: /dev/sda2 Sensors: System Temperatures: cpu: 27.0 C mobo: 31.0 C Fan Speeds (RPM): fan-1: 0 fan-2: 2276 fan-3: 0 fan-4: 2216 fan-5: 0 fan-6: 0 Voltages: 12v: N/A 5v: N/A 3.3v: 3.42 vbat: 3.15 Info: Processes: 227 Uptime: 36m Memory: 7.48 GiB used: 1.59 GiB (21.2%) Init: systemd runlevel: 5 Compilers: gcc: 9.3.0 Shell: bash v: 5.0.17 inxi: 3.0.38 corrado@corrado-x4-focal:~$ ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: simple-scan 3.36.3-0ubuntu0.20.04.0 ProcVersionSignature: Ubuntu 5.4.0-56.62-generic 5.4.73 Uname: Linux 5.4.0-56-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.13 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Dec 7 17:16:02 2020 ExecutablePath: /usr/bin/simple-scan InstallationDate: Installed on 2020-04-29 (222 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-56-generic root=UUID=8a3753b1-5036-49b8-98d8-8b5c3eb01c74 ro quiet splash SimpleScanLog: SourcePackage: simple-scan UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/11/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.10 dmi.board.name: H110M-G/M.2 dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP1.10:bd05/11/2017:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnH110M-G/M.2:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product
[Desktop-packages] [Bug 1907121] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1907121/+attachment/5452633/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to simple-scan in Ubuntu. https://bugs.launchpad.net/bugs/1907121 Title: simple-scan unable to connect scanner HP 2630 Status in simple-scan package in Ubuntu: New Bug description: simple-scan says: "Ready to scan" but when i click on "scan" it fails to scan with a message "unable to connect to scanner" corrado@corrado-x4-focal:~$ scanimage -L device `hpaio:/usb/DeskJet_2600_series?serial=CN0569B27006PS' is a Hewlett-Packard DeskJet_2600_series all-in-one corrado@corrado-x4-focal:~$ apt policy simple-scan simple-scan: Installed: 3.36.3-0ubuntu0.20.04.0 Candidate: 3.36.3-0ubuntu0.20.04.0 Version table: *** 3.36.3-0ubuntu0.20.04.0 500 500 http://archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 100 /var/lib/dpkg/status 3.36.0-0ubuntu1 500 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages corrado@corrado-x4-focal:~$ inxi -Fx System:Host: corrado-x4-focal Kernel: 5.4.0-56-generic x86_64 bits: 64 compiler: gcc v: 9.3.0 Desktop: Gnome 3.36.4 Distro: Ubuntu 20.04.1 LTS (Focal Fossa) Machine: Type: Desktop Mobo: ASRock model: H110M-G/M.2 serial: UEFI: American Megatrends v: P1.10 date: 05/11/2017 CPU: Topology: Dual Core model: Intel Core i3-7100 bits: 64 type: MT MCP arch: Kaby Lake rev: 9 L2 cache: 3072 KiB flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 31199 Speed: 801 MHz min/max: 800/3900 MHz Core speeds (MHz): 1: 800 2: 800 3: 800 4: 800 Graphics: Device-1: Intel HD Graphics 630 vendor: ASRock driver: i915 v: kernel bus ID: 00:02.0 Display: x11 server: X.Org 1.20.8 driver: i915 resolution: 1920x1080~60Hz OpenGL: renderer: Mesa Intel HD Graphics 630 (KBL GT2) v: 4.6 Mesa 20.0.8 direct render: Yes Audio: Device-1: Intel 100 Series/C230 Series Family HD Audio vendor: ASRock driver: snd_hda_intel v: kernel bus ID: 00:1f.3 Device-2: Logitech QuickCam Pro 9000 type: USB driver: snd-usb-audio,uvcvideo bus ID: 1-2:3 Sound Server: ALSA v: k5.4.0-56-generic Network: Device-1: Intel Ethernet I219-V vendor: ASRock driver: e1000e v: 3.2.6-k port: f040 bus ID: 00:1f.6 IF: enp0s31f6 state: up speed: 100 Mbps duplex: full mac: 70:85:c2:44:7b:86 Drives:Local Storage: total: 2.05 TiB used: 19.43 GiB (0.9%) ID-1: /dev/nvme0n1 vendor: Kingston model: SKC2000M8250G size: 232.89 GiB ID-2: /dev/sda vendor: Toshiba model: DT01ACA100 size: 931.51 GiB ID-3: /dev/sdb vendor: Hitachi model: HDS721010CLA332 size: 931.51 GiB Partition: ID-1: / size: 31.25 GiB used: 19.42 GiB (62.2%) fs: ext4 dev: /dev/nvme0n1p4 ID-2: swap-1 size: 8.00 GiB used: 0 KiB (0.0%) fs: swap dev: /dev/sda2 Sensors: System Temperatures: cpu: 27.0 C mobo: 31.0 C Fan Speeds (RPM): fan-1: 0 fan-2: 2276 fan-3: 0 fan-4: 2216 fan-5: 0 fan-6: 0 Voltages: 12v: N/A 5v: N/A 3.3v: 3.42 vbat: 3.15 Info: Processes: 227 Uptime: 36m Memory: 7.48 GiB used: 1.59 GiB (21.2%) Init: systemd runlevel: 5 Compilers: gcc: 9.3.0 Shell: bash v: 5.0.17 inxi: 3.0.38 corrado@corrado-x4-focal:~$ ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: simple-scan 3.36.3-0ubuntu0.20.04.0 ProcVersionSignature: Ubuntu 5.4.0-56.62-generic 5.4.73 Uname: Linux 5.4.0-56-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.13 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Dec 7 17:16:02 2020 ExecutablePath: /usr/bin/simple-scan InstallationDate: Installed on 2020-04-29 (222 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-56-generic root=UUID=8a3753b1-5036-49b8-98d8-8b5c3eb01c74 ro quiet splash SimpleScanLog: SourcePackage: simple-scan UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/11/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.10 dmi.board.name: H110M-G/M.2 dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP1.10:bd05/11/2017:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnH110M-G/M.2:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Fille
[Desktop-packages] [Bug 1907121] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1907121/+attachment/5452636/+files/ProcModules.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to simple-scan in Ubuntu. https://bugs.launchpad.net/bugs/1907121 Title: simple-scan unable to connect scanner HP 2630 Status in simple-scan package in Ubuntu: New Bug description: simple-scan says: "Ready to scan" but when i click on "scan" it fails to scan with a message "unable to connect to scanner" corrado@corrado-x4-focal:~$ scanimage -L device `hpaio:/usb/DeskJet_2600_series?serial=CN0569B27006PS' is a Hewlett-Packard DeskJet_2600_series all-in-one corrado@corrado-x4-focal:~$ apt policy simple-scan simple-scan: Installed: 3.36.3-0ubuntu0.20.04.0 Candidate: 3.36.3-0ubuntu0.20.04.0 Version table: *** 3.36.3-0ubuntu0.20.04.0 500 500 http://archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 100 /var/lib/dpkg/status 3.36.0-0ubuntu1 500 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages corrado@corrado-x4-focal:~$ inxi -Fx System:Host: corrado-x4-focal Kernel: 5.4.0-56-generic x86_64 bits: 64 compiler: gcc v: 9.3.0 Desktop: Gnome 3.36.4 Distro: Ubuntu 20.04.1 LTS (Focal Fossa) Machine: Type: Desktop Mobo: ASRock model: H110M-G/M.2 serial: UEFI: American Megatrends v: P1.10 date: 05/11/2017 CPU: Topology: Dual Core model: Intel Core i3-7100 bits: 64 type: MT MCP arch: Kaby Lake rev: 9 L2 cache: 3072 KiB flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 31199 Speed: 801 MHz min/max: 800/3900 MHz Core speeds (MHz): 1: 800 2: 800 3: 800 4: 800 Graphics: Device-1: Intel HD Graphics 630 vendor: ASRock driver: i915 v: kernel bus ID: 00:02.0 Display: x11 server: X.Org 1.20.8 driver: i915 resolution: 1920x1080~60Hz OpenGL: renderer: Mesa Intel HD Graphics 630 (KBL GT2) v: 4.6 Mesa 20.0.8 direct render: Yes Audio: Device-1: Intel 100 Series/C230 Series Family HD Audio vendor: ASRock driver: snd_hda_intel v: kernel bus ID: 00:1f.3 Device-2: Logitech QuickCam Pro 9000 type: USB driver: snd-usb-audio,uvcvideo bus ID: 1-2:3 Sound Server: ALSA v: k5.4.0-56-generic Network: Device-1: Intel Ethernet I219-V vendor: ASRock driver: e1000e v: 3.2.6-k port: f040 bus ID: 00:1f.6 IF: enp0s31f6 state: up speed: 100 Mbps duplex: full mac: 70:85:c2:44:7b:86 Drives:Local Storage: total: 2.05 TiB used: 19.43 GiB (0.9%) ID-1: /dev/nvme0n1 vendor: Kingston model: SKC2000M8250G size: 232.89 GiB ID-2: /dev/sda vendor: Toshiba model: DT01ACA100 size: 931.51 GiB ID-3: /dev/sdb vendor: Hitachi model: HDS721010CLA332 size: 931.51 GiB Partition: ID-1: / size: 31.25 GiB used: 19.42 GiB (62.2%) fs: ext4 dev: /dev/nvme0n1p4 ID-2: swap-1 size: 8.00 GiB used: 0 KiB (0.0%) fs: swap dev: /dev/sda2 Sensors: System Temperatures: cpu: 27.0 C mobo: 31.0 C Fan Speeds (RPM): fan-1: 0 fan-2: 2276 fan-3: 0 fan-4: 2216 fan-5: 0 fan-6: 0 Voltages: 12v: N/A 5v: N/A 3.3v: 3.42 vbat: 3.15 Info: Processes: 227 Uptime: 36m Memory: 7.48 GiB used: 1.59 GiB (21.2%) Init: systemd runlevel: 5 Compilers: gcc: 9.3.0 Shell: bash v: 5.0.17 inxi: 3.0.38 corrado@corrado-x4-focal:~$ ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: simple-scan 3.36.3-0ubuntu0.20.04.0 ProcVersionSignature: Ubuntu 5.4.0-56.62-generic 5.4.73 Uname: Linux 5.4.0-56-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.13 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Dec 7 17:16:02 2020 ExecutablePath: /usr/bin/simple-scan InstallationDate: Installed on 2020-04-29 (222 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-56-generic root=UUID=8a3753b1-5036-49b8-98d8-8b5c3eb01c74 ro quiet splash SimpleScanLog: SourcePackage: simple-scan UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/11/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.10 dmi.board.name: H110M-G/M.2 dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP1.10:bd05/11/2017:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnH110M-G/M.2:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M.
[Desktop-packages] [Bug 1907121] Lsusb-v.txt
apport information ** Attachment added: "Lsusb-v.txt" https://bugs.launchpad.net/bugs/1907121/+attachment/5452631/+files/Lsusb-v.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to simple-scan in Ubuntu. https://bugs.launchpad.net/bugs/1907121 Title: simple-scan unable to connect scanner HP 2630 Status in simple-scan package in Ubuntu: New Bug description: simple-scan says: "Ready to scan" but when i click on "scan" it fails to scan with a message "unable to connect to scanner" corrado@corrado-x4-focal:~$ scanimage -L device `hpaio:/usb/DeskJet_2600_series?serial=CN0569B27006PS' is a Hewlett-Packard DeskJet_2600_series all-in-one corrado@corrado-x4-focal:~$ apt policy simple-scan simple-scan: Installed: 3.36.3-0ubuntu0.20.04.0 Candidate: 3.36.3-0ubuntu0.20.04.0 Version table: *** 3.36.3-0ubuntu0.20.04.0 500 500 http://archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 100 /var/lib/dpkg/status 3.36.0-0ubuntu1 500 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages corrado@corrado-x4-focal:~$ inxi -Fx System:Host: corrado-x4-focal Kernel: 5.4.0-56-generic x86_64 bits: 64 compiler: gcc v: 9.3.0 Desktop: Gnome 3.36.4 Distro: Ubuntu 20.04.1 LTS (Focal Fossa) Machine: Type: Desktop Mobo: ASRock model: H110M-G/M.2 serial: UEFI: American Megatrends v: P1.10 date: 05/11/2017 CPU: Topology: Dual Core model: Intel Core i3-7100 bits: 64 type: MT MCP arch: Kaby Lake rev: 9 L2 cache: 3072 KiB flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 31199 Speed: 801 MHz min/max: 800/3900 MHz Core speeds (MHz): 1: 800 2: 800 3: 800 4: 800 Graphics: Device-1: Intel HD Graphics 630 vendor: ASRock driver: i915 v: kernel bus ID: 00:02.0 Display: x11 server: X.Org 1.20.8 driver: i915 resolution: 1920x1080~60Hz OpenGL: renderer: Mesa Intel HD Graphics 630 (KBL GT2) v: 4.6 Mesa 20.0.8 direct render: Yes Audio: Device-1: Intel 100 Series/C230 Series Family HD Audio vendor: ASRock driver: snd_hda_intel v: kernel bus ID: 00:1f.3 Device-2: Logitech QuickCam Pro 9000 type: USB driver: snd-usb-audio,uvcvideo bus ID: 1-2:3 Sound Server: ALSA v: k5.4.0-56-generic Network: Device-1: Intel Ethernet I219-V vendor: ASRock driver: e1000e v: 3.2.6-k port: f040 bus ID: 00:1f.6 IF: enp0s31f6 state: up speed: 100 Mbps duplex: full mac: 70:85:c2:44:7b:86 Drives:Local Storage: total: 2.05 TiB used: 19.43 GiB (0.9%) ID-1: /dev/nvme0n1 vendor: Kingston model: SKC2000M8250G size: 232.89 GiB ID-2: /dev/sda vendor: Toshiba model: DT01ACA100 size: 931.51 GiB ID-3: /dev/sdb vendor: Hitachi model: HDS721010CLA332 size: 931.51 GiB Partition: ID-1: / size: 31.25 GiB used: 19.42 GiB (62.2%) fs: ext4 dev: /dev/nvme0n1p4 ID-2: swap-1 size: 8.00 GiB used: 0 KiB (0.0%) fs: swap dev: /dev/sda2 Sensors: System Temperatures: cpu: 27.0 C mobo: 31.0 C Fan Speeds (RPM): fan-1: 0 fan-2: 2276 fan-3: 0 fan-4: 2216 fan-5: 0 fan-6: 0 Voltages: 12v: N/A 5v: N/A 3.3v: 3.42 vbat: 3.15 Info: Processes: 227 Uptime: 36m Memory: 7.48 GiB used: 1.59 GiB (21.2%) Init: systemd runlevel: 5 Compilers: gcc: 9.3.0 Shell: bash v: 5.0.17 inxi: 3.0.38 corrado@corrado-x4-focal:~$ ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: simple-scan 3.36.3-0ubuntu0.20.04.0 ProcVersionSignature: Ubuntu 5.4.0-56.62-generic 5.4.73 Uname: Linux 5.4.0-56-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.13 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Dec 7 17:16:02 2020 ExecutablePath: /usr/bin/simple-scan InstallationDate: Installed on 2020-04-29 (222 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-56-generic root=UUID=8a3753b1-5036-49b8-98d8-8b5c3eb01c74 ro quiet splash SimpleScanLog: SourcePackage: simple-scan UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/11/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.10 dmi.board.name: H110M-G/M.2 dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP1.10:bd05/11/2017:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnH110M-G/M.2:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.prod
[Desktop-packages] [Bug 1907121] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1907121/+attachment/5452627/+files/Lspci.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to simple-scan in Ubuntu. https://bugs.launchpad.net/bugs/1907121 Title: simple-scan unable to connect scanner HP 2630 Status in simple-scan package in Ubuntu: New Bug description: simple-scan says: "Ready to scan" but when i click on "scan" it fails to scan with a message "unable to connect to scanner" corrado@corrado-x4-focal:~$ scanimage -L device `hpaio:/usb/DeskJet_2600_series?serial=CN0569B27006PS' is a Hewlett-Packard DeskJet_2600_series all-in-one corrado@corrado-x4-focal:~$ apt policy simple-scan simple-scan: Installed: 3.36.3-0ubuntu0.20.04.0 Candidate: 3.36.3-0ubuntu0.20.04.0 Version table: *** 3.36.3-0ubuntu0.20.04.0 500 500 http://archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 100 /var/lib/dpkg/status 3.36.0-0ubuntu1 500 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages corrado@corrado-x4-focal:~$ inxi -Fx System:Host: corrado-x4-focal Kernel: 5.4.0-56-generic x86_64 bits: 64 compiler: gcc v: 9.3.0 Desktop: Gnome 3.36.4 Distro: Ubuntu 20.04.1 LTS (Focal Fossa) Machine: Type: Desktop Mobo: ASRock model: H110M-G/M.2 serial: UEFI: American Megatrends v: P1.10 date: 05/11/2017 CPU: Topology: Dual Core model: Intel Core i3-7100 bits: 64 type: MT MCP arch: Kaby Lake rev: 9 L2 cache: 3072 KiB flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 31199 Speed: 801 MHz min/max: 800/3900 MHz Core speeds (MHz): 1: 800 2: 800 3: 800 4: 800 Graphics: Device-1: Intel HD Graphics 630 vendor: ASRock driver: i915 v: kernel bus ID: 00:02.0 Display: x11 server: X.Org 1.20.8 driver: i915 resolution: 1920x1080~60Hz OpenGL: renderer: Mesa Intel HD Graphics 630 (KBL GT2) v: 4.6 Mesa 20.0.8 direct render: Yes Audio: Device-1: Intel 100 Series/C230 Series Family HD Audio vendor: ASRock driver: snd_hda_intel v: kernel bus ID: 00:1f.3 Device-2: Logitech QuickCam Pro 9000 type: USB driver: snd-usb-audio,uvcvideo bus ID: 1-2:3 Sound Server: ALSA v: k5.4.0-56-generic Network: Device-1: Intel Ethernet I219-V vendor: ASRock driver: e1000e v: 3.2.6-k port: f040 bus ID: 00:1f.6 IF: enp0s31f6 state: up speed: 100 Mbps duplex: full mac: 70:85:c2:44:7b:86 Drives:Local Storage: total: 2.05 TiB used: 19.43 GiB (0.9%) ID-1: /dev/nvme0n1 vendor: Kingston model: SKC2000M8250G size: 232.89 GiB ID-2: /dev/sda vendor: Toshiba model: DT01ACA100 size: 931.51 GiB ID-3: /dev/sdb vendor: Hitachi model: HDS721010CLA332 size: 931.51 GiB Partition: ID-1: / size: 31.25 GiB used: 19.42 GiB (62.2%) fs: ext4 dev: /dev/nvme0n1p4 ID-2: swap-1 size: 8.00 GiB used: 0 KiB (0.0%) fs: swap dev: /dev/sda2 Sensors: System Temperatures: cpu: 27.0 C mobo: 31.0 C Fan Speeds (RPM): fan-1: 0 fan-2: 2276 fan-3: 0 fan-4: 2216 fan-5: 0 fan-6: 0 Voltages: 12v: N/A 5v: N/A 3.3v: 3.42 vbat: 3.15 Info: Processes: 227 Uptime: 36m Memory: 7.48 GiB used: 1.59 GiB (21.2%) Init: systemd runlevel: 5 Compilers: gcc: 9.3.0 Shell: bash v: 5.0.17 inxi: 3.0.38 corrado@corrado-x4-focal:~$ ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: simple-scan 3.36.3-0ubuntu0.20.04.0 ProcVersionSignature: Ubuntu 5.4.0-56.62-generic 5.4.73 Uname: Linux 5.4.0-56-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.13 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Dec 7 17:16:02 2020 ExecutablePath: /usr/bin/simple-scan InstallationDate: Installed on 2020-04-29 (222 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-56-generic root=UUID=8a3753b1-5036-49b8-98d8-8b5c3eb01c74 ro quiet splash SimpleScanLog: SourcePackage: simple-scan UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/11/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.10 dmi.board.name: H110M-G/M.2 dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP1.10:bd05/11/2017:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnH110M-G/M.2:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.s
[Desktop-packages] [Bug 1907121] DriverPackageVersions.txt
apport information ** Attachment added: "DriverPackageVersions.txt" https://bugs.launchpad.net/bugs/1907121/+attachment/5452626/+files/DriverPackageVersions.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to simple-scan in Ubuntu. https://bugs.launchpad.net/bugs/1907121 Title: simple-scan unable to connect scanner HP 2630 Status in simple-scan package in Ubuntu: New Bug description: simple-scan says: "Ready to scan" but when i click on "scan" it fails to scan with a message "unable to connect to scanner" corrado@corrado-x4-focal:~$ scanimage -L device `hpaio:/usb/DeskJet_2600_series?serial=CN0569B27006PS' is a Hewlett-Packard DeskJet_2600_series all-in-one corrado@corrado-x4-focal:~$ apt policy simple-scan simple-scan: Installed: 3.36.3-0ubuntu0.20.04.0 Candidate: 3.36.3-0ubuntu0.20.04.0 Version table: *** 3.36.3-0ubuntu0.20.04.0 500 500 http://archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 100 /var/lib/dpkg/status 3.36.0-0ubuntu1 500 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages corrado@corrado-x4-focal:~$ inxi -Fx System:Host: corrado-x4-focal Kernel: 5.4.0-56-generic x86_64 bits: 64 compiler: gcc v: 9.3.0 Desktop: Gnome 3.36.4 Distro: Ubuntu 20.04.1 LTS (Focal Fossa) Machine: Type: Desktop Mobo: ASRock model: H110M-G/M.2 serial: UEFI: American Megatrends v: P1.10 date: 05/11/2017 CPU: Topology: Dual Core model: Intel Core i3-7100 bits: 64 type: MT MCP arch: Kaby Lake rev: 9 L2 cache: 3072 KiB flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 31199 Speed: 801 MHz min/max: 800/3900 MHz Core speeds (MHz): 1: 800 2: 800 3: 800 4: 800 Graphics: Device-1: Intel HD Graphics 630 vendor: ASRock driver: i915 v: kernel bus ID: 00:02.0 Display: x11 server: X.Org 1.20.8 driver: i915 resolution: 1920x1080~60Hz OpenGL: renderer: Mesa Intel HD Graphics 630 (KBL GT2) v: 4.6 Mesa 20.0.8 direct render: Yes Audio: Device-1: Intel 100 Series/C230 Series Family HD Audio vendor: ASRock driver: snd_hda_intel v: kernel bus ID: 00:1f.3 Device-2: Logitech QuickCam Pro 9000 type: USB driver: snd-usb-audio,uvcvideo bus ID: 1-2:3 Sound Server: ALSA v: k5.4.0-56-generic Network: Device-1: Intel Ethernet I219-V vendor: ASRock driver: e1000e v: 3.2.6-k port: f040 bus ID: 00:1f.6 IF: enp0s31f6 state: up speed: 100 Mbps duplex: full mac: 70:85:c2:44:7b:86 Drives:Local Storage: total: 2.05 TiB used: 19.43 GiB (0.9%) ID-1: /dev/nvme0n1 vendor: Kingston model: SKC2000M8250G size: 232.89 GiB ID-2: /dev/sda vendor: Toshiba model: DT01ACA100 size: 931.51 GiB ID-3: /dev/sdb vendor: Hitachi model: HDS721010CLA332 size: 931.51 GiB Partition: ID-1: / size: 31.25 GiB used: 19.42 GiB (62.2%) fs: ext4 dev: /dev/nvme0n1p4 ID-2: swap-1 size: 8.00 GiB used: 0 KiB (0.0%) fs: swap dev: /dev/sda2 Sensors: System Temperatures: cpu: 27.0 C mobo: 31.0 C Fan Speeds (RPM): fan-1: 0 fan-2: 2276 fan-3: 0 fan-4: 2216 fan-5: 0 fan-6: 0 Voltages: 12v: N/A 5v: N/A 3.3v: 3.42 vbat: 3.15 Info: Processes: 227 Uptime: 36m Memory: 7.48 GiB used: 1.59 GiB (21.2%) Init: systemd runlevel: 5 Compilers: gcc: 9.3.0 Shell: bash v: 5.0.17 inxi: 3.0.38 corrado@corrado-x4-focal:~$ ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: simple-scan 3.36.3-0ubuntu0.20.04.0 ProcVersionSignature: Ubuntu 5.4.0-56.62-generic 5.4.73 Uname: Linux 5.4.0-56-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.13 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Dec 7 17:16:02 2020 ExecutablePath: /usr/bin/simple-scan InstallationDate: Installed on 2020-04-29 (222 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-56-generic root=UUID=8a3753b1-5036-49b8-98d8-8b5c3eb01c74 ro quiet splash SimpleScanLog: SourcePackage: simple-scan UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/11/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.10 dmi.board.name: H110M-G/M.2 dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP1.10:bd05/11/2017:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnH110M-G/M.2:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be
[Desktop-packages] [Bug 1907121] Lsusb-t.txt
apport information ** Attachment added: "Lsusb-t.txt" https://bugs.launchpad.net/bugs/1907121/+attachment/5452630/+files/Lsusb-t.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to simple-scan in Ubuntu. https://bugs.launchpad.net/bugs/1907121 Title: simple-scan unable to connect scanner HP 2630 Status in simple-scan package in Ubuntu: New Bug description: simple-scan says: "Ready to scan" but when i click on "scan" it fails to scan with a message "unable to connect to scanner" corrado@corrado-x4-focal:~$ scanimage -L device `hpaio:/usb/DeskJet_2600_series?serial=CN0569B27006PS' is a Hewlett-Packard DeskJet_2600_series all-in-one corrado@corrado-x4-focal:~$ apt policy simple-scan simple-scan: Installed: 3.36.3-0ubuntu0.20.04.0 Candidate: 3.36.3-0ubuntu0.20.04.0 Version table: *** 3.36.3-0ubuntu0.20.04.0 500 500 http://archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 100 /var/lib/dpkg/status 3.36.0-0ubuntu1 500 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages corrado@corrado-x4-focal:~$ inxi -Fx System:Host: corrado-x4-focal Kernel: 5.4.0-56-generic x86_64 bits: 64 compiler: gcc v: 9.3.0 Desktop: Gnome 3.36.4 Distro: Ubuntu 20.04.1 LTS (Focal Fossa) Machine: Type: Desktop Mobo: ASRock model: H110M-G/M.2 serial: UEFI: American Megatrends v: P1.10 date: 05/11/2017 CPU: Topology: Dual Core model: Intel Core i3-7100 bits: 64 type: MT MCP arch: Kaby Lake rev: 9 L2 cache: 3072 KiB flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 31199 Speed: 801 MHz min/max: 800/3900 MHz Core speeds (MHz): 1: 800 2: 800 3: 800 4: 800 Graphics: Device-1: Intel HD Graphics 630 vendor: ASRock driver: i915 v: kernel bus ID: 00:02.0 Display: x11 server: X.Org 1.20.8 driver: i915 resolution: 1920x1080~60Hz OpenGL: renderer: Mesa Intel HD Graphics 630 (KBL GT2) v: 4.6 Mesa 20.0.8 direct render: Yes Audio: Device-1: Intel 100 Series/C230 Series Family HD Audio vendor: ASRock driver: snd_hda_intel v: kernel bus ID: 00:1f.3 Device-2: Logitech QuickCam Pro 9000 type: USB driver: snd-usb-audio,uvcvideo bus ID: 1-2:3 Sound Server: ALSA v: k5.4.0-56-generic Network: Device-1: Intel Ethernet I219-V vendor: ASRock driver: e1000e v: 3.2.6-k port: f040 bus ID: 00:1f.6 IF: enp0s31f6 state: up speed: 100 Mbps duplex: full mac: 70:85:c2:44:7b:86 Drives:Local Storage: total: 2.05 TiB used: 19.43 GiB (0.9%) ID-1: /dev/nvme0n1 vendor: Kingston model: SKC2000M8250G size: 232.89 GiB ID-2: /dev/sda vendor: Toshiba model: DT01ACA100 size: 931.51 GiB ID-3: /dev/sdb vendor: Hitachi model: HDS721010CLA332 size: 931.51 GiB Partition: ID-1: / size: 31.25 GiB used: 19.42 GiB (62.2%) fs: ext4 dev: /dev/nvme0n1p4 ID-2: swap-1 size: 8.00 GiB used: 0 KiB (0.0%) fs: swap dev: /dev/sda2 Sensors: System Temperatures: cpu: 27.0 C mobo: 31.0 C Fan Speeds (RPM): fan-1: 0 fan-2: 2276 fan-3: 0 fan-4: 2216 fan-5: 0 fan-6: 0 Voltages: 12v: N/A 5v: N/A 3.3v: 3.42 vbat: 3.15 Info: Processes: 227 Uptime: 36m Memory: 7.48 GiB used: 1.59 GiB (21.2%) Init: systemd runlevel: 5 Compilers: gcc: 9.3.0 Shell: bash v: 5.0.17 inxi: 3.0.38 corrado@corrado-x4-focal:~$ ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: simple-scan 3.36.3-0ubuntu0.20.04.0 ProcVersionSignature: Ubuntu 5.4.0-56.62-generic 5.4.73 Uname: Linux 5.4.0-56-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.13 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Dec 7 17:16:02 2020 ExecutablePath: /usr/bin/simple-scan InstallationDate: Installed on 2020-04-29 (222 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-56-generic root=UUID=8a3753b1-5036-49b8-98d8-8b5c3eb01c74 ro quiet splash SimpleScanLog: SourcePackage: simple-scan UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/11/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.10 dmi.board.name: H110M-G/M.2 dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP1.10:bd05/11/2017:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnH110M-G/M.2:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.prod
[Desktop-packages] [Bug 1907121] Lspci-vt.txt
apport information ** Attachment added: "Lspci-vt.txt" https://bugs.launchpad.net/bugs/1907121/+attachment/5452628/+files/Lspci-vt.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to simple-scan in Ubuntu. https://bugs.launchpad.net/bugs/1907121 Title: simple-scan unable to connect scanner HP 2630 Status in simple-scan package in Ubuntu: New Bug description: simple-scan says: "Ready to scan" but when i click on "scan" it fails to scan with a message "unable to connect to scanner" corrado@corrado-x4-focal:~$ scanimage -L device `hpaio:/usb/DeskJet_2600_series?serial=CN0569B27006PS' is a Hewlett-Packard DeskJet_2600_series all-in-one corrado@corrado-x4-focal:~$ apt policy simple-scan simple-scan: Installed: 3.36.3-0ubuntu0.20.04.0 Candidate: 3.36.3-0ubuntu0.20.04.0 Version table: *** 3.36.3-0ubuntu0.20.04.0 500 500 http://archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 100 /var/lib/dpkg/status 3.36.0-0ubuntu1 500 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages corrado@corrado-x4-focal:~$ inxi -Fx System:Host: corrado-x4-focal Kernel: 5.4.0-56-generic x86_64 bits: 64 compiler: gcc v: 9.3.0 Desktop: Gnome 3.36.4 Distro: Ubuntu 20.04.1 LTS (Focal Fossa) Machine: Type: Desktop Mobo: ASRock model: H110M-G/M.2 serial: UEFI: American Megatrends v: P1.10 date: 05/11/2017 CPU: Topology: Dual Core model: Intel Core i3-7100 bits: 64 type: MT MCP arch: Kaby Lake rev: 9 L2 cache: 3072 KiB flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 31199 Speed: 801 MHz min/max: 800/3900 MHz Core speeds (MHz): 1: 800 2: 800 3: 800 4: 800 Graphics: Device-1: Intel HD Graphics 630 vendor: ASRock driver: i915 v: kernel bus ID: 00:02.0 Display: x11 server: X.Org 1.20.8 driver: i915 resolution: 1920x1080~60Hz OpenGL: renderer: Mesa Intel HD Graphics 630 (KBL GT2) v: 4.6 Mesa 20.0.8 direct render: Yes Audio: Device-1: Intel 100 Series/C230 Series Family HD Audio vendor: ASRock driver: snd_hda_intel v: kernel bus ID: 00:1f.3 Device-2: Logitech QuickCam Pro 9000 type: USB driver: snd-usb-audio,uvcvideo bus ID: 1-2:3 Sound Server: ALSA v: k5.4.0-56-generic Network: Device-1: Intel Ethernet I219-V vendor: ASRock driver: e1000e v: 3.2.6-k port: f040 bus ID: 00:1f.6 IF: enp0s31f6 state: up speed: 100 Mbps duplex: full mac: 70:85:c2:44:7b:86 Drives:Local Storage: total: 2.05 TiB used: 19.43 GiB (0.9%) ID-1: /dev/nvme0n1 vendor: Kingston model: SKC2000M8250G size: 232.89 GiB ID-2: /dev/sda vendor: Toshiba model: DT01ACA100 size: 931.51 GiB ID-3: /dev/sdb vendor: Hitachi model: HDS721010CLA332 size: 931.51 GiB Partition: ID-1: / size: 31.25 GiB used: 19.42 GiB (62.2%) fs: ext4 dev: /dev/nvme0n1p4 ID-2: swap-1 size: 8.00 GiB used: 0 KiB (0.0%) fs: swap dev: /dev/sda2 Sensors: System Temperatures: cpu: 27.0 C mobo: 31.0 C Fan Speeds (RPM): fan-1: 0 fan-2: 2276 fan-3: 0 fan-4: 2216 fan-5: 0 fan-6: 0 Voltages: 12v: N/A 5v: N/A 3.3v: 3.42 vbat: 3.15 Info: Processes: 227 Uptime: 36m Memory: 7.48 GiB used: 1.59 GiB (21.2%) Init: systemd runlevel: 5 Compilers: gcc: 9.3.0 Shell: bash v: 5.0.17 inxi: 3.0.38 corrado@corrado-x4-focal:~$ ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: simple-scan 3.36.3-0ubuntu0.20.04.0 ProcVersionSignature: Ubuntu 5.4.0-56.62-generic 5.4.73 Uname: Linux 5.4.0-56-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.13 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Dec 7 17:16:02 2020 ExecutablePath: /usr/bin/simple-scan InstallationDate: Installed on 2020-04-29 (222 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-56-generic root=UUID=8a3753b1-5036-49b8-98d8-8b5c3eb01c74 ro quiet splash SimpleScanLog: SourcePackage: simple-scan UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/11/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.10 dmi.board.name: H110M-G/M.2 dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP1.10:bd05/11/2017:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnH110M-G/M.2:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.pr
[Desktop-packages] [Bug 1907121] Re: simple-scan unable to connect scanner HP 2630
apport information ** Tags added: apport-collected hirsute ** Description changed: simple-scan says: "Ready to scan" but when i click on "scan" it fails to scan with a message "unable to connect to scanner" corrado@corrado-x4-focal:~$ scanimage -L device `hpaio:/usb/DeskJet_2600_series?serial=CN0569B27006PS' is a Hewlett-Packard DeskJet_2600_series all-in-one corrado@corrado-x4-focal:~$ apt policy simple-scan simple-scan: Installed: 3.36.3-0ubuntu0.20.04.0 Candidate: 3.36.3-0ubuntu0.20.04.0 Version table: *** 3.36.3-0ubuntu0.20.04.0 500 500 http://archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 100 /var/lib/dpkg/status 3.36.0-0ubuntu1 500 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages corrado@corrado-x4-focal:~$ inxi -Fx System:Host: corrado-x4-focal Kernel: 5.4.0-56-generic x86_64 bits: 64 compiler: gcc v: 9.3.0 Desktop: Gnome 3.36.4 Distro: Ubuntu 20.04.1 LTS (Focal Fossa) Machine: Type: Desktop Mobo: ASRock model: H110M-G/M.2 serial: UEFI: American Megatrends v: P1.10 date: 05/11/2017 CPU: Topology: Dual Core model: Intel Core i3-7100 bits: 64 type: MT MCP arch: Kaby Lake rev: 9 L2 cache: 3072 KiB flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 31199 Speed: 801 MHz min/max: 800/3900 MHz Core speeds (MHz): 1: 800 2: 800 3: 800 4: 800 Graphics: Device-1: Intel HD Graphics 630 vendor: ASRock driver: i915 v: kernel bus ID: 00:02.0 Display: x11 server: X.Org 1.20.8 driver: i915 resolution: 1920x1080~60Hz OpenGL: renderer: Mesa Intel HD Graphics 630 (KBL GT2) v: 4.6 Mesa 20.0.8 direct render: Yes Audio: Device-1: Intel 100 Series/C230 Series Family HD Audio vendor: ASRock driver: snd_hda_intel v: kernel bus ID: 00:1f.3 Device-2: Logitech QuickCam Pro 9000 type: USB driver: snd-usb-audio,uvcvideo bus ID: 1-2:3 Sound Server: ALSA v: k5.4.0-56-generic Network: Device-1: Intel Ethernet I219-V vendor: ASRock driver: e1000e v: 3.2.6-k port: f040 bus ID: 00:1f.6 IF: enp0s31f6 state: up speed: 100 Mbps duplex: full mac: 70:85:c2:44:7b:86 Drives:Local Storage: total: 2.05 TiB used: 19.43 GiB (0.9%) ID-1: /dev/nvme0n1 vendor: Kingston model: SKC2000M8250G size: 232.89 GiB ID-2: /dev/sda vendor: Toshiba model: DT01ACA100 size: 931.51 GiB ID-3: /dev/sdb vendor: Hitachi model: HDS721010CLA332 size: 931.51 GiB Partition: ID-1: / size: 31.25 GiB used: 19.42 GiB (62.2%) fs: ext4 dev: /dev/nvme0n1p4 ID-2: swap-1 size: 8.00 GiB used: 0 KiB (0.0%) fs: swap dev: /dev/sda2 Sensors: System Temperatures: cpu: 27.0 C mobo: 31.0 C Fan Speeds (RPM): fan-1: 0 fan-2: 2276 fan-3: 0 fan-4: 2216 fan-5: 0 fan-6: 0 Voltages: 12v: N/A 5v: N/A 3.3v: 3.42 vbat: 3.15 Info: Processes: 227 Uptime: 36m Memory: 7.48 GiB used: 1.59 GiB (21.2%) Init: systemd runlevel: 5 Compilers: gcc: 9.3.0 Shell: bash v: 5.0.17 inxi: 3.0.38 corrado@corrado-x4-focal:~$ ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: simple-scan 3.36.3-0ubuntu0.20.04.0 ProcVersionSignature: Ubuntu 5.4.0-56.62-generic 5.4.73 Uname: Linux 5.4.0-56-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.13 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Dec 7 17:16:02 2020 ExecutablePath: /usr/bin/simple-scan InstallationDate: Installed on 2020-04-29 (222 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-56-generic root=UUID=8a3753b1-5036-49b8-98d8-8b5c3eb01c74 ro quiet splash SimpleScanLog: SourcePackage: simple-scan UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/11/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.10 dmi.board.name: H110M-G/M.2 dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP1.10:bd05/11/2017:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnH110M-G/M.2:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. + --- + ProblemType: Bug + ApportVersion: 2.20.11-0ubuntu55 + Architecture: amd64 + CasperMD5CheckResult: skip + CurrentDesktop: ubuntu:GNOME + DistroRelease: Ubuntu 21.04 + InstallationDate: Installed on 2020-12-14 (29 days
