[krusader] [Bug 376272] Default browser for XML files is useless
https://bugs.kde.org/show_bug.cgi?id=376272 Davide Gianforte changed: What|Removed |Added Status|NEEDSINFO |REPORTED Resolution|WAITINGFORINFO |--- --- Comment #13 from Davide Gianforte --- Changing status -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 375012] cannot print in custom dimensions
https://bugs.kde.org/show_bug.cgi?id=375012 Michael Weghorn changed: What|Removed |Added Resolution|--- |WAITINGFORINFO Status|REPORTED|NEEDSINFO --- Comment #7 from Michael Weghorn --- (In reply to Michael Weghorn from comment #1) > This sounds very much like a Qt bug which has just recently been fixed by > Albert in Qt's development branch: > https://codereview.qt-project.org/#/c/215054/ @Gregor B. Rosenauer: Given this: Are you still experiencing your original issue or is this no longer the case with current Okular versions? -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 375012] cannot print in custom dimensions
https://bugs.kde.org/show_bug.cgi?id=375012 --- Comment #6 from Michael Weghorn --- (In reply to bruce.samha...@samhaber.ca from comment #2) > Created attachment 122940 [details] > Okular print properties Page Custom size media > > When printing from Okular with a page that is a Custom size sheet, tried > setting the media size property in Page and advance Tabs to the 'custom' > sheet. In the page tab it remembers the Custom setting but does not allow > editing of the sheet dimensions. Okular should be using the dimensions from > the file automatically. In the Advanced tab the "Media Size" property is > listed twice, wher the first occurance saves the selected option of 'Custom' > but the second occurance always reverts back to 'Letter' This appears to be > the reason for the Error. What version of Okular are you using? The screenshot looks like this is still a Qt 4 based version, and as far as I know, this has been fixed in Qt 5, so should no longer be the case for recent Okular versions. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 412251] Kmail crashes when deleting mail
https://bugs.kde.org/show_bug.cgi?id=412251 Laurent Montel changed: What|Removed |Added CC||mon...@kde.org, ||vkra...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 412462] New: plasmashell crashes
https://bugs.kde.org/show_bug.cgi?id=412462 Bug ID: 412462 Summary: plasmashell crashes Product: plasmashell Version: 5.16.90 Platform: openSUSE RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: mathias.hom...@opensuse.org CC: plasma-b...@kde.org Target Milestone: 1.0 Application: plasmashell (5.16.90) Qt Version: 5.13.1 Frameworks Version: 5.62.0 Operating System: Linux 4.12.14-lp150.12.73-default x86_64 Distribution: "openSUSE Leap 15.0" -- Information about the crash: - What I was doing when the application crashed: I was running an OpenGL app. Plasmashell chrashed, then crashed twice more when I tried to restart it with "kstart5 plasmashell" The crash can be reproduced sometimes. -- Backtrace: Application: Plasma (plasmashell), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7fe3d405c540 (LWP 23724))] Thread 5 (Thread 0x7fe39ff33700 (LWP 23737)): #0 0x7fe3cafec90d in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7fe3cde3b87b in QWaitConditionPrivate::wait (deadline=..., this=0x5583ea72b290) at thread/qwaitcondition_unix.cpp:146 #2 QWaitCondition::wait (this=, mutex=0x5583ea72a5c0, deadline=...) at thread/qwaitcondition_unix.cpp:225 #3 0x7fe3cde3bb89 in QWaitCondition::wait (this=0x5583ea72a5c8, mutex=0x5583ea72a5c0, time=) at thread/qwaitcondition_unix.cpp:208 #4 0x7fe3d1eb18b8 in ?? () from /usr/lib64/libQt5Quick.so.5 #5 0x7fe3d1eb1cea in ?? () from /usr/lib64/libQt5Quick.so.5 #6 0x7fe3cde348e2 in QThreadPrivate::start (arg=0x5583ea72a540) at thread/qthread_unix.cpp:360 #7 0x7fe3cafe6569 in start_thread () from /lib64/libpthread.so.0 #8 0x7fe3cd732a2f in clone () from /lib64/libc.so.6 Thread 4 (Thread 0x7fe3b5ed5700 (LWP 23728)): #0 0x7fe3c7807768 in g_main_context_prepare () from /usr/lib64/libglib-2.0.so.0 #1 0x7fe3c780814b in g_main_context_iterate.isra () from /usr/lib64/libglib-2.0.so.0 #2 0x7fe3c780832c in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #3 0x7fe3ce07770b in QEventDispatcherGlib::processEvents (this=0x7fe3ac000b10, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #4 0x7fe3ce017c6a in QEventLoop::exec (this=this@entry=0x7fe3b5ed4c90, flags=..., flags@entry=...) at kernel/qeventloop.cpp:225 #5 0x7fe3cde3313a in QThread::exec (this=) at thread/qthread.cpp:531 #6 0x7fe3d194ced5 in ?? () from /usr/lib64/libQt5Qml.so.5 #7 0x7fe3cde348e2 in QThreadPrivate::start (arg=0x5583e9ca8530) at thread/qthread_unix.cpp:360 #8 0x7fe3cafe6569 in start_thread () from /lib64/libpthread.so.0 #9 0x7fe3cd732a2f in clone () from /lib64/libc.so.6 Thread 3 (Thread 0x7fe3bc952700 (LWP 23726)): #0 0x7fe3ce0774bd in socketNotifierSourceCheck (source=0x7fe3b0004c10) at kernel/qeventdispatcher_glib.cpp:75 #1 0x7fe3c7807c31 in g_main_context_check () from /usr/lib64/libglib-2.0.so.0 #2 0x7fe3c78081c0 in g_main_context_iterate.isra () from /usr/lib64/libglib-2.0.so.0 #3 0x7fe3c780832c in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #4 0x7fe3ce07770b in QEventDispatcherGlib::processEvents (this=0x7fe3bb10, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #5 0x7fe3ce017c6a in QEventLoop::exec (this=this@entry=0x7fe3bc951c80, flags=..., flags@entry=...) at kernel/qeventloop.cpp:225 #6 0x7fe3cde3313a in QThread::exec (this=) at thread/qthread.cpp:531 #7 0x7fe3cf143e35 in ?? () from /usr/lib64/libQt5DBus.so.5 #8 0x7fe3cde348e2 in QThreadPrivate::start (arg=0x7fe3cf3bbd80) at thread/qthread_unix.cpp:360 #9 0x7fe3cafe6569 in start_thread () from /lib64/libpthread.so.0 #10 0x7fe3cd732a2f in clone () from /lib64/libc.so.6 Thread 2 (Thread 0x7fe3be4cd700 (LWP 23725)): #0 0x7fe3cd7281db in poll () from /lib64/libc.so.6 #1 0x7fe3d2a8b387 in ?? () from /usr/lib64/libxcb.so.1 #2 0x7fe3d2a8cfba in xcb_wait_for_event () from /usr/lib64/libxcb.so.1 #3 0x7fe3c0eac9c0 in ?? () from /usr/lib64/libQt5XcbQpa.so.5 #4 0x7fe3cde348e2 in QThreadPrivate::start (arg=0x5583e99f4440) at thread/qthread_unix.cpp:360 #5 0x7fe3cafe6569 in start_thread () from /lib64/libpthread.so.0 #6 0x7fe3cd732a2f in clone () from /lib64/libc.so.6 Thread 1 (Thread 0x7fe3d405c540 (LWP 23724)): [KCrash Handler] #6 0x7fe3cdfe0b80 in QSortFilterProxyModelPrivate::build_source_to_proxy_mapping (proxy_to_source=..., source_to_proxy=..., this=0x5583ea54c840) at itemmodels/qsortfilterproxymodel.cpp:1184 #7 0x7fe3cdfe5441 in QSortFilterProxyModelPrivate::sort (this=0x5583ea54c840) at itemmodels/qsortfilterproxymodel.cpp:615 #8 0x7fe3a12c4d10 in Image::backgroundsFound (this=0x5583ea56d120)
[plasmashell] [Bug 407526] Plasmashell and ksysguardd uses cpu
https://bugs.kde.org/show_bug.cgi?id=407526 Bug Janitor Service changed: What|Removed |Added Resolution|WAITINGFORINFO |WORKSFORME Status|NEEDSINFO |RESOLVED --- Comment #4 from Bug Janitor Service --- This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 411463] Copy Paste layer group to another document, group is flattened, group layers not preserved.
https://bugs.kde.org/show_bug.cgi?id=411463 Bug Janitor Service changed: What|Removed |Added Resolution|WAITINGFORINFO |WORKSFORME Status|NEEDSINFO |RESOLVED --- Comment #3 from Bug Janitor Service --- This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[krusader] [Bug 376272] Default browser for XML files is useless
https://bugs.kde.org/show_bug.cgi?id=376272 --- Comment #12 from Bug Janitor Service --- Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 410456] If the selection is made only with outline selection tool, can't use Stroke Selection on it.
https://bugs.kde.org/show_bug.cgi?id=410456 --- Comment #4 from acc4commissi...@gmail.com --- (In reply to acc4commissions from comment #3) > Looks like it's fixed now. git 096bf25. But I'm not sure since when it haven't happened. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 410456] If the selection is made only with outline selection tool, can't use Stroke Selection on it.
https://bugs.kde.org/show_bug.cgi?id=410456 acc4commissi...@gmail.com changed: What|Removed |Added Resolution|--- |FIXED Status|REPORTED|RESOLVED --- Comment #3 from acc4commissi...@gmail.com --- Looks like it's fixed now. -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 412447] Scaling-Level as multiple of 0.25
https://bugs.kde.org/show_bug.cgi?id=412447 --- Comment #5 from Christoph Cullmann --- The main issue is: 0.1 is no floating point value you can represent on a machine. With factors like 1.1, you get rounding artifacts everywhere. Even if you scale something trivial like a 10 pixel UI element with that, you will never get a non-fractional real pixel height even if you repeat this 10 times. With 0.25 or 0.5 you at least have some floating point value that will not lead to such strange rounding issues. https://www.exploringbinary.com/why-0-point-1-does-not-exist-in-floating-point/ It has a reason that Microsoft per default only allows such levels and hides the others behind some "now all is broken" text. Beside that, before the rise of HiDPI, for such minimal DPI differences, one just adjusted the fonts, no need to render 1 pixel lines as 1.1 pixel. I just don't even see the use-case for allowing per default such fine-grained zooming, beside that it breaks the rendering of close to everything. If I try that here, I have rendering artifacts everywhere, from the standard menus to toolbars... -- You are receiving this mail because: You are watching all bug changes.
[frameworks-ktexteditor] [Bug 390451] Horizontal Lines with Fractional Scaling on Apps that use KTextEditor framework
https://bugs.kde.org/show_bug.cgi?id=390451 --- Comment #20 from Christoph Cullmann --- There is nothing to round in virtual pixel. e.g. if the font is 10 virtual pixel high, you get real 12.5 real pixel if you scale with 1.25. KTextEditor will not at all see this and we will get some ugly lines sprinkled in here and there. Even worse for scaling factors that never lead to full pixel ever again, like 0.1. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 412382] Kwin Crash when minimized window with Magic Lamp effects
https://bugs.kde.org/show_bug.cgi?id=412382 --- Comment #2 from dendy oc --- (In reply to Vlad Zahorodnii from comment #1) > Unfortunately the backtrace lacks debug symbols. Please repackage kwin > according to [1] and submit a new backtrace with debug symbols. > > [1] > https://wiki.archlinux.org/index.php/Debug_- > _Getting_Traces#CMAKE_(KDE)_applications done updated distribution on bug report, im using manjaro. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 412382] Kwin Crash when minimized window with Magic Lamp effects
https://bugs.kde.org/show_bug.cgi?id=412382 dendy oc changed: What|Removed |Added Platform|unspecified |Manjaro -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 375012] cannot print in custom dimensions
https://bugs.kde.org/show_bug.cgi?id=375012 --- Comment #5 from bruce.samha...@samhaber.ca --- When printing from Okular with a page that is a Custom size sheet, tried setting the media size property in Page and advance Tabs to the 'custom' sheet. In the page tab it remembers the Custom setting but does not allow editing of the sheet dimensions. Okular should be using the dimensions from the file automatically. In the Advanced tab the "Media Size" property is listed twice, where the first occurrance saves the selected option of 'Custom' but the second occurrance always reverts back to 'Letter' -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 375012] cannot print in custom dimensions
https://bugs.kde.org/show_bug.cgi?id=375012 --- Comment #4 from bruce.samha...@samhaber.ca --- Created attachment 122942 --> https://bugs.kde.org/attachment.cgi?id=122942=edit Okular print Custom size Error message When printing from Okular with a page that is a Custom size sheet, tried setting the media size property in Page and advance Tabs to the 'custom' sheet. In the page tab it remembers the Custom setting but does not allow editing of the sheet dimensions. Okular should be using the dimensions from the file automatically. In the Advanced tab the "Media Size" property is listed twice, where the first occurrance saves the selected option of 'Custom' but the second occurrance always reverts back to 'Letter' -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 375012] cannot print in custom dimensions
https://bugs.kde.org/show_bug.cgi?id=375012 --- Comment #3 from bruce.samha...@samhaber.ca --- Created attachment 122941 --> https://bugs.kde.org/attachment.cgi?id=122941=edit Okular print properties Advanced tab, custom size media When printing from Okular with a page that is a Custom size sheet, tried setting the media size property in Page and advance Tabs to the 'custom' sheet. In the page tab it remembers the Custom setting but does not allow editing of the sheet dimensions. Okular should be using the dimensions from the file automatically. In the Advanced tab the "Media Size" property is listed twice, where the first occurance saves the selected option of 'Custom' but the second occurance always reverts back to 'Letter' -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 375012] cannot print in custom dimensions
https://bugs.kde.org/show_bug.cgi?id=375012 bruce.samha...@samhaber.ca changed: What|Removed |Added CC||bruce.samha...@samhaber.ca --- Comment #2 from bruce.samha...@samhaber.ca --- Created attachment 122940 --> https://bugs.kde.org/attachment.cgi?id=122940=edit Okular print properties Page Custom size media When printing from Okular with a page that is a Custom size sheet, tried setting the media size property in Page and advance Tabs to the 'custom' sheet. In the page tab it remembers the Custom setting but does not allow editing of the sheet dimensions. Okular should be using the dimensions from the file automatically. In the Advanced tab the "Media Size" property is listed twice, wher the first occurance saves the selected option of 'Custom' but the second occurance always reverts back to 'Letter' This appears to be the reason for the Error. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 169751] Allow separators between Places panel items
https://bugs.kde.org/show_bug.cgi?id=169751 --- Comment #23 from Christoph Feck --- Bug 309620 is not really a duplicate, because it was requesting multiple groups (with a new header title), while this ticket requests a simple separator line (within Places in a group). -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 309621] Allow re-ordering of groups in the Places Panel
https://bugs.kde.org/show_bug.cgi?id=309621 Christoph Feck changed: What|Removed |Added CC||s...@olan.org --- Comment #2 from Christoph Feck --- *** Bug 407490 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 407490] Ability change order of sections in Places Panel
https://bugs.kde.org/show_bug.cgi?id=407490 Christoph Feck changed: What|Removed |Added Status|CONFIRMED |RESOLVED Resolution|--- |DUPLICATE --- Comment #2 from Christoph Feck --- *** This bug has been marked as a duplicate of bug 309621 *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 412065] plasmashell crashed after quitting virt-viewer/remote-viewer
https://bugs.kde.org/show_bug.cgi?id=412065 Christoph Feck changed: What|Removed |Added Resolution|WAITINGFORINFO |WORKSFORME Status|NEEDSINFO |RESOLVED --- Comment #3 from Christoph Feck --- Thanks for the update; changing status. -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 412447] Scaling-Level as multiple of 0.25
https://bugs.kde.org/show_bug.cgi?id=412447 Christoph Feck changed: What|Removed |Added CC||cf...@kde.org --- Comment #4 from Christoph Feck --- What exactly is the difference you are trying to solve with this proposal? The Kate issue you mentioned (and worked around with trying to find a font size that gets an integer upscaled result) doesn't sound plausible. For example, if you scale e.g. 22 pixels (common icon size) up by 1.25 or 1.4, you still get a fractional result in either case. I agree that limiting to only a single fractional digit is wrong, but not being able to set finer scaling ratios than 0.25 is not something I feel comfortable. -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 412381] KMyMoney Import CSV
https://bugs.kde.org/show_bug.cgi?id=412381 Christoph Feck changed: What|Removed |Added Component|general |general Product|kde |kmymoney Assignee|unassigned-b...@kde.org |kmymoney-de...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[frameworks-ktexteditor] [Bug 390451] Horizontal Lines with Fractional Scaling on Apps that use KTextEditor framework
https://bugs.kde.org/show_bug.cgi?id=390451 --- Comment #19 from Christoph Feck --- That looks like a hack indeed. I always assumed the bounding box used for clearing/background rendering wasn't correctly rounded to whole pixels, see Konsole's attempt at bug 373232 comment 31. Top/Left need to be rounded down, while Bottom/Right need to be rounded up. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 389440] Filter: Add to Addressbook needs to include REPLY-TO field as source
https://bugs.kde.org/show_bug.cgi?id=389440 gjditchfi...@acm.org changed: What|Removed |Added Resolution|WAITINGFORINFO |WORKSFORME Status|NEEDSINFO |RESOLVED --- Comment #3 from gjditchfi...@acm.org --- Well, at least we can close this one! -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 410723] Freehand annotation jagged lines with stylus
https://bugs.kde.org/show_bug.cgi?id=410723 --- Comment #16 from Christoph Feck --- Could bug 411487 be related? -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 411495] Allow to change left right balance of a source in pulseaudio
https://bugs.kde.org/show_bug.cgi?id=411495 Christoph Feck changed: What|Removed |Added Resolution|--- |DUPLICATE Status|CONFIRMED |RESOLVED --- Comment #1 from Christoph Feck --- *** This bug has been marked as a duplicate of bug 385250 *** -- You are receiving this mail because: You are watching all bug changes.
[plasma-pa] [Bug 385250] Cannot change volume per channel
https://bugs.kde.org/show_bug.cgi?id=385250 Christoph Feck changed: What|Removed |Added CC||yanp.b...@gmail.com --- Comment #4 from Christoph Feck --- *** Bug 411495 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 411504] "You will be asked to authenticate before saving" takes a few milliseconds to appear below the header
https://bugs.kde.org/show_bug.cgi?id=411504 Christoph Feck changed: What|Removed |Added Severity|normal |minor -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 411564] Plasmashell hangs the desktop with 100% CPU usage
https://bugs.kde.org/show_bug.cgi?id=411564 Christoph Feck changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |DOWNSTREAM --- Comment #1 from Christoph Feck --- Crash is in libnvidia-glcore.so.430.40 OpenGL driver. Please report this issue directly to nvidia developers via https://devtalk.nvidia.com/default/topic/522835/linux/if-you-have-a-problem-please-read-this-first/ -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 411496] Scrollbar should only be shown if needed
https://bugs.kde.org/show_bug.cgi?id=411496 --- Comment #2 from Christoph Feck --- Since Konsole cannot reflow text, a newly appearing scrollbar would cover content. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 411537] Nanosecond timestamps support
https://bugs.kde.org/show_bug.cgi?id=411537 Christoph Feck changed: What|Removed |Added Severity|wishlist|minor -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 411522] Modified column on details view mode not show 2 digits on short date
https://bugs.kde.org/show_bug.cgi?id=411522 --- Comment #1 from Christoph Feck --- If this depends on the selected locale, the formatting data comes from CLDR database in Qt. -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 412461] Crash or extreme memory usage (over 20 gigabytes, OOM) on large attachment, over a gigabyte
https://bugs.kde.org/show_bug.cgi?id=412461 Melvin Vermeeren changed: What|Removed |Added CC||m...@mel.vin -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 412461] New: Crash or extreme memory usage (over 20 gigabytes, OOM) on large attachment, over a gigabyte
https://bugs.kde.org/show_bug.cgi?id=412461 Bug ID: 412461 Summary: Crash or extreme memory usage (over 20 gigabytes, OOM) on large attachment, over a gigabyte Product: kontact Version: 5.9.2 Platform: Debian stable OS: Linux Status: REPORTED Severity: major Priority: NOR Component: mail Assignee: kdepim-b...@kde.org Reporter: m...@mel.vin Target Milestone: --- Created attachment 122939 --> https://bugs.kde.org/attachment.cgi?id=122939=edit htop prior to freeze and OOM (Note: perhaps this bug should be filed under akonadi and kmail too.) These are really two distinct bugs, both related to absurdly large attachments. 1. When attaching a really large attachment (try one of a few GB), Kontact crashes. This one is not so bad, you restart Kontact and it still works. 2. When attaching a large-but-not-large-enough-to-crash attachment (a 779,5 MiB file), it gets accepted but akonadi then completely chokes and uses 20GB+ RAM spread over its agents until kernel OOM killer nukes it. The message is stuck in outbox, any access to local folders will trigger message processing again leading to the 20GB+ RAM usage again. STEPS TO REPRODUCE 1. Attach a 779,5 MiB attachment to a mail in the composer. 2. Attempt to send the mail. OBSERVED RESULT The mail gets stuck in the local folders outbox and OOM will quickly follow. (Unless you have enough RAM, perhaps 100GB or so?) Every access of local folders will cause akonadi to re-read this mail, because it's stuck in the outbox, triggering the issue again and again. EXPECTED RESULT One of: a. It works without crashing or consuming a ridiculous amount of memory. b. It refuses to attach ridiculously oversized attachments. WORKAROUND If a mail with an extremely large attachment is stuck in the local folders, use "ncdu" or similar tool to locate the mail file on disk. For example "ncdu ~/.local/share/akonadi_maildir_resource_0". Then, stop akonadi, delete the problematic file and start akonadi again. RECOMMENDED FIX Set the composer setting "Maximum Attachment Size" somewhere between 50MB and 100MB or so by default. Then also either disallow unlimited attachment size completely or add a gigantic warning regarding the memory usage if set to unlimited. SOFTWARE/OS VERSIONS Kontact 5.9.3 (18.08.3, Debian Buster/Stable) Operating System: Debian GNU/Linux 10 KDE Plasma Version: 5.14.5 Qt Version: 5.11.3 KDE Frameworks Version: 5.54.0 Kernel Version: 4.19.0-6-amd64 OS Type: 64-bit ADDITIONAL INFORMATION See the attachment for htop output just before system unresponsiveness due to swapping and OOM killer invocation. Personal note: Although it may seem silly trying to try and attach a gigantic file to an email, I've seen this bug in production. Dragging & dropping a large LibreOffice presentation from Dolphin into Kontact is easily done, and the user's Kontact/akonadi is completely crippled afterwards if the file size happens to be in the "sweet spot". -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 389440] Filter: Add to Addressbook needs to include REPLY-TO field as source
https://bugs.kde.org/show_bug.cgi?id=389440 --- Comment #2 from si...@i2cchip.com --- Thanks for the suggestion, that works for me. (And it is remarkable how often replyto is completely different!) BTW, Long Headers weren't in the settings->plugins until after I had tried "all headers" and restarted. then several restarts were needed before long headers appeared in the view options. (Kmail5.2) Kmail 5 is so goddamn flakey. Have they even restored printing yet? I would suggest that it should be a default in Fancy Headers to show reply-to when it is non-empty and different from sender. -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 412429] étiquettes placées dans une ventilation ne sont pas détectées
https://bugs.kde.org/show_bug.cgi?id=412429 --- Comment #1 from Jack --- I am only guessing, but I think you are missing a step somewhere. I'm also not sure if you are having problems with categories or tags, but I don't have any problem with either. I tried: 1) create a new transaction and select a payee 2) click the split button 3) create and save a split with a new category and a new tag. 4) create and save a second split with a different new category and different new tag. 5) save the splits (Note you must explicitly save each new split and then save all the splits.) 6) save the new transaction I see both new categories in the category view and I see both new tags in the tag view. When you go back and look at the transaction and all the splits, is every detail as you set it? If not, you forgot to save at some step. -- You are receiving this mail because: You are watching all bug changes.
[kdelibs] [Bug 101684] Pressing "Launch Bug Report Wizard" should close the window
https://bugs.kde.org/show_bug.cgi?id=101684 ramad changed: What|Removed |Added CC||i...@add4.org -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 412460] New: Keyboard shortcuts for changing the brush size do not work when using the Line Tool
https://bugs.kde.org/show_bug.cgi?id=412460 Bug ID: 412460 Summary: Keyboard shortcuts for changing the brush size do not work when using the Line Tool Product: krita Version: 4.2.6 Platform: MS Windows OS: MS Windows Status: REPORTED Severity: minor Priority: NOR Component: Usability Assignee: krita-bugs-n...@kde.org Reporter: catava...@gmail.com Target Milestone: --- SUMMARY While using the Line Tool, keyboard sortcuts (square brackets in my case), or otherwise using Shift+Click and dragging doesn't change the brush size. STEPS TO REPRODUCE 1. Select the Line Tool 2. Use square brackets to change brush size or Shift+Click OBSERVED RESULT Brush size does not change. EXPECTED RESULT Brush size should change. SOFTWARE/OS VERSIONS Windows: Windows 10 Pro, Version 1903 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.
[krunner] [Bug 412459] New: KRunner crashes when selecting a Spectacle window containing an unsaved screenshot
https://bugs.kde.org/show_bug.cgi?id=412459 Bug ID: 412459 Summary: KRunner crashes when selecting a Spectacle window containing an unsaved screenshot Product: krunner Version: 5.16.90 Platform: Archlinux Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@privat.broulik.de Reporter: tokmajigeo...@gmail.com Target Milestone: --- Application: krunner (5.16.90) Qt Version: 5.13.1 Frameworks Version: 5.62.0 Operating System: Linux 5.3.1-arch1-1-ARCH x86_64 Distribution: "Arch Linux" -- Information about the crash: When selecting an open Spectacle window containing an unsaved screenshot, KRunner segfaults. The crash can be reproduced every time. -- Backtrace: Application: krunner (krunner), signal: Segmentation fault Using host libthread_db library "/usr/lib/libthread_db.so.1". [Current thread is 1 (Thread 0x7f16bb901c80 (LWP 334272))] Thread 21 (Thread 0x7f167cff9700 (LWP 334365)): #0 0x7f16bfe42415 in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7f16c0ab2660 in QWaitCondition::wait(QMutex*, QDeadlineTimer) () at /usr/lib/libQt5Core.so.5 #2 0x7f16c0ab2752 in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/libQt5Core.so.5 #3 0x7f16b0cca309 in ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*, bool, bool, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #4 0x7f16b0ccdd8b in () at /usr/lib/libKF5ThreadWeaver.so.5 #5 0x7f16b0cc94fe in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #6 0x7f16b0ccdde1 in () at /usr/lib/libKF5ThreadWeaver.so.5 #7 0x7f16b0cc94fe in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #8 0x7f16b0ccbecc in ThreadWeaver::Thread::run() () at /usr/lib/libKF5ThreadWeaver.so.5 #9 0x7f16c0aac5b0 in () at /usr/lib/libQt5Core.so.5 #10 0x7f16bfe3c57f in start_thread () at /usr/lib/libpthread.so.0 #11 0x7f16c07390e3 in clone () at /usr/lib/libc.so.6 Thread 20 (Thread 0x7f167d7fa700 (LWP 334364)): #0 0x7f16bfe42415 in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7f16c0ab2660 in QWaitCondition::wait(QMutex*, QDeadlineTimer) () at /usr/lib/libQt5Core.so.5 #2 0x7f16c0ab2752 in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/libQt5Core.so.5 #3 0x7f16b0cca309 in ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*, bool, bool, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #4 0x7f16b0ccdd8b in () at /usr/lib/libKF5ThreadWeaver.so.5 #5 0x7f16b0cc94fe in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #6 0x7f16b0ccdde1 in () at /usr/lib/libKF5ThreadWeaver.so.5 #7 0x7f16b0cc94fe in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #8 0x7f16b0ccbecc in ThreadWeaver::Thread::run() () at /usr/lib/libKF5ThreadWeaver.so.5 #9 0x7f16c0aac5b0 in () at /usr/lib/libQt5Core.so.5 #10 0x7f16bfe3c57f in start_thread () at /usr/lib/libpthread.so.0 #11 0x7f16c07390e3 in clone () at /usr/lib/libc.so.6 Thread 19 (Thread 0x7f167dffb700 (LWP 334363)): #0 0x7f16bfe42415 in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7f16c0ab2660 in QWaitCondition::wait(QMutex*, QDeadlineTimer) () at /usr/lib/libQt5Core.so.5 #2 0x7f16c0ab2752 in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/libQt5Core.so.5 #3 0x7f16b0cca309 in ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*, bool, bool, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #4 0x7f16b0ccdd8b in () at /usr/lib/libKF5ThreadWeaver.so.5 #5 0x7f16b0cc94fe in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #6 0x7f16b0ccdde1 in () at /usr/lib/libKF5ThreadWeaver.so.5 #7 0x7f16b0cc94fe in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #8 0x7f16b0ccbecc in ThreadWeaver::Thread::run() () at /usr/lib/libKF5ThreadWeaver.so.5 #9 0x7f16c0aac5b0 in () at /usr/lib/libQt5Core.so.5 #10 0x7f16bfe3c57f in start_thread () at /usr/lib/libpthread.so.0 #11 0x7f16c07390e3 in clone () at /usr/lib/libc.so.6 Thread 18 (Thread 0x7f167e7fc700 (LWP 334362)): #0 0x7f16bfe42415 in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7f16c0ab2660 in QWaitCondition::wait(QMutex*, QDeadlineTimer) () at /usr/lib/libQt5Core.so.5 #2 0x7f16c0ab2752 in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/libQt5Core.so.5 #3 0x7f16b0cca309 in
[krita] [Bug 412458] New: Make the preview line from the assistant tool invisible when snapping to it is disabled
https://bugs.kde.org/show_bug.cgi?id=412458 Bug ID: 412458 Summary: Make the preview line from the assistant tool invisible when snapping to it is disabled Product: krita Version: 4.2.7-beta1 Platform: MS Windows OS: MS Windows Status: REPORTED Severity: wishlist Priority: NOR Component: Tool/Assistants Assignee: krita-bugs-n...@kde.org Reporter: acc4commissi...@gmail.com Target Milestone: --- SUMMARY git 096bf25 Or make the whole assistant tool invisible. Making it visible the whole time seems unnecessary and only bothers users. SOFTWARE/OS VERSIONS Windows: Win7 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.
[krita] [Bug 412457] Importing .CSV of animation
https://bugs.kde.org/show_bug.cgi?id=412457 --- Comment #1 from Kevin --- I found this topic in the KDE forum: How can I import a TVPaint csv file in Krita? https://forum.kde.org/viewtopic.php?f=139=159957 My argument for fixing this is that most applications with an a timeline have some form of data export as it is an essential step in compositing (TVPaint, Adobe Premiere, After Effects, Final Cut Pro, etc.). -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 412457] Importing .CSV of animation
https://bugs.kde.org/show_bug.cgi?id=412457 Kevin changed: What|Removed |Added CC||ke...@blastframe.com -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 412456] Export Animation as .CSV
https://bugs.kde.org/show_bug.cgi?id=412456 Kevin changed: What|Removed |Added CC||ke...@blastframe.com -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 412457] New: Importing .CSV of animation
https://bugs.kde.org/show_bug.cgi?id=412457 Bug ID: 412457 Summary: Importing .CSV of animation Product: krita Version: 4.2.6 Platform: MS Windows OS: MS Windows Status: REPORTED Severity: normal Priority: NOR Component: Animation Assignee: krita-bugs-n...@kde.org Reporter: ke...@blastframe.com Target Milestone: --- Created attachment 122938 --> https://bugs.kde.org/attachment.cgi?id=122938=edit A .csv generated by Krita through File > Export SUMMARY The Krita documentation says it both export and import the .csv animation format from TVPaint. https://docs.krita.org/en/general_concepts/file_formats/file_csv.html?highlight=csv It does not seem possible to import the .csv animation. STEPS TO REPRODUCE 1. I've attached a .csv file generated by Krita. 2. Choose File > Open 3. Navigate to .csv and choose open --ALTERNATIVE METHOD-- (I didn't really expect this one to work, but thought it could be possible) 1. File > Import animation frames 2. A dialog opens for adding images. I choose Add Images... and select the .csv 3. Click OK OBSERVED RESULT I get the following Error message alert: "Could not open file:\\\Krita_Animation_Test.csv. Reason: The file format cannot be parsed.." https://i.imgur.com/a7iLG4L.png EXPECTED RESULT A Krita project opens with the same layer structure and frame timing as when exporting the .csv. SOFTWARE/OS VERSIONS Windows: 10 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.
[krita] [Bug 412456] Export Animation as .CSV
https://bugs.kde.org/show_bug.cgi?id=412456 --- Comment #1 from Kevin --- This does seem possible by going to File > Export then from the Exporting Dialogue window, choosing CSV document (*.csv) from 'Save as type.' It does not seem possible from the Render Animation dialogue. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 412456] New: Export Animation as .CSV
https://bugs.kde.org/show_bug.cgi?id=412456 Bug ID: 412456 Summary: Export Animation as .CSV Product: krita Version: 4.2.7 Platform: Other OS: MS Windows Status: REPORTED Severity: normal Priority: NOR Component: Animation Assignee: krita-bugs-n...@kde.org Reporter: ke...@blastframe.com Target Milestone: --- Created attachment 122937 --> https://bugs.kde.org/attachment.cgi?id=122937=edit Popup alert after failed .csv animation export. SUMMARY Krita doesn't seem capable of creating a .csv document from an animation. STEPS TO REPRODUCE 1. Produce multi-frame animation. 2. Choose File > Render Animation 3. In Render Animation dialogue, File format > CSV document 4. Click OK OBSERVED RESULT Warning alert pops up: "Failed to render animation frames!" (see Failed_to_Render.png image, attached). EXPECTED RESULT A .csv with information about the frame file paths & durations, similar to the .csv exported from TVPaint: https://docs.krita.org/en/general_concepts/file_formats/file_csv.html?highlight=csv SOFTWARE/OS VERSIONS Windows: 10 Pro 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.
[kstars] [Bug 410761] The Directory of the CCD Panel is not saved
https://bugs.kde.org/show_bug.cgi?id=410761 --- Comment #2 from Rob --- I would think the only way this might not be saved is if KStars did not shut down properly. Did it crash or say that it crashed on exit? -- You are receiving this mail because: You are watching all bug changes.
[LabPlot2] [Bug 412455] Segfault of LabPlot2 when opening settings dropdown
https://bugs.kde.org/show_bug.cgi?id=412455 --- Comment #1 from waterlub...@rocketmail.com --- I reinstalled Labplot and was able to reproduce the issue. It appears to occur when I hover over "Color Theme" in the settings dropdown. -- You are receiving this mail because: You are watching all bug changes.
[ktorrent] [Bug 383127] KTorrent crash while closing
https://bugs.kde.org/show_bug.cgi?id=383127 --- Comment #44 from Valerii Malov --- Git commit b819ef6a35495e12a204cbb241cdb2502c4cd11e by Valerii Malov. Committed on 29/09/2019 at 20:31. Pushed by valeriymalov into branch '5.1'. Cleanup ViewModel a bit and try to fix crash on exit Summary: removeTorrent makes changes to torrent list we are currently iterating on per-item basis, this causees heap-use-after-free in onExit Just call removeRows which should be functionally the same, but should delete all items in one batch Compact ViewModel::Item::update Fix a few warnings (0 as nullptr, c-style casts) Remove useless ViewModel::torrentFromIndex variant Remove unused headers add CMakeLists.txt.user to gitignore Test Plan: build with asan, run & exit, see asan stacktrace before changing onExit Reviewers: stikonas Differential Revision: https://phabricator.kde.org/D24149 M +1-0.gitignore M +1-0ktorrent/CMakeLists.txt M +51 -146 ktorrent/view/viewmodel.cpp M +10 -11 ktorrent/view/viewmodel.h https://commits.kde.org/ktorrent/b819ef6a35495e12a204cbb241cdb2502c4cd11e -- You are receiving this mail because: You are watching all bug changes.
[LabPlot2] [Bug 412455] New: Segfault of LabPlot2 when opening settings dropdown
https://bugs.kde.org/show_bug.cgi?id=412455 Bug ID: 412455 Summary: Segfault of LabPlot2 when opening settings dropdown Product: LabPlot2 Version: 2.6.0 Platform: Archlinux Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: alexander.se...@web.de Reporter: waterlub...@rocketmail.com Target Milestone: --- Application: labplot2 (2.6.0) Qt Version: 5.13.1 Frameworks Version: 5.62.0 Operating System: Linux 5.3.1-zen1-1-zen x86_64 Distribution: "Arch Linux" -- Information about the crash: - What I was doing when the application crashed: Created a new project Scrolled around on the left menu thing a little Opened up the "settings" dropdown Crash - Custom settings of the application: Notably, the system that LabPlot was installed on previously ran MATE. I switched it to KDE fairly recently. This might affect things somewhat. The stacktrace mentions my graphics drivers, which is odd. I am running with an AMD RX 480 with the open source drivers (except for the OpenCL ones, which are proprietary.) -- Backtrace: Application: labplot2 (labplot2), signal: Segmentation fault Using host libthread_db library "/usr/lib/libthread_db.so.1". [Current thread is 1 (Thread 0x7f3932065840 (LWP 11547))] Thread 18 (Thread 0x7f38e3fff700 (LWP 11564)): #0 0x7f3936894667 in poll () at /usr/lib/libc.so.6 #1 0x7f393500c130 in () at /usr/lib/libglib-2.0.so.0 #2 0x7f393500c201 in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #3 0x7f3937defa1c in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #4 0x7f3937d964ec in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #5 0x7f3937bc8385 in QThread::exec() () at /usr/lib/libQt5Core.so.5 #6 0x7f3936127b37 in () at /usr/lib/libQt5DBus.so.5 #7 0x7f3937bc95b0 in () at /usr/lib/libQt5Core.so.5 #8 0x7f393678957f in start_thread () at /usr/lib/libpthread.so.0 #9 0x7f393689f0e3 in clone () at /usr/lib/libc.so.6 Thread 17 (Thread 0x7f3900ff9700 (LWP 11563)): #0 0x7f393678f415 in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7f39293989ec in () at /usr/lib/dri/radeonsi_dri.so #2 0x7f39293985e8 in () at /usr/lib/dri/radeonsi_dri.so #3 0x7f393678957f in start_thread () at /usr/lib/libpthread.so.0 #4 0x7f393689f0e3 in clone () at /usr/lib/libc.so.6 Thread 16 (Thread 0x7f39017fa700 (LWP 11562)): #0 0x7f393678f415 in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7f39293989ec in () at /usr/lib/dri/radeonsi_dri.so #2 0x7f39293985e8 in () at /usr/lib/dri/radeonsi_dri.so #3 0x7f393678957f in start_thread () at /usr/lib/libpthread.so.0 #4 0x7f393689f0e3 in clone () at /usr/lib/libc.so.6 Thread 15 (Thread 0x7f3901ffb700 (LWP 11561)): #0 0x7f393678f415 in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7f39293989ec in () at /usr/lib/dri/radeonsi_dri.so #2 0x7f39293985e8 in () at /usr/lib/dri/radeonsi_dri.so #3 0x7f393678957f in start_thread () at /usr/lib/libpthread.so.0 #4 0x7f393689f0e3 in clone () at /usr/lib/libc.so.6 Thread 14 (Thread 0x7f39027fc700 (LWP 11560)): #0 0x7f393678f415 in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7f39293989ec in () at /usr/lib/dri/radeonsi_dri.so #2 0x7f39293985e8 in () at /usr/lib/dri/radeonsi_dri.so #3 0x7f393678957f in start_thread () at /usr/lib/libpthread.so.0 #4 0x7f393689f0e3 in clone () at /usr/lib/libc.so.6 Thread 13 (Thread 0x7f3902ffd700 (LWP 11559)): #0 0x7f393678f415 in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7f39293989ec in () at /usr/lib/dri/radeonsi_dri.so #2 0x7f39293985e8 in () at /usr/lib/dri/radeonsi_dri.so #3 0x7f393678957f in start_thread () at /usr/lib/libpthread.so.0 #4 0x7f393689f0e3 in clone () at /usr/lib/libc.so.6 Thread 12 (Thread 0x7f39037fe700 (LWP 11558)): #0 0x7f393678f415 in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7f39293989ec in () at /usr/lib/dri/radeonsi_dri.so #2 0x7f39293985e8 in () at /usr/lib/dri/radeonsi_dri.so #3 0x7f393678957f in start_thread () at /usr/lib/libpthread.so.0 #4 0x7f393689f0e3 in clone () at /usr/lib/libc.so.6 Thread 11 (Thread 0x7f3903fff700 (LWP 11557)): #0 0x7f393678f415 in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7f39293989ec in () at /usr/lib/dri/radeonsi_dri.so #2 0x7f39293985e8 in () at /usr/lib/dri/radeonsi_dri.so #3 0x7f393678957f in start_thread () at /usr/lib/libpthread.so.0 #4 0x7f393689f0e3 in clone () at /usr/lib/libc.so.6 Thread 10 (Thread 0x7f39208a0700 (LWP 11556)): #0 0x7f393678f415 in
[kdenlive] [Bug 410815] Changing speed can only be done in single percentage increments using up-down.
https://bugs.kde.org/show_bug.cgi?id=410815 --- Comment #2 from cuill...@laposte.net --- Other workaround : You can use the mouse scroll. Even though it will still use single percentage increments, you'll be able to go much faster! -- You are receiving this mail because: You are watching all bug changes.
[kstars] [Bug 410761] The Directory of the CCD Panel is not saved
https://bugs.kde.org/show_bug.cgi?id=410761 Jasem Mutlaq changed: What|Removed |Added Status|REPORTED|RESOLVED CC||mutla...@ikarustech.com Resolution|--- |WORKSFORME -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 410815] Changing speed can only be done in single percentage increments using up-down.
https://bugs.kde.org/show_bug.cgi?id=410815 cuill...@laposte.net changed: What|Removed |Added CC||cuill...@laposte.net -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 356357] Continous index flushing with fdatasync degrades interactive performance
https://bugs.kde.org/show_bug.cgi?id=356357 Kai Krakow changed: What|Removed |Added CC||k...@kaishome.de --- Comment #14 from Kai Krakow --- I've added some patches before finding this bug. My findings are that disabling read-ahead on the database somewhat helps in low-mem situation but the biggest problem is fsync: That call will actually sync the whole filesystem and not just the database file, and doing that constantly is toxic to performance. It's as simple as that. Here's the link: https://bugs.kde.org/show_bug.cgi?id=404057 and https://github.com/kakra/baloo/commits/fixes/bko-404057. Some of these patches may not be needed at all, some optimize for corner cases. But we should really turn off fsync as the very least. If you don't want to disable fsync, then LMDB is probably the wrong tool to do the job. You'd then need some append-only database with garbage collection (LMDB is already acting a lot like this). I'm pretty sure LMDB is actually a bad choice for baloo, if, and only if, you expect it to be the only software needing to do IO. But after some research, I think LMDB is not the wrong tool, thus we need to adjust how Baloo uses it. The devs of LMDB say that it is safe to use without fsync on any current Linux filesystem (it can loose transactions but it won't corrupt). It is not safe to use on some hypothetical filesystems (it could corrupt). Can we please at least let the user decide and allow him to shoot his own foot? Maybe a config option or env variable? Baloo already has some sort of recovery: If it fails to open the database it will simply purge and recreate it. Maybe it could detect corruptions during use somehow and act similar? I'm not sure if LMDB function could return errors or simply cause crashes. In the first case, it should be easy. I also like the time-based instead of count-based approach much more: Linux already flushes data after no more than 30s, why not just use the same amount? Regarding fsync: I'm not sure if LMDB uses fsync or fdatasync, or if this is even a choice. The developers say in their documentation it's fsync, the strace by Riku says fdatasync. Whatever is used: It's a problem: You cannot expect users to use the software if it totally destroys their user experience. Baloo should be designed around the idea that corruption can occur and luckily it's easy to recover from it: Just rebuild the database. So the proposed solution is really about: How do we properly detect database corruption? -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 412447] Scaling-Level as multiple of 0.25
https://bugs.kde.org/show_bug.cgi?id=412447 --- Comment #3 from Dominik Haumann --- I think Christoph's point is exactly about NOT allowing these 0.1 increments. Say we optimize it in such a way that we have the 2^-n steps (e.g. 0.125, or 0.25), then these values at least can be represented as floating point value. Adding an advanced mode that again lets the user to break things is not a good idea, is it? So +1 for the 0.25 steps. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 411927] Crash during initial scan
https://bugs.kde.org/show_bug.cgi?id=411927 Maik Qualmann changed: What|Removed |Added CC||fuerall...@gmail.com --- Comment #7 from Maik Qualmann --- *** Bug 412453 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 412453] Crash after adding a new album-network drive
https://bugs.kde.org/show_bug.cgi?id=412453 Maik Qualmann changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |DUPLICATE --- Comment #5 from Maik Qualmann --- *** This bug has been marked as a duplicate of bug 411927 *** -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 411965] Rendering issue in dual screen hidpi setup
https://bugs.kde.org/show_bug.cgi?id=411965 Guo Yunhe changed: What|Removed |Added Resolution|--- |FIXED Status|REOPENED|RESOLVED --- Comment #25 from Guo Yunhe --- Yes, I can confirm that patch works. I am not sure if the winId() function is working as described: > If a widget is non-native (alien) and winId() is invoked on it, that widget > will be provided a native handle. https://doc.qt.io/qt-5/qwidget.html#winId -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 412453] Crash after adding a new album-network drive
https://bugs.kde.org/show_bug.cgi?id=412453 --- Comment #4 from Maik Qualmann --- Ok, this crash is already fixed. You can test the pre-release version of digiKam-6.4.0: https://files.kde.org/digikam/ Another thing is the external album. You should assign a drive letter to the network share. We do not support network paths. Maik -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 412453] Crash after adding a new album-network drive
https://bugs.kde.org/show_bug.cgi?id=412453 fuerall...@gmail.com changed: What|Removed |Added Component|Database-Scan |general --- Comment #3 from fuerall...@gmail.com --- (In reply to fuerallesg from comment #2) > Created attachment 122936 [details] > log from start to crash Seems to be in context of a locked database. I have deleted the databases and created new ones but nothing changed. Hope someone can help. Thanks Thoms -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 412454] Adding a Manually added launchers for a script or application is placed in the tasks area
https://bugs.kde.org/show_bug.cgi?id=412454 Recesvintvs changed: What|Removed |Added Resolution|NOT A BUG |FIXED --- Comment #2 from Recesvintvs --- (In reply to Michail Vourlakos from comment #1) > This is default behavior in order to protect the user. If you prefer to add > it as an applet you can disable that behavior through: Dock Settings -> > advanced -> Tasks -> Interaction -> (disable) "Add launchers only in the > Tasks Area" Didn't know about that. Cool! Thanks. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 412453] Crash after adding a new album-network drive
https://bugs.kde.org/show_bug.cgi?id=412453 caulier.gil...@gmail.com changed: What|Removed |Added CC||caulier.gil...@gmail.com Component|general |Database-Scan -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 412453] Crash after adding a new album-network drive
https://bugs.kde.org/show_bug.cgi?id=412453 --- Comment #2 from fuerall...@gmail.com --- Created attachment 122936 --> https://bugs.kde.org/attachment.cgi?id=122936=edit log from start to crash -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 412454] Adding a Manually added launchers for a script or application is placed in the tasks area
https://bugs.kde.org/show_bug.cgi?id=412454 Michail Vourlakos changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |NOT A BUG --- Comment #1 from Michail Vourlakos --- This is default behavior in order to protect the user. If you prefer to add it as an applet you can disable that behavior through: Dock Settings -> advanced -> Tasks -> Interaction -> (disable) "Add launchers only in the Tasks Area" -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 410994] Losing transactions after 8000+ DB to KmyFile
https://bugs.kde.org/show_bug.cgi?id=410994 Ralf Habacker changed: What|Removed |Added Version Fixed In|5.0.7 |4.8.5,5.0.8 -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 410994] Losing transactions after 8000+ DB to KmyFile
https://bugs.kde.org/show_bug.cgi?id=410994 Ralf Habacker changed: What|Removed |Added Latest Commit|https://commits.kde.org/kmy |https://commits.kde.org/kmy |money/781c18c3356d043da2503 |money/f77639cd24b0689959e88 |9d50b41a658de95cac2 |a0f3dc127f5f09aba9e Version Fixed In|4.8.5 |5.0.7 --- Comment #25 from Ralf Habacker --- Git commit f77639cd24b0689959e88a0f3dc127f5f09aba9e by Ralf Habacker. Committed on 29/09/2019 at 12:39. Pushed by habacker into branch '5.0'. Fix fetchTransactions for sql databases Base implementation by Thomas Baumgart from loval feature branch, adapted to 5.x branch by Ralf Habacker. Implementation verified with mymoneydatabasemgrtest. FIXED-IN:5.0.7 M +15 -0kmymoney/plugins/sql/mymoneydbdef.h M +101 -78 kmymoney/plugins/sql/mymoneystoragesql.cpp https://commits.kde.org/kmymoney/f77639cd24b0689959e88a0f3dc127f5f09aba9e -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 410994] Losing transactions after 8000+ DB to KmyFile
https://bugs.kde.org/show_bug.cgi?id=410994 Ralf Habacker changed: What|Removed |Added Latest Commit|https://commits.kde.org/kmy |https://commits.kde.org/kmy |money/781c18c3356d043da2503 |money/f77639cd24b0689959e88 |9d50b41a658de95cac2 |a0f3dc127f5f09aba9e Version Fixed In|4.8.5 |5.0.7 --- Comment #26 from Ralf Habacker --- Git commit 1216c3c5866dd9bf639216f96726c90ff0931cb5 by Ralf Habacker. Committed on 29/09/2019 at 12:39. Pushed by habacker into branch '5.0'. Fix sql statement case Conflicts: kmymoney/mymoney/sql/mymoneystoragesql.cpp M +15 -15 kmymoney/plugins/sql/mymoneystoragesql.cpp https://commits.kde.org/kmymoney/1216c3c5866dd9bf639216f96726c90ff0931cb5 --- Comment #25 from Ralf Habacker --- Git commit f77639cd24b0689959e88a0f3dc127f5f09aba9e by Ralf Habacker. Committed on 29/09/2019 at 12:39. Pushed by habacker into branch '5.0'. Fix fetchTransactions for sql databases Base implementation by Thomas Baumgart from loval feature branch, adapted to 5.x branch by Ralf Habacker. Implementation verified with mymoneydatabasemgrtest. FIXED-IN:5.0.7 M +15 -0kmymoney/plugins/sql/mymoneydbdef.h M +101 -78 kmymoney/plugins/sql/mymoneystoragesql.cpp https://commits.kde.org/kmymoney/f77639cd24b0689959e88a0f3dc127f5f09aba9e -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 412454] New: Adding a Manually added launchers for a script or application is placed in the tasks area
https://bugs.kde.org/show_bug.cgi?id=412454 Bug ID: 412454 Summary: Adding a Manually added launchers for a script or application is placed in the tasks area Product: lattedock Version: 0.9.2 Platform: Other OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: application Assignee: mvourla...@gmail.com Reporter: colabor...@pseudoname.io Target Milestone: --- SUMMARY If I try to add an icon for a .desktop file, to have a handy launcher for a script or aplication, said icon is always placed in the central area of Latte, not in the place I want, normally beside the system tray. STEPS TO REPRODUCE 1. Drag & drop a script from Dolphin to Latte, just close to the clock and system tray area. OBSERVED RESULT Said icon is placed in the middle of Latte's panel, together with the icons of the running apps, so is easy you run unwillingly the corresponding script or program if you make a mistake and click just half centimeter more to the right/left than you really want. EXPECTED RESULT The icon should sit in the very same place that I drop it on. I'd swear than in older versions it worked that way, or maybe it's the Plasma panel which works like that. Anyway, I think that manually added icons should sit in the position the user wants because we normally have a reason to try placing them right there. SOFTWARE/OS VERSIONS KDE Plasma Version: 5.16.5 KDE Frameworks Version: 5.62 Qt Version: 5.12.3 -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 412106] Discover not showing every application in the search results
https://bugs.kde.org/show_bug.cgi?id=412106 --- Comment #4 from techxga...@outlook.com --- $ appstreamcli search kde-config-cron Unable to find component matching kde-config-cron! $ appstreamcli search kcron Unable to find component matching kcron! Should I report this as a bug to KCron? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 364766] Graphics distorted after suspend/resume with nvidia
https://bugs.kde.org/show_bug.cgi?id=364766 --- Comment #123 from techxga...@outlook.com --- Bummer that Kubuntu, IIRC, will use Qt 5.12 for 20.04 LTS -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 411965] Rendering issue in dual screen hidpi setup
https://bugs.kde.org/show_bug.cgi?id=411965 Christoph Cullmann changed: What|Removed |Added Resolution|FIXED |--- Status|RESOLVED|REOPENED -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 411965] Rendering issue in dual screen hidpi setup
https://bugs.kde.org/show_bug.cgi?id=411965 --- Comment #24 from Christoph Cullmann --- I think I have some fix: https://invent.kde.org/kde/konsole/merge_requests/33 For me that removes the distortion. I think winId introduces native widgets in the wrong places. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 411965] Rendering issue in dual screen hidpi setup
https://bugs.kde.org/show_bug.cgi?id=411965 Christoph Cullmann changed: What|Removed |Added Resolution|--- |FIXED Latest Commit||https://invent.kde.org/kde/ ||konsole/commit/343bc39548f0 ||c42386ba983167b075b2940d626 ||b Status|CONFIRMED |RESOLVED --- Comment #22 from Christoph Cullmann --- Git commit 343bc39548f0c42386ba983167b075b2940d626b by Christoph Cullmann. Committed on 29/09/2019 at 18:10. Pushed by cullmann into branch 'fix-win-id-rendering'. fix rendering artifacts introduced by calling winId winId shall not be called on non-native widgets just call effectiveWinId that will handle this for us M +10 -9src/Session.cpp https://invent.kde.org/kde/konsole/commit/343bc39548f0c42386ba983167b075b2940d626b -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 411965] Rendering issue in dual screen hidpi setup
https://bugs.kde.org/show_bug.cgi?id=411965 Christoph Cullmann changed: What|Removed |Added Latest Commit|https://invent.kde.org/kde/ |https://commits.kde.org/kon |konsole/commit/343bc39548f0 |sole/343bc39548f0c42386ba98 |c42386ba983167b075b2940d626 |3167b075b2940d626b |b | --- Comment #23 from Christoph Cullmann --- Git commit 343bc39548f0c42386ba983167b075b2940d626b by Christoph Cullmann. Committed on 29/09/2019 at 18:10. Pushed by scmsync into branch 'fix-win-id-rendering'. fix rendering artifacts introduced by calling winId winId shall not be called on non-native widgets just call effectiveWinId that will handle this for us M +10 -9src/Session.cpp https://commits.kde.org/konsole/343bc39548f0c42386ba983167b075b2940d626b -- You are receiving this mail because: You are watching all bug changes.
[frameworks-ktexteditor] [Bug 404907] ktexteditor: lineheight regression
https://bugs.kde.org/show_bug.cgi?id=404907 Christoph Cullmann changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |FIXED --- Comment #16 from Christoph Cullmann --- For me this works, if the font is chosen properly. If you choose a font that will lead to some fallback for some characters and these have different heights, this fails. If somebody has a proper fix for that case that doesn't lead to rendering artifacts between lines, this can be re-opened. Otherwise I consider this fixed. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 387313] Subsurfaces are not clipped
https://bugs.kde.org/show_bug.cgi?id=387313 Rainer Finke changed: What|Removed |Added Version|5.16.0 |5.16.90 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-ktexteditor] [Bug 390451] Horizontal Lines with Fractional Scaling on Apps that use KTextEditor framework
https://bugs.kde.org/show_bug.cgi?id=390451 Christoph Cullmann changed: What|Removed |Added Version Fixed In||5.63 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-ktexteditor] [Bug 390451] Horizontal Lines with Fractional Scaling on Apps that use KTextEditor framework
https://bugs.kde.org/show_bug.cgi?id=390451 Christoph Cullmann changed: What|Removed |Added Status|CONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #18 from Christoph Cullmann --- I merged my branch to master, more testers welcome. For me it fixed the artifacts for reasonable zoom factors. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 406866] Windows rearranged when coming back from power save
https://bugs.kde.org/show_bug.cgi?id=406866 John B changed: What|Removed |Added Platform|Fedora RPMs |Kubuntu Packages -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 412453] Crash after adding a new album-network drive
https://bugs.kde.org/show_bug.cgi?id=412453 Maik Qualmann changed: What|Removed |Added CC||metzping...@gmail.com --- Comment #1 from Maik Qualmann --- No, no problem of size. Rather a broken image in the album. Please download DebugView from Microsoft and start it. Post the log from start to crash. Maik -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 412453] Crash after adding a new album-network drive
https://bugs.kde.org/show_bug.cgi?id=412453 fuerall...@gmail.com changed: What|Removed |Added Version|unspecified |6.3.0 OS|Linux |MS Windows Platform|Other |MS Windows -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 412453] New: Crash after adding a new album-network drive
https://bugs.kde.org/show_bug.cgi?id=412453 Bug ID: 412453 Summary: Crash after adding a new album-network drive Product: digikam Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: digikam-bugs-n...@kde.org Reporter: fuerall...@gmail.com Target Milestone: --- SUMMARY I setted up digiKam and added next to a local album location one on the network drive. The network drive has a size of 80 Gb. If I click on album and press F5, digikam crashes within a few seconds. Maybe a size problem? STEPS TO REPRODUCE 1. Click on album 2. Press F5 3. Crash within a few seconds OBSERVED RESULT Crash EXPECTED RESULT No crash but scan process SOFTWARE/OS VERSIONS Windows: 10 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 412447] Scaling-Level as multiple of 0.25
https://bugs.kde.org/show_bug.cgi?id=412447 Christoph Cullmann changed: What|Removed |Added CC||cullm...@kde.org --- Comment #2 from Christoph Cullmann --- I would prefer to just have 0.25 as minimal step. 10% zoom looks for me strange anyways, you can just alter your font sizes a bit and you will have this effect in a much more usable way. (without any artifacts) -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 410254] Clipboard from platform to OS doesn't work 100% of the time
https://bugs.kde.org/show_bug.cgi?id=410254 Frank changed: What|Removed |Added CC||alteahandle-...@yahoo.ca Version|unspecified |1.3.2 --- Comment #5 from Frank --- Same here Pixel 2 after Android 10 Copy on KDE Neon desktop, phone receives and makes pastable. Copy on the phone and desktop receives nothing. Very frustrating when someone sends you a link. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 371837] Dolphin General option "Executing scripts or desktop files" doesn't let you choose between "execute" and "open".
https://bugs.kde.org/show_bug.cgi?id=371837
Nate Graham changed:
What|Removed |Added
Status|REOPENED|RESOLVED
Version Fixed In||19.12.0
Resolution|--- |FIXED
Latest Commit||https://commits.kde.org/dol
||phin/983273924d2887cdccdd7c
||3618d332b52dc0dad6
--- Comment #12 from Nate Graham ---
Git commit 983273924d2887cdccdd7c3618d332b52dc0dad6 by Nate Graham.
Committed on 29/09/2019 at 16:27.
Pushed by ngraham into branch 'master'.
Expose full set of script execution options in settings window
Summary:
Right now the script execution setting is a checkbox, capable only of handling
boolean
input. This is not appropriate because there are actually three options
available.
Accordingly, this patch replaces the checkbox with a combobox (to save space
compared
to radio buttons) that clearly exposes all three options.
FIXED-IN: 19.12.0
Test Plan:
{F7440559}
- All three options do what they say they'll do
- All options get saved properly
- The combobox displays the correct option when the window is loaded
- The {nav Defaults} button resets it to "always ask" as expected
Reviewers: elvisangelaccio, #dolphin, #vdg
Reviewed By: elvisangelaccio, #dolphin
Subscribers: kfm-devel
Tags: #dolphin
Maniphest Tasks: T9932
Differential Revision: https://phabricator.kde.org/D24247
M +40 -9src/settings/general/confirmationssettingspage.cpp
M +2-1src/settings/general/confirmationssettingspage.h
https://commits.kde.org/dolphin/983273924d2887cdccdd7c3618d332b52dc0dad6
--
You are receiving this mail because:
You are watching all bug changes.
[plasmashell] [Bug 412236] Crash in QWaylandXdgSurface::setGrabPopup
https://bugs.kde.org/show_bug.cgi?id=412236 Rex Dieter changed: What|Removed |Added CC||rdie...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 412366] Print to File (PDF) broken on KDE4 in 4.8.4
https://bugs.kde.org/show_bug.cgi?id=412366 --- Comment #7 from Erich --- I can confirm that the following all work: Attachment 122884 (https://bugs.kde.org/attachment.cgi?id=122884) to kdelibs adds the required functionality to kdelibs so that KMyMoney 4.8.4 print works correctly. (Of course KMyMoney must be recompiled after upgrading kdelibs so that the new behavior to print() is enabled.) OR Commit beca6d920 (https://cgit.kde.org/kmymoney.git/commit/?id=beca6d92002eabc52ebd1da52d6edf4c06c9c22c) restores print functionality on stock Slackware64 14.2. The print dialog appears twice, but this is acceptable for me. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 408355] Selection context menu missing find in this document
https://bugs.kde.org/show_bug.cgi?id=408355 Syam changed: What|Removed |Added CC||get.so...@gmail.com --- Comment #4 from Syam --- (In reply to Albert Astals Cid from comment #3) Isn't "search for ... in this document" better than "search for ... in open document"? The first time I saw the screenshot in 'this week in KDE' report, it took me a few seconds to understand that "open document" does not refer to ODF. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 412065] plasmashell crashed after quitting virt-viewer/remote-viewer
https://bugs.kde.org/show_bug.cgi?id=412065 --- Comment #2 from Helmut Robben --- Sorry, but I couldn't reproduce the error. I installed the debug symbols for libplasma-volume-declarative.so, but the error didn't occur anymore. Yesterday my system crashed due to a glibc.so version mess while updating, so I did a complete fresh install without KDE Plasma. My apology for not being of any help here. -- You are receiving this mail because: You are watching all bug changes.
[BalooWidgets] [Bug 409989] Additional Information -> Rating always shows a 0/5 rating
https://bugs.kde.org/show_bug.cgi?id=409989 Alex changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |NOT A BUG --- Comment #1 from Alex --- Looks like the issue occurred simply because I had disabled Baloo. Closing. I think it should be clearer in Dolphin's UI that some of the items under Additional Information require Baloo in order to work, but of course that's a separate issue. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 391445] Bold fonts set in profile settings are not applied after restarting konsole
https://bugs.kde.org/show_bug.cgi?id=391445 promask changed: What|Removed |Added URL||http://www.gruz-profmaster. ||ru -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 371877] Support for keyboard_shortcuts_inhibit_unstable_v1 needed
https://bugs.kde.org/show_bug.cgi?id=371877 Vlad Zahorodnii changed: What|Removed |Added Summary|key combos not being|Support for |properly passed into|keyboard_shortcuts_inhibit_ |keyboard-captured apps |unstable_v1 needed Flags||Wayland+ -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 412349] kwin crashed after VT switch from another X session
https://bugs.kde.org/show_bug.cgi?id=412349 Vlad Zahorodnii changed: What|Removed |Added Resolution|--- |BACKTRACE Status|REPORTED|NEEDSINFO --- Comment #1 from Vlad Zahorodnii --- Unfortunately the backtrace lacks debug symbols. Please install kwin debug packages and submit a new backtrace. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 412391] Crash adter unlocking PC
https://bugs.kde.org/show_bug.cgi?id=412391 Vlad Zahorodnii changed: What|Removed |Added Resolution|--- |BACKTRACE Status|REPORTED|NEEDSINFO --- Comment #1 from Vlad Zahorodnii --- Unfortunately the backtrace lacks debug symbols. Please install kwin debug packages and submit a new backtrace. Also, please post output of qdbus org.kde.KWin /KWin supportInformation -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 412382] Kwin Crash when minimized window with Magic Lamp effects
https://bugs.kde.org/show_bug.cgi?id=412382 Vlad Zahorodnii changed: What|Removed |Added Status|REPORTED|NEEDSINFO Resolution|--- |WAITINGFORINFO --- Comment #1 from Vlad Zahorodnii --- Unfortunately the backtrace lacks debug symbols. Please repackage kwin according to [1] and submit a new backtrace with debug symbols. [1] https://wiki.archlinux.org/index.php/Debug_-_Getting_Traces#CMAKE_(KDE)_applications -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 412357] kwin crashes after minimizing some applications
https://bugs.kde.org/show_bug.cgi?id=412357 Vlad Zahorodnii changed: What|Removed |Added Status|REPORTED|NEEDSINFO Resolution|--- |BACKTRACE --- Comment #1 from Vlad Zahorodnii --- Unfortunately the backtrace lacks debug symbols. Please repackage kwin according to [1] and submit a new backtrace with debug symbols. [1] https://wiki.archlinux.org/index.php/Debug_-_Getting_Traces#CMAKE_(KDE)_applications -- You are receiving this mail because: You are watching all bug changes.
[kdeplasma-addons] [Bug 396254] QQC2 context menu theme differs from widget theme
https://bugs.kde.org/show_bug.cgi?id=396254 Björn Feber changed: What|Removed |Added Product|frameworks-qqc2-desktop-sty |kdeplasma-addons |le | Component|general |General -- You are receiving this mail because: You are watching all bug changes.
[frameworks-qqc2-desktop-style] [Bug 396254] QQC2 context menu theme differs from widget theme
https://bugs.kde.org/show_bug.cgi?id=396254 Björn Feber changed: What|Removed |Added CC||bfe...@protonmail.com Version Fixed In||5.17.0 Status|CONFIRMED |RESOLVED Resolution|--- |FIXED Latest Commit||https://cgit.kde.org/kdepla ||sma-addons.git/commit/?id=3 ||7e9c5a628834b943edd0e0631a8 ||4c8f8d730b77 -- You are receiving this mail because: You are watching all bug changes.
