[Touch-packages] [Bug 1902464] Re: The rear panel of Lenovo P620 doesn't support more than one audio device at the same time
@Seb, I'll work on these two patches comment#3 mentioned in the other bug. https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1929371 Let's leave this ticket to track https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/merge_requests/290 -- 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/1902464 Title: The rear panel of Lenovo P620 doesn't support more than one audio device at the same time Status in HWE Next: New Status in OEM Priority Project: Confirmed Status in alsa-ucm-conf package in Ubuntu: Fix Released Status in pulseaudio package in Ubuntu: New Bug description: After backporting following patches from PA and alsa-ucm-conf and then it works. https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/merge_requests/290 https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/merge_requests/354 https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/merge_requests/355 https://github.com/alsa-project/alsa-ucm-conf/tree/master/ucm2/USB- Audio [landed by aa74f4c12eefcc98582572d2fc48982cf7478b51] Here is the test PPA: https://launchpad.net/~os369510/+archive/ubuntu/oem-package-test Since the upstream not yet accepted those patches, the regression potential may quite high. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1902464/+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 1739510] Re: ill install you signature
[Expired for xorg (Ubuntu) because there has been no activity for 60 days.] ** Changed in: xorg (Ubuntu) Status: Incomplete => Expired -- 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/1739510 Title: ill install you signature Status in xorg package in Ubuntu: Expired Bug description: hope you can help me. i cant affort another computer and spain is acting violence ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.10.0-42.46~16.04.1-generic 4.10.17 Uname: Linux 4.10.0-42-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.14 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: Thu Dec 21 01:27:15 2017 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Device [8086:5916] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Device [103c:81ed] InstallationDate: Installed on 2017-12-19 (1 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 0c45:651b Microdia Bus 001 Device 003: ID 8087:0aa7 Intel Corp. Bus 001 Device 002: ID 276d:1160 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP 250 G5 Notebook PC ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-42-generic.efi.signed root=UUID=d6ad60b5-3719-45b3-8b42-1bb91b324af7 ro nopat vesafb.invalid=1 plymouth:debug drm.debug=0xe SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/20/2017 dmi.bios.vendor: Insyde dmi.bios.version: F.24 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 81ED dmi.board.vendor: HP dmi.board.version: 62.39 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.24:bd01/20/2017:svnHP:pnHP250G5NotebookPC:pvrType1ProductConfigId:rvnHP:rn81ED:rvr62.39:cvnHP:ct10:cvrChassisVersion: dmi.product.name: HP 250 G5 Notebook PC dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.76-1~ubuntu16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.7-0ubuntu0.16.04.2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.7-0ubuntu0.16.04.2 version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A xserver.bootTime: Thu Dec 21 00:06:27 2017 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.19.3-1ubuntu1~16.04.4 xserver.video_driver: modeset To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1739510/+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 1923232] Re: SRU of LXC 4.0.6 to focal (upstream bugfix release)
Hello Serge, or anyone else affected, Accepted lxc into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/lxc/1:4.0.6-0ubuntu1~20.04.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- focal to verification-done-focal. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-focal. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: lxc (Ubuntu Focal) Status: Triaged => Fix Committed ** Tags added: verification-needed verification-needed-focal -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1923232 Title: SRU of LXC 4.0.6 to focal (upstream bugfix release) Status in lxc package in Ubuntu: Fix Released Status in lxc source package in Focal: Fix Committed Bug description: LXC released 4.0.6 as a bugfix release with the following changelog: - Improve handling for compatibility architectures for seccomp - Harden seccomp notifier implementation - Rework parsing of /proc//mountinfo to handle kernel regression - Improve network device restoration - Significantly cleanup and harden config file parsing - Support new capabilities CAP_PERFORM, CAP_BPF, and CAP_CHECKPOINT_RESTORE - Harden containers started without CAP_NET_ADMIN * New upstream bugfix release (4.0.5): - Support allocating PTS devices from within the container - Harden more path/mount handling logics - Rework LSM logic to limit initializer use * Cherry-pick upstream fixes: - 0002-commands-fix-check-for-seccomp-notify-support.patch - 0003-configure-skip-libseccomp-tests-if-it-is-disabled.patch - 0004-conf-fix-containers-retaining-CAP_NET_ADMIN.patch - 0005-cgroups-fix-cgroup-mounting.patch - 0006-lsm-remove-obsolute-comment-about-constructor.patch - 0007-lxc_attach-include-rexec-conditionally.patch - 0008-tree-wide-fix-some-header-inclusions.patch - 0009-initutils-fix-missing-includes.patch - 0010-configure-support-static-binaries.patch - 0011-autotools-enable-static-builds-for-tools.patch - 0012-autotools-enable-static-builds-for-commands.patch - 0013-tree-wide-fix-compilation-with-Wstrict-prototypes-Wo.patch - 0014-config-update-ax_pthread.m4.patch - 0015-configure-add-AC_SYS_LARGEFILE-checking.patch - 0016-autotools-update-build.patch - 0017-file_utils-introduce-read_file_at.patch - 0018-string_utils-add-must_make_path_relative.patch - 0019-cgroups-coding-style-fixes.patch - 0020-cgroups-rework-cg_unified_init.patch - 0021-cgroups-detect-and-record-cgroup2-freezer-support.patch - 0022-criu-handle-cgroup2-freezer.patch - 0023-mkdir-p-proc-sys-on-container-startup.patch - 0024-conf-fix-coding-style.patch - 0025-conf-coding-style-fixes.patch - 0026-conf-move-proc-and-sys-mountpoint-creation-int-lxc_m.patch - 0027-attach-invert-child-parent-handling.patch - 0028-attach-use-__do_free-cleanup-macro-for-cwd.patch - 0029-attach-tweak-logging.patch - 0030-attach-use-__do_close-for-labelfd.patch - 0031-attach-coding-style-fixes.patch - 0032-attach-use-free_disarm.patch - 0033-attach-s-attach_child_main-do_attach-g.patch - 0034-attach-mark-do_attach-as-__noreturn.patch - 0035-attach-make-do_attach-void.patch - 0036-attach-use-close_prot_errno_disarm.patch - 0037-attach-add-some-DEBUG-logging-to-stdfd-dpulication.patch - 0038-cgroups-fix-cgroup-mounting.patch - 0039-utils-fix-mount_at.patch - 0040-configure-fix-static-builds-with-clang-12-and-LTO.patch - 0041-cgroups-bpf-fixes.patch - 0042-croups-improve-__do_bpf_program_free.patch - 0043-cgroups-coding-style-fixes.patch - 0044-cgroups-don-t-initiliaze-NULL-log.patch - 0045-cgroups-ensure-all-memory-is-zeroed.patch - 0046-cgroups-use-zalloc.patch - 0047-cgroups-tweak-cgroup-initialization.patch - 0048-log-remov
[Touch-packages] [Bug 1537047] Re: Selected button not adequately highlighted in GTK3 themes (orange highlight too thin)
Yeah, let's not get focal or Yaru involved here. If anyone has a problem with focal or Yaru they should open a new bug with a screenshot of whatever is bothering them. ** Tags removed: focal ** No longer affects: yaru-theme (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-themes in Ubuntu. https://bugs.launchpad.net/bugs/1537047 Title: Selected button not adequately highlighted in GTK3 themes (orange highlight too thin) Status in ubuntu-themes package in Ubuntu: Confirmed Bug description: With Ubuntu's GTK+ 3 Theme, the orange dotted line is so thin, it's practically invisible and the red button highlight is missing. This makes it appear that the window is not in focus and you must use the mouse to select the dialog buttons. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-themes/+bug/1537047/+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 1929456] Re: XrandR does not propose 21:9 resolution
*** This bug is a duplicate of bug 1901470 *** https://bugs.launchpad.net/bugs/1901470 I have decoded your monitor's EDID and it does show the desired resolution but only as a "Detailed mode". So that would appear to make this a duplicate of bug 1901470. EDID version: 1.3 Manufacturer: GSM Model 23025 Serial Number 10845 Made in week 9 of 2015 Digital display Maximum image size: 80 cm x 34 cm Gamma: 2.20 DPMS levels: Standby Suspend Off RGB color display First detailed timing is preferred timing Color Characteristics Red: 0.6513, 0.3320 Green: 0.3066, 0.6308 Blue: 0.1503, 0.0595 White: 0.3134, 0.3291 Established Timings I & II 720x40070.082 Hz 9:531.467 kHz 28.320 MHz (IBM) 640x48059.940 Hz 4:331.469 kHz 25.175 MHz (DMT) 640x48075.000 Hz 4:337.500 kHz 31.500 MHz (DMT) 800x60060.317 Hz 4:337.879 kHz 40.000 MHz (DMT) 800x60075.000 Hz 4:346.875 kHz 49.500 MHz (DMT) 1024x76860.004 Hz 4:348.363 kHz 65.000 MHz (DMT) 1024x76875.029 Hz 4:360.023 kHz 78.750 MHz (DMT) 1280x1024 75.025 Hz 5:479.976 kHz 135.000 MHz (DMT) 1152x87075.062 Hz 192:145 68.681 kHz 100.000 MHz (Apple) Standard Timings 1152x86475.000 Hz 4:367.500 kHz 108.000 MHz (DMT) 1280x1024 60.020 Hz 5:463.981 kHz 108.000 MHz (DMT) 1280x72060.000 Hz 16:945.000 kHz 74.250 MHz (DMT) 1600x90060.000 Hz 16:960.000 kHz 108.000 MHz (DMT, RB) 1680x1050 59.954 Hz 16:10 65.290 kHz 146.250 MHz (DMT) Detailed mode: Clock 185.580 MHz, 798 mm x 334 mm 2560 2624 2688 2784 ( 64 64 96) 1080 1083 1093 ( 3 10 18) -hsync -vsync VertFreq: 60.000 Hz, HorFreq: 66.659 kHz Detailed mode: Clock 148.500 MHz, 798 mm x 334 mm 1920 2008 2052 2200 ( 88 44 148) 1080 1084 1089 1125 ( 4 5 36) +hsync +vsync VertFreq: 60.000 Hz, HorFreq: 67.500 kHz Display Product Name: LG ULTRAWIDE Display Range Limits Monitor ranges (GTF): 56-75 Hz V, 30-90 kHz H, max dotclock 240 MHz Has 1 extension block Checksum: 0x7b CTA-861 Extension Block Revision 3 Underscans PC formats by default Basic audio support Supports YCbCr 4:4:4 Supports YCbCr 4:2:2 1 native detailed modes 25 bytes of CTA data blocks Video Data Block 1920x1080 60.000 Hz 16:967.500 kHz 148.500 MHz (VIC 16, native) 1280x72060.000 Hz 16:945.000 kHz 74.250 MHz (VIC 4) 720x48059.940 Hz 16:931.469 kHz 27.000 MHz (VIC 3) 1920x1080 30.000 Hz 16:933.750 kHz 74.250 MHz (VIC 34) 1920x1080i 50.000 Hz 16:928.125 kHz 74.250 MHz (VIC 20) 720x57650.000 Hz 16:931.250 kHz 27.000 MHz (VIC 18) 1920x1080i 60.000 Hz 16:933.750 kHz 74.250 MHz (VIC 5) 1920x1080 50.000 Hz 16:956.250 kHz 148.500 MHz (VIC 31) 640x48059.940 Hz 4:331.469 kHz 25.175 MHz (VIC 1) 1280x72050.000 Hz 16:937.500 kHz 74.250 MHz (VIC 19) Audio Data Block Linear PCM, max channels 2 Supported sample rates (kHz): 48 44.1 32 Supported sample sizes (bits): 24 20 16 Speaker Allocation Data Block Speaker map: FL/FR - Front Left/Right Vendor-Specific Data Block, OUI 0x000c03 (HDMI) Source physical address 1.0.0.0 Detailed mode: Clock 148.500 MHz, 598 mm x 337 mm 1920 2008 2052 2200 ( 88 44 148) 1080 1084 1089 1125 ( 4 5 36) +hsync +vsync VertFreq: 60.000 Hz, HorFreq: 67.500 kHz Detailed mode: Clock 74.250 MHz, 598 mm x 337 mm 1920 2008 2052 2200 ( 88 44 148) 540 542 547 562 ( 2 5 15) +hsync +vsync VertFreq: 60.000i Hz, HorFreq: 33.750 kHz Detailed mode: Clock 74.250 MHz, 598 mm x 337 mm 1280 1390 1430 1650 (110 40 220) 720 725 730 750 ( 5 5 20) +hsync +vsync VertFreq: 60.000 Hz, HorFreq: 45.000 kHz Detailed mode: Clock 27.000 MHz, 598 mm x 337 mm 720 736 798 858 ( 16 62 60) 480 489 495 525 ( 9 6 30) -hsync -vsync VertFreq: 59.940 Hz, HorFreq: 31.469 kHz Detailed mode: 00 00 00 ff 00 35 30 39 4e 54 4b 46 30 41 38 34 35 0a .509NTKF0A845. Checksum: 0x8c ** This bug has been marked a duplicate of bug 1901470 [modeset][i915] Native resolution (EDID detailed mode) of 2560x1440 or 2560x1080 not listed, defaults to 1920x1080 instead -- 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/1929456 Title: XrandR does not propose 21:9 resolution Status in xorg package in Ubuntu: Confirmed Bug description: If come here over bug 1895301 "XrandR does not propose 3440x1440 21:9 r
[Touch-packages] [Bug 1929456] Re: XrandR does not propose 21:9 resolution
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: xorg (Ubuntu) Status: New => Confirmed -- 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/1929456 Title: XrandR does not propose 21:9 resolution Status in xorg package in Ubuntu: Confirmed Bug description: If come here over bug 1895301 "XrandR does not propose 3440x1440 21:9 resolution". In bug 1895301 sombody wrote "We just need one person experiencing the bug to open a bug with the relevant system details automatically attached." - so I did. I have a similar problem with a 21:9 monitor with a resolution of 2560x1080. It's a LG 25UB55-B on a HP docking station A7E32A, DVI output with adapter to HDMI, HDMI cable and input to the monitor via HDMI. Laptop is an HP Elitebook 8440p (Intel i5-520 with Intel HD Graphics (ILK)), internal display with 1366*768 is in use as well. I had Ubuntu 18.04 LTS before until January this year, with automatic updates on, so presumably up to date. There it worked fine out of the box, i.e. since first install I had the full resolution of 21:9 in 2560x1080 on my external monitor. I didn't change any hardware, just installed Ubuntu 20.04 from DVD, an it stopped working. I got only 16:9 with 1920x1080. I've updated to Ubuntu 20.10, tried Ubuntu 21.04 (from DVD as well), changed cable and adapter, nothing helped. Did some reseach with google and found the mentioned bug 1895301. The workaround worked, I got full resolution of 2560x1080 on the external display. It is not permanent, so at the moment of filing this bug, I'm still back on the 16:9 with 1920x1080. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: xorg 1:7.7+19ubuntu15 ProcVersionSignature: Ubuntu 5.8.0-53.60-generic 5.8.18 Uname: Linux 5.8.0-53-generic x86_64 ApportVersion: 2.20.11-0ubuntu50.6 Architecture: amd64 BootLog: Error: [Errno 13] Keine Berechtigung: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME CurrentDmesg: Error: command ['pkexec', 'dmesg'] failed with exit code 126: Error executing command as another user: Request dismissed Date: Mon May 24 20:23:52 2021 DistUpgraded: 2021-05-23 15:18:23,444 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (g-exec-error-quark: Kindprozess »./xorg_fix_proprietary.py« konnte nicht ausgeführt werden (Datei oder Verzeichnis nicht gefunden) (8)) DistroCodename: groovy DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Core Processor Integrated Graphics Controller [8086:0046] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Core Processor Integrated Graphics Controller [103c:172a] InstallationDate: Installed on 2021-02-10 (103 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: Hewlett-Packard HP EliteBook 8440p ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.8.0-53-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to groovy on 2021-05-23 (1 days ago) dmi.bios.date: 09/13/2013 dmi.bios.release: 15.36 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68CCU Ver. F.24 dmi.board.name: 172A dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 30.34 dmi.chassis.asset.tag: CZC040C94D dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.ec.firmware.release: 48.52 dmi.modalias: dmi:bvnHewlett-Packard:bvr68CCUVer.F.24:bd09/13/2013:br15.36:efr48.52:svnHewlett-Packard:pnHPEliteBook8440p:pvr:rvnHewlett-Packard:rn172A:rvrKBCVersion30.34:cvnHewlett-Packard:ct10:cvr: dmi.product.family: 103C_5336AN dmi.product.name: HP EliteBook 8440p dmi.product.sku: J2544631 dmi.sys.vendor: Hewlett-Packard version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.10.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1929456/+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/
[Touch-packages] [Bug 1929475] [NEW] Bluetooth sound card conecctivity issues
Public bug reported: I have Bluetooth 5.0 device soundcore life q10, while I'm using WiFi my Headphone disconnects often and microphone doesn't listed on audio settings. connecting wired mode it works perfectly. if you need any other query I'm a happy to answer your query. And I checked some forums many people also having this issues so can you make it as soon as possible. thank you for valuable service. have a good day. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.8.0-53.60~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-53-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.17 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: saravanan 1350 F pulseaudio /dev/snd/pcmC0D0p: saravanan 1350 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue May 25 06:13:04 2021 InstallationDate: Installed on 2021-05-05 (19 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) PackageArchitecture: all ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Title: Bluetooth sound card not detected UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/23/2018 dmi.bios.release: 1.45 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.45 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: Ironman_SK dmi.board.vendor: Acer dmi.board.version: V1.45 dmi.chassis.type: 10 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 2.50 dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.45:bd07/23/2018:br1.45:efr2.50:svnAcer:pnAspireE5-575:pvrV1.45:rvnAcer:rnIronman_SK:rvrV1.45:cvnChassisManufacturer:ct10:cvrChassisVersion: dmi.product.family: SKL dmi.product.name: Aspire E5-575 dmi.product.sku: Aspire E5-575_1094_1.45 dmi.product.version: V1.45 dmi.sys.vendor: Acer ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1929475 Title: Bluetooth sound card conecctivity issues Status in alsa-driver package in Ubuntu: New Bug description: I have Bluetooth 5.0 device soundcore life q10, while I'm using WiFi my Headphone disconnects often and microphone doesn't listed on audio settings. connecting wired mode it works perfectly. if you need any other query I'm a happy to answer your query. And I checked some forums many people also having this issues so can you make it as soon as possible. thank you for valuable service. have a good day. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.8.0-53.60~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-53-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.17 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: saravanan 1350 F pulseaudio /dev/snd/pcmC0D0p: saravanan 1350 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue May 25 06:13:04 2021 InstallationDate: Installed on 2021-05-05 (19 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) PackageArchitecture: all ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Title: Bluetooth sound card not detected UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/23/2018 dmi.bios.release: 1.45 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.45 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: Ironman_SK dmi.board.vendor: Acer dmi.board.version: V1.45 dmi.chassis.type: 10 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 2.50 dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.45:bd07/23/2018:br1.45:efr2.50:svnAcer:pnAspireE5-575:pvrV1.45:rvnAcer:rnIronman_SK:rvrV1.45:cvnChassisManufacturer:ct10:cvrChassisVersion: dmi.product.family: SKL dmi.product.name: Aspire E5-575 dmi.product.sku: Aspire E5-575_1094_1.45 dmi.product.version: V1.45 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1929475/+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
Re: [Touch-packages] [Bug 1898026] Re: interruption of dist-upgrade can leave you next release in sources.list
On Mon, May 24, 2021, 8:20 AM Launchpad Bug Tracker <
1898...@bugs.launchpad.net> wrote:
> This bug was fixed in the package ubuntu-release-upgrader - 1:20.04.33
>
> ---
> ubuntu-release-upgrader (1:20.04.33) focal; urgency=medium
>
> * DistUpgrade/DistUpgradeController.py: restore sources.list where
> possible
> if a KeyboardInterrupt event is received and redirect the output of
> gnome-session-inhibit to devnull so a message regarding Ctrl-C is not
> displayed. (LP: #1898026)
> * DistUpgrade/DistUpgradeQuirks.py: Restore code which ensured the python
> package was maked for removal. (LP: #1928397)
> * Update mirrors and translations.
>
> -- Brian Murray Thu, 13 May 2021 16:38:41 -0700
>
> ** Changed in: ubuntu-release-upgrader (Ubuntu Focal)
>Status: Fix Committed => Fix Released
>
> --
> You received this bug notification because you are subscribed to apt in
> Ubuntu.
> Matching subscriptions: dragonhahney
> https://bugs.launchpad.net/bugs/1898026
>
> Title:
> interruption of dist-upgrade can leave you next release in
> sources.list
>
> Status in apt package in Ubuntu:
> Fix Released
> Status in ubuntu-release-upgrader package in Ubuntu:
> Fix Released
> Status in apt source package in Bionic:
> New
> Status in ubuntu-release-upgrader source package in Bionic:
> New
> Status in apt source package in Focal:
> New
> Status in ubuntu-release-upgrader source package in Focal:
> Fix Released
> Status in apt source package in Groovy:
> Fix Released
> Status in ubuntu-release-upgrader source package in Groovy:
> Fix Committed
> Status in apt source package in Hirsute:
> Fix Released
> Status in ubuntu-release-upgrader source package in Hirsute:
> Fix Released
>
> Bug description:
> [Impact]
> Calling update() or installing packages from apt clients resets their
> SIGINT and SIGQUIT handlers to SIG_DFL, overriding any signal handlers they
> might have set for them.
>
> In case of ubuntu-release-upgrader, this results in the release
> upgrader being unable to handle interrupts after it did the initial
> update - the default libc handler will run and the program exits.
>
> [Test plan]
>
> [[apt]]
> As a standalone test for apt, we can test the following script:
>
> import apt
> import time
>
> apt.Cache().update()
> print("WAITING")
> try:
> time.sleep(1)
> except BaseException as e:
> print("Seen", repr(e))
> print("END")
>
> Pressing Ctrl+C while WAITING is printed should print Seen
> KeyboardInterrupt, and importantly, also the END line.
>
> [[ubuntu-release-upgrader]]
> 1) On an Ubuntu 18.04 system run do-release-upgrade in a terminal.
> 2) At the "Do you want to start the upgrade?" question say Y.
> 3) When you see the "Lock screen disabled" message you will also see
> "Inhibiting until Ctrl+C is pressed".
> 4) Press "Ctrl+C"
>
> Your /etc/apt/sources.list file will now have focal in it instead of
> bionic although the upgrade has quit. With the version of ubuntu-
> release-upgrader in -proposed you will not see the "Ctrl+C" message.
> For your sources.list file to be restored you'll need the version of
> apt from bionic-proposed installed before starting the upgrade.
>
> [Where problems could occur]
> apt: This specific change removes the two lines that SIG_DFL the signal
> handlers after running scripts. AFAWCT those lines are unnecessary - the
> code that calls it temporarily sets the handlers to SIG_IGN but restores
> previous handlers at the end; it was wrongly refactored decades ago. A
> regression could occur in that those signals will now continue to be
> ignored if we missed a spot.
>
> ubuntu-release-upgrader: The change is wrapping a bunch of code in a
> try: except: block so if the indentation was off the pyflakes /
> pycodestyle tests would fail but autopkgtest will catch that.
>
> [Original bug report]
> As a long-time-user of ?ubuntu, with apt-get as tool of choice for
> updates/upgrades I wrote a daily script for updates, with 'dist-upgrade'.
> In all earlier years, it wouldn't actually do an upgrade of a ?ubuntu
> version; just all packages including new ones. Version updates had to be
> initiated manually, and I was always asked if I really wanted the new
> ?ubuntu version. Sounds appropriate.
>
> Last night when it (dist-upgrade), it just gave me 20.04. No questions
> asked. I for one consider this kind of intrusive, though.
> It *might* have to make with me trying 'sudo do-release-upgrade -m
> desktop' a number of times earlier; just to *check* if the upgrade was on
> offer; but this is only a guess.
>
> In *any* case, a pop-up asking "Are you sure? Are you connected
> through an adequate pipe? Are you sitting with full batteries; better
> a power supply?" would be convenient; since I am using my PC for
> urgent duties, and didn't want to fiddle with unexpected upgrade bugs.
>
> ProblemType: BugDistroRelease: Ubuntu 20.04
[Touch-packages] [Bug 1929110] Re: Please merge sudo 1.9.5p2-3 (main) from Debian unstable (main) Edit
This corrected patch accounts for the apport-hooks now being present in Debian. ** Patch added: "Diff from Debian" https://bugs.launchpad.net/ubuntu/+source/sudo/+bug/1929110/+attachment/5500040/+files/sudo-debian-ubuntu.debdiff -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to sudo in Ubuntu. https://bugs.launchpad.net/bugs/1929110 Title: Please merge sudo 1.9.5p2-3 (main) from Debian unstable (main) Edit Status in sudo package in Ubuntu: Confirmed Bug description: This requires a merge because there are changes in the Ubuntu version not present in the Debian version. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sudo/+bug/1929110/+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 1929110] Re: Please merge sudo 1.9.5p2-3 (main) from Debian unstable (main) Edit
This corrected patch accounts for the apport-hooks now being present in Debian. ** Patch added: "Diff from 1.9.5p2-2ubuntu3" https://bugs.launchpad.net/ubuntu/+source/sudo/+bug/1929110/+attachment/5500041/+files/sudo-ubuntu-ubuntu.debdiff -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to sudo in Ubuntu. https://bugs.launchpad.net/bugs/1929110 Title: Please merge sudo 1.9.5p2-3 (main) from Debian unstable (main) Edit Status in sudo package in Ubuntu: Confirmed Bug description: This requires a merge because there are changes in the Ubuntu version not present in the Debian version. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sudo/+bug/1929110/+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 1926265] Re: slapd enter in infinite loop on sched_yield syscall
If I understand the work so far, this issue is only present in Bionic,
since later releases already have the release (and the subsequent fix)?
Sounds like the next action here would be to SRU the changes packaged in
https://launchpad.net/~sergiodj/+archive/ubuntu/openldap-
bug1926265/+packages. A possible catch though is that the SRU process
dislikes introducing known regressions, and it sounds like this revert
patch would do so. So it may be worth discussing this with an SRU
administrator first. If introducing the regression is a no-go, then
that means a bionic-specific fix would need developed based on
https://github.com/openldap/openldap/commit/735e1ab14bb055344b4e767a216aa410aa7d1503.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openldap in Ubuntu.
https://bugs.launchpad.net/bugs/1926265
Title:
slapd enter in infinite loop on sched_yield syscall
Status in openldap package in Ubuntu:
Confirmed
Status in openldap source package in Bionic:
Triaged
Bug description:
On a production server, sometimes slapd become unbresponsive, some threads
loops in sched_yield syscall and consumme all CPU.
To recover, slapd needs to restart.
No related information is reported in log file.
All same issues in OpenLDAP upstream project are old and fixed.
So maybe this issue affects only Ubuntu package.
It occurs randomly, so I have no steps to reproduce.
OS : Bionic
Openldap version:
libldap-2.4-2:amd642.4.45+dfsg-1ubuntu1.10
libldap-common 2.4.45+dfsg-1ubuntu1.10
slapd 2.4.45+dfsg-1ubuntu1.10
Modules loaded:
olcModuleLoad: {0}back_bdb
olcModuleLoad: {1}syncprov
olcModuleLoad: {2}back_monitor
olcModuleLoad: {3}memberof.la
olcModuleLoad: {4}refint.la
olcModuleLoad: {5}rwm
olcModuleload: {6}back_ldap
Backend is BDB. slapd run in (single) master - (multi) slave mode.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openldap/+bug/1926265/+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 1926265] Re: slapd enter in infinite loop on sched_yield syscall
** Also affects: openldap (Ubuntu Bionic)
Importance: Undecided
Status: New
** Changed in: openldap (Ubuntu Bionic)
Status: New => Triaged
** Changed in: openldap (Ubuntu Bionic)
Importance: Undecided => High
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openldap in Ubuntu.
https://bugs.launchpad.net/bugs/1926265
Title:
slapd enter in infinite loop on sched_yield syscall
Status in openldap package in Ubuntu:
Confirmed
Status in openldap source package in Bionic:
Triaged
Bug description:
On a production server, sometimes slapd become unbresponsive, some threads
loops in sched_yield syscall and consumme all CPU.
To recover, slapd needs to restart.
No related information is reported in log file.
All same issues in OpenLDAP upstream project are old and fixed.
So maybe this issue affects only Ubuntu package.
It occurs randomly, so I have no steps to reproduce.
OS : Bionic
Openldap version:
libldap-2.4-2:amd642.4.45+dfsg-1ubuntu1.10
libldap-common 2.4.45+dfsg-1ubuntu1.10
slapd 2.4.45+dfsg-1ubuntu1.10
Modules loaded:
olcModuleLoad: {0}back_bdb
olcModuleLoad: {1}syncprov
olcModuleLoad: {2}back_monitor
olcModuleLoad: {3}memberof.la
olcModuleLoad: {4}refint.la
olcModuleLoad: {5}rwm
olcModuleload: {6}back_ldap
Backend is BDB. slapd run in (single) master - (multi) slave mode.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openldap/+bug/1926265/+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 1929110] Re: Please merge sudo 1.9.5p2-3 (main) from Debian unstable (main) Edit
This looks mostly ok but the merge doesn't seem to account for the apport hooks being in debian now -- the changelog still lists it as a difference, the package-hooks dir is in the .dirs files twice, and I think they might be installed twice. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to sudo in Ubuntu. https://bugs.launchpad.net/bugs/1929110 Title: Please merge sudo 1.9.5p2-3 (main) from Debian unstable (main) Edit Status in sudo package in Ubuntu: Confirmed Bug description: This requires a merge because there are changes in the Ubuntu version not present in the Debian version. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sudo/+bug/1929110/+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 1537047] Re: Selected button not adequately highlighted in GTK3 themes (orange highlight too thin)
This bug is from 2016 at this time yaru was not yet existing. What is this bug about? Ambiance? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-themes in Ubuntu. https://bugs.launchpad.net/bugs/1537047 Title: Selected button not adequately highlighted in GTK3 themes (orange highlight too thin) Status in ubuntu-themes package in Ubuntu: Confirmed Status in yaru-theme package in Ubuntu: Incomplete Bug description: With Ubuntu's GTK+ 3 Theme, the orange dotted line is so thin, it's practically invisible and the red button highlight is missing. This makes it appear that the window is not in focus and you must use the mouse to select the dialog buttons. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-themes/+bug/1537047/+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 1926547] Re: Add Dell Privacy Mic Mute Key mapping
> Is Groovy also need to apply this change yes, the SRU process does require all changes to be applied in all affected releases, or at least all newer affected releases (meaning, if we want to patch focal, we have to patch groovy and hirsute too). -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1926547 Title: Add Dell Privacy Mic Mute Key mapping Status in OEM Priority Project: New Status in OEM Priority Project focal series: New Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Focal: In Progress Status in systemd source package in Groovy: In Progress Status in systemd source package in Hirsute: In Progress Bug description: [Impact] * Dell introduces new function called Dell Privacy, it utilizes hardware mute to control audio and camera. The commit map the reported key event to mic mute for making userspace can work as before, "Mic Mute" dialog pop-up while the mic mute button is pressed. [Test Plan] * Use a Dell machine, which has Dell privacy function, and press mic mute key. GUI will pop up "Mic Mute" icon. [Where problems could occur] * This change adds key event mapping in hwdb, which won't impact other hardware. any regression would likely cause problems with key(s) from the specific dell kb matching the modified listing in the hw db. [Other Info] * The change can only work with kernel commit on some specific hardware, ex. Latitude 9520. The commit series is "hardware-privacy-implementation-for-dell-laptop" in alsa-devel kernel tree. https://patchwork.kernel.org/project/alsa-devel/list/?series=465445 * This change has been verified on Dell machine. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1926547/+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 1928360] Re: Switch to Fcitx 5 for Chinese
Gunnar, indeed, it had much less in it than I expected; I don't know much about the snap packaging for Chromium, but it looked to me like it was trying to do bluetooth things and that's all that was denied. I'm no fcitx expert but I didn't think it looked related. Thanks -- 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/1928360 Title: Switch to Fcitx 5 for Chinese Status in Lubuntu default settings: New Status in Ubuntu Kylin: In Progress Status in apparmor package in Ubuntu: New Status in language-selector package in Ubuntu: Fix Released Bug description: In Debian 11 Fcitx 5 will be the default IM framework for Chinese on non-GNOME desktops. I can think it's time to make the equivalent changes in Ubuntu 21.10 as well. I'd appreciate input on the topic from the Ubuntu Kylin team as well as other Chinese speaking users. To manage notifications about this bug go to: https://bugs.launchpad.net/lubuntu-default-settings/+bug/1928360/+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 1929456] Re: XrandR does not propose 21:9 resolution
As I said, the workaround worked. To help others looking for a solution and finding this bug, I will show it here for my configuration: 1.) Open a terminal 2.) Call xrandr to see, how your desired device is called. In my case, it's called "HDMI-1". If you have more than one, you may guess, but output should by clear enough. 3.) Call cvt with desired resolution and frequency. In my case it must be 2560x1080 with 30 (Hz), If you are unsure you have to try (I tried 60 Hz first - didn't work in the last step no. 6): cvt 2560 1080 30 Output in my case is # 2560x1080 29.97 Hz (CVT) hsync: 33.03 kHz; pclk: 106.75 MHz Modeline "2560x1080_30.00" 106.75 2560 2640 2896 3232 1080 1083 1093 1102 -hsync +vsync 4.) Call xrandr to set new mode, copy everything after "Modeline": xrandr --newmode "2560x1080_30.00" 106.75 2560 2640 2896 3232 1080 1083 1093 1102 -hsync +vsync (The name in quotation marks could be changed, but no need to do so.) 5.) Call xrandr to add this mode by it's name to your desired device: xrandr --addmode HDMI-1 2560x1080_30.00 6.) Call xrandr to set your desired device (here. HDMI-1) to the mode xrandr --output HDMI-1 --mode 2560x1080_30.00 Instead of step 6 via terminal you could use the GUI to change the resolution, it should be there now. Hope this may help somebody. It is not persistent. I made a script and added it to autostart. There may be other ways, maybe a config file for xrandr? -- 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/1929456 Title: XrandR does not propose 21:9 resolution Status in xorg package in Ubuntu: New Bug description: If come here over bug 1895301 "XrandR does not propose 3440x1440 21:9 resolution". In bug 1895301 sombody wrote "We just need one person experiencing the bug to open a bug with the relevant system details automatically attached." - so I did. I have a similar problem with a 21:9 monitor with a resolution of 2560x1080. It's a LG 25UB55-B on a HP docking station A7E32A, DVI output with adapter to HDMI, HDMI cable and input to the monitor via HDMI. Laptop is an HP Elitebook 8440p (Intel i5-520 with Intel HD Graphics (ILK)), internal display with 1366*768 is in use as well. I had Ubuntu 18.04 LTS before until January this year, with automatic updates on, so presumably up to date. There it worked fine out of the box, i.e. since first install I had the full resolution of 21:9 in 2560x1080 on my external monitor. I didn't change any hardware, just installed Ubuntu 20.04 from DVD, an it stopped working. I got only 16:9 with 1920x1080. I've updated to Ubuntu 20.10, tried Ubuntu 21.04 (from DVD as well), changed cable and adapter, nothing helped. Did some reseach with google and found the mentioned bug 1895301. The workaround worked, I got full resolution of 2560x1080 on the external display. It is not permanent, so at the moment of filing this bug, I'm still back on the 16:9 with 1920x1080. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: xorg 1:7.7+19ubuntu15 ProcVersionSignature: Ubuntu 5.8.0-53.60-generic 5.8.18 Uname: Linux 5.8.0-53-generic x86_64 ApportVersion: 2.20.11-0ubuntu50.6 Architecture: amd64 BootLog: Error: [Errno 13] Keine Berechtigung: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME CurrentDmesg: Error: command ['pkexec', 'dmesg'] failed with exit code 126: Error executing command as another user: Request dismissed Date: Mon May 24 20:23:52 2021 DistUpgraded: 2021-05-23 15:18:23,444 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (g-exec-error-quark: Kindprozess »./xorg_fix_proprietary.py« konnte nicht ausgeführt werden (Datei oder Verzeichnis nicht gefunden) (8)) DistroCodename: groovy DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Core Processor Integrated Graphics Controller [8086:0046] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Core Processor Integrated Graphics Controller [103c:172a] InstallationDate: Installed on 2021-02-10 (103 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: Hewlett-Packard HP EliteBook 8440p ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.8.0-53-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to groovy on 2021-05-23 (1 days ago) dmi.bios.date: 09/13/2013 dmi.bios.release: 15.36 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68CCU Ver. F.24 dmi.board.name: 172A dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 30.34 dmi.chassis.asset.tag: CZC040C94D dm
[Touch-packages] [Bug 1918044] Re: (Update libgweather to 3.36.2) Weather forecast and info is not available anymore
** Description changed: + [Impact] + The weather forecast is not available since one week now. Also, the weather info is gone from gnome-shell. The weather service provider retired their old API. https://developer.yr.no/news/important-changes-to-locationforecast-and-nowcast/ - https://developer.yr.no/doc/guides/getting-started-from-forecast-xml/ + + https://gitlab.gnome.org/GNOME/libgweather/-/blob/gnome-3-36/NEWS + + == + Version 3.36.2 + == + + This version switches the yr.no backend to use met.no instead. Please note + that this backport is only meant as a compatibility layer. Where at all + possible, the newer libgweather 40 should be used as applications cannot + fully comply with the met.no ToS otherwise. + + + [Test case] + + - gnome-weather shows the weather forecast + - gnome-shell shows the weather forecast in the calendar menu + + + [Regression potential] + + - Weather forecast is totally broken now and can't be more broken. + ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: libgweather-3-16 3.36.1-1~ubuntu20.04.1 ProcVersionSignature: Ubuntu 5.8.0-44.50~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-44-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Mar 7 09:54:52 2021 InstallationDate: Installed on 2020-04-26 (314 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: libgweather UpgradeStatus: No upgrade log present (probably fresh install) -- 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/1918044 Title: (Update libgweather to 3.36.2) Weather forecast and info is not available anymore Status in libgweather: Unknown Status in gnome-weather package in Ubuntu: Confirmed Status in libgweather package in Ubuntu: Confirmed Status in gnome-weather package in Fedora: New Bug description: [Impact] The weather forecast is not available since one week now. Also, the weather info is gone from gnome-shell. The weather service provider retired their old API. https://developer.yr.no/news/important-changes-to-locationforecast-and-nowcast/ https://gitlab.gnome.org/GNOME/libgweather/-/blob/gnome-3-36/NEWS == Version 3.36.2 == This version switches the yr.no backend to use met.no instead. Please note that this backport is only meant as a compatibility layer. Where at all possible, the newer libgweather 40 should be used as applications cannot fully comply with the met.no ToS otherwise. [Test case] - gnome-weather shows the weather forecast - gnome-shell shows the weather forecast in the calendar menu [Regression potential] - Weather forecast is totally broken now and can't be more broken. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: libgweather-3-16 3.36.1-1~ubuntu20.04.1 ProcVersionSignature: Ubuntu 5.8.0-44.50~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-44-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Mar 7 09:54:52 2021 InstallationDate: Installed on 2020-04-26 (314 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: libgweather UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/libgweather/+bug/1918044/+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 1929456] [NEW] XrandR does not propose 21:9 resolution
Public bug reported: If come here over bug 1895301 "XrandR does not propose 3440x1440 21:9 resolution". In bug 1895301 sombody wrote "We just need one person experiencing the bug to open a bug with the relevant system details automatically attached." - so I did. I have a similar problem with a 21:9 monitor with a resolution of 2560x1080. It's a LG 25UB55-B on a HP docking station A7E32A, DVI output with adapter to HDMI, HDMI cable and input to the monitor via HDMI. Laptop is an HP Elitebook 8440p (Intel i5-520 with Intel HD Graphics (ILK)), internal display with 1366*768 is in use as well. I had Ubuntu 18.04 LTS before until January this year, with automatic updates on, so presumably up to date. There it worked fine out of the box, i.e. since first install I had the full resolution of 21:9 in 2560x1080 on my external monitor. I didn't change any hardware, just installed Ubuntu 20.04 from DVD, an it stopped working. I got only 16:9 with 1920x1080. I've updated to Ubuntu 20.10, tried Ubuntu 21.04 (from DVD as well), changed cable and adapter, nothing helped. Did some reseach with google and found the mentioned bug 1895301. The workaround worked, I got full resolution of 2560x1080 on the external display. It is not permanent, so at the moment of filing this bug, I'm still back on the 16:9 with 1920x1080. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: xorg 1:7.7+19ubuntu15 ProcVersionSignature: Ubuntu 5.8.0-53.60-generic 5.8.18 Uname: Linux 5.8.0-53-generic x86_64 ApportVersion: 2.20.11-0ubuntu50.6 Architecture: amd64 BootLog: Error: [Errno 13] Keine Berechtigung: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME CurrentDmesg: Error: command ['pkexec', 'dmesg'] failed with exit code 126: Error executing command as another user: Request dismissed Date: Mon May 24 20:23:52 2021 DistUpgraded: 2021-05-23 15:18:23,444 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (g-exec-error-quark: Kindprozess »./xorg_fix_proprietary.py« konnte nicht ausgeführt werden (Datei oder Verzeichnis nicht gefunden) (8)) DistroCodename: groovy DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Core Processor Integrated Graphics Controller [8086:0046] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Core Processor Integrated Graphics Controller [103c:172a] InstallationDate: Installed on 2021-02-10 (103 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: Hewlett-Packard HP EliteBook 8440p ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.8.0-53-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to groovy on 2021-05-23 (1 days ago) dmi.bios.date: 09/13/2013 dmi.bios.release: 15.36 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68CCU Ver. F.24 dmi.board.name: 172A dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 30.34 dmi.chassis.asset.tag: CZC040C94D dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.ec.firmware.release: 48.52 dmi.modalias: dmi:bvnHewlett-Packard:bvr68CCUVer.F.24:bd09/13/2013:br15.36:efr48.52:svnHewlett-Packard:pnHPEliteBook8440p:pvr:rvnHewlett-Packard:rn172A:rvrKBCVersion30.34:cvnHewlett-Packard:ct10:cvr: dmi.product.family: 103C_5336AN dmi.product.name: HP EliteBook 8440p dmi.product.sku: J2544631 dmi.sys.vendor: Hewlett-Packard version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.10.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-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 groovy third-party-packages 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/1929456 Title: XrandR does not propose 21:9 resolution Status in xorg package in Ubuntu: New Bug description: If come here over bug 1895301 "XrandR does not propose 3440x1440 21:9 resolution". In bug 1895301 sombody wrote "We just need one person experiencing the bug to open a bug with the relevant system details automatically attached." - so I did. I have a similar problem with a 21:9 monitor with a resolution of 2560x1080. It's a LG 25UB55-B on a HP docking station A7E32A, DVI output with adapter to HDMI, HDMI cable and input to the m
[Touch-packages] [Bug 1918044] Re: (Update libgweather to 3.36.2) Weather forecast and info is not available anymore
** Summary changed: - Weather forecast and info is not available any more + (Update libgweather to 3.36.2) Weather forecast and info is not available anymore -- 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/1918044 Title: (Update libgweather to 3.36.2) Weather forecast and info is not available anymore Status in libgweather: Unknown Status in gnome-weather package in Ubuntu: Confirmed Status in libgweather package in Ubuntu: Confirmed Status in gnome-weather package in Fedora: New Bug description: The weather forecast is not available since one week now. Also, the weather info is gone from gnome-shell. The weather service provider retired their old API. https://developer.yr.no/news/important-changes-to-locationforecast-and-nowcast/ https://developer.yr.no/doc/guides/getting-started-from-forecast-xml/ ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: libgweather-3-16 3.36.1-1~ubuntu20.04.1 ProcVersionSignature: Ubuntu 5.8.0-44.50~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-44-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Mar 7 09:54:52 2021 InstallationDate: Installed on 2020-04-26 (314 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: libgweather UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/libgweather/+bug/1918044/+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 1929125] Re: lib32z1 cannot be installed on ubuntu 20.04 LTS
*** This bug is a duplicate of bug 1926918 *** https://bugs.launchpad.net/bugs/1926918 >My mind somehow converted 2.33 into 2.3.3 No problem. I had to double check the numbers, so I can see why you came to that conclusion :) > libc6-i386 : Depends: libc6 (= 2.31-0ubuntu9.2) but 2.31-0ubuntu9.3 is to be installed Ok, so this explains things. This is a known issue, already reported as bug 1926918. The short version is that 2.31-0ubuntu9.3 was released as an upgrade, but some regresions were discovered so the upgrade was removed again. In the meantime, people who installed it before it was removed might run into issues when attempting to install new libc* packages because the versions doesn't matched with what is already installed. While I haven't tried it myself, the other bug report also suggests manually installing/going back to version 2.31-0ubuntu9.2. I would check the output of the command before running it in case it affects (or tries to remove) other packages, though that sounds unlikely as it is undoing an upgrade which no longer exists to go back to the previous version. ** This bug has been marked a duplicate of bug 1926918 cannot install libc6-dev, requires old libc6 version -- 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/1929125 Title: lib32z1 cannot be installed on ubuntu 20.04 LTS Status in zlib package in Ubuntu: Confirmed Bug description: I am using Ubuntu 20.04 LTS. When trying to install lib32z1, I get the following error: The following packages have unmet dependencies: lib32z1 : Depends: libc6-i386 (>= 2.4) but it is not going to be installed E: Unable to correct problems, you have held broken packages. lib32z1 (https://packages.ubuntu.com/focal/lib32z1) depends on libc6-i386 (>= 2.4) but the latest version of libc6-i386 I can find for Ubuntu is 2.33 (https://packages.ubuntu.com/impish/libc6-i386) Is it possible Ubuntu is asking for a version of a dependency so high that it doesn't even exist? The reason I'm installing a 32-bit package is it's required for Android Studio installation process: https://developer.android.com/studio/install#linux --- apt-cache policy libc6-i386 libc6-i386: Installed: (none) Candidate: 2.31-0ubuntu9.2 Version table: 2.31-0ubuntu9.2 500 500 http://ca.archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 2.31-0ubuntu9 500 500 http://ca.archive.ubuntu.com/ubuntu focal/main amd64 Packages apt-cache policy lib32z1 lib32z1: Installed: (none) Candidate: 1:1.2.11.dfsg-2ubuntu1.2 Version table: 1:1.2.11.dfsg-2ubuntu1.2 500 500 http://ca.archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 1:1.2.11.dfsg-2ubuntu1 500 500 http://ca.archive.ubuntu.com/ubuntu focal/main amd64 Packages lsb_release -rd Description: Ubuntu 20.04.2 LTS Release: 20.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zlib/+bug/1929125/+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 1309535] Re: Running without pam-kwallet installed issues a warning in auth.log
The correct way to fix this issue is not to comment out the lines mentioning kwallet, but to make the modules silent by prepending a '-' (dash) to each line. Example: # /etc/pam.d/lightdm -authoptionalpam_kwallet.so -authoptionalpam_kwallet5.so -session optionalpam_kwallet.so auto_start -session optionalpam_kwallet5.so auto_start Same in /etc/pam.d/lightdm-greeter. This feature is mentioned in the pam.conf(5) manpage: If the type value from the list above is prepended with a - character the PAM library will not log to the system log if it is not possible to load the module because it is missing in the system. This can be useful especially for modules which are not always installed on the system and are not required for correct authentication and authorization of the login session. -- 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/1309535 Title: Running without pam-kwallet installed issues a warning in auth.log Status in lightdm package in Ubuntu: Won't Fix Status in pam package in Ubuntu: Won't Fix Bug description: After upgrading to lightdm 1.10.0-0ubuntu2 I started to see this error in auth.log: Apr 10 14:34:54 simon-laptop lightdm: PAM unable to dlopen(pam_kwallet.so): /lib/security/pam_kwallet.so: cannot open shared object file: No such file or directory Apr 10 14:34:54 simon-laptop lightdm: PAM adding faulty module: pam_kwallet.so This seems like a regression because with lightdm 1.10.0-0ubuntu1 or before I didn't have this error showing. FYI, I don't have the pam- kwallet package installed. $ lsb_release -rd Description: Ubuntu 14.04 LTS Release: 14.04 $ apt-cache policy lightdm pam-kwallet lightdm: Installed: 1.10.0-0ubuntu3 Candidate: 1.10.0-0ubuntu3 Version table: *** 1.10.0-0ubuntu3 0 500 http://archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: lightdm 1.10.0-0ubuntu3 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 CurrentDesktop: Unity Date: Fri Apr 18 09:12:37 2014 InstallationDate: Installed on 2014-01-26 (81 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140124) SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1309535/+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 1926165] Re: Bass speakers not enabled on Lenovo Yoga 9i
@Hui Wang, the alsa-info.txt for Yoga C930 is here http://alsa-project.org/db/?f=1ffb1551a46965865ee272cef105769e879397c7 -- 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/1926165 Title: Bass speakers not enabled on Lenovo Yoga 9i Status in alsa-driver package in Ubuntu: Confirmed Bug description: The Lenovo Yoga 9i has two sets of speakers: regular ones and bass speakers. The former work but while latter are detected and show up in alsamixer, they play no sound. Plugging headphones in and out or toggling any of the volume options does not fix the issue. A possibly related issue for a different Yoga version: https://bugzilla.kernel.org/show_bug.cgi?id=205755 ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: alsa-base 1.0.25+dfsg-0ubuntu7 ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 Uname: Linux 5.11.0-16-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 4466 F pulseaudio ubuntu 6219 F alsamixer /dev/snd/pcmC0D0p: ubuntu 4466 F...m pulseaudio CasperMD5CheckResult: pass CasperVersion: 1.461 CurrentDesktop: ubuntu:GNOME Date: Mon Apr 26 15:10:05 2021 LiveMediaBuild: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:sofhdadsp successful Symptom_Card: Tiger Lake-LP Smart Sound Technology Audio Controller - sof-hda-dsp Symptom_Jack: Speaker, Internal Symptom_PulsePlaybackTest: PulseAudio playback test successful Symptom_Type: None of the above Title: [82BG, Realtek ALC287, Speaker, Internal] Playback problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/28/2021 dmi.bios.release: 1.40 dmi.bios.vendor: LENOVO dmi.bios.version: EHCN40WW dmi.board.asset.tag: No Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697WIN dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: LENOVO dmi.chassis.version: Yoga 9 14ITL5 dmi.ec.firmware.release: 1.40 dmi.modalias: dmi:bvnLENOVO:bvrEHCN40WW:bd01/28/2021:br1.40:efr1.40:svnLENOVO:pn82BG:pvrYoga914ITL5:rvnLENOVO:rnLNVNB161216:rvrSDK0J40697WIN:cvnLENOVO:ct31:cvrYoga914ITL5: dmi.product.family: Yoga 9 14ITL5 dmi.product.name: 82BG dmi.product.sku: LENOVO_MT_82BG_BU_idea_FM_Yoga 9 14ITL5 dmi.product.version: Yoga 9 14ITL5 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1926165/+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 1918044] Re: Weather forecast and info is not available any more
"libgweather 3.36.2 is published" Seems this is fixed in the latest 3.36 release https://gitlab.gnome.org/GNOME/libgweather/-/blob/a18ae04879704e65c0ac858cbbfa451a22e8745c/NEWS -- 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/1918044 Title: Weather forecast and info is not available any more Status in libgweather: Unknown Status in gnome-weather package in Ubuntu: Confirmed Status in libgweather package in Ubuntu: Confirmed Status in gnome-weather package in Fedora: New Bug description: The weather forecast is not available since one week now. Also, the weather info is gone from gnome-shell. The weather service provider retired their old API. https://developer.yr.no/news/important-changes-to-locationforecast-and-nowcast/ https://developer.yr.no/doc/guides/getting-started-from-forecast-xml/ ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: libgweather-3-16 3.36.1-1~ubuntu20.04.1 ProcVersionSignature: Ubuntu 5.8.0-44.50~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-44-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Mar 7 09:54:52 2021 InstallationDate: Installed on 2020-04-26 (314 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: libgweather UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/libgweather/+bug/1918044/+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 1898026] Re: interruption of dist-upgrade can leave you next release in sources.list
This bug was fixed in the package ubuntu-release-upgrader - 1:20.04.33
---
ubuntu-release-upgrader (1:20.04.33) focal; urgency=medium
* DistUpgrade/DistUpgradeController.py: restore sources.list where possible
if a KeyboardInterrupt event is received and redirect the output of
gnome-session-inhibit to devnull so a message regarding Ctrl-C is not
displayed. (LP: #1898026)
* DistUpgrade/DistUpgradeQuirks.py: Restore code which ensured the python
package was maked for removal. (LP: #1928397)
* Update mirrors and translations.
-- Brian Murray Thu, 13 May 2021 16:38:41 -0700
** Changed in: ubuntu-release-upgrader (Ubuntu Focal)
Status: Fix Committed => Fix Released
--
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/1898026
Title:
interruption of dist-upgrade can leave you next release in
sources.list
Status in apt package in Ubuntu:
Fix Released
Status in ubuntu-release-upgrader package in Ubuntu:
Fix Released
Status in apt source package in Bionic:
New
Status in ubuntu-release-upgrader source package in Bionic:
New
Status in apt source package in Focal:
New
Status in ubuntu-release-upgrader source package in Focal:
Fix Released
Status in apt source package in Groovy:
Fix Released
Status in ubuntu-release-upgrader source package in Groovy:
Fix Committed
Status in apt source package in Hirsute:
Fix Released
Status in ubuntu-release-upgrader source package in Hirsute:
Fix Released
Bug description:
[Impact]
Calling update() or installing packages from apt clients resets their SIGINT
and SIGQUIT handlers to SIG_DFL, overriding any signal handlers they might have
set for them.
In case of ubuntu-release-upgrader, this results in the release
upgrader being unable to handle interrupts after it did the initial
update - the default libc handler will run and the program exits.
[Test plan]
[[apt]]
As a standalone test for apt, we can test the following script:
import apt
import time
apt.Cache().update()
print("WAITING")
try:
time.sleep(1)
except BaseException as e:
print("Seen", repr(e))
print("END")
Pressing Ctrl+C while WAITING is printed should print Seen
KeyboardInterrupt, and importantly, also the END line.
[[ubuntu-release-upgrader]]
1) On an Ubuntu 18.04 system run do-release-upgrade in a terminal.
2) At the "Do you want to start the upgrade?" question say Y.
3) When you see the "Lock screen disabled" message you will also see
"Inhibiting until Ctrl+C is pressed".
4) Press "Ctrl+C"
Your /etc/apt/sources.list file will now have focal in it instead of
bionic although the upgrade has quit. With the version of ubuntu-
release-upgrader in -proposed you will not see the "Ctrl+C" message.
For your sources.list file to be restored you'll need the version of
apt from bionic-proposed installed before starting the upgrade.
[Where problems could occur]
apt: This specific change removes the two lines that SIG_DFL the signal
handlers after running scripts. AFAWCT those lines are unnecessary - the code
that calls it temporarily sets the handlers to SIG_IGN but restores previous
handlers at the end; it was wrongly refactored decades ago. A regression could
occur in that those signals will now continue to be ignored if we missed a spot.
ubuntu-release-upgrader: The change is wrapping a bunch of code in a
try: except: block so if the indentation was off the pyflakes /
pycodestyle tests would fail but autopkgtest will catch that.
[Original bug report]
As a long-time-user of ?ubuntu, with apt-get as tool of choice for
updates/upgrades I wrote a daily script for updates, with 'dist-upgrade'.
In all earlier years, it wouldn't actually do an upgrade of a ?ubuntu
version; just all packages including new ones. Version updates had to be
initiated manually, and I was always asked if I really wanted the new ?ubuntu
version. Sounds appropriate.
Last night when it (dist-upgrade), it just gave me 20.04. No questions asked.
I for one consider this kind of intrusive, though.
It *might* have to make with me trying 'sudo do-release-upgrade -m desktop' a
number of times earlier; just to *check* if the upgrade was on offer; but this
is only a guess.
In *any* case, a pop-up asking "Are you sure? Are you connected
through an adequate pipe? Are you sitting with full batteries; better
a power supply?" would be convenient; since I am using my PC for
urgent duties, and didn't want to fiddle with unexpected upgrade bugs.
ProblemType: BugDistroRelease: Ubuntu 20.04
Package: ubuntu-release-upgrader-core 1:20.04.25
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
CrashDB: ubuntu
CurrentDesktop: KDE
Date: Th
[Touch-packages] [Bug 1928973] Re: Please merge lvm2 2.03.11-2.1 from Debian unstable
** Changed in: lvm2 (Ubuntu) Status: New => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lvm2 in Ubuntu. https://bugs.launchpad.net/bugs/1928973 Title: Please merge lvm2 2.03.11-2.1 from Debian unstable Status in lvm2 package in Ubuntu: Fix Committed Bug description: Please merge lvm2 2.03.11-2.1 from Debian unstable. Updated changelog and diff against Debian unstable to be attached below. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/1928973/+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 1920047] Re: sanlock global lock creation fail
** Changed in: lvm2 (Ubuntu) Assignee: (unassigned) => Heitor Alves de Siqueira (halves) ** Changed in: lvm2 (Ubuntu) Importance: Undecided => High ** Changed in: lvm2 (Ubuntu) Status: New => Fix Released ** Also affects: lvm2 (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: lvm2 (Ubuntu Groovy) Importance: Undecided Status: New ** Changed in: lvm2 (Ubuntu Focal) Status: New => Confirmed ** Changed in: lvm2 (Ubuntu Groovy) Status: New => Confirmed ** Changed in: lvm2 (Ubuntu Focal) Importance: Undecided => High ** Changed in: lvm2 (Ubuntu Focal) Assignee: (unassigned) => Heitor Alves de Siqueira (halves) ** Changed in: lvm2 (Ubuntu Groovy) Assignee: (unassigned) => Heitor Alves de Siqueira (halves) ** Changed in: lvm2 (Ubuntu Groovy) Importance: Undecided => High -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lvm2 in Ubuntu. https://bugs.launchpad.net/bugs/1920047 Title: sanlock global lock creation fail Status in lvm2 package in Ubuntu: Fix Released Status in lvm2 source package in Focal: Confirmed Status in lvm2 source package in Groovy: Confirmed Bug description: Hello, Running Ubuntu server 20.04, I cannot create a shared VG using sanlock : # vgcreate --shared foo /dev/mapper/vol Enabling sanlock global lock Skipping global lock: lockspace not found or started Logical volume "lvmlock" created. VG foo init failed: -28 Failed to initialize lock args for lock type sanlock Volume group "foo" successfully removed Messages in /var/log/syslog lvmlockd[446807]: 1616089866 WARNING: mixed block sizes physical 4096 logical 512 (using 4096) for /dev/mapper/foo-lvmlock lvmlockd[446807]: 1616089866 S lvm_foo init_vg_san write_resource gl error -28 /dev/mapper/foo-lvmlock # lsb_release -rd Description:Ubuntu 20.04.2 LTS Release:20.04 # dpkg -l | grep lvm ii liblvm2cmd2.03:amd64 2.03.07-1ubuntu1 amd64LVM2 command library ii lvm2 2.03.07-1ubuntu1 amd64Linux Logical Volume Manager ii lvm2-lockd 2.03.07-1ubuntu1 amd64LVM locking daemon A similar bug report from RHEL8 : https://bugzilla.redhat.com/show_bug.cgi?id=1833837 Bug has been fixed upstream : https://sourceware.org/git/?p=lvm2.git;a=commit;h=2d1fe38d84d499011d13ae1ea11535398528fc87 It seems to be included in version 2.03.10 : https://sourceware.org/git/?p=lvm2.git;a=shortlog;h=refs/tags/v2_03_10 How can we get this patch included in Ubuntu 20.04 ? King Regards, Charles To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/1920047/+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 1928973] Re: Please merge lvm2 2.03.11-2.1 from Debian unstable
LGTM, sponsoring! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lvm2 in Ubuntu. https://bugs.launchpad.net/bugs/1928973 Title: Please merge lvm2 2.03.11-2.1 from Debian unstable Status in lvm2 package in Ubuntu: New Bug description: Please merge lvm2 2.03.11-2.1 from Debian unstable. Updated changelog and diff against Debian unstable to be attached below. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/1928973/+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 1927796] Re: [SRU]pam_tally2 can cause accounts to be locked by correct password. pam_faillock use is the recommended fix
Oh, I seem to have overlooked that one. We are hitting the exact same issue with the new postgresql releases, so it's unrelated to the pam SRU: https://bugs.launchpad.net/ubuntu/+source/postgresql-12/+bug/1928773/comments/2 -- 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/1927796 Title: [SRU]pam_tally2 can cause accounts to be locked by correct password. pam_faillock use is the recommended fix Status in pam package in Ubuntu: Fix Released Status in pam source package in Bionic: Fix Committed Status in pam source package in Focal: Fix Released Status in pam source package in Groovy: Fix Released Status in pam source package in Hirsute: Fix Released Status in pam source package in Impish: Fix Released Bug description: [IMPACT] There is a known issue in pam_tally2 which may cause an account to be lock down even with correct password, in a busy node environment where simultaneous logins takes place (https://github.com/linux-pam/linux-pam/issues/71). There are already two customer cases from Canonical clients complaining about this behavior (00297697 and 00303806). Also, potentially, this will cause further problems in the future, since both STIG benchmarks and CIS benchmarks rely on pam_tally2 to lock accounts when wrong passwords are used. And both benchmarks - but specially STIG - requires use of a lot of audit rules, which can lead to the busy node environment. The issue impacts all pam_tally2 versions distributed in all currently supported Ubuntu versions and also the next unreleased one. Note that, according to https://github.com/linux-pam/linux-pam/issues/71, there is no plan to fix this issue! [FIX] This fix proposes to add pam_faillock module to the PAM package, so users of pam_tally2 having issues can migrate to pam_faillock. We also plan to modify the current STIG benchmarks to rely on pam_faillock instead of pam_tally2, but in order to do so, we need the pam_faillock module to be available. Note that we don't propose to remove pam_tally2, since not every user of this module is affected. [TEST] Tested on a VM installed with Focal server iso and on another with Bionic server iso. Enabled pam_faillock module as recommeded by its man page. Then tried to log over ssh with an incorrect password, until the account got locked. Waited for the configured grace time to unlock and logged in using the correct password. Note that, since the pam_tally2 issue is caused by a racing condition, with a hard to recreate environment (we could not even reproduce it with pam_tally2), we could not reproduce the conditions to test pam_faillock with. [REGRESSION POTENTIAL] The regression potential for this is small, since we're not removing the old pam_tally2 module, just adding another one. So anyone still using pam_tally2 will be able to do so. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pam/+bug/1927796/+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 1927796] Re: [SRU]pam_tally2 can cause accounts to be locked by correct password. pam_faillock use is the recommended fix
Hey Marc! What about the postgresql-10/armhf autopkgtest failure for bionic? -- 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/1927796 Title: [SRU]pam_tally2 can cause accounts to be locked by correct password. pam_faillock use is the recommended fix Status in pam package in Ubuntu: Fix Released Status in pam source package in Bionic: Fix Committed Status in pam source package in Focal: Fix Released Status in pam source package in Groovy: Fix Released Status in pam source package in Hirsute: Fix Released Status in pam source package in Impish: Fix Released Bug description: [IMPACT] There is a known issue in pam_tally2 which may cause an account to be lock down even with correct password, in a busy node environment where simultaneous logins takes place (https://github.com/linux-pam/linux-pam/issues/71). There are already two customer cases from Canonical clients complaining about this behavior (00297697 and 00303806). Also, potentially, this will cause further problems in the future, since both STIG benchmarks and CIS benchmarks rely on pam_tally2 to lock accounts when wrong passwords are used. And both benchmarks - but specially STIG - requires use of a lot of audit rules, which can lead to the busy node environment. The issue impacts all pam_tally2 versions distributed in all currently supported Ubuntu versions and also the next unreleased one. Note that, according to https://github.com/linux-pam/linux-pam/issues/71, there is no plan to fix this issue! [FIX] This fix proposes to add pam_faillock module to the PAM package, so users of pam_tally2 having issues can migrate to pam_faillock. We also plan to modify the current STIG benchmarks to rely on pam_faillock instead of pam_tally2, but in order to do so, we need the pam_faillock module to be available. Note that we don't propose to remove pam_tally2, since not every user of this module is affected. [TEST] Tested on a VM installed with Focal server iso and on another with Bionic server iso. Enabled pam_faillock module as recommeded by its man page. Then tried to log over ssh with an incorrect password, until the account got locked. Waited for the configured grace time to unlock and logged in using the correct password. Note that, since the pam_tally2 issue is caused by a racing condition, with a hard to recreate environment (we could not even reproduce it with pam_tally2), we could not reproduce the conditions to test pam_faillock with. [REGRESSION POTENTIAL] The regression potential for this is small, since we're not removing the old pam_tally2 module, just adding another one. So anyone still using pam_tally2 will be able to do so. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pam/+bug/1927796/+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 1902898] Re: power-button action inconsistent between user session and greeter
This bug was fixed in the package ubuntu-settings - 20.04.6 --- ubuntu-settings (20.04.6) focal; urgency=medium * debian/ubuntu-settings.gsettings-override: - use the same power options between session and greeter. (LP: #1902898) -- Didier Roche Fri, 30 Apr 2021 09:01:06 +0200 ** Changed in: ubuntu-settings (Ubuntu Focal) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-settings in Ubuntu. https://bugs.launchpad.net/bugs/1902898 Title: power-button action inconsistent between user session and greeter Status in ubuntu-settings package in Ubuntu: Fix Released Status in ubuntu-settings source package in Focal: Fix Released Status in ubuntu-settings source package in Hirsute: Fix Released Bug description: [Impact] When a user is logged in to the Ubuntu desktop, a power button event will cause the user to be prompted to choose if they'd like to proceed with a shutdown. However, if the system is sitting at a greeter screen, a power button event will instead attempt a suspend w/o prompting. This is due to a different set of defaults for the greeter and the user. This is a fix for this, aligning all power actions between the greeter behaviour and the user session one on the user session. [Test Plan] 1. Install new package and reboot 2. On the greeter screen (gdm), press the physical power button of your machine. 3. You should be now prompted about what to do, like shutdown. You can dismiss it. 4. Clicking on the physical suspend button should suspend the machine immediatly. [Where problems could occur] We change the scope of when we applied those settings: we were only applying them to the GNOME session ran by the user, and it will now be applied as default to the GNOME session ran by gdm. Impacts is thus limited to the greeter screen. Diff is available on this commit: https://git.launchpad.net/~ubuntu-desktop/ubuntu/+source/ubuntu-settings/commit/?h=focal&id=ca2f9aa9b03862ff044b64d7ef9506ca87e3dd89 -- Original report content: For a logged-in desktop user, they see: $ gsettings get org.gnome.settings-daemon.plugins.power power-button-action 'interactive' But the gdm user sees: $ sudo machinectl shell gdm@ /bin/bash Connected to the local host. Press ^] three times within 1s to exit session. gdm:~$ gsettings get org.gnome.settings-daemon.plugins.power power-button-action 'suspend' Changing the gdm user's setting to "interactive" using gsettings causes the greeter to begin prompting, consistent with the logged in user experience. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-settings/+bug/1902898/+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 1902898] Update Released
The verification of the Stable Release Update for ubuntu-settings has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-settings in Ubuntu. https://bugs.launchpad.net/bugs/1902898 Title: power-button action inconsistent between user session and greeter Status in ubuntu-settings package in Ubuntu: Fix Released Status in ubuntu-settings source package in Focal: Fix Released Status in ubuntu-settings source package in Hirsute: Fix Released Bug description: [Impact] When a user is logged in to the Ubuntu desktop, a power button event will cause the user to be prompted to choose if they'd like to proceed with a shutdown. However, if the system is sitting at a greeter screen, a power button event will instead attempt a suspend w/o prompting. This is due to a different set of defaults for the greeter and the user. This is a fix for this, aligning all power actions between the greeter behaviour and the user session one on the user session. [Test Plan] 1. Install new package and reboot 2. On the greeter screen (gdm), press the physical power button of your machine. 3. You should be now prompted about what to do, like shutdown. You can dismiss it. 4. Clicking on the physical suspend button should suspend the machine immediatly. [Where problems could occur] We change the scope of when we applied those settings: we were only applying them to the GNOME session ran by the user, and it will now be applied as default to the GNOME session ran by gdm. Impacts is thus limited to the greeter screen. Diff is available on this commit: https://git.launchpad.net/~ubuntu-desktop/ubuntu/+source/ubuntu-settings/commit/?h=focal&id=ca2f9aa9b03862ff044b64d7ef9506ca87e3dd89 -- Original report content: For a logged-in desktop user, they see: $ gsettings get org.gnome.settings-daemon.plugins.power power-button-action 'interactive' But the gdm user sees: $ sudo machinectl shell gdm@ /bin/bash Connected to the local host. Press ^] three times within 1s to exit session. gdm:~$ gsettings get org.gnome.settings-daemon.plugins.power power-button-action 'suspend' Changing the gdm user's setting to "interactive" using gsettings causes the greeter to begin prompting, consistent with the logged in user experience. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-settings/+bug/1902898/+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 1902898] Re: power-button action inconsistent between user session and greeter
Dann, please be sure to always include the version number of the package you have tested next time! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-settings in Ubuntu. https://bugs.launchpad.net/bugs/1902898 Title: power-button action inconsistent between user session and greeter Status in ubuntu-settings package in Ubuntu: Fix Released Status in ubuntu-settings source package in Focal: Fix Released Status in ubuntu-settings source package in Hirsute: Fix Released Bug description: [Impact] When a user is logged in to the Ubuntu desktop, a power button event will cause the user to be prompted to choose if they'd like to proceed with a shutdown. However, if the system is sitting at a greeter screen, a power button event will instead attempt a suspend w/o prompting. This is due to a different set of defaults for the greeter and the user. This is a fix for this, aligning all power actions between the greeter behaviour and the user session one on the user session. [Test Plan] 1. Install new package and reboot 2. On the greeter screen (gdm), press the physical power button of your machine. 3. You should be now prompted about what to do, like shutdown. You can dismiss it. 4. Clicking on the physical suspend button should suspend the machine immediatly. [Where problems could occur] We change the scope of when we applied those settings: we were only applying them to the GNOME session ran by the user, and it will now be applied as default to the GNOME session ran by gdm. Impacts is thus limited to the greeter screen. Diff is available on this commit: https://git.launchpad.net/~ubuntu-desktop/ubuntu/+source/ubuntu-settings/commit/?h=focal&id=ca2f9aa9b03862ff044b64d7ef9506ca87e3dd89 -- Original report content: For a logged-in desktop user, they see: $ gsettings get org.gnome.settings-daemon.plugins.power power-button-action 'interactive' But the gdm user sees: $ sudo machinectl shell gdm@ /bin/bash Connected to the local host. Press ^] three times within 1s to exit session. gdm:~$ gsettings get org.gnome.settings-daemon.plugins.power power-button-action 'suspend' Changing the gdm user's setting to "interactive" using gsettings causes the greeter to begin prompting, consistent with the logged in user experience. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-settings/+bug/1902898/+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 1927796] Re: [SRU]pam_tally2 can cause accounts to be locked by correct password. pam_faillock use is the recommended fix
This bug was fixed in the package pam - 1.3.1-5ubuntu4.2 --- pam (1.3.1-5ubuntu4.2) focal; urgency=medium * Backport pam_faillock module from pam 1.4.0 (LP: #1927796) - debian/patches-applied/add_pam_faillock.patch: add module. - debian/patches-applied/pam_faillock_create_directory: create dir before creating file in modules/pam_faillock/faillock.c. - debian/rules: set execute permissions on pam_faillock test. - debian/libpam-modules-bin.install: install faillock binary and man page. -- Marc Deslauriers Thu, 08 Apr 2021 07:06:27 -0400 ** Changed in: pam (Ubuntu Focal) 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/1927796 Title: [SRU]pam_tally2 can cause accounts to be locked by correct password. pam_faillock use is the recommended fix Status in pam package in Ubuntu: Fix Released Status in pam source package in Bionic: Fix Committed Status in pam source package in Focal: Fix Released Status in pam source package in Groovy: Fix Released Status in pam source package in Hirsute: Fix Released Status in pam source package in Impish: Fix Released Bug description: [IMPACT] There is a known issue in pam_tally2 which may cause an account to be lock down even with correct password, in a busy node environment where simultaneous logins takes place (https://github.com/linux-pam/linux-pam/issues/71). There are already two customer cases from Canonical clients complaining about this behavior (00297697 and 00303806). Also, potentially, this will cause further problems in the future, since both STIG benchmarks and CIS benchmarks rely on pam_tally2 to lock accounts when wrong passwords are used. And both benchmarks - but specially STIG - requires use of a lot of audit rules, which can lead to the busy node environment. The issue impacts all pam_tally2 versions distributed in all currently supported Ubuntu versions and also the next unreleased one. Note that, according to https://github.com/linux-pam/linux-pam/issues/71, there is no plan to fix this issue! [FIX] This fix proposes to add pam_faillock module to the PAM package, so users of pam_tally2 having issues can migrate to pam_faillock. We also plan to modify the current STIG benchmarks to rely on pam_faillock instead of pam_tally2, but in order to do so, we need the pam_faillock module to be available. Note that we don't propose to remove pam_tally2, since not every user of this module is affected. [TEST] Tested on a VM installed with Focal server iso and on another with Bionic server iso. Enabled pam_faillock module as recommeded by its man page. Then tried to log over ssh with an incorrect password, until the account got locked. Waited for the configured grace time to unlock and logged in using the correct password. Note that, since the pam_tally2 issue is caused by a racing condition, with a hard to recreate environment (we could not even reproduce it with pam_tally2), we could not reproduce the conditions to test pam_faillock with. [REGRESSION POTENTIAL] The regression potential for this is small, since we're not removing the old pam_tally2 module, just adding another one. So anyone still using pam_tally2 will be able to do so. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pam/+bug/1927796/+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 1898026] Re: interruption of dist-upgrade can leave you next release in sources.list
Hello udippel, or anyone else affected,
Accepted ubuntu-release-upgrader into groovy-proposed. The package will
build now and be available at https://launchpad.net/ubuntu/+source
/ubuntu-release-upgrader/1:20.10.16 in a few hours, and then in the
-proposed repository.
Please help us by testing this new package. See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed. Your feedback will aid us getting this
update out to other Ubuntu users.
If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, what testing has been
performed on the package and change the tag from verification-needed-
groovy to verification-done-groovy. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-groovy. In either case, without details of your testing we will
not be able to proceed.
Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in
advance for helping!
N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.
** Changed in: ubuntu-release-upgrader (Ubuntu Groovy)
Status: In Progress => Fix Committed
** Tags removed: verification-done-groovy
** Tags added: verification-needed-groovy
--
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/1898026
Title:
interruption of dist-upgrade can leave you next release in
sources.list
Status in apt package in Ubuntu:
Fix Released
Status in ubuntu-release-upgrader package in Ubuntu:
Fix Released
Status in apt source package in Bionic:
New
Status in ubuntu-release-upgrader source package in Bionic:
New
Status in apt source package in Focal:
New
Status in ubuntu-release-upgrader source package in Focal:
Fix Committed
Status in apt source package in Groovy:
Fix Released
Status in ubuntu-release-upgrader source package in Groovy:
Fix Committed
Status in apt source package in Hirsute:
Fix Released
Status in ubuntu-release-upgrader source package in Hirsute:
Fix Released
Bug description:
[Impact]
Calling update() or installing packages from apt clients resets their SIGINT
and SIGQUIT handlers to SIG_DFL, overriding any signal handlers they might have
set for them.
In case of ubuntu-release-upgrader, this results in the release
upgrader being unable to handle interrupts after it did the initial
update - the default libc handler will run and the program exits.
[Test plan]
[[apt]]
As a standalone test for apt, we can test the following script:
import apt
import time
apt.Cache().update()
print("WAITING")
try:
time.sleep(1)
except BaseException as e:
print("Seen", repr(e))
print("END")
Pressing Ctrl+C while WAITING is printed should print Seen
KeyboardInterrupt, and importantly, also the END line.
[[ubuntu-release-upgrader]]
1) On an Ubuntu 18.04 system run do-release-upgrade in a terminal.
2) At the "Do you want to start the upgrade?" question say Y.
3) When you see the "Lock screen disabled" message you will also see
"Inhibiting until Ctrl+C is pressed".
4) Press "Ctrl+C"
Your /etc/apt/sources.list file will now have focal in it instead of
bionic although the upgrade has quit. With the version of ubuntu-
release-upgrader in -proposed you will not see the "Ctrl+C" message.
For your sources.list file to be restored you'll need the version of
apt from bionic-proposed installed before starting the upgrade.
[Where problems could occur]
apt: This specific change removes the two lines that SIG_DFL the signal
handlers after running scripts. AFAWCT those lines are unnecessary - the code
that calls it temporarily sets the handlers to SIG_IGN but restores previous
handlers at the end; it was wrongly refactored decades ago. A regression could
occur in that those signals will now continue to be ignored if we missed a spot.
ubuntu-release-upgrader: The change is wrapping a bunch of code in a
try: except: block so if the indentation was off the pyflakes /
pycodestyle tests would fail but autopkgtest will catch that.
[Original bug report]
As a long-time-user of ?ubuntu, with apt-get as tool of choice for
updates/upgrades I wrote a daily script for updates, with 'dist-upgrade'.
In all earlier years, it wouldn't actually do an upgrade of a ?ubuntu
version; just all packages including new ones. Version updates had to be
initiated manually, and I was always asked if I really wanted the new ?ubuntu
version. Sounds appropriate.
Last night when it (dist-upgrade), it just gave me 20.04. No questions asked.
I for one consider this kind of intrusive, though.
It *might* have to make with
[Touch-packages] [Bug 1927796] Re: [SRU]pam_tally2 can cause accounts to be locked by correct password. pam_faillock use is the recommended fix
This bug was fixed in the package pam - 1.3.1-5ubuntu6.20.10.1 --- pam (1.3.1-5ubuntu6.20.10.1) groovy; urgency=medium * Backport pam_faillock module from pam 1.4.0 (LP: #1927796) - debian/patches-applied/add_pam_faillock.patch: add module. - debian/patches-applied/pam_faillock_create_directory: create dir before creating file in modules/pam_faillock/faillock.c. - debian/rules: set execute permissions on pam_faillock test. - debian/libpam-modules-bin.install: install faillock binary and man page. -- Richard Maciel Costa Thu, 08 Apr 2021 07:06:27 -0400 ** Changed in: pam (Ubuntu Groovy) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pam in Ubuntu. https://bugs.launchpad.net/bugs/1927796 Title: [SRU]pam_tally2 can cause accounts to be locked by correct password. pam_faillock use is the recommended fix Status in pam package in Ubuntu: Fix Released Status in pam source package in Bionic: Fix Committed Status in pam source package in Focal: Fix Committed Status in pam source package in Groovy: Fix Released Status in pam source package in Hirsute: Fix Released Status in pam source package in Impish: Fix Released Bug description: [IMPACT] There is a known issue in pam_tally2 which may cause an account to be lock down even with correct password, in a busy node environment where simultaneous logins takes place (https://github.com/linux-pam/linux-pam/issues/71). There are already two customer cases from Canonical clients complaining about this behavior (00297697 and 00303806). Also, potentially, this will cause further problems in the future, since both STIG benchmarks and CIS benchmarks rely on pam_tally2 to lock accounts when wrong passwords are used. And both benchmarks - but specially STIG - requires use of a lot of audit rules, which can lead to the busy node environment. The issue impacts all pam_tally2 versions distributed in all currently supported Ubuntu versions and also the next unreleased one. Note that, according to https://github.com/linux-pam/linux-pam/issues/71, there is no plan to fix this issue! [FIX] This fix proposes to add pam_faillock module to the PAM package, so users of pam_tally2 having issues can migrate to pam_faillock. We also plan to modify the current STIG benchmarks to rely on pam_faillock instead of pam_tally2, but in order to do so, we need the pam_faillock module to be available. Note that we don't propose to remove pam_tally2, since not every user of this module is affected. [TEST] Tested on a VM installed with Focal server iso and on another with Bionic server iso. Enabled pam_faillock module as recommeded by its man page. Then tried to log over ssh with an incorrect password, until the account got locked. Waited for the configured grace time to unlock and logged in using the correct password. Note that, since the pam_tally2 issue is caused by a racing condition, with a hard to recreate environment (we could not even reproduce it with pam_tally2), we could not reproduce the conditions to test pam_faillock with. [REGRESSION POTENTIAL] The regression potential for this is small, since we're not removing the old pam_tally2 module, just adding another one. So anyone still using pam_tally2 will be able to do so. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pam/+bug/1927796/+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 1928001] Re: [SRU] New stable release 2.68.1
This bug was fixed in the package glib2.0 - 2.68.1-1~ubuntu21.04.1
---
glib2.0 (2.68.1-1~ubuntu21.04.1) hirsute; urgency=medium
* debian/{control,gbp.conf}: Update branch refs for hirsute
* Backport from Debian to hirsute for SRU (LP: #1928001)
glib2.0 (2.68.1-1) experimental; urgency=medium
* New upstream stable release
* d/tests/run-with-locales: Avoid FTBFS with locales-all installed
-- Iain Lane Mon, 10 May 2021 18:14:07 +0100
** Changed in: glib2.0 (Ubuntu Hirsute)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to glib2.0 in Ubuntu.
https://bugs.launchpad.net/bugs/1928001
Title:
[SRU] New stable release 2.68.1
Status in glib2.0 package in Ubuntu:
Fix Released
Status in glib2.0 source package in Hirsute:
Fix Released
Bug description:
[ Description ]
Take this new upstream stable release.
* Fix a crash in `GKeyFile` when parsing a file which contains translations
using a `GKeyFile` instance which has loaded another file previously (#2361)
* Pin GIO DLL in memory on Windows (!2016)
* Bugs fixed:
- #2361 g_key_file_load_from_file segfaults on "Key[*]="like lines
- !1997 Backport !1996 “Include glibconfig.h to get the G_OS_UNIX token” to
glib-2-68
- !2016 GIO W32: Pin gio DLL
- !2021 Backport MR !2016 (GIO W32: Pin gio DLL) into glib-2-68
- !2022 Few fixes and notes for building on Visual Studio 2012 and earlier
- !2034 Backport MR !2032 (gkeyfile: Drop a redundant check) into glib-2-68
- !2035 Backport !2026 “Split g_test_log() messages that contain multiple
lines” to glib-2-68
[ QA ]
Upstream release, so QA already performed by maintainers
https://wiki.ubuntu.com/StableReleaseUpdates/GNOME
This upload will trigger many autopkgtests that we expect to not be
regressed by this upload.
[ What could go wrong ]
This update contains fixes in multiple places so multiple apps could
be affected. The consequences of a broken GLib can range from some
functions returning bad results sometimes, which have minimal runtime
implications, up to the system simply crashing all the time.
Pretty much all parts of GNOME use GLib, so test anything in the
desktop that you can. If you reboot the machine and can get to the
desktop, that's already tested GLib extensively. But also run
applications like GNOME terminal, Files and Epiphany.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1928001/+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 1928001] Update Released
The verification of the Stable Release Update for glib2.0 has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1928001 Title: [SRU] New stable release 2.68.1 Status in glib2.0 package in Ubuntu: Fix Released Status in glib2.0 source package in Hirsute: Fix Released Bug description: [ Description ] Take this new upstream stable release. * Fix a crash in `GKeyFile` when parsing a file which contains translations using a `GKeyFile` instance which has loaded another file previously (#2361) * Pin GIO DLL in memory on Windows (!2016) * Bugs fixed: - #2361 g_key_file_load_from_file segfaults on "Key[*]="like lines - !1997 Backport !1996 “Include glibconfig.h to get the G_OS_UNIX token” to glib-2-68 - !2016 GIO W32: Pin gio DLL - !2021 Backport MR !2016 (GIO W32: Pin gio DLL) into glib-2-68 - !2022 Few fixes and notes for building on Visual Studio 2012 and earlier - !2034 Backport MR !2032 (gkeyfile: Drop a redundant check) into glib-2-68 - !2035 Backport !2026 “Split g_test_log() messages that contain multiple lines” to glib-2-68 [ QA ] Upstream release, so QA already performed by maintainers https://wiki.ubuntu.com/StableReleaseUpdates/GNOME This upload will trigger many autopkgtests that we expect to not be regressed by this upload. [ What could go wrong ] This update contains fixes in multiple places so multiple apps could be affected. The consequences of a broken GLib can range from some functions returning bad results sometimes, which have minimal runtime implications, up to the system simply crashing all the time. Pretty much all parts of GNOME use GLib, so test anything in the desktop that you can. If you reboot the machine and can get to the desktop, that's already tested GLib extensively. But also run applications like GNOME terminal, Files and Epiphany. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1928001/+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 1928001] Re: [SRU] New stable release 2.68.1
Hints committed, thanks for looking into that! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1928001 Title: [SRU] New stable release 2.68.1 Status in glib2.0 package in Ubuntu: Fix Released Status in glib2.0 source package in Hirsute: Fix Released Bug description: [ Description ] Take this new upstream stable release. * Fix a crash in `GKeyFile` when parsing a file which contains translations using a `GKeyFile` instance which has loaded another file previously (#2361) * Pin GIO DLL in memory on Windows (!2016) * Bugs fixed: - #2361 g_key_file_load_from_file segfaults on "Key[*]="like lines - !1997 Backport !1996 “Include glibconfig.h to get the G_OS_UNIX token” to glib-2-68 - !2016 GIO W32: Pin gio DLL - !2021 Backport MR !2016 (GIO W32: Pin gio DLL) into glib-2-68 - !2022 Few fixes and notes for building on Visual Studio 2012 and earlier - !2034 Backport MR !2032 (gkeyfile: Drop a redundant check) into glib-2-68 - !2035 Backport !2026 “Split g_test_log() messages that contain multiple lines” to glib-2-68 [ QA ] Upstream release, so QA already performed by maintainers https://wiki.ubuntu.com/StableReleaseUpdates/GNOME This upload will trigger many autopkgtests that we expect to not be regressed by this upload. [ What could go wrong ] This update contains fixes in multiple places so multiple apps could be affected. The consequences of a broken GLib can range from some functions returning bad results sometimes, which have minimal runtime implications, up to the system simply crashing all the time. Pretty much all parts of GNOME use GLib, so test anything in the desktop that you can. If you reboot the machine and can get to the desktop, that's already tested GLib extensively. But also run applications like GNOME terminal, Files and Epiphany. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1928001/+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 1927796] Re: [SRU]pam_tally2 can cause accounts to be locked by correct password. pam_faillock use is the recommended fix
This bug was fixed in the package pam - 1.3.1-5ubuntu6.21.04.1 --- pam (1.3.1-5ubuntu6.21.04.1) hirsute; urgency=medium * Backport pam_faillock module from pam 1.4.0 (LP: #1927796) - debian/patches-applied/add_pam_faillock.patch: add module. - debian/patches-applied/pam_faillock_create_directory: create dir before creating file in modules/pam_faillock/faillock.c. - debian/rules: set execute permissions on pam_faillock test. - debian/libpam-modules-bin.install: install faillock binary and man page. -- Richard Maciel Costa Thu, 08 Apr 2021 07:06:27 -0400 ** Changed in: pam (Ubuntu Hirsute) 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/1927796 Title: [SRU]pam_tally2 can cause accounts to be locked by correct password. pam_faillock use is the recommended fix Status in pam package in Ubuntu: Fix Released Status in pam source package in Bionic: Fix Committed Status in pam source package in Focal: Fix Committed Status in pam source package in Groovy: Fix Committed Status in pam source package in Hirsute: Fix Released Status in pam source package in Impish: Fix Released Bug description: [IMPACT] There is a known issue in pam_tally2 which may cause an account to be lock down even with correct password, in a busy node environment where simultaneous logins takes place (https://github.com/linux-pam/linux-pam/issues/71). There are already two customer cases from Canonical clients complaining about this behavior (00297697 and 00303806). Also, potentially, this will cause further problems in the future, since both STIG benchmarks and CIS benchmarks rely on pam_tally2 to lock accounts when wrong passwords are used. And both benchmarks - but specially STIG - requires use of a lot of audit rules, which can lead to the busy node environment. The issue impacts all pam_tally2 versions distributed in all currently supported Ubuntu versions and also the next unreleased one. Note that, according to https://github.com/linux-pam/linux-pam/issues/71, there is no plan to fix this issue! [FIX] This fix proposes to add pam_faillock module to the PAM package, so users of pam_tally2 having issues can migrate to pam_faillock. We also plan to modify the current STIG benchmarks to rely on pam_faillock instead of pam_tally2, but in order to do so, we need the pam_faillock module to be available. Note that we don't propose to remove pam_tally2, since not every user of this module is affected. [TEST] Tested on a VM installed with Focal server iso and on another with Bionic server iso. Enabled pam_faillock module as recommeded by its man page. Then tried to log over ssh with an incorrect password, until the account got locked. Waited for the configured grace time to unlock and logged in using the correct password. Note that, since the pam_tally2 issue is caused by a racing condition, with a hard to recreate environment (we could not even reproduce it with pam_tally2), we could not reproduce the conditions to test pam_faillock with. [REGRESSION POTENTIAL] The regression potential for this is small, since we're not removing the old pam_tally2 module, just adding another one. So anyone still using pam_tally2 will be able to do so. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pam/+bug/1927796/+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 1925379] Update Released
The verification of the Stable Release Update for gtk+3.0 has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1925379 Title: Auto-Correct in LibreOffice does not work with 3.24.25-1ubuntu4 Status in gtk+3.0 package in Ubuntu: Fix Released Status in gtk+3.0 source package in Hirsute: Fix Released Bug description: * Impact The auto-correction in libreoffice is not action as it should * Test case see comment 9 * Regression potential The changes are in the input handling so check that standard input, keyboard layouts, compose and keybinding as worked as expected on different layout and language type, include ibus and chinese. I just did a fresh install of Ubuntu 21.04 (smooth as silk), but then discovered that Auto-Correct in LibreOffice does not work. Yesterday, when I was still running 20.04, Auto-Correct worked fine -- same LibreOffice version, same LibreOffice profile, same LibreOffice document, and no changes on my part to my LibreOffice settings since I installed Ubuntu 21.04. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1925379/+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 1925379] Re: Auto-Correct in LibreOffice does not work with 3.24.25-1ubuntu4
This bug was fixed in the package gtk+3.0 - 3.24.25-1ubuntu4.1 --- gtk+3.0 (3.24.25-1ubuntu4.1) hirsute; urgency=medium * debian/patches/git_imcontext.patch: - cherry pick imcontext fixes until 3.24.29 (LP: #1925379) -- Rico Tzschichholz Sat, 01 May 2021 10:01:31 +0200 ** Changed in: gtk+3.0 (Ubuntu Hirsute) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1925379 Title: Auto-Correct in LibreOffice does not work with 3.24.25-1ubuntu4 Status in gtk+3.0 package in Ubuntu: Fix Released Status in gtk+3.0 source package in Hirsute: Fix Released Bug description: * Impact The auto-correction in libreoffice is not action as it should * Test case see comment 9 * Regression potential The changes are in the input handling so check that standard input, keyboard layouts, compose and keybinding as worked as expected on different layout and language type, include ibus and chinese. I just did a fresh install of Ubuntu 21.04 (smooth as silk), but then discovered that Auto-Correct in LibreOffice does not work. Yesterday, when I was still running 20.04, Auto-Correct worked fine -- same LibreOffice version, same LibreOffice profile, same LibreOffice document, and no changes on my part to my LibreOffice settings since I installed Ubuntu 21.04. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1925379/+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 1927796] Update Released
The verification of the Stable Release Update for pam has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- 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/1927796 Title: [SRU]pam_tally2 can cause accounts to be locked by correct password. pam_faillock use is the recommended fix Status in pam package in Ubuntu: Fix Released Status in pam source package in Bionic: Fix Committed Status in pam source package in Focal: Fix Committed Status in pam source package in Groovy: Fix Committed Status in pam source package in Hirsute: Fix Released Status in pam source package in Impish: Fix Released Bug description: [IMPACT] There is a known issue in pam_tally2 which may cause an account to be lock down even with correct password, in a busy node environment where simultaneous logins takes place (https://github.com/linux-pam/linux-pam/issues/71). There are already two customer cases from Canonical clients complaining about this behavior (00297697 and 00303806). Also, potentially, this will cause further problems in the future, since both STIG benchmarks and CIS benchmarks rely on pam_tally2 to lock accounts when wrong passwords are used. And both benchmarks - but specially STIG - requires use of a lot of audit rules, which can lead to the busy node environment. The issue impacts all pam_tally2 versions distributed in all currently supported Ubuntu versions and also the next unreleased one. Note that, according to https://github.com/linux-pam/linux-pam/issues/71, there is no plan to fix this issue! [FIX] This fix proposes to add pam_faillock module to the PAM package, so users of pam_tally2 having issues can migrate to pam_faillock. We also plan to modify the current STIG benchmarks to rely on pam_faillock instead of pam_tally2, but in order to do so, we need the pam_faillock module to be available. Note that we don't propose to remove pam_tally2, since not every user of this module is affected. [TEST] Tested on a VM installed with Focal server iso and on another with Bionic server iso. Enabled pam_faillock module as recommeded by its man page. Then tried to log over ssh with an incorrect password, until the account got locked. Waited for the configured grace time to unlock and logged in using the correct password. Note that, since the pam_tally2 issue is caused by a racing condition, with a hard to recreate environment (we could not even reproduce it with pam_tally2), we could not reproduce the conditions to test pam_faillock with. [REGRESSION POTENTIAL] The regression potential for this is small, since we're not removing the old pam_tally2 module, just adding another one. So anyone still using pam_tally2 will be able to do so. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pam/+bug/1927796/+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 1529932] Re: X session crashes with EQ overflowing
Thank you for reporting this bug to Ubuntu. Ubuntu 16.04 (xenial) reached end of standard support in April 2021: https://wiki.ubuntu.com/Releases If you would like to continue with free support then please update to a newer Ubuntu version and tell us if the problem still occurs. If you would like to continue with Ubuntu 16.04 then there is a paid support option detailed at https://www.ubuntu.com/esm ** Changed in: xorg (Ubuntu) Status: Triaged => Won't Fix -- 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/1529932 Title: X session crashes with EQ overflowing Status in X.Org X server: Unknown Status in xorg package in Ubuntu: Won't Fix Bug description: On my very old laptop, that is equipped with an Ati Mobility Radeon X700, sometimes (and, sadly, I have to use this word, because I found no regularity pattern for the occurrence of this bug) randomly the desktop session locks, that is I can only move the mouse pointer, but I cannot interact anymore with the desktop session. I am forced to login trough ssh from another pc and to restart the laptop. In Xorg.0.log I found these lines that are, in my opinion, related to the crash: (EE) [mi] EQ overflowing. Additional events will be discarded until existing events are processed. (EE) (EE) Backtrace: (EE) 0: /usr/bin/X (xorg_backtrace+0x4e) [0x5608e56a768e] (EE) 1: /usr/bin/X (mieqEnqueue+0x253) [0x5608e5689373] (EE) 2: /usr/bin/X (QueuePointerEvents+0x52) [0x5608e5563152] (EE) 3: /usr/bin/X (xf86PostMotionEvent+0xd6) [0x5608e559a026] (EE) 4: /usr/lib/xorg/modules/input/synaptics_drv.so (0x7f5e497b3000+0x5322) [0x7f5e497b8322] (EE) 5: /usr/lib/xorg/modules/input/synaptics_drv.so (0x7f5e497b3000+0x73d2) [0x7f5e497ba3d2] (EE) 6: /usr/bin/X (0x5608e54f3000+0x96ac8) [0x5608e5589ac8] (EE) 7: /usr/bin/X (0x5608e54f3000+0xbfc92) [0x5608e55b2c92] (EE) 8: /lib/x86_64-linux-gnu/libc.so.6 (0x7f5e522c9000+0x352f0) [0x7f5e522fe2f0] (EE) 9: /lib/x86_64-linux-gnu/libc.so.6 (ioctl+0x7) [0x7f5e523c60b7] (EE) 10: /usr/lib/x86_64-linux-gnu/libdrm.so.2 (drmIoctl+0x28) [0x7f5e536ada08] (EE) 11: /usr/lib/x86_64-linux-gnu/libdrm.so.2 (drmCommandWrite+0x1b) [0x7f5e536b06cb] (EE) 12: /usr/lib/x86_64-linux-gnu/libdrm_radeon.so.1 (0x7f5e4e3ad000+0x19c9) [0x7f5e4e3ae9c9] (EE) 13: /usr/lib/x86_64-linux-gnu/libdrm_radeon.so.1 (0x7f5e4e3ad000+0x1c0c) [0x7f5e4e3aec0c] (EE) 14: /usr/lib/xorg/modules/drivers/radeon_drv.so (0x7f5e4e5b9000+0x26236) [0x7f5e4e5df236] (EE) 15: /usr/lib/xorg/modules/libexa.so (0x7f5e4d973000+0x569b) [0x7f5e4d97869b] (EE) 16: /usr/lib/xorg/modules/libexa.so (0x7f5e4d973000+0x7e8f) [0x7f5e4d97ae8f] (EE) 17: /usr/lib/xorg/modules/libexa.so (0x7f5e4d973000+0x11953) [0x7f5e4d984953] (EE) 18: /usr/lib/xorg/modules/libexa.so (0x7f5e4d973000+0xe770) [0x7f5e4d981770] (EE) 19: /usr/bin/X (0x5608e54f3000+0x13ca51) [0x5608e562fa51] (EE) 20: /usr/lib/xorg/modules/libexa.so (0x7f5e4d973000+0xf74f) [0x7f5e4d98274f] (EE) 21: /usr/bin/X (0x5608e54f3000+0x1332a2) [0x5608e56262a2] (EE) 22: /usr/bin/X (0x5608e54f3000+0x5818f) [0x5608e554b18f] (EE) 23: /usr/bin/X (0x5608e54f3000+0x5c34b) [0x5608e554f34b] (EE) 24: /lib/x86_64-linux-gnu/libc.so.6 (__libc_start_main+0xf0) [0x7f5e522e9a40] (EE) 25: /usr/bin/X (_start+0x29) [0x5608e55396c9] (EE) (EE) [mi] These backtraces from mieqEnqueue may point to a culprit higher up the stack. (EE) [mi] mieq is *NOT* the cause. It is a victim. (EE) [mi] EQ overflow continuing. 100 events have been dropped. (EE) (EE) Backtrace: (EE) 0: /usr/bin/X (xorg_backtrace+0x4e) [0x5608e56a768e] (EE) 1: /usr/bin/X (QueuePointerEvents+0x52) [0x5608e5563152] (EE) 2: /usr/bin/X (xf86PostMotionEvent+0xd6) [0x5608e559a026] (EE) 3: /usr/lib/xorg/modules/input/synaptics_drv.so (0x7f5e497b3000+0x5322) [0x7f5e497b8322] (EE) 4: /usr/lib/xorg/modules/input/synaptics_drv.so (0x7f5e497b3000+0x73d2) [0x7f5e497ba3d2] (EE) 5: /usr/bin/X (0x5608e54f3000+0x96ac8) [0x5608e5589ac8] (EE) 6: /usr/bin/X (0x5608e54f3000+0xbfc92) [0x5608e55b2c92] (EE) 7: /lib/x86_64-linux-gnu/libc.so.6 (0x7f5e522c9000+0x352f0) [0x7f5e522fe2f0] (EE) 8: /lib/x86_64-linux-gnu/libc.so.6 (ioctl+0x7) [0x7f5e523c60b7] (EE) 9: /usr/lib/x86_64-linux-gnu/libdrm.so.2 (drmIoctl+0x28) [0x7f5e536ada08] (EE) 10: /usr/lib/x86_64-linux-gnu/libdrm.so.2 (drmCommandWrite+0x1b) [0x7f5e536b06cb] (EE) 11: /usr/lib/x86_64-linux-gnu/libdrm_radeon.so.1 (0x7f5e4e3ad000+0x19c9) [0x7f5e4e3ae9c9] (EE) 12: /usr/lib/x86_64-linux-gnu/libdrm_radeon.so.1 (0x7f5e4e3ad000+0x1c0c) [0x7f5e4e3aec0c] (EE) 13: /usr/lib/xorg/modules/drivers/radeon_drv.so (0x7f5e4e5b9000+0x26236) [0x7f5e4e5df236] (EE) 14: /usr/lib/xorg/modules/libexa.so (0x7f5e4d973000+0x569b) [0x7f5e4d97869b] (EE) 15: /usr/lib/xorg/modules/libexa.so (0x7f5e4d973000+0x7e8f) [0x7f5e4d97ae8f] (EE) 16:
[Touch-packages] [Bug 1570653] Re: LG 31MU97-B Black 31" 4K Monitor not detected properly
Thank you for reporting this bug to Ubuntu. Ubuntu 16.04 (xenial) reached end of standard support in April 2021: https://wiki.ubuntu.com/Releases If you would like to continue with free support then please update to a newer Ubuntu version and tell us if the problem still occurs. If you would like to continue with Ubuntu 16.04 then there is a paid support option detailed at https://www.ubuntu.com/esm ** Changed in: xorg (Ubuntu) Status: Confirmed => Won't Fix -- 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/1570653 Title: LG 31MU97-B Black 31" 4K Monitor not detected properly Status in xorg package in Ubuntu: Won't Fix Bug description: 4K monitor is not properly detected. using xfce desktop "Display" utility, my monitor is detected as "Goldstar Company Ltd 27" with a resolution of 3840x2160 and 60.0Hz The actual monitor is an LG 31MU97-B Black 31" with a resolution of 4096x2160. I'm pretty sure the Monitor's resolution was properly detected in 15.10 (4096x2160). It was called "Goldstar Company Ltd" but I do not recall which size was detected. (27" or 31") I remember seeing a 4K youtube video in 15.10 and noting the black bands on each side of the display, due to the difference between 3840 and 4096. --- ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: XFCE DistUpgraded: 2016-04-14 20:11:08,467 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process "./xorg_fix_proprietary.py" (No such file or directory) (8)) DistroCodename: xenial DistroRelease: Ubuntu 16.04 DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Curacao PRO [Radeon R7 370 / R9 270/370 OEM] [1002:6811] (prog-if 00 [VGA controller]) Subsystem: PC Partner Limited / Sapphire Technology Curacao PRO [Radeon R7 370 / R9 270/370 OEM] [174b:e271] InstallationDate: Installed on 2015-11-24 (204 days ago) InstallationMedia: Xubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) LightdmGreeterLog: upstart: indicator-application main process (2191) killed by TERM signal Invalid MIT-MAGIC-COOKIE-1 key LightdmGreeterLogOld: ** Message: Starting lightdm-gtk-greeter 2.0.1 (Aug 7 2015, 01:24:18) ** Message: [Configuration] Reading file: /etc/lightdm/lightdm-gtk-greeter.conf.d/01_ubuntu.conf ** Message: [Configuration] Reading file: /etc/lightdm/lightdm-gtk-greeter.conf.d/30_xubuntu.conf ** Message: [Configuration] Reading file: /etc/lightdm/lightdm-gtk-greeter.conf upstart: indicator-application main process (1802) killed by TERM signal MachineType: To be filled by O.E.M. To be filled by O.E.M. Package: xorg 1:7.7+13ubuntu3 PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-22-lowlatency root=/dev/mapper/xubuntu--vg-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.4.0-22.40-lowlatency 4.4.8 Tags: xenial ubuntu Uname: Linux 4.4.0-22-lowlatency x86_64 UpgradeStatus: Upgraded to xenial on 2016-04-15 (62 days ago) UserGroups: adm audio cdrom dip libvirtd lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/08/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2501 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: SABERTOOTH 990FX R2.0 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.:bvr2501:bd04/08/2014:svnTobefilledbyO.E.M.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnASUSTeKCOMPUTERINC.:rnSABERTOOTH990FXR2.0: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. version.compiz: compiz N/A version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2 version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2.2 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 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 To manage notifications about this bug go to: https://bugs.launchpad.net/ub
[Touch-packages] [Bug 1525477] Re: X server crash when pasting selection using middle button in Chromium
Thank you for reporting this bug to Ubuntu. Ubuntu 16.04 (xenial) reached end of standard support in April 2021: https://wiki.ubuntu.com/Releases If you would like to continue with free support then please update to a newer Ubuntu version and tell us if the problem still occurs. If you would like to continue with Ubuntu 16.04 then there is a paid support option detailed at https://www.ubuntu.com/esm ** Changed in: xorg (Ubuntu) Status: New => Won't Fix -- 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/1525477 Title: X server crash when pasting selection using middle button in Chromium Status in xorg package in Ubuntu: Won't Fix Bug description: Description: Ubuntu 14.04.3 LTS Release: 14.04 xorg 1:7.7+1ubuntu8.1 Select any text; use middle button to paste selection in Chromium (I observed it pasting in URL bar or in any form text input field, including previous attempt to report this bug :) ). Session crashes. It does not happen, when either pasting into different application (like terminal) or wen use Copy - Paste instead of middle button. I noticed it about a week ago, so it must be some recent change; I use selection paste often enough to notice something like this before. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8.1 ProcVersionSignature: Ubuntu 4.2.0-19.23~14.04.1-generic 4.2.6 Uname: Linux 4.2.0-19-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.19 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 CurrentDesktop: Unity Date: Sat Dec 12 11:09:22 2015 DistUpgraded: Fresh install DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-trusty-amd64-20140620-0 DistroCodename: trusty DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation Broadwell-U Integrated Graphics [8086:1616] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:062b] InstallationDate: Installed on 2015-07-02 (162 days ago) InstallationMedia: Ubuntu 14.04 "Trusty" - Build amd64 LIVE Binary 20140620-04:25 MachineType: Dell Inc. Latitude E5450 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-19-generic root=UUID=d06b07a3-04bf-46e1-8cae-5f2592c69192 ro quiet splash pcie_aspm=force radeon.modeset=0 nouveau.modeset=0 video.use_native_backlight=1 video.use_native_backlight=1 crashkernel=384M-:128M vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/19/2015 dmi.bios.vendor: Dell Inc. dmi.bios.version: A07 dmi.board.name: 06J17N dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA07:bd05/19/2015:svnDellInc.:pnLatitudeE5450:pvr01:rvnDellInc.:rn06J17N:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E5450 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.11.3+14.04.20150313-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.60-2~ubuntu14.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.5 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.5 version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2.7 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3.1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1.6 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 xserver.bootTime: Sat Dec 12 11:08:11 2015 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id1133 vendor LGD xserver.version: 2:1.15.1-0ubuntu2.7 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1525477/+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 1541082] Re: [PowerMac3, 1] Blotchy GUI graphics for images
Thank you for reporting this bug to Ubuntu. Ubuntu 16.04 (xenial) reached end of standard support in April 2021: https://wiki.ubuntu.com/Releases If you would like to continue with free support then please update to a newer Ubuntu version and tell us if the problem still occurs. If you would like to continue with Ubuntu 16.04 then there is a paid support option detailed at https://www.ubuntu.com/esm ** Changed in: xorg (Ubuntu) Status: Confirmed => Won't Fix -- 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/1541082 Title: [PowerMac3,1] Blotchy GUI graphics for images Status in xorg package in Ubuntu: Won't Fix Bug description: The background image and other image files are blotchy. --- ApportVersion: 2.20.1-0ubuntu2.1 Architecture: powerpc BootLog: fsck from util-linux 2.27.1 /dev/sda13: clean, 182266/1458176 files, 1099215/5826607 blocks CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None DistUpgraded: Fresh install DistroCodename: xenial DistroRelease: Ubuntu 16.04 DistroVariant: ubuntu DpkgLog: ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Rage 128 PRO AGP 4x TMDS [1002:5046] (prog-if 00 [VGA controller]) InstallationDate: Installed on 2016-01-31 (154 days ago) InstallationMedia: Ubuntu-MATE 16.04 LTS "Xenial Xerus" - Alpha powerpc (20160123) Lsusb: Bus 002 Device 004: ID 047d:1029 Kensington Mouse*in*a*Box Optical Elite Bus 002 Device 003: ID 05ac:0220 Apple, Inc. Aluminum Keyboard (ANSI) Bus 002 Device 002: ID 05ac:1006 Apple, Inc. Hub in Aluminum Keyboard Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Package: xorg 1:7.7+13ubuntu3 PackageArchitecture: powerpc ProcEnviron: LANGUAGE=en_US TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: root=UUID=4eb514e5-48d7-4e99-a402-5294c80e78cc ro quiet splash ProcVersionSignature: Ubuntu 4.4.0-24.43-powerpc-smp 4.4.10 Renderer: Software Tags: xenial ubuntu Uname: Linux 4.4.0-24-powerpc-smp ppc UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True version.compiz: compiz 1:0.9.12.2+16.04.20160526-0ubuntu1 version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2 version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2.2 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 N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1541082/+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 1576784] Re: MatchIsTouchscreen also matches touchpads in 16.04
Thank you for reporting this bug to Ubuntu. Ubuntu 16.04 (xenial) reached end of standard support in April 2021: https://wiki.ubuntu.com/Releases If you would like to continue with free support then please update to a newer Ubuntu version and tell us if the problem still occurs. If you would like to continue with Ubuntu 16.04 then there is a paid support option detailed at https://www.ubuntu.com/esm ** Changed in: xorg (Ubuntu) Status: Confirmed => Won't Fix -- 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/1576784 Title: MatchIsTouchscreen also matches touchpads in 16.04 Status in xorg package in Ubuntu: Won't Fix Bug description: Previously in 15.10 I had the following rule in /usr/share/X11/xorg.conf.d/99-no-touchscreen.conf: Section "InputClass" Identifier "Touchscreen disable" MatchIsTouchscreen "on" Option "Ignore" "on" EndSection This worked in disabling the touchpad on my lenovo T440s After the upgrade to 16.04 I noticed that my touchpad would not work. And I found the following lines in the log: [ 3107.956] (II) config/udev: Adding input device SynPS/2 Synaptics TouchPad (/dev/input/event6) [ 3107.956] (**) SynPS/2 Synaptics TouchPad: Ignoring device from InputClass "Touchscreen disable" [ 3107.956] (II) config/udev: Adding input device SynPS/2 Synaptics TouchPad (/dev/input/mouse0) [ 3107.956] (**) SynPS/2 Synaptics TouchPad: Ignoring device from InputClass "Touchscreen disable" So I had to disable the rule in order to be able to use the touchpad, and now I can't disable the touchscreen. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xserver-xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-22.38-generic 4.4.8 Uname: Linux 4.4.0-22-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 CurrentDesktop: KDE Date: Fri Apr 29 09:39:23 2016 InstallationDate: Installed on 2015-03-18 (407 days ago) InstallationMedia: Kubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: xorg UpgradeStatus: Upgraded to xenial on 2016-04-28 (1 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1576784/+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 1610666] Re: Mouse cursor moves choppy/doesn't update its position as it should
Thank you for reporting this bug to Ubuntu. Ubuntu 16.04 (xenial) reached end of standard support in April 2021: https://wiki.ubuntu.com/Releases If you would like to continue with free support then please update to a newer Ubuntu version and tell us if the problem still occurs. If you would like to continue with Ubuntu 16.04 then there is a paid support option detailed at https://www.ubuntu.com/esm ** Changed in: xorg (Ubuntu) Status: Triaged => Won't Fix -- 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/1610666 Title: Mouse cursor moves choppy/doesn't update its position as it should Status in xorg package in Ubuntu: Won't Fix Bug description: Q. What I expected to happen? A. The mouse would run smoothly as it does run in windows. Q. What happened instead? A. The mouse lags moves choppy/doesn't update its position as it should Additional Information: Output of "xinput --list --short" ⎡ Virtual core pointerid=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointer id=4[slave pointer (2)] ⎜ ↳ E-Signal USB Gaming Mouse id=10 [slave pointer (2)] ⎜ ↳ E-Signal USB Gaming Mouse id=11 [slave pointer (2)] ⎣ Virtual core keyboard id=3[master keyboard (2)] ↳ Virtual core XTEST keyboard id=5[slave keyboard (3)] ↳ Power Buttonid=6[slave keyboard (3)] ↳ Video Bus id=7[slave keyboard (3)] ↳ Power Buttonid=8[slave keyboard (3)] ↳ Microsoft® LifeCam HD-3000 id=9[slave keyboard (3)] ↳ AT Translated Set 2 keyboardid=12 [slave keyboard (3)] Output of "xinput --list-props 11" Device 'E-Signal USB Gaming Mouse': Device Enabled (133):1 Coordinate Transformation Matrix (135): 1.00, 0.00, 0.00, 0.00, 1.00, 0.00, 0.00, 0.00, 1.00 Device Accel Profile (259): 0 Device Accel Constant Deceleration (260):1.00 Device Accel Adaptive Deceleration (261):1.00 Device Accel Velocity Scaling (262): 10.00 Device Product ID (251): 1241, 41132 Device Node (252): "/dev/input/event4" Evdev Axis Inversion (263): 0, 0 Evdev Axes Swap (265): 0 Axis Labels (266): "Rel X" (143), "Rel Y" (144), "Rel Horiz Wheel" (257), "Rel Vert Wheel" (258) Button Labels (267): "Button Left" (136), "Button Middle" (137), "Button Right" (138), "Button Wheel Up" (139), "Button Wheel Down" (140), "Button Horiz Wheel Left" (141), "Button Horiz Wheel Right" (142), "Button Side" (255), "Button Extra" (256), "Button Unknown" (254), "Button Unknown" (254), "Button Unknown" (254), "Button Unknown" (254) Evdev Scrolling Distance (268): 1, 1, 1 Evdev Middle Button Emulation (269): 0 Evdev Middle Button Timeout (270): 50 Evdev Third Button Emulation (271): 0 Evdev Third Button Emulation Timeout (272): 1000 Evdev Third Button Emulation Button (273): 3 Evdev Third Button Emulation Threshold (274):20 Evdev Wheel Emulation (275): 0 Evdev Wheel Emulation Axes (276):0, 0, 4, 5 Evdev Wheel Emulation Inertia (277): 10 Evdev Wheel Emulation Timeout (278): 200 Evdev Wheel Emulation Button (279): 4 Evdev Drag Lock Buttons (280): 0 Output of "lsusb" Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 006 Device 002: ID 0bc2:3321 Seagate RSS LLC Bus 006 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 005 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 005: ID 04d9:a0ac Holtek Semiconductor, Inc. Bus 001 Device 003: ID 045e:0779 Microsoft Corp. LifeCam HD-3000 Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Note : Holtek Semiconductor, Inc. is my mouse Also found this in dmesg : [ 292.597380] usb 1-1.4: new full-speed USB device number 5 using ehci-pci [ 293.941408] usb 1-1.4: New USB device found, idVendor=04d9, idProduct=a0ac [ 293.941413] usb 1-1.4: New USB device strings: Mfr=1, Product=2, SerialNumber=0 [ 293.941416] usb 1-1.4: Product: USB Gaming Mouse [ 293.941418] usb 1-1.4: Manufacturer: E-Signal [ 294.241702] input: E-Signal USB Gaming Mouse as /devices/pci:00/:00:1a.0/usb1/1-1/1-1.4/1-1.4:1.0/0003:04D9:A0AC.0004/input/input16 [ 294.242160] hid-generic 0003:04D9:A0AC.
[Touch-packages] [Bug 1581270] Re: Hybrid Graphics: [drm:si_resume [radeon]] *ERROR* si startup failed on resume
Thank you for reporting this bug to Ubuntu. Ubuntu 16.04 (xenial) reached end of standard support in April 2021: https://wiki.ubuntu.com/Releases If you would like to continue with free support then please update to a newer Ubuntu version and tell us if the problem still occurs. If you would like to continue with Ubuntu 16.04 then there is a paid support option detailed at https://www.ubuntu.com/esm ** Changed in: xorg (Ubuntu) Status: Confirmed => Won't Fix -- 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/1581270 Title: Hybrid Graphics: [drm:si_resume [radeon]] *ERROR* si startup failed on resume Status in xorg package in Ubuntu: Won't Fix Bug description: dmesg shows issues with being able to use the discrete graphics card (relevant dmesg lines attached). Grub does pass "radeon.modeset=1" but it doesn't seem to make a difference. If I pass both "radeon.modeset=1" and "radeon.startpm=1"to the kernel, then it does not error (except for the VCE error -110, which is probably harmless). Running `DRI_PRIME=1 glxgears`: - with "radeon.modeset=1" and "radeon.startpm=1", no error but only a black window with a visible top bar. - with just "radeon.modeset=1", error (attached as 'glxgears'). Results are similar on Ubuntu GNOME 16.04, except with "radeon.modeset=1" and "radeon.startpm=1" set. It works, but lots of screen tearing. Attached are relevant dmesg lines, grep'd with 'drm'. I'll also be attaching entire contents of dmesg, /var/log/syslog, etc., but TLDR: [ 22.916285] [drm] ring test on 0 succeeded in 2 usecs [ 22.916289] [drm] ring test on 1 succeeded in 1 usecs [ 22.916292] [drm] ring test on 2 succeeded in 1 usecs [ 22.916299] [drm] ring test on 3 succeeded in 3 usecs [ 22.916304] [drm] ring test on 4 succeeded in 3 usecs [ 23.092271] [drm] ring test on 5 succeeded in 2 usecs [ 23.092276] [drm] UVD initialized successfully. [ 23.092311] [drm] ib test on ring 0 succeeded in 0 usecs [ 23.092349] [drm] ib test on ring 1 succeeded in 0 usecs [ 23.092375] [drm] ib test on ring 2 succeeded in 0 usecs [ 23.092392] [drm] ib test on ring 3 succeeded in 0 usecs [ 23.092407] [drm] ib test on ring 4 succeeded in 0 usecs [ 33.241928] [drm:uvd_v1_0_ib_test [radeon]] *ERROR* radeon: fence wait failed (-35). [ 33.241948] [drm:radeon_ib_ring_tests [radeon]] *ERROR* radeon: failed testing IB on ring 5 (-35). lsb_release -rd: Description: Ubuntu 16.04 LTS Release: 16.04 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-22.39-generic 4.4.8 Uname: Linux 4.4.0-22-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2 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 CurrentDesktop: Unity Date: Thu May 12 20:43:03 2016 DistUpgraded: Fresh install DistroCodename: xenial 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: Samsung Electronics Co Ltd 3rd Gen Core processor Graphics Controller [144d:c0e6] Subsystem: Samsung Electronics Co Ltd Mars [Radeon HD 8670A/8670M/8750M] [144d:c0e6] InstallationDate: Installed on 2016-05-13 (0 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) MachineType: SAMSUNG ELECTRONICS CO., LTD. 870Z5E/880Z5E/680Z5E ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-22-generic.efi.signed root=UUID=644ba363-51c7-419c-8544-2ff7be960f21 ro quiet splash radeon.modeset=1 vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/21/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P05ADH.017.140421.SH dmi.board.asset.tag: No Asset Tag dmi.board.name: NP680Z5E-X01US dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.board.version: SEC_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.:bvrP05ADH.017.140421.SH:bd04/21/2014:svnSAMSUNGELECTRONICSCO.,LTD.:pn870Z5E/880Z5E/680Z5E:pvrP05ADH:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNP680Z5E-X01US:rvrSEC_SW_REVISION_1234567890ABCD:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvrN/A: dmi.product.name: 870Z5E/880Z5E/680Z5E dmi.product.version: P05ADH dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD. version.compiz: compiz 1:0.9.12.2+16.04.20160415-0ubuntu1 version.ia32-libs: ia32-libs N
[Touch-packages] [Bug 1929371] Re: [SRU] there is always a "Rear Microphone - Built-in Audio" option on the input device list even if the microphone is unplugged
Incomplete due to blank Bug Description. ** Changed in: pulseaudio (Ubuntu) Status: New => Incomplete -- 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/1929371 Title: [SRU] there is always a "Rear Microphone - Built-in Audio" option on the input device list even if the microphone is unplugged Status in OEM Priority Project: In Progress Status in pulseaudio package in Ubuntu: Incomplete Bug description: [Impact] [Fix] [Test] [Where problems could occur] To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1929371/+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
