** No longer affects: linux
** No longer affects: linux (Ubuntu)
--
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/2063143
Title:
Frequent boot to black display
Status in
** Also affects: systemd (Ubuntu)
Importance: Undecided
Status: New
** Bug watch added: github.com/systemd/systemd/issues #32509
https://github.com/systemd/systemd/issues/32509
** Also affects: systemd via
https://github.com/systemd/systemd/issues/32509
Importance: Unknown
Upstream QT bugtracker url (can't add to launchpad because it doesn't
recognize the format) https://bugreports.qt.io/browse/QTBUG-94871
** Also affects: qtbase-opensource-src (Ubuntu)
Importance: Undecided
Status: New
** Changed in: qtbase-opensource-src (Ubuntu)
Status: New =>
Seems like a racecondition of some sort. I tried a few days ago with no
issue.
This seems to be a long running bug, not something new since its been reported
in other places.
https://ubuntuforums.org/archive/index.php/t-2391820.html
Does not seem fully fixed as I am still seeing the comments. Unless this
is expected functionality. See
https://bugs.launchpad.net/ubuntu/+source/software-
properties/+bug/2061214/comments/17
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
I do not think the GTK version is fixed.
I am seeing the issue as seen in the screenshot.
Tell me to open a new bug if needed.
`sources.list`
```
# Ubuntu sources have moved to the /etc/apt/sources.list.d/ubuntu.sources
# file, which uses the deb822 format. Use deb822-formatted .sources files
#
Adding Julian Andres Klode as a subscriber as seemingly this could only
be due to the recent package update from aspell
https://changelogs.ubuntu.com/changelogs/pool/main/a/aspell/aspell_0.60.8.1-1build1/changelog
--
You received this bug notification because you are a member of Ubuntu
Touch
Public bug reported:
Hardware: AMD Framework 13
OS: Ubuntu Noble 24.04
DE: Plasma Wayland
BIOS: version 3.03 and 3.05 (latest new release)
Kernel: 6.8.0-31-generic #31-Ubuntu SMP PREEMPT_DYNAMIC Sat Apr 20 00:40:06 UTC
2024 x86_64 x86_64 x86_64 GNU/Linux
This issue started about 2-3 weeks ago I
** Description changed:
+ this is running with LC_ALL=C
+
+ the following are output in terminal when configuring dictionaries-
+ common
+
Setting up dictionaries-common (1.29.7) ...
Processing triggers for dictionaries-common (1.29.7) ...
aspell-autobuildhash: processing: en [en-common].
Public bug reported:
Setting up dictionaries-common (1.29.7) ...
Processing triggers for dictionaries-common (1.29.7) ...
aspell-autobuildhash: processing: en [en-common].
Error: /dev/null:1: The key "/usr/bin/aspell" is unknown.
Undefined subroutine ::subst called at
Found a rouge service (not from the ubuntu distro but instead my custom
nvidia tegra BSP) that had the `/usr/lib/bluetooth/bluetoothd` path in
it.
Closing as removing or altering that service fixes it.
** Changed in: bluez (Ubuntu)
Status: New => Invalid
--
You received this bug
You are not.
I have rebooted multiple times and continue to get this message in journalctl
(yes it's a new entry on each boot).
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
** Description changed:
Release: Ubuntu Noble Dev Branch
the location of bluetoothd was just changed to
/usr/libexec/bluetooth/bluetoothd
this causes bluetooth to fail to start since something is still looking
for the old location
Jan 17 21:23:26 switch systemd[1]: Starting
Public bug reported:
Release: Ubuntu Noble Dev Branch
the location of bluetoothd was just changed to
/usr/libexec/bluetooth/bluetoothd
this causes bluetooth to fail to start since something is still looking
for the old location
Jan 17 21:23:26 switch systemd[1]: Starting bluetooth.service -
Public bug reported:
Release: Ubuntu Focal
Architecture: armhf
wget version: 1.20.3-1ubuntu2
The following affects Ubuntu focal and likely future releases as well on armhf
platforms. No this is not a missing certificate issue.
Attempting to download a file with wget using https fails to
15 matches
Mail list logo
