[plasmashell] [Bug 483205] Rapidly moving the pointer over categories causes Plasma to lag and eventually freeze if you keep doing it
https://bugs.kde.org/show_bug.cgi?id=483205 MScattolin changed: What|Removed |Added CC||matheus.scattolinanselmo@ou ||tlook.com --- Comment #9 from MScattolin --- *** Bug 485136 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 485136] Quickly mouse-hovering kickoff's sidebar momentarily freezes plasma and leaks memory
https://bugs.kde.org/show_bug.cgi?id=485136 MScattolin changed: What|Removed |Added Resolution|--- |DUPLICATE Status|REPORTED|RESOLVED --- Comment #1 from MScattolin --- *** This bug has been marked as a duplicate of bug 483205 *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 485136] New: Quickly mouse-hovering kickoff's sidebar momentarily freezes plasma and leaks memory
https://bugs.kde.org/show_bug.cgi?id=485136 Bug ID: 485136 Summary: Quickly mouse-hovering kickoff's sidebar momentarily freezes plasma and leaks memory Classification: Plasma Product: plasmashell Version: 6.0.3 Platform: unspecified OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: Application Launcher (Kickoff) Assignee: plasma-b...@kde.org Reporter: matheus.scattolinanse...@outlook.com CC: mikel5...@gmail.com, noaha...@gmail.com Target Milestone: 1.0 Created attachment 168220 --> https://bugs.kde.org/attachment.cgi?id=168220=edit a recording of kickoff freezing SUMMARY This causes plasma to freeze, using a lot of CPU and memory. When plasma unfreezes the allocated memory is not freed until the process is killed. It can freeze plasma for multiple minutes, and it ends up allocating gigabytes of RAM if you keep hovering STEPS TO REPRODUCE 1. Open kickoff 2. Quickly hover up and down over the sidebar OBSERVED RESULT The longer this is done, the more memory ends up being used SOFTWARE/OS VERSIONS Linux/KDE Plasma: 6.8.0 KDE Plasma Version: 6.0.3 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.3 ADDITIONAL INFORMATION There's a recording attached with a systemmonitor window on the background to keep track of the used memory -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 478114] New: Crash after display power off
https://bugs.kde.org/show_bug.cgi?id=478114 Bug ID: 478114 Summary: Crash after display power off Classification: Plasma Product: plasmashell Version: 5.90.0 Platform: Arch Linux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: generic-crash Assignee: plasma-b...@kde.org Reporter: matheus.scattolinanse...@outlook.com Target Milestone: 1.0 Flags: Wayland+ SUMMARY This crash happened after manually powering off the connected display. It doesn't seem to happen every time STEPS TO REPRODUCE 1. Manually power off the display through a hardware button 2. Plasma crashed on the background SOFTWARE/OS VERSIONS Linux/KDE Plasma: 6.6.4 KDE Plasma Version: 5.90.0 KDE Frameworks Version: 5.246.0 Qt Version: 6.6.1 BACKTRACE #0 __GI___pthread_sigmask (how=1, newmask=, oldmask=0x0) at pthread_sigmask.c:43 #1 0x7fdc6145c90d in __GI___sigprocmask (how=, set=, oset=) at ../sysdeps/unix/sysv/linux/sigprocmask.c:25 #2 0x7fdc644024eb in KCrash::setCrashHandler(void (*)(int)) (handler=handler@entry=0x0) at /usr/src/debug/kcrash/kcrash-5.246.0/src/kcrash.cpp:407 #3 0x7fdc64404958 in KCrash::defaultCrashHandler(int) (sig=11) at /usr/src/debug/kcrash/kcrash-5.246.0/src/kcrash.cpp:611 #4 0x7fdc6145c710 in () at /usr/lib/libc.so.6 #5 std::__atomic_base::load(std::memory_order) const (__m=std::memory_order::relaxed, this=0x2e65646b2e677273, this=, __m=) at /usr/include/c++/13.2.1/bits/atomic_base.h:503 #6 QAtomicOps::loadRelaxed(std::atomic const&) (_q_value=, _q_value=) at /usr/include/qt6/QtCore/qatomic_cxx11.h:201 #7 QBasicAtomicInteger::loadRelaxed() const (this=0x2e65646b2e677273, this=) at /usr/include/qt6/QtCore/qbasicatomic.h:38 #8 QWeakPointer::internalData() const (this=0x5585a6706910) at /usr/include/qt6/QtCore/qsharedpointer_impl.h:704 #9 QPointer::data() const (this=0x5585a6706910) at /usr/include/qt6/QtCore/qpointer.h:71 #10 QPointer::operator Plasma::Containment*() const (this=0x5585a6706910) at /usr/include/qt6/QtCore/qpointer.h:79 #11 PlasmaQuick::ContainmentView::containment() const (this=0x5585a6357a20) at /usr/src/debug/libplasma/libplasma-5.90.0/src/plasmaquick/containmentview.cpp:239 #12 0x5585a14911a7 in operator() (__closure=0x5585a6316550) at /usr/src/debug/plasma-workspace/plasma-workspace-5.90.0/shell/shellcorona.cpp:1502 #13 QtPrivate::FunctorCall, QtPrivate::List<>, void, ShellCorona::createWaitingPanels():: >::call (arg=, f=...) at /usr/include/qt6/QtCore/qobjectdefs_impl.h:137 #14 QtPrivate::Functor, 0>::call, void> (arg=, f=...) at /usr/include/qt6/QtCore/qobjectdefs_impl.h:339 #15 QtPrivate::QCallableObject, QtPrivate::List<>, void>::impl(int, QtPrivate::QSlotObjectBase *, QObject *, void **, bool *) (which=, this_=0x5585a6316540, r=, a=, ret=) at /usr/include/qt6/QtCore/qobjectdefs_impl.h:522 #16 0x7fdc61bb9ec9 in QtPrivate::QSlotObjectBase::call(QObject*, void**) (a=0x7ffe72f85aa0, r=0x5585a2d7ebf0, this=0x5585a6316540, this=, r=, a=) at /usr/src/debug/qt6-base/qtbase-everywhere-src-6.6.1/src/corelib/kernel/qobjectdefs_impl.h:433 #17 doActivate(QObject*, int, void**) (sender=0x5585a6357a20, signal_index=15, argv=0x7ffe72f85aa0) at /usr/src/debug/qt6-base/qtbase-everywhere-src-6.6.1/src/corelib/kernel/qobject.cpp:4021 #18 0x7fdc62200476 in QWindow::visibleChanged(bool) (_t1=false, this=0x5585a6357a20) at /usr/src/debug/qt6-base/build/src/gui/Gui_autogen/include/moc_qwindow.cpp:1195 #19 QWindowPrivate::setVisible(bool) (this=0x5585a61bb910, visible=false) at /usr/src/debug/qt6-base/qtbase-everywhere-src-6.6.1/src/gui/kernel/qwindow.cpp:340 #20 0x7fdc6220496a in QWindow::setVisible(bool) (visible=false, this=0x5585a6357a20) at /usr/src/debug/qt6-base/qtbase-everywhere-src-6.6.1/src/gui/kernel/qwindow.cpp:681 #21 QWindowPrivate::destroy() (this=0x5585a61bb910) at /usr/src/debug/qt6-base/qtbase-everywhere-src-6.6.1/src/gui/kernel/qwindow.cpp:2042 #22 0x7fdc621fec52 in QWindow::~QWindow() (this=0x5585a6357a20, this=) at /usr/src/debug/qt6-base/qtbase-everywhere-src-6.6.1/src/gui/kernel/qwindow.cpp:185 #23 0x5585a1466f3d in PanelView::~PanelView() (this=0x5585a6357a20, this=) at /usr/src/debug/plasma-workspace/plasma-workspace-5.90.0/shell/panelview.cpp:128 #24 0x7fdc61ba5258 in qDeleteInEventHandler(QObject*) (o=0x5585a6357a20) at /usr/src/debug/qt6-base/qtbase-everywhere-src-6.6.1/src/corelib/kernel/qobject.cpp:4900 #25 QObject::event(QEvent*) (this=0x5585a6357a20, e=0x5585a653a390) at /usr/src/debug/qt6-base/qtbase-everywhere-src-6.6.1/src/corelib/kernel/qobject.cpp:1424 #26 0x7fdc63b7319b in QApplicationPrivate::notify_helper(QObject*, QEvent*) (this=, receiver=0x5585a6357a20, e=0x5585a653a390) at /usr/src/debug/qt6-base/qtbase-everywhere-src-6.6.1/src/widgets/kernel/qapplication.cpp:3296 #27 0x7fdc61b62a78 in
[systemsettings] [Bug 477928] New: Night Light KCM prompts to save changes after geolocation has been completed, even though no changes were made
https://bugs.kde.org/show_bug.cgi?id=477928 Bug ID: 477928 Summary: Night Light KCM prompts to save changes after geolocation has been completed, even though no changes were made Classification: Applications Product: systemsettings Version: 5.90.0 Platform: Other OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: kcm_nightcolor Assignee: plasma-b...@kde.org Reporter: matheus.scattolinanse...@outlook.com CC: kwin-bugs-n...@kde.org Target Milestone: --- SUMMARY If the kcm is set to handle night light automatically according to the current location, it prompts the user to save when switching away to another module even if no changes were made. This only happens AFTER the geolocation completes, switching away before it does triggers no prompt STEPS TO REPRODUCE 1. Click on Night Light KCM through systemsettings 2. Wait for the geolocation to complete 3. Switch to another KCM OBSERVED RESULT A dialog prompting to save changes that were not made SOFTWARE/OS VERSIONS Linux/KDE Plasma: 6.5.13 KDE Plasma Version: 5.90.0 KDE Frameworks Version: 5.246.0 Qt Version: 6.6.1 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 477233] New: plasmashell crashes when trying to exit "Edit Mode"
https://bugs.kde.org/show_bug.cgi?id=477233 Bug ID: 477233 Summary: plasmashell crashes when trying to exit "Edit Mode" Classification: Plasma Product: plasmashell Version: 5.27.80 Platform: Other OS: Linux Status: REPORTED Keywords: qt6 Severity: normal Priority: NOR Component: Edit Mode toolbar Assignee: plasma-b...@kde.org Reporter: matheus.scattolinanse...@outlook.com Target Milestone: 1.0 SUMMARY Plasma sometimes crashes whilst exiting Edit Mode, either through clicking the close button or pressing ESC (which doesn't seem to work every time, but it still crashes it) Also while fiddling with it in an attempt to get plasma to crash again, I actually got a different stack trace once while doing the same thing, it is attached at the end of the main trace because I was unsure about opening a different report STEPS TO REPRODUCE 1. Right click panel 2. Enter Edit Mode 3. Press ESC OBSERVED RESULT the shell crashes SOFTWARE/OS VERSIONS Linux/KDE Plasma: Arch, KDE-Unstable repo, kernel 6.5.11 KDE Plasma Version: 5.27.80 KDE Frameworks Version: 5.245.0 Qt Version: 6.6.0 Wayland Session ADDITIONAL INFORMATION Core was generated by `/usr/bin/plasmashell --replace'. Program terminated with signal SIGSEGV, Segmentation fault. #0 __pthread_kill_implementation (threadid=, signo=signo@entry=11, no_tid=no_tid@entry=0) at pthread_kill.c:44 #1 0x7ff8ed8ac8a3 in __pthread_kill_internal (signo=11, threadid=) at pthread_kill.c:78 #2 0x7ff8ed85c668 in __GI_raise (sig=11) at ../sysdeps/posix/raise.c:26 #3 0x7ff8f0614582 in KCrash::defaultCrashHandler(int) (sig=11) at /usr/src/debug/kcrash/kcrash-5.245.0/src/kcrash.cpp:597 #4 0x7ff8ed85c710 in () at /usr/lib/libc.so.6 #5 QScopedScopeLevelCounter::QScopedScopeLevelCounter(QThreadData*) (threadData=0x0, this=, this=, threadData=) at /usr/src/debug/qt6-base/build/include/QtCore/6.6.0/QtCore/private/../../../../../../qtbase-everywhere-src-6.6.0/src/corelib/thread/qthread_p.h:339 #6 QCoreApplication::notifyInternal2(QObject*, QEvent*) (receiver=0x562dd22edf20, event=0x7ffe8db286b0) at /usr/src/debug/qt6-base/qtbase-everywhere-src-6.6.0/src/corelib/kernel/qcoreapplication.cpp:1115 #7 0x7ff8edf6271d in QCoreApplication::sendEvent(QObject*, QEvent*) (receiver=, event=) at /usr/src/debug/qt6-base/qtbase-everywhere-src-6.6.0/src/corelib/kernel/qcoreapplication.cpp:1536 #8 0x7ff8ee5e9ad0 in QPlatformWindow::deliverUpdateRequest() (this=) at /usr/src/debug/qt6-base/qtbase-everywhere-src-6.6.0/src/gui/kernel/qplatformwindow.cpp:783 #9 0x7ff8edfa5077 in QObject::event(QEvent*) (this=0x562dd2606670, e=0x562dd2929190) at /usr/src/debug/qt6-base/qtbase-everywhere-src-6.6.0/src/corelib/kernel/qobject.cpp:1437 #10 0x7ff8eef7318b in QApplicationPrivate::notify_helper(QObject*, QEvent*) (this=, receiver=0x562dd2606670, e=0x562dd2929190) at /usr/src/debug/qt6-base/qtbase-everywhere-src-6.6.0/src/widgets/kernel/qapplication.cpp:3290 #11 0x7ff8edf626d8 in QCoreApplication::notifyInternal2(QObject*, QEvent*) (receiver=0x562dd2606670, event=event@entry=0x562dd2929190) at /usr/src/debug/qt6-base/qtbase-everywhere-src-6.6.0/src/corelib/kernel/qcoreapplication.cpp:1118 #12 0x7ff8edf62a5b in QCoreApplication::sendEvent(QObject*, QEvent*) (event=0x562dd2929190, receiver=) at /usr/src/debug/qt6-base/qtbase-everywhere-src-6.6.0/src/corelib/kernel/qcoreapplication.cpp:1536 #13 QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) (receiver=0x0, event_type=0, data=0x562dcec96690) at /usr/src/debug/qt6-base/qtbase-everywhere-src-6.6.0/src/corelib/kernel/qcoreapplication.cpp:1898 #14 0x7ff8ee199d24 in QCoreApplication::sendPostedEvents(QObject*, int) (receiver=0x0, event_type=0) at /usr/src/debug/qt6-base/qtbase-everywhere-src-6.6.0/src/corelib/kernel/qcoreapplication.cpp:1757 #15 postEventSourceDispatch(GSource*, GSourceFunc, gpointer) (s=0x562dced1f550) at /usr/src/debug/qt6-base/qtbase-everywhere-src-6.6.0/src/corelib/kernel/qeventdispatcher_glib.cpp:243 #16 0x7ff8ecb45f69 in g_main_dispatch (context=0x7ff8e4000ef0) at ../glib/glib/gmain.c:3476 #17 0x7ff8ecba4327 in g_main_context_dispatch_unlocked (context=0x7ff8e4000ef0) at ../glib/glib/gmain.c:4284 #18 g_main_context_iterate_unlocked.isra.0 (context=context@entry=0x7ff8e4000ef0, block=block@entry=1, dispatch=dispatch@entry=1, self=) at ../glib/glib/gmain.c:4349 #19 0x7ff8ecb44162 in g_main_context_iteration (context=0x7ff8e4000ef0, may_block=1) at ../glib/glib/gmain.c:4414 #20 0x7ff8ee197934 in QEventDispatcherGlib::processEvents(QFlags) (this=0x562dcec9bad0, flags=...) at /usr/src/debug/qt6-base/qtbase-everywhere-src-6.6.0/src/corelib/kernel/qeventdispatcher_glib.cpp:393 --Type for more, q to quit, c to continue without paging-- #21 0x7ff8edf6cc5e in
[kwin] [Bug 471562] Crash in KWin::DrmGammaRamp constructor
https://bugs.kde.org/show_bug.cgi?id=471562 MScattolin changed: What|Removed |Added CC||matheus.scattolinanselmo@ou ||tlook.com --- Comment #2 from MScattolin --- I'm experiencing the same crash with the exact same backtrace. However there's an oddity on my setup that triggers this crash so I thought about adding it to this report just in case it's useful in any way. I have only one display on a desktop computer, but it is connected through HDMI and DPI at same time from the same GPU. KScreen detects both connectors but I have the HDMI disabled. I have it this way because the UEFI settings on my motherboard refuse to work through the DP output, so this weird setup is not KDE related It crashes when waking up from sleep if I have the HDMI cable connected but disabled on KScreen, it never happens if it's physically unplugged -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 470484] Powerdevil crashes multiple times during screen sleep
https://bugs.kde.org/show_bug.cgi?id=470484 --- Comment #2 from MScattolin --- (In reply to Nicolas Fella from comment #1) > Can you please follow > https://community.kde.org/Guidelines_and_HOWTOs/Debugging/ > How_to_create_useful_crash_reports#Retrieving_a_backtrace_using_coredumpctl > to get a proper backtrace? The one you pasted is missing demangling and > debug symbols to be fully useful Hello, sure, got the following from the latest coredump: #0 __GI___pthread_sigmask (how=1, newmask=, oldmask=0x0) at pthread_sigmask.c:43 #1 0x7fd6e264fcad in __GI___sigprocmask (how=, set=, oset=) at ../sysdeps/unix/sysv/linux/sigprocmask.c:25 #2 0x7fd6e3c5520b in KCrash::setCrashHandler(void (*)(int)) (handler=handler@entry=0x0) at /usr/src/debug/kcrash/kcrash-5.106.0/src/kcrash.cpp:414 #3 0x7fd6e3c57816 in KCrash::defaultCrashHandler(int) (sig=11) at /usr/src/debug/kcrash/kcrash-5.106.0/src/kcrash.cpp:625 #4 0x7fd6e264fab0 in () at /usr/lib/libc.so.6 #5 QtWayland::org_kde_kwin_dpms::set(unsigned int) (mode=, this=0x10) at /usr/src/debug/libkscreen/build/src/libdpms/qwayland-dpms.cpp:126 #6 WaylandDpmsHelper::trigger(KScreen::Dpms::Mode, QList const&) (this=0x559b6a7b7380, mode=, screens=) at /usr/src/debug/libkscreen/libkscreen-5.27.5/src/libdpms/waylanddpmshelper.cpp:191 #7 0x7fd6dc2ffcc4 in KScreen::Dpms::switchMode(KScreen::Dpms::Mode, QList const&) (this=, mode=mode@entry=KScreen::Dpms::Off, screens=...) at /usr/src/debug/libkscreen/libkscreen-5.27.5/src/libdpms/dpms.cpp:40 #8 0x7fd6dc30a6ca in PowerDevil::BundledActions::DPMS::onIdleTimeout(int) (this=, msec=) at /usr/src/debug/powerdevil/powerdevil-5.27.5/daemon/actions/bundled/dpms.cpp:135 #9 0x7fd6e3c22a51 in PowerDevil::Core::onKIdleTimeoutReached(int, int) (this=0x559b6a7606b0, identifier=1, msec=150) at /usr/src/debug/powerdevil/powerdevil-5.27.5/daemon/powerdevilcore.cpp:840 #10 0x7fd6e2ed01a3 in doActivate(QObject*, int, void**) (sender=0x559b6a759570, signal_index=5, argv=0x7ffc3e8201a0) at kernel/qobject.cpp:3935 #11 0x7fd6e31c433d in KIdleTime::timeoutReached(int, int) (this=this@entry=0x559b6a759570, _t1=, _t1@entry=1, _t2=, _t2@entry=150) at /usr/src/debug/kidletime/build/src/KF5IdleTime_autogen/include/moc_kidletime.cpp:195 #12 0x7fd6e31c4ee1 in KIdleTimePrivate::timeoutReached(int) (msec=150, this=) at /usr/src/debug/kidletime/kidletime-5.106.0/src/kidletime.cpp:297 #13 operator() (msec=150, __closure=) at /usr/src/debug/kidletime/kidletime-5.106.0/src/kidletime.cpp:88 #14 QtPrivate::FunctorCall, QtPrivate::List, void, KIdleTime::KIdleTime():: >::call (arg=, f=) at /usr/include/qt/QtCore/qobjectdefs_impl.h:146 #15 QtPrivate::Functor, 1>::call, void> (arg=, f=) at /usr/include/qt/QtCore/qobjectdefs_impl.h:256 #16 QtPrivate::QFunctorSlotObject, 1, QtPrivate::List, void>::impl(int, QtPrivate::QSlotObjectBase *, QObject *, void **, bool *) (which=, this_=, r=, a=, ret=) at /usr/include/qt/QtCore/qobjectdefs_impl.h:443 #17 0x7fd6e2ecffe7 in QtPrivate::QSlotObjectBase::call(QObject*, void**) (a=0x7ffc3e8202f0, r=, this=0x559b6a7b2c30, this=, r=, a=) at ../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398 #18 doActivate(QObject*, int, void**) (sender=0x559b6a81b3f0, signal_index=4, argv=0x7ffc3e8202f0) at kernel/qobject.cpp:3923 #19 0x7fd6e31c4226 in AbstractSystemPoller::timeoutReached(int) (this=, _t1=) at /usr/src/debug/kidletime/build/src/KF5IdleTime_autogen/EWIEGA46WW/moc_abstractsystempoller.cpp:189 #20 0x7fd6e2ecffe7 in QtPrivate::QSlotObjectBase::call(QObject*, void**) (a=0x7ffc3e8203a0, r=, this=0x559b6a76c5b0, this=, r=, a=) at ../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398 #21 doActivate(QObject*, int, void**) (sender=0x7fd6d8026640, signal_index=3, argv=0x7ffc3e8203a0) at kernel/qobject.cpp:3923 #22 0x7fd6e3c6b4f6 in () at /usr/lib/libffi.so.8 #23 0x7fd6e3c67f5e in () at /usr/lib/libffi.so.8 #24 0x7fd6e3c6ab73 in ffi_call () at /usr/lib/libffi.so.8 #25 0x7fd6e3c76645 in wl_closure_invoke (closure=closure@entry=0x7fd6d0001980, target=, target@entry=0x559b6a848860, opcode=opcode@entry=0, data=, flags=1) at ../wayland-1.22.0/src/connection.c:1025 #26 0x7fd6e3c76e73 in dispatch_event (display=display@entry=0x559b6a753100, queue=0x559b6a7531f0) at ../wayland-1.22.0/src/wayland-client.c:1631 #27 0x7fd6e3c7713c in dispatch_queue (queue=0x559b6a7531f0, display=0x559b6a753100) at ../wayland-1.22.0/src/wayland-client.c:1777 #28 wl_display_dispatch_queue_pending (display=0x559b6a753100, queue=0x559b6a7531f0) at ../wayland-1.22.0/src/wayland-client.c:2019 #29 0x7fd6dd6efc06 in QtWaylandClient::QWaylandDisplay::flushRequests() (this=) at /usr/src/debug/qt5-wayland/qtwayland/src/client/qwaylanddisplay.cpp:255 #30 0x7fd6e2ec2834 in QObject::event(QEvent*) (this=0x559b6a752fa0, e=0x7fd6d0001
[Powerdevil] [Bug 470484] New: Powerdevil crashes multiple times during screen sleep
https://bugs.kde.org/show_bug.cgi?id=470484 Bug ID: 470484 Summary: Powerdevil crashes multiple times during screen sleep Classification: Plasma Product: Powerdevil Version: 5.27.5 Platform: Archlinux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: matheus.scattolinanse...@outlook.com CC: m...@ratijas.tk, natalie_clar...@yahoo.de Target Milestone: --- Created attachment 159367 --> https://bugs.kde.org/attachment.cgi?id=159367=edit dr konqi screenshot SUMMARY Every day when I leave my computer idle with the screen powered off, powerdevil keeps regularly crashing and dumping core It's a desktop and it's not configured to suspend after a certain time STEPS TO REPRODUCE 1. turn off the computer monitor 2. wait 3. powerdevil will have crashed multiple times, plasma seems unaffected OBSERVED RESULT System log will be filled with stack traces from powerdevil EXPECTED RESULT Same but without crashes SOFTWARE/OS VERSIONS Linux/KDE Plasma: 6.3.3 KDE Plasma Version: 5.27.5 KDE Frameworks Version: 5.106.0 Qt Version: 5.15.9 ADDITIONAL INFORMATION I'm using plasma on wayland, with a radeon GPU, mesa drivers and one monitor connected through displayport Taking a look at those crashes on dr konqi, I noticed that every crash happens around 25min from each other. It's the same amount of time I have set on powerdevil's KCM for screen switch off STACK TRACE Stack trace of thread 110517: #0 0x7f54074a43c8 __GI___pthread_sigmask (libc.so.6 + 0x8e3c8) #1 0x7f540744fcad __GI___sigprocmask (libc.so.6 + 0x39cad) #2 0x7f5408a7820b _ZN6KCrash15setCrashHandlerEPFviE (libKF5Crash.so.5 + 0x520b) #3 0x7f5408a7a816 _ZN6KCrash19defaultCrashHandlerEi (libKF5Crash.so.5 + 0x7816) #4 0x7f540744fab0 __restore_rt (libc.so.6 + 0x39ab0) #5 0x7f540011a97c _ZN9QtWayland17org_kde_kwin_dpms3setEj (libKF5ScreenDpms.so.8 + 0x797c) #6 0x7f540011bcc4 _ZN7KScreen4Dpms10switchModeENS0_4ModeERK5QListIP7QScreenE (libKF5ScreenDpms.so.8 + 0x8cc4) #7 0x7f54001266ca _ZN10PowerDevil14BundledActions4DPMS13onIdleTimeoutEi (powerdevil_dpmsaction.so + 0x56ca) #8 0x7f5408a45a51 _ZN10PowerDevil4Core21onKIdleTimeoutReachedEii (libpowerdevilcore.so.2 + 0x17a51) #9 0x7f5407cd01a3 _Z10doActivateILb0EEvP7QObjectiPPv (libQt5Core.so.5 + 0x2d01a3) #10 0x7f540869833d _ZN9KIdleTime14timeoutReachedEii (libKF5IdleTime.so.5 + 0x433d) #11 0x7f5408698ee1 _ZN9QtPrivate18QFunctorSlotObjectIZN9KIdleTimeC4EvEUliE_Li1ENS_4ListIJiEEEvE4implEiPNS_15QSlotObjectBaseEP7QObjectPPvPb (libKF5IdleTime.so.5 + 0x4ee1) #12 0x7f5407ccffe7 _ZN9QtPrivate15QSlotObjectBase4callEP7QObjectPPv (libQt5Core.so.5 + 0x2cffe7) #13 0x7f5408698226 _ZN20AbstractSystemPoller14timeoutReachedEi (libKF5IdleTime.so.5 + 0x4226) #14 0x7f5407ccffe7 _ZN9QtPrivate15QSlotObjectBase4callEP7QObjectPPv (libQt5Core.so.5 + 0x2cffe7) #15 0x7f5408a8e4f6 n/a (libffi.so.8 + 0x74f6) #16 0x7f5408a8af5e n/a (libffi.so.8 + 0x3f5e) #17 0x7f5408a8db73 ffi_call (libffi.so.8 + 0x6b73) #18 0x7f5408a99645 wl_closure_invoke (libwayland-client.so.0 + 0x7645) #19 0x7f5408a99e73 dispatch_event (libwayland-client.so.0 + 0x7e73) #20 0x7f5408a9a13c dispatch_queue (libwayland-client.so.0 + 0x813c) #21 0x7f54024efc06 _ZN15QtWaylandClient15QWaylandDisplay13flushRequestsEv (libQt5WaylandClient.so.5 + 0x72c06) #22 0x7f5407cc2834 _ZN7QObject5eventEP6QEvent (libQt5Core.so.5 + 0x2c2834) #23 0x7f5407c9ab18 _ZN16QCoreApplication15notifyInternal2EP7QObjectP6QEvent (libQt5Core.so.5 + 0x29ab18) #24 0x7f5407c9fa7b _ZN23QCoreApplicationPrivate16sendPostedEventsEP7QObjectiP11QThreadData (libQt5Core.so.5 + 0x29fa7b) #25 0x7f5407ce6088 postEventSourceDispatch (libQt5Core.so.5 + 0x2e6088) #26 0x7f5406710981 g_main_context_dispatch (libglib-2.0.so.0 + 0x5a981) #27 0x7f540676db39 n/a (libglib-2.0.so.0 + 0xb7b39) #28 0x7f540670e032 g_main_context_iteration (libglib-2.0.so.0 + 0x58032) #29 0x7f5407ce9f0c _ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE (libQt5Core.so.5 + 0x2e9f0c) #30 0x7f5407c99824 _ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE (libQt5Core.so.5 + 0x299824) #31 0x7f5407c9acc3 _ZN16QCoreApplication4execEv (libQt5Core.so.5 + 0x29acc3)
[kwin] [Bug 463808] Quickly pressing alt+tab in succession from a window that is capturing the cursor won't keep mouse focus
https://bugs.kde.org/show_bug.cgi?id=463808 --- Comment #1 from MScattolin --- Created attachment 155740 --> https://bugs.kde.org/attachment.cgi?id=155740=edit alt+tabbing from a game (TF2) and back Here's a recording for illustration purposes, I'm alt+tabbing out of a game and back, then doing it again after a short delay, if you do it too fast, the game won't grab the cursor anymore. Then I repeated but after waiting a short while, and it worked. I originally stated that it happens in any game, but it's not true, I've found exceptions. However, I have no idea why some do, some don't, but it happens every time with ones who do. Being fullscreen and changing the cursor or just grabbing it seems to be related, but as it is now, the pattern is somewhat unclear Also, I should note that it only happens when using the alt+tab shortcut, manually clicking on the taskbar icon works as expected every time. I'm on plasma 5.26.5, but tested with 5.27 beta to same results, X11 session remains unaffected. I'm also using an AMD GPU on mesa drivers. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 463808] New: Quickly pressing alt+tab in succession from a window that is capturing the cursor won't keep mouse focus
https://bugs.kde.org/show_bug.cgi?id=463808 Bug ID: 463808 Summary: Quickly pressing alt+tab in succession from a window that is capturing the cursor won't keep mouse focus Classification: Plasma Product: kwin Version: 5.26.5 Platform: Archlinux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: wayland-generic Assignee: kwin-bugs-n...@kde.org Reporter: matheus.scattolinanse...@outlook.com Target Milestone: --- SUMMARY This does not happen in the X11 session, only wayland is affected here. If the current focused window is capturing the pointer, pressing alt+tab twice (apparently under 1s), effectively switching to another window and quickly going back, the mouse focus is completely lost, as in you can't interact with the window using the mouse pointer anymore. This is particularly obvious in full screen games, as you can't use the mouse within the game window after alt+tabbing twice, yet the cursor is visible on the screen, it's simply not relayed to the window anymore. The workaround is to manually minimize the window or pressing alt+tab again, then waiting a second, then alt tabbing back. It kinda feels like there's a timer component to it Keyboard focus in this scenario works as expected regardless STEPS TO REPRODUCE 1. Open fullscreen game: native/wine, it doesn't matter 2. Press alt+tab twice quickly 3. Cursor is visible on top of the window, but you can't interact with it anymore -- You are receiving this mail because: You are watching all bug changes.
[xdg-desktop-portal-kde] [Bug 450930] New: Can't close "Open with.." dialog when there's no suitable application installed
https://bugs.kde.org/show_bug.cgi?id=450930 Bug ID: 450930 Summary: Can't close "Open with.." dialog when there's no suitable application installed Product: xdg-desktop-portal-kde Version: 5.24.2 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: matheus.scattolinanse...@outlook.com CC: aleix...@kde.org, jgrul...@redhat.com, n...@kde.org Target Milestone: --- Created attachment 147174 --> https://bugs.kde.org/attachment.cgi?id=147174=edit "open with..." dialog 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 *** The summary pretty much describes it, a screenshot is also attached. You can't close the dialog by right-clicking the icon on the task manager either. STEPS TO REPRODUCE 1. Download a file with no associated program installed through Firefox using xdg-desktop-portal 2. Open it through the browser OBSERVED RESULT An unclosable dialog will open with no suggestions. The "Show More" button will help if a suitable program is installed but not set, but it won't if you'd have to install it manually. I've also tested and does not happen in chromium, it opens the same KIO dialog Dolphin does. EXPECTED RESULT Be able to close the dialog, install a suitable program elsewhere, and then try again. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: 5.16.11 (available in About System) KDE Plasma Version: 5.24.2 KDE Frameworks Version: 5.91.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION Also there's an horizontal scrollbar at all times, even though there is no content. -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 446482] Invisible item in 'Default theme' combobox causes list to scroll automatically when hovering with the cursor
https://bugs.kde.org/show_bug.cgi?id=446482 MScattolin changed: What|Removed |Added Summary|Invisible item on 'Default |Invisible item in 'Default |theme' combobox causes list |theme' combobox causes list |to scroll automatically |to scroll automatically |when hovering with the |when hovering with the |cursor |cursor -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 446482] New: Invisible item on 'Default theme' combobox causes list to scroll automatically when hovering with the cursor
https://bugs.kde.org/show_bug.cgi?id=446482 Bug ID: 446482 Summary: Invisible item on 'Default theme' combobox causes list to scroll automatically when hovering with the cursor Product: kate Version: 21.08.3 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: general Assignee: kwrite-bugs-n...@kde.org Reporter: matheus.scattolinanse...@outlook.com Target Milestone: --- Created attachment 144216 --> https://bugs.kde.org/attachment.cgi?id=144216=edit What happens when hovering, I did not used the mouse scroll wheel or arrow keys. SUMMARY When changing both kate and kwrite theme through the settings window, it seems that there's an invisible item under "Automatic Selection", that ends up at the bottom of the combobox list when scrolled past, causing the list to scroll down whenever the cursor hovers it. STEPS TO REPRODUCE 1. Go to Tools > Configure Editor... > Color Themes 2. Click on "Default theme for [kate/kwrite]" Combobox 3. Scroll Past "Automatic Selection" and the empty item under it 4. Hover at the end of the combobox list, a few px tall OBSERVED RESULT The list scrolls automatically EXPECTED RESULT The list should scroll only when activated SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: Arch (available in About System) KDE Plasma Version: 5.23.4 KDE Frameworks Version: 5.88.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION Attached small mkv as illustration. -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 445782] New: Latte ignores it's own "thickness" setting when aligning the tray item on vertical panels.
https://bugs.kde.org/show_bug.cgi?id=445782 Bug ID: 445782 Summary: Latte ignores it's own "thickness" setting when aligning the tray item on vertical panels. Product: lattedock Version: 0.10.4 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: application Assignee: mvourla...@gmail.com Reporter: matheus.scattolinanse...@outlook.com Target Milestone: --- Created attachment 143752 --> https://bugs.kde.org/attachment.cgi?id=143752=edit recording demonstrating what happens and how it fits whitin the the "thickness" setting from latte SUMMARY I've attached a gif demonstrating exactly what happens. This does not happen on horizontal panels. The tray subitem seems to ignore completely the 'thickness' setting within latte when drawing the popup. ADDITIONAL INFORMATION I'm on wayland, but that happens on X11 too. Other than that, thank you for your work :) -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 439472] Latte dock crashes when attempting to add widgets
https://bugs.kde.org/show_bug.cgi?id=439472 --- Comment #8 from MScattolin --- Created attachment 142967 --> https://bugs.kde.org/attachment.cgi?id=142967=edit New crash information added by DrKonqi latte-dock (0.10.3) using Qt 5.15.2 - What I was doing when the application crashed: 1. Right click on any latte dock/panel 2. Click 'Add New Widgets' 3. On the newly open "Widgets" window, click "Get New Widgets..." 4. Click "Download New Plasma Widgets" 5. Latte will crash every time, even with a clean config. Doing the same thing when right-clicking elsewhere, like the desktop, causes no crashes. -- Backtrace (Reduced): #4 0x7f250611f860 in QSGTexture::setFiltering(QSGTexture::Filtering) () at /usr/lib/libQt5Quick.so.5 #5 0x7f2506150b3c in QSGOpaqueTextureMaterialShader::updateState(QSGMaterialShader::RenderState const&, QSGMaterial*, QSGMaterial*) () at /usr/lib/libQt5Quick.so.5 #6 0x7f250613741a in QSGBatchRenderer::Renderer::renderMergedBatch(QSGBatchRenderer::Batch const*) () at /usr/lib/libQt5Quick.so.5 #7 0x7f250613cb96 in QSGBatchRenderer::Renderer::renderBatches() () at /usr/lib/libQt5Quick.so.5 #8 0x7f250613d5a5 in QSGBatchRenderer::Renderer::render() () at /usr/lib/libQt5Quick.so.5 -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 439472] Latte dock crashes when attempting to add widgets
https://bugs.kde.org/show_bug.cgi?id=439472 MScattolin changed: What|Removed |Added CC||matheus.scattolinanselmo@ou ||tlook.com -- You are receiving this mail because: You are watching all bug changes.
[plasma-systemmonitor] [Bug 435515] systemmonitor crashes when switching away from "Process Table" or "Application Table"
https://bugs.kde.org/show_bug.cgi?id=435515 --- Comment #2 from MScattolin --- I'was actually about to include it, but I thought it was not very helpful. Nevertheless, here is what Dr. Konqi presents me. --- Application: System Monitor (plasma-systemmonitor), signal: Segmentation fault [KCrash Handler] #4 0x7f364735049d in ?? () from /usr/lib/libQt5QuickTemplates2.so.5 #5 0x7f36473459cf in QQuickControlPrivate::updateImplicitContentWidth() () from /usr/lib/libQt5QuickTemplates2.so.5 #6 0x7f3647350632 in ?? () from /usr/lib/libQt5QuickTemplates2.so.5 #7 0x7f364766d915 in QQuickItemPrivate::implicitWidthChanged() () from /usr/lib/libQt5Quick.so.5 #8 0x7f364767182b in QQuickItem::setImplicitSize(double, double) () from /usr/lib/libQt5Quick.so.5 #9 0x7f364412773f in ?? () from /usr/lib/qt/qml/QtQuick/Layouts/libqquicklayoutsplugin.so #10 0x7f3644129e0b in ?? () from /usr/lib/qt/qml/QtQuick/Layouts/libqquicklayoutsplugin.so #11 0x7f36441268e4 in ?? () from /usr/lib/qt/qml/QtQuick/Layouts/libqquicklayoutsplugin.so #12 0x7f3644129ddf in ?? () from /usr/lib/qt/qml/QtQuick/Layouts/libqquicklayoutsplugin.so #13 0x7f3644131403 in ?? () from /usr/lib/qt/qml/QtQuick/Layouts/libqquicklayoutsplugin.so #14 0x7f3650abdd3e in QObjectPrivate::deleteChildren() () from /usr/lib/libQt5Core.so.5 #15 0x7f3650ac8be5 in QObject::~QObject() () from /usr/lib/libQt5Core.so.5 #16 0x7f363fa0bc67 in ?? () from /usr/lib/qt/qml/QtQuick/Templates.2/libqtquicktemplates2plugin.so #17 0x7f3650abdd3e in QObjectPrivate::deleteChildren() () from /usr/lib/libQt5Core.so.5 #18 0x7f3650ac8be5 in QObject::~QObject() () from /usr/lib/libQt5Core.so.5 #19 0x7f363fa0d800 in ?? () from /usr/lib/qt/qml/QtQuick/Templates.2/libqtquicktemplates2plugin.so #20 0x7f3650abdd3e in QObjectPrivate::deleteChildren() () from /usr/lib/libQt5Core.so.5 #21 0x7f3650ac8be5 in QObject::~QObject() () from /usr/lib/libQt5Core.so.5 #22 0x7f363c243867 in ?? () from /usr/lib/qt/qml/org/kde/ksysguard/faces/libFacesPlugin.so #23 0x7f3650abff70 in QObject::event(QEvent*) () from /usr/lib/libQt5Core.so.5 #24 0x7f36515e5762 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib/libQt5Widgets.so.5 #25 0x7f3650a936aa in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /usr/lib/libQt5Core.so.5 #26 0x7f3650a961a3 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () from /usr/lib/libQt5Core.so.5 #27 0x7f3650aecbe4 in ?? () from /usr/lib/libQt5Core.so.5 #28 0x7f364f4e9f9c in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0 #29 0x7f364f53da49 in ?? () from /usr/lib/libglib-2.0.so.0 #30 0x7f364f4e76f1 in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0 #31 0x7f3650aec221 in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/libQt5Core.so.5 #32 0x7f3650a9200c in QEventLoop::exec(QFlags) () from /usr/lib/libQt5Core.so.5 #33 0x7f3650a9a4c4 in QCoreApplication::exec() () from /usr/lib/libQt5Core.so.5 #34 0x55cdac4ca2a4 in ?? () #35 0x7f365045ab25 in __libc_start_main () from /usr/lib/libc.so.6 #36 0x55cdac4ca77e in ?? () [Inferior 1 (process 136276) detached] -- You are receiving this mail because: You are watching all bug changes.
[plasma-systemmonitor] [Bug 435515] New: systemmonitor crashes when switching away from "Process Table" or "Application Table"
https://bugs.kde.org/show_bug.cgi?id=435515 Bug ID: 435515 Summary: systemmonitor crashes when switching away from "Process Table" or "Application Table" Product: plasma-systemmonitor Version: 5.21.4 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: ksysguard-b...@kde.org Reporter: matheus.scattolinanse...@outlook.com CC: ahiems...@heimr.nl, plasma-b...@kde.org Target Milestone: --- SUMMARY plasma-systemmonitor crashes every time you are switching "Display Styles" from either "Application Table" or "Process Table" to anything else. STEPS TO REPRODUCE 1. Open systemmonitor 2. Click "Edit Page" and select any chart on it 3. Under "Display Styles", pick either Application Table or Process Table (skip if it already was one of them) 4. Under the same chart, switch the Display Style again to something else eg. Bar Chart OBSERVED RESULT systemmonitor will crash every time EXPECTED RESULT it should switch away from it seamlessly. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: Arch 5.11.11 (available in About System) KDE Plasma Version: 5.21.4 KDE Frameworks Version: 5.80.0 Qt Version: 5.15.12 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 434645] New: Colors KCM hides bottom frame when systemsettings window is at minimum size
https://bugs.kde.org/show_bug.cgi?id=434645 Bug ID: 434645 Summary: Colors KCM hides bottom frame when systemsettings window is at minimum size Product: systemsettings Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: kcm_colors Assignee: plasma-b...@kde.org Reporter: matheus.scattolinanse...@outlook.com CC: jpwhit...@kde.org, mwoehlke.fl...@gmail.com Target Milestone: --- Created attachment 136867 --> https://bugs.kde.org/attachment.cgi?id=136867=edit missing frame at the bottom SUMMARY KCM won't show "Install from File" and "Get New Color Schemes" buttons and their frame at the bottom when opening the KCM while the systemsettings window is at the minimum allowed size. If the window is enlarged and shrunken back at the minimun size, the frame will keep, but will disappear when switching KCMs. STEPS TO REPRODUCE 1. Open systemsettings / Go to any other KCM 2. Resize window to the minimum size 3. Open the 'Colors' KCM OBSERVED RESULT Bottom frame will be missing EXPECTED RESULT The bottom frame should be there no matter the window size SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: 5.11.7 (available in About System) KDE Plasma Version: 5.21.3 KDE Frameworks Version: 5.80 Qt Version: 5.15.2 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[plasma-systemmonitor] [Bug 434515] Changing a sensor color in a chart with multiple sensors wrongly applies it to every sensor in that chart
https://bugs.kde.org/show_bug.cgi?id=434515 MScattolin changed: What|Removed |Added Summary|Unable to change a sensor's |Changing a sensor color in |color |a chart with multiple ||sensors wrongly applies it ||to every sensor in that ||chart -- You are receiving this mail because: You are watching all bug changes.
[plasma-systemmonitor] [Bug 434515] Unable to change a sensor's color
https://bugs.kde.org/show_bug.cgi?id=434515 --- Comment #2 from MScattolin --- Created attachment 136794 --> https://bugs.kde.org/attachment.cgi?id=136794=edit gif illustrating the situation Not really, I've attached a gif showing what happens. -- You are receiving this mail because: You are watching all bug changes.
[plasma-systemmonitor] [Bug 434515] New: Unable to change a sensor's color
https://bugs.kde.org/show_bug.cgi?id=434515 Bug ID: 434515 Summary: Unable to change a sensor's color Product: plasma-systemmonitor Version: 5.21.3 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: ksysguard-b...@kde.org Reporter: matheus.scattolinanse...@outlook.com CC: ahiems...@heimr.nl, plasma-b...@kde.org Target Milestone: --- SUMMARY When customizing the overview page, you can't assign different colors to each sensor other than the defaults. STEPS TO REPRODUCE 1. Start systemmonitor for the first time (I've erased ~/.local/share/plasma-systemmonitor/overview.page) 2. Click on "Edit Page" 3. Add a new column to the top row 4. Add 2 sensors to that column 5. Pick a new color to one of them by clicking on the color square beside the name 6. Pick another color by clicking on the square on the other sensor OBSERVED RESULT Both sensors are assigned the color chosen on step 6. EXPECTED RESULT When picking a color on step 6, the color chosen during the step 5 should remain. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: 5.11.6 (available in About System) KDE Plasma Version: 5.21.3 KDE Frameworks Version: 5.80 Qt Version: 5.15.2 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 431956] Window titlebar is taller when running on wayland
https://bugs.kde.org/show_bug.cgi?id=431956 --- Comment #3 from MScattolin --- (In reply to Nate Graham from comment #1) > Does this happen with other window decoration themes, or just Breeze? > > Also does it happen with Noto Sans 10 or Noto Sans 11? I can confirm it happens on oxygen as well, so maybe this should be moved to kwin? Regarding the fonts, it does not happen with noto, the panel scales when changing from 11 to 12, on both wayland and x11. Fira does the same on X11, but the titlebar scales with size 11 on wayland only. This is more like defect than properly a bug, but it can look pretty odd when using (not so) non standard fonts. Since the titlebar size seems tied to glyph size, is it done differently on wayland? -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 431956] New: Window titlebar is taller when running on wayland
https://bugs.kde.org/show_bug.cgi?id=431956 Bug ID: 431956 Summary: Window titlebar is taller when running on wayland Product: Breeze Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: window decoration Assignee: plasma-b...@kde.org Reporter: matheus.scattolinanse...@outlook.com CC: kwin-bugs-n...@kde.org Target Milestone: --- Created attachment 135072 --> https://bugs.kde.org/attachment.cgi?id=135072=edit this shows a wayland screenshot(under) with a X11 screenshot(above) SUMMARY STEPS TO REPRODUCE 1. Start plasma on wayland 2. Titlebars are bigger than the same configuration on X11 3. - OBSERVED RESULT Considerably taller window titlebar when running on wayland EXPECTED RESULT, Given that both use the same font, fontsize, and titlebar size on systemsettings, they should have the same size. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: 5.10.9 (available in About System) KDE Plasma Version: 5.20.90 KDE Frameworks Version: 5.78.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION It seems something related to the font/size, as changing fonts alter this behaviour. I am using Fira Sans 11pt as window title. I am also using it under 94dpi, if it matters. This issue happens for quite some time now. I'm reporting it after seeing it still happens on the latest plasma beta (5.20.90) -- You are receiving this mail because: You are watching all bug changes.
[ksysguard] [Bug 424671] New: Wrong CPU usage reported after OOM kill
https://bugs.kde.org/show_bug.cgi?id=424671 Bug ID: 424671 Summary: Wrong CPU usage reported after OOM kill Product: ksysguard Version: 5.19.3 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: ksysguard-b...@kde.org Reporter: matheus.scattolinanse...@outlook.com CC: plasma-b...@kde.org Target Milestone: --- Created attachment 130403 --> https://bugs.kde.org/attachment.cgi?id=130403=edit comparison between ksysguard and htop SUMMARY After an "out of memory" kill is triggered, ksysguard will report incorrect CPU usage. It is happening without any userspace tool for OOM management, and I've only managed to fix it by restarting the session, closing ksysguard and opening it again will keep showing incorrect data. "wrong" as in higher than reported in other tool, such as 100% in some of the cores, all of them or just one, depending on what the program was doing before stopping. I'm using htop and gnome-system-monitor for comparison. STEPS TO REPRODUCE 1. Open enough applications to fill up the memory. One single program filling the entire memory works best, like a game. 2. Wait for the kernel to kill the application. 3. ksysguard will report wrong CPU usage info from now on. OBSERVED RESULT wronge CPU usage information EXPECTED RESULT CPU usage according to what is displayed on the 'Process Table' tab SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: 5.7.10 (available in About System) KDE Plasma Version: 5.19.3 KDE Frameworks Version: 5.72 Qt Version: 5.15 ADDITIONAL INFORMATION the OOM kill logs the following, plus some stack trace: jul 25 22:55:46 hades kernel: Out of memory: Killed process 2651 (Cities.x64) total-vm:13314264kB, anon-rss:3085924kB, file-rss:0kB, shmem-rss:9716kB, UID:1000 pgtables:8536kB oom_score_adj:0 -- You are receiving this mail because: You are watching all bug changes.
