[Ubuntustudio-bugs] [Bug 2063403] Re: /home/oem and /home/oem/Desktop is owned by root after oem installation, causing the OEM configuration environment to be (nearly) unusable

2024-04-25 Thread Launchpad Bug Tracker
This bug was fixed in the package calamares-settings-ubuntu - 1:24.04.39

---
calamares-settings-ubuntu (1:24.04.39) noble; urgency=medium

  * Fix permissions on /home/oem when doing OEM installations. (LP:
#2063403)

 -- Aaron Rainbolt   Thu, 25 Apr 2024 00:01:37
-0500

** Changed in: calamares-settings-ubuntu (Ubuntu)
   Status: Triaged => Fix Released

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

Title:
  /home/oem and /home/oem/Desktop is owned by root after oem
  installation, causing the OEM configuration environment to be (nearly)
  unusable

Status in calamares-settings-ubuntu package in Ubuntu:
  Fix Released

Bug description:
  Steps to reproduce:

  1: Boot an ISO of Kubuntu 24.04 Release Candidate.
  2: Select "OEM mode (for manufacturers)" at bootup.
  3: Proceed through the installation.
  4: Boot into the OEM user.

  Expected result: The system should boot normally.

  Actual result: Plasma will fail to start.

  Reason: I foolishly instructed a fellow Ubuntu Developer to add code
  to calamares-settings-ubuntu that drops a desktop file into
  /home/oem/Desktop that allows exiting OEM configuration mode easily
  (similar to how oem-config works). I failed to take into account that
  having the code drop this file into place when the code runs as root
  would mean that /home/oem/Desktop (and also /home/oem) would end up
  owned by root. Because they are owned by root, Plasma and Unity are
  unable to start. LXQt starts, but won't function as expected.

  This requires only one line of code to fix per release - a simple
  `chown -R oem:oem /home/oem` is needed after extracting the OEM mode
  tarball into the root filesystem of the installed system. This is a
  very safe change to make because it's confined only to OEM mode (the
  code never runs outside of an OEM installation context), and, well,
  OEM mode is already hopelessly broken, we can't break it much more :P

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/calamares-settings-ubuntu/+bug/2063403/+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 2063354] Re: Calamares based flavours do not set grub-{efi, pc}/install_devices debconf

2024-04-24 Thread Launchpad Bug Tracker
This bug was fixed in the package calamares - 3.3.5-0ubuntu4

---
calamares (3.3.5-0ubuntu4) noble; urgency=medium

  * Populate grub-{efi,pc}/install_devices debconf config (LP:
#2063354).

 -- Simon Quigley   Wed, 24 Apr 2024 15:28:29 -0500

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

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

Title:
  Calamares based flavours do not set grub-{efi,pc}/install_devices
  debconf

Status in calamares package in Ubuntu:
  Fix Released
Status in calamares source package in Noble:
  Fix Released

Bug description:
  This debconf is required to be set for grub package reinstallations
  (especially grub-pc) to work correctly.

  This was masked in the 23.10 cycle due to
  https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1889556.

  That workaround was removed in the 24.04 cycle in
  https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/2043995.

  This will result in Calamares based installs throwing debconf prompt
  at the user to choose a GRUB install device upon GRUB package
  upgrades.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/calamares/+bug/2063354/+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 2063108] Re: Ubuntu Unity fails to install with no network

2024-04-22 Thread Launchpad Bug Tracker
This bug was fixed in the package calamares-settings-ubuntu - 1:24.04.38

---
calamares-settings-ubuntu (1:24.04.38) noble; urgency=high

  * Do not remove zram-config on Ubuntu Unity, it does not exist in the first
place (LP: #2063108).

 -- Simon Quigley   Mon, 22 Apr 2024 07:10:28 -0500

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

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

Title:
  Ubuntu Unity fails to install with no network

Status in calamares-settings-ubuntu package in Ubuntu:
  Fix Released

Bug description:
  Fails during the `packages` module, rs2009 sent me a screenshot

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/calamares-settings-ubuntu/+bug/2063108/+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 2062945] [NEW] Kubuntu 24.04 (Beta) Installer ISO shows Lubuntu artwork

2024-04-20 Thread Launchpad Bug Tracker
You have been subscribed to a public bug:

When doing a fresh install of Kubuntu 24.04 (Beta), and choosing the
"install to disk" option rather than the Live CD option, during the
actual installation of the operating system, the artwork and messaging
that's shown to the user (the commercials) are for Lubuntu rather than
Kubuntu. This is probably an oversight but it should probably be
corrected before 24.04 goes live in a few days. Apologies if this bug
has already been reported.

Thank you

ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: ubiquity (not installed)
ProcVersionSignature: Ubuntu 6.8.0-22.22-generic 6.8.1
Uname: Linux 6.8.0-22-generic x86_64
ApportVersion: 2.28.0-0ubuntu1
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: KDE
Date: Fri Apr 19 22:05:28 2024
InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz --- quiet splash
InstallationDate: Installed on 2024-04-20 (0 days ago)
InstallationMedia: Kubuntu 24.04 LTS "Noble Numbat" - Beta amd64 (20240411.2)
SourcePackage: ubiquity
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: calamares-settings-ubuntu (Ubuntu)
 Importance: Undecided
 Status: Fix Released


** Tags: amd64 apport-bug noble
-- 
Kubuntu 24.04 (Beta) Installer ISO shows Lubuntu artwork 
https://bugs.launchpad.net/bugs/2062945
You received this bug notification because you are a member of Ubuntu Studio 
Bugs, which is subscribed to calamares-settings-ubuntu in Ubuntu.

-- 
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 2060928] Re: First boot after OEM install should have a desktop icon installed for finishing setup

2024-04-19 Thread Launchpad Bug Tracker
This bug was fixed in the package calamares-settings-ubuntu - 1:24.04.37

---
calamares-settings-ubuntu (1:24.04.37) noble; urgency=medium

  * Correctly lengthen timeouts for network and initramfs package commands.
(LP: #2060429)

 -- Aaron Rainbolt   Fri, 19 Apr 2024 18:52:09
-0500

** Changed in: calamares-settings-ubuntu (Ubuntu Noble)
   Status: Fix Committed => Fix Released

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

Title:
  First boot after OEM install should have a desktop icon installed for
  finishing setup

Status in calamares-settings-ubuntu package in Ubuntu:
  Fix Released
Status in calamares-settings-ubuntu source package in Noble:
  Fix Released

Bug description:
  Should be a simple symlink of some kind, may have to do some Calamares
  magic to DTRT based on what the user is called

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/calamares-settings-ubuntu/+bug/2060928/+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 2062438] Re: pkgselect module offers Thunderbird as a third-party app on Kubuntu when Thunderbird ships with Kubuntu

2024-04-19 Thread Launchpad Bug Tracker
This bug was fixed in the package calamares-settings-ubuntu - 1:24.04.37

---
calamares-settings-ubuntu (1:24.04.37) noble; urgency=medium

  * Correctly lengthen timeouts for network and initramfs package commands.
(LP: #2060429)

 -- Aaron Rainbolt   Fri, 19 Apr 2024 18:52:09
-0500

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

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

Title:
  pkgselect module offers Thunderbird as a third-party app on Kubuntu
  when Thunderbird ships with Kubuntu

Status in calamares-settings-ubuntu package in Ubuntu:
  Fix Released

Bug description:
  On the "Customize" screen of the installer, one of the additional apps
  you can install is Thunderbird. This makes sense on Lubuntu, where
  Thunderbird isn't installed by default, but Thunderbird *is* installed
  by default on Kubuntu, making the checkbox confusing and unnecessary
  there.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/calamares-settings-ubuntu/+bug/2062438/+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 2060429] Re: lubuntu noble - /usr/libexec/fixconkeys-part2 failed to finish in 30 seconds.

2024-04-19 Thread Launchpad Bug Tracker
This bug was fixed in the package calamares-settings-ubuntu - 1:24.04.37

---
calamares-settings-ubuntu (1:24.04.37) noble; urgency=medium

  * Correctly lengthen timeouts for network and initramfs package commands.
(LP: #2060429)

 -- Aaron Rainbolt   Fri, 19 Apr 2024 18:52:09
-0500

** Changed in: calamares-settings-ubuntu (Ubuntu)
   Status: Fix Committed => Fix Released

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

Title:
  lubuntu noble - /usr/libexec/fixconkeys-part2 failed to finish in 30
  seconds.

Status in calamares-settings-ubuntu package in Ubuntu:
  Fix Released

Bug description:
  install to
  - hp dc7700 (c2d-e6230, 7gb, amd/ati rv610/radeon hd2400 pro/xt)
  testcase: install using existing partition

  
  Command /usr/libexec/fixconkeys-part2 failed to finish in 30 seconds.

  (i clicked install at try/install & thus copy of error didn't survive
  gui start)

  this was NOT a clean install (no format) BUT a 'install using existing 
partition'..
  ie. boot & select the SDA1 as / partition without format...
  install on that partition was a lubuntu noble install (with some music files 
& a few basic packages installs such as music player (audacious i think, or 
clementine)

  ---
  2024-04-08 - 15:43:34 [1]: void 
Calamares::ViewManager::onInstallationFailed(const QString&, const QString&)
  2024-04-08 - 15:43:34 [1]: ERROR: Installation failed: "External command 
failed to finish."
  2024-04-08 - 15:43:34 [6]: .. - message: "External command failed to 
finish."
  2024-04-08 - 15:43:34 [6]: .. - details: Command 
/usr/libexec/fixconkeys-part2 failed to finish in 30 seconds.
  There was no output from the command.
  2024-04-08 - 15:43:34 [6]: void 
Calamares::ViewManager::onInstallationFailed(const QString&, const QString&)
  ---

  install reported failure..

  On reboot I can login and everything looks okay (will be passing QA
  test), BUT /var/log/installer/mediainfo shows 0320.1 ISO which was
  numerous installs ago & not today's ISO  (last install failed,
  different issue but same type of install thus why numerous installs
  ago)

  viewing / shows many directories date/timestamped matching a new
  (re-)install, however some system directories do NOT reflect a re-
  install; ie. calamares reached an error & stopped the system
  booted correctly, but that's no doubt because it was a functional
  Lubuntu noble system & it's using setup possibly from prior install...

  
  ProblemType: BugDistroRelease: Ubuntu 24.04
  Package: calamares 3.3.5-0ubuntu3
  ProcVersionSignature: Ubuntu 6.8.0-22.22-generic 6.8.1
  Uname: Linux 6.8.0-22-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.28.0-0ubuntu1
  Architecture: amd64
  CasperMD5CheckResult: pass
  CasperVersion: 1.495build1
  CurrentDesktop: LXQt
  Date: Mon Apr  8 15:57:10 2024
  LiveMediaBuild: Lubuntu 24.04 LTS "Noble Numbat" - Daily amd64 (20240407.3)
  RelatedPackageVersions:
   calamares-settings-ubuntu-common 1:24.04.23
   calamares-settings-lubuntu   1:24.04.23
   xfsprogs 6.6.0-1ubuntu2
   btrfs-progs  6.6.3-1.1build2
  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-settings-ubuntu/+bug/2060429/+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 2060845] Re: New branding Kubuntu

2024-04-18 Thread Launchpad Bug Tracker
This bug was fixed in the package kubuntu-installer-prompt - 24.04.9

---
kubuntu-installer-prompt (24.04.9) noble; urgency=medium

  * Rebrand installer prompt. (LP: #2060845)
  * Add a dependency on a version of kubuntu-settings-desktop that has all
needed fonts.

 -- Aaron Rainbolt   Thu, 18 Apr 2024 13:52:15
-0400

** Changed in: kubuntu-installer-prompt (Ubuntu Noble)
   Status: New => Fix Released

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

Title:
  New branding Kubuntu

Status in calamares-settings-ubuntu package in Ubuntu:
  Fix Released
Status in kubuntu-installer-prompt package in Ubuntu:
  Fix Released
Status in kubuntu-settings package in Ubuntu:
  Fix Released
Status in kubuntu-wallpapers package in Ubuntu:
  Fix Released
Status in calamares-settings-ubuntu source package in Noble:
  Fix Released
Status in kubuntu-installer-prompt source package in Noble:
  Fix Released
Status in kubuntu-settings source package in Noble:
  Fix Released
Status in kubuntu-wallpapers source package in Noble:
  Fix Released

Bug description:
  Kubuntu has new branding for Noble. It was achieved by a design contest which 
just ended
  More info here: 
https://kubuntu.org/news/celebrating-creativity-announcing-the-winners-of-the-kubuntu-contests/

  With that said we now need to apply this to our defaults this
  affects kubuntu-wallpapers and kubuntu-settings and hopefully soon
  calamares-settings-kubuntu.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/calamares-settings-ubuntu/+bug/2060845/+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 2060845] Re: New branding Kubuntu

2024-04-18 Thread Launchpad Bug Tracker
This bug was fixed in the package kubuntu-settings - 1:24.04.9

---
kubuntu-settings (1:24.04.9) noble; urgency=medium

  * Move fonts-ibm-plex to Recommends.

 -- Scarlett Moore   Thu, 18 Apr 2024 05:33:35 -0700

** Changed in: kubuntu-settings (Ubuntu Noble)
   Status: New => Fix Released

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

Title:
  New branding Kubuntu

Status in calamares-settings-ubuntu package in Ubuntu:
  Fix Released
Status in kubuntu-installer-prompt package in Ubuntu:
  New
Status in kubuntu-settings package in Ubuntu:
  Fix Released
Status in kubuntu-wallpapers package in Ubuntu:
  Fix Released
Status in calamares-settings-ubuntu source package in Noble:
  Fix Released
Status in kubuntu-installer-prompt source package in Noble:
  New
Status in kubuntu-settings source package in Noble:
  Fix Released
Status in kubuntu-wallpapers source package in Noble:
  Fix Released

Bug description:
  Kubuntu has new branding for Noble. It was achieved by a design contest which 
just ended
  More info here: 
https://kubuntu.org/news/celebrating-creativity-announcing-the-winners-of-the-kubuntu-contests/

  With that said we now need to apply this to our defaults this
  affects kubuntu-wallpapers and kubuntu-settings and hopefully soon
  calamares-settings-kubuntu.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/calamares-settings-ubuntu/+bug/2060845/+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 2060845] Re: New branding Kubuntu

2024-04-17 Thread Launchpad Bug Tracker
This bug was fixed in the package kubuntu-wallpapers - 24.04.1

---
kubuntu-wallpapers (24.04.1) noble; urgency=medium

  * Add new light and dark wallpaper theme. (LP: #2060845)

 -- Scarlett Moore   Wed, 17 Apr 2024 01:24:12 -0700

** Changed in: kubuntu-wallpapers (Ubuntu Noble)
   Status: New => Fix Released

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

Title:
  New branding Kubuntu

Status in calamares-settings-ubuntu package in Ubuntu:
  Fix Released
Status in kubuntu-installer-prompt package in Ubuntu:
  New
Status in kubuntu-settings package in Ubuntu:
  New
Status in kubuntu-wallpapers package in Ubuntu:
  Fix Released
Status in calamares-settings-ubuntu source package in Noble:
  Fix Released
Status in kubuntu-installer-prompt source package in Noble:
  New
Status in kubuntu-settings source package in Noble:
  New
Status in kubuntu-wallpapers source package in Noble:
  Fix Released

Bug description:
  Kubuntu has new branding for Noble. It was achieved by a design contest which 
just ended
  More info here: 
https://kubuntu.org/news/celebrating-creativity-announcing-the-winners-of-the-kubuntu-contests/

  With that said we now need to apply this to our defaults this
  affects kubuntu-wallpapers and kubuntu-settings and hopefully soon
  calamares-settings-kubuntu.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/calamares-settings-ubuntu/+bug/2060845/+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 2060845] Re: New branding Kubuntu

2024-04-16 Thread Launchpad Bug Tracker
This bug was fixed in the package calamares-settings-ubuntu - 1:24.04.31

---
calamares-settings-ubuntu (1:24.04.31) noble; urgency=medium

  * Add Kubuntu branding. (LP: #2060845)

 -- Aaron Rainbolt   Tue, 16 Apr 2024 12:57:56
-0500

** Changed in: calamares-settings-ubuntu (Ubuntu Noble)
   Status: New => Fix Released

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

Title:
  New branding Kubuntu

Status in calamares-settings-ubuntu package in Ubuntu:
  Fix Released
Status in kubuntu-installer-prompt package in Ubuntu:
  New
Status in kubuntu-settings package in Ubuntu:
  New
Status in kubuntu-wallpapers package in Ubuntu:
  New
Status in calamares-settings-ubuntu source package in Noble:
  Fix Released
Status in kubuntu-installer-prompt source package in Noble:
  New
Status in kubuntu-settings source package in Noble:
  New
Status in kubuntu-wallpapers source package in Noble:
  New

Bug description:
  Kubuntu has new branding for Noble. It was achieved by a design contest which 
just ended
  More info here: 
https://kubuntu.org/news/celebrating-creativity-announcing-the-winners-of-the-kubuntu-contests/

  With that said we now need to apply this to our defaults this
  affects kubuntu-wallpapers and kubuntu-settings and hopefully soon
  calamares-settings-kubuntu.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/calamares-settings-ubuntu/+bug/2060845/+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 2061858] Re: Dummy audio device running on new installs

2024-04-16 Thread Launchpad Bug Tracker
This bug was fixed in the package ubuntustudio-installer - 1.18

---
ubuntustudio-installer (1.18) noble; urgency=medium

  * Fix dummy audio systemd service global enablement (LP: #2061858)

 -- Erich Eickmeyer   Tue, 16 Apr 2024 08:26:26
-0700

** Changed in: ubuntustudio-installer (Ubuntu)
   Status: Fix Committed => Fix Released

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

Title:
  Dummy audio device running on new installs

Status in ubuntustudio-installer package in Ubuntu:
  Fix Released

Bug description:
  It has been found on new installs that, despite attempt to disable via
  debian/postinst, that the dummy audio device is running. This is due
  to a systemd service being enabled globally for all users.

  A solution is being worked on to override this via debian/rules.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntustudio-installer/+bug/2061858/+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 2060898] Re: Trying to install gimp-help-en threatens to install wslu

2024-04-16 Thread Launchpad Bug Tracker
This bug was fixed in the package ubuntu-mate-meta - 1.296

---
ubuntu-mate-meta (1.296) noble; urgency=medium

  * Refreshed dependencies
  * Added caja-seahorse to desktop-recommends [armhf]
  * Added firefox to core-recommends [amd64 arm64 armhf], desktop-
