from:"Erich Eickmeyer"

Users still experiencing this should consider upgrading to 20.04 LTS at
minimum since it contains a newer version of entangle that does not
experience this issue.

** Also affects: entangle (Ubuntu Bionic)
   Importance: Undecided
   Status: New

** Changed in: entangle (Ubuntu Bionic)
   Status: New => Triaged

** Also affects: entangle (Ubuntu Focal)
   Importance: Undecided
   Status: New

** Also affects: entangle (Ubuntu Impish)
   Importance: Undecided
   Status: New

** Also affects: entangle (Ubuntu Jammy)
   Importance: Undecided
   Status: New

** Changed in: entangle (Ubuntu Focal)
   Status: New => Invalid

** Changed in: entangle (Ubuntu Impish)
   Status: New => Invalid

** Changed in: entangle (Ubuntu Jammy)
   Status: New => Invalid

-- 
You received this bug notification because you are a member of Ubuntu
Studio Bugs, which is subscribed to entangle in Ubuntu.
Matching subscriptions: Ubuntu Studio Bugs
https://bugs.launchpad.net/bugs/1739503

Title:
  
/usr/bin/entangle:11:do_refresh_control_entry_idle:g_main_dispatch:g_main_context_dispatch:g_main_context_iterate:g_main_context_iteration

Status in entangle package in Ubuntu:
  Invalid
Status in entangle source package in Bionic:
  Triaged
Status in entangle source package in Focal:
  Invalid
Status in entangle source package in Impish:
  Invalid
Status in entangle source package in Jammy:
  Invalid

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
entangle.  This problem was most recently seen with package version 
0.7.1-1build1, the problem page at 
https://errors.ubuntu.com/problem/d7e01aa7ed812d6ff01ca5d17f53f9fff78b2f2d 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
  If you do not have access to the Ubuntu Error Tracker and are a software 
developer, you can request it at http://forms.canonical.com/reports/.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/entangle/+bug/1739503/+subscriptions


-- 
Mailing list: https://launchpad.net/~ubuntustudio-bugs
Post to : ubuntustudio-bugs@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntustudio-bugs
More help   : https://help.launchpad.net/ListHelp

[Ubuntustudio-bugs] [Bug 1716656] Re: Plugins not loading

** Changed in: entangle (Ubuntu Jammy)
 Assignee: Erich Eickmeyer  (eeickmeyer) => (unassigned)

-- 
You received this bug notification because you are a member of Ubuntu
Studio Bugs, which is subscribed to entangle in Ubuntu.
Matching subscriptions: Ubuntu Studio Bugs
https://bugs.launchpad.net/bugs/1716656

Title:
  Plugins not loading

Status in entangle package in Ubuntu:
  Fix Released
Status in entangle source package in Bionic:
  Won't Fix
Status in entangle source package in Focal:
  Won't Fix
Status in entangle source package in Impish:
  Won't Fix
Status in entangle source package in Jammy:
  Fix Released
Status in entangle package in Debian:
  Fix Released

Bug description:
  Ubuntu: desktop 17.04
  Entangle version: v0.7.1
  libgphoto2 version: v2.5.12
  Camera model: Canon EOS SL1 FW v101
  Description of problem: 
  I am having trouble loading plugin's.  On a fresh install I can not see 
plugin's in the preferences menu.  I can see that they are located in 
'/usr/share/entangle/plugins/'.  If i copy the plugin's to 
'/home/daniel/.config/entangle/plugins/' I can see them in the preferences 
menu.  But checking the box dose not allow there use.

  Install method is 'sudo apt-get install entangle'

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/entangle/+bug/1716656/+subscriptions


-- 
Mailing list: https://launchpad.net/~ubuntustudio-bugs
Post to : ubuntustudio-bugs@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntustudio-bugs
More help   : https://help.launchpad.net/ListHelp

[Ubuntustudio-bugs] [Bug 1398432] Re: Using 12.04 LTS software center install doesn't install entangle

Thank you for reporting this bug to Ubuntu.

Ubuntu 12.04 (precise) reached end-of-life on April 28, 2017.

See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases

Since this was filed against the wrong package, and due to the age of
this bug and my inability to reproduce, I'm closing this.

** Changed in: entangle (Ubuntu)
   Status: New => Won't Fix

-- 
You received this bug notification because you are a member of Ubuntu
Studio Bugs, which is subscribed to entangle in Ubuntu.
Matching subscriptions: Ubuntu Studio Bugs
https://bugs.launchpad.net/bugs/1398432

Title:
  Using 12.04 LTS software center install doesn't install entangle

Status in entangle package in Ubuntu:
  Won't Fix

Bug description:
  in a terminal 
  dpkg -L entangle
  /.
  /usr
  /usr/share
  /usr/share/doc
  /usr/share/doc/entangle
  /usr/share/doc/entangle/changelog.Debian.gz
  /usr/share/doc/entangle/copyright
  /usr/share/doc/entangle/NEWS.gz
  /usr/share/doc/entangle/README
  /usr/share/doc/entangle/README.Debian

  but there's nothing in the /usr/bin file but 
  I can load it ok from
  http://www.ubuntuupdates.org/package/getdeb_apps/precise/apps/getdeb/entangle
  using GDebi package installer

   dpkg -L entangle

  /.
  /usr
  /usr/bin
  /usr/bin/entangle
  plus many others
  it works just fine until the update manager attempts to replace it then it's 
wiped out and I'm back a square one. 
  Hopes this helps. 
  DKS

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/entangle/+bug/1398432/+subscriptions


-- 
Mailing list: https://launchpad.net/~ubuntustudio-bugs
Post to : ubuntustudio-bugs@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntustudio-bugs
More help   : https://help.launchpad.net/ListHelp

[Ubuntustudio-bugs] [Bug 1440544] Re: entangle should depends on gnome-icon-theme-symbolic

In the current version, I see adwaita-icon-theme in the recommends,
which get installed if they're available. This should suffice as it
replaces the old gnome-icon-theme. Closing this as fixed.

** Changed in: entangle (Ubuntu)
   Status: New => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Studio Bugs, which is subscribed to entangle in Ubuntu.
Matching subscriptions: Ubuntu Studio Bugs
https://bugs.launchpad.net/bugs/1440544

Title:
  entangle should depends on  gnome-icon-theme-symbolic

Status in entangle package in Ubuntu:
  Fix Released

Bug description:
  icons are not showned due to missing dependies on gnome-icon-theme-
  symbolic

  $> apt-cache depends entangle  
  entangle
   |Depends: dconf-gsettings-backend
Depends: 
  dconf-gsettings-backend
Depends: libc6
Depends: libcairo2
Depends: libgdk-pixbuf2.0-0
Depends: libgexiv2-2
Depends: libgirepository-1.0-1
Depends: libglib2.0-0
Depends: libgphoto2-6
Depends: libgphoto2-port10
Depends: libgtk-3-0
Depends: libgudev-1.0-0
Depends: liblcms2-2
Depends: libpeas-1.0-0
Depends: libraw10
Depends: libxext6
Enhances: digikam
Enhances: gimp
Enhances: gnumed-client
Conflicts: entangle:i386

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/entangle/+bug/1440544/+subscriptions


-- 
Mailing list: https://launchpad.net/~ubuntustudio-bugs
Post to : ubuntustudio-bugs@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntustudio-bugs
More help   : https://help.launchpad.net/ListHelp

[Ubuntustudio-bugs] [Bug 1716656] Re: Plugins not loading

** Bug watch added: Debian Bug tracker #1001814
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1001814

** Also affects: entangle (Debian) via
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1001814
   Importance: Unknown
   Status: Unknown

** Also affects: entangle (Ubuntu Focal)
   Importance: Undecided
   Status: New

** Also affects: entangle (Ubuntu Impish)
   Importance: Undecided
   Status: New

** Also affects: entangle (Ubuntu Bionic)
   Importance: Undecided
   Status: New

** Changed in: entangle (Ubuntu Bionic)
   Status: New => Won't Fix

** Changed in: entangle (Ubuntu Focal)
   Status: New => Won't Fix

** Changed in: entangle (Ubuntu Impish)
   Status: New => Won't Fix

-- 
You received this bug notification because you are a member of Ubuntu
Studio Bugs, which is subscribed to entangle in Ubuntu.
Matching subscriptions: Ubuntu Studio Bugs
https://bugs.launchpad.net/bugs/1716656

Title:
  Plugins not loading

Status in entangle package in Ubuntu:
  Triaged
Status in entangle source package in Bionic:
  Won't Fix
Status in entangle source package in Focal:
  Won't Fix
Status in entangle source package in Impish:
  Won't Fix
Status in entangle source package in Jammy:
  Triaged
Status in entangle package in Debian:
  Unknown

Bug description:
  Ubuntu: desktop 17.04
  Entangle version: v0.7.1
  libgphoto2 version: v2.5.12
  Camera model: Canon EOS SL1 FW v101
  Description of problem: 
  I am having trouble loading plugin's.  On a fresh install I can not see 
plugin's in the preferences menu.  I can see that they are located in 
'/usr/share/entangle/plugins/'.  If i copy the plugin's to 
'/home/daniel/.config/entangle/plugins/' I can see them in the preferences 
menu.  But checking the box dose not allow there use.

  Install method is 'sudo apt-get install entangle'

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/entangle/+bug/1716656/+subscriptions


-- 
Mailing list: https://launchpad.net/~ubuntustudio-bugs
Post to : ubuntustudio-bugs@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntustudio-bugs
More help   : https://help.launchpad.net/ListHelp

[Ubuntustudio-bugs] [Bug 1716656] Re: Plugins not loading

Matteo,

Debian import freeze is in effect. Unless this is manually sync'd (must
be requested), it won't land in Ubuntu 22.04 and won't get sync'd until
the next release cycle opens (KK). It's very late in the release cycle,
so we'll need a decent amount of justification to get this sync'd.

In general:

 * This must be a bugfix-only release for entangle, and
 * This must not include any new features.

Please reply with what you'd like to do.

** Changed in: entangle (Ubuntu)
   Status: Fix Released => Triaged

-- 
You received this bug notification because you are a member of Ubuntu
Studio Bugs, which is subscribed to entangle in Ubuntu.
Matching subscriptions: Ubuntu Studio Bugs
https://bugs.launchpad.net/bugs/1716656

Title:
  Plugins not loading

Status in entangle package in Ubuntu:
  Triaged
Status in entangle source package in Jammy:
  Triaged

Bug description:
  Ubuntu: desktop 17.04
  Entangle version: v0.7.1
  libgphoto2 version: v2.5.12
  Camera model: Canon EOS SL1 FW v101
  Description of problem: 
  I am having trouble loading plugin's.  On a fresh install I can not see 
plugin's in the preferences menu.  I can see that they are located in 
'/usr/share/entangle/plugins/'.  If i copy the plugin's to 
'/home/daniel/.config/entangle/plugins/' I can see them in the preferences 
menu.  But checking the box dose not allow there use.

  Install method is 'sudo apt-get install entangle'

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/entangle/+bug/1716656/+subscriptions


-- 
Mailing list: https://launchpad.net/~ubuntustudio-bugs
Post to : ubuntustudio-bugs@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntustudio-bugs
More help   : https://help.launchpad.net/ListHelp

[Ubuntustudio-bugs] [Bug 1716656] Re: Plugins not loading

This was just given the green light to sync to Jammy, so as soon as I
see it land, I'll do the sync.

** Changed in: entangle (Ubuntu Jammy)
   Status: Triaged => In Progress

** Changed in: entangle (Ubuntu Jammy)
 Assignee: (unassigned) => Erich Eickmeyer  (eeickmeyer)

** Changed in: entangle (Ubuntu Jammy)
   Importance: Undecided => High

-- 
You received this bug notification because you are a member of Ubuntu
Studio Bugs, which is subscribed to entangle in Ubuntu.
Matching subscriptions: Ubuntu Studio Bugs
https://bugs.launchpad.net/bugs/1716656

Title:
  Plugins not loading

Status in entangle package in Ubuntu:
  In Progress
Status in entangle source package in Bionic:
  Won't Fix
Status in entangle source package in Focal:
  Won't Fix
Status in entangle source package in Impish:
  Won't Fix
Status in entangle source package in Jammy:
  In Progress
Status in entangle package in Debian:
  Fix Released

Bug description:
  Ubuntu: desktop 17.04
  Entangle version: v0.7.1
  libgphoto2 version: v2.5.12
  Camera model: Canon EOS SL1 FW v101
  Description of problem: 
  I am having trouble loading plugin's.  On a fresh install I can not see 
plugin's in the preferences menu.  I can see that they are located in 
'/usr/share/entangle/plugins/'.  If i copy the plugin's to 
'/home/daniel/.config/entangle/plugins/' I can see them in the preferences 
menu.  But checking the box dose not allow there use.

  Install method is 'sudo apt-get install entangle'

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/entangle/+bug/1716656/+subscriptions


-- 
Mailing list: https://launchpad.net/~ubuntustudio-bugs
Post to : ubuntustudio-bugs@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntustudio-bugs
More help   : https://help.launchpad.net/ListHelp

[Ubuntustudio-bugs] [Bug 1716656] Re: Plugins not loading

** Also affects: entangle (Ubuntu Jammy)
   Importance: Undecided
   Status: Triaged

-- 
You received this bug notification because you are a member of Ubuntu
Studio Bugs, which is subscribed to entangle in Ubuntu.
Matching subscriptions: Ubuntu Studio Bugs
https://bugs.launchpad.net/bugs/1716656

Title:
  Plugins not loading

Status in entangle package in Ubuntu:
  Triaged
Status in entangle source package in Jammy:
  Triaged

Bug description:
  Ubuntu: desktop 17.04
  Entangle version: v0.7.1
  libgphoto2 version: v2.5.12
  Camera model: Canon EOS SL1 FW v101
  Description of problem: 
  I am having trouble loading plugin's.  On a fresh install I can not see 
plugin's in the preferences menu.  I can see that they are located in 
'/usr/share/entangle/plugins/'.  If i copy the plugin's to 
'/home/daniel/.config/entangle/plugins/' I can see them in the preferences 
menu.  But checking the box dose not allow there use.

  Install method is 'sudo apt-get install entangle'

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/entangle/+bug/1716656/+subscriptions


-- 
Mailing list: https://launchpad.net/~ubuntustudio-bugs
Post to : ubuntustudio-bugs@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntustudio-bugs
More help   : https://help.launchpad.net/ListHelp

[Ubuntustudio-bugs] [Bug 2033618] Re: Please update Blender to 3.6.2

2023-09-05 Thread Erich Eickmeyer

Nathan, Armv7 (armhf) fails and is expected. It's been removed from the
archive because blender no longer supports 32-bit architectures.

-- 
You received this bug notification because you are a member of Ubuntu
Studio Bugs, which is subscribed to blender in Ubuntu.
Matching subscriptions: ubuntustudio-bugs: blender
https://bugs.launchpad.net/bugs/2033618

Title:
  Please update Blender to 3.6.2

Status in blender package in Ubuntu:
  Confirmed

Bug description:
  The Blender you get in Ubuntu with `sudo apt install blender` is
  awful. It gets slower and slower after two hours of working. Crashes
  on large files. And won't render, giving the error: "Built without
  Open Image Denoise". If you instead use the latest Blender LTS from
  the Blender website everything works perfectly.

  But you can't install that Blender version automatically, you have to
  take longer doing the download and extract manually.

  Please keep your APT packages up to date with the latest version of
  software in Ubuntu. Otherwise this OS is not trustworthy and wastes
  users time.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.04
  Package: blender 3.4.1+dfsg-2build3
  ProcVersionSignature: Ubuntu 6.2.0-1011.11-lowlatency 6.2.15
  Uname: Linux 6.2.0-1011-lowlatency x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset 
nvidia
  ApportVersion: 2.26.1-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Aug 31 10:11:51 2023
  InstallationDate: Installed on 2023-07-27 (34 days ago)
  InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 
