[Touch-packages] [Bug 2081153] [NEW] X / GUI not starting after boot
Public bug reported: GUI not starting after login. But startx works after login on tty )ctrl- alt-f3) ProblemType: Bug DistroRelease: Ubuntu 24.10 Package: xorg 1:7.7+23ubuntu3 ProcVersionSignature: Ubuntu 6.11.0-7.7-generic 6.11.0-rc7 Uname: Linux 6.11.0-7-generic x86_64 ApportVersion: 2.30.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: GNOME Date: Thu Sep 19 10:35:21 2024 DistUpgraded: 2024-09-18 19:52:58,283 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: oracular DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0126] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Fujitsu Limited. Device [10cf:15e9] InstallationDate: Installed on 2017-11-06 (2508 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) MachineType: FUJITSU LIFEBOOK E751 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.11.0-7-generic root=UUID=c6e78d2f-08ae-477d-afc4-4575ad1a2843 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to oracular on 2024-09-18 (1 days ago) dmi.bios.date: 06/20/2012 dmi.bios.release: 1.21 dmi.bios.vendor: FUJITSU // Phoenix Technologies Ltd. dmi.bios.version: Version 1.21 dmi.board.name: FJNB222 dmi.board.vendor: FUJITSU dmi.board.version: H3 dmi.chassis.type: 10 dmi.chassis.vendor: FUJITSU dmi.chassis.version: LIFEBOOK E751 dmi.modalias: dmi:bvnFUJITSU//PhoenixTechnologiesLtd.:bvrVersion1.21:bd06/20/2012:br1.21:svnFUJITSU:pnLIFEBOOKE751:pvr10601409269:rvnFUJITSU:rnFJNB222:rvrH3:cvnFUJITSU:ct10:cvrLIFEBOOKE751:sku: dmi.product.name: LIFEBOOK E751 dmi.product.version: 10601409269 dmi.sys.vendor: FUJITSU version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.122-1 version.libgl1-mesa-dri: libgl1-mesa-dri 24.2.2-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 23.1.3-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:21.1.13-2ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:22.0.0-1build1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1build1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-3ubuntu1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug oracular 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/2081153 Title: X / GUI not starting after boot Status in xorg package in Ubuntu: New Bug description: GUI not starting after login. But startx works after login on tty )ctrl-alt-f3) ProblemType: Bug DistroRelease: Ubuntu 24.10 Package: xorg 1:7.7+23ubuntu3 ProcVersionSignature: Ubuntu 6.11.0-7.7-generic 6.11.0-rc7 Uname: Linux 6.11.0-7-generic x86_64 ApportVersion: 2.30.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: GNOME Date: Thu Sep 19 10:35:21 2024 DistUpgraded: 2024-09-18 19:52:58,283 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: oracular DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0126] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Fujitsu Limited. Device [10cf:15e9] InstallationDate: Installed on 2017-11-06 (2508 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) MachineType: FUJITSU LIFEBOOK E751 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.11.0-7-generic root=UUID=c6e78d2f-08ae-477d-afc4-4575ad1a2843 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to oracular on 2024-09-18 (1 days ago) dmi.bios.date: 06/20/2012 dmi.bios.release: 1.21 dmi.bios.vendor: FUJITSU // Phoenix Technologies Ltd. dmi.bios.version: Version 1.21 dmi.board.name: FJNB222 dmi.board.vendor: FUJITSU dmi.board.version: H3 dmi.chassis.type: 10 dmi.chassis.vendor: FUJITSU dmi.chassis.version: LIFEBOOK E751 dmi.modalias: dmi:bvnFUJITSU//PhoenixTechnologiesLtd.:bvrVersion1.21:bd06/20/2012:br1.21:svnFUJITSU:pnLIFEBOOKE751:pvr10601409269:rvnFUJITSU:rnFJNB222:rvrH3:cvnFUJITSU:ct10:cvrLIFEBOOKE751:sku: dmi.product.name: LIFEBOOK E751 dmi.product.version: 10601409269 dmi.sys.vendor: FUJITSU version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.122-1 version.libgl1-mesa-dri: libgl1-mesa-dri 24.2.2-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 23.1.3-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:21.1.13-2ubuntu1 version.xserver-xorg-i
[Touch-packages] [Bug 2078720] Re: Upgrading from jammy to noble results in a linux-headers package being in a broken state
Not fixed. Its Sept. 11 and I reinstalled and reupgraded no dice. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/2078720 Title: Upgrading from jammy to noble results in a linux-headers package being in a broken state Status in apt package in Ubuntu: New Status in linux-aws package in Ubuntu: Confirmed Status in linux-gcp package in Ubuntu: Confirmed Status in ubuntu-release-upgrader package in Ubuntu: Fix Released Status in apt source package in Jammy: Fix Released Status in linux-aws source package in Jammy: New Status in linux-gcp source package in Jammy: New Status in apt source package in Noble: New Status in linux-aws source package in Noble: New Status in linux-gcp source package in Noble: New Status in ubuntu-release-upgrader source package in Noble: Fix Released Bug description: (For APT SRU versioning, see https://wiki.ubuntu.com/AptUpdates) [Impact] Obsolete packages can be removed despite still having reverse dependencies installed, for example: Now that 24.04.1 has been released, 22.04 users are encouraged to upgrade to 24.04 via the `do-release-upgrade` command. This issue was seen whilst testing this upgrade path. Upgrading and later rebooting a jammy GCP instance results in `linux-headers-6.5.0-1025-gcp` being a broken state. ``` $ sudo apt install Reading package lists... Done Building dependency tree... Done Reading state information... Done You might want to run 'apt --fix-broken install' to correct these. The following packages have unmet dependencies: linux-headers-6.5.0-1025-gcp : Depends: linux-gcp-6.5-headers-6.5.0-1025 but it is not installable E: Unmet dependencies. Try 'apt --fix-broken install' with no packages (or specify a solution). ``` `linux-gcp-6.5-headers-6.5.0-1025` is a dependency of `linux-image-6.5.0-1025-gcp` which is also not removed during the upgrade. ``` $ apt-cache rdepends linux-headers-6.5.0-1025-gcp linux-headers-6.5.0-1025-gcp Reverse Depends: linux-image-6.5.0-1025-gcp $ apt-cache rdepends linux-image-6.5.0-1025-gcp linux-image-6.5.0-1025-gcp Reverse Depends: ``` Running `apt --fix-broken install` resolves the error. ``` $ sudo apt --fix-broken install Reading package lists... Done Building dependency tree... Done Reading state information... Done Correcting dependencies... Done The following packages will be REMOVED: linux-headers-6.5.0-1025-gcp 0 upgraded, 0 newly installed, 1 to remove and 0 not upgraded. After this operation, 27.9 MB disk space will be freed. Do you want to continue? [Y/n] y (Reading database ... 83770 files and directories currently installed.) Removing linux-headers-6.5.0-1025-gcp (6.5.0-1025.27~22.04.1) ... $ sudo apt install Reading package lists... Done Building dependency tree... Done Reading state information... Done 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. ``` This issue was also observed after upgrading a jammy AWS instance to noble. ``` $ sudo apt install Reading package lists... Done Building dependency tree... Done Reading state information... Done You might want to run 'apt --fix-broken install' to correct these. The following packages have unmet dependencies: linux-headers-6.5.0-1024-aws : Depends: linux-aws-6.5-headers-6.5.0-1024 but it is not installable E: Unmet dependencies. Try 'apt --fix-broken install' with no packages (or specify a solution). ``` [Test plan] ## Jammy APT verification To prepare the VMs, follow the following scheme: $ lxc launch ubuntu:jammy jammy-to-noble --vm If using lxc shell or exec to connect to it, also perform the step below: $ lxc exec jammy-to-noble apt-mark lxd-agent-launcher # otherwise it resets On this jammy VM, edit /etc/update-manager/release-upgrades and set Prompt to "normal" (since release upgrades to noble via the lts prompt are temporarily blocked due to this bug) If this test run is meant to test the fix, then at this point you should install apt from jammy proposed. Otherwise, continue directly with the release upgrade. Then to continue with the test, proceed to the release upgrade: $ sudo do-release-upgrade Check that currently booted linux-headers- are *not* removed as obsolete. After the reboot at the end, in the rebooted system, issue: $ sudo apt upgrade With the bug present, you will get an error like this: $ sudo apt upgrade Reading package lists... Done Building dependency tree... Done Reading state information... Done You might want to run 'apt --fix-broken install' to correct these. The following packages have unmet dependencies: linux-headers-5.15.0-1065-kvm : Depends: linux-kvm-headers-5.15.0-1065 but it is not installable E
[Touch-packages] [Bug 2077883] Re: usermod silently fails modifying group membership for extrausers
Correct, this has a reported bug (though not in the proper place) since 2019 https://forum.snapcraft.io/t/how-to-add-extra-user-to-group/13321/7 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to shadow in Ubuntu. https://bugs.launchpad.net/bugs/2077883 Title: usermod silently fails modifying group membership for extrausers Status in shadow package in Ubuntu: New Bug description: Release Distributor ID: Ubuntu Description:Ubuntu 24.04 LTS Release:24.04 Codename: noble Package: passwd 1:4.13+dfsg1-4ubuntu3.2 When using the libnss-extrausers package to store users in a seperate DB at /var/lib/extrausers, the usermod program is unable to edit group memberships (usermod -a -G ) Running group-modifying usermod command fails silently, no error is generated and the return code is 0, but there is no change at /var/lib/extrausers usermod DOES support some extrausers features, I can successfully change a user's GECOS. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shadow/+bug/2077883/+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 2077883] [NEW] usermod silently fails modifying group membership for extrausers
Public bug reported: Release Distributor ID: Ubuntu Description:Ubuntu 24.04 LTS Release:24.04 Codename: noble Package: passwd 1:4.13+dfsg1-4ubuntu3.2 When using the libnss-extrausers package to store users in a seperate DB at /var/lib/extrausers, the usermod program is unable to edit group memberships (usermod -a -G ) Running group-modifying usermod command fails silently, no error is generated and the return code is 0, but there is no change at /var/lib/extrausers usermod DOES support some extrausers features, I can successfully change a user's GECOS. ** Affects: shadow (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to shadow in Ubuntu. https://bugs.launchpad.net/bugs/2077883 Title: usermod silently fails modifying group membership for extrausers Status in shadow package in Ubuntu: New Bug description: Release Distributor ID: Ubuntu Description:Ubuntu 24.04 LTS Release:24.04 Codename: noble Package: passwd 1:4.13+dfsg1-4ubuntu3.2 When using the libnss-extrausers package to store users in a seperate DB at /var/lib/extrausers, the usermod program is unable to edit group memberships (usermod -a -G ) Running group-modifying usermod command fails silently, no error is generated and the return code is 0, but there is no change at /var/lib/extrausers usermod DOES support some extrausers features, I can successfully change a user's GECOS. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shadow/+bug/2077883/+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 2057687] Re: systemctl hibernate error: "Call to Hibernate failed: Invalid argument"
Actually it's more simple than that, initramfs(step 6) is not required. After each kernel upgrade (during apt dist/full upgrade) I face the "invalid argument" error and each time I fix it only by steps 1, 2, 5, 7, 8, 9. -- 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/2057687 Title: systemctl hibernate error: "Call to Hibernate failed: Invalid argument" Status in systemd package in Ubuntu: Confirmed Bug description: After upgrading systemd to 255(255.2-3ubuntu2) hibernate stopped working. Trying to hibernate: systemctl hibernate I get: Call to Hibernate failed: Invalid argument systemctl status systemd-hibernate.service - × systemd-hibernate.service - Hibernate Loaded: loaded (/usr/lib/systemd/system/systemd-hibernate.service; static) Active: failed (Result: exit-code) since Tue 2024-03-12 18:48:12 MSK; 1min 33s ago Docs: man:systemd-hibernate.service(8) Process: 4473 ExecStart=/usr/lib/systemd/systemd-sleep hibernate (code=exited, status=1/FAILURE) Main PID: 4473 (code=exited, status=1/FAILURE) CPU: 5ms мар 12 18:48:12 ASUSPRO-P3540FA systemd[1]: Starting systemd-hibernate.service - Hibernate... мар 12 18:48:12 ASUSPRO-P3540FA systemd-sleep[4473]: Failed to find location to hibernate to: Invalid argument мар 12 18:48:12 ASUSPRO-P3540FA systemd[1]: systemd-hibernate.service: Main process exited, code=exited, status=1/FAILURE мар 12 18:48:12 ASUSPRO-P3540FA systemd[1]: systemd-hibernate.service: Failed with result 'exit-code'. мар 12 18:48:12 ASUSPRO-P3540FA systemd[1]: Failed to start systemd-hibernate.service - Hibernate. -- Previous version (254.x) worked: swapfile(on EXT4 fs) is used to hibernate/resume, resume with resume_offset kernel parameters. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2057687/+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 2057687] Re: systemctl hibernate error: "Call to Hibernate failed: Invalid argument"
Somehow this was fixed for me by the following (almost random) sequence of steps: 1. remove resume/resume_offset kernel parameters from /etc/default/grub 2. update-grub, reboot: hibernate options appear in ubuntu shutdown menu 3. hibernate: works, no more "invalid argument" error. 4. resume(power on): not works - just regular power on. Tried several times. 5. return resume/resume_offset kernel parameters back to /etc/default/grub. 6. initramfs -c -k all : maybe this fixed it? (should not be necessary to do) 7. update-grub 8. hibernate 9. resume: works (!) -- 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/2057687 Title: systemctl hibernate error: "Call to Hibernate failed: Invalid argument" Status in systemd package in Ubuntu: Confirmed Bug description: After upgrading systemd to 255(255.2-3ubuntu2) hibernate stopped working. Trying to hibernate: systemctl hibernate I get: Call to Hibernate failed: Invalid argument systemctl status systemd-hibernate.service - × systemd-hibernate.service - Hibernate Loaded: loaded (/usr/lib/systemd/system/systemd-hibernate.service; static) Active: failed (Result: exit-code) since Tue 2024-03-12 18:48:12 MSK; 1min 33s ago Docs: man:systemd-hibernate.service(8) Process: 4473 ExecStart=/usr/lib/systemd/systemd-sleep hibernate (code=exited, status=1/FAILURE) Main PID: 4473 (code=exited, status=1/FAILURE) CPU: 5ms мар 12 18:48:12 ASUSPRO-P3540FA systemd[1]: Starting systemd-hibernate.service - Hibernate... мар 12 18:48:12 ASUSPRO-P3540FA systemd-sleep[4473]: Failed to find location to hibernate to: Invalid argument мар 12 18:48:12 ASUSPRO-P3540FA systemd[1]: systemd-hibernate.service: Main process exited, code=exited, status=1/FAILURE мар 12 18:48:12 ASUSPRO-P3540FA systemd[1]: systemd-hibernate.service: Failed with result 'exit-code'. мар 12 18:48:12 ASUSPRO-P3540FA systemd[1]: Failed to start systemd-hibernate.service - Hibernate. -- Previous version (254.x) worked: swapfile(on EXT4 fs) is used to hibernate/resume, resume with resume_offset kernel parameters. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2057687/+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 2047447] Re: No valid source.list found while upgrading from mantic to noble
Hello from noble by the way ) ``` $ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu Noble Numbat (development branch) Release:24.04 Codename: noble ``` -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python-apt in Ubuntu. https://bugs.launchpad.net/bugs/2047447 Title: No valid source.list found while upgrading from mantic to noble Status in python-apt package in Ubuntu: Fix Released Status in ubuntu-release-upgrader package in Ubuntu: Invalid Status in python-apt source package in Mantic: Confirmed Status in ubuntu-release-upgrader source package in Mantic: Invalid Bug description: Checking package manager Reading package lists... Done Building dependency tree... Done Reading state information... Done Hit http://fr.archive.ubuntu.com/ubuntu mantic InRelease Hit http://fr.archive.ubuntu.com/ubuntu mantic-updates InRelease Hit http://fr.archive.ubuntu.com/ubuntu mantic-security InRelease Hit http://fr.archive.ubuntu.com/ubuntu mantic-backports InRelease Hit https://packages.gitlab.com/gitlab/gitlab-ce/ubuntu lunar InRelease Fetched 0 B in 0s (0 B/s) Reading package lists... Done Building dependency tree... Done Reading state information... Done Checking for installed snaps Calculating snap size requirements Updating repository information No valid sources.list entry found While scanning your repository information no entry about mantic could be found. An upgrade might not succeed. Do you want to continue anyway? Continue [yN] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-apt/+bug/2047447/+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 2047447] Re: No valid source.list found while upgrading from mantic to noble
> That is not the case Seems you are right In my case there was `/etc/apt/sources.list.d/vscode.list` with content ``` ### THIS FILE IS AUTOMATICALLY CONFIGURED ### # You may comment out this entry, but any other modifications may be lost. ``` If wipe out/remove this file then upgrader does not complain about apt repos -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python-apt in Ubuntu. https://bugs.launchpad.net/bugs/2047447 Title: No valid source.list found while upgrading from mantic to noble Status in python-apt package in Ubuntu: Fix Released Status in ubuntu-release-upgrader package in Ubuntu: Confirmed Status in python-apt source package in Mantic: New Status in ubuntu-release-upgrader source package in Mantic: New Bug description: Checking package manager Reading package lists... Done Building dependency tree... Done Reading state information... Done Hit http://fr.archive.ubuntu.com/ubuntu mantic InRelease Hit http://fr.archive.ubuntu.com/ubuntu mantic-updates InRelease Hit http://fr.archive.ubuntu.com/ubuntu mantic-security InRelease Hit http://fr.archive.ubuntu.com/ubuntu mantic-backports InRelease Hit https://packages.gitlab.com/gitlab/gitlab-ce/ubuntu lunar InRelease Fetched 0 B in 0s (0 B/s) Reading package lists... Done Building dependency tree... Done Reading state information... Done Checking for installed snaps Calculating snap size requirements Updating repository information No valid sources.list entry found While scanning your repository information no entry about mantic could be found. An upgrade might not succeed. Do you want to continue anyway? Continue [yN] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-apt/+bug/2047447/+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 2047447] Re: No valid source.list found while upgrading from mantic to noble
It was upgraded too in prev update ``` $ cat /etc/apt/sources.list.d/vscode.sources Types: deb URIs: http://packages.microsoft.com/repos/code Suites: stable Components: main Architectures: amd64 Signed-By: /etc/apt/trusted.gpg.d/microsoft.gpg ``` -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python-apt in Ubuntu. https://bugs.launchpad.net/bugs/2047447 Title: No valid source.list found while upgrading from mantic to noble Status in python-apt package in Ubuntu: Fix Released Status in ubuntu-release-upgrader package in Ubuntu: Confirmed Status in python-apt source package in Mantic: New Status in ubuntu-release-upgrader source package in Mantic: New Bug description: Checking package manager Reading package lists... Done Building dependency tree... Done Reading state information... Done Hit http://fr.archive.ubuntu.com/ubuntu mantic InRelease Hit http://fr.archive.ubuntu.com/ubuntu mantic-updates InRelease Hit http://fr.archive.ubuntu.com/ubuntu mantic-security InRelease Hit http://fr.archive.ubuntu.com/ubuntu mantic-backports InRelease Hit https://packages.gitlab.com/gitlab/gitlab-ce/ubuntu lunar InRelease Fetched 0 B in 0s (0 B/s) Reading package lists... Done Building dependency tree... Done Reading state information... Done Checking for installed snaps Calculating snap size requirements Updating repository information No valid sources.list entry found While scanning your repository information no entry about mantic could be found. An upgrade might not succeed. Do you want to continue anyway? Continue [yN] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-apt/+bug/2047447/+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 2047447] Re: No valid source.list found while upgrading from mantic to noble
`/etc/apt/sources.list.d/vscode.list` seems created on every vscode update. Seems there some script about it in deb. I definitely remember that I removed that file in past. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python-apt in Ubuntu. https://bugs.launchpad.net/bugs/2047447 Title: No valid source.list found while upgrading from mantic to noble Status in python-apt package in Ubuntu: Fix Released Status in ubuntu-release-upgrader package in Ubuntu: Confirmed Status in python-apt source package in Mantic: New Status in ubuntu-release-upgrader source package in Mantic: New Bug description: Checking package manager Reading package lists... Done Building dependency tree... Done Reading state information... Done Hit http://fr.archive.ubuntu.com/ubuntu mantic InRelease Hit http://fr.archive.ubuntu.com/ubuntu mantic-updates InRelease Hit http://fr.archive.ubuntu.com/ubuntu mantic-security InRelease Hit http://fr.archive.ubuntu.com/ubuntu mantic-backports InRelease Hit https://packages.gitlab.com/gitlab/gitlab-ce/ubuntu lunar InRelease Fetched 0 B in 0s (0 B/s) Reading package lists... Done Building dependency tree... Done Reading state information... Done Checking for installed snaps Calculating snap size requirements Updating repository information No valid sources.list entry found While scanning your repository information no entry about mantic could be found. An upgrade might not succeed. Do you want to continue anyway? Continue [yN] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-apt/+bug/2047447/+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 2047447] Re: No valid source.list found while upgrading from mantic to noble
> Copying those sources as-is into /etc/apt/sources.list.d/ubuntu.sources works fine for me The problem not in "sources" file but "empty" /etc/apt/sources.list Upgrader say about it "No valid sources.list entry found While scanning your repository information no entry about mantic could be found." But maybe I did not correct understand what are you saying about. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python-apt in Ubuntu. https://bugs.launchpad.net/bugs/2047447 Title: No valid source.list found while upgrading from mantic to noble Status in python-apt package in Ubuntu: Fix Released Status in ubuntu-release-upgrader package in Ubuntu: Confirmed Status in python-apt source package in Mantic: New Status in ubuntu-release-upgrader source package in Mantic: New Bug description: Checking package manager Reading package lists... Done Building dependency tree... Done Reading state information... Done Hit http://fr.archive.ubuntu.com/ubuntu mantic InRelease Hit http://fr.archive.ubuntu.com/ubuntu mantic-updates InRelease Hit http://fr.archive.ubuntu.com/ubuntu mantic-security InRelease Hit http://fr.archive.ubuntu.com/ubuntu mantic-backports InRelease Hit https://packages.gitlab.com/gitlab/gitlab-ce/ubuntu lunar InRelease Fetched 0 B in 0s (0 B/s) Reading package lists... Done Building dependency tree... Done Reading state information... Done Checking for installed snaps Calculating snap size requirements Updating repository information No valid sources.list entry found While scanning your repository information no entry about mantic could be found. An upgrade might not succeed. Do you want to continue anyway? Continue [yN] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-apt/+bug/2047447/+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 2057687] [NEW] systemctl hibernate error: "Call to Hibernate failed: Invalid argument"
Public bug reported: After upgrading systemd to 255(255.2-3ubuntu2) hibernate stopped working. Trying to hibernate: systemctl hibernate I get: Call to Hibernate failed: Invalid argument systemctl status systemd-hibernate.service - × systemd-hibernate.service - Hibernate Loaded: loaded (/usr/lib/systemd/system/systemd-hibernate.service; static) Active: failed (Result: exit-code) since Tue 2024-03-12 18:48:12 MSK; 1min 33s ago Docs: man:systemd-hibernate.service(8) Process: 4473 ExecStart=/usr/lib/systemd/systemd-sleep hibernate (code=exited, status=1/FAILURE) Main PID: 4473 (code=exited, status=1/FAILURE) CPU: 5ms мар 12 18:48:12 ASUSPRO-P3540FA systemd[1]: Starting systemd-hibernate.service - Hibernate... мар 12 18:48:12 ASUSPRO-P3540FA systemd-sleep[4473]: Failed to find location to hibernate to: Invalid argument мар 12 18:48:12 ASUSPRO-P3540FA systemd[1]: systemd-hibernate.service: Main process exited, code=exited, status=1/FAILURE мар 12 18:48:12 ASUSPRO-P3540FA systemd[1]: systemd-hibernate.service: Failed with result 'exit-code'. мар 12 18:48:12 ASUSPRO-P3540FA systemd[1]: Failed to start systemd-hibernate.service - Hibernate. -- Previous version (254.x) worked: swapfile(on EXT4 fs) is used to hibernate/resume, resume with resume_offset kernel parameters. ** Affects: systemd (Ubuntu) Importance: Undecided Status: New -- 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/2057687 Title: systemctl hibernate error: "Call to Hibernate failed: Invalid argument" Status in systemd package in Ubuntu: New Bug description: After upgrading systemd to 255(255.2-3ubuntu2) hibernate stopped working. Trying to hibernate: systemctl hibernate I get: Call to Hibernate failed: Invalid argument systemctl status systemd-hibernate.service - × systemd-hibernate.service - Hibernate Loaded: loaded (/usr/lib/systemd/system/systemd-hibernate.service; static) Active: failed (Result: exit-code) since Tue 2024-03-12 18:48:12 MSK; 1min 33s ago Docs: man:systemd-hibernate.service(8) Process: 4473 ExecStart=/usr/lib/systemd/systemd-sleep hibernate (code=exited, status=1/FAILURE) Main PID: 4473 (code=exited, status=1/FAILURE) CPU: 5ms мар 12 18:48:12 ASUSPRO-P3540FA systemd[1]: Starting systemd-hibernate.service - Hibernate... мар 12 18:48:12 ASUSPRO-P3540FA systemd-sleep[4473]: Failed to find location to hibernate to: Invalid argument мар 12 18:48:12 ASUSPRO-P3540FA systemd[1]: systemd-hibernate.service: Main process exited, code=exited, status=1/FAILURE мар 12 18:48:12 ASUSPRO-P3540FA systemd[1]: systemd-hibernate.service: Failed with result 'exit-code'. мар 12 18:48:12 ASUSPRO-P3540FA systemd[1]: Failed to start systemd-hibernate.service - Hibernate. -- Previous version (254.x) worked: swapfile(on EXT4 fs) is used to hibernate/resume, resume with resume_offset kernel parameters. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2057687/+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 2056368] Re: crash on app start after upgrade 23.0.4-0ubuntu1~22.04.1, 23.2.1-1ubuntu3.1~22.04.2
Downgrading to 23.0.4-0ubuntu1~22.04.1 resolves the issues.
--
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/2056368
Title:
crash on app start after upgrade 23.0.4-0ubuntu1~22.04.1,
23.2.1-1ubuntu3.1~22.04.2
Status in mesa package in Ubuntu:
New
Bug description:
Firefox:
[GFX1-]: Failed to compile vertex shader: gpu_cache_update
[ERROR webrender::device::gl] Failed to compile vertex shader:
gpu_cache_update
[GFX1-]: wr_window_new: Shader(Compilation("gpu_cache_update", ""))
[GFX1-]: Failed to connect WebRenderBridgeChild. isParent=true
[GFX1-]: Fallback WR to SW-WR
Alacritty:
Error: Render(Shader(Compile("")))
$ lsb_release -rd
Description: Ubuntu 22.04.4 LTS
Release: 22.04
$ glxinfo -B
name of display: :0
display: :0 screen: 0
direct rendering: Yes
Extended renderer info (GLX_MESA_query_renderer):
Vendor: Intel (0x8086)
Device: Mesa Intel(R) UHD Graphics 620 (WHL GT2) (0x3ea0)
Version: 23.2.1
Accelerated: yes
Video memory: 15668MB
Unified memory: yes
Preferred profile: core (0x1)
Max core profile version: 4.6
Max compat profile version: 4.6
Max GLES1 profile version: 1.1
Max GLES[23] profile version: 3.2
OpenGL vendor string: Intel
OpenGL renderer string: Mesa Intel(R) UHD Graphics 620 (WHL GT2)
OpenGL core profile version string: 4.6 (Core Profile) Mesa
23.2.1-1ubuntu3.1~22.04.2
OpenGL core profile shading language version string: 4.60
OpenGL core profile context flags: (none)
OpenGL core profile profile mask: core profile
OpenGL version string: 4.6 (Compatibility Profile) Mesa
23.2.1-1ubuntu3.1~22.04.2
OpenGL shading language version string: 4.60
OpenGL context flags: (none)
OpenGL profile mask: compatibility profile
OpenGL ES profile version string: OpenGL ES 3.2 Mesa 23.2.1-1ubuntu3.1~22.04.2
OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.20
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/2056368/+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 2056368] [NEW] crash on app start after upgrade 23.0.4-0ubuntu1~22.04.1, 23.2.1-1ubuntu3.1~22.04.2
Public bug reported:
Firefox:
[GFX1-]: Failed to compile vertex shader: gpu_cache_update
[ERROR webrender::device::gl] Failed to compile vertex shader: gpu_cache_update
[GFX1-]: wr_window_new: Shader(Compilation("gpu_cache_update", ""))
[GFX1-]: Failed to connect WebRenderBridgeChild. isParent=true
[GFX1-]: Fallback WR to SW-WR
Alacritty:
Error: Render(Shader(Compile("")))
$ lsb_release -rd
Description:Ubuntu 22.04.4 LTS
Release:22.04
$ glxinfo -B
name of display: :0
display: :0 screen: 0
direct rendering: Yes
Extended renderer info (GLX_MESA_query_renderer):
Vendor: Intel (0x8086)
Device: Mesa Intel(R) UHD Graphics 620 (WHL GT2) (0x3ea0)
Version: 23.2.1
Accelerated: yes
Video memory: 15668MB
Unified memory: yes
Preferred profile: core (0x1)
Max core profile version: 4.6
Max compat profile version: 4.6
Max GLES1 profile version: 1.1
Max GLES[23] profile version: 3.2
OpenGL vendor string: Intel
OpenGL renderer string: Mesa Intel(R) UHD Graphics 620 (WHL GT2)
OpenGL core profile version string: 4.6 (Core Profile) Mesa
23.2.1-1ubuntu3.1~22.04.2
OpenGL core profile shading language version string: 4.60
OpenGL core profile context flags: (none)
OpenGL core profile profile mask: core profile
OpenGL version string: 4.6 (Compatibility Profile) Mesa
23.2.1-1ubuntu3.1~22.04.2
OpenGL shading language version string: 4.60
OpenGL context flags: (none)
OpenGL profile mask: compatibility profile
OpenGL ES profile version string: OpenGL ES 3.2 Mesa 23.2.1-1ubuntu3.1~22.04.2
OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.20
** Affects: mesa (Ubuntu)
Importance: Undecided
Status: New
--
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/2056368
Title:
crash on app start after upgrade 23.0.4-0ubuntu1~22.04.1,
23.2.1-1ubuntu3.1~22.04.2
Status in mesa package in Ubuntu:
New
Bug description:
Firefox:
[GFX1-]: Failed to compile vertex shader: gpu_cache_update
[ERROR webrender::device::gl] Failed to compile vertex shader:
gpu_cache_update
[GFX1-]: wr_window_new: Shader(Compilation("gpu_cache_update", ""))
[GFX1-]: Failed to connect WebRenderBridgeChild. isParent=true
[GFX1-]: Fallback WR to SW-WR
Alacritty:
Error: Render(Shader(Compile("")))
$ lsb_release -rd
Description: Ubuntu 22.04.4 LTS
Release: 22.04
$ glxinfo -B
name of display: :0
display: :0 screen: 0
direct rendering: Yes
Extended renderer info (GLX_MESA_query_renderer):
Vendor: Intel (0x8086)
Device: Mesa Intel(R) UHD Graphics 620 (WHL GT2) (0x3ea0)
Version: 23.2.1
Accelerated: yes
Video memory: 15668MB
Unified memory: yes
Preferred profile: core (0x1)
Max core profile version: 4.6
Max compat profile version: 4.6
Max GLES1 profile version: 1.1
Max GLES[23] profile version: 3.2
OpenGL vendor string: Intel
OpenGL renderer string: Mesa Intel(R) UHD Graphics 620 (WHL GT2)
OpenGL core profile version string: 4.6 (Core Profile) Mesa
23.2.1-1ubuntu3.1~22.04.2
OpenGL core profile shading language version string: 4.60
OpenGL core profile context flags: (none)
OpenGL core profile profile mask: core profile
OpenGL version string: 4.6 (Compatibility Profile) Mesa
23.2.1-1ubuntu3.1~22.04.2
OpenGL shading language version string: 4.60
OpenGL context flags: (none)
OpenGL profile mask: compatibility profile
OpenGL ES profile version string: OpenGL ES 3.2 Mesa 23.2.1-1ubuntu3.1~22.04.2
OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.20
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/2056368/+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 2035406] Re: udev update has broken ubuntu's ability to import photos in digikam, gphoto2 can no longer see usb camera, entangle can no longer see camera
I downgraded to 249.11-0ubuntu3.9, 249.11-0ubuntu3.7 Because I know for a Fact I had no issues with it, My last install was working with 249.11-0ubuntu3.9, you rolled out the update to 249.11-0ubuntu3.10 and that is when all this started. I simply went back to an older version after a fresh install to be safe, one computer and already lost 2 days on it, could not afford to try out 249.11-0ubuntu3.9 again and hope it all worked, I also know for a fact it Broke on 249.11-0ubuntu3.10. Again I am no programmer or software engineer, so you do what you feel is best for the code, I know what broke, when it broke, but I will never know why it broke. Close this bug out if your comfortable with rolling out 249.11-0ubuntu3.10. -- 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/2035406 Title: udev update has broken ubuntu's ability to import photos in digikam, gphoto2 can no longer see usb camera, entangle can no longer see camera Status in systemd package in Ubuntu: Invalid Status in systemd source package in Jammy: Incomplete Status in systemd source package in Lunar: Invalid Status in systemd source package in Mantic: Invalid Bug description: udev update has broken ubuntu's ability to import photos in digikam, gphoto2 can no longer see usb camera, entangle can no longer see camera after Upgrade: udev:amd64 (249.11-0ubuntu3.9, 249.11-0ubuntu3.10), systemd-timesyncd:amd64 (249.11-0ubuntu3.9, 249.11-0ubuntu3.10), libpam-systemd:amd64 (249.11-0ubuntu3.9, 249.11-0ubuntu3.10), libpam-systemd:i386 (249.11-0ubuntu3.9, 249.11-0ubuntu3.10), libsystemd0:amd64 (249.11-0ubuntu3.9, 249.11-0ubuntu3.10), libsystemd0:i386 (249.11-0ubuntu3.9, 249.11-0ubuntu3.10), libnss-systemd:amd64 (249.11-0ubuntu3.9, 249.11-0ubuntu3.10), libudev-dev:amd64 (249.11-0ubuntu3.9, 249.11-0ubuntu3.10), systemd:amd64 (249.11-0ubuntu3.9, 249.11-0ubuntu3.10), libudev1:amd64 (249.11-0ubuntu3.9, 249.11-0ubuntu3.10), libudev1:i386 (249.11-0ubuntu3.9, 249.11-0ubuntu3.10), systemd-sysv:amd64 (249.11-0ubuntu3.9, 249.11-0ubuntu3.10) ubuntu no longer allows gphoto2 or entangle control of my dslr, lsusb sees the camera fine, but the upgrade broke the usage, and cant roll back shows it will break system to roll back please fix ASAP. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: udev 249.11-0ubuntu3.10 ProcVersionSignature: Ubuntu 6.2.0-1009.9~22.04.1-lowlatency 6.2.13 Uname: Linux 6.2.0-1009-lowlatency x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Wed Sep 13 18:16:14 2023 InstallationDate: Installed on 2023-08-23 (21 days ago) InstallationMedia: Ubuntu-Studio 22.04.3 LTS "Jammy Jellyfish" - Release amd64 (20230807) MachineType: Alienware Alienware 18 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.2.0-1009-lowlatency root=UUID=17502284-0952-44fe-81f8-54cebffc3800 ro threadirqs quiet splash vt.handoff=1 SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/22/2019 dmi.bios.vendor: Alienware dmi.bios.version: A15 dmi.board.name: 0FT9KT dmi.board.vendor: Alienware dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Alienware dmi.chassis.version: A15 dmi.ec.firmware.release: 1.1 dmi.modalias: dmi:bvnAlienware:bvrA15:bd07/22/2019:efr1.1:svnAlienware:pnAlienware18:pvrA15:rvnAlienware:rn0FT9KT:rvrA00:cvnAlienware:ct8:cvrA15:skuAlienware18: dmi.product.family: 00 dmi.product.name: Alienware 18 dmi.product.sku: Alienware 18 dmi.product.version: A15 dmi.sys.vendor: Alienware To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2035406/+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 2035406] Re: udev update has broken ubuntu's ability to import photos in digikam, gphoto2 can no longer see usb camera, entangle can no longer see camera
22.04.3LTS -Ubuntu Downgrade: udev:amd64 (249.11-0ubuntu3.9, 249.11-0ubuntu3.7), libudev1:amd64 (249.11-0ubuntu3.9, 249.11-0ubuntu3.7) Camera any kind, I tried both my NikonD5600 and Olympus OM-D E-M5, which both work again as they should and did before this mess started. -- 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/2035406 Title: udev update has broken ubuntu's ability to import photos in digikam, gphoto2 can no longer see usb camera, entangle can no longer see camera Status in systemd package in Ubuntu: Invalid Status in systemd source package in Jammy: Incomplete Status in systemd source package in Lunar: Invalid Status in systemd source package in Mantic: Invalid Bug description: udev update has broken ubuntu's ability to import photos in digikam, gphoto2 can no longer see usb camera, entangle can no longer see camera after Upgrade: udev:amd64 (249.11-0ubuntu3.9, 249.11-0ubuntu3.10), systemd-timesyncd:amd64 (249.11-0ubuntu3.9, 249.11-0ubuntu3.10), libpam-systemd:amd64 (249.11-0ubuntu3.9, 249.11-0ubuntu3.10), libpam-systemd:i386 (249.11-0ubuntu3.9, 249.11-0ubuntu3.10), libsystemd0:amd64 (249.11-0ubuntu3.9, 249.11-0ubuntu3.10), libsystemd0:i386 (249.11-0ubuntu3.9, 249.11-0ubuntu3.10), libnss-systemd:amd64 (249.11-0ubuntu3.9, 249.11-0ubuntu3.10), libudev-dev:amd64 (249.11-0ubuntu3.9, 249.11-0ubuntu3.10), systemd:amd64 (249.11-0ubuntu3.9, 249.11-0ubuntu3.10), libudev1:amd64 (249.11-0ubuntu3.9, 249.11-0ubuntu3.10), libudev1:i386 (249.11-0ubuntu3.9, 249.11-0ubuntu3.10), systemd-sysv:amd64 (249.11-0ubuntu3.9, 249.11-0ubuntu3.10) ubuntu no longer allows gphoto2 or entangle control of my dslr, lsusb sees the camera fine, but the upgrade broke the usage, and cant roll back shows it will break system to roll back please fix ASAP. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: udev 249.11-0ubuntu3.10 ProcVersionSignature: Ubuntu 6.2.0-1009.9~22.04.1-lowlatency 6.2.13 Uname: Linux 6.2.0-1009-lowlatency x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Wed Sep 13 18:16:14 2023 InstallationDate: Installed on 2023-08-23 (21 days ago) InstallationMedia: Ubuntu-Studio 22.04.3 LTS "Jammy Jellyfish" - Release amd64 (20230807) MachineType: Alienware Alienware 18 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.2.0-1009-lowlatency root=UUID=17502284-0952-44fe-81f8-54cebffc3800 ro threadirqs quiet splash vt.handoff=1 SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/22/2019 dmi.bios.vendor: Alienware dmi.bios.version: A15 dmi.board.name: 0FT9KT dmi.board.vendor: Alienware dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Alienware dmi.chassis.version: A15 dmi.ec.firmware.release: 1.1 dmi.modalias: dmi:bvnAlienware:bvrA15:bd07/22/2019:efr1.1:svnAlienware:pnAlienware18:pvrA15:rvnAlienware:rn0FT9KT:rvrA00:cvnAlienware:ct8:cvrA15:skuAlienware18: dmi.product.family: 00 dmi.product.name: Alienware 18 dmi.product.sku: Alienware 18 dmi.product.version: A15 dmi.sys.vendor: Alienware To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2035406/+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 2035406] Re: udev update has broken ubuntu's ability to import photos in digikam, gphoto2 can no longer see usb camera, entangle can no longer see camera
Tried all your steps, they kept breaking my system more and more. Had to re-install ubutnu from liveusb, installed synaptic downgraded udev and locked verison, read markings, reboot, update, upgrade reboot, get my audio and bluetooth up and working again reboot, everything works, its your udev update, dont know how, dont know why, and not sure how my system is the only one effected, but its your udev update. Thanks for your help, hope you figure it out before it causes more issues wide spread. Im out for now on this bug. As fresh install and down grade udev and locking version has everything working again. -- 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/2035406 Title: udev update has broken ubuntu's ability to import photos in digikam, gphoto2 can no longer see usb camera, entangle can no longer see camera Status in systemd package in Ubuntu: Invalid Status in systemd source package in Jammy: Incomplete Status in systemd source package in Lunar: Invalid Status in systemd source package in Mantic: Invalid Bug description: udev update has broken ubuntu's ability to import photos in digikam, gphoto2 can no longer see usb camera, entangle can no longer see camera after Upgrade: udev:amd64 (249.11-0ubuntu3.9, 249.11-0ubuntu3.10), systemd-timesyncd:amd64 (249.11-0ubuntu3.9, 249.11-0ubuntu3.10), libpam-systemd:amd64 (249.11-0ubuntu3.9, 249.11-0ubuntu3.10), libpam-systemd:i386 (249.11-0ubuntu3.9, 249.11-0ubuntu3.10), libsystemd0:amd64 (249.11-0ubuntu3.9, 249.11-0ubuntu3.10), libsystemd0:i386 (249.11-0ubuntu3.9, 249.11-0ubuntu3.10), libnss-systemd:amd64 (249.11-0ubuntu3.9, 249.11-0ubuntu3.10), libudev-dev:amd64 (249.11-0ubuntu3.9, 249.11-0ubuntu3.10), systemd:amd64 (249.11-0ubuntu3.9, 249.11-0ubuntu3.10), libudev1:amd64 (249.11-0ubuntu3.9, 249.11-0ubuntu3.10), libudev1:i386 (249.11-0ubuntu3.9, 249.11-0ubuntu3.10), systemd-sysv:amd64 (249.11-0ubuntu3.9, 249.11-0ubuntu3.10) ubuntu no longer allows gphoto2 or entangle control of my dslr, lsusb sees the camera fine, but the upgrade broke the usage, and cant roll back shows it will break system to roll back please fix ASAP. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: udev 249.11-0ubuntu3.10 ProcVersionSignature: Ubuntu 6.2.0-1009.9~22.04.1-lowlatency 6.2.13 Uname: Linux 6.2.0-1009-lowlatency x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Wed Sep 13 18:16:14 2023 InstallationDate: Installed on 2023-08-23 (21 days ago) InstallationMedia: Ubuntu-Studio 22.04.3 LTS "Jammy Jellyfish" - Release amd64 (20230807) MachineType: Alienware Alienware 18 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.2.0-1009-lowlatency root=UUID=17502284-0952-44fe-81f8-54cebffc3800 ro threadirqs quiet splash vt.handoff=1 SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/22/2019 dmi.bios.vendor: Alienware dmi.bios.version: A15 dmi.board.name: 0FT9KT dmi.board.vendor: Alienware dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Alienware dmi.chassis.version: A15 dmi.ec.firmware.release: 1.1 dmi.modalias: dmi:bvnAlienware:bvrA15:bd07/22/2019:efr1.1:svnAlienware:pnAlienware18:pvrA15:rvnAlienware:rn0FT9KT:rvrA00:cvnAlienware:ct8:cvrA15:skuAlienware18: dmi.product.family: 00 dmi.product.name: Alienware 18 dmi.product.sku: Alienware 18 dmi.product.version: A15 dmi.sys.vendor: Alienware To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2035406/+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 2035406] Re: udev update has broken ubuntu's ability to import photos in digikam, gphoto2 can no longer see usb camera, entangle can no longer see camera
PROBLEM STILL PERSISTS, and Now I HAVE NO AUDIO. No I have to do a fresh install. You guys really need to pay better attention to your updates, this is a system break not an upgrade. Im really not happy, and as I love ubuntu, and I really appreciate all the hard work you guys all put into making and keeping it great, sometimes I wish you took just a few extra minuets to verify nothing will break with your new updates. It sure would saved all of us a bunch of work. Now back to re-installing ubuntu and putting it all back together, hoping your update does not break it again. -- 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/2035406 Title: udev update has broken ubuntu's ability to import photos in digikam, gphoto2 can no longer see usb camera, entangle can no longer see camera Status in systemd package in Ubuntu: Invalid Status in systemd source package in Jammy: Incomplete Status in systemd source package in Lunar: Invalid Status in systemd source package in Mantic: Invalid Bug description: udev update has broken ubuntu's ability to import photos in digikam, gphoto2 can no longer see usb camera, entangle can no longer see camera after Upgrade: udev:amd64 (249.11-0ubuntu3.9, 249.11-0ubuntu3.10), systemd-timesyncd:amd64 (249.11-0ubuntu3.9, 249.11-0ubuntu3.10), libpam-systemd:amd64 (249.11-0ubuntu3.9, 249.11-0ubuntu3.10), libpam-systemd:i386 (249.11-0ubuntu3.9, 249.11-0ubuntu3.10), libsystemd0:amd64 (249.11-0ubuntu3.9, 249.11-0ubuntu3.10), libsystemd0:i386 (249.11-0ubuntu3.9, 249.11-0ubuntu3.10), libnss-systemd:amd64 (249.11-0ubuntu3.9, 249.11-0ubuntu3.10), libudev-dev:amd64 (249.11-0ubuntu3.9, 249.11-0ubuntu3.10), systemd:amd64 (249.11-0ubuntu3.9, 249.11-0ubuntu3.10), libudev1:amd64 (249.11-0ubuntu3.9, 249.11-0ubuntu3.10), libudev1:i386 (249.11-0ubuntu3.9, 249.11-0ubuntu3.10), systemd-sysv:amd64 (249.11-0ubuntu3.9, 249.11-0ubuntu3.10) ubuntu no longer allows gphoto2 or entangle control of my dslr, lsusb sees the camera fine, but the upgrade broke the usage, and cant roll back shows it will break system to roll back please fix ASAP. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: udev 249.11-0ubuntu3.10 ProcVersionSignature: Ubuntu 6.2.0-1009.9~22.04.1-lowlatency 6.2.13 Uname: Linux 6.2.0-1009-lowlatency x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Wed Sep 13 18:16:14 2023 InstallationDate: Installed on 2023-08-23 (21 days ago) InstallationMedia: Ubuntu-Studio 22.04.3 LTS "Jammy Jellyfish" - Release amd64 (20230807) MachineType: Alienware Alienware 18 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.2.0-1009-lowlatency root=UUID=17502284-0952-44fe-81f8-54cebffc3800 ro threadirqs quiet splash vt.handoff=1 SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/22/2019 dmi.bios.vendor: Alienware dmi.bios.version: A15 dmi.board.name: 0FT9KT dmi.board.vendor: Alienware dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Alienware dmi.chassis.version: A15 dmi.ec.firmware.release: 1.1 dmi.modalias: dmi:bvnAlienware:bvrA15:bd07/22/2019:efr1.1:svnAlienware:pnAlienware18:pvrA15:rvnAlienware:rn0FT9KT:rvrA00:cvnAlienware:ct8:cvrA15:skuAlienware18: dmi.product.family: 00 dmi.product.name: Alienware 18 dmi.product.sku: Alienware 18 dmi.product.version: A15 dmi.sys.vendor: Alienware To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2035406/+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 2035406] Re: udev update has broken ubuntu's ability to import photos in digikam, gphoto2 can no longer see usb camera, entangle can no longer see camera
More interesting info, so I just tested digiKam-8.1.0-x86-64.appimage and it Can talk to my camera, but the Installed digikam package CAN NOT TALK, but I still can not use gphoto2 to stream my camera, nor can I use entangle to use my camera tethered. Because they can not talk to the camera, I understand the appimage has everything self contained, so it makes sense it works that way. But I wanted to let you know, as somehow it may be useful to figuring out this very odd bug. -- 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/2035406 Title: udev update has broken ubuntu's ability to import photos in digikam, gphoto2 can no longer see usb camera, entangle can no longer see camera Status in systemd package in Ubuntu: Invalid Status in systemd source package in Jammy: Incomplete Status in systemd source package in Lunar: Invalid Status in systemd source package in Mantic: Invalid Bug description: udev update has broken ubuntu's ability to import photos in digikam, gphoto2 can no longer see usb camera, entangle can no longer see camera after Upgrade: udev:amd64 (249.11-0ubuntu3.9, 249.11-0ubuntu3.10), systemd-timesyncd:amd64 (249.11-0ubuntu3.9, 249.11-0ubuntu3.10), libpam-systemd:amd64 (249.11-0ubuntu3.9, 249.11-0ubuntu3.10), libpam-systemd:i386 (249.11-0ubuntu3.9, 249.11-0ubuntu3.10), libsystemd0:amd64 (249.11-0ubuntu3.9, 249.11-0ubuntu3.10), libsystemd0:i386 (249.11-0ubuntu3.9, 249.11-0ubuntu3.10), libnss-systemd:amd64 (249.11-0ubuntu3.9, 249.11-0ubuntu3.10), libudev-dev:amd64 (249.11-0ubuntu3.9, 249.11-0ubuntu3.10), systemd:amd64 (249.11-0ubuntu3.9, 249.11-0ubuntu3.10), libudev1:amd64 (249.11-0ubuntu3.9, 249.11-0ubuntu3.10), libudev1:i386 (249.11-0ubuntu3.9, 249.11-0ubuntu3.10), systemd-sysv:amd64 (249.11-0ubuntu3.9, 249.11-0ubuntu3.10) ubuntu no longer allows gphoto2 or entangle control of my dslr, lsusb sees the camera fine, but the upgrade broke the usage, and cant roll back shows it will break system to roll back please fix ASAP. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: udev 249.11-0ubuntu3.10 ProcVersionSignature: Ubuntu 6.2.0-1009.9~22.04.1-lowlatency 6.2.13 Uname: Linux 6.2.0-1009-lowlatency x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Wed Sep 13 18:16:14 2023 InstallationDate: Installed on 2023-08-23 (21 days ago) InstallationMedia: Ubuntu-Studio 22.04.3 LTS "Jammy Jellyfish" - Release amd64 (20230807) MachineType: Alienware Alienware 18 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.2.0-1009-lowlatency root=UUID=17502284-0952-44fe-81f8-54cebffc3800 ro threadirqs quiet splash vt.handoff=1 SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/22/2019 dmi.bios.vendor: Alienware dmi.bios.version: A15 dmi.board.name: 0FT9KT dmi.board.vendor: Alienware dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Alienware dmi.chassis.version: A15 dmi.ec.firmware.release: 1.1 dmi.modalias: dmi:bvnAlienware:bvrA15:bd07/22/2019:efr1.1:svnAlienware:pnAlienware18:pvrA15:rvnAlienware:rn0FT9KT:rvrA00:cvnAlienware:ct8:cvrA15:skuAlienware18: dmi.product.family: 00 dmi.product.name: Alienware 18 dmi.product.sku: Alienware 18 dmi.product.version: A15 dmi.sys.vendor: Alienware To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2035406/+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 2035406] Re: udev update has broken ubuntu's ability to import photos in digikam, gphoto2 can no longer see usb camera, entangle can no longer see camera
Dont know if this helps, but here is a complete list of installed libnova-0.16-0 install libgpg-error-l10n install dpkginstall kerneloops install libkf5quickaddons5 install golang-golang-x-term-devinstall fontconfig:i386 install r-cran-quantreg install libkdecorations2-5v5install libvulkan1 install libvulkan1:i386 install telnet install libgdal30 install libkf5alarmcalendar5abi2install r-cran-evd install signon-ui-service install libdleyna-core-1.0-5install libnetfilter-conntrack3 install php-composer-metadata-minifier install python3-incremental install libkf5wallet-data install megapixels install libqt5webengine-datainstall php-symfony-config install libkf5konq6 install breeze install libkf5mailtransportakonadi5 install lsb-release install libtext-unidecode-perl install clamav-daemon install libpulse-java install puredata-import install libpipewire-0.3-dev install libevent-pthreads-2.1-7 install plasma-runners-addons install r-cran-fnn install r-cran-mlmetricsinstall clamav-milter install gconf2-common install fonts-cantarell install r-cran-fts install libgucharmap-2-90-7 install python3-pyxattr install libsphinxbase3 install librust-syn+printing-devinstall libkf5identitymanagement5abi1 install python3-parso install libklu1 install libkf5kdelibs4support5-bin install cervisiainstall libjs-prettify install r-cran-jquerylibinstall libssh2-1 install libcuda1-340install libsub-exporter-perlinstall fonts-sil-andikainstall libsynctex2 install tcpdump install libperl5.34 install node-highlight.js install libokular5core10install fonts-tlwg-purisa-ttf install fonts-tibetan-machine install vlc-plugin-qt install libsimage-dev install tracker install libopenblas0install openjdk-11-jre install xserver-xorg-video-nouveau install libblkid-devinstall dmidecode install r-cran-gsl install libspa-0.2-dev install libel-api-java install r-cran-spatstat.sparse install libcups2install jalvinstall libpoppler-qt5-1install libneon27-gnutlsinstall libkf5dav-data install lintian install gnustep-back0.29install qttranslations5-l10ninstall pkg-kde-tools install libxcb-present0 install libxcb-present0:i386install libvlc5 install libxapian30 install libwrap0install python3-jediinstall r-cran-hms install dvipng install fonts-kacst-one install python3-appdirs install libcanberra-gtk3-0 install reiserfsprogs install libkf5kipi32.0.0install node-acorn install libkeyutils1install libkeyutils1:i386 install libmrpt-common-dev install libkf5mailimporterakonadi5 install python3-pycparser install python3-blinker install lsp-plugins-lv2 install gstreamer1.0-qt5install qtchooser install debhelper install ruby-sdbm install libkf5widgetsaddons5install kwave install qtspeech5-flite-plugin install libyajl2install libhtml-treebuilder-xpath-perl install python3-pyclamd install libhtml-treebuilder-libxml-perl install libselinux1-dev install r-cran-ini install chafa install libxtables12install libkpimimportwizard5install libcurl4install fonts-jura install libpolkit-agent-1-0 install dv4linstall libupower-glib3 install libxml-namespacesupport-perlinstall dmeventdinstall fonts-lohit-beng-bengaliinstall libqt5websockets5 install golang-go install librust-winapi-x86-64-pc-windows-gnu-devinstall filelight install libkf5baloowidgets-data install libalgorithm-merge-perl install libobasis7.6-librelogo install libcsound64-6.0 install gir1.2-wp-0.4 install qastools-common install
[Touch-packages] [Bug 2035406] Re: udev update has broken ubuntu's ability to import photos in digikam, gphoto2 can no longer see usb camera, entangle can no longer see camera
Tried to stream with debug,
gphoto2 --stdout --capture-movie --debug | ffmpeg -i - -vcodec rawvideo
-pix_fmt yuv420p -threads 0 -f v4l2 /dev/video0
0.000107 main(2): ALWAYS INCLUDE THE FOLLOWING LINES
WHEN SENDING DEBUG MESSAGES TO THE MAILING LIST:
0.000131 main(2): gphoto2 2.5.27
0.000137 main(2): gphoto2 has been compiled with the
following options:
0.000145 main(2): + gcc (C compiler used)
0.000148 main(2): + popt (mandatory, for handling
command-line parameters)
0.000151 main(2): + exif (for displaying EXIF
information)
0.000154 main(2): + cdk (for accessing configuration
options)
0.000157 main(2): + aa (for displaying live previews)
0.000161 main(2): + jpeg (for displaying live previews
in JPEG format)
0.000164 main(2): + readline (for easy navigation in
the shell)
0.000172 main(2): libgphoto2 2.5.31
0.000175 main(2): libgphoto2 has been compiled with the
following options:
0.000180 main(2): + standard camlib set SKIPPING SOME
(ax203 canon digigr8 dimagev directory jl2005a jl2005c kodak_dc240 mars pentax
ptp2 ricoh_g3 sierra sonix sq905 st2205 topfield tp6801 SKIPPING docupen lumix)
0.000184 main(2): + gcc (C compiler used)
0.000187 main(2): + no ltdl (for portable loading of
camlibs)
0.000190 main(2): + EXIF (for special handling of EXIF
files)
0.000196 main(2): libgphoto2_port 0.12.2
0.000200 main(2): libgphoto2_port has been compiled
with the following options:
0.000203 main(2): + iolibs: disk ptpip serial
0.000206 main(2): + gcc (C compiler used)
0.000211 main(2): + no ltdl (for portable loading of
iolibs)
0.000214 main(2): + EXIF (for vusb)
0.000217 main(2): + no USB (for USB cameras)
0.000221 main(2): + serial (for serial cameras)
0.000224 main(2): + no resmgr (serial port access and
locking)
0.000227 main(2): + no ttylock (serial port locking)
0.000230 main(2): + no lockdev (serial port locking)
0.000235 main(2): CAMLIBS env var not set, using
compile-time default instead
0.000238 main(2): IOLIBS env var not set, using
compile-time default instead
0.000242 main(2): invoked with following arguments:
0.000245 main(2): --stdout
0.000248 main(2): --capture-movie
0.000252 main(2): --debug
0.000268 load_settings (2): Creating gphoto config directory
('/home/pasjrwoctx/.gphoto')
0.000306 load_settings (2): Loading settings from file
'/home/pasjrwoctx/.gphoto/settings'.
0.000341 main(2): The user has not specified both a
model and a port. Try to figure them out.
0.000347 gp_port_init_localedir (2): localedir has been set to
/usr/local/share/locale (compile-time default)
0.000353 gp_port_info_list_load (2): Using ltdl to load io-drivers from
'/usr/local/lib/libgphoto2_port/0.12.2'...
0.000410 foreach_func(2): Called for filename
'/usr/local/lib/libgphoto2_port/0.12.2/disk'.
0.000644 gp_port_library_list(2): found fstab fstype vfat
0.000660 gp_port_library_list(2): found fstab fstype ext4
0.000667 gp_port_library_list(2): found fstab fstype ext4
0.000676 gp_port_library_list(2): found fstab fstype tmpfs
0.000757 gp_port_library_list(2): found mtab fstype sysfs
0.000763 gp_port_library_list(2): found mtab fstype proc
0.000767 gp_port_library_list(2): found mtab fstype devtmpfs
0.000779 gp_port_library_list(2): found mtab fstype devpts
0.000784 gp_port_library_list(2): found mtab fstype tmpfs
0.000794 gp_port_library_list(2): found mtab fstype ext4
0.000801 gp_port_library_list(2): found mtab fstype securityfs
0.000805 gp_port_library_list(2): found mtab fstype tmpfs
0.000817 gp_port_library_list(2): found mtab fstype tmpfs
0.000829 gp_port_library_list(2): found mtab fstype cgroup2
0.000833 gp_port_library_list(2): found mtab fstype pstore
0.000846 gp_port_library_list(2): found mtab fstype bpf
0.000857 gp_port_library_list(2): found mtab fstype autofs
0.000863 gp_port_library_list(2): found mtab fstype mqueue
0.000890 gp_port_library_list(2): found mtab fstype hugetlbfs
0.000902 gp_port_library_list
[Touch-packages] [Bug 2035406] Re: udev update has broken ubuntu's ability to import photos in digikam, gphoto2 can no longer see usb camera, entangle can no longer see camera
In order to roll back udev in Synaptic, I get To Be Removed libgstreamer-plugins-base1.0-dev libgudev-1.0-dev libnm0:i386 libpipewire-0.3-0:i386 libpipewire-0.3-modules:i386 libspa-0.2-modules:i386 libudev-dev libudev1:i386 pipewire:i386 steam:i386 To be downgraded libudev1 I cant roll back or lose functionality and software. Im not sure how all this works together, but that update really messed things up, and I am no Programmer or Engineer, but normally I can with a little bit of digging, figure things out, but this has me very confused, as none of this should be tied together, and the bug has to do with how udev handles protocols for camera to software, because the computer can in fact see the camera when attached, the software is simply blocked from seeing the camera. USB harddrive not affected, I tried to reprogram my hand held Ham radio via usb, worked fine, it simply between what ever protocols ubuntu, udev and software packages use to see and communicate with cameras. And as a digital creator, this is a huge issue for me. If I do a fresh install I lose another 2 days getting everything back up running, not to mention I dont have extra drives right now for backing up, nor the funds to buy one, also the reason I have yet to, is if I do, and go to update, and this all happens again, then I am further behind. So I am trying to figure out how this update broke my system, and fix it so it is right. -- 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/2035406 Title: udev update has broken ubuntu's ability to import photos in digikam, gphoto2 can no longer see usb camera, entangle can no longer see camera Status in systemd package in Ubuntu: Invalid Status in systemd source package in Jammy: Incomplete Status in systemd source package in Lunar: Invalid Status in systemd source package in Mantic: Invalid Bug description: udev update has broken ubuntu's ability to import photos in digikam, gphoto2 can no longer see usb camera, entangle can no longer see camera after Upgrade: udev:amd64 (249.11-0ubuntu3.9, 249.11-0ubuntu3.10), systemd-timesyncd:amd64 (249.11-0ubuntu3.9, 249.11-0ubuntu3.10), libpam-systemd:amd64 (249.11-0ubuntu3.9, 249.11-0ubuntu3.10), libpam-systemd:i386 (249.11-0ubuntu3.9, 249.11-0ubuntu3.10), libsystemd0:amd64 (249.11-0ubuntu3.9, 249.11-0ubuntu3.10), libsystemd0:i386 (249.11-0ubuntu3.9, 249.11-0ubuntu3.10), libnss-systemd:amd64 (249.11-0ubuntu3.9, 249.11-0ubuntu3.10), libudev-dev:amd64 (249.11-0ubuntu3.9, 249.11-0ubuntu3.10), systemd:amd64 (249.11-0ubuntu3.9, 249.11-0ubuntu3.10), libudev1:amd64 (249.11-0ubuntu3.9, 249.11-0ubuntu3.10), libudev1:i386 (249.11-0ubuntu3.9, 249.11-0ubuntu3.10), systemd-sysv:amd64 (249.11-0ubuntu3.9, 249.11-0ubuntu3.10) ubuntu no longer allows gphoto2 or entangle control of my dslr, lsusb sees the camera fine, but the upgrade broke the usage, and cant roll back shows it will break system to roll back please fix ASAP. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: udev 249.11-0ubuntu3.10 ProcVersionSignature: Ubuntu 6.2.0-1009.9~22.04.1-lowlatency 6.2.13 Uname: Linux 6.2.0-1009-lowlatency x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Wed Sep 13 18:16:14 2023 InstallationDate: Installed on 2023-08-23 (21 days ago) InstallationMedia: Ubuntu-Studio 22.04.3 LTS "Jammy Jellyfish" - Release amd64 (20230807) MachineType: Alienware Alienware 18 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.2.0-1009-lowlatency root=UUID=17502284-0952-44fe-81f8-54cebffc3800 ro threadirqs quiet splash vt.handoff=1 SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/22/2019 dmi.bios.vendor: Alienware dmi.bios.version: A15 dmi.board.name: 0FT9KT dmi.board.vendor: Alienware dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Alienware dmi.chassis.version: A15 dmi.ec.firmware.release: 1.1 dmi.modalias: dmi:bvnAlienware:bvrA15:bd07/22/2019:efr1.1:svnAlienware:pnAlienware18:pvrA15:rvnAlienware:rn0FT9KT:rvrA00:cvnAlienware:ct8:cvrA15:skuAlienware18: dmi.product.family: 00 dmi.product.name: Alienware 18 dmi.product.sku: Alienware 18 dmi.product.version: A15 dmi.sys.vendor: Alienware To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2035406/+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 2035406] Re: udev update has broken ubuntu's ability to import photos in digikam, gphoto2 can no longer see usb camera, entangle can no longer see camera
I downloaded your rules and used you commands to move it, I rebooted and
same issue, here is the result of gphoto2 --debug
gphoto2 --debug
0.000101 main(2): ALWAYS INCLUDE THE FOLLOWING LINES
WHEN SENDING DEBUG MESSAGES TO THE MAILING LIST:
0.000114 main(2): gphoto2 2.5.27
0.000127 main(2): gphoto2 has been compiled with the
following options:
0.000129 main(2): + gcc (C compiler used)
0.000131 main(2): + popt (mandatory, for handling
command-line parameters)
0.000132 main(2): + exif (for displaying EXIF
information)
0.000134 main(2): + cdk (for accessing configuration
options)
0.000137 main(2): + aa (for displaying live previews)
0.000140 main(2): + jpeg (for displaying live previews
in JPEG format)
0.000153 main(2): + readline (for easy navigation in
the shell)
0.000157 main(2): libgphoto2 2.5.31
0.000160 main(2): libgphoto2 has been compiled with the
following options:
0.000163 main(2): + standard camlib set SKIPPING SOME
(ax203 canon digigr8 dimagev directory jl2005a jl2005c kodak_dc240 mars pentax
ptp2 ricoh_g3 sierra sonix sq905 st2205 topfield tp6801 SKIPPING docupen lumix)
0.000166 main(2): + gcc (C compiler used)
0.000168 main(2): + no ltdl (for portable loading of
camlibs)
0.000171 main(2): + EXIF (for special handling of EXIF
files)
0.000175 main(2): libgphoto2_port 0.12.2
0.000177 main(2): libgphoto2_port has been compiled
with the following options:
0.000179 main(2): + iolibs: disk ptpip serial
0.000181 main(2): + gcc (C compiler used)
0.000183 main(2): + no ltdl (for portable loading of
iolibs)
0.000185 main(2): + EXIF (for vusb)
0.000187 main(2): + no USB (for USB cameras)
0.000188 main(2): + serial (for serial cameras)
0.000190 main(2): + no resmgr (serial port access and
locking)
0.000192 main(2): + no ttylock (serial port locking)
0.000195 main(2): + no lockdev (serial port locking)
0.000197 main(2): CAMLIBS env var not set, using
compile-time default instead
0.000199 main(2): IOLIBS env var not set, using
compile-time default instead
0.000201 main(2): invoked with following arguments:
0.000203 main(2): --debug
0.000212 load_settings (2): Creating gphoto config directory
('/home/pasjrwoctx/.gphoto')
0.000248 load_settings (2): Loading settings from file
'/home/pasjrwoctx/.gphoto/settings'.
0.000309 gp_camera_free (2): Freeing camera...
0.000312 gp_port_free(2): Freeing port...
0.000325 gp_filesystem_reset (2): resetting filesystem
0.000327 gp_filesystem_lru_clear (2): Clearing fscache LRU list...
0.000329 gp_filesystem_lru_clear (2): fscache LRU list already empty
0.000331 delete_all_folders (2): Internally deleting all folders from
'/'...
0.000333 lookup_folder (2): Lookup folder '/'...
0.000336 lookup_folder (2): Found! / is 0x55cbf0b9e8e0
0.000337 recurse_delete_folder (2): Recurse delete folder 0x55cbf0b9e8e0//
0.000340 delete_all_files(2): Delete all files in folder
0x55cbf0b9e8e0//
Maybe this help?
--
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/2035406
Title:
udev update has broken ubuntu's ability to import photos in digikam,
gphoto2 can no longer see usb camera, entangle can no longer see
camera
Status in systemd package in Ubuntu:
Invalid
Status in systemd source package in Jammy:
Incomplete
Status in systemd source package in Lunar:
Invalid
Status in systemd source package in Mantic:
Invalid
Bug description:
udev update has broken ubuntu's ability to import photos in digikam, gphoto2
can no longer see usb camera, entangle can no longer see camera
after Upgrade: udev:amd64 (249.11-0ubuntu3.9, 249.11-0ubuntu3.10),
systemd-timesyncd:amd64 (249.11-0ubuntu3.9, 249.11-0ubuntu3.10),
libpam-systemd:amd64 (249.11-0ubuntu3.9, 249.11-0ubuntu3.10),
libpam-systemd:i386 (249.11-0ubuntu3.9, 249.11-0ubuntu3.10), libsystemd0:amd64
(249.11-0ubuntu3.9, 249.11-0ubuntu3.10), libsystemd0:i386 (249.11-0ubuntu3.9,
249.11-0ubuntu3.10), libnss-systemd:amd64 (249.11-0ubuntu3.9,
249.11-0ubuntu3.10), libude
[Touch-packages] [Bug 2035406] Re: udev update has broken ubuntu's ability to import photos in digikam, gphoto2 can no longer see usb camera, entangle can no longer see camera
nu/libglib-2.0.so.0 #28 0x7f50d0176258 in () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #29 0x7f50d011e3e3 in g_main_context_iteration () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #30 0x7f50ded130b8 in QEventDispatcherGlib::processEvents(QFlags) () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #31 0x7f50decb875b in QEventLoop::exec(QFlags) () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #32 0x7f50decc0cf4 in QCoreApplication::exec() () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #33 0x55b27f2cc9b4 in () #34 0x7f50de229d90 in __libc_start_call_main (main=main@entry=0x55b27f2cb850, argc=argc@entry=1, argv=argv@entry=0x7ffc8df6e5a8) at ../sysdeps/nptl/libc_start_call_main.h:58 #35 0x7f50de229e40 in __libc_start_main_impl (main=0x55b27f2cb850, argc=1, argv=0x7ffc8df6e5a8, init=, fini=, rtld_fini=, stack_end=0x7ffc8df6e598) at ../csu/libc-start.c:392 #36 0x55b27f2cd775 in () [Inferior 1 (process 282496) detached] -- 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/2035406 Title: udev update has broken ubuntu's ability to import photos in digikam, gphoto2 can no longer see usb camera, entangle can no longer see camera Status in systemd package in Ubuntu: Invalid Status in systemd source package in Jammy: Incomplete Status in systemd source package in Lunar: Invalid Status in systemd source package in Mantic: Invalid Bug description: udev update has broken ubuntu's ability to import photos in digikam, gphoto2 can no longer see usb camera, entangle can no longer see camera after Upgrade: udev:amd64 (249.11-0ubuntu3.9, 249.11-0ubuntu3.10), systemd-timesyncd:amd64 (249.11-0ubuntu3.9, 249.11-0ubuntu3.10), libpam-systemd:amd64 (249.11-0ubuntu3.9, 249.11-0ubuntu3.10), libpam-systemd:i386 (249.11-0ubuntu3.9, 249.11-0ubuntu3.10), libsystemd0:amd64 (249.11-0ubuntu3.9, 249.11-0ubuntu3.10), libsystemd0:i386 (249.11-0ubuntu3.9, 249.11-0ubuntu3.10), libnss-systemd:amd64 (249.11-0ubuntu3.9, 249.11-0ubuntu3.10), libudev-dev:amd64 (249.11-0ubuntu3.9, 249.11-0ubuntu3.10), systemd:amd64 (249.11-0ubuntu3.9, 249.11-0ubuntu3.10), libudev1:amd64 (249.11-0ubuntu3.9, 249.11-0ubuntu3.10), libudev1:i386 (249.11-0ubuntu3.9, 249.11-0ubuntu3.10), systemd-sysv:amd64 (249.11-0ubuntu3.9, 249.11-0ubuntu3.10) ubuntu no longer allows gphoto2 or entangle control of my dslr, lsusb sees the camera fine, but the upgrade broke the usage, and cant roll back shows it will break system to roll back please fix ASAP. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: udev 249.11-0ubuntu3.10 ProcVersionSignature: Ubuntu 6.2.0-1009.9~22.04.1-lowlatency 6.2.13 Uname: Linux 6.2.0-1009-lowlatency x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Wed Sep 13 18:16:14 2023 InstallationDate: Installed on 2023-08-23 (21 days ago) InstallationMedia: Ubuntu-Studio 22.04.3 LTS "Jammy Jellyfish" - Release amd64 (20230807) MachineType: Alienware Alienware 18 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.2.0-1009-lowlatency root=UUID=17502284-0952-44fe-81f8-54cebffc3800 ro threadirqs quiet splash vt.handoff=1 SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/22/2019 dmi.bios.vendor: Alienware dmi.bios.version: A15 dmi.board.name: 0FT9KT dmi.board.vendor: Alienware dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Alienware dmi.chassis.version: A15 dmi.ec.firmware.release: 1.1 dmi.modalias: dmi:bvnAlienware:bvrA15:bd07/22/2019:efr1.1:svnAlienware:pnAlienware18:pvrA15:rvnAlienware:rn0FT9KT:rvrA00:cvnAlienware:ct8:cvrA15:skuAlienware18: dmi.product.family: 00 dmi.product.name: Alienware 18 dmi.product.sku: Alienware 18 dmi.product.version: A15 dmi.sys.vendor: Alienware To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2035406/+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 2035406] Re: udev update has broken ubuntu's ability to import photos in digikam, gphoto2 can no longer see usb camera, entangle can no longer see camera
YES this bug persists after (a) sudo systemctl daemon-reexec, and/or (b) reboot -- 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/2035406 Title: udev update has broken ubuntu's ability to import photos in digikam, gphoto2 can no longer see usb camera, entangle can no longer see camera Status in systemd package in Ubuntu: Invalid Status in systemd source package in Jammy: Incomplete Status in systemd source package in Lunar: Invalid Status in systemd source package in Mantic: Invalid Bug description: udev update has broken ubuntu's ability to import photos in digikam, gphoto2 can no longer see usb camera, entangle can no longer see camera after Upgrade: udev:amd64 (249.11-0ubuntu3.9, 249.11-0ubuntu3.10), systemd-timesyncd:amd64 (249.11-0ubuntu3.9, 249.11-0ubuntu3.10), libpam-systemd:amd64 (249.11-0ubuntu3.9, 249.11-0ubuntu3.10), libpam-systemd:i386 (249.11-0ubuntu3.9, 249.11-0ubuntu3.10), libsystemd0:amd64 (249.11-0ubuntu3.9, 249.11-0ubuntu3.10), libsystemd0:i386 (249.11-0ubuntu3.9, 249.11-0ubuntu3.10), libnss-systemd:amd64 (249.11-0ubuntu3.9, 249.11-0ubuntu3.10), libudev-dev:amd64 (249.11-0ubuntu3.9, 249.11-0ubuntu3.10), systemd:amd64 (249.11-0ubuntu3.9, 249.11-0ubuntu3.10), libudev1:amd64 (249.11-0ubuntu3.9, 249.11-0ubuntu3.10), libudev1:i386 (249.11-0ubuntu3.9, 249.11-0ubuntu3.10), systemd-sysv:amd64 (249.11-0ubuntu3.9, 249.11-0ubuntu3.10) ubuntu no longer allows gphoto2 or entangle control of my dslr, lsusb sees the camera fine, but the upgrade broke the usage, and cant roll back shows it will break system to roll back please fix ASAP. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: udev 249.11-0ubuntu3.10 ProcVersionSignature: Ubuntu 6.2.0-1009.9~22.04.1-lowlatency 6.2.13 Uname: Linux 6.2.0-1009-lowlatency x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Wed Sep 13 18:16:14 2023 InstallationDate: Installed on 2023-08-23 (21 days ago) InstallationMedia: Ubuntu-Studio 22.04.3 LTS "Jammy Jellyfish" - Release amd64 (20230807) MachineType: Alienware Alienware 18 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.2.0-1009-lowlatency root=UUID=17502284-0952-44fe-81f8-54cebffc3800 ro threadirqs quiet splash vt.handoff=1 SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/22/2019 dmi.bios.vendor: Alienware dmi.bios.version: A15 dmi.board.name: 0FT9KT dmi.board.vendor: Alienware dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Alienware dmi.chassis.version: A15 dmi.ec.firmware.release: 1.1 dmi.modalias: dmi:bvnAlienware:bvrA15:bd07/22/2019:efr1.1:svnAlienware:pnAlienware18:pvrA15:rvnAlienware:rn0FT9KT:rvrA00:cvnAlienware:ct8:cvrA15:skuAlienware18: dmi.product.family: 00 dmi.product.name: Alienware 18 dmi.product.sku: Alienware 18 dmi.product.version: A15 dmi.sys.vendor: Alienware To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2035406/+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 2035406] Re: udev update has broken ubuntu's ability to import photos in digikam, gphoto2 can no longer see usb camera, entangle can no longer see camera
Rebooting does nothing, same issue. systemctl daemon-reexec does nothing, same issue no one can talk to my camera, I tried a different camera same issue, lsusb cameras show up just fine so usb's are working, but something happens with that update that caused a roadblock between usb and other software packages. -- 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/2035406 Title: udev update has broken ubuntu's ability to import photos in digikam, gphoto2 can no longer see usb camera, entangle can no longer see camera Status in systemd package in Ubuntu: Invalid Status in systemd source package in Jammy: Incomplete Status in systemd source package in Lunar: Invalid Status in systemd source package in Mantic: Invalid Bug description: udev update has broken ubuntu's ability to import photos in digikam, gphoto2 can no longer see usb camera, entangle can no longer see camera after Upgrade: udev:amd64 (249.11-0ubuntu3.9, 249.11-0ubuntu3.10), systemd-timesyncd:amd64 (249.11-0ubuntu3.9, 249.11-0ubuntu3.10), libpam-systemd:amd64 (249.11-0ubuntu3.9, 249.11-0ubuntu3.10), libpam-systemd:i386 (249.11-0ubuntu3.9, 249.11-0ubuntu3.10), libsystemd0:amd64 (249.11-0ubuntu3.9, 249.11-0ubuntu3.10), libsystemd0:i386 (249.11-0ubuntu3.9, 249.11-0ubuntu3.10), libnss-systemd:amd64 (249.11-0ubuntu3.9, 249.11-0ubuntu3.10), libudev-dev:amd64 (249.11-0ubuntu3.9, 249.11-0ubuntu3.10), systemd:amd64 (249.11-0ubuntu3.9, 249.11-0ubuntu3.10), libudev1:amd64 (249.11-0ubuntu3.9, 249.11-0ubuntu3.10), libudev1:i386 (249.11-0ubuntu3.9, 249.11-0ubuntu3.10), systemd-sysv:amd64 (249.11-0ubuntu3.9, 249.11-0ubuntu3.10) ubuntu no longer allows gphoto2 or entangle control of my dslr, lsusb sees the camera fine, but the upgrade broke the usage, and cant roll back shows it will break system to roll back please fix ASAP. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: udev 249.11-0ubuntu3.10 ProcVersionSignature: Ubuntu 6.2.0-1009.9~22.04.1-lowlatency 6.2.13 Uname: Linux 6.2.0-1009-lowlatency x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Wed Sep 13 18:16:14 2023 InstallationDate: Installed on 2023-08-23 (21 days ago) InstallationMedia: Ubuntu-Studio 22.04.3 LTS "Jammy Jellyfish" - Release amd64 (20230807) MachineType: Alienware Alienware 18 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.2.0-1009-lowlatency root=UUID=17502284-0952-44fe-81f8-54cebffc3800 ro threadirqs quiet splash vt.handoff=1 SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/22/2019 dmi.bios.vendor: Alienware dmi.bios.version: A15 dmi.board.name: 0FT9KT dmi.board.vendor: Alienware dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Alienware dmi.chassis.version: A15 dmi.ec.firmware.release: 1.1 dmi.modalias: dmi:bvnAlienware:bvrA15:bd07/22/2019:efr1.1:svnAlienware:pnAlienware18:pvrA15:rvnAlienware:rn0FT9KT:rvrA00:cvnAlienware:ct8:cvrA15:skuAlienware18: dmi.product.family: 00 dmi.product.name: Alienware 18 dmi.product.sku: Alienware 18 dmi.product.version: A15 dmi.sys.vendor: Alienware To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2035406/+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 2035406] Re: udev update has broken ubuntu's ability to import photos in digikam, gphoto2 can no longer see usb camera, entangle can no longer see camera
everything was working before the updating and then I updated " udev:amd64 (249.11-0ubuntu3.9, 249.11-0ubuntu3.10), systemd- timesyncd:amd64 (249.11-0ubuntu3.9, 249.11-0ubuntu3.10), libpam- systemd:amd64 (249.11-0ubuntu3.9, 249.11-0ubuntu3.10), libpam- systemd:i386 (249.11-0ubuntu3.9, 249.11-0ubuntu3.10), libsystemd0:amd64 (249.11-0ubuntu3.9, 249.11-0ubuntu3.10), libsystemd0:i386 (249.11-0ubuntu3.9, 249.11-0ubuntu3.10), libnss-systemd:amd64 (249.11-0ubuntu3.9, 249.11-0ubuntu3.10), libudev-dev:amd64 (249.11-0ubuntu3.9, 249.11-0ubuntu3.10), systemd:amd64 (249.11-0ubuntu3.9, 249.11-0ubuntu3.10), libudev1:amd64 (249.11-0ubuntu3.9, 249.11-0ubuntu3.10), libudev1:i386 (249.11-0ubuntu3.9, 249.11-0ubuntu3.10), systemd-sysv:amd64 (249.11-0ubuntu3.9, 249.11-0ubuntu3.10) " and all of a sudden digikam could no longer talk to my camera, gphoto2 could no longer talk to my camera, entangle could no longer talk to my camera, again it all was working right before the update, I took a nap came back had an update, and did the update, went to live stream and gphoto2 could detect my camera, I took a picture with the camera manually, tried to import with digikam, digikam failed to connect, tried to use camera with entangle, which reported no camera attached, lsusb saw my camera clearly lsusb Bus 003 Device 006: ID 04b0:043f Nikon Corp. D5600 the only thing that changed was the above update/upgrade and now I am unable to do what I normally do, and well this bug stinks. -- 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/2035406 Title: udev update has broken ubuntu's ability to import photos in digikam, gphoto2 can no longer see usb camera, entangle can no longer see camera Status in systemd package in Ubuntu: Invalid Status in systemd source package in Jammy: Confirmed Status in systemd source package in Lunar: Invalid Status in systemd source package in Mantic: Invalid Bug description: udev update has broken ubuntu's ability to import photos in digikam, gphoto2 can no longer see usb camera, entangle can no longer see camera after Upgrade: udev:amd64 (249.11-0ubuntu3.9, 249.11-0ubuntu3.10), systemd-timesyncd:amd64 (249.11-0ubuntu3.9, 249.11-0ubuntu3.10), libpam-systemd:amd64 (249.11-0ubuntu3.9, 249.11-0ubuntu3.10), libpam-systemd:i386 (249.11-0ubuntu3.9, 249.11-0ubuntu3.10), libsystemd0:amd64 (249.11-0ubuntu3.9, 249.11-0ubuntu3.10), libsystemd0:i386 (249.11-0ubuntu3.9, 249.11-0ubuntu3.10), libnss-systemd:amd64 (249.11-0ubuntu3.9, 249.11-0ubuntu3.10), libudev-dev:amd64 (249.11-0ubuntu3.9, 249.11-0ubuntu3.10), systemd:amd64 (249.11-0ubuntu3.9, 249.11-0ubuntu3.10), libudev1:amd64 (249.11-0ubuntu3.9, 249.11-0ubuntu3.10), libudev1:i386 (249.11-0ubuntu3.9, 249.11-0ubuntu3.10), systemd-sysv:amd64 (249.11-0ubuntu3.9, 249.11-0ubuntu3.10) ubuntu no longer allows gphoto2 or entangle control of my dslr, lsusb sees the camera fine, but the upgrade broke the usage, and cant roll back shows it will break system to roll back please fix ASAP. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: udev 249.11-0ubuntu3.10 ProcVersionSignature: Ubuntu 6.2.0-1009.9~22.04.1-lowlatency 6.2.13 Uname: Linux 6.2.0-1009-lowlatency x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Wed Sep 13 18:16:14 2023 InstallationDate: Installed on 2023-08-23 (21 days ago) InstallationMedia: Ubuntu-Studio 22.04.3 LTS "Jammy Jellyfish" - Release amd64 (20230807) MachineType: Alienware Alienware 18 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.2.0-1009-lowlatency root=UUID=17502284-0952-44fe-81f8-54cebffc3800 ro threadirqs quiet splash vt.handoff=1 SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/22/2019 dmi.bios.vendor: Alienware dmi.bios.version: A15 dmi.board.name: 0FT9KT dmi.board.vendor: Alienware dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Alienware dmi.chassis.version: A15 dmi.ec.firmware.release: 1.1 dmi.modalias: dmi:bvnAlienware:bvrA15:bd07/22/2019:efr1.1:svnAlienware:pnAlienware18:pvrA15:rvnAlienware:rn0FT9KT:rvrA00:cvnAlienware:ct8:cvrA15:skuAlienware18: dmi.product.family: 00 dmi.product.name: Alienware 18 dmi.product.sku: Alienware 18 dmi.product.version: A15 dmi.sys.vendor: Alienware To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2035406/+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 2035406] Re: udev update has broken ubuntu's ability to import photos in digikam, gphoto2 can no longer see usb camera, entangle can no longer see camera
No I am using it for both still photography and for video streaming. -- 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/2035406 Title: udev update has broken ubuntu's ability to import photos in digikam, gphoto2 can no longer see usb camera, entangle can no longer see camera Status in systemd package in Ubuntu: Invalid Status in systemd source package in Jammy: Confirmed Status in systemd source package in Lunar: Invalid Status in systemd source package in Mantic: Invalid Bug description: udev update has broken ubuntu's ability to import photos in digikam, gphoto2 can no longer see usb camera, entangle can no longer see camera after Upgrade: udev:amd64 (249.11-0ubuntu3.9, 249.11-0ubuntu3.10), systemd-timesyncd:amd64 (249.11-0ubuntu3.9, 249.11-0ubuntu3.10), libpam-systemd:amd64 (249.11-0ubuntu3.9, 249.11-0ubuntu3.10), libpam-systemd:i386 (249.11-0ubuntu3.9, 249.11-0ubuntu3.10), libsystemd0:amd64 (249.11-0ubuntu3.9, 249.11-0ubuntu3.10), libsystemd0:i386 (249.11-0ubuntu3.9, 249.11-0ubuntu3.10), libnss-systemd:amd64 (249.11-0ubuntu3.9, 249.11-0ubuntu3.10), libudev-dev:amd64 (249.11-0ubuntu3.9, 249.11-0ubuntu3.10), systemd:amd64 (249.11-0ubuntu3.9, 249.11-0ubuntu3.10), libudev1:amd64 (249.11-0ubuntu3.9, 249.11-0ubuntu3.10), libudev1:i386 (249.11-0ubuntu3.9, 249.11-0ubuntu3.10), systemd-sysv:amd64 (249.11-0ubuntu3.9, 249.11-0ubuntu3.10) ubuntu no longer allows gphoto2 or entangle control of my dslr, lsusb sees the camera fine, but the upgrade broke the usage, and cant roll back shows it will break system to roll back please fix ASAP. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: udev 249.11-0ubuntu3.10 ProcVersionSignature: Ubuntu 6.2.0-1009.9~22.04.1-lowlatency 6.2.13 Uname: Linux 6.2.0-1009-lowlatency x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Wed Sep 13 18:16:14 2023 InstallationDate: Installed on 2023-08-23 (21 days ago) InstallationMedia: Ubuntu-Studio 22.04.3 LTS "Jammy Jellyfish" - Release amd64 (20230807) MachineType: Alienware Alienware 18 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.2.0-1009-lowlatency root=UUID=17502284-0952-44fe-81f8-54cebffc3800 ro threadirqs quiet splash vt.handoff=1 SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/22/2019 dmi.bios.vendor: Alienware dmi.bios.version: A15 dmi.board.name: 0FT9KT dmi.board.vendor: Alienware dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Alienware dmi.chassis.version: A15 dmi.ec.firmware.release: 1.1 dmi.modalias: dmi:bvnAlienware:bvrA15:bd07/22/2019:efr1.1:svnAlienware:pnAlienware18:pvrA15:rvnAlienware:rn0FT9KT:rvrA00:cvnAlienware:ct8:cvrA15:skuAlienware18: dmi.product.family: 00 dmi.product.name: Alienware 18 dmi.product.sku: Alienware 18 dmi.product.version: A15 dmi.sys.vendor: Alienware To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2035406/+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 2035406] Re: udev update has broken ubuntu's ability to import photos in digikam, gphoto2 can no longer see usb camera, entangle can no longer see camera
Here is my output of ls -l /dev/video* ls -l /dev/video* crw-rw+ 1 root video 81, 0 Sep 13 18:45 /dev/video0 crw-rw+ 1 root video 81, 1 Sep 13 18:45 /dev/video1 crw-rw+ 1 root video 81, 2 Sep 13 18:45 /dev/video2 -- 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/2035406 Title: udev update has broken ubuntu's ability to import photos in digikam, gphoto2 can no longer see usb camera, entangle can no longer see camera Status in systemd package in Ubuntu: Invalid Status in systemd source package in Jammy: Confirmed Status in systemd source package in Lunar: Invalid Status in systemd source package in Mantic: Invalid Bug description: udev update has broken ubuntu's ability to import photos in digikam, gphoto2 can no longer see usb camera, entangle can no longer see camera after Upgrade: udev:amd64 (249.11-0ubuntu3.9, 249.11-0ubuntu3.10), systemd-timesyncd:amd64 (249.11-0ubuntu3.9, 249.11-0ubuntu3.10), libpam-systemd:amd64 (249.11-0ubuntu3.9, 249.11-0ubuntu3.10), libpam-systemd:i386 (249.11-0ubuntu3.9, 249.11-0ubuntu3.10), libsystemd0:amd64 (249.11-0ubuntu3.9, 249.11-0ubuntu3.10), libsystemd0:i386 (249.11-0ubuntu3.9, 249.11-0ubuntu3.10), libnss-systemd:amd64 (249.11-0ubuntu3.9, 249.11-0ubuntu3.10), libudev-dev:amd64 (249.11-0ubuntu3.9, 249.11-0ubuntu3.10), systemd:amd64 (249.11-0ubuntu3.9, 249.11-0ubuntu3.10), libudev1:amd64 (249.11-0ubuntu3.9, 249.11-0ubuntu3.10), libudev1:i386 (249.11-0ubuntu3.9, 249.11-0ubuntu3.10), systemd-sysv:amd64 (249.11-0ubuntu3.9, 249.11-0ubuntu3.10) ubuntu no longer allows gphoto2 or entangle control of my dslr, lsusb sees the camera fine, but the upgrade broke the usage, and cant roll back shows it will break system to roll back please fix ASAP. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: udev 249.11-0ubuntu3.10 ProcVersionSignature: Ubuntu 6.2.0-1009.9~22.04.1-lowlatency 6.2.13 Uname: Linux 6.2.0-1009-lowlatency x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Wed Sep 13 18:16:14 2023 InstallationDate: Installed on 2023-08-23 (21 days ago) InstallationMedia: Ubuntu-Studio 22.04.3 LTS "Jammy Jellyfish" - Release amd64 (20230807) MachineType: Alienware Alienware 18 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.2.0-1009-lowlatency root=UUID=17502284-0952-44fe-81f8-54cebffc3800 ro threadirqs quiet splash vt.handoff=1 SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/22/2019 dmi.bios.vendor: Alienware dmi.bios.version: A15 dmi.board.name: 0FT9KT dmi.board.vendor: Alienware dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Alienware dmi.chassis.version: A15 dmi.ec.firmware.release: 1.1 dmi.modalias: dmi:bvnAlienware:bvrA15:bd07/22/2019:efr1.1:svnAlienware:pnAlienware18:pvrA15:rvnAlienware:rn0FT9KT:rvrA00:cvnAlienware:ct8:cvrA15:skuAlienware18: dmi.product.family: 00 dmi.product.name: Alienware 18 dmi.product.sku: Alienware 18 dmi.product.version: A15 dmi.sys.vendor: Alienware To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2035406/+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 2035406] [NEW] udev update has broken ubuntu's ability to import photos in digikam, gphoto2 can no longer see usb camera, entangle can no longer see camera
Public bug reported: udev update has broken ubuntu's ability to import photos in digikam, gphoto2 can no longer see usb camera, entangle can no longer see camera after Upgrade: udev:amd64 (249.11-0ubuntu3.9, 249.11-0ubuntu3.10), systemd-timesyncd:amd64 (249.11-0ubuntu3.9, 249.11-0ubuntu3.10), libpam-systemd:amd64 (249.11-0ubuntu3.9, 249.11-0ubuntu3.10), libpam-systemd:i386 (249.11-0ubuntu3.9, 249.11-0ubuntu3.10), libsystemd0:amd64 (249.11-0ubuntu3.9, 249.11-0ubuntu3.10), libsystemd0:i386 (249.11-0ubuntu3.9, 249.11-0ubuntu3.10), libnss-systemd:amd64 (249.11-0ubuntu3.9, 249.11-0ubuntu3.10), libudev-dev:amd64 (249.11-0ubuntu3.9, 249.11-0ubuntu3.10), systemd:amd64 (249.11-0ubuntu3.9, 249.11-0ubuntu3.10), libudev1:amd64 (249.11-0ubuntu3.9, 249.11-0ubuntu3.10), libudev1:i386 (249.11-0ubuntu3.9, 249.11-0ubuntu3.10), systemd-sysv:amd64 (249.11-0ubuntu3.9, 249.11-0ubuntu3.10) ubuntu no longer allows gphoto2 or entangle control of my dslr, lsusb sees the camera fine, but the upgrade broke the usage, and cant roll back shows it will break system to roll back please fix ASAP. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: udev 249.11-0ubuntu3.10 ProcVersionSignature: Ubuntu 6.2.0-1009.9~22.04.1-lowlatency 6.2.13 Uname: Linux 6.2.0-1009-lowlatency x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Wed Sep 13 18:16:14 2023 InstallationDate: Installed on 2023-08-23 (21 days ago) InstallationMedia: Ubuntu-Studio 22.04.3 LTS "Jammy Jellyfish" - Release amd64 (20230807) MachineType: Alienware Alienware 18 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.2.0-1009-lowlatency root=UUID=17502284-0952-44fe-81f8-54cebffc3800 ro threadirqs quiet splash vt.handoff=1 SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/22/2019 dmi.bios.vendor: Alienware dmi.bios.version: A15 dmi.board.name: 0FT9KT dmi.board.vendor: Alienware dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Alienware dmi.chassis.version: A15 dmi.ec.firmware.release: 1.1 dmi.modalias: dmi:bvnAlienware:bvrA15:bd07/22/2019:efr1.1:svnAlienware:pnAlienware18:pvrA15:rvnAlienware:rn0FT9KT:rvrA00:cvnAlienware:ct8:cvrA15:skuAlienware18: dmi.product.family: 00 dmi.product.name: Alienware 18 dmi.product.sku: Alienware 18 dmi.product.version: A15 dmi.sys.vendor: Alienware ** Affects: systemd (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 systemd in Ubuntu. https://bugs.launchpad.net/bugs/2035406 Title: udev update has broken ubuntu's ability to import photos in digikam, gphoto2 can no longer see usb camera, entangle can no longer see camera Status in systemd package in Ubuntu: New Bug description: udev update has broken ubuntu's ability to import photos in digikam, gphoto2 can no longer see usb camera, entangle can no longer see camera after Upgrade: udev:amd64 (249.11-0ubuntu3.9, 249.11-0ubuntu3.10), systemd-timesyncd:amd64 (249.11-0ubuntu3.9, 249.11-0ubuntu3.10), libpam-systemd:amd64 (249.11-0ubuntu3.9, 249.11-0ubuntu3.10), libpam-systemd:i386 (249.11-0ubuntu3.9, 249.11-0ubuntu3.10), libsystemd0:amd64 (249.11-0ubuntu3.9, 249.11-0ubuntu3.10), libsystemd0:i386 (249.11-0ubuntu3.9, 249.11-0ubuntu3.10), libnss-systemd:amd64 (249.11-0ubuntu3.9, 249.11-0ubuntu3.10), libudev-dev:amd64 (249.11-0ubuntu3.9, 249.11-0ubuntu3.10), systemd:amd64 (249.11-0ubuntu3.9, 249.11-0ubuntu3.10), libudev1:amd64 (249.11-0ubuntu3.9, 249.11-0ubuntu3.10), libudev1:i386 (249.11-0ubuntu3.9, 249.11-0ubuntu3.10), systemd-sysv:amd64 (249.11-0ubuntu3.9, 249.11-0ubuntu3.10) ubuntu no longer allows gphoto2 or entangle control of my dslr, lsusb sees the camera fine, but the upgrade broke the usage, and cant roll back shows it will break system to roll back please fix ASAP. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: udev 249.11-0ubuntu3.10 ProcVersionSignature: Ubuntu 6.2.0-1009.9~22.04.1-lowlatency 6.2.13 Uname: Linux 6.2.0-1009-lowlatency x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Wed Sep 13 18:16:14 2023 InstallationDate: Installed on 2023-08-23 (21 days ago) InstallationMedia: Ubuntu-Studio 22.04.3 LTS "Jammy Jellyfish" - Release amd64 (20230807) MachineType: Alienware Alienware 18 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.2.0-1009-lowlatency root=UUID=17502284-0952-44fe-81f8-54cebffc3800 ro threadirqs quiet splash vt.handoff=1 SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/22/2019 dmi.bios.vendor: Alienware dmi.bios.version: A15 dmi.board.name: 0FT9KT dmi.board.vendor: Alienware dmi.board
[Touch-packages] [Bug 2017614] [NEW] Xwayland
Public bug reported: I am using the NetBeans 12.5 IDE (Java 11) for study reasons, I am having a bug with the OS I recently upgraded from Ubuntu 22.10 to Ubuntu 23.04, every time I run a project and for example: I have a button configured to show and hide a form when i press the button the OS freezes and logs me out, this never happened to me on ubuntu 22.10 ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 Uname: Linux 6.2.0-20-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 BootLog: Error: [Errno 13] Permiso denegado: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Apr 24 20:36:04 2023 DistUpgraded: Fresh install DistroCodename: lunar DistroVariant: ubuntu DkmsStatus: v4l2loopback/0.12.7, 5.19.0-40-generic, x86_64: installed (WARNING! Diff between built and installed module!) v4l2loopback/0.12.7, 6.2.0-20-generic, x86_64: installed (WARNING! Diff between built and installed module!) GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0102] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company 2nd Generation Core Processor Family Integrated Graphics Controller [103c:2ae2] InstallationDate: Installed on 2021-07-08 (656 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) MachineType: Hewlett-Packard CQ2951LA ProcEnviron: LANG=es_CR.UTF-8 LANGUAGE=es_CR:es PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-20-generic root=UUID=375418d9-5c30-48db-b088-b27ed63e58dd ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg crash UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/31/2012 dmi.bios.release: 4.6 dmi.bios.vendor: AMI dmi.bios.version: 8.08 dmi.board.asset.tag: 3CR2390SBN dmi.board.name: 2AE2 dmi.board.vendor: PEGATRON CORPORATION dmi.board.version: 1.02 dmi.chassis.asset.tag: 3CR2390SBN dmi.chassis.type: 3 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnAMI:bvr8.08:bd08/31/2012:br4.6:svnHewlett-Packard:pnCQ2951LA:pvr1.00:rvnPEGATRONCORPORATION:rn2AE2:rvr1.02:cvnHewlett-Packard:ct3:cvr:skuH3X53AA#ABM: dmi.product.family: 103C_53316J G=D dmi.product.name: CQ2951LA dmi.product.sku: H3X53AA#ABM dmi.product.version: 1.00 dmi.sys.vendor: Hewlett-Packard version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.114-1 version.libgl1-mesa-dri: libgl1-mesa-dri 23.0.2-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 23.0.2-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-1ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3 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 crash lunar 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/2017614 Title: Xwayland Status in xorg package in Ubuntu: New Bug description: I am using the NetBeans 12.5 IDE (Java 11) for study reasons, I am having a bug with the OS I recently upgraded from Ubuntu 22.10 to Ubuntu 23.04, every time I run a project and for example: I have a button configured to show and hide a form when i press the button the OS freezes and logs me out, this never happened to me on ubuntu 22.10 ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 Uname: Linux 6.2.0-20-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 BootLog: Error: [Errno 13] Permiso denegado: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Apr 24 20:36:04 2023 DistUpgraded: Fresh install DistroCodename: lunar DistroVariant: ubuntu DkmsStatus: v4l2loopback/0.12.7, 5.19.0-40-generic, x86_64: installed (WARNING! Diff between built and installed module!) v4l2loopback/0.12.7, 6.2.0-20-generic, x86_64: installed (WARNING! Diff between built and installed module!) GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0102] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company 2nd Generation Core Processor Family Integrated Graphics Controller [103c:2ae2] InstallationDate: Installed on 2021-07-08 (656 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) MachineType: Hewlett-Packard CQ2
[Touch-packages] [Bug 1632808] Re: Consider supporting IPv6 autoconf in configure_networking
Is there any status updates on this ? -- 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/1632808 Title: Consider supporting IPv6 autoconf in configure_networking Status in MAAS: Invalid Status in initramfs-tools package in Ubuntu: Triaged Bug description: Because DHCPv6 only does addresses, and not routes, configure_networking needs to wait for the kernel to process a router- advertisement before returning claiming an IPv6 config (since all it will have is a /128 and no routes, making for a pretty useless network stack.) See Bug #1609898 for context. (The syntax for ip= should probably also be extended to allow SLAAC configuration. If the user said "dhcp", then we should insist on getting our answer from DHCP.) On the bright side, iscsi retries, so after 1 or more failures to connect, the router-advertisement comes in and the connect succeeds. To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1632808/+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 2006073] Re: PAM: CVE-2022-28321 patch not correctly applied
Is Ubuntu/Linux really affected by that CVE? It really looks like it is specific to Suse. I tried to reproduce on ubuntu what was described in the original report at SUSE https://bugzilla.suse.com/show_bug.cgi?id=1197654: -:user1:ALL EXCEPT 127.0.0.1 and on ubuntu, it was the correct behaviour. Could not connect beside via 127.0.0.1. ** Bug watch added: bugzilla.suse.com/ #1197654 https://bugzilla.suse.com/show_bug.cgi?id=1197654 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pam in Ubuntu. https://bugs.launchpad.net/bugs/2006073 Title: PAM: CVE-2022-28321 patch not correctly applied Status in pam package in Ubuntu: Fix Released Bug description: In the latest update for PAM, the patch was added to "debian/patches" instead of "debian/patches-applied" where all other PAM patches reside. pam (1.3.1-5ubuntu4.4) focal-security; urgency=medium * SECURITY UPDATE: authentication bypass vulnerability - debian/patches/CVE-2022-28321.patch: pam_access: handle hostnames in access.conf - CVE-2022-28321 -- Nishit Majithia Tue, 24 Jan 2023 17:15:43 +0530 While building, it picks up all patches from debian/patches-applied but not debian/patches. The build passes but the CVE fix is not applied. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pam/+bug/2006073/+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 1993800]
(In reply to Aaron Puchert from comment #10) > (In reply to Fabian Vogt from comment #9) > > So the missing "instcombine" pass causes the "Cannot select" error and the > > pass is missing > > because Mesa passes an invalid list of passes to LLVMRunPasses and ignores > > the error. > > Would it be possible to improve error handling here? At least some tracing > would be nice. From your analysis it looks like this might affect more > platforms and not just armv7, and we wouldn't have noticed anything were it > not for the backend bug. Correct. The code is unfortunately not ready for handling errors (even logging isn't really possible FWICT), so all I could do is ask for some ideas on the MR. -- 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/1993800 Title: LLVM ERROR: Cannot select: 0x2f689c8: v4i32 = ARMISD::VCMPZ 0x2f696b8, Constant:i32<2> Status in LLVM: New Status in llvm-toolchain-15 package in Ubuntu: Confirmed Status in mesa package in Ubuntu: Confirmed Status in llvm-toolchain-15 package in openSUSE: Unknown Bug description: LLVM ERROR: Cannot select: 0x2f689c8: v4i32 = ARMISD::VCMPZ 0x2f696b8, Constant:i32<2> 0x2f696b8: v4i32,ch = ARMISD::VLD1DUP<(load (s32) from %ir.212)> 0x2aad434, 0x2f84090:1, Constant:i32<4> 0x2f84090: i32,i32,ch = load<(load (s32) from %ir.209, align 8), > 0x2aad434, 0x2f63a30, Constant:i32<64> 0x2f63a30: i32,ch = CopyFromReg 0x2aad434, Register:i32 %23 0x2f51c10: i32 = Register %23 0x2f82500: i32 = Constant<64> 0x2f81b28: i32 = Constant<4> 0x2f81e40: i32 = Constant<2> In function: fs_variant_partial [https://launchpadlibrarian.net/629171689/buildlog_ubuntu-kinetic- armhf.mutter_43.0-1ubuntu3_BUILDING.txt.gz] Although "LLVM ERROR: Cannot select" seems to be from LLVM, I can't determine what project "fs_variant_partial" is in. Sounds like it might be in some old version of Mesa? The start of the log suggests it's running on focal. To manage notifications about this bug go to: https://bugs.launchpad.net/llvm/+bug/1993800/+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 1960268] Re: SSL handshake failed - VPN SSL broken in 22.04
I have upgraded to Ubuntu 22.04 .1 LTS and have GlobalProtect 5.1.6-6. I followed @fru1z instructions and fixed the issue. Thanks! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssl in Ubuntu. https://bugs.launchpad.net/bugs/1960268 Title: SSL handshake failed - VPN SSL broken in 22.04 Status in openssl package in Ubuntu: Expired Bug description: I'm trying to connect with global protect VPN but fails at login with: SSL handshake failed Failed to load URL https://... QtNetwork Error 6 Another VPN client does work but the rdp connection to a remote server fails with: transport_connect_tls:freerdp_set_last_error_ex ERRCONNECT_TLS_CONNECT_FAILED --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu76 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE DistroRelease: Ubuntu 21.10 InstallationDate: Installed on 2021-03-19 (325 days ago) InstallationMedia: Kubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) Package: openssl 3.0.1-0ubuntu1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12 Tags: wayland-session impish Uname: Linux 5.15.0-18-generic x86_64 UpgradeStatus: Upgraded to impish on 2022-02-04 (3 days ago) UserGroups: adm cdrom dialout dip docker input lpadmin lxd plugdev sambashare sudo uinput _MarkForUpload: True --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu76 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2021-03-19 (325 days ago) InstallationMedia: Kubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) Package: openssl 3.0.1-0ubuntu1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12 Tags: wayland-session jammy Uname: Linux 5.15.0-18-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-02-04 (3 days ago) UserGroups: adm cdrom dialout dip docker input lpadmin lxd plugdev sambashare sudo uinput _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1960268/+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 1973441] Re: Printing does not work on Ubuntu 22.04 - cups-pki-invalid
Deleting the certificate also worked for me. To do this user needs admin privileges. I guess this breaks basic printing functionality for regular users. This is my printer: HP_Smart_Tank_530_series_21D133 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1973441 Title: Printing does not work on Ubuntu 22.04 - cups-pki-invalid Status in cups package in Ubuntu: Confirmed Bug description: After upgrading to 22.04 printing did not work. There is cups-pki- invalid error and printer goes to paused state. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: cups 2.4.1op1-1ubuntu4 Uname: Linux 5.17.7-051707-generic x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CupsErrorLog: Error: [Errno 13] Permission denied: '/var/log/cups/error_log' CurrentDesktop: ubuntu:GNOME Date: Sun May 15 15:34:47 2022 EcryptfsInUse: Yes InstallationDate: Installed on 2021-10-12 (214 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Daily amd64 (20211010) Lpstat: device for HP_Color_LaserJet_M552_5F80BF: implicitclass://HP_Color_LaserJet_M552_5F80BF/ MachineType: ASUSTeK COMPUTER INC. ROG Strix G513QY_G513QY Papersize: a4 PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/HP_Color_LaserJet_M552_5F80BF.ppd'] failed with exit code 2: grep: /etc/cups/ppd/HP_Color_LaserJet_M552_5F80BF.ppd: Permission denied ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.17.7-051707-generic root=UUID=ff964c9b-ce92-4334-8759-9d785a262c60 ro rootflags=subvol=@ quiet splash vt.handoff=7 SourcePackage: cups UpgradeStatus: Upgraded to jammy on 2022-04-24 (21 days ago) dmi.bios.date: 03/29/2022 dmi.bios.release: 5.19 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: G513QY.318 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: G513QY dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.ec.firmware.release: 0.81 dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrG513QY.318:bd03/29/2022:br5.19:efr0.81:svnASUSTeKCOMPUTERINC.:pnROGStrixG513QY_G513QY:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnG513QY:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:sku: dmi.product.family: ROG Strix dmi.product.name: ROG Strix G513QY_G513QY dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1973441/+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 1777070] Re: firefox plugin libwidevinecdm.so crashes due to apparmor denial
Solved it for me by editing /etc/apparmor.d/usr.bin.firefox on XSE
(Debian- & Xubutnu 18.04 LTS-based distro):
# per-user firefox configuration
#...
owner @{HOME}/.{firefox,mozilla}/**/gmp-widevinecdm/*/lib*so m,
That solved the problem when using Mz Firefox 100.0 (64-bit) and widevine
4.10.2449.0
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in Ubuntu.
https://bugs.launchpad.net/bugs/1777070
Title:
firefox plugin libwidevinecdm.so crashes due to apparmor denial
Status in apparmor package in Ubuntu:
Confirmed
Status in firefox package in Ubuntu:
Confirmed
Bug description:
Ubuntu 18.04, Firefox 60.0.1+build2-0ubuntu0.18.04.1
Running firefix, then going to netflix.com and attempting to play a
movie. The widevinecdm plugin crashes, the following is found in
syslog:
Jun 15 19:13:22 xplt kernel: [301351.553043] audit: type=1400
audit(1529046802.585:246): apparmor="DENIED" operation="file_mmap"
profile="/usr/lib/firefox/firefox{,*[^s][^h]}"
name="/home/xav/.mozilla/firefox/wiavokxk.default-1510977878171/gmp-widevinecdm/1.4.8.1008/libwidevinecdm.so"
pid=16118 comm="plugin-containe" requested_mask="m" denied_mask="m" fsuid=1000
ouid=1000
Jun 15 19:13:22 xplt kernel: [301351.553236] audit: type=1400
audit(1529046802.585:247): apparmor="DENIED" operation="ptrace"
profile="/usr/lib/firefox/firefox{,*[^s][^h]}" pid=24714 comm="firefox"
requested_mask="trace" denied_mask="trace"
peer="/usr/lib/firefox/firefox{,*[^s][^h]}"
Jun 15 19:13:22 xplt kernel: [301351.553259] plugin-containe[16118]: segfault
at 0 ip 7fcdfdaa76af sp 7ffc1ff03e28 error 6 in
libxul.so[7fcdfb77a000+6111000]
Jun 15 19:13:22 xplt snmpd[2334]: error on subcontainer 'ia_addr' insert (-1)
Jun 15 19:13:22 xplt /usr/lib/gdm3/gdm-x-session[6549]: ###!!!
[Parent][MessageChannel::Call] Error: Channel error: cannot send/recv
Jun 15 19:13:24 xplt kernel: [301353.960182] audit: type=1400
audit(1529046804.994:248): apparmor="DENIED" operation="file_mmap"
profile="/usr/lib/firefox/firefox{,*[^s][^h]}"
name="/home/xav/.mozilla/firefox/wiavokxk.default-1510977878171/gmp-widevinecdm/1.4.8.1008/libwidevinecdm.so"
pid=16135 comm="plugin-containe" requested_mask="m" denied_mask="m" fsuid=1000
ouid=1000
Jun 15 19:13:24 xplt kernel: [301353.960373] audit: type=1400
audit(1529046804.994:249): apparmor="DENIED" operation="ptrace"
profile="/usr/lib/firefox/firefox{,*[^s][^h]}" pid=24714 comm="firefox"
requested_mask="trace" denied_mask="trace"
peer="/usr/lib/firefox/firefox{,*[^s][^h]}"
Jun 15 19:13:24 xplt kernel: [301353.960398] plugin-containe[16135]: segfault
at 0 ip 7fe3b57f46af sp 7ffe6dc0b488 error 6 in
libxul.so[7fe3b34c7000+6111000]
Jun 15 19:13:28 xplt kernel: [301357.859177] audit: type=1400
audit(1529046808.895:250): apparmor="DENIED" operation="file_mmap"
profile="/usr/lib/firefox/firefox{,*[^s][^h]}"
name="/home/xav/.mozilla/firefox/wiavokxk.default-1510977878171/gmp-widevinecdm/1.4.8.1008/libwidevinecdm.so"
pid=16139 comm="plugin-containe" requested_mask="m" denied_mask="m" fsuid=1000
ouid=1000
Jun 15 19:13:28 xplt kernel: [301357.859328] audit: type=1400
audit(1529046808.895:251): apparmor="DENIED" operation="ptrace"
profile="/usr/lib/firefox/firefox{,*[^s][^h]}" pid=24714 comm="firefox"
requested_mask="trace" denied_mask="trace"
peer="/usr/lib/firefox/firefox{,*[^s][^h]}"
Jun 15 19:13:28 xplt kernel: [301357.859349] plugin-containe[16139]: segfault
at 0 ip 7fcf32ae06af sp 7ffeb8a136c8 error 6 in
libxul.so[7fcf307b3000+6111000]
Jun 15 19:13:25 xplt /usr/lib/gdm3/gdm-x-session[6549]: ###!!!
[Parent][MessageChannel::Call] Error: Channel error: cannot send/recv
Jun 15 19:13:29 xplt /usr/lib/gdm3/gdm-x-session[6549]: ERROR block_reap:328:
[hamster] bad exit code 1
Jun 15 19:13:29 xplt /usr/lib/gdm3/gdm-x-session[6549]: ###!!!
[Parent][MessageChannel::Call] Error: Channel error: cannot send/recv
Jun 15 19:13:29 xplt kernel: [301358.227635] audit: type=1400
audit(1529046809.263:252): apparmor="DENIED" operation="file_mmap"
profile="/usr/lib/firefox/firefox{,*[^s][^h]}"
name="/home/xav/.mozilla/firefox/wiavokxk.default-1510977878171/gmp-widevinecdm/1.4.8.1008/libwidevinecdm.so"
pid=16188 comm="plugin-containe" requested_mask="m" denied_mask="m" fsuid=1000
ouid=1000
Jun 15 19:13:29 xplt kernel: [301358.227811] audit: type=1400
audit(1529046809.263:253): appar
[Touch-packages] [Bug 1961327] [NEW] Audio drops when switiching applications
Public bug reported: The audio on my laptop drops when I open a new application (or switch to a different one). Sometimes it happens when switching tabs. It does not matter which application is playing audio, the audio usually stops when the application is switched. The typical workaround is to kill pulseaudio and start it again but that requires me to restart the application which is playing the audio. I found a better workaround which is to open PulseAudio Volume Control (pavucontrol) and toggle the profile from "Play HiFi quality music" -> "Off" -> "Play HiFi quality music". ➜ lsb_release -rd Description:Ubuntu 21.10 Release:21.10 ➜ apt-cache policy pulseaudio pulseaudio: Installed: 1:15.0+dfsg1-1ubuntu2.2 Candidate: 1:15.0+dfsg1-1ubuntu2.2 Version table: *** 1:15.0+dfsg1-1ubuntu2.2 500 500 http://ca.archive.ubuntu.com/ubuntu impish-updates/main amd64 Packages 100 /var/lib/dpkg/status 1:15.0+dfsg1-1ubuntu2 500 500 http://ca.archive.ubuntu.com/ubuntu impish/main amd64 Packages ** Affects: pulseaudio (Ubuntu) Importance: Undecided Status: New ** Description changed: The audio on my laptop drops when I open a new application (or switch to a different one). Sometimes it happens when switching tabs. It does not matter which application is playing audio, the audio usually stops when the application is switched. The typical workaround is to kill pulseaudio and start it again but that requires me to restart the application which is playing the audio. I found a better workaround which is to open PulseAudio Volume Control (pavucontrol) and toggle the profile from "Play HiFi quality music" -> "Off" -> "Play HiFi quality music". - - ``` + ` ➜ lsb_release -rd Description: Ubuntu 21.10 Release: 21.10 - ``` + ` - ``` + ` apt-cache policy pulseaudio pulseaudio: - Installed: 1:15.0+dfsg1-1ubuntu2.2 - Candidate: 1:15.0+dfsg1-1ubuntu2.2 - Version table: - *** 1:15.0+dfsg1-1ubuntu2.2 500 - 500 http://ca.archive.ubuntu.com/ubuntu impish-updates/main amd64 Packages - 100 /var/lib/dpkg/status - 1:15.0+dfsg1-1ubuntu2 500 - 500 http://ca.archive.ubuntu.com/ubuntu impish/main amd64 Packages - ``` + Installed: 1:15.0+dfsg1-1ubuntu2.2 + Candidate: 1:15.0+dfsg1-1ubuntu2.2 + Version table: + *** 1:15.0+dfsg1-1ubuntu2.2 500 + 500 http://ca.archive.ubuntu.com/ubuntu impish-updates/main amd64 Packages + 100 /var/lib/dpkg/status + 1:15.0+dfsg1-1ubuntu2 500 + 500 http://ca.archive.ubuntu.com/ubuntu impish/main amd64 Packages + ` ** Description changed: The audio on my laptop drops when I open a new application (or switch to a different one). Sometimes it happens when switching tabs. It does not matter which application is playing audio, the audio usually stops when the application is switched. The typical workaround is to kill pulseaudio and start it again but that requires me to restart the application which is playing the audio. I found a better workaround which is to open PulseAudio Volume Control (pavucontrol) and toggle the profile from "Play HiFi quality music" -> "Off" -> "Play HiFi quality music". - ` + ➜ lsb_release -rd Description: Ubuntu 21.10 Release: 21.10 ` - ` - apt-cache policy pulseaudio + + ➜ apt-cache policy pulseaudio pulseaudio: Installed: 1:15.0+dfsg1-1ubuntu2.2 Candidate: 1:15.0+dfsg1-1ubuntu2.2 Version table: *** 1:15.0+dfsg1-1ubuntu2.2 500 500 http://ca.archive.ubuntu.com/ubuntu impish-updates/main amd64 Packages 100 /var/lib/dpkg/status 1:15.0+dfsg1-1ubuntu2 500 500 http://ca.archive.ubuntu.com/ubuntu impish/main amd64 Packages - ` ** Description changed: The audio on my laptop drops when I open a new application (or switch to a different one). Sometimes it happens when switching tabs. It does not matter which application is playing audio, the audio usually stops when the application is switched. The typical workaround is to kill pulseaudio and start it again but that requires me to restart the application which is playing the audio. I found a better workaround which is to open PulseAudio Volume Control (pavucontrol) and toggle the profile from "Play HiFi quality music" -> "Off" -> "Play HiFi quality music". - ➜ lsb_release -rd Description: Ubuntu 21.10 Release: 21.10 - ` - ➜ apt-cache policy pulseaudio pulseaudio: Installed: 1:15.0+dfsg1-1ubuntu2.2 Candidate: 1:15.0+dfsg1-1ubuntu2.2 Version table: *** 1:15.0+dfsg1-1ubuntu2.2 500 500 http://ca.archive.ubuntu.com/ubuntu impish-updates/main amd64 Packages 100 /var/lib/dpkg/status 1:15.0+dfsg1-1ubuntu2 500 500 http://ca.archive.ubuntu.
[Touch-packages] [Bug 1811531]
SUSE-FU-2022:0454-1: An update that solves 54 vulnerabilities, contains 6 features and has 247 fixes is now available. Category: feature (moderate) Bug References: 180,1000117,1000194,1000742,1002895,1003091,1005246,1010874,1010966,1011936,1015549,1027610,1027705,1029902,1030038,1032118,1032119,1035604,1039469,1040164,1040256,1041090,1042670,1049186,1049304,1050653,1050665,1055478,1055542,1056951,1057496,1062237,1066873,1068790,1070737,1070738,1070853,1071941,1073310,1073845,1073879,1074247,1076519,1077096,1077230,1078329,1079761,1080301,1081005,1081750,1081751,1082155,1082163,1082318,1083826,1084117,1084157,1085276,1085529,1085661,1087104,1088573,1090427,1090953,1093518,1093917,1094788,1094814,1094883,1095267,1096738,1096937,1097531,1098535,1099308,1099569,1102868,1108508,1109882,1109998,1110435,1110869,1110871,493,622,657,1112357,1115769,1118611,1119376,1119416,1119792,1121717,1121852,1122191,1123064,1123185,1123186,1123558,1124885,1125815,1126283,1126318,1127173,1128146,1128323,1128355,1129071,1129566,1130840,1132174,1132323,1132455,1132663,1132900,1135009,1136444,1138666,1138715,1138746,1139915,1140255,1141168,1142899,1143033,1143454,1143893,1144506,1149686,1149792,1150190,1150895,1153830,1155815,1156677,1156694,1156908,1157104,1157354,1159235,1159538,1161557,1161770,1162224,1162367,1162743,1163978,1164310,1165439,1165578,1165730,1165823,1165960,1166139,1166758,1167008,1167501,1167732,1167746,1168480,1168973,1169489,1170175,1170863,1171368,1171561,1172226,1172908,1172928,1173226,1173356,1174009,1174091,1174514,1175729,1176116,1176129,1176134,1176232,1176256,1176257,1176258,1176259,1176262,1176389,1176785,1176977,1177120,1177127,1178168,1178341,1178670,1179562,1179630,1179805,1180125,1180781,1181126,1181324,1181944,1182066,1182211,1182244,1182264,1182379,1182963,1183059,1183374,1183858,1184505,1185588,1185706,1185748,1186738,1187045,1190781,1193357,428177,431945,589441,613497,637176,657698,658604,673071,715423,743787,747125,750618,751718,754447,754677,761500,784670,787526,799119,809831,811890,825221,828513,831629,834601,835687,839107,84331,855666,858239,867887,871152,885662,885882,889363,892480,898917,907584,912460,913229,915479,917607,917759,917815,922448,929736,930189,931978,935856,937912,939456,940608,942385,942751,944204,945455,946648,947357,947679,948198,954486,954690,961334,962291,963974,964204,964472,964474,965830,967128,968270,968601,975875,981848,988086,992988,992989,992992,993130,993825,993968,994910,996255,997614 CVE References: CVE-2011-3389,CVE-2011-4944,CVE-2012-0845,CVE-2012-1150,CVE-2013-1437,CVE-2013-1752,CVE-2013-4238,CVE-2013-4314,CVE-2014-0012,CVE-2014-1829,CVE-2014-1830,CVE-2014-2667,CVE-2014-4650,CVE-2014-7202,CVE-2014-7203,CVE-2014-9721,CVE-2015-2296,CVE-2016-10745,CVE-2016-1238,CVE-2016-9015,CVE-2017-18342,CVE-2017-6512,CVE-2018-18074,CVE-2018-20060,CVE-2018-7750,CVE-2019-10906,CVE-2019-11236,CVE-2019-11324,CVE-2019-13132,CVE-2019-20907,CVE-2019-20916,CVE-2019-5010,CVE-2019-6250,CVE-2019-8341,CVE-2019-9740,CVE-2019-9947,CVE-2020-14343,CVE-2020-15166,CVE-2020-15523,CVE-2020-15801,CVE-2020-1747,CVE-2020-25659,CVE-2020-26137,CVE-2020-27783,CVE-2020-28493,CVE-2020-29651,CVE-2020-36242,CVE-2020-8492,CVE-2021-23336,CVE-2021-28957,CVE-2021-29921,CVE-2021-3177,CVE-2021-33503,CVE-2021-3426 JIRA References: ECO-3105,SLE-12986,SLE-17532,SLE-17957,SLE-7686,SLE-9135 Sources used: NOTE: This line indicates an update has been released for the listed product(s). At times this might be only a partial fix. If you have questions please reach out to maintenance coordination. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to zeromq3 in Ubuntu. https://bugs.launchpad.net/bugs/1811531 Title: remote execution vulnerability Status in zeromq3 package in Ubuntu: Fix Released Status in zeromq3 package in Debian: Fix Released Status in zeromq package in Suse: Fix Released Bug description: Dear Maintainer, A remote execution vulnerability has been reported in zeromq. Full details can be found on the upstream issue tracker [1]. The issue is fixed in upstream version v4.3.1, just released, or with the attached patch which is targeted for v4.2.5 (bionic and cosmic). The latest version will hopefully arrive in disco via debian unstable soon, but I would recommend patching older releases. As mentioned in the upstream tracker and the changelog, the issue can be mitigated by ASLR and by authentication via CURVE/GSSAPI. As far as I am aware no CVEs have been assigned nor have been requested as of now. [1] https://github.com/zeromq/libzmq/issues/3351 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zeromq3/+bug/1811531/+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 1811531]
SUSE-FU-2022:0447-1: An update that solves 54 vulnerabilities, contains 6 features and has 247 fixes is now available. Category: feature (moderate) Bug References: 180,1000117,1000194,1000742,1002895,1003091,1005246,1010874,1010966,1011936,1015549,1027610,1027705,1029902,1030038,1032118,1032119,1035604,1039469,1040164,1040256,1041090,1042670,1049186,1049304,1050653,1050665,1055478,1055542,1056951,1057496,1062237,1066873,1068790,1070737,1070738,1070853,1071941,1073310,1073845,1073879,1074247,1076519,1077096,1077230,1078329,1079761,1080301,1081005,1081750,1081751,1082155,1082163,1082318,1083826,1084117,1084157,1085276,1085529,1085661,1087104,1088573,1090427,1090953,1093518,1093917,1094788,1094814,1094883,1095267,1096738,1096937,1097531,1098535,1099308,1099569,1102868,1108508,1109882,1109998,1110435,1110869,1110871,493,622,657,1112357,1115769,1118611,1119376,1119416,1119792,1121717,1121852,1122191,1123064,1123185,1123186,1123558,1124885,1125815,1126283,1126318,1127173,1128146,1128323,1128355,1129071,1129566,1130840,1132174,1132323,1132455,1132663,1132900,1135009,1136444,1138666,1138715,1138746,1139915,1140255,1141168,1142899,1143033,1143454,1143893,1144506,1149686,1149792,1150190,1150895,1153830,1155815,1156677,1156694,1156908,1157104,1157354,1159235,1159538,1161557,1161770,1162224,1162367,1162743,1163978,1164310,1165439,1165578,1165730,1165823,1165960,1166139,1166758,1167008,1167501,1167732,1167746,1168480,1168973,1169489,1170175,1170863,1171368,1171561,1172226,1172908,1172928,1173226,1173356,1174009,1174091,1174514,1175729,1176116,1176129,1176134,1176232,1176256,1176257,1176258,1176259,1176262,1176389,1176785,1176977,1177120,1177127,1178168,1178341,1178670,1179562,1179630,1179805,1180125,1180781,1181126,1181324,1181944,1182066,1182211,1182244,1182264,1182379,1182963,1183059,1183374,1183858,1184505,1185588,1185706,1185748,1186738,1187045,1190781,1193357,428177,431945,589441,613497,637176,657698,658604,673071,715423,743787,747125,750618,751718,754447,754677,761500,784670,787526,799119,809831,811890,825221,828513,831629,834601,835687,839107,84331,855666,858239,867887,871152,885662,885882,889363,892480,898917,907584,912460,913229,915479,917607,917759,917815,922448,929736,930189,931978,935856,937912,939456,940608,942385,942751,944204,945455,946648,947357,947679,948198,954486,954690,961334,962291,963974,964204,964472,964474,965830,967128,968270,968601,975875,981848,988086,992988,992989,992992,993130,993825,993968,994910,996255,997614 CVE References: CVE-2011-3389,CVE-2011-4944,CVE-2012-0845,CVE-2012-1150,CVE-2013-1437,CVE-2013-1752,CVE-2013-4238,CVE-2013-4314,CVE-2014-0012,CVE-2014-1829,CVE-2014-1830,CVE-2014-2667,CVE-2014-4650,CVE-2014-7202,CVE-2014-7203,CVE-2014-9721,CVE-2015-2296,CVE-2016-10745,CVE-2016-1238,CVE-2016-9015,CVE-2017-18342,CVE-2017-6512,CVE-2018-18074,CVE-2018-20060,CVE-2018-7750,CVE-2019-10906,CVE-2019-11236,CVE-2019-11324,CVE-2019-13132,CVE-2019-20907,CVE-2019-20916,CVE-2019-5010,CVE-2019-6250,CVE-2019-8341,CVE-2019-9740,CVE-2019-9947,CVE-2020-14343,CVE-2020-15166,CVE-2020-15523,CVE-2020-15801,CVE-2020-1747,CVE-2020-25659,CVE-2020-26137,CVE-2020-27783,CVE-2020-28493,CVE-2020-29651,CVE-2020-36242,CVE-2020-8492,CVE-2021-23336,CVE-2021-28957,CVE-2021-29921,CVE-2021-3177,CVE-2021-33503,CVE-2021-3426 JIRA References: ECO-3105,SLE-12986,SLE-17532,SLE-17957,SLE-7686,SLE-9135 Sources used: NOTE: This line indicates an update has been released for the listed product(s). At times this might be only a partial fix. If you have questions please reach out to maintenance coordination. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to zeromq3 in Ubuntu. https://bugs.launchpad.net/bugs/1811531 Title: remote execution vulnerability Status in zeromq3 package in Ubuntu: Fix Released Status in zeromq3 package in Debian: Fix Released Status in zeromq package in Suse: Fix Released Bug description: Dear Maintainer, A remote execution vulnerability has been reported in zeromq. Full details can be found on the upstream issue tracker [1]. The issue is fixed in upstream version v4.3.1, just released, or with the attached patch which is targeted for v4.2.5 (bionic and cosmic). The latest version will hopefully arrive in disco via debian unstable soon, but I would recommend patching older releases. As mentioned in the upstream tracker and the changelog, the issue can be mitigated by ASLR and by authentication via CURVE/GSSAPI. As far as I am aware no CVEs have been assigned nor have been requested as of now. [1] https://github.com/zeromq/libzmq/issues/3351 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zeromq3/+bug/1811531/+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 1811531]
SUSE-FU-2022:0452-1: An update that solves 54 vulnerabilities, contains 6 features and has 247 fixes is now available. Category: feature (moderate) Bug References: 180,1000117,1000194,1000742,1002895,1003091,1005246,1010874,1010966,1011936,1015549,1027610,1027705,1029902,1030038,1032118,1032119,1035604,1039469,1040164,1040256,1041090,1042670,1049186,1049304,1050653,1050665,1055478,1055542,1056951,1057496,1062237,1066873,1068790,1070737,1070738,1070853,1071941,1073310,1073845,1073879,1074247,1076519,1077096,1077230,1078329,1079761,1080301,1081005,1081750,1081751,1082155,1082163,1082318,1083826,1084117,1084157,1085276,1085529,1085661,1087104,1088573,1090427,1090953,1093518,1093917,1094788,1094814,1094883,1095267,1096738,1096937,1097531,1098535,1099308,1099569,1102868,1108508,1109882,1109998,1110435,1110869,1110871,493,622,657,1112357,1115769,1118611,1119376,1119416,1119792,1121717,1121852,1122191,1123064,1123185,1123186,1123558,1124885,1125815,1126283,1126318,1127173,1128146,1128323,1128355,1129071,1129566,1130840,1132174,1132323,1132455,1132663,1132900,1135009,1136444,1138666,1138715,1138746,1139915,1140255,1141168,1142899,1143033,1143454,1143893,1144506,1149686,1149792,1150190,1150895,1153830,1155815,1156677,1156694,1156908,1157104,1157354,1159235,1159538,1161557,1161770,1162224,1162367,1162743,1163978,1164310,1165439,1165578,1165730,1165823,1165960,1166139,1166758,1167008,1167501,1167732,1167746,1168480,1168973,1169489,1170175,1170863,1171368,1171561,1172226,1172908,1172928,1173226,1173356,1174009,1174091,1174514,1175729,1176116,1176129,1176134,1176232,1176256,1176257,1176258,1176259,1176262,1176389,1176785,1176977,1177120,1177127,1178168,1178341,1178670,1179562,1179630,1179805,1180125,1180781,1181126,1181324,1181944,1182066,1182211,1182244,1182264,1182379,1182963,1183059,1183374,1183858,1184505,1185588,1185706,1185748,1186738,1187045,1190781,1193357,428177,431945,589441,613497,637176,657698,658604,673071,715423,743787,747125,750618,751718,754447,754677,761500,784670,787526,799119,809831,811890,825221,828513,831629,834601,835687,839107,84331,855666,858239,867887,871152,885662,885882,889363,892480,898917,907584,912460,913229,915479,917607,917759,917815,922448,929736,930189,931978,935856,937912,939456,940608,942385,942751,944204,945455,946648,947357,947679,948198,954486,954690,961334,962291,963974,964204,964472,964474,965830,967128,968270,968601,975875,981848,988086,992988,992989,992992,993130,993825,993968,994910,996255,997614 CVE References: CVE-2011-3389,CVE-2011-4944,CVE-2012-0845,CVE-2012-1150,CVE-2013-1437,CVE-2013-1752,CVE-2013-4238,CVE-2013-4314,CVE-2014-0012,CVE-2014-1829,CVE-2014-1830,CVE-2014-2667,CVE-2014-4650,CVE-2014-7202,CVE-2014-7203,CVE-2014-9721,CVE-2015-2296,CVE-2016-10745,CVE-2016-1238,CVE-2016-9015,CVE-2017-18342,CVE-2017-6512,CVE-2018-18074,CVE-2018-20060,CVE-2018-7750,CVE-2019-10906,CVE-2019-11236,CVE-2019-11324,CVE-2019-13132,CVE-2019-20907,CVE-2019-20916,CVE-2019-5010,CVE-2019-6250,CVE-2019-8341,CVE-2019-9740,CVE-2019-9947,CVE-2020-14343,CVE-2020-15166,CVE-2020-15523,CVE-2020-15801,CVE-2020-1747,CVE-2020-25659,CVE-2020-26137,CVE-2020-27783,CVE-2020-28493,CVE-2020-29651,CVE-2020-36242,CVE-2020-8492,CVE-2021-23336,CVE-2021-28957,CVE-2021-29921,CVE-2021-3177,CVE-2021-33503,CVE-2021-3426 JIRA References: ECO-3105,SLE-12986,SLE-17532,SLE-17957,SLE-7686,SLE-9135 Sources used: NOTE: This line indicates an update has been released for the listed product(s). At times this might be only a partial fix. If you have questions please reach out to maintenance coordination. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to zeromq3 in Ubuntu. https://bugs.launchpad.net/bugs/1811531 Title: remote execution vulnerability Status in zeromq3 package in Ubuntu: Fix Released Status in zeromq3 package in Debian: Fix Released Status in zeromq package in Suse: Fix Released Bug description: Dear Maintainer, A remote execution vulnerability has been reported in zeromq. Full details can be found on the upstream issue tracker [1]. The issue is fixed in upstream version v4.3.1, just released, or with the attached patch which is targeted for v4.2.5 (bionic and cosmic). The latest version will hopefully arrive in disco via debian unstable soon, but I would recommend patching older releases. As mentioned in the upstream tracker and the changelog, the issue can be mitigated by ASLR and by authentication via CURVE/GSSAPI. As far as I am aware no CVEs have been assigned nor have been requested as of now. [1] https://github.com/zeromq/libzmq/issues/3351 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zeromq3/+bug/1811531/+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 1811531]
SUSE-FU-2022:0444-1: An update that solves 51 vulnerabilities, contains 21 features and has 249 fixes is now available. Category: feature (moderate) Bug References: 180,1000117,1000194,1000742,1002895,1003091,1005246,1010874,1010966,1011936,1015549,1027610,1027705,1029902,1030038,1032118,1032119,1035604,1039469,1040164,1040256,1041090,1042670,1049186,1049304,1050653,1050665,1055478,1055542,1056951,1057496,1062237,1066873,1068790,1070737,1070738,1070853,1071941,1073310,1073845,1073879,1074247,1076519,1077096,1077230,1078329,1079761,1080301,1081005,1081750,1081751,1082155,1082163,1082318,1083826,1084117,1084157,1085276,1085529,1085661,1087104,1088573,1090427,1090953,1093518,1093917,1094788,1094814,1094883,1095267,1096738,1096937,1097531,1098535,1099308,1099569,1102868,1108508,1109882,1109998,1110435,1110869,1110871,493,622,657,1112357,1115769,1118611,1119376,1119416,1119792,1121717,1121852,1122191,1123064,1123185,1123186,1123558,1124885,1125815,1126283,1126318,1127173,1128146,1128323,1128355,1129071,1129566,1130840,1132174,1132323,1132455,1132663,1132900,1135009,1136444,1138666,1138715,1138746,1139915,1140255,1141168,1142899,1143033,1143454,1143893,1144506,1149686,1149792,1150190,1150895,1153830,1155815,1156677,1156694,1156908,1157104,1157354,1159235,1159538,1161557,1161770,1162224,1162367,1162743,1163978,1164310,1165439,1165578,1165730,1165823,1165960,1166139,1166758,1167008,1167501,1167732,1167746,1168480,1168973,1169489,1170175,1170863,1171368,1171561,1172226,1172908,1172928,1173226,1173356,1174009,1174091,1174514,1175729,1176116,1176129,1176134,1176232,1176256,1176257,1176258,1176259,1176262,1176389,1176785,1176977,1177120,1177127,1177559,1178168,1178341,1178670,1179562,1179630,1179805,1180125,1180781,1181126,1181324,1181944,1182066,1182211,1182244,1182264,1182379,1182963,1183059,1183374,1183858,1184505,1185588,1185706,1185748,1186738,1187045,1190781,1193357,428177,431945,637176,657698,658604,673071,715423,743787,747125,750618,751718,754447,754677,761500,784670,787526,799119,809831,811890,825221,828513,831629,834601,835687,839107,84331,855666,858239,867887,871152,885662,885882,889363,892480,898917,907584,912460,913229,915479,917607,917759,917815,922448,929736,930189,931978,935856,937912,939456,940608,942385,942751,944204,945455,946648,947357,947679,948198,954486,954690,961334,962291,963974,964204,964472,964474,965830,967128,968270,968601,975875,981848,988086,992988,992989,992992,993130,993825,993968,994910,996255,997614 CVE References: CVE-2011-3389,CVE-2011-4944,CVE-2012-0845,CVE-2012-1150,CVE-2013-1752,CVE-2013-4238,CVE-2013-4314,CVE-2014-0012,CVE-2014-1829,CVE-2014-1830,CVE-2014-2667,CVE-2014-4650,CVE-2014-7202,CVE-2014-7203,CVE-2014-9721,CVE-2015-2296,CVE-2016-10745,CVE-2016-9015,CVE-2017-18342,CVE-2018-18074,CVE-2018-20060,CVE-2018-7750,CVE-2019-10906,CVE-2019-11236,CVE-2019-11324,CVE-2019-13132,CVE-2019-20907,CVE-2019-20916,CVE-2019-5010,CVE-2019-6250,CVE-2019-8341,CVE-2019-9740,CVE-2019-9947,CVE-2020-14343,CVE-2020-15166,CVE-2020-15523,CVE-2020-15801,CVE-2020-1747,CVE-2020-25659,CVE-2020-26137,CVE-2020-27783,CVE-2020-28493,CVE-2020-29651,CVE-2020-36242,CVE-2020-8492,CVE-2021-23336,CVE-2021-28957,CVE-2021-29921,CVE-2021-3177,CVE-2021-33503,CVE-2021-3426 JIRA References: ECO-3105,SLE-11435,SLE-12684,SLE-12986,SLE-13688,SLE-14253,SLE-15159,SLE-15860,SLE-15861,SLE-16754,SLE-17532,SLE-17957,SLE-18260,SLE-18354,SLE-18446,SLE-19264,SLE-3887,SLE-4480,SLE-4577,SLE-7686,SLE-9135 Sources used: SUSE Manager Tools 15-BETA (src):venv-salt-minion-3002.2-159000.3.3.2 NOTE: This line indicates an update has been released for the listed product(s). At times this might be only a partial fix. If you have questions please reach out to maintenance coordination. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to zeromq3 in Ubuntu. https://bugs.launchpad.net/bugs/1811531 Title: remote execution vulnerability Status in zeromq3 package in Ubuntu: Fix Released Status in zeromq3 package in Debian: Fix Released Status in zeromq package in Suse: Fix Released Bug description: Dear Maintainer, A remote execution vulnerability has been reported in zeromq. Full details can be found on the upstream issue tracker [1]. The issue is fixed in upstream version v4.3.1, just released, or with the attached patch which is targeted for v4.2.5 (bionic and cosmic). The latest version will hopefully arrive in disco via debian unstable soon, but I would recommend patching older releases. As mentioned in the upstream tracker and the changelog, the issue can be mitigated by ASLR and by authentication via CURVE/GSSAPI. As far as I am aware no CVEs have been assigned nor have been requested as of now. [1] https://github.com/zeromq/libzmq/issues/3351 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zeromq3/+bug/1811531/+subscriptions -- Mailing list: https://launchpad.net
[Touch-packages] [Bug 1811531]
SUSE-FU-2022:0450-1: An update that solves 54 vulnerabilities, contains 6 features and has 247 fixes is now available. Category: feature (moderate) Bug References: 180,1000117,1000194,1000742,1002895,1003091,1005246,1010874,1010966,1011936,1015549,1027610,1027705,1029902,1030038,1032118,1032119,1035604,1039469,1040164,1040256,1041090,1042670,1049186,1049304,1050653,1050665,1055478,1055542,1056951,1057496,1062237,1066873,1068790,1070737,1070738,1070853,1071941,1073310,1073845,1073879,1074247,1076519,1077096,1077230,1078329,1079761,1080301,1081005,1081750,1081751,1082155,1082163,1082318,1083826,1084117,1084157,1085276,1085529,1085661,1087104,1088573,1090427,1090953,1093518,1093917,1094788,1094814,1094883,1095267,1096738,1096937,1097531,1098535,1099308,1099569,1102868,1108508,1109882,1109998,1110435,1110869,1110871,493,622,657,1112357,1115769,1118611,1119376,1119416,1119792,1121717,1121852,1122191,1123064,1123185,1123186,1123558,1124885,1125815,1126283,1126318,1127173,1128146,1128323,1128355,1129071,1129566,1130840,1132174,1132323,1132455,1132663,1132900,1135009,1136444,1138666,1138715,1138746,1139915,1140255,1141168,1142899,1143033,1143454,1143893,1144506,1149686,1149792,1150190,1150895,1153830,1155815,1156677,1156694,1156908,1157104,1157354,1159235,1159538,1161557,1161770,1162224,1162367,1162743,1163978,1164310,1165439,1165578,1165730,1165823,1165960,1166139,1166758,1167008,1167501,1167732,1167746,1168480,1168973,1169489,1170175,1170863,1171368,1171561,1172226,1172908,1172928,1173226,1173356,1174009,1174091,1174514,1175729,1176116,1176129,1176134,1176232,1176256,1176257,1176258,1176259,1176262,1176389,1176785,1176977,1177120,1177127,1178168,1178341,1178670,1179562,1179630,1179805,1180125,1180781,1181126,1181324,1181944,1182066,1182211,1182244,1182264,1182379,1182963,1183059,1183374,1183858,1184505,1185588,1185706,1185748,1186738,1187045,1190781,1193357,428177,431945,589441,613497,637176,657698,658604,673071,715423,743787,747125,750618,751718,754447,754677,761500,784670,787526,799119,809831,811890,825221,828513,831629,834601,835687,839107,84331,855666,858239,867887,871152,885662,885882,889363,892480,898917,907584,912460,913229,915479,917607,917759,917815,922448,929736,930189,931978,935856,937912,939456,940608,942385,942751,944204,945455,946648,947357,947679,948198,954486,954690,961334,962291,963974,964204,964472,964474,965830,967128,968270,968601,975875,981848,988086,992988,992989,992992,993130,993825,993968,994910,996255,997614 CVE References: CVE-2011-3389,CVE-2011-4944,CVE-2012-0845,CVE-2012-1150,CVE-2013-1437,CVE-2013-1752,CVE-2013-4238,CVE-2013-4314,CVE-2014-0012,CVE-2014-1829,CVE-2014-1830,CVE-2014-2667,CVE-2014-4650,CVE-2014-7202,CVE-2014-7203,CVE-2014-9721,CVE-2015-2296,CVE-2016-10745,CVE-2016-1238,CVE-2016-9015,CVE-2017-18342,CVE-2017-6512,CVE-2018-18074,CVE-2018-20060,CVE-2018-7750,CVE-2019-10906,CVE-2019-11236,CVE-2019-11324,CVE-2019-13132,CVE-2019-20907,CVE-2019-20916,CVE-2019-5010,CVE-2019-6250,CVE-2019-8341,CVE-2019-9740,CVE-2019-9947,CVE-2020-14343,CVE-2020-15166,CVE-2020-15523,CVE-2020-15801,CVE-2020-1747,CVE-2020-25659,CVE-2020-26137,CVE-2020-27783,CVE-2020-28493,CVE-2020-29651,CVE-2020-36242,CVE-2020-8492,CVE-2021-23336,CVE-2021-28957,CVE-2021-29921,CVE-2021-3177,CVE-2021-33503,CVE-2021-3426 JIRA References: ECO-3105,SLE-12986,SLE-17532,SLE-17957,SLE-7686,SLE-9135 Sources used: NOTE: This line indicates an update has been released for the listed product(s). At times this might be only a partial fix. If you have questions please reach out to maintenance coordination. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to zeromq3 in Ubuntu. https://bugs.launchpad.net/bugs/1811531 Title: remote execution vulnerability Status in zeromq3 package in Ubuntu: Fix Released Status in zeromq3 package in Debian: Fix Released Status in zeromq package in Suse: Fix Released Bug description: Dear Maintainer, A remote execution vulnerability has been reported in zeromq. Full details can be found on the upstream issue tracker [1]. The issue is fixed in upstream version v4.3.1, just released, or with the attached patch which is targeted for v4.2.5 (bionic and cosmic). The latest version will hopefully arrive in disco via debian unstable soon, but I would recommend patching older releases. As mentioned in the upstream tracker and the changelog, the issue can be mitigated by ASLR and by authentication via CURVE/GSSAPI. As far as I am aware no CVEs have been assigned nor have been requested as of now. [1] https://github.com/zeromq/libzmq/issues/3351 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zeromq3/+bug/1811531/+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 1811531]
-2014-9721,CVE-2015-0204,CVE-2015-0205,CVE-2015-0206,CVE-2015-0209,CVE-2015-0286,CVE-2015-0287,CVE-2015-0288,CVE-2015-0289,CVE-2015-0293,CVE-2015-1788,CVE-2015-1789,CVE-2015-1790,CVE-2015-1791,CVE-2015-1792,CVE-2015-2296,CVE-2015-3194,CVE-2015-3195,CVE-2015-3196,CVE-2015-3197,CVE-2015-3216,CVE-2015-4000,CVE-2016-0702,CVE-2016-0705,CVE-2016-0797,CVE-2016-0798,CVE-2016-0799,CVE-2016-0800,CVE-2016-10745,CVE-2016-2105,CVE-2016-2106,CVE-2016-2107,CVE-2016-2109,CVE-2016-2176,CVE-2016-2177,CVE-2016-2178,CVE-2016-2179,CVE-2016-2180,CVE-2016-2181,CVE-2016-2182,CVE-2016-2183,CVE-2016-6302,CVE-2016-6303,CVE-2016-6304,CVE-2016-6306,CVE-2016-7052,CVE-2016-7055,CVE-2016-9015,CVE-2017-18342,CVE-2017-3731,CVE-2017-3732,CVE-2017-3735,CVE-2017-3736,CVE-2017-3737,CVE-2017-3738,CVE-2018-0732,CVE-2018-0734,CVE-2018-0737,CVE-2018-0739,CVE-2018-18074,CVE-2018-20060,CVE-2018-5407,CVE-2018-7750,CVE-2019-10906,CVE-2019-11236,CVE-2019-11324,CVE-2019-13132,CVE-2019-1547,CVE-2019-1551,CVE-2019-1559,CVE-2019-1563,CVE-2019-20907,CVE-2019-20916,CVE-2019-5010,CVE-2019-6250,CVE-2019-8341,CVE-2019-9740,CVE-2019-9947,CVE-2020-14343,CVE-2020-15166,CVE-2020-15523,CVE-2020-15801,CVE-2020-1747,CVE-2020-1971,CVE-2020-25659,CVE-2020-26137,CVE-2020-27783,CVE-2020-28493,CVE-2020-29651,CVE-2020-36242,CVE-2020-8492,CVE-2021-23336,CVE-2021-23840,CVE-2021-23841,CVE-2021-28957,CVE-2021-29921,CVE-2021-3177,CVE-2021-33503,CVE-2021-3426,CVE-2021-3712 JIRA References: ECO-3105,SLE-11435,SLE-12684,SLE-12986,SLE-13688,SLE-14253,SLE-15159,SLE-15860,SLE-15861,SLE-16754,SLE-17532,SLE-17957,SLE-18260,SLE-18354,SLE-18446,SLE-19264,SLE-3887,SLE-4480,SLE-4577,SLE-7686,SLE-9135 Sources used: SUSE Manager Tools 12-BETA (src):venv-salt-minion-3002.2-3.3.2 NOTE: This line indicates an update has been released for the listed product(s). At times this might be only a partial fix. If you have questions please reach out to maintenance coordination. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to zeromq3 in Ubuntu. https://bugs.launchpad.net/bugs/1811531 Title: remote execution vulnerability Status in zeromq3 package in Ubuntu: Fix Released Status in zeromq3 package in Debian: Fix Released Status in zeromq package in Suse: Fix Released Bug description: Dear Maintainer, A remote execution vulnerability has been reported in zeromq. Full details can be found on the upstream issue tracker [1]. The issue is fixed in upstream version v4.3.1, just released, or with the attached patch which is targeted for v4.2.5 (bionic and cosmic). The latest version will hopefully arrive in disco via debian unstable soon, but I would recommend patching older releases. As mentioned in the upstream tracker and the changelog, the issue can be mitigated by ASLR and by authentication via CURVE/GSSAPI. As far as I am aware no CVEs have been assigned nor have been requested as of now. [1] https://github.com/zeromq/libzmq/issues/3351 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zeromq3/+bug/1811531/+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 1811531]
SUSE-FU-2022:0456-1: An update that solves 54 vulnerabilities, contains 6 features and has 247 fixes is now available. Category: feature (moderate) Bug References: 180,1000117,1000194,1000742,1002895,1003091,1005246,1010874,1010966,1011936,1015549,1027610,1027705,1029902,1030038,1032118,1032119,1035604,1039469,1040164,1040256,1041090,1042670,1049186,1049304,1050653,1050665,1055478,1055542,1056951,1057496,1062237,1066873,1068790,1070737,1070738,1070853,1071941,1073310,1073845,1073879,1074247,1076519,1077096,1077230,1078329,1079761,1080301,1081005,1081750,1081751,1082155,1082163,1082318,1083826,1084117,1084157,1085276,1085529,1085661,1087104,1088573,1090427,1090953,1093518,1093917,1094788,1094814,1094883,1095267,1096738,1096937,1097531,1098535,1099308,1099569,1102868,1108508,1109882,1109998,1110435,1110869,1110871,493,622,657,1112357,1115769,1118611,1119376,1119416,1119792,1121717,1121852,1122191,1123064,1123185,1123186,1123558,1124885,1125815,1126283,1126318,1127173,1128146,1128323,1128355,1129071,1129566,1130840,1132174,1132323,1132455,1132663,1132900,1135009,1136444,1138666,1138715,1138746,1139915,1140255,1141168,1142899,1143033,1143454,1143893,1144506,1149686,1149792,1150190,1150895,1153830,1155815,1156677,1156694,1156908,1157104,1157354,1159235,1159538,1161557,1161770,1162224,1162367,1162743,1163978,1164310,1165439,1165578,1165730,1165823,1165960,1166139,1166758,1167008,1167501,1167732,1167746,1168480,1168973,1169489,1170175,1170863,1171368,1171561,1172226,1172908,1172928,1173226,1173356,1174009,1174091,1174514,1175729,1176116,1176129,1176134,1176232,1176256,1176257,1176258,1176259,1176262,1176389,1176785,1176977,1177120,1177127,1178168,1178341,1178670,1179562,1179630,1179805,1180125,1180781,1181126,1181324,1181944,1182066,1182211,1182244,1182264,1182379,1182963,1183059,1183374,1183858,1184505,1185588,1185706,1185748,1186738,1187045,1190781,1193357,428177,431945,589441,613497,637176,657698,658604,673071,715423,743787,747125,750618,751718,754447,754677,761500,784670,787526,799119,809831,811890,825221,828513,831629,834601,835687,839107,84331,855666,858239,867887,871152,885662,885882,889363,892480,898917,907584,912460,913229,915479,917607,917759,917815,922448,929736,930189,931978,935856,937912,939456,940608,942385,942751,944204,945455,946648,947357,947679,948198,954486,954690,961334,962291,963974,964204,964472,964474,965830,967128,968270,968601,975875,981848,988086,992988,992989,992992,993130,993825,993968,994910,996255,997614 CVE References: CVE-2011-3389,CVE-2011-4944,CVE-2012-0845,CVE-2012-1150,CVE-2013-1437,CVE-2013-1752,CVE-2013-4238,CVE-2013-4314,CVE-2014-0012,CVE-2014-1829,CVE-2014-1830,CVE-2014-2667,CVE-2014-4650,CVE-2014-7202,CVE-2014-7203,CVE-2014-9721,CVE-2015-2296,CVE-2016-10745,CVE-2016-1238,CVE-2016-9015,CVE-2017-18342,CVE-2017-6512,CVE-2018-18074,CVE-2018-20060,CVE-2018-7750,CVE-2019-10906,CVE-2019-11236,CVE-2019-11324,CVE-2019-13132,CVE-2019-20907,CVE-2019-20916,CVE-2019-5010,CVE-2019-6250,CVE-2019-8341,CVE-2019-9740,CVE-2019-9947,CVE-2020-14343,CVE-2020-15166,CVE-2020-15523,CVE-2020-15801,CVE-2020-1747,CVE-2020-25659,CVE-2020-26137,CVE-2020-27783,CVE-2020-28493,CVE-2020-29651,CVE-2020-36242,CVE-2020-8492,CVE-2021-23336,CVE-2021-28957,CVE-2021-29921,CVE-2021-3177,CVE-2021-33503,CVE-2021-3426 JIRA References: ECO-3105,SLE-12986,SLE-17532,SLE-17957,SLE-7686,SLE-9135 Sources used: NOTE: This line indicates an update has been released for the listed product(s). At times this might be only a partial fix. If you have questions please reach out to maintenance coordination. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to zeromq3 in Ubuntu. https://bugs.launchpad.net/bugs/1811531 Title: remote execution vulnerability Status in zeromq3 package in Ubuntu: Fix Released Status in zeromq3 package in Debian: Fix Released Status in zeromq package in Suse: Fix Released Bug description: Dear Maintainer, A remote execution vulnerability has been reported in zeromq. Full details can be found on the upstream issue tracker [1]. The issue is fixed in upstream version v4.3.1, just released, or with the attached patch which is targeted for v4.2.5 (bionic and cosmic). The latest version will hopefully arrive in disco via debian unstable soon, but I would recommend patching older releases. As mentioned in the upstream tracker and the changelog, the issue can be mitigated by ASLR and by authentication via CURVE/GSSAPI. As far as I am aware no CVEs have been assigned nor have been requested as of now. [1] https://github.com/zeromq/libzmq/issues/3351 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zeromq3/+bug/1811531/+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 1958011] [NEW] why /usr/lib/python39.zip
Public bug reported: dear mantainers, just out of curiosity, why is /usr/lib/python39.zip in the sys.path? no package ships such file... thanks a. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: python3-minimal 3.9.4-1build1 ProcVersionSignature: Ubuntu 5.13.0-25.26-generic 5.13.19 Uname: Linux 5.13.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 CasperMD5CheckResult: pass Date: Sat Jan 15 10:48:31 2022 InstallationDate: Installed on 2021-10-21 (86 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) SourcePackage: python3-defaults UpgradeStatus: Upgraded to impish on 2021-10-21 (85 days ago) ** Affects: python3-defaults (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug impish -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python3-defaults in Ubuntu. https://bugs.launchpad.net/bugs/1958011 Title: why /usr/lib/python39.zip Status in python3-defaults package in Ubuntu: New Bug description: dear mantainers, just out of curiosity, why is /usr/lib/python39.zip in the sys.path? no package ships such file... thanks a. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: python3-minimal 3.9.4-1build1 ProcVersionSignature: Ubuntu 5.13.0-25.26-generic 5.13.19 Uname: Linux 5.13.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 CasperMD5CheckResult: pass Date: Sat Jan 15 10:48:31 2022 InstallationDate: Installed on 2021-10-21 (86 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) SourcePackage: python3-defaults UpgradeStatus: Upgraded to impish on 2021-10-21 (85 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python3-defaults/+bug/1958011/+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 1941752]
(In reply to Gordon Lack from comment #26) > Do we need a prod on the libexiv2 package as well to indicate that it needs > an update to fix the cause of the crash? (The fix for gwenview to handle > such crashes better is welcome, but not sufficient). > > I can't see any bug report with libexiv2 as the product. There is https://bugs.launchpad.net/ubuntu/+source/exiv2/+bug/1942799 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to exiv2 in Ubuntu. https://bugs.launchpad.net/bugs/1941752 Title: Regression: exiv2 0.27.3-3ubuntu1.5 makes Gwenview crash when opening images exported by darktable Status in Gwenview: Fix Released Status in exiv2 package in Ubuntu: Confirmed Status in gwenview package in Ubuntu: Confirmed Bug description: Since the recent security update of exiv2, Gwenview crashes when trying to open image files that got exported by darktable. Steps to reproduce: * Make a test installation of Kubuntu 21.04 in VirtualBox * Install all updates * Install darktable * Copy one of the images in /usr/share/wallpapers (or any other image) to your home directory and open it with darktable * Within darktable, export a copy of the image (no need to do any actual modifications) * Try to open that copy with Gwenview. Gwenview will crash. I'm attaching a crash report hinting that this is related to exiv2. Temporary workaround: If I downgrade libexiv2-27 to 0.27.3-3ubuntu1.4, Gwenview doesn't crash, so it seems the crash is related to changes in 0.27.3-3ubuntu1.5. I don't know if the underlying cause is actually some bug in exiv2, Gwenview or darktable. Kind regards, Jan ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: libexiv2-27 0.27.3-3ubuntu1.5 ProcVersionSignature: Ubuntu 5.11.0-31.33-generic 5.11.22 Uname: Linux 5.11.0-31-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: KDE Date: Thu Aug 26 15:16:47 2021 InstallationDate: Installed on 2021-08-26 (0 days ago) InstallationMedia: Kubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) SourcePackage: exiv2 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gwenview/+bug/1941752/+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 1941752]
This is now fixed both upstream in libexiv2 0.27.5 with https://github.com/Exiv2/exiv2/pull/1918/commits/8a1e949bff482f74599f60b8ab518442036b1834 and in Gwenview for version 21.12.1 with https://invent.kde.org/graphics/gwenview/-/commit/91fcbe9c63c17bc20dbb3dd90e0451997f1c78a6 by Lukáš Karas. The fix in Gwenview has not been merged into master and will not be present for example in future Gwenview 22.04 because we expect packagers to have shipped the fixed libexiv2 versions by the time Gwenview 22.04 is released. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to exiv2 in Ubuntu. https://bugs.launchpad.net/bugs/1941752 Title: Regression: exiv2 0.27.3-3ubuntu1.5 makes Gwenview crash when opening images exported by darktable Status in Gwenview: Fix Released Status in exiv2 package in Ubuntu: Confirmed Status in gwenview package in Ubuntu: Confirmed Bug description: Since the recent security update of exiv2, Gwenview crashes when trying to open image files that got exported by darktable. Steps to reproduce: * Make a test installation of Kubuntu 21.04 in VirtualBox * Install all updates * Install darktable * Copy one of the images in /usr/share/wallpapers (or any other image) to your home directory and open it with darktable * Within darktable, export a copy of the image (no need to do any actual modifications) * Try to open that copy with Gwenview. Gwenview will crash. I'm attaching a crash report hinting that this is related to exiv2. Temporary workaround: If I downgrade libexiv2-27 to 0.27.3-3ubuntu1.4, Gwenview doesn't crash, so it seems the crash is related to changes in 0.27.3-3ubuntu1.5. I don't know if the underlying cause is actually some bug in exiv2, Gwenview or darktable. Kind regards, Jan ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: libexiv2-27 0.27.3-3ubuntu1.5 ProcVersionSignature: Ubuntu 5.11.0-31.33-generic 5.11.22 Uname: Linux 5.11.0-31-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: KDE Date: Thu Aug 26 15:16:47 2021 InstallationDate: Installed on 2021-08-26 (0 days ago) InstallationMedia: Kubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) SourcePackage: exiv2 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gwenview/+bug/1941752/+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 1954943] [NEW] ubuntu-bug crashed while reporting an audio issue
Public bug reported: When trying to report an audio issue using "ubuntu-bug", pulse audio crashed. The original audio bug I was trying to report and was not able to was: All audio skips the first 2 seconds AFTER the video starts or continues. This happens in YOUTUBE, VLC etc, in all videos that have audio, the audio skips the first two seconds. If I rewind the video to the beginning, the audio starts correctly as expected. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu3.13 ProcVersionSignature: Ubuntu 5.11.0-43.47~20.04.2-generic 5.11.22 Uname: Linux 5.11.0-43-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: steve 1093 F pulseaudio /dev/snd/controlC1: steve 1093 F pulseaudio /dev/snd/pcmC1D3p: steve 1093 F...m pulseaudio CasperMD5CheckResult: skip Date: Wed Dec 15 13:00:24 2021 InstallationDate: Installed on 2021-05-11 (218 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: pulseaudio Symptom: audio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/18/2012 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: FB dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: 970A-DS3 dmi.board.vendor: AMD Corporation dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrFB:bd10/18/2012:br4.6:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:skuTobefilledbyO.E.M.:rvnAMDCorporation:rn970A-DS3:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: To be filled by O.E.M. dmi.product.sku: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. ** Affects: pulseaudio (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1954943 Title: ubuntu-bug crashed while reporting an audio issue Status in pulseaudio package in Ubuntu: New Bug description: When trying to report an audio issue using "ubuntu-bug", pulse audio crashed. The original audio bug I was trying to report and was not able to was: All audio skips the first 2 seconds AFTER the video starts or continues. This happens in YOUTUBE, VLC etc, in all videos that have audio, the audio skips the first two seconds. If I rewind the video to the beginning, the audio starts correctly as expected. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu3.13 ProcVersionSignature: Ubuntu 5.11.0-43.47~20.04.2-generic 5.11.22 Uname: Linux 5.11.0-43-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: steve 1093 F pulseaudio /dev/snd/controlC1: steve 1093 F pulseaudio /dev/snd/pcmC1D3p: steve 1093 F...m pulseaudio CasperMD5CheckResult: skip Date: Wed Dec 15 13:00:24 2021 InstallationDate: Installed on 2021-05-11 (218 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: pulseaudio Symptom: audio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/18/2012 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: FB dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: 970A-DS3 dmi.board.vendor: AMD Corporation dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrFB:bd10/18/2012:br4.6:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:skuTobefilledbyO.E.M.:rvnAMDCorporation:rn970A-DS3:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To be filled by O.E.M. d
[Touch-packages] [Bug 1892798] Re: systemd package missing resolvconf(8) compatibility symlink, and a Provides: resolvconf
I think he meant to post this on https://bugs.launchpad.net/ubuntu/+source/wireguard/+bug/1950317 -- 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/1892798 Title: systemd package missing resolvconf(8) compatibility symlink, and a Provides: resolvconf Status in systemd package in Ubuntu: Won't Fix Status in wireguard package in Ubuntu: Confirmed Status in systemd package in Debian: Incomplete Bug description: By default Ubuntu now uses systemd to manage the nameservers in resolv.conf, so resolvconf and openresolv seem to be redundant. However, it appears that systemd's resolvectl is compatable with resolvconf style commands if symlinked as resolvconf. I'm not really sure how deb packaging works, but if it possible to check for the resolvconf command, and if not found just symlink /usr/bin/resolvectl to /usr/sbin/resolvconf then wg-quick will work without additional packages. See https://manpages.ubuntu.com/manpages/focal/man1/resolvectl.1#compatibility%20with%20resolvconf(8) for more info. Apologies if there is a better place to direct this info. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1892798/+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 1941752]
Mee too! Can't no longer view my photos saved by darktable... Gwenview 21.08.2 Kubuntu 21.10 KDE Frameworks Version 5.87.0 Qt 5.15.2 libexiv2-27 0.27.3-3ubuntu4 $ gwenview dsc_0013_jf.jpg org.kde.kdegraphics.gwenview.lib: Unresolved mime type "image/x-mng" org.kde.kdegraphics.gwenview.lib: Unresolved raw mime type "image/x-nikon-nrw" org.kde.kdegraphics.gwenview.lib: Unresolved raw mime type "image/x-samsung-srw" terminate called after throwing an instance of 'std::out_of_range' what(): basic_string::at: __n (which is 19) >= this->size() (which is 19) KCrash: crashing... crashRecursionCounter = 2 KCrash: Application Name = gwenview path = /usr/bin pid = 235591 KCrash: Arguments: /usr/bin/gwenview dsc_0013_jf.jpg KCrash: Attempting to start /usr/lib/x86_64-linux-gnu/libexec/drkonqi [1]+ Angehalten gwenview dsc_0013_jf.jpg Application: Gwenview (gwenview), signal: Aborted [KCrash Handler] #4 __pthread_kill_implementation (no_tid=0, signo=6, threadid=140084165356608) at pthread_kill.c:44 #5 __pthread_kill_internal (signo=6, threadid=140084165356608) at pthread_kill.c:80 #6 __GI___pthread_kill (threadid=140084165356608, signo=signo@entry=6) at pthread_kill.c:91 #7 0x7f67e85db476 in __GI_raise (sig=sig@entry=6) at ../sysdeps/posix/raise.c:26 #8 0x7f67e85c17b7 in __GI_abort () at abort.c:79 #9 0x7f67e885ea31 in ?? () from /lib/x86_64-linux-gnu/libstdc++.so.6 #10 0x7f67e886a4ec in ?? () from /lib/x86_64-linux-gnu/libstdc++.so.6 #11 0x7f67e886a557 in std::terminate() () from /lib/x86_64-linux-gnu/libstdc++.so.6 #12 0x7f67e886a7f9 in __cxa_throw () from /lib/x86_64-linux-gnu/libstdc++.so.6 #13 0x7f67e8861448 in ?? () from /lib/x86_64-linux-gnu/libstdc++.so.6 #14 0x7f67e83967fd in ?? () from /lib/x86_64-linux-gnu/libexiv2.so.27 #15 0x7f67e833612d in Exiv2::Xmpdatum::write(std::ostream&, Exiv2::ExifData const*) const () from /lib/x86_64-linux-gnu/libexiv2.so.27 #16 0x7f67ea8fa6d6 in Gwenview::ImageMetaInfoModel::setExiv2Image(Exiv2::Image const*) () from /lib/x86_64-linux-gnu/libgwenviewlib.so.5 #17 0x7f67ea8bfcd0 in Gwenview::Document::setExiv2Image(std::unique_ptr >) () from /lib/x86_64-linux-gnu/libgwenviewlib.so.5 #18 0x7f67ea8cacab in ?? () from /lib/x86_64-linux-gnu/libgwenviewlib.so.5 #19 0x7f67e8cc6a53 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #20 0x7f67e8aacec5 in QFutureWatcherBase::event(QEvent*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #21 0x7f67e99f66b3 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #22 0x7f67e8c8f16a in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #23 0x7f67e8c92257 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #24 0x7f67e8ce8ef7 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #25 0x7f67e63708bb in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #26 0x7f67e63c3f08 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #27 0x7f67e636e003 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #28 0x7f67e8ce8548 in QEventDispatcherGlib::processEvents(QFlags) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #29 0x7f67e8c8da9b in QEventLoop::exec(QFlags) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #30 0x7f67e8c96024 in QCoreApplication::exec() () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #31 0x5646e78c5553 in ?? () #32 0x7f67e85c2fd0 in __libc_start_call_main (main=main@entry=0x5646e78c4fe0, argc=argc@entry=2, argv=argv@entry=0x7ffcec921388) at ../sysdeps/nptl/libc_start_call_main.h:58 #33 0x7f67e85c307d in __libc_start_main_impl (main=0x5646e78c4fe0, argc=2, argv=0x7ffcec921388, init=, fini=, rtld_fini=, stack_end=0x7ffcec921378) at ../csu/libc-start.c:409 #34 0x5646e78c5b75 in ?? () [Inferior 1 (process 235591) detached] -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to exiv2 in Ubuntu. https://bugs.launchpad.net/bugs/1941752 Title: Regression: exiv2 0.27.3-3ubuntu1.5 makes Gwenview crash when opening images exported by darktable Status in Gwenview: Unknown Status in exiv2 package in Ubuntu: Confirmed Status in gwenview package in Ubuntu: Confirmed Bug description: Since the recent security update of exiv2, Gwenview crashes when trying to open image files that got exported by darktable. Steps to reproduce: * Make a test installation of Kubuntu 21.04 in VirtualBox * Install all updates * Install darktable * Copy one of the images in /usr/share/wallpapers (or any other image) to your home directory and open it with darktable * Within darktable, export a copy of the image (no need to do any actual modifications)
[Touch-packages] [Bug 1900008] Re: Sessions of screen does not keep running in background
Hi, I can confirm that this does not happen in plain Ubuntu Desktop 20.04. I winder why in KDE Neon 20.04 does happens since is based in Ubuntu 20.04... I will have to report to them. Thanks! -- 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/198 Title: Sessions of screen does not keep running in background Status in screen package in Ubuntu: Incomplete Status in systemd package in Ubuntu: Incomplete Bug description: In a new fresh installed 20.04, when I use screen command and close the terminal (not closing screen sesion), then I can't recover it with screen -x, since does not exist. I can only recover screen sesion if the original terminal running screen is not being closed. For some reason, this is closing screen session of that user: Oct 15 13:32:45 pc-caja2 systemd[1]: session-66.scope: Succeeded. Oct 15 13:32:45 pc-caja2 systemd[1]: Stopped Session 66 of user usuario. This does not happen in an upgraded system from 18.04 to 20.04. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/screen/+bug/198/+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 1900008] Re: Sessions of screen does not keep running in background
Ok, today I have some time, I am installing Ubuntu Desktop 20.04 in VirtualBox. Meanwhile, the only way to keep a session alive (in KDE Neon 20.04) is by using: systemd-run --scope --user screen Will keep posted once I've tested in the Ubuntu installation. -- 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/198 Title: Sessions of screen does not keep running in background Status in screen package in Ubuntu: Incomplete Status in systemd package in Ubuntu: Incomplete Bug description: In a new fresh installed 20.04, when I use screen command and close the terminal (not closing screen sesion), then I can't recover it with screen -x, since does not exist. I can only recover screen sesion if the original terminal running screen is not being closed. For some reason, this is closing screen session of that user: Oct 15 13:32:45 pc-caja2 systemd[1]: session-66.scope: Succeeded. Oct 15 13:32:45 pc-caja2 systemd[1]: Stopped Session 66 of user usuario. This does not happen in an upgraded system from 18.04 to 20.04. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/screen/+bug/198/+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 1900008] Re: Sessions of screen does not keep running in background
Hi, I did not forgot this, but I reallt didn' t have time to test in a VM. But, I've installed a new machine with same OS (KDE Neon 20.04) and the same thing happens. So, like I said before, this does not happen don upgraded machine from 18.04 to 20.04. I will try to test in VM with Gnome desktop (and Ubuntu 20.04) as soon as I can. -- 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/198 Title: Sessions of screen does not keep running in background Status in screen package in Ubuntu: New Status in systemd package in Ubuntu: New Bug description: In a new fresh installed 20.04, when I use screen command and close the terminal (not closing screen sesion), then I can't recover it with screen -x, since does not exist. I can only recover screen sesion if the original terminal running screen is not being closed. For some reason, this is closing screen session of that user: Oct 15 13:32:45 pc-caja2 systemd[1]: session-66.scope: Succeeded. Oct 15 13:32:45 pc-caja2 systemd[1]: Stopped Session 66 of user usuario. This does not happen in an upgraded system from 18.04 to 20.04. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/screen/+bug/198/+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 1928996] [NEW] [X58A-UD3R, Nvidia GPU 84 HDMI/DP, Digital Out, HDMI] No sound at all after resuming from suspend
Public bug reported: Sound works fine after an initial boot up, but fails after resuming from a suspend. Going to the "Sound" section in the Settings app, I no longer see the HDMI device presented as an output option when this occurs. I suspect this is due to issues with pulseaudio. At least, running `pulseaudio -k && pulseaudio --start`, then restarting apps seems to fix the issue. In particular I've found that the pulseaudio systemd service has failed after resuming from suspend. After scanning through journalctl, there are a few suspect sections. I've attached the logs in their entirety, and an abbreviated log with only sections that I found interesting. I cannot be sure which are at fault, but hopefully it helps narrow the search. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-73.82-generic 5.4.106 Uname: Linux 5.4.0-73-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.17 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: skainswo 2282708 F pulseaudio /dev/snd/controlC0: skainswo 2282708 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed May 19 16:08:41 2021 InstallationDate: Installed on 2020-05-15 (369 days ago) InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 (20200203.1) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/home/username/.nix-profile/bin/zsh SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:NVidia failed Symptom_Card: GP106 High Definition Audio Controller - HDA NVidia Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: skainswo 2282708 F pulseaudio /dev/snd/controlC0: skainswo 2282708 F pulseaudio Symptom_Jack: Digital Out, HDMI Symptom_Type: No sound at all Title: [X58A-UD3R, Nvidia GPU 84 HDMI/DP, Digital Out, HDMI] No sound at all UpgradeStatus: Upgraded to focal on 2020-08-08 (284 days ago) dmi.bios.date: 04/20/2010 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: FA dmi.board.name: X58A-UD3R dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrFA:bd04/20/2010:svnGigabyteTechnologyCo.,Ltd.:pnX58A-UD3R:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnX58A-UD3R:rvr:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: X58A-UD3R dmi.sys.vendor: Gigabyte Technology Co., Ltd. ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal third-party-packages ** Attachment added: "pulseaudio-logs.zip" https://bugs.launchpad.net/bugs/1928996/+attachment/5498825/+files/pulseaudio-logs.zip -- 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/1928996 Title: [X58A-UD3R, Nvidia GPU 84 HDMI/DP, Digital Out, HDMI] No sound at all after resuming from suspend Status in alsa-driver package in Ubuntu: New Bug description: Sound works fine after an initial boot up, but fails after resuming from a suspend. Going to the "Sound" section in the Settings app, I no longer see the HDMI device presented as an output option when this occurs. I suspect this is due to issues with pulseaudio. At least, running `pulseaudio -k && pulseaudio --start`, then restarting apps seems to fix the issue. In particular I've found that the pulseaudio systemd service has failed after resuming from suspend. After scanning through journalctl, there are a few suspect sections. I've attached the logs in their entirety, and an abbreviated log with only sections that I found interesting. I cannot be sure which are at fault, but hopefully it helps narrow the search. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-73.82-generic 5.4.106 Uname: Linux 5.4.0-73-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.17 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: skainswo 2282708 F pulseaudio /dev/snd/controlC0: skainswo 2282708 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed May 19 16:08:41 2021 InstallationDate: Installed on 2020-05-15 (369 days ago) InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 (20200203.1) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/home/username/.nix-profile/
[Touch-packages] [Bug 1576559] Re: Refused to switch profile to headset_head_unit: Not connected
Same issue here. As many others here, I need to use the mic at work's meetings and I needed to spent extra money on a wired headset because of this bug made my airpods useless for the task. elementary OS 5.1.7 Hera, Built on Ubuntu 18.04.4 LTS. Linux 4.15.0-135-generic. $pactl list cards Card #0 Name: alsa_card.pci-_00_1b.0 Driver: module-alsa-card.c Owner Module: 7 Properties: alsa.card = "0" alsa.card_name = "HDA Intel" alsa.long_card_name = "HDA Intel at 0xf000 irq 26" alsa.driver_name = "snd_hda_intel" device.bus_path = "pci-:00:1b.0" sysfs.path = "/devices/pci:00/:00:1b.0/sound/card0" device.bus = "pci" device.vendor.id = "8086" device.vendor.name = "Intel Corporation" device.product.id = "27d8" device.product.name = "NM10/ICH7 Family High Definition Audio Controller" device.form_factor = "internal" device.string = "0" device.description = "Built-in Audio" module-udev-detect.discovered = "1" device.icon_name = "audio-card-pci" Profiles: input:analog-stereo: Analog Stereo Input (sinks: 0, sources: 1, priority: 60, available: no) output:analog-stereo: Analog Stereo Output (sinks: 1, sources: 0, priority: 6000, available: yes) output:analog-stereo+input:analog-stereo: Analog Stereo Duplex (sinks: 1, sources: 1, priority: 6060, available: yes) output:iec958-stereo: Digital Stereo (IEC958) Output (sinks: 1, sources: 0, priority: 5500, available: yes) output:iec958-stereo+input:analog-stereo: Digital Stereo (IEC958) Output + Analog Stereo Input (sinks: 1, sources: 1, priority: 5560, available: yes) off: Off (sinks: 0, sources: 0, priority: 0, available: yes) Active Profile: output:analog-stereo+input:analog-stereo Ports: analog-input-mic: Microphone (priority: 8700, latency offset: 0 usec, not available) Properties: device.icon_name = "audio-input-microphone" Part of profile(s): input:analog-stereo, output:analog-stereo+input:analog-stereo, output:iec958-stereo+input:analog-stereo analog-output-speaker: Speakers (priority: 1, latency offset: 0 usec) Properties: device.icon_name = "audio-speakers" Part of profile(s): output:analog-stereo, output:analog-stereo+input:analog-stereo analog-output-headphones: Headphones (priority: 9000, latency offset: 0 usec, not available) Properties: device.icon_name = "audio-headphones" Part of profile(s): output:analog-stereo, output:analog-stereo+input:analog-stereo iec958-stereo-output: Digital Output (S/PDIF) (priority: 0, latency offset: 0 usec) Part of profile(s): output:iec958-stereo, output:iec958-stereo+input:analog-stereo Card #7 Name: bluez_card.AC_80_1C_01_34_B0 Driver: module-bluez5-device.c Owner Module: 33 Properties: device.description = "Baseus Encok W04 Pro" device.string = "AC:80:1C:01:34:B0" device.api = "bluez" device.class = "sound" device.bus = "bluetooth" device.form_factor = "headset" bluez.path = "/org/bluez/hci0/dev_AC_80_1C_01_34_B0" bluez.class = "0x240404" bluez.alias = "Baseus Encok W04 Pro" device.icon_name = "audio-headset-bluetooth" device.intended_roles = "phone" Profiles: a2dp_sink: High Fidelity Playback (A2DP Sink) (sinks: 1, sources: 0, priority: 40, available: yes) headset_head_unit: Headset Head Unit (HSP/HFP) (sinks: 1, sources: 1, priority: 30, available: no) off: Off (sinks: 0, sources: 0, priority: 0, available: yes) Active Profile: off Ports: headset-output: Headset (priority: 0, latency offset: 0 usec) Part of profile(s): a2dp_sink, headset_head_unit headset-input: Headset (priority: 0, latency offset: 0 usec, not available) Part of profile(s): headset_head_unit $ bluetoothctl [NEW] Controller 00:1A:7D:DA:7
[Touch-packages] [Bug 1900008] Re: Sessions of screen does not keep running in background
Hi, Sure, I will let you know here the results. Also, I will try to modify login.conf as suggested in the link before doing any test. But anyways, is this was not affected in my other upgrades installations, I don't think that is the problem here, but won't hurt me trying. -- 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/198 Title: Sessions of screen does not keep running in background Status in screen package in Ubuntu: New Status in systemd package in Ubuntu: New Bug description: In a new fresh installed 20.04, when I use screen command and close the terminal (not closing screen sesion), then I can't recover it with screen -x, since does not exist. I can only recover screen sesion if the original terminal running screen is not being closed. For some reason, this is closing screen session of that user: Oct 15 13:32:45 pc-caja2 systemd[1]: session-66.scope: Succeeded. Oct 15 13:32:45 pc-caja2 systemd[1]: Stopped Session 66 of user usuario. This does not happen in an upgraded system from 18.04 to 20.04. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/screen/+bug/198/+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 1900008] Re: Sessions of screen does not keep running in background
Well, is a really close (or same) behaviur like exposed in https://bugs.debian.org/825394 (shared by Axel). Screen version 4.8.0-1. The system (or either systemd) has modifications at all, so is really weird. -- 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/198 Title: Sessions of screen does not keep running in background Status in screen package in Ubuntu: New Status in systemd package in Ubuntu: New Bug description: In a new fresh installed 20.04, when I use screen command and close the terminal (not closing screen sesion), then I can't recover it with screen -x, since does not exist. I can only recover screen sesion if the original terminal running screen is not being closed. For some reason, this is closing screen session of that user: Oct 15 13:32:45 pc-caja2 systemd[1]: session-66.scope: Succeeded. Oct 15 13:32:45 pc-caja2 systemd[1]: Stopped Session 66 of user usuario. This does not happen in an upgraded system from 18.04 to 20.04. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/screen/+bug/198/+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 1900008] Re: Sessions of screen does not keep running in background
Hi, first of all I don' t know why I did' t receive any notification of this bug report. Second, and to clarify, I being using screen command since 2000 (which Is my beginning as Linux admin). This being said, I know how it works. All my other Ubuntu upgrades from 18.04 to 20.04, this does not happen (I do not have time yet to test it in a new Ubuntu 20.04, maybe later in a VM). Simple test: open screen. Just close you terminal (not exit...). When I want to recover screen session with screen -x, is gone, none, nothing... Btw, I only tested this KDE Neon, which is Ubuntu 20.04 based and I think has nothing to do that is KDE based, since screen has nothing to do with it. -- 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/198 Title: Sessions of screen does not keep running in background Status in screen package in Ubuntu: New Status in systemd package in Ubuntu: New Bug description: In a new fresh installed 20.04, when I use screen command and close the terminal (not closing screen sesion), then I can't recover it with screen -x, since does not exist. I can only recover screen sesion if the original terminal running screen is not being closed. For some reason, this is closing screen session of that user: Oct 15 13:32:45 pc-caja2 systemd[1]: session-66.scope: Succeeded. Oct 15 13:32:45 pc-caja2 systemd[1]: Stopped Session 66 of user usuario. This does not happen in an upgraded system from 18.04 to 20.04. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/screen/+bug/198/+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 1903382] Re: unable to add online account for google, flickr, microsoft, facebook
** Also affects: webkit2gtk (Ubuntu)
Importance: Undecided
Status: New
** No longer affects: gnome-control-center (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gnome-online-accounts in
Ubuntu.
https://bugs.launchpad.net/bugs/1903382
Title:
unable to add online account for google, flickr, microsoft, facebook
Status in gnome-online-accounts package in Ubuntu:
New
Status in webkit2gtk package in Ubuntu:
New
Bug description:
Fresh install of groovy. When I try to add Google, Flickr or Microsoft
account, the loading window stays grey forever. When trying Facebook,
i can see the loaded page for a second then switches to grey also.
gnome-online-accounts:
Telepítve: 3.37.90-1ubuntu1
Jelölt:3.37.90-1ubuntu1
I see these messages in journal:
10:03:14 kernel: traps: WebKitWebProces[14044] trap int3 ip:7f510e1933cb
sp:7ffd7c266ba0 error:0 in libglib-2.0.so.0.6600.1[7f510e153000+8b000]
10:03:14 WebKitWebProces:backtrace from your debugger if you break on the
gdk_x_error() function.)
10:03:14 WebKitWebProces:backtrace from your debugger if you break on the
gdk_x_error() function.)
10:03:14 WebKitWebProces:variable to change this behavior. You can then
get a meaningful
10:03:14 WebKitWebProces:To debug your program, run it with the
GDK_SYNCHRONIZE environment
10:03:14 WebKitWebProces:that is, you will receive the error a while
after causing it.
10:03:14 WebKitWebProces: (Note to programmers: normally, X errors are
reported asynchronously;
10:03:14 WebKitWebProces: (Details: serial 221 error_code 2 request_code
152 (GLX) minor_code 34)
10:03:14 WebKitWebProces: The error was 'BadValue (integer parameter out of
range for operation)'.
10:03:14 WebKitWebProces: This probably reflects a bug in the program.
10:03:14 WebKitWebProces: (WebKitWebProcess:2): Gdk-ERROR **: 10:03:14.587:
The program 'WebKitWebProcess' received an X Window System error.
10:03:14 WebKitWebProces: libGL error: failed to load driver: swrast
10:03:14 WebKitWebProces: libGL error: MESA-LOADER: failed to open swrast
(search paths /usr/lib/x86_64-linux-gnu/dri:\$${ORIGIN}/dri:/usr/lib/dri)
10:03:14 WebKitWebProces: libGL error: failed to load driver: radeonsi
10:03:14 WebKitWebProces: libGL error: MESA-LOADER: failed to open radeonsi
(search paths /usr/lib/x86_64-linux-gnu/dri:\$${ORIGIN}/dri:/usr/lib/dri)
10:03:14 WebKitWebProces: libGL error: failed to load driver: radeonsi
10:03:14 WebKitWebProces: libGL error: MESA-LOADER: failed to open radeonsi
(search paths /usr/lib/x86_64-linux-gnu/dri:\$${ORIGIN}/dri:/usr/lib/dri)
10:03:02 kernel: traps: eadedCompositor[14032] trap int3 ip:7f38f64183cb
sp:7f387c5fde10 error:0 in libglib-2.0.so.0.6600.1[7f38f63d8000+8b000]
10:03:02 WebKitWebProces:backtrace from your debugger if you break on the
gdk_x_error() function.)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-online-accounts/+bug/1903382/+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 1903382] [NEW] unable to add online account for google, flickr, microsoft, facebook
Public bug reported:
Fresh install of groovy. When I try to add Google, Flickr or Microsoft
account, the loading window stays grey forever. When trying Facebook, i
can see the loaded page for a second then switches to grey also.
gnome-online-accounts:
Telepítve: 3.37.90-1ubuntu1
Jelölt:3.37.90-1ubuntu1
I see these messages in journal:
10:03:14 kernel: traps: WebKitWebProces[14044] trap int3 ip:7f510e1933cb
sp:7ffd7c266ba0 error:0 in libglib-2.0.so.0.6600.1[7f510e153000+8b000]
10:03:14 WebKitWebProces:backtrace from your debugger if you break on the
gdk_x_error() function.)
10:03:14 WebKitWebProces:backtrace from your debugger if you break on the
gdk_x_error() function.)
10:03:14 WebKitWebProces:variable to change this behavior. You can then get
a meaningful
10:03:14 WebKitWebProces:To debug your program, run it with the
GDK_SYNCHRONIZE environment
10:03:14 WebKitWebProces:that is, you will receive the error a while after
causing it.
10:03:14 WebKitWebProces: (Note to programmers: normally, X errors are
reported asynchronously;
10:03:14 WebKitWebProces: (Details: serial 221 error_code 2 request_code 152
(GLX) minor_code 34)
10:03:14 WebKitWebProces: The error was 'BadValue (integer parameter out of
range for operation)'.
10:03:14 WebKitWebProces: This probably reflects a bug in the program.
10:03:14 WebKitWebProces: (WebKitWebProcess:2): Gdk-ERROR **: 10:03:14.587: The
program 'WebKitWebProcess' received an X Window System error.
10:03:14 WebKitWebProces: libGL error: failed to load driver: swrast
10:03:14 WebKitWebProces: libGL error: MESA-LOADER: failed to open swrast
(search paths /usr/lib/x86_64-linux-gnu/dri:\$${ORIGIN}/dri:/usr/lib/dri)
10:03:14 WebKitWebProces: libGL error: failed to load driver: radeonsi
10:03:14 WebKitWebProces: libGL error: MESA-LOADER: failed to open radeonsi
(search paths /usr/lib/x86_64-linux-gnu/dri:\$${ORIGIN}/dri:/usr/lib/dri)
10:03:14 WebKitWebProces: libGL error: failed to load driver: radeonsi
10:03:14 WebKitWebProces: libGL error: MESA-LOADER: failed to open radeonsi
(search paths /usr/lib/x86_64-linux-gnu/dri:\$${ORIGIN}/dri:/usr/lib/dri)
10:03:02 kernel: traps: eadedCompositor[14032] trap int3 ip:7f38f64183cb
sp:7f387c5fde10 error:0 in libglib-2.0.so.0.6600.1[7f38f63d8000+8b000]
10:03:02 WebKitWebProces:backtrace from your debugger if you break on the
gdk_x_error() function.)
** Affects: gnome-control-center (Ubuntu)
Importance: Undecided
Status: New
** Affects: gnome-online-accounts (Ubuntu)
Importance: Undecided
Status: New
** Also affects: gnome-online-accounts (Ubuntu)
Importance: Undecided
Status: New
** Summary changed:
- nable to add online account for google, flickr, microsoft, facebook
+ unable to add online account for google, flickr, microsoft, facebook
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gnome-online-accounts in
Ubuntu.
https://bugs.launchpad.net/bugs/1903382
Title:
unable to add online account for google, flickr, microsoft, facebook
Status in gnome-control-center package in Ubuntu:
New
Status in gnome-online-accounts package in Ubuntu:
New
Bug description:
Fresh install of groovy. When I try to add Google, Flickr or Microsoft
account, the loading window stays grey forever. When trying Facebook,
i can see the loaded page for a second then switches to grey also.
gnome-online-accounts:
Telepítve: 3.37.90-1ubuntu1
Jelölt:3.37.90-1ubuntu1
I see these messages in journal:
10:03:14 kernel: traps: WebKitWebProces[14044] trap int3 ip:7f510e1933cb
sp:7ffd7c266ba0 error:0 in libglib-2.0.so.0.6600.1[7f510e153000+8b000]
10:03:14 WebKitWebProces:backtrace from your debugger if you break on the
gdk_x_error() function.)
10:03:14 WebKitWebProces:backtrace from your debugger if you break on the
gdk_x_error() function.)
10:03:14 WebKitWebProces:variable to change this behavior. You can then
get a meaningful
10:03:14 WebKitWebProces:To debug your program, run it with the
GDK_SYNCHRONIZE environment
10:03:14 WebKitWebProces:that is, you will receive the error a while
after causing it.
10:03:14 WebKitWebProces: (Note to programmers: normally, X errors are
reported asynchronously;
10:03:14 WebKitWebProces: (Details: serial 221 error_code 2 request_code
152 (GLX) minor_code 34)
10:03:14 WebKitWebProces: The error was 'BadValue (integer parameter out of
range for operation)'.
10:03:14 WebKitWebProces: This probably reflects a bug in the program.
10:03:14 WebKitWebProces: (WebKitWebProcess:2): Gdk-ERROR **: 10:03:14.587:
The program 'WebKitWebProcess' received an X Window System error.
10:03:14 WebKitWebProces: libGL error: failed to load driver: swrast
10:03:14 WebKitWebProces: libGL error: MESA-LOADER: failed to open swrast
(search paths /usr/lib/x86_64-linux-gnu/d
[Touch-packages] [Bug 214786] Re: Apple USB ISO keyboard has incorrectly swapped keys
After posting, I tried https://bugs.launchpad.net/ubuntu/+source/linux/+bug/214786/comments/78 and it worked for me on a Spanish USB apple keyboard. Currently I have my laptop's and the USB Apple keyboard working correctly _and_ simultaneously Just my .2 cents -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xkeyboard-config in Ubuntu. https://bugs.launchpad.net/bugs/214786 Title: Apple USB ISO keyboard has incorrectly swapped keys Status in Mactel Support: Confirmed Status in linux package in Ubuntu: Fix Released Status in xkeyboard-config package in Ubuntu: Confirmed Bug description: Since upgrading kernel to version 2.6.24-12.22 two keys are now swapped on my Apple USB aluminium keyboard with danish layout. Now the keys "<" and "½" are swapped and no longer matches the actual print on the keycaps. The error is isolated to the following commit: http://kernel.ubuntu.com/git?p=ubuntu/ubuntu- hardy.git;a=commitdiff;h=efb3031b446d441dca5b10619503ac0bba7f9748 This commit introduced a key swapping for all "ISO" type Apple keyboards. In my case this swapping is incorrect, and generally it seems like a very bad idea to perform hard coded locale specific key mapping in kernel space as this is also done several places in user space. The included patch reverts the behavior to the default that matches the keycap printing. To manage notifications about this bug go to: https://bugs.launchpad.net/mactel-support/+bug/214786/+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 214786] Re: Apple USB ISO keyboard has incorrectly swapped keys
I'm having this issue with a Spanish USB Mac keyboard. Is it really so difficult to detect when you have a Mac keyboard connected and/or disconnected? Can't anything be done with hotplug, udev, etc. ? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xkeyboard-config in Ubuntu. https://bugs.launchpad.net/bugs/214786 Title: Apple USB ISO keyboard has incorrectly swapped keys Status in Mactel Support: Confirmed Status in linux package in Ubuntu: Fix Released Status in xkeyboard-config package in Ubuntu: Confirmed Bug description: Since upgrading kernel to version 2.6.24-12.22 two keys are now swapped on my Apple USB aluminium keyboard with danish layout. Now the keys "<" and "½" are swapped and no longer matches the actual print on the keycaps. The error is isolated to the following commit: http://kernel.ubuntu.com/git?p=ubuntu/ubuntu- hardy.git;a=commitdiff;h=efb3031b446d441dca5b10619503ac0bba7f9748 This commit introduced a key swapping for all "ISO" type Apple keyboards. In my case this swapping is incorrect, and generally it seems like a very bad idea to perform hard coded locale specific key mapping in kernel space as this is also done several places in user space. The included patch reverts the behavior to the default that matches the keycap printing. To manage notifications about this bug go to: https://bugs.launchpad.net/mactel-support/+bug/214786/+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 1890716] Re: misidentifies .html file as Perl script when it contains JavaScript "use strict"
@Kai Kasurinen >probably fixed on shared-mime-info 2.0: >https://gitlab.freedesktop.org/xdg/shared-mime-info/-/commit/18bb7cfc6c43d710ecf60339b5dd9bd19c297cdf Yeah, well. It's if they only used the same database. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to shared-mime-info in Ubuntu. https://bugs.launchpad.net/bugs/1890716 Title: misidentifies .html file as Perl script when it contains JavaScript "use strict" Status in shared-mime-info: Unknown Status in kde-cli-tools package in Ubuntu: New Status in shared-mime-info package in Ubuntu: Fix Committed Status in shared-mime-info package in Debian: Confirmed Bug description: For .html files `xdg-mime` reports wrong type. The culprit is the `"use strict"` phrase which is used in JavaScript. It should not mistake .html files for anything else except of text/html ! STEPS TO REPRODUCE: Run the following step by step in any folder: 1. $ echo "\"use strict\"" > index.html 2. $ xdg-mime query filetype index.html # -> application/x-perl - this should be text/html! Platform: Ubuntu 20.04.1 LTS (Focal Fossa)" Linux version 5.4.0-42-generic (buildd@lgw01-amd64-038) (gcc version 9.3.0 (Ubuntu 9.3.0-10ubuntu2)) xdg-utils: 1.1.3-2ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/shared-mime-info/+bug/1890716/+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 1890716] Re: misidentifies .html file as Perl script when it contains JavaScript "use strict"
If you wrap string in the proper tags you will get the same result, but
with different offset (28 chars):
tee "index.html" <
`printf "x"%.0s {1..228}`
use strict
eol # -> text/html
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to shared-mime-info in
Ubuntu.
https://bugs.launchpad.net/bugs/1890716
Title:
misidentifies .html file as Perl script when it contains JavaScript
"use strict"
Status in shared-mime-info:
Unknown
Status in kde-cli-tools package in Ubuntu:
New
Status in shared-mime-info package in Ubuntu:
Fix Committed
Status in shared-mime-info package in Debian:
Confirmed
Bug description:
For .html files `xdg-mime` reports wrong type. The culprit is the
`"use strict"` phrase which is used in JavaScript. It should not
mistake .html files for anything else except of text/html !
STEPS TO REPRODUCE:
Run the following step by step in any folder:
1. $ echo "\"use strict\"" > index.html
2. $ xdg-mime query filetype index.html # -> application/x-perl - this should
be text/html!
Platform:
Ubuntu 20.04.1 LTS (Focal Fossa)"
Linux version 5.4.0-42-generic (buildd@lgw01-amd64-038) (gcc version 9.3.0
(Ubuntu 9.3.0-10ubuntu2))
xdg-utils: 1.1.3-2ubuntu1
To manage notifications about this bug go to:
https://bugs.launchpad.net/shared-mime-info/+bug/1890716/+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 1890716] Re: misidentifies .html file as Perl script when it contains JavaScript "use strict"
#ＩＮＴＲＯ After digging up for a while I've found where the issue comes from for both `.html` and `.py` (bug #1857824) files. #ＳＨＯＲＴ The culprit responsible for misidentification resides in `.xml` database which specifies how to match mime-type against input data. It can be found here [2]. #ＬＯＮＧ The `kmimetypefinder.cpp` pulls up [0] `QMimeDatabase db` apis by `db.mimeTypeForFile(...)` which in turns bootstrup `QMimeDatabasePrivate ...` XML database from .xml file.[1] If we look carefully at the content of the `"text/x-perl"` entry we would see the following: ``` ... ... ``` Did you notice the offset attribute `"0:256"`? Now if we run the following two cases we will see that files whose content contains keywords `use strict` in the range of 1..256 will be identified as `text/x-perl` script and as `text/html` if the `use trict` is located outside of such range otherwise, checkout: 💲 tee "index.html" <https://github.com/KDE/kde-cli-tools/blob/master/kmimetypefinder/kmimetypefinder.cpp [1]: https://github.com/qt/qtbase/blob/03dfd4199deb4a0f5123fb1eead42f7e1f85e9e3/src/corelib/mimetypes/qmimedatabase.cpp#L102 [2]: https://github.com/qt/qtbase/tree/03dfd4199deb4a0f5123fb1eead42f7e1f85e9e3/src/corelib/mimetypes/mime/packages -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to shared-mime-info in Ubuntu. https://bugs.launchpad.net/bugs/1890716 Title: misidentifies .html file as Perl script when it contains JavaScript "use strict" Status in shared-mime-info: Unknown Status in kde-cli-tools package in Ubuntu: New Status in shared-mime-info package in Ubuntu: Fix Committed Status in shared-mime-info package in Debian: Confirmed Bug description: For .html files `xdg-mime` reports wrong type. The culprit is the `"use strict"` phrase which is used in JavaScript. It should not mistake .html files for anything else except of text/html ! STEPS TO REPRODUCE: Run the following step by step in any folder: 1. $ echo "\"use strict\"" > index.html 2. $ xdg-mime query filetype index.html # -> application/x-perl - this should be text/html! Platform: Ubuntu 20.04.1 LTS (Focal Fossa)" Linux version 5.4.0-42-generic (buildd@lgw01-amd64-038) (gcc version 9.3.0 (Ubuntu 9.3.0-10ubuntu2)) xdg-utils: 1.1.3-2ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/shared-mime-info/+bug/1890716/+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 1890716] Re: misidentifies .html file as Perl script when it contains JavaScript "use strict"
With the same setup I have the `mimetype` to output `text/html` for `index.html`. It seems it workds correctly. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to shared-mime-info in Ubuntu. https://bugs.launchpad.net/bugs/1890716 Title: misidentifies .html file as Perl script when it contains JavaScript "use strict" Status in shared-mime-info: Unknown Status in kde-cli-tools package in Ubuntu: New Status in shared-mime-info package in Ubuntu: Fix Committed Status in shared-mime-info package in Debian: Confirmed Bug description: For .html files `xdg-mime` reports wrong type. The culprit is the `"use strict"` phrase which is used in JavaScript. It should not mistake .html files for anything else except of text/html ! STEPS TO REPRODUCE: Run the following step by step in any folder: 1. $ echo "\"use strict\"" > index.html 2. $ xdg-mime query filetype index.html # -> application/x-perl - this should be text/html! Platform: Ubuntu 20.04.1 LTS (Focal Fossa)" Linux version 5.4.0-42-generic (buildd@lgw01-amd64-038) (gcc version 9.3.0 (Ubuntu 9.3.0-10ubuntu2)) xdg-utils: 1.1.3-2ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/shared-mime-info/+bug/1890716/+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 1890716] Re: misidentifies .html file as Perl script when it contains JavaScript "use strict"
** Also affects: kde-cli-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 shared-mime-info in Ubuntu. https://bugs.launchpad.net/bugs/1890716 Title: misidentifies .html file as Perl script when it contains JavaScript "use strict" Status in shared-mime-info: Unknown Status in kde-cli-tools package in Ubuntu: New Status in shared-mime-info package in Ubuntu: New Status in shared-mime-info package in Debian: Unknown Bug description: For .html files `xdg-mime` reports wrong type. The culprit is the `"use strict"` phrase which is used in JavaScript. It should not mistake .html files for anything else except of text/html ! STEPS TO REPRODUCE: Run the following step by step in any folder: 1. $ echo "\"use strict\"" > index.html 2. $ xdg-mime query filetype index.html # -> application/x-perl - this should be text/html! Platform: Ubuntu 20.04.1 LTS (Focal Fossa)" Linux version 5.4.0-42-generic (buildd@lgw01-amd64-038) (gcc version 9.3.0 (Ubuntu 9.3.0-10ubuntu2)) xdg-utils: 1.1.3-2ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/shared-mime-info/+bug/1890716/+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 1890716] Re: kmimetypefinder5 *.html reports wrong type
I've reported a new bug providing a complete and correct description: https://bugs.launchpad.net/ubuntu/+source/kde-cli-tools/+bug/1896682 This one can be safely closed. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to shared-mime-info in Ubuntu. https://bugs.launchpad.net/bugs/1890716 Title: kmimetypefinder5 *.html reports wrong type Status in shared-mime-info package in Ubuntu: Invalid Bug description: For .html files `xdg-mime` reports wrong type. The culprit is the `"use strict"` phrase which is used in JavaScript. It should not mistake .html files for anything else except of text/html ! STEPS TO REPRODUCE: Run the following step by step in any folder: 1. $ echo "\"use strict\"" > index.html 2. $ xdg-mime query filetype index.html # -> application/x-perl - this should be text/html! Platform: Ubuntu 20.04.1 LTS (Focal Fossa)" Linux version 5.4.0-42-generic (buildd@lgw01-amd64-038) (gcc version 9.3.0 (Ubuntu 9.3.0-10ubuntu2)) xdg-utils: 1.1.3-2ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shared-mime-info/+bug/1890716/+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 1890716] Re: kmimetypefinder5 *.html reports wrong type
New bug reopened with complete and correct explanation: https://bugs.launchpad.net/ubuntu/+source/kde-cli-tools/+bug/1896682 ** Changed in: shared-mime-info (Ubuntu) Status: Incomplete => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to shared-mime-info in Ubuntu. https://bugs.launchpad.net/bugs/1890716 Title: kmimetypefinder5 *.html reports wrong type Status in shared-mime-info package in Ubuntu: Invalid Bug description: For .html files `xdg-mime` reports wrong type. The culprit is the `"use strict"` phrase which is used in JavaScript. It should not mistake .html files for anything else except of text/html ! STEPS TO REPRODUCE: Run the following step by step in any folder: 1. $ echo "\"use strict\"" > index.html 2. $ xdg-mime query filetype index.html # -> application/x-perl - this should be text/html! Platform: Ubuntu 20.04.1 LTS (Focal Fossa)" Linux version 5.4.0-42-generic (buildd@lgw01-amd64-038) (gcc version 9.3.0 (Ubuntu 9.3.0-10ubuntu2)) xdg-utils: 1.1.3-2ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shared-mime-info/+bug/1890716/+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 1890716] Re: xdg-mime query filetype index.html reports wrong type
After running that commands I got the following output: $ ... Running kmimetypefinder5 "/home/alex/Desktop/index.html" application/x-perl It seems like that kmimetypefinder5 is major culprit here. I've found another unrelated bugreport here which was reported about a year ago: https://bugs.launchpad.net/ubuntu/+source/kde-cli-tools/+bug/1857824 In that case the program reports wrong type for *.py files with correct content. Weird! I think it's wortht to rename this bugreport. ** Summary changed: - xdg-mime query filetype index.html reports wrong type + kmimetypefinder5 *.html reports wrong type -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to shared-mime-info in Ubuntu. https://bugs.launchpad.net/bugs/1890716 Title: kmimetypefinder5 *.html reports wrong type Status in shared-mime-info package in Ubuntu: Incomplete Bug description: For .html files `xdg-mime` reports wrong type. The culprit is the `"use strict"` phrase which is used in JavaScript. It should not mistake .html files for anything else except of text/html ! STEPS TO REPRODUCE: Run the following step by step in any folder: 1. $ echo "\"use strict\"" > index.html 2. $ xdg-mime query filetype index.html # -> application/x-perl - this should be text/html! Platform: Ubuntu 20.04.1 LTS (Focal Fossa)" Linux version 5.4.0-42-generic (buildd@lgw01-amd64-038) (gcc version 9.3.0 (Ubuntu 9.3.0-10ubuntu2)) xdg-utils: 1.1.3-2ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shared-mime-info/+bug/1890716/+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 1890716] Re: xdg-mime query filetype index.html reports wrong type
I just have tried a fresh new user. The output is identical. See attached screenshot. ** Attachment added: "xdg-mime query wrong result" https://bugs.launchpad.net/ubuntu/+source/shared-mime-info/+bug/1890716/+attachment/5413048/+files/Screenshot_20200921_232318.png -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to shared-mime-info in Ubuntu. https://bugs.launchpad.net/bugs/1890716 Title: xdg-mime query filetype index.html reports wrong type Status in shared-mime-info package in Ubuntu: Incomplete Bug description: For .html files `xdg-mime` reports wrong type. The culprit is the `"use strict"` phrase which is used in JavaScript. It should not mistake .html files for anything else except of text/html ! STEPS TO REPRODUCE: Run the following step by step in any folder: 1. $ echo "\"use strict\"" > index.html 2. $ xdg-mime query filetype index.html # -> application/x-perl - this should be text/html! Platform: Ubuntu 20.04.1 LTS (Focal Fossa)" Linux version 5.4.0-42-generic (buildd@lgw01-amd64-038) (gcc version 9.3.0 (Ubuntu 9.3.0-10ubuntu2)) xdg-utils: 1.1.3-2ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shared-mime-info/+bug/1890716/+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 1894917] [NEW] [chtmax98090 - chtmax98090, playback] Pulseaudio fails to detect card // Bluetooth and USB devices work but internal speakers do not work (gives dummy output)
Public bug reported: To give some other background information: Description:Ubuntu 20.04.1 LTS Release:20.04 pulseaudio: Installed: 1:13.99.1-1ubuntu3.6 Candidate: 1:13.99.1-1ubuntu3.6 Version table: *** 1:13.99.1-1ubuntu3.6 500 500 http://us.archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 100 /var/lib/dpkg/status 1:13.99.1-1ubuntu3.2 500 500 http://security.ubuntu.com/ubuntu focal-security/main amd64 Packages 1:13.99.1-1ubuntu3 500 500 http://us.archive.ubuntu.com/ubuntu focal/main amd64 Packages Linux is fairly new for me and any other information I need to provide can be given as long as I am told on how to retrieve it. This system I am currently using is Dell Chromebook 11 (Candy MODEL) with 4 GB Ram and 16 GB of Har drive space. I am primarily using a Linux Distro such as Ubuntu or other distros in the same family. (This one is Linux Lite) Audio will play from USB connected devices or Bluetooth speakers/headphones. Internal speakers do not work at this moment and give me Dummy Output. The configuration file in puvucontrol gives me HDMI outputs or surround sound but no option for the internal speakers. I'm pretty sure my kernal driver is snd_hda-intel and tried loading different drivers from the file in '/etc/modprobe.d/alsa-base.conf' but to no avail. I'm not sure if this certain device cannot produce output from a linux distro but I will be trying other resources. I've reinstalled Pulse audio, its base and reinstalled Linux on this machine multiple times. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu3.6 ProcVersionSignature: Ubuntu 5.4.0-46.50-generic 5.4.60 Uname: Linux 5.4.0-46-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27.9 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: areebcancode 1417 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: XFCE Date: Tue Sep 8 17:24:36 2020 InstallationDate: Installed on 2020-09-01 (7 days ago) InstallationMedia: Linux Lite 5.0 - Release amd64 SourcePackage: pulseaudio Symptom: audio Symptom_Card: Built-in Audio - HDA Intel PCH Title: [chtmax98090 - chtmax98090, playback] Pulseaudio fails to detect card UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/03/2019 dmi.bios.vendor: coreboot dmi.chassis.type: 3 dmi.chassis.vendor: GOOGLE dmi.modalias: dmi:bvncoreboot:bvr:bd01/03/2019:svnGOOGLE:pnCandy:pvr1.0:cvnGOOGLE:ct3:cvr: dmi.product.name: Candy dmi.product.version: 1.0 dmi.sys.vendor: GOOGLE modified.conffile..etc.pulse.default.pa: [modified] mtime.conffile..etc.pulse.default.pa: 2020-09-03T17:56:09.564820 ** Affects: pulseaudio (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1894917 Title: [chtmax98090 - chtmax98090, playback] Pulseaudio fails to detect card // Bluetooth and USB devices work but internal speakers do not work (gives dummy output) Status in pulseaudio package in Ubuntu: New Bug description: To give some other background information: Description: Ubuntu 20.04.1 LTS Release: 20.04 pulseaudio: Installed: 1:13.99.1-1ubuntu3.6 Candidate: 1:13.99.1-1ubuntu3.6 Version table: *** 1:13.99.1-1ubuntu3.6 500 500 http://us.archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 100 /var/lib/dpkg/status 1:13.99.1-1ubuntu3.2 500 500 http://security.ubuntu.com/ubuntu focal-security/main amd64 Packages 1:13.99.1-1ubuntu3 500 500 http://us.archive.ubuntu.com/ubuntu focal/main amd64 Packages Linux is fairly new for me and any other information I need to provide can be given as long as I am told on how to retrieve it. This system I am currently using is Dell Chromebook 11 (Candy MODEL) with 4 GB Ram and 16 GB of Har drive space. I am primarily using a Linux Distro such as Ubuntu or other distros in the same family. (This one is Linux Lite) Audio will play from USB connected devices or Bluetooth speakers/headphones. Internal speakers do not work at this moment and give me Dummy Output. The configuration file in puvucontrol gives me HDMI outputs or surround sound but no option for the internal speakers. I'm pretty sure my kernal driver is snd_hda-intel and tried loading different drivers from the file in '/etc/modprobe.d/alsa-base.conf' but to no avail. I'm not sure if this certain device cannot produce output from a linux distro but I will be trying other resources. I've reinstalled Pulse audio, its base and reinstalled Linux on this machine multiple times. ProblemType: Bug DistroRelease: Ubunt
[Touch-packages] [Bug 1892798] Re: systemd package missing resolvconf(8) compatibility symlink, and a Provides: resolvconf
Your four appended comments are super full of just plain wrong information. I'll try to unpack these all piecemeal: > Ubuntu/Debian has never used openresolv This is not the case. Ubuntu and Debian have provided openresolv for a very long time, and resolvconf has mostly been an unmaintained mess. Most users who do DNS stuff wind up switching from resolvconf to openresolv if their OS comes preinstalled with resolvconf, and you'll find a lot of blogs advocating that too. Openresolv has definitely been part of the Debian/Ubuntu verse for a long time. > and yes systemd-resolved had a contribution to have openresolv compatible input interface. "had a contribution" what? Lennart wrote that code. It wasn't just some random third party contribution that got accidentally merged or something. The maintainer of the project wrote it and merged it. Why did he do that? Because resolvconf(8) is the standard stack-agnostic CLI interface for managing DNS on Linux. It's not some "legacy" thing or a "compatibility" thing, but a standard thing. Ensuring that systemd provides that was important for systemd to be able to become a drop in replacement for standard uniform resolver infra. > I am not asking for wireguard to implement any legacy/compat interfaces, but use directly systemd-resolved standard interface which has abi guarantees. Wha?! You've got it all backwards here. WireGuard uses resolvconf(8), because that's the standard Linux mechanism for managing DNS resolution. It will *not* use some specific backend, or write support for 20 different backends, because the resolvconf(8) is a successful abstraction over these so that application writers need not include a massive list of various things to try. So no, sorry, asking an upstream to implement some random newfangled thing isn't going to fly: Linux has a standard interface already for this kind of thing, which systemd implements because systemd is a caring citizen in the Linux-verse, and you're just crippling your users by *not* providing this standard interface. Please quit trying to introduce more fragmentation and shoving the burden of that upstream to application writers, in order to support your OS. Rather, play nicely with others, and provide the standard interfaces. Two of your upstreams are working together for this -- systemd provides a resolvconf(8), and wireguard uses a resolvconf(8). But for some bad reason you want to take away the standard link between the two and instead impose vendor-specific things on upstreams. This is a waste of everybody's time and makes code harder to maintain. > There is a lot more things and options one can provide to systemd-resolved > via native API that is impossible to specify via openresolv or > compat-openresolv. So what? resolvconf(8) provides a good acceptable abstraction for most use cases, which is why application writers use it. If somebody needs to dip down below the abstraction, so be it, but that's mostly not the case, and it certainly isn't the case here. > I do not wish to ship any openresolv/resolvconf/compat symlinks at all going > forward. Please, stop adding fragmentation. You're doing a disservice to both your users and your upstreams. The result is that things will stop working on Ubuntu, or you'll convince a few upstreams to incorporate brain damaged Ubuntu-specific hacks, as is commonly the case. Don't do this. > Integration with resolvconf _without_ using .$suffix of where the DNS > information is originating is incorrect integration on Debian/Ubuntu, because > of how resolvconf is shipped and configured on Debian/Ubuntu and used by > other packages. > > Arch used to use openresolv, openresolv compat was added to systemd-resolved, > and yes hence they were able to switch to systemd-resolved providing > openresolv symlink / compat / integration. Either by default, or as an option. > > That is not possible for Debian/Ubuntu because of more than three dozen of > packaging & hooks, calling resolvconf with .$suffix notation. Your reasoning here doesn't make sense. If you're removing resolvconf(8), all packages and hooks will stop working. If you're replacing broken Debian resolvconf(8) with compliant openresolv or systemd-resolvconf, it's either the same exact situation, or it's a situation that's slightly less bad. And, fixing the .$suffix notation seems a lot easier than refactoring everything anyway. Either way, you might have to do work. But, seeing as openresolv is *already* something available to users and *already* something that users use frequently, why not ship systemd-resolvconf too? Stop trying to gimp your users. > Please see previous bugs about this, trying to identify, enumerate and fix all of those usecases. The bugs that I've seen always seem like t
[Touch-packages] [Bug 1892798] Re: systemd package missing resolvconf(8) compatibility symlink, and a Provides: resolvconf
** Changed in: wireguard (Ubuntu) Status: Incomplete => Confirmed -- 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/1892798 Title: systemd package missing resolvconf(8) compatibility symlink, and a Provides: resolvconf Status in systemd package in Ubuntu: Won't Fix Status in wireguard package in Ubuntu: Confirmed Bug description: By default Ubuntu now uses systemd to manage the nameservers in resolv.conf, so resolvconf and openresolv seem to be redundant. However, it appears that systemd's resolvectl is compatable with resolvconf style commands if symlinked as resolvconf. I'm not really sure how deb packaging works, but if it possible to check for the resolvconf command, and if not found just symlink /usr/bin/resolvectl to /usr/sbin/resolvconf then wg-quick will work without additional packages. See https://manpages.ubuntu.com/manpages/focal/man1/resolvectl.1#compatibility%20with%20resolvconf(8) for more info. Apologies if there is a better place to direct this info. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1892798/+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 1892798] Re: systemd package missing resolvconf(8) compatibility symlink, and a Provides: resolvconf
By the way, Arch manages the possibility of openresolv colliding with systemd's resolvconf by providing a package called "systemd-resolvconf": https://www.archlinux.org/packages/core/x86_64/systemd-resolvconf/ https://github.com/archlinux/svntogit- packages/blob/packages/systemd/trunk/PKGBUILD#L239-L251 This seems like a perfectly reasonable way to accomplish this. Simply package the symlink in a separate package, and then the "Recommends:" for wireguard just includes systemd-resolvconf in the list alongside openresolv and resolvconf. That seems like an exceedingly reasonable way of going about things. Why not just do the same thing here? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1892798 Title: systemd package missing resolvconf(8) compatibility symlink, and a Provides: resolvconf Status in systemd package in Ubuntu: Won't Fix Status in wireguard package in Ubuntu: Confirmed Bug description: By default Ubuntu now uses systemd to manage the nameservers in resolv.conf, so resolvconf and openresolv seem to be redundant. However, it appears that systemd's resolvectl is compatable with resolvconf style commands if symlinked as resolvconf. I'm not really sure how deb packaging works, but if it possible to check for the resolvconf command, and if not found just symlink /usr/bin/resolvectl to /usr/sbin/resolvconf then wg-quick will work without additional packages. See https://manpages.ubuntu.com/manpages/focal/man1/resolvectl.1#compatibility%20with%20resolvconf(8) for more info. Apologies if there is a better place to direct this info. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1892798/+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 1892798] Re: eliminating resolvconf/openresolv dependencies
> wireguard package => please feed DNS data direct to systemd-resolved using either dbus or the cli. Absolutely not. We're not going to add vendor-specific hacks for broken distros that are unable to include the standard interface for this kind of thing, resolvconf(8). This is a pretty clear case of downstream being broken. > Unfortunately systemd's resolved's resolvctl is not compatible with Debian's/Ubuntu's historical resolvconf. First of all, we're not talking about systemd's resolvectl. We're talking about systemd's resolvconf compatibility symlink which provides the same interface as openresolv or the debian resolvconf monster. With that clarified, if you still think there's a problem due to Debian's resolvconf using an interface prefix list, I think you're incorrect there too. Firstly, openresolv doesn't act that way, and things work fine. Secondly, systems that have moved to systemd-resolved (that is, Ubuntu itself) have in the process _broken_ resolvconf anyway. Replacing broken resolvconf with one that is less broken -- even if it doesn't do priority interface prefixes -- is still a marked improvement. And thirdly, every script I've seen that uses resolvconf actually continues to work fine with systemd's compatibility symlink of resolvconf; if any you see don't, why not fix them? So, in other words, I don't think you've presented a very compelling argument at all. I can't see any correct technical reasoning in what you wrote. It seems like adding the resolvconf compatibility symlink is a marked improvement over the current broken status quo. ** Summary changed: - eliminating resolvconf/openresolv dependencies + systemd package missing resolvconf(8) compatibility symlink, and a Provides: resolvconf -- 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/1892798 Title: systemd package missing resolvconf(8) compatibility symlink, and a Provides: resolvconf Status in systemd package in Ubuntu: Won't Fix Status in wireguard package in Ubuntu: Confirmed Bug description: By default Ubuntu now uses systemd to manage the nameservers in resolv.conf, so resolvconf and openresolv seem to be redundant. However, it appears that systemd's resolvectl is compatable with resolvconf style commands if symlinked as resolvconf. I'm not really sure how deb packaging works, but if it possible to check for the resolvconf command, and if not found just symlink /usr/bin/resolvectl to /usr/sbin/resolvconf then wg-quick will work without additional packages. See https://manpages.ubuntu.com/manpages/focal/man1/resolvectl.1#compatibility%20with%20resolvconf(8) for more info. Apologies if there is a better place to direct this info. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1892798/+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 1892798] Re: eliminating resolvconf/openresolv dependencies
Thanks for bringing this to my attention. I believe your assessment is correct. Do you know which Ubuntu first started using resolved? How far back do we need to make changes? There are two facets of this: 1) The Ubuntu systemd package should install the resolvconf compatibility symlink. I have no idea why this isn't already the case, and that seems like a bug that should be remedied ASAP. resolvconf(8) is the standard interface for programs to interact with DNS, which is why systemd provides it. Not providing it is super confusing. 2) The Recommends in the wireguard package should be adjusted. I believe apw@ can handle (2). Somebody on the systemd team should handle (1). ** Changed in: wireguard (Ubuntu) Status: New => Confirmed ** Also affects: systemd (Ubuntu) Importance: Undecided Status: New ** Changed in: systemd (Ubuntu) Status: New => Confirmed -- 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/1892798 Title: eliminating resolvconf/openresolv dependencies Status in systemd package in Ubuntu: Confirmed Status in wireguard package in Ubuntu: Confirmed Bug description: By default Ubuntu now uses systemd to manage the nameservers in resolv.conf, so resolvconf and openresolv seem to be redundant. However, it appears that systemd's resolvectl is compatable with resolvconf style commands if symlinked as resolvconf. I'm not really sure how deb packaging works, but if it possible to check for the resolvconf command, and if not found just symlink /usr/bin/resolvectl to /usr/sbin/resolvconf then wg-quick will work without additional packages. See https://manpages.ubuntu.com/manpages/focal/man1/resolvectl.1#compatibility%20with%20resolvconf(8) for more info. Apologies if there is a better place to direct this info. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1892798/+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 1890716] Re: xdg-mime query filetype index.html reports wrong type
why did you tag the report* Bump. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to shared-mime-info in Ubuntu. https://bugs.launchpad.net/bugs/1890716 Title: xdg-mime query filetype index.html reports wrong type Status in shared-mime-info package in Ubuntu: Invalid Bug description: For .html files `xdg-mime` reports wrong type. The culprit is the `"use strict"` phrase which is used in JavaScript. It should not mistake .html files for anything else except of text/html ! STEPS TO REPRODUCE: Run the following step by step in any folder: 1. $ echo "\"use strict\"" > index.html 2. $ xdg-mime query filetype index.html # -> application/x-perl - this should be text/html! Platform: Ubuntu 20.04.1 LTS (Focal Fossa)" Linux version 5.4.0-42-generic (buildd@lgw01-amd64-038) (gcc version 9.3.0 (Ubuntu 9.3.0-10ubuntu2)) xdg-utils: 1.1.3-2ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shared-mime-info/+bug/1890716/+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 1890716] Re: xdg-mime query filetype index.html reports wrong type
Hi Sebastien. Thaks your for your reply. I suggest you to do the following to see that even if file is starting with proper tags it is recognized as `application/x-perl`: $ tee "index.html" < use strict eol $ xdg-mime query filetype index.html # -> application/x-perl - wrong type Why did you tagged report as invalid? I just got a file with minified JS code which has `use strict` burrowed deep somewhere inside correct html file but it's still recognized as perl script. I can't use some tools to open the file in browser by using xdg-open and forced to use browser-specific launcher. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to shared-mime-info in Ubuntu. https://bugs.launchpad.net/bugs/1890716 Title: xdg-mime query filetype index.html reports wrong type Status in shared-mime-info package in Ubuntu: Invalid Bug description: For .html files `xdg-mime` reports wrong type. The culprit is the `"use strict"` phrase which is used in JavaScript. It should not mistake .html files for anything else except of text/html ! STEPS TO REPRODUCE: Run the following step by step in any folder: 1. $ echo "\"use strict\"" > index.html 2. $ xdg-mime query filetype index.html # -> application/x-perl - this should be text/html! Platform: Ubuntu 20.04.1 LTS (Focal Fossa)" Linux version 5.4.0-42-generic (buildd@lgw01-amd64-038) (gcc version 9.3.0 (Ubuntu 9.3.0-10ubuntu2)) xdg-utils: 1.1.3-2ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shared-mime-info/+bug/1890716/+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 1890286] Re: ansi escape sequence injection in add-apt-repository
You might be right that the remaining ones that slip through your regex are mere "nuisance"s. But you know how those things go - one man's nuisance is another man's vuln. Some of those, anyhow, are implemented by the Linux console driver. Why not just take the tried and true "safe" route, as implemented by vis(3)'s VIS_SAFE or similar? Otherwise it sounds like you're playing with a bit of fire. Put differently, is there some legitimate use case of the ANSI escape characters that make you want to preserve some of their usage while disallowing other parts? If so, that would really surprise me. -- 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/1890286 Title: ansi escape sequence injection in add-apt-repository Status in software-properties package in Ubuntu: Fix Released Bug description: This was reported to oss-security and to secur...@ubuntu.com, but I figure I should make a real bug report, as otherwise it'll probably be missed. Original post from https://www.openwall.com/lists/oss- security/2020/08/03/1 follows below. -- Hi, I've found a rather low grade concern: I'm able to inject ANSI escape sequences into PPA descriptions on Launchpad, and then have them rendered by add-apt-repository *before* the user consents to actually adding that repository. There might be some sort of trust barrier issue with that. This could be used to clear the screen and imitate a fresh bash prompt, upload files, dump the current screen to a file, or other classic shenanigans, well chronicled in the archives of oss-sec. PoC time -- I'm using this "feature" for good at the moment to announce the deprecation in bold text of a PPA that I maintain: https://data.zx2c4.com/add-apt-repository-ansi-injection.png The proper fix to this is likely to do sanitization on the add-apt-repository side. Regards, Jason To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1890286/+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 1890286] Re: ansi escape sequence injection in add-apt-repository
I'm not convinced that really cuts it. Namely, from the diff:
-print(" %s" % (info["description"] or ""))
+# strip ANSI escape sequences
+description = re.sub(r"(\x9B|\x1B\[)[0-?]*[ -/]*[@-~]",
+ "", info["description"] or "")
+
+print(" %s" % description)
There are sequences that don't get filtered by that. Aside from the
usual things like \r or \b, it looks like https://man7.org/linux/man-
pages/man4/console_codes.4.html lists a few codes that defy it too.
While that diff above might be the "stackoverflow answer", it doesn't
seem complete.
Instead, why not just adopt a whitelist policy? Only allow visible and
space characters, or something like that.
--
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/1890286
Title:
ansi escape sequence injection in add-apt-repository
Status in software-properties package in Ubuntu:
Fix Released
Bug description:
This was reported to oss-security and to secur...@ubuntu.com, but I
figure I should make a real bug report, as otherwise it'll probably be
missed. Original post from https://www.openwall.com/lists/oss-
security/2020/08/03/1 follows below.
--
Hi,
I've found a rather low grade concern: I'm able to inject ANSI escape
sequences into PPA descriptions on Launchpad, and then have them
rendered by add-apt-repository *before* the user consents to actually
adding that repository. There might be some sort of trust barrier
issue with that. This could be used to clear the screen and imitate a
fresh bash prompt, upload files, dump the current screen to a file, or
other classic shenanigans, well chronicled in the archives of oss-sec.
PoC time -- I'm using this "feature" for good at the moment to
announce the deprecation in bold text of a PPA that I maintain:
https://data.zx2c4.com/add-apt-repository-ansi-injection.png
The proper fix to this is likely to do sanitization on the
add-apt-repository side.
Regards,
Jason
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1890286/+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 1890286] Re: ansi escape sequence injection into add-apt-repository
Looks like this has come up before in other utilities and was fixed, such as https://bugs.launchpad.net/ubuntu/+source/base- files/+bug/1649352 . ** Summary changed: - ansi escape sequence injection into add-apt-repository + ansi escape sequence injection in add-apt-repository -- 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/1890286 Title: ansi escape sequence injection in add-apt-repository Status in software-properties package in Ubuntu: New Bug description: This was reported to oss-security and to secur...@ubuntu.com, but I figure I should make a real bug report, as otherwise it'll probably be missed. Original post from https://www.openwall.com/lists/oss- security/2020/08/03/1 follows below. -- Hi, I've found a rather low grade concern: I'm able to inject ANSI escape sequences into PPA descriptions on Launchpad, and then have them rendered by add-apt-repository *before* the user consents to actually adding that repository. There might be some sort of trust barrier issue with that. This could be used to clear the screen and imitate a fresh bash prompt, upload files, dump the current screen to a file, or other classic shenanigans, well chronicled in the archives of oss-sec. PoC time -- I'm using this "feature" for good at the moment to announce the deprecation in bold text of a PPA that I maintain: https://data.zx2c4.com/add-apt-repository-ansi-injection.png The proper fix to this is likely to do sanitization on the add-apt-repository side. Regards, Jason To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1890286/+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 1890286] [NEW] ansi escape sequence injection in add-apt-repository
*** This bug is a security vulnerability *** Public security bug reported: This was reported to oss-security and to secur...@ubuntu.com, but I figure I should make a real bug report, as otherwise it'll probably be missed. Original post from https://www.openwall.com/lists/oss- security/2020/08/03/1 follows below. -- Hi, I've found a rather low grade concern: I'm able to inject ANSI escape sequences into PPA descriptions on Launchpad, and then have them rendered by add-apt-repository *before* the user consents to actually adding that repository. There might be some sort of trust barrier issue with that. This could be used to clear the screen and imitate a fresh bash prompt, upload files, dump the current screen to a file, or other classic shenanigans, well chronicled in the archives of oss-sec. PoC time -- I'm using this "feature" for good at the moment to announce the deprecation in bold text of a PPA that I maintain: https://data.zx2c4.com/add-apt-repository-ansi-injection.png The proper fix to this is likely to do sanitization on the add-apt-repository side. Regards, Jason ** Affects: software-properties (Ubuntu) Importance: Undecided Status: New ** Information type changed from Private Security to Public ** Information type changed from Public to Public Security -- 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/1890286 Title: ansi escape sequence injection in add-apt-repository Status in software-properties package in Ubuntu: New Bug description: This was reported to oss-security and to secur...@ubuntu.com, but I figure I should make a real bug report, as otherwise it'll probably be missed. Original post from https://www.openwall.com/lists/oss- security/2020/08/03/1 follows below. -- Hi, I've found a rather low grade concern: I'm able to inject ANSI escape sequences into PPA descriptions on Launchpad, and then have them rendered by add-apt-repository *before* the user consents to actually adding that repository. There might be some sort of trust barrier issue with that. This could be used to clear the screen and imitate a fresh bash prompt, upload files, dump the current screen to a file, or other classic shenanigans, well chronicled in the archives of oss-sec. PoC time -- I'm using this "feature" for good at the moment to announce the deprecation in bold text of a PPA that I maintain: https://data.zx2c4.com/add-apt-repository-ansi-injection.png The proper fix to this is likely to do sanitization on the add-apt-repository side. Regards, Jason To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1890286/+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 1889015] [NEW] display crashes sometimes when click on firefox or settings
Public bug reported: display crashes sometimes when click on firefox or settings ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-112.113-generic 4.15.18 Uname: Linux 4.15.0-112-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.15 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity:Unity7:ubuntu Date: Sun Jul 26 16:07:13 2020 DistUpgraded: 2020-07-09 17:13:15,323 DEBUG icon theme changed, re-reading DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: NVIDIA Corporation C61 [GeForce 6150SE nForce 430] [10de:03d0] (rev a2) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company C61 [GeForce 6150SE nForce 430] [103c:2a58] InstallationDate: Installed on 2020-07-09 (17 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) Lsusb: Bus 001 Device 002: ID 0bda:0111 Realtek Semiconductor Corp. RTS5111 Card Reader Controller Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: HP-Pavilion RX885AA-ABA a6000n ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-112-generic root=UUID=e43514f2-3e33-49da-9662-a8e8923b87f6 ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to bionic on 2020-07-09 (16 days ago) dmi.bios.date: 02/02/2007 dmi.bios.vendor: Phoenix Technologies, LTD dmi.bios.version: 5.01 dmi.board.name: NARRA dmi.board.vendor: ASUSTek Computer INC. dmi.board.version: 1.01 dmi.chassis.type: 3 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnPhoenixTechnologies,LTD:bvr5.01:bd02/02/2007:svnHP-Pavilion:pnRX885AA-ABAa6000n:pvr:rvnASUSTekComputerINC.:rnNARRA:rvr1.01:cvnHewlett-Packard:ct3:cvrChassisVersion: dmi.product.family: 103C_53316J dmi.product.name: RX885AA-ABA a6000n dmi.sys.vendor: HP-Pavilion version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.101-2~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~18.04.3 version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.8-0ubuntu0~18.04.3 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 xserver.bootTime: Sun Jul 26 16:01:21 2020 xserver.configfile: default xserver.devices: inputPower Button KEYBOARD, id 6 inputPower Button KEYBOARD, id 7 inputAT Translated Set 2 keyboard KEYBOARD, id 8 inputImPS/2 Generic Wheel Mouse MOUSE, id 9 xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.19.6-1ubuntu4.4 xserver.video_driver: nouveau ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic compiz-0.9 corruption 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/1889015 Title: display crashes sometimes when click on firefox or settings Status in xorg package in Ubuntu: New Bug description: display crashes sometimes when click on firefox or settings ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-112.113-generic 4.15.18 Uname: Linux 4.15.0-112-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.15 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity:Unity7:ubuntu Date: Sun Jul 26 16:07:13 2020 DistUpgraded: 2020-07-09 17:13:15,323 DEBUG icon theme changed, re-reading DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: NVIDIA Corporation C61 [GeForce 6150SE nForce 430] [10de:03d0] (rev a2) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company C61 [GeForce 6150SE nForce 430] [103c:2a58] InstallationDate: Installed on 2020-07-09 (17 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Re
[Touch-packages] [Bug 1887683] [NEW] I Have no system settings
Public bug reported: When I start the computer it loads as it always have but when I use the dropdowns to get a program it just flashes and loads the top program three or for times. So I then switch off and reboot, This I do two or three times until it works properly. Best Regards Gordon ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-111.112-generic 4.15.18 Uname: Linux 4.15.0-111-generic x86_64 NonfreeKernelModules: nvidia .proc.driver.nvidia.gpus.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 304.137 Thu Sep 14 13:51:03 PDT 2017 GCC version: gcc version 7.5.0 (Ubuntu 7.5.0-3ubuntu1~18.04) .tmp.unity_support_test.1: ApportVersion: 2.20.9-0ubuntu7.15 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Wed Jul 15 16:08:46 2020 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: nvidia, 304.137, 4.15.0-108-generic, x86_64: installed nvidia, 304.137, 4.15.0-109-generic, x86_64: installed nvidia, 304.137, 4.15.0-111-generic, x86_64: installed GraphicsCard: NVIDIA Corporation C61 [GeForce 7025 / nForce 630a] [10de:03d6] (rev a2) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. C61 [GeForce 7025 / nForce 630a] [1043:83a4] InstallationDate: Installed on 2012-09-29 (2846 days ago) InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release amd64 (20120823.1) MachineType: System manufacturer System Product Name ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-111-generic root=UUID=6eb98a42-bc12-42f1-992b-97782d05bb24 ro splash quiet Renderer: Software SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/26/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0702 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: M4N68T-M-LE-V2 dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0702:bd01/26/2011:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM4N68T-M-LE-V2:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.101-2~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.8-0ubuntu1~18.04.1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 xserver.bootTime: Wed Jul 15 11:12:03 2020 xserver.configfile: /etc/X11/xorg.conf xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.19.6-1ubuntu4.4 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic possible-manual-nvidia-install 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/1887683 Title: I Have no system settings Status in xorg package in Ubuntu: New Bug description: When I start the computer it loads as it always have but when I use the dropdowns to get a program it just flashes and loads the top program three or for times. So I then switch off and reboot, This I do two or three times until it works properly. Best Regards Gordon ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-111.112-generic 4.15.18 Uname: Linux 4.15.0-111-generic x86_64 NonfreeKernelModules: nvidia .proc.driver.nvidia.gpus.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 304.137 Thu Sep 14 13:51:03 PDT 2017 GCC version: gcc version 7.5.0 (Ubuntu 7.5.0-3ubuntu1~18.04) .tmp.unity_support_test.1: ApportVersion: 2.20.9-0ubuntu7.15 Architecture: amd64 CompizPlugins: No
[Touch-packages] [Bug 1887685] [NEW] I Have no system settings
Public bug reported: When I start the computer it loads as it always have but when I use the dropdowns to get a program it just flashes and loads the top program three or for times. So I then switch off and reboot, This I do two or three times until it works properly. Best Regards Gordon ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-111.112-generic 4.15.18 Uname: Linux 4.15.0-111-generic x86_64 NonfreeKernelModules: nvidia .proc.driver.nvidia.gpus.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 304.137 Thu Sep 14 13:51:03 PDT 2017 GCC version: gcc version 7.5.0 (Ubuntu 7.5.0-3ubuntu1~18.04) .tmp.unity_support_test.1: ApportVersion: 2.20.9-0ubuntu7.15 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Wed Jul 15 16:08:46 2020 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: nvidia, 304.137, 4.15.0-108-generic, x86_64: installed nvidia, 304.137, 4.15.0-109-generic, x86_64: installed nvidia, 304.137, 4.15.0-111-generic, x86_64: installed GraphicsCard: NVIDIA Corporation C61 [GeForce 7025 / nForce 630a] [10de:03d6] (rev a2) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. C61 [GeForce 7025 / nForce 630a] [1043:83a4] InstallationDate: Installed on 2012-09-29 (2846 days ago) InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release amd64 (20120823.1) MachineType: System manufacturer System Product Name ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-111-generic root=UUID=6eb98a42-bc12-42f1-992b-97782d05bb24 ro splash quiet Renderer: Software SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/26/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0702 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: M4N68T-M-LE-V2 dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0702:bd01/26/2011:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM4N68T-M-LE-V2:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.101-2~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.8-0ubuntu1~18.04.1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 xserver.bootTime: Wed Jul 15 11:12:03 2020 xserver.configfile: /etc/X11/xorg.conf xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.19.6-1ubuntu4.4 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic possible-manual-nvidia-install 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/1887685 Title: I Have no system settings Status in xorg package in Ubuntu: New Bug description: When I start the computer it loads as it always have but when I use the dropdowns to get a program it just flashes and loads the top program three or for times. So I then switch off and reboot, This I do two or three times until it works properly. Best Regards Gordon ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-111.112-generic 4.15.18 Uname: Linux 4.15.0-111-generic x86_64 NonfreeKernelModules: nvidia .proc.driver.nvidia.gpus.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 304.137 Thu Sep 14 13:51:03 PDT 2017 GCC version: gcc version 7.5.0 (Ubuntu 7.5.0-3ubuntu1~18.04) .tmp.unity_support_test.1: ApportVersion: 2.20.9-0ubuntu7.15 Architecture: amd64 CompizPlugins: No
Re: [Touch-packages] [Bug 1886412] Re: $ ubuntu-bug xorg
On 06/07/2020 22:19, Sebastien Bacher wrote: > Thank you for taking the time to report this bug and help make Ubuntu > better. Unfortunately, we cannot work on this bug because your > description didn't include enough information. You may find it helpful > to read 'How to report bugs effectively' > http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be grateful > if you would then provide a more complete description of the problem. > > We have instructions on debugging some types of problems at > http://wiki.ubuntu.com/DebuggingProcedures. > > At a minimum, we need: > 1. The specific steps or actions you took that caused you to encounter the > problem. > 2. The behavior you expected. > 3. The behavior you actually encountered (in as much detail as possible). > > Thanks! > > ** Changed in: xorg (Ubuntu) > Importance: Undecided => Low > > ** Changed in: xorg (Ubuntu) > Status: New => Incomplete > Hi I was downloading the normal updates that come automatically when finished it told me to restart the computer, the OS opened with no problems no message I left for about 15mins and the screen used to sleep after Five mins. When I returned the screen was still open I clicked on Applications for the drop-down programmes which flashed and returned to the top. When I clicked on the top right of the screen the same thing happened. I then decided to reboot again, the same thing happened seven time before I got a good screen that worked OK except that I could not open system settings from top right icon all the rest worked. I now decided to ask Ubuntu 1 for an answer, it then set up a scan which took some time and asked me to submit the results which I did. When I click on system settings the "About this computer" loads, I have not switched off since but I switch off the screen when not in use. Regards Gordon Wright Thank you. -- 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/1886412 Title: $ ubuntu-bug xorg Status in xorg package in Ubuntu: Incomplete Bug description: I cannot open system settings so I can set up a sleep mode after leaving offfor a spell. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-109.110-generic 4.15.18 Uname: Linux 4.15.0-109-generic x86_64 NonfreeKernelModules: nvidia .proc.driver.nvidia.gpus.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 304.137 Thu Sep 14 13:51:03 PDT 2017 GCC version: gcc version 7.5.0 (Ubuntu 7.5.0-3ubuntu1~18.04) .tmp.unity_support_test.1: ApportVersion: 2.20.9-0ubuntu7.15 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Mon Jul 6 11:57:21 2020 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: nvidia, 304.137, 4.15.0-108-generic, x86_64: installed nvidia, 304.137, 4.15.0-109-generic, x86_64: installed GraphicsCard: NVIDIA Corporation C61 [GeForce 7025 / nForce 630a] [10de:03d6] (rev a2) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. C61 [GeForce 7025 / nForce 630a] [1043:83a4] InstallationDate: Installed on 2012-09-29 (2837 days ago) InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release amd64 (20120823.1) MachineType: System manufacturer System Product Name ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-109-generic root=UUID=6eb98a42-bc12-42f1-992b-97782d05bb24 ro splash quiet Renderer: Software SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/26/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0702 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: M4N68T-M-LE-V2 dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0702:bd01/26/2011:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM4N68T-M-LE-V2:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
[Touch-packages] [Bug 1850966] Re: Stuck at "Refreshing software cache" after enabling repository not updated for Eoan
I also have the problem, and since then, I haven't been able to use software-properties. (focal) -- 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/1850966 Title: Stuck at "Refreshing software cache" after enabling repository not updated for Eoan Status in software-properties package in Ubuntu: Confirmed Bug description: Steps to reproduce: 1. Open Software and Updates 2. Go to "other software" and enable, for example, a repository disabled during upgrade to Eoan which is not updated for Eoan yet 3. Press close and then reload on the dialog that opens. 4. Refreshing software cache dialog is stuck After closing the dialogs by right clicking on the windows and the open apps bar, re opening Software and updates only shows a white square you can't interact with. Ubuntu 19.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1850966/+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 725126]
Tracking the new bug here now: https://sourceware.org/bugzilla/show_bug.cgi?id=26141 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to binutils in Ubuntu. https://bugs.launchpad.net/bugs/725126 Title: gas may assemble b to locally-defined, preemptible global symbol as "b.n" Status in binutils: Fix Released Status in Linaro Binutils: Won't Fix Status in Cortex String Routines: Invalid Status in armel-cross-toolchain-base package in Ubuntu: Fix Released Status in binutils package in Ubuntu: Fix Released Bug description: There's no guarantee that R_ARM_THM_JUMP11 relocation can be resolved correctly if the symbol gets preempted. Observed in binutils-arm-linux-gnueabi 2.20.51.20100908-0ubuntu2cross1.52. Observed on binutils trunk on 2011-02-25. The problem seems to strike when the compiler optimises a sibling call to "b ", for which the assembler generates a b.n. As a side-effect of the presence of this relocation, Thumb-2 kernel modules may fail to load, since the kernel doesn't support fixing up this relocation. I believe the kernel doesn't do any symbol preemption processing when loading modules -- if so, the relocation is actually redundant. But there's no way for the kernel to detect at module load time that the relocation can safely be ignored. In kernel builds, about 1 out every 6 modules suffers from this problem. It's not clear to me whether the method used by the kernel to link .ko objects is wrong or not. It seems that either the tools should support symbol preemption in this scenario (implying that a short branch is not adequate to guarantee that preemption will work -- i.e., a gas bug) or not (in this case the fixup should be done locally and there should presumably be no relocation -- i.e., a different gas bug). It appears that passing -fno-optimize-sibling-calls to GCC can work around the problem by avoiding the generation of local branches to global symbols, but this is clearly not the correct fix. To manage notifications about this bug go to: https://bugs.launchpad.net/binutils/+bug/725126/+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 725126]
This problem still exists on binutils 2.33 when -fvisibility=hidden is passed to cflags. I imagine this is so due to some conflicting code where the forced B.W is only generated for static functions, since non- static ones will be relocated differently, but then because of -fvisibility=hidden, they get treated like statics, only B is used instead of the forced B.W, causing this issue to crop up again. OpenWRT experienced this when including WireGuard on a new board. I fixed it like this: https://git.zx2c4.com/wireguard-linux- compat/commit/?id=178cdfffb99f2fd6fb4a5bfd2f9319461d93f53b -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to binutils in Ubuntu. https://bugs.launchpad.net/bugs/725126 Title: gas may assemble b to locally-defined, preemptible global symbol as "b.n" Status in binutils: Fix Released Status in Linaro Binutils: Won't Fix Status in Cortex String Routines: Invalid Status in armel-cross-toolchain-base package in Ubuntu: Fix Released Status in binutils package in Ubuntu: Fix Released Bug description: There's no guarantee that R_ARM_THM_JUMP11 relocation can be resolved correctly if the symbol gets preempted. Observed in binutils-arm-linux-gnueabi 2.20.51.20100908-0ubuntu2cross1.52. Observed on binutils trunk on 2011-02-25. The problem seems to strike when the compiler optimises a sibling call to "b ", for which the assembler generates a b.n. As a side-effect of the presence of this relocation, Thumb-2 kernel modules may fail to load, since the kernel doesn't support fixing up this relocation. I believe the kernel doesn't do any symbol preemption processing when loading modules -- if so, the relocation is actually redundant. But there's no way for the kernel to detect at module load time that the relocation can safely be ignored. In kernel builds, about 1 out every 6 modules suffers from this problem. It's not clear to me whether the method used by the kernel to link .ko objects is wrong or not. It seems that either the tools should support symbol preemption in this scenario (implying that a short branch is not adequate to guarantee that preemption will work -- i.e., a gas bug) or not (in this case the fixup should be done locally and there should presumably be no relocation -- i.e., a different gas bug). It appears that passing -fno-optimize-sibling-calls to GCC can work around the problem by avoiding the generation of local branches to global symbols, but this is clearly not the correct fix. To manage notifications about this bug go to: https://bugs.launchpad.net/binutils/+bug/725126/+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 1872118] Re: DHCP Cluster crashes after a few hours
I just moved primary dns and dhcp from 16.04.6 LTS to 20.04 LTS and also observe this behavior. Primary is isc-dhcp-server 4.4.1-2.1ubuntu5 amd64. Crashes regularly. Secondary is isc-dhcp-server 4.3.5-3+deb9 armhf which runs fine. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to isc-dhcp in Ubuntu. https://bugs.launchpad.net/bugs/1872118 Title: DHCP Cluster crashes after a few hours Status in isc-dhcp package in Ubuntu: Confirmed Bug description: I have a pair of DHCP serevrs running in a cluster on ubuntu 20.04, All worked perfectly until recently, when they started stopping with code=killed, status=6/ABRT. This is being fixed by https://bugs.launchpad.net/bugs/1870729 However now one stops after a few hours with the following errors. One can stay on line but not both. Syslog shows Apr 10 17:20:15 dhcp-primary sh[6828]: ../../../../lib/isc/unix/socket.c:3361: INSIST(!sock->pending_send) failed, back trace Apr 10 17:20:15 dhcp-primary sh[6828]: #0 0x7fbe78702a4a in ?? Apr 10 17:20:15 dhcp-primary sh[6828]: #1 0x7fbe78702980 in ?? Apr 10 17:20:15 dhcp-primary sh[6828]: #2 0x7fbe7873e7e1 in ?? Apr 10 17:20:15 dhcp-primary sh[6828]: #3 0x7fbe784e5609 in ?? Apr 10 17:20:15 dhcp-primary sh[6828]: #4 0x7fbe78621103 in ?? nothing in kern.log apport.log shows ERROR: apport (pid 6850) Fri Apr 10 17:20:15 2020: called for pid 6828, signal 6, core limit 0, dump mode 2 ERROR: apport (pid 6850) Fri Apr 10 17:20:15 2020: not creating core for pid with dump mode of 2 ERROR: apport (pid 6850) Fri Apr 10 17:20:15 2020: executable: /usr/sbin/dhcpd (command line "dhcpd -user dhcpd -group dhcpd -f -4 -pf /run/dhcp-server/dhcpd.pid -cf /etc/dhcp/dhcpd.conf") ERROR: apport (pid 6850) Fri Apr 10 17:20:15 2020: is_closing_session(): no DBUS_SESSION_BUS_ADDRESS in environment ERROR: apport (pid 6850) Fri Apr 10 17:20:15 2020: wrote report /var/crash/_usr_sbin_dhcpd.0.crash /var/crash/_usr_sbin_dhcpd.0.crash shows ProblemType: Crash Architecture: amd64 CrashCounter: 1 Date: Fri Apr 10 17:20:15 2020 DistroRelease: Ubuntu 20.04 ExecutablePath: /usr/sbin/dhcpd ExecutableTimestamp: 1586210315 ProcCmdline: dhcpd -user dhcpd -group dhcpd -f -4 -pf /run/dhcp-server/dhcpd.pid -cf /etc/dhcp/dhcpd.conf ProcEnviron: Error: [Errno 13] Permission denied: 'environ' ProcMaps: Error: [Errno 13] Permission denied: 'maps' ProcStatus: Name: dhcpd Umask: 0022 State: D (disk sleep) Tgid: 6828 Ngid: 0 Pid: 6828 PPid: 1 TracerPid: 0 Uid: 113 113 113 113 Gid: 118 118 118 118 FDSize:128 Groups: NStgid:6828 NSpid: 6828 NSpgid:6828 NSsid: 6828 VmPeak: 236244 kB VmSize: 170764 kB VmLck:0 kB VmPin:0 kB VmHWM:12064 kB VmRSS:12064 kB RssAnon: 5940 kB RssFile: 6124 kB RssShmem: 0 kB VmData: 30792 kB VmStk: 132 kB VmExe: 592 kB VmLib: 5424 kB VmPTE: 76 kB VmSwap: 0 kB HugetlbPages: 0 kB CoreDumping: 1 THP_enabled: 1 Threads: 4 SigQ: 0/7609 SigPnd: ShdPnd: SigBlk: SigIgn:1000 SigCgt:00018000 CapInh: CapPrm: CapEff: CapBnd:003f CapAmb: NoNewPrivs:0 Seccomp: 0 Speculation_Store_Bypass: thread vulnerable Cpus_allowed: 3 Cpus_allowed_list: 0-1 Mems_allowed: ,,,,,,,,,,,,,,,,,,,,,,,,,,,, ,,,0001 Mems_allowed_list: 0 voluntary_ctxt_switches: 111 nonvoluntary_ctxt_switches:144 Signal: 6 Uname: Linux 5.4.0-21-generic x86_64 UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1872118/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1576559] Re: Refused to switch profile to headset_head_unit: Not connected
(I'm not using Ubuntu for my desktop but I'have had the same problem. I'm running Pulseaudio 13 built with enable_bluez5_native_headset and Bluez 5.54) Solved it by adding headset=native forthe module module-bluetooth-discover in default.pa : load-module module-bluetooth-discover headset=native in ~/.pulse/default.pa (or /etc/pulse/default.pa) then restarting pulseaudio with pulseaudio -k Since Pulseaudio 11.0 has ofono support, "headset=auto" option enabled by default, pactl list shows that both profiles with available: yes Generally when using VoIP application automatically switch bluetooth profile to HSP works , but when not or when switch back to A2DP need to be done annually (for me, Blueman does the job with a few clicks). Sound with HSP profile isn't very good and HFP doesn't seems to work as I haven't setup phonesimp (ref https://www.freedesktop.org/wiki/Software/PulseAudio/Documentation/User/Bluetooth/ ) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1576559 Title: Refused to switch profile to headset_head_unit: Not connected Status in PulseAudio: Unknown Status in pulseaudio package in Ubuntu: Confirmed Bug description: I'm trying to connect a bluetooth-speaker-with-microphone (Mi Bluetooth Speaker) to Ubuntu. It works well as an A2DP sync, but can't use it as a headset with microphone. The device doesn't list in the "Input Devices" by default, and using the sound settings to change the profile of the device to HSP/HFP results in this log message: W: [pulseaudio] module-bluez5-device.c: Refused to switch profile to headset_head_unit: Not connected I'm running Ubuntu 16.04 LTS. I did an upgrade from Ubuntu 15.10. pulseaudio: Installed: 1:8.0-0ubuntu3 bluez: Installed: 5.37-0ubuntu5 To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/1576559/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1878738] Re: program abort by "lh_table_new: calloc failed"
Seems to affect all software which uses this library. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to json-c in Ubuntu. https://bugs.launchpad.net/bugs/1878738 Title: program abort by "lh_table_new: calloc failed" Status in json-c package in Ubuntu: Confirmed Bug description: I wrote small sample program which abort by lh_table_new calloc failed. see this. https://gist.github.com/735eec6fd0869df1facb08da5baa402c To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/json-c/+bug/1878738/+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 1794033] Re: i965: Failed to submit batchbuffer: Bad address
Previous issue (https://gitlab.freedesktop.org/mesa/mesa/-/issues/1680) was closed as duplicated of this one. see https://gitlab.freedesktop.org/mesa/mesa/-/issues/1680#note_328635. ** Bug watch added: gitlab.freedesktop.org/mesa/mesa/-/issues #2134 https://gitlab.freedesktop.org/mesa/mesa/-/issues/2134 ** Bug watch added: gitlab.freedesktop.org/mesa/mesa/-/issues #1680 https://gitlab.freedesktop.org/mesa/mesa/-/issues/1680 ** Changed in: mesa Status: Fix Released => Unknown ** Changed in: mesa Remote watch: gitlab.freedesktop.org/mesa/mesa/issues #1680 => gitlab.freedesktop.org/mesa/mesa/-/issues #2134 -- 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/1794033 Title: i965: Failed to submit batchbuffer: Bad address Status in Mesa: Unknown Status in mesa package in Ubuntu: Confirmed Status in xserver-xorg-video-intel package in Fedora: Unknown Bug description: cpu: Intel® Core™ i5-7500 CPU @ 3.40GHz × 4 gpu: Intel® HD Graphics 630 (Kaby Lake GT2) 00:00.0 Host bridge: Intel Corporation Intel Kaby Lake Host Bridge (rev 05) 00:02.0 VGA compatible controller: Intel Corporation HD Graphics 630 (rev 04) 00:08.0 System peripheral: Intel Corporation Skylake Gaussian Mixture Model xserver-xorg-video-intel: Installed: 2:2.99.917+git20171229-1 Candidate: 2:2.99.917+git20171229-1 ubuntu: 18.04 LTS bionic gnome: 3.28.2 gdm3: Installed: 3.28.2-0ubuntu1.4 Candidate: 3.28.2-0ubuntu1.4 os type: 64 bit kernel: Linux eva1 4.15.0-30-generic #32-Ubuntu SMP Thu Jul 26 17:42:43 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux mesa-va-drivers: Installed: 18.0.5-0ubuntu0~18.04.1 Candidate: 18.0.5-0ubuntu0~18.04.1 from syslog: Sep 24 04:08:16 eva /usr/lib/gdm3/gdm-x-session[1170]: i965: Failed to submit batchbuffer: Bad address Sep 24 04:08:21 eva gnome-terminal-[2597]: gnome-terminal-server: Fatal IO error 11 (Resource temporarily unavailable) on X server :0. Sep 24 04:08:22 eva [2541]: update-notifier: Fatal IO error 11 (Resource temporarily unavailable) on X server :0. Sep 24 04:08:22 eva at-spi-bus-launcher[1274]: XIO: fatal IO error 11 (Resource temporarily unavailable) on X server ":0" - but (followed by pages upon pages of applications within gnome failing.) nothing in kern.log around that time. Singular gnome crash, taking down all applications running within it. Not yet reproduced. gdm successfully started a new session afterwards. Was definitely in a palermoon session on some website or other. To manage notifications about this bug go to: https://bugs.launchpad.net/mesa/+bug/1794033/+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 1794033] Re: i965: Failed to submit batchbuffer: Bad address
Also facing this issue persistently, always when working with little memory available (as #32). My system: Dell XPS 13 9370 - Ubuntu 18.04.4 LTS $ uname -a Linux charon 5.3.0-51-generic #44~18.04.2-Ubuntu SMP Thu Apr 23 14:27:18 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux $ journalctl --since=-2w | grep -A1 'Failed to submit batchbuffer' abr 27 17:17:09 charon org.gnome.Shell.desktop[3359]: i965: Failed to submit batchbuffer: Dirección incorrecta abr 27 17:17:09 charon kernel: mce: CPU3: Core temperature above threshold, cpu clock throttled (total events = 2304) -- abr 27 18:23:14 charon /usr/lib/gdm3/gdm-x-session[3239]: i965: Failed to submit batchbuffer: Bad address abr 27 18:23:14 charon org.gnome.Shell.desktop[3359]: [9820:9820:0427/182314.955599:ERROR:chrome_browser_main_extra_parts_x11.cc(62)] X IO error received (X server probably went away) -- abr 27 21:59:47 charon org.gnome.Shell.desktop[24418]: i965: Failed to submit batchbuffer: Dirección incorrecta abr 27 21:59:48 charon org.gnome.Shell.desktop[24418]: [20630:20630:0427/215948.650070:ERROR:sandbox_linux.cc(374)] InitializeSandbox() called with multiple threads in process gpu-process. -- abr 28 11:32:50 charon /usr/lib/gdm3/gdm-x-session[24313]: i965: Failed to submit batchbuffer: Bad address abr 28 11:32:50 charon dropbox[24681]: dropbox: Fatal IO error 11 (Recurso no disponible temporalmente) on X server :0. -- may 06 11:10:23 charon /usr/lib/gdm3/gdm-x-session[6485]: i965: Failed to submit batchbuffer: Bad address may 06 11:10:23 charon org.gnome.Shell.desktop[6634]: [8456:8456:0506/111023.129635:ERROR:gl_surface_presentation_helper.cc(259)] GetVSyncParametersIfAvailable() failed for 1 times! -- may 08 11:07:53 charon /usr/lib/gdm3/gdm-x-session[6255]: i965: Failed to submit batchbuffer: Bad address may 08 11:07:53 charon dropbox[6661]: dropbox: Fatal IO error 11 (Recurso no disponible temporalmente) on X server :0. -- 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/1794033 Title: i965: Failed to submit batchbuffer: Bad address Status in Mesa: Fix Released Status in mesa package in Ubuntu: Confirmed Status in xserver-xorg-video-intel package in Fedora: Unknown Bug description: cpu: Intel® Core™ i5-7500 CPU @ 3.40GHz × 4 gpu: Intel® HD Graphics 630 (Kaby Lake GT2) 00:00.0 Host bridge: Intel Corporation Intel Kaby Lake Host Bridge (rev 05) 00:02.0 VGA compatible controller: Intel Corporation HD Graphics 630 (rev 04) 00:08.0 System peripheral: Intel Corporation Skylake Gaussian Mixture Model xserver-xorg-video-intel: Installed: 2:2.99.917+git20171229-1 Candidate: 2:2.99.917+git20171229-1 ubuntu: 18.04 LTS bionic gnome: 3.28.2 gdm3: Installed: 3.28.2-0ubuntu1.4 Candidate: 3.28.2-0ubuntu1.4 os type: 64 bit kernel: Linux eva1 4.15.0-30-generic #32-Ubuntu SMP Thu Jul 26 17:42:43 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux mesa-va-drivers: Installed: 18.0.5-0ubuntu0~18.04.1 Candidate: 18.0.5-0ubuntu0~18.04.1 from syslog: Sep 24 04:08:16 eva /usr/lib/gdm3/gdm-x-session[1170]: i965: Failed to submit batchbuffer: Bad address Sep 24 04:08:21 eva gnome-terminal-[2597]: gnome-terminal-server: Fatal IO error 11 (Resource temporarily unavailable) on X server :0. Sep 24 04:08:22 eva [2541]: update-notifier: Fatal IO error 11 (Resource temporarily unavailable) on X server :0. Sep 24 04:08:22 eva at-spi-bus-launcher[1274]: XIO: fatal IO error 11 (Resource temporarily unavailable) on X server ":0" - but (followed by pages upon pages of applications within gnome failing.) nothing in kern.log around that time. Singular gnome crash, taking down all applications running within it. Not yet reproduced. gdm successfully started a new session afterwards. Was definitely in a palermoon session on some website or other. To manage notifications about this bug go to: https://bugs.launchpad.net/mesa/+bug/1794033/+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 1876442] [NEW] chromium causing many audit messages in syslog
Public bug reported: chromium as installed through snap: chromium 81.0.4044.129 1135 latest/stable canonical✓ - $ tail -f /var/log/syslog May 2 12:46:20 master3900x kernel: [56493.196311] audit: type=1326 audit(1588416380.844:3238): auid=4294967295 uid=1000 gid=1000 ses=4294967295 subj==snap.chromium.chromium (enforce) pid=55655 comm="chrome" exe="/snap/chromium/1135/usr/lib/chromium-browser/chrome" sig=0 arch=c03e syscall=203 compat=0 ip=0x7fdf221bdb8f code=0x5 May 2 12:46:20 master3900x kernel: [56493.196389] audit: type=1326 audit(1588416380.844:3239): auid=4294967295 uid=1000 gid=1000 ses=4294967295 subj==snap.chromium.chromium (enforce) pid=55655 comm="chrome" exe="/snap/chromium/1135/usr/lib/chromium-browser/chrome" sig=0 arch=c03e syscall=203 compat=0 ip=0x7fdf221bdb8f code=0x5 May 2 12:46:29 master3900x kernel: [56501.999823] audit: type=1326 audit(1588416389.648:3240): auid=4294967295 uid=1000 gid=1000 ses=4294967295 subj==snap.chromium.chromium (enforce) pid=55655 comm="chrome" exe="/snap/chromium/1135/usr/lib/chromium-browser/chrome" sig=0 arch=c03e syscall=203 compat=0 ip=0x7fdf221bdb8f code=0x5 May 2 12:46:29 master3900x kernel: [56501.35] audit: type=1326 audit(1588416389.648:3241): auid=4294967295 uid=1000 gid=1000 ses=4294967295 subj==snap.chromium.chromium (enforce) pid=55655 comm="chrome" exe="/snap/chromium/1135/usr/lib/chromium-browser/chrome" sig=0 arch=c03e syscall=203 compat=0 ip=0x7fdf221bdb8f code=0x5 May 2 12:46:30 master3900x kernel: [56502.993348] audit: type=1326 audit(1588416390.644:3242): auid=4294967295 uid=1000 gid=1000 ses=4294967295 subj==snap.chromium.chromium (enforce) pid=55655 comm="chrome" exe="/snap/chromium/1135/usr/lib/chromium-browser/chrome" sig=0 arch=c03e syscall=203 compat=0 ip=0x7fdf221bdb8f code=0x5 May 2 12:46:30 master3900x kernel: [56502.993410] audit: type=1326 audit(1588416390.644:3243): auid=4294967295 uid=1000 gid=1000 ses=4294967295 subj==snap.chromium.chromium (enforce) pid=55655 comm="chrome" exe="/snap/chromium/1135/usr/lib/chromium-browser/chrome" sig=0 arch=c03e syscall=203 compat=0 ip=0x7fdf221bdb8f code=0x5 May 2 12:46:30 master3900x kernel: [56503.104490] audit: type=1326 audit(1588416390.752:3244): auid=4294967295 uid=1000 gid=1000 ses=4294967295 subj==snap.chromium.chromium (enforce) pid=55655 comm="chrome" exe="/snap/chromium/1135/usr/lib/chromium-browser/chrome" sig=0 arch=c03e syscall=203 compat=0 ip=0x7fdf221bdb8f code=0x5 May 2 12:46:30 master3900x kernel: [56503.104561] audit: type=1326 audit(1588416390.752:3245): auid=4294967295 uid=1000 gid=1000 ses=4294967295 subj==snap.chromium.chromium (enforce) pid=55655 comm="chrome" exe="/snap/chromium/1135/usr/lib/chromium-browser/chrome" sig=0 arch=c03e syscall=203 compat=0 ip=0x7fdf221bdb8f code=0x5 May 2 12:46:34 master3900x kernel: [56506.398229] audit: type=1326 audit(1588416394.048:3246): auid=4294967295 uid=1000 gid=1000 ses=4294967295 subj==snap.chromium.chromium (enforce) pid=55655 comm="chrome" exe="/snap/chromium/1135/usr/lib/chromium-browser/chrome" sig=0 arch=c03e syscall=203 compat=0 ip=0x7fdf221bdb8f code=0x5 May 2 12:46:34 master3900x kernel: [56506.398318] audit: type=1326 audit(1588416394.048:3247): auid=4294967295 uid=1000 gid=1000 ses=4294967295 subj==snap.chromium.chromium (enforce) pid=55655 comm="chrome" exe="/snap/chromium/1135/usr/lib/chromium-browser/chrome" sig=0 arch=c03e syscall=203 compat=0 ip=0x7fdf221bdb8f code=0x5 May 2 12:46:49 master3900x kernel: [56521.357592] audit: type=1326 audit(1588416409.004:3248): auid=4294967295 uid=1000 gid=1000 ses=4294967295 subj==snap.chromium.chromium (enforce) pid=55655 comm="chrome" exe="/snap/chromium/1135/usr/lib/chromium-browser/chrome" sig=0 arch=c03e syscall=203 compat=0 ip=0x7fdf221bdb8f code=0x5 May 2 12:46:49 master3900x kernel: [56521.357678] audit: type=1326 audit(1588416409.004:3249): auid=4294967295 uid=1000 gid=1000 ses=4294967295 subj==snap.chromium.chromium (enforce) pid=55655 comm="chrome" exe="/snap/chromium/1135/usr/lib/chromium-browser/chrome" sig=0 arch=c03e syscall=203 compat=0 ip=0x7fdf221bdb8f code=0x5 ** Affects: chromium (Ubuntu) Importance: Undecided Status: New ** Package changed: alsa-driver (Ubuntu) => chromium (Ubuntu) -- 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/1876442 Title: chromium causing many audit messages in syslog Status in chromium package in Ubuntu: New Bug description: chromium as installed through
[Touch-packages] [Bug 1875985] Re: [Inspiron 13-5368, Realtek ALC3253, Speaker, Internal] No sound at all after kernel upgrade to 4.15.0-99-generic on Ubuntu 18.04.4
Same issue here on a Dell Inspiron 13-7378 (ALC3253). Audio was working fine on the previous kernel (4.15.0-96-lowlatency) and after update to 4.15.0-99-lowlatency there is no sound from the internal speaker and also the mic is not working. The sound works fine on an external USB device (plantronics P610). -- 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/1875985 Title: [Inspiron 13-5368, Realtek ALC3253, Speaker, Internal] No sound at all after kernel upgrade to 4.15.0-99-generic on Ubuntu 18.04.4 Status in alsa-driver package in Ubuntu: Confirmed Bug description: VERSION="18.04.4 LTS (Bionic Beaver)" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Ubuntu 18.04.4 LTS" Running it in the flavour of Xubuntu. Just like in https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1875916 my sound stopped working with the new kernel "4.15.0-99-generic #100-Ubuntu SMP Wed Apr 22 20:32:56 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux". Rebooting into "4.15.0-96-generic #97-Ubuntu SMP Wed Apr 1 03:25:46 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux" sound works again. With 4.15.0-99-generic I do see a signal on the meters of the sound/volume control app, but physically there is no sound on either internal speakers nor on the headphones. With 4.15.0-96-generic everything is back to normal. My touchpad is working though (#1875916 seems to suggest that the touchpad stops working with 4.15.0-99-generic). ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.15.0-99.100-generic 4.15.18 Uname: Linux 4.15.0-99-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: rkm1814 F pulseaudio CurrentDesktop: XFCE Date: Wed Apr 29 23:45:15 2020 InstallationDate: Installed on 2016-10-20 (1287 days ago) InstallationMedia: Xubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: rkm1814 F pulseaudio Symptom_Jack: Speaker, Internal Symptom_Type: No sound at all Title: [Inspiron 13-5368, Realtek ALC3253, Speaker, Internal] No sound at all UpgradeStatus: Upgraded to bionic on 2018-08-31 (607 days ago) dmi.bios.date: 05/26/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: 01.03.00 dmi.board.name: 0RJ0RW dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr01.03.00:bd05/26/2016:svnDellInc.:pnInspiron13-5368:pvr:rvnDellInc.:rn0RJ0RW:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Inspiron 13-5368 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1875985/+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 905147]
Sorry, it seems that the issue isn't resolved. Okular doesn't save the margins values nor the "Force rasterization" checkbox. If I try to set the values as default, the print tool ignores them while a command-line lp works : lpoptions -p Zebra -o page-bottom=0 -o page-left=0 -o page-right=0 -o page-top=0 -o fitplot Kubuntu 19.04 KDE Plasma Version: 5.16.5 KDE Frameworks Version: 5.62.0 Qt Version: 5.12.4 Quite the same as https://bugs.kde.org/show_bug.cgi?id=404510 or https://bugs.kde.org/show_bug.cgi?id=383697 So I tried with Kate and the values are saved in katerc : [Kate Print Settings][Margins] bottom=0 left=0 right=0 top=0 Strangely I just migrated from Kubuntu 14.04 (KDE 4.13) to Kubuntu 19.04 (KDE 5.62) and I didn't face this issue on the previous computer. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qt4-x11 in Ubuntu. https://bugs.launchpad.net/bugs/905147 Title: QPrinterDialog ignores default settings from CUPS Status in Qt: Won't Fix Status in qt4-x11 package in Ubuntu: Fix Released Bug description: KDE as well as many QT-Applications use QPrinterDialog as their printing dialog. Thing is: This dialog ignores default settings defined in CUPS - it doesn't even remember that last settings that were chosen. I know this is a QT issue but I kindly ask you not to close this bug as upstream and here's why: 1. This bug has been around for years now - the first report to Nokia about was back in 2008 if I recall correctly. 2. A user doesn't know and doesn't care about whose fault it is. He just knows, that he set his printer settings to default to duplex in CUPS and that his QT applications don't print duplex. At first he might shrug and set duplex in the dialog. Next time the setting is back to simplex. The same is true for other options like collate and color settings. It's just a huge usability issue. 3. The fix below has been adopted by other major distributions for quite some time now. It works for duplex, collate and color settings. 4. It saves lots and lots of trees! I think it does not work for paper size and in general it doesn't fix the problem that QT can't remember the settings you choose in the print dialog. The paper size may be read from the configured defaults easily, too, but settings saving may be a bit harder. However, you'd implement this fix, you'd do something VERY good for Ubuntu - especially since 12.04 is meant to be an LTS release! If you could even improve the fix that would be huge! Here's the fix from the KDE bug tracker: https://bugs.kde.org/attachment.cgi?id=41187 More info: https://bugs.kde.org/show_bug.cgi?id=180051 https://bugreports.qt.nokia.com//browse/QTBUG-6471 (and https://bugreports.qt.nokia.com/browse/QTBUG-23037) and other bug reports from the comments there. For Oneiric I've made a patched version in a PPA of mine that you could look at. You'll see it's really a minor modification that doesn't take any effort at all to implement. You can find it here: https://launchpad.net/~dhertel/+archive/myfixes As a side note: I know that KDE is not the default environment in Ubuntu, but it's getting more important for people since Gnome2 officially is no more and Unity isn't exactly better when one doesn't even like Gnome3 to begin with. So I hope this makes it into Precise... Cheers, Dominik To manage notifications about this bug go to: https://bugs.launchpad.net/qt/+bug/905147/+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 1871766] [NEW] Totem : Playing a corrupt video can result in full system crash - Linux Kernel unresponsive
Public bug reported: # DESCRIPTION : Playing a "partially corrupt" video starts normally, then starts showing visual artifacts (apparition of a red gradient on the bottom of the viewframe and a green gradient on top), which increase in intensity over time (can result in brigth blinking, black bars appearing in the middle of the video, etc.) and can, at some point, result in a complete system freeze. Once the system is frozen, the mouse can still move, but nothing else on the screen reacts - neither on click nor on hover. After a few seconds, the screens (I have two screens) go black briefly, then re-appear to show complete noise, with a 64x64-pixel-box of lighter noise around where the mouse is. The mouse can still move normally (the lighter 64x64 box moves at the same speed my mouse moved before the crash - no lag, no FPS drop). # IMPORTANT BEHAVIORAL OBSERVATIONS : - Alt + SysReq + R, E, I, S, U, B DOES NOT RESPOND (that's why I believe the kernel is affected). I tried several times, waiting a full second between each input; no response. I believe I was doing it correctly because I have used that technique successfully several times in the past on different systems. - The bug first occurred a few months ago, and since then I have updated my system several times (using Ubuntu's built-in graphical update notifier - I've installed everything update I saw), and none of the updates have fixed the problem. I did notice, though, that lately the bug was harder to reproduce, but I have no idea if that correlation means causation or not. - The same physical machine runs another instance of the exact same operating system (Ubuntu 18.04.4 LTS) on a different hard drive. I just switch hard drives manually to change systems. The other system has always used VLC to play videos as Totem lacks codecs to play the videos I want. It (the other system) suffers no major glitch, AFAIK. # STEPS TO REPRODUCE (might not work on different system - read further for why I believe it is necessary to report nevertheless): - Play a partially corrupt video file (I provided two in the attachment) with Totem and wait. I believe - but I am not sure - that stressing the application (for example, dragging the video scroller while the video plays) increases the likeliness of visual artifacts appearing. Usually, the green-at-the-top and red-at-the-bottom appear quite easily, the rest comes by letting the whole thing run in the background for a few minutes, maybe a few hours at most (never took up to an hour on my side). # WHY I THINK IT'S AN IMPORTANT ISSUE (but not a "security issue" per se) : The entire operating system was rendered unresponsive. While some visual cues appearing on the video may hint that everything isn't right, if you were working on something while the video plays and it crashes, you lost everything you were doing back to the last point you saved. I also believe - though I could be wrong - the the Kernel was dead as well, since REISUB doesn't work, as mentioned earlier. The bug shows it is possible for an ordinary application to cause a complete denial of service on the whole system. No matter what the problem inside Totem is, it has the power to creep down to the whole system (and maybe the kernel); an application running in user space shouldn't have such power. However, I struggled to find clear, easily reproducible steps that could result in a crash 100% of the time on any Ubuntu 18.04.4 LTS system. I therefore cannot guarantee it isn't just a problem on my end (but even if it is, I would like to understand how a bug in Totem can have such a huge impact). If my reasoning is wrong, then I apologize for the inconvenience. Feel free to classify my report the way it should be if need there is. # FILES ATTACHED : - 2020-04-09 01-04-59.mp4 : (I apologize for the unprofessional video... I tested it on a meme) A recording made with OBS of the apparition of the visual artifacts. The artifacts are essentially concentrated in the first minute of the video - the rest shows only the red/green gradients, which are still disturbing but much less aggressive on the eye. At the very end of the video, I close the target file and re-open it; fatal decision, it was at that moment that my computer roze and stopped responding. A few moments later, the screen went black, and showed the strange noise vision I described earlier and that I show in the other video file. - video20200409_011018907.mp4 : The other video file, recorded this time with my phone, showing the screen once it has switched to it's "noisy" state described earlier. There was no sound playing from the speakers, so I recorded with no sound (thanks Ubuntu Touch for that option). Also, my mouse froze after some time. - Screenshot from 2020-04-09 01-15-02.png : When re-playing the video file (which was obviously partly corrupt, since OBS crashed with the
