[kwin] [Bug 455285] New: Playing TF2 (OpenGL), Closed out and it Started Flickering
https://bugs.kde.org/show_bug.cgi?id=455285 Bug ID: 455285 Summary: Playing TF2 (OpenGL), Closed out and it Started Flickering Product: kwin Version: 5.24.5 Platform: unspecified OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kwin-bugs-n...@kde.org Reporter: dominicglus...@gmail.com Target Milestone: --- Application: kwin_x11 (5.24.5) Qt Version: 5.15.4 Frameworks Version: 5.95.0 Operating System: Linux 5.18.3-zen1-1-zen x86_64 Windowing System: X11 Distribution: EndeavourOS DrKonqi: 5.24.5 [KCrashBackend] -- Information about the crash: - What I was doing when the application crashed: I just quit out of tf2 and it started flickering and i couldnt do anything The reporter is unsure if this crash is reproducible. -- Backtrace: Application: KWin (kwin_x11), signal: Segmentation fault [KCrash Handler] #4 0x7f51833ca9af in KWin::GLTexture::bind() () at /usr/lib/libkwinglutils.so.13 #5 0x7f517807aaee in KWin::LightlyShadersEffect::paintWindow(KWin::EffectWindow*, int, QRegion, KWin::WindowPaintData&) () at /usr/lib/qt/plugins/kwin/effects/plugins/kwin4_effect_lightlyshaders.so #6 0x7f5183167229 in KWin::EffectsHandlerImpl::paintWindow(KWin::EffectWindow*, int, QRegion const&, KWin::WindowPaintData&) () at /usr/lib/libkwin.so.5 #7 0x7f5183167229 in KWin::EffectsHandlerImpl::paintWindow(KWin::EffectWindow*, int, QRegion const&, KWin::WindowPaintData&) () at /usr/lib/libkwin.so.5 #8 0x7f5183167229 in KWin::EffectsHandlerImpl::paintWindow(KWin::EffectWindow*, int, QRegion const&, KWin::WindowPaintData&) () at /usr/lib/libkwin.so.5 #9 0x7f5183167229 in KWin::EffectsHandlerImpl::paintWindow(KWin::EffectWindow*, int, QRegion const&, KWin::WindowPaintData&) () at /usr/lib/libkwin.so.5 #10 0x7f51831d1820 in KWin::Scene::paintWindow(KWin::Scene::Window*, int, QRegion const&) () at /usr/lib/libkwin.so.5 #11 0x7f51831d26a6 in KWin::Scene::paintSimpleScreen(int, QRegion const&) () at /usr/lib/libkwin.so.5 #12 0x7f5183167178 in KWin::EffectsHandlerImpl::paintScreen(int, QRegion const&, KWin::ScreenPaintData&) () at /usr/lib/libkwin.so.5 #13 0x7f5183167178 in KWin::EffectsHandlerImpl::paintScreen(int, QRegion const&, KWin::ScreenPaintData&) () at /usr/lib/libkwin.so.5 #14 0x7f5183167178 in KWin::EffectsHandlerImpl::paintScreen(int, QRegion const&, KWin::ScreenPaintData&) () at /usr/lib/libkwin.so.5 #15 0x7f5183167178 in KWin::EffectsHandlerImpl::paintScreen(int, QRegion const&, KWin::ScreenPaintData&) () at /usr/lib/libkwin.so.5 #16 0x7f51831d11fd in KWin::Scene::paintScreen(QRegion const&, QRegion const&, QRegion*, QRegion*, KWin::RenderLoop*, QMatrix4x4 const&) () at /usr/lib/libkwin.so.5 #17 0x7f51832973a7 in KWin::SceneOpenGL::paint(KWin::AbstractOutput*, QRegion const&, QList const&, KWin::RenderLoop*) () at /usr/lib/libkwin.so.5 #18 0x7f5183139709 in KWin::Compositor::composite(KWin::RenderLoop*) () at /usr/lib/libkwin.so.5 #19 0x7f5183139e9f in KWin::X11Compositor::composite(KWin::RenderLoop*) () at /usr/lib/libkwin.so.5 #20 0x7f51814be251 in () at /usr/lib/libQt5Core.so.5 #21 0x7f51830f08d7 in KWin::RenderLoop::frameRequested(KWin::RenderLoop*) () at /usr/lib/libkwin.so.5 #22 0x7f51831c25b8 in KWin::RenderLoopPrivate::dispatch() () at /usr/lib/libkwin.so.5 #23 0x7f51814be251 in () at /usr/lib/libQt5Core.so.5 #24 0x7f51814c060f in QTimer::timeout(QTimer::QPrivateSignal) () at /usr/lib/libQt5Core.so.5 #25 0x7f51814b13d6 in QObject::event(QEvent*) () at /usr/lib/libQt5Core.so.5 #26 0x7f5180b78a7c in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /usr/lib/libQt5Widgets.so.5 #27 0x7f518148db28 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /usr/lib/libQt5Core.so.5 #28 0x7f51814d7ac3 in QTimerInfoList::activateTimers() () at /usr/lib/libQt5Core.so.5 #29 0x7f51814d7f72 in QEventDispatcherUNIX::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #30 0x7f517b6eff43 in () at /usr/lib/libQt5XcbQpa.so.5 #31 0x7f51814862ec in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #32 0x7f5181490dd9 in QCoreApplication::exec() () at /usr/lib/libQt5Core.so.5 #33 0x5651a95aadd5 in () #34 0x7f5180229290 in () at /usr/lib/libc.so.6 #35 0x7f518022934a in __libc_start_main () at /usr/lib/libc.so.6 #36 0x5651a95ac1a5 in () [Inferior 1 (process 880) detached] Possible duplicates by query: bug 453626, bug 452482, bug 451022, bug 449702, bug 445375. Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 455299] New: Switching to Hybrid mode on an Optimus Laptop Won't Start the Session
https://bugs.kde.org/show_bug.cgi?id=455299 Bug ID: 455299 Summary: Switching to Hybrid mode on an Optimus Laptop Won't Start the Session Product: plasmashell Version: master Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: generic-crash Assignee: plasma-b...@kde.org Reporter: dominicglus...@gmail.com Target Milestone: 1.0 SUMMARY *** NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** STEPS TO REPRODUCE 1. Install and setup optimus switch (done via endeavour os' guide) 2. Run the command optimus-manager --switch hybrid or through system tray icon 3. Logout and be unable to log back in with a error message saying session can't start OBSERVED RESULT Something with the nvidia card and integrated card being both used screws with the new plasma 5.25 update. EXPECTED RESULT With the previous versions I've been able to switch back and forth just fine, get logged out and log right back in. SOFTWARE/OS VERSIONS Windows: N/A macOS: N/A Linux/KDE Plasma: 5.18.3-zen1-1-zen (Kernal?) (available in About System) KDE Plasma Version: 5.25.5 KDE Frameworks Version: 5.95 Qt Version: 5.15.4 ADDITIONAL INFORMATION Running on X11, I hope this is the right place to report the bug. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 455299] Switching to Hybrid mode on an Optimus Laptop Won't Start the Session
https://bugs.kde.org/show_bug.cgi?id=455299 --- Comment #2 from Dominic --- (In reply to Nate Graham from comment #1) > Can you upgrade to 5.25 and see if it still happens? I'm currently on 5.25.5 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 455299] Switching to Hybrid mode on an Optimus Laptop Won't Start the Session
https://bugs.kde.org/show_bug.cgi?id=455299 --- Comment #3 from Dominic --- Created attachment 149763 --> https://bugs.kde.org/attachment.cgi?id=149763&action=edit Image1 of Crash -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 455299] Switching to Hybrid mode on an Optimus Laptop Won't Start the Session
https://bugs.kde.org/show_bug.cgi?id=455299 --- Comment #4 from Dominic --- Created attachment 149764 --> https://bugs.kde.org/attachment.cgi?id=149764&action=edit Image2 of Crash -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 455299] Switching to Hybrid mode on an Optimus Laptop Won't Start the Session
https://bugs.kde.org/show_bug.cgi?id=455299 --- Comment #6 from Dominic --- (In reply to Nate Graham from comment #5) > 5.25.5 doesn't exist. You're either on 5.24.5, or 5.24.90 (the 5.25 beta) or > 5.25.0, or 5.25.80 (i.e. current git master). > > Which one is it exactly? Sorry mistype 5.25.0 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 455299] Switching to Hybrid mode on an Optimus Laptop Won't Start the Session
https://bugs.kde.org/show_bug.cgi?id=455299 --- Comment #7 from Dominic --- (In reply to Dominic from comment #0) > SUMMARY > *** > NOTE: If you are reporting a crash, please try to attach a backtrace with > debug symbols. > See > https://community.kde.org/Guidelines_and_HOWTOs/Debugging/ > How_to_create_useful_crash_reports Since I have to reboot after it crashes by going ctrl alt f2 then rebooting I can't get a backtrace sense I don't get a crash handler. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 467666] New: reshade-shaders-git picked up as a false update in discover but won't update.
https://bugs.kde.org/show_bug.cgi?id=467666 Bug ID: 467666 Summary: reshade-shaders-git picked up as a false update in discover but won't update. Classification: Applications Product: Discover Version: unspecified Platform: Archlinux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: discover Assignee: plasma-b...@kde.org Reporter: dominicglus...@gmail.com CC: aleix...@kde.org Target Milestone: --- Created attachment 157502 --> https://bugs.kde.org/attachment.cgi?id=157502&action=edit Had to copy and paste the output, tee refuses to work for me. Very strange bug specifically with reshade-shaders-git from both aur and chaotic aur. Discover will pick up an update for it (which there isn't one), but gives the output attached when running plasma-discover-update. It's only this package, which is what makes it strange. Removing it will make the update notification go away. SOFTWARE/OS VERSIONS Linux/KDE Plasma: 6.27-zen1-1zen (64-bit) (available in About System) KDE Plasma Version: 5.27.3 KDE Frameworks Version: 5.104.0 Qt Version: 5.18.8 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[frameworks-knewstuff] [Bug 467952] New: Annoying Loading Screen and Various API Errors
https://bugs.kde.org/show_bug.cgi?id=467952 Bug ID: 467952 Summary: Annoying Loading Screen and Various API Errors Classification: Frameworks and Libraries Product: frameworks-knewstuff Version: 5.104.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: ad...@leinir.dk Reporter: dominicglus...@gmail.com CC: alexander.loh...@gmx.de, kdelibs-b...@kde.org Target Milestone: --- Created attachment 157711 --> https://bugs.kde.org/attachment.cgi?id=157711&action=edit Bug in effect knewstuff Seems to have a lot of network errors. Scrolling too fast will make this super long loading screen appear that isn't in the Ubuntu releases of KDE Plasma I've attached a simple recording of both bugs. Not sure where logs are stored but it happens without fail everytime I scroll through a "Get New Stuff" dialog. Another one I'll get is: Unknown Open Collaboration Service API error. (0) kde SOFTWARE/OS VERSIONS Linux/KDE Plasma: EndeavourOS (Arch) KDE Plasma Version: 5.27.3 KDE Frameworks Version: 5.104.0 Qt Version: 5.15.8 ADDITIONAL INFORMATION I have plasma-meta and kde-applications-meta installed since I use all of your apps as my default apps. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 467666] reshade-shaders-git picked up as a false update in discover but won't update.
https://bugs.kde.org/show_bug.cgi?id=467666 --- Comment #2 from Dominic --- (In reply to Aleix Pol from comment #1) > This is a known problem in ArchLinux's PackageKit backend: > https://github.com/PackageKit/PackageKit/issues/533 Thanks for the clarification, happy to see it's already been reported -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 468217] xf86-input-libinput 1.3.0 DPI and mouse acceleration issue on KDE Plasma X11
https://bugs.kde.org/show_bug.cgi?id=468217 Dominic changed: What|Removed |Added CC||dominicglus...@gmail.com --- Comment #3 from Dominic --- Having same issue here, issue is present on X11, but not on wayland. Tested on both Logitech and Razer mice, same issue of a dramatic increase in sensitivity. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 469363] New: Systemsettings Crash When Changing GTK Theme
https://bugs.kde.org/show_bug.cgi?id=469363 Bug ID: 469363 Summary: Systemsettings Crash When Changing GTK Theme Classification: Applications Product: systemsettings Version: 5.27.3 Platform: openSUSE OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: dominicglus...@gmail.com Target Milestone: --- Application: systemsettings (5.27.3) Qt Version: 5.15.9 Frameworks Version: 5.105.0 Operating System: Linux 6.3.1-1-default x86_64 Windowing System: X11 Distribution: "openSUSE Tumbleweed" DrKonqi: 5.27.4 [KCrashBackend] -- Information about the crash: Recent update with opensuse, including various gtk packages versioned 3.24.37+70 openSUSE Tumbleweed release 2023503 and gtk3-branding-openSUSE 15. Most likely due to the new gtk versions The crash can be reproduced every time. -- Backtrace: Application: System Settings (systemsettings), signal: Segmentation fault [KCrash Handler] #4 0x7fb29e78dfcb in () #5 0x7fb25c049448 in g_closure_invoke () at /lib64/libgobject-2.0.so.0 #6 0x7fb25c05c4fe in () at /lib64/libgobject-2.0.so.0 #7 0x7fb25c06382e in g_signal_emit_valist () at /lib64/libgobject-2.0.so.0 #8 0x7fb25c0639df in g_signal_emit () at /lib64/libgobject-2.0.so.0 #9 0x7fb25c04d6c4 in () at /lib64/libgobject-2.0.so.0 #10 0x7fb25c04e018 in () at /lib64/libgobject-2.0.so.0 #11 0x7fb25c051ec6 in g_object_set_valist () at /lib64/libgobject-2.0.so.0 #12 0x7fb25c052aa3 in g_object_set () at /lib64/libgobject-2.0.so.0 #13 0x7fb2a405d3df in () at /usr/lib64/gtk-2.0/modules/libappmenu-gtk-module.so #14 0x7fb2a405d4ac in () at /usr/lib64/gtk-2.0/modules/libappmenu-gtk-module.so #15 0x7fb2a405b78b in gtk_module_init () at /usr/lib64/gtk-2.0/modules/libappmenu-gtk-module.so #16 0x7fb24d951cd2 in () at /lib64/libgtk-x11-2.0.so.0 #17 0x7fb24d9a6678 in () at /lib64/libgtk-x11-2.0.so.0 #18 0x7fb25c049448 in g_closure_invoke () at /lib64/libgobject-2.0.so.0 #19 0x7fb25c05c615 in () at /lib64/libgobject-2.0.so.0 #20 0x7fb25c06382e in g_signal_emit_valist () at /lib64/libgobject-2.0.so.0 #21 0x7fb25c0639df in g_signal_emit () at /lib64/libgobject-2.0.so.0 #22 0x7fb25c04d6c4 in () at /lib64/libgobject-2.0.so.0 #23 0x7fb25c05060e in g_object_notify () at /lib64/libgobject-2.0.so.0 #24 0x7fb24d9a375f in () at /lib64/libgtk-x11-2.0.so.0 #25 0x7fb24d985418 in () at /lib64/libgtk-x11-2.0.so.0 #26 0x7fb24d98623d in () at /lib64/libgtk-x11-2.0.so.0 #27 0x7fb24d9863fe in () at /lib64/libgtk-x11-2.0.so.0 #28 0x7fb24d987377 in gtk_rc_reparse_all_for_settings () at /lib64/libgtk-x11-2.0.so.0 #29 0x7fb24d98751e in () at /lib64/libgtk-x11-2.0.so.0 #30 0x7fb25c049448 in g_closure_invoke () at /lib64/libgobject-2.0.so.0 #31 0x7fb25c05c4fe in () at /lib64/libgobject-2.0.so.0 #32 0x7fb25c06382e in g_signal_emit_valist () at /lib64/libgobject-2.0.so.0 #33 0x7fb25c0639df in g_signal_emit () at /lib64/libgobject-2.0.so.0 #34 0x7fb25c04d6c4 in () at /lib64/libgobject-2.0.so.0 #35 0x7fb25c05060e in g_object_notify () at /lib64/libgobject-2.0.so.0 #36 0x7fb24f3a61de in () at /lib64/libgdk-x11-2.0.so.0 #37 0x7fb2d6a698d8 in g_main_context_dispatch () at /lib64/libglib-2.0.so.0 #38 0x7fb2d6a69ce8 in () at /lib64/libglib-2.0.so.0 #39 0x7fb2d6a69d7c in g_main_context_iteration () at /lib64/libglib-2.0.so.0 #40 0x7fb2d8145f26 in QEventDispatcherGlib::processEvents(QFlags) () at /lib64/libQt5Core.so.5 #41 0x7fb2a7545670 in runRdb(unsigned int) () at /lib64/libkrdb.so #42 0x7fb29ed21388 in () at /usr/lib64/qt5/plugins/plasma/kcms/systemsettings/kcm_style.so #43 0x7fb2d8bcb3e2 in () at /lib64/libKF5KCMUtils.so.5 #44 0x7fb2d8bd3397 in KCModuleProxy::save() () at /lib64/libKF5KCMUtils.so.5 #45 0x7fb2d9ae8881 in ModuleView::moduleSave(KCModuleProxy*) () at /lib64/libsystemsettingsview.so.3 #46 0x7fb2d9aed0ee in () at /lib64/libsystemsettingsview.so.3 #47 0x7fb2d81251d3 in () at /lib64/libQt5Core.so.5 #48 0x7fb2d8e969c2 in QAbstractButton::clicked(bool) () at /lib64/libQt5Widgets.so.5 #49 0x7fb2d8e96c2a in () at /lib64/libQt5Widgets.so.5 #50 0x7fb2d8e98467 in () at /lib64/libQt5Widgets.so.5 #51 0x7fb2d8e98677 in QAbstractButton::mouseReleaseEvent(QMouseEvent*) () at /lib64/libQt5Widgets.so.5 #52 0x7fb2d8de6d78 in QWidget::event(QEvent*) () at /lib64/libQt5Widgets.so.5 #53 0x7fb2d8da51ae in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /lib64/libQt5Widgets.so.5 #54 0x7fb2d8dad5df in QApplication::notify(QObject*, QEvent*) () at /lib64/libQt5Widgets.so.5 #55 0x7fb2d80ec978 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /lib64/libQt5Core.so.5 #56 0x7fb2d8dab93e in QAp
[kwin] [Bug 460181] New: Overview won't work with a game in windowed borderless, if compositing is turned off automatically, and mouse will be stuck in fullscreen application
https://bugs.kde.org/show_bug.cgi?id=460181 Bug ID: 460181 Summary: Overview won't work with a game in windowed borderless, if compositing is turned off automatically, and mouse will be stuck in fullscreen application Classification: Plasma Product: kwin Version: master Platform: Archlinux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: effects-overview Assignee: kwin-bugs-n...@kde.org Reporter: dominicglus...@gmail.com Target Milestone: --- SUMMARY *** There's no crash but just nothing will happen which is a bit frustruating, I've tested this with Payday 2 (proton) and Hoi4 (native). STEPS TO REPRODUCE 1. Launch hoi4 in borderless borderless with overview turned on and auto turn off compositing on 2. Attempt to use super+w to activate overview, for nothing to happen 3. Launch Payday 2 and repeat step 2, overview will activate, your mouse will appear in overview UNTIL you move it which then it will be forced back into the game window where you can still move the camera around Expected Result: A overview similar to gnome or a more interactive alt tab. SOFTWARE/OS VERSIONS Linux/KDE Plasma: EndeavourOS (available in About System) KDE Plasma Version: 5.25.5 KDE Frameworks Version: 5.98.0 Qt Version: 5.15.6 Kernal Version: 5.19.13-zen1-1-zen (64-bit) Graphics Platform: X11 If you need anymore info I'll happily share -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 460181] Overview won't work with a game in windowed borderless, if compositing is turned off automatically, and mouse will be stuck in fullscreen application
https://bugs.kde.org/show_bug.cgi?id=460181 --- Comment #2 from Dominic --- (In reply to Nate Graham from comment #1) > > if compositing is turned off automatically > Yep, that's how it works. The overview effect is implement as a desktop > effect that uses compositing, and so if compositing is turned off, you can't > use it. > > Two options: > 1. Don't let apps turn off compositing (System Settings > Display and > Monitor > Compositor > some setting in there) > 2. Use the Wayland session where compositing can't be turned off So why does it only affect certain games? Even with gamemode on? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 482813] Two-finger tap doesn't work on icons only task manager
https://bugs.kde.org/show_bug.cgi?id=482813 Dominic changed: What|Removed |Added CC||dom.fin...@gmail.com --- Comment #3 from Dominic --- Also experiencing this, was just about to open another issue but caught this one first. SUMMARY Two finger tapping on icons within the task menu panel does not do anything and doesn't mimic the same behavior if you were right-clicking with a physical mouse. STEPS TO REPRODUCE 1. Ensure "Tap-to-click" and "Press anywhere with two fingers" is enabled within Touch-pad settings 2. Have an Icons-only task menu with at least one icon for an application. 3. Attempt to two-finger tap to open a context menu for the icon, observe behavior does not occur as expected. OBSERVED RESULT Two finger tapping on an icon within the Icons-only task menu panel acts as neither a click to open the selected window, nor does a context menu appear. EXPECTED RESULT As a user, I should be able to two finger tap with a laptop touch-pad on icons within the Icons-only task menu panel to show the context-menu for that application. ADDITIONAL INFORMATION OS: Arch Linux x86_64 Host: ROG Zephyrus G14 GA402RJ 1.0 Kernel: 6.7.9-arch1-1 Shell: bash 5.2.26 Resolution: 2560x1600 DE: Plasma 6.0.1 WM: kwin WM Theme: Kanagawa Theme: [Plasma], Kanagawa-B [GTK2/3] Icons: [Plasma], breeze-dark [GTK2/3] CPU: AMD Ryzen 9 6900HS with Radeon Graphics (16) @ 4.935GHz GPU: AMD ATI Radeon 680M -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 473712] Plasmashell crashing on wayland when opening Yakuake
https://bugs.kde.org/show_bug.cgi?id=473712 Dominic changed: What|Removed |Added Resolution|--- |FIXED Status|REPORTED|RESOLVED -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 479269] Dark GTK apps show mis-colored icons when using Breeze icon theme
https://bugs.kde.org/show_bug.cgi?id=479269 Dominic changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 481192] New: Systemsettings crashes when going into various kcm modules
https://bugs.kde.org/show_bug.cgi?id=481192 Bug ID: 481192 Summary: Systemsettings crashes when going into various kcm modules Classification: Applications Product: systemsettings Version: master Platform: openSUSE OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: generic-crash Assignee: plasma-b...@kde.org Reporter: dominicglus...@gmail.com Target Milestone: --- SUMMARY *** Various kcm modules cause systemsettings to crash, from navigating to it in the gui or running systemsettings kcm_foobar, here's a list of the one's I can confirm are broken. It always gives an error about Cyclic dependency, and the kcrash always says crashRecursionCounter=2 kcm_aboutdistro 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" KCrash: Application 'systemsettings' crashing... crashRecursionCounter = 2 [1]5731 segmentation fault (core dumped) systemsettings kcm_about-distro kcm_colors 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" KCrash: Application 'systemsettings' crashing... crashRecursionCounter = 2 [1]6862 segmentation fault (core dumped) systemsettings kcm_colors (It's the same for the rest) kcm_cursortheme kcm_pulseaudio kcm_style kcm_fonts There might be more that I accidently clicked over, if anyone can confirm more please list them. NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** STEPS TO REPRODUCE 1. Add the kde unstable repos to openSUSE Tumbleweed 2. Update via sudo zypper dup --force-resolution ; sudo zypper install plasma6-session ; sudo zypper inr ; reboot 3. Open systemsettings either from the application launcher or running systemsettings kcm_foobar (replace with the broken kcm module) OBSERVED RESULT Crashes on various modules EXPECTED RESULT Not to crash SOFTWARE/OS VERSIONS Linux/KDE Plasma: openSUSE Tumbleweed 20240208 (available in About System) KDE Plasma: 6.0.80 KDE Frameworks: 5.116.0 Qt: 5.15.12 Kernel: 6.7.4-1-default ADDITIONAL INFORMATION I'm new to bug reporting, please let me know how I can provide more info. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 481192] Systemsettings crashes when going into various kcm modules
https://bugs.kde.org/show_bug.cgi?id=481192 Dominic changed: What|Removed |Added CC||dominicglus...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 479269] Breeze-Dark Icon Theme not using Dark Icons
https://bugs.kde.org/show_bug.cgi?id=479269 --- Comment #12 from Dominic --- (In reply to Nate Graham from comment #10) > Thanks. Can you reproduce the issue in any non-GTK apps? Sorry for the late reply, I need to turn on email notifications No it seems to be exclusive to gtk -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 481192] Systemsettings crashes when going into various kcm modules
https://bugs.kde.org/show_bug.cgi?id=481192 --- Comment #2 from Dominic --- (In reply to fanzhuyifan from comment #1) > Can't reproduce on Arch source build of git master. Perhaps this is a > packaging issue? Thanks for testing, it might a packaging issue, where do I go to report it? -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 481192] Systemsettings crashes when going into various kcm modules
https://bugs.kde.org/show_bug.cgi?id=481192 --- Comment #7 from Dominic --- (In reply to Nate Graham from comment #3) > To the Arch people. But if you do want to continue here, we need a backtrace > of the crash. See > https://community.kde.org/Guidelines_and_HOWTOs/Debugging/ > How_to_create_useful_crash_reports#Retrieving_a_backtrace_using_coredumpctl Here's my log output, took me a bit to figure out. This is from systemettings kcm_fonts PID: 2949 (systemsettings) UID: 1000 (domglusk) GID: 1000 (domglusk) Signal: 11 (SEGV) Timestamp: Thu 2024-02-15 19:39:02 CST (30s ago) Command Line: systemsettings kcm_fonts Executable: /usr/bin/systemsettings Control Group: /user.slice/user-1000.slice/user@1000.service/app.slice/app-kitty-6efeb581ef414879926b3601e4b3d066.scope Unit: user@1000.service User Unit: app-kitty-6efeb581ef414879926b3601e4b3d066.scope Slice: user-1000.slice Owner UID: 1000 (domglusk) Boot ID: e526f7750dc84b1ea2840fe904ded9b4 Machine ID: ee1179f562664432962f643dd602eb39 Hostname: dominic-ge75raider10sf Storage: /var/lib/systemd/coredump/core.systemsettings.1000.e526f7750dc84b1ea2840fe904ded9b4.2949.170804754200.zst (present) Size on Disk: 7.1M Message: Process 2949 (systemsettings) of user 1000 dumped core. Stack trace of thread 2964: #0 0x7eff344949ec __pthread_kill_implementation (libc.so.6 + 0x949ec) #1 0x7eff34441176 raise (libc.so.6 + 0x41176) #2 0x7eff379b7b93 _ZN6KCrash19defaultCrashHandlerEi (libKF6Crash.so.6 + 0x6b93) #3 0x7eff34441240 __restore_rt (libc.so.6 + 0x41240) #4 0x7eff3615cee7 n/a (libQt6Qml.so.6 + 0x35cee7) #5 0x7eff3615d297 n/a (libQt6Qml.so.6 + 0x35d297) #6 0x7eff3615d297 n/a (libQt6Qml.so.6 + 0x35d297) #7 0x7eff3615d297 n/a (libQt6Qml.so.6 + 0x35d297) #8 0x7eff3615d297 n/a (libQt6Qml.so.6 + 0x35d297) #9 0x7eff361535ef n/a (libQt6Qml.so.6 + 0x3535ef) #10 0x7eff361638f0 n/a (libQt6Qml.so.6 + 0x3638f0) #11 0x7eff360a8f3b _ZN12QQmlDataBlob7tryDoneEv (libQt6Qml.so.6 + 0x2a8f3b) #12 0x7eff36171410 _ZN14QQmlTypeLoader7setDataERK14QQmlRefPointerI12QQmlDataBlobERKNS1_14SourceCodeDataE (libQt6Qml.so.6 + 0x371410) #13 0x7eff36171c1a _ZN14QQmlTypeLoader7setDataERK14QQmlRefPointerI12QQmlDataBlobERK7QString (libQt6Qml.so.6 + 0x371c1a) #14 0x7eff36175655 _ZN14QQmlTypeLoader10loadThreadERK14QQmlRefPointerI12QQmlDataBlobE (libQt6Qml.so.6 + 0x375655) #15 0x7eff361796c5 n/a (libQt6Qml.so.6 + 0x3796c5) #16 0x7eff36079054 n/a (libQt6Qml.so.6 + 0x279054) #17 0x7eff36dc094e _ZN19QApplicationPrivate13notify_helperEP7QObjectP6QEvent (libQt6Widgets.so.6 + 0x1c094e) #18 0x7eff34d87268 _ZN16QCoreApplication15notifyInternal2EP7QObjectP6QEvent (libQt6Core.so.6 + 0x187268) #19 0x7eff34d875c7 _ZN23QCoreApplicationPrivate16sendPostedEventsEP7QObjectiP11QThreadData (libQt6Core.so.6 + 0x1875c7) #20 0x7eff34fa5d83 n/a (libQt6Core.so.6 + 0x3a5d83) #21 0x7eff3424af30 n/a (libglib-2.0.so.0 + 0x5bf30) #22 0x7eff3424cb58 n/a (libglib-2.0.so.0 + 0x5db58) #23 0x7eff3424d20c g_main_context_iteration (libglib-2.0.so.0 + 0x5e20c) #24 0x7eff34fab12c _ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE (libQt6Core.so.6 + 0x3ab12c) #25 0x7eff34d91adb _ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE (libQt6Core.so.6 + 0x191adb) #26 0x7eff34e66024 _ZN7QThread4execEv (libQt6Core.so.6 + 0x266024) #27 0x7eff34ee4d49 n/a (libQt6Core.so.6 + 0x2e4d49) #28 0x7eff34492bb2 start_thread (libc.so.6 + 0x92bb2) #29 0x7eff3451400c __clone3 (libc.so.6 + 0x11400c) Stack trace of thread 2949: #0 0x7eff3448effe __futex_abstimed_wait_common (libc.so.6 + 0x8effe) #1 0x7eff34491d40 pthread_cond_wait@@GLIBC_2.3.2 (libc.so.6 + 0x91d40) #2 0x7eff34ee2deb _ZN14QWaitCondition4waitEP6QMutex14QDeadlineTimer (libQt6Core.so.6 + 0x2e2deb) #3 0x7eff3607804b n/a (libQt6Qml.so.6 + 0x27804b) #4 0x7eff3617596a _ZN14QQmlTypeLoader4loadEP12QQmlDataBlobNS_4ModeE (libQt6Qml.so.6 + 0x37596a) #5 0x7eff3617f63f _ZN14QQmlTypeLoader7getTypeERK4QUrlNS_4ModeE (libQt6Qml.so.6 + 0x37f63f) #6 0x7eff3609c52f _ZN20QQmlComponentPrivate7loadUrlERK4QUrlN13QQmlComponent15CompilationModeE (libQt6Qml.so.6 + 0x29c52f)
[systemsettings] [Bug 481192] Systemsettings crashes when going into various kcm modules
https://bugs.kde.org/show_bug.cgi?id=481192 --- Comment #8 from Dominic --- I know it's insecure and a bad practice but I ran kdesu systemsettings and was able to enter the modules that are broken. Could it be a plasmoid or colorscheme is causing things to break? -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 481192] Systemsettings crashes when going into various kcm modules
https://bugs.kde.org/show_bug.cgi?id=481192 --- Comment #11 from Dominic --- (In reply to fanzhuyifan from comment #10) > For the original reporter -- which Qt version are you using? Is this also > fixed for you on Qt 6.6.2? Yes it is, I haven't had any crashes on any of the modules, it's resolved for me, is anyone else still getting crashes? (qt version is 6.6.2) -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 481192] Systemsettings crashes when going into various kcm modules
https://bugs.kde.org/show_bug.cgi?id=481192 Dominic changed: What|Removed |Added Resolution|BACKTRACE |FIXED Status|NEEDSINFO |RESOLVED --- Comment #15 from Dominic --- (In reply to Nate Graham from comment #13) > Can you please get a backtrace from that stack trace? See > https://community.kde.org/Guidelines_and_HOWTOs/Debugging/ > How_to_create_useful_crash_reports#Retrieving_a_backtrace_using_coredumpctl? Seems to have been fixed. Marking as complete -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 481192] Systemsettings crashes when going into various kcm modules
https://bugs.kde.org/show_bug.cgi?id=481192 Dominic changed: What|Removed |Added Ever confirmed|0 |1 Resolution|WORKSFORME |--- Status|RESOLVED|REOPENED --- Comment #12 from Dominic --- Now getting a crash when opening kcm_kscreen Not sure if this is new or not, but I turned my monitor's adaptive refresh rate off, and now the module is crashing when opening, turning it back on doesn't resolve the issue. Here's the core dump PID: 10047 (systemsettings) UID: 1000 (domglusk) GID: 1000 (domglusk) Signal: 11 (SEGV) Timestamp: Wed 2024-03-13 16:26:42 CDT (2min 19s ago) Command Line: systemsettings kcm_kscreen Executable: /usr/bin/systemsettings Control Group: /user.slice/user-1000.slice/user@1000.service/app.slice/app-kitty-8751b70390f2415da43ffda07b65e446.scope Unit: user@1000.service User Unit: app-kitty-8751b70390f2415da43ffda07b65e446.scope Slice: user-1000.slice Owner UID: 1000 (domglusk) Boot ID: a537d2c799f245458e45bd894be816f2 Machine ID: ee1179f562664432962f643dd602eb39 Hostname: dominic-ge75raider10sf Storage: /var/lib/systemd/coredump/core.systemsettings.1000.a537d2c799f245458e45bd894be816f2.10047.171036520200.zst (present) Size on Disk: 6.0M Message: Process 10047 (systemsettings) of user 1000 dumped core. Stack trace of thread 10063: #0 0x7ff4ec0949ec __pthread_kill_implementation (libc.so.6 + 0x949ec) #1 0x7ff4ec041176 raise (libc.so.6 + 0x41176) #2 0x7ff4ef6beb93 _ZN6KCrash19defaultCrashHandlerEi (libKF6Crash.so.6 + 0x6b93) #3 0x7ff4ec041240 __restore_rt (libc.so.6 + 0x41240) #4 0x7ff4edd5fe47 n/a (libQt6Qml.so.6 + 0x35fe47) #5 0x7ff4edd601f1 n/a (libQt6Qml.so.6 + 0x3601f1) #6 0x7ff4edd571df n/a (libQt6Qml.so.6 + 0x3571df) #7 0x7ff4edd648d0 n/a (libQt6Qml.so.6 + 0x3648d0) #8 0x7ff4edca961e _ZN12QQmlDataBlob7tryDoneEv (libQt6Qml.so.6 + 0x2a961e) #9 0x7ff4edd73cc0 _ZN14QQmlTypeLoader7setDataERK14QQmlRefPointerI12QQmlDataBlobERKNS1_14SourceCodeDataE (libQt6Qml.so.6 + 0x373cc0) #10 0x7ff4edd74b4a _ZN14QQmlTypeLoader7setDataERK14QQmlRefPointerI12QQmlDataBlobERK7QString (libQt6Qml.so.6 + 0x374b4a) #11 0x7ff4edd76cb5 _ZN14QQmlTypeLoader10loadThreadERK14QQmlRefPointerI12QQmlDataBlobE (libQt6Qml.so.6 + 0x376cb5) #12 0x7ff4edd76eff _ZN14QQmlTypeLoader4loadEP12QQmlDataBlobNS_4ModeE (libQt6Qml.so.6 + 0x376eff) #13 0x7ff4edd775ff _ZN14QQmlTypeLoader7getTypeERK4QUrlNS_4ModeE (libQt6Qml.so.6 + 0x3775ff) #14 0x7ff4edd70105 n/a (libQt6Qml.so.6 + 0x370105) #15 0x7ff4edd73e1b _ZN14QQmlTypeLoader7setDataERK14QQmlRefPointerI12QQmlDataBlobERKNS1_14SourceCodeDataE (libQt6Qml.so.6 + 0x373e1b) #16 0x7ff4edd74b4a _ZN14QQmlTypeLoader7setDataERK14QQmlRefPointerI12QQmlDataBlobERK7QString (libQt6Qml.so.6 + 0x374b4a) #17 0x7ff4edd76cb5 _ZN14QQmlTypeLoader10loadThreadERK14QQmlRefPointerI12QQmlDataBlobE (libQt6Qml.so.6 + 0x376cb5) #18 0x7ff4edd76eff _ZN14QQmlTypeLoader4loadEP12QQmlDataBlobNS_4ModeE (libQt6Qml.so.6 + 0x376eff) #19 0x7ff4edd775ff _ZN14QQmlTypeLoader7getTypeERK4QUrlNS_4ModeE (libQt6Qml.so.6 + 0x3775ff) #20 0x7ff4edd70105 n/a (libQt6Qml.so.6 + 0x370105) #21 0x7ff4edd73e1b _ZN14QQmlTypeLoader7setDataERK14QQmlRefPointerI12QQmlDataBlobERKNS1_14SourceCodeDataE (libQt6Qml.so.6 + 0x373e1b) #22 0x7ff4edd74b4a _ZN14QQmlTypeLoader7setDataERK14QQmlRefPointerI12QQmlDataBlobERK7QString (libQt6Qml.so.6 + 0x374b4a) #23 0x7ff4edd76cb5 _ZN14QQmlTypeLoader10loadThreadERK14QQmlRefPointerI12QQmlDataBlobE (libQt6Qml.so.6 + 0x376cb5) #24 0x7ff4edd7c875 n/a (libQt6Qml.so.6 + 0x37c875) #25 0x7ff4edc788d4 n/a (libQt6Qml.so.6 + 0x2788d4) #26 0x7ff4ee9c1aae _ZN19QApplicationPrivate13notify_helperEP7QObjectP6QEvent (libQt6Widgets.so.6 + 0x1c1aae) #27 0x7ff4ec987498 _ZN16QCoreApplication15notifyInternal2EP7QObjectP6QEvent (libQt6Core.so.6 + 0x187498) #28 0x7ff4ec9877f7 _ZN23QCoreApplicationPrivate16sendPostedEventsEP7QObjectiP11QThreadData (libQt6Core.so.6 + 0x1877f7) #29 0x7ff4ecba6783 n/a (libQt6Core.so.6 + 0x3a6783) #30 0x7ff4ebf13f30 n/a (libglib-2.0.so.0 + 0x5bf30) #31 0x7ff4ebf15b58 n/a (libglib-2.0.so.0 + 0x5db58) #32 0x0
[lattedock] [Bug 453007] New: Editing Latte Dock crashes the whole dock
https://bugs.kde.org/show_bug.cgi?id=453007 Bug ID: 453007 Summary: Editing Latte Dock crashes the whole dock Product: lattedock Version: unspecified Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: application Assignee: mvourla...@gmail.com Reporter: dominicglus...@gmail.com Target Milestone: --- SUMMARY *** NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** STEPS TO REPRODUCE 1. Download Apus Latte Style (Or any style) 2. Right click a dock with latte-tasks on it 3. Hit Edit Dock OBSERVED RESULT Latte will crash 75% of the time, and the 25% of the time you get into the edit menu, add widgets or try to install new indicators crashes the whole dock EXPECTED RESULT Able to freely edit and add new widgets and new indicators SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: 5.17.4-zen1-1 zen, Endeavour OS (available in About System) KDE Plasma Version: 5.24.4 KDE Frameworks Version: 5.93.0 Qt Version: Not entirely sure ADDITIONAL INFORMATION N/A -- You are receiving this mail because: You are watching all bug changes.
[frameworks-plasma] [Bug 453010] New: Kvantum is trying to work around "qqc2-desktop-style" which doesn't respect Kvantum styles
https://bugs.kde.org/show_bug.cgi?id=453010 Bug ID: 453010 Summary: Kvantum is trying to work around "qqc2-desktop-style" which doesn't respect Kvantum styles Product: frameworks-plasma Version: unspecified Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: major Priority: NOR Component: libplasma Assignee: plasma-b...@kde.org Reporter: dominicglus...@gmail.com CC: m...@ratijas.tk, notm...@gmail.com Target Milestone: --- Created attachment 148361 --> https://bugs.kde.org/attachment.cgi?id=148361&action=edit A really obvious example with Dracula Kvantum. SUMMARY *** NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** STEPS TO REPRODUCE 1. Download Kvantum and pick ANY KDE global suite 2. Apply the application style Kvantum 3. Look at the settings for an immediate result of the bug OBSERVED RESULT An inconsistent transparency and button cropping in most KDE apps. EXPECTED RESULT A consistent customized experience SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: Arch - Endeavor OS (available in About System) KDE Plasma Version: 5.24.4 KDE Frameworks Version: 5.93.0 Qt Version: 5.15.3 ADDITIONAL INFORMATION I'm reporting this bug on behalf of every single theme creator that uses the amazing kvantum application style which adds much-needed fundamental customization and alternative to Breeze. I'm quoting both sources from the creator of Kvantum and further backed up by the Lightly creators on Github. -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 453007] Editing Latte Dock crashes the whole dock
https://bugs.kde.org/show_bug.cgi?id=453007 --- Comment #2 from Dominic --- (In reply to Michail Vourlakos from comment #1) > What is the crash report? Normally it would give me an option to report it but this time it didn't -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 455649] Latte Dock crashes when closing Steam
https://bugs.kde.org/show_bug.cgi?id=455649 --- Comment #1 from Dominic --- Created attachment 149985 --> https://bugs.kde.org/attachment.cgi?id=149985&action=edit New crash information added by DrKonqi latte-dock (0.10.77) using Qt 5.15.5 Latte dock crashes every once in awhile after performing a regular reboot -- Backtrace (Reduced): #4 0x7f72ca58a1d4 in QSGTexture::setFiltering(QSGTexture::Filtering) () at /usr/lib/libQt5Quick.so.5 #5 0x7f72ca5b9ef0 in QSGOpaqueTextureMaterialShader::updateState(QSGMaterialShader::RenderState const&, QSGMaterial*, QSGMaterial*) () at /usr/lib/libQt5Quick.so.5 #6 0x7f72ca5a2ffe in QSGBatchRenderer::Renderer::renderMergedBatch(QSGBatchRenderer::Batch const*) () at /usr/lib/libQt5Quick.so.5 #7 0x7f72ca5a69c6 in QSGBatchRenderer::Renderer::renderBatches() () at /usr/lib/libQt5Quick.so.5 #8 0x7f72ca5ab211 in QSGBatchRenderer::Renderer::render() () at /usr/lib/libQt5Quick.so.5 -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 455649] Latte Dock crashes when closing Steam
https://bugs.kde.org/show_bug.cgi?id=455649 Dominic changed: What|Removed |Added CC||dominicglus...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 455649] latte crashes when closing steam from systray
https://bugs.kde.org/show_bug.cgi?id=455649 --- Comment #11 from Dominic --- Created attachment 150590 --> https://bugs.kde.org/attachment.cgi?id=150590&action=edit New crash information added by DrKonqi latte-dock (0.10.77) using Qt 5.15.5 Everytime you use the "Add a Widget" button it crashes after opening up the kde store -- Backtrace (Reduced): #4 0x7f8068f8a1d4 in QSGTexture::setFiltering(QSGTexture::Filtering) () at /usr/lib/libQt5Quick.so.5 #5 0x7f8068fb9ef0 in QSGOpaqueTextureMaterialShader::updateState(QSGMaterialShader::RenderState const&, QSGMaterial*, QSGMaterial*) () at /usr/lib/libQt5Quick.so.5 #6 0x7f8068fa2ffe in QSGBatchRenderer::Renderer::renderMergedBatch(QSGBatchRenderer::Batch const*) () at /usr/lib/libQt5Quick.so.5 #7 0x7f8068fa69c6 in QSGBatchRenderer::Renderer::renderBatches() () at /usr/lib/libQt5Quick.so.5 #8 0x7f8068fab211 in QSGBatchRenderer::Renderer::render() () at /usr/lib/libQt5Quick.so.5 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 427380] Crashes when running face detection
https://bugs.kde.org/show_bug.cgi?id=427380 --- Comment #3 from Dominic --- Just as an update. The beta build is crashing far less often than 7.1.0. I was getting a crash every 5-15 minutes I would say. The 7.2.0 beta has only crash twice in the last 3 or 4 hours. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 427380] Crashes when running face detection
https://bugs.kde.org/show_bug.cgi?id=427380 --- Comment #5 from Dominic --- Memory wasn't bad (the images are mostly 2-10MB). I watched it intermittently and it never went over about 1.2Gb of RAM (the machine has at least 6Gb free with this running so there's no pressure). -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 427380] Crashes when running face detection
https://bugs.kde.org/show_bug.cgi?id=427380 --- Comment #8 from Dominic --- Yup, still crashes, but in a different way. I get a standard windows Application Error dialog appearing (I'll attach a screenshot). I'll also run again to see if it fails in the previous way sometimes. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 427380] Crashes when running face detection
https://bugs.kde.org/show_bug.cgi?id=427380 --- Comment #9 from Dominic --- Created attachment 132209 --> https://bugs.kde.org/attachment.cgi?id=132209&action=edit Screenshot of Application Error -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 427380] Crashes when running face detection
https://bugs.kde.org/show_bug.cgi?id=427380 --- Comment #10 from Dominic --- It's still crashing in the other way as well. Windows just vanished with no error dialog or anything like that appearing. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 427380] Crashes when running face detection
https://bugs.kde.org/show_bug.cgi?id=427380 --- Comment #11 from Dominic --- Sorry, disregard that last comment (2020-10-08 13:36:41 UTC). I don't know that to true just now - my mistake. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 427380] Crashes when running face detection
https://bugs.kde.org/show_bug.cgi?id=427380 --- Comment #12 from Dominic --- OK. I can confirm it's still crashing by totally vanishing. In the windows event log I found this: Log Name: Application Source:Application Error Date: 08/10/2020 14:43:58 Event ID: 1000 Task Category: (100) Level: Error Keywords: Classic User: N/A Computer: badger Description: Faulting application name: digikam.exe, version: 0.0.0.0, time stamp: 0x Faulting module name: libexiv2.dll, version: 0.0.0.0, time stamp: 0x Exception code: 0xc005 Fault offset: 0x00029db9 Faulting process ID: 0x1aa8 Faulting application start time: 0x01d69d77fb8bd15e Faulting application path: C:\Program Files\digiKam\digikam.exe Faulting module path: C:\Program Files\digiKam\libexiv2.dll Report ID: d359cd6f-0f37-42d3-ba01-b08e39d5d9e6 Faulting package full name: Faulting package-relative application ID: Event Xml: http://schemas.microsoft.com/win/2004/08/events/event";> 1000 0 2 100 0 0x80 10857 Application badger digikam.exe 0.0.0.0 libexiv2.dll 0.0.0.0 c005 00029db9 1aa8 01d69d77fb8bd15e C:\Program Files\digiKam\digikam.exe C:\Program Files\digiKam\libexiv2.dll d359cd6f-0f37-42d3-ba01-b08e39d5d9e6 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 427380] Crashes when running face detection
https://bugs.kde.org/show_bug.cgi?id=427380 --- Comment #13 from Dominic --- It feels like random. This time the crash is in a different library. Log Name: Application Source:Application Error Date: 08/10/2020 15:14:28 Event ID: 1000 Task Category: (100) Level: Error Keywords: Classic User: N/A Computer: badger Description: Faulting application name: digikam.exe, version: 0.0.0.0, time stamp: 0x Faulting module name: Qt5Core.dll, version: 5.15.1.0, time stamp: 0x Exception code: 0xc005 Fault offset: 0x0001b30d Faulting process ID: 0x2a4c Faulting application start time: 0x01d69d7b0ba4fbc2 Faulting application path: C:\Program Files\digiKam\digikam.exe Faulting module path: C:\Program Files\digiKam\Qt5Core.dll Report ID: 9369758b-b70c-4002-a197-ce2160eed74d Faulting package full name: Faulting package-relative application ID: Event Xml: http://schemas.microsoft.com/win/2004/08/events/event";> 1000 0 2 100 0 0x80 10942 Application badger digikam.exe 0.0.0.0 Qt5Core.dll 5.15.1.0 c005 0001b30d 2a4c 01d69d7b0ba4fbc2 C:\Program Files\digiKam\digikam.exe C:\Program Files\digiKam\Qt5Core.dll 9369758b-b70c-4002-a197-ce2160eed74d -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 427380] Crashes when running face detection
https://bugs.kde.org/show_bug.cgi?id=427380 --- Comment #15 from Dominic --- I don't have a crash dump there but I do have some useful sounding files in AppData/Local/CrashDumps... Attaching one of those - hopefully helpful. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 427380] Crashes when running face detection
https://bugs.kde.org/show_bug.cgi?id=427380 --- Comment #16 from Dominic --- Ah, nope. Those dumps are 50Mb (12Mb zipped) so can't attach them. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 427380] Crashes when running face detection
https://bugs.kde.org/show_bug.cgi?id=427380 --- Comment #17 from Dominic --- Is there some setting required to trigger the creation of the crash log files? -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 427380] Crashes when running face detection
https://bugs.kde.org/show_bug.cgi?id=427380 --- Comment #20 from Dominic --- No, nothing special at all in my photo collection, and I suspect that whatever is making it crash, it subsequently gets past somehow as it's gradually making progress. When I first reported this it had scanned about 20% of my collection and now it's at 80%. I looked at a few of the debug logs when it was first happening and it was not the case that the same images kept cropping up. It was different ones each time it crashed as far as I could tell. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 479238] New: Independent System Tray and Icon Themes
https://bugs.kde.org/show_bug.cgi?id=479238 Bug ID: 479238 Summary: Independent System Tray and Icon Themes Classification: Plasma Product: plasmashell Version: master Platform: openSUSE OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: System Tray Assignee: plasma-b...@kde.org Reporter: dominicglus...@gmail.com CC: mate...@gmail.com Target Milestone: 1.0 Please add the ability to use a separate icon theme for the status icons, while using another theme for everything else, for example, I like using the Papirus Icon Theme, but it's system tray icons aren't or haven't been properly implemented (for example Bluetooth icon is the Bluetooth network folder, and battery icon doesn't show percentage left), but I really like Breeze's system tray icons. Having a way to use separate system tray icons would help with icon themes that don't apply and allow for more customization. SOFTWARE/OS VERSIONS Linux/KDE Plasma: openSUSE Tumbleweed 20231226 KDE Plasma Version: 5.91.90 KDE Frameworks Version: 5.248.0 Qt Version: 6.6.1 ADDITIONAL INFORMATION Running on Wayland, and using KDE Unstable repo's for openSUSE Tumbleweed -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 479269] New: Breeze-Dark Icon Theme not using Dark Icons
https://bugs.kde.org/show_bug.cgi?id=479269 Bug ID: 479269 Summary: Breeze-Dark Icon Theme not using Dark Icons Classification: Plasma Product: Breeze Version: master Platform: openSUSE OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Icons Assignee: visual-des...@kde.org Reporter: dominicglus...@gmail.com CC: kain...@gmail.com, m...@nueljl.in Target Milestone: --- Created attachment 164601 --> https://bugs.kde.org/attachment.cgi?id=164601&action=edit Conky-Manager2 SUMMARY Various apps are using a light icon instead of the dark colorscheme, see screenshots attached NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** STEPS TO REPRODUCE 1. Open nwg-look 2. Switch from your current icon theme to Breeze-Dark 3. Dark on dark icons are shown EXPECTED RESULT Using contrasting icons for dark themes SOFTWARE/OS VERSIONS Linux/KDE Plasma: openSUSE Tumbleweed 20231226 x86_64 (available in About System) KDE Plasma Version: 5.91.90 KDE Frameworks Version: 5.248.0 Qt Version: 6.6.1 ADDITIONAL INFORMATION Wayland -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 479269] Breeze-Dark Icon Theme not using Dark Icons
https://bugs.kde.org/show_bug.cgi?id=479269 --- Comment #1 from Dominic --- Created attachment 164602 --> https://bugs.kde.org/attachment.cgi?id=164602&action=edit GTK File Picker -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 479269] Breeze-Dark Icon Theme not using Dark Icons
https://bugs.kde.org/show_bug.cgi?id=479269 --- Comment #2 from Dominic --- Created attachment 164603 --> https://bugs.kde.org/attachment.cgi?id=164603&action=edit nwg-look -- You are receiving this mail because: You are watching all bug changes.
[plasma-integration] [Bug 477902] Breeze themed cursor changes to a generic one when hovering over Qt5 apps, and also some other apps.
https://bugs.kde.org/show_bug.cgi?id=477902 Dominic changed: What|Removed |Added CC||dominicglus...@gmail.com --- Comment #6 from Dominic --- Created attachment 164781 --> https://bugs.kde.org/attachment.cgi?id=164781&action=edit Wezterm example I also get this bug, here's an example with Wezterm. I also get it with kitty -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 479818] New: Incorrect bold font rendering
https://bugs.kde.org/show_bug.cgi?id=479818 Bug ID: 479818 Summary: Incorrect bold font rendering Classification: Applications Product: konsole Version: master Platform: openSUSE OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: font Assignee: konsole-de...@kde.org Reporter: dominicglus...@gmail.com Target Milestone: --- Created attachment 164905 --> https://bugs.kde.org/attachment.cgi?id=164905&action=edit Incorrect bold font rendering SUMMARY *** Both Yakuake and Konsole render bold text incorrectly, STEPS TO REPRODUCE 1. Use FiraCode Nerd Font 10pt as the font 2. In ZSH with fast-syntax-highlighting enabled, type using a bold error color, type in ddd and then dd to see the comparison of incorrect bold rendering OBSERVED RESULT Bold seems to be raised compared to standard EXPECTED RESULT On the same line SOFTWARE/OS VERSIONS Linux/KDE: openSUSE Tumbleweed 20240112 (available in About System) KDE Plasma Version: 6.0.80 KDE Frameworks Version: Version: 5.249.0 Qt Version: 6.6.1 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 479828] New: Very low framerate in Neovim w/ LazyVim
https://bugs.kde.org/show_bug.cgi?id=479828 Bug ID: 479828 Summary: Very low framerate in Neovim w/ LazyVim Classification: Applications Product: konsole Version: master Platform: openSUSE OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: emulation Assignee: konsole-de...@kde.org Reporter: dominicglus...@gmail.com Target Milestone: --- SUMMARY *** The framerate in konsole when scrolling with an animation when using lazyvim (https://www.lazyvim.org/) which uses mini-animate for animations *** STEPS TO REPRODUCE 1. Install konsole 2. Install LazyVim from the website provided 3. Enable mini-animate in LazyExtras 4. Use shift + up and shift + down to see the low animation framerate OBSERVED RESULT Very low framerate EXPECTED RESULT Same framerate as Kitty, which is set to match my refresh rate. SOFTWARE/OS VERSIONS : Linux/KDE Plasma: openSUSE Tumbleweed 20240112 KDE Plasma Version: 6.0.80 KDE Frameworks Version: 5.249.0 Qt Version: 6.6.1 ADDITIONAL INFORMATION Recorded using gpu-screen-recorder at 144hz, converted using ffmpeg from a mp4 to a webm, and trimmed using Video Trimmer from flathub -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 479828] Very low framerate in Neovim w/ LazyVim
https://bugs.kde.org/show_bug.cgi?id=479828 --- Comment #1 from Dominic --- Created attachment 164910 --> https://bugs.kde.org/attachment.cgi?id=164910&action=edit Kitty vs Konsole in animation framerate -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 479828] Very low framerate in Neovim w/ LazyVim
https://bugs.kde.org/show_bug.cgi?id=479828 --- Comment #2 from Dominic --- Had to record new video for example, didn't use Video Trimmer, just ffmpeg to compress and convert -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 479269] Breeze-Dark Icon Theme not using Dark Icons
https://bugs.kde.org/show_bug.cgi?id=479269 --- Comment #4 from Dominic --- (In reply to Nate Graham from comment #3) > Can you paste the output of running `grep "Theme=" ~/.config/kdeglobals` in > a terminal window? Theme=Papirus-Dark -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 479269] Breeze-Dark Icon Theme not using Dark Icons
https://bugs.kde.org/show_bug.cgi?id=479269 --- Comment #5 from Dominic --- (In reply to Dominic from comment #4) > (In reply to Nate Graham from comment #3) > > Can you paste the output of running `grep "Theme=" ~/.config/kdeglobals` in > > a terminal window? > > Theme=Papirus-Dark This is what I'm using in the meantime, here's the output when using breeze dark Theme=breeze-dark -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 479269] Breeze-Dark Icon Theme not using Dark Icons
https://bugs.kde.org/show_bug.cgi?id=479269 --- Comment #9 from Dominic --- (In reply to Nate Graham from comment #6) > So to be clear, the issue happens when using the Breeze Dark icon theme, but > NOT when using the Papirus icon theme? Yes it's exclusive to Breeze Dark -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 477640] New: File Selector (?) Rendering Wrong in a Few Apps
https://bugs.kde.org/show_bug.cgi?id=477640 Bug ID: 477640 Summary: File Selector (?) Rendering Wrong in a Few Apps Classification: I don't know Product: kde Version: unspecified Platform: openSUSE OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: dominicglus...@gmail.com Target Milestone: --- Created attachment 163553 --> https://bugs.kde.org/attachment.cgi?id=163553&action=edit Preview of the screen tearing SUMMARY *** NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** I've noticed this rendering error in some GTK apps but can't pin down the exact cause. I know its consistently an error in Firefox STEPS TO REPRODUCE 1. Start Plasma in Wayland 2. Open Firefox and go to any website that asks for a file upload, for example the kde bug report site 3. Tearing and broken file list making it unable to select something OBSERVED RESULT You can use arrow keys and the file preview to figure out what your selecting but that's the only workaround I've found EXPECTED RESULT Consistent file picker between all apps SOFTWARE/OS VERSIONS Linux/KDE Plasma: 6.6.2-1-default (available in About System) KDE Plasma Version: 5.27.9 KDE Frameworks Version: 5.112.0 Qt Version: 5.15.11 ADDITIONAL INFORMATION Hybrid Nvidia/Intel gpu laptop. I've tested on a amdgpu, and iris intel gpu with the same result -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 473712] New: Plasmashell crashing on wayland when opening Yakuake
https://bugs.kde.org/show_bug.cgi?id=473712 Bug ID: 473712 Summary: Plasmashell crashing on wayland when opening Yakuake Classification: Plasma Product: plasmashell Version: 5.27.7 Platform: openSUSE OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: dominicglus...@gmail.com CC: k...@davidedmundson.co.uk Target Milestone: 1.0 Application: plasmashell (5.27.7) Qt Version: 5.15.10 Frameworks Version: 5.109.0 Operating System: Linux 6.4.11-1-default x86_64 Windowing System: Wayland Distribution: "openSUSE Tumbleweed" DrKonqi: 5.27.7 [CoredumpBackend] -- Information about the crash: No idea what is causing it, no special settings or anything, but it's 9/10 times. The crash can be reproduced every time. -- Backtrace (Reduced): #4 0x7f3321c8cf04 in QtQml::qmlAttachedPropertiesObject(QObject*, QObject* (*)(QObject*), bool) () at /lib64/libQt5Qml.so.5 [...] #8 0x7f3320309701 in QWaitCondition::wakeOne() () at /lib64/libQt5Core.so.5 #9 0x7f3321f26a3a in QtWaylandClient::QWaylandDisplay::flushRequests() () at /lib64/libQt5WaylandClient.so.5 #10 0x7f3320519320 in QObject::event(QEvent*) () at /lib64/libQt5Core.so.5 #11 0x7f33213a519e in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /lib64/libQt5Widgets.so.5 Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 473712] Plasmashell crashing on wayland when opening Yakuake
https://bugs.kde.org/show_bug.cgi?id=473712 --- Comment #1 from Dominic --- Created attachment 161151 --> https://bugs.kde.org/attachment.cgi?id=161151&action=edit New crash information added by DrKonqi DrKonqi auto-attaching complete backtrace. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 474243] Plasma crashes every once and awhile on notification dropdown
https://bugs.kde.org/show_bug.cgi?id=474243 --- Comment #1 from Dominic --- Created attachment 161458 --> https://bugs.kde.org/attachment.cgi?id=161458&action=edit New crash information added by DrKonqi DrKonqi auto-attaching complete backtrace. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 474243] New: Plasma crashes every once and awhile on notification dropdown
https://bugs.kde.org/show_bug.cgi?id=474243 Bug ID: 474243 Summary: Plasma crashes every once and awhile on notification dropdown Classification: Plasma Product: plasmashell Version: 5.27.7 Platform: openSUSE OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: dominicglus...@gmail.com CC: k...@davidedmundson.co.uk Target Milestone: 1.0 Application: plasmashell (5.27.7) Qt Version: 5.15.10 Frameworks Version: 5.109.0 Operating System: Linux 6.4.12-1-default x86_64 Windowing System: X11 Distribution: "openSUSE Tumbleweed" DrKonqi: 5.27.7 [CoredumpBackend] -- Information about the crash: I have no idea what the consistency is, but I hope the backtrace helps The crash can be reproduced sometimes. -- Backtrace (Reduced): #3 0x7f2d10409b18 in Kirigami::PlatformTheme::backgroundColor() const () at /lib64/libKF5Kirigami2.so.5 [...] #7 0x7f2d12098322 in _iris_batch_flush(iris_batch*, char const*, int) (batch=0x564c2b4d2930, file=, line=) at ../src/gallium/drivers/iris/iris_batch.c:896 #8 0x7f2d12d1e3c7 in iris_fence_flush(pipe_context*, pipe_fence_handle**, unsigned int) (ctx=0x564c2b4d23f0, out_fence=0x0, flags=0) at ../src/gallium/drivers/iris/iris_fence.c:266 #9 0x7f2d125edb7b in tc_flush(pipe_context*, pipe_fence_handle**, unsigned int) (_pipe=0x564c2b4e1ab0, fence=0x0, flags=0) at ../src/gallium/auxiliary/util/u_threaded_context.c:3540 #10 0x7f2d122ab5d4 in st_flush (flags=0, fence=0x0, st=0x564c2b432000) at ../src/mesa/state_tracker/st_cb_flush.c:63 Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[kmix] [Bug 463505] New: Unable to Raise Maximum Volume Within System Tray Widget
https://bugs.kde.org/show_bug.cgi?id=463505 Bug ID: 463505 Summary: Unable to Raise Maximum Volume Within System Tray Widget Classification: Applications Product: kmix Version: unspecified Platform: Archlinux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: KMix Panel Docking Assignee: es...@kde.org Reporter: dominicglus...@gmail.com Target Milestone: --- Created attachment 154836 --> https://bugs.kde.org/attachment.cgi?id=154836&action=edit Issue Summary: When opening the volume icon and checking raise maximum volume the slider doesn't go above 100%, so I've had to use pavucontrol which is inconvenient SOFTWARE/OS VERSIONS Linux/KDE Plasma: EndeavourOS (available in About System) KDE Plasma Version: 5.26.4 KDE Frameworks Version: 5.101.0 Qt Version: 5.15.7 ADDITIONAL INFORMATION Not using -git version, just regular repo release. -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 464166] New: Night color doesn't start when logging in, but its reported as on, you need to turn it off and on again via applet.
https://bugs.kde.org/show_bug.cgi?id=464166 Bug ID: 464166 Summary: Night color doesn't start when logging in, but its reported as on, you need to turn it off and on again via applet. Classification: I don't know Product: kde Version: unspecified Platform: Archlinux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: dominicglus...@gmail.com Target Milestone: --- Whenever I restart my computer or logout and login, night color (blue light filter) isn't on. I have it set as always on at 3,000k. To reproduce - Turn on night color mode - Restart computer or end session The temporary fix is to turn it off and on again via the applet SOFTWARE/OS VERSIONS Linux/KDE Plasma: EndeavourOS (available in About System) KDE Plasma Version: 5.26.5 KDE Frameworks Version: 5.101.0 Qt Version: 5.15.8 Graphics Platform: X11 Graphics Proccessor: Nvidia (nvidia-dkms driver) -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 500837] Wayland Night Color Mode causes Color Issues (notably on dark areas)
https://bugs.kde.org/show_bug.cgi?id=500837 Dominic changed: What|Removed |Added Version|6.3.1 |6.3.2 --- Comment #1 from Dominic --- Tested on 6.3.2 the visual bug is still there. The issue still is present on both prefer efficiency and prefer color accuracy settings. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 500837] Wayland Night Color Mode causes Color Issues (notably on dark areas)
https://bugs.kde.org/show_bug.cgi?id=500837 --- Comment #3 from Dominic --- (In reply to Geno from comment #2) > I'm on an Arch Linux based system running KDE Plasma 6 in X11. > > Since the kwin update to 6.3.2.1-1, Night Light has a stark green/purple hue > instead of red/orange. Sounds like a different issue, mine is exclusive to wayland -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 500837] New: Wayland Night Color Mode causes Color Issues (notably on dark areas)
https://bugs.kde.org/show_bug.cgi?id=500837 Bug ID: 500837 Summary: Wayland Night Color Mode causes Color Issues (notably on dark areas) Classification: Plasma Product: kwin Version: 6.3.1 Platform: Other OS: Linux Status: REPORTED Severity: major Priority: NOR Component: night color Assignee: kwin-bugs-n...@kde.org Reporter: dominicglus...@gmail.com Target Milestone: --- SUMMARY Colors in games are noticeably worse, the best example is in Deadlock, going to one of the corners and turning night light off and on shows a very noticeable drop in quality, (it looks similar to how photos taken in the dark have that weird shading to it). Another example is the skill tree in Path of Exile. What's also weird, and I'm not sure if it's related, but moving the mouse back from my laptop monitor to my secondary monitor seems to dim my laptop screen, almost like I have the dim inactive windows effect on. Before the 6.3 update this wasn't an issue. The more extreme of a temperature (3000K>) the issues become more noticeable This issue is exclusively on Wayland, on X11 it works just fine and none of the mentioned bugs are present. I can't share a screenshot because it doesn't capture night light. STEPS TO REPRODUCE 1. Log into a Plasma Wayland 2. Open something with a dark image 3. Turn on Night Light and notice the difference in quality 4. Move mouse back and forth from monitor to show the dimming effect SOFTWARE/OS VERSIONS Operating System: openSUSE Tumbleweed 20250222 KDE Plasma Version: 6.3.1 KDE Frameworks Version: 6.11.0 Qt Version: 6.8.2 Kernel Version: 6.13.3-1-default (64-bit) Processors: 12 × Intel® Core™ i7-10750H CPU @ 2.60GHz Memory: 15.4 GiB of RAM Graphics Processor 1: Intel® UHD Graphics Graphics Processor 2: NVIDIA GeForce RTX 2070 Manufacturer: Micro-Star International Co., Ltd. Product Name: GE75 Raider 10SF System Version: REV:1.0 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 500837] Wayland Night Color Mode causes Color Issues (notably on dark areas)
https://bugs.kde.org/show_bug.cgi?id=500837 --- Comment #9 from Dominic --- Created attachment 179080 --> https://bugs.kde.org/attachment.cgi?id=179080&action=edit The output of drm_info -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 500837] Wayland Night Color Mode causes Color Issues (notably on dark areas)
https://bugs.kde.org/show_bug.cgi?id=500837 Dominic changed: What|Removed |Added Platform|Other |openSUSE -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 500837] Wayland Night Color Mode causes Color Issues (notably on dark areas)
https://bugs.kde.org/show_bug.cgi?id=500837 --- Comment #16 from Dominic --- (In reply to Zamundaaa from comment #15) > OP is using Intel to drive the screen. The degamma lut is already disabled > for NVidia for unrelated reasons. Correct, I have a optimus system, laptop screen runs off of intel card, external monitor (via display port) runs on nvidia. What was changed in the update to have caused night light to suddenly ruin colors on screens? I'll have to wait for the patch to be pushed to OpenSUSE Tumbleweed repos before I can say for sure it's fixed for me -- You are receiving this mail because: You are watching all bug changes.
[kstars] [Bug 433186] opening "whats intresting"
https://bugs.kde.org/show_bug.cgi?id=433186 Dominic bundy changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |FIXED --- Comment #3 from Dominic bundy --- checked seams stable, could replicate on 3.5.5 -- You are receiving this mail because: You are watching all bug changes.
[kstars] [Bug 433186] opening "whats intresting"
https://bugs.kde.org/show_bug.cgi?id=433186 --- Comment #4 from Dominic bundy --- (In reply to Dominic bundy from comment #3) > checked seams stable, could replicate on 3.5.5 couldn't replicate that should have said !! -- You are receiving this mail because: You are watching all bug changes.
[kstars] [Bug 433186] New: opening "whats intresting"
https://bugs.kde.org/show_bug.cgi?id=433186 Bug ID: 433186 Summary: opening "whats intresting" Product: kstars Version: unspecified Platform: Ubuntu Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: mutla...@ikarustech.com Reporter: d...@bundy.co.uk Target Milestone: --- Application: kstars (3.5.1 Stable) Qt Version: 5.12.8 Frameworks Version: 5.68.0 Operating System: Linux 5.4.0-65-generic x86_64 Windowing system: X11 Distribution: Ubuntu 20.04.2 LTS -- Information about the crash: - What I was doing when the application crashed: I opened whats intresting and the whole application crashed The crash can be reproduced sometimes. -- Backtrace: Application: KStars (kstars), signal: Aborted Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f0e3778bac0 (LWP 132247))] Thread 7 (Thread 0x7f0e2305b700 (LWP 132290)): #0 __libc_read (nbytes=16, buf=0x7f0e2305a8b0, fd=9) at ../sysdeps/unix/sysv/linux/read.c:26 #1 __libc_read (fd=9, buf=0x7f0e2305a8b0, nbytes=16) at ../sysdeps/unix/sysv/linux/read.c:24 #2 0x7f0e3b98389f in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f0e3b93acde in g_main_context_check () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7f0e3b93b132 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7f0e3b93b2c3 in g_main_context_iteration () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #6 0x7f0e3cc41583 in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7f0e3cbe84db in QEventLoop::exec(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7f0e3ca20785 in QThread::exec() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #9 0x7f0e3eee01a9 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5 #10 0x7f0e3ca219d2 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #11 0x7f0e3db3d609 in start_thread (arg=) at pthread_create.c:477 #12 0x7f0e3bf71293 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 6 (Thread 0x7f0e2285a700 (LWP 132273)): #0 0x7f0e3bf64aff in __GI___poll (fds=0x7f0e0400fa80, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7f0e3b93b18e in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f0e3b93b513 in g_main_loop_run () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f0e2c611eda in ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 #4 0x7f0e3b964911 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7f0e3db3d609 in start_thread (arg=) at pthread_create.c:477 #6 0x7f0e3bf71293 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 5 (Thread 0x7f0e21858700 (LWP 132271)): #0 0x7f0e3bf64aff in __GI___poll (fds=0x563a360a0750, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7f0e3b93b18e in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f0e3b93b2c3 in g_main_context_iteration () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f0e3b93b311 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7f0e3b964911 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7f0e3db3d609 in start_thread (arg=) at pthread_create.c:477 #6 0x7f0e3bf71293 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 4 (Thread 0x7f0e0bfff700 (LWP 132268)): #0 0x7f0e3bf64aff in __GI___poll (fds=0x7f0df40025e0, nfds=1, timeout=1852) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7f0e3b93b18e in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f0e3b93b2c3 in g_main_context_iteration () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f0e3cc41583 in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7f0e3cbe84db in QEventLoop::exec(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f0e3ca20785 in QThread::exec() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7f0e3ca219d2 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7f0e3db3d609 in start_thread (arg=) at pthread_create.c:477 #8 0x7f0e3bf71293 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 3 (Thread 0x7f0e35f4b700 (LWP 132249)): #0 __libc_read (nbytes=16, buf=0x7f0e35f4a8a0, fd=6) at ../sysdeps/unix/sysv/linux/read.c:26 #1 __libc_read (fd=6, buf=0x7f0e35f4a8a0, nbytes=16) at ../sysdeps/unix/sysv/linux/read.c:24 #2 0x7f0e3b98389f in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f0e3b93acde in g_main_context_check () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7f0e3b93b132 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7f0e3b93b2c3 in g_main
[kate] [Bug 447384] New: Session restore only restores 'windows'/'tabs' viewspace state for a maximum of one stashed document (that is not yet saved), despite many others being present on session save
https://bugs.kde.org/show_bug.cgi?id=447384
Bug ID: 447384
Summary: Session restore only restores 'windows'/'tabs'
viewspace state for a maximum of one stashed document
(that is not yet saved), despite many others being
present on session save
Product: kate
Version: 21.12.0
Platform: Microsoft Windows
OS: Microsoft Windows
Status: REPORTED
Severity: normal
Priority: NOR
Component: application
Assignee: kwrite-bugs-n...@kde.org
Reporter: dominic.pal...@outlook.com
Target Milestone: ---
SUMMARY
For context, I have been looking into Kate as a personal replacement for
Notepad++. There has long been scope for another editor to challenge
Notepad++'s functionality whereby:
1. Untitled/unsaved/anonymous files can be created freely and populated with
text as normal.
2. On closing Notepad++, any untitled files with non-empty text content are
written to disk in a temp folder, and the session state (including window and
tab placement of the untitled files) is stored.
3. On reopening Notepad++, any untitled files are popped from disk and the
window/tab/session state is fully recovered.
Much of this functionality is now present in Kate through sessions and stashes.
A 'God' session can be created, such that provided no other sessions are
created, Kate will always reopen and restore it at startup ('always open most
recent session').
List item 1 above is also possible through Kate - unsaved files can be added to
a session at will.
List item 2 is implemented - the addition of KateStashManager means that
unsaved documents are now pushed to a stash on close (via
KateStashManager::stashDocuments in katestashmanager.cpp, lines 42-72, provided
the text content is non-empty) and popped on restore.
The issue is that on session restore, the window/tab state of _at most one_
unsaved document that was stashed is restored. This means that a user could
have a session with 5 untitled/unsaved documents open, all populated with text,
and close Kate. On reopening, just one of those untitled sessions will have a
window/tab reopened for it, despite all untitled sessions being visible in the
documents toolbar. This means that the document content IS being correctly
popped on restore and reflected in the documents tree, but either:
1. Window/tab/viewspace state for untitled documents is not saved in config,
and hence can't be restored OR
2. Window/tab/viewspace state for untitled documents is saved, but not restored
on startup
A potentially unrelated but similar issue is that the state of the document
tree is not restored either, for both untitled and titled (i.e., previously
saved files w/ a checksum). The document tree toolbar only expands the
directory of any file in the active window. The state of the tree on session
close or the last session save is ignored. This leads me to wonder whether more
data in general needs to be written to .katesession on save.
STEPS TO REPRODUCE
1. Start a new Kate session. Open 1 file that is already stored on disk for
reference. Add 2 new untitled/unsaved files to the session.
2. In the untitled files, add some random text content. This will force Kate to
stash the document on session close/save.
3. Configure Kate to save the session on close, and reopen the most recent
session on startup.
4. Have the active window open on the file already stored on disk, but make
sure that both untitled files have tabs open regardless.
5. Close Kate.
6. Reopen.
OBSERVED RESULT
The window state will be restored such that the file stored on disk has a tab,
yet just ONE of the 2 untitled files will have a tab. All 3 files will be
present in the document tree toolbar despite this.
EXPECTED RESULT
The exact window state at the point of session save should have been stashed
and restored on startup. This means that all 3 files (1 on disk, 2 untitled)
should have tabs already open. The state of the document tree should also be
preserved, and shouldn't only expand directories for the file currently in the
active window.
SOFTWARE/OS VERSIONS
Windows: Windows 10 Pro 21H1 19043.1415
macOS: N/A
Linux/KDE Plasma: N/A
(available in About System)
KDE Plasma Version: N/A
KDE Frameworks Version: N/A
Qt Version: N/A
ADDITIONAL INFORMATION
To fully capture users who use Notepad++ for persistence of temporary unsaved
files, it may also be worth looking into enforcing the right click -> Open with
Kate menu to open the file with the last used session. At the moment, Kate will
create a new anonymous session when using this menu (if Kate isn't already
open), regardless of whether it's configured to open the most recent session.
--
You are receiving this mail because:
You are watching all bug changes.
[kstars] [Bug 429660] New: kstars crash when starting job from schedualer
https://bugs.kde.org/show_bug.cgi?id=429660 Bug ID: 429660 Summary: kstars crash when starting job from schedualer Product: kstars Version: unspecified Platform: Ubuntu Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: mutla...@ikarustech.com Reporter: d...@bundy.co.uk Target Milestone: --- Application: kstars (3.5.0 Stable) Qt Version: 5.12.8 Frameworks Version: 5.68.0 Operating System: Linux 5.4.0-54-generic x86_64 Windowing system: X11 Distribution: Ubuntu 20.04.1 LTS -- Information about the crash: - What I was doing when the application crashed: started job from shedular, then as automation ran it crashed The crash can be reproduced every time. -- Backtrace: Application: KStars (kstars), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f5b17db1ac0 (LWP 1633))] Thread 15 (Thread 0x7f5ae32ae700 (LWP 1932)): #0 __libc_read (nbytes=16, buf=0x7f5ae32ad8b0, fd=50) at ../sysdeps/unix/sysv/linux/read.c:26 #1 __libc_read (fd=50, buf=0x7f5ae32ad8b0, nbytes=16) at ../sysdeps/unix/sysv/linux/read.c:24 #2 0x7f5b1bfa989f in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f5b1bf60cfe in g_main_context_check () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7f5b1bf61152 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7f5b1bf612e3 in g_main_context_iteration () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #6 0x7f5b1d267583 in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7f5b1d20e4db in QEventLoop::exec(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7f5b1d046785 in QThread::exec() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #9 0x7f5b1f5061a9 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5 #10 0x7f5b1d0479d2 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #11 0x7f5b1e163609 in start_thread (arg=) at pthread_create.c:477 #12 0x7f5b1c597293 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 14 (Thread 0x7f5ae17fd700 (LWP 1913)): #0 syscall () at ../sysdeps/unix/sysv/linux/x86_64/syscall.S:38 #1 0x7f5b1d049dd1 in QSemaphore::acquire(int) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #2 0x7f5b1d23b77d in QMetaObject::activate(QObject*, int, int, void**) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #3 0x5604bbc89536 in ClientManager::newINDIDevice (this=this@entry=0x5604c28884f0, _t1=, _t1@entry=0x7f5ac00784f0) at ./obj-x86_64-linux-gnu/kstars/KStarsLib_autogen/FRI4DANIHA/moc_clientmanager.cpp:333 #4 0x5604bbd03b7f in ClientManager::newDevice (this=0x5604c28884f0, dp=0x7f5ac0078490) at ./kstars/indi/clientmanager.cpp:86 #5 0x5604bc385195 in INDI::BaseClient::addDevice(xml_ele_*, char*) () #6 0x5604bc385320 in INDI::BaseClient::findDev(xml_ele_*, int, char*) () #7 0x5604bc3863ff in INDI::BaseClient::dispatchCommand(xml_ele_*, char*) () #8 0x5604bc387065 in INDI::BaseClient::listenINDI() () #9 0x5604bc3871fa in INDI::BaseClient::listenHelper(void*) () #10 0x5604bc387239 in std::thread::_State_impl > >::_M_run() () #11 0x7f5b1c8a9d84 in ?? () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6 #12 0x7f5b1e163609 in start_thread (arg=) at pthread_create.c:477 #13 0x7f5b1c597293 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 13 (Thread 0x7f5ae1ffe700 (LWP 1826)): #0 0x7f5b1bfae368 in g_mutex_unlock () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #1 0x7f5b1bf60b70 in g_main_context_check () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f5b1bf61152 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f5b1bf612e3 in g_main_context_iteration () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7f5b1d267583 in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f5b1d20e4db in QEventLoop::exec(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7f5b1d046785 in QThread::exec() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7f5b1d0479d2 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7f5b1e163609 in start_thread (arg=) at pthread_create.c:477 #9 0x7f5b1c597293 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 12 (Thread 0x7f5b01494700 (LWP 1775)): #0 0x7f5b1c58aaff in __GI___poll (fds=0x7f5ac40025e0, nfds=1, timeout=3638) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7f5b1bf611ae in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f5b1bf612e3 in g_main_context_iteration () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f5b1d267583 in QEventDispatcherGlib::proces
[kstars] [Bug 429660] kstars crash when starting job from schedualer
https://bugs.kde.org/show_bug.cgi?id=429660 Dominic bundy changed: What|Removed |Added CC||d...@bundy.co.uk -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 421300] New: Problem with install.sh script
https://bugs.kde.org/show_bug.cgi?id=421300 Bug ID: 421300 Summary: Problem with install.sh script Product: lattedock Version: git (master) Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: application Assignee: mvourla...@gmail.com Reporter: dominick...@gmail.com Target Milestone: --- Linux/KDE Plasma: Manjaro KDE (Kernel 5.6.10-3-MANJARO) KDE Plasma Version: 5.18.5 KDE Frameworks Version: 5.69.0 Qt Version: 5.14.2 SUMMARY When trying to build latte-dock-master, I was running into an issue with the cmake script. When trying to run the install.sh script, it was pointing to the wrong directory on my system specifically. STEPS TO REPRODUCE 1. Download git version of latte-dock 2. Extract components into folder 3. Make sure extra-cmake-modules is installed 4. Run install.sh script OBSERVED RESULT CMake Error at /usr/local/share/ECM/cmake/ECMConfig.cmake:11 (message):File or directory /usr/local/include/KF5 referenced by variablePlasmaQuick_INCLUDE_DIR does not exist !Call Stack (most recent call first):/usr/lib64/cmake/KF5PlasmaQuick/KF5PlasmaQuickConfig.cmake:45 (set_and_check)/usr/local/share/ECM/find-modules/FindKF5.cmake:74 (find_package)CMakeLists.txt:22 (find_package) Work Around For My Issue The problem is that the script references /usr/local/include/KF5 which does not exist. KF5 is located in /usr/include/KF5 on my system. A quick fix I found is just to create a symlink between /usr/include/KF5 and /usr/local/include/KF5 ln -s /usr/include/KF5/ /usr/local/include/KF5/ After this, the install.sh script runs just fine. ADDITIONAL INFORMATION I'm not sure if this is a bug related to cmake or latte-dock specifically. (First bug report. Sorry if anything is wrong & please let me know if I can do anything better) -- You are receiving this mail because: You are watching all bug changes.
[kdelibs] [Bug 60900] Setting a local raw printer using CUPS does not work
https://bugs.kde.org/show_bug.cgi?id=60900 Dominic Jacques changed: What|Removed |Added Resolution|WAITINGFORINFO |--- Status|NEEDSINFO |REPORTED --- Comment #3 from Dominic Jacques --- I've entered the bug 15 years ago... Please close it, it is probably no more relevant. Regards, Dominic -- You are receiving this mail because: You are watching all bug changes.