(20230223)
  ProcEnviron:
   LANG=en_ZA.UTF-8
   LANGUAGE=en_ZA:en
   PATH=(custom, no user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  SourcePackage: blender
  UpgradeStatus: Upgraded to lunar on 2023-07-27 (34 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/blender/+bug/2033618/+subscriptions


-- 
Mailing list: https://launchpad.net/~ubuntustudio-bugs
Post to : ubuntustudio-bugs@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntustudio-bugs
More help   : https://help.launchpad.net/ListHelp

[Ubuntustudio-bugs] [Bug 2033618] Re: Please update Blender to 3.6.2

2023-09-05 Thread Erich Eickmeyer

To be fair, we're working on this for Mantic Minotaur (future 23.10) and
it's not likely to be backported to 23.04, so if you need 3.6.2 the snap
is probably the best way to go or wait and upgrade to 23.10 when it is
released in October.

-- 
You received this bug notification because you are a member of Ubuntu
Studio Bugs, which is subscribed to blender in Ubuntu.
Matching subscriptions: ubuntustudio-bugs: blender
https://bugs.launchpad.net/bugs/2033618

Title:
  Please update Blender to 3.6.2

Status in blender package in Ubuntu:
  Confirmed

Bug description:
  The Blender you get in Ubuntu with `sudo apt install blender` is
  awful. It gets slower and slower after two hours of working. Crashes
  on large files. And won't render, giving the error: "Built without
  Open Image Denoise". If you instead use the latest Blender LTS from
  the Blender website everything works perfectly.

  But you can't install that Blender version automatically, you have to
  take longer doing the download and extract manually.

  Please keep your APT packages up to date with the latest version of
  software in Ubuntu. Otherwise this OS is not trustworthy and wastes
  users time.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.04
  Package: blender 3.4.1+dfsg-2build3
  ProcVersionSignature: Ubuntu 6.2.0-1011.11-lowlatency 6.2.15
  Uname: Linux 6.2.0-1011-lowlatency x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset 
nvidia
  ApportVersion: 2.26.1-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Aug 31 10:11:51 2023
  InstallationDate: Installed on 2023-07-27 (34 days ago)
  InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 
(20230223)
  ProcEnviron:
   LANG=en_ZA.UTF-8
   LANGUAGE=en_ZA:en
   PATH=(custom, no user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  SourcePackage: blender
  UpgradeStatus: Upgraded to lunar on 2023-07-27 (34 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/blender/+bug/2033618/+subscriptions


-- 
Mailing list: https://launchpad.net/~ubuntustudio-bugs
Post to : ubuntustudio-bugs@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntustudio-bugs
More help   : https://help.launchpad.net/ListHelp

[Ubuntustudio-bugs] [Bug 2033618] Re: Please update Blender to 3.6.2

2023-09-05 Thread Erich Eickmeyer

** Also affects: blender (Ubuntu Mantic)
   Importance: Undecided
 Assignee: Nathan Teodosio (nteodosio)
   Status: Fix Committed

** Also affects: blender (Ubuntu Lunar)
   Importance: Undecided
   Status: New

** Changed in: blender (Ubuntu Lunar)
   Status: New => Won't Fix

-- 
You received this bug notification because you are a member of Ubuntu
Studio Bugs, which is subscribed to blender in Ubuntu.
Matching subscriptions: ubuntustudio-bugs: blender
https://bugs.launchpad.net/bugs/2033618

Title:
  Please update Blender to 3.6.2

Status in blender package in Ubuntu:
  Fix Committed
Status in blender source package in Lunar:
  Won't Fix
Status in blender source package in Mantic:
  Fix Committed

Bug description:
  The Blender you get in Ubuntu with `sudo apt install blender` is
  awful. It gets slower and slower after two hours of working. Crashes
  on large files. And won't render, giving the error: "Built without
  Open Image Denoise". If you instead use the latest Blender LTS from
  the Blender website everything works perfectly.

  But you can't install that Blender version automatically, you have to
  take longer doing the download and extract manually.

  Please keep your APT packages up to date with the latest version of
  software in Ubuntu. Otherwise this OS is not trustworthy and wastes
  users time.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.04
  Package: blender 3.4.1+dfsg-2build3
  ProcVersionSignature: Ubuntu 6.2.0-1011.11-lowlatency 6.2.15
  Uname: Linux 6.2.0-1011-lowlatency x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset 
nvidia
  ApportVersion: 2.26.1-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Aug 31 10:11:51 2023
  InstallationDate: Installed on 2023-07-27 (34 days ago)
  InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 
(20230223)
  ProcEnviron:
   LANG=en_ZA.UTF-8
   LANGUAGE=en_ZA:en
   PATH=(custom, no user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  SourcePackage: blender
  UpgradeStatus: Upgraded to lunar on 2023-07-27 (34 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/blender/+bug/2033618/+subscriptions


-- 
Mailing list: https://launchpad.net/~ubuntustudio-bugs
Post to : ubuntustudio-bugs@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntustudio-bugs
More help   : https://help.launchpad.net/ListHelp

[Ubuntustudio-bugs] [Bug 1681111] Re: Wacom Bamboo Pen not working (Freezes Ubuntu )17.04

2023-09-01 Thread Erich Eickmeyer

Thank you for reporting this bug to Ubuntu.

Ubuntu 17.04 (zesty) reached end-of-life on January 13, 2018.

See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases

Moreover, this bug report is missing any useful logs or data that might
help anybody fix this. Therefore, this bug is being closed, Please open
a new bug against a currently supported version of this package if you
test and this is a problem.

** Changed in: xf86-input-wacom (Ubuntu)
   Status: New => Won't Fix

-- 
You received this bug notification because you are a member of Ubuntu
Studio Bugs, which is subscribed to xf86-input-wacom in Ubuntu.
Matching subscriptions: Ubuntu Studio Bugs
https://bugs.launchpad.net/bugs/168

Title:
  Wacom Bamboo Pen not working (Freezes Ubuntu )17.04

Status in xf86-input-wacom package in Ubuntu:
  Won't Fix

Bug description:
  After upgrading from 16.10 to 17.04 , Wacom Bamboo Pen is not responding if 
it's already plugged in before opening Gimp, Krita or Raw Therapee. If it's 
connected after opening one of these programs it freezes all system.
  Inkscape seems to be the only one working so far.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xf86-input-wacom/+bug/168/+subscriptions


-- 
Mailing list: https://launchpad.net/~ubuntustudio-bugs
Post to : ubuntustudio-bugs@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntustudio-bugs
More help   : https://help.launchpad.net/ListHelp

[Ubuntustudio-bugs] [Bug 2033547] Re: Unable to run Install Lubuntu from desktop

2023-08-30 Thread Erich Eickmeyer

This is likely due to the new polkitd dropping support for the old pkla
(polkit local authority) files. Therefore, the lubuntu desktop seed
likely needs polkitd-pkla seeded in order to use those old pkla files to
avoid this.

** Also affects: lubuntu-meta (Ubuntu)
   Importance: Undecided
   Status: New

-- 
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/2033547

Title:
  Unable to run Install Lubuntu from desktop

Status in calamares package in Ubuntu:
  New
Status in lubuntu-meta package in Ubuntu:
  New

Bug description:
  Testing Lubuntu daily ISO dated 30.08.2023

  
  Unable to run Install Lubuntu from desktop as the installer requires 
authentication (password).
  However was able to run "Install system" from the menu but this resulted in a 
crash and failed installation.

  Running "ubuntu-bug" also required password but but seemed to run in
  background.

  see attached screenshot

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: calamares 3.3.0-alpha2-0ubuntu4
  ProcVersionSignature: Ubuntu 6.3.0-7.7-generic 6.3.5
  Uname: Linux 6.3.0-7-generic x86_64
  .etc.calamares.modules.after_bootloader_context.conf:
   ---
   dontChroot: false
   timeout: 120
   firmwareType:
   "*": "-rm ${ROOT}/home/${USER}/Desktop/lubuntu-calamares.desktop"
  .etc.calamares.modules.finished.conf:
   ---
   restartNowMode: user-checked
   restartNowCommand: "systemctl -i reboot"
  .etc.calamares.modules.fstab.conf:
   crypttabOptions: luks,keyscript=/bin/cat
   efiMountOptions: umask=0077
  .etc.calamares.modules.shellprocess_logs.conf:
   ---
   dontChroot: true
   timeout: 30
   script:
   - calamares-logs-helper ${ROOT}
  .etc.calamares.modules.unpackfs.conf:
   ---
   unpack:
   -   source: "/cdrom/casper/filesystem.squashfs"
   sourcefs: "squashfs"
   destination: ""
  ApportVersion: 2.27.0-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: pass
  CasperVersion: 1.482
  CurrentDesktop: LXQt
  Date: Wed Aug 30 17:40:18 2023
  LiveMediaBuild: Lubuntu 23.10 "Mantic Minotaur" - Daily amd64 (20230830)
  RelatedPackageVersions:
   calamares-settings-ubuntu-common 1:23.10.1
   calamares-settings-lubuntu   1:23.10.1
   xfsprogs 6.3.0-1ubuntu1
   btrfs-progs  6.3.2-1
  SourcePackage: calamares
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/calamares/+bug/2033547/+subscriptions


-- 
Mailing list: https://launchpad.net/~ubuntustudio-bugs
Post to : ubuntustudio-bugs@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntustudio-bugs
More help   : https://help.launchpad.net/ListHelp

[Ubuntustudio-bugs] [Bug 2033440] Re: ubuntustudio-installer: error occurred while applying changes

2023-08-29 Thread Erich Eickmeyer

The problem is occurring because ubuntustudio-pulseaudio-config is
incompatible with the ubuntu-desktop metapackage as, for some reason,
ubuntu-desktop has pipewire-audio as a hard dependency which has
pipewire-alsa as a hard dependency. This means that the bug is really in
ubuntu-meta and not in ubuntustudio-installer due to a package conflict,
and a hard dependency in a metapackage that shouldn't exist.

It's unlikely this will be fixed in 23.04, but it might get fixed in
time for 23.10, but we'll see. I can make no guarantees as I only
oversee Ubuntu Studio. Unfortunately, Ubuntu Desktop users will have to
remain on PipeWire and not use the ubuntustudio-pulseaudio-config
package due to this discrepancy. This also means that Ubuntu Desktop
23.04 cannot and should not be used for professional audio.

** Package changed: ubuntustudio-installer (Ubuntu) => ubuntu-meta
(Ubuntu)

** Also affects: ubuntu-meta (Ubuntu Lunar)
   Importance: Undecided
   Status: New

** Also affects: ubuntu-meta (Ubuntu Mantic)
   Importance: Undecided
   Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Studio Bugs, which is subscribed to ubuntustudio-installer in Ubuntu.
https://bugs.launchpad.net/bugs/2033440

Title:
  ubuntustudio-installer: error occurred while applying changes

Status in ubuntu-meta package in Ubuntu:
  New
Status in ubuntu-meta source package in Lunar:
  New
Status in ubuntu-meta source package in Mantic:
  New

Bug description:
  
  I have installed successfully the standard Ubuntu 23.04 (on a 500 GB external 
USB drive). Immediately after the installation, I have also installed with apt 
the "ubuntustudio-installer" package.

  In the dialog provided by the ubuntustudio-installer, I have selected
  the following metapackages:

  - linux-lowlatency
  - ubuntustudio-lowlatency-settings
  - ubuntustudio-performance-tweaks
  - ubuntustudio-audio
  - ubuntu-pulseaudio-config

  and pressed "Modify installed Package Selection"

  After a while a "qaptbatch" dialog has appeared with title

  "Commit Error"

  and message

  "An error occurred while applying changes"

  So the installation has failed. Then I have tried to manually install
  each metapackage in the list above with apt and every package was
  installed successfully.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/2033440/+subscriptions


-- 
Mailing list: https://launchpad.net/~ubuntustudio-bugs
Post to : ubuntustudio-bugs@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntustudio-bugs
More help   : https://help.launchpad.net/ListHelp

[Ubuntustudio-bugs] [Bug 1925221] Re: Not possible to select language on Ubuntu Studio Live Session

2023-09-18 Thread Erich Eickmeyer

So, here's where we're at with this:

Ubiquity is back in Ubuntu Studio and we're using the GTK version as of
23.10 which, for ubuntustudio-meta, fixes this bug. However, for 24.04
LTS we will have to switch to subiquity with the flutter-based frontend
as Ubuiquity must be sunsetted as Canonical cannot support it for
another LTS along with subiquity.

As far as fixing in previous releases, it's not so much as "won't fix"
as we can't fix. Therefore, I'm marking as such.

** Also affects: ubiquity (Ubuntu Jammy)
   Importance: Undecided
   Status: New

** Also affects: ubuntustudio-meta (Ubuntu Jammy)
   Importance: Undecided
   Status: New

** Also affects: calamares (Ubuntu Jammy)
   Importance: Undecided
   Status: New

** Also affects: ubiquity (Ubuntu Mantic)
   Importance: Medium
   Status: New

** Also affects: ubuntustudio-meta (Ubuntu Mantic)
   Importance: Medium
   Status: Triaged

** Also affects: calamares (Ubuntu Mantic)
   Importance: Wishlist
   Status: Triaged

** Also affects: ubiquity (Ubuntu Lunar)
   Importance: Undecided
   Status: New

** Also affects: ubuntustudio-meta (Ubuntu Lunar)
   Importance: Undecided
   Status: New

** Also affects: calamares (Ubuntu Lunar)
   Importance: Undecided
   Status: New

** Changed in: ubuntustudio-meta (Ubuntu Jammy)
   Status: New => Won't Fix

** Changed in: ubuntustudio-meta (Ubuntu Lunar)
   Status: New => Won't Fix

** Changed in: ubuntustudio-meta (Ubuntu Mantic)
   Status: Triaged => Fix Released

** No longer affects: ubiquity (Ubuntu)

** No longer affects: ubiquity (Ubuntu Jammy)

** No longer affects: ubiquity (Ubuntu Lunar)

** No longer affects: ubiquity (Ubuntu Mantic)

** Changed in: calamares (Ubuntu Mantic)
   Status: Triaged => Invalid

** Changed in: calamares (Ubuntu Lunar)
   Status: New => Won't Fix

** Changed in: calamares (Ubuntu Jammy)
   Status: New => Won't Fix

-- 
You received this bug notification because you are a member of Ubuntu
Studio Bugs, which is subscribed to ubuntustudio-meta in Ubuntu.
Matching subscriptions: UbuntuStudioPackages
https://bugs.launchpad.net/bugs/1925221

Title:
  Not possible to select language on Ubuntu Studio Live Session

Status in Ubuntu Manual Tests:
  Invalid
Status in calamares package in Ubuntu:
  Invalid
Status in ubuntustudio-meta package in Ubuntu:
  Fix Released
Status in calamares source package in Jammy:
  Won't Fix
Status in ubuntustudio-meta source package in Jammy:
  Won't Fix
Status in calamares source package in Lunar:
  Won't Fix
Status in ubuntustudio-meta source package in Lunar:
  Won't Fix
Status in calamares source package in Mantic:
  Invalid
Status in ubuntustudio-meta source package in Mantic:
  Fix Released

Bug description:
  Hi,

  I just tried running the Hirsute Final image for Ubuntu Studio in a
  Virtual Box machine and it is not possible to select a language as
  stated in the Live Session Test Case.

  Expected behaviour (as stated in the test case):
  1. Boot Screen
  2. Ubiquity - select language
  3. Click Try Ubuntu

  Actual behaviour:
  1. Grub menu - I chose Ubuntu Studio (not clear it was for the live session - 
but the other options were definitely not).
  2. Boots successfully into the Live Session, but everything is in English.

  This is probably not the best experience for a non-English speaker to
  "try Ubuntu Studio".

  Regards,

  Ross
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu65
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  ubuntu-studio   2221 F pulseaudio
   /dev/snd/controlC0:  ubuntu-studio   2221 F pulseaudio
  CRDA: N/A
  CasperMD5CheckResult: pass
  CasperVersion: 1.461
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 21.04
  LiveMediaBuild: Ubuntu-Studio 21.04 "Hirsute Hippo" - Release amd64 (20210420)
  MachineType: Hewlett-Packard Compaq CQ58 Notebook PC
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  Package: linux (not installed)
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz 
file=/cdrom/preseed/ubuntustudio.seed maybe-ubiquity quiet splash ---
  ProcVersionSignature: Ubuntu 5.11.0-16.17-lowlatency 5.11.12
  RelatedPackageVersions:
   linux-restricted-modules-5.11.0-16-lowlatency N/A
   linux-backports-modules-5.11.0-16-lowlatency  N/A
   linux-firmware1.197
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  Tags:  hirsute
  Uname: Linux 5.11.0-16-lowlatency x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm audio cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 06/26/2013
  dmi.bios.release: 15.55
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.37
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 188B
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 69.18
  dmi.chassis.asset.tag:

[Ubuntustudio-bugs] [Bug 2037787] [NEW] New upstream bugfix release 2.5.7

2023-09-30 Thread Erich Eickmeyer

Public bug reported:

The author of Carla has released a new bugfix for Carla 2.5.7 indicating
a bugfix release. This has the following fixes:

 * Allow configuration of Carla client name when headless (via 
CARLA_CLIENT_NAME env var)
 * Fix save missing LV2 files
 * Fix some wine bridge details

This should have been a smaller diff but, per my conversations with the
author, a file was erroneously cherry-picked from the development branch
and is not used during build time
(source/frontend/pluginlist/pluginlistdialog.cpp), so it can be safely
ignored from the diff.

As such, this contains no new features, but should be included to remove
important bugs.

** Affects: carla (Ubuntu)
 Importance: High
 Assignee: Erich Eickmeyer (eeickmeyer)
 Status: In Progress

** Changed in: carla (Ubuntu)
Milestone: None => ubuntu-23.10

-- 
You received this bug notification because you are a member of Ubuntu
Studio Bugs, which is subscribed to carla in Ubuntu.
https://bugs.launchpad.net/bugs/2037787

Title:
  New upstream bugfix release 2.5.7

Status in carla package in Ubuntu:
  In Progress

Bug description:
  The author of Carla has released a new bugfix for Carla 2.5.7
  indicating a bugfix release. This has the following fixes:

   * Allow configuration of Carla client name when headless (via 
CARLA_CLIENT_NAME env var)
   * Fix save missing LV2 files
   * Fix some wine bridge details

  This should have been a smaller diff but, per my conversations with
  the author, a file was erroneously cherry-picked from the development
  branch and is not used during build time
  (source/frontend/pluginlist/pluginlistdialog.cpp), so it can be safely
  ignored from the diff.

  As such, this contains no new features, but should be included to
  remove important bugs.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/carla/+bug/2037787/+subscriptions


-- 
Mailing list: https://launchpad.net/~ubuntustudio-bugs
Post to : ubuntustudio-bugs@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntustudio-bugs
More help   : https://help.launchpad.net/ListHelp

[Ubuntustudio-bugs] [Bug 2037787] Re: New upstream bugfix release 2.5.7

2023-09-30 Thread Erich Eickmeyer

** Changed in: carla (Ubuntu)
   Status: In Progress => Fix Committed

** Tags added: mantic

-- 
You received this bug notification because you are a member of Ubuntu
Studio Bugs, which is subscribed to carla in Ubuntu.
https://bugs.launchpad.net/bugs/2037787

Title:
  New upstream bugfix release 2.5.7

Status in carla package in Ubuntu:
  Fix Committed

Bug description:
  The author of Carla has released a new bugfix for Carla 2.5.7
  indicating a bugfix release. This has the following fixes:

   * Allow configuration of Carla client name when headless (via 
CARLA_CLIENT_NAME env var)
   * Fix save missing LV2 files
   * Fix some wine bridge details

  This should have been a smaller diff but, per my conversations with
  the author, a file was erroneously cherry-picked from the development
  branch and is not used during build time
  (source/frontend/pluginlist/pluginlistdialog.cpp), so it can be safely
  ignored from the diff.

  As such, this contains no new features, but should be included to
  remove important bugs.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/carla/+bug/2037787/+subscriptions


-- 
Mailing list: https://launchpad.net/~ubuntustudio-bugs
Post to : ubuntustudio-bugs@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntustudio-bugs
More help   : https://help.launchpad.net/ListHelp

[Ubuntustudio-bugs] [Bug 1964404] Re: lsp-plugins 1.1.31 FTBFS on armhf

2023-09-18 Thread Erich Eickmeyer

** Changed in: lsp-plugins (Ubuntu)
   Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Studio Bugs, which is subscribed to lsp-plugins in Ubuntu.
https://bugs.launchpad.net/bugs/1964404

Title:
  lsp-plugins 1.1.31 FTBFS on armhf

Status in lsp-plugins package in Ubuntu:
  Fix Released
Status in lsp-plugins package in Debian:
  Fix Released

Bug description:
  lsp-plugins 1.1.31 FTBFS on armhf

  Reported to Debian and upstream developer

  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1003904
  https://github.com/sadko4u/lsp-plugins/issues/222

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lsp-plugins/+bug/1964404/+subscriptions


-- 
Mailing list: https://launchpad.net/~ubuntustudio-bugs
Post to : ubuntustudio-bugs@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntustudio-bugs
More help   : https://help.launchpad.net/ListHelp

[Ubuntustudio-bugs] [Bug 303293] Re: Audacity fails to import its own .aup file, makes X use lots of CPU

2023-08-28 Thread Erich Eickmeyer

Hi Reuben,

It's mostly copypasta, to be honest. Just trying to close bugs that
aren't relevant anymore, especially considering we have bugs that have
decade-old stacktraces that don't help solve problems anymore. Rest
assured, though, the bug is most likely fixed in the latest versions of
Audacity, just not this particular version of this package which isn't
even available in Ubuntu's repositories anymore, but a much newer
version.

Also, to be honest, the copypasta is meant for newer bugs that are filed
against these old packages, so it's possible that some better wording
could be created.

Thanks.

-- 
You received this bug notification because you are a member of Ubuntu
Studio Bugs, which is subscribed to audacity in Ubuntu.
Matching subscriptions: Ubuntu Studio Bugs
https://bugs.launchpad.net/bugs/303293

Title:
  Audacity fails to import its own .aup file, makes X use lots of CPU

Status in audacity package in Ubuntu:
  Won't Fix

Bug description:
  Binary package hint: audacity

  I opened a .aup file copied from another computer, and Audacity presents
  a dialog labelled

  "Inspecting project file data..."

  which does not seem to progress. There is about 1Gb of sound data
  files.

  Audacity consumes about 10% of CPU, and the X server about 85% while
  this is happening; if I kill audacity, the X usage goes back to normal
  (roughly 0%).

  ProblemType: Bug
  Architecture: i386
  DistroRelease: Ubuntu 8.10
  Package: audacity 1.3.5-2
  ProcEnviron:
   SHELL=/bin/bash
   
PATH=/usr/local/sbin:/sbin:/usr/sbin:/usr/NX/bin:/usr/local/epocemx/bin:/home/username/bin:/home/username/local/i686/bin:/home/username/local/bin:/home/username/.luarocks/bin:/home/username/Work/Adsensus/svn/nancy/trunk:/home/username/Work/Adsensus/svn/adsensus/trunk:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
   LANG=en_GB.UTF-8
  SourcePackage: audacity
  Uname: Linux 2.6.24-21-generic i686

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/audacity/+bug/303293/+subscriptions


-- 
Mailing list: https://launchpad.net/~ubuntustudio-bugs
Post to : ubuntustudio-bugs@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntustudio-bugs
More help   : https://help.launchpad.net/ListHelp

[Ubuntustudio-bugs] [Bug 1969827] Re: Studio Controls doesn't actually switch to FFADO

2022-04-21 Thread Erich Eickmeyer 

** Description changed:

+ [Impact]
+ 
+  * Users of Studio Controls, specifically Ubuntu Studio users using
+ Firewire audio interfaces, are running into issues where using Studio
+ Controls to switch to the FFADO driver as provided by libffado (as
+ opposed to the ALSA firewire driver) are unable to do so.
+ 
+  * The dropdown menu in Studio Controls that switches between the two is
+ supposed to add a blacklist item into /etc/modprobe.d to blacklist the
+ ALSA Firewire driver, which is in direct conflict with the FFADO driver
+ required by some Firewire audio interfaces and must be blacklisted.
+ Currently, this dropdown menu has no effect.
+ 
+  * The uploaded package fixes this by refactoring the copying mechanism.
+ This has already been fixed in a future release of Studio Controls.
+ 
+ [Test Plan]
+ 
+  * Launch Studio Controls
+ 
+  * In the System Tweaks tab, switch "FireWire Module select (reboot to
+ switch):) menu to "Use FFADO FireWire Modules"
+ 
+  * Reboot
+ 
+  * Login, launch Studio Controls
+ 
+  * Notice FireWire Module Select is back on ALSA.
+ 
+  * 'ls /etc/modprobe.d/' will not show 'blacklist-studio.conf'
+ 
+  * Expected behavior: FireWire Module select should be on FFADO and
+ 'blacklist-studio.conf' should exist in '/etc/modprobe.d/'
+ 
+ [Where problems could occur]
+ 
+  * Although great care has been taken to avoid this, the 
'blacklist-studio.conf' file could get stuck and remain blacklisting ALSA 
firewire modules. If this does cause such a regression, a further upload will 
fix this. However, this is unlikely as it merely invokes code that was not 
being invoked before that already existed as this is merely correcting a 
regression.
+
+ [Other Info]
+  
+  * Original Description:
+ 
  Choosing the drop-down to switch the FireWire module from ALSA to FFADO
  doesn't appear to actually do anything.
  
  No blacklist-studio.conf file ever gets created in /etc/modprobe.d.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: studio-controls 2.3.1-0ubuntu1
  ProcVersionSignature: Ubuntu 5.15.0-24.24-lowlatency 5.15.30
  Uname: Linux 5.15.0-24-lowlatency x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: KDE
  Date: Thu Apr 21 20:07:06 2022
  InstallationDate: Installed on 2022-04-20 (1 days ago)
  InstallationMedia: Ubuntu-Studio 22.04 LTS "Jammy Jellyfish" - Beta amd64 
(20220329.1)
  PackageArchitecture: all
  SourcePackage: studio-controls
  UpgradeStatus: No upgrade log present (probably fresh install)

-- 
You received this bug notification because you are a member of Ubuntu
Studio Bugs, which is subscribed to studio-controls in Ubuntu.
https://bugs.launchpad.net/bugs/1969827

Title:
  Studio Controls doesn't actually switch to FFADO

Status in studio-controls package in Ubuntu:
  New

Bug description:
  [Impact]

   * Users of Studio Controls, specifically Ubuntu Studio users using
  Firewire audio interfaces, are running into issues where using Studio
  Controls to switch to the FFADO driver as provided by libffado (as
  opposed to the ALSA firewire driver) are unable to do so.

   * The dropdown menu in Studio Controls that switches between the two
  is supposed to add a blacklist item into /etc/modprobe.d to blacklist
  the ALSA Firewire driver, which is in direct conflict with the FFADO
  driver required by some Firewire audio interfaces and must be
  blacklisted. Currently, this dropdown menu has no effect.

   * The uploaded package fixes this by refactoring the copying
  mechanism. This has already been fixed in a future release of Studio
  Controls.

  [Test Plan]

   * Launch Studio Controls

   * In the System Tweaks tab, switch "FireWire Module select (reboot to
  switch):) menu to "Use FFADO FireWire Modules"

   * Reboot

   * Login, launch Studio Controls

   * Notice FireWire Module Select is back on ALSA.

   * 'ls /etc/modprobe.d/' will not show 'blacklist-studio.conf'

   * Expected behavior: FireWire Module select should be on FFADO and
  'blacklist-studio.conf' should exist in '/etc/modprobe.d/'

  [Where problems could occur]

   * Although great care has been taken to avoid this, the 
'blacklist-studio.conf' file could get stuck and remain blacklisting ALSA 
firewire modules. If this does cause such a regression, a further upload will 
fix this. However, this is unlikely as it merely invokes code that was not 
being invoked before that already existed as this is merely correcting a 
regression.
 
  [Other Info]
   
   * Original Description:

  Choosing the drop-down to switch the FireWire module from ALSA to
  FFADO doesn't appear to actually do anything.

  No blacklist-studio.conf file ever gets created in /etc/modprobe.d.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: studio-controls 2.3.1-0ubuntu1
  ProcVersionSignature: Ubuntu 5.15.0-24.24-lowlatency 5.15.30
  Uname: Linux 5.15.0-24-lowlatency x86_64

[Ubuntustudio-bugs] [Bug 1969788] Re: Carla can't find plugins in plugin directories located in the user's home

2022-04-21 Thread Erich Eickmeyer 

** Changed in: ubuntustudio-menu-add
   Status: New => Invalid

** Changed in: ubuntustudio-menu-add
 Assignee: Erich Eickmeyer  (eeickmeyer) => (unassigned)

-- 
You received this bug notification because you are a member of Ubuntu
Studio Bugs, which is subscribed to The Ubuntu Studio Project.
Matching subscriptions: UbuntuStudio Bugs
https://bugs.launchpad.net/bugs/1969788

Title:
  Carla can't find plugins in plugin directories located in the user's
  home

Status in Ubuntu Studio Menu Add:
  Invalid

Bug description:
  In the LV2 location in my home directory .lv2 I have the following
  plugin:

  ➜ ls ~/.lv2   
  librnnoise_lv2.so

  ${HOME}/.lv2 is configured in Carla as a search path.

  In the Add Plugin dialog for Carla if I search for noise nothing shows
  up.

  This worked fine previously on 21.10.

  Release notes for Carla 2.4.3 [1] include this line: Fix plugin search
  (regression from 2.4.2)

  Ubuntu Studio 22.04 currently has the bugged version:

  ➜ carla --version
  Using Carla version 2.4.2

  [1] https://github.com/falkTX/Carla/releases/tag/v2.4.3

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntustudio-menu-add/+bug/1969788/+subscriptions


-- 
Mailing list: https://launchpad.net/~ubuntustudio-bugs
Post to : ubuntustudio-bugs@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntustudio-bugs
More help   : https://help.launchpad.net/ListHelp

[Ubuntustudio-bugs] [Bug 1969798] Re: Carla can't find plugins in plugin directories located in the user's home

2022-04-21 Thread Erich Eickmeyer 

** Changed in: carla (Ubuntu)
 Assignee: (unassigned) => Erich Eickmeyer  (eeickmeyer)

** Changed in: carla (Ubuntu)
   Importance: Undecided => High

** Also affects: carla (Ubuntu Jammy)
   Importance: High
 Assignee: Erich Eickmeyer  (eeickmeyer)
   Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Studio Bugs, which is subscribed to carla in Ubuntu.
https://bugs.launchpad.net/bugs/1969798

Title:
  Carla can't find plugins in plugin directories located in the user's
  home

Status in carla package in Ubuntu:
  New
Status in carla source package in Jammy:
  New

Bug description:
  In the LV2 location in my home directory .lv2 I have the following
  plugin:

  ➜ ls ~/.lv2
  librnnoise_lv2.so

  ${HOME}/.lv2 is configured in Carla as a search path.

  In the Add Plugin dialog for Carla if I search for noise nothing shows
  up.

  This worked fine previously on 21.10.

  Release notes for Carla 2.4.3 [1] include this line: Fix plugin search
  (regression from 2.4.2)

  Ubuntu Studio 22.04 currently has the bugged version:

  ➜ carla --version
  Using Carla version 2.4.2

  [1] https://github.com/falkTX/Carla/releases/tag/v2.4.3

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: carla 2.4.2-0ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-24.24-lowlatency 5.15.30
  Uname: Linux 5.15.0-24-lowlatency x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: KDE
  Date: Thu Apr 21 15:41:13 2022
  InstallationDate: Installed on 2022-04-20 (1 days ago)
  InstallationMedia: Ubuntu-Studio 22.04 LTS "Jammy Jellyfish" - Beta amd64 
(20220329.1)
  SourcePackage: carla
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/carla/+bug/1969798/+subscriptions


-- 
Mailing list: https://launchpad.net/~ubuntustudio-bugs
Post to : ubuntustudio-bugs@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntustudio-bugs
More help   : https://help.launchpad.net/ListHelp

[Ubuntustudio-bugs] [Bug 1969798] Re: Carla can't find plugins in plugin directories located in the user's home

** Changed in: carla (Ubuntu Jammy)
   Status: New => Triaged

-- 
You received this bug notification because you are a member of Ubuntu
Studio Bugs, which is subscribed to carla in Ubuntu.
https://bugs.launchpad.net/bugs/1969798

Title:
  Carla can't find plugins in plugin directories located in the user's
  home

Status in carla package in Ubuntu:
  Triaged
Status in carla source package in Jammy:
  Triaged

Bug description:
  In the LV2 location in my home directory .lv2 I have the following
  plugin:

  ➜ ls ~/.lv2
  librnnoise_lv2.so

  ${HOME}/.lv2 is configured in Carla as a search path.

  In the Add Plugin dialog for Carla if I search for noise nothing shows
  up.

  This worked fine previously on 21.10.

  Release notes for Carla 2.4.3 [1] include this line: Fix plugin search
  (regression from 2.4.2)

  Ubuntu Studio 22.04 currently has the bugged version:

  ➜ carla --version
  Using Carla version 2.4.2

  [1] https://github.com/falkTX/Carla/releases/tag/v2.4.3

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: carla 2.4.2-0ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-24.24-lowlatency 5.15.30
  Uname: Linux 5.15.0-24-lowlatency x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: KDE
  Date: Thu Apr 21 15:41:13 2022
  InstallationDate: Installed on 2022-04-20 (1 days ago)
  InstallationMedia: Ubuntu-Studio 22.04 LTS "Jammy Jellyfish" - Beta amd64 
(20220329.1)
  SourcePackage: carla
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/carla/+bug/1969798/+subscriptions


-- 
Mailing list: https://launchpad.net/~ubuntustudio-bugs
Post to : ubuntustudio-bugs@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntustudio-bugs
More help   : https://help.launchpad.net/ListHelp

[Ubuntustudio-bugs] [Bug 1969798] Re: Carla can't find plugins in plugin directories located in the user's home

** Changed in: carla (Ubuntu Jammy)
Milestone: None => jammy-updates

-- 
You received this bug notification because you are a member of Ubuntu
Studio Bugs, which is subscribed to carla in Ubuntu.
https://bugs.launchpad.net/bugs/1969798

Title:
  Carla can't find plugins in plugin directories located in the user's
  home

Status in carla package in Ubuntu:
  New
Status in carla source package in Jammy:
  New

Bug description:
  In the LV2 location in my home directory .lv2 I have the following
  plugin:

  ➜ ls ~/.lv2
  librnnoise_lv2.so

  ${HOME}/.lv2 is configured in Carla as a search path.

  In the Add Plugin dialog for Carla if I search for noise nothing shows
  up.

  This worked fine previously on 21.10.

  Release notes for Carla 2.4.3 [1] include this line: Fix plugin search
  (regression from 2.4.2)

  Ubuntu Studio 22.04 currently has the bugged version:

  ➜ carla --version
  Using Carla version 2.4.2

  [1] https://github.com/falkTX/Carla/releases/tag/v2.4.3

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: carla 2.4.2-0ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-24.24-lowlatency 5.15.30
  Uname: Linux 5.15.0-24-lowlatency x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: KDE
  Date: Thu Apr 21 15:41:13 2022
  InstallationDate: Installed on 2022-04-20 (1 days ago)
  InstallationMedia: Ubuntu-Studio 22.04 LTS "Jammy Jellyfish" - Beta amd64 
(20220329.1)
  SourcePackage: carla
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/carla/+bug/1969798/+subscriptions


-- 
Mailing list: https://launchpad.net/~ubuntustudio-bugs
Post to : ubuntustudio-bugs@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntustudio-bugs
More help   : https://help.launchpad.net/ListHelp

[Ubuntustudio-bugs] [Bug 1969798] Re: Carla can't find plugins in plugin directories located in the user's home

** Description changed:

+ [Impact]
+ 
+ Users of Carla are unable to refresh audio plugins when more are
+ installed, i.e. in the user's home directory. Furthermore, this can
+ cause Carla to crash.
+ 
+ [Test Plan]
+ 
+  * Launch Carla
+  * Click "Add Plugin"
+  * Click "Refresh"
+  * Click "Scan"
+  
+  Expected: Carla will scan for new plugins and find them.
+ 
+  Actual: Carla does not scan for plugins, and may crash.
+ 
+ [Where problems could occur]
+ 
+  * The patch may just plain not work, in which case we may have to do a
+ wholesale upload of Carla 2.4.3 instead as opposed to simply patching
+ 2.4.2 with the cherry-picked commit as uploaded.
+ 
+  * The other thing this might do is cause the application to cease to
+ function, though this is highly unlikely.
+ 
+ [Other Info]
+  
+ Original bug report as follows:
+ --
+ 
  In the LV2 location in my home directory .lv2 I have the following
  plugin:
  
  ➜ ls ~/.lv2
  librnnoise_lv2.so
  
  ${HOME}/.lv2 is configured in Carla as a search path.
  
  In the Add Plugin dialog for Carla if I search for noise nothing shows
  up.
  
  This worked fine previously on 21.10.
  
  Release notes for Carla 2.4.3 [1] include this line: Fix plugin search
  (regression from 2.4.2)
  
  Ubuntu Studio 22.04 currently has the bugged version:
  
  ➜ carla --version
  Using Carla version 2.4.2
  
  [1] https://github.com/falkTX/Carla/releases/tag/v2.4.3
  
  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: carla 2.4.2-0ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-24.24-lowlatency 5.15.30
  Uname: Linux 5.15.0-24-lowlatency x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: KDE
  Date: Thu Apr 21 15:41:13 2022
  InstallationDate: Installed on 2022-04-20 (1 days ago)
  InstallationMedia: Ubuntu-Studio 22.04 LTS "Jammy Jellyfish" - Beta amd64 
(20220329.1)
  SourcePackage: carla
  UpgradeStatus: No upgrade log present (probably fresh install)

-- 
You received this bug notification because you are a member of Ubuntu
Studio Bugs, which is subscribed to carla in Ubuntu.
https://bugs.launchpad.net/bugs/1969798

Title:
  Carla can't find plugins in plugin directories located in the user's
  home

Status in carla package in Ubuntu:
  Triaged
Status in carla source package in Jammy:
  Triaged

Bug description:
  [Impact]

  Users of Carla are unable to refresh audio plugins when more are
  installed, i.e. in the user's home directory. Furthermore, this can
  cause Carla to crash.

  [Test Plan]

   * Launch Carla
   * Click "Add Plugin"
   * Click "Refresh"
   * Click "Scan"
   
   Expected: Carla will scan for new plugins and find them.

   Actual: Carla does not scan for plugins, and may crash.

  [Where problems could occur]

   * The patch may just plain not work, in which case we may have to do
  a wholesale upload of Carla 2.4.3 instead as opposed to simply
  patching 2.4.2 with the cherry-picked commit as uploaded.

   * The other thing this might do is cause the application to cease to
  function, though this is highly unlikely.

  [Other Info]
   
  Original bug report as follows:
  --

  In the LV2 location in my home directory .lv2 I have the following
  plugin:

  ➜ ls ~/.lv2
  librnnoise_lv2.so

  ${HOME}/.lv2 is configured in Carla as a search path.

  In the Add Plugin dialog for Carla if I search for noise nothing shows
  up.

  This worked fine previously on 21.10.

  Release notes for Carla 2.4.3 [1] include this line: Fix plugin search
  (regression from 2.4.2)

  Ubuntu Studio 22.04 currently has the bugged version:

  ➜ carla --version
  Using Carla version 2.4.2

  [1] https://github.com/falkTX/Carla/releases/tag/v2.4.3

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: carla 2.4.2-0ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-24.24-lowlatency 5.15.30
  Uname: Linux 5.15.0-24-lowlatency x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: KDE
  Date: Thu Apr 21 15:41:13 2022
  InstallationDate: Installed on 2022-04-20 (1 days ago)
  InstallationMedia: Ubuntu-Studio 22.04 LTS "Jammy Jellyfish" - Beta amd64 
(20220329.1)
  SourcePackage: carla
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/carla/+bug/1969798/+subscriptions


-- 
Mailing list: https://launchpad.net/~ubuntustudio-bugs
Post to : ubuntustudio-bugs@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntustudio-bugs
More help   : https://help.launchpad.net/ListHelp

[Ubuntustudio-bugs] [Bug 1969798] Re: Carla can't find plugins in plugin directories located in the user's home

** Changed in: carla (Ubuntu Jammy)
   Status: Triaged => In Progress

** Changed in: carla (Ubuntu Jammy)
   Status: In Progress => Fix Committed

-- 
You received this bug notification because you are a member of Ubuntu
Studio Bugs, which is subscribed to carla in Ubuntu.
https://bugs.launchpad.net/bugs/1969798

Title:
  Carla can't find plugins in plugin directories located in the user's
  home

Status in carla package in Ubuntu:
  Fix Committed
Status in carla source package in Jammy:
  Fix Committed

Bug description:
  [Impact]

  Users of Carla are unable to refresh audio plugins when more are
  installed, i.e. in the user's home directory. Furthermore, this can
  cause Carla to crash.

  [Test Plan]

   * Launch Carla
   * Click "Add Plugin"
   * Click "Refresh"
   * Click "Scan"
   
   Expected: Carla will scan for new plugins and find them.

   Actual: Carla does not scan for plugins, and may crash.

  [Where problems could occur]

   * The patch may just plain not work, in which case we may have to do
  a wholesale upload of Carla 2.4.3 instead as opposed to simply
  patching 2.4.2 with the cherry-picked commit as uploaded.

   * The other thing this might do is cause the application to cease to
  function, though this is highly unlikely.

  [Other Info]
   
  Original bug report as follows:
  --

  In the LV2 location in my home directory .lv2 I have the following
  plugin:

  ➜ ls ~/.lv2
  librnnoise_lv2.so

  ${HOME}/.lv2 is configured in Carla as a search path.

  In the Add Plugin dialog for Carla if I search for noise nothing shows
  up.

  This worked fine previously on 21.10.

  Release notes for Carla 2.4.3 [1] include this line: Fix plugin search
  (regression from 2.4.2)

  Ubuntu Studio 22.04 currently has the bugged version:

  ➜ carla --version
  Using Carla version 2.4.2

  [1] https://github.com/falkTX/Carla/releases/tag/v2.4.3

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: carla 2.4.2-0ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-24.24-lowlatency 5.15.30
  Uname: Linux 5.15.0-24-lowlatency x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: KDE
  Date: Thu Apr 21 15:41:13 2022
  InstallationDate: Installed on 2022-04-20 (1 days ago)
  InstallationMedia: Ubuntu-Studio 22.04 LTS "Jammy Jellyfish" - Beta amd64 
(20220329.1)
  SourcePackage: carla
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/carla/+bug/1969798/+subscriptions


-- 
Mailing list: https://launchpad.net/~ubuntustudio-bugs
Post to : ubuntustudio-bugs@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntustudio-bugs
More help   : https://help.launchpad.net/ListHelp

[Ubuntustudio-bugs] [Bug 1969827] Re: Studio Controls doesn't actually switch to FFADO

2022-04-25 Thread Erich Eickmeyer 

** Tags removed: verification-needed verification-needed-jammy
** Tags added: verification-done verification-done-jammy

-- 
You received this bug notification because you are a member of Ubuntu
Studio Bugs, which is subscribed to studio-controls in Ubuntu.
https://bugs.launchpad.net/bugs/1969827

Title:
  Studio Controls doesn't actually switch to FFADO

Status in studio-controls package in Ubuntu:
  Fix Committed
Status in studio-controls source package in Jammy:
  Fix Committed

Bug description:
  [Impact]

   * Users of Studio Controls, specifically Ubuntu Studio users using
  Firewire audio interfaces, are running into issues where using Studio
  Controls to switch to the FFADO driver as provided by libffado (as
  opposed to the ALSA firewire driver) are unable to do so.

   * The dropdown menu in Studio Controls that switches between the two
  is supposed to add a blacklist item into /etc/modprobe.d to blacklist
  the ALSA Firewire driver, which is in direct conflict with the FFADO
  driver required by some Firewire audio interfaces and must be
  blacklisted. Currently, this dropdown menu has no effect.

   * The uploaded package fixes this by refactoring the copying
  mechanism. This has already been fixed in a future release of Studio
  Controls.

  [Test Plan]

   * Launch Studio Controls

   * In the System Tweaks tab, switch "FireWire Module select (reboot to
  switch):) menu to "Use FFADO FireWire Modules"

   * Reboot

   * Login, launch Studio Controls

   * Notice FireWire Module Select is back on ALSA.

   * 'ls /etc/modprobe.d/' will not show 'blacklist-studio.conf'

   * Expected behavior: FireWire Module select should be on FFADO and
  'blacklist-studio.conf' should exist in '/etc/modprobe.d/'

  [Where problems could occur]

   * Although great care has been taken to avoid this, the 
