Public bug reported:
/home/frank/Downloads# dpkg -i base-passwd_3.5.52build1_amd64.deb
(Reading database ... 236425 files and directories currently installed.)
Preparing to unpack base-passwd_3.5.52build1_amd64.deb ...
Unpacking base-passwd (3.5.52build1) over (3.5.52build1) ...
Setting up
Thanks for the bug report. Next time the problem happens, after
rebooting please run:
journalctl -b-1 > prevboot.txt
and attach the resulting text file here.
** Package changed: xorg (Ubuntu) => ubuntu
** Changed in: ubuntu
Status: New => Incomplete
--
You received this bug
Thanks for the bug report.
It appears you're using the old unsupported (and buggy) 'intel' graphics
driver. Please remove any config files you have loading that and even
consider removing the entire driver:
sudo apt remove xserver-xorg-video-intel
Alternatively, please just log into 'Ubuntu'
okay, I can reproduce this issue in Xorg as well.
`stress-ng --stack 0 --timeout 300` and I can see
Tue Aug 16 03:13:49 PM CST 2022
./memory.pressure
some avg10=64.25 avg60=28.75 avg300=7.33 total=23575913
full avg10=62.74 avg60=28.13 avg300=7.17 total=23107632
systemd-oomd doesn't care about the slices other than user slice, it's
why the sshd won't be killed but it also use a lot of memory:
/sys/fs/cgroup/user.slice/user-1001.slice/session-4.scope/memory.pressure
some avg10=69.94 avg60=69.56 avg300=43.64 total=202010660
full avg10=69.07 avg60=68.73
Public bug reported:
happened on startup
ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: linux-image-5.14.0-1048-oem 5.14.0-1048.55
ProcVersionSignature: Ubuntu 5.15.0-46.49~20.04.1-generic 5.15.39
Uname: Linux 5.15.0-46-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.24
Architecture:
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.
Hello Heinrich,
yes, very gladly.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ifupdown in Ubuntu.
https://bugs.launchpad.net/bugs/1907878
Title:
wrong var declaration in if-up.d/resolved (nm-dispatcher[54417]:
@tjaalton it's 21.2.6-0ubuntu0.1~20.04.2 in focal:
https://launchpad.net/~ubuntu-security-proposed/+archive/ubuntu/ppa/+build/23235579
https://launchpad.net/ubuntu/+source/mesa
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
Public bug reported:
Hi,
https://discourse.ubuntu.com/t/phased-updates-in-apt-in-21-04/20345
describes Dir::Etc::machine-id, APT::Get::Always-Include-Phased-Updates
and APT::Get::Never-Include-Phased-Updates. I expected these to be
documented in apt.conf(5) which I treat as a definitive
Public bug reported:
ubuntu-bug on Kinetic Kudu crashes with:
$ ubuntu-bug
Traceback (most recent call last):
File "/usr/share/apport/apport-kde", line 19, in
import sip
ModuleNotFoundError: No module named 'sip'
During handling of the above exception, another exception occurred:
Just to be clear: apt.conf(5) is not the definitive source, that is
(fsvo reference) in /use/share/doc/examples/configure-index. The manual
page only documents popular options whereas the index lists them all
(apt test suite type checks against it).
Phased updates are documented in
And I can confirm that the patch at
https://bugzilla.mindrot.org/attachment.cgi?id=3581 applies cleanly and
fixes this issue.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssh in Ubuntu.
Looking at apt.conf(5), it does read as if it's the definitive
reference, too, and the examples file is just an example.
--
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/1986660
That's not really discoverable as a reference though. I wouldn't expect
"examples" to contain a definitive reference, and nor a Discourse post
about a feature that as far as I know isn't pointed to from any
definitive documentation. Same with apt_preferences - I do expect to
find information about
I was not able to make the .link approach work, even in an installed
environment. I fought with it for a while during spurts of machine
access. Without that, I was not able to move on to the next step of
trying to insert it into a commissioning script.
--
You received this bug notification
oh right, 22.0.5 hasn't been backported yet
anyway, if llvm is enabled, it'll essentially break swrast for riscv64..
if that's a tradeoff you can live with, then okay
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mesa in
*** This bug is a duplicate of bug 1980553 ***
https://bugs.launchpad.net/bugs/1980553
** This bug has been marked a duplicate of bug 1980553
/usr/share/apport/apport-kde:NameError:/usr/share/apport/apport-kde@19:/usr/share/apport/apport-kde@58
--
You received this bug notification
openldap@jammy also needs no further changes
** Changed in: openldap (Ubuntu Jammy)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openldap in Ubuntu.
Hello Jeremy, or anyone else affected,
Accepted glib2.0 into jammy-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/glib2.0/2.72.3-0ubuntu1 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
openldap in kinetic needs no further changes, marking that task as fix
released.
** Changed in: openldap (Ubuntu)
Status: Confirmed => Fix Released
** Also affects: cyrus-sasl2 (Ubuntu Jammy)
Importance: Undecided
Status: New
** Also affects: openldap (Ubuntu Jammy)
This upstream fix for this was backported to 251.4, which I am currently
working on merging from Debian.
** Changed in: systemd (Ubuntu Kinetic)
Status: Triaged => In Progress
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
** Changed in: binutils (Ubuntu)
Importance: Undecided => Medium
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to binutils in Ubuntu.
https://bugs.launchpad.net/bugs/1974265
Title:
`demangle_const` causes infinite
yes, it same as what I understand.
systemd-run and over ssh could have a session out of monitored by systemd-oomd.
I'm trying to understand if any use cases will similar to this case?
something like launching a lot of tabs from chrome/firefox browsers, I suppose
all tabs will belong to same
Someone needs to update gst-plugins-bad1.0 to not depend on this before
the removal can proceed.
** Also affects: cog (Ubuntu)
Importance: Undecided
Status: New
** Also affects: gst-plugins-bad1.0 (Ubuntu)
Importance: Undecided
Status: New
** Changed in: wpewebkit (Ubuntu)
** Also affects: firefox (Ubuntu)
Importance: Undecided
Status: New
** Also affects: firefox via
https://bugzilla.mozilla.org/show_bug.cgi?id=1784977
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a member of Ubuntu
Touch seeded
Closed it first because I can not find any normal use case as what stress-ng
did.
Feel free to reopen and investigating if any normal use case got "being ...% >
50.00% for > 20s with reclaim activity".
** Changed in: systemd (Ubuntu)
Status: New => Invalid
** Changed in: oem-priority
** Merge proposal linked:
https://code.launchpad.net/~enr0n/ubuntu/+source/systemd/+git/systemd/+merge/428423
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1979952
Just had this message on Ubuntu 22.04.1 (5.15.0-46-generic) - was unable
to boot. Related or not, the suggesting to update /etc/fstab in the
comments above got me able to boot again.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
alright, although the children are belong to same cgroup but
> as a measurement of the CPU time lost due to lack of memory.
it seems to me there is no a normal case from users will hit it unless
memory stressors.
--
You received this bug notification because you are a member of Ubuntu
Touch
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: alsa-driver (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to alsa-driver in Ubuntu.
** Changed in: evolution (Ubuntu)
Assignee: (unassigned) => Nathan Teodosio (nteodosio)
** Changed in: gtk+3.0 (Ubuntu)
Assignee: (unassigned) => Nathan Teodosio (nteodosio)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
Public bug reported:
error with dpkg and base-files..12ubuntu.amd64.deb
ProblemType: Package
DistroRelease: Ubuntu 22.04
Package: base-files 12ubuntu4.1
ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39
Uname: Linux 5.15.0-46-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.1
AptOrdering:
Fixed upstream:
https://github.com/canonical/apport/commit/64820a0e2de0065d2ce08592bd1765169656c716
** Changed in: apport
Status: New => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apport in Ubuntu.
The issue exists in the Firefox snap as well:
https://bugzilla.mozilla.org/show_bug.cgi?id=1784977
** Bug watch added: Mozilla Bugzilla #1784977
https://bugzilla.mozilla.org/show_bug.cgi?id=1784977
--
You received this bug notification because you are a member of Ubuntu
Touch seeded
Upstream feature request: https://github.com/canonical/lightdm/issues/95
** Bug watch added: github.com/canonical/lightdm/issues #95
https://github.com/canonical/lightdm/issues/95
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
** Changed in: evolution (Ubuntu)
Importance: Undecided => Medium
** Changed in: gtk+3.0 (Ubuntu)
Importance: Undecided => Medium
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu.
Looks like the specific upstream issue is
https://github.deere.com/FOCUS/WineATL/blob/fab575865d1bbceedde12226d2517d17b20189bc/gdb/wine-
add-symbol-file.py
And there's a build for kinetic that contains the fix, which does
actually install and work on jammy (since no other dependencies changed
too
Thanks for the information you provided. I set up a Ubuntu Jammy VM with
ssh and dnsmasq running and unfortunately I cannot reproduce it just
with that. There might be something else happening in your system.
If you could provide information about all processes running in your
system when this
This does not look like an Ubuntu bug. You have the most recent jammy
version of dpkg installed on your system according to your bug report,
however the upgrade failure shows an internal error when trying to
invoke 'dpkg --valiate-version' from dpkg-maintscript-helper.
What does `which dpkg`
** Merge proposal linked:
https://code.launchpad.net/~ahasenack/ubuntu/+source/cyrus-sasl2/+git/cyrus-sasl2/+merge/428422
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openldap in Ubuntu.
*** This bug is a duplicate of bug 1889443 ***
https://bugs.launchpad.net/bugs/1889443
This bug is fixed by
https://github.com/canonical/apport/commit/64820a0e2de0065d2ce08592bd1765169656c716
So I will mark this bug as duplicate of bug #1889443.
** This bug has been marked a duplicate of
Can reproduce on Jammy.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ifupdown in Ubuntu.
https://bugs.launchpad.net/bugs/1986536
Title:
Running ifup@ for all interfaces breaks no-auto-down
Status in ifupdown package in
** Description changed:
kdesu fails to authenticate with sudo from Jammy.
See upstream bug: KDE bug: https://bugs.kde.org/show_bug.cgi?id=452532
Examples: Launch Kubuntu driver manager from system setting, launching
ksystemlog from the main menu, or trying to run krusader root mode
Spent the whole morning on it and finally figured it out—I had dnsmasq looking
at the wrong DNS server because it was looking at the wrong resolv.conf:
⏵ cat /var/run/NetworkManager/resolv.conf
# Generated by NetworkManager
nameserver 127.0.0.53
I remember now that early on there
Yeah many options are not really for end users though so it's not all
encompassing.
--
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/1986660
Title:
Phased update configuration
I suppose we may need to work with a PPA then.
@xypron what do you think?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1980386
Title:
`radeonsi_dri.so` driver missing on
It seems that systemd-oomd is doing what it is supposed to do -- you're
running a memory stress test that is exceeding the memory pressure
limits set by systemd-oomd, so it is killing the offending cgroup(s). If
you want to run the stress tests in a separate cgroup, try making a
script called e.g.
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: gtk+3.0 (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu.
49 matches
Mail list logo
