Ok, I filed a bug report with Debian. Hope it gets through.
** Bug watch added: Debian Bug tracker #1067662
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1067662
--
You received this bug notification because you are a member of Ubuntu
Studio Bugs, which is subscribed to a2jmidid in Ubuntu
Filed as bug 1067662 in https://bugs.debian.org/cgi-
bin/bugreport.cgi?bug=1067662
--
You received this bug notification because you are a member of Ubuntu
Studio Bugs, which is subscribed to a2jmidid in Ubuntu.
Matching subscriptions: Ubuntu Studio Bugs
https://bugs.launchpad.net/bugs/2058799
T
** Changed in: a2jmidid (Ubuntu)
Status: Incomplete => Triaged
** Changed in: a2jmidid (Ubuntu)
Importance: Undecided => Medium
--
You received this bug notification because you are a member of Ubuntu
Studio Bugs, which is subscribed to a2jmidid in Ubuntu.
Matching subscriptions: Ubunt
In the interest of time (Ubuntu Beta freeze is in one week), I've
decided to work on it here. I'll SRU it in previous supported versions.
** Also affects: a2jmidid (Ubuntu Mantic)
Importance: Undecided
Status: New
** Also affects: a2jmidid (Ubuntu Noble)
Importance: Medium
Sta
Reinaert,
The patch has been uploaded to Noble (future 24.04). Can you come up
with a simple, step-by-step procedure for testing in previous versions
and be willing to do the tests when the SRU team accepts? I have the
feeling these are fairly hardware-specific requirements and not just
anyone wil
As it turns out, we were setting $BROWSER to `sudo -H -u lubuntu firefox' all
the way up until Jammy:
https://git.lubuntu.me/Lubuntu/calamares-settings-ubuntu/src/branch/ubuntu/jammy/lubuntu/lubuntu-calamares.desktop.in
As you can see in the upstream bug that's mentioned in the upstream bug linke
** Package changed: calamares-settings-ubuntu (Ubuntu) => calamares
(Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Studio Bugs, which is subscribed to calamares in Ubuntu.
https://bugs.launchpad.net/bugs/1876950
Title:
Lubuntu Calamares install fails if loop0
Hi, thanks! You need a device that exposes two separate midi ports in
ALSA and apparently a post 5.11 kernel as ALSA changed the way they name
the ports in that case. The only device that I know of that exposes two
ports is my M-Audio Keystation 88 MK3. I'm on 22.04 so I can only test
on that one.
As you can see, we dropped fcitx from Jammy, so this bug is irrelevant in any
supported release:
https://git.lubuntu.me/Lubuntu/seed/commit/4627a4628acf738cfc8d276469aba7a6bf08fbff
** Changed in: calamares-settings-ubuntu (Ubuntu)
Status: New => Invalid
--
You received this bug notificat
Right, but the SRU team would require a test in 23.10 for the fix there.
Any chance you could partition and do a test install there when the time
comes? Either way, I don't have that device, so I'll have to rely on you
to write up the test case step-by-step here so I can write up a proper
SRU docum
*** This bug is a duplicate of bug 2048470 ***
https://bugs.launchpad.net/bugs/2048470
** Package changed: calamares-settings-ubuntu (Ubuntu) => calamares
(Ubuntu)
** This bug has been marked a duplicate of bug 2048470
Calamares crashes when using LVM
--
You received this bug notificatio
Public bug reported:
rakarrack 0.6.1-8build1 is built in -proposed but not on armhf. This
will not block migration because armhf binaries are being removed from
the release pocket, but unless addressed will regress armhf availability
of this package in 24.04 LTS.
** Affects: rakarrack (Ubuntu)
Ok, there is also this reply to consider from the developers of a2jmidid:
https://github.com/jackaudio/a2jmidid/issues/25#issuecomment-2019233806
Maybe we should hold back?
** Bug watch added: github.com/jackaudio/a2jmidid/issues #25
https://github.com/jackaudio/a2jmidid/issues/25
--
You rec
13 matches
Mail list logo
