[Touch-packages] [Bug 1926934] Re: gdb batch calls time out on armhf
** Tags added: ftbfs -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gdb in Ubuntu. https://bugs.launchpad.net/bugs/1926934 Title: gdb batch calls time out on armhf Status in gdb: Confirmed Status in gdb package in Ubuntu: New Bug description: seen when trying to build the gcc-10, or gcc-snapshot packages. A lot of tests in the guality test suite time out after 300 seconds (the default dejagnu timeout). These tests, like pr36728-1.c run ok on other architectures (and fail), but timeout on armhf. Seen in impish with gcc-10 and gcc-snapshot. Trying to run the gdb 10.2 tests on both hirsute and impish, I see a lot of timeouts as well. To manage notifications about this bug go to: https://bugs.launchpad.net/gdb/+bug/1926934/+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 1927161] Re: dpkg-source: error: diff 'openssl/debian/patches/pr12272.patch' patches files multiple times; split the diff in multiple files or merge the hunks into a single one
The attachment "debdiff for openssl on groovy" seems to be a debdiff. The ubuntu-sponsors team has been subscribed to the bug report so that they can review and hopefully sponsor the debdiff. If the attachment isn't a patch, please remove the "patch" flag from the attachment, remove the "patch" tag, and if you are member of the ~ubuntu-sponsors, unsubscribe the team. [This is an automated message performed by a Launchpad user owned by ~brian-murray, for any issue please contact him.] ** Tags added: patch -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssl in Ubuntu. https://bugs.launchpad.net/bugs/1927161 Title: dpkg-source: error: diff 'openssl/debian/patches/pr12272.patch' patches files multiple times; split the diff in multiple files or merge the hunks into a single one Status in openssl package in Ubuntu: In Progress Status in openssl source package in Groovy: In Progress Status in openssl source package in Hirsute: In Progress Status in openssl source package in Impish: In Progress Bug description: [impact] openssl doesn't build source properly because of a badly-constructed patch [test case] $ pull-lp-source openssl groovy ... $ cd openssl-1.1.1f/ $ quilt pop -a ... $ dpkg-buildpackage -d -S dpkg-buildpackage: info: source package openssl dpkg-buildpackage: info: source version 1.1.1f-1ubuntu4.3 dpkg-buildpackage: info: source distribution groovy-security dpkg-buildpackage: info: source changed by Marc Deslauriers dpkg-source --before-build . dpkg-source: warning: can't parse dependency perl:native dpkg-source: error: diff 'openssl-1.1.1f/debian/patches/pr12272.patch' patches files multiple times; split the diff in multiple files or merge the hunks into a single one dpkg-buildpackage: error: dpkg-source --before-build . subprocess returned exit status 25 Test builds are available in the following ppa: https://launchpad.net/~mruffell/+archive/ubuntu/lp1927161-test [regression potential] any regression would likely cause a failed build or would affect the functionality that patch pr12272 was added for, which is adding support for Intel CET [scope] this is needed only for g and later this is caused by the bad patch 'pr12272.patch' which is only included in g/h/i, so this does not apply to f or earlier [other info] note that if the patches are applied, this bug is bypassed; i.e. if 'quilt pop -a' is removed from the test case above, the bug doesn't reproduce. this is only a problem when the patches aren't already applied and dpkg-buildpackage needs to call dpkg-source to apply the patches. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1927161/+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 1927082] Re: Mouse and keyboard bug
Next time the problem happens, please: 1. Reboot. 2. Open a Terminal and run: journalctl -b-1 > prevboot.txt 3. Attach the resulting text file here. ** Package changed: xorg (Ubuntu) => xorg-server (Ubuntu) ** Changed in: xorg-server (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1927082 Title: Mouse and keyboard bug Status in xorg-server package in Ubuntu: Incomplete Bug description: My mouse and keyboard stop working after while. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3.1 ProcVersionSignature: Ubuntu 4.15.0-142.146~16.04.1-generic 4.15.18 Uname: Linux 4.15.0-142-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia .proc.driver.nvidia.gpus..03.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:03:00.0' .proc.driver.nvidia.gpus..04.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:04:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 384.130 Wed Mar 21 03:37:26 PDT 2018 GCC version: gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.12) .proc.driver.nvidia.warnings.fbdev: Your system is not currently configured to drive a VGA console on the primary VGA device. The NVIDIA Linux graphics driver requires the use of a text-mode VGA console. Use of other console drivers including, but not limited to, vesafb, may result in corruption and stability problems, and is not supported. .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.30 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: Tue May 4 12:58:52 2021 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GP106 [GeForce GTX 1060 3GB] [10de:1c02] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] Device [1462:3287] NVIDIA Corporation GP106 [GeForce GTX 1060 3GB] [10de:1c02] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] Device [1462:3287] InstallationDate: Installed on 2018-01-20 (1199 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) MachineType: MSI MS-7885 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-142-generic root=UUID=2d0f054b-beb1-4182-9871-2d8ea219b402 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/15/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.D0 dmi.board.asset.tag: Default string dmi.board.name: X99A SLI PLUS(MS-7885) dmi.board.vendor: MSI dmi.board.version: 1.0 dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.D0:bd07/15/2016:svnMSI:pnMS-7885:pvr1.0:rvnMSI:rnX99ASLIPLUS(MS-7885):rvr1.0:cvnMSI:ct3:cvr1.0: dmi.product.family: Default string dmi.product.name: MS-7885 dmi.product.version: 1.0 dmi.sys.vendor: MSI version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.91-2~16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~16.04.1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A 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: Tue May 4 12:43:15 2021 xserver.configfile: default xserver.devices: inputPower Button KEYBOARD, id 6 inputPower Button KEYBOARD, id 7 inputKYE SYSTEMS CORP. Wired Mouse MOUSE, id 8 inputSEM USB Keyboard KEYBOARD, id 9 inputSEM USB Keyboard KEYBOARD, id 10 xserver.errors: [drm] Failed to open DRM device for (null): -22 xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.19.6-1ubuntu4.1~16.04.6 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1927082/+subscriptions -- Mailing list:
[Touch-packages] [Bug 1576559] Re: Refused to switch profile to headset_head_unit: Not connected
Whenever PulseAudio 15 is ready. I don't know when that is but it can be found at https://gitlab.freedesktop.org/pulseaudio -- 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/1576559 Title: Refused to switch profile to headset_head_unit: Not connected Status in PulseAudio: Unknown Status in pulseaudio package in Ubuntu: Fix Committed Bug description: I'm trying to connect a bluetooth-speaker-with-microphone (Mi Bluetooth Speaker) to Ubuntu. It works well as an A2DP sync, but can't use it as a headset with microphone. The device doesn't list in the "Input Devices" by default, and using the sound settings to change the profile of the device to HSP/HFP results in this log message: W: [pulseaudio] module-bluez5-device.c: Refused to switch profile to headset_head_unit: Not connected I'm running Ubuntu 16.04 LTS. I did an upgrade from Ubuntu 15.10. pulseaudio: Installed: 1:8.0-0ubuntu3 bluez: Installed: 5.37-0ubuntu5 To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/1576559/+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 1883534] Re: Screen flickering
*** This bug is a duplicate of bug 1853094 *** https://bugs.launchpad.net/bugs/1853094 Jorge, Wayland should never have such problems. If it does then you should open a NEW bug by running: ubuntu-bug xorg -- 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/1883534 Title: Screen flickering Status in xorg package in Ubuntu: Confirmed Bug description: To whom it may concern, As stated I have screen flickerings (see lightning like flickering on photo attached for portrait screen, for horizontal screen I also have screen flickering on the upper part but hard to catch in a photo) on freshly installed Ubuntu 20.04 LTS. I have tried this: https://askubuntu.com/questions/1231441/ubuntu-screen-flickering and this: https://learnubuntumate.weebly.com/screen-tearing-on-intel- graphics.html without success. I have also seen some other people mentioning screen flickering on ubuntu 20.04 here: https://www.reddit.com/r/Ubuntu/comments/fvk536/anyone_else_noticing_window_flickering_on_ubuntu/ without solution. I also know that it is very unlikely hardware problem because my screens were displaying well on archlinux. I think my graphic card info are already included in the report but just in case: Intel Corporation UHD Graphics 630. Might be intel driver problems ? Could you help me on this please ? Best regards, Jeremy ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41 Uname: Linux 5.4.0-37-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Jun 15 15:05:27 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation UHD Graphics 630 (Desktop) [8086:3e92] (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. UHD Graphics 630 (Desktop) [1043:8694] InstallationDate: Installed on 2020-06-12 (2 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 046a:0023 Cherry GmbH Keyboard Bus 001 Device 003: ID 046d:c077 Logitech, Inc. M105 Optical Mouse Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/10p, 5000M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/16p, 480M |__ Port 9: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 1.5M |__ Port 9: Dev 2, If 1, Class=Human Interface Device, Driver=usbhid, 1.5M |__ Port 10: Dev 3, If 0, Class=Human Interface Device, Driver=usbhid, 1.5M MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-37-generic root=UUID=81cee77a-b529-4dac-9834-dc6d5ab2dc16 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/11/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0615 dmi.board.asset.tag: Default string dmi.board.name: PRIME Z370-P dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0615:bd04/11/2018:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEZ370-P:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1883534/+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 1926855] Re: Raspberry Pi: desktop forgets audio device selected after reboot
** Tags added: hirsute raspi -- 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/1926855 Title: Raspberry Pi: desktop forgets audio device selected after reboot Status in pulseaudio package in Ubuntu: New Bug description: Hirsute 21.04 Raspberry Pi on Pi 4B 4GB Audio output device defaults to 'Headphones - Built-in Audio': this is the AV jack. Settings also lists 'Digital Output (S/PDIF) - Built-in Audio' which is HDMI, and I can get audio from it correctly. However, this setting is not saved, and on reboot it defaults back to 'Headphones - Built-in Audio'. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1926855/+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 1927161] Re: dpkg-source: error: diff 'openssl/debian/patches/pr12272.patch' patches files multiple times; split the diff in multiple files or merge the hunks into a single one
** Description changed: [impact] openssl doesn't build source properly because of a badly-constructed patch [test case] $ pull-lp-source openssl groovy ... $ cd openssl-1.1.1f/ $ quilt pop -a ... $ dpkg-buildpackage -d -S dpkg-buildpackage: info: source package openssl dpkg-buildpackage: info: source version 1.1.1f-1ubuntu4.3 dpkg-buildpackage: info: source distribution groovy-security dpkg-buildpackage: info: source changed by Marc Deslauriers dpkg-source --before-build . dpkg-source: warning: can't parse dependency perl:native dpkg-source: error: diff 'openssl-1.1.1f/debian/patches/pr12272.patch' patches files multiple times; split the diff in multiple files or merge the hunks into a single one dpkg-buildpackage: error: dpkg-source --before-build . subprocess returned exit status 25 + Test builds are available in the following ppa: + + https://launchpad.net/~mruffell/+archive/ubuntu/lp1927161-test + [regression potential] any regression would likely cause a failed build or would affect the functionality that patch pr12272 was added for, which is adding support for Intel CET [scope] this is needed only for g and later this is caused by the bad patch 'pr12272.patch' which is only included in g/h/i, so this does not apply to f or earlier [other info] note that if the patches are applied, this bug is bypassed; i.e. if 'quilt pop -a' is removed from the test case above, the bug doesn't reproduce. this is only a problem when the patches aren't already applied and dpkg-buildpackage needs to call dpkg-source to apply the patches. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssl in Ubuntu. https://bugs.launchpad.net/bugs/1927161 Title: dpkg-source: error: diff 'openssl/debian/patches/pr12272.patch' patches files multiple times; split the diff in multiple files or merge the hunks into a single one Status in openssl package in Ubuntu: In Progress Status in openssl source package in Groovy: In Progress Status in openssl source package in Hirsute: In Progress Status in openssl source package in Impish: In Progress Bug description: [impact] openssl doesn't build source properly because of a badly-constructed patch [test case] $ pull-lp-source openssl groovy ... $ cd openssl-1.1.1f/ $ quilt pop -a ... $ dpkg-buildpackage -d -S dpkg-buildpackage: info: source package openssl dpkg-buildpackage: info: source version 1.1.1f-1ubuntu4.3 dpkg-buildpackage: info: source distribution groovy-security dpkg-buildpackage: info: source changed by Marc Deslauriers dpkg-source --before-build . dpkg-source: warning: can't parse dependency perl:native dpkg-source: error: diff 'openssl-1.1.1f/debian/patches/pr12272.patch' patches files multiple times; split the diff in multiple files or merge the hunks into a single one dpkg-buildpackage: error: dpkg-source --before-build . subprocess returned exit status 25 Test builds are available in the following ppa: https://launchpad.net/~mruffell/+archive/ubuntu/lp1927161-test [regression potential] any regression would likely cause a failed build or would affect the functionality that patch pr12272 was added for, which is adding support for Intel CET [scope] this is needed only for g and later this is caused by the bad patch 'pr12272.patch' which is only included in g/h/i, so this does not apply to f or earlier [other info] note that if the patches are applied, this bug is bypassed; i.e. if 'quilt pop -a' is removed from the test case above, the bug doesn't reproduce. this is only a problem when the patches aren't already applied and dpkg-buildpackage needs to call dpkg-source to apply the patches. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1927161/+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 1927161] Re: dpkg-source: error: diff 'openssl/debian/patches/pr12272.patch' patches files multiple times; split the diff in multiple files or merge the hunks into a single one
Attached is a V2 for hirsute which correctly has d/p/ in the debian/changelog. ** Patch added: "debdiff for openssl on hirsute" https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1927161/+attachment/5494814/+files/lp1927161_hirsute_v2.debdiff -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssl in Ubuntu. https://bugs.launchpad.net/bugs/1927161 Title: dpkg-source: error: diff 'openssl/debian/patches/pr12272.patch' patches files multiple times; split the diff in multiple files or merge the hunks into a single one Status in openssl package in Ubuntu: In Progress Status in openssl source package in Groovy: In Progress Status in openssl source package in Hirsute: In Progress Status in openssl source package in Impish: In Progress Bug description: [impact] openssl doesn't build source properly because of a badly-constructed patch [test case] $ pull-lp-source openssl groovy ... $ cd openssl-1.1.1f/ $ quilt pop -a ... $ dpkg-buildpackage -d -S dpkg-buildpackage: info: source package openssl dpkg-buildpackage: info: source version 1.1.1f-1ubuntu4.3 dpkg-buildpackage: info: source distribution groovy-security dpkg-buildpackage: info: source changed by Marc Deslauriers dpkg-source --before-build . dpkg-source: warning: can't parse dependency perl:native dpkg-source: error: diff 'openssl-1.1.1f/debian/patches/pr12272.patch' patches files multiple times; split the diff in multiple files or merge the hunks into a single one dpkg-buildpackage: error: dpkg-source --before-build . subprocess returned exit status 25 [regression potential] any regression would likely cause a failed build or would affect the functionality that patch pr12272 was added for, which is adding support for Intel CET [scope] this is needed only for g and later this is caused by the bad patch 'pr12272.patch' which is only included in g/h/i, so this does not apply to f or earlier [other info] note that if the patches are applied, this bug is bypassed; i.e. if 'quilt pop -a' is removed from the test case above, the bug doesn't reproduce. this is only a problem when the patches aren't already applied and dpkg-buildpackage needs to call dpkg-source to apply the patches. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1927161/+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 1927161] Re: dpkg-source: error: diff 'openssl/debian/patches/pr12272.patch' patches files multiple times; split the diff in multiple files or merge the hunks into a single one
Attached is a V2 for impish which correctly has d/p/ in the debian/changelog. ** Patch added: "debdiff for openssl on impish" https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1927161/+attachment/5494813/+files/lp1927161_impish_v2.debdiff ** Patch removed: "debdiff for openssl on hirsute" https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1927161/+attachment/5494811/+files/lp1927161_hirsute.debdiff -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssl in Ubuntu. https://bugs.launchpad.net/bugs/1927161 Title: dpkg-source: error: diff 'openssl/debian/patches/pr12272.patch' patches files multiple times; split the diff in multiple files or merge the hunks into a single one Status in openssl package in Ubuntu: In Progress Status in openssl source package in Groovy: In Progress Status in openssl source package in Hirsute: In Progress Status in openssl source package in Impish: In Progress Bug description: [impact] openssl doesn't build source properly because of a badly-constructed patch [test case] $ pull-lp-source openssl groovy ... $ cd openssl-1.1.1f/ $ quilt pop -a ... $ dpkg-buildpackage -d -S dpkg-buildpackage: info: source package openssl dpkg-buildpackage: info: source version 1.1.1f-1ubuntu4.3 dpkg-buildpackage: info: source distribution groovy-security dpkg-buildpackage: info: source changed by Marc Deslauriers dpkg-source --before-build . dpkg-source: warning: can't parse dependency perl:native dpkg-source: error: diff 'openssl-1.1.1f/debian/patches/pr12272.patch' patches files multiple times; split the diff in multiple files or merge the hunks into a single one dpkg-buildpackage: error: dpkg-source --before-build . subprocess returned exit status 25 [regression potential] any regression would likely cause a failed build or would affect the functionality that patch pr12272 was added for, which is adding support for Intel CET [scope] this is needed only for g and later this is caused by the bad patch 'pr12272.patch' which is only included in g/h/i, so this does not apply to f or earlier [other info] note that if the patches are applied, this bug is bypassed; i.e. if 'quilt pop -a' is removed from the test case above, the bug doesn't reproduce. this is only a problem when the patches aren't already applied and dpkg-buildpackage needs to call dpkg-source to apply the patches. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1927161/+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 1927161] Re: dpkg-source: error: diff 'openssl/debian/patches/pr12272.patch' patches files multiple times; split the diff in multiple files or merge the hunks into a single one
Attached is a debdiff for openssl on groovy, which fixes this issue, and also bug 1926254 ** Patch added: "debdiff for openssl on groovy" https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1927161/+attachment/5494812/+files/lp1926254_lp1927161_groovy.debdiff ** Patch removed: "debdiff for openssl on impish" https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1927161/+attachment/5494810/+files/lp1927161_impish.debdiff -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssl in Ubuntu. https://bugs.launchpad.net/bugs/1927161 Title: dpkg-source: error: diff 'openssl/debian/patches/pr12272.patch' patches files multiple times; split the diff in multiple files or merge the hunks into a single one Status in openssl package in Ubuntu: In Progress Status in openssl source package in Groovy: In Progress Status in openssl source package in Hirsute: In Progress Status in openssl source package in Impish: In Progress Bug description: [impact] openssl doesn't build source properly because of a badly-constructed patch [test case] $ pull-lp-source openssl groovy ... $ cd openssl-1.1.1f/ $ quilt pop -a ... $ dpkg-buildpackage -d -S dpkg-buildpackage: info: source package openssl dpkg-buildpackage: info: source version 1.1.1f-1ubuntu4.3 dpkg-buildpackage: info: source distribution groovy-security dpkg-buildpackage: info: source changed by Marc Deslauriers dpkg-source --before-build . dpkg-source: warning: can't parse dependency perl:native dpkg-source: error: diff 'openssl-1.1.1f/debian/patches/pr12272.patch' patches files multiple times; split the diff in multiple files or merge the hunks into a single one dpkg-buildpackage: error: dpkg-source --before-build . subprocess returned exit status 25 [regression potential] any regression would likely cause a failed build or would affect the functionality that patch pr12272 was added for, which is adding support for Intel CET [scope] this is needed only for g and later this is caused by the bad patch 'pr12272.patch' which is only included in g/h/i, so this does not apply to f or earlier [other info] note that if the patches are applied, this bug is bypassed; i.e. if 'quilt pop -a' is removed from the test case above, the bug doesn't reproduce. this is only a problem when the patches aren't already applied and dpkg-buildpackage needs to call dpkg-source to apply the patches. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1927161/+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 1927161] Re: dpkg-source: error: diff 'openssl/debian/patches/pr12272.patch' patches files multiple times; split the diff in multiple files or merge the hunks into a single one
Attached is a debdiff for openssl on hirsute which fixes this problem. ** Patch added: "debdiff for openssl on hirsute" https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1927161/+attachment/5494811/+files/lp1927161_hirsute.debdiff -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssl in Ubuntu. https://bugs.launchpad.net/bugs/1927161 Title: dpkg-source: error: diff 'openssl/debian/patches/pr12272.patch' patches files multiple times; split the diff in multiple files or merge the hunks into a single one Status in openssl package in Ubuntu: In Progress Status in openssl source package in Groovy: In Progress Status in openssl source package in Hirsute: In Progress Status in openssl source package in Impish: In Progress Bug description: [impact] openssl doesn't build source properly because of a badly-constructed patch [test case] $ pull-lp-source openssl groovy ... $ cd openssl-1.1.1f/ $ quilt pop -a ... $ dpkg-buildpackage -d -S dpkg-buildpackage: info: source package openssl dpkg-buildpackage: info: source version 1.1.1f-1ubuntu4.3 dpkg-buildpackage: info: source distribution groovy-security dpkg-buildpackage: info: source changed by Marc Deslauriers dpkg-source --before-build . dpkg-source: warning: can't parse dependency perl:native dpkg-source: error: diff 'openssl-1.1.1f/debian/patches/pr12272.patch' patches files multiple times; split the diff in multiple files or merge the hunks into a single one dpkg-buildpackage: error: dpkg-source --before-build . subprocess returned exit status 25 [regression potential] any regression would likely cause a failed build or would affect the functionality that patch pr12272 was added for, which is adding support for Intel CET [scope] this is needed only for g and later this is caused by the bad patch 'pr12272.patch' which is only included in g/h/i, so this does not apply to f or earlier [other info] note that if the patches are applied, this bug is bypassed; i.e. if 'quilt pop -a' is removed from the test case above, the bug doesn't reproduce. this is only a problem when the patches aren't already applied and dpkg-buildpackage needs to call dpkg-source to apply the patches. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1927161/+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 1927161] Re: dpkg-source: error: diff 'openssl/debian/patches/pr12272.patch' patches files multiple times; split the diff in multiple files or merge the hunks into a single one
Attached is a debdiff for impish which fixes this problem. ** Patch added: "debdiff for openssl on impish" https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1927161/+attachment/5494810/+files/lp1927161_impish.debdiff -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssl in Ubuntu. https://bugs.launchpad.net/bugs/1927161 Title: dpkg-source: error: diff 'openssl/debian/patches/pr12272.patch' patches files multiple times; split the diff in multiple files or merge the hunks into a single one Status in openssl package in Ubuntu: In Progress Status in openssl source package in Groovy: In Progress Status in openssl source package in Hirsute: In Progress Status in openssl source package in Impish: In Progress Bug description: [impact] openssl doesn't build source properly because of a badly-constructed patch [test case] $ pull-lp-source openssl groovy ... $ cd openssl-1.1.1f/ $ quilt pop -a ... $ dpkg-buildpackage -d -S dpkg-buildpackage: info: source package openssl dpkg-buildpackage: info: source version 1.1.1f-1ubuntu4.3 dpkg-buildpackage: info: source distribution groovy-security dpkg-buildpackage: info: source changed by Marc Deslauriers dpkg-source --before-build . dpkg-source: warning: can't parse dependency perl:native dpkg-source: error: diff 'openssl-1.1.1f/debian/patches/pr12272.patch' patches files multiple times; split the diff in multiple files or merge the hunks into a single one dpkg-buildpackage: error: dpkg-source --before-build . subprocess returned exit status 25 [regression potential] any regression would likely cause a failed build or would affect the functionality that patch pr12272 was added for, which is adding support for Intel CET [scope] this is needed only for g and later this is caused by the bad patch 'pr12272.patch' which is only included in g/h/i, so this does not apply to f or earlier [other info] note that if the patches are applied, this bug is bypassed; i.e. if 'quilt pop -a' is removed from the test case above, the bug doesn't reproduce. this is only a problem when the patches aren't already applied and dpkg-buildpackage needs to call dpkg-source to apply the patches. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1927161/+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 1927161] Re: dpkg-source: error: diff 'openssl/debian/patches/pr12272.patch' patches files multiple times; split the diff in multiple files or merge the hunks into a single one
I split 'pr12272.patch' into one file per commit, and I did a diff to ensure that there is no changes to the code: https://paste.ubuntu.com/p/zDqqXmsM8c/ When using these split up patches "dpkg-buildpackage -d -S" completes successfully. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssl in Ubuntu. https://bugs.launchpad.net/bugs/1927161 Title: dpkg-source: error: diff 'openssl/debian/patches/pr12272.patch' patches files multiple times; split the diff in multiple files or merge the hunks into a single one Status in openssl package in Ubuntu: In Progress Status in openssl source package in Groovy: In Progress Status in openssl source package in Hirsute: In Progress Status in openssl source package in Impish: In Progress Bug description: [impact] openssl doesn't build source properly because of a badly-constructed patch [test case] $ pull-lp-source openssl groovy ... $ cd openssl-1.1.1f/ $ quilt pop -a ... $ dpkg-buildpackage -d -S dpkg-buildpackage: info: source package openssl dpkg-buildpackage: info: source version 1.1.1f-1ubuntu4.3 dpkg-buildpackage: info: source distribution groovy-security dpkg-buildpackage: info: source changed by Marc Deslauriers dpkg-source --before-build . dpkg-source: warning: can't parse dependency perl:native dpkg-source: error: diff 'openssl-1.1.1f/debian/patches/pr12272.patch' patches files multiple times; split the diff in multiple files or merge the hunks into a single one dpkg-buildpackage: error: dpkg-source --before-build . subprocess returned exit status 25 [regression potential] any regression would likely cause a failed build or would affect the functionality that patch pr12272 was added for, which is adding support for Intel CET [scope] this is needed only for g and later this is caused by the bad patch 'pr12272.patch' which is only included in g/h/i, so this does not apply to f or earlier [other info] note that if the patches are applied, this bug is bypassed; i.e. if 'quilt pop -a' is removed from the test case above, the bug doesn't reproduce. this is only a problem when the patches aren't already applied and dpkg-buildpackage needs to call dpkg-source to apply the patches. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1927161/+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 1927161] Re: dpkg-source: error: diff 'openssl/debian/patches/pr12272.patch' patches files multiple times; split the diff in multiple files or merge the hunks into a single one
** Changed in: openssl (Ubuntu Groovy) Status: New => In Progress ** Changed in: openssl (Ubuntu Hirsute) Status: New => In Progress ** Changed in: openssl (Ubuntu Impish) Status: New => In Progress ** Changed in: openssl (Ubuntu Groovy) Assignee: (unassigned) => Matthew Ruffell (mruffell) ** Changed in: openssl (Ubuntu Hirsute) Assignee: (unassigned) => Matthew Ruffell (mruffell) ** Changed in: openssl (Ubuntu Impish) Assignee: (unassigned) => Matthew Ruffell (mruffell) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssl in Ubuntu. https://bugs.launchpad.net/bugs/1927161 Title: dpkg-source: error: diff 'openssl/debian/patches/pr12272.patch' patches files multiple times; split the diff in multiple files or merge the hunks into a single one Status in openssl package in Ubuntu: In Progress Status in openssl source package in Groovy: In Progress Status in openssl source package in Hirsute: In Progress Status in openssl source package in Impish: In Progress Bug description: [impact] openssl doesn't build source properly because of a badly-constructed patch [test case] $ pull-lp-source openssl groovy ... $ cd openssl-1.1.1f/ $ quilt pop -a ... $ dpkg-buildpackage -d -S dpkg-buildpackage: info: source package openssl dpkg-buildpackage: info: source version 1.1.1f-1ubuntu4.3 dpkg-buildpackage: info: source distribution groovy-security dpkg-buildpackage: info: source changed by Marc Deslauriers dpkg-source --before-build . dpkg-source: warning: can't parse dependency perl:native dpkg-source: error: diff 'openssl-1.1.1f/debian/patches/pr12272.patch' patches files multiple times; split the diff in multiple files or merge the hunks into a single one dpkg-buildpackage: error: dpkg-source --before-build . subprocess returned exit status 25 [regression potential] any regression would likely cause a failed build or would affect the functionality that patch pr12272 was added for, which is adding support for Intel CET [scope] this is needed only for g and later this is caused by the bad patch 'pr12272.patch' which is only included in g/h/i, so this does not apply to f or earlier [other info] note that if the patches are applied, this bug is bypassed; i.e. if 'quilt pop -a' is removed from the test case above, the bug doesn't reproduce. this is only a problem when the patches aren't already applied and dpkg-buildpackage needs to call dpkg-source to apply the patches. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1927161/+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 1911637] Re: Another app is currently holding the xtables lock
This has been reported on the ansible module side as well as it impacts the ability to configure ufw on Ubuntu 20.04.02 LTS servers. ufw is essentially unusable because of this bug. https://github.com/ansible-collections/community.general/issues/2336 https://github.com/ansible-collections/community.general/issues/2452 ** Bug watch added: github.com/ansible-collections/community.general/issues #2336 https://github.com/ansible-collections/community.general/issues/2336 ** Bug watch added: github.com/ansible-collections/community.general/issues #2452 https://github.com/ansible-collections/community.general/issues/2452 ** Also affects: ufw (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ufw in Ubuntu. https://bugs.launchpad.net/bugs/1911637 Title: Another app is currently holding the xtables lock Status in ufw: New Status in ufw package in Ubuntu: New Status in ufw package in Debian: New Bug description: Version: ufw 0.36 (via Debian buster 0.36-1 deb-package) I'm using ufw together with fail2ban, and often I get an error while fail2ban is trying to ban an ip: ``` ERROR: initcaps [Errno 2] Another app is currently holding the xtables lock. Perhaps you want to use the -w option? ``` it seems that in utils.py, get_netfilter_capabilities(...) iptables is called without "-w" flag to wait for the table lock perhaps the checks should include this parameter to avoid leaving temporary tables behind (and breaking fail2ban, but thats a different story ...)? To manage notifications about this bug go to: https://bugs.launchpad.net/ufw/+bug/1911637/+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 1927163] [NEW] Support time status is not correctly if we use ubuntu-support-status command in terminal
Public bug reported: Dear Launchpad Community, I used ubuntu-support-status command on my Ubuntu 18.04.5 system and I can see that these packages are not supported: gstreamer1.0-gtk3 libbrotli1 libwoff1 Like we know these packages are from main repositore so this should have support to 2023 year so this is why I report this like bug. Package: gstreamer1.0-gtk3 Version: 1.14.5-0ubuntu1~18.04.2 Package: libbrotli1 Version: 1.0.3-1ubuntu1.3 Package: libwoff1 Version: 1.0.2-1build0.1 lsb_release -a Distributor ID: Ubuntu Description:Ubuntu 18.04.5 LTS Release:18.04 Codename: bionic I hope that you fix it or explain me why these packages are not supported. Yours faithfully, Piotr ** Affects: brotli (Ubuntu) Importance: Undecided Status: New ** Affects: gst-plugins-good1.0 (Ubuntu) Importance: Undecided Status: New ** Affects: woff2 (Ubuntu) Importance: Undecided Status: New ** Also affects: woff2 (Ubuntu) Importance: Undecided Status: New ** Also affects: brotli (Ubuntu) Importance: Undecided Status: New ** No longer affects: brotli (Ubuntu) ** Also affects: brotli (Ubuntu) Importance: Undecided Status: New ** Summary changed: - Support time status is not corrected if we use ubuntus-support-status + Support time status is not corrected if we use ubuntu-support-status command in terminal ** Summary changed: - Support time status is not corrected if we use ubuntu-support-status command in terminal + Support time status is not correctly if we use ubuntu-support-status command in terminal ** Description changed: Dear Launchpad Comminity, I used ubuntu-support-status command on my Ubuntu 18.04.5 system and I can see that these packages are not supported: gstreamer1.0-gtk3 libbrotli1 libwoff1 Like we know these packages are from main repositore so this should have support to 2023 year so this is why I report this like bug. - Package: gstreamer1.0-gtk3 Version: 1.14.5-0ubuntu1~18.04.2 + + Package: libbrotli1 + Version: 1.0.3-1ubuntu1.3 + + Package: libwoff1 + Version: 1.0.2-1build0.1 lsb_release -a Distributor ID: Ubuntu Description: Ubuntu 18.04.5 LTS Release: 18.04 Codename: bionic - - I hope that you fix it or explain me why these packages are not supported. + I hope that you fix it or explain me why these packages are not + supported. Yours faithfully, Piotr ** Description changed: - Dear Launchpad Comminity, + Dear Launchpad Community, I used ubuntu-support-status command on my Ubuntu 18.04.5 system and I can see that these packages are not supported: gstreamer1.0-gtk3 libbrotli1 libwoff1 Like we know these packages are from main repositore so this should have support to 2023 year so this is why I report this like bug. Package: gstreamer1.0-gtk3 Version: 1.14.5-0ubuntu1~18.04.2 Package: libbrotli1 Version: 1.0.3-1ubuntu1.3 Package: libwoff1 Version: 1.0.2-1build0.1 lsb_release -a Distributor ID: Ubuntu Description: Ubuntu 18.04.5 LTS Release: 18.04 Codename: bionic I hope that you fix it or explain me why these packages are not supported. Yours faithfully, Piotr -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gst-plugins-good1.0 in Ubuntu. https://bugs.launchpad.net/bugs/1927163 Title: Support time status is not correctly if we use ubuntu-support-status command in terminal Status in brotli package in Ubuntu: New Status in gst-plugins-good1.0 package in Ubuntu: New Status in woff2 package in Ubuntu: New Bug description: Dear Launchpad Community, I used ubuntu-support-status command on my Ubuntu 18.04.5 system and I can see that these packages are not supported: gstreamer1.0-gtk3 libbrotli1 libwoff1 Like we know these packages are from main repositore so this should have support to 2023 year so this is why I report this like bug. Package: gstreamer1.0-gtk3 Version: 1.14.5-0ubuntu1~18.04.2 Package: libbrotli1 Version: 1.0.3-1ubuntu1.3 Package: libwoff1 Version: 1.0.2-1build0.1 lsb_release -a Distributor ID: Ubuntu Description: Ubuntu 18.04.5 LTS Release: 18.04 Codename: bionic I hope that you fix it or explain me why these packages are not supported. Yours faithfully, Piotr To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/brotli/+bug/1927163/+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 1927063] Re: Terminal prompt got strangely replicated when resizing terminal horizontally
I can confirm this. I'm using Ubuntu 20.04.2 LTS and GNOME Terminal has the same issue. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bash in Ubuntu. https://bugs.launchpad.net/bugs/1927063 Title: Terminal prompt got strangely replicated when resizing terminal horizontally Status in bash package in Ubuntu: Confirmed Status in gnome-terminal package in Ubuntu: Confirmed Status in mate-terminal package in Ubuntu: Confirmed Status in tilix package in Ubuntu: Confirmed Status in vte2.91 package in Ubuntu: Confirmed Bug description: Steps to reproduce: 1. Have Ubuntu installed 2. Launch MATE Terminal 3. Navigate to some folder with long name - `cd /usr/share/doc/ayatana-indicator-application` 4. Resize terminal horizontally Expected results: * terminal shows the same "user@host:/usr/share/doc/ayatana-indicator-application$" with single occurrence Actual results: * terminal shows multiple occurrencies of "user@host:/usr/share/doc/ayatana-indicator-application$" (see attached screencast) ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: mate-terminal 1.24.1-1 ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 Uname: Linux 5.11.0-16-generic x86_64 ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: MATE Date: Tue May 4 10:54:59 2021 InstallationDate: Installed on 2021-04-23 (10 days ago) InstallationMedia: Ubuntu-MATE 21.04 "Hirsute Hippo" - Release amd64 (20210420) SourcePackage: mate-terminal UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bash/+bug/1927063/+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 1927063] Re: Terminal prompt got strangely replicated when resizing terminal horizontally
Disagree with 18.04 LTS (18.04.5) comment by @nrbrtx, considering gnome- terminal. Open gnome-terminal. Change directory to long name, from first character of username to last character "$" of directory summing 60, or 61+ characters. Give it best effort and utilize "clear" command. Utilize keyboard shortcut to escape from current command, "CTRL + C", twice. Utilize keyboard shortcut to adjust window, "ALT + F8", and reduce horizontal width from the RIGHT edge to 62 characters. Notice one line of history is gone. Continue and reduce horizontal width to 58 characters. Notice an unexpected character at beginning of last line of prompt. Continue to 57 characters. The whole path is no longer visible. Continue to 56 characters. Part of the path appears inside the cursor. Continue to 55 characters. Path is now obscured. Continue to 50 characters. Notice the obscured path is no longer present, but the path is not whole. Continue and reduce horizontal width to minimum (31) from the RIGHT edge with arrow keys. Utilize keyboard shortcut to escape from current command, "CTRL + C", twice. The tool to change horizontal width has been disabled and a ^C is made visible at the last prompt, escaping to a new prompt with full path. Utilize keyboard shortcut to adjust window, "ALT + F8", and increase horizontal width from the RIGHT edge to 60 characters or 61 characters. Notice the username is obscured. If performed with 60 character line, Continue to typical 80 characters. The first letter of the username is now repeated on the last line. If performed with 61 character line, first character of username is sometimes repeated on previous line. If performed with 61+ character line, multiples of path are seen as original bug reports. You can make more lines with path appear if iterating between width of 31 and 32 characters. My example is 62 characters: userna@userna:~/userna/usernamefolder/direct/foobars/foobars$ Results: userna@userna:~/userna/usernamefolder userna@userna:~/userna/usernamefolder/direct/foobars/foobars$ Either with fast keyboard strokes or slow, there are a number of errors in line feed and character removal when adjusting the terminal width. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bash in Ubuntu. https://bugs.launchpad.net/bugs/1927063 Title: Terminal prompt got strangely replicated when resizing terminal horizontally Status in bash package in Ubuntu: Confirmed Status in gnome-terminal package in Ubuntu: Confirmed Status in mate-terminal package in Ubuntu: Confirmed Status in tilix package in Ubuntu: Confirmed Status in vte2.91 package in Ubuntu: Confirmed Bug description: Steps to reproduce: 1. Have Ubuntu installed 2. Launch MATE Terminal 3. Navigate to some folder with long name - `cd /usr/share/doc/ayatana-indicator-application` 4. Resize terminal horizontally Expected results: * terminal shows the same "user@host:/usr/share/doc/ayatana-indicator-application$" with single occurrence Actual results: * terminal shows multiple occurrencies of "user@host:/usr/share/doc/ayatana-indicator-application$" (see attached screencast) ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: mate-terminal 1.24.1-1 ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 Uname: Linux 5.11.0-16-generic x86_64 ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: MATE Date: Tue May 4 10:54:59 2021 InstallationDate: Installed on 2021-04-23 (10 days ago) InstallationMedia: Ubuntu-MATE 21.04 "Hirsute Hippo" - Release amd64 (20210420) SourcePackage: mate-terminal UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bash/+bug/1927063/+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 1927063] Re: Terminal prompt got strangely replicated when resizing terminal horizontally
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: tilix (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bash in Ubuntu. https://bugs.launchpad.net/bugs/1927063 Title: Terminal prompt got strangely replicated when resizing terminal horizontally Status in bash package in Ubuntu: Confirmed Status in gnome-terminal package in Ubuntu: Confirmed Status in mate-terminal package in Ubuntu: Confirmed Status in tilix package in Ubuntu: Confirmed Status in vte2.91 package in Ubuntu: Confirmed Bug description: Steps to reproduce: 1. Have Ubuntu installed 2. Launch MATE Terminal 3. Navigate to some folder with long name - `cd /usr/share/doc/ayatana-indicator-application` 4. Resize terminal horizontally Expected results: * terminal shows the same "user@host:/usr/share/doc/ayatana-indicator-application$" with single occurrence Actual results: * terminal shows multiple occurrencies of "user@host:/usr/share/doc/ayatana-indicator-application$" (see attached screencast) ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: mate-terminal 1.24.1-1 ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 Uname: Linux 5.11.0-16-generic x86_64 ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: MATE Date: Tue May 4 10:54:59 2021 InstallationDate: Installed on 2021-04-23 (10 days ago) InstallationMedia: Ubuntu-MATE 21.04 "Hirsute Hippo" - Release amd64 (20210420) SourcePackage: mate-terminal UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bash/+bug/1927063/+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 1927063] Re: Terminal prompt got strangely replicated when resizing terminal horizontally
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gnome-terminal (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bash in Ubuntu. https://bugs.launchpad.net/bugs/1927063 Title: Terminal prompt got strangely replicated when resizing terminal horizontally Status in bash package in Ubuntu: Confirmed Status in gnome-terminal package in Ubuntu: Confirmed Status in mate-terminal package in Ubuntu: Confirmed Status in tilix package in Ubuntu: Confirmed Status in vte2.91 package in Ubuntu: Confirmed Bug description: Steps to reproduce: 1. Have Ubuntu installed 2. Launch MATE Terminal 3. Navigate to some folder with long name - `cd /usr/share/doc/ayatana-indicator-application` 4. Resize terminal horizontally Expected results: * terminal shows the same "user@host:/usr/share/doc/ayatana-indicator-application$" with single occurrence Actual results: * terminal shows multiple occurrencies of "user@host:/usr/share/doc/ayatana-indicator-application$" (see attached screencast) ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: mate-terminal 1.24.1-1 ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 Uname: Linux 5.11.0-16-generic x86_64 ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: MATE Date: Tue May 4 10:54:59 2021 InstallationDate: Installed on 2021-04-23 (10 days ago) InstallationMedia: Ubuntu-MATE 21.04 "Hirsute Hippo" - Release amd64 (20210420) SourcePackage: mate-terminal UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bash/+bug/1927063/+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 1927161] [NEW] dpkg-source: error: diff 'openssl/debian/patches/pr12272.patch' patches files multiple times; split the diff in multiple files or merge the hunks into a single one
Public bug reported: [impact] openssl doesn't build source properly because of a badly-constructed patch [test case] $ pull-lp-source openssl groovy ... $ cd openssl-1.1.1f/ $ quilt pop -a ... $ dpkg-buildpackage -d -S dpkg-buildpackage: info: source package openssl dpkg-buildpackage: info: source version 1.1.1f-1ubuntu4.3 dpkg-buildpackage: info: source distribution groovy-security dpkg-buildpackage: info: source changed by Marc Deslauriers dpkg-source --before-build . dpkg-source: warning: can't parse dependency perl:native dpkg-source: error: diff 'openssl-1.1.1f/debian/patches/pr12272.patch' patches files multiple times; split the diff in multiple files or merge the hunks into a single one dpkg-buildpackage: error: dpkg-source --before-build . subprocess returned exit status 25 [regression potential] any regression would likely cause a failed build or would affect the functionality that patch pr12272 was added for, which is adding support for Intel CET [scope] this is needed only for g and later this is caused by the bad patch 'pr12272.patch' which is only included in g/h/i, so this does not apply to f or earlier [other info] note that if the patches are applied, this bug is bypassed; i.e. if 'quilt pop -a' is removed from the test case above, the bug doesn't reproduce. this is only a problem when the patches aren't already applied and dpkg-buildpackage needs to call dpkg-source to apply the patches. ** Affects: openssl (Ubuntu) Importance: Low Status: New ** Affects: openssl (Ubuntu Groovy) Importance: Low Status: New ** Affects: openssl (Ubuntu Hirsute) Importance: Low Status: New ** Affects: openssl (Ubuntu Impish) Importance: Low Status: New ** Description changed: [impact] openssl doesn't build properly because of a badly-constructed patch [test case] $ pull-lp-source openssl groovy ... $ cd openssl-1.1.1f/ $ quilt pop -a ... $ dpkg-buildpackage -d -S dpkg-buildpackage: info: source package openssl dpkg-buildpackage: info: source version 1.1.1f-1ubuntu4.3 dpkg-buildpackage: info: source distribution groovy-security dpkg-buildpackage: info: source changed by Marc Deslauriers - dpkg-source --before-build . + dpkg-source --before-build . dpkg-source: warning: can't parse dependency perl:native dpkg-source: error: diff 'openssl-1.1.1f/debian/patches/pr12272.patch' patches files multiple times; split the diff in multiple files or merge the hunks into a single one dpkg-buildpackage: error: dpkg-source --before-build . subprocess returned exit status 25 [regression potential] any regression would likely cause a failed build or would affect the functionality that patch pr12272 was added for, which is adding support for Intel CET [scope] this is needed only for g and later this is caused by the bad patch 'pr12272.patch' which is only included in g/h/i, so this does not apply to f or earlier + + [other info] + + note that if the patches are applied, this bug is bypassed; i.e. if + 'quilt pop -a' is removed from the test case above, the bug doesn't + reproduce. this is only a problem when the patches aren't already + applied and dpkg-buildpackage needs to call dpkg-source to apply the + patches. ** Also affects: openssl (Ubuntu Impish) Importance: Undecided Status: New ** Also affects: openssl (Ubuntu Hirsute) Importance: Undecided Status: New ** Also affects: openssl (Ubuntu Groovy) Importance: Undecided Status: New ** Changed in: openssl (Ubuntu Groovy) Importance: Undecided => Low ** Changed in: openssl (Ubuntu Hirsute) Importance: Undecided => Low ** Changed in: openssl (Ubuntu Impish) Importance: Undecided => Low ** Description changed: [impact] - openssl doesn't build properly because of a badly-constructed patch + openssl doesn't build source properly because of a badly-constructed + patch [test case] $ pull-lp-source openssl groovy ... $ cd openssl-1.1.1f/ $ quilt pop -a ... $ dpkg-buildpackage -d -S dpkg-buildpackage: info: source package openssl dpkg-buildpackage: info: source version 1.1.1f-1ubuntu4.3 dpkg-buildpackage: info: source distribution groovy-security dpkg-buildpackage: info: source changed by Marc Deslauriers dpkg-source --before-build . dpkg-source: warning: can't parse dependency perl:native dpkg-source: error: diff 'openssl-1.1.1f/debian/patches/pr12272.patch' patches files multiple times; split the diff in multiple files or merge the hunks into a single one dpkg-buildpackage: error: dpkg-source --before-build . subprocess returned exit status 25 [regression potential] any regression would likely cause a failed build or would affect the functionality that patch pr12272 was added for, which is adding support for Intel CET [scope] this is needed only for g and later this is caused by the bad patch
[Touch-packages] [Bug 1883534] Re: Screen flickering
*** This bug is a duplicate of bug 1853094 *** https://bugs.launchpad.net/bugs/1853094 I have de same problem, I change to star ubuntu wayland, but in different moments, ubuntu again present the same problem, this occurs when update the ubuntu because never see this problem the last year in my laptop. Where is the Answer to resolve this problem, I have intel graphic.. -- 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/1883534 Title: Screen flickering Status in xorg package in Ubuntu: Confirmed Bug description: To whom it may concern, As stated I have screen flickerings (see lightning like flickering on photo attached for portrait screen, for horizontal screen I also have screen flickering on the upper part but hard to catch in a photo) on freshly installed Ubuntu 20.04 LTS. I have tried this: https://askubuntu.com/questions/1231441/ubuntu-screen-flickering and this: https://learnubuntumate.weebly.com/screen-tearing-on-intel- graphics.html without success. I have also seen some other people mentioning screen flickering on ubuntu 20.04 here: https://www.reddit.com/r/Ubuntu/comments/fvk536/anyone_else_noticing_window_flickering_on_ubuntu/ without solution. I also know that it is very unlikely hardware problem because my screens were displaying well on archlinux. I think my graphic card info are already included in the report but just in case: Intel Corporation UHD Graphics 630. Might be intel driver problems ? Could you help me on this please ? Best regards, Jeremy ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41 Uname: Linux 5.4.0-37-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Jun 15 15:05:27 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation UHD Graphics 630 (Desktop) [8086:3e92] (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. UHD Graphics 630 (Desktop) [1043:8694] InstallationDate: Installed on 2020-06-12 (2 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 046a:0023 Cherry GmbH Keyboard Bus 001 Device 003: ID 046d:c077 Logitech, Inc. M105 Optical Mouse Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/10p, 5000M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/16p, 480M |__ Port 9: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 1.5M |__ Port 9: Dev 2, If 1, Class=Human Interface Device, Driver=usbhid, 1.5M |__ Port 10: Dev 3, If 0, Class=Human Interface Device, Driver=usbhid, 1.5M MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-37-generic root=UUID=81cee77a-b529-4dac-9834-dc6d5ab2dc16 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/11/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0615 dmi.board.asset.tag: Default string dmi.board.name: PRIME Z370-P dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0615:bd04/11/2018:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEZ370-P:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1883534/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages
[Touch-packages] [Bug 1915126] Re: autopkgtest times out (or fails before that) in hirsute on test infra, passes locally
I've split the upstream test in 247.3-5ubuntu1 and also forwarded the change: https://salsa.debian.org/systemd-team/systemd/-/merge_requests/128 -- 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/1915126 Title: autopkgtest times out (or fails before that) in hirsute on test infra, passes locally Status in Auto Package Testing: Incomplete Status in systemd package in Ubuntu: Fix Released Bug description: Hi, I've asked yesterday on IRC but so far got no answer. I think it is right to file a bug about the current state of systemd autopkgtest to unite the efforts in regard to it. I was looking at the systemd tests for a no-change rebuild that really had no reason to now make it fail. While checking I found that as of this month (first bad test on 1st of February) most of the systemd test runs on amd64 will not pass/fail but instead in most cases time out. I've seen various people retry the case as it shows the typical symptoms of a "not the fault of the package, let us retry this" case. But it seems that won't help as the test history is rather clear. * Watch this in monospace to make more sense of it * $ check-autopkgtest-stats.sh -c 50 -p systemd -r "hirsute" -a "amd64" Check last 50 test results for src:systemd on releases 'hirsute' on architectures 'amd64' Of the 50 last tests, we had these subtest failing per release/arch: hirsute amd64 tests-in-lxd (F 2% f 0% S 0% B 12% => P 52%/) .BTTTBTT.BTBTTTBBTTT..F.. hostnamed (F 0% f 0% S 0% B 12% => P 54%/) .BTTTBTT.BTBTTTBBTTT. build-login(F 0% f 0% S 0% B 12% => P 54%/) .BTTTBTT.BTBTTTBBTTT. unit-config(F 0% f 0% S 0% B 12% => P 54%/) .BTTTBTT.BTBTTTBBTTT. networkd-testpy(F 0% f 0% S 0% B 12% => P 54%/) .BTTTBTT.BTBTTTBBTTT. localed-locale (F 0% f 0% S 0% B 12% => P 54%/) .BTTTBTT.BTBTTTBBTTT. boot-and-services (F 4% f 0% S 0% B 12% => P 50%/) .BTTTBTT.BTBTTTBBTTT...F.F... timedated (F 0% f 0% S 0% B 12% => P 54%/) .BTTTBTT.BTBTTTBBTTT. boot-smoke (F 0% f 0% S 0% B 12% => P 54%/) .BTTTBTT.BTBTTTBBTTT. logind (F 0% f 0% S 0% B 12% => P 54%/) .BTTTBTT.BTBTTTBBTTT. storage(F 0% f 0% S 0% B 12% => P 54%/) .BTTTBTT.BTBTTTBBTTT. upstream (F 12% f 0% S 0% B 12% => P 42%/) .BTTTBTT.BTBTTTBBTTTF.F.F..FF..F. udev (F 0% f 0% S 0% B 12% => P 54%/) .BTTTBTT.BTBTTTBBTTT. systemd-fsckd (F 8% f 0% S 0% B 12% => P 46%/) FBTTTBTTFBTBTTTBBTTT.F..F root-unittests (F 0% f 0% S 0% B 12% => P 54%/) .BTTTBTT.BTBTTTBBTTT. localed-x11-keymap (F 0% f 0% S 0% B 12% => P 54%/) .BTTTBTT.BTBTTTBBTTT. We see that formerly we had the known to be somewhat flaky, but otherwise working test (time goes from right to left). So we had the usual suspects of tests like upstream/systemd-fsck that failed a few times, but also working runs in between. But since February 22/24 runs failed very bad. 6 (=B) of those cases are aborting mid execution autopkgtest [22:08:58]: ERROR: testbed failure: testbed auxverb failed with exit code 255 And 16 of them timed out : failure: Timed out on waiting for ssh connection Sadly the 2/24 that didn't hard fail by that where broken by the known flaky systemd-fsckd test. Something drives this test crazy that we have to find and resolve, at the current rate nothing depending on it is likely to migrate. To manage notifications about this bug go to: https://bugs.launchpad.net/auto-package-testing/+bug/1915126/+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 1884024] Re: lxc-test-device-add-remove from ubuntu_lxc failed on B-5.4
Spotted also with bionic/linux-hwe-5.4 5.4.0-73.82~18.04.1. ** Tags added: hwe ** Tags added: hwe-5.4 -- 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/1884024 Title: lxc-test-device-add-remove from ubuntu_lxc failed on B-5.4 Status in ubuntu-kernel-tests: New Status in lxc package in Ubuntu: Fix Committed Bug description: Issue found on with 5.4.0-1016.16~18.04.1-oracle on both VM.Standard2.1 and VM.Standard2.16 Test failed with: FAIL: lxc-tests: lxc-test-device-add-remove (1s) --- Adding /dev/network_latency to the container (device_add_remove_test) failed... This issue can be found on oracle : 5.4.0-1011.11~18.04.1 on VM.Standard2.16 but passed on VM.Standard2.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1884024/+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 1927136] [NEW] Canon printer will not print. Message shows it does print. I can scan
Public bug reported: Printer worked fine in version 18. Does not print in version 20. It will scan docs back to the computer. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: cups 2.3.1-9ubuntu1.1 ProcVersionSignature: Ubuntu 5.4.0-72.80-generic 5.4.101 Uname: Linux 5.4.0-72-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue May 4 12:36:48 2021 InstallationDate: Installed on 2019-12-07 (514 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) Lpstat: device for Canon-MG3200-series: usb://Canon/MG3200%20series?serial=120A84=1 device for localhost: ///dev/null MachineType: Dell Inc. Vostro 230 Papersize: letter PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/Canon-MG3200-series.ppd'] failed with exit code 2: grep: /etc/cups/ppd/Canon-MG3200-series.ppd: Permission denied ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-72-generic root=UUID=5b75bf38-459b-47b1-95cd-d4beda9dbc47 ro quiet splash vt.handoff=7 SourcePackage: cups UpgradeStatus: Upgraded to focal on 2021-03-08 (56 days ago) dmi.bios.date: 07/07/2010 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.2.0 dmi.board.name: 07N90W dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvr1.2.0:bd07/07/2010:svnDellInc.:pnVostro230:pvr00:rvnDellInc.:rn07N90W:rvrA01:cvnDellInc.:ct3:cvrNotSpecified: dmi.product.family: 0 dmi.product.name: Vostro 230 dmi.product.sku: 0 dmi.product.version: 00 dmi.sys.vendor: Dell Inc. ** Affects: cups (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 cups in Ubuntu. https://bugs.launchpad.net/bugs/1927136 Title: Canon printer will not print. Message shows it does print. I can scan Status in cups package in Ubuntu: New Bug description: Printer worked fine in version 18. Does not print in version 20. It will scan docs back to the computer. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: cups 2.3.1-9ubuntu1.1 ProcVersionSignature: Ubuntu 5.4.0-72.80-generic 5.4.101 Uname: Linux 5.4.0-72-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue May 4 12:36:48 2021 InstallationDate: Installed on 2019-12-07 (514 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) Lpstat: device for Canon-MG3200-series: usb://Canon/MG3200%20series?serial=120A84=1 device for localhost: ///dev/null MachineType: Dell Inc. Vostro 230 Papersize: letter PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/Canon-MG3200-series.ppd'] failed with exit code 2: grep: /etc/cups/ppd/Canon-MG3200-series.ppd: Permission denied ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-72-generic root=UUID=5b75bf38-459b-47b1-95cd-d4beda9dbc47 ro quiet splash vt.handoff=7 SourcePackage: cups UpgradeStatus: Upgraded to focal on 2021-03-08 (56 days ago) dmi.bios.date: 07/07/2010 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.2.0 dmi.board.name: 07N90W dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvr1.2.0:bd07/07/2010:svnDellInc.:pnVostro230:pvr00:rvnDellInc.:rn07N90W:rvrA01:cvnDellInc.:ct3:cvrNotSpecified: dmi.product.family: 0 dmi.product.name: Vostro 230 dmi.product.sku: 0 dmi.product.version: 00 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1927136/+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 1927063] Re: Terminal prompt got strangely replicated when resizing terminal horizontally
** Also affects: gnome-terminal (Ubuntu) Importance: Undecided Status: New ** Also affects: tilix (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bash in Ubuntu. https://bugs.launchpad.net/bugs/1927063 Title: Terminal prompt got strangely replicated when resizing terminal horizontally Status in bash package in Ubuntu: Confirmed Status in gnome-terminal package in Ubuntu: New Status in mate-terminal package in Ubuntu: Confirmed Status in tilix package in Ubuntu: New Status in vte2.91 package in Ubuntu: Confirmed Bug description: Steps to reproduce: 1. Have Ubuntu installed 2. Launch MATE Terminal 3. Navigate to some folder with long name - `cd /usr/share/doc/ayatana-indicator-application` 4. Resize terminal horizontally Expected results: * terminal shows the same "user@host:/usr/share/doc/ayatana-indicator-application$" with single occurrence Actual results: * terminal shows multiple occurrencies of "user@host:/usr/share/doc/ayatana-indicator-application$" (see attached screencast) ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: mate-terminal 1.24.1-1 ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 Uname: Linux 5.11.0-16-generic x86_64 ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: MATE Date: Tue May 4 10:54:59 2021 InstallationDate: Installed on 2021-04-23 (10 days ago) InstallationMedia: Ubuntu-MATE 21.04 "Hirsute Hippo" - Release amd64 (20210420) SourcePackage: mate-terminal UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bash/+bug/1927063/+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 1927063] Re: Terminal prompt got strangely replicated when resizing terminal horizontally
Can confirm this, it also affects Tilix and Gnome-Terminal (Ubuntu 20.04, Gnome 3.36.4). -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bash in Ubuntu. https://bugs.launchpad.net/bugs/1927063 Title: Terminal prompt got strangely replicated when resizing terminal horizontally Status in bash package in Ubuntu: Confirmed Status in gnome-terminal package in Ubuntu: New Status in mate-terminal package in Ubuntu: Confirmed Status in tilix package in Ubuntu: New Status in vte2.91 package in Ubuntu: Confirmed Bug description: Steps to reproduce: 1. Have Ubuntu installed 2. Launch MATE Terminal 3. Navigate to some folder with long name - `cd /usr/share/doc/ayatana-indicator-application` 4. Resize terminal horizontally Expected results: * terminal shows the same "user@host:/usr/share/doc/ayatana-indicator-application$" with single occurrence Actual results: * terminal shows multiple occurrencies of "user@host:/usr/share/doc/ayatana-indicator-application$" (see attached screencast) ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: mate-terminal 1.24.1-1 ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 Uname: Linux 5.11.0-16-generic x86_64 ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: MATE Date: Tue May 4 10:54:59 2021 InstallationDate: Installed on 2021-04-23 (10 days ago) InstallationMedia: Ubuntu-MATE 21.04 "Hirsute Hippo" - Release amd64 (20210420) SourcePackage: mate-terminal UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bash/+bug/1927063/+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 1927078] Re: Don't allow useradd to use fully numeric names
I don't have a strong opinion either, but given that scripts would ignore the warnings and the resulting numeric users are going to face random, seemingly unrelated issues thanks to the interaction with systemd, I think I prefer the failure. FWIW, I've prepared a test version in a PPA[1] which keeps the rules from Debian[2] but prevents the fully numeric names. This is what it looks like: $ useradd 0 useradd: invalid user name '0' $ echo $? 3 $ sudo useradd 0c0 $ sudo useradd 0 --badnames $ cat /etc/passwd | grep ^0 0c0:x:1001:1001::/home/0c0:/bin/sh 0:x:1002:1002::/home/0:/bin/sh [1] https://launchpad.net/~vtapia/+archive/ubuntu/sf305373 [2] https://salsa.debian.org/debian/shadow/-/blob/master/debian/patches/506_relaxed_usernames -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to shadow in Ubuntu. https://bugs.launchpad.net/bugs/1927078 Title: Don't allow useradd to use fully numeric names Status in shadow package in Ubuntu: New Status in shadow source package in Focal: New Status in shadow source package in Groovy: New Status in shadow source package in Hirsute: New Status in shadow source package in Impish: New Bug description: [Description] Fully numeric names support in Ubuntu is inconsistent in Focal onwards because systemd does not like them[1] but are still allowed by default by useradd, leaving the session behavior in hands of the running applications. Two examples: 1. After creating a user named "0", the user can log in via ssh or console but loginctl won't create a session for it: root@focal:/home/ubuntu# useradd -m 0 root@focal:/home/ubuntu# id 0 uid=1005(0) gid=1005(0) groups=1005(0) .. 0@192.168.122.6's password: Welcome to Ubuntu 20.04.2 LTS (GNU/Linux 5.8.0-48-generic x86_64) Last login: Thu Apr 8 16:17:06 2021 from 192.168.122.1 $ loginctl No sessions. $ w 16:20:09 up 4 min, 1 user, load average: 0.03, 0.14, 0.08 USER TTY FROM LOGIN@ IDLE JCPU PCPU WHAT 0pts/0192.168.122.116:170.00s 0.00s 0.00s w And pam-systemd shows the following message: Apr 08 16:17:06 focal sshd[1584]: pam_unix(sshd:session): session opened for user 0 by (uid=0) Apr 08 16:17:06 focal sshd[1584]: pam_systemd(sshd:session): pam-systemd initializing Apr 08 16:17:06 focal sshd[1584]: pam_systemd(sshd:session): Failed to get user record: Invalid argument 2. With that same username, every successful authentication in gdm will loop back to gdm again instead of starting gnome, making the user unable to login. Making useradd fail (unless --badnames is set) when a fully numeric name is used will make the default OS behavior consistent. [Other info] - Upstream does not support fully numeric usernames - useradd has a --badnames parameter that would still allow the use of these type of names To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shadow/+bug/1927078/+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 1897561] Re: libperl.so.5.30.0 causes nginx to segfault
Can confirm, this bug is still a reality in Ubuntu 20.04 (focal) and is triggered by two reloads in a row. root@nginx:~# ps aux|grep nginx root 3356067 0.0 0.1 71600 9788 ?Ss 15:46 0:00 nginx: master process /usr/sbin/nginx -g daemon on; master_process on; www-data 3356068 0.0 0.1 73012 15348 ?S15:46 0:00 nginx: worker process www-data 3356069 0.0 0.1 73012 15348 ?S15:46 0:00 nginx: worker process www-data 3356070 0.0 0.1 73012 15348 ?S15:46 0:00 nginx: worker process www-data 3356071 0.0 0.1 73012 15348 ?S15:46 0:00 nginx: worker process www-data 3356072 0.0 0.1 73012 15348 ?S15:46 0:00 nginx: worker process www-data 3356073 0.0 0.1 73012 15348 ?S15:46 0:00 nginx: worker process www-data 3356074 0.0 0.1 73012 15348 ?S15:46 0:00 nginx: worker process www-data 3356075 0.0 0.1 73012 15348 ?S15:46 0:00 nginx: worker process root 3356102 0.0 0.0 8900 676 pts/0S+ 15:46 0:00 grep --color=auto nginx root@nginx:~# service nginx reload root@nginx:~# ps aux|grep nginx root 3356067 0.2 0.3 81404 28848 ?Ss 15:46 0:00 nginx: master process /usr/sbin/nginx -g daemon on; master_process on; www-data 3356266 0.0 0.2 81644 22608 ?S15:46 0:00 nginx: worker process www-data 3356267 0.0 0.2 81644 22608 ?S15:46 0:00 nginx: worker process www-data 3356268 0.0 0.2 81644 22608 ?S15:46 0:00 nginx: worker process www-data 3356269 0.0 0.2 81644 22608 ?S15:46 0:00 nginx: worker process www-data 3356270 0.0 0.2 81644 22608 ?S15:46 0:00 nginx: worker process www-data 3356271 0.0 0.2 81644 22608 ?S15:46 0:00 nginx: worker process www-data 3356272 0.0 0.2 81644 22608 ?S15:46 0:00 nginx: worker process www-data 3356273 0.0 0.2 81644 22608 ?S15:46 0:00 nginx: worker process root 3356296 0.0 0.0 17196 7168 ?R15:46 0:00 /usr/bin/pgrep nginx root 3356309 0.0 0.0 8900 736 pts/0S+ 15:46 0:00 grep --color=auto nginx root@nginx:~# service nginx reload root@nginx:~# ps aux|grep nginx root 3356355 0.0 0.0 8900 736 pts/0S+ 15:46 0:00 grep --color=auto nginx At the time of the second reload, the following segfault is logged in /var/log/kern.log: May 4 15:46:50 onl-paylb02-p kernel: [4141537.262674] nginx[3356067]: segfault at 51 ip 7f6b7d1535c9 sp 7ffe634334d0 error 4 in libperl.so.5.30.0[7f6b7d0eb000+166000] May 4 15:46:50 onl-paylb02-p kernel: [4141537.262681] Code: 00 0f b6 40 30 49 c1 ed 03 49 29 c5 0f 84 17 01 00 00 48 8b 76 10 48 8b 52 10 4c 8d 3c fe 4c 8d 0c c2 84 c9 0f 84 c7 02 00 00 <49> 83 39 00 0f 85 ad 03 00 00 49 83 c1 08 49 83 ed 01 49 8d 74 1d -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to perl in Ubuntu. https://bugs.launchpad.net/bugs/1897561 Title: libperl.so.5.30.0 causes nginx to segfault Status in perl package in Ubuntu: Confirmed Bug description: [Steps to reproduce] 1) launch a focal container $ lxc launch images:ubuntu/focal focal-1897561 2) enter the container $ lxc shell focal-1897561 3) install libnginx-mod-http-perl # apt-get install -y nginx-core libnginx-mod-http-perl 4) check nginx journal # journalctl -fu nginx & 5) reload nginx 2-3 times # systemctl reload nginx Eventually you will see this from the journal: Oct 13 17:13:34 focal-1897561 systemd[1]: Reloaded A high performance web server and a reverse proxy server. Oct 13 17:13:35 focal-1897561 systemd[1]: nginx.service: Main process exited, code=dumped, status=11/SEGV Oct 13 17:13:35 focal-1897561 systemd[1]: nginx.service: Killing process 588 (nginx) with signal SIGKILL. Oct 13 17:13:35 focal-1897561 systemd[1]: nginx.service: Killing process 589 (nginx) with signal SIGKILL. Oct 13 17:13:35 focal-1897561 systemd[1]: nginx.service: Killing process 588 (nginx) with signal SIGKILL. Oct 13 17:13:35 focal-1897561 systemd[1]: nginx.service: Killing process 589 (nginx) with signal SIGKILL. Oct 13 17:13:35 focal-1897561 systemd[1]: nginx.service: Failed with result 'core-dump'. [Workaround] If libnginx-mod-http-perl is not needed, purging it and restarting nginx sidesteps the problem. [Original bug description] Ubuntu 20.04 LTS Looks that Perl 5.30 has bug that causes nginx to die, usually occurs after "service nginx reload" This looks like nginx, but it really is perl issue: https://github.com/Perl/perl5/issues/17154 Fix done in 5.32 (Perl5 commit bf0) and people are asking backport to 5.30 to get fix also to nginx. Error: Sep 28 07:39:43 host kernel: [1340832.811014] nginx[3253005]: segfault at 10 ip 7fbf3220d593 sp 7ffd6bba6260 error 4 in
[Touch-packages] [Bug 1889416] Re: pulseaudio.service: Start request repeated too quickly.
Ehrm. I don't agree with editing the service file that comes from the package and will get overwritten. Ensuring the correct order in the PAM configuration is the correct fix here. -- 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/1889416 Title: pulseaudio.service: Start request repeated too quickly. Status in fscrypt package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Confirmed Bug description: PA doesn't start on it's own after the latest update. ``` nafallo@wendigo:~$ systemctl --user status pulseaudio ● pulseaudio.service - Sound Service Loaded: loaded (/usr/lib/systemd/user/pulseaudio.service; enabled; vendor preset: enabled) Active: failed (Result: exit-code) since Wed 2020-07-29 14:59:19 CEST; 11min ago TriggeredBy: ● pulseaudio.socket Process: 2774 ExecStart=/usr/bin/pulseaudio --daemonize=no --log-target=journal (code=exited, status=1/FAILURE) Main PID: 2774 (code=exited, status=1/FAILURE) Jul 29 14:59:19 wendigo systemd[2664]: pulseaudio.service: Scheduled restart job, restart counter is at 5. Jul 29 14:59:19 wendigo systemd[2664]: Stopped Sound Service. Jul 29 14:59:19 wendigo systemd[2664]: pulseaudio.service: Start request repeated too quickly. Jul 29 14:59:19 wendigo systemd[2664]: pulseaudio.service: Failed with result 'exit-code'. Jul 29 14:59:19 wendigo systemd[2664]: Failed to start Sound Service. Jul 29 14:59:20 wendigo systemd[2664]: pulseaudio.service: Start request repeated too quickly. Jul 29 14:59:20 wendigo systemd[2664]: pulseaudio.service: Failed with result 'exit-code'. Jul 29 14:59:20 wendigo systemd[2664]: Failed to start Sound Service. ``` But works after starting it manually. ``` nafallo@wendigo:~$ systemctl --user start pulseaudio nafallo@wendigo:~$ systemctl --user status pulseaudio ● pulseaudio.service - Sound Service Loaded: loaded (/usr/lib/systemd/user/pulseaudio.service; enabled; vendor preset: enabled) Active: active (running) since Wed 2020-07-29 15:11:14 CEST; 5min ago TriggeredBy: ● pulseaudio.socket Main PID: 5675 (pulseaudio) CGroup: /user.slice/user-1000.slice/user@1000.service/pulseaudio.service └─5675 /usr/bin/pulseaudio --daemonize=no --log-target=journal Jul 29 15:11:13 wendigo systemd[2664]: Starting Sound Service... Jul 29 15:11:14 wendigo systemd[2664]: Started Sound Service. ``` ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu3.5 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: nafallo5675 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Jul 29 15:11:28 2020 InstallationDate: Installed on 2018-06-27 (763 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/11/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.12.1 dmi.board.name: 0W970W dmi.board.vendor: Dell Inc. dmi.board.version: A03 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.12.1:bd12/11/2019:svnDellInc.:pnXPS139370:pvr:rvnDellInc.:rn0W970W:rvrA03:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9370 dmi.product.sku: 07E6 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fscrypt/+bug/1889416/+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 1576559] Re: Refused to switch profile to headset_head_unit: Not connected
Hi, @Daniel van Vugt - Not familiar with the release process at pulseaudio and/or Ubuntu, so... when will this fix be out in the field? Thanks in advance, Tom. -- 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/1576559 Title: Refused to switch profile to headset_head_unit: Not connected Status in PulseAudio: Unknown Status in pulseaudio package in Ubuntu: Fix Committed Bug description: I'm trying to connect a bluetooth-speaker-with-microphone (Mi Bluetooth Speaker) to Ubuntu. It works well as an A2DP sync, but can't use it as a headset with microphone. The device doesn't list in the "Input Devices" by default, and using the sound settings to change the profile of the device to HSP/HFP results in this log message: W: [pulseaudio] module-bluez5-device.c: Refused to switch profile to headset_head_unit: Not connected I'm running Ubuntu 16.04 LTS. I did an upgrade from Ubuntu 15.10. pulseaudio: Installed: 1:8.0-0ubuntu3 bluez: Installed: 5.37-0ubuntu5 To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/1576559/+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 1927078] Re: Don't allow useradd to use fully numeric names
Maybe it should be a warning in the SRUs as opposed to a failure, but I don't have a strong opinion. I'm a bit scared of breaking scripts. But maybe that's a good thing. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to shadow in Ubuntu. https://bugs.launchpad.net/bugs/1927078 Title: Don't allow useradd to use fully numeric names Status in shadow package in Ubuntu: New Status in shadow source package in Focal: New Status in shadow source package in Groovy: New Status in shadow source package in Hirsute: New Status in shadow source package in Impish: New Bug description: [Description] Fully numeric names support in Ubuntu is inconsistent in Focal onwards because systemd does not like them[1] but are still allowed by default by useradd, leaving the session behavior in hands of the running applications. Two examples: 1. After creating a user named "0", the user can log in via ssh or console but loginctl won't create a session for it: root@focal:/home/ubuntu# useradd -m 0 root@focal:/home/ubuntu# id 0 uid=1005(0) gid=1005(0) groups=1005(0) .. 0@192.168.122.6's password: Welcome to Ubuntu 20.04.2 LTS (GNU/Linux 5.8.0-48-generic x86_64) Last login: Thu Apr 8 16:17:06 2021 from 192.168.122.1 $ loginctl No sessions. $ w 16:20:09 up 4 min, 1 user, load average: 0.03, 0.14, 0.08 USER TTY FROM LOGIN@ IDLE JCPU PCPU WHAT 0pts/0192.168.122.116:170.00s 0.00s 0.00s w And pam-systemd shows the following message: Apr 08 16:17:06 focal sshd[1584]: pam_unix(sshd:session): session opened for user 0 by (uid=0) Apr 08 16:17:06 focal sshd[1584]: pam_systemd(sshd:session): pam-systemd initializing Apr 08 16:17:06 focal sshd[1584]: pam_systemd(sshd:session): Failed to get user record: Invalid argument 2. With that same username, every successful authentication in gdm will loop back to gdm again instead of starting gnome, making the user unable to login. Making useradd fail (unless --badnames is set) when a fully numeric name is used will make the default OS behavior consistent. [Other info] - Upstream does not support fully numeric usernames - useradd has a --badnames parameter that would still allow the use of these type of names To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shadow/+bug/1927078/+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 1927063] Re: Terminal prompt got strangely replicated when resizing terminal horizontally
Previous Ubuntu versions like 18.04 LTS, 18.10 do not have such an issue. The bug was first introduced in Ubuntu 19.04. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bash in Ubuntu. https://bugs.launchpad.net/bugs/1927063 Title: Terminal prompt got strangely replicated when resizing terminal horizontally Status in bash package in Ubuntu: Confirmed Status in mate-terminal package in Ubuntu: Confirmed Status in vte2.91 package in Ubuntu: Confirmed Bug description: Steps to reproduce: 1. Have Ubuntu installed 2. Launch MATE Terminal 3. Navigate to some folder with long name - `cd /usr/share/doc/ayatana-indicator-application` 4. Resize terminal horizontally Expected results: * terminal shows the same "user@host:/usr/share/doc/ayatana-indicator-application$" with single occurrence Actual results: * terminal shows multiple occurrencies of "user@host:/usr/share/doc/ayatana-indicator-application$" (see attached screencast) ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: mate-terminal 1.24.1-1 ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 Uname: Linux 5.11.0-16-generic x86_64 ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: MATE Date: Tue May 4 10:54:59 2021 InstallationDate: Installed on 2021-04-23 (10 days ago) InstallationMedia: Ubuntu-MATE 21.04 "Hirsute Hippo" - Release amd64 (20210420) SourcePackage: mate-terminal UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bash/+bug/1927063/+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 1927082] [NEW] Mouse and keyboard bug
Public bug reported: My mouse and keyboard stop working after while. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3.1 ProcVersionSignature: Ubuntu 4.15.0-142.146~16.04.1-generic 4.15.18 Uname: Linux 4.15.0-142-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia .proc.driver.nvidia.gpus..03.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:03:00.0' .proc.driver.nvidia.gpus..04.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:04:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 384.130 Wed Mar 21 03:37:26 PDT 2018 GCC version: gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.12) .proc.driver.nvidia.warnings.fbdev: Your system is not currently configured to drive a VGA console on the primary VGA device. The NVIDIA Linux graphics driver requires the use of a text-mode VGA console. Use of other console drivers including, but not limited to, vesafb, may result in corruption and stability problems, and is not supported. .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.30 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: Tue May 4 12:58:52 2021 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GP106 [GeForce GTX 1060 3GB] [10de:1c02] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] Device [1462:3287] NVIDIA Corporation GP106 [GeForce GTX 1060 3GB] [10de:1c02] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] Device [1462:3287] InstallationDate: Installed on 2018-01-20 (1199 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) MachineType: MSI MS-7885 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-142-generic root=UUID=2d0f054b-beb1-4182-9871-2d8ea219b402 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/15/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.D0 dmi.board.asset.tag: Default string dmi.board.name: X99A SLI PLUS(MS-7885) dmi.board.vendor: MSI dmi.board.version: 1.0 dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.D0:bd07/15/2016:svnMSI:pnMS-7885:pvr1.0:rvnMSI:rnX99ASLIPLUS(MS-7885):rvr1.0:cvnMSI:ct3:cvr1.0: dmi.product.family: Default string dmi.product.name: MS-7885 dmi.product.version: 1.0 dmi.sys.vendor: MSI version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.91-2~16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~16.04.1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A 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: Tue May 4 12:43:15 2021 xserver.configfile: default xserver.devices: inputPower Button KEYBOARD, id 6 inputPower Button KEYBOARD, id 7 inputKYE SYSTEMS CORP. Wired Mouse MOUSE, id 8 inputSEM USB Keyboard KEYBOARD, id 9 inputSEM USB Keyboard KEYBOARD, id 10 xserver.errors: [drm] Failed to open DRM device for (null): -22 xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.19.6-1ubuntu4.1~16.04.6 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug compiz-0.9 ubuntu xenial -- 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/1927082 Title: Mouse and keyboard bug Status in xorg package in Ubuntu: New Bug description: My mouse and keyboard stop working after while. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3.1 ProcVersionSignature: Ubuntu 4.15.0-142.146~16.04.1-generic 4.15.18 Uname: Linux 4.15.0-142-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia .proc.driver.nvidia.gpus..03.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:03:00.0' .proc.driver.nvidia.gpus..04.00.0: Error: [Errno 21] Is a
[Touch-packages] [Bug 1926855] Re: Raspberry Pi: desktop forgets audio device selected after reboot
** Package changed: ubuntu => pulseaudio (Ubuntu) -- 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/1926855 Title: Raspberry Pi: desktop forgets audio device selected after reboot Status in pulseaudio package in Ubuntu: New Bug description: Hirsute 21.04 Raspberry Pi on Pi 4B 4GB Audio output device defaults to 'Headphones - Built-in Audio': this is the AV jack. Settings also lists 'Digital Output (S/PDIF) - Built-in Audio' which is HDMI, and I can get audio from it correctly. However, this setting is not saved, and on reboot it defaults back to 'Headphones - Built-in Audio'. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1926855/+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 1926855] [NEW] Raspberry Pi: desktop forgets audio device selected after reboot
You have been subscribed to a public bug: Hirsute 21.04 Raspberry Pi on Pi 4B 4GB Audio output device defaults to 'Headphones - Built-in Audio': this is the AV jack. Settings also lists 'Digital Output (S/PDIF) - Built-in Audio' which is HDMI, and I can get audio from it correctly. However, this setting is not saved, and on reboot it defaults back to 'Headphones - Built-in Audio'. ** Affects: pulseaudio (Ubuntu) Importance: Undecided Status: New ** Tags: bot-comment -- Raspberry Pi: desktop forgets audio device selected after reboot https://bugs.launchpad.net/bugs/1926855 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1927070] Re: stack-overflow on GNU libiberty/rust-demangle.c:1024 demangle_type
** Description changed: - stack-overflowon GNU libiberty/rust-demangle.c:84 peek when we run + stack-overflowon GNU libiberty/rust-demangle.c:84 peek when we run cat /crashes/poc | ./cxxfilt + the version : binutils(2.36) /crashes/poc: F}��.]]��_RYFB1_��z^A^R]M�^?N�^K^]�J^@^@^@^@^@^@^@^@�^A^@��]^yCo#Mo?NCgyCo7MoPggCo~NMG^P#��=^F~@c�Cqot�_ZooSk;^]���]^yCo7Mo?NCgyCo7MoPggCo~NMG^P#^R�7Cg^V^A_���^?^@^A�_ZooSoBbg6^@g^_�@gg��g!T^[ asan output: - root@f960c0e3747a:cat /crashes/poc | ./cxxfilt + root@f960c0e3747a:cat /crashes/poc | ./cxxfilt ASAN:SIGSEGV = ==35495==ERROR: AddressSanitizer: stack-overflow on address 0x7ffcda322ff8 (pc 0x006a0e3f bp 0x7ffcda323000 sp 0x7ffcda322ff0 T0) - #0 0x6a0e3e in peek rust-demangle.c:84 - #1 0x6a0f96 in next rust-demangle.c:105 - #2 0x6a478f in demangle_type rust-demangle.c:864 - #3 0x6a5110 in demangle_type rust-demangle.c:1024 - #4 0x6a5110 in demangle_type rust-demangle.c:1024 - #5 0x6a5110 in demangle_type rust-demangle.c:1024 - #6 0x6a5110 in demangle_type rust-demangle.c:1024 - #7 0x6a5110 in demangle_type rust-demangle.c:1024 - #8 0x6a5110 in demangle_type rust-demangle.c:1024 - #9 0x6a5110 in demangle_type rust-demangle.c:1024 - #10 0x6a5110 in demangle_type rust-demangle.c:1024 - #11 0x6a5110 in demangle_type rust-demangle.c:1024 - #12 0x6a5110 in demangle_type rust-demangle.c:1024 - #13 0x6a5110 in demangle_type rust-demangle.c:1024 - #14 0x6a5110 in demangle_type rust-demangle.c:1024 - #15 0x6a5110 in demangle_type rust-demangle.c:1024 - #16 0x6a5110 in demangle_type rust-demangle.c:1024 - #17 0x6a5110 in demangle_type rust-demangle.c:1024 - #18 0x6a5110 in demangle_type rust-demangle.c:1024 - #19 0x6a5110 in demangle_type rust-demangle.c:1024 - #20 0x6a5110 in demangle_type rust-demangle.c:1024 - #21 0x6a5110 in demangle_type rust-demangle.c:1024 - #22 0x6a5110 in demangle_type rust-demangle.c:1024 - #23 0x6a5110 in demangle_type rust-demangle.c:1024 - #24 0x6a5110 in demangle_type rust-demangle.c:1024 - #25 0x6a5110 in demangle_type rust-demangle.c:1024 - #26 0x6a5110 in demangle_type rust-demangle.c:1024 - #27 0x6a5110 in demangle_type rust-demangle.c:1024 - #28 0x6a5110 in demangle_type rust-demangle.c:1024 - #29 0x6a5110 in demangle_type rust-demangle.c:1024 - #30 0x6a5110 in demangle_type rust-demangle.c:1024 - #31 0x6a5110 in demangle_type rust-demangle.c:1024 - #32 0x6a5110 in demangle_type rust-demangle.c:1024 - #33 0x6a5110 in demangle_type rust-demangle.c:1024 - #34 0x6a5110 in demangle_type rust-demangle.c:1024 - #35 0x6a5110 in demangle_type rust-demangle.c:1024 - #36 0x6a5110 in demangle_type rust-demangle.c:1024 - #37 0x6a5110 in demangle_type rust-demangle.c:1024 - #38 0x6a5110 in demangle_type rust-demangle.c:1024 - #39 0x6a5110 in demangle_type rust-demangle.c:1024 - #40 0x6a5110 in demangle_type rust-demangle.c:1024 - #41 0x6a5110 in demangle_type rust-demangle.c:1024 - #42 0x6a5110 in demangle_type rust-demangle.c:1024 - #43 0x6a5110 in demangle_type rust-demangle.c:1024 - #44 0x6a5110 in demangle_type rust-demangle.c:1024 - #45 0x6a5110 in demangle_type rust-demangle.c:1024 - #46 0x6a5110 in demangle_type rust-demangle.c:1024 - #47 0x6a5110 in demangle_type rust-demangle.c:1024 - #48 0x6a5110 in demangle_type rust-demangle.c:1024 - #49 0x6a5110 in demangle_type rust-demangle.c:1024 - #50 0x6a5110 in demangle_type rust-demangle.c:1024 - #51 0x6a5110 in demangle_type rust-demangle.c:1024 - #52 0x6a5110 in demangle_type rust-demangle.c:1024 - #53 0x6a5110 in demangle_type rust-demangle.c:1024 - #54 0x6a5110 in demangle_type rust-demangle.c:1024 - #55 0x6a5110 in demangle_type rust-demangle.c:1024 - #56 0x6a5110 in demangle_type rust-demangle.c:1024 - #57 0x6a5110 in demangle_type rust-demangle.c:1024 - #58 0x6a5110 in demangle_type rust-demangle.c:1024 - #59 0x6a5110 in demangle_type rust-demangle.c:1024 - #60 0x6a5110 in demangle_type rust-demangle.c:1024 - #61 0x6a5110 in demangle_type rust-demangle.c:1024 - #62 0x6a5110 in demangle_type rust-demangle.c:1024 - #63 0x6a5110 in demangle_type rust-demangle.c:1024 - #64 0x6a5110 in demangle_type rust-demangle.c:1024 - #65 0x6a5110 in demangle_type rust-demangle.c:1024 - #66 0x6a5110 in demangle_type rust-demangle.c:1024 - #67 0x6a5110 in demangle_type rust-demangle.c:1024 - #68 0x6a5110 in demangle_type rust-demangle.c:1024 - #69 0x6a5110 in demangle_type rust-demangle.c:1024 - #70 0x6a5110 in demangle_type rust-demangle.c:1024 - #71 0x6a5110 in demangle_type rust-demangle.c:1024 - #72 0x6a5110 in demangle_type rust-demangle.c:1024 - #73 0x6a5110 in demangle_type
[Touch-packages] [Bug 1927070] Re: stack-overflow on GNU libiberty/rust-demangle.c:1024 demangle_type
what value do these bug reports have? did you file these upstream? it's also not clear which version you are testing ** Changed in: binutils (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to binutils in Ubuntu. https://bugs.launchpad.net/bugs/1927070 Title: stack-overflow on GNU libiberty/rust-demangle.c:1024 demangle_type Status in binutils package in Ubuntu: Incomplete Bug description: stack-overflowon GNU libiberty/rust-demangle.c:84 peek when we run cat /crashes/poc | ./cxxfilt /crashes/poc: F}��.]]��_RYFB1_��z^A^R]M�^?N�^K^]�J^@^@^@^@^@^@^@^@�^A^@��]^yCo#Mo?NCgyCo7MoPggCo~NMG^P#��=^F~@c�Cqot�_ZooSk;^]���]^yCo7Mo?NCgyCo7MoPggCo~NMG^P#^R�7Cg^V^A_���^?^@^A�_ZooSoBbg6^@g^_�@gg��g!T^[ asan output: root@f960c0e3747a:cat /crashes/poc | ./cxxfilt ASAN:SIGSEGV = ==35495==ERROR: AddressSanitizer: stack-overflow on address 0x7ffcda322ff8 (pc 0x006a0e3f bp 0x7ffcda323000 sp 0x7ffcda322ff0 T0) #0 0x6a0e3e in peek rust-demangle.c:84 #1 0x6a0f96 in next rust-demangle.c:105 #2 0x6a478f in demangle_type rust-demangle.c:864 #3 0x6a5110 in demangle_type rust-demangle.c:1024 #4 0x6a5110 in demangle_type rust-demangle.c:1024 #5 0x6a5110 in demangle_type rust-demangle.c:1024 #6 0x6a5110 in demangle_type rust-demangle.c:1024 #7 0x6a5110 in demangle_type rust-demangle.c:1024 #8 0x6a5110 in demangle_type rust-demangle.c:1024 #9 0x6a5110 in demangle_type rust-demangle.c:1024 #10 0x6a5110 in demangle_type rust-demangle.c:1024 #11 0x6a5110 in demangle_type rust-demangle.c:1024 #12 0x6a5110 in demangle_type rust-demangle.c:1024 #13 0x6a5110 in demangle_type rust-demangle.c:1024 #14 0x6a5110 in demangle_type rust-demangle.c:1024 #15 0x6a5110 in demangle_type rust-demangle.c:1024 #16 0x6a5110 in demangle_type rust-demangle.c:1024 #17 0x6a5110 in demangle_type rust-demangle.c:1024 #18 0x6a5110 in demangle_type rust-demangle.c:1024 #19 0x6a5110 in demangle_type rust-demangle.c:1024 #20 0x6a5110 in demangle_type rust-demangle.c:1024 #21 0x6a5110 in demangle_type rust-demangle.c:1024 #22 0x6a5110 in demangle_type rust-demangle.c:1024 #23 0x6a5110 in demangle_type rust-demangle.c:1024 #24 0x6a5110 in demangle_type rust-demangle.c:1024 #25 0x6a5110 in demangle_type rust-demangle.c:1024 #26 0x6a5110 in demangle_type rust-demangle.c:1024 #27 0x6a5110 in demangle_type rust-demangle.c:1024 #28 0x6a5110 in demangle_type rust-demangle.c:1024 #29 0x6a5110 in demangle_type rust-demangle.c:1024 #30 0x6a5110 in demangle_type rust-demangle.c:1024 #31 0x6a5110 in demangle_type rust-demangle.c:1024 #32 0x6a5110 in demangle_type rust-demangle.c:1024 #33 0x6a5110 in demangle_type rust-demangle.c:1024 #34 0x6a5110 in demangle_type rust-demangle.c:1024 #35 0x6a5110 in demangle_type rust-demangle.c:1024 #36 0x6a5110 in demangle_type rust-demangle.c:1024 #37 0x6a5110 in demangle_type rust-demangle.c:1024 #38 0x6a5110 in demangle_type rust-demangle.c:1024 #39 0x6a5110 in demangle_type rust-demangle.c:1024 #40 0x6a5110 in demangle_type rust-demangle.c:1024 #41 0x6a5110 in demangle_type rust-demangle.c:1024 #42 0x6a5110 in demangle_type rust-demangle.c:1024 #43 0x6a5110 in demangle_type rust-demangle.c:1024 #44 0x6a5110 in demangle_type rust-demangle.c:1024 #45 0x6a5110 in demangle_type rust-demangle.c:1024 #46 0x6a5110 in demangle_type rust-demangle.c:1024 #47 0x6a5110 in demangle_type rust-demangle.c:1024 #48 0x6a5110 in demangle_type rust-demangle.c:1024 #49 0x6a5110 in demangle_type rust-demangle.c:1024 #50 0x6a5110 in demangle_type rust-demangle.c:1024 #51 0x6a5110 in demangle_type rust-demangle.c:1024 #52 0x6a5110 in demangle_type rust-demangle.c:1024 #53 0x6a5110 in demangle_type rust-demangle.c:1024 #54 0x6a5110 in demangle_type rust-demangle.c:1024 #55 0x6a5110 in demangle_type rust-demangle.c:1024 #56 0x6a5110 in demangle_type rust-demangle.c:1024 #57 0x6a5110 in demangle_type rust-demangle.c:1024 #58 0x6a5110 in demangle_type rust-demangle.c:1024 #59 0x6a5110 in demangle_type rust-demangle.c:1024 #60 0x6a5110 in demangle_type rust-demangle.c:1024 #61 0x6a5110 in demangle_type rust-demangle.c:1024 #62 0x6a5110 in demangle_type rust-demangle.c:1024 #63 0x6a5110 in demangle_type rust-demangle.c:1024 #64 0x6a5110 in demangle_type rust-demangle.c:1024 #65 0x6a5110 in demangle_type rust-demangle.c:1024 #66 0x6a5110 in demangle_type rust-demangle.c:1024 #67 0x6a5110 in demangle_type rust-demangle.c:1024
[Touch-packages] [Bug 1927078] [NEW] Don't allow useradd to use fully numeric names
Public bug reported: [Description] Fully numeric names support in Ubuntu is inconsistent in Focal onwards because systemd does not like them[1] but are still allowed by default by useradd, leaving the session behavior in hands of the running applications. Two examples: 1. After creating a user named "0", the user can log in via ssh or console but loginctl won't create a session for it: root@focal:/home/ubuntu# useradd -m 0 root@focal:/home/ubuntu# id 0 uid=1005(0) gid=1005(0) groups=1005(0) .. 0@192.168.122.6's password: Welcome to Ubuntu 20.04.2 LTS (GNU/Linux 5.8.0-48-generic x86_64) Last login: Thu Apr 8 16:17:06 2021 from 192.168.122.1 $ loginctl No sessions. $ w 16:20:09 up 4 min, 1 user, load average: 0.03, 0.14, 0.08 USER TTY FROM LOGIN@ IDLE JCPU PCPU WHAT 0pts/0192.168.122.116:170.00s 0.00s 0.00s w And pam-systemd shows the following message: Apr 08 16:17:06 focal sshd[1584]: pam_unix(sshd:session): session opened for user 0 by (uid=0) Apr 08 16:17:06 focal sshd[1584]: pam_systemd(sshd:session): pam-systemd initializing Apr 08 16:17:06 focal sshd[1584]: pam_systemd(sshd:session): Failed to get user record: Invalid argument 2. With that same username, every successful authentication in gdm will loop back to gdm again instead of starting gnome, making the user unable to login. Making useradd fail (unless --badnames is set) when a fully numeric name is used will make the default OS behavior consistent. [Other info] - Upstream does not support fully numeric usernames - useradd has a --badnames parameter that would still allow the use of these type of names ** Affects: shadow (Ubuntu) Importance: Undecided Status: New ** Affects: shadow (Ubuntu Focal) Importance: Undecided Status: New ** Affects: shadow (Ubuntu Groovy) Importance: Undecided Status: New ** Affects: shadow (Ubuntu Hirsute) Importance: Undecided Status: New ** Affects: shadow (Ubuntu Impish) Importance: Undecided Status: New ** Also affects: shadow (Ubuntu Groovy) Importance: Undecided Status: New ** Also affects: shadow (Ubuntu Hirsute) Importance: Undecided Status: New ** Also affects: shadow (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: shadow (Ubuntu Impish) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to shadow in Ubuntu. https://bugs.launchpad.net/bugs/1927078 Title: Don't allow useradd to use fully numeric names Status in shadow package in Ubuntu: New Status in shadow source package in Focal: New Status in shadow source package in Groovy: New Status in shadow source package in Hirsute: New Status in shadow source package in Impish: New Bug description: [Description] Fully numeric names support in Ubuntu is inconsistent in Focal onwards because systemd does not like them[1] but are still allowed by default by useradd, leaving the session behavior in hands of the running applications. Two examples: 1. After creating a user named "0", the user can log in via ssh or console but loginctl won't create a session for it: root@focal:/home/ubuntu# useradd -m 0 root@focal:/home/ubuntu# id 0 uid=1005(0) gid=1005(0) groups=1005(0) .. 0@192.168.122.6's password: Welcome to Ubuntu 20.04.2 LTS (GNU/Linux 5.8.0-48-generic x86_64) Last login: Thu Apr 8 16:17:06 2021 from 192.168.122.1 $ loginctl No sessions. $ w 16:20:09 up 4 min, 1 user, load average: 0.03, 0.14, 0.08 USER TTY FROM LOGIN@ IDLE JCPU PCPU WHAT 0pts/0192.168.122.116:170.00s 0.00s 0.00s w And pam-systemd shows the following message: Apr 08 16:17:06 focal sshd[1584]: pam_unix(sshd:session): session opened for user 0 by (uid=0) Apr 08 16:17:06 focal sshd[1584]: pam_systemd(sshd:session): pam-systemd initializing Apr 08 16:17:06 focal sshd[1584]: pam_systemd(sshd:session): Failed to get user record: Invalid argument 2. With that same username, every successful authentication in gdm will loop back to gdm again instead of starting gnome, making the user unable to login. Making useradd fail (unless --badnames is set) when a fully numeric name is used will make the default OS behavior consistent. [Other info] - Upstream does not support fully numeric usernames - useradd has a --badnames parameter that would still allow the use of these type of names To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shadow/+bug/1927078/+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 1927063] Re: Terminal prompt got strangely replicated when resizing terminal horizontally
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: bash (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bash in Ubuntu. https://bugs.launchpad.net/bugs/1927063 Title: Terminal prompt got strangely replicated when resizing terminal horizontally Status in bash package in Ubuntu: Confirmed Status in mate-terminal package in Ubuntu: Confirmed Status in vte2.91 package in Ubuntu: Confirmed Bug description: Steps to reproduce: 1. Have Ubuntu installed 2. Launch MATE Terminal 3. Navigate to some folder with long name - `cd /usr/share/doc/ayatana-indicator-application` 4. Resize terminal horizontally Expected results: * terminal shows the same "user@host:/usr/share/doc/ayatana-indicator-application$" with single occurrence Actual results: * terminal shows multiple occurrencies of "user@host:/usr/share/doc/ayatana-indicator-application$" (see attached screencast) ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: mate-terminal 1.24.1-1 ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 Uname: Linux 5.11.0-16-generic x86_64 ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: MATE Date: Tue May 4 10:54:59 2021 InstallationDate: Installed on 2021-04-23 (10 days ago) InstallationMedia: Ubuntu-MATE 21.04 "Hirsute Hippo" - Release amd64 (20210420) SourcePackage: mate-terminal UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bash/+bug/1927063/+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 1927063] Re: Terminal prompt got strangely replicated when resizing terminal horizontally
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: mate-terminal (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bash in Ubuntu. https://bugs.launchpad.net/bugs/1927063 Title: Terminal prompt got strangely replicated when resizing terminal horizontally Status in bash package in Ubuntu: Confirmed Status in mate-terminal package in Ubuntu: Confirmed Status in vte2.91 package in Ubuntu: Confirmed Bug description: Steps to reproduce: 1. Have Ubuntu installed 2. Launch MATE Terminal 3. Navigate to some folder with long name - `cd /usr/share/doc/ayatana-indicator-application` 4. Resize terminal horizontally Expected results: * terminal shows the same "user@host:/usr/share/doc/ayatana-indicator-application$" with single occurrence Actual results: * terminal shows multiple occurrencies of "user@host:/usr/share/doc/ayatana-indicator-application$" (see attached screencast) ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: mate-terminal 1.24.1-1 ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 Uname: Linux 5.11.0-16-generic x86_64 ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: MATE Date: Tue May 4 10:54:59 2021 InstallationDate: Installed on 2021-04-23 (10 days ago) InstallationMedia: Ubuntu-MATE 21.04 "Hirsute Hippo" - Release amd64 (20210420) SourcePackage: mate-terminal UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bash/+bug/1927063/+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 1927063] Re: Terminal prompt got strangely replicated when resizing terminal horizontally
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: vte2.91 (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bash in Ubuntu. https://bugs.launchpad.net/bugs/1927063 Title: Terminal prompt got strangely replicated when resizing terminal horizontally Status in bash package in Ubuntu: Confirmed Status in mate-terminal package in Ubuntu: Confirmed Status in vte2.91 package in Ubuntu: Confirmed Bug description: Steps to reproduce: 1. Have Ubuntu installed 2. Launch MATE Terminal 3. Navigate to some folder with long name - `cd /usr/share/doc/ayatana-indicator-application` 4. Resize terminal horizontally Expected results: * terminal shows the same "user@host:/usr/share/doc/ayatana-indicator-application$" with single occurrence Actual results: * terminal shows multiple occurrencies of "user@host:/usr/share/doc/ayatana-indicator-application$" (see attached screencast) ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: mate-terminal 1.24.1-1 ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 Uname: Linux 5.11.0-16-generic x86_64 ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: MATE Date: Tue May 4 10:54:59 2021 InstallationDate: Installed on 2021-04-23 (10 days ago) InstallationMedia: Ubuntu-MATE 21.04 "Hirsute Hippo" - Release amd64 (20210420) SourcePackage: mate-terminal UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bash/+bug/1927063/+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 1888934] Re: Indicator is shown twice
Ubuntu 20.04.2 (desktop) with kernel 5.4.0-72-generic all up to date to latest @ 4/5/2021 Bluetooth-indicator is shown twice after boot today as shown in the screenshot of the bug filer -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-bluetooth in Ubuntu. https://bugs.launchpad.net/bugs/1888934 Title: Indicator is shown twice Status in indicator-bluetooth package in Ubuntu: Confirmed Bug description: See the screenshot. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: indicator-bluetooth 0.0.6+17.10.20170605-0ubuntu3 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 NonfreeKernelModules: lkp_Ubuntu_5_4_0_40_44_generic_69 nvidia ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: X-Cinnamon Date: Sat Jul 25 12:03:34 2020 InstallationDate: Installed on 2013-10-11 (2478 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) SourcePackage: indicator-bluetooth UpgradeStatus: Upgraded to focal on 2020-07-12 (12 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-bluetooth/+bug/1888934/+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 1888934] Re: Indicator is shown twice
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: indicator-bluetooth (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-bluetooth in Ubuntu. https://bugs.launchpad.net/bugs/1888934 Title: Indicator is shown twice Status in indicator-bluetooth package in Ubuntu: Confirmed Bug description: See the screenshot. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: indicator-bluetooth 0.0.6+17.10.20170605-0ubuntu3 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 NonfreeKernelModules: lkp_Ubuntu_5_4_0_40_44_generic_69 nvidia ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: X-Cinnamon Date: Sat Jul 25 12:03:34 2020 InstallationDate: Installed on 2013-10-11 (2478 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) SourcePackage: indicator-bluetooth UpgradeStatus: Upgraded to focal on 2020-07-12 (12 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-bluetooth/+bug/1888934/+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 1927070] Re: stack-overflow on GNU libiberty/rust-demangle.c:84 peek
** Summary changed: - stack-overflow on GNU libiberty/rust-demangle.c:84 peek + stack-overflow on GNU libiberty/rust-demangle.c:1024 demangle_type -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to binutils in Ubuntu. https://bugs.launchpad.net/bugs/1927070 Title: stack-overflow on GNU libiberty/rust-demangle.c:1024 demangle_type Status in binutils package in Ubuntu: New Bug description: stack-overflowon GNU libiberty/rust-demangle.c:84 peek when we run cat /crashes/poc | ./cxxfilt /crashes/poc: F}��.]]��_RYFB1_��z^A^R]M�^?N�^K^]�J^@^@^@^@^@^@^@^@�^A^@��]^yCo#Mo?NCgyCo7MoPggCo~NMG^P#��=^F~@c�Cqot�_ZooSk;^]���]^yCo7Mo?NCgyCo7MoPggCo~NMG^P#^R�7Cg^V^A_���^?^@^A�_ZooSoBbg6^@g^_�@gg��g!T^[ asan output: root@f960c0e3747a:cat /crashes/poc | ./cxxfilt ASAN:SIGSEGV = ==35495==ERROR: AddressSanitizer: stack-overflow on address 0x7ffcda322ff8 (pc 0x006a0e3f bp 0x7ffcda323000 sp 0x7ffcda322ff0 T0) #0 0x6a0e3e in peek rust-demangle.c:84 #1 0x6a0f96 in next rust-demangle.c:105 #2 0x6a478f in demangle_type rust-demangle.c:864 #3 0x6a5110 in demangle_type rust-demangle.c:1024 #4 0x6a5110 in demangle_type rust-demangle.c:1024 #5 0x6a5110 in demangle_type rust-demangle.c:1024 #6 0x6a5110 in demangle_type rust-demangle.c:1024 #7 0x6a5110 in demangle_type rust-demangle.c:1024 #8 0x6a5110 in demangle_type rust-demangle.c:1024 #9 0x6a5110 in demangle_type rust-demangle.c:1024 #10 0x6a5110 in demangle_type rust-demangle.c:1024 #11 0x6a5110 in demangle_type rust-demangle.c:1024 #12 0x6a5110 in demangle_type rust-demangle.c:1024 #13 0x6a5110 in demangle_type rust-demangle.c:1024 #14 0x6a5110 in demangle_type rust-demangle.c:1024 #15 0x6a5110 in demangle_type rust-demangle.c:1024 #16 0x6a5110 in demangle_type rust-demangle.c:1024 #17 0x6a5110 in demangle_type rust-demangle.c:1024 #18 0x6a5110 in demangle_type rust-demangle.c:1024 #19 0x6a5110 in demangle_type rust-demangle.c:1024 #20 0x6a5110 in demangle_type rust-demangle.c:1024 #21 0x6a5110 in demangle_type rust-demangle.c:1024 #22 0x6a5110 in demangle_type rust-demangle.c:1024 #23 0x6a5110 in demangle_type rust-demangle.c:1024 #24 0x6a5110 in demangle_type rust-demangle.c:1024 #25 0x6a5110 in demangle_type rust-demangle.c:1024 #26 0x6a5110 in demangle_type rust-demangle.c:1024 #27 0x6a5110 in demangle_type rust-demangle.c:1024 #28 0x6a5110 in demangle_type rust-demangle.c:1024 #29 0x6a5110 in demangle_type rust-demangle.c:1024 #30 0x6a5110 in demangle_type rust-demangle.c:1024 #31 0x6a5110 in demangle_type rust-demangle.c:1024 #32 0x6a5110 in demangle_type rust-demangle.c:1024 #33 0x6a5110 in demangle_type rust-demangle.c:1024 #34 0x6a5110 in demangle_type rust-demangle.c:1024 #35 0x6a5110 in demangle_type rust-demangle.c:1024 #36 0x6a5110 in demangle_type rust-demangle.c:1024 #37 0x6a5110 in demangle_type rust-demangle.c:1024 #38 0x6a5110 in demangle_type rust-demangle.c:1024 #39 0x6a5110 in demangle_type rust-demangle.c:1024 #40 0x6a5110 in demangle_type rust-demangle.c:1024 #41 0x6a5110 in demangle_type rust-demangle.c:1024 #42 0x6a5110 in demangle_type rust-demangle.c:1024 #43 0x6a5110 in demangle_type rust-demangle.c:1024 #44 0x6a5110 in demangle_type rust-demangle.c:1024 #45 0x6a5110 in demangle_type rust-demangle.c:1024 #46 0x6a5110 in demangle_type rust-demangle.c:1024 #47 0x6a5110 in demangle_type rust-demangle.c:1024 #48 0x6a5110 in demangle_type rust-demangle.c:1024 #49 0x6a5110 in demangle_type rust-demangle.c:1024 #50 0x6a5110 in demangle_type rust-demangle.c:1024 #51 0x6a5110 in demangle_type rust-demangle.c:1024 #52 0x6a5110 in demangle_type rust-demangle.c:1024 #53 0x6a5110 in demangle_type rust-demangle.c:1024 #54 0x6a5110 in demangle_type rust-demangle.c:1024 #55 0x6a5110 in demangle_type rust-demangle.c:1024 #56 0x6a5110 in demangle_type rust-demangle.c:1024 #57 0x6a5110 in demangle_type rust-demangle.c:1024 #58 0x6a5110 in demangle_type rust-demangle.c:1024 #59 0x6a5110 in demangle_type rust-demangle.c:1024 #60 0x6a5110 in demangle_type rust-demangle.c:1024 #61 0x6a5110 in demangle_type rust-demangle.c:1024 #62 0x6a5110 in demangle_type rust-demangle.c:1024 #63 0x6a5110 in demangle_type rust-demangle.c:1024 #64 0x6a5110 in demangle_type rust-demangle.c:1024 #65 0x6a5110 in demangle_type rust-demangle.c:1024 #66 0x6a5110 in demangle_type rust-demangle.c:1024 #67 0x6a5110 in demangle_type rust-demangle.c:1024 #68 0x6a5110 in demangle_type
[Touch-packages] [Bug 1927070] [NEW] stack-overflow on GNU libiberty/rust-demangle.c:84 peek
Public bug reported: stack-overflowon GNU libiberty/rust-demangle.c:84 peek when we run cat /crashes/poc | ./cxxfilt /crashes/poc: F}��.]]��_RYFB1_��z^A^R]M�^?N�^K^]�J^@^@^@^@^@^@^@^@�^A^@��]^yCo#Mo?NCgyCo7MoPggCo~NMG^P#��=^F~@c�Cqot�_ZooSk;^]���]^yCo7Mo?NCgyCo7MoPggCo~NMG^P#^R�7Cg^V^A_���^?^@^A�_ZooSoBbg6^@g^_�@gg��g!T^[ asan output: root@f960c0e3747a:cat /crashes/poc | ./cxxfilt ASAN:SIGSEGV = ==35495==ERROR: AddressSanitizer: stack-overflow on address 0x7ffcda322ff8 (pc 0x006a0e3f bp 0x7ffcda323000 sp 0x7ffcda322ff0 T0) #0 0x6a0e3e in peek rust-demangle.c:84 #1 0x6a0f96 in next rust-demangle.c:105 #2 0x6a478f in demangle_type rust-demangle.c:864 #3 0x6a5110 in demangle_type rust-demangle.c:1024 #4 0x6a5110 in demangle_type rust-demangle.c:1024 #5 0x6a5110 in demangle_type rust-demangle.c:1024 #6 0x6a5110 in demangle_type rust-demangle.c:1024 #7 0x6a5110 in demangle_type rust-demangle.c:1024 #8 0x6a5110 in demangle_type rust-demangle.c:1024 #9 0x6a5110 in demangle_type rust-demangle.c:1024 #10 0x6a5110 in demangle_type rust-demangle.c:1024 #11 0x6a5110 in demangle_type rust-demangle.c:1024 #12 0x6a5110 in demangle_type rust-demangle.c:1024 #13 0x6a5110 in demangle_type rust-demangle.c:1024 #14 0x6a5110 in demangle_type rust-demangle.c:1024 #15 0x6a5110 in demangle_type rust-demangle.c:1024 #16 0x6a5110 in demangle_type rust-demangle.c:1024 #17 0x6a5110 in demangle_type rust-demangle.c:1024 #18 0x6a5110 in demangle_type rust-demangle.c:1024 #19 0x6a5110 in demangle_type rust-demangle.c:1024 #20 0x6a5110 in demangle_type rust-demangle.c:1024 #21 0x6a5110 in demangle_type rust-demangle.c:1024 #22 0x6a5110 in demangle_type rust-demangle.c:1024 #23 0x6a5110 in demangle_type rust-demangle.c:1024 #24 0x6a5110 in demangle_type rust-demangle.c:1024 #25 0x6a5110 in demangle_type rust-demangle.c:1024 #26 0x6a5110 in demangle_type rust-demangle.c:1024 #27 0x6a5110 in demangle_type rust-demangle.c:1024 #28 0x6a5110 in demangle_type rust-demangle.c:1024 #29 0x6a5110 in demangle_type rust-demangle.c:1024 #30 0x6a5110 in demangle_type rust-demangle.c:1024 #31 0x6a5110 in demangle_type rust-demangle.c:1024 #32 0x6a5110 in demangle_type rust-demangle.c:1024 #33 0x6a5110 in demangle_type rust-demangle.c:1024 #34 0x6a5110 in demangle_type rust-demangle.c:1024 #35 0x6a5110 in demangle_type rust-demangle.c:1024 #36 0x6a5110 in demangle_type rust-demangle.c:1024 #37 0x6a5110 in demangle_type rust-demangle.c:1024 #38 0x6a5110 in demangle_type rust-demangle.c:1024 #39 0x6a5110 in demangle_type rust-demangle.c:1024 #40 0x6a5110 in demangle_type rust-demangle.c:1024 #41 0x6a5110 in demangle_type rust-demangle.c:1024 #42 0x6a5110 in demangle_type rust-demangle.c:1024 #43 0x6a5110 in demangle_type rust-demangle.c:1024 #44 0x6a5110 in demangle_type rust-demangle.c:1024 #45 0x6a5110 in demangle_type rust-demangle.c:1024 #46 0x6a5110 in demangle_type rust-demangle.c:1024 #47 0x6a5110 in demangle_type rust-demangle.c:1024 #48 0x6a5110 in demangle_type rust-demangle.c:1024 #49 0x6a5110 in demangle_type rust-demangle.c:1024 #50 0x6a5110 in demangle_type rust-demangle.c:1024 #51 0x6a5110 in demangle_type rust-demangle.c:1024 #52 0x6a5110 in demangle_type rust-demangle.c:1024 #53 0x6a5110 in demangle_type rust-demangle.c:1024 #54 0x6a5110 in demangle_type rust-demangle.c:1024 #55 0x6a5110 in demangle_type rust-demangle.c:1024 #56 0x6a5110 in demangle_type rust-demangle.c:1024 #57 0x6a5110 in demangle_type rust-demangle.c:1024 #58 0x6a5110 in demangle_type rust-demangle.c:1024 #59 0x6a5110 in demangle_type rust-demangle.c:1024 #60 0x6a5110 in demangle_type rust-demangle.c:1024 #61 0x6a5110 in demangle_type rust-demangle.c:1024 #62 0x6a5110 in demangle_type rust-demangle.c:1024 #63 0x6a5110 in demangle_type rust-demangle.c:1024 #64 0x6a5110 in demangle_type rust-demangle.c:1024 #65 0x6a5110 in demangle_type rust-demangle.c:1024 #66 0x6a5110 in demangle_type rust-demangle.c:1024 #67 0x6a5110 in demangle_type rust-demangle.c:1024 #68 0x6a5110 in demangle_type rust-demangle.c:1024 #69 0x6a5110 in demangle_type rust-demangle.c:1024 #70 0x6a5110 in demangle_type rust-demangle.c:1024 #71 0x6a5110 in demangle_type rust-demangle.c:1024 #72 0x6a5110 in demangle_type rust-demangle.c:1024 #73 0x6a5110 in demangle_type rust-demangle.c:1024 #74 0x6a5110 in demangle_type rust-demangle.c:1024 #75 0x6a5110 in demangle_type rust-demangle.c:1024 #76 0x6a5110 in demangle_type rust-demangle.c:1024 #77 0x6a5110 in demangle_type rust-demangle.c:1024 #78 0x6a5110 in demangle_type rust-demangle.c:1024 #79 0x6a5110 in demangle_type
[Touch-packages] [Bug 1254628] Re: update-notifier crashed with SIGSEGV in rate_limiter_free()
upstream consider that one fixed and there was no new activity in years, closing please open a new bug if you still get an issue in the current serie ** Changed in: glib2.0 (Ubuntu) Status: Confirmed => 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/1254628 Title: update-notifier crashed with SIGSEGV in rate_limiter_free() Status in GLib: Fix Released Status in glib2.0 package in Ubuntu: Fix Released Bug description: 1) patben@esp-patben-amd:~$ lsb_release -rd Description: Ubuntu 13.10 Release: 13.10 2) patben@esp-patben-amd:~$ apt-cache policy update-notifier update-notifier: Zainstalowana: 0.147.1 Kandydująca: 0.147.1 Tabela wersji: *** 0.147.1 0 500 http://archive.ubuntu.com/ubuntu/ saucy-proposed/main amd64 Packages 100 /var/lib/dpkg/status 0.147 0 500 http://archive.ubuntu.com/ubuntu/ saucy/main amd64 Packages ProblemType: Crash DistroRelease: Ubuntu 13.10 Package: update-notifier 0.147.1 ProcVersionSignature: Ubuntu 3.11.0-14.21-generic 3.11.7 Uname: Linux 3.11.0-14-generic x86_64 NonfreeKernelModules: fglrx ApportVersion: 2.12.5-0ubuntu2.1 Architecture: amd64 Date: Mon Nov 25 07:54:33 2013 ExecutablePath: /usr/bin/update-notifier InstallationDate: Installed on 2013-05-28 (180 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) MarkForUpload: True ProcCmdline: update-notifier SegvAnalysis: Segfault happened at: 0x7fbf4f501ae4:mov(%rdi),%rdi PC (0x7fbf4f501ae4) ok source "(%rdi)" (0x) not located in a known VMA region (needed readable region)! destination "%rdi" ok Stack memory exhausted (SP below stack segment) SegvReason: reading NULL VMA Signal: 11 SourcePackage: update-notifier StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 g_file_monitor_emit_event () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 Title: update-notifier crashed with SIGSEGV in g_file_monitor_emit_event() UpgradeStatus: Upgraded to saucy on 2013-10-30 (25 days ago) UserGroups: adm cdrom dip libvirtd lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/glib/+bug/1254628/+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 1254628] Re: update-notifier crashed with SIGSEGV in rate_limiter_free()
@thedgofficial : this is very old bug report from late year 2013. I think its better to report new one with full data, and reference this bur report number in your report. -- 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/1254628 Title: update-notifier crashed with SIGSEGV in rate_limiter_free() Status in GLib: Fix Released Status in glib2.0 package in Ubuntu: Fix Released Bug description: 1) patben@esp-patben-amd:~$ lsb_release -rd Description: Ubuntu 13.10 Release: 13.10 2) patben@esp-patben-amd:~$ apt-cache policy update-notifier update-notifier: Zainstalowana: 0.147.1 Kandydująca: 0.147.1 Tabela wersji: *** 0.147.1 0 500 http://archive.ubuntu.com/ubuntu/ saucy-proposed/main amd64 Packages 100 /var/lib/dpkg/status 0.147 0 500 http://archive.ubuntu.com/ubuntu/ saucy/main amd64 Packages ProblemType: Crash DistroRelease: Ubuntu 13.10 Package: update-notifier 0.147.1 ProcVersionSignature: Ubuntu 3.11.0-14.21-generic 3.11.7 Uname: Linux 3.11.0-14-generic x86_64 NonfreeKernelModules: fglrx ApportVersion: 2.12.5-0ubuntu2.1 Architecture: amd64 Date: Mon Nov 25 07:54:33 2013 ExecutablePath: /usr/bin/update-notifier InstallationDate: Installed on 2013-05-28 (180 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) MarkForUpload: True ProcCmdline: update-notifier SegvAnalysis: Segfault happened at: 0x7fbf4f501ae4:mov(%rdi),%rdi PC (0x7fbf4f501ae4) ok source "(%rdi)" (0x) not located in a known VMA region (needed readable region)! destination "%rdi" ok Stack memory exhausted (SP below stack segment) SegvReason: reading NULL VMA Signal: 11 SourcePackage: update-notifier StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 g_file_monitor_emit_event () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 Title: update-notifier crashed with SIGSEGV in g_file_monitor_emit_event() UpgradeStatus: Upgraded to saucy on 2013-10-30 (25 days ago) UserGroups: adm cdrom dip libvirtd lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/glib/+bug/1254628/+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 1926062] Re: [hirsute] Can't turn bluetooth on again after turning it off
This might just be a GUI bug in gnome-control-center. Someone will need to tinker with bluetoothctl to investigate further. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1926062 Title: [hirsute] Can't turn bluetooth on again after turning it off Status in bluez package in Ubuntu: Confirmed Status in gnome-control-center package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: When ever i Turn on my system or restart bluetooth is open any it connects to any device. But when i turn off bluetooth and try to turn it on again. it neither turns on nor scans/connects to any device. This is happening since I updated my system to ubuntu 21.04 LTS ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: bluetooth (not installed) ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 Uname: Linux 5.11.0-16-generic x86_64 ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sun Apr 25 15:09:23 2021 InstallationDate: Installed on 2020-12-15 (130 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) InterestingModules: rfcomm bnep btusb bluetooth MachineType: LENOVO 80TR ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-16-generic root=UUID=7c507bd4-c66c-4233-a64e-804f6df5412b ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: Upgraded to hirsute on 2021-04-22 (2 days ago) dmi.bios.date: 07/31/2017 dmi.bios.release: 1.29 dmi.bios.vendor: LENOVO dmi.bios.version: 3UCN29WW dmi.board.asset.tag: No Asset Tag dmi.board.name: Nano 5B1 dmi.board.vendor: LENOVO dmi.board.version: No DPK dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad 110-15AST dmi.ec.firmware.release: 1.29 dmi.modalias: dmi:bvnLENOVO:bvr3UCN29WW:bd07/31/2017:br1.29:efr1.29:svnLENOVO:pn80TR:pvrLenovoideapad110-15AST:rvnLENOVO:rnNano5B1:rvrNoDPK:cvnLENOVO:ct10:cvrLenovoideapad110-15AST: dmi.product.family: IDEAPAD dmi.product.name: 80TR dmi.product.sku: LENOVO_MT_80TR_BU_idea_FM_Lenovo ideapad 110-15AST dmi.product.version: Lenovo ideapad 110-15AST dmi.sys.vendor: LENOVO hciconfig: hci0:Type: Primary Bus: USB BD Address: C8:3D:D4:84:E0:06 ACL MTU: 820:8 SCO MTU: 255:16 DOWN RX bytes:744804 acl:76 sco:0 events:105989 errors:0 TX bytes:51871528 acl:113157 sco:0 commands:192 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1926062/+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 1923564] Re: BlueZ 5.58 release
** Attachment added: "bluez_5.58-0ubuntu1.debian.tar.xz" https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1923564/+attachment/5494657/+files/bluez_5.58-0ubuntu1.debian.tar.xz -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1923564 Title: BlueZ 5.58 release Status in bluez package in Ubuntu: In Progress Bug description: BlueZ 5.58 has been released. We should look at it for the 21.10 cycle... http://www.bluez.org/release-of-bluez-5-58-and-5-57/ https://mirrors.edge.kernel.org/pub/linux/bluetooth/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1923564/+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 1926062] Re: [hirsute] Can't turn bluetooth on again after turning it off
** Also affects: gnome-control-center (Ubuntu) Importance: Undecided Status: New ** Changed in: gnome-control-center (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1926062 Title: [hirsute] Can't turn bluetooth on again after turning it off Status in bluez package in Ubuntu: Confirmed Status in gnome-control-center package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: When ever i Turn on my system or restart bluetooth is open any it connects to any device. But when i turn off bluetooth and try to turn it on again. it neither turns on nor scans/connects to any device. This is happening since I updated my system to ubuntu 21.04 LTS ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: bluetooth (not installed) ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 Uname: Linux 5.11.0-16-generic x86_64 ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sun Apr 25 15:09:23 2021 InstallationDate: Installed on 2020-12-15 (130 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) InterestingModules: rfcomm bnep btusb bluetooth MachineType: LENOVO 80TR ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-16-generic root=UUID=7c507bd4-c66c-4233-a64e-804f6df5412b ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: Upgraded to hirsute on 2021-04-22 (2 days ago) dmi.bios.date: 07/31/2017 dmi.bios.release: 1.29 dmi.bios.vendor: LENOVO dmi.bios.version: 3UCN29WW dmi.board.asset.tag: No Asset Tag dmi.board.name: Nano 5B1 dmi.board.vendor: LENOVO dmi.board.version: No DPK dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad 110-15AST dmi.ec.firmware.release: 1.29 dmi.modalias: dmi:bvnLENOVO:bvr3UCN29WW:bd07/31/2017:br1.29:efr1.29:svnLENOVO:pn80TR:pvrLenovoideapad110-15AST:rvnLENOVO:rnNano5B1:rvrNoDPK:cvnLENOVO:ct10:cvrLenovoideapad110-15AST: dmi.product.family: IDEAPAD dmi.product.name: 80TR dmi.product.sku: LENOVO_MT_80TR_BU_idea_FM_Lenovo ideapad 110-15AST dmi.product.version: Lenovo ideapad 110-15AST dmi.sys.vendor: LENOVO hciconfig: hci0:Type: Primary Bus: USB BD Address: C8:3D:D4:84:E0:06 ACL MTU: 820:8 SCO MTU: 255:16 DOWN RX bytes:744804 acl:76 sco:0 events:105989 errors:0 TX bytes:51871528 acl:113157 sco:0 commands:192 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1926062/+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 1927063] Re: Terminal prompt got strangely replicated when resizing terminal horizontally
** Tags added: focal ** Tags added: groovy ** Tags added: impish -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bash in Ubuntu. https://bugs.launchpad.net/bugs/1927063 Title: Terminal prompt got strangely replicated when resizing terminal horizontally Status in bash package in Ubuntu: New Status in mate-terminal package in Ubuntu: New Status in vte2.91 package in Ubuntu: New Bug description: Steps to reproduce: 1. Have Ubuntu installed 2. Launch MATE Terminal 3. Navigate to some folder with long name - `cd /usr/share/doc/ayatana-indicator-application` 4. Resize terminal horizontally Expected results: * terminal shows the same "user@host:/usr/share/doc/ayatana-indicator-application$" with single occurrence Actual results: * terminal shows multiple occurrencies of "user@host:/usr/share/doc/ayatana-indicator-application$" (see attached screencast) ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: mate-terminal 1.24.1-1 ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 Uname: Linux 5.11.0-16-generic x86_64 ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: MATE Date: Tue May 4 10:54:59 2021 InstallationDate: Installed on 2021-04-23 (10 days ago) InstallationMedia: Ubuntu-MATE 21.04 "Hirsute Hippo" - Release amd64 (20210420) SourcePackage: mate-terminal UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bash/+bug/1927063/+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 1926062] Re: [hirsute] Can't turn bluetooth on again after turning it off
I'm preparing BlueZ 5.58 for Ubuntu 21.10 and the same bug just started happening there too. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1926062 Title: [hirsute] Can't turn bluetooth on again after turning it off Status in bluez package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: When ever i Turn on my system or restart bluetooth is open any it connects to any device. But when i turn off bluetooth and try to turn it on again. it neither turns on nor scans/connects to any device. This is happening since I updated my system to ubuntu 21.04 LTS ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: bluetooth (not installed) ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 Uname: Linux 5.11.0-16-generic x86_64 ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sun Apr 25 15:09:23 2021 InstallationDate: Installed on 2020-12-15 (130 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) InterestingModules: rfcomm bnep btusb bluetooth MachineType: LENOVO 80TR ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-16-generic root=UUID=7c507bd4-c66c-4233-a64e-804f6df5412b ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: Upgraded to hirsute on 2021-04-22 (2 days ago) dmi.bios.date: 07/31/2017 dmi.bios.release: 1.29 dmi.bios.vendor: LENOVO dmi.bios.version: 3UCN29WW dmi.board.asset.tag: No Asset Tag dmi.board.name: Nano 5B1 dmi.board.vendor: LENOVO dmi.board.version: No DPK dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad 110-15AST dmi.ec.firmware.release: 1.29 dmi.modalias: dmi:bvnLENOVO:bvr3UCN29WW:bd07/31/2017:br1.29:efr1.29:svnLENOVO:pn80TR:pvrLenovoideapad110-15AST:rvnLENOVO:rnNano5B1:rvrNoDPK:cvnLENOVO:ct10:cvrLenovoideapad110-15AST: dmi.product.family: IDEAPAD dmi.product.name: 80TR dmi.product.sku: LENOVO_MT_80TR_BU_idea_FM_Lenovo ideapad 110-15AST dmi.product.version: Lenovo ideapad 110-15AST dmi.sys.vendor: LENOVO hciconfig: hci0:Type: Primary Bus: USB BD Address: C8:3D:D4:84:E0:06 ACL MTU: 820:8 SCO MTU: 255:16 DOWN RX bytes:744804 acl:76 sco:0 events:105989 errors:0 TX bytes:51871528 acl:113157 sco:0 commands:192 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1926062/+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 1927063] [NEW] Terminal prompt got strangely replicated when resizing terminal horizontally
Public bug reported: Steps to reproduce: 1. Have Ubuntu installed 2. Launch MATE Terminal 3. Navigate to some folder with long name - `cd /usr/share/doc/ayatana-indicator-application` 4. Resize terminal horizontally Expected results: * terminal shows the same "user@host:/usr/share/doc/ayatana-indicator-application$" with single occurrence Actual results: * terminal shows multiple occurrencies of "user@host:/usr/share/doc/ayatana-indicator-application$" (see attached screencast) ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: mate-terminal 1.24.1-1 ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 Uname: Linux 5.11.0-16-generic x86_64 ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: MATE Date: Tue May 4 10:54:59 2021 InstallationDate: Installed on 2021-04-23 (10 days ago) InstallationMedia: Ubuntu-MATE 21.04 "Hirsute Hippo" - Release amd64 (20210420) SourcePackage: mate-terminal UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: bash (Ubuntu) Importance: Undecided Status: New ** Affects: mate-terminal (Ubuntu) Importance: Undecided Status: New ** Affects: vte2.91 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal hirsute ** Attachment added: "Screencast showing the issue" https://bugs.launchpad.net/bugs/1927063/+attachment/5494630/+files/terminal.gif ** Also affects: vte2.91 (Ubuntu) Importance: Undecided Status: New ** Also affects: bash (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bash in Ubuntu. https://bugs.launchpad.net/bugs/1927063 Title: Terminal prompt got strangely replicated when resizing terminal horizontally Status in bash package in Ubuntu: New Status in mate-terminal package in Ubuntu: New Status in vte2.91 package in Ubuntu: New Bug description: Steps to reproduce: 1. Have Ubuntu installed 2. Launch MATE Terminal 3. Navigate to some folder with long name - `cd /usr/share/doc/ayatana-indicator-application` 4. Resize terminal horizontally Expected results: * terminal shows the same "user@host:/usr/share/doc/ayatana-indicator-application$" with single occurrence Actual results: * terminal shows multiple occurrencies of "user@host:/usr/share/doc/ayatana-indicator-application$" (see attached screencast) ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: mate-terminal 1.24.1-1 ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 Uname: Linux 5.11.0-16-generic x86_64 ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: MATE Date: Tue May 4 10:54:59 2021 InstallationDate: Installed on 2021-04-23 (10 days ago) InstallationMedia: Ubuntu-MATE 21.04 "Hirsute Hippo" - Release amd64 (20210420) SourcePackage: mate-terminal UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bash/+bug/1927063/+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 1923564] Re: BlueZ 5.58 release
** Attachment added: "bluez_5.58.orig.tar.xz" https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1923564/+attachment/5494628/+files/bluez_5.58.orig.tar.xz -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1923564 Title: BlueZ 5.58 release Status in bluez package in Ubuntu: In Progress Bug description: BlueZ 5.58 has been released. We should look at it for the 21.10 cycle... http://www.bluez.org/release-of-bluez-5-58-and-5-57/ https://mirrors.edge.kernel.org/pub/linux/bluetooth/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1923564/+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 1923564] Re: BlueZ 5.58 release
** Changed in: bluez (Ubuntu) Assignee: (unassigned) => Daniel van Vugt (vanvugt) ** Changed in: bluez (Ubuntu) Importance: Undecided => Wishlist ** Changed in: bluez (Ubuntu) Status: New => In Progress -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1923564 Title: BlueZ 5.58 release Status in bluez package in Ubuntu: In Progress Bug description: BlueZ 5.58 has been released. We should look at it for the 21.10 cycle... http://www.bluez.org/release-of-bluez-5-58-and-5-57/ https://mirrors.edge.kernel.org/pub/linux/bluetooth/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1923564/+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 1754140] Re: Gnome gets stuck in overview mode
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: ubuntu-meta (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1754140 Title: Gnome gets stuck in overview mode Status in ubuntu-meta package in Ubuntu: Confirmed Bug description: I'm running Ubuntu 17.10, and I have repeatedly had a problem with the desktop environment getting stuck in overview mode. When stuck, I can close and select windows, and access the menus at on the top bar, but I cannot exit overview mode. The only solution I've found is to log out and log back in. I'm not exactly sure what combination of circumstances causes it to happen, but it seems to happen more often if invoked via the corner hover point. It also happens in both Wayland and Xorg. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: ubuntu-desktop 1.404.1 Uname: Linux 4.14.15-041415-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 CurrentDesktop: GNOME Date: Wed Mar 7 11:02:02 2018 InstallationDate: Installed on 2017-05-04 (307 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: ubuntu-meta UpgradeStatus: Upgraded to artful on 2017-10-29 (129 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1754140/+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 1754140] Re: Gnome gets stuck in overview mode
I also hit this within an hour of installing hippo (21.04) on a new machine, having made zero configuration changes anywhere. My guess is that it happened when I accidentally mashed a few keys at once (which may have included the windows key)...? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1754140 Title: Gnome gets stuck in overview mode Status in ubuntu-meta package in Ubuntu: Confirmed Bug description: I'm running Ubuntu 17.10, and I have repeatedly had a problem with the desktop environment getting stuck in overview mode. When stuck, I can close and select windows, and access the menus at on the top bar, but I cannot exit overview mode. The only solution I've found is to log out and log back in. I'm not exactly sure what combination of circumstances causes it to happen, but it seems to happen more often if invoked via the corner hover point. It also happens in both Wayland and Xorg. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: ubuntu-desktop 1.404.1 Uname: Linux 4.14.15-041415-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 CurrentDesktop: GNOME Date: Wed Mar 7 11:02:02 2018 InstallationDate: Installed on 2017-05-04 (307 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: ubuntu-meta UpgradeStatus: Upgraded to artful on 2017-10-29 (129 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1754140/+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 1925705] Re: 100% cpu
Which process is using 100% CPU? I also wonder if this is related to bug 1924624... ** Package changed: xorg (Ubuntu) => ubuntu ** Changed in: ubuntu Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1925705 Title: 100% cpu Status in Ubuntu: Incomplete Bug description: my spek i5 gen3 ram 8Gb ssd 512 fresh install and my cpu always 100% when open and run apps, like firefox, chrome ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.8.0-50.56~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-50-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 BootLog: CasperMD5CheckResult: skip CompositorRunning: None Date: Fri Apr 23 07:15:41 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: I just need to know a workaround GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo 3rd Gen Core processor Graphics Controller [17aa:21f3] InstallationDate: Installed on 2021-04-20 (2 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) MachineType: LENOVO 2349CTO ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-50-generic root=UUID=6e403edb-143d-4aa1-8a31-b84abf6175a9 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/07/2019 dmi.bios.release: 2.82 dmi.bios.vendor: LENOVO dmi.bios.version: G1ETC2WW (2.82 ) dmi.board.asset.tag: Not Available dmi.board.name: 2349CTO dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.ec.firmware.release: 1.14 dmi.modalias: dmi:bvnLENOVO:bvrG1ETC2WW(2.82):bd08/07/2019:br2.82:efr1.14:svnLENOVO:pn2349CTO:pvrThinkPadT430:rvnLENOVO:rn2349CTO:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad T430 dmi.product.name: 2349CTO dmi.product.sku: LENOVO_MT_2349 dmi.product.version: ThinkPad T430 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1925705/+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 1924184] Re: drive not showing
Sounds like this is about graphics drivers. This system has an Intel GPU so there are no additional graphics drivers. There is no bug here. ** Package changed: xorg (Ubuntu) => ubuntu ** Changed in: ubuntu Status: Incomplete => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1924184 Title: drive not showing Status in Ubuntu: Incomplete Bug description: i coudnt find graphic drive ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.8.0-49.55~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-49-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Apr 15 03:35:34 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu GraphicsCard: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Dell UHD Graphics 620 [1028:0844] Subsystem: Dell Jet PRO [Radeon R5 M230 / R7 M260DX / Radeon 520 Mobile] [1028:0844] InstallationDate: Installed on 2021-04-13 (1 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: Dell Inc. Vostro 3578 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-49-generic root=UUID=7cf915de-bb29-49e2-a9cc-0079efc75ed1 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/09/2020 dmi.bios.release: 1.10 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.10.0 dmi.board.name: 01Y7V4 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.10.0:bd01/09/2020:br1.10:svnDellInc.:pnVostro3578:pvr:rvnDellInc.:rn01Y7V4:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Vostro dmi.product.name: Vostro 3578 dmi.product.sku: 0844 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1924184/+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 1926062] Re: [hirsute] Can't turn bluetooth on again after turning it off
I was facing the same problem. My toggle was not at all working, neither from the top bar dropdown menu nor from the settings window. Switching on the toggle did not have any effect. I had also reported this bug. Someone in the comments had suggested a workaround to type this command in the terminal: systemctl restart Bluetooth This command kind of hard restarts the Bluetooth service and works for me for the time being until the bug is fixed. It might also help someone else. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1926062 Title: [hirsute] Can't turn bluetooth on again after turning it off Status in bluez package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: When ever i Turn on my system or restart bluetooth is open any it connects to any device. But when i turn off bluetooth and try to turn it on again. it neither turns on nor scans/connects to any device. This is happening since I updated my system to ubuntu 21.04 LTS ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: bluetooth (not installed) ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 Uname: Linux 5.11.0-16-generic x86_64 ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sun Apr 25 15:09:23 2021 InstallationDate: Installed on 2020-12-15 (130 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) InterestingModules: rfcomm bnep btusb bluetooth MachineType: LENOVO 80TR ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-16-generic root=UUID=7c507bd4-c66c-4233-a64e-804f6df5412b ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: Upgraded to hirsute on 2021-04-22 (2 days ago) dmi.bios.date: 07/31/2017 dmi.bios.release: 1.29 dmi.bios.vendor: LENOVO dmi.bios.version: 3UCN29WW dmi.board.asset.tag: No Asset Tag dmi.board.name: Nano 5B1 dmi.board.vendor: LENOVO dmi.board.version: No DPK dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad 110-15AST dmi.ec.firmware.release: 1.29 dmi.modalias: dmi:bvnLENOVO:bvr3UCN29WW:bd07/31/2017:br1.29:efr1.29:svnLENOVO:pn80TR:pvrLenovoideapad110-15AST:rvnLENOVO:rnNano5B1:rvrNoDPK:cvnLENOVO:ct10:cvrLenovoideapad110-15AST: dmi.product.family: IDEAPAD dmi.product.name: 80TR dmi.product.sku: LENOVO_MT_80TR_BU_idea_FM_Lenovo ideapad 110-15AST dmi.product.version: Lenovo ideapad 110-15AST dmi.sys.vendor: LENOVO hciconfig: hci0:Type: Primary Bus: USB BD Address: C8:3D:D4:84:E0:06 ACL MTU: 820:8 SCO MTU: 255:16 DOWN RX bytes:744804 acl:76 sco:0 events:105989 errors:0 TX bytes:51871528 acl:113157 sco:0 commands:192 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1926062/+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 1927019] Re: Xorg freeze
Thanks for the bug report. Next time the problem happens please reboot and then run: journalctl -b-1 > prevboot.txt and attach the resulting text file here. Although I notice the attached logs already show your SSD is experiencing hardware errors. You might need to replace the SSD: [ 1633.238345] pcieport 1:e0:06.0: AER: Corrected error received: 1:e1:00.0 [ 1633.238381] nvme 1:e1:00.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) [ 1633.238384] nvme 1:e1:00.0: device [15b7:5006] error status/mask=0001/e000 [ 1633.238387] nvme 1:e1:00.0:[ 0] RxErr (First) ** Summary changed: - Xorg freeze + System freeze ** Package changed: xorg (Ubuntu) => linux (Ubuntu) ** Changed in: linux (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1927019 Title: System freeze Status in linux package in Ubuntu: Incomplete Bug description: Ubuntu 21.04 Freeze sometime ( using wayland ) . A black screen appear from top to bottom and ubuntu doesn't react to any keyboard shortcut. It's appears, maybe after 2 hours of work. I didn't see this bug with my previous ubuntu 20.10. My computer is a new DELL XPS 13 - intel core i7. I disabled the 4K screen and I am using a resolution 1920x1080. I enabled the night mode. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: xorg 1:7.7+22ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 Uname: Linux 5.11.0-16-generic x86_64 ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue May 4 00:10:39 2021 DistUpgraded: Fresh install DistroCodename: hirsute DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GpuHangFrequency: Several times a day GpuHangReproducibility: Seems to happen randomly GpuHangStarted: Immediately after installing this version of Ubuntu GraphicsCard: Intel Corporation TigerLake GT2 [Iris Xe Graphics] [8086:9a49] (rev 01) (prog-if 00 [VGA controller]) Subsystem: Dell Iris Xe Graphics [1028:0a5c] InstallationDate: Installed on 2021-04-30 (3 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) MachineType: Dell Inc. XPS 13 9305 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/usr/bin/zsh ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-16-generic root=UUID=37473b6f-8714-4a48-91c1-f6964b09347d ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/13/2021 dmi.bios.release: 1.0 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.0.1 dmi.board.name: 0PPYW4 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.0.1:bd01/13/2021:br1.0:svnDellInc.:pnXPS139305:pvr:rvnDellInc.:rn0PPYW4:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9305 dmi.product.sku: 0A5C dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.104-1build1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.1-2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1927019/+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 1926976] Re: during mouse drag operations I'm getting undesired/unprompted dropping and potentially picking up of something else
It sounds like you are getting spurious mouse button (or even keyboard) events from one of your input devices, which will randomly break drag operations. This does happen to people occasionally and in every case (so far) it turns out to be a broken input device. Please try unplugging all input devices from the machine and then adding them back in one-by-one. Please also try a different mouse if you can, and hit all the keys on your keyboard in case one of them is sticking or causing unwanted events. ** Package changed: xorg (Ubuntu) => ubuntu ** Changed in: ubuntu Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1926976 Title: during mouse drag operations I'm getting undesired/unprompted dropping and potentially picking up of something else Status in Ubuntu: Incomplete Bug description: I am not really sure this is an Xorg problem. Since my last system update (upon the system prompting), I think less than a week ago, I have noticed this troubling intermittent behavior. I go to drag (mouse-initiated) a window across some screen distances (between external monitors and my laptop's builtin monitor) the window will get dropped without me releasing the mouse button before arriving at my desired drop point. More than half the times this happens, something will immediately be picked up in a drag operation. Sometimes it is another window that begins being moved. Other times it is a window resize operation that is picked up. A third option is the selection of text. I have noticed that most of the time it is triggered when I am moving rapidly (though no more rapidly than I have done successfully in the past). Sometimes it happens when I pause during the drag operation. It even happens infrequently when I am dragging slowly. Often I can just go back and pick up the window and complete the operation. However, sometimes the problem just keeps happening until I give up and go away for 5 minutes or so. I have a stock configuration of 20.04. I keep it updated and haven't changed anything significant about X, Gnome, etc. I have done a few tweaks, but nothing I can think of that would relate to this problem. My laptop, a Dell XPS 13, uses a USB 3.1 hub and through that drives two monitors via HDMI. My mouse is bluetooth - Logitech MX Vertical. I don't believe I have installed any proprietary drivers. My 3 displays are arranged into an inverted "L" shape, as the laptop display is "below" and identically sized to the 27" monitor "above" it. The other 27" monitor is to the left of the first one. Some, potentially useful, debugging info: $ lsb_release -rd Description: Ubuntu 20.04.2 LTS Release: 20.04 $ apt-cache policy xorg xorg: Installed: 1:7.7+19ubuntu14 Candidate: 1:7.7+19ubuntu14 Version table: *** 1:7.7+19ubuntu14 500 500 http://us.archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status $ bluetoothctl --version bluetoothctl: 5.53 $ hciconfig -a hci0: Type: Primary Bus: USB BD Address: 9C:B6:D0:99:27:2C ACL MTU: 1024:8 SCO MTU: 50:8 UP RUNNING RX bytes:21743080 acl:954252 sco:0 events:141080 errors:0 TX bytes:6895 acl:169 sco:0 commands:208 errors:0 Features: 0xff 0xfe 0x8f 0xfe 0xd8 0x3f 0x5b 0x87 Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3 Link policy: RSWITCH HOLD SNIFF Link mode: SLAVE ACCEPT Name: 'kbuchs' Class: 0x0c010c Service Classes: Rendering, Capturing Device Class: Computer, Laptop HCI Version: 4.2 (0x8) Revision: 0x0 LMP Version: 4.2 (0x8) Subversion: 0x25a Manufacturer: Qualcomm (29) $ bluetoothctl Agent registered [CHG] Controller 9C:B6:D0:99:27:2C Pairable: yes [MX Vertical]# show Controller 9C:B6:D0:99:27:2C (public) Name: kbuchs Alias: kbuchs Class: 0x000c010c Powered: yes Discoverable: no DiscoverableTimeout: 0x00b4 Pairable: yes UUID: A/V Remote Control(110e--1000-8000-00805f9b34fb) UUID: Audio Source (110a--1000-8000-00805f9b34fb) UUID: PnP Information (1200--1000-8000-00805f9b34fb) UUID: Headset AG(1112--1000-8000-00805f9b34fb) UUID: Audio Sink(110b--1000-8000-00805f9b34fb) UUID: A/V Remote Control Target (110c--1000-8000-00805f9b34fb) UUID: Generic Access Profile(1800--1000-8000-00805f9b34fb) UUID: Headset (1108--1000-8000-00805f9b34fb) UUID: Generic Attribute Profile (1801--1000-8000-00805f9b34fb) Modalias: usb:v1D6Bp0246d0535 Discovering: no
[Touch-packages] [Bug 1926783] Re: [MSI MS-7B98] Sound is faster, high-pitched and distorted
Since you say the current kernel for Ubuntu 20.04 does not have the problem then it is considered Fix Released. If there is a newer kernel that does still have the bug then you should report it upstream, not here. ** Summary changed: - [USB-Audio - Saffire 6 USB, playback] Sound is faster, high-pitched and distorted + [MSI MS-7B98] Sound is faster, high-pitched and distorted ** Package changed: pulseaudio (Ubuntu) => linux (Ubuntu) ** Changed in: linux (Ubuntu) Status: New => Fix Released -- 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/1926783 Title: [MSI MS-7B98] Sound is faster, high-pitched and distorted Status in linux package in Ubuntu: Fix Released Bug description: It works normally when playing youtube videos, only audio files on PC are a problem. Also, kernel 5.8.0-50-generic does not have this problem. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu3.10 ProcVersionSignature: Ubuntu 5.11.0-7614.15~1618626693~20.04~ecb25cd-generic 5.11.13 Uname: Linux 5.11.0-7614-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: michal 1518 F pulseaudio /dev/snd/controlC2: michal 1518 F pulseaudio /dev/snd/controlC1: michal 1518 F pulseaudio /dev/snd/pcmC1D0p: michal 1518 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: Unity:Unity7:ubuntu CurrentDmesg: Error: command ['dmesg'] failed with exit code 1: dmesg: read kernel buffer failed: Operation not permitted Date: Fri Apr 30 17:05:38 2021 InstallationDate: Installed on 2021-01-31 (89 days ago) InstallationMedia: SourcePackage: pulseaudio Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:USB successful Symptom_Card: TU104 HD Audio Controller - HDA NVidia Symptom_PulsePlaybackTest: PulseAudio playback test failed Symptom_Type: Digital clip or distortion, or "overdriven" sound Title: [USB-Audio - Saffire 6 USB, playback] Sound is distorted UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/25/2019 dmi.bios.release: 5.13 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.80 dmi.board.asset.tag: Default string dmi.board.name: Z390-A PRO (MS-7B98) dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: 1.0 dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.80:bd12/25/2019:br5.13:svnMicro-StarInternationalCo.,Ltd.:pnMS-7B98:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnZ390-APRO(MS-7B98):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0: dmi.product.family: Default string dmi.product.name: MS-7B98 dmi.product.sku: Default string dmi.product.version: 1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1926783/+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 1926062] Re: [RTL8821A][ideapad_bluetooth] I am unable to open/close/connect/scan bluetooth
Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 1926095, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find. ** Summary changed: - [RTL8821A][ideapad_bluetooth] I am unable to open/close/connect/scan bluetooth + [hirsute] Can't turn bluetooth on again after turning it off ** Also affects: bluez (Ubuntu) Importance: Undecided Status: New ** Changed in: bluez (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1926062 Title: [hirsute] Can't turn bluetooth on again after turning it off Status in bluez package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: When ever i Turn on my system or restart bluetooth is open any it connects to any device. But when i turn off bluetooth and try to turn it on again. it neither turns on nor scans/connects to any device. This is happening since I updated my system to ubuntu 21.04 LTS ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: bluetooth (not installed) ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 Uname: Linux 5.11.0-16-generic x86_64 ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sun Apr 25 15:09:23 2021 InstallationDate: Installed on 2020-12-15 (130 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) InterestingModules: rfcomm bnep btusb bluetooth MachineType: LENOVO 80TR ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-16-generic root=UUID=7c507bd4-c66c-4233-a64e-804f6df5412b ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: Upgraded to hirsute on 2021-04-22 (2 days ago) dmi.bios.date: 07/31/2017 dmi.bios.release: 1.29 dmi.bios.vendor: LENOVO dmi.bios.version: 3UCN29WW dmi.board.asset.tag: No Asset Tag dmi.board.name: Nano 5B1 dmi.board.vendor: LENOVO dmi.board.version: No DPK dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad 110-15AST dmi.ec.firmware.release: 1.29 dmi.modalias: dmi:bvnLENOVO:bvr3UCN29WW:bd07/31/2017:br1.29:efr1.29:svnLENOVO:pn80TR:pvrLenovoideapad110-15AST:rvnLENOVO:rnNano5B1:rvrNoDPK:cvnLENOVO:ct10:cvrLenovoideapad110-15AST: dmi.product.family: IDEAPAD dmi.product.name: 80TR dmi.product.sku: LENOVO_MT_80TR_BU_idea_FM_Lenovo ideapad 110-15AST dmi.product.version: Lenovo ideapad 110-15AST dmi.sys.vendor: LENOVO hciconfig: hci0:Type: Primary Bus: USB BD Address: C8:3D:D4:84:E0:06 ACL MTU: 820:8 SCO MTU: 255:16 DOWN RX bytes:744804 acl:76 sco:0 events:105989 errors:0 TX bytes:51871528 acl:113157 sco:0 commands:192 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1926062/+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 1926121] Re: After suspending, no video signal appears after waking up
** Tags added: regression-release ** Tags added: amdgpu ** Summary changed: - After suspending, no video signal appears after waking up + [amdgpu] After suspending, no video signal appears after waking up ** Package changed: xorg (Ubuntu) => xserver-xorg-video-amdgpu (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/1926121 Title: [amdgpu] After suspending, no video signal appears after waking up Status in xserver-xorg-video-amdgpu package in Ubuntu: New Bug description: No video signal appears after waking up my computer from suspending it and leaving it in this state for a while. This issue has appeared after upgrading from Ubuntu 20.10 (where suspending and waking up worked flawlessly) to 21.04. The computer in question is a HP Desktop - M01-F0230ng with a Ryzen 5 3400G processor. A similar issue exists with a Lenovo Desktop and a Ryzen 7 4600G. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: xorg 1:7.7+22ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 Uname: Linux 5.11.0-16-generic x86_64 ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 BootLog: Error: [Errno 13] Keine Berechtigung: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Apr 26 07:12:31 2021 DistUpgraded: 2021-04-22 20:20:35,886 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (g-io-error-quark: Konnte Unterprozess "./xorg_fix_proprietary.py" nicht ausführen: Failed to execve: Datei oder Verzeichnis nicht gefunden (1)) DistroCodename: hirsute DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Picasso [1002:15d8] (rev c8) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Picasso [103c:8643] InstallationDate: Installed on 2020-03-28 (393 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200328) MachineType: HP HP Desktop M01-F0xxx ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-16-generic root=UUID=8fc8c49e-2944-4e22-9137-fd8870710ea3 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to hirsute on 2021-04-22 (3 days ago) dmi.bios.date: 11/26/2019 dmi.bios.release: 15.17 dmi.bios.vendor: AMI dmi.bios.version: F.11 dmi.board.name: 8643 dmi.board.vendor: HP dmi.board.version: SMVB dmi.chassis.type: 3 dmi.chassis.vendor: HP dmi.ec.firmware.release: 52.38 dmi.modalias: dmi:bvnAMI:bvrF.11:bd11/26/2019:br15.17:efr52.38:svnHP:pnHPDesktopM01-F0xxx:pvr:rvnHP:rn8643:rvrSMVB:cvnHP:ct3:cvr: dmi.product.family: 103C_53311M HP Desktop PC dmi.product.name: HP Desktop M01-F0xxx dmi.product.sku: 8KX18EA#ABD dmi.sys.vendor: HP version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.104-1build1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.1-2 version.libgl1-mesa-glx: libgl1-mesa-glx 21.0.1-2 version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-amdgpu/+bug/1926121/+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 1926095] Re: The bluetooth toggle is not working properly. Switching it on does not turn on the bluetooth. It remains off permanently.
*** This bug is a duplicate of bug 1926062 *** https://bugs.launchpad.net/bugs/1926062 Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 1926062, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find. ** This bug has been marked a duplicate of bug 1926062 [hirsute] Can't turn bluetooth on again after turning it off -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1926095 Title: The bluetooth toggle is not working properly. Switching it on does not turn on the bluetooth. It remains off permanently. Status in bluez package in Ubuntu: Confirmed Bug description: I have described the issue here with screenshots https://askubuntu.com/q/1333848/1022606. Please have a look at the screenshots. Turning on the Bluetooth toggle has no effect. The system doesn't turn on the Bluetooth and does no scan for devices. Turning it on just moves the toggle, even the system doesn't acknowledge by showing that Bluetooth is on. The status remains off. It happened only after the upgrade I did yesterday. It was working fine before that. Please look into it. I cannot connect my Bluetooth earphones to my PC. This poses a lot of problems since my classes and courses are all online. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: ubuntu-release-upgrader-core 1:21.04.11 ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 Uname: Linux 5.11.0-16-generic x86_64 ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 CasperMD5CheckResult: unknown CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Mon Apr 26 00:09:35 2021 InstallationDate: Installed on 2019-12-05 (507 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: dist-upgrade UpgradeStatus: Upgraded to hirsute on 2021-04-24 (1 days ago) VarLogDistupgradeTermlog: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1926095/+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 1926770] Re: Bluetooth switches back on each reboot
Thank you for taking the time to report this bug and helping to make Ubuntu better. Please execute the following command only once, as it will automatically gather debugging information, in a terminal: apport-collect 1926770 When reporting bugs in the future please use apport by using 'ubuntu- bug' and the name of the package affected. You can learn more about this functionality at https://wiki.ubuntu.com/ReportingBugs. ** Changed in: bluez (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1926770 Title: Bluetooth switches back on each reboot Status in bluez package in Ubuntu: Incomplete Bug description: Dear, When switching off Bluetooth in the settings menu, after each reboot and login into GNOME, the Bluetooth radio stack seems to be switched on again. Could this setting made by persistent over reboots? Thanks, To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1926770/+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
