[Touch-packages] [Bug 1888975] Re: Double click on a window's titlebar is transferred to desktop
** Description changed: Hi. In ubuntu 20.04, whenever I double click on the titlebar of the window of some programs (including: firefox, simplenote, geany, visual studio code, etc.; excluding gedit, evince, nautilus, etc.), the double - click is transferred to the desktop. For example, if behind the - titlebar, at the (X,Y) position of mouse pointer, there is a folder - icon on my desktop, that folder gets opened. + click is transferred to the desktop. For example, if behind the titlebar + of firefox, at the (X,Y) position of mouse pointer, there is a folder + icon on my desktop, that folder gets opened after firefix window is + maximized/unmaximized. However, if right behind the titlebar there is another window (not desktop), the double click is not transferred to that window or to desktop. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Jul 26 10:02:04 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller [8086:2a42] (rev 09) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Mobile 4 Series Chipset Integrated Graphics Controller [1043:1863] Subsystem: ASUSTeK Computer Inc. Mobile 4 Series Chipset Integrated Graphics Controller [1043:1863] InstallationDate: Installed on 2020-04-19 (97 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200417) MachineType: ASUSTeK Computer Inc. F82Q ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic root=UUID=ad3f3a2c-64bc-415b-b70c-4da2b1dbf0af ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/19/2009 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 206 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: F82Q dmi.board.vendor: ASUSTeK Computer Inc. dmi.board.version: 1.0 dmi.chassis.asset.tag: ATN12345678901234567 dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK Computer Inc. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr206:bd05/19/2009:svnASUSTeKComputerInc.:pnF82Q:pvr1.0:rvnASUSTeKComputerInc.:rnF82Q:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr1.0: dmi.product.name: F82Q dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK Computer Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Description changed: Hi. In ubuntu 20.04, whenever I double click on the titlebar of the window of some programs (including: firefox, simplenote, geany, visual - studio code, etc.; excluding gedit, evince, nautilus, etc.), the double + studio code, etc.; excluding: gedit, evince, nautilus, etc.), the double click is transferred to the desktop. For example, if behind the titlebar of firefox, at the (X,Y) position of mouse pointer, there is a folder icon on my desktop, that folder gets opened after firefix window is maximized/unmaximized. However, if right behind the titlebar there is another window (not desktop), the double click is not transferred to that window or to desktop. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Jul 26 10:02:04 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller [8086:2a42] (rev 09) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Mobile 4 Series Chipset Integrated Graphics Controller [1043:1863]
[Touch-packages] [Bug 1888975] [NEW] Double click on a window's titlebar is transferred to desktop
Public bug reported: Hi. In ubuntu 20.04, whenever I double click on the titlebar of the window of some programs (including: firefox, simplenote, geany, visual studio code, etc.; excluding gedit, evince, nautilus, etc.), the double click is transferred to the desktop. For example, if behind the titlebar, at the (X,Y) position of mouse pointer, there is a folder icon on my desktop, that folder gets opened. However, if right behind the titlebar there is another window (not desktop), the double click is not transferred to that window or to desktop. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Jul 26 10:02:04 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller [8086:2a42] (rev 09) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Mobile 4 Series Chipset Integrated Graphics Controller [1043:1863] Subsystem: ASUSTeK Computer Inc. Mobile 4 Series Chipset Integrated Graphics Controller [1043:1863] InstallationDate: Installed on 2020-04-19 (97 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200417) MachineType: ASUSTeK Computer Inc. F82Q ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic root=UUID=ad3f3a2c-64bc-415b-b70c-4da2b1dbf0af ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/19/2009 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 206 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: F82Q dmi.board.vendor: ASUSTeK Computer Inc. dmi.board.version: 1.0 dmi.chassis.asset.tag: ATN12345678901234567 dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK Computer Inc. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr206:bd05/19/2009:svnASUSTeKComputerInc.:pnF82Q:pvr1.0:rvnASUSTeKComputerInc.:rnF82Q:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr1.0: dmi.product.name: F82Q dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK Computer Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ubuntu ** Description changed: - Hi. In ubuntu 20.20, whenever I double click on the titlebar of the + Hi. In ubuntu 20.04, whenever I double click on the titlebar of the window of some programs (including: firefox, simplenote, geany, visual studio code, etc.; excluding gedit, evince, nautilus, etc.), the double click is transferred to the desktop. For example, if behind the titlebar, at the (X,Y) position of mouse pointer, there is a folder icon on my desktop, that folder gets opened. However, if right behind the titlebar there is another window (not desktop), the double click is not transferred to that window or to desktop. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Jul 26 10:02:04 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: - Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller [8086:2a42] (rev 09) (prog-if 00 [VGA controller]) -Subsystem: ASUSTeK Computer Inc. Mobile 4 Series Chipset Integrated Graphics Controller [1043:1863] -Subsystem: ASUSTeK Computer Inc. Mobile 4 Series Chipset Integrated Graphics Controller [1043:1863] + Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller [8086:2a42] (rev 09) (prog-if 00 [VGA controller]) + Subsystem: ASUSTeK Computer Inc. Mobile 4 Series Chipset Integrated Graphics Cont
[Touch-packages] [Bug 1882525] Re: [amdgpu] MATE desktop is corrupted upon login on Ryzen APU
I've discovered some useful info about this bug. First, there's a forum thread about it with lots of good info: https://ubuntu- mate.community/t/20-04-display-issues-with-amd-gpu/21648/37 Second, a new workaround. To recap, the first workaround I found was booting with nomodeset, but that disables all hardware acceleration. The new workaround, as detailed in the forum thread, is to open MATE Tweak, and in the Windows tab, change the window manager to Marco (no compositor). Third, we found the upstream bug in xf86-video-amdgpu: https://gitlab.freedesktop.org/xorg/driver/xf86-video-amdgpu/-/issues/10 . I believe this is packaged as xserver-xorg-video-amdgpu in Ubuntu. It's been fixed upstream and the Ubuntu Mate devs will include it in 20.04.1 is possible. Fourth, bug #1873895 appears to be the same bug, but originally reported as manifesting in Xubuntu. Maybe this is a duplicate. ** Bug watch added: gitlab.freedesktop.org/xorg/driver/xf86-video-amdgpu/-/issues #10 https://gitlab.freedesktop.org/xorg/driver/xf86-video-amdgpu/-/issues/10 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1882525 Title: [amdgpu] MATE desktop is corrupted upon login on Ryzen APU Status in marco package in Ubuntu: New Status in mesa package in Ubuntu: New Status in xorg-server package in Ubuntu: New Status in xserver-xorg-video-amdgpu package in Ubuntu: New Bug description: Today I upgraded from Ubuntu MATE 19.10 to 20.04. After doing so, Ubuntu boots normally to the display manager (login screen) as expected. But once I log in, everything on the screen is cut up into horizontal slices, with each slice offset farther right than the slice above, and squares of random colors running diagonally across the screen. I've attached a picture of my monitor showing the issue for reference. My hardware is a home-built PC with an ASUS Prime B450M motherboard, a Ryzen 3 2200G APU, and using that APU's integrated graphics. In terms of software I'm running Ubuntu 20.04, which I just upgraded to and did a software update on. I have Linux 5.4.0-33-generic, X.Org 1.20.8, and Mesa 20.0.4. Before I upgraded Ubuntu, I was affected by Bug #1880041 but it seems fixed in the new kernel. I don't believe they're related but I figure it's worth mentioning. I tried adding the nomodeset kernel option at boot, and it's an effective workaround. Also, I tried booting from an Ubuntu Mate 20.04 live USB to see if this was caused by some quirk of my particular software setup, and successfully reproduced the bug, proving it wasn't. If you'd like me to, I can provide log files, system information, etc. or help narrow it down by testing workarounds. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xserver-xorg-core 2:1.20.8-2ubuntu2.1 ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 Uname: Linux 5.4.0-33-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 CasperMD5CheckResult: skip CompositorRunning: None Date: Mon Jun 8 06:41:47 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExecutablePath: /usr/lib/xorg/Xorg ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Raven Ridge [Radeon Vega Series / Radeon Vega Mobile Series] [1002:15dd] (rev c8) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Raven Ridge [Radeon Vega Series / Radeon Vega Mobile Series] [1043:876b] InstallationDate: Installed on 2019-10-20 (231 days ago) InstallationMedia: Ubuntu-MATE 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: System manufacturer System Product Name ProcEnviron: PATH=(custom, no user) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-33-generic root=UUID=43189257-cc94-4e98-ac1d-e16336dd152e ro quiet splash vt.handoff=7 SourcePackage: xorg-server UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/13/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2006 dmi.board.asset.tag: Default string dmi.board.name: PRIME B450M-A 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.:bvr2006:bd11/13/2019:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEB450M-A: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 20.0.4-2ubuntu1 v
[Touch-packages] [Bug 1888598] Re: pulseaudio has is buggy with hdmi audio and sleep/wake
yep, looks like even after sleep and when things are all messed up, they're still listed as available: ports: hdmi-output-0: HDMI / DisplayPort (priority 5900, latency offset 0 usec, available: yes) properties: device.icon_name = "video-display" device.product.name = "LG Ultra HD " hdmi-output-1: HDMI / DisplayPort 2 (priority 5800, latency offset 0 usec, available: yes) properties: device.icon_name = "video-display" device.product.name = "HTR-5063 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1888598 Title: pulseaudio has is buggy with hdmi audio and sleep/wake Status in pulseaudio package in Ubuntu: Confirmed Bug description: on a fresh Ubuntu 20.04 x64 install, I've noticed some troubling bugs with pulseaudio after putting my system to sleep and then waking it up. these bugs aren't present on a fresh boot, only after resuming from sleep: - it forgets which sound output device it's set to, and always reverse to the motherboard's S/PDIF output. - I have two devices connected to my video card, one is a displayport monitor, and one is a home theater receiver via HDMI. it confuses the two, and randomly switches which device it thinks is capable of surround sound. - it sometimes refuses to switch to the correct audio device, and just resets any choice back to the internal S/PDIF, until the system is rebooted. as you can imagine, this a pretty frustrating state of affairs. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu3.4 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: tessa 3387 F pulseaudio /dev/snd/pcmC1D7p: tessa 3387 F...m pulseaudio /dev/snd/controlC2: tessa 3387 F pulseaudio /dev/snd/controlC0: tessa 3387 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Jul 22 18:38:42 2020 InstallationDate: Installed on 2020-07-15 (7 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/18/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3503 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: GRYPHON Z97 dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3503:bd04/18/2018:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnGRYPHONZ97:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: ASUS MB dmi.product.name: All Series dmi.product.sku: All dmi.product.version: System Version dmi.sys.vendor: ASUS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1888598/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1841551] Re: Update to 0.20.2
Bump version in the title as another upstream release has been published, link below. Am I missing something here, isn't this a package that is something of a keystone in the package maintenance toolchain? Couldn't we just cook one up and release it on our end? If someone gives me the thumbs up I'll even try to make something happen on that front myself. GNU gettext 0.20.2 - * tarball: https://ftp.gnu.org/gnu/gettext/gettext-0.20.2.tar.xz * signature: https://ftp.gnu.org/gnu/gettext/gettext-0.20.2.tar.xz.sig -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gettext in Ubuntu. https://bugs.launchpad.net/bugs/1841551 Title: Update to 0.20.2 Status in gettext package in Ubuntu: Triaged Status in gettext package in Debian: New Bug description: Requested to Debian as well on https://bugs.debian.org/cgi- bin/bugreport.cgi?bug=934738 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gettext/+bug/1841551/+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 1841551] Re: Update to 0.20.2
** Summary changed: - Update to 0.20.1 + Update to 0.20.2 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gettext in Ubuntu. https://bugs.launchpad.net/bugs/1841551 Title: Update to 0.20.2 Status in gettext package in Ubuntu: Triaged Status in gettext package in Debian: New Bug description: Requested to Debian as well on https://bugs.debian.org/cgi- bin/bugreport.cgi?bug=934738 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gettext/+bug/1841551/+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 1308262] Re: libpam-systemd postinstall stuck on upgrade
*** This bug is a duplicate of bug 1325142 *** https://bugs.launchpad.net/bugs/1325142 Got this on Ubuntu 20.04 -- 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/1308262 Title: libpam-systemd postinstall stuck on upgrade Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Trusty: Incomplete Bug description: Just did an "apt-get update && apt-get dist-upgrade" on my trusty laptop. It's been stuck in the libpam-systemd postinst for 15-20 minutes: Recent output from dist-upgrade: Unpacking xpra (0.12.3+dfsg-1ubuntu1) over (0.12.2+dfsg-1ubuntu1) ... Processing triggers for man-db (2.6.7.1-1) ... Processing triggers for ureadahead (0.100.0-16) ... ureadahead will be reprofiled on next reboot Processing triggers for gnome-menus (3.10.1-0ubuntu2) ... Processing triggers for desktop-file-utils (0.22-1ubuntu1) ... Processing triggers for mime-support (3.54ubuntu1) ... Processing triggers for hicolor-icon-theme (0.13-1) ... Setting up libcgmanager0:i386 (0.24-0ubuntu5) ... Setting up libcgmanager0:amd64 (0.24-0ubuntu5) ... Setting up libudev1:amd64 (204-5ubuntu20) ... Setting up libudev1:i386 (204-5ubuntu20) ... Setting up udev (204-5ubuntu20) ... udev stop/waiting udev start/running, process 30898 Removing 'diversion of /bin/udevadm to /bin/udevadm.upgrade by fake-udev' update-initramfs: deferring update (trigger activated) Setting up libsystemd-daemon0:amd64 (204-5ubuntu20) ... Setting up systemd-services (204-5ubuntu20) ... Setting up libpam-systemd:amd64 (204-5ubuntu20) ... Installing new version of config file /etc/init/systemd-logind.conf ... [stuck here] Relevant processes running: | | | | |-bash---sudo---apt-get---dpkg ---libpam-systemd:---invoke-rc.d---start root 28517 17005 0 16:14 pts/26 00:00:00 sudo apt-get dist-upgrade root 28579 28517 3 16:14 pts/26 00:00:56 apt-get dist-upgrade root 30803 28579 0 16:15 pts/28 00:00:00 /usr/bin/dpkg --status-fd 69 --configure libcgmanager0:i386 libcgmanager0:amd64 libudev1:amd64 libudev1:i386 udev:amd64 libsystemd-daemon0:amd64 systemd-services:amd64 libpam-systemd:amd64 libsystemd-login0:amd64 chromium-codecs-ffmpeg-extra:amd64 chromium-browser:amd64 chromium-browser-l10n:all libgudev-1.0-0:amd64 cgmanager:amd64 liblxc1:amd64 python3-lxc:amd64 lxc:amd64 lxc-templates:amd64 libva1:amd64 libva-x11-1:amd64 libsystemd-journal0:amd64 ubuntu-minimal:amd64 gir1.2-gudev-1.0:amd64 libxenstore3.0:amd64 libxen-4.4:amd64 python-qt4:amd64 python-qt4-dbus:amd64 xpra:amd64 root 30928 30803 0 16:15 pts/28 00:00:00 /bin/sh /var/lib/dpkg/info/libpam-systemd:amd64.postinst configure 204-5ubuntu19 root 30942 30928 0 16:15 pts/28 00:00:00 /bin/sh /usr/sbin/invoke-rc.d systemd-logind start root 30984 30942 0 16:15 pts/28 00:00:00 start systemd-logind System info: Description:Ubuntu 14.04 LTS Release:14.04 libpam-systemd: Installed: 204-5ubuntu20 Candidate: 204-5ubuntu20 Version table: *** 204-5ubuntu20 0 500 http://us.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1308262/+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 1835660] Re: initramfs unpacking failed
Is part of the issue here that some (most) initramfs-tools created images have an uncompressed early CPU microcode firmware prefixed ? That is stored as ASCII CPIO which is why Con see's that reported by 'file' since that tool checks the magic signatures at start of a file. binwalk reveals more detail. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1835660 Title: initramfs unpacking failed Status in initramfs-tools package in Ubuntu: Invalid Status in linux package in Ubuntu: Confirmed Bug description: "initramfs unpacking failed: Decoding failed", message appears on boot up. If I "update-initramfs" using gzip instead of lz, then boot up passes without decoding failed message. --- However, we currently believe that the decoding error reported in dmesg is actually harmless and has no impact on usability on the system. Switching from lz4 to gzip compression, simply papers over the warning, without any benefits, and slows down boot. Kernel should be fixed to correctly parse lz4 compressed initrds, or at least lower the warning, to not be user visible as an error. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1835660/+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 1887977] Re: Bluetooth headset is not reconnecting automatically if disconnected in between
please let me know if more details are needed -- 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/1887977 Title: Bluetooth headset is not reconnecting automatically if disconnected in between Status in bluez package in Ubuntu: Incomplete Bug description: Some times Bluetooth headset is not reconnecting automatically if disconnected in between. I need to remove the bluetooth headset and again pair it, then it is connecting. 1. Ubuntu Version - 20.04 2. Software version - bluez Installed: 5.53-0ubuntu3 3. Expected result : Every time when I restart the laptop or resume it the headset should connect automatically 4. Issues Faced : Some times when I restart the laptop or resume the laptop, then eventhough headset is switched on bluetooth connection is not established. Instead if I remove the the headset from bluetooth list and again newly pair it with laptop then headset it connected. Verified the bluetooth head set by connecting it to mobile phone and other os like windows/mac os and it seems there is no issue with headset. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: bluez 5.53-0ubuntu3 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Jul 17 19:58:10 2020 InstallationDate: Installed on 2020-05-04 (73 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) InterestingModules: rfcomm bnep btusb bluetooth Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 0408:a060 Quanta Computer, Inc. HD Webcam Bus 001 Device 003: ID 8087:0aaa Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Acer Nitro AN515-52 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-40-generic root=UUID=a609dea6-45d9-4ed8-8a46-ba56dae5a117 ro quiet splash SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/13/2018 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.19 dmi.board.asset.tag: Type2 - Board Serial Number dmi.board.name: Freed_CFS dmi.board.vendor: CFL dmi.board.version: V1.19 dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V1.19 dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.19:bd07/13/2018:svnAcer:pnNitroAN515-52:pvrV1.19:rvnCFL:rnFreed_CFS:rvrV1.19:cvnAcer:ct10:cvrV1.19: dmi.product.family: Acer Nitro 5 dmi.product.name: Nitro AN515-52 dmi.product.sku: dmi.product.version: V1.19 dmi.sys.vendor: Acer hciconfig: hci0:Type: Primary Bus: USB BD Address: 18:56:80:A6:CA:8D ACL MTU: 1021:4 SCO MTU: 96:6 UP RUNNING PSCAN RX bytes:16973 acl:0 sco:0 events:2752 errors:0 TX bytes:678011 acl:0 sco:0 commands:2750 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1887977/+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 1887977] Re: Bluetooth headset is not reconnecting automatically if disconnected in between
the model of the head set is boat rockerz 510 -- 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/1887977 Title: Bluetooth headset is not reconnecting automatically if disconnected in between Status in bluez package in Ubuntu: Incomplete Bug description: Some times Bluetooth headset is not reconnecting automatically if disconnected in between. I need to remove the bluetooth headset and again pair it, then it is connecting. 1. Ubuntu Version - 20.04 2. Software version - bluez Installed: 5.53-0ubuntu3 3. Expected result : Every time when I restart the laptop or resume it the headset should connect automatically 4. Issues Faced : Some times when I restart the laptop or resume the laptop, then eventhough headset is switched on bluetooth connection is not established. Instead if I remove the the headset from bluetooth list and again newly pair it with laptop then headset it connected. Verified the bluetooth head set by connecting it to mobile phone and other os like windows/mac os and it seems there is no issue with headset. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: bluez 5.53-0ubuntu3 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Jul 17 19:58:10 2020 InstallationDate: Installed on 2020-05-04 (73 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) InterestingModules: rfcomm bnep btusb bluetooth Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 0408:a060 Quanta Computer, Inc. HD Webcam Bus 001 Device 003: ID 8087:0aaa Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Acer Nitro AN515-52 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-40-generic root=UUID=a609dea6-45d9-4ed8-8a46-ba56dae5a117 ro quiet splash SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/13/2018 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.19 dmi.board.asset.tag: Type2 - Board Serial Number dmi.board.name: Freed_CFS dmi.board.vendor: CFL dmi.board.version: V1.19 dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V1.19 dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.19:bd07/13/2018:svnAcer:pnNitroAN515-52:pvrV1.19:rvnCFL:rnFreed_CFS:rvrV1.19:cvnAcer:ct10:cvrV1.19: dmi.product.family: Acer Nitro 5 dmi.product.name: Nitro AN515-52 dmi.product.sku: dmi.product.version: V1.19 dmi.sys.vendor: Acer hciconfig: hci0:Type: Primary Bus: USB BD Address: 18:56:80:A6:CA:8D ACL MTU: 1021:4 SCO MTU: 96:6 UP RUNNING PSCAN RX bytes:16973 acl:0 sco:0 events:2752 errors:0 TX bytes:678011 acl:0 sco:0 commands:2750 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1887977/+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 1888940] [NEW] RShift + LShift works together with LAlt + LShift to switch language layout
Public bug reported: Steps to reproduce: 1. Have default Ubuntu 20.04 LTS installed 2. Configure two keyboard layouts - English and Russian 3. Configure + as keyboard layout switcher in GNOME Tweaks 4. Press and hold , then do multiple click on Expected results: * nothing, keyboard layout does not change Actual results: * keyboard layout changes as when + was clicked --- Details: ``` $ cat /etc/default/keyboard ; gsettings get org.gnome.desktop.input-sources xkb-options ; gsettings get org.freedesktop.ibus.general.hotkey triggers XKBLAYOUT=us,ru XKBVARIANT=, BACKSPACE=guess ['grp:lalt_lshift_toggle'] ['space'] ``` Note: first seen on https://askubuntu.com/q/1261935 . --- ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-settings-daemon 3.36.1-0ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat Jul 25 16:57:06 2020 InstallationDate: Installed on 2020-04-27 (88 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: gnome-settings-daemon UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-settings-daemon (Ubuntu) Importance: Undecided Status: New ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Affects: ubuntu-meta (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal groovy ** Also affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Also affects: ubuntu-meta (Ubuntu) Importance: Undecided Status: New -- 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/1888940 Title: RShift + LShift works together with LAlt + LShift to switch language layout Status in gnome-settings-daemon package in Ubuntu: New Status in gnome-shell package in Ubuntu: New Status in ubuntu-meta package in Ubuntu: New Bug description: Steps to reproduce: 1. Have default Ubuntu 20.04 LTS installed 2. Configure two keyboard layouts - English and Russian 3. Configure + as keyboard layout switcher in GNOME Tweaks 4. Press and hold , then do multiple click on Expected results: * nothing, keyboard layout does not change Actual results: * keyboard layout changes as when + was clicked --- Details: ``` $ cat /etc/default/keyboard ; gsettings get org.gnome.desktop.input-sources xkb-options ; gsettings get org.freedesktop.ibus.general.hotkey triggers XKBLAYOUT=us,ru XKBVARIANT=, BACKSPACE=guess ['grp:lalt_lshift_toggle'] ['space'] ``` Note: first seen on https://askubuntu.com/q/1261935 . --- ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-settings-daemon 3.36.1-0ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat Jul 25 16:57:06 2020 InstallationDate: Installed on 2020-04-27 (88 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: gnome-settings-daemon UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1888940/+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] [NEW] Indicator is shown twice
Public bug reported: 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) ** Affects: indicator-bluetooth (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal third-party-packages ** Attachment added: "Screenshot from 2020-07-25 12-02-17.png" https://bugs.launchpad.net/bugs/1888934/+attachment/5395678/+files/Screenshot%20from%202020-07-25%2012-02-17.png -- 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: New 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 1888648] Re: network-manager crashes: "NetworkManager needs to be running"
So I think this is the journalctl from the time it crashed. These lines caught my eyes: Jul 23 14:52:40 creative-machine kernel: ath10k_pci :02:00.0: failed to wake target for read32 at 0x00036044: -110 Jul 23 14:52:41 creative-machine kernel: ath10k_pci :02:00.0: firmware crashed! (guid a3417396-44ed-4633-81d1-fc662aad62b4) ** Attachment added: "Journalctl of the boot my network-manager crashed" https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1888648/+attachment/5395674/+files/journalctl-network-manager.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1888648 Title: network-manager crashes: "NetworkManager needs to be running" Status in network-manager package in Ubuntu: Incomplete Bug description: Hi. Sometimes network-manager crashes and I can't connect to any network. Restarting the network manager service via terminal hangs and even restarting the OS hangs and I have to force shutdown via power button. When I open settings > Wi-Fi it says: "Oops, something has gone wrong. Please contact your software vendor. NetworkManager needs to be running". I'm not facing the problem right now as I just restarted my laptop so if there's any information that I need to gather while this problem is happening, let me know. Thanks. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: network-manager 1.22.10-1ubuntu2.1 ProcVersionSignature: Ubuntu 5.4.0-42.46-lowlatency 5.4.44 Uname: Linux 5.4.0-42-lowlatency x86_64 ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Jul 23 14:07:57 2020 InstallationDate: Installed on 2020-06-20 (33 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) IpRoute: default via 192.168.1.1 dev wlp2s0 proto dhcp metric 20600 169.254.0.0/16 dev wlp2s0 scope link metric 1000 192.168.1.0/24 dev wlp2s0 proto kernel scope link src 192.168.1.36 metric 600 SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-dev: DEVICE TYPE STATE IP4-CONNECTIVITY IP6-CONNECTIVITY DBUS-PATH CONNECTION CON-UUID CON-PATH wlp2s0 wifi connected limited limited /org/freedesktop/NetworkManager/Devices/2 neverlookaway 7b44595b-b6bc-4add-9873-a7af7393c65d /org/freedesktop/NetworkManager/ActiveConnection/1 p2p-dev-wlp2s0 wifi-p2p disconnected none none /org/freedesktop/NetworkManager/Devices/3 -- -- -- lo loopback unmanaged unknown unknown /org/freedesktop/NetworkManager/Devices/1 -- -- -- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.22.10 connected (site only) started limited enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1888648/+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 1888705] Re: lxc ftbfs against libselinux 3.1
https://github.com/lxc/lxc/pull/3498 ** Changed in: lxc (Ubuntu) Status: New => In Progress -- 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/1888705 Title: lxc ftbfs against libselinux 3.1 Status in lxc package in Ubuntu: In Progress Bug description: lxc fails to build from source against libselinux 3.1 in groovy- proposed, as seen in the autopkgtests which do a rebuild as part of the test: libtool: compile: gcc -DHAVE_CONFIG_H -I. -I../../src -fPIC -DPIC -DLXCROOTFSMOUNT=\"/usr/lib/x86_64-linux-gnu/lxc\" -DLXCPATH=\"/var/lib/lxc\" -DLXC_GLOBAL_CONF=\"/etc/lxc/lxc.conf\" -DLXCINITDIR=\"/usr/lib/x86_64-linux-gnu\" -DLIBEXECDIR=\"/usr/lib/x86_64-linux-gnu\" -DLXCTEMPLATEDIR=\"/usr/share/lxc/templates\" -DLXCTEMPLATECONFIG=\"/usr/share/lxc/config\" -DLOGPATH=\"/var/log/lxc\" -DLXC_DEFAULT_CONFIG=\"/etc/lxc/default.conf\" -DLXC_USERNIC_DB=\"/run/lxc/nics\" -DLXC_USERNIC_CONF=\"/etc/lxc/lxc-usernet\" -DDEFAULT_CGROUP_PATTERN=\"\" -DRUNTIME_PATH=\"/run\" -DSBINDIR=\"/usr/sbin\" -DAPPARMOR_CACHE_DIR=\"/var/cache/lxc/apparmor\" -I ../../src -I ../../src/lxc -I ../../src/lxc/storage -I ../../src/lxc/cgroups -DHAVE_APPARMOR -DHAVE_SECCOMP -DHAVE_SELINUX -pthread -g -O2 -fdiagnostics-color -Wimplicit-fallthrough=5 -Wcast-align -fno-strict-aliasing -fstack-clash-protection -fstack-protector-strong --param=ssp-buffer-size=4 -g -Werror=implicit-function-declaration -Wlogical-op -Wmissing-include-dirs -Winit-self -Wunused-but-set-variable -Wfloat-equal -Wsuggest-attribute=noreturn -Werror=return-type -Werror=incompatible-pointer-types -Wformat=2 -Wshadow -Wendif-labels -Werror=overflow -fdiagnostics-show-option -Werror=shift-count-overflow -Werror=shift-overflow=2 -Wdate-time -Wnested-externs -fasynchronous-unwind-tables -pipe -fexceptions -Wvla -std=gnu11 -Werror -MT lsm/liblxc_la-selinux.lo -MD -MP -MF lsm/.deps/liblxc_la-selinux.Tpo -c lsm/selinux.c -fPIC -DPIC -o lsm/.libs/liblxc_la-selinux.o lsm/selinux.c: In function ‘selinux_process_label_get’: lsm/selinux.c:35:2: error: ‘security_context_t’ is deprecated [-Werror=deprecated-declarations] 35 | security_context_t ctx; | ^~ cc1: all warnings being treated as errors Because this is a universe package, I intend to force libselinux into the release, overriding this test failure. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1888705/+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 1888926] [NEW] tls.tlscfgcmd not recognized; rebuild rsyslog against librelp 1.5.0
Public bug reported:
rsyslogd: error during parsing file /etc/rsyslog.d/FILENAME.conf, on or
before line 22: imrelp: librelp does not support input parameter
'tls.tlscfgcmd'; it probably is too old (1.5.0 or higher should be
fine); ignoring setting now. [v8.2001.0 try
https://www.rsyslog.com/e/2207 ]
Here is the config:
module(load="imrelp" tls.tlslib="openssl")
input(
type="imrelp" port="2515"
tls="on"
# This should work in rsyslog 8.2006.0:
#tls.mycert="/etc/rsyslog.tls/fullchain.pem"
# for now we use the work-around discussed in:
# https://github.com/rsyslog/rsyslog/issues/4360
tls.cacert="/etc/rsyslog.tls/chain.pem"
tls.mycert="/etc/rsyslog.tls/cert.pem"
tls.myprivkey="/etc/rsyslog.tls/privkey.pem"
tls.tlscfgcmd="ServerPreference
CipherString=ECDHE-ECDSA-AES128-GCM-SHA256:ECDHE-RSA-AES128-GCM-SHA256:ECDHE-ECDSA-AES256-GCM-SHA384:ECDHE-RSA-AES256-GCM-SHA384:ECDHE-ECDSA-CHACHA20-POLY1305:ECDHE-RSA-CHACHA20-POLY1305:DHE-RSA-AES128-GCM-SHA256:DHE-RSA-AES256-GCM-SHA384
Ciphersuites=TLS_AES_128_GCM_SHA256:TLS_CHACHA20_POLY1305_SHA256:TLS_AES_256_GCM_SHA384
MinProtocol=TLSv1.2"
)
This error comes from this code in plugins/imrelp/imrelp.c:
#if defined(HAVE_RELPENGINESETTLSCFGCMD)
inst->tlscfgcmd =
(uchar*)es_str2cstr(pvals[i].val.d.estr, NULL);
#else
parser_errmsg("imrelp: librelp does not support input
parameter 'tls.tlscfgcmd'; "
"it probably is too old (1.5.0 or higher should
be fine); ignoring setting now.");
#endif
The build log for focal:
https://launchpadlibrarian.net/464665610/buildlog_ubuntu-focal-arm64.rsyslog_8.2001.0-1ubuntu1_BUILDING.txt.gz
says:
checking for relpSrvSetTlsConfigCmd... no
checking for relpSrvSetTlsConfigCmd... (cached) no
The build log for groovy:
https://launchpadlibrarian.net/486409321/buildlog_ubuntu-groovy-arm64.rsyslog_8.2006.0-2ubuntu1_BUILDING.txt.gz
says:
checking for relpSrvSetTlsConfigCmd... yes
checking for relpSrvSetTlsConfigCmd... (cached) yes
If I rebuild the rsyslog package, I get:
checking for relpSrvSetTlsConfigCmd... yes
checking for relpSrvSetTlsConfigCmd... (cached) yes
I suspect that the rsyslog package was built against and older librelp
version. A simple rebuild of rsyslog should fix this, though a more
complete fix would be to raise the Build-Depends from librelp-dev (>=
1.4.0) to librelp-dev (>= 1.5.0).
** Affects: rsyslog (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to rsyslog in Ubuntu.
https://bugs.launchpad.net/bugs/1888926
Title:
tls.tlscfgcmd not recognized; rebuild rsyslog against librelp 1.5.0
Status in rsyslog package in Ubuntu:
New
Bug description:
rsyslogd: error during parsing file /etc/rsyslog.d/FILENAME.conf, on
or before line 22: imrelp: librelp does not support input parameter
'tls.tlscfgcmd'; it probably is too old (1.5.0 or higher should be
fine); ignoring setting now. [v8.2001.0 try
https://www.rsyslog.com/e/2207 ]
Here is the config:
module(load="imrelp" tls.tlslib="openssl")
input(
type="imrelp" port="2515"
tls="on"
# This should work in rsyslog 8.2006.0:
#tls.mycert="/etc/rsyslog.tls/fullchain.pem"
# for now we use the work-around discussed in:
# https://github.com/rsyslog/rsyslog/issues/4360
tls.cacert="/etc/rsyslog.tls/chain.pem"
tls.mycert="/etc/rsyslog.tls/cert.pem"
tls.myprivkey="/etc/rsyslog.tls/privkey.pem"
tls.tlscfgcmd="ServerPreference
CipherString=ECDHE-ECDSA-AES128-GCM-SHA256:ECDHE-RSA-AES128-GCM-SHA256:ECDHE-ECDSA-AES256-GCM-SHA384:ECDHE-RSA-AES256-GCM-SHA384:ECDHE-ECDSA-CHACHA20-POLY1305:ECDHE-RSA-CHACHA20-POLY1305:DHE-RSA-AES128-GCM-SHA256:DHE-RSA-AES256-GCM-SHA384
Ciphersuites=TLS_AES_128_GCM_SHA256:TLS_CHACHA20_POLY1305_SHA256:TLS_AES_256_GCM_SHA384
MinProtocol=TLSv1.2"
)
This error comes from this code in plugins/imrelp/imrelp.c:
#if defined(HAVE_RELPENGINESETTLSCFGCMD)
inst->tlscfgcmd =
(uchar*)es_str2cstr(pvals[i].val.d.estr, NULL);
#else
parser_errmsg("imrelp: librelp does not support input
parameter 'tls.tlscfgcmd'; "
"it probably is too old (1.5.0 or higher
should be fine); ignoring setting now.");
#endif
The build log for focal:
https://launchpadlibrarian.net/464665610/buildlog_ubuntu-focal-arm64.rsyslog_8.2001.0-1ubuntu1_BUILDING.txt.gz
says:
checking for relpSrvSetTlsConfigCmd... no
checking for relpSrvSetTlsConfigCmd... (cached) no
The build log for groovy:
https://launchpadlibrarian.net/486409321/buildlog_ubuntu-groovy-arm64.rsyslog_8.2006.0-2ubuntu1_BUILDING.txt.gz
says:
checking for relpSrvSetTlsConfigCmd... yes
checking for relpSrvSetTlsConfigCmd... (cached) yes
If I rebuil
[Touch-packages] [Bug 1802718] Re: Allow people to do sudo apt-get build-dep without any further configuration
Should probably be add-apt-repository deb-src ? ** Package changed: apt (Ubuntu) => software-properties (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1802718 Title: Allow people to do sudo apt-get build-dep without any further configuration Status in software-properties package in Ubuntu: Confirmed Bug description: Or provide a reliable CLI method, a direct sed on /etc/atp/sources.list does not feel clean. Motivation: https://askubuntu.com/questions/496549/error-you-must-put- some-source-uris-in-your-sources-list This is specially important for Docker, but also a big annoyance on desktop, as there is no clean CLI way of enabling it. Why not just enable by default and save people the trouble? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1802718/+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 1802718] Re: Allow people to do sudo apt-get build-dep without any further configuration
Enabling by default does not make much sense and people usually use pull-lp-source instead which does not need sources.list entries and pulls directly from launchpad. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1802718 Title: Allow people to do sudo apt-get build-dep without any further configuration Status in software-properties package in Ubuntu: Confirmed Bug description: Or provide a reliable CLI method, a direct sed on /etc/atp/sources.list does not feel clean. Motivation: https://askubuntu.com/questions/496549/error-you-must-put- some-source-uris-in-your-sources-list This is specially important for Docker, but also a big annoyance on desktop, as there is no clean CLI way of enabling it. Why not just enable by default and save people the trouble? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1802718/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1888598] Re: pulseaudio has is buggy with hdmi audio and sleep/wake
after the resume, you run pacmd list-cards, do the hdmi-output-0 and -1 are "available: yes" as below? hdmi-output-0: HDMI / DisplayPort (priority 5900, latency offset 0 usec, available: yes) properties: device.icon_name = "video-display" device.product.name = "LG Ultra HD " hdmi-output-1: HDMI / DisplayPort 2 (priority 5800, latency offset 0 usec, available: yes) properties: device.icon_name = "video-display" device.product.name = "HTR-5063 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1888598 Title: pulseaudio has is buggy with hdmi audio and sleep/wake Status in pulseaudio package in Ubuntu: Confirmed Bug description: on a fresh Ubuntu 20.04 x64 install, I've noticed some troubling bugs with pulseaudio after putting my system to sleep and then waking it up. these bugs aren't present on a fresh boot, only after resuming from sleep: - it forgets which sound output device it's set to, and always reverse to the motherboard's S/PDIF output. - I have two devices connected to my video card, one is a displayport monitor, and one is a home theater receiver via HDMI. it confuses the two, and randomly switches which device it thinks is capable of surround sound. - it sometimes refuses to switch to the correct audio device, and just resets any choice back to the internal S/PDIF, until the system is rebooted. as you can imagine, this a pretty frustrating state of affairs. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu3.4 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: tessa 3387 F pulseaudio /dev/snd/pcmC1D7p: tessa 3387 F...m pulseaudio /dev/snd/controlC2: tessa 3387 F pulseaudio /dev/snd/controlC0: tessa 3387 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Jul 22 18:38:42 2020 InstallationDate: Installed on 2020-07-15 (7 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/18/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3503 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: GRYPHON Z97 dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3503:bd04/18/2018:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnGRYPHONZ97:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: ASUS MB dmi.product.name: All Series dmi.product.sku: All dmi.product.version: System Version dmi.sys.vendor: ASUS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1888598/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
