It's SDDM's fault - I can reproduce this using the Openbox session too.
** Also affects: sddm (Ubuntu)
Importance: Undecided
Status: New
** No longer affects: lxqt-build-tools (Ubuntu)
** No longer affects: lxqt-build-tools (Ubuntu Noble)
** No longer affects: lxqt-build-tools (Ubuntu
grrr... no, it's not SDDM's fault apparently, upgrading it in a 22.04 VM
didn't cause the issue to appear! Still hunting.
--
You received this bug notification because you are a member of Kubuntu
Bugs, which is subscribed to sddm in Ubuntu.
https://bugs.launchpad.net/bugs/2045706
Title:
Loggin
Finally pinned it down by upgrading packages a little bit at a time from
Backports on a Lubuntu 22.04 LTS VM. Upgrading lubuntu-update-notifier
triggers the bug.
** Also affects: lubuntu-update-notifier (Ubuntu)
Importance: Undecided
Status: New
** No longer affects: sddm (Ubuntu Noble)
This is affecting Falkon and qutebrowser as well. Just now me and a
couple of the Lubuntu devs did a deep debugging session and found the
issue.
About four days ago, an upload was made in AppArmor that no longer
allows unprivileged programs to create user namespaces. See
https://launchpad.net/ubun
This bug also breaks Electron-based AppImages, such as Balena Etcher.
While we specifically don't support these apps, I find it very likely
that Ubuntu has potentially hundreds of thousands of users of these
kinds of apps.
--
You received this bug notification because you are a member of Kubuntu
Thanks! I'll be on the hunt for any more that act like this and add them
to the report. I'm also happy to help prep uploads (I'm not an MOTU yet
so I can't upload on my own, but I can prep the packaging).
--
You received this bug notification because you are a member of Kubuntu
Bugs, which is sub
Nice! This works with AppImages? If so, I think we have a perfect
solution.
--
You received this bug notification because you are a member of Kubuntu
Bugs, which is subscribed to digikam in Ubuntu.
https://bugs.launchpad.net/bugs/2046844
Title:
AppArmor user namespace creation restrictions cau
How acceptable or possible would a solution be that had one universal
"allowUserNamespaces" attribute in an AppArmor config that could then
simply be set on whatever files one wanted to enable the features on?
That would support all third-party apps that a user deemed worthy
without needing much ef
I can't seem to get the xattr solution to work. I'm trying it on a
normal binary and it's failing like so:
# Contents of /etc/apparmor.d/falkon
abi ,
include
profile falkon xattrs=(security.apparmor=falkon) flags=(unconfined) {
userns,
include if exists
}
# setfattr command
user@user-stan
The reason I was suggesting a single attribute to enable user namespace
creation is because of the myriad of third-party apps that we probably
*aren't* going to catch here that users use out there that require user
namespace privileges. For instance, there are probably at least some
QtWebEngine-bas
User prompting sounds like a good idea. Tt fixes one concern I wanted to
bring up, which is developers who use user namespaces in their code
(possibly indirectly by using QtWebEngine for instance). Those devs
would end up with their software crashing for no apparent reason. A user
prompt or descrip
finished.
This FFe applies to both lubuntu-installer-prompt and kubuntu-installer-
prompt.
** Affects: kubuntu-installer-prompt (Ubuntu)
Importance: Undecided
Assignee: Aaron Rainbolt (arraybolt3)
Status: New
** Affects: lubuntu-installer-prompt (Ubuntu)
Importance: Undecided
Released => Confirmed
** Changed in: kubuntu-settings (Ubuntu Noble)
Importance: Medium => High
** Changed in: kubuntu-settings (Ubuntu Noble)
Assignee: Erich Eickmeyer (eeickmeyer) => Aaron Rainbolt (arraybolt3)
** No longer affects: kubuntu-settings (Ubuntu Noble)
--
You rece
nevermind, it looks like this is a new bug. I'll file one.
--
You received this bug notification because you are a member of Kubuntu
Bugs, which is subscribed to kubuntu-settings in Ubuntu.
https://bugs.launchpad.net/bugs/1969984
Title:
[SRU] Kubuntu Plymouth Theme Shows Badly on Multi-Screen
I believe bwrap was ignored intentionally, as the point of the apparmor
change was to prevent arbitrary apps from making unprivileged user
namespaces with capabilities. Allowing Bubblewrap to do so would provide
a loophole. Same reason `unshare` isn't allowed to make unprivileged
namespaces with ca
Public bug reported:
Space Grotesk and DM Mono are fonts used in Kubuntu's branding refresh.
As these are intended to be a part of Kubuntu's branding, it is
necessary that these fonts be included in the Kubuntu 24.04 final ISOs.
(IBM Plex is also used in the branding refresh but is already package
** Changed in: kubuntu-meta (Ubuntu)
Milestone: None => ubuntu-24.04
** Changed in: kubuntu-meta (Ubuntu)
Importance: Undecided => High
** Summary changed:
- Package and seed fonts-space-grotesk, fonts-dm-mono, seed fonts-ibm-plex
+ FFe: Package and seed fonts-space-grotesk, fonts-dm-mono
Both of these fonts have now been packaged and uploaded to the NEW
queue. They build without problems and place the fonts in question into
the correct locations. The packaging is based on the packaging for
fonts-cabin (plus some extra guidance from fonts-tlwg-typist for the OTF
vs. TTF font package
Public bug reported:
Steps to reproduce:
1: Install the latest daily image of Kubuntu 24.04.
2: Log into the installed system.
3: Click on the application menu, then click "Shut Down".
Expected result: The Kubuntu logo used as the user's avatar should be
blue on a white background.
Actual resul
** Also affects: kubuntu-installer-prompt (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Kubuntu
Bugs, which is subscribed to kubuntu-settings in Ubuntu.
https://bugs.launchpad.net/bugs/2060845
Title:
New branding Kubuntu
with BGRT, I'll have to check that
out. Thank you!
** Changed in: kubuntu-settings (Ubuntu)
Status: New => Confirmed
** Changed in: kubuntu-settings (Ubuntu)
Assignee: (unassigned) => Aaron Rainbolt (arraybolt3)
--
You received this bug notification because you are a m
Alright, so this is fun. Apparently there's an image full of keyboard
layout labels in Kubuntu's plymouth theme. There also appears to be code
that handles the password prompt, my assumption is that code extracts a
slice of this image to show the keyboard layout to the user. Evidently
it's doing it
Looks like our keymap render image is out-of-date and that's what causes
this. If I copy the keymap-render.png from the `spinner` theme into the
kubuntu-logo theme, things appear to work.
** Changed in: kubuntu-settings (Ubuntu)
Importance: Undecided => Critical
** Summary changed:
- plymouth
Installed Windows 10 Home allowing it to use the entire SSD of my test system.
Booted Kubuntu 24.04 ISO.
Install alongside option appeared, used it.
Installation succeeded.
Upon reboot, I was presented with a GRUB menu, providing both "Ubuntu" and
"Windows Boot Manager" options. Selecting "Ubuntu"
Marking this as High as it is an ugly glitch in an otherwise nicely
refreshed user experience. The fix is trivial and safe.
--
You received this bug notification because you are a member of Kubuntu
Bugs, which is subscribed to kubuntu-settings in Ubuntu.
https://bugs.launchpad.net/bugs/2061313
T
This is happening on the SDDM screen too.
** Changed in: kubuntu-settings (Ubuntu)
Importance: Undecided => Critical
** Changed in: kubuntu-settings (Ubuntu)
Importance: Critical => High
--
You received this bug notification because you are a member of Kubuntu
Bugs, which is subscribed to
The Tor Browser is actually installable on Ubuntu, and we have
privacy-conscious folks here who are Ubuntu Developers. We just were
absolutely slammed in more ways than we imagined would happen this
cycle and things slipped through the cracks. This is probably one of
them.
You can follow the instr
Unless your app and Bubblewrap can both work without any capabilities in
an unprivileged user namespace, things will probably go south. You
should probably be installing an AppArmor profile for your app that
allows you to use unprivileged user namespaces normally again, as
described in Comment 5
(h
Also note that even the system's build of Bubblewrap is not granted the
ability to bypass user namespace restrictions as that would allow the
restrictions to be bypassed by any application. Doing this to your own
build of Bubblewrap will pose the same security issue. If you can avoid
doing things t
This should be fixed in Kubuntu 24.04. We did a significant theming
update and this issue doesn't appear on any systems I've tried the new
theming on.
23.04 is EOL, so it would be recommended to update to 24.04.
** Changed in: kubuntu-settings (Ubuntu)
Status: New => Fix Released
--
You
buntu logo is on a solid-white background that
looks out of place.
** Affects: kubuntu-settings (Ubuntu)
Importance: High
Assignee: Aaron Rainbolt (arraybolt3)
Status: Confirmed
** Affects: kubuntu-settings (Ubuntu Noble)
Importance: High
Status: Fix Committed
Assignee: (unassigned) => Aaron Rainbolt (arraybolt3)
** Also affects: kubuntu-settings (Ubuntu Noble)
Importance: Undecided
Status: New
** Also affects: kubuntu-settings (Ubuntu Oracular)
Importance: High
Assignee: Aaron Rainbolt (arraybolt3)
Status: Confirmed
** Chang
lors needs
to be renamed to /usr/share/kubuntu-default-
settings/kf5-settings/calamaresrc.
** Affects: kubuntu-settings (Ubuntu)
Importance: High
Assignee: Aaron Rainbolt (arraybolt3)
Status: Fix Committed
** Affects: kubuntu-settings (Ubuntu Noble)
Importance: High
** Description changed:
+ [ Impact ]
+ Due to an oversight during the Kubuntu rebrand in the 24.04 cycle, two
Kubuntu logo images were left with a solid white background when they should
have been transparent. This may affect any application that attempts to display
the logo by using /usr/share
** Description changed:
+ [ Impact ]
+ Due to an oversight during the Kubuntu 24.04 rebrand, a file that was
supposed to change the color scheme of the Calamares installer was left named
incorrectly. It is thus not picked up by Calamares at all, and the default
background color of the window is
** Changed in: kubuntu-settings (Ubuntu Oracular)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Kubuntu
Bugs, which is subscribed to kubuntu-settings in Ubuntu.
https://bugs.launchpad.net/bugs/2072163
Title:
Color scheme for Cala
** Changed in: kubuntu-settings (Ubuntu Oracular)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Kubuntu
Bugs, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/2072149
Title:
Kubuntu logo in System Settings has a
** Description changed:
[ Impact ]
Due to an oversight during the Kubuntu 24.04 rebrand, a file that was
supposed to change the color scheme of the Calamares installer was left named
incorrectly. It is thus not picked up by Calamares at all, and the default
background color of the window is
Testing complete, passes as expected. Using version 1:24.04.12, from
noble-proposed.
** Tags removed: verification-needed verification-needed-noble
** Tags added: verification-done verification-done-noble
--
You received this bug notification because you are a member of Kubuntu
Bugs, which is su
Testing complete, passes as expected. Using version 1:24.04.12, from
noble-proposed.
** Tags removed: verification-needed verification-needed-noble
** Tags added: verification-done verification-done-noble
--
You received this bug notification because you are a member of Kubuntu
Bugs, which is su
Public bug reported:
pkgkde-symbolshelper uses Gettext internally. According to the embedded
changelog in Dpkg::Gettext (at /usr/share/perl5/Dpkg/Gettext.pm):
=head2 Version 2.00 (dpkg 1.20.0)
Remove function: _g().
=head2 Version 1.03 (dpkg 1.19.0)
New envvar: Add support for
Heh, this is from the Noble cycle :) The fonts are already packaged
(though in a different way than proposed here) and are shipping on
Kubuntu 24.04 ISOs. Thus I don't think we should redo them in this way
for Oracular. This should probably be wontfixed, though I'll let someone
else from the Kubunt
Public bug reported:
Test hardware is an HP Z220 SFF Workstation, 32 GB RAM, 256 GB SSD.
Testing inside Gnome Boxes, VM is using SeaBIOS, 4 GB RAM. Bug is
showing up in a Kubuntu Kinetic live session with the latest ISO.
Discover version is Discover 5.24.5.
Steps to reproduce:
1: Click the Disco
Public bug reported:
Hardware is an HP Z220 SFF Workstation, 256 GB SSD + 1 TB SSD, 32 GB
RAM, UEFI, no secure boot. Testing was done within a Gnome Boxes VM,
SeaBIOS, 4 GB RAM, Kubuntu Kinetic live session.
Steps to reproduce bug:
1: Open the Application Menu.
2: Type "KSystemLog".
3: Click "KS
Thank you for taking the time to report this bug and helping to make
Ubuntu better. Unfortunately, we cannot work on this bug because your
description didn't include enough information. You may find it helpful
to read "How to report bugs effectively"
http://www.chiark.greenend.org.uk/~sgtatham/bugs
The problem is the lack of blue highlighting. When you click on a menu
item in a system with the Breeze theme, the text turns white, while the
background turns blue. Since the blue highlighting isn't appearing
anymore, the text appears to (mostly) vanish (really it turns white on a
slightly off-whi
This bug doesn't seem to affect Kubuntu, so I'm not sure what exactly is
wrong with Breeze + LXQt. It appears that Breeze and LXQt don't always
work so well together from other discussions, so I'm changing this to a
bug in lubuntu-default-settings so that a quick patch to change the
default theme c
Further research on this bug has confirmed that it is indeed a problem
introduced in a recent change in Breeze. I intend on git bisecting this
today (Central Daylight Time) and hopefully having a fix or at least a
pinpointed commit by tonight or tomorrow.
--
You received this bug notification bec
Enabled -proposed on a VM affected by this bug. Installed the new
ubuntustudio-default-settings, then rebooted. SDDM theme appears to be
working correctly again.
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification because you are a member o
Public bug reported:
Steps to reproduce:
1. Boot the latest Lubuntu Lunar ISO in a virtual machine.
2. Open Discover.
3. Click any application section in the left sidebar (the "Office" section is
the one I'm using).
4. Click on any app.
Expected result: Detailed information about the app should
Public bug reported:
OS: Kubuntu Oracular daily built (latest build at time of this writing)
Steps to reproduce:
1: Boot the latest Kubuntu Oracular ISO.
2: Click "Install Kubuntu".
3: Click "Cancel".
Expected result: Cancel confirmation prompt's window title uses a
normal-looking font.
Actual
Public bug reported:
kubuntu-installer-prompt was supposed to be ported to Qt6 in order to
align with the use of Plasma 6 in Kubuntu. The code doesn't even hardly
need ported, it just needs configured to build against Qt6/KF6, some
deprecated function calls updated, and the method of drawing a
bac
Public bug reported:
OS: Lubuntu Oracular beta release candidate
Steps to reproduce:
* Install Lubuntu
* `sudo apt install falkon`
* Run `falkon`
Expected result: Falkon launches
Actual result: Two errors about being unable to execvp to
/usr/lib/qt6/libexec/QtWebEngineProcess, then a trace/bre
This affects Lubuntu as well. This can slide for beta I think but this
absolutely must be fixed before release.
** Summary changed:
- Kubuntu 24.10: Installer graphics and slideshow still show 24.04 references
and screenshots
+ Kubuntu, Lubuntu 24.10: Installer graphics and slideshow still show
** Also affects: kubuntu-installer-prompt (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Kubuntu
Bugs, which is subscribed to kubuntu-installer-prompt in Ubuntu.
https://bugs.launchpad.net/bugs/2081229
Title:
Strange horiz
Sorry for the very slow reply, been very busy and haven't been checking
my bug mail.
The keyboard layout order is determined by Calamares, or whatever it's
using to set the keyboard layouts. The first layout in that order is the
default, and the user has to explicitly hit a key combo to change it,
(Ubuntu)
** Changed in: debconf-kde (Ubuntu)
Importance: Undecided => Critical
** Changed in: debconf-kde (Ubuntu)
Status: New => Confirmed
** Changed in: debconf-kde (Ubuntu)
Assignee: (unassigned) => Aaron Rainbolt (arraybolt3)
--
You received this bug notification because yo
** Description changed:
[ Impact ]
plasma-distro-release-notifier's distro-preview-upgrade is unable to
popup a test notification, indicating that the notifier is broken. This
will almost certainly mean that people will not be able to upgrade from
Kubuntu 24.10 to Kubuntu 25.04.
** Changed in: plasma-distro-release-notifier (Ubuntu Oracular)
Status: New => In Progress
** Changed in: plasma-distro-release-notifier (Ubuntu)
Status: New => Won't Fix
--
You received this bug notification because you are a member of Kubuntu
Bugs, which is subscribed to plasma-d
27;t have a window for most of the duration of
the upgrade. This is a bug most likely in do-release-upgrade itself, not
a bug in the release notifier itself.
** Affects: plasma-distro-release-notifier (Ubuntu)
Importance: Medium
Assignee: Aaron Rainbolt (arraybolt3)
Status:
** Changed in: plasma-distro-release-notifier (Ubuntu)
Status: Won't Fix => Fix Released
--
You received this bug notification because you are a member of Kubuntu
Bugs, which is subscribed to plasma-distro-release-notifier in Ubuntu.
https://bugs.launchpad.net/bugs/2097029
Title:
Releas
Test plan passed (after editing it to include actually running the test
script with the updated package).
** Description changed:
[ Impact ]
plasma-distro-release-notifier's distro-preview-upgrade is unable to
popup a test notification, indicating that the notifier is broken. This
will
** Description changed:
[ Impact ]
plasma-distro-release-notifier's distro-preview-upgrade is unable to
popup a test notification, indicating that the notifier is broken. This
will almost certainly mean that people will not be able to upgrade from
Kubuntu 24.10 to Kubuntu 25.04.
** Also affects: lubuntu-update-notifier (Ubuntu)
Importance: Undecided
Status: New
** Changed in: lubuntu-update-notifier (Ubuntu)
Importance: Undecided => High
--
You received this bug notification because you are a member of Kubuntu
Bugs, which is subscribed to debconf-kde in Ubu
Also, worthy of note, using the Qt5 KDE frontend did *not* entirely fix
the problem, the update was able to proceed but got hung at a later
stage. This was running it manually with sudo, not through lubuntu-
update, so this has to be the KDE frontend's fault.
--
You received this bug notification
This is the fault of the Qt6 port, I've fallen back to the Qt5 version
and the bug is resolved.
--
You received this bug notification because you are a member of Kubuntu
Bugs, which is subscribed to debconf-kde in Ubuntu.
https://bugs.launchpad.net/bugs/2091704
Title:
Lubuntu-update-notifier f
Could not reproduce this on Debian Sid.
--
You received this bug notification because you are a member of Kubuntu
Bugs, which is subscribed to debconf-kde in Ubuntu.
https://bugs.launchpad.net/bugs/2091704
Title:
Lubuntu-update-notifier fails to update - locale UTF-8 error
To manage notificat
Switched lubuntu-update to use the noninteractive debconf frontend. It's
not as good as the KDE frontend, but it's no more dangerous than what
plasma-discover does AIUI. debconf-kde still needs fixed, but at least
the updater will work now.
** Changed in: debconf-kde (Ubuntu)
Importance: Critic
68 matches
Mail list logo
