[Bug 1973322] Re: Bacula for 22.04/Jammy
FYI I have rebuilt the version of bacula for jammy in a PPA - https://launchpad.net/~alexmurray/+archive/ubuntu/lp1973322 - if anyone could give this a test and let me know how it works for you, then we can look at trying to release it via an SRU. Thanks. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1973322 Title: Bacula for 22.04/Jammy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bacula/+bug/1973322/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1970563] Re: Qemu 1:6.2+dfsg-2ubuntu6 deadlock bug
Completed in Kinetic, uploaded to Jammy now - waiting for the SRU team to have a look -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1970563 Title: Qemu 1:6.2+dfsg-2ubuntu6 deadlock bug To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1970563/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1975599] Re: jammy/linux-raspi: Update to upstream raspberrypi rpi-5.15.y (2022-05-24)
** Tags added: kern-3384 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1975599 Title: jammy/linux-raspi: Update to upstream raspberrypi rpi-5.15.y (2022-05-24) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1975599/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1871015] Re: test_vxlan_under_vrf.sh in net from ubuntu_kernel_selftests failed with H (Check VM connectivity through VXLAN (underlay in the default VRF) [FAIL])
** Changed in: linux (Ubuntu Impish) Assignee: (unassigned) => Po-Hsu Lin (cypressyew) ** Changed in: ubuntu-kernel-tests Assignee: (unassigned) => Po-Hsu Lin (cypressyew) ** Changed in: linux (Ubuntu Impish) Status: Confirmed => In Progress ** Changed in: ubuntu-kernel-tests Status: New => In Progress -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1871015 Title: test_vxlan_under_vrf.sh in net from ubuntu_kernel_selftests failed with H (Check VM connectivity through VXLAN (underlay in the default VRF) [FAIL]) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1871015/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1975665] [NEW] /usr/lib/x86_64-linux-gnu/kodi/kodi.bin: symbol lookup error: /usr/lib/x86_64-linux-gnu/kodi/kodi.bin: undefined symbol: _ZN7wayland9display_tC1ENSt7__cxx1112basic_stringIcSt11char
Public bug reported: Looks like this was a breaking change introduced in 0.2.9 release in Jan 2022, it has since been patched https://github.com/NilsBrause/waylandpp/releases Debian article about the bug https://bugs.debian.org/cgi- bin/bugreport.cgi?bug=1006812 Which would be good since Ubuntu only has 0.2.8 in its repo but i believe that the issue was patched backwards into 0.2.8-2, judging by the identical error message. Recommend including 0.2.10 or higher in the stable ubuntu repo to address ** Affects: waylandpp (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1975665 Title: /usr/lib/x86_64-linux-gnu/kodi/kodi.bin: symbol lookup error: /usr/lib/x86_64-linux-gnu/kodi/kodi.bin: undefined symbol: _ZN7wayland9display_tC1ENSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEE To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/waylandpp/+bug/1975665/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1871148] Re: services start before apparmor profiles are loaded
Oh, thanks Alex, I forgot that we have our own service for loading the AppArmor profiles of the snaps! Etienne, could you please show the output of sudo systemctl status snapd.apparmor ? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1871148 Title: services start before apparmor profiles are loaded To manage notifications about this bug go to: https://bugs.launchpad.net/apparmor/+bug/1871148/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1973847] Re: Sometimes Firefox could not change mode from English to Japanese
Hi,
nakasima@asrock:~$ gsettings get org.gnome.desktop.input-sources sources
[('ibus', 'mozc-jp'), ('xkb', 'jp')]
nakasima@asrock:~$
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1973847
Title:
Sometimes Firefox could not change mode from English to Japanese
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mozc/+bug/1973847/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1971933] Re: [Regression] Unable to wake laptop using trackpad input
$ pwd /sys/devices/pci:00/:00:15.1/i2c_designware.1/i2c-2/i2c-DLL0798:00/power $ sudo ls -l total 0 -rw-r--r-- 1 root root 4096 May 24 19:13 async -rw-r--r-- 1 root root 4096 May 24 19:13 autosuspend_delay_ms -rw-r--r-- 1 root root 4096 May 24 19:13 control -r--r--r-- 1 root root 4096 May 24 19:13 runtime_active_kids -r--r--r-- 1 root root 4096 May 24 19:13 runtime_active_time -r--r--r-- 1 root root 4096 May 24 19:13 runtime_enabled -r--r--r-- 1 root root 4096 May 24 19:13 runtime_status -r--r--r-- 1 root root 4096 May 24 19:13 runtime_suspended_time -r--r--r-- 1 root root 4096 May 24 19:13 runtime_usage -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1971933 Title: [Regression] Unable to wake laptop using trackpad input To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1971933/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1971933] Re: [Regression] Unable to wake laptop using trackpad input
I did, there is no "wakeup" file. I used tab auto-complete to reach there. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1971933 Title: [Regression] Unable to wake laptop using trackpad input To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1971933/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1975493] Re: [MIR] manila
Assigning to ubuntu-security for further review. Manila uses exactly the same modules as the majority of other OpenStack services for security related touchpoints as I've noted in my review which may determine the depth of security review needed for this package. ** Changed in: manila (Ubuntu) Milestone: None => ubuntu-22.10 ** Changed in: manila (Ubuntu) Assignee: James Page (james-page) => Ubuntu Security Team (ubuntu-security) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1975493 Title: [MIR] manila To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/manila/+bug/1975493/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1975493] Re: [MIR] manila
[Summary] Generally this package and Manila itself are carbon copies of the other OpenStack Services packaged for Ubuntu. There are no red flags and the package uses all of the existing in main oslo modules used for OpenStack services (WSGI, serialization, root escalation++). As this package provides a network service and processes user provided data (JSON) this does need a security review, so I'll assign ubuntu-security. List of specific binary packages to be promoted to main: - manila-api - manila-share - manila-scheduler - manila-data These should be added to the appropriate seed for Ubuntu. Notes: See below Required TODOs: None Recommended TODOs: - This package uses the complex set of tools that the Debian OpenStack team uses for managing maintainer scripts, systemd units etc. Not a block but it would be good to see where we can simplify this usage for the needs of Ubuntu users and to reduce the overhead of package maintenace. [Duplication] - There is no other package in main providing the same functionality. [Dependencies] OK: - no other Dependencies to MIR due to this - no -dev/-debug/-doc packages that need exclusion [Embedded sources and static linking] OK: - no embedded source present - no static linking [Security] OK: - history of CVEs does not look concerning - does not run a daemon as root - does not use webkit1,2 - does not use lib*v8 directly - does not process arbitrary web content - does not use centralized online accounts - does not integrate arbitrary javascript into the desktop - does not deal with system authentication (eg, pam), etc)a NOTE: - does parse data formats Manila service use JSON serialization for processing of API requests and for RPC messaging - uses the oslo.seralization module already in main. - does open a port Manila API service provides access via WSGI which uses the oslo.service module already in main. oslo.policy and kesytoneauth1 are use for authentication and authorization for specific endpoints. [Common blockers] OK: - does not FTBFS currently - does have a test suite that runs at build time - test suite fails will fail the build upon error. - does have a test suite that runs as autopkgtest - The package has a team bug subscriber - no translation present, but none needed for this case (user visible)? - no new python2 dependency - Python package that is using dh_python [Packaging red flags] OK: - Ubuntu does carry a delta, but it is reasonable and maintenance under control - symbols tracking not applicable for this kind of code. - d/watch is present and looks ok - Upstream update history is good - Debian/Ubuntu update history is good - the current release is packaged - promoting this does not seem to cause issues for MOTUs that so far maintained the package - no massive Lintian warnings - d/rules is rather clean - Does not have Built-Using [Upstream red flags] OK: - no Errors/warnings during the build - no incautious use of malloc/sprintf (as far as I can check it) - no use of gksu, pkexec, or LD_LIBRARY_PATH - no use of user nobody - no use of setuid - no important open bugs (crashers, etc) in Debian or Ubuntu - no dependency on webkit, qtwebkit, seed or libgoa-* - not part of the UI for extra checks NOTE: - use of sudo by manila-share service however uses oslo.rootwrap to whitelist commands to control priviledge escalation ** Changed in: manila (Ubuntu) Status: In Progress => New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1975493 Title: [MIR] manila To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/manila/+bug/1975493/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1927808] Re: rtw88_8821ce causes freeze
There are many new fixes for rtw88 driver in linux-next, please give it a try: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/log/drivers/net/wireless/realtek/rtw88 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1927808 Title: rtw88_8821ce causes freeze To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1927808/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1951220] Re: Caja and Nautilus umacceptably slow for more than 50 files
[Expired for caja (Ubuntu) because there has been no activity for 60 days.] ** Changed in: caja (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1951220 Title: Caja and Nautilus umacceptably slow for more than 50 files To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/caja/+bug/1951220/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1966336] Re: gnome-disks crashed with SIGSEGV in get_all_native_children()
[Expired for gnome-disk-utility (Ubuntu) because there has been no activity for 60 days.] ** Changed in: gnome-disk-utility (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1966336 Title: gnome-disks crashed with SIGSEGV in get_all_native_children() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-disk-utility/+bug/1966336/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1951220] Re: Caja and Nautilus umacceptably slow for more than 50 files
[Expired for nautilus (Ubuntu) because there has been no activity for 60 days.] ** Changed in: nautilus (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1951220 Title: Caja and Nautilus umacceptably slow for more than 50 files To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/caja/+bug/1951220/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1961859] Re: When we install ModemManager1.16.6 and others, this will lead to ubuntu can not enter into GNOME UI.
[Expired for modemmanager (Ubuntu) because there has been no activity for 60 days.] ** Changed in: modemmanager (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1961859 Title: When we install ModemManager1.16.6 and others, this will lead to ubuntu can not enter into GNOME UI. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/modemmanager/+bug/1961859/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1966407] Re: UI bug
[Expired for update-notifier (Ubuntu) because there has been no activity for 60 days.] ** Changed in: update-notifier (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1966407 Title: UI bug To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/update-notifier/+bug/1966407/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1971933] Re: [Regression] Unable to wake laptop using trackpad input
Some characters may need to escape, so it's better to cd to the sysfs directory first. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1971933 Title: [Regression] Unable to wake laptop using trackpad input To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1971933/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1975444] Re: mt7921e wifi fails to resume after suspend
Please give mainline kernel a try: https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.18/amd64/ -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1975444 Title: mt7921e wifi fails to resume after suspend To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1975444/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1971933] Re: [Regression] Unable to wake laptop using trackpad input
$ sudo ls -l /sys/devices/pci:00/:00:15.1/i2c_designware.1/i2c-2/i2c-DLL0798:00/power/wakeup ls: cannot access '/sys/devices/pci:00/:00:15.1/i2c_designware.1/i2c-2/i2c-DLL0798:00/power/wakeup': No such file or directory -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1971933 Title: [Regression] Unable to wake laptop using trackpad input To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1971933/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1975444] Re: mt7921e wifi fails to resume after suspend
[ 63.782837] mt7921e :02:00.0: can't change power state from D3cold to D0 (config space inaccessible) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1975444 Title: mt7921e wifi fails to resume after suspend To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1975444/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1975660] [NEW] Disabling fprintd.service prevents boot
Public bug reported: Disabling fprintd.service prevents boot. System: Ubuntu Desktop 22.04 Behavior: Rebooting immediately after disabling and masking fprintd.service, fails. A series of [DEPEND] messages scroll past in tty1 early in the boot process, too quickly to read but that appear to be mount units failing for want of a dependency. Consistently, the last message to appear in tty1 is: [ OK ] Reached Target Printer Support Expected behavior: No disruption in boot process from the deletion of an irrelevant service for which no hardware exists. Unfortunately, no further information is available because the machine resists booting. - While booted to a separate partition, I deleted the symlink in /etc/systemd/system to /dev/null, but boot failed thereafter in the same way. - I chrooted into the partition to attempt to re-enable the unit but the command failed by reason of being in a chroot environment. - The partition's syslog has no entries containing DEPEND, probably because they occurred before rsyslog could receive input from the kernel ring buffer. ** Affects: fprintd (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1975660 Title: Disabling fprintd.service prevents boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fprintd/+bug/1975660/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1975657] [NEW] Installer crashed on Raspberry Pi
Public bug reported: trying to install ubuntu mate on my raspberry Pi 2 Model B ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: ubiquity 21.10.10 ProcVersionSignature: Ubuntu 5.13.0-1009.10-raspi 5.13.14 Uname: Linux 5.13.0-1009-raspi armv7l ApportVersion: 2.20.11-0ubuntu71 Architecture: armhf CasperMD5CheckResult: unknown Date: Tue May 24 23:25:40 2022 ImageMediaBuild: 20211105 ProcEnviron: TERM=linux PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 LC_NUMERIC=C.UTF-8 SourcePackage: ubiquity UbiquityDebug: UbiquitySyslog: UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: ubiquity (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug armhf armhf-image impish oem-config raspi-image -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1975657 Title: Installer crashed on Raspberry Pi To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1975657/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1971933] Re: [Regression] Unable to wake laptop using trackpad input
There's no "/sys/devices/pci:00/:00:15.1/i2c_designware.1/i2c-2/i2c-DLL0798:00/power/wakeup"? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1971933 Title: [Regression] Unable to wake laptop using trackpad input To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1971933/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1965563] Re: gnome-extensions-app fails to start [Error reading events from display: Protocol error]
Also affected (bug 1975647). Notably, this happened after I attempted to dual boot Debian 11 (stable, then testing). The workspace indicator extension worked before then, but disappeared after I switched back. user@host:~$ gnome-extensions-app Gdk-Message: 20:03:19.701: Error flushing display: Protocol error user@host:~$ cheese (cheese:32950): Gdk-WARNING **: 20:04:45.134: Native Windows taller than 65535 pixels are not supported Gdk-Message: 20:04:46.246: Error 71 (Protocol error) dispatching to Wayland display. user@host:~$ In syslog: gnome-shell[2051]: WL: error in client communication (pid 32877) cheese[32877]: Error reading events from display: Protocol error -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1965563 Title: gnome-extensions-app fails to start [Error reading events from display: Protocol error] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1965563/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1969939] Re: puppet 5 package incompatible with ruby 3 / ubuntu 22.04
As an SRU team member, it's unclear to me whether the errors reported in this verification are introduced by this update or are merely existing problems that the code now hits because it's getting further. It's also not clear to me what the effect of these errors is - if these are just harmless warnings printed, that's ok, but if they are exposing real problems that's an issue. Even more if they're exposing problems that might hit users that are not already broken by this bug. Can we please get an analysis of what - if anything - is broken here? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1969939 Title: puppet 5 package incompatible with ruby 3 / ubuntu 22.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/puppet/+bug/1969939/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1970927] Re: r8152 tx status -71
Please attach dmesg when the issue happens, thanks! ** Changed in: linux (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1970927 Title: r8152 tx status -71 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1970927/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1972134] Re: AMD APU s2idle is broken after the ASIC reset fix
** Tags removed: verification-needed-focal ** Tags added: verification-done-focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1972134 Title: AMD APU s2idle is broken after the ASIC reset fix To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1972134/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1975647] Re: gnome shell extensions crashes on launch
*** This bug is a duplicate of bug 1965563 *** https://bugs.launchpad.net/bugs/1965563 ** This bug has been marked a duplicate of bug 1965563 gnome-extensions-app fails to start [Error reading events from display: Protocol error] -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1975647 Title: gnome shell extensions crashes on launch To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1975647/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1971757] Re: wslu prevents opening files/directories on desktop, and peripherals on the dock
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: wslu (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1971757 Title: wslu prevents opening files/directories on desktop, and peripherals on the dock To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gimp-help/+bug/1971757/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1971757] Re: wslu prevents opening files/directories on desktop, and peripherals on the dock
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gimp-help (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1971757 Title: wslu prevents opening files/directories on desktop, and peripherals on the dock To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gimp-help/+bug/1971757/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1975635] Re: PC Freeze on 5.13.0.40
Thank you for taking the time to report this bug and helping to make Ubuntu better. When reporting bugs in the future please use apport by using 'ubuntu- bug' and the name of the package affected. You can learn more about this functionality at https://wiki.ubuntu.com/ReportingBugs. Please note: `ubuntu-bug`, `apport` & bug reporting tools are provided with Ubuntu by default, many require manual addition for some releases of downstream OSes based on Ubuntu (eg. Linux Mint). You should check with your distribution first. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1975635 Title: PC Freeze on 5.13.0.40 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1975635/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1975647] Re: gnome shell extensions crashes on launch
If the problem is not bug 1965563 then please check for crashes by following https://wiki.ubuntu.com/Bugs/Responses#Missing_a_crash_report_or_having_a_.crash_attachment If the problem is not a crash but a hang then please turn it into a crash report by sending the process a fatal signal like 'kill -ABRT ...' and then follow the above link. ** Tags added: jammy ** Changed in: gnome-shell (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1975647 Title: gnome shell extensions crashes on launch To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1975647/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1975650] Re: Display stuck in low resolution
** Description changed: I often have to forcibly power down my PC because of this bug: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1970808. Well, the most recent time I did that, when the computer restarted, the resolution is stuck on 1024x768 even though I am on a 1920x1080 monitor. I restarted my PC again and it is still stuck on the low resolution. This Ask Ubuntu answer (https://askubuntu.com/a/1167437/1589552) did allow me to force my resolution to 1920x1080, but a few things still seemed off: - The display settings page in the Gnome settings app still showed my display as "unknown display" and did not have any options for changing the resolution. - A WebGL-based application I use for work was very slow compared to normal. I reverted the change to my Grub config and now I'm back to 1024x768. I have an Nvidia GTX 1060 connected to a 1920x1080 monitor via HDMI. Let me know of any other information I can provide that would be helpful. Also let me know if there is a workaround other than reinstalling the OS. + Edit: I have a Windows dual boot on this PC, with Windows installed on a + separate SSD. I booted into Windows and everything seems completely + fine. This provides further evidence that this is a software issue, not + a hardware one. + ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-33.34-generic 5.15.30 Uname: Linux 5.15.0-33-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue May 24 20:14:55 2022 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: - NVIDIA Corporation GP106 [GeForce GTX 1060 3GB] [10de:1c02] (rev a1) (prog-if 00 [VGA controller]) -Subsystem: Micro-Star International Co., Ltd. [MSI] GP106 [GeForce GTX 1060 3GB] [1462:3287] + NVIDIA Corporation GP106 [GeForce GTX 1060 3GB] [10de:1c02] (rev a1) (prog-if 00 [VGA controller]) + Subsystem: Micro-Star International Co., Ltd. [MSI] GP106 [GeForce GTX 1060 3GB] [1462:3287] InstallationDate: Installed on 2022-04-23 (31 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: Gigabyte Technology Co., Ltd. B450M DS3H ProcEnviron: - TERM=xterm-256color - PATH=(custom, no user) - XDG_RUNTIME_DIR= - LANG=en_US.UTF-8 - SHELL=/usr/bin/zsh + TERM=xterm-256color + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=en_US.UTF-8 + SHELL=/usr/bin/zsh ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-33-generic root=UUID=c4ac1391-7d4e-4282-94ba-fbae3c4c044c ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/25/2019 dmi.bios.release: 5.13 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F4 dmi.board.asset.tag: Default string dmi.board.name: B450M DS3H-CF 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.:bvrF4:bd01/25/2019:br5.13:svnGigabyteTechnologyCo.,Ltd.:pnB450MDS3H:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnB450MDS3H-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring: dmi.product.family: Default string dmi.product.name: B450M DS3H 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.110-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.1-1ubuntu2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1975650 Title: Display stuck in low resolution To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1975650/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1975621] Status changed to Confirmed
This change was made by a bot. ** Changed in: linux (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1975621 Title: [Star Labs Lite IV] screen flashes on-off unless PSR is turned off To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1975621/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1966860] Re: hit issue with script rescan-scsi-bus.sh in VM with image ubuntu 22.04 live server running in ESXi
> it looks to me like there may be a hardware problem involved? I suspect it's issue of script file rescan-scsi-bus.sh. VMware have developed own file rescan-scsi-bus.sh and this script file works well with these steps. > Why are you seeing so many I/O errors? I think it's because the boot disk /dev/sda is removed by command "rescan-scsi-bus.sh -a -r" unexpectedly. So we will see many I/O errors when access the file in /dev/sda. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1966860 Title: hit issue with script rescan-scsi-bus.sh in VM with image ubuntu 22.04 live server running in ESXi To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sg3-utils/+bug/1966860/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1969959] Re: [nouveau] Weird colors after startup (Ubuntu 22.04)
Pipewire isn't involved in putting pixels on the screen. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1969959 Title: [nouveau] Weird colors after startup (Ubuntu 22.04) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1969959/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1943587] Re: [Ethtool][TSN] Support frame preemption
This might be an Aaeon issue; maybe only 1 port supports TSN? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1943587 Title: [Ethtool][TSN] Support frame preemption To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1943587/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1969598] Re: Desktop Icons NG steals keyboard focus from apps after workspace switch
** Also affects: gnome-shell-extension-desktop-icons-ng via https://gitlab.com/rastersoft/desktop-icons-ng/-/issues/235 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1969598 Title: Desktop Icons NG steals keyboard focus from apps after workspace switch To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1969598/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1968911] Re: assertion failures in cr_parser_new_from_buf and cr_declaration_parse_list_from_buf
** 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 Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1968911 Title: assertion failures in cr_parser_new_from_buf and cr_declaration_parse_list_from_buf To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1968911/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1975549] Re: NetworkManager uses tethered Android phone as ethernet connection instead of wired ethernet connection
> It's a bit weird, https://launchpadlibrarian.net/602981658/nmcli-dev.txt > shows no connection associated to the usb device nor IP for it Thanks again Sebastien. This may be because I booted the machine with the phone unplugged. I can run apport again with the phone plugged in (and then reboot) to duplicate the issue. Would you like me to run apport again after booting with the phone plugged in? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1975549 Title: NetworkManager uses tethered Android phone as ethernet connection instead of wired ethernet connection To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1975549/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1975621] Re: [Star Labs Lite IV] screen flashes on-off unless PSR is turned off
** Summary changed: - screen flashes on-off unless PSR is turned off + [Star Labs Lite IV] screen flashes on-off unless PSR is turned off ** Package changed: xorg (Ubuntu) => linux (Ubuntu) ** Tags added: psr -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1975621 Title: [Star Labs Lite IV] screen flashes on-off unless PSR is turned off To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1975621/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1972802] Re: enable config for fixing 5.17 kernel won't load mok
5.17-oem-1007 kernel have the fix, wait it's landing and then do verification. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1972802 Title: enable config for fixing 5.17 kernel won't load mok To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1972802/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1972722] Re: Include gtk4 changes needed for mutter 42.1
This bug was fixed in the package gtk4 - 4.6.3+ds1-0ubuntu1 --- gtk4 (4.6.3+ds1-0ubuntu1) jammy; urgency=medium [ Jeremy Bicha ] * New upstream bugfix release (LP: #1973219) * Cherry-pick additional bug fixes: - Fix text view scrolling with mutter 42.1 (LP: #1972722) - Work around infinite loop in box allocation (Closes: #1010547) - Make it easier to select the current folder with a file chooser - Fix saving into a subdirectory with a file chooser - Fix an invalid format string with EGL support [ Simon McVittie ] * d/log-reftests.py: Update names of GSK renderers * d/rules, d/run-tests.sh: Add infrastructure to ignore failing GSK tests * Ignore unaligned-offscreen GSK comparison test -- Jeremy Bicha Thu, 12 May 2022 11:41:48 -0400 ** Changed in: gtk4 (Ubuntu Jammy) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1972722 Title: Include gtk4 changes needed for mutter 42.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk4/+bug/1972722/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1972722] Update Released
The verification of the Stable Release Update for gtk4 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 Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1972722 Title: Include gtk4 changes needed for mutter 42.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk4/+bug/1972722/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1973219] Re: Update gtk4 to 4.6.3
This bug was fixed in the package gtk4 - 4.6.3+ds1-0ubuntu1 --- gtk4 (4.6.3+ds1-0ubuntu1) jammy; urgency=medium [ Jeremy Bicha ] * New upstream bugfix release (LP: #1973219) * Cherry-pick additional bug fixes: - Fix text view scrolling with mutter 42.1 (LP: #1972722) - Work around infinite loop in box allocation (Closes: #1010547) - Make it easier to select the current folder with a file chooser - Fix saving into a subdirectory with a file chooser - Fix an invalid format string with EGL support [ Simon McVittie ] * d/log-reftests.py: Update names of GSK renderers * d/rules, d/run-tests.sh: Add infrastructure to ignore failing GSK tests * Ignore unaligned-offscreen GSK comparison test -- Jeremy Bicha Thu, 12 May 2022 11:41:48 -0400 ** Changed in: gtk4 (Ubuntu Jammy) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1973219 Title: Update gtk4 to 4.6.3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk4/+bug/1973219/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1973219] Update Released
The verification of the Stable Release Update for gtk4 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 Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1973219 Title: Update gtk4 to 4.6.3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk4/+bug/1973219/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1973091] Re: Ubuntu 22.04: libusb-1.0.25 breaks libinklevel and ink
This bug was fixed in the package libusb-1.0 - 2:1.0.25-1ubuntu2 --- libusb-1.0 (2:1.0.25-1ubuntu2) jammy; urgency=medium * debian/patches/git_backward_compat.patch: revert a behaviour change in libusb 1.0.25 which triggers issues when the API is misused, fix ink segfaulting (lp: #1973091) -- Sebastien Bacher Fri, 13 May 2022 13:20:38 +0200 ** Changed in: libusb-1.0 (Ubuntu Jammy) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1973091 Title: Ubuntu 22.04: libusb-1.0.25 breaks libinklevel and ink To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libusb-1.0/+bug/1973091/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1971164] Re: [Azure][CVM] hv/bounce buffer: Fix a race that can fail disk detection
This bug is awaiting verification that the linux-azure- cvm/5.4.0-1080.83+cvm1 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-focal' to 'verification- done-focal'. If the problem still exists, change the tag 'verification- needed-focal' to 'verification-failed-focal'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1971164 Title: [Azure][CVM] hv/bounce buffer: Fix a race that can fail disk detection To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure-cvm/+bug/1971164/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1973091] Update Released
The verification of the Stable Release Update for libusb-1.0 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 Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1973091 Title: Ubuntu 22.04: libusb-1.0.25 breaks libinklevel and ink To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libusb-1.0/+bug/1973091/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 359309] Re: mysql client package has broken SSL support
MySQL 5.1 has long been EOL in Ubuntu and upstream. Please open a new bug if MySQL 5.7 or MySQL 8.0 as shipped in currently supported Ubuntu version still have the problem. ** Changed in: mysql-dfsg-5.1 (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/359309 Title: mysql client package has broken SSL support To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mysql-dfsg-5.1/+bug/359309/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1971576] Re: SATA device hot plug regression on AMD EPYC (Asus) server
@Mario, May I ask you another 2 extending questions. A. What is results in a AMD client( like laptop)? I thought this hot plug works out of box in client, what cause this difference from kernel/code? B. I was told that hot plug works out of box on their Intel's server. What cause this difference? thanks, Mao -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1971576 Title: SATA device hot plug regression on AMD EPYC (Asus) server To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1971576/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1786013] Autopkgtest regression report (linux-meta-aws-5.4/5.4.0.1073.55)
All autopkgtests for the newly accepted linux-meta-aws-5.4 (5.4.0.1073.55) for bionic have finished running. The following regressions have been reported in tests triggered by the package: lxc/3.0.3-0ubuntu1~18.04.1 (amd64) kpatch/0.5.0-0ubuntu1.1 (amd64) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/bionic/update_excuses.html#linux-meta-aws-5.4 [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1786013 Title: Packaging resync To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1786013/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1974262] Re: Ubuntu 20.04 Xen Dom0 Cannot Boot
Thanks, Bryce. I can report it on Debian, but not sure what version to report it against. Given that 20.04 is an LTS, doesn't changing the compression of the kernel in a way that causes breakages a significant regression? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1974262 Title: Ubuntu 20.04 Xen Dom0 Cannot Boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xen/+bug/1974262/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1970270] Re: LibreOffice localization is not working out of the box
The attachment "Bind-mounts /run/systemd/resolve from the live environment to the installed system during installation, allowing packages to be installed at OS install time." seems to be a patch. If it isn't, please remove the "patch" flag from the attachment, remove the "patch" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team. [This is an automated message performed by a Launchpad user owned by ~brian-murray, for any issues please contact him.] ** Tags added: patch -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1970270 Title: LibreOffice localization is not working out of the box To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/calamares-settings-ubuntu/+bug/1970270/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1970672] Re: makedumpfile falls back to cp with "__vtop4_x86_64: Can't get a valid pmd_pte."
Thanks everyone for trying to tackle this long-standing issue. fwiw, here's my $0.02 no how we could proceed: Someone should draft a special case page for makedumpfile: https://wiki.ubuntu.com/StableReleaseUpdates#Documentation_for_Special_Cases I'm happy to review/provide feedback, but I'd rather someone who would be carrying out the plan drive it. As others have mentioned, testing is the hard part, and we need to define what will be tested in the special case documentation. Since makedumpfile is really just a filter, I don't think we need to (or reasonably could) boot a bunch of systems in different configs and generate crashdumps for every new update. Rather, i think we could build a repository of representative, unfiltered, /proc/vmcore files that focal's existing makedumpfile can parse. Then we can just check that all of those files can still be parsed by the proposed makedumpfile. With some scripting and a multi-architecture cloud, this could be automated. In fact, if this vmcore repo were online, we could implement this an autopkgtest (w/ needs-internet set). But we should also do at least one end-to-end kdump, just to make sure the kdump-tools->makedumpfile interface hasn't been broken. What is a representative sample? One of each of the current LTS and HWE kernels on amd64, arm64, ppc64el and s390x seems like an obvious start (or the subset of those that actually work today). I don't think the machine type is as important, VMs should be fine IMO. If we know of examples where different machines expose structures differently in a way that makedumpfile cares about, then perhaps add those as well. Once a new makedumpfile lands that adds support for a new HWE kernel, we should probably then update the repo w/ vmcore samples from that kernel, so we can make sure the next update doesn't regress that support (probably convenient to do when verifying the SRU, since I imagine we'd be testing that it works w/ the new HWE kernel then anyway). It'd be good to note in the special case request that kdump-tools does fall back to a raw /proc/vmcore file cp if makedumpfile fails, which can mitigate regressions for a subset of users - those with the necessary disk space and lack of time constraints. While I agree that crash falls into the same category, I don't think it necessarily needs to happen at the same time. Obviously users running focal need to dump their vmcore using focal - bug for developers debugging a crash, I don't think it is to onerous to use a newer version of Ubuntu. Again, I'm no saying we *shouldn't* add crash to the special case, it just seems like a makedumpfile exception is significantly more important. Finally, I don't think we need to commit to a frequency of backports, or a point at which they will stop. Rather we can just stick to agreeing on how it *can* be done when someone has the time/interest in doing it. Guillherme's LTS->LTS+1 scheme sounds like a reasonable pattern to shoot for, but if that doesn't happen every time, we're still improving the situation over the status quo. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1970672 Title: makedumpfile falls back to cp with "__vtop4_x86_64: Can't get a valid pmd_pte." To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/makedumpfile/+bug/1970672/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1975650] [NEW] Display stuck in low resolution
Public bug reported: I often have to forcibly power down my PC because of this bug: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1970808. Well, the most recent time I did that, when the computer restarted, the resolution is stuck on 1024x768 even though I am on a 1920x1080 monitor. I restarted my PC again and it is still stuck on the low resolution. This Ask Ubuntu answer (https://askubuntu.com/a/1167437/1589552) did allow me to force my resolution to 1920x1080, but a few things still seemed off: - The display settings page in the Gnome settings app still showed my display as "unknown display" and did not have any options for changing the resolution. - A WebGL-based application I use for work was very slow compared to normal. I reverted the change to my Grub config and now I'm back to 1024x768. I have an Nvidia GTX 1060 connected to a 1920x1080 monitor via HDMI. Let me know of any other information I can provide that would be helpful. Also let me know if there is a workaround other than reinstalling the OS. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-33.34-generic 5.15.30 Uname: Linux 5.15.0-33-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue May 24 20:14:55 2022 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GP106 [GeForce GTX 1060 3GB] [10de:1c02] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] GP106 [GeForce GTX 1060 3GB] [1462:3287] InstallationDate: Installed on 2022-04-23 (31 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: Gigabyte Technology Co., Ltd. B450M DS3H ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/usr/bin/zsh ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-33-generic root=UUID=c4ac1391-7d4e-4282-94ba-fbae3c4c044c ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/25/2019 dmi.bios.release: 5.13 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F4 dmi.board.asset.tag: Default string dmi.board.name: B450M DS3H-CF 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.:bvrF4:bd01/25/2019:br5.13:svnGigabyteTechnologyCo.,Ltd.:pnB450MDS3H:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnB450MDS3H-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring: dmi.product.family: Default string dmi.product.name: B450M DS3H 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.110-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.1-1ubuntu2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy resolution ubuntu ** Attachment added: "Display settings" https://bugs.launchpad.net/bugs/1975650/+attachment/5592732/+files/Screenshot%20from%202022-05-24%2020-18-45.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1975650 Title: Display stuck in low resolution To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1975650/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1942394] Re: [MIR] mdevctl 1.0.0 (rust switch)
** Tags added: packaging -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1942394 Title: [MIR] mdevctl 1.0.0 (rust switch) To manage notifications about this bug go to: https://bugs.launchpad.net/mdevctl/+bug/1942394/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1581864] Re: nginx.service: Failed to read PID from file /run/nginx.pid: Invalid argument
** Tags added: packaging -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1581864 Title: nginx.service: Failed to read PID from file /run/nginx.pid: Invalid argument To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nginx/+bug/1581864/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1948699] Re: Please enable luajit for arm64
** Tags added: packaging -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1948699 Title: Please enable luajit for arm64 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nginx/+bug/1948699/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1971251] Re: Merge multipath-tools from Debian unstable for kinetic
** Description changed: Upstream: 0.8.9 - Debian: 0.8.8-1 + Debian: 0.8.8-1 Ubuntu: 0.8.8-1ubuntu1 Debian typically updates multipath-tools every 3 months on average, but it was last updated 22.01 and looks overdue. Check back in on this monthly. + > # https://pad.lv/1961633 - +(Triaged) [multipath-tools] - Consider + > dropping d/p/kpartx-Improve-finding-loopback-devic… + > + > This bug is in our backlog and has not been touched in 60 days. I think we + > should consider this when merging multipath-tool during the KK cycle. + ### New Debian Changes ### multipath-tools (0.8.8-1) unstable; urgency=medium - [ Utkarsh Gupta ] - * [74952ce] d/t/kpartx-file-loopback: silence gdisk warnings on stderr - * [a3ad859] d/t/tgtbasedmpaths: Use stable wwn-* names in autopkgtest - * [7a22711] d/t/tgtbasedmpaths: Add sleep to allow for device creation - - [ Ritesh Raj Sarraf ] - * [9169942] Add some documentation about LVM + DM-Multipath setup. - Thanks to Carlos Barros (Closes: 1001710) - - [ Chris Hofstaedtler ] - * [7fcb8ba] New upstream version 0.8.8 - * [e63a379] Refresh patches - * [4ab9ce2] Drop old dmsetup_env hack - dmsetup long supports DM_NAME and DM_UUID, and the other variables - are not used anymore. - * [2cd669e] Avoid installing libmpathvalid.so until users appear - - -- Chris Hofstaedtler Sun, 16 Jan 2022 22:57:28 + [ Utkarsh Gupta ] + * [74952ce] d/t/kpartx-file-loopback: silence gdisk warnings on stderr + * [a3ad859] d/t/tgtbasedmpaths: Use stable wwn-* names in autopkgtest + * [7a22711] d/t/tgtbasedmpaths: Add sleep to allow for device creation + + [ Ritesh Raj Sarraf ] + * [9169942] Add some documentation about LVM + DM-Multipath setup. + Thanks to Carlos Barros (Closes: 1001710) + + [ Chris Hofstaedtler ] + * [7fcb8ba] New upstream version 0.8.8 + * [e63a379] Refresh patches + * [4ab9ce2] Drop old dmsetup_env hack + dmsetup long supports DM_NAME and DM_UUID, and the other variables + are not used anymore. + * [2cd669e] Avoid installing libmpathvalid.so until users appear + + -- Chris Hofstaedtler Sun, 16 Jan 2022 22:57:28 + multipath-tools (0.8.5-2) unstable; urgency=medium - * [373f5c5] Fix bashism in script kpartx/kpartx_id. - Thanks to Julien Cristau (Closes: #987669) - - -- Ritesh Raj Sarraf Wed, 28 Apr 2021 22:40:55 +0530 + * [373f5c5] Fix bashism in script kpartx/kpartx_id. + Thanks to Julien Cristau (Closes: #987669) + + -- Ritesh Raj Sarraf Wed, 28 Apr 2021 22:40:55 +0530 multipath-tools (0.8.5-1) unstable; urgency=medium - [ Ritesh Raj Sarraf ] - * [9e88f52] Add README.alua to docs section - - [ Christian Ehrhardt ] - * [7860503] d/t/tgtbasedmpaths: reduce memory pressure avoiding OOM - triggered false positives - - [ Chris Hofstaedtler ] - * [859ade1] Update upstream git (and our debian/watch) URL - * [bdc291a] New upstream version 0.8.5 - * [83060d2] Rebase patches - * [cb467ba] multipath.rules: Avoid usrmerge paths (Closes: #973853) - * [61df246] kpartx: update package description (Closes: #690995) - * [3262269] Drop 0001-Blacklist-cciss-devices.patch. - Upstream has switched to an exclusive list of devices by default. - Only sd, dasd and nvme devices are seen by multipath now. This makes - the cciss exclusion obsolete. - * [602298a] Follow README.md rename - * [2018daf] Remove obsolete override for lintian tag - init.d-script-does-not-implement-optional-option - - -- Chris Hofstaedtler Wed, 23 Dec 2020 23:53:53 + [ Ritesh Raj Sarraf ] + * [9e88f52] Add README.alua to docs section + + [ Christian Ehrhardt ] + * [7860503] d/t/tgtbasedmpaths: reduce memory pressure avoiding OOM + triggered false positives + + [ Chris Hofstaedtler ] + * [859ade1] Update upstream git (and our debian/watch) URL + * [bdc291a] New upstream version 0.8.5 + * [83060d2] Rebase patches + * [cb467ba] multipath.rules: Avoid usrmerge paths (Closes: #973853) + * [61df246] kpartx: update package description (Closes: #690995) + * [3262269] Drop 0001-Blacklist-cciss-devices.patch. + Upstream has switched to an exclusive list of devices by default. + Only sd, dasd and nvme devices are seen by multipath now. This makes + the cciss exclusion obsolete. + * [602298a] Follow README.md rename + * [2018daf] Remove obsolete override for lintian tag + init.d-script-does-not-implement-optional-option + + -- Chris Hofstaedtler Wed, 23 Dec 2020 23:53:53 + multipath-tools (0.8.4-4) unstable; urgency=medium - * [637efc8] Remove overly complicated INSTALL_PROGRAM setup. - Thanks to Simon McVittie (Closes: #968528) - * [d793f77] kpartx, multipath-tools: remove pre-oldstable upgrade code - * [aa2fab9] d/*: trim trailing whitespace - * [1657612] multipath-tools, multipath-tools-boot: update lintian overrides - * [825c1e2] debian/po/de.po:
[Bug 1961633] Re: Consider dropping d/p/kpartx-Improve-finding-loopback-device-by-file.patch
** Tags added: packaging -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1961633 Title: Consider dropping d/p/kpartx-Improve-finding-loopback-device-by- file.patch To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/1961633/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1909941] Re: xdg-email changes break simple-scan email functionality
I'm also having the same issue with xdg-utils 1.1.3-4ubuntu1 on 22.04, using thunderbird 91.9.1 using: xdg-email --attach filename does open the thunderbird compose window, but no attachment... Tried on 3 different computers, same result. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1909941 Title: xdg-email changes break simple-scan email functionality To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xdg-utils/+bug/1909941/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1949297] Re: nvidia-340 340.108-0ubuntu5.20.04.2: nvidia-340 kernel module failed to build
Does anyone monitor this forum at all? If so, I would like to ask a question. Since this bug is clearly a result of the Nvidia driver, is there a way to revert the current kernel to use the generic graphics driver rather than the Nvidia driver? Since the GUI won't launch due to the incompatible graphics driver, is there a way to enter a command to revert the video driver outside of the GUI? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1949297 Title: nvidia-340 340.108-0ubuntu5.20.04.2: nvidia-340 kernel module failed to build To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/1949297/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1973033] Re: [MIR] wpebackend-fdo
** Tags added: sec-1034 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1973033 Title: [MIR] wpebackend-fdo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wpebackend-fdo/+bug/1973033/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1971297] Re: Merge nginx from Debian unstable for kinetic
** Description changed: Upstream: tbd - Debian: 1.18.0-9 + Debian: 1.18.0-9 Ubuntu: 1.18.0-6ubuntu14.1 - + As part of the merge, please also consider these bugs: + LP: #1948699 - + Confirmed [nginx] 24.11.21 Low - Please enable luajit for arm64 + LP: #1581864 -Confirmed [nginx] 16.12.21 Low - nginx.service: Failed to read PID from file /run/nginx.pid:… ### New Debian Changes ### nginx (1.18.0-9) unstable; urgency=medium - [ Jan Mojžíš ] - * http-lua: Downgrade to 0.10.13 (Closes: #1008787). - * http-lua: Backport upstream bugfix for segfault in nginx core >= 1.15.0 - when libnginx-mod-http-lua is loaded and init_worker_by_lua* is used. - * d/control: Add mips64el,ppc64,kfreebsd-amd64 to list of luajit platforms. - * d/control: fix Homepage nginx.net -> nginx.org (Closes: #976158) - - [ Thomas Ward ] - * d/watch: Update watch syntax to match all even versions of NGINX releases - rather than use a watch syntax that is static to one specific version. - This will fix the untracked 'New upstream stable versions' problem. - * d/control: Update 'uploaders' as Thomas Ward is now a maintainer in - the Salsa repository. - - -- Jan Mojžíš Tue, 05 Apr 2022 19:11:47 +0200 + [ Jan Mojžíš ] + * http-lua: Downgrade to 0.10.13 (Closes: #1008787). + * http-lua: Backport upstream bugfix for segfault in nginx core >= 1.15.0 + when libnginx-mod-http-lua is loaded and init_worker_by_lua* is used. + * d/control: Add mips64el,ppc64,kfreebsd-amd64 to list of luajit platforms. + * d/control: fix Homepage nginx.net -> nginx.org (Closes: #976158) + + [ Thomas Ward ] + * d/watch: Update watch syntax to match all even versions of NGINX releases + rather than use a watch syntax that is static to one specific version. + This will fix the untracked 'New upstream stable versions' problem. + * d/control: Update 'uploaders' as Thomas Ward is now a maintainer in + the Salsa repository. + + -- Jan Mojžíš Tue, 05 Apr 2022 19:11:47 +0200 nginx (1.18.0-8) unstable; urgency=medium - * Restore patch: - d/p/Resolver-fixed-off-by-one-write-in-ngx_resolver_copy.patch - - -- Ondřej Nový Tue, 15 Mar 2022 13:23:06 +0100 + * Restore patch: + d/p/Resolver-fixed-off-by-one-write-in-ngx_resolver_copy.patch + + -- Ondřej Nový Tue, 15 Mar 2022 13:23:06 +0100 nginx (1.18.0-7) unstable; urgency=medium - [ Ondřej Nový ] - * d/p/CVE-2019-20372.patch: Drop, applied upstream. - * http-auth-pam: Upgrade to 1.5.3. - * http-echo: Upgrade to 0.62. - * nchan: Upgrade to 1.2.15. - * http-fancyindex: Upgrade to 0.5.2. - * rtmp: Upgrade to 1.2.2. - * http-lua: Upgrade to 0.10.15 (Closes: #994178). - * http-lua: Rebase patch. - * nchan: Drop GCC 10 patch, applied upstream. - * d/watch: Bump version to 4. - * Bump standards version to 4.6.1 (no changes). - * d/copyright: Bump my copyright year. - - [ Ondřej Surý ] - * Add arm64 and ppc64el to list of luajit platforms. - - [ Athos Ribeiro ] - * d/nginx-common.nginx.service: Fix service shutdown description to mention - SIGQUIT instead of SIGSTOP (LP: #1919965). - - -- Ondřej Nový Tue, 15 Mar 2022 11:50:18 +0100 + [ Ondřej Nový ] + * d/p/CVE-2019-20372.patch: Drop, applied upstream. + * http-auth-pam: Upgrade to 1.5.3. + * http-echo: Upgrade to 0.62. + * nchan: Upgrade to 1.2.15. + * http-fancyindex: Upgrade to 0.5.2. + * rtmp: Upgrade to 1.2.2. + * http-lua: Upgrade to 0.10.15 (Closes: #994178). + * http-lua: Rebase patch. + * nchan: Drop GCC 10 patch, applied upstream. + * d/watch: Bump version to 4. + * Bump standards version to 4.6.1 (no changes). + * d/copyright: Bump my copyright year. + + [ Ondřej Surý ] + * Add arm64 and ppc64el to list of luajit platforms. + + [ Athos Ribeiro ] + * d/nginx-common.nginx.service: Fix service shutdown description to mention + SIGQUIT instead of SIGSTOP (LP: #1919965). + + -- Ondřej Nový Tue, 15 Mar 2022 11:50:18 +0100 nginx (1.18.0-6.1) unstable; urgency=high - * Non-maintainer upload. - * Resolver: fixed off-by-one write in ngx_resolver_copy() (CVE-2021-23017) - (Closes: #989095) - - -- Salvatore Bonaccorso Sat, 29 May 2021 16:21:37 + * Non-maintainer upload. + * Resolver: fixed off-by-one write in ngx_resolver_copy() (CVE-2021-23017) + (Closes: #989095) + + -- Salvatore Bonaccorso Sat, 29 May 2021 16:21:37 +0200 nginx (1.18.0-6) unstable; urgency=medium - * Fix GCC-10 compatibility (Closes: #957605). - - -- Ondřej Nový Wed, 19 Aug 2020 15:27:02 +0200 + * Fix GCC-10 compatibility (Closes: #957605). + + -- Ondřej Nový Wed, 19 Aug 2020 15:27:02 +0200 nginx (1.18.0-5) unstable; urgency=medium - * Prevented request smuggling in LUA - CVE-2020-11724 - Closes: #964950 - - -- Ondřej Nový Tue, 14 Jul 2020 10:08:15 +0200 + * Prevented request smuggling in LUA + CVE-2020-11724
[Bug 1942394] Re: [MIR] mdevctl 1.0.0 (rust switch)
** Tags added: needs-sync ** Changed in: mdevctl (Ubuntu) Milestone: None => ubuntu-22.06 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1942394 Title: [MIR] mdevctl 1.0.0 (rust switch) To manage notifications about this bug go to: https://bugs.launchpad.net/mdevctl/+bug/1942394/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1975516] Re: System freeze
It happened again, with the laptop idle same as before. This time the screen went dark (backlight off) and the fans were spinning fast. I could feel the laptop was a bit hot. I had Transmission, LibreOffice Writer and GNOME Files running at the time. ** Attachment added: "journalctl log of the second freeze" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1975516/+attachment/5592731/+files/journalctl_2.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1975516 Title: System freeze To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1975516/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1946660] Re: Ubuntu port of v4l2loopback doesn't behave the same as official port (v0.12.5)
The issue persists into 22.04 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1946660 Title: Ubuntu port of v4l2loopback doesn't behave the same as official port (v0.12.5) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/v4l2loopback/+bug/1946660/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1970943] Re: OpenVPN connection fails with smartcard provided private key; please update pkcs11-helper
Hello Lorenz, or anyone else affected, Accepted pkcs11-helper into jammy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/pkcs11-helper/1.28-1ubuntu0.22.04.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- jammy to verification-done-jammy. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-jammy. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: pkcs11-helper (Ubuntu Jammy) Status: New => Fix Committed ** Tags added: verification-needed verification-needed-jammy -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1970943 Title: OpenVPN connection fails with smartcard provided private key; please update pkcs11-helper To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pkcs11-helper/+bug/1970943/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1970411] Re: gnome-remote-desktop-daemon crashes on fuse_thread_func → g_thread_proxy → start_thread: Failed to mount FUSE filesystem (as per missing fusermount3)
Hello errors.ubuntu.com, or anyone else affected, Accepted gnome-remote-desktop into jammy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/gnome-remote- desktop/42.1.1-0ubuntu1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- jammy to verification-done-jammy. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-jammy. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: gnome-remote-desktop (Ubuntu Jammy) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-jammy -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1970411 Title: gnome-remote-desktop-daemon crashes on fuse_thread_func → g_thread_proxy → start_thread: Failed to mount FUSE filesystem (as per missing fusermount3) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-remote-desktop/+bug/1970411/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1970662] Re: Update gnome-remote-desktop to 42.1.1
Hello Jeremy, or anyone else affected, Accepted gnome-remote-desktop into jammy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/gnome-remote- desktop/42.1.1-0ubuntu1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- jammy to verification-done-jammy. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-jammy. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: gnome-remote-desktop (Ubuntu Jammy) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-jammy -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1970662 Title: Update gnome-remote-desktop to 42.1.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-remote-desktop/+bug/1970662/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1971195] Re: gnome-remote-desktop leads to a session crash inside qemu with virtio-vga
Hello Allan, or anyone else affected, Accepted gnome-remote-desktop into jammy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/gnome-remote- desktop/42.1.1-0ubuntu1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- jammy to verification-done-jammy. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-jammy. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: gnome-remote-desktop (Ubuntu Jammy) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-jammy -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1971195 Title: gnome-remote-desktop leads to a session crash inside qemu with virtio- vga To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-remote-desktop/+bug/1971195/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1973028] Re: gnome-remote-desktop user service is always running
Hello Jeremy, or anyone else affected, Accepted gnome-remote-desktop into jammy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/gnome-remote- desktop/42.1.1-0ubuntu1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- jammy to verification-done-jammy. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-jammy. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: gnome-remote-desktop (Ubuntu Jammy) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-jammy -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1973028 Title: gnome-remote-desktop user service is always running To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-remote-desktop/+bug/1973028/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1973847] Re: Sometimes Firefox could not change mode from English to Japanese
Please run this command: gsettings get org.gnome.desktop.input-sources sources and let us know what it outputs. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1973847 Title: Sometimes Firefox could not change mode from English to Japanese To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mozc/+bug/1973847/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1975649] [NEW] flowtable: fix TCP flow teardown
Public bug reported: * Explain the feature This patch addresses three possible problems: 1. ct gc may race to undo the timeout adjustment of the packet path, leaving the conntrack entry in place with the internal offload timeout (one day). 2. ct gc removes the ct because the IPS_OFFLOAD_BIT is not set and the CLOSE timeout is reached before the flow offload del. 3. tcp ct is always set to ESTABLISHED with a very long timeout in flow offload teardown/delete even though the state might be already CLOSED. Also as a remark we cannot assume that the FIN or RST packet is hitting flow table teardown as the packet might get bumped to the slow path in nftables. This patch resets IPS_OFFLOAD_BIT from flow_offload_teardown(), so conntrack handles the tcp rst/fin packet which triggers the CLOSE/FIN state transition. Moreover, return the connection's ownership to conntrack upon teardown by clearing the offload flag and fixing the established timeout value. The flow table GC thread will asynchonrnously free the flow table and hardware offload entries. Before this patch, the IPS_OFFLOAD_BIT remained set for expired flows on which is also misleading since the flow is back to classic conntrack path. If nf_ct_delete() removes the entry from the conntrack table, then it calls nf_ct_put() which decrements the refcnt. This is not a problem because the flowtable holds a reference to the conntrack object from flow_offload_alloc() path which is released via flow_offload_free(). This patch also updates nft_flow_offload to skip packets in SYN_RECV state. Since we might miss or bump packets to slow path, we do not know what will happen there while we are still in SYN_RECV, this patch postpones offload up to the next packet which also aligns to the existing behaviour in tc-ct. flow_offload_teardown() does not reset the existing tcp state from flow_offload_fixup_tcp() to ESTABLISHED anymore, packets bump to slow path might have already update the state to CLOSE/FIN. * How to test Adding the following flows to the OVS bridge in DPU OS: # ovs-ofctl add-flow ovsbr1 "table=0, ip,ct_state=-trk, actions=ct(table=1)" # ovs-ofctl add-flow ovsbr1 "table=1, ip,ct_state=+new, actions=ct(commit),normal" # ovs-ofctl add-flow ovsbr1 "table=1, ip,ct_state=-new, actions=normal" Start netserver on SUT: # netserver -p 5007 Start multiple TCP_CRR tests on peer: # count=1;while [ $count -lt 10 ]; do screen -d -m netperf -t TCP_CRR -H 11.0.0.2 -l 360 -- -r 1 -O " MIN_LAETENCY, MAX_LATENCY, MEAN_LATENCY, P90_LATENCY, P99_LATENCY ,P999_LATENCY,P_LATENCY,STDDEV_LATENCY ,THROUGHPUT ,THROUGHPUT_UNITS "; count=`expr $count + 1`; done A huge number of connections will be established and tear down. After the tests, some of them are not aged out: # From /proc/net/nf_conntrack in DPU OS ipv4 2 tcp 6 86354 LAST_ACK src=11.0.0.1 dst=11.0.0.2 sport=35862 dport=46797 src=11.0.0.2 dst=11.0.0.1 sport=46797 dport=35862 [ASSURED] mark=0 zone=0 use=2 ipv4 2 tcp 6 86354 LAST_ACK src=11.0.0.1 dst=11.0.0.2 sport=35862 dport=46797 src=11.0.0.2 dst=11.0.0.1 sport=46797 dport=35862 [ASSURED] mark=0 zone=0 use=2 ipv4 2 tcp 6 86354 LAST_ACK src=11.0.0.1 dst=11.0.0.2 sport=35862 dport=46797 src=11.0.0.2 dst=11.0.0.1 sport=46797 dport=35862 [ASSURED] mark=0 zone=0 use=2 The issue is usually reproduced after running the for several times. * What it could break. N/A ** Affects: linux-bluefield (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1975649 Title: flowtable: fix TCP flow teardown To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/1975649/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1974235] Please test proposed package
Hello James, or anyone else affected, Accepted cloud-init into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/cloud- init/22.2-0ubuntu1~18.04.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-bionic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1974235 Title: sru cloud-init (22.1-14 to 22.2) Bionic, Focal, Impish, Jammy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1974235/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1974235] Please test proposed package
Hello James, or anyone else affected, Accepted cloud-init into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/cloud- init/22.2-0ubuntu1~20.04.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- focal to verification-done-focal. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-focal. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: cloud-init (Ubuntu Bionic) Status: New => Fix Committed ** Tags added: verification-needed-bionic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1974235 Title: sru cloud-init (22.1-14 to 22.2) Bionic, Focal, Impish, Jammy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1974235/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1974235] Re: sru cloud-init (22.1-14 to 22.2) Bionic, Focal, Impish, Jammy
Hello James, or anyone else affected, Accepted cloud-init into impish-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/cloud- init/22.2-0ubuntu1~21.10.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- impish to verification-done-impish. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-impish. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: cloud-init (Ubuntu Impish) Status: New => Fix Committed ** Tags added: verification-needed-impish ** Changed in: cloud-init (Ubuntu Focal) Status: New => Fix Committed ** Tags added: verification-needed-focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1974235 Title: sru cloud-init (22.1-14 to 22.2) Bionic, Focal, Impish, Jammy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1974235/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1975647] [NEW] gnome shell extensions crashes on launch
Public bug reported: When launching the Extensions app, the icon briefly appears in the dock and immediately disappears. No log can be found. Launching "/usr/bin/gnome-extensions-app --gapplication-service" in a terminal just hangs the process, with `strace` saying that it gets stuck in `wait4(-1,`. It may have something to do with dual booting Debian testing and sharing root possibly messing up some config files, but Extensions shouldn't just crash and should at least provide some errors or log output for troubleshooting. dpkg says that the desktop file is in package "gnome-shell-extension- prefs", but launchpad says that it doesn't exist in Ubuntu. Ubuntu 22.04 Gnome Wayland Nvidia 510.73.05 ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1975647 Title: gnome shell extensions crashes on launch To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1975647/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1971933] Re: [Regression] Unable to wake laptop using trackpad input
@kaihengfeng any workarounds? The device node "/sys/devices/pci:00/:00:15.1/i2c_designware.1/i2c-2/i2c-DLL0798:00" doesn't have "wakeup" file to write "enabled" to ... Am I missing something ? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1971933 Title: [Regression] Unable to wake laptop using trackpad input To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1971933/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1974235] Re: sru cloud-init (22.1-14 to 22.2) Bionic, Focal, Impish, Jammy
Hello James, or anyone else affected, Accepted cloud-init into jammy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/cloud- init/22.2-0ubuntu1~22.04.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- jammy to verification-done-jammy. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-jammy. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: cloud-init (Ubuntu Jammy) Status: New => Fix Committed ** Tags added: verification-needed verification-needed-jammy -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1974235 Title: sru cloud-init (22.1-14 to 22.2) Bionic, Focal, Impish, Jammy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1974235/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1958019]
Appears that these kernels are including these drivers. You might have to figure out how to build your own kernel while enabling the necessary kernel options yourself after all. On 5/24/22 01:46, bugzilla-dae...@kernel.org wrote: > https://bugzilla.kernel.org/show_bug.cgi?id=208555 > > --- Comment #616 from she...@liang.at (she...@liang.at) --- > Oh, sorry I was in the wrong one version cuz I tried reverting to the older > one > when nvidia didn't work anymore. > > In kernel 5.17.0 the first command gives > $ sudo modprobe snd-hda-codec-cs35l41-i2c > modprobe: FATAL: Module snd-hda-codec-cs35l41-i2c not found in directory > /lib/modules/5.17.0-051700-generic > > while the other two give nothing. > > > (In reply to Cameron Berkenpas from comment #615) >> Your error message shows you're 5.13, which definitely doesn't have support. >> >> >> >> On 5/23/22 08:46, bugzilla-dae...@kernel.org wrote: >>> https://bugzilla.kernel.org/show_bug.cgi?id=208555 >>> >>> --- Comment #614 from she...@liang.at (she...@liang.at) --- >>> The first two modprobe commands returned >>> ` >>> modprobe: FATAL: Module snd-hda-codec-cs35l41-i2c not found in directory >>> /lib/modules/5.13.0-051300-generic >>> ` >>> The third one returns nothing. >>> >>> I tried reinstalling my nvidia driver too but even after purging all it >>> doesn't >>> seem to work :\ >>> >>> I tried following these instructions: >>> >> >> https://forums.developer.nvidia.com/t/nvidia-smi-has-failed-because-it-couldnt-communicate-with-the-nvidia-driver-make-sure-that-the-latest-nvidia-driver-is-installed-and-running/197141/6 >>> (In reply to Cameron Berkenpas from comment #612) I would try try 5.17. 5.18 only came out yesterday, and therefore doesn't even have any point releases so chances are reasonably high you'll run >> into bugs. Additionally, I don't have the ACHg6. It's possible you'll need to specify which modules to load. In the likely event that 5.17 doesn't work, perhaps someone can provide information on what's needed there. Possibly these steps will work: sudo modprobe snd-hda-codec-cs35l41-i2c sudo modeprobe snd_soc_cs35l41_i2c sudo modeprobe i2c-multi-instantiate (In reply to she...@liang.at from comment #609) > Thanks for the quick responses. I followed the instructions to install >> the > latest version. Is it supposed to work if I installed 5.18 too? It's not > working and it stopped recognising my external monitors too. > -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1958019 Title: [Lenovo Legion7 16ACHg6 82N6, Realtek ALC287, Speaker, Internal] No sound at all To manage notifications about this bug go to: https://bugs.launchpad.net/sound-2.6/+bug/1958019/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1958019]
It seems the path to endian.h may have changed from /usr/include/sys/endian.h to /usr/include/endian.h. In the failing file(s), try changing it from: #include To: #include On 5/24/22 05:37, bugzilla-dae...@kernel.org wrote: > https://bugzilla.kernel.org/show_bug.cgi?id=208555 > > --- Comment #617 from singo (hnsinan...@gmail.com) --- > Thanks for the quick reply and the pointer to the github tutorial. I've tried > going down this rabbit hole but face numerous error messages when following > the > guide. Unfortunately I failed at building the js qemu fork. Maybe it fails > because I'm on Ubuntu 22.04.? Anyways, I can't build it and thus can't even > continue with the actual hard part. > > Here's the output for the failed configuration of qemu: > https://pastebin.com/Lfq5vPz6 > > Maybe it has to do with the dependencies? When executing sudo apt install > build-essential && apt build-dep qemu-system-x86 it will says something along > the lines of "choosing qemu instead of quemu-system-x86". > > > (In reply to Cameron Berkenpas from comment #613) >> There's no patch for your laptop yet. >> >> Assuming your sound bar is initialized through verbs (I suspect it is), >> you'll need to find the verb sequence yourself: >> https://github.com/thiagotei/linux-realtek-alc287/tree/cameron >> >> Once there's a working verb sequence, a patch can be created. >> >> On 5/23/22 04:50, bugzilla-dae...@kernel.org wrote: >>> https://bugzilla.kernel.org/show_bug.cgi?id=208555 >>> >>> --- Comment #611 from singo (hnsinan...@gmail.com) --- >>> Hello everyone, >>> >>> I really appreciate this thread and all of the solutions that have been >>> produced for this issue. Thanks to everyone contributing, especially >> Cameron >>> Berkenpas who has been very helpful to a number of users and the main >> driving >>> force for fixes:) >>> >>> Now to my issue: I own a Lenovo Yoga 7i 15ITL05 82AC with the ALC287. >>> Currently >>> it runs Ubuntu 22.04. LTS with the included 5.15 Kernel. Before I have run >>> Pop_OS 21.04. and 22.04. With all these distros, the sound worked partially >>> but >>> never fully. The experience is the same as many other users here, where >> there >>> would only be sound coming out the from the downward firing speakers, but >> not >>> from the soundbar above the keyboard, which are the bass speakers judging >> by >>> the tinny sound I get now. The sound works beautifully in Windows, since >> the >>> lower end frequencies can be replayed. >>> >>> Quite honestly, I've lost the overview over this thread and am not so sure >>> which patch I should apply. I've tried manually update my Ubuntu 22.04. to >>> the >>> mainline 5.17 Kernel, which worked OS-wise but didn't change sound. My hope >>> was >>> that the sound patches have been included in that Kernel, but it seems >>> they're >>> only working for the Legion 7. >>> >>> Could someone point me to the right patch or verbs that have to be applied >>> for >>> my Lenovo model in order for the bass speakers to work? Maybe someone has >>> figured it out for this particular case? >>> >>> Much thanks in advance. >>> >>> Here's my alsa-info: >>> >>> http://alsa-project.org/db/?f=ad3990bed59a24417ea6429250275012611a0302 >>> -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1958019 Title: [Lenovo Legion7 16ACHg6 82N6, Realtek ALC287, Speaker, Internal] No sound at all To manage notifications about this bug go to: https://bugs.launchpad.net/sound-2.6/+bug/1958019/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1958019]
Thanks for the quick reply and the pointer to the github tutorial. I've tried going down this rabbit hole but face numerous error messages when following the guide. Unfortunately I failed at building the js qemu fork. Maybe it fails because I'm on Ubuntu 22.04.? Anyways, I can't build it and thus can't even continue with the actual hard part. Here's the output for the failed configuration of qemu: https://pastebin.com/Lfq5vPz6 Maybe it has to do with the dependencies? When executing sudo apt install build-essential && apt build-dep qemu-system-x86 it will says something along the lines of "choosing qemu instead of quemu- system-x86". (In reply to Cameron Berkenpas from comment #613) > There's no patch for your laptop yet. > > Assuming your sound bar is initialized through verbs (I suspect it is), > you'll need to find the verb sequence yourself: > https://github.com/thiagotei/linux-realtek-alc287/tree/cameron > > Once there's a working verb sequence, a patch can be created. > > On 5/23/22 04:50, bugzilla-dae...@kernel.org wrote: > > https://bugzilla.kernel.org/show_bug.cgi?id=208555 > > > > --- Comment #611 from singo (hnsinan...@gmail.com) --- > > Hello everyone, > > > > I really appreciate this thread and all of the solutions that have been > > produced for this issue. Thanks to everyone contributing, especially > Cameron > > Berkenpas who has been very helpful to a number of users and the main > driving > > force for fixes:) > > > > Now to my issue: I own a Lenovo Yoga 7i 15ITL05 82AC with the ALC287. > > Currently > > it runs Ubuntu 22.04. LTS with the included 5.15 Kernel. Before I have run > > Pop_OS 21.04. and 22.04. With all these distros, the sound worked partially > > but > > never fully. The experience is the same as many other users here, where > there > > would only be sound coming out the from the downward firing speakers, but > not > > from the soundbar above the keyboard, which are the bass speakers judging > by > > the tinny sound I get now. The sound works beautifully in Windows, since > the > > lower end frequencies can be replayed. > > > > Quite honestly, I've lost the overview over this thread and am not so sure > > which patch I should apply. I've tried manually update my Ubuntu 22.04. to > > the > > mainline 5.17 Kernel, which worked OS-wise but didn't change sound. My hope > > was > > that the sound patches have been included in that Kernel, but it seems > > they're > > only working for the Legion 7. > > > > Could someone point me to the right patch or verbs that have to be applied > > for > > my Lenovo model in order for the bass speakers to work? Maybe someone has > > figured it out for this particular case? > > > > Much thanks in advance. > > > > Here's my alsa-info: > > > > http://alsa-project.org/db/?f=ad3990bed59a24417ea6429250275012611a0302 > > -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1958019 Title: [Lenovo Legion7 16ACHg6 82N6, Realtek ALC287, Speaker, Internal] No sound at all To manage notifications about this bug go to: https://bugs.launchpad.net/sound-2.6/+bug/1958019/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1958019]
Oh, sorry I was in the wrong one version cuz I tried reverting to the older one when nvidia didn't work anymore. In kernel 5.17.0 the first command gives $ sudo modprobe snd-hda-codec-cs35l41-i2c modprobe: FATAL: Module snd-hda-codec-cs35l41-i2c not found in directory /lib/modules/5.17.0-051700-generic while the other two give nothing. (In reply to Cameron Berkenpas from comment #615) > Your error message shows you're 5.13, which definitely doesn't have support. > > > > On 5/23/22 08:46, bugzilla-dae...@kernel.org wrote: > > https://bugzilla.kernel.org/show_bug.cgi?id=208555 > > > > --- Comment #614 from she...@liang.at (she...@liang.at) --- > > The first two modprobe commands returned > > ` > > modprobe: FATAL: Module snd-hda-codec-cs35l41-i2c not found in directory > > /lib/modules/5.13.0-051300-generic > > ` > > The third one returns nothing. > > > > I tried reinstalling my nvidia driver too but even after purging all it > > doesn't > > seem to work :\ > > > > I tried following these instructions: > > > > > https://forums.developer.nvidia.com/t/nvidia-smi-has-failed-because-it-couldnt-communicate-with-the-nvidia-driver-make-sure-that-the-latest-nvidia-driver-is-installed-and-running/197141/6 > > > > (In reply to Cameron Berkenpas from comment #612) > >> I would try try 5.17. 5.18 only came out yesterday, and therefore doesn't > >> even have any point releases so chances are reasonably high you'll run > into > >> bugs. > >> > >> Additionally, I don't have the ACHg6. It's possible you'll need to specify > >> which modules to load. In the likely event that 5.17 doesn't work, perhaps > >> someone can provide information on what's needed there. > >> > >> Possibly these steps will work: > >> sudo modprobe snd-hda-codec-cs35l41-i2c > >> sudo modeprobe snd_soc_cs35l41_i2c > >> sudo modeprobe i2c-multi-instantiate > >> > >> (In reply to she...@liang.at from comment #609) > >>> Thanks for the quick responses. I followed the instructions to install > the > >>> latest version. Is it supposed to work if I installed 5.18 too? It's not > >>> working and it stopped recognising my external monitors too. > >>> -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1958019 Title: [Lenovo Legion7 16ACHg6 82N6, Realtek ALC287, Speaker, Internal] No sound at all To manage notifications about this bug go to: https://bugs.launchpad.net/sound-2.6/+bug/1958019/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 591713] Re: Illegal instruction in AES ciphers on WinChip C6
No, I can't check because I don't have the hardware anymore. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/591713 Title: Illegal instruction in AES ciphers on WinChip C6 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/591713/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 883459]
Still valid in akonadi 21.12.3 on Kubuntu 22.04. I think akonadi should automatically handle this problem. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/883459 Title: KMail duplicates emails To manage notifications about this bug go to: https://bugs.launchpad.net/kdepim/+bug/883459/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1784499] Re: AppArmor treats regular NFS file access as network op
@rikka0w0 are you willing to test a kernel patch for this issue? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1784499 Title: AppArmor treats regular NFS file access as network op To manage notifications about this bug go to: https://bugs.launchpad.net/apparmor/+bug/1784499/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1970270] Re: LibreOffice localization is not working out of the box
OK, so, after further research and testing, I learned the following: 1: It is not necessary to bind-mount all of /run - just /run/systemd/resolve does the trick. 2: There's no need to add "libreoffice-l10n-$LOCALE" to the packages.conf file - one of the packages already there must depend on it, since my latest solution still ends up with the bug solved even without modifying packages.conf. I am submitting a patch which solves this bug. The patch should be applied to /etc/calamares/modules/mount.conf. I have tested this and verified that it works on Lubuntu 22.04 Jammy. ** Patch added: "Bind-mounts /run/systemd/resolve from the live environment to the installed system during installation, allowing packages to be installed at OS install time." https://bugs.launchpad.net/ubuntu/+source/calamares-settings-ubuntu/+bug/1970270/+attachment/5592730/+files/libreOfficeLocalizationFix.diff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1970270 Title: LibreOffice localization is not working out of the box To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/calamares-settings-ubuntu/+bug/1970270/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1964084] Re: package gitsome (not installed) failed to install/upgrade: tentative de remplacement de « /usr/bin/gh », qui appartient aussi au paquet gh 2.4.0+dfsg1-1
** Changed in: gitsome (Debian) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1964084 Title: package gitsome (not installed) failed to install/upgrade: tentative de remplacement de « /usr/bin/gh », qui appartient aussi au paquet gh 2.4.0+dfsg1-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gh/+bug/1964084/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1975533] Re: No longer possible to use do-release-upgrade on Groovy
** Attachment added: "ubuntu-upgrader-DistUpgrade.png" https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1975533/+attachment/5592729/+files/ubuntu-upgrader-DistUpgrade.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1975533 Title: No longer possible to use do-release-upgrade on Groovy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1975533/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1975533] Re: No longer possible to use do-release-upgrade on Groovy
@Brian Murray, if you don't mind, I will post my notes here, as comments, so that it will be easier for someone else to follow my thought process on getting familiar with the problem, i.e., getting to better know how does `do-release-upgrade` and `DistUpgrade.cfg` work. It is very important to know all recent Ubuntu release names (https://wiki.ubuntu.com/Releases) in order to keep track with the analysis below. Ok, so I inspected the `DistUpgrade.cfg` file (https://git.launchpad.net/ubuntu/+source/ubuntu-release- upgrader/tree/data/DistUpgrade.cfg?h=ubuntu%2Fjammy#n109; stored in my file system at `/usr/share/ubuntu-release-upgrader/DistUpgrade.cfg`). It contains: ... 108 [Sources] 109 From=impish 110 To=jammy ... So it represents my most recent update. (I finally did groovy=>impish, and impish=>jammy.) Then, during the next update, it would look like: ... 108 [Sources] 109 From=jammy 110 To=kinetic ... (see: https://git.launchpad.net/ubuntu/+source/ubuntu-release- upgrader/tree/data/DistUpgrade.cfg#n110) I also found the `DistUpgrade.cfg.focal` (https://git.launchpad.net/ubuntu/+source/ubuntu-release- upgrader/tree/data/DistUpgrade.cfg.focal), and it contains: ... 108 [Sources] 109 From=focal 110 To=jammy ... Interestingly, the `DistUpgrade.cfg.focal` stored at my file system (at "~/.local/share/Trash/files/DistUpgrade.cfg.focal") contains: ... 108 [Sources] 109 From=focal 110 To=hirsute ... E.g., it was moved to the trash when the `ubuntu-hirsute` branch was in use on my system, see: https://git.launchpad.net/ubuntu/+source/ubuntu- release-upgrader/tree/data/DistUpgrade.cfg.focal?h=ubuntu%2Fhirsute#n109 . --- @Brian Murray, your other suggestion was to create `demoted.cfg.groovy`. Indeed, in the https://git.launchpad.net/ubuntu/+source/ubuntu-release- upgrader/tree/utils there is no `demoted.cfg.groovy`. Maybe part of the simplest solution (for the others to use) is, as you suggest, to create "demoted.cfg.groovy" which contains basically the same packages as "demoted.cfg.focal". --- Brian Murray wrote: > "For what its worth I tested an upgrade of a stock Ubuntu 20.10 system to Ubuntu 21.10 by copying DistUpgrade.cfg.focal to DistUpgrade.cfg.groovy and did not run into any issues" It worked because of this piece of code: lines 44 & 45 here: https://git.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/tree/DistUpgrade/DistUpgradeConfigParser.py#n44 ( ``` if os.path.exists(maincfg + "." + from_release): maincfg += "." + from_release ``` ) It is not a particularly neat solution, but it will work. In the ideal world, there would be a mechanism similar to this: https://git.launchpad.net/ubuntu/+source/ubuntu-release- upgrader/tree/DistUpgrade/DistUpgradeConfigParser.py#n39 (from_release = ...) in combination with the list of known releases (https://wiki.ubuntu.com/Releases) for the `DistUpgradeConfigParser.py` not to take fixed release names (from `DistUpgrade.cfg`/focal/groovy), but dynamically decide what is the release on the system, and what is the next available release, so that the `do-release-upgrade` would attempt to upgrade to the next available release. This way upgrades from the EOL systems would be supported, or as @Scott Carle wrote in the title of his bug report: it would be "easy peasy" (https://bugs.launchpad.net/ubuntu/+source/ubuntu-release- upgrader/+bug/1745754), now upgrading from EOL is not that simple. Getting back to the technicalities: the problem now seems to be that both groovy=>impish and hirsute=>impish should be supported. With release names being fixed on the branches, it is not possible (see: https://git.launchpad.net/ubuntu/+source/ubuntu-release- upgrader/tree/data/DistUpgrade.cfg?h=ubuntu%2Fimpish#n109). I am still missing one point: how did my groovy knew that impish was the latest supported system? That's it for the analysis. I will try to come up with some solution (in the code) that will support upgrading from at least groovy, if not from any EOL release, to the first available, still supported release (e.g., at the moment, groovy=>impish and hirsute=>impish). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1975533 Title: No longer possible to use do-release-upgrade on Groovy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1975533/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1973156] Re: Ubiquity window resizes in an odd way during Ubuntu installation when clicking "Install Now" after inputting disk encryption details
** Changed in: ubiquity (Ubuntu) Importance: Undecided => Medium -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1973156 Title: Ubiquity window resizes in an odd way during Ubuntu installation when clicking "Install Now" after inputting disk encryption details To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1973156/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1975362] Re: Subiquity 435 does not detect my disk sdb
** Also affects: subiquity Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1975362 Title: Subiquity 435 does not detect my disk sdb To manage notifications about this bug go to: https://bugs.launchpad.net/subiquity/+bug/1975362/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1888347] Re: blk-availability unmounts filesystems before applications have finished using them
** Tags added: rls-ff-incoming -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1888347 Title: blk-availability unmounts filesystems before applications have finished using them To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/1888347/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1974182] Re: Autopkgtest fails when HTTP proxy is used
This was sponsored but the Ubuntu Sponsors team was not unsubscribed. requests (2.27.1+dfsg-1ubuntu1) kinetic; urgency=medium * Fix autopkgtest when http_proxy, https_proxy or no_proxy variable is set (LP: #1974182) -- Olivier Gayot Thu, 19 May 2022 14:14:07 +0200 ** Changed in: requests (Ubuntu) Status: Confirmed => Fix Committed ** Changed in: requests (Ubuntu) Importance: Undecided => Medium -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1974182 Title: Autopkgtest fails when HTTP proxy is used To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/requests/+bug/1974182/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1975614] Re: audispd daemon missing in 22.04
I did not know the dispatcher is part of the main daemon now. My issue was about wrong ownership (non-root) of my plug-in, and I wrongly attributed it to the missing dispatcher. Thanks for the help, I guess the bug can be closed as not-a-bug. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1975614 Title: audispd daemon missing in 22.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/audit/+bug/1975614/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1973847] Re: Sometimes Firefox could not change mode from English to Japanese
Hi, Today, same problem occur. modify /usr/share/ibus/component/mozc.xml is not effective. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1973847 Title: Sometimes Firefox could not change mode from English to Japanese To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mozc/+bug/1973847/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1974063] Re: system load indicator does not show memory usage, ignoring preferences
I concur with Anthony Chubb's comments, which were indeed the original impetus that motivated me to begin tinkering with the indicator width in the first.place. I forgot to mention this in the wake of the more catastrophic problems that occurred when I tried to change the width. But had these symptoms not existed, I never would have bothered messing with the width. My ideal state would be to see the "Mem: 6.2 GB" text that I used to see, and not flickering. As to my Question 2 above, I did discover that this setting was maintained in dconf under the key of /de/mh21/indicator-multiload/, as indicated in my link above. Navigating there, I was able to change the width back to 40 and reinstall the indicator without breaking the system. However, I only see the graphical display, which is better than nothing, but not ideal, and it does flicker. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1974063 Title: system load indicator does not show memory usage, ignoring preferences To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-multiload/+bug/1974063/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
