[ksysguard] [Bug 410127] New: Sorting processes by name, username, or window title displays results in an undefined order
https://bugs.kde.org/show_bug.cgi?id=410127 Bug ID: 410127 Summary: Sorting processes by name, username, or window title displays results in an undefined order Product: ksysguard Version: 5.16.2 Platform: openSUSE RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: ksysguard Assignee: ksysguard-b...@kde.org Reporter: smokythebearonthemount...@gmx.com Target Milestone: --- SUMMARY When using ksysguard 5.16.2 on either OpenSUSE Tumbleweed or Manjaro (stable), it is not possible to sort the process table by the name of the process, the username, or the window title. Clicking any of these column headers produces an up or down arrow as expected, but the process entries themselves are not sorted and instead appear in an undefined order with no obvious pattern. STEPS TO REPRODUCE 1. With the process table tab active, click on either 'Name,' 'Username,' or 'Window Title.' 2. 3. OBSERVED RESULT The list of processes will appear in an undefined order. EXPECTED RESULT The list of processes should be sorted be name, username, or window title depending on the column header selected. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: tested on both openSUSE Tumbleweed and Manjaro KDE, both versions current as of 23 July 2019. American English language is active in both cases. KDE Plasma Version: 5.16.2 KDE Frameworks Version: 5.59.0 Qt Version: 5.13.0 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kinfocenter] [Bug 387366] Energy consumption statistics not available
https://bugs.kde.org/show_bug.cgi?id=387366 Artem Grishin changed: What|Removed |Added CC||g...@list.ru -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 410103] KDevelop 5.3.3 abort due to "Failed to open repository" (Persistent Declaration Table)
https://bugs.kde.org/show_bug.cgi?id=410103 RJVB changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |NOT A BUG --- Comment #4 from RJVB --- Turns out this was a false alarm, it just took me way too long to get the idea to check who was using libKDevPlatformSerialisation. Sure enough I had a not-so-zombie KDevelop 5.3.2 process running which I thought I had quit before logging off (the 1st time after upgrading to 5.60.0). My issues started after logging in. Two things would probably have helped me think of this sooner: - using the hex version number in the version file, so I'd have seen an unexpected version_5030201 file. - storing the application PID in the file instead of keeping it empty. It's been a (potentially) interesting "experiment" though that has shown that the session can survive unexpected "failed to open registry" errors, i.e. that an immediate abort isn't required. -- You are receiving this mail because: You are watching all bug changes.
[print-manager] [Bug 410124] Plasmashell crashes when the CUPS service is on
https://bugs.kde.org/show_bug.cgi?id=410124 Rik Mills changed: What|Removed |Added Resolution|--- |DUPLICATE Status|REPORTED|RESOLVED CC||rikmi...@kubuntu.org --- Comment #1 from Rik Mills --- *** This bug has been marked as a duplicate of bug 326289 *** -- You are receiving this mail because: You are watching all bug changes.
[print-manager] [Bug 326289] plasma-desktop crashed after configuring printer applet [JobModel::updateJob]
https://bugs.kde.org/show_bug.cgi?id=326289 Rik Mills changed: What|Removed |Added CC||geneloca...@yandex.com --- Comment #32 from Rik Mills --- *** Bug 410124 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 410128] New: Discover crashing when clicking on certain apps
https://bugs.kde.org/show_bug.cgi?id=410128 Bug ID: 410128 Summary: Discover crashing when clicking on certain apps Product: Discover Version: 5.16.3 Platform: Neon Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: discover Assignee: lei...@leinir.dk Reporter: dougjsha...@gmail.com CC: aleix...@kde.org Target Milestone: --- Application: plasma-discover (5.16.3) Qt Version: 5.12.3 Frameworks Version: 5.60.0 Operating System: Linux 4.15.0-55-generic x86_64 Distribution: KDE neon User Edition 5.16 -- Information about the crash: - What I was doing when the application crashed: Browsing apps, clicked on a few apps, and after a few, Discover crashed when I clicked on one. -- 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 0x7ffae6b75e00 (LWP 9298))] Thread 11 (Thread 0x7ffa565d4700 (LWP 9376)): #0 0x7ffae1ebac18 in QThreadData::current (createIfNecessary=createIfNecessary@entry=true) at thread/qthread_unix.cpp:238 #1 0x7ffae20f2491 in postEventSourcePrepare (timeout=0x0, s=0x7ffa40003f10) at kernel/qeventdispatcher_glib.cpp:252 #2 postEventSourceCheck (source=0x7ffa40003f10) at kernel/qeventdispatcher_glib.cpp:269 #3 0x7ffadbc62fe1 in g_main_context_check () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7ffadbc63570 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7ffadbc636dc in g_main_context_iteration () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #6 0x7ffae20f1dcb in QEventDispatcherGlib::processEvents (this=0x7ffa4b20, flags=...) at kernel/qeventdispatcher_glib.cpp:424 #7 0x7ffae209303a in QEventLoop::exec (this=this@entry=0x7ffa565d3c60, flags=..., flags@entry=...) at kernel/qeventloop.cpp:225 #8 0x7ffae1eba4ca in QThread::exec (this=) at thread/qthread.cpp:531 #9 0x7ffae1ebbc72 in QThreadPrivate::start (arg=0x7ffa4c009cd0) at thread/qthread_unix.cpp:361 #10 0x7ffade5456db in start_thread (arg=0x7ffa565d4700) at pthread_create.c:463 #11 0x7ffae17bb88f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 10 (Thread 0x7ffa56dd5700 (LWP 9375)): #0 0x7ffae17aa0b4 in __GI___libc_read (fd=43, buf=0x7ffa56dd49e0, nbytes=16) at ../sysdeps/unix/sysv/linux/read.c:27 #1 0x7ffadbca82d0 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7ffadbc630b7 in g_main_context_check () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7ffadbc63570 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7ffadbc636dc in g_main_context_iteration () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7ffae20f1dcb in QEventDispatcherGlib::processEvents (this=0x7ffa4c000b20, flags=...) at kernel/qeventdispatcher_glib.cpp:424 #6 0x7ffae209303a in QEventLoop::exec (this=this@entry=0x7ffa56dd4bf0, flags=..., flags@entry=...) at kernel/qeventloop.cpp:225 #7 0x7ffae1eba4ca in QThread::exec (this=this@entry=0x5578c6eaba40) at thread/qthread.cpp:531 #8 0x7ffae54d3926 in QQuickPixmapReader::run (this=0x5578c6eaba40) at util/qquickpixmapcache.cpp:953 #9 0x7ffae1ebbc72 in QThreadPrivate::start (arg=0x5578c6eaba40) at thread/qthread_unix.cpp:361 #10 0x7ffade5456db in start_thread (arg=0x7ffa56dd5700) at pthread_create.c:463 #11 0x7ffae17bb88f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 9 (Thread 0x7ffa575d6700 (LWP 9372)): #0 0x7ffae17aa0b4 in __GI___libc_read (fd=29, buf=0x7ffa575d5a50, nbytes=16) at ../sysdeps/unix/sysv/linux/read.c:27 #1 0x7ffadbca82d0 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7ffadbc630b7 in g_main_context_check () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7ffadbc63570 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7ffadbc636dc in g_main_context_iteration () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7ffae20f1dcb in QEventDispatcherGlib::processEvents (this=0x7ffa48000b20, flags=...) at kernel/qeventdispatcher_glib.cpp:424 #6 0x7ffae209303a in QEventLoop::exec (this=this@entry=0x7ffa575d5c60, flags=..., flags@entry=...) at kernel/qeventloop.cpp:225 #7 0x7ffae1eba4ca in QThread::exec (this=) at thread/qthread.cpp:531 #8 0x7ffae1ebbc72 in QThreadPrivate::start (arg=0x5578c464ecb0) at thread/qthread_unix.cpp:361 #9 0x7ffade5456db in start_thread (arg=0x7ffa575d6700) at pthread_create.c:463 #10 0x7ffae17bb88f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 8 (Thread 0x7ffaa944b700 (LWP 9310)): #0 0x7ffade54b9f3 in futex_wait_cancelable (private=, expected=0, futex_word=0x5578c48df150) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 __pthread_cond_wait_co
[kwin] [Bug 410129] New: System completly hang after opening a 144MB file with kwrite
https://bugs.kde.org/show_bug.cgi?id=410129 Bug ID: 410129 Summary: System completly hang after opening a 144MB file with kwrite Product: kwin Version: 5.16.3 Platform: Neon Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kwin-bugs-n...@kde.org Reporter: isalgue...@gmail.com Target Milestone: --- Application: kwin_x11 (5.16.3) Qt Version: 5.12.3 Frameworks Version: 5.60.0 Operating System: Linux 4.18.0-25-generic x86_64 Distribution: KDE neon User Edition 5.16 -- Information about the crash: - What I was doing when the application crashed: I downloaded SoapUI installer from here https://www.soapui.org/downloads/soapui.html. It downloads a shell script, so I opened with kwrite to take a look (I tend to not execute random things from the internet without checking them first ¯\_(ツ)_/¯) without realising that ths script was so huge. Moved myself around that shell script with Av Pag and everything stoped responding, I couldn't even log in in a text mode terminal. After a restart, this kwin segfault report was here. -- Backtrace: Application: KWin (kwin_x11), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7fd5f36e8880 (LWP 2515))] Thread 5 (Thread 0x7fd5ba44d700 (LWP 2622)): #0 0x7fd5ebfb39f3 in futex_wait_cancelable (private=, expected=0, futex_word=0x7fd5ef56cfb8) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 __pthread_cond_wait_common (abstime=0x0, mutex=0x7fd5ef56cf68, cond=0x7fd5ef56cf90) at pthread_cond_wait.c:502 #2 __pthread_cond_wait (cond=0x7fd5ef56cf90, mutex=0x7fd5ef56cf68) at pthread_cond_wait.c:655 #3 0x7fd5ef276844 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Script.so.5 #4 0x7fd5ef276889 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Script.so.5 #5 0x7fd5ebfad6db in start_thread (arg=0x7fd5ba44d700) at pthread_create.c:463 #6 0x7fd5f304888f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 4 (Thread 0x7fd5d150c700 (LWP 2617)): #0 0x7fd5f303bcf6 in __GI_ppoll (fds=fds@entry=0x7fd5c8000d28, nfds=nfds@entry=1, timeout=, timeout@entry=0x0, sigmask=sigmask@entry=0x0) at ../sysdeps/unix/sysv/linux/ppoll.c:39 #1 0x7fd5f058fab1 in ppoll (__ss=, __timeout=, __nfds=, __fds=) at /usr/include/x86_64-linux-gnu/bits/poll2.h:77 #2 qt_ppoll (timeout_ts=0x0, nfds=1, fds=0x7fd5c8000d28) at kernel/qcore_unix.cpp:132 #3 qt_safe_poll (fds=0x7fd5c8000d28, nfds=1, timeout_ts=timeout_ts@entry=0x0) at kernel/qcore_unix.cpp:153 #4 0x7fd5f05911be in QEventDispatcherUNIX::processEvents (this=, flags=...) at kernel/qeventdispatcher_unix.cpp:500 #5 0x7fd5f053503a in QEventLoop::exec (this=this@entry=0x7fd5d150bd00, flags=..., flags@entry=...) at kernel/qeventloop.cpp:225 #6 0x7fd5f035c4ca in QThread::exec (this=) at thread/qthread.cpp:531 #7 0x7fd5ea9cb115 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5 #8 0x7fd5f035dc72 in QThreadPrivate::start (arg=0x555824097dd0) at thread/qthread_unix.cpp:361 #9 0x7fd5ebfad6db in start_thread (arg=0x7fd5d150c700) at pthread_create.c:463 #10 0x7fd5f304888f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 3 (Thread 0x7fd5d1f4e700 (LWP 2566)): [KCrash Handler] #6 QHashNode >::same_key (key0=..., h0=2494525897, this=0x50) at /usr/include/x86_64-linux-gnu/qt5/QtCore/qhash.h:158 #7 QHash >::findNode (this=this@entry=0x7fd5c4001828, akey=..., h=h@entry=2494525897) at /usr/include/x86_64-linux-gnu/qt5/QtCore/qhash.h:919 #8 0x7fd5ead6bbb2 in QHash >::findNode (ahp=, akey=..., this=0x7fd5c4001828) at /usr/include/x86_64-linux-gnu/qt5/QtCore/qhash.h:938 #9 QHash >::insert (avalue=..., akey=..., this=0x7fd5c4001828) at /usr/include/x86_64-linux-gnu/qt5/QtCore/qhash.h:774 #10 KPackage::PackageLoader::listPackages (this=0x7fd5c4001a70, packageFormat=..., packageRoot=...) at ./src/kpackage/packageloader.cpp:283 #11 0x7fd5f2b9ffdd in KWin::ScriptedEffectLoader::findAllEffects (this=) at ./effectloader.cpp:292 #12 0x7fd5f2ba7dd7 in QtConcurrent::StoredConstMemberFunctionPointerCall0, KWin::ScriptedEffectLoader>::runFunctor (this=0x5558243addc0) at /usr/include/x86_64-linux-gnu/qt5/QtConcurrent/qtconcurrentstoredfunctioncall.h:228 #13 QtConcurrent::RunFunctionTask >::run (this=0x5558243addc0) at /usr/include/x86_64-linux-gnu/qt5/QtConcurrent/qtconcurrentrunbase.h:108 #14 0x7fd5f03623e2 in QThreadPoolThread::run (this=0x5558240383b0) at thread/qthreadpool.cpp:99 #15 0x7fd5f035dc72 in QThreadPrivate::start (arg=0x5558240383b0) at thread/qthread_unix.cpp:361 #16 0x7fd5ebfad6db in start_thread (arg=0x7fd5d1f4e700) at pthread_create.c:463 #17 0x7fd5f304888f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 2 (Thread 0x7fd5d
[Spectacle] [Bug 409798] Spectacle Copy To Clipboard Doesn't Work Properly Under Wayland Session
https://bugs.kde.org/show_bug.cgi?id=409798 David Edmundson changed: What|Removed |Added Resolution|--- |UPSTREAM Status|CONFIRMED |RESOLVED CC||k...@davidedmundson.co.uk --- Comment #3 from David Edmundson --- Thanks https://codereview.qt-project.org/c/qt/qtwayland/+/268352 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 410059] 'Blur' via Filter layer producing white/transparent edges; only disappears when I make a new layer and delete the new layer
https://bugs.kde.org/show_bug.cgi?id=410059 --- Comment #2 from Soulty Ragevin --- (In reply to Ahab Greybeard from comment #1) > You have a multi-group, multi-layer file there. Can you simplify the > situation and use just one image layer and a filter mask to see if it still > happens? (It seems to be a Filter Mask, not a Filter Layer.) > Does this happen with any other files you have? > Does it happen if you go back to using 4.2.2 with this file? Hello! I tried what you suggested. Surprisingly, it doesn't happen on the one you suggested even when it's inside a group or opened in 4.2.2. It only happens on my file shown in the video. Tt happens when I create a NEW FILTER LAYER, not a Filter mask. I've tried opening it up on 4.2.2. The edges are there, and disappears when I hide/unhide the filter layer. New update: I installed 4.2.3 after uninstalling 4.2.2. The edges now disappear when I hide/unhide the filter layer, similar to 4.2.2. This didn't happen on the first video using 4.2.3 Here are the 2 videos showing the bug. I've also attached the .kra file showing the problem and the one that isn't. https://drive.google.com/open?id=1CrpDIzGWOJiXz-2dTKVi4l0uBx7L4ad2 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 410079] All brushes cant be used on surface Pro 3 dotted lines
https://bugs.kde.org/show_bug.cgi?id=410079 Boudewijn Rempt changed: What|Removed |Added CC||b...@valdyas.org Platform|Windows CE |MS Windows OS|Windows CE |MS Windows -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 409914] Circular *refresh* and update-* icons have arrows that are facing in the wrong direction
https://bugs.kde.org/show_bug.cgi?id=409914 victorhck changed: What|Removed |Added CC||victor...@opensuse.org --- Comment #8 from victorhck --- This also fix the wrong direction icon in Kickoff menu and log out screen? (the arrows in that points to left). -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 409001] when opened message (incapsulated by outlook) kmail crashes
https://bugs.kde.org/show_bug.cgi?id=409001 Matthias Welwarsky changed: What|Removed |Added CC||ma...@welwarsky.de -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 409257] Baloo index gets corrupted, no results
https://bugs.kde.org/show_bug.cgi?id=409257 Igor Poboiko changed: What|Removed |Added Status|CONFIRMED |RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 410034] Gradient labels are not translated (and two are not translatable)
https://bugs.kde.org/show_bug.cgi?id=410034 Karl Ove Hufthammer changed: What|Removed |Added Resolution|FIXED |--- Status|RESOLVED|REOPENED --- Comment #2 from Karl Ove Hufthammer --- Reopening. The ‘Foreground to Transparent’ and ‘Foreground to Background’ strings are now translatable, and show up as translated in the UI, but the *other* gradient names (from the .ggr files) are still not shown as translated in the UI. To clarify, it’s possible to *translate* all the gradient names (e.g. ‘GPS Fire Blueish’). But the translations (except ‘Foreground to Transparent’ and ‘Foreground to Background’) are not actually used in the UI. -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 409499] Krunner returns empty item
https://bugs.kde.org/show_bug.cgi?id=409499 Igor Poboiko changed: What|Removed |Added CC||igor.pobo...@gmail.com --- Comment #3 from Igor Poboiko --- This can be related to bug 409257, which should be fixed in KF 5.60. Can you try the most recent version? -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 409914] Circular *refresh* and update-* icons have arrows that are facing in the wrong direction
https://bugs.kde.org/show_bug.cgi?id=409914 --- Comment #9 from Kai Uwe Broulik --- Yes -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 408936] Vector objects fail to render after loading on large files
https://bugs.kde.org/show_bug.cgi?id=408936 --- Comment #3 from Boudewijn Rempt --- This is actually a limit in qpainter/qimage api: see for instance https://stackoverflow.com/questions/7080052/qimage-qpixmap-size-limitations. To avoid this we should implement rendering to tiles instead of one big QImage in KisShapeLayerCanvas. This is quite a job, but not impossible. An impossible but interesting alternative would be to implement a QPainterEngine that works directly on a KisPaintDevice. -- You are receiving this mail because: You are watching all bug changes.
[kdevplatform] [Bug 410130] New: explicitly assigning value of variable to itself
https://bugs.kde.org/show_bug.cgi?id=410130 Bug ID: 410130 Summary: explicitly assigning value of variable to itself Product: kdevplatform Version: git master Platform: unspecified OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: util Assignee: kdevelop-bugs-n...@kde.org Reporter: kdebugzi...@ebasoft.com.pl Target Milestone: --- kdevplatform/util/dbus_socket_transformer/main.cpp:253:14: warning: explicitly assigning value of variable of type 'std::string' (aka 'basic_string') to itself path = path; ^ -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 410131] New: performing pointer arithmetic on a null pointer has undefined behavior if the offset is nonzero
https://bugs.kde.org/show_bug.cgi?id=410131 Bug ID: 410131 Summary: performing pointer arithmetic on a null pointer has undefined behavior if the offset is nonzero Product: kdevelop Version: git master Platform: Other OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: Language Support: QML/JavaScript Assignee: kdevelop-bugs-n...@kde.org Reporter: kdebugzi...@ebasoft.com.pl Target Milestone: --- plugins/qmljs/duchain/frameworks/nodejs.cpp:78:36: warning: performing pointer arithmetic on a null pointer has undefined behavior if the offset is nonzero (QmlJS::AST::Node*)nullptr + index, ~~ ^ -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 387775] KWin touch screen edge creates a 1 pixel dead zone on that edge that doesn't accept mouse clicks outside of full-screen mode
https://bugs.kde.org/show_bug.cgi?id=387775 Andrey Rahmatullin changed: What|Removed |Added CC||w...@wrar.name -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 410059] 'Blur' via Filter layer producing white/transparent edges; only disappears when I make a new layer and delete the new layer
https://bugs.kde.org/show_bug.cgi?id=410059 --- Comment #3 from Ahab Greybeard --- Thank you for the original .kra file. Your image content size seems to be different from the image size. (This sounds strange but it's the only way I can try to describe it). If I do Image -> Trim To Image Size, the white border no longer happens on opening the file. Did you make a small change to the canvas size at any stage? [Before I noticed that, I noted that you have the Copy blending mode used for the Blur Filter Layer. If that mode is set to Normal, then the white boundary effect does not happen. This can't be the only reason because your other .kra file also has its Blur Filter Layer set to Copy blending mode and does not show the white border effect. - I'll leave the explanation for that to someone who knows about the details of blending modes.] -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 410132] New: Content Menu don't show correctly
https://bugs.kde.org/show_bug.cgi?id=410132 Bug ID: 410132 Summary: Content Menu don't show correctly Product: plasmashell Version: 5.16.3 Platform: Neon Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Desktop Containment Assignee: se...@kde.org Reporter: ser...@iskynet.es CC: plasma-b...@kde.org Target Milestone: 1.0 Created attachment 121689 --> https://bugs.kde.org/attachment.cgi?id=121689&action=edit Capture SUMMARY STEPS TO REPRODUCE 1. Active blur effects and transparency on KDE Plasma. 2. Select a file and drag to other windows or desktop. 3. When you drag file, you view context menu. If you move cursor by different options, this not show correctly. I attatch a capture. SOFTWARE/OS VERSIONS Linux/KDE Plasma: KDE NEON 18.04 (available in About System) KDE Plasma Version: 5.16.3 KDE Frameworks Version: 5.60.0 Qt Version: 5.12.3 -- You are receiving this mail because: You are watching all bug changes.
[kde-windows] [Bug 293610] khelpcenter do not show any help
https://bugs.kde.org/show_bug.cgi?id=293610 Ron Brickle changed: What|Removed |Added CC||rb19...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 410133] New: Horizontal line strike throug whole tabbbar
https://bugs.kde.org/show_bug.cgi?id=410133 Bug ID: 410133 Summary: Horizontal line strike throug whole tabbbar Product: konsole Version: 19.04.3 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: tabbar Assignee: konsole-de...@kde.org Reporter: hanni...@astral.lodz.pl Target Milestone: --- Created attachment 121690 --> https://bugs.kde.org/attachment.cgi?id=121690&action=edit Horizontal line screenshot >From some time (probably since 19.04.0) a horizontal line strike through my tabbar in konsole. It is good visible only in Oxygen theme. In Fusion and MS Windows there is something but above tabs. In Breeze everything looks OK. It can be Oxygen problem, but I don't observe this kind of problem in other KDE apps. OBSERVED RESULT Line above tabs. EXPECTED RESULT No line above tabs. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Slackware current with Alien plasma packages. KDE Plasma Version: 5.16.3 KDE Frameworks Version: 5.60.0 Qt Version: 5.13.0 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 410059] 'Blur' via Filter layer producing white/transparent edges; only disappears when I make a new layer and delete the new layer
https://bugs.kde.org/show_bug.cgi?id=410059 --- Comment #4 from Soulty Ragevin --- (In reply to Ahab Greybeard from comment #3) > Thank you for the original .kra file. Your image content size seems to be > different from the image size. (This sounds strange but it's the only way I > can try to describe it). If I do Image -> Trim To Image Size, the white > border no longer happens on opening the file. Did you make a small change to > the canvas size at any stage? > > [Before I noticed that, I noted that you have the Copy blending mode used > for the Blur Filter Layer. If that mode is set to Normal, then the white > boundary effect does not happen. This can't be the only reason because your > other .kra file also has its Blur Filter Layer set to Copy blending mode and > does not show the white border effect. - I'll leave the explanation for that > to someone who knows about the details of blending modes.] Thank you so much for the quick response! I tried to do the Image -> Trim To Image size. It fixed the problem, even if the filter layer's blending mode is set to Copy. >Did you make a small change to > the canvas size at any stage? Yes, I've only did once, when I was still in sketching phase where I cropped the canvas. Is there an explanation how the trimming stopped this problem? Thank you for also the new insight on the Trimming part. I might do that in the future in case something like this happens. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 410134] New: Crash Baloo File Indexing
https://bugs.kde.org/show_bug.cgi?id=410134 Bug ID: 410134 Summary: Crash Baloo File Indexing Product: frameworks-baloo Version: 5.59.0 Platform: openSUSE RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: Baloo File Daemon Assignee: stefan.bru...@rwth-aachen.de Reporter: fay...@hotmail.fr Target Milestone: --- Application: baloo_file (5.59.0) Qt Version: 5.13.0 Frameworks Version: 5.59.0 Operating System: Linux 5.1.16-1-default x86_64 Distribution: "openSUSE Tumbleweed" -- Information about the crash: - What I was doing when the application crashed: Hello, When i reboot my computer, i have a message like : "Sorry :( Baloo File Indexing crash". The crash can be reproduced sometimes. -- Backtrace: Application: Baloo File Indexing Daemon (baloo_file), signal: Aborted Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f946c6e06c0 (LWP 2922))] Thread 3 (Thread 0x7f9469dd6700 (LWP 3323)): [KCrash Handler] #6 0x7f946f04fdd1 in raise () from /lib64/libc.so.6 #7 0x7f946f039549 in abort () from /lib64/libc.so.6 #8 0x7f946d49e523 in mdb_assert_fail.constprop () from /usr/lib64/liblmdb-0.9.23.so #9 0x7f946d49cbb5 in mdb_page_dirty.lto_priv () from /usr/lib64/liblmdb-0.9.23.so #10 0x7f946d495da6 in mdb_page_alloc.isra.0.lto_priv () from /usr/lib64/liblmdb-0.9.23.so #11 0x7f946d49d193 in mdb_page_touch.lto_priv () from /usr/lib64/liblmdb-0.9.23.so #12 0x7f946d494cfc in mdb_cursor_touch () from /usr/lib64/liblmdb-0.9.23.so #13 0x7f946d49771c in mdb_cursor_put () from /usr/lib64/liblmdb-0.9.23.so #14 0x7f946d49a64b in mdb_put () from /usr/lib64/liblmdb-0.9.23.so #15 0x7f946ee276d7 in Baloo::DocumentDB::put (this=0x7f9469dd5a70, docId=, list=...) at /usr/src/debug/baloo5-5.59.0-1.2.x86_64/src/engine/documentdb.cpp:79 #16 0x7f946ee15807 in Baloo::WriteTransaction::addDocument (this=0x55938e88a4d0, doc=...) at /usr/src/debug/baloo5-5.59.0-1.2.x86_64/src/engine/writetransaction.cpp:62 #17 0x7f946ee159de in Baloo::Transaction::addDocument (doc=..., this=this@entry=0x7f9469dd5b80, this=this@entry=0x7f9469dd5b80, doc=...) at /usr/src/debug/baloo5-5.59.0-1.2.x86_64/src/engine/transaction.cpp:252 #18 0x55938e454e95 in Baloo::UnindexedFileIndexer::run (this=0x55938e830d90) at /usr/include/qt5/QtCore/qrefcount.h:60 #19 0x7f946e896432 in QThreadPoolThread::run (this=0x55938e83c500) at thread/qthreadpool.cpp:99 #20 0x7f946e893112 in QThreadPrivate::start (arg=0x55938e83c500) at thread/qthread_unix.cpp:360 #21 0x7f946d4fdfaa in start_thread () from /lib64/libpthread.so.0 #22 0x7f946f11173f in clone () from /lib64/libc.so.6 Thread 2 (Thread 0x7f946a989700 (LWP 2932)): #0 0x7ffcc45f2649 in ?? () #1 0x7f946f11f3b7 in clock_gettime () from /lib64/libc.so.6 #2 0x7f946eab05f1 in qt_clock_gettime (ts=0x7f946a988ae0, clock=1) at kernel/qelapsedtimer_unix.cpp:175 #3 do_gettime (frac=, sec=) at kernel/qelapsedtimer_unix.cpp:166 #4 qt_gettime () at kernel/qelapsedtimer_unix.cpp:175 #5 0x7f946eaaef09 in QTimerInfoList::updateCurrentTime (this=this@entry=0x7f9464005150) at kernel/qtimerinfo_unix.cpp:91 #6 0x7f946eaaf4d5 in QTimerInfoList::timerWait (this=0x7f9464005150, tm=...) at kernel/qtimerinfo_unix.cpp:388 #7 0x7f946eab0a4e in timerSourcePrepareHelper (timeout=0x7f946a988ba4, src=) at kernel/qeventdispatcher_glib.cpp:162 #8 timerSourcePrepare (source=, timeout=0x7f946a988ba4) at kernel/qeventdispatcher_glib.cpp:166 #9 0x7f946cd5cc8f in g_main_context_prepare () from /usr/lib64/libglib-2.0.so.0 #10 0x7f946cd5d2cb in ?? () from /usr/lib64/libglib-2.0.so.0 #11 0x7f946cd5d46f in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #12 0x7f946eab0ceb in QEventDispatcherGlib::processEvents (this=0x7f9464000b20, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #13 0x7f946ea592eb in QEventLoop::exec (this=this@entry=0x7f946a988d70, flags=..., flags@entry=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:140 #14 0x7f946e891f91 in QThread::exec (this=) at ../../include/QtCore/../../src/corelib/global/qflags.h:120 #15 0x7f946ee4c4f6 in ?? () from /usr/lib64/libQt5DBus.so.5 #16 0x7f946e893112 in QThreadPrivate::start (arg=0x7f946eeced80) at thread/qthread_unix.cpp:360 #17 0x7f946d4fdfaa in start_thread () from /lib64/libpthread.so.0 #18 0x7f946f11173f in clone () from /lib64/libc.so.6 Thread 1 (Thread 0x7f946c6e06c0 (LWP 2922)): #0 0x7f946f106cbf in poll () from /lib64/libc.so.6 #1 0x7f946cd5d39e in ?? () from /usr/lib64/libglib-2.0.so.0 #2 0x7f946cd5d46f in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #3 0x7f946eab0cd1 in QEventDispatcherGlib::processEvents (this=0x55938e81c960, flags=...) at kernel/qeventdispatcher_glib.
[kscreenlocker] [Bug 374890] kscreenlocker_greet freezes
https://bugs.kde.org/show_bug.cgi?id=374890 --- Comment #8 from Jan-Matthias Braun --- Just to make sure that the driver does not interfere I checked: the backtraces after not setting MESA_LOADER_DRIVER_OVERRIDE=iris look the same as with the iris driver. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 410135] New: L or GSM (Local or Global Selection Mask) is not updated on-canvas after Invert Selection
https://bugs.kde.org/show_bug.cgi?id=410135 Bug ID: 410135 Summary: L or GSM (Local or Global Selection Mask) is not updated on-canvas after Invert Selection Product: krita Version: nightly build (please specify the git hash!) Platform: Debian stable OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Layer Stack Assignee: krita-bugs-n...@kde.org Reporter: ahab.greybe...@hotmail.co.uk Target Milestone: --- SUMMARY This is observed on the latest nightly appimage 4.3.0-prealpha (git 585f1c6) and back to the 4.2.1 build. The LSM or GSM is not updated on-canvas if Select -> Invert Selection (Ctrl+Shift+I) is done. The Layers Docker thumbnail for the LSM or GSM is updated (often quite slowly). STEPS TO REPRODUCE 1. Create a new file and add an LSM to a layer or a GSM to the image. 2. Select the LSM or GSM and use the selection outline tools (or use monochrome paint) to create a selection which shows as red/white. 3. Do an Invert Selection operation. OBSERVED RESULT The on-canvas display of the LSM or GSM is not updated to show the inversion. You have to toggle the LSM or GSM off/on or select a different layer (then go back to the LSM or GSM) before the on-canvas display is updated. While the LSM or GSM has been inverted but not updated on-canvas, you can paint on it and the paint operation shows the correct appearance locally at the painted locations. EXPECTED RESULT The LSM or GSM on-canvas appearance should update after the Invert operation. SOFTWARE/OS VERSIONS Version: 4.3.0-prealpha (git 585f1c6) Languages: en_GB, en Hidpi: true Qt Version (compiled): 5.12.4 Version (loaded): 5.12.4 OS Information Build ABI: x86_64-little_endian-lp64 Build CPU: x86_64 CPU: x86_64 Kernel Type: linux Kernel Version: 4.19.0-5-amd64 Pretty Productname: Debian GNU/Linux 10 (buster) Product Type: debian Product Version: 10 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 409823] [Wayland] List of network connections is empty when I open the KCM via plasma-nm applet
https://bugs.kde.org/show_bug.cgi?id=409823 --- Comment #4 from Patrick Silva --- yes, this bug only occurs on Wayland session. Maybe related to this Qt bug https://bugreports.qt.io/browse/QTBUG-54888 -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 409517] [Wayland] KMail freezes
https://bugs.kde.org/show_bug.cgi?id=409517 juha.heljora...@iki.fi changed: What|Removed |Added CC||juha.heljora...@iki.fi --- Comment #3 from juha.heljora...@iki.fi --- Same thing here. kmail-19.04.2-2.fc30.x86_64 KDE Frameworks Version: 5.59.0 Qt Version: 5.14.4 gdb: Thread 1 (Thread 0x7f736b23c040 (LWP 4565)): #0 syscall () at ../sysdeps/unix/sysv/linux/x86_64/syscall.S:38 #1 0x7f737e1cea25 in QtLinuxFutex::_q_futex (val3=0, addr2=0x0, val2=0, val=3, op=0, addr=0x7f735e25c2b0 ) at thread/qfutex_p.h:105 #2 QtLinuxFutex::futexWait > (expectedValue=0x3, futex=...) at thread/qfutex_p.h:107 #3 lockInternal_helper (timeout=-1, elapsedTimer=0x0, d_ptr=...) at thread/qmutex_linux.cpp:142 #4 QBasicMutex::lockInternal (this=this@entry=0x7f735e25c2b0 ) at thread/qmutex_linux.cpp:159 #5 0x7f737e1cea88 in QMutex::lock (this=this@entry=0x7f735e25c2b0 ) at thread/qmutex.cpp:227 #6 0x7f735e1bfced in QMutexLocker::QMutexLocker (m=0x7f735e25c2b0 , this=) at /usr/include/qt5/QtCore/qmutex.h:206 #7 QtWaylandClient::QWaylandWindow::waitForFrameSync (this=0x55bd7911f010, timeout=100) at qwaylandwindow.cpp:664 #8 0x7f735de1c022 in QtWaylandClient::QWaylandGLContext::swapBuffers (this=0x55bd7c4debd0, surface=) at ../../../../hardwareintegration/client/wayland-egl/qwaylandglcontext.cpp:566 #9 0x7f737e780881 in QOpenGLContext::swapBuffers (this=0x55bd7c4da960, surface=surface@entry=0x55bd783b9970) at kernel/qopenglcontext.cpp:1115 #10 0x7f737e9d65cf in QPlatformBackingStore::composeAndFlush (this=this@entry=0x55bd795004b0, window=0x55bd783b9960, region=..., offset=..., textures=textures@entry=0x7f737f2061e0 <(anonymous namespace)::Q_QGS_qt_dummy_platformTextureList::innerFunction()::holder>, translucentBackground=translucentBackground@entry=false) at painting/qplatformbackingstore.cpp:463 #11 0x7f737ece5c06 in QWidgetBackingStore::qt_flush (widgetBackingStore=, widgetTextures=0x7f737f2061e0 <(anonymous namespace)::Q_QGS_qt_dummy_platformTextureList::innerFunction()::holder>, tlw=, backingStore=, region=..., widget=0x55bd7954e720) at kernel/qwidgetbackingstore.cpp:154 #12 QWidgetBackingStore::qt_flush (widget=0x55bd7954e720, region=..., backingStore=, tlw=, widgetTextures=, widgetBackingStore=) at kernel/qwidgetbackingstore.cpp:83 #13 0x7f737ece7618 in QWidgetBackingStore::flush (this=this@entry=0x55bd783ba230, widget=widget@entry=0x0) at kernel/qwidgetbackingstore.cpp:1442 #14 0x7f737ece8c40 in QWidgetBackingStore::endPaint (beginPaintInfo=, backingStore=, cleaned=..., this=0x55bd783ba230) at kernel/qwidgetbackingstore.cpp:363 #15 QWidgetBackingStore::doSync (this=) at kernel/qwidgetbackingstore.cpp:1426 #16 0x7f737ece8fc1 in QWidgetBackingStore::sync (this=0x55bd783ba230) at kernel/qwidgetbackingstore.cpp:1204 #17 0x7f737ed01065 in QWidgetPrivate::syncBackingStore (this=0x55bd78df3130) at kernel/qwidget.cpp:1961 #18 0x7f737ed19bc8 in QWidget::event (this=this@entry=0x55bd7954e720, event=event@entry=0x7ffe0a2de4b0) at kernel/qwidget.cpp:9264 #19 0x7f737ee2d908 in QMainWindow::event (this=this@entry=0x55bd7954e720, event=event@entry=0x7ffe0a2de4b0) at widgets/qmainwindow.cpp:1339 #20 0x7f737dc45e0b in KMainWindow::event (this=this@entry=0x55bd7954e720, ev=ev@entry=0x7ffe0a2de4b0) at /usr/src/debug/kf5-kxmlgui-5.59.0-2.fc30.x86_64/src/kmainwindow.cpp:877 #21 0x7f737dc928fb in KXmlGuiWindow::event (this=0x55bd7954e720, ev=0x7ffe0a2de4b0) at /usr/src/debug/kf5-kxmlgui-5.59.0-2.fc30.x86_64/src/kxmlguiwindow.cpp:125 #22 0x7f737ecd6af6 in QApplicationPrivate::notify_helper (this=, receiver=0x55bd7954e720, e=0x7ffe0a2de4b0) at kernel/qapplication.cpp:3737 #23 0x7f737ecdfe80 in QApplication::notify(QObject*, QEvent*) () at kernel/qapplication.cpp:3483 #24 0x7f737e375ae8 in QCoreApplication::notifyInternal2 (receiver=0x55bd7954e720, event=0x7ffe0a2de4b0) at kernel/qcoreapplication.cpp:1084 #25 0x7f737ece9be3 in QWidgetBackingStore::sendUpdateRequest (this=this@entry=0x55bd783ba230, widget=0x55bd7954e720, updateTime=updateTime@entry=QWidgetBackingStore::UpdateNow) at kernel/qwidgetbackingstore.cpp:504 #26 0x7f737ecea91e in QWidgetBackingStore::sendUpdateRequest (updateTime=QWidgetBackingStore::UpdateNow, widget=, this=0x55bd783ba230) at kernel/qwidgetbackingstore.cpp:474 #27 QWidgetBackingStore::markDirty (this=0x55bd783ba230, rect=..., widget=widget@entry=0x55bd7954e720, updateTime=updateTime@entry=QWidgetBackingStore::UpdateNow, bufferState=bufferState@entry=QWidgetBackingStore::BufferValid) at kernel/qwidgetbackingstore.cpp:678 #28 0x7f737ed02f31 in QWidgetPrivate::repaint (r=..., this=) at ../../include/QtWidgets/5.12.4/QtWidgets/private/../../../../../src/widgets/kernel/qwidget_p.h:139 #29 QWidget::repaint (this=, rect=...) at kernel/qwidget.cpp:11072 #30 0x7f737ed02fa0 in QWidg
[kdeconnect] [Bug 409079] Cant open filesystem on Android device
https://bugs.kde.org/show_bug.cgi?id=409079 --- Comment #5 from Albert Vaca --- Could you also give us the versions of kdeconnect on the desktop? -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 409518] Visiting Fonts KCM changes antialliasing settings without warning
https://bugs.kde.org/show_bug.cgi?id=409518 Fabian Vogt changed: What|Removed |Added Resolution|--- |WAITINGFORINFO Status|CONFIRMED |NEEDSINFO --- Comment #19 from Fabian Vogt --- I still cannot reproduce this bug on openSUSE TW, and I'm trying quite hard. I noticed that all reports about this bug seem to come from users of Arch or derivatives, so maybe it's something with compile options or other library versions. Can someone build it with -fsanitize=address and/or run with valgrind? I think that we're chasing some uninitialized variables. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 409829] Baloo file indexing daemon crashes immediately after login
https://bugs.kde.org/show_bug.cgi?id=409829 --- Comment #5 from Patrick Silva --- Today Arch updated to lmdb 0.9.24-1 and this crash persists. -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 385885] Multi-monitor HiDPI screens with scaling: Rectangular Region mode causes graphical corruption on one of the screens
https://bugs.kde.org/show_bug.cgi?id=385885 --- Comment #28 from Guo Yunhe --- The rectangular Region mode is a full screen window/widget painted with full screenshot, and users draw a rectangle on it. You can still select all area in the window. Actually everything works fine, just the window was placed in a wrong position. Sometimes it is left offset, sometimes it is top offset. So I guess it is a KWin related. Maybe KWin developers can help with it. -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 374890] kscreenlocker_greet freezes
https://bugs.kde.org/show_bug.cgi?id=374890 David Edmundson changed: What|Removed |Added Status|REPORTED|NEEDSINFO CC||k...@davidedmundson.co.uk Resolution|--- |WAITINGFORINFO --- Comment #9 from David Edmundson --- Could you include all threads. "thread apply all bt" This just shows that we're blocked and waiting on the render thread to complete. Can you reproduce with /usr/lib64/libexec/kscreenlocker_greet --testing ? -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 385885] Multi-monitor HiDPI screens with scaling: Rectangular Region mode causes graphical corruption on one of the screens
https://bugs.kde.org/show_bug.cgi?id=385885 --- Comment #29 from Guo Yunhe --- Created attachment 121692 --> https://bugs.kde.org/attachment.cgi?id=121692&action=edit Similar issue with Qt Creator window When I was about to use Qt Creator to test something, I get this wired window: all content are moved left. I can also reproduce it with Kate and some other Qt app. No matter how I resize the window it doesn't help. Look similar to this bug. If it happens to different software, no matter window position or widget position, then it is more likely a Qt issue. -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 385885] Multi-monitor HiDPI screens with scaling: Rectangular Region mode causes graphical corruption on one of the screens
https://bugs.kde.org/show_bug.cgi?id=385885 --- Comment #30 from Guo Yunhe --- I opened a bug ticket at Qt website. Subscribe if you are interested! https://bugreports.qt.io/browse/QTBUG-77149 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 409518] Visiting Fonts KCM changes antialliasing settings without warning
https://bugs.kde.org/show_bug.cgi?id=409518 --- Comment #20 from mthw0 --- I (OP) have checked and I don't seem to have this problem anymore. I remember deleting "~/.config/kcmfonts" but I am not sure if it is what fixed this. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 408402] "Extract Zone" not working
https://bugs.kde.org/show_bug.cgi?id=408402 Evert Vorster changed: What|Removed |Added Status|CONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #5 from Evert Vorster --- Hey, thanks for fixing this one! It took me a while to realize that there is a new branch, which explains the lag in reporting this bug as fixed. Kind regards, Evert -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 360478] Desktop widgets are permanently repositioned when fullscreen games lower display resolution
https://bugs.kde.org/show_bug.cgi?id=360478 Marcin Juszkiewicz changed: What|Removed |Added CC||mar...@juszkiewicz.com.pl --- Comment #42 from Marcin Juszkiewicz --- Fedora 30 Plasma 5.15.5 Same shit. Probably gets closed one day as WONTFIX/INVALID/KTHXBYE but who knows... -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 410059] 'Blur' via Filter layer producing white/transparent edges; only disappears when I make a new layer and delete the new layer
https://bugs.kde.org/show_bug.cgi?id=410059 Ahab Greybeard changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |NOT A BUG --- Comment #5 from Ahab Greybeard --- There are probably many interacting effects here but the main thing is that your image size and canvas size seem to be not identical in some way. There may also be off canvas content affecting things but I didn't try to find it. I'll set this bug report to Resolved - Not A Bug but you can reopen it by changing its status in the future if you have similar or related problems. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 410055] filter layer and filter mask pop ups are locked to the center of the screen with dark opaque screen overlay
https://bugs.kde.org/show_bug.cgi?id=410055 Boudewijn Rempt changed: What|Removed |Added Status|REPORTED|RESOLVED CC||b...@valdyas.org Resolution|--- |NOT A BUG --- Comment #7 from Boudewijn Rempt --- The difference is that since this release, those dialogs now have the main window as parent. That makes your window manager treat them this way; having the parent set is the proper thing, and your window manager should have an option to disable this behaviour. -- You are receiving this mail because: You are watching all bug changes.
[ktorrent] [Bug 409568] Options disappear on bottom bar in version 5.1.1-2
https://bugs.kde.org/show_bug.cgi?id=409568 Christoph Feck changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |DOWNSTREAM --- Comment #2 from Christoph Feck --- Thanks for the update; changing status. -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 406707] Copying files to KDE connect on android using Dolphin fails
https://bugs.kde.org/show_bug.cgi?id=406707 Albert Vaca changed: What|Removed |Added Latest Commit|b9a0f310c7c6d1b2f6e036718a3 |https://invent.kde.org/kde/ |d20d3279833a1 |kdeconnect-android/commit/4 ||be5800b8be20d3612904373e7e8 ||40fb24eb6b27 --- Comment #17 from Albert Vaca --- Git commit 4be5800b8be20d3612904373e7e840fb24eb6b27 by Albert Vaca. Committed on 23/07/2019 at 12:58. Pushed by albertvaka into branch 'master'. Disable google backups of the app This was causing problems when a restored app remembered the list of storage locations it had access to, but it no longer could access them. In the past, this also caused problems when a restored app would carry with it a certificate that was no longer valid on the new device because the device id had changed. M +1-0AndroidManifest.xml https://invent.kde.org/kde/kdeconnect-android/commit/4be5800b8be20d3612904373e7e840fb24eb6b27 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 410136] New: Brush Editor does not show the blending mode until that blending mode is changed
https://bugs.kde.org/show_bug.cgi?id=410136 Bug ID: 410136 Summary: Brush Editor does not show the blending mode until that blending mode is changed Product: krita Version: unspecified Platform: Debian stable OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: Usability Assignee: krita-bugs-n...@kde.org Reporter: ahab.greybe...@hotmail.co.uk Target Milestone: --- SUMMARY This minor UI bug happens in all appimage versions from 4.1.7 onwards. STEPS TO REPRODUCE 1. Start krita and select any brush preset that has a blending mode. 2. Open the brush editor and select the Blending Mode page. Note that the blending mode is not displayed there (it's blank) but it is shown correctly in the Toolbar display. 3. In the brush editor, change the blending mode to any other mode (note that is is displayed correctly) and then back to what it should be. OBSERVED RESULT >From this point on, the blending mode for all brush presets is correctly shown in the brush editor. The fault returns when krita is Quit and restarted. EXPECTED RESULT The brush editor should correctly display the blending mode at all times. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kcrash] [Bug 409961] Dr.Konqui doesn't report plasmashell crash when using Wayland
https://bugs.kde.org/show_bug.cgi?id=409961 Harald Sitter changed: What|Removed |Added Assignee|unassigned-b...@kde.org |fa...@kde.org Status|NEEDSINFO |REPORTED CC||kdelibs-b...@kde.org Resolution|WAITINGFORINFO |--- Product|drkonqi |frameworks-kcrash Version|unspecified |5.60.0 Component|general |general --- Comment #7 from Harald Sitter --- Right, so I *think* I've found it happening, but it's not really drkonqi's fault. What likely happens is that GIO is being used by something (in my case discover) and GIO will trip over a filedescriptor that was closed by KCrash before drkonqi starts. GIO has a forced fatality attached to this so essentially plasmashell crashes while we are trying to trace the crash. I've not really found an easy way to prevent this. Possibly coordinate closing with drkonqi may prevent this sort of problem. I.e. since we now have a socket from kcrash to drkonqi we could have drkonqi tell kcrash when it SIGSTOP'ed the process, at this point kcrash can safely close the file descriptors without risking that a still running thread will fall over the closed FD. Alas, I don't really know enough about this, or even if there is a reason that the FDs are closed before starting drkonqi. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 409257] Baloo index gets corrupted, no results
https://bugs.kde.org/show_bug.cgi?id=409257 --- Comment #31 from Gerson --- yes, I confirm. After upgrading to 5.60 the bug is gone! Thanks! -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 410136] Brush Editor does not show the blending mode until that blending mode is changed
https://bugs.kde.org/show_bug.cgi?id=410136 Scott Petrovic changed: What|Removed |Added Status|REPORTED|CONFIRMED CC||scottpetro...@gmail.com Ever confirmed|0 |1 --- Comment #1 from Scott Petrovic --- I can confirm this on git master -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 409518] Visiting Fonts KCM changes antialliasing settings without warning
https://bugs.kde.org/show_bug.cgi?id=409518 Antonio Rojas changed: What|Removed |Added CC||aro...@archlinux.org --- Comment #21 from Antonio Rojas --- I can reproduce, investigating - it's unrelated to 08ec9a036bf5b3ee102938ad332f624adc1060b9 -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 400593] In Coregrind, use statx for some internal syscalls if [f]stat[64] fail
https://bugs.kde.org/show_bug.cgi?id=400593 --- Comment #1 from Petar Jovanovic --- Is everyone OK with this change? -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 410137] New: New palette are not saved anywhere and lost when Krita close
https://bugs.kde.org/show_bug.cgi?id=410137 Bug ID: 410137 Summary: New palette are not saved anywhere and lost when Krita close Product: krita Version: 4.2.3 Platform: Appimage OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Usability Assignee: krita-bugs-n...@kde.org Reporter: i...@davidrevoy.com Target Milestone: --- Hi, I made a new palette using the GUI; then when I closed Krita I lost it. I tried to reproduce and I realised the palette were not saved at all. (nothing in .local/share/krita/palettes/) To reproduce: = 1. Open a document, add the Palette docker 2. Click on the drop down (color icon) to access palettes, then press the "+" on the bottom of this drop-down. 3. A dialog pop-up; name the palette (eg. XYZ), press OK 4. Add color to the palette (in the color selector switch color, and click on empty slot to fill with color slots). 5. Close document, close Krita. 6. Re-open Krita, new document 7. Try to find the created palette. Result: === The list doesn't contain the new created palette at previous session. (nothing too in .local/share/krita/palettes/). I lost a detailed palette I took 30min to do because I was pretty sure the feature was designed to save the change I was doing to the palette... Expected: = To find the palette (eg. XYZ) in the list with latest modifications. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 400872] Add nanoMIPS support to Valgrind
https://bugs.kde.org/show_bug.cgi?id=400872 --- Comment #8 from Petar Jovanovic --- I will try to review and merge these changes hopefully soon. If anyone has any objections, please raise them here. -- You are receiving this mail because: You are watching all bug changes.
[drkonqi] [Bug 383863] Absence of DrKonqi icon in a tray after same crash reappeared
https://bugs.kde.org/show_bug.cgi?id=383863 --- Comment #6 from Harald Sitter --- Git commit 3eeb0ce5bc1ee61dc9c9ff4376cad5302db4e2de by Harald Sitter. Committed on 23/07/2019 at 13:42. Pushed by sitter into branch 'Plasma/5.16'. guard against plasmashell being properly dead and not showing the SNI Summary: when plasmashell is particularly dead and not even able to restart, the SNI host may still be around when we check for it in the main.cpp as its disappearance from dbus is tied to sockets closing and dbus' event loop reacting to that. so there is a race potential that can cause the SNI to not actually be visible on account of the SNI host (plasmashell) being dead even though we expected SNI support to be available. guard against this scenario by starting an automatic activation timer when the notification service disappears. should it not reappear within 10 second we consider it dead and show the dialog automatically as the user won't be seeing the SNI anymore Possibly fixing Test Plan: - crash something so the sni appears - kill plasma - wait 10s - dialog appears - same again - restart plasma before 10s have passed - sni appears again in plasmashell Reviewers: #plasma Subscribers: davidedmundson, plasma-devel Tags: #plasma Differential Revision: https://phabricator.kde.org/D22553 M +18 -0src/statusnotifier.cpp https://commits.kde.org/drkonqi/3eeb0ce5bc1ee61dc9c9ff4376cad5302db4e2de -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 409518] Visiting Fonts KCM changes antialliasing settings without warning
https://bugs.kde.org/show_bug.cgi?id=409518 Filip Fila changed: What|Removed |Added CC||filipfila@gmail.com --- Comment #22 from Filip Fila --- [Manjaro] I also experienced this. It was triggered by changing the font and then it wouldn't stop happening. I deleted fonts.conf in the home dir and generated it with qt5ct. Haven't touched the Fonts kcm since and have been left alone by the bug. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kcrash] [Bug 409961] Dr.Konqui doesn't report plasmashell crash when using Wayland
https://bugs.kde.org/show_bug.cgi?id=409961 --- Comment #8 from Patrick Silva --- I just noticed that this issue also affects X11 session. Drkonqi shows the same "The debugger has quit unexpectedly" message seen in my screenshot. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 410103] KDevelop 5.3.3 abort due to "Failed to open repository" (Persistent Declaration Table)
https://bugs.kde.org/show_bug.cgi?id=410103 RJVB changed: What|Removed |Added Attachment #121676|0 |1 is obsolete|| --- Comment #5 from RJVB --- Created attachment 121693 --> https://bugs.kde.org/attachment.cgi?id=121693&action=edit no abort and more informative version_XXX file This implements the earlier workaround to prevent the abort(), and my idea to make the version_XXX file a bit more useful to understand the kind of issue I was confronted with. The number in the filename is stored in hex (so it becomes evident which KDevelop version created the file) and the file itself contains the application PIC. Depending on feedback here I may clean this up where necessary and put it up for review on phab after the summer (and 5.4 release) -- You are receiving this mail because: You are watching all bug changes.
[klipper] [Bug 409366] Clearing clipboard history does not clear the clipboard / Content of clipboard is lost after closing application
https://bugs.kde.org/show_bug.cgi?id=409366 --- Comment #7 from ultr --- Fix: https://phabricator.kde.org/D22684 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 410137] New palette are not saved anywhere and lost when Krita close
https://bugs.kde.org/show_bug.cgi?id=410137 wolthera changed: What|Removed |Added Status|REPORTED|CONFIRMED CC||griffinval...@gmail.com Ever confirmed|0 |1 --- Comment #1 from wolthera --- Hi, I think new palettes are saved by default into the document, which IS very confusing default behaviour. Let's change it :) -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 410137] New palette are saved by default into the document: This is confusing behaviour.
https://bugs.kde.org/show_bug.cgi?id=410137 wolthera changed: What|Removed |Added Summary|New palette are not saved |New palette are saved by |anywhere and lost when |default into the document: |Krita close |This is confusing ||behaviour. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 410138] New: Strange characters displayed in emails when viewed as html or plain text, when there should be a quote character
https://bugs.kde.org/show_bug.cgi?id=410138 Bug ID: 410138 Summary: Strange characters displayed in emails when viewed as html or plain text, when there should be a quote character Product: kmail2 Version: 5.11.3 Platform: Neon Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: misc Assignee: kdepim-b...@kde.org Reporter: nick.craig@gmail.com Target Milestone: --- Created attachment 121694 --> https://bugs.kde.org/attachment.cgi?id=121694&action=edit email in HTML view showing odd character (circled) instead of ' character SOFTWARE/OS VERSIONS KDE NEON Linux/KDE Plasma: Neon 5.16.3 KDE Plasma Version: 5.16.3 KDE Frameworks Version: 5.60.0 Qt Version: 5.12.3 Kernel 4.15.0-55-generic 64bit SUMMARY When displaying some emails (either HTML or text mode) you get some strange looking characters inserted amongst the text as shown below. Here's an extract... notice the '┬' character 4th line up from the bottom and 2nd line up from the bottom. Images not loading? Click Here to view this newsletter in your browser.(http://emailclick.imlgrouponthenet.net/profile/S-23344@aawG9tsEOImiTXAR1Zm2UUCtJMmysgmQ6-mvyV8oq5U.@11) EPDT's July 2019 issue is now available, in print & digital editions! Read the digital issue(http://emailclick.imlgrouponthenet.net/email/S-23344@1068604@aawG9tsEOImiTXAR1Zm2UUCtJMmysgmQ6-mvyV8oq5U.@) now or register to receive the print magazine(http://emailclick.imlgrouponthenet.net/email/S-23344@1068605@aawG9tsEOImiTXAR1Zm2UUCtJMmysgmQ6-mvyV8oq5U.@) each month. This monthтАЩs issue(http://emailclick.imlgrouponthenet.net/email/S-23344@1068606@aawG9tsEOImiTXAR1Zm2UUCtJMmysgmQ6-mvyV8oq5U.@) contains features on Electromechanical technologies and Mil/Aero applications, as well as EPDT's twice-yearly IoT & Industry 4.0 supplement(http://emailclick.imlgrouponthenet.net/email/S-23344@1068607@aawG9tsEOImiTXAR1Zm2UUCtJMmysgmQ6-mvyV8oq5U.@). ┬а (http://emailclick.imlgrouponthenet.net/email/S-23344@1068608@aawG9tsEOImiTXAR1Zm2UUCtJMmysgmQ6-mvyV8oq5U.@) ┬а ┬а Inside EPDT's July issue: Take a look at the two attachment pictures. One picture is the HTML version of the above email. The other is how it is rendered properly in gmail. STEPS TO REPRODUCE Just look through your emails for odd looking characters OBSERVED RESULT See one of the attachments, I have circled the strange character where there should be a ' character. EXPECTED RESULT See one of the attachments for the HTML email rendered correctly in gmail. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 410138] Strange characters displayed in emails when viewed as html or plain text, when there should be a quote character
https://bugs.kde.org/show_bug.cgi?id=410138 --- Comment #1 from Nick --- Created attachment 121695 --> https://bugs.kde.org/attachment.cgi?id=121695&action=edit Email properly rendered in gmail, correctly showing ' character -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 410138] Strange characters displayed in emails when viewed as html or plain text, when there should be a quote character
https://bugs.kde.org/show_bug.cgi?id=410138 --- Comment #2 from Nick --- This is not just the incorrect display of quote characters but also the copyright character and I would imagine lots of other non alpha numeric characters. I'm not exactly sure when this bug appeared but I think it might have been after a recent update. -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 385885] Multi-monitor HiDPI screens with scaling: Rectangular Region mode causes graphical corruption on one of the screens
https://bugs.kde.org/show_bug.cgi?id=385885 Nate Graham changed: What|Removed |Added URL||https://bugreports.qt.io/br ||owse/QTBUG-77149 --- Comment #31 from Nate Graham --- Thanks so much! -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 409798] Spectacle Copy To Clipboard Doesn't Work Properly Under Wayland Session
https://bugs.kde.org/show_bug.cgi?id=409798 Nate Graham changed: What|Removed |Added URL||https://codereview.qt-proje ||ct.org/c/qt/qtwayland/+/268 ||352 -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 410139] New: Konsole not getting locale, print messages in spanish instead englisg
https://bugs.kde.org/show_bug.cgi?id=410139 Bug ID: 410139 Summary: Konsole not getting locale, print messages in spanish instead englisg Product: konsole Version: 19.04.3 Platform: Kubuntu Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: konsole-de...@kde.org Reporter: luiseduard...@gmail.com Target Milestone: --- SUMMARY In the beginning I installed Kubuntu in spanish. Then I changed to english, so I can use the console output for documentation purposes. It works on GNOME with Wayland, but it fails on KDE Plasma, and it still print messages in spanish. Locale output: luis@starseedstation:~$ locale LANG=en_US.UTF-8 LANGUAGE=en_US:es LC_CTYPE="en_US.UTF-8" LC_NUMERIC="en_US.UTF-8" LC_TIME="en_US.UTF-8" LC_COLLATE="en_US.UTF-8" LC_MONETARY="en_US.UTF-8" LC_MESSAGES="en_US.UTF-8" LC_PAPER="en_US.UTF-8" LC_NAME="en_US.UTF-8" LC_ADDRESS="en_US.UTF-8" LC_TELEPHONE="en_US.UTF-8" LC_MEASUREMENT="en_US.UTF-8" LC_IDENTIFICATION="en_US.UTF-8" LC_ALL=en_US.UTF-8 And I think that should be enough, right? STEPS TO REPRODUCE 1. Install Kubuntu in spanish. 2. Change the environment to english. 3. Run any command that prints a system output: sudo apt-get update OBSERVED RESULT luis@starseedstation:~$ sudo apt-get update [sudo] contraseña para luis: Obj:1 https://repo.skype.com/deb stable InRelease Ign:2 http://dl.google.com/linux/chrome/deb stable InRelease Obj:3 http://ppa.launchpad.net/ansible/ansible/ubuntu disco InRelease Obj:4 https://download.docker.com/linux/ubuntu disco InRelease Obj:5 http://dl.google.com/linux/chrome/deb stable Release Obj:6 http://archive.ubuntu.com/ubuntu disco InRelease Obj:7 http://archive.ubuntu.com/ubuntu disco-updates InRelease Obj:8 http://ppa.launchpad.net/kubuntu-ppa/backports/ubuntu disco InRelease Obj:10 http://archive.ubuntu.com/ubuntu disco-backports InRelease Obj:11 http://archive.ubuntu.com/ubuntu disco-security InRelease Leyendo lista de paquetes... Hecho EXPECTED RESULT I exepct the first two lines and also the last one in english, not spanish. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: Kubuntu 19.04 / 5.0.0-21-generic (available in About System) KDE Plasma Version: KDE Plasma 5.16.3 KDE Frameworks Version: 5.60.0 Qt Version: 5.12.2 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 410140] New: Plasma crashed when dropping file on desktop widget
https://bugs.kde.org/show_bug.cgi?id=410140 Bug ID: 410140 Summary: Plasma crashed when dropping file on desktop widget Product: plasmashell Version: 5.16.3 Platform: Fedora RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: zawer...@gmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 Application: plasmashell (5.16.3) Qt Version: 5.12.4 Frameworks Version: 5.60.0 Operating System: Linux 5.1.18-300.fc30.x86_64 x86_64 Distribution: "Fedora release 30 (Thirty)" -- Information about the crash: - What I was doing when the application crashed: Select any file in Dolphin and drag&drop it on plasma desktop changing widget. The crash can be reproduced every time. -- Backtrace: Application: Plasma (plasmashell), signal: Bus error Using host libthread_db library "/lib64/libthread_db.so.1". 29return SYSCALL_CANCEL (poll, fds, nfds, timeout); [Current thread is 1 (Thread 0x7fecf2f9ad00 (LWP 29743))] Thread 8 (Thread 0x7fecc318a700 (LWP 29773)): #0 0x7fecf90a14d5 in futex_wait_cancelable (private=0, expected=0, futex_word=0x5583d88977a4) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 0x7fecf90a14d5 in __pthread_cond_wait_common (abstime=0x0, mutex=0x5583d8897750, cond=0x5583d8897778) at pthread_cond_wait.c:502 #2 0x7fecf90a14d5 in __pthread_cond_wait (cond=0x5583d8897778, mutex=0x5583d8897750) at pthread_cond_wait.c:655 #3 0x7fecf9bfd283 in QWaitCondition::wait(QMutex*, QDeadlineTimer) () at /lib64/libQt5Core.so.5 #4 0x7fecf9bfd311 in QWaitCondition::wait(QMutex*, unsigned long) () at /lib64/libQt5Core.so.5 #5 0x7fecfb99af59 in () at /lib64/libQt5Quick.so.5 #6 0x7fecfb99b1fd in () at /lib64/libQt5Quick.so.5 #7 0x7fecf9bf7786 in () at /lib64/libQt5Core.so.5 #8 0x7fecf909b5a2 in start_thread (arg=) at pthread_create.c:486 #9 0x7fecf9876303 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 7 (Thread 0x7fecc3fff700 (LWP 29771)): #0 0x7fecf8285ced in g_mutex_lock () at /lib64/libglib-2.0.so.0 #1 0x7fecf8239244 in g_main_context_acquire () at /lib64/libglib-2.0.so.0 #2 0x7fecf823a095 in () at /lib64/libglib-2.0.so.0 #3 0x7fecf823a313 in g_main_context_iteration () at /lib64/libglib-2.0.so.0 #4 0x7fecf9df3bf3 in QEventDispatcherGlib::processEvents(QFlags) () at /lib64/libQt5Core.so.5 #5 0x7fecf9d9d9eb in QEventLoop::exec(QFlags) () at /lib64/libQt5Core.so.5 #6 0x7fecf9bf6635 in QThread::exec() () at /lib64/libQt5Core.so.5 #7 0x7fecd0922c4c in KCupsConnection::run() () at /lib64/libkcupslib.so #8 0x7fecf9bf7786 in () at /lib64/libQt5Core.so.5 #9 0x7fecf909b5a2 in start_thread (arg=) at pthread_create.c:486 #10 0x7fecf9876303 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 6 (Thread 0x7fecd282b700 (LWP 29758)): #0 0x7fecf90a14d5 in futex_wait_cancelable (private=0, expected=0, futex_word=0x5583d7f3a4c0) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 0x7fecf90a14d5 in __pthread_cond_wait_common (abstime=0x0, mutex=0x5583d7f3a470, cond=0x5583d7f3a498) at pthread_cond_wait.c:502 #2 0x7fecf90a14d5 in __pthread_cond_wait (cond=0x5583d7f3a498, mutex=0x5583d7f3a470) at pthread_cond_wait.c:655 #3 0x7fecf9bfd283 in QWaitCondition::wait(QMutex*, QDeadlineTimer) () at /lib64/libQt5Core.so.5 #4 0x7fecf9bfd311 in QWaitCondition::wait(QMutex*, unsigned long) () at /lib64/libQt5Core.so.5 #5 0x7fecfb99af59 in () at /lib64/libQt5Quick.so.5 #6 0x7fecfb99b1fd in () at /lib64/libQt5Quick.so.5 #7 0x7fecf9bf7786 in () at /lib64/libQt5Core.so.5 #8 0x7fecf909b5a2 in start_thread (arg=) at pthread_create.c:486 #9 0x7fecf9876303 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 5 (Thread 0x7fecd3fff700 (LWP 29757)): #0 0x7fecf8285ce0 in g_mutex_lock () at /lib64/libglib-2.0.so.0 #1 0x7fecf82395cb in g_main_context_prepare () at /lib64/libglib-2.0.so.0 #2 0x7fecf823a10b in () at /lib64/libglib-2.0.so.0 #3 0x7fecf823a313 in g_main_context_iteration () at /lib64/libglib-2.0.so.0 #4 0x7fecf9df3bf3 in QEventDispatcherGlib::processEvents(QFlags) () at /lib64/libQt5Core.so.5 #5 0x7fecf9d9d9eb in QEventLoop::exec(QFlags) () at /lib64/libQt5Core.so.5 #6 0x7fecf9bf6635 in QThread::exec() () at /lib64/libQt5Core.so.5 #7 0x7fecfb90ee4a in () at /lib64/libQt5Quick.so.5 #8 0x7fecf9bf7786 in () at /lib64/libQt5Core.so.5 #9 0x7fecf909b5a2 in start_thread (arg=) at pthread_create.c:486 #10 0x7fecf9876303 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 4 (Thread 0x7fece4847700 (LWP 29755)): #0 0x7fecf986b5c7 in __GI___poll (fds=0x7fecd4004a30, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.
[plasmashell] [Bug 410140] Plasma crashed when dropping file on desktop widget
https://bugs.kde.org/show_bug.cgi?id=410140 --- Comment #1 from Yaroslav Sidlovsky --- Created attachment 121696 --> https://bugs.kde.org/attachment.cgi?id=121696&action=edit desktop_widget.png Screenshot of desktop widget added, just to avoid misunderstandings :) -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 410138] Strange characters displayed in emails when viewed as html or plain text, when there should be a quote character
https://bugs.kde.org/show_bug.cgi?id=410138 --- Comment #3 from Nick --- Again, here's a direct copy of the rendered text in a HTML email hereтАЩs a cool little email exclusive for your weekend тАУ weтАЩre trimming 15% off your takeaway*. And thatтАЩs whether you order Friday, Saturday or Sunday. Tuck in! and here's what that specific section of the email source looks like. here=E2=80=99s a cool little email exclusive fo= r your weekend =E2=80=93 we=E2=80=99re trimming 15% off your takeaway*. And= that=E2=80=99s whether you order Friday, Saturday or Sunday. Tuck in! Notice the =E2=80=99 where there should be a ` or ' -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 410138] Strange characters displayed in emails when viewed as html or plain text, when there should be a quote character
https://bugs.kde.org/show_bug.cgi?id=410138 --- Comment #4 from Nick --- Here's another easy way to reproduce the problem by sending yourself an email containing a special character such as the copyright symbol. To insert a special character, from the menu edit->insert special character. select European Latin 1 supplement. Click on the copyright symbol. The copyright symbol correctly appears in your composed email but after you have sent that email to yourself and view it in kmail the copyright symbol is now a й If you view that same email in gmail the copyright symbol is displayed correctly. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 410138] Strange characters displayed in emails when viewed as html or plain text, when there should be a quote character
https://bugs.kde.org/show_bug.cgi?id=410138 --- Comment #5 from Nick --- So kmail manages to display the correct character when composing the email but not when viewing the email, however that same email when viewed in gmail displays the copyright symbol correctly. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kholidays] [Bug 366182] KHolidays needs to support event categories
https://bugs.kde.org/show_bug.cgi?id=366182 Alexander Potashev changed: What|Removed |Added CC||aspotas...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 410141] New: Cannot enter accented characters in Payee field
https://bugs.kde.org/show_bug.cgi?id=410141 Bug ID: 410141 Summary: Cannot enter accented characters in Payee field Product: kmymoney Version: 5.0.4 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kmymoney-de...@kde.org Reporter: schoenes-...@web.de Target Milestone: --- SUMMARY When trying to enter an accented character such as é in the "Payee" field of the Transaction form, the accent will be suppressed and the base character shown instead. In the "Filter" field, however, it works perfectly, also in the Payee administration. STEPS TO REPRODUCE 1. Enter a new or existing transaction 2. Type ' followed by e, for instance. 3. OBSERVED RESULT Accent is being suppressed EXPECTED RESULT Accent should be shown SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: Fedora 30 GNOME Version 3.32.2 (available in About System) KDE Plasma Version: KDE Frameworks Version: 5.59.0 Qt Version: 5.12.4 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 365153] False holidays, at least for Poland
https://bugs.kde.org/show_bug.cgi?id=365153 Alexander Potashev changed: What|Removed |Added CC||aspotas...@gmail.com --- Comment #15 from Alexander Potashev --- Seems fixed in https://cgit.kde.org/kholidays.git/commit/?id=d1f6062a818cfab2adef6a3219ab8b9154b8c78a -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 357642] Calendar no longer highlights holidays like Bank Holidays, Christmas, New Year
https://bugs.kde.org/show_bug.cgi?id=357642 Alexander Potashev changed: What|Removed |Added CC||aspotas...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kwidgetsaddons] [Bug 77997] Show holidays in KDatePicker
https://bugs.kde.org/show_bug.cgi?id=77997 Alexander Potashev changed: What|Removed |Added CC||aspotas...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 410138] Strange characters displayed in emails when viewed as html or plain text, when there should be a quote character
https://bugs.kde.org/show_bug.cgi?id=410138 --- Comment #6 from Nick --- In the email header for the above simple email I have Content-Type: text/plain; charset="iso-8859-1" So it's like the kmail code that displays the email is using the wrong character encoding to render the text correctly. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 407730] Incorrect display of events in the calendar
https://bugs.kde.org/show_bug.cgi?id=407730 Alexander Potashev changed: What|Removed |Added CC||aspotas...@gmail.com --- Comment #2 from Alexander Potashev --- Same problem here. Operating System: Fedora 30 KDE Plasma Version: 5.15.5 KDE Frameworks Version: 5.59.0 Qt Version: 5.12.4 Kernel Version: 5.1.16-300.fc30.x86_64 OS Type: 64-bit Processors: 8 × Intel® Core™ i7-6700HQ CPU @ 2.60GHz Memory: 15,4 ГиБ -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 410141] Cannot enter accented characters in Payee field
https://bugs.kde.org/show_bug.cgi?id=410141 --- Comment #1 from schoenes-...@web.de --- Just updated to KMyMoney 5.0.5; still the same problem. -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 410141] Cannot enter accented characters in Payee field
https://bugs.kde.org/show_bug.cgi?id=410141 schoenes-...@web.de changed: What|Removed |Added Version|5.0.4 |5.0.5 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 383634] Calendar plasmoid to display holiday events "At a glance"
https://bugs.kde.org/show_bug.cgi?id=383634 Alexander Potashev changed: What|Removed |Added CC||aspotas...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 372090] Plasma show events only after second enable of holidays
https://bugs.kde.org/show_bug.cgi?id=372090 Alexander Potashev changed: What|Removed |Added CC||aspotas...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kdeplasma-addons] [Bug 399038] Untranslatable calendar plugin names
https://bugs.kde.org/show_bug.cgi?id=399038 Alexander Potashev changed: What|Removed |Added Flags||Translation_missing+ -- You are receiving this mail because: You are watching all bug changes.
[korganizer] [Bug 187116] Holidays > 1 day show as multiple holidays.
https://bugs.kde.org/show_bug.cgi?id=187116 Alexander Potashev changed: What|Removed |Added CC||aspotas...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kholidays] [Bug 336147] cannot turn off religious days in calendar
https://bugs.kde.org/show_bug.cgi?id=336147 Alexander Potashev changed: What|Removed |Added CC||aspotas...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[klipper] [Bug 409366] Clearing clipboard history does not clear the clipboard
https://bugs.kde.org/show_bug.cgi?id=409366 phd changed: What|Removed |Added Summary|Clearing clipboard history |Clearing clipboard history |does not clear the |does not clear the |clipboard / Content of |clipboard |clipboard is lost after | |closing application | CC||p...@phd.re Status|REOPENED|ASSIGNED Assignee|plasma-b...@kde.org |p...@phd.re -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 397728] Minimise caused crash
https://bugs.kde.org/show_bug.cgi?id=397728 takanowaka changed: What|Removed |Added CC||takanow...@live.com -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 410111] Breeze theme cannot be selected
https://bugs.kde.org/show_bug.cgi?id=410111 Nate Graham changed: What|Removed |Added CC||n...@kde.org Status|REPORTED|NEEDSINFO Resolution|--- |WAITINGFORINFO --- Comment #1 from Nate Graham --- Cannot reproduce. Can you attach a screen recording? -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 410108] Two Okular launchers with the same name
https://bugs.kde.org/show_bug.cgi?id=410108 Nate Graham changed: What|Removed |Added CC||n...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 408331] Brush size display in toolbar not updated correctly
https://bugs.kde.org/show_bug.cgi?id=408331 vaderpiz...@gmail.com changed: What|Removed |Added Resolution|FIXED |--- CC||vaderpiz...@gmail.com Status|RESOLVED|REOPENED --- Comment #19 from vaderpiz...@gmail.com --- still happening in 4.2.3 -- You are receiving this mail because: You are watching all bug changes.
[elisa] [Bug 410110] Spacebar to play/pause doesn't work anymore
https://bugs.kde.org/show_bug.cgi?id=410110 Nate Graham changed: What|Removed |Added CC||n...@kde.org --- Comment #1 from Nate Graham --- Works for me FWIW. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 410137] New palette are saved by default into the document: This is confusing behaviour.
https://bugs.kde.org/show_bug.cgi?id=410137 --- Comment #2 from David REVOY --- Oh ok :) Good to know for the palette being saved inside the document. True; not intuitive default. I found a workaround: I create a placeholder mypalette.gpl file ( a *.gpl file almost empty) in .local/share/krita/palettes/ , then I can edit it and all changes are done into a mypalette.kpl file next to it. (btw, the Drag&Drop of color-squares is a really cool new feature.) -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 327757] Internationalisation: languages mixed
https://bugs.kde.org/show_bug.cgi?id=327757 Nate Graham changed: What|Removed |Added CC||luiseduard...@gmail.com --- Comment #9 from Nate Graham --- *** Bug 410139 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 410139] Konsole not getting locale, print messages in spanish instead englisg
https://bugs.kde.org/show_bug.cgi?id=410139 Nate Graham changed: What|Removed |Added Resolution|--- |DUPLICATE Status|REPORTED|RESOLVED CC||n...@kde.org --- Comment #1 from Nate Graham --- *** This bug has been marked as a duplicate of bug 327757 *** -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 408331] Brush size display in toolbar not updated correctly
https://bugs.kde.org/show_bug.cgi?id=408331 --- Comment #20 from mcoudert --- (In reply to vaderpizza3 from comment #19) > still happening in 4.2.3 I think it was fix after the 4.2.3 release, test with the nightlies afeter 2019-07-21 -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 410126] Memory Leak when searching
https://bugs.kde.org/show_bug.cgi?id=410126 Nate Graham changed: What|Removed |Added CC||n...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 410129] System completly hang after opening a 144MB file with kwrite
https://bugs.kde.org/show_bug.cgi?id=410129 Nate Graham changed: What|Removed |Added CC||n...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 410129] System completly hang after opening a 144MB file with kwrite
https://bugs.kde.org/show_bug.cgi?id=410129 --- Comment #1 from Nate Graham --- Crashing in KPackage::PackageLoader::listPackages(), called from KWin::ScriptedEffectLoader::findAllEffects() -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 399680] Graphical glitch/corruption in certain menus when transparency effect is enabled
https://bugs.kde.org/show_bug.cgi?id=399680 Nate Graham changed: What|Removed |Added CC||ser...@iskynet.es --- Comment #15 from Nate Graham --- *** Bug 410132 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 410132] Content Menu don't show correctly
https://bugs.kde.org/show_bug.cgi?id=410132 Nate Graham changed: What|Removed |Added Status|REPORTED|RESOLVED CC||n...@kde.org Resolution|--- |DUPLICATE --- Comment #1 from Nate Graham --- *** This bug has been marked as a duplicate of bug 399680 *** -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 410125] "Preserve aspect ratio" when cropping should be off by default
https://bugs.kde.org/show_bug.cgi?id=410125 Nate Graham changed: What|Removed |Added Ever confirmed|0 |1 Status|REPORTED|CONFIRMED CC||n...@kde.org --- Comment #1 from Nate Graham --- Yes, I agree. This has been irritating me as well. -- You are receiving this mail because: You are watching all bug changes.
