[Touch-packages] [Bug 1888598] Re: pulseaudio has is buggy with hdmi audio and sleep/wake
before pacmd --list, with the input correctly selected as 5.1 surround on HDMI / DisplayPort 2. ** Attachment added: "before.txt" https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1888598/+attachment/5406020/+files/before.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1888598 Title: pulseaudio has is buggy with hdmi audio and sleep/wake Status in pulseaudio package in Ubuntu: Confirmed Bug description: on a fresh Ubuntu 20.04 x64 install, I've noticed some troubling bugs with pulseaudio after putting my system to sleep and then waking it up. these bugs aren't present on a fresh boot, only after resuming from sleep: - it forgets which sound output device it's set to, and always reverse to the motherboard's S/PDIF output. - I have two devices connected to my video card, one is a displayport monitor, and one is a home theater receiver via HDMI. it confuses the two, and randomly switches which device it thinks is capable of surround sound. - it sometimes refuses to switch to the correct audio device, and just resets any choice back to the internal S/PDIF, until the system is rebooted. as you can imagine, this a pretty frustrating state of affairs. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu3.4 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: tessa 3387 F pulseaudio /dev/snd/pcmC1D7p: tessa 3387 F...m pulseaudio /dev/snd/controlC2: tessa 3387 F pulseaudio /dev/snd/controlC0: tessa 3387 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Jul 22 18:38:42 2020 InstallationDate: Installed on 2020-07-15 (7 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/18/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3503 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: GRYPHON Z97 dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx 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.:bvr3503:bd04/18/2018:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnGRYPHONZ97:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: ASUS MB dmi.product.name: All Series dmi.product.sku: All dmi.product.version: System Version dmi.sys.vendor: ASUS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1888598/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1888598] Re: pulseaudio has is buggy with hdmi audio and sleep/wake
after pacmd --list, when the system has woken from sleep, and now is on the wrong sound output. note that it's not going to the internal sound card at the moment, but the other hdmi device. even though looking at the diff, it thinks the default sync hasn't changed, it actually is now going to the wrong output, and i have to manually switch it to the other hdmi/dp in the sound settings. ** Attachment added: "after.txt" https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1888598/+attachment/5406021/+files/after.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1888598 Title: pulseaudio has is buggy with hdmi audio and sleep/wake Status in pulseaudio package in Ubuntu: Confirmed Bug description: on a fresh Ubuntu 20.04 x64 install, I've noticed some troubling bugs with pulseaudio after putting my system to sleep and then waking it up. these bugs aren't present on a fresh boot, only after resuming from sleep: - it forgets which sound output device it's set to, and always reverse to the motherboard's S/PDIF output. - I have two devices connected to my video card, one is a displayport monitor, and one is a home theater receiver via HDMI. it confuses the two, and randomly switches which device it thinks is capable of surround sound. - it sometimes refuses to switch to the correct audio device, and just resets any choice back to the internal S/PDIF, until the system is rebooted. as you can imagine, this a pretty frustrating state of affairs. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu3.4 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: tessa 3387 F pulseaudio /dev/snd/pcmC1D7p: tessa 3387 F...m pulseaudio /dev/snd/controlC2: tessa 3387 F pulseaudio /dev/snd/controlC0: tessa 3387 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Jul 22 18:38:42 2020 InstallationDate: Installed on 2020-07-15 (7 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/18/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3503 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: GRYPHON Z97 dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx 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.:bvr3503:bd04/18/2018:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnGRYPHONZ97:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: ASUS MB dmi.product.name: All Series dmi.product.sku: All dmi.product.version: System Version dmi.sys.vendor: ASUS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1888598/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1882547] Re: systemd-resolved dumps core all the time
Can most rapidly reproduce with a config like: [Resolve] Domains=domaina domainb DNSSEC=yes And querying a "hostc" that exists under "domainb" only. Will reliably fail after about 5-20 invocations of "resolvectl query hostc". -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1882547 Title: systemd-resolved dumps core all the time Status in systemd package in Ubuntu: Confirmed Bug description: It dumps core all the time. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: systemd 245.4-4ubuntu3.1 ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 Uname: Linux 5.4.0-33-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 CasperMD5CheckResult: skip Date: Mon Jun 8 16:51:11 2020 ExecutablePath: /usr/lib/systemd/systemd-resolved InstallationDate: Installed on 2019-09-30 (252 days ago) InstallationMedia: Kubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: Dell Inc. Precision 5530 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-33-generic root=/dev/mapper/kubuntu--vg-root ro quiet splash vt.handoff=7 SourcePackage: systemd SystemdDelta: [EXTENDED] /usr/lib/systemd/system/rc-local.service → /usr/lib/systemd/system/rc-local.service.d/debian.conf [EXTENDED] /usr/lib/systemd/system/user@.service → /usr/lib/systemd/system/user@.service.d/timeout.conf 2 overridden configuration files found. UpgradeStatus: Upgraded to focal on 2020-05-28 (11 days ago) dmi.bios.date: 08/22/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.13.0 dmi.board.name: 0FP2W2 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.13.0:bd08/22/2019:svnDellInc.:pnPrecision5530:pvr:rvnDellInc.:rn0FP2W2:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Precision dmi.product.name: Precision 5530 dmi.product.sku: 087D dmi.sys.vendor: Dell Inc. mtime.conffile..etc.systemd.logind.conf: 2019-11-18T09:50:53.885999 mtime.conffile..etc.systemd.resolved.conf: 2020-06-04T14:51:08.011600 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1882547/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1882547] Re: systemd-resolved dumps core all the time
Seeing this frequently too after adding multiple entries to "Domains" in "/etc/systemd/resolved.conf" -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1882547 Title: systemd-resolved dumps core all the time Status in systemd package in Ubuntu: Confirmed Bug description: It dumps core all the time. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: systemd 245.4-4ubuntu3.1 ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 Uname: Linux 5.4.0-33-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 CasperMD5CheckResult: skip Date: Mon Jun 8 16:51:11 2020 ExecutablePath: /usr/lib/systemd/systemd-resolved InstallationDate: Installed on 2019-09-30 (252 days ago) InstallationMedia: Kubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: Dell Inc. Precision 5530 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-33-generic root=/dev/mapper/kubuntu--vg-root ro quiet splash vt.handoff=7 SourcePackage: systemd SystemdDelta: [EXTENDED] /usr/lib/systemd/system/rc-local.service → /usr/lib/systemd/system/rc-local.service.d/debian.conf [EXTENDED] /usr/lib/systemd/system/user@.service → /usr/lib/systemd/system/user@.service.d/timeout.conf 2 overridden configuration files found. UpgradeStatus: Upgraded to focal on 2020-05-28 (11 days ago) dmi.bios.date: 08/22/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.13.0 dmi.board.name: 0FP2W2 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.13.0:bd08/22/2019:svnDellInc.:pnPrecision5530:pvr:rvnDellInc.:rn0FP2W2:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Precision dmi.product.name: Precision 5530 dmi.product.sku: 087D dmi.sys.vendor: Dell Inc. mtime.conffile..etc.systemd.logind.conf: 2019-11-18T09:50:53.885999 mtime.conffile..etc.systemd.resolved.conf: 2020-06-04T14:51:08.011600 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1882547/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1882547] Re: systemd-resolved dumps core all the time
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: systemd (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1882547 Title: systemd-resolved dumps core all the time Status in systemd package in Ubuntu: Confirmed Bug description: It dumps core all the time. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: systemd 245.4-4ubuntu3.1 ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 Uname: Linux 5.4.0-33-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 CasperMD5CheckResult: skip Date: Mon Jun 8 16:51:11 2020 ExecutablePath: /usr/lib/systemd/systemd-resolved InstallationDate: Installed on 2019-09-30 (252 days ago) InstallationMedia: Kubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: Dell Inc. Precision 5530 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-33-generic root=/dev/mapper/kubuntu--vg-root ro quiet splash vt.handoff=7 SourcePackage: systemd SystemdDelta: [EXTENDED] /usr/lib/systemd/system/rc-local.service → /usr/lib/systemd/system/rc-local.service.d/debian.conf [EXTENDED] /usr/lib/systemd/system/user@.service → /usr/lib/systemd/system/user@.service.d/timeout.conf 2 overridden configuration files found. UpgradeStatus: Upgraded to focal on 2020-05-28 (11 days ago) dmi.bios.date: 08/22/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.13.0 dmi.board.name: 0FP2W2 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.13.0:bd08/22/2019:svnDellInc.:pnPrecision5530:pvr:rvnDellInc.:rn0FP2W2:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Precision dmi.product.name: Precision 5530 dmi.product.sku: 087D dmi.sys.vendor: Dell Inc. mtime.conffile..etc.systemd.logind.conf: 2019-11-18T09:50:53.885999 mtime.conffile..etc.systemd.resolved.conf: 2020-06-04T14:51:08.011600 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1882547/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1892358] Re: autopkgtest success rate dropped inhibiting proposed migration
If not going for marking the subtest flaky as in groovy, I have prepared force-reset-test as alternatives in: - https://code.launchpad.net/~paelzer/britney/hints-ubuntu-focal-disable-systemd/+merge/390005 - https://code.launchpad.net/~paelzer/britney/hints-ubuntu-focal-disable-systemd/+merge/390004 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1892358 Title: autopkgtest success rate dropped inhibiting proposed migration Status in build-essential package in Ubuntu: Invalid Status in glib2.0 package in Ubuntu: Invalid Status in iputils package in Ubuntu: Invalid Status in kbd package in Ubuntu: Invalid Status in linux-meta package in Ubuntu: Invalid Status in ntpsec package in Ubuntu: Invalid Status in qemu package in Ubuntu: Invalid Status in systemd package in Ubuntu: Fix Released Status in util-linux package in Ubuntu: Invalid Status in linux-meta source package in Bionic: New Status in systemd source package in Bionic: New Status in build-essential source package in Focal: Confirmed Status in linux-meta source package in Focal: New Status in qemu source package in Focal: Confirmed Status in systemd source package in Focal: Confirmed Status in util-linux source package in Focal: Confirmed Bug description: Hi, we had such cases in the past like bug 1817721 for bionic and maybe bug 1892130 is about the same as well. There were more but I didn't want to search for all of them - what I checked is that there are no open ones clearly pointing out the recent further drop in already flaky subtests. In particular the tests "tests-in-lxd" and "systemd-fsckd" were known to be flaky before, but got even worse. Here stats of the last 40 runs, it might be a coincidences that this is after 246-2ubuntu1 landed. Could as well be any other change groovy amd64 tests-in-lxd (F 42% S 0% B 10% => P 45%/) BFFFBFF.B.F.F...FBF build-login(F 0% S 0% B 10% => P 87%/) B...B...BB. unit-config(F 0% S 0% B 10% => P 87%/) B...B...BB. networkd-testpy(F 0% S 0% B 10% => P 87%/) B...B...BB. boot-and-services (F 0% S 0% B 10% => P 87%/) B...B...BB. boot-smoke (F 0% S 0% B 10% => P 87%/) B...B...BB. logind (F 0% S 0% B 10% => P 87%/) B...B...BB. storage(F 0% S 0% B 10% => P 87%/) B...B...BB. upstream (F 35% S 0% B 10% => P 52%/) ..FFB.FFF.FFBFF.B.F.F..FFBF udev (F 0% S 0% B 10% => P 87%/) B...B...BB. systemd-fsckd (F 37% S 0% B 10% => P 50%/) BFFFB.FF...FB.F..B. root-unittests (F 0% S 0% B 10% => P 87%/) B...B...BB. ppc64el tests-in-lxd (F 25% S 0% B 0% => P 75%/) FFFFF.F. systemd-fsckd (F 35% S 0% B 0% => P 65%/) FFF...FFFFF.F..F root-unittests (F 2% S 0% B 0% => P 97%/) ..F. s390x tests-in-lxd (F 52% S 0% B 0% => P 47%/) FFF.FFF.FF....F. timedated (F 2% S 0% B 0% => P 97%/) ...F upstream (F 17% S 0% B 0% => P 82%/) .F..F.F.FFF...F. systemd-fsckd (F 32% S 0% B 0% => P 67%/) FFF..FF..F.FF..F root-unittests (F 10% S 0% B 0% => P 90%/) FFF...F. arm64 tests-in-lxd (F 40% S 0% B 2% => P 57%/) F.B...FFF.FF..F..F.FFF.F logind (F 2% S 0% B 2% => P 95%/) ..B...F. upstream (F 22% S 0% B 2% => P 75%/) ...F.FB.F.F.F..FFF.F root-unittests (F 12% S 0% B 2% => P 85%/) ..B.F...F.FF...F (I'm sure LP will make this unreadable, but is is nice in monospace) Whatever the root cause is - the success rate of these has reduced so much that the (even formerly questionable) practice of retry-until- success won't work anymore. I have run the two tests in a local VM and systemd-fsckd works there while tests-in-lxd seems to trip over the old flaky fellow being "boot-and-services". We had the discussion in the past, but I think I need to again bring up the suggesti
[Touch-packages] [Bug 1892358] Re: autopkgtest success rate dropped inhibiting proposed migration
To match the open packages blocked on this in active releases I added linux-meta for BIonic (thanks Kleber for the hint) and Focal (Thanks Kelsey for the hint). I think all of those had enough of retry-until-success and I'd ask again for how we should proceed there. Masking/Resetting the test via an override would throw away so much other coverage, but lacking other feedback I'll at least proposed the change - maybe this also brings more attention to here. Last 20 focal amd64 upstream (F 5% S 0% B 5% => P 90%/) F.B. systemd-fsckd (F 95% S 0% B 5% => P 0%/) FFBF ppc64el systemd-fsckd (F 65% S 0% B 0% => P 35%/) ...F s390x systemd-fsckd (F 60% S 0% B 0% => P 40%/) bionic amd64 boot-smoke (F 20% S 0% B 0% => P 80%/) ...F.FFF upstream (F 10% S 0% B 0% => P 90%/) ...F..F. systemd-fsckd (F 85% S 0% B 0% => P 15%/) FFF.FF.. They all seem to continue to be heavy on "systemd-fsckd" ** Also affects: linux-meta (Ubuntu) Importance: Undecided Status: New ** Changed in: linux-meta (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1892358 Title: autopkgtest success rate dropped inhibiting proposed migration Status in build-essential package in Ubuntu: Invalid Status in glib2.0 package in Ubuntu: Invalid Status in iputils package in Ubuntu: Invalid Status in kbd package in Ubuntu: Invalid Status in linux-meta package in Ubuntu: Invalid Status in ntpsec package in Ubuntu: Invalid Status in qemu package in Ubuntu: Invalid Status in systemd package in Ubuntu: Fix Released Status in util-linux package in Ubuntu: Invalid Status in linux-meta source package in Bionic: New Status in build-essential source package in Focal: Confirmed Status in linux-meta source package in Focal: New Status in qemu source package in Focal: Confirmed Status in systemd source package in Focal: Confirmed Status in util-linux source package in Focal: Confirmed Bug description: Hi, we had such cases in the past like bug 1817721 for bionic and maybe bug 1892130 is about the same as well. There were more but I didn't want to search for all of them - what I checked is that there are no open ones clearly pointing out the recent further drop in already flaky subtests. In particular the tests "tests-in-lxd" and "systemd-fsckd" were known to be flaky before, but got even worse. Here stats of the last 40 runs, it might be a coincidences that this is after 246-2ubuntu1 landed. Could as well be any other change groovy amd64 tests-in-lxd (F 42% S 0% B 10% => P 45%/) BFFFBFF.B.F.F...FBF build-login(F 0% S 0% B 10% => P 87%/) B...B...BB. unit-config(F 0% S 0% B 10% => P 87%/) B...B...BB. networkd-testpy(F 0% S 0% B 10% => P 87%/) B...B...BB. boot-and-services (F 0% S 0% B 10% => P 87%/) B...B...BB. boot-smoke (F 0% S 0% B 10% => P 87%/) B...B...BB. logind (F 0% S 0% B 10% => P 87%/) B...B...BB. storage(F 0% S 0% B 10% => P 87%/) B...B...BB. upstream (F 35% S 0% B 10% => P 52%/) ..FFB.FFF.FFBFF.B.F.F..FFBF udev (F 0% S 0% B 10% => P 87%/) B...B...BB. systemd-fsckd (F 37% S 0% B 10% => P 50%/) BFFFB.FF...FB.F..B. root-unittests (F 0% S 0% B 10% => P 87%/) B...B...BB. ppc64el tests-in-lxd (F 25% S 0% B 0% => P 75%/) FFFFF.F. systemd-fsckd (F 35% S 0% B 0% => P 65%/) FFF...FFFFF.F..F root-unittests (F 2% S 0% B 0% => P 97%/) ..F. s390x tests-in-lxd (F 52% S 0% B 0% => P 47%/) FFF.FFF.FF....F. timedated (F 2% S 0% B 0% => P 97%/) ...F upstream (F 17% S 0% B 0% => P 82%/) .F..F.F.FFF...F. systemd-fsckd (F 32% S 0% B 0% => P 67%/) FFF..FF..F.FF..F root-unittests (F 10% S 0% B
[Touch-packages] [Bug 1625324] Re: prints pdf files very faintly on EPSON WF-7620. All other types of files print normally
[Expired for cups (Ubuntu) because there has been no activity for 60 days.] ** Changed in: cups (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1625324 Title: prints pdf files very faintly on EPSON WF-7620. All other types of files print normally Status in cups package in Ubuntu: Expired Bug description: Printer is installed as a network printer. Windows does not print pdf files faintly. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: evince 3.18.2-1ubuntu4 ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16 Uname: Linux 4.4.0-36-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CurrentDesktop: Unity Date: Mon Sep 19 15:06:37 2016 InstallationDate: Installed on 2016-08-09 (41 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: evince UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1625324/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1893601] Re: 4k not working
Please try: 1. Selecting 'Ubuntu on Wayland' from the login screen. Do you now get 4K modes offered in Settings? 2. Run: grep . /sys/class/drm/*/modes > kernel-modes.txt and then attach the resulting text file here. ** Package changed: xorg (Ubuntu) => xorg-server (Ubuntu) ** Changed in: xorg-server (Ubuntu) Status: New => Incomplete ** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Changed in: linux (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1893601 Title: 4k not working Status in linux package in Ubuntu: Incomplete Status in xorg-server package in Ubuntu: Incomplete Bug description: Windows 10 is working with 4k monitor, but not Ubuntu 20.04 LTS. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Aug 30 20:35:52 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: virtualbox, 6.1.10, 5.4.0-42-generic, x86_64: installed ExtraDebuggingInterest: No GraphicsCard: Intel Corporation HD Graphics 530 [8086:1912] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company HD Graphics 530 [103c:81b4] InstallationDate: Installed on 2020-08-28 (2 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 046d:c52b Logitech, Inc. Unifying Receiver Bus 001 Device 002: ID 413c:2113 Dell Computer Corp. Dell KB216 Wired Keyboard Bus 001 Device 004: ID 8087:0aa7 Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP 510-p114 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic root=UUID=906d29e9-4c50-43be-a8f5-2f6d9df94188 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/02/2016 dmi.bios.vendor: AMI dmi.bios.version: F.13 dmi.board.asset.tag: CNV6370S3L dmi.board.name: 81B4 dmi.board.vendor: HP dmi.board.version: 00 dmi.chassis.asset.tag: CNV6370S3L dmi.chassis.type: 3 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnAMI:bvrF.13:bd08/02/2016:svnHP:pn510-p114:pvr:rvnHP:rn81B4:rvr00:cvnHP:ct3:cvr: dmi.product.family: 103C_53316J G=D dmi.product.name: 510-p114 dmi.product.sku: X6F90AA#ABA dmi.sys.vendor: HP version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.2 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/1893601/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1893601] Re: 4k not working
Yes it looks like either the kernel driver or Xorg driver is failing to expose 4K modes, which definitely should be available: EDID version: 1.3 Manufacturer: SAM Model 3988 Serial Number 0 Made in week 41 of 2018 Digital display Maximum image size: 70 cm x 39 cm Gamma: 2.20 DPMS levels: Off RGB color display First detailed timing is preferred timing Color Characteristics Red: 0.6513, 0.3398 Green: 0.2998, 0.6230 Blue: 0.1494, 0.0712 White: 0.3125, 0.3291 Established Timings I & II 720x40070.082 Hz 9:531.467 kHz 28.320 MHz (IBM) 640x48059.940 Hz 4:331.469 kHz 25.175 MHz (DMT) 640x48066.667 Hz 4:335.000 kHz 30.240 MHz (Apple) 640x48072.809 Hz 4:337.861 kHz 31.500 MHz (DMT) 640x48075.000 Hz 4:337.500 kHz 31.500 MHz (DMT) 800x60056.250 Hz 4:335.156 kHz 36.000 MHz (DMT) 800x60060.317 Hz 4:337.879 kHz 40.000 MHz (DMT) 800x60072.188 Hz 4:348.077 kHz 50.000 MHz (DMT) 800x60075.000 Hz 4:346.875 kHz 49.500 MHz (DMT) 832x62474.551 Hz 4:349.726 kHz 57.284 MHz (Apple) 1024x76860.004 Hz 4:348.363 kHz 65.000 MHz (DMT) 1024x76870.069 Hz 4:356.476 kHz 75.000 MHz (DMT) 1024x76875.029 Hz 4:360.023 kHz 78.750 MHz (DMT) 1280x1024 75.025 Hz 5:479.976 kHz 135.000 MHz (DMT) 1152x87075.062 Hz 192:145 68.681 kHz 100.000 MHz (Apple) Standard Timings 1152x86475.000 Hz 4:367.500 kHz 108.000 MHz (DMT) 1280x80059.810 Hz 16:10 49.702 kHz 83.500 MHz (DMT) 1280x72060.000 Hz 16:945.000 kHz 74.250 MHz (DMT) 1280x1024 60.020 Hz 5:463.981 kHz 108.000 MHz (DMT) 1440x90059.887 Hz 16:10 55.935 kHz 106.500 MHz (DMT) 1600x90060.000 Hz 16:960.000 kHz 108.000 MHz (DMT, RB) 1680x1050 59.954 Hz 16:10 65.290 kHz 146.250 MHz (DMT) Detailed mode: Clock 594.000 MHz, 697 mm x 392 mm 3840 4016 4104 4400 (176 88 296) 2160 2168 2178 2250 ( 8 10 72) +hsync +vsync VertFreq: 60.000 Hz, HorFreq: 135.000 kHz Display Range Limits Monitor ranges (GTF): 24-75 Hz V, 30-135 kHz H, max dotclock 600 MHz Display Product Name: U32R59x Display Product Serial Number: H1AK50 Has 1 extension block Checksum: 0x46 CTA-861 Extension Block Revision 3 Underscans PC formats by default Basic audio support Supports YCbCr 4:4:4 Supports YCbCr 4:2:2 0 native detailed modes 48 bytes of CTA data blocks Video Data Block 3840x2160 60.000 Hz 16:9 135.000 kHz 594.000 MHz (VIC 97) 720x57650.000 Hz 16:931.250 kHz 27.000 MHz (VIC 18) 720x48059.940 Hz 16:931.469 kHz 27.000 MHz (VIC 3) 1280x72050.000 Hz 16:937.500 kHz 74.250 MHz (VIC 19) 1280x72060.000 Hz 16:945.000 kHz 74.250 MHz (VIC 4) 1920x1080 24.000 Hz 16:927.000 kHz 74.250 MHz (VIC 32) 1920x1080 30.000 Hz 16:933.750 kHz 74.250 MHz (VIC 34) 1920x1080 50.000 Hz 16:956.250 kHz 148.500 MHz (VIC 31) 1920x1080 60.000 Hz 16:967.500 kHz 148.500 MHz (VIC 16) 3840x2160 30.000 Hz 16:967.500 kHz 297.000 MHz (VIC 95) 3840x2160 50.000 Hz 16:9 112.500 kHz 594.000 MHz (VIC 96) 3840x2160 24.000 Hz 16:954.000 kHz 297.000 MHz (VIC 93) 3840x2160 25.000 Hz 16:956.250 kHz 297.000 MHz (VIC 94) Audio Data Block Linear PCM, max channels 2 Supported sample rates (kHz): 48 44.1 32 Supported sample sizes (bits): 24 20 16 Speaker Allocation Data Block Speaker map: FL/FR - Front Left/Right Vendor-Specific Data Block, OUI 0x000c03 (HDMI) Source physical address 1.0.0.0 Supports_AI DC_36bit DC_30bit DC_Y444 Maximum TMDS clock: 300 MHz Extended HDMI video details: HDMI VICs: 3840x2160 30.000 Hz 16:967.500 kHz 297.000 MHz (HDMI VIC 1) 3840x2160 25.000 Hz 16:956.250 kHz 297.000 MHz (HDMI VIC 2) 3840x2160 24.000 Hz 16:954.000 kHz 297.000 MHz (HDMI VIC 3) Vendor-Specific Data Block, OUI 0xc45dd8 (HDMI Forum) Version: 1 Maximum TMDS Character Rate: 600 MHz SCDC Present Supports 12-bits/component Deep Color 4:2:0 Pixel Encoding Supports 10-bits/component Deep Color 4:2:0 Pixel Encoding Extended tag: YCbCr 4:2:0 Capability Map Data Block 3840x2160 60.000 Hz 16:9 135.000 kHz 594.000 MHz (VIC 97) 3840x2160 50.000 Hz 16:9 112.500 kHz 594.000 MHz (VIC 96) Detailed mode: Clock 148.500 MHz, 697 mm x 392 mm 1920 2008 2052 2200 ( 88 44 148) 1080 1084 1089 1125 ( 4 5 36) +hsync +vsync VertFreq: 60.000 Hz, HorFreq: 67.500 kHz Detailed mode: Clock 148.500 MHz, 697 mm x 392 mm 1920 2448 2492 2640 (528 44 148) 1080 1084 1089 1125 ( 4 5 36) +hsync +vsync
[Touch-packages] [Bug 1893601] [NEW] 4k not working
Public bug reported: Windows 10 is working with 4k monitor, but not Ubuntu 20.04 LTS. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Aug 30 20:35:52 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: virtualbox, 6.1.10, 5.4.0-42-generic, x86_64: installed ExtraDebuggingInterest: No GraphicsCard: Intel Corporation HD Graphics 530 [8086:1912] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company HD Graphics 530 [103c:81b4] InstallationDate: Installed on 2020-08-28 (2 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 046d:c52b Logitech, Inc. Unifying Receiver Bus 001 Device 002: ID 413c:2113 Dell Computer Corp. Dell KB216 Wired Keyboard Bus 001 Device 004: ID 8087:0aa7 Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP 510-p114 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic root=UUID=906d29e9-4c50-43be-a8f5-2f6d9df94188 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/02/2016 dmi.bios.vendor: AMI dmi.bios.version: F.13 dmi.board.asset.tag: CNV6370S3L dmi.board.name: 81B4 dmi.board.vendor: HP dmi.board.version: 00 dmi.chassis.asset.tag: CNV6370S3L dmi.chassis.type: 3 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnAMI:bvrF.13:bd08/02/2016:svnHP:pn510-p114:pvr:rvnHP:rn81B4:rvr00:cvnHP:ct3:cvr: dmi.product.family: 103C_53316J G=D dmi.product.name: 510-p114 dmi.product.sku: X6F90AA#ABA dmi.sys.vendor: HP version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ubuntu -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1893601 Title: 4k not working Status in xorg package in Ubuntu: New Bug description: Windows 10 is working with 4k monitor, but not Ubuntu 20.04 LTS. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Aug 30 20:35:52 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: virtualbox, 6.1.10, 5.4.0-42-generic, x86_64: installed ExtraDebuggingInterest: No GraphicsCard: Intel Corporation HD Graphics 530 [8086:1912] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company HD Graphics 530 [103c:81b4] InstallationDate: Installed on 2020-08-28 (2 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 046d:c52b Logitech, Inc. Unifying Receiver Bus 001 Device 002: ID 413c:2113 Dell Computer Corp. Dell KB216 Wired Keyboard Bus 001 Device 004: ID 8087:0aa7 Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP 510-p114 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic root=UUID=906d29e9-4c50-43be-a8f5-2f6d9df94188 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/02/2016 dmi.bios.vendor: AMI dmi.bios.version: F.13 dmi.board.asset.tag: CNV6370S3L dmi.board.name: 81B4 dmi.board.vendor: HP dmi.board.version: 00 dmi.chassis.asset.tag: CNV6370S3L dmi.chassis.type: 3 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnAMI:bvrF.13
[Touch-packages] [Bug 1893520] Re: screen auto scroll
Please attach a video of the issue so we can see what you mean. Please also tell us if the problem affects all apps or only some. ** Package changed: xorg (Ubuntu) => ubuntu ** Changed in: ubuntu Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1893520 Title: screen auto scroll Status in Ubuntu: Incomplete Bug description: screen auto scroll , mouse is ok. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-115.116-generic 4.15.18 Uname: Linux 4.15.0-115-generic x86_64 NonfreeKernelModules: wl .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.17 Architecture: amd64 CompositorRunning: None Date: Sat Aug 29 19:58:28 2020 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: bcmwl, 6.30.223.271+bdcom, 4.15.0-115-generic, x86_64: installed GraphicsCard: Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company HD Graphics 5500 [103c:80c1] InstallationDate: Installed on 2015-10-17 (1777 days ago) InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) MachineType: Hewlett-Packard HP Notebook ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-115-generic root=UUID=733f49c2-0b52-4a07-9eea-15cbf15593cf ro drm.debug=0xe plymouth:debug SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/04/2015 dmi.bios.vendor: Insyde dmi.bios.version: F.0B dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 80C1 dmi.board.vendor: Hewlett-Packard dmi.board.version: 96.11 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.0B:bd06/04/2015:svnHewlett-Packard:pnHPNotebook:pvrType1ProductConfigId:rvnHewlett-Packard:rn80C1:rvr96.11:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP dmi.product.name: HP Notebook dmi.product.version: Type1ProductConfigId dmi.sys.vendor: Hewlett-Packard version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.101-2~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.8-0ubuntu1~18.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 xserver.bootTime: Wed Aug 26 19:22:07 2020 xserver.configfile: default xserver.devices: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.19.6-1ubuntu4.4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1893520/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1893509] Re: llvmpipe instead of intel graphics or amd graphics
** Package changed: xorg (Ubuntu) => ubuntu ** Changed in: ubuntu Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1893509 Title: llvmpipe instead of intel graphics or amd graphics Status in Ubuntu: Invalid Bug description: I dont see my monitor detected in monitor settings. I see duplicated display with low res. I have intel integrated and amd radeon graphics. In the inxi -G i see those cards, but the driver says : N/A in the about computer - the graphics is llvmpipe Something is totally wrong, please help! ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: MATE Date: Sat Aug 29 14:45:03 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a2e] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo Haswell-ULT Integrated Graphics Controller [17aa:380c] Subsystem: Lenovo Sun LE [Radeon HD 8550M / R5 M230] [17aa:380c] InstallationDate: Installed on 2020-06-12 (77 days ago) InstallationMedia: Ubuntu-MATE 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: LENOVO 20351 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic root=UUID=b6c37141-5b45-4f4d-8eec-c4e3187dcf66 ro quiet splash nomodeset vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/20/2014 dmi.bios.vendor: LENOVO dmi.bios.version: 9ACN29WW dmi.board.asset.tag: No Asset Tag dmi.board.name: Lancer 5A2 dmi.board.vendor: LENOVO dmi.board.version: NANANANANO DPK dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo G50-70 dmi.modalias: dmi:bvnLENOVO:bvr9ACN29WW:bd10/20/2014:svnLENOVO:pn20351:pvrLenovoG50-70:rvnLENOVO:rnLancer5A2:rvrNANANANANODPK:cvnLENOVO:ct10:cvrLenovoG50-70: dmi.product.family: IDEAPAD dmi.product.name: 20351 dmi.product.sku: LENOVO_MT_20351_BU_idea_FM_Lenovo G50-70 dmi.product.version: Lenovo G50-70 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.2 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/+bug/1893509/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1893509] Re: llvmpipe instead of intel graphics or amd graphics
You have disabled the graphics drivers with the 'nomodeset' kernel parameter. Please remove that from /etc/default/grub and then run: sudo update-grub and reboot. If then problem persists after that then please open a new bug. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1893509 Title: llvmpipe instead of intel graphics or amd graphics Status in xorg package in Ubuntu: New Bug description: I dont see my monitor detected in monitor settings. I see duplicated display with low res. I have intel integrated and amd radeon graphics. In the inxi -G i see those cards, but the driver says : N/A in the about computer - the graphics is llvmpipe Something is totally wrong, please help! ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: MATE Date: Sat Aug 29 14:45:03 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a2e] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo Haswell-ULT Integrated Graphics Controller [17aa:380c] Subsystem: Lenovo Sun LE [Radeon HD 8550M / R5 M230] [17aa:380c] InstallationDate: Installed on 2020-06-12 (77 days ago) InstallationMedia: Ubuntu-MATE 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: LENOVO 20351 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic root=UUID=b6c37141-5b45-4f4d-8eec-c4e3187dcf66 ro quiet splash nomodeset vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/20/2014 dmi.bios.vendor: LENOVO dmi.bios.version: 9ACN29WW dmi.board.asset.tag: No Asset Tag dmi.board.name: Lancer 5A2 dmi.board.vendor: LENOVO dmi.board.version: NANANANANO DPK dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo G50-70 dmi.modalias: dmi:bvnLENOVO:bvr9ACN29WW:bd10/20/2014:svnLENOVO:pn20351:pvrLenovoG50-70:rvnLENOVO:rnLancer5A2:rvrNANANANANODPK:cvnLENOVO:ct10:cvrLenovoG50-70: dmi.product.family: IDEAPAD dmi.product.name: 20351 dmi.product.sku: LENOVO_MT_20351_BU_idea_FM_Lenovo G50-70 dmi.product.version: Lenovo G50-70 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.2 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/xorg/+bug/1893509/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1888572] Re: motd-news: use wget instead of curl
** Tags removed: verification-needed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to base-files in Ubuntu.
https://bugs.launchpad.net/bugs/1888572
Title:
motd-news: use wget instead of curl
Status in base-files package in Ubuntu:
Fix Released
Status in base-files source package in Xenial:
Fix Committed
Status in base-files source package in Bionic:
Fix Committed
Status in base-files source package in Focal:
Fix Committed
Bug description:
[Impact]
The motd-news script is using curl, but since that is an optional package,
there is no guarantee that it will be installed. The script correctly checks
for its presence before trying to use it, though, so it won't fail. As we don't
want to add such a dependency to the base-files package, we should switch to
wget, which is standard.
[Test Case]
wget has a different behavior than curl in some areas, one of which is
crucial for the motd-per-cloud feature. While curl will only complain about a
404 from the server if given a specific parameter (-f), wget does that by
default, and needs special handling.
a) With curl, base-files and ubuntu-server installed, first verify motd-news
works:
$ sudo /etc/update-motd.d/50-motd-news --force
* Are you ready for Kubernetes 1.19? It's nearly here! Try RC3 with
sudo snap install microk8s --channel=1.19/candidate --classic
https://microk8s.io/ has docs and details.
Now remove curl, and retry. It should exit immediately with no output:
$ sudo /etc/update-motd.d/50-motd-news --force
Install the updated base-files package and the new motd-news-config
package from proposed:
$ sudo apt install base-files motd-news-config
Note curl is still not available:
$ curl
Command 'curl' not found, but can be installed with:
sudo apt install curl
Re-run the motd-news script, this time it should produce output again:
$ sudo /etc/update-motd.d/50-motd-news --force
* Are you ready for Kubernetes 1.19? It's nearly here! Try RC3 with
sudo snap install microk8s --channel=1.19/candidate --classic
https://microk8s.io/ has docs and details.
b) Verify motd-news per cloud remains working.
If you have /usr/bin/cloud-id, copy it to a backup:
sudo cp /usr/bin/cloud-id{,.orig}
Create a new one, per supported cloud. For aws, for example:
echo -e '#!/bin/sh\necho aws' | sudo tee /usr/bin/cloud-id
Confirm by running it:
$ cloud-id
aws
And confirm motd-news keeps working (it might return different content):
$ sudo /etc/update-motd.d/50-motd-news --force
* Are you ready for Kubernetes 1.19? It's nearly here! Try RC3 with
sudo snap install microk8s --channel=1.19/candidate --classic
https://microk8s.io/ has docs and details.
Repeat for the gce and azure clouds, by changing the cloud-id script
accordingly.
To confirm the right cloud_id is being used, use sh -x and grep for
its output:
$ sudo sh -x /etc/update-motd.d/50-motd-news --force 2>&1 | grep -wE 'wget
.*cloud_id/[a-z]+'
+ wget --timeout 60 -U wget/1.20.3-1ubuntu1 Ubuntu/20.04.1/LTS
GNU/Linux/5.4.0-42-generic/x86_64 Intel(R)/Core(TM)/i7-7600U/CPU/@/2.80GHz
cloud_id/azure -O- --content-on-error https://motd.ubuntu.com
This also verifies again it's using wget instead of curl.
[Regression Potential]
Possible regressions will likely be tied to a difference in behavior between
curl and wget. In fact, one was caught[1] in the development release and the
fix is included here, with a test.
[Other Info]
N/A
1. https://bugs.launchpad.net/bugs/1889117
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/1888572/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1886572] Re: Remove uptime from the motd-news user agent
** Tags removed: verification-needed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to base-files in Ubuntu. https://bugs.launchpad.net/bugs/1886572 Title: Remove uptime from the motd-news user agent Status in base-files package in Ubuntu: Fix Released Status in base-files source package in Xenial: Fix Committed Status in base-files source package in Bionic: Fix Committed Status in base-files source package in Focal: Fix Committed Bug description: [Impact] The uptime value in the user-agent string sent to the motd-news server is unused and not necessary. It should be removed. [Test Case] Inspect the /etc/update-motd.d/50-motd-news script and verify that uptime is no longer used. Previous version: $ grep uptime /etc/update-motd.d/50-motd-news # Some messages may only be pertinent before or after some amount of uptime read up idle < /proc/uptime uptime="uptime/$up/$idle" USER_AGENT="curl/$curl_ver $lsb $platform $cpu $uptime cloud_id/$cloud_id" Updated version: $ grep uptime /etc/update-motd.d/50-motd-news (no output) [Regression Potential] The server side, if it were checking this value, could be surprised by this change. [Other Info] N/A [Original Description] I don't why that was included but it shouldn't be. Please remove it. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/1886572/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1888575] Re: Split motd-news config into a new package
** Tags removed: verification-needed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to base-files in Ubuntu. https://bugs.launchpad.net/bugs/1888575 Title: Split motd-news config into a new package Status in base-files package in Ubuntu: Fix Released Status in ubuntu-meta package in Ubuntu: Fix Released Status in base-files source package in Xenial: Fix Committed Status in ubuntu-meta source package in Xenial: Fix Committed Status in base-files source package in Bionic: Fix Committed Status in ubuntu-meta source package in Bionic: Fix Committed Status in base-files source package in Focal: Fix Committed Status in ubuntu-meta source package in Focal: Fix Committed Status in base-files source package in Groovy: Fix Released Status in ubuntu-meta source package in Groovy: Fix Released Bug description: [Impact] The motd-news script is largely useless for desktop users, as they rarely login via a text console. It makes more sense for server users. We can use package dependencies to have the motd-news script enabled on servers, but disabled on desktops, and still handle upgrades. This is the plan: - move /etc/default/motd-news from base-files into a new binary package (motd-news-config, produced by src:base-files) - have ubuntu-server depend on motd-news-config - have base-files break current ubuntu-server, so that if base-files if upgraded and ubuntu-server is installed, ubuntu-server will also be upgraded to the new version which has the depends on motd-news-config Care must be taken to preserve a changed /etc/default/motd-news when the upgrade installs the new motd-news-config package. For example, on a server that has set ENABLED=0 in /etc/default/motd-news and upgrades to the new base-files and ubuntu-server, and gets the new motd-config- news package, ENABLED=0 must remain set. [Test Case] a) base-files installed, ubuntu-server installed, unmodified /e/d/motd-news apt install base-files - upgrades ubuntu-server - installs motd-news-config - /e/d/motd-news remains, motd-news remains enabled b) base-files installed, ubuntu-server installed, modified /e/d/motd-news apt install base-files - upgrades ubuntu-server - installs motd-news-config - /e/d/motd-news remains with the original modification c) base-files installed, ubuntu-server not installed, unmodified /e/d/motd-news apt install base-files - upgrades base-files - removes /e/d/motd-news - motd-news is disabled d) base-files installed, ubuntu-server not installed, modified /e/d/motd-news apt install base-files - upgrades base-files - /e/d/motd-news gets renamed to backup - motd-news is disabled e) removing motd-news-config will also remove ubuntu-server (since it's a depends, and not a recommends) f) upgrading just ubuntu-server should pull motd-news-config in, and force-upgrade base-files g) Removing motd-news-server leaves /e/d/motd-news around; purging motd-news-server removes the /e/d/motd-news config file h) base-files installed, ubuntu-server installed, removed /e/d/motd-news - apt install base-files - upgrades base-files, upgrades ubuntu-server, installs motd-news-config - /e/d/motd-news is installed with ENABLED=0 i) base-files installed, ubuntu-server NOT installed, removed e/d/motd-news - apt install base-files - base-files is upgraded - no /e/d/motd-news is installed, motd-news remains disabled j) Perform a release upgrade from the previous ubuntu release to the one being tested while having ubuntu-server NOT installed (or use a desktop install). At the end, motd-news should be disabled. Verify with: $ sudo /etc/update-motd.d/50-motd-news --force $ (no output) [Regression Potential] This update is about config file ownership transfer: /e/d/motd-news belonged to base-files, now it belongs to motd-news-config. We tried to handle two important cases here: a) /e/d/motd-news config was changed while it belonged to base-files. For example, an user could have set ENABLED=0. We need to transfer that change to the motd-news-config package when it is installed, otherwise this SRU would jsut re-enabled motd-news. This is handled in d/motd-news-config.postinst's configure case. b) /e/d/motd-news config file was *removed* while it belonged to base-files. In such a case, a normal upgrade of the package (base-files in this example) would not reinstate the file. Much less this upgrade here, which has an explicit rm_conffile maintscript-helper for it. But the motd-news-config package that could be installed in the transaction would place the default config file back, and the default is ENABLED=1. Thus, a system that had motd-news disabled via removing the config file would now have it re-enabled after the upgrade. This was trickier to handle, and we do it in base-files's postinst and motd-news-config's postinst. The dra
[Touch-packages] [Bug 1887210] Re: USB DAC/AMP unselectable from Sound Settings and crashes alsamixer
Looks like it is a kernel driver's problem. Could you install the 18.04's kernel under 20.04 to test? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1887210 Title: USB DAC/AMP unselectable from Sound Settings and crashes alsamixer Status in alsa-driver package in Ubuntu: Confirmed Bug description: I am experiencing the same issue with the same device described in this report comment: https://bugs.launchpad.net/ubuntu/+source/alsa- driver/+bug/1267866/comments/26 The device works as expected with Windows 10 and macOS no drivers required. However, the device is not an option from Ubuntu's sound settings. It is visible in alsamixer, however, it crashes immediately upon selection with 'cannot load mixer controls: Broken pipe'. Here's some more debug information. Let me know if there is anymore I can provide or feel free to redirect me if there is another place this is better reported. Device: Schiit Audio Fulla 3 USB DAC/AMP Kernel version: 5.4.0-40-generic Ubuntu version: 20.04 Alsa debug output: http://alsa- project.org/db/?f=3f494b2155bdde7f5ee0e52240da77468bcb `dmesg -w` output upon re-plugging in the device: [ 895.624302] usb 3-2.3: new high-speed USB device number 8 using xhci_hcd [ 895.739125] usb 3-2.3: New USB device found, idVendor=30be, idProduct=0100, bcdDevice= 1.02 [ 895.739129] usb 3-2.3: New USB device strings: Mfr=1, Product=2, SerialNumber=0 [ 895.739131] usb 3-2.3: Product: I'm Fulla Schiit [ 895.739133] usb 3-2.3: Manufacturer: Schiit Audio [ 896.076914] input: Schiit Audio I'm Fulla Schiit as /devices/pci:00/:00:07.1/:11:00.3/usb3/3-2/3-2.3/3-2.3:1.3/0003:30BE:0100.0007/input/input20 [ 896.136457] hid-generic 0003:30BE:0100.0007: input,hidraw5: USB HID v1.00 Device [Schiit Audio I'm Fulla Schiit] on usb-:11:00.3-2.3/input3 [ 896.228480] audit: type=1107 audit(1594446870.681:57): pid=1286 uid=105 auid=4294967295 ses=4294967295 msg='apparmor="DENIED" operation="dbus_signal" bus="system" path="/org/freedesktop/NetworkManager" interface="org.freedesktop.NetworkManager" member="CheckPermissions" name=":1.8" mask="receive" pid=10228 label="snap.spotify.spotify" peer_pid=1287 peer_label="unconfined" exe="/usr/bin/dbus-daemon" sauid=105 hostname=? addr=? terminal=?' [ 896.238190] usb 3-2.3: cannot get ctl value: req = 0x81, wValue = 0x100, wIndex = 0x1100, type = 1 [ 896.298659] usb 3-2.3: cannot get ctl value: req = 0x81, wValue = 0x100, wIndex = 0x1100, type = 1 [ 896.427249] usb 3-2.3: cannot get ctl value: req = 0x81, wValue = 0x100, wIndex = 0x1100, type = 1 [ 896.618498] usb 3-2.3: cannot get ctl value: req = 0x81, wValue = 0x100, wIndex = 0x1100, type = 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1887210/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1893561] Re: font size
*** This bug is a duplicate of bug 1892440 *** https://bugs.launchpad.net/bugs/1892440 Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 1892440, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find. ** This bug has been marked a duplicate of bug 1892440 Shell text is too small in mutter 3.36.4-0ubuntu0.20.04.2 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1893561 Title: font size Status in xorg package in Ubuntu: New Bug description: Hi, everytime i turn on my pc (connected via HDMI to an AV-ampli sorround system) i have to set the text size to "large" then again "normal" to see the text above the application logo or in the main bar; if not the text are extremely tiny and can't be read. Sorry for my english. Have a good day. Best regards ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-45.49-generic 5.4.55 Uname: Linux 5.4.0-45-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] È una directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 390.138 Thu May 14 01:01:53 PDT 2020 GCC version: gcc version 9.3.0 (Ubuntu 9.3.0-10ubuntu2) ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 BootLog: Error: [Errno 13] Permesso negato: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Aug 30 17:16:35 2020 DistUpgraded: 2020-05-11 23:30:24,176 DEBUG icon theme changed, re-reading DistroCodename: focal DistroVariant: ubuntu DkmsStatus: nvidia, 390.138, 5.4.0-40-generic, x86_64: installed nvidia, 390.138, 5.4.0-42-generic, x86_64: installed nvidia, 390.138, 5.4.0-45-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: NVIDIA Corporation GF106 [GeForce GTS 450] [10de:0dc4] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Point of View BV GF106 [GeForce GTS 450] [1acc:45a1] InstallationDate: Installed on 2020-05-11 (110 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: System manufacturer System Product Name ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-45-generic root=UUID=18184fdf-eea7-4e9d-bf94-7262aee7e822 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to focal on 2020-05-11 (110 days ago) dmi.bios.date: 06/22/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0703 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: P8H61-M LE 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.:bvr0703:bd06/22/2011:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP8H61-MLE:rvrRevx.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: To be filled by O.E.M. dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.2 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/xorg/+bug/1893561/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1893566] Re: [MS-7A40, Realtek ALC887-VD, Green Headphone Out, Front] fails if headphone not plugged in on bootl
Please plug in the headphone, then run alsa-info.sh and upload the alsa- info.txt BTW, what do you mean "Sound works for a while, then breaks"? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1893566 Title: [MS-7A40, Realtek ALC887-VD, Green Headphone Out, Front] fails if headphone not plugged in on bootl Status in alsa-driver package in Ubuntu: New Bug description: [MS-7A40, Realtek ALC887-VD, Green Headphone Out, Front] fails if headphone is not plugged in on boot. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 NonfreeKernelModules: lkp_Ubuntu_5_4_0_42_46_generic_70 nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: mea1935 F pulseaudio /dev/snd/pcmC1D0c: mea1935 F...m pulseaudio /dev/snd/controlC0: mea1935 F pulseaudio /dev/snd/controlC2: mea1935 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Aug 30 12:29:20 2020 InstallationDate: Installed on 2020-07-17 (44 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_Card: Starship/Matisse HD Audio Controller - HD-Audio Generic Symptom_Jack: Green Headphone Out, Front Symptom_PulseAudioLog: Aug 30 11:07:51 mea-MS-7A40 dbus-daemon[908]: [system] Activating via systemd: service name='org.freedesktop.RealtimeKit1' unit='rtkit-daemon.service' requested by ':1.28' (uid=125 pid=1178 comm="/usr/bin/pulseaudio --daemonize=no --log-target=jo" label="unconfined") Symptom_Type: Sound works for a while, then breaks Title: [MS-7A40, Realtek ALC887-VD, Green Headphone Out, Front] fails after a while UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/12/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: A.B0 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B450I GAMING PLUS AC (MS-7A40) dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: 2.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: 2.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrA.B0:bd11/12/2019:svnMicro-StarInternationalCo.,Ltd.:pnMS-7A40:pvr2.0:rvnMicro-StarInternationalCo.,Ltd.:rnB450IGAMINGPLUSAC(MS-7A40):rvr2.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr2.0: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7A40 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 2.0 dmi.sys.vendor: Micro-Star International Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1893566/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1886112] Re: Enabling DMESG_RESTRICT in Groovy Onward
As per my most recent email to ubuntu-devel, I am marking the changes to util-linux as Won't Fix. Relevant mailing list discussion (for future reference): Ansgar responded on debian-devel mentioning that adding cap_syslog to dmesg enables the user to clear the kernel log buffer: https://lists.debian.org/debian-devel/2020/08/msg00121.html>> > That grants additional rights to the `adm` group that it did not have > before, for example to clear the dmesg buffer: > > $ dmesg --clear > > works after adding `cap_syslog` to the dmesg binary whereas it did not > work before. Chris Hofstaedtler, the maintainer of util-linux, mentions that granting such powers to members of adm is more or less unacceptable: https://lists.ubuntu.com/archives/ubuntu-devel/2020-August/041151.html > Re-enabling dmesg for the %adm group does not seem to add value for > Debian now, and granting the --clear (and other) permissions seems > to be too much. This was further acked by Steve Langasek: https://lists.ubuntu.com/archives/ubuntu-devel/2020-August/041152.html > I agree, and on that basis I also do not believe we should include this > change to util-linux in Ubuntu. Because of this, I will no longer pursue opening dmesg up to users in the adm group, or at least until cap_syslog gets a read-only sister capability. Hopefully Ubuntu users won't be too inconvenienced by having to run dmesg as superuser. Users can always turn off the behaviour, by setting "kernel.dmesg_restrict = 0" in /etc/sysctl.d/10-kernel-hardening.conf ** Changed in: util-linux (Ubuntu Groovy) Status: In Progress => Won't Fix -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to util-linux in Ubuntu. https://bugs.launchpad.net/bugs/1886112 Title: Enabling DMESG_RESTRICT in Groovy Onward Status in linux package in Ubuntu: Fix Released Status in procps package in Ubuntu: In Progress Status in util-linux package in Ubuntu: In Progress Status in linux source package in Groovy: Fix Released Status in procps source package in Groovy: In Progress Status in util-linux source package in Groovy: Won't Fix Bug description: [Impact] This bug implements the enablement of CONFIG_SECURITY_DMESG_RESTRICT feature by default for Groovy onward, proposed to ubuntu-devel: https://lists.ubuntu.com/archives/ubuntu-devel/2020-June/041063.html The kernel log buffer contains a wealth of sensitive information, such as detailed call traces and kernel addresses found in register dumps in kernel oops messages. Exploit developers and attackers can leverage these information leaks to get past KASLR, and they can use the kernel log buffer to get instant feedback on their privilege escalation attacks, as failures will be shown as further oops messages, which attackers can use to fix and tune their programs until they work. Currently, if I create a new, unprivileged user on a Focal system, they cannot access /var/log/kern.log, /var/log/syslog or see system events in journalctl. But yet, they are given free reign to the kernel log buffer. $ sudo adduser dave $ su dave $ groups dave $ cat /var/log/kern.log cat: /var/log/kern.log: Permission denied $ cat /var/log/syslog cat: /var/log/syslog: Permission denied $ journalctl Hint: You are currently not seeing messages from other users and the system. Users in groups 'adm', 'systemd-journal' can see all messages. Pass -q to turn off this notice. Jun 16 23:44:59 ubuntu systemd[2328]: Reached target Main User Target. Jun 16 23:44:59 ubuntu systemd[2328]: Startup finished in 69ms. $ dmesg [0.00] Linux version 5.4.0-34-generic (buildd at lcy01-amd64-014) (gcc version 9.3.0 (Ubuntu 9.3.0-10ubuntu2)) #38-Ubuntu SMP Mon May 25 15:46:55 UTC 2020 (Ubuntu 5.4.0-34.38-generic 5.4.41) [0.00] Command line: BOOT_IMAGE=/boot/vmlinuz-5.4.0-34-generic root=UUID=f9f909c3-782a-43c2-a59d-c789656b4188 ro ... I propose that we restrict access to dmesg to users in group 'adm' like so: 1) Add kernel.dmesg_restrict = 1 to /etc/sysctl.d/10-kernel-hardening.conf 2) Following changes to /bin/dmesg permissions in package 'util-linux' - Ownership changes to root:adm - Permissions changed to 0750 (-rwxr-x---) - Add cap_syslog capability to binary. For most users, they will use the initial admin account, which is in the 'adm' group already, and will see no impact to these changes. If a log scraper type program needs access to dmesg, the user the daemon runs as can simply be added to the 'adm' group. [Testcase] Currently, all users can run /usr/bin/dmesg to view the kernel log buffer: $ dmesg [0.00] Linux version 5.4.0-34-generic (buildd at lcy01-amd64-014) (gcc version 9.3.0 (Ubuntu 9.3.0-10ubuntu2)) #38-Ubuntu SMP Mon May 25 15:46:55 UTC 2020 (Ubuntu 5.4.0-34.38-generic 5.4.41) [0.00] Command line: BOOT_
[Touch-packages] [Bug 1886112] Re: Enabling DMESG_RESTRICT in Groovy Onward
As 5.8.0-16-generic has now been released to the -release pocket, CONFIG_SECURITY_DMESG_RESTRICT is now enabled in Groovy. Marking the changes to the kernel as Fix Released. ** Changed in: linux (Ubuntu Groovy) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to util-linux in Ubuntu. https://bugs.launchpad.net/bugs/1886112 Title: Enabling DMESG_RESTRICT in Groovy Onward Status in linux package in Ubuntu: Fix Released Status in procps package in Ubuntu: In Progress Status in util-linux package in Ubuntu: In Progress Status in linux source package in Groovy: Fix Released Status in procps source package in Groovy: In Progress Status in util-linux source package in Groovy: Won't Fix Bug description: [Impact] This bug implements the enablement of CONFIG_SECURITY_DMESG_RESTRICT feature by default for Groovy onward, proposed to ubuntu-devel: https://lists.ubuntu.com/archives/ubuntu-devel/2020-June/041063.html The kernel log buffer contains a wealth of sensitive information, such as detailed call traces and kernel addresses found in register dumps in kernel oops messages. Exploit developers and attackers can leverage these information leaks to get past KASLR, and they can use the kernel log buffer to get instant feedback on their privilege escalation attacks, as failures will be shown as further oops messages, which attackers can use to fix and tune their programs until they work. Currently, if I create a new, unprivileged user on a Focal system, they cannot access /var/log/kern.log, /var/log/syslog or see system events in journalctl. But yet, they are given free reign to the kernel log buffer. $ sudo adduser dave $ su dave $ groups dave $ cat /var/log/kern.log cat: /var/log/kern.log: Permission denied $ cat /var/log/syslog cat: /var/log/syslog: Permission denied $ journalctl Hint: You are currently not seeing messages from other users and the system. Users in groups 'adm', 'systemd-journal' can see all messages. Pass -q to turn off this notice. Jun 16 23:44:59 ubuntu systemd[2328]: Reached target Main User Target. Jun 16 23:44:59 ubuntu systemd[2328]: Startup finished in 69ms. $ dmesg [0.00] Linux version 5.4.0-34-generic (buildd at lcy01-amd64-014) (gcc version 9.3.0 (Ubuntu 9.3.0-10ubuntu2)) #38-Ubuntu SMP Mon May 25 15:46:55 UTC 2020 (Ubuntu 5.4.0-34.38-generic 5.4.41) [0.00] Command line: BOOT_IMAGE=/boot/vmlinuz-5.4.0-34-generic root=UUID=f9f909c3-782a-43c2-a59d-c789656b4188 ro ... I propose that we restrict access to dmesg to users in group 'adm' like so: 1) Add kernel.dmesg_restrict = 1 to /etc/sysctl.d/10-kernel-hardening.conf 2) Following changes to /bin/dmesg permissions in package 'util-linux' - Ownership changes to root:adm - Permissions changed to 0750 (-rwxr-x---) - Add cap_syslog capability to binary. For most users, they will use the initial admin account, which is in the 'adm' group already, and will see no impact to these changes. If a log scraper type program needs access to dmesg, the user the daemon runs as can simply be added to the 'adm' group. [Testcase] Currently, all users can run /usr/bin/dmesg to view the kernel log buffer: $ dmesg [0.00] Linux version 5.4.0-34-generic (buildd at lcy01-amd64-014) (gcc version 9.3.0 (Ubuntu 9.3.0-10ubuntu2)) #38-Ubuntu SMP Mon May 25 15:46:55 UTC 2020 (Ubuntu 5.4.0-34.38-generic 5.4.41) [0.00] Command line: BOOT_IMAGE=/boot/vmlinuz-5.4.0-34-generic root=UUID=f9f909c3-782a-43c2-a59d-c789656b4188 ro ... When the changes are applied, the default admin user will be able to view dmesg (since they are in group 'adm'), while new unprivileged users will not. Test packages are available in the following ppa: https://launchpad.net/~mruffell/+archive/ubuntu/lp1886112-test $ whoami ubuntu $ groups ubuntu adm cdrom sudo dip plugdev $ dmesg [0.00] Linux version 5.4.0-34-generic (buildd at lcy01-amd64-014) (gcc version 9.3.0 (Ubuntu 9.3.0-10ubuntu2)) #38-Ubuntu SMP Mon May 25 15:46:55 UTC 2020 (Ubuntu 5.4.0-34.38-generic 5.4.41) [0.00] Command line: BOOT_IMAGE=/boot/vmlinuz-5.4.0-34-generic root=UUID=f9f909c3-782a-43c2-a59d-c789656b4188 ro ... $ sudo adduser dave $ su dave $ groups dave $ dmesg -bash: /usr/bin/dmesg: Permission denied [Regression Potential] Some users or log scraper type programs may need to view the kernel log buffer, or have access to dmesg. In this case, the underlying service user would need to be added to the 'adm' group. Users have the ability to disable DMESG_RESTRICT by changing kernel.dmesg_restrict sysctl in /etc/sysctl.d/10-kernel-hardening.conf from '1' to '0', followed by a reboot. To manage notifications about this bug go to: https://bugs.
[Touch-packages] [Bug 1887210] Re: USB DAC/AMP unselectable from Sound Settings and crashes alsamixer
I am able to view the device in Sound Settings, but when it attempts to play any audio, it crashes immediately. In my case I am behind a KVM, but my Windows device and my Ubuntu 18.04 server work perfectly, only my 20.04 desktop crashes. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1887210 Title: USB DAC/AMP unselectable from Sound Settings and crashes alsamixer Status in alsa-driver package in Ubuntu: Confirmed Bug description: I am experiencing the same issue with the same device described in this report comment: https://bugs.launchpad.net/ubuntu/+source/alsa- driver/+bug/1267866/comments/26 The device works as expected with Windows 10 and macOS no drivers required. However, the device is not an option from Ubuntu's sound settings. It is visible in alsamixer, however, it crashes immediately upon selection with 'cannot load mixer controls: Broken pipe'. Here's some more debug information. Let me know if there is anymore I can provide or feel free to redirect me if there is another place this is better reported. Device: Schiit Audio Fulla 3 USB DAC/AMP Kernel version: 5.4.0-40-generic Ubuntu version: 20.04 Alsa debug output: http://alsa- project.org/db/?f=3f494b2155bdde7f5ee0e52240da77468bcb `dmesg -w` output upon re-plugging in the device: [ 895.624302] usb 3-2.3: new high-speed USB device number 8 using xhci_hcd [ 895.739125] usb 3-2.3: New USB device found, idVendor=30be, idProduct=0100, bcdDevice= 1.02 [ 895.739129] usb 3-2.3: New USB device strings: Mfr=1, Product=2, SerialNumber=0 [ 895.739131] usb 3-2.3: Product: I'm Fulla Schiit [ 895.739133] usb 3-2.3: Manufacturer: Schiit Audio [ 896.076914] input: Schiit Audio I'm Fulla Schiit as /devices/pci:00/:00:07.1/:11:00.3/usb3/3-2/3-2.3/3-2.3:1.3/0003:30BE:0100.0007/input/input20 [ 896.136457] hid-generic 0003:30BE:0100.0007: input,hidraw5: USB HID v1.00 Device [Schiit Audio I'm Fulla Schiit] on usb-:11:00.3-2.3/input3 [ 896.228480] audit: type=1107 audit(1594446870.681:57): pid=1286 uid=105 auid=4294967295 ses=4294967295 msg='apparmor="DENIED" operation="dbus_signal" bus="system" path="/org/freedesktop/NetworkManager" interface="org.freedesktop.NetworkManager" member="CheckPermissions" name=":1.8" mask="receive" pid=10228 label="snap.spotify.spotify" peer_pid=1287 peer_label="unconfined" exe="/usr/bin/dbus-daemon" sauid=105 hostname=? addr=? terminal=?' [ 896.238190] usb 3-2.3: cannot get ctl value: req = 0x81, wValue = 0x100, wIndex = 0x1100, type = 1 [ 896.298659] usb 3-2.3: cannot get ctl value: req = 0x81, wValue = 0x100, wIndex = 0x1100, type = 1 [ 896.427249] usb 3-2.3: cannot get ctl value: req = 0x81, wValue = 0x100, wIndex = 0x1100, type = 1 [ 896.618498] usb 3-2.3: cannot get ctl value: req = 0x81, wValue = 0x100, wIndex = 0x1100, type = 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1887210/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1887210] Re: USB DAC/AMP unselectable from Sound Settings and crashes alsamixer
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: alsa-driver (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1887210 Title: USB DAC/AMP unselectable from Sound Settings and crashes alsamixer Status in alsa-driver package in Ubuntu: Confirmed Bug description: I am experiencing the same issue with the same device described in this report comment: https://bugs.launchpad.net/ubuntu/+source/alsa- driver/+bug/1267866/comments/26 The device works as expected with Windows 10 and macOS no drivers required. However, the device is not an option from Ubuntu's sound settings. It is visible in alsamixer, however, it crashes immediately upon selection with 'cannot load mixer controls: Broken pipe'. Here's some more debug information. Let me know if there is anymore I can provide or feel free to redirect me if there is another place this is better reported. Device: Schiit Audio Fulla 3 USB DAC/AMP Kernel version: 5.4.0-40-generic Ubuntu version: 20.04 Alsa debug output: http://alsa- project.org/db/?f=3f494b2155bdde7f5ee0e52240da77468bcb `dmesg -w` output upon re-plugging in the device: [ 895.624302] usb 3-2.3: new high-speed USB device number 8 using xhci_hcd [ 895.739125] usb 3-2.3: New USB device found, idVendor=30be, idProduct=0100, bcdDevice= 1.02 [ 895.739129] usb 3-2.3: New USB device strings: Mfr=1, Product=2, SerialNumber=0 [ 895.739131] usb 3-2.3: Product: I'm Fulla Schiit [ 895.739133] usb 3-2.3: Manufacturer: Schiit Audio [ 896.076914] input: Schiit Audio I'm Fulla Schiit as /devices/pci:00/:00:07.1/:11:00.3/usb3/3-2/3-2.3/3-2.3:1.3/0003:30BE:0100.0007/input/input20 [ 896.136457] hid-generic 0003:30BE:0100.0007: input,hidraw5: USB HID v1.00 Device [Schiit Audio I'm Fulla Schiit] on usb-:11:00.3-2.3/input3 [ 896.228480] audit: type=1107 audit(1594446870.681:57): pid=1286 uid=105 auid=4294967295 ses=4294967295 msg='apparmor="DENIED" operation="dbus_signal" bus="system" path="/org/freedesktop/NetworkManager" interface="org.freedesktop.NetworkManager" member="CheckPermissions" name=":1.8" mask="receive" pid=10228 label="snap.spotify.spotify" peer_pid=1287 peer_label="unconfined" exe="/usr/bin/dbus-daemon" sauid=105 hostname=? addr=? terminal=?' [ 896.238190] usb 3-2.3: cannot get ctl value: req = 0x81, wValue = 0x100, wIndex = 0x1100, type = 1 [ 896.298659] usb 3-2.3: cannot get ctl value: req = 0x81, wValue = 0x100, wIndex = 0x1100, type = 1 [ 896.427249] usb 3-2.3: cannot get ctl value: req = 0x81, wValue = 0x100, wIndex = 0x1100, type = 1 [ 896.618498] usb 3-2.3: cannot get ctl value: req = 0x81, wValue = 0x100, wIndex = 0x1100, type = 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1887210/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1528422] Re: Additional drivers reports the wrong driver in use
Similar issue here: I was using kernel 5.4.0.42.46 with nvidia-drivers-440, installed 5.8.3, booted into the new kernel and the graphics were way worse. Software & Updates still has the radio button selected for nvidia, see attached, this looked terrible stretched across a 3440*1440 screen. but: hwinfo --gfxcard Driver Info #0: Driver Status: nvidiafb is not active Driver Activation Cmd: "modprobe nvidiafb" Driver Info #1: Driver Status: nouveau is not active Driver Activation Cmd: "modprobe nouveau" Config Status: cfg=new, avail=yes, need=no, active=unknown Then, Selected nouveau driver, apply, hwinfo says both drivers still inactive, restarted, looks good (hi res), nvidia settings absent from start menu settings, nouveau radio button highlit in software & updates, hwinfo --gfxcard Driver Info #0: Driver Status: nvidiafb is not active Driver Activation Cmd: "modprobe nvidiafb" Driver Info #1: Driver Status: nouveau is active Driver Activation Cmd: "modprobe nouveau" Config Status: cfg=new, avail=yes, need=no, active=unknown Attached to: #7 (PCI bridge) So nouveau is being used, graphics problem fixed, nvidia definitely the culprit of the graphics issues which had been plaguing me for about a year. I'll file a bug with them, however part of what took me so long to diagnose this was that I thought the nouveau drivers were broken since I could only get 1024*768. I spent hours trying to fix that, to no avail. Turns out there was nothing wrong with them, they just weren't selected. I didn't know this because I didn't think to check, I just believed the radio button. Feasibly the selected item is highlit until changed in the GUI or backend by the user, but it doesn't do an internal check (hwinfo or otherwise) to confirm that the driver it thinks is selected, is selected? Thanks ** Attachment added: "screenshot" https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1528422/+attachment/5405908/+files/Kernel5.8.3.NolagLowResMoreDeets.png -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1528422 Title: Additional drivers reports the wrong driver in use Status in software-properties package in Ubuntu: Confirmed Bug description: See attached screenshot - it's reporting the AMD driver is in use, while in reality it is the Intel driver. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: software-properties-gtk 0.96.13.1 ProcVersionSignature: Ubuntu 4.2.0-22.27-generic 4.2.6 Uname: Linux 4.2.0-22-generic x86_64 ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 CurrentDesktop: Unity Date: Tue Dec 22 12:45:42 2015 InstallationDate: Installed on 2014-06-26 (543 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) PackageArchitecture: all SourcePackage: software-properties UpgradeStatus: Upgraded to wily on 2015-10-26 (56 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1528422/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1528422] Re: Additional drivers reports the wrong driver in use
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: software-properties (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1528422 Title: Additional drivers reports the wrong driver in use Status in software-properties package in Ubuntu: Confirmed Bug description: See attached screenshot - it's reporting the AMD driver is in use, while in reality it is the Intel driver. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: software-properties-gtk 0.96.13.1 ProcVersionSignature: Ubuntu 4.2.0-22.27-generic 4.2.6 Uname: Linux 4.2.0-22-generic x86_64 ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 CurrentDesktop: Unity Date: Tue Dec 22 12:45:42 2015 InstallationDate: Installed on 2014-06-26 (543 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) PackageArchitecture: all SourcePackage: software-properties UpgradeStatus: Upgraded to wily on 2015-10-26 (56 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1528422/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1873429] Re: Problem with printing in 20.04 version
I downloaded from the espson support site https://download.ebz.epson.net/dsc/search/01/search/?OSC=LX the latest drive epson-printer-utility_1.1.1-1lsb3.2_amd64.deb installed new printer and it worked! Hope this help... -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1873429 Title: Problem with printing in 20.04 version Status in cups package in Ubuntu: Incomplete Bug description: In previous 19.10 my Epson Stylus CX3600 both prints & scans fine. In 20.04 it scans fine, but in print mode the process banners show the job is sent to the printer, then printing is complete. However there is no print output. I reinstalled the Epson print drivers but without success. I'm staying on 20.04, but by running Ubuntu 19.10 from a USB drive the printing issue is solved. The Epson is recognised and my documents print and scan fine. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-control-center 1:3.36.1-1ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-24.28-generic 5.4.30 Uname: Linux 5.4.0-24-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Apr 17 10:59:10 2020 InstallationDate: Installed on 2019-12-10 (128 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) SourcePackage: gnome-control-center UpgradeStatus: Upgraded to focal on 2020-04-01 (15 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1873429/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1873429] Re: Problem with printing in 20.04 version
Same problem to me. EPSON BX305F I scans without problems. I tried to reinstall as new printer and to update the driver. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1873429 Title: Problem with printing in 20.04 version Status in cups package in Ubuntu: Incomplete Bug description: In previous 19.10 my Epson Stylus CX3600 both prints & scans fine. In 20.04 it scans fine, but in print mode the process banners show the job is sent to the printer, then printing is complete. However there is no print output. I reinstalled the Epson print drivers but without success. I'm staying on 20.04, but by running Ubuntu 19.10 from a USB drive the printing issue is solved. The Epson is recognised and my documents print and scan fine. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-control-center 1:3.36.1-1ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-24.28-generic 5.4.30 Uname: Linux 5.4.0-24-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Apr 17 10:59:10 2020 InstallationDate: Installed on 2019-12-10 (128 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) SourcePackage: gnome-control-center UpgradeStatus: Upgraded to focal on 2020-04-01 (15 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1873429/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1893567] [NEW] Login name ellipsis/dot-dot-dot in GDM
Public bug reported: Recently, my Ubuntu 20.04.1 login screen started showing my username as a dot-dot-dot, with a vertical scroll, despite being my user name only four letters (i.e.: kopa). It is the only user account in the system too. I've attached a screenshot of the login screen where the issue can be seen. GDM here is version 3.34.1-1ubuntu1. I'm running Xorg (no wayland). No changes to its configuration were made. I can provide whatever extra information that could be useful in diagnosing this problem. Thank you. ** Affects: gdm3 (Ubuntu) Importance: Undecided Status: New ** Tags: ellipsis focal gdm login ** Attachment added: "gdm_username_bug.png" https://bugs.launchpad.net/bugs/1893567/+attachment/5405847/+files/gdm_username_bug.png ** Description changed: Recently, my Ubuntu 20.04.1 login screen started showing my username as a dot-dot-dot, with a vertical scroll, despite being my user name only four letters (i.e.: kopa). It is the only user account in the system too. I've attached a screenshot of the login screen where the issue can be seen. - GDM here is version 3.34.1-1ubuntu1. No changes to its configuration - were made. + GDM here is version 3.34.1-1ubuntu1. I'm running Xorg (no wayland). No + changes to its configuration were made. I can provide whatever extra information that could be useful in diagnosing this problem. Thank you. ** Package changed: alsa-driver (Ubuntu) => gdm3 (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1893567 Title: Login name ellipsis/dot-dot-dot in GDM Status in gdm3 package in Ubuntu: New Bug description: Recently, my Ubuntu 20.04.1 login screen started showing my username as a dot-dot-dot, with a vertical scroll, despite being my user name only four letters (i.e.: kopa). It is the only user account in the system too. I've attached a screenshot of the login screen where the issue can be seen. GDM here is version 3.34.1-1ubuntu1. I'm running Xorg (no wayland). No changes to its configuration were made. I can provide whatever extra information that could be useful in diagnosing this problem. Thank you. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1893567/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1893566] [NEW] [MS-7A40, Realtek ALC887-VD, Green Headphone Out, Front] fails if headphone not plugged in on bootl
Public bug reported: [MS-7A40, Realtek ALC887-VD, Green Headphone Out, Front] fails if headphone is not plugged in on boot. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 NonfreeKernelModules: lkp_Ubuntu_5_4_0_42_46_generic_70 nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: mea1935 F pulseaudio /dev/snd/pcmC1D0c: mea1935 F...m pulseaudio /dev/snd/controlC0: mea1935 F pulseaudio /dev/snd/controlC2: mea1935 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Aug 30 12:29:20 2020 InstallationDate: Installed on 2020-07-17 (44 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_Card: Starship/Matisse HD Audio Controller - HD-Audio Generic Symptom_Jack: Green Headphone Out, Front Symptom_PulseAudioLog: Aug 30 11:07:51 mea-MS-7A40 dbus-daemon[908]: [system] Activating via systemd: service name='org.freedesktop.RealtimeKit1' unit='rtkit-daemon.service' requested by ':1.28' (uid=125 pid=1178 comm="/usr/bin/pulseaudio --daemonize=no --log-target=jo" label="unconfined") Symptom_Type: Sound works for a while, then breaks Title: [MS-7A40, Realtek ALC887-VD, Green Headphone Out, Front] fails after a while UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/12/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: A.B0 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B450I GAMING PLUS AC (MS-7A40) dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: 2.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: 2.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrA.B0:bd11/12/2019:svnMicro-StarInternationalCo.,Ltd.:pnMS-7A40:pvr2.0:rvnMicro-StarInternationalCo.,Ltd.:rnB450IGAMINGPLUSAC(MS-7A40):rvr2.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr2.0: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7A40 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 2.0 dmi.sys.vendor: Micro-Star International Co., Ltd. ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1893566 Title: [MS-7A40, Realtek ALC887-VD, Green Headphone Out, Front] fails if headphone not plugged in on bootl Status in alsa-driver package in Ubuntu: New Bug description: [MS-7A40, Realtek ALC887-VD, Green Headphone Out, Front] fails if headphone is not plugged in on boot. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 NonfreeKernelModules: lkp_Ubuntu_5_4_0_42_46_generic_70 nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: mea1935 F pulseaudio /dev/snd/pcmC1D0c: mea1935 F...m pulseaudio /dev/snd/controlC0: mea1935 F pulseaudio /dev/snd/controlC2: mea1935 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Aug 30 12:29:20 2020 InstallationDate: Installed on 2020-07-17 (44 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_Card: Starship/Matisse HD Audio Controller - HD-Audio Generic Symptom_Jack: Green Headphone Out, Front Symptom_PulseAudioLog: Aug 30 11:07:51 mea-MS-7A40 dbus-daemon[908]: [system] Activating via systemd: service name='org.freedesktop.RealtimeKit1' unit='rtkit-daemon.service' requested by ':1.28' (uid=125 pid=1178 comm="/usr/bin/pulseaudio --daemonize=no --log-target=jo" label="unconfined") Symptom_Type: Sound works for a while, then breaks Title: [MS-7A40, Realtek ALC887-VD, Green Headphone Out, Front] fails after a while UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/12/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: A.B0 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B450I GAMING PLUS AC (MS-7A40) dmi.board.vendor: Micro-Star Int
[Touch-packages] [Bug 1893561] [NEW] font size
Public bug reported: Hi, everytime i turn on my pc (connected via HDMI to an AV-ampli sorround system) i have to set the text size to "large" then again "normal" to see the text above the application logo or in the main bar; if not the text are extremely tiny and can't be read. Sorry for my english. Have a good day. Best regards ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-45.49-generic 5.4.55 Uname: Linux 5.4.0-45-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] È una directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 390.138 Thu May 14 01:01:53 PDT 2020 GCC version: gcc version 9.3.0 (Ubuntu 9.3.0-10ubuntu2) ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 BootLog: Error: [Errno 13] Permesso negato: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Aug 30 17:16:35 2020 DistUpgraded: 2020-05-11 23:30:24,176 DEBUG icon theme changed, re-reading DistroCodename: focal DistroVariant: ubuntu DkmsStatus: nvidia, 390.138, 5.4.0-40-generic, x86_64: installed nvidia, 390.138, 5.4.0-42-generic, x86_64: installed nvidia, 390.138, 5.4.0-45-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: NVIDIA Corporation GF106 [GeForce GTS 450] [10de:0dc4] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Point of View BV GF106 [GeForce GTS 450] [1acc:45a1] InstallationDate: Installed on 2020-05-11 (110 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: System manufacturer System Product Name ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-45-generic root=UUID=18184fdf-eea7-4e9d-bf94-7262aee7e822 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to focal on 2020-05-11 (110 days ago) dmi.bios.date: 06/22/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0703 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: P8H61-M LE 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.:bvr0703:bd06/22/2011:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP8H61-MLE:rvrRevx.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: To be filled by O.E.M. dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal fonts ubuntu -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1893561 Title: font size Status in xorg package in Ubuntu: New Bug description: Hi, everytime i turn on my pc (connected via HDMI to an AV-ampli sorround system) i have to set the text size to "large" then again "normal" to see the text above the application logo or in the main bar; if not the text are extremely tiny and can't be read. Sorry for my english. Have a good day. Best regards ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-45.49-generic 5.4.55 Uname: Linux 5.4.0-45-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] È una directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 390.138 Thu May 14 01:01:53 PDT 2020 GCC version: gcc version 9.3.0 (Ubuntu 9.3.0-10ubuntu2) ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 BootLog: Error: [Errno 13] Permesso negato: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Aug 30 17:
[Touch-packages] [Bug 1891407] Re: [journalctl --follow] Wi-Fi auto disconnect randomly, unable fix and better uninstall ubuntu (updated: including PCIe Bus Error)
** Changed in: network-manager (Ubuntu)
Status: Incomplete => New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1891407
Title:
[journalctl --follow] Wi-Fi auto disconnect randomly, unable fix and
better uninstall ubuntu (updated: including PCIe Bus Error)
Status in network-manager package in Ubuntu:
New
Bug description:
Ubuntu 20.04.01 LTS (newly installed)
(Moved that device from windows 10, didnt had issue in it)
HP 15T-au000 device.
[lspci]Network controller: Realtek Semiconductor Co., Ltd. RTL8723BE
PCIe Wireless Network Adapter
[lspci | awk '/[Nn]et/ {print $1}' | xargs -i% lspci -ks %]
02:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL810xE PCI
Express Fast Ethernet controller (rev 0a)
DeviceName: Realtek PCIe FE Family Controller
Subsystem: Hewlett-Packard Company RTL810xE PCI Express Fast Ethernet
controller
Kernel driver in use: r8169
Kernel modules: r8169
03:00.0 Network controller: Realtek Semiconductor Co., Ltd. RTL8723BE PCIe
Wireless Network Adapter
DeviceName: Realtek Sanji2 RTL8723BE b/g/n 1x1 + BT 4 LE PCIe+USB M.2
Subsystem: Hewlett-Packard Company RTL8723BE PCIe Wireless Network Adapter
Kernel driver in use: rtl8723be
Kernel modules: rtl8723be
Wi-Fi key is correct (i can use internet to visit sites, watch videos in
youtube etc) however randomly disconnect and appear window to re-connect
(sometimes constantly disconnect)
No network related change has made (IPv6 disabled through settings)
Only one SSID is in use: Dialog 4G
I ran `journalctl --follow` and below is the log. let me know if
required to provide further details
~Updated~
There also `PCIe Bus Error: severity=Corrected, type=Physical Layer` occur
due that wifi card - RTL8723BE
It usually appear when boot the device (before login screen) and currently i
suppressed that issue by adding `pci=noaer` to grub (alternative pci=nomsi)
I found https://github.com/rtlwifi-linux/rtlwifi_new and
https://github.com/silenoth/rtlwifi_new-extended it contain
'RTL8723BE' however most people had used them due wifi card does not
display or unable connect but i dont have such issue and users have
reported installation issues then didnt consider to put to my machine.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1891407/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1593749] Re: puppet apply with pip provider gives 403 error
** Package changed: dbus (Ubuntu) => puppet (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to dbus in Ubuntu.
https://bugs.launchpad.net/bugs/1593749
Title:
puppet apply with pip provider gives 403 error
Status in puppet package in Ubuntu:
New
Bug description:
Since some time on 16/06/2016 Puppet manifests that use the "pip"
provider to manage Python packages are failing with a 403 error, on
(at least) Ubuntu 14.04.4 LTS, when processed using "puppet apply...".
puppet version is 3.4.3-1ubuntu1.1
python-pip version is 1.5.4-1ubuntu3
python version is 2.7.5-5ubuntu3
On the command line:
pip install --upgrade rarfile
returns:
Requirement already up-to-date: rarfile in
/usr/local/lib/python2.7/dist-packages
Cleaning up...
However, creating init.pp containing:
package { 'rarfile':
ensure => 'latest',
provider => 'pip',
}
and running:
puppet apply ./init.pp
returns:
Notice: Compiled catalog for narsaq.isys.bris.ac.uk in environment production
in 0.01 seconds
Error: Could not get latest version: HTTP-Error: 403 Must access using HTTPS
instead of HTTP
Error: /Stage[main]/Main/Package[rarfile]/ensure: change from 2.8 to latest
failed: Could not get latest version: HTTP-Error: 403 Must access using HTTPS
instead of HTTP
Notice: Finished catalog run in 1.05 seconds
This was previously working.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/puppet/+bug/1593749/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1800723] Re: Missing package python3.7-pip
$ python3.7 -m pip --version pip 9.0.1 from /usr/lib/python3/dist-packages (python 3.7) also python3.7 -m pip install ... works fine ** Changed in: python-pip (Ubuntu) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python3-defaults in Ubuntu. https://bugs.launchpad.net/bugs/1800723 Title: Missing package python3.7-pip Status in python-pip package in Ubuntu: Invalid Status in python3-defaults package in Ubuntu: Invalid Bug description: There appears to be no way to get "pip" or "python3.7 -m pip" to work after installing python3.7 using "apt install python3.7". I expected to be able to install a "python3.7-pip" package similar to the other "python3.7-*" packages but I couldn't find one. This problem appears in a clean install of 18.04 as well as 18.10. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-pip/+bug/1800723/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1800723] Re: Missing package python3.7-pip
** Changed in: python3-defaults (Ubuntu) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python3-defaults in Ubuntu. https://bugs.launchpad.net/bugs/1800723 Title: Missing package python3.7-pip Status in python-pip package in Ubuntu: Invalid Status in python3-defaults package in Ubuntu: Invalid Bug description: There appears to be no way to get "pip" or "python3.7 -m pip" to work after installing python3.7 using "apt install python3.7". I expected to be able to install a "python3.7-pip" package similar to the other "python3.7-*" packages but I couldn't find one. This problem appears in a clean install of 18.04 as well as 18.10. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-pip/+bug/1800723/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
