[valgrind] [Bug 476548] valgrind 3.22.0 fails on assertion when loading debuginfo file produced by mold

2023-11-18 Thread Jan Palus
https://bugs.kde.org/show_bug.cgi?id=476548 --- Comment #7 from Jan Palus --- Confirmed the fix works fine. Thanks! -- You are receiving this mail because: You are watching all bug changes.

[valgrind] [Bug 476548] valgrind 3.22.0 fails on assertion when loading debuginfo file produced by mold

2023-11-07 Thread Jan Palus
https://bugs.kde.org/show_bug.cgi?id=476548 --- Comment #3 from Jan Palus --- I've done some debugging and possibly found the culprit. The assertion di->rodata_size == a_shdr.sh_size failed because left hand side was 8 while the other was 3. However in readelf output for both strippe

[valgrind] [Bug 476548] New: valgrind 3.22.0 fails on assertion when loading debuginfo file produced by mold

2023-11-04 Thread Jan Palus
https://bugs.kde.org/show_bug.cgi?id=476548 Bug ID: 476548 Summary: valgrind 3.22.0 fails on assertion when loading debuginfo file produced by mold Classification: Developer tools Product: valgrind Version: 3.22 GIT Pla

[konsole] [Bug 443411] Regression: %w and %t placeholders not available in bell notifications

2021-11-02 Thread Jan Palus
https://bugs.kde.org/show_bug.cgi?id=443411 --- Comment #3 from Jan Palus --- Not sure if I follow, do you mean where it's replaced (https://invent.kde.org/frameworks/knotifications/-/commit/e25f1f552a9ce6b684e573f26c82cfc76bfcbe18) or how do I use it (for mimicking urgency hint in swa

[konsole] [Bug 443411] Regression: %w and %t placeholders not available in bell notifications

2021-10-20 Thread Jan Palus
https://bugs.kde.org/show_bug.cgi?id=443411 Jan Palus changed: What|Removed |Added CC||jbb.m...@gmx.de

[konsole] [Bug 443411] New: Regression: %w and %t placeholders not available in bell notifications

2021-10-06 Thread Jan Palus
https://bugs.kde.org/show_bug.cgi?id=443411 Bug ID: 443411 Summary: Regression: %w and %t placeholders not available in bell notifications Product: konsole Version: 21.08.1 Platform: Other OS: Linux

[releaseme] [Bug 382550] man pages not created in kaffeine 2.0.12

2017-07-23 Thread Jan Palus
https://bugs.kde.org/show_bug.cgi?id=382550 --- Comment #3 from Jan Palus --- (In reply to Mauro Carvalho Chehab from comment #2) > I created a new tarball using kde-create-tarball script, instead of > releaseme. It should provide manpages: > > https://download.kde.org/stable/kaf

[kaffeine] [Bug 382550] New: man pages not created in 2.0.12

2017-07-20 Thread Jan Palus
https://bugs.kde.org/show_bug.cgi?id=382550 Bug ID: 382550 Summary: man pages not created in 2.0.12 Product: kaffeine Version: unspecified Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal

[kaffeine] [Bug 368907] kaffeine sometimes uses 100% CPU

2017-07-08 Thread Jan Palus
https://bugs.kde.org/show_bug.cgi?id=368907 --- Comment #40 from Jan Palus --- Looks like this was it! After applying last patch issue did not occur within 10min of constant channel switching. Thanks a lot Mauro! -- You are receiving this mail because: You are watching all bug changes.

[kaffeine] [Bug 368907] kaffeine sometimes uses 100% CPU

2017-07-08 Thread Jan Palus
https://bugs.kde.org/show_bug.cgi?id=368907 --- Comment #37 from Jan Palus --- And just to be clear -- not empty counter continues to increase with the same pace once bug is triggered and everything works fine (TV runs smoothly), it's just high CPU usage in the background that changes. --

[kaffeine] [Bug 368907] kaffeine sometimes uses 100% CPU

2017-07-08 Thread Jan Palus
https://bugs.kde.org/show_bug.cgi?id=368907 --- Comment #36 from Jan Palus --- Looks like it's still the same, but I'm not really sure whether we are on the same page -- writeToPipe() is not looping. It is rather called a lot once the bug is triggered. I've made following small ad

[kaffeine] [Bug 368907] kaffeine sometimes uses 100% CPU

2017-07-08 Thread Jan Palus
https://bugs.kde.org/show_bug.cgi?id=368907 --- Comment #31 from Jan Palus --- Thanks for the patch. Unfortunately it does not change much -- issue is still there. New warning is constantly printed when kaffeine operates normally: 08-07-17 14:23:17.447 [Warning ] kaffeine.mediawidget: Error 11

[kaffeine] [Bug 368907] kaffeine sometimes uses 100% CPU

2017-07-08 Thread Jan Palus
https://bugs.kde.org/show_bug.cgi?id=368907 --- Comment #29 from Jan Palus --- It appears once the issue is triggered DvbLiveViewInternal::writeToPipe() is called thousands of times a second but buffers is always empty. -- You are receiving this mail because: You are watching all bug changes.

[kaffeine] [Bug 368907] kaffeine sometimes uses 100% CPU

2017-07-08 Thread Jan Palus
https://bugs.kde.org/show_bug.cgi?id=368907 --- Comment #28 from Jan Palus --- Some random observations: 1. For some reason issue is much easier to reproduce if kaffeine is run from gdb. Usually takes single channel change to trigger the problem 2. With enabled G_MAIN_POLL_DEBUG in glib I see

[kaffeine] [Bug 368907] kaffeine sometimes uses 100% CPU

2017-07-05 Thread Jan Palus
https://bugs.kde.org/show_bug.cgi?id=368907 --- Comment #26 from Jan Palus --- Created attachment 106452 --> https://bugs.kde.org/attachment.cgi?id=106452&action=edit callgrind output Also attaching callgrind output -- You are receiving this mail because: You are watching all bug changes.

[kaffeine] [Bug 368907] kaffeine sometimes uses 100% CPU

2017-07-05 Thread Jan Palus
https://bugs.kde.org/show_bug.cgi?id=368907 --- Comment #25 from Jan Palus --- I experience the same issue (version 2.0.10). Seems like it starts to happen as soon as some glitch in decoding is encountered -- video artifacts, green screen which kaffeine recovers from within seconds but keeps on

[kaffeine] [Bug 368907] kaffeine sometimes uses 100% CPU

2017-07-05 Thread Jan Palus
https://bugs.kde.org/show_bug.cgi?id=368907 Jan Palus changed: What|Removed |Added CC||jan.pa...@gmail.com --- Comment #24 from Jan Palus