[plasmashell] [Bug 488104] New: support systemd-homed's "forget keys on suspend"
https://bugs.kde.org/show_bug.cgi?id=488104 Bug ID: 488104 Summary: support systemd-homed's "forget keys on suspend" Classification: Plasma Product: plasmashell Version: master Platform: unspecified OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: Session Management Assignee: plasma-b...@kde.org Reporter: kdeb...@hirebzs.mozmail.com CC: natalie_clar...@yahoo.de Target Milestone: 1.0 SUMMARY As a user I would like to improve the security posture of my KDE-installed system. One way to achieve this is to use systemd-homed to fully encrypt my home directory, and have it automatically locked with the keys purged from memory when the system suspends, by using systemd-homed's "[forget keys on suspend](https://www.freedesktop.org/software/systemd/man/latest/pam_systemd_home.html)" feature. GDM is already [working](https://gitlab.gnome.org/GNOME/gdm/-/merge_requests/251) on supporting this, would love to see it in SDDM/KDE as well. STEPS TO REPRODUCE 1. user creates encrypted home directory using systemd-homed and enables relevant setting in pam_systemd_homed 2. user suspends active session 3. user resumes session from suspended state EXPECTED RESULT user's home directory locked and keys purged from memory; user be asked to authenticate again to unlock home directory ADDITIONAL INFORMATION looks like there is some upstream work pending [this PR](https://github.com/systemd/systemd/pull/31796) targeting systemd v256 but the DM & shell bits should be ready for work -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 467237] SIGSEGV in kscreen_osd_ser on a Wayland session
https://bugs.kde.org/show_bug.cgi?id=467237 kdeb...@hirebzs.mozmail.com changed: What|Removed |Added Summary|SIGSEGV in kscreen_osd_ser |SIGSEGV in kscreen_osd_ser ||on a Wayland session Keywords||drkonqi, wayland -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 467237] SIGSEGV in kscreen_osd_ser
https://bugs.kde.org/show_bug.cgi?id=467237 --- Comment #4 from kdeb...@hirebzs.mozmail.com --- Created attachment 157211 --> https://bugs.kde.org/attachment.cgi?id=157211&action=edit drkonqi crash info -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 467237] SIGSEGV in kscreen_osd_ser
https://bugs.kde.org/show_bug.cgi?id=467237 --- Comment #3 from kdeb...@hirebzs.mozmail.com --- Created attachment 157210 --> https://bugs.kde.org/attachment.cgi?id=157210&action=edit link to core file -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 467237] SIGSEGV in kscreen_osd_ser
https://bugs.kde.org/show_bug.cgi?id=467237 --- Comment #2 from kdeb...@hirebzs.mozmail.com --- Operating System: Fedora Linux 37 KDE Plasma Version: 5.27.2 KDE Frameworks Version: 5.103.0 Qt Version: 5.15.8 Kernel Version: 6.1.14-200.fc37.x86_64 (64-bit) Graphics Platform: Wayland Processors: 16 × AMD Ryzen 7 PRO 6850U with Radeon Graphics Memory: 14.4 GiB of RAM Graphics Processor: AMD Radeon Graphics 680M -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 467237] SIGSEGV in kscreen_osd_ser
https://bugs.kde.org/show_bug.cgi?id=467237 --- Comment #1 from kdeb...@hirebzs.mozmail.com --- Created attachment 157209 --> https://bugs.kde.org/attachment.cgi?id=157209&action=edit system journal -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 467237] New: SIGSEGV in kscreen_osd_ser
https://bugs.kde.org/show_bug.cgi?id=467237 Bug ID: 467237 Summary: SIGSEGV in kscreen_osd_ser Classification: Plasma Product: KScreen Version: 5.27.2 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: OSD Assignee: kscreen-bugs-n...@kde.org Reporter: kdeb...@hirebzs.mozmail.com Target Milestone: --- Created attachment 157208 --> https://bugs.kde.org/attachment.cgi?id=157208&action=edit full decoded backtrace SUMMARY Found this crash in the log, don't remember what caused it but full backtrace, syslog & additional info attached SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 467234] kwin_wayland SIGSEGV in KWaylandServer::OutputInterface::handle()
https://bugs.kde.org/show_bug.cgi?id=467234 --- Comment #3 from kdeb...@hirebzs.mozmail.com --- Created attachment 157207 --> https://bugs.kde.org/attachment.cgi?id=157207&action=edit link to core file -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 467234] kwin_wayland SIGSEGV in KWaylandServer::OutputInterface::handle()
https://bugs.kde.org/show_bug.cgi?id=467234 kdeb...@hirebzs.mozmail.com changed: What|Removed |Added Summary|kwin_wayland SIGSEGV|kwin_wayland SIGSEGV in ||KWaylandServer::OutputInter ||face::handle() -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 467234] kwin_wayland SIGSEGV
https://bugs.kde.org/show_bug.cgi?id=467234 --- Comment #2 from kdeb...@hirebzs.mozmail.com --- Created attachment 157204 --> https://bugs.kde.org/attachment.cgi?id=157204&action=edit drkonqi -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 467234] kwin_wayland SIGSEGV
https://bugs.kde.org/show_bug.cgi?id=467234 --- Comment #1 from kdeb...@hirebzs.mozmail.com --- Created attachment 157203 --> https://bugs.kde.org/attachment.cgi?id=157203&action=edit decoded backtrace -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 467234] New: kwin_wayland SIGSEGV
https://bugs.kde.org/show_bug.cgi?id=467234 Bug ID: 467234 Summary: kwin_wayland SIGSEGV Classification: Plasma Product: kwin Version: 5.27.2 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: wayland-generic Assignee: kwin-bugs-n...@kde.org Reporter: kdeb...@hirebzs.mozmail.com Target Milestone: --- Created attachment 157202 --> https://bugs.kde.org/attachment.cgi?id=157202&action=edit system journal SUMMARY System is a laptop with an external monitor attached on HDMI port; I was not at the computer when the crash happened, and certainly wasn't interacting with it. When I came back to it I found that kwin_wayland had crashed and restarted, so I'm afraid I can't provide exact events leading up to the crash, perhaps it has to do with screenlocking. But I've attached core dump, back trace & libs info as found by drkonqi and system journal around the crash. STEPS TO REPRODUCE unsure OBSERVED RESULT kwin_wayland crashed EXPECTED RESULT kwin_wayland should not crash SOFTWARE/OS VERSIONS Operating System: Fedora Linux 37 KDE Plasma Version: 5.27.2 KDE Frameworks Version: 5.103.0 Qt Version: 5.15.8 Kernel Version: 6.1.14-200.fc37.x86_64 (64-bit) Graphics Platform: Wayland Processors: 16 × AMD Ryzen 7 PRO 6850U with Radeon Graphics Memory: 14.4 GiB of RAM Graphics Processor: AMD Radeon Graphics 680M -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 467230] Application windows moved to the wrong physical monitor on resume if suspend was done by closing the lid
https://bugs.kde.org/show_bug.cgi?id=467230 --- Comment #1 from kdeb...@hirebzs.mozmail.com --- how can I get `kscreen-doctor` to output EDID info? I tried following https://notmart.org/blog/2023/02/how-to-report-multiscreen-bugs/ but if I just run `kscreen-doctor` it prints nothing to the console -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 467230] New: Application windows moved to the wrong physical monitor on resume if suspend was done by closing the lid
https://bugs.kde.org/show_bug.cgi?id=467230 Bug ID: 467230 Summary: Application windows moved to the wrong physical monitor on resume if suspend was done by closing the lid Classification: Plasma Product: kwin Version: 5.27.2 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: multi-screen Assignee: kwin-bugs-n...@kde.org Reporter: kdeb...@hirebzs.mozmail.com Target Milestone: --- My laptop is attached to one other monitor on the HDMI port, with the laptop's builtin screen set as the primary monitor. When I suspend by closing the lid, application windows (tried Firefox and Logseq, both installed via Flatpak) placed on the external screen before suspend would get restored to the builtin screen. But if I suspend by using the "sleep" button in kickstart, application windows are restored to the correct physical monitor. STEPS TO REPRODUCE 1. attach external monitor, place some windows there 2. close lid of laptop 3. open lid OBSERVED RESULT application windows assigned to the external screen before suspend are restored to the builtin screen EXPECTED RESULT windows assigned to the external screen before suspend are restored to the external screen SOFTWARE/OS VERSIONS Operating System: Fedora Linux 37 Kinoite KDE Plasma Version: 5.27.2 KDE Frameworks Version: 5.103.0 Qt Version: 5.15.8 Kernel Version: 6.1.14-200.fc37.x86_64 (64-bit) Graphics Platform: Wayland Processors: 16 × AMD Ryzen 7 PRO 6850U with Radeon Graphics Memory: 14.4 GiB of RAM Graphics Processor: AMD Radeon Graphics 680M Manufacturer: LENOVO System Version: ThinkPad T14s Gen 3 ADDITIONAL INFORMATION ❯ kscreen-doctor -o took 99ms Output: 1 eDP-1 enabled connected priority 1 Panel Modes: 0:1920x1200@60*! 1:1920x1080@60 2:1600x1200@60 3:1680x1050@60 4:1280x1024@60 5:1440x900@60 6:1280x800@60 7:1280x720@60 8:1024x768@60 9:800x600@60 10:640x480@60 11:1600x1200@60 12:1280x1024@60 13:1024x768@60 14:1920x1200@60 15:1280x800@60 16:1920x1080@60 17:1600x900@60 18:1368x768@60 19:1280x720@60 Geometry: 0,0 1920x1200 Scale: 1 Rotation: 1 Overscan: 0 Vrr: incapable RgbRange: unknown Output: 2 HDMI-A-1 enabled connected priority 2 HDMI Modes: 0:1920x1080@60*! 1:1920x1080@75 2:1920x1080@60 3:1920x1080@60 4:1920x1080@50 5:1680x1050@60 6:1280x1024@75 7:1280x1024@60 8:1440x900@60 9:1280x960@60 10:1280x800@60 11:1280x720@60 12:1280x720@60 13:1280x720@60 14:1280x720@50 15:1024x768@75 16:1024x768@70 17:1024x768@60 18:832x624@75 19:800x600@75 20:800x600@72 21:800x600@60 22:800x600@56 23:720x576@50 24:720x576@50 25:720x576@50 26:720x480@60 27:720x480@60 28:720x480@60 29:720x480@60 30:720x480@60 31:640x480@75 32:640x480@73 33:640x480@67 34:640x480@60 35:640x480@60 36:640x480@60 37:720x400@70 38:1280x1024@60 39:1024x768@60 40:1280x800@60 41:1920x1080@60 42:1600x900@60 43:1368x768@60 44:1280x720@60 Geometry: 1920,0 1920x1080 Scale: 1 Rotation: 1 Overscan: 0 Vrr: Never RgbRange: unknown -- You are receiving this mail because: You are watching all bug changes.
[Craft] [Bug 453950] The MSBuild Craft build system crashes when the build time is MinSizeRel
https://bugs.kde.org/show_bug.cgi?id=453950 --- Comment #1 from kdeb...@noahandrews.me --- Merge request submitted here: https://invent.kde.org/packaging/craft/-/merge_requests/76 -- You are receiving this mail because: You are watching all bug changes.
[Craft] [Bug 453950] The MSBuild Craft build system crashes when the build time is MinSizeRel
https://bugs.kde.org/show_bug.cgi?id=453950 kdeb...@noahandrews.me changed: What|Removed |Added CC||kdeb...@noahandrews.me -- You are receiving this mail because: You are watching all bug changes.
[Craft] [Bug 453950] New: The MSBuild Craft build system crashes when the build time is MinSizeRel
https://bugs.kde.org/show_bug.cgi?id=453950 Bug ID: 453950 Summary: The MSBuild Craft build system crashes when the build time is MinSizeRel Product: Craft Version: master Platform: Microsoft Windows OS: Microsoft Windows Status: REPORTED Severity: normal Priority: NOR Component: Core Assignee: vonr...@kde.org Reporter: kdeb...@noahandrews.me CC: kde-wind...@kde.org Target Milestone: --- SUMMARY When trying to build KDE Connect on Windows using MSVC for the first time, the build failed because liblzma apparently specified a build type of MinSizeRel, which the MSBuild build system does not support. STEPS TO REPRODUCE 1. Follow the steps to install Craft and build KDE Connect on Windows using MSVC: https://community.kde.org/KDEConnect/Build_Windows OBSERVED RESULT Relevant log output: *** Handling package: libs/liblzma, action: all *** *** Action: fetch-binary for libs/liblzma *** Could not find libs/liblzma=5.2.3 in https://files.kde.org/craft/master/22.05/windows/msvc2019_64/cl/MinSizeRel *** libs/liblzma not found in cache *** *** Action: fetch for libs/liblzma *** *** Action: unpack for libs/liblzma *** Please enable Windows 10 development mode to enable support for symlinks. This will enable faster extractions. https://docs.microsoft.com/en-us/windows/uwp/get-started/enable-your-device-for-development *** Action: compile for libs/liblzma *** entering the source directory! *** Craft all succeeded: libs/liblzma after 0 seconds *** 'MinSizeRel' Traceback (most recent call last): File "C:\CraftRoot\craft\bin\craft.py", line 274, in success = main(timer) File "C:\CraftRoot\craft\bin\craft.py", line 264, in main if not CraftCommands.run(package, action, tempArgs): File "C:\CraftRoot\craft\bin\CraftCommands.py", line 425, in run if not handlePackage(info, action, directTargets=directTargets): File "C:\CraftRoot\craft\bin\CraftCommands.py", line 94, in handlePackage success = doExec(package, action) File "C:\CraftRoot\craft\bin\CraftCommands.py", line 58, in doExec ret = package.instance.runAction(action) File "C:\CraftRoot\craft\bin\Package\PackageBase.py", line 247, in runAction if not getattr(self, step)(): File "C:\CraftRoot\craft\bin\BuildSystem\BuildSystemBase.py", line 89, in compile return configure() and make() File "C:\CraftRoot\craft\bin\BuildSystem\MSBuildBuildSystem.py", line 46, in make buildType =self.buildTypes[self.buildType()] KeyError: 'MinSizeRel' EXPECTED RESULT The software should build successfully SOFTWARE/OS VERSIONS Windows: Windows 11 Pro 21H2 -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 416049] Connect icon in the top bar is invisible in dark mode on MacOS
https://bugs.kde.org/show_bug.cgi?id=416049 Phil KdeBugs changed: What|Removed |Added CC||phil3em...@earthlink.net --- Comment #2 from Phil KdeBugs --- I've been able to reproduce this on macOS 10.15.6 , built from git (aug16,2020) -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 385251] catastrophic memory leak triggered by panel interaction
https://bugs.kde.org/show_bug.cgi?id=385251 --- Comment #11 from Phil KdeBugs --- what extra information can I provide? It locks up, goes into a memory dive quite frequently...! -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 385251] catastrophic memory leak triggered by panel interaction
https://bugs.kde.org/show_bug.cgi?id=385251 --- Comment #9 from Phil KdeBugs --- to be clear - the panel completely locks up. Fortunately , alt-tab can expose a terminal to run the commands. I assumed that was obvious due to the excessive (4GB!) memory use. Callgrind slows the execution such, I waited until after the shell get's started to get an instrumentation sample. Fortunately, plasmashell can be restarted frequently without interrupting my work... -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 385251] catastrophic memory leak triggered by panel interaction
https://bugs.kde.org/show_bug.cgi?id=385251 --- Comment #8 from Phil KdeBugs --- if you want a tar.gz of of text files I can send, but not sure how to upload so I put them in a pdf. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 385251] catastrophic memory leak triggered by panel interaction
https://bugs.kde.org/show_bug.cgi?id=385251 --- Comment #7 from Phil KdeBugs --- Created attachment 108235 --> https://bugs.kde.org/attachment.cgi?id=108235&action=edit a collection of callgrind reports Collection of callgrind before and after memory leak runaway, all the way to 4GB!! -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 352742] Custom allocator using sbrk() fails after about 800MB when running under memcheck
https://bugs.kde.org/show_bug.cgi?id=352742 Phil KdeBugs changed: What|Removed |Added CC||phil3em...@earthlink.net --- Comment #7 from Phil KdeBugs --- Created attachment 108234 --> https://bugs.kde.org/attachment.cgi?id=108234&action=edit collectiion of callgrind reports Collection of callgrind before and after memory leak runaway, all the way to 4GB!! -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 385251] catastrophic memory leak triggered by panel interaction
https://bugs.kde.org/show_bug.cgi?id=385251 --- Comment #6 from Phil KdeBugs --- Hi, OK I recompiled valgrind to make the RLIMIT 256MB (vs 8MB default) to raise the limit before we get brk errors. I turned on the instrumentation after the start up sequence. I then took dumps before and after the perceived leak. The attachments include: a) all the error output from the process b) callgrind dumps from before (1) and after (2..7) upto 4GB of memory c) the final stack trace from callgrind. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 385251] catastrophic memory leak triggered by panel interaction
https://bugs.kde.org/show_bug.cgi?id=385251 Phil KdeBugs changed: What|Removed |Added Attachment #108113|0 |1 is obsolete|| CC||phil3em...@earthlink.net --- Comment #4 from Phil KdeBugs --- Created attachment 108230 --> https://bugs.kde.org/attachment.cgi?id=108230&action=edit memory use, and gdb stack trace plasmashell This has the memory use (2.1G) on the first line, followed by GDB stacktrace following clicking on a firefox instance (20 panes) -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 385469] New: plasma discover crashes on start
https://bugs.kde.org/show_bug.cgi?id=385469 Bug ID: 385469 Summary: plasma discover crashes on start Product: Discover Version: 5.8.5 Platform: Debian stable OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: discover Assignee: aleix...@kde.org Reporter: phil3em...@earthlink.net Target Milestone: --- Application: plasma-discover (5.8.5) Qt Version: 5.7.1 Frameworks Version: 5.28.0 Operating System: Linux 4.9.0-3-amd64 x86_64 Distribution: Debian GNU/Linux 9.1 (stretch) -- Information about the crash: occurs everytime with system in current state. The crash can be reproduced every time. -- Backtrace: Application: Discover (plasma-discover), signal: Aborted Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7fa90b007d80 (LWP 12590))] Thread 8 (Thread 0x7fa8d91a9700 (LWP 12697)): #0 0x7fa9078ae71d in read () at ../sysdeps/unix/syscall-template.S:84 #1 0x7fa900bd5073 in () at /usr/lib/x86_64-linux-gnu/tls/libnvidia-tls.so.375.82 #2 0x7fa902fd1d40 in read (__nbytes=16, __buf=0x7fa8d91a8be0, __fd=) at /usr/include/x86_64-linux-gnu/bits/unistd.h:44 #3 0x7fa902fd1d40 in g_wakeup_acknowledge (wakeup=0x7fa8d40025c0) at ././glib/gwakeup.c:210 #4 0x7fa902f8d4be in g_main_context_check (context=context@entry=0x55850b1af960, max_priority=2147483647, fds=fds@entry=0x7fa8cc0010c0, n_fds=n_fds@entry=1) at ././glib/gmain.c:3707 #5 0x7fa902f8d994 in g_main_context_iterate (context=0x55850b1af960, block=block@entry=1, dispatch=dispatch@entry=1, self=) at ././glib/gmain.c:3926 #6 0x7fa902f8dd82 in g_main_loop_run (loop=0x55850b96ebf0) at ././glib/gmain.c:4125 #7 0x7fa8db226656 in gdbus_shared_thread_func (user_data=0x55850b97b5d0) at ././gio/gdbusprivate.c:247 #8 0x7fa902fb53d5 in g_thread_proxy (data=0x55850b98a8f0) at ././glib/gthread.c:784 #9 0x7fa9051c2494 in start_thread (arg=0x7fa8d91a9700) at pthread_create.c:333 #10 0x7fa9078bbaff in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:97 Thread 7 (Thread 0x7fa8d99aa700 (LWP 12696)): #0 0x7fa9078b26ad in poll () at ../sysdeps/unix/syscall-template.S:84 #1 0x7fa902f8d9f6 in g_main_context_poll (priority=, n_fds=1, fds=0x7fa8d8c0, timeout=, context=0x55850b987d40) at ././glib/gmain.c:4228 #2 0x7fa902f8d9f6 in g_main_context_iterate (context=context@entry=0x55850b987d40, block=block@entry=1, dispatch=dispatch@entry=1, self=) at ././glib/gmain.c:3924 #3 0x7fa902f8db0c in g_main_context_iteration (context=0x55850b987d40, may_block=may_block@entry=1) at ././glib/gmain.c:3990 #4 0x7fa902f8db51 in glib_worker_main (data=) at ././glib/gmain.c:5783 #5 0x7fa902fb53d5 in g_thread_proxy (data=0x55850b98a8a0) at ././glib/gthread.c:784 #6 0x7fa9051c2494 in start_thread (arg=0x7fa8d99aa700) at pthread_create.c:333 #7 0x7fa9078bbaff in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:97 Thread 6 (Thread 0x7fa8e77fe700 (LWP 12661)): #0 0x7ffc53515b12 in __vdso_clock_gettime (clock=1, ts=0x7fa8e77fda20) at ./arch/x86/entry/vdso/vclock_gettime.c:269 #1 0x7fa9078c8996 in __GI___clock_gettime (clock_id=clock_id@entry=1, tp=tp@entry=0x7fa8e77fda20) at ../sysdeps/unix/clock_gettime.c:115 #2 0x7fa908357091 in qt_clock_gettime (ts=0x7fa8e77fda20, clock=) at tools/qelapsedtimer_unix.cpp:109 #3 0x7fa908357091 in do_gettime (frac=, sec=) at tools/qelapsedtimer_unix.cpp:164 #4 0x7fa908357091 in qt_gettime() () at tools/qelapsedtimer_unix.cpp:173 #5 0x7fa9084d3ce9 in QTimerInfoList::updateCurrentTime() (this=this@entry=0x7fa8d4002ed0) at kernel/qtimerinfo_unix.cpp:91 #6 0x7fa9084d4295 in QTimerInfoList::timerWait(timespec&) (this=0x7fa8d4002ed0, tm=...) at kernel/qtimerinfo_unix.cpp:388 #7 0x7fa9084d563e in timerSourcePrepareHelper (timeout=0x7fa8e77fdaf4, src=) at kernel/qeventdispatcher_glib.cpp:132 #8 0x7fa9084d563e in timerSourcePrepare(GSource*, gint*) (source=, timeout=timeout@entry=0x7fa8e77fdaf4) at kernel/qeventdispatcher_glib.cpp:165 #9 0x7fa902f8cedd in g_main_context_prepare (context=context@entry=0x7fa8d40009b0, priority=priority@entry=0x7fa8e77fdb80) at ././glib/gmain.c:3501 #10 0x7fa902f8d91b in g_main_context_iterate (context=context@entry=0x7fa8d40009b0, block=block@entry=1, dispatch=dispatch@entry=1, self=) at ././glib/gmain.c:3909 #11 0x7fa902f8db0c in g_main_context_iteration (context=0x7fa8d40009b0, may_block=may_block@entry=1) at ././glib/gmain.c:3990 #12 0x7fa9084d606b in QEventDispatcherGlib::processEvents(QFlags) (this=0x7fa8d40008e0, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #13 0x7fa90847f9ca in QEventLoop::exec(QFlags) (this=this@entry=0x7fa8e77fdcc0, flags=..., flags@entry=...) at kernel/qeventloop.cpp:212 #14 0x7fa9082ad0f3 in QThread::exec() (this
[plasmashell] [Bug 385251] catastrophic memory leak triggered by panel interaction
https://bugs.kde.org/show_bug.cgi?id=385251 --- Comment #3 from Phil KdeBugs --- I just noticed(!) checking 381000 how old my version seems to be , even though this is clean install of stretch. I'm happy to try a more recent version (if this is fixed), though it does seem quite severe... -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 385251] catastrophic memory leak triggered by panel interaction
https://bugs.kde.org/show_bug.cgi?id=385251 --- Comment #2 from Phil KdeBugs --- Hi, I just installed the dbsyms for the following: libqt5core5a-dbgsym libqt5gui-dbgsym libqt5gui5-dbgsym Version: 5.7.1+dfsg-3+b1 I will try and grab a better annotated trace. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 385251] New: catastrophic memory leak triggered by panel interaction
https://bugs.kde.org/show_bug.cgi?id=385251 Bug ID: 385251 Summary: catastrophic memory leak triggered by panel interaction Product: plasmashell Version: master Platform: Debian stable OS: Linux Status: UNCONFIRMED Severity: critical Priority: NOR Component: Panel Assignee: plasma-b...@kde.org Reporter: phil3em...@earthlink.net Target Milestone: 1.0 Created attachment 108113 --> https://bugs.kde.org/attachment.cgi?id=108113&action=edit stack trace of memory leak Hi, I thought this maybe related to another problem, but some more digging suggests it is more serious. I have a workstation with 256GB of memory and so the extremely severe memory leak would probably disable most machines before time to inspect. I got a hung panel and therefore time to investigate. I disabled the "notifications" which flashes window pictures, but just clicking on an application will reproduce this - many times now. I am running a fresh and up-to-date (30SEP2017) version of debian stretch. I am running the openbox window manager (kwin is too unstable - possible it is the panel causing this). The relevant software (?) is: plasma-workspace 4:5.8.6-2.1 Linux 4.9.0-3-amd64 #1 SMP Debian 4.9.30-2+deb9u5 (2017-09-19) xserver-xorg 1:7.7+19 NVIDIA-SMI 375.66 openbox 3.6.1-4 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 372447] Plasma 5 causes memory leak in Xorg
https://bugs.kde.org/show_bug.cgi?id=372447 --- Comment #8 from Phil KdeBugs --- Created attachment 108109 --> https://bugs.kde.org/attachment.cgi?id=108109&action=edit valgrind , shows massive memory allocation. Does not run sufficiently to profiel Valgrind. Some direction of what to look for would help. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 372447] Plasma 5 causes memory leak in Xorg
https://bugs.kde.org/show_bug.cgi?id=372447 --- Comment #7 from Phil KdeBugs --- Hi, This might help. My workstation has 256GB of memory, so I had plenty of time to catch plasmashell in the act of chewing up all the memory it could. When I first caught it , it has reached 1.5GB!! This is a brand new install of debian stretch, completely up-to-date (30Sep2017). I attached the debug trace when I attached GDB and saw where it was stuck. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 372447] Plasma 5 causes memory leak in Xorg
https://bugs.kde.org/show_bug.cgi?id=372447 Phil KdeBugs changed: What|Removed |Added CC||phil3em...@earthlink.net --- Comment #6 from Phil KdeBugs --- Created attachment 108107 --> https://bugs.kde.org/attachment.cgi?id=108107&action=edit stack trace of memory leak plasma-workspace 4:5.8.6-2.1 xserver-xorg 1:7.7+19 debian stretch -- You are receiving this mail because: You are watching all bug changes.
