[Touch-packages] [Bug 1888992] Re: [Realtek ALC892, Green Headphone Out, Front] Not detecting/switching to front jack after plugging in headphones
** Package changed: alsa-driver (Ubuntu) => linux (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/1888992 Title: [Realtek ALC892, Green Headphone Out, Front] Not detecting/switching to front jack after plugging in headphones Status in linux package in Ubuntu: New Bug description: I boot my system without any sound devices plugged into any jacks; checking Gnome settings Sound, Output Device is "Dummy Output" (no other options available in drop-down list). I plug in headphones into the front jack and play some audio, but do not hear any sound from the headphones; checking Gnome settings Sound, the Output Device is still "Dummy Output", with no other options available. This is a regression from previous behaviour, when plugging in headphones into the front jack would automatically enable/switch to the front jack and its associated controller "Family 17h (Models 00h- 0fh) HD Audio Controller" (this is the motherboard's onboard audio hardware). I can currently workaround this each time I plug in the headphones by installing and running pavucontrol, and under Configuration selecting "Analogue Stereo Output (unplugged) (unavailable)" - this option becomes "Analogue Stereo Output" after I select it. This seems to be a regression in pulseaudio after an upgrade from from 1:13.99.1-1ubuntu3.3 to 1:13.99.1-1ubuntu3.5. 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 ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: chinf 1741 F pulseaudio /dev/snd/pcmC1D0p: chinf 1741 F...m pulseaudio /dev/snd/controlC0: chinf 1741 F pulseaudio /dev/snd/timer: chinf 1741 f pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Jul 26 12:46:52 2020 InstallationDate: Installed on 2018-10-29 (635 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Generic successful Symptom_Card: Family 17h (Models 00h-0fh) HD Audio Controller - HD-Audio Generic Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: chinf 1741 F pulseaudio /dev/snd/controlC0: chinf 1741 F pulseaudio Symptom_Jack: Green Headphone Out, Front Symptom_PulsePlaybackTest: PulseAudio playback test successful Symptom_Type: No sound at all Title: [To Be Filled By O.E.M., Realtek ALC892, Green Headphone Out, Front] No sound at all UpgradeStatus: Upgraded to focal on 2020-05-04 (83 days ago) dmi.bios.date: 12/19/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P5.40 dmi.board.name: AB350 Pro4 dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP5.40:bd12/19/2018:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnAB350Pro4:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1888992/+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 1876486] Re: systemd breaks due to old libsecomp libs left on the system
[Expired for libseccomp (Ubuntu) because there has been no activity for 60 days.] ** Changed in: libseccomp (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libseccomp in Ubuntu. https://bugs.launchpad.net/bugs/1876486 Title: systemd breaks due to old libsecomp libs left on the system Status in libseccomp package in Ubuntu: Expired Bug description: Upgraded Ubuntu 18.04 to 20.04. Following the upgrade, booting was not possible. The error messages is: /sbin/init: symbol lookup error: /lib/systemd/libsystemd-shared-245.so: undefined symbol: seccomp_api_get [4.608900] Kernel panic - not syncing: Attempted to kill init! exitcode=0x7f00 See also attached photograph of screen during boot. Upgrade followed steps from here: https://help.ubuntu.com/community/FocalUpgrades/Kubuntu With the excpetion that The -d flag was used for the do-release-upgrade: sudo do-release-upgrade -d -m desktop 1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> About Ubuntu Prior to upgrade: Ubuntu 18.04.4 After upgrade (but never booted): Ubuntu (Kubuntu) 20.04 Note that Ubuntu had originally be installed, but kubuntu-desktop was recently installed to change to Kubuntu, but no booting problems were experienced before updating to 20.04. 2) The version of the package you are using, via 'apt-cache policy pkgname' or by checking in Unknown -- Package version may have changed when upgrading to 20.04. 3) What you expected to happen Boot without kernel panic. 4) What happened instead Could not boot. Even selecting safe mode from grub could not boot. Had to restore system from backups. Will not attempt upgrade again. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libseccomp/+bug/1876486/+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 1899527] Re: bluetooth remains off even the switch is on from settings
*** This bug is a duplicate of bug 1857787 *** https://bugs.launchpad.net/bugs/1857787 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 1857787, 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 1857787 Bluetooth cannot be turned on once turned off -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1899527 Title: bluetooth remains off even the switch is on from settings Status in bluez package in Ubuntu: New Status in gnome-control-center package in Ubuntu: New Bug description: sometimes my bluetooth is just turned of and not able to turn it on even if I click the button in settings->bluetooth ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: bluetooth (not installed) ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60 Uname: Linux 5.4.0-48-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.9 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Oct 12 23:45:43 2020 InterestingModules: bluetooth Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 007: ID 0bda:58ea Realtek Semiconductor Corp. EasyCamera Bus 001 Device 002: ID 3938:1031 MOSART Semi. 2.4G Wireless Mouse Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/6p, 5000M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/12p, 480M |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M |__ Port 8: Dev 7, If 1, Class=Video, Driver=uvcvideo, 480M |__ Port 8: Dev 7, If 0, Class=Video, Driver=uvcvideo, 480M MachineType: LENOVO 81DE ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-48-generic root=UUID=05f0328a-3146-4fe8-94ad-3fee253ebdaf ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/18/2020 dmi.bios.vendor: LENOVO dmi.bios.version: 8TCN58WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: NO DPK dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad 330-15IKB dmi.modalias: dmi:bvnLENOVO:bvr8TCN58WW:bd06/18/2020:svnLENOVO:pn81DE:pvrLenovoideapad330-15IKB:rvnLENOVO:rnLNVNB161216:rvrNODPK:cvnLENOVO:ct10:cvrLenovoideapad330-15IKB: dmi.product.family: ideapad 330-15IKB dmi.product.name: 81DE dmi.product.sku: LENOVO_MT_81DE_BU_idea_FM_ideapad 330-15IKB dmi.product.version: Lenovo ideapad 330-15IKB dmi.sys.vendor: LENOVO hciconfig: syslog: Oct 12 23:38:39 pankaj-pc NetworkManager[860]: [1602526119.6673] Loaded device plugin: NMBluezManager (/usr/lib/x86_64-linux-gnu/NetworkManager/1.22.10/libnm-device-plugin-bluetooth.so) Oct 12 23:38:51 pankaj-pc systemd[1]: Condition check resulted in Bluetooth service being skipped. Oct 12 23:39:28 pankaj-pc systemd[1]: Condition check resulted in Bluetooth service being skipped. Oct 12 23:42:00 pankaj-pc systemd[1]: Condition check resulted in Bluetooth service being skipped. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1899527/+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 1899526] Re: Mouse stopped working
By "mouse" do you mean touchpad or an external mouse? I can see you have a wireless mouse/keyboard combo and the receiver for that is certainly still connected. Can you please try a wired mouse? Or any other mouse? ** 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/1899526 Title: Mouse stopped working Status in Ubuntu: Incomplete Bug description: Mouse stopped working after a while(approximately 4 months). ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60 Uname: Linux 5.4.0-48-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: Mon Oct 12 20:52:33 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company 3rd Gen Core processor Graphics Controller [103c:18df] InstallationDate: Installed on 2020-07-29 (75 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: Hewlett-Packard HP EliteBook Folio 9470m ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-48-generic root=UUID=a9b729b7-6080-4654-96ab-48a91ef5d818 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/16/2013 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68IBD Ver. F.46 dmi.board.name: 18DF dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 62.17 dmi.chassis.asset.tag: CNU3339MTG dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr68IBDVer.F.46:bd07/16/2013:svnHewlett-Packard:pnHPEliteBookFolio9470m:pvrA1029D1102:rvnHewlett-Packard:rn18DF:rvrKBCVersion62.17:cvnHewlett-Packard:ct10:cvr: dmi.product.family: 103C_5336AN G=N L=BUS B=HP S=ELI dmi.product.name: HP EliteBook Folio 9470m dmi.product.sku: D9Z90US#ABA dmi.product.version: A1029D1102 dmi.sys.vendor: Hewlett-Packard 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 20.0.8-0ubuntu1~20.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1899526/+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 1899527] Re: bluetooth remains off even the switch is on from settings
*** This bug is a duplicate of bug 1857787 *** https://bugs.launchpad.net/bugs/1857787 ** Also affects: gnome-control-center (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1899527 Title: bluetooth remains off even the switch is on from settings Status in bluez package in Ubuntu: New Status in gnome-control-center package in Ubuntu: New Bug description: sometimes my bluetooth is just turned of and not able to turn it on even if I click the button in settings->bluetooth ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: bluetooth (not installed) ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60 Uname: Linux 5.4.0-48-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.9 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Oct 12 23:45:43 2020 InterestingModules: bluetooth Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 007: ID 0bda:58ea Realtek Semiconductor Corp. EasyCamera Bus 001 Device 002: ID 3938:1031 MOSART Semi. 2.4G Wireless Mouse Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/6p, 5000M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/12p, 480M |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M |__ Port 8: Dev 7, If 1, Class=Video, Driver=uvcvideo, 480M |__ Port 8: Dev 7, If 0, Class=Video, Driver=uvcvideo, 480M MachineType: LENOVO 81DE ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-48-generic root=UUID=05f0328a-3146-4fe8-94ad-3fee253ebdaf ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/18/2020 dmi.bios.vendor: LENOVO dmi.bios.version: 8TCN58WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: NO DPK dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad 330-15IKB dmi.modalias: dmi:bvnLENOVO:bvr8TCN58WW:bd06/18/2020:svnLENOVO:pn81DE:pvrLenovoideapad330-15IKB:rvnLENOVO:rnLNVNB161216:rvrNODPK:cvnLENOVO:ct10:cvrLenovoideapad330-15IKB: dmi.product.family: ideapad 330-15IKB dmi.product.name: 81DE dmi.product.sku: LENOVO_MT_81DE_BU_idea_FM_ideapad 330-15IKB dmi.product.version: Lenovo ideapad 330-15IKB dmi.sys.vendor: LENOVO hciconfig: syslog: Oct 12 23:38:39 pankaj-pc NetworkManager[860]: [1602526119.6673] Loaded device plugin: NMBluezManager (/usr/lib/x86_64-linux-gnu/NetworkManager/1.22.10/libnm-device-plugin-bluetooth.so) Oct 12 23:38:51 pankaj-pc systemd[1]: Condition check resulted in Bluetooth service being skipped. Oct 12 23:39:28 pankaj-pc systemd[1]: Condition check resulted in Bluetooth service being skipped. Oct 12 23:42:00 pankaj-pc systemd[1]: Condition check resulted in Bluetooth service being skipped. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1899527/+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 1893655] Re: Sony WH-1000XM3 headphones connect but don't appear in the audio devices list
** Tags added: groovy -- 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/1893655 Title: Sony WH-1000XM3 headphones connect but don't appear in the audio devices list Status in bluez package in Ubuntu: New Status in pulseaudio package in Ubuntu: New Bug description: When I switch on my Sony WH-1000XM3 headphones, they reconnect to my laptop at Bluetooth level, but don't appear as an audio device. I have to remove them in the Ubuntu Bluetooth settings, and then re-pair them, every time. This is rather inconvenient. This started happening after upgrading to Ubuntu 20.04. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: bluez 5.53-0ubuntu3 ProcVersionSignature: Ubuntu 5.6.0-1021.21-oem 5.6.19 Uname: Linux 5.6.0-1021-oem x86_64 ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: Unity:Unity7:ubuntu Date: Mon Aug 31 14:48:53 2020 InstallationDate: Installed on 2020-07-14 (48 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) InterestingModules: rfcomm bnep btusb bluetooth MachineType: LENOVO 20U9CTO1WW ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.6.0-1021-oem root=UUID=42d20f5a-04dd-4073-ac83-e07bd283a1d1 ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/01/2020 dmi.bios.vendor: LENOVO dmi.bios.version: N2WET19W (1.09 ) dmi.board.asset.tag: Not Available dmi.board.name: 20U9CTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0R32862 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN2WET19W(1.09):bd07/01/2020:svnLENOVO:pn20U9CTO1WW:pvrThinkPadX1CarbonGen8:rvnLENOVO:rn20U9CTO1WW:rvrSDK0R32862WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X1 Carbon Gen 8 dmi.product.name: 20U9CTO1WW dmi.product.sku: LENOVO_MT_20U9_BU_Think_FM_ThinkPad X1 Carbon Gen 8 dmi.product.version: ThinkPad X1 Carbon Gen 8 dmi.sys.vendor: LENOVO hciconfig: hci0:Type: Primary Bus: USB BD Address: F8:AC:65:6D:04:AB ACL MTU: 1021:4 SCO MTU: 96:6 UP RUNNING RX bytes:1274806 acl:246 sco:0 events:180845 errors:0 TX bytes:152114364 acl:177469 sco:0 commands:3182 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1893655/+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 1899195] Re: /usr/share/apport/apport:AttributeError:/usr/share/apport/apport@451:parse_arguments:print_usage:_print_message
** Branch linked: lp:~ubuntu-core-dev/ubuntu/groovy/apport/ubuntu -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1899195 Title: /usr/share/apport/apport:AttributeError:/usr/share/apport/apport@451:parse_arguments:print_usage:_print_message Status in apport package in Ubuntu: In Progress Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding apport. This problem was most recently seen with package version 2.20.11-0ubuntu27.10, the problem page at https://errors.ubuntu.com/problem/290470c9cf5f278596966c386aac31e70a49988e contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. Traceback (most recent call last): File "/usr/share/apport/apport", line 451, in options = parse_arguments() File "/usr/share/apport/apport", line 396, in parse_arguments parser.print_usage() File "/usr/lib/python3.6/argparse.py", line 2370, in print_usage self._print_message(self.format_usage(), file) File "/usr/lib/python3.6/argparse.py", line 2381, in _print_message file.write(message) AttributeError: 'NoneType' object has no attribute 'write' After working on https://bugs.launchpad.net/apport/+bug/1732962, the error tracker started throwing the error above. it appears that print_usage is called and throwing an error because in this context (called with core_pattern) apport doesn't have an stdout or stderr. after looking at traces it seems the kernel is adding 'deleted' to the name of the process which cause argument parsing to fail. The fix below from bdmurray seems to fix it. https://paste.ubuntu.com/p/pVKNP9kWP4/ There is report of this issue in Focal, Bionic and xenial To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1899195/+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 1899538] [NEW] Cannnot use printer because of some apparmor access right
Public bug reported: My Epson printer disappeared from the list of registered printers. I could not assign a suitable driver, even though a relevant package supplied by Epson was already installed (under /opt). It turned out that the logs contained messages like this one: audit: type=1400 audit(1602529987.370:8039): apparmor="DENIED" operation="open" profile="/usr/sbin/cupsd" name="/home/_opt/epson- inkjet-printer-stylus-photo-px810fw-series/ppds/" pid=29169 comm="cups- driverd" requested_mask="r" denied_mask="r" fsuid=7 ouid=0 As explained in https://wiki.ubuntu.com/DebuggingPrintingProblems#AppArmor_Protection_of_the_printing_system, a workaround is to install apparmor-utils and run `aa-complain cupsd'. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: cups 2.3.1-9ubuntu1.1 ProcVersionSignature: Ubuntu 5.4.0-7642.46~1598628707~20.04~040157c~dev-generic 5.4.44 Uname: Linux 5.4.0-7642-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.9 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Oct 12 23:30:38 2020 InstallationDate: Installed on 2020-08-14 (59 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) Lpstat: device for Epson-Stylus-Photo-PX710W: dnssd://EPSONF904BC._printer._tcp.local/ MachineType: System76, Inc. Pangolin Performance Papersize: a4 PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/Epson-Stylus-Photo-PX710W.ppd'] failed with exit code 2: grep: /etc/cups/ppd/Epson-Stylus-Photo-PX710W.ppd: Permission denied ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-7642-generic root=UUID=675a1866-9c2b-49b9-a2c5-c131e736d65c ro quiet splash acpi_os_name=Linux acpi_osi= vt.handoff=7 SourcePackage: cups UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/25/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4.6.5 dmi.board.asset.tag: Tag 12345 dmi.board.name: Pangolin Performance dmi.board.vendor: System76, Inc. dmi.board.version: panp9 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd06/25/2012:svnSystem76,Inc.:pnPangolinPerformance:pvrpanp9:rvnSystem76,Inc.:rnPangolinPerformance:rvrpanp9:cvnNoEnclosure:ct10:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: Pangolin Performance dmi.product.sku: Not Applicable dmi.product.version: panp9 dmi.sys.vendor: System76, Inc. ** Affects: cups (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apparmor apport-bug focal -- 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/1899538 Title: Cannnot use printer because of some apparmor access right Status in cups package in Ubuntu: New Bug description: My Epson printer disappeared from the list of registered printers. I could not assign a suitable driver, even though a relevant package supplied by Epson was already installed (under /opt). It turned out that the logs contained messages like this one: audit: type=1400 audit(1602529987.370:8039): apparmor="DENIED" operation="open" profile="/usr/sbin/cupsd" name="/home/_opt/epson- inkjet-printer-stylus-photo-px810fw-series/ppds/" pid=29169 comm ="cups-driverd" requested_mask="r" denied_mask="r" fsuid=7 ouid=0 As explained in https://wiki.ubuntu.com/DebuggingPrintingProblems#AppArmor_Protection_of_the_printing_system, a workaround is to install apparmor-utils and run `aa-complain cupsd'. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: cups 2.3.1-9ubuntu1.1 ProcVersionSignature: Ubuntu 5.4.0-7642.46~1598628707~20.04~040157c~dev-generic 5.4.44 Uname: Linux 5.4.0-7642-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.9 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Oct 12 23:30:38 2020 InstallationDate: Installed on 2020-08-14 (59 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) Lpstat: device for Epson-Stylus-Photo-PX710W: dnssd://EPSONF904BC._printer._tcp.local/ MachineType: System76, Inc. Pangolin Performance Papersize: a4 PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/Epson-Stylus-Photo-PX710W.ppd'] failed with exit code 2: grep: /etc/cups/ppd/Epson-Stylus-Photo-PX710W.ppd: Permission denied ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-7642-generic root=UUID=675a1866-9c2b-49b9-a2c5-c131e736d65c ro quiet splash acpi_os_name=Linux acpi_osi= vt.handoff=7 SourcePackage: cups UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/25/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4.6.5 dmi.board.asset.tag: Tag 12345 dmi.board.name: Pangolin Performance dmi.board.vendor: System76, Inc. dmi.board.version: panp9 dmi.chassis.ass
[Touch-packages] [Bug 1899195] Re: /usr/share/apport/apport:AttributeError:/usr/share/apport/apport@451:parse_arguments:print_usage:_print_message
While you won't get a Traceback with the following test case you will see apport usage printed: $ PYTHONPATH=/home/bdmurray/source-trees/apport/trunk data/apport '8219' '11' '0' '1' '8219' '!usr!share!spotify!spotify' '(deleted)' usage: apport [-h] [-p PID] [-s SIGNAL_NUMBER] [-c CORE_ULIMIT] [-d DUMP_MODE] [-P [GLOBAL_PID]] With the fixed version of apport you'll see no such usage message. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1899195 Title: /usr/share/apport/apport:AttributeError:/usr/share/apport/apport@451:parse_arguments:print_usage:_print_message Status in apport package in Ubuntu: In Progress Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding apport. This problem was most recently seen with package version 2.20.11-0ubuntu27.10, the problem page at https://errors.ubuntu.com/problem/290470c9cf5f278596966c386aac31e70a49988e contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. Traceback (most recent call last): File "/usr/share/apport/apport", line 451, in options = parse_arguments() File "/usr/share/apport/apport", line 396, in parse_arguments parser.print_usage() File "/usr/lib/python3.6/argparse.py", line 2370, in print_usage self._print_message(self.format_usage(), file) File "/usr/lib/python3.6/argparse.py", line 2381, in _print_message file.write(message) AttributeError: 'NoneType' object has no attribute 'write' After working on https://bugs.launchpad.net/apport/+bug/1732962, the error tracker started throwing the error above. it appears that print_usage is called and throwing an error because in this context (called with core_pattern) apport doesn't have an stdout or stderr. after looking at traces it seems the kernel is adding 'deleted' to the name of the process which cause argument parsing to fail. The fix below from bdmurray seems to fix it. https://paste.ubuntu.com/p/pVKNP9kWP4/ There is report of this issue in Focal, Bionic and xenial To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1899195/+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 1899195] Re: /usr/share/apport/apport:AttributeError:/usr/share/apport/apport@451:parse_arguments:print_usage:_print_message
My patch works by ensuring the apport can handle the number of arguments being passed such that print_usage() is never called so we won't Traceback trying to write to a non-existent file. ** Changed in: apport (Ubuntu) Status: Confirmed => In Progress ** Changed in: apport (Ubuntu) Importance: Undecided => High ** Changed in: apport (Ubuntu) Assignee: (unassigned) => Brian Murray (brian-murray) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1899195 Title: /usr/share/apport/apport:AttributeError:/usr/share/apport/apport@451:parse_arguments:print_usage:_print_message Status in apport package in Ubuntu: In Progress Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding apport. This problem was most recently seen with package version 2.20.11-0ubuntu27.10, the problem page at https://errors.ubuntu.com/problem/290470c9cf5f278596966c386aac31e70a49988e contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. Traceback (most recent call last): File "/usr/share/apport/apport", line 451, in options = parse_arguments() File "/usr/share/apport/apport", line 396, in parse_arguments parser.print_usage() File "/usr/lib/python3.6/argparse.py", line 2370, in print_usage self._print_message(self.format_usage(), file) File "/usr/lib/python3.6/argparse.py", line 2381, in _print_message file.write(message) AttributeError: 'NoneType' object has no attribute 'write' After working on https://bugs.launchpad.net/apport/+bug/1732962, the error tracker started throwing the error above. it appears that print_usage is called and throwing an error because in this context (called with core_pattern) apport doesn't have an stdout or stderr. after looking at traces it seems the kernel is adding 'deleted' to the name of the process which cause argument parsing to fail. The fix below from bdmurray seems to fix it. https://paste.ubuntu.com/p/pVKNP9kWP4/ There is report of this issue in Focal, Bionic and xenial To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1899195/+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 1899531] [NEW] package make (not installed) failed to install/upgrade: dpkg-deb --control subprocess returned error exit status 127
Public bug reported: the make package fails to install ProblemType: Package DistroRelease: Ubuntu 20.04 Package: make (not installed) 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.4 AptOrdering: make:amd64: Install NULL: ConfigurePending Architecture: amd64 CasperMD5CheckResult: skip Date: Mon Oct 12 16:01:08 2020 DpkgTerminalLog: Inconsistency detected by ld.so: ../sysdeps/x86_64/dl-machine.h: 541: elf_machine_rela_relative: Assertion `ELFW(R_TYPE) (reloc->r_info) == R_X86_64_RELATIVE' failed! [1mdpkg:[0m error processing archive /var/cache/apt/archives/make_4.2.1-1.2_amd64.deb (--unpack): dpkg-deb --control subprocess returned error exit status 127 ErrorMessage: dpkg-deb --control subprocess returned error exit status 127 InstallationDate: Installed on 2020-10-11 (0 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.2ubuntu0.1 SourcePackage: make-dfsg Title: package make (not installed) failed to install/upgrade: dpkg-deb --control subprocess returned error exit status 127 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: make-dfsg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package focal -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to make-dfsg in Ubuntu. https://bugs.launchpad.net/bugs/1899531 Title: package make (not installed) failed to install/upgrade: dpkg-deb --control subprocess returned error exit status 127 Status in make-dfsg package in Ubuntu: New Bug description: the make package fails to install ProblemType: Package DistroRelease: Ubuntu 20.04 Package: make (not installed) 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.4 AptOrdering: make:amd64: Install NULL: ConfigurePending Architecture: amd64 CasperMD5CheckResult: skip Date: Mon Oct 12 16:01:08 2020 DpkgTerminalLog: Inconsistency detected by ld.so: ../sysdeps/x86_64/dl-machine.h: 541: elf_machine_rela_relative: Assertion `ELFW(R_TYPE) (reloc->r_info) == R_X86_64_RELATIVE' failed! [1mdpkg:[0m error processing archive /var/cache/apt/archives/make_4.2.1-1.2_amd64.deb (--unpack): dpkg-deb --control subprocess returned error exit status 127 ErrorMessage: dpkg-deb --control subprocess returned error exit status 127 InstallationDate: Installed on 2020-10-11 (0 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.2ubuntu0.1 SourcePackage: make-dfsg Title: package make (not installed) failed to install/upgrade: dpkg-deb --control subprocess returned error exit status 127 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/make-dfsg/+bug/1899531/+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
Also have problems with Schiit Hel on Ubuntu 20.04. I've sound (both input and output) but broken pipe when selecting it from alsamnixer. Using pulsemixer to "set the audio source from off to digital stereo duplex it should prevent alsa crashing and actually allow the audio source to work" did not worked for me. -- 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 1899527] Re: bluetooth remains off even the switch is on from settings
** Package changed: ubuntu => bluez (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1899527 Title: bluetooth remains off even the switch is on from settings Status in bluez package in Ubuntu: New Bug description: sometimes my bluetooth is just turned of and not able to turn it on even if I click the button in settings->bluetooth ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: bluetooth (not installed) ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60 Uname: Linux 5.4.0-48-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.9 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Oct 12 23:45:43 2020 InterestingModules: bluetooth Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 007: ID 0bda:58ea Realtek Semiconductor Corp. EasyCamera Bus 001 Device 002: ID 3938:1031 MOSART Semi. 2.4G Wireless Mouse Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/6p, 5000M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/12p, 480M |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M |__ Port 8: Dev 7, If 1, Class=Video, Driver=uvcvideo, 480M |__ Port 8: Dev 7, If 0, Class=Video, Driver=uvcvideo, 480M MachineType: LENOVO 81DE ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-48-generic root=UUID=05f0328a-3146-4fe8-94ad-3fee253ebdaf ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/18/2020 dmi.bios.vendor: LENOVO dmi.bios.version: 8TCN58WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: NO DPK dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad 330-15IKB dmi.modalias: dmi:bvnLENOVO:bvr8TCN58WW:bd06/18/2020:svnLENOVO:pn81DE:pvrLenovoideapad330-15IKB:rvnLENOVO:rnLNVNB161216:rvrNODPK:cvnLENOVO:ct10:cvrLenovoideapad330-15IKB: dmi.product.family: ideapad 330-15IKB dmi.product.name: 81DE dmi.product.sku: LENOVO_MT_81DE_BU_idea_FM_ideapad 330-15IKB dmi.product.version: Lenovo ideapad 330-15IKB dmi.sys.vendor: LENOVO hciconfig: syslog: Oct 12 23:38:39 pankaj-pc NetworkManager[860]: [1602526119.6673] Loaded device plugin: NMBluezManager (/usr/lib/x86_64-linux-gnu/NetworkManager/1.22.10/libnm-device-plugin-bluetooth.so) Oct 12 23:38:51 pankaj-pc systemd[1]: Condition check resulted in Bluetooth service being skipped. Oct 12 23:39:28 pankaj-pc systemd[1]: Condition check resulted in Bluetooth service being skipped. Oct 12 23:42:00 pankaj-pc systemd[1]: Condition check resulted in Bluetooth service being skipped. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1899527/+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 1899527] [NEW] bluetooth remains off even the switch is on from settings
You have been subscribed to a public bug: sometimes my bluetooth is just turned of and not able to turn it on even if I click the button in settings->bluetooth ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: bluetooth (not installed) ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60 Uname: Linux 5.4.0-48-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.9 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Oct 12 23:45:43 2020 InterestingModules: bluetooth Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 007: ID 0bda:58ea Realtek Semiconductor Corp. EasyCamera Bus 001 Device 002: ID 3938:1031 MOSART Semi. 2.4G Wireless Mouse Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/6p, 5000M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/12p, 480M |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M |__ Port 8: Dev 7, If 1, Class=Video, Driver=uvcvideo, 480M |__ Port 8: Dev 7, If 0, Class=Video, Driver=uvcvideo, 480M MachineType: LENOVO 81DE ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-48-generic root=UUID=05f0328a-3146-4fe8-94ad-3fee253ebdaf ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/18/2020 dmi.bios.vendor: LENOVO dmi.bios.version: 8TCN58WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: NO DPK dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad 330-15IKB dmi.modalias: dmi:bvnLENOVO:bvr8TCN58WW:bd06/18/2020:svnLENOVO:pn81DE:pvrLenovoideapad330-15IKB:rvnLENOVO:rnLNVNB161216:rvrNODPK:cvnLENOVO:ct10:cvrLenovoideapad330-15IKB: dmi.product.family: ideapad 330-15IKB dmi.product.name: 81DE dmi.product.sku: LENOVO_MT_81DE_BU_idea_FM_ideapad 330-15IKB dmi.product.version: Lenovo ideapad 330-15IKB dmi.sys.vendor: LENOVO hciconfig: syslog: Oct 12 23:38:39 pankaj-pc NetworkManager[860]: [1602526119.6673] Loaded device plugin: NMBluezManager (/usr/lib/x86_64-linux-gnu/NetworkManager/1.22.10/libnm-device-plugin-bluetooth.so) Oct 12 23:38:51 pankaj-pc systemd[1]: Condition check resulted in Bluetooth service being skipped. Oct 12 23:39:28 pankaj-pc systemd[1]: Condition check resulted in Bluetooth service being skipped. Oct 12 23:42:00 pankaj-pc systemd[1]: Condition check resulted in Bluetooth service being skipped. ** Affects: bluez (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- bluetooth remains off even the switch is on from settings https://bugs.launchpad.net/bugs/1899527 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. -- 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 1871794] Re: [Bluetooth] No audio output/input in HSP/HFP mode
Ok, all these devices have intel wireless and use btintel together with btusb. And i am also pretty sure it has something to do with the firmware not loading. Also this bug has been reported on April the 9th this year and i don't see anyone working on this. And we already have a point release. Why is this not getting any attention? At least give us a status update. Many people work at home now and use bluetooth headphones for Slack or Skype etc. We bought company laptops with 20.04 LTS preinstalled and we all had to downgrade them to make them usable for working at home. -- 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/1871794 Title: [Bluetooth] No audio output/input in HSP/HFP mode Status in bluez package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Confirmed Bug description: I'm testing with Sony bluetooth headset SBH20, works fine in A2DP profile, but I can't get audio input and output work in HSP/HFP profile. [Reproduce steps] 1. Scan and pair BT headset in Bluetooth setting 2. Switch to HSP/HFP profile in Sound setting 3. Test sound output/input [Machine information] ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu25 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1359 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Thu Apr 9 16:26:52 2020 InstallationDate: Installed on 2020-04-09 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) SourcePackage: pulseaudio Symptom: audio Symptom_Card: SBH20 Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1359 F pulseaudio Symptom_Type: No sound at all Title: [SBH20, recording] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/17/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.0.13 dmi.board.name: 0188D1 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 31 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.0.13:bd09/17/2019:svnDellInc.:pnXPS1373902-in-1:pvr:rvnDellInc.:rn0188D1:rvrA00:cvnDellInc.:ct31:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 7390 2-in-1 dmi.product.sku: 08B0 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1871794/+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 1166529] Re: Creative Recon3d & Sound Blaster Z (CA0132), No sound at all
Hello : My latest tests for this sound card : With Linux Mint LMDE4 64 (live session no config, no patch) the sound is ok 2.0 Kernel = 4.19.0-8-amd64 x86-64 With Linux Mint 19.3 Cinnamon 64 (live session no config, no patch) the sound is ok 5.1 Kernel = 5.0.0--32generic x86-64 With Linux Mint 20 Cinnamon 64 (live session) it is also OK. -- 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/1166529 Title: Creative Recon3d & Sound Blaster Z (CA0132), No sound at all Status in ALSA driver: Fix Released Status in Linux: Confirmed Status in alsa-driver package in Ubuntu: Confirmed Status in alsa-driver package in Debian: New Bug description: [WORKAROUND] Run the following command: echo "options snd-hda-intel position_fix=1" | sudo tee -a /etc/modprobe.d/alsa-base.conf [EDIT] Workaround doesn't work anymore for me at least. I assume it only has a small possibility of working due to a firmware bug. [ORIGINAL REPORT] No sound, no jacks; It is detected by Linux however. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: alsa-base 1.0.25+dfsg-0ubuntu4 ProcVersionSignature: Ubuntu 3.8.0-16.26-generic 3.8.5 Uname: Linux 3.8.0-16-generic x86_64 NonfreeKernelModules: fglrx ApportVersion: 2.9.2-0ubuntu5 Architecture: amd64 Date: Mon Apr 8 18:56:44 2013 InstallationDate: Installed on 2013-04-07 (1 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20130402.1) MarkForUpload: True PackageArchitecture: all ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Creative failed Symptom_Card: HDA Creative - HDA Creative Symptom_Type: No sound at all Title: [To be filled by O.E.M., Creative CA0132, Green Line Out, Rear] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/12/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1102 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: SABERTOOTH 990FX 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.:bvr1102:bd03/12/2012:svnTobefilledbyO.E.M.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnASUSTeKCOMPUTERINC.:rnSABERTOOTH990FX:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: To be filled by O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/alsa-driver/+bug/1166529/+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 1863027] Re: package rsyslog 8.2001.0-1ubuntu1 failed to install/upgrade: installed rsyslog package post-installation script subprocess returned error exit status 10
erro ao atualizar -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to rsyslog in Ubuntu. https://bugs.launchpad.net/bugs/1863027 Title: package rsyslog 8.2001.0-1ubuntu1 failed to install/upgrade: installed rsyslog package post-installation script subprocess returned error exit status 10 Status in rsyslog package in Ubuntu: Confirmed Bug description: This error occurred in system update. ProblemType: Package DistroRelease: Ubuntu 20.04 Package: rsyslog 8.2001.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8 Uname: Linux 5.4.0-12-generic x86_64 ApportVersion: 2.20.11-0ubuntu16 Architecture: amd64 Date: Wed Feb 12 19:18:14 2020 DuplicateSignature: package:rsyslog:8.2001.0-1ubuntu1 Installing new version of config file /etc/logcheck/ignore.d.server/rsyslog ... O usuário 'syslog' já é um membro de 'adm'. dpkg: error processing package rsyslog (--configure): installed rsyslog package post-installation script subprocess returned error exit status 10 ErrorMessage: installed rsyslog package post-installation script subprocess returned error exit status 10 InstallationDate: Installed on 2020-02-01 (11 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200124) Python3Details: /usr/bin/python3.7, Python 3.7.6, unpackaged PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu2 apt 1.9.9 SourcePackage: rsyslog Title: package rsyslog 8.2001.0-1ubuntu1 failed to install/upgrade: installed rsyslog package post-installation script subprocess returned error exit status 10 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/1863027/+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 1863027] Re: package rsyslog 8.2001.0-1ubuntu1 failed to install/upgrade: installed rsyslog package post-installation script subprocess returned error exit status 10
erro em atualizar -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to rsyslog in Ubuntu. https://bugs.launchpad.net/bugs/1863027 Title: package rsyslog 8.2001.0-1ubuntu1 failed to install/upgrade: installed rsyslog package post-installation script subprocess returned error exit status 10 Status in rsyslog package in Ubuntu: Confirmed Bug description: This error occurred in system update. ProblemType: Package DistroRelease: Ubuntu 20.04 Package: rsyslog 8.2001.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8 Uname: Linux 5.4.0-12-generic x86_64 ApportVersion: 2.20.11-0ubuntu16 Architecture: amd64 Date: Wed Feb 12 19:18:14 2020 DuplicateSignature: package:rsyslog:8.2001.0-1ubuntu1 Installing new version of config file /etc/logcheck/ignore.d.server/rsyslog ... O usuário 'syslog' já é um membro de 'adm'. dpkg: error processing package rsyslog (--configure): installed rsyslog package post-installation script subprocess returned error exit status 10 ErrorMessage: installed rsyslog package post-installation script subprocess returned error exit status 10 InstallationDate: Installed on 2020-02-01 (11 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200124) Python3Details: /usr/bin/python3.7, Python 3.7.6, unpackaged PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu2 apt 1.9.9 SourcePackage: rsyslog Title: package rsyslog 8.2001.0-1ubuntu1 failed to install/upgrade: installed rsyslog package post-installation script subprocess returned error exit status 10 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/1863027/+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 1899524] Re: package rsyslog 8.2001.0-1ubuntu1.1 failed to install/upgrade: installed rsyslog package post-installation script subprocess returned error exit status 10
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to rsyslog in Ubuntu. https://bugs.launchpad.net/bugs/1899524 Title: package rsyslog 8.2001.0-1ubuntu1.1 failed to install/upgrade: installed rsyslog package post-installation script subprocess returned error exit status 10 Status in rsyslog package in Ubuntu: New Bug description: Atualização ProblemType: Package DistroRelease: Ubuntu 20.04 Package: rsyslog 8.2001.0-1ubuntu1.1 ProcVersionSignature: Ubuntu 5.4.0-47.51-generic 5.4.55 Uname: Linux 5.4.0-47-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.9 Architecture: amd64 CasperMD5CheckResult: skip Date: Mon Oct 12 11:48:23 2020 ErrorMessage: installed rsyslog package post-installation script subprocess returned error exit status 10 InstallationDate: Installed on 2020-07-11 (93 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Python3Details: /usr/bin/python3.8, Python 3.8.5, unpackaged PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.2ubuntu0.1 SourcePackage: rsyslog Title: package rsyslog 8.2001.0-1ubuntu1.1 failed to install/upgrade: installed rsyslog package post-installation script subprocess returned error exit status 10 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/1899524/+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 1899526] [NEW] Mouse stopped working
Public bug reported: Mouse stopped working after a while(approximately 4 months). ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60 Uname: Linux 5.4.0-48-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: Mon Oct 12 20:52:33 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company 3rd Gen Core processor Graphics Controller [103c:18df] InstallationDate: Installed on 2020-07-29 (75 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: Hewlett-Packard HP EliteBook Folio 9470m ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-48-generic root=UUID=a9b729b7-6080-4654-96ab-48a91ef5d818 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/16/2013 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68IBD Ver. F.46 dmi.board.name: 18DF dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 62.17 dmi.chassis.asset.tag: CNU3339MTG dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr68IBDVer.F.46:bd07/16/2013:svnHewlett-Packard:pnHPEliteBookFolio9470m:pvrA1029D1102:rvnHewlett-Packard:rn18DF:rvrKBCVersion62.17:cvnHewlett-Packard:ct10:cvr: dmi.product.family: 103C_5336AN G=N L=BUS B=HP S=ELI dmi.product.name: HP EliteBook Folio 9470m dmi.product.sku: D9Z90US#ABA dmi.product.version: A1029D1102 dmi.sys.vendor: Hewlett-Packard 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 20.0.8-0ubuntu1~20.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: 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/1899526 Title: Mouse stopped working Status in xorg package in Ubuntu: New Bug description: Mouse stopped working after a while(approximately 4 months). ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60 Uname: Linux 5.4.0-48-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: Mon Oct 12 20:52:33 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company 3rd Gen Core processor Graphics Controller [103c:18df] InstallationDate: Installed on 2020-07-29 (75 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: Hewlett-Packard HP EliteBook Folio 9470m ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-48-generic root=UUID=a9b729b7-6080-4654-96ab-48a91ef5d818 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/16/2013 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68IBD Ver. F.46 dmi.board.name: 18DF dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 62.17 dmi.chassis.asset.tag: CNU3339MTG dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr68IBDVer.F.46:bd07/16/2013:svnHewlett-Packard:pnHPEliteBookFolio9470m:pvrA1029D1102:rvnHewlett-Packard:rn18DF:rvrKBCVersion62.17:cvnHewlett-Packard:ct10:cvr: dmi.product.family: 103C_5336AN G=N L=BUS B=HP S=ELI dmi.product.name: HP EliteBook Folio 9470m dmi.product.sku: D9Z90US#ABA dmi.product.version: A1029D1102 dmi.sys.vendor: Hewlett-Packard 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 20.0.8-0ubuntu1~20.04.1 versio
[Touch-packages] [Bug 1899524] [NEW] package rsyslog 8.2001.0-1ubuntu1.1 failed to install/upgrade: installed rsyslog package post-installation script subprocess returned error exit status 10
Public bug reported: Atualização ProblemType: Package DistroRelease: Ubuntu 20.04 Package: rsyslog 8.2001.0-1ubuntu1.1 ProcVersionSignature: Ubuntu 5.4.0-47.51-generic 5.4.55 Uname: Linux 5.4.0-47-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.9 Architecture: amd64 CasperMD5CheckResult: skip Date: Mon Oct 12 11:48:23 2020 ErrorMessage: installed rsyslog package post-installation script subprocess returned error exit status 10 InstallationDate: Installed on 2020-07-11 (93 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Python3Details: /usr/bin/python3.8, Python 3.8.5, unpackaged PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.2ubuntu0.1 SourcePackage: rsyslog Title: package rsyslog 8.2001.0-1ubuntu1.1 failed to install/upgrade: installed rsyslog package post-installation script subprocess returned error exit status 10 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: rsyslog (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package focal -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to rsyslog in Ubuntu. https://bugs.launchpad.net/bugs/1899524 Title: package rsyslog 8.2001.0-1ubuntu1.1 failed to install/upgrade: installed rsyslog package post-installation script subprocess returned error exit status 10 Status in rsyslog package in Ubuntu: New Bug description: Atualização ProblemType: Package DistroRelease: Ubuntu 20.04 Package: rsyslog 8.2001.0-1ubuntu1.1 ProcVersionSignature: Ubuntu 5.4.0-47.51-generic 5.4.55 Uname: Linux 5.4.0-47-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.9 Architecture: amd64 CasperMD5CheckResult: skip Date: Mon Oct 12 11:48:23 2020 ErrorMessage: installed rsyslog package post-installation script subprocess returned error exit status 10 InstallationDate: Installed on 2020-07-11 (93 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Python3Details: /usr/bin/python3.8, Python 3.8.5, unpackaged PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.2ubuntu0.1 SourcePackage: rsyslog Title: package rsyslog 8.2001.0-1ubuntu1.1 failed to install/upgrade: installed rsyslog package post-installation script subprocess returned error exit status 10 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/1899524/+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 1899218] Re: Incorrect warning from apparmor_parser on force complained profiles
FYI, this is part of the groovy upload in unapproved. ** Changed in: apparmor (Ubuntu) Status: New => Fix Committed ** Changed in: apparmor (Ubuntu) Assignee: (unassigned) => John Johansen (jjohansen) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/1899218 Title: Incorrect warning from apparmor_parser on force complained profiles Status in apparmor package in Ubuntu: Fix Committed Bug description: apparmor_parser on a force complained profile produces an incorrect warning message: $ sudo apparmor_parser -rW /etc/apparmor.d/usr.sbin.sssd Warning: found usr.sbin.sssd in /etc/apparmor.d/force-complain, forcing complain mode Warning from /etc/apparmor.d/usr.sbin.sssd (/etc/apparmor.d/usr.sbin.sssd line 54): Warning failed to create cache: usr.sbin.sssd Even though not generating the cache at all is expected, the warning should describe caching is disabled for force complained profiles instead of failure to create it. $ lsb_release -rd Description: Ubuntu Groovy Gorilla (development branch) Release: 20.10 $ apt-cache policy apparmor apparmor: Installed: 3.0.0~beta1-0ubuntu6 Candidate: 3.0.0~beta1-0ubuntu6 Version table: *** 3.0.0~beta1-0ubuntu6 500 500 http://archive.ubuntu.com/ubuntu groovy/main amd64 Packages 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1899218/+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 1876504] Re: Gdebi close when trying to install a .deb with right-clic
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: gdebi (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gdebi in Ubuntu.
https://bugs.launchpad.net/bugs/1876504
Title:
Gdebi close when trying to install a .deb with right-clic
Status in gdebi package in Ubuntu:
Confirmed
Bug description:
In focal(20.04), gdebi 0.9.5.7+nmu3 has a problem.
In a terminal : sudo gdebi xxx.deb works (but no graphic mode)
In a terminal : sudo gdebi-gtk launch gdebi. Then, in the graphic UI,
choose a .deb file ("file > open"), then clic on "install" and it's
works.
BUT right-clic on the .deb, then "open with gdebi" => gdebi launch, et
show the .deb file. But clic on "install" button, and gdebi close
without any installation.
Solution / workaround :
change in gdebi.desktop the line
exec=gdebi-gtk %f
by :
exec=sh -c "gdebi-gtk %f"
And it's works perfectly.
Please, change the gdebi.desktop in gdebi.deb on focal.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdebi/+bug/1876504/+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 1899046] Re: /usr/bin/aa-notify:ModuleNotFoundError:/usr/bin/aa-notify@39
This has been uploaded to groovy and is currently in unapproved. ** Changed in: apparmor (Ubuntu) Status: In Progress => Fix Committed ** Changed in: apparmor (Ubuntu) Assignee: (unassigned) => Emilia Torino (emitorino) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/1899046 Title: /usr/bin/aa-notify:ModuleNotFoundError:/usr/bin/aa-notify@39 Status in apparmor package in Ubuntu: Fix Committed Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding apparmor. This problem was most recently seen with package version 3.0.0~beta1-0ubuntu6, the problem page at https://errors.ubuntu.com/problem/69bb6832fe7b294bd7e2d75970fdc903f412c409 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1899046/+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 1871794] Re: [Bluetooth] No audio output/input in HSP/HFP mode
I have the issue as well and the 5.4.0-48-generic kernel does NOT fix it for me. - Ubuntu 20.04.1 LTS (just upgraded from 18.04 where it worked) - Dell XPS 13 7390 Developer Edition - SteelSeries Arctis Pro Wireless -- 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/1871794 Title: [Bluetooth] No audio output/input in HSP/HFP mode Status in bluez package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Confirmed Bug description: I'm testing with Sony bluetooth headset SBH20, works fine in A2DP profile, but I can't get audio input and output work in HSP/HFP profile. [Reproduce steps] 1. Scan and pair BT headset in Bluetooth setting 2. Switch to HSP/HFP profile in Sound setting 3. Test sound output/input [Machine information] ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu25 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1359 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Thu Apr 9 16:26:52 2020 InstallationDate: Installed on 2020-04-09 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) SourcePackage: pulseaudio Symptom: audio Symptom_Card: SBH20 Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1359 F pulseaudio Symptom_Type: No sound at all Title: [SBH20, recording] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/17/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.0.13 dmi.board.name: 0188D1 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 31 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.0.13:bd09/17/2019:svnDellInc.:pnXPS1373902-in-1:pvr:rvnDellInc.:rn0188D1:rvrA00:cvnDellInc.:ct31:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 7390 2-in-1 dmi.product.sku: 08B0 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1871794/+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 1849859] Re: smb printing fails
Is this the same as https://bugs.launchpad.net/ubuntu/+source/system-config-printer/+bug/1895852 ? In short for me syst-config-printer ask for non existent password. -- 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/1849859 Title: smb printing fails Status in cups package in Ubuntu: Confirmed Status in samba package in Ubuntu: Confirmed Status in system-config-printer package in Ubuntu: Fix Released Bug description: when I connect to smb server (nas) permanently appears "Error while getting peer-to-peer dbus connection: Operation was cancelled" The printer at this NAS doesn't work too. "held for authentication KeyError: 'auth-info-required'" The same printer at usb port works fine. Ubuntu development version 20.04 system-config-printer version 1.5.11-4ubuntu1 smbclient version 2:4.10.7+dfsg-0ubuntu3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1849859/+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 1899354] Re: apport-bug crashes (Kununtu)
** Package changed: apport (Ubuntu) => apport-symptoms (Ubuntu)
** Changed in: apport-symptoms (Ubuntu)
Status: New => In Progress
** Changed in: apport-symptoms (Ubuntu)
Assignee: (unassigned) => Brian Murray (brian-murray)
** Changed in: apport-symptoms (Ubuntu)
Importance: Undecided => Medium
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apport in Ubuntu.
https://bugs.launchpad.net/bugs/1899354
Title:
apport-bug crashes (Kununtu)
Status in apport-symptoms package in Ubuntu:
In Progress
Bug description:
Starting apport-bug from the terminal and then selecting "Sound/audio
related problems" crashes apport-bug:
cassiopeia ~ > apport-bug
ERROR: symptom script /usr/share/apport/symptoms/installer.py crashed:
Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/apport/ui.py", line 95, in
thread_collect_info
package = symb['run'](report, ui)
File "/usr/share/apport/symptoms/installer.py", line 9, in run
with os.scandir('/var/log/installer') as entries:
FileNotFoundError: [Errno 2] No such file or directory: '/var/log/installer'
Of course, I never was able to submit ANY bug using apport-bug,
because it does not work for other options either.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport-symptoms/+bug/1899354/+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 1847350] Re: printers.cgi crashed with SIGSEGV in __GI___strdup()
** Information type changed from Private to Public -- 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/1847350 Title: printers.cgi crashed with SIGSEGV in __GI___strdup() Status in cups package in Ubuntu: New Bug description: na configuração de impressora de rede ... ProblemType: Crash DistroRelease: Ubuntu 19.10 Package: cups 2.2.12-2ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-17.18-generic 5.3.1 Uname: Linux 5.3.0-17-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 Date: Tue Oct 8 17:48:49 2019 ExecutablePath: /usr/lib/cups/cgi-bin/printers.cgi InstallationDate: Installed on 2019-10-08 (0 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Beta amd64 (20190926.1) Lpstat: device for CD-COM-01: smb://192.168.0.233/CD-COM-01 MachineType: Dell Inc. Vostro 3460 Papersize: a4 PpdFiles: CD-COM-01: Kyocera ECOSYS M2035dn (KPDL) ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-5.3.0-17-generic root=UUID=02d52d10-3ca6-49b6-9ba3-a3cf84a14f73 ro quiet splash vt.handoff=7 ProcEnviron: PATH=(custom, no user) LANG=en_US.UTF8 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-17-generic root=UUID=02d52d10-3ca6-49b6-9ba3-a3cf84a14f73 ro quiet splash vt.handoff=7 SegvAnalysis: Segfault happened at: 0x7f3116893d8a <__strlen_sse2+42>: movdqu (%rax),%xmm4 PC (0x7f3116893d8a) ok source "(%rax)" (0x) not located in a known VMA region (needed readable region)! destination "%xmm4" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: cups StacktraceTop: __GI___strdup (s=0x0) at strdup.c:41 ?? () ?? () ?? () ?? () Title: printers.cgi crashed with SIGSEGV in __GI___strdup() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: dmi.bios.date: 04/18/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A16 dmi.board.name: 0C0NHY dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnDellInc.:bvrA16:bd04/18/2013:svnDellInc.:pnVostro3460:pvr:rvnDellInc.:rn0C0NHY:rvrA01:cvnDellInc.:ct8:cvr0.1: dmi.product.family: ChiefRiver System dmi.product.name: Vostro 3460 dmi.product.sku: System SKUNumber dmi.sys.vendor: Dell Inc. separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1847350/+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 1899483] Re: long hang apt install mariadb-server on Ubuntu 20.04 server
After failed installation command 'service mysql start' hangs endless, but mysqlshow and mysql are working. $ ps -f -t pts/4 UID PIDPPID C STIME TTY TIME CMD root 107880 107877 0 12:46 pts/400:00:00 -bash root 125389 107880 0 13:01 pts/400:00:00 systemctl start mysql.service root 125396 125389 0 13:01 pts/400:00:00 /bin/systemd-tty-ask-password-agent --watch $ ps -f -u mysql mysql 125461 1 0 13:01 ?00:00:00 /usr/sbin/mysqld -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1899483 Title: long hang apt install mariadb-server on Ubuntu 20.04 server Status in apt package in Ubuntu: New Bug description: Ubuntu 20.04 server => no graphical user interface MariaDb is functional: mysqlshow works, mysqladmin create xxx works After 10 Minutes - the installation terminates - dbms terminates Oct 12 12:38:19 host systemd[1]: Starting MariaDB 10.3.22 database server... Oct 12 12:38:19 host mysqld[124254]: 2020-10-12 12:38:19 0 [Note] /usr/sbin/mysqld (mysqld 10.3.22-MariaDB-1ubuntu1) starting as process 124254 ... Oct 12 12:53:19 host systemd[1]: mariadb.service: start operation timed out. Terminating. Oct 12 12:53:20 host systemd[1]: mariadb.service: Failed with result 'timeout'. Oct 12 12:53:20 host systemd[1]: Failed to start MariaDB 10.3.22 database server. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: apt 2.0.2ubuntu0.1 ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60 Uname: Linux 5.4.0-48-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.9 Architecture: amd64 CasperMD5CheckResult: skip Date: Mon Oct 12 12:43:49 2020 ExecutablePath: /usr/bin/apt InstallationDate: Installed on 2020-05-11 (154 days ago) InstallationMedia: Ubuntu-Server 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) ProcEnviron: SHELL=/bin/bash LANG=en_US.UTF-8 TERM=xterm-256color PATH=(custom, no user) SourcePackage: apt UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1899483/+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 1659719] Re: ssh can't call a binary from a snap without the full path
This bug was fixed in the package pam - 1.1.8-3.2ubuntu2.3 --- pam (1.1.8-3.2ubuntu2.3) xenial; urgency=medium * Move patch fixing LP: #1666203 from debian/patches to debian/patches-applied so it actually gets applied. * debian/libpam-modules.postinst: Add /snap/bin to $PATH in /etc/environment. (LP: #1659719) pam (1.1.8-3.2ubuntu2.2) xenial; urgency=medium * Fix: pam_tty_audit failed in pam_open_session (LP: #1666203) -- Michael Hudson-Doyle Thu, 01 Oct 2020 10:03:21 +1300 ** Changed in: pam (Ubuntu Xenial) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pam in Ubuntu. https://bugs.launchpad.net/bugs/1659719 Title: ssh can't call a binary from a snap without the full path Status in Snappy: Fix Committed Status in livecd-rootfs package in Ubuntu: Fix Released Status in openssh package in Ubuntu: Confirmed Status in pam package in Ubuntu: Fix Released Status in livecd-rootfs source package in Xenial: New Status in openssh source package in Xenial: Won't Fix Status in pam source package in Xenial: Fix Released Status in livecd-rootfs source package in Bionic: New Status in openssh source package in Bionic: Won't Fix Status in pam source package in Bionic: Fix Released Status in livecd-rootfs source package in Focal: New Status in openssh source package in Focal: Won't Fix Status in pam source package in Focal: Fix Released Status in livecd-rootfs source package in Groovy: Fix Released Status in openssh source package in Groovy: Confirmed Status in pam source package in Groovy: Fix Released Status in openssh package in Debian: New Bug description: [impact] ssh can't call a binary from a snap, it will only work using the full path. [test case] Create a container. Install the go snap (and make sure golang-go is not installed). Run "ssh go version" and check the binary is found. [regression potential] It's a pam change an they are always a bit scary but the code follows the existing pattern for updating PATH in /etc/environment and has been tested in groovy. [original description] Let's say I have the hello snap installed in 192.168.122.24. Then: elopio@ubuntu-xenial:~/mosh$ ssh 192.168.122.24 hello elopio@192.168.122.24's password: bash: hello: command not found elopio@ubuntu-xenial:~/mosh$ ssh 192.168.122.24 /snap/bin/hello elopio@192.168.122.24's password: Hello, world! To manage notifications about this bug go to: https://bugs.launchpad.net/snappy/+bug/1659719/+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 1666203] Re: pam_tty_audit failed in pam_open_session
This bug was fixed in the package pam - 1.1.8-3.2ubuntu2.3 --- pam (1.1.8-3.2ubuntu2.3) xenial; urgency=medium * Move patch fixing LP: #1666203 from debian/patches to debian/patches-applied so it actually gets applied. * debian/libpam-modules.postinst: Add /snap/bin to $PATH in /etc/environment. (LP: #1659719) pam (1.1.8-3.2ubuntu2.2) xenial; urgency=medium * Fix: pam_tty_audit failed in pam_open_session (LP: #1666203) -- Michael Hudson-Doyle Thu, 01 Oct 2020 10:03:21 +1300 ** Changed in: pam (Ubuntu Xenial) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pam in Ubuntu. https://bugs.launchpad.net/bugs/1666203 Title: pam_tty_audit failed in pam_open_session Status in pam package in Ubuntu: Fix Released Status in pam source package in Xenial: Fix Released Status in pam source package in Bionic: Fix Released Status in pam source package in Cosmic: Fix Released Status in pam package in Debian: Fix Released Bug description: [Impact] * Kernel keystroke auditing via pam_tty_audit.so not working * When Using the pam_tty_audit with other pam modules(ex, pam_ldap), it failed in pam_open_session. It was triggared by use uninitialized variable in pam_tty_audit.c::pam_open_session. [Test Case] 1) Open a shell & escalate to root 2) Update /etc/pam.d/common-session & /etc/pam.d/common-session-noninteractive and add the following line directly after the line: "session required pam_unix.so": "session required pam_tty_audit.so enable=*" 3) Start a second new shell session on the box and type a variety of commands 4) Exit the second shell session to flush the buffer? 5) In the root shell run "aureport -tty -i". The output should show the commands run in the other shell. [Regression Potential] * Low, we are simply including the missing header file and copy the old status as initialization of new. The fix is already found/part of Debian and Disco. [Pending SRU] All regressions found in Bionic and Cosmic looks like long standing ADT failure. Nothing has been introduce by this particular SRU. [Other Info] # Upstream fix: https://github.com/linux-pam/linux-pam/commit/c5f829931a22c65feffee16570efdae036524bee # git describe --contains c5f829931a22c65feffee16570efdae036524bee Linux-PAM-1_2_0~75 # rmadision pam => pam | 1.1.8-1ubuntu2.2 | trusty-updates | source => pam | 1.1.8-3.2ubuntu2 | xenial | source => pam | 1.1.8-3.2ubuntu2.1 | xenial-updates | source => pam | 1.1.8-3.6ubuntu2 | bionic | source => pam | 1.1.8-3.6ubuntu2 | cosmic | source pam | 1.3.1-5ubuntu1 | disco| source [Original Description] Dear Maintainer. I found a bug in pam_tty_audit. When Using the pam_tty_audit with other pam modules(ex, pam_ldap), it failed in pam_open_session. It was triggared by use uninitialized variable in pam_tty_audit.c::pam_open_session. * Enviroments Ubuntu 14.04.4 LTS linux-image-3.16.0-71-generic3.16.0-71.92~14.04.1 libpam-ldap:amd64184-8.5ubuntu3 libpam-modules:amd641.1.8-1ubuntu2.2 Ubuntu 16.04.2 TLS linux-image-4.4.0-62-generic4.4.0-62.83 libpam-ldap:amd64184-8.7ubuntu1 libpam-modules:amd641.1.8-3.2ubuntu2 * Reproduction method 1. Install libpam-ldap. 2. Add the following to the end of /etc/pam.d/common-sessions session required pam_tty_audit.so enable=* open_only 3. When logging in with ssh etc., pam_tty_audit will fail and login fails * Solution (== 2018/04/16 Link updated ==) apply upstream patch https://github.com/linux-pam/linux-pam/commit/c5f829931a22c65feffee16570efdae036524bee * Logs (on Ubuntu14.04) -- auth.log -- May 18 14:47:03 vm sshd[2272]: Accepted publickey for test from 10.99.0.1 port 51398 ssh2: RSA 8f:39:1c:3a:f4:9d:ca:99:67:fc:e3:fd:1e:0c:5b:a8 May 18 14:47:03 vm sshd[2272]: pam_unix(sshd:session): session opened for user test by (uid=0) May 18 14:47:03 vm sshd[2272]: pam_tty_audit(sshd:session): error setting current audit status: Invalid argument May 18 14:47:03 vm sshd[2272]: error: PAM: pam_open_session(): Cannot make/remove an entry for the specified session May 18 14:47:03 vm sshd[2297]: Received disconnect from 10.99.0.1: 11: disconnected by user -- syslog -- May 18 14:47:03 vm audispd: node=vm type=USER_ACCT msg=audit(1463550423.399:58): pid=2272 uid=0 auid=4294967295 ses=4294967295 msg='op=PAM:accounting acct="test" exe="/usr/sbin/sshd" hostname=10.99.0.1 addr=10.99.0.1 terminal=ssh res=success' May 18 14:47:03 vm audispd: node=vm type=CRED_ACQ msg=audit(1463550423.403:59): pid=2272 uid=0 auid=4294967295 ses=4294967295 msg='op=PAM:setcred acct="test" exe="/usr/sbin/sshd" hostname=10.99.0.1 addr=10.99.0.1 terminal=ssh res=success' May 18 14:47:03 vm audispd: nod
[Touch-packages] [Bug 1899483] [NEW] long hang apt install mariadb-server on Ubuntu 20.04 server
Public bug reported: Ubuntu 20.04 server => no graphical user interface MariaDb is functional: mysqlshow works, mysqladmin create xxx works After 10 Minutes - the installation terminates - dbms terminates Oct 12 12:38:19 host systemd[1]: Starting MariaDB 10.3.22 database server... Oct 12 12:38:19 host mysqld[124254]: 2020-10-12 12:38:19 0 [Note] /usr/sbin/mysqld (mysqld 10.3.22-MariaDB-1ubuntu1) starting as process 124254 ... Oct 12 12:53:19 host systemd[1]: mariadb.service: start operation timed out. Terminating. Oct 12 12:53:20 host systemd[1]: mariadb.service: Failed with result 'timeout'. Oct 12 12:53:20 host systemd[1]: Failed to start MariaDB 10.3.22 database server. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: apt 2.0.2ubuntu0.1 ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60 Uname: Linux 5.4.0-48-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.9 Architecture: amd64 CasperMD5CheckResult: skip Date: Mon Oct 12 12:43:49 2020 ExecutablePath: /usr/bin/apt InstallationDate: Installed on 2020-05-11 (154 days ago) InstallationMedia: Ubuntu-Server 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) ProcEnviron: SHELL=/bin/bash LANG=en_US.UTF-8 TERM=xterm-256color PATH=(custom, no user) SourcePackage: apt UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: apt (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 apt in Ubuntu. https://bugs.launchpad.net/bugs/1899483 Title: long hang apt install mariadb-server on Ubuntu 20.04 server Status in apt package in Ubuntu: New Bug description: Ubuntu 20.04 server => no graphical user interface MariaDb is functional: mysqlshow works, mysqladmin create xxx works After 10 Minutes - the installation terminates - dbms terminates Oct 12 12:38:19 host systemd[1]: Starting MariaDB 10.3.22 database server... Oct 12 12:38:19 host mysqld[124254]: 2020-10-12 12:38:19 0 [Note] /usr/sbin/mysqld (mysqld 10.3.22-MariaDB-1ubuntu1) starting as process 124254 ... Oct 12 12:53:19 host systemd[1]: mariadb.service: start operation timed out. Terminating. Oct 12 12:53:20 host systemd[1]: mariadb.service: Failed with result 'timeout'. Oct 12 12:53:20 host systemd[1]: Failed to start MariaDB 10.3.22 database server. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: apt 2.0.2ubuntu0.1 ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60 Uname: Linux 5.4.0-48-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.9 Architecture: amd64 CasperMD5CheckResult: skip Date: Mon Oct 12 12:43:49 2020 ExecutablePath: /usr/bin/apt InstallationDate: Installed on 2020-05-11 (154 days ago) InstallationMedia: Ubuntu-Server 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) ProcEnviron: SHELL=/bin/bash LANG=en_US.UTF-8 TERM=xterm-256color PATH=(custom, no user) SourcePackage: apt UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1899483/+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 1893655] Re: Sony WH-1000XM3 headphones connect but don't appear in the audio devices list
This is still happening after upgrading to Ubuntu 20.10. -- 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/1893655 Title: Sony WH-1000XM3 headphones connect but don't appear in the audio devices list Status in bluez package in Ubuntu: New Status in pulseaudio package in Ubuntu: New Bug description: When I switch on my Sony WH-1000XM3 headphones, they reconnect to my laptop at Bluetooth level, but don't appear as an audio device. I have to remove them in the Ubuntu Bluetooth settings, and then re-pair them, every time. This is rather inconvenient. This started happening after upgrading to Ubuntu 20.04. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: bluez 5.53-0ubuntu3 ProcVersionSignature: Ubuntu 5.6.0-1021.21-oem 5.6.19 Uname: Linux 5.6.0-1021-oem x86_64 ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: Unity:Unity7:ubuntu Date: Mon Aug 31 14:48:53 2020 InstallationDate: Installed on 2020-07-14 (48 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) InterestingModules: rfcomm bnep btusb bluetooth MachineType: LENOVO 20U9CTO1WW ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.6.0-1021-oem root=UUID=42d20f5a-04dd-4073-ac83-e07bd283a1d1 ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/01/2020 dmi.bios.vendor: LENOVO dmi.bios.version: N2WET19W (1.09 ) dmi.board.asset.tag: Not Available dmi.board.name: 20U9CTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0R32862 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN2WET19W(1.09):bd07/01/2020:svnLENOVO:pn20U9CTO1WW:pvrThinkPadX1CarbonGen8:rvnLENOVO:rn20U9CTO1WW:rvrSDK0R32862WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X1 Carbon Gen 8 dmi.product.name: 20U9CTO1WW dmi.product.sku: LENOVO_MT_20U9_BU_Think_FM_ThinkPad X1 Carbon Gen 8 dmi.product.version: ThinkPad X1 Carbon Gen 8 dmi.sys.vendor: LENOVO hciconfig: hci0:Type: Primary Bus: USB BD Address: F8:AC:65:6D:04:AB ACL MTU: 1021:4 SCO MTU: 96:6 UP RUNNING RX bytes:1274806 acl:246 sco:0 events:180845 errors:0 TX bytes:152114364 acl:177469 sco:0 commands:3182 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1893655/+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 1899442] Re: Can't change output device from Settings
*** This bug is a duplicate of bug 1866194 *** https://bugs.launchpad.net/bugs/1866194 Err, I mean lp:1866194 :P ** This bug has been marked a duplicate of bug 1866194 External audio device shows up in the sound output options but the sound keeps being emitted from the internal laptop speaker, or none at all. -- 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/1899442 Title: Can't change output device from Settings Status in gnome-control-center package in Ubuntu: New Status in pulseaudio package in Ubuntu: New Bug description: I upgraded my Desktop from 18.04 to 20.04.1 and noticed that in addition to the appearance changes in the Sound Settings, there was also a regression. Steps to Reproduce: 1. Open Settings app and go to Sound section. 2. Click 'Test' button beside chosen Output Device. 3. Press the 'Front Left', 'Front Right', etc buttons and hear the corresponding output. 4. Change output device to a different device. 5. Try Step 3 again. Expected: The test audio plays out of the newly selected device. Actual: The test audio plays out of the previous device. Toggling the device does not help. Nor does restarting the Settings app. Note: This isn't just the Test Audio. Currently playing audio won't switch to the selected device, nor will any new audio started after the switch. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60 Uname: Linux 5.4.0-48-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.9 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Oct 12 01:40:21 2020 InstallationDate: Installed on 2018-09-01 (772 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_Card: USB PnP Sound Device - USB PnP Sound Device Symptom_PulseAudioLog: Oct 12 01:17:33 luq-home-pc dbus-daemon[945]: [system] Activating via systemd: service name='org.freedesktop.RealtimeKit1' unit='rtkit-daemon.service' requested by ':1.30' (uid=121 pid=1281 comm="/usr/bin/pulseaudio --daemonize=no --log-target=jo" label="unconfined") Oct 12 01:17:33 home-pc pulseaudio[1281]: No UCM verb is valid for hw:1 Oct 12 01:17:34 home-pc pulseaudio[1281]: No UCM verb is valid for hw:0 Oct 12 01:17:40 home-pc systemd[1275]: pulseaudio.service: Succeeded. Oct 12 01:17:51 home-pc systemd[1275]: pulseaudio.socket: Succeeded. Symptom_Type: Volume slider, or mixer problems Title: [HDA-Intel - HDA Intel PCH, playback] volume slider problem UpgradeStatus: Upgraded to focal on 2020-10-12 (0 days ago) dmi.bios.date: 10/26/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F2b dmi.board.asset.tag: Default string dmi.board.name: Z370N WIFI-CF dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF2b:bd10/26/2017:svnGigabyteTechnologyCo.,Ltd.:pnZ370NWIFI:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnZ370NWIFI-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: Z370N WIFI dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1899442/+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 1899442] Re: Can't change output device from Settings
*** This bug is a duplicate of bug 1866194 *** https://bugs.launchpad.net/bugs/1866194 Looks like a duplicate of lp:1899442. After clearing my .config/pulse things seem to work as intended. -- 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/1899442 Title: Can't change output device from Settings Status in gnome-control-center package in Ubuntu: New Status in pulseaudio package in Ubuntu: New Bug description: I upgraded my Desktop from 18.04 to 20.04.1 and noticed that in addition to the appearance changes in the Sound Settings, there was also a regression. Steps to Reproduce: 1. Open Settings app and go to Sound section. 2. Click 'Test' button beside chosen Output Device. 3. Press the 'Front Left', 'Front Right', etc buttons and hear the corresponding output. 4. Change output device to a different device. 5. Try Step 3 again. Expected: The test audio plays out of the newly selected device. Actual: The test audio plays out of the previous device. Toggling the device does not help. Nor does restarting the Settings app. Note: This isn't just the Test Audio. Currently playing audio won't switch to the selected device, nor will any new audio started after the switch. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60 Uname: Linux 5.4.0-48-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.9 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Oct 12 01:40:21 2020 InstallationDate: Installed on 2018-09-01 (772 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_Card: USB PnP Sound Device - USB PnP Sound Device Symptom_PulseAudioLog: Oct 12 01:17:33 luq-home-pc dbus-daemon[945]: [system] Activating via systemd: service name='org.freedesktop.RealtimeKit1' unit='rtkit-daemon.service' requested by ':1.30' (uid=121 pid=1281 comm="/usr/bin/pulseaudio --daemonize=no --log-target=jo" label="unconfined") Oct 12 01:17:33 home-pc pulseaudio[1281]: No UCM verb is valid for hw:1 Oct 12 01:17:34 home-pc pulseaudio[1281]: No UCM verb is valid for hw:0 Oct 12 01:17:40 home-pc systemd[1275]: pulseaudio.service: Succeeded. Oct 12 01:17:51 home-pc systemd[1275]: pulseaudio.socket: Succeeded. Symptom_Type: Volume slider, or mixer problems Title: [HDA-Intel - HDA Intel PCH, playback] volume slider problem UpgradeStatus: Upgraded to focal on 2020-10-12 (0 days ago) dmi.bios.date: 10/26/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F2b dmi.board.asset.tag: Default string dmi.board.name: Z370N WIFI-CF dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF2b:bd10/26/2017:svnGigabyteTechnologyCo.,Ltd.:pnZ370NWIFI:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnZ370NWIFI-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: Z370N WIFI dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1899442/+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 1899442] Re: Can't change output device from Settings
Updated description and title to indicate that the selected device choice is not respected for all audio, not just the test audio. ** Summary changed: - Test Output Device Button does not respect when you change the output device + Can't change output device from Settings ** Description changed: I upgraded my Desktop from 18.04 to 20.04.1 and noticed that in addition to the appearance changes in the Sound Settings, there was also a regression. Steps to Reproduce: 1. Open Settings app and go to Sound section. 2. Click 'Test' button beside chosen Output Device. 3. Press the 'Front Left', 'Front Right', etc buttons and hear the corresponding output. 4. Change output device to a different device. 5. Try Step 3 again. Expected: The test audio plays out of the newly selected device. Actual: The test audio plays out of the previous device. Toggling the device does not help. Nor does restarting the Settings app. + + Note: This isn't just the Test Audio. Currently playing audio won't + switch to the selected device, nor will any new audio started after the + switch. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60 Uname: Linux 5.4.0-48-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.9 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Oct 12 01:40:21 2020 InstallationDate: Installed on 2018-09-01 (772 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_Card: USB PnP Sound Device - USB PnP Sound Device Symptom_PulseAudioLog: Oct 12 01:17:33 luq-home-pc dbus-daemon[945]: [system] Activating via systemd: service name='org.freedesktop.RealtimeKit1' unit='rtkit-daemon.service' requested by ':1.30' (uid=121 pid=1281 comm="/usr/bin/pulseaudio --daemonize=no --log-target=jo" label="unconfined") Oct 12 01:17:33 home-pc pulseaudio[1281]: No UCM verb is valid for hw:1 Oct 12 01:17:34 home-pc pulseaudio[1281]: No UCM verb is valid for hw:0 Oct 12 01:17:40 home-pc systemd[1275]: pulseaudio.service: Succeeded. Oct 12 01:17:51 home-pc systemd[1275]: pulseaudio.socket: Succeeded. Symptom_Type: Volume slider, or mixer problems Title: [HDA-Intel - HDA Intel PCH, playback] volume slider problem UpgradeStatus: Upgraded to focal on 2020-10-12 (0 days ago) dmi.bios.date: 10/26/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F2b dmi.board.asset.tag: Default string dmi.board.name: Z370N WIFI-CF dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF2b:bd10/26/2017:svnGigabyteTechnologyCo.,Ltd.:pnZ370NWIFI:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnZ370NWIFI-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: Z370N WIFI dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. -- 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/1899442 Title: Can't change output device from Settings Status in gnome-control-center package in Ubuntu: New Status in pulseaudio package in Ubuntu: New Bug description: I upgraded my Desktop from 18.04 to 20.04.1 and noticed that in addition to the appearance changes in the Sound Settings, there was also a regression. Steps to Reproduce: 1. Open Settings app and go to Sound section. 2. Click 'Test' button beside chosen Output Device. 3. Press the 'Front Left', 'Front Right', etc buttons and hear the corresponding output. 4. Change output device to a different device. 5. Try Step 3 again. Expected: The test audio plays out of the newly selected device. Actual: The test audio plays out of the previous device. Toggling the device does not help. Nor does restarting the Settings app. Note: This isn't just the Test Audio. Currently playing audio won't switch to the selected device, nor will any new audio started after the switch. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60 Uname: Linux 5.4.0-48-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.9 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Oct 12 01:40:21 2020 InstallationDate: Installed on 2018-09-01 (772 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) PackageArchitecture: all SourcePackage: alsa-driver Sym
[Touch-packages] [Bug 483928] Re: ssh-keyscan(1) exits prematurely on some non-fatal errors
8 years later, we saw this on one of our customer's systems. Looking at the status of this entry, it looks like it's still unresolved? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/483928 Title: ssh-keyscan(1) exits prematurely on some non-fatal errors Status in portable OpenSSH: Confirmed Status in openssh package in Ubuntu: Confirmed Bug description: Binary package hint: openssh-client This concerns openssh-client 1:5.1p1-5ubuntu1 in Karmic. I am using ssh-keyscan(1) for its intended purpose: building an ssh_known_hosts file for a large network. Most of the hosts on this network are well-maintained systems, with properly-functioning SSH servers, and present no difficulty to the program. However, a handful of hosts are barely alive, with SSH servers that are not exactly in good working order. ssh-keyscan(1) currently will scan these systems, encounter some form of error, and then---right here is the problem---exit in the middle of the scan. The last bit of stderr output may look like # A.B.C.D SSH-2.0-OpenSSH_4.3 # A.B.C.E SSH-2.0-OpenSSH_4.3 # A.B.C.F SSH-1.99-OpenSSH_3.7p1 Connection closed by A.B.C.F or # A.B.C.D SSH-2.0-OpenSSH_4.1 # A.B.C.E SSH-2.0-OpenSSH_4.1 # A.B.C.F SSH-2.0-mpSSH_0.1.0 Received disconnect from A.B.C.F: 10: Protocol error or # A.B.C.D SSH-2.0-OpenSSH_4.4p1 # A.B.C.E SSH-2.0-OpenSSH_5.0p1 # A.B.C.F SSH-2.0-mpSSH_0.1.0 Received disconnect from A.B.C.F: 11: SSH Disabled (These are the different failure modes I've observed to date) ssh-keyscan(1) needs to be robust to these kinds of errors---simply make a note of them, and continue on with the scan. I don't want to have to find out which systems are misbehaving by running and re- running the scan (each run yields at most one bad host, obviously), nor manually edit out the few bad apples from the input list of hosts (especially considering that this particular subset can change over time). Neither is feasible when the number of hosts being scanned is very large. To manage notifications about this bug go to: https://bugs.launchpad.net/openssh/+bug/483928/+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 1884514] Comment bridged from LTC Bugzilla
--- Comment From heinz-werner_se...@de.ibm.com 2020-10-12 06:44 EDT--- IBM Bugzilla status-> closed , Fix Released with groovy -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to zlib in Ubuntu. https://bugs.launchpad.net/bugs/1884514 Title: [FFe][20.10 FEAT] zlib/gzip hardware compression enablement Status in Ubuntu on IBM z Systems: Fix Released Status in zlib package in Ubuntu: Fix Released Bug description: [Feature Freeze Exception] 1. Feature: The latest s390x hardware comes with a new concept for hardware assisted compression/decompression, based on a 'Next Accelerator Function unit' (NXU). This is an on-chip concept, a co-processor for compression available to all cores on the same chip. It provides functions as normal 'problem state' instructions (in other words user space instructions that are directly consumable by libraries and applications) and supports DEFLATE compliant compression/decompression + GZIP CRC/ZLIB Adler. To enable this hardware support for zlib and gzip, zlib needs to be compiled with CFLAGS="-O2 -DDFLTCC -DDFLTCC_LEVEL_MASK=0x7e". The value of 0x7e enables hardware compression for the compression levels 1-6 (out of 0-9). There is a significant business value of having the enablement active by default, since tests on a system with 4 IFLs and hardware compression enabled this way offered (especially for DEFLATE as best case) a speed up of more than 40x. 2. Changes Adding CFLAGS="-O2 -DDFLTCC -DDFLTCC_LEVEL_MASK=0x7e" attributes/macro during build of zlib and gzip. 3. Regression risk The concept is new and comes with IBM z15 and LinuxONE III only and is with that specific and limited to s390x. Hence a potential regressions of this late addition would be limited to s390x and there again with the above changes to zlib (and gzip). In case of unforeseen issues with the NXU hardware component, a fallback to software is done. On top a modified zlib package was build and made available in a PPA for further testing. This change should have been included earlier, but was blocked by other zlib tickets/bugs that needed to be fixed and integrated first (like LP 1893170), hence this request for late addition. __ HW Compression need to be enabled with Default-Compression-Level 6. Adding following CFLAGS attributes during build of zlib and gzip "-DDFLTCC_LEVEL_MASK=0x7e" CFLAGS="-O2 -DDFLTCC -DDFLTCC_LEVEL_MASK=0x7e" ./configure To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1884514/+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 1884514] Re: [FFe][20.10 FEAT] zlib/gzip hardware compression enablement
** Changed in: ubuntu-z-systems Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to zlib in Ubuntu. https://bugs.launchpad.net/bugs/1884514 Title: [FFe][20.10 FEAT] zlib/gzip hardware compression enablement Status in Ubuntu on IBM z Systems: Fix Released Status in zlib package in Ubuntu: Fix Released Bug description: [Feature Freeze Exception] 1. Feature: The latest s390x hardware comes with a new concept for hardware assisted compression/decompression, based on a 'Next Accelerator Function unit' (NXU). This is an on-chip concept, a co-processor for compression available to all cores on the same chip. It provides functions as normal 'problem state' instructions (in other words user space instructions that are directly consumable by libraries and applications) and supports DEFLATE compliant compression/decompression + GZIP CRC/ZLIB Adler. To enable this hardware support for zlib and gzip, zlib needs to be compiled with CFLAGS="-O2 -DDFLTCC -DDFLTCC_LEVEL_MASK=0x7e". The value of 0x7e enables hardware compression for the compression levels 1-6 (out of 0-9). There is a significant business value of having the enablement active by default, since tests on a system with 4 IFLs and hardware compression enabled this way offered (especially for DEFLATE as best case) a speed up of more than 40x. 2. Changes Adding CFLAGS="-O2 -DDFLTCC -DDFLTCC_LEVEL_MASK=0x7e" attributes/macro during build of zlib and gzip. 3. Regression risk The concept is new and comes with IBM z15 and LinuxONE III only and is with that specific and limited to s390x. Hence a potential regressions of this late addition would be limited to s390x and there again with the above changes to zlib (and gzip). In case of unforeseen issues with the NXU hardware component, a fallback to software is done. On top a modified zlib package was build and made available in a PPA for further testing. This change should have been included earlier, but was blocked by other zlib tickets/bugs that needed to be fixed and integrated first (like LP 1893170), hence this request for late addition. __ HW Compression need to be enabled with Default-Compression-Level 6. Adding following CFLAGS attributes during build of zlib and gzip "-DDFLTCC_LEVEL_MASK=0x7e" CFLAGS="-O2 -DDFLTCC -DDFLTCC_LEVEL_MASK=0x7e" ./configure To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1884514/+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 1884514] Re: [FFe][20.10 FEAT] zlib/gzip hardware compression enablement
This bug was fixed in the package zlib - 1:1.2.11.dfsg-2ubuntu3 --- zlib (1:1.2.11.dfsg-2ubuntu3) groovy; urgency=medium * Enable hardware compression on s390x at level 6. LP: #1884514 -- Michael Hudson-Doyle Thu, 24 Sep 2020 08:44:35 +1200 ** Changed in: zlib (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to zlib in Ubuntu. https://bugs.launchpad.net/bugs/1884514 Title: [FFe][20.10 FEAT] zlib/gzip hardware compression enablement Status in Ubuntu on IBM z Systems: Fix Committed Status in zlib package in Ubuntu: Fix Released Bug description: [Feature Freeze Exception] 1. Feature: The latest s390x hardware comes with a new concept for hardware assisted compression/decompression, based on a 'Next Accelerator Function unit' (NXU). This is an on-chip concept, a co-processor for compression available to all cores on the same chip. It provides functions as normal 'problem state' instructions (in other words user space instructions that are directly consumable by libraries and applications) and supports DEFLATE compliant compression/decompression + GZIP CRC/ZLIB Adler. To enable this hardware support for zlib and gzip, zlib needs to be compiled with CFLAGS="-O2 -DDFLTCC -DDFLTCC_LEVEL_MASK=0x7e". The value of 0x7e enables hardware compression for the compression levels 1-6 (out of 0-9). There is a significant business value of having the enablement active by default, since tests on a system with 4 IFLs and hardware compression enabled this way offered (especially for DEFLATE as best case) a speed up of more than 40x. 2. Changes Adding CFLAGS="-O2 -DDFLTCC -DDFLTCC_LEVEL_MASK=0x7e" attributes/macro during build of zlib and gzip. 3. Regression risk The concept is new and comes with IBM z15 and LinuxONE III only and is with that specific and limited to s390x. Hence a potential regressions of this late addition would be limited to s390x and there again with the above changes to zlib (and gzip). In case of unforeseen issues with the NXU hardware component, a fallback to software is done. On top a modified zlib package was build and made available in a PPA for further testing. This change should have been included earlier, but was blocked by other zlib tickets/bugs that needed to be fixed and integrated first (like LP 1893170), hence this request for late addition. __ HW Compression need to be enabled with Default-Compression-Level 6. Adding following CFLAGS attributes during build of zlib and gzip "-DDFLTCC_LEVEL_MASK=0x7e" CFLAGS="-O2 -DDFLTCC -DDFLTCC_LEVEL_MASK=0x7e" ./configure To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1884514/+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 1878194] Re: [Sennheiser HD 4.50 BTNC] Bluetooth headset not working when selecting HSP/HFP audio profile in Focal Fossa
*** This bug is a duplicate of bug 1871794 *** https://bugs.launchpad.net/bugs/1871794 For me it is fixed since the latest kernel update, 5.4.0-48-generic. - Ubuntu 20.04.1 LTS - Dell XPS 15 7590 - Bose QuietComfort 35 II -- 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/1878194 Title: [Sennheiser HD 4.50 BTNC] Bluetooth headset not working when selecting HSP/HFP audio profile in Focal Fossa Status in bluez package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Confirmed Bug description: After updating the release from Ubuntu 19.10 to 20.04, the bluetooth headset doesn't work anymore when HSP/HFP profile is selected. With Ubuntu 19.10 the headset was working, there was audio and the mic was perfect for video conferencing. [Steps to reproduce] 1. Connect headset (used blueman to setup and connect) 1.1. When connected the system automatically selects A2DP profile 2. Start playing audio (browser or other) 3. Change profile to HSP/HFP with pavucontrol (or blueman) 4. The audio disappears and microphone is not working (no input) 5. Optionally switch back to A2DP and the audio comes back [Expected] When switching to HSP/HFP the audio should keep playing and the microphone should start working [Notes] I tried with pavucontrol to switch between profiles while playing audio from a browser. As side note there's a led in the headset that still blinks when switching profile. I tried deleting the pulse folder under user's profile .config without success, also reinstalled packages and did a `sudo alsa force-reload` and rebooting several times. Note: not sure this is a duplicate of [Bug #1576559], it looks quite different since the profile changes but the headset stops working. [System info] Ubuntu: 20.04 - Linux 5.4.0-29-generic x86_64 pulseaudio: 1:13.99.1-1ubuntu3 bluez: 5.53-0ubuntu3 Headset: Sennheiser HD 4.50 BTNC To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1878194/+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 1871794] Re: [Bluetooth] No audio output/input in HSP/HFP mode
For me it is fixed since the latest kernel update, 5.4.0-48-generic. - Ubuntu 20.04.1 LTS - Dell XPS 15 7590 - Bose QuietComfort 35 II -- 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/1871794 Title: [Bluetooth] No audio output/input in HSP/HFP mode Status in bluez package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Confirmed Bug description: I'm testing with Sony bluetooth headset SBH20, works fine in A2DP profile, but I can't get audio input and output work in HSP/HFP profile. [Reproduce steps] 1. Scan and pair BT headset in Bluetooth setting 2. Switch to HSP/HFP profile in Sound setting 3. Test sound output/input [Machine information] ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu25 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1359 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Thu Apr 9 16:26:52 2020 InstallationDate: Installed on 2020-04-09 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) SourcePackage: pulseaudio Symptom: audio Symptom_Card: SBH20 Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1359 F pulseaudio Symptom_Type: No sound at all Title: [SBH20, recording] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/17/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.0.13 dmi.board.name: 0188D1 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 31 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.0.13:bd09/17/2019:svnDellInc.:pnXPS1373902-in-1:pvr:rvnDellInc.:rn0188D1:rvrA00:cvnDellInc.:ct31:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 7390 2-in-1 dmi.product.sku: 08B0 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1871794/+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 1873678] Re: gnome-language-selector crashed with dbus.exceptions.DBusException in call_blocking(): org.freedesktop.Accounts.Error.Failed: 'C.UTF-8' is not a valid locale name
This bug was fixed in the package accountsservice - 0.6.55-0ubuntu13 --- accountsservice (0.6.55-0ubuntu13) groovy; urgency=medium * debian/patches/0010-set-language.patch: - Don't dismiss C.UTF-8 as an invalid locale name (LP: #1873678) -- Gunnar Hjalmarsson Fri, 09 Oct 2020 15:08:15 +0200 ** Changed in: accountsservice (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to accountsservice in Ubuntu. https://bugs.launchpad.net/bugs/1873678 Title: gnome-language-selector crashed with dbus.exceptions.DBusException in call_blocking(): org.freedesktop.Accounts.Error.Failed: 'C.UTF-8' is not a valid locale name Status in accountsservice package in Ubuntu: Fix Released Status in accountsservice source package in Focal: In Progress Bug description: [Impact] accountsservice includes a function for checking the validity of locales, and it incorrectly considers "C.UTF-8" to be invalid. It leads to incorrect behavior under certain conditions and also a crash if the function was triggered from language-selector-gnome. Even if this only makes a difference in special corner cases, it happens often enough to justify this SRU: https://errors.ubuntu.com/?release=Ubuntu%2020.04&package=language- selector&period=year (It's the top ranked crash type in the list.) The version in focal-proposed fixes the issue. [Test case] Make a fresh install of Ubuntu 20.04 (a VM works fine) Once logged in: * Install accountsservice, gir1.2-accountsservice-1.0 and libaccountsservice0 from focal-proposed * Open /etc/default/locale for editing, replace its contents with the single line: LANG=C.UTF-8 and reboot. Open Language Support and change language (drag any language above the "English" item) Open ~/.pam_environment and find that e.g. LANG is now the locale representing the language you selected, while e.g. LC_TIME is set to "C.UTF-8". [Regression risk] This is a oneliner which white list "C.UTF-8" as a valid locale name. I can't think of a case where this would cause unexpected behavior. [Original description] USB live disk (20.04 beta) ProblemType: Crash DistroRelease: Ubuntu 20.04 Package: language-selector-gnome 0.203 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu22 Architecture: amd64 CasperVersion: 1.442 CurrentDesktop: MATE Date: Sun Apr 19 17:07:26 2020 ExecutablePath: /usr/bin/gnome-language-selector InterpreterPath: /usr/bin/python3.8 LiveMediaBuild: Ubuntu-MATE 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) PackageArchitecture: all ProcCmdline: /usr/bin/python3 /usr/bin/gnome-language-selector ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 3.8.2-0ubuntu1 PythonArgs: ['/usr/bin/gnome-language-selector'] PythonDetails: N/A SourcePackage: language-selector Title: gnome-language-selector crashed with dbus.exceptions.DBusException in call_blocking(): org.freedesktop.Accounts.Error.Failed: 'C.UTF-8' is not a valid locale name UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/1873678/+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 1899442] Re: Test Output Device Button does not respect when you change the output device
Also interestingly, the little Testing window popup now lets you press multiple buttons and hear the test sounds simultaneously whereas before it was one at a time. -- 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/1899442 Title: Test Output Device Button does not respect when you change the output device Status in gnome-control-center package in Ubuntu: New Status in pulseaudio package in Ubuntu: New Bug description: I upgraded my Desktop from 18.04 to 20.04.1 and noticed that in addition to the appearance changes in the Sound Settings, there was also a regression. Steps to Reproduce: 1. Open Settings app and go to Sound section. 2. Click 'Test' button beside chosen Output Device. 3. Press the 'Front Left', 'Front Right', etc buttons and hear the corresponding output. 4. Change output device to a different device. 5. Try Step 3 again. Expected: The test audio plays out of the newly selected device. Actual: The test audio plays out of the previous device. Toggling the device does not help. Nor does restarting the Settings app. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60 Uname: Linux 5.4.0-48-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.9 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Oct 12 01:40:21 2020 InstallationDate: Installed on 2018-09-01 (772 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_Card: USB PnP Sound Device - USB PnP Sound Device Symptom_PulseAudioLog: Oct 12 01:17:33 luq-home-pc dbus-daemon[945]: [system] Activating via systemd: service name='org.freedesktop.RealtimeKit1' unit='rtkit-daemon.service' requested by ':1.30' (uid=121 pid=1281 comm="/usr/bin/pulseaudio --daemonize=no --log-target=jo" label="unconfined") Oct 12 01:17:33 home-pc pulseaudio[1281]: No UCM verb is valid for hw:1 Oct 12 01:17:34 home-pc pulseaudio[1281]: No UCM verb is valid for hw:0 Oct 12 01:17:40 home-pc systemd[1275]: pulseaudio.service: Succeeded. Oct 12 01:17:51 home-pc systemd[1275]: pulseaudio.socket: Succeeded. Symptom_Type: Volume slider, or mixer problems Title: [HDA-Intel - HDA Intel PCH, playback] volume slider problem UpgradeStatus: Upgraded to focal on 2020-10-12 (0 days ago) dmi.bios.date: 10/26/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F2b dmi.board.asset.tag: Default string dmi.board.name: Z370N WIFI-CF dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF2b:bd10/26/2017:svnGigabyteTechnologyCo.,Ltd.:pnZ370NWIFI:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnZ370NWIFI-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: Z370N WIFI dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1899442/+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 1899442] Re: Test Output Device Button does not respect when you change the output device
** Also affects: pulseaudio (Ubuntu) Importance: Undecided Status: New -- 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/1899442 Title: Test Output Device Button does not respect when you change the output device Status in gnome-control-center package in Ubuntu: New Status in pulseaudio package in Ubuntu: New Bug description: I upgraded my Desktop from 18.04 to 20.04.1 and noticed that in addition to the appearance changes in the Sound Settings, there was also a regression. Steps to Reproduce: 1. Open Settings app and go to Sound section. 2. Click 'Test' button beside chosen Output Device. 3. Press the 'Front Left', 'Front Right', etc buttons and hear the corresponding output. 4. Change output device to a different device. 5. Try Step 3 again. Expected: The test audio plays out of the newly selected device. Actual: The test audio plays out of the previous device. Toggling the device does not help. Nor does restarting the Settings app. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60 Uname: Linux 5.4.0-48-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.9 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Oct 12 01:40:21 2020 InstallationDate: Installed on 2018-09-01 (772 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_Card: USB PnP Sound Device - USB PnP Sound Device Symptom_PulseAudioLog: Oct 12 01:17:33 luq-home-pc dbus-daemon[945]: [system] Activating via systemd: service name='org.freedesktop.RealtimeKit1' unit='rtkit-daemon.service' requested by ':1.30' (uid=121 pid=1281 comm="/usr/bin/pulseaudio --daemonize=no --log-target=jo" label="unconfined") Oct 12 01:17:33 home-pc pulseaudio[1281]: No UCM verb is valid for hw:1 Oct 12 01:17:34 home-pc pulseaudio[1281]: No UCM verb is valid for hw:0 Oct 12 01:17:40 home-pc systemd[1275]: pulseaudio.service: Succeeded. Oct 12 01:17:51 home-pc systemd[1275]: pulseaudio.socket: Succeeded. Symptom_Type: Volume slider, or mixer problems Title: [HDA-Intel - HDA Intel PCH, playback] volume slider problem UpgradeStatus: Upgraded to focal on 2020-10-12 (0 days ago) dmi.bios.date: 10/26/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F2b dmi.board.asset.tag: Default string dmi.board.name: Z370N WIFI-CF dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF2b:bd10/26/2017:svnGigabyteTechnologyCo.,Ltd.:pnZ370NWIFI:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnZ370NWIFI-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: Z370N WIFI dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1899442/+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 1899442] [NEW] Test Output Device Button does not respect when you change the output device
Public bug reported: I upgraded my Desktop from 18.04 to 20.04.1 and noticed that in addition to the appearance changes in the Sound Settings, there was also a regression. Steps to Reproduce: 1. Open Settings app and go to Sound section. 2. Click 'Test' button beside chosen Output Device. 3. Press the 'Front Left', 'Front Right', etc buttons and hear the corresponding output. 4. Change output device to a different device. 5. Try Step 3 again. Expected: The test audio plays out of the newly selected device. Actual: The test audio plays out of the previous device. Toggling the device does not help. Nor does restarting the Settings app. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60 Uname: Linux 5.4.0-48-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.9 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Oct 12 01:40:21 2020 InstallationDate: Installed on 2018-09-01 (772 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_Card: USB PnP Sound Device - USB PnP Sound Device Symptom_PulseAudioLog: Oct 12 01:17:33 luq-home-pc dbus-daemon[945]: [system] Activating via systemd: service name='org.freedesktop.RealtimeKit1' unit='rtkit-daemon.service' requested by ':1.30' (uid=121 pid=1281 comm="/usr/bin/pulseaudio --daemonize=no --log-target=jo" label="unconfined") Oct 12 01:17:33 home-pc pulseaudio[1281]: No UCM verb is valid for hw:1 Oct 12 01:17:34 home-pc pulseaudio[1281]: No UCM verb is valid for hw:0 Oct 12 01:17:40 home-pc systemd[1275]: pulseaudio.service: Succeeded. Oct 12 01:17:51 home-pc systemd[1275]: pulseaudio.socket: Succeeded. Symptom_Type: Volume slider, or mixer problems Title: [HDA-Intel - HDA Intel PCH, playback] volume slider problem UpgradeStatus: Upgraded to focal on 2020-10-12 (0 days ago) dmi.bios.date: 10/26/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F2b dmi.board.asset.tag: Default string dmi.board.name: Z370N WIFI-CF dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF2b:bd10/26/2017:svnGigabyteTechnologyCo.,Ltd.:pnZ370NWIFI:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnZ370NWIFI-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: Z370N WIFI dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. ** Affects: gnome-control-center (Ubuntu) Importance: Undecided Status: New ** Affects: pulseaudio (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ** Description changed: I upgraded my Desktop from 18.04 to 20.04.1 and noticed that in addition to the appearance changes in the Sound Settings, there was also a regression. Steps to Reproduce: 1. Open Settings app and go to Sound section. 2. Click 'Test' button beside chosen Output Device. 3. Press the 'Front Left', 'Front Right', etc buttons and hear the corresponding output. 4. Change output device to a different device. 5. Try Step 3 again. Expected: The test audio plays out of the newly selected device. Actual: The test audio plays out of the previous device. Toggling the device does not help. Nor does restarting the Settings app. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60 Uname: Linux 5.4.0-48-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.9 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Oct 12 01:40:21 2020 InstallationDate: Installed on 2018-09-01 (772 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_Card: USB PnP Sound Device - USB PnP Sound Device Symptom_PulseAudioLog: - Oct 12 01:17:33 luq-home-pc dbus-daemon[945]: [system] Activating via systemd: service name='org.freedesktop.RealtimeKit1' unit='rtkit-daemon.service' requested by ':1.30' (uid=121 pid=1281 comm="/usr/bin/pulseaudio --daemonize=no --log-target=jo" label="unconfined") - Oct 12 01:17:33 luq-home-pc pulseaudio[1281]: No UCM verb is valid for hw:1 - Oct 12 01:17:34 luq-home-pc pulseaudio[1281]: No UCM verb is valid for hw:0 - Oct 12 01:17:40 luq-home-pc systemd[1275]: pulseaudio.service: Succeeded. - Oct 12 01:17:51 luq-home-pc systemd[1275]: pulseaudio.socket: Succeeded. + Oct 12 01:17:33 luq-home-pc dbus-daemon[945]: [system] Activating via systemd: service name='org.freedesktop.RealtimeKit1' unit='rtkit-dae
[Touch-packages] [Bug 1899315] Re: Keyboard won't work in password entry when resuming
If I attempt to "Switch users" it'll give me a different graphical login, let me type my password, blank the screens and be back where I was. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1899315 Title: Keyboard won't work in password entry when resuming Status in lightdm package in Ubuntu: New Bug description: If I lock my screen and return, lightdm-gtk will ask for my password, but accepts no keyboard input. I can Ctrl-Alt-F1, log in and restart the lightdm service which mostly solves the issue, but this is a pain to do every time. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: lightdm 1.30.0-0ubuntu3.1 ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60 Uname: Linux 5.4.0-48-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.9 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: XFCE Date: Sun Oct 11 15:19:25 2020 InstallationDate: Installed on 2017-08-29 (1138 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) SourcePackage: lightdm UpgradeStatus: Upgraded to focal on 2020-10-09 (2 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1899315/+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 1838151] Re: Poor quality audio with modern Bluetooth headsets in HSP/HFP. Missing wide band speech support (Bluetooth A2DP codecs).
Same here (Ubuntu 20.04) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1838151 Title: Poor quality audio with modern Bluetooth headsets in HSP/HFP. Missing wide band speech support (Bluetooth A2DP codecs). Status in PulseAudio: New Status in bluez package in Ubuntu: Fix Released Status in linux package in Ubuntu: Fix Released Status in pulseaudio package in Ubuntu: In Progress Status in Arch Linux: New Bug description: Bluetooth HSP/HFP audio quality is poor on Ubuntu comparative to all other major platforms (Windows, MacOS, ChromeOS, Android, iOS). Modern Bluetooth headsets (such as the Bose QC series headphones, many others) are capable of using HFP 1.6 with mSBC 16kHz audio encoding. As it currently stands, Ubuntu defaults to only supporting HSP headsets using 8kHz CVSD, and is incapable of supporting HFP 1.6 at this time. The ChromiumOS team recently tackled this issue - https://bugs.chromium.org/p/chromium/issues/detail?id=843048 Their efforts may assist in bringing this to Ubuntu, however it appears that there are quite a lot of differences considering they have developed their own audio server solution etc. The Bluetooth Telephony Working Group published the HFP 1.6 spec in May 2011 - https://www.bluetooth.org/docman/handlers/downloaddoc.ashx?doc_id=238193 Patches have been proposed in the past for this issue to the kernel and PulseAudio: PulseAudio: https://patchwork.freedesktop.org/patch/245272/ Kernel: https://www.spinics.net/lists/linux-bluetooth/msg76982.html It appears that the Chromium OS team applied the same kernel patch: https://chromium.googlesource.com/chromiumos/third_party/kernel/+/77dd0cb94c1713a8a12f6e392955dfa64c430e54 ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: pulseaudio 1:12.2-2ubuntu3 ProcVersionSignature: Ubuntu 5.0.0-20.21-generic 5.0.8 Uname: Linux 5.0.0-20-generic x86_64 ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jnappi 2777 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sat Jul 27 11:08:29 2019 EcryptfsInUse: Yes InstallationDate: Installed on 2017-11-04 (629 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio UpgradeStatus: Upgraded to disco on 2019-07-18 (9 days ago) dmi.bios.date: 06/07/2016 dmi.bios.vendor: LENOVO dmi.bios.version: R07ET67W (2.07 ) dmi.board.asset.tag: Not Available dmi.board.name: 20FW000TUS dmi.board.vendor: LENOVO dmi.board.version: SDK0J40705 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrR07ET67W(2.07):bd06/07/2016:svnLENOVO:pn20FW000TUS:pvrThinkPadT460p:rvnLENOVO:rn20FW000TUS:rvrSDK0J40705WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T460p dmi.product.name: 20FW000TUS dmi.product.sku: LENOVO_MT_20FW_BU_Think_FM_ThinkPad T460p dmi.product.version: ThinkPad T460p dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/1838151/+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 1316518] Re: [900X3G, Realtek ALC282, Mic, Internal] inverted mic not working
Still exist in 20.04 ** Attachment added: "status-s900x-2020-10-12=09-30.bash" https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1316518/+attachment/5421161/+files/status-s900x-2020-10-12%3D09-30.bash -- 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/1316518 Title: [900X3G, Realtek ALC282, Mic, Internal] inverted mic not working Status in alsa-driver package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: Internal Mic of Samsung Ativ book 9 (NP900X3G) is not supported properly. Stereo recording in audacity records sound from mic in L channel and only loud noise in R channel (phase inverted?) Muting R channel, and setting L channel to around 16%, in pavucontrol allows to record audio, but in poor quality. alsa-info.sh output: http://www.alsa- project.org/db/?f=064f0b536a1b068efd30d58c2641b5ec2348f059 Ubuntu Gnome 14.04 ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: alsa-base 1.0.25+dfsg-0ubuntu4 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 ApportVersion: 2.14.1-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: sarah 2014 F pulseaudio sarah 8509 F alsamixer /dev/snd/controlC0: sarah 2014 F pulseaudio CurrentDesktop: GNOME Date: Tue May 6 11:55:36 2014 InstallationDate: Installed on 2014-04-29 (6 days ago) InstallationMedia: Ubuntu-GNOME 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.2) PackageArchitecture: all ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaRecordingTest: ALSA recording test through plughw:PCH failed Symptom_Card: Internes Audio - HDA Intel PCH Symptom_Jack: Mic, Internal Symptom_Type: None of the above Title: [900X3G, Realtek ALC282, Mic, Internal] Recording problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/14/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P04ADU.023.140414.PS dmi.board.asset.tag: No Asset Tag dmi.board.name: NP900X3G-K02DE dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.board.version: SAMSUNG_SW_REVISION_1234567890ABCD dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP04ADU.023.140414.PS:bd04/14/2014:svnSAMSUNGELECTRONICSCO.,LTD.:pn900X3G:pvrP04ADU:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNP900X3G-K02DE:rvrSAMSUNG_SW_REVISION_1234567890ABCD:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvrN/A: dmi.product.name: 900X3G dmi.product.version: P04ADU dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD. --- ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: sarah 2004 F pulseaudio /dev/snd/controlC1: sarah 2004 F pulseaudio CurrentDesktop: GNOME DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=UUID=b4bd3914-d1c4-40f0-ba32-fb19aa9af13c InstallationDate: Installed on 2014-04-29 (27 days ago) InstallationMedia: Ubuntu-GNOME 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.2) MachineType: SAMSUNG ELECTRONICS CO., LTD. 900X3G Package: linux (not installed) ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-24-generic root=UUID=92ac4966-692f-4e06-a1dd-da069008e861 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.13.0-24.47-generic 3.13.9 RelatedPackageVersions: linux-restricted-modules-3.13.0-24-generic N/A linux-backports-modules-3.13.0-24-generic N/A linux-firmware 1.127.2 StagingDrivers: rts5139 Tags: trusty trusty staging Uname: Linux 3.13.0-24-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/14/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P04ADU.023.140414.PS dmi.board.asset.tag: No Asset Tag dmi.board.name: NP900X3G-K02DE dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.board.version: SAMSUNG_SW_REVISION_1234567890ABCD dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP04ADU.023.140414.PS:bd04/14/2014:svnSAMSUNGELECTRONICSCO.,LTD.:pn900X3G:pvrP04ADU:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNP900X3G-K02DE:rvrSAMSUNG_SW_REVISION_1234567890ABCD:c
[Touch-packages] [Bug 1892643] Re: [SRU] Update libgweather to 3.36.1
** Changed in: libgweather (Ubuntu Focal) Status: New => In Progress -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libgweather in Ubuntu. https://bugs.launchpad.net/bugs/1892643 Title: [SRU] Update libgweather to 3.36.1 Status in libgweather: Unknown Status in libgweather package in Ubuntu: Fix Released Status in libgweather source package in Focal: In Progress Status in libgweather package in Debian: Unknown Bug description: [Impact] libgweather 3.36.1 is a bug-fix release as part of GNOME 3.36. https://gitlab.gnome.org/GNOME/libgweather/-/blob/gnome-3-36/NEWS This version works around the unavailability of the NOAA weather services by using very short-term forecasts as current weather conditions. Sometimes the current weather is not available because the NOAA weather servers aren't working correctly. Version 3.36.1 fixes the unavailability of current temperature in some locations. [Test case] Make sure that gnome-weather is still working properly and the weather in gnome-shell is shown when gnome-weather is installed. [Regression potential] The regression potential is low since the changes in version 3.36.1 are small. [Other] libgweather 3.36.1 has been successfully built as a no-change backport from Groovy to Focal in my PPA and runs fine: https://launchpad.net/~amribrahim1987/+archive/ubuntu/ppa/+packages?field.name_filter=libgweather&field.status_filter=published&field.series_filter= ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: libgweather-3-16 3.36.0-1 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 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Aug 23 19:05:21 2020 InstallationDate: Installed on 2020-04-26 (119 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: libgweather UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/libgweather/+bug/1892643/+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 1892643] Re: [SRU] Update libgweather to 3.36.1
I reapplied your debian/changelog directly and pushed to focal (pending approval). Thanks a lot! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libgweather in Ubuntu. https://bugs.launchpad.net/bugs/1892643 Title: [SRU] Update libgweather to 3.36.1 Status in libgweather: Unknown Status in libgweather package in Ubuntu: Fix Released Status in libgweather source package in Focal: New Status in libgweather package in Debian: Unknown Bug description: [Impact] libgweather 3.36.1 is a bug-fix release as part of GNOME 3.36. https://gitlab.gnome.org/GNOME/libgweather/-/blob/gnome-3-36/NEWS This version works around the unavailability of the NOAA weather services by using very short-term forecasts as current weather conditions. Sometimes the current weather is not available because the NOAA weather servers aren't working correctly. Version 3.36.1 fixes the unavailability of current temperature in some locations. [Test case] Make sure that gnome-weather is still working properly and the weather in gnome-shell is shown when gnome-weather is installed. [Regression potential] The regression potential is low since the changes in version 3.36.1 are small. [Other] libgweather 3.36.1 has been successfully built as a no-change backport from Groovy to Focal in my PPA and runs fine: https://launchpad.net/~amribrahim1987/+archive/ubuntu/ppa/+packages?field.name_filter=libgweather&field.status_filter=published&field.series_filter= ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: libgweather-3-16 3.36.0-1 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 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Aug 23 19:05:21 2020 InstallationDate: Installed on 2020-04-26 (119 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: libgweather UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/libgweather/+bug/1892643/+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 1742865] Re: Lenovo Yoga 500-15ISK Fn Keys do not work, nvidia card not found
This is two separate issues: 1. Please tell us if you still have a problem with Fn keys not working in a more recent Ubuntu release. 2. The nvidia card is detected according to your Lspci.txt, but it appears there's just no driver installed for it. ** Summary changed: - Fn Keys do not work, nvidia card not found + Lenovo Yoga 500-15ISK Fn Keys do not work, nvidia card not found ** Package changed: xorg (Ubuntu) => linux (Ubuntu) ** 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/1742865 Title: Lenovo Yoga 500-15ISK Fn Keys do not work, nvidia card not found Status in linux package in Ubuntu: Incomplete Bug description: Browsed and tried solutions over the past 2 years, nothing worked... ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-108.131-generic 4.4.98 Uname: Linux 4.4.0-108-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Fri Jan 12 06:43:48 2018 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Sky Lake Integrated Graphics [8086:1916] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Lenovo Skylake Integrated Graphics [17aa:3828] Subsystem: Lenovo GM108M [GeForce 940M] [17aa:3829] InstallationDate: Installed on 2016-07-07 (553 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 04f3:208d Elan Microelectronics Corp. Bus 001 Device 003: ID 174f:14e6 Syntek Bus 001 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 80R6 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-108-generic.efi.signed root=UUID=8fa7aafa-77cc-4651-b87f-4565439e7577 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/28/2015 dmi.bios.vendor: LENOVO dmi.bios.version: D3CN27WW dmi.board.asset.tag: No Asset Tag dmi.board.name: Lenovo Yoga 500-15ISK dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Yoga 500-15ISK dmi.modalias: dmi:bvnLENOVO:bvrD3CN27WW:bd10/28/2015:svnLENOVO:pn80R6:pvrLenovoYoga500-15ISK:rvnLENOVO:rnLenovoYoga500-15ISK:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrLenovoYoga500-15ISK: dmi.product.name: 80R6 dmi.product.version: Lenovo Yoga 500-15ISK dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.83-1~16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.4-0ubuntu1~16.04.2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.4-0ubuntu1~16.04.2 version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.7 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1.2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 xserver.bootTime: Fri Jan 12 06:14:57 2018 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 14162 vendor SDC xserver.version: 2:1.18.4-0ubuntu0.7 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1742865/+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
