[systemsettings] [Bug 486513] Steam Deck doesn't see built–in speakers
https://bugs.kde.org/show_bug.cgi?id=486513 --- Comment #2 from Overko Ivan --- Yes, this is stocke installation, but now after update sistem, everything is working. Thanks On Sun, May 5, 2024, 02:37 Nate Graham wrote: > https://bugs.kde.org/show_bug.cgi?id=486513 > > --- Comment #1 from Nate Graham --- > Did you actually compile the sources yourself, or is this a stock > installation? > > -- > You are receiving this mail because: > You reported the bug. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 486513] New: Steam Deck doesn't see built–in speakers
https://bugs.kde.org/show_bug.cgi?id=486513 Bug ID: 486513 Summary: Steam Deck doesn't see built–in speakers Classification: Applications Product: systemsettings Version: 5.27.10 Platform: Compiled Sources OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: overiva...@gmail.com Target Milestone: --- Application: systemsettings (5.27.10) (Compiled from sources) Qt Version: 5.15.12 Frameworks Version: 5.115.0 Operating System: Linux 6.5.0-valve3-3-neptune-65-gf73fe24f1b3a x86_64 Windowing System: X11 Distribution: SteamOS DrKonqi: 5.27.10 [KCrashBackend] -- Information about the crash: After updating the system, the Steam Deck lost sound; in desktop mode, when i try to enter the settings, the program crashes. Audio panel doesn't see speakers. The crash can be reproduced every time. -- Backtrace: Application: System Settings (systemsettings), signal: Bus error [KCrash Handler] #4 0x7fad0cf79101 in ??? () at /usr/lib/libc.so.6 #5 0x7fad0d694b70 in ??? () at /usr/lib/libQt5Core.so.5 #6 0x7fad0d685009 in QPluginLoader::setFileName(QString const&) () at /usr/lib/libQt5Core.so.5 #7 0x7fad0e97adec in KPluginMetaData::KPluginMetaData(QString const&, KPluginMetaData::KPluginMetaDataOption) () at /usr/lib/libKF5CoreAddons.so.5 #8 0x7fad0e97b1ea in ??? () at /usr/lib/libKF5CoreAddons.so.5 #9 0x7fad0e97872a in KPluginMetaData::findPlugins(QString const&, std::function, KPluginMetaData::KPluginMetaDataOption) () at /usr/lib/libKF5CoreAddons.so.5 #10 0x7fad0e978b08 in KPluginMetaData::findPlugins(QString const&, std::function) () at /usr/lib/libKF5CoreAddons.so.5 #11 0x55f4a22972ed in ??? () #12 0x55f4a2298047 in ??? () #13 0x7fad0d6bb964 in QObject::event(QEvent*) () at /usr/lib/libQt5Core.so.5 #14 0x7fad0f05e03e in KXmlGuiWindow::event(QEvent*) () at /usr/lib/libKF5XmlGui.so.5 #15 0x7fad0e3578ff in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /usr/lib/libQt5Widgets.so.5 #16 0x7fad0d693ef8 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /usr/lib/libQt5Core.so.5 #17 0x7fad0d698e5b in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () at /usr/lib/libQt5Core.so.5 #18 0x7fad0d6deec8 in ??? () at /usr/lib/libQt5Core.so.5 #19 0x7fad0bf0df69 in ??? () at /usr/lib/libglib-2.0.so.0 #20 0x7fad0bf6c3a7 in ??? () at /usr/lib/libglib-2.0.so.0 #21 0x7fad0bf0c162 in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #22 0x7fad0d6e2d0c in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #23 0x7fad0d692c04 in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #24 0x7fad0d6940a3 in QCoreApplication::exec() () at /usr/lib/libQt5Core.so.5 #25 0x55f4a228dbd9 in ??? () #26 0x7fad0ce43cd0 in ??? () at /usr/lib/libc.so.6 #27 0x7fad0ce43d8a in __libc_start_main () at /usr/lib/libc.so.6 #28 0x55f4a228e575 in ??? () [Inferior 1 (process 7459) detached] Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 479891] Some text glyphs in QML software are mis-aligned or squished when using a fractional scale factor
https://bugs.kde.org/show_bug.cgi?id=479891 Ivan Jelic changed: What|Removed |Added CC||ivan.je...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 482185] Context menu (when right-clicking on the desktop) appears in a separate window after external monitor restart
https://bugs.kde.org/show_bug.cgi?id=482185 ivan changed: What|Removed |Added Version|6.0.3 |6.0.4 --- Comment #12 from ivan --- Issue is still present in 6.0.4 on Kde Neon running on amd cpu and gpu. -- You are receiving this mail because: You are watching all bug changes.
[Plasma Vault] [Bug 485895] Error loading Vaults
https://bugs.kde.org/show_bug.cgi?id=485895 --- Comment #1 from Ivan Čukić --- Is it possible that the issue is in the installation? I don't see this problem on Artix (Arch + OpenRC). Updating the system now, will see if it breaks with the latest. -- You are receiving this mail because: You are watching all bug changes.
[Plasma Vault] [Bug 485151] Correct password won't open vault as destination is "not empty"
https://bugs.kde.org/show_bug.cgi?id=485151 --- Comment #2 from Ivan Čukić --- cryfs' high memory requirements are by design since at least 2020 - see https://github.com/cryfs/cryfs/issues/335#issuecomment-652338744 Now, the question I have is how do the 'not empty' and 'cryfs killed' results relate to each other? Does one happen the first time, and the other one the second time you try it, or something else? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 485639] Adaptive Sync has inconsistent refresh in KWin Plasma/6.0 (AMDGPU)
https://bugs.kde.org/show_bug.cgi?id=485639 --- Comment #8 from Ivan Ko --- (In reply to Bug Janitor Service from comment #5) > A possibly relevant merge request was started @ > https://invent.kde.org/plasma/kwin/-/merge_requests/5626 Confirmed issue was fixed. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 485639] Adaptive Sync has inconsistent refresh in KWin Plasma/6.0 (AMDGPU)
https://bugs.kde.org/show_bug.cgi?id=485639 --- Comment #3 from Ivan Ko --- Reverting the following commit from 6.0.4 branch fixes the issue for me: https://invent.kde.org/plasma/kwin/-/commit/19ffe2ac411b866cd646942d4e3cfb41d8ca89a1 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 485639] Adaptive Sync has inconsistent refresh in KWin Plasma/6.0 (AMDGPU)
https://bugs.kde.org/show_bug.cgi?id=485639 Ivan Ko changed: What|Removed |Added CC||ivanwheele...@gmail.com --- Comment #2 from Ivan Ko --- Can confirm that 6.0.4 is the issue. Tried to patch stable 6.0.4 with those commits (required some changes) and that didn't fix anything. Rebuilding kwin 6.0.3 package fixes framerate and games are butter smooth again. -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 483856] Service file '/usr/share//dbus-1/services/org.kde.kscreen.service' is not named after the D-Bus name 'org.kde.KScreen'.
https://bugs.kde.org/show_bug.cgi?id=483856 --- Comment #2 from Ivan Stankovic --- Yes, I think that's the case (heh) here: https://github.com/bus1/dbus-broker/blob/0cdc6e08154ea4d9321c17451de85d416ba5c127/src/launch/launcher.c#L635 There are others though where it's not about the case: Service file '/usr/share//dbus-1/services/org.kde.dolphin.FileManager1.service' is not named after the D-Bus name 'org.freedesktop.FileManager1'. Service file '/usr/share//dbus-1/services/org.kde.plasma.Notifications.service' is not named after the D-Bus name 'org.freedesktop.Notifications'. -- You are receiving this mail because: You are watching all bug changes.
[Plasma Vault] [Bug 485051] Remove EncFS from the list of supported Algorithms
https://bugs.kde.org/show_bug.cgi?id=485051 Ivan Čukić changed: What|Removed |Added Resolution|--- |INTENTIONAL Status|REPORTED|RESOLVED --- Comment #1 from Ivan Čukić --- The issues with encfs are important for the user to know about, and for that reason Vaults shows the information about the issues. The problems the audit pointed out relate to using encfs in a situation where the encrypted data is synced to a remote data storage that the attacker has access to. If encfs is used locally only, the encryption it has is good enough. Apart from the message about the security of encfs, an additional deterrent of using it with online syncing is that you can not choose the location of the encrypted data storage when using encfs as the backend. After the recent news with xz, I'm starting to think that the fact we don't have a new version of encfs is a good thing - we have a version that has been audited and for which we know the faults and when it should and shouldn't be used. For the things that have active development, an audit (if they have been audited at all) quickly becomes obsolete and new patches might worsen the security. :) -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 447530] Untracked empty folders in a git repo are wrongly shown with the 'up-to-date' icon
https://bugs.kde.org/show_bug.cgi?id=447530 Ivan Jurišić changed: What|Removed |Added CC||i...@jurisic.org --- Comment #3 from Ivan Jurišić --- I confirm this bug also in Debian 12 Bookworm, KDE Plasma Version: 5.27.5 KDE Frameworks Version: 5.103.0 Qt Version: 5.15.8 Kernel Version: 6.1.0-18-amd64 Debian package name: dolphin-plugins, Version: 22.12.3-1 -- You are receiving this mail because: You are watching all bug changes.
[NeoChat] [Bug 484352] A number of warnings emitted on start
https://bugs.kde.org/show_bug.cgi?id=484352 Ivan Stankovic changed: What|Removed |Added Ever confirmed|0 |1 Status|RESOLVED|REOPENED Resolution|NOT A BUG |--- --- Comment #2 from Ivan Stankovic --- Could you please elaborate on why these warnings are irrelevant? I would like to know more. Also, do you consider things like neochat[36637]: QQmlVMEMetaObject: Internal error - attempted to evaluate a function in an invalid context neochat[36637]: qrc:/org/kde/neochat/qml/TimelineView.qml:271: TypeError: Type error also irrelevant? I would like to understand why. -- You are receiving this mail because: You are watching all bug changes.
[NeoChat] [Bug 484352] New: A number of warnings emitted on start
https://bugs.kde.org/show_bug.cgi?id=484352 Bug ID: 484352 Summary: A number of warnings emitted on start Classification: Applications Product: NeoChat Version: 24.02.1 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: General Assignee: fe...@posteo.de Reporter: istanko...@posteo.net CC: c...@carlschwan.eu Target Milestone: --- SUMMARY Starting neochat emits a number of warnings: neochat[36637]: qrc:/org/kde/neochat/qml/TimelineView.qml:139:17: QML SectionDelegate: Possible anchor loop detected on horizontal anchor. neochat[36637]: qrc:/org/kde/neochat/qml/TimelineView.qml:139:17: QML SectionDelegate: Possible anchor loop detected on horizontal anchor. neochat[36637]: qrc:/org/kde/neochat/qml/TimelineView.qml:139:17: QML SectionDelegate: Possible anchor loop detected on horizontal anchor. neochat[36637]: qrc:/org/kde/neochat/qml/TimelineView.qml:139:17: QML SectionDelegate: Possible anchor loop detected on horizontal anchor. neochat[36637]: qrc:/org/kde/neochat/qml/TimelineView.qml:139:17: QML SectionDelegate: Possible anchor loop detected on horizontal anchor. neochat[36637]: qrc:/org/kde/neochat/qml/TimelineView.qml:139:17: QML SectionDelegate: Possible anchor loop detected on horizontal anchor. neochat[36637]: qrc:/org/kde/neochat/qml/TimelineView.qml:139:17: QML SectionDelegate: Possible anchor loop detected on horizontal anchor. neochat[36637]: qrc:/org/kde/neochat/qml/TimelineView.qml:139:17: QML SectionDelegate: Possible anchor loop detected on horizontal anchor. neochat[36637]: qrc:/org/kde/neochat/qml/TimelineView.qml:139:17: QML SectionDelegate: Possible anchor loop detected on horizontal anchor. neochat[36637]: qrc:/org/kde/neochat/qml/TimelineView.qml:139:17: QML SectionDelegate: Possible anchor loop detected on horizontal anchor. neochat[36637]: qrc:/org/kde/neochat/qml/TimelineView.qml:139:17: QML SectionDelegate: Possible anchor loop detected on horizontal anchor. neochat[36637]: qrc:/org/kde/neochat/qml/RoomInformation.qml:133:13: QML ListSectionHeader: Binding loop detected for property "implicitWidth" neochat[36637]: qrc:/org/kde/neochat/qml/RoomInformation.qml:67:13: QML ListSectionHeader: Binding loop detected for property "implicitWidth" neochat[36637]: qrc:/org/kde/neochat/qml/TimelineView.qml:139:17: QML SectionDelegate: Possible anchor loop detected on horizontal anchor. neochat[36637]: qrc:/org/kde/neochat/qml/TimelineView.qml:139:17: QML SectionDelegate: Possible anchor loop detected on horizontal anchor. neochat[36637]: qrc:/org/kde/neochat/qml/TimelineView.qml:139:17: QML SectionDelegate: Possible anchor loop detected on horizontal anchor. neochat[36637]: qrc:/org/kde/neochat/qml/TimelineView.qml:139:17: QML SectionDelegate: Possible anchor loop detected on horizontal anchor. neochat[36637]: qt.gui.icc: fromIccProfile: failed minimal tag size sanity neochat[36637]: qrc:/org/kde/neochat/qml/TimelineView.qml:139:17: QML SectionDelegate: Possible anchor loop detected on horizontal anchor. neochat[36637]: qrc:/org/kde/neochat/qml/TimelineView.qml:139:17: QML SectionDelegate: Possible anchor loop detected on horizontal anchor. neochat[36637]: qrc:/org/kde/neochat/qml/TimelineView.qml:139:17: QML SectionDelegate: Possible anchor loop detected on horizontal anchor. neochat[36637]: qrc:/org/kde/neochat/qml/TimelineView.qml:139:17: QML SectionDelegate: Possible anchor loop detected on horizontal anchor. neochat[36637]: qrc:/org/kde/neochat/qml/TimelineView.qml:139:17: QML SectionDelegate: Possible anchor loop detected on horizontal anchor. neochat[36637]: qrc:/org/kde/neochat/qml/TimelineView.qml:139:17: QML SectionDelegate: Possible anchor loop detected on horizontal anchor. neochat[36637]: qrc:/org/kde/neochat/qml/TimelineView.qml:139:17: QML SectionDelegate: Possible anchor loop detected on horizontal anchor. neochat[36637]: qrc:/org/kde/neochat/qml/TimelineView.qml:139:17: QML SectionDelegate: Possible anchor loop detected on horizontal anchor. neochat[36637]: qrc:/org/kde/neochat/qml/TimelineView.qml:139:17: QML SectionDelegate: Possible anchor loop detected on horizontal anchor. neochat[36637]: qrc:/org/kde/neochat/qml/TimelineView.qml:139:17: QML SectionDelegate: Possible anchor loop detected on horizontal anchor. neochat[36637]: qrc:/org/kde/neochat/qml/TimelineView.qml:139:17: QML SectionDelegate: Possible anchor loop detected on horizontal anchor. neochat[36637]: qrc:/org/kde/neochat/qml/TimelineView.qml:139:17: QML SectionDelegate: Possible anchor loop detected on horizontal anchor. neochat[36637]: qrc:/org/kde/neochat/qml/TimelineView.qml:139:17: QML SectionDelegate: Possible anchor loop detected on horizontal anchor. neochat[36637]: qrc:/org/kde/neochat/qml/TimelineView.qml:139:17: QML SectionDelegate: Possible anchor loop detected on horizontal anchor. neochat[36637]:
[plasmashell] [Bug 484351] New: QML RowLayout: Layout polish loop detected
https://bugs.kde.org/show_bug.cgi?id=484351 Bug ID: 484351 Summary: QML RowLayout: Layout polish loop detected Classification: Plasma Product: plasmashell Version: 6.0.2 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: istanko...@posteo.net CC: k...@davidedmundson.co.uk Target Milestone: 1.0 SUMMARY Hovering mouse pointer over applet icons causes a number of warnings to be emitted: plasmashell[1398]: qrc:/plasma/DefaultToolTip.qml:25:5: QML RowLayout: Layout polish loop detected for QQuickRowLayout(0x59fa93db58f0, id="mainLayout", parent=0x765c84016e70, geometry=-101,-50 360x174). Aborting after two iterations. plasmashell[1398]: qrc:/plasma/DefaultToolTip.qml:25:5: QML RowLayout: Layout polish loop detected for QQuickRowLayout(0x59fa93db58f0, id="mainLayout", parent=0x765c84016e70, geometry=-82,-22 360x135). Aborting after two iterations. plasmashell[1398]: qrc:/plasma/DefaultToolTip.qml:25:5: QML RowLayout: Layout polish loop detected for QQuickRowLayout(0x59fa93db58f0, id="mainLayout", parent=0x765c84016e70, geometry=-101,-50 360x174). Aborting after two iterations. plasmashell[1398]: qrc:/plasma/DefaultToolTip.qml:25:5: QML RowLayout: Layout polish loop detected for QQuickRowLayout(0x59fa93db58f0, id="mainLayout", parent=0x765c84016e70, geometry=-16,-1 228x93). Aborting after two iterations. plasmashell[1398]: qrc:/plasma/DefaultToolTip.qml:25:5: QML RowLayout: Layout polish loop detected for QQuickRowLayout(0x59fa93db58f0, id="mainLayout", parent=0x765c84016e70, geometry=-19,-11 176x78). Aborting after two iterations. plasmashell[1398]: qrc:/plasma/DefaultToolTip.qml:25:5: QML RowLayout: Layout polish loop detected for QQuickRowLayout(0x59fa93db58f0, id="mainLayout", parent=0x765c84016e70, geometry=-22,-12 176x57). Aborting after two iterations. plasmashell[1398]: qrc:/plasma/DefaultToolTip.qml:25:5: QML RowLayout: Layout polish loop detected for QQuickRowLayout(0x59fa93db58f0, id="mainLayout", parent=0x765c84016e70, geometry=-33,-61 203x177). Aborting after two iterations. plasmashell[1398]: qrc:/plasma/DefaultToolTip.qml:25:5: QML RowLayout: Layout polish loop detected for QQuickRowLayout(0x59fa93db58f0, id="mainLayout", parent=0x765c84016e70, geometry=-4,9 228x75). Aborting after two iterations. plasmashell[1398]: qrc:/plasma/DefaultToolTip.qml:25:5: QML RowLayout: Layout polish loop detected for QQuickRowLayout(0x59fa93db58f0, id="mainLayout", parent=0x765c84016e70, geometry=-82,-22 360x135). Aborting after two iterations. This is with applets for weather, bluetooth, sound, screen brightness, lock status etc. SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 6.0.2 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.2 Kernel Version: 6.8.1-arch1-1 (64-bit) Graphics Platform: Wayland -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 484270] QML PlasmoidHeading: Binding loop detected for property "leftInset"
https://bugs.kde.org/show_bug.cgi?id=484270 --- Comment #1 from Ivan Stankovic --- Same warning happens with org.kde.plasma.mediacontroller: plasmashell[1398]: file:///usr/share/plasma/plasmoids/org.kde.plasma.mediacontroller/contents/ui/ExpandedRepresentation.qml:648:13: QML PlasmoidHeading: Binding loop detected for property "leftInset" -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 482987] Bottom edge of screen has pixels that are held to the color of previously opened windows after closing those windows
https://bugs.kde.org/show_bug.cgi?id=482987 Ivan Jelic changed: What|Removed |Added CC||ivan.je...@gmail.com --- Comment #12 from Ivan Jelic --- Hi there, confirming the bug, 2560x1440 at 150% (Framework 13 12th Gen Intel). Changing scale factor didn't help, though. Thanks -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 484272] New: org.kde.plasma.weather: Setting initial properties failed
https://bugs.kde.org/show_bug.cgi?id=484272 Bug ID: 484272 Summary: org.kde.plasma.weather: Setting initial properties failed Classification: Plasma Product: plasmashell Version: 6.0.2 Platform: Other OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: istanko...@posteo.net CC: k...@davidedmundson.co.uk Target Milestone: 1.0 SUMMARY There were following warnings when I interacted with the weather applet (I was configuring my location): plasmashell[1249]: file:///usr/share/plasma/plasmoids/org.kde.plasma.weather/contents/ui/config/ConfigAppearance.qml:16:1: QML ConfigAppearance: Created graphical object was not placed in the graphics scene. plasmashell[1249]: file:///usr/share/plasma/plasmoids/org.kde.plasma.weather/contents/ui/config/ConfigAppearance.qml: Setting initial properties failed: ConfigAppearance does not have a property called cfg_pressureUnit plasmashell[1249]: file:///usr/share/plasma/plasmoids/org.kde.plasma.weather/contents/ui/config/ConfigAppearance.qml: Setting initial properties failed: ConfigAppearance does not have a property called cfg_pressureUnitDefault plasmashell[1249]: file:///usr/share/plasma/plasmoids/org.kde.plasma.weather/contents/ui/config/ConfigAppearance.qml: Setting initial properties failed: ConfigAppearance does not have a property called cfg_showHumidityInTooltipDefault plasmashell[1249]: file:///usr/share/plasma/plasmoids/org.kde.plasma.weather/contents/ui/config/ConfigAppearance.qml: Setting initial properties failed: ConfigAppearance does not have a property called cfg_showPressureInTooltipDefault plasmashell[1249]: file:///usr/share/plasma/plasmoids/org.kde.plasma.weather/contents/ui/config/ConfigAppearance.qml: Setting initial properties failed: ConfigAppearance does not have a property called cfg_showTemperatureInBadgeDefault plasmashell[1249]: file:///usr/share/plasma/plasmoids/org.kde.plasma.weather/contents/ui/config/ConfigAppearance.qml: Setting initial properties failed: ConfigAppearance does not have a property called cfg_showTemperatureInCompactModeDefault plasmashell[1249]: file:///usr/share/plasma/plasmoids/org.kde.plasma.weather/contents/ui/config/ConfigAppearance.qml: Setting initial properties failed: ConfigAppearance does not have a property called cfg_showTemperatureInTooltipDefault plasmashell[1249]: file:///usr/share/plasma/plasmoids/org.kde.plasma.weather/contents/ui/config/ConfigAppearance.qml: Setting initial properties failed: ConfigAppearance does not have a property called cfg_showWindInTooltipDefault plasmashell[1249]: file:///usr/share/plasma/plasmoids/org.kde.plasma.weather/contents/ui/config/ConfigAppearance.qml: Setting initial properties failed: ConfigAppearance does not have a property called cfg_source plasmashell[1249]: file:///usr/share/plasma/plasmoids/org.kde.plasma.weather/contents/ui/config/ConfigAppearance.qml: Setting initial properties failed: ConfigAppearance does not have a property called cfg_sourceDefault plasmashell[1249]: file:///usr/share/plasma/plasmoids/org.kde.plasma.weather/contents/ui/config/ConfigAppearance.qml: Setting initial properties failed: ConfigAppearance does not have a property called cfg_speedUnit plasmashell[1249]: file:///usr/share/plasma/plasmoids/org.kde.plasma.weather/contents/ui/config/ConfigAppearance.qml: Setting initial properties failed: ConfigAppearance does not have a property called cfg_speedUnitDefault plasmashell[1249]: file:///usr/share/plasma/plasmoids/org.kde.plasma.weather/contents/ui/config/ConfigAppearance.qml: Setting initial properties failed: ConfigAppearance does not have a property called cfg_temperatureUnit plasmashell[1249]: file:///usr/share/plasma/plasmoids/org.kde.plasma.weather/contents/ui/config/ConfigAppearance.qml: Setting initial properties failed: ConfigAppearance does not have a property called cfg_temperatureUnitDefault plasmashell[1249]: file:///usr/share/plasma/plasmoids/org.kde.plasma.weather/contents/ui/config/ConfigAppearance.qml: Setting initial properties failed: ConfigAppearance does not have a property called cfg_updateInterval plasmashell[1249]: file:///usr/share/plasma/plasmoids/org.kde.plasma.weather/contents/ui/config/ConfigAppearance.qml: Setting initial properties failed: ConfigAppearance does not have a property called cfg_updateIntervalDefault plasmashell[1249]: file:///usr/share/plasma/plasmoids/org.kde.plasma.weather/contents/ui/config/ConfigAppearance.qml: Setting initial properties failed: ConfigAppearance does not have a property called cfg_visibilityUnit plasmashell[1249]: file:///usr/share/plasma/plasmoids/org.kde.plasma.weather/contents/ui/config/ConfigAppearance.qml: Setting initial properties failed: ConfigAppearance does not have a property called cfg_visibilityUnitDefault plasmashell[1249]:
[plasmashell] [Bug 484270] New: QML PlasmoidHeading: Binding loop detected for property "leftInset"
https://bugs.kde.org/show_bug.cgi?id=484270 Bug ID: 484270 Summary: QML PlasmoidHeading: Binding loop detected for property "leftInset" Classification: Plasma Product: plasmashell Version: 6.0.2 Platform: Other OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: istanko...@posteo.net CC: k...@davidedmundson.co.uk Target Milestone: 1.0 SUMMARY I'm seeing the following warnings: plasmashell[1249]: file:///usr/share/plasma/plasmoids/org.kde.plasma.volume/contents/ui/main.qml:775:17: QML PlasmoidHeading: Binding loop detected for property "leftInset" plasmashell[1249]: file:///usr/share/plasma/plasmoids/org.kde.plasma.volume/contents/ui/main.qml:517:17: QML PlasmoidHeading: Binding loop detected for property "leftInset" plasmashell[1249]: file:///usr/share/plasma/plasmoids/org.kde.plasma.bluetooth/contents/ui/FullRepresentation.qml:65:13: QML Toolbar: Binding loop detected for property "leftInset" plasmashell[1249]: file:///usr/share/plasma/plasmoids/org.kde.plasma.battery/contents/ui/PopupDialog.qml:52:13: QML PlasmoidHeading: Binding loop detected for property "leftInset" SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 6.0.2 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.2 Kernel Version: 6.8.1-arch1-1 (64-bit) Graphics Platform: Wayland -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 482980] Keyboard repeat does not work
https://bugs.kde.org/show_bug.cgi?id=482980 --- Comment #14 from Ivan Stankovic --- Yes, I think we should close this since this is an IBus problem. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 484169] New: "Keep launchers separate" is grayed out even if relevant
https://bugs.kde.org/show_bug.cgi?id=484169 Bug ID: 484169 Summary: "Keep launchers separate" is grayed out even if relevant Classification: Plasma Product: plasmashell Version: 6.0.2 Platform: openSUSE OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: Task Manager and Icons-Only Task Manager Assignee: plasma-b...@kde.org Reporter: doktor@gmail.com CC: qydwhotm...@gmail.com Target Milestone: 1.0 SUMMARY "Keep launchers separate" is grayed out even in "Sort" modes where it is relevant (e.g.: in "By desktop"). Context: I want the "Pin" to only be visible if the corresponding app is not running. If it is running, I only want the Classic Task Manager's button, not the "pin". See: https://mstdn.science/@dryak/112133815180180834 STEPS TO REPRODUCE 1. Right click -> "Configure Task manager" 2. "Behaviour" pane 3. Section "Sort:" OBSERVED RESULT My "Sort" is on the default "By desktop". "Keep launchers separate" is grayed out, so I cannot un-check it to obtain the behaviour desired (see "context" above). EXPECTED RESULT 4. Un-check "Keep launchers separate" checkbox. 5. "Ok" 6. Now "pins" are hidden if the app is running and there's a Task button WORKAROUND 4. Switch "Sort:" to "Manual" (this un-grays the checkbox) 5. Un-check "Keep launchers separate" checkbox. 6. Switch back to your favourite "Sort" - e.g. "By desktop" (this re-grays the checkbox, but now it's un-checked). 7. "Ok" 8. Now "pins" are hidden if the app is running and there's a Task button SOFTWARE/OS VERSIONS Linux/KDE Plasma: Opensuse Tumbleeed 20240319 KDE Plasma Version: 6.0.2 KDE Frameworks Version: 6.0.2 Qt Version: 6.6.2 ADDITIONAL INFORMATION "minor" as this is just a UX/UI hiccup (need to fight around gray out check box) the actual desired functionnality (hiding "pins" automatically) works. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 483860] New: plasmashell[1454]: file:///usr/share/plasma/plasmoids/org.kde.desktopcontainment/contents/ui/FolderItemDelegate.qml:237:17: Unable to assign [undefined] to bool
https://bugs.kde.org/show_bug.cgi?id=483860 Bug ID: 483860 Summary: plasmashell[1454]: file:///usr/share/plasma/plasmoids/org.kde.desktopcont ainment/contents/ui/FolderItemDelegate.qml:237:17: Unable to assign [undefined] to bool Classification: Plasma Product: plasmashell Version: 6.0.2 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: istanko...@posteo.net CC: k...@davidedmundson.co.uk Target Milestone: 1.0 SUMMARY I get the following warning in logs: plasmashell[1454]: file:///usr/share/plasma/plasmoids/org.kde.desktopcontainment/contents/ui/FolderItemDelegate.qml:237:17: Unable to assign [undefined] to bool SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 6.0.2 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.2 Kernel Version: 6.8.1-arch1-1 (64-bit) Graphics Platform: Wayland -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 482980] Keyboard repeat does not work
https://bugs.kde.org/show_bug.cgi?id=482980 --- Comment #12 from Ivan Stankovic --- Seems to be an ibus-wayland issue: https://github.com/ibus/ibus/issues/2610 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 483859] New: plasmashell[1454]: file:///usr/share/plasma/plasmoids/org.kde.desktopcontainment/contents/ui/main.qml:196:25: QML FolderViewDropArea (parent or ancestor of QQuickLayout
https://bugs.kde.org/show_bug.cgi?id=483859 Bug ID: 483859 Summary: plasmashell[1454]: file:///usr/share/plasma/plasmoids/org.kde.desktopcont ainment/contents/ui/main.qml:196:25: QML FolderViewDropArea (parent or ancestor of QQuickLayoutAttached): Binding loop detected for property "minimumWidth"│ Classification: Plasma Product: plasmashell Version: 6.0.2 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: istanko...@posteo.net CC: k...@davidedmundson.co.uk Target Milestone: 1.0 SUMMARY I get the following warning: plasmashell[1454]: file:///usr/share/plasma/plasmoids/org.kde.desktopcontainment/contents/ui/main.qml:196:25: QML FolderViewDropArea (parent or ancestor of QQuickLayoutAttached): Binding loop detected for property "minimumWidth"│ SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 6.0.2 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.2 Kernel Version: 6.8.1-arch1-1 (64-bit) Graphics Platform: Wayland -- You are receiving this mail because: You are watching all bug changes.
[KAccounts] [Bug 483858] New: kf.coreaddons: The plugin "/usr/lib/qt6/plugins/kaccounts/daemonplugins/kaccounts_kio_webdav_plugin.so" explicitly states an Id in the embedded metadata, which is differe
https://bugs.kde.org/show_bug.cgi?id=483858 Bug ID: 483858 Summary: kf.coreaddons: The plugin "/usr/lib/qt6/plugins/kaccounts/daemonplugins/kaccount s_kio_webdav_plugin.so" explicitly states an Id in the embedded metadata, which is different from the one derived from the filename Classification: Frameworks and Libraries Product: KAccounts Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: istanko...@posteo.net CC: ad...@leinir.dk, natalie_clar...@yahoo.de Target Milestone: --- SUMMARY I get the following warning: kf.coreaddons: The plugin "/usr/lib/qt6/plugins/kaccounts/daemonplugins/kaccounts_kio_webdav_plugin.so" explicitly states an Id in the embedded metadata, which is different from the one derived from the filename The Id field from the KPlugin object in the metadata should be removed SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 6.0.2 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.2 Kernel Version: 6.8.1-arch1-1 (64-bit) Graphics Platform: Wayland -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 483857] New: Cyclic dependency detected between "qrc:/qt/qml/org/kde/desktop/private/TextFieldContextMenu.qml" and "qrc:/qt/qml/org/kde/desktop/MenuItem.qml"
https://bugs.kde.org/show_bug.cgi?id=483857 Bug ID: 483857 Summary: Cyclic dependency detected between "qrc:/qt/qml/org/kde/desktop/private/TextFieldContextM enu.qml" and "qrc:/qt/qml/org/kde/desktop/MenuItem.qml" Classification: Plasma Product: kwin Version: 6.0.2 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: wayland-generic Assignee: kwin-bugs-n...@kde.org Reporter: istanko...@posteo.net Target Milestone: --- SUMMARY I get the following warning: kwin_wayland[1201]: qt.qml.typeresolution.cycle: Cyclic dependency detected between "qrc:/qt/qml/org/kde/desktop/private/TextFieldContextMenu.qml" and "qrc:/qt/qml/org/kde/desktop/MenuItem.qml" SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 6.0.2 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.2 Kernel Version: 6.8.1-arch1-1 (64-bit) Graphics Platform: Wayland -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 483856] New: Service file '/usr/share//dbus-1/services/org.kde.kscreen.service' is not named after the D-Bus name 'org.kde.KScreen'.
https://bugs.kde.org/show_bug.cgi?id=483856 Bug ID: 483856 Summary: Service file '/usr/share//dbus-1/services/org.kde.kscreen.service' is not named after the D-Bus name 'org.kde.KScreen'. Classification: Plasma Product: KScreen Version: 6.0.2 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: common Assignee: kscreen-bugs-n...@kde.org Reporter: istanko...@posteo.net Target Milestone: --- SUMMARY I get the following warning: Subject: Invalid service file Defined-By: dbus-broker Support: https://groups.google.com/forum/#!forum/bus1-devel A service file is a ini-type configuration file. It has one required section named [D-BUS Service]. The section contains the required key 'Name', which must be a valid D-Bus name that is unique across all service files. It also contains at least one of the two optional keys 'SystemdService' and 'Exec', as well as optionally the key 'User'. Exec must be a valid shell command and User must be a valid user on the system. A service file should be named after the D-Bus name it configures. That is a file containing Name=org.foo.bar1 should be named org.foo.bar1.service. For backwards compatibility, we only warn when files do not follow this convention when run as a user bus. The system bus considers this an error and ignores the service file. dbus-broker-launch[1141]: Service file '/usr/share//dbus-1/services/org.kde.kscreen.service' is not named after the D-Bus name 'org.kde.KScreen'. SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 6.0.2 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.2 Kernel Version: 6.8.1-arch1-1 (64-bit) Graphics Platform: Wayland -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 482980] Keyboard repeat does not work
https://bugs.kde.org/show_bug.cgi?id=482980
--- Comment #9 from Ivan Stankovic ---
On Arch I think I only needed the ibus and ibus-hangul packages. I assume the
virtual keyboard module of KDE system settings then automatically recognized
the available input method engine.
These are the IBus processes and their arguments that I have running:
/usr/lib/ibus/ibus-ui-gtk3 --enable-wayland-im --exec-daemon --daemon-args
--xim --panel disable
ibus-daemon --xim --panel disable
/usr/lib/ibus/ibus-dconf
/usr/lib/ibus/ibus-extension-gtk3
/usr/lib/ibus/ibus-x11 --kill-daemon
/usr/lib/ibus/ibus-portal
/usr/lib/ibus/ibus-engine-simple
/usr/lib/ibus/ibus-engine-hangul --ibus
And it's all started by kwin_wayland:
├─kwin_wayland_wr─┬─kwin_wayland─┬─Xwayland───9*[{Xwayland}]
│ │
├─ibus-ui-gtk3─┬─ibus-daemon─┬─ibus-dconf───4*[{ibus-dconf}]
│ │ │ │
├─ibus-engine-han───4*[{ibus-engine-han}]
│ │ │ │
├─ibus-engine-sim───3*[{ibus-engine-sim}]
│ │ │ │
├─ibus-extension-───4*[{ibus-extension-}]
│ │ │ │
└─3*[{ibus-daemon}]
│ │ │ └─5*[{ibus-ui-gtk3}]
│ │ └─38*[{kwin_wayland}]
│ └─{kwin_wayland_wr}
--
You are receiving this mail because:
You are watching all bug changes.
[konsole] [Bug 482980] Keyboard repeat does not work
https://bugs.kde.org/show_bug.cgi?id=482980 --- Comment #7 from Ivan Stankovic --- You do not need to have a touchscreen device to reproduce this. I for sure don't have one. Just 1. install IBus 2. enable IBus Wayland virtual keyboard in system settings 3. add 2 different keyboard layouts in keyboard settings (I'm guessing any two will do) -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 482185] Context menu (when right-clicking on the desktop) appears in a separate window after external monitor restart
https://bugs.kde.org/show_bug.cgi?id=482185 ivan changed: What|Removed |Added CC||v...@ircsystem.net --- Comment #10 from ivan --- Using Neon and Wayland, can confirm this issue. I'm on a desktop workstation with a single DP monitor and as soon as it gets powered off by either power saving rules or a suspend action, when the monitor turns on, the right client context menu on desktop gets rendered in a window at the center of the screen if another window is in focus. A plasmashell restart fixes it temporarly, until the screen goes off again. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 482980] Keyboard repeat does not work
https://bugs.kde.org/show_bug.cgi?id=482980 Ivan Stankovic changed: What|Removed |Added Resolution|WAITINGFORINFO |--- Status|NEEDSINFO |REPORTED --- Comment #5 from Ivan Stankovic --- Alright, this seems to be due to me using the IBus Wayland virtual keyboard (System Settings -> Keyboard -> Virtual Keyboard). Once I select "None" virtual keyboard, key repeat works fine. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 482980] Keyboard repeat does not work
https://bugs.kde.org/show_bug.cgi?id=482980 --- Comment #4 from Ivan Stankovic --- This is also not a problem with my keyboard since key repeat works fine in the console (ttyX). -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 482980] Keyboard repeat does not work
https://bugs.kde.org/show_bug.cgi?id=482980 --- Comment #3 from Ivan Stankovic --- Still an issue, even with 6.0.2. I'm unable to trigger key repeat with regular keys (e.g. 'j', 'k'), but key repeat works fine with keys like 'PageUp', 'Up arrow'. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 483557] Right clicking on panel when not focused on the desktop after switching monitors causes the context menu to open in a window
https://bugs.kde.org/show_bug.cgi?id=483557 ivan changed: What|Removed |Added CC||v...@ircsystem.net --- Comment #2 from ivan --- On Wayland the same thing happens when waking from sleep and/or locking and unlocking the session. Every right click on desktop or on panels when the focus is on another application will result in the contextual menu to appear in the middle of the screen. If the desktop or panel is focused via left click first, then the menu will appear correctly under the mouse, but the situation doesn't heal if the focus is given back to an application. A plasmashell restart fixes it. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 482980] Keyboard repeat does not work
https://bugs.kde.org/show_bug.cgi?id=482980 --- Comment #1 from Ivan Stankovic --- This seems not to be konsole-specific; same behaviour can be observed system-wide, e.g. in kate etc. -- You are receiving this mail because: You are watching all bug changes.
[Plasma Vault] [Bug 483063] Unable to detect cryfs/encfs/encfsctl/gocryptfs version - cannot create a vault
https://bugs.kde.org/show_bug.cgi?id=483063 --- Comment #1 from Ivan Čukić --- Hi, Do you have cryfs, encfs or gocryptfs installed, and available in your $PATH? -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 482980] Keyboard repeat does not work
https://bugs.kde.org/show_bug.cgi?id=482980 Ivan Stankovic changed: What|Removed |Added Keywords||qt6, wayland -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 482980] Keyboard repeat does not work
https://bugs.kde.org/show_bug.cgi?id=482980 Ivan Stankovic changed: What|Removed |Added Platform|Other |Arch Linux -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 482980] New: Keyboard repeat does not work
https://bugs.kde.org/show_bug.cgi?id=482980 Bug ID: 482980 Summary: Keyboard repeat does not work Classification: Applications Product: konsole Version: 24.02.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: keyboard Assignee: konsole-de...@kde.org Reporter: istanko...@posteo.net Target Milestone: --- SUMMARY It seems that keyboard repeat stopped working in konsole, or, more precisely, it fails to start in many cases. There are cases where it's possible to trigger a key repeat, but it is unclear how precisely. One thing that I've noticed is that after switching focus to konsole from another application, it makes it more likely for key repeat to work, but _only_ for the first time. Subsequent attempts at key repeat do not work. STEPS TO REPRODUCE 1. Make sure key repeat is enabled in keyboard settings 2. Open konsole 3. Press a key and hold it down OBSERVED RESULT Only one character is printed. EXPECTED RESULT Same character should be repeatedly output, as long as the key is held down. SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 6.0.1 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.2 Kernel Version: 6.7.9-arch1-1 (64-bit) Graphics Platform: Wayland -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 422324] Desktop offset horizontally from display
https://bugs.kde.org/show_bug.cgi?id=422324 Ivan Korytov changed: What|Removed |Added CC||boot@yandex.ru -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kconfig] [Bug 482149] F10 as menu shortcut steals it from applications
https://bugs.kde.org/show_bug.cgi?id=482149 --- Comment #8 from Ivan --- > Of course any change we ever make (even if it is during a major transition > from Qt 5 to Qt 6 like this) will go against previously expected behaviour. > I don't really see though in what way what you are saying disagrees with me. > I do agree with your point that it is unwanted when a terminal program's F10 > shortcut doesn't work because it was stolen by Konsole. But this doesn't > change the argument I made which was: "When a completely blind person sits > in front of Konsole and tries to go to the menu F10 is their only option > AFAIK. Take that away and they can't even open the help menu AFAIK." I disagree that conservative approach is not a way to go. Terminal is very special application and it should be excluded from a "normal" behaviour. IMHO F10 to open a menu is a stupid idea in the first place in the same way as F11 for full screen etc. It may work well in a browser, but not in all applications. And when it comes to terminal - it's not just an app, it's a container for running apps. I don't think that terminal should be aware what keys are used in a terminal app and to decide when to open the menu or to pass. I have lots of scripts I created that utilise all F keys. And I always loved Konsole. Suddenly I'm in a big trouble. Not to mention popular apps like mc, htop etc. IMHO getting rid of this "feature" is a way to go, or at least adding something like shift+F10, like they did for copy-paste (ctrl+shift+c). I wouldn't be surprised if someone wants to use ctrl+c in terminal for copy :) -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kconfig] [Bug 482149] F10 as menu shortcut steals it from applications
https://bugs.kde.org/show_bug.cgi?id=482149 Ivan changed: What|Removed |Added CC||knezivan...@gmail.com --- Comment #6 from Ivan --- (In reply to Felix Ernst from comment #4) > I am not sure "being conservative" works here. When a completely blind > person sits in front of Konsole and tries to go to the menu F10 is their > only option AFAIK. Take that away and they can't even open the help menu > AFAIK. > > That's why I suggested that Konsole should only give up control of the F10 > key when the current terminal application uses it. This way the general > accessibility of Konsole doesn't have to suffer just because some terminal > applications also want to use F10. I disagree. F10 is often used in terminal applications. People are used to Ctrl+C and Ctrl+V and other common shortcuts, but that's not how it works in Konsole. The same should be applied to F10 and F11. I'm pretty much blind and when I'm using terminal apps like I'm used to instead of getting F10 action from my application I'm getting some useless menu. In my opinion this is serious bug -- You are receiving this mail because: You are watching all bug changes.
[kinfocenter] [Bug 482296] New: The Energy Saver information screen is not stable. Constantly rattles with great frequency.
https://bugs.kde.org/show_bug.cgi?id=482296 Bug ID: 482296 Summary: The Energy Saver information screen is not stable. Constantly rattles with great frequency. Classification: Applications Product: kinfocenter Version: 5.27.5 Platform: Debian stable OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: ivan.chernousov.1...@gmail.com CC: sit...@kde.org Target Milestone: --- Created attachment 166348 --> https://bugs.kde.org/attachment.cgi?id=166348=edit Recording the Energy Saving-System Information window. SUMMARY: The Energy Saver information screen is not stable. Constantly rattles with great frequency. Video from the screen is attached. EXPECTED RESULT Fix bug. SOFTWARE/OS VERSIONS Linux/KDE Plasma: 5.27.5 (available in About System) KDE Plasma Version: 5.27.5 KDE Frameworks Version: 5.103.0 Qt Version: 5.15.8 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 452119] With an Intel iGPU, animations aren't as smooth on Wayland versus Xorg
https://bugs.kde.org/show_bug.cgi?id=452119 Ivan D Vasin changed: What|Removed |Added CC||i...@nisavid.io -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 481735] New: program crashes when trying to open an image with parameter luminosity in metadata
https://bugs.kde.org/show_bug.cgi?id=481735 Bug ID: 481735 Summary: program crashes when trying to open an image with parameter luminosity in metadata Classification: Applications Product: digikam Version: 8.2.0 Platform: Microsoft Windows OS: Microsoft Windows Status: REPORTED Severity: crash Priority: NOR Component: Metadata-Exif Assignee: digikam-bugs-n...@kde.org Reporter: korti...@gmail.com Target Milestone: --- Created attachment 166045 --> https://bugs.kde.org/attachment.cgi?id=166045=edit In the attached files is an example of an image with metadata that is causing the crash SUMMARY If the image metadata has a parameter with more characters after zero (3.909536743164), a crash occurs. And what is worse, after that it is impossible to load the program, and have to demolish the whole database, so that it does not contain this number. STEPS TO REPRODUCE 1. Download the attached file 2. Try to read it in the program or enter it into the database 3. See the result OBSERVED RESULT crash EXPECTED RESULT no crashes program and database didn't crash SOFTWARE/OS VERSIONS Windows: Windows 11 Pro 23H2 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 479254] Window for entering fingerprint is too tall
https://bugs.kde.org/show_bug.cgi?id=479254 Ivan Sosnov changed: What|Removed |Added CC||ivanmsos...@gmail.com --- Comment #3 from Ivan Sosnov --- Can still reproduce on 5.93.0 at any resolution or scaling -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 469062] Moving some icons on primary screen while secondary screen is unplugged resets icon positions on the secondary screen
https://bugs.kde.org/show_bug.cgi?id=469062 Ivan Korytov changed: What|Removed |Added CC||boot@yandex.ru -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 465747] desktop icons moved to secondary monitor upon login
https://bugs.kde.org/show_bug.cgi?id=465747 Ivan Korytov changed: What|Removed |Added CC||boot@yandex.ru -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 468546] Desktop icons reset position when switching between laptop and external displays with different resolutions
https://bugs.kde.org/show_bug.cgi?id=468546 Ivan Korytov changed: What|Removed |Added CC||boot@yandex.ru -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 466869] Desktop icons reset positions after changing screen setup
https://bugs.kde.org/show_bug.cgi?id=466869 Ivan Korytov changed: What|Removed |Added CC||boot@yandex.ru -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 479894] New: Several settings categories overflow the window
https://bugs.kde.org/show_bug.cgi?id=479894 Bug ID: 479894 Summary: Several settings categories overflow the window Classification: Applications Product: systemsettings Version: 5.92.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: ivanmsos...@gmail.com Target Milestone: --- Created attachment 164951 --> https://bugs.kde.org/attachment.cgi?id=164951=edit Example of a cut off window SUMMARY Several settings categories do not fit in their window margins, essentially cutting off parts of the view structure STEPS TO REPRODUCE 1. Open System Settings 2. Navigate into Quick Settings, Accessibility, Colors & Themes (and all sub-categories), Text & Font, Wallpapers, Notifications, General Behavior, Search, Screen Locking, About this System, Energy Saving, Software Updates, Users, or Autostart 3. Occurs with 100% success rate OBSERVED RESULT Top of the view is cut off EXPECTED RESULT Top of the view not being cut off SOFTWARE/OS VERSIONS Linux/KDE Plasma: Archlinux on kde-unstable KDE Plasma Version: 5.92.0 KDE Frameworks Version: 5.248.0 Qt Version: 6.7.0beta1-2 Nvidia: 545.29.06 -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 477662] New: Saved display style differ for a shared folder and symlink
https://bugs.kde.org/show_bug.cgi?id=477662 Bug ID: 477662 Summary: Saved display style differ for a shared folder and symlink Classification: Applications Product: dolphin Version: 23.04.3 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: view-engine: general Assignee: dolphin-bugs-n...@kde.org Reporter: boot@yandex.ru CC: kfm-de...@kde.org Target Milestone: --- STEPS TO REPRODUCE 1. Set option "View" to "Remember display style" in Dolphin configuration 2. Get in to a shared folder (e.g. /mnt/shares/Public), set view option to Compact 3. Create symlink to that folder somewhere else (e.g. /home/user/Desktop/Public) 4. Get in to a folder using symlink OBSERVED RESULT Display style in symlink (/home/user/Desktop/Public) is not the same as in folder itself (/mnt/shares/Public). EXPECTED RESULT Display style in symlink is the same as in folder itself, because they are the same folder, only path differs. SOFTWARE/OS VERSIONS Linux/KDE Plasma: ALT Linux Workstation K 10.2 x86_64 KDE Plasma Version: 5.27.9 KDE Frameworks Version: 5.111.0 Qt Version: 5.15.10 ADDITIONAL INFORMATION Dolphin creates a structure to hold .directory files for shared folders in ~/.local/share/dolphin/view_properties and it confirms that it differentiates between folder and symlink by storing separate settings for them. For other directories, e.g. ~/Downloads, there is no such behavior, because .directory file created in the directory itslef, not in "view_properties". For shared folders, keeping the .directory files separate should be more convenient, because user doesn't always have access to write in the root of the shared folder. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 414621] I cannot press play to play the animation in krita to look it over. It will not play no matter how much I try.
https://bugs.kde.org/show_bug.cgi?id=414621 Ivan Padilla changed: What|Removed |Added CC||shico.toz...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 476633] Plasma crash due to lack of memory
https://bugs.kde.org/show_bug.cgi?id=476633 --- Comment #2 from Ivan --- Created attachment 163249 --> https://bugs.kde.org/attachment.cgi?id=163249=edit New crash information added by DrKonqi plasmashell (5.27.5) using Qt 5.15.8 i was just browsing with firefox, then plasma suddenly crashed (maybe due to lack of ram, because around 2.6 gib and 712 mib of swap were used out of 4 gib and 1 gb) -- Backtrace (Reduced): #5 0x7f13e5966c86 in QtQml::qmlExecuteDeferred(QObject*) () from /lib/x86_64-linux-gnu/libQt5Qml.so.5 #6 0x7f13e5d76059 in QQuickTransition::prepare(QList&, QList&, QQuickTransitionManager*, QObject*) () from /lib/x86_64-linux-gnu/libQt5Quick.so.5 #7 0x7f13e5d6b997 in QQuickTransitionManager::transition(QList const&, QQuickTransition*, QObject*) () from /lib/x86_64-linux-gnu/libQt5Quick.so.5 #8 0x7f13e431650d in QObject::event(QEvent*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #9 0x7f13e4fdffae in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 476633] Plasma crash due to lack of memory
https://bugs.kde.org/show_bug.cgi?id=476633 Ivan changed: What|Removed |Added CC||oivan2...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 472712] Filesystem tree jumps to selected folder when expanding another folder
https://bugs.kde.org/show_bug.cgi?id=472712 Ivan Korytov changed: What|Removed |Added CC||boot@yandex.ru -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 469730] Night color shifting happens at the wrong time during daylight savings time when using manual Date & Time setting
https://bugs.kde.org/show_bug.cgi?id=469730 --- Comment #33 from Ivan Garcia --- (In reply to Natalie Clarius from comment #32) > Is it the case that the time that it says would be sunset is correct but it > only actually kicks in one hour after it's dark, or does it display a wrong > time for when it should be sunset at your location but the actual effect is > aligned with the sun hours? it shows the correct sunset time( when night color supposed to kick in) but at least for me it kicks in at 2PM EST even though it detects the coordinates and calculates the time correctly (18:37 EST, full transition 19:20 EST). -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 431057] Refresh rate values in Display Configuration menu are always incorrect due to floating-point precision issues
https://bugs.kde.org/show_bug.cgi?id=431057 Ivan Korytov changed: What|Removed |Added CC||boot@yandex.ru -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 471639] Transition to night color starts way too early
https://bugs.kde.org/show_bug.cgi?id=471639 --- Comment #8 from Ivan Garcia --- (In reply to Ivan Garcia from comment #6) > (In reply to Nate Graham from comment #4) > > The geolocator should print the location it calculated. Can you verify that > > it's correct? > > It calculates the location correctly. It also shows the times where it is > going to change color accurately as well. The issue is that it does not > honor the settings. As everyone stated here, if you set it to "manual" night > light works as expected. It does not show on the screenshot but night color is active (4500k) even though it was only 5:01PMEST -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 471639] Transition to night color starts way too early
https://bugs.kde.org/show_bug.cgi?id=471639 --- Comment #7 from Ivan Garcia --- Created attachment 162387 --> https://bugs.kde.org/attachment.cgi?id=162387=edit night light -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 471639] Transition to night color starts way too early
https://bugs.kde.org/show_bug.cgi?id=471639 Ivan Garcia changed: What|Removed |Added CC||igar...@cloudox.org --- Comment #6 from Ivan Garcia --- (In reply to Nate Graham from comment #4) > The geolocator should print the location it calculated. Can you verify that > it's correct? It calculates the location correctly. It also shows the times where it is going to change color accurately as well. The issue is that it does not honor the settings. As everyone stated here, if you set it to "manual" night light works as expected. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 475729] plasma crash when closing notification message
https://bugs.kde.org/show_bug.cgi?id=475729 --- Comment #1 from Ivan Panayotov --- Created attachment 162368 --> https://bugs.kde.org/attachment.cgi?id=162368=edit New crash information added by DrKonqi plasmashell (5.27.5) using Qt 5.15.8 this crash appear when pc is turning on displays from sleep -- Backtrace (Reduced): #6 0x7f644ab9b49b in QWidget::removeAction(QAction*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 [...] #8 0x7f644ab62fae in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #9 0x7f6449eb16f8 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #10 0x7f6449ee6b07 in QObjectPrivate::setParent_helper(QObject*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #11 0x7f6449ee7083 in QObject::~QObject() () from /lib/x86_64-linux-gnu/libQt5Core.so.5 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 475729] plasma crash when closing notification message
https://bugs.kde.org/show_bug.cgi?id=475729 Ivan Panayotov changed: What|Removed |Added CC||panayoto...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 475729] New: plasma crash when closing notification message
https://bugs.kde.org/show_bug.cgi?id=475729 Bug ID: 475729 Summary: plasma crash when closing notification message Classification: Plasma Product: plasmashell Version: 5.27.5 Platform: Debian stable OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: panayoto...@gmail.com CC: k...@davidedmundson.co.uk Target Milestone: 1.0 Application: plasmashell (5.27.5) Qt Version: 5.15.8 Frameworks Version: 5.103.0 Operating System: Linux 6.1.0-13-amd64 x86_64 Windowing System: X11 Distribution: Debian GNU/Linux 12 (bookworm) DrKonqi: 5.27.5 [CoredumpBackend] -- Information about the crash: plasma crash when closing notification message. it happen several times per week. not to severe bug The reporter is unsure if this crash is reproducible. -- Backtrace: Application: Plasma (plasmashell), signal: Segmentation fault PID: 1255 (plasmashell) UID: 1000 (panayotovip) GID: 1000 (panayotovip) Signal: 11 (SEGV) Timestamp: Tue 2023-10-17 09:53:26 EEST (45s ago) Command Line: /usr/bin/plasmashell --no-respawn Executable: /usr/bin/plasmashell Control Group: /user.slice/user-1000.slice/user@1000.service/session.slice/plasma-plasmashell.service Unit: user@1000.service User Unit: plasma-plasmashell.service Slice: user-1000.slice Owner UID: 1000 (panayotovip) Boot ID: b927a14f2a2942918a3c2be87b388cc4 Machine ID: 93b8132d78914146b529766d901bc920 Hostname: station Storage: /var/lib/systemd/coredump/core.plasmashell.1000.b927a14f2a2942918a3c2be87b388cc4.1255.169752560600.zst (present) Size on Disk: 41.3M Message: Process 1255 (plasmashell) of user 1000 dumped core. Module libsystemd.so.0 from deb systemd-252.17-1~deb12u1.amd64 Module libudev.so.1 from deb systemd-252.17-1~deb12u1.amd64 Stack trace of thread 1255: #0 0x7f2ad92aec24 pthread_sigmask (libc.so.6 + 0x8fc24) #1 0x7f2ad925b1b9 sigprocmask (libc.so.6 + 0x3c1b9) #2 0x7f2adb8dce9b _ZN6KCrash15setCrashHandlerEPFviE (libKF5Crash.so.5 + 0x4e9b) #3 0x7f2adb8ddb3e _ZN6KCrash19defaultCrashHandlerEi (libKF5Crash.so.5 + 0x5b3e) #4 0x7f2ad925afd0 n/a (libc.so.6 + 0x3bfd0) #5 0x7f2ada58a56b n/a (libQt5Widgets.so.5 + 0x18a56b) #6 0x7f2ada59b49b _ZN7QWidget12removeActionEP7QAction (libQt5Widgets.so.5 + 0x19b49b) #7 0x7f2a9dd8bf94 n/a (libplasmacomponentsplugin.so + 0xff94) #8 0x7f2ada562fae _ZN19QApplicationPrivate13notify_helperEP7QObjectP6QEvent (libQt5Widgets.so.5 + 0x162fae) #9 0x7f2ad96b16f8 _ZN16QCoreApplication15notifyInternal2EP7QObjectP6QEvent (libQt5Core.so.5 + 0x2b16f8) #10 0x7f2ad96e6b07 _ZN14QObjectPrivate16setParent_helperEP7QObject (libQt5Core.so.5 + 0x2e6b07) #11 0x7f2ad96e7083 _ZN7QObjectD2Ev (libQt5Core.so.5 + 0x2e7083) #12 0x7f2a9dd88ac6 n/a (libplasmacomponentsplugin.so + 0xcac6) #13 0x7f2ad96dd4bf _ZN7QObject5eventEP6QEvent (libQt5Core.so.5 + 0x2dd4bf) #14 0x7f2ada562fae _ZN19QApplicationPrivate13notify_helperEP7QObjectP6QEvent (libQt5Widgets.so.5 + 0x162fae) #15 0x7f2ad96b16f8 _ZN16QCoreApplication15notifyInternal2EP7QObjectP6QEvent (libQt5Core.so.5 + 0x2b16f8) #16 0x7f2ad96b4681 _ZN23QCoreApplicationPrivate16sendPostedEventsEP7QObjectiP11QThreadData (libQt5Core.so.5 + 0x2b4681) #17 0x7f2ad970a153 n/a (libQt5Core.so.5 + 0x30a153) #18 0x7f2ad81017a9 g_main_context_dispatch (libglib-2.0.so.0 + 0x547a9) #19 0x7f2ad8101a38 n/a (libglib-2.0.so.0 + 0x54a38) #20 0x7f2ad8101acc g_main_context_iteration (libglib-2.0.so.0 + 0x54acc) #21 0x7f2ad9709836 _ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE (libQt5Core.so.5 + 0x309836) #22 0x7f2ad96b017b _ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE (libQt5Core.so.5 + 0x2b017b) #23 0x7f2ad96b82d6 _ZN16QCoreApplication4execEv (libQt5Core.so.5 + 0x2b82d6) #24 0x560388dcbdc3 n/a (plasmashell + 0x26dc3) #25 0x7f2ad92461ca n/a (libc.so.6 + 0x271ca) #26 0x7f2ad9246285 __libc_start_main (libc.so.6 + 0x27285) #27 0x560388dcbee1 n/a (plasmashell + 0x26ee1) Stack trace of thread 1287: #0 0x7f2ad931b05f __poll (libc.so.6 + 0xfc05f) #1 0x7f2ad81019ae n/a (libglib-2.0.so.0 +
[systemsettings] [Bug 469730] Night color shifting does not start at the correct time or end at the correct time
https://bugs.kde.org/show_bug.cgi?id=469730 --- Comment #19 from Ivan Garcia --- (In reply to Nate Graham from comment #17) > So you switched away from KDE since submitting this bug report? This bug is present on Fedora 38 KDE as well. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 354109] Custom shortcuts: Window Data autodetect (conditions > new > active window) removes mouse button function
https://bugs.kde.org/show_bug.cgi?id=354109 ivan.tsyauk2...@yandex.ru changed: What|Removed |Added CC||ivan.tsyauk2...@yandex.ru --- Comment #10 from ivan.tsyauk2...@yandex.ru --- I have exactly the same bug. Operating System: Manjaro Linux KDE Plasma Version: 5.27.8 KDE Frameworks Version: 5.110.0 Qt Version: 5.15.10 Kernel Version: 6.1.53-1-MANJARO (64-bit) Graphics Platform: X11 Processors: 24 × AMD Ryzen 9 5900X 12-Core Processor Memory: 15,6 GiB of RAM Graphics Processor: NVIDIA GeForce GTX 1050 Ti/PCIe/SSE2 Manufacturer: Gigabyte Technology Co., Ltd. Product Name: B550 AORUS PRO AC -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 469260] Sometimes new files created in ~/Desktop not using Folder View don't show up
https://bugs.kde.org/show_bug.cgi?id=469260 Ivan Korytov changed: What|Removed |Added CC||boot@yandex.ru -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 474322] Refresh Desktop command doesn't actually do anything
https://bugs.kde.org/show_bug.cgi?id=474322 Ivan Korytov changed: What|Removed |Added CC||boot@yandex.ru -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 449163] Plasma panel visually freezes after some time under Wayland
https://bugs.kde.org/show_bug.cgi?id=449163 Ivan Sosnov changed: What|Removed |Added CC|ivanmsos...@gmail.com | -- You are receiving this mail because: You are watching all bug changes.
[partitionmanager] [Bug 474183] New: Add dev path to KDE Partition Manager Partition properties window
https://bugs.kde.org/show_bug.cgi?id=474183 Bug ID: 474183 Summary: Add dev path to KDE Partition Manager Partition properties window Classification: Applications Product: partitionmanager Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: general Assignee: andr...@stikonas.eu Reporter: driz...@zoho.eu Target Milestone: --- Created attachment 161411 --> https://bugs.kde.org/attachment.cgi?id=161411=edit Dev path Please add dev name info on Partition properties window. Look at screenshot. Sometimes need to copy path to device for using in terminal. Now no way to do this. Path can be found in window title but it can't be copied from this place. -- You are receiving this mail because: You are watching all bug changes.
[Skanpage] [Bug 474010] New: List of scanners doesn't fit inside window
https://bugs.kde.org/show_bug.cgi?id=474010 Bug ID: 474010 Summary: List of scanners doesn't fit inside window Classification: Applications Product: Skanpage Version: 22.12.3 Platform: Other OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: general Assignee: a.stipp...@gmx.net Reporter: boot@yandex.ru Target Milestone: --- Created attachment 161319 --> https://bugs.kde.org/attachment.cgi?id=161319=edit List of scanners STEPS TO REPRODUCE 1. Find a network with 10+ MFPs that have AirScan enabled 2. Open Skanpage 3. Try to confirm selection of one of them OBSERVED RESULT List of scanners doesn't fit inside window and no scrollbar available, bottom buttons to select scanner and refresh the list are not visible. EXPECTED RESULT List of scanners is scrollable and bottom buttons are fixed at the bottom edge, or displayed as a dropdown box. SOFTWARE/OS VERSIONS Linux/KDE Plasma: ALT Linux Workstation K 10.1, KDE Plasma 5.27.6 KDE Plasma Version: 5.27.6 KDE Frameworks Version: 5.108.0 Qt Version: 5.15.10 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 469730] Night color shifting does not start at the correct time or end at the correct time
https://bugs.kde.org/show_bug.cgi?id=469730 --- Comment #11 from Ivan Garcia --- (In reply to Nate Graham from comment #8) > Can you please paste the output of running `qdbus org.kde.KWin /ColorCorrect > GetAll org.kde.kwin.ColorCorrect` in a terminal window when the screen color > temperature is incorrect? Please also specify the expected screen > temperature. Thanks! Info attached, thanks! -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 471517] Whole-screen diagonal-stripes glitch on external display with hybrid graphics
https://bugs.kde.org/show_bug.cgi?id=471517 Ivan D Vasin changed: What|Removed |Added Status|RESOLVED|REOPENED Resolution|FIXED |--- --- Comment #14 from Ivan D Vasin --- Unfortunately, the issue persists even after updating to Plasma 5.27.7. Unsetting KWIN_DRM_DEVICES brings back the same distortion as before. Are there any other diagnostics I can provide that might help pin this down? I also have the KDE/Plasma 5 sources set up for building. Happy to try out patches without waiting for a release. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 473058] New: Plasma shell crashes after deleting new default panel and closing "panel removed" notification
https://bugs.kde.org/show_bug.cgi?id=473058 Bug ID: 473058 Summary: Plasma shell crashes after deleting new default panel and closing "panel removed" notification Classification: Plasma Product: plasmashell Version: 5.27.5 Platform: Debian stable OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: ivan@gmail.com CC: k...@davidedmundson.co.uk Target Milestone: 1.0 Application: plasmashell (5.27.5) Qt Version: 5.15.8 Frameworks Version: 5.103.0 Operating System: Linux 6.1.0-10-amd64 x86_64 Windowing System: Wayland Distribution: Debian GNU/Linux 12 (bookworm) DrKonqi: 5.27.5 [CoredumpBackend] -- Information about the crash: Created new default panel, edited the panel and then deleted it. After closing the "panel removed" notification by clicking on the red "x" button plasma suddenly crashed. The reporter is unsure if this crash is reproducible. -- Backtrace: Application: Plasma (plasmashell), signal: Segmentation fault PID: 1198 (plasmashell) UID: 1000 (ivan) GID: 1000 (ivan) Signal: 11 (SEGV) Timestamp: Sun 2023-08-06 00:33:46 CEST (1min 10s ago) Command Line: /usr/bin/plasmashell --no-respawn Executable: /usr/bin/plasmashell Control Group: /user.slice/user-1000.slice/user@1000.service/session.slice/plasma-plasmashell.service Unit: user@1000.service User Unit: plasma-plasmashell.service Slice: user-1000.slice Owner UID: 1000 (ivan) Boot ID: 6949b5c50f2944ba9b898954483c1eec Machine ID: f9a42193b6db47fb9d2cae67364f9a30 Hostname: minipc Storage: /var/lib/systemd/coredump/core.plasmashell.1000.6949b5c50f2944ba9b898954483c1eec.1198.169127482600.zst (present) Size on Disk: 29.6M Message: Process 1198 (plasmashell) of user 1000 dumped core. Module libsystemd.so.0 from deb systemd-252.12-1~deb12u1.amd64 Module libudev.so.1 from deb systemd-252.12-1~deb12u1.amd64 Stack trace of thread 1198: #0 0x7f3efdeaec24 pthread_sigmask (libc.so.6 + 0x8fc24) #1 0x7f3efde5b1b9 sigprocmask (libc.so.6 + 0x3c1b9) #2 0x7f3f004f1e9b _ZN6KCrash15setCrashHandlerEPFviE (libKF5Crash.so.5 + 0x4e9b) #3 0x7f3f004f2b3e _ZN6KCrash19defaultCrashHandlerEi (libKF5Crash.so.5 + 0x5b3e) #4 0x7f3efde5afd0 n/a (libc.so.6 + 0x3bfd0) #5 0x7f3effa77c86 _ZN5QtQml18qmlExecuteDeferredEP7QObject (libQt5Qml.so.5 + 0x277c86) #6 0x7f3efff49059 _ZN16QQuickTransition7prepareER5QListI17QQuickStateActionERS0_I12QQmlPropertyEP23QQuickTransitionManagerP7QObject (libQt5Quick.so.5 + 0x149059) #7 0x7f3efff3e997 _ZN23QQuickTransitionManager10transitionERK5QListI17QQuickStateActionEP16QQuickTransitionP7QObject (libQt5Quick.so.5 + 0x13e997) #8 0x7f3efe2dd50d _ZN7QObject5eventEP6QEvent (libQt5Core.so.5 + 0x2dd50d) #9 0x7f3eff162fae _ZN19QApplicationPrivate13notify_helperEP7QObjectP6QEvent (libQt5Widgets.so.5 + 0x162fae) #10 0x7f3efe2b16f8 _ZN16QCoreApplication15notifyInternal2EP7QObjectP6QEvent (libQt5Core.so.5 + 0x2b16f8) #11 0x7f3efe308c31 _ZN14QTimerInfoList14activateTimersEv (libQt5Core.so.5 + 0x308c31) #12 0x7f3efe3094c4 n/a (libQt5Core.so.5 + 0x3094c4) #13 0x7f3efcd017a9 g_main_context_dispatch (libglib-2.0.so.0 + 0x547a9) #14 0x7f3efcd01a38 n/a (libglib-2.0.so.0 + 0x54a38) #15 0x7f3efcd01acc g_main_context_iteration (libglib-2.0.so.0 + 0x54acc) #16 0x7f3efe309836 _ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE (libQt5Core.so.5 + 0x309836) #17 0x7f3efe2b017b _ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE (libQt5Core.so.5 + 0x2b017b) #18 0x7f3efe2b82d6 _ZN16QCoreApplication4execEv (libQt5Core.so.5 + 0x2b82d6) #19 0x55c346242dc3 n/a (plasmashell + 0x26dc3) #20 0x7f3efde461ca n/a (libc.so.6 + 0x271ca) #21 0x7f3efde46285 __libc_start_main (libc.so.6 + 0x27285) #22 0x55c346242ee1 n/a (plasmashell + 0x26ee1) Stack trace of thread 1215: #0 0x7f3efdea4da6 n/a (libc.so.6 + 0x85da6) #1 0x7f3efdea7468 pthread_cond_wait (libc.so.6 + 0x88468) #2 0x7f3efe0d1a2b _ZN14QWaitCondition4waitEP6QMutex14QDeadlineTimer (libQt5Core.so.5 + 0xd1a2b) #3 0x7f3eff72fc7f n/a (libQt5WaylandClient.so.5 + 0x7ac7f)
[Akonadi] [Bug 472915] New: Drag drop moving email in Thunderbird and desktop environment crashed
https://bugs.kde.org/show_bug.cgi?id=472915 Bug ID: 472915 Summary: Drag drop moving email in Thunderbird and desktop environment crashed Classification: Frameworks and Libraries Product: Akonadi Version: unspecified Platform: Fedora RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: server Assignee: kdepim-b...@kde.org Reporter: drz.se.genera...@gmail.com CC: c...@carlschwan.eu Target Milestone: --- Application: akonadiserver (5.22.3 (22.12.3)) Qt Version: 5.15.9 Frameworks Version: 5.105.0 Operating System: Linux 6.4.6-100.fc37.x86_64 x86_64 Windowing System: Wayland Distribution: Fedora Linux 37 (KDE Plasma) DrKonqi: 5.27.4 [KCrashBackend] -- Information about the crash: Was trying to drag-drop move email from one Thunderbird folder to another when desktop environment restarted. The reporter is unsure if this crash is reproducible. -- Backtrace: Application: Akonadi Server (akonadiserver), signal: Segmentation fault [KCrash Handler] #4 0x562ed552729b in Akonadi::Server::AkonadiServer::connectionDisconnected() () #5 0x7f805fec8264 in QObject::event(QEvent*) () from /lib64/libQt5Core.so.5 #6 0x7f805fe9d5fb in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /lib64/libQt5Core.so.5 #7 0x7f805fea0984 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () from /lib64/libQt5Core.so.5 #8 0x7f805feeec27 in postEventSourceDispatch(_GSource*, int (*)(void*), void*) () from /lib64/libQt5Core.so.5 #9 0x7f805e118c7f in g_main_context_dispatch () from /lib64/libglib-2.0.so.0 #10 0x7f805e16f118 in g_main_context_iterate.constprop () from /lib64/libglib-2.0.so.0 #11 0x7f805e115f00 in g_main_context_iteration () from /lib64/libglib-2.0.so.0 #12 0x7f805feee71a in QEventDispatcherGlib::processEvents(QFlags) () from /lib64/libQt5Core.so.5 #13 0x7f805fe9c06a in QEventLoop::exec(QFlags) () from /lib64/libQt5Core.so.5 #14 0x7f805fea4132 in QCoreApplication::exec() () from /lib64/libQt5Core.so.5 #15 0x562ed551d058 in main () [Inferior 1 (process 2053) detached] Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[Plasma Vault] [Bug 472633] vault lost all data
https://bugs.kde.org/show_bug.cgi?id=472633 --- Comment #3 from Ivan Čukić --- Looks like you put the wrong directory in the cryfs command - it should not be the path to the location where vault shows the data when opened, but the path to encrypted data. If you didn't change the default path when creating the vault, it will be in your home directory under ~/.local/share/plasma-vault/ Apart from getting the path from plasmavaultrc, you can also find all directories where cryfs keeps its data by doing (this will search only under your user's home directory): find ~ -name 'cryfs.config' > when I did the apt upgrade, it was open and had some security and > firmware updates, could it have some relevance? An update should not have an influence over the user data. -- You are receiving this mail because: You are watching all bug changes.
[Plasma Vault] [Bug 472633] vault lost all data
https://bugs.kde.org/show_bug.cgi?id=472633 --- Comment #1 from Ivan Čukić --- Vault doesn't handle the data, the only way for the data to disappear is if they were deleted or there was a filesystem corruption. I'd try to mount the cryfs manually - see the relevant paths in the .config/plasmavaultrc The location of the encrypted data is the path in square brackets. For example, [/home/user/.vaults/SomeVaultName.enc]. First, backup that directory somewhere just in case. After that, do this: mkdir /tmp/SomeVaultName cryfs /home/user/.vaults/SomeVaultName.enc /tmp/SomeVaultName If you get an error saying something about the filesystem needs to be upgraded, call cryfs --allow-filesystem-upgrade /home/user/.vaults/SomeVaultName.enc /tmp/ SomeVaultName If that doesn't help (it should mount the data into /tmp/SomeVaultName) post me the error message you got. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 472580] New: Baloo crashes
https://bugs.kde.org/show_bug.cgi?id=472580 Bug ID: 472580 Summary: Baloo crashes Classification: Frameworks and Libraries Product: frameworks-baloo Version: 5.108.0 Platform: Archlinux OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: Baloo File Daemon Assignee: baloo-bugs-n...@kde.org Reporter: codethe...@gmail.com Target Milestone: --- Application: baloo_file_extractor (5.108.0) Qt Version: 5.15.10 Frameworks Version: 5.108.0 Operating System: Linux 6.4.4-artix1-1 x86_64 Windowing System: X11 Distribution: Artix Linux DrKonqi: 5.27.6 [KCrashBackend] -- Information about the crash: When selecting themes and applying them in the kde settings for the screensaver, a "Baloo crashes" error appears when accessing the desktop from SDDM The crash can be reproduced every time. -- Backtrace: Application: Служба извлечения информации для поиска в подсистеме Baloo (baloo_file_extractor), signal: Aborted [KCrash Handler] #4 __pthread_kill_implementation (threadid=, signo=signo@entry=6, no_tid=no_tid@entry=0) at pthread_kill.c:44 #5 0x7ff0340a0983 in __pthread_kill_internal (signo=6, threadid=) at pthread_kill.c:78 #6 0x7ff034051ea8 in __GI_raise (sig=sig@entry=6) at ../sysdeps/posix/raise.c:26 #7 0x7ff03403b53d in __GI_abort () at abort.c:79 #8 0x7ff03450691e in ?? () from /usr/lib/liblmdb.so #9 0x7ff034504c2a in ?? () from /usr/lib/liblmdb.so #10 0x7ff034512646 in ?? () from /usr/lib/liblmdb.so #11 0x7ff034509d53 in ?? () from /usr/lib/liblmdb.so #12 0x7ff03450b987 in ?? () from /usr/lib/liblmdb.so #13 0x7ff03450fc8d in mdb_cursor_del () from /usr/lib/liblmdb.so #14 0x7ff034511485 in ?? () from /usr/lib/liblmdb.so #15 0x7ff035475db7 in Baloo::DocumentIdDB::del(unsigned long long) () from /usr/lib/libKF5BalooEngine.so.5 #16 0x7ff035484d7f in Baloo::Transaction::removePhaseOne(unsigned long long) () from /usr/lib/libKF5BalooEngine.so.5 #17 0x562a382d2176 in ?? () #18 0x562a382d324e in ?? () #19 0x7ff0348d2b77 in ?? () from /usr/lib/libQt5Core.so.5 #20 0x7ff0348c33fe in QObject::event(QEvent*) () from /usr/lib/libQt5Core.so.5 #21 0x7ff03489ba08 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /usr/lib/libQt5Core.so.5 #22 0x7ff0348ea07b in QTimerInfoList::activateTimers() () from /usr/lib/libQt5Core.so.5 #23 0x7ff0348ea65a in ?? () from /usr/lib/libQt5Core.so.5 #24 0x7ff03370fa31 in g_main_dispatch (context=0x7ff028000ee0) at ../glib/glib/gmain.c:3460 #25 g_main_context_dispatch (context=0x7ff028000ee0) at ../glib/glib/gmain.c:4200 #26 0x7ff03376ccc9 in g_main_context_iterate.isra.0 (context=context@entry=0x7ff028000ee0, block=block@entry=1, dispatch=dispatch@entry=1, self=) at ../glib/glib/gmain.c:4276 #27 0x7ff03370d0e2 in g_main_context_iteration (context=0x7ff028000ee0, may_block=1) at ../glib/glib/gmain.c:4343 #28 0x7ff0348ea81c in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/libQt5Core.so.5 #29 0x7ff03489a714 in QEventLoop::exec(QFlags) () from /usr/lib/libQt5Core.so.5 #30 0x7ff03489bbb3 in QCoreApplication::exec() () from /usr/lib/libQt5Core.so.5 #31 0x562a382c8d4e in ?? () #32 0x7ff03403c790 in __libc_start_call_main (main=main@entry=0x562a382c8020, argc=argc@entry=1, argv=argv@entry=0x7ffc8e34b0b8) at ../sysdeps/nptl/libc_start_call_main.h:58 #33 0x7ff03403c84a in __libc_start_main_impl (main=0x562a382c8020, argc=1, argv=0x7ffc8e34b0b8, init=, fini=, rtld_fini=, stack_end=0x7ffc8e34b0a8) at ../csu/libc-start.c:360 #34 0x562a382c8e75 in ?? () [Inferior 1 (process 12153) detached] Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[kfontview] [Bug 439470] KFontView is unable to open or install a font on Wayland
https://bugs.kde.org/show_bug.cgi?id=439470 Ivan D Vasin changed: What|Removed |Added CC||i...@nisavid.io -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 471517] Whole-screen diagonal-stripes glitch on external display with hybrid graphics
https://bugs.kde.org/show_bug.cgi?id=471517 --- Comment #10 from Ivan D Vasin --- To be clear: this issue appears to be specific to KWin on Wayland. It does not occur with other Wayland compositors (at least, not with Hyprland or Mutter in their default configurations), nor with KWin on X11. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 471517] Whole-screen diagonal-stripes glitch on external display with hybrid graphics
https://bugs.kde.org/show_bug.cgi?id=471517 --- Comment #9 from Ivan D Vasin --- Created attachment 159944 --> https://bugs.kde.org/attachment.cgi?id=159944=edit edid-decode < /sys/class/drm/card1-DP-2/edid -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 471517] Whole-screen diagonal-stripes glitch on external display with hybrid graphics
https://bugs.kde.org/show_bug.cgi?id=471517 --- Comment #8 from Ivan D Vasin --- Created attachment 159943 --> https://bugs.kde.org/attachment.cgi?id=159943=edit KScreen output 2f4e4ef6ae9112f2683b157615664340 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 471517] Whole-screen diagonal-stripes glitch on external display with hybrid graphics
https://bugs.kde.org/show_bug.cgi?id=471517 --- Comment #7 from Ivan D Vasin --- Created attachment 159942 --> https://bugs.kde.org/attachment.cgi?id=159942=edit KScreen output 2627fe60f26afd08b11e318517ade0ae -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 471517] Whole-screen diagonal-stripes glitch on external display with hybrid graphics
https://bugs.kde.org/show_bug.cgi?id=471517 --- Comment #6 from Ivan D Vasin --- Created attachment 159941 --> https://bugs.kde.org/attachment.cgi?id=159941=edit kscreen.log -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 471517] Whole-screen diagonal-stripes glitch on external display with hybrid graphics
https://bugs.kde.org/show_bug.cgi?id=471517 --- Comment #5 from Ivan D Vasin --- Created attachment 159940 --> https://bugs.kde.org/attachment.cgi?id=159940=edit kwin-drm-debug.log -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 471517] Whole-screen diagonal-stripes glitch on external display with hybrid graphics
https://bugs.kde.org/show_bug.cgi?id=471517 --- Comment #4 from Ivan D Vasin --- Created attachment 159939 --> https://bugs.kde.org/attachment.cgi?id=159939=edit dmesg-drm-debug.log -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 471517] Whole-screen diagonal-stripes glitch on external display with hybrid graphics
https://bugs.kde.org/show_bug.cgi?id=471517 --- Comment #3 from Ivan D Vasin --- Created attachment 159938 --> https://bugs.kde.org/attachment.cgi?id=159938=edit KWin Support Information -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 471517] Whole-screen diagonal-stripes glitch on external display with hybrid graphics
https://bugs.kde.org/show_bug.cgi?id=471517 --- Comment #2 from Ivan D Vasin --- Created attachment 159937 --> https://bugs.kde.org/attachment.cgi?id=159937=edit kscreen-console bug -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 471517] Whole-screen diagonal-stripes glitch on external display with hybrid graphics
https://bugs.kde.org/show_bug.cgi?id=471517 --- Comment #1 from Ivan D Vasin --- Created attachment 159936 --> https://bugs.kde.org/attachment.cgi?id=159936=edit drm_info -j -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 471517] New: Whole-screen diagonal-stripes glitch on external display with hybrid graphics
https://bugs.kde.org/show_bug.cgi?id=471517 Bug ID: 471517 Summary: Whole-screen diagonal-stripes glitch on external display with hybrid graphics Classification: Plasma Product: kwin Version: 5.27.6 Platform: Archlinux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: wayland-generic Assignee: kwin-bugs-n...@kde.org Reporter: i...@nisavid.io Target Milestone: --- Created attachment 159935 --> https://bugs.kde.org/attachment.cgi?id=159935=edit photo of the distorted screen SUMMARY With the default configuration running on Wayland, the entire screen's image on my external display is distorted in a way that makes that screen totally unusable and has an appearance of diagonal stripes from the top right to the bottom left. Looking closely at the distorted image and moving the mouse cursor around on that screen, it seems that each subsequent row of pixels is effectively being shifted to the left by some number of pixels. That is to say, perhaps all of the screen's pixels are being rendered, but the rows are all so misaligned as to be incoherent. Screenshotting with Spectacle doesn't capture the distortion. A photo of the distorted screen is attached. This system has NVIDIA Optimus hybrid graphics with Intel UHD Graphics 630 as the integrated GPU (DRI card0) and NVIDIA GeForce GTX 1070 Mobile as the discrete GPU (DRI card1). The internal display is wired via Embedded DisplayPort to the iGPU; there are Mini DisplayPort and HDMI ports that are both wired to the dGPU. The internal display (which renders as expected) is an AU Optronics panel connected via eDP and has a native resolution of 3840×2160. The external display (affected by this issue) is an ASUS ROG PG348Q connected via mDP and has a native resolution of 3440×1440. The issue manifests identically under all these conditions: • the display is connected via mDP, HDMI, or an mDP-to-HDMI adapter • the display refresh rate is set to any value between 50 and 100 Hz via KScreen • the two screens are rearranged in any manner via KScreen • the scaling factor for either screen is adjusted to any value via KScreen • either screen is chosen as the primary display via KScreen • the EDID for both screens is retrieved via Windows 11 and applied during initramfs startup via the drm.edid_firmware kernel parameter The issue goes away if I set the external display's resolution to anything below 3440×1440 via KScreen. Strangely, KScreen only offers 1024×768, 800×600, and 640×480—the same resolutions as are listed by /sys/class/drm/card1-DP-2/modes—whereas in actuality the display supports many other resolutions, as one would expect, and which xrandr sees just fine. Even more oddly, KScreen offers all the expected resolutions for my internal display, even though /sys/class/drm/card0-eDP-1/modes only lists 3840×2160. Setting KWIN_DRM_DEVICES=/dev/dri/card1:/dev/dri/card0 resolves the issue completely. That is, I have to configure KWin to prioritize my dGPU (NVIDIA) first and my iGPU (Intel) second. I do this by putting the following line in /etc/environment: export KWIN_DRM_DEVICES=/dev/dri/card1:/dev/dri/card0 Doing this in ~/.config/plasma-workspace/env/kwin.sh instead also works to fix the Plasma session, but I prefer to put it in /etc/environment so that SDDM also picks it up. I've configured SDDM to run on Wayland using KWin as its compositor; in this configuration, SDDM suffers the same glitch in the absence of the above setting in /etc/environment. KWin's default behavior seems to be equivalent to KWIN_DRM_DEVICES=/dev/dri/card0:/dev/dri/card1 (iGPU first, dGPU second). Setting KWIN_DRM_DEVICES=/dev/dri/card0 causes only the internal display to be operational (correctly). Setting KWIN_DRM_DEVICES=/dev/dri/card1 causes only the external display to be operational (correctly). The issue is not reproducible using Hyprland or Mutter with their default configurations. STEPS TO REPRODUCE 1. Launch a Plasma Wayland session with the external display connected. OBSERVED RESULT The entire screen on the external display is severely distorted. The screen on the internal display is rendered correctly. EXPECTED RESULT Both screens are rendered correctly. SOFTWARE/OS VERSIONS Operating System: CachyOS Linux KDE Plasma Version: 5.27.6 KDE Frameworks Version: 5.107.0 Qt Version: 5.15.10 Kernel Version: 6.3.9-1-cachyos (64-bit) Graphics Platform: Wayland Processors: 12 × Intel® Core™ i7-8750H CPU @ 2.20GHz Memory: 31.2 GiB of RAM Graphics Processor: NVIDIA GeForce GTX 1070 with Max-Q Design/PCIe/SSE2 Manufacturer: GIGABYTE Product Name: AERO 15XV8 ADDITIONAL INFORMATION $ inxi -Gazy Graphics: Device-1: Intel CoffeeLake-H GT2 [UHD Graphics 630] vendor: Gigabyte driver: i915 v: kernel arch: Gen-9.5 process: Intel 14nm built: 2016-20 ports: active: eDP-1 empty: DP-1
[kwin] [Bug 455526] Blur glitches started to appear in wayland again
https://bugs.kde.org/show_bug.cgi?id=455526 Ivan D Vasin changed: What|Removed |Added CC||i...@nisavid.io -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 448866] [NVIDIA] Graphical glitches and unresponsive after waking from sleep
https://bugs.kde.org/show_bug.cgi?id=448866 Ivan D Vasin changed: What|Removed |Added CC||i...@nisavid.io -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 452219] Low fps and high CPU usage on external monitor connected to NVIDIA when default GPU is Intel
https://bugs.kde.org/show_bug.cgi?id=452219 Ivan D Vasin changed: What|Removed |Added CC||i...@nisavid.io -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 470411] When turning on/restarting/suspending one of the screens acquires low resolution.
https://bugs.kde.org/show_bug.cgi?id=470411 --- Comment #6 from Ivan --- (In reply to Nate Graham from comment #5) > Yes, in System Settings > Display and Monitor Hi thanks, I change the setting in System Settings > Display & Monitor but it changes randomly... so how can I change it so it doesn't change after any event (reboot, sleep etc)? Any config file that I can edit, any parameters, ...? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 470411] When turning on/restarting/suspending one of the screens acquires low resolution.
https://bugs.kde.org/show_bug.cgi?id=470411 --- Comment #4 from Ivan --- Hello everybody! Is it possible to set the resolution manually? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 470411] When turning on/restarting/suspending one of the screens acquires low resolution.
https://bugs.kde.org/show_bug.cgi?id=470411 --- Comment #3 from Ivan --- Created attachment 159337 --> https://bugs.kde.org/attachment.cgi?id=159337=edit printscreen-after-crash -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 470411] When turning on/restarting/suspending one of the screens acquires low resolution.
https://bugs.kde.org/show_bug.cgi?id=470411 --- Comment #2 from Ivan --- Created attachment 159336 --> https://bugs.kde.org/attachment.cgi?id=159336=edit K-23.04-dmesg-after-crash -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 470411] When turning on/restarting/suspending one of the screens acquires low resolution.
https://bugs.kde.org/show_bug.cgi?id=470411 --- Comment #1 from Ivan --- Created attachment 159335 --> https://bugs.kde.org/attachment.cgi?id=159335=edit K-23.04-Xorg.0.log-after-crash -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 470411] New: When turning on/restarting/suspending one of the screens acquires low resolution.
https://bugs.kde.org/show_bug.cgi?id=470411 Bug ID: 470411 Summary: When turning on/restarting/suspending one of the screens acquires low resolution. Classification: Plasma Product: kwin Version: 5.27.4 Platform: Kubuntu OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: multi-screen Assignee: kwin-bugs-n...@kde.org Reporter: gome...@hotmail.com Target Milestone: --- Created attachment 159319 --> https://bugs.kde.org/attachment.cgi?id=159319=edit low resolution on 2º screen SUMMARY When turning on/restarting/suspending one of the screens returns with low resolution (640x480). This behavior is random (it doesn't always happen). I have two HP V206hz monitors that have a maximum resolution of 1600x900x60hz and are connected to a Radeon RX 6600 via cable (displayport > DVI). Wayland does not allow resolution change (attachment). 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 Search bugs on google https://forums.gentoo.org/viewtopic-p-8782847.html?sid=709763f992be9f655473ea850ef7b784 The dmesg and xorg.0.log files https://pastebin.com/u/anarcochip/1/znbvbyhU STEPS TO REPRODUCE 1. Turn on, restart, or suspend your computer. 2. Power on, restart, or wait for the hibernation process to complete (front panel LED flashes). 3. Wait for the login screen or press any key to wake up the computer. OBSERVED RESULT One of the screens returns with a resolution of 640x480. In some moments the screen with low resolution changes the color scale to 16bits (I suppose), in these moments, sometimes the screen changes and goes black, but it remains "on" (the monitor's led does not blink). This behavior is random (doesn't always happen) and happens randomly on both monitors, sometimes the 1st sometimes the 2nd. Sometimes restarting resolves the issue. EXPECTED RESULT Both screens turn on with resolution set to 1600x900x60hz. SOFTWARE/OS VERSIONS Windows: This behavior is not observed on win11 system macOS: Not tested Linux/KDE Plasma: Kubuntu 23.04 KDE Plasma Version: 5.27.4 KDE Frameworks Version: 5.104.0 Qt Version: 5.15.8 ADDITIONAL INFORMATION I noticed that kwin related issues were not answered on Ubuntu's bugs.launchpad.net so I decided to move to Kubuntu-23.04 which wants to support multi-screem -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 470180] Screens go black after manual suspend
https://bugs.kde.org/show_bug.cgi?id=470180 Ivan changed: What|Removed |Added Status|RESOLVED|CLOSED -- You are receiving this mail because: You are watching all bug changes.
