[Bug 2072151] [NEW] ubuntu-release-upgrader reboots machine during mantic > noble upgrade
Public bug reported: During an upgrade of Edubuntu from mantic to noble on two separate machines, one after the other, both machines rebooted at what appears to have been the exact same point in the upgrade. Upon reboot, I was able to get both machines back up to speed, but only after booting back into the Mantic kernel (6.5) since the `update- initramfs` had not yet been run on the Noble (6.8) kernel, but if solely running the 6.8 kernel, this could potentially leave the machine in an unbootable state. I'll leave a comment with the terminal output after the reboot from the `dpkg --configure -a` as to not fill this description up too much. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: ubuntu-release-upgrader-core 1:24.04.19 ProcVersionSignature: Ubuntu 6.8.0-36.36-generic 6.8.4 Uname: Linux 6.8.0-36-generic x86_64 ApportVersion: 2.28.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: pass CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Thu Jul 4 15:52:03 2024 InstallationDate: Installed on 2023-11-09 (239 days ago) InstallationMedia: Edubuntu 23.10 "Mantic Minotaur" - Release amd64 (20231010) PackageArchitecture: all ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= SourcePackage: ubuntu-release-upgrader Symptom: ubuntu-release-upgrader UpgradeStatus: Upgraded to noble on 2024-07-04 (0 days ago) VarLogDistupgradeTermlog: ** Affects: ubuntu-release-upgrader (Ubuntu) Importance: High Assignee: Nick Rosbrook (enr0n) Status: New ** Tags: amd64 apport-bug dist-upgrade noble wayland-session -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2072151 Title: ubuntu-release-upgrader reboots machine during mantic > noble upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/2072151/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2072151] Re: ubuntu-release-upgrader reboots machine during mantic > noble upgrade
sudo dpkg --configure -a
Setting up cups (2.4.7-1.2ubuntu7.2) ...
Updating PPD files for cups ...
Updating PPD files for hpcups ...
Updating PPD files for postscript-hp ...
Updating PPD files for ptouch ...
Updating PPD files for splix ...
Setting up libblockdev-crypto3:amd64 (3.1.1-1) ...
Setting up python3-pyqt6 (6.6.1-2build4) ...
Setting up libwebkitgtk-6.0-4:amd64 (2.44.2-0ubuntu0.24.04.2) ...
Setting up network-manager-gnome (1.34.0-1ubuntu3) ...
Installing new version of config file /etc/xdg/autostart/nm-applet.desktop ...
Setting up yaru-theme-gtk (24.04.2-0ubuntu1) ...
Setting up qgnomeplatform-qt5:amd64 (0.9.2-1build6) ...
Setting up totem-plugins (43.0-2ubuntu4) ...
Setting up pyqt6-dev-tools (6.6.1-2build4) ...
Setting up colord (1.4.7-1build2) ...
Setting up gnome-weather (46.0-1) ...
Setting up libanalitzawidgets8:amd64 (4:23.08.5-0ubuntu4) ...
Setting up libqt6webenginewidgets6:amd64 (6.4.2-final+dfsg-12ubuntu9) ...
Setting up qml-module-qtquick-controls:amd64 (5.15.13-1) ...
Setting up libyelp0:amd64 (42.2-1build2) ...
Setting up seahorse (43.0-3build2) ...
Setting up libkf5xmlgui5:amd64 (5.115.0-0ubuntu5) ...
Setting up libkf5textwidgets5:amd64 (5.115.0-0ubuntu4) ...
Setting up libkf5iconthemes-bin (5.115.0-0ubuntu6) ...
Setting up libqt6webenginequick6:amd64 (6.4.2-final+dfsg-12ubuntu9) ...
Setting up kgeography (4:23.08.5-0ubuntu4) ...
Setting up libkf5kiogui5:amd64 (5.115.0-0ubuntu6) ...
Setting up python3-pyqt6.qtwebchannel (6.6.1-2build4) ...
Setting up gcompris-qt (4.0-1build3) ...
Setting up libedataserverui-1.2-4t64:amd64 (3.52.0-1build3) ...
Setting up printer-driver-foo2zjs (20200505dfsg0-2ubuntu6) ...
Setting up polkit-kde-agent-1 (4:5.27.11-0ubuntu3) ...
Setting up python3-pyqt6.qtsvg (6.6.1-2build4) ...
Setting up libkf5wallet-bin (5.115.0-0ubuntu3) ...
Setting up edubuntu-artwork (24.04.26.1) ...
Setting up printer-driver-splix (2.0.0+svn315-7fakesync1ubuntu1) ...
Setting up phonon4qt5:amd64 (4:4.12.0-3.1build3) ...
Setting up bluez-cups (5.72-0ubuntu5) ...
Setting up python3-pyqt5.qtwebchannel (5.15.10+dfsg-1build6) ...
Setting up gnome-initial-setup (46.0-1ubuntu6) ...
Setting up duplicity (2.1.4-3ubuntu2) ...
Setting up gir1.2-webkit-6.0:amd64 (2.44.2-0ubuntu0.24.04.2) ...
Setting up python3-pyqt6.qtqml (6.6.1-2build4) ...
Setting up blinken (4:23.08.5-0ubuntu4) ...
Setting up libkf5bookmarks5:amd64 (5.115.0-0ubuntu5) ...
Setting up printer-driver-hpcups (3.23.12+dfsg0-0ubuntu5) ...
Setting up python3-pyqt5.qtwebengine (5.15.6-1build2) ...
Setting up qml-module-org-kde-analitza:amd64 (4:23.08.5-0ubuntu4) ...
Setting up libedataserverui4-1.0-0t64:amd64 (3.52.0-1build3) ...
Setting up libmarblewidget-qt5-28:amd64 (4:23.08.5-0ubuntu3) ...
Setting up hplip (3.23.12+dfsg0-0ubuntu5) ...
Creating/updating hplip user account...
Setting up python3-pyqt6.qtquick (6.6.1-2build4) ...
Setting up udisks2 (2.10.1-6build1) ...
Setting up gnome-control-center (1:46.0.1-1ubuntu7) ...
Setting up evolution-data-server (3.52.0-1build3) ...
Installing new version of config file
/etc/xdg/autostart/org.gnome.Evolution-alarm-notify.desktop ...
Setting up gnome-calendar (46.0-1build1) ...
Setting up libkf5kiowidgets5:amd64 (5.115.0-0ubuntu6) ...
Setting up kbruch (4:23.08.5-0ubuntu4) ...
Setting up libqapt3-runtime (3.0.5-2build3) ...
Setting up yelp (42.2-1build2) ...
Setting up gvfs-daemons (1.54.0-1ubuntu2) ...
Setting up libkf5kiofilewidgets5:amd64 (5.115.0-0ubuntu6) ...
Setting up endeavour (43.0-1build3) ...
Setting up bijiben (40.1-6build4) ...
Setting up deja-dup (45.2-1build2) ...
Setting up marble-qt (4:23.08.5-0ubuntu3) ...
Setting up marble-plugins:amd64 (4:23.08.5-0ubuntu3) ...
Setting up python3-pyqt6.qtwebengine (6.6.0-1build2) ...
Setting up kio (5.115.0-0ubuntu6) ...
Setting up gnome-disk-utility (46.0-1ubuntu3) ...
Setting up libkeduvocdocument5abi1:amd64 (4:23.08.5-0ubuntu3) ...
Setting up libfolks-eds26:amd64 (0.15.9-1ubuntu5) ...
Setting up qapt-batch (3.0.5-2build3) ...
Setting up ubuntu-docs (24.04.2) ...
Setting up libkf5parts5:amd64 (5.115.0-0ubuntu5) ...
Setting up gvfs:amd64 (1.54.0-1ubuntu2) ...
Setting up kactivitymanagerd (5.27.11-0ubuntu3) ...
Setting up libkf5plasma5:amd64 (5.115.0-0ubuntu4) ...
Setting up gnome-user-docs (46.0-1ubuntu1) ...
Setting up gnome-contacts (46.0-1build1) ...
Setting up libcantorlibs28 (4:23.08.5-0ubuntu4) ...
Setting up edubuntu-installer (0.6) ...
Setting up libkf5declarative5:amd64 (5.115.0-0ubuntu5) ...
Setting up gvfs-backends (1.54.0-1ubuntu2) ...
Setting up libkf5quickaddons5:amd64 (5.115.0-0ubuntu5) ...
Setting up qml-module-org-kde-kconfig:amd64 (5.115.0-0ubuntu5) ...
Setting up libkf5plasmaquick5:amd64 (5.115.0-0ubuntu4) ...
Setting up libkf5newstuffcore5:amd64 (5.115.0-0ubuntu5) ...
Setting up calibre (7.6.0+ds-1build1) ...
/usr/lib/calibre/templite/__init__.py:33: SyntaxWarning: invalid escape
sequence '\['
auto_emit = re.compile('(^[\'\"])|(^[a-zA-Z0-9_\[\]\'\"]+$)')
Setting up keditbookmarks (23.08.5-0ubuntu4) ...
Setting
[Bug 2070151] Re: package linux-image-6.8.0-35-lowlatency 6.8.0-35.35.1 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1
To be honest, ubuntustudio-installer wasn't developed with raspberry pi in mind, so it's not really supported even though the package is available. I'm the author of the current iteration; the previous iteration was also not developed with any other architectures other than amd64 in mind. In 24.10, the linux-lowlatency package won't even be a selectable option in ubuntustudio-installer as we're switching to the generic kernel. I'm assuming you selected this which is precisely what caused the crash. Therefore, since it's not developed for 24.04 and linux-lowlatency isn't really a thing on raspberry pi, I'm marking this as Won't Fix. ** Changed in: initramfs-tools (Ubuntu) Status: New => Invalid ** Changed in: ubuntustudio-installer (Ubuntu) Status: Invalid => Won't Fix -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2070151 Title: package linux-image-6.8.0-35-lowlatency 6.8.0-35.35.1 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/2070151/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2070151] Re: package linux-image-6.8.0-35-lowlatency 6.8.0-35.35.1 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1
To be honest, ubuntustudio-installer wasn't developed with raspberry pi in mind, so it's not really supported even though the package is available. I'm the author of the current iteration; the previous iteration was also not developed with any other architectures other than amd64 in mind. In 24.10, the linux-lowlatency package won't even be a selectable option in ubuntustudio-installer as we're switching to the generic kernel. I'm assuming you selected this which is precisely what caused the crash. Therefore, since it's not developed for 24.04 and linux-lowlatency isn't really a thing on raspberry pi, I'm marking this as Won't Fix. ** Changed in: ubuntustudio-installer (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2070151 Title: package linux-image-6.8.0-35-lowlatency 6.8.0-35.35.1 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/2070151/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2061329] Re: [SRU] displaycal 3.9.11-2 needs patch to work with Python 3.12
$ apt-cache policy displaycal displaycal: Installed: 3.9.11-2ubuntu0.24.04.1 Candidate: 3.9.11-2ubuntu0.24.04.1 Version table: *** 3.9.11-2ubuntu0.24.04.1 100 100 http://us.archive.ubuntu.com/ubuntu noble-proposed/universe amd64 Packages 100 /var/lib/dpkg/status 3.9.11-2 500 500 http://us.archive.ubuntu.com/ubuntu noble/universe amd64 Packages * Ran displaycal * No issues, application ran normally and as expected. Didn't crash on close, either. :) ** Tags removed: verification-needed verification-needed-noble ** Tags added: verification-done verification-done-noble -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2061329 Title: [SRU] displaycal 3.9.11-2 needs patch to work with Python 3.12 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/displaycal-py3/+bug/2061329/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2061329] Re: [SRU] displaycal 3.9.11-2 needs patch to work with Python 3.12
> 1) Fix the development release to not be brittle in this way, so it won't unnecessarily break if Python is updated in a way that doesn't break its API in a way that matters to this package. Done. It no longer tests for python versions at all, but still needs to grab the python version for internal functions. > 2) Fix the SRU upload to also not be brittle in this way, so it won't unnecessarily break against a newer version of Python were we to add it to 24.04 during its lifetime, as we did for 22.04. For example, you could the patch you're adding so it works for all future Python versions, not just 3.12. Done in the same fashion. > 3) This also needs some further explanation, please. Is this related to "since it could crash upon closure", or something else? What's the status of this? Are you proposing this SRU on the basis that it's definitely better than the current state? All of this should be documented, please. The "since it could crash upon closure" is related to WxPython and not related to this bug at all. As stated, this has not occurred in my testing of the actual binary in my PPA at https://launchpad.net/~eeickmeyer/+archive/ubuntu/displaycaltest. > > > ++@pytest.mark.skip(reason="Test segfaults with python 3.12 - further > > > investigation required.") This is related to an internal test not during build, but during runtime upon launch. Upstream has not yet figured out why it segfaults at this point (upstream is now maintaining abandoned code and is not the original author), so they're working diligently on it. However, as stated in the description, I argue that having a functioning application is better than a flaky test that crashes the entire application. As far as I can see, the application functions normally without the test. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2061329 Title: [SRU] displaycal 3.9.11-2 needs patch to work with Python 3.12 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/displaycal-py3/+bug/2061329/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2061329] Re: [SRU] displaycal 3.9.11-2 needs patch to work with Python 3.12
** Description changed: [Impact] DisplayCAL, when released, was only compatible with Python 3.8-3.11. However, all it needed was WxWidgets 4.1.1 and a few patches to make it work with Python 3.12. Without, it would simply fail. Namely, it needed to be patched to remove the Python version check upon launch. [Test Case] * Install displaycal * Run displaycal Expected: Run normally Result: Traceback (most recent call last): File "/usr/bin/displaycal", line 4, in from DisplayCAL.main import main File "/usr/lib/python3/dist-packages/DisplayCAL/main.py", line 27, in raise RuntimeError( RuntimeError: Need Python version >= 3.8 <= 3.11, got 3.12.2 [What could go wrong] The DisplayCAL developers do not yet support Python 3.12 until the release of WxWidgets 4.2.0 since it could crash upon closure. I (Erich Eickmeyer) have not experienced this in my testing, however, it is plausible. Additionally, the patches that were used to make this work were developed after the release of DisplayCAL 3.9.12, but still applied cleanly to 3.9.11 and made it function correctly. To be clear, the issue with WxWidgets is a separate bug and outside the scope of this bug. [Other Information] Currently the tests have to be skipped otherwise they segfault with - Python 3.12 and the entire source FTBFS, hence the inclusion of the - patch `05_skip-test-wioth-python-3.12.patch`. + Python 3.12 and the entire application fails to run, hence the inclusion + of the patch `05_skip-test-wioth-python-3.12.patch`. I would, however, + argue that the application running trumps its internal tests + segfaulting. Original bug report: I have upgraded to the noble beta today, and displaycal fails to start. The package dependencies request python 3.12, but the actual software needs 3.11 (or older). ``` $ apt show displaycal | grep Depends WARNING: apt does not have a stable CLI interface. Use with caution in scripts. Depends: libc6 (>= 2.34), libx11-6, libxinerama1 (>= 2:1.1.4), libxrandr2 (>= 2:1.2.0), libxxf86vm1, python3 (<< 3.13), python3 (>= 3.12~), python3-build, python3-certifi, python3-dbus, python3-distro, python3-numpy, python3-pil, python3-pychromecast, python3-send2trash, python3-wxgtk4.0, python3-zeroconf, python3:any, dbus-x11, argyll, libjs-jquery, python3-gi, libsdl2-mixer-2.0-0 $ displaycal --help Traceback (most recent call last): File "/usr/bin/displaycal", line 4, in from DisplayCAL.main import main File "/usr/lib/python3/dist-packages/DisplayCAL/main.py", line 27, in raise RuntimeError( RuntimeError: Need Python version >= 3.8 <= 3.11, got 3.12.2 ``` ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: displaycal 3.9.11-2 ProcVersionSignature: Ubuntu 6.8.0-22.22-generic 6.8.1 Uname: Linux 6.8.0-22-generic x86_64 NonfreeKernelModules: zfs ApportVersion: 2.28.0-0ubuntu1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sun Apr 14 15:16:10 2024 ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/zsh TERM=xterm-256color XDG_RUNTIME_DIR= SourcePackage: displaycal-py3 UpgradeStatus: Upgraded to noble on 2024-04-14 (0 days ago) mtime.conffile..etc.xdg.autostart.z-displaycal-apply-profiles.desktop: 2023-10-22T21:28:16.420795 ** Description changed: [Impact] DisplayCAL, when released, was only compatible with Python 3.8-3.11. However, all it needed was WxWidgets 4.1.1 and a few patches to make it work with Python 3.12. Without, it would simply fail. Namely, it needed to be patched to remove the Python version check upon launch. [Test Case] * Install displaycal * Run displaycal Expected: Run normally Result: Traceback (most recent call last): File "/usr/bin/displaycal", line 4, in from DisplayCAL.main import main File "/usr/lib/python3/dist-packages/DisplayCAL/main.py", line 27, in raise RuntimeError( RuntimeError: Need Python version >= 3.8 <= 3.11, got 3.12.2 [What could go wrong] The DisplayCAL developers do not yet support Python 3.12 until the release of WxWidgets 4.2.0 since it could crash upon closure. I (Erich Eickmeyer) have not experienced this in my testing, however, it is plausible. Additionally, the patches that were used to make this work were developed after the release of DisplayCAL 3.9.12, but still applied cleanly to 3.9.11 and made it function correctly. To be clear, the issue with WxWidgets is a separate bug and outside the scope of this bug. [Other Information] Currently the tests have to be skipped otherwise they segfault with Python 3.12 and the entire application fails to run, hence the inclusion of the patch `05_skip-test-wioth-python-3.12.patch`
[Bug 2061329] Re: [SRU] displaycal 3.9.11-2 needs patch to work with Python 3.12
** Description changed: [Impact] DisplayCAL, when released, was only compatible with Python 3.8-3.11. However, all it needed was WxWidgets 4.1.1 and a few patches to make it - work with Python 3.12. Without, it would simply fail. - + work with Python 3.12. Without, it would simply fail. Namely, it needed + to be patched to remove the Python version check upon launch. [Test Case] - * Install displaycal - * Run displaycal + * Install displaycal + * Run displaycal Expected: Run normally Result: Traceback (most recent call last): File "/usr/bin/displaycal", line 4, in from DisplayCAL.main import main File "/usr/lib/python3/dist-packages/DisplayCAL/main.py", line 27, in raise RuntimeError( RuntimeError: Need Python version >= 3.8 <= 3.11, got 3.12.2 - [What could go wrong] The DisplayCAL developers do not yet support Python 3.12 until the release of WxWidgets 4.2.0 since it could crash upon closure. I (Erich Eickmeyer) have not experienced this in my testing, however, it is plausible. Additionally, the patches that were used to make this work were developed after the release of DisplayCAL 3.9.12, but still applied cleanly to 3.9.11 and made it function correctly. + To be clear, the issue with WxWidgets is a separate bug and outside the + scope of this bug. [Other Information] + + Currently the tests have to be skipped otherwise they segfault with + Python 3.12 and the entire source FTBFS, hence the inclusion of the + patch `05_skip-test-wioth-python-3.12.patch`. Original bug report: I have upgraded to the noble beta today, and displaycal fails to start. The package dependencies request python 3.12, but the actual software needs 3.11 (or older). ``` $ apt show displaycal | grep Depends WARNING: apt does not have a stable CLI interface. Use with caution in scripts. Depends: libc6 (>= 2.34), libx11-6, libxinerama1 (>= 2:1.1.4), libxrandr2 (>= 2:1.2.0), libxxf86vm1, python3 (<< 3.13), python3 (>= 3.12~), python3-build, python3-certifi, python3-dbus, python3-distro, python3-numpy, python3-pil, python3-pychromecast, python3-send2trash, python3-wxgtk4.0, python3-zeroconf, python3:any, dbus-x11, argyll, libjs-jquery, python3-gi, libsdl2-mixer-2.0-0 $ displaycal --help Traceback (most recent call last): File "/usr/bin/displaycal", line 4, in from DisplayCAL.main import main File "/usr/lib/python3/dist-packages/DisplayCAL/main.py", line 27, in raise RuntimeError( RuntimeError: Need Python version >= 3.8 <= 3.11, got 3.12.2 ``` ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: displaycal 3.9.11-2 ProcVersionSignature: Ubuntu 6.8.0-22.22-generic 6.8.1 Uname: Linux 6.8.0-22-generic x86_64 NonfreeKernelModules: zfs ApportVersion: 2.28.0-0ubuntu1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sun Apr 14 15:16:10 2024 ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/zsh TERM=xterm-256color XDG_RUNTIME_DIR= SourcePackage: displaycal-py3 UpgradeStatus: Upgraded to noble on 2024-04-14 (0 days ago) mtime.conffile..etc.xdg.autostart.z-displaycal-apply-profiles.desktop: 2023-10-22T21:28:16.420795 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2061329 Title: [SRU] displaycal 3.9.11-2 needs patch to work with Python 3.12 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/displaycal-py3/+bug/2061329/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2069775] [NEW] [BPO] lsp-plugins/1.2.16-1 from oracular to noble
Public bug reported: [Impact] This is an update of an existing backport in noble-backports (lsp- plugins/1.2.15-2~bpo24.04.1) (LP: #2065359) [Scope] * Backport lsp-plugins 1.2.16-1 from ocular (dev series) * Backport to 24.04 (Noble Numbat) [Other Information) Reverse dependencies: * NONE Reverse recommends: * EasyEffects: EasyEffects functionality is merely enhanced by lsp- plugins and no adverse effects by a newer version are foreseen. Furthermore, no changes to the internal MIDI Input/Output of the plugins, on which EasyEffects uses them, have changed, therefore justifying no impact. Maintenance: * Further backports of lsp-plugins will be provided by myself to noble with newer versions in the devel branch as they come. Successfully built in https://launchpad.net/~ubuntustudio- ppa/+archive/ubuntu/backports-staging ** Affects: lsp-plugins (Ubuntu) Importance: Undecided Status: Invalid ** Affects: lsp-plugins (Ubuntu Noble) Importance: Undecided Assignee: Erich Eickmeyer (eeickmeyer) Status: In Progress ** Also affects: lsp-plugins (Ubuntu Noble) Importance: Undecided Status: New ** Changed in: lsp-plugins (Ubuntu) Status: New => Invalid ** Changed in: lsp-plugins (Ubuntu Noble) Status: New => In Progress ** Changed in: lsp-plugins (Ubuntu Noble) Assignee: (unassigned) => Erich Eickmeyer (eeickmeyer) ** Summary changed: - [BPO] lsp/plugins/1.2.16-2 from oracular to noble + [BPO] lsp/plugins/1.2.16-1 from oracular to noble ** Summary changed: - [BPO] lsp/plugins/1.2.16-1 from oracular to noble + [BPO] lsp-plugins/1.2.16-1 from oracular to noble -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2069775 Title: [BPO] lsp-plugins/1.2.16-1 from oracular to noble To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lsp-plugins/+bug/2069775/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2067510] Re: [SRU] enable ubuntustudio-fix-firstrun.service on initial login
$ apt-cache policy ubuntustudio-installer ubuntustudio-installer: Installed: 1.18.4 Candidate: 1.18.4 Version table: *** 1.18.4 100 100 http://us.archive.ubuntu.com/ubuntu noble-proposed/universe amd64 Packages 100 http://us.archive.ubuntu.com/ubuntu noble-proposed/universe i386 Packages 1.18.2 500 500 http://us.archive.ubuntu.com/ubuntu noble-updates/universe amd64 Packages 500 http://us.archive.ubuntu.com/ubuntu noble-updates/universe i386 Packages 1.18 500 500 http://us.archive.ubuntu.com/ubuntu noble/universe amd64 Packages 500 http://us.archive.ubuntu.com/ubuntu noble/universe i386 Packages * added new user * signed-in as new user * User was prompted to restart for proper configs to take place. ** Tags removed: verification-needed verification-needed-noble ** Tags added: verification-done verification-done-noble -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2067510 Title: [SRU] enable ubuntustudio-fix-firstrun.service on initial login To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntustudio-installer/+bug/2067510/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2067512] Re: [SRU] fix for user first run should not affect live session user
$ apt-cache policy ubuntustudio-installer ubuntustudio-installer: Installed: 1.18.4 Candidate: 1.18.4 Version table: *** 1.18.4 100 100 http://us.archive.ubuntu.com/ubuntu noble-proposed/universe amd64 Packages 100 http://us.archive.ubuntu.com/ubuntu noble-proposed/universe i386 Packages 1.18.2 500 500 http://us.archive.ubuntu.com/ubuntu noble-updates/universe amd64 Packages 500 http://us.archive.ubuntu.com/ubuntu noble-updates/universe i386 Packages 1.18 500 500 http://us.archive.ubuntu.com/ubuntu noble/universe amd64 Packages 500 http://us.archive.ubuntu.com/ubuntu noble/universe i386 Packages * Upgraded fully * Installed from noble-proposed * Restarted sddm to restart live session * ubuntustudio-audio-config did *not* pop-up at all. ** Tags removed: verification-needed verification-needed-noble ** Tags added: verification-done verification-done-noble -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2067512 Title: [SRU] fix for user first run should not affect live session user To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntustudio-installer/+bug/2067512/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2066026] Re: [SRU] Klayout 0.28.15 segmentation fault on startup
$ apt-cache policy klayout klayout: Installed: 0.28.16-0ubuntu0.24.04.1 Candidate: 0.28.16-0ubuntu0.24.04.1 Version table: *** 0.28.16-0ubuntu0.24.04.1 100 100 http://us.archive.ubuntu.com/ubuntu noble-proposed/universe amd64 Packages 100 /var/lib/dpkg/status 0.28.15-1build5 500 500 http://us.archive.ubuntu.com/ubuntu noble/universe amd64 Packages * Started klayout Application runs with no apparent issues. ** Tags removed: verification-needed verification-needed-noble ** Tags added: verification-done verification-done-noble -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2066026 Title: [SRU] Klayout 0.28.15 segmentation fault on startup To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/klayout/+bug/2066026/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2067512] Re: [SRU] fix for user first run should not affect live session user
** Changed in: ubuntustudio-installer (Ubuntu Oracular) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2067512 Title: [SRU] fix for user first run should not affect live session user To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntustudio-installer/+bug/2067512/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2067512] Re: [SRU] fix for user first run should not affect live session user
** Changed in: ubuntustudio-installer (Ubuntu Oracular) Status: Fix Released => 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/2067512 Title: [SRU] fix for user first run should not affect live session user To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntustudio-installer/+bug/2067512/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2067510] Re: [SRU] enable ubuntustudio-fix-firstrun.service on initial login
$ apt-cache policy ubuntustudio-installer ubuntustudio-installer: Installed: 1.18.3 Candidate: 1.18.3 Version table: *** 1.18.3 100 100 http://us.archive.ubuntu.com/ubuntu noble-proposed/universe amd64 Packages 100 http://us.archive.ubuntu.com/ubuntu noble-proposed/universe i386 Packages 100 /var/lib/dpkg/status 1.18.2 500 500 http://us.archive.ubuntu.com/ubuntu noble-updates/universe amd64 Packages 500 http://us.archive.ubuntu.com/ubuntu noble-updates/universe i386 Packages 1.18 500 500 http://us.archive.ubuntu.com/ubuntu noble/universe amd64 Packages 500 http://us.archive.ubuntu.com/ubuntu noble/universe i386 Packages At first, this verification was unsuccessful as I had forgotten that I was experimenting with diverting /usr/bin/adduser to /usr/bin/adduser- actual and replacing it with the following script: #!/bin/sh /usr/sbin/adduser-actual --ingroup audio $@ Upon investigation, I realized this created the user with the audio group which made it so that the actual mechanism for ubuntustudio- installer would not be necessary if this script and diversion was added to ubuntustudio-default-settings as described above. This was also per a conversation with Steve Langasek on IRC. However, after removing this and putting /usr/sbin/adduser back where it belongs, I redid the test: * added new user * signed-in as new user * User was prompted to restart for proper configs to take place. ** Tags removed: verification-needed verification-needed-noble ** Tags added: verification-done verification-done-noble -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2067510 Title: [SRU] enable ubuntustudio-fix-firstrun.service on initial login To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntustudio-installer/+bug/2067510/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2067512] Re: [SRU] fix for user first run should not affect live session user
Unfortunately, verification has failed in this case as during testing,
using ubuntustudio-installer/1.18.3 from noble-proposed, it would pop-up
prior to loading the system installer (ubuntu-desktop-bootstrap) and
wouldn't start the installer until after it was closed.
This simply will require the User systemd service file to be changed to
the following:
- ExecStart=sh -c 'if ! [ -e ${HOME}/.config/ubuntustudio-audio-firstrun ];
then /usr/bin/ubuntustudio-audio-config; fi'
+ ExecStart=sh -c 'if ! [ -e ${HOME}/.config/ubuntustudio-audio-firstrun ] &&
if ! [ "$(id -nu)" = "ubuntu-studio" ]; then
/usr/bin/ubuntustudio-audio-config; fi'
This will prevent it from running in the Live Session user on startup
completely.
** Tags removed: verification-needed verification-needed-noble
** Tags added: verification-failed verification-failed-noble
** Changed in: ubuntustudio-installer (Ubuntu Noble)
Status: Fix Committed => 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/2067512
Title:
[SRU] fix for user first run should not affect live session user
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntustudio-installer/+bug/2067512/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2067338] Re: [SRU] Long SysEx messages are skipped by Midi-Bridge
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2067338 Title: [SRU] Long SysEx messages are skipped by Midi-Bridge To manage notifications about this bug go to: https://bugs.launchpad.net/pipewire/+bug/2067338/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2067338] Re: [SRU] Long SysEx messages are skipped by Midi-Bridge
Now with the version in noble-proposed: $ apt-cache policy pipewire pipewire: Installed: 1.0.5-1ubuntu1 Candidate: 1.0.5-1ubuntu1 Version table: *** 1.0.5-1ubuntu1 100 100 http://us.archive.ubuntu.com/ubuntu noble-proposed/main amd64 Packages 100 /var/lib/dpkg/status 1.0.5-1 500 500 http://us.archive.ubuntu.com/ubuntu noble/main amd64 Packages * Connected Behringer X-Touch to computer via USB * Started Ardour * Selected X-Touch as Mackie controller Result: Using the project file I had, the controller immediately sprung to life and acted as expected (see attached picture). Faders moved to proper position, scribble strip populated with channel information, mute LEDs lit, timecode appeared, and other information. Ardour responded to controls. ** Attachment added: "20240607_093441.jpg" https://bugs.launchpad.net/ubuntu/+source/pipewire/+bug/2067338/+attachment/5787259/+files/20240607_093441.jpg ** Tags removed: verification-needed verification-needed-noble ** Tags added: verification-done verification-done-noble -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2067338 Title: [SRU] Long SysEx messages are skipped by Midi-Bridge To manage notifications about this bug go to: https://bugs.launchpad.net/pipewire/+bug/2067338/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2067338] Re: [SRU] Long SysEx messages are skipped by Midi-Bridge
I'm going to comment twice to show exactly what we're talking about here. First, here's without the version in noble-proposed: $ apt-cache policy pipewire pipewire: Installed: 1.0.5-1 Candidate: 1.0.5-1 Version table: *** 1.0.5-1 500 500 http://us.archive.ubuntu.com/ubuntu noble/main amd64 Packages 100 /var/lib/dpkg/status * Connected Behringer X-Touch to computer via USB * Started Ardour * Selected X-Touch as the Mackie controller Result: No response from X-Touch other than population of colors in scribble strip (see attached picture) Explanation: The "Scribble Strip" is where engineers used to literally "scribble" the channel assignments on a mixer to what the channel assignment was for and would sometimes color code. Ardour is capable of not only populating the LCD scribble strip, but also assigning color code. Unfortunately, due to the long SysEx messages getting skipped, only the short SysEx messages consisting of the color assignments are getting through. We're also supposed to see the faders automatically move and a timecode in the upper-right-hand corner for the position of the "tape head" of the audio workstation, telling us where we are in the recording. That also is not populating. Moreover, any control changes we make are not being sent back to Ardour properly. ** Attachment added: "20240607_090630.jpg" https://bugs.launchpad.net/ubuntu/+source/pipewire/+bug/2067338/+attachment/5787237/+files/20240607_090630.jpg -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2067338 Title: [SRU] Long SysEx messages are skipped by Midi-Bridge To manage notifications about this bug go to: https://bugs.launchpad.net/pipewire/+bug/2067338/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2067338] Re: [SRU] Long SysEx messages are skipped by Midi-Bridge
Unsubscribing sponsors, Simon Quigley handled new upload. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2067338 Title: [SRU] Long SysEx messages are skipped by Midi-Bridge To manage notifications about this bug go to: https://bugs.launchpad.net/pipewire/+bug/2067338/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2066026] Re: [SRU] Klayout 0.28.15 segmentation fault on startup
I have sponsored the fix for this package by uploading this package to noble-proposed UNAPPROVED awaiting approval from the Ubuntu Stable Release Updates team. Subsequently, I have unsubscribed the Ubuntu Sponsors Team as the upload has now been sponsored and awaits SRU approval. For more information about this process, see https://wiki.ubuntu.com/StableReleaseUpdates -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2066026 Title: [SRU] Klayout 0.28.15 segmentation fault on startup To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/klayout/+bug/2066026/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2067338] Re: [SRU] Long SysEx messages are skipped by Midi-Bridge
** Patch removed: "pipewire_1.0.5-1ubuntu1.debdiff" https://bugs.launchpad.net/ubuntu/+source/pipewire/+bug/2067338/+attachment/5783484/+files/pipewire_1.0.5-1ubuntu1.debdiff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2067338 Title: [SRU] Long SysEx messages are skipped by Midi-Bridge To manage notifications about this bug go to: https://bugs.launchpad.net/pipewire/+bug/2067338/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2067338] Re: [SRU] Long SysEx messages are skipped by Midi-Bridge
Working with Andreas Hasenack, we determined that the larger of the two included patches was actually not included in the code of 1.0.7 and after testing I found out it was not needed. For that reason, I'm uploading a new .debdiff and this will need another upload. ** Patch added: "pipewire_1.0.5-1ubuntu1.debdiff" https://bugs.launchpad.net/ubuntu/+source/pipewire/+bug/2067338/+attachment/5786973/+files/pipewire_1.0.5-1ubuntu1.debdiff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2067338 Title: [SRU] Long SysEx messages are skipped by Midi-Bridge To manage notifications about this bug go to: https://bugs.launchpad.net/pipewire/+bug/2067338/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2066026] Re: [SRU] Klayout 0.28.15 segmentation fault on startup
** Description changed: + [Impact] + + Klayout 0.28.15 is completely incompatible with Python 3.12, and + segfaults on startup. Included patches attempted to increase the + supported version number, but the code itself was incompatible and it + simply would not run. + + Attempts to include a simple patch from upstream proved unsuccessful and + resulted in a complete FTBFS. This was due to the shifting of code in + other places prior to the commits of the patch, meaning the patch was + irrelevant without other pieces of code changed. Hence, the first + version of klayout that supported Python 3.12 was 0.28.16, released on + 12 February 2024. Unfortunately, it was not uploaded to Debian prior to + Feature Freeze/Debian Import Freeze, so it did not make it in-time. + + As reported by the reporter of this bug, no testing on the runtime was + done prior to release. So, while the build was successful, runs are + reproducibly unsuccessful. This package is, therefore, completely + useless in the archive as it stands unless it is updated to version + 0.28.16. + + [Test Case] + + * Install klayout + * Attempt to run klayout + + Expected: Application runs + Actual: Segmentation fault + + [What could go wrong] + + Looking into this application, it seems to be a Suggests of electronics- + asic-dev which is a metapackage for asic development, which installs + applications much like itself, i.e. for electronics engineers and others + who build electronic circuits. It doesn't appear to enhance any other + packages, meaning it has no *actual* reverse dependencies, nor does it + provide any libraries. + + It's hard to regress an application that simply does not function, and + considering it has no actual reverse dependencies, I'm having trouble + fathoming anything going wrong here other than 0.28.16 also failing to + run with further updates. :) + + [Other Information] + + While this is a point release and does concentrate on bug fixes, it does + include some "enhancements" as they're called on the changelog[1] that + may or may not be considered "features": + + * Enhancement: DRC enhancements related to touching edges + - New DRC function switches: "without_touching_corners", "without_touching_edges" to skip width and space errors at kissing corners and touching-edge configurations + - Kissing corners are now detected also in non-collinear edge configuration + * Enhancement: OASIS reader errors out on broken OASIS with duplicate CELLNAMEs + + While including features would normally require a Feature Freeze + exception or a backport, I would argue against it in this case as the + version in the development release of Ubuntu at this time is 0.29.1 + which is magnitudes newer and definitely, per the changelog[2] contains + many new features. + + Other options, such as simply patching for Python 3.12, have been + exhausted. No-change rebuilds also proved to be ineffective. Moving up + one point release as opposed to moving to the latest release seemed to + be the best compromise. Apologies for the diff being so large but, + unfortunately, carrying patches to make 0.28.15 Python 3.12 compatible + would have been more time-consuming and created a diff nearly as large. + + [1]https://www.klayout.de/development.html#0.28.16 + [2]https://www.klayout.de/development.html#0.29.1 + --- + Original bug report follows: + On Ubuntu 24.04, Klayout 0.28.15-1build5 crashes on startup. This is due to a bug described in the upstream issue https://github.com/KLayout/klayout/issues/1619, which shows up on systems using Python 3.12. This bug was fixed in Klayout versions >=0.28.16. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2066026 Title: [SRU] Klayout 0.28.15 segmentation fault on startup To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/klayout/+bug/2066026/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2066026] Re: [SRU] Klayout 0.28.15 segmentation fault on startup
** Summary changed: - Klayout 0.28.15 segmentation fault on startup + [SRU] Klayout 0.28.15 segmentation fault on startup -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2066026 Title: [SRU] Klayout 0.28.15 segmentation fault on startup To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/klayout/+bug/2066026/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2066026] Re: Klayout 0.28.15 segmentation fault on startup
Attempted a no-change rebuild without the patch. Predictably, it built, but segfaulted upon run due to the Python 3.12 incompatibility. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2066026 Title: Klayout 0.28.15 segmentation fault on startup To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/klayout/+bug/2066026/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2066026] Re: Klayout 0.28.15 segmentation fault on startup
The build FTBFS, but it gave an honest try. Turns out the patch is irrellevant without some commits beforehand, but this would be a matter of going into parent commit hell, so I think a saner solution might be to try to update it to 0.28.16. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2066026 Title: Klayout 0.28.15 segmentation fault on startup To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/klayout/+bug/2066026/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2066026] Re: Klayout 0.28.15 segmentation fault on startup
Just a quick update while this is building in my PPA: the patch did *not* apply cleanly and needed a bit of modification since the patch was based on newer code than exists in 0.28.15. Furthermore, even with the changes, it was fuzzy and needed to be applied with the fuzz so the fuzz could be extracted and then the patch rebuilt, which I have done. That said, now we have a clean patched version building in my PPA and hopefully it will run. Will report back as soon as I have an update. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2066026 Title: Klayout 0.28.15 segmentation fault on startup To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/klayout/+bug/2066026/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2066026] Re: Klayout 0.28.15 segmentation fault on startup
** Changed in: klayout (Ubuntu Noble) Status: Triaged => 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/2066026 Title: Klayout 0.28.15 segmentation fault on startup To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/klayout/+bug/2066026/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2066026] Re: Klayout 0.28.15 segmentation fault on startup
** Changed in: klayout (Ubuntu Noble) Status: New => Triaged ** Changed in: klayout (Ubuntu Noble) 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/2066026 Title: Klayout 0.28.15 segmentation fault on startup To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/klayout/+bug/2066026/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2066026] Re: Klayout 0.28.15 segmentation fault on startup
Hi Peter,
>Can we just sync up to debian/0.29.1-1?
In oracular? Yes, it's already there. In noble? That would be a hard
sell. If we can build against the patch that fixes it in the github
issue you linked, then it would be a much easier sell as an SRU.
See https://wiki.ubuntu.com/StableReleaseUpdates for more information.
I'll get working on this.
** Changed in: klayout (Ubuntu)
Assignee: (unassigned) => Erich Eickmeyer (eeickmeyer)
** Also affects: klayout (Ubuntu Oracular)
Importance: Undecided
Assignee: Erich Eickmeyer (eeickmeyer)
Status: New
** Also affects: klayout (Ubuntu Noble)
Importance: Undecided
Status: New
** Changed in: klayout (Ubuntu Noble)
Assignee: (unassigned) => Erich Eickmeyer (eeickmeyer)
** Changed in: klayout (Ubuntu Oracular)
Status: New => Fix Released
** Changed in: klayout (Ubuntu Oracular)
Assignee: Erich Eickmeyer (eeickmeyer) => (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2066026
Title:
Klayout 0.28.15 segmentation fault on startup
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/klayout/+bug/2066026/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2061075] Re: firefox, chromium-browser are not merely a transitional packages
This is sitting in the sponsorship queue doing nothing with a valid debdiff to update at least chromium's info. Furthermore, it's approaching SRU territory and the bug needs to be formatted as such. What's going on here? I'd certainly put this on a higher priority or this is just going to rot. ** Changed in: chromium-browser (Ubuntu) Importance: Low => Medium ** Changed in: firefox (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/2061075 Title: firefox, chromium-browser are not merely a transitional packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2061075/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2061329] Re: [SRU] displaycal 3.9.11-2 fails to start in noble, needs python 3.11
** Summary changed: - displaycal 3.9.11-2 fails to start in noble, needs python 3.11 + [SRU] displaycal 3.9.11-2 fails to start in noble, needs python 3.11 ** Summary changed: - [SRU] displaycal 3.9.11-2 fails to start in noble, needs python 3.11 + [SRU] displaycal 3.9.11-2 needs patch to work with Python 3.12 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2061329 Title: [SRU] displaycal 3.9.11-2 needs patch to work with Python 3.12 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/displaycal-py3/+bug/2061329/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2067618] Re: displaycal-py3 fails to launch due to python version mismatch
*** This bug is a duplicate of bug 2061329 *** https://bugs.launchpad.net/bugs/2061329 ** This bug has been marked a duplicate of bug 2061329 displaycal 3.9.11-2 fails to start in noble, needs python 3.11 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2067618 Title: displaycal-py3 fails to launch due to python version mismatch To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/displaycal-py3/+bug/2067618/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2067338] Re: [SRU] Long SysEx messages are skipped by Midi-Bridge
** Summary changed: - Long SysEx messages are skipped by Midi-Bridge + [SRU] Long SysEx messages are skipped by Midi-Bridge -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2067338 Title: [SRU] Long SysEx messages are skipped by Midi-Bridge To manage notifications about this bug go to: https://bugs.launchpad.net/pipewire/+bug/2067338/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2063879] Re: [SRU] EasyEffects Depends: calf-plugins should be Recommends
$ apt-cache policy easyeffects easyeffects: Installed: 7.1.6-1ubuntu0.24.04.1 Candidate: 7.1.6-1ubuntu0.24.04.1 Version table: *** 7.1.6-1ubuntu0.24.04.1 100 100 http://us.archive.ubuntu.com/ubuntu noble-proposed/universe amd64 Packages 100 /var/lib/dpkg/status 7.1.6-1 500 500 http://us.archive.ubuntu.com/ubuntu noble/universe amd64 Packages Running easyeffects No issues except some filters do not work and require calf-plugins. As stated before, this is merely an enhancement and no longer required by the application. Most state they are using lsp-plugins in lieu of calf- plugins, but without calf some simply don't work. So yes, there is some functionality lost, but not a complete loss of application functionality. For those plugins to work, those users can install calf-plugins, but will lose the ability to use ardour or audacity. For what it's worth, Audacity and Ardour functioned just fine without calf-plugins being installed with easyeffects installed. In my professional opinion, I wouldn't run easyeffects at the same time since, when doing audio production, you want flat speaker response. :) ** Tags removed: verification-needed verification-needed-noble ** Tags added: verification-done verification-done-noble -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2063879 Title: [SRU] EasyEffects Depends: calf-plugins should be Recommends To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/easyeffects/+bug/2063879/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2063847] Re: Audacity hangs on launch if calf-plugins package is installed
Gabriel, For what it's worth, we've had some movement on LP: #2063879 which will remove calf-plugins from being a dependency of easyeffects, so that should solve the coinstallability problem and allow you to remove calf- plugins soon. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2063847 Title: Audacity hangs on launch if calf-plugins package is installed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/audacity/+bug/2063847/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2061329] Re: displaycal 3.9.11-2 fails to start in noble, needs python 3.11
Ok, the fix is now uploaded for Oracular and Noble, and is awaiting SRU approval for Noble. This will take a minimum of one week for the SRU process. For more information, see https://wiki.ubuntu.com/StableReleaseUpdates ** Changed in: displaycal-py3 (Ubuntu Oracular) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2061329 Title: displaycal 3.9.11-2 fails to start in noble, needs python 3.11 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/displaycal-py3/+bug/2061329/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2061329] Re: displaycal 3.9.11-2 fails to start in noble, needs python 3.11
** Description changed: + [Impact] + + DisplayCAL, when released, was only compatible with Python 3.8-3.11. + However, all it needed was WxWidgets 4.1.1 and a few patches to make it + work with Python 3.12. Without, it would simply fail. + + + [Test Case] + + * Install displaycal + * Run displaycal + + Expected: Run normally + Result: + + Traceback (most recent call last): + File "/usr/bin/displaycal", line 4, in + from DisplayCAL.main import main + File "/usr/lib/python3/dist-packages/DisplayCAL/main.py", line 27, in + raise RuntimeError( + RuntimeError: Need Python version >= 3.8 <= 3.11, got 3.12.2 + + + [What could go wrong] + + The DisplayCAL developers do not yet support Python 3.12 until the + release of WxWidgets 4.2.0 since it could crash upon closure. I (Erich + Eickmeyer) have not experienced this in my testing, however, it is + plausible. Additionally, the patches that were used to make this work + were developed after the release of DisplayCAL 3.9.12, but still applied + cleanly to 3.9.11 and made it function correctly. + + + [Other Information] + + Original bug report: + I have upgraded to the noble beta today, and displaycal fails to start. The package dependencies request python 3.12, but the actual software needs 3.11 (or older). ``` $ apt show displaycal | grep Depends WARNING: apt does not have a stable CLI interface. Use with caution in scripts. Depends: libc6 (>= 2.34), libx11-6, libxinerama1 (>= 2:1.1.4), libxrandr2 (>= 2:1.2.0), libxxf86vm1, python3 (<< 3.13), python3 (>= 3.12~), python3-build, python3-certifi, python3-dbus, python3-distro, python3-numpy, python3-pil, python3-pychromecast, python3-send2trash, python3-wxgtk4.0, python3-zeroconf, python3:any, dbus-x11, argyll, libjs-jquery, python3-gi, libsdl2-mixer-2.0-0 - $ displaycal --help + $ displaycal --help Traceback (most recent call last): - File "/usr/bin/displaycal", line 4, in - from DisplayCAL.main import main - File "/usr/lib/python3/dist-packages/DisplayCAL/main.py", line 27, in - raise RuntimeError( + File "/usr/bin/displaycal", line 4, in + from DisplayCAL.main import main + File "/usr/lib/python3/dist-packages/DisplayCAL/main.py", line 27, in + raise RuntimeError( RuntimeError: Need Python version >= 3.8 <= 3.11, got 3.12.2 ``` ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: displaycal 3.9.11-2 ProcVersionSignature: Ubuntu 6.8.0-22.22-generic 6.8.1 Uname: Linux 6.8.0-22-generic x86_64 NonfreeKernelModules: zfs ApportVersion: 2.28.0-0ubuntu1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sun Apr 14 15:16:10 2024 ProcEnviron: - LANG=en_US.UTF-8 - PATH=(custom, no user) - SHELL=/bin/zsh - TERM=xterm-256color - XDG_RUNTIME_DIR= + LANG=en_US.UTF-8 + PATH=(custom, no user) + SHELL=/bin/zsh + TERM=xterm-256color + XDG_RUNTIME_DIR= SourcePackage: displaycal-py3 UpgradeStatus: Upgraded to noble on 2024-04-14 (0 days ago) mtime.conffile..etc.xdg.autostart.z-displaycal-apply-profiles.desktop: 2023-10-22T21:28:16.420795 ** Also affects: displaycal-py3 (Ubuntu Noble) Importance: Undecided Status: New ** Also affects: displaycal-py3 (Ubuntu Oracular) Importance: High Assignee: Erich Eickmeyer (eeickmeyer) Status: In Progress ** Changed in: displaycal-py3 (Ubuntu Noble) Status: New => In Progress ** Changed in: displaycal-py3 (Ubuntu Noble) Importance: Undecided => High ** Changed in: displaycal-py3 (Ubuntu Noble) Assignee: (unassigned) => Erich Eickmeyer (eeickmeyer) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2061329 Title: displaycal 3.9.11-2 fails to start in noble, needs python 3.11 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/displaycal-py3/+bug/2061329/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2061329] Re: displaycal 3.9.11-2 fails to start in noble, needs python 3.11
Ok, we have success built in my PPA at https://launchpad.net/~eeickmeyer/+archive/ubuntu/displaycaltest. I'll convert this bug into an SRU now. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2061329 Title: displaycal 3.9.11-2 fails to start in noble, needs python 3.11 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/displaycal-py3/+bug/2061329/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2061329] Re: displaycal 3.9.11-2 fails to start in noble, needs python 3.11
** Changed in: displaycal-py3 (Ubuntu) Status: Triaged => In Progress ** Changed in: displaycal-py3 (Ubuntu) Assignee: (unassigned) => Erich Eickmeyer (eeickmeyer) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2061329 Title: displaycal 3.9.11-2 fails to start in noble, needs python 3.11 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/displaycal-py3/+bug/2061329/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2061329] Re: displaycal 3.9.11-2 fails to start in noble, needs python 3.11
Unfortunately, that one patch didn't work and it needs more work. Got the following: Traceback (most recent call last): File "/usr/lib/python3/dist-packages/DisplayCAL/main.py", line 549, in main _main(module, name, app_lock_file_name) File "/usr/lib/python3/dist-packages/DisplayCAL/main.py", line 466, in _main from DisplayCAL.wxwindows import BaseApp File "/usr/lib/python3/dist-packages/DisplayCAL/wxwindows.py", line 28, in from DisplayCAL import ICCProfile as ICCP File "/usr/lib/python3/dist-packages/DisplayCAL/ICCProfile.py", line 51, in from DisplayCAL import edid File "/usr/lib/python3/dist-packages/DisplayCAL/edid.py", line 43, in from DisplayCAL import RealDisplaySizeMM as RDSMM File "/usr/lib/python3/dist-packages/DisplayCAL/RealDisplaySizeMM.py", line 47, in _GetXRandROutputXID = GetXRandROutputXID ^^ NameError: name 'GetXRandROutputXID' is not defined -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2061329 Title: displaycal 3.9.11-2 fails to start in noble, needs python 3.11 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/displaycal-py3/+bug/2061329/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2061329] Re: displaycal 3.9.11-2 fails to start in noble, needs python 3.11
Heh, it won't. It simply needs this commit: https://github.com/eoyilmaz/displaycal- py3/commit/0025940335eb1bd56f03f742aa095028d7ffa06f. I'll try simply patching and see if that works. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2061329 Title: displaycal 3.9.11-2 fails to start in noble, needs python 3.11 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/displaycal-py3/+bug/2061329/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2061329] Re: displaycal 3.9.11-2 fails to start in noble, needs python 3.11
Actually, the version of wxwidgets supports 3.12. Currently seeing what a backport of the version in oracular, which contains no new features, does. If it works, I'll try to SRU it into noble. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2061329 Title: displaycal 3.9.11-2 fails to start in noble, needs python 3.11 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/displaycal-py3/+bug/2061329/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2061329] Re: displaycal 3.9.11-2 fails to start in noble, needs python 3.11
So I guess this is an upstream issue they are certainly aware of but it's currently out of their hands. I guess all we can do is wait and see. In the meantime, once we get a viable 3.12 version, I'll try to get it into 24.04 one way or another, hopefully just by patching this version. If not, a wholesale backport of the new version might be in order as it might have changes to be relevant. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2061329 Title: displaycal 3.9.11-2 fails to start in noble, needs python 3.11 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/displaycal-py3/+bug/2061329/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2061329] Re: displaycal 3.9.11-2 fails to start in noble, needs python 3.11
Looks like what we're really waiting on is https://github.com/wxWidgets/Phoenix/issues/2553. ** Bug watch added: github.com/wxWidgets/Phoenix/issues #2553 https://github.com/wxWidgets/Phoenix/issues/2553 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2061329 Title: displaycal 3.9.11-2 fails to start in noble, needs python 3.11 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/displaycal-py3/+bug/2061329/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2061329] Re: displaycal 3.9.11-2 fails to start in noble, needs python 3.11
There's a potential clue on fixing this in https://github.com/eoyilmaz/displaycal-py3/issues/341, but I'm not 100% sure on this. I'm definitely keeping an eye on this. ** Changed in: displaycal-py3 (Ubuntu) Status: Confirmed => Triaged ** Changed in: displaycal-py3 (Ubuntu) Importance: Undecided => High ** Bug watch added: github.com/eoyilmaz/displaycal-py3/issues #341 https://github.com/eoyilmaz/displaycal-py3/issues/341 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2061329 Title: displaycal 3.9.11-2 fails to start in noble, needs python 3.11 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/displaycal-py3/+bug/2061329/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2067510] Re: [SRU] enable ubuntustudio-fix-firstrun.service on initial login
** Changed in: ubuntustudio-installer (Ubuntu Oracular) Status: In Progress => Fix Committed ** Changed in: ubuntustudio-installer (Ubuntu Noble) Status: Triaged => 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/2067510 Title: [SRU] enable ubuntustudio-fix-firstrun.service on initial login To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntustudio-installer/+bug/2067510/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2067512] Re: [SRU] fix for user first run should not affect live session user
** Changed in: ubuntustudio-installer (Ubuntu Oracular) Status: In Progress => Fix Committed ** Changed in: ubuntustudio-installer (Ubuntu Noble) Status: Triaged => 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/2067512 Title: [SRU] fix for user first run should not affect live session user To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntustudio-installer/+bug/2067512/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2067510] Re: [SRU] enable ubuntustudio-fix-firstrun.service on initial login
** Changed in: ubuntustudio-installer (Ubuntu Noble) Milestone: None => noble-updates -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2067510 Title: [SRU] enable ubuntustudio-fix-firstrun.service on initial login To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntustudio-installer/+bug/2067510/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2067512] [NEW] [SRU] fix for user first run should not affect live session user
Public bug reported: [Impact] The fix for configuring users for audio in Ubuntu Studio in LP: #2063899 and LP: #2067510 should not affect and launch for the live session user as it will adversely prompt for a restart when this is not necessary for the live session. While the live session user is, admittedly, not part of the audio group (which should be rectified somehow but is outside of the scope of this SRU), we want to prevent Ubuntu Studio Audio Configuration from launching to do this. This is done by preventing a user named `ubuntu- studio` from running the fix. [Test Case] With a live .iso image of Ubuntu Studio * Fully `apt upgrade` * `systemctl --global enable ubuntustudio-fix-firstrun.service` * `systemctl restart sddm` Expected: Nothing Actual: User is prompted to reboot [What could go wrong] This means that a user cannot be created with the username `ubuntu- studio` and expect normal operation. Users will be notified via release notes that this is the case as it's a reserved username for the live session user. Also, users will be notified via release notes that Ubuntu Studio should not be normally run via persistent USB but should be installed to a system, and that we cannot support persistent USB setups. With the demand Ubuntu Studio has on systems from its applications, realistically, we don't support USB pendrive setups anyhow, so persistent USB setups are discouraged, but now they will be explicitly unsupported. ** Affects: ubuntustudio-installer (Ubuntu) Importance: High Assignee: Erich Eickmeyer (eeickmeyer) Status: In Progress ** Affects: ubuntustudio-installer (Ubuntu Noble) Importance: High Assignee: Erich Eickmeyer (eeickmeyer) Status: Triaged ** Affects: ubuntustudio-installer (Ubuntu Oracular) Importance: High Assignee: Erich Eickmeyer (eeickmeyer) Status: In Progress ** Also affects: ubuntustudio-installer (Ubuntu Noble) Importance: Undecided Status: New ** Also affects: ubuntustudio-installer (Ubuntu Oracular) Importance: High Assignee: Erich Eickmeyer (eeickmeyer) Status: New ** Changed in: ubuntustudio-installer (Ubuntu Noble) Status: New => Triaged ** Changed in: ubuntustudio-installer (Ubuntu Oracular) Status: New => In Progress ** Changed in: ubuntustudio-installer (Ubuntu Noble) Importance: Undecided => High ** Changed in: ubuntustudio-installer (Ubuntu Noble) Assignee: (unassigned) => Erich Eickmeyer (eeickmeyer) ** Changed in: ubuntustudio-installer (Ubuntu Noble) Milestone: None => noble-updates -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2067512 Title: [SRU] fix for user first run should not affect live session user To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntustudio-installer/+bug/2067512/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2067510] [NEW] [SRU] enable ubuntustudio-fix-firstrun.service on initial login
Public bug reported: [Impact] The Debian/rules file includes a `override_dh_installsystemduser:` line to prohibit `ubuntustudio-dummy-audio.service` from being enabled by default for all users on the system. Unfortunately, I neglected to add a `dh_installsystemduser` line for `ubuntustudio-fix-firstrun.service` This means we're not fixing it for users unless they manually run Ubuntu Studio Audio Configuration. [Test Case] * Log in to Ubuntu Studio Expected: Pop-up to tell users to reboot to finish configuration (adds user to the audio group) Actual: nothing [What could go wrong] This is what went wrong with LP: #2063899 but I wouldn't consider it a regression of it as it didn't cause any additional problems, but more like I neglected a step. What could go wrong with this is more like user annoyance, but worth it as it actually solves a problem caused by the lack of user group configuration administration options in ubuntu- desktop-provision. ** Affects: ubuntustudio-installer (Ubuntu) Importance: High Assignee: Erich Eickmeyer (eeickmeyer) Status: In Progress ** Affects: ubuntustudio-installer (Ubuntu Noble) Importance: High Assignee: Erich Eickmeyer (eeickmeyer) Status: Triaged ** Affects: ubuntustudio-installer (Ubuntu Oracular) Importance: High Assignee: Erich Eickmeyer (eeickmeyer) Status: In Progress ** Also affects: ubuntustudio-installer (Ubuntu Noble) Importance: Undecided Status: New ** Also affects: ubuntustudio-installer (Ubuntu Oracular) Importance: Undecided Status: New ** Changed in: ubuntustudio-installer (Ubuntu Noble) Importance: Undecided => High ** Changed in: ubuntustudio-installer (Ubuntu Oracular) Importance: Undecided => High ** Changed in: ubuntustudio-installer (Ubuntu Noble) Assignee: (unassigned) => Erich Eickmeyer (eeickmeyer) ** Changed in: ubuntustudio-installer (Ubuntu Oracular) Assignee: (unassigned) => Erich Eickmeyer (eeickmeyer) ** Changed in: ubuntustudio-installer (Ubuntu Noble) Status: New => Triaged ** Changed in: ubuntustudio-installer (Ubuntu Oracular) 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/2067510 Title: [SRU] enable ubuntustudio-fix-firstrun.service on initial login To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntustudio-installer/+bug/2067510/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2063879] Re: [SRU] EasyEffects Depends: calf-plugins should be Recommends
Ok, fixed Oracular and fixed version string for Noble. ** Changed in: easyeffects (Ubuntu Oracular) Status: In Progress => Fix Committed ** Changed in: easyeffects (Ubuntu Noble) Status: Incomplete => 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/2063879 Title: [SRU] EasyEffects Depends: calf-plugins should be Recommends To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/easyeffects/+bug/2063879/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2067338] Re: Long SysEx messages are skipped by Midi-Bridge
For the SRU teams's sake, we probably should change this status back to "In Progress". ** Changed in: pipewire (Ubuntu Noble) Status: Fix Committed => 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/2067338 Title: Long SysEx messages are skipped by Midi-Bridge To manage notifications about this bug go to: https://bugs.launchpad.net/pipewire/+bug/2067338/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2063895] Re: Multiple plymouth themes display wrong keyboard layout for decryption due to outdated keymap-render.png
$ apt-cache policy plymouth-theme-edubuntu plymouth-theme-edubuntu: Installed: 24.04.26.1 Candidate: 24.04.26.1 Version table: *** 24.04.26.1 100 100 http://us.archive.ubuntu.com/ubuntu noble-proposed/universe amd64 Packages 100 /var/lib/dpkg/status 24.04.26 500 500 http://us.archive.ubuntu.com/ubuntu noble/universe amd64 Packages Upgraded and rebooted. Per attached screenshot, was exactly as expected. ** Attachment added: "VirtualBox_ISOTest_28_05_2024_13_01_45.png" https://bugs.launchpad.net/ubuntu/+source/lubuntu-artwork/+bug/2063895/+attachment/5783668/+files/VirtualBox_ISOTest_28_05_2024_13_01_45.png ** Tags removed: verification-needed verification-needed-noble ** Tags added: verification-done verification-done-noble -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2063895 Title: Multiple plymouth themes display wrong keyboard layout for decryption due to outdated keymap-render.png To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/edubuntu-artwork/+bug/2063895/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2067338] Re: Long SysEx messages are skipped by Midi-Bridge
** Description changed: [Impact] A regression in 1.0.5 has been found in PipeWire and is fixed in 1.0.7. Users of certain MIDI controllers that rely on long SysEx messages are unable to function properly. I noticed this when reconnecting my Beheringer X-Touch (shown here: https://nextcloud.ericheickmeyer.com/index.php/s/k9Aa9Bq7RDD5DoR) after the installation of 24.04 LTS, it could not operate properly. Disabling pipewire-jack and running ardour's internal jack functionality caused it to work properly. Investigation consisted of backporting 1.0.7 via a PPA to Noble which fixed the bug. Bug was confirmed via https://gitlab.freedesktop.org/pipewire/pipewire/-/issues/4005. Solving bug via SRU will consist of creating patches from the commits that fixed the issue in upstream PipeWire. + Tested patches in 1.0.5, confirmed it worked as expected. In my case, + the patches operated normally. Used build in PPA at + https://launchpad.net/~eeickmeyer/+archive/ubuntu/ppa + [Test Case] Using Ubuntu Studio - * Connect a MIDI controller that uses long SysEx messages, such as a + * Connect a MIDI controller that uses long SysEx messages, such as a Behringer X-Touch, to the system. - * Star Ardour + * Star Ardour - * In Preferences > Control Surfaces > Mackie, select the MIDI + * In Preferences > Control Surfaces > Mackie, select the MIDI controller for "Surface sends via:" and "Surface receives via:". Expected: complete control population and function Actual: Only display colors are populated [What could go wrong] It is possible that these patches could cause other problems outside of long SysEx messages in MIDI controllers. However, these patches were developed by the lead developer of PipeWire, Wim Taymans, and I tend to trust that he knows exactly what he's doing with this kind of thing. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: pipewire 1.0.5-1 ProcVersionSignature: Ubuntu 6.8.0-31.31.1-lowlatency 6.8.1 Uname: Linux 6.8.0-31-lowlatency x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.28.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: KDE Date: Mon May 27 20:35:49 2024 InstallationDate: Installed on 2024-04-15 (42 days ago) InstallationMedia: Ubuntu-Studio 24.04 LTS "Noble Numbat" - Beta amd64 (20240410.2) SourcePackage: pipewire UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2067338 Title: Long SysEx messages are skipped by Midi-Bridge To manage notifications about this bug go to: https://bugs.launchpad.net/pipewire/+bug/2067338/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2067338] Re: Long SysEx messages are skipped by Midi-Bridge
As I'm only a MOTU and this is in main, I must request sponosrship from a core-dev. However, I have confirmed that this fixes the bug. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2067338 Title: Long SysEx messages are skipped by Midi-Bridge To manage notifications about this bug go to: https://bugs.launchpad.net/pipewire/+bug/2067338/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2067338] Re: Long SysEx messages are skipped by Midi-Bridge
** Patch added: "pipewire_1.0.5-1ubuntu1.debdiff" https://bugs.launchpad.net/ubuntu/+source/pipewire/+bug/2067338/+attachment/5783484/+files/pipewire_1.0.5-1ubuntu1.debdiff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2067338 Title: Long SysEx messages are skipped by Midi-Bridge To manage notifications about this bug go to: https://bugs.launchpad.net/pipewire/+bug/2067338/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2067338] Re: Long SysEx messages are skipped by Midi-Bridge
** Bug watch added: gitlab.freedesktop.org/pipewire/pipewire/-/issues #4005
https://gitlab.freedesktop.org/pipewire/pipewire/-/issues/4005
** Also affects: pipewire via
https://gitlab.freedesktop.org/pipewire/pipewire/-/issues/4005
Importance: Unknown
Status: Unknown
** Also affects: pipewire (Ubuntu Oracular)
Importance: High
Assignee: Erich Eickmeyer (eeickmeyer)
Status: New
** Also affects: pipewire (Ubuntu Noble)
Importance: Undecided
Status: New
** Changed in: pipewire (Ubuntu Oracular)
Status: New => Fix Released
** Changed in: pipewire (Ubuntu Noble)
Assignee: (unassigned) => Erich Eickmeyer (eeickmeyer)
** Changed in: pipewire (Ubuntu Noble)
Milestone: None => noble-updates
** Changed in: pipewire (Ubuntu Oracular)
Milestone: noble-updates => None
** Changed in: pipewire (Ubuntu Oracular)
Assignee: Erich Eickmeyer (eeickmeyer) => (unassigned)
** Changed in: pipewire (Ubuntu Noble)
Importance: Undecided => High
** Changed in: pipewire (Ubuntu Oracular)
Importance: High => Undecided
** Changed in: pipewire (Ubuntu Noble)
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/2067338
Title:
Long SysEx messages are skipped by Midi-Bridge
To manage notifications about this bug go to:
https://bugs.launchpad.net/pipewire/+bug/2067338/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2067338] [NEW] Long SysEx messages are skipped by Midi-Bridge
Public bug reported: [Impact] A regression in 1.0.5 has been found in PipeWire and is fixed in 1.0.7. Users of certain MIDI controllers that rely on long SysEx messages are unable to function properly. I noticed this when reconnecting my Beheringer X-Touch (shown here: https://nextcloud.ericheickmeyer.com/index.php/s/k9Aa9Bq7RDD5DoR) after the installation of 24.04 LTS, it could not operate properly. Disabling pipewire-jack and running ardour's internal jack functionality caused it to work properly. Investigation consisted of backporting 1.0.7 via a PPA to Noble which fixed the bug. Bug was confirmed via https://gitlab.freedesktop.org/pipewire/pipewire/-/issues/4005. Solving bug via SRU will consist of creating patches from the commits that fixed the issue in upstream PipeWire. [Test Case] Using Ubuntu Studio * Connect a MIDI controller that uses long SysEx messages, such as a Behringer X-Touch, to the system. * Star Ardour * In Preferences > Control Surfaces > Mackie, select the MIDI controller for "Surface sends via:" and "Surface receives via:". Expected: complete control population and function Actual: Only display colors are populated [What could go wrong] It is possible that these patches could cause other problems outside of long SysEx messages in MIDI controllers. However, these patches were developed by the lead developer of PipeWire, Wim Taymans, and I tend to trust that he knows exactly what he's doing with this kind of thing. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: pipewire 1.0.5-1 ProcVersionSignature: Ubuntu 6.8.0-31.31.1-lowlatency 6.8.1 Uname: Linux 6.8.0-31-lowlatency x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.28.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: KDE Date: Mon May 27 20:35:49 2024 InstallationDate: Installed on 2024-04-15 (42 days ago) InstallationMedia: Ubuntu-Studio 24.04 LTS "Noble Numbat" - Beta amd64 (20240410.2) SourcePackage: pipewire UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: pipewire (Ubuntu) Importance: High Assignee: Erich Eickmeyer (eeickmeyer) Status: New ** Tags: amd64 apport-bug noble -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2067338 Title: Long SysEx messages are skipped by Midi-Bridge To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pipewire/+bug/2067338/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2063895] Re: Multiple plymouth themes display wrong keyboard layout for decryption due to outdated keymap-render.png
$ apt-cache policy plymouth-theme-ubuntustudio plymouth-theme-ubuntustudio: Installed: 24.04.9 Candidate: 24.04.9 Version table: *** 24.04.9 100 100 http://archive.ubuntu.com/ubuntu noble-proposed/universe amd64 Packages 100 /var/lib/dpkg/status 24.04.8 500 500 http://archive.ubuntu.com/ubuntu noble/universe amd64 Packages 500 http://us.archive.ubuntu.com/ubuntu noble/universe amd64 Packages Proper layout is now shown, see attached image. ** Attachment added: "VirtualBox_ISOTest_13_05_2024_07_26_57.png" https://bugs.launchpad.net/ubuntu/+source/ubuntustudio-look/+bug/2063895/+attachment/5777987/+files/VirtualBox_ISOTest_13_05_2024_07_26_57.png ** Tags removed: verification-needed verification-needed-noble ** Tags added: verification-done verification-done-noble -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2063895 Title: Multiple plymouth themes display wrong keyboard layout for decryption due to outdated keymap-render.png To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/edubuntu-artwork/+bug/2063895/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2063899] Re: [SRU] Users are not initially configured properly for audio in Ubuntu Studio
$ apt-cache policy ubuntustudio-installer ubuntustudio-installer: Installed: 1.18.2 Candidate: 1.18.2 Version table: *** 1.18.2 100 100 http://us.archive.ubuntu.com/ubuntu noble-proposed/universe amd64 Packages 100 http://us.archive.ubuntu.com/ubuntu noble-proposed/universe i386 Packages 100 /var/lib/dpkg/status 1.18 500 500 http://us.archive.ubuntu.com/ubuntu noble/universe amd64 Packages 500 http://us.archive.ubuntu.com/ubuntu noble/universe i386 Packages * Created new user * Signed-in as new user * Ubuntu Studio Audio Configuration launched, prompted for reboot * Signed-in as new user, launched Ardour * No complaints from Ardour This does appear to be fixed and will properly configure for current users. ** Tags removed: verification-needed verification-needed-noble ** Tags added: verification-done verification-done-noble -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2063899 Title: [SRU] Users are not initially configured properly for audio in Ubuntu Studio To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-desktop-provision/+bug/2063899/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2064170] Re: [SRU] "Switch Configuration" menu selection inoperable
$ apt-cache policy ubuntustudio-installer ubuntustudio-installer: Installed: 1.18.2 Candidate: 1.18.2 Version table: *** 1.18.2 100 100 http://us.archive.ubuntu.com/ubuntu noble-proposed/universe amd64 Packages 100 http://us.archive.ubuntu.com/ubuntu noble-proposed/universe i386 Packages 100 /var/lib/dpkg/status 1.18 500 500 http://us.archive.ubuntu.com/ubuntu noble/universe amd64 Packages 500 http://us.archive.ubuntu.com/ubuntu noble/universe i386 Packages Still working as expected. ** Tags removed: verification-needed verification-needed-noble ** Tags added: verification-done verification-done-noble -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2064170 Title: [SRU] "Switch Configuration" menu selection inoperable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntustudio-installer/+bug/2064170/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2065359] [NEW] [BPO] lsp-plugins/1.2.15-2 from ocular to noble
Public bug reported: [Impact] lsp-plugins 1.2.15 was released shortly after Noble Numbat's feature freeze and includes some features that would not justify an SRU, namely: * Experimental VST-3 Plugin Support * Added built-in presets for Compressor plugin series. among other new features. [Scope] * Backport lsp-plugins 1.2.15-2 from ocular (dev series) * Backport to 24.04 (Noble Numbat) [Other Information) Reverse dependencies: * NONE Reverse recommends: * EasyEffects: EasyEffects functionality is merely enhanced by lsp- plugins and no adverse effects by a newer version are foreseen. Furthermore, no changes to the internal MIDI Input/Output of the plugins, on which EasyEffects uses them, have changed, therefore justifying no impact. Maintenance: * Further backports of lsp-plugins will be provided by myself to noble with newer versions in the devel branch as they come. Successfully built in https://launchpad.net/~ubuntustudio- ppa/+archive/ubuntu/backports-staging ** Affects: lsp-plugins (Ubuntu) Importance: Undecided Status: Invalid ** Affects: lsp-plugins (Ubuntu Noble) Importance: Undecided Assignee: Erich Eickmeyer (eeickmeyer) Status: New ** Also affects: lsp-plugins (Ubuntu Noble) Importance: Undecided Status: New ** Changed in: lsp-plugins (Ubuntu Noble) Assignee: (unassigned) => Erich Eickmeyer (eeickmeyer) ** Changed in: lsp-plugins (Ubuntu) Assignee: Erich Eickmeyer (eeickmeyer) => (unassigned) ** Changed in: lsp-plugins (Ubuntu) Status: New => Invalid ** Description changed: [Impact] lsp-plugins 1.2.15 was released shortly after Noble Numbat's feature freeze and includes some features that would not justify an SRU, namely: - * Experimental VST-3 Plugin Support - * Added built-in presets for Compressor plugin series. + * Experimental VST-3 Plugin Support + * Added built-in presets for Compressor plugin series. among other new features. [Scope] - * Backport lsp-plugins 1.2.15-2 from ocular (dev series) - * Backport to 24.04 (Noble Numbat) + * Backport lsp-plugins 1.2.15-2 from ocular (dev series) + * Backport to 24.04 (Noble Numbat) [Other Information) Reverse dependencies: - * NONE + * NONE Reverse recommends: - * EasyEffects: EasyEffects functionality is merely enhanced by lsp- + * EasyEffects: EasyEffects functionality is merely enhanced by lsp- plugins and no adverse effects by a newer version are foreseen. Furthermore, no changes to the internal MIDI Input/Output of the plugins, on which EasyEffects uses them, have changed, therefore justifying no impact. Maintenance: - * Further backports of lsp-plugins will be provided by myself to noble + * Further backports of lsp-plugins will be provided by myself to noble with newer versions in the devel branch as they come. + + Successfully built in https://launchpad.net/~ubuntustudio- + ppa/+archive/ubuntu/backports-staging -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2065359 Title: [BPO] lsp-plugins/1.2.15-2 from ocular to noble To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lsp-plugins/+bug/2065359/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2054395] Re: [sru] sos upstream 4.7.0
@athos-ribeiro
A debdiff should most certainly not be trying to patch a symlink. I'd
recommend trying it with `patch -p1 < {debdiff}` and build the source
package to see if it works. If it complains about changes to the source
that aren't reflected, then yes, there's a problem with the debdiff, but
that's usually overcome by extracting the source.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2054395
Title:
[sru] sos upstream 4.7.0
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-pro/+bug/2054395/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2065112] Re: Sync chroma 1.19-2 (universe) from Debian unstable (main)
This bug was fixed in the package chroma - 1.19-2 --- chroma (1.19-2) unstable; urgency=low * No-change upload to cancel NMU re #1007426 and fix spuriuous "ubuntu" in version. -- Ian Jackson Sun, 11 Dec 2022 17:54:27 + chroma (1.19-1ubuntu1) unstable; urgency=low * Fix build process to isolate inkscape from $HOME and the GUI. (Closes: #997904) * Fix generation of images using Inkscape >= 1.0. -- Simon Tatham Wed, 27 Oct 2021 18:51:17 +0100 ** Changed in: chroma (Ubuntu) Status: New => In Progress ** Changed in: chroma (Ubuntu) Status: In Progress => 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/2065112 Title: Sync chroma 1.19-2 (universe) from Debian unstable (main) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chroma/+bug/2065112/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2065117] Re: Please merge 0.0.2012-06-kde4.8-6 into Oracular
Sponsored! ** Changed in: oxygencursors (Ubuntu) Status: New => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2065117 Title: Please merge 0.0.2012-06-kde4.8-6 into Oracular To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/oxygencursors/+bug/2065117/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2063899] Re: [SRU] Users are not initially configured properly for audio in Ubuntu Studio
$ apt-cache policy ubuntustudio-installer ubuntustudio-installer: Installed: 1.18.1 Candidate: 1.18.1 Version table: *** 1.18.1 100 100 http://us.archive.ubuntu.com/ubuntu noble-proposed/universe amd64 Packages 100 http://us.archive.ubuntu.com/ubuntu noble-proposed/universe i386 Packages 100 /var/lib/dpkg/status 1.18 500 500 http://us.archive.ubuntu.com/ubuntu noble/universe amd64 Packages 500 http://us.archive.ubuntu.com/ubuntu noble/universe i386 Packages * Created new user * Signed-in as new user x Ubuntu Studio Audio Configuration did *NOT* launch to configure user in audio group or install audio.conf file if necessary * Manually launched Ubuntu Studio Audio Configuarion - successfully added user to audio group, made sure audio.conf file was installed, and rebooted system. With that, the test was 1/2 successful - this should have happened on login not on launch of the audio configuration utility. As it turns out, the `graphical.target` in the systemd .session file should be `graphical-session.target`. Will reupload with a fix. ** Changed in: ubuntustudio-installer (Ubuntu Noble) Status: Fix Committed => In Progress ** Changed in: ubuntustudio-installer (Ubuntu Oracular) Status: Fix Released => In Progress ** Tags removed: verification-needed verification-needed-noble ** Tags added: verification-failed verification-failed-noble -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2063899 Title: [SRU] Users are not initially configured properly for audio in Ubuntu Studio To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-desktop-provision/+bug/2063899/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2063899] Re: [SRU] Users are not initially configured properly for audio in Ubuntu Studio
** Changed in: ubuntustudio-default-settings (Ubuntu Oracular) Status: Fix Committed => Triaged ** Changed in: ubuntustudio-default-settings (Ubuntu Noble) Status: In Progress => Triaged -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2063899 Title: [SRU] Users are not initially configured properly for audio in Ubuntu Studio To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-desktop-provision/+bug/2063899/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2064170] Re: [SRU] "Switch Configuration" menu selection inoperable
$ apt-cache policy ubuntustudio-installer ubuntustudio-installer: Installed: 1.18.1 Candidate: 1.18.1 Version table: *** 1.18.1 100 100 http://us.archive.ubuntu.com/ubuntu noble-proposed/universe amd64 Packages 100 http://us.archive.ubuntu.com/ubuntu noble-proposed/universe i386 Packages 100 /var/lib/dpkg/status 1.18 500 500 http://us.archive.ubuntu.com/ubuntu noble/universe amd64 Packages 500 http://us.archive.ubuntu.com/ubuntu noble/universe i386 Packages New behavior: No longer taken back to main menu, but properly presented with menu to switch to legacy configuration. This is desired. ** Tags removed: verification-needed verification-needed-noble ** Tags added: verification-done verification-done-noble -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2064170 Title: [SRU] "Switch Configuration" menu selection inoperable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntustudio-installer/+bug/2064170/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2063895] Re: Multiple plymouth themes display wrong keyboard layout for decryption due to outdated keymap-render.png
>Can you explain the purpose of this change? A leading _ is usually a marker that a string is to be translated. It doesn't seem like a change we want to make these strings NOT be translated. Copied directly from the actual /usr/share/Plymouth/themes/spinner/spinner.plymouth. Unfortunately, the items with the underscores were never translated. ** Changed in: ubuntustudio-look (Ubuntu Noble) Status: Incomplete => 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/2063895 Title: Multiple plymouth themes display wrong keyboard layout for decryption due to outdated keymap-render.png To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/edubuntu-artwork/+bug/2063895/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2063899] Re: [SRU] Users are not initially configured properly for audio in Ubuntu Studio
** Changed in: ubuntustudio-default-settings (Ubuntu Noble) Status: Triaged => 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/2063899 Title: [SRU] Users are not initially configured properly for audio in Ubuntu Studio To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-desktop-provision/+bug/2063899/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2063899] Re: [SRU] Users are not initially configured properly for audio in Ubuntu Studio
> This results in an unowned file on the filesystem, and you don't remove it again on package removal. Is there a reason you aren't shipping this as a conffile? Merely forgot to make sure it gets removed, but it has to be conditional in that it doesn't get removed *if* ubuntustudio-installer is also installed since both packages install the file. ubuntustudio-installer doesn't require that ubuntustudio-default-settings be present, so neither can own the file. Shipping as a conffile would require both ubuntustudio-installer *and* this package shipping it as a conffile, so that's not a good idea. ** Changed in: ubuntustudio-default-settings (Ubuntu Noble) Status: Incomplete => Triaged -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2063899 Title: [SRU] Users are not initially configured properly for audio in Ubuntu Studio To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-desktop-provision/+bug/2063899/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2063895] Re: Multiple plymouth themes display wrong keyboard layout for decryption due to outdated keymap-render.png
** Changed in: edubuntu-artwork (Ubuntu Noble) Status: Incomplete => In Progress ** Changed in: edubuntu-artwork (Ubuntu Oracular) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2063895 Title: Multiple plymouth themes display wrong keyboard layout for decryption due to outdated keymap-render.png To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/edubuntu-artwork/+bug/2063895/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2063899] Re: [SRU] Users are not initially configured properly for audio in Ubuntu Studio
> this is marked 'fix committed' but there is no upload in oracular- proposed. blocks SRU. I uploaded it before changing the status and just got a "Rejected" for trying to upload again. ** Changed in: ubuntustudio-default-settings (Ubuntu Oracular) Status: Incomplete => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2063899 Title: [SRU] Users are not initially configured properly for audio in Ubuntu Studio To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-desktop-provision/+bug/2063899/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2064170] Re: [SRU] "Switch Configuration" menu selection inoperable
** Also affects: ubuntustudio-installer (Ubuntu Noble) Importance: Undecided Status: New ** Also affects: ubuntustudio-installer (Ubuntu Oracular) Importance: High Assignee: Erich Eickmeyer (eeickmeyer) Status: Incomplete ** Changed in: ubuntustudio-installer (Ubuntu Oracular) Status: Incomplete => Fix Committed ** Changed in: ubuntustudio-installer (Ubuntu Noble) Status: New => In Progress ** Changed in: ubuntustudio-installer (Ubuntu Noble) Importance: Undecided => High ** Changed in: ubuntustudio-installer (Ubuntu Noble) Assignee: (unassigned) => Erich Eickmeyer (eeickmeyer) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2064170 Title: [SRU] "Switch Configuration" menu selection inoperable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntustudio-installer/+bug/2064170/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2063899] Re: [SRU] Users are not initially configured properly for audio in Ubuntu Studio
** Changed in: ubuntustudio-installer (Ubuntu Oracular) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2063899 Title: [SRU] Users are not initially configured properly for audio in Ubuntu Studio To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-desktop-provision/+bug/2063899/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2063895] Re: Multiple plymouth themes display wrong keyboard layout for decryption due to outdated keymap-render.png
** Changed in: ubuntustudio-look (Ubuntu Oracular) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2063895 Title: Multiple plymouth themes display wrong keyboard layout for decryption due to outdated keymap-render.png To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/edubuntu-artwork/+bug/2063895/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2063895] Re: Multiple plymouth themes display wrong keyboard layout for decryption due to outdated keymap-render.png
** Also affects: edubuntu-artwork (Ubuntu Oracular) Importance: High Status: In Progress ** Also affects: ubuntustudio-look (Ubuntu Oracular) Importance: High Status: In Progress ** Also affects: lubuntu-artwork (Ubuntu Oracular) Importance: High Status: New ** Also affects: plymouth-theme-ubuntu-unity (Ubuntu Oracular) Importance: High Status: New ** Changed in: ubuntustudio-look (Ubuntu Noble) Milestone: None => noble-updates ** Changed in: edubuntu-artwork (Ubuntu Noble) Milestone: None => noble-updates -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2063895 Title: Multiple plymouth themes display wrong keyboard layout for decryption due to outdated keymap-render.png To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/edubuntu-artwork/+bug/2063895/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2063899] Re: [SRU] Users are not initially configured properly for audio in Ubuntu Studio
** Changed in: ubuntustudio-default-settings (Ubuntu Oracular) Status: In Progress => Fix Committed ** Changed in: ubuntustudio-installer (Ubuntu Oracular) Milestone: noble-updates => None ** Changed in: ubuntustudio-installer (Ubuntu Noble) Milestone: None => noble-updates ** Changed in: ubuntustudio-default-settings (Ubuntu Noble) Milestone: None => noble-updates -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2063899 Title: [SRU] Users are not initially configured properly for audio in Ubuntu Studio To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-desktop-provision/+bug/2063899/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2063879] Re: [SRU] EasyEffects Depends: calf-plugins should be Recommends
** Also affects: easyeffects (Ubuntu Oracular) Importance: Medium Assignee: Erich Eickmeyer (eeickmeyer) Status: 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/2063879 Title: [SRU] EasyEffects Depends: calf-plugins should be Recommends To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/easyeffects/+bug/2063879/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2063899] Re: [SRU] Users are not initially configured properly for audio in Ubuntu Studio
** Also affects: ubuntustudio-default-settings (Ubuntu Noble) Importance: Undecided Status: New ** Also affects: ubuntustudio-installer (Ubuntu Noble) Importance: Undecided Status: New ** Also affects: ubuntustudio-default-settings (Ubuntu Oracular) Importance: High Assignee: Erich Eickmeyer (eeickmeyer) Status: In Progress ** Also affects: ubuntustudio-installer (Ubuntu Oracular) Importance: High Assignee: Erich Eickmeyer (eeickmeyer) Status: In Progress ** Changed in: ubuntustudio-default-settings (Ubuntu Noble) Status: New => In Progress ** Changed in: ubuntustudio-installer (Ubuntu Noble) Status: New => In Progress ** Changed in: ubuntustudio-installer (Ubuntu Noble) Importance: Undecided => High ** Changed in: ubuntustudio-default-settings (Ubuntu Noble) Importance: Undecided => High ** Changed in: ubuntustudio-default-settings (Ubuntu Noble) Assignee: (unassigned) => Erich Eickmeyer (eeickmeyer) ** Changed in: ubuntustudio-installer (Ubuntu Noble) Assignee: (unassigned) => Erich Eickmeyer (eeickmeyer) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2063899 Title: [SRU] Users are not initially configured properly for audio in Ubuntu Studio To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-desktop-provision/+bug/2063899/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2063879] Re: [SRU] EasyEffects Depends: calf-plugins should be Recommends
The change in behavior depends on what the user wants. Basically, it comes down to this: does the user want EasyEffects with the enhancements provided by calf-plugins and broken Ardour/Audacity (or others perhaps?) or do they want to be able to remove calf-plugins and still have a functioning EasyEffects minus those enhancements? Additionally, and one reason why I got lsp-plugins packaged in Ubuntu (and then it was undertaken by Debian so long ago) was because calf- plugins development had stalled as it depends on GTK-2, which in turn causes errors in Ardour. lsp-plugins takes the place of a lot of calf- plugins in functionality and may have surpassed by now These plugins function in such a way that their code becomes part of the code of the host program, so if the host program has a conflicting toolkit, it tends to crash. EasyEffects does not expose the plugins' native interface to the user, thus avoiding those issues. However, Ardour and Audacity do, which causes them to break when testing the plugins for functionality during an initial scan. The recommendation in the Debian bug report is to drop calf-plugins to a recommends, but I took it a step further by making it a recommends if lsp-plugins is not already installed. This should make it auto- uninstalable on machines that already have it installed. If a user wants those enhancements again, it's simple to reinstall. So far, I have had no objections in the Debian package. One thing I'd note, though, is that within easyeffects, lsp-plugins and calf-plugins do duplicate each others' capabilities, which is why I'd think having one or the other as a recommends would be ideal. The reason easyeffects had calf-plugins as a Depends was merely due to leftovers from PulseEffects, its predecessor, which required calf- plugins as a hard dependency in order to even function. However, PipeWire doesn't require that as it has built-in filters, but having the plugins serves as an enhancement. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2063879 Title: [SRU] EasyEffects Depends: calf-plugins should be Recommends To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/easyeffects/+bug/2063879/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2063899] Re: [SRU] Users are not initially configured properly for audio in Ubuntu Studio
** Also affects: ubuntustudio-default-settings (Ubuntu) Importance: Undecided Status: New ** Changed in: ubuntustudio-default-settings (Ubuntu) Status: New => In Progress ** Changed in: ubuntustudio-default-settings (Ubuntu) Importance: Undecided => High ** Changed in: ubuntustudio-default-settings (Ubuntu) Assignee: (unassigned) => Erich Eickmeyer (eeickmeyer) ** Description changed: [Impact] Ubiquity and Calamares used to have a facility to make the first configured user part of the `audio` group by default. Unfortunately, with `ubuntu-desktop-bootstrap`, we lost this ability in Ubuntu Studio and making sure that the users had the proper configuration (memory limits for the audio group) was an oversight. Fortunately, the ubuntustudio-installer application, and its included ubuntustudio-audio-config application, have the facility to do that, although the script needed a little bit of work and the entire package was missing a runtime dependency on `polkitd-pkla` to make the whole system work as expected. + + Additionally, `ubuntustudio-default-settings` needs to add additional + configuations to /etc/adduser.conf so that new users are automatically + part of the audio group and provide the + /etc/security/limits.d/audio.conf file. In the meantime, having Audio + Configuration fix existing users is a good workaround. [Test Case] * Run Ardour * Ardour will complain about limited memory (see screenshot attached) Expected: No complaints from Ardour [What could go wrong] The only thing I expect could go wrong is that the systemd user service fails to launch. The backup for this is to run ubuntustudio-audio-config from the launcher, which would run everything as expected (setting the memory limits, adding the user to the `audio` group, and rebooting the system). - [Other Information] What really needs to happen here is that `ubuntu-desktop-provision` or `subiquity` needs to add the initial user to the audio group, or at least provide the facility for Ubuntu Studio to configure the initial user to be added as such similar to how Ubiquity did. - - Additionally, `ubuntustudio-lowlatency-settings` (part of ubuntustudio- - default-settings) may need to add an `adduser` hook to add new users to - the audio group and provide the /etc/security/limits.d/audio.conf file. - In the meantime, having Audio Configuration fix existing users is a good - workaround. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2063899 Title: [SRU] Users are not initially configured properly for audio in Ubuntu Studio To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-desktop-provision/+bug/2063899/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2063899] Re: [SRU] Users are not initially configured properly
** Also affects: ubuntu-desktop-provision Importance: Undecided Status: New ** Summary changed: - [SRU] Users are not initially configured properly + [SRU] Users are not initially configured properly for audio in Ubuntu Studio ** Description changed: [Impact] Ubiquity and Calamares used to have a facility to make the first configured user part of the `audio` group by default. Unfortunately, with `ubuntu-desktop-bootstrap`, we lost this ability in Ubuntu Studio and making sure that the users had the proper configuration (memory limits for the audio group) was an oversight. Fortunately, the ubuntustudio-installer application, and its included ubuntustudio-audio-config application, have the facility to do that, although the script needed a little bit of work and the entire package was missing a runtime dependency on `polkitd-pkla` to make the whole system work as expected. [Test Case] - * Run Ardour - * Ardour will complain about limited memory (see screenshot attached) + * Run Ardour + * Ardour will complain about limited memory (see screenshot attached) Expected: No complaints from Ardour [What could go wrong] The only thing I expect could go wrong is that the systemd user service fails to launch. The backup for this is to run ubuntustudio-audio-config from the launcher, which would run everything as expected (setting the memory limits, adding the user to the `audio` group, and rebooting the system). + + + [Other Information] + + What really needs to happen here is that `ubuntu-desktop-provision` or + `subiquity` needs to add the initial user to the audio group, or at + least provide the facility for Ubuntu Studio to configure the initial + user to be added as such similar to how Ubiquity did. + + Additionally, `ubuntustudio-lowlatency-settings` (part of ubuntustudio- + default-settings) may need to add an `adduser` hook to add new users to + the audio group and provide the /etc/security/limits.d/audio.conf file. + In the meantime, having Audio Configuration fix existing users is a good + workaround. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2063899 Title: [SRU] Users are not initially configured properly for audio in Ubuntu Studio To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-desktop-provision/+bug/2063899/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2064170] Re: [SRU] "Switch Configuration" menu selection inoperable
** Changed in: ubuntustudio-installer (Ubuntu) Status: Triaged => In Progress ** Changed in: ubuntustudio-installer (Ubuntu) Assignee: (unassigned) => Erich Eickmeyer (eeickmeyer) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2064170 Title: [SRU] "Switch Configuration" menu selection inoperable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntustudio-installer/+bug/2064170/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2064170] [NEW] [SRU] "Switch Configuration" menu selection inoperable
Public bug reported: [Impact] In Ubuntu Studio Audio Configuration, the "Switch Configuration" selection, which allows a user to switch between the (now considered deprecated) PulseAudio/JACK setup and the modern PipeWire setup, is completely inoperable due to a typographical error in the code. [Test Case] * Open Ubuntu Studio Audio Configuration * Click on "Switch Configuration", click "Continue" * User is not taken to next step, but repeated to main menu. This is not desired. [What could go wrong] This was due to the omission of the letter "n" when looking for a string returned by zenity. This is highly tested and the fix works as expected, if not perfectly, but maybe something else snuck-in. ** Affects: ubuntustudio-installer (Ubuntu) Importance: High Status: Triaged -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2064170 Title: [SRU] "Switch Configuration" menu selection inoperable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntustudio-installer/+bug/2064170/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2063879] Re: [SRU] EasyEffects Depends: calf-plugins should be Recommends
I mean, not a bad idea, but it does handle *some* functionality, but it's not *required* to function. I'm not sure that demoting it that much is completely justified and I don't want to step on the maintainer too much. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2063879 Title: [SRU] EasyEffects Depends: calf-plugins should be Recommends To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/easyeffects/+bug/2063879/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2063895] Re: Multiple plymouth themes display wrong keyboard layout for decryption due to outdated keymap-render.png
Likewise, attaching screenshot of Ubuntu Studio to show issue. Bringing that dialog up slightly in the fix as well. ** Attachment added: "VirtualBox_ISOTest_26_04_2024_18_56_17.png" https://bugs.launchpad.net/ubuntu/+source/ubuntustudio-look/+bug/2063895/+attachment/5771198/+files/VirtualBox_ISOTest_26_04_2024_18_56_17.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2063895 Title: Multiple plymouth themes display wrong keyboard layout for decryption due to outdated keymap-render.png To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/edubuntu-artwork/+bug/2063895/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2063895] Re: Multiple plymouth themes display wrong keyboard layout for decryption due to outdated keymap-render.png
Attaching screenshot of Edubuntu without fix. Also fixing to bring that dialog down to make readable. ** Changed in: ubuntustudio-look (Ubuntu Noble) Status: Triaged => In Progress ** Changed in: edubuntu-artwork (Ubuntu Noble) Status: Triaged => In Progress ** Attachment added: "VirtualBox_ISOTest_26_04_2024_18_36_41.png" https://bugs.launchpad.net/ubuntu/+source/ubuntustudio-look/+bug/2063895/+attachment/5771197/+files/VirtualBox_ISOTest_26_04_2024_18_36_41.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2063895 Title: Multiple plymouth themes display wrong keyboard layout for decryption due to outdated keymap-render.png To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/edubuntu-artwork/+bug/2063895/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2063895] Re: Multiple plymouth themes display wrong keyboard layout for decryption due to outdated keymap-render.png
** Changed in: edubuntu-artwork (Ubuntu Noble) Status: New => Triaged ** Changed in: ubuntustudio-look (Ubuntu Noble) Status: New => Triaged -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2063895 Title: Multiple plymouth themes display wrong keyboard layout for decryption due to outdated keymap-render.png To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/edubuntu-artwork/+bug/2063895/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2063895] Re: Multiple plymouth themes display wrong keyboard layout for decryption due to outdated keymap-render.png
** Also affects: ubuntustudio-look (Ubuntu) Importance: Undecided Status: New ** Changed in: ubuntustudio-look (Ubuntu Noble) Importance: Undecided => High -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2063895 Title: Multiple plymouth themes display wrong keyboard layout for decryption due to outdated keymap-render.png To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/edubuntu-artwork/+bug/2063895/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2063895] Re: Multiple plymouth themes display wrong keyboard layout for decryption due to outdated keymap-render.png
I thought attaching the file in question here might be a good idea. :) ** Attachment added: "keymap-render.png" https://bugs.launchpad.net/ubuntu/+source/plymouth-theme-ubuntu-unity/+bug/2063895/+attachment/5771196/+files/keymap-render.png ** Also affects: edubuntu-artwork (Ubuntu) Importance: Undecided Status: New ** Changed in: edubuntu-artwork (Ubuntu Noble) Importance: Undecided => High -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2063895 Title: Multiple plymouth themes display wrong keyboard layout for decryption due to outdated keymap-render.png To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/edubuntu-artwork/+bug/2063895/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2063895] Re: Multiple plymouth themes display wrong keyboard layout for decryption due to outdated keymap-render.png
** Description changed: [ Impact ] During the 24.04 cycle, an update was made to Plymouth. This update - apparently mandated the includsion of a lot more keyboard layouts into + apparently mandated the inclusion of a lot more keyboard layouts into the `keymap-render.png` file for each Plymouth theme, which is used by Plymouth to display what keyboard layout the user should type in when providing a disk decryption passphrase. The changes made to Plymouth are not compatible with the older `keymap-render.png` files, meaning that if a user installs with FDE enabled, the keyboard layout shown to them on the Plymouth screen will **not** be the keyboard layout actually in use. For instance, if you install a system using the US English keyboard layout, you will be told you should type in Norse (layout `no`) to decrypt the disk, despite the fact that the layout actually in use is indeed `us`. While the `spinner` Plymouth theme in use by Ubuntu got the needed update, and Kubuntu and Ubuntu Cinnamon both got the needed updates, many if not all of the remaining Plymouth themes were not updated, meaning FDE users are being shown confusing keyboard layout information every time they boot their system. The solution is to copy the `keymap-render.png` file from the `spinner` Plymouth theme into the Plymouth themes for each affected flavor. So far Lubuntu and Ubuntu Unity are known to be affected. It is likely that other flavors are as well. [ Test Plan ] * For each flavor, do an encrypted installation and observe whether the wrong keyboard layout is shown on the decryption screen. Ideally, do each installation with a different keyboard layout selected. * For each affected flavor, install a Plymouth theme package that has the updated keymap-render.png file, then reboot the system. * Observe the decryption screen and ensure the proper keyboard layout is shown. [ Where problems could occur ] If the keymap-render.png file from `spinner` is also wrong in some way (which I have not seen yet), then applying updates in this way will result in everyone's decryption keyboard layout indicator being broken in the same way. Doing each installation with a different keyboard layout should detect if the image is obviously broken and only just so happens to work with the couple of keyboard layouts I've already tried. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2063895 Title: Multiple plymouth themes display wrong keyboard layout for decryption due to outdated keymap-render.png To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lubuntu-artwork/+bug/2063895/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2063899] Re: Dummy audio device running on new installs
** Changed in: ubuntustudio-installer (Ubuntu) Importance: Undecided => High ** Summary changed: - Dummy audio device running on new installs + [SRU] Users are not initially configured properly -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2063899 Title: [SRU] Users are not initially configured properly To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntustudio-installer/+bug/2063899/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2063899] [NEW] Dummy audio device running on new installs
Public bug reported: [Impact] Ubiquity and Calamares used to have a facility to make the first configured user part of the `audio` group by default. Unfortunately, with `ubuntu-desktop-bootstrap`, we lost this ability in Ubuntu Studio and making sure that the users had the proper configuration (memory limits for the audio group) was an oversight. Fortunately, the ubuntustudio-installer application, and its included ubuntustudio-audio-config application, have the facility to do that, although the script needed a little bit of work and the entire package was missing a runtime dependency on `polkitd-pkla` to make the whole system work as expected. [Test Case] * Run Ardour * Ardour will complain about limited memory (see screenshot attached) Expected: No complaints from Ardour [What could go wrong] The only thing I expect could go wrong is that the systemd user service fails to launch. The backup for this is to run ubuntustudio-audio-config from the launcher, which would run everything as expected (setting the memory limits, adding the user to the `audio` group, and rebooting the system). ** Affects: ubuntustudio-installer (Ubuntu) Importance: Undecided Assignee: Erich Eickmeyer (eeickmeyer) Status: In Progress ** Attachment added: "Screenshot_20240426_163412.png" https://bugs.launchpad.net/bugs/2063899/+attachment/5771168/+files/Screenshot_20240426_163412.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2063899 Title: Dummy audio device running on new installs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntustudio-installer/+bug/2063899/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2063879] Re: [SRU] EasyEffects Depends: calf-plugins should be Recommends
** Changed in: easyeffects (Ubuntu Noble) Milestone: None => noble-updates -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2063879 Title: [SRU] EasyEffects Depends: calf-plugins should be Recommends To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/easyeffects/+bug/2063879/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2063879] [NEW] [SRU] EasyEffects Depends: calf-plugins should be Recommends
Public bug reported:
[Impact]
easyeffects has a packaging error in that it has a hard run-time Depends
on calf-plugins, which hasn't had a proper release in over five years
and has suffered bit-rot. Its mere presence on a system with Ardour and
Audacity installed can cause either program to crash (see LP: #2063847).
While this is certainly a bug in calf, removing it causing a removal of
EasyEffects isn't necessary.
Per the codebase of EasyEffects, it's calf is merely stated to be an
optional dependency, and as stated in the readme, "usage was replaced by
native PipeWire filters."
[Test Case]
* Install easyeffects
* Install audacity
* Run Audacity (Audacity will likely crash due to calf-plugins)
* Attempt removal of calf-plugins (will remove easyeffects)
[What could go wrong]
Some functionality of easyeffects could go missing, but this would
likely be replaced by the lsp-plugins-lv2 package which is more stable,
development-active, and functional. As an audio professional and Ubuntu
Studio's lead, we recommend these plugins over calf anyhow in terms of
quality.
[Other information]
This has been reported upstream (https://bugs.debian.org/cgi-
bin/bugreport.cgi?bug=1063319), and as part of the Debian Multimedia
Team I have submitted a direct commit to the package
(https://salsa.debian.org/multimedia-
team/easyeffects/-/commit/862142c0b64f6c0cf07a4abda2a57946663eeb4c).
** Affects: easyeffects (Ubuntu)
Importance: Medium
Assignee: Erich Eickmeyer (eeickmeyer)
Status: In Progress
** Affects: easyeffects (Ubuntu Noble)
Importance: Medium
Assignee: Erich Eickmeyer (eeickmeyer)
Status: In Progress
** Changed in: easyeffects (Ubuntu)
Assignee: (unassigned) => Erich Eickmeyer (eeickmeyer)
** Changed in: easyeffects (Ubuntu)
Status: New => In Progress
** Changed in: easyeffects (Ubuntu)
Importance: Undecided => Medium
** Also affects: easyeffects (Ubuntu Focal)
Importance: Undecided
Status: New
** Also affects: easyeffects (Ubuntu Noble)
Importance: Medium
Assignee: Erich Eickmeyer (eeickmeyer)
Status: In Progress
** No longer affects: easyeffects (Ubuntu Focal)
** Description changed:
[Impact]
easyeffects has a packaging error in that it has a hard run-time Depends
on calf-plugins, which hasn't had a proper release in over five years
and has suffered bit-rot. Its mere presence on a system with Ardour and
Audacity installed can cause either program to crash (see LP: #2063847).
While this is certainly a bug in calf, removing it causing a removal of
EasyEffects isn't necessary.
Per the codebase of EasyEffects, it's calf is merely stated to be an
optional dependency, and as stated in the readme, "usage was replaced by
native PipeWire filters."
[Test Case]
- * Install easyeffects
- * Install audacity
- * Run Audacity (Audacity will likely crash due to calf-plugins)
- * Attempt removal of calf-plugins (will remove easyeffects)
+ * Install easyeffects
+ * Install audacity
+ * Run Audacity (Audacity will likely crash due to calf-plugins)
+ * Attempt removal of calf-plugins (will remove easyeffects)
[What could go wrong]
Some functionality of easyeffects could go missing, but this would
likely be replaced by the lsp-plugins-lv2 package which is more stable,
development-active, and functional. As an audio professional and Ubuntu
Studio's lead, we recommend these plugins over calf anyhow in terms of
quality.
+
+ [Other information]
+
+ This has been reported upstream (https://bugs.debian.org/cgi-
+ bin/bugreport.cgi?bug=1063319), and as part of the Debian Multimedia
+ Team I have submitted a direct commit to the package
+ (https://salsa.debian.org/multimedia-
+ team/easyeffects/-/commit/862142c0b64f6c0cf07a4abda2a57946663eeb4c).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2063879
Title:
[SRU] EasyEffects Depends: calf-plugins should be Recommends
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/easyeffects/+bug/2063879/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2063847] Re: Audacity hangs on launch if calf-plugins package is installed
That's fine, but I am working on an SRU (Stable Release Update) of EasyEffects since this is certainly a packaging error that I can fix (not my error, but I have a fairly big hammer). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2063847 Title: Audacity hangs on launch if calf-plugins package is installed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/audacity/+bug/2063847/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2063847] Re: Audacity hangs on launch if calf-plugins package is installed
There's an open Debian bug in regards to that (https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1063319), but that's a separate bug from this, though it would be justify to fix it as it affects this bug (as noted in that bug). ** Bug watch added: Debian Bug tracker #1063319 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1063319 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2063847 Title: Audacity hangs on launch if calf-plugins package is installed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/audacity/+bug/2063847/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
