[valgrind] [Bug 497432] Feature Request: Automated Snapshot Generation in Callgrind on Process Termination
https://bugs.kde.org/show_bug.cgi?id=497432 Elie changed: What|Removed |Added CC||ekas...@live.com -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 497432] New: Feature Request: Automated Snapshot Generation in Callgrind on Process Termination
https://bugs.kde.org/show_bug.cgi?id=497432 Bug ID: 497432 Summary: Feature Request: Automated Snapshot Generation in Callgrind on Process Termination Classification: Developer tools Product: valgrind Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: callgrind Assignee: josef.weidendor...@gmx.de Reporter: ekas...@live.com Target Milestone: --- Dear Valgrind Development Team, I hope this message finds you well. I am a frequent user of Callgrind for performance profiling and greatly appreciate the tool’s flexibility and robustness. However, I have encountered a scenario where I believe a new feature could significantly enhance its usability. Proposed Feature: I propose adding an optional capability for Callgrind to automatically save a snapshot of profiling data upon the monitored process’s termination (normal or abnormal). This feature could be controlled via a command-line option or environment variable, such as --auto-dump-on-exit, and applied selectively using existing NPID control mechanisms. Use Case: In workflows where applications may terminate unexpectedly (e.g., due to crashes or external signals), the current manual invocation of CALLGRIND_DUMP_STATS can result in missed profiling opportunities. Automating this step would ensure critical profiling data is captured without requiring changes to the application code or extensive wrapper scripts. Feasibility: Given that Callgrind already supports NPID-based control, implementing this feature seems feasible by extending its termination handling logic. Users could opt-in to this behavior only for specific processes of interest to avoid unnecessary data generation. Benefits: -Ensures profiling data is not lost due to unforeseen process terminations. -Reduces the need for custom instrumentation or external monitoring scripts. -Enhances user control while maintaining Callgrind’s efficiency. I would be happy to discuss this further or provide additional examples and use cases. If this feature aligns with the tool’s development goals. Thank you for considering this request, and I look forward to your feedback. Best regards, Elie Expert Performance Test Engineer -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 469660] New: Lightly
https://bugs.kde.org/show_bug.cgi?id=469660 Bug ID: 469660 Summary: Lightly Classification: Applications Product: systemsettings Version: 5.27.3 Platform: unspecified OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: gavin.e...@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: I tried to use the lightly qt style by https://github.com/Luwx/Lightly The crash can be reproduced every time. -- Backtrace: Application: System Settings (systemsettings), signal: Segmentation fault [KCrash Handler] #4 0x7f8f23f31d60 in KDecoration2::Decoration::shadow() const () from /lib64/libkdecorations2.so.5 #5 0x7f8f23ac3ef1 in ?? () from /usr/lib64/qt5/qml/org/kde/kwin/private/kdecoration/libkdecorationprivatedeclarative.so #6 0x7f8f76287368 in QQuickItem::event(QEvent*) () from /lib64/libQt5Quick.so.5 #7 0x7f8f78ba51ae in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /lib64/libQt5Widgets.so.5 #8 0x7f8f77eec978 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /lib64/libQt5Core.so.5 #9 0x7f8f7629e773 in QQuickWindowPrivate::sendHoverEvent(QEvent::Type, QQuickItem*, QPointF const&, QPointF const&, QFlags, unsigned long, bool) () from /lib64/libQt5Quick.so.5 #10 0x7f8f7629f7ad in QQuickWindowPrivate::deliverHoverEvent(QQuickItem*, QPointF const&, QPointF const&, QFlags, unsigned long, bool&) () from /lib64/libQt5Quick.so.5 #11 0x7f8f7629ee96 in QQuickWindowPrivate::deliverHoverEvent(QQuickItem*, QPointF const&, QPointF const&, QFlags, unsigned long, bool&) () from /lib64/libQt5Quick.so.5 #12 0x7f8f7629ee96 in QQuickWindowPrivate::deliverHoverEvent(QQuickItem*, QPointF const&, QPointF const&, QFlags, unsigned long, bool&) () from /lib64/libQt5Quick.so.5 #13 0x7f8f7629ee96 in QQuickWindowPrivate::deliverHoverEvent(QQuickItem*, QPointF const&, QPointF const&, QFlags, unsigned long, bool&) () from /lib64/libQt5Quick.so.5 #14 0x7f8f7629ee96 in QQuickWindowPrivate::deliverHoverEvent(QQuickItem*, QPointF const&, QPointF const&, QFlags, unsigned long, bool&) () from /lib64/libQt5Quick.so.5 #15 0x7f8f7629ee96 in QQuickWindowPrivate::deliverHoverEvent(QQuickItem*, QPointF const&, QPointF const&, QFlags, unsigned long, bool&) () from /lib64/libQt5Quick.so.5 #16 0x7f8f7629ee96 in QQuickWindowPrivate::deliverHoverEvent(QQuickItem*, QPointF const&, QPointF const&, QFlags, unsigned long, bool&) () from /lib64/libQt5Quick.so.5 #17 0x7f8f7629ee96 in QQuickWindowPrivate::deliverHoverEvent(QQuickItem*, QPointF const&, QPointF const&, QFlags, unsigned long, bool&) () from /lib64/libQt5Quick.so.5 #18 0x7f8f7629ee96 in QQuickWindowPrivate::deliverHoverEvent(QQuickItem*, QPointF const&, QPointF const&, QFlags, unsigned long, bool&) () from /lib64/libQt5Quick.so.5 #19 0x7f8f7629ee96 in QQuickWindowPrivate::deliverHoverEvent(QQuickItem*, QPointF const&, QPointF const&, QFlags, unsigned long, bool&) () from /lib64/libQt5Quick.so.5 #20 0x7f8f7629ee96 in QQuickWindowPrivate::deliverHoverEvent(QQuickItem*, QPointF const&, QPointF const&, QFlags, unsigned long, bool&) () from /lib64/libQt5Quick.so.5 #21 0x7f8f7629ee96 in QQuickWindowPrivate::deliverHoverEvent(QQuickItem*, QPointF const&, QPointF const&, QFlags, unsigned long, bool&) () from /lib64/libQt5Quick.so.5 #22 0x7f8f7629ee96 in QQuickWindowPrivate::deliverHoverEvent(QQuickItem*, QPointF const&, QPointF const&, QFlags, unsigned long, bool&) () from /lib64/libQt5Quick.so.5 #23 0x7f8f7629ee96 in QQuickWindowPrivate::deliverHoverEvent(QQuickItem*, QPointF const&, QPointF const&, QFlags, unsigned long, bool&) () from /lib64/libQt5Quick.so.5 #24 0x7f8f7629ee96 in QQuickWindowPrivate::deliverHoverEvent(QQuickItem*, QPointF const&, QPointF const&, QFlags, unsigned long, bool&) () from /lib64/libQt5Quick.so.5 #25 0x7f8f7629ee96 in QQuickWindowPrivate::deliverHoverEvent(QQuickItem*, QPointF const&, QPointF const&, QFlags, unsigned long, bool&) () from /lib64/libQt5Quick.so.5 #26 0x7f8f7629ee96 in QQuickWindowPrivate::deliverHoverEvent(QQuickItem*, QPointF const&, QPointF const&, QFlags, unsigned long, bool&) () from /lib64/libQt5Quick.so.5 #27 0x7f8f7629ee96 in QQuickWindowPrivate::deliverHoverEvent(QQuickItem*, QPointF const&, QPointF const&, QFlags, unsigned long, bool&) () from /lib64/libQt5Quick.so.5 #28 0x7f8f7629ee96 in QQuickWindowPrivate::deliverHoverEvent(QQuickItem*, QPointF const&, QPointF const&, QFlags, unsigned long, bool&) () from /lib64/libQt5Quick.so.5 #29 0x7f8f7629ee96 in QQuickWindowPriva
[plasmashell] [Bug 489125] New: powerdevil crashes plasmashell(panel)
https://bugs.kde.org/show_bug.cgi?id=489125 Bug ID: 489125 Summary: powerdevil crashes plasmashell(panel) Classification: Plasma Product: plasmashell Version: 6.1.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Panel Assignee: plasma-b...@kde.org Reporter: walkonfir...@yahoo.com CC: niccolo.venera...@gmail.com Target Milestone: 1.0 Hello , Powerdevil crashes plasmashell panel, when u hover with the mouse over the icon or press few times on the power management icon then it randomly freezes. Debug Result . [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib64/libthread_db.so.1". Core was generated by `/usr/bin/plasmashell --no-respawn'. Program terminated with signal SIGSEGV, Segmentation fault. #0 0x74dc05115cff in KCrash::defaultCrashHandler(int) () from /lib64/libKF6Crash.so.6 [Current thread is 1 (Thread 0x74dbfe082b00 (LWP 2506))] (gdb) q elias@weedbox:~/kde/usr/bin> -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 493120] New: mouse freezes for 0.5sec while moving .
https://bugs.kde.org/show_bug.cgi?id=493120 Bug ID: 493120 Summary: mouse freezes for 0.5sec while moving . Classification: Plasma Product: kwin Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: input Assignee: kwin-bugs-n...@kde.org Reporter: walkonfir...@yahoo.com Target Milestone: --- Hello , STEPS TO REPRODUCE 1. Install Age Of Mythology Retold , Age Of Empire 3:DE 2. Open A Skirmish Map , PLay, Move the mouse it freezes for 0.5second then move again , u will notice it easy. 3. OBSERVED RESULT Specs EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: macOS: (available in the Info Center app, or by running `kinfo` in a terminal window) Linux/KDE Plasma: KDE Plasma Version: tested in 6.1.x , 6.2- Beta KDE Frameworks Version: Qt Version: 6.7 ADDITIONAL INFORMATION my system spec , currently running gnome elias@WeedBox:~> inxi -S -G System: Host: WeedBox Kernel: 6.10.10-lqx1-1-liquorix arch: x86_64 bits: 64 Desktop: GNOME v: 46.4 Distro: openSUSE Tumbleweed 20240912 Graphics: Device-1: NVIDIA AD102 [GeForce RTX 4090] driver: nvidia v: 560.35.03 Display: wayland server: X.org v: 1.21.1.12 with: Xwayland v: 24.1.2 compositor: gnome-shell driver: X: loaded: nvidia gpu: nvidia resolution: 3840x2160 API: EGL v: 1.5 drivers: nvidia,swrast platforms: gbm,wayland,x11,surfaceless,device API: OpenGL v: 4.6.0 compat-v: 4.5 vendor: nvidia mesa v: 560.35.03 renderer: NVIDIA GeForce RTX 4090/PCIe/SSE2 API: Vulkan v: 1.3.290 drivers: N/A surfaces: xcb,xlib,wayland elias@WeedBox:~> inxi -S -G -C System: Host: WeedBox Kernel: 6.10.10-lqx1-1-liquorix arch: x86_64 bits: 64 Desktop: GNOME v: 46.4 Distro: openSUSE Tumbleweed 20240912 CPU: Info: 16-core model: AMD Ryzen 9 7950X bits: 64 type: MT MCP cache: L2: 16 MiB Speed (MHz): avg: 5500 min/max: 545/6070 cores: 1: 5500 2: 5500 3: 5500 4: 5500 5: 5500 6: 5500 7: 5500 8: 5500 9: 5500 10: 5500 11: 5500 12: 5500 13: 5500 14: 5500 15: 5500 16: 5500 17: 5500 18: 5500 19: 5500 20: 5500 21: 5500 22: 5500 23: 5500 24: 5500 25: 5500 26: 5500 27: 5500 28: 5500 29: 5500 30: 5500 31: 5500 32: 5500 Graphics: Device-1: NVIDIA AD102 [GeForce RTX 4090] driver: nvidia v: 560.35.03 Display: wayland server: X.org v: 1.21.1.12 with: Xwayland v: 24.1.2 compositor: gnome-shell driver: X: loaded: nvidia gpu: nvidia resolution: 3840x2160 API: EGL v: 1.5 drivers: nvidia,swrast platforms: gbm,wayland,x11,surfaceless,device API: OpenGL v: 4.6.0 compat-v: 4.5 vendor: nvidia mesa v: 560.35.03 renderer: NVIDIA GeForce RTX 4090/PCIe/SSE2 API: Vulkan v: 1.3.290 drivers: N/A surfaces: xcb,xlib,wayland elias@WeedBox:~> Note : This was tested on different kernel , also tested with Mesa-nvidia driver and nvidia driver both from opensuse and nvidia . Works fine under X11 . -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 483067] Fractional scaling causes unwanted mouse acceleration in games
https://bugs.kde.org/show_bug.cgi?id=483067 Elie Dadde changed: What|Removed |Added Resolution|WAITINGFORINFO |FIXED --- Comment #4 from Elie Dadde --- (In reply to Zamundaaa from comment #3) > What do you have the scaling setting for legacy applications set to? "Apply > scaling themselves", or "scaled by the system"? Does changing it make a > difference? Apply scaling themselves , on my system . -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 483067] Fractional scaling causes unwanted mouse acceleration in games
https://bugs.kde.org/show_bug.cgi?id=483067 --- Comment #5 from Elie Dadde --- (In reply to Elie Dadde from comment #4) > (In reply to Zamundaaa from comment #3) > > What do you have the scaling setting for legacy applications set to? "Apply > > scaling themselves", or "scaled by the system"? Does changing it make a > > difference? > > Apply scaling themselves , on my system . Changing it do make a difference but u can't play at 4K Anymore games resolution goes down to 2k . -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 483067] Fractional scaling causes unwanted mouse acceleration in games
https://bugs.kde.org/show_bug.cgi?id=483067 --- Comment #16 from Elie Dadde --- (In reply to Berwick from comment #15) > Is there a link to the ticket about the mouse freezing? I've net experienced > that, just the unexpected acceleration. I've not tested the new changes to > Kwin yet as I'm not great at building it myself. > > If the mouse freezing is separate to the acceleration, we can move the > conversation to that ticket? i did open the ticket ,however i didn't keep track of it , both issues seems related though , as 100% scaling do fix the mouse freezing , and i did build kwin with zamunda's changes , didn't really have any improving . -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 483067] Fractional scaling causes unwanted mouse acceleration in games
https://bugs.kde.org/show_bug.cgi?id=483067 --- Comment #13 from Elie Dadde --- (In reply to Zamundaaa from comment #12) > Git commit 6d633e4bd19a32390eb0da26a50e881eb7fbb36d by Xaver Hugl. > Committed on 04/10/2024 at 23:41. > Pushed by zamundaaa into branch 'Plasma/6.2'. > > wayland/relativepointer: don't scale non-accelerated pointer values > > Normally, pointer values are in logical units, which get implicitly scaled > with the scale of > the screen, so scaling them when scaling Xwayland makes sense. If the > pointer moves too fast > for the user with that scaling, they will simply use the libinput pointer > acceleration setting > to reduce that speed in a manner that's uniform for all their screens. > However, unaccelerated values are not affected by that setting, and thus > they should also not > be affected by the screen's scale. This commit removes that scaling for > Xwayland, which matches > SDL's usage of the value in Wayland native mode and brings it in line with > user expectations. > > > (cherry picked from commit 47f800c12786d4b04a2e812785784d41e39bbfbc) > > Co-authored-by: Xaver Hugl > > M +2-2src/wayland/relativepointer_v1.cpp > > https://invent.kde.org/plasma/kwin/-/commit/ > 6d633e4bd19a32390eb0da26a50e881eb7fbb36d update on the issue , this didn't fix the behavior inside some games , scaling on 4k mouse still causes mouses acceleration freeze . -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 483067] Fractional scaling causes unwanted mouse acceleration in games
https://bugs.kde.org/show_bug.cgi?id=483067 --- Comment #14 from Elie Dadde --- (In reply to Elie Dadde from comment #13) > (In reply to Zamundaaa from comment #12) > > Git commit 6d633e4bd19a32390eb0da26a50e881eb7fbb36d by Xaver Hugl. > > Committed on 04/10/2024 at 23:41. > > Pushed by zamundaaa into branch 'Plasma/6.2'. > > > > wayland/relativepointer: don't scale non-accelerated pointer values > > > > Normally, pointer values are in logical units, which get implicitly scaled > > with the scale of > > the screen, so scaling them when scaling Xwayland makes sense. If the > > pointer moves too fast > > for the user with that scaling, they will simply use the libinput pointer > > acceleration setting > > to reduce that speed in a manner that's uniform for all their screens. > > However, unaccelerated values are not affected by that setting, and thus > > they should also not > > be affected by the screen's scale. This commit removes that scaling for > > Xwayland, which matches > > SDL's usage of the value in Wayland native mode and brings it in line with > > user expectations. > > > > > > (cherry picked from commit 47f800c12786d4b04a2e812785784d41e39bbfbc) > > > > Co-authored-by: Xaver Hugl > > > > M +2-2src/wayland/relativepointer_v1.cpp > > > > https://invent.kde.org/plasma/kwin/-/commit/ > > 6d633e4bd19a32390eb0da26a50e881eb7fbb36d > > update on the issue , this didn't fix the pointer behavior inside some games > , > scaling still causes mouse acceleration issues . -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 483067] Fractional scaling causes unwanted mouse acceleration in games
https://bugs.kde.org/show_bug.cgi?id=483067 --- Comment #18 from Elie Dadde --- (In reply to Zamundaaa from comment #17) > This bug report and the fix are not about any freezes. Your problem is > something different. put the scaling at 100% , fixes the mouse freeze , somehow it should be related . -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 483067] Fractional scaling causes unwanted mouse acceleration in games
https://bugs.kde.org/show_bug.cgi?id=483067 Elie Dadde changed: What|Removed |Added CC||walkonfir...@yahoo.com --- Comment #2 from Elie Dadde --- i can confirm that i always thought that was kwin issue , i have another bug reported about the mouse freeze in some games , gnome and x11(kde) don't suffer from that , it has to be something with kwin , set scaling to 100% fixes the issue indeed . -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 493120] mouse freezes for 0.5sec while moving .
https://bugs.kde.org/show_bug.cgi?id=493120 --- Comment #3 from Elie Dadde --- (In reply to Elie Dadde from comment #2) > (In reply to Vlad Zahorodnii from comment #1) > > If you force software cursor by setting the KWIN_FORCE_SW_CURSOR=1 envvar, > > is it better? > > Updating kde 6.2 at the moment , will recheck once the DE is up again and > will update the post . Nope , didn't help. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 493120] mouse freezes for 0.5sec while moving .
https://bugs.kde.org/show_bug.cgi?id=493120 --- Comment #2 from Elie Dadde --- (In reply to Vlad Zahorodnii from comment #1) > If you force software cursor by setting the KWIN_FORCE_SW_CURSOR=1 envvar, > is it better? Updating kde 6.2 at the moment , will recheck once the DE is up again and will update the post . -- You are receiving this mail because: You are watching all bug changes.