'blacklist-studio.conf' file could get stuck and remain blacklisting ALSA 
firewire modules. If this does cause such a regression, a further upload will 
fix this. However, this is unlikely as it merely invokes code that was not 
being invoked before that already existed as this is merely correcting a 
regression.
 
  [Other Info]
   
   * Original Description:

  Choosing the drop-down to switch the FireWire module from ALSA to
  FFADO doesn't appear to actually do anything.

  No blacklist-studio.conf file ever gets created in /etc/modprobe.d.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: studio-controls 2.3.1-0ubuntu1
  ProcVersionSignature: Ubuntu 5.15.0-24.24-lowlatency 5.15.30
  Uname: Linux 5.15.0-24-lowlatency x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: KDE
  Date: Thu Apr 21 20:07:06 2022
  InstallationDate: Installed on 2022-04-20 (1 days ago)
  InstallationMedia: Ubuntu-Studio 22.04 LTS "Jammy Jellyfish" - Beta amd64 
(20220329.1)
  PackageArchitecture: all
  SourcePackage: studio-controls
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/studio-controls/+bug/1969827/+subscriptions


-- 
Mailing list: https://launchpad.net/~ubuntustudio-bugs
Post to : ubuntustudio-bugs@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntustudio-bugs
More help   : https://help.launchpad.net/ListHelp

[Ubuntustudio-bugs] [Bug 1970238] Re: calf-plugins always display a maximized window

2022-04-25 Thread Erich Eickmeyer 

Thank you for taking the time to report this bug and helping to make
Ubuntu better. Please execute the following command only once, as it
will automatically gather debugging information, in a terminal:

apport-collect 1970238

When reporting bugs in the future please use apport by using 'ubuntu-
bug' and the name of the package affected. You can learn more about this
functionality at https://wiki.ubuntu.com/ReportingBugs.

-MOREOVER-

This package is synced unchanged from Debian. Therefore, the issue you
are reporting is an upstream one and it would be nice if somebody having
it could send the bug to the maintainers of the software by following
the instructions at https://wiki.ubuntu.com/Debian/Bugs. If you have
done so, please tell us the number of the upstream bug (or the link), so
we can add a bugwatch that will inform us about its status.

-FURTHERMORE-

This may very well be an issue the developers of the software need to be
made aware of. Please report this issue to https://github.com/calf-
studio-gear/calf/issues if it doesn't already exist and report the filed
issue here.

Please take the above steps and change this bug's status from
"Incomplete" to "New".

N.B. Bug reports are about helping other people to not encounter the
same issue, not fixing individual support issues. Therefore, if the
above steps are not taken within 60 days, this bug will automatically
expire.

** Changed in: calf (Ubuntu)
   Status: New => Incomplete

-- 
You received this bug notification because you are a member of Ubuntu
Studio Bugs, which is subscribed to calf in Ubuntu.
Matching subscriptions: Ubuntu Studio Bugs
https://bugs.launchpad.net/bugs/1970238

Title:
  calf-plugins always display a maximized window

Status in calf package in Ubuntu:
  Incomplete

Bug description:
  
  $ lsb_release -rd
  Description:Ubuntu 22.04 LTS
  Release:22.04

  $ dpkg -l calf-plugins
  Desired=Unknown/Install/Remove/Purge/Hold
  | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
  |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
  ||/ Name   Version  Architecture Description
  
+++-==---=
  ii  calf-plugins   0.90.3-3 amd64Calf Studio Gear - audio effects 
and sound generators

  Expected: ability to resize parameters window for plugin[s].

  Observed: inability to resize window that insists upon being maximized
  [full-screen]

  My use case is under the qtractor DAW, and can be easily repro'd as
  follows:

  * sudo apt install calf-plugins [from default repositories for either release]
  * start qtractor
  * add track
  * open mixer window
  * add plugin to new track - i.e. select LV2 plugin calf-reverb
  * observe that the parameters window for the plugin is maximized and very 
stubborn about resizing.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/calf/+bug/1970238/+subscriptions


-- 
Mailing list: https://launchpad.net/~ubuntustudio-bugs
Post to : ubuntustudio-bugs@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntustudio-bugs
More help   : https://help.launchpad.net/ListHelp

[Ubuntustudio-bugs] [Bug 1970238] Re: calf-plugins always display a maximized window

2022-04-25 Thread Erich Eickmeyer 

Thanks, Jack.

As for the Debian report, it *shouldn't* post to the open internet as
their archives mask email addresses (I think?), but you've gone as far
upstream as you can go, so you've done the right thing.

The biggest issue here is that Calf uses GTK and not a custom toolkit
like most plugins (like LSP), so the resizing issues you're experiencing
might very well be a result of that.

I don't use qtractor myself, and have worked with the calf developers in
the past. Hopefully working with them will help resolve this issue. I'm
going to mark it as "Triaged" in the meantime. If you have any further
updates to post, feel free to put them here.

** Changed in: calf (Ubuntu)
   Status: Incomplete => Triaged

-- 
You received this bug notification because you are a member of Ubuntu
Studio Bugs, which is subscribed to calf in Ubuntu.
Matching subscriptions: Ubuntu Studio Bugs
https://bugs.launchpad.net/bugs/1970238

Title:
  calf-plugins always display a maximized window

Status in calf package in Ubuntu:
  Triaged

Bug description:
  
  $ lsb_release -rd
  Description:Ubuntu 22.04 LTS
  Release:22.04

  $ dpkg -l calf-plugins
  Desired=Unknown/Install/Remove/Purge/Hold
  | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
  |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
  ||/ Name   Version  Architecture Description
  
+++-==---=
  ii  calf-plugins   0.90.3-3 amd64Calf Studio Gear - audio effects 
and sound generators

  Expected: ability to resize parameters window for plugin[s].

  Observed: inability to resize window that insists upon being maximized
  [full-screen]

  My use case is under the qtractor DAW, and can be easily repro'd as
  follows:

  * sudo apt install calf-plugins [from default repositories for either release]
  * start qtractor
  * add track
  * open mixer window
  * add plugin to new track - i.e. select LV2 plugin calf-reverb
  * observe that the parameters window for the plugin is maximized and very 
stubborn about resizing.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/calf/+bug/1970238/+subscriptions


-- 
Mailing list: https://launchpad.net/~ubuntustudio-bugs
Post to : ubuntustudio-bugs@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntustudio-bugs
More help   : https://help.launchpad.net/ListHelp

[Ubuntustudio-bugs] [Bug 1967691] Re: Ubuntu Studio will not install on VM with UEFI

2022-04-10 Thread Erich Eickmeyer 

Norman,

It's an invalid bug because a bug must be filed against an individual
package and not the distribution as a while. Additionally, must be
reproducible. This is NOT the place to ask for help with something.
Please see ubuntustudio.org/support for help options. Launchpad is a bug
tracker, not a mailing list or help forum.

Seek help with the issue before attempting to file a bug report. The big
problem here is we cannot narrow this down to a single package this way.

-- 
You received this bug notification because you are a member of Ubuntu
Studio Bugs, which is subscribed to Ubuntu Studio.
Matching subscriptions: UbuntuStudio Bugs
https://bugs.launchpad.net/bugs/1967691

Title:
  Ubuntu Studio will not install on VM with UEFI

Status in Ubuntu Studio:
  Invalid

Bug description:
  I tried to install Ubuntu Studio 22.04 Beta on both VirtualBox and
  VMware set for UEFI with GPT partitioning.  I used the same settings
  that I have previously used to install Ubuntu Studio on both virtual
  machines and computers.  I was also successful installing previous
  versions of Ubuntu Studio 22.04 (alpha versions) with the settings.
  When I try the install, I can click "Install Ubuntu Studio"; the
  screen then changes to a blank screen.

  My UEFI settings are: 512 Mb FAT32 boot, ~15 Gb root, ~25 Gb home.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntustudio/+bug/1967691/+subscriptions


-- 
Mailing list: https://launchpad.net/~ubuntustudio-bugs
Post to : ubuntustudio-bugs@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntustudio-bugs
More help   : https://help.launchpad.net/ListHelp

[Ubuntustudio-bugs] [Bug 1969798] Re: Carla can't find plugins in plugin directories located in the user's home

Unfortunately, this completely FTBFS. It will likely have to be a
complete backport of Carla 2.4.3. I'll work on that once Kinetic
completely opens.

** Also affects: carla (Ubuntu Kinetic)
   Importance: High
 Assignee: Erich Eickmeyer  (eeickmeyer)
   Status: Fix Committed

** Changed in: carla (Ubuntu Jammy)
   Status: Fix Committed => Triaged

** Changed in: carla (Ubuntu Kinetic)
   Status: Fix Committed => Triaged

** Changed in: carla (Ubuntu Kinetic)
Milestone: jammy-updates => None

-- 
You received this bug notification because you are a member of Ubuntu
Studio Bugs, which is subscribed to carla in Ubuntu.
https://bugs.launchpad.net/bugs/1969798

Title:
  Carla can't find plugins in plugin directories located in the user's
  home

Status in carla package in Ubuntu:
  Triaged
Status in carla source package in Jammy:
  Triaged
Status in carla source package in Kinetic:
  Triaged

Bug description:
  [Impact]

  Users of Carla are unable to refresh audio plugins when more are
  installed, i.e. in the user's home directory. Furthermore, this can
  cause Carla to crash.

  [Test Plan]

   * Launch Carla
   * Click "Add Plugin"
   * Click "Refresh"
   * Click "Scan"
   
   Expected: Carla will scan for new plugins and find them.

   Actual: Carla does not scan for plugins, and may crash.

  [Where problems could occur]

   * The patch may just plain not work, in which case we may have to do
  a wholesale upload of Carla 2.4.3 instead as opposed to simply
  patching 2.4.2 with the cherry-picked commit as uploaded.

   * The other thing this might do is cause the application to cease to
  function, though this is highly unlikely.

  [Other Info]
   
  Original bug report as follows:
  --

  In the LV2 location in my home directory .lv2 I have the following
  plugin:

  ➜ ls ~/.lv2
  librnnoise_lv2.so

  ${HOME}/.lv2 is configured in Carla as a search path.

  In the Add Plugin dialog for Carla if I search for noise nothing shows
  up.

  This worked fine previously on 21.10.

  Release notes for Carla 2.4.3 [1] include this line: Fix plugin search
  (regression from 2.4.2)

  Ubuntu Studio 22.04 currently has the bugged version:

  ➜ carla --version
  Using Carla version 2.4.2

  [1] https://github.com/falkTX/Carla/releases/tag/v2.4.3

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: carla 2.4.2-0ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-24.24-lowlatency 5.15.30
  Uname: Linux 5.15.0-24-lowlatency x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: KDE
  Date: Thu Apr 21 15:41:13 2022
  InstallationDate: Installed on 2022-04-20 (1 days ago)
  InstallationMedia: Ubuntu-Studio 22.04 LTS "Jammy Jellyfish" - Beta amd64 
(20220329.1)
  SourcePackage: carla
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/carla/+bug/1969798/+subscriptions


-- 
Mailing list: https://launchpad.net/~ubuntustudio-bugs
Post to : ubuntustudio-bugs@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntustudio-bugs
More help   : https://help.launchpad.net/ListHelp

[Ubuntustudio-bugs] [Bug 1970481] Re: After an update about a month ago audio through my Focusrite 2i2 is "chirpy" and distorted.

Well, because you reported the bug against the website, which makes it
automatically invalid. Additionally, most things are support issues
until they can be proven that they're actually bugs.

-- 
You received this bug notification because you are a member of Ubuntu
Studio Bugs, which is subscribed to The Ubuntu Studio Project.
Matching subscriptions: UbuntuStudio Bugs
https://bugs.launchpad.net/bugs/1970481

Title:
  After an update about a month ago audio through my Focusrite 2i2 is
  "chirpy" and distorted.

Status in Ubuntu Studio Website:
  Invalid

Bug description:
  After an update about a month ago audio through my Focusrite 2i2 is
  "chirpy" and distorted.

  It worked prior to whatever update came down the pike about a month
  ago.

  As I say, audio playing through my USB Focusrite Scarlet 2i2 is
  "Chirpy" and distorted. If I listen with earbuds out the laptop's
  analog output the audio sounds fine.

  This is out of the headphone jack on the 2i2 and out of the balanced
  TRS on the back. The interface works fine with every other computer in
  the house. Tested on 3.

  I am running Ubuntu Studio 20.04 LTS on a Lenovo Thinkpad laptop.
  Kernel version is:

  5.13.0-40-lowlatency

  I just tested again and there seems to be a sample rate issue as well.
  In addition to being distorted the music seems to be slower and lower
  in pitch.

  I didn't make any changes I am aware of to ANY configs on this laptop.
  This just started suddenly happening after an update.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntustudio-website/+bug/1970481/+subscriptions


-- 
Mailing list: https://launchpad.net/~ubuntustudio-bugs
Post to : ubuntustudio-bugs@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntustudio-bugs
More help   : https://help.launchpad.net/ListHelp

[Ubuntustudio-bugs] [Bug 1970481] Re: After an update about a month ago audio through my Focusrite 2i2 is "chirpy" and distorted.

If that's the case, then keep the discussion there, no need to open a
new bug.

-- 
You received this bug notification because you are a member of Ubuntu
Studio Bugs, which is subscribed to The Ubuntu Studio Project.
Matching subscriptions: UbuntuStudio Bugs
https://bugs.launchpad.net/bugs/1970481

Title:
  After an update about a month ago audio through my Focusrite 2i2 is
  "chirpy" and distorted.

Status in Ubuntu Studio Website:
  Invalid

Bug description:
  After an update about a month ago audio through my Focusrite 2i2 is
  "chirpy" and distorted.

  It worked prior to whatever update came down the pike about a month
  ago.

  As I say, audio playing through my USB Focusrite Scarlet 2i2 is
  "Chirpy" and distorted. If I listen with earbuds out the laptop's
  analog output the audio sounds fine.

  This is out of the headphone jack on the 2i2 and out of the balanced
  TRS on the back. The interface works fine with every other computer in
  the house. Tested on 3.

  I am running Ubuntu Studio 20.04 LTS on a Lenovo Thinkpad laptop.
  Kernel version is:

  5.13.0-40-lowlatency

  I just tested again and there seems to be a sample rate issue as well.
  In addition to being distorted the music seems to be slower and lower
  in pitch.

  I didn't make any changes I am aware of to ANY configs on this laptop.
  This just started suddenly happening after an update.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntustudio-website/+bug/1970481/+subscriptions


-- 
Mailing list: https://launchpad.net/~ubuntustudio-bugs
Post to : ubuntustudio-bugs@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntustudio-bugs
More help   : https://help.launchpad.net/ListHelp

[Ubuntustudio-bugs] [Bug 1970481] Re: After an update about a month ago audio through my Focusrite 2i2 is "chirpy" and distorted.

Please seek support at https://ubuntustudio.org/support. Support is not
appropriate on a bug tracker.

** Changed in: ubuntustudio-website
   Status: New => Invalid

-- 
You received this bug notification because you are a member of Ubuntu
Studio Bugs, which is subscribed to The Ubuntu Studio Project.
Matching subscriptions: UbuntuStudio Bugs
https://bugs.launchpad.net/bugs/1970481

Title:
  After an update about a month ago audio through my Focusrite 2i2 is
  "chirpy" and distorted.

Status in Ubuntu Studio Website:
  Invalid

Bug description:
  After an update about a month ago audio through my Focusrite 2i2 is
  "chirpy" and distorted.

  It worked prior to whatever update came down the pike about a month
  ago.

  As I say, audio playing through my USB Focusrite Scarlet 2i2 is
  "Chirpy" and distorted. If I listen with earbuds out the laptop's
  analog output the audio sounds fine.

  This is out of the headphone jack on the 2i2 and out of the balanced
  TRS on the back. The interface works fine with every other computer in
  the house. Tested on 3.

  I am running Ubuntu Studio 20.04 LTS on a Lenovo Thinkpad laptop.
  Kernel version is:

  5.13.0-40-lowlatency

  I just tested again and there seems to be a sample rate issue as well.
  In addition to being distorted the music seems to be slower and lower
  in pitch.

  I didn't make any changes I am aware of to ANY configs on this laptop.
  This just started suddenly happening after an update.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntustudio-website/+bug/1970481/+subscriptions


-- 
Mailing list: https://launchpad.net/~ubuntustudio-bugs
Post to : ubuntustudio-bugs@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntustudio-bugs
More help   : https://help.launchpad.net/ListHelp

[Ubuntustudio-bugs] [Bug 2043214] [NEW] Unreadable screen in Ubiquity

2023-11-10 Thread Erich Eickmeyer

Public bug reported:

[Impact]

ubuntustudio-installer now contains a separate application for
configuring the audio subsystem, which may in the future be spun-off
into its own binary package. Initially, it was meant to simply switch
systems between the PipeWire and the legacy PulseAudio/JACK
configuration (an installer function). However, it became clear that it
needed to be able to configure the PipeWire configuration as well.

This used to be as simple as changing the PIPEWIRE_QUANTUM environment
variable with a logout/in, but this changed with the version of PipeWire
in Mantic and required a somewhat higher level of complexity involving
the `pw-metadata` command. This was not foreseen before release.

This also requires a systemd user service that applies these settings at
login, also part of this change.

[Test Case]

With Ubuntu Studio installed:

 * Open Patchance
 * Note the sample rate and buffer (1024/48000 is the default)
 * Go to Ubuntu Studio Audio Configuration
 * Change the sample rate and buffer to something like 512 96000
 * Log out and in
 * Open Patchance
 * Note the sample rate and buffer *HAS NOT CHANGED* <- This is the problem
   ** Expected result is that it did change

[What could go wrong]

The only regression here is that in order to change the buffer size and
sample rate, people will have to go back to the Audio Configuration
utility to do so as opposed to whatever interface they are in, but the
plus side is that it will no longer require a relog.

** Affects: ubuntustudio-installer (Ubuntu)
 Importance: High
 Assignee: Erich Eickmeyer (eeickmeyer)
 Status: In Progress

** Affects: ubuntustudio-installer (Ubuntu Mantic)
 Importance: High
 Assignee: Erich Eickmeyer (eeickmeyer)
 Status: In Progress

** Affects: ubuntustudio-installer (Ubuntu Noble)
 Importance: High
 Assignee: Erich Eickmeyer (eeickmeyer)
 Status: In Progress

** Also affects: ubuntustudio-installer (Ubuntu Noble)
   Importance: High
 Assignee: Erich Eickmeyer (eeickmeyer)
   Status: In Progress

** Also affects: ubuntustudio-installer (Ubuntu Mantic)
   Importance: Undecided
   Status: New

** Changed in: ubuntustudio-installer (Ubuntu Mantic)
   Status: New => In Progress

** Changed in: ubuntustudio-installer (Ubuntu Mantic)
   Importance: Undecided => High

** Changed in: ubuntustudio-installer (Ubuntu Mantic)
 Assignee: (unassigned) => Erich Eickmeyer (eeickmeyer)

** Description changed:

  [Impact]
  
  ubuntustudio-installer now contains a separate application for
  configuring the audio subsystem, which may in the future be spun-off
  into its own binary package. Initially, it was meant to simply switch
  systems between the PipeWire and the legacy PulseAudio/JACK
  configuration (an installer function). However, it became clear that it
  needed to be able to configure the PipeWire configuration as well.
  
  This used to be as simple as changing the PIPEWIRE_QUANTUM environment
  variable with a logout/in, but this changed with the version of PipeWire
  in Mantic and required a somewhat higher level of complexity involving
  the `pw-metadata` command. This was not foreseen before release.
  
  This also requires a systemd user service that applies these settings at
  login, also part of this change.
  
  [Test Case]
  
  With Ubuntu Studio installed:
  
-  * Open Patchance
-  * Note the sample rate and buffer (1024/48000 is the default)
-  * Go to Ubuntu Studio Audio Configuration
-  * Change the sample rate and buffer to something like 512 96000
-  * Log out and in
-  * Open Patchance
-  * Note the sample rate and buffer *HAS NOT CHANGED* <- This is the problem
-** Expected result is that it did change
+  * Open Patchance
+  * Note the sample rate and buffer (1024/48000 is the default)
+  * Go to Ubuntu Studio Audio Configuration
+  * Change the sample rate and buffer to something like 512 96000
+  * Log out and in
+  * Open Patchance
+  * Note the sample rate and buffer *HAS NOT CHANGED* <- This is the problem
+    ** Expected result is that it did change
  
- [Regression Potential]
+ [What could go wrong]
  
  The only regression here is that in order to change the buffer size and
  sample rate, people will have to go back to the Audio Configuration
  utility to do so as opposed to whatever interface they are in, but the
  plus side is that it will no longer require a relog.

-- 
You received this bug notification because you are a member of Ubuntu
Studio Bugs, which is subscribed to ubuntustudio-installer in Ubuntu.
https://bugs.launchpad.net/bugs/2043214

Title:
  Unreadable screen in Ubiquity

Status in ubuntustudio-installer package in Ubuntu:
  In Progress
Status in ubuntustudio-installer source package in Mantic:
  In Progress
Status in ubuntustudio-installer source package in Noble:
  In Progress

Bug description:
  [Impact]

  ubuntustudio-installer now contains a separate application for
  configuring t

[Ubuntustudio-bugs] [Bug 1973052] Re: Length and position of selection is not shown correctly

2022-05-11 Thread Erich Eickmeyer 

** Changed in: audacity (Ubuntu)
   Status: New => Incomplete

-- 
You received this bug notification because you are a member of Ubuntu
Studio Bugs, which is subscribed to audacity in Ubuntu.
Matching subscriptions: Ubuntu Studio Bugs
https://bugs.launchpad.net/bugs/1973052

Title:
  Length and position of selection is not shown correctly

Status in audacity package in Ubuntu:
  Incomplete

Bug description:
  Steps to reproduce:

  1. Open .wav/.ogg file in audacity 2.4.2
  2. Select length and end position as selection option below
  3. Make a short selection (e.g. 4 samples long)
  4. Change length and position unit to "samples"

  Expected Result:
  "000 000 004 Samples" as length is shown

  Result:
  "004 000 000 Samples" as length is shown

  
  Good time to update to audacity 3.1.x?

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: audacity 2.4.2~dfsg0-5
  ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30
  Uname: Linux 5.15.0-27-generic x86_64
  AlsaCards:
   0 [PCH]: HDA-Intel - HDA Intel PCH
 HDA Intel PCH at 0xef24 irq 138
1 [U0x46d0x825]: USB-Audio - USB Device 0x46d:0x825
 USB Device 0x46d:0x825 at usb-:00:14.0-4.1.4, high 
