Public bug reported:
Test hardware is an Elitebook 8570p, 16 GB RAM, 120 GB SSD.
While reporting Bug #1973469, I discovered that ubuntu-bug was unable to
open Firefox at the very end of the process. Sadly, I closed the
terminal window that contained the initial error, but I was able to
easily
Apologies for the long delay, I've had a lot I was doing.
The command you listed successfully launches Firefox, with
https://ubuntu.com in the address bar, and the Ubuntu website visible.
Note that I'm on the same Kinetic install that I was on when I first
posted the bug report.
--
You received
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"
I added back the "Our analysis" section from the old bug report since it
has a wealth of useful debugging data. Thank you for going to so much
trouble to make this report, all that debugging you did may prove
extremely useful.
** Description changed:
Phenomenon:
After installing the driver
This may sound silly, but try a different USB cable between your printer
and the system. That will help rule out a USB cable problem. (Even
though Windows and macOS don't have this problem, there's still a chance
that the USB cable is at fault.)
--
You received this bug notification because you
And it's happening with multiple printers as well? (Asking to narrow
down where the problem might be)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to cups in Ubuntu.
https://bugs.launchpad.net/bugs/1982551
Title:
Print is
*** This bug is a duplicate of bug 1983000 ***
https://bugs.launchpad.net/bugs/1983000
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
*** This bug is a duplicate of bug 1983000 ***
https://bugs.launchpad.net/bugs/1983000
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
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"
Public bug reported:
Hardware: HP Elitebook 8570p, 16 GB RAM, 120 GB SSD, 3rd Gen Intel Core
i5, UEFI, no secure boot, Broadcom WiFi.
OS: Ubuntu Studio Kinetic, Final ISO
Steps to reproduce:
1. Boot the Ubuntu Studio ISO on a system with Broadcom WiFi, and install the
system normally. (No
I'm not sure if this problem is happening on Linux Mint 21 or Ubuntu
22.04.1. While Linux Mint is based on Ubuntu, it is not the same as
Ubuntu, and may have behaviors (and bugs!) that differ from Ubuntu's.
Could you clarify which Linux distro you're experiencing this problem
on?
--
You received
Public bug reported:
Welp, this is a weird one. Known to affect Ubuntu Server and multiple
flavors of Ubuntu.
Steps to reproduce:
1: If you are shown a graphical login prompt (e.g. GDM or SDDM), switch to a
TTY.
2. At the login prompt, press the up arrow key twice.
3: Press Backspace twice.
4:
Can you try running "sudo apt install firmware-sof-signed" and see if
that resolves the problem?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to alsa-driver in Ubuntu.
https://bugs.launchpad.net/bugs/1991530
Title:
After
Thank you for taking the time to report this bug and helping to make Ubuntu
better. Please execute the following command only once, as it will
automatically gather debugging information, in a terminal:
apport-collect 1983784
When reporting bugs in the future please use apport by using 'ubuntu-
Public bug reported:
Multiple users have recently been reporting strange "out of memory"
errors during early boot. Most notably, the Kubuntu Focus NX system
seems to be unable to boot when the proprietary NVIDIA drivers are
installed for an external NVIDIA GPU. These errors seem to be the result
*** This bug is a duplicate of bug 1842320 ***
https://bugs.launchpad.net/bugs/1842320
Nevermind, I missed that there was an ongoing effort to fix the out of
memory bug. And the thing I'm proposing here wouldn't even work. Marking
this as invalid and a duplicate, sorry about that.
** Changed
@vorlon I just attempted an installation of Ubuntu Desktop 23.04 using
the latest (broken) ISO. I am able to get to the installer since a setup
wizard has me create a user account to get into the live ISO. I saw
multiple "System program problem detected" warnings appear during the
installation,
I believe we have a working patch for the problem. A quick summary of
what it looks like is happening:
Openbox maintains a list of windows organized by stacking order from
highest to lowest. This is a doubly-linked list.
There is a function in Openbox called client_calc_layer that uses a
pointer
One worry I am having with my patch now is, what happens if the first
element is the one being modified? Then itPrev is a null pointer. I
*think* from looking at the GLib code that g_list_next will then return
null when it it handed itPrev, which means "it" will be set to null,
which I believe
New patch, same approach, but with a fallback added if itPrev turns out
to be null.
** Patch added: "glib_crash_bugfix.patch"
https://bugs.launchpad.net/ubuntu/+source/openbox/+bug/2011751/+attachment/5656971/+files/glib_crash_bugfix.patch
--
You received this bug notification because you
Gah, ok, one more try. I failed to update the debian/copyright file last
time. This version has the updated copyright file.
** Patch added: "glib_crash_bugfix.patch"
https://bugs.launchpad.net/ubuntu/+source/openbox/+bug/2011751/+attachment/5657032/+files/glib_crash_bugfix.patch
--
You
After a discussion with dbungert, we're using a different patch instead.
This one is possibly upstream already, which makes it superior to the
original patch I was suggesting since it means less maintenance overhead
in the future.
** Patch added: "glib_crash_bugfix.patch"
Latest patch has requested changes. Bug has been submitted to upstream
Debian here: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1033385
** Bug watch added: Debian Bug tracker #1033385
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1033385
** Patch added: "glib_crash_bugfix_v5.patch"
** Changed in: openbox (Ubuntu)
Assignee: (unassigned) => Aaron Rainbolt (arraybolt3)
** Changed in: glib2.0 (Ubuntu)
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to glib2.0 in
(One extra bit of info that I realized was left out - according to the
comment on the Arch Linux forums here:
https://bbs.archlinux.org/viewtopic.php?pid=2090270#p2090270 the first
loop iteration succeeds. It's not until the second iteration (after the
list has been modified) that the crash
I don't have upload access to this package yet (it's not in the Lubuntu
packageset apparently) so I'm uploading the patch here so that it can be
sponsored.
** Patch added: "glib_crash_bugfix.patch"
OK, so I'm not entirely sure testing the one item case is even possible
since the crash happens when switching from a fullscreen window (which
implies that there are at least two windows). However, this is what I
did, and everything was successful (no crashes).
1. Boot a Lubuntu Lunar ISO, and
@dbungert: While the patch that simply copies the list is a possible way
of doing things, a very experienced user on the Arch Linux forums had
concerns about doing things that way, see
https://bbs.archlinux.org/viewtopic.php?pid=2090570#p2090570 "But
creating a copy of the list is inefficient and
There is now an MP in software-properties that will fix this bug.
https://code.launchpad.net/~arraybolt3/software-
properties/+git/software-properties/+merge/438504
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
** Also affects: software-properties (Ubuntu Lunar)
Importance: Undecided
Status: Triaged
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to software-properties in
Ubuntu.
https://bugs.launchpad.net/bugs/1795278
This bug also affects the latest Jammy daily ISO.
** Also affects: software-properties (Ubuntu Kinetic)
Importance: Undecided
Status: New
** Also affects: software-properties (Ubuntu Jammy)
Importance: Undecided
Status: New
** Changed in: software-properties (Ubuntu Kinetic)
Looks like Sean was right - removing libva-wayland2 and then rebooting
resolved the issue.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/2013071
Title:
Session crash after
Interestingly, I'm not getting any XFCE-related crashes when I use
gnome-boxes rather than QEMU. The process that is crashing is actually
X.
I got a backtrace from it:
(gdb) bt -full
#0 __pthread_kill_implementation (no_tid=0, signo=6, threadid=)
at ./nptl/pthread_kill.c:44
tid =
I notice a blueman-applet crash when I reproduce this.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/2013071
Title:
Session crash after initial login
Status in xorg
Hmm, and now xfce4-power-manager.
Looking at the stacktrace when xfce4-power-manager goes awry, it's
GLib's fault. Which means we probably have another slice allocator
removal causing problems.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which
And there's more random crashes. (xiccd being the next one to go kaput)
All of this in a pure QEMU VM.
My guess is xfce4-power-manager crashes thanks to GLib and that takes
down other stuff at random. Not sure how that would be triggered by the
third-party software option, but that's what I'm
I can't reproduce this on Ubuntu MATE (though I can make other things
crash sadly).
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/2013071
Title:
Session crash after initial
I see the same segmentation fault that fossfreedom points out also
happening in my Ubuntu MATE logs (which are in
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/2012159 which is
a dupe of this). My very first guess is that this is that GLib update
messing us up again with the removed
I can verify that the latest version of Ubiquity from -proposed fixes
this problem - I booted Ubuntu Desktop 22.04.1, enabled -proposed on the
ISO, installed Ubiquity from -proposed, then did a ZFS+encryption
installation. Rebooted, logged in, "sudo apt update" behaves normally,
Firefox launches
Could you try changing the permissions back to something more strict
(maybe 0600), and then changing ownership to the `apt` user/group?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in Ubuntu.
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 Ubuntu
Touch seeded
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
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 Ubuntu
Touch seeded packages, which is subscribed to apparmor in Ubuntu.
https://bugs.launchpad.net/bugs/2046844
Title:
AppArmor user namespace
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 Ubuntu
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
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
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
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
Public bug reported:
Lubuntu uses Qt as the primary framework for most of the apps we ship.
However, some functionality we ship in Lubuntu doesn't have a Qt
application that provides that functionality, so we have some GTK3 apps
that we ship as well. Starting in Lubuntu 24.04, we are adding and
Can confirm this looks awful in Konsole and even more awful in
Konsole+tmux.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to vim in Ubuntu.
https://bugs.launchpad.net/bugs/2047982
Title:
Highlighting of patches offers
Will do. You'll have to forgive me, I was on a six-month hiatus from
Ubuntu development and wasn't around to verify it at that time. I have
the needed hardware though.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
Followed the test plan using the latest daily image of Ubuntu Studio
Jammy. Everything worked as expected (no error in terminal when
selecting "Using Broadcom 802.11 Linux STA wireless driver from bcmwl-
kernel-source (proprietary)"), driver installed properly and allowed me
to connect to WiFi.
This does NOT occur on Noble. Trying it there, the following happens
(note that I allowed debuginfod to be used but I'm not sure if that
makes any difference):
```
(gdb) print strlen(statstr)
'strlen' has unknown return type; cast the call to its declared return type
(gdb) print
Public bug reported:
Steps to reproduce:
1: Create a file `test.c` with the following very simple program:
#include /* for printf */
#include /* for strlen */
int main(int argc, char **argv) {
const char *statstr = "hello there!";
printf("%s\n", statstr);
}
Public bug reported:
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
** Also affects: ubuntu-meta (Ubuntu Noble)
Importance: Undecided
Status: New
** Also affects: wslu (Ubuntu Noble)
Importance: Undecided
Status: New
** Changed in: ubuntu-meta (Ubuntu Noble)
Milestone: None => ubuntu-24.04
** Changed in: wslu (Ubuntu Noble)
I assume you didn't install Kubuntu Noble on a VM due to a Calamares bug
who's fix isn't managing to migrate out of -proposed. There's a fairly
easy workaround for that issue (`vim /lib/x86_64-linux-
gnu/calamares/modules/networkcfg/main.py`, search for "0o" via `/0o` and
then change the `f` to
** Summary changed:
- All Snaps are denied the ability to use DBus for notifications and apptray
indicators
+ All Snaps are denied the ability to use DBus for notifications and apptray
indicators in Kubuntu
** Summary changed:
- All Snaps are denied the ability to use DBus for notifications
I might try to SRU it into Jammy eventually (perhaps after the release
of Noble), but Focal is now unsupported from the perspective of all
flavors and I don't think Ubuntu Desktop has any use for software-
properties-qt as it has software-properties-gtk (I believe). Marking
Focal as Won't Fix for
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
We rewrote the update notifier in Qt/C++ and got rid of the aptdaemon
dependency earlier in the Noble cycle, so this is now resolved in Noble.
** Changed in: lubuntu-update-notifier (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member
** Changed in: unity-scope-home (Ubuntu)
Status: New => In Progress
** Changed in: unity-lens-music (Ubuntu)
Status: Fix Committed => In Progress
** Changed in: unity-lens-files (Ubuntu)
Status: Fix Committed => In Progress
** Changed in: unity-lens-applications (Ubuntu)
unity-lens-video is building just fine, marked as invalid. The other
four are suffering from Vala incompatibilities and I'm working through
them now.
** Changed in: unity-lens-applications (Ubuntu)
Status: New => Fix Committed
** Changed in: unity-lens-files (Ubuntu)
Status: New =>
63 matches
Mail list logo
