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
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 conso
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:
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.
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.
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
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.
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
S
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.
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: 1
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.
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.
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
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
St
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: Mic
https://bugs.kde.org/show_bug.cgi?id=453950
kdeb...@noahandrews.me changed:
What|Removed |Added
CC||kdeb...@noahandrews.me
--
You are rec
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.
https://bugs.kde.org/show_bug.cgi?id=416049
Phil KdeBugs changed:
What|Removed |Added
CC||phil3em...@earthlink.net
--- Comment #2 from
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.
https://bugs.kde.org/show_bug.cgi?id=372447
Phil KdeBugs changed:
What|Removed |Added
CC||phil3em...@earthlink.net
--- Comment #6 from
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
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
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
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
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 s
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
https://bugs.kde.org/show_bug.cgi?id=385251
Phil KdeBugs changed:
What|Removed |Added
Attachment #108113|0 |1
is obsolete
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
https://bugs.kde.org/show_bug.cgi?id=352742
Phil KdeBugs changed:
What|Removed |Added
CC||phil3em...@earthlink.net
--- Comment #7 from
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
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.
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
32 matches
Mail list logo