speed
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: XFCE
  Date: Wed May 11 19:24:04 2022
  InstallationDate: Installed on 2016-04-30 (2202 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  SourcePackage: audacity
  UpgradeStatus: Upgraded to jammy on 2022-04-28 (13 days ago)
  modified.conffile..etc.default.apport:
   # set this to 0 to disable apport, or to 1 to enable it
   # you can temporarily override this with
   # sudo service apport start force_start=1
   enabled=0
  mtime.conffile..etc.default.apport: 2017-06-27T22:18:31.198313

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/audacity/+bug/1973052/+subscriptions


-- 
Mailing list: https://launchpad.net/~ubuntustudio-bugs
Post to : ubuntustudio-bugs@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntustudio-bugs
More help   : https://help.launchpad.net/ListHelp

[Ubuntustudio-bugs] [Bug 1973052] Re: Length and position of selection is not shown correctly

2022-05-11 Thread Erich Eickmeyer 

Per the version number (as an example lacking the -0ubuntu1 suffix),
this package is synced directly from Debian without changes, Therefore,
the issue you are reporting is an upstream one and it would be nice if
somebody having it could send the bug to the developers of the software
by following the instructions at https://wiki.ubuntu.com/Debian/Bugs. If
you have done so, please tell us the number of the upstream bug (or the
link), so we can add a bugwatch that will inform us about its status.
Thanks in advance.

> Good time to update to audacity 3.1.x?

This is not likely to happen as packages in Ubuntu may not be the
latest. Ubuntu aims for stability, so "latest" may not be a good idea.
Post-release updates are only considered if they are fixes for security
vulnerabilities, high impact bug fixes, or unintrusive bug fixes with
substantial benefit. A small patch might work, but one would have to be
willing to patch this older version.

-- 
You received this bug notification because you are a member of Ubuntu
Studio Bugs, which is subscribed to audacity in Ubuntu.
Matching subscriptions: Ubuntu Studio Bugs
https://bugs.launchpad.net/bugs/1973052

Title:
  Length and position of selection is not shown correctly

Status in audacity package in Ubuntu:
  New

Bug description:
  Steps to reproduce:

  1. Open .wav/.ogg file in audacity 2.4.2
  2. Select length and end position as selection option below
  3. Make a short selection (e.g. 4 samples long)
  4. Change length and position unit to "samples"

  Expected Result:
  "000 000 004 Samples" as length is shown

  Result:
  "004 000 000 Samples" as length is shown

  
  Good time to update to audacity 3.1.x?

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: audacity 2.4.2~dfsg0-5
  ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30
  Uname: Linux 5.15.0-27-generic x86_64
  AlsaCards:
   0 [PCH]: HDA-Intel - HDA Intel PCH
 HDA Intel PCH at 0xef24 irq 138
1 [U0x46d0x825]: USB-Audio - USB Device 0x46d:0x825
 USB Device 0x46d:0x825 at usb-:00:14.0-4.1.4, high 
speed
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: XFCE
  Date: Wed May 11 19:24:04 2022
  InstallationDate: Installed on 2016-04-30 (2202 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  SourcePackage: audacity
  UpgradeStatus: Upgraded to jammy on 2022-04-28 (13 days ago)
  modified.conffile..etc.default.apport:
   # set this to 0 to disable apport, or to 1 to enable it
   # you can temporarily override this with
   # sudo service apport start force_start=1
   enabled=0
  mtime.conffile..etc.default.apport: 2017-06-27T22:18:31.198313

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/audacity/+bug/1973052/+subscriptions


-- 
Mailing list: https://launchpad.net/~ubuntustudio-bugs
Post to : ubuntustudio-bugs@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntustudio-bugs
More help   : https://help.launchpad.net/ListHelp

[Ubuntustudio-bugs] [Bug 1980687] Re: [SRU] Quassel should not have #debian as default channel in Ubuntu

2022-07-11 Thread Erich Eickmeyer 

** Tags added: verification-done

** Changed in: quassel (Ubuntu Jammy)
   Status: Fix Released => Fix Committed

-- 
You received this bug notification because you are a member of Ubuntu
Studio Bugs, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1980687

Title:
  [SRU] Quassel should not have #debian as default channel in Ubuntu

Status in quassel package in Ubuntu:
  Fix Released
Status in quassel source package in Jammy:
  Fix Committed
Status in quassel source package in Kinetic:
  Fix Released

Bug description:
  [Impact]

   * Quassel currently is carrying a patch that, by default, connects
  users to OFTC and the #debian channel. This is not desired for users
  of Lubuntu and Ubuntu Studio, which seed Quassel.

  * Instead, the patch has been changed to go to #ubuntu on Libera,
  which supports both Ubuntu Studio and Lubuntu, and/or has volunteers
  who can redirect to the flavor support channels.

  [Test Plan]

   * Install Quassel
   * Connect
   * You'll find yourself in #debian on OFTC

  [Where problems could occur]

   * Users of Ubuntu who think they're on a Debian system might be irked
  they're no longer going to Debian support, but this is not likely.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/quassel/+bug/1980687/+subscriptions


-- 
Mailing list: https://launchpad.net/~ubuntustudio-bugs
Post to : ubuntustudio-bugs@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntustudio-bugs
More help   : https://help.launchpad.net/ListHelp

[Ubuntustudio-bugs] [Bug 1193373] Re: [needs-packaging] No "blender-chemicals" and "BioBlender" in repository

2022-07-12 Thread Erich Eickmeyer 

** No longer affects: ubuntustudio-meta (Ubuntu)

-- 
You received this bug notification because you are a member of Ubuntu
Studio Bugs, which is subscribed to ubuntustudio-meta in Ubuntu.
Matching subscriptions: UbuntuStudioPackages, ubuntustudio-bugs: blender
https://bugs.launchpad.net/bugs/1193373

Title:
  [needs-packaging] No "blender-chemicals" and "BioBlender" in
  repository

Status in blender package in Ubuntu:
  New

Bug description:
  I have an idea that many users may like to use in Blender. Programs
  like Viewmol (https://launchpad.net/ubuntu/saucy/+package/viewmol) and
  Ballview (https://launchpad.net/ubuntu/saucy/+package/ballview)
  display molecules by using chemical file formats like XYZ
  (http://en.wikipedia.org/wiki/Xyz_file).  Would it be easy to give
  Blender the ability to read a chemical file
  (http://en.wikipedia.org/wiki/Chemical_file_format) generate a model
  that can be used in Blender. This feature would help animators and
  graphics designers to generate graphics faster because many molecular
  model files can be downloaded freely. Then, this would save designers
  time becasue the molecule would be drawn for the graphics designer.
  Ballview, Viewmol, and numerous other molecular model viewers are open
  source, so the Blender developers should have an easier time
  implementing this idea rather than writting the code from scratch.

  Thank you, and I hope my idea benefits Blender and its users. I am
  willing to be a beta tester for this feature. I am currently learning
  how to use Blender. I am very familiar with molecular model files (I
  own hundreds or more). I know how to use OpenBabel, which is an open-
  source program that converts one molecule model format to another.
  OpenBabel would enable us to test many formats.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/blender/+bug/1193373/+subscriptions


-- 
Mailing list: https://launchpad.net/~ubuntustudio-bugs
Post to : ubuntustudio-bugs@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntustudio-bugs
More help   : https://help.launchpad.net/ListHelp

[Ubuntustudio-bugs] [Bug 1980687] Re: [SRU] Quassel should not have #debian as default channel in Ubuntu

2022-07-06 Thread Erich Eickmeyer 

** Changed in: quassel (Ubuntu Kinetic)
   Status: Fix Released => In Progress

** Changed in: quassel (Ubuntu Jammy)
   Status: Fix Committed => In Progress

** Changed in: quassel (Ubuntu Kinetic)
   Status: In Progress => Fix Committed

-- 
You received this bug notification because you are a member of Ubuntu
Studio Bugs, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1980687

Title:
  [SRU] Quassel should not have #debian as default channel in Ubuntu

Status in quassel package in Ubuntu:
  Fix Committed
Status in quassel source package in Jammy:
  In Progress
Status in quassel source package in Kinetic:
  Fix Committed

Bug description:
  [Impact]

   * Quassel currently is carrying a patch that, by default, connects
  users to OFTC and the #debian channel. This is not desired for users
  of Lubuntu and Ubuntu Studio, which seed Quassel.

  * Instead, the patch has been changed to go to #ubuntu on Libera,
  which supports both Ubuntu Studio and Lubuntu, and/or has volunteers
  who can redirect to the flavor support channels.

  [Test Plan]

   * Install Quassel
   * Connect
   * You'll find yourself in #debian on OFTC

  [Where problems could occur]

   * Users of Ubuntu who think they're on a Debian system might be irked
  they're no longer going to Debian support, but this is not likely.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/quassel/+bug/1980687/+subscriptions


-- 
Mailing list: https://launchpad.net/~ubuntustudio-bugs
Post to : ubuntustudio-bugs@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntustudio-bugs
More help   : https://help.launchpad.net/ListHelp

[Ubuntustudio-bugs] [Bug 1980687] Re: [SRU] Quassel should not have #debian as default channel in Ubuntu

2022-07-06 Thread Erich Eickmeyer 

Uploaded to both Jammy and Kinetic. Robie, sorry for the trouble on this
one, and SRU team, thanks for your patience as usual. I guess this is
why this regression testing exists.

-- 
You received this bug notification because you are a member of Ubuntu
Studio Bugs, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1980687

Title:
  [SRU] Quassel should not have #debian as default channel in Ubuntu

Status in quassel package in Ubuntu:
  Fix Committed
Status in quassel source package in Jammy:
  In Progress
Status in quassel source package in Kinetic:
  Fix Committed

Bug description:
  [Impact]

   * Quassel currently is carrying a patch that, by default, connects
  users to OFTC and the #debian channel. This is not desired for users
  of Lubuntu and Ubuntu Studio, which seed Quassel.

  * Instead, the patch has been changed to go to #ubuntu on Libera,
  which supports both Ubuntu Studio and Lubuntu, and/or has volunteers
  who can redirect to the flavor support channels.

  [Test Plan]

   * Install Quassel
   * Connect
   * You'll find yourself in #debian on OFTC

  [Where problems could occur]

   * Users of Ubuntu who think they're on a Debian system might be irked
  they're no longer going to Debian support, but this is not likely.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/quassel/+bug/1980687/+subscriptions


-- 
Mailing list: https://launchpad.net/~ubuntustudio-bugs
Post to : ubuntustudio-bugs@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntustudio-bugs
More help   : https://help.launchpad.net/ListHelp

[Ubuntustudio-bugs] [Bug 1980901] [NEW] [FFe] libreoffice-calc erroneously missing from ubuntustudio 22.04 seed

2022-07-06 Thread Erich Eickmeyer 

Public bug reported:

During the effort before Feature Freeze for Jammy, the Ubuntu Studio
team (with myself as lead) were scrambling with ideas to reduce the
install size image. This was before I had the idea to use ISO-level-3 in
our ISO builds, which was eventually accepted to ubuntu-cdimage, and
future-proofed all Ubuntu (and flavor) images for many years to come as
it removed the 4GB file size limit on disk.

However, in this process, libreoffice-calc never got re-added to the
seed and this was an oversight.   This has been a large complaint from
our users and reviewers and we wish to rectify this prior to the release
of 22.04.1.

The rest of the libreoffice suite (sans base) is already installed, so
this shouldn't be a matter of additional dependencies as most, if not
all, are already present and seeded. Therefore, I hope this fix should
be trivial and that we should be allowed to proceed.

** Affects: ubuntustudio-meta (Ubuntu)
 Importance: Undecided
 Status: Fix Released

** Affects: ubuntustudio-meta (Ubuntu Jammy)
 Importance: High
 Assignee: Erich Eickmeyer  (eeickmeyer)
 Status: New

** Affects: ubuntustudio-meta (Ubuntu Kinetic)
 Importance: Undecided
 Status: Fix Released

** Also affects: ubuntustudio-meta (Ubuntu Jammy)
   Importance: Undecided
   Status: New

** Also affects: ubuntustudio-meta (Ubuntu Kinetic)
   Importance: Undecided
   Status: New

** Changed in: ubuntustudio-meta (Ubuntu Kinetic)
   Status: New => Fix Released

** Changed in: ubuntustudio-meta (Ubuntu Jammy)
 Assignee: (unassigned) => Erich Eickmeyer  (eeickmeyer)

** Changed in: ubuntustudio-meta (Ubuntu Jammy)
   Importance: Undecided => High

-- 
You received this bug notification because you are a member of Ubuntu
Studio Bugs, which is subscribed to ubuntustudio-meta in Ubuntu.
Matching subscriptions: UbuntuStudioPackages
https://bugs.launchpad.net/bugs/1980901

Title:
  [FFe] libreoffice-calc erroneously missing from ubuntustudio 22.04
  seed

Status in ubuntustudio-meta package in Ubuntu:
  Fix Released
Status in ubuntustudio-meta source package in Jammy:
  New
Status in ubuntustudio-meta source package in Kinetic:
  Fix Released

Bug description:
  During the effort before Feature Freeze for Jammy, the Ubuntu Studio
  team (with myself as lead) were scrambling with ideas to reduce the
  install size image. This was before I had the idea to use ISO-level-3
  in our ISO builds, which was eventually accepted to ubuntu-cdimage,
  and future-proofed all Ubuntu (and flavor) images for many years to
  come as it removed the 4GB file size limit on disk.

  However, in this process, libreoffice-calc never got re-added to the
  seed and this was an oversight.   This has been a large complaint from
  our users and reviewers and we wish to rectify this prior to the
  release of 22.04.1.

  The rest of the libreoffice suite (sans base) is already installed, so
  this shouldn't be a matter of additional dependencies as most, if not
  all, are already present and seeded. Therefore, I hope this fix should
  be trivial and that we should be allowed to proceed.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntustudio-meta/+bug/1980901/+subscriptions


-- 
Mailing list: https://launchpad.net/~ubuntustudio-bugs
Post to : ubuntustudio-bugs@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntustudio-bugs
More help   : https://help.launchpad.net/ListHelp

[Ubuntustudio-bugs] [Bug 1952949] Re: Studio controls hangs forever on "adding bridges"

2022-06-14 Thread Erich Eickmeyer 

Please don't necro-bump old bugs, file new bug reports.

-- 
You received this bug notification because you are a member of Ubuntu
Studio Bugs, which is subscribed to studio-controls in Ubuntu.
https://bugs.launchpad.net/bugs/1952949

Title:
  Studio controls hangs forever on "adding bridges"

Status in studio-controls package in Ubuntu:
  Fix Released

Bug description:
  I want to user studio-controls to run my jackd.

  But when doing that, Jack seems to start basically, but eventially
  it's status is displayed as "adding bridges" - and this doesn't change
  even after minutes of waiting.

  I have turned off any type of bridging - no midi, no pulse audio etc,
  so for one thing it's unclear what bridhges are to be added, and also
  why it hangs forever.

  I could not find any logfiles that give me any further information
  what's happening, running studio-controls in the terminal also doesnt
  show more information.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: studio-controls 2.2.8-0ubuntu0.21.10.1
  ProcVersionSignature: Ubuntu 5.13.0-21.21-lowlatency 5.13.18
  Uname: Linux 5.13.0-21-lowlatency x86_64
  ApportVersion: 2.20.11-0ubuntu71
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Dec  1 20:01:51 2021
  InstallationDate: Installed on 2020-04-12 (597 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  PackageArchitecture: all
  SourcePackage: studio-controls
  UpgradeStatus: Upgraded to impish on 2021-11-14 (16 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/studio-controls/+bug/1952949/+subscriptions


-- 
Mailing list: https://launchpad.net/~ubuntustudio-bugs
Post to : ubuntustudio-bugs@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntustudio-bugs
More help   : https://help.launchpad.net/ListHelp

[Ubuntustudio-bugs] [Bug 1978736] Re: Studio Controls stuck on "Adding Bridges" with "'int' object is not subscriptable"

2022-06-14 Thread Erich Eickmeyer 

This has been fixed in studio-controls 2.3.5 available from the Ubuntu
Studio Backports PPA. Please install that and report back.

** Changed in: studio-controls (Ubuntu)
   Status: New => Incomplete

-- 
You received this bug notification because you are a member of Ubuntu
Studio Bugs, which is subscribed to studio-controls in Ubuntu.
https://bugs.launchpad.net/bugs/1978736

Title:
  Studio Controls stuck on "Adding Bridges" with "'int' object is not
  subscriptable"

Status in studio-controls package in Ubuntu:
  Incomplete

Bug description:
  Studio Controls is hanging at the "Adding Bridges" phase.  (Unrelated
  to bug #1952949, which is resolved.)

  I am running Studio Controls version 2.3.4 on Ubuntu 22.04 LTS.
  Kernel version is Linux 5.15.0-37-lowlatency x86_64.

  I can start JACK fine from Qjackctl, but I was using Studio Controls
  because it adds Pulse bridges.  For a while this was failing
  intermittently.  Now it is failing every time.

  Here is the output from ~/.log/autojack.log:

2022-06-14 17:26:31,641 - AutoJack - INFO - Autojack started: logging 
started
2022-06-14 17:26:35,646 - AutoJack - DEBUG - Checking for phones plugged in
2022-06-14 17:26:36,191 - AutoJack - DEBUG - Checking phones device: PCH
2022-06-14 17:26:36,191 - AutoJack - DEBUG - Checking for phones with 
internal device
2022-06-14 17:26:36,193 - AutoJack - DEBUG - amixer command: 
/usr/bin/amixer -D hw:PCH cget iface=CARD,name='Headphone Jack'
2022-06-14 17:26:36,196 - AutoJack - DEBUG - amixer line: 
numid=16,iface=CARD,name='Headphone Jack'
  ; type=BOOLEAN,access=r---,values=1
2022-06-14 17:26:36,196 - AutoJack - DEBUG - amixer line: values=off
2022-06-14 17:26:36,196 - AutoJack - DEBUG - Changing Headphone to plugged 
in = False
2022-06-14 17:26:36,196 - AutoJack - DEBUG - Headphone port: 
PCH,0,0-out:playback_1
2022-06-14 17:26:36,198 - AutoJack - DEBUG - got signal - args: start
2022-06-14 17:26:36,198 - AutoJack - INFO - Got start signal.
2022-06-14 17:26:36,198 - AutoJack - INFO - Running: config_start()
2022-06-14 17:26:36,737 - AutoJack - DEBUG - phone port set to: 
PCH,0,0-out:playback_1
2022-06-14 17:26:38,739 - AutoJack - DEBUG - Running: config_start jack stat
2022-06-14 17:26:38,739 - AutoJack - INFO - Running: config_start after 
jack_stat
2022-06-14 17:26:38,742 - AutoJack - DEBUG - Pulseaudio: 
2022-06-14 17:26:39,745 - AutoJack - DEBUG - Pulseaudio: 
2022-06-14 17:26:42,801 - AutoJack - DEBUG - Kill old Procs: 
2022-06-14 17:26:42,807 - AutoJack - DEBUG - JACK is True restart pulse: 
/org/freedesktop/systemd1/job/1312
2022-06-14 17:26:42,808 - AutoJack - DEBUG - JACK is True start up jack
2022-06-14 17:26:43,079 - AutoJack - DEBUG - remove jackdbus_detect: 
2022-06-14 17:26:43,079 - AutoJack - DEBUG - Found previous jack config 
removing
2022-06-14 17:26:43,093 - AutoJack - DEBUG - JACK driver set to: alsa
2022-06-14 17:26:43,494 - AutoJack - DEBUG - JACK device set to: USB,0,0
2022-06-14 17:26:44,497 - AutoJack - DEBUG - JACK rate/period/nperiods set 
to: 48000/512/2
2022-06-14 17:26:47,628 - AutoJack - DEBUG - JACK started
2022-06-14 17:26:50,631 - AutoJack - DEBUG - create jack client
2022-06-14 17:26:50,658 - AutoJack - DEBUG - jack client created
2022-06-14 17:26:51,695 - AutoJack - DEBUG - Pulseaudio: 24
2022-06-14 17:26:52,729 - AutoJack - DEBUG - Pulseaudio: 25
2022-06-14 17:26:53,732 - AutoJack - DEBUG - remove module-udev-detect: 
2022-06-14 17:26:54,735 - AutoJack - DEBUG - remove module-alsa-card: 
2022-06-14 17:26:55,735 - AutoJack - DEBUG - updating extra devices
2022-06-14 17:26:56,782 - AutoJack - DEBUG - checking: PCH,0,0 channel 
counts: 100 100 card: 0
2022-06-14 17:26:56,782 - AutoJack - DEBUG - Start slave: PCH,0,0
2022-06-14 17:26:57,322 - AutoJack - ERROR - Exception in handler for D-Bus 
signal:
Traceback (most recent call last):
  File "/usr/lib/python3/dist-packages/dbus/connection.py", line 232, in 
maybe_handle_message
self._handler(*args, **kwargs)
  File "/usr/bin/autojack", line 1739, in ses_cb_command
config_start()
  File "/usr/bin/autojack", line 819, in config_start
extra_devices()
  File "/usr/bin/autojack", line 142, in extra_devices
start_slave(fullname)
  File "/usr/bin/autojack", line 1364, in start_slave
dsr = sub_db['frame']['rate']
TypeError: 'int' object is not subscriptable
2022-06-14 17:26:57,323 - AutoJack - DEBUG - Connection changed
2022-06-14 17:26:57,323 - AutoJack - DEBUG - moving connections from 
system:playback_1 to none
2022-06-14 17:26:57,324 - AutoJack - DEBUG - Jack port: none not found

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/studio-controls/+bug/1978736/+subscriptions


-- 
Mailing list: https://launchpad.net/~ubuntustudio-bugs
Post to :

[Ubuntustudio-bugs] [Bug 1969798] Re: Carla can't find plugins in plugin directories located in the user's home

2022-07-19 Thread Erich Eickmeyer 

Working with upstream on this one, he was able to release 2.4.4 as a bug
fix. Will upload to Kinetic and hopefully we can do a backport of this
per his request. But yes, 2.4.3 FTBFS on Kinetic.

** Tags removed: verification-needed verification-needed-jammy
** Tags added: verification-failed verification-failed-jammy

-- 
You received this bug notification because you are a member of Ubuntu
Studio Bugs, which is subscribed to carla in Ubuntu.
https://bugs.launchpad.net/bugs/1969798

Title:
  Carla can't find plugins in plugin directories located in the user's
  home

Status in carla package in Ubuntu:
  Triaged
Status in carla source package in Jammy:
  Triaged
Status in carla source package in Kinetic:
  Triaged

Bug description:
  [Impact]

  Users of Carla are unable to refresh audio plugins when more are
  installed, i.e. in the user's home directory. Furthermore, this can
  cause Carla to crash.

  [Test Plan]

   * Launch Carla
   * Click "Add Plugin"
   * Click "Refresh"
   * Click "Scan"
   
   Expected: Carla will scan for new plugins and find them.

   Actual: Carla does not scan for plugins, and may crash.

  [Where problems could occur]

   * The patch may just plain not work, in which case we may have to do
  a wholesale upload of Carla 2.4.3 instead as opposed to simply
  patching 2.4.2 with the cherry-picked commit as uploaded.

   * The other thing this might do is cause the application to cease to
  function, though this is highly unlikely.

  [Other Info]
   
  Original bug report as follows:
  --

  In the LV2 location in my home directory .lv2 I have the following
  plugin:

  ➜ ls ~/.lv2
  librnnoise_lv2.so

  ${HOME}/.lv2 is configured in Carla as a search path.

  In the Add Plugin dialog for Carla if I search for noise nothing shows
  up.

  This worked fine previously on 21.10.

  Release notes for Carla 2.4.3 [1] include this line: Fix plugin search
  (regression from 2.4.2)

  Ubuntu Studio 22.04 currently has the bugged version:

  ➜ carla --version
  Using Carla version 2.4.2

  [1] https://github.com/falkTX/Carla/releases/tag/v2.4.3

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: carla 2.4.2-0ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-24.24-lowlatency 5.15.30
  Uname: Linux 5.15.0-24-lowlatency x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: KDE
  Date: Thu Apr 21 15:41:13 2022
  InstallationDate: Installed on 2022-04-20 (1 days ago)
  InstallationMedia: Ubuntu-Studio 22.04 LTS "Jammy Jellyfish" - Beta amd64 
(20220329.1)
  SourcePackage: carla
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/carla/+bug/1969798/+subscriptions


-- 
Mailing list: https://launchpad.net/~ubuntustudio-bugs
Post to : ubuntustudio-bugs@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntustudio-bugs
More help   : https://help.launchpad.net/ListHelp

[Ubuntustudio-bugs] [Bug 1980901] Re: [SRU] [FFe] libreoffice-calc erroneously missing from ubuntustudio 22.04 seed

2022-07-14 Thread Erich Eickmeyer 

** Changed in: ubuntustudio-meta (Ubuntu Jammy)
   Status: Triaged => In Progress

** Description changed:

  [ Impact ]
  
-  * Ubuntu Studio had previously carried libreoffice-calc as part of its
+  * Ubuntu Studio had previously carried libreoffice-calc as part of its
  default installation and as part of the ubuntustudio-desktop
  metapackage. However, as part of missing libreoffice-calc in the seed
  (see Original FFe Request below), it was also missed in the
  ubuntustudio-desktop metapackage.
  
-  * There have been numerous complaints from users and reviewers about
+  * There have been numerous complaints from users and reviewers about
  the omission of libreoffice-calc. This SRU attempts to rectify the
  situation.
  
  [ Test Plan ]
  
-  * Install (or try) Ubuntu Studio 22.04.1
+  * Install (or try) Ubuntu Studio 22.04
  
-  * Notice Libreoffice Calc is not installed
+  * Notice Libreoffice Calc is not installed
  
  [ Where Problems Could Occur ]
  
-  * Users may not be expecting an update to bring them libreoffice-calc,
+  * Users may not be expecting an update to bring them libreoffice-calc,
  however, this will be shown to them during their update whether that be
  via plasma-discover, apt update, or other means.
  
  [ Other Info ]
  
  [ Original FFe Request ]
  
  During the effort before Feature Freeze for Jammy, the Ubuntu Studio
  team (with myself as lead) were scrambling with ideas to reduce the
  install size image. This was before I had the idea to use ISO-level-3 in
  our ISO builds, which was eventually accepted to ubuntu-cdimage, and
  future-proofed all Ubuntu (and flavor) images for many years to come as
  it removed the 4GB file size limit on disk.
  
  However, in this process, libreoffice-calc never got re-added to the
  seed and this was an oversight.   This has been a large complaint from
  our users and reviewers and we wish to rectify this prior to the release
  of 22.04.1.
  
  The rest of the libreoffice suite (sans base) is already installed, so
  this shouldn't be a matter of additional dependencies as most, if not
  all, are already present and seeded. Therefore, I hope this fix should
  be trivial and that we should be allowed to proceed.

-- 
You received this bug notification because you are a member of Ubuntu
Studio Bugs, which is subscribed to ubuntustudio-meta in Ubuntu.
Matching subscriptions: UbuntuStudioPackages
https://bugs.launchpad.net/bugs/1980901

Title:
  [SRU] [FFe] libreoffice-calc erroneously missing from ubuntustudio
  22.04 seed

Status in ubuntustudio-meta package in Ubuntu:
  Fix Released
Status in ubuntustudio-meta source package in Jammy:
  In Progress
Status in ubuntustudio-meta source package in Kinetic:
  Fix Released

Bug description:
  [ Impact ]

   * Ubuntu Studio had previously carried libreoffice-calc as part of
  its default installation and as part of the ubuntustudio-desktop
  metapackage. However, as part of missing libreoffice-calc in the seed
  (see Original FFe Request below), it was also missed in the
  ubuntustudio-desktop metapackage.

   * There have been numerous complaints from users and reviewers about
  the omission of libreoffice-calc. This SRU attempts to rectify the
  situation.

  [ Test Plan ]

   * Install (or try) Ubuntu Studio 22.04

   * Notice Libreoffice Calc is not installed

  [ Where Problems Could Occur ]

   * Users may not be expecting an update to bring them libreoffice-
  calc, however, this will be shown to them during their update whether
  that be via plasma-discover, apt update, or other means.

  [ Other Info ]

  [ Original FFe Request ]

  During the effort before Feature Freeze for Jammy, the Ubuntu Studio
  team (with myself as lead) were scrambling with ideas to reduce the
  install size image. This was before I had the idea to use ISO-level-3
  in our ISO builds, which was eventually accepted to ubuntu-cdimage,
  and future-proofed all Ubuntu (and flavor) images for many years to
  come as it removed the 4GB file size limit on disk.

  However, in this process, libreoffice-calc never got re-added to the
  seed and this was an oversight.   This has been a large complaint from
  our users and reviewers and we wish to rectify this prior to the
  release of 22.04.1.

  The rest of the libreoffice suite (sans base) is already installed, so
  this shouldn't be a matter of additional dependencies as most, if not
  all, are already present and seeded. Therefore, I hope this fix should
  be trivial and that we should be allowed to proceed.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntustudio-meta/+bug/1980901/+subscriptions


-- 
Mailing list: https://launchpad.net/~ubuntustudio-bugs
Post to : ubuntustudio-bugs@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntustudio-bugs
More help   : https://help.launchpad.net/ListHelp

[Ubuntustudio-bugs] [Bug 1980901] Re: [FFe] libreoffice-calc erroneously missing from ubuntustudio 22.04 seed

2022-07-14 Thread Erich Eickmeyer 

** Description changed:

+ [ Impact ]
+ 
+  * Ubuntu Studio had previously carried libreoffice-calc as part of its
+ default installation and as part of the ubuntustudio-desktop
+ metapackage. However, as part of missing libreoffice-calc in the seed
+ (see Original FFe Request below), it was also missed in the
+ ubuntustudio-desktop metapackage.
+ 
+  * There have been numerous complaints from users and reviewers about
+ the omission of libreoffice-calc. This SRU attempts to rectify the
+ situation.
+ 
+ [ Test Plan ]
+ 
+  * Install (or try) Ubuntu Studio 22.04.1
+ 
+  * Notice Libreoffice Calc is not installed
+ 
+ [ Where Problems Could Occur ]
+ 
+  * Users may not be expecting an update to bring them libreoffice-calc,
+ however, this will be shown to them during their update whether that be
+ via plasma-discover, apt update, or other means.
+ 
+ [ Other Info ]
+ 
+ [ Original FFe Request ]
+ 
  During the effort before Feature Freeze for Jammy, the Ubuntu Studio
  team (with myself as lead) were scrambling with ideas to reduce the
  install size image. This was before I had the idea to use ISO-level-3 in
  our ISO builds, which was eventually accepted to ubuntu-cdimage, and
  future-proofed all Ubuntu (and flavor) images for many years to come as
  it removed the 4GB file size limit on disk.
  
  However, in this process, libreoffice-calc never got re-added to the
  seed and this was an oversight.   This has been a large complaint from
  our users and reviewers and we wish to rectify this prior to the release
  of 22.04.1.
  
  The rest of the libreoffice suite (sans base) is already installed, so
  this shouldn't be a matter of additional dependencies as most, if not
  all, are already present and seeded. Therefore, I hope this fix should
  be trivial and that we should be allowed to proceed.

** Summary changed:

- [FFe] libreoffice-calc erroneously missing from ubuntustudio 22.04 seed
+ [SRU] [FFe] libreoffice-calc erroneously missing from ubuntustudio 22.04 seed

-- 
You received this bug notification because you are a member of Ubuntu
Studio Bugs, which is subscribed to ubuntustudio-meta in Ubuntu.
Matching subscriptions: UbuntuStudioPackages
https://bugs.launchpad.net/bugs/1980901

Title:
  [SRU] [FFe] libreoffice-calc erroneously missing from ubuntustudio
  22.04 seed

Status in ubuntustudio-meta package in Ubuntu:
  Fix Released
Status in ubuntustudio-meta source package in Jammy:
  Triaged
Status in ubuntustudio-meta source package in Kinetic:
  Fix Released

Bug description:
  [ Impact ]

   * Ubuntu Studio had previously carried libreoffice-calc as part of
  its default installation and as part of the ubuntustudio-desktop
  metapackage. However, as part of missing libreoffice-calc in the seed
  (see Original FFe Request below), it was also missed in the
  ubuntustudio-desktop metapackage.

   * There have been numerous complaints from users and reviewers about
  the omission of libreoffice-calc. This SRU attempts to rectify the
  situation.

  [ Test Plan ]

   * Install (or try) Ubuntu Studio 22.04.1

   * Notice Libreoffice Calc is not installed

  [ Where Problems Could Occur ]

   * Users may not be expecting an update to bring them libreoffice-
  calc, however, this will be shown to them during their update whether
  that be via plasma-discover, apt update, or other means.

  [ Other Info ]

  [ Original FFe Request ]

  During the effort before Feature Freeze for Jammy, the Ubuntu Studio
  team (with myself as lead) were scrambling with ideas to reduce the
  install size image. This was before I had the idea to use ISO-level-3
  in our ISO builds, which was eventually accepted to ubuntu-cdimage,
  and future-proofed all Ubuntu (and flavor) images for many years to
  come as it removed the 4GB file size limit on disk.

  However, in this process, libreoffice-calc never got re-added to the
  seed and this was an oversight.   This has been a large complaint from
  our users and reviewers and we wish to rectify this prior to the
  release of 22.04.1.

  The rest of the libreoffice suite (sans base) is already installed, so
  this shouldn't be a matter of additional dependencies as most, if not
  all, are already present and seeded. Therefore, I hope this fix should
  be trivial and that we should be allowed to proceed.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntustudio-meta/+bug/1980901/+subscriptions


-- 
Mailing list: https://launchpad.net/~ubuntustudio-bugs
Post to : ubuntustudio-bugs@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntustudio-bugs
More help   : https://help.launchpad.net/ListHelp

[Ubuntustudio-bugs] [Bug 1980901] Re: [FFe] libreoffice-calc erroneously missing from ubuntustudio 22.04 seed

2022-07-14 Thread Erich Eickmeyer 

Łukasz,

Yes, libreoffic-calc was preinstalled in all series prior to 22.04.
Thanks for your approval, I'll commit the seed change and write-up the
SRU for the ubuntustudio-meta package itself shortly.

-- 
You received this bug notification because you are a member of Ubuntu
Studio Bugs, which is subscribed to ubuntustudio-meta in Ubuntu.
Matching subscriptions: UbuntuStudioPackages
https://bugs.launchpad.net/bugs/1980901

Title:
  [FFe] libreoffice-calc erroneously missing from ubuntustudio 22.04
  seed

Status in ubuntustudio-meta package in Ubuntu:
  Fix Released
Status in ubuntustudio-meta source package in Jammy:
  Triaged
Status in ubuntustudio-meta source package in Kinetic:
  Fix Released

Bug description:
  During the effort before Feature Freeze for Jammy, the Ubuntu Studio
  team (with myself as lead) were scrambling with ideas to reduce the
  install size image. This was before I had the idea to use ISO-level-3
  in our ISO builds, which was eventually accepted to ubuntu-cdimage,
  and future-proofed all Ubuntu (and flavor) images for many years to
  come as it removed the 4GB file size limit on disk.

  However, in this process, libreoffice-calc never got re-added to the
  seed and this was an oversight.   This has been a large complaint from
  our users and reviewers and we wish to rectify this prior to the
  release of 22.04.1.

  The rest of the libreoffice suite (sans base) is already installed, so
  this shouldn't be a matter of additional dependencies as most, if not
  all, are already present and seeded. Therefore, I hope this fix should
  be trivial and that we should be allowed to proceed.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntustudio-meta/+bug/1980901/+subscriptions


-- 
Mailing list: https://launchpad.net/~ubuntustudio-bugs
Post to : ubuntustudio-bugs@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntustudio-bugs
More help   : https://help.launchpad.net/ListHelp

[Ubuntustudio-bugs] [Bug 1904266] Re: calamares data entry; cursor jumps to end of field making editing difficult

2022-07-28 Thread Erich Eickmeyer 

** Also affects: calamares (Ubuntu Jammy)
   Importance: Undecided
   Status: New

** Also affects: calamares (Ubuntu Kinetic)
   Importance: Undecided
   Status: Confirmed

** Changed in: calamares (Ubuntu Kinetic)
   Status: Confirmed => Fix Released

** Changed in: calamares (Ubuntu Jammy)
   Status: New => Fix Committed

-- 
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/1904266

Title:
  calamares data entry; cursor jumps to end of field making editing
  difficult

Status in Calamares:
  Fix Released
Status in calamares package in Ubuntu:
  Fix Released
Status in calamares source package in Jammy:
  Fix Committed
Status in calamares source package in Kinetic:
  Fix Released

Bug description:
  Lubuntu hirsute daily QA-test install, two boxes
  - dell [optiplex] 755 (c2d-e8300, 8gb, amd/ati radeon rv610/radeon hd2400 
pro/xt)
  - hp dc7700 (c2d-e6320, 5gb, nvidia quadro nvs 290)

  ** To re-create

  Start an install, get to the "user setup" entry fields where you enter
  "name, username, hostname, password.."

  Enter values.. I noticed this on HOSTNAME.

  Going to the hostname field, it was pre-loaded with something from the
  box firmware itself, I tried amending this..

  ** Expected behavior

  Assume the hostname is preloaded with

  "hpcompaqdc7700"

  I move the cursor to the beginning of the field, with intention of
  adding "blah" to the start of it.

  I expect either "blahhpcompaqdc7700" (inserted) or "blahmpaqdc7700"
  (replaced)

  ** Actual behavior

  Instead I get the "bhpcompaqdc7700lah"

  because on entry of the first character "b" of "blah", the cursor
  jumps to the end of the field for the subsequent characters.

  This is occurring anywhere in the field (cursor jumps to the end after
  typing a letter).

  I've NOT noticed this behavior before.  It's annoying only (easily
  worked around)

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: calamares 3.2.32.1-0ubuntu1
  ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14
  Uname: Linux 5.8.0-25-generic x86_64
  .etc.calamares.modules.finished.conf:
   ---
   restartNowMode: user-checked
   restartNowCommand: "systemctl -i reboot"
  .etc.calamares.modules.partition.conf:
   efiSystemPartition: "/boot/efi"
   enableLuksAutomatedPartitioning: true
   userSwapChoices: none
   drawNestedPartitions: true
   defaultFileSystemType: "ext4"
  .etc.calamares.modules.shellprocess_logs.conf:
   ---
   dontChroot: true
   timeout: 30
   script:
   - calamares-logs-helper @@ROOT@@
  .etc.calamares.modules.unpackfs.conf:
   ---
   unpack:
   -   source: "/cdrom/casper/filesystem.squashfs"
   sourcefs: "squashfs"
   destination: ""
  ApportVersion: 2.20.11-0ubuntu51
  Architecture: amd64
  CasperMD5CheckResult: pass
  CasperVersion: 1.455
  CurrentDesktop: LXQt
  Date: Sat Nov 14 20:31:08 2020
  LiveMediaBuild: Lubuntu 21.04 "Hirsute Hippo" - Alpha amd64 (20201113)
  RelatedPackageVersions:
   calamares-settings-ubuntu-common 1:20.10.11
   calamares-settings-lubuntu   1:20.10.11
   xfsprogs 5.6.0-1ubuntu4
   btrfs-progs  5.9-1
  SourcePackage: calamares
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/calamares/+bug/1904266/+subscriptions


-- 
Mailing list: https://launchpad.net/~ubuntustudio-bugs
Post to : ubuntustudio-bugs@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntustudio-bugs
More help   : https://help.launchpad.net/ListHelp

[Ubuntustudio-bugs] [Bug 1983136] [NEW] [SRU] v4l2loopback-dkms breaks secure boot installation in seed

2022-07-29 Thread Erich Eickmeyer 

Public bug reported:

[Impact]

 * For users installing Ubuntu Studio 22.04 LTS on secure boot machines,
this is currently not possible as v4l2loopback-dkms is currently seeded.

 * When v4l2loopback-dkms attempts to compile during installation on a
secure boot machine without user interaction with calamares, it
completely fails and the system installation fails.

 * In order to proceed, v4l2loopback-dkms must be removed from the seed
and the ubuntustudio-video meta.

 * This was recently discovered while working with the Lubuntu team and
undergoing extensive testing with the new Calamares. While it was not an
issue with Calamares, it did point to the issue with v4l2loopback and
explained some complaints received in the #ubuntustudio IRC chat.

[Test Plan]

 * Download Ubuntu Studio 22.04 ISO image.

 * Attempt to install on machine with Secure Boot enabled.

 * Installation will fail when v4l2loopback-dkms modules attempt to
compile and install to kernel.

[Where problems could occur]

 * Problems can occur when existing users update and end up with
v4l2loopback-dkms marked as autoremovable and run 'sudo apt autoremove',
which will unexpectedly remove this package from their system.
Unfortunately, there's no good way to mitigate this except to advise to
reinstall this package.

** Affects: ubuntustudio-meta (Ubuntu)
 Importance: Undecided
 Status: New

** Affects: ubuntustudio-meta (Ubuntu Jammy)
 Importance: Undecided
 Status: New

** Affects: ubuntustudio-meta (Ubuntu Kinetic)
 Importance: Undecided
 Status: New

** Also affects: ubuntustudio-meta (Ubuntu Jammy)
   Importance: Undecided
   Status: New

** Also affects: ubuntustudio-meta (Ubuntu Kinetic)
   Importance: Undecided
   Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Studio Bugs, which is subscribed to ubuntustudio-meta in Ubuntu.
Matching subscriptions: UbuntuStudioPackages
https://bugs.launchpad.net/bugs/1983136

Title:
  [SRU] v4l2loopback-dkms breaks secure boot installation in seed

Status in ubuntustudio-meta package in Ubuntu:
  New
Status in ubuntustudio-meta source package in Jammy:
  New
Status in ubuntustudio-meta source package in Kinetic:
  New

Bug description:
  [Impact]

   * For users installing Ubuntu Studio 22.04 LTS on secure boot
  machines, this is currently not possible as v4l2loopback-dkms is
  currently seeded.

   * When v4l2loopback-dkms attempts to compile during installation on a
  secure boot machine without user interaction with calamares, it
  completely fails and the system installation fails.

   * In order to proceed, v4l2loopback-dkms must be removed from the
  seed and the ubuntustudio-video meta.

   * This was recently discovered while working with the Lubuntu team
  and undergoing extensive testing with the new Calamares. While it was
  not an issue with Calamares, it did point to the issue with
  v4l2loopback and explained some complaints received in the
  #ubuntustudio IRC chat.

  [Test Plan]

   * Download Ubuntu Studio 22.04 ISO image.

   * Attempt to install on machine with Secure Boot enabled.

   * Installation will fail when v4l2loopback-dkms modules attempt to
  compile and install to kernel.

  [Where problems could occur]

   * Problems can occur when existing users update and end up with
  v4l2loopback-dkms marked as autoremovable and run 'sudo apt
  autoremove', which will unexpectedly remove this package from their
  system. Unfortunately, there's no good way to mitigate this except to
  advise to reinstall this package.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntustudio-meta/+bug/1983136/+subscriptions


-- 
Mailing list: https://launchpad.net/~ubuntustudio-bugs
Post to : ubuntustudio-bugs@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntustudio-bugs
More help   : https://help.launchpad.net/ListHelp

[Ubuntustudio-bugs] [Bug 1248174] Re: Update the Ubuntu colour palette to fit the spec

2022-07-22 Thread Erich Eickmeyer 

I can see this might start getting out of hand so I'm going to be the
referee here.

Luis, you cannot force someone to work on a bug report.

Alberto, since you're unwilling or unable to confirm, please keep the
report as incomplete for gimp.

To maintain a respectful atmosphere, please follow the code of conduct -
http://www.ubuntu.com/project/about-ubuntu/conduct. Bug reports are
handled by humans, the majority of whom are volunteers, so please bear
this in mind.

-- 
You received this bug notification because you are a member of Ubuntu
Studio Bugs, which is subscribed to inkscape in Ubuntu.
Matching subscriptions: Ubuntu Studio Bugs
https://bugs.launchpad.net/bugs/1248174

Title:
  Update the Ubuntu colour palette to fit the spec

Status in One Hundred Papercuts:
  Triaged
Status in Inkscape:
  Fix Released
Status in Ubuntu Accomplishments Daemon:
  Confirmed
Status in Ubuntu Accomplishments Extra Information:
  Confirmed
Status in Ubuntu Accomplishments System:
  Confirmed
Status in Ubuntu Accomplishments Viewer:
  Confirmed
Status in Ubuntu Accomplishments Web Gallery:
  Confirmed
Status in Ubuntu Brand Guidelines website:
  Invalid
Status in ubuntu-community:
  Fix Released
Status in Ubuntu Community Accomplishments:
  Confirmed
Status in Ubuntu Desktop Accomplishments:
  Confirmed
Status in gimp package in Ubuntu:
  Incomplete
Status in inkscape package in Ubuntu:
  Fix Released
Status in libreoffice package in Ubuntu:
  Fix Released

Bug description:
  
  HOW TO REPRODUCE
  

  1. In Inkscape create a figure colored "Accent Orange", from the "Ubuntu" 
colour palette.
  2. Compare colour with "Ubuntu Orange" in 
http://design.ubuntu.com/brand/colour-palette.

  **
  EXPECTED BEHAVIOUR
  **

  - The colour to be the same.

  **
  REAL BEHAVIOUR
  **

  - The colour is different.
  - The colours listed in the palette from Inkscape have no relationship with 
the ones in design.ubuntu.com.

  ***
  WORK-AROUND
  ***

  - To use the colours in http://design.ubuntu.com/brand/colour-palette
  instead.

  
  RELEVANT DETAILS
  

  - Orange colour is very similar, but not equal. So it's very probable someone 
use the wrong colour in their designs for Ubuntu.
  - In fact, the logo of "Ubuntu" project in Launchpad is affected 
(https://launchpad.net/ubuntu).
  - A demonstrative image is attached to this bug.

  **
  TECHNICAL INFO
  **

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: inkscape 0.48.4-1ubuntu3
  ProcVersionSignature: Ubuntu 3.8.0-25.37-generic 3.8.13
  Uname: Linux 3.8.0-25-generic x86_64
  ApportVersion: 2.12.5-0ubuntu2.1
  Architecture: amd64
  Date: Tue Nov  5 13:47:52 2013
  InstallationDate: Installed on 2013-05-21 (167 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  MarkForUpload: True
  SourcePackage: inkscape
  UpgradeStatus: Upgraded to saucy on 2013-10-18 (18 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/hundredpapercuts/+bug/1248174/+subscriptions


-- 
Mailing list: https://launchpad.net/~ubuntustudio-bugs
Post to : ubuntustudio-bugs@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntustudio-bugs
More help   : https://help.launchpad.net/ListHelp

[Ubuntustudio-bugs] [Bug 1980901] Re: [SRU] [FFe] libreoffice-calc erroneously missing from ubuntustudio 22.04 seed

2022-07-19 Thread Erich Eickmeyer 

ubuntustudio-desktop 0.266.1 does indeed bring back libreoffice-calc as
expected.

** Tags removed: verification-needed verification-needed-jammy
** Tags added: verification-done verification-done-jammy

-- 
You received this bug notification because you are a member of Ubuntu
Studio Bugs, which is subscribed to ubuntustudio-meta in Ubuntu.
Matching subscriptions: UbuntuStudioPackages
https://bugs.launchpad.net/bugs/1980901

Title:
  [SRU] [FFe] libreoffice-calc erroneously missing from ubuntustudio
  22.04 seed

Status in ubuntustudio-meta package in Ubuntu:
  Fix Released
Status in ubuntustudio-meta source package in Jammy:
  Fix Committed
Status in ubuntustudio-meta source package in Kinetic:
  Fix Released

Bug description:
  [ Impact ]

   * Ubuntu Studio had previously carried libreoffice-calc as part of
  its default installation and as part of the ubuntustudio-desktop
  metapackage. However, as part of missing libreoffice-calc in the seed
  (see Original FFe Request below), it was also missed in the
  ubuntustudio-desktop metapackage.

   * There have been numerous complaints from users and reviewers about
  the omission of libreoffice-calc. This SRU attempts to rectify the
  situation.

  [ Test Plan ]

   * Install (or try) Ubuntu Studio 22.04

   * Notice Libreoffice Calc is not installed

  [ Where Problems Could Occur ]

   * Users may not be expecting an update to bring them libreoffice-
  calc, however, this will be shown to them during their update whether
  that be via plasma-discover, apt update, or other means.

  [ Other Info ]

  [ Original FFe Request ]

  During the effort before Feature Freeze for Jammy, the Ubuntu Studio
  team (with myself as lead) were scrambling with ideas to reduce the
  install size image. This was before I had the idea to use ISO-level-3
  in our ISO builds, which was eventually accepted to ubuntu-cdimage,
  and future-proofed all Ubuntu (and flavor) images for many years to
  come as it removed the 4GB file size limit on disk.

  However, in this process, libreoffice-calc never got re-added to the
  seed and this was an oversight.   This has been a large complaint from
  our users and reviewers and we wish to rectify this prior to the
  release of 22.04.1.

  The rest of the libreoffice suite (sans base) is already installed, so
  this shouldn't be a matter of additional dependencies as most, if not
  all, are already present and seeded. Therefore, I hope this fix should
  be trivial and that we should be allowed to proceed.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntustudio-meta/+bug/1980901/+subscriptions


-- 
Mailing list: https://launchpad.net/~ubuntustudio-bugs
Post to : ubuntustudio-bugs@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntustudio-bugs
More help   : https://help.launchpad.net/ListHelp

[Ubuntustudio-bugs] [Bug 1970270] Re: LibreOffice localization is not working out of the box

If the problem (and solution) is in /etc/calamares/modules/mount.conf,
then this is an improperly filed bug and needs to be filed against
calamares-settings-ubuntu, don't you think? Not the metas.

-- 
You received this bug notification because you are a member of Ubuntu
Studio Bugs, which is subscribed to ubuntustudio-meta in Ubuntu.
Matching subscriptions: UbuntuStudioPackages
https://bugs.launchpad.net/bugs/1970270

Title:
  LibreOffice localization is not working out of the box

Status in lubuntu-meta package in Ubuntu:
  New
Status in ubuntustudio-meta package in Ubuntu:
  New

Bug description:
  Using Lubuntu 22.04 within a virtual machine made using virt-manager,
  KVM, and QEMU.

  When Lubuntu 22.04 is installed in a language other than English, the
  LibreOffice UI displays in English, despite the user's language
  choice. The issue can be worked around by running "sudo apt update"
  followed by "sudo apt install libreoffice-l10n-", where 
  is replaced with the 2-character language code (for example, de or
  fr). This will cause LibreOffice to display in the correct language.

  I have tested using both German and French language options at install
  time - the problem exists in both scenarios.

  Reproducibility: 100%

  Steps to reproduce (edited to be more precise):

  1: Open virt-manager.
  2: Add a connection to "QEMU User session".
  3: Create a new virtual machine under "QEMU User session". I set the OS as 
"Ubuntu 21.04", since that's the newest version of Ubuntu that my version of 
virt-manager supports. I gave the VM 20 GB of hard drive space, 4 GB of RAM, 
and 2 CPU cores. I didn't make any other customizations.
  4: Once the VM is running, select "Try or install Lubuntu" in the GRUB prompt.
  5: Once Lubuntu is done booting, double-click "Install Lubuntu 22.04".
  6: At the first screen of the installation, select a language other than 
American English. I tried using German and French, and they both reproduced the 
issue.
  7: Use the default keyboard settings for your chosen language.
  8: Use the "Erase disk" option when choosing where to install Lubuntu.
  9: Set your name as "User", your username as "user", your computer name as 
"user-germantest", and your password as "z". I also enabled automatic login 
here.
  10: Wait for the installation to finish, then reboot.
  11: Open LibreOffice Writer.

  Expected result: The UI should be displayed in the language selected
  at install time.

  Actual result: The UI displays in English, regardless of the language
  selected at install time.

  Additional notes:

  I am using LibreOffice version 7.3.2 within the VM. I am using fully-
  updated Ubuntu Studio 21.10 as the host OS.

  Prior to running "sudo apt update", there are no LibreOffice
  localization packages available in apt (as verified by doing "apt-
  cache search l10n"). After the update, the packages appear.

  I have not yet tested Ubuntu 22.04 for this problem, so I do not know
  if this applies to Ubuntu as a whole, or to Lubuntu alone. I do intend
  to test this in the near future.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lubuntu-meta/+bug/1970270/+subscriptions


-- 
Mailing list: https://launchpad.net/~ubuntustudio-bugs
Post to : ubuntustudio-bugs@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntustudio-bugs
More help   : https://help.launchpad.net/ListHelp

[Ubuntustudio-bugs] [Bug 1970270] Re: LibreOffice localization is not working out of the box

Let's keep the lubuntu tag and add ubuntustudio since it affects us as
well. Ubuntu Studio and Lubuntu use Calamares for an installer, all
others use Ubiquity.

** Tags added: lubuntu ubuntustudio

-- 
You received this bug notification because you are a member of Ubuntu
Studio Bugs, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1970270

Title:
  LibreOffice localization is not working out of the box

Status in calamares-settings-ubuntu package in Ubuntu:
  Confirmed
Status in calamares-settings-ubuntu source package in Impish:
  Won't Fix
Status in calamares-settings-ubuntu source package in Jammy:
  Confirmed
Status in calamares-settings-ubuntu source package in Kinetic:
  Confirmed

Bug description:
  Using Lubuntu 22.04 within a virtual machine made using virt-manager,
  KVM, and QEMU.

  When Lubuntu 22.04 is installed in a language other than English, the
  LibreOffice UI displays in English, despite the user's language
  choice. The issue can be worked around by running "sudo apt update"
  followed by "sudo apt install libreoffice-l10n-", where 
  is replaced with the 2-character language code (for example, de or
  fr). This will cause LibreOffice to display in the correct language.

  I have tested using both German and French language options at install
  time - the problem exists in both scenarios.

  Reproducibility: 100%

  Steps to reproduce (edited to be more precise):

  1: Open virt-manager.
  2: Add a connection to "QEMU User session".
  3: Create a new virtual machine under "QEMU User session". I set the OS as 
"Ubuntu 21.04", since that's the newest version of Ubuntu that my version of 
virt-manager supports. I gave the VM 20 GB of hard drive space, 4 GB of RAM, 
and 2 CPU cores. I didn't make any other customizations.
  4: Once the VM is running, select "Try or install Lubuntu" in the GRUB prompt.
  5: Once Lubuntu is done booting, double-click "Install Lubuntu 22.04".
  6: At the first screen of the installation, select a language other than 
American English. I tried using German and French, and they both reproduced the 
issue.
  7: Use the default keyboard settings for your chosen language.
  8: Use the "Erase disk" option when choosing where to install Lubuntu.
  9: Set your name as "User", your username as "user", your computer name as 
"user-germantest", and your password as "z". I also enabled automatic login 
here.
  10: Wait for the installation to finish, then reboot.
  11: Open LibreOffice Writer.

  Expected result: The UI should be displayed in the language selected
  at install time.

  Actual result: The UI displays in English, regardless of the language
  selected at install time.

  Additional notes:

  I am using LibreOffice version 7.3.2 within the VM. I am using fully-
  updated Ubuntu Studio 21.10 as the host OS.

  Prior to running "sudo apt update", there are no LibreOffice
  localization packages available in apt (as verified by doing "apt-
  cache search l10n"). After the update, the packages appear.

  I have not yet tested Ubuntu 22.04 for this problem, so I do not know
  if this applies to Ubuntu as a whole, or to Lubuntu alone. I do intend
  to test this in the near future.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/calamares-settings-ubuntu/+bug/1970270/+subscriptions


-- 
Mailing list: https://launchpad.net/~ubuntustudio-bugs
Post to : ubuntustudio-bugs@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntustudio-bugs
More help   : https://help.launchpad.net/ListHelp

[Ubuntustudio-bugs] [Bug 1970270] Re: LibreOffice localization is not working out of the box

Yes, they absolutely should be removed because they have absolutely no
bearing on this.

** No longer affects: ubuntustudio-meta (Ubuntu)

** No longer affects: lubuntu-meta (Ubuntu)

** Changed in: calamares-settings-ubuntu (Ubuntu)
Status: New => Confirmed

** Changed in: calamares-settings-ubuntu (Ubuntu)
Importance: Undecided => High

** Also affects: calamares-settings-ubuntu (Ubuntu Impish)
Importance: Undecided
Status: New

** Also affects: calamares-settings-ubuntu (Ubuntu Kinetic)
Importance: High
Status: Confirmed

** Also affects: calamares-settings-ubuntu (Ubuntu Jammy)
Importance: Undecided
Status: New

** Changed in: calamares-settings-ubuntu (Ubuntu Jammy)
Status: New => Confirmed

** Changed in: calamares-settings-ubuntu (Ubuntu Impish)
Status: New => Won't Fix

--
You received this bug notification because you are a member of Ubuntu
Studio Bugs, which is subscribed to ubuntustudio-meta in Ubuntu.
Matching subscriptions: UbuntuStudioPackages
https://bugs.launchpad.net/bugs/1970270

Title:
LibreOffice localization is not working out of the box

Status in calamares-settings-ubuntu package in Ubuntu:
Confirmed
Status in calamares-settings-ubuntu source package in Impish:
Won't Fix
Status in calamares-settings-ubuntu source package in Jammy:
Confirmed
Status in calamares-settings-ubuntu source package in Kinetic:
Confirmed

Bug description:
Using Lubuntu 22.04 within a virtual machine made using virt-manager,
KVM, and QEMU.

When Lubuntu 22.04 is installed in a language other than English, the
LibreOffice UI displays in English, despite the user's language
choice. The issue can be worked around by running "sudo apt update"
followed by "sudo apt install libreoffice-l10n-", where
is replaced with the 2-character language code (for example, de or
fr). This will cause LibreOffice to display in the correct language.

I have tested using both German and French language options at install
time - the problem exists in both scenarios.

Reproducibility: 100%

Steps to reproduce (edited to be more precise):

1: Open virt-manager.
2: Add a connection to "QEMU User session".
3: Create a new virtual machine under "QEMU User session". I set the OS as
"Ubuntu 21.04", since that's the newest version of Ubuntu that my version of
virt-manager supports. I gave the VM 20 GB of hard drive space, 4 GB of RAM,
and 2 CPU cores. I didn't make any other customizations.
4: Once the VM is running, select "Try or install Lubuntu" in the GRUB prompt.
5: Once Lubuntu is done booting, double-click "Install Lubuntu 22.04".
6: At the first screen of the installation, select a language other than
American English. I tried using German and French, and they both reproduced the
issue.
7: Use the default keyboard settings for your chosen language.
8: Use the "Erase disk" option when choosing where to install Lubuntu.
9: Set your name as "User", your username as "user", your computer name as
"user-germantest", and your password as "z". I also enabled automatic login
here.
10: Wait for the installation to finish, then reboot.
11: Open LibreOffice Writer.

Expected result: The UI should be displayed in the language selected
at install time.

Actual result: The UI displays in English, regardless of the language
selected at install time.

Additional notes:

I am using LibreOffice version 7.3.2 within the VM. I am using fully-
updated Ubuntu Studio 21.10 as the host OS.

Prior to running "sudo apt update", there are no LibreOffice
localization packages available in apt (as verified by doing "apt-
cache search l10n"). After the update, the packages appear.

I have not yet tested Ubuntu 22.04 for this problem, so I do not know
if this applies to Ubuntu as a whole, or to Lubuntu alone. I do intend
to test this in the near future.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/calamares-settings-ubuntu/+bug/1970270/+subscriptions

--
Mailing list: https://launchpad.net/~ubuntustudio-bugs
Post to : ubuntustudio-bugs@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntustudio-bugs
More help : https://help.launchpad.net/ListHelp

[Ubuntustudio-bugs] [Bug 1970270] Re: LibreOffice localization is not working out of the box

Marking impish as "Won't Fix" simply because of the amount of time left
of support.

** Changed in: calamares-settings-ubuntu (Ubuntu Jammy)
   Importance: Undecided => High

-- 
You received this bug notification because you are a member of Ubuntu
Studio Bugs, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1970270

Title:
  LibreOffice localization is not working out of the box

Status in calamares-settings-ubuntu package in Ubuntu:
  Confirmed
Status in calamares-settings-ubuntu source package in Impish:
  Won't Fix
Status in calamares-settings-ubuntu source package in Jammy:
  Confirmed
Status in calamares-settings-ubuntu source package in Kinetic:
  Confirmed

Bug description:
  Using Lubuntu 22.04 within a virtual machine made using virt-manager,
  KVM, and QEMU.

  When Lubuntu 22.04 is installed in a language other than English, the
  LibreOffice UI displays in English, despite the user's language
  choice. The issue can be worked around by running "sudo apt update"
  followed by "sudo apt install libreoffice-l10n-", where 
  is replaced with the 2-character language code (for example, de or
  fr). This will cause LibreOffice to display in the correct language.

  I have tested using both German and French language options at install
  time - the problem exists in both scenarios.

  Reproducibility: 100%

  Steps to reproduce (edited to be more precise):

  1: Open virt-manager.
  2: Add a connection to "QEMU User session".
  3: Create a new virtual machine under "QEMU User session". I set the OS as 
"Ubuntu 21.04", since that's the newest version of Ubuntu that my version of 
virt-manager supports. I gave the VM 20 GB of hard drive space, 4 GB of RAM, 
and 2 CPU cores. I didn't make any other customizations.
  4: Once the VM is running, select "Try or install Lubuntu" in the GRUB prompt.
  5: Once Lubuntu is done booting, double-click "Install Lubuntu 22.04".
  6: At the first screen of the installation, select a language other than 
American English. I tried using German and French, and they both reproduced the 
issue.
  7: Use the default keyboard settings for your chosen language.
  8: Use the "Erase disk" option when choosing where to install Lubuntu.
  9: Set your name as "User", your username as "user", your computer name as 
"user-germantest", and your password as "z". I also enabled automatic login 
here.
  10: Wait for the installation to finish, then reboot.
  11: Open LibreOffice Writer.

  Expected result: The UI should be displayed in the language selected
  at install time.

  Actual result: The UI displays in English, regardless of the language
  selected at install time.

  Additional notes:

  I am using LibreOffice version 7.3.2 within the VM. I am using fully-
  updated Ubuntu Studio 21.10 as the host OS.

  Prior to running "sudo apt update", there are no LibreOffice
  localization packages available in apt (as verified by doing "apt-
  cache search l10n"). After the update, the packages appear.

  I have not yet tested Ubuntu 22.04 for this problem, so I do not know
  if this applies to Ubuntu as a whole, or to Lubuntu alone. I do intend
  to test this in the near future.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/calamares-settings-ubuntu/+bug/1970270/+subscriptions


-- 
Mailing list: https://launchpad.net/~ubuntustudio-bugs
Post to : ubuntustudio-bugs@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntustudio-bugs
More help   : https://help.launchpad.net/ListHelp

[Ubuntustudio-bugs] [Bug 1969798] Re: Carla can't find plugins in plugin directories located in the user's home

2022-04-27 Thread Erich Eickmeyer 

This is a bit more serious, working with upstream on a resolution.

-- 
You received this bug notification because you are a member of Ubuntu
Studio Bugs, which is subscribed to carla in Ubuntu.
https://bugs.launchpad.net/bugs/1969798

Title:
  Carla can't find plugins in plugin directories located in the user's
  home

Status in carla package in Ubuntu:
  Triaged
Status in carla source package in Jammy:
  Triaged
Status in carla source package in Kinetic:
  Triaged

Bug description:
  [Impact]

  Users of Carla are unable to refresh audio plugins when more are
  installed, i.e. in the user's home directory. Furthermore, this can
  cause Carla to crash.

  [Test Plan]

   * Launch Carla
   * Click "Add Plugin"
   * Click "Refresh"
   * Click "Scan"
   
   Expected: Carla will scan for new plugins and find them.

   Actual: Carla does not scan for plugins, and may crash.

  [Where problems could occur]

   * The patch may just plain not work, in which case we may have to do
  a wholesale upload of Carla 2.4.3 instead as opposed to simply
  patching 2.4.2 with the cherry-picked commit as uploaded.

   * The other thing this might do is cause the application to cease to
  function, though this is highly unlikely.

  [Other Info]
   
  Original bug report as follows:
  --

  In the LV2 location in my home directory .lv2 I have the following
  plugin:

  ➜ ls ~/.lv2
  librnnoise_lv2.so

  ${HOME}/.lv2 is configured in Carla as a search path.

  In the Add Plugin dialog for Carla if I search for noise nothing shows
  up.

  This worked fine previously on 21.10.

  Release notes for Carla 2.4.3 [1] include this line: Fix plugin search
  (regression from 2.4.2)

  Ubuntu Studio 22.04 currently has the bugged version:

  ➜ carla --version
  Using Carla version 2.4.2

  [1] https://github.com/falkTX/Carla/releases/tag/v2.4.3

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: carla 2.4.2-0ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-24.24-lowlatency 5.15.30
  Uname: Linux 5.15.0-24-lowlatency x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: KDE
  Date: Thu Apr 21 15:41:13 2022
  InstallationDate: Installed on 2022-04-20 (1 days ago)
  InstallationMedia: Ubuntu-Studio 22.04 LTS "Jammy Jellyfish" - Beta amd64 
(20220329.1)
  SourcePackage: carla
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/carla/+bug/1969798/+subscriptions


-- 
Mailing list: https://launchpad.net/~ubuntustudio-bugs
Post to : ubuntustudio-bugs@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntustudio-bugs
More help   : https://help.launchpad.net/ListHelp

[Ubuntustudio-bugs] [Bug 1983136] Re: [SRU] v4l2loopback-dkms breaks secure boot installation in seed

2022-08-01 Thread Erich Eickmeyer 

Metapackage installed normally

** Tags removed: verification-needed verification-needed-jammy
** Tags added: verification-done verification-done-jammy

-- 
You received this bug notification because you are a member of Ubuntu
Studio Bugs, which is subscribed to ubuntustudio-meta in Ubuntu.
Matching subscriptions: UbuntuStudioPackages
https://bugs.launchpad.net/bugs/1983136

Title:
  [SRU] v4l2loopback-dkms breaks secure boot installation in seed

Status in ubuntustudio-meta package in Ubuntu:
  Fix Released
Status in ubuntustudio-meta source package in Jammy:
  Fix Released
Status in ubuntustudio-meta source package in Kinetic:
  Fix Released

Bug description:
  [Impact]

   * For users installing Ubuntu Studio 22.04 LTS on secure boot
  machines, this is currently not possible as v4l2loopback-dkms is
  currently seeded.

   * When v4l2loopback-dkms attempts to compile during installation on a
  secure boot machine without user interaction with calamares, it
  completely fails and the system installation fails.

   * In order to proceed, v4l2loopback-dkms must be removed from the
  seed and the ubuntustudio-video meta.

   * This was recently discovered while working with the Lubuntu team
  and undergoing extensive testing with the new Calamares. While it was
  not an issue with Calamares, it did point to the issue with
  v4l2loopback and explained some complaints received in the
  #ubuntustudio IRC chat.

  [Test Plan]

   * Download Ubuntu Studio 22.04 ISO image.

   * Attempt to install on machine with Secure Boot enabled.

   * Installation will fail when v4l2loopback-dkms modules attempt to
  compile and install to kernel.

  [Where problems could occur]

   * Problems can occur when existing users update and end up with
  v4l2loopback-dkms marked as autoremovable and run 'sudo apt
  autoremove', which will unexpectedly remove this package from their
  system. Unfortunately, there's no good way to mitigate this except to
  advise to reinstall this package.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntustudio-meta/+bug/1983136/+subscriptions


-- 
Mailing list: https://launchpad.net/~ubuntustudio-bugs
Post to : ubuntustudio-bugs@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntustudio-bugs
More help   : https://help.launchpad.net/ListHelp

[Ubuntustudio-bugs] [Bug 1983136] Re: [SRU] v4l2loopback-dkms breaks secure boot installation in seed

2022-07-30 Thread Erich Eickmeyer 

** Changed in: ubuntustudio-meta (Ubuntu Jammy)
 Assignee: (unassigned) => Erich Eickmeyer  (eeickmeyer)

** Changed in: ubuntustudio-meta (Ubuntu Kinetic)
 Assignee: (unassigned) => Erich Eickmeyer  (eeickmeyer)

** Changed in: ubuntustudio-meta (Ubuntu Jammy)
   Importance: Undecided => Critical

** Changed in: ubuntustudio-meta (Ubuntu Kinetic)
   Importance: Undecided => High

** Changed in: ubuntustudio-meta (Ubuntu Kinetic)
   Status: New => Fix Committed

** Changed in: ubuntustudio-meta (Ubuntu Jammy)
   Status: New => In Progress

-- 
You received this bug notification because you are a member of Ubuntu
Studio Bugs, which is subscribed to ubuntustudio-meta in Ubuntu.
Matching subscriptions: UbuntuStudioPackages
https://bugs.launchpad.net/bugs/1983136

Title:
  [SRU] v4l2loopback-dkms breaks secure boot installation in seed

Status in ubuntustudio-meta package in Ubuntu:
  Fix Committed
Status in ubuntustudio-meta source package in Jammy:
  In Progress
Status in ubuntustudio-meta source package in Kinetic:
  Fix Committed

Bug description:
  [Impact]

   * For users installing Ubuntu Studio 22.04 LTS on secure boot
  machines, this is currently not possible as v4l2loopback-dkms is
  currently seeded.

   * When v4l2loopback-dkms attempts to compile during installation on a
  secure boot machine without user interaction with calamares, it
  completely fails and the system installation fails.

   * In order to proceed, v4l2loopback-dkms must be removed from the
  seed and the ubuntustudio-video meta.

   * This was recently discovered while working with the Lubuntu team
  and undergoing extensive testing with the new Calamares. While it was
  not an issue with Calamares, it did point to the issue with
  v4l2loopback and explained some complaints received in the
  #ubuntustudio IRC chat.

  [Test Plan]

   * Download Ubuntu Studio 22.04 ISO image.

   * Attempt to install on machine with Secure Boot enabled.

   * Installation will fail when v4l2loopback-dkms modules attempt to
  compile and install to kernel.

  [Where problems could occur]

   * Problems can occur when existing users update and end up with
  v4l2loopback-dkms marked as autoremovable and run 'sudo apt
  autoremove', which will unexpectedly remove this package from their
  system. Unfortunately, there's no good way to mitigate this except to
  advise to reinstall this package.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntustudio-meta/+bug/1983136/+subscriptions


-- 
Mailing list: https://launchpad.net/~ubuntustudio-bugs
Post to : ubuntustudio-bugs@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntustudio-bugs
More help   : https://help.launchpad.net/ListHelp

[Ubuntustudio-bugs] [Bug 1987934] [NEW] kdenlive 22.08: missing Recommends: mediainfo

2022-08-26 Thread Erich Eickmeyer 

Public bug reported:

kdenlive introduced a new soft dependency on mediainfo. This should be
included as a Recommends in the package.

** Affects: kdenlive (Ubuntu)
 Importance: Medium
 Assignee: Erich Eickmeyer  (eeickmeyer)
 Status: Triaged

** Affects: kdenlive (Ubuntu Kinetic)
 Importance: Medium
 Assignee: Erich Eickmeyer  (eeickmeyer)
 Status: Triaged


** Tags: kinetic ubuntustudio

** Also affects: kdenlive (Ubuntu Kinetic)
   Importance: Undecided
 Assignee: Erich Eickmeyer  (eeickmeyer)
   Status: Triaged

** Changed in: kdenlive (Ubuntu Kinetic)
   Importance: Undecided => Medium

-- 
You received this bug notification because you are a member of Ubuntu
Studio Bugs, which is subscribed to kdenlive in Ubuntu.
Matching subscriptions: Ubuntu Studio Bugs
https://bugs.launchpad.net/bugs/1987934

Title:
  kdenlive 22.08: missing Recommends: mediainfo

Status in kdenlive package in Ubuntu:
  Triaged
Status in kdenlive source package in Kinetic:
  Triaged

Bug description:
  kdenlive introduced a new soft dependency on mediainfo. This should be
  included as a Recommends in the package.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/kdenlive/+bug/1987934/+subscriptions


-- 
Mailing list: https://launchpad.net/~ubuntustudio-bugs
Post to : ubuntustudio-bugs@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntustudio-bugs
More help   : https://help.launchpad.net/ListHelp

[Ubuntustudio-bugs] [Bug 1987934] Re: kdenlive 22.08: missing Recommends: mediainfo

2022-08-27 Thread Erich Eickmeyer 

** Changed in: kdenlive (Ubuntu Kinetic)
   Status: In Progress => Fix Committed

-- 
You received this bug notification because you are a member of Ubuntu
Studio Bugs, which is subscribed to kdenlive in Ubuntu.
Matching subscriptions: Ubuntu Studio Bugs
https://bugs.launchpad.net/bugs/1987934

Title:
  kdenlive 22.08: missing Recommends: mediainfo

Status in kdenlive package in Ubuntu:
  Fix Committed
Status in kdenlive source package in Kinetic:
  Fix Committed

Bug description:
  kdenlive introduced a new soft dependency on mediainfo. This should be
  included as a Recommends in the package.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/kdenlive/+bug/1987934/+subscriptions


-- 
Mailing list: https://launchpad.net/~ubuntustudio-bugs
Post to : ubuntustudio-bugs@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntustudio-bugs
More help   : https://help.launchpad.net/ListHelp

[Ubuntustudio-bugs] [Bug 1987934] Re: kdenlive 22.08: missing Recommends: mediainfo

2022-08-27 Thread Erich Eickmeyer 

** Changed in: kdenlive (Ubuntu Kinetic)
   Status: Triaged => In Progress

-- 
You received this bug notification because you are a member of Ubuntu
Studio Bugs, which is subscribed to kdenlive in Ubuntu.
Matching subscriptions: Ubuntu Studio Bugs
https://bugs.launchpad.net/bugs/1987934

Title:
  kdenlive 22.08: missing Recommends: mediainfo

Status in kdenlive package in Ubuntu:
  In Progress
Status in kdenlive source package in Kinetic:
  In Progress

Bug description:
  kdenlive introduced a new soft dependency on mediainfo. This should be
  included as a Recommends in the package.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/kdenlive/+bug/1987934/+subscriptions


-- 
Mailing list: https://launchpad.net/~ubuntustudio-bugs
Post to : ubuntustudio-bugs@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntustudio-bugs
More help   : https://help.launchpad.net/ListHelp

[Ubuntustudio-bugs] [Bug 1762846] Re: OpenCL disabled on nvidia

> Should darktable depend on nvidia-opencl-dev

No, because that would potentially install nvidia dependencies for those
that don't need it. Therefore, those that need opencl support on nvidia
should do as you did and install nvidia-opencl-dev.

Closing this as this was a support issue, not a packaging issue, and
should never have been open in the bug tracker as bug trackers are not
places for support questions.

** Changed in: darktable (Ubuntu)
   Status: Confirmed => Invalid

-- 
You received this bug notification because you are a member of Ubuntu
Studio Bugs, which is subscribed to darktable in Ubuntu.
Matching subscriptions: Ubuntu Studio Bugs
https://bugs.launchpad.net/bugs/1762846

Title:
  OpenCL disabled on nvidia

Status in darktable package in Ubuntu:
  Invalid

Bug description:
  OpenCL is not enabled by default.

  Steps to reproduce :
   * install the nvidia driver
   * install darktable
   * run darktable on command line : $darktable -d opencl

  =>
  [opencl_init] could not find opencl runtime library 'libOpenCL'
  0.159268 [opencl_init] could not find opencl runtime library 'libOpenCL.so'
  0.159327 [opencl_init] could not find opencl runtime library 'libOpenCL.so.1'
  0.159333 [opencl_init] no working opencl library found. Continue with opencl 
disabled
  0.159336 [opencl_init] FINALLY: opencl is NOT AVAILABLE on this system.

  Workaround : install package nvidia-opencl-dev

  Should darktable depend on nvidia-opencl-dev ?

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: darktable 2.4.2-1
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu4
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Apr 10 23:49:56 2018
  InstallationDate: Installed on 2018-04-09 (1 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180407)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  SourcePackage: darktable
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/darktable/+bug/1762846/+subscriptions


-- 
Mailing list: https://launchpad.net/~ubuntustudio-bugs
Post to : ubuntustudio-bugs@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntustudio-bugs
More help   : https://help.launchpad.net/ListHelp

[Ubuntustudio-bugs] [Bug 1115474] Re: darktable does not render text in overlay/watermark svg-files

Thank you for reporting this bug to Ubuntu.

Ubuntu 13.10 (saucy) reached end-of-life on July 17, 2014.

See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases

We appreciate that this bug may be old and you might not be interested
in discussing it any more. But if you are then please upgrade to the
latest Ubuntu version and re-test. If you then find the bug is still
present in the newer Ubuntu version, please add a comment here telling
us which new version it is in.


** Changed in: darktable (Ubuntu)
   Status: Confirmed => Incomplete

-- 
You received this bug notification because you are a member of Ubuntu
Studio Bugs, which is subscribed to darktable in Ubuntu.
Matching subscriptions: Ubuntu Studio Bugs
https://bugs.launchpad.net/bugs/1115474

Title:
  darktable does not render text in overlay/watermark svg-files

Status in darktable package in Ubuntu:
  Incomplete

Bug description:
  darktable does not render text in svg-files created with inkscape
  correctly.

  To reproduce: make a svg-file containig text with inkscape. Add it to
  darktable's watermark source and try to apply it to an image. The text
  will not render. Instead a black box is shown where the text should
  be.

  For example: see attached screenshot.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/darktable/+bug/1115474/+subscriptions


-- 
Mailing list: https://launchpad.net/~ubuntustudio-bugs
Post to : ubuntustudio-bugs@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntustudio-bugs
More help   : https://help.launchpad.net/ListHelp

[Ubuntustudio-bugs] [Bug 1760074] Re: Will the bugfix releases for 2.4 come up in 18.04 packages or do I have to add the ppa?

** Changed in: darktable (Ubuntu)
   Status: Confirmed => Invalid

** Converted to question:
   https://answers.launchpad.net/ubuntu/+source/darktable/+question/702869

-- 
You received this bug notification because you are a member of Ubuntu
Studio Bugs, which is subscribed to darktable in Ubuntu.
Matching subscriptions: Ubuntu Studio Bugs
https://bugs.launchpad.net/bugs/1760074

Title:
  Will the bugfix releases for 2.4 come up in 18.04 packages or do I
  have to add the ppa?

Status in darktable package in Ubuntu:
  Invalid

Bug description:
  Well the question is in the subject, again:

  Will the bugfix releases for 2.4 come up in 18.04 packages or do I
  have to add the ppa?

  I am not sure about how this works - is ist enough to wait for regular
  bionic updates or is the version in 18.04 doomed to have bugs forever
  and I have to add the ppa to get new releases?

  It would be very appreciated to read some info about this, thanks!

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/darktable/+bug/1760074/+subscriptions


-- 
Mailing list: https://launchpad.net/~ubuntustudio-bugs
Post to : ubuntustudio-bugs@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntustudio-bugs
More help   : https://help.launchpad.net/ListHelp

[Ubuntustudio-bugs] [Bug 1255656] Re: Localization darktable

Thank you for reporting this bug to Ubuntu.

Ubuntu 13.10 (saucy) reached end-of-life on July 17, 2014.

See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases

We appreciate that this bug may be old and you might not be interested
in discussing it any more. But if you are then please upgrade to the
latest Ubuntu version and re-test. If you then find the bug is still
present in the newer Ubuntu version, please add a comment here telling
us which new version it is in.

** Changed in: darktable (Ubuntu)
   Status: Confirmed => Incomplete

-- 
You received this bug notification because you are a member of Ubuntu
Studio Bugs, which is subscribed to darktable in Ubuntu.
Matching subscriptions: Ubuntu Studio Bugs
https://bugs.launchpad.net/bugs/1255656

Title:
  Localization darktable

Status in darktable package in Ubuntu:
  Incomplete

Bug description:
  Is there anyway we can translate darktable?

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: darktable 1.2.3-1ubuntu1
  Uname: Linux 3.12.0-031200-generic x86_64
  NonfreeKernelModules: fglrx
  ApportVersion: 2.12.5-0ubuntu2.1
  Architecture: amd64
  Date: Thu Nov 28 03:52:52 2013
  InstallationDate: Installed on 2013-11-03 (24 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  MarkForUpload: True
  SourcePackage: darktable
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/darktable/+bug/1255656/+subscriptions


-- 
Mailing list: https://launchpad.net/~ubuntustudio-bugs
Post to : ubuntustudio-bugs@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntustudio-bugs
More help   : https://help.launchpad.net/ListHelp

[Ubuntustudio-bugs] [Bug 1988628] Re: audacity ffmpeg error encoding frame failed

2022-09-03 Thread Erich Eickmeyer 

Thank you for taking the time to report this bug and helping to make
Ubuntu better. Please execute the following command only once, as it
will automatically gather debugging information, in a terminal:

apport-collect 1988628

When reporting bugs in the future please use apport by using 'ubuntu-
bug' and the name of the package affected. You can learn more about this
functionality at https://wiki.ubuntu.com/ReportingBugs.

** Changed in: audacity (Ubuntu)
   Status: New => Incomplete

-- 
You received this bug notification because you are a member of Ubuntu
Studio Bugs, which is subscribed to audacity in Ubuntu.
Matching subscriptions: Ubuntu Studio Bugs
https://bugs.launchpad.net/bugs/1988628

Title:
  audacity ffmpeg error encoding frame failed

Status in audacity package in Ubuntu:
  Incomplete

Bug description:
  When exporting audio, an error window saying "ffmpeg error encoding
  frame failed" pops up and the export fails.  This does not happen with
  the flatpak version.

  Relevant links:
  
https://superuser.com/questions/1649367/ffmpeg-errors-encoding-frame-failed-and-cant-encode-audio-frame-when-attemp
  https://bbs.archlinux.org/viewtopic.php?id=265947

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/audacity/+bug/1988628/+subscriptions


-- 
Mailing list: https://launchpad.net/~ubuntustudio-bugs
Post to : ubuntustudio-bugs@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntustudio-bugs
More help   : https://help.launchpad.net/ListHelp

[Ubuntustudio-bugs] [Bug 1988628] Re: audacity ffmpeg error encoding frame failed

2022-09-03 Thread Erich Eickmeyer 

Well, whatever you did it seemed to work.

** Changed in: audacity (Ubuntu)
   Status: Incomplete => New

-- 
You received this bug notification because you are a member of Ubuntu
Studio Bugs, which is subscribed to audacity in Ubuntu.
Matching subscriptions: Ubuntu Studio Bugs
https://bugs.launchpad.net/bugs/1988628

Title:
  audacity ffmpeg error encoding frame failed

Status in audacity package in Ubuntu:
  New

Bug description:
  When exporting audio, an error window saying "ffmpeg error encoding
  frame failed" pops up and the export fails.  This does not happen with
  the flatpak version.

  Relevant links:
  
https://superuser.com/questions/1649367/ffmpeg-errors-encoding-frame-failed-and-cant-encode-audio-frame-when-attemp
  https://bbs.archlinux.org/viewtopic.php?id=265947
  --- 
  ProblemType: Bug
  AlsaCards:
   0 [PCH]: HDA-Intel - HDA Intel PCH
 HDA Intel PCH at 0xed518000 irq 180
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2022-04-23 (133 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: audacity 2.4.2~dfsg0-5
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.15.0-47.51-generic 5.15.46
  Tags:  wayland-session jammy
  Uname: Linux 5.15.0-47-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout dip i2c lpadmin lxd plugdev sambashare 
ssh-users sudo
  _MarkForUpload: True
  modified.conffile..etc.apport.crashdb.conf: [modified]
  mtime.conffile..etc.apport.crashdb.conf: 2022-05-09T11:14:43.789743

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/audacity/+bug/1988628/+subscriptions


-- 
Mailing list: https://launchpad.net/~ubuntustudio-bugs
Post to : ubuntustudio-bugs@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntustudio-bugs
More help   : https://help.launchpad.net/ListHelp

[Ubuntustudio-bugs] [Bug 1933114] Re: [needs packaging] dvdstyler

2022-09-26 Thread Erich Eickmeyer 

Unfortunately, that RFP was closed as a duplicate of the previous 10+
year old RFP/ITP, so it needs to be tracked there.

** Bug watch added: Debian Bug tracker #635516
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=635516

** Changed in: debian
   Status: Fix Released => Unknown

** Changed in: debian
 Remote watch: Debian Bug tracker #1019978 => Debian Bug tracker #635516

-- 
You received this bug notification because you are a member of Ubuntu
Studio Bugs, which is subscribed to dvdstyler in Ubuntu.
Matching subscriptions: Ubuntu Studio Bugs
https://bugs.launchpad.net/bugs/1933114

Title:
  [needs packaging] dvdstyler

Status in dvdstyler package in Ubuntu:
  Triaged
Status in Debian:
  Unknown

Bug description:
  Could someone create a new package for dvdstyler version 3.2  ?

  DVDStyler is a cross-platform free DVD authoring application for the
  creation of professional-looking DVDs.

  URL: https://dvdstyler.org
  License: GNU GENERAL PUBLIC LICENSE Version 2
  Notes: a PPA exists for dvdstyler  3.1-0 (see 
https://launchpad.net/~ubuntuhandbook1/+archive/ubuntu/dvdstyler),  and I can't 
find it in 
https://packages.ubuntu.com/search?keywords=dvdstyler=names=all=all

  https://github.com/linuxmint/linuxmint/issues/357

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dvdstyler/+bug/1933114/+subscriptions


-- 
Mailing list: https://launchpad.net/~ubuntustudio-bugs
Post to : ubuntustudio-bugs@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntustudio-bugs
More help   : https://help.launchpad.net/ListHelp

[Ubuntustudio-bugs] [Bug 1973052] Re: Length and position of selection is not shown correctly

2022-09-28 Thread Erich Eickmeyer 

** Changed in: audacity (Ubuntu)
   Status: Incomplete => New

-- 
You received this bug notification because you are a member of Ubuntu
Studio Bugs, which is subscribed to audacity in Ubuntu.
Matching subscriptions: Ubuntu Studio Bugs
https://bugs.launchpad.net/bugs/1973052

Title:
  Length and position of selection is not shown correctly

Status in audacity package in Ubuntu:
  New
Status in audacity package in Debian:
  New

Bug description:
  Steps to reproduce:

  1. Open .wav/.ogg file in audacity 2.4.2
  2. Select length and end position as selection option below
  3. Make a short selection (e.g. 4 samples long)
  4. Change length and position unit to "samples"

  Expected Result:
  "000 000 004 Samples" as length is shown

  Result:
  "004 000 000 Samples" as length is shown

  
  Good time to update to audacity 3.1.x?

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: audacity 2.4.2~dfsg0-5
  ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30
  Uname: Linux 5.15.0-27-generic x86_64
  AlsaCards:
   0 [PCH]: HDA-Intel - HDA Intel PCH
 HDA Intel PCH at 0xef24 irq 138
1 [U0x46d0x825]: USB-Audio - USB Device 0x46d:0x825
 USB Device 0x46d:0x825 at usb-:00:14.0-4.1.4, high 
speed
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: XFCE
  Date: Wed May 11 19:24:04 2022
  InstallationDate: Installed on 2016-04-30 (2202 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  SourcePackage: audacity
  UpgradeStatus: Upgraded to jammy on 2022-04-28 (13 days ago)
  modified.conffile..etc.default.apport:
   # set this to 0 to disable apport, or to 1 to enable it
   # you can temporarily override this with
   # sudo service apport start force_start=1
   enabled=0
  mtime.conffile..etc.default.apport: 2017-06-27T22:18:31.198313

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/audacity/+bug/1973052/+subscriptions


-- 
Mailing list: https://launchpad.net/~ubuntustudio-bugs
Post to : ubuntustudio-bugs@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntustudio-bugs
More help   : https://help.launchpad.net/ListHelp

[Ubuntustudio-bugs] [Bug 1993464] Re: Ctrl+Alt+T no longer pulls up a Konsole window in Ubuntu Studio Kinetic

2022-10-19 Thread Erich Eickmeyer 

As stated by Rik, this is not a shortcut that gets set by default in
Plasma. Furthermore, due to https://bugs.kde.org/show_bug.cgi?id=456958,
it is not one that is easily set by default. Unfortunately, this puts
this into the "Can't Fix/Won't Fix" category.

** Bug watch added: KDE Bug Tracking System #456958
https://bugs.kde.org/show_bug.cgi?id=456958

** Package changed: ubuntustudio-meta (Ubuntu) => ubuntustudio-default-
settings (Ubuntu)

** Changed in: ubuntustudio-default-settings (Ubuntu)
Status: New => Won't Fix

Title:
Ctrl+Alt+T no longer pulls up a Konsole window in Ubuntu Studio
Kinetic

Status in ubuntustudio-default-settings package in Ubuntu:
Won't Fix

Bug description:
Reporting this against the meta since I have absolutely no clue what
package is at fault here. I discovered this bug on a bare metal
installation, so I know that this isn't my virtualization software's
fault since there isn't any virtualization software involved.

Steps to reproduce:

1. Install the Ubuntu Studio Kinetic using the Final ISO.
2. Reboot and log into the newly installed system.
3. Press Ctrl+Alt+T.

Expected result: A Konsole window should appear.

Actual result: Nothing happens.

Notes: The problem can be worked around by opening the Application
Menu, searching for "shortcuts", and launching the Shortcuts System
Settings module. Then click "Add Application...", and add Konsole to
the list. The Apply button will not become active after doing this -
simply close the System Settings window. The keyboard shortcut will
immediately start working and will continue to work after a reboot.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntustudio-default-settings/+bug/1993464/+subscriptions

[Ubuntustudio-bugs] [Bug 1989263] Re: [FFe] plasma-distro-release-notifier for Ubuntu Studio

2022-09-12 Thread Erich Eickmeyer 

** Changed in: ubuntustudio-meta (Ubuntu Kinetic)
Milestone: None => ubuntu-22.10-beta

** Description changed:

- Currently awaiting approval is plasma-distro-release-notifier, an applet
- which, in conjunction with update-notifier, notifies the user of a new
- version of Ubuntu using the same logic that update-notifier currently
- uses from the configuration in /etc/update-manager/release-upgrades.
- This has been sorely missing from previous releases of Ubuntu Studio and
- Kubuntu and should be included in all releases of Ubuntu Studio going
- forward and should be included in currently supported releases.
+ plasma-distro-release-notifier is an applet which, in conjunction with
+ update-notifier, notifies the user of a new version of Ubuntu using the
+ same logic that update-notifier currently uses from the configuration in
+ /etc/update-manager/release-upgrades. This has been sorely missing from
+ previous releases of Ubuntu Studio and Kubuntu and should be included in
+ all releases of Ubuntu Studio and Kubuntu going forward and should be
+ included in currently supported releases.
  
  Currently, users are not prompted when a new version of Ubuntu is
  released, and as such, users of the Plasma desktop (Ubuntu Studio and
  Kubuntu) get stuck on an EOL release very quickly. I have seen several
  posts on #kubuntu and Reddit requesting help because the user simply did
  not know that they needed to update their machine to a newer release.
  Including this package would prevent that.
+ 
+ Tests on 20.04 using the same package have been successful, with not
+ only a notification, but also a tray icon indicating that the upgrade is
+ available.
+ 
+ The intention will be, once through this FFe process, to backport the
+ package via SRU to 22.04. A stretch goal would be to backport the same
+ package to Kubuntu 20.04 through the same process as it is still
+ supported until April 2023 and many users there are not getting the
+ prompt to upgrade.
+ 
+ I am still awaiting buy-in from the Kubuntu team to see if they would be
+ interested in this, but this seems like, from a UX standpoint, something
+ they definitely should have.
+ 
+ As of this writing, plasma-distro-release-notifier has been accepted
+ into kinetic.

** Summary changed:

- [FFe] plasma-distro-release-notifier for Ubuntu Studio
+ [FFe] plasma-distro-release-notifier for Ubuntu Studio and/or Kubuntu

-- 
You received this bug notification because you are a member of Ubuntu
Studio Bugs, which is subscribed to ubuntustudio-meta in Ubuntu.
Matching subscriptions: UbuntuStudioPackages
https://bugs.launchpad.net/bugs/1989263

Title:
  [FFe] plasma-distro-release-notifier for Ubuntu Studio and/or Kubuntu

Status in ubuntustudio-meta package in Ubuntu:
  New
Status in ubuntustudio-meta source package in Kinetic:
  New

Bug description:
  plasma-distro-release-notifier is an applet which, in conjunction with
  update-notifier, notifies the user of a new version of Ubuntu using
  the same logic that update-notifier currently uses from the
  configuration in /etc/update-manager/release-upgrades. This has been
  sorely missing from previous releases of Ubuntu Studio and Kubuntu and
  should be included in all releases of Ubuntu Studio and Kubuntu going
  forward and should be included in currently supported releases.

  Currently, users are not prompted when a new version of Ubuntu is
  released, and as such, users of the Plasma desktop (Ubuntu Studio and
  Kubuntu) get stuck on an EOL release very quickly. I have seen several
  posts on #kubuntu and Reddit requesting help because the user simply
  did not know that they needed to update their machine to a newer
  release. Including this package would prevent that.

  Tests on 20.04 using the same package have been successful, with not
  only a notification, but also a tray icon indicating that the upgrade
  is available.

  The intention will be, once through this FFe process, to backport the
  package via SRU to 22.04. A stretch goal would be to backport the same
  package to Kubuntu 20.04 through the same process as it is still
  supported until April 2023 and many users there are not getting the
  prompt to upgrade.

  I am still awaiting buy-in from the Kubuntu team to see if they would
  be interested in this, but this seems like, from a UX standpoint,
  something they definitely should have.

  As of this writing, plasma-distro-release-notifier has been accepted
  into kinetic.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntustudio-meta/+bug/1989263/+subscriptions


-- 
Mailing list: https://launchpad.net/~ubuntustudio-bugs
Post to : ubuntustudio-bugs@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntustudio-bugs
More help   : https://help.launchpad.net/ListHelp

[Ubuntustudio-bugs] [Bug 1989263] Re: [FFe] plasma-distro-release-notifier for Ubuntu Studio and/or Kubuntu

2022-09-12 Thread Erich Eickmeyer 

** Also affects: kubuntu-meta (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: kubuntu-meta (Ubuntu Kinetic)
 Assignee: (unassigned) => Rik Mills (rikmills)

** Changed in: kubuntu-meta (Ubuntu Kinetic)
Milestone: None => ubuntu-22.10-beta

-- 
You received this bug notification because you are a member of Ubuntu
Studio Bugs, which is subscribed to ubuntustudio-meta in Ubuntu.
Matching subscriptions: UbuntuStudioPackages
https://bugs.launchpad.net/bugs/1989263

Title:
  [FFe] plasma-distro-release-notifier for Ubuntu Studio and/or Kubuntu

Status in kubuntu-meta package in Ubuntu:
  New
Status in ubuntustudio-meta package in Ubuntu:
  New
Status in kubuntu-meta source package in Kinetic:
  New
Status in ubuntustudio-meta source package in Kinetic:
  New

Bug description:
  plasma-distro-release-notifier is an applet which, in conjunction with
  update-notifier, notifies the user of a new version of Ubuntu using
  the same logic that update-notifier currently uses from the
  configuration in /etc/update-manager/release-upgrades. This has been
  sorely missing from previous releases of Ubuntu Studio and Kubuntu and
  should be included in all releases of Ubuntu Studio and Kubuntu going
  forward and should be included in currently supported releases.

  Currently, users are not prompted when a new version of Ubuntu is
  released, and as such, users of the Plasma desktop (Ubuntu Studio and
  Kubuntu) get stuck on an EOL release very quickly. I have seen several
  posts on #kubuntu and Reddit requesting help because the user simply
  did not know that they needed to update their machine to a newer
  release. Including this package would prevent that.

  Tests on 20.04 using the same package have been successful, with not
  only a notification, but also a tray icon indicating that the upgrade
  is available.

  The intention will be, once through this FFe process, to backport the
  package via SRU to 22.04. A stretch goal would be to backport the same
  package to Kubuntu 20.04 through the same process as it is still
  supported until April 2023 and many users there are not getting the
  prompt to upgrade.

  I am still awaiting buy-in from the Kubuntu team to see if they would
  be interested in this, but this seems like, from a UX standpoint,
  something they definitely should have.

  As of this writing, plasma-distro-release-notifier has been accepted
  into kinetic.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/kubuntu-meta/+bug/1989263/+subscriptions


-- 
Mailing list: https://launchpad.net/~ubuntustudio-bugs
Post to : ubuntustudio-bugs@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntustudio-bugs
More help   : https://help.launchpad.net/ListHelp

[Ubuntustudio-bugs] [Bug 1989263] Re: [FFe] plasma-distro-release-notifier for Ubuntu Studio and Kubuntu

The easiest way to test it is to install the package in a 20.04 Kubuntu
VM and reboot. I have done this, and it works perfectly. The user is
notified right away of the existence of 22.04.1 and is prompted to
upgrade.

-- 
You received this bug notification because you are a member of Ubuntu
Studio Bugs, which is subscribed to ubuntustudio-meta in Ubuntu.
Matching subscriptions: UbuntuStudioPackages
https://bugs.launchpad.net/bugs/1989263

Title:
  [FFe] plasma-distro-release-notifier for Ubuntu Studio and Kubuntu

Status in kubuntu-meta package in Ubuntu:
  Triaged
Status in ubuntustudio-meta package in Ubuntu:
  Triaged
Status in kubuntu-meta source package in Kinetic:
  Triaged
Status in ubuntustudio-meta source package in Kinetic:
  Triaged

Bug description:
  plasma-distro-release-notifier is an applet which, in conjunction with
  update-notifier, notifies the user of a new version of Ubuntu using
  the same logic that update-notifier currently uses from the
  configuration in /etc/update-manager/release-upgrades. This has been
  sorely missing from previous releases of Ubuntu Studio and Kubuntu and
  should be included in all releases of Ubuntu Studio and Kubuntu going
  forward and should be included in currently supported releases.

  Currently, users are not prompted when a new version of Ubuntu is
  released, and as such, users of the Plasma desktop (Ubuntu Studio and
  Kubuntu) get stuck on an EOL release very quickly. I have seen several
  posts on #kubuntu and Reddit requesting help because the user simply
  did not know that they needed to update their machine to a newer
  release. Including this package would prevent that.

  Tests on 20.04 using the same package have been successful, with not
  only a notification, but also a tray icon indicating that the upgrade
  is available.

  The intention will be, once through this FFe process, to backport the
  package via SRU to 22.04. A stretch goal would be to backport the same
  package to Kubuntu 20.04 through the same process as it is still
  supported until April 2023 and many users there are not getting the
  prompt to upgrade.

  As of this writing, plasma-distro-release-notifier has been accepted
  into kinetic.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/kubuntu-meta/+bug/1989263/+subscriptions


-- 
Mailing list: https://launchpad.net/~ubuntustudio-bugs
Post to : ubuntustudio-bugs@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntustudio-bugs
More help   : https://help.launchpad.net/ListHelp

[Ubuntustudio-bugs] [Bug 1989263] Re: [FFe] plasma-distro-release-notifier for Ubuntu Studio and Kubuntu

** Changed in: ubuntustudio-meta (Ubuntu Kinetic)
   Status: Triaged => Fix Committed

-- 
You received this bug notification because you are a member of Ubuntu
Studio Bugs, which is subscribed to ubuntustudio-meta in Ubuntu.
Matching subscriptions: UbuntuStudioPackages
https://bugs.launchpad.net/bugs/1989263

Title:
  [FFe] plasma-distro-release-notifier for Ubuntu Studio and Kubuntu

Status in kubuntu-meta package in Ubuntu:
  Triaged
Status in ubuntustudio-meta package in Ubuntu:
  Fix Committed
Status in kubuntu-meta source package in Kinetic:
  Triaged
Status in ubuntustudio-meta source package in Kinetic:
  Fix Committed

Bug description:
  plasma-distro-release-notifier is an applet which, in conjunction with
  update-notifier, notifies the user of a new version of Ubuntu using
  the same logic that update-notifier currently uses from the
  configuration in /etc/update-manager/release-upgrades. This has been
  sorely missing from previous releases of Ubuntu Studio and Kubuntu and
  should be included in all releases of Ubuntu Studio and Kubuntu going
  forward and should be included in currently supported releases.

  Currently, users are not prompted when a new version of Ubuntu is
  released, and as such, users of the Plasma desktop (Ubuntu Studio and
  Kubuntu) get stuck on an EOL release very quickly. I have seen several
  posts on #kubuntu and Reddit requesting help because the user simply
  did not know that they needed to update their machine to a newer
  release. Including this package would prevent that.

  Tests on 20.04 using the same package have been successful, with not
  only a notification, but also a tray icon indicating that the upgrade
  is available.

  The intention will be, once through this FFe process, to backport the
  package via SRU to 22.04. A stretch goal would be to backport the same
  package to Kubuntu 20.04 through the same process as it is still
  supported until April 2023 and many users there are not getting the
  prompt to upgrade.

  As of this writing, plasma-distro-release-notifier has been accepted
  into kinetic.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/kubuntu-meta/+bug/1989263/+subscriptions


-- 
Mailing list: https://launchpad.net/~ubuntustudio-bugs
Post to : ubuntustudio-bugs@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntustudio-bugs
More help   : https://help.launchpad.net/ListHelp

[Ubuntustudio-bugs] [Bug 1989263] Re: [FFe] plasma-distro-release-notifier for Ubuntu Studio and/or Kubuntu

** Description changed:

  plasma-distro-release-notifier is an applet which, in conjunction with
  update-notifier, notifies the user of a new version of Ubuntu using the
  same logic that update-notifier currently uses from the configuration in
  /etc/update-manager/release-upgrades. This has been sorely missing from
  previous releases of Ubuntu Studio and Kubuntu and should be included in
  all releases of Ubuntu Studio and Kubuntu going forward and should be
  included in currently supported releases.
  
  Currently, users are not prompted when a new version of Ubuntu is
  released, and as such, users of the Plasma desktop (Ubuntu Studio and
  Kubuntu) get stuck on an EOL release very quickly. I have seen several
  posts on #kubuntu and Reddit requesting help because the user simply did
  not know that they needed to update their machine to a newer release.
  Including this package would prevent that.
  
  Tests on 20.04 using the same package have been successful, with not
  only a notification, but also a tray icon indicating that the upgrade is
  available.
  
  The intention will be, once through this FFe process, to backport the
  package via SRU to 22.04. A stretch goal would be to backport the same
  package to Kubuntu 20.04 through the same process as it is still
  supported until April 2023 and many users there are not getting the
  prompt to upgrade.
  
- I am still awaiting buy-in from the Kubuntu team to see if they would be
- interested in this, but this seems like, from a UX standpoint, something
- they definitely should have.
- 
  As of this writing, plasma-distro-release-notifier has been accepted
  into kinetic.

** Summary changed:

- [FFe] plasma-distro-release-notifier for Ubuntu Studio and/or Kubuntu
+ [FFe] plasma-distro-release-notifier for Ubuntu Studio and Kubuntu

-- 
You received this bug notification because you are a member of Ubuntu
Studio Bugs, which is subscribed to ubuntustudio-meta in Ubuntu.
Matching subscriptions: UbuntuStudioPackages
https://bugs.launchpad.net/bugs/1989263

Title:
  [FFe] plasma-distro-release-notifier for Ubuntu Studio and Kubuntu

Status in kubuntu-meta package in Ubuntu:
  Triaged
Status in ubuntustudio-meta package in Ubuntu:
  Triaged
Status in kubuntu-meta source package in Kinetic:
  Triaged
Status in ubuntustudio-meta source package in Kinetic:
  Triaged

Bug description:
  plasma-distro-release-notifier is an applet which, in conjunction with
  update-notifier, notifies the user of a new version of Ubuntu using
  the same logic that update-notifier currently uses from the
  configuration in /etc/update-manager/release-upgrades. This has been
  sorely missing from previous releases of Ubuntu Studio and Kubuntu and
  should be included in all releases of Ubuntu Studio and Kubuntu going
  forward and should be included in currently supported releases.

  Currently, users are not prompted when a new version of Ubuntu is
  released, and as such, users of the Plasma desktop (Ubuntu Studio and
  Kubuntu) get stuck on an EOL release very quickly. I have seen several
  posts on #kubuntu and Reddit requesting help because the user simply
  did not know that they needed to update their machine to a newer
  release. Including this package would prevent that.

  Tests on 20.04 using the same package have been successful, with not
  only a notification, but also a tray icon indicating that the upgrade
  is available.

  The intention will be, once through this FFe process, to backport the
  package via SRU to 22.04. A stretch goal would be to backport the same
  package to Kubuntu 20.04 through the same process as it is still
  supported until April 2023 and many users there are not getting the
  prompt to upgrade.

  As of this writing, plasma-distro-release-notifier has been accepted
  into kinetic.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/kubuntu-meta/+bug/1989263/+subscriptions


-- 
Mailing list: https://launchpad.net/~ubuntustudio-bugs
Post to : ubuntustudio-bugs@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntustudio-bugs
More help   : https://help.launchpad.net/ListHelp

[Ubuntustudio-bugs] [Bug 1989611] Re: [SRU] plasma-distro-release-notifier for Jammy, Focal

** Changed in: kubuntu-meta (Ubuntu Focal)
 Assignee: (unassigned) => Rik Mills (rikmills)

** Changed in: kubuntu-meta (Ubuntu Jammy)
 Assignee: (unassigned) => Rik Mills (rikmills)

** Changed in: plasma-distro-release-notifier (Ubuntu Focal)
   Importance: Undecided => High

** Changed in: plasma-distro-release-notifier (Ubuntu Jammy)
   Importance: Undecided => High

** Changed in: ubuntustudio-meta (Ubuntu Jammy)
   Importance: Undecided => High

-- 
You received this bug notification because you are a member of Ubuntu
Studio Bugs, which is subscribed to ubuntustudio-meta in Ubuntu.
Matching subscriptions: UbuntuStudioPackages
https://bugs.launchpad.net/bugs/1989611

Title:
  [SRU] plasma-distro-release-notifier for Jammy, Focal

Status in kubuntu-meta package in Ubuntu:
  Fix Released
Status in plasma-distro-release-notifier package in Ubuntu:
  Fix Released
Status in ubuntustudio-meta package in Ubuntu:
  Fix Released
Status in kubuntu-meta source package in Focal:
  New
Status in plasma-distro-release-notifier source package in Focal:
  In Progress
Status in ubuntustudio-meta source package in Focal:
  Invalid
Status in kubuntu-meta source package in Jammy:
  New
Status in plasma-distro-release-notifier source package in Jammy:
  In Progress
Status in ubuntustudio-meta source package in Jammy:
  In Progress
Status in kubuntu-meta source package in Kinetic:
  Fix Released
Status in plasma-distro-release-notifier source package in Kinetic:
  Fix Released
Status in ubuntustudio-meta source package in Kinetic:
  Fix Released

Bug description:
  [ Impact ]

   * The status-quo for current Ubuntu Studio and Kubuntu users (all
  users of Ubuntu running the KDE Plasma Desktop) is that there is no
  mechanism to warn them of new releases. This is especially problematic
  for LTS releases when a new LTS release comes out, or if it is set to
  look for a new regular release.

   * This is resolved by a new package included in Kinetic - plasma-
  distro-release-notifier - which uses the backend of update-manager-
  common to identify whether or not a new version of Ubuntu has been
  released.

  [ Test Plan ]

   * Install Ubuntu Studio 22.04 -OR- Kubuntu 22.04 -OR- Kubuntu 20.04

   * Notice 20.04 does not notify of a new release despite being set to
  "lts" in /etc/update-manager/release-upgrades.

   * For 22.04 releases, change /etc/update-manager/meta-release "URI ="
  line to " URI = https://changelogs.ubuntu.com/meta-release-
  development" and /etc/update-manager/release-upgrades "Prompt=" line
  to "Prompt=normal"

   * Also, notice no prompt for updates on 22.04 releases.

  [ Where problems could occur ]

   * This will require introducing an entirely new package and adding
  the package to the kubuntu-desktop metapackage and the ubuntustudio-
  desktop metapackage for Jammy, and the kubuntu-desktop metapackage for
  focal. Things could go wrong if there is a failure to upgrade.

   * Additional failures can happen if the patch in d/patches of plasma-
  distro-release-notifier for the version number fails to point to the
  correct version number upon upload. This is easily fixed, but also
  something to keep an eye on and would be human error.

  [ Other Info ]
   
   * plasma-distro-release-notifier was initially tested to work inside of 
20.04 with positive results. The same is expected for 22.04.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/kubuntu-meta/+bug/1989611/+subscriptions


-- 
Mailing list: https://launchpad.net/~ubuntustudio-bugs
Post to : ubuntustudio-bugs@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntustudio-bugs
More help   : https://help.launchpad.net/ListHelp

[Ubuntustudio-bugs] [Bug 1989611] Re: [SRU] plasma-distro-release-notifier for Jammy, Focal

** Changed in: ubuntustudio-meta (Ubuntu Jammy)
   Status: New => In Progress

** Changed in: plasma-distro-release-notifier (Ubuntu Jammy)
   Status: New => In Progress

** Changed in: plasma-distro-release-notifier (Ubuntu Focal)
   Status: New => In Progress

-- 
You received this bug notification because you are a member of Ubuntu
Studio Bugs, which is subscribed to ubuntustudio-meta in Ubuntu.
Matching subscriptions: UbuntuStudioPackages
https://bugs.launchpad.net/bugs/1989611

Title:
  [SRU] plasma-distro-release-notifier for Jammy, Focal

Status in kubuntu-meta package in Ubuntu:
  Fix Released
Status in plasma-distro-release-notifier package in Ubuntu:
  Fix Released
Status in ubuntustudio-meta package in Ubuntu:
  Fix Released
Status in kubuntu-meta source package in Focal:
  New
Status in plasma-distro-release-notifier source package in Focal:
  In Progress
Status in ubuntustudio-meta source package in Focal:
  Invalid
Status in kubuntu-meta source package in Jammy:
  New
Status in plasma-distro-release-notifier source package in Jammy:
  In Progress
Status in ubuntustudio-meta source package in Jammy:
  In Progress
Status in kubuntu-meta source package in Kinetic:
  Fix Released
Status in plasma-distro-release-notifier source package in Kinetic:
  Fix Released
Status in ubuntustudio-meta source package in Kinetic:
  Fix Released

Bug description:
  [ Impact ]

   * The status-quo for current Ubuntu Studio and Kubuntu users (all
  users of Ubuntu running the KDE Plasma Desktop) is that there is no
  mechanism to warn them of new releases. This is especially problematic
  for LTS releases when a new LTS release comes out, or if it is set to
  look for a new regular release.

   * This is resolved by a new package included in Kinetic - plasma-
  distro-release-notifier - which uses the backend of update-manager-
  common to identify whether or not a new version of Ubuntu has been
  released.

  [ Test Plan ]

   * Install Ubuntu Studio 22.04 -OR- Kubuntu 22.04 -OR- Kubuntu 20.04

   * Notice 20.04 does not notify of a new release despite being set to
  "lts" in /etc/update-manager/release-upgrades.

   * For 22.04 releases, change /etc/update-manager/meta-release "URI ="
  line to " URI = https://changelogs.ubuntu.com/meta-release-
  development" and /etc/update-manager/release-upgrades "Prompt=" line
  to "Prompt=normal"

   * Also, notice no prompt for updates on 22.04 releases.

  [ Where problems could occur ]

   * This will require introducing an entirely new package and adding
  the package to the kubuntu-desktop metapackage and the ubuntustudio-
  desktop metapackage for Jammy, and the kubuntu-desktop metapackage for
  focal. Things could go wrong if there is a failure to upgrade.

   * Additional failures can happen if the patch in d/patches of plasma-
  distro-release-notifier for the version number fails to point to the
  correct version number upon upload. This is easily fixed, but also
  something to keep an eye on and would be human error.

  [ Other Info ]
   
   * plasma-distro-release-notifier was initially tested to work inside of 
20.04 with positive results. The same is expected for 22.04.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/kubuntu-meta/+bug/1989611/+subscriptions


-- 
Mailing list: https://launchpad.net/~ubuntustudio-bugs
Post to : ubuntustudio-bugs@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntustudio-bugs
More help   : https://help.launchpad.net/ListHelp

[Ubuntustudio-bugs] [Bug 1989263] [NEW] [FFe] plasma-distro-release-notifier for Ubuntu Studio

2022-09-10 Thread Erich Eickmeyer 

Public bug reported:

Currently awaiting approval is plasma-distro-release-notifier, an applet
which, in conjunction with update-notifier, notifies the user of a new
version of Ubuntu using the same logic that update-notifier currently
uses from the configuration in /etc/update-manager/release-upgrades.
This has been sorely missing from previous releases of Ubuntu Studio and
Kubuntu and should be included in all releases of Ubuntu Studio going
forward and should be included in currently supported releases.

Currently, users are not prompted when a new version of Ubuntu is
released, and as such, users of the Plasma desktop (Ubuntu Studio and
Kubuntu) get stuck on an EOL release very quickly. I have seen several
posts on #kubuntu and Reddit requesting help because the user simply did
not know that they needed to update their machine to a newer release.
Including this package would prevent that.

** Affects: ubuntustudio-meta (Ubuntu)
 Importance: High
 Assignee: Erich Eickmeyer  (eeickmeyer)
 Status: New

** Affects: ubuntustudio-meta (Ubuntu Kinetic)
 Importance: High
 Assignee: Erich Eickmeyer  (eeickmeyer)
 Status: New

** Also affects: ubuntustudio-meta (Ubuntu Kinetic)
   Importance: High
 Assignee: Erich Eickmeyer  (eeickmeyer)
   Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Studio Bugs, which is subscribed to ubuntustudio-meta in Ubuntu.
Matching subscriptions: UbuntuStudioPackages
https://bugs.launchpad.net/bugs/1989263

Title:
  [FFe] plasma-distro-release-notifier for Ubuntu Studio

Status in ubuntustudio-meta package in Ubuntu:
  New
Status in ubuntustudio-meta source package in Kinetic:
  New

Bug description:
  Currently awaiting approval is plasma-distro-release-notifier, an
  applet which, in conjunction with update-notifier, notifies the user
  of a new version of Ubuntu using the same logic that update-notifier
  currently uses from the configuration in /etc/update-manager/release-
  upgrades. This has been sorely missing from previous releases of
  Ubuntu Studio and Kubuntu and should be included in all releases of
  Ubuntu Studio going forward and should be included in currently
  supported releases.

  Currently, users are not prompted when a new version of Ubuntu is
  released, and as such, users of the Plasma desktop (Ubuntu Studio and
  Kubuntu) get stuck on an EOL release very quickly. I have seen several
  posts on #kubuntu and Reddit requesting help because the user simply
  did not know that they needed to update their machine to a newer
  release. Including this package would prevent that.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntustudio-meta/+bug/1989263/+subscriptions


-- 
Mailing list: https://launchpad.net/~ubuntustudio-bugs
Post to : ubuntustudio-bugs@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntustudio-bugs
More help   : https://help.launchpad.net/ListHelp

[Ubuntustudio-bugs] [Bug 1983862] Re: [FFe] Audacity 3.1 for Kinetic (was 2.4.2 FTBFS with ffmpeg 5.x)

2022-09-16 Thread Erich Eickmeyer 

After investigation, Dan and I cannot get this to work near-term, so I'm
going to have to withdraw my FFe request and, sadly, I think we're going
to have to remove Audacity from the repos for Kinetic. Release team,
feel free to unsubscribe.

** Summary changed:

- [FFe] Audacity 3.1 for Kinetic (was 2.4.2 FTBFS with ffmpeg 5.x)
+ Audacity 2.4.2 FTBFS with ffmpeg 5.x)

-- 
You received this bug notification because you are a member of Ubuntu
Studio Bugs, which is subscribed to audacity in Ubuntu.
Matching subscriptions: Ubuntu Studio Bugs
https://bugs.launchpad.net/bugs/1983862

Title:
  Audacity 2.4.2 FTBFS with ffmpeg 5.x)

Status in audacity package in Ubuntu:
  Confirmed
Status in audacity package in Debian:
  Confirmed

Bug description:
  Audacity is a very high-profile, cross-platform application. As it
  stands. Audacity has been stagnant at 2.4.2 for several releases. 3.1
  has been out for some time and is compatible with ffmpeg 5.

  At this point, we are finding our hand forced. 2.4.2 is incompatible
  with ffmpeg 5, and as such we must upgrade, patch, or remove. Users of
  Audacity would much rather see an upgrade, as I have seen in bug
  reports as of late, or in the #ubuntustudio chat.

  The biggest hurdles have been the telemetry which can be disabled by
  default as discussed via
  https://github.com/audacity/audacity/discussions/889.

  Note that the biggest requirement, wxwidgets, only recently got
  uploaded post-Feature Freeze, which otherwise would have made this FFe
  moot. This bug has been being worked on since prior to FFe, so IMO
  this is a bug fix that just happens to carry features with it, similar
  to what you'd find if wxwidgets had been uploaded prior to Feature
  Freeze.

  Basically, I'm hoping that some of the logic that can be applied here
  is that the exception is based mostly on the late upload of wxwidgets
  which was beyond the control of those involved.

  I think that having new features in an application is a better option
  than having it removed completely for the sake of a feature freeze in
  this case, especially when it's as high-profile of an application as
  this one.

  
  
  Original Description:

  https://launchpadlibrarian.net/615233650/buildlog_ubuntu-kinetic-
  amd64.audacity_2.4.2~dfsg0-5build1_BUILDING.txt.gz

  (...)
  In file included from /<>/src/AudacityApp.cpp:82:
  /<>/src/FFmpeg.h: In constructor ‘AVPacketEx::AVPacketEx()’:
  /<>/src/FFmpeg.h:892:21: warning: ‘void 
av_init_packet(AVPacket*)’ is deprecated [-Wdeprecated-declarations]
    892 |   av_init_packet(this);
    |   ~~^~
  In file included from /usr/include/x86_64-linux-gnu/libavcodec/avcodec.h:45,
   from /<>/src/FFmpeg.h:53:
  /usr/include/x86_64-linux-gnu/libavcodec/packet.h:506:6: note: declared here
    506 | void av_init_packet(AVPacket *pkt);
    |  ^~
  /<>/src/FFmpeg.h: In member function ‘void AVPacketEx::reset()’:
  /<>/src/FFmpeg.h:919:7: error: ‘av_free_packet’ was not declared 
in this scope; did you mean ‘av_new_packet’?
    919 |   av_free_packet(this);
    |   ^~
    |   av_new_packet
  /<>/src/FFmpeg.h: In member function ‘void 
AVPacketEx::steal(AVPacketEx&&)’:
  /<>/src/FFmpeg.h:926:21: warning: ‘void 
av_init_packet(AVPacket*)’ is deprecated [-Wdeprecated-declarations]
    926 |   av_init_packet();
    |   ~~^~~
  /usr/include/x86_64-linux-gnu/libavcodec/packet.h:506:6: note: declared here
    506 | void av_init_packet(AVPacket *pkt);
    |  ^~

  FFmpeg 5.0 changed the API and it required a big patch for audacity:
  https://github.com/audacity/audacity/pull/3121/files

  Note that patch is on top of master, and Debian/Ubuntu still carry old
  version 2.4.2. To fix this, the package needs to be first updated to
  3.1.3 (or later), and then have that patch applied.

  Upstream issue (now resolved): 
https://github.com/audacity/audacity/issues/2445
  Debian RC bug: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1004598

  audacity was removed from debian testing today:
  https://tracker.debian.org/news/1352473/audacity-removed-from-testing/

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/audacity/+bug/1983862/+subscriptions


-- 
Mailing list: https://launchpad.net/~ubuntustudio-bugs
Post to : ubuntustudio-bugs@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntustudio-bugs
More help   : https://help.launchpad.net/ListHelp

[Ubuntustudio-bugs] [Bug 1983862] Re: [FFe] Audacity 3.1 for Kinetic (was 2.4.2 FTBFS with ffmpeg 5.x)

2022-09-15 Thread Erich Eickmeyer 

Hi Łukasz,

I think I can summarize a bunch of this by answering the last question
first:

> Also, did anyone discuss with Debian on how they intend to proceed
here?

Per https://salsa.debian.org/multimedia-team/audacity/, they're already
moving on a ~dfsg version of 3.1.3, meaning very likely they've got this
all figured out and intend to upload shortly. However, I think in the
interest of time, it might be worth taking what has been done there, the
pristine-tar, and uploading our own version. Then *if* they upload prior
to Final Freeze, we can simply sync their version over.

I think I can don my rarely-used Debian Multimedia Team hat here and do
the testing on Dennis's packaging and see if it works, and test the
binaries as built in my PPA. If it looks good, I have no problem with
reporting back here and allowing either yourself or Dan to take a look
at the package in my PPA prior to FFe approval. This whole process
should take less than 24 hours.

-- 
You received this bug notification because you are a member of Ubuntu
Studio Bugs, which is subscribed to audacity in Ubuntu.
Matching subscriptions: Ubuntu Studio Bugs
https://bugs.launchpad.net/bugs/1983862

Title:
  [FFe] Audacity 3.1 for Kinetic (was 2.4.2 FTBFS with ffmpeg 5.x)

Status in audacity package in Ubuntu:
  Confirmed
Status in audacity package in Debian:
  Confirmed

Bug description:
  Audacity is a very high-profile, cross-platform application. As it
  stands. Audacity has been stagnant at 2.4.2 for several releases. 3.1
  has been out for some time and is compatible with ffmpeg 5.

  At this point, we are finding our hand forced. 2.4.2 is incompatible
  with ffmpeg 5, and as such we must upgrade, patch, or remove. Users of
  Audacity would much rather see an upgrade, as I have seen in bug
  reports as of late, or in the #ubuntustudio chat.

  The biggest hurdles have been the telemetry which can be disabled by
  default as discussed via
  https://github.com/audacity/audacity/discussions/889.

  Note that the biggest requirement, wxwidgets, only recently got
  uploaded post-Feature Freeze, which otherwise would have made this FFe
  moot. This bug has been being worked on since prior to FFe, so IMO
  this is a bug fix that just happens to carry features with it, similar
  to what you'd find if wxwidgets had been uploaded prior to Feature
  Freeze.

  Basically, I'm hoping that some of the logic that can be applied here
  is that the exception is based mostly on the late upload of wxwidgets
  which was beyond the control of those involved.

  I think that having new features in an application is a better option
  than having it removed completely for the sake of a feature freeze in
  this case, especially when it's as high-profile of an application as
  this one.

  
  
  Original Description:

  https://launchpadlibrarian.net/615233650/buildlog_ubuntu-kinetic-
  amd64.audacity_2.4.2~dfsg0-5build1_BUILDING.txt.gz

  (...)
  In file included from /<>/src/AudacityApp.cpp:82:
  /<>/src/FFmpeg.h: In constructor ‘AVPacketEx::AVPacketEx()’:
  /<>/src/FFmpeg.h:892:21: warning: ‘void 
av_init_packet(AVPacket*)’ is deprecated [-Wdeprecated-declarations]
    892 |   av_init_packet(this);
    |   ~~^~
  In file included from /usr/include/x86_64-linux-gnu/libavcodec/avcodec.h:45,
   from /<>/src/FFmpeg.h:53:
  /usr/include/x86_64-linux-gnu/libavcodec/packet.h:506:6: note: declared here
    506 | void av_init_packet(AVPacket *pkt);
    |  ^~
  /<>/src/FFmpeg.h: In member function ‘void AVPacketEx::reset()’:
  /<>/src/FFmpeg.h:919:7: error: ‘av_free_packet’ was not declared 
in this scope; did you mean ‘av_new_packet’?
    919 |   av_free_packet(this);
    |   ^~
    |   av_new_packet
  /<>/src/FFmpeg.h: In member function ‘void 
AVPacketEx::steal(AVPacketEx&&)’:
  /<>/src/FFmpeg.h:926:21: warning: ‘void 
av_init_packet(AVPacket*)’ is deprecated [-Wdeprecated-declarations]
    926 |   av_init_packet();
    |   ~~^~~
  /usr/include/x86_64-linux-gnu/libavcodec/packet.h:506:6: note: declared here
    506 | void av_init_packet(AVPacket *pkt);
    |  ^~

  FFmpeg 5.0 changed the API and it required a big patch for audacity:
  https://github.com/audacity/audacity/pull/3121/files

  Note that patch is on top of master, and Debian/Ubuntu still carry old
  version 2.4.2. To fix this, the package needs to be first updated to
  3.1.3 (or later), and then have that patch applied.

  Upstream issue (now resolved): 
https://github.com/audacity/audacity/issues/2445
  Debian RC bug: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1004598

  audacity was removed from debian testing today:
  https://tracker.debian.org/news/1352473/audacity-removed-from-testing/

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/audacity/+bug/1983862/+subscriptions


-- 
Mailing list:

[Ubuntustudio-bugs] [Bug 1983862] Re: [FFe] Audacity 3.1 for Kinetic (was 2.4.2 FTBFS with ffmpeg 5.x)

2022-09-15 Thread Erich Eickmeyer 

Well, after doing a ton of work on this, I ran into a huge roadblock and
I'm fearing the worst. Right now, it FTBFS and I'm in over my head.
https://launchpadlibrarian.net/623527544/buildlog_ubuntu-kinetic-
amd64.audacity_3.1.3~dfsg0-0ubuntu1~ppa4_BUILDING.txt.gz is my latest
buildlog and I don't understand what's happening. If anybody has any
ideas, let me know. I suspect GCC 12 compatibility issues now.

-- 
You received this bug notification because you are a member of Ubuntu
Studio Bugs, which is subscribed to audacity in Ubuntu.
Matching subscriptions: Ubuntu Studio Bugs
https://bugs.launchpad.net/bugs/1983862

Title:
  [FFe] Audacity 3.1 for Kinetic (was 2.4.2 FTBFS with ffmpeg 5.x)

Status in audacity package in Ubuntu:
  Confirmed
Status in audacity package in Debian:
  Confirmed

Bug description:
  Audacity is a very high-profile, cross-platform application. As it
  stands. Audacity has been stagnant at 2.4.2 for several releases. 3.1
  has been out for some time and is compatible with ffmpeg 5.

  At this point, we are finding our hand forced. 2.4.2 is incompatible
  with ffmpeg 5, and as such we must upgrade, patch, or remove. Users of
  Audacity would much rather see an upgrade, as I have seen in bug
  reports as of late, or in the #ubuntustudio chat.

  The biggest hurdles have been the telemetry which can be disabled by
  default as discussed via
  https://github.com/audacity/audacity/discussions/889.

  Note that the biggest requirement, wxwidgets, only recently got
  uploaded post-Feature Freeze, which otherwise would have made this FFe
  moot. This bug has been being worked on since prior to FFe, so IMO
  this is a bug fix that just happens to carry features with it, similar
  to what you'd find if wxwidgets had been uploaded prior to Feature
  Freeze.

  Basically, I'm hoping that some of the logic that can be applied here
  is that the exception is based mostly on the late upload of wxwidgets
  which was beyond the control of those involved.

  I think that having new features in an application is a better option
  than having it removed completely for the sake of a feature freeze in
  this case, especially when it's as high-profile of an application as
  this one.

  
  
  Original Description:

  https://launchpadlibrarian.net/615233650/buildlog_ubuntu-kinetic-
  amd64.audacity_2.4.2~dfsg0-5build1_BUILDING.txt.gz

  (...)
  In file included from /<>/src/AudacityApp.cpp:82:
  /<>/src/FFmpeg.h: In constructor ‘AVPacketEx::AVPacketEx()’:
  /<>/src/FFmpeg.h:892:21: warning: ‘void 
av_init_packet(AVPacket*)’ is deprecated [-Wdeprecated-declarations]
    892 |   av_init_packet(this);
    |   ~~^~
  In file included from /usr/include/x86_64-linux-gnu/libavcodec/avcodec.h:45,
   from /<>/src/FFmpeg.h:53:
  /usr/include/x86_64-linux-gnu/libavcodec/packet.h:506:6: note: declared here
    506 | void av_init_packet(AVPacket *pkt);
    |  ^~
  /<>/src/FFmpeg.h: In member function ‘void AVPacketEx::reset()’:
  /<>/src/FFmpeg.h:919:7: error: ‘av_free_packet’ was not declared 
in this scope; did you mean ‘av_new_packet’?
    919 |   av_free_packet(this);
    |   ^~
    |   av_new_packet
  /<>/src/FFmpeg.h: In member function ‘void 
AVPacketEx::steal(AVPacketEx&&)’:
  /<>/src/FFmpeg.h:926:21: warning: ‘void 
av_init_packet(AVPacket*)’ is deprecated [-Wdeprecated-declarations]
    926 |   av_init_packet();
    |   ~~^~~
  /usr/include/x86_64-linux-gnu/libavcodec/packet.h:506:6: note: declared here
    506 | void av_init_packet(AVPacket *pkt);
    |  ^~

  FFmpeg 5.0 changed the API and it required a big patch for audacity:
  https://github.com/audacity/audacity/pull/3121/files

  Note that patch is on top of master, and Debian/Ubuntu still carry old
  version 2.4.2. To fix this, the package needs to be first updated to
  3.1.3 (or later), and then have that patch applied.

  Upstream issue (now resolved): 
https://github.com/audacity/audacity/issues/2445
  Debian RC bug: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1004598

  audacity was removed from debian testing today:
  https://tracker.debian.org/news/1352473/audacity-removed-from-testing/

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/audacity/+bug/1983862/+subscriptions


-- 
Mailing list: https://launchpad.net/~ubuntustudio-bugs
Post to : ubuntustudio-bugs@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntustudio-bugs
More help   : https://help.launchpad.net/ListHelp

[Ubuntustudio-bugs] [Bug 1989611] Re: [SRU] plasma-distro-release-notifier for Jammy, Focal

** Also affects: plasma-distro-release-notifier (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: plasma-distro-release-notifier (Ubuntu Kinetic)
   Status: New => Fix Released

** Changed in: plasma-distro-release-notifier (Ubuntu Jammy)
 Assignee: (unassigned) => Erich Eickmeyer  (eeickmeyer)

** Changed in: plasma-distro-release-notifier (Ubuntu Focal)
 Assignee: (unassigned) => Erich Eickmeyer  (eeickmeyer)

** Changed in: ubuntustudio-meta (Ubuntu Kinetic)
 Assignee: Erich Eickmeyer  (eeickmeyer) => (unassigned)

-- 
You received this bug notification because you are a member of Ubuntu
Studio Bugs, which is subscribed to ubuntustudio-meta in Ubuntu.
Matching subscriptions: UbuntuStudioPackages
https://bugs.launchpad.net/bugs/1989611

Title:
  [SRU] plasma-distro-release-notifier for Jammy, Focal

Status in kubuntu-meta package in Ubuntu:
  Fix Released
Status in plasma-distro-release-notifier package in Ubuntu:
  Fix Released
Status in ubuntustudio-meta package in Ubuntu:
  Fix Released
Status in kubuntu-meta source package in Focal:
  New
Status in plasma-distro-release-notifier source package in Focal:
  New
Status in ubuntustudio-meta source package in Focal:
  Invalid
Status in kubuntu-meta source package in Jammy:
  New
Status in plasma-distro-release-notifier source package in Jammy:
  New
Status in ubuntustudio-meta source package in Jammy:
  New
Status in kubuntu-meta source package in Kinetic:
  Fix Released
Status in plasma-distro-release-notifier source package in Kinetic:
  Fix Released
Status in ubuntustudio-meta source package in Kinetic:
  Fix Released

Bug description:
  [ Impact ]

   * The status-quo for current Ubuntu Studio and Kubuntu users (all
  users of Ubuntu running the KDE Plasma Desktop) is that there is no
  mechanism to warn them of new releases. This is especially problematic
  for LTS releases when a new LTS release comes out, or if it is set to
  look for a new regular release.

   * This is resolved by a new package included in Kinetic - plasma-
  distro-release-notifier - which uses the backend of update-manager-
  common to identify whether or not a new version of Ubuntu has been
  released.

  [ Test Plan ]

   * Install Ubuntu Studio 22.04 -OR- Kubuntu 22.04 -OR- Kubuntu 20.04

   * Notice 20.04 does not notify of a new release despite being set to
  "lts" in /etc/update-manager/release-upgrades.

   * For 22.04 releases, change /etc/update-manager/meta-release "URI ="
  line to " URI = https://changelogs.ubuntu.com/meta-release-
  development" and /etc/update-manager/release-upgrades "Prompt=" line
  to "Prompt=normal"

   * Also, notice no prompt for updates on 22.04 releases.

  [ Where problems could occur ]

   * This will require introducing an entirely new package and adding
  the package to the kubuntu-desktop metapackage and the ubuntustudio-
  desktop metapackage for Jammy, and the kubuntu-desktop metapackage for
  focal. Things could go wrong if there is a failure to upgrade.

   * Additional failures can happen if the patch in d/patches of plasma-
  distro-release-notifier for the version number fails to point to the
  correct version number upon upload. This is easily fixed, but also
  something to keep an eye on and would be human error.

  [ Other Info ]
   
   * plasma-distro-release-notifier was initially tested to work inside of 
20.04 with positive results. The same is expected for 22.04.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/kubuntu-meta/+bug/1989611/+subscriptions


-- 
Mailing list: https://launchpad.net/~ubuntustudio-bugs
Post to : ubuntustudio-bugs@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntustudio-bugs
More help   : https://help.launchpad.net/ListHelp

[Ubuntustudio-bugs] [Bug 1983862] Re: [FFe] Audacity 3.1 for Kinetic (was 2.4.2 FTBFS with ffmpeg 5.x)

** Changed in: audacity (Ubuntu)
   Status: New => Confirmed

-- 
You received this bug notification because you are a member of Ubuntu
Studio Bugs, which is subscribed to audacity in Ubuntu.
Matching subscriptions: Ubuntu Studio Bugs
https://bugs.launchpad.net/bugs/1983862

Title:
  [FFe] Audacity 3.1 for Kinetic (was 2.4.2 FTBFS with ffmpeg 5.x)

Status in audacity package in Ubuntu:
  Confirmed
Status in audacity package in Debian:
  Confirmed

Bug description:
  Audacity is a very high-profile, cross-platform application. As it
  stands. Audacity has been stagnant at 2.4.2 for several releases. 3.1
  has been out for some time and is compatible with ffmpeg 5.

  At this point, we are finding our hand forced. 2.4.2 is incompatible
  with ffmpeg 5, and as such we must upgrade, patch, or remove. Users of
  Audacity would much rather see an upgrade, as I have seen in bug
  reports as of late, or in the #ubuntustudio chat.

  The biggest hurdles have been the telemetry which can be disabled by
  default as discussed via
  https://github.com/audacity/audacity/discussions/889.

  Note that the biggest requirement, wxwidgets, only recently got
  uploaded post-Feature Freeze, which otherwise would have made this FFe
  moot. This bug has been being worked on since prior to FFe, so IMO
  this is a bug fix that just happens to carry features with it, similar
  to what you'd find if wxwidgets had been uploaded prior to Feature
  Freeze.

  Basically, I'm hoping that some of the logic that can be applied here
  is that the exception is based mostly on the late upload of wxwidgets
  which was beyond the control of those involved.

  I think that having new features in an application is a better option
  than having it removed completely for the sake of a feature freeze in
  this case, especially when it's as high-profile of an application as
  this one.

  
  
  Original Description:

  https://launchpadlibrarian.net/615233650/buildlog_ubuntu-kinetic-
  amd64.audacity_2.4.2~dfsg0-5build1_BUILDING.txt.gz

  (...)
  In file included from /<>/src/AudacityApp.cpp:82:
  /<>/src/FFmpeg.h: In constructor ‘AVPacketEx::AVPacketEx()’:
  /<>/src/FFmpeg.h:892:21: warning: ‘void 
av_init_packet(AVPacket*)’ is deprecated [-Wdeprecated-declarations]
    892 |   av_init_packet(this);
    |   ~~^~
  In file included from /usr/include/x86_64-linux-gnu/libavcodec/avcodec.h:45,
   from /<>/src/FFmpeg.h:53:
  /usr/include/x86_64-linux-gnu/libavcodec/packet.h:506:6: note: declared here
    506 | void av_init_packet(AVPacket *pkt);
    |  ^~
  /<>/src/FFmpeg.h: In member function ‘void AVPacketEx::reset()’:
  /<>/src/FFmpeg.h:919:7: error: ‘av_free_packet’ was not declared 
in this scope; did you mean ‘av_new_packet’?
    919 |   av_free_packet(this);
    |   ^~
    |   av_new_packet
  /<>/src/FFmpeg.h: In member function ‘void 
AVPacketEx::steal(AVPacketEx&&)’:
  /<>/src/FFmpeg.h:926:21: warning: ‘void 
av_init_packet(AVPacket*)’ is deprecated [-Wdeprecated-declarations]
    926 |   av_init_packet();
    |   ~~^~~
  /usr/include/x86_64-linux-gnu/libavcodec/packet.h:506:6: note: declared here
    506 | void av_init_packet(AVPacket *pkt);
    |  ^~

  FFmpeg 5.0 changed the API and it required a big patch for audacity:
  https://github.com/audacity/audacity/pull/3121/files

  Note that patch is on top of master, and Debian/Ubuntu still carry old
  version 2.4.2. To fix this, the package needs to be first updated to
  3.1.3 (or later), and then have that patch applied.

  Upstream issue (now resolved): 
https://github.com/audacity/audacity/issues/2445
  Debian RC bug: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1004598

  audacity was removed from debian testing today:
  https://tracker.debian.org/news/1352473/audacity-removed-from-testing/

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/audacity/+bug/1983862/+subscriptions


-- 
Mailing list: https://launchpad.net/~ubuntustudio-bugs
Post to : ubuntustudio-bugs@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntustudio-bugs
More help   : https://help.launchpad.net/ListHelp

[Ubuntustudio-bugs] [Bug 1989611] [NEW] [SRU] plasma-distro-release-notifier for Jammy, Focal

Public bug reported:

[ Impact ]

 * The status-quo for current Ubuntu Studio and Kubuntu users (all users
of Ubuntu running the KDE Plasma Desktop) is that there is no mechanism
to warn them of new releases. This is especially problematic for LTS
releases when a new LTS release comes out, or if it is set to look for a
new regular release.

 * This is resolved by a new package included in Kinetic - plasma-
distro-release-notifier - which uses the backend of update-manager-
common to identify whether or not a new version of Ubuntu has been
released.

[ Test Plan ]

 * Install Ubuntu Studio 22.04 -OR- Kubuntu 22.04 -OR- Kubuntu 20.04

 * Notice 20.04 does not notify of a new release despite being set to
"lts" in /etc/update-manager/release-upgrades.

 * For 22.04 releases, change /etc/update-manager/meta-release "URI ="
line to " URI = https://changelogs.ubuntu.com/meta-release-development;
and /etc/update-manager/release-upgrades "Prompt=" line to
"Prompt=normal"

 * Also, notice no prompt for updates on 22.04 releases.

[ Where problems could occur ]

 * This will require introducing an entirely new package and adding the
package to the kubuntu-desktop metapackage and the ubuntustudio-desktop
metapackage for Jammy, and the kubuntu-desktop metapackage for focal.
Things could go wrong if there is a failure to upgrade.

 * Additional failures can happen if the patch in d/patches of plasma-
distro-release-notifier for the version number fails to point to the
correct version number upon upload. This is easily fixed, but also
something to keep an eye on and would be human error.

[ Other Info ]
 
 * plasma-distro-release-notifier was initially tested to work inside of 20.04 
with positive results. The same is expected for 22.04.

** Affects: kubuntu-meta (Ubuntu)
 Importance: Undecided
 Status: Fix Released

** Affects: plasma-distro-release-notifier (Ubuntu)
 Importance: Undecided
 Status: Fix Released

** Affects: ubuntustudio-meta (Ubuntu)
 Importance: Undecided
 Status: Fix Released

** Affects: kubuntu-meta (Ubuntu Focal)
 Importance: Undecided
 Status: New

** Affects: plasma-distro-release-notifier (Ubuntu Focal)
     Importance: Undecided
 Assignee: Erich Eickmeyer  (eeickmeyer)
 Status: New

** Affects: ubuntustudio-meta (Ubuntu Focal)
 Importance: Undecided
 Status: Invalid

** Affects: kubuntu-meta (Ubuntu Jammy)
 Importance: Undecided
 Status: New

** Affects: plasma-distro-release-notifier (Ubuntu Jammy)
     Importance: Undecided
 Assignee: Erich Eickmeyer  (eeickmeyer)
 Status: New

** Affects: ubuntustudio-meta (Ubuntu Jammy)
     Importance: Undecided
 Assignee: Erich Eickmeyer  (eeickmeyer)
 Status: New

** Affects: kubuntu-meta (Ubuntu Kinetic)
 Importance: Undecided
 Status: Fix Released

** Affects: plasma-distro-release-notifier (Ubuntu Kinetic)
 Importance: Undecided
 Status: Fix Released

** Affects: ubuntustudio-meta (Ubuntu Kinetic)
 Importance: Undecided
 Status: Fix Released


** Tags: focal jammy

** Also affects: ubuntustudio-meta (Ubuntu Jammy)
   Importance: Undecided
   Status: New

** Also affects: ubuntustudio-meta (Ubuntu Focal)
   Importance: Undecided
   Status: New

** Also affects: ubuntustudio-meta (Ubuntu Kinetic)
   Importance: Undecided
 Assignee: Erich Eickmeyer  (eeickmeyer)
   Status: New

** Changed in: ubuntustudio-meta (Ubuntu Focal)
   Status: New => Invalid

** Changed in: ubuntustudio-meta (Ubuntu Kinetic)
   Status: New => Fix Released

** Also affects: kubuntu-meta (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: kubuntu-meta (Ubuntu Kinetic)
   Status: New => Fix Released

** Changed in: ubuntustudio-meta (Ubuntu Jammy)
 Assignee: (unassigned) => Erich Eickmeyer  (eeickmeyer)

-- 
You received this bug notification because you are a member of Ubuntu
Studio Bugs, which is subscribed to ubuntustudio-meta in Ubuntu.
Matching subscriptions: UbuntuStudioPackages
https://bugs.launchpad.net/bugs/1989611

Title:
  [SRU] plasma-distro-release-notifier for Jammy, Focal

Status in kubuntu-meta package in Ubuntu:
  Fix Released
Status in plasma-distro-release-notifier package in Ubuntu:
  Fix Released
Status in ubuntustudio-meta package in Ubuntu:
  Fix Released
Status in kubuntu-meta source package in Focal:
  New
Status in plasma-distro-release-notifier source package in Focal:
  New
Status in ubuntustudio-meta source package in Focal:
  Invalid
Status in kubuntu-meta source package in Jammy:
  New
Status in plasma-distro-release-notifier source package in Jammy:
  New
Status in ubuntustudio-meta source package in Jammy:
  New
Status in kubuntu-meta source package in Kinetic:
  Fix Released
Status in plasma-distro-release-notifier source package in Kinetic:
  Fix Released
Status in ubuntustudio-meta source packag

[Ubuntustudio-bugs] [Bug 1989611] Re: [SRU] plasma-distro-release-notifier for Jammy, Focal

** Tags added: kubuntu ubuntustudio

-- 
You received this bug notification because you are a member of Ubuntu
Studio Bugs, which is subscribed to ubuntustudio-meta in Ubuntu.
Matching subscriptions: UbuntuStudioPackages
https://bugs.launchpad.net/bugs/1989611

Title:
  [SRU] plasma-distro-release-notifier for Jammy, Focal

Status in kubuntu-meta package in Ubuntu:
  Fix Released
Status in plasma-distro-release-notifier package in Ubuntu:
  Fix Released
Status in ubuntustudio-meta package in Ubuntu:
  Fix Released
Status in kubuntu-meta source package in Focal:
  New
Status in plasma-distro-release-notifier source package in Focal:
  New
Status in ubuntustudio-meta source package in Focal:
  Invalid
Status in kubuntu-meta source package in Jammy:
  New
Status in plasma-distro-release-notifier source package in Jammy:
  New
Status in ubuntustudio-meta source package in Jammy:
  New
Status in kubuntu-meta source package in Kinetic:
  Fix Released
Status in plasma-distro-release-notifier source package in Kinetic:
  Fix Released
Status in ubuntustudio-meta source package in Kinetic:
  Fix Released

Bug description:
  [ Impact ]

   * The status-quo for current Ubuntu Studio and Kubuntu users (all
  users of Ubuntu running the KDE Plasma Desktop) is that there is no
  mechanism to warn them of new releases. This is especially problematic
  for LTS releases when a new LTS release comes out, or if it is set to
  look for a new regular release.

   * This is resolved by a new package included in Kinetic - plasma-
  distro-release-notifier - which uses the backend of update-manager-
  common to identify whether or not a new version of Ubuntu has been
  released.

  [ Test Plan ]

   * Install Ubuntu Studio 22.04 -OR- Kubuntu 22.04 -OR- Kubuntu 20.04

   * Notice 20.04 does not notify of a new release despite being set to
  "lts" in /etc/update-manager/release-upgrades.

   * For 22.04 releases, change /etc/update-manager/meta-release "URI ="
  line to " URI = https://changelogs.ubuntu.com/meta-release-
  development" and /etc/update-manager/release-upgrades "Prompt=" line
  to "Prompt=normal"

   * Also, notice no prompt for updates on 22.04 releases.

  [ Where problems could occur ]

   * This will require introducing an entirely new package and adding
  the package to the kubuntu-desktop metapackage and the ubuntustudio-
  desktop metapackage for Jammy, and the kubuntu-desktop metapackage for
  focal. Things could go wrong if there is a failure to upgrade.

   * Additional failures can happen if the patch in d/patches of plasma-
  distro-release-notifier for the version number fails to point to the
  correct version number upon upload. This is easily fixed, but also
  something to keep an eye on and would be human error.

  [ Other Info ]
   
   * plasma-distro-release-notifier was initially tested to work inside of 
20.04 with positive results. The same is expected for 22.04.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/kubuntu-meta/+bug/1989611/+subscriptions


-- 
Mailing list: https://launchpad.net/~ubuntustudio-bugs
Post to : ubuntustudio-bugs@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntustudio-bugs
More help   : https://help.launchpad.net/ListHelp

[Ubuntustudio-bugs] [Bug 1983862] Re: FTBFS with ffmpeg 5.x

Second proposal for Kinetic since removal will make for a lot of angry
Ubuntu (and Ubuntu Studio) users:

* FFe this in. Might be a hard sell, but if we don't, then we lose a
very high-profile application. Note that this bug has been worked-on
since early August, prior to Feature Freeze, so I think that makes a
very good case for a FFe.

** Summary changed:

- FTBFS with ffmpeg 5.x
+ [FFe] Audacity 3.1 for Kinetic (was 2.4.2 FTBFS with ffmpeg 5.x)

-- 
You received this bug notification because you are a member of Ubuntu
Studio Bugs, which is subscribed to audacity in Ubuntu.
Matching subscriptions: Ubuntu Studio Bugs
https://bugs.launchpad.net/bugs/1983862

Title:
  [FFe] Audacity 3.1 for Kinetic (was 2.4.2 FTBFS with ffmpeg 5.x)

Status in audacity package in Ubuntu:
  New
Status in audacity package in Debian:
  Confirmed

Bug description:
  https://launchpadlibrarian.net/615233650/buildlog_ubuntu-kinetic-
  amd64.audacity_2.4.2~dfsg0-5build1_BUILDING.txt.gz

  (...)
  In file included from /<>/src/AudacityApp.cpp:82:
  /<>/src/FFmpeg.h: In constructor ‘AVPacketEx::AVPacketEx()’:
  /<>/src/FFmpeg.h:892:21: warning: ‘void 
av_init_packet(AVPacket*)’ is deprecated [-Wdeprecated-declarations]
892 |   av_init_packet(this);
|   ~~^~
  In file included from /usr/include/x86_64-linux-gnu/libavcodec/avcodec.h:45,
   from /<>/src/FFmpeg.h:53:
  /usr/include/x86_64-linux-gnu/libavcodec/packet.h:506:6: note: declared here
506 | void av_init_packet(AVPacket *pkt);
|  ^~
  /<>/src/FFmpeg.h: In member function ‘void AVPacketEx::reset()’:
  /<>/src/FFmpeg.h:919:7: error: ‘av_free_packet’ was not declared 
in this scope; did you mean ‘av_new_packet’?
919 |   av_free_packet(this);
|   ^~
|   av_new_packet
  /<>/src/FFmpeg.h: In member function ‘void 
AVPacketEx::steal(AVPacketEx&&)’:
  /<>/src/FFmpeg.h:926:21: warning: ‘void 
av_init_packet(AVPacket*)’ is deprecated [-Wdeprecated-declarations]
926 |   av_init_packet();
|   ~~^~~
  /usr/include/x86_64-linux-gnu/libavcodec/packet.h:506:6: note: declared here
506 | void av_init_packet(AVPacket *pkt);
|  ^~

  FFmpeg 5.0 changed the API and it required a big patch for audacity:
  https://github.com/audacity/audacity/pull/3121/files

  Note that patch is on top of master, and Debian/Ubuntu still carry old
  version 2.4.2. To fix this, the package needs to be first updated to
  3.1.3 (or later), and then have that patch applied.

  Upstream issue (now resolved): 
https://github.com/audacity/audacity/issues/2445
  Debian RC bug: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1004598

  audacity was removed from debian testing today:
  https://tracker.debian.org/news/1352473/audacity-removed-from-testing/

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/audacity/+bug/1983862/+subscriptions


-- 
Mailing list: https://launchpad.net/~ubuntustudio-bugs
Post to : ubuntustudio-bugs@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntustudio-bugs
More help   : https://help.launchpad.net/ListHelp

[Ubuntustudio-bugs] [Bug 1983862] Re: [FFe] Audacity 3.1 for Kinetic (was 2.4.2 FTBFS with ffmpeg 5.x)