[Touch-packages] [Bug 1914106] Re: Xorg freeze
Thanks for the bug report. 1. Please open the 'Extensions' app and disable any you might have installed yourself. We need to check this first because so many bugs are caused by extensions. Even sometimes X11-specific. 2. Next time the freeze happens, please reboot and then open a Terminal and run: journalctl -b-1 > prevboot.txt and attach the resulting text file here. 3. Please check for any crash reports which might explain the graphics freezing, using these steps: https://wiki.ubuntu.com/Bugs/Responses#Missing_a_crash_report_or_having_a_.crash_attachment ** 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/1914106 Title: Xorg freeze Status in Ubuntu: Incomplete Bug description: I am not finding this problem in Wayland, just X11 / Xorg ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-65.73-generic 5.4.78 Uname: Linux 5.4.0-65-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 CasperMD5CheckResult: skip CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Feb 1 11:48:27 2021 DistUpgraded: 2020-09-20 17:26:20,447 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process “./xorg_fix_proprietary.py” (No such file or directory) (8)) DistroCodename: focal DistroVariant: ubuntu DkmsStatus: nvidia, 390.141, 5.4.0-64-generic, x86_64: installed nvidia, 390.141, 5.4.0-65-generic, x86_64: installed ExtraDebuggingInterest: Yes GpuHangFrequency: Continuously GpuHangReproducibility: Yes, I can easily reproduce it GpuHangStarted: Immediately after installing this version of Ubuntu GraphicsCard: Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. HD Graphics 620 [1043:1520] InstallationDate: Installed on 2017-07-04 (1308 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) MachineType: ASUSTeK COMPUTER INC. UX330UAK ProcEnviron: LANGUAGE=en_CA:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_CA.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-65-generic root=UUID=1778a8fc-a0e5-4815-9737-655369bac47b ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: Upgraded to focal on 2020-09-20 (133 days ago) dmi.bios.date: 04/19/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX330UAK.315 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX330UAK dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX330UAK.315:bd04/19/2019:svnASUSTeKCOMPUTERINC.:pnUX330UAK:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX330UAK:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: ZenBook dmi.product.name: UX330UAK dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz 1:0.9.14.1+20.04.20200211-0ubuntu1 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 20.2.6-0ubuntu0.20.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.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 xserver.bootTime: Mon Sep 21 15:47:24 2020 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.20.8-2ubuntu2.4 xserver.video_driver: modeset To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1914106/+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 1831039] Re: When using Wayland, the onscreen keyboard does not open in text inputs for non-GTK applications such as Firefox or Chrome
** Also affects: qtbase-opensource-src (Ubuntu) Importance: Undecided Status: New ** Changed in: qtbase-opensource-src (Ubuntu) Status: New => Confirmed ** Changed in: qtbase-opensource-src (Ubuntu) Importance: Undecided => Low -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtbase-opensource-src in Ubuntu. https://bugs.launchpad.net/bugs/1831039 Title: When using Wayland, the onscreen keyboard does not open in text inputs for non-GTK applications such as Firefox or Chrome Status in chromium-browser package in Ubuntu: Confirmed Status in firefox package in Ubuntu: Confirmed Status in gnome-shell package in Ubuntu: Confirmed Status in qtbase-opensource-src package in Ubuntu: Confirmed Bug description: When using wayland - onscreen keyboard not open in text inputs in many applications such as firefox or chrome. Ubuntu 18.04 --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2015-06-09 (1455 days ago) InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1) Package: gnome-shell 3.28.3+git20190124-0ubuntu18.04.2 PackageArchitecture: amd64 ProcEnviron: LANG=cs_CZ.UTF-8 TERM=xterm-256color SHELL=/bin/bash XDG_RUNTIME_DIR= PATH=(custom, no user) ProcVersionSignature: Ubuntu 4.15.0-50.54-generic 4.15.18 Tags: third-party-packages bionic Uname: Linux 4.15.0-50-generic x86_64 UpgradeStatus: Upgraded to bionic on 2018-05-31 (368 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1831039/+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 1871268] Re: Installation fails due to useless immediate configuration error when "Install Third-Party Drivers" is selected
** Changed in: ubuntu-cdimage Assignee: (unassigned) => davi gouvea santos (davi33) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1871268 Title: Installation fails due to useless immediate configuration error when "Install Third-Party Drivers" is selected Status in Ubuntu CD Images: Fix Released Status in apt package in Ubuntu: Fix Released Status in apt source package in Bionic: In Progress Status in apt source package in Focal: Fix Released Status in apt source package in Groovy: Fix Released Status in apt package in Debian: Unknown Bug description: [Impact] Installations that really succeeded would then fail because APT could not immediately configure a package. Which is a pointless way to fail at that point, because everything did work out anyway. We have two changes that help address this: * The first one stops immediately configuring multi-arch siblings (e.g. libc6:i386 when it's configuring libc6:amd64). This was not necessary, and caused all the libc6:i386 failures here. * The second change sort of also supersedes the first one: It just ignores any errors from immediate configuration, relying on the fact that it's checked and rectified at a later point if there are unconfigured packages (which is what made all those failures happen spuriously after having successfully installed everything). [Test case] We have one test case in EIPP format in the Debian bug 973305 which was only helped by the second change, not the first one. Run /usr/lib/apt/planners < eipp.log and check there are no errors. TODO: It's unclear if the APT from proposed installed in the live session will fix the installer, needs investigation, but would make a useful test case. [Regression potential] It's imaginable that we missed something somewhere and some path that checked for a set error doesn't check it anymore, and we report success when we hit an error, but it seems unlikely. Behavior of --simulate changes. This used to fail before as well, and will now only produce a warning. We don't believe that is a reason of concern. [Groovy SRU] The groovy SRU is a sync of the 2.1.11 micro release from Debian unstable which also incorporates changes to the documentation: A typo fix, replacing focal with groovy in examples, and minor Dutch manual pages translation updates. We do not have test cases for the documentation changes, and we do not consider there to be a huge regression potential. As long as they build, they should be readable - maybe some words are wrong in the translation, who knows. [Original bug report] Test Case 1. Install Ubuntu Desktop on hardware with an nVidia card and select to install 3rd party drivers 2. Proceed with installation The following error message is displayed in /var/log/syslog /plugininstall.py: Verifying downloads ... /plugininstall.py: Failed to find package object for /cdrom//pool/main/g/gcc-defaults/gcc_9.3.0-1ubuntu2_amd64.deb: "Version: '9.3.0-1ubuntu2' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libxcrypt/libcrypt-dev_4.4.10-10ubuntu4_amd64.deb: "Version: '4.4.10-10ubuntu4' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/g/gcc-defaults/g++_9.3.0-1ubuntu2_amd64.deb: "Version: '9.3.0-1ubuntu2' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/z/zlib/zlib1g_1.2.11.dfsg-2ubuntu1_i386.deb: "Version: '1.2.11.dfsg-2ubuntu1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libxau/libxau6_1.0.9-0ubuntu1_i386.deb: "Version: '1.0.9-0ubuntu1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libxdmcp/libxdmcp6_1.1.3-0ubuntu1_i386.deb: "Version: '1.1.3-0ubuntu1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libx11/libx11-6_1.6.9-2ubuntu1_i386.deb: "Version: '1.6.9-2ubuntu1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libxext/libxext6_1.3.4-0ubuntu1_i386.deb: "Version: '1.3.4-0ubuntu1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/l/lm-sensors/libsensors5_3.6.0-2ubuntu1_i386.deb: "Version: '3.6.0-2ubuntu1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libx11/libx11-xcb1_1.6.9-2ubuntu1_i386.deb: "Version: '1.6.9-2ubuntu1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libxdamage/libxdamage1_1.1.5-1_i386.deb: "Version: '1.1.5-1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libxfixes/libxfixes3_5.0.3-1_i386.deb: "Version: '5.0.3-1' not found." /plugininstall.py: Failed to find package object for /cdrom//po
[Touch-packages] [Bug 1913979] Re: misleading error messages when /etc/NetworkManager/system-connections is a cross-filesystem symlink
** Description changed: - As of a couple of days ago, I am unable to get network manager to - connect to any wifi network. + If the /etc/NetworkManager/system-connections directory is a cross- + filesystem symlink, activating connections will fail with the unrelated + messages: - It looks like the groovy network manager packages have not received any - updates since release, but since I can successfully use wpasupplicant - directly I'm ruling out issues with my specific home wifi or wifi card. + * "failed to create file ...: Read-only file system" (TRACE level) - Though this might still ultimately be due to my specific setup, the - error message logged by network manager is really insufficient for - determining where the failure may lie, even when debug mode is turned - on[0]. The Gnome UI doesn't display an error at all. + * "failure adding connection: settings plugin does not support adding + connections" (DEBUG level and above) + + * no error message (Gnome UI) + + I suspect moving the systems-connections directory onto a separate + filesystem is not supported because network manager tries to atomically + move a connection temp file into place and fails, but this is really + hard to figure out since the error messages are completely unrelated. + Versions: Ubuntu 20.10 network-manager 1.26.2-1ubuntu1 network-manager-gnome 1.18.0-1ubuntu2 + How to reproduce: + sudo mv /etc/NetworkManager/system-connections /some/other/mountpoint/system-connections + sudo ln -s /some/other/mountpoint/system-connections /etc/NetworkManager/system-connections + + Then: * select any wifi network via the Gnome UI, or * connect to a wifi network via nmcli, or * connect to a wifi network via nmtui + Symptoms: - * no UI popup is produced when using the Gnome UI - * the message "failure adding connection: settings plugin does not support adding connections" is shown when using nmcli or nmtui - * debug logs include slightly more information: + * "failed to create file ...: Read-only file system" (TRACE level, + journalctl) - Jan 31 20:32:57 laptop NetworkManager[3315]: [1612143177.8651] active-connection[0x55b6b9a25b50]: set device "wlp61s0" [0x55b6b9b62cb0] - Jan 31 20:32:57 laptop NetworkManager[3315]: [1612143177.8652] device[fd0e531202f8924b] (wlp61s0): add_pending_action (1): 'activation-22' - Jan 31 20:32:57 laptop NetworkManager[3315]: [1612143177.8653] active-connection[0x55b6b9a25b50]: constructed (NMActRequest, version-id 22, type managed) - Jan 31 20:32:57 laptop NetworkManager[3315]: [1612143177.8807] active-connection[0x55b6b9a25b50]: Failed to activate '(null)': failure adding connection: settings plugin does not support adding connections - Jan 31 20:32:57 laptop NetworkManager[3315]: [1612143177.8808] active-connection[0x55b6b9a25b50]: set state deactivated (was unknown) - Jan 31 20:32:57 laptop NetworkManager[3315]: [1612143177.8808] active-connection[0x55b6b9a25b50]: check-master-ready: not signalling (state deactivated, no master) - Jan 31 20:32:57 laptop NetworkManager[3315]: [1612143177.8808] device[fd0e531202f8924b] (wlp61s0): remove_pending_action (0): 'activation-22' - Jan 31 20:32:57 laptop NetworkManager[3315]: [1612143177.8811] audit: op="connection-add-activate" pid=452187 uid=1000 result="fail" reason="failure adding connection: settings plugin does not support adding connections" - Jan 31 20:32:57 laptop NetworkManager[3315]: [1612143177.8812] active-connection[0x55b6b9a25b50]: disposing + * "failure adding connection: settings plugin does not support adding + connections" (DEBUG level and above, journalctl and nmtui/nmcli output) - Workaround: - - * connect to networks by using wpasupplicant directly[1] + * no error message (Gnome UI) - [0] https://wiki.gnome.org/Projects/NetworkManager/Debugging - [1] https://shapeshed.com/linux-wifi/ + Relevant sample logs: + + Feb 01 20:56:04 laptop NetworkManager[1368510]: [1612230964.4038] active-connection[0x56274f6f0a60]: creating + Feb 01 20:56:04 laptop NetworkManager[1368510]: [1612230964.4039] active-connection[0x56274f6f0a60]: set device "wlp61s0" [0x56274f883f00] + Feb 01 20:56:04 laptop NetworkManager[1368510]: [1612230964.4039] device[d62304f9da70d783] (wlp61s0): add_pending_action (1): 'activation-5' + Feb 01 20:56:04 laptop NetworkManager[1368510]: [1612230964.4040] active-connection[0x56274f6f0a60]: constructed (NMActRequest, version-id 5, type managed) + Feb 01 20:56:04 laptop NetworkManager[1368510]: [1612230964.4040] auth: call[37]: CheckAuthorization(org.freedesktop.NetworkManager.network-control), subject=unix-process[pid=1369566, uid=0, start=18908113] (succeeding for root) + Feb 01 20:56:04 laptop NetworkManager[1368510]: [1612230964.4041] auth: call[37]: completed: authorized=1, challenge=0 (simulated) + Feb 01 20:56:04 laptop NetworkManager[1368510]: [1612230964.4041] auth: call[38]: CheckAuthorization(org.freedesktop.NetworkManager.set
[Touch-packages] [Bug 1913979] Re: misleading error messages when /etc/NetworkManager/system-connections is a cross-filesystem symlink
** Summary changed: - settings plugin does not support adding connections + misleading error messages when /etc/NetworkManager/system-connections is a cross-filesystem symlink -- 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/1913979 Title: misleading error messages when /etc/NetworkManager/system-connections is a cross-filesystem symlink Status in network-manager package in Ubuntu: New Bug description: As of a couple of days ago, I am unable to get network manager to connect to any wifi network. It looks like the groovy network manager packages have not received any updates since release, but since I can successfully use wpasupplicant directly I'm ruling out issues with my specific home wifi or wifi card. Though this might still ultimately be due to my specific setup, the error message logged by network manager is really insufficient for determining where the failure may lie, even when debug mode is turned on[0]. The Gnome UI doesn't display an error at all. Versions: Ubuntu 20.10 network-manager 1.26.2-1ubuntu1 network-manager-gnome 1.18.0-1ubuntu2 How to reproduce: * select any wifi network via the Gnome UI, or * connect to a wifi network via nmcli, or * connect to a wifi network via nmtui Symptoms: * no UI popup is produced when using the Gnome UI * the message "failure adding connection: settings plugin does not support adding connections" is shown when using nmcli or nmtui * debug logs include slightly more information: Jan 31 20:32:57 laptop NetworkManager[3315]: [1612143177.8651] active-connection[0x55b6b9a25b50]: set device "wlp61s0" [0x55b6b9b62cb0] Jan 31 20:32:57 laptop NetworkManager[3315]: [1612143177.8652] device[fd0e531202f8924b] (wlp61s0): add_pending_action (1): 'activation-22' Jan 31 20:32:57 laptop NetworkManager[3315]: [1612143177.8653] active-connection[0x55b6b9a25b50]: constructed (NMActRequest, version-id 22, type managed) Jan 31 20:32:57 laptop NetworkManager[3315]: [1612143177.8807] active-connection[0x55b6b9a25b50]: Failed to activate '(null)': failure adding connection: settings plugin does not support adding connections Jan 31 20:32:57 laptop NetworkManager[3315]: [1612143177.8808] active-connection[0x55b6b9a25b50]: set state deactivated (was unknown) Jan 31 20:32:57 laptop NetworkManager[3315]: [1612143177.8808] active-connection[0x55b6b9a25b50]: check-master-ready: not signalling (state deactivated, no master) Jan 31 20:32:57 laptop NetworkManager[3315]: [1612143177.8808] device[fd0e531202f8924b] (wlp61s0): remove_pending_action (0): 'activation-22' Jan 31 20:32:57 laptop NetworkManager[3315]: [1612143177.8811] audit: op="connection-add-activate" pid=452187 uid=1000 result="fail" reason="failure adding connection: settings plugin does not support adding connections" Jan 31 20:32:57 laptop NetworkManager[3315]: [1612143177.8812] active-connection[0x55b6b9a25b50]: disposing Workaround: * connect to networks by using wpasupplicant directly[1] [0] https://wiki.gnome.org/Projects/NetworkManager/Debugging [1] https://shapeshed.com/linux-wifi/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1913979/+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 1912330] Re: regression: non-X VTs stopped using energy star after xenial
** Summary changed: - non-X VTs should use energy star + regression: non-X VTs stopped using energy star after xenial ** Description changed: - it's simple. it's easy. let's get our servers being good energy star - citizens shall we? + as of xenial, non-X VTs timed out and powered down even if nobody ever + logged in. but that's no longer true in bionic and focal. if a VT is running X at all, whether that's running sddm and never logged in, or sddm and logged-in, or not running sddm and simply logged- in and running X started with startx, that VT will timeout and - powerdown. so far so good. + powerdown, even on bionic and focal. no problem there. but a VT that's either running getty, or logged in and just running - bash, will stay powered up and blazing away forever, whether it's ubuntu - server 20.04, lubuntu 20.04, or centos 8. + bash, will stay powered up and blazing away forever, if it's ubuntu + 18.04 or 20.04, server or lubuntu. or centos 8. so probably RHEL 8 too, so probably most servers, aren't being good - energy star citizens! boo! + energy star citizens anymore. something happened since xenial. the util-linux package is used by both centos 8 and ubuntu 20.04, and contains both getty and setterm. - thus getty seems to me to be the sensible place to call: + probably getty would be the place, that either used to call, or should + now call: setterm -term=linux -powersave=powerdown -powerdown=15 -store>/dev/tty0https://bugs.launchpad.net/bugs/1912330 Title: regression: non-X VTs stopped using energy star after xenial Status in util-linux package in Ubuntu: New Bug description: as of xenial, non-X VTs timed out and powered down even if nobody ever logged in. but that's no longer true in bionic and focal. if a VT is running X at all, whether that's running sddm and never logged in, or sddm and logged-in, or not running sddm and simply logged-in and running X started with startx, that VT will timeout and powerdown, even on bionic and focal. no problem there. but a VT that's either running getty, or logged in and just running bash, will stay powered up and blazing away forever, if it's ubuntu 18.04 or 20.04, server or lubuntu. or centos 8. so probably RHEL 8 too, so probably most servers, aren't being good energy star citizens anymore. something happened since xenial. the util-linux package is used by both centos 8 and ubuntu 20.04, and contains both getty and setterm. probably getty would be the place, that either used to call, or should now call: setterm -term=linux -powersave=powerdown -powerdown=15 -store>/dev/tty0https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1912330/+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 1914029] Re: pulseaudio startup script should not blindly force audible bell
*** This bug is a duplicate of bug 1827842 *** https://bugs.launchpad.net/bugs/1827842 Thanks for the bug report. It appears this was already fixed (removed) at some point between Ubuntu 18.04 and 20.04. ** Changed in: pulseaudio (Ubuntu) Status: New => Fix Released ** This bug has been marked a duplicate of bug 1827842 pulseaudio should not load module-x11-bell in gnome-shell -- 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/1914029 Title: pulseaudio startup script should not blindly force audible bell Status in pulseaudio package in Ubuntu: Fix Released Bug description: File /usr/bin/start-pulseaudio-x11 ALWAYS loads module module-x11-bell and uploads audio sample for Pulseaudio if the file /usr/share/sounds/ubuntu/stereo/bell.ogg EXISTS in the filesystem. I have configured only visual bell for everything and therefore any part of the system that forcibly tries to play any kind of audio for bell output is simply broken. At bare minimum, this script should first check if the desktop environment has been configured to use visual bell instead of audible bell before loading the module. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: pulseaudio 1:11.1-1ubuntu7.11 ProcVersionSignature: Ubuntu 5.4.0-64.72~18.04.1-lowlatency 5.4.78 Uname: Linux 5.4.0-64-lowlatency x86_64 ApportVersion: 2.20.9-0ubuntu7.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: mira 6634 F pulseaudio /dev/snd/controlC0: mira 6634 F pulseaudio CurrentDesktop: MATE Date: Mon Feb 1 11:48:03 2021 EcryptfsInUse: Yes InstallationDate: Installed on 2019-01-05 (757 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/17/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1505 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: P8H77-M PRO dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1505:bd10/17/2014:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP8H77-MPRO:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: 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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1914029/+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 1914053] Re: US intl. Deadkeys not working in some programs
I'm not sure which package(s) this should be but 'xorg' is not a package that provides any relevant binaries. Moving to 'xorg-server'. ** Tags added: focal ** Package changed: xorg (Ubuntu) => xorg-server (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/1914053 Title: US intl. Deadkeys not working in some programs Status in xorg-server package in Ubuntu: New Bug description: Kubuntu 20.04 KDE Plasma 5.18.5 KDE Frameworks Version: 5.68.0 Qt Version: 5.12.8 xorg: Installed: 1:7.7+19ubuntu14 Candidate: 1:7.7+19ubuntu14 Version table: *** 1:7.7+19ubuntu14 500 500 http://no.archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status The keyboard layout is set as English (US, intl., with dead keys) to deal with European lettering. This worked fine for a long time, but suddenly, the dead keys are not working in several programs. As in, when typing the dead key nothing happens. E.g. they don't work in browsers (checked in Firefox and Chrome) and in the Matrix Element program. However, they do work in other programs, such as Kate and LibreOffice. Normally one can type an apostrophe (') by hitting that key and typing a space, but now the only way to get that character in those few programs is by pressing Alt Gr+' . The same thing for letters like é. Normally pressing '+e would work, now only Alt Gr+e works. Apport bug report (aka ubuntu-bug xorg) did not work for the xorg package. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1914053/+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 1913411] Re: Support for 5G (ModemManager >= 1.14.0)
Thanks for the details. We would first need a GNOME developer to backport the aforementioned gnome-shell patches to the gnome-3-36 branch. After that it could be included in Ubuntu 20.04 updates. ** Summary changed: - While I updating ModemManager to 1.14.2, there isno mobile broadband in system status bar drop-down menu. + Support for 5G (ModemManager >= 1.14.0) ** Changed in: modemmanager (Ubuntu) Status: Invalid => Fix Released ** Changed in: gnome-shell (Ubuntu) Status: Invalid => Fix Released ** Tags added: fixed-in-3.38.2 fixed-upstream -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to modemmanager in Ubuntu. https://bugs.launchpad.net/bugs/1913411 Title: Support for 5G (ModemManager >= 1.14.0) Status in gnome-shell package in Ubuntu: Fix Released Status in modemmanager package in Ubuntu: Fix Released Bug description: While I updating ModemManager to 1.14.2, there isno mobile broadband in system status bar drop-down menu. I just can see mobile broadband in network in system settings menu. OS: ubuntu20.04 Module: SDX55 ModemManager:1.14.2 iusse: 1.No mobile broadband in system status bar drop-down menu. 2.Every time I connect to the mobile broadband network in system settings menu, I need to add new connection. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1913411/+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 1913859] Re: RT3290 Bluetooth not finding any device
*** This bug is a duplicate of bug 1914007 *** https://bugs.launchpad.net/bugs/1914007 ** This bug has been marked a duplicate of bug 1914007 RT3290 Bluetooth not finding any device -- 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/1913859 Title: RT3290 Bluetooth not finding any device Status in bluez package in Ubuntu: Invalid Bug description: Ubuntu :- 20.04 Hello I have RT3290 bluetooth in built and it was not working so I installed its latest driver from github whose version is 3.9.6 . Now its working but its not discoverable to any other device and also not finding any other device. Outout of command :- service bluetooth status ● bluetooth.service - Bluetooth service Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled; vendor pre> Active: active (running) since Sat 2021-01-30 09:49:10 IST; 1h 0min ago Docs: man:bluetoothd(8) Main PID: 1389 (bluetoothd) Status: "Running" Tasks: 1 (limit: 4514) Memory: 2.0M CGroup: /system.slice/bluetooth.service └─1389 /usr/lib/bluetooth/bluetoothd Jan 30 09:49:07 Piyush-X55C systemd[1]: Starting Bluetooth service... Jan 30 09:49:10 Piyush-X55C bluetoothd[1389]: Bluetooth daemon 5.53 Jan 30 09:49:10 Piyush-X55C systemd[1]: Started Bluetooth service. Jan 30 09:49:10 Piyush-X55C bluetoothd[1389]: Starting SDP server Jan 30 09:49:10 Piyush-X55C bluetoothd[1389]: Bluetooth management interface 1.> Jan 30 10:49:34 Piyush-X55C bluetoothd[1389]: Endpoint registered: sender=:1.66> Jan 30 10:49:34 Piyush-X55C bluetoothd[1389]: Endpoint registered: sender=:1.66> lines 1-18/18 (END) Output of command :- sudo btmgmt info Index list with 1 item hci0: Primary controller addr A4:17:31:1D:65:54 version 4 manufacturer 91 class 0x00 supported settings: powered connectable fast-connectable discoverable bondable link-security ssp br/edr debug-keys current settings: powered bondable ssp br/edr name Piyush-X55C Output of command :- bluetoothctl Agent registered [bluetooth]# scan on [bluetooth]# discoverable on [bluetooth]# scan on Failed to start discovery: org.bluez.Error.InProgress [bluetooth]# discoverable on Changing discoverable on succeeded [bluetooth]# Output of command :- sudo btmgmt find Unable to start discovery. status 0x0c (Not Supported) Output of command :- lspci -knn | grep Net -A3; lsusb 02:00.0 Network controller [0280]: Ralink corp. RT3290 Wireless 802.11n 1T/1R PCIe [1814:3290] Subsystem: Foxconn International, Inc. RT3290 Wireless 802.11n 1T/1R PCIe [105b:e055] Kernel driver in use: rt2800pci Kernel modules: rt2800pci Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 003: ID 1bcf:2883 Sunplus Innovation Technology Inc. Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 003 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Output of command :-dmesg | grep -i bluetooth [ 12.851854] Bluetooth: Core ver 2.22 [ 12.851883] Bluetooth: HCI device and connection manager initialized [ 12.851888] Bluetooth: HCI socket layer initialized [ 12.851889] Bluetooth: L2CAP socket layer initialized [ 12.851893] Bluetooth: SCO socket layer initialized [ 67.399550] audit: type=1400 audit(1611909043.091:58): apparmor="DENIED" operation="create" profile="snap.bluez.bluez" pid=875 comm="bluetoothd" family="bluetooth" sock_type="raw" protocol=1 requested_mask="create" denied_mask="create" [ 67.727240] audit: type=1400 audit(1611909043.419:60): apparmor="DENIED" operation="connect" profile="snap.bluez.bluez" name="/run/dbus/system_bus_socket" pid=875 comm="bluetoothd" requested_mask="wr" denied_mask="wr" fsuid=0 ouid=0 [ 67.929889] audit: type=1400 audit(1611909043.619:62): apparmor="DENIED" operation="create" profile="snap.bluez.bluez" pid=1043 comm="bluetoothd" family="bluetooth" sock_type="raw" protocol=1 requested_mask="create" denied_mask="create" [ 67.930261] audit: type=1400 audit(1611909043.623:63): apparmor="DENIED" operation="connect" profile="snap.bluez.bluez" name="/run/dbus/system_bus_socket" pid=1043 comm="bluetoothd" requested_mask="wr" denied_mask="wr" fsuid=0 ouid=0 [ 68.194380] audit: type=1400 audit(1611909043.887:65): apparmor="DENIED" operation="create" profile="snap.bluez.bluez" pid=1102 comm="bluetoothd" family="bluetooth" sock_type="raw" protocol=1 requested_mask="create" denied_mask="create" [ 68.194
[Touch-packages] [Bug 1838151] Re: Poor quality audio with modern Bluetooth headsets in HSP/HFP. Missing wide band speech support (Bluetooth A2DP codecs).
** Changed in: pulseaudio (Ubuntu) Status: Triaged => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1838151 Title: Poor quality audio with modern Bluetooth headsets in HSP/HFP. Missing wide band speech support (Bluetooth A2DP codecs). Status in PulseAudio: New Status in bluez package in Ubuntu: Fix Released Status in linux package in Ubuntu: Fix Released Status in pulseaudio package in Ubuntu: Fix Committed Status in Arch Linux: New Bug description: Bluetooth HSP/HFP audio quality is poor on Ubuntu comparative to all other major platforms (Windows, MacOS, ChromeOS, Android, iOS). Modern Bluetooth headsets (such as the Bose QC series headphones, many others) are capable of using HFP 1.6 with mSBC 16kHz audio encoding. As it currently stands, Ubuntu defaults to only supporting HSP headsets using 8kHz CVSD, and is incapable of supporting HFP 1.6 at this time. The ChromiumOS team recently tackled this issue - https://bugs.chromium.org/p/chromium/issues/detail?id=843048 Their efforts may assist in bringing this to Ubuntu, however it appears that there are quite a lot of differences considering they have developed their own audio server solution etc. The Bluetooth Telephony Working Group published the HFP 1.6 spec in May 2011 - https://www.bluetooth.org/docman/handlers/downloaddoc.ashx?doc_id=238193 Patches have been proposed in the past for this issue to the kernel and PulseAudio: PulseAudio: https://patchwork.freedesktop.org/patch/245272/ Kernel: https://www.spinics.net/lists/linux-bluetooth/msg76982.html It appears that the Chromium OS team applied the same kernel patch: https://chromium.googlesource.com/chromiumos/third_party/kernel/+/77dd0cb94c1713a8a12f6e392955dfa64c430e54 ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: pulseaudio 1:12.2-2ubuntu3 ProcVersionSignature: Ubuntu 5.0.0-20.21-generic 5.0.8 Uname: Linux 5.0.0-20-generic x86_64 ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jnappi 2777 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sat Jul 27 11:08:29 2019 EcryptfsInUse: Yes InstallationDate: Installed on 2017-11-04 (629 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio UpgradeStatus: Upgraded to disco on 2019-07-18 (9 days ago) dmi.bios.date: 06/07/2016 dmi.bios.vendor: LENOVO dmi.bios.version: R07ET67W (2.07 ) dmi.board.asset.tag: Not Available dmi.board.name: 20FW000TUS dmi.board.vendor: LENOVO dmi.board.version: SDK0J40705 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrR07ET67W(2.07):bd06/07/2016:svnLENOVO:pn20FW000TUS:pvrThinkPadT460p:rvnLENOVO:rn20FW000TUS:rvrSDK0J40705WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T460p dmi.product.name: 20FW000TUS dmi.product.sku: LENOVO_MT_20FW_BU_Think_FM_ThinkPad T460p dmi.product.version: ThinkPad T460p dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/1838151/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1912535] Re: [SRU] python-cffi and libffi in Groovy need a no-change rebuild
** Changed in: python-cffi (Ubuntu Groovy) Status: New => Incomplete ** Changed in: libffi (Ubuntu Groovy) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libffi in Ubuntu. https://bugs.launchpad.net/bugs/1912535 Title: [SRU] python-cffi and libffi in Groovy need a no-change rebuild Status in libffi package in Ubuntu: Fix Released Status in python-cffi package in Ubuntu: Fix Released Status in libffi source package in Groovy: Incomplete Status in python-cffi source package in Groovy: Incomplete Status in libffi source package in Hirsute: Fix Released Status in python-cffi source package in Hirsute: Fix Released Bug description: [Impact] * Users of studio-controls have been reporting bugs against studio- controls upstream on Github. For reference, see https://github.com/ovenwerks/studio-controls/issues/43 * Per the bug report, the following error is being thrown: SystemError: ffi_prep_closure(): bad user_data (it seems that the version of the libffi library seen at runtime is different from the 'ffi.h' file seen at compile-time) * Based on this error, and based on the build time of python-cffi and libffi in relation to cffi, it appears as though python-cffi and libffi were built on an older version of cffi. This explains the error. [Test Case] * A certain number of users have reported that simply running studio- controls causes this error. [Where problems could occur] * Since this is a no-change rebuild being requested, the possibility of breakage is slim to none. We are introducing no new changes here, but rather, resolving a regression that happened as a result of a newer version of cffi being introduced without a rebuild of dependencies. * If any problems happen, it would be a result of applications using python-cffi and expecting this bug with built-in workarounds. I can't imagine such a case exists, so this is just a stretch. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libffi/+bug/1912535/+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 1914148] Re: Firefox connstantly disabled on Apparmor
The Firefox AppArmor profile isn't enabled by default because it forces the user to change how they interact with their browser. Consider that the profile really allows downloads only into ~/Downloads/ directories. (There's other places that are writable, but even less suitable for downloads.) Many users prefer to download directly to their existing directory structure. Consider the wide variety of plugins that may supply helper executables. Plugins failing without a good interface in the browser to know why they have failed would be very confusing. Consider the huge number of applications that people install to handle mime types. People want to be able to click a link to any random file and have the browser offer to launch the helper. People who are fine with all these impositions in how they can use Firefox can enable the Firefox profile. They'll know how to debug issues when they arise, and furthermore, probably already have a workflow that makes it easy to work with the AppArmor policy restrictions. But most Ubuntu users are completely unaware that they're running AppArmor on many of their services. Surely some of this group would like to use it more, if only they knew about it, but also many people just need their computers to keep working as they always have. If we enable this one profile, we run the serious risk that users will disable AppArmor entirely. Thanks ** Package changed: apparmor (Ubuntu) => firefox (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/1914148 Title: Firefox connstantly disabled on Apparmor Status in firefox package in Ubuntu: New Bug description: Once again Apparmor policies are constantly disabled for Firefox. -I've reported this bug in December, then came a patch, then for the last month of January - regardless of updates, Firefox profiles are skipped. - You cannot be serious? -This is a consistent seccurity issue! - Please write rules that consistently work or teach us how to do so / deal with Mozilla "Feb 02 00:17:24 USER apparmor.systemd[1117]: Skipping profile in /etc/apparmor.d/disable: usr.bin.firefox Feb 02 00:17:24 USER apparmor.systemd[1118]: Skipping profile in /etc/apparmor.d/disable: usr.sbin.rsyslogd Feb 02 00:17:24 USER systemd[1]: Finished Load AppArmor profiles. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1914148/+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 1914148] [NEW] Firefox connstantly disabled on Apparmor
Public bug reported: Once again Apparmor policies are constantly disabled for Firefox. -I've reported this bug in December, then came a patch, then for the last month of January - regardless of updates, Firefox profiles are skipped. - You cannot be serious? -This is a consistent seccurity issue! - Please write rules that consistently work or teach us how to do so / deal with Mozilla "Feb 02 00:17:24 USER apparmor.systemd[1117]: Skipping profile in /etc/apparmor.d/disable: usr.bin.firefox Feb 02 00:17:24 USER apparmor.systemd[1118]: Skipping profile in /etc/apparmor.d/disable: usr.sbin.rsyslogd Feb 02 00:17:24 USER systemd[1]: Finished Load AppArmor profiles. ** Affects: apparmor (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/1914148 Title: Firefox connstantly disabled on Apparmor Status in apparmor package in Ubuntu: New Bug description: Once again Apparmor policies are constantly disabled for Firefox. -I've reported this bug in December, then came a patch, then for the last month of January - regardless of updates, Firefox profiles are skipped. - You cannot be serious? -This is a consistent seccurity issue! - Please write rules that consistently work or teach us how to do so / deal with Mozilla "Feb 02 00:17:24 USER apparmor.systemd[1117]: Skipping profile in /etc/apparmor.d/disable: usr.bin.firefox Feb 02 00:17:24 USER apparmor.systemd[1118]: Skipping profile in /etc/apparmor.d/disable: usr.sbin.rsyslogd Feb 02 00:17:24 USER systemd[1]: Finished Load AppArmor profiles. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1914148/+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 1912330] Re: non-X VTs should use energy star
** Description changed: it's simple. it's easy. let's get our servers being good energy star citizens shall we? if a VT is running X at all, whether that's running sddm and never logged in, or sddm and logged-in, or not running sddm and simply logged- in and running X started with startx, that VT will timeout and powerdown. so far so good. but a VT that's either running getty, or logged in and just running bash, will stay powered up and blazing away forever, whether it's ubuntu server 20.04, lubuntu 20.04, or centos 8. so probably RHEL 8 too, so probably most servers, aren't being good energy star citizens! boo! the util-linux package is used by both centos 8 and ubuntu 20.04, and contains both getty and setterm. thus getty seems to me to be the sensible place to call: - setterm -powersave=powerdown -powerdown=15 -store + setterm -term=linux -powersave=powerdown -powerdown=15 + -store>/dev/tty0https://bugs.launchpad.net/bugs/1912330 Title: non-X VTs should use energy star Status in util-linux package in Ubuntu: New Bug description: it's simple. it's easy. let's get our servers being good energy star citizens shall we? if a VT is running X at all, whether that's running sddm and never logged in, or sddm and logged-in, or not running sddm and simply logged-in and running X started with startx, that VT will timeout and powerdown. so far so good. but a VT that's either running getty, or logged in and just running bash, will stay powered up and blazing away forever, whether it's ubuntu server 20.04, lubuntu 20.04, or centos 8. so probably RHEL 8 too, so probably most servers, aren't being good energy star citizens! boo! the util-linux package is used by both centos 8 and ubuntu 20.04, and contains both getty and setterm. thus getty seems to me to be the sensible place to call: setterm -term=linux -powersave=powerdown -powerdown=15 -store>/dev/tty0https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1912330/+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 1894329] Re: ZFS revert from grub menu not working.
** No longer affects: coreutils (Ubuntu Groovy) ** No longer affects: coreutils (Ubuntu Focal) ** No longer affects: coreutils (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to coreutils in Ubuntu. https://bugs.launchpad.net/bugs/1894329 Title: ZFS revert from grub menu not working. Status in zfs-linux package in Ubuntu: Fix Released Status in zfs-linux source package in Focal: Fix Released Status in zfs-linux source package in Groovy: Fix Released Bug description: [Impact] * Users can’t revert to previous snapshots when enabling the hw enablement stack kernel on focal or using any more recent version. * The option is available on grub and will let you with a broken system, partially cloned. [Test Case] * Boot on a system, using ZFS and ZSys. * In grub, select "History" entry * Select one of the "Revert" option: the system should boot after being reverted with an older version. [Where problems could occur] * The code is in the initramfs, where the generated id suffix for all our ZFS datasets was empty due to new coreutils/kernels. * We replace dd with another way (more robust and simple) for generating this ID. - @coreutils maintainers, any idea why dd is being flagged as having an executable stack? When I try to revert to a previous state from the grub menu, the boot fails. The system drops me to a repair modus. zfs-mount-generator fails with the message: couldn't ensure boot: Mounted clone bootFS dataset created by initramfs doesn't have a valid _suffix (at least .*_): \"rpool/ROOT/ubuntu_\"". After a reboot I have an extra clone called "rpool/ROOT/ubuntu_", indeed without a suffix. After a little investigation I found the problem in /usr/share/initramfs-tools/scripts/zfs at the end in function uid() { dd if=/dev/urandom of=/dev/stdout bs=1 count=100 2>/dev/null | tr -dc 'a-z0-9' | cut -c-6 }, the dd command fails during boot with the message "process 'dd' started with executable stack. After this an empty uid is returned which explains the dataset without a proper suffix. Replacing the function with: uid() { grep -a -m10 -E "\*" /dev/urandom 2>/dev/null | tr -dc 'a-z0-9' | cut -c-6 } fixes the problem. Ubuntu version is: Description:Ubuntu Groovy Gorilla (development branch) Release:20.10 zfs-initramfs version is: 0.8.4-1ubuntu11 With regards, Usarin Heininga ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: zfs-initramfs 0.8.4-1ubuntu11 ProcVersionSignature: Ubuntu 5.8.0-18.19-generic 5.8.4 Uname: Linux 5.8.0-18-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu45 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Fri Sep 4 20:23:44 2020 InstallationDate: Installed on 2020-09-02 (2 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200831) ProcEnviron: LANGUAGE= PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=nl_NL.UTF-8 SHELL=/bin/bash SourcePackage: zfs-linux UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1894329/+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 1856392] Re: [HP ZBook 15 G6, Realtek ALC285, Black Mic, Right] Microphone not detected
Just as a follow-up on this topic. now running Linux ZBook15G6 5.8.0-41-generic #46-Ubuntu SMP Mon Jan 18 16:48:44 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux and things are a bit better. I have everything working fine (mic + sound + thunderbolt dock), but I have to boot the laptop unplugged to the AC adapter. When doing so, everything works fine. If I boot the laptop with the AC adaptor hooked (and of course power supply), then mic in ok, but I then have no sound. This seems strange to me, but this is the actually observed / repeatable behaviour. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1856392 Title: [HP ZBook 15 G6, Realtek ALC285, Black Mic, Right] Microphone not detected Status in alsa-driver package in Ubuntu: Expired Status in linux package in Ubuntu: Expired Bug description: Hello, on a brand new HPZbook15G6, with a fresh dual boot 19.10 Ubuntu install, I have no internal mic detected. The GNOME settings sound entry list is empty. Speaker sound is working properly. When hooking a microphone enabled headphone on the jack plug, the headphones mic is then detected, but there is now no sound output on the headphone. I've been looking for a few similar issues on recent (HP or not) laptops and found a few similar issues : Bug #1523100 Bug #1837821 so I guess this is a generic alsa or snd-hda-intel issue with newer ALC2xx hardware. I already tryed quite a few of the workaroubds/fix available here and there (e.g. overriding pin with hdajackretask, adding options to snd-hda-intel module etc. none with success) I'm available to test/provide any additional needed data. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 Uname: Linux 5.3.0-24-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: mathieu1719 F pulseaudio /dev/snd/controlC0: mathieu1719 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sat Dec 14 13:33:14 2019 InstallationDate: Installed on 2019-12-13 (0 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaRecordingTest: ALSA recording test through plughw:PCH successful Symptom_Card: Audio interne - HDA Intel PCH Symptom_Jack: Black Mic, Right Symptom_PulseAudioRecordingTest: PulseAudio recording test through plughw:PCH successful Symptom_Type: Only some of inputs are working Title: [HP ZBook 15 G6, Realtek ALC285, Black Mic, Right] Recording problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/06/2019 dmi.bios.vendor: HP dmi.bios.version: R92 Ver. 01.03.04 dmi.board.name: 860F dmi.board.vendor: HP dmi.board.version: KBC Version 65.23.00 dmi.chassis.asset.tag: 5CD944676Z dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrR92Ver.01.03.04:bd11/06/2019:svnHP:pnHPZBook15G6:pvr:rvnHP:rn860F:rvrKBCVersion65.23.00:cvnHP:ct10:cvr: dmi.product.family: 103C_5336AN HP ZBook dmi.product.name: HP ZBook 15 G6 dmi.product.sku: 6VD99AV dmi.sys.vendor: HP mtime.conffile..etc.modprobe.d.alsa-base.conf: 2019-12-14T13:26:02.404591 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1856392/+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 1914106] [NEW] Xorg freeze
Public bug reported: I am not finding this problem in Wayland, just X11 / Xorg ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-65.73-generic 5.4.78 Uname: Linux 5.4.0-65-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 CasperMD5CheckResult: skip CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Feb 1 11:48:27 2021 DistUpgraded: 2020-09-20 17:26:20,447 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process “./xorg_fix_proprietary.py” (No such file or directory) (8)) DistroCodename: focal DistroVariant: ubuntu DkmsStatus: nvidia, 390.141, 5.4.0-64-generic, x86_64: installed nvidia, 390.141, 5.4.0-65-generic, x86_64: installed ExtraDebuggingInterest: Yes GpuHangFrequency: Continuously GpuHangReproducibility: Yes, I can easily reproduce it GpuHangStarted: Immediately after installing this version of Ubuntu GraphicsCard: Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. HD Graphics 620 [1043:1520] InstallationDate: Installed on 2017-07-04 (1308 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) MachineType: ASUSTeK COMPUTER INC. UX330UAK ProcEnviron: LANGUAGE=en_CA:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_CA.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-65-generic root=UUID=1778a8fc-a0e5-4815-9737-655369bac47b ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: Upgraded to focal on 2020-09-20 (133 days ago) dmi.bios.date: 04/19/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX330UAK.315 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX330UAK dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX330UAK.315:bd04/19/2019:svnASUSTeKCOMPUTERINC.:pnUX330UAK:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX330UAK:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: ZenBook dmi.product.name: UX330UAK dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz 1:0.9.14.1+20.04.20200211-0ubuntu1 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 20.2.6-0ubuntu0.20.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.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 xserver.bootTime: Mon Sep 21 15:47:24 2020 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.20.8-2ubuntu2.4 xserver.video_driver: modeset ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal freeze third-party-packages ubuntu wayland-session -- 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/1914106 Title: Xorg freeze Status in xorg package in Ubuntu: New Bug description: I am not finding this problem in Wayland, just X11 / Xorg ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-65.73-generic 5.4.78 Uname: Linux 5.4.0-65-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 CasperMD5CheckResult: skip CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Feb 1 11:48:27 2021 DistUpgraded: 2020-09-20 17:26:20,447 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process “./xorg_fix_proprietary.py” (No such file or directory) (8)) DistroCodename: focal DistroVariant: ubuntu DkmsStatus: nvidia, 390.141, 5.4.0-64-generic, x86_64: installed nvidia, 390.141, 5.4.0-65-generic, x86_64: installed ExtraDebuggingInterest: Yes GpuHangFrequency: Continuously GpuHangReproducibility: Yes, I can easily reproduce it GpuHangStarted: Immediately after installing this version of Ubuntu GraphicsCard: Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. HD Graphics 620 [1043:1520] InstallationDate: I
[Touch-packages] [Bug 1871268] Re: Installation fails due to useless immediate configuration error when "Install Third-Party Drivers" is selected
** Changed in: ubuntu-cdimage Assignee: Andrius KL (andrewdaman) => (unassigned) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1871268 Title: Installation fails due to useless immediate configuration error when "Install Third-Party Drivers" is selected Status in Ubuntu CD Images: Fix Released Status in apt package in Ubuntu: Fix Released Status in apt source package in Bionic: In Progress Status in apt source package in Focal: Fix Released Status in apt source package in Groovy: Fix Released Status in apt package in Debian: Unknown Bug description: [Impact] Installations that really succeeded would then fail because APT could not immediately configure a package. Which is a pointless way to fail at that point, because everything did work out anyway. We have two changes that help address this: * The first one stops immediately configuring multi-arch siblings (e.g. libc6:i386 when it's configuring libc6:amd64). This was not necessary, and caused all the libc6:i386 failures here. * The second change sort of also supersedes the first one: It just ignores any errors from immediate configuration, relying on the fact that it's checked and rectified at a later point if there are unconfigured packages (which is what made all those failures happen spuriously after having successfully installed everything). [Test case] We have one test case in EIPP format in the Debian bug 973305 which was only helped by the second change, not the first one. Run /usr/lib/apt/planners < eipp.log and check there are no errors. TODO: It's unclear if the APT from proposed installed in the live session will fix the installer, needs investigation, but would make a useful test case. [Regression potential] It's imaginable that we missed something somewhere and some path that checked for a set error doesn't check it anymore, and we report success when we hit an error, but it seems unlikely. Behavior of --simulate changes. This used to fail before as well, and will now only produce a warning. We don't believe that is a reason of concern. [Groovy SRU] The groovy SRU is a sync of the 2.1.11 micro release from Debian unstable which also incorporates changes to the documentation: A typo fix, replacing focal with groovy in examples, and minor Dutch manual pages translation updates. We do not have test cases for the documentation changes, and we do not consider there to be a huge regression potential. As long as they build, they should be readable - maybe some words are wrong in the translation, who knows. [Original bug report] Test Case 1. Install Ubuntu Desktop on hardware with an nVidia card and select to install 3rd party drivers 2. Proceed with installation The following error message is displayed in /var/log/syslog /plugininstall.py: Verifying downloads ... /plugininstall.py: Failed to find package object for /cdrom//pool/main/g/gcc-defaults/gcc_9.3.0-1ubuntu2_amd64.deb: "Version: '9.3.0-1ubuntu2' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libxcrypt/libcrypt-dev_4.4.10-10ubuntu4_amd64.deb: "Version: '4.4.10-10ubuntu4' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/g/gcc-defaults/g++_9.3.0-1ubuntu2_amd64.deb: "Version: '9.3.0-1ubuntu2' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/z/zlib/zlib1g_1.2.11.dfsg-2ubuntu1_i386.deb: "Version: '1.2.11.dfsg-2ubuntu1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libxau/libxau6_1.0.9-0ubuntu1_i386.deb: "Version: '1.0.9-0ubuntu1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libxdmcp/libxdmcp6_1.1.3-0ubuntu1_i386.deb: "Version: '1.1.3-0ubuntu1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libx11/libx11-6_1.6.9-2ubuntu1_i386.deb: "Version: '1.6.9-2ubuntu1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libxext/libxext6_1.3.4-0ubuntu1_i386.deb: "Version: '1.3.4-0ubuntu1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/l/lm-sensors/libsensors5_3.6.0-2ubuntu1_i386.deb: "Version: '3.6.0-2ubuntu1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libx11/libx11-xcb1_1.6.9-2ubuntu1_i386.deb: "Version: '1.6.9-2ubuntu1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libxdamage/libxdamage1_1.1.5-1_i386.deb: "Version: '1.1.5-1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libxfixes/libxfixes3_5.0.3-1_i386.deb: "Version: '5.0.3-1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/
[Touch-packages] [Bug 1913763] Re: hyperv: unable to distinguish PTP devices
A similar rule has already been added upstream for KVM PTP device, see: https://github.com/systemd/systemd/pull/5495 -- 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/1913763 Title: hyperv: unable to distinguish PTP devices Status in systemd package in Ubuntu: New Bug description: Hyperv provides a PTP device. On system with multiple PTP devices, services like Chrony don't have a way to know which one is which. We would like to have a udev rule to create a symlink to the hyperv clock. This way, services could be configured to always use this clock no matter if it is ptp0, ptp1, etc.. For example: ``` SUBSYSTEM=="ptp", ATTR{clock_name}=="hyperv", SYMLINK += "ptp_hyperv" ``` To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1913763/+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 1913810] Re: restart doesn't test for syntax errors
** Changed in: openssh (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/1913810 Title: restart doesn't test for syntax errors Status in openssh package in Ubuntu: Confirmed Bug description: Tested openssh on bionic and groovy, same issue. The switch to systemd lost the ability to do a sanity check on the config file (via sshd -t) before attempting to restart sshd. This was originally bug #624361 in the SySV days, fixed in the initscript back then. The sysv script still does it, but it's not used anymore: restart) check_privsep_dir check_config log_daemon_msg "Restarting OpenBSD Secure Shell server" "sshd" || true And: check_config() { if [ ! -e /etc/ssh/sshd_not_to_be_run ]; then /usr/sbin/sshd $SSHD_OPTS -t || exit 1 fi } The systemd service file has only ExecStartPre, which doesn't let it start if there is an error, but will happily stop it: [Unit] Description=OpenBSD Secure Shell server After=network.target auditd.service ConditionPathExists=!/etc/ssh/sshd_not_to_be_run [Service] EnvironmentFile=-/etc/default/ssh ExecStartPre=/usr/sbin/sshd -t ExecStart=/usr/sbin/sshd -D $SSHD_OPTS ExecReload=/usr/sbin/sshd -t ExecReload=/bin/kill -HUP $MAINPID ... Example: # sshd -t # systemctl restart sshd # telnet localhost 22 Trying 127.0.0.1... Connected to localhost. Escape character is '^]'. SSH-2.0-OpenSSH_7.6p1 Ubuntu-4ubuntu0.3 ^] telnet> quit Connection closed. # echo "syntax error" >> /etc/ssh/sshd_config # sshd -t /etc/ssh/sshd_config: line 123: Bad configuration option: syntax /etc/ssh/sshd_config: terminating, 1 bad configuration options # systemctl restart sshd Job for ssh.service failed because the control process exited with error code. See "systemctl status ssh.service" and "journalctl -xe" for details. # telnet localhost 22 Trying 127.0.0.1... telnet: Unable to connect to remote host: Connection refused # To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1913810/+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 1871268] Re: Installation fails due to useless immediate configuration error when "Install Third-Party Drivers" is selected
** Changed in: ubuntu-cdimage Assignee: (unassigned) => Andrius KL (andrewdaman) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1871268 Title: Installation fails due to useless immediate configuration error when "Install Third-Party Drivers" is selected Status in Ubuntu CD Images: Fix Released Status in apt package in Ubuntu: Fix Released Status in apt source package in Bionic: In Progress Status in apt source package in Focal: Fix Released Status in apt source package in Groovy: Fix Released Status in apt package in Debian: Unknown Bug description: [Impact] Installations that really succeeded would then fail because APT could not immediately configure a package. Which is a pointless way to fail at that point, because everything did work out anyway. We have two changes that help address this: * The first one stops immediately configuring multi-arch siblings (e.g. libc6:i386 when it's configuring libc6:amd64). This was not necessary, and caused all the libc6:i386 failures here. * The second change sort of also supersedes the first one: It just ignores any errors from immediate configuration, relying on the fact that it's checked and rectified at a later point if there are unconfigured packages (which is what made all those failures happen spuriously after having successfully installed everything). [Test case] We have one test case in EIPP format in the Debian bug 973305 which was only helped by the second change, not the first one. Run /usr/lib/apt/planners < eipp.log and check there are no errors. TODO: It's unclear if the APT from proposed installed in the live session will fix the installer, needs investigation, but would make a useful test case. [Regression potential] It's imaginable that we missed something somewhere and some path that checked for a set error doesn't check it anymore, and we report success when we hit an error, but it seems unlikely. Behavior of --simulate changes. This used to fail before as well, and will now only produce a warning. We don't believe that is a reason of concern. [Groovy SRU] The groovy SRU is a sync of the 2.1.11 micro release from Debian unstable which also incorporates changes to the documentation: A typo fix, replacing focal with groovy in examples, and minor Dutch manual pages translation updates. We do not have test cases for the documentation changes, and we do not consider there to be a huge regression potential. As long as they build, they should be readable - maybe some words are wrong in the translation, who knows. [Original bug report] Test Case 1. Install Ubuntu Desktop on hardware with an nVidia card and select to install 3rd party drivers 2. Proceed with installation The following error message is displayed in /var/log/syslog /plugininstall.py: Verifying downloads ... /plugininstall.py: Failed to find package object for /cdrom//pool/main/g/gcc-defaults/gcc_9.3.0-1ubuntu2_amd64.deb: "Version: '9.3.0-1ubuntu2' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libxcrypt/libcrypt-dev_4.4.10-10ubuntu4_amd64.deb: "Version: '4.4.10-10ubuntu4' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/g/gcc-defaults/g++_9.3.0-1ubuntu2_amd64.deb: "Version: '9.3.0-1ubuntu2' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/z/zlib/zlib1g_1.2.11.dfsg-2ubuntu1_i386.deb: "Version: '1.2.11.dfsg-2ubuntu1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libxau/libxau6_1.0.9-0ubuntu1_i386.deb: "Version: '1.0.9-0ubuntu1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libxdmcp/libxdmcp6_1.1.3-0ubuntu1_i386.deb: "Version: '1.1.3-0ubuntu1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libx11/libx11-6_1.6.9-2ubuntu1_i386.deb: "Version: '1.6.9-2ubuntu1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libxext/libxext6_1.3.4-0ubuntu1_i386.deb: "Version: '1.3.4-0ubuntu1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/l/lm-sensors/libsensors5_3.6.0-2ubuntu1_i386.deb: "Version: '3.6.0-2ubuntu1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libx11/libx11-xcb1_1.6.9-2ubuntu1_i386.deb: "Version: '1.6.9-2ubuntu1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libxdamage/libxdamage1_1.1.5-1_i386.deb: "Version: '1.1.5-1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libxfixes/libxfixes3_5.0.3-1_i386.deb: "Version: '5.0.3-1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/
[Touch-packages] [Bug 1874381] Re: LVM device unavailable after 18.04 to 20.04 upgrade Timed out waiting for device /dev/mapper/s5lp8--v g-home
** Changed in: lvm2 (Ubuntu Focal) Milestone: ubuntu-20.04.2 => focal-updates -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lvm2 in Ubuntu. https://bugs.launchpad.net/bugs/1874381 Title: LVM device unavailable after 18.04 to 20.04 upgrade Timed out waiting for device /dev/mapper/s5lp8--v g-home Status in Ubuntu on IBM z Systems: Confirmed Status in lvm2 package in Ubuntu: Confirmed Status in lvm2 source package in Focal: Confirmed Bug description: After upgrading an LPAR configured with LVM from 18.04 to 20.04 /home is no longer mounted. During boot the console shows Timed out waiting for device /dev/mapper/s5lp8--vg-home Please see the attached dist-upgrade logs and console output for more detail. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1874381/+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 1914075] Re: subiquity 20.04.2 fails to install hwe kernel offline
** Changed in: ubuntu-meta (Ubuntu) Status: New => Fix Committed -- 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/1914075 Title: subiquity 20.04.2 fails to install hwe kernel offline Status in ubuntu-meta package in Ubuntu: Fix Committed Bug description: subiquity 20.04.2 fails to install hwe kernel offline as hwe kernel is missing from the pool To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1914075/+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 1914075] Re: subiquity 20.04.2 fails to install hwe kernel offline
** Merge proposal linked: https://code.launchpad.net/~xnox/ubuntu-seeds/+git/ubuntu-seeds/+merge/397277 -- 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/1914075 Title: subiquity 20.04.2 fails to install hwe kernel offline Status in ubuntu-meta package in Ubuntu: Fix Committed Bug description: subiquity 20.04.2 fails to install hwe kernel offline as hwe kernel is missing from the pool To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1914075/+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 1914075] [NEW] subiquity 20.04.2 fails to install hwe kernel offline
Public bug reported: subiquity 20.04.2 fails to install hwe kernel offline as hwe kernel is missing from the pool ** Affects: ubuntu-meta (Ubuntu) Importance: Undecided Status: Fix Committed ** Changed in: ubuntu-meta (Ubuntu) Milestone: None => ubuntu-20.04.2 -- 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/1914075 Title: subiquity 20.04.2 fails to install hwe kernel offline Status in ubuntu-meta package in Ubuntu: Fix Committed Bug description: subiquity 20.04.2 fails to install hwe kernel offline as hwe kernel is missing from the pool To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1914075/+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 1913859] Re: RT3290 Bluetooth not finding any device
** This bug is no longer a duplicate of bug 1914007 RT3290 Bluetooth not finding any device -- 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/1913859 Title: RT3290 Bluetooth not finding any device Status in bluez package in Ubuntu: Invalid Bug description: Ubuntu :- 20.04 Hello I have RT3290 bluetooth in built and it was not working so I installed its latest driver from github whose version is 3.9.6 . Now its working but its not discoverable to any other device and also not finding any other device. Outout of command :- service bluetooth status ● bluetooth.service - Bluetooth service Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled; vendor pre> Active: active (running) since Sat 2021-01-30 09:49:10 IST; 1h 0min ago Docs: man:bluetoothd(8) Main PID: 1389 (bluetoothd) Status: "Running" Tasks: 1 (limit: 4514) Memory: 2.0M CGroup: /system.slice/bluetooth.service └─1389 /usr/lib/bluetooth/bluetoothd Jan 30 09:49:07 Piyush-X55C systemd[1]: Starting Bluetooth service... Jan 30 09:49:10 Piyush-X55C bluetoothd[1389]: Bluetooth daemon 5.53 Jan 30 09:49:10 Piyush-X55C systemd[1]: Started Bluetooth service. Jan 30 09:49:10 Piyush-X55C bluetoothd[1389]: Starting SDP server Jan 30 09:49:10 Piyush-X55C bluetoothd[1389]: Bluetooth management interface 1.> Jan 30 10:49:34 Piyush-X55C bluetoothd[1389]: Endpoint registered: sender=:1.66> Jan 30 10:49:34 Piyush-X55C bluetoothd[1389]: Endpoint registered: sender=:1.66> lines 1-18/18 (END) Output of command :- sudo btmgmt info Index list with 1 item hci0: Primary controller addr A4:17:31:1D:65:54 version 4 manufacturer 91 class 0x00 supported settings: powered connectable fast-connectable discoverable bondable link-security ssp br/edr debug-keys current settings: powered bondable ssp br/edr name Piyush-X55C Output of command :- bluetoothctl Agent registered [bluetooth]# scan on [bluetooth]# discoverable on [bluetooth]# scan on Failed to start discovery: org.bluez.Error.InProgress [bluetooth]# discoverable on Changing discoverable on succeeded [bluetooth]# Output of command :- sudo btmgmt find Unable to start discovery. status 0x0c (Not Supported) Output of command :- lspci -knn | grep Net -A3; lsusb 02:00.0 Network controller [0280]: Ralink corp. RT3290 Wireless 802.11n 1T/1R PCIe [1814:3290] Subsystem: Foxconn International, Inc. RT3290 Wireless 802.11n 1T/1R PCIe [105b:e055] Kernel driver in use: rt2800pci Kernel modules: rt2800pci Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 003: ID 1bcf:2883 Sunplus Innovation Technology Inc. Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 003 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Output of command :-dmesg | grep -i bluetooth [ 12.851854] Bluetooth: Core ver 2.22 [ 12.851883] Bluetooth: HCI device and connection manager initialized [ 12.851888] Bluetooth: HCI socket layer initialized [ 12.851889] Bluetooth: L2CAP socket layer initialized [ 12.851893] Bluetooth: SCO socket layer initialized [ 67.399550] audit: type=1400 audit(1611909043.091:58): apparmor="DENIED" operation="create" profile="snap.bluez.bluez" pid=875 comm="bluetoothd" family="bluetooth" sock_type="raw" protocol=1 requested_mask="create" denied_mask="create" [ 67.727240] audit: type=1400 audit(1611909043.419:60): apparmor="DENIED" operation="connect" profile="snap.bluez.bluez" name="/run/dbus/system_bus_socket" pid=875 comm="bluetoothd" requested_mask="wr" denied_mask="wr" fsuid=0 ouid=0 [ 67.929889] audit: type=1400 audit(1611909043.619:62): apparmor="DENIED" operation="create" profile="snap.bluez.bluez" pid=1043 comm="bluetoothd" family="bluetooth" sock_type="raw" protocol=1 requested_mask="create" denied_mask="create" [ 67.930261] audit: type=1400 audit(1611909043.623:63): apparmor="DENIED" operation="connect" profile="snap.bluez.bluez" name="/run/dbus/system_bus_socket" pid=1043 comm="bluetoothd" requested_mask="wr" denied_mask="wr" fsuid=0 ouid=0 [ 68.194380] audit: type=1400 audit(1611909043.887:65): apparmor="DENIED" operation="create" profile="snap.bluez.bluez" pid=1102 comm="bluetoothd" family="bluetooth" sock_type="raw" protocol=1 requested_mask="create" denied_mask="create" [ 68.194710] audit: type=1400 audit(1611909043.887:66): apparmor="DENIED" operation="connect" profile=
[Touch-packages] [Bug 1913810] Re: restart doesn't test for syntax errors
** Tags added: server-next -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/1913810 Title: restart doesn't test for syntax errors Status in openssh package in Ubuntu: New Bug description: Tested openssh on bionic and groovy, same issue. The switch to systemd lost the ability to do a sanity check on the config file (via sshd -t) before attempting to restart sshd. This was originally bug #624361 in the SySV days, fixed in the initscript back then. The sysv script still does it, but it's not used anymore: restart) check_privsep_dir check_config log_daemon_msg "Restarting OpenBSD Secure Shell server" "sshd" || true And: check_config() { if [ ! -e /etc/ssh/sshd_not_to_be_run ]; then /usr/sbin/sshd $SSHD_OPTS -t || exit 1 fi } The systemd service file has only ExecStartPre, which doesn't let it start if there is an error, but will happily stop it: [Unit] Description=OpenBSD Secure Shell server After=network.target auditd.service ConditionPathExists=!/etc/ssh/sshd_not_to_be_run [Service] EnvironmentFile=-/etc/default/ssh ExecStartPre=/usr/sbin/sshd -t ExecStart=/usr/sbin/sshd -D $SSHD_OPTS ExecReload=/usr/sbin/sshd -t ExecReload=/bin/kill -HUP $MAINPID ... Example: # sshd -t # systemctl restart sshd # telnet localhost 22 Trying 127.0.0.1... Connected to localhost. Escape character is '^]'. SSH-2.0-OpenSSH_7.6p1 Ubuntu-4ubuntu0.3 ^] telnet> quit Connection closed. # echo "syntax error" >> /etc/ssh/sshd_config # sshd -t /etc/ssh/sshd_config: line 123: Bad configuration option: syntax /etc/ssh/sshd_config: terminating, 1 bad configuration options # systemctl restart sshd Job for ssh.service failed because the control process exited with error code. See "systemctl status ssh.service" and "journalctl -xe" for details. # telnet localhost 22 Trying 127.0.0.1... telnet: Unable to connect to remote host: Connection refused # To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1913810/+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 1913951] Re: ca-certificates: Symantec CA blacklisted for non-TLS uses
It looks like the reverted blacklist will work fine for new installs of groovy, so I'll be pushing a new version of the ca-certificates package tomorrow with an updated bundle that will solve this issue at the same time. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ca-certificates in Ubuntu. https://bugs.launchpad.net/bugs/1913951 Title: ca-certificates: Symantec CA blacklisted for non-TLS uses Status in ca-certificates package in Ubuntu: Fix Committed Status in ca-certificates source package in Groovy: Confirmed Status in ca-certificates source package in Hirsute: Fix Committed Status in ca-certificates package in Debian: Fix Committed Bug description: ~$ lsb_release -rd Description: Ubuntu 20.10 Release: 20.10 ~$ apt list --installed | grep ca-certificates WARNING: apt does not have a stable CLI interface. Use with caution in scripts. ca-certificates/groovy-updates,groovy-security,now 20201027ubuntu0.20.10.1 all [installed,automatic] Repro steps: 1. Open Terminal. 2. Execute: wget https://dot.net/v1/dotnet-install.sh chmod +x ./dotnet-install.sh ./dotnet-install.sh -c 5.0 export DOTNET_ROOT=$HOME/.dotnet export PATH=$PATH:$HOME/.dotnet dotnet new console dotnet add package System.Collections.Immutable Expected result: Package restore will succeed. Actual result: Package restore fails with: error: NU3028: Package 'System.Collections.Immutable 5.0.0' from source 'https://api.nuget.org/v3/index.json': The author primary signature's timestamp found a chain building issue: UntrustedRoot: self signed certificate in certificate chain There has been a planned process to distrust Symantec certificates in the certificate store over the past two years. The Debian ca-certificates package removed this CA for both TLS (expected) and other uses (like timestamping) (unexpected). Trust was added back in a subsequent update. See https://release.debian.org/proposed-updates/stable.html#ca-certificates_20200601~deb10u2 for details. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ca-certificates/+bug/1913951/+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 1913951] Re: ca-certificates: Symantec CA blacklisted for non-TLS uses
** Changed in: ca-certificates (Debian) Status: Unknown => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ca-certificates in Ubuntu. https://bugs.launchpad.net/bugs/1913951 Title: ca-certificates: Symantec CA blacklisted for non-TLS uses Status in ca-certificates package in Ubuntu: Fix Committed Status in ca-certificates source package in Groovy: Confirmed Status in ca-certificates source package in Hirsute: Fix Committed Status in ca-certificates package in Debian: Fix Committed Bug description: ~$ lsb_release -rd Description: Ubuntu 20.10 Release: 20.10 ~$ apt list --installed | grep ca-certificates WARNING: apt does not have a stable CLI interface. Use with caution in scripts. ca-certificates/groovy-updates,groovy-security,now 20201027ubuntu0.20.10.1 all [installed,automatic] Repro steps: 1. Open Terminal. 2. Execute: wget https://dot.net/v1/dotnet-install.sh chmod +x ./dotnet-install.sh ./dotnet-install.sh -c 5.0 export DOTNET_ROOT=$HOME/.dotnet export PATH=$PATH:$HOME/.dotnet dotnet new console dotnet add package System.Collections.Immutable Expected result: Package restore will succeed. Actual result: Package restore fails with: error: NU3028: Package 'System.Collections.Immutable 5.0.0' from source 'https://api.nuget.org/v3/index.json': The author primary signature's timestamp found a chain building issue: UntrustedRoot: self signed certificate in certificate chain There has been a planned process to distrust Symantec certificates in the certificate store over the past two years. The Debian ca-certificates package removed this CA for both TLS (expected) and other uses (like timestamping) (unexpected). Trust was added back in a subsequent update. See https://release.debian.org/proposed-updates/stable.html#ca-certificates_20200601~deb10u2 for details. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ca-certificates/+bug/1913951/+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 1914064] [NEW] ca-certificates update to 2.46 bundle
*** This bug is a security vulnerability *** Public security bug reported: Bug to track upgrading the ca-certificates package to the NSS 2.46 bundle. ** Affects: ca-certificates (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ca-certificates in Ubuntu. https://bugs.launchpad.net/bugs/1914064 Title: ca-certificates update to 2.46 bundle Status in ca-certificates package in Ubuntu: New Bug description: Bug to track upgrading the ca-certificates package to the NSS 2.46 bundle. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ca-certificates/+bug/1914064/+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 1912330] Re: non-X VTs should use energy star
** Summary changed: - ubuntu server not a good energy star citizen apparently + non-X VTs should use energy star ** Description changed: - Something like + it's simple. it's easy. let's get our servers being good energy star + citizens shall we? - setterm -powersave=powerdown -powerdown=15 -store + if a VT is running X at all, whether that's running sddm and never + logged in, or sddm and logged-in, or not running sddm and simply logged- + in and running X started with startx, that VT will timeout and + powerdown. so far so good. - ought to do it, probably right whenever/wherever a VT is activated. + but a VT that's either running getty, or logged in and just running + bash, will stay powered up and blazing away forever, whether it's ubuntu + server 20.04, lubuntu 20.04, or centos 8. - tho when i try that command i get + so probably RHEL 8 too, so probably most servers, aren't being good + energy star citizens! boo! - setterm: cannot (un)set powersave mode: Inappropriate ioctl for device + the util-linux package is used by both centos 8 and ubuntu 20.04, and + contains both getty and setterm. - is that the problem, something lacking in a device driver or whatever? + thus getty seems to me to be the sensible place to call: - or does the HP EliteDesk Pro 800 G1 SFF actually lack dpms energy star - features? seems dubious that it would. + setterm -powersave=powerdown -powerdown=15 -store - or is it just a case of finger pointing? ubuntu saying systemd should - do it, systemd saying getty should do it? - - whatever, i shouldn't walk up to a server terminal that's had nobody - there for hours and hours and see it's display still burning away, - right? + such that a VT running getty, or logged in and running bash, would then + timeout and powerdown. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: systemd 245.4-4ubuntu3.4 ProcVersionSignature: Ubuntu 5.4.0-62.70-generic 5.4.78 Uname: Linux 5.4.0-62-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 CasperMD5CheckResult: pass Date: Tue Jan 19 05:13:35 2021 InstallationDate: Installed on 2020-12-28 (21 days ago) InstallationMedia: Ubuntu-Server 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: Hewlett-Packard HP EliteDesk 800 G1 SFF ProcEnviron: - TERM=screen - PATH=(custom, no user) - LANG=C.UTF-8 - SHELL=/bin/bash + TERM=screen + PATH=(custom, no user) + LANG=C.UTF-8 + SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/fs/boot/vmlinuz ro root=UUID=a671d866-a05f-4b83-8714-0b448b1eeac4 subroot=/fs init=/fs/etc/g/subroot SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/15/2014 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: L01 v02.33 dmi.board.name: 1998 dmi.board.vendor: Hewlett-Packard dmi.chassis.type: 4 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvrL01v02.33:bd07/15/2014:svnHewlett-Packard:pnHPEliteDesk800G1SFF:pvr:rvnHewlett-Packard:rn1998:rvr:cvnHewlett-Packard:ct4:cvr: dmi.product.family: 103C_53307F G=D dmi.product.name: HP EliteDesk 800 G1 SFF dmi.product.sku: J6D79UT#ABA dmi.sys.vendor: Hewlett-Packard ** Package changed: systemd (Ubuntu) => util-linux (Ubuntu) -- 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/1912330 Title: non-X VTs should use energy star Status in util-linux package in Ubuntu: New Bug description: it's simple. it's easy. let's get our servers being good energy star citizens shall we? if a VT is running X at all, whether that's running sddm and never logged in, or sddm and logged-in, or not running sddm and simply logged-in and running X started with startx, that VT will timeout and powerdown. so far so good. but a VT that's either running getty, or logged in and just running bash, will stay powered up and blazing away forever, whether it's ubuntu server 20.04, lubuntu 20.04, or centos 8. so probably RHEL 8 too, so probably most servers, aren't being good energy star citizens! boo! the util-linux package is used by both centos 8 and ubuntu 20.04, and contains both getty and setterm. thus getty seems to me to be the sensible place to call: setterm -powersave=powerdown -powerdown=15 -store such that a VT running getty, or logged in and running bash, would then timeout and powerdown. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: systemd 245.4-4ubuntu3.4 ProcVersionSignature: Ubuntu 5.4.0-62.70-generic 5.4.78 Uname: Linux 5.4.0-62-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 CasperMD5CheckResult: pass Date: Tue Jan 19 05:13:35 2021 InstallationDate: Installed on 2020-12-28 (21 days ago) InstallationMedia: Ubuntu-Server 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) Machine
[Touch-packages] [Bug 1914062] [NEW] NetworkManager-wait-online.service in 1.28.0-2ubuntu1 fails to start in LXC
Public bug reported: This regresses systemd's autopkgtest because it expects the system in the container to reach running state, but the system ends up in degraded state due to the service failing. https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-hirsute/hirsute/amd64/s/systemd/20210112_185712_ff570@/log.gz ... == FAIL: test_no_failed (__main__.ServicesTest) No failed units -- Traceback (most recent call last): File "/tmp/autopkgtest.fFC3Lw/build.xLc/real-tree/debian/tests/boot-and-services", line 68, in test_no_failed self.assertEqual(failed, []) AssertionError: Lists differ: ['● NetworkManager-wait-online.service loa[42 chars]ine'] != [] First list contains 1 additional elements. First extra element 0: '● NetworkManager-wait-online.service loaded failed failed Network Manager Wait Online' + [] - ['● NetworkManager-wait-online.service loaded failed failed Network Manager ' - 'Wait Online'] -- Ran 23 tests in 4.435s ... Reproducible locally by installing n-m from -proposed, then restarting the system in the LXC container. ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New ** Tags: update-excuse -- 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/1914062 Title: NetworkManager-wait-online.service in 1.28.0-2ubuntu1 fails to start in LXC Status in network-manager package in Ubuntu: New Bug description: This regresses systemd's autopkgtest because it expects the system in the container to reach running state, but the system ends up in degraded state due to the service failing. https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-hirsute/hirsute/amd64/s/systemd/20210112_185712_ff570@/log.gz ... == FAIL: test_no_failed (__main__.ServicesTest) No failed units -- Traceback (most recent call last): File "/tmp/autopkgtest.fFC3Lw/build.xLc/real-tree/debian/tests/boot-and-services", line 68, in test_no_failed self.assertEqual(failed, []) AssertionError: Lists differ: ['● NetworkManager-wait-online.service loa[42 chars]ine'] != [] First list contains 1 additional elements. First extra element 0: '● NetworkManager-wait-online.service loaded failed failed Network Manager Wait Online' + [] - ['● NetworkManager-wait-online.service loaded failed failed Network Manager ' - 'Wait Online'] -- Ran 23 tests in 4.435s ... Reproducible locally by installing n-m from -proposed, then restarting the system in the LXC container. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1914062/+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 1913951] Re: ca-certificates: Symantec CA blacklisted for non-TLS uses
Version 20210119 in hirsute-proposed fixes this issue. The Symantec certs were never blacklisted in focal and earlier, so they aren't affected. This issue does affect Groovy, but even if we removed the blacklist from the ca-certificates package, the certs will still be blacklisted because of debian bug #743339. We need to investigate how to remove the blacklist in a maintainer script on package upgrade. ** Bug watch added: Debian Bug tracker #962596 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=962596 ** Also affects: ca-certificates (Debian) via https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=962596 Importance: Unknown Status: Unknown ** Also affects: ca-certificates (Ubuntu Hirsute) Importance: Undecided Status: Confirmed ** Also affects: ca-certificates (Ubuntu Groovy) Importance: Undecided Status: New ** Changed in: ca-certificates (Ubuntu Groovy) Status: New => Confirmed ** Changed in: ca-certificates (Ubuntu Hirsute) Status: Confirmed => Fix Committed ** Changed in: ca-certificates (Ubuntu Groovy) Assignee: (unassigned) => Marc Deslauriers (mdeslaur) ** Changed in: ca-certificates (Ubuntu Groovy) Importance: Undecided => High -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ca-certificates in Ubuntu. https://bugs.launchpad.net/bugs/1913951 Title: ca-certificates: Symantec CA blacklisted for non-TLS uses Status in ca-certificates package in Ubuntu: Fix Committed Status in ca-certificates source package in Groovy: Confirmed Status in ca-certificates source package in Hirsute: Fix Committed Status in ca-certificates package in Debian: Unknown Bug description: ~$ lsb_release -rd Description: Ubuntu 20.10 Release: 20.10 ~$ apt list --installed | grep ca-certificates WARNING: apt does not have a stable CLI interface. Use with caution in scripts. ca-certificates/groovy-updates,groovy-security,now 20201027ubuntu0.20.10.1 all [installed,automatic] Repro steps: 1. Open Terminal. 2. Execute: wget https://dot.net/v1/dotnet-install.sh chmod +x ./dotnet-install.sh ./dotnet-install.sh -c 5.0 export DOTNET_ROOT=$HOME/.dotnet export PATH=$PATH:$HOME/.dotnet dotnet new console dotnet add package System.Collections.Immutable Expected result: Package restore will succeed. Actual result: Package restore fails with: error: NU3028: Package 'System.Collections.Immutable 5.0.0' from source 'https://api.nuget.org/v3/index.json': The author primary signature's timestamp found a chain building issue: UntrustedRoot: self signed certificate in certificate chain There has been a planned process to distrust Symantec certificates in the certificate store over the past two years. The Debian ca-certificates package removed this CA for both TLS (expected) and other uses (like timestamping) (unexpected). Trust was added back in a subsequent update. See https://release.debian.org/proposed-updates/stable.html#ca-certificates_20200601~deb10u2 for details. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ca-certificates/+bug/1913951/+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 1914056] [NEW] package procps 2:3.3.10-4ubuntu2 [modified: usr/bin/free usr/bin/pgrep usr/bin/pwdx usr/bin/skill usr/bin/slabtop usr/bin/tload usr/bin/top usr/bin/uptime usr/bin/
Public bug reported: dpkg: erreur de traitement du paquet procps (--configure) : le paquet procps n'est pas prêt pour la configuration configuration impossible (état actuel « half-installed ») dpkg: des problèmes de dépendances empêchent la configuration de udev : udev dépend de procps ; cependant : Le paquet procps n'est pas installé. dpkg: erreur de traitement du paquet udev (--configure) : problèmes de dépendances - laissé non configuré dpkg: des problèmes de dépendances empêchent la configuration de bluez : bluez dépend de udev (>= 170-1) ; cependant : Le paquet udev n'est pas encore configuré. dpkg: erreur de traitement du paquet bluez (--configure) : problèmes de dépendances - laissé non configuré dpkg: des problèmes de dépendances empêchent la configuration de cups-daemon : cups-daemon dépend de procps ; cependant : Le paquet procps n'est pas installé. dpkg: erreur de traitement du paquet cups-daemon (--configure) : problèmes de dépendances - laissé non configuré dpkg: des problèmes de dépendances empêchent la configuration de initramfs-tools-core : initramfs-tools-core dépend de udev ; cependant : Le paquet udAucun rapport « apport » n'a été créé car le message d'erreur indique une erreur consécutive à un échec précédent. Aucun rapport « apport » n'a été créé car le message d'erreur indique une erreur consécutive à un échec précédent. Aucun rapport « apport » écrit car MaxReports a déjà été atteint Aucun rapport « apport » écrit car MaxReports a déjà été atteint Aucun rapport « apport » écrit car MaxReports a déjà été atteint Aucun rapport « apport » écrit car MaxReports a déjà été atteint ev n'est pas encore configuré. dpkg: erreur de traitement du paquet initramfs-tools-core (--configure) : problèmes de dépendances - laissé non configuré dpkg: des problèmes de dépendances empêchent la configuration de initramfs-tools : initramfs-tools dépend de initramfs-tools-core (= 0.122ubuntu8.17) ; cependant : Le paquet initramfs-tools-core n'est pas encore configuré. dpkg: erreur de traitement du paquet initramfs-tools (--configure) : problèmes de dépendances - laissé non configuré dpkg: des problèmes de dépendances empêchent la configuration de cups-core-drivers : cups-core-drivers dépend de cups-daemon (>= 2.1.3-4ubuntu0.11) ; cependant : Le paquet cups-daemon n'est pas encore configuré. dpkg: erreur de traitement du paquet cups-core-drivers (--configure) : problèmes de dépendances - laissé non configuré dpkg: des problèmes de dépendances empêchent la configuration de cups : cups dépend de cups-core-drivers (>= 2.1.3-4ubuntu0.11) ; cepeAucun rapport « apport » écrit car MaxReports a déjà été atteint Aucun rapport « apport » écrit car MaxReports a déjà été atteint ndant : Le paquet cups-core-drivers n'est pas encore configuré. cups dépend de cups-daemon (>= 2.1.3-4ubuntu0.11) ; cependant : Le paquet cups-daemon n'est pas encore configuré. cups dépend de procps ; cependant : Le paquet procps n'est pas installé. dpkg: erreur de traitement du paquet cups (--configure) : problèmes de dépendances - laissé non configuré dpkg: des problèmes de dépendances empêchent la configuration de xserver-xorg-core : xserver-xorg-core dépend de udev (>= 149) ; cependant : Le paquet udev n'est pas encore configuré. dpkg: erreur de traitement du paquet xserver-xorg-core (--configure) : problèmes de dépendances - laissé non configuré Des erreurs ont été rencontrées pendant l'exécution : procps udev bluez cups-daemon initramfs-tools-core initramfs-tools cups-core-drivers cups xserver-xorg-core E: Sub-process /usr/bin/dpkg returned an error code (1) ProblemType: Package DistroRelease: Ubuntu 16.04 Package: procps 2:3.3.10-4ubuntu2 [modified: usr/bin/free usr/bin/pgrep usr/bin/pwdx usr/bin/skill usr/bin/slabtop usr/bin/tload usr/bin/top usr/bin/uptime usr/bin/vmstat usr/bin/watch] ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13 Uname: Linux 4.4.0-31-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 Date: Mon Feb 1 14:49:19 2021 ErrorMessage: le paquet procps n'est pas prêt pour la configuration configuration impossible (état actuel « half-installed ») InstallationDate: Installed on 2021-01-28 (3 days ago) InstallationMedia: Ub
[Touch-packages] [Bug 1914053] [NEW] US intl. Deadkeys not working in some programs
Public bug reported: Kubuntu 20.04 KDE Plasma 5.18.5 KDE Frameworks Version: 5.68.0 Qt Version: 5.12.8 xorg: Installed: 1:7.7+19ubuntu14 Candidate: 1:7.7+19ubuntu14 Version table: *** 1:7.7+19ubuntu14 500 500 http://no.archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status The keyboard layout is set as English (US, intl., with dead keys) to deal with European lettering. This worked fine for a long time, but suddenly, the dead keys are not working in several programs. As in, when typing the dead key nothing happens. E.g. they don't work in browsers (checked in Firefox and Chrome) and in the Matrix Element program. However, they do work in other programs, such as Kate and LibreOffice. Normally one can type an apostrophe (') by hitting that key and typing a space, but now the only way to get that character in those few programs is by pressing Alt Gr+' . The same thing for letters like é. Normally pressing '+e would work, now only Alt Gr+e works. Apport bug report (aka ubuntu-bug xorg) did not work for the xorg package. ** Affects: xorg (Ubuntu) Importance: Undecided Status: New -- 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/1914053 Title: US intl. Deadkeys not working in some programs Status in xorg package in Ubuntu: New Bug description: Kubuntu 20.04 KDE Plasma 5.18.5 KDE Frameworks Version: 5.68.0 Qt Version: 5.12.8 xorg: Installed: 1:7.7+19ubuntu14 Candidate: 1:7.7+19ubuntu14 Version table: *** 1:7.7+19ubuntu14 500 500 http://no.archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status The keyboard layout is set as English (US, intl., with dead keys) to deal with European lettering. This worked fine for a long time, but suddenly, the dead keys are not working in several programs. As in, when typing the dead key nothing happens. E.g. they don't work in browsers (checked in Firefox and Chrome) and in the Matrix Element program. However, they do work in other programs, such as Kate and LibreOffice. Normally one can type an apostrophe (') by hitting that key and typing a space, but now the only way to get that character in those few programs is by pressing Alt Gr+' . The same thing for letters like é. Normally pressing '+e would work, now only Alt Gr+e works. Apport bug report (aka ubuntu-bug xorg) did not work for the xorg package. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1914053/+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 1911614] Re: Ubuntu 20.04 and 20.04.1 images use linux-generic-hwe-20.04 instead of linux-generic
Also release team posted this update https://discourse.ubuntu.com/t /improvements-for-hardware-support-in-ubuntu-desktop-installation- media/20606 about this issue, which they were forced to do before the weekend instead of during normal working hours this week. They were hoping to collect more evidence before posting, however another statement pushed out without coordination with the tech-board forced the release team to publish incomplete statement. -- 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/1911614 Title: Ubuntu 20.04 and 20.04.1 images use linux-generic-hwe-20.04 instead of linux-generic Status in ubuntu-meta package in Ubuntu: Confirmed Bug description: Beginning about January 8th Focal users that installed Focal using either the Ubuntu 20.04 or 20.04.1 installation media began getting updated to the 5.8 series linux kernel. Those who had installed using the Ubuntu Focal Beta were not effected. This is because Focal Beta was properly built with ‘linux-generic’ but the 20.04 and 20.04.1 images were built with ‘linux-generic-hwe-20.04‘. This can be easily verified by looking at the iso manifest: https://releases.ubuntu.com/20.04.1/ubuntu-20.04.1-desktop- amd64.manifest Note: old-release manifests (where 20.04 Beta and 20.04 reside) must be downloaded here: https://old-releases.ubuntu.com/releases/20.04/ The expected behavior is for Ubuntu Focal users to remain on the 5.4 series kernel unless they install with 20.04.2 or later images as indicated here: https://wiki.ubuntu.com/Kernel/LTSEnablementStack While not entirely updated it says “if one wants to remain on the original GA (General Availability) stacks, the options [include]; Install from a previous 12.04.0/12.04.1/14.04.0/14.04.1/16.04.0/16.04.1/18.04.0/18.04.1 point release and update”. Jump just below that to the Focal specific notes and it says “The 20.04.2 and newer point releases will ship with an updated kernel and X stack by default for the desktop”. Since 20.04.2 is not even due for release until next month it makes no sense for updates to the 5.8 series kernel to be occurring unless the focal-proposed repos are enabled even if HWE protocols had been changed. It’s also worth noting that thankfully no accompanying HWE X stack is yet available in the repos. I say thankfully because my efforts at downgrading the X stack in 16.04 and 18.04 were never successful! But the lack of a matching X stack may explain the many complaints on the forums about broken graphics??? It’s also worth noting that even the release notes say that “Ubuntu 20.04 LTS is based on the long-term supported Linux release series 5.4“. https://wiki.ubuntu.com/FocalFossa/ReleaseNotes#Linux_Kernel Scroll to the bottom here and you’ll also see that 20.04 and 20.04.1 are supposed to be supported with the 5.4 series kernel for the entire 5 year life span: https://ubuntu.com/kernel/lifecycle The other flavors’ 20.04 and 20.04.1 images were all built correctly with ‘linux-generic’ with the possible exception of Ubuntu Studio which uses a kernel stack I’m not familiar with. I’m also uncertain about Ubuntu server because I’m simply not familiar with it. Original bug description below: ## Just as the title says, the 20.04 and 20.04.1 images use the HWE version of linux-generic resulting in upgrades to the 5.8 series kernel. This seems to effect Ubuntu only, or I should say I checked the Kubuntu, Ubuntu Mate, Xubuntu, and Lubuntu iso manifests which all correctly list linux-generic. Also HWE is not truly complete without the accompanying HWE Xstack. I checked all the documentation I could find and this was clearly not intentional. In fact the manifest for Ubuntu Focal Beta still used linux-generic, so this got messed up some time between April 3, 2020 and April 23, 2020. Here's just one example of the documentation for kernel support in Focal LTS: https://ubuntu.com/about/release-cycle#ubuntu-kernel-release-cycle Installations performed with 20.04 and 20.04.1 media were supposed to remain on the 5.4 series kernel throughout Focal's 5 year lifespan as had been the case since HWE was introduced. The first step in fixing this needs to be stopping fresh installs of Focal using the 20.04 and 20.04.1 media from immediately upgrading to the 5.8 series kernel. It might be a little tricky to revert users from 5.8 to 5.4, but there have been reports of breakage, particularly concerning Broadcom wifi drivers and some graphics problems. But the graphics problems could also be exacerbated by the lack of the matching HWE Xstack? At any rate it's a bug. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubunt
[Touch-packages] [Bug 1911614] Re: Ubuntu 20.04 and 20.04.1 images use linux-generic-hwe-20.04 instead of linux-generic
@michel.ekimia https://bugs.launchpad.net/ubuntu/+source/virtualbox/+bug/1901904 has full support for the v5.8 kernel in focal, released on 18th of January 2021. What package versions are you referring to? for which release? and which archive origin? And which combinations of the hypervisor/guests? -- 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/1911614 Title: Ubuntu 20.04 and 20.04.1 images use linux-generic-hwe-20.04 instead of linux-generic Status in ubuntu-meta package in Ubuntu: Confirmed Bug description: Beginning about January 8th Focal users that installed Focal using either the Ubuntu 20.04 or 20.04.1 installation media began getting updated to the 5.8 series linux kernel. Those who had installed using the Ubuntu Focal Beta were not effected. This is because Focal Beta was properly built with ‘linux-generic’ but the 20.04 and 20.04.1 images were built with ‘linux-generic-hwe-20.04‘. This can be easily verified by looking at the iso manifest: https://releases.ubuntu.com/20.04.1/ubuntu-20.04.1-desktop- amd64.manifest Note: old-release manifests (where 20.04 Beta and 20.04 reside) must be downloaded here: https://old-releases.ubuntu.com/releases/20.04/ The expected behavior is for Ubuntu Focal users to remain on the 5.4 series kernel unless they install with 20.04.2 or later images as indicated here: https://wiki.ubuntu.com/Kernel/LTSEnablementStack While not entirely updated it says “if one wants to remain on the original GA (General Availability) stacks, the options [include]; Install from a previous 12.04.0/12.04.1/14.04.0/14.04.1/16.04.0/16.04.1/18.04.0/18.04.1 point release and update”. Jump just below that to the Focal specific notes and it says “The 20.04.2 and newer point releases will ship with an updated kernel and X stack by default for the desktop”. Since 20.04.2 is not even due for release until next month it makes no sense for updates to the 5.8 series kernel to be occurring unless the focal-proposed repos are enabled even if HWE protocols had been changed. It’s also worth noting that thankfully no accompanying HWE X stack is yet available in the repos. I say thankfully because my efforts at downgrading the X stack in 16.04 and 18.04 were never successful! But the lack of a matching X stack may explain the many complaints on the forums about broken graphics??? It’s also worth noting that even the release notes say that “Ubuntu 20.04 LTS is based on the long-term supported Linux release series 5.4“. https://wiki.ubuntu.com/FocalFossa/ReleaseNotes#Linux_Kernel Scroll to the bottom here and you’ll also see that 20.04 and 20.04.1 are supposed to be supported with the 5.4 series kernel for the entire 5 year life span: https://ubuntu.com/kernel/lifecycle The other flavors’ 20.04 and 20.04.1 images were all built correctly with ‘linux-generic’ with the possible exception of Ubuntu Studio which uses a kernel stack I’m not familiar with. I’m also uncertain about Ubuntu server because I’m simply not familiar with it. Original bug description below: ## Just as the title says, the 20.04 and 20.04.1 images use the HWE version of linux-generic resulting in upgrades to the 5.8 series kernel. This seems to effect Ubuntu only, or I should say I checked the Kubuntu, Ubuntu Mate, Xubuntu, and Lubuntu iso manifests which all correctly list linux-generic. Also HWE is not truly complete without the accompanying HWE Xstack. I checked all the documentation I could find and this was clearly not intentional. In fact the manifest for Ubuntu Focal Beta still used linux-generic, so this got messed up some time between April 3, 2020 and April 23, 2020. Here's just one example of the documentation for kernel support in Focal LTS: https://ubuntu.com/about/release-cycle#ubuntu-kernel-release-cycle Installations performed with 20.04 and 20.04.1 media were supposed to remain on the 5.4 series kernel throughout Focal's 5 year lifespan as had been the case since HWE was introduced. The first step in fixing this needs to be stopping fresh installs of Focal using the 20.04 and 20.04.1 media from immediately upgrading to the 5.8 series kernel. It might be a little tricky to revert users from 5.8 to 5.4, but there have been reports of breakage, particularly concerning Broadcom wifi drivers and some graphics problems. But the graphics problems could also be exacerbated by the lack of the matching HWE Xstack? At any rate it's a bug. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1911614/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe :
[Touch-packages] [Bug 1911614] Re: Ubuntu 20.04 and 20.04.1 images use linux-generic-hwe-20.04 instead of linux-generic
https://wiki.ubuntu.com/Kernel/LTSEnablementStack was updated with expanded instructions around 20.04 LTS, and make it more obvious that one is most likely tracking HWE kernel on Desktop; unless one is on the OEM kernel. Note that on certified hardware downgrades to GA stack may cause loss of functionality. References from LTSEnablementStack to RollingLTSEnablementStack, have been clarified that rollingness of the hwe stacks is same as it was since 16.04. It used to be the case that one could install Quantal/Raring/Saucy hwe kernels and keep them until Trusty hwe comes out. However since 16.04, we have been rolling hwe stacks, such that the three intermediate kernel series roll over. ubuntu.com/kernel/lifecycle update is in progress and is tracked at https://github.com/canonical-web-and-design/ubuntu.com/issues/9101 ** Bug watch added: github.com/canonical-web-and-design/ubuntu.com/issues #9101 https://github.com/canonical-web-and-design/ubuntu.com/issues/9101 -- 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/1911614 Title: Ubuntu 20.04 and 20.04.1 images use linux-generic-hwe-20.04 instead of linux-generic Status in ubuntu-meta package in Ubuntu: Confirmed Bug description: Beginning about January 8th Focal users that installed Focal using either the Ubuntu 20.04 or 20.04.1 installation media began getting updated to the 5.8 series linux kernel. Those who had installed using the Ubuntu Focal Beta were not effected. This is because Focal Beta was properly built with ‘linux-generic’ but the 20.04 and 20.04.1 images were built with ‘linux-generic-hwe-20.04‘. This can be easily verified by looking at the iso manifest: https://releases.ubuntu.com/20.04.1/ubuntu-20.04.1-desktop- amd64.manifest Note: old-release manifests (where 20.04 Beta and 20.04 reside) must be downloaded here: https://old-releases.ubuntu.com/releases/20.04/ The expected behavior is for Ubuntu Focal users to remain on the 5.4 series kernel unless they install with 20.04.2 or later images as indicated here: https://wiki.ubuntu.com/Kernel/LTSEnablementStack While not entirely updated it says “if one wants to remain on the original GA (General Availability) stacks, the options [include]; Install from a previous 12.04.0/12.04.1/14.04.0/14.04.1/16.04.0/16.04.1/18.04.0/18.04.1 point release and update”. Jump just below that to the Focal specific notes and it says “The 20.04.2 and newer point releases will ship with an updated kernel and X stack by default for the desktop”. Since 20.04.2 is not even due for release until next month it makes no sense for updates to the 5.8 series kernel to be occurring unless the focal-proposed repos are enabled even if HWE protocols had been changed. It’s also worth noting that thankfully no accompanying HWE X stack is yet available in the repos. I say thankfully because my efforts at downgrading the X stack in 16.04 and 18.04 were never successful! But the lack of a matching X stack may explain the many complaints on the forums about broken graphics??? It’s also worth noting that even the release notes say that “Ubuntu 20.04 LTS is based on the long-term supported Linux release series 5.4“. https://wiki.ubuntu.com/FocalFossa/ReleaseNotes#Linux_Kernel Scroll to the bottom here and you’ll also see that 20.04 and 20.04.1 are supposed to be supported with the 5.4 series kernel for the entire 5 year life span: https://ubuntu.com/kernel/lifecycle The other flavors’ 20.04 and 20.04.1 images were all built correctly with ‘linux-generic’ with the possible exception of Ubuntu Studio which uses a kernel stack I’m not familiar with. I’m also uncertain about Ubuntu server because I’m simply not familiar with it. Original bug description below: ## Just as the title says, the 20.04 and 20.04.1 images use the HWE version of linux-generic resulting in upgrades to the 5.8 series kernel. This seems to effect Ubuntu only, or I should say I checked the Kubuntu, Ubuntu Mate, Xubuntu, and Lubuntu iso manifests which all correctly list linux-generic. Also HWE is not truly complete without the accompanying HWE Xstack. I checked all the documentation I could find and this was clearly not intentional. In fact the manifest for Ubuntu Focal Beta still used linux-generic, so this got messed up some time between April 3, 2020 and April 23, 2020. Here's just one example of the documentation for kernel support in Focal LTS: https://ubuntu.com/about/release-cycle#ubuntu-kernel-release-cycle Installations performed with 20.04 and 20.04.1 media were supposed to remain on the 5.4 series kernel throughout Focal's 5 year lifespan as had been the case since HWE was introduced. The first step in fixing this needs
[Touch-packages] [Bug 1848626] Re: When seeking in VLC playing most videos, sound is choppy for 9s after seek.
Enabling "Quick search" in Settings -> Input / Codecs (checkbox) seems to fix this issue. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1848626 Title: When seeking in VLC playing most videos, sound is choppy for 9s after seek. Status in alsa-driver package in Ubuntu: Confirmed Bug description: System was working fine in Ubuntu 19.04. After update to 19.10 and reboot, videos have audio problems after seeking. The majority of videos I tested had trouble, but the severity of the problem varies even in the problem videos. The sound cuts in and out inconsistently, as if some software is having trouble filling the audio buffer in time. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1 Uname: Linux 5.3.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: x 1708 F pulseaudio /dev/snd/controlC0: x 1708 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Thu Oct 17 21:07:33 2019 InstallationDate: Installed on 2018-12-09 (313 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Generic successful Symptom_Card: Family 17h (Models 00h-0fh) HD Audio Controller - HD-Audio Generic Symptom_Jack: Black SPDIF Out, Rear Symptom_PulsePlaybackTest: PulseAudio playback test failed Symptom_Type: None of the above Title: [To Be Filled By O.E.M., Realtek ALC1220, Black SPDIF Out, Rear] Playback problem UpgradeStatus: Upgraded to eoan on 2019-10-17 (0 days ago) dmi.bios.date: 04/01/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P3.20 dmi.board.name: B450 Gaming-ITX/ac dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP3.20:bd04/01/2019:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnB450Gaming-ITX/ac:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1848626/+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 1913951] Re: ca-certificates: Symantec CA blacklisted for non-TLS uses
You can find every details about the Nuget incident here: https://github.com/NuGet/Announcements/issues/49#issue-795386700 ** Bug watch added: github.com/NuGet/Announcements/issues #49 https://github.com/NuGet/Announcements/issues/49 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ca-certificates in Ubuntu. https://bugs.launchpad.net/bugs/1913951 Title: ca-certificates: Symantec CA blacklisted for non-TLS uses Status in ca-certificates package in Ubuntu: Confirmed Bug description: ~$ lsb_release -rd Description: Ubuntu 20.10 Release: 20.10 ~$ apt list --installed | grep ca-certificates WARNING: apt does not have a stable CLI interface. Use with caution in scripts. ca-certificates/groovy-updates,groovy-security,now 20201027ubuntu0.20.10.1 all [installed,automatic] Repro steps: 1. Open Terminal. 2. Execute: wget https://dot.net/v1/dotnet-install.sh chmod +x ./dotnet-install.sh ./dotnet-install.sh -c 5.0 export DOTNET_ROOT=$HOME/.dotnet export PATH=$PATH:$HOME/.dotnet dotnet new console dotnet add package System.Collections.Immutable Expected result: Package restore will succeed. Actual result: Package restore fails with: error: NU3028: Package 'System.Collections.Immutable 5.0.0' from source 'https://api.nuget.org/v3/index.json': The author primary signature's timestamp found a chain building issue: UntrustedRoot: self signed certificate in certificate chain There has been a planned process to distrust Symantec certificates in the certificate store over the past two years. The Debian ca-certificates package removed this CA for both TLS (expected) and other uses (like timestamping) (unexpected). Trust was added back in a subsequent update. See https://release.debian.org/proposed-updates/stable.html#ca-certificates_20200601~deb10u2 for details. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ca-certificates/+bug/1913951/+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 1913951] Re: ca-certificates: Symantec CA blacklisted for non-TLS uses
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: ca-certificates (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ca-certificates in Ubuntu. https://bugs.launchpad.net/bugs/1913951 Title: ca-certificates: Symantec CA blacklisted for non-TLS uses Status in ca-certificates package in Ubuntu: Confirmed Bug description: ~$ lsb_release -rd Description: Ubuntu 20.10 Release: 20.10 ~$ apt list --installed | grep ca-certificates WARNING: apt does not have a stable CLI interface. Use with caution in scripts. ca-certificates/groovy-updates,groovy-security,now 20201027ubuntu0.20.10.1 all [installed,automatic] Repro steps: 1. Open Terminal. 2. Execute: wget https://dot.net/v1/dotnet-install.sh chmod +x ./dotnet-install.sh ./dotnet-install.sh -c 5.0 export DOTNET_ROOT=$HOME/.dotnet export PATH=$PATH:$HOME/.dotnet dotnet new console dotnet add package System.Collections.Immutable Expected result: Package restore will succeed. Actual result: Package restore fails with: error: NU3028: Package 'System.Collections.Immutable 5.0.0' from source 'https://api.nuget.org/v3/index.json': The author primary signature's timestamp found a chain building issue: UntrustedRoot: self signed certificate in certificate chain There has been a planned process to distrust Symantec certificates in the certificate store over the past two years. The Debian ca-certificates package removed this CA for both TLS (expected) and other uses (like timestamping) (unexpected). Trust was added back in a subsequent update. See https://release.debian.org/proposed-updates/stable.html#ca-certificates_20200601~deb10u2 for details. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ca-certificates/+bug/1913951/+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 1911030] Re: Graphical flashes on a raspi 4
Daniel - FYI - I raised the issue of the dtoverlay vc4-kms-v3d vs vc4 -kms-v3d-pi4. TL;DR - the v3d overlay is not activating the accelerated driver. Upstream confirmed this is an issue with Ubuntu's kernel - I'm hoping this will be caught and resolved in an upcoming raspi kernel update. https://github.com/raspberrypi/linux/issues/4080#issuecomment-762709027 Looking forward to testing the v5.10 raspi kernel whenever that is pushed into proposed ** Bug watch added: github.com/raspberrypi/linux/issues #4080 https://github.com/raspberrypi/linux/issues/4080 -- 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/1911030 Title: Graphical flashes on a raspi 4 Status in mesa package in Ubuntu: New Status in xorg-server package in Ubuntu: New Bug description: Using gnome-shell - activities - see attached video Graphics flash - more prominent with more than one app running. If you install ubuntu-budgie-desktop and simply move through the menu categories the flashing is even more prominent. I'm guessing this is xorg related - but I do note the recent mesa uplift has made things worse ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: xorg 1:7.7+19ubuntu15 ProcVersionSignature: Ubuntu 5.8.0-1011.14+21.04.1-raspi 5.8.18 Uname: Linux 5.8.0-1011-raspi aarch64 ApportVersion: 2.20.11-0ubuntu55 Architecture: arm64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Jan 11 16:49:14 2021 DistUpgraded: Fresh install DistroCodename: hirsute DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: ImageMediaBuild: 20201225 Lspci-vt: -[:00]---00.0-[01]00.0 VIA Technologies, Inc. VL805 USB 3.0 Host Controller ProcKernelCmdLine: coherent_pool=1M 8250.nr_uarts=0 snd_bcm2835.enable_compat_alsa=0 snd_bcm2835.enable_hdmi=1 snd_bcm2835.enable_headphones=1 video=HDMI-A-1:640x480M@60 smsc95xx.macaddr=DC:A6:32:D1:3E:28 vc_mem.mem_base=0x3ec0 vc_mem.mem_size=0x4000 dwc_otg.lpm_enable=0 console=tty1 root=LABEL=writable rootfstype=ext4 elevator=deadline rootwait fixrtc quiet splash SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) acpidump: version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.103-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.3.2-1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A 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/mesa/+bug/1911030/+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 1914007] Re: RT3290 Bluetooth not finding any device
This bug is Invalid for Ubuntu. If you would like to track the problem that is in Ubuntu then please use bug 1189721. ** Package changed: bluez (Ubuntu) => ubuntu ** Changed in: ubuntu Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1914007 Title: RT3290 Bluetooth not finding any device Status in Ubuntu: Invalid Bug description: Ubuntu :- 20.04 Hello I have RT3290 bluetooth in built and it was not working so I installed its latest driver from github whose version is 3.9.6 . Now its working but its not discoverable to any other device and also not finding any other device. Outout of command :- service bluetooth status ● bluetooth.service - Bluetooth service Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled; vendor pre> Active: active (running) since Sat 2021-01-30 09:49:10 IST; 1h 0min ago Docs: man:bluetoothd(8) Main PID: 1389 (bluetoothd) Status: "Running" Tasks: 1 (limit: 4514) Memory: 2.0M CGroup: /system.slice/bluetooth.service └─1389 /usr/lib/bluetooth/bluetoothd Jan 30 09:49:07 Piyush-X55C systemd[1]: Starting Bluetooth service... Jan 30 09:49:10 Piyush-X55C bluetoothd[1389]: Bluetooth daemon 5.53 Jan 30 09:49:10 Piyush-X55C systemd[1]: Started Bluetooth service. Jan 30 09:49:10 Piyush-X55C bluetoothd[1389]: Starting SDP server Jan 30 09:49:10 Piyush-X55C bluetoothd[1389]: Bluetooth management interface 1.> Jan 30 10:49:34 Piyush-X55C bluetoothd[1389]: Endpoint registered: sender=:1.66> Jan 30 10:49:34 Piyush-X55C bluetoothd[1389]: Endpoint registered: sender=:1.66> lines 1-18/18 (END) Output of command :- sudo btmgmt info Index list with 1 item hci0: Primary controller addr A4:17:31:1D:65:54 version 4 manufacturer 91 class 0x00 supported settings: powered connectable fast-connectable discoverable bondable link-security ssp br/edr debug-keys current settings: powered bondable ssp br/edr name Piyush-X55C Output of command :- bluetoothctl Agent registered [bluetooth]# scan on [bluetooth]# discoverable on [bluetooth]# scan on Failed to start discovery: org.bluez.Error.InProgress [bluetooth]# discoverable on Changing discoverable on succeeded [bluetooth]# Output of command :- sudo btmgmt find Unable to start discovery. status 0x0c (Not Supported) Output of command :- lspci -knn | grep Net -A3; lsusb 02:00.0 Network controller [0280]: Ralink corp. RT3290 Wireless 802.11n 1T/1R PCIe [1814:3290] Subsystem: Foxconn International, Inc. RT3290 Wireless 802.11n 1T/1R PCIe [105b:e055] Kernel driver in use: rt2800pci Kernel modules: rt2800pci Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 003: ID 1bcf:2883 Sunplus Innovation Technology Inc. Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 003 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Output of command :-dmesg | grep -i bluetooth [ 12.851854] Bluetooth: Core ver 2.22 [ 12.851883] Bluetooth: HCI device and connection manager initialized [ 12.851888] Bluetooth: HCI socket layer initialized [ 12.851889] Bluetooth: L2CAP socket layer initialized [ 12.851893] Bluetooth: SCO socket layer initialized [ 67.399550] audit: type=1400 audit(1611909043.091:58): apparmor="DENIED" operation="create" profile="snap.bluez.bluez" pid=875 comm="bluetoothd" family="bluetooth" sock_type="raw" protocol=1 requested_mask="create" denied_mask="create" [ 67.727240] audit: type=1400 audit(1611909043.419:60): apparmor="DENIED" operation="connect" profile="snap.bluez.bluez" name="/run/dbus/system_bus_socket" pid=875 comm="bluetoothd" requested_mask="wr" denied_mask="wr" fsuid=0 ouid=0 [ 67.929889] audit: type=1400 audit(1611909043.619:62): apparmor="DENIED" operation="create" profile="snap.bluez.bluez" pid=1043 comm="bluetoothd" family="bluetooth" sock_type="raw" protocol=1 requested_mask="create" denied_mask="create" [ 67.930261] audit: type=1400 audit(1611909043.623:63): apparmor="DENIED" operation="connect" profile="snap.bluez.bluez" name="/run/dbus/system_bus_socket" pid=1043 comm="bluetoothd" requested_mask="wr" denied_mask="wr" fsuid=0 ouid=0 [ 68.194380] audit: type=1400 audit(1611909043.887:65): apparmor="DENIED" operation="create" profile="snap.bluez.bluez" pid=1102 comm="bluetoothd" family="bluetooth" sock_type="raw" protocol=1 requested_mask="create" denied_mask="create" [ 68.194710] audit: typ
[Touch-packages] [Bug 1914007] Re: RT3290 Bluetooth not finding any device
** Changed in: bluez (Ubuntu) Status: Invalid => New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1914007 Title: RT3290 Bluetooth not finding any device Status in bluez package in Ubuntu: New Bug description: Ubuntu :- 20.04 Hello I have RT3290 bluetooth in built and it was not working so I installed its latest driver from github whose version is 3.9.6 . Now its working but its not discoverable to any other device and also not finding any other device. Outout of command :- service bluetooth status ● bluetooth.service - Bluetooth service Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled; vendor pre> Active: active (running) since Sat 2021-01-30 09:49:10 IST; 1h 0min ago Docs: man:bluetoothd(8) Main PID: 1389 (bluetoothd) Status: "Running" Tasks: 1 (limit: 4514) Memory: 2.0M CGroup: /system.slice/bluetooth.service └─1389 /usr/lib/bluetooth/bluetoothd Jan 30 09:49:07 Piyush-X55C systemd[1]: Starting Bluetooth service... Jan 30 09:49:10 Piyush-X55C bluetoothd[1389]: Bluetooth daemon 5.53 Jan 30 09:49:10 Piyush-X55C systemd[1]: Started Bluetooth service. Jan 30 09:49:10 Piyush-X55C bluetoothd[1389]: Starting SDP server Jan 30 09:49:10 Piyush-X55C bluetoothd[1389]: Bluetooth management interface 1.> Jan 30 10:49:34 Piyush-X55C bluetoothd[1389]: Endpoint registered: sender=:1.66> Jan 30 10:49:34 Piyush-X55C bluetoothd[1389]: Endpoint registered: sender=:1.66> lines 1-18/18 (END) Output of command :- sudo btmgmt info Index list with 1 item hci0: Primary controller addr A4:17:31:1D:65:54 version 4 manufacturer 91 class 0x00 supported settings: powered connectable fast-connectable discoverable bondable link-security ssp br/edr debug-keys current settings: powered bondable ssp br/edr name Piyush-X55C Output of command :- bluetoothctl Agent registered [bluetooth]# scan on [bluetooth]# discoverable on [bluetooth]# scan on Failed to start discovery: org.bluez.Error.InProgress [bluetooth]# discoverable on Changing discoverable on succeeded [bluetooth]# Output of command :- sudo btmgmt find Unable to start discovery. status 0x0c (Not Supported) Output of command :- lspci -knn | grep Net -A3; lsusb 02:00.0 Network controller [0280]: Ralink corp. RT3290 Wireless 802.11n 1T/1R PCIe [1814:3290] Subsystem: Foxconn International, Inc. RT3290 Wireless 802.11n 1T/1R PCIe [105b:e055] Kernel driver in use: rt2800pci Kernel modules: rt2800pci Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 003: ID 1bcf:2883 Sunplus Innovation Technology Inc. Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 003 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Output of command :-dmesg | grep -i bluetooth [ 12.851854] Bluetooth: Core ver 2.22 [ 12.851883] Bluetooth: HCI device and connection manager initialized [ 12.851888] Bluetooth: HCI socket layer initialized [ 12.851889] Bluetooth: L2CAP socket layer initialized [ 12.851893] Bluetooth: SCO socket layer initialized [ 67.399550] audit: type=1400 audit(1611909043.091:58): apparmor="DENIED" operation="create" profile="snap.bluez.bluez" pid=875 comm="bluetoothd" family="bluetooth" sock_type="raw" protocol=1 requested_mask="create" denied_mask="create" [ 67.727240] audit: type=1400 audit(1611909043.419:60): apparmor="DENIED" operation="connect" profile="snap.bluez.bluez" name="/run/dbus/system_bus_socket" pid=875 comm="bluetoothd" requested_mask="wr" denied_mask="wr" fsuid=0 ouid=0 [ 67.929889] audit: type=1400 audit(1611909043.619:62): apparmor="DENIED" operation="create" profile="snap.bluez.bluez" pid=1043 comm="bluetoothd" family="bluetooth" sock_type="raw" protocol=1 requested_mask="create" denied_mask="create" [ 67.930261] audit: type=1400 audit(1611909043.623:63): apparmor="DENIED" operation="connect" profile="snap.bluez.bluez" name="/run/dbus/system_bus_socket" pid=1043 comm="bluetoothd" requested_mask="wr" denied_mask="wr" fsuid=0 ouid=0 [ 68.194380] audit: type=1400 audit(1611909043.887:65): apparmor="DENIED" operation="create" profile="snap.bluez.bluez" pid=1102 comm="bluetoothd" family="bluetooth" sock_type="raw" protocol=1 requested_mask="create" denied_mask="create" [ 68.194710] audit: type=1400 audit(1611909043.887:66): apparmor="DENIED" operation="connect" profile="snap.bluez.bluez" name="/run/dbus/system_bus_socket" pid=1102
[Touch-packages] [Bug 1914029] [NEW] pulseaudio startup script should not blindly force audible bell
Public bug reported: File /usr/bin/start-pulseaudio-x11 ALWAYS loads module module-x11-bell and uploads audio sample for Pulseaudio if the file /usr/share/sounds/ubuntu/stereo/bell.ogg EXISTS in the filesystem. I have configured only visual bell for everything and therefore any part of the system that forcibly tries to play any kind of audio for bell output is simply broken. At bare minimum, this script should first check if the desktop environment has been configured to use visual bell instead of audible bell before loading the module. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: pulseaudio 1:11.1-1ubuntu7.11 ProcVersionSignature: Ubuntu 5.4.0-64.72~18.04.1-lowlatency 5.4.78 Uname: Linux 5.4.0-64-lowlatency x86_64 ApportVersion: 2.20.9-0ubuntu7.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: mira 6634 F pulseaudio /dev/snd/controlC0: mira 6634 F pulseaudio CurrentDesktop: MATE Date: Mon Feb 1 11:48:03 2021 EcryptfsInUse: Yes InstallationDate: Installed on 2019-01-05 (757 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/17/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1505 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: P8H77-M PRO dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1505:bd10/17/2014:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP8H77-MPRO:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: 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 ** Affects: pulseaudio (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- 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/1914029 Title: pulseaudio startup script should not blindly force audible bell Status in pulseaudio package in Ubuntu: New Bug description: File /usr/bin/start-pulseaudio-x11 ALWAYS loads module module-x11-bell and uploads audio sample for Pulseaudio if the file /usr/share/sounds/ubuntu/stereo/bell.ogg EXISTS in the filesystem. I have configured only visual bell for everything and therefore any part of the system that forcibly tries to play any kind of audio for bell output is simply broken. At bare minimum, this script should first check if the desktop environment has been configured to use visual bell instead of audible bell before loading the module. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: pulseaudio 1:11.1-1ubuntu7.11 ProcVersionSignature: Ubuntu 5.4.0-64.72~18.04.1-lowlatency 5.4.78 Uname: Linux 5.4.0-64-lowlatency x86_64 ApportVersion: 2.20.9-0ubuntu7.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: mira 6634 F pulseaudio /dev/snd/controlC0: mira 6634 F pulseaudio CurrentDesktop: MATE Date: Mon Feb 1 11:48:03 2021 EcryptfsInUse: Yes InstallationDate: Installed on 2019-01-05 (757 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/17/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1505 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: P8H77-M PRO dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1505:bd10/17/2014:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP8H77-MPRO:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: 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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1914029/+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 1913411] Re: While I updating ModemManager to 1.14.2, there isno mobile broadband in system status bar drop-down menu.
This problem is solved, the patch is in here: https://gitlab.gnome.org/Popax21/gnome- shell/-/commit/461bbcff153d7167d22bbf0e80ecbc5397d724cd However, there is no updated package on Ubuntu 20.04 to solve it. Will there be an updated package to solve this problem later? This question is very important because the current supported ModemManager-1.12.8 does not support 5G capability, and only updates to ModemManager >=1.14.0 will supports 5G. Can this patch be added to the next version of Ubuntu20.04 gnome-shell package? Best Regards, Freedom -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to modemmanager in Ubuntu. https://bugs.launchpad.net/bugs/1913411 Title: While I updating ModemManager to 1.14.2, there isno mobile broadband in system status bar drop-down menu. Status in gnome-shell package in Ubuntu: Invalid Status in modemmanager package in Ubuntu: Invalid Bug description: While I updating ModemManager to 1.14.2, there isno mobile broadband in system status bar drop-down menu. I just can see mobile broadband in network in system settings menu. OS: ubuntu20.04 Module: SDX55 ModemManager:1.14.2 iusse: 1.No mobile broadband in system status bar drop-down menu. 2.Every time I connect to the mobile broadband network in system settings menu, I need to add new connection. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1913411/+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 1913859] Re: RT3290 Bluetooth not finding any device
*** This bug is a duplicate of bug 1914007 *** https://bugs.launchpad.net/bugs/1914007 ** Changed in: bluez (Ubuntu) Status: In Progress => Invalid ** This bug has been marked a duplicate of bug 1914007 RT3290 Bluetooth not finding any device -- 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/1913859 Title: RT3290 Bluetooth not finding any device Status in bluez package in Ubuntu: Invalid Bug description: Ubuntu :- 20.04 Hello I have RT3290 bluetooth in built and it was not working so I installed its latest driver from github whose version is 3.9.6 . Now its working but its not discoverable to any other device and also not finding any other device. Outout of command :- service bluetooth status ● bluetooth.service - Bluetooth service Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled; vendor pre> Active: active (running) since Sat 2021-01-30 09:49:10 IST; 1h 0min ago Docs: man:bluetoothd(8) Main PID: 1389 (bluetoothd) Status: "Running" Tasks: 1 (limit: 4514) Memory: 2.0M CGroup: /system.slice/bluetooth.service └─1389 /usr/lib/bluetooth/bluetoothd Jan 30 09:49:07 Piyush-X55C systemd[1]: Starting Bluetooth service... Jan 30 09:49:10 Piyush-X55C bluetoothd[1389]: Bluetooth daemon 5.53 Jan 30 09:49:10 Piyush-X55C systemd[1]: Started Bluetooth service. Jan 30 09:49:10 Piyush-X55C bluetoothd[1389]: Starting SDP server Jan 30 09:49:10 Piyush-X55C bluetoothd[1389]: Bluetooth management interface 1.> Jan 30 10:49:34 Piyush-X55C bluetoothd[1389]: Endpoint registered: sender=:1.66> Jan 30 10:49:34 Piyush-X55C bluetoothd[1389]: Endpoint registered: sender=:1.66> lines 1-18/18 (END) Output of command :- sudo btmgmt info Index list with 1 item hci0: Primary controller addr A4:17:31:1D:65:54 version 4 manufacturer 91 class 0x00 supported settings: powered connectable fast-connectable discoverable bondable link-security ssp br/edr debug-keys current settings: powered bondable ssp br/edr name Piyush-X55C Output of command :- bluetoothctl Agent registered [bluetooth]# scan on [bluetooth]# discoverable on [bluetooth]# scan on Failed to start discovery: org.bluez.Error.InProgress [bluetooth]# discoverable on Changing discoverable on succeeded [bluetooth]# Output of command :- sudo btmgmt find Unable to start discovery. status 0x0c (Not Supported) Output of command :- lspci -knn | grep Net -A3; lsusb 02:00.0 Network controller [0280]: Ralink corp. RT3290 Wireless 802.11n 1T/1R PCIe [1814:3290] Subsystem: Foxconn International, Inc. RT3290 Wireless 802.11n 1T/1R PCIe [105b:e055] Kernel driver in use: rt2800pci Kernel modules: rt2800pci Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 003: ID 1bcf:2883 Sunplus Innovation Technology Inc. Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 003 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Output of command :-dmesg | grep -i bluetooth [ 12.851854] Bluetooth: Core ver 2.22 [ 12.851883] Bluetooth: HCI device and connection manager initialized [ 12.851888] Bluetooth: HCI socket layer initialized [ 12.851889] Bluetooth: L2CAP socket layer initialized [ 12.851893] Bluetooth: SCO socket layer initialized [ 67.399550] audit: type=1400 audit(1611909043.091:58): apparmor="DENIED" operation="create" profile="snap.bluez.bluez" pid=875 comm="bluetoothd" family="bluetooth" sock_type="raw" protocol=1 requested_mask="create" denied_mask="create" [ 67.727240] audit: type=1400 audit(1611909043.419:60): apparmor="DENIED" operation="connect" profile="snap.bluez.bluez" name="/run/dbus/system_bus_socket" pid=875 comm="bluetoothd" requested_mask="wr" denied_mask="wr" fsuid=0 ouid=0 [ 67.929889] audit: type=1400 audit(1611909043.619:62): apparmor="DENIED" operation="create" profile="snap.bluez.bluez" pid=1043 comm="bluetoothd" family="bluetooth" sock_type="raw" protocol=1 requested_mask="create" denied_mask="create" [ 67.930261] audit: type=1400 audit(1611909043.623:63): apparmor="DENIED" operation="connect" profile="snap.bluez.bluez" name="/run/dbus/system_bus_socket" pid=1043 comm="bluetoothd" requested_mask="wr" denied_mask="wr" fsuid=0 ouid=0 [ 68.194380] audit: type=1400 audit(1611909043.887:65): apparmor="DENIED" operation="create" profile="snap.bluez.bluez" pid=1102 comm="bluetoothd" family="bluetooth" sock_type="raw" prot
[Touch-packages] [Bug 1914007] Re: RT3290 Bluetooth not finding any device
Yes, you have a different problem caused by a driver that is not supported or provided by Ubuntu. That makes this bug Invalid for the 'Ubuntu' task. My only suggestions are: 1. Subscribe to bug 1189721. 2. Try replacing the wireless card in the laptop with a different card, ideally made by Intel. Because it looks like RT3290 might never be supported in Linux. -- 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/1914007 Title: RT3290 Bluetooth not finding any device Status in bluez package in Ubuntu: Invalid Bug description: Ubuntu :- 20.04 Hello I have RT3290 bluetooth in built and it was not working so I installed its latest driver from github whose version is 3.9.6 . Now its working but its not discoverable to any other device and also not finding any other device. Outout of command :- service bluetooth status ● bluetooth.service - Bluetooth service Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled; vendor pre> Active: active (running) since Sat 2021-01-30 09:49:10 IST; 1h 0min ago Docs: man:bluetoothd(8) Main PID: 1389 (bluetoothd) Status: "Running" Tasks: 1 (limit: 4514) Memory: 2.0M CGroup: /system.slice/bluetooth.service └─1389 /usr/lib/bluetooth/bluetoothd Jan 30 09:49:07 Piyush-X55C systemd[1]: Starting Bluetooth service... Jan 30 09:49:10 Piyush-X55C bluetoothd[1389]: Bluetooth daemon 5.53 Jan 30 09:49:10 Piyush-X55C systemd[1]: Started Bluetooth service. Jan 30 09:49:10 Piyush-X55C bluetoothd[1389]: Starting SDP server Jan 30 09:49:10 Piyush-X55C bluetoothd[1389]: Bluetooth management interface 1.> Jan 30 10:49:34 Piyush-X55C bluetoothd[1389]: Endpoint registered: sender=:1.66> Jan 30 10:49:34 Piyush-X55C bluetoothd[1389]: Endpoint registered: sender=:1.66> lines 1-18/18 (END) Output of command :- sudo btmgmt info Index list with 1 item hci0: Primary controller addr A4:17:31:1D:65:54 version 4 manufacturer 91 class 0x00 supported settings: powered connectable fast-connectable discoverable bondable link-security ssp br/edr debug-keys current settings: powered bondable ssp br/edr name Piyush-X55C Output of command :- bluetoothctl Agent registered [bluetooth]# scan on [bluetooth]# discoverable on [bluetooth]# scan on Failed to start discovery: org.bluez.Error.InProgress [bluetooth]# discoverable on Changing discoverable on succeeded [bluetooth]# Output of command :- sudo btmgmt find Unable to start discovery. status 0x0c (Not Supported) Output of command :- lspci -knn | grep Net -A3; lsusb 02:00.0 Network controller [0280]: Ralink corp. RT3290 Wireless 802.11n 1T/1R PCIe [1814:3290] Subsystem: Foxconn International, Inc. RT3290 Wireless 802.11n 1T/1R PCIe [105b:e055] Kernel driver in use: rt2800pci Kernel modules: rt2800pci Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 003: ID 1bcf:2883 Sunplus Innovation Technology Inc. Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 003 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Output of command :-dmesg | grep -i bluetooth [ 12.851854] Bluetooth: Core ver 2.22 [ 12.851883] Bluetooth: HCI device and connection manager initialized [ 12.851888] Bluetooth: HCI socket layer initialized [ 12.851889] Bluetooth: L2CAP socket layer initialized [ 12.851893] Bluetooth: SCO socket layer initialized [ 67.399550] audit: type=1400 audit(1611909043.091:58): apparmor="DENIED" operation="create" profile="snap.bluez.bluez" pid=875 comm="bluetoothd" family="bluetooth" sock_type="raw" protocol=1 requested_mask="create" denied_mask="create" [ 67.727240] audit: type=1400 audit(1611909043.419:60): apparmor="DENIED" operation="connect" profile="snap.bluez.bluez" name="/run/dbus/system_bus_socket" pid=875 comm="bluetoothd" requested_mask="wr" denied_mask="wr" fsuid=0 ouid=0 [ 67.929889] audit: type=1400 audit(1611909043.619:62): apparmor="DENIED" operation="create" profile="snap.bluez.bluez" pid=1043 comm="bluetoothd" family="bluetooth" sock_type="raw" protocol=1 requested_mask="create" denied_mask="create" [ 67.930261] audit: type=1400 audit(1611909043.623:63): apparmor="DENIED" operation="connect" profile="snap.bluez.bluez" name="/run/dbus/system_bus_socket" pid=1043 comm="bluetoothd" requested_mask="wr" denied_mask="wr" fsuid=0 ouid=0 [ 68.194380] audit: type=1400 audit(1611909043.887:65): apparmor="DENIED" operation="create" profile="sn
[Touch-packages] [Bug 1914007] Re: RT3290 Bluetooth not finding any device
Please suggest me a solution for this @Daniel. ** This bug is no longer a duplicate of bug 1189721 Ralink RT3290 doesn't have a bluetooth driver -- 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/1914007 Title: RT3290 Bluetooth not finding any device Status in bluez package in Ubuntu: Invalid Bug description: Ubuntu :- 20.04 Hello I have RT3290 bluetooth in built and it was not working so I installed its latest driver from github whose version is 3.9.6 . Now its working but its not discoverable to any other device and also not finding any other device. Outout of command :- service bluetooth status ● bluetooth.service - Bluetooth service Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled; vendor pre> Active: active (running) since Sat 2021-01-30 09:49:10 IST; 1h 0min ago Docs: man:bluetoothd(8) Main PID: 1389 (bluetoothd) Status: "Running" Tasks: 1 (limit: 4514) Memory: 2.0M CGroup: /system.slice/bluetooth.service └─1389 /usr/lib/bluetooth/bluetoothd Jan 30 09:49:07 Piyush-X55C systemd[1]: Starting Bluetooth service... Jan 30 09:49:10 Piyush-X55C bluetoothd[1389]: Bluetooth daemon 5.53 Jan 30 09:49:10 Piyush-X55C systemd[1]: Started Bluetooth service. Jan 30 09:49:10 Piyush-X55C bluetoothd[1389]: Starting SDP server Jan 30 09:49:10 Piyush-X55C bluetoothd[1389]: Bluetooth management interface 1.> Jan 30 10:49:34 Piyush-X55C bluetoothd[1389]: Endpoint registered: sender=:1.66> Jan 30 10:49:34 Piyush-X55C bluetoothd[1389]: Endpoint registered: sender=:1.66> lines 1-18/18 (END) Output of command :- sudo btmgmt info Index list with 1 item hci0: Primary controller addr A4:17:31:1D:65:54 version 4 manufacturer 91 class 0x00 supported settings: powered connectable fast-connectable discoverable bondable link-security ssp br/edr debug-keys current settings: powered bondable ssp br/edr name Piyush-X55C Output of command :- bluetoothctl Agent registered [bluetooth]# scan on [bluetooth]# discoverable on [bluetooth]# scan on Failed to start discovery: org.bluez.Error.InProgress [bluetooth]# discoverable on Changing discoverable on succeeded [bluetooth]# Output of command :- sudo btmgmt find Unable to start discovery. status 0x0c (Not Supported) Output of command :- lspci -knn | grep Net -A3; lsusb 02:00.0 Network controller [0280]: Ralink corp. RT3290 Wireless 802.11n 1T/1R PCIe [1814:3290] Subsystem: Foxconn International, Inc. RT3290 Wireless 802.11n 1T/1R PCIe [105b:e055] Kernel driver in use: rt2800pci Kernel modules: rt2800pci Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 003: ID 1bcf:2883 Sunplus Innovation Technology Inc. Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 003 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Output of command :-dmesg | grep -i bluetooth [ 12.851854] Bluetooth: Core ver 2.22 [ 12.851883] Bluetooth: HCI device and connection manager initialized [ 12.851888] Bluetooth: HCI socket layer initialized [ 12.851889] Bluetooth: L2CAP socket layer initialized [ 12.851893] Bluetooth: SCO socket layer initialized [ 67.399550] audit: type=1400 audit(1611909043.091:58): apparmor="DENIED" operation="create" profile="snap.bluez.bluez" pid=875 comm="bluetoothd" family="bluetooth" sock_type="raw" protocol=1 requested_mask="create" denied_mask="create" [ 67.727240] audit: type=1400 audit(1611909043.419:60): apparmor="DENIED" operation="connect" profile="snap.bluez.bluez" name="/run/dbus/system_bus_socket" pid=875 comm="bluetoothd" requested_mask="wr" denied_mask="wr" fsuid=0 ouid=0 [ 67.929889] audit: type=1400 audit(1611909043.619:62): apparmor="DENIED" operation="create" profile="snap.bluez.bluez" pid=1043 comm="bluetoothd" family="bluetooth" sock_type="raw" protocol=1 requested_mask="create" denied_mask="create" [ 67.930261] audit: type=1400 audit(1611909043.623:63): apparmor="DENIED" operation="connect" profile="snap.bluez.bluez" name="/run/dbus/system_bus_socket" pid=1043 comm="bluetoothd" requested_mask="wr" denied_mask="wr" fsuid=0 ouid=0 [ 68.194380] audit: type=1400 audit(1611909043.887:65): apparmor="DENIED" operation="create" profile="snap.bluez.bluez" pid=1102 comm="bluetoothd" family="bluetooth" sock_type="raw" protocol=1 requested_mask="create" denied_mask="create" [ 68.194710] audit: type=1400 audit(1611909043.887:66): apparmor="DENIED"
[Touch-packages] [Bug 1914007] Re: RT3290 Bluetooth not finding any device
And yeah in that given bug post there is a solution how to get working RT3290 but my problem is different my adapter is working but the agent Bluetoothctl is giving an error related to blueman so isn't it a different problem? @Daniel -- 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/1914007 Title: RT3290 Bluetooth not finding any device Status in bluez package in Ubuntu: Invalid Bug description: Ubuntu :- 20.04 Hello I have RT3290 bluetooth in built and it was not working so I installed its latest driver from github whose version is 3.9.6 . Now its working but its not discoverable to any other device and also not finding any other device. Outout of command :- service bluetooth status ● bluetooth.service - Bluetooth service Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled; vendor pre> Active: active (running) since Sat 2021-01-30 09:49:10 IST; 1h 0min ago Docs: man:bluetoothd(8) Main PID: 1389 (bluetoothd) Status: "Running" Tasks: 1 (limit: 4514) Memory: 2.0M CGroup: /system.slice/bluetooth.service └─1389 /usr/lib/bluetooth/bluetoothd Jan 30 09:49:07 Piyush-X55C systemd[1]: Starting Bluetooth service... Jan 30 09:49:10 Piyush-X55C bluetoothd[1389]: Bluetooth daemon 5.53 Jan 30 09:49:10 Piyush-X55C systemd[1]: Started Bluetooth service. Jan 30 09:49:10 Piyush-X55C bluetoothd[1389]: Starting SDP server Jan 30 09:49:10 Piyush-X55C bluetoothd[1389]: Bluetooth management interface 1.> Jan 30 10:49:34 Piyush-X55C bluetoothd[1389]: Endpoint registered: sender=:1.66> Jan 30 10:49:34 Piyush-X55C bluetoothd[1389]: Endpoint registered: sender=:1.66> lines 1-18/18 (END) Output of command :- sudo btmgmt info Index list with 1 item hci0: Primary controller addr A4:17:31:1D:65:54 version 4 manufacturer 91 class 0x00 supported settings: powered connectable fast-connectable discoverable bondable link-security ssp br/edr debug-keys current settings: powered bondable ssp br/edr name Piyush-X55C Output of command :- bluetoothctl Agent registered [bluetooth]# scan on [bluetooth]# discoverable on [bluetooth]# scan on Failed to start discovery: org.bluez.Error.InProgress [bluetooth]# discoverable on Changing discoverable on succeeded [bluetooth]# Output of command :- sudo btmgmt find Unable to start discovery. status 0x0c (Not Supported) Output of command :- lspci -knn | grep Net -A3; lsusb 02:00.0 Network controller [0280]: Ralink corp. RT3290 Wireless 802.11n 1T/1R PCIe [1814:3290] Subsystem: Foxconn International, Inc. RT3290 Wireless 802.11n 1T/1R PCIe [105b:e055] Kernel driver in use: rt2800pci Kernel modules: rt2800pci Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 003: ID 1bcf:2883 Sunplus Innovation Technology Inc. Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 003 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Output of command :-dmesg | grep -i bluetooth [ 12.851854] Bluetooth: Core ver 2.22 [ 12.851883] Bluetooth: HCI device and connection manager initialized [ 12.851888] Bluetooth: HCI socket layer initialized [ 12.851889] Bluetooth: L2CAP socket layer initialized [ 12.851893] Bluetooth: SCO socket layer initialized [ 67.399550] audit: type=1400 audit(1611909043.091:58): apparmor="DENIED" operation="create" profile="snap.bluez.bluez" pid=875 comm="bluetoothd" family="bluetooth" sock_type="raw" protocol=1 requested_mask="create" denied_mask="create" [ 67.727240] audit: type=1400 audit(1611909043.419:60): apparmor="DENIED" operation="connect" profile="snap.bluez.bluez" name="/run/dbus/system_bus_socket" pid=875 comm="bluetoothd" requested_mask="wr" denied_mask="wr" fsuid=0 ouid=0 [ 67.929889] audit: type=1400 audit(1611909043.619:62): apparmor="DENIED" operation="create" profile="snap.bluez.bluez" pid=1043 comm="bluetoothd" family="bluetooth" sock_type="raw" protocol=1 requested_mask="create" denied_mask="create" [ 67.930261] audit: type=1400 audit(1611909043.623:63): apparmor="DENIED" operation="connect" profile="snap.bluez.bluez" name="/run/dbus/system_bus_socket" pid=1043 comm="bluetoothd" requested_mask="wr" denied_mask="wr" fsuid=0 ouid=0 [ 68.194380] audit: type=1400 audit(1611909043.887:65): apparmor="DENIED" operation="create" profile="snap.bluez.bluez" pid=1102 comm="bluetoothd" family="bluetooth" sock_type="raw" protocol=1 requested_mask="create" denied_mask="cre
[Touch-packages] [Bug 1914016] [NEW] package linux-firmware 1.187.9 failed to install/upgrade: installed linux-firmware package post-installation script subprocess returned error exit status 1
Public bug reported: ON a zfs file system ProblemType: Package DistroRelease: Ubuntu 20.04 Package: linux-firmware 1.187.9 ProcVersionSignature: Ubuntu 5.8.0-41.46~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-41-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gdm3156 F pulseaudio chmick11493 F pulseaudio /dev/snd/controlC1: gdm3156 F pulseaudio chmick11493 F pulseaudio CasperMD5CheckResult: skip Date: Thu Jan 28 17:40:56 2021 Dependencies: ErrorMessage: installed linux-firmware package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2020-07-31 (184 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) IwConfig: lono wireless extensions. enp2s0no wireless extensions. MachineType: To be filled by O.E.M. To be filled by O.E.M. PackageArchitecture: all ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_mp63t3@/vmlinuz-5.8.0-41-generic root=ZFS=rpool/ROOT/ubuntu_mp63t3 ro quiet splash vt.handoff=1 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: grub-pc 2.04-1ubuntu26.8 RfKill: SourcePackage: initramfs-tools Title: package linux-firmware 1.187.9 failed to install/upgrade: installed linux-firmware package post-installation script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/24/2015 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2601 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: M5A97 R2.0 dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2601:bd03/24/2015:br4.6:svnTobefilledbyO.E.M.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnASUSTeKCOMPUTERINC.:rnM5A97R2.0:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: To be filled by O.E.M. dmi.product.sku: SKU dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: To be filled by O.E.M. ** Affects: initramfs-tools (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package focal -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1914016 Title: package linux-firmware 1.187.9 failed to install/upgrade: installed linux-firmware package post-installation script subprocess returned error exit status 1 Status in initramfs-tools package in Ubuntu: New Bug description: ON a zfs file system ProblemType: Package DistroRelease: Ubuntu 20.04 Package: linux-firmware 1.187.9 ProcVersionSignature: Ubuntu 5.8.0-41.46~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-41-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gdm3156 F pulseaudio chmick11493 F pulseaudio /dev/snd/controlC1: gdm3156 F pulseaudio chmick11493 F pulseaudio CasperMD5CheckResult: skip Date: Thu Jan 28 17:40:56 2021 Dependencies: ErrorMessage: installed linux-firmware package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2020-07-31 (184 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) IwConfig: lono wireless extensions. enp2s0no wireless extensions. MachineType: To be filled by O.E.M. To be filled by O.E.M. PackageArchitecture: all ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_mp63t3@/vmlinuz-5.8.0-41-generic root=ZFS=rpool/ROOT/ubuntu_mp63t3 ro quiet splash vt.handoff=1 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: grub-pc 2.04-1ubuntu26.8 RfKill: SourcePackage: initramfs-tools Title: package linux-firmware 1.187.9 failed to install/upgrade: installed linux-firmware package post-installation script
[Touch-packages] [Bug 983220] Re: subpixel rendering doesn't respect screen rotation
Thank you for reporting this bug to Ubuntu. Ubuntu 12.04 (precise) reached end-of-life on April 28, 2017. See this document for currently supported Ubuntu releases: https://wiki.ubuntu.com/Releases We appreciate that this bug may be old and you might not be interested in discussing it any more. But if you are then please upgrade to the latest Ubuntu version and re-test. If you then find the bug is still present in the newer Ubuntu version, please add a comment here telling us which new version it is in. ** Package changed: wayland (Ubuntu) => ubuntu ** Changed in: ubuntu Status: New => Won't Fix -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to freetype in Ubuntu. https://bugs.launchpad.net/bugs/983220 Title: subpixel rendering doesn't respect screen rotation Status in Ubuntu: Won't Fix Status in freetype package in Ubuntu: Invalid Bug description: 1) Open gnome-terminal 2) xrandr --output default --rotate inverted 2) Open another gnome-terminal In both the original and the new terminal, text has red and blue "shadows" caused by subpixel rendering that doesn't match up to the inverted pixel layout resulting from the screen being flipped 180 degrees. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: libfreetype6 2.4.8-1ubuntu2 ProcVersionSignature: Ubuntu 3.2.0-23.36-generic 3.2.14 Uname: Linux 3.2.0-23-generic x86_64 NonfreeKernelModules: nvidia wl ApportVersion: 2.0.1-0ubuntu3 Architecture: amd64 Date: Mon Apr 16 11:34:06 2012 EcryptfsInUse: Yes InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Alpha amd64 (2029.1) ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: freetype UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/983220/+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 1723130] Re: totem crashed with SIGSEGV in wl_proxy_add_listener() from wl_buffer_add_listener() from dri2_wl_swap_buffers_with_damage() from eglSwapBuffers() from _cogl_winsys_o
** Tags removed: artful -- 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/1723130 Title: totem crashed with SIGSEGV in wl_proxy_add_listener() from wl_buffer_add_listener() from dri2_wl_swap_buffers_with_damage() from eglSwapBuffers() from _cogl_winsys_onscreen_swap_buffers_with_damage() Status in mesa package in Ubuntu: Confirmed Status in totem package in Ubuntu: Confirmed Status in wayland package in Ubuntu: Confirmed Bug description: https://errors.ubuntu.com/problem/bc6e28a2367ba53b9714f5982d0034dbd45a1fd7 --- I just opened the video from nautilus with double click ProblemType: Crash DistroRelease: Ubuntu 17.10 Package: totem 3.26.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.12.0-13.14-generic 4.12.10 Uname: Linux 4.12.0-13-generic x86_64 ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Oct 12 16:06:22 2017 ExecutablePath: /usr/bin/totem InstallationDate: Installed on 2017-09-17 (24 days ago) InstallationMedia: It ProcCmdline: /usr/bin/totem --gapplication-service ProcEnviron: SHELL=/bin/bash XDG_RUNTIME_DIR= PATH=(custom, no user) LANG=es_ES.UTF-8 SegvAnalysis: Segfault happened at: 0x7f368b77c77c : testb $0x4,0x28(%rdi) PC (0x7f368b77c77c) ok source "$0x4" ok destination "0x28(%rdi)" (0x0028) not located in a known VMA region (needed writable region)! SegvReason: writing NULL VMA Signal: 11 SourcePackage: totem StacktraceTop: wl_proxy_add_listener () from /usr/lib/x86_64-linux-gnu/libwayland-client.so.0 ?? () from /usr/lib/x86_64-linux-gnu/mesa-egl/libEGL.so.1 eglSwapBuffers () from /usr/lib/x86_64-linux-gnu/mesa-egl/libEGL.so.1 ?? () from /usr/lib/x86_64-linux-gnu/libcogl.so.20 cogl_onscreen_swap_buffers_with_damage () from /usr/lib/x86_64-linux-gnu/libcogl.so.20 Title: totem crashed with SIGSEGV in wl_proxy_add_listener() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo XorgLog: Error: [Errno 2] No existe el archivo o el directorio: '/var/log/Xorg.0.log' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1723130/+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 1630931] Re: Wayland turkish language bug
Please tell us if you still experience this bug, and if so then what Ubuntu release is affected. ** Package changed: wayland (Ubuntu) => mutter (Ubuntu) ** Changed in: mutter (Ubuntu) Status: Confirmed => Incomplete ** Tags added: i18n ** Tags added: wayland wayland-session -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to wayland in Ubuntu. https://bugs.launchpad.net/bugs/1630931 Title: Wayland turkish language bug Status in Kali Linux : Fix Released Status in mutter package in Ubuntu: Incomplete Status in Fedora: Won't Fix Bug description: I can not write any of these letters "ı,I,i,İ" in GNOME Wayland Session. To manage notifications about this bug go to: https://bugs.launchpad.net/kiddomonster/+bug/1630931/+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 1914007] Re: RT3290 Bluetooth not finding any device
** Changed in: bluez (Ubuntu) Status: New => Invalid ** This bug has been marked a duplicate of bug 1189721 Ralink RT3290 doesn't have a bluetooth driver -- 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/1914007 Title: RT3290 Bluetooth not finding any device Status in bluez package in Ubuntu: Invalid Bug description: Ubuntu :- 20.04 Hello I have RT3290 bluetooth in built and it was not working so I installed its latest driver from github whose version is 3.9.6 . Now its working but its not discoverable to any other device and also not finding any other device. Outout of command :- service bluetooth status ● bluetooth.service - Bluetooth service Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled; vendor pre> Active: active (running) since Sat 2021-01-30 09:49:10 IST; 1h 0min ago Docs: man:bluetoothd(8) Main PID: 1389 (bluetoothd) Status: "Running" Tasks: 1 (limit: 4514) Memory: 2.0M CGroup: /system.slice/bluetooth.service └─1389 /usr/lib/bluetooth/bluetoothd Jan 30 09:49:07 Piyush-X55C systemd[1]: Starting Bluetooth service... Jan 30 09:49:10 Piyush-X55C bluetoothd[1389]: Bluetooth daemon 5.53 Jan 30 09:49:10 Piyush-X55C systemd[1]: Started Bluetooth service. Jan 30 09:49:10 Piyush-X55C bluetoothd[1389]: Starting SDP server Jan 30 09:49:10 Piyush-X55C bluetoothd[1389]: Bluetooth management interface 1.> Jan 30 10:49:34 Piyush-X55C bluetoothd[1389]: Endpoint registered: sender=:1.66> Jan 30 10:49:34 Piyush-X55C bluetoothd[1389]: Endpoint registered: sender=:1.66> lines 1-18/18 (END) Output of command :- sudo btmgmt info Index list with 1 item hci0: Primary controller addr A4:17:31:1D:65:54 version 4 manufacturer 91 class 0x00 supported settings: powered connectable fast-connectable discoverable bondable link-security ssp br/edr debug-keys current settings: powered bondable ssp br/edr name Piyush-X55C Output of command :- bluetoothctl Agent registered [bluetooth]# scan on [bluetooth]# discoverable on [bluetooth]# scan on Failed to start discovery: org.bluez.Error.InProgress [bluetooth]# discoverable on Changing discoverable on succeeded [bluetooth]# Output of command :- sudo btmgmt find Unable to start discovery. status 0x0c (Not Supported) Output of command :- lspci -knn | grep Net -A3; lsusb 02:00.0 Network controller [0280]: Ralink corp. RT3290 Wireless 802.11n 1T/1R PCIe [1814:3290] Subsystem: Foxconn International, Inc. RT3290 Wireless 802.11n 1T/1R PCIe [105b:e055] Kernel driver in use: rt2800pci Kernel modules: rt2800pci Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 003: ID 1bcf:2883 Sunplus Innovation Technology Inc. Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 003 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Output of command :-dmesg | grep -i bluetooth [ 12.851854] Bluetooth: Core ver 2.22 [ 12.851883] Bluetooth: HCI device and connection manager initialized [ 12.851888] Bluetooth: HCI socket layer initialized [ 12.851889] Bluetooth: L2CAP socket layer initialized [ 12.851893] Bluetooth: SCO socket layer initialized [ 67.399550] audit: type=1400 audit(1611909043.091:58): apparmor="DENIED" operation="create" profile="snap.bluez.bluez" pid=875 comm="bluetoothd" family="bluetooth" sock_type="raw" protocol=1 requested_mask="create" denied_mask="create" [ 67.727240] audit: type=1400 audit(1611909043.419:60): apparmor="DENIED" operation="connect" profile="snap.bluez.bluez" name="/run/dbus/system_bus_socket" pid=875 comm="bluetoothd" requested_mask="wr" denied_mask="wr" fsuid=0 ouid=0 [ 67.929889] audit: type=1400 audit(1611909043.619:62): apparmor="DENIED" operation="create" profile="snap.bluez.bluez" pid=1043 comm="bluetoothd" family="bluetooth" sock_type="raw" protocol=1 requested_mask="create" denied_mask="create" [ 67.930261] audit: type=1400 audit(1611909043.623:63): apparmor="DENIED" operation="connect" profile="snap.bluez.bluez" name="/run/dbus/system_bus_socket" pid=1043 comm="bluetoothd" requested_mask="wr" denied_mask="wr" fsuid=0 ouid=0 [ 68.194380] audit: type=1400 audit(1611909043.887:65): apparmor="DENIED" operation="create" profile="snap.bluez.bluez" pid=1102 comm="bluetoothd" family="bluetooth" sock_type="raw" protocol=1 requested_mask="create" denied_mask="create" [ 68.194710] audit: type=1400 audit(1611909043.887:66): ap
[Touch-packages] [Bug 1894329] Re: ZFS revert from grub menu not working.
This bug was fixed in the package zfs-linux - 0.8.3-1ubuntu12.6 --- zfs-linux (0.8.3-1ubuntu12.6) focal; urgency=medium [ Didier Roche ] [ Jean-Baptiste Lallement ] * Generate clone uuid without dd which is flagged as having an executable stack. Thanks Usarin Heininga for the patch (LP: #1894329) [ Andrea Righi ] * fix potential user-space double free when running "zfs mount -a" (LP: #1902588) - 4702-Revert-Let-zfs-mount-all-tolerate-in-progress-mounts.patch -- Colin Ian King Mon, 30 Nov 2020 19:00:00 + ** Changed in: zfs-linux (Ubuntu Focal) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to coreutils in Ubuntu. https://bugs.launchpad.net/bugs/1894329 Title: ZFS revert from grub menu not working. Status in coreutils package in Ubuntu: Incomplete Status in zfs-linux package in Ubuntu: Fix Released Status in coreutils source package in Focal: Incomplete Status in zfs-linux source package in Focal: Fix Released Status in coreutils source package in Groovy: Incomplete Status in zfs-linux source package in Groovy: Fix Released Bug description: [Impact] * Users can’t revert to previous snapshots when enabling the hw enablement stack kernel on focal or using any more recent version. * The option is available on grub and will let you with a broken system, partially cloned. [Test Case] * Boot on a system, using ZFS and ZSys. * In grub, select "History" entry * Select one of the "Revert" option: the system should boot after being reverted with an older version. [Where problems could occur] * The code is in the initramfs, where the generated id suffix for all our ZFS datasets was empty due to new coreutils/kernels. * We replace dd with another way (more robust and simple) for generating this ID. - @coreutils maintainers, any idea why dd is being flagged as having an executable stack? When I try to revert to a previous state from the grub menu, the boot fails. The system drops me to a repair modus. zfs-mount-generator fails with the message: couldn't ensure boot: Mounted clone bootFS dataset created by initramfs doesn't have a valid _suffix (at least .*_): \"rpool/ROOT/ubuntu_\"". After a reboot I have an extra clone called "rpool/ROOT/ubuntu_", indeed without a suffix. After a little investigation I found the problem in /usr/share/initramfs-tools/scripts/zfs at the end in function uid() { dd if=/dev/urandom of=/dev/stdout bs=1 count=100 2>/dev/null | tr -dc 'a-z0-9' | cut -c-6 }, the dd command fails during boot with the message "process 'dd' started with executable stack. After this an empty uid is returned which explains the dataset without a proper suffix. Replacing the function with: uid() { grep -a -m10 -E "\*" /dev/urandom 2>/dev/null | tr -dc 'a-z0-9' | cut -c-6 } fixes the problem. Ubuntu version is: Description:Ubuntu Groovy Gorilla (development branch) Release:20.10 zfs-initramfs version is: 0.8.4-1ubuntu11 With regards, Usarin Heininga ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: zfs-initramfs 0.8.4-1ubuntu11 ProcVersionSignature: Ubuntu 5.8.0-18.19-generic 5.8.4 Uname: Linux 5.8.0-18-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu45 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Fri Sep 4 20:23:44 2020 InstallationDate: Installed on 2020-09-02 (2 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200831) ProcEnviron: LANGUAGE= PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=nl_NL.UTF-8 SHELL=/bin/bash SourcePackage: zfs-linux UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/coreutils/+bug/1894329/+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 1913493] Re: pc
Please tell us what kind of problem you are experiencing. ** 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/1913493 Title: pc Status in Ubuntu: Incomplete Bug description: pc ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3.1 ProcVersionSignature: Ubuntu 4.15.0-45.48~16.04.1-generic 4.15.18 Uname: Linux 4.15.0-45-generic i686 .tmp.unity_support_test.1: ApportVersion: 2.20.1-0ubuntu2.18 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Thu Jan 28 00:27:54 2021 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu DpkgLog: ExtraDebuggingInterest: Yes GraphicsCard: Device [1234:] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Red Hat, Inc. Device [1af4:1100] InstallationDate: Installed on 2019-05-05 (633 days ago) InstallationMedia: Ubuntu 16.04.6 LTS "Xenial Xerus" - Release i386 (20190227.1) Lsusb: Bus 001 Device 004: ID 0627:0001 Adomax Technology Co., Ltd Bus 001 Device 003: ID 0409:55aa NEC Corp. Hub Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: QEMU Standard PC (i440FX + PIIX, 1996) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-45-generic root=UUID=218dfaed-f9ed-4bbe-af1a-aeb8953f26c8 ro quiet splash Renderer: Software SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: rel-1.12.1-0-ga5cab58e9a3f-prebuilt.qemu.org dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-4.0 dmi.modalias: dmi:bvnSeaBIOS:bvrrel-1.12.1-0-ga5cab58e9a3f-prebuilt.qemu.org:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-4.0:cvnQEMU:ct1:cvrpc-i440fx-4.0: dmi.product.name: Standard PC (i440FX + PIIX, 1996) dmi.product.version: pc-i440fx-4.0 dmi.sys.vendor: QEMU version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1 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.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A xserver.bootTime: Thu Jan 28 00:23:55 2021 xserver.configfile: default xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.19.6-1ubuntu4.1~16.04.2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1913493/+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 1914007] Re: RT3290 Bluetooth not finding any device
Yeah I know that it might be a driver issue, but there no other option for me and I have gone through the given bug by you and its quite old and available for old kernal versions and I am a noob in these bugs and all and have no knowlwdge about this. I tried there given solution but I got errors in them and as I said (have no knowledge) don't know how to fix it.BTW Thanks. -- 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/1914007 Title: RT3290 Bluetooth not finding any device Status in bluez package in Ubuntu: New Bug description: Ubuntu :- 20.04 Hello I have RT3290 bluetooth in built and it was not working so I installed its latest driver from github whose version is 3.9.6 . Now its working but its not discoverable to any other device and also not finding any other device. Outout of command :- service bluetooth status ● bluetooth.service - Bluetooth service Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled; vendor pre> Active: active (running) since Sat 2021-01-30 09:49:10 IST; 1h 0min ago Docs: man:bluetoothd(8) Main PID: 1389 (bluetoothd) Status: "Running" Tasks: 1 (limit: 4514) Memory: 2.0M CGroup: /system.slice/bluetooth.service └─1389 /usr/lib/bluetooth/bluetoothd Jan 30 09:49:07 Piyush-X55C systemd[1]: Starting Bluetooth service... Jan 30 09:49:10 Piyush-X55C bluetoothd[1389]: Bluetooth daemon 5.53 Jan 30 09:49:10 Piyush-X55C systemd[1]: Started Bluetooth service. Jan 30 09:49:10 Piyush-X55C bluetoothd[1389]: Starting SDP server Jan 30 09:49:10 Piyush-X55C bluetoothd[1389]: Bluetooth management interface 1.> Jan 30 10:49:34 Piyush-X55C bluetoothd[1389]: Endpoint registered: sender=:1.66> Jan 30 10:49:34 Piyush-X55C bluetoothd[1389]: Endpoint registered: sender=:1.66> lines 1-18/18 (END) Output of command :- sudo btmgmt info Index list with 1 item hci0: Primary controller addr A4:17:31:1D:65:54 version 4 manufacturer 91 class 0x00 supported settings: powered connectable fast-connectable discoverable bondable link-security ssp br/edr debug-keys current settings: powered bondable ssp br/edr name Piyush-X55C Output of command :- bluetoothctl Agent registered [bluetooth]# scan on [bluetooth]# discoverable on [bluetooth]# scan on Failed to start discovery: org.bluez.Error.InProgress [bluetooth]# discoverable on Changing discoverable on succeeded [bluetooth]# Output of command :- sudo btmgmt find Unable to start discovery. status 0x0c (Not Supported) Output of command :- lspci -knn | grep Net -A3; lsusb 02:00.0 Network controller [0280]: Ralink corp. RT3290 Wireless 802.11n 1T/1R PCIe [1814:3290] Subsystem: Foxconn International, Inc. RT3290 Wireless 802.11n 1T/1R PCIe [105b:e055] Kernel driver in use: rt2800pci Kernel modules: rt2800pci Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 003: ID 1bcf:2883 Sunplus Innovation Technology Inc. Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 003 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Output of command :-dmesg | grep -i bluetooth [ 12.851854] Bluetooth: Core ver 2.22 [ 12.851883] Bluetooth: HCI device and connection manager initialized [ 12.851888] Bluetooth: HCI socket layer initialized [ 12.851889] Bluetooth: L2CAP socket layer initialized [ 12.851893] Bluetooth: SCO socket layer initialized [ 67.399550] audit: type=1400 audit(1611909043.091:58): apparmor="DENIED" operation="create" profile="snap.bluez.bluez" pid=875 comm="bluetoothd" family="bluetooth" sock_type="raw" protocol=1 requested_mask="create" denied_mask="create" [ 67.727240] audit: type=1400 audit(1611909043.419:60): apparmor="DENIED" operation="connect" profile="snap.bluez.bluez" name="/run/dbus/system_bus_socket" pid=875 comm="bluetoothd" requested_mask="wr" denied_mask="wr" fsuid=0 ouid=0 [ 67.929889] audit: type=1400 audit(1611909043.619:62): apparmor="DENIED" operation="create" profile="snap.bluez.bluez" pid=1043 comm="bluetoothd" family="bluetooth" sock_type="raw" protocol=1 requested_mask="create" denied_mask="create" [ 67.930261] audit: type=1400 audit(1611909043.623:63): apparmor="DENIED" operation="connect" profile="snap.bluez.bluez" name="/run/dbus/system_bus_socket" pid=1043 comm="bluetoothd" requested_mask="wr" denied_mask="wr" fsuid=0 ouid=0 [ 68.194380] audit: type=1400 audit(1611909043.887:65): apparmor="DENIED" operation="create" prof
[Touch-packages] [Bug 1913859] Re: RT3290 Bluetooth not finding any device
** This bug is no longer a duplicate of bug 1189721 Ralink RT3290 doesn't have a bluetooth driver ** Changed in: bluez (Ubuntu) Status: Invalid => In Progress ** Changed in: bluez (Ubuntu) Assignee: (unassigned) => Piyush Santosh Mhatre (piyush-m) -- 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/1913859 Title: RT3290 Bluetooth not finding any device Status in bluez package in Ubuntu: In Progress Bug description: Ubuntu :- 20.04 Hello I have RT3290 bluetooth in built and it was not working so I installed its latest driver from github whose version is 3.9.6 . Now its working but its not discoverable to any other device and also not finding any other device. Outout of command :- service bluetooth status ● bluetooth.service - Bluetooth service Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled; vendor pre> Active: active (running) since Sat 2021-01-30 09:49:10 IST; 1h 0min ago Docs: man:bluetoothd(8) Main PID: 1389 (bluetoothd) Status: "Running" Tasks: 1 (limit: 4514) Memory: 2.0M CGroup: /system.slice/bluetooth.service └─1389 /usr/lib/bluetooth/bluetoothd Jan 30 09:49:07 Piyush-X55C systemd[1]: Starting Bluetooth service... Jan 30 09:49:10 Piyush-X55C bluetoothd[1389]: Bluetooth daemon 5.53 Jan 30 09:49:10 Piyush-X55C systemd[1]: Started Bluetooth service. Jan 30 09:49:10 Piyush-X55C bluetoothd[1389]: Starting SDP server Jan 30 09:49:10 Piyush-X55C bluetoothd[1389]: Bluetooth management interface 1.> Jan 30 10:49:34 Piyush-X55C bluetoothd[1389]: Endpoint registered: sender=:1.66> Jan 30 10:49:34 Piyush-X55C bluetoothd[1389]: Endpoint registered: sender=:1.66> lines 1-18/18 (END) Output of command :- sudo btmgmt info Index list with 1 item hci0: Primary controller addr A4:17:31:1D:65:54 version 4 manufacturer 91 class 0x00 supported settings: powered connectable fast-connectable discoverable bondable link-security ssp br/edr debug-keys current settings: powered bondable ssp br/edr name Piyush-X55C Output of command :- bluetoothctl Agent registered [bluetooth]# scan on [bluetooth]# discoverable on [bluetooth]# scan on Failed to start discovery: org.bluez.Error.InProgress [bluetooth]# discoverable on Changing discoverable on succeeded [bluetooth]# Output of command :- sudo btmgmt find Unable to start discovery. status 0x0c (Not Supported) Output of command :- lspci -knn | grep Net -A3; lsusb 02:00.0 Network controller [0280]: Ralink corp. RT3290 Wireless 802.11n 1T/1R PCIe [1814:3290] Subsystem: Foxconn International, Inc. RT3290 Wireless 802.11n 1T/1R PCIe [105b:e055] Kernel driver in use: rt2800pci Kernel modules: rt2800pci Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 003: ID 1bcf:2883 Sunplus Innovation Technology Inc. Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 003 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Output of command :-dmesg | grep -i bluetooth [ 12.851854] Bluetooth: Core ver 2.22 [ 12.851883] Bluetooth: HCI device and connection manager initialized [ 12.851888] Bluetooth: HCI socket layer initialized [ 12.851889] Bluetooth: L2CAP socket layer initialized [ 12.851893] Bluetooth: SCO socket layer initialized [ 67.399550] audit: type=1400 audit(1611909043.091:58): apparmor="DENIED" operation="create" profile="snap.bluez.bluez" pid=875 comm="bluetoothd" family="bluetooth" sock_type="raw" protocol=1 requested_mask="create" denied_mask="create" [ 67.727240] audit: type=1400 audit(1611909043.419:60): apparmor="DENIED" operation="connect" profile="snap.bluez.bluez" name="/run/dbus/system_bus_socket" pid=875 comm="bluetoothd" requested_mask="wr" denied_mask="wr" fsuid=0 ouid=0 [ 67.929889] audit: type=1400 audit(1611909043.619:62): apparmor="DENIED" operation="create" profile="snap.bluez.bluez" pid=1043 comm="bluetoothd" family="bluetooth" sock_type="raw" protocol=1 requested_mask="create" denied_mask="create" [ 67.930261] audit: type=1400 audit(1611909043.623:63): apparmor="DENIED" operation="connect" profile="snap.bluez.bluez" name="/run/dbus/system_bus_socket" pid=1043 comm="bluetoothd" requested_mask="wr" denied_mask="wr" fsuid=0 ouid=0 [ 68.194380] audit: type=1400 audit(1611909043.887:65): apparmor="DENIED" operation="create" profile="snap.bluez.bluez" pid=1102 comm="bluetoothd" family="bluetooth" sock_type=
[Touch-packages] [Bug 1914007] Re: RT3290 Bluetooth not finding any device
** This bug is no longer a duplicate of bug 1189721 Ralink RT3290 doesn't have a bluetooth driver -- 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/1914007 Title: RT3290 Bluetooth not finding any device Status in bluez package in Ubuntu: New Bug description: Ubuntu :- 20.04 Hello I have RT3290 bluetooth in built and it was not working so I installed its latest driver from github whose version is 3.9.6 . Now its working but its not discoverable to any other device and also not finding any other device. Outout of command :- service bluetooth status ● bluetooth.service - Bluetooth service Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled; vendor pre> Active: active (running) since Sat 2021-01-30 09:49:10 IST; 1h 0min ago Docs: man:bluetoothd(8) Main PID: 1389 (bluetoothd) Status: "Running" Tasks: 1 (limit: 4514) Memory: 2.0M CGroup: /system.slice/bluetooth.service └─1389 /usr/lib/bluetooth/bluetoothd Jan 30 09:49:07 Piyush-X55C systemd[1]: Starting Bluetooth service... Jan 30 09:49:10 Piyush-X55C bluetoothd[1389]: Bluetooth daemon 5.53 Jan 30 09:49:10 Piyush-X55C systemd[1]: Started Bluetooth service. Jan 30 09:49:10 Piyush-X55C bluetoothd[1389]: Starting SDP server Jan 30 09:49:10 Piyush-X55C bluetoothd[1389]: Bluetooth management interface 1.> Jan 30 10:49:34 Piyush-X55C bluetoothd[1389]: Endpoint registered: sender=:1.66> Jan 30 10:49:34 Piyush-X55C bluetoothd[1389]: Endpoint registered: sender=:1.66> lines 1-18/18 (END) Output of command :- sudo btmgmt info Index list with 1 item hci0: Primary controller addr A4:17:31:1D:65:54 version 4 manufacturer 91 class 0x00 supported settings: powered connectable fast-connectable discoverable bondable link-security ssp br/edr debug-keys current settings: powered bondable ssp br/edr name Piyush-X55C Output of command :- bluetoothctl Agent registered [bluetooth]# scan on [bluetooth]# discoverable on [bluetooth]# scan on Failed to start discovery: org.bluez.Error.InProgress [bluetooth]# discoverable on Changing discoverable on succeeded [bluetooth]# Output of command :- sudo btmgmt find Unable to start discovery. status 0x0c (Not Supported) Output of command :- lspci -knn | grep Net -A3; lsusb 02:00.0 Network controller [0280]: Ralink corp. RT3290 Wireless 802.11n 1T/1R PCIe [1814:3290] Subsystem: Foxconn International, Inc. RT3290 Wireless 802.11n 1T/1R PCIe [105b:e055] Kernel driver in use: rt2800pci Kernel modules: rt2800pci Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 003: ID 1bcf:2883 Sunplus Innovation Technology Inc. Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 003 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Output of command :-dmesg | grep -i bluetooth [ 12.851854] Bluetooth: Core ver 2.22 [ 12.851883] Bluetooth: HCI device and connection manager initialized [ 12.851888] Bluetooth: HCI socket layer initialized [ 12.851889] Bluetooth: L2CAP socket layer initialized [ 12.851893] Bluetooth: SCO socket layer initialized [ 67.399550] audit: type=1400 audit(1611909043.091:58): apparmor="DENIED" operation="create" profile="snap.bluez.bluez" pid=875 comm="bluetoothd" family="bluetooth" sock_type="raw" protocol=1 requested_mask="create" denied_mask="create" [ 67.727240] audit: type=1400 audit(1611909043.419:60): apparmor="DENIED" operation="connect" profile="snap.bluez.bluez" name="/run/dbus/system_bus_socket" pid=875 comm="bluetoothd" requested_mask="wr" denied_mask="wr" fsuid=0 ouid=0 [ 67.929889] audit: type=1400 audit(1611909043.619:62): apparmor="DENIED" operation="create" profile="snap.bluez.bluez" pid=1043 comm="bluetoothd" family="bluetooth" sock_type="raw" protocol=1 requested_mask="create" denied_mask="create" [ 67.930261] audit: type=1400 audit(1611909043.623:63): apparmor="DENIED" operation="connect" profile="snap.bluez.bluez" name="/run/dbus/system_bus_socket" pid=1043 comm="bluetoothd" requested_mask="wr" denied_mask="wr" fsuid=0 ouid=0 [ 68.194380] audit: type=1400 audit(1611909043.887:65): apparmor="DENIED" operation="create" profile="snap.bluez.bluez" pid=1102 comm="bluetoothd" family="bluetooth" sock_type="raw" protocol=1 requested_mask="create" denied_mask="create" [ 68.194710] audit: type=1400 audit(1611909043.887:66): apparmor="DENIED" operation="connect" profile="snap.bluez.bluez" nam
[Touch-packages] [Bug 1914007] Re: RT3290 Bluetooth not finding any device
Thanks for reporting the bug again. Unfortunately because you're using a driver (rtbth kernel module) that's not from Ubuntu, we can't support it. So that makes this bug 'Invalid'. I can see however that you didn't get much choice because it seems Ubuntu doesn't offer a driver for RTL3290 bluetooth. This issue is already covered by bug 1189721 so I will group it there. ** This bug has been marked a duplicate of bug 1189721 Ralink RT3290 doesn't have a bluetooth driver -- 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/1914007 Title: RT3290 Bluetooth not finding any device Status in bluez package in Ubuntu: New Bug description: Ubuntu :- 20.04 Hello I have RT3290 bluetooth in built and it was not working so I installed its latest driver from github whose version is 3.9.6 . Now its working but its not discoverable to any other device and also not finding any other device. Outout of command :- service bluetooth status ● bluetooth.service - Bluetooth service Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled; vendor pre> Active: active (running) since Sat 2021-01-30 09:49:10 IST; 1h 0min ago Docs: man:bluetoothd(8) Main PID: 1389 (bluetoothd) Status: "Running" Tasks: 1 (limit: 4514) Memory: 2.0M CGroup: /system.slice/bluetooth.service └─1389 /usr/lib/bluetooth/bluetoothd Jan 30 09:49:07 Piyush-X55C systemd[1]: Starting Bluetooth service... Jan 30 09:49:10 Piyush-X55C bluetoothd[1389]: Bluetooth daemon 5.53 Jan 30 09:49:10 Piyush-X55C systemd[1]: Started Bluetooth service. Jan 30 09:49:10 Piyush-X55C bluetoothd[1389]: Starting SDP server Jan 30 09:49:10 Piyush-X55C bluetoothd[1389]: Bluetooth management interface 1.> Jan 30 10:49:34 Piyush-X55C bluetoothd[1389]: Endpoint registered: sender=:1.66> Jan 30 10:49:34 Piyush-X55C bluetoothd[1389]: Endpoint registered: sender=:1.66> lines 1-18/18 (END) Output of command :- sudo btmgmt info Index list with 1 item hci0: Primary controller addr A4:17:31:1D:65:54 version 4 manufacturer 91 class 0x00 supported settings: powered connectable fast-connectable discoverable bondable link-security ssp br/edr debug-keys current settings: powered bondable ssp br/edr name Piyush-X55C Output of command :- bluetoothctl Agent registered [bluetooth]# scan on [bluetooth]# discoverable on [bluetooth]# scan on Failed to start discovery: org.bluez.Error.InProgress [bluetooth]# discoverable on Changing discoverable on succeeded [bluetooth]# Output of command :- sudo btmgmt find Unable to start discovery. status 0x0c (Not Supported) Output of command :- lspci -knn | grep Net -A3; lsusb 02:00.0 Network controller [0280]: Ralink corp. RT3290 Wireless 802.11n 1T/1R PCIe [1814:3290] Subsystem: Foxconn International, Inc. RT3290 Wireless 802.11n 1T/1R PCIe [105b:e055] Kernel driver in use: rt2800pci Kernel modules: rt2800pci Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 003: ID 1bcf:2883 Sunplus Innovation Technology Inc. Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 003 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Output of command :-dmesg | grep -i bluetooth [ 12.851854] Bluetooth: Core ver 2.22 [ 12.851883] Bluetooth: HCI device and connection manager initialized [ 12.851888] Bluetooth: HCI socket layer initialized [ 12.851889] Bluetooth: L2CAP socket layer initialized [ 12.851893] Bluetooth: SCO socket layer initialized [ 67.399550] audit: type=1400 audit(1611909043.091:58): apparmor="DENIED" operation="create" profile="snap.bluez.bluez" pid=875 comm="bluetoothd" family="bluetooth" sock_type="raw" protocol=1 requested_mask="create" denied_mask="create" [ 67.727240] audit: type=1400 audit(1611909043.419:60): apparmor="DENIED" operation="connect" profile="snap.bluez.bluez" name="/run/dbus/system_bus_socket" pid=875 comm="bluetoothd" requested_mask="wr" denied_mask="wr" fsuid=0 ouid=0 [ 67.929889] audit: type=1400 audit(1611909043.619:62): apparmor="DENIED" operation="create" profile="snap.bluez.bluez" pid=1043 comm="bluetoothd" family="bluetooth" sock_type="raw" protocol=1 requested_mask="create" denied_mask="create" [ 67.930261] audit: type=1400 audit(1611909043.623:63): apparmor="DENIED" operation="connect" profile="snap.bluez.bluez" name="/run/dbus/system_bus_socket" pid=1043 comm="bluetoothd" requested_mask="wr" denied_mask="wr" fsuid=0 ouid=0
[Touch-packages] [Bug 1913859] Re: RT3290 Bluetooth not finding any device
** This bug is no longer a duplicate of bug 1914007 RT3290 Bluetooth not finding any device ** This bug has been marked a duplicate of bug 1189721 Ralink RT3290 doesn't have a bluetooth driver -- 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/1913859 Title: RT3290 Bluetooth not finding any device Status in bluez package in Ubuntu: In Progress Bug description: Ubuntu :- 20.04 Hello I have RT3290 bluetooth in built and it was not working so I installed its latest driver from github whose version is 3.9.6 . Now its working but its not discoverable to any other device and also not finding any other device. Outout of command :- service bluetooth status ● bluetooth.service - Bluetooth service Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled; vendor pre> Active: active (running) since Sat 2021-01-30 09:49:10 IST; 1h 0min ago Docs: man:bluetoothd(8) Main PID: 1389 (bluetoothd) Status: "Running" Tasks: 1 (limit: 4514) Memory: 2.0M CGroup: /system.slice/bluetooth.service └─1389 /usr/lib/bluetooth/bluetoothd Jan 30 09:49:07 Piyush-X55C systemd[1]: Starting Bluetooth service... Jan 30 09:49:10 Piyush-X55C bluetoothd[1389]: Bluetooth daemon 5.53 Jan 30 09:49:10 Piyush-X55C systemd[1]: Started Bluetooth service. Jan 30 09:49:10 Piyush-X55C bluetoothd[1389]: Starting SDP server Jan 30 09:49:10 Piyush-X55C bluetoothd[1389]: Bluetooth management interface 1.> Jan 30 10:49:34 Piyush-X55C bluetoothd[1389]: Endpoint registered: sender=:1.66> Jan 30 10:49:34 Piyush-X55C bluetoothd[1389]: Endpoint registered: sender=:1.66> lines 1-18/18 (END) Output of command :- sudo btmgmt info Index list with 1 item hci0: Primary controller addr A4:17:31:1D:65:54 version 4 manufacturer 91 class 0x00 supported settings: powered connectable fast-connectable discoverable bondable link-security ssp br/edr debug-keys current settings: powered bondable ssp br/edr name Piyush-X55C Output of command :- bluetoothctl Agent registered [bluetooth]# scan on [bluetooth]# discoverable on [bluetooth]# scan on Failed to start discovery: org.bluez.Error.InProgress [bluetooth]# discoverable on Changing discoverable on succeeded [bluetooth]# Output of command :- sudo btmgmt find Unable to start discovery. status 0x0c (Not Supported) Output of command :- lspci -knn | grep Net -A3; lsusb 02:00.0 Network controller [0280]: Ralink corp. RT3290 Wireless 802.11n 1T/1R PCIe [1814:3290] Subsystem: Foxconn International, Inc. RT3290 Wireless 802.11n 1T/1R PCIe [105b:e055] Kernel driver in use: rt2800pci Kernel modules: rt2800pci Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 003: ID 1bcf:2883 Sunplus Innovation Technology Inc. Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 003 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Output of command :-dmesg | grep -i bluetooth [ 12.851854] Bluetooth: Core ver 2.22 [ 12.851883] Bluetooth: HCI device and connection manager initialized [ 12.851888] Bluetooth: HCI socket layer initialized [ 12.851889] Bluetooth: L2CAP socket layer initialized [ 12.851893] Bluetooth: SCO socket layer initialized [ 67.399550] audit: type=1400 audit(1611909043.091:58): apparmor="DENIED" operation="create" profile="snap.bluez.bluez" pid=875 comm="bluetoothd" family="bluetooth" sock_type="raw" protocol=1 requested_mask="create" denied_mask="create" [ 67.727240] audit: type=1400 audit(1611909043.419:60): apparmor="DENIED" operation="connect" profile="snap.bluez.bluez" name="/run/dbus/system_bus_socket" pid=875 comm="bluetoothd" requested_mask="wr" denied_mask="wr" fsuid=0 ouid=0 [ 67.929889] audit: type=1400 audit(1611909043.619:62): apparmor="DENIED" operation="create" profile="snap.bluez.bluez" pid=1043 comm="bluetoothd" family="bluetooth" sock_type="raw" protocol=1 requested_mask="create" denied_mask="create" [ 67.930261] audit: type=1400 audit(1611909043.623:63): apparmor="DENIED" operation="connect" profile="snap.bluez.bluez" name="/run/dbus/system_bus_socket" pid=1043 comm="bluetoothd" requested_mask="wr" denied_mask="wr" fsuid=0 ouid=0 [ 68.194380] audit: type=1400 audit(1611909043.887:65): apparmor="DENIED" operation="create" profile="snap.bluez.bluez" pid=1102 comm="bluetoothd" family="bluetooth" sock_type="raw" protocol=1 requested_mask="create" denied_mask="create"
[Touch-packages] [Bug 1913859] Re: RT3290 Bluetooth not finding any device
*** This bug is a duplicate of bug 1914007 *** https://bugs.launchpad.net/bugs/1914007 ** This bug has been marked a duplicate of bug 1914007 RT3290 Bluetooth not finding any device -- 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/1913859 Title: RT3290 Bluetooth not finding any device Status in bluez package in Ubuntu: Invalid Bug description: Ubuntu :- 20.04 Hello I have RT3290 bluetooth in built and it was not working so I installed its latest driver from github whose version is 3.9.6 . Now its working but its not discoverable to any other device and also not finding any other device. Outout of command :- service bluetooth status ● bluetooth.service - Bluetooth service Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled; vendor pre> Active: active (running) since Sat 2021-01-30 09:49:10 IST; 1h 0min ago Docs: man:bluetoothd(8) Main PID: 1389 (bluetoothd) Status: "Running" Tasks: 1 (limit: 4514) Memory: 2.0M CGroup: /system.slice/bluetooth.service └─1389 /usr/lib/bluetooth/bluetoothd Jan 30 09:49:07 Piyush-X55C systemd[1]: Starting Bluetooth service... Jan 30 09:49:10 Piyush-X55C bluetoothd[1389]: Bluetooth daemon 5.53 Jan 30 09:49:10 Piyush-X55C systemd[1]: Started Bluetooth service. Jan 30 09:49:10 Piyush-X55C bluetoothd[1389]: Starting SDP server Jan 30 09:49:10 Piyush-X55C bluetoothd[1389]: Bluetooth management interface 1.> Jan 30 10:49:34 Piyush-X55C bluetoothd[1389]: Endpoint registered: sender=:1.66> Jan 30 10:49:34 Piyush-X55C bluetoothd[1389]: Endpoint registered: sender=:1.66> lines 1-18/18 (END) Output of command :- sudo btmgmt info Index list with 1 item hci0: Primary controller addr A4:17:31:1D:65:54 version 4 manufacturer 91 class 0x00 supported settings: powered connectable fast-connectable discoverable bondable link-security ssp br/edr debug-keys current settings: powered bondable ssp br/edr name Piyush-X55C Output of command :- bluetoothctl Agent registered [bluetooth]# scan on [bluetooth]# discoverable on [bluetooth]# scan on Failed to start discovery: org.bluez.Error.InProgress [bluetooth]# discoverable on Changing discoverable on succeeded [bluetooth]# Output of command :- sudo btmgmt find Unable to start discovery. status 0x0c (Not Supported) Output of command :- lspci -knn | grep Net -A3; lsusb 02:00.0 Network controller [0280]: Ralink corp. RT3290 Wireless 802.11n 1T/1R PCIe [1814:3290] Subsystem: Foxconn International, Inc. RT3290 Wireless 802.11n 1T/1R PCIe [105b:e055] Kernel driver in use: rt2800pci Kernel modules: rt2800pci Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 003: ID 1bcf:2883 Sunplus Innovation Technology Inc. Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 003 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Output of command :-dmesg | grep -i bluetooth [ 12.851854] Bluetooth: Core ver 2.22 [ 12.851883] Bluetooth: HCI device and connection manager initialized [ 12.851888] Bluetooth: HCI socket layer initialized [ 12.851889] Bluetooth: L2CAP socket layer initialized [ 12.851893] Bluetooth: SCO socket layer initialized [ 67.399550] audit: type=1400 audit(1611909043.091:58): apparmor="DENIED" operation="create" profile="snap.bluez.bluez" pid=875 comm="bluetoothd" family="bluetooth" sock_type="raw" protocol=1 requested_mask="create" denied_mask="create" [ 67.727240] audit: type=1400 audit(1611909043.419:60): apparmor="DENIED" operation="connect" profile="snap.bluez.bluez" name="/run/dbus/system_bus_socket" pid=875 comm="bluetoothd" requested_mask="wr" denied_mask="wr" fsuid=0 ouid=0 [ 67.929889] audit: type=1400 audit(1611909043.619:62): apparmor="DENIED" operation="create" profile="snap.bluez.bluez" pid=1043 comm="bluetoothd" family="bluetooth" sock_type="raw" protocol=1 requested_mask="create" denied_mask="create" [ 67.930261] audit: type=1400 audit(1611909043.623:63): apparmor="DENIED" operation="connect" profile="snap.bluez.bluez" name="/run/dbus/system_bus_socket" pid=1043 comm="bluetoothd" requested_mask="wr" denied_mask="wr" fsuid=0 ouid=0 [ 68.194380] audit: type=1400 audit(1611909043.887:65): apparmor="DENIED" operation="create" profile="snap.bluez.bluez" pid=1102 comm="bluetoothd" family="bluetooth" sock_type="raw" protocol=1 requested_mask="create" denied_mask="create" [ 68.194