https://bugs.kde.org/show_bug.cgi?id=515635
TraceyC <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |[email protected] Version First|master |6.5.5 Reported In| | Summary|Blackscreen after clicking |Black screen after clicking |on Dolphin File Manager |on Dolphin File Manager Resolution|--- |DOWNSTREAM Product|plasmashell |kwin Component|Activities in general |general Status|REPORTED |RESOLVED Assignee|[email protected] |[email protected] Target Milestone|1.0 |--- --- Comment #3 from TraceyC <[email protected]> --- Thanks for the bug report and the detailed logs. It sounds like kwin crashed or ran into an error condition. >From what I see, there may be a system level issue. It looks like a number of services may be misconfigured. These parts of the log are what leads me to think that: fev 06 12:44:58 desktop-pc dbus-broker-launch[3017]: Service file '/usr/share/dbus-1/services/org.kde.dolphin.FileManager1.service' is not named after the D-Bus name 'org.freedesktop.FileManager1'. fev 06 12:44:58 desktop-pc dbus-broker-launch[3017]: Service file '/usr/share/dbus-1/services/org.kde.kscreen.service' is not named after the D-Bus name 'org.kde.KScreen'. fev 06 12:44:58 desktop-pc dbus-broker-launch[3017]: Service file '/usr/share/dbus-1/services/org.kde.plasma.Notifications.service' is not named after the D-Bus name 'org.freedesktop.Notifications'. fev 06 12:44:59 desktop-pc wireplumber[3040]: default: Failed to get percentage from UPower: org.freedesktop.DBus.Error.NameHasNoOwner fev 06 12:44:59 desktop-pc wireplumber[3040]: spa.bluez5: BlueZ system service is not available fev 06 12:45:00 desktop-pc dbus-broker-launch[2558]: Activation request for 'org.freedesktop.Avahi' failed: The systemd unit 'dbus-org.freedesktop.Avahi.service' could not be found fev 06 12:45:05 desktop-pc pipewire[3671]: pw.conf: 0x561d1ba3ac40: error loading config '/home/user/.config/pipewire/pipewire.conf.d/20-echo-cancel.conf': Invalid argument fev 06 12:45:05 desktop-pc wireplumber[3674]: wp-conf: <WpConf:0x55e158c923e0> failed to open '/home/user/.config/wireplumber/wireplumber.conf.d/54-set-default-output-profile.conf': section 'monitor.alsa.rules' has no value fev 06 12:45:06 desktop-pc wireplumber[3674]: default: Failed to get percentage from UPower: org.freedesktop.DBus.Error.NameHasNoOwner fev 06 12:45:06 desktop-pc wireplumber[3674]: spa.bluez5: BlueZ system service is not available fev 06 12:45:06 desktop-pc kernel: nvme nvme0: using unchecked data buffer fev 06 12:45:06 desktop-pc kded6[3734]: QDBusObjectPath: invalid path "/modules/oom-notifier" fev 06 12:45:06 desktop-pc kded6[3734]: The kded module name "oom-notifier" is invalid! fev 06 12:45:06 desktop-pc kded6[3734]: QDBusObjectPath: invalid path "/modules/plasma-session-shortcuts" fev 06 12:45:06 desktop-pc kded6[3734]: The kded module name "plasma-session-shortcuts" is invalid! fev 06 12:45:06 desktop-pc kded6[3734]: Failed to connect to Bolt manager DBus interface: fev 06 12:45:06 desktop-pc kded6[3734]: QDBusObjectPath: invalid path "/modules/wpad-detector" fev 06 12:45:06 desktop-pc kded6[3734]: The kded module name "wpad-detector" is invalid! fev 06 12:45:06 desktop-pc kconf_update[3865]: /usr/share/kconf_update/filepicker.upd defined Version=5 but Version=6 was expected fev 06 12:45:06 desktop-pc kded6[3734]: QDBusConnection: name 'org.freedesktop.UPower' had owner '' but we thought it was ':1.53' fev 06 12:45:06 desktop-pc dbus-broker-launch[2558]: Activation request for 'org.freedesktop.ModemManager1' failed: The systemd unit 'dbus-org.freedesktop.ModemManager1.service' could not be found. fev 06 12:45:06 desktop-pc kded6[3734]: Failed enumerating MM objects: "org.freedesktop.DBus.Error.NameHasNoOwner" "Could not activate remote peer 'org.freedesktop.ModemManager1': activation request failed: unknown unit" You didn't mention which distro you have installed, but I recommend reaching out to their support channels to get your system in a good state first. If you continue to have problems after that, take a look at the Crashed Process Viewer and see if there are entries for kwin. If so we would need a backtrace of the crash. Thanks! -- You are receiving this mail because: You are watching all bug changes.
