** Changed in: initramfs-tools (Debian)
Status: Unknown => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1950996
Title:
Missing all modules fo
** Changed in: apport (Ubuntu)
Status: Confirmed => Triaged
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apport in Ubuntu.
https://bugs.launchpad.net/bugs/1315559
Title:
UpgradeStatus can be incorrect
Status in a
That was firefox packaged as a deb, right?
This issue is specifically with snaps.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lightdm in Ubuntu.
https://bugs.launchpad.net/bugs/1593407
Title:
Guest session cannot run sn
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: policykit-1 (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to policykit-1 in Ubuntu.
https://bugs.lau
I am experiencing the same issue on Ubuntu 20.04.4 with the below polkit
config, where sysapp is an LDAP group, and we are using SSSD for LDAP
login to our machines.
# This file is managed by Puppet. DO NOT EDIT.
[Configuration]
AdminIdentities=unix-group:sysapp;unix-group:sudo;unix-group:admin
Thanks for reporting this bug. It should not have happened that your
patch got unaddressed for so long.
I checked /etc/sudoers in Ubuntu 22.04 and it is correct there: the last
line is "@includedir /etc/sudoers.d". So I mark this bug as fixed.
** Changed in: sudo (Ubuntu)
Status: Incomplet
The upstream patch got applied as commit
b121da2e21cabd2793fc423d84ceddd919fd6e47 and was released in sudo
1.8.11. Therefore this bug is fixed since Ubuntu 16.04 (xenial).
** Changed in: sudo (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are
As with comment #41, #44, and #45, has the decision been made to fix
grub2's memory issues or just the compression level change that was with
initramfs (as I believe it was a choice made to increase Raspberry Pie
boot times)?
--
You received this bug notification because you are a member of Ubunt
Hi, I tried to check all sudo bugs with attached patches. Sadly the
upstream bug link is broken. So I cannot follow-up the upstream
progress. The git history revealed no reference to bug number 457.
Looking at the upstream code, I found following in
lib/eventlog/eventlog.c:
#if defined(HAVE_NL_LA
Thanks for reporting this issue and for providing steps to reproduce.
I tried to reproduce it on Ubuntu 22.04 (jammy) and added a
"#--ariel--#" comment line to my sudoers file. sudo correctly ignore it.
So I mark this bug as fixed.
** Changed in: sudo (Ubuntu)
Status: Confirmed => Fix Rele
** Changed in: sudo (Ubuntu)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to sudo in Ubuntu.
https://bugs.launchpad.net/bugs/1915789
Title:
sudo: /usr/bin/sudo must be owned by u
** Summary changed:
- Incorrect Sudo configuration
+ sudoers: admin group has permissions, but does not exist by default
** Changed in: sudo (Ubuntu)
Status: Confirmed => Triaged
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subs
In case it's relevant...
I bricked my old PC while trying to work around this bug(!). After
putting the same RAM and plugging the same monitor into a new machine,
the bug does not occur. So the trigger for the bug was more to do with
the old machine's firmware.
--
You received this bug notificat
Thanks for reporting this issue. Since you need to be root to create a
new user, this can probably not be used directly as exploit. But I agree
that creating a user "admin" should not create one that is in the admin
group. So either removing this configuration line or create a admin
group by defaul
I see a similar (same?) issue: if I say a bug is display-related, apport
collecting problem information hangs ~20% through the process and
neither "Cancel" nor (x) can stop the process. Cancel in the parent
window helps.
This is on 20.04.
--
You received this bug notification because you are a m
Yes, grub will be fixed eventually, but we are blocked by the security
update not being out yet. This is not a blocker for enabling upgrades to
22.04.1, as it only affects a small number of systems and grub fixes
itself by using the previous kernel version if the new one fails.
--
You received th
@Tomislav, can you report a separate bug? My gut feeling is that you
experienced a different issue (with similar symptoms).
@Peter, sadly the stack trace posted only contains threading.py and
nothing from apport itself. So I have not enough information to fix this
bug without a test case. Can you
** Also affects: sudo (Ubuntu Jammy)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to sudo in Ubuntu.
https://bugs.launchpad.net/bugs/1958055
Title:
sudo apport-kde is in a differe
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: initramfs-tools (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu.
https://
The relevant log is:
zstd: error 25 : Write error : No space left on device (cannot write compressed
block)
So you ran out of free space to update your initramfs.
** Summary changed:
- package initramfs-tools 0.140ubuntu13 failed to install/upgrade:
»installiertes initramfs-tools-Skript des Pa
Public bug reported:
This is a fresh Ubuntu 22.04 installation in a VM used for debugging bug
#1979159. I had modified some files, but checked with "sudo debsums -ac"
that I reverted all local changes. The failure still happens after the
reboot.
$ LANG=C sudo update-initramfs -u
update-initramfs:
...and I found the culprit: My fiddling around left a file name
/usr/share/initramfs-tools/hooks/cryptroot.orig which was executed by
update-initramfs too.
** Changed in: initramfs-tools (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubun
it appears phased upates are everywhere and not just with proposed repos... so
although the bug might be against the wrong package filed (feel free to
reassign to somewhere else). there's a bug
lacking information how to properly opt out of phased updates.
which is pointless to take part of if t
** Changed in: apt (Ubuntu)
Status: In Progress => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in Ubuntu.
https://bugs.launchpad.net/bugs/1981672
Title:
apt phased out broken code, missing document
It's documented in the discourse thread (Discourse is where Ubuntu
documentation lives) You have not provided evidence that it does not
work for you. APT itself has test cases that proof that *it does* work.
Note that newer apt versions (2.4.6, 2.5.1) will install more phased
updates
- as phasing
I recall/see again a mention of aptitude:
aptitude and aptitude-robot are not supported components. They are
packages provided by the community as part of the universe repository.
While the implementation of phased updates in apt versions prior to
2.4.6 would work there, the current version does
I have added an aptitude task and set the tasks accordingly to indicate
that this is a feature request for aptitude. The needed API will surface
at some point in APT due to some refactoring, likely in the 23.04 cycle.
aptitude could then consume that API in its resolver and make choices to
keep ba
Hi Julian,
Julian Andres Klode wrote:
> aptitude is not a reliable tool that respects your choices like that
> (its solver will happily suggest solutions violating your wishes; it
I have to object here. It very well respects the user's wishes and
also has a setting where the user can configure it
To make it clear, my suggestion for a workaround for jammy would be to
have
_config->CndSet("APT::Get::Phase-Policy", true);
somewhere in the aptitude code. It is unclear to me if aptitude will
break then as phased versions get their pin limited to 1, apt certainly
does if there's a mismatch as i
Hi Julian,
Julian Andres Klode wrote:
> Do note that aptitude is mostly unmaintained these days.
I have to object here as well:
There's no development currently, but it is _not_ unmaintained. (And
the current RC bug in Debian will soon be addressed. I'm just back
from holidays.)
** Changed in: cyrus-sasl2 (Ubuntu Impish)
Status: Triaged => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to cyrus-sasl2 in Ubuntu.
https://bugs.launchpad.net/bugs/827151
Title:
Annoying log message "DIGES
** Also affects: dh-python (Ubuntu Focal)
Importance: Undecided
Status: New
** Changed in: dh-python (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to dh-python in Ubuntu.
h
I tried reinstalling all the packages, even the python ones and nothing
worked. So I read the code in /lib/python3/dist-
packages/softwareproperties/gtk/SoftwarePropertiesGtk.py and commenting
out line 222 everything worked again!!! self.backend.Reload(); --> #
self.backend.Reload();
--
You recei
I did some testing to confirm this is present in jammy (the offending
code is also in kinetic). I will test the upstream fix soon.
** Tags added: rls-jj-incoming rls-kk-incoming
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
What's the user impact here please? Just noisy logs, or are users
impacted in a more meaningful way? The downside here is that a rebuild
of apparmor is going to result in virtually every Ubuntu Bionic user
having to download and install an update. The vast majority of whom
aren't using dovecot, or
>From an SRU perspective bug 1703821 is similar to this, except for
dovecot in Bionic. In both cases, a workaround is trivially available
since a user can safely modify the profile directly in /etc.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, wh
Please also fix the bug status for the Ubuntu development release
apparmor package task.
--
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/1703821
Title:
Dovecot and Apparmo
Bug 1979879 is similar to this, except for samba in Jammy. In both
cases, a workaround is trivially available since a user can safely
modify the profile directly in /etc.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmo
** Changed in: qtbase-opensource-src (Ubuntu)
Status: Triaged => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to qtbase-opensource-src in
Ubuntu.
https://bugs.launchpad.net/bugs/1980210
Title:
[SRU] Unab
I lost all sound devices recently using Kubuntu 22.04 and the 5.18
kernel on my Legion 7 16ACHg6. Following this guide restored my devices:
https://pipewire-debian.github.io/pipewire-debian/
Note: I installed all of the recommended wireplumber and BT options as
well as the pipewire packages.
*** This bug is a duplicate of bug 1969460 ***
https://bugs.launchpad.net/bugs/1969460
** Information type changed from Private to Public
** This bug has been marked a duplicate of bug 1969460
software-properties-gtk crashed with TypeError in
on_driver_selection_changed(): Expected a stri
*** This bug is a duplicate of bug 1969460 ***
https://bugs.launchpad.net/bugs/1969460
** This bug is no longer a duplicate of bug 1968661
software-properties-gtk crashed with TypeError in
on_driver_selection_changed(): Expected a string or a pair of strings
** This bug has been marked a d
*** This bug is a duplicate of bug 1969460 ***
https://bugs.launchpad.net/bugs/1969460
** This bug is no longer a duplicate of bug 1968661
software-properties-gtk crashed with TypeError in
on_driver_selection_changed(): Expected a string or a pair of strings
** This bug has been marked a d
*** This bug is a duplicate of bug 1969460 ***
https://bugs.launchpad.net/bugs/1969460
** This bug is no longer a duplicate of bug 1968661
software-properties-gtk crashed with TypeError in
on_driver_selection_changed(): Expected a string or a pair of strings
** This bug has been marked a d
*** This bug is a duplicate of bug 1969460 ***
https://bugs.launchpad.net/bugs/1969460
** This bug is no longer a duplicate of bug 1968661
software-properties-gtk crashed with TypeError in
on_driver_selection_changed(): Expected a string or a pair of strings
** This bug has been marked a d
*** This bug is a duplicate of bug 1969460 ***
https://bugs.launchpad.net/bugs/1969460
** This bug is no longer a duplicate of bug 1968661
software-properties-gtk crashed with TypeError in
on_driver_selection_changed(): Expected a string or a pair of strings
** This bug has been marked a d
*** This bug is a duplicate of bug 1969460 ***
https://bugs.launchpad.net/bugs/1969460
** This bug is no longer a duplicate of bug 1968661
software-properties-gtk crashed with TypeError in
on_driver_selection_changed(): Expected a string or a pair of strings
** This bug has been marked a d
** Changed in: sudo (Ubuntu)
Importance: Undecided => Medium
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to sudo in Ubuntu.
https://bugs.launchpad.net/bugs/1843829
Title:
sudoers: admin group has permissions, but does n
This message doesn't seem to affect anything, from what I can tell.
Here's a technical analysis.
The system call, sched_setattr, is being made in glib's
g_system_thread_get_scheduler_settings. It gets the current scheduling
settings, and then tests to make sure it can set them on the same
thread.
You have been subscribed to a public bug:
When totem crashes and I try to report the crash with ubuntu-bug, one of
two things happens:
1) Sometimes after the dialog pops up and I click the "Send" button,
ubuntu-bug immediately exits without doing anything:
jik@jik5:~$ ubuntu-bug /var/crash/_usr_
** Package changed: totem (Ubuntu) => apport (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apport in Ubuntu.
https://bugs.launchpad.net/bugs/1983481
Title:
Can't report totem crash with ubuntu-bug
Status in appo
You have been subscribed to a public bug:
Not sure if it's relevant, but there are some errors in dmesg:
$ sudo dmesg | grep audio
[ 14.290226] snd_hda_intel :01:00.1: Handle vga_switcheroo audio client
[ 14.440430] sof-audio-pci-intel-tgl :00:1f.3: DSP detected with PCI
class/subcl
** Package changed: ubuntu => alsa-driver (Ubuntu)
--
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/1983529
Title:
No sound after upgrade to prerelease Kinetic (Thinkpad
53 matches
Mail list logo
