** No longer affects: linux
** No longer affects: linux (Ubuntu)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2063143
Title:
Frequent boot to black display
Status in Plymouth:
New
** 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
** Changed in: sddm (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2063143
Title:
Frequent boot to black display
Status in Linux:
New
Status
here is i915 failed to boot in the same way. you can see the i915 kernel
driver does not finish until much after sddm starts
** Attachment added: "i915-fail-boot.txt"
https://bugs.launchpad.net/sddm/+bug/2063143/+attachment/5770118/+files/i915-fail-boot.txt
--
You received this bug
here is i915 with a successfull boot. the i915 driver finishes starting
before sddm starts.
** Attachment added: "i915-successfull-boot.txt"
https://bugs.launchpad.net/sddm/+bug/2063143/+attachment/5770119/+files/i915-successfull-boot.txt
--
You received this bug notification because you
I am hitting this on i915 as well with the same 50-75% frequency.
I think this need to be upgraded to critical status (at least for non
GDM login managers where no mitigation exists) and potentially release
blocker depending on how widespread this issue is.
Devices I have confirmed affected by
** Bug watch added: github.com/sddm/sddm/issues #1917
https://github.com/sddm/sddm/issues/1917
** Also affects: sddm via
https://github.com/sddm/sddm/issues/1917
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a member of Kernel
AMD kernel developer wants to classify this is as both SDDM bug and
plymouth bug https://gitlab.freedesktop.org/drm/amd/-/issues/3341.
amdgpu kernel driver is not ready by the time that sddm and plymouth are
started in some cases (race condition). Marking this as a sddm and
plymouth bug (in
** Bug watch added: gitlab.freedesktop.org/drm/amd/-/issues #3341
https://gitlab.freedesktop.org/drm/amd/-/issues/3341
** Also affects: linux via
https://gitlab.freedesktop.org/drm/amd/-/issues/3341
Importance: Unknown
Status: Unknown
--
You received this bug notification
this issue has appeared before on other AMD hardware but was closed due
to lack of activity and driver changes. my issue shows that it has re-
appeared on new hardware and drivers
https://gitlab.freedesktop.org/drm/amd/-/issues/1256
** Bug watch added: gitlab.freedesktop.org/drm/amd/-/issues
Going to change this back to linux as the plymouth failing to display
indicates an issues with KMS (plymouth uses KMS to display graphics on
earlyboot which is what is happening here). The bootlogo from plymouth
always shows (even for a very brief time) when SDDM starts and when it
boots to a
Here is my current boot journalctl (where booting to a desktop
succeeded) for comparison incase it helps.
I will also note that on the boot to black screen I never see any
plymouth bootlogos or messages. The screen remains black after grub
(with only backlight level changing). When I get a
Attached is the journalctl as instructed. I tried to power it off by
short pressing the power button a few times (as you can see in the log
at the end) while black screened but wasn't able to do that so hard to
force power off.
There are no logs in /var/crash/
** Attachment added: "preboot.txt"
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
Anyone looking into this? I get this a few times a week especially with
multiple chromium based applications open.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2057155
Title:
amdgpu
** Attachment added: "look_at_this_journalctl_from_previous_boot.log"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2057155/+attachment/5754997/+files/look_at_this_journalctl_from_previous_boot.log
--
You received this bug notification because you are a member of Kernel
Packages,
Public bug reported:
Mar 11 18:30:07 garrett-desktop kernel: [drm:amdgpu_job_timedout [amdgpu]]
*ERROR* ring gfx timeout, signaled seq=211055, emitted seq=211057
Mar 11 18:30:07 garrett-desktop kernel: [drm:amdgpu_job_timedout [amdgpu]]
*ERROR* Process information: process armcord pid 14844
Public bug reported:
Description:Ubuntu Noble Numbat (development branch)
Release:24.04
Kernel info: Linux gman-Laptop-13-AMD-Ryzen-7040Series 6.8.0-11-generic
#11-Ubuntu SMP PREEMPT_DYNAMIC Wed Feb 14 00:29:05 UTC 2024 x86_64
x86_64 x86_64 GNU/Linux
Hardware: AMD Framework 13
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 Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/2049708
** 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 -
22 matches
Mail list logo
