[plasmashell] [Bug 373885] Plasma Shell crashes on login in ShellCorona::screenForContainment() after screen configuration changes
https://bugs.kde.org/show_bug.cgi?id=373885 --- Comment #17 from Melvin --- I can confirm that on my system (Ubuntu 20.04.4 LTS) with plasma-desktop 4:5.18.8-0ubuntu0.1 the behavior does no longer occur. -- You are receiving this mail because: You are watching all bug changes.
[sieveeditor] [Bug 437858] Ksieve Editor login failed, sends username as password
https://bugs.kde.org/show_bug.cgi?id=437858 Melvin Vermeeren changed: What|Removed |Added Summary|Ksieve Editor login failed |Ksieve Editor login failed, ||sends username as password -- You are receiving this mail because: You are watching all bug changes.
[sieveeditor] [Bug 437858] Ksieve Editor login failed
https://bugs.kde.org/show_bug.cgi?id=437858 Melvin Vermeeren changed: What|Removed |Added Ever confirmed|0 |1 CC||m...@mel.vin Status|REPORTED|CONFIRMED --- Comment #1 from Melvin Vermeeren --- Having the same issue after upgrading to Debian bookworm. 5.23.2/21.08.1. Logs indeed show it is sending the password as username, exposing it to server's logfiles plainly. -- You are receiving this mail because: You are watching all bug changes.
[ktorrent] [Bug 392202] 4MB metadata limit is too small
https://bugs.kde.org/show_bug.cgi?id=392202 Melvin Vermeeren changed: What|Removed |Added Ever confirmed|0 |1 Status|REPORTED|CONFIRMED CC||m...@mel.vin --- Comment #1 from Melvin Vermeeren --- Hit the same issue recently and today I decided to dig into things, found the root cause and also the bug report here. MR submitted to fix it, see https://invent.kde.org/network/libktorrent/-/merge_requests/26. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 421895] New: Multi-monitor login on laptop results in primary & secondary monitor confusion, Plasma then crashes when external monitor is removed
https://bugs.kde.org/show_bug.cgi?id=421895 Bug ID: 421895 Summary: Multi-monitor login on laptop results in primary & secondary monitor confusion, Plasma then crashes when external monitor is removed Product: plasmashell Version: 5.18.5 Platform: Ubuntu Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: melvin.hausmann+bugs@gmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 Application: plasmashell (5.18.5) Qt Version: 5.12.8 Frameworks Version: 5.68.0 Operating System: Linux 5.4.0-31-generic x86_64 Windowing system: X11 Distribution: Ubuntu 20.04 LTS -- Information about the crash: General Info: Hardware System is a laptop with an nvidia optimus card (Nvidia GT 540M with the Nvidia 390 driver installed) Internal monitor resolution is 1366*768 pixel, external is 1920*1080 pixel. Software System is a clean install of Kubuntu 20.04 (no upgrade) using X. - What I was doing when the application crashed: When logging in with the external monitor connected the plasma shell displays the control bar and the background image for the primary monitor on the secondary screen (my case: the laptop screen) and the background image for the secondary screen on the primary monitor (aka the external monitor) Then I unplug the external monitor and the plasma shell crashes, restarts and from there on behaves normally (no more crashing when de-/reattaching displays, displaying things where they should be) The crash can be reproduced every time. -- Backtrace: Application: Plasma (plasmashell), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f60e1d1f280 (LWP 1396))] Thread 11 (Thread 0x7f60af01a700 (LWP 1943)): #0 g_source_ref (source=0x7f60a0005070) at ../../../glib/gmain.c:2166 #1 0x7f60e4011168 in g_source_iter_next (iter=iter@entry=0x7f60af019ba0, source=source@entry=0x7f60af019b98) at ../../../glib/gmain.c:1046 #2 0x7f60e4012aff in g_main_context_check (context=context@entry=0x7f60ac30, max_priority=2147483647, fds=fds@entry=0x7f60a00029e0, n_fds=n_fds@entry=1) at ../../../glib/gmain.c:3860 #3 0x7f60e4013152 in g_main_context_iterate (context=context@entry=0x7f60ac30, block=block@entry=1, dispatch=dispatch@entry=1, self=) at ../../../glib/gmain.c:4044 #4 0x7f60e40132e3 in g_main_context_iteration (context=0x7f60ac30, may_block=may_block@entry=1) at ../../../glib/gmain.c:4108 #5 0x7f60e598a583 in QEventDispatcherGlib::processEvents (this=0x7f60ab60, flags=...) at kernel/qeventdispatcher_glib.cpp:424 #6 0x7f60e59314db in QEventLoop::exec (this=this@entry=0x7f60af019d60, flags=..., flags@entry=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:140 #7 0x7f60e5769785 in QThread::exec (this=) at ../../include/QtCore/../../src/corelib/global/qflags.h:120 #8 0x7f60af5120bc in KCupsConnection::run() () from /lib/x86_64-linux-gnu/libkcupslib.so #9 0x7f60e576a9d2 in QThreadPrivate::start (arg=0x55df48666730) at thread/qthread_unix.cpp:361 #10 0x7f60e4c10609 in start_thread (arg=) at pthread_create.c:477 #11 0x7f60e53f9103 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 10 (Thread 0x7f60b7885700 (LWP 1678)): #0 g_source_ref (source=0x7f60b0004cb0) at ../../../glib/gmain.c:2166 #1 0x7f60e4011168 in g_source_iter_next (iter=iter@entry=0x7f60b7884ba0, source=source@entry=0x7f60b7884b98) at ../../../glib/gmain.c:1046 #2 0x7f60e4012aff in g_main_context_check (context=context@entry=0x7f60bc30, max_priority=2147483647, fds=fds@entry=0x7f60b00058f0, n_fds=n_fds@entry=1) at ../../../glib/gmain.c:3860 #3 0x7f60e4013152 in g_main_context_iterate (context=context@entry=0x7f60bc30, block=block@entry=1, dispatch=dispatch@entry=1, self=) at ../../../glib/gmain.c:4044 #4 0x7f60e40132e3 in g_main_context_iteration (context=0x7f60bc30, may_block=may_block@entry=1) at ../../../glib/gmain.c:4108 #5 0x7f60e598a583 in QEventDispatcherGlib::processEvents (this=0x7f60bb60, flags=...) at kernel/qeventdispatcher_glib.cpp:424 #6 0x7f60e59314db in QEventLoop::exec (this=this@entry=0x7f60b7884d60, flags=..., flags@entry=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:140 #7 0x7f60e5769785 in QThread::exec (this=this@entry=0x7f60d400ca20) at ../../include/QtCore/../../src/corelib/global/qflags.h:120 #8 0x7f60e73c2e1a in QQuickPixmapReader::run (this=0x7f60d400ca20) at util/qquickpixmapcache.cpp:953 #9 0x7f60e576a9d2 in QThreadPrivate::start (arg=0x7f60d400ca20) at thread/qthread_unix.cpp:361 #10 0x7f60e4c10609 in start_thread (arg=) at pthread_create.c:477 #11 0x7f60e53f9103 in clone ()
[krita] [Bug 417814] New: Measure Tool should have an option to make it stay after switching to another tool
https://bugs.kde.org/show_bug.cgi?id=417814 Bug ID: 417814 Summary: Measure Tool should have an option to make it stay after switching to another tool Product: krita Version: 4.2.8 Platform: Debian stable OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: Tool/Assistants Assignee: krita-bugs-n...@kde.org Reporter: m...@mel.vin Target Milestone: --- SUMMARY It's currently not possible to make the result of a measurement "stick" as you switch to other tools, making it difficult to use it correctly. Ideally it would behave somewhat like other assistants, creating a real object that can be moved, deleted, etc. STEPS TO REPRODUCE 1. Use measure tool to measure something. 2. Select the brush tool. OBSERVED RESULT Measurement result is gone, can't refer to the result while painting. EXPECTED RESULT Some way to make the result stick while continuing to paint. SOFTWARE/OS VERSIONS Krita 4.2.8, manual backport. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 417814] Measure Tool should have an option to make it stay after switching to another tool
https://bugs.kde.org/show_bug.cgi?id=417814 Melvin Vermeeren changed: What|Removed |Added CC||m...@mel.vin -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 417813] Measure Tool should support setting the arbitrary base line to compare to
https://bugs.kde.org/show_bug.cgi?id=417813 Melvin Vermeeren changed: What|Removed |Added CC||m...@mel.vin -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 417813] New: Measure Tool should support setting the arbitrary base line to compare to
https://bugs.kde.org/show_bug.cgi?id=417813 Bug ID: 417813 Summary: Measure Tool should support setting the arbitrary base line to compare to Product: krita Version: 4.2.8 Platform: Debian stable OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: Tool/Assistants Assignee: krita-bugs-n...@kde.org Reporter: m...@mel.vin Target Milestone: --- Created attachment 126112 --> https://bugs.kde.org/attachment.cgi?id=126112=edit measuring a v in gimp SUMMARY The measure tool cannot measure between two non-horizontal lines. STEPS TO REPRODUCE 1. Draw the letter V on a canvas, make it big. 1. Select the measure tool. 2. Try to measure an angle between between the two lines of the V. OBSERVED RESULT The measure tool snaps to perfect horizontal. Unless you draw one of the two lines of your V perfectly horizontally it is not easy to measure the angle between the two lines. EXPECTED RESULT Some method to specify two lines to measure angle between. SOFTWARE/OS VERSIONS Krita 4.2.8, manual backport. ADDITIONAL INFORMATION GIMP's measure tool can do this if you hold shift and click on the start point after setting the first measurement line. See the attachment. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 411776] Gaussian Blur Filter Layer Doesn't Wrap Around Canvas like Gaussian Blur Filter Operation
https://bugs.kde.org/show_bug.cgi?id=411776 Melvin changed: What|Removed |Added Status|RESOLVED|REOPENED Ever confirmed|0 |1 CC||me...@hotmail.fr Resolution|WORKSFORME |--- --- Comment #4 from Melvin --- Hi, I have this bug too : the blur filter behave differently if we have the image wrapping on or off, but we don't have control on it with a Blur Filter Layer. I'm on Windows 10 64bit, version 4.2.8 (stable). The suggestion of Eoin seems good (adding a toggle to enable blur wrapping). -- You are receiving this mail because: You are watching all bug changes.
[ktorrent] [Bug 368114] KTorrent fills up .xsession-errors with connection logs
https://bugs.kde.org/show_bug.cgi?id=368114 Melvin Vermeeren changed: What|Removed |Added Status|RESOLVED|REOPENED Resolution|FIXED |--- CC||m...@mel.vin Ever confirmed|0 |1 --- Comment #3 from Melvin Vermeeren --- Don't ask me how but somehow 5.1 branch does NOT have the fix: https://cgit.kde.org/ktorrent.git/tree/ktorrent/main.cpp?h=5.1#n211 Master does have the fix: https://cgit.kde.org/ktorrent.git/tree/ktorrent/main.cpp#n206 I'm guessing a mistake was made during merge at some point. Consider cherry picking af1abedb3bc5cd8e73f134e123857b0f9dcaa239 into 5.1 branch. -- 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.
[kdeplasma-addons] [Bug 395641] plasma-redshift-control manual mouse wheel control broken with recent redshift version
https://bugs.kde.org/show_bug.cgi?id=395641 Melvin Vermeeren changed: What|Removed |Added CC||m...@mel.vin --- Comment #3 from Melvin Vermeeren --- Submitted a patch to Phabricator: https://phabricator.kde.org/D23330 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 407868] New: Wrong selection display of outlines : strange triangles on the top the selection "holes".
https://bugs.kde.org/show_bug.cgi?id=407868 Bug ID: 407868 Summary: Wrong selection display of outlines : strange triangles on the top the selection "holes". Product: krita Version: 4.1.7 Platform: MS Windows OS: Windows CE Status: REPORTED Severity: minor Priority: NOR Component: Tools/Selection Assignee: krita-bugs-n...@kde.org Reporter: me...@hotmail.fr Target Milestone: --- Created attachment 120268 --> https://bugs.kde.org/attachment.cgi?id=120268=edit Wrongly displayed selection. SUMMARY Sometimes, selection outlines is wrongly displayed : strange triangles appear on the top the selection "holes". STEPS TO REPRODUCE 1. On a white layer, draw some random shapes 2. Use the "Contiguous Selection Tool" on the background OBSERVED RESULT Depending on the selection shape, I can see added triangle outlines on the top of the drawn shapes. They go 1px higher than the real selection (wrong display of selection). EXPECTED RESULT Correct shape outline. SOFTWARE/OS VERSIONS Windows: 10 ADDITIONAL INFORMATION Tested with "OpenGL" and "DirectX 11 via ANGLE" renderers. Tested with NVidia 870M and Intel integrated graphic chipset. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 407824] New: The "Pixel Art Fill" base brush isn't symmetrical.
https://bugs.kde.org/show_bug.cgi?id=407824 Bug ID: 407824 Summary: The "Pixel Art Fill" base brush isn't symmetrical. Product: krita Version: 4.1.7 Platform: unspecified OS: MS Windows Status: REPORTED Severity: normal Priority: NOR Component: Brush Engine/Shape Assignee: krita-bugs-n...@kde.org Reporter: me...@hotmail.fr Target Milestone: --- SUMMARY The "Pixel Art Fill" base brush isn't symmetrical. STEPS TO REPRODUCE 1. Select "Pixel Art Fill" brush. 2. Use 6px size as an example, but the bug exists with various sizes. 3. You can use various ratio setting (eg. 0.50), it makes it even less symmetrical. 4. Click somewhere in the canvas. EXPECTED RESULT You get an unsymmetrical circle. ADDITIONAL INFORMATIONS Maybe the internal brush have an offset. I'm really not an expert, sorry but I can't help more. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 403597] New: Discover Crashes upon opening
https://bugs.kde.org/show_bug.cgi?id=403597 Bug ID: 403597 Summary: Discover Crashes upon opening Product: Discover Version: 5.14.5 Platform: Neon Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: discover Assignee: aleix...@kde.org Reporter: virtualspect...@gmail.com Target Milestone: --- Application: plasma-discover (5.14.5) Qt Version: 5.11.2 Frameworks Version: 5.54.0 Operating System: Linux 4.15.0-43-generic x86_64 Distribution: KDE neon User Edition 5.14 -- Information about the crash: - What I was doing when the application crashed: I just opened Discover normally. - Unusual behavior I noticed: Discover crashes upon opening the app. It doesn't even load, I just get a notification about it crashing. The crash can be reproduced every time. -- Backtrace: Application: Discover (plasma-discover), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7fde141a1200 (LWP 17477))] Thread 10 (Thread 0x7fddc9081700 (LWP 17491)): #0 0x7fde0f6f70b4 in __GI___libc_read (fd=39, buf=0x7fddc9080b90, nbytes=16) at ../sysdeps/unix/sysv/linux/read.c:27 #1 0x7fde09ca9cd0 in () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7fde09c65027 in g_main_context_check () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7fde09c654e0 in () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7fde09c6564c in g_main_context_iteration () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7fde1003604b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7fde0ffda30a in QEventLoop::exec(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7fde0fe05bba in QThread::exec() () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7fde0fe10adb in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #9 0x7fde0be016db in start_thread (arg=0x7fddc9081700) at pthread_create.c:463 #10 0x7fde0f70888f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 9 (Thread 0x7fddcbb87700 (LWP 17486)): #0 0x7fde0be09054 in __GI___pthread_getspecific (key=4) at pthread_getspecific.c:60 #1 0x7fde09c8d5f0 in g_thread_self () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7fde09c6563d in g_main_context_iteration () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7fde1003604b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7fde0ffda30a in QEventLoop::exec(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7fde0fe05bba in QThread::exec() () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7fde0fe10adb in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7fde0be016db in start_thread (arg=0x7fddcbb87700) at pthread_create.c:463 #8 0x7fde0f70888f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 8 (Thread 0x7fddd707b700 (LWP 17484)): #0 0x7fde0f6fbbf9 in __GI___poll (fds=0x7fddcc003de0, nfds=1, timeout=10050) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7fde09c65539 in () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7fde09c6564c in g_main_context_iteration () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7fde1003604b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7fde0ffda30a in QEventLoop::exec(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7fde0fe05bba in QThread::exec() () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7fde0fe10adb in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7fde0be016db in start_thread (arg=0x7fddd707b700) at pthread_create.c:463 #8 0x7fde0f70888f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 7 (Thread 0x7fdddc9a0700 (LWP 17483)): #0 0x7fde0f6fbbf9 in __GI___poll (fds=0x5559d40810c0, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7fde09c65539 in () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7fde09c658d2 in g_main_loop_run () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7fdddf8f9026 in () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 #4 0x7fde09c8d105 in () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7fde0be016db in start_thread (arg=0x7fdddc9a0700) at pthread_create.c:463 #6 0x7fde0f70888f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 6 (Thread 0x7f1a1700 (LWP 17482)): #0 0x7fde0f6f70b4 in __GI___libc_read (fd=14, buf=0x7f1a0ce0, nbytes=16) at ../sysdeps/unix/sysv/linux/read.c:27 #1 0x7fde09ca9cd0 in () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7fde09c65027 in g_main_context_check () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3
[krita] [Bug 391992] crash on close
https://bugs.kde.org/show_bug.cgi?id=391992 Melvin Vermeeren <m...@mel.vin> changed: What|Removed |Added CC||m...@mel.vin -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 392073] Segmentation fault on exit
https://bugs.kde.org/show_bug.cgi?id=392073 --- Comment #4 from Melvin Vermeeren <m...@mel.vin> --- (In reply to Antonio Rojas from comment #3) > (In reply to Melvin Vermeeren from comment #2) > > I also experience the segfault on exit on Arch Linux, since version 4.0. > > Also happened in the week before 4.0 release when I was running it from > > master (git). Everything else is working fine. > > That's bug 391992, unrelated to this. You are right, after downgrading sip packages the segfault stopped. I had not seen the closed bug. It does seem that the python plugins are unavailable after downgrading, not a problem as I don't need those right now. Thanks for the help! -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 392073] Segmentation fault on exit
https://bugs.kde.org/show_bug.cgi?id=392073
Melvin Vermeeren <m...@mel.vin> changed:
What|Removed |Added
CC||m...@mel.vin
--- Comment #2 from Melvin Vermeeren <m...@mel.vin> ---
I also experience the segfault on exit on Arch Linux, since version 4.0. Also
happened in the week before 4.0 release when I was running it from master
(git). Everything else is working fine.
System is up-to-date and no foreign (dropped from official repo) packages, my
DE is KDE. Note that Qt version here is 5.10.1. As I am running it from the
repos I cannot generate a proper stracktrace. Let me know if giving one will be
helpful to finding the problem. I will compile it without stripping symbols
then.
I attached some info that may help finding the issue below, hopefully it helps
finding the problem.
Thank you!
-- System info
Krita
Version: 4.0.0
OS Information
Build ABI: x86_64-little_endian-lp64
Build CPU: x86_64
CPU: x86_64
Kernel Type: linux
Kernel Version: 4.14.24-rt19-1-rt
Pretty Productname: Arch Linux
Product Type: arch
Product Version: unknown
OpenGL Info
Vendor: NVIDIA Corporation
Renderer: "GeForce GTX TITAN Black/PCIe/SSE2"
Version: "4.6.0 NVIDIA 390.42"
Shading language: 4.60 NVIDIA
Requested format: QSurfaceFormat(version 3.0, options
QFlags(DeprecatedFunctions), depthBufferSize 24,
redBufferSize -1, greenBufferSize -1, blueBufferSize -1, alphaBufferSize -1,
stencilBufferSize 8, samples -1, swapBehavior
QSurfaceFormat::SwapBehavior(DoubleBuffer), swapInterval 0, colorSpace
QSurfaceFormat::ColorSpace(DefaultColorSpace), profile
QSurfaceFormat::OpenGLContextProfile(CompatibilityProfile))
Current format:QSurfaceFormat(version 4.6, options
QFlags(DeprecatedFunctions), depthBufferSize 24,
redBufferSize 8, greenBufferSize 8, blueBufferSize 8, alphaBufferSize 0,
stencilBufferSize 8, samples -1, swapBehavior
QSurfaceFormat::SwapBehavior(DoubleBuffer), swapInterval 0, colorSpace
QSurfaceFormat::ColorSpace(DefaultColorSpace), profile
QSurfaceFormat::OpenGLContextProfile(CompatibilityProfile))
Version: 4.6
Supports deprecated functions true
is OpenGL ES: false
-- Terminal output (LC_ALL=C I use for OpenColorIO workaround as mentioned on
docs.krita.org)
$ LC_ALL=C krita
Setting XDG_DATA_DIRS
"/usr/bin/../share:/usr/share:/usr/share:/usr/local/share"
Override language: ""
OpenGL Info
Vendor: NVIDIA Corporation
Renderer: "GeForce GTX TITAN Black/PCIe/SSE2"
Version: "4.6.0 NVIDIA 390.42"
Shading language: 4.60 NVIDIA
Requested format: QSurfaceFormat(version 3.0, options
QFlags(DeprecatedFunctions), depthBufferSize 24,
redBufferSize -1, greenBufferSize -1, blueBufferSize -1, alphaBufferSize -1,
stencilBufferSize 8, samples -1, swapBehavior
QSurfaceFormat::SwapBehavior(DoubleBuffer), swapInterval 0, colorSpace
QSurfaceFormat::ColorSpace(DefaultColorSpace), profile
QSurfaceFormat::OpenGLContextProfile(CompatibilityProfile))
Current format:QSurfaceFormat(version 4.6, options
QFlags(DeprecatedFunctions), depthBufferSize 24,
redBufferSize 8, greenBufferSize 8, blueBufferSize 8, alphaBufferSize 0,
stencilBufferSize 8, samples -1, swapBehavior
QSurfaceFormat::SwapBehavior(DoubleBuffer), swapInterval 0, colorSpace
QSurfaceFormat::ColorSpace(DefaultColorSpace), profile
QSurfaceFormat::OpenGLContextProfile(CompatibilityProfile))
Version: 4.6
Supports deprecated functions true
is OpenGL ES: false
krita has opengl true
Available translations QSet("es", "fa", "sv", "lt", "pl", "fr", "nn", "se",
"vi", "it", "kk", "lv", "en_US", "sq", "he", "be", "eo", "ca", "da", "en_GB",
"ia", "pt_BR", "km", "zh_CN", "zh_TW", "ta", "hr", "ug", "el", "tg", "et",
"ms", "nds", "uk", "nl", "xh", "af", "wa", "uz", "pa", "ar", "ast", "pt", "ro",
"cs", "sl", "fi", "br", "mai", "hi", "cy", "sk", "ja", "hu", "fy",
"ca@valencia", "mk", "nb", "ko", "oc", "ru", "uz@cyrillic", "is", "th", "de",
"tr", "ne", "hne", "bs", "mr", "bg", "ga", "eu", "gl")
Available domain translations QSet("es",
[plasmashell] [Bug 384904] Checkboxes become bigger when changing fonts
https://bugs.kde.org/show_bug.cgi?id=384904 --- Comment #3 from Melvin Garcia <virtualspect...@gmail.com> --- As you can see in the screenshots some things look normal while others are blown up depending on the font I use. Only the default fonts work as intended, Ubuntu and Garuda both have issues. All apps looked normal, only some plasma shell elements are blown up. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 384904] Checkboxes become bigger when changing fonts
https://bugs.kde.org/show_bug.cgi?id=384904 --- Comment #2 from Melvin Garcia <virtualspect...@gmail.com> --- That bug has been discarded. I don't see a fix. I continued my testing and things got worse after logging out and back in. You can see more screenshots in this folder I've created. https://drive.google.com/folderview?id=0B8Sna2alGiTLUHBsRjg5RG5WbG8 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 384904] New: Checkboxes become bigger when changing fonts
https://bugs.kde.org/show_bug.cgi?id=384904 Bug ID: 384904 Summary: Checkboxes become bigger when changing fonts Product: plasmashell Version: 5.10.95 Platform: Neon Packages OS: Linux Status: UNCONFIRMED Severity: minor Priority: NOR Component: System Tray Assignee: plasma-b...@kde.org Reporter: virtualspect...@gmail.com Target Milestone: 1.0 I first discovered this bug in Kubuntu 17.04 using Plasma 10.5, then checked on the latest KDE Neon dev unstable build to check if I can recreate it. Some fonts, like Garuda and Ubuntu (I didn't test any other font) make the checkboxes in the network menu in the system tray bigger than they should be. I've uploaded files to Imgur to visually help with the bug. https://imgur.com/a/RooLk -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 357120] Remember rectangular region when retaking screenshot
https://bugs.kde.org/show_bug.cgi?id=357120 Melvin Vermeeren <m...@melvinvermeeren.com> changed: What|Removed |Added CC||m...@melvinvermeeren.com -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 356831] cannot send image to clipboard in background mode
https://bugs.kde.org/show_bug.cgi?id=356831 --- Comment #8 from Melvin Vermeeren <m...@melvinvermeeren.com> --- Hiding the option in the GUI for regular users makes sense, but why not allow the command-line flag for advanced users? It looks like quite a big amount of users would like that feature and I don' t see a valid reason to not add it as a command-line flag. You could print something like "This option requires a clipboard manager to function!" in the --help. Besides, Plasma 5 ships with the clipboard applet enabled. Alternatively, spectacle could have some sort of daemon mode in which case the daemon process keeps running so a clipboard manager isn't needed at all. I would prefer adding just the flag though. Please reconsider this hidden feature, it would make a lot of people happy. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 356950] [Regression][15.12.0] Empty message when viewing encrypted message in preview pane without auto-decrypt.
https://bugs.kde.org/show_bug.cgi?id=356950 Melvin Vermeeren <m...@melvinvermeeren.com> changed: What|Removed |Added CC||m...@melvinvermeeren.com -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 356955] [Desktop Grid] Allow zoom/pop effect on mouse-over to be disabled.
https://bugs.kde.org/show_bug.cgi?id=356955 Melvin Vermeeren <m...@melvinvermeeren.com> changed: What|Removed |Added CC||m...@melvinvermeeren.com -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 356955] New: [Desktop Grid] Allow zoom/pop effect on mouse-over to be disabled.
https://bugs.kde.org/show_bug.cgi?id=356955 Bug ID: 356955 Summary: [Desktop Grid] Allow zoom/pop effect on mouse-over to be disabled. Product: kwin Version: 5.5.1 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: wishlist Priority: NOR Component: effects-window-management Assignee: kwin-bugs-n...@kde.org Reporter: m...@melvinvermeeren.com After updating Plasma to 5.5 I noticed some new behaviour in desktop grid. Hovering over a window with the mouse causes it to zoom/pop. Personally I prefer desktop grid without that effect, it feels a bit smoother. The zooming also seems to cause some issues with alignment when exiting the grid (probably the zoom de-activating late). I would appreciate it if it could be turned off, probably through the "Desktop Grid" settings found in "Desktop Effects". Reproducible: Always Steps to Reproduce: 1. Update from Plasma 5.4 to 5.5. Actual Results: Hovering over a window in desktop grid makes it zoom/pop a bit. No way to turn it off. Expected Results: Hovering over a window in desktop grid makes it zoom/pop a bit. It can be turned off in the "Desktop Effects" => "Desktop Grid" settings. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 356950] New: [Regression][15.12.0] Empty message when viewing encrypted message in preview pane without auto-decrypt.
https://bugs.kde.org/show_bug.cgi?id=356950 Bug ID: 356950 Summary: [Regression][15.12.0] Empty message when viewing encrypted message in preview pane without auto-decrypt. Product: kmail2 Version: unspecified Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: message list Assignee: kdepim-b...@kde.org Reporter: m...@melvinvermeeren.com When viewing an encrypted message in the preview pane the message is empty, as if there is no body at all. This is with option "Security" => "Attempt decryption of encrypted messages when viewing" turned off. With the option turned on, it asks for passphrase and decrypts normally. The preview pane is also empty with the setting on before the passphrase is given (pinentry). Reproducible: Always Steps to Reproduce: 1. Make sure option "Security" => "Attempt decryption of encrypted messages when viewing" is OFF. 2. Preview an encrypted message in the preview pane. Actual Results: The preview pane only shows the header, the message body is blank as if there were none. Expected Results: The "This message is encrypted click here to decrypt" template as seen in previous versions. -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 356952] Option --clipboard saves file to picture directory instead of only copying to clipboard.
https://bugs.kde.org/show_bug.cgi?id=356952 Melvin Vermeeren <m...@melvinvermeeren.com> changed: What|Removed |Added CC||m...@melvinvermeeren.com -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 356952] New: Option --clipboard saves file to picture directory instead of only copying to clipboard.
https://bugs.kde.org/show_bug.cgi?id=356952 Bug ID: 356952 Summary: Option --clipboard saves file to picture directory instead of only copying to clipboard. Product: Spectacle Version: unspecified Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: General Assignee: m...@baloneygeek.com Reporter: m...@melvinvermeeren.com When taking a screenshot with --background and --clipboard the resulting screenshot is saved to the picture folder when it should only be copied to the clipboard. Reproducible: Always Steps to Reproduce: 1. Run something like "spectacle -rbc" or "spectacle -fbc" Actual Results: Screenshot is saved to picture directory and copied to clipboard. Expected Results: Screenshot is only copied to clipboard. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 356953] New: Allow style to be changed to pre-5.5 (thin line above application name)
https://bugs.kde.org/show_bug.cgi?id=356953 Bug ID: 356953 Summary: Allow style to be changed to pre-5.5 (thin line above application name) Product: plasmashell Version: 5.5.1 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: wishlist Priority: NOR Component: Task Manager Assignee: h...@kde.org Reporter: m...@melvinvermeeren.com CC: plasma-b...@kde.org In versions prior to 5.5, such as 5.4, there was a thin line above an application name indicating the active window and eventual notifications. Personally I prefer the old style, it somehow feels smoother and less obtrusive, probably because it uses less colour. I would appreciate if one could select the style he wants, perhaps through the task manager configuration. Screenshot of old style from YouTube thumb: https://i.ytimg.com/vi/FKAyy4Gfxrs/maxresdefault.jpg Reproducible: Always Steps to Reproduce: 1. Update from Plasma 5.4 to 5.5. Actual Results: Task manager style is different with no way to change it. Expected Results: Task manager style is different, but old style can selected through options. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 356953] Allow style to be changed to pre-5.5 (thin line above application name)
https://bugs.kde.org/show_bug.cgi?id=356953 Melvin Vermeeren <m...@melvinvermeeren.com> changed: What|Removed |Added Resolution|INVALID |FIXED --- Comment #2 from Melvin Vermeeren <m...@melvinvermeeren.com> --- Thanks for the quick reply, I managed to work out a solution that only changes the bask bar but leaves everything else. For anyone that wants the same in the future (only old taskbar, everything else new): 1. Open "Desktop Theme" settings. 2. Go to "Details" tab. 3. Tick "More" at the bottom. 4. Select desired theme and export it. Unzip it and change directory name to new-theme-name. 5. Edit "metadata.desktop" and set "X-KDE-PluginInfo-Name" to "new-theme-name". 6. Download and unzip only the classic "widgets/tasks.svgz" into "new-theme-name/widgets/tasks.svgz". - https://opendesktop.org/content/show.php?content=174360 (Breeze) - https://opendesktop.org/content/show.php?content=174361 (Breeze Dark) 7. Zip the "new-theme-name" directory. 8. Import the newly created zip file in the "Desktop Theme" dialog. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 356953] Allow style to be changed to pre-5.5 (thin line above application name)
https://bugs.kde.org/show_bug.cgi?id=356953 Melvin Vermeeren <m...@melvinvermeeren.com> changed: What|Removed |Added CC||m...@melvinvermeeren.com -- You are receiving this mail because: You are watching all bug changes.
