https://bugs.kde.org/show_bug.cgi?id=459611
Bug ID: 459611
Summary: dbus.socket failed to listen, dbus-broker failed to
start,.... New Kernel 5.19.10-200.fc36.x86_64 does not
boot, at all!
Classification: I don't know
Product: kde
Version: unspecified
Platform: Fedora RPMs
OS: Linux
Status: REPORTED
Severity: critical
Priority: NOR
Component: general
Assignee: unassigned-b...@kde.org
Reporter: embedded_syst...@hotmail.co.uk
Target Milestone: ---
SUMMARY
***
NOTE: If you are reporting a crash, please try to attach a backtrace with debug
symbols.
See
https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports
***
STEPS TO REPRODUCE
1.
2.
3.
OBSERVED RESULT
EXPECTED RESULT
SOFTWARE/OS VERSIONS
Linux/KDE Plasma:
(available in About System)
KDE Plasma Version:
KDE Frameworks Version:
Qt Version:
ADDITIONAL INFORMATION
Hi,
I have just updated the Kernel, -> 5.19.10-200.fc36.x86_64
But, I have been having trouble with the Desktop (KDE Plasma workspaces), with
the Desktop turning Black, behind whatever I am running.
It will not shutdown, or reboot, after that (Needing to hard reboot).
In single mode, I run sudo dnf update, and it installed the new kernel and
Pipewire-...
It now will not boot, at all!
Lucky I have a later copy of the kernel install 5.19.8-200.fc36.x86_64.
So, I am now running this.
I notice within the boot messages that dbus.socket fails to listen, dbus-broker
fails to start, and termald, logind,... all fail to start?
Any ideas?
Regards,
RDM
Now running spare kernel:
Linux localhost 5.19.8-200.fc36.x86_64 #1 SMP PREEMPT_DYNAMIC Thu Sep 8
19:02:21 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux
--
You are receiving this mail because:
You are watching all bug changes.
