[Touch-packages] [Bug 1962453] Re: Apply default TTL to records obtained from getaddrinfo()
Hi Utkarsh, Is the backport taken for all the above versions as well? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to keyutils in Ubuntu. https://bugs.launchpad.net/bugs/1962453 Title: Apply default TTL to records obtained from getaddrinfo() Status in keyutils package in Ubuntu: Fix Released Status in keyutils source package in Bionic: Fix Released Status in keyutils source package in Focal: Incomplete Status in keyutils source package in Impish: Incomplete Bug description: [Impact] There's a strong dependency for cifs.ko (and nfs.ko) on keyutils for DNS resolution. The keyutils package contains the userspace utility to update the kernel keyring with the DNS mapping to IP address. Prior to 1.6.2, this utility may erroneously set unlimited lifetime for this keyring in the kernel. [Test plan] === 1. Create a file share on an SMB server (can be a samba server) with two IP addresses. Make sure that FQDN of the server resolves to one of these addresses. 2. mount the created share on the cifs client using the FQDN for the server. Make sure that the mount point is accessible. 3. Using the ss command on the client, to kill the sockets that connect to the server: sudo ss -K dport :445 4. Now update the DNS entry to make sure that the server FQDN now resolves to the second IP address of the server. Make sure that nslookup on the client now resolves to the new IP address. 5. Repeat step 3 to kill the sockets that connect to server to force re-connection again. Without the fix, after step 5, with the "ss -t" command, you'll see that the client has reconnected to the old IP address, even when DNS lookups return the new IP. With the fix (after a reboot of the client machine to make sure that kernel keys are refreshed), you'll see that the client reconnects to the new IP address. The bug is due to unlimited lifetime set by key.dns_resolver (which is part of keyutils package). As a result, even if IP address for the DNS entries change, the kernel filesystems would continue to use old IP address, due to the cached keys. This issue causes clients to misbehave when Azure Files service endpoints move to a different cluster. [Where problems could occur] Address records obtained from getaddrinfo() don't come with any TTL information, even if they're obtained from the DNS, so if someone is relying on this particularly, might face some problem/regression but I don't think they would face that as it would still be highly configurable. [Other information] === This request is essentially from one of our cloud partners and they're highly affected by this. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/keyutils/+bug/1962453/+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 1971523] [NEW] Static build does not work for libmnl (-lmnl)
Public bug reported: Example; # gcc -o /tmp/hello /tmp/hello.c -lmnl (dynamic libs work) # gcc -static -o /tmp/hello /tmp/hello.c -lmnl /usr/bin/ld: cannot find -lmnl: No such file or directory My program uses both -lmnl and -lnetfilter_queue and in Ubuntu 20.04 the -lnetfilter_queue did not work and -lmnl worked for static builds. In Ubuntu 22.04 the problem is reversed, -lnetfilter_queue works but -lmnl doesn't for static builds. This is very awkward during the transition 20.04->22.04 when both should be supported. I compensated in Ubuntu 20.04 by building netfilter_queue locally; https://github.com/Nordix/nfqueue-loadbalancer#build ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: libmnl0:amd64 1.0.4-3build2 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Uname: Linux 5.15.0-27-generic x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: XFCE Date: Wed May 4 07:33:26 2022 InstallationDate: Installed on 2018-09-07 (1334 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: libmnl UpgradeStatus: Upgraded to jammy on 2022-05-01 (2 days ago) ** Affects: libmnl (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libmnl in Ubuntu. https://bugs.launchpad.net/bugs/1971523 Title: Static build does not work for libmnl (-lmnl) Status in libmnl package in Ubuntu: New Bug description: Example; # gcc -o /tmp/hello /tmp/hello.c -lmnl (dynamic libs work) # gcc -static -o /tmp/hello /tmp/hello.c -lmnl /usr/bin/ld: cannot find -lmnl: No such file or directory My program uses both -lmnl and -lnetfilter_queue and in Ubuntu 20.04 the -lnetfilter_queue did not work and -lmnl worked for static builds. In Ubuntu 22.04 the problem is reversed, -lnetfilter_queue works but -lmnl doesn't for static builds. This is very awkward during the transition 20.04->22.04 when both should be supported. I compensated in Ubuntu 20.04 by building netfilter_queue locally; https://github.com/Nordix/nfqueue-loadbalancer#build ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: libmnl0:amd64 1.0.4-3build2 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Uname: Linux 5.15.0-27-generic x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: XFCE Date: Wed May 4 07:33:26 2022 InstallationDate: Installed on 2018-09-07 (1334 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: libmnl UpgradeStatus: Upgraded to jammy on 2022-05-01 (2 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libmnl/+bug/1971523/+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 1971460] Re: Xorg and Wayland freeze
Thanks for the bug report. Next time a freeze happens please: 1. Wait 10 seconds. 2. Reboot. 3. Run: journalctl -b-1 > prevboot.txt 4. Attach the resulting text file here. 5. Also check for crashes by following https://wiki.ubuntu.com/Bugs/Responses#Missing_a_crash_report_or_having_a_.crash_attachment ** Tags added: amdgpu ** Summary changed: - Xorg and Wayland freeze + [amdgpu] System freezes coming out from suspension or randomly from screen power save ** 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/1971460 Title: [amdgpu] System freezes coming out from suspension or randomly from screen power save Status in Ubuntu: Incomplete Bug description: I've Ubuntu 22.04 with Wayland and Sapphire Radeon RX 6600 with Xiaomi 34" curved gaming monitor capable of 3440x1440 @144,00hz. Using refresh of 120hz or 144hz, the system freezes coming out from suspension or randomly from screen power save. Setting @60hz it's more stable. It seems something related to wrong Modeline for this VGA and monitor resolution/frequencies. The problem is with both DP or HDMI cable. With HDMI it supports only 99,99hz I had no problem with the provious HP RX 460 HanSolo or XFX GTX 1060 3GB with proprietary nVidia drivers. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Uname: Linux 5.15.0-27-generic x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 BootLog: Error: [Errno 13] Permesso negato: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue May 3 18:29:05 2022 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu DkmsStatus: virtualbox/6.1.32, 5.15.0-25-generic, x86_64: installed virtualbox/6.1.32, 5.15.0-27-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GpuHangFrequency: Several times a day GpuHangReproducibility: Yes, I can easily reproduce it GpuHangStarted: Immediately after installing this version of Ubuntu GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Navi 23 [Radeon RX 6600/6600 XT/6600M] [1002:73ff] (rev c7) (prog-if 00 [VGA controller]) Subsystem: Sapphire Technology Limited Navi 23 [Radeon RX 6600/6600 XT/6600M] [1da2:e447] InstallationDate: Installed on 2022-04-23 (9 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: System manufacturer System Product Name ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-27-generic root=UUID=be1c4139-f2bc-472b-87c1-099f2be97b1a ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/25/2022 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3604 dmi.board.asset.tag: Default string dmi.board.name: TUF B450M-PRO GAMING dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3604:bd02/25/2022:br5.17:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnTUFB450M-PROGAMING:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.110-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.1-1ubuntu2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1971460/+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 1802483] Autopkgtest regression report (libnotify/0.7.9-3ubuntu5.22.04.1)
All autopkgtests for the newly accepted libnotify (0.7.9-3ubuntu5.22.04.1) for jammy have finished running. The following regressions have been reported in tests triggered by the package: firewalld/1.1.1-1ubuntu1 (amd64) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/jammy/update_excuses.html#libnotify [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libnotify in Ubuntu. https://bugs.launchpad.net/bugs/1802483 Title: Notifications emitted by a snap with local files or desktop files use wrong namespace Status in libnotify package in Ubuntu: Fix Released Status in libnotify source package in Focal: In Progress Status in libnotify source package in Jammy: Fix Committed Bug description: As can be tested using this example snap: - https://github.com/3v1n0/notify-send-test-snap Basically the icons are referenced using absolute paths in snap environment, while they should be readapted so that they depend on $SNAP location. As we do with appindicators and libunity emblems. [ Impact ] Icons sonuds and desktop files referenced by a snapped app using notifications aren't exposed to the desktop in absolute paths [ Test case ] Build the test snap (or install it from the attached files to this bug): git clone https://github.com/3v1n0/notify-send-test-snap snapcraft prime snap try prime To use the pre-built snap (https://bugs.launchpad.net/ubuntu/+source/libnotify/+bug/1802483/comments/7) snap install --dangerous notify-send-test-snap_*.snap Check that icons are shown when launching: notify-send-test-snap notify-send-test-snap.image-path notify-send-test-snap.image-uri Ensure that desktop entry is correctly sent, monitoring the dbus session: In a terminal: dbus-monitor --session --monitor "interface='org.freedesktop.Notifications'" In the other: notify-send-test-snap.desktop-entry notify-send-test-snap.desktop-entry-explicit-id notify-send-test-snap.desktop-entry-explicit-file-name notify-send-test-snap.desktop-entry-explicit-path notify-send-test-snap.desktop-entry-explicit-uri notify-send-test-snap.desktop-entry-explicit-snapped-uri The `desktop-entry` value sent to dbus should be either: - A `notify-send-test-snap_`-prefixed desktop ID - A .desktop file path (readable from both inside and outside the snap) - A .desktop file uri (readable from both inside and outside the snap) [ Regression potential ] Normal applications that are run with a SNAP environment variable set, might use wrong paths for files or desktop file To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libnotify/+bug/1802483/+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 1970647] Autopkgtest regression report (libnotify/0.7.9-3ubuntu5.22.04.1)
All autopkgtests for the newly accepted libnotify (0.7.9-3ubuntu5.22.04.1) for jammy have finished running. The following regressions have been reported in tests triggered by the package: firewalld/1.1.1-1ubuntu1 (amd64) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/jammy/update_excuses.html#libnotify [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libnotify in Ubuntu. https://bugs.launchpad.net/bugs/1970647 Title: notify-send exit code doesn't match result Status in libnotify package in Ubuntu: Fix Released Status in libnotify source package in Focal: In Progress Status in libnotify source package in Jammy: Fix Committed Bug description: No error exit code is returned by notify-send on failure [ Test case ] 1. Run: jhbuild run env DBUS_SESSION_BUS_ADDRESS= notify-send foo bar || echo error 2. In a terminal "error" should be printed [ Regression potential ] Programs relying on notify-send may have errors when they did not. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libnotify/+bug/1970647/+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 1971481] Re: root pass on KDE discover software source error
** Summary changed: - root pass on discover sofware source error + root pass on KDE discover software source error ** Package changed: xorg (Ubuntu) => 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/1971481 Title: root pass on KDE discover software source error Status in Ubuntu: New Bug description: STEPS TO REPRODUCE 1. Go to Discover 2. Go to Preferences 3. Click on Software Sources and put root pass OBSERVED RESULT Error always to try enter in software sources EXPECTED RESULT Open software sources and manage all preferences SOFTWARE/OS VERSIONS Linux/KDE Plasma: Kubuntu 22.04 KDE Plasma Version: 5.24.4 ADDITIONAL INFORMATION It only is happened on Kubuntu 22.04. If you use Kubuntu backport from Kubuntu 21.10 it runs perfectly ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Uname: Linux 5.15.0-27-generic x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 BootLog: Error: [Errno 13] Permiso denegado: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: KDE Date: Tue May 3 20:57:25 2022 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: I just need to know a workaround GraphicsCard: VMware SVGA II Adapter [15ad:0405] (prog-if 00 [VGA controller]) Subsystem: VMware SVGA II Adapter [15ad:0405] InstallationDate: Installed on 2022-04-23 (9 days ago) InstallationMedia: Kubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) Lsusb: Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Lsusb-t: /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ohci-pci/12p, 12M |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M MachineType: innotek GmbH VirtualBox ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-27-generic root=UUID=0a53b0d0-ec7a-4a08-b211-4b5411d87fa9 ro quiet splash SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/01/2006 dmi.bios.vendor: innotek GmbH dmi.bios.version: VirtualBox dmi.board.name: VirtualBox dmi.board.vendor: Oracle Corporation dmi.board.version: 1.2 dmi.chassis.type: 1 dmi.chassis.vendor: Oracle Corporation dmi.modalias: dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:sku: dmi.product.family: Virtual Machine dmi.product.name: VirtualBox dmi.product.version: 1.2 dmi.sys.vendor: innotek GmbH version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.110-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.1-1ubuntu2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1971481/+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 1971158] Re: ssh connect to server stop on "SSH2_MSG_KEXINIT sent"
Could the problem be something else? Adding the old algorithm to the configuration did not help me. Example in config Host old-host HostkeyAlgorithms +ssh-rsa PubkeyAcceptedAlgorithms +ssh-rsa And try with cli options ssh -vvv -X -oPubkeyAcceptedAlgorithms=+ssh-rsa -oHostkeyAlgorithms=+ssh-rsa dual debug1: load_hostkeys: fopen /etc/ssh/ssh_known_hosts2: No such file or directory debug3: order_hostkeyalgs: no algorithms matched; accept original debug3: send packet: type 20 debug1: SSH2_MSG_KEXINIT sent -- 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/1971158 Title: ssh connect to server stop on "SSH2_MSG_KEXINIT sent" Status in openssh package in Ubuntu: Won't Fix Bug description: After upgrade on Ubuntu 22.04 i can't connect to several servers. Connecting stopped on SSH2_MSG_KEXINIT sent ``` ssh -vvv -o KexAlgorithms=diffie-hellman-group-exchange-sha256 -oHostKeyAlgorithms=+ssh-rsa -X vld@sansa OpenSSH_8.9p1 Ubuntu-3, OpenSSL 3.0.2 15 Mar 2022 debug1: Reading configuration data /home/ruslan/.ssh/config debug3: kex names ok: [diffie-hellman-group1-sha1] debug3: kex names ok: [diffie-hellman-group-exchange-sha256,diffie-hellman-group-exchange-sha1,diffie-hellman-group14-sha1,diffie-hellman-group1-sha1] debug3: kex names ok: [diffie-hellman-group1-sha1] debug1: Reading configuration data /etc/ssh/ssh_config debug1: /etc/ssh/ssh_config line 19: include /etc/ssh/ssh_config.d/*.conf matched no files debug1: /etc/ssh/ssh_config line 21: Applying options for * debug3: expanded UserKnownHostsFile '~/.ssh/known_hosts' -> '/home/ruslan/.ssh/known_hosts' debug3: expanded UserKnownHostsFile '~/.ssh/known_hosts2' -> '/home/ruslan/.ssh/known_hosts2' debug2: resolving "sansa" port 22 debug3: resolve_host: lookup sansa:22 debug3: ssh_connect_direct: entering debug1: Connecting to sansa [172.16.xx.xx] port 22. debug3: set_sock_tos: set socket 3 IP_TOS 0x10 debug1: Connection established. debug1: identity file /home/ruslan/.ssh/id_rsa type -1 debug1: identity file /home/ruslan/.ssh/id_rsa-cert type -1 debug1: identity file /home/ruslan/.ssh/id_ecdsa type -1 debug1: identity file /home/ruslan/.ssh/id_ecdsa-cert type -1 debug1: identity file /home/ruslan/.ssh/id_ecdsa_sk type -1 debug1: identity file /home/ruslan/.ssh/id_ecdsa_sk-cert type -1 debug1: identity file /home/ruslan/.ssh/id_ed25519 type -1 debug1: identity file /home/ruslan/.ssh/id_ed25519-cert type -1 debug1: identity file /home/ruslan/.ssh/id_ed25519_sk type -1 debug1: identity file /home/ruslan/.ssh/id_ed25519_sk-cert type -1 debug1: identity file /home/ruslan/.ssh/id_xmss type -1 debug1: identity file /home/ruslan/.ssh/id_xmss-cert type -1 debug1: identity file /home/ruslan/.ssh/id_dsa type -1 debug1: identity file /home/ruslan/.ssh/id_dsa-cert type -1 debug1: Local version string SSH-2.0-OpenSSH_8.9p1 Ubuntu-3 debug1: Remote protocol version 2.0, remote software version OpenSSH_5.3 debug1: compat_banner: match: OpenSSH_5.3 pat OpenSSH_5* compat 0x0c02 debug2: fd 3 setting O_NONBLOCK debug1: Authenticating to sansa:22 as 'vld' debug1: load_hostkeys: fopen /etc/ssh/ssh_known_hosts2: No such file or directory debug3: order_hostkeyalgs: no algorithms matched; accept original debug3: send packet: type 20 debug1: SSH2_MSG_KEXINIT sent ``` I'm checking connection on old version Ubuntu 20.04, it's working. Remote server use KexAlgorithms=diffie-hellman-group-exchange-sha256 and HostKeyAlgorithms=ssh-rsa On Ubuntu 21.04 ssh was work. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1971158/+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 1966179] Re: The airplane hotkey does not work on lots of HP platforms
@Brian, Thanks for your attention. As comment#8 from LP#1955997: ``` evdev:name:Intel HID events:dmi:bvn*:bvr*:bd*:svnHP*:pnHPZBookStudio16.0InchMobileWorkstationPC:pvr* ``` Unfortunately, ``` In the mail from HP (please see the lp1966179), HP also confirmed the previous two platforms' dmi string need to adjust. pnHPZBookFury16G9MobileWorkstationPC pnHPZBookStudio16inchG9MobileWorkstationPC ``` Sorry for I didn't explain it clearly, in the production phase, HP changed the product name of dmi table from HPZBookStudio16.0InchMobileWorkstationPC to HPZBookStudio16inchG9MobileWorkstationPC via internal mail from: Nukala, Ravi (CW) date: Mar 31, 2022, 11:23 AM subject:RE: [Stella] The airplane hotkey (F11) has no function I can forward the mail to use for reference if needed, thank you. -- 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/1966179 Title: The airplane hotkey does not work on lots of HP platforms Status in OEM Priority Project: Fix Committed Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Focal: Fix Committed Status in systemd source package in Impish: Incomplete Bug description: [Impact] The airplane hokey doesn't work on HP new generation machines. [Test Plan] Press airplane hokey. [Where problems could occur] If we don't have whitelist in focal and impish, then the airplane key won't work on new HP platforms. Please refer to Bug #1955997 as well. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1966179/+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 1969874] Re: Bluetooth Mouse and Keyboard drop connections when Laptop using battery
** Package changed: bluez (Ubuntu) => ubuntu ** Changed in: ubuntu Status: Incomplete => Fix Released -- 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/1969874 Title: Bluetooth Mouse and Keyboard drop connections when Laptop using battery Status in Ubuntu: Fix Released Bug description: Bluetooth Mouse and Keyboard drop connections when Laptop using battery (power discconnected). Keyboard and mouse work correctly when laptop is powered by mains power. May be related to suspend/resume. Symptoms: - Mouse and keyboard don't work. - Mouse and keyboard bluetooth association cannot be removed rand e-connected. - Mouse and keyboard are detected (sometimes) with different device names. The following does NOT fix the problem:: - Connect laptop power; - In Bluetooth settings Turn Bluetooth off, then on again Rebooting allows devices to be configured again, and connect correctly. Ubuntu version: Ubuntu 21.10 Kernel: 5.13.0-39-generic Package: bluez 5.60-0ubuntu2.2 When working the keyboard and mouse appear with: root@silver:/home/paul# bluetoothctl devices Device D2:91:D2:B9:6B:9D Logi POP Keys Device D1:8F:A4:4B:1B:F9 Logi POP Mouse When not working, the devices show up as: Device D2:91:D2:B9:6B:9D Logi POP @ Device D1:8F:A4:4B:1B:F9 Logi POP @ This devices are: - https://www.logitech.com/en-au/products/mice/pop-wireless-mouse.910-006515.html - https://www.logitech.com/en-au/products/keyboards/pop-keys-wireless-mechanical.920-010578.html I know that the devices both work with a Windows 10 desktop. Bluetooth Device Details When working.. root@silver:/home/paul# hciconfig -a hci0: Type: Primary Bus: USB BD Address: 20:68:9D:64:8A:FC ACL MTU: 1021:8 SCO MTU: 64:1 UP RUNNING RX bytes:1801269 acl:99624 sco:0 events:560 errors:0 TX bytes:8612 acl:173 sco:0 commands:227 errors:0 Features: 0xbf 0xfe 0xcf 0xfe 0xdb 0xff 0x7b 0x87 Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3 Link policy: RSWITCH SNIFF Link mode: SLAVE ACCEPT Name: 'silver' Class: 0x7c010c Service Classes: Rendering, Capturing, Object Transfer, Audio, Telephony Device Class: Computer, Laptop HCI Version: 4.0 (0x6) Revision: 0x1000 LMP Version: 4.0 (0x6) Subversion: 0x220e Manufacturer: Broadcom Corporation (15) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1969874/+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 1969874] Re: Bluetooth Mouse and Keyboard drop connections when Laptop using battery
Sorry.. 22.04 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1969874 Title: Bluetooth Mouse and Keyboard drop connections when Laptop using battery Status in bluez package in Ubuntu: Incomplete Bug description: Bluetooth Mouse and Keyboard drop connections when Laptop using battery (power discconnected). Keyboard and mouse work correctly when laptop is powered by mains power. May be related to suspend/resume. Symptoms: - Mouse and keyboard don't work. - Mouse and keyboard bluetooth association cannot be removed rand e-connected. - Mouse and keyboard are detected (sometimes) with different device names. The following does NOT fix the problem:: - Connect laptop power; - In Bluetooth settings Turn Bluetooth off, then on again Rebooting allows devices to be configured again, and connect correctly. Ubuntu version: Ubuntu 21.10 Kernel: 5.13.0-39-generic Package: bluez 5.60-0ubuntu2.2 When working the keyboard and mouse appear with: root@silver:/home/paul# bluetoothctl devices Device D2:91:D2:B9:6B:9D Logi POP Keys Device D1:8F:A4:4B:1B:F9 Logi POP Mouse When not working, the devices show up as: Device D2:91:D2:B9:6B:9D Logi POP @ Device D1:8F:A4:4B:1B:F9 Logi POP @ This devices are: - https://www.logitech.com/en-au/products/mice/pop-wireless-mouse.910-006515.html - https://www.logitech.com/en-au/products/keyboards/pop-keys-wireless-mechanical.920-010578.html I know that the devices both work with a Windows 10 desktop. Bluetooth Device Details When working.. root@silver:/home/paul# hciconfig -a hci0: Type: Primary Bus: USB BD Address: 20:68:9D:64:8A:FC ACL MTU: 1021:8 SCO MTU: 64:1 UP RUNNING RX bytes:1801269 acl:99624 sco:0 events:560 errors:0 TX bytes:8612 acl:173 sco:0 commands:227 errors:0 Features: 0xbf 0xfe 0xcf 0xfe 0xdb 0xff 0x7b 0x87 Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3 Link policy: RSWITCH SNIFF Link mode: SLAVE ACCEPT Name: 'silver' Class: 0x7c010c Service Classes: Rendering, Capturing, Object Transfer, Audio, Telephony Device Class: Computer, Laptop HCI Version: 4.0 (0x6) Revision: 0x1000 LMP Version: 4.0 (0x6) Subversion: 0x220e Manufacturer: Broadcom Corporation (15) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1969874/+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 1969874] Re: Bluetooth Mouse and Keyboard drop connections when Laptop using battery
I have upgraded to 22.03 The bluetooth mouse and keyboard are working. I will report if the problem occurs again. -- 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/1969874 Title: Bluetooth Mouse and Keyboard drop connections when Laptop using battery Status in bluez package in Ubuntu: Incomplete Bug description: Bluetooth Mouse and Keyboard drop connections when Laptop using battery (power discconnected). Keyboard and mouse work correctly when laptop is powered by mains power. May be related to suspend/resume. Symptoms: - Mouse and keyboard don't work. - Mouse and keyboard bluetooth association cannot be removed rand e-connected. - Mouse and keyboard are detected (sometimes) with different device names. The following does NOT fix the problem:: - Connect laptop power; - In Bluetooth settings Turn Bluetooth off, then on again Rebooting allows devices to be configured again, and connect correctly. Ubuntu version: Ubuntu 21.10 Kernel: 5.13.0-39-generic Package: bluez 5.60-0ubuntu2.2 When working the keyboard and mouse appear with: root@silver:/home/paul# bluetoothctl devices Device D2:91:D2:B9:6B:9D Logi POP Keys Device D1:8F:A4:4B:1B:F9 Logi POP Mouse When not working, the devices show up as: Device D2:91:D2:B9:6B:9D Logi POP @ Device D1:8F:A4:4B:1B:F9 Logi POP @ This devices are: - https://www.logitech.com/en-au/products/mice/pop-wireless-mouse.910-006515.html - https://www.logitech.com/en-au/products/keyboards/pop-keys-wireless-mechanical.920-010578.html I know that the devices both work with a Windows 10 desktop. Bluetooth Device Details When working.. root@silver:/home/paul# hciconfig -a hci0: Type: Primary Bus: USB BD Address: 20:68:9D:64:8A:FC ACL MTU: 1021:8 SCO MTU: 64:1 UP RUNNING RX bytes:1801269 acl:99624 sco:0 events:560 errors:0 TX bytes:8612 acl:173 sco:0 commands:227 errors:0 Features: 0xbf 0xfe 0xcf 0xfe 0xdb 0xff 0x7b 0x87 Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3 Link policy: RSWITCH SNIFF Link mode: SLAVE ACCEPT Name: 'silver' Class: 0x7c010c Service Classes: Rendering, Capturing, Object Transfer, Audio, Telephony Device Class: Computer, Laptop HCI Version: 4.0 (0x6) Revision: 0x1000 LMP Version: 4.0 (0x6) Subversion: 0x220e Manufacturer: Broadcom Corporation (15) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1969874/+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 1971005] Re: locate returns nothing
What file system are you using for your / partition? ** Package changed: findutils (Ubuntu) => plocate (Ubuntu) ** Changed in: plocate (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to findutils in Ubuntu. https://bugs.launchpad.net/bugs/1971005 Title: locate returns nothing Status in plocate package in Ubuntu: Incomplete Bug description: After upgrading to 22.04 LTS I found locate command not operable. For example: locate fstab returns nothing. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: findutils 4.8.0-1ubuntu3 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Uname: Linux 5.15.0-27-generic x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Sat Apr 30 01:08:18 2022 InstallationDate: Installed on 2019-04-13 (1112 days ago) InstallationMedia: Kubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190326.1) ProcEnviron: LANGUAGE= PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=uk_UA.UTF-8 SHELL=/bin/bash SourcePackage: findutils UpgradeStatus: Upgraded to jammy on 2022-04-22 (7 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/plocate/+bug/1971005/+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 1971158] Re: ssh connect to server stop on "SSH2_MSG_KEXINIT sent"
This is documented in the release note for Jammy Jellyfish (https://discourse.ubuntu.com/t/jammy-jellyfish-release-notes/24668): ssh-rsa is now disabled by default in OpenSSH 237. The release notes also contain a link to a way to continue connetcing to servers configured with ssh-rsa. ** Changed in: openssh (Ubuntu) Status: Confirmed => Won't Fix -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/1971158 Title: ssh connect to server stop on "SSH2_MSG_KEXINIT sent" Status in openssh package in Ubuntu: Won't Fix Bug description: After upgrade on Ubuntu 22.04 i can't connect to several servers. Connecting stopped on SSH2_MSG_KEXINIT sent ``` ssh -vvv -o KexAlgorithms=diffie-hellman-group-exchange-sha256 -oHostKeyAlgorithms=+ssh-rsa -X vld@sansa OpenSSH_8.9p1 Ubuntu-3, OpenSSL 3.0.2 15 Mar 2022 debug1: Reading configuration data /home/ruslan/.ssh/config debug3: kex names ok: [diffie-hellman-group1-sha1] debug3: kex names ok: [diffie-hellman-group-exchange-sha256,diffie-hellman-group-exchange-sha1,diffie-hellman-group14-sha1,diffie-hellman-group1-sha1] debug3: kex names ok: [diffie-hellman-group1-sha1] debug1: Reading configuration data /etc/ssh/ssh_config debug1: /etc/ssh/ssh_config line 19: include /etc/ssh/ssh_config.d/*.conf matched no files debug1: /etc/ssh/ssh_config line 21: Applying options for * debug3: expanded UserKnownHostsFile '~/.ssh/known_hosts' -> '/home/ruslan/.ssh/known_hosts' debug3: expanded UserKnownHostsFile '~/.ssh/known_hosts2' -> '/home/ruslan/.ssh/known_hosts2' debug2: resolving "sansa" port 22 debug3: resolve_host: lookup sansa:22 debug3: ssh_connect_direct: entering debug1: Connecting to sansa [172.16.xx.xx] port 22. debug3: set_sock_tos: set socket 3 IP_TOS 0x10 debug1: Connection established. debug1: identity file /home/ruslan/.ssh/id_rsa type -1 debug1: identity file /home/ruslan/.ssh/id_rsa-cert type -1 debug1: identity file /home/ruslan/.ssh/id_ecdsa type -1 debug1: identity file /home/ruslan/.ssh/id_ecdsa-cert type -1 debug1: identity file /home/ruslan/.ssh/id_ecdsa_sk type -1 debug1: identity file /home/ruslan/.ssh/id_ecdsa_sk-cert type -1 debug1: identity file /home/ruslan/.ssh/id_ed25519 type -1 debug1: identity file /home/ruslan/.ssh/id_ed25519-cert type -1 debug1: identity file /home/ruslan/.ssh/id_ed25519_sk type -1 debug1: identity file /home/ruslan/.ssh/id_ed25519_sk-cert type -1 debug1: identity file /home/ruslan/.ssh/id_xmss type -1 debug1: identity file /home/ruslan/.ssh/id_xmss-cert type -1 debug1: identity file /home/ruslan/.ssh/id_dsa type -1 debug1: identity file /home/ruslan/.ssh/id_dsa-cert type -1 debug1: Local version string SSH-2.0-OpenSSH_8.9p1 Ubuntu-3 debug1: Remote protocol version 2.0, remote software version OpenSSH_5.3 debug1: compat_banner: match: OpenSSH_5.3 pat OpenSSH_5* compat 0x0c02 debug2: fd 3 setting O_NONBLOCK debug1: Authenticating to sansa:22 as 'vld' debug1: load_hostkeys: fopen /etc/ssh/ssh_known_hosts2: No such file or directory debug3: order_hostkeyalgs: no algorithms matched; accept original debug3: send packet: type 20 debug1: SSH2_MSG_KEXINIT sent ``` I'm checking connection on old version Ubuntu 20.04, it's working. Remote server use KexAlgorithms=diffie-hellman-group-exchange-sha256 and HostKeyAlgorithms=ssh-rsa On Ubuntu 21.04 ssh was work. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1971158/+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 1971425] Re: The "look" cli dictionary only sees capitalized words
Curiously some words starting with b seem fine: $ look butter butter buttercup buttercup's buttercups buttered butterfat .. ** Tags added: rls-jj-incoming -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to util-linux in Ubuntu. https://bugs.launchpad.net/bugs/1971425 Title: The "look" cli dictionary only sees capitalized words Status in util-linux package in Ubuntu: Confirmed Bug description: In Ubuntu 20.04; ~ > look accident accident accident's accidental accidental's accidentally accidentals accidents In Ubuntu 22.04; ~ > look accident (nothing) ~ > look acc Accenture Accenture's Accra Accra's Digging deeper; the dictionary at /usr/share/dict/words seems OK. If I copy the "look" binary from Ubuntu 20.04 and use it on Ubuntu 22.04 it works; ~ > ./look accident accident accidental accidentally accidental's accidentals accident's accidents ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: bsdextrautils 2.37.2-4ubuntu3 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Uname: Linux 5.15.0-27-generic x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: XFCE Date: Tue May 3 14:19:57 2022 InstallationDate: Installed on 2018-09-07 (1334 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: util-linux UpgradeStatus: Upgraded to jammy on 2022-05-01 (2 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1971425/+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 1959345] Re: vulkaninfo reports error
Thank you. It does seem to point to that. Even so, vulkan-mesa-drivers has been installed and has not provided vulkan-icd. Does it go under a different name? When I installed vulkan-mesa-drivers, has dpkg or apt seen a remnant of amdgpu-pro and not installed the icd even though by normal means like the commands above I see no trace of amdgpu-pro? That appears unlikely. -- 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/1959345 Title: vulkaninfo reports error Status in mesa package in Ubuntu: Invalid Bug description: Tracker says mesa-vulkan-drivers is not in Ubuntu!? mesa-vulkan-drivers/bionic-updates,now 20.0.8-0ubuntu1~18.04.1 amd64 [installed] Ubuntu 18.04.6 LTS AMD Ryzen 7 2700x eight-core processor x 16 AMD Radeon rx 5700 xt apt-cache show says that vulkan-mesa-drivers provides vulkan-icd. find / -name vulkan-icd finds nothing vulkaninfo reports: ERROR: [Loader Message] Code 0 : loader_get_json: Failed to open JSON file amd_icd64.json There is an intel_icd.x86_64.json and radeon_icd.x86_64.json in /usr/share/vulkan/icd.d/ Either the error is a false positive or I should have amd_icd64.json - and then maybe all the other problems with the GPU would go away! --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: gary 12435 F pulseaudio /dev/snd/controlC2: gary 12435 F pulseaudio /dev/snd/controlC0: gary 12435 F pulseaudio CurrentDesktop: GNOME DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=4cce61c8-7d97-4fc3-8c3f-abfa4fd2810c InstallationDate: Installed on 2020-02-14 (740 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: Gigabyte Technology Co., Ltd. B450 AORUS ELITE Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-99-generic root=UUID=88ad01a0-775b-4405-b569-8928dac46131 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.4.0-99.112~18.04.1-generic 5.4.162 RelatedPackageVersions: linux-restricted-modules-5.4.0-99-generic N/A linux-backports-modules-5.4.0-99-generic N/A linux-firmware1.173.20 RfKill: Tags: bionic Uname: Linux 5.4.0-99-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dialout dip libvirt lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 10/13/2021 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: F63d dmi.board.asset.tag: Default string dmi.board.name: B450 AORUS ELITE dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrF63d:bd10/13/2021:svnGigabyteTechnologyCo.,Ltd.:pnB450AORUSELITE:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnB450AORUSELITE:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: B450 MB dmi.product.name: B450 AORUS ELITE dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1959345/+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 1970244] Re: [SRU] Enable support for Zed Cloud Archive
Hello Corey, or anyone else affected, Accepted software-properties into jammy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/software- properties/0.99.22.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- jammy to verification-done-jammy. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-jammy. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: software-properties (Ubuntu Jammy) Status: New => Fix Committed ** Tags added: verification-needed verification-needed-jammy -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1970244 Title: [SRU] Enable support for Zed Cloud Archive Status in software-properties package in Ubuntu: Fix Released Status in software-properties source package in Jammy: Fix Committed Bug description: Please add support for: cloud-archive:zed cloud-archive:zed-proposed This will also need to be SRU'd back to jammy. [Impact] End users have to manually enable the zed cloud archive pockets. [Test case] sudo add-apt-repository cloud-archive:zed sudo add-apt-repository cloud-archive:zed-proposed [Regression potential] Limited - just a data item addition To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1970244/+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 1970647] Re: notify-send exit code doesn't match result
Hello Marco, or anyone else affected, Accepted libnotify into jammy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/libnotify/0.7.9-3ubuntu5.22.04.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- jammy to verification-done-jammy. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-jammy. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: libnotify (Ubuntu Jammy) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-jammy -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libnotify in Ubuntu. https://bugs.launchpad.net/bugs/1970647 Title: notify-send exit code doesn't match result Status in libnotify package in Ubuntu: Fix Released Status in libnotify source package in Focal: In Progress Status in libnotify source package in Jammy: Fix Committed Bug description: No error exit code is returned by notify-send on failure [ Test case ] 1. Run: jhbuild run env DBUS_SESSION_BUS_ADDRESS= notify-send foo bar || echo error 2. In a terminal "error" should be printed [ Regression potential ] Programs relying on notify-send may have errors when they did not. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libnotify/+bug/1970647/+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 1802483] Re: Notifications emitted by a snap with local files or desktop files use wrong namespace
Hello Marco, or anyone else affected, Accepted libnotify into jammy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/libnotify/0.7.9-3ubuntu5.22.04.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- jammy to verification-done-jammy. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-jammy. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: libnotify (Ubuntu Jammy) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-jammy -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libnotify in Ubuntu. https://bugs.launchpad.net/bugs/1802483 Title: Notifications emitted by a snap with local files or desktop files use wrong namespace Status in libnotify package in Ubuntu: Fix Released Status in libnotify source package in Focal: In Progress Status in libnotify source package in Jammy: Fix Committed Bug description: As can be tested using this example snap: - https://github.com/3v1n0/notify-send-test-snap Basically the icons are referenced using absolute paths in snap environment, while they should be readapted so that they depend on $SNAP location. As we do with appindicators and libunity emblems. [ Impact ] Icons sonuds and desktop files referenced by a snapped app using notifications aren't exposed to the desktop in absolute paths [ Test case ] Build the test snap (or install it from the attached files to this bug): git clone https://github.com/3v1n0/notify-send-test-snap snapcraft prime snap try prime To use the pre-built snap (https://bugs.launchpad.net/ubuntu/+source/libnotify/+bug/1802483/comments/7) snap install --dangerous notify-send-test-snap_*.snap Check that icons are shown when launching: notify-send-test-snap notify-send-test-snap.image-path notify-send-test-snap.image-uri Ensure that desktop entry is correctly sent, monitoring the dbus session: In a terminal: dbus-monitor --session --monitor "interface='org.freedesktop.Notifications'" In the other: notify-send-test-snap.desktop-entry notify-send-test-snap.desktop-entry-explicit-id notify-send-test-snap.desktop-entry-explicit-file-name notify-send-test-snap.desktop-entry-explicit-path notify-send-test-snap.desktop-entry-explicit-uri notify-send-test-snap.desktop-entry-explicit-snapped-uri The `desktop-entry` value sent to dbus should be either: - A `notify-send-test-snap_`-prefixed desktop ID - A .desktop file path (readable from both inside and outside the snap) - A .desktop file uri (readable from both inside and outside the snap) [ Regression potential ] Normal applications that are run with a SNAP environment variable set, might use wrong paths for files or desktop file To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libnotify/+bug/1802483/+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 1969934] Re: Update evolution-data-server to 3.44.1
Hello Jeremy, or anyone else affected, Accepted evolution-data-server into jammy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/evolution-data- server/3.44.1-0ubuntu1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- jammy to verification-done-jammy. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-jammy. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: evolution-data-server (Ubuntu Jammy) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-jammy -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to evolution-data-server in Ubuntu. https://bugs.launchpad.net/bugs/1969934 Title: Update evolution-data-server to 3.44.1 Status in evolution-data-server package in Ubuntu: Fix Released Status in evolution-data-server source package in Jammy: Fix Committed Bug description: Impact -- This is a new stable release in the 3.44 series (corresponding with GNOME 42). https://gitlab.gnome.org/GNOME/evolution-data- server/-/blob/3.44.1/NEWS It is required to update evolution to 3.44.1 (LP: #1969935) Test Case - Install the update Log out and log back in (or restart) Ensure that GNOME Calendar and Evolution still work fine. What Could Go Wrong --- As a component of GNOME core, there is a micro-release exception for evolution-data-server https://wiki.ubuntu.com/StableReleaseUpdates/GNOME To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution-data-server/+bug/1969934/+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 1971492] [NEW] package lightdm 1.30.0-0ubuntu4~20.04.2 failed to install/upgrade: end of file on stdin at conffile prompt
Public bug reported: Nothing obviously wrong that I could tell ProblemType: Package DistroRelease: Ubuntu 20.04 Package: lightdm 1.30.0-0ubuntu4~20.04.2 ProcVersionSignature: Ubuntu 5.4.0-96.109-generic 5.4.157 Uname: Linux 5.4.0-96-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 AptOrdering: rfkill:amd64: Install NULL: ConfigurePending Architecture: amd64 CasperMD5CheckResult: skip Date: Tue May 3 06:05:52 2022 DpkgHistoryLog: Start-Date: 2022-05-03 06:05:50 Commandline: /usr/bin/unattended-upgrade Upgrade: rfkill:amd64 (2.34-0.1ubuntu9.1, 2.34-0.1ubuntu9.3) ErrorMessage: end of file on stdin at conffile prompt InstallationDate: Installed on 2018-12-10 (1239 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4 RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.6 SourcePackage: lightdm Title: package lightdm 1.30.0-0ubuntu4~20.04.2 failed to install/upgrade: end of file on stdin at conffile prompt UpgradeStatus: Upgraded to focal on 2021-12-15 (139 days ago) mtime.conffile..etc.pam.d.lightdm: 2018-12-10T13:15:57.713002 ** Affects: lightdm (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package focal need-duplicate-check -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1971492 Title: package lightdm 1.30.0-0ubuntu4~20.04.2 failed to install/upgrade: end of file on stdin at conffile prompt Status in lightdm package in Ubuntu: New Bug description: Nothing obviously wrong that I could tell ProblemType: Package DistroRelease: Ubuntu 20.04 Package: lightdm 1.30.0-0ubuntu4~20.04.2 ProcVersionSignature: Ubuntu 5.4.0-96.109-generic 5.4.157 Uname: Linux 5.4.0-96-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 AptOrdering: rfkill:amd64: Install NULL: ConfigurePending Architecture: amd64 CasperMD5CheckResult: skip Date: Tue May 3 06:05:52 2022 DpkgHistoryLog: Start-Date: 2022-05-03 06:05:50 Commandline: /usr/bin/unattended-upgrade Upgrade: rfkill:amd64 (2.34-0.1ubuntu9.1, 2.34-0.1ubuntu9.3) ErrorMessage: end of file on stdin at conffile prompt InstallationDate: Installed on 2018-12-10 (1239 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4 RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.6 SourcePackage: lightdm Title: package lightdm 1.30.0-0ubuntu4~20.04.2 failed to install/upgrade: end of file on stdin at conffile prompt UpgradeStatus: Upgraded to focal on 2021-12-15 (139 days ago) mtime.conffile..etc.pam.d.lightdm: 2018-12-10T13:15:57.713002 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1971492/+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 1971481] Re: root pass on discover sofware source error
** Package changed: ubuntu => xorg (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/1971481 Title: root pass on discover sofware source error Status in xorg package in Ubuntu: New Bug description: STEPS TO REPRODUCE 1. Go to Discover 2. Go to Preferences 3. Click on Software Sources and put root pass OBSERVED RESULT Error always to try enter in software sources EXPECTED RESULT Open software sources and manage all preferences SOFTWARE/OS VERSIONS Linux/KDE Plasma: Kubuntu 22.04 KDE Plasma Version: 5.24.4 ADDITIONAL INFORMATION It only is happened on Kubuntu 22.04. If you use Kubuntu backport from Kubuntu 21.10 it runs perfectly ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Uname: Linux 5.15.0-27-generic x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 BootLog: Error: [Errno 13] Permiso denegado: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: KDE Date: Tue May 3 20:57:25 2022 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: I just need to know a workaround GraphicsCard: VMware SVGA II Adapter [15ad:0405] (prog-if 00 [VGA controller]) Subsystem: VMware SVGA II Adapter [15ad:0405] InstallationDate: Installed on 2022-04-23 (9 days ago) InstallationMedia: Kubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) Lsusb: Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Lsusb-t: /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ohci-pci/12p, 12M |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M MachineType: innotek GmbH VirtualBox ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-27-generic root=UUID=0a53b0d0-ec7a-4a08-b211-4b5411d87fa9 ro quiet splash SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/01/2006 dmi.bios.vendor: innotek GmbH dmi.bios.version: VirtualBox dmi.board.name: VirtualBox dmi.board.vendor: Oracle Corporation dmi.board.version: 1.2 dmi.chassis.type: 1 dmi.chassis.vendor: Oracle Corporation dmi.modalias: dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:sku: dmi.product.family: Virtual Machine dmi.product.name: VirtualBox dmi.product.version: 1.2 dmi.sys.vendor: innotek GmbH version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.110-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.1-1ubuntu2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1971481/+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 1971468] Re: The upgrade will continue but the 'linux-image-5.13.0-39-generic' package may not be in a working state.
** Package changed: ubuntu => vim (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to vim in Ubuntu. https://bugs.launchpad.net/bugs/1971468 Title: The upgrade will continue but the 'linux-image-5.13.0-39-generic' package may not be in a working state. Status in vim package in Ubuntu: New Bug description: installed linux-image-5.13.0-39-generic package post-removal script subprocess returned error exit status 1 Ubuntu 22.04 Can not upgrade update Can not remove Brave Waiting for cache lock: Could not get lock /var/lib/dpkg/lock-frontend. It is held by process 2767 (do-partial-upgr) Brave and Chrome keep crashing Ubuntu grub shows 2 ubuntu menu ( upgraded to 22.04 from 21.10 few days ago ), both ubuntu menu are openng ubuntu 22.04 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: vim (not installed) ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Uname: Linux 5.15.0-27-generic x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed May 4 00:55:44 2022 InstallationDate: Installed on 2022-03-24 (40 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) SourcePackage: vim UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vim/+bug/1971468/+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 1971468] [NEW] The upgrade will continue but the 'linux-image-5.13.0-39-generic' package may not be in a working state.
You have been subscribed to a public bug: installed linux-image-5.13.0-39-generic package post-removal script subprocess returned error exit status 1 Ubuntu 22.04 Can not upgrade update Can not remove Brave Waiting for cache lock: Could not get lock /var/lib/dpkg/lock-frontend. It is held by process 2767 (do-partial-upgr) Brave and Chrome keep crashing Ubuntu grub shows 2 ubuntu menu ( upgraded to 22.04 from 21.10 few days ago ), both ubuntu menu are openng ubuntu 22.04 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: vim (not installed) ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Uname: Linux 5.15.0-27-generic x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed May 4 00:55:44 2022 InstallationDate: Installed on 2022-03-24 (40 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) SourcePackage: vim UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: vim (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy wayland-session -- The upgrade will continue but the 'linux-image-5.13.0-39-generic' package may not be in a working state. https://bugs.launchpad.net/bugs/1971468 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to vim in Ubuntu. -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1971481] [NEW] root pass on discover sofware source error
You have been subscribed to a public bug: STEPS TO REPRODUCE 1. Go to Discover 2. Go to Preferences 3. Click on Software Sources and put root pass OBSERVED RESULT Error always to try enter in software sources EXPECTED RESULT Open software sources and manage all preferences SOFTWARE/OS VERSIONS Linux/KDE Plasma: Kubuntu 22.04 KDE Plasma Version: 5.24.4 ADDITIONAL INFORMATION It only is happened on Kubuntu 22.04. If you use Kubuntu backport from Kubuntu 21.10 it runs perfectly ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Uname: Linux 5.15.0-27-generic x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 BootLog: Error: [Errno 13] Permiso denegado: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: KDE Date: Tue May 3 20:57:25 2022 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: I just need to know a workaround GraphicsCard: VMware SVGA II Adapter [15ad:0405] (prog-if 00 [VGA controller]) Subsystem: VMware SVGA II Adapter [15ad:0405] InstallationDate: Installed on 2022-04-23 (9 days ago) InstallationMedia: Kubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) Lsusb: Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Lsusb-t: /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ohci-pci/12p, 12M |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M MachineType: innotek GmbH VirtualBox ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-27-generic root=UUID=0a53b0d0-ec7a-4a08-b211-4b5411d87fa9 ro quiet splash SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/01/2006 dmi.bios.vendor: innotek GmbH dmi.bios.version: VirtualBox dmi.board.name: VirtualBox dmi.board.vendor: Oracle Corporation dmi.board.version: 1.2 dmi.chassis.type: 1 dmi.chassis.vendor: Oracle Corporation dmi.modalias: dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:sku: dmi.product.family: Virtual Machine dmi.product.name: VirtualBox dmi.product.version: 1.2 dmi.sys.vendor: innotek GmbH version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.110-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.1-1ubuntu2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy kubuntu ubuntu -- root pass on discover sofware source error https://bugs.launchpad.net/bugs/1971481 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1729491] Re: [UIFe] ubuntu-bug says that snap packages are not installed
** Changed in: ubuntu-docs (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1729491 Title: [UIFe] ubuntu-bug says that snap packages are not installed Status in apport package in Ubuntu: Fix Released Status in ubuntu-docs package in Ubuntu: Confirmed Status in apport source package in Bionic: Fix Released Bug description: User Interface Freeze Exception Justification = The interface for ubuntu-bug/apport-bug is super confusing if was installed as a snap. List Notifications == https://lists.ubuntu.com/archives/ubuntu-translators/2018-April/007471.html Original Bug Description 1. I installed the package gnome-recipes, tried to send an error report program in response to the received message:you cannot report a problem: The report belongs to a package that was not installed. 2. Expected that the program will be identified as installed. 3. sudo apt -f install [sudo] password for Alexander: Reading package lists... Done Building dependency tree Reading state information... Ready 0 upgraded, 0 newly installed, for removal 0 packets are marked, and 0 packages are not updated. sudo gnome-sudo recipes: gnome-recipes: command not found sudo apt install gnome-recipes Reading package lists... Done Building dependency tree Reading state information... Ready E: unable to locate package gnome-recipes I installed via software-center gnome-recipes snap-confine has elevated permissions and is not confined but should be. Refusing to continue to avoid permission escalation attacks ubuntu-bug gnome-recipes dpkg-query: template gnome-recipes no corresponding package Gtk-Message: GtkDialog mapped without a transient parent. This is discouraged. ^C^Z [1]+ Stopped ubuntu-bug gnome-recipes https://youtu.be/AXtR5m2uqUg --- 1. произвёл установку пакета gnome-recipes, попытался отправить отчёт об ошибке программы, в ответ получил сообщение:Не удаётся сообщить о неполадке: Отчёт относится к пакету , который не был установлен. 2. Ожидал что программа будет идентифицироваться как установленная. 3. sudo apt -f install [sudo] пароль для alexandr: Чтение списков пакетов… Готово Построение дерева зависимостей Чтение информации о состоянии… Готово обновлено 0, установлено 0 новых пакетов, для удаления отмечено 0 пакетов, и 0 пакетов не обновлено. sudo gnome-recipes sudo: gnome-recipes: команда не найдена sudo apt install gnome-recipes Чтение списков пакетов… Готово Построение дерева зависимостей Чтение информации о состоянии… Готово E: Не удалось найти пакет gnome-recipes произвёл установку через software-center gnome-recipes snap-confine has elevated permissions and is not confined but should be. Refusing to continue to avoid permission escalation attacks ubuntu-bug gnome-recipes dpkg-query: шаблону gnome-recipes не соответствует ни один пакет Gtk-Message: GtkDialog mapped without a transient parent. This is discouraged. ^C^Z [1]+ Остановлено ubuntu-bug gnome-recipes https://youtu.be/AXtR5m2uqUg ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: software-center (not installed) Uname: Linux 4.14.0-041400rc7-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 CurrentDesktop: Unity Date: Thu Nov 2 08:06:48 2017 InstallationDate: Installed on 2017-10-29 (3 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) SourcePackage: software-center UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1729491/+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 1966179] Re: The airplane hotkey does not work on lots of HP platforms
I don't see any indication that "evdev:name:Intel HID events:dmi:bvn*:bvr*:bd*:svnHP*:pnHPZBookStudio16.0InchMobileWorkstationPC:pvr*" is still working (which was asked to be tested in comment #8). Is it? ** Changed in: systemd (Ubuntu Impish) Status: Fix Committed => Incomplete -- 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/1966179 Title: The airplane hotkey does not work on lots of HP platforms Status in OEM Priority Project: Fix Committed Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Focal: Fix Committed Status in systemd source package in Impish: Incomplete Bug description: [Impact] The airplane hokey doesn't work on HP new generation machines. [Test Plan] Press airplane hokey. [Where problems could occur] If we don't have whitelist in focal and impish, then the airplane key won't work on new HP platforms. Please refer to Bug #1955997 as well. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1966179/+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 1967038] Re: Add mic mute key for HP Elite x360 series
This bug was fixed in the package systemd - 249.11-0ubuntu3.1 --- systemd (249.11-0ubuntu3.1) jammy; urgency=medium [ Andy Chi ] * Add mic mute key support for HP Elite x360 series (LP: #1967038) Author: Andy Chi File: debian/patches/hwdb-Add-mic-mute-key-mapping-for-HP-Elite-x360.patch https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=45e809103de9c356c75b692d35089e8770602617 -- Lukas Märdian Thu, 21 Apr 2022 14:14:26 +0200 ** Changed in: systemd (Ubuntu Jammy) Status: Fix Committed => Fix Released -- 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/1967038 Title: Add mic mute key for HP Elite x360 series Status in OEM Priority Project: Fix Committed Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Focal: Fix Committed Status in systemd source package in Impish: Fix Committed Status in systemd source package in Jammy: Fix Released Bug description: Upstream commit: https://github.com/systemd/systemd/commit/f09f6dc2c8f59b2b58159cc413b605a547c8646e [Impact] * User can't use mic mute key if they buy Elite x360 G9 series. [Test Plan] * Test mic mute key on Elite x360 G9 series. [Where problems could occur] * This change adds key event mapping in hwdb, which won't impact other hardware. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1967038/+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 1967038] Update Released
The verification of the Stable Release Update for systemd has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1967038 Title: Add mic mute key for HP Elite x360 series Status in OEM Priority Project: Fix Committed Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Focal: Fix Committed Status in systemd source package in Impish: Fix Committed Status in systemd source package in Jammy: Fix Released Bug description: Upstream commit: https://github.com/systemd/systemd/commit/f09f6dc2c8f59b2b58159cc413b605a547c8646e [Impact] * User can't use mic mute key if they buy Elite x360 G9 series. [Test Plan] * Test mic mute key on Elite x360 G9 series. [Where problems could occur] * This change adds key event mapping in hwdb, which won't impact other hardware. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1967038/+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 1971474] [NEW] SRU: Update gdb to the final 12.1 release in 22.04 LTS
Public bug reported: Update gdb to the final 12.1 release in 22.04 LTS. jammy ships with the gdb 12.1 release candidate, taken from the gdb-12 branch. Changes up to the final release are: - updated gnulib library - Fix for PR mi/29002 (Windows only) - gdb: fix 'remote show FOO-packet' aliases - various testsuite fixes - fixing compiler warnings - Fix bug in Ada number lexing - Remove "Ada Settings" node from the manual - Handle TLS variable lookups when using separate debug files. - PR 28980: gdb: don't copy entirely optimized out values in value_copy - gdb/mi: fix use after free of frame_info causing spurious notifications Comparing the test results between the two builds doesn't show any regression on any architecture. ** Affects: gdb (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gdb in Ubuntu. https://bugs.launchpad.net/bugs/1971474 Title: SRU: Update gdb to the final 12.1 release in 22.04 LTS Status in gdb package in Ubuntu: New Bug description: Update gdb to the final 12.1 release in 22.04 LTS. jammy ships with the gdb 12.1 release candidate, taken from the gdb-12 branch. Changes up to the final release are: - updated gnulib library - Fix for PR mi/29002 (Windows only) - gdb: fix 'remote show FOO-packet' aliases - various testsuite fixes - fixing compiler warnings - Fix bug in Ada number lexing - Remove "Ada Settings" node from the manual - Handle TLS variable lookups when using separate debug files. - PR 28980: gdb: don't copy entirely optimized out values in value_copy - gdb/mi: fix use after free of frame_info causing spurious notifications Comparing the test results between the two builds doesn't show any regression on any architecture. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdb/+bug/1971474/+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 1971460] [NEW] Xorg and Wayland freeze
Public bug reported: I've Ubuntu 22.04 with Wayland and Sapphire Radeon RX 6600 with Xiaomi 34" curved gaming monitor capable of 3440x1440 @144,00hz. Using refresh of 120hz or 144hz, the system freezes coming out from suspension or randomly from screen power save. Setting @60hz it's more stable. It seems something related to wrong Modeline for this VGA and monitor resolution/frequencies. The problem is with both DP or HDMI cable. With HDMI it supports only 99,99hz I had no problem with the provious HP RX 460 HanSolo or XFX GTX 1060 3GB with proprietary nVidia drivers. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Uname: Linux 5.15.0-27-generic x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 BootLog: Error: [Errno 13] Permesso negato: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue May 3 18:29:05 2022 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu DkmsStatus: virtualbox/6.1.32, 5.15.0-25-generic, x86_64: installed virtualbox/6.1.32, 5.15.0-27-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GpuHangFrequency: Several times a day GpuHangReproducibility: Yes, I can easily reproduce it GpuHangStarted: Immediately after installing this version of Ubuntu GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Navi 23 [Radeon RX 6600/6600 XT/6600M] [1002:73ff] (rev c7) (prog-if 00 [VGA controller]) Subsystem: Sapphire Technology Limited Navi 23 [Radeon RX 6600/6600 XT/6600M] [1da2:e447] InstallationDate: Installed on 2022-04-23 (9 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: System manufacturer System Product Name ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-27-generic root=UUID=be1c4139-f2bc-472b-87c1-099f2be97b1a ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/25/2022 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3604 dmi.board.asset.tag: Default string dmi.board.name: TUF B450M-PRO GAMING dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3604:bd02/25/2022:br5.17:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnTUFB450M-PROGAMING:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.110-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.1-1ubuntu2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug freeze jammy 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/1971460 Title: Xorg and Wayland freeze Status in xorg package in Ubuntu: New Bug description: I've Ubuntu 22.04 with Wayland and Sapphire Radeon RX 6600 with Xiaomi 34" curved gaming monitor capable of 3440x1440 @144,00hz. Using refresh of 120hz or 144hz, the system freezes coming out from suspension or randomly from screen power save. Setting @60hz it's more stable. It seems something related to wrong Modeline for this VGA and monitor resolution/frequencies. The problem is with both DP or HDMI cable. With HDMI it supports only 99,99hz I had no problem with the provious HP RX 460 HanSolo or XFX GTX 1060 3GB with proprietary nVidia drivers. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Uname: Linux 5.15.0-27-generic x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 BootLog: Error: [Errno 13] Permesso negato: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue May 3 18:29:05 2022 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant:
[Touch-packages] [Bug 1971089] Re: Network Manager bug constant reconnecting and CPU usage
Thank you for your bug report, could you add a 'journalctl -b 0 > log' record to the bug after triggering the issue? ** Changed in: network-manager (Ubuntu) Status: New => Incomplete -- 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/1971089 Title: Network Manager bug constant reconnecting and CPU usage Status in network-manager package in Ubuntu: Incomplete Bug description: Anyconnectin result cpu heavy usage. constant reconnections wifi/ethernet..no matter ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: network-manager 1.36.4-2ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Uname: Linux 5.15.0-27-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Sun May 1 17:00:00 2022 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2017-06-03 (1793 days ago) InstallationMedia: Kubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) IpRoute: default via 192.168.1.1 dev enp5s0 proto dhcp metric 100 169.254.0.0/16 dev docker0 scope link metric 1000 linkdown 172.17.0.0/16 dev docker0 proto kernel scope link src 172.17.0.1 linkdown 192.168.1.0/24 dev enp5s0 proto kernel scope link src 192.168.1.148 metric 100 SourcePackage: network-manager UpgradeStatus: Upgraded to jammy on 2022-04-25 (6 days ago) nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.36.4 connected started full enabled enabled enabled enabled disabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1971089/+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 1951653] Re: can't use NM for ethernet device on 20.04 LTS because it is 'strictly unmanaged'
I agree that the /usr/lib/NetworkManager/conf.d/10-globally-managed- devices.conf should be deleted from Ubuntu's network-manager package. Especially, as it is being overwritten in any normal Ubuntu Desktop installation, using the following netplan YAML: ``` network: version: 2 renderer: NetworkManager ``` If we use a global "renderer: NetworkManager" stanza (as is the default on Ubuntu Desktop, where NM is part of the default installation) netplan will create an empty file in /run/NetworkManager/conf.d/10-globally- managed-devices.conf, to override that file anyway. But we should be aware that it could introduce a change of default behavior on Ubuntu server where network-manager is being installed additionally. But netplan generates /run/NetworkManager/conf.d/netplan.conf to specifically ignore devices that are not supposed to be handled by NM, so we should be fine there, too. I've recently updated the allow- and deny-list logic in netplan to be more generic and instruct NetworkManager to ignore/manage devices based on specific udev rules. With this PR I'm also changing the 10-globally- managed-devices.conf logic to override Ubuntu's default anytime a NetworkManager interface is being defined in netplan YAML (not just if it's defined as the global renderer). https://github.com/canonical/netplan/pull/276 ** Changed in: netplan.io (Ubuntu) Assignee: (unassigned) => Lukas Märdian (slyon) ** Changed in: netplan.io (Ubuntu) Status: Triaged => In Progress -- 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/1951653 Title: can't use NM for ethernet device on 20.04 LTS because it is 'strictly unmanaged' Status in netplan.io package in Ubuntu: In Progress Status in network-manager package in Ubuntu: Confirmed Bug description: I have tried to tell netplan to let my ethernet device be managed by NetworkManager, so that I can then configure a pppoe connection on top of this device. This fails with: # nmcli c up netplan-wan Error: Connection activation failed: No suitable device found for this connection (device lo not available because device is strictly unmanaged). # I don't know why it mentions 'lo' in that message, but the wan interface is unmanaged (as are all devices on the system, but this one is supposed to be managed): # nmcli d status | grep wan wan ethernet unmanaged -- # After much searching, I've figured out that this comes from /usr/lib/NetworkManager/conf.d/10-globally-managed-devices.conf: keyfile] unmanaged-devices=*,except:type:wifi,except:type:gsm,except:type:cdma Even though I've told netplan to use the NM renderer for this device, the configuration emitted by netplan is insufficient to override this. Using the workaround from https://askubuntu.com/questions/71159/network-manager-says-device-not- managed (sudo touch /etc/NetworkManager/conf.d/10-globally-managed- devices.conf) doesn't work, but if I set NetworkManager as the toplevel renderer in /etc/netplan, /run/NetworkManager/conf.d/10-globally-managed-devices.conf is emitted, which evidently DOES work. But I only have one device that I want rendered by NM, so I shouldn't have to declare NM at the top level of the yaml with a lot of duplication in order to get this result. I would argue that the 10-globally-managed-devices.conf should not be there at all. But if it is going to be, then netplan needs to consistently override it whenever there is any use of the NetworkManager backend. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/netplan.io/+bug/1951653/+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 1673625] Re: 10-globally-managed-devices.conf contained in wrong package
*** This bug is a duplicate of bug 1951653 *** https://bugs.launchpad.net/bugs/1951653 ** This bug has been marked a duplicate of bug 1951653 can't use NM for ethernet device on 20.04 LTS because it is 'strictly unmanaged' -- 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/1673625 Title: 10-globally-managed-devices.conf contained in wrong package Status in network-manager package in Ubuntu: Won't Fix Status in nplan package in Ubuntu: Won't Fix Bug description: /usr/lib/NetworkManager/conf.d/10-globally-managed-devices.conf is installed from network-manager but without nplan it has no benefit, and breaks networking until you override it. Since the config is there to change how NetworkManager behaves in the presence of nplan, the configuration file itself should actually be contained in the nplan package. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1673625/+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 1971425] Re: The "look" cli dictionary only sees capitalized words
could be the same issue than https://github.com/util-linux/util- linux/issues/1493 ** Bug watch added: github.com/util-linux/util-linux/issues #1493 https://github.com/util-linux/util-linux/issues/1493 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to util-linux in Ubuntu. https://bugs.launchpad.net/bugs/1971425 Title: The "look" cli dictionary only sees capitalized words Status in util-linux package in Ubuntu: Confirmed Bug description: In Ubuntu 20.04; ~ > look accident accident accident's accidental accidental's accidentally accidentals accidents In Ubuntu 22.04; ~ > look accident (nothing) ~ > look acc Accenture Accenture's Accra Accra's Digging deeper; the dictionary at /usr/share/dict/words seems OK. If I copy the "look" binary from Ubuntu 20.04 and use it on Ubuntu 22.04 it works; ~ > ./look accident accident accidental accidentally accidental's accidentals accident's accidents ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: bsdextrautils 2.37.2-4ubuntu3 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Uname: Linux 5.15.0-27-generic x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: XFCE Date: Tue May 3 14:19:57 2022 InstallationDate: Installed on 2018-09-07 (1334 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: util-linux UpgradeStatus: Upgraded to jammy on 2022-05-01 (2 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1971425/+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 1971425] Re: The "look" cli dictionary only sees capitalized words
Thank you for your bug report. Indeed it seems buggy but the description isn't accurate since using it with 'keyboard' works as expected ** Changed in: util-linux (Ubuntu) Status: New => Confirmed ** Changed in: util-linux (Ubuntu) Importance: Undecided => Low -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to util-linux in Ubuntu. https://bugs.launchpad.net/bugs/1971425 Title: The "look" cli dictionary only sees capitalized words Status in util-linux package in Ubuntu: Confirmed Bug description: In Ubuntu 20.04; ~ > look accident accident accident's accidental accidental's accidentally accidentals accidents In Ubuntu 22.04; ~ > look accident (nothing) ~ > look acc Accenture Accenture's Accra Accra's Digging deeper; the dictionary at /usr/share/dict/words seems OK. If I copy the "look" binary from Ubuntu 20.04 and use it on Ubuntu 22.04 it works; ~ > ./look accident accident accidental accidentally accidental's accidentals accident's accidents ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: bsdextrautils 2.37.2-4ubuntu3 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Uname: Linux 5.15.0-27-generic x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: XFCE Date: Tue May 3 14:19:57 2022 InstallationDate: Installed on 2018-09-07 (1334 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: util-linux UpgradeStatus: Upgraded to jammy on 2022-05-01 (2 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1971425/+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 1971430] [NEW] lz4 is not a dependency of initramfs-tools-core
Public bug reported: lz4 is not a dependency of initramfs-tools-core, although it uses lz4cat in the unmkinitramfs script. ** Affects: initramfs-tools (Ubuntu) Importance: Undecided Status: New -- 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/1971430 Title: lz4 is not a dependency of initramfs-tools-core Status in initramfs-tools package in Ubuntu: New Bug description: lz4 is not a dependency of initramfs-tools-core, although it uses lz4cat in the unmkinitramfs script. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1971430/+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 1958267] Re: "Connection failed" for WPA Enterprise network (e.g. eduroam)
There are thousand ways to do stuff in linux era :D, I have picked one. To clear the mark and the impish repo: sudo rm -f /etc/apt/sources.list.d/impish.list sudo apt-mark unhold wpasupplicant After they have released the updated package. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to wpa in Ubuntu. https://bugs.launchpad.net/bugs/1958267 Title: "Connection failed" for WPA Enterprise network (e.g. eduroam) Status in wpa package in Ubuntu: Confirmed Status in wpa source package in Jammy: Confirmed Bug description: With the current jammy version of wpasupplicant (2:2.10-1), I cannot connect to the WPA Enterprise network eduroam, which is used by Universities worldwide. I get a "Connection failed" message or a request to re-enter the password. - I've re-tried the credentials: no fix ;-) - Tried a 21.10 live session on the same machine: works fine! - Manually downgraded wpasupplicant to the impish version (2:2.9.0-21build1): connected normally. - Upgraded wpasupplicant to the latest version: fails to connect again. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: wpasupplicant 2:2.10-1 ProcVersionSignature: Ubuntu 5.15.0-17.17-generic 5.15.12 Uname: Linux 5.15.0-17-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu75 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Jan 18 09:56:23 2022 InstallationDate: Installed on 2021-11-30 (48 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20211130) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: wpa UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1958267/+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 1971418] Re: network-manager/1.36.4-2ubuntu1 ADT test failure with linux/5.15.0-28.29
** Changed in: linux (Ubuntu Jammy) Status: In Progress => Fix Committed -- 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/1971418 Title: network-manager/1.36.4-2ubuntu1 ADT test failure with linux/5.15.0-28.29 Status in linux package in Ubuntu: Invalid Status in network-manager package in Ubuntu: Invalid Status in linux source package in Jammy: Fix Committed Status in network-manager source package in Jammy: Invalid Bug description: This is a scripted bug report about ADT failures while running network-manager tests for linux/5.15.0-28.29 on jammy. Whether this is caused by the dep8 tests of the tested source or the kernel has yet to be determined. Testing failed on: amd64: https://autopkgtest.ubuntu.com/results/autopkgtest-jammy/jammy/amd64/n/network-manager/20220503_090742_432dd@/log.gz arm64: https://autopkgtest.ubuntu.com/results/autopkgtest-jammy/jammy/arm64/n/network-manager/20220429_062345_345a3@/log.gz ppc64el: https://autopkgtest.ubuntu.com/results/autopkgtest-jammy/jammy/ppc64el/n/network-manager/20220429_060513_fc2a9@/log.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1971418/+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 1971425] [NEW] The "look" cli dictionary only sees capitalized words
Public bug reported: In Ubuntu 20.04; ~ > look accident accident accident's accidental accidental's accidentally accidentals accidents In Ubuntu 22.04; ~ > look accident (nothing) ~ > look acc Accenture Accenture's Accra Accra's Digging deeper; the dictionary at /usr/share/dict/words seems OK. If I copy the "look" binary from Ubuntu 20.04 and use it on Ubuntu 22.04 it works; ~ > ./look accident accident accidental accidentally accidental's accidentals accident's accidents ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: bsdextrautils 2.37.2-4ubuntu3 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Uname: Linux 5.15.0-27-generic x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: XFCE Date: Tue May 3 14:19:57 2022 InstallationDate: Installed on 2018-09-07 (1334 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: util-linux UpgradeStatus: Upgraded to jammy on 2022-05-01 (2 days ago) ** Affects: util-linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to util-linux in Ubuntu. https://bugs.launchpad.net/bugs/1971425 Title: The "look" cli dictionary only sees capitalized words Status in util-linux package in Ubuntu: New Bug description: In Ubuntu 20.04; ~ > look accident accident accident's accidental accidental's accidentally accidentals accidents In Ubuntu 22.04; ~ > look accident (nothing) ~ > look acc Accenture Accenture's Accra Accra's Digging deeper; the dictionary at /usr/share/dict/words seems OK. If I copy the "look" binary from Ubuntu 20.04 and use it on Ubuntu 22.04 it works; ~ > ./look accident accident accidental accidentally accidental's accidentals accident's accidents ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: bsdextrautils 2.37.2-4ubuntu3 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Uname: Linux 5.15.0-27-generic x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: XFCE Date: Tue May 3 14:19:57 2022 InstallationDate: Installed on 2018-09-07 (1334 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: util-linux UpgradeStatus: Upgraded to jammy on 2022-05-01 (2 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1971425/+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 1958267] Re: "Connection failed" for WPA Enterprise network (e.g. eduroam)
it would be easier to wget, dpkg -i the deb rather than change the sources... -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to wpa in Ubuntu. https://bugs.launchpad.net/bugs/1958267 Title: "Connection failed" for WPA Enterprise network (e.g. eduroam) Status in wpa package in Ubuntu: Confirmed Status in wpa source package in Jammy: Confirmed Bug description: With the current jammy version of wpasupplicant (2:2.10-1), I cannot connect to the WPA Enterprise network eduroam, which is used by Universities worldwide. I get a "Connection failed" message or a request to re-enter the password. - I've re-tried the credentials: no fix ;-) - Tried a 21.10 live session on the same machine: works fine! - Manually downgraded wpasupplicant to the impish version (2:2.9.0-21build1): connected normally. - Upgraded wpasupplicant to the latest version: fails to connect again. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: wpasupplicant 2:2.10-1 ProcVersionSignature: Ubuntu 5.15.0-17.17-generic 5.15.12 Uname: Linux 5.15.0-17-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu75 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Jan 18 09:56:23 2022 InstallationDate: Installed on 2021-11-30 (48 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20211130) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: wpa UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1958267/+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 1958267] Re: "Connection failed" for WPA Enterprise network (e.g. eduroam)
For having the command quickly about downgrading wpasupplicant, what solved my issue temporarily: sudo cat <<'EOF' | sudo tee /etc/apt/sources.list.d/impish.list deb http://archive.ubuntu.com/ubuntu/ impish main restricted universe multiverse deb http://archive.ubuntu.com/ubuntu/ impish-updates main restricted universe multiverse deb http://archive.ubuntu.com/ubuntu/ impish-security main restricted universe multiverse EOF sudo apt update sudo apt -y --allow-downgrades install wpasupplicant=2:2.9.0-21build1 sudo apt-mark hold wpasupplicant -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to wpa in Ubuntu. https://bugs.launchpad.net/bugs/1958267 Title: "Connection failed" for WPA Enterprise network (e.g. eduroam) Status in wpa package in Ubuntu: Confirmed Status in wpa source package in Jammy: Confirmed Bug description: With the current jammy version of wpasupplicant (2:2.10-1), I cannot connect to the WPA Enterprise network eduroam, which is used by Universities worldwide. I get a "Connection failed" message or a request to re-enter the password. - I've re-tried the credentials: no fix ;-) - Tried a 21.10 live session on the same machine: works fine! - Manually downgraded wpasupplicant to the impish version (2:2.9.0-21build1): connected normally. - Upgraded wpasupplicant to the latest version: fails to connect again. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: wpasupplicant 2:2.10-1 ProcVersionSignature: Ubuntu 5.15.0-17.17-generic 5.15.12 Uname: Linux 5.15.0-17-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu75 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Jan 18 09:56:23 2022 InstallationDate: Installed on 2021-11-30 (48 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20211130) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: wpa UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1958267/+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 1971158] Re: ssh connect to server stop on "SSH2_MSG_KEXINIT sent"
Status changed to 'Confirmed' because the bug affects multiple users. ** 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/1971158 Title: ssh connect to server stop on "SSH2_MSG_KEXINIT sent" Status in openssh package in Ubuntu: Confirmed Bug description: After upgrade on Ubuntu 22.04 i can't connect to several servers. Connecting stopped on SSH2_MSG_KEXINIT sent ``` ssh -vvv -o KexAlgorithms=diffie-hellman-group-exchange-sha256 -oHostKeyAlgorithms=+ssh-rsa -X vld@sansa OpenSSH_8.9p1 Ubuntu-3, OpenSSL 3.0.2 15 Mar 2022 debug1: Reading configuration data /home/ruslan/.ssh/config debug3: kex names ok: [diffie-hellman-group1-sha1] debug3: kex names ok: [diffie-hellman-group-exchange-sha256,diffie-hellman-group-exchange-sha1,diffie-hellman-group14-sha1,diffie-hellman-group1-sha1] debug3: kex names ok: [diffie-hellman-group1-sha1] debug1: Reading configuration data /etc/ssh/ssh_config debug1: /etc/ssh/ssh_config line 19: include /etc/ssh/ssh_config.d/*.conf matched no files debug1: /etc/ssh/ssh_config line 21: Applying options for * debug3: expanded UserKnownHostsFile '~/.ssh/known_hosts' -> '/home/ruslan/.ssh/known_hosts' debug3: expanded UserKnownHostsFile '~/.ssh/known_hosts2' -> '/home/ruslan/.ssh/known_hosts2' debug2: resolving "sansa" port 22 debug3: resolve_host: lookup sansa:22 debug3: ssh_connect_direct: entering debug1: Connecting to sansa [172.16.xx.xx] port 22. debug3: set_sock_tos: set socket 3 IP_TOS 0x10 debug1: Connection established. debug1: identity file /home/ruslan/.ssh/id_rsa type -1 debug1: identity file /home/ruslan/.ssh/id_rsa-cert type -1 debug1: identity file /home/ruslan/.ssh/id_ecdsa type -1 debug1: identity file /home/ruslan/.ssh/id_ecdsa-cert type -1 debug1: identity file /home/ruslan/.ssh/id_ecdsa_sk type -1 debug1: identity file /home/ruslan/.ssh/id_ecdsa_sk-cert type -1 debug1: identity file /home/ruslan/.ssh/id_ed25519 type -1 debug1: identity file /home/ruslan/.ssh/id_ed25519-cert type -1 debug1: identity file /home/ruslan/.ssh/id_ed25519_sk type -1 debug1: identity file /home/ruslan/.ssh/id_ed25519_sk-cert type -1 debug1: identity file /home/ruslan/.ssh/id_xmss type -1 debug1: identity file /home/ruslan/.ssh/id_xmss-cert type -1 debug1: identity file /home/ruslan/.ssh/id_dsa type -1 debug1: identity file /home/ruslan/.ssh/id_dsa-cert type -1 debug1: Local version string SSH-2.0-OpenSSH_8.9p1 Ubuntu-3 debug1: Remote protocol version 2.0, remote software version OpenSSH_5.3 debug1: compat_banner: match: OpenSSH_5.3 pat OpenSSH_5* compat 0x0c02 debug2: fd 3 setting O_NONBLOCK debug1: Authenticating to sansa:22 as 'vld' debug1: load_hostkeys: fopen /etc/ssh/ssh_known_hosts2: No such file or directory debug3: order_hostkeyalgs: no algorithms matched; accept original debug3: send packet: type 20 debug1: SSH2_MSG_KEXINIT sent ``` I'm checking connection on old version Ubuntu 20.04, it's working. Remote server use KexAlgorithms=diffie-hellman-group-exchange-sha256 and HostKeyAlgorithms=ssh-rsa On Ubuntu 21.04 ssh was work. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1971158/+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 1971418] Re: network-manager/1.36.4-2ubuntu1 ADT test failure with linux/5.15.0-28.29
** Also affects: network-manager (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Jammy) Importance: Undecided Status: New ** Changed in: network-manager (Ubuntu Jammy) Status: New => Invalid ** Changed in: linux (Ubuntu Jammy) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Jammy) Status: New => In Progress ** Changed in: linux (Ubuntu Jammy) Assignee: (unassigned) => Stefan Bader (smb) ** Changed in: linux (Ubuntu) Status: Incomplete => Invalid -- 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/1971418 Title: network-manager/1.36.4-2ubuntu1 ADT test failure with linux/5.15.0-28.29 Status in linux package in Ubuntu: Invalid Status in network-manager package in Ubuntu: Invalid Status in linux source package in Jammy: In Progress Status in network-manager source package in Jammy: Invalid Bug description: This is a scripted bug report about ADT failures while running network-manager tests for linux/5.15.0-28.29 on jammy. Whether this is caused by the dep8 tests of the tested source or the kernel has yet to be determined. Testing failed on: amd64: https://autopkgtest.ubuntu.com/results/autopkgtest-jammy/jammy/amd64/n/network-manager/20220503_090742_432dd@/log.gz arm64: https://autopkgtest.ubuntu.com/results/autopkgtest-jammy/jammy/arm64/n/network-manager/20220429_062345_345a3@/log.gz ppc64el: https://autopkgtest.ubuntu.com/results/autopkgtest-jammy/jammy/ppc64el/n/network-manager/20220429_060513_fc2a9@/log.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1971418/+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 1971418] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window: apport-collect 1971418 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1971418 Title: network-manager/1.36.4-2ubuntu1 ADT test failure with linux/5.15.0-28.29 Status in linux package in Ubuntu: Invalid Status in network-manager package in Ubuntu: Invalid Status in linux source package in Jammy: In Progress Status in network-manager source package in Jammy: Invalid Bug description: This is a scripted bug report about ADT failures while running network-manager tests for linux/5.15.0-28.29 on jammy. Whether this is caused by the dep8 tests of the tested source or the kernel has yet to be determined. Testing failed on: amd64: https://autopkgtest.ubuntu.com/results/autopkgtest-jammy/jammy/amd64/n/network-manager/20220503_090742_432dd@/log.gz arm64: https://autopkgtest.ubuntu.com/results/autopkgtest-jammy/jammy/arm64/n/network-manager/20220429_062345_345a3@/log.gz ppc64el: https://autopkgtest.ubuntu.com/results/autopkgtest-jammy/jammy/ppc64el/n/network-manager/20220429_060513_fc2a9@/log.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1971418/+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 1971418] Re: network-manager/1.36.4-2ubuntu1 ADT test failure with linux/5.15.0-28.29
This seems to be related to: "rfkill: make new event layout opt-in" in the -28 kernel. When I revert that a local reproduction run starts to work again. However I never got the same error pattern as in the ADT logs (those seem to get random data back from trying to read the MAC address). So a little doubt remains. -- 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/1971418 Title: network-manager/1.36.4-2ubuntu1 ADT test failure with linux/5.15.0-28.29 Status in linux package in Ubuntu: New Status in network-manager package in Ubuntu: Invalid Bug description: This is a scripted bug report about ADT failures while running network-manager tests for linux/5.15.0-28.29 on jammy. Whether this is caused by the dep8 tests of the tested source or the kernel has yet to be determined. Testing failed on: amd64: https://autopkgtest.ubuntu.com/results/autopkgtest-jammy/jammy/amd64/n/network-manager/20220503_090742_432dd@/log.gz arm64: https://autopkgtest.ubuntu.com/results/autopkgtest-jammy/jammy/arm64/n/network-manager/20220429_062345_345a3@/log.gz ppc64el: https://autopkgtest.ubuntu.com/results/autopkgtest-jammy/jammy/ppc64el/n/network-manager/20220429_060513_fc2a9@/log.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1971418/+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 1971418] [NEW] network-manager/1.36.4-2ubuntu1 ADT test failure with linux/5.15.0-28.29
Public bug reported: This is a scripted bug report about ADT failures while running network- manager tests for linux/5.15.0-28.29 on jammy. Whether this is caused by the dep8 tests of the tested source or the kernel has yet to be determined. Testing failed on: amd64: https://autopkgtest.ubuntu.com/results/autopkgtest-jammy/jammy/amd64/n/network-manager/20220503_090742_432dd@/log.gz arm64: https://autopkgtest.ubuntu.com/results/autopkgtest-jammy/jammy/arm64/n/network-manager/20220429_062345_345a3@/log.gz ppc64el: https://autopkgtest.ubuntu.com/results/autopkgtest-jammy/jammy/ppc64el/n/network-manager/20220429_060513_fc2a9@/log.gz ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Affects: network-manager (Ubuntu) Importance: Undecided Status: Invalid ** Tags: kernel-adt-failure ** Tags added: kernel-adt-failure ** Changed in: network-manager (Ubuntu) Status: New => Invalid -- 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/1971418 Title: network-manager/1.36.4-2ubuntu1 ADT test failure with linux/5.15.0-28.29 Status in linux package in Ubuntu: New Status in network-manager package in Ubuntu: Invalid Bug description: This is a scripted bug report about ADT failures while running network-manager tests for linux/5.15.0-28.29 on jammy. Whether this is caused by the dep8 tests of the tested source or the kernel has yet to be determined. Testing failed on: amd64: https://autopkgtest.ubuntu.com/results/autopkgtest-jammy/jammy/amd64/n/network-manager/20220503_090742_432dd@/log.gz arm64: https://autopkgtest.ubuntu.com/results/autopkgtest-jammy/jammy/arm64/n/network-manager/20220429_062345_345a3@/log.gz ppc64el: https://autopkgtest.ubuntu.com/results/autopkgtest-jammy/jammy/ppc64el/n/network-manager/20220429_060513_fc2a9@/log.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1971418/+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 1971288] Re: Merge libseccomp from Debian unstable for kinetic
I uploaded https://launchpad.net/ubuntu/+source/libseccomp/2.5.4-1ubuntu1 earlier today. ** Changed in: libseccomp (Ubuntu) Status: New => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libseccomp in Ubuntu. https://bugs.launchpad.net/bugs/1971288 Title: Merge libseccomp from Debian unstable for kinetic Status in libseccomp package in Ubuntu: Fix Committed Bug description: Upstream: tbd Debian: 2.5.4-1 Ubuntu: 2.5.3-2ubuntu2 ### Old Ubuntu Delta ### libseccomp (2.5.3-2ubuntu2) jammy; urgency=medium * No-change rebuild with Python 3.10 only -- Graham Inggs Thu, 17 Mar 2022 19:27:18 + libseccomp (2.5.3-2ubuntu1) jammy; urgency=medium * Merge from Debian unstable; remaining changes: - Add autopkgtests * Added changes: - Update autopkgtests to use syscalls from 5.16-rc1 -- Alex Murray Thu, 24 Feb 2022 09:53:35 +1030 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libseccomp/+bug/1971288/+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 1971409] [NEW] value_copy: Assertion `arg->contents != nullptr' failed.
Public bug reported: When debugging RP2040 with vscode this assert makes gdb crash. This is a new assert, that wasn't present in gdb 11. The fix is easy, replace `if (!value_lazy (val))` to `if (!value_lazy (val) && arg->contents != nullptr) `. ** Affects: gdb (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gdb in Ubuntu. https://bugs.launchpad.net/bugs/1971409 Title: value_copy: Assertion `arg->contents != nullptr' failed. Status in gdb package in Ubuntu: New Bug description: When debugging RP2040 with vscode this assert makes gdb crash. This is a new assert, that wasn't present in gdb 11. The fix is easy, replace `if (!value_lazy (val))` to `if (!value_lazy (val) && arg->contents != nullptr) `. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdb/+bug/1971409/+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 1971146] Re: [radeon] Pictures including wallpaper not showing
Great. Next would be to try 5.14/ and 5.13.9/ (because it is halfway between 5.13 and 5.14) ** No longer affects: mesa (Ubuntu) ** Tags added: regression-release -- 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/1971146 Title: [radeon] Pictures including wallpaper not showing Status in linux package in Ubuntu: Confirmed Bug description: I can't see pictures in emails or on some pictures on websites. Sometimes it just shows the bottom 20mm of pictures. The wallpaper is just a blank white screen. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Uname: Linux 5.15.0-27-generic x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon May 2 13:12:31 2022 DistUpgraded: 2022-04-24 19:05:38,365 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: jammy DistroVariant: ubuntu DkmsStatus: virtualbox/6.1.32, 5.15.0-25-generic, x86_64: installed virtualbox/6.1.32, 5.15.0-27-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Venus XT [Radeon HD 8870M / R9 M270X/M370X] [1002:6821] (rev 83) (prog-if 00 [VGA controller]) Subsystem: Apple Inc. Radeon R9 M370X Mac Edition [106b:0149] InstallationDate: Installed on 2021-04-26 (371 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) Lsusb: Bus 002 Device 003: ID 05ac:8406 Apple, Inc. Internal Memory Card Reader Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 05ac:8290 Apple, Inc. Bluetooth Host Controller Bus 001 Device 003: ID 05ac:0274 Apple, Inc. Apple Internal Keyboard / Trackpad Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Apple Inc. MacBookPro11,5 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-27-generic root=UUID=2234e6d3-3ebc-44e6-b0a5-bef132fd1f72 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to jammy on 2022-04-24 (7 days ago) dmi.bios.date: 06/11/2020 dmi.bios.release: 0.1 dmi.bios.vendor: Apple Inc. dmi.bios.version: 199.0.0.0.0 dmi.board.name: Mac-06F11F11946D27C5 dmi.board.vendor: Apple Inc. dmi.board.version: MacBookPro11,5 dmi.chassis.type: 9 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-06F11F11946D27C5 dmi.modalias: dmi:bvnAppleInc.:bvr199.0.0.0.0:bd06/11/2020:br0.1:svnAppleInc.:pnMacBookPro11,5:pvr1.0:rvnAppleInc.:rnMac-06F11F11946D27C5:rvrMacBookPro11,5:cvnAppleInc.:ct9:cvrMac-06F11F11946D27C5:sku: dmi.product.family: MacBook Pro dmi.product.name: MacBookPro11,5 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.110-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.1-1ubuntu2 version.libgl1-mesa-glx: libgl1-mesa-glx 22.0.1-1ubuntu2 version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1971146/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
Re: [Touch-packages] [Bug 1971146] Re: [radeon] Pictures including wallpaper not showing
No problem with kernel: 5.13.0-051300-generic On 03/05/2022 08:21, Daniel van Vugt wrote: > Yes it seems to be specific to 'radeon' which is both a kernel driver > and a Mesa driver. > -- 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/1971146 Title: [radeon] Pictures including wallpaper not showing Status in linux package in Ubuntu: Confirmed Status in mesa package in Ubuntu: New Bug description: I can't see pictures in emails or on some pictures on websites. Sometimes it just shows the bottom 20mm of pictures. The wallpaper is just a blank white screen. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Uname: Linux 5.15.0-27-generic x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon May 2 13:12:31 2022 DistUpgraded: 2022-04-24 19:05:38,365 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: jammy DistroVariant: ubuntu DkmsStatus: virtualbox/6.1.32, 5.15.0-25-generic, x86_64: installed virtualbox/6.1.32, 5.15.0-27-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Venus XT [Radeon HD 8870M / R9 M270X/M370X] [1002:6821] (rev 83) (prog-if 00 [VGA controller]) Subsystem: Apple Inc. Radeon R9 M370X Mac Edition [106b:0149] InstallationDate: Installed on 2021-04-26 (371 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) Lsusb: Bus 002 Device 003: ID 05ac:8406 Apple, Inc. Internal Memory Card Reader Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 05ac:8290 Apple, Inc. Bluetooth Host Controller Bus 001 Device 003: ID 05ac:0274 Apple, Inc. Apple Internal Keyboard / Trackpad Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Apple Inc. MacBookPro11,5 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-27-generic root=UUID=2234e6d3-3ebc-44e6-b0a5-bef132fd1f72 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to jammy on 2022-04-24 (7 days ago) dmi.bios.date: 06/11/2020 dmi.bios.release: 0.1 dmi.bios.vendor: Apple Inc. dmi.bios.version: 199.0.0.0.0 dmi.board.name: Mac-06F11F11946D27C5 dmi.board.vendor: Apple Inc. dmi.board.version: MacBookPro11,5 dmi.chassis.type: 9 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-06F11F11946D27C5 dmi.modalias: dmi:bvnAppleInc.:bvr199.0.0.0.0:bd06/11/2020:br0.1:svnAppleInc.:pnMacBookPro11,5:pvr1.0:rvnAppleInc.:rnMac-06F11F11946D27C5:rvrMacBookPro11,5:cvnAppleInc.:ct9:cvrMac-06F11F11946D27C5:sku: dmi.product.family: MacBook Pro dmi.product.name: MacBookPro11,5 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.110-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.1-1ubuntu2 version.libgl1-mesa-glx: libgl1-mesa-glx 22.0.1-1ubuntu2 version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1971146/+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 1593407] Re: Guest session cannot run snaps
** Changed in: ubuntu-mate Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1593407 Title: Guest session cannot run snaps Status in Light Display Manager: Confirmed Status in Snappy: Confirmed Status in Ubuntu MATE: Confirmed Status in firefox package in Ubuntu: Confirmed Status in lightdm package in Ubuntu: Confirmed Status in snapd package in Ubuntu: Confirmed Status in firefox source package in Xenial: Confirmed Status in lightdm source package in Xenial: Confirmed Status in snapd source package in Xenial: Confirmed Bug description: I'm using Ubuntu 16.04. The guest session cannot execute snaps, because of a permission error. The LightDM's guest session AppArmor profile is not allowing access to /snap and other needed files and folders. To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/1593407/+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 1593407] Re: Guest session cannot run snaps
6 Year old Bug, really? I am frustrated with Ubuntu. Don't change firefox to a snap package when you have problems like this canonical -__- -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1593407 Title: Guest session cannot run snaps Status in Light Display Manager: Confirmed Status in Snappy: Confirmed Status in Ubuntu MATE: New Status in firefox package in Ubuntu: Confirmed Status in lightdm package in Ubuntu: Confirmed Status in snapd package in Ubuntu: Confirmed Status in firefox source package in Xenial: Confirmed Status in lightdm source package in Xenial: Confirmed Status in snapd source package in Xenial: Confirmed Bug description: I'm using Ubuntu 16.04. The guest session cannot execute snaps, because of a permission error. The LightDM's guest session AppArmor profile is not allowing access to /snap and other needed files and folders. To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/1593407/+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 1593407] Re: Guest session cannot run snaps
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: snapd (Ubuntu Xenial) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1593407 Title: Guest session cannot run snaps Status in Light Display Manager: Confirmed Status in Snappy: Confirmed Status in Ubuntu MATE: New Status in firefox package in Ubuntu: Confirmed Status in lightdm package in Ubuntu: Confirmed Status in snapd package in Ubuntu: Confirmed Status in firefox source package in Xenial: Confirmed Status in lightdm source package in Xenial: Confirmed Status in snapd source package in Xenial: Confirmed Bug description: I'm using Ubuntu 16.04. The guest session cannot execute snaps, because of a permission error. The LightDM's guest session AppArmor profile is not allowing access to /snap and other needed files and folders. To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/1593407/+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 1593407] Re: Guest session cannot run snaps
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: lightdm (Ubuntu Xenial) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1593407 Title: Guest session cannot run snaps Status in Light Display Manager: Confirmed Status in Snappy: Confirmed Status in Ubuntu MATE: New Status in firefox package in Ubuntu: Confirmed Status in lightdm package in Ubuntu: Confirmed Status in snapd package in Ubuntu: Confirmed Status in firefox source package in Xenial: Confirmed Status in lightdm source package in Xenial: Confirmed Status in snapd source package in Xenial: Confirmed Bug description: I'm using Ubuntu 16.04. The guest session cannot execute snaps, because of a permission error. The LightDM's guest session AppArmor profile is not allowing access to /snap and other needed files and folders. To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/1593407/+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 1593407] Re: Guest session cannot run snaps
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: firefox (Ubuntu Xenial) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1593407 Title: Guest session cannot run snaps Status in Light Display Manager: Confirmed Status in Snappy: Confirmed Status in Ubuntu MATE: New Status in firefox package in Ubuntu: Confirmed Status in lightdm package in Ubuntu: Confirmed Status in snapd package in Ubuntu: Confirmed Status in firefox source package in Xenial: Confirmed Status in lightdm source package in Xenial: Confirmed Status in snapd source package in Xenial: Confirmed Bug description: I'm using Ubuntu 16.04. The guest session cannot execute snaps, because of a permission error. The LightDM's guest session AppArmor profile is not allowing access to /snap and other needed files and folders. To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/1593407/+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 1593407] Re: Guest session cannot run snaps
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: firefox (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1593407 Title: Guest session cannot run snaps Status in Light Display Manager: Confirmed Status in Snappy: Confirmed Status in Ubuntu MATE: New Status in firefox package in Ubuntu: Confirmed Status in lightdm package in Ubuntu: Confirmed Status in snapd package in Ubuntu: Confirmed Status in firefox source package in Xenial: Confirmed Status in lightdm source package in Xenial: Confirmed Status in snapd source package in Xenial: Confirmed Bug description: I'm using Ubuntu 16.04. The guest session cannot execute snaps, because of a permission error. The LightDM's guest session AppArmor profile is not allowing access to /snap and other needed files and folders. To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/1593407/+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 1593407] Re: Guest session cannot run snaps
This is fantastically cool decision to ship pre-installed Firefox web-browser as Snap. It can't be started on freshly installed Ubuntu MATE 22.04 LTS. Very smart and efficient idea. Very useful for internet kiosks. ``` guest-t2chxy@m:~/Desktop$ firefox 2022/05/03 10:18:59.480499 tool_linux.go:82: cannot open snapd info file "/snap/snapd/current/usr/lib/snapd/info": open /snap/snapd/current/usr/lib/snapd/info: permission denied guest-t2chxy@m:~/Desktop$ snap list 2022/05/03 10:26:00.694252 tool_linux.go:82: cannot open snapd info file "/snap/snapd/current/usr/lib/snapd/info": open /snap/snapd/current/usr/lib/snapd/info: permission denied ``` I can confirm this bug on Ubuntu MATE 22.04 LTS. Should you plan to fix it? ** Changed in: snapd (Ubuntu) Status: Triaged => Confirmed ** Changed in: lightdm (Ubuntu) Status: Triaged => Confirmed ** Tags added: bionic focal impish jammy ** Also affects: ubuntu-mate Importance: Undecided Status: New ** Also affects: firefox (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1593407 Title: Guest session cannot run snaps Status in Light Display Manager: Confirmed Status in Snappy: Confirmed Status in Ubuntu MATE: New Status in firefox package in Ubuntu: New Status in lightdm package in Ubuntu: Confirmed Status in snapd package in Ubuntu: Confirmed Status in firefox source package in Xenial: New Status in lightdm source package in Xenial: New Status in snapd source package in Xenial: New Bug description: I'm using Ubuntu 16.04. The guest session cannot execute snaps, because of a permission error. The LightDM's guest session AppArmor profile is not allowing access to /snap and other needed files and folders. To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/1593407/+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 1971112] Re: File picker gets bigger more and more each time!
Is that on an xorg session? If so it sounds like https://gitlab.gnome.org/GNOME/gtk/-/issues/4136 ** Bug watch added: gitlab.gnome.org/GNOME/gtk/-/issues #4136 https://gitlab.gnome.org/GNOME/gtk/-/issues/4136 ** Package changed: nautilus (Ubuntu) => gtk+3.0 (Ubuntu) ** Changed in: gtk+3.0 (Ubuntu) Importance: Undecided => High -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1971112 Title: File picker gets bigger more and more each time! Status in gtk+3.0 package in Ubuntu: Confirmed Bug description: Hello. I've just switched to Ubuntu and ever since day 1 I had this issue that whenever I tried to choose a file the file picker window was way too big and it was getting bigger and bigger each time. I have posted a video on Reddit recording this unusual/unexpected behavior. Here is the reddit post link (with video): https://www.reddit.com/r/Ubuntu/comments/ug97qx/annoying_bug_file_picker_gets_bigger_more_and/ I've also attached the video to this post, in case you don't want to click the link above. Here is my neofetch output: OS: Ubuntu 22.04 LTS x86_64 Kernel: 5.15.0-27-generic Uptime: 13 hours, 13 mins Shell: bash 5.1.16 Resolution: 1440x900, 1920x1080 DE: GNOME 42.0 WM: Mutter WM Theme: Adwaita Theme: Yaru-viridian-dark [GTK2/3] Icons: Yaru-viridian [GTK2/3] Terminal: gnome-terminal CPU: Intel i7-8700K (12) @ 4.700GHz GPU: NVIDIA GeForce GTX 1060 3GB Memory: 5869MiB / 15936MiB To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1971112/+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 1971146] Re: [radeon] Pictures including wallpaper not showing
Yes it seems to be specific to 'radeon' which is both a kernel driver and a Mesa driver. -- 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/1971146 Title: [radeon] Pictures including wallpaper not showing Status in linux package in Ubuntu: Confirmed Status in mesa package in Ubuntu: New Bug description: I can't see pictures in emails or on some pictures on websites. Sometimes it just shows the bottom 20mm of pictures. The wallpaper is just a blank white screen. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Uname: Linux 5.15.0-27-generic x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon May 2 13:12:31 2022 DistUpgraded: 2022-04-24 19:05:38,365 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: jammy DistroVariant: ubuntu DkmsStatus: virtualbox/6.1.32, 5.15.0-25-generic, x86_64: installed virtualbox/6.1.32, 5.15.0-27-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Venus XT [Radeon HD 8870M / R9 M270X/M370X] [1002:6821] (rev 83) (prog-if 00 [VGA controller]) Subsystem: Apple Inc. Radeon R9 M370X Mac Edition [106b:0149] InstallationDate: Installed on 2021-04-26 (371 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) Lsusb: Bus 002 Device 003: ID 05ac:8406 Apple, Inc. Internal Memory Card Reader Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 05ac:8290 Apple, Inc. Bluetooth Host Controller Bus 001 Device 003: ID 05ac:0274 Apple, Inc. Apple Internal Keyboard / Trackpad Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Apple Inc. MacBookPro11,5 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-27-generic root=UUID=2234e6d3-3ebc-44e6-b0a5-bef132fd1f72 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to jammy on 2022-04-24 (7 days ago) dmi.bios.date: 06/11/2020 dmi.bios.release: 0.1 dmi.bios.vendor: Apple Inc. dmi.bios.version: 199.0.0.0.0 dmi.board.name: Mac-06F11F11946D27C5 dmi.board.vendor: Apple Inc. dmi.board.version: MacBookPro11,5 dmi.chassis.type: 9 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-06F11F11946D27C5 dmi.modalias: dmi:bvnAppleInc.:bvr199.0.0.0.0:bd06/11/2020:br0.1:svnAppleInc.:pnMacBookPro11,5:pvr1.0:rvnAppleInc.:rnMac-06F11F11946D27C5:rvrMacBookPro11,5:cvnAppleInc.:ct9:cvrMac-06F11F11946D27C5:sku: dmi.product.family: MacBook Pro dmi.product.name: MacBookPro11,5 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.110-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.1-1ubuntu2 version.libgl1-mesa-glx: libgl1-mesa-glx 22.0.1-1ubuntu2 version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1971146/+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 1971112] [NEW] File picker gets bigger more and more each time!
You have been subscribed to a public bug: Hello. I've just switched to Ubuntu and ever since day 1 I had this issue that whenever I tried to choose a file the file picker window was way too big and it was getting bigger and bigger each time. I have posted a video on Reddit recording this unusual/unexpected behavior. Here is the reddit post link (with video): https://www.reddit.com/r/Ubuntu/comments/ug97qx/annoying_bug_file_picker_gets_bigger_more_and/ I've also attached the video to this post, in case you don't want to click the link above. Here is my neofetch output: OS: Ubuntu 22.04 LTS x86_64 Kernel: 5.15.0-27-generic Uptime: 13 hours, 13 mins Shell: bash 5.1.16 Resolution: 1440x900, 1920x1080 DE: GNOME 42.0 WM: Mutter WM Theme: Adwaita Theme: Yaru-viridian-dark [GTK2/3] Icons: Yaru-viridian [GTK2/3] Terminal: gnome-terminal CPU: Intel i7-8700K (12) @ 4.700GHz GPU: NVIDIA GeForce GTX 1060 3GB Memory: 5869MiB / 15936MiB ** Affects: gtk+3.0 (Ubuntu) Importance: High Status: Confirmed ** Tags: bot-comment gnome nautilus -- File picker gets bigger more and more each time! https://bugs.launchpad.net/bugs/1971112 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1971280] [NEW] Merge heimdal from Debian unstable for kinetic
Public bug reported: Upstream: tbd Debian: 7.7.0+dfsg-3 Ubuntu: 7.7.0+dfsg-3ubuntu1 ### New Debian Changes ### heimdal (7.7.0+dfsg-3) unstable; urgency=high * Fix CVE-2021-3671: A null pointer de-reference was found in the way samba kerberos server handled missing sname in TGS-REQ. Closes: #996586. * Fix autoconf 2.7 issues. -- Brian May Wed, 17 Nov 2021 12:12:45 +1100 heimdal (7.7.0+dfsg-2) unstable; urgency=medium * Build using python3. Closes: #936695, #960032. -- Brian May Tue, 12 May 2020 06:56:04 +1000 heimdal (7.7.0+dfsg-1) unstable; urgency=medium * New upstream version. * Fix CVE-2019-14870: The DelegationNotAllowed Kerberos feature restriction was not being applied when processing protocol transition requests (S4U2Self), in the AD DC KDC. Closes: #946786. -- Brian May Tue, 17 Dec 2019 20:23:41 +1100 heimdal (7.5.0+dfsg-3) unstable; urgency=high * CVE-2018-16860: Samba AD DC S4U2Self/S4U2Proxy unkeyed checksum. Closes: #928966. * CVE-2019-12098: Always confirm PA-PKINIT-KX for anon PKINIT. Closes: #929064. * Update test certificates to pre 2038 expiry. Closes: #923930. -- Brian May Tue, 21 May 2019 18:04:35 +1000 heimdal (7.5.0+dfsg-2.1) unstable; urgency=medium * Non-maintainer upload * Add patch to create headers before building (Closes: 906623) -- Hilko Bengen Sun, 28 Oct 2018 15:10:44 +0100 heimdal (7.5.0+dfsg-2) unstable; urgency=medium * Replace 'MAXHOSTNAMELEN' with 'MaxHostNameLen' in kdc/kx509.c for The Hurd. Closes: #900079. -- Brian May Sat, 02 Jun 2018 10:01:46 +1000 heimdal (7.5.0+dfsg-1) unstable; urgency=high * New upstream version. (Closes: #850723) + CVE-2017-17439: Remote unauthenticated DoS in Heimdal-KDC 7.4 (Closes: #878144, #868157) + Refresh patches. * Bump Standards-Version to 4.1.2 and compat level to 10. + Remove explicit reference to dh-autoreconf. * Use uscan to get orig source. + Refrain from mangling some bundled RFC texts; just exclude the mas they are not installed into any binary anyway. + Update d/copyright to DEP-5. + Can now use standard uscan/gbp/pristine-tar workflow. * Fix some lintian errors/warnings. + Strip trailing whitespace from changelog. + Fix some duplicate long descriptions. + Use optional priority everywhere. + Update/remove some overrides. + Enforce set -e in maintainer scripts. + Enable hardening. * Migrate to -dbgsym. * Add myself to uploaders. -- Dominik George Fri, 15 Dec 2017 01:13:04 +0100 heimdal (7.4.0.dfsg.1-2) unstable; urgency=medium [ Jelmer Vernooij ] * Remove myself from uploaders. [ Brian May ] * Be explicit with heimdal.mkey filename in postinst. Closes: #868638. * Tests should respect DEB_BUILD_OPTIONS=nocheck. Closes: #868842. -- Brian May Sun, 23 Jul 2017 10:32:34 +1000 heimdal (7.4.0.dfsg.1-1) unstable; urgency=high * New upstream version. * Update standards version to 4.0.0. * CVE-2017-11103: Fix Orpheus' Lyre KDC-REP service name validation. (Closes: #868208). -- Brian May Sat, 15 Jul 2017 19:47:32 +1000 heimdal (7.1.0+dfsg-13) unstable; urgency=medium * Add missing symbols base64_decode and base64_encode back into libroken. Closes: #848694. -- Brian May Wed, 26 Apr 2017 19:38:20 +1000 heimdal (7.1.0+dfsg-12) unstable; urgency=high ### Old Ubuntu Delta ### heimdal (7.7.0+dfsg-3ubuntu1) jammy; urgency=medium * Merge with Debian unstable (LP: #1946860). Remaining changes: - Disable lto, to regain dep on roken, otherwise dependencies on amd64 are different to i386 resulting in different files on amd64 and i386. LP #1934936 - Remove symbol rk_closefrom@HEIMDAL_ROKEN_1.0 1.4.0+git20110226 (LP #1945787) -- Andreas Hasenack Wed, 08 Dec 2021 18:02:13 -0300 ** Affects: heimdal (Ubuntu) Importance: Undecided Status: New ** Tags: needs-merge upgrade-software-version ** Changed in: heimdal (Ubuntu) Milestone: None => ubuntu-22.05 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to heimdal in Ubuntu. https://bugs.launchpad.net/bugs/1971280 Title: Merge heimdal from Debian unstable for kinetic Status in heimdal package in Ubuntu: New Bug description: Upstream: tbd Debian: 7.7.0+dfsg-3 Ubuntu: 7.7.0+dfsg-3ubuntu1 ### New Debian Changes ### heimdal (7.7.0+dfsg-3) unstable; urgency=high * Fix CVE-2021-3671: A null pointer de-reference was found in the way samba kerberos server handled missing sname in TGS-REQ. Closes: #996586. * Fix autoconf 2.7 issues. -- Brian May Wed, 17 Nov 2021 12:12:45 +1100 heimdal (7.7.0+dfsg-2) unstable; urgency=medium * Build using python3. Closes: #936695, #960032. -- Brian May Tue, 12 May 2020 06:56:04 +1000 heimdal (7.7.0+dfsg-1) unstable; urgency=medium * New upstream version. * Fix
[Touch-packages] [Bug 1971288] [NEW] Merge libseccomp from Debian unstable for kinetic
Public bug reported: Upstream: tbd Debian: 2.5.4-1 Ubuntu: 2.5.3-2ubuntu2 ### Old Ubuntu Delta ### libseccomp (2.5.3-2ubuntu2) jammy; urgency=medium * No-change rebuild with Python 3.10 only -- Graham Inggs Thu, 17 Mar 2022 19:27:18 + libseccomp (2.5.3-2ubuntu1) jammy; urgency=medium * Merge from Debian unstable; remaining changes: - Add autopkgtests * Added changes: - Update autopkgtests to use syscalls from 5.16-rc1 -- Alex Murray Thu, 24 Feb 2022 09:53:35 +1030 ** Affects: libseccomp (Ubuntu) Importance: Undecided Status: New ** Tags: needs-merge upgrade-software-version ** Changed in: libseccomp (Ubuntu) Milestone: None => later -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libseccomp in Ubuntu. https://bugs.launchpad.net/bugs/1971288 Title: Merge libseccomp from Debian unstable for kinetic Status in libseccomp package in Ubuntu: New Bug description: Upstream: tbd Debian: 2.5.4-1 Ubuntu: 2.5.3-2ubuntu2 ### Old Ubuntu Delta ### libseccomp (2.5.3-2ubuntu2) jammy; urgency=medium * No-change rebuild with Python 3.10 only -- Graham Inggs Thu, 17 Mar 2022 19:27:18 + libseccomp (2.5.3-2ubuntu1) jammy; urgency=medium * Merge from Debian unstable; remaining changes: - Add autopkgtests * Added changes: - Update autopkgtests to use syscalls from 5.16-rc1 -- Alex Murray Thu, 24 Feb 2022 09:53:35 +1030 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libseccomp/+bug/1971288/+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 1971296] [NEW] Merge net-tools from Debian unstable for kinetic
Public bug reported: Upstream: tbd Debian: 1.60+git20181103.0eebece-1 Ubuntu: 1.60+git20181103.0eebece-1ubuntu5 ### New Debian Changes ### net-tools (1.60+git20181103.0eebece-1) unstable; urgency=medium * New upstream version 1.60+git20181103.0eebece - Fix nstrcmp() to prevent ifconfig from showing duplicate interfaces. (Closes: #812886) * Fix d/watch to point to upstream git repository * Add patch to fix decoding of MII vendor ids. (Closes: #549397) - Thanks, Ben Hutchings, for the patch. * Add patch to fix Japanese translation which uses a wrong Kanji character. (Closes: #621752) - Thanks, Takeshi Hamasaki, for the patch. * Add patch to fix wrong indentation of 'collisions' in the Japanese translation. (Closes: #653117) - Thanks, NODA, Kai, for the patch. * Fix Uploaders' field. - Add myself as an uploader. - Fix Tina's details. -- Utkarsh Gupta Fri, 02 Oct 2020 15:01:04 +0530 net-tools (1.60+git20180626.aebd88e-1) unstable; urgency=medium * New upstream snapshot * Refresh patches. * Fix typos in German manpages. Thanks to Prof. Dr. Steffen Wendzel and Dr. Tobias Quathamer for the patch. Closes: #900962. -- Martín Ferrari Mon, 24 Sep 2018 19:08:57 + net-tools (1.60+git20161116.90da8a0-4) unstable; urgency=medium * Update maintainer email address. Closes: #899617. * Update Standards-Version with no changes. -- Martín Ferrari Mon, 24 Sep 2018 17:16:31 + net-tools (1.60+git20161116.90da8a0-3) unstable; urgency=medium * debian/control: Update Vcs-* and Standards-Version. * debian/control: remove references to ancient package ja-trans. * debian/gbp.conf: Update repo layout. -- Martín Ferrari Tue, 31 Jul 2018 19:09:00 + net-tools (1.60+git20161116.90da8a0-2) unstable; urgency=medium * Fix typo in French manpage. Thanks to Michel Grigaut for the patch. * Add manpage for iptunnel, thanks to Sergio Durigan Junior. Closes: #88910 * Rename patches so CME does not choke on them. * Automated cme fixes; packaging improvements. * Remove unused and ancient patch. -- Martín Ferrari Sun, 11 Feb 2018 17:29:24 + net-tools (1.60+git20161116.90da8a0-1) unstable; urgency=medium * New upstream snapshot. * Re-synced translations.patch. * Acknowledge NMUs. Thanks a lot to Andrey Rahmatullin for the fixes and uploads. Closes: 846509. * Fix FTCBFS, thanks to Helmut Grohne for the patch. Closes: #811561. + Really assign CC for cross compilation. + Use triplet prefixed pkg-config. * Add debian/NEWS warning about changing output in net-tools commands. Closing bugs that reported problems in 3rd-party scripts arising from these changes. Closes: #845153, #843892, #820212. * Update Standards-Version, with no changes. -- Martín Ferrari Mon, 26 Dec 2016 05:58:42 + net-tools (1.60+git20150829.73cef8a-2.2) unstable; urgency=medium * Non-maintainer upload. * Apply an additional fix for the previous FTBFS for some architectures. -- Andrey Rahmatullin Thu, 01 Dec 2016 22:49:27 +0500 net-tools (1.60+git20150829.73cef8a-2.1) unstable; urgency=medium * Non-maintainer upload. * Fix FTBFS by applying the upstream patch (Closes: #844073). -- Andrey Rahmatullin Sun, 20 Nov 2016 15:23:12 +0500 net-tools (1.60+git20150829.73cef8a-2) unstable; urgency=medium [ Laurent Bigonville ] * Enable SELinux support. Closes: #666204. [ Martín Ferrari ] * Mark the package 'Multi-Arch: foreign', thanks to Frédéric Brière . Closes: #752584. * Fix bug in Portuguese man page, thanks to julianofisc...@gmail.com. Closes: #805377. -- Martín Ferrari Thu, 19 Nov 2015 14:48:47 + net-tools (1.60+git20150829.73cef8a-1) unstable; urgency=medium ### Old Ubuntu Delta ### net-tools (1.60+git20181103.0eebece-1ubuntu5) jammy; urgency=high * No change rebuild for ppc64el baseline bump. -- Julian Andres Klode Thu, 24 Mar 2022 17:20:48 +0100 net-tools (1.60+git20181103.0eebece-1ubuntu4) jammy; urgency=low * Add new DEP8 tests for hostname and ifconfig (LP: #1679346): - d/t/control: add hostname-set-get and ifconfig-lo-info - d/t/hostname-set-get: new test - d/t/ifconfig-lo-info: new test -- Lena Voytek Fri, 22 Oct 2021 07:49:06 -0700 net-tools (1.60+git20181103.0eebece-1ubuntu3) impish; urgency=medium * No-change rebuild to build packages with zstd compression. -- Matthias Klose Thu, 07 Oct 2021 12:21:22 +0200 net-tools (1.60+git20181103.0eebece-1ubuntu2) hirsute; urgency=medium * No change rebuild with fixed ownership. -- Dimitri John Ledkov Tue, 16 Feb 2021 15:18:30 + net-tools (1.60+git20181103.0eebece-1ubuntu1) hirsute; urgency=low * Merge from Debian unstable. Remaining changes: - Ubuntu_unit_conversion.patch: + Ubuntu Policy: output using standard SI unit multiples: KB (10^3), MB (10^6), GB (10^9), TB (10^12) and PB (10^15). Includes manpage update to remove comment
[Touch-packages] [Bug 1971299] [NEW] Merge nss from Debian unstable for kinetic
Public bug reported: Upstream: tbd Debian: 2:3.77-1 Ubuntu: 2:3.68.2-0ubuntu1 ### New Debian Changes ### nss (2:3.77-1) unstable; urgency=medium * New upstream release. * debian/libnss3.symbols: Add NSS_3.77 symbol version. -- Mike Hommey Wed, 06 Apr 2022 09:18:22 +0900 nss (2:3.75-1) unstable; urgency=medium * New upstream release. -- Mike Hommey Wed, 09 Feb 2022 08:46:51 +0900 nss (2:3.73.1-1) unstable; urgency=medium * New upstream release. -- Mike Hommey Fri, 17 Dec 2021 06:16:55 +0900 nss (2:3.73-1) unstable; urgency=medium * New upstream release. * Fixes MFSA-2021-51, aka CVE-2021-43527: Memory corruption via DER-encoded DSA and RSA-PSS signatures. -- Mike Hommey Thu, 02 Dec 2021 06:04:31 +0900 nss (2:3.72-2) unstable; urgency=medium * debian/control: libnss3-dev breaks libxmlsec1-dev (<< 1.2.33-1). Closes: #998733. -- Mike Hommey Fri, 12 Nov 2021 06:21:05 +0900 nss (2:3.72-1) unstable; urgency=medium * New upstream release. * debian/libnss3.symbols, nss/lib/ssl/sslinfo.c, nss/lib/ssl/sslt.h, nss/cmd/selfserv/selfserv.c, nss/cmd/strsclnt/strsclnt.c, nss/cmd/tstclnt/tstclnt.c: Bump dependency version for SSL_GetChannelInfo symbol and remove the previous workaround. Closes: #990058. * debian/libnss3.lintian-overrides.in, debian/rules, nss/cmd/shlibsign/shlibsign.c, nss/lib/pk11wrap/pk11load.c, nss/lib/util/secload.c, nss/cmd/shlibsign/Makefile, nss/cmd/shlibsign/manifest.mn: Stop putting freebl, softokn, etc. in a subdirectory. It's a deviation from upstream that is causing more problems than it's worth keeping. Closes: #737855, #846012, #979159. * debian/libnss3-dev.links.in: Remove xulrunner-nss.pc. * debian/rules: Stop forcing xz compression. * debian/copyright: Add dot for continuation. * debian/watch: Upgrade to version 4. * debian/control: Upgrade Standard-Version to 4.6.0: - debian/rules: Build with `make -s` when DEB_BUILD_OPTIONS contains terse. - debian/control: Add Rules-Requires-Root: no. * debian/control: Remove conflict with libnss3-1d. The last Debian version with libnss3-1d was jessie, and it had a newer version anyways. * debian/rules: Enable all hardening options. * debian/libnss3-symbols: Add Build-Depends-Package in symbols file. * debian/*.lintian-overrides*: Remove copyright-refers-to-versionless-license-file lintian overrides. * debian/libnss3.lintian-overrides.in: - s/shlib-without-versioned-soname/shared-library-lacks-version/. - Add lacks-unversioned-link-to-shared-library overrides. * debian/nss-config.in, debian/rules: Ship upstream nss-config instead of ours. Closes: #737855, #963136. * debian/rules, debian/control: Always set Multi-Arch: same. * debian/copyright: - Remove commas in `Files`. - Add missing license name for ifparser. - Add missing `Copyright`. - Remove copyright for mkdepend, which is not in the source tree anymore. * debian/upstream/metadata: Add upstream bug tracking metadata. [ Daniel Kahn Gillmor ] * debian/control: correct Homepage (old URL redirects to 404) [ Janitor ] * debian/changelog: Trim trailing whitespace. * debian/copyright: Use secure copyright file specification URI. * debian/compat, debian/control: - Bump debhelper from deprecated 9 to 13. - Set debhelper-compat version in Build-Depends. * debian/upstream/metadata: Set upstream metadata fields: Repository. * debian/rules: Drop transition for old debug package migration. -- Mike Hommey Tue, 02 Nov 2021 06:57:06 +0900 nss (2:3.70-1) unstable; urgency=medium * New upstream release. -- Mike Hommey Wed, 08 Sep 2021 08:31:23 +0900 nss (2:3.68-1) unstable; urgency=medium * New upstream release. -- Mike Hommey Mon, 19 Jul 2021 06:23:39 +0900 ### Old Ubuntu Delta ### nss (2:3.68.2-0ubuntu1) jammy; urgency=medium * New upstream release. (LP: #1959126) * d/p/CVE-2021-43527.patch: drop patch applied upstream. [ Fixed in 3.68.1 ] -- Athos Ribeiro Mon, 21 Feb 2022 14:55:42 -0300 nss (2:3.68-1ubuntu2) jammy; urgency=medium * SECURITY UPDATE: heap overflow when verifying DSA/RSA-PSS DER-encoded signatures - debian/patches/CVE-2021-43527.patch: check signature lengths in nss/lib/cryptohi/secvfy.c. - CVE-2021-43527 -- Marc Deslauriers Mon, 29 Nov 2021 07:12:54 -0500 nss (2:3.68-1ubuntu1) impish; urgency=medium * Merge with Debian unstable. Remaining changes: - d/libnss3.links: Make freebl3 available as library. (LP #1744328) - d/control: Add dh-exec to Build-Depends. - d/rules: Make mkdir tolerate debian/tmp existing (due to dh-exec). - d/p/disable_fips_enabled_read.patch: Disable reading fips_enabled flag in FIPS mode as libnss is not a FIPS certified library. (LP #1837734) - d/p/set-tls1.2-as-minimum.patch: Set TLSv1.2 as minimum TLS version. (LP #1856428) - d/libnss3.links.in: Symlink chk files to fix
[Touch-packages] [Bug 1971305] [NEW] Merge openldap from Debian unstable for kinetic
Public bug reported:
Upstream: tbd
Debian: 2.5.11+dfsg-1
Ubuntu: 2.5.11+dfsg-1~exp1ubuntu3
Debian does new releases regularly, so it's likely there will be newer
versions available before FF that we can pick up if this merge is done
later in the cycle.
### New Debian Changes ###
openldap (2.5.11+dfsg-1) unstable; urgency=medium
* Upload to unstable.
-- Ryan Tandy Fri, 11 Mar 2022 19:38:02 -0800
openldap (2.5.11+dfsg-1~exp1) experimental; urgency=medium
* New upstream release.
* Add openssl to Build-Depends to enable more checks in test067-tls.
* Update slapd-contrib's custom-library-search-path override to work with
current Lintian.
-- Ryan Tandy Sun, 23 Jan 2022 17:16:05 -0800
openldap (2.5.8+dfsg-1~exp1) experimental; urgency=medium
* New upstream release.
* Update slapd-contrib's custom-library-search-path override to work with
Lintian 2.108.0.
-- Ryan Tandy Wed, 13 Oct 2021 18:42:55 -0700
openldap (2.5.7+dfsg-1~exp1) experimental; urgency=medium
* New upstream release.
* Don't run autoreconf in contrib/ldapc++. We don't build it, and it is not
yet compatible with autoconf 2.71. (Closes: #993032)
* Stop disabling automake in debian/rules now that upstream removed the
AM_INIT_AUTOMAKE invocation.
* Drop custom config.{guess,sub} handling. dh_update_autotools_config does
the right thing for us.
* Update Standards-Version to 4.6.0; no changes required.
* debian/not-installed: Add the ldapvc.1 man page.
-- Ryan Tandy Mon, 30 Aug 2021 18:54:25 -0700
openldap (2.5.6+dfsg-1~exp1) experimental; urgency=medium
[ Ryan Tandy ]
* New upstream release.
* Export the cn=config database to LDIF format before upgrading from 2.4.
* slapd.README.Debian:
- Remove text about the dropped evolution-ntlm patch.
- Add guidance for recovering from upgrade failures.
* Remove the debconf warning and README text about the unsafe ACL configured
by default in versions before jessie.
* Remove upgrade code for adding the pwdMaxRecordedFailure attribute to the
ppolicy schema. It's obsolete since the schema has been internalized.
[ Sergio Durigan Junior ]
* Implement the 'escape hatch' mechanism.
- d/po/*.po: Update PO files given the new template note.
- d/po/templates.pot: Update file.
- d/slapd.templates: Add note warning user about a postinst failure,
its possible cause and what to do.
- d/slapd.postinst: Make certain upgrade functions return failure
instead of exiting, which allows the postinst script to gracefully
fail when applicable. Also, when the general configuration upgrade
fails, display a critical warning to the user. Implement
ignore_init_failure function.
- d/slapd.prerm: Implement ignore_init_failure function.
- d/slapd.scripts-common: Make certain functions return failure
instead of exiting.
- d/rules: Use dh_installinit's --error-handler to instruct it on how
to handle possible errors with the init script.
- d/slapd.NEWS: Add excerpt mentioning that the postinst script might
error out if it can't migrate the existing (old) database backend.
-- Ryan Tandy Mon, 16 Aug 2021 18:32:29 -0700
openldap (2.5.5+dfsg-1~exp1) experimental; urgency=medium
* New upstream release.
- Drop patches applied upstream: ITS#9544, ITS#9548.
* Mark slapd-contrib as breaking the old version of slapd to reduce the
chance of upgrade failure due to slapd-contrib being unpacked first.
-- Ryan Tandy Fri, 11 Jun 2021 11:43:15 -0700
openldap (2.5.4+dfsg-1~exp1) experimental; urgency=medium
* New upstream release.
- Changing olcAuthzRegexp dynamically is supported. (Closes: #761407)
- Support for LANMAN password hashes has been removed. (Closes: #988033)
- Added pkg-config files for liblber and libldap. (Closes: #670824)
- libldap_r has been merged into libldap. The Debian package will continue
to install a libldap_r.so symlink for backwards compatibility with
applications that still link with -lldap_r.
- The Berkeley DB backends, slapd-bdb(5) and slapd-hdb(5), have been
removed.
- The shell backend, slapd-shell(5), has been removed.
- New backend: slapd-asyncmeta(5).
- New core overlays: slapd-homedir(5), slapd-otp(5), and
slapd-remoteauth(5).
- The ppolicy schema has been merged into the slapo-ppolicy(5) module.
- The argon2 password module has been promoted from contrib to core.
* Add a superficial autopkgtest for smbk5pwd.
* Update Standards-Version to 4.5.1; no changes needed.
* Upgrade to debhelper compat level 12.
### Old Ubuntu Delta ###
openldap (2.5.11+dfsg-1~exp1ubuntu3) jammy; urgency=medium
* No-change rebuild to update maintainer scripts, see LP: 1959054
-- Dave Jones Wed, 16 Feb 2022 17:15:26
+
openldap (2.5.11+dfsg-1~exp1ubuntu2) jammy; urgency=medium
* No-change rebuild for the perl update.
-- Matthias Klose Mon, 07 Feb
[Touch-packages] [Bug 1971319] [NEW] Merge rsync from Debian unstable for kinetic
Public bug reported: Upstream: tbd Debian: 3.2.4-1 Ubuntu: 3.2.3-8ubuntu3 Debian does new releases regularly, so it's likely there will be newer versions available before FF that we can pick up if this merge is done later in the cycle. ### New Debian Changes ### rsync (3.2.4-1) unstable; urgency=medium [ Samuel Henrique ] * New upstream version 3.2.4 - Work around a glibc bug where lchmod() breaks in a chroot w/o /proc mounted (closes: #995046). - rsync.1: remove prepended backticks which broke --stop-after and --stop-at formatting (closes: #1007990). * Ship new python-based rrsync with --with-rrsync: - rrsync was previouysly written in bash. - A manpage is now shipped for rrsync. - python3 and python3-cmarkgfm are new B-Ds since they're needed to generate the manpage. * d/control: - Add version requirement for some libxxhash-dev and libzstd-dev as per upstream docs. - Add python3-braceexpand to Suggests as it can be used by rrsync. * d/rsync.install: cull_options has been renamed to cull-options. * d/patches: - Refresh the following patches: ~ disable_reconfigure_req.diff; ~ perl_shebang.patch; ~ skip_devices_test.patch; - Drop the following patches, applied upstream now: ~ CVE-2020-14387.patch; ~ copy-devices.diff; ~ fix_delay_updates.patch; ~ fix_ftcbfs_configure.patch; ~ fix_mkpath.patch; ~ fix_rsync-ssl_RSYNC_SSL_CERT_feature.patch; ~ fix_sparse_inplace.patch; ~ manpage_upstream_fixes.patch; ~ update_rrsync_options.patch; ~ workaround_glibc_lchmod_regression.patch; [ Sergio Durigan Junior ] * d/rules: Disable ASM optimizations when building. This is not needed because the only ASM-optimized implementation available is the MD5 hash, which is actually a no-op because we link against OpenSSL and rsync ends up using that library's implementation of the hash. Even then, the final binary ends up with the ASM-optimized version included, which makes it become CET-incompatible. Thanks to Dimitri John Ledkov -- Samuel Henrique Mon, 18 Apr 2022 14:44:44 +0100 rsync (3.2.3-8) unstable; urgency=medium * debian/patches: - manpage_upstream_fixes.patch: Import multiple upstream patches to fix manpage. - copy-devices.diff: Add missing manpage changes to patch - CVE-2020-14387.patch: Add Forwarded DEP3 field to point to upstream patch - fix_delay_updates.patch: Refresh patch - fix_mkpath.patch: New upstream patch to fix an edge case on --mkpath - fix_rsync-ssl_RSYNC_SSL_CERT_feature.patch: New upstream patch - fix_sparse_inplace.patch: New upstream patch to fix --sparse + --inplace options - update_rrsync_options.patch: New upstream patch to update rrsync options -- Samuel Henrique Sat, 25 Sep 2021 17:38:16 +0100 rsync (3.2.3-7) unstable; urgency=medium * Bump Standards-Version to 4.6.0 * d/p/workaround_glibc_lchmod_regression.patch: New patch from upstream (closes: #994543) * debian/rsync.NEWS: Fix typo in last entry -- Samuel Henrique Sat, 18 Sep 2021 00:25:13 +0100 rsync (3.2.3-6) unstable; urgency=medium * d/t/upstream-tests: Suppress stderr warnings from the build process -- Samuel Henrique Sun, 12 Sep 2021 18:22:57 +0100 rsync (3.2.3-5) unstable; urgency=medium [ 刘建强 ] * Set the rsync.service not to start automatically after installation, the rsyncd.conf configuration file needs to be configured by the user before the service can start [ Samuel Henrique ] * Re-add upstream patch for --copy-devices, the --write-devices option is not fully equivalent (closes: #992215) * d/rsync.docs: Add NEWS.md file (previously named NEWS) (closes: #993697) * d/p/fix_delay_updates.patch: New patch from upstream (closes: #992231) -- Samuel Henrique Sun, 12 Sep 2021 17:25:37 +0100 rsync (3.2.3-4) unstable; urgency=medium [ Helmut Grohne ] * d/p/fix_ftcbfs_configure.patch: New patch to fix FTCBFS (closes: #971285) [ Samuel Henrique ] * Bump Standards-Version to 4.5.1 ### Old Ubuntu Delta ### rsync (3.2.3-8ubuntu3) jammy; urgency=high * No change rebuild for ppc64el baseline bump. -- Julian Andres Klode Fri, 25 Mar 2022 10:51:06 +0100 rsync (3.2.3-8ubuntu2) jammy; urgency=medium * No-change rebuild against openssl3 -- Simon Chopin Wed, 24 Nov 2021 14:01:07 + rsync (3.2.3-8ubuntu1) jammy; urgency=medium * Merge with Debian unstable. Remaining changes: - debian/rules: add --disable-asm configure flag. The only asm implementation is available for md5 on x86_64, however it is no-op, because we built with OpenSSL which has optimized md5 implementation. Furthermore, linking noop md5 asm on x86_64 results in rsync binary not getting marked as CET compatible, because the noop md5 asm is not marked as CET compatible. Thus building without noop md5 asm, results
[Touch-packages] [Bug 1971323] [NEW] Merge six from Debian unstable for kinetic
Public bug reported: Upstream: tbd Debian: 1.16.0-3 Ubuntu: 1.16.0-3ubuntu1 Debian typically updates six every 2 months on average, but it was last updated 21.12 and looks overdue. Check back in on this monthly. ### New Debian Changes ### six (1.16.0-3) unstable; urgency=medium [ Debian Janitor ] * Bump debhelper from old 12 to 13. * Update standards version to 4.5.1, no changes needed. [ Colin Watson ] * Link directly to upstream in Homepage and debian/copyright. -- Colin Watson Sun, 26 Dec 2021 02:24:26 + six (1.16.0-2) unstable; urgency=medium * Team upload. [ Andreas Beckmann ] * python-six/python3-six: Copy Breaks: python (<< 2.7.18), python-minimal (<< 2.7.18), libpython-stdlib (<< 2.7.18), python-iso8601 (<< 0.1.12-2~), python-pbr (<< 5.4.5) from python2.7 to ensure removal of the unversioned python packages (and some persisting obsolete Python 2 module packages) on upgrades from buster. In some upgrade scenarios (mostly involving openstack packages) these Breaks in python2.7 were ineffective because the unversioned python packages got higher scores than python2.7. python-six/python3-six are usually very high scoring Python module packages in these cases, making them ideal candidates for such copies of the Breaks. (Closes: #991433) -- Stefano Rivera Tue, 27 Jul 2021 11:44:18 -0400 six (1.16.0-1) unstable; urgency=medium * New upstream release. -- Colin Watson Sun, 09 May 2021 11:40:54 +0100 six (1.15.0-2) unstable; urgency=medium [ Ondřej Nový ] * d/control: Update Maintainer field with new Debian Python Team contact address. * d/control: Update Vcs-* fields with new Debian Python Team Salsa layout. [ Colin Watson ] * Remove Barry Warsaw from Uploaders, with thanks for their previous contributions (closes: #970181). -- Colin Watson Tue, 10 Nov 2020 00:16:45 + six (1.15.0-1) unstable; urgency=medium [ Debian Janitor ] * Update standards version to 4.5.0, no changes needed. [ Colin Watson ] * New upstream release. -- Colin Watson Sun, 24 May 2020 10:23:22 +0100 six (1.14.0-3) unstable; urgency=medium * Dont run unittests for python2 binary, to reduce pytest rdeps -- Sandro Tosi Mon, 13 Apr 2020 20:16:04 -0400 six (1.14.0-2) unstable; urgency=medium * Build-depend on python2 rather than python. -- Colin Watson Tue, 21 Jan 2020 09:44:26 + six (1.14.0-1) unstable; urgency=medium [ Debian Janitor ] * Remove unnecessary team-upload line in changelog. * Set upstream metadata fields: Bug-Database, Repository. * Set upstream metadata fields: Bug-Submit, Repository-Browse. [ Colin Watson ] * New upstream release. -- Colin Watson Mon, 20 Jan 2020 21:39:42 + six (1.13.0-1) unstable; urgency=medium [ Emmanuel Arias ] * New upstream version 1.13.0 * d/control: Bump Standard-Version to 4.4.1 * d/control: Bump debhelper-compat to 12 (from 9) [ Colin Watson ] * Replace manually-written basic autopkgtests with 'Testsuite: autopkgtest-pkg-python'. * Remove build-dependencies on python-py and python3-py, no longer used upstream. * Fix HTML paths in doc-base control file. -- Colin Watson Tue, 12 Nov 2019 08:10:54 + six (1.12.0-2) unstable; urgency=medium ### Old Ubuntu Delta ### six (1.16.0-3ubuntu1) jammy; urgency=medium * Drop Breaks on python to allow python-is-python2 to remain when upgrading from Focal (LP: #1958720) -- Robie Basak Wed, 13 Apr 2022 21:08:40 +0100 ** Affects: six (Ubuntu) Importance: Undecided Status: Incomplete ** Tags: needs-merge upgrade-software-version ** Changed in: six (Ubuntu) Status: New => Incomplete ** Changed in: six (Ubuntu) Milestone: None => ubuntu-22.06 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to six in Ubuntu. https://bugs.launchpad.net/bugs/1971323 Title: Merge six from Debian unstable for kinetic Status in six package in Ubuntu: Incomplete Bug description: Upstream: tbd Debian: 1.16.0-3 Ubuntu: 1.16.0-3ubuntu1 Debian typically updates six every 2 months on average, but it was last updated 21.12 and looks overdue. Check back in on this monthly. ### New Debian Changes ### six (1.16.0-3) unstable; urgency=medium [ Debian Janitor ] * Bump debhelper from old 12 to 13. * Update standards version to 4.5.1, no changes needed. [ Colin Watson ] * Link directly to upstream in Homepage and debian/copyright. -- Colin Watson Sun, 26 Dec 2021 02:24:26 + six (1.16.0-2) unstable; urgency=medium * Team upload. [ Andreas Beckmann ] * python-six/python3-six: Copy Breaks: python (<< 2.7.18), python-minimal (<< 2.7.18), libpython-stdlib (<< 2.7.18), python-iso8601 (<< 0.1.12-2~), python-pbr (<< 5.4.5) from python2.7 to ensure removal of the unversioned python
[Touch-packages] [Bug 1958267] Re: "Connection failed" for WPA Enterprise network (e.g. eduroam)
This affects WiFi hotspot as well. After downgrading to wpasupplicant_2.9.0-21build1_amd64.deb my phone can connect to the WiFi hotspot. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to wpa in Ubuntu. https://bugs.launchpad.net/bugs/1958267 Title: "Connection failed" for WPA Enterprise network (e.g. eduroam) Status in wpa package in Ubuntu: Confirmed Status in wpa source package in Jammy: Confirmed Bug description: With the current jammy version of wpasupplicant (2:2.10-1), I cannot connect to the WPA Enterprise network eduroam, which is used by Universities worldwide. I get a "Connection failed" message or a request to re-enter the password. - I've re-tried the credentials: no fix ;-) - Tried a 21.10 live session on the same machine: works fine! - Manually downgraded wpasupplicant to the impish version (2:2.9.0-21build1): connected normally. - Upgraded wpasupplicant to the latest version: fails to connect again. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: wpasupplicant 2:2.10-1 ProcVersionSignature: Ubuntu 5.15.0-17.17-generic 5.15.12 Uname: Linux 5.15.0-17-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu75 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Jan 18 09:56:23 2022 InstallationDate: Installed on 2021-11-30 (48 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20211130) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: wpa UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1958267/+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 1971272] [NEW] Merge cyrus-sasl2 from Debian unstable for kinetic
Public bug reported: Upstream: tbd Debian: 2.1.28+dfsg-4 Ubuntu: 2.1.27+dfsg2-3ubuntu1 Debian does new releases regularly, so it's likely there will be newer versions available before FF that we can pick up if this merge is done later in the cycle. ### New Debian Changes ### cyrus-sasl2 (2.1.28+dfsg-4) unstable; urgency=medium * d/copyright: java/* files were removed upstream * d/copyright: Reformat the default license's margin * d/copyright: Add project's license to include/makemd5.c * Move SCRAM to libsasl2-modules (Closes: #977360) * Install additional GS2 module for Heimdal * Remove Roberto from the Uploaders * Drop 0005-Fixes-in-library-mutexes.patch * Drop 0021-Fix-keytab-option-for-MIT-Kerberos.patch * Remove former logcheck conffile (Closes: #1009851) * lintian: Fix excessive-priority-for-library-package * lintian: Fix package-contains-empty-directory -- Bastian Germann Wed, 20 Apr 2022 01:01:01 +0200 cyrus-sasl2 (2.1.28+dfsg-3) unstable; urgency=high * Set MIT/Heimdal CFLAGS instead of CPPFLAGS * Drop unnecessary 0027-properly-create-libsasl2.pc.patch * Prevent installing outdated ChangeLog (Closes: #1009681) * Remove debug log message and its logcheck rule (Closes: #805310) * Self-reference pluginviewer man as saslpluginviewer (Closes: #1009380) * Get rid of broken README.configure-options * Add sasldbconverter2.8 manpage * d/copyright: Add missing KTH license * Install libsasl.5 manpage [ Debian Janitor ] * Remove constraints unnecessary since buster -- Bastian Germann Fri, 15 Apr 2022 12:02:13 +0200 cyrus-sasl2 (2.1.28+dfsg-2) unstable; urgency=medium * Remove cruft -- Bastian Germann Fri, 25 Feb 2022 18:58:54 +0100 cyrus-sasl2 (2.1.28+dfsg-1) experimental; urgency=medium * Drop upstream patches * Import new release signing key * Reset repacksuffix * New upstream version 2.1.28+dfsg (CVE-2022-24407) * Rebase 0027-properly-create-libsasl2.pc.patch -- Bastian Germann Tue, 22 Feb 2022 23:40:47 +0100 cyrus-sasl2 (2.1.27+dfsg2-3) unstable; urgency=medium [ Andreas Hasenack ] * Fix configure.ac for autoconf 2.70 (Closes: #1003355, #1000152) -- Bastian Germann Tue, 11 Jan 2022 11:25:37 +0100 cyrus-sasl2 (2.1.27+dfsg2-2) unstable; urgency=medium [ Helmut Grohne ] * Fix FTCBFS: (Closes: #928512) + cross.patch: Support caching SPNEGO support test. + Provide SPNEGO support test result. [ Vagrant Cascadian ] * Set date in man pages (Closes: #995145) -- Bastian Germann Wed, 17 Nov 2021 01:23:49 +0100 cyrus-sasl2 (2.1.27+dfsg2-1) unstable; urgency=medium * Add bage to uploaders (Closes: #799864) * Use upstream patches where possible * Amend off-by-one in _sasl_add_string function * Replace some patches by upstream equivalents * Apply the patches in order of to their prefixes * Add missing caret (^) in logcheck rule (Closes: #830764) * Remove unnecessary GPL copy * Add missing copyright/licenses * Repack, getting rid of more problematic files * Build html documentation * Make the package rebuildable * Remove outdated README.Debian info * Disable autostart via debhelper * Drop unnecessary patch * Remove alternative, old build dep libmysqlclient-dev Annotate documentation Build-Depends with :native [ Frédéric Brière ] * Make logcheck snippet compatible with systemd journal -- Bastian Germann Sun, 14 Nov 2021 14:11:18 +0100 cyrus-sasl2 (2.1.27+dfsg-2.3) unstable; urgency=medium * Non-maintainer upload. * d/watch: Check the github releases page * Get rid of a patch's patch * Recover upstream-compatible patch license (Closes: #996866) + Relicense libobj patch * Fix lintian: unused-override ### Old Ubuntu Delta ### cyrus-sasl2 (2.1.27+dfsg2-3ubuntu1) jammy; urgency=medium * SECURITY UPDATE: SQL injection in SQL plugin - debian/patches/CVE-2022-24407.patch: escape password for SQL insert/update commands in plugins/sql.c. - CVE-2022-24407 -- Marc Deslauriers Tue, 22 Feb 2022 14:17:18 -0500 ** Affects: cyrus-sasl2 (Ubuntu) Importance: Undecided Status: New ** Tags: needs-merge upgrade-software-version ** Changed in: cyrus-sasl2 (Ubuntu) Milestone: None => ubuntu-22.07 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cyrus-sasl2 in Ubuntu. https://bugs.launchpad.net/bugs/1971272 Title: Merge cyrus-sasl2 from Debian unstable for kinetic Status in cyrus-sasl2 package in Ubuntu: New Bug description: Upstream: tbd Debian: 2.1.28+dfsg-4 Ubuntu: 2.1.27+dfsg2-3ubuntu1 Debian does new releases regularly, so it's likely there will be newer versions available before FF that we can pick up if this merge is done later in the cycle. ### New Debian Changes ### cyrus-sasl2 (2.1.28+dfsg-4) unstable; urgency=medium * d/copyright: java/* files were removed upstream * d/copyright: Reformat
[Touch-packages] [Bug 1971264] [NEW] Merge bridge-utils from Debian unstable for kinetic
Public bug reported: Upstream: tbd Debian: 1.7-1 Ubuntu: 1.7-1ubuntu3 Debian typically updates bridge-utils every 4 months on average, but it was last updated 21.02 and looks overdue. Check back in on this monthly. Based on Upstream's release history for bridge-utils we should have expected a new upstream update around 2022.03. Presumably it could come any time now. ### New Debian Changes ### bridge-utils (1.7-1) unstable; urgency=medium * New upstream version. Only messages related changes and compilation fixes. * Remove preserve_gcc_flags patch (in upstream now). * Bump standards, no change needed. * Clarify portprio and fix example. * Update upstream url. * Fix NEWS versioning of last entry :-? -- Santiago Garcia Mantinan Wed, 24 Feb 2021 12:34:03 +0100 bridge-utils (1.6-6) unstable; urgency=medium * Fix IPv6 address getting assigned on hotplug devices. Closes: #980752. * Fix waiting so that DAD works again. Closes: #982943. * Move mac setting before brctl addif to ensure mac setting. Closes: #980856. * Update documentation and add examples. Closes: #765098. * Update manpages. Closes: #981253. * Add a note on MTU settings. Closes: #292088. * Hook also on down to recreate the bridge so that multiple stanzas work Ok on ifdown. Closes: #319832. -- Santiago Garcia Mantinan Tue, 16 Feb 2021 13:29:04 +0100 bridge-utils (1.6-5) unstable; urgency=low * Overload bridge_hw to allow do specify an interface as well as the MAC address. Closes: #966244. * Change man page for bridge-utils-interfaces and news fileto document this overloading. -- Santiago Garcia Mantinan Fri, 22 Jan 2021 11:08:47 +0100 bridge-utils (1.6-4) unstable; urgency=low * Add en* to the device regex so that all catches them. Closes: #966319. * Document MAC address changes on news. Closes: #980505. -- Santiago Garcia Mantinan Thu, 21 Jan 2021 10:51:31 +0100 bridge-utils (1.6-3) unstable; urgency=medium * Support VLAN aware setups where we need vlan filtering. Thanks Benedikt Spranger for the patch. Closes: #950879. * Clarify on manual page that stp will get IPv6 lost. Closes: #736336. * Add a 1 second sleep if hw address needs to be changed. Closes: #945466. -- Santiago Garcia Mantinan Thu, 30 Apr 2020 10:06:38 +0200 bridge-utils (1.6-2) unstable; urgency=medium * Bump Standards-Version. * Preserve gcc flags set when building the lib. -- Santiago Garcia Mantinan Mon, 28 Jan 2019 00:25:14 +0100 bridge-utils (1.6-1) unstable; urgency=low * New upstream version. * Change default back to not hotplug. Closes: #892277. * Allow mtu to be set on the bridge by propagating it to the bridged interfaces. Closes: #661711. * Remove kernel headers from the package. -- Santiago Garcia Mantinan Tue, 15 Jan 2019 13:18:33 +0100 bridge-utils (1.5-16) unstable; urgency=medium * Don't set dev globally at bridge-utils.sh. Closes: #873086. -- Santiago Garcia Mantinan Sun, 08 Apr 2018 23:06:30 +0200 bridge-utils (1.5-15) unstable; urgency=medium * Fix substrings on interfaces. Closes: #873087. * Make it lintian clean sticking to 1.0 source format for now. No time to properly comment all the patches right now. -- Santiago Garcia Mantinan Fri, 02 Mar 2018 22:08:20 +0100 bridge-utils (1.5-14) unstable; urgency=low * Fix a problem with some vlan interfaces not being created. -- Santiago Garcia Mantinan Mon, 26 Jun 2017 17:48:37 +0200 bridge-utils (1.5-13) unstable; urgency=low * Fix a hardcoded interface name on bridge-utils.sh. Closes: #854841. -- Santiago Garcia Mantinan Sat, 11 Feb 2017 00:16:45 +0100 bridge-utils (1.5-12) unstable; urgency=medium * Add vlan support so that old setups using vlans as ports don't break. -- Santiago Garcia Mantinan Sun, 22 Jan 2017 00:23:50 +0100 ### Old Ubuntu Delta ### bridge-utils (1.7-1ubuntu3) jammy; urgency=medium * No-change rebuild for ppc64el baseline bump. -- Łukasz 'sil2100' Zemczak Wed, 23 Mar 2022 10:44:35 +0100 bridge-utils (1.7-1ubuntu2) impish; urgency=medium * No-change rebuild to build packages with zstd compression. -- Matthias Klose Thu, 07 Oct 2021 12:09:41 +0200 bridge-utils (1.7-1ubuntu1) impish; urgency=low * Merge from Debian unstable. Remaining changes: - Don't call ifup from bridge-network-interface, instead just call brctl and let udev/upstart bring the interface up. - debian/ifupdown.sh: Handle bridge params which use port and value - debian/bridge-utils-interface.5: + Update max, default value for path cost + Update unsettable gcint value for newer kernels -- Steve Langasek Wed, 17 Mar 2021 12:32:22 -0700 ** Affects: bridge-utils (Ubuntu) Importance: Undecided Status: Incomplete ** Tags: needs-merge upgrade-software-version ** Changed in: bridge-utils (Ubuntu) Status: New => Incomplete ** Changed in: bridge-utils (Ubuntu) Milestone: None =>
Re: [Touch-packages] [Bug 1971146] Re: [radeon] Pictures including wallpaper not showing
Yes but I think it points to the graphics driver maybe On 03/05/2022 07:26, Daniel van Vugt wrote: > Not solved then. Recovery mode is a workaround but not a fix. > -- 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/1971146 Title: [radeon] Pictures including wallpaper not showing Status in linux package in Ubuntu: Confirmed Status in mesa package in Ubuntu: New Bug description: I can't see pictures in emails or on some pictures on websites. Sometimes it just shows the bottom 20mm of pictures. The wallpaper is just a blank white screen. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Uname: Linux 5.15.0-27-generic x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon May 2 13:12:31 2022 DistUpgraded: 2022-04-24 19:05:38,365 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: jammy DistroVariant: ubuntu DkmsStatus: virtualbox/6.1.32, 5.15.0-25-generic, x86_64: installed virtualbox/6.1.32, 5.15.0-27-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Venus XT [Radeon HD 8870M / R9 M270X/M370X] [1002:6821] (rev 83) (prog-if 00 [VGA controller]) Subsystem: Apple Inc. Radeon R9 M370X Mac Edition [106b:0149] InstallationDate: Installed on 2021-04-26 (371 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) Lsusb: Bus 002 Device 003: ID 05ac:8406 Apple, Inc. Internal Memory Card Reader Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 05ac:8290 Apple, Inc. Bluetooth Host Controller Bus 001 Device 003: ID 05ac:0274 Apple, Inc. Apple Internal Keyboard / Trackpad Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Apple Inc. MacBookPro11,5 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-27-generic root=UUID=2234e6d3-3ebc-44e6-b0a5-bef132fd1f72 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to jammy on 2022-04-24 (7 days ago) dmi.bios.date: 06/11/2020 dmi.bios.release: 0.1 dmi.bios.vendor: Apple Inc. dmi.bios.version: 199.0.0.0.0 dmi.board.name: Mac-06F11F11946D27C5 dmi.board.vendor: Apple Inc. dmi.board.version: MacBookPro11,5 dmi.chassis.type: 9 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-06F11F11946D27C5 dmi.modalias: dmi:bvnAppleInc.:bvr199.0.0.0.0:bd06/11/2020:br0.1:svnAppleInc.:pnMacBookPro11,5:pvr1.0:rvnAppleInc.:rnMac-06F11F11946D27C5:rvrMacBookPro11,5:cvnAppleInc.:ct9:cvrMac-06F11F11946D27C5:sku: dmi.product.family: MacBook Pro dmi.product.name: MacBookPro11,5 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.110-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.1-1ubuntu2 version.libgl1-mesa-glx: libgl1-mesa-glx 22.0.1-1ubuntu2 version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1971146/+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 1971146] Re: [radeon] Pictures including wallpaper not showing
Not solved then. Recovery mode is a workaround but not a fix. -- 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/1971146 Title: [radeon] Pictures including wallpaper not showing Status in linux package in Ubuntu: Confirmed Status in mesa package in Ubuntu: New Bug description: I can't see pictures in emails or on some pictures on websites. Sometimes it just shows the bottom 20mm of pictures. The wallpaper is just a blank white screen. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Uname: Linux 5.15.0-27-generic x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon May 2 13:12:31 2022 DistUpgraded: 2022-04-24 19:05:38,365 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: jammy DistroVariant: ubuntu DkmsStatus: virtualbox/6.1.32, 5.15.0-25-generic, x86_64: installed virtualbox/6.1.32, 5.15.0-27-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Venus XT [Radeon HD 8870M / R9 M270X/M370X] [1002:6821] (rev 83) (prog-if 00 [VGA controller]) Subsystem: Apple Inc. Radeon R9 M370X Mac Edition [106b:0149] InstallationDate: Installed on 2021-04-26 (371 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) Lsusb: Bus 002 Device 003: ID 05ac:8406 Apple, Inc. Internal Memory Card Reader Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 05ac:8290 Apple, Inc. Bluetooth Host Controller Bus 001 Device 003: ID 05ac:0274 Apple, Inc. Apple Internal Keyboard / Trackpad Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Apple Inc. MacBookPro11,5 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-27-generic root=UUID=2234e6d3-3ebc-44e6-b0a5-bef132fd1f72 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to jammy on 2022-04-24 (7 days ago) dmi.bios.date: 06/11/2020 dmi.bios.release: 0.1 dmi.bios.vendor: Apple Inc. dmi.bios.version: 199.0.0.0.0 dmi.board.name: Mac-06F11F11946D27C5 dmi.board.vendor: Apple Inc. dmi.board.version: MacBookPro11,5 dmi.chassis.type: 9 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-06F11F11946D27C5 dmi.modalias: dmi:bvnAppleInc.:bvr199.0.0.0.0:bd06/11/2020:br0.1:svnAppleInc.:pnMacBookPro11,5:pvr1.0:rvnAppleInc.:rnMac-06F11F11946D27C5:rvrMacBookPro11,5:cvnAppleInc.:ct9:cvrMac-06F11F11946D27C5:sku: dmi.product.family: MacBook Pro dmi.product.name: MacBookPro11,5 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.110-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.1-1ubuntu2 version.libgl1-mesa-glx: libgl1-mesa-glx 22.0.1-1ubuntu2 version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1971146/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
Re: [Touch-packages] [Bug 1971146] Re: [radeon] Pictures including wallpaper not showing
If I boot into recovery mode then click normal boot the desktop appears, every time. Kernel 5.17.5-051705-generic If I just do a normal boot the desktop appears maybe 1 in out of every 20 reboots, same kernel. Regards, Mick On 03/05/2022 06:30, Daniel van Vugt wrote: > Great to hear. > > Additional logs certainly won't help if it's working now. But if you > have the patience then finding out what version number exactly fixed it > would help. Or what kernel version was the last to have the bug, keeping > in mind the broken kernel was (roughly) upstream version 5.15.30 > > ** No longer affects: mutter (Ubuntu) > -- 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/1971146 Title: [radeon] Pictures including wallpaper not showing Status in linux package in Ubuntu: Confirmed Status in mesa package in Ubuntu: New Bug description: I can't see pictures in emails or on some pictures on websites. Sometimes it just shows the bottom 20mm of pictures. The wallpaper is just a blank white screen. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Uname: Linux 5.15.0-27-generic x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon May 2 13:12:31 2022 DistUpgraded: 2022-04-24 19:05:38,365 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: jammy DistroVariant: ubuntu DkmsStatus: virtualbox/6.1.32, 5.15.0-25-generic, x86_64: installed virtualbox/6.1.32, 5.15.0-27-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Venus XT [Radeon HD 8870M / R9 M270X/M370X] [1002:6821] (rev 83) (prog-if 00 [VGA controller]) Subsystem: Apple Inc. Radeon R9 M370X Mac Edition [106b:0149] InstallationDate: Installed on 2021-04-26 (371 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) Lsusb: Bus 002 Device 003: ID 05ac:8406 Apple, Inc. Internal Memory Card Reader Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 05ac:8290 Apple, Inc. Bluetooth Host Controller Bus 001 Device 003: ID 05ac:0274 Apple, Inc. Apple Internal Keyboard / Trackpad Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Apple Inc. MacBookPro11,5 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-27-generic root=UUID=2234e6d3-3ebc-44e6-b0a5-bef132fd1f72 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to jammy on 2022-04-24 (7 days ago) dmi.bios.date: 06/11/2020 dmi.bios.release: 0.1 dmi.bios.vendor: Apple Inc. dmi.bios.version: 199.0.0.0.0 dmi.board.name: Mac-06F11F11946D27C5 dmi.board.vendor: Apple Inc. dmi.board.version: MacBookPro11,5 dmi.chassis.type: 9 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-06F11F11946D27C5 dmi.modalias: dmi:bvnAppleInc.:bvr199.0.0.0.0:bd06/11/2020:br0.1:svnAppleInc.:pnMacBookPro11,5:pvr1.0:rvnAppleInc.:rnMac-06F11F11946D27C5:rvrMacBookPro11,5:cvnAppleInc.:ct9:cvrMac-06F11F11946D27C5:sku: dmi.product.family: MacBook Pro dmi.product.name: MacBookPro11,5 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.110-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.1-1ubuntu2 version.libgl1-mesa-glx: libgl1-mesa-glx 22.0.1-1ubuntu2 version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1971146/+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 1971232] [NEW] [Dell XPS 8940] [ALC3861] No audio from headset mic when plugged into front panel jack, works under Windows
Public bug reported: There is no audio coming from the headset mic when plugged into the front panel headset jack (bog standard wired headphones with mic, Sony MDR-EX15AP). Upon plugging in Gnome should offer a choice of "Headset" amongst others, but the only ones available are "Headphones" and "Microphone", neither of which enables the mic on the headset. The same headset works under Windows, so it shouldn't be an issue of mismatching TRRS. I'm happy to provide any further details if needed. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: alsa-base 1.0.25+dfsg-0ubuntu7 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Uname: Linux 5.15.0-27-generic x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jonathan 8896 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: GNOME Date: Tue May 3 13:54:25 2022 InstallationDate: Installed on 2021-08-16 (260 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaRecordingTest: ALSA recording test through plughw:PCH successful Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jonathan 8896 F pulseaudio Symptom_PulseAudioRecordingTest: PulseAudio recording test through plughw:PCH successful Symptom_Type: No sound at all Title: [HDA-Intel - HDA Intel PCH, recording] No sound at all UpgradeStatus: Upgraded to jammy on 2022-04-27 (5 days ago) dmi.bios.date: 03/29/2022 dmi.bios.release: 2.5 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.5.1 dmi.board.name: 0427JK dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.5.1:bd03/29/2022:br2.5:svnDellInc.:pnXPS8940:pvr:rvnDellInc.:rn0427JK:rvrA00:cvnDellInc.:ct3:cvr:sku09C5: dmi.product.family: XPS dmi.product.name: XPS 8940 dmi.product.sku: 09C5 dmi.sys.vendor: Dell Inc. modified.conffile..etc.modprobe.d.alsa-base.conf: [modified] mtime.conffile..etc.modprobe.d.alsa-base.conf: 2022-04-28T14:25:53.371743 ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy wayland-session -- 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/1971232 Title: [Dell XPS 8940] [ALC3861] No audio from headset mic when plugged into front panel jack, works under Windows Status in alsa-driver package in Ubuntu: New Bug description: There is no audio coming from the headset mic when plugged into the front panel headset jack (bog standard wired headphones with mic, Sony MDR-EX15AP). Upon plugging in Gnome should offer a choice of "Headset" amongst others, but the only ones available are "Headphones" and "Microphone", neither of which enables the mic on the headset. The same headset works under Windows, so it shouldn't be an issue of mismatching TRRS. I'm happy to provide any further details if needed. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: alsa-base 1.0.25+dfsg-0ubuntu7 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Uname: Linux 5.15.0-27-generic x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jonathan 8896 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: GNOME Date: Tue May 3 13:54:25 2022 InstallationDate: Installed on 2021-08-16 (260 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaRecordingTest: ALSA recording test through plughw:PCH successful Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jonathan 8896 F pulseaudio Symptom_PulseAudioRecordingTest: PulseAudio recording test through plughw:PCH successful Symptom_Type: No sound at all Title: [HDA-Intel - HDA Intel PCH, recording] No sound at all UpgradeStatus: Upgraded to jammy on 2022-04-27 (5 days ago) dmi.bios.date: 03/29/2022 dmi.bios.release: 2.5 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.5.1 dmi.board.name: 0427JK dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.5.1:bd03/29/2022:br2.5:svnDellInc.:pnXPS8940:pvr:rvnDellInc.:rn0427JK:rvrA00:cvnDellInc.:ct3:cvr:sku09C5: dmi.product.family: XPS dmi.product.name: XPS 8940 dmi.product.sku: 09C5 dmi.sys.vendor: Dell Inc. modified.conffile..etc.modprobe.d.alsa-base.conf: [modified] mtime.conffile..etc.modprobe.d.alsa-base.conf: 2022-04-28T14:25:53.371743 To