recommends [amd64 arm64 armhf] (LP: #2060898)

 -- Martin Wimpress   Tue, 16 Apr 2024 14:47:27 +

** Changed in: ubuntu-mate-meta (Ubuntu Noble)
   Status: Fix Committed => Fix Released

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

Title:
  Trying to install gimp-help-en threatens to install wslu

Status in edubuntu-meta package in Ubuntu:
  Fix Released
Status in kubuntu-meta package in Ubuntu:
  Fix Released
Status in lubuntu-meta package in Ubuntu:
  Fix Released
Status in ubuntu-budgie-meta package in Ubuntu:
  Fix Released
Status in ubuntu-mate-meta package in Ubuntu:
  Fix Released
Status in ubuntu-meta package in Ubuntu:
  Invalid
Status in ubuntustudio-meta package in Ubuntu:
  Fix Released
Status in wslu package in Ubuntu:
  Invalid
Status in edubuntu-meta source package in Noble:
  Fix Released
Status in kubuntu-meta source package in Noble:
  Fix Released
Status in lubuntu-meta source package in Noble:
  Fix Released
Status in ubuntu-budgie-meta source package in Noble:
  Fix Released
Status in ubuntu-mate-meta source package in Noble:
  Fix Released
Status in ubuntu-meta source package in Noble:
  Invalid
Status in ubuntustudio-meta source package in Noble:
  Fix Released
Status in wslu source package in Noble:
  Invalid

Bug description:
  Filing this against ubuntu-meta since I believe this is a seed problem
  that potentially affects all variants of Ubuntu (flavors or
  otherwise).

  wslu is "a collection of utilities for the Windows 10 Linux Subsystem,
  such as for converting Linux paths to a Windows paths or creating
  Linux application shortcuts on the Windows 10 Desktop." Obviously this
  package should *never* be installed on a desktop or even on most VMs,
  but only within WSL instances. However...

  wslu provides the virtual package www-browser, as one of its features
  is to open links in Windows 10 using the default browser set there.
  This means that if a package depends or recommends www-browser, it may
  attempt to pull in one of several packages, wslu included. In the
  past, this hasn't been a problem because Firefox was present on all
  flavor images, and Firefox provides www-browser as well. However, now
  that Firefox is a Snap, it is possible for Firefox to be installed
  without the firefox transitional apt package being installed. (This is
  the case in a default installation of Kubuntu Noble Beta.) As it turns
  out, Kubuntu Noble Beta ships with *no* packages that provide www-
  browser, meaning that any package that depends on it will have to
  install a new browser.

  Due to some stroke of misfortune, apt is picking wslu out of all
  packages as the package for this use case. Installing gimp-help-en
  will also install www-browser, which results in wslu becoming
  installed.

  wslu causes quite a few problems when installed on a desktop system -
  among them, the syslog is spammed with errors due to the system not in
  fact being a WSL VM, audio breaks in weird ways, and application
  launchers sometimes fail. Why this happens is unclear, but the issues
  appear to resolve once wslu is removed from the system. It is
  therefore probably a good idea to avoid wslu becoming installed on
  accident in this way.

  Probably the best way to resolve this is to ensure that some package
  that provides www-browser is available on every Ubuntu image. This
  could be done via seeding or by adding a package to ubuntu-minimal.
  Alternatively, wslu could be set to no longer provide www-browser,
  though it's unclear if that would break its functionality.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/edubuntu-meta/+bug/2060898/+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 2061681] Re: On kubuntu 24.04, after_bootloader_context claims to fail to remove installaton icon

2024-04-16 Thread Launchpad Bug Tracker
This bug was fixed in the package calamares-settings-ubuntu - 1:24.04.29

---
calamares-settings-ubuntu (1:24.04.29) noble; urgency=medium

  [ Aaron Rainbolt ]
  * Change Kubuntu's Calamares sidebar color.

  [ Walter Lapchynski ]
  * Remove after_bootloader contextual process. (LP: #2061681)

 -- Walter Lapchynski   Tue, 16 Apr 2024 01:10:47 +

** Changed in: calamares-settings-ubuntu (Ubuntu)
   Status: Fix Committed => Fix Released

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

Title:
  On kubuntu 24.04, after_bootloader_context claims to fail to remove
  installaton icon

Status in calamares-settings-ubuntu package in Ubuntu:
  Fix Released

Bug description:
  On Kubuntu 24.04 daily (up to 24.04.2)
  kubuntu/modules/after_bootloader_context.conf claims to fail to remove
  installation .desktop file:

  2024-04-11 - 23:38:46 [6]: Starting job "Performing contextual processes' 
job…" ( 32 / 41 )
  2024-04-11 - 23:38:46 [6]: .. Running ("/bin/sh", "-c", "rm 
//home/user/Desktop/kubuntu-calamares.desktop")
  2024-04-11 - 23:38:46 [6]: .. Target cmd: ("/bin/sh", "-c", "rm 
//home/user/Desktop/kubuntu-calamares.desktop") Exit code: 1 output:
  rm: cannot remove '//home/user/Desktop/kubuntu-calamares.desktop': No such 
file or directory
  2024-04-11 - 23:38:46 [6]: Calamares::JobResult Calamares::CommandList::run()
  2024-04-11 - 23:38:46 [6]: Error code 1 ignored by CommandList 
configuration.

  It seems to try to remove it from live system instead of chroot.
  But, since I don't see the icon on the target system I believe this module is 
redundant and can be removed.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/calamares-settings-ubuntu/+bug/2061681/+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 2045580] Re: Improve third-party app installation

2024-04-16 Thread Launchpad Bug Tracker
This bug was fixed in the package lubuntu-default-settings - 24.04.9

---
lubuntu-default-settings (24.04.9) noble; urgency=medium

  * Create lubuntu-snap-installation-monitor, which tells the user if snaps
are still being pre-seeded in the background. Mostly used in the case of
preseeding a lot of snaps, or preseeding snaps on a slower machine
(LP: #2045580, LP: #2061318).

 -- Simon Quigley   Sun, 14 Apr 2024 15:49:12 -0500

** Changed in: lubuntu-default-settings (Ubuntu)
   Status: Confirmed => Fix Released

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

Title:
  Improve third-party app installation

Status in calamares-settings-ubuntu package in Ubuntu:
  Fix Released
Status in lubuntu-default-settings package in Ubuntu:
  Fix Released

Bug description:
  In the Lubuntu Noble ISO, there is the option to install third-party
  applications. This tracks the following:

   - Snaps on the backend should auto-resolve dependencies... somehow. That way 
we don't have bitrot come LTS time.
   - When selecting the Minimal install, the checkboxes should disappear 
entirely.
   - When selecting the Full install, it should automatically check all four of 
those boxes, even if it just hides them/displays a read-only/disabled copy. 
Normal should be the only option in which you can freely manipulate the 
checkboxes.
   - We may want to move this from QML to a dedicated UI file to fit with 
theming better.
   - We need some kind of translations, even if we can somehow convince 
upstream Calamares to adopt our module, to get that translation support.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/calamares-settings-ubuntu/+bug/2045580/+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 2061588] Re: Ubuntu Studio missing print-manager

2024-04-15 Thread Launchpad Bug Tracker
This bug was fixed in the package ubuntustudio-meta - 24.04.21

---
ubuntustudio-meta (24.04.21) noble; urgency=medium

  * Refreshed dependencies
  * Added print-manager to desktop-recommends (LP: #2061588)

 -- Erich Eickmeyer   Mon, 15 Apr 2024 09:33:04
-0700

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

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

Title:
  Ubuntu Studio missing print-manager

Status in ubuntustudio-meta package in Ubuntu:
  Fix Released

Bug description:
  It was discovered during an update that Ubuntu Studio wants to remove
  print-manager as needed in Plasma and as a recommends by Kubuntu.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntustudio-meta/+bug/2061588/+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 2061150] Re: Selecting "full installation" crashes installation with "external command errors"

2024-04-14 Thread Launchpad Bug Tracker
This bug was fixed in the package calamares-settings-ubuntu - 1:24.04.28

---
calamares-settings-ubuntu (1:24.04.28) noble; urgency=medium

  * Run apt updates before installing packages. (LP: #2061150)

 -- Walter Lapchynski   Sat, 13 Apr 2024 00:44:32 +

** Changed in: calamares-settings-ubuntu (Ubuntu)
   Status: In Progress => Fix Released

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

Title:
  Selecting "full installation" crashes installation with "external
  command errors"

Status in calamares-settings-ubuntu package in Ubuntu:
  Fix Released

Bug description:
  Installing Kubuntu Noble Desktop (BETA) dated 20240412

  selected "full installation" and just before the install completed
  received the error: Installation failed  (unable to locate package
  virt-manager)

  see attached screenshots

  tried to run ubuntu-bug calamares-settings-kubuntu but this also
  failed

  also attached are the crash logs

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/calamares-settings-ubuntu/+bug/2061150/+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 2060898] Re: Trying to install gimp-help-en threatens to install wslu

2024-04-13 Thread Launchpad Bug Tracker
This bug was fixed in the package ubuntustudio-meta - 24.04.19

---
ubuntustudio-meta (24.04.19) noble; urgency=medium

  * Refreshed dependencies
  * Added firefox to desktop-recommends [amd64 arm64 armhf] (LP: #2060898)
  * Added krita to graphics-recommends [armhf]
  * Added libimath-3-1-29t64 to graphics-recommends

 -- Erich Eickmeyer   Thu, 11 Apr 2024 14:33:35
-0700

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

Title:
  Trying to install gimp-help-en threatens to install wslu

Status in edubuntu-meta package in Ubuntu:
  Fix Released
Status in kubuntu-meta package in Ubuntu:
  Fix Released
Status in lubuntu-meta package in Ubuntu:
  Fix Released
Status in ubuntu-budgie-meta package in Ubuntu:
  Fix Released
Status in ubuntu-mate-meta package in Ubuntu:
  Triaged
Status in ubuntu-meta package in Ubuntu:
  Invalid
Status in ubuntustudio-meta package in Ubuntu:
  Fix Released
Status in wslu package in Ubuntu:
  Invalid
Status in edubuntu-meta source package in Noble:
  Fix Released
Status in kubuntu-meta source package in Noble:
  Fix Released
Status in lubuntu-meta source package in Noble:
  Fix Released
Status in ubuntu-budgie-meta source package in Noble:
  Fix Released
Status in ubuntu-mate-meta source package in Noble:
  Triaged
Status in ubuntu-meta source package in Noble:
  Invalid
Status in ubuntustudio-meta source package in Noble:
  Fix Released
Status in wslu source package in Noble:
  Invalid

Bug description:
  Filing this against ubuntu-meta since I believe this is a seed problem
  that potentially affects all variants of Ubuntu (flavors or
  otherwise).

  wslu is "a collection of utilities for the Windows 10 Linux Subsystem,
  such as for converting Linux paths to a Windows paths or creating
  Linux application shortcuts on the Windows 10 Desktop." Obviously this
  package should *never* be installed on a desktop or even on most VMs,
  but only within WSL instances. However...

  wslu provides the virtual package www-browser, as one of its features
  is to open links in Windows 10 using the default browser set there.
  This means that if a package depends or recommends www-browser, it may
  attempt to pull in one of several packages, wslu included. In the
  past, this hasn't been a problem because Firefox was present on all
  flavor images, and Firefox provides www-browser as well. However, now
  that Firefox is a Snap, it is possible for Firefox to be installed
  without the firefox transitional apt package being installed. (This is
  the case in a default installation of Kubuntu Noble Beta.) As it turns
  out, Kubuntu Noble Beta ships with *no* packages that provide www-
  browser, meaning that any package that depends on it will have to
  install a new browser.

  Due to some stroke of misfortune, apt is picking wslu out of all
  packages as the package for this use case. Installing gimp-help-en
  will also install www-browser, which results in wslu becoming
  installed.

  wslu causes quite a few problems when installed on a desktop system -
  among them, the syslog is spammed with errors due to the system not in
  fact being a WSL VM, audio breaks in weird ways, and application
  launchers sometimes fail. Why this happens is unclear, but the issues
  appear to resolve once wslu is removed from the system. It is
  therefore probably a good idea to avoid wslu becoming installed on
  accident in this way.

  Probably the best way to resolve this is to ensure that some package
  that provides www-browser is available on every Ubuntu image. This
  could be done via seeding or by adding a package to ubuntu-minimal.
  Alternatively, wslu could be set to no longer provide www-browser,
  though it's unclear if that would break its functionality.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/edubuntu-meta/+bug/2060898/+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 2060898] Re: Trying to install gimp-help-en threatens to install wslu

2024-04-13 Thread Launchpad Bug Tracker
This bug was fixed in the package ubuntu-budgie-meta - 0.126

---
ubuntu-budgie-meta (0.126) noble; urgency=medium

  * Refreshed dependencies
  * Added firefox to desktop-minimal-recommends [amd64 arm64 armhf],
desktop-raspi-recommends [amd64 arm64 armhf], desktop-recommends
[amd64 arm64 armhf] (LP: #2060898)
  * Added printer-driver-c2esp to desktop-minimal-recommends [amd64],
desktop-raspi-recommends [amd64], desktop-recommends [amd64]

 -- David Mohammed   Thu, 11 Apr 2024 20:45:05
+0100

** Changed in: ubuntustudio-meta (Ubuntu Noble)
   Status: Fix Committed => Fix Released

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

Title:
  Trying to install gimp-help-en threatens to install wslu

Status in edubuntu-meta package in Ubuntu:
  Fix Released
Status in kubuntu-meta package in Ubuntu:
  Fix Released
Status in lubuntu-meta package in Ubuntu:
  Fix Released
Status in ubuntu-budgie-meta package in Ubuntu:
  Fix Released
Status in ubuntu-mate-meta package in Ubuntu:
  Triaged
Status in ubuntu-meta package in Ubuntu:
  Invalid
Status in ubuntustudio-meta package in Ubuntu:
  Fix Released
Status in wslu package in Ubuntu:
  Invalid
Status in edubuntu-meta source package in Noble:
  Fix Released
Status in kubuntu-meta source package in Noble:
  Fix Released
Status in lubuntu-meta source package in Noble:
  Fix Released
Status in ubuntu-budgie-meta source package in Noble:
  Fix Released
Status in ubuntu-mate-meta source package in Noble:
  Triaged
Status in ubuntu-meta source package in Noble:
  Invalid
Status in ubuntustudio-meta source package in Noble:
  Fix Released
Status in wslu source package in Noble:
  Invalid

Bug description:
  Filing this against ubuntu-meta since I believe this is a seed problem
  that potentially affects all variants of Ubuntu (flavors or
  otherwise).

  wslu is "a collection of utilities for the Windows 10 Linux Subsystem,
  such as for converting Linux paths to a Windows paths or creating
  Linux application shortcuts on the Windows 10 Desktop." Obviously this
  package should *never* be installed on a desktop or even on most VMs,
  but only within WSL instances. However...

  wslu provides the virtual package www-browser, as one of its features
  is to open links in Windows 10 using the default browser set there.
  This means that if a package depends or recommends www-browser, it may
  attempt to pull in one of several packages, wslu included. In the
  past, this hasn't been a problem because Firefox was present on all
  flavor images, and Firefox provides www-browser as well. However, now
  that Firefox is a Snap, it is possible for Firefox to be installed
  without the firefox transitional apt package being installed. (This is
  the case in a default installation of Kubuntu Noble Beta.) As it turns
  out, Kubuntu Noble Beta ships with *no* packages that provide www-
  browser, meaning that any package that depends on it will have to
  install a new browser.

  Due to some stroke of misfortune, apt is picking wslu out of all
  packages as the package for this use case. Installing gimp-help-en
  will also install www-browser, which results in wslu becoming
  installed.

  wslu causes quite a few problems when installed on a desktop system -
  among them, the syslog is spammed with errors due to the system not in
  fact being a WSL VM, audio breaks in weird ways, and application
  launchers sometimes fail. Why this happens is unclear, but the issues
  appear to resolve once wslu is removed from the system. It is
  therefore probably a good idea to avoid wslu becoming installed on
  accident in this way.

  Probably the best way to resolve this is to ensure that some package
  that provides www-browser is available on every Ubuntu image. This
  could be done via seeding or by adding a package to ubuntu-minimal.
  Alternatively, wslu could be set to no longer provide www-browser,
  though it's unclear if that would break its functionality.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/edubuntu-meta/+bug/2060898/+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 2060898] Re: Trying to install gimp-help-en threatens to install wslu

2024-04-13 Thread Launchpad Bug Tracker
This bug was fixed in the package lubuntu-meta - 24.04.9

---
lubuntu-meta (24.04.9) noble; urgency=medium

  * Refreshed dependencies
  * Added firefox to desktop-recommends [amd64 arm64 armhf] (LP: #2060898)

 -- Walter Lapchynski   Thu, 11 Apr 2024 21:27:39 +

** Changed in: edubuntu-meta (Ubuntu Noble)
   Status: Fix Committed => Fix Released

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

Title:
  Trying to install gimp-help-en threatens to install wslu

Status in edubuntu-meta package in Ubuntu:
  Fix Released
Status in kubuntu-meta package in Ubuntu:
  Fix Released
Status in lubuntu-meta package in Ubuntu:
  Fix Released
Status in ubuntu-budgie-meta package in Ubuntu:
  Fix Released
Status in ubuntu-mate-meta package in Ubuntu:
  Triaged
Status in ubuntu-meta package in Ubuntu:
  Invalid
Status in ubuntustudio-meta package in Ubuntu:
  Fix Released
Status in wslu package in Ubuntu:
  Invalid
Status in edubuntu-meta source package in Noble:
  Fix Released
Status in kubuntu-meta source package in Noble:
  Fix Released
Status in lubuntu-meta source package in Noble:
  Fix Released
Status in ubuntu-budgie-meta source package in Noble:
  Fix Released
Status in ubuntu-mate-meta source package in Noble:
  Triaged
Status in ubuntu-meta source package in Noble:
  Invalid
Status in ubuntustudio-meta source package in Noble:
  Fix Released
Status in wslu source package in Noble:
  Invalid

Bug description:
  Filing this against ubuntu-meta since I believe this is a seed problem
  that potentially affects all variants of Ubuntu (flavors or
  otherwise).

  wslu is "a collection of utilities for the Windows 10 Linux Subsystem,
  such as for converting Linux paths to a Windows paths or creating
  Linux application shortcuts on the Windows 10 Desktop." Obviously this
  package should *never* be installed on a desktop or even on most VMs,
  but only within WSL instances. However...

  wslu provides the virtual package www-browser, as one of its features
  is to open links in Windows 10 using the default browser set there.
  This means that if a package depends or recommends www-browser, it may
  attempt to pull in one of several packages, wslu included. In the
  past, this hasn't been a problem because Firefox was present on all
  flavor images, and Firefox provides www-browser as well. However, now
  that Firefox is a Snap, it is possible for Firefox to be installed
  without the firefox transitional apt package being installed. (This is
  the case in a default installation of Kubuntu Noble Beta.) As it turns
  out, Kubuntu Noble Beta ships with *no* packages that provide www-
  browser, meaning that any package that depends on it will have to
  install a new browser.

  Due to some stroke of misfortune, apt is picking wslu out of all
  packages as the package for this use case. Installing gimp-help-en
  will also install www-browser, which results in wslu becoming
  installed.

  wslu causes quite a few problems when installed on a desktop system -
  among them, the syslog is spammed with errors due to the system not in
  fact being a WSL VM, audio breaks in weird ways, and application
  launchers sometimes fail. Why this happens is unclear, but the issues
  appear to resolve once wslu is removed from the system. It is
  therefore probably a good idea to avoid wslu becoming installed on
  accident in this way.

  Probably the best way to resolve this is to ensure that some package
  that provides www-browser is available on every Ubuntu image. This
  could be done via seeding or by adding a package to ubuntu-minimal.
  Alternatively, wslu could be set to no longer provide www-browser,
  though it's unclear if that would break its functionality.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/edubuntu-meta/+bug/2060898/+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 2060898] Re: Trying to install gimp-help-en threatens to install wslu

2024-04-13 Thread Launchpad Bug Tracker
This bug was fixed in the package edubuntu-meta - 24.04.13

---
edubuntu-meta (24.04.13) noble; urgency=medium

  * Refreshed dependencies
  * Added firefox to desktop-gnome-minimal-recommends [amd64 arm64
armhf], desktop-gnome-raspi-recommends [amd64 arm64 armhf], desktop-
gnome-recommends [amd64 arm64 armhf] (LP: #2060898)
  * Removed gbrainy from ubuntu-edu-secondary-recommends [armhf], ubuntu-
edu-tertiary-recommends [armhf]

 -- Erich Eickmeyer   Thu, 11 Apr 2024 15:01:48
-0700

** Changed in: ubuntu-budgie-meta (Ubuntu Noble)
   Status: Fix Committed => Fix Released

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

Title:
  Trying to install gimp-help-en threatens to install wslu

Status in edubuntu-meta package in Ubuntu:
  Fix Released
Status in kubuntu-meta package in Ubuntu:
  Fix Released
Status in lubuntu-meta package in Ubuntu:
  Fix Released
Status in ubuntu-budgie-meta package in Ubuntu:
  Fix Released
Status in ubuntu-mate-meta package in Ubuntu:
  Triaged
Status in ubuntu-meta package in Ubuntu:
  Invalid
Status in ubuntustudio-meta package in Ubuntu:
  Fix Released
Status in wslu package in Ubuntu:
  Invalid
Status in edubuntu-meta source package in Noble:
  Fix Released
Status in kubuntu-meta source package in Noble:
  Fix Released
Status in lubuntu-meta source package in Noble:
  Fix Released
Status in ubuntu-budgie-meta source package in Noble:
  Fix Released
Status in ubuntu-mate-meta source package in Noble:
  Triaged
Status in ubuntu-meta source package in Noble:
  Invalid
Status in ubuntustudio-meta source package in Noble:
  Fix Released
Status in wslu source package in Noble:
  Invalid

Bug description:
  Filing this against ubuntu-meta since I believe this is a seed problem
  that potentially affects all variants of Ubuntu (flavors or
  otherwise).

  wslu is "a collection of utilities for the Windows 10 Linux Subsystem,
  such as for converting Linux paths to a Windows paths or creating
  Linux application shortcuts on the Windows 10 Desktop." Obviously this
  package should *never* be installed on a desktop or even on most VMs,
  but only within WSL instances. However...

  wslu provides the virtual package www-browser, as one of its features
  is to open links in Windows 10 using the default browser set there.
  This means that if a package depends or recommends www-browser, it may
  attempt to pull in one of several packages, wslu included. In the
  past, this hasn't been a problem because Firefox was present on all
  flavor images, and Firefox provides www-browser as well. However, now
  that Firefox is a Snap, it is possible for Firefox to be installed
  without the firefox transitional apt package being installed. (This is
  the case in a default installation of Kubuntu Noble Beta.) As it turns
  out, Kubuntu Noble Beta ships with *no* packages that provide www-
  browser, meaning that any package that depends on it will have to
  install a new browser.

  Due to some stroke of misfortune, apt is picking wslu out of all
  packages as the package for this use case. Installing gimp-help-en
  will also install www-browser, which results in wslu becoming
  installed.

  wslu causes quite a few problems when installed on a desktop system -
  among them, the syslog is spammed with errors due to the system not in
  fact being a WSL VM, audio breaks in weird ways, and application
  launchers sometimes fail. Why this happens is unclear, but the issues
  appear to resolve once wslu is removed from the system. It is
  therefore probably a good idea to avoid wslu becoming installed on
  accident in this way.

  Probably the best way to resolve this is to ensure that some package
  that provides www-browser is available on every Ubuntu image. This
  could be done via seeding or by adding a package to ubuntu-minimal.
  Alternatively, wslu could be set to no longer provide www-browser,
  though it's unclear if that would break its functionality.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/edubuntu-meta/+bug/2060898/+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 2060898] Re: Trying to install gimp-help-en threatens to install wslu

2024-04-13 Thread Launchpad Bug Tracker
This bug was fixed in the package kubuntu-meta - 1.450

---
kubuntu-meta (1.450) noble; urgency=medium

  * Refreshed dependencies
  * Added printer-driver-c2esp to desktop-recommends [amd64]
  * Removed firefox from desktop-recommends [amd64]
  * Refreshed dependencies
  * Added firefox to desktop-recommends [amd64 arm64 armhf]
Ref: (LP: #2060898)

 -- Scarlett Moore   Fri, 12 Apr 2024 01:21:12 -0700

** Changed in: kubuntu-meta (Ubuntu Noble)
   Status: Fix Committed => Fix Released

** Changed in: lubuntu-meta (Ubuntu Noble)
   Status: Fix Committed => Fix Released

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

Title:
  Trying to install gimp-help-en threatens to install wslu

Status in edubuntu-meta package in Ubuntu:
  Fix Released
Status in kubuntu-meta package in Ubuntu:
  Fix Released
Status in lubuntu-meta package in Ubuntu:
  Fix Released
Status in ubuntu-budgie-meta package in Ubuntu:
  Fix Released
Status in ubuntu-mate-meta package in Ubuntu:
  Triaged
Status in ubuntu-meta package in Ubuntu:
  Invalid
Status in ubuntustudio-meta package in Ubuntu:
  Fix Released
Status in wslu package in Ubuntu:
  Invalid
Status in edubuntu-meta source package in Noble:
  Fix Released
Status in kubuntu-meta source package in Noble:
  Fix Released
Status in lubuntu-meta source package in Noble:
  Fix Released
Status in ubuntu-budgie-meta source package in Noble:
  Fix Released
Status in ubuntu-mate-meta source package in Noble:
  Triaged
Status in ubuntu-meta source package in Noble:
  Invalid
Status in ubuntustudio-meta source package in Noble:
  Fix Released
Status in wslu source package in Noble:
  Invalid

Bug description:
  Filing this against ubuntu-meta since I believe this is a seed problem
  that potentially affects all variants of Ubuntu (flavors or
  otherwise).

  wslu is "a collection of utilities for the Windows 10 Linux Subsystem,
  such as for converting Linux paths to a Windows paths or creating
  Linux application shortcuts on the Windows 10 Desktop." Obviously this
  package should *never* be installed on a desktop or even on most VMs,
  but only within WSL instances. However...

  wslu provides the virtual package www-browser, as one of its features
  is to open links in Windows 10 using the default browser set there.
  This means that if a package depends or recommends www-browser, it may
  attempt to pull in one of several packages, wslu included. In the
  past, this hasn't been a problem because Firefox was present on all
  flavor images, and Firefox provides www-browser as well. However, now
  that Firefox is a Snap, it is possible for Firefox to be installed
  without the firefox transitional apt package being installed. (This is
  the case in a default installation of Kubuntu Noble Beta.) As it turns
  out, Kubuntu Noble Beta ships with *no* packages that provide www-
  browser, meaning that any package that depends on it will have to
  install a new browser.

  Due to some stroke of misfortune, apt is picking wslu out of all
  packages as the package for this use case. Installing gimp-help-en
  will also install www-browser, which results in wslu becoming
  installed.

  wslu causes quite a few problems when installed on a desktop system -
  among them, the syslog is spammed with errors due to the system not in
  fact being a WSL VM, audio breaks in weird ways, and application
  launchers sometimes fail. Why this happens is unclear, but the issues
  appear to resolve once wslu is removed from the system. It is
  therefore probably a good idea to avoid wslu becoming installed on
  accident in this way.

  Probably the best way to resolve this is to ensure that some package
  that provides www-browser is available on every Ubuntu image. This
  could be done via seeding or by adding a package to ubuntu-minimal.
  Alternatively, wslu could be set to no longer provide www-browser,
  though it's unclear if that would break its functionality.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/edubuntu-meta/+bug/2060898/+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 2061150] [NEW] Selecting "full installation" crashes installation with "external command errors"

2024-04-12 Thread Launchpad Bug Tracker
You have been subscribed to a public bug:

Installing Kubuntu Noble Desktop (BETA) dated 20240412

selected "full installation" and just before the install completed
received the error: Installation failed  (unable to locate package virt-
manager)

see attached screenshots

tried to run ubuntu-bug calamares-settings-kubuntu but this also failed

also attached are the crash logs

** Affects: calamares-settings-ubuntu (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: iso-testing
-- 
Selecting "full installation" crashes installation with "external command 
errors"
https://bugs.launchpad.net/bugs/2061150
You received this bug notification because you are a member of Ubuntu Studio 
Bugs, which is subscribed to calamares-settings-ubuntu in Ubuntu.

-- 
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 2061100] [NEW] Kubuntu 24.04 using Lubuntu slideshow

2024-04-12 Thread Launchpad Bug Tracker
You have been subscribed to a public bug:

Kubuntu 24.04 using Lubuntu slideshow.
Kubuntu image 20240412.
Most likely due to Kubuntu's slideshow not completed for testing daily version.
QA Testing using virtualbox 7.0 Full disk install.
Install-'Passed' Testing with no problems.
This bug report should be considered "Low Priority"

ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: ubiquity (not installed)
ProcVersionSignature: Ubuntu 6.8.0-22.22-generic 6.8.1
Uname: Linux 6.8.0-22-generic x86_64
ApportVersion: 2.28.0-0ubuntu1
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: KDE
Date: Fri Apr 12 03:56:42 2024
InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz --- quiet splash
InstallationDate: Installed on 2024-04-12 (0 days ago)
InstallationMedia: Kubuntu 24.04 LTS "Noble Numbat" - Beta amd64 (20240412)
SourcePackage: ubiquity
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: calamares (Ubuntu)
 Importance: Undecided
 Status: Confirmed


** Tags: amd64 apport-bug iso-testing noble
-- 
Kubuntu 24.04 using Lubuntu slideshow
https://bugs.launchpad.net/bugs/2061100
You received this bug notification because you are a member of Ubuntu Studio 
Bugs, which is subscribed to calamares in Ubuntu.

-- 
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 2060879] Re: pkgselect module is broken in Kubuntu and Ubuntu Unity

2024-04-10 Thread Launchpad Bug Tracker
This bug was fixed in the package calamares-settings-ubuntu - 1:24.04.26

---
calamares-settings-ubuntu (1:24.04.26) noble; urgency=medium

  * Make the pkgselect module actually work on Kubuntu and Ubuntu Unity.
(LP: #2060879)

 -- Aaron Rainbolt   Wed, 10 Apr 2024 16:16:21
-0500

** Changed in: calamares-settings-ubuntu (Ubuntu Noble)
   Status: Fix Committed => Fix Released

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

Title:
  pkgselect module is broken in Kubuntu and Ubuntu Unity

Status in calamares-settings-ubuntu package in Ubuntu:
  Fix Released
Status in calamares-settings-ubuntu source package in Noble:
  Fix Released

Bug description:
  Due to an oversight in development, Kubuntu was left without any
  functional configuration for the "Customize" screen of the installer
  (the pkgselect module), while Ubuntu Unity was left with pkgselect
  misconfigured. This causes all package customization features to do
  nothing in Kubuntu, and will likely result in similar (or worse)
  misbehavior in Ubuntu Unity.

  The fix is to copy Lubuntu's pkgselect configuration to Kubuntu and
  Ubuntu Unity, and then customize the "packages to purge for a minimal
  install" list for both.

  In my opinion this should be fixed prior to beta release, as the
  pkgselect module is *glaringly* obvious in the installers for Kubuntu
  and Ubuntu Unity. If it does nothing (or causes the installer to
  crash), the user experience will be very degraded.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/calamares-settings-ubuntu/+bug/2060879/+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 2056061] Re: FFe: Calamares customize menu

2024-04-04 Thread Launchpad Bug Tracker
This bug was fixed in the package calamares-settings-ubuntu - 1:24.04.23

---
calamares-settings-ubuntu (1:24.04.23) noble; urgency=medium

  * Set GOCACHE to stay within the build directory

 -- Simon Chopin   Wed, 03 Apr 2024 19:40:50 +0200

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

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

Title:
  FFe: Calamares customize menu

Status in calamares-settings-ubuntu package in Ubuntu:
  Fix Released

Bug description:
  Our pkgselect UI has some issues and will need an overhaul, which we intent 
to do. This IS a feature goal and thus need the FFe. If you need anymore 
information please feel free to ask.
  Thanks for your consideration.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/calamares-settings-ubuntu/+bug/2056061/+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 2058813] Re: proposed-migration for gimp-plugin-registry 9.20200928build2

2024-04-03 Thread Launchpad Bug Tracker
** Merge proposal linked:
   
https://code.launchpad.net/~vpa1977/ubuntu/+source/gimp-plugin-registry/+git/gimp-plugin-registry/+merge/463634

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

Title:
  proposed-migration for gimp-plugin-registry 9.20200928build2

Status in gimp-plugin-registry package in Ubuntu:
  New
Status in gimp-plugin-registry package in Debian:
  Unknown

Bug description:
  gimp-plugin-registry 9.20200928build2 is stuck in -proposed.  It fails
  to build on armhf due to implicit function declarations.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gimp-plugin-registry/+bug/2058813/+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 2058799] Re: a2jmidid doesn't handle midi interfaces with two or more identical port names correctly and fails to expose them

2024-03-28 Thread Launchpad Bug Tracker
This bug was fixed in the package a2jmidid - 9-3ubuntu1

---
a2jmidid (9-3ubuntu1) noble; urgency=medium

  * Patch: add port id to port name to avoid collision (LP: #2058799)
- (Closes: #1067662)

 -- Erich Eickmeyer   Mon, 25 Mar 2024 09:38:40
-0700

** Changed in: a2jmidid (Ubuntu Noble)
   Status: Fix Committed => Fix Released

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

Title:
  a2jmidid doesn't handle midi interfaces with two or more identical
  port names correctly and fails to expose them

Status in a2jmidid package in Ubuntu:
  Fix Released
Status in a2jmidid source package in Jammy:
  In Progress
Status in a2jmidid source package in Mantic:
  In Progress
Status in a2jmidid source package in Noble:
  Fix Released

Bug description:
  This issue has been solved in 2019 in a2jmidid:
  https://github.com/jackaudio/a2jmidid/pull/5

  It's been described in various places:
  https://linuxmusicians.com/viewtopic.php?t=24822

  Could you please include this in the packages? It basically boils down to 
this four letter change in port.c:
  119c119
  <   "%s [%d] (%s): [%d] %s",
  ---
  >   "%s [%d] (%s): %s",

  
  Kind regards,

  Reinaert

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/a2jmidid/+bug/2058799/+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 2055799] Re: FFe: Switch Ubuntu Unity to using Calamares

2024-03-28 Thread Launchpad Bug Tracker
This bug was fixed in the package calamares-settings-ubuntu - 1:24.04.20

---
calamares-settings-ubuntu (1:24.04.20) noble; urgency=medium

  * Fix LUKS passphrase unlocker for non-US keyboard layouts.
  * Disable pkgselect module on Kubuntu, it's not ready for use and wasn't
intentionally enabled.

 -- Aaron Rainbolt   Thu, 21 Mar 2024 13:32:53
-0500

** Changed in: calamares-settings-ubuntu (Ubuntu)
   Status: Triaged => Fix Released

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

Title:
  FFe: Switch Ubuntu Unity to using Calamares

Status in calamares-settings-ubuntu package in Ubuntu:
  Fix Released

Bug description:
  Filing this under calamares-settings-ubuntu as this is where the
  majority of the code will be.

  Ubuntu Unity intends on moving away from the Ubiquity installer this
  cycle. As discussed with team lead Rudra Saraswat on Matrix, the goal
  is to move to the Calamares installer currently used by Lubuntu and
  Kubuntu. (The Ubuntu Desktop Installer was considered but does not
  appear to be Ubuntu Unity's intended installer at the moment.)

  I believe this is relatively safe change to make, as I did the
  majority of the work to port Calamares to Kubuntu, and it was able to
  be ported to using Calamares in a couple of days. The remaining work
  was mainly due to development of brand new features (almost all of
  which will simply be ported to Ubuntu Unity rather than being created
  from scratch). Furthermore, a thorough testing checklist exists for
  flavors that use Calamares, helping to catch both flavor-specific and
  Ubuntu-wide bugs in Calamares. This checklist is used regularly by
  Lubuntu for every release, and would easily be applicable to Ubuntu
  Unity as well.

  Upon completion, all existing Ubuntu Calamares features will be
  enabled for Ubuntu Unity, including OEM installation mode, a try or
  install screen with network and localization selection menus, and full
  disk encryption with unencrypted /boot. This will require the
  following packages to be modified:

  * calamares-settings-ubuntu: Add config for Ubuntu Unity
  * casper: Automatically log into an ubuntu-unity-live-environment X session 
to start the installer prompt screen, provide the installation icon on Ubuntu 
Unity's desktop
  * debian-cd: Remove Ubiquity preseed, adjust GRUB menu entries to only 
provide a "Try or Install Ubuntu Unity" entry, as the OEM installation mode 
will be triggered from within the live environment rather than from the GRUB 
menu

  NO LONGER APPLICABLE:

  * ubuntu-unity-installer-prompt (which will be a NEW package): Port
  installer prompt screen to Ubuntu Unity

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/calamares-settings-ubuntu/+bug/2055799/+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 2057704] Re: jackd2 FTBFS due to waflib incompatible with Python 3.12

2024-03-28 Thread Launchpad Bug Tracker
This bug was fixed in the package jackd2 - 1.9.21~dfsg-3ubuntu1

---
jackd2 (1.9.21~dfsg-3ubuntu1) noble; urgency=medium

  * d/p/1002-Update-to-waf-2.0.26.patch: apply an upstream patch to fix
Python 3.12 compatibility issues with the waf build system.
(LP: #2057704).

 -- Zixing Liu   Tue, 12 Mar 2024 14:45:25
-0600

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

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

Title:
  jackd2 FTBFS due to waflib incompatible with Python 3.12

Status in jackd2 package in Ubuntu:
  Fix Released

Bug description:
  jackd2 is now unbuildable after Python 3.12 due to a very outdated WAF
  build system inside.

  The upstream has already fixed the issue in a recent commit, we need
  to introduce this as a patch.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/jackd2/+bug/2057704/+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 2058375] [NEW] Kubuntu noble Try/Install main screen

2024-03-19 Thread Launchpad Bug Tracker
You have been subscribed to a public bug:

Launching kubuntu's daily image, in the main screen I select "Español de
España" as language, then "try kubuntu"

When desktop is loaded, translations seem ok but keyboard "es" is not
loaded

(Ubuntu Noble Numbat (development branch), Release 24.04)

** Affects: calamares (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: kubuntu noble
-- 
Kubuntu noble Try/Install main screen
https://bugs.launchpad.net/bugs/2058375
You received this bug notification because you are a member of Ubuntu Studio 
Bugs, which is subscribed to calamares in Ubuntu.

-- 
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 2058367] [NEW] Kubuntu noble daily installer broken

2024-03-19 Thread Launchpad Bug Tracker
You have been subscribed to a public bug:

For more than a month it has been impossible to install the kubuntu-
daily image, the installer always crashes and the installation is not
completed (Ubuntu Noble Numbat (development branch), Release 24.04)

In every daily version, always is the same error: "El archivo de
secuencia de comandos principal /usr/lib/x86_64-linux-
gnu/calamares/modules/networkcfg/main.py para el trabajo de Python
networckg generó una excepción"

This bug has ben solved in calamares 3.3.5 so it seems a good idea
update to this version.

Comparing with the KDE NEON version I have discovered that editing line
158 in .../calamares/modules/networkcfg/main.py from "os.chmod(f,
0o0600" to "os.chmod(f.fileno(), 0o600)" also solves the problem and
allows the installation to be completed successfully.

** Affects: calamares (Ubuntu)
 Importance: Undecided
 Status: New

-- 
Kubuntu noble daily installer broken
https://bugs.launchpad.net/bugs/2058367
You received this bug notification because you are a member of Ubuntu Studio 
Bugs, which is subscribed to calamares in Ubuntu.

-- 
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 2058067] Re: raysession.py crashed with ModuleNotFoundError in /usr/share/raysession/src/gui/patchbay/patchcanvas/icon_widget.py: No module named 'PyQt5.QtSvg'

2024-03-15 Thread Launchpad Bug Tracker
This bug was fixed in the package raysession - 0.14.3-0ubuntu2

---
raysession (0.14.3-0ubuntu2) noble; urgency=medium

  * Fix for missing python3-qtpy runtime dependency (LP: #2058067)

 -- Erich Eickmeyer   Fri, 15 Mar 2024 13:35:18
-0700

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

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

Title:
  raysession.py crashed with ModuleNotFoundError in
  /usr/share/raysession/src/gui/patchbay/patchcanvas/icon_widget.py: No
  module named 'PyQt5.QtSvg'

Status in raysession package in Ubuntu:
  Fix Released

Bug description:
  Attempting to launch RaySession on Edubuntu, clean install, Raspberry
  Pi 5. Likely missing `python3-qtpy` dependency.

  ProblemType: Crash
  DistroRelease: Ubuntu 24.04
  Package: raysession 0.14.3-0ubuntu1
  ProcVersionSignature: Ubuntu 6.8.0-1001.1-raspi 6.8.0-rc4
  Uname: Linux 6.8.0-1001-raspi aarch64
  ApportVersion: 2.28.0-0ubuntu1
  Architecture: arm64
  CasperMD5CheckResult: unknown
  CloudArchitecture: aarch64
  CloudID: none
  CloudName: none
  CloudPlatform: none
  CloudSubPlatform: config
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Mar 15 13:24:16 2024
  ExecutablePath: /usr/share/raysession/src/gui/raysession.py
  InterpreterPath: /usr/bin/python3.12
  PackageArchitecture: all
  ProcCmdline: /usr/bin/python3 -u /usr/share/raysession/src/bin/raysession
  ProcEnviron:
   LANG=C.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  Python3Details: /usr/bin/python3.12, Python 3.12.2, python3-minimal, 
3.12.1-0ubuntu2
  PythonArgs: ['/usr/share/raysession/src/bin/raysession']
  PythonDetails: N/A
  SourcePackage: raysession
  Title: raysession.py crashed with ModuleNotFoundError in 
/usr/share/raysession/src/gui/patchbay/patchcanvas/icon_widget.py: No module 
named 'PyQt5.QtSvg'
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo users

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/raysession/+bug/2058067/+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 2056481] Re: [snap] Thunderbird does not support native notifications on KDE Plasma Desktop

2024-03-11 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: xdg-desktop-portal (Ubuntu)
   Status: New => Confirmed

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

Title:
  [snap] Thunderbird does not support native notifications on KDE Plasma
  Desktop

Status in thunderbird package in Ubuntu:
  Confirmed
Status in xdg-desktop-portal package in Ubuntu:
  Confirmed

Bug description:
  After testing and upgrading, I have discovered that the thunderbird
  snap does not support native notifications on KDE Plasma Desktop on
  either Kubuntu or Ubuntu Studio (same packages and desktop, really).
  This might be an issue with xdg-desktop-portal, so I'm also going to
  mark it as affected.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/2056481/+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 2056481] Re: [snap] Thunderbird does not support native notifications on KDE Plasma Desktop

2024-03-11 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: thunderbird (Ubuntu)
   Status: New => Confirmed

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

Title:
  [snap] Thunderbird does not support native notifications on KDE Plasma
  Desktop

Status in thunderbird package in Ubuntu:
  Confirmed
Status in xdg-desktop-portal package in Ubuntu:
  Confirmed

Bug description:
  After testing and upgrading, I have discovered that the thunderbird
  snap does not support native notifications on KDE Plasma Desktop on
  either Kubuntu or Ubuntu Studio (same packages and desktop, really).
  This might be an issue with xdg-desktop-portal, so I'm also going to
  mark it as affected.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/2056481/+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 2043161] Re: lubuntu noble install to sony vaio (efi, encryption, no internet) fails

2024-03-09 Thread Launchpad Bug Tracker
[Expired for calamares (Ubuntu) because there has been no activity for
60 days.]

** Changed in: calamares (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  lubuntu noble install to sony vaio (efi, encryption, no internet)
  fails

Status in calamares package in Ubuntu:
  Expired

Bug description:
  install on sony vaio (lubuntu noble)

  offline install, encryption without swap, also selected auto-login (If
  I recall correctly)

  install fails reported; message/popup showing

  ---
  Command apt install -y --no-upgrade -o 
Acquire::gpgv::Options::=--ignore-time-conflict grub-efi-$(if grep -q 64 
/sys/firmware/efi/fw_platform_size; then echo amd64-signed; else echo ia32; 
fi) finished with exit code 100.
  Output:
  WARNING: apt does not have a stable CLI interface. Use with caution in 
scripts.

  Reading package lists...
  Building dependency tree...
  Reading state information...
  E: Unable to locate package grub-efi-amd64-signed
  ---

  this however seems familiar (reported earlier by Leok & sudodus issue;
  as I recall; though their messages mentioned source issue (cdrom
  related) so maybe unrelated

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: calamares 3.3.0-alpha4-0ubuntu1
  ProcVersionSignature: Ubuntu 6.5.0-9.9-generic 6.5.3
  Uname: Linux 6.5.0-9-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-0ubuntu6
  Architecture: amd64
  CasperMD5CheckResult: pass
  CasperVersion: 1.486
  CurrentDesktop: LXQt
  Date: Fri Nov 10 16:59:25 2023
  LiveMediaBuild: Lubuntu 24.04 "Noble Numbat" - Daily amd64 (20231109)
  RelatedPackageVersions:
   calamares-settings-ubuntu-common 1:23.10.4
   calamares-settings-lubuntu   1:23.10.4
   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/2043161/+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 2044587] Re: lubuntu noble calamares failure

2024-03-09 Thread Launchpad Bug Tracker
[Expired for calamares (Ubuntu) because there has been no activity for
60 days.]

** Changed in: calamares (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  lubuntu noble calamares failure

Status in calamares package in Ubuntu:
  Expired

Bug description:
  Lubuntu noble re-install (attempted non-destructive) on
  - hp prodesk 600 g3 sff (i5-7500, 8gb, nvidia geforce gt710 (gk208b) + intel 
graphics 630)

  ** expected result

  Install completes; reboot into new system

  ** actual outcome

  Error messages are as follows

  ---
  Command apt install -y --no-upgrade -o 
Acquire::gpgv::Options::=--ignore-time-conflict shim-signed finished with 
exit code 100.
  Output:
  WARNING: apt does not have a stable CLI interface. Use with caution in 
scripts.

  Reading package lists...
  Building dependency tree...
  Reading state information...
  The following NEW packages will be installed:
    shim-signed
  0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
  Need to get 0 B/663 kB of archives.
  After this operation, 4837 kB of additional disk space will be used.
  Get:1 cdrom://Lubuntu 24.04 _Noble Numbat_ - Daily amd64 (20231124) 
noble/main amd64 shim-signed amd64 1.56+15.7-0ubuntu1 [663 kB]
  Preconfiguring packages ...
  E: Can not write log (Is /dev/pts mounted?) - posix_openpt (19: No such 
device)
  Selecting previously unselected package shim-signed.
  (Reading database ... 275142 files and directories currently installed.)
  Preparing to unpack .../shim-signed_1.56+15.7-0ubuntu1_amd64.deb ...
  Unpacking shim-signed (1.56+15.7-0ubuntu1) ...
  Setting up shim-signed (1.56+15.7-0ubuntu1) ...
  Installing grub to /boot/efi.
  Installing for x86_64-efi platform.
  Installation finished. No error reported.
  Error! The module/version combo: nvidia-470.223.02/6.5.0-9-generic is not 
located in the DKMS tree.

  shim-signed: failed to prepare dkms module for signing; ignoring.
    module: nvidia/470.223.02/6.5.0-9-generic
    kernel: 6.5.0-9-generic
  Unknown terminal: qterminal
  Check the TERM environment variable.
  Also make sure that the terminal is defined in the terminfo database.
  Alternatively, set the TERMCAP environment variable to the desired
  termcap entry.
  debconf: whiptail output the above errors, giving up!
  dpkg: error processing package shim-signed (--configure):
   installed shim-signed package post-installation script subprocess returned 
error exit status 255
  Errors were encountered while processing:
   shim-signed
  E: Sub-process /usr/bin/dpkg returned an error code (1)
  ---

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: calamares 3.3.0-alpha6-0ubuntu1
  ProcVersionSignature: Ubuntu 6.5.0-9.9-generic 6.5.3
  Uname: Linux 6.5.0-9-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-0ubuntu6
  Architecture: amd64
  CasperMD5CheckResult: pass
  CasperVersion: 1.487
  CurrentDesktop: LXQt
  Date: Sat Nov 25 14:56:33 2023
  LiveMediaBuild: Lubuntu 24.04 "Noble Numbat" - Daily amd64 (20231124)
  RelatedPackageVersions:
   calamares-settings-ubuntu-common 1:24.04.8
   calamares-settings-lubuntu   1:24.04.8
   xfsprogs 6.5.0-1
   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/2044587/+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 2056481] [NEW] [snap] Thunderbird does not support native notifications on KDE Plasma Desktop

2024-03-07 Thread Launchpad Bug Tracker
You have been subscribed to a public bug by Erich Eickmeyer (eeickmeyer):

After testing and upgrading, I have discovered that the thunderbird snap
does not support native notifications on KDE Plasma Desktop on either
Kubuntu or Ubuntu Studio (same packages and desktop, really). This might
be an issue with xdg-desktop-portal, so I'm also going to mark it as
affected.

** Affects: thunderbird (Ubuntu)
 Importance: High
 Status: New

** Affects: xdg-desktop-portal (Ubuntu)
 Importance: High
 Status: New

-- 
[snap] Thunderbird does not support native notifications on KDE Plasma Desktop
https://bugs.launchpad.net/bugs/2056481
You received this bug notification because you are a member of Ubuntu Studio 
Bugs, which is subscribed to the bug report.

-- 
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 2056375] [NEW] Ubuntu Studio ISO fails to build: "/usr/sbin/grub-probe: error: failed to get canonical path of `overlay'."

2024-03-06 Thread Launchpad Bug Tracker
You have been subscribed to a public bug by Simon Quigley (tsimonq2):

Full build log is at
https://launchpadlibrarian.net/717896339/buildlog_ubuntu_noble_amd64_ubuntustudio_BUILDING.txt.gz.
Relevant section:

Preconfiguring packages ...
Fetched 692 MB in 4s (169 MB/s)
(Reading database ... 
(Reading database ... 5%
(Reading database ... 10%
(Reading database ... 15%
(Reading database ... 20%
(Reading database ... 25%
(Reading database ... 30%
(Reading database ... 35%
(Reading database ... 40%
(Reading database ... 45%
(Reading database ... 50%
(Reading database ... 55%
(Reading database ... 60%
(Reading database ... 65%
(Reading database ... 70%
(Reading database ... 75%
(Reading database ... 80%
(Reading database ... 85%
(Reading database ... 90%
(Reading database ... 95%
(Reading database ... 100%
(Reading database ... 347331 files and directories currently installed.)
Removing os-prober (1.81ubuntu3) ...
Removing memtest86+ (7.00-1) ...
Removing ubuntustudio-lowlatency-settings (24.04.14) ...
Removing plymouth-theme-ubuntustudio (24.04.1) ...
update-alternatives: removing manually selected alternative - switching 
default.plymouth to auto mode
update-alternatives: using /usr/share/plymouth/themes/bgrt/bgrt.plymouth to 
provide /usr/share/plymouth/themes/default.plymouth (default.plymouth) in auto 
mode
update-alternatives: using 
/usr/share/plymouth/themes/ubuntu-text/ubuntu-text.plymouth to provide 
/usr/share/plymouth/themes/text.plymouth (text.plymouth) in auto mode
update-initramfs: deferring update (trigger activated)
/usr/sbin/grub-probe: error: failed to get canonical path of `overlay'.
dpkg: error processing package plymouth-theme-ubuntustudio (--remove):
 installed plymouth-theme-ubuntustudio package post-removal script subprocess 
returned error exit status 1
dpkg: too many errors, stopping
Errors were encountered while processing:
 plymouth-theme-ubuntustudio
Processing was halted because there were too many errors.

** Affects: grub2 (Ubuntu)
 Importance: Critical
 Status: Confirmed


** Tags: rls-nn-incoming
-- 
Ubuntu Studio ISO fails to build: "/usr/sbin/grub-probe: error: failed to get 
canonical path of `overlay'."
https://bugs.launchpad.net/bugs/2056375
You received this bug notification because you are a member of Ubuntu Studio 
Bugs, which is subscribed to the bug report.

-- 
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 2046844] Re: AppArmor user namespace creation restrictions cause many applications to crash with SIGTRAP

2024-03-06 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: firefox (Ubuntu)
   Status: New => Confirmed

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

Title:
  AppArmor user namespace creation restrictions cause many applications
  to crash with SIGTRAP

Status in akonadiconsole package in Ubuntu:
  Fix Released
Status in akregator package in Ubuntu:
  Fix Released
Status in angelfish package in Ubuntu:
  Fix Released
Status in apparmor package in Ubuntu:
  Fix Released
Status in bubblewrap package in Ubuntu:
  Confirmed
Status in cantor package in Ubuntu:
  Fix Released
Status in devhelp package in Ubuntu:
  Fix Released
Status in digikam package in Ubuntu:
  Fix Released
Status in epiphany-browser package in Ubuntu:
  Fix Released
Status in evolution package in Ubuntu:
  Fix Released
Status in falkon package in Ubuntu:
  Fix Released
Status in firefox package in Ubuntu:
  Confirmed
Status in freecad package in Ubuntu:
  Confirmed
Status in geary package in Ubuntu:
  Confirmed
Status in ghostwriter package in Ubuntu:
  Fix Released
Status in gnome-packagekit package in Ubuntu:
  Confirmed
Status in goldendict-webengine package in Ubuntu:
  Confirmed
Status in kalgebra package in Ubuntu:
  Fix Released
Status in kchmviewer package in Ubuntu:
  Confirmed
Status in kdeplasma-addons package in Ubuntu:
  Fix Released
Status in kgeotag package in Ubuntu:
  Fix Released
Status in kiwix package in Ubuntu:
  Confirmed
Status in kmail package in Ubuntu:
  Fix Released
Status in konqueror package in Ubuntu:
  Fix Released
Status in kontact package in Ubuntu:
  Fix Released
Status in marble package in Ubuntu:
  Fix Released
Status in notepadqq package in Ubuntu:
  Confirmed
Status in opam package in Ubuntu:
  Fix Released
Status in pageedit package in Ubuntu:
  Confirmed
Status in plasma-desktop package in Ubuntu:
  Fix Released
Status in plasma-welcome package in Ubuntu:
  Fix Released
Status in privacybrowser package in Ubuntu:
  Confirmed
Status in qmapshack package in Ubuntu:
  Confirmed
Status in qutebrowser package in Ubuntu:
  Confirmed
Status in rssguard package in Ubuntu:
  Confirmed
Status in steam package in Ubuntu:
  Fix Committed
Status in supercollider package in Ubuntu:
  Confirmed
Status in tellico package in Ubuntu:
  Fix Released

Bug description:
  Hi, I run Ubuntu development branch 24.04 and I have a problem with
  Epiphany browser 45.1-1 (Gnome Web): program doesn't launch, and I get
  this error

  $ epiphany
  bwrap: Creating new namespace failed: Permission denied

  ** (epiphany:12085): ERROR **: 14:44:35.023: Failed to fully launch 
dbus-proxy: Le processus fils s’est terminé avec le code 1
  Trappe pour point d'arrêt et de trace (core dumped)

  $ epiphany
  bwrap: Creating new namespace failed: Permission denied

  ** (epiphany:30878): ERROR **: 22:22:26.926: Failed to fully launch 
dbus-proxy: Le processus fils s’est terminé avec le code 1
  Trappe pour point d'arrêt et de trace (core dumped)

  Thanks for your help!

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/akonadiconsole/+bug/2046844/+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 2056313] [NEW] Lubuntu-24.04 Installation failed

2024-03-06 Thread Launchpad Bug Tracker
You have been subscribed to a public bug:

Fresh installation of Lubuntu 24.04 (Noble Numbat) Daily Build  on
VirtualBox 7 on March-06-2024. Installation failed. See attached
screenshot. The same happend on March-04-2024.

** Affects: calamares (Ubuntu)
 Importance: Undecided
 Status: New

-- 
Lubuntu-24.04 Installation failed
https://bugs.launchpad.net/bugs/2056313
You received this bug notification because you are a member of Ubuntu Studio 
Bugs, which is subscribed to calamares in Ubuntu.

-- 
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 2017786] Re: update script in ubuntu-meta not handling germinate or specified versions

2024-02-27 Thread Launchpad Bug Tracker
This bug was fixed in the package kubuntu-meta - 1.443

---
kubuntu-meta (1.443) noble; urgency=medium

  * Update update to check for germinate. Ref: (LP: #2017786)

 -- Scarlett Moore   Tue, 27 Feb 2024 05:02:36 -0700

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

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

Title:
  update script in ubuntu-meta not handling germinate or specified
  versions

Status in edubuntu-meta package in Ubuntu:
  Won't Fix
Status in kubuntu-meta package in Ubuntu:
  Fix Released
Status in lubuntu-meta package in Ubuntu:
  New
Status in ubuntu-budgie-meta package in Ubuntu:
  New
Status in ubuntu-mate-meta package in Ubuntu:
  New
Status in ubuntu-meta package in Ubuntu:
  Fix Released
Status in ubuntu-unity-meta package in Ubuntu:
  New
Status in ubuntucinnamon-meta package in Ubuntu:
  New
Status in ubuntukylin-meta package in Ubuntu:
  New
Status in ubuntustudio-meta package in Ubuntu:
  Won't Fix
Status in xubuntu-meta package in Ubuntu:
  New

Bug description:
  update script handled debootstrap and devscripts, does not handle
  germinate. also doesn't handle potential specified versions in the
  package directory.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/edubuntu-meta/+bug/2017786/+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 2046844] Re: AppArmor user namespace creation restrictions cause many applications to crash with SIGTRAP

2024-02-26 Thread Launchpad Bug Tracker
This bug was fixed in the package ghostwriter - 23.08.5+ds-0ubuntu1

---
ghostwriter (23.08.5+ds-0ubuntu1) noble; urgency=medium

  * New upstream release (23.08.5)

ghostwriter (23.08.4+ds-0ubuntu2) noble; urgency=medium

  * Add apparmor profile to fix userns. (LP: #2046844)

 -- Scarlett Moore   Thu, 22 Feb 2024 09:31:12 -0700

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

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

Title:
  AppArmor user namespace creation restrictions cause many applications
  to crash with SIGTRAP

Status in akonadiconsole package in Ubuntu:
  Fix Released
Status in akregator package in Ubuntu:
  Fix Released
Status in angelfish package in Ubuntu:
  In Progress
Status in apparmor package in Ubuntu:
  Fix Released
Status in bubblewrap package in Ubuntu:
  Confirmed
Status in cantor package in Ubuntu:
  Fix Released
Status in devhelp package in Ubuntu:
  Fix Released
Status in digikam package in Ubuntu:
  Fix Released
Status in epiphany-browser package in Ubuntu:
  Fix Released
Status in evolution package in Ubuntu:
  Fix Released
Status in falkon package in Ubuntu:
  Fix Released
Status in freecad package in Ubuntu:
  Confirmed
Status in ghostwriter package in Ubuntu:
  Fix Released
Status in gnome-packagekit package in Ubuntu:
  Confirmed
Status in goldendict-webengine package in Ubuntu:
  Confirmed
Status in kalgebra package in Ubuntu:
  Fix Released
Status in kchmviewer package in Ubuntu:
  Confirmed
Status in kdeplasma-addons package in Ubuntu:
  Confirmed
Status in kgeotag package in Ubuntu:
  Fix Released
Status in kiwix package in Ubuntu:
  Confirmed
Status in kmail package in Ubuntu:
  Fix Released
Status in konqueror package in Ubuntu:
  Fix Released
Status in kontact package in Ubuntu:
  Fix Released
Status in marble package in Ubuntu:
  Fix Released
Status in notepadqq package in Ubuntu:
  Confirmed
Status in opam package in Ubuntu:
  Fix Released
Status in pageedit package in Ubuntu:
  Confirmed
Status in plasma-desktop package in Ubuntu:
  Confirmed
Status in plasma-welcome package in Ubuntu:
  Fix Released
Status in privacybrowser package in Ubuntu:
  Confirmed
Status in qmapshack package in Ubuntu:
  Confirmed
Status in qutebrowser package in Ubuntu:
  Confirmed
Status in rssguard package in Ubuntu:
  Confirmed
Status in steam package in Ubuntu:
  Fix Committed
Status in supercollider package in Ubuntu:
  Confirmed
Status in tellico package in Ubuntu:
  Fix Released

Bug description:
  Hi, I run Ubuntu development branch 24.04 and I have a problem with
  Epiphany browser 45.1-1 (Gnome Web): program doesn't launch, and I get
  this error

  $ epiphany
  bwrap: Creating new namespace failed: Permission denied

  ** (epiphany:12085): ERROR **: 14:44:35.023: Failed to fully launch 
dbus-proxy: Le processus fils s’est terminé avec le code 1
  Trappe pour point d'arrêt et de trace (core dumped)

  $ epiphany
  bwrap: Creating new namespace failed: Permission denied

  ** (epiphany:30878): ERROR **: 22:22:26.926: Failed to fully launch 
dbus-proxy: Le processus fils s’est terminé avec le code 1
  Trappe pour point d'arrêt et de trace (core dumped)

  Thanks for your help!

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/akonadiconsole/+bug/2046844/+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 2046844] Re: AppArmor user namespace creation restrictions cause many applications to crash with SIGTRAP

2024-02-26 Thread Launchpad Bug Tracker
** Merge proposal linked:
   https://code.launchpad.net/~p-pisati/britney/+git/hints-ubuntu/+merge/461043

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

Title:
  AppArmor user namespace creation restrictions cause many applications
  to crash with SIGTRAP

Status in akonadiconsole package in Ubuntu:
  Fix Released
Status in akregator package in Ubuntu:
  Fix Released
Status in angelfish package in Ubuntu:
  In Progress
Status in apparmor package in Ubuntu:
  Fix Released
Status in bubblewrap package in Ubuntu:
  Confirmed
Status in cantor package in Ubuntu:
  Fix Released
Status in devhelp package in Ubuntu:
  Fix Released
Status in digikam package in Ubuntu:
  Fix Released
Status in epiphany-browser package in Ubuntu:
  Fix Released
Status in evolution package in Ubuntu:
  Fix Released
Status in falkon package in Ubuntu:
  Fix Released
Status in freecad package in Ubuntu:
  Confirmed
Status in ghostwriter package in Ubuntu:
  Fix Committed
Status in gnome-packagekit package in Ubuntu:
  Confirmed
Status in goldendict-webengine package in Ubuntu:
  Confirmed
Status in kalgebra package in Ubuntu:
  Fix Released
Status in kchmviewer package in Ubuntu:
  Confirmed
Status in kdeplasma-addons package in Ubuntu:
  Confirmed
Status in kgeotag package in Ubuntu:
  Fix Released
Status in kiwix package in Ubuntu:
  Confirmed
Status in kmail package in Ubuntu:
  Fix Released
Status in konqueror package in Ubuntu:
  Fix Released
Status in kontact package in Ubuntu:
  Fix Released
Status in marble package in Ubuntu:
  Fix Released
Status in notepadqq package in Ubuntu:
  Confirmed
Status in opam package in Ubuntu:
  Fix Released
Status in pageedit package in Ubuntu:
  Confirmed
Status in plasma-desktop package in Ubuntu:
  Confirmed
Status in plasma-welcome package in Ubuntu:
  Fix Released
Status in privacybrowser package in Ubuntu:
  Confirmed
Status in qmapshack package in Ubuntu:
  Confirmed
Status in qutebrowser package in Ubuntu:
  Confirmed
Status in rssguard package in Ubuntu:
  Confirmed
Status in steam package in Ubuntu:
  Fix Committed
Status in supercollider package in Ubuntu:
  Confirmed
Status in tellico package in Ubuntu:
  Fix Released

Bug description:
  Hi, I run Ubuntu development branch 24.04 and I have a problem with
  Epiphany browser 45.1-1 (Gnome Web): program doesn't launch, and I get
  this error

  $ epiphany
  bwrap: Creating new namespace failed: Permission denied

  ** (epiphany:12085): ERROR **: 14:44:35.023: Failed to fully launch 
dbus-proxy: Le processus fils s’est terminé avec le code 1
  Trappe pour point d'arrêt et de trace (core dumped)

  $ epiphany
  bwrap: Creating new namespace failed: Permission denied

  ** (epiphany:30878): ERROR **: 22:22:26.926: Failed to fully launch 
dbus-proxy: Le processus fils s’est terminé avec le code 1
  Trappe pour point d'arrêt et de trace (core dumped)

  Thanks for your help!

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/akonadiconsole/+bug/2046844/+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 2039663] Re: gnome-font-manager hangs on launch, sometimes

2024-02-26 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: font-manager (Ubuntu)
   Status: New => Confirmed

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

Title:
  gnome-font-manager hangs on launch, sometimes

Status in font-manager package in Ubuntu:
  Confirmed

Bug description:
  /usr/bin/gnome-font-viewer, /usr/libexec/font-manager/font-viewer

  Launch from favorites, shows windows, not responding to window actions and 
close
  Launch new window from favorites, same thing happens.
  Launch from show-applications window, same thing happens.

  THis is occasional, not constant.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: font-manager 0.7.7-0.3
  ProcVersionSignature: Ubuntu 5.15.0-86.96~20.04.1-generic 5.15.122
  Uname: Linux 5.15.0-86-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Oct 18 03:03:18 2023
  InstallationDate: Installed on 2021-06-13 (856 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: font-manager
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/font-manager/+bug/2039663/+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 2046844] Re: AppArmor user namespace creation restrictions cause many applications to crash with SIGTRAP

2024-02-25 Thread Launchpad Bug Tracker
This bug was fixed in the package kgeotag - 1.5.0-1ubuntu1

---
kgeotag (1.5.0-1ubuntu1) noble; urgency=medium

  * Add apparmor profile to fix userns. Ref: (LP: #2046844)

 -- Scarlett Moore   Thu, 15 Feb 2024 00:06:50 -0700

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

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

Title:
  AppArmor user namespace creation restrictions cause many applications
  to crash with SIGTRAP

Status in akonadiconsole package in Ubuntu:
  Fix Released
Status in akregator package in Ubuntu:
  Fix Released
Status in angelfish package in Ubuntu:
  In Progress
Status in apparmor package in Ubuntu:
  Fix Released
Status in bubblewrap package in Ubuntu:
  Confirmed
Status in cantor package in Ubuntu:
  Fix Released
Status in devhelp package in Ubuntu:
  Fix Released
Status in digikam package in Ubuntu:
  Fix Released
Status in epiphany-browser package in Ubuntu:
  Fix Released
Status in evolution package in Ubuntu:
  Fix Released
Status in falkon package in Ubuntu:
  Fix Released
Status in freecad package in Ubuntu:
  Confirmed
Status in ghostwriter package in Ubuntu:
  Fix Committed
Status in gnome-packagekit package in Ubuntu:
  Confirmed
Status in goldendict-webengine package in Ubuntu:
  Confirmed
Status in kalgebra package in Ubuntu:
  Fix Released
Status in kchmviewer package in Ubuntu:
  Confirmed
Status in kdeplasma-addons package in Ubuntu:
  Confirmed
Status in kgeotag package in Ubuntu:
  Fix Released
Status in kiwix package in Ubuntu:
  Confirmed
Status in kmail package in Ubuntu:
  Fix Released
Status in konqueror package in Ubuntu:
  Fix Released
Status in kontact package in Ubuntu:
  Fix Released
Status in marble package in Ubuntu:
  Fix Released
Status in notepadqq package in Ubuntu:
  Confirmed
Status in opam package in Ubuntu:
  Fix Released
Status in pageedit package in Ubuntu:
  Confirmed
Status in plasma-desktop package in Ubuntu:
  Confirmed
Status in plasma-welcome package in Ubuntu:
  Fix Released
Status in privacybrowser package in Ubuntu:
  Confirmed
Status in qmapshack package in Ubuntu:
  Confirmed
Status in qutebrowser package in Ubuntu:
  Confirmed
Status in rssguard package in Ubuntu:
  Confirmed
Status in steam package in Ubuntu:
  Fix Committed
Status in supercollider package in Ubuntu:
  Confirmed
Status in tellico package in Ubuntu:
  Fix Released

Bug description:
  Hi, I run Ubuntu development branch 24.04 and I have a problem with
  Epiphany browser 45.1-1 (Gnome Web): program doesn't launch, and I get
  this error

  $ epiphany
  bwrap: Creating new namespace failed: Permission denied

  ** (epiphany:12085): ERROR **: 14:44:35.023: Failed to fully launch 
dbus-proxy: Le processus fils s’est terminé avec le code 1
  Trappe pour point d'arrêt et de trace (core dumped)

  $ epiphany
  bwrap: Creating new namespace failed: Permission denied

  ** (epiphany:30878): ERROR **: 22:22:26.926: Failed to fully launch 
dbus-proxy: Le processus fils s’est terminé avec le code 1
  Trappe pour point d'arrêt et de trace (core dumped)

  Thanks for your help!

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/akonadiconsole/+bug/2046844/+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 2046844] Re: AppArmor user namespace creation restrictions cause many applications to crash with SIGTRAP

2024-02-25 Thread Launchpad Bug Tracker
This bug was fixed in the package akonadiconsole - 4:23.08.5-0ubuntu2

---
akonadiconsole (4:23.08.5-0ubuntu2) noble; urgency=medium

  * Add apparmor profile to fix userns. Ref: (LP: #2046844)

 -- Scarlett Moore   Sun, 25 Feb 2024 01:25:04 -0700

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

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

Title:
  AppArmor user namespace creation restrictions cause many applications
  to crash with SIGTRAP

Status in akonadiconsole package in Ubuntu:
  Fix Released
Status in akregator package in Ubuntu:
  Fix Released
Status in angelfish package in Ubuntu:
  In Progress
Status in apparmor package in Ubuntu:
  Fix Released
Status in bubblewrap package in Ubuntu:
  Confirmed
Status in cantor package in Ubuntu:
  Fix Released
Status in devhelp package in Ubuntu:
  Fix Released
Status in digikam package in Ubuntu:
  Fix Released
Status in epiphany-browser package in Ubuntu:
  Fix Released
Status in evolution package in Ubuntu:
  Fix Released
Status in falkon package in Ubuntu:
  Fix Released
Status in freecad package in Ubuntu:
  Confirmed
Status in ghostwriter package in Ubuntu:
  Fix Committed
Status in gnome-packagekit package in Ubuntu:
  Confirmed
Status in goldendict-webengine package in Ubuntu:
  Confirmed
Status in kalgebra package in Ubuntu:
  Fix Released
Status in kchmviewer package in Ubuntu:
  Confirmed
Status in kdeplasma-addons package in Ubuntu:
  Confirmed
Status in kgeotag package in Ubuntu:
  In Progress
Status in kiwix package in Ubuntu:
  Confirmed
Status in kmail package in Ubuntu:
  Fix Released
Status in konqueror package in Ubuntu:
  Fix Released
Status in kontact package in Ubuntu:
  Fix Released
Status in marble package in Ubuntu:
  Fix Released
Status in notepadqq package in Ubuntu:
  Confirmed
Status in opam package in Ubuntu:
  Fix Released
Status in pageedit package in Ubuntu:
  Confirmed
Status in plasma-desktop package in Ubuntu:
  Confirmed
Status in plasma-welcome package in Ubuntu:
  Fix Released
Status in privacybrowser package in Ubuntu:
  Confirmed
Status in qmapshack package in Ubuntu:
  Confirmed
Status in qutebrowser package in Ubuntu:
  Confirmed
Status in rssguard package in Ubuntu:
  Confirmed
Status in steam package in Ubuntu:
  Fix Committed
Status in supercollider package in Ubuntu:
  Confirmed
Status in tellico package in Ubuntu:
  Fix Released

Bug description:
  Hi, I run Ubuntu development branch 24.04 and I have a problem with
  Epiphany browser 45.1-1 (Gnome Web): program doesn't launch, and I get
  this error

  $ epiphany
  bwrap: Creating new namespace failed: Permission denied

  ** (epiphany:12085): ERROR **: 14:44:35.023: Failed to fully launch 
dbus-proxy: Le processus fils s’est terminé avec le code 1
  Trappe pour point d'arrêt et de trace (core dumped)

  $ epiphany
  bwrap: Creating new namespace failed: Permission denied

  ** (epiphany:30878): ERROR **: 22:22:26.926: Failed to fully launch 
dbus-proxy: Le processus fils s’est terminé avec le code 1
  Trappe pour point d'arrêt et de trace (core dumped)

  Thanks for your help!

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/akonadiconsole/+bug/2046844/+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 1873950] Re: Calamares failed: command 'mount' returned non-zero exit status 32.

2024-02-23 Thread Launchpad Bug Tracker
[Expired for calamares (Ubuntu) because there has been no activity for
60 days.]

** Changed in: calamares (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  Calamares failed: command 'mount' returned non-zero exit status 32.

Status in calamares package in Ubuntu:
  Expired

Bug description:
  Booting in my 'standard test computer' a Toshiba laptop, Calamares
  failed with the most basic mode, to use the whole drive for the new
  Lubuntu installation.

  http://www.toshiba.se/laptops/satellite-pro/c850/satellite-
  pro-c850-19w/

  Booted in BIOS mode. The partition table in the internal drive is
  MSDOS. There were two previous operating systems in the drive.

  I tried a second time, this time with a clean drive (after the
  previous try, and this time Calamares worked). So either it was a
  temporary glitch, or there was some confusion in the first case
  because of the partition table (which contained and EFI system
  partition, not only root partitions for a dual boot system).

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: calamares 3.2.20-0ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-25.29-generic 5.4.30
  Uname: Linux 5.4.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-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: pass
  CasperVersion: 1.445
  CurrentDesktop: LXQt
  Date: Mon Apr 20 21:25:04 2020
  LiveMediaBuild: Lubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200420)
  RelatedPackageVersions:
   calamares-settings-ubuntu-common 1:20.04.2
   calamares-settings-lubuntu   1:20.04.2
   xfsprogs 5.3.0-1ubuntu2
   btrfs-progs  5.4.1-2
  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/1873950/+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 1863421] Re: Lubuntu installer does not honor the 'flag', 'bios-grub' when GPT option is selected leading to failure to install grub.

2024-02-22 Thread Launchpad Bug Tracker
[Expired for calamares (Ubuntu) because there has been no activity for
60 days.]

** Changed in: calamares (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  Lubuntu installer does not honor the 'flag', 'bios-grub' when GPT
  option is selected leading to failure to install grub.

Status in calamares package in Ubuntu:
  Expired

Bug description:
  I wanted to install Lubuntu (20.04) with btrfs root. I am using
  20200208 media and during partition setup choose 'Manual' option and
  set partitions as follows:

  /dev/sda1 8M unformatted (selected flag 'bios-grub', from the installer GUI)
  /dev/sda2 2G swap
  /dev/sda3 18G btrfs for /

  Continuing with installation with this option, the grub-install fails
  complaining it could not see 'BIOS boot' partition. See attached
  sceenshot.

  Solution is to manually set 'BIOS boot'. May be one could do it
  beforehand, which I did not try. What I did was to create partitions
  as above and while installation was in progress, opened up a terminal
  and manually set partition type to BIOS boot. I used parted and did
  'set 1 bios_grub on'.

  I checked on Kubuntu; if we choose 'Reservered BIOS boot area' option,
  the installer (ubiquity) remembers this and grub-install finishes
  successfully.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: calamares (not installed)
  ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18
  Uname: Linux 5.4.0-14-generic x86_64
  ApportVersion: 2.20.11-0ubuntu16
  Architecture: amd64
  CurrentDesktop: LXQt
  Date: Sat Feb 15 19:33:25 2020
  InstallationDate: Installed on 2020-02-15 (0 days ago)
  InstallationMedia: Lubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200208)
  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/1863421/+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 1867826] Re: Press "Cancel" button during initial "waiting on 16 modules to load" causes Calamares to hang

2024-02-22 Thread Launchpad Bug Tracker
[Expired for calamares (Ubuntu) because there has been no activity for
60 days.]

** Changed in: calamares (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  Press "Cancel" button during initial "waiting on 16 modules to load"
  causes Calamares to hang

Status in calamares package in Ubuntu:
  Expired

Bug description:
  ISO testing 20.04 Lubuntu daily image (20200317). If I click the
  "Cancel" button while Calamares is starting up, displaying the
  "waiting on n modules to load... 4 seconds," it hangs.

  Even right-clicking the Calamares placeholder in the taskbar, and
  "close" doesn't entirely get rid of it. The Calamares window
  disappears. But, the "Lubuntu inst... [Killing]" placeholder remains
  in the taskbar.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: calamares 3.2.20-0ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24
  Uname: Linux 5.4.0-18-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-0ubuntu20
  Architecture: amd64
  CasperVersion: 1.441
  CurrentDesktop: LXQt
  Date: Tue Mar 17 19:31:14 2020
  LiveMediaBuild: Lubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200317)
  RelatedPackageVersions:
   calamares-settings-ubuntu-common 1:20.04.2
   calamares-settings-lubuntu   1:20.04.2
   xfsprogs 5.3.0-1ubuntu1
   btrfs-progs  5.4.1-2
  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/1867826/+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 1917724] Re: lubuntu hirsute install fail mkfs.xfs

2024-02-22 Thread Launchpad Bug Tracker
[Expired for calamares (Ubuntu) because there has been no activity for
60 days.]

** Changed in: calamares (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  lubuntu hirsute install fail mkfs.xfs

Status in calamares package in Ubuntu:
  Expired

Bug description:
  Lubuntu hirsute QA-test install (daily) on
  -dell [optiplex] 755 (c2d-e6850, 5gb, amd/ati radeon rv516/x1300/x1550)

  Testcase:  re-use /home (sda8) & format of sda9 for / (XFS this time,
  it was reiserfs; but I've been alternating between XFS & BTRFS
  usually)

  The installer failed to create partition on disk 'ST3160815AS'.
  
==
  Create a new partition (22.00 GiB, xfs) on ‘/dev/sda’
  
==
  
==
  Job: Create new partition on device ‘/dev/sda’
  
==
  Command: mkfs.xfs -f /dev/sda9
  
==

  Note: this was a repeat install of lp 1864787 / 1914521
  so the problem could be related to those.. error listed differs though

  In session.log is "Command: sfdisk --force --append /dev/sda" so I'm
  pretty sure this is a duplicate of
  https://bugs.launchpad.net/ubuntu/+source/calamares/+bug/1864787

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: calamares 3.2.37-0ubuntu1
  ProcVersionSignature: Ubuntu 5.10.0-14.15-generic 5.10.11
  Uname: Linux 5.10.0-14-generic x86_64
  .etc.calamares.modules.finished.conf:
   ---
   restartNowMode: user-checked
   restartNowCommand: "systemctl -i reboot"
  .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-0ubuntu59
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CasperVersion: 1.458
  CurrentDesktop: LXQt
  Date: Thu Mar  4 18:34:54 2021
  LiveMediaBuild: Lubuntu 21.04 "Hirsute Hippo" - Alpha amd64 (20210303)
  RelatedPackageVersions:
   calamares-settings-ubuntu-common 1:21.04.2
   calamares-settings-lubuntu   1:21.04.2
   xfsprogs 5.10.0-2ubuntu3
   btrfs-progs  5.10.1-1build1
  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/1917724/+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 1923128] Re: command systemd-machine-id-setup finished with exist code 127 : lubuntu calamares install with existing partition:

2024-02-22 Thread Launchpad Bug Tracker
[Expired for calamares (Ubuntu) because there has been no activity for
60 days.]

** Changed in: calamares (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  command systemd-machine-id-setup finished with exist code 127 :
  lubuntu calamares install with existing partition:

Status in calamares package in Ubuntu:
  Expired

Bug description:
  Lubuntu hirsute daily QA-test install on
  - dell [optiplex] 780 (c2q-q9400, 8gb, amd/ati cedar radeon hd 
5000/6000/7350/8350)
  Testcase:  install with existing partition (ie. replace sda1 which was 18.04 
with 21.04)

  Calamares reported at "Finish" step of QA-test install

  ---
  "Installation Failed"
  External command finished with errors.
  Command systemd-machine-id-setup finished with exit code 127.
  Output:
  systemd-machine-id-setup: error while loading shared libraries: 
libsystemd-shared-247.so: cannot open shared object file: No such file or 
directory
  ---

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: calamares 3.2.37-0ubuntu1
  ProcVersionSignature: Ubuntu 5.11.0-13.14-generic 5.11.7
  Uname: Linux 5.11.0-13-generic x86_64
  .etc.calamares.modules.finished.conf:
   ---
   restartNowMode: user-checked
   restartNowCommand: "systemctl -i reboot"
  .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-0ubuntu62
  Architecture: amd64
  CasperMD5CheckResult: pass
  CasperVersion: 1.461
  CurrentDesktop: LXQt
  Date: Fri Apr  9 14:37:02 2021
  LiveMediaBuild: Lubuntu 21.04 "Hirsute Hippo" - Beta amd64 (20210408)
  RelatedPackageVersions:
   calamares-settings-ubuntu-common 1:21.04.2
   calamares-settings-lubuntu   1:21.04.2
   xfsprogs 5.10.0-2ubuntu3
   btrfs-progs  5.10.1-1build1
  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/1923128/+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 1904974] Re: calamares selected wrong timezone

2024-02-22 Thread Launchpad Bug Tracker
[Expired for calamares (Ubuntu) because there has been no activity for
60 days.]

** Changed in: calamares (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  calamares selected wrong timezone

Status in calamares package in Ubuntu:
  Expired

Bug description:
  Lubuntu hirsute daily install on dc7700 with internet

  https://ipapi.co/json reports
  ---

  ip"58.7.111.61"
  version   "IPv4"
  city  "Melbourne"
  region"Victoria"
  region_code   "VIC"
  country   "AU"
  country_name  "Australia"
  country_code  "AU"
  country_code_iso3 "AUS"
  country_capital   "Canberra"
  country_tld   ".au"
  continent_code"OC"
  in_eu false
  postal"3004"
  latitude  -37.8411
  longitude 144.9799
  timezone  "Australia/Melbourne"
  utc_offset"+1100"
  country_calling_code  "+61"
  currency  "AUD"
  currency_name "Dollar"
  languages "en-AU"
  country_area  7686850
  country_population24992369
  asn   "AS7545"
  org   "TPG Telecom Limited"
  ---

  However calamares on screen is showing my location as Perth (west side
  of aussieland, not east side; 3hrs out)

  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: Fri Nov 20 11:56:55 2020
  LiveMediaBuild: Lubuntu 21.04 "Hirsute Hippo" - Alpha amd64 (20201119)
  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/ubuntu/+source/calamares/+bug/1904974/+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 1923126] Re: current & after map in calamares doesn't change - lubuntu testcase: install with existing partition

2024-02-22 Thread Launchpad Bug Tracker
[Expired for calamares (Ubuntu) because there has been no activity for
60 days.]

** Changed in: calamares (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  current & after map in calamares doesn't change - lubuntu testcase:
  install with existing partition

Status in calamares package in Ubuntu:
  Expired

Bug description:
  Lubuntu hirsite daily QA-test install on 
  - dell [optiplex] 780 (c2q-q9400, 8gb, amd/ati cedar radeon hd 
5000/6000/7350/8350)

  Maybe loosely related to
  https://bugs.launchpad.net/ubuntu/+source/calamares/+bug/1888106

  Lubuntu QA-testcase: Install with existing partition

  ** Summary

  The partition map shown by `calamares` in the summary for CURRENT
  shows sda1 as containing Ubuntu 18.04.5 LTS (correctly), however so
  does it in the AFTER

  ** Expected Behavior

  The AFTER drive map should show the new install taking place on sda1,
  and the 18.04 system being overwritten by this new 21.04/hirsute
  install

  ** Actual Behavior

  The AFTER drive map still shows "Ubuntu 18.04.5 LTS (18.04)" as being
  on sda1; where it won't be on completion...

  This behavior only occurs as the partition is NOT formatted I believe.
  The consequence I believe to be minor, as it reports

  Flag partition /dev/sda1 as boot
  Install Lubuntu on ext4 system partition /dev/sda1
  Install boot loader on /dev/sda

  Photo : https://photos.app.goo.gl/uuiNsEJ3N1ULKhPV8

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: calamares 3.2.37-0ubuntu1
  ProcVersionSignature: Ubuntu 5.11.0-13.14-generic 5.11.7
  Uname: Linux 5.11.0-13-generic x86_64
  .etc.calamares.modules.finished.conf:
   ---
   restartNowMode: user-checked
   restartNowCommand: "systemctl -i reboot"
  .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-0ubuntu62
  Architecture: amd64
  CasperMD5CheckResult: pass
  CasperVersion: 1.461
  CurrentDesktop: LXQt
  Date: Fri Apr  9 14:15:01 2021
  LiveMediaBuild: Lubuntu 21.04 "Hirsute Hippo" - Beta amd64 (20210408)
  RelatedPackageVersions:
   calamares-settings-ubuntu-common 1:21.04.2
   calamares-settings-lubuntu   1:21.04.2
   xfsprogs 5.10.0-2ubuntu3
   btrfs-progs  5.10.1-1build1
  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/1923126/+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 1932236] Re: lubuntu - calamares doesn't cope well with ditherers

2024-02-22 Thread Launchpad Bug Tracker
[Expired for calamares (Ubuntu) because there has been no activity for
60 days.]

** Changed in: calamares (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  lubuntu - calamares doesn't cope well with ditherers

Status in calamares package in Ubuntu:
  Expired

Bug description:
  QA-test install to
  - hp dc7700 (c2d-e6320, 5gb, nvidia quadro nvs 290)
  testcase: install with existing partition, sda1

  I had a calamares failure whilst DITHERING on installer in focal.3
  daily install earlier; so I'll attempt to repeat my DITHERING here and
  see if calamares will crash here too... ie. exploration of
  http://launchpad.net/bugs/1932233

  ie. before get to "manual partitioning" I'll select REPLACE PARTITION,
  then select sda1, sda2, sda1, sda2, etc.

  I didn't have it crash, so switched it to "MANUAL PARTITIONING,
  changed my mind & back to "REPLACE PARTITION and back to selecting
  sda1, sda2, sda1 etc again & keep changing my mind...  (this switch to
  manual & back to replace partition may have been done twice)

  On final switch to MANUAL PARTITION calamares window just closes.

  Installed was started from menu (what I'm using today, did in focal.3
  too)

  
  This issue is of minor importance... if the OP does not dither so much, it 
won't occur... 

  (prior focal bug will be linked to this one)

  
  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: calamares 3.2.37-0ubuntu3
  ProcVersionSignature: Ubuntu 5.11.0-18.19+21.10.1-generic 5.11.17
  Uname: Linux 5.11.0-18-generic x86_64
  .etc.calamares.modules.finished.conf:
   ---
   restartNowMode: user-checked
   restartNowCommand: "systemctl -i reboot"
  .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-0ubuntu67
  Architecture: amd64
  CasperMD5CheckResult: pass
  CasperVersion: 1.462
  CurrentDesktop: LXQt
  Date: Thu Jun 17 13:35:44 2021
  LiveMediaBuild: Lubuntu 21.10 "Impish Indri" - Alpha amd64 (20210614)
  RelatedPackageVersions:
   calamares-settings-ubuntu-common 1:21.04.2
   calamares-settings-lubuntu   1:21.04.2
   xfsprogs 5.10.0-4ubuntu1
   btrfs-progs  5.10.1-2
  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/1932236/+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 1933614] Re: lubuntu qa-install; unknown crash (calamares just closed)

2024-02-22 Thread Launchpad Bug Tracker
[Expired for calamares (Ubuntu) because there has been no activity for
60 days.]

** Changed in: calamares (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  lubuntu qa-install; unknown crash (calamares just closed)

Status in calamares package in Ubuntu:
  Expired

Bug description:
  qa-test install on
  - sony vaio svp112a1cw (i5-9400u, 4gb, intel haswell-ULT)

  
  calamares window just closed 

  I looked and *calamares.crash existed in /var/crash/.

  I didn't ubuntu-bug that .crash file, I just entered `ubuntu-bug
  calamares`

  reboot & install looks good

  I don't see the issue, and wish I'd `ubuntu-bug /var/crash...`, as I
  only see

  2021-06-25 - 16:48:53 [6]: ..  Finished. Exit code: 0

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: calamares 3.2.37-0ubuntu3
  ProcVersionSignature: Ubuntu 5.11.0-20.21+21.10.1-generic 5.11.21
  Uname: Linux 5.11.0-20-generic x86_64
  .etc.calamares.modules.finished.conf:
   ---
   restartNowMode: user-checked
   restartNowCommand: "systemctl -i reboot"
  .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-0ubuntu67
  Architecture: amd64
  CasperMD5CheckResult: pass
  CasperVersion: 1.462
  CurrentDesktop: LXQt
  Date: Fri Jun 25 16:49:28 2021
  LiveMediaBuild: Lubuntu 21.10 "Impish Indri" - Alpha amd64 (20210624)
  RelatedPackageVersions:
   calamares-settings-ubuntu-common 1:21.04.2
   calamares-settings-lubuntu   1:21.04.2
   xfsprogs 5.10.0-4ubuntu1
   btrfs-progs  5.10.1-2
  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/1933614/+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 1945849] Re: lubuntu manual partitioning install - failed to create partition "Command: mkfs.ext4 -qF /dev/sda5"

2024-02-22 Thread Launchpad Bug Tracker
[Expired for calamares (Ubuntu) because there has been no activity for
60 days.]

** Changed in: calamares (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  lubuntu manual partitioning install - failed to create partition
  "Command: mkfs.ext4 -qF /dev/sda5"

Status in calamares package in Ubuntu:
  Expired

Bug description:
  Lubuntu impish daily install to 
  - hp dc7700 (c2d-e6320, 5gb, nvidia quadro nvs 290)

  testcase: custom, manual with separate /home

  In "Manual Partitioning" I shrank last (largest) partition & made new
  extend partition which contains / & /home.

  The disk is small on this box; and I didn't spend much time ensuring I
  have enough space (I expected it to work though; but will check after
  this is uploaded to exclude me-errors)

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: calamares 3.2.41.1-0ubuntu1
  ProcVersionSignature: Ubuntu 5.13.0-16.16-generic 5.13.13
  Uname: Linux 5.13.0-16-generic x86_64
  .etc.calamares.modules.finished.conf:
   ---
   restartNowMode: user-checked
   restartNowCommand: "systemctl -i reboot"
  .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-0ubuntu69
  Architecture: amd64
  CasperMD5CheckResult: pass
  CasperVersion: 1.465
  CurrentDesktop: LXQt
  Date: Sat Oct  2 16:47:21 2021
  LiveMediaBuild: Lubuntu 21.10 "Impish Indri" - Beta amd64 (20211001)
  RelatedPackageVersions:
   calamares-settings-ubuntu-common 1:21.10.2
   calamares-settings-lubuntu   1:21.10.2
   xfsprogs 5.10.0-4ubuntu1
   btrfs-progs  5.10.1-2
  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/1945849/+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 1960730] Re: calamares focal install to sony vaio - failure to boot

2024-02-22 Thread Launchpad Bug Tracker
[Expired for calamares (Ubuntu) because there has been no activity for
60 days.]

** Changed in: calamares (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  calamares focal install to sony vaio - failure to boot

Status in calamares package in Ubuntu:
  Expired

Bug description:
  QA-test install of Lubuntu focal.4 daily on
  - sony vaio svp112a1cw (i5-9400u, 4gb, intel haswell-ULT)
  testcase: full disk, encryption, internet, uEFI

  NOTE:   I didn't check SECURE-uEFI setting on device; so it was
  incorrectly set to SECURE

  ** expected result

  on reboot perform checks & record successful test (hopefully realize I
  had SECURE setting wrong too!)

  ** actual result

  on reboot

  "SECURE BOOT FAILED ; your VAIO has detected an invalid operating
  system"

  and various options such as go into BIOS/uEFI settings, reboot etc...

  

  The installed was re-attempted; same conditions however this time I
  ran `ubuntu-bug calamares` before reboot.  This second attempt
  resulted in identical failure.

  NOTE:  My intention was NOT SECURE-uEFI but I must have failed to
  switch Secure-boot OFF.. I think the last install attempted was Ubuntu
  ISO (exploration of bug 1960226) but it was a successful install (alas
  with the wrong ISO thus why install worked)

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: calamares 3.2.20-0ubuntu1
  ProcVersionSignature: Ubuntu 5.13.0-30.33~20.04.1-generic 5.13.19
  Uname: Linux 5.13.0-30-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-0ubuntu27.21
  Architecture: amd64
  CasperMD5CheckResult: pass
  CasperVersion: 1.445.1
  CurrentDesktop: LXQt
  Date: Sun Feb 13 14:49:30 2022
  LiveMediaBuild: Lubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220212)
  RelatedPackageVersions:
   calamares-settings-ubuntu-common 1:20.04.2.1
   calamares-settings-lubuntu   1:20.04.2.1
   xfsprogs 5.3.0-1ubuntu2
   btrfs-progs  5.4.1-2
  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/1960730/+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 1973469] Re: Lubuntu Kinetic installation crashes near the end on a system with a badly outdated clock

2024-02-22 Thread Launchpad Bug Tracker
[Expired for calamares (Ubuntu) because there has been no activity for
60 days.]

** Changed in: calamares (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  Lubuntu Kinetic installation crashes near the end on a system with a
  badly outdated clock

Status in calamares package in Ubuntu:
  Expired

Bug description:
  Test hardware is on an HP Elitebook 8570p, 16 GB RAM, 120 GB SSD.

  My Elitebook has a hardware problem that requires that I detach the
  CMOS battery and leave it that way in order for the system to
  function. Additionally, if I shut the system down, I have to leave it
  unplugged and with the battery removed, otherwise it won't boot when I
  go to turn it on next. (I think a thunderstorm fried a capacitor that
  had something to do with the CMOS, but anyway, weird as it may sound,
  that's the problem with my computer.)

  As a result, when I power my Elitebook on, it thinks that it's some
  time in the year 2000, which is about 22 years off.

  In addition, my Elitebook uses a Broadcom wireless chip, meaning that
  I have to connect to the Internet via Ethernet in order to install the
  driver for it. Since getting an Ethernet connection in my house is not
  so easy, I chose to simply perform the installation offline.

  At the very end of the installation, the installation failed, and I
  received the following error message:

  External command finished with errors.

  Command apt-get update finished with exit code 100.
  Output:
  Ign:1 cdrom://Lubuntu 22.10 _Kinetic Kudu_ - Alpha amd64 (20220514) 
kinetic InRelease
  Hit:2 cdrom://Lubuntu 22.10 _Kinetic Kudu_ - Alpha amd64 (20220514) 
kinetic Release
  /bin/tar: libreoffice-calc_libreoffice-calc.png: time stamp 2022-05-03 
18:02:43 is 1075359.205693822 s in the future
  /bin/tar: libreoffice-draw_libreoffice-draw.png: time stamp 2022-05-03 
18:02:44 is 1075360.20555066 s in the future
  Reading package lists...
  E: Release file for cdrom://Lubuntu 22.10 _Kinetic Kudu_ - Alpha amd64 
(20220514)/dists/kinetic/Release is not valid yet (invalid for another 18d 6h 
51min 33s). Updates for this repository will not be applied.

  The tar errors lead me to believe that this is a result of the out-of-
  date clock on my system. Furthermore, after connecting to the Internet
  to install the Broadcom drivers in the live environment and make the
  bug report, my clock is up-to-date, and I was able to install the
  system thereafter.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: calamares 3.2.41.1-0ubuntu5
  ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30
  Uname: Linux 5.15.0-27-generic x86_64
  NonfreeKernelModules: wl
  .etc.calamares.modules.finished.conf:
   ---
   restartNowMode: user-checked
   restartNowCommand: "systemctl -i reboot"
  .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-0ubuntu82
  Architecture: amd64
  CasperMD5CheckResult: pass
  CasperVersion: 1.470
  CurrentDesktop: LXQt
  Date: Sun May 15 11:26:02 2022
  LiveMediaBuild: Lubuntu 22.10 "Kinetic Kudu" - Alpha amd64 (20220514)
  RelatedPackageVersions:
   calamares-settings-ubuntu-common 1:22.10.1
   calamares-settings-lubuntu   1:22.10.1
   xfsprogs 5.13.0-1ubuntu3
   btrfs-progs  5.16.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/1973469/+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 1989165] Re: lubuntu calamares - replace partition (sda2) failed

2024-02-22 Thread Launchpad Bug Tracker
[Expired for calamares (Ubuntu) because there has been no activity for
60 days.]

** Changed in: calamares (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  lubuntu calamares - replace partition (sda2) failed

Status in calamares package in Ubuntu:
  Expired

Bug description:
  ** I encountered another older bug with the `ubuntu-bug calamares` so
  I've forgotten the issue & thus cannot select any existing bug
  report...  I'll amend this when I've refreshed memory by looking at
  calamares session.log

  hp8200 install using 'replace partition'  - sda2 was selected; EFI was
  detected & it reported it would re-use SDA1 as ESP (if I recall
  correctly)

  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: calamares 3.3.0-alpha2-0ubuntu2
  ProcVersionSignature: Ubuntu 5.19.0-15.15-generic 5.19.0
  Uname: Linux 5.19.0-15-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.23.0-0ubuntu1
  Architecture: amd64
  CasperMD5CheckResult: pass
  CasperVersion: 1.474
  CurrentDesktop: LXQt
  Date: Fri Sep  9 15:34:51 2022
  LiveMediaBuild: Lubuntu 22.10 "Kinetic Kudu" - Alpha amd64 (20220908)
  RelatedPackageVersions:
   calamares-settings-ubuntu-common 1:22.10.11
   calamares-settings-lubuntu   1:22.10.11
   xfsprogs 5.16.0-1ubuntu1
   btrfs-progs  5.19-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/1989165/+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 1993526] Re: lubuntu kinetic (install using existing partition) failure (again)

2024-02-22 Thread Launchpad Bug Tracker
[Expired for calamares (Ubuntu) because there has been no activity for
60 days.]

** Changed in: calamares (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  lubuntu kinetic (install using existing partition) failure (again)

Status in calamares package in Ubuntu:
  Expired

Bug description:
  lubuntu kinetic install to dell optiplex 755
  re-use / & /home (no format)

  package failure?

  this was last run on 12th October successfully (ISO 2022-10-11) so
  unexpected... but did I add packages or something post-install that
  has lead to this failure??  if so what???

  my aim is to explore this shortly; I'm still not yet convinced we have
  a problem yet; I'll try next on a different box with a cleaner setup
  (ie. known config)

  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: calamares 3.3.0-alpha2-0ubuntu2
  ProcVersionSignature: Ubuntu 5.19.0-21.21-generic 5.19.7
  Uname: Linux 5.19.0-21-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.23.1-0ubuntu3
  Architecture: amd64
  CasperMD5CheckResult: pass
  CasperVersion: 1.475
  CurrentDesktop: LXQt
  Date: Wed Oct 19 22:27:11 2022
  LiveMediaBuild: Lubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221017.1)
  RelatedPackageVersions:
   calamares-settings-ubuntu-common 1:22.10.12
   calamares-settings-lubuntu   1:22.10.12
   xfsprogs 5.16.0-1ubuntu1
   btrfs-progs  5.19-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/1993526/+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 2002122] Re: Fujitsu Siemens Amilo Calamares shows not full size of HDD in dropdown

2024-02-22 Thread Launchpad Bug Tracker
[Expired for calamares (Ubuntu) because there has been no activity for
60 days.]

** Changed in: calamares (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  Fujitsu Siemens Amilo Calamares shows not full size of HDD in dropdown

Status in calamares package in Ubuntu:
  Expired

Bug description:
  Calamares shows not full size of HDD in dropdown
  https://linux-hardware.org/?probe=4a918c5503

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: calamares 3.2.60-0ubuntu0.1
  ProcVersionSignature: Ubuntu 5.15.0-43.46-generic 5.15.39
  Uname: Linux 5.15.0-43-generic x86_64
  .etc.calamares.modules.finished.conf:
   ---
   restartNowMode: user-checked
   restartNowCommand: "systemctl -i reboot"
  .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-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: pass
  CasperVersion: 1.470
  CurrentDesktop: LXQt
  Date: Fri Jan  6 15:27:51 2023
  LiveMediaBuild: Lubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809)
  RelatedPackageVersions:
   calamares-settings-ubuntu-common 1:22.04.4.1
   calamares-settings-lubuntu   1:22.04.4.1
   xfsprogs 5.13.0-1ubuntu2
   btrfs-progs  5.16.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/2002122/+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 1994479] Re: calamares install failure; rsync error? d755-5 sda5 & sda6 (again)

2024-02-22 Thread Launchpad Bug Tracker
[Expired for calamares (Ubuntu) because there has been no activity for
60 days.]

** Changed in: calamares (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  calamares install failure; rsync error?  d755-5 sda5 & sda6 (again)

Status in calamares package in Ubuntu:
  Expired

Bug description:
  Lubuntu jammy install (using existing partition)

  install to
  - dell [optiplex] 755 (c2d-e6850, 5gb, amd/ati radeon rv516/x1300/x1550)
  re-use of sda6 (/) & sda7 (/home) WITHOUT FORMAT

  -- NOTE:

  the last install to this box (kinetic/22.10 to these partitions)
  failed and I've not yet resolved that, thus this failure may NOT be
  related to [new] calamares issue at all; I'll re-do this test using
  sda8 & sda9 to confirm that and expect that to work.   This maybe red-
  herring, but may also give me more clues to finding what is wrong
  (with with kinetic failure to install)

  this failure does NOT concern me re: SRU's calamares...

  I'll only worry if the install fails on a working system I've yet to
  test.

  Rsync error message surprised, but prior fails appear related to
  package issues

  Kinetic failure is recorded here -
  https://bugs.launchpad.net/ubuntu/+source/calamares/+bug/1993526 but
  install was fine on other boxes (and worked perfectly same partitions
  on kinetic 12-October-2022 using 20221011 ISO)

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: calamares 3.2.61-0ubuntu0.1
  ProcVersionSignature: Ubuntu 5.15.0-53.59-generic 5.15.64
  Uname: Linux 5.15.0-53-generic x86_64
  .etc.calamares.modules.finished.conf:
   ---
   restartNowMode: user-checked
   restartNowCommand: "systemctl -i reboot"
  .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-0ubuntu82.2
  Architecture: amd64
  CasperMD5CheckResult: pass
  CasperVersion: 1.470.1
  CurrentDesktop: LXQt
  Date: Wed Oct 26 16:47:14 2022
  LiveMediaBuild: Lubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20221025.1)
  RelatedPackageVersions:
   calamares-settings-ubuntu-common 1:22.04.4.2
   calamares-settings-lubuntu   1:22.04.4.2
   xfsprogs 5.13.0-1ubuntu2
   btrfs-progs  5.16.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/1994479/+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 2002126] Re: Bootloaded wants to install usb even when selected HDD in Manual mode

2024-02-22 Thread Launchpad Bug Tracker
[Expired for calamares (Ubuntu) because there has been no activity for
60 days.]

** Changed in: calamares (Ubuntu)
   Status: Incomplete => Expired

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

Title:
   Bootloaded wants to install usb even when selected HDD  in Manual
  mode

Status in calamares package in Ubuntu:
  Expired

Bug description:
   Bootloaded wants to install usb even when selected HDD  in Manual
  mode

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: calamares 3.2.60-0ubuntu0.1
  ProcVersionSignature: Ubuntu 5.15.0-43.46-generic 5.15.39
  Uname: Linux 5.15.0-43-generic x86_64
  .etc.calamares.modules.finished.conf:
   ---
   restartNowMode: user-checked
   restartNowCommand: "systemctl -i reboot"
  .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-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: pass
  CasperVersion: 1.470
  CurrentDesktop: LXQt
  Date: Fri Jan  6 15:33:57 2023
  LiveMediaBuild: Lubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809)
  RelatedPackageVersions:
   calamares-settings-ubuntu-common 1:22.04.4.1
   calamares-settings-lubuntu   1:22.04.4.1
   xfsprogs 5.13.0-1ubuntu2
   btrfs-progs  5.16.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/2002126/+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 2003157] Re: lubuntu calamares install; calamares window just closed

2024-02-22 Thread Launchpad Bug Tracker
[Expired for calamares (Ubuntu) because there has been no activity for
60 days.]

** Changed in: calamares (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  lubuntu calamares install; calamares window just closed

Status in calamares package in Ubuntu:
  Expired

Bug description:
  Lubuntu jammy.2 daily install on
  - lenovo g560 (i5m-480, 4gb, i915)

  install alongside; selected large windows partition to shrink...

  install appeared to be going normally, without message the laptop
  screen returned to wallpaper (calamares crashed)

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: calamares 3.2.61-0ubuntu0.1
  ProcVersionSignature: Ubuntu 5.15.0-59.65-generic 5.15.78
  Uname: Linux 5.15.0-59-generic x86_64
  .etc.calamares.modules.finished.conf:
   ---
   restartNowMode: user-checked
   restartNowCommand: "systemctl -i reboot"
  .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-0ubuntu82.3
  Architecture: amd64
  CasperMD5CheckResult: pass
  CasperVersion: 1.470.1
  CurrentDesktop: LXQt
  Date: Mon Nov 10 03:26:25 2025
  LiveMediaBuild: Lubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20230117)
  RelatedPackageVersions:
   calamares-settings-ubuntu-common 1:22.04.4.2
   calamares-settings-lubuntu   1:22.04.4.2
   xfsprogs 5.13.0-1ubuntu2
   btrfs-progs  5.16.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/2003157/+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 2007559] Re: lubuntu 22.04 daily QA-test install; calamares just closed

2024-02-22 Thread Launchpad Bug Tracker
[Expired for calamares (Ubuntu) because there has been no activity for
60 days.]

** Changed in: calamares (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  lubuntu 22.04 daily QA-test install; calamares just closed

Status in calamares package in Ubuntu:
  Expired

Bug description:
  Lubuntu 22.04 LTS QA-test install of daily

  
  Using calamares; and got to the user dialog (my name, username password etc) 
and my operation of mouse wasn't as intended (ie. user error) and the screen 
just bypassed that screen and went to a blank summary of install screen???

  I don't know what I hit with mouse (I think button was pushed by
  object when I didn't want) that caused the blank calamares summary
  screen; but I hit back to return & enter details.

  On hitting back; it went back to the user dialog as hoped, however
  here when I tried to enter my details calamares just closed... Crash
  report found in /var/crash.

  install on hp dc7700  (install alongside testcase)

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: calamares 3.2.61-0ubuntu0.1
  ProcVersionSignature: Ubuntu 5.19.0-32.33~22.04.1-generic 5.19.17
  Uname: Linux 5.19.0-32-generic x86_64
  .etc.calamares.modules.finished.conf:
   ---
   restartNowMode: user-checked
   restartNowCommand: "systemctl -i reboot"
  .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-0ubuntu82.3
  Architecture: amd64
  CasperMD5CheckResult: pass
  CasperVersion: 1.470.2
  CurrentDesktop: LXQt
  Date: Thu Feb 16 21:10:29 2023
  LiveMediaBuild: Lubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 
(20230215)
  RelatedPackageVersions:
   calamares-settings-ubuntu-common 1:22.04.4.2
   calamares-settings-lubuntu   1:22.04.4.2
   xfsprogs 5.13.0-1ubuntu2
   btrfs-progs  5.16.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/2007559/+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 2022287] Re: lubuntu mantic install (unclean) over ubuntu desktop

2024-02-22 Thread Launchpad Bug Tracker
[Expired for calamares (Ubuntu) because there has been no activity for
60 days.]

** Changed in: calamares (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  lubuntu mantic install (unclean) over ubuntu desktop

Status in calamares package in Ubuntu:
  Expired

Bug description:
  THIS INSTALL MOSTLY WORKED, so very minor.  Problem encountered was

  - unclear error message from calamares (just error & close); the major
  issue I suspect; yet install worked booted & two OSes could be
  selected; mostly worked

  I'll do some more installs of this type (unclean install) so this
  report could be marked as incomplete (waiting for me to get to that &
  see how severe etc)

  ---

  qa-test install to
  - hp dc7700 (c2d-e6320, 8gb amd/ati rv610/radeon hd2400 pro/xt)
  testcase: install using existing partition (sda6 or whatever I last used 
yesterday)

  (two installs on box; lunar ubuntu-mate & mantic ubuntu-desktop; I'm
  selecting the ubuntu-desktop partition which has additional packages &
  music installed)

  possibly of interest; ubuntu-desktop installed to two partitions being
  / & ESP; I only selected the / partition of lubuntu mantic & this
  install

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: calamares 3.3.0-alpha2-0ubuntu4
  ProcVersionSignature: Ubuntu 6.2.0-21.21-generic 6.2.6
  Uname: Linux 6.2.0-21-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.26.1-0ubuntu3
  Architecture: amd64
  CasperMD5CheckResult: pass
  CasperVersion: 1.481
  CurrentDesktop: LXQt
  Date: Fri Jun  2 13:56:27 2023
  LiveMediaBuild: Lubuntu 23.10 "Mantic Minotaur" - Daily amd64 (20230530)
  RelatedPackageVersions:
   calamares-settings-ubuntu-common 1:23.04.12
   calamares-settings-lubuntu   1:23.04.12
   xfsprogs 6.1.0-1ubuntu1
   btrfs-progs  6.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/2022287/+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 2028334] Re: lubuntu mantic install (replace partition) create new partition fail

2024-02-22 Thread Launchpad Bug Tracker
[Expired for calamares (Ubuntu) because there has been no activity for
60 days.]

** Changed in: calamares (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  lubuntu mantic install (replace partition) create new partition fail

Status in calamares package in Ubuntu:
  Expired

Bug description:
  Lubuntu mantic (daily) install to
  - hp dc7700 (c2d-e6230, 7gb amd/ati rv610/radeon hd2400 pro/xt)

  The box had 2x installs
  - Ubuntu Desktop (mantic: installed yesterday if I remember correctly)
  - Xubuntu mantic (mantic; not recent; but still not that long ago)

  I didn't boot & confirm which was on first partition & which was
  second..

  ** Testcase

  Replace partition; i just selected partition to re-use & provided name
  etc

  ** Expected Result

  New install with new Lubuntu mantic & either Ubuntu/Xubuntu mantic on
  other  (xubuntu install is perfect xubuntu; if ubuntu.desktop survived
  it'll get to gdm3 correctly which would have been pass for me for this
  test)

  ** Actual Result

  Installation Failed

  The installer failed to create partition on disk 'WDC WD800JD-60LSA5'
  Details:

  Create a new partition (30.53 GiB, ext4) on ‘/dev/sda’

  Job: Create new partition on device ‘/dev/sda’

  ** Of note

  Whilst I've not had any issues with Xubuntu during the mantic cycle; I
  HAVE HAD issues with Ubuntu Desktop that leaves the GUI black-locked..
  Whilst I always endeavor to SysRq REISUO/REISUB so file-system is left
  clean; maybe I didn't? which led to this??

  I don't believe that is the issue, but either way - on only a single
  FAIL currently; to me this issue isn't worth spending much effort on
  (currently anyway)..  as I'll be encountering this numerous times on
  this box (and don't intend re-using this box on Ubuntu Desktop much
  anymore whilst it has this video card)

  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.26.1-0ubuntu3
  Architecture: amd64
  CasperMD5CheckResult: pass
  CasperVersion: 1.481
  CurrentDesktop: LXQt
  Date: Fri Jul 21 16:17:20 2023
  LiveMediaBuild: Lubuntu 23.10 "Mantic Minotaur" - Daily amd64 (20230720)
  RelatedPackageVersions:
   calamares-settings-ubuntu-common 1:23.04.12
   calamares-settings-lubuntu   1:23.04.12
   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/2028334/+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 2036699] Re: lubuntu mantic install; full disk no encryption (flaky internet) on BIOS (dc7700)

2024-02-22 Thread Launchpad Bug Tracker
[Expired for calamares (Ubuntu) because there has been no activity for
60 days.]

** Changed in: calamares (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  lubuntu mantic install; full disk no encryption (flaky internet) on
  BIOS (dc7700)

Status in calamares package in Ubuntu:
  Expired

Bug description:
  Lubuntu mantic install on
  - hp dc7700 (c2d-e6320, 8gb amd/ati rv610/radeon hd2400 pro/xt)

  I didn't expect issues... My internet is flaky (so I'll need to check that 
wasn't the cause) given a full disk install without encryption, but installed 
reported failure..
  (Note install mostly worked; booted & looked good)

  old legacy BIOS box

  INSTALLED ABENDED (abnormal-end)

  ---
  Command calamares-logs-helper /tmp/calamares-root-nbye456p finished 
with exit code 1.
  Output:
  + root=/tmp/calamares-root-nbye456p
  + install_dir=/tmp/calamares-root-nbye456p/var/log/installer
  + [ -d /tmp/calamares-root-nbye456p/var/log/installer ]
  + mkdir -p /tmp/calamares-root-nbye456p/var/log/installer
  + cp /root/.cache/calamares/session.log 
/tmp/calamares-root-nbye456p/var/log/installer/debug
  cp: cannot stat '/root/.cache/calamares/session.log': No such file or 
directory
  ---

  on reboot; the system booted & auto-logged in (I used that option I
  believe so expected)... the installed system looked good actually !!

  general look at file-system, and it looks like a valid install HOWEVER
  not all is there; /var/log/installer/ is EMPTY so no mediainfo for me
  to check etc...  installer didn't complete tasks

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: calamares 3.3.0-alpha2-0ubuntu5
  ProcVersionSignature: Ubuntu 6.5.0-5.5-generic 6.5.0
  Uname: Linux 6.5.0-5-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 Sep 20 16:58:49 2023
  LiveMediaBuild: Lubuntu 23.10 "Mantic Minotaur" - Beta amd64 (20230919)
  RelatedPackageVersions:
   calamares-settings-ubuntu-common 1:23.10.3
   calamares-settings-lubuntu   1:23.10.3
   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/2036699/+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 2042911] Re: Calamares fails -External command finished with errors

2024-02-22 Thread Launchpad Bug Tracker
[Expired for calamares (Ubuntu) because there has been no activity for
60 days.]

** Changed in: calamares (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  Calamares fails -External command finished with errors

Status in calamares package in Ubuntu:
  Expired

Bug description:
  Calamares fails -External command finished with errors

  Testing Lubuntu Noble daily ISO dated 06-11-2023 machine running in
  UEFI+secure boot mode

  see attached screenshot

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: calamares 3.3.0-alpha4-0ubuntu1
  ProcVersionSignature: Ubuntu 6.5.0-9.9-generic 6.5.3
  Uname: Linux 6.5.0-9-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-0ubuntu5
  Architecture: amd64
  CasperMD5CheckResult: pass
  CasperVersion: 1.486
  CurrentDesktop: LXQt
  Date: Tue Nov  7 08:16:58 2023
  LiveMediaBuild: Lubuntu 24.04 "Noble Numbat" - Daily amd64 (20231106)
  RelatedPackageVersions:
   calamares-settings-ubuntu-common 1:23.10.4
   calamares-settings-lubuntu   1:23.10.4
   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/2042911/+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 2038254] Re: lubuntu mantic ; third install that has had me in new york (today)

2024-02-22 Thread Launchpad Bug Tracker
[Expired for calamares (Ubuntu) because there has been no activity for
60 days.]

** Changed in: calamares (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  lubuntu mantic ; third install that has had me in new york (today)

Status in calamares package in Ubuntu:
  Expired

Bug description:
  Install on
  - hp dc7700 (c2d-e6320, 8gb amd/ati rv610/radeon hd2400 pro/xt)

  https://ipapi.co/json reports my address as

  ---
  ip"220.235.233.145"
  network   "220.235.232.0/21"
  version   "IPv4"
  city  "Melbourne"
  region"Victoria"
  region_code   "VIC"
  country   "AU"
  country_name  "Australia"
  country_code  "AU"
  country_code_iso3 "AUS"
  country_capital   "Canberra"
  country_tld   ".au"
  continent_code"OC"
  in_eu false
  postal"3000"
  latitude  -37.8159
  longitude 144.9669
  timezone  "Australia/Melbourne"
  utc_offset"+1100"
  country_calling_code  "+61"
  currency  "AUD"
  currency_name "Dollar"
  languages "en-AU"
  country_area  7686850
  country_population24992369
  asn   "AS7545"
  org   "TPG Telecom Limited"
  ---

  Three installs thus far today on this box, all has had calamares
  suggest me as being at New York USA.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: calamares 3.3.0-alpha2-0ubuntu5
  ProcVersionSignature: Ubuntu 6.5.0-5.5-generic 6.5.0
  Uname: Linux 6.5.0-5-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-0ubuntu3
  Architecture: amd64
  CasperMD5CheckResult: pass
  CasperVersion: 1.484
  CurrentDesktop: LXQt
  Date: Tue Oct  3 14:54:15 2023
  LiveMediaBuild: Lubuntu 23.10 "Mantic Minotaur" - Daily amd64 (20231002)
  RelatedPackageVersions:
   calamares-settings-ubuntu-common 1:23.10.3
   calamares-settings-lubuntu   1:23.10.3
   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/2038254/+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 2046844] Re: AppArmor user namespace creation restrictions cause many applications to crash with SIGTRAP

2024-02-21 Thread Launchpad Bug Tracker
This bug was fixed in the package plasma-welcome - 5.27.10-1ubuntu1

---
plasma-welcome (5.27.10-1ubuntu1) noble; urgency=low

  [ Ubuntu Merge-o-Matic ]
  * Merge from Debian unstable. Remaining changes:
- Kubuntu Vcs and maintainer fields.

  [ Scarlett Moore ]
  * Add apparmor profile to fix userns. Ref: LP: #2046844
  * Release to archive.

plasma-welcome (5.27.10-1) unstable; urgency=medium

  [ Patrick Franz ]
  * New upstream release (5.27.10).

 -- Scarlett Moore   Wed, 21 Feb 2024 04:23:15 -0700

** Changed in: plasma-welcome (Ubuntu)
   Status: In Progress => Fix Released

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

Title:
  AppArmor user namespace creation restrictions cause many applications
  to crash with SIGTRAP

Status in akonadiconsole package in Ubuntu:
  In Progress
Status in akregator package in Ubuntu:
  Fix Released
Status in angelfish package in Ubuntu:
  In Progress
Status in apparmor package in Ubuntu:
  Fix Released
Status in bubblewrap package in Ubuntu:
  Confirmed
Status in cantor package in Ubuntu:
  Fix Released
Status in devhelp package in Ubuntu:
  Fix Released
Status in digikam package in Ubuntu:
  Fix Released
Status in epiphany-browser package in Ubuntu:
  Fix Released
Status in evolution package in Ubuntu:
  Fix Released
Status in falkon package in Ubuntu:
  Fix Released
Status in freecad package in Ubuntu:
  Confirmed
Status in ghostwriter package in Ubuntu:
  Fix Committed
Status in gnome-packagekit package in Ubuntu:
  Confirmed
Status in goldendict-webengine package in Ubuntu:
  Confirmed
Status in kalgebra package in Ubuntu:
  Fix Released
Status in kchmviewer package in Ubuntu:
  Confirmed
Status in kdeplasma-addons package in Ubuntu:
  Confirmed
Status in kgeotag package in Ubuntu:
  In Progress
Status in kiwix package in Ubuntu:
  Confirmed
Status in kmail package in Ubuntu:
  Fix Released
Status in konqueror package in Ubuntu:
  Fix Released
Status in kontact package in Ubuntu:
  Fix Released
Status in marble package in Ubuntu:
  Fix Released
Status in notepadqq package in Ubuntu:
  Confirmed
Status in opam package in Ubuntu:
  Fix Released
Status in pageedit package in Ubuntu:
  Confirmed
Status in plasma-desktop package in Ubuntu:
  Confirmed
Status in plasma-welcome package in Ubuntu:
  Fix Released
Status in privacybrowser package in Ubuntu:
  Confirmed
Status in qmapshack package in Ubuntu:
  Confirmed
Status in qutebrowser package in Ubuntu:
  Confirmed
Status in rssguard package in Ubuntu:
  Confirmed
Status in steam package in Ubuntu:
  Fix Committed
Status in supercollider package in Ubuntu:
  Confirmed
Status in tellico package in Ubuntu:
  Fix Released

Bug description:
  Hi, I run Ubuntu development branch 24.04 and I have a problem with
  Epiphany browser 45.1-1 (Gnome Web): program doesn't launch, and I get
  this error

  $ epiphany
  bwrap: Creating new namespace failed: Permission denied

  ** (epiphany:12085): ERROR **: 14:44:35.023: Failed to fully launch 
dbus-proxy: Le processus fils s’est terminé avec le code 1
  Trappe pour point d'arrêt et de trace (core dumped)

  $ epiphany
  bwrap: Creating new namespace failed: Permission denied

  ** (epiphany:30878): ERROR **: 22:22:26.926: Failed to fully launch 
dbus-proxy: Le processus fils s’est terminé avec le code 1
  Trappe pour point d'arrêt et de trace (core dumped)

  Thanks for your help!

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/akonadiconsole/+bug/2046844/+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 2046844] Re: AppArmor user namespace creation restrictions cause many applications to crash with SIGTRAP

2024-02-15 Thread Launchpad Bug Tracker
This bug was fixed in the package apparmor - 4.0.0~alpha4-0ubuntu1

---
apparmor (4.0.0~alpha4-0ubuntu1) noble; urgency=medium

  [Georgia Garcia]
  * New upstream release.
  * Add unconfined profiles to support the use unprivileged user namespace
(LP: #2052297, LP: #2046844)
- d/p/u/add-keybase-unconfined-profile.patch
- d/p/u/add-more-unconfined-profiles.patch
  * Fix regression tests failures on regex.sh, exec.sh and userns.sh
- d/p/u/tests-fix-usr-merge-failures-on-exec-and-regex-tests.patch
- d/p/u/tests-handle-unprivileged_userns-transition-in-usern.patch
  * Drop patches which have now been applied upstream
- d/p/u/userns-unconfined-profiles.patch
- d/p/u/tests-fix-userns-setns-opening-pipe-order.patch
- d/p/u/tests-replace-individual-socket-permissions.patch
- d/p/u/tests-fix-test-specifying-path-on-attach-disconnected.patch
- d/p/u/binutils-aa_status.c-quiet-verbose-outputs-when-json.patch
- d/p/u/oot-unconfined-profiles.patch
  * Refresh patches
- d/p/d/etc-writable.patch
- d/p/u/profiles-grant-access-to-systemd-resolved.patch
- d/p/u/userns-runtime-disable.patch
  * d/apparmor.install
- install new profiles
  - plasmashell
  - surfshark
  - unprivileged_userns
  - keybase
  - devhelp
  - epiphany
  - evolution
  - opam
- renamed profiles
  - ch-checkns
  - ch-run
  - crun
  - flatpak
  - linux-sandbox
  - busybox
  - buildah
  - cam
  - ipa_verify
  - lc-compliance
  - libcamerify
  - qcam
  - podman
  - lxc-attach
  - lxc-create
  - lxc-destroy
  - lxc-execute
  - lxc-stop
  - lxc-unshare
  - lxc-usernsexec
  - mmdebstrap
  - vpnns
  - QtWebEngineProcess
  - systemd-coredump
  - rootlesskit
  - rpm
  - runc
  - virtiofsd
  - sbuild
  - sbuild-abort
  - sbuild-adduser
  - sbuild-apt
  - sbuild-checkpackages
  - sbuild-clean
  - sbuild-createchroot
  - sbuild-destroychroot
  - sbuild-distupgrade
  - sbuild-hold
  - sbuild-shell
  - sbuild-unhold
  - sbuild-update
  - sbuild-upgrade
  - slirp4netns
  - stress-ng
  - thunderbird
  - toybox
  - trinity
  - tup
  - userbindmount
  - uwsgi-core
  - vdens
  - chrome
  - msedge
  - brave
  - vivaldi-bin
  * d/apparmor.maintscript
- add renamed profiles so they are removed on upgrade
  * d/libapache2-mod-apparmor.install
- remove etc/apparmor.d/local/usr.sbin.apache2, no longer needed

  [John Johansen]
  * debian/rules:
- don't run debian/put-all-profiles-in-complain-mode.sh on install

  [Alex Murray]
  * debian/apparmor.lintian-overrides:
- suppress false-positive warning about needing a Depends: on adduser
  for the apparmor binary package

 -- Georgia Garcia   Fri, 02 Feb 2024
16:12:21 -0300

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

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

Title:
  AppArmor user namespace creation restrictions cause many applications
  to crash with SIGTRAP

Status in akregator package in Ubuntu:
  Fix Released
Status in angelfish package in Ubuntu:
  In Progress
Status in apparmor package in Ubuntu:
  Fix Released
Status in bubblewrap package in Ubuntu:
  Confirmed
Status in cantor package in Ubuntu:
  Fix Released
Status in devhelp package in Ubuntu:
  Confirmed
Status in digikam package in Ubuntu:
  Fix Released
Status in epiphany-browser package in Ubuntu:
  Confirmed
Status in evolution package in Ubuntu:
  Confirmed
Status in falkon package in Ubuntu:
  Fix Released
Status in freecad package in Ubuntu:
  Confirmed
Status in ghostwriter package in Ubuntu:
  Fix Released
Status in gnome-packagekit package in Ubuntu:
  Confirmed
Status in goldendict-webengine package in Ubuntu:
  Confirmed
Status in kalgebra package in Ubuntu:
  Fix Released
Status in kchmviewer package in Ubuntu:
  Confirmed
Status in kdeplasma-addons package in Ubuntu:
  Confirmed
Status in kgeotag package in Ubuntu:
  In Progress
Status in kiwix package in Ubuntu:
  Confirmed
Status in kmail package in Ubuntu:
  Fix Released
Status in konqueror package in Ubuntu:
  Fix Released
Status in kontact package in Ubuntu:
  Fix Released
Status in marble package in Ubuntu:
  Fix Released
Status in notepadqq package in Ubuntu:
  Confirmed
Status in opam package in Ubuntu:
  Confirmed
Status in pageedit package in Ubuntu:
  Confirmed
Status in plasma-desktop package in Ubuntu:
  Confirmed
Status in plasma-welcome package in Ubuntu:
  In Progress
Status in privacybrowser package in Ubuntu:
  Confirmed
Status in qmapshack package in Ubuntu:
  Confirmed
Status in qutebrowser package in Ubuntu:
  Confirmed
Status in rssguard package in Ubuntu:
  Confirmed
Status in steam 

[Ubuntustudio-bugs] [Bug 2047656] Re: [SRU] Players terminate after stopping and restarting

2024-01-22 Thread Launchpad Bug Tracker
This bug was fixed in the package fluidsynth - 2.3.3-2.1ubuntu0.23.10.1

---
fluidsynth (2.3.3-2.1ubuntu0.23.10.1) mantic; urgency=medium

  * Patch to fix player termination after stopping and restarting (LP:
#2047656)

 -- Erich Eickmeyer   Wed, 03 Jan 2024 09:39:14
-0800

** Changed in: fluidsynth (Ubuntu Mantic)
   Status: Fix Committed => Fix Released

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

Title:
  [SRU] Players terminate after stopping and restarting

Status in fluidsynth package in Ubuntu:
  Fix Released
Status in fluidsynth source package in Mantic:
  Fix Released
Status in fluidsynth source package in Noble:
  Fix Released

Bug description:
  [ Impact ]

  Fluidsynth 2.3.3 has an issue where it will terminate upon start/stop
  of playback of a midi song, causing issues for a multitude of players
  including EasyABC. This will cause said player to be unable to
  playback again and perhaps even crash. See
  https://github.com/FluidSynth/fluidsynth/issues/1272, fix in
  
https://github.com/FluidSynth/fluidsynth/commit/377ab9db2f87bc407eeb940e0361edc77da77055.
  This is the included patch with the upload of
  2.3.3-2.1ubuntu-0.23.10.1

  [ Test Case ]

  * To reproduce the bug:

  # download sample midi file from wikiepdia:

  wget
  https://upload.wikimedia.org/wikipedia/commons/5/55/MIDI_sample.mid

  # play it with fluidsynth

  fluidsynth MIDI_sample.mid

  # at this point, you will actually be at a prompt. Wait for the song
  to play for a few seconds, then issue a stop command at that prompt:

  player_stop

  # And this is where the bug happens. Issue a continuation:

  player_cont

  And this is where things break:

  > player_cont
  > fluidsynth: error: The maximum playback duration has been reached. 
Terminating player!

  * With the fixed package, the audio resumes playback.

  [ What could go wrong ]

  This is actually a fix for a regression that was found in version
  2.3.3 of fluidsynth and fixed for 2.3.4, which can be found in noble.
  I think the only thing that can go wrong here is that this patch is
  not the actual fix and we need to find more solutions within.

  I have tested this in my PPA and it *seems* to fix it, but it would be
  nice if the original reporter could verify once this lands in
  proposed.

  [ Other information ]

  Included below is the original report, in which case the reporter
  deduces that the problem is the binary being spat-out is the 2.3.2
  version from the 2.3.3 sources. This is not the case, as it appears to
  be confusion due to the -2.1 Debian revision number. I assure, this is
  definitely the 2.3.3, and the bug, per the github link in the Impact
  section, is pertinent to this version.

  ---

  The latest package of fluidsynth should include the sources from
  version 2.3.3 but the binary includes only version 2.3.2

  This version has a bug (see
  https://github.com/FluidSynth/fluidsynth/issues/1272), which leads to
  problems in EasyABC.

  Please include the latest version 2.3.3 from upstream in the ubuntu
  package.

  --

  Description:  Ubuntu 23.10
  Release:  23.10
  Codename: mantic

  $ apt-cache policy libfluidsynth3
  libfluidsynth3:
    Installiert:   2.3.3-2.1
    Installationskandidat: 2.3.3-2.1
    Versionstabelle:
   *** 2.3.3-2.1 500
  500 http://de.archive.ubuntu.com/ubuntu mantic/universe amd64 Packages
  100 /var/lib/dpkg/status

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fluidsynth/+bug/2047656/+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 2046844] Re: AppArmor user namespace creation restrictions cause many applications to crash with SIGTRAP

2024-01-04 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: steam (Ubuntu)
   Status: New => Confirmed

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

Title:
  AppArmor user namespace creation restrictions cause many applications
  to crash with SIGTRAP

Status in apparmor package in Ubuntu:
  Confirmed
Status in bubblewrap package in Ubuntu:
  Confirmed
Status in devhelp package in Ubuntu:
  Confirmed
Status in digikam package in Ubuntu:
  Confirmed
Status in epiphany-browser package in Ubuntu:
  Confirmed
Status in evolution package in Ubuntu:
  Confirmed
Status in falkon package in Ubuntu:
  Confirmed
Status in freecad package in Ubuntu:
  Confirmed
Status in gnome-packagekit package in Ubuntu:
  Confirmed
Status in kdeplasma-addons package in Ubuntu:
  Confirmed
Status in kontact package in Ubuntu:
  Confirmed
Status in plasma-desktop package in Ubuntu:
  Confirmed
Status in qutebrowser package in Ubuntu:
  Confirmed
Status in steam package in Ubuntu:
  Confirmed

Bug description:
  Hi, I run Ubuntu development branch 24.04 and I have a problem with
  Epiphany browser 45.1-1 (Gnome Web): program doesn't launch, and I get
  this error

  $ epiphany
  bwrap: Creating new namespace failed: Permission denied

  ** (epiphany:12085): ERROR **: 14:44:35.023: Failed to fully launch 
dbus-proxy: Le processus fils s’est terminé avec le code 1
  Trappe pour point d'arrêt et de trace (core dumped)

  $ epiphany
  bwrap: Creating new namespace failed: Permission denied

  ** (epiphany:30878): ERROR **: 22:22:26.926: Failed to fully launch 
dbus-proxy: Le processus fils s’est terminé avec le code 1
  Trappe pour point d'arrêt et de trace (core dumped)

  Thanks for your help!

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/2046844/+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 2046844] Re: AppArmor user namespace creation restrictions cause many applications to crash with SIGTRAP

2024-01-04 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: devhelp (Ubuntu)
   Status: New => Confirmed

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

Title:
  AppArmor user namespace creation restrictions cause many applications
  to crash with SIGTRAP

Status in apparmor package in Ubuntu:
  Confirmed
Status in bubblewrap package in Ubuntu:
  Confirmed
Status in devhelp package in Ubuntu:
  Confirmed
Status in digikam package in Ubuntu:
  Confirmed
Status in epiphany-browser package in Ubuntu:
  Confirmed
Status in evolution package in Ubuntu:
  Confirmed
Status in falkon package in Ubuntu:
  Confirmed
Status in freecad package in Ubuntu:
  Confirmed
Status in gnome-packagekit package in Ubuntu:
  Confirmed
Status in kdeplasma-addons package in Ubuntu:
  Confirmed
Status in kontact package in Ubuntu:
  Confirmed
Status in plasma-desktop package in Ubuntu:
  Confirmed
Status in qutebrowser package in Ubuntu:
  Confirmed
Status in steam package in Ubuntu:
  Confirmed

Bug description:
  Hi, I run Ubuntu development branch 24.04 and I have a problem with
  Epiphany browser 45.1-1 (Gnome Web): program doesn't launch, and I get
  this error

  $ epiphany
  bwrap: Creating new namespace failed: Permission denied

  ** (epiphany:12085): ERROR **: 14:44:35.023: Failed to fully launch 
dbus-proxy: Le processus fils s’est terminé avec le code 1
  Trappe pour point d'arrêt et de trace (core dumped)

  $ epiphany
  bwrap: Creating new namespace failed: Permission denied

  ** (epiphany:30878): ERROR **: 22:22:26.926: Failed to fully launch 
dbus-proxy: Le processus fils s’est terminé avec le code 1
  Trappe pour point d'arrêt et de trace (core dumped)

  Thanks for your help!

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/2046844/+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 2046844] Re: AppArmor user namespace creation restrictions cause many applications to crash with SIGTRAP

2024-01-04 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: bubblewrap (Ubuntu)
   Status: New => Confirmed

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

Title:
  AppArmor user namespace creation restrictions cause many applications
  to crash with SIGTRAP

Status in apparmor package in Ubuntu:
  Confirmed
Status in bubblewrap package in Ubuntu:
  Confirmed
Status in devhelp package in Ubuntu:
  Confirmed
Status in digikam package in Ubuntu:
  Confirmed
Status in epiphany-browser package in Ubuntu:
  Confirmed
Status in evolution package in Ubuntu:
  Confirmed
Status in falkon package in Ubuntu:
  Confirmed
Status in freecad package in Ubuntu:
  Confirmed
Status in gnome-packagekit package in Ubuntu:
  Confirmed
Status in kdeplasma-addons package in Ubuntu:
  Confirmed
Status in kontact package in Ubuntu:
  Confirmed
Status in plasma-desktop package in Ubuntu:
  Confirmed
Status in qutebrowser package in Ubuntu:
  Confirmed
Status in steam package in Ubuntu:
  Confirmed

Bug description:
  Hi, I run Ubuntu development branch 24.04 and I have a problem with
  Epiphany browser 45.1-1 (Gnome Web): program doesn't launch, and I get
  this error

  $ epiphany
  bwrap: Creating new namespace failed: Permission denied

  ** (epiphany:12085): ERROR **: 14:44:35.023: Failed to fully launch 
dbus-proxy: Le processus fils s’est terminé avec le code 1
  Trappe pour point d'arrêt et de trace (core dumped)

  $ epiphany
  bwrap: Creating new namespace failed: Permission denied

  ** (epiphany:30878): ERROR **: 22:22:26.926: Failed to fully launch 
dbus-proxy: Le processus fils s’est terminé avec le code 1
  Trappe pour point d'arrêt et de trace (core dumped)

  Thanks for your help!

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/2046844/+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 2045741] Re: Installer lists "American English" twice on welcome screen

2024-01-01 Thread Launchpad Bug Tracker
This bug was fixed in the package calamares - 3.3.0.0-0ubuntu5

---
calamares (3.3.0.0-0ubuntu5) noble; urgency=medium

  * Fix two American English entries (LP: #2045741):
- https://github.com/calamares/calamares/issues/2257

 -- Simon Quigley   Mon, 01 Jan 2024 13:39:12 -0600

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

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

Title:
  Installer lists "American English" twice on welcome screen

Status in Calamares:
  Fix Released
Status in calamares package in Ubuntu:
  Fix Released

Bug description:
  Testing Lubuntu Noble daily image 20231205.1

  The installer lsits "American English" twice on the welcome screen.

  Minor bug that has no real influence on the install. see attached
  screenshot

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: calamares (not installed)
  ProcVersionSignature: Ubuntu 6.5.0-9.9-generic 6.5.3
  Uname: Linux 6.5.0-9-generic x86_64
  ApportVersion: 2.27.0-0ubuntu6
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: LXQt
  Date: Wed Dec  6 08:25:31 2023
  InstallationDate: Installed on 2023-12-06 (0 days ago)
  InstallationMedia: Lubuntu 24.04 LTS "Noble Numbat" - Daily amd64 (20231205.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/2045741/+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 2046099] Re: lubuntu calamares/lubuntu-installer-prompt - changing to english(AU) has app restart & ask language again as if still on english(US)

2023-12-23 Thread Launchpad Bug Tracker
This bug was fixed in the package lubuntu-installer-prompt -
1.1.1-0ubuntu2

---
lubuntu-installer-prompt (1.1.1-0ubuntu2) noble; urgency=medium

  * Ensure C is not the default locale, to the user.

 -- Simon Quigley   Sat, 23 Dec 2023 18:03:34 -0600

** Changed in: lubuntu-installer-prompt (Ubuntu)
   Status: In Progress => Fix Released

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

Title:
  lubuntu calamares/lubuntu-installer-prompt - changing to english(AU)
  has app restart & ask language again as if still on english(US)

Status in calamares package in Ubuntu:
  Invalid
Status in lubuntu-installer-prompt package in Ubuntu:
  Fix Released

Bug description:
  Lubuntu QA-test install on
  - hp dc7700 (c2d-e6230, 7gb amd/ati rv610/radeon hd2400 pro/xt)

  As reported in #lubuntu-devel, I changed the language in the lubuntu-
  installer-prompt from english(US) to english(AU), which caused both
  monitors to darken as the app/session? restarted and it re-appeared.

  I again was given the option to choose a language; with it default to
  ENGLISH(US) AGAIN, despite my changing it to ENGLISH(AU) !

  Simon said the language has changed (I can't tell given both are
  english in this example), BUT the app restarting has me return again
  with the default option asking if I want to change (away from)
  english(US) as if nothing was done.

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: calamares 3.3.0-alpha6-0ubuntu1
  ProcVersionSignature: Ubuntu 6.5.0-9.9-generic 6.5.3
  Uname: Linux 6.5.0-9-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-0ubuntu6
  Architecture: amd64
  CasperMD5CheckResult: pass
  CasperVersion: 1.488
  CurrentDesktop: LXQt
  Date: Mon Dec 11 13:48:03 2023
  LiveMediaBuild: Lubuntu 24.04 LTS "Noble Numbat" - Daily amd64 (20231210.2)
  RelatedPackageVersions:
   calamares-settings-ubuntu-common 1:24.04.9
   calamares-settings-lubuntu   1:24.04.9
   xfsprogs 6.5.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/2046099/+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 2047023] [NEW] Qt app crashed after upgrading Qt5 libraries to 5.15.10+dfsg-5build1 in noble-proposed

2023-12-22 Thread Launchpad Bug Tracker
You have been subscribed to a public bug by Simon Quigley (tsimonq2):

After upgrading Qt5 libraries to 5.15.10+dfsg-5build1, several Qt5
applications (including lxqt-panel and goldendict) crashed, leaving a
"*** buffer overflow detected ***: terminated" message in console.

It seems that the crashed applications all used the QSettings. The
following sample code will crash with 5.15.10+dfsg-5build1, but not with
5.15.10+dfsg-5

#include 
int main(int argc, char *argv[])
{
QSettings s("/tmp/a.ini", QSettings::IniFormat);
s.setValue("a", 123);
s.sync();
return 0;
}

** Affects: qtbase-opensource-src (Ubuntu)
 Importance: Medium
 Assignee: Rik Mills (rikmills)
 Status: Confirmed

-- 
Qt app crashed after upgrading Qt5 libraries to 5.15.10+dfsg-5build1 in 
noble-proposed
https://bugs.launchpad.net/bugs/2047023
You received this bug notification because you are a member of Ubuntu Studio 
Bugs, which is subscribed to the bug report.

-- 
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 2046844] [NEW] AppArmor user namespace creation restrictions cause many applications to crash with SIGTRAP

2023-12-21 Thread Launchpad Bug Tracker
You have been subscribed to a public bug by Simon Quigley (tsimonq2):

Hi, I run Ubuntu development branch 24.04 and I have a problem with
Epiphany browser 45.1-1 (Gnome Web): program doesn't launch, and I get
this error

$ epiphany
bwrap: Creating new namespace failed: Permission denied

** (epiphany:12085): ERROR **: 14:44:35.023: Failed to fully launch dbus-proxy: 
Le processus fils s’est terminé avec le code 1
Trappe pour point d'arrêt et de trace (core dumped)

$ epiphany
bwrap: Creating new namespace failed: Permission denied

** (epiphany:30878): ERROR **: 22:22:26.926: Failed to fully launch dbus-proxy: 
Le processus fils s’est terminé avec le code 1
Trappe pour point d'arrêt et de trace (core dumped)

Thanks for your help!

** Affects: apparmor (Ubuntu)
 Importance: Critical
 Status: Confirmed

** Affects: digikam (Ubuntu)
 Importance: High
 Status: Confirmed

** Affects: epiphany-browser (Ubuntu)
 Importance: High
 Status: Confirmed

** Affects: falkon (Ubuntu)
 Importance: High
 Status: Confirmed

** Affects: qutebrowser (Ubuntu)
 Importance: High
 Status: Confirmed

-- 
AppArmor user namespace creation restrictions cause many applications to crash 
with SIGTRAP
https://bugs.launchpad.net/bugs/2046844
You received this bug notification because you are a member of Ubuntu Studio 
Bugs, which is subscribed to the bug report.

-- 
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 2046386] [NEW] Ubuntu Studio images aren't being built with a live user

2023-12-13 Thread Launchpad Bug Tracker
You have been subscribed to a public bug by Erich Eickmeyer (eeickmeyer):

This is a tracking bug to figure out the issue with Ubuntu Studio noble
images not being built with a live user.

This appeared after we started the transition to using ubuntustudio-
system-installer (a fork of ubuntu-flavor-installer, itself a layer on
top of ubuntu-desktop-installer). With Steve Langasek's guidance, we
merged the code to livecd-rootfs to get .iso images building with
ubuntustudio-system-installer, but the system boots to a blank black
screen with a mouse cursor themed with the Breeze cursor theme from KDE
Plasma Desktop, meaning something is attempting to be loaded here.

However, switching to a VM results in a login prompt, but attempts to
login as "ubuntu-studio" as in the past proved in vain. Upon
investigating the squashfs image, no user directories populate the /home
directory, suggesting casper never creates the ubuntu-studio user.

I noticed that all previous flavors (Ubuntu Desktop, Ubuntu Budgie)
using ubuntu-desktop-installer have something similar to the following
line:

> add_package standard.live linux-$KERNEL_FLAVOURS casper

While, in theory, this would mean simply adding casper to the live seed
would fix it, in practice, adding casper to the live seed for Ubuntu
Studio does not.

Therefore, this is either a bug in livecd-rootfs or casper itself. Right
now, I have a MP open in livecd-rootfs as I suspect, based on the other
flavors' stanzas, that this one line change should fix it, but it could
also be that casper itself is not doing its job.

** Affects: casper (Ubuntu)
 Importance: High
 Status: New

** Affects: livecd-rootfs (Ubuntu)
 Importance: High
 Status: New

-- 
Ubuntu Studio images aren't being built with a live user
https://bugs.launchpad.net/bugs/2046386
You received this bug notification because you are a member of Ubuntu Studio 
Bugs, which is subscribed to the bug report.

-- 
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] Re: [SRU] buffer size and sample rate no longer updates

2023-12-05 Thread Launchpad Bug Tracker
This bug was fixed in the package ubuntustudio-installer - 1.9.1

---
ubuntustudio-installer (1.9.1) mantic; urgency=medium

  * No-change backport to mantic.

ubuntustudio-installer (1.10) noble; urgency=medium

  * Fix for variable no longer setting latency or samplerate (LP:
#2043214)

 -- Erich Eickmeyer   Fri, 10 Nov 2023 07:01:23
-0800

** Changed in: ubuntustudio-installer (Ubuntu Mantic)
   Status: Fix Committed => Fix Released

-- 
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:
  [SRU] buffer size and sample rate no longer updates

Status in ubuntustudio-installer package in Ubuntu:
  Fix Released
Status in ubuntustudio-installer source package in Mantic:
  Fix Released
Status in ubuntustudio-installer source package in Noble:
  Fix Released

Bug description:
  [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.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntustudio-installer/+bug/2043214/+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 2044623] Re: (L)Ubuntu 24.04 Daily install fails when XFS is selected

2023-12-05 Thread Launchpad Bug Tracker
This bug was fixed in the package xfsprogs - 6.5.0-1ubuntu1

---
xfsprogs (6.5.0-1ubuntu1) noble; urgency=medium

  * debian/patches/revert-mkfs-enable-large-extent-counts-by-default.patch:
Revert large extent counts feature for noble (LP: #2044623)

 -- Julian Andres Klode   Tue, 28 Nov 2023 18:27:22
+0100

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

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

Title:
  (L)Ubuntu 24.04 Daily install fails when XFS is selected

Status in calamares package in Ubuntu:
  Invalid
Status in grub2 package in Ubuntu:
  Confirmed
Status in xfsprogs package in Ubuntu:
  Fix Released

Bug description:
  Lubuntu Noble install on Proxmox VM with EFI
  4G RAM 32G disk 2CPU cores
  XFS Erase disk automatic partitioning selected.

  ** expected result
  Install proceeds using the XFS filesystem and completes without error; reboot 
into the new system

  ** actual result
  Install fails with error -
  2023-11-25 - 16:08:25 [1]: ERROR: Installation failed: "Bootloader 
installation error"
  2023-11-25 - 16:08:25 [6]: .. - message: "Bootloader installation error"
  2023-11-25 - 16:08:25 [6]: .. - details: The bootloader could not be 
installed. The installation command grub-install --target=x86_64-efi 
--efi-directory=/boot/efi --bootloader-id=ubuntu --force returned error 
code 1.

  Booting into the new system fails.

  An installation with EXT4 proceeds and works as expected on the same
  VM configuration.

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: calamares 3.3.0-alpha6-0ubuntu1
  ProcVersionSignature: Ubuntu 6.5.0-9.9-generic 6.5.3
  Uname: Linux 6.5.0-9-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-0ubuntu6
  Architecture: amd64
  CasperMD5CheckResult: pass
  CasperVersion: 1.487
  CurrentDesktop: LXQt
  Date: Sat Nov 25 16:40:22 2023
  LiveMediaBuild: Lubuntu 24.04 "Noble Numbat" - Daily amd64 (20231124)
  RelatedPackageVersions:
   calamares-settings-ubuntu-common 1:24.04.8
   calamares-settings-lubuntu   1:24.04.8
   xfsprogs 6.5.0-1
   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/2044623/+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 2045095] Re: Merge rapid-photo-downloader from Debian

2023-11-29 Thread Launchpad Bug Tracker
This bug was fixed in the package rapid-photo-downloader -
0.9.34+repack-1ubuntu1

---
rapid-photo-downloader (0.9.34+repack-1ubuntu1) noble; urgency=low

  * Merge from Debian unstable. (LP: #2045095) Remaining changes:
- Add gir1.2-unity-5.0 to Depends, requested by upstream

rapid-photo-downloader (0.9.34+repack-1) unstable; urgency=medium

  * New upstream version 0.9.34
- Fix build with setuptools 67.x.
  Thanks to Antoine Beaupré  (Closes: #1042356)
  Because d/patches are not applied for the clean target,
  the build fails due to the wrong python_requires version string.
  The repackaged source changes the file setup.py and uses
  the version string suggested in the above mentioned bug report.
  Upstream has fixed this in VCS, but there's no released
  version yet. For the next upstream version, there shouldn't
  be a repacking necessary.
  * Update d/copyright
  * Update Standards-Version to 4.6.2, no changes needed
  * Fix lintian warning for d/copyright and move paragraph

rapid-photo-downloader (0.9.33-1.1) unstable; urgency=medium

  * Non-maintainer upload.
  * Patch: Support setuptools 60. (Closes: #1022437)

rapid-photo-downloader (0.9.33-1) unstable; urgency=medium

  [ Tino Mettler ]
  * New upstream version 0.9.33
  * Add Depends: for python3-showinfilemanager
  * Add Depends: for ifuse and libimobiledevice-utils, needed as of 0.9.29
  * Remove Recommends: for libraw-bin, as it is not used anymore
  * Remove 0002-Disable-optional-rawkit-usage.patch, applied upstream
  * Don't generate analyze-pv-structure.1 as it was removed upstream
  * Use CHANGES.md, CHANGES.rst was dropped by upstream
  * Disable dh_auto_test, it causes a build failure
  * Add myself to Uploaders:
  * Update debian/copyright

  [ Debian Janitor ]
  * Re-export upstream signing key without extra signatures.
  * Set upstream metadata fields: Repository, Repository-Browse.

  [ Tino Mettler ]
  * Set upstream metadata fields: Bug-Database, Bug-Submit
  * Update Standards-Version to 4.6.0.1, no changes needed
  * Add images from upstream git repository to regenerate qrc_resources.py
  * Add pyqt5-dev-tools to build dependencies for pyrcc5
  * Regenerate qrc_resources.py (Closes: #1010570)
  * Replace override_dh_auto_clean actions with debian/clean
  * Add details about source files with generated binary data in d/copyright

 -- Aaron Rainbolt   Tue, 28 Nov 2023 20:19:30
-0600

** Changed in: rapid-photo-downloader (Ubuntu)
   Status: Fix Committed => Fix Released

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

Title:
  Merge rapid-photo-downloader from Debian

Status in rapid-photo-downloader package in Ubuntu:
  Fix Released

Bug description:
  Debian version: 0.9.34+repack-1
  Ubuntu version: 0.9.33-0ubuntu1

  Merge patch is attached.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/rapid-photo-downloader/+bug/2045095/+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 2043261] Re: kdenlive fails to show effects or compositions unless qml-module-org-kde-kcm is installed

2023-11-17 Thread Launchpad Bug Tracker
This bug was fixed in the package kdenlive - 4:23.08.3-0ubuntu2

---
kdenlive (4:23.08.3-0ubuntu2) noble; urgency=medium

  * Add missing runtime qml module depends:
- qml-module-org-kde-kcm (LP: #2043261)
- qml-module-org-kde-newstuff

 -- Rik Mills   Sat, 11 Nov 2023 14:25:50 +

** Changed in: kdenlive (Ubuntu Noble)
   Status: Fix Committed => Fix Released

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

Title:
  kdenlive fails to show effects or compositions unless qml-module-org-
  kde-kcm is installed

Status in kdenlive package in Ubuntu:
  Fix Released
Status in kdenlive source package in Mantic:
  Triaged
Status in kdenlive source package in Noble:
  Fix Released

Bug description:
  kdenlive normally shows lists of effects plugins or composition tools
  in a pane/tab at various places in the UI.  After installing kdenlive
  directly from apt, these panes show blank space (white in my case,
  despite the dark theme).  This appears to be a UI rendering problem,
  which I suspect for the following reasons:

  1. The effects are available from the menu: Timeline→Add Effect→[choose 
effect category]→[choose effect]
  2. After I installed qml-module-org-kde-kcm via apt, the problem went away 
and the interface now shows the effects tree as shown in the documentation for 
kdenlive.

  This appears to be a missing dependency only, and for a rather
  prominent video editor in Ubuntu.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: kdenlive 4:23.08.1-0ubuntu1
  ProcVersionSignature: Ubuntu 6.5.0-10.10-generic 6.5.3
  Uname: Linux 6.5.0-10-generic x86_64
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Nov 11 11:05:52 2023
  InstallationDate: Installed on 2022-12-13 (333 days ago)
  InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020)
  SourcePackage: kdenlive
  UpgradeStatus: Upgraded to mantic on 2023-10-28 (14 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/kdenlive/+bug/2043261/+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 2043301] Re: lubuntu noble install failure - encryption

2023-11-14 Thread Launchpad Bug Tracker
This bug was fixed in the package calamares - 3.3.0-alpha4-0ubuntu2

---
calamares (3.3.0-alpha4-0ubuntu2) noble; urgency=medium

  * Fixed encrypted installations. (LP: #2043301)
  * Fixed watch file.
  * Swapped out an obsolete build dependency (poilcykit-1).
  * Created upstream/metadata file.

 -- Aaron Rainbolt   Tue, 14 Nov 2023 17:32:18
-0600

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

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

Title:
  lubuntu noble install failure - encryption

Status in calamares package in Ubuntu:
  Fix Released

Bug description:
  possibly a duplicate...  (install attempt a few days back report is
  here -
  https://bugs.launchpad.net/ubuntu/+source/calamares/+bug/2043161)

  but error message doesn't quite match.. thus new report  but likely
  related

  ** details

  install to

  - sony vaio ultrabook svp11216cgb (i5-9400u, 4gb, intel haswell-ULT)

  testcase: full disk, encryption, EFI, no-internet, no-swap, autologin

  ** expected result

  clean install, reboot & login

  ** actual result

  calamares ended with message
  ---
  The bootloader could not be installed. The installation command 
grub-install --target=x86_64-efi --efi-directory=/boot/efi 
--bootloader-id=ubuntu --force returned error code 1.
  ---

  Installs with options
  - testcase: full disk, no-encryption, EFI, no-internet, no-swap
  - testcase: full disk, no-encryption, EFI, no-internet, no-swap, autologin

  This failed install used options
  - testcase: full disk, encryption, EFI, no-internet, no-swap, autologin

  ie. issue is with ENCRYPTION being used I believe

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: calamares 3.3.0-alpha4-0ubuntu1
  ProcVersionSignature: Ubuntu 6.5.0-9.9-generic 6.5.3
  Uname: Linux 6.5.0-9-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-0ubuntu6
  Architecture: amd64
  CasperMD5CheckResult: pass
  CasperVersion: 1.486
  CurrentDesktop: LXQt
  Date: Sun Nov 12 17:36:59 2023
  LiveMediaBuild: Lubuntu 24.04 "Noble Numbat" - Daily amd64 (2023)
  RelatedPackageVersions:
   calamares-settings-ubuntu-common 1:23.10.4
   calamares-settings-lubuntu   1:23.10.4
   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/2043301/+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 2043261] Re: kdenlive fails to show effects or compositions unless qml-module-org-kde-kcm is installed

2023-11-11 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: kdenlive (Ubuntu)
   Status: New => Confirmed

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

Title:
  kdenlive fails to show effects or compositions unless qml-module-org-
  kde-kcm is installed

Status in kdenlive package in Ubuntu:
  Confirmed

Bug description:
  kdenlive normally shows lists of effects plugins or composition tools
  in a pane/tab at various places in the UI.  After installing kdenlive
  directly from apt, these panes show blank space (white in my case,
  despite the dark theme).  This appears to be a UI rendering problem,
  which I suspect for the following reasons:

  1. The effects are available from the menu: Timeline→Add Effect→[choose 
effect category]→[choose effect]
  2. After I installed qml-module-org-kde-kcm via apt, the problem went away 
and the interface now shows the effects tree as shown in the documentation for 
kdenlive.

  This appears to be a missing dependency only, and for a rather
  prominent video editor in Ubuntu.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: kdenlive 4:23.08.1-0ubuntu1
  ProcVersionSignature: Ubuntu 6.5.0-10.10-generic 6.5.3
  Uname: Linux 6.5.0-10-generic x86_64
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Nov 11 11:05:52 2023
  InstallationDate: Installed on 2022-12-13 (333 days ago)
  InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020)
  SourcePackage: kdenlive
  UpgradeStatus: Upgraded to mantic on 2023-10-28 (14 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/kdenlive/+bug/2043261/+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] Re: [SRU] buffer size and sample rate no longer updates

2023-11-10 Thread Launchpad Bug Tracker
This bug was fixed in the package ubuntustudio-installer - 1.10

---
ubuntustudio-installer (1.10) noble; urgency=medium

  * Fix for variable no longer setting latency or samplerate (LP:
#2043214)

 -- Erich Eickmeyer   Fri, 10 Nov 2023 06:37:53
-0800

** Changed in: ubuntustudio-installer (Ubuntu Noble)
   Status: In Progress => Fix Released

-- 
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:
  [SRU] buffer size and sample rate no longer updates

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

Bug description:
  [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.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntustudio-installer/+bug/2043214/+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 2033575] Re: lubuntu jammy install; failure re-using existing partition

2023-10-29 Thread Launchpad Bug Tracker
[Expired for calamares (Ubuntu) because there has been no activity for
60 days.]

** Changed in: calamares (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  lubuntu jammy install; failure re-using existing partition

Status in calamares package in Ubuntu:
  Expired

Bug description:
  lubuntu re-install (jammy daily) on 
  - hp 8200 elite sff (i5-2400, 8gb, nvidia quadro 600)

  system directories were mostly erased (all binary directories anyway).

  i think the sources included packages.element.io/debian where
  NO_PUBKEY exists on ISO (it's a 3rd party resource that's why) meaning
  it's expected & not an error.   I'll confirm this I hope shortly, but
  if/when I do this bug report will be INVALID  (maybe I can document
  something to help users with this issue??)

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: calamares 3.2.61-0ubuntu0.1
  ProcVersionSignature: Ubuntu 6.2.0-32.32~22.04.1-generic 6.2.16
  Uname: Linux 6.2.0-32-generic x86_64
  .etc.calamares.modules.finished.conf:
   ---
   restartNowMode: user-checked
   restartNowCommand: "systemctl -i reboot"
  .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-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: pass
  CasperVersion: 1.470.3
  CurrentDesktop: LXQt
  Date: Thu Aug 31 13:33:15 2023
  LiveMediaBuild: Lubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 
(20230830)
  RelatedPackageVersions:
   calamares-settings-ubuntu-common 1:22.04.4.3
   calamares-settings-lubuntu   1:22.04.4.3
   xfsprogs 5.13.0-1ubuntu2
   btrfs-progs  5.16.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/2033575/+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 1995644] Re: No AC3/EAC3 Ubuntu 22.10

2023-10-22 Thread Launchpad Bug Tracker
[Expired for pavucontrol (Ubuntu) because there has been no activity for
60 days.]

** Changed in: pavucontrol (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  No AC3/EAC3 Ubuntu 22.10

Status in pavucontrol package in Ubuntu:
  Expired
Status in wireplumber package in Ubuntu:
  Expired

Bug description:
  I posted the same issue in Pipewire Issues and Pipewire-Wirplumber
  @Gitlab. There someone suggested it might be a Wireplumber issue so
  I'm going to try my luck here.

  I recently upgraded to 22.10 with Pipewire as audio server. In Ubuntu
  22.04 I used to be able to control the audio formats which my receiver
  can decode with Pulse Audio Volume Control. Now this doesn't work
  anymore. My receiver no longer switches between DD, DD+ and DTS
  signals (defaults to DD). For example, when I play DTS audio, my
  receiver stays on DD.

  In PulseAudio Volume Control I can still set which formats my receiver
  understands, but after a reboot these options are all turned off
  again. So these settings are not saved.

  When I set the audio formats back in PulseAudio Volume Control after a
  reboot, DTS is passed on to my receiver, AC3 and EAC3 too (my receiver
  switches format to DD or DD+) but there's no sound or I hear
  intermittently very stuttering audio, as if a piece of audio is
  repeated over and over like a sample.

  So without setting formats with pavucontrol there's only AC3.
  AC3, EAC3 and DTS are submiited as AC3.

  With formats AC3, EAC3 and DTS turned on only DTS works and EAC3 is
  sent to my receiver (the display changes to DD+) but there's no sound.

  I have read Wireplumber and Pipewire wikis but I can't get it to work.

  How can I get Pipewire-Wireplumber to play EAC3 and other surround
  formats, if at all possible?

  Ubuntu 22.10

  Package: pipewire
  Version: 0.3.58-2ubuntu1

  Package: wireplumber
  Version: 0.4.12-1

  Package: vlc
  Version: 3.0.17.4-5

  Package: pavucontrol
  Version: 5.0-2

  Package: pulseaudio
  Version: 1:16.1+dfsg1-1ubuntu3

  Might be related to bug 1991934 as I too see the error Can't find xdg-
  portal?

  nov 03 19:40:39  systemd[2871]: Started PipeWire Multimedia Service.
  nov 03 19:40:39  pipewire[3023]: mod.rt: Can't find xdg-portal: (null)
  nov 03 19:40:39  pipewire[3023]: mod.rt: found session bus but no portal

  pactl list short sinks
  46 alsa_output.pci-_00_1b.0.analog-stereo PipeWire s32le 2ch 48000Hz 
RUNNING

  
  pw-cli ls Node

id 45, type PipeWire:Interface:Node/3
object.serial = "87"
object.path = "alsa:pcm:0:hdmi:0:playback"
factory.id = "18"
client.id = "31"
device.id = "40"
priority.session = "696"
priority.driver = "696"
node.description = "Built-in Audio Digital Stereo (HDMI)"
node.name = "alsa_output.pci-_00_1b.0.hdmi-stereo"
node.nick = "DENON-AVR"
media.class = "Audio/Sink"

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pavucontrol/+bug/1995644/+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 1995644] Re: No AC3/EAC3 Ubuntu 22.10

2023-10-22 Thread Launchpad Bug Tracker
[Expired for wireplumber (Ubuntu) because there has been no activity for
60 days.]

** Changed in: wireplumber (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  No AC3/EAC3 Ubuntu 22.10

Status in pavucontrol package in Ubuntu:
  Expired
Status in wireplumber package in Ubuntu:
  Expired

Bug description:
  I posted the same issue in Pipewire Issues and Pipewire-Wirplumber
  @Gitlab. There someone suggested it might be a Wireplumber issue so
  I'm going to try my luck here.

  I recently upgraded to 22.10 with Pipewire as audio server. In Ubuntu
  22.04 I used to be able to control the audio formats which my receiver
  can decode with Pulse Audio Volume Control. Now this doesn't work
  anymore. My receiver no longer switches between DD, DD+ and DTS
  signals (defaults to DD). For example, when I play DTS audio, my
  receiver stays on DD.

  In PulseAudio Volume Control I can still set which formats my receiver
  understands, but after a reboot these options are all turned off
  again. So these settings are not saved.

  When I set the audio formats back in PulseAudio Volume Control after a
  reboot, DTS is passed on to my receiver, AC3 and EAC3 too (my receiver
  switches format to DD or DD+) but there's no sound or I hear
  intermittently very stuttering audio, as if a piece of audio is
  repeated over and over like a sample.

  So without setting formats with pavucontrol there's only AC3.
  AC3, EAC3 and DTS are submiited as AC3.

  With formats AC3, EAC3 and DTS turned on only DTS works and EAC3 is
  sent to my receiver (the display changes to DD+) but there's no sound.

  I have read Wireplumber and Pipewire wikis but I can't get it to work.

  How can I get Pipewire-Wireplumber to play EAC3 and other surround
  formats, if at all possible?

  Ubuntu 22.10

  Package: pipewire
  Version: 0.3.58-2ubuntu1

  Package: wireplumber
  Version: 0.4.12-1

  Package: vlc
  Version: 3.0.17.4-5

  Package: pavucontrol
  Version: 5.0-2

  Package: pulseaudio
  Version: 1:16.1+dfsg1-1ubuntu3

  Might be related to bug 1991934 as I too see the error Can't find xdg-
  portal?

  nov 03 19:40:39  systemd[2871]: Started PipeWire Multimedia Service.
  nov 03 19:40:39  pipewire[3023]: mod.rt: Can't find xdg-portal: (null)
  nov 03 19:40:39  pipewire[3023]: mod.rt: found session bus but no portal

  pactl list short sinks
  46 alsa_output.pci-_00_1b.0.analog-stereo PipeWire s32le 2ch 48000Hz 
RUNNING

  
  pw-cli ls Node

id 45, type PipeWire:Interface:Node/3
object.serial = "87"
object.path = "alsa:pcm:0:hdmi:0:playback"
factory.id = "18"
client.id = "31"
device.id = "40"
priority.session = "696"
priority.driver = "696"
node.description = "Built-in Audio Digital Stereo (HDMI)"
node.name = "alsa_output.pci-_00_1b.0.hdmi-stereo"
node.nick = "DENON-AVR"
media.class = "Audio/Sink"

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pavucontrol/+bug/1995644/+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 2036999] Re: ubiquity: Wifi password not copied to new install

2023-10-08 Thread Launchpad Bug Tracker
This bug was fixed in the package calamares - 3.3.0-alpha2-0ubuntu6

---
calamares (3.3.0-alpha2-0ubuntu6) mantic; urgency=medium

  * Add support for Netplan backends (LP: #2036999).

 -- Simon Quigley   Sun, 08 Oct 2023 11:41:22 -0500

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

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

Title:
  ubiquity: Wifi password not copied to new install

Status in calamares package in Ubuntu:
  Fix Released
Status in ubiquity package in Ubuntu:
  Fix Released

Bug description:
  This is related to bug 2036997 except this is for Ubiquity ("legacy"
  installer) and the other bug is for the new Ubuntu Desktop Installer

  What happened?
  ==
  If a Wifi password is provided during the install, the Wifi network is 
supposed to be preconfigured with that password after install. It's not working 
with Ubuntu 23.10.

  Steps to reproduce
  ==
  Use the "legacy" Ubuntu Desktop installer to install Ubuntu 23.10 from a 
computer that has a wifi card
  During the install, connect to a password-protected wifi network
  After the install, the computer should be automatically connected to that 
network

  Additional context
  ==
  20230920 Ubuntu Desktop Legacy Mantic ISO

  Ubuntu Desktop 23.10 now uses Netplan as the NetworkManager backend.

  Unlike with bug 2036997, there is no netplan config file referencing
  the wifi network.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/calamares/+bug/2036999/+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 2038351] Re: darktable FTBFS

2023-10-03 Thread Launchpad Bug Tracker
This bug was fixed in the package darktable - 4.4.2-1ubuntu1

---
darktable (4.4.2-1ubuntu1) mantic; urgency=medium

  * Disable openmp for arm64 builds (LP: #2038351)
See Debian bug: #1053405

 -- Mitchell Dzurick   Tue, 03 Oct 2023
08:58:01 -0700

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

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

Title:
  darktable FTBFS

Status in darktable package in Ubuntu:
  Fix Released

Bug description:
  4.4.2-1 currently FTBFS

  This is an active issue in Debian - https://bugs.debian.org/cgi-
  bin/bugreport.cgi?bug=1053405

  Potentially an issue with gcc, upstream gcc bug filed -
  https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111677

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/darktable/+bug/2038351/+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 Launchpad Bug Tracker
This bug was fixed in the package carla - 2.5.7-0ubuntu1

---
carla (2.5.7-0ubuntu1) mantic; urgency=medium

  [ Erich Eickmeyer ]
  * New upstream bugfix release (LP: #2037787)

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

 -- Erich Eickmeyer   Sat, 30 Sep 2023 08:35:21
-0700

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

-- 
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 Released

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 2012146] Re: very high cpu usage, system unresponsive

2023-09-24 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: ibus (Ubuntu)
   Status: New => Confirmed

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

Title:
  very high cpu usage, system unresponsive

Status in ibus:
  Unknown
Status in ardour package in Ubuntu:
  Confirmed
Status in ibus package in Ubuntu:
  Confirmed
Status in ardour package in Debian:
  New

Bug description:
  may be related to Ardour 7.3, when I start ardour and start working
  with the app, the system slows down and htop shows 100% cpu usage for
  ibus-daemon

  ProblemType: Bug
  DistroRelease: Ubuntu 23.04
  Package: ibus 1.5.28-2
  ProcVersionSignature: Ubuntu 6.1.0-16.16-generic 6.1.6
  Uname: Linux 6.1.0-16-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.26.0-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Mar 18 15:21:55 2023
  InstallationDate: Installed on 2022-05-13 (308 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  SourcePackage: ibus
  UpgradeStatus: Upgraded to lunar on 2023-03-17 (1 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ibus/+bug/2012146/+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 2012146] Re: very high cpu usage, system unresponsive

2023-09-24 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: ardour (Ubuntu)
   Status: New => Confirmed

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

Title:
  very high cpu usage, system unresponsive

Status in ibus:
  Unknown
Status in ardour package in Ubuntu:
  Confirmed
Status in ibus package in Ubuntu:
  Confirmed
Status in ardour package in Debian:
  New

Bug description:
  may be related to Ardour 7.3, when I start ardour and start working
  with the app, the system slows down and htop shows 100% cpu usage for
  ibus-daemon

  ProblemType: Bug
  DistroRelease: Ubuntu 23.04
  Package: ibus 1.5.28-2
  ProcVersionSignature: Ubuntu 6.1.0-16.16-generic 6.1.6
  Uname: Linux 6.1.0-16-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.26.0-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Mar 18 15:21:55 2023
  InstallationDate: Installed on 2022-05-13 (308 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  SourcePackage: ibus
  UpgradeStatus: Upgraded to lunar on 2023-03-17 (1 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ibus/+bug/2012146/+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 2036181] Re: ftbfs on i386: cli_actions-path-simplify_check_output failed

2023-09-16 Thread Launchpad Bug Tracker
This bug was fixed in the package inkscape - 1.2.2-2ubuntu4

---
inkscape (1.2.2-2ubuntu4) mantic; urgency=medium

  * use -fexcess-precision=fast to compile 2geom. (LP: #2036181)
Since gcc-13, excess precision support has been implemented for C++.
-fexcess-precision=fast restores previous behavior.

 -- Shengjing Zhu   Sat, 16 Sep 2023
14:43:10 +0800

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

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

Title:
  ftbfs on i386: cli_actions-path-simplify_check_output failed

Status in inkscape package in Ubuntu:
  Fix Released

Bug description:
  99% tests passed, 1 tests failed out of 342

  Total Test time (real) =  52.38 sec

  The following tests did not run:
 50 - cli_export-type_ps_check_output (Skipped)
 52 - cli_export-type_eps_check_output (Skipped)
 54 - cli_export-type_pdf_check_output (Skipped)
 56 - cli_export-type_emf_check_output (Skipped)
 66 - cli_export-area-page_pdf_check_output (Skipped)
 68 - cli_export-area-page_ps_check_output (Skipped)
 70 - cli_export-area-page_emf_check_output (Skipped)
 78 - cli_export-area-page_export-id_pdf_check_output (Skipped)
 80 - cli_export-area-page_export-id_ps_check_output (Skipped)
 86 - cli_export-area-drawing_pdf_check_output (Skipped)
 88 - cli_export-area-drawing_ps_check_output (Skipped)
 90 - cli_export-area-drawing_eps_check_output (Skipped)
100 - cli_export-dpi_pdf_check_output (Skipped)
102 - cli_export-dpi_ps_check_output (Skipped)
104 - cli_export-dpi_eps_check_output (Skipped)
120 - cli_export-margin_mm_pdf_check_output (Skipped)
124 - cli_export-margin_px_ps_check_output (Skipped)
130 - cli_export-margin_export-id_export-id-only_ps_check_output 
(Skipped)
134 - cli_export-margin_export-area-drawing_ps_check_output (Skipped)
150 - cli_export-id_export-id-only_pdf_check_output (Skipped)
152 - cli_export-id_export-id-only_ps_check_output (Skipped)
154 - cli_export-id_export-id-only_eps_check_output (Skipped)
160 - cli_export-id_export-id-only_export-area-page_pdf_check_output 
(Skipped)
162 - cli_export-id_export-id-only_export-area-page_ps_check_output 
(Skipped)
168 - cli_export-ps-level_2_check_output (Skipped)
172 - cli_export-ps-level_3_check_output (Skipped)
210 - cli_export-with-filters_ps_check_output (Skipped)
212 - cli_export-with-filters_eps_check_output (Skipped)
214 - cli_export-with-filters_pdf_check_output (Skipped)
216 - cli_export-ignore-filters_ps_check_output (Skipped)
218 - cli_export-ignore-filters_pdf_check_output (Skipped)
220 - cli_export-ignore-filters_emf_check_output (Skipped)
246 - cli_export-extension_ps_check_output (Skipped)
248 - cli_export-extension_eps_check_output (Skipped)
250 - cli_export-extension_pdf_check_output (Skipped)
252 - cli_export-extension_emf_check_output (Skipped)

  The following tests FAILED:
288 - cli_actions-path-simplify_check_output (Failed)
  Errors while running CTest
  FAILED: CMakeFiles/test.util 
  cd /<>/obj-i686-linux-gnu && /usr/bin/ctest 
--force-new-ctest-process
  ninja: build stopped: subcommand failed.
  dh_auto_test: error: cd obj-i686-linux-gnu && LC_ALL=C.UTF-8 
MESON_TESTTHREADS=1 ninja test returned exit code 1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/inkscape/+bug/2036181/+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-06 Thread Launchpad Bug Tracker
This bug was fixed in the package blender - 3.6.2+dfsg-1ubuntu1

---
blender (3.6.2+dfsg-1ubuntu1) mantic; urgency=medium

  * debian/patches: patchset updated (LP: #2033618)
- 0004-double-promotion-not-error.patch added
- 0005-device-pointer-type.patch added

 -- Nathan Pratta Teodosio   Tue, 05 Sep
2023 15:51:34 +0200

** Changed in: blender (Ubuntu Mantic)
   Status: Fix Committed => Fix Released

-- 
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 Released
Status in blender source package in Lunar:
  Won't Fix
Status in blender source package in Mantic:
  Fix Released

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 1900908] [NEW] Mutter doesn't apply gsettings appropriately to Wacom tablet on Xorg, but Wayland works

2023-09-01 Thread Launchpad Bug Tracker
You have been subscribed to a public bug:

I have a Wacom Intuos VT M tablet in a setting with two monitors (laptop
+ external). Under an up-to-date Ubuntu Focal running X, if I map the
tablet to a single monitor it fails to map it more often than not. A
reliable way of getting failure is first connecting the tablet via
bluetooth and then via USB. The only way to revert to a correct behavior
is reseting X (ALT+F2 r). This is necessary even after rebooting.

I've noticed that, when not working well, the problem is that Mutter
sends the mapping data to the "Wacom Intuos BT M Pad pad" device, while
it should be sending them to "Wacom Intuos BT M Pad stylus" (this is
what it does when it works well).

Under Wayland it works well (well, the tablet buttons don't work under
Wayland but this is unrelated).

PS I reported this bug against the Wacom X driver but was told it's
really related to mutter (https://github.com/linuxwacom/xf86-input-
wacom/issues/148).

** Affects: mutter
 Importance: Unknown
 Status: Fix Released

** Affects: xf86-input-wacom
 Importance: Unknown
 Status: New

** Affects: gnome-control-center (Ubuntu)
 Importance: Undecided
 Status: Confirmed

** Affects: mutter (Ubuntu)
 Importance: Medium
 Status: Confirmed

** Affects: xf86-input-wacom (Ubuntu)
 Importance: Undecided
 Status: Confirmed


** Tags: focal wacom
-- 
Mutter doesn't apply gsettings appropriately to Wacom tablet on Xorg, but 
Wayland works
https://bugs.launchpad.net/bugs/1900908
You received this bug notification because you are a member of Ubuntu Studio 
Bugs, which is subscribed to xf86-input-wacom in Ubuntu.

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


  1   2   3   4   5   6   7   8   9   10   >