[krita] [Bug 457981] New: Transform Tool - Perspective, after moving one corner point, other corner points are also moved.
https://bugs.kde.org/show_bug.cgi?id=457981 Bug ID: 457981 Summary: Transform Tool - Perspective, after moving one corner point, other corner points are also moved. Product: krita Version: 5.1.0-RC1 Platform: Other OS: Other Status: REPORTED Severity: normal Priority: NOR Component: Tools/Transform Assignee: krita-bugs-n...@kde.org Reporter: 1012468...@qq.com Target Milestone: --- Created attachment 151367 --> https://bugs.kde.org/attachment.cgi?id=151367=edit The kra file used to reproduce the bug. SUMMARY Transform Tool - Perspective, after moving one corner point, other corner points are also moved. I don’t understand why what didn’t move moved. This makes it impossible to quickly align them using the Transform Tool - Perspective. For example, paste the portrait to the portrait frame on the wall through the transformation tool - perspective. STEPS TO REPRODUCE 1. Open kra. 2. Switch to Transform Tool - Perspective. 3. Press and hold the lower right corner. 4. Approach to the upper left corner, then move away. (Multiple repetitions will be obvious.) OBSERVED RESULT Transform Tool - Perspective, after moving one corner point, other corner points are also moved. EXPECTED RESULT The moving corner point moves, and the other corner points remain stationary. SOFTWARE/OS VERSIONS Krita Version: 5.1.0-RC1 Installation type: installer / portable package Hidpi: true Qt Version (compiled): 5.12.12 Version (loaded): 5.12.12 OS Information Build ABI: x86_64-little_endian-llp64 Build CPU: x86_64 CPU: x86_64 Kernel Type: winnt Kernel Version: 10.0.19042 Pretty Productname: Windows 10 (10.0) Product Type: windows Product Version: 10 Locale Languages: en_US, en_US C locale: C QLocale current: en QLocale system: zh QTextCodec for locale: UTF-8 Process ACP: 65001 (UTF-8) System locale default ACP: 936 (ANSI/OEM - 简体中文 GBK) OpenGL Info Vendor: "Google Inc. (NVIDIA)" Renderer: "ANGLE (NVIDIA, NVIDIA GeForce GTX 970 Direct3D11 vs_5_0 ps_5_0, D3D11-30.0.15.1179)" Version: "OpenGL ES 3.0.0 (ANGLE 2.1.0 git hash: f2280c0c5f93+krita_qt5.12.12)" Shading language: "OpenGL ES GLSL ES 3.00 (ANGLE 2.1.0 git hash: f2280c0c5f93+krita_qt5.12.12)" Requested format: QSurfaceFormat(version 3.0, options QFlags(DeprecatedFunctions), depthBufferSize 24, redBufferSize 8, greenBufferSize 8, blueBufferSize 8, alphaBufferSize 8, stencilBufferSize 8, samples -1, swapBehavior QSurfaceFormat::DoubleBuffer, swapInterval 0, colorSpace QSurfaceFormat::DefaultColorSpace, profile QSurfaceFormat::CompatibilityProfile) Current format: QSurfaceFormat(version 3.0, options QFlags(), depthBufferSize 24, redBufferSize 8, greenBufferSize 8, blueBufferSize 8, alphaBufferSize 8, stencilBufferSize 8, samples 0, swapBehavior QSurfaceFormat::DefaultSwapBehavior, swapInterval 0, colorSpace QSurfaceFormat::DefaultColorSpace, profile QSurfaceFormat::NoProfile) Version: 3.0 Supports deprecated functions false is OpenGL ES: true supportsBufferMapping: true supportsBufferInvalidation: false forceDisableTextureBuffers: true Extensions: "GL_EXT_debug_label" "GL_OVR_multiview" "GL_EXT_disjoint_timer_query" "GL_OES_compressed_ETC2_sRGB8_alpha8_texture" "GL_OES_texture_border_clamp" "GL_NV_EGL_stream_consumer_external" "GL_NV_fence" "GL_EXT_occlusion_query_boolean" "GL_EXT_texture_rg" "GL_EXT_float_blend" "GL_EXT_multi_draw_indirect" "GL_OES_EGL_image_external" "GL_ANGLE_texture_compression_dxt5" "GL_ANGLE_framebuffer_blit" "GL_ANGLE_lossy_etc_decode" "GL_CHROMIUM_lose_context" "GL_EXT_shader_texture_lod" "GL_OES_packed_depth_stencil" "" "GL_CHROMIUM_bind_uniform_location" "GL_EXT_discard_framebuffer" "GL_EXT_clip_control" "GL_OES_element_index_uint" "GL_NV_framebuffer_blit" "GL_ANGLE_texture_multisample" "GL_KHR_debug" "GL_KHR_parallel_shader_compile" "GL_OES_texture_stencil8" "GL_EXT_debug_marker" "GL_EXT_sRGB" "GL_ANGLE_pack_reverse_row_order" "GL_ANGLE_framebuffer_multisample" "GL_EXT_instanced_arrays" "GL_OES_texture_half_float" "GL_EXT_read_format_bgra" "GL_OES_compressed_EAC_RG11_signed_texture" "GL_OVR_multiview2" "GL_OES_mapbuffer" "GL_ANGLE_multi_draw" "GL_AMD_performance_monitor" "GL_OES_get_program_binary" "GL_EXT_map_buffer_range" "GL_EXT_texture_filter_anisotropic" "GL_CHROMIUM_copy_texture" "GL_ANGLE_base_vertex_base_instance" "GL_OES_rgb8_rgba8" "GL_EXT_texture_compression_bptc" "GL_ANGLE_get_tex_level_parameter" "GL_EXT_texture_norm16" "GL_ANGLE_request_extension"
[kaddressbook] [Bug 387804] Create folder in KAddressBook fails
https://bugs.kde.org/show_bug.cgi?id=387804 Dmitry Smirnov changed: What|Removed |Added CC||only...@member.fsf.org -- You are receiving this mail because: You are watching all bug changes.
[kaddressbook] [Bug 405200] Creating a subfolder in any addressbook fails: can't create collection...
https://bugs.kde.org/show_bug.cgi?id=405200 Dmitry Smirnov changed: What|Removed |Added CC||only...@member.fsf.org -- You are receiving this mail because: You are watching all bug changes.
[kactivitymanagerd] [Bug 454000] current activity information doesn't change
https://bugs.kde.org/show_bug.cgi?id=454000
Yuuki Harano changed:
What|Removed |Added
Resolution|WAITINGFORINFO |NOT A BUG
Status|NEEDSINFO |RESOLVED
--- Comment #6 from Yuuki Harano ---
I'm very very sorry! I have misunderstood "activity".
I have thought it is something like "application".
Now, I created a new activity, switched between it and the default,
and I could get the current activity name.
method return time=1660711391.549389 sender=:1.20 -> destination=:1.170
serial=196 reply_serial=2
struct {
string "4b80d0b3-7c4a-4b31-b537-1f5b3d6d729b"
string "Mine2"
string ""
string "activities"
int32 2
}
I'm closing this issue.
--
You are receiving this mail because:
You are watching all bug changes.
[krita] [Bug 455570] Krita plus 5.1.0 prealpha : complex brush outline causes performance lag
https://bugs.kde.org/show_bug.cgi?id=455570 --- Comment #38 from Protoniv --- Created attachment 151366 --> https://bugs.kde.org/attachment.cgi?id=151366=edit tablet log (Pentium 3825U+igpu Win10 machine) Here is a tablet test log on my lower end Windows 10 machine. Testing with a very complex outline (auto brushtip 30% density, zoom canvas 200%, large brush ~800px), and outline is getting stuck. However, Windows 10 is spreading one thread load to all core on Task Manager (have seen this with single core stress test), it is really hard to observe if the "brush outline + drawing tablet" is stuck at single thread speed under windows. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 457917] Krita crashes after opening the fill layer properties.
https://bugs.kde.org/show_bug.cgi?id=457917 Bug Janitor Service changed: What|Removed |Added Status|NEEDSINFO |REPORTED Resolution|WAITINGFORINFO |--- --- Comment #6 from Bug Janitor Service --- Thanks for your comment! Automatically switching the status of this bug to REPORTED so that the KDE team knows that the bug is ready to get confirmed. In the future you may also do this yourself when providing needed information. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-knewstuff] [Bug 456818] Download New Global Themes window crash
https://bugs.kde.org/show_bug.cgi?id=456818 Bug Janitor Service changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|BACKTRACE |WORKSFORME --- Comment #3 from Bug Janitor Service --- This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 454171] Krita Crashes when making a new file/opening existing file
https://bugs.kde.org/show_bug.cgi?id=454171 Bug Janitor Service changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |WORKSFORME --- Comment #9 from Bug Janitor Service --- This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 450956] Crash while using Charcoal_KA
https://bugs.kde.org/show_bug.cgi?id=450956 Bug Janitor Service changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |WORKSFORME --- Comment #14 from Bug Janitor Service --- This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 457393] When I draw a line, only a dot at the start and a dot at the end show up. I am unable to draw even one line.
https://bugs.kde.org/show_bug.cgi?id=457393 --- Comment #2 from Bug Janitor Service --- Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 457374] Hovering over truncated bookmark pops up screen with file properties.
https://bugs.kde.org/show_bug.cgi?id=457374 --- Comment #2 from Bug Janitor Service --- Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 457308] Font is Being Whacky
https://bugs.kde.org/show_bug.cgi?id=457308 --- Comment #2 from Bug Janitor Service --- Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 454675] Update broke mouse scrolling (wheel) in all applications
https://bugs.kde.org/show_bug.cgi?id=454675 --- Comment #2 from Bug Janitor Service --- Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[kdelibs] [Bug 198172] printer margin settings are forgotten at restart
https://bugs.kde.org/show_bug.cgi?id=198172 --- Comment #20 from Bug Janitor Service --- Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 427214] Add ability to paste Klipper's contents on selection
https://bugs.kde.org/show_bug.cgi?id=427214 cgoh...@gmail.com changed: What|Removed |Added CC||cgoh...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 457935] Conflict with MIME type and preview
https://bugs.kde.org/show_bug.cgi?id=457935 --- Comment #5 from MILAS Robin --- Ok so I finally found the cause. This is due to KFileItemModel using setDelayedMimeTypes(true) on its KDirListener. This means that the mimetype is determined by file extension EXCEPT when item are sorted by types. Meaning that my preview does not work when files are sorted by names, but does display when files are sorted by types !! I'm gonna take a look a bit latter to try to see where this can be fix. There still be some other strange behaviour, which I think might be due to more time to execute full mime research on files when in a big folder because for a strange reason the preview and mimetype does work in my download folder without being sorted by types -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 457980] Application windows don't move to another activity
https://bugs.kde.org/show_bug.cgi?id=457980 techxga...@outlook.com changed: What|Removed |Added Platform|Other |Neon Packages OS|Other |Linux -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 457980] New: Application windows don't move to another activity
https://bugs.kde.org/show_bug.cgi?id=457980 Bug ID: 457980 Summary: Application windows don't move to another activity Product: plasmashell Version: master Platform: Other OS: Other Status: REPORTED Severity: normal Priority: NOR Component: Task Manager and Icons-Only Task Manager Assignee: plasma-b...@kde.org Reporter: techxga...@outlook.com Target Milestone: 1.0 SUMMARY Making the app window move to another activity makes it show on ALL activities until I manually select the right activity STEPS TO REPRODUCE 1. Right click on a application window in the task bar 2. Hover in Show in Activities & Select the activity you want to move it to (labeled "Move to ") 3. (When it shows on ALL) Select the Activity you want to move it to (not the one labeled "Move to...") OBSERVED RESULT The app shows up in ALL activities instead of moving EXPECTED RESULT The app window should move to the selected activity SOFTWARE/OS VERSIONS Operating System: KDE neon Unstable Edition KDE Plasma Version: 5.25.80 KDE Frameworks Version: 5.97.0 Qt Version: 5.15.5 Kernel Version: 5.15.0-46-generic (64-bit) Graphics Platform: Wayland Processors: 8 × AMD EPYC-Milan Processor Memory: 7.8 GiB of RAM Graphics Processor: NVIDIA GeForce GTX 1060 6GB/PCIe/SSE2 Manufacturer: QEMU Product Name: Standard PC (Q35 + ICH9, 2009) System Version: pc-q35-6.0 ADDITIONAL INFORMATION I'm on Wayland -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 200223] default language of spellchecker is ignored
https://bugs.kde.org/show_bug.cgi?id=200223 --- Comment #11 from caulier.gil...@gmail.com --- Git commit fb9bc61ea2cc4d5045d7adde54d3b03bc59e888f by Gilles Caulier. Committed on 17/08/2022 at 02:59. Pushed by cgilles into branch 'master'. If user change a current language from an alternative language text edit widget, and if the language is not "x-default", force spell-checker to use this language as well. If user change a current language from an alternative language text edit widget to "x-default", turn on the auto-detection of language in spell-checker. Note: By default, an alternative language text edit widget always use the auto-detection of language in spell-checker. Related: bug 376345 M +5-1core/libs/widgets/metadata/utils/altlangstredit.cpp M +56 -10 core/libs/widgets/text/dtextedit.cpp M +2-0core/libs/widgets/text/dtextedit.h M +2-2core/libs/widgets/text/spellcheckconfig.cpp M +5-5core/libs/widgets/text/spellcheckcontainer.cpp M +2-1core/libs/widgets/text/spellcheckcontainer.h https://invent.kde.org/graphics/digikam/commit/fb9bc61ea2cc4d5045d7adde54d3b03bc59e888f -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 376345] can't disable "auto spell check" while editing metadata
https://bugs.kde.org/show_bug.cgi?id=376345 --- Comment #10 from caulier.gil...@gmail.com --- Git commit fb9bc61ea2cc4d5045d7adde54d3b03bc59e888f by Gilles Caulier. Committed on 17/08/2022 at 02:59. Pushed by cgilles into branch 'master'. If user change a current language from an alternative language text edit widget, and if the language is not "x-default", force spell-checker to use this language as well. If user change a current language from an alternative language text edit widget to "x-default", turn on the auto-detection of language in spell-checker. Note: By default, an alternative language text edit widget always use the auto-detection of language in spell-checker. Related: bug 200223 M +5-1core/libs/widgets/metadata/utils/altlangstredit.cpp M +56 -10 core/libs/widgets/text/dtextedit.cpp M +2-0core/libs/widgets/text/dtextedit.h M +2-2core/libs/widgets/text/spellcheckconfig.cpp M +5-5core/libs/widgets/text/spellcheckcontainer.cpp M +2-1core/libs/widgets/text/spellcheckcontainer.h https://invent.kde.org/graphics/digikam/commit/fb9bc61ea2cc4d5045d7adde54d3b03bc59e888f -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 457935] Conflict with MIME type and preview
https://bugs.kde.org/show_bug.cgi?id=457935 --- Comment #4 from MILAS Robin --- So as far as I am it seems that KCoreDirLister emit items with incorrect mimetype (at least they do not check content, in some case). -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 457979] New: Disable the long-clicking functionality to trigger "Edit Mode" on desktop
https://bugs.kde.org/show_bug.cgi?id=457979 Bug ID: 457979 Summary: Disable the long-clicking functionality to trigger "Edit Mode" on desktop Product: plasmashell Version: master Platform: openSUSE RPMs OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: Touchpad Assignee: plasma-b...@kde.org Reporter: koea...@gmail.com Target Milestone: 1.0 SUMMARY There is a mouse / touchpad gesture that lets me trigger this if I simply click and hold for no more than a second. Sometimes, I have a pen-based graphics tablet that lets me press and hold for more than a second. This feature gets annoying when I'm not intentionally trying to trigger this function or anything else requiring a long-click. SOFTWARE/OS VERSIONS Linux/KDE Plasma: OpenSUSE 15.4 Leap (available in About System) KDE Plasma Version: 5.25.4 ADDITIONAL INFORMATION I'd really like some way to turn this off, because after I had a mailing list in the KDE community we later figured out this was likely hardcoded and a part of plasma5-mobile. There should be some way to turn this off at least, given I'm always in a desktop and it should be more convenient to cater to desktop-only users like me. I already have Alt + D and the context menu for my right click to enter edit mode, why would I need a third shortcut that hinders my ability to use things like my graphics tablet? -- You are receiving this mail because: You are watching all bug changes.
[kolourpaint] [Bug 457978] Text tool doesn't allow typing accents (á, à, ã, ô, etc.) in portuguese
https://bugs.kde.org/show_bug.cgi?id=457978 --- Comment #2 from Bernardo Janko Gonçalves Biesseck --- Comment on attachment 151365 --> https://bugs.kde.org/attachment.cgi?id=151365 Printscreen of KolourPaint showing that accents are not displayed Accents are not displayed when typing brazilian words: pão, mão, Paraná, Pelé. -- You are receiving this mail because: You are watching all bug changes.
[kolourpaint] [Bug 457978] Text tool doesn't allow typing accents (á, à, ã, ô, etc.) in portuguese
https://bugs.kde.org/show_bug.cgi?id=457978 --- Comment #1 from Bernardo Janko Gonçalves Biesseck --- Created attachment 151365 --> https://bugs.kde.org/attachment.cgi?id=151365=edit Printscreen of KolourPaint showing that accents are not displayed -- You are receiving this mail because: You are watching all bug changes.
[kolourpaint] [Bug 457978] New: Text tool doesn't allow typing accents (á, à, ã, ô, etc.) in portuguese
https://bugs.kde.org/show_bug.cgi?id=457978 Bug ID: 457978 Summary: Text tool doesn't allow typing accents (á, à, ã, ô, etc.) in portuguese Product: kolourpaint Version: 21.12.1 Platform: Ubuntu Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kolourpaint-supp...@lists.sourceforge.net Reporter: biess...@gmail.com Target Milestone: --- STEPS TO REPRODUCE 1. Start KolourPaint. 2. Select the "Text" tool. 3. Draw a rectangular text region. 4. Try to type brazilian portuguese words containing accents: pão, mão, Paraná, Pelé. OBSERVED RESULT: Accents are not displayed. EXPECTED RESULT: Type brazilian words should be shown containing theirs accents. SOFTWARE/OS VERSIONS Linux: Ubuntu 22.04 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[ksudoku] [Bug 457951] ksudoku commit 6e9d941ce with an existing theme config results in a blank play-space and qpainter engine errors
https://bugs.kde.org/show_bug.cgi?id=457951 --- Comment #13 from Duncan <1i5t5.dun...@cox.net> --- (In reply to Duncan from comment #12) > What makes kpat's Egyptian different so it won't take it? User mistake. I didn't read the tabs and was changing card decks instead of game themes, not realizing they were separate. Once I changed game theme to Egyptian as well, it took. I'm not entirely sure whether the card deck was changing to Egyptian all the time and I didn't notice it as I was staring at the (to me[1]) blinding green-blaze background, or whether it only took once I changed the game theme to Egyptian as well, but in any case, I can say the card deck Egyptian did take once I set the game theme Egyptian. But we're still left with the fact that the patch breaks the existing kpatrc theme choice, tho not as badly as ksudoku's breakage, as kpat does at least revert to a usable default instead of blanking. Both honor resetting the theme, but kpat's breakage is less as it reverts to a usable (if personally uncomfortable) default instead of breaking game play. --- [1] I wear rigid gas-perm contacts with a rather high nearsightedness correction of ~ -10 diopters. The combination of the strongly negative correction and rigid lenses means too bright backgrounds star-flare-reflect in the contacts and eventually give me a headache as my eyes and brain try to compensate and see around/through the flare-reflections. It took me years to figure out, but that's why I strongly prefer a "reversed" light-on-dark color-scheme as at least then the flares are smaller than when the entire background is bright. The brown-sand Egyptian background is perfect for that, plus I visited and find the idea of the theme rather pleasing as well! -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 457977] New: Kickoff not switching to already launched application
https://bugs.kde.org/show_bug.cgi?id=457977 Bug ID: 457977 Summary: Kickoff not switching to already launched application Product: plasmashell Version: master Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Application Launcher (Kickoff) Assignee: plasma-b...@kde.org Reporter: mtj...@gmail.com CC: mikel5...@gmail.com, noaha...@gmail.com Target Milestone: 1.0 SUMMARY *** When user inadvertently launches an application that is already running (usually on another virtual desktop) nothing happens. I'm not sure if this is a bug, but I would expect plasmashell to switch to the already running application. *** STEPS TO REPRODUCE 1. Create some virtual desktops. I usually use three virtual desktops. 2. Open an application, for example System Monitor and move it to another virtual desktop, to virtual desktop #2 3. While on virtual desktop #1 launch System Monitor. OBSERVED RESULT Nothing happens. Some application that are designed to run multiple instances like Kwrite open another instance. EXPECTED RESULT Expect KDE to switch to the already running application if designed to run only single instance. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: KDE Neon (kernel 5.15.0-46-generic (available in About System) KDE Plasma Version: 5.25.4 Wayland session KDE Frameworks Version: 5.96.0 Qt Version: 5.15.0 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[ksudoku] [Bug 457951] ksudoku commit 6e9d941ce with an existing theme config results in a blank play-space and qpainter engine errors
https://bugs.kde.org/show_bug.cgi?id=457951 --- Comment #12 from Duncan <1i5t5.dun...@cox.net> --- Yikes! The patch breaks kpat's Egyptian theme (at least with my existing kpatrc). In the kpat case, however, it *does* revert to something else (default?) instead of blanking, as I proposed for ksudoku. However, unlike ksudoku, I can't reset it to Egyptian -- it simply doesn't take -- tho I *can* set at least some other themes and they will take. It took all I tried (several, it ships way more than the three ksudoku ships) /except/ Egyptian. Which is weird, as again, I've not HNS-ed additional themes so they're all as-shipped. What makes kpat's Egyptian different so it won't take it? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 457976] Plasma crashes when change monitor configuration via bash script (xrandr command)
https://bugs.kde.org/show_bug.cgi?id=457976 James changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |FIXED --- Comment #1 from James --- Change scripts to be one line ie: xrandr --output DP-0 --off --output HDMI-0 --mode 2560x1440 --primary --pos 0x1440 --rotate normal --output DP-4 --mode 3440x1440 --pos 469x0--rotate normal and it seemed to stop the crashing. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 457976] New: Plasma crashes when change monitor configuration via bash script (xrandr command)
https://bugs.kde.org/show_bug.cgi?id=457976 Bug ID: 457976 Summary: Plasma crashes when change monitor configuration via bash script (xrandr command) Product: plasmashell Version: 5.24.4 Platform: Ubuntu Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: jtk...@gmail.com CC: k...@davidedmundson.co.uk Target Milestone: 1.0 Application: plasmashell (5.24.4) Qt Version: 5.15.3 Frameworks Version: 5.92.0 Operating System: Linux 5.15.0-46-generic x86_64 Windowing System: X11 Distribution: Ubuntu 22.04.1 LTS DrKonqi: 5.24.4 [KCrashBackend] -- Information about the crash: - What I was doing when the application crashed: Executed bash script to disable or enable third monitor. - Custom settings of the application: Disable third monitor: xrandr --output DP-0 --off \ --output HDMI-0 --mode 2560x1440 --primary --pos 0x1440 --rotate normal \ --output DP-4 --mode 3440x1440 --pos 469x0--rotate normal Enable third monitor: xrandr --output DP-0 --mode 2560x1440 --primary --pos 2560x1440 --rotate normal \ --output HDMI-0 --mode 2560x1440 --pos 0x1440 --rotate normal \ --output DP-4 --mode 3440x1440 --pos 469x0--rotate normal The crash can be reproduced every time. -- Backtrace: Application: Plasma (plasmashell), signal: Segmentation fault [KCrash Handler] #4 0x7efc546f6134 in QScreen::geometry() const () at /lib/x86_64-linux-gnu/libQt5Gui.so.5 #5 0x559a30d74f63 in () #6 0x559a30d78f16 in () #7 0x7efc546d95a5 in QWindow::event(QEvent*) () at /lib/x86_64-linux-gnu/libQt5Gui.so.5 #8 0x7efc54fdb713 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #9 0x7efc542e4e2a in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #10 0x7efc546ce748 in QGuiApplicationPrivate::processExposeEvent(QWindowSystemInterfacePrivate::ExposeEvent*) () at /lib/x86_64-linux-gnu/libQt5Gui.so.5 #11 0x7efc546a2a2c in QWindowSystemInterface::sendWindowSystemEvents(QFlags) () at /lib/x86_64-linux-gnu/libQt5Gui.so.5 #12 0x7efc4f20ad6e in () at /lib/x86_64-linux-gnu/libQt5XcbQpa.so.5 #13 0x7efc526c0d1b in g_main_context_dispatch () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #14 0x7efc527156f8 in () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #15 0x7efc526be3c3 in g_main_context_iteration () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #16 0x7efc5433e0a8 in QEventDispatcherGlib::processEvents(QFlags) () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #17 0x7efc542e374b in QEventLoop::exec(QFlags) () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #18 0x7efc542ebce4 in QCoreApplication::exec() () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #19 0x559a30d60dce in () #20 0x7efc53c00d90 in __libc_start_call_main (main=main@entry=0x559a30d5ff70, argc=argc@entry=1, argv=argv@entry=0x7ffc30bb0408) at ../sysdeps/nptl/libc_start_call_main.h:58 #21 0x7efc53c00e40 in __libc_start_main_impl (main=0x559a30d5ff70, argc=1, argv=0x7ffc30bb0408, init=, fini=, rtld_fini=, stack_end=0x7ffc30bb03f8) at ../csu/libc-start.c:392 #22 0x559a30d60ef5 in () [Inferior 1 (process 1513) detached] The reporter indicates this bug may be a duplicate of or related to bug 457282. Possible duplicates by query: bug 457916, bug 457912, bug 457862, bug 457827, bug 457721. Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[ksudoku] [Bug 457951] ksudoku commit 6e9d941ce with an existing theme config results in a blank play-space and qpainter engine errors
https://bugs.kde.org/show_bug.cgi?id=457951 --- Comment #11 from Duncan <1i5t5.dun...@cox.net> --- (In reply to Duncan from comment #10) > [H]ow difficult would it be to code up a "this entry > doesn't make sense, ignore it and use/rewrite the default" solution? ... maybe with a warning, to STDERR, notification or dialog depending on evaluated priority of the user actually seeing it, saying the existing entry was corrupted (or whatever better wording) so it reverted to default. -- You are receiving this mail because: You are watching all bug changes.
[ksudoku] [Bug 457951] ksudoku commit 6e9d941ce with an existing theme config results in a blank play-space and qpainter engine errors
https://bugs.kde.org/show_bug.cgi?id=457951 --- Comment #10 from Duncan <1i5t5.dun...@cox.net> --- (In reply to Friedrich W. H. Kossebau from comment #9) > https://invent.kde.org/games/libkdegames/-/merge_requests/20.diff Good and bad news: Good: The relative style ksudokurc theme entry works with that patch. Bad: The full-path style does not. If there hasn't been a release with the now-existing code that creates the full-path entry I imagine the bad news can be ignored (unless we want to give people hand-editing their ksudokurc files the choice of doing full paths, too). If there has been a release, the question is do we want to cover both styles and thus cover the short-period code that additionally only writes the full path for symlinked paths, or are we willing to sacrifice the narrow segment who both ran the new release and have in-path symlinks, most of who likely were upgrades already and thus had to do the blow-away/hand-edit process once already in ordered to get that full path entry in the first place? Alternatively or as well, how difficult would it be to code up a "this entry doesn't make sense, ignore it and use/rewrite the default" solution? I'd personally prefer that, as then the worst-case (triggered by say a fully corrupted entry or one pointed at a missing theme) would be losing the configured theme and resetting to default, instead of showing blank/broken game-play areas thus breaking the games in question. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 457861] Wallpaper accent color sometimes has bad contrast on Breeze Dark
https://bugs.kde.org/show_bug.cgi?id=457861 Fushan Wen changed: What|Removed |Added CC|qydwhotm...@gmail.com | -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 457861] Wallpaper accent color sometimes has bad contrast on Breeze Dark
https://bugs.kde.org/show_bug.cgi?id=457861 Fushan Wen changed: What|Removed |Added Status|ASSIGNED|CONFIRMED -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 456210] Cannot unlock screen when using multiple monitors
https://bugs.kde.org/show_bug.cgi?id=456210 --- Comment #43 from ratijas --- Can reproduce. After normal password prompt a useless lonely "Unlock" buttons shows up, like the one for password-less users. Clicking it sometimes terminates the lock screen app and thus returns to the desktop, but sometimes does nothing. Build-in laptop screen + external HDMI 4K@30FPS monitor. Both with testing and real screen locking. No fingerprints, no fprint, only password. Workaround is to run loginctl unlock-session from TTY2 (Ctrl+Alt+F2 or +F8 depending on your distro). Operating System: Arch Linux KDE: git master Qt Version: 5.15.5 Kernel Version: 5.18.16-arch1-1 (64-bit) Graphics Platform: X11 I'm not getting EDID logs in journalctl, but I do get this line on start of kscreenlocker_greet: >kscreenlocker_greet[8858]: pam_systemd_home(kde:auth): systemd-homed is > not available: >Unit dbus-org.freedesktop.home1.service not found. I'm also getting these cosmetic error messages after every failed attempt, even though I can't find any instance where it is defined as "read-only": > > file:///usr/local/kde/share/plasma/look-and-feel/org.kde.breeze.desktop/contents/lockscreen/LockScreenUi.qml:75: >TypeError: Cannot assign to read-only property "showPassword" Consistent observation: when entering a correct password one screen first, the following dummy "Unlock" button terminates the screen locker and returns me to the desktop. But if I enter the password on another screen first — it won't unlock, it'll do nothing. It doesn't matter when do you do next: only first correct password attempt seems to matter. "One" and "another" screens are randomly chosen laptop's built-in and external HDMI: in other words it would either work on a first try because you guessed the screen correctly, or it won't work no matter how many times you click. So far I'm more lucky with the "one" being the built-in laptop's one. Basically, the same logs as posted above. The only difference when it's about to enter the unlockable state (i.e. I guessed the screen wrong) is an extra `kscreenlocker_greet: Start auth` line after `kscreenlocker_greet: Auth done RC 0`. -- You are receiving this mail because: You are watching all bug changes.
[ksudoku] [Bug 457951] ksudoku commit 6e9d941ce with an existing theme config results in a blank play-space and qpainter engine errors
https://bugs.kde.org/show_bug.cgi?id=457951 --- Comment #9 from Friedrich W. H. Kossebau --- Thanks for getting and showing that log. Okay, that should back up the working theory about the cause :) If you like to help more, please give the meanwhile created bug fix proposal as reported before by the bot a test. It should also apply to current master (I assume). You can download the patch itself by blue "Code" button (choose "Plain diff" in the popup menu) or using this link directly: https://invent.kde.org/games/libkdegames/-/merge_requests/20.diff -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 432264] Wayland context Menus entries disappear/ graphic glitching
https://bugs.kde.org/show_bug.cgi?id=432264 ja...@jamesharding.me changed: What|Removed |Added CC||ja...@jamesharding.me -- You are receiving this mail because: You are watching all bug changes.
[ksudoku] [Bug 457951] ksudoku commit 6e9d941ce with an existing theme config results in a blank play-space and qpainter engine errors
https://bugs.kde.org/show_bug.cgi?id=457951
--- Comment #8 from Duncan <1i5t5.dun...@cox.net> ---
(In reply to Friedrich W. H. Kossebau from comment #6)
> Please try the attached patch for libkdegames
> Interesting will be all the log output starting with "THEMELOADING"
For clarity this is at libkdegames c5848c0d6 and $HOME=/h/x (with
$XDG_CONFIG_HOME=$HOME/config), but having visited Egypt I /really/ like that
theme and I haven't felt the need to HNS any themes, so (/usr)/share/ksudoku is
the only location with any.
THEMELOADING considering locations ("/h/x/config/share/ksudoku",
"/usr/local/share/ksudoku", "/usr/share/ksudoku")
THEMELOADING considering desktop file
"/usr/share/ksudoku/themes/abstraction.desktop"
THEMELOADING canonical path "/share/ksudoku/themes/abstraction.desktop"
THEMELOADING id "/usr/share/ksudoku/themes/abstraction.desktop"
THEMELOADING considering desktop file
"/usr/share/ksudoku/themes/default.desktop"
THEMELOADING canonical path "/share/ksudoku/themes/default.desktop"
THEMELOADING id "/usr/share/ksudoku/themes/default.desktop"
THEMELOADING considering desktop file
"/usr/share/ksudoku/themes/ksudoku_scrible.desktop"
THEMELOADING canonical path "/share/ksudoku/themes/ksudoku_scrible.desktop"
THEMELOADING id "/usr/share/ksudoku/themes/ksudoku_scrible.desktop"
--
You are receiving this mail because:
You are watching all bug changes.
[kwin] [Bug 449924] Windows are not resized back to original size
https://bugs.kde.org/show_bug.cgi?id=449924 Riccardo Robecchi changed: What|Removed |Added Component|virtual-keyboard|general Summary|Windows are not resized |Windows are not resized |back to original size when |back to original size |opening and closing a | |virtual keyboard such as| |Onboard | --- Comment #6 from Riccardo Robecchi --- As I have learned in these months, the bug is not related just to virtual keyboards. It applies to a variety of other situations, e.g. with Latte as mentioned before, but also with Plasma panels in some situations. It appears that KWin does not restore the size of windows properly in general, not just with virtual keyboards (and this may be the cause behind bug 457950, just to name one which I know). -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 457974] Snap kdevelop crashes at launch
https://bugs.kde.org/show_bug.cgi?id=457974 --- Comment #3 from Sven Brauch --- Hi, unfortunately KDevelop is relatively short-staffed and simply nobody built an AppImage for the latest release. It would of course be possible to do that, though. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 457974] Snap kdevelop crashes at launch
https://bugs.kde.org/show_bug.cgi?id=457974 --- Comment #2 from Ian H --- Hmm... is there any where i can get the latest kdevelop that functions? i cant use flatpak because it cant get access to /usr/bin (for protobuf), and i cant use the snap because it doesnt run. the latest version from 22.04.1 repo is 21.08 and gets stuck when you try to copy files. The latest app images on kdevelop.org is 5.6.1. Is there any reason that there are no available downloads for latest versions anymore? -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 457917] Krita crashes after opening the fill layer properties.
https://bugs.kde.org/show_bug.cgi?id=457917 --- Comment #5 from ico.dy...@gmail.com --- Before the first crash I changed the fill layer blending mode to Grain Merge and the transparency to 50%, clicked ok and opened the properties level dialog. After the crash the problem appears again and again... -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 457917] Krita crashes after opening the fill layer properties.
https://bugs.kde.org/show_bug.cgi?id=457917 --- Comment #4 from ico.dy...@gmail.com --- After a while the same problem reappeared and I can't find the source... ;___; -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 456562] Searching for files in application launchers other than Kickoff fails
https://bugs.kde.org/show_bug.cgi?id=456562 Nate Graham changed: What|Removed |Added Version Fixed In||5.25.5 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 457972] digiKam Crash when select multiple files and add to cue to batch process
https://bugs.kde.org/show_bug.cgi?id=457972 --- Comment #3 from Maik Qualmann --- Yes, Gilles it should be the same problem. I can't reproduce it with the BQM at the moment, but as a test with the Delete Dialog immediately if the Uniform Row Heights are set to false. Although it is generally a good idea to set the Uniform Row Heights to true for performance reasons, it must not crash. Maik -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 435004] Circular timeout indicator looks bad at fractional scale or when using some non-Breeze icon themes
https://bugs.kde.org/show_bug.cgi?id=435004 Nate Graham changed: What|Removed |Added Severity|minor |normal -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 457972] digiKam Crash when select multiple files and add to cue to batch process
https://bugs.kde.org/show_bug.cgi?id=457972 Maik Qualmann changed: What|Removed |Added CC||metzping...@gmail.com --- Comment #2 from Maik Qualmann --- This is a Qt bug in current Qt-5.15.5. This problem occurs on openSUSE Tumbleweed and Gentoo when a QTreeWidget does not have Uniform Row Heights set to true. We can do a workaround here, but the problem needs to be fixed in Qt, please report the problem to openSUSE with the link to here. Maik -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 457972] digiKam Crash when select multiple files and add to cue to batch process
https://bugs.kde.org/show_bug.cgi?id=457972 caulier.gil...@gmail.com changed: What|Removed |Added Component|general |BatchQueueManager-Core -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 457972] digiKam Crash when select multiple files and add to cue to batch process
https://bugs.kde.org/show_bug.cgi?id=457972 caulier.gil...@gmail.com changed: What|Removed |Added CC||caulier.gil...@gmail.com Summary|Digicam Crash when select |digiKam Crash when select |multiple files and add to |multiple files and add to |cue to batch process|cue to batch process --- Comment #1 from caulier.gil...@gmail.com --- Maik, it's probably the same problem than Delete Dialog that you fix few days ago... Gilles -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 457974] Snap kdevelop crashes at launch
https://bugs.kde.org/show_bug.cgi?id=457974 Sven Brauch changed: What|Removed |Added Status|REPORTED|RESOLVED CC||m...@svenbrauch.de Resolution|--- |DOWNSTREAM --- Comment #1 from Sven Brauch --- This is a packaging issue, in a package not provided by KDE. Please report this to Ubuntu. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 457975] Click-and-hold enters Selection Mode, but tap-and-hold does not
https://bugs.kde.org/show_bug.cgi?id=457975 Nate Graham changed: What|Removed |Added CC||fe.a.er...@gmail.com Keywords||usability -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 457973] Dragging item while not in selection mode enters it
https://bugs.kde.org/show_bug.cgi?id=457973 Nate Graham changed: What|Removed |Added CC||fe.a.er...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 457975] New: Click-and-hold enters Selection Mode, but tap-and-hold does not
https://bugs.kde.org/show_bug.cgi?id=457975 Bug ID: 457975 Summary: Click-and-hold enters Selection Mode, but tap-and-hold does not Product: dolphin Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: view-engine: general Assignee: dolphin-bugs-n...@kde.org Reporter: n...@kde.org CC: kfm-de...@kde.org Target Milestone: --- Everything KDE from current git master. STEPS TO REPRODUCE 1. Open Dolphin. 2. Click-and-hold on an item using a pointing device. OBSERVED RESULT Dolphin enters Selection mode. See also Bug 457973. STEPS TO REPRODUCE 1. Open Dolphin. 2. Press-and-hold on an item using a touchscreen OBSERVED RESULT Dolphin shows a context menu but does not enter selection mode. These behaviors aren't quite right. Click-and-hold should generally do nothing when using a pointing device, while press-and-hold using a touch device should enter Selection Mode rather than showing the context menu; the context-sensitive Selection Mode toolbar is more or less a touch-friendly replacement for the context menu. It's especially important that press-and-hold enter selection mode on touch since the user likely won't have access to the spacebar keyboard shortcut. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 457974] New: Snap kdevelop crashes at launch
https://bugs.kde.org/show_bug.cgi?id=457974 Bug ID: 457974 Summary: Snap kdevelop crashes at launch Product: kdevelop Version: 5.8.220403 Platform: Snap OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: general Assignee: kdevelop-bugs-n...@kde.org Reporter: master.ha...@gmail.com Target Milestone: --- SUMMARY *** Snap version of kdevelop crashes immediately at launch on ubuntu 22.04 *** STEPS TO REPRODUCE 1. Install latest snap (5.8.220403) 2. run with /snap/bin/kdevelop 3. crash OBSERVED RESULT Crashes every boot with the error: Cannot mix incompatible Qt library (5.15.3) with this library (5.15.5) Aborted (core dumped) EXPECTED RESULT Software should run as normal SOFTWARE/OS VERSIONS Linux/KDE Plasma: Ubuntu 22.04.1 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 457973] New: Dragging item while not in selection mode enters it
https://bugs.kde.org/show_bug.cgi?id=457973 Bug ID: 457973 Summary: Dragging item while not in selection mode enters it Product: dolphin Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: view-engine: general Assignee: dolphin-bugs-n...@kde.org Reporter: n...@kde.org CC: kfm-de...@kde.org Target Milestone: --- Everything KDE from current git master. STEPS TO REPRODUCE 1. Open Dolphin 2. Start dragging an item such that it passes over the Dolphin window while being dragged OBSERVED RESULT Dolphin enters Selection mode. EXPECTED RESULT Dolphin doesn't enter selection mode. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 457972] New: Digicam Crash when select multiple files and add to cue to batch process
https://bugs.kde.org/show_bug.cgi?id=457972 Bug ID: 457972 Summary: Digicam Crash when select multiple files and add to cue to batch process Product: digikam Version: 7.7.0 Platform: openSUSE RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: digikam-bugs-n...@kde.org Reporter: m...@klige.de Target Milestone: --- Application: digikam (7.7.0) Qt Version: 5.15.5 Frameworks Version: 5.96.0 Operating System: Linux 5.19.1-1-default x86_64 Windowing System: X11 Distribution: openSUSE Tumbleweed DrKonqi: 5.25.4 [KCrashBackend] -- Information about the crash: selected 2 images and added it to actual cue to batch process The reporter is unsure if this crash is reproducible. -- Backtrace: Application: digiKam (digikam), signal: Segmentation fault [KCrash Handler] #4 0x7ff7113a782b in QTreeView::drawRow(QPainter*, QStyleOptionViewItem const&, QModelIndex const&) const () from /lib64/libQt5Widgets.so.5 #5 0x7ff7113ab7f9 in QTreeView::drawTree(QPainter*, QRegion const&) const () from /lib64/libQt5Widgets.so.5 #6 0x7ff7113b2234 in QTreeView::paintEvent(QPaintEvent*) () from /lib64/libQt5Widgets.so.5 #7 0x7ff71110ac68 in QWidget::event(QEvent*) () from /lib64/libQt5Widgets.so.5 #8 0x7ff7111b659e in QFrame::event(QEvent*) () from /lib64/libQt5Widgets.so.5 #9 0x7ff710518d3b in QCoreApplicationPrivate::sendThroughObjectEventFilters(QObject*, QEvent*) () from /lib64/libQt5Core.so.5 #10 0x7ff7110c940e in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /lib64/libQt5Widgets.so.5 #11 0x7ff710518fb8 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /lib64/libQt5Core.so.5 #12 0x7ff711102fc5 in QWidgetPrivate::sendPaintEvent(QRegion const&) () from /lib64/libQt5Widgets.so.5 #13 0x7ff711103881 in QWidgetPrivate::drawWidget(QPaintDevice*, QRegion const&, QPoint const&, QFlags, QPainter*, QWidgetRepaintManager*) () from /lib64/libQt5Widgets.so.5 #14 0x7ff711104b86 in QWidgetPrivate::paintSiblingsRecursive(QPaintDevice*, QList const&, int, QRegion const&, QPoint const&, QFlags, QPainter*, QWidgetRepaintManager*) () from /lib64/libQt5Widgets.so.5 #15 0x7ff7111049e9 in QWidgetPrivate::paintSiblingsRecursive(QPaintDevice*, QList const&, int, QRegion const&, QPoint const&, QFlags, QPainter*, QWidgetRepaintManager*) () from /lib64/libQt5Widgets.so.5 #16 0x7ff7111034fc in QWidgetPrivate::drawWidget(QPaintDevice*, QRegion const&, QPoint const&, QFlags, QPainter*, QWidgetRepaintManager*) () from /lib64/libQt5Widgets.so.5 #17 0x7ff711104b86 in QWidgetPrivate::paintSiblingsRecursive(QPaintDevice*, QList const&, int, QRegion const&, QPoint const&, QFlags, QPainter*, QWidgetRepaintManager*) () from /lib64/libQt5Widgets.so.5 #18 0x7ff7111034fc in QWidgetPrivate::drawWidget(QPaintDevice*, QRegion const&, QPoint const&, QFlags, QPainter*, QWidgetRepaintManager*) () from /lib64/libQt5Widgets.so.5 #19 0x7ff711104b86 in QWidgetPrivate::paintSiblingsRecursive(QPaintDevice*, QList const&, int, QRegion const&, QPoint const&, QFlags, QPainter*, QWidgetRepaintManager*) () from /lib64/libQt5Widgets.so.5 #20 0x7ff7111049e9 in QWidgetPrivate::paintSiblingsRecursive(QPaintDevice*, QList const&, int, QRegion const&, QPoint const&, QFlags, QPainter*, QWidgetRepaintManager*) () from /lib64/libQt5Widgets.so.5 #21 0x7ff7111034fc in QWidgetPrivate::drawWidget(QPaintDevice*, QRegion const&, QPoint const&, QFlags, QPainter*, QWidgetRepaintManager*) () from /lib64/libQt5Widgets.so.5 #22 0x7ff711104b86 in QWidgetPrivate::paintSiblingsRecursive(QPaintDevice*, QList const&, int, QRegion const&, QPoint const&, QFlags, QPainter*, QWidgetRepaintManager*) () from /lib64/libQt5Widgets.so.5 #23 0x7ff7111034fc in QWidgetPrivate::drawWidget(QPaintDevice*, QRegion const&, QPoint const&, QFlags, QPainter*, QWidgetRepaintManager*) () from /lib64/libQt5Widgets.so.5 #24 0x7ff711104b86 in QWidgetPrivate::paintSiblingsRecursive(QPaintDevice*, QList const&, int, QRegion const&, QPoint const&, QFlags, QPainter*, QWidgetRepaintManager*) () from /lib64/libQt5Widgets.so.5 #25 0x7ff7111049e9 in QWidgetPrivate::paintSiblingsRecursive(QPaintDevice*, QList const&, int, QRegion const&, QPoint const&, QFlags, QPainter*, QWidgetRepaintManager*) () from /lib64/libQt5Widgets.so.5 #26 0x7ff7111049e9 in QWidgetPrivate::paintSiblingsRecursive(QPaintDevice*, QList const&, int, QRegion const&, QPoint const&, QFlags, QPainter*, QWidgetRepaintManager*) () from /lib64/libQt5Widgets.so.5 #27 0x7ff7111034fc in QWidgetPrivate::drawWidget(QPaintDevice*, QRegion const&, QPoint const&, QFlags, QPainter*, QWidgetRepaintManager*) () from /lib64/libQt5Widgets.so.5 #28 0x7ff711104b86 in QWidgetPrivate::paintSiblingsRecursive(QPaintDevice*, QList const&, int,
[kate] [Bug 457480] Changing text font in print dialogue
https://bugs.kde.org/show_bug.cgi?id=457480 Nate Graham changed: What|Removed |Added Version Fixed In||5.98 CC||n...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 450448] Scrolling with touchscreen does not work consistently
https://bugs.kde.org/show_bug.cgi?id=450448 Nate Graham changed: What|Removed |Added Version Fixed In||5.26 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 457949] Setting "Do not disturb" in KDE notification settings should also prevent notifications from the browser
https://bugs.kde.org/show_bug.cgi?id=457949 --- Comment #4 from myndstr...@protonmail.ch --- These notifications display in the top right, not the bottom right. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 457949] Setting "Do not disturb" in KDE notification settings should also prevent notifications from the browser
https://bugs.kde.org/show_bug.cgi?id=457949 --- Comment #3 from myndstr...@protonmail.ch --- Thanks for moving the issue. Yes, it's the Firefox in Debian11 stable. Currently I don't have plasma-browser-integration installed. Note the relatively old version in Debian. I think this problem occurred either always or most of the time. I expected browser notifications to get suppressed in this mode but then I thought it was browser-specific and has to be configured in the Firefox preferences. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 457855] [Nvidia Wayland] Max Refresh rate is Smaller than Display
https://bugs.kde.org/show_bug.cgi?id=457855 --- Comment #10 from nekone...@protonmail.ch --- This isn't the case in X11, so it's just an Nvidia Wayland bug? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 457970] When kwin_wayland crashes and takes down all your apps, ksmserver doesn't restart so it can restore them
https://bugs.kde.org/show_bug.cgi?id=457970 --- Comment #1 from Nate Graham --- Several other background-ish services also fail to restart in this case: ● plasma-baloorunner.service > ● plasma-krunner.service > ● plasma-kscreen-osd.service > ● plasma-ksmserver.service > ● plasma-kwallet-pam.service Could they all be fixed in a generic way, or would this require something to specially fix each of them? -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 200223] default language of spellchecker is ignored
https://bugs.kde.org/show_bug.cgi?id=200223 caulier.gil...@gmail.com changed: What|Removed |Added Status|REOPENED|RESOLVED Resolution|--- |FIXED Version Fixed In||8.0.0 --- Comment #10 from caulier.gil...@gmail.com --- With next 8.0.0 release, we will use KF5::Sonnet SpellChecker to perform spell error detection and provide correction. It will be available everywhere in digiKam where users needs to enter a text (aka captions, titles, etc.) The language will be automatically detected by powerful algorithms by parsing words entered in text widgets. If a text widget as a specific language property as XMP alternative languages strings, the selected language by user will be used to check words. It's explained in the new setup/Miscs/SpellCheck config panel, as rhe spellchecking in digiKam and Showfoto will not depend of KDE/Plasma desktop (after all, we work under Windows, MacOS, and other Linux desktops...) https://i.imgur.com/HI6wZ86.png Gilles Caulier -- You are receiving this mail because: You are watching all bug changes.
[Elisa] [Bug 457971] New: Add support for webm format
https://bugs.kde.org/show_bug.cgi?id=457971 Bug ID: 457971 Summary: Add support for webm format Product: Elisa Version: unspecified Platform: Manjaro OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: general Assignee: matthieu_gall...@yahoo.fr Reporter: tob...@g3ro.eu Target Milestone: --- SUMMARY Followup to https://bugs.kde.org/show_bug.cgi?id=457849. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 457855] [Nvidia Wayland] Max Refresh rate is Smaller than Display
https://bugs.kde.org/show_bug.cgi?id=457855 Zamundaaa changed: What|Removed |Added Resolution|--- |NOT A BUG Status|REPORTED|RESOLVED --- Comment #9 from Zamundaaa --- Your driver is reporting 30Hz to be the maximum refresh rate at the 3840x2160 resolution. Either that is the maximum refresh rate your gpu/cable/monitor can do, or it's a driver bug -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 457970] New: When kwin_wayland crashes and takes down all your apps, ksmserver doesn't restart so it can restore them
https://bugs.kde.org/show_bug.cgi?id=457970 Bug ID: 457970 Summary: When kwin_wayland crashes and takes down all your apps, ksmserver doesn't restart so it can restore them Product: plasmashell Version: master Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Startup process Assignee: plasma-b...@kde.org Reporter: n...@kde.org CC: k...@davidedmundson.co.uk Target Milestone: 1.0 Git master everything KDE on Fedora 35. STEPS TO REPRODUCE 1. Use systemd boot. 2. Make kwin_wayland crash, or else kill it yourself. OBSERVED RESULT Plasma restarts, but with no apps open that were open before, because ksmserver didn't restart too. EXPECTED RESULT ksmserver also restarts and re-opens all the apps you had open at the moment KWin crashed. ADDITIONAL INFORMATION If I manually run `systemctl --user restart plasma-ksmserver.service`, ksmserver launches and immediately restores all the apps that went down when KWin crashed. So it would be nice for this to happen automatically, somehow. -- You are receiving this mail because: You are watching all bug changes.
[Elisa] [Bug 457849] Support some more audio formats (and maybe video formats)
https://bugs.kde.org/show_bug.cgi?id=457849 --- Comment #4 from tob...@g3ro.eu --- (In reply to Nate Graham from comment #3) > > I think it would be useful to simply collect all format requests in one > > report. > > I'm afraid it would not. Please file additional bug reports for additional > format support requests. > > *** This bug has been marked as a duplicate of bug 457701 *** Ok, understood. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 453054] MYPAINT:Missing "dab per basic radius"
https://bugs.kde.org/show_bug.cgi?id=453054 Bug Janitor Service changed: What|Removed |Added Status|REPORTED|ASSIGNED Ever confirmed|0 |1 --- Comment #3 from Bug Janitor Service --- A possibly relevant merge request was started @ https://invent.kde.org/graphics/krita/-/merge_requests/1545 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 457969] New: Plasma crashes when dragging an applet to another desktop containment
https://bugs.kde.org/show_bug.cgi?id=457969 Bug ID: 457969 Summary: Plasma crashes when dragging an applet to another desktop containment Product: plasmashell Version: master Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Desktop Containment Assignee: plasma-b...@kde.org Reporter: m...@ratijas.tk CC: notm...@gmail.com Target Milestone: 1.0 Created attachment 151364 --> https://bugs.kde.org/attachment.cgi?id=151364=edit plasmashell stacktrace SUMMARY Plasma crashes when dragging an applet to another desktop containment STEPS TO REPRODUCE 0. Connect second monitor. 1. Put an applet on one desktop. 2. Enter Edit Mode. 3. Drag an applet to another desktop. OBSERVED RESULT Segfault, Plasma restarts, applet has disappeared and nowhere to be found. EXPECTED RESULT Welp, not this. SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE: git master Qt Version: 5.15.5 Kernel Version: 5.18.16-arch1-1 (64-bit) Graphics Platform: X11 Processors: 8 × Intel® Core™ i7-6700HQ CPU @ 2.60GHz Memory: 15.6 GiB of RAM Graphics Processor: NVIDIA GeForce GTX 970M/PCIe/SSE2 Manufacturer: ASUSTeK COMPUTER INC. Product Name: G752VT System Version: 1.0 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 200223] default language of spellchecker is ignored
https://bugs.kde.org/show_bug.cgi?id=200223 caulier.gil...@gmail.com changed: What|Removed |Added Resolution|FIXED |--- Ever confirmed|0 |1 Status|RESOLVED|REOPENED Version Fixed In|1.0.0 | -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 457925] Steam, Discord and other application does not appear in the systray
https://bugs.kde.org/show_bug.cgi?id=457925 thomas_toulo...@yahoo.com changed: What|Removed |Added Resolution|FIXED |WAITINGFORINFO -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 457939] Crash when opening "Configure "Desktop and Wallpaper..." from desktop.
https://bugs.kde.org/show_bug.cgi?id=457939 --- Comment #1 from frankhavebi...@gmail.com --- Created attachment 151363 --> https://bugs.kde.org/attachment.cgi?id=151363=edit New crash information added by DrKonqi systemsettings (5.25.4) using Qt 5.15.5 The crash occured for me when I clicked on "Configure Night Color" upon starting the machine. Why the KDE Settings Application would crash because of that is beyond my understanding. Perhaps opening up anything settings or Qt related quickly on startup is rarely going to result in this behaviour. -- Backtrace (Reduced): #11 0x7fcf86977e8b in QV4::QObjectWrapper::virtualResolveLookupGetter(QV4::Object const*, QV4::ExecutionEngine*, QV4::Lookup*) () from /usr/lib/libQt5Qml.so.5 [...] #14 0x7fcf8693a7f6 in QV4::Function::call(QV4::Value const*, QV4::Value const*, int, QV4::ExecutionContext const*) () from /usr/lib/libQt5Qml.so.5 #15 0x7fcf86a8ee6d in QQmlJavaScriptExpression::evaluate(QV4::CallData*, bool*) () from /usr/lib/libQt5Qml.so.5 #16 0x7fcf86a52121 in QQmlBoundSignalExpression::evaluate(void**) () from /usr/lib/libQt5Qml.so.5 [...] #18 0x7fcf86a758cf in QQmlNotifier::emitNotify(QQmlNotifierEndpoint*, void**) () from /usr/lib/libQt5Qml.so.5 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 457939] Crash when opening "Configure "Desktop and Wallpaper..." from desktop.
https://bugs.kde.org/show_bug.cgi?id=457939 frankhavebi...@gmail.com changed: What|Removed |Added CC||frankhavebi...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 449924] Windows are not resized back to original size when opening and closing a virtual keyboard such as Onboard
https://bugs.kde.org/show_bug.cgi?id=449924 Nate Graham changed: What|Removed |Added Component|general |virtual-keyboard -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 457925] Steam, Discord and other application does not appear in the systray
https://bugs.kde.org/show_bug.cgi?id=457925 thomas_toulo...@yahoo.com changed: What|Removed |Added Resolution|WAITINGFORINFO |FIXED -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 457925] Steam, Discord and other application does not appear in the systray
https://bugs.kde.org/show_bug.cgi?id=457925 thomas_toulo...@yahoo.com changed: What|Removed |Added Resolution|FIXED |WAITINGFORINFO -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 456417] Translucency
https://bugs.kde.org/show_bug.cgi?id=456417 Nate Graham changed: What|Removed |Added Resolution|--- |NOT A BUG Status|REPORTED|RESOLVED --- Comment #8 from Nate Graham --- I still can't tell if you're reporting a bug or requesting a feature, and if so, what it is. I don't think this is actionable unless you can describe the issue clearly and simply, without using references, analogies, sentence fragments, or tons of external links. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 457855] [Nvidia Wayland] Max Refresh rate is Smaller than Display
https://bugs.kde.org/show_bug.cgi?id=457855 --- Comment #8 from nekone...@protonmail.ch --- Created attachment 151362 --> https://bugs.kde.org/attachment.cgi?id=151362=edit drm_info (The requested drm_info terminal output) -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 385321] Screen locker 'unable to unlock, use loginctl instead' randomly when system is locked
https://bugs.kde.org/show_bug.cgi?id=385321 veeh...@zoho.com changed: What|Removed |Added CC||veeh...@zoho.com --- Comment #9 from veeh...@zoho.com --- i've been seeing this for a while (Fedora 34-36) and put it down to a few things that I can't isolate easily. Dell XPS13 9305 laptop (i5-1135g7) with built-in 4k screen on it's own works fine 100% reliably. While the laptop is in sleep, if i connect or disconnect either the official Dell USB-C HDMI dongle, or the Dell WD19TB dock with a 27" 2560x1440 screen then I'll see this issue maybe 80% of the time. being dongles/docks then i know there's multiple pieces of hardware being added/removed: display, audio, usb, etc etc. if i do not change these connections while in sleep state then it appears reliable so it's like the screenlocker cannot handle a change in hardware while in a sleep state. there also appears to be some sort of delay too; if i try to reproduce the issue with only a few seconds/minutes in sleep then the issue does not occur. if i leave it hours/overnight then the issue seems far more common. I've no issues if i connect/disconnect the dock/dongle once the session is unlocked. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 457855] [Nvidia Wayland] Max Refresh rate is Smaller than Display
https://bugs.kde.org/show_bug.cgi?id=457855 --- Comment #7 from Nate Graham --- Yeah. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 457949] Setting "Do not disturb" in KDE notification settings should also prevent notifications from the browser
https://bugs.kde.org/show_bug.cgi?id=457949 --- Comment #2 from Kai Uwe Broulik --- What browser is this? Firefox? -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 457855] [Nvidia Wayland] Max Refresh rate is Smaller than Display
https://bugs.kde.org/show_bug.cgi?id=457855 --- Comment #6 from nekone...@protonmail.ch --- Do I need to log back into the wayland session for this? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 455429] kwin sometimes composes windows in the wrong order when using the Slide Back effect
https://bugs.kde.org/show_bug.cgi?id=455429 Nate Graham changed: What|Removed |Added Ever confirmed|0 |1 Summary|kwin sometimes composes |kwin sometimes composes |windows in the wrong order |windows in the wrong order ||when using the Slide Back ||effect Status|REPORTED|CONFIRMED -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 455429] kwin sometimes composes windows in the wrong order
https://bugs.kde.org/show_bug.cgi?id=455429 Nate Graham changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=456873 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 456873] Unable to use activities since Plasma 5.25.0
https://bugs.kde.org/show_bug.cgi?id=456873 Nate Graham changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=455429 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kglobalaccel] [Bug 417087] Launching apps via global hotkeys does not display launch feedback on X11
https://bugs.kde.org/show_bug.cgi?id=417087 --- Comment #9 from Nicolas Fella --- It also work fine for me on X11 FWIW -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 457968] New: File rename modal blocks copy
https://bugs.kde.org/show_bug.cgi?id=457968 Bug ID: 457968 Summary: File rename modal blocks copy Product: kdevelop Version: 5.7.211203 Platform: Ubuntu Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: UI: general Assignee: kdevelop-bugs-n...@kde.org Reporter: master.ha...@gmail.com Target Milestone: --- SUMMARY *** Copying files opens up two modal dialogs that prevent eachother from being modified. Can not finish a copy that involves a rename of the file *** STEPS TO REPRODUCE 1. Copy file from a folder to the same folder 2. Rename and copy dialogs pop up 3. Can not click anything, completely locks the ui. OBSERVED RESULT The two dialogs locks the ui entirely and requires the process to be killed EXPECTED RESULT only one dialog popup at a time or neither should be modal. SOFTWARE/OS VERSIONS Linux/KDE Plasma: ubuntu 22.04.1 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 457855] [Nvidia Wayland] Max Refresh rate is Smaller than Display
https://bugs.kde.org/show_bug.cgi?id=457855 --- Comment #5 from nekone...@protonmail.ch --- neko-san@ARCH ~> doas pacman -Qo drm_info doas (neko-san@ARCH) password: error: No package owns drm_info It's not in the Arch repos but it's on the AUR, so I'll get it from there -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 397120] Global shortcuts imported from .desktop files do not refresh commands
https://bugs.kde.org/show_bug.cgi?id=397120 Nicolas Fella changed: What|Removed |Added CC||nicolas.fe...@gmx.de --- Comment #1 from Nicolas Fella --- I think this must have been fixed at some point. The kcm doesn't copy desktop files, it only pokes kglobalacceld to read the original desktop file -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 454396] Kickoff does not find application whose name was edited via 'Edit application' window and then removed from Shortcut KCM
https://bugs.kde.org/show_bug.cgi?id=454396 Bug Janitor Service changed: What|Removed |Added Status|CONFIRMED |ASSIGNED --- Comment #2 from Bug Janitor Service --- A possibly relevant merge request was started @ https://invent.kde.org/frameworks/kglobalaccel/-/merge_requests/54 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kglobalaccel] [Bug 440507] Command-line arguments specified in exec= line get removed
https://bugs.kde.org/show_bug.cgi?id=440507 h...@runiq.de changed: What|Removed |Added CC||h...@runiq.de -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 457935] Conflict with MIME type and preview
https://bugs.kde.org/show_bug.cgi?id=457935 --- Comment #3 from MILAS Robin --- Created attachment 151361 --> https://bugs.kde.org/attachment.cgi?id=151361=edit File properties Type is set to "application/x-iso-image" as well as associated app "Content" field match "application/x-gamecube-image" but associated app are not even proposed nor the preview. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 457935] Conflict with MIME type and preview
https://bugs.kde.org/show_bug.cgi?id=457935
--- Comment #2 from MILAS Robin ---
I don't see the issue content so I will add it back there.
I've got an issue with my custom thumbnailer. I checked it and my thumbnailer
work and even produce thumbnail for the parent folder.
However, the preview of the file is not displayed on the file in question.
The file is a gamecube ISO file. It seems that dolphin use the generic ISO
("raw CD image" MIME:"application/x-cd-image") instead of its dedicated MIME:
"application/x-gamecube-rom".
"xdg-mime query filetype" does correctly report the file as an
"application/x-gamecube-rom".
Dolphin seems to inconsistently use both MIME as the preview work on the parent
folder but not on the file in question as well as proposed programs are the one
for "application/x-cd-image" ignoring totaly the
"application/x-gamecube-rom"associated programs.
--
You are receiving this mail because:
You are watching all bug changes.
[plasmashell] [Bug 457949] Setting "Do not disturb" in KDE notification settings should also prevent notifications from the browser
https://bugs.kde.org/show_bug.cgi?id=457949 Kai Uwe Broulik changed: What|Removed |Added Assignee|k...@privat.broulik.de |plasma-b...@kde.org Version|unspecified |5.18.8 CC||k...@privat.broulik.de Component|general |Notifications Target Milestone|--- |1.0 Product|plasma-browser-integration |plasmashell --- Comment #1 from Kai Uwe Broulik --- plasma-browser-integration does not affect browser notifications. It's strange that the browser could bypass do not disturb mode, that's a bug in notifications then. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 457935] Conflict with MIME type and preview
https://bugs.kde.org/show_bug.cgi?id=457935 MILAS Robin changed: What|Removed |Added Summary|Preview does not work for |Conflict with MIME type and |some large ISO files|preview --- Comment #1 from MILAS Robin --- Additional Information: It seems to be linked to a MIME-Type detection which partially fail ! -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 457847] kwin becomes unresponsive, need to restart session
https://bugs.kde.org/show_bug.cgi?id=457847 Ralf Jung changed: What|Removed |Added Severity|normal |crash --- Comment #1 from Ralf Jung --- Actually turns out this can happen without vsocde being involved. It just happened while I was just using my webbrowser, not starting any new application. There was still a black square in the bottom right corner though. Maybe that is from a plasma notification? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 457847] kwin becomes unresponsive, need to restart session
https://bugs.kde.org/show_bug.cgi?id=457847 Ralf Jung changed: What|Removed |Added Summary|kwin becomes unresponsive |kwin becomes unresponsive, |sometimes when starting |need to restart session |vscode | -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 457956] most plasma desktop events are delayed (toggling the app launcher, actions applet)
https://bugs.kde.org/show_bug.cgi?id=457956 Patrick Silva changed: What|Removed |Added CC||bugsefor...@gmx.com --- Comment #4 from Patrick Silva --- same symptoms reported as bug 454379 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 376345] can't disable "auto spell check" while editing metadata
https://bugs.kde.org/show_bug.cgi?id=376345 caulier.gil...@gmail.com changed: What|Removed |Added Resolution|--- |FIXED Version Fixed In||8.0.0 Latest Commit||https://invent.kde.org/grap ||hics/digikam/commit/09e9acc ||42caf0d6bab9631e8ea287f728b ||f51cec Status|REOPENED|RESOLVED --- Comment #9 from caulier.gil...@gmail.com --- Git commit 09e9acc42caf0d6bab9631e8ea287f728bf51cec by Gilles Caulier. Committed on 16/08/2022 at 17:19. Pushed by cgilles into branch 'master'. Spell Checking config widget: show backend and dictionary lists. FIXED-IN: 8.0.0 M +2-21 core/libs/dialogs/libsinfodlg.cpp M +1-0core/libs/widgets/CMakeLists.txt M +84 -6core/libs/widgets/text/spellcheckconfig.cpp https://invent.kde.org/graphics/digikam/commit/09e9acc42caf0d6bab9631e8ea287f728bf51cec -- You are receiving this mail because: You are watching all bug changes.
[kleopatra] [Bug 384013] Kleopatra does not save revocation certificate
https://bugs.kde.org/show_bug.cgi?id=384013 Erik Moeller changed: What|Removed |Added CC||eloque...@gmail.com --- Comment #3 from Erik Moeller --- I'm seeing the same behavior in version 3.1.11 (the version included in current Tails OS). It appears to be related to how the `gpg` operations are performed; if I run Kleopatra from a terminal, I can save the revocation successfully (and see the `gpg` output in the terminal); if I run it without a TTY, I also cannot save successfully. -- You are receiving this mail because: You are watching all bug changes.
