[Touch-packages] [Bug 2020150] Re: no sound after selecting motherboard audio jack after headphones plugged in to front panel
** Description changed: # Symptom No sound coming from line out (motherboard jack) while headphones are plugged in(front panel) even after selecting Line out(motherboard jack) in sound settings. # Workaround run `alsamixer` in terminal press F6 to choose sound card select HD-Audio Generic use left/right arrow keys to select "Auto Mute Mode" use up/down to set to "Disabled" ESC to close run `sudo alsactl store` to save the current settings # System info Ubuntu 22.04 LTS I have ASUS X570 E Gaming motherboard (SupremeFX S1220A) (I'm assuming thats the same chip as Realtek ALC1220A) $ apt list --installed | grep alsa alsa-base/jammy,jammy,now 1.0.25+dfsg-0ubuntu7 all [installed,automatic] alsa-topology-conf/jammy,jammy,now 1.2.5.1-2 all [installed,automatic] alsa-ucm-conf/jammy-updates,jammy-updates,now 1.2.6.3-1ubuntu1.5 all [installed,automatic] alsa-utils/jammy,now 1.2.6-1ubuntu1 amd64 [installed,automatic] gstreamer1.0-alsa/jammy,now 1.20.1-1 amd64 [installed,automatic] # Personal remarks Auto Mute Mode on alsamixer should be disabled by default or a way to configure it via the Sound Settings GUI in Ubuntu - I don't see any scenario where a user selected Audio output should be + I don't see any scenario where a user-selected Audio output should be muted and current behavior. the current issue I'm describing is exactly the same as "User Journey 2: Changing output port from panel UI" in this Ubuntu Design doc: https://docs.google.com/document/d/1Vb1jUVLoHXBK9drley6Vd5bYGguBbCTEWVcZz7R-LFI/edit#heading=h.8h8mt4f5unfz + + # Another issue related to user experience with this same User Journey as above: + after using the workaround when the volume level on the headphones is high and the volume on the speakers was low, and you change the audio device from headphones to the speakers, the audio volume would be very loud on the speakers for a fraction of a second (perceived as a loud pop) ** Description changed: # Symptom No sound coming from line out (motherboard jack) while headphones are plugged in(front panel) even after selecting Line out(motherboard jack) in sound settings. # Workaround run `alsamixer` in terminal press F6 to choose sound card select HD-Audio Generic use left/right arrow keys to select "Auto Mute Mode" use up/down to set to "Disabled" ESC to close run `sudo alsactl store` to save the current settings # System info Ubuntu 22.04 LTS I have ASUS X570 E Gaming motherboard (SupremeFX S1220A) (I'm assuming thats the same chip as Realtek ALC1220A) $ apt list --installed | grep alsa alsa-base/jammy,jammy,now 1.0.25+dfsg-0ubuntu7 all [installed,automatic] alsa-topology-conf/jammy,jammy,now 1.2.5.1-2 all [installed,automatic] alsa-ucm-conf/jammy-updates,jammy-updates,now 1.2.6.3-1ubuntu1.5 all [installed,automatic] alsa-utils/jammy,now 1.2.6-1ubuntu1 amd64 [installed,automatic] gstreamer1.0-alsa/jammy,now 1.20.1-1 amd64 [installed,automatic] # Personal remarks Auto Mute Mode on alsamixer should be disabled by default or a way to configure it via the Sound Settings GUI in Ubuntu I don't see any scenario where a user-selected Audio output should be muted and current behavior. - the current issue I'm describing is exactly the same as "User Journey 2: Changing output port from panel UI" + the current issue I'm describing is exactly the same as "User Journey #2: Changing output port from panel UI" in this Ubuntu Design doc: https://docs.google.com/document/d/1Vb1jUVLoHXBK9drley6Vd5bYGguBbCTEWVcZz7R-LFI/edit#heading=h.8h8mt4f5unfz # Another issue related to user experience with this same User Journey as above: after using the workaround when the volume level on the headphones is high and the volume on the speakers was low, and you change the audio device from headphones to the speakers, the audio volume would be very loud on the speakers for a fraction of a second (perceived as a loud pop) ** Description changed: # Symptom No sound coming from line out (motherboard jack) while headphones are plugged in(front panel) even after selecting Line out(motherboard jack) in sound settings. # Workaround run `alsamixer` in terminal press F6 to choose sound card select HD-Audio Generic use left/right arrow keys to select "Auto Mute Mode" use up/down to set to "Disabled" ESC to close run `sudo alsactl store` to save the current settings # System info Ubuntu 22.04 LTS I have ASUS X570 E Gaming motherboard (SupremeFX S1220A) (I'm assuming thats the same chip as Realtek ALC1220A) $ apt list --installed | grep alsa alsa-base/jammy,jammy,now 1.0.25+dfsg-0ubuntu7 all [installed,automatic] alsa-topology-conf/jammy,jammy,now 1.2.5.1-2 all [installed,automatic] alsa-ucm-conf/jammy-updates,jammy-updates,now 1.2.6.3-1ubuntu1.5 all [installed,automatic] alsa-utils/jammy,now
[Touch-packages] [Bug 2020150] [NEW] no sound after selecting motherboard audio jack after headphones plugged in to front panel
Public bug reported: # Symptom No sound coming from line out (motherboard jack) while headphones are plugged in(front panel) even after selecting Line out(motherboard jack) in sound settings. # Workaround run `alsamixer` in terminal press F6 to choose sound card select HD-Audio Generic use left/right arrow keys to select "Auto Mute Mode" use up/down to set to "Disabled" ESC to close run `sudo alsactl store` to save the current settings # System info Ubuntu 22.04 LTS I have ASUS X570 E Gaming motherboard (SupremeFX S1220A) (I'm assuming thats the same chip as Realtek ALC1220A) $ apt list --installed | grep alsa alsa-base/jammy,jammy,now 1.0.25+dfsg-0ubuntu7 all [installed,automatic] alsa-topology-conf/jammy,jammy,now 1.2.5.1-2 all [installed,automatic] alsa-ucm-conf/jammy-updates,jammy-updates,now 1.2.6.3-1ubuntu1.5 all [installed,automatic] alsa-utils/jammy,now 1.2.6-1ubuntu1 amd64 [installed,automatic] gstreamer1.0-alsa/jammy,now 1.20.1-1 amd64 [installed,automatic] # Personal remarks Auto Mute Mode on alsamixer should be disabled by default or a way to configure it via the Sound Settings GUI in Ubuntu I don't see any scenario where a user selected Audio output should be muted and current behavior. the current issue I'm describing is exactly the same as "User Journey 2: Changing output port from panel UI" in this Ubuntu Design doc: https://docs.google.com/document/d/1Vb1jUVLoHXBK9drley6Vd5bYGguBbCTEWVcZz7R-LFI/edit#heading=h.8h8mt4f5unfz ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: alsa headphones no-sound realtek-alc1220a sound-settings ** Tags removed: alc1220a ** Tags added: realtek-alc1220a -- 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/2020150 Title: no sound after selecting motherboard audio jack after headphones plugged in to front panel Status in alsa-driver package in Ubuntu: New Bug description: # Symptom No sound coming from line out (motherboard jack) while headphones are plugged in(front panel) even after selecting Line out(motherboard jack) in sound settings. # Workaround run `alsamixer` in terminal press F6 to choose sound card select HD-Audio Generic use left/right arrow keys to select "Auto Mute Mode" use up/down to set to "Disabled" ESC to close run `sudo alsactl store` to save the current settings # System info Ubuntu 22.04 LTS I have ASUS X570 E Gaming motherboard (SupremeFX S1220A) (I'm assuming thats the same chip as Realtek ALC1220A) $ apt list --installed | grep alsa alsa-base/jammy,jammy,now 1.0.25+dfsg-0ubuntu7 all [installed,automatic] alsa-topology-conf/jammy,jammy,now 1.2.5.1-2 all [installed,automatic] alsa-ucm-conf/jammy-updates,jammy-updates,now 1.2.6.3-1ubuntu1.5 all [installed,automatic] alsa-utils/jammy,now 1.2.6-1ubuntu1 amd64 [installed,automatic] gstreamer1.0-alsa/jammy,now 1.20.1-1 amd64 [installed,automatic] # Personal remarks Auto Mute Mode on alsamixer should be disabled by default or a way to configure it via the Sound Settings GUI in Ubuntu I don't see any scenario where a user selected Audio output should be muted and current behavior. the current issue I'm describing is exactly the same as "User Journey 2: Changing output port from panel UI" in this Ubuntu Design doc: https://docs.google.com/document/d/1Vb1jUVLoHXBK9drley6Vd5bYGguBbCTEWVcZz7R-LFI/edit#heading=h.8h8mt4f5unfz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/2020150/+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 2020127] Re: x apps fail to launch from terminal shell
Thanks for the bug report. I can't seem to reproduce the issue here. Perhaps you just need to delete ~/.Xauthority or perhaps there's something in your local config setting it? Try: grep XAUTHORITY ~/.* -- 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/2020127 Title: x apps fail to launch from terminal shell Status in xorg package in Ubuntu: New Bug description: New upgrade to 23.04 In terminal typing xeyes, idle or other X app including ubuntu-bug fails to launch with error Invalid MIT-MAGIC-COOKIE-1 keyError: cannot open display: :0 Desktop and remote access from another machine to a shell on this host with ssh -X work correctly echo $XAUTHORITY is /home/dave/.Xauthority File exists and contains 2 cookies Clue: export XAUTHORITY=$(ls /run/user/1000/.mutter-Xwayland*) ubuntu-bug links to a working per session cookie, and I'm able to type this. Expected behaviour: display just works when an X application is started from a shell. 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: unknown CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu May 18 18:44:46 2023 DistUpgraded: 2023-05-16 20:52:31,229 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: lunar DistroVariant: ubuntu DkmsStatus: virtualbox/7.0.6, 5.19.0-42-generic, x86_64: installed virtualbox/7.0.6, 6.2.0-20-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Pitcairn XT [Radeon HD 7870 GHz Edition] [1002:6818] (prog-if 00 [VGA controller]) Subsystem: Hightech Information System Ltd. Pitcairn XT [Radeon HD 7870 GHz Edition] [1787:2321] InstallationDate: Installed on 2021-03-06 (802 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) MachineType: Gigabyte Technology Co., Ltd. Z490 AORUS ELITE AC ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-20-generic root=UUID=c3300897-9f55-4525-91f6-ac8cfbe405f3 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to lunar on 2023-05-16 (1 days ago) dmi.bios.date: 08/28/2020 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F5 dmi.board.asset.tag: Default string dmi.board.name: Z490 AORUS ELITE AC dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF5:bd08/28/2020:br5.17:svnGigabyteTechnologyCo.,Ltd.:pnZ490AORUSELITEAC:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnZ490AORUSELITEAC:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring: dmi.product.family: Z490 MB dmi.product.name: Z490 AORUS ELITE AC dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. 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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/2020127/+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 446657] Re: Bluetooth's on/off status doesn't update from the SetProperty D-Bus method that bluetoothd sends
** Changed in: bluez (Fedora) Status: Confirmed => Won't Fix -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/446657 Title: Bluetooth's on/off status doesn't update from the SetProperty D-Bus method that bluetoothd sends Status in GNOME Bluetooth: Unknown Status in The Ubuntu Power Consumption Project: New Status in bluez package in Ubuntu: Invalid Status in linux package in Ubuntu: Invalid Status in bluez package in Fedora: Won't Fix Bug description: Binary package hint: gnome-bluetooth Gnome's bluetooth applet should get a bluetooth device's on/off status through dbus from SetProperty setting sent by bluetoothd. This information was given in http://permalink.gmane.org/gmane.linux.bluez.kernel/4302 There is a setting controlling this feature: RememberPowered=true in /etc/bluetooth/main.conf Questions: Is the dbus message is even sent? If it is sent, why gnome-bluetooth doesn't do anything for it? Does bluez's SetProperty actually find the last (if even saved) bluetooth status? ProblemType: Bug Architecture: i386 Date: Thu Oct 8 20:54:15 2009 DistroRelease: Ubuntu 9.10 NonfreeKernelModules: wl Package: gnome-bluetooth 2.28.1-0ubuntu1 ProcEnviron: PATH=(custom, user) LANG=es_ES.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 2.6.31-12.41-generic SourcePackage: gnome-bluetooth Uname: Linux 2.6.31-12-generic i686 To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-bluetooth/+bug/446657/+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 446657]
FEDORA-2022-f38f479b8f has been submitted as an update to Fedora 35. https://bodhi.fedoraproject.org/updates/FEDORA-2022-f38f479b8f -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/446657 Title: Bluetooth's on/off status doesn't update from the SetProperty D-Bus method that bluetoothd sends Status in GNOME Bluetooth: Unknown Status in The Ubuntu Power Consumption Project: New Status in bluez package in Ubuntu: Invalid Status in linux package in Ubuntu: Invalid Status in bluez package in Fedora: Won't Fix Bug description: Binary package hint: gnome-bluetooth Gnome's bluetooth applet should get a bluetooth device's on/off status through dbus from SetProperty setting sent by bluetoothd. This information was given in http://permalink.gmane.org/gmane.linux.bluez.kernel/4302 There is a setting controlling this feature: RememberPowered=true in /etc/bluetooth/main.conf Questions: Is the dbus message is even sent? If it is sent, why gnome-bluetooth doesn't do anything for it? Does bluez's SetProperty actually find the last (if even saved) bluetooth status? ProblemType: Bug Architecture: i386 Date: Thu Oct 8 20:54:15 2009 DistroRelease: Ubuntu 9.10 NonfreeKernelModules: wl Package: gnome-bluetooth 2.28.1-0ubuntu1 ProcEnviron: PATH=(custom, user) LANG=es_ES.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 2.6.31-12.41-generic SourcePackage: gnome-bluetooth Uname: Linux 2.6.31-12-generic i686 To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-bluetooth/+bug/446657/+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 2020086] Re: Consider shipping keama, The KEA Migration Assistant
** Merge proposal linked: https://code.launchpad.net/~athos-ribeiro/ubuntu/+source/isc-dhcp/+git/isc-dhcp/+merge/443236 -- 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/2020086 Title: Consider shipping keama, The KEA Migration Assistant Status in isc-dhcp package in Ubuntu: Triaged Status in isc-dhcp package in Debian: New Bug description: The KEA Migration Assistant (aka keama) is an experimental tool which helps to translate ISC DHCP configurations to Kea [1]. It is maintained within the isc-dhcp sources [2], therefore, it is reasonable to ship it as another binary within the isc-dhcp package. The build process should be straightforward and all the package needs to ship is a binary file and a manpage. [1] https://kb.isc.org/docs/migrating-from-isc-dhcp-to-kea-dhcp-using-the-migration-assistant [2] https://gitlab.isc.org/isc-projects/dhcp/tree/master/keama To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/2020086/+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 2019986] Re: package openjdk-17-jre-headless:amd64 17.0.7+7~us1-0ubuntu1~22.04.2 failed to install/upgrade: end of file on stdin at conffile prompt
Assigned unattended-upgrades as this looks like a generic issue installing a package with a modified configuration file. ** Also affects: unattended-upgrades (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unattended-upgrades in Ubuntu. https://bugs.launchpad.net/bugs/2019986 Title: package openjdk-17-jre-headless:amd64 17.0.7+7~us1-0ubuntu1~22.04.2 failed to install/upgrade: end of file on stdin at conffile prompt Status in openjdk-17 package in Ubuntu: New Status in unattended-upgrades package in Ubuntu: New Bug description: Crash occurred first thing in the morning, before any interaction. ProblemType: Package DistroRelease: Ubuntu 22.04 Package: openjdk-17-jre-headless:amd64 17.0.7+7~us1-0ubuntu1~22.04.2 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 AptOrdering: openjdk-17-jdk:amd64: Install openjdk-17-jdk-headless:amd64: Install openjdk-17-jre:amd64: Install openjdk-17-jre-headless:amd64: Install NULL: ConfigurePending Architecture: amd64 CasperMD5CheckResult: unknown Date: Wed May 17 06:23:45 2023 ErrorMessage: end of file on stdin at conffile prompt InstallationDate: Installed on 2022-05-21 (360 days ago) InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223) Python3Details: /usr/bin/python3.10, Python 3.10.6, unpackaged PythonDetails: N/A RelatedPackageVersions: dpkg 1.21.1ubuntu2.1 apt 2.4.9 SourcePackage: openjdk-17 Title: package openjdk-17-jre-headless:amd64 17.0.7+7~us1-0ubuntu1~22.04.2 failed to install/upgrade: end of file on stdin at conffile prompt UpgradeStatus: Upgraded to jammy on 2022-08-31 (258 days ago) modified.conffile..etc.java-17-openjdk.jvm-amd64.cfg: -server KNOWN -client IGNORE -zero KNOWN -dcevm KNOWN modified.conffile..etc.java-17-openjdk.security.blocked.certs: [modified] modified.conffile..etc.java-17-openjdk.security.default.policy: [modified] modified.conffile..etc.java-17-openjdk.security.java.policy: [modified] modified.conffile..etc.java-17-openjdk.security.java.security: [modified] modified.conffile..etc.java-17-openjdk.security.nss.cfg: name = NSS nssDbMode = noDb attributes = compatibility handleStartupErrors = ignoreMultipleInitialisation modified.conffile..etc.java-17-openjdk.swing.properties: # uncomment to set the default look and feel to GTK #swing.defaultlaf=com.sun.java.swing.plaf.gtk.GTKLookAndFeel mtime.conffile..etc.java-17-openjdk.jfr.default.jfc: 2023-01-20T00:56:27 mtime.conffile..etc.java-17-openjdk.jfr.profile.jfc: 2023-01-20T00:56:27 mtime.conffile..etc.java-17-openjdk.jvm-amd64.cfg: 2023-01-20T00:56:27 mtime.conffile..etc.java-17-openjdk.logging.properties: 2023-01-20T00:56:27 mtime.conffile..etc.java-17-openjdk.management.jmxremote.access: 2023-01-20T00:56:27 mtime.conffile..etc.java-17-openjdk.management.management.properties: 2023-01-20T00:56:27 mtime.conffile..etc.java-17-openjdk.net.properties: 2023-01-20T00:56:27 mtime.conffile..etc.java-17-openjdk.psfont.properties.ja: 2023-01-20T00:56:27 mtime.conffile..etc.java-17-openjdk.psfontj2d.properties: 2023-01-20T00:56:27 mtime.conffile..etc.java-17-openjdk.security.blocked.certs: 2023-01-20T00:56:27 mtime.conffile..etc.java-17-openjdk.security.default.policy: 2023-01-20T00:56:27 mtime.conffile..etc.java-17-openjdk.security.java.policy: 2023-01-20T00:56:27 mtime.conffile..etc.java-17-openjdk.security.java.security: 2023-01-20T00:56:27 mtime.conffile..etc.java-17-openjdk.security.nss.cfg: 2023-01-20T00:56:27 mtime.conffile..etc.java-17-openjdk.security.policy.README.txt: 2023-01-20T00:56:27 mtime.conffile..etc.java-17-openjdk.security.policy.limited.default_US_export.policy: 2023-01-20T00:56:27 mtime.conffile..etc.java-17-openjdk.security.policy.limited.default_local.policy: 2023-01-20T00:56:27 mtime.conffile..etc.java-17-openjdk.security.policy.limited.exempt_local.policy: 2023-01-20T00:56:27 mtime.conffile..etc.java-17-openjdk.security.policy.unlimited.default_US_export.policy: 2023-01-20T00:56:27 mtime.conffile..etc.java-17-openjdk.security.policy.unlimited.default_local.policy: 2023-01-20T00:56:27 mtime.conffile..etc.java-17-openjdk.security.public_suffix_list.dat: 2023-01-20T00:56:27 mtime.conffile..etc.java-17-openjdk.sound.properties: 2023-01-20T00:56:27 mtime.conffile..etc.java-17-openjdk.swing.properties: 2023-01-17T14:28:11 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openjdk-17/+bug/2019986/+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 2020127] Re: x apps fail to launch from terminal shell
** Package changed: ubuntu => xorg (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/2020127 Title: x apps fail to launch from terminal shell Status in xorg package in Ubuntu: New Bug description: New upgrade to 23.04 In terminal typing xeyes, idle or other X app including ubuntu-bug fails to launch with error Invalid MIT-MAGIC-COOKIE-1 keyError: cannot open display: :0 Desktop and remote access from another machine to a shell on this host with ssh -X work correctly echo $XAUTHORITY is /home/dave/.Xauthority File exists and contains 2 cookies Clue: export XAUTHORITY=$(ls /run/user/1000/.mutter-Xwayland*) ubuntu-bug links to a working per session cookie, and I'm able to type this. Expected behaviour: display just works when an X application is started from a shell. 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: unknown CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu May 18 18:44:46 2023 DistUpgraded: 2023-05-16 20:52:31,229 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: lunar DistroVariant: ubuntu DkmsStatus: virtualbox/7.0.6, 5.19.0-42-generic, x86_64: installed virtualbox/7.0.6, 6.2.0-20-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Pitcairn XT [Radeon HD 7870 GHz Edition] [1002:6818] (prog-if 00 [VGA controller]) Subsystem: Hightech Information System Ltd. Pitcairn XT [Radeon HD 7870 GHz Edition] [1787:2321] InstallationDate: Installed on 2021-03-06 (802 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) MachineType: Gigabyte Technology Co., Ltd. Z490 AORUS ELITE AC ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-20-generic root=UUID=c3300897-9f55-4525-91f6-ac8cfbe405f3 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to lunar on 2023-05-16 (1 days ago) dmi.bios.date: 08/28/2020 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F5 dmi.board.asset.tag: Default string dmi.board.name: Z490 AORUS ELITE AC dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF5:bd08/28/2020:br5.17:svnGigabyteTechnologyCo.,Ltd.:pnZ490AORUSELITEAC:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnZ490AORUSELITEAC:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring: dmi.product.family: Z490 MB dmi.product.name: Z490 AORUS ELITE AC dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. 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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/2020127/+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 1983794] Re: Evolution not deleting autosave files
This is still needing a kinetic verification.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libcanberra in Ubuntu.
https://bugs.launchpad.net/bugs/1983794
Title:
Evolution not deleting autosave files
Status in Evolution:
Fix Released
Status in evolution package in Ubuntu:
Invalid
Status in libcanberra package in Ubuntu:
Fix Released
Status in libcanberra source package in Jammy:
Fix Committed
Status in evolution source package in Kinetic:
Confirmed
Status in libcanberra source package in Kinetic:
Fix Committed
Bug description:
[ Impact ]
Autosave files are not removed from evolution local state directories
(and windows leaked)
[ Test case ]
1. Open evolution, and start to compose a new email
2. Write enough text and wait few minutes so that this command returns a file
ls -l ~/.local/share/evolution/.evolution-composer.autosave-*
3. Close the email composer window, hitting "Do not save"
4. ls -l ~/.local/share/evolution/.evolution-composer.autosave-* should list
no files
5. Opening and closing again evolution should not ask to restore the previous
email
[ Regression potential ]
No sounds could be performed during some UI actions
---
Running Ubuntu MATE, Ubuntu 22.04.1 LTS. Evolution v3.44.1-0ubuntu1
was installed with the distribution on a new system and received
settings imported from an earlier version on another computer.
When composing an email, if the process takes long enough an autosave
file is created as ~/.local/share/evolution/.evolution-
composer.autosave-xx ("xx" is a random 6 character string).
When the email is successfully sent, the autosave file SHOULD be
deleted. It's not. When evolution is shut down and restarted I'm asked
if I want to recover an unfinished email. Answering No to this will
delete the autosave file, but otherwise it persists and the recovery
query recurs the next time I open evolution.
Other people are having the same issue, see
https://gitlab.gnome.org/GNOME/evolution/-/issues/1972. The Gnome
people aren't dealing with it, perhaps considering it a distro-
specific bug.
On a system used by many people this is a potential security issue.
To manage notifications about this bug go to:
https://bugs.launchpad.net/evolution/+bug/1983794/+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 2019856] Re: Add missing ARM-cores to support Grace-based systems
Heather mentioned some changes she has for the debdiffs, I also noted some changes to DEP3 headers, and debdiffs v2 are in progress. Thanks, Heather! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to util-linux in Ubuntu. https://bugs.launchpad.net/bugs/2019856 Title: Add missing ARM-cores to support Grace-based systems Status in util-linux package in Ubuntu: New Status in util-linux source package in Jammy: In Progress Status in util-linux source package in Lunar: In Progress Bug description: [Impact] When running "lscpu" on a Grace-based system + Ubuntu 22.04, it doesn't report a model name: Vendor ID: ARM Model: 0 [Fix] Adding the additional arm_part to sys-utils/lscpu-arm.c solves the problem. The commit below adds the specific codes missing from Jammy's version. https://github.com/util-linux/util- linux/commit/6857cccbb4157d5da34ca98f77a0ac9d68e1e740 [Evidence] When upstream code is compiled, output of lscpu is correctly displayed: Vendor ID: ARM Model name: Neoverse-V2 [What Could Go Wrong] The fix does not apply directly to Jammy's version, as other commits change sys-utils/lscpu-arm.c. The suggestion is only to add the missing arm_part to the list. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/2019856/+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 2017229] Update Released
The verification of the Stable Release Update for evolution-data-server has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to evolution-data-server in Ubuntu. https://bugs.launchpad.net/bugs/2017229 Title: Update evolution-data-server to 3.48.1 Status in evolution-data-server package in Ubuntu: Fix Released Status in evolution-data-server source package in Lunar: Fix Released Bug description: Impact -- This is a new stable release in the stable 3.48 series. https://gitlab.gnome.org/GNOME/evolution-data- server/-/blob/3.48.1/NEWS It is required to update the evolution app to 3.48.1 (LP: #2017231) Test Case - Install the update Log out and log back in (or restart) Ensure that GNOME Calendar and Evolution still work fine. What Could Go Wrong --- As a component of GNOME core, there is a micro-release exception for evolution-data-server https://wiki.ubuntu.com/StableReleaseUpdates/GNOME evolution-data-server is included in all the Ubuntu Desktop flavors except for Kubuntu, Lubuntu, and Xubuntu Other Info -- There will be new evolution-data-server bugfix releases monthly until September. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution-data-server/+bug/2017229/+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 2017229] Re: Update evolution-data-server to 3.48.1
This bug was fixed in the package evolution-data-server - 3.48.1-0ubuntu1 --- evolution-data-server (3.48.1-0ubuntu1) lunar; urgency=medium * New upstream release (LP: #2017229) * debian/*.symbols: Add new symbols -- Jeremy Bicha Fri, 21 Apr 2023 12:41:37 +0200 ** Changed in: evolution-data-server (Ubuntu Lunar) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to evolution-data-server in Ubuntu. https://bugs.launchpad.net/bugs/2017229 Title: Update evolution-data-server to 3.48.1 Status in evolution-data-server package in Ubuntu: Fix Released Status in evolution-data-server source package in Lunar: Fix Released Bug description: Impact -- This is a new stable release in the stable 3.48 series. https://gitlab.gnome.org/GNOME/evolution-data- server/-/blob/3.48.1/NEWS It is required to update the evolution app to 3.48.1 (LP: #2017231) Test Case - Install the update Log out and log back in (or restart) Ensure that GNOME Calendar and Evolution still work fine. What Could Go Wrong --- As a component of GNOME core, there is a micro-release exception for evolution-data-server https://wiki.ubuntu.com/StableReleaseUpdates/GNOME evolution-data-server is included in all the Ubuntu Desktop flavors except for Kubuntu, Lubuntu, and Xubuntu Other Info -- There will be new evolution-data-server bugfix releases monthly until September. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution-data-server/+bug/2017229/+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 2017149] Re: package linux-firmware 20220329.git681281e4-0ubuntu3.12 failed to install/upgrade: installed linux-firmware package post-installation script subprocess returned erro
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: initramfs-tools (Ubuntu) Status: New => Confirmed -- 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/2017149 Title: package linux-firmware 20220329.git681281e4-0ubuntu3.12 failed to install/upgrade: installed linux-firmware package post-installation script subprocess returned error exit status 1 Status in initramfs-tools package in Ubuntu: Confirmed Bug description: Unknown ProblemType: Package DistroRelease: Ubuntu 22.04 Package: linux-firmware 20220329.git681281e4-0ubuntu3.12 ProcVersionSignature: Ubuntu 5.19.0-38.39~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-38-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.4 AptOrdering: linux-firmware:amd64: Install NULL: ConfigurePending Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: Susan 1732 F pulseaudio /dev/snd/pcmC0D3p: Susan 1732 F...m pulseaudio /dev/snd/pcmC0D0c: Susan 1732 F...m pulseaudio CasperMD5CheckResult: pass Date: Thu Apr 20 06:55:38 2023 Dependencies: firmware-sof-signed 2.0-1ubuntu4.1 ErrorMessage: installed linux-firmware package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2022-02-02 (442 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) MachineType: Acer Aspire A515-56 PackageArchitecture: all ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.19.0-38-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.10, Python 3.10.6, python3-minimal, 3.10.6-1~22.04 PythonDetails: N/A RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: grub-pc 2.06-2ubuntu7.1 SourcePackage: initramfs-tools Title: package linux-firmware 20220329.git681281e4-0ubuntu3.12 failed to install/upgrade: installed linux-firmware package post-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to jammy on 2022-12-01 (140 days ago) dmi.bios.date: 08/31/2021 dmi.bios.release: 1.17 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.17 dmi.board.asset.tag: Type2 - Board Chassis Location dmi.board.name: Iris_TL dmi.board.vendor: TGL dmi.board.version: V1.17 dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V1.17 dmi.ec.firmware.release: 1.17 dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.17:bd08/31/2021:br1.17:efr1.17:svnAcer:pnAspireA515-56:pvrV1.17:rvnTGL:rnIris_TL:rvrV1.17:cvnAcer:ct10:cvrV1.17:sku: dmi.product.family: Aspire 5 dmi.product.name: Aspire A515-56 dmi.product.sku: dmi.product.version: V1.17 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/2017149/+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 2020123] Re: package keyboard-configuration 1.194ubuntu3 failed to install/upgrade: el subproceso instalado paquete keyboard-configuration script post-installation devolvió el có
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to console-setup in Ubuntu. https://bugs.launchpad.net/bugs/2020123 Title: package keyboard-configuration 1.194ubuntu3 failed to install/upgrade: el subproceso instalado paquete keyboard-configuration script post- installation devolvió el código de salida de error 2 Status in console-setup package in Ubuntu: New Bug description: Choices: 1: Launch a browser now C: Cancel Please choose (1/C): 1 sudo: xdg-open: command not found No se han podido instalar las actualizaciones La actualización se ha cancelado. Su sistema podría haber quedado en un estado no utilizable. Ahora se llevará a cabo una recuperación (dpkg --configure -a). Configurando keyboard-configuration (1.194ubuntu3) ... /var/lib/dpkg/info/keyboard-configuration.config: 1: eval: Syntax error: Unterminated quoted string dpkg: error al procesar el paquete keyboard-configuration (--configure): el subproceso instalado paquete keyboard-configuration script post-installation devolvió el código de salida de error 2 dpkg: problemas de dependencias impiden la configuración de console-setup: console-setup depende de keyboard-configuration (= 1.194ubuntu3); sin embargo: El paquete `keyboard-configuration' no está configurado todavía. dpkg: error al procesar el paquete console-setup (--configure): problemas de dependencias - se deja sin configurar dpkg: problemas de dependencias impiden la configuración de ubuntu-minimal: ubuntu-minimal depende de console-setup; sin embargo: El paquete `console-setup' no está configurado todavía. dpkg: error al procesar el paquete ubuntu-minimal (--configure): problemas de dependencias - se deja sin configurar dpkg: problemas de dependencias impiden la configuración de kbd: kbd depende de console-setup | console-setup-mini; sin embargo: El paquete `console-setup' no está configurado todavía. El paquete `console-setup-mini' no está instalado. dpkg: error al procesar el paquete kbd (--configure): problemas de dependencias - se deja sin configurar dpkg: problemas de dependencias impiden la configuración de console-setup-linux: console-setup-linux depende de kbd (>= 0.99-12) | console-tools (>= 1:0.2.3-16); sin embargo: El paquete `kbd' no está configurado todavía. El paquete `console-tools' no está instalado. console-setup-linux depende de keyboard-configuration (= 1.194ubuntu3); sin embargo: El paquete `keyboard-configuration' no está configurado todavía. dpkg: error al procesar el paquete console-setup-linux (--configure): problemas de dependencias - se deja sin configurar Se encontraron errores al procesar: keyboard-configuration console-setup ubuntu-minimal kbd console-setup-linux Actualización completada ProblemType: Package DistroRelease: Ubuntu 20.04 Package: keyboard-configuration 1.194ubuntu3 ProcVersionSignature: Ubuntu 4.15.0-211.222-generic 4.15.18 Uname: Linux 4.15.0-211-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.26 Architecture: amd64 CasperMD5CheckResult: skip Date: Thu May 18 10:19:55 2023 ErrorMessage: el subproceso instalado paquete keyboard-configuration script post-installation devolvió el código de salida de error 2 PackageArchitecture: all Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4 RelatedPackageVersions: dpkg 1.19.7ubuntu3.2 apt 2.0.9 SourcePackage: console-setup Title: package keyboard-configuration 1.194ubuntu3 failed to install/upgrade: el subproceso instalado paquete keyboard-configuration script post-installation devolvió el código de salida de error 2 UpgradeStatus: Upgraded to focal on 2023-05-18 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/2020123/+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 2020123] [NEW] package keyboard-configuration 1.194ubuntu3 failed to install/upgrade: el subproceso instalado paquete keyboard-configuration script post-installation devolvió el
Public bug reported: Choices: 1: Launch a browser now C: Cancel Please choose (1/C): 1 sudo: xdg-open: command not found No se han podido instalar las actualizaciones La actualización se ha cancelado. Su sistema podría haber quedado en un estado no utilizable. Ahora se llevará a cabo una recuperación (dpkg --configure -a). Configurando keyboard-configuration (1.194ubuntu3) ... /var/lib/dpkg/info/keyboard-configuration.config: 1: eval: Syntax error: Unterminated quoted string dpkg: error al procesar el paquete keyboard-configuration (--configure): el subproceso instalado paquete keyboard-configuration script post-installation devolvió el código de salida de error 2 dpkg: problemas de dependencias impiden la configuración de console-setup: console-setup depende de keyboard-configuration (= 1.194ubuntu3); sin embargo: El paquete `keyboard-configuration' no está configurado todavía. dpkg: error al procesar el paquete console-setup (--configure): problemas de dependencias - se deja sin configurar dpkg: problemas de dependencias impiden la configuración de ubuntu-minimal: ubuntu-minimal depende de console-setup; sin embargo: El paquete `console-setup' no está configurado todavía. dpkg: error al procesar el paquete ubuntu-minimal (--configure): problemas de dependencias - se deja sin configurar dpkg: problemas de dependencias impiden la configuración de kbd: kbd depende de console-setup | console-setup-mini; sin embargo: El paquete `console-setup' no está configurado todavía. El paquete `console-setup-mini' no está instalado. dpkg: error al procesar el paquete kbd (--configure): problemas de dependencias - se deja sin configurar dpkg: problemas de dependencias impiden la configuración de console-setup-linux: console-setup-linux depende de kbd (>= 0.99-12) | console-tools (>= 1:0.2.3-16); sin embargo: El paquete `kbd' no está configurado todavía. El paquete `console-tools' no está instalado. console-setup-linux depende de keyboard-configuration (= 1.194ubuntu3); sin embargo: El paquete `keyboard-configuration' no está configurado todavía. dpkg: error al procesar el paquete console-setup-linux (--configure): problemas de dependencias - se deja sin configurar Se encontraron errores al procesar: keyboard-configuration console-setup ubuntu-minimal kbd console-setup-linux Actualización completada ProblemType: Package DistroRelease: Ubuntu 20.04 Package: keyboard-configuration 1.194ubuntu3 ProcVersionSignature: Ubuntu 4.15.0-211.222-generic 4.15.18 Uname: Linux 4.15.0-211-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.26 Architecture: amd64 CasperMD5CheckResult: skip Date: Thu May 18 10:19:55 2023 ErrorMessage: el subproceso instalado paquete keyboard-configuration script post-installation devolvió el código de salida de error 2 PackageArchitecture: all Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4 RelatedPackageVersions: dpkg 1.19.7ubuntu3.2 apt 2.0.9 SourcePackage: console-setup Title: package keyboard-configuration 1.194ubuntu3 failed to install/upgrade: el subproceso instalado paquete keyboard-configuration script post-installation devolvió el código de salida de error 2 UpgradeStatus: Upgraded to focal on 2023-05-18 (0 days ago) ** Affects: console-setup (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package focal third-party-packages uec-images -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to console-setup in Ubuntu. https://bugs.launchpad.net/bugs/2020123 Title: package keyboard-configuration 1.194ubuntu3 failed to install/upgrade: el subproceso instalado paquete keyboard-configuration script post- installation devolvió el código de salida de error 2 Status in console-setup package in Ubuntu: New Bug description: Choices: 1: Launch a browser now C: Cancel Please choose (1/C): 1 sudo: xdg-open: command not found No se han podido instalar las actualizaciones La actualización se ha cancelado. Su sistema podría haber quedado en un estado no utilizable. Ahora se llevará a cabo una recuperación (dpkg --configure -a). Configurando keyboard-configuration (1.194ubuntu3) ... /var/lib/dpkg/info/keyboard-configuration.config: 1: eval: Syntax error: Unterminated quoted string dpkg: error al procesar el paquete keyboard-configuration (--configure): el subproceso instalado paquete keyboard-configuration script post-installation devolvió el código de salida de error 2 dpkg: problemas de dependencias impiden la configuración de console-setup: console-setup depende de keyboard-configuration (= 1.194ubuntu3); sin embargo: El paquete `keyboard-configuration' no está configurado todavía. dpkg: error al procesar el paquete console-setup (--configure): problemas de dependencias - se deja sin
[Touch-packages] [Bug 2019856] Re: Add missing ARM-cores to support Grace-based systems
The attachment "lp-2019856-add-missing-arm-cores-jammy.debdiff" seems to be a debdiff. The ubuntu-sponsors team has been subscribed to the bug report so that they can review and hopefully sponsor the debdiff. If the attachment isn't a patch, please remove the "patch" flag from the attachment, remove the "patch" tag, and if you are member of the ~ubuntu-sponsors, unsubscribe the team. [This is an automated message performed by a Launchpad user owned by ~brian-murray, for any issue please contact him.] ** Tags added: patch -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to util-linux in Ubuntu. https://bugs.launchpad.net/bugs/2019856 Title: Add missing ARM-cores to support Grace-based systems Status in util-linux package in Ubuntu: New Status in util-linux source package in Jammy: In Progress Status in util-linux source package in Lunar: In Progress Bug description: [Impact] When running "lscpu" on a Grace-based system + Ubuntu 22.04, it doesn't report a model name: Vendor ID: ARM Model: 0 [Fix] Adding the additional arm_part to sys-utils/lscpu-arm.c solves the problem. The commit below adds the specific codes missing from Jammy's version. https://github.com/util-linux/util- linux/commit/6857cccbb4157d5da34ca98f77a0ac9d68e1e740 [Evidence] When upstream code is compiled, output of lscpu is correctly displayed: Vendor ID: ARM Model name: Neoverse-V2 [What Could Go Wrong] The fix does not apply directly to Jammy's version, as other commits change sys-utils/lscpu-arm.c. The suggestion is only to add the missing arm_part to the list. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/2019856/+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 2019940] Re: Directly manipulating NetworkManager keyfiles
Invalid for cloud-init because the affected code is for rendering NetworkManager config on (non-Ubuntu) systems that are not using netplan. ** Changed in: cloud-init (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/2019940 Title: Directly manipulating NetworkManager keyfiles Status in augeas package in Ubuntu: New Status in calamares package in Ubuntu: New Status in cloud-init package in Ubuntu: Invalid Status in cruft-ng package in Ubuntu: New Status in dracut package in Ubuntu: New Status in forensic-artifacts package in Ubuntu: New Status in guestfs-tools package in Ubuntu: New Status in guix package in Ubuntu: New Status in ltsp package in Ubuntu: Invalid Status in netcfg package in Ubuntu: Won't Fix Status in netplan.io package in Ubuntu: Won't Fix Status in network-manager package in Ubuntu: New Status in refpolicy package in Ubuntu: New Status in sosreport package in Ubuntu: New Status in uhd package in Ubuntu: New Status in vagrant package in Ubuntu: New Bug description: The affected packages can manipulate NetworkManager keyfiles directly on disk, which might not be appropriate anymore on Ubuntu, since the Netplan integration was enabled in NetworkManager (starting with Mantic), migrating any keyfile configuration from /etc/NetworkManager/system-connections/*[.nmconnection] to /etc/netplan/90-NM-*.yaml See Netplan's documentation for how connections are handled: https://netplan.readthedocs.io/en/latest/netplan-everywhere/ PS: Packages were queried using: https://codesearch.debian.net/search?q=%2Fsystem-connections=1=1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/augeas/+bug/2019940/+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 2015645] Re: ufw crashes in wsl2
** Also affects: ufw (Ubuntu)
Importance: Undecided
Status: New
** Also affects: ufw (Ubuntu Mantic)
Importance: Undecided
Status: New
** Also affects: ufw (Ubuntu Focal)
Importance: Undecided
Status: New
** Also affects: ufw (Ubuntu Jammy)
Importance: Undecided
Status: New
** Changed in: ufw (Ubuntu Mantic)
Status: New => Triaged
** Changed in: ufw (Ubuntu Jammy)
Status: New => Triaged
** Changed in: ufw (Ubuntu Focal)
Status: New => Triaged
** Changed in: ufw (Ubuntu Mantic)
Importance: Undecided => High
** Changed in: ufw (Ubuntu Jammy)
Importance: Undecided => High
** Changed in: ufw (Ubuntu Focal)
Importance: Undecided => High
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ufw in Ubuntu.
https://bugs.launchpad.net/bugs/2015645
Title:
ufw crashes in wsl2
Status in ufw:
Fix Released
Status in ufw package in Ubuntu:
Triaged
Status in ufw source package in Focal:
Triaged
Status in ufw source package in Jammy:
Triaged
Status in ufw source package in Mantic:
Triaged
Bug description:
When I enable systemd in WSL2 (it became supported recently), install
ufw, and run sudo ufw enable, I get the error detailed in
https://superuser.com/questions/1775776/enabling-ufw-failed-with-
ubuntu-from-wsl2. You may already be aware of this error, I'm not sure
if "NotTheDr01ds" has talked to you about this yet. Note that the WSL2
/proc/[pid]/stat format, although weird, does comply with the spec:
https://man7.org/linux/man-pages/man5/proc.5.html
I verified that you can fix this issue by replacing the first split in
line 427 with rsplit(')', 1) so it splits based on the last
parenthesis instead of the all parenthesis.
Before:
ppid = open(name).readlines()[0].split(')')[1].split()[1]
After:
ppid = open(name).readlines()[0].rsplit(')',1)[1].split()[1]
C:\Users\caleb>wsl --version
WSL version: 1.1.6.0
Kernel version: 5.15.90.1
WSLg version: 1.0.50
MSRDC version: 1.2.3770
Direct3D version: 1.608.2-61064218
DXCore version: 10.0.25131.1002-220531-1700.rs-onecore-base2-hyp
Windows version: 10.0.19045.2728
➜ ufw git:(master) ufw --version
ufw 0.36
Copyright 2008-2015 Canonical Ltd.
➜ ufw git:(master) cat /proc/229/stat | cut -c -23
229 (Relay(230)) S 228
To manage notifications about this bug go to:
https://bugs.launchpad.net/ufw/+bug/2015645/+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 2020110] Re: Migrate netplan settings to this package
** Merge proposal linked: https://code.launchpad.net/~waveform/ubuntu/+source/ubuntu-settings/+git/ubuntu-settings/+merge/443210 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-settings in Ubuntu. https://bugs.launchpad.net/bugs/2020110 Title: Migrate netplan settings to this package Status in ubuntu-settings package in Ubuntu: New Bug description: The current netplan configuration that specifies Network Manager as the renderer comes from a livecd-rootfs hack and results in an "unowned" file in /etc/netplan/01-use-network-manager.yaml. It was decided at the engineering sprint to migrate this to /lib/netplan (with a slightly tweaked filename starting 00- for precedence) owned by ubuntu-settings which will ease maintenance (and image builds) in future. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-settings/+bug/2020110/+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 2011458] Re: ssh fails to rebind when it is killed with -HUP
This bug was fixed in the package openssh - 1:9.0p1-1ubuntu8.1 --- openssh (1:9.0p1-1ubuntu8.1) lunar; urgency=medium * debian/patches/systemd-socket-activation.patch: Fix re-execution behavior (LP: #2011458): - Remove FD_CLOEXEC on fds passed by systemd to prevent automatic closing when sshd re-executes. - Do not manually close fds passed by systemd when re-executing. - Only call sd_listen_fds() once, and only in the parent process. - Check the LISTEN_FDS environment variable to get the number of fds passed by systemd when re-executing as a child process. * debian/tests/systemd-socket-activation: Add autopkgtest for systemd socket activation functionality. -- Nick Rosbrook Fri, 31 Mar 2023 12:44:32 -0400 ** Changed in: openssh (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/2011458 Title: ssh fails to rebind when it is killed with -HUP Status in openssh package in Ubuntu: Fix Released Status in openssh source package in Kinetic: Fix Committed Status in openssh source package in Lunar: Fix Committed Bug description: [Impact] The sshd re-execution logic is generally broken with systemd socket activation, which means that (1) sshd fails when it is told to re-exec via SIGHUP (e.g. systemctl reload ssh), and (2) sshd fails when started in debug mode. [Test Case] (1) Test systemctl reload ssh: * On a machine with openssh-server installed, make a connection to localhost to activate ssh.service (the connection does not need to be complete, so you can just say "no" at the host key verification stage): $ ssh localhost [...] * Send SIGHUP to sshd by calling systemctl reload ssh: $ systemctl reload ssh * Check the service state: $ systemctl status ssh × ssh.service - OpenBSD Secure Shell server Loaded: loaded (/lib/systemd/system/ssh.service; disabled; preset: enabled) Drop-In: /etc/systemd/system/ssh.service.d └─00-socket.conf Active: failed (Result: exit-code) since Mon 2023-04-17 20:43:27 UTC; 4s ago Duration: 2min 44.132s TriggeredBy: ● ssh.socket Docs: man:sshd(8) man:sshd_config(5) Process: 1112 ExecStart=/usr/sbin/sshd -D $SSHD_OPTS (code=exited, status=255/EXCEPTION) Process: 1152 ExecReload=/usr/sbin/sshd -t (code=exited, status=0/SUCCESS) Process: 1153 ExecReload=/bin/kill -HUP $MAINPID (code=exited, status=0/SUCCESS) Main PID: 1112 (code=exited, status=255/EXCEPTION) CPU: 79ms Apr 17 20:40:43 lunar systemd[1]: Started ssh.service - OpenBSD Secure Shell server. Apr 17 20:41:06 lunar sshd[1113]: Connection closed by 127.0.0.1 port 54666 [preauth] Apr 17 20:43:27 lunar systemd[1]: Reloading ssh.service - OpenBSD Secure Shell server... Apr 17 20:43:27 lunar sshd[1112]: Received SIGHUP; restarting. Apr 17 20:43:27 lunar systemd[1]: Reloaded ssh.service - OpenBSD Secure Shell server. Apr 17 20:43:27 lunar sshd[1112]: error: Bind to port 22 on 0.0.0.0 failed: Address already in use. Apr 17 20:43:27 lunar sshd[1112]: error: Bind to port 22 on :: failed: Address already in use. Apr 17 20:43:27 lunar sshd[1112]: fatal: Cannot bind any address. Apr 17 20:43:27 lunar systemd[1]: ssh.service: Main process exited, code=exited, status=255/EXCEPTION Apr 17 20:43:27 lunar systemd[1]: ssh.service: Failed with result 'exit-code'. * On an affected machine, the service will fail as shown above. (2) Test debug mode: * On a machine with openssh-server installed, edit /etc/default/ssh to configure debug mode for sshd: $ cat /etc/default/ssh # Default settings for openssh-server. This file is sourced by /bin/sh from # /etc/init.d/ssh. # Options to pass to sshd SSHD_OPTS=-ddd * Attempt to make a connection to localhost: $ ssh localhost kex_exchange_identification: read: Connection reset by peer Connection reset by 127.0.0.1 port 22 * On an affected machine, the attempt will fail as shown above, and the service will be in a failed state: $ systemctl status ssh × ssh.service - OpenBSD Secure Shell server Loaded: loaded (/lib/systemd/system/ssh.service; disabled; preset: enabled) Drop-In: /etc/systemd/system/ssh.service.d └─00-socket.conf Active: failed (Result: exit-code) since Mon 2023-04-17 20:46:34 UTC; 2min 27s ago Duration: 5ms TriggeredBy: ● ssh.socket Docs: man:sshd(8) man:sshd_config(5) Process: 1166 ExecStartPre=/usr/sbin/sshd -t (code=exited, status=0/SUCCESS) Process: 1167 ExecStart=/usr/sbin/sshd -D $SSHD_OPTS (code=exited, status=255/EXCEPTION) Main PID: 1167 (code=exited, status=255/EXCEPTION) CPU: 40ms Apr 17 20:46:34 lunar sshd[1167]: Server listening on :: port
[Touch-packages] [Bug 2020110] Re: Migrate netplan settings to this package
Test package building in ppa:waveform/ubuntu-settings for mantic (https://launchpad.net/~waveform/+archive/ubuntu/ubuntu-settings) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-settings in Ubuntu. https://bugs.launchpad.net/bugs/2020110 Title: Migrate netplan settings to this package Status in ubuntu-settings package in Ubuntu: New Bug description: The current netplan configuration that specifies Network Manager as the renderer comes from a livecd-rootfs hack and results in an "unowned" file in /etc/netplan/01-use-network-manager.yaml. It was decided at the engineering sprint to migrate this to /lib/netplan (with a slightly tweaked filename starting 00- for precedence) owned by ubuntu-settings which will ease maintenance (and image builds) in future. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-settings/+bug/2020110/+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 2020086] Re: Consider shipping keama, The KEA Migration Assistant
** Changed in: isc-dhcp (Debian) Status: Unknown => New -- 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/2020086 Title: Consider shipping keama, The KEA Migration Assistant Status in isc-dhcp package in Ubuntu: Triaged Status in isc-dhcp package in Debian: New Bug description: The KEA Migration Assistant (aka keama) is an experimental tool which helps to translate ISC DHCP configurations to Kea [1]. It is maintained within the isc-dhcp sources [2], therefore, it is reasonable to ship it as another binary within the isc-dhcp package. The build process should be straightforward and all the package needs to ship is a binary file and a manpage. [1] https://kb.isc.org/docs/migrating-from-isc-dhcp-to-kea-dhcp-using-the-migration-assistant [2] https://gitlab.isc.org/isc-projects/dhcp/tree/master/keama To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/2020086/+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 2020110] [NEW] Migrate netplan settings to this package
Public bug reported: The current netplan configuration that specifies Network Manager as the renderer comes from a livecd-rootfs hack and results in an "unowned" file in /etc/netplan/01-use-network-manager.yaml. It was decided at the engineering sprint to migrate this to /lib/netplan (with a slightly tweaked filename starting 00- for precedence) owned by ubuntu-settings which will ease maintenance (and image builds) in future. ** Affects: ubuntu-settings (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-settings in Ubuntu. https://bugs.launchpad.net/bugs/2020110 Title: Migrate netplan settings to this package Status in ubuntu-settings package in Ubuntu: New Bug description: The current netplan configuration that specifies Network Manager as the renderer comes from a livecd-rootfs hack and results in an "unowned" file in /etc/netplan/01-use-network-manager.yaml. It was decided at the engineering sprint to migrate this to /lib/netplan (with a slightly tweaked filename starting 00- for precedence) owned by ubuntu-settings which will ease maintenance (and image builds) in future. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-settings/+bug/2020110/+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 2019856] Re: Add missing ARM-cores to support Grace-based systems
adds lunar debdiff ** Patch added: "lp-2019856-add-arm-core-lunar.debdiff" https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/2019856/+attachment/5673899/+files/lp-2019856-add-arm-core-lunar.debdiff -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to util-linux in Ubuntu. https://bugs.launchpad.net/bugs/2019856 Title: Add missing ARM-cores to support Grace-based systems Status in util-linux package in Ubuntu: New Status in util-linux source package in Jammy: In Progress Status in util-linux source package in Lunar: In Progress Bug description: [Impact] When running "lscpu" on a Grace-based system + Ubuntu 22.04, it doesn't report a model name: Vendor ID: ARM Model: 0 [Fix] Adding the additional arm_part to sys-utils/lscpu-arm.c solves the problem. The commit below adds the specific codes missing from Jammy's version. https://github.com/util-linux/util- linux/commit/6857cccbb4157d5da34ca98f77a0ac9d68e1e740 [Evidence] When upstream code is compiled, output of lscpu is correctly displayed: Vendor ID: ARM Model name: Neoverse-V2 [What Could Go Wrong] The fix does not apply directly to Jammy's version, as other commits change sys-utils/lscpu-arm.c. The suggestion is only to add the missing arm_part to the list. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/2019856/+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 1951018] Re: No ability to discern IPv4 vs IPv6 rules through Python
This was fixed in 0.36.2. ** Changed in: ufw Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ufw in Ubuntu. https://bugs.launchpad.net/bugs/1951018 Title: No ability to discern IPv4 vs IPv6 rules through Python Status in ufw: Fix Released Status in ufw package in Ubuntu: Triaged Bug description: Version: ufw 0.36 Ubuntu Version: 20.04.3 LTS There doesn't appear to be a Python method for accessing IPv4 and IPv6 rules in a distinguishable manner. In the source code (root/src/backend.py) there is an object that stores IPv4 and IPv6 rules in separate lists. Those lists are then accessed with the following method: def get_rules(self): '''Return list of all rules''' return self.rules + self.rules6 The issue with this is that the returned list doesn't contain an indication of what IP version each item corresponds to and would display something like the following. 1 allow 22/tcp 2 allow 80 3 allow 443 4 allow 22/tcp 5 allow 80 6 allow 443 I don't currently see a way to distinguish between IPv4 and IPv6 rules other than accessing the lists in the backend object directly (but I don't think this is best practice). E.g.: rules_ipv4 = backend.rules rules_ipv6 = backend.rules6 One possible fix would be to add functions that return only the IPv4 or IPv6 rules. E.g.: def get_rules_ipv4(self): '''Return list of all ipv4 rules''' return self.rules def get_rules_ipv6(self): '''Return list of all ipv6 rules''' return self.rules6 To manage notifications about this bug go to: https://bugs.launchpad.net/ufw/+bug/1951018/+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 1946804] Re: ufw breaks boot on network root filesystem
This was fixed in 0.36.2. ** Changed in: ufw Importance: Undecided => Medium ** Changed in: ufw Assignee: (unassigned) => Jamie Strandboge (jdstrand) ** Changed in: ufw Status: Fix Committed => Fix Released ** Changed in: ufw (Ubuntu) Importance: Undecided => Medium -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ufw in Ubuntu. https://bugs.launchpad.net/bugs/1946804 Title: ufw breaks boot on network root filesystem Status in ufw: Fix Released Status in ufw package in Ubuntu: Fix Released Status in ufw source package in Bionic: Fix Released Status in ufw source package in Focal: Fix Released Status in ufw source package in Hirsute: Fix Released Status in ufw source package in Impish: Fix Released Bug description: [Impact] A system with rootfs on iSCSI stops booting when ufw.service starts. The kernel logs iSCSI command/reset timeout until I/O fails and the root filesystem/journal break. The issue is that ufw_start() sets the default policy _first_, then adds rules _later_. So, a default INPUT policy of DROP (default setting in ufw) prevents further access to the root filesystem (blocks incoming iSCSI traffic) thus any rules that could help are not loaded (nor anything else.) [Fix] The fix is to set default policy after loading rules in ufw_start(). That seems to be OK as `ip[6]tables-restore -n/--noflush` is used, and per iptables source, that only sets the chain policy. This allows the system to boot due to the RELATED,ESTABLISHED rule, that is introduced by before.rules in INPUT/ufw-before-input chain. The comparison of `iptables -L` before/after shows no differences (verified on a local rootfs); `run_tests.sh` has 0 skipped/errors. [Test Steps] * Install Ubuntu on an iSCSI (or other network-based) root filesystem. (eg, Oracle Cloud's bare-metal 'BM.Standard1.36' shape.) * sudo ufw enable * Observed: system may stall immediately if no prior iptables rules. (eg, iptables -A INPUT -p tcp -s 169.254.0.2 --sport 3260 -j ACCEPT) * Expected: system continues working. * sudo reboot * Observed: system boot stalls once ufw.service starts (see below.) * Expected: system boot should move on. [Regression Potential] * Potential regressions would be observed on ufw start/reload, when iptables rules are configured. * The resulting iptables configuration has been compared before/after the change, with identical rules on both. [Other Info] * Fixed in Debian and Jammy. [ufw info] # ufw --version ufw 0.36 Copyright 2008-2015 Canonical Ltd. # lsb_release -cs focal [Boot Log] [ 232.168355] iBFT detected. Begin: Running /scripts/init-premount ... done. Begin: Mounting root file system ... Begin: Running /scripts/local-top ... Setting up software interface enp45s0f0np0 ... [ 254.644505] Loading iSCSI transport class v2.0-870. [ 254.714938] iscsi: registered transport (tcp) [ 254.780129] scsi host12: iSCSI Initiator over TCP/IP ... [ 255.433491] sd 12:0:0:1: [sda] 251658240 512-byte logical blocks: (129 GB/120 GiB) ... [ 256.379550] EXT4-fs (sda1): mounted filesystem with ordered data mode. Opts: (null) ... [ 266.620860] systemd[1]: Starting Uncomplicated firewall... Starting Uncomplicated firewall... ... [ 298.491560] session1: iscsi_eh_cmd_timed_out scsi cmd 310a6696 timedout [ 298.580803] session1: iscsi_eh_cmd_timed_out return shutdown or nh [ 298.656262] session1: iscsi_eh_cmd_timed_out scsi cmd 94ad9246 timedout [ 298.745237] session1: iscsi_eh_cmd_timed_out return shutdown or nh [ 298.745270] session1: iscsi_eh_abort aborting sc 310a6696 [ 298.899644] session1: iscsi_eh_abort aborting [sc 310a6696 itt 0x13] [ 298.985788] session1: iscsi_exec_task_mgmt_fn tmf set timeout [ 302.075554] session1: iscsi_eh_cmd_timed_out scsi cmd 1a9458b5 timedout [ 302.164786] session1: iscsi_eh_cmd_timed_out return shutdown or nh [ 314.107541] session1: iscsi_tmf_timedout tmf timedout [ 314.169797] connection1:0: detected conn error (1021) [ 314.232266] session1: iscsi_eh_abort abort failed [sc 310a6696 itt 0x13] [ 314.323531] session1: iscsi_eh_abort aborting sc 94ad9246 [ 314.399640] session1: iscsi_eh_abort sc never reached iscsi layer or it completed. [ 314.495578] session1: iscsi_eh_abort aborting sc 1a9458b5 [ 314.571554] session1: iscsi_eh_abort sc never reached iscsi layer or it completed. [ 314.664050] session1: iscsi_eh_device_reset LU Reset [sc 310a6696 lun 1] [ 314.755773] session1: iscsi_eh_device_reset dev reset result = FAILED [ 314.834736] session1: iscsi_eh_target_reset tgt Reset [sc 310a6696 tgt <...>] [ 314.954144] session1: iscsi_eh_target_reset tgt <...> reset result = FAILED [ 315.063456] connection1:0: detected conn
[Touch-packages] [Bug 2019856] Re: Add missing ARM-cores to support Grace-based systems
** Tags added: se-sponsor-mfo -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to util-linux in Ubuntu. https://bugs.launchpad.net/bugs/2019856 Title: Add missing ARM-cores to support Grace-based systems Status in util-linux package in Ubuntu: New Status in util-linux source package in Jammy: In Progress Status in util-linux source package in Lunar: In Progress Bug description: [Impact] When running "lscpu" on a Grace-based system + Ubuntu 22.04, it doesn't report a model name: Vendor ID: ARM Model: 0 [Fix] Adding the additional arm_part to sys-utils/lscpu-arm.c solves the problem. The commit below adds the specific codes missing from Jammy's version. https://github.com/util-linux/util- linux/commit/6857cccbb4157d5da34ca98f77a0ac9d68e1e740 [Evidence] When upstream code is compiled, output of lscpu is correctly displayed: Vendor ID: ARM Model name: Neoverse-V2 [What Could Go Wrong] The fix does not apply directly to Jammy's version, as other commits change sys-utils/lscpu-arm.c. The suggestion is only to add the missing arm_part to the list. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/2019856/+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 2019856] Re: Add missing ARM-cores to support Grace-based systems
adds jammy debdiff ** Patch added: "lp-2019856-add-missing-arm-cores-jammy.debdiff" https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/2019856/+attachment/5673887/+files/lp-2019856-add-missing-arm-cores-jammy.debdiff ** Changed in: util-linux (Ubuntu Jammy) Status: New => In Progress ** Changed in: util-linux (Ubuntu Lunar) Status: New => In Progress -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to util-linux in Ubuntu. https://bugs.launchpad.net/bugs/2019856 Title: Add missing ARM-cores to support Grace-based systems Status in util-linux package in Ubuntu: New Status in util-linux source package in Jammy: In Progress Status in util-linux source package in Lunar: In Progress Bug description: [Impact] When running "lscpu" on a Grace-based system + Ubuntu 22.04, it doesn't report a model name: Vendor ID: ARM Model: 0 [Fix] Adding the additional arm_part to sys-utils/lscpu-arm.c solves the problem. The commit below adds the specific codes missing from Jammy's version. https://github.com/util-linux/util- linux/commit/6857cccbb4157d5da34ca98f77a0ac9d68e1e740 [Evidence] When upstream code is compiled, output of lscpu is correctly displayed: Vendor ID: ARM Model name: Neoverse-V2 [What Could Go Wrong] The fix does not apply directly to Jammy's version, as other commits change sys-utils/lscpu-arm.c. The suggestion is only to add the missing arm_part to the list. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/2019856/+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 2020089] [NEW] Update to 20230311 bundle
*** This bug is a security vulnerability *** Public security bug reported: This is a tracking bug to update the ca-certificates database to 2.60 ** Affects: ca-certificates (Ubuntu) Importance: Undecided Status: Fix Released ** Affects: ca-certificates (Ubuntu Bionic) Importance: Undecided Assignee: Marc Deslauriers (mdeslaur) Status: In Progress ** Affects: ca-certificates (Ubuntu Focal) Importance: Undecided Assignee: Marc Deslauriers (mdeslaur) Status: In Progress ** Affects: ca-certificates (Ubuntu Jammy) Importance: Undecided Assignee: Marc Deslauriers (mdeslaur) Status: In Progress ** Affects: ca-certificates (Ubuntu Kinetic) Importance: Undecided Assignee: Marc Deslauriers (mdeslaur) Status: In Progress ** Affects: ca-certificates (Ubuntu Lunar) Importance: Undecided Status: Fix Released ** Affects: ca-certificates (Ubuntu Mantic) Importance: Undecided Status: Fix Released ** Also affects: ca-certificates (Ubuntu Kinetic) Importance: Undecided Status: New ** Also affects: ca-certificates (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: ca-certificates (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: ca-certificates (Ubuntu Mantic) Importance: Undecided Status: New ** Also affects: ca-certificates (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: ca-certificates (Ubuntu Lunar) Importance: Undecided Status: New ** Changed in: ca-certificates (Ubuntu Lunar) Status: New => Fix Released ** Changed in: ca-certificates (Ubuntu Mantic) Status: New => Fix Released ** Changed in: ca-certificates (Ubuntu Bionic) Status: New => In Progress ** Changed in: ca-certificates (Ubuntu Focal) Status: New => In Progress ** Changed in: ca-certificates (Ubuntu Jammy) Status: New => In Progress ** Changed in: ca-certificates (Ubuntu Kinetic) Status: New => In Progress ** Changed in: ca-certificates (Ubuntu Bionic) Assignee: (unassigned) => Marc Deslauriers (mdeslaur) ** Changed in: ca-certificates (Ubuntu Focal) Assignee: (unassigned) => Marc Deslauriers (mdeslaur) ** Changed in: ca-certificates (Ubuntu Jammy) Assignee: (unassigned) => Marc Deslauriers (mdeslaur) ** Changed in: ca-certificates (Ubuntu Kinetic) Assignee: (unassigned) => Marc Deslauriers (mdeslaur) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ca-certificates in Ubuntu. https://bugs.launchpad.net/bugs/2020089 Title: Update to 20230311 bundle Status in ca-certificates package in Ubuntu: Fix Released Status in ca-certificates source package in Bionic: In Progress Status in ca-certificates source package in Focal: In Progress Status in ca-certificates source package in Jammy: In Progress Status in ca-certificates source package in Kinetic: In Progress Status in ca-certificates source package in Lunar: Fix Released Status in ca-certificates source package in Mantic: Fix Released Bug description: This is a tracking bug to update the ca-certificates database to 2.60 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ca-certificates/+bug/2020089/+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 2020086] Re: Consider shipping keama, The KEA Migration Assistant
** Bug watch added: Debian Bug tracker #1036277 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1036277 ** Also affects: isc-dhcp (Debian) via https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1036277 Importance: Unknown Status: Unknown -- 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/2020086 Title: Consider shipping keama, The KEA Migration Assistant Status in isc-dhcp package in Ubuntu: Triaged Status in isc-dhcp package in Debian: Unknown Bug description: The KEA Migration Assistant (aka keama) is an experimental tool which helps to translate ISC DHCP configurations to Kea [1]. It is maintained within the isc-dhcp sources [2], therefore, it is reasonable to ship it as another binary within the isc-dhcp package. The build process should be straightforward and all the package needs to ship is a binary file and a manpage. [1] https://kb.isc.org/docs/migrating-from-isc-dhcp-to-kea-dhcp-using-the-migration-assistant [2] https://gitlab.isc.org/isc-projects/dhcp/tree/master/keama To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/2020086/+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 2020086] [NEW] Consider shipping keama, The KEA Migration Assistant
Public bug reported: The KEA Migration Assistant (aka keama) is an experimental tool which helps to translate ISC DHCP configurations to Kea [1]. It is maintained within the isc-dhcp sources [2], therefore, it is reasonable to ship it as another binary within the isc-dhcp package. The build process should be straightforward and all the package needs to ship is a binary file and a manpage. [1] https://kb.isc.org/docs/migrating-from-isc-dhcp-to-kea-dhcp-using-the-migration-assistant [2] https://gitlab.isc.org/isc-projects/dhcp/tree/master/keama ** Affects: isc-dhcp (Ubuntu) Importance: Undecided Assignee: Athos Ribeiro (athos-ribeiro) Status: Triaged ** Tags: server-todo ** Changed in: isc-dhcp (Ubuntu) Assignee: (unassigned) => Athos Ribeiro (athos-ribeiro) ** Changed in: isc-dhcp (Ubuntu) Status: New => Triaged ** Tags added: server-todo -- 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/2020086 Title: Consider shipping keama, The KEA Migration Assistant Status in isc-dhcp package in Ubuntu: Triaged Bug description: The KEA Migration Assistant (aka keama) is an experimental tool which helps to translate ISC DHCP configurations to Kea [1]. It is maintained within the isc-dhcp sources [2], therefore, it is reasonable to ship it as another binary within the isc-dhcp package. The build process should be straightforward and all the package needs to ship is a binary file and a manpage. [1] https://kb.isc.org/docs/migrating-from-isc-dhcp-to-kea-dhcp-using-the-migration-assistant [2] https://gitlab.isc.org/isc-projects/dhcp/tree/master/keama To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/2020086/+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 2017142] Re: [jammy] VA-API doesn't work on DCN 3.1.4
** Tags removed: verification-needed verification-needed-jammy ** Tags added: verification-done verification-done-jammy -- 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/2017142 Title: [jammy] VA-API doesn't work on DCN 3.1.4 Status in mesa package in Ubuntu: Fix Released Status in mesa source package in Jammy: Fix Committed Bug description: [ Impact ] VA-API decoding doesn't work on DCN 3.1.4. Mesa 22.2.5 includes all the code to support it but is missing the chip ID. The device ID was included in upstream mesa 22.3.1. [ Test Plan ] * Verify that VA-API works using "mpv" or a similar tool that uses VA-API * Verify that '# vainfo' shows the correct information. [ Where problems could occur ] * If just the new ID is backported then they would be unique to DCN 3.1.4 as it's now running VA-API codepaths. * If newer mesa point release is adopted, then it could be a regression that happened in changes on common code in mesa between those two point releases. [ Other Info ] * It can be cherry picked with this single commit: https://gitlab.freedesktop.org/mesa/mesa/-/commit/4291e545d5a0f18c652f0ea57907f445392e8858 * AMD has already tested cherry-picked commit on top of the Ubuntu mesa 22.2.5 package and verified it works. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/2017142/+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 2017142] Re: [jammy] VA-API doesn't work on DCN 3.1.4
Looks positive on my end with mesa proposed -- 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/2017142 Title: [jammy] VA-API doesn't work on DCN 3.1.4 Status in mesa package in Ubuntu: Fix Released Status in mesa source package in Jammy: Fix Committed Bug description: [ Impact ] VA-API decoding doesn't work on DCN 3.1.4. Mesa 22.2.5 includes all the code to support it but is missing the chip ID. The device ID was included in upstream mesa 22.3.1. [ Test Plan ] * Verify that VA-API works using "mpv" or a similar tool that uses VA-API * Verify that '# vainfo' shows the correct information. [ Where problems could occur ] * If just the new ID is backported then they would be unique to DCN 3.1.4 as it's now running VA-API codepaths. * If newer mesa point release is adopted, then it could be a regression that happened in changes on common code in mesa between those two point releases. [ Other Info ] * It can be cherry picked with this single commit: https://gitlab.freedesktop.org/mesa/mesa/-/commit/4291e545d5a0f18c652f0ea57907f445392e8858 * AMD has already tested cherry-picked commit on top of the Ubuntu mesa 22.2.5 package and verified it works. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/2017142/+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 2019927] Re: package linux-firmware 20230323.gitbcdcfbcf-0ubuntu1 failed to install/upgrade: installed linux-firmware package post-installation script subprocess returned error e
Ah, yeah, I had to do quite a bit of manual zsysctl removal before the new kernel could be installed. Sorry, I got confused with what the error was about, when I reported it, that `failed with exit code 1: No PulseAudio daemon running` seemed to be the issue. But I guess that's just coincidental, please close this bug. -- 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/2019927 Title: package linux-firmware 20230323.gitbcdcfbcf-0ubuntu1 failed to install/upgrade: installed linux-firmware package post-installation script subprocess returned error exit status 1 Status in initramfs-tools package in Ubuntu: New Bug description: This bug report showed up after rebooting first time to 23.04. I have not yet noticed anything actually broken in the system, but uptime is only 6 minutes. ProblemType: Package DistroRelease: Ubuntu 23.04 Package: linux-firmware 20230323.gitbcdcfbcf-0ubuntu1 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 CasperMD5CheckResult: pass Date: Tue May 16 23:41:05 2023 Dependencies: firmware-sof-signed 2.2.4-1 ErrorMessage: installed linux-firmware package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2021-03-21 (786 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Alpha amd64 (20210321) MachineType: ASUSTeK COMPUTER INC. ZenBook UX425IA_UM425IA PackageArchitecture: all ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_bpduzc@/vmlinuz-6.2.0-20-generic root=ZFS=rpool/ROOT/ubuntu_bpduzc ro quiet splash vt.handoff=1 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.11, Python 3.11.2, python3-minimal, 3.11.2-1 PythonDetails: N/A RelatedPackageVersions: grub-pc 2.06-2ubuntu16 SourcePackage: initramfs-tools Title: package linux-firmware 20230323.gitbcdcfbcf-0ubuntu1 failed to install/upgrade: installed linux-firmware package post-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to lunar on 2023-05-17 (0 days ago) dmi.bios.date: 09/16/2020 dmi.bios.release: 5.16 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX425IA.307 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX425IA 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: 3.7 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX425IA.307:bd09/16/2020:br5.16:efr3.7:svnASUSTeKCOMPUTERINC.:pnZenBookUX425IA_UM425IA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX425IA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:sku: dmi.product.family: ZenBook dmi.product.name: ZenBook UX425IA_UM425IA 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/initramfs-tools/+bug/2019927/+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 2017770] Re: "Enter code on ubuntu.com/pro/attach" is not clickable URL like everything else
** Merge proposal linked: https://code.launchpad.net/~xnox/software-properties/+git/software-properties/+merge/443188 -- 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/2017770 Title: "Enter code on ubuntu.com/pro/attach" is not clickable URL like everything else Status in software-properties package in Ubuntu: Confirmed Bug description: Enter code on ubuntu.com/pro/attach is not a clickable url. however ubuntu.com/pro and "register new account" are. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/2017770/+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 2018538] Re: All PDFs when printed come out mirror image
In the time being, I've ended up having to use [cpdf](https://github.com/coherentgraphics/cpdf-binaries) to make a mirrored copy of the PDF I want to print. It's not ideal, but at least I can print PDFs I can read them without looking at it through a mirror. The command I use to flip them is ` ./cpdf -i input.pdf -hflip -o out.pdf ` -- 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/2018538 Title: All PDFs when printed come out mirror image Status in cups package in Ubuntu: Confirmed Bug description: Since updating to Ubuntu 23.04. Whenever I try to print a PDF (regardless of application the PDF is open in) it will print the PDF in mirror image. If I enable printing mirror image in the settings, every other page become mirror image as instead. (I'm printing double sided/long edge print, so one side is normal and the other side becomes mirror image when I do this). I'm trying to print to a HP Colour LaserJet CP2025dn Note: If I print from my second device when it was running Ubuntu 22.10 it would print normally, but as soon as I updated it to 23.04, it started having the same issue as well. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: ubiquity (not installed) ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 Uname: Linux 6.2.0-20-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu May 4 20:31:48 2023 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed maybe-ubiquity quiet splash --- InstallationDate: Installed on 2022-10-22 (194 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) SourcePackage: ubiquity Symptom: installation UpgradeStatus: Upgraded to lunar on 2023-04-21 (13 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/2018538/+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 2019745] Re: problem closing a window on the desktop
*** This bug is a duplicate of bug 2012388 *** https://bugs.launchpad.net/bugs/2012388 Sounds like you're getting blocked by bug 2012388 ** Package changed: xorg (Ubuntu) => ubuntu ** This bug has been marked a duplicate of bug 2012388 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/2019745 Title: problem closing a window on the desktop Status in Ubuntu: New Bug description: If I fully open my Firefox or any program and then I want to close it nothing happens.You have to drag the window from the title bar downwards and move it away from the top of the screen. Any app that's fully open has the same problem. Only happens since I upgraded. I am using dual screen and this happens on the screen on the first line. 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 .tmp.unity_support_test.0: ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon May 15 19:05:39 2023 DistUpgraded: Fresh install DistroCodename: lunar DistroVariant: ubuntu DkmsStatus: nvidia/390.157, 6.2.0-20-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Cezanne [Radeon Vega Series / Radeon Vega Mobile Series] [1002:1638] (rev c9) (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd Cezanne [Radeon Vega Series / Radeon Vega Mobile Series] [1458:d000] InstallationDate: Installed on 2020-05-19 (1091 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: Gigabyte Technology Co., Ltd. B550 AORUS ELITE V2 ProcEnviron: LANG=en_ZA.UTF-8 LANGUAGE=en_ZA:en PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-20-generic root=UUID=7ccfa3c6-7f5e-43fc-8097-6169b339d161 ro ...security=apparmor apparmor=1... SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/04/2022 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: F14 dmi.board.asset.tag: Default string dmi.board.name: B550 AORUS ELITE V2 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrF14:bd01/04/2022:br5.17:svnGigabyteTechnologyCo.,Ltd.:pnB550AORUSELITEV2:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnB550AORUSELITEV2:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring: dmi.product.family: B550 MB dmi.product.name: B550 AORUS ELITE V2 dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz 1:0.9.14.2+22.10.20220822-0ubuntu3 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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/2019745/+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 2019481] Re: Xorg freeze
Thanks for the bug report. Please reproduce the problem again so we can collect the full system log, then reboot to a terminal and run: journalctl -b-1 > prevboot.txt and attach the resulting text file here. Although your Xorg log already mentions: [20.820] (EE) NVIDIA(GPU-0): Failed to initialize the NVIDIA GPU at PCI:1:0:0. Please [20.820] (EE) NVIDIA(GPU-0): check your system's kernel log for additional error [20.820] (EE) NVIDIA(GPU-0): messages and refer to Chapter 8: Common Problems in the [20.820] (EE) NVIDIA(GPU-0): README for additional information. [20.820] (EE) NVIDIA(GPU-0): Failed to initialize the NVIDIA graphics device! we still need to see what happened before that. ** Summary changed: - Xorg freeze + System boots to a black screen when nvidia-390 is installed ** Package changed: xorg (Ubuntu) => nvidia-graphics-drivers-390 (Ubuntu) ** Changed in: nvidia-graphics-drivers-390 (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/2019481 Title: System boots to a black screen when nvidia-390 is installed Status in nvidia-graphics-drivers-390 package in Ubuntu: Incomplete Bug description: Upon installing the 3rd party nVidia version 390 drivers for the Dell E6520 laptop, after reboot hangs with a black screen and a blinking cursor in the upper left hand corner. Booting to a terminal prompt and using "sudo apt remove *nvidia*" and rebooting solves the issue. This did NOT happen in 22.04 LTS on this laptop with no other hardware or BIOS changes. This install of 23.04 was a clean install, the 22.04 install was wiped. vendor : NVIDIA Corporation model: GF119M [NVS 4200M] driver : nvidia-driver-390 - distro non-free recommended driver : xserver-xorg-video-nouveau - distro free builtin If I install that driver the system will not boot, removing it solves the issue. I've wiped and reinstalled 23.04 4x, both with full options and minimal, the problem always returns. 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: unknown CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat May 13 10:46:41 2023 DistUpgraded: Fresh install DistroCodename: lunar DistroVariant: ubuntu ExtraDebuggingInterest: Yes GpuHangFrequency: Continuously GpuHangReproducibility: Yes, I can easily reproduce it GpuHangStarted: Immediately after installing this version of Ubuntu GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0126] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell 2nd Generation Core Processor Family Integrated Graphics Controller [1028:0494] NVIDIA Corporation GF119M [NVS 4200M] [10de:1056] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Dell GF119M [NVS 4200M] [1028:1494] InstallationDate: Installed on 2023-05-13 (0 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418) MachineType: Dell Inc. Latitude E6520 ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-20-generic root=UUID=f7260292-99f4-4e45-a79a-97643cc0cb92 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/06/2018 dmi.bios.release: 4.6 dmi.bios.vendor: Dell Inc. dmi.bios.version: A21 dmi.board.name: 0692FT dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA21:bd03/06/2018:br4.6:svnDellInc.:pnLatitudeE6520:pvr01:rvnDellInc.:rn0692FT:rvrA00:cvnDellInc.:ct9:cvr:sku: dmi.product.name: Latitude E6520 dmi.product.version: 01 dmi.sys.vendor: Dell 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 this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/2019481/+subscriptions -- Mailing list:
[Touch-packages] [Bug 2019230] Re: Standard Notes Black Display
Were you actually using Xorg or Wayland when the problem happened? Sounds like the same mutter issue as bug 1987976. ** Package changed: xorg (Ubuntu) => mutter (Ubuntu) ** Changed in: mutter (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/2019230 Title: Standard Notes Black Display Status in mutter package in Ubuntu: Incomplete Bug description: When I launch the application "Standard Notes" the application window appears as solid black. I have had to change from using the Nvidia graphics driver under 22.10 to the Nouveau driver since upgrading to 23.04 because the Nvidia 390 driver wasn't working (I have a GeForce GT 730 graphics card). 1) Ubuntu Release: 23.04 2) xorg package: 1:7.7+23ubuntu2 3) What I expected to happen: the Standard Notes would launch normally and would be usable. 4) What happened instead: the Standard Notes window launches but is a solid blob of black - the application is completely unusable. 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: unknown CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu May 11 17:55:20 2023 DistUpgraded: 2023-05-02 13:20:29,911 DEBUG icon theme changed, re-reading DistroCodename: lunar DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GF108 [GeForce GT 730] [10de:0f02] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. GF108 [GeForce GT 730] [1043:84f6] InstallationDate: Installed on 2019-05-04 (1467 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-20-generic root=UUID=0d1374ee-63ea-4275-8996-fad19b20d6e1 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to lunar on 2023-05-02 (9 days ago) dmi.bios.date: 01/18/2019 dmi.bios.release: 5.13 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2012 dmi.board.asset.tag: Default string dmi.board.name: PRIME B360M-A dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2012:bd01/18/2019:br5.13:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEB360M-A:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:skuASUS_MB_CNL: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: ASUS_MB_CNL dmi.product.version: System Version dmi.sys.vendor: System manufacturer 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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2019230/+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 2019165] Re: It takes 56 seconds to open a window/program
Please try: * Running the affected apps in a Terminal window to see if they log anything. * Running 'gnome-extensions list --enabled' to see if any extensions other than the three Ubuntu extensions are active. * Running 'journalctl -f' to see if anything is flooding the system log. Your attached kernel log suggests there is a recurring issue with sof-audio-pci-intel-cnl which may be an audio driver bug, Nvidia driver bug, or hardware problem. ** 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/2019165 Title: It takes 56 seconds to open a window/program Status in Ubuntu: Incomplete Bug description: Yes, even more than that, it takes 56 seconds to open a program, to display a context menu, to open a new tab, but everything is okay within the window, such as typing. It happens in gnome terminal, file manager (nautilus), settings, firefox, etc. But it doesn't happen to chromium. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: x11-common 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.19.0-41.42~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-41-generic x86_64 .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 Open Kernel Module for x86_64 530.41.03 Release Build (dvs-builder@U16-T02-35-3) Thu Mar 16 19:33:35 UTC 2023 GCC version: gcc version 11.3.0 (Ubuntu 11.3.0-1ubuntu1~22.04.1) ApportVersion: 2.20.11-0ubuntu82.4 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu May 11 08:58:18 2023 Dependencies: lsb-base 11.1.0ubuntu4 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation CometLake-H GT2 [UHD Graphics] [8086:9bc4] (rev 05) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company CometLake-H GT2 [UHD Graphics] [103c:878e] NVIDIA Corporation TU106M [GeForce RTX 2060 Max-Q] [10de:1f12] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company TU106M [GeForce RTX 2060 Max-Q] [103c:878e] InstallationDate: Installed on 2021-06-05 (704 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) MachineType: HP HP ENVY Laptop 15-ep0xxx PackageArchitecture: all ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-41-generic root=UUID=34001051-5122-4187-b21f-2032a99219e8 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/30/2021 dmi.bios.release: 15.7 dmi.bios.vendor: AMI dmi.bios.version: F.07 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 878E dmi.board.vendor: HP dmi.board.version: 18.33 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 18.33 dmi.modalias: dmi:bvnAMI:bvrF.07:bd07/30/2021:br15.7:efr18.33:svnHP:pnHPENVYLaptop15-ep0xxx:pvr:rvnHP:rn878E:rvr18.33:cvnHP:ct10:cvrChassisVersion:sku16P91PA#AR6: dmi.product.family: 103C_5335KV HP ENVY dmi.product.name: HP ENVY Laptop 15-ep0xxx dmi.product.sku: 16P91PA#AR6 dmi.sys.vendor: HP nvidia-settings: ERROR: A query to find an object was unsuccessful version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.2.5-0ubuntu0.1~22.04.1 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.4-2ubuntu1.7~22.04.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1 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/2019165/+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 2018734] Re: Mouse events stop being propagated to most of the application windows
Sounds like VirtualBox had a "grab" on the mouse. ** Package changed: xorg (Ubuntu) => virtualbox (Ubuntu) ** Summary changed: - Mouse events stop being propagated to most of the application windows + Mouse events stop being propagated to most of the application windows when VirtualBox is running -- 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/2018734 Title: Mouse events stop being propagated to most of the application windows when VirtualBox is running Status in virtualbox package in Ubuntu: New Bug description: Bug starts replicating randonly after unlocking the screen. Mouse events stop being propageted to windows of most of the applications. That includes Window decorator. Windows also cannot be dragged. Keyboard events work fine. Problem does not affect the desktop, notification and activities bar, lock screen, launcher, settings, terminal, gnome-text-editor, Ubuntu Software. Problem was reproduced with applications: Google Chrome, MS Edge, Firefox, VS Code, Oracle Virtual Box, Gimp Only way to recover right now is to restart system. 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 8 14:29:24 2023 DistUpgraded: 2023-04-21 18:19:49,810 DEBUG icon theme changed, re-reading DistroCodename: lunar DistroVariant: ubuntu DkmsStatus: virtualbox/7.0.6, 6.2.0-20-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Lucienne [1002:164c] (rev c1) (prog-if 00 [VGA controller]) Subsystem: Dell Lucienne [1028:0a77] InstallationDate: Installed on 2023-04-13 (24 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) MachineType: Dell Inc. Inspiron 5415 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.2.0-20-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to lunar on 2023-04-21 (16 days ago) dmi.bios.date: 02/13/2023 dmi.bios.release: 1.15 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.15.0 dmi.board.name: 0WKFHK dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 1.15.0 dmi.modalias: dmi:bvnDellInc.:bvr1.15.0:bd02/13/2023:br1.15:svnDellInc.:pnInspiron5415:pvr1.15.0:rvnDellInc.:rn0WKFHK:rvrA00:cvnDellInc.:ct10:cvr1.15.0:sku0A77: dmi.product.family: Inspiron dmi.product.name: Inspiron 5415 dmi.product.sku: 0A77 dmi.product.version: 1.15.0 dmi.sys.vendor: Dell 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 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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/virtualbox/+bug/2018734/+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 2019152] Re: Bluetooth crashes in Ubuntu 23.04
Next time the problem happens, before rebooting please run: journalctl -b0 > journal.txt or after rebooting: journalctl -b-1 > prevboot.txt and attach the resulting text file here. ** Package changed: bluez (Ubuntu) => linux (Ubuntu) ** Changed in: linux (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/2019152 Title: Bluetooth crashes in Ubuntu 23.04 Status in linux package in Ubuntu: Incomplete Bug description: Bluetooth stops working. Mouse (logitech M720) stopped mid scroll. Never had any problems with this mouse under Ubuntu before. Workaround: Reboot fixes the problem. Switching in and out of airplane mode gets bluetooth working again Frequency: Second time this has happened since upgrade from 22.10 (about 2 weeks ago) Limited knowledge fault tracing: >sudo systemctl restart bluetooth doesn't make any difference >rfkill shows no bluetooth device >lspci ... 3b:00.0 Network controller: Intel Corporation Wireless 8265 / 8275 (rev 78) ... Ubuntu settings - show bluetooth is off, but I didn't disable it and it can't be re-enabled. So I assume the driver has crashed, but I don't know how to find out more about this. Could collect some more info next time it happens if someone tells me what to do. >lsb_release -rd No LSB modules are available. Description: Ubuntu 23.04 Release: 23.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2019152/+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
