[Touch-packages] [Bug 298617] Re: Popularity Contest should be uninstallable
https://discourse.ubuntu.com/t/popcon-to-be-removed-from-the-standard- seed/17238 Currently invalid bug as of 2022 - https://packages.ubuntu.com/jammy/ubuntu-standard ** Changed in: ubuntu-meta (Ubuntu) Status: Triaged => Invalid ** Changed in: ubuntu-meta (Ubuntu) Status: Invalid => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/298617 Title: Popularity Contest should be uninstallable Status in popularity-contest package in Ubuntu: Fix Released Status in ubuntu-meta package in Ubuntu: Fix Released Bug description: Binary package hint: popularity-contest Popularity Contest is (at least in hardy) enabled by default. It now has a dependency with ubuntu-standard, and no menu item in "services". This means that switching it off cannot be done via the GNOME UI. There are several reasons why a user or administrator would like to switch it off. I see no reason for the dependency with ubuntu-standard, except in order to FORCE users to enable it when using Ubuntu. Making it recommended for ubuntu-standard, instead of a hard dependency would enable me to uninstall it using synaptic package manager. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/popularity-contest/+bug/298617/+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 2018342] [NEW] Undefined symbol nghttp2_option_set_no_rfc9113_leading_and_trailing_ws_validation
Public bug reported: I updated Ubuntu from 22.10 to 23.04 this morning and have this issue when NetworkManager starts : > NetworkManager: symbol lookup error: /lib/x86_64-linux-gnu/libcurl- gnutls.so.4: undefined symbol: nghttp2_option_set_no_rfc9113_leading_and_trailing_ws_validation I tried to remove/reinstall libcurl and network-manager and all dependencies. I created this ticket on the Curl repo : https://github.com/curl/curl/tree/d8df0d6db7441b6e14920a7e16a10e32bdc9c7ae It was close because : > This is not a curl bug. This is libcurl having been built with an nghttp2 version >= 1.50.0 (which has that function) and then at run-time it uses an older nghttp2 library that doesn't have the function. Versions : libcurl4 : 7.88.1-8ubuntu1 libcurl3-gnu-tls : 7.88.1-8ubuntu1 libnghttp2-dev : 1.52.0-1 libnghttp2-14 : 1.52.0-1 network-manager : 1.42.4 operating system : Linux ubuntu 6.2.0-20-generic #20-Ubuntu SMP PREEMPT_DYNAMIC Thu Apr 6 07:48:48 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux ** Affects: curl (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to curl in Ubuntu. https://bugs.launchpad.net/bugs/2018342 Title: Undefined symbol nghttp2_option_set_no_rfc9113_leading_and_trailing_ws_validation Status in curl package in Ubuntu: New Bug description: I updated Ubuntu from 22.10 to 23.04 this morning and have this issue when NetworkManager starts : > NetworkManager: symbol lookup error: /lib/x86_64-linux-gnu/libcurl- gnutls.so.4: undefined symbol: nghttp2_option_set_no_rfc9113_leading_and_trailing_ws_validation I tried to remove/reinstall libcurl and network-manager and all dependencies. I created this ticket on the Curl repo : https://github.com/curl/curl/tree/d8df0d6db7441b6e14920a7e16a10e32bdc9c7ae It was close because : > This is not a curl bug. This is libcurl having been built with an nghttp2 version >= 1.50.0 (which has that function) and then at run- time it uses an older nghttp2 library that doesn't have the function. Versions : libcurl4 : 7.88.1-8ubuntu1 libcurl3-gnu-tls : 7.88.1-8ubuntu1 libnghttp2-dev : 1.52.0-1 libnghttp2-14 : 1.52.0-1 network-manager : 1.42.4 operating system : Linux ubuntu 6.2.0-20-generic #20-Ubuntu SMP PREEMPT_DYNAMIC Thu Apr 6 07:48:48 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/curl/+bug/2018342/+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 2017984] Re: Microsoft Edge "Save as" dialog is not in dark mode
Sorry for the delay. The same behavior is in firefox browser ** Attachment added: "Issue in firefox" https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/2017984/+attachment/5670431/+files/Screenshot%20from%202023-05-02%2023-07-35.png -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/2017984 Title: Microsoft Edge "Save as" dialog is not in dark mode Status in gtk+3.0 package in Ubuntu: Incomplete Status in yaru-theme package in Ubuntu: New Bug description: After update to 23.04 I'm having the following issue. In dark mode of Yaru-dark theme, when downloading the file and choosing the "Save as" option - popup window for folder selection is not in dark mode. When using Xorg session problem is not reproduced. The same applies for upload logic. 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] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Apr 28 12:31:55 2023 DistUpgraded: 2023-04-25 21:06:12,927 DEBUG icon theme changed, re-reading DistroCodename: lunar DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation TigerLake-LP GT2 [Iris Xe Graphics] [8086:9a49] (rev 01) (prog-if 00 [VGA controller]) Subsystem: Lenovo TigerLake-LP GT2 [Iris Xe Graphics] [17aa:508f] InstallationDate: Installed on 2022-08-26 (244 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) MachineType: LENOVO 20X4S1GH08 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.2.0-20-generic root=/dev/mapper/vgubuntu-root ro usbcore.autosuspend=-1 quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to lunar on 2023-04-25 (2 days ago) dmi.bios.date: 11/22/2022 dmi.bios.release: 1.60 dmi.bios.vendor: LENOVO dmi.bios.version: R1JET60W (1.60 ) dmi.board.asset.tag: Not Available dmi.board.name: 20X4S1GH08 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.48 dmi.modalias: dmi:bvnLENOVO:bvrR1JET60W(1.60):bd11/22/2022:br1.60:efr1.48:svnLENOVO:pn20X4S1GH08:pvrThinkPadL15Gen2:rvnLENOVO:rn20X4S1GH08:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20X4_BU_Think_FM_ThinkPadL15Gen2: dmi.product.family: ThinkPad L15 Gen 2 dmi.product.name: 20X4S1GH08 dmi.product.sku: LENOVO_MT_20X4_BU_Think_FM_ThinkPad L15 Gen 2 dmi.product.version: ThinkPad L15 Gen 2 dmi.sys.vendor: LENOVO 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 N/A 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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/2017984/+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 2018330] [NEW] routel script gives shift errors
Public bug reported: The routel(8) shell script is meant to format the output of ip(8) commands for human viewing, but the script is not robust enough. Running 22.04.2 LTS jammy jellyfish, freshly installed on an AWS EC2 instance and then "apt upgrade"d. (It's headless and remote, so it can't submit bug reports. I generated an apport file, but have no other Ubuntu system that could re-parse it to submit the report. But it's here if it would be useful.) The iproute2 package is: iproute2: Installed: 5.15.0-1ubuntu2 Candidate: 5.15.0-1ubuntu2 Version table: *** 5.15.0-1ubuntu2 500 500 http://us-east-2.ec2.archive.ubuntu.com/ubuntu jammy/main amd64 Packages 100 /var/lib/dpkg/status Here's the raw output of ip(8): $ ip route list table 0 default via 10.37.67.1 dev eth0 proto dhcp src 10.37.67.187 metric 100 10.37.64.2 via 10.37.67.1 dev eth0 proto dhcp src 10.37.67.187 metric 100 10.37.64.231 via 10.37.67.1 dev eth0 proto dhcp src 10.37.67.187 metric 100 10.37.65.30 via 10.37.67.1 dev eth0 proto dhcp src 10.37.67.187 metric 100 10.37.67.0/24 dev eth0 proto kernel scope link src 10.37.67.187 metric 100 10.37.67.1 dev eth0 proto dhcp scope link src 10.37.67.187 metric 100 local 10.37.67.187 dev eth0 table local proto kernel scope host src 10.37.67.187 broadcast 10.37.67.255 dev eth0 table local proto kernel scope link src 10.37.67.187 local 127.0.0.0/8 dev lo table local proto kernel scope host src 127.0.0.1 local 127.0.0.1 dev lo table local proto kernel scope host src 127.0.0.1 broadcast 127.255.255.255 dev lo table local proto kernel scope link src 127.0.0.1 ::1 dev lo proto kernel metric 256 pref medium fe80::/64 dev eth0 proto kernel metric 256 pref medium local ::1 dev lo table local proto kernel metric 0 pref medium local fe80::458:96ff:fe61:6829 dev eth0 table local proto kernel metric 0 pref medium multicast ff00::/8 dev eth0 table local proto kernel metric 256 pref medium Running routel, however, yields this: $ routel targetgateway sourceprotoscopedev tbl default 10.37.67.110.37.67.187 dhcpeth0 10.37.64.2 10.37.67.110.37.67.187 dhcpeth0 10.37.64.231 10.37.67.110.37.67.187 dhcpeth0 10.37.65.30 10.37.67.110.37.67.187 dhcpeth0 10.37.67.0/ 2410.37.67.187 kernel link eth0 10.37.67.1 10.37.67.187 dhcp link eth0 10.37.67.187 local10.37.67.187 kernel host eth0 local 10.37.67.255 broadcast10.37.67.187 kernel link eth0 local 127.0.0.0/ 8local 127.0.0.1 kernel host lo local 127.0.0.1 local 127.0.0.1 kernel host lo local 127.255.255.255 broadcast 127.0.0.1 kernel link lo local /usr/bin/routel: 48: shift: ::1 kernel lo fe80::/ 64 kerneleth0 ::1 local kernel lo local fe80::458:96ff:fe61:6829 local kernel eth0 local can't shift that many Splitting stdout and stderr for readability: $ routel 2> /tmp/err targetgateway sourceprotoscopedev tbl default 10.37.67.110.37.67.187 dhcpeth0 10.37.64.2 10.37.67.110.37.67.187 dhcpeth0 10.37.64.231 10.37.67.110.37.67.187 dhcpeth0 10.37.65.30 10.37.67.110.37.67.187 dhcpeth0 10.37.67.0/ 2410.37.67.187 kernel link eth0 10.37.67.1 10.37.67.187 dhcp link eth0 10.37.67.187 local10.37.67.187 kernel host eth0 local 10.37.67.255 broadcast10.37.67.187 kernel link eth0 local 127.0.0.0/ 8local 127.0.0.1 kernel host lo local 127.0.0.1 local 127.0.0.1 kernel host lo local 127.255.255.255 broadcast 127.0.0.1 kernel link lo local ::1 kernel lo fe80::/ 64 kerneleth0 ::1 local kernel lo local fe80::458:96ff:fe61:6829 local kernel eth0 local $ cat /tmp/err /usr/bin/routel: 48: shift: can't shift that many $ It's giving the same errors as in Debian bug 875476 some six years ago, which was "fixed in upstream" and then apparently broken again. ** Affects: avahi (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because
[Touch-packages] [Bug 535517] Re: netatalk fails to generate unique server signatures
For the record: This bug was fixed with v2.1.0 -- https://sourceforge.net/p/netatalk/bugs/362/ -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to coreutils in Ubuntu. https://bugs.launchpad.net/bugs/535517 Title: netatalk fails to generate unique server signatures Status in coreutils package in Ubuntu: Invalid Status in eglibc package in Ubuntu: New Status in glibc package in Ubuntu: New Status in netatalk package in Ubuntu: Triaged Bug description: Binary package hint: netatalk Description: Ubuntu 9.10 Release: 9.10 ii netatalk 2.0.4~beta2-5ubuntu2 AppleTalk user binaries NetATalk fails to generate a unique server signature. Analysis of client/server communication reveals that both NetATalk servers here report the signature 01017F0001017F0001017F0001017F00 . This confuses Mac clients, resulting in them apparently randomly directing AFP requests to one server or the other. Users will connect to SERVER1 and get a volume list from SERVER2 or vice versa. The netatalk code for generating server signatures (etc/afpd/status.c:191) uses the libc gethostid() call to obtain a 32-bit unique identifier for the host. GNU Libc's man page for gethostid(3) notes that: "In the glibc implementation, the hostid is stored in the file /etc/hostid. (In glibc versions before 2.2, the file /var/adm/hostid was used.) "In the glibc implementation, if gethostid() cannot open the file containing the host ID, then it obtains the hostname using gethostname(2), passes that hostname to gethostbyname_r(3) in order to obtain the host's IPv4 address, and returns a value obtained by bit-twiddling the IPv4 address. (This value may not be unique.)" Ubuntu systems do not have any /etc/hostid by default, so glibc falls back on gethostbyname_r(3). However, Ubuntu systems' /etc/hosts files map the hostname to 127.0.0.1: 127.0.0.1 localhost 127.0.1.1 HOSTNAME.localnetHOSTNAME so gethostbyname_r for the hostname in /etc/hostname will always return 127.0.0.1 . gethostid(3) will therefore always return the same value, and NetATalk's system id will always be the same on different Ubuntu hosts. WORKAROUND: To each line in your afpd.conf, append an explicit: -signature user:SERVERNAME (if you have more than one line in afpd.conf, make sure the signature is unique for each one). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/coreutils/+bug/535517/+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 2018327] [NEW] package initramfs-tools 0.140ubuntu13.1 failed to install/upgrade: el subproceso instalado paquete initramfs-tools script post-installation devolvió el código de s
Public bug reported: I receive error msg ProblemType: Package DistroRelease: Ubuntu 22.04 Package: initramfs-tools 0.140ubuntu13.1 ProcVersionSignature: Ubuntu 5.19.0-40.41~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-40-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu82.4 AptOrdering: openssl:amd64: Install NULL: ConfigurePending Architecture: amd64 CasperMD5CheckResult: unknown Date: Tue May 2 20:34:26 2023 ErrorMessage: el subproceso instalado paquete initramfs-tools script post-installation devolvió el código de salida de error 1 InstallationDate: Installed on 2020-05-25 (1071 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) PackageArchitecture: all Python3Details: /usr/bin/python3.10, Python 3.10.6, python3-minimal, 3.10.6-1~22.04 PythonDetails: N/A RelatedPackageVersions: dpkg 1.21.1ubuntu2.1 apt 2.4.9 SourcePackage: initramfs-tools Title: package initramfs-tools 0.140ubuntu13.1 failed to install/upgrade: el subproceso instalado paquete initramfs-tools script post-installation devolvió el código de salida de error 1 UpgradeStatus: Upgraded to jammy on 2022-08-24 (251 days ago) ** Affects: initramfs-tools (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package jammy -- 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/2018327 Title: package initramfs-tools 0.140ubuntu13.1 failed to install/upgrade: el subproceso instalado paquete initramfs-tools script post-installation devolvió el código de salida de error 1 Status in initramfs-tools package in Ubuntu: New Bug description: I receive error msg ProblemType: Package DistroRelease: Ubuntu 22.04 Package: initramfs-tools 0.140ubuntu13.1 ProcVersionSignature: Ubuntu 5.19.0-40.41~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-40-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu82.4 AptOrdering: openssl:amd64: Install NULL: ConfigurePending Architecture: amd64 CasperMD5CheckResult: unknown Date: Tue May 2 20:34:26 2023 ErrorMessage: el subproceso instalado paquete initramfs-tools script post-installation devolvió el código de salida de error 1 InstallationDate: Installed on 2020-05-25 (1071 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) PackageArchitecture: all Python3Details: /usr/bin/python3.10, Python 3.10.6, python3-minimal, 3.10.6-1~22.04 PythonDetails: N/A RelatedPackageVersions: dpkg 1.21.1ubuntu2.1 apt 2.4.9 SourcePackage: initramfs-tools Title: package initramfs-tools 0.140ubuntu13.1 failed to install/upgrade: el subproceso instalado paquete initramfs-tools script post-installation devolvió el código de salida de error 1 UpgradeStatus: Upgraded to jammy on 2022-08-24 (251 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/2018327/+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 2018305] Re: Bluetooth headset suddenly stops playback (until power is turned off and on again)"
bluetooth audio isn't handled by alsa, but by pulseaudio directly. ** Package changed: alsa-driver (Ubuntu) => pulseaudio (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/2018305 Title: Bluetooth headset suddenly stops playback (until power is turned off and on again)" Status in pulseaudio package in Ubuntu: New Bug description: When watching videos using video players (SM Player, VLC, etc.) and repeatedly using the space key to toggle play/pause, the sound output to the Bluetooth headset stops working after a short while. When the Bluetooth headset's power is turned off, the sound that was not working immediately starts coming out of the built-in speaker. It's as if the sound data that was trapped in a queue suddenly pours out when the blockage is cleared. The same symptom occurs not only in video players, but also in other learning programs and places where keyboard or mouse clicks are repeated. Whenever the sound gets blocked, I have to repeatedly turn the Bluetooth headset off and on again. This issue occurs very frequently. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: alsa-base 1.0.25+dfsg-0ubuntu7 ProcVersionSignature: Ubuntu 5.19.0-41.42~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-41-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: fts2436 F pulseaudio /dev/snd/controlC1: fts2436 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue May 2 22:43:12 2023 InstallationDate: Installed on 2022-07-09 (297 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Title: Bluetooth sound card not detected UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/20/2021 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P03AJK.039.210920.SH dmi.board.asset.tag: No Asset Tag dmi.board.name: NT850XCR-HD7AB dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.board.version: SGLFREEDOS-C00-R000-S+1.0. dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP03AJK.039.210920.SH:bd09/20/2021:br5.17:svnSAMSUNGELECTRONICSCO.,LTD.:pn850XCJ:pvrP03AJK:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNT850XCR-HD7AB:rvrSGLFREEDOS-C00-R000-S+1.0.:cvnSAMSUNGELECTRONICSCO.,LTD.:ct10:cvrN/A:skuSCAI-A5A5-A5A5-A5A5-PAJK: dmi.product.family: Odyssey Series dmi.product.name: 850XCJ dmi.product.sku: SCAI-A5A5-A5A5-A5A5-PAJK dmi.product.version: P03AJK dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/2018305/+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 2018305] Re: Bluetooth headset suddenly stops playback (until power is turned off and on again)"
** Package changed: ubuntu => alsa-driver (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/2018305 Title: Bluetooth headset suddenly stops playback (until power is turned off and on again)" Status in alsa-driver package in Ubuntu: New Bug description: When watching videos using video players (SM Player, VLC, etc.) and repeatedly using the space key to toggle play/pause, the sound output to the Bluetooth headset stops working after a short while. When the Bluetooth headset's power is turned off, the sound that was not working immediately starts coming out of the built-in speaker. It's as if the sound data that was trapped in a queue suddenly pours out when the blockage is cleared. The same symptom occurs not only in video players, but also in other learning programs and places where keyboard or mouse clicks are repeated. Whenever the sound gets blocked, I have to repeatedly turn the Bluetooth headset off and on again. This issue occurs very frequently. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: alsa-base 1.0.25+dfsg-0ubuntu7 ProcVersionSignature: Ubuntu 5.19.0-41.42~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-41-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: fts2436 F pulseaudio /dev/snd/controlC1: fts2436 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue May 2 22:43:12 2023 InstallationDate: Installed on 2022-07-09 (297 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Title: Bluetooth sound card not detected UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/20/2021 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P03AJK.039.210920.SH dmi.board.asset.tag: No Asset Tag dmi.board.name: NT850XCR-HD7AB dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.board.version: SGLFREEDOS-C00-R000-S+1.0. dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP03AJK.039.210920.SH:bd09/20/2021:br5.17:svnSAMSUNGELECTRONICSCO.,LTD.:pn850XCJ:pvrP03AJK:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNT850XCR-HD7AB:rvrSGLFREEDOS-C00-R000-S+1.0.:cvnSAMSUNGELECTRONICSCO.,LTD.:ct10:cvrN/A:skuSCAI-A5A5-A5A5-A5A5-PAJK: dmi.product.family: Odyssey Series dmi.product.name: 850XCJ dmi.product.sku: SCAI-A5A5-A5A5-A5A5-PAJK dmi.product.version: P03AJK dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/2018305/+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 2018132] Re: wifi connection lost on firefox crash
No problem. I think it is a new bug, unrelated to any of my previous problems. Specifically, following your step-by-step guidance: 1. nothing found here 2. nothing related found here, but some bugs at the time of new fresh OS install (many days before the new bug submitted) I don't know if this helps, but recently the firefox snap has been refreshed to a new version and if I remember correctly the submitted bug found after that time. Additionally, the black window bug when starting firefox snap remains, not as usual as before. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/2018132 Title: wifi connection lost on firefox crash Status in network-manager package in Ubuntu: Incomplete Bug description: firefox snap occasionally crashes, ie shown a black screen on startup. lately, when it crashes, nm-applet disappears from the tray without disconnecting from the router. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: network-manager 1.42.4-1ubuntu2 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 CRDA: N/A CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sat Apr 29 11:13:03 2023 InstallationDate: Installed on 2023-04-24 (4 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418) IpRoute: default via 192.168.1.1 dev wlo1 proto dhcp src 192.168.1.3 metric 600 192.168.1.0/24 dev wlo1 proto kernel scope link src 192.168.1.3 metric 600 ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-dev: DEVICETYPE STATE IP4-CONNECTIVITY IP6-CONNECTIVITY DBUS-PATH CONNECTION CON-UUID CON-PATH wlo1 wifi connected full full /org/freedesktop/NetworkManager/Devices/2 Forthnet-4jPPK eb56363e-28c9-432a-864b-cebcedbfdacf /org/freedesktop/NetworkManager/ActiveConnection/2 loloopback connected (externally) unknown unknown /org/freedesktop/NetworkManager/Devices/1 lo ccbf9b80-8294-485c-bc1c-3050ad48b3d9 /org/freedesktop/NetworkManager/ActiveConnection/1 p2p-dev-wlo1 wifi-p2p disconnectednone none /org/freedesktop/NetworkManager/Devices/3 -- -- -- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.42.4 connected started full enabled enabled enabled missing enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/2018132/+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 2018132] Re: wifi connection lost on firefox crash
Thank you for taking the time to report this bug and helping to make Ubuntu better. It sounds like some part of the system has crashed. To help us find the cause of the crash please follow these steps: 1. Look in /var/crash for crash files and if found run: ubuntu-bug YOURFILE.crash Then tell us the ID of the newly-created bug. 2. If step 1 failed then look at https://errors.ubuntu.com/user/ID where ID is the content of file /var/lib/whoopsie/whoopsie-id on the machine. Do you find any links to recent problems on that page? If so then please send the links to us. Please take care to avoid attaching .crash files to bugs as we are unable to process them as file attachments. It would also be a security risk for yourself. ** Changed in: network-manager (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/2018132 Title: wifi connection lost on firefox crash Status in network-manager package in Ubuntu: Incomplete Bug description: firefox snap occasionally crashes, ie shown a black screen on startup. lately, when it crashes, nm-applet disappears from the tray without disconnecting from the router. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: network-manager 1.42.4-1ubuntu2 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 CRDA: N/A CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sat Apr 29 11:13:03 2023 InstallationDate: Installed on 2023-04-24 (4 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418) IpRoute: default via 192.168.1.1 dev wlo1 proto dhcp src 192.168.1.3 metric 600 192.168.1.0/24 dev wlo1 proto kernel scope link src 192.168.1.3 metric 600 ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-dev: DEVICETYPE STATE IP4-CONNECTIVITY IP6-CONNECTIVITY DBUS-PATH CONNECTION CON-UUID CON-PATH wlo1 wifi connected full full /org/freedesktop/NetworkManager/Devices/2 Forthnet-4jPPK eb56363e-28c9-432a-864b-cebcedbfdacf /org/freedesktop/NetworkManager/ActiveConnection/2 loloopback connected (externally) unknown unknown /org/freedesktop/NetworkManager/Devices/1 lo ccbf9b80-8294-485c-bc1c-3050ad48b3d9 /org/freedesktop/NetworkManager/ActiveConnection/1 p2p-dev-wlo1 wifi-p2p disconnectednone none /org/freedesktop/NetworkManager/Devices/3 -- -- -- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.42.4 connected started full enabled enabled enabled missing enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/2018132/+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 1992454] Re: iptables: segfault when renaming a chain
Adjusting the DEP8 tests in all releases. Bionic doesn't even have the test runner, so I just added the new segfault test as an individual script call. Focal has the test runner, but many tests fail, so I'm using the runner to run just this new test (as per your debdiff). Jammy and Kinetic can run all tests it seems. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to iptables in Ubuntu. https://bugs.launchpad.net/bugs/1992454 Title: iptables: segfault when renaming a chain Status in iptables package in Ubuntu: Fix Released Status in iptables source package in Bionic: In Progress Status in iptables source package in Focal: In Progress Status in iptables source package in Jammy: In Progress Status in iptables source package in Kinetic: In Progress Bug description: [ Impact ] * An explanation of the effects of the bug on users This is the description for the upstream fix of this bug[1] : This is an odd bug: If the number of chains is right and one renames the last one in the list, libiptc dereferences a NULL pointer. * An explanation of the effects of the bug on users and * justification for backporting the fix to the stable release. Without this patch, users may experience segmentation fault when using the following versions of iptables : - Bionic : iptables - Focal : iptables - Jammy : iptables-legacy * In addition, it is helpful, but not required, to include an explanation of how the upload fixes this bug. The upstream fix adjust the size of the chain_index if the element is the last chain in the list. [1] http://git.netfilter.org/iptables/commit/?id=97bf4e68fc0794adba3243fd96f40f4568e7216f [ Test Plan ] * detailed instructions how to reproduce the bug The following code (adapted from the upstream commit to work on Kinetic) may be used to reproduce the issue : 8< #!/bin/bash # # Cover for a bug in libiptc: # - the chain 'node-98-tmp' is the last in the list sorted by name # - there are 81 chains in total, so three chain index buckets # - the last index bucket contains only the 'node-98-tmp' chain # => rename temporarily removes it from the bucket, leaving a NULL bucket # behind which is dereferenced later when inserting the chain again with new # name again ( echo "*filter" for chain in node-1 node-10 node-101 node-102 node-104 node-107 node-11 node-12 node-13 node-14 node-15 node-16 node-17 node-18 node-19 node-2 node-20 node-21 node-22 node-23 node-25 node-26 node-27 node-28 node-29 node-3 node-30 node-31 node-32 node-33 node-34 node-36 node-37 node-39 node-4 node-40 node-41 node-42 node-43 node-44 node-45 node-46 node-47 node-48 node-49 node-5 node-50 node-51 node-53 node-54 node-55 node-56 node-57 node-58 node-59 node-6 node-60 node-61 node-62 node-63 node-64 node-65 node-66 node-68 node-69 node-7 node-70 node-71 node-74 node-75 node-76 node-8 node-80 node-81 node-86 node-89 node-9 node-92 node-93 node-95 node-98-tmp; do echo ":$chain - [0:0]" done echo "COMMIT" ) | $XT_MULTI iptables-legacy-restore $XT_MULTI iptables-legacy -E node-98-tmp node-98 exit $? >8 [ Where problems could occur ] For Jammy and onward, only users of the -legacy commands may be affected. Since Jammy, iptables uses the new nft libraries which are not affected by the bug. For Bionic and Focal users, the regular iptables command is affected by the change. As stated in the manpage : E, --rename-chain old-chain new-chain Rename the user specified chain to the user supplied name. This is cosmetic, and has no effect on the structure of the table. In case of a problem, only the modification of the name would be affected as this is clearly outlined as a cosmetic only change. [ Other Info ] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/iptables/+bug/1992454/+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 2017999] Re: tzdata 2023c-0ubuntu0.22.04.1 might have some inconsistency
Wrote attached test case to catch the inconsistencies (patch attached) and forwarded to upstream: https://mm.icann.org/pipermail/tz/2023-May/032937.html ** Patch added: "0001-Add-autopkgtest-test-case-for-post-1970-symlink-cons.patch" https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/2017999/+attachment/5670328/+files/0001-Add-autopkgtest-test-case-for-post-1970-symlink-cons.patch -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tzdata in Ubuntu. https://bugs.launchpad.net/bugs/2017999 Title: tzdata 2023c-0ubuntu0.22.04.1 might have some inconsistency Status in tzdata package in Ubuntu: Confirmed Bug description: compared to 2023c-0ubuntu0.22.04.0 - America/Ensenada->only dst changes until 2022 are shown - Atlantic/Jan_Mayen->now valid data is shown - Europe/Tiraspol->only dst changes until 2010 are shown To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/2017999/+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 2018262] Re: nm-connection-editor exits with coredump when importing ovpn file
Thank you for the bug report, upstream pushed a fix in their vcs https://gitlab.gnome.org/GNOME/network-manager-applet/-/commit/01281fae ** Package changed: network-manager (Ubuntu) => network-manager-applet (Ubuntu) ** Changed in: network-manager-applet (Ubuntu) Importance: Undecided => High ** Changed in: network-manager-applet (Ubuntu) Status: New => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/2018262 Title: nm-connection-editor exits with coredump when importing ovpn file Status in network-manager-applet package in Ubuntu: Fix Committed Bug description: Software versions: Networkmanager: 1.42.6-1 nm-connection-editor: 1.32.0-1 networkmanager-openvpn: 1.10.2-1 openvpn: 2.6.2-1 Arch Linux kernel: 6.2.13-zen-1-zen While trying to import an ovpn file downloaded from NordVPN, nm- connection-editor exits with a coredump. Downgrading to nm-connection-editor ver 1.30.0-1 allowed me to import the configuration. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager-applet/+bug/2018262/+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 2010561] Re: The Netplan Everywhere NetworkManager fails to supply Netplan with networking information until a connection is deleted and re-created
** Merge proposal linked: https://code.launchpad.net/~slyon/network-manager/+git/network-manager/+merge/423735 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/2010561 Title: The Netplan Everywhere NetworkManager fails to supply Netplan with networking information until a connection is deleted and re-created Status in netplan: Invalid Status in network-manager package in Ubuntu: Fix Committed Bug description: Steps to reproduce: 1. Install Ubuntu Lunar or a flavor thereof onto physical hardware with a WiFi adapter. (I used Lubuntu Lunar.) 2. Connect to WiFi and install all updates. 3. Enable the Netplan Everywhere PPA and install the updated NetworkManager from it (further details at https://discourse.ubuntu.com/t/call-for-testing-networkmanager-yaml-settings/32420?u=arraybolt3) 4. When the installation finishes, run "sudo netplan get". Expected result: Networking information related to the WiFi connection should appear in the "sudo netplan get" output. Actual result: "sudo netplan get" returns the following: ** (process:4088): WARNING **: 12:41:41.394; Permissions for /etc/netplan/01-network-manager-all.yaml are too open. Netplan configuration should NOT be accessible by others. network: version: 2 renderer: NetworkManager End of output. Additionally, the /etc/netplan folder does not contain files that I would expect to be there that would contain the networking info. Additional information: If I disconnect from WiFi, then delete my WiFi connection entirely in nmtui, and *then* reconnect to the same WiFi network, "sudo netplan get" returns the expected networking information. /etc/netplan is also properly populated after doing this. This bug seems like it will probably cause unintended behavior after an upgrade from 23.04 (which uses normal NetworkManager) to 23.10 (which is supposed to be using the Netplan Everywhere NetworkManager). People probably won't know to entirely delete the WiFi and other connections and then reconnect them in order for the netplan output to be usable. To manage notifications about this bug go to: https://bugs.launchpad.net/netplan/+bug/2010561/+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 2017999] Re: tzdata 2023c-0ubuntu0.22.04.1 might have some inconsistency
** Tags added: regression-update ** Changed in: tzdata (Ubuntu) Importance: Undecided => High ** Changed in: tzdata (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tzdata in Ubuntu. https://bugs.launchpad.net/bugs/2017999 Title: tzdata 2023c-0ubuntu0.22.04.1 might have some inconsistency Status in tzdata package in Ubuntu: Confirmed Bug description: compared to 2023c-0ubuntu0.22.04.0 - America/Ensenada->only dst changes until 2022 are shown - Atlantic/Jan_Mayen->now valid data is shown - Europe/Tiraspol->only dst changes until 2010 are shown To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/2017999/+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 2003851] Re: occasional hanging 'apt-get update' from daily cronjob since Jammy 22.04
Hi Julian, > [There] isn't much we can do otherwise, this highly depends on network specifics like latency and mtus and is never reliably reproducible. So, with my bogus python PoC server I mentioned in the comments, it is quite easily reproducible. If I can assist you in getting it up and running, do let me know. Cheers, Walter -- 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/2003851 Title: occasional hanging 'apt-get update' from daily cronjob since Jammy 22.04 Status in apt package in Ubuntu: Confirmed Bug description: Hi! Yesterday I spotted several machines of ours where a period `apt-get update` was stalled. The `http` children were hanging in `WaitFd` (waiting for parent instructions/queue). The parent was looping in `AcquireUpdate` every 500ms. We have a cronjob that runs every few hours which calls `apt-get update` and does some post-processing. We noticed that several of them had stalled at some point in time. Killing the parent (apt-get) got it unstuck, removing the locks. Example: ``` # apt-get update Reading package lists... Done E: Could not get lock /var/lib/apt/lists/lock. It is held by process 154026 (apt-get) N: Be aware that removing the lock file is not a solution and may break your system. E: Unable to lock directory /var/lib/apt/lists/ ``` Task listing: ``` root 153929 \_ /usr/sbin/CRON -f -P root 153942 \_ /bin/sh -c [ -x /etc/zabbix/scripts/dpkg.updates ] && /etc/zabbix/scripts/dpkg.updates --cron root 153943 \_ /bin/sh /etc/zabbix/scripts/dpkg.updates --cron root 154026 \_ apt-get update _apt 154029 \_ /usr/lib/apt/methods/http _apt 154030 \_ /usr/lib/apt/methods/http _apt 154031 \_ /usr/lib/apt/methods/http _apt 154033 \_ /usr/lib/apt/methods/gpgv ``` Open (TCP) sockets. All have 1 item in the Recv-Q (probably a FIN or RST?): ``` # netstat -apn | grep -E '154026|154029|154030|154031|154033' tcp 1 0 10.x.x.x:60868 217.x.x.x:80 CLOSE_WAIT 154030/http tcp 1 0 10.x.x.x:40756 178.x.x.x:80 CLOSE_WAIT 154029/http tcp 1 0 10.x.x.x:56818 185.x.x.x:80 CLOSE_WAIT 154031/http ``` All children (including gpgv) were waiting using pselect6(1, [0], NULL, NULL, NULL, NULL). The parent (apt-get) was waiting using pselect6(10, [5 6 7 9], [], NULL, {tv_sec=0, tv_nsec=5}, NULL). The http sockets in the children were at fd=3. Parent lsof: ``` # lsof -p 154026 +E ... apt-get 154026 root4uW REG8,10 262281 /var/lib/apt/lists/lock apt-get 154026 root5r FIFO 0,13 0t0 4015176 pipe 154029,http,1w apt-get 154026 root6r FIFO 0,13 0t0 4012448 pipe 154030,http,1w apt-get 154026 root7r FIFO 0,13 0t0 4015192 pipe 154031,http,1w apt-get 154026 root8w FIFO 0,13 0t0 4015177 pipe 154029,http,0r apt-get 154026 root9r FIFO 0,13 0t0 4015233 pipe 154033,gpgv,1w apt-get 154026 root 10w FIFO 0,13 0t0 4012449 pipe 154030,http,0r apt-get 154026 root 12w FIFO 0,13 0t0 4015193 pipe 154031,http,0r apt-get 154026 root 14w FIFO 0,13 0t0 4015234 pipe 154033,gpgv,0r http 154029 _apt0r FIFO 0,13 0t0 4015177 pipe 154026,apt-get,8w http 154029 _apt1w FIFO 0,13 0t0 4015176 pipe 154026,apt-get,5r http 154030 _apt0r FIFO 0,13 0t0 4012449 pipe 154026,apt-get,10w http 154030 _apt1w FIFO 0,13 0t0 4012448 pipe 154026,apt-get,6r http 154031 _apt0r FIFO 0,13 0t0 4015193 pipe 154026,apt-get,12w http 154031 _apt1w FIFO 0,13 0t0 4015192 pipe 154026,apt-get,7r gpgv 154033 _apt0r FIFO 0,13 0t0 4015234 pipe 154026,apt-get,14w gpgv 154033 _apt1w FIFO 0,13 0t0 4015233 pipe 154026,apt-get,9r ``` So: - apt-get is waiting for any data written by any of its four children (at fd 5/6/7/9) - http and gpgv are waiting for any data written by their parent (at their respective fd 0) Parent backtrace: ``` #0 0x7f420116a74d in select () from /lib/x86_64-linux-gnu/libc.so.6 #1 0x7f420153fb5d in pkgAcquire::Run(int) () from /lib/x86_64-linux-gnu/libapt-pkg.so.6.0 #2 0x7f420161d535 in AcquireUpdate(pkgAcquire&, int, bool, bool) () from /lib/x86_64-linux-gnu/libapt-pkg.so.6.0 #3 0x7f420161d986 in ListUpdate(pkgAcquireStatus&, pkgSourceList&, int) () from /lib/x86_64-linux-gnu/libapt-pkg.so.6.0 #4 0x7f42016d127b in DoUpdate (CmdL=...) at ./apt-private/private-update.cc:73 #5 0x7f420156d73f in CommandLine::DispatchArg(CommandLine::Dispatch const*, bool) () from
[Touch-packages] [Bug 2017984] Re: Microsoft Edge "Save as" dialog is not in dark mode
It's more likely to be an issue in edge than gtk itself...do you have another application showing the same issue? ** Changed in: gtk+3.0 (Ubuntu) Status: New => Incomplete ** Changed in: gtk+3.0 (Ubuntu) Importance: Undecided => Low -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/2017984 Title: Microsoft Edge "Save as" dialog is not in dark mode Status in gtk+3.0 package in Ubuntu: Incomplete Status in yaru-theme package in Ubuntu: New Bug description: After update to 23.04 I'm having the following issue. In dark mode of Yaru-dark theme, when downloading the file and choosing the "Save as" option - popup window for folder selection is not in dark mode. When using Xorg session problem is not reproduced. The same applies for upload logic. 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] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Apr 28 12:31:55 2023 DistUpgraded: 2023-04-25 21:06:12,927 DEBUG icon theme changed, re-reading DistroCodename: lunar DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation TigerLake-LP GT2 [Iris Xe Graphics] [8086:9a49] (rev 01) (prog-if 00 [VGA controller]) Subsystem: Lenovo TigerLake-LP GT2 [Iris Xe Graphics] [17aa:508f] InstallationDate: Installed on 2022-08-26 (244 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) MachineType: LENOVO 20X4S1GH08 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.2.0-20-generic root=/dev/mapper/vgubuntu-root ro usbcore.autosuspend=-1 quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to lunar on 2023-04-25 (2 days ago) dmi.bios.date: 11/22/2022 dmi.bios.release: 1.60 dmi.bios.vendor: LENOVO dmi.bios.version: R1JET60W (1.60 ) dmi.board.asset.tag: Not Available dmi.board.name: 20X4S1GH08 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.48 dmi.modalias: dmi:bvnLENOVO:bvrR1JET60W(1.60):bd11/22/2022:br1.60:efr1.48:svnLENOVO:pn20X4S1GH08:pvrThinkPadL15Gen2:rvnLENOVO:rn20X4S1GH08:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20X4_BU_Think_FM_ThinkPadL15Gen2: dmi.product.family: ThinkPad L15 Gen 2 dmi.product.name: 20X4S1GH08 dmi.product.sku: LENOVO_MT_20X4_BU_Think_FM_ThinkPad L15 Gen 2 dmi.product.version: ThinkPad L15 Gen 2 dmi.sys.vendor: LENOVO 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 N/A 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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/2017984/+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 1522675] Re: Warning messages about unsandboxed downloads
on Jammy 22.04.02 if installing via Synaptic kernel 5.19.0-41.42 and others W: Download is performed unsandboxed as root as file '/root/.synaptic/tmp//tmp_cl' couldn't be accessed by user '_apt'. - pkgAcquire::Run (13: Permission denied) Its not first error by Synaptic. Ok, manully repair permission now. -- 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/1522675 Title: Warning messages about unsandboxed downloads Status in apt package in Ubuntu: Fix Released Status in aptitude package in Ubuntu: Fix Released Status in synaptic package in Ubuntu: Triaged Status in update-notifier package in Ubuntu: Fix Released Status in aptitude source package in Xenial: Confirmed Status in synaptic source package in Xenial: Confirmed Status in update-notifier source package in Xenial: Fix Released Status in apt source package in Hirsute: Fix Released Status in aptitude source package in Hirsute: Fix Released Status in synaptic source package in Hirsute: Won't Fix Status in update-notifier source package in Hirsute: Fix Released Status in apt package in Debian: Fix Released Status in aptitude package in Debian: Fix Released Status in synaptic package in Debian: New Bug description: READ ME FIRST = This is only a regression on a cosmetic level. Previous versions of apt did not have any sandboxing whatsoever, so this means apt reverted back to that old behavior. update-notifier SRU --- [Impact] Cosmetic. Warnings when installing packages using update-notifier downloading stuff [Test case] Install flashplugin-installer with apt and check that the output does not contain a message like this: W: Can't drop privileges for downloading as file '...' couldn't be accessed by user '_apt' [Regression Potential] It just chowns /var/lib/update-notifier/package-data- downloads/partial/ to _apt:root, there should not be any regression. Original report --- Recently we got new versions for synaptic 0.82+build1 & apt 1.1.3, but now get that error when installing/upgrading some packages: Setting up libc6-dbg:amd64 (2.21-0ubuntu5) ... Processing triggers for libc-bin (2.21-0ubuntu5) ... W: Can't drop privileges for downloading as file '/root/.synaptic/tmp//tmp_cl' couldn't be accessed by user '_apt'. - pkgAcquire::Run (13: Permission denied) From nautilus, i'm seeing a /root/ folder locked (x on its icon) and the folder is empty (no /.synaptic/ sub-folder or file), so the above error. oem@u64:~$ ls -l .synaptic total 4 -rw-rw-r-- 1 oem oem 0 Aug 25 11:19 options -rw-rw-r-- 1 oem oem 236 Aug 25 11:19 synaptic.conf oem@u64:~$ ls -l /var/lib/apt/lists/ -rw-r- 1 root root0 Sep 20 06:36 lock drwx-- 2 _apt root16384 Sep 24 15:25 partial .. oem@u64:~$ sudo ls -l /var/lib/update-notifier/package-data-downloads/ . drwxr-xr-x 2 _apt root 4096 Sep 22 23:33 partial ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: synaptic 0.82+build1 ProcVersionSignature: Ubuntu 4.3.0-1.10-generic 4.3.0 Uname: Linux 4.3.0-1-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.19.2-0ubuntu8 Architecture: amd64 CurrentDesktop: GNOME Date: Fri Dec 4 05:23:25 2015 SourcePackage: synaptic UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1522675/+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 2002789] Re: Missing 50-ubuntu-logging in sysvinit-utils 3.05-7ubuntu1
** Changed in: sysvinit (Debian) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to sysvinit in Ubuntu. https://bugs.launchpad.net/bugs/2002789 Title: Missing 50-ubuntu-logging in sysvinit-utils 3.05-7ubuntu1 Status in sysvinit package in Ubuntu: Fix Released Status in sysvinit package in Debian: Fix Released Bug description: The following file used to be provided by the lsb-base package in Ubuntu and it now supposed to be provided by the sysvinit-utils package. * lsb/init-functions.d/50-ubuntu-logging The file is Ubuntu specific but is not included in Ubuntu using a delta from Debian. Instead, the debian source tree includes the file but conditional statements in debian/rules makes it absent from the binary packages in Debian. Sadly, when moving the file from src:lsb to src:sysvinit, the conditional statements are not consistent anymore, resulting in the file being absent from the Ubuntu binary package as well. Affected version: sysvinit-utils 3.05-7ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sysvinit/+bug/2002789/+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 2018290] Re: Clicking on the top right corner fails
*** This bug is a duplicate of bug 2012388 *** https://bugs.launchpad.net/bugs/2012388 Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 2012388, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find. ** Package changed: xorg (Ubuntu) => ubuntu ** This bug has been marked a duplicate of bug 2012388 AnyDesk X11 window at top-right of the screen is invisible and steals mouse clicks -- 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/2018290 Title: Clicking on the top right corner fails Status in Ubuntu: New Bug description: Problem is that when any app gets maximized, or uses the half screen technique (eg: Drag a window to the left or right side of the screen so it half-screen maximizes itself) the top portion of the window can not be clicked (left or right clicked). So any button on that area do not work. Like something is overlapping the buttons. The solution is to drag the window back to a smaller size to use those buttons again. It also has a similar issue where, when clicking on the gnome extensions at the top or even the options of ubuntu at the top, you need to slightly click below them a bit for them to actually register the click. The problem has been mentioned here which is the same one: https://askubuntu.com/questions/1464858/right-corner-at-chrome-not-response-to-mouse-click 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 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 530.41.03 Thu Mar 16 19:48:20 UTC 2023 GCC version: gcc version 12.2.0 (Ubuntu 12.2.0-17ubuntu1) ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 BootLog: CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue May 2 03:55:34 2023 DistUpgraded: Fresh install DistroCodename: lunar DistroVariant: ubuntu DkmsStatus: nvidia/530.41.03, 6.2.0-20-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation AD102 [GeForce RTX 4090] [10de:2684] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ZOTAC International (MCO) Ltd. AD102 [GeForce RTX 4090] [19da:4675] InstallationDate: Installed on 2023-04-20 (11 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418) MachineType: ASUS System Product Name ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-20-generic root=UUID=276e1671-8c73-42fc-bf30-ea9c79e82647 ro mitigations=off pci=nommconf nvidia-drm.modeset=1 intel_idle.max_cstate=1 ibt=off SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/29/2023 dmi.bios.release: 9.4 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0904 dmi.board.asset.tag: Default string dmi.board.name: ROG MAXIMUS Z790 HERO dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0904:bd03/29/2023:br9.4:svnASUS:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGMAXIMUSZ790HERO:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: ASUS 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 N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A 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:
[Touch-packages] [Bug 1066101] Re: netbase 5.0ubuntu1 fails to cleanly upgrade, asks about conffiles
Note to future-sarnold: Remove 'devscripts' from ~/.mk-sbuild.rc Install devscripts into the -source schroot by hand later. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to netbase in Ubuntu. https://bugs.launchpad.net/bugs/1066101 Title: netbase 5.0ubuntu1 fails to cleanly upgrade, asks about conffiles Status in netbase package in Ubuntu: Triaged Status in netbase source package in Quantal: Won't Fix Bug description: Setting up netbase (5.0ubuntu1) ... Configuration file `/etc/protocols' ==> File on system created by you or by a script. ==> File also in package provided by package maintainer. ==> Using current old file as you requested. Configuration file `/etc/services' ==> File on system created by you or by a script. ==> File also in package provided by package maintainer. ==> Using current old file as you requested. In the sbuild chroot. I am not touching those files, so they should auto-upgrade in a sane way. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/netbase/+bug/1066101/+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 2018160] Re: gnome-shell crashes when top right panel touched on touchscreen
Thank you for taking the time to report this bug and helping to make Ubuntu better. It sounds like some part of the system has crashed. To help us find the cause of the crash please follow these steps: 1. Look in /var/crash for crash files and if found run: ubuntu-bug YOURFILE.crash Then tell us the ID of the newly-created bug. 2. If step 1 failed then look at https://errors.ubuntu.com/user/ID where ID is the content of file /var/lib/whoopsie/whoopsie-id on the machine. Do you find any links to recent problems on that page? If so then please send the links to us. Please take care to avoid attaching .crash files to bugs as we are unable to process them as file attachments. It would also be a security risk for yourself. ** Package changed: xorg (Ubuntu) => gnome-shell (Ubuntu) ** Changed in: gnome-shell (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/2018160 Title: gnome-shell crashes when top right panel touched on touchscreen Status in gnome-shell package in Ubuntu: Incomplete Bug description: Version: ubuntu 23.04 Package: gnome-shell: Installed: 44.0-2ubuntu3 Candidate: 44.0-2ubuntu3 Version table: *** 44.0-2ubuntu3 500 500 http://archive.ubuntu.com/ubuntu lunar/main amd64 Packages 100 /var/lib/dpkg/status What I expected: I expected the wifi/bluetooth/dark... menu (in the upper right hand corner) to popup when I touched it on my touchscreen (clicking with a mouse or touchpad works fine, touchscreen press does not). This works as intended on Ubuntu 22.04.2 LTS. What happened: The menu popped up as intended, but 2 seconds later it disappeared, along with the top gnome shell panel (presumably it crashed). A few seconds later the gnome panel restores but without the menu. Running applications (such as firefox) don't seem to be affected. Running on an Asus Vivobook 14 (touchscreen). Tried using both safe mode and proprietary graphic mode with same result. Earlier versions of gnome seem to work fine. Same problem happens in Fedora too. Willing to do additional testing. Really wanna get this working. Thanks 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 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CasperVersion: 1.480 CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Apr 29 18:06:49 2023 DistUpgraded: Fresh install DistroCodename: lunar DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation TigerLake-LP GT2 [Iris Xe Graphics] [8086:9a49] (rev 01) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. TigerLake-LP GT2 [Iris Xe Graphics] [1043:13d2] LiveMediaBuild: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418) MachineType: ASUSTeK COMPUTER INC. VivoBook_ASUSLaptop TP470EA_TP470EA ProcEnviron: LANG=C.UTF-8 PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz nomodeset layerfs-path=minimal.standard.live.squashfs --- quiet splash SourcePackage: xorg Symptom: display Title: Xorg crash UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/22/2021 dmi.bios.release: 5.19 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: TP470EA.311 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: TP470EA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrTP470EA.311:bd07/22/2021:br5.19:svnASUSTeKCOMPUTERINC.:pnVivoBook_ASUSLaptopTP470EA_TP470EA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnTP470EA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct31:cvr1.0:sku: dmi.product.family: VivoBook Flip dmi.product.name: VivoBook_ASUSLaptop TP470EA_TP470EA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. 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 N/A 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 To manage notifications about
[Touch-packages] [Bug 2018233] Re: Xorg crash / Wayland
Thank you for taking the time to report this bug and helping to make Ubuntu better. It sounds like some part of the system has crashed. To help us find the cause of the crash please follow these steps: 1. Look in /var/crash for crash files and if found run: ubuntu-bug YOURFILE.crash Then tell us the ID of the newly-created bug. 2. If step 1 failed then look at https://errors.ubuntu.com/user/ID where ID is the content of file /var/lib/whoopsie/whoopsie-id on the machine. Do you find any links to recent problems on that page? If so then please send the links to us. Please take care to avoid attaching .crash files to bugs as we are unable to process them as file attachments. It would also be a security risk for yourself. ** Package changed: xorg (Ubuntu) => ubuntu ** Changed in: ubuntu Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/2018233 Title: Xorg crash / Wayland Status in Ubuntu: Incomplete Bug description: I'm not sure if it's Xorg crashing, i'm using wayland. Clean installation Ubuntu 22.10 and upgraded to 23.04. The bug can be re-produced. Symptom: Moving firefox with ongoing video for example Youtube. Moving the firefox window from screen 2 or 3 to screen1 then it crashes 100% of times. Screen 1 is in vertical view mode. Screen 2 and 3 landscape. ## unk@unk-ThinkPad-X1-Carbon-Gen-10:~$ lsb_release -rd No LSB modules are available. Description: Ubuntu 23.04 Release: 23.04 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] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon May 1 15:17:51 2023 DistUpgraded: 2023-04-23 20:27:46,523 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: lunar DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Alder Lake-P Integrated Graphics Controller [8086:46a6] (rev 0c) (prog-if 00 [VGA controller]) Subsystem: Lenovo Alder Lake-P Integrated Graphics Controller [17aa:22e7] InstallationDate: Installed on 2023-03-22 (39 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) MachineType: LENOVO 21CB00AYMX ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.2.0-20-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg crash UpgradeStatus: Upgraded to lunar on 2023-04-23 (7 days ago) dmi.bios.date: 03/02/2023 dmi.bios.release: 1.37 dmi.bios.vendor: LENOVO dmi.bios.version: N3AET72W (1.37 ) dmi.board.asset.tag: Not Available dmi.board.name: 21CB00AYMX dmi.board.vendor: LENOVO dmi.board.version: SDK0T76538 WIN dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.18 dmi.modalias: dmi:bvnLENOVO:bvrN3AET72W(1.37):bd03/02/2023:br1.37:efr1.18:svnLENOVO:pn21CB00AYMX:pvrThinkPadX1CarbonGen10:rvnLENOVO:rn21CB00AYMX:rvrSDK0T76538WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21CB_BU_Think_FM_ThinkPadX1CarbonGen10: dmi.product.family: ThinkPad X1 Carbon Gen 10 dmi.product.name: 21CB00AYMX dmi.product.sku: LENOVO_MT_21CB_BU_Think_FM_ThinkPad X1 Carbon Gen 10 dmi.product.version: ThinkPad X1 Carbon Gen 10 dmi.sys.vendor: LENOVO 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 N/A 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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/2018233/+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 2017984] Re: "Save as" window from browser is not in dark mode
Thanks. It looks like Microsoft Edge is an external deb so the bug here will be in GTK (part of Ubuntu). ** Package changed: yaru-theme (Ubuntu) => gtk+3.0 (Ubuntu) ** Changed in: gtk+3.0 (Ubuntu) Status: Incomplete => New ** Also affects: yaru-theme (Ubuntu) Importance: Undecided Status: New ** Summary changed: - "Save as" window from browser is not in dark mode + Microsoft Edge "Save as" dialog is not in dark mode -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/2017984 Title: Microsoft Edge "Save as" dialog is not in dark mode Status in gtk+3.0 package in Ubuntu: New Status in yaru-theme package in Ubuntu: New Bug description: After update to 23.04 I'm having the following issue. In dark mode of Yaru-dark theme, when downloading the file and choosing the "Save as" option - popup window for folder selection is not in dark mode. When using Xorg session problem is not reproduced. The same applies for upload logic. 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] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Apr 28 12:31:55 2023 DistUpgraded: 2023-04-25 21:06:12,927 DEBUG icon theme changed, re-reading DistroCodename: lunar DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation TigerLake-LP GT2 [Iris Xe Graphics] [8086:9a49] (rev 01) (prog-if 00 [VGA controller]) Subsystem: Lenovo TigerLake-LP GT2 [Iris Xe Graphics] [17aa:508f] InstallationDate: Installed on 2022-08-26 (244 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) MachineType: LENOVO 20X4S1GH08 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.2.0-20-generic root=/dev/mapper/vgubuntu-root ro usbcore.autosuspend=-1 quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to lunar on 2023-04-25 (2 days ago) dmi.bios.date: 11/22/2022 dmi.bios.release: 1.60 dmi.bios.vendor: LENOVO dmi.bios.version: R1JET60W (1.60 ) dmi.board.asset.tag: Not Available dmi.board.name: 20X4S1GH08 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.48 dmi.modalias: dmi:bvnLENOVO:bvrR1JET60W(1.60):bd11/22/2022:br1.60:efr1.48:svnLENOVO:pn20X4S1GH08:pvrThinkPadL15Gen2:rvnLENOVO:rn20X4S1GH08:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20X4_BU_Think_FM_ThinkPadL15Gen2: dmi.product.family: ThinkPad L15 Gen 2 dmi.product.name: 20X4S1GH08 dmi.product.sku: LENOVO_MT_20X4_BU_Think_FM_ThinkPad L15 Gen 2 dmi.product.version: ThinkPad L15 Gen 2 dmi.sys.vendor: LENOVO 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 N/A 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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/2017984/+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 2018290] [NEW] Clicking on the top right corner fails
Public bug reported: Problem is that when any app gets maximized, or uses the half screen technique (eg: Drag a window to the left or right side of the screen so it half-screen maximizes itself) the top portion of the window can not be clicked (left or right clicked). So any button on that area do not work. Like something is overlapping the buttons. The solution is to drag the window back to a smaller size to use those buttons again. It also has a similar issue where, when clicking on the gnome extensions at the top or even the options of ubuntu at the top, you need to slightly click below them a bit for them to actually register the click. The problem has been mentioned here which is the same one: https://askubuntu.com/questions/1464858/right-corner-at-chrome-not-response-to-mouse-click 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 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 530.41.03 Thu Mar 16 19:48:20 UTC 2023 GCC version: gcc version 12.2.0 (Ubuntu 12.2.0-17ubuntu1) ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 BootLog: CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue May 2 03:55:34 2023 DistUpgraded: Fresh install DistroCodename: lunar DistroVariant: ubuntu DkmsStatus: nvidia/530.41.03, 6.2.0-20-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation AD102 [GeForce RTX 4090] [10de:2684] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ZOTAC International (MCO) Ltd. AD102 [GeForce RTX 4090] [19da:4675] InstallationDate: Installed on 2023-04-20 (11 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418) MachineType: ASUS System Product Name ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-20-generic root=UUID=276e1671-8c73-42fc-bf30-ea9c79e82647 ro mitigations=off pci=nommconf nvidia-drm.modeset=1 intel_idle.max_cstate=1 ibt=off SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/29/2023 dmi.bios.release: 9.4 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0904 dmi.board.asset.tag: Default string dmi.board.name: ROG MAXIMUS Z790 HERO dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0904:bd03/29/2023:br9.4:svnASUS:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGMAXIMUSZ790HERO:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: ASUS 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 N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A 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 lunar 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/2018290 Title: Clicking on the top right corner fails Status in xorg package in Ubuntu: New Bug description: Problem is that when any app gets maximized, or uses the half screen technique (eg: Drag a window to the left or right side of the screen so it half-screen maximizes itself) the top portion of the window can not be clicked (left or right clicked). So any button on that area do not work. Like something is overlapping the buttons. The solution is to drag the window back to a smaller size to use those buttons again. It also has a similar issue where, when clicking on the gnome extensions at the top or even the options of ubuntu at the top, you need to slightly click below
[Touch-packages] [Bug 1959525] Re: Occasional no display output on 6900XT or if been idle for too long
Cf. https://gitlab.freedesktop.org/drm/amd/-/issues/2447 ** Bug watch added: gitlab.freedesktop.org/drm/amd/-/issues #2447 https://gitlab.freedesktop.org/drm/amd/-/issues/2447 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libdrm in Ubuntu. https://bugs.launchpad.net/bugs/1959525 Title: Occasional no display output on 6900XT or if been idle for too long Status in libdrm package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Status in xserver-xorg-video-amdgpu package in Ubuntu: Confirmed Bug description: ## No output at boot The dmesg I attached is from when nothing showed at boot. Journal output: $ journalctl -r --grep amdgpu -- Journal begins at Thu 2022-01-27 05:36:17 EST, ends at Sun 2022-01-30 15:58:40 EST. -- Jan 30 15:50:24 Y4M1-II kernel: amdgpu: probe of :0c:00.0 failed with error -110 Jan 30 15:50:24 Y4M1-II kernel: [drm] amdgpu: ttm finalized Jan 30 15:50:24 Y4M1-II kernel: amdgpu_init+0x77/0x1000 [amdgpu] Jan 30 15:50:24 Y4M1-II kernel: amdgpu_pci_probe+0x12a/0x1b0 [amdgpu] Jan 30 15:50:24 Y4M1-II kernel: amdgpu_driver_load_kms.cold+0x46/0x83 [amdgpu] Jan 30 15:50:24 Y4M1-II kernel: amdgpu_driver_unload_kms+0x43/0x70 [amdgpu] Jan 30 15:50:24 Y4M1-II kernel: amdgpu_device_fini+0xc5/0x1e5 [amdgpu] Jan 30 15:50:24 Y4M1-II kernel: amdgpu_device_ip_fini.isra.0+0x206/0x2cd [amdgpu] Jan 30 15:50:24 Y4M1-II kernel: gmc_v10_0_sw_fini+0x33/0x40 [amdgpu] Jan 30 15:50:24 Y4M1-II kernel: amdgpu_bo_fini+0x12/0x50 [amdgpu] Jan 30 15:50:24 Y4M1-II kernel: amdgpu_ttm_fini+0xab/0x100 [amdgpu] Jan 30 15:50:24 Y4M1-II kernel: amdgpu_vram_mgr_fini+0xe8/0x160 [amdgpu] Jan 30 15:50:24 Y4M1-II kernel: Modules linked in: hid_generic usbhid hid amdgpu(+) iommu_v2 gpu_sched i2c_algo_bit drm_ttm_helper ttm drm_kms_helper crct10dif_pclmul syscopyarea crc32_pclmul sysfillrect ghash_clmulni_intel sysimgblt fb_sys_fops cec aesni_intel rc_core crypto_simd cryptd drm nvme ahci xhci_pci i2c_piix4 nvme_core igc libahci xhci_pci_renesas wmi Jan 30 15:50:24 Y4M1-II kernel: [drm:psp_v11_0_ring_destroy [amdgpu]] *ERROR* Fail to stop psp ring Jan 30 15:50:24 Y4M1-II kernel: amdgpu :0c:00.0: amdgpu: amdgpu: finishing device. Jan 30 15:50:24 Y4M1-II kernel: amdgpu :0c:00.0: amdgpu: Fatal error during GPU init Jan 30 15:50:24 Y4M1-II kernel: amdgpu :0c:00.0: amdgpu: amdgpu_device_ip_init failed Jan 30 15:50:24 Y4M1-II kernel: [drm:amdgpu_device_ip_init [amdgpu]] *ERROR* hw_init of IP block failed -110 Jan 30 15:50:24 Y4M1-II kernel: [drm:amdgpu_gfx_enable_kcq.cold [amdgpu]] *ERROR* KCQ enable failed Jan 30 15:50:24 Y4M1-II kernel: amdgpu :0c:00.0: [drm:amdgpu_ring_test_helper [amdgpu]] *ERROR* ring kiq_2.1.0 test failed (-110) Jan 30 15:50:24 Y4M1-II kernel: amdgpu :0c:00.0: amdgpu: SMU is initialized successfully! Jan 30 15:50:24 Y4M1-II kernel: amdgpu :0c:00.0: amdgpu: use vbios provided pptable Jan 30 15:50:24 Y4M1-II kernel: amdgpu :0c:00.0: amdgpu: SMU driver if version not matched Jan 30 15:50:24 Y4M1-II kernel: amdgpu :0c:00.0: amdgpu: smu driver if version = 0x003d, smu fw if version = 0x0040, smu fw version = 0x003a4700 (58.71.0) Jan 30 15:50:24 Y4M1-II kernel: amdgpu :0c:00.0: amdgpu: SECUREDISPLAY: securedisplay ta ucode is not available Jan 30 15:50:24 Y4M1-II kernel: amdgpu :0c:00.0: amdgpu: Will use PSP to load VCN firmware Jan 30 15:50:24 Y4M1-II kernel: [drm] amdgpu: 16368M of GTT memory ready. Jan 30 15:50:24 Y4M1-II kernel: [drm] amdgpu: 16368M of VRAM memory ready Jan 30 15:50:24 Y4M1-II kernel: amdgpu :0c:00.0: amdgpu: AGP: 267894784M 0x0084 - 0x Jan 30 15:50:24 Y4M1-II kernel: amdgpu :0c:00.0: amdgpu: GART: 512M 0x - 0x1FFF Jan 30 15:50:24 Y4M1-II kernel: amdgpu :0c:00.0: amdgpu: VRAM: 16368M 0x0080 - 0x0083FEFF (16368M used) Jan 30 15:50:24 Y4M1-II kernel: amdgpu :0c:00.0: amdgpu: SRAM ECC is not presented. Jan 30 15:50:24 Y4M1-II kernel: amdgpu :0c:00.0: amdgpu: MEM ECC is not presented. Jan 30 15:50:24 Y4M1-II kernel: amdgpu: ATOM BIOS: 113-EXT800216-L05 Jan 30 15:50:24 Y4M1-II kernel: amdgpu :0c:00.0: amdgpu: Fetched VBIOS from VFCT Jan 30 15:50:24 Y4M1-II kernel: amdgpu :0c:00.0: amdgpu: Trusted Memory Zone (TMZ) feature not supported Jan 30 15:50:24 Y4M1-II kernel: amdgpu :0c:00.0: enabling device (0006 -> 0007) Jan 30 15:50:24 Y4M1-II kernel: amdgpu :0c:00.0: vgaarb: deactivate vga console Jan 30 15:50:24 Y4M1-II kernel: fb0: switching to amdgpudrmfb from EFI VGA Jan 30 15:50:24 Y4M1-II kernel: amdgpu: Topology: Add CPU node Jan 30 15:50:24 Y4M1-II kernel: amdgpu: Virtual CRAT table created for CPU Jan 30 15:50:24 Y4M1-II kernel: amdgpu: Ignoring ACPI CRAT on non-APU system Jan 30 15:50:24 Y4M1-II kernel:
[Touch-packages] [Bug 2018273] [NEW] package libnih-dbus1 1.0.3-6ubuntu2 failed to install/upgrade: package libnih-dbus1:amd64 (1.0.3-12build1) with field 'Multi-Arch: no' is not co-installable with l
Public bug reported: . ProblemType: Package DistroRelease: Ubuntu 22.04 Package: libnih-dbus1 1.0.3-6ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-71.78-generic 5.15.92 Uname: Linux 5.15.0-71-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.4 AptOrdering: libnih-dbus1:amd64: Install libnih1:amd64: Install NULL: ConfigurePending Architecture: amd64 CasperMD5CheckResult: unknown Date: Tue May 2 09:33:36 2023 DpkgTerminalLog: dpkg: error processing archive /var/cache/apt/archives/libnih-dbus1_1.0.3-12build1_amd64.deb (--unpack): package libnih-dbus1:amd64 (1.0.3-12build1) with field 'Multi-Arch: no' is not co-installable with libnih-dbus1 which has multiple installed instances ErrorMessage: package libnih-dbus1:amd64 (1.0.3-12build1) with field 'Multi-Arch: no' is not co-installable with libnih-dbus1 which has multiple installed instances InstallationDate: Installed on 2014-05-11 (3278 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) Python3Details: /usr/bin/python3.10, Python 3.10.6, python3-minimal, 3.10.6-1~22.04 PythonDetails: /usr/bin/python3.10, Python 3.10.6, python-is-python2, 2.7.17-4 RelatedPackageVersions: dpkg 1.21.1ubuntu2.1 apt 2.4.8 SourcePackage: libnih Title: package libnih-dbus1 1.0.3-6ubuntu2 failed to install/upgrade: package libnih-dbus1:amd64 (1.0.3-12build1) with field 'Multi-Arch: no' is not co-installable with libnih-dbus1 which has multiple installed instances UpgradeStatus: Upgraded to jammy on 2022-11-20 (162 days ago) ** Affects: libnih (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package jammy -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libnih in Ubuntu. https://bugs.launchpad.net/bugs/2018273 Title: package libnih-dbus1 1.0.3-6ubuntu2 failed to install/upgrade: package libnih-dbus1:amd64 (1.0.3-12build1) with field 'Multi-Arch: no' is not co-installable with libnih-dbus1 which has multiple installed instances Status in libnih package in Ubuntu: New Bug description: . ProblemType: Package DistroRelease: Ubuntu 22.04 Package: libnih-dbus1 1.0.3-6ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-71.78-generic 5.15.92 Uname: Linux 5.15.0-71-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.4 AptOrdering: libnih-dbus1:amd64: Install libnih1:amd64: Install NULL: ConfigurePending Architecture: amd64 CasperMD5CheckResult: unknown Date: Tue May 2 09:33:36 2023 DpkgTerminalLog: dpkg: error processing archive /var/cache/apt/archives/libnih-dbus1_1.0.3-12build1_amd64.deb (--unpack): package libnih-dbus1:amd64 (1.0.3-12build1) with field 'Multi-Arch: no' is not co-installable with libnih-dbus1 which has multiple installed instances ErrorMessage: package libnih-dbus1:amd64 (1.0.3-12build1) with field 'Multi-Arch: no' is not co-installable with libnih-dbus1 which has multiple installed instances InstallationDate: Installed on 2014-05-11 (3278 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) Python3Details: /usr/bin/python3.10, Python 3.10.6, python3-minimal, 3.10.6-1~22.04 PythonDetails: /usr/bin/python3.10, Python 3.10.6, python-is-python2, 2.7.17-4 RelatedPackageVersions: dpkg 1.21.1ubuntu2.1 apt 2.4.8 SourcePackage: libnih Title: package libnih-dbus1 1.0.3-6ubuntu2 failed to install/upgrade: package libnih-dbus1:amd64 (1.0.3-12build1) with field 'Multi-Arch: no' is not co-installable with libnih-dbus1 which has multiple installed instances UpgradeStatus: Upgraded to jammy on 2022-11-20 (162 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libnih/+bug/2018273/+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 2017999] Re: tzdata 2023c-0ubuntu0.22.04.1 might have some inconsistency
here the expected values: - America/Ensenada->has also dst changes in 2023, 2023-03-12 from UTC-8 to UTC-7 - Atlantic/Jan_Mayen->has a lot of dst changes over the years, f.e. 2023-03-26 from UTC+1 to UTC+2 - Europe/Tiraspol->has also dst changes in 2023, 2023-03-26 from UTC+2 to UTC+3 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tzdata in Ubuntu. https://bugs.launchpad.net/bugs/2017999 Title: tzdata 2023c-0ubuntu0.22.04.1 might have some inconsistency Status in tzdata package in Ubuntu: New Bug description: compared to 2023c-0ubuntu0.22.04.0 - America/Ensenada->only dst changes until 2022 are shown - Atlantic/Jan_Mayen->now valid data is shown - Europe/Tiraspol->only dst changes until 2010 are shown To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/2017999/+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