I removed a bunch of stuff I did not really need, game servers, xorg-
xserver drivers for hardware I did not have, kvm-qemu stuff that I have
not used on this machine since last July, tor, and after getting rid of
a bunch of cruft, it does reboot properly so now I have to figure out
which
Public bug reported:
This server has a new install of Ubuntu 18.04 server. Sometimes (around
50% of the time) when it boots systemd-networkd.service initially fails
to start with an error as below. It then tries again and succeeds,
however other services which depend on systemd-networkd have
This bug was fixed in the package software-properties - 0.98.9.5
---
software-properties (0.98.9.5) focal; urgency=medium
* cloudarchive: Enable support for the Xena Ubuntu Cloud Archive on
20.04 (LP: #1926796).
-- Corey Bryant Fri, 30 Apr 2021 14:13:30
-0400
** Changed
The verification of the Stable Release Update for software-properties
has completed successfully and the package is now being released to
-updates. Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that
I accidentally saved the reboot image attachment before I completed the
comment, so that's where
it hangs. This time I only waited about a minute and a half before holding
down control+alt+del to force the reboot, but I've walked away for an hour and
let it sit, it does not finish beyond this
** Attachment added: "Picture of Monitor at please reboot hangs."
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1928564/+attachment/5498329/+files/reboot.png
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
This bug was fixed in the package python-apt - 2.2.0~ubuntu0.21.04.1
---
python-apt (2.2.0~ubuntu0.21.04.1) hirsute; urgency=medium
* Upload to hirsute; changes since 2.1.7ubuntu2:
- Annotate test dependencies with (Closes: #980719)
- Mirror list updates
- debfile:
I accidentally saved the reboot image attachment before I completed the
comment, so that's where
it hangs. This time I only waited about a minute and a half before holding
down control+alt+del to force the reboot, but I've walked away for an hour and
let it sit, it does not finish beyond this
** Attachment added: "Log of what happened after I typed systemctl reboot"
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1928564/+attachment/5498328/+files/logs
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
I tested and upgrade from a Bionic system to Focal using do-release-
upgrade -p and as you can see in the attached screenshot the "Inhibiting
until Ctrl+C is pressed" message no longer appears. So I'm setting this
to verification-done.
** Attachment added: "bug-1898026-focal-verification.png"
Tested on: Ubuntu 21.04
Package: evolution-data-server 3.40.1-2 (from Impish-proposed)
There aren't packages for hursuit (21.04) but I just tried the impish
(21.10) package and works.
Thanks again
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages,
Unfortunately it seems like this bug has resurfaced.
For reference, it looks like this may have also been fixed here:
https://aur.archlinux.org/packages/gtk3-typeahead/
Any chance this regression will be repatched for Ubuntu 20.04?
This bug is related to the removal of type-ahead in nautilus:
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.
This bug was fixed in the package db5.3 - 5.3.28+dfsg1-0.8ubuntu1
---
db5.3 (5.3.28+dfsg1-0.8ubuntu1) impish; urgency=low
* Merge from Debian unstable (LP: #1927978). Remaining changes:
- SECURITY UPDATE: Heap out-of-bounds read
- debian/patches/CVE-2019-8457.patch:
This kernel also does not produce sound from the bottom bass speakers
--
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/1926165
Title:
Bass speakers not enabled on
On 2021-05-17 16:06, Rüdiger Kupper wrote:
> Is this issue related to Bug #1890905?
Well, it was me who suggested that. Maybe I should rather have pointed
to the rather old bug #1423890, which includes a link to a mailing list
discussion.
--
You received this bug notification because you are a
The upstream ABI of libjsoncpp has changed, and libjsoncpp1 is not
available in later releases. The project you point to has a buggy
bootstrap script, it should be pointing at libjsoncpp-dev only, not at a
specific soname of the runtime library.
** Changed in: libjsoncpp (Ubuntu)
Status:
Here it is.
** Attachment added: "alsa-project.org.txt"
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1926165/+attachment/5498257/+files/alsa-project.org.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
@mvo Please keep this bug updated and/or notify me when snapd is ready
for the switch. Ideally way before 21.10 Feature Freeze.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lxc in Ubuntu.
Public bug reported:
Machine details:
Hardware: Raspberrypi4B
OS: ubuntu 21.04
Issue: when trying to install openthread as per the installation procedure in
the path: https://openthread.io/codelabs/openthread-border-router#1
it fails to install libjsoncpp1.
When tried to install via
** Also affects: apt (Ubuntu Bionic)
Importance: Undecided
Status: New
** Also affects: apt (Ubuntu Hirsute)
Importance: Undecided
Status: New
** Also affects: apt (Ubuntu Focal)
Importance: Undecided
Status: New
** Also affects: apt (Ubuntu Impish)
Importance:
I'm running fedora 34, but I'm more then happy to install ubuntu back
today and try these kernels if it will help resolve the issue. Just
need some time to get that done.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
This looks an awful lot like bug 1875577 and from reading the latest
comments it seems like that was never fixed in focal.
Colin did you ever get focal updated with the fix for bug 1875577?
** Package changed: systemd (Ubuntu) => zfs-linux (Ubuntu)
--
You received this bug notification because
** Tags removed: verification-needed verification-needed-focal
** Tags added: verification-done verification-done-focal
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unattended-upgrades in
Ubuntu.
Public bug reported:
[Impact]
The cdrom media change prompt hangs on EOF. This causes the autopkgtest to hang
when run in a debian lxd container for unknown reasons related to lxd/systemd
isolation likely (it works fine in Ubuntu), but it's also surprising behavior
in general.
[Test plan]
We
> This is a valid issue, but are we certain it's the same one? The
> reporter talked about sched_yield and their backtraces included several
> threads of back_monitor waiting on some kind of lock.
You're right. It may be a different issue (though possibly linked to the
same root cause). In my
Is this issue related to Bug #1890905?
--
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/1856738
Title:
access always denied when using @{HOME} tunable in peer_addr for
** Information type changed from Public to Public Security
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openldap in Ubuntu.
https://bugs.launchpad.net/bugs/1926265
Title:
slapd enter in infinite loop on sched_yield
Unfortunately I can only run live cd:s on this machine due to reasons.
Maybe someone else with the issue can give it a go?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to alsa-driver in Ubuntu.
I have TWO unrelated machines one a KVM-Qemu virtual machine, and one
my physical workstation, both exhibit this behavior. I'll try to get some
logs for you.
-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-
Eskimo North Linux Friendly Internet Access, Shell
No, this bug was submitted from the GUI. By that point, I'd already killed
the second systemd. You could say I have a chicken and egg problem.
On Mon, May 17, 2021, 14:30 Dan Streetman <1928...@bugs.launchpad.net>
wrote:
> I don't see anywhere in your dmesg where systemd is 'running twice', you
I don't see anywhere in your dmesg where systemd is 'running twice', you
probably should attach your boot/journal logs that show the problem.
** Changed in: systemd (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Touch seeded
sudo systemctl reboot works fine for me. You should check your logs to
see what hung your reboot, or attach your journal logs from a boot where
you reproduced the problem.
** Changed in: systemd (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a
Please install, reboot and test this testing kernel.
https://people.canonical.com/~hwang4/lp1926165/
And generate and upload the alsa-info.txt with the testing kernel.
thx.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
Dual pointers doesn't sound like a bug because you probably have dual
pointing input devices.
As for the tracking speed, does selecting 'Ubuntu on Xorg' from the
login screen fix that?
** Tags added: wacom
** Package changed: xorg (Ubuntu) => mutter (Ubuntu)
** Changed in: mutter (Ubuntu)
Testing former status with 5.11.0-17-generic
Journal:
Add:
May 17 05:56:26 h kernel: crw_info : CRW reports slct=0, oflw=0, chn=1, rsc=3,
anc=0, erc=4, rsid=5
May 17 05:56:26 h kernel: crw_info : CRW reports slct=0, oflw=0, chn=0, rsc=3,
anc=0, erc=4, rsid=0
May 17 05:56:26 h kernel: virtio_blk
*** This bug is a duplicate of bug 1928475 ***
https://bugs.launchpad.net/bugs/1928475
Thank you for taking the time to report this bug and helping to make
Ubuntu better. This particular bug has already been reported and is a
duplicate of bug 1928475, so it is being marked as such. Please
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: ubuntu-meta (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu.
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: ubuntu-advantage-tools (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu.
** Summary changed:
- Can not wake up after sleep.
+ Can not wake up after sleep using 5.4.0-73-generic, but 5.4.0-65-generic
works fine
** Package changed: xorg (Ubuntu) => linux (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
40 matches
Mail list logo
