| Summary: | Powerdevil: Error EACCES(-13): No permission opening /dev/i2c-* | ||
|---|---|---|---|
| Product: | [Plasma] plasmashell | Reporter: | Marcus Seyfarth <m.seyfarth> |
| Component: | Power management & brightness | Assignee: | Plasma Bugs List <plasma-bugs-null> |
| Status: | RESOLVED DOWNSTREAM | ||
| Severity: | minor | CC: | nate |
| Priority: | NOR | ||
| Version First Reported In: | 6.3.5 | ||
| Target Milestone: | 1.0 | ||
| Platform: | Other | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
|
Description
Marcus Seyfarth
2025-06-20 10:04:37 UTC
I've just noticed that the logs also point to a seperate issue with plasmashell: Issue 2: QML Binding Loop in Plasma Shell Component: plasmashell (User Interface) Description: A binding loop in the QML code causes repeated warnings, potentially impacting UI responsiveness. Logs (Translated): Jun 18 11:05:57 n5z690 plasmashell[1492]: kf.plasma.quick: Applet preload policy set to 1 Jun 18 11:05:57 n5z690 plasmashell[1492]: file:///usr/share/plasma/plasmoids/org.kde.desktopcontainment/contents/ui/main.qml:178:25: QML FolderViewDropArea (parent or ancestor of QQuickLayoutAttached): Binding loop > file:///usr/share/plasma/plasmoids/org.kde.desktopcontainment/contents/ui/main.qml:201:9 Jun 18 11:05:57 n5z690 plasmashell[1492]: Toolbox not loading, toolbox package is either invalid or disabled. Analysis: The QML file main.qml (Desktop Containment widget) has a recursive binding at lines 178 and 201. Please report separate issues in separate bug reports. Thanks! Hmm, where is the issue in powerdevil here? Why would it be powerdevil's fault if it doesn't have permission to access a resource provided by a different part of the system? I am probably not the correct person to answer this as I honestly can't tell which project is responsible to solve these errors and owns this problem (therefore filing a downstream CachyOS bug first). From my limited understanding of the problem it could be a powerdevil problem in needing such a udev rule or a distribution-level problem to require such a rule. All I can tell is that I didn't get these errors in the logs with earlier KDE releases. In general this kind of this is controlled by the distro. |