[kwin] [Bug 467989] trying to open video file in vlc crashes xwayland
https://bugs.kde.org/show_bug.cgi?id=467989 --- Comment #4 from Martin Tlustos --- Well, it doesn't crash under X11... sent from my Android phone David Edmundson schrieb am Fr., 31. März 2023, 13:26: > https://bugs.kde.org/show_bug.cgi?id=467989 > > David Edmundson changed: > >What|Removed |Added > > > Resolution|--- |DOWNSTREAM > Status|REPORTED|RESOLVED > CC||k...@davidedmundson.co.uk > > --- Comment #3 from David Edmundson --- > If xwayland crashes it needs reporting to X. > > There's not much we can do our side. > > -- > You are receiving this mail because: > You reported the bug. -- You are receiving this mail because: You are watching all bug changes.
[LabPlot2] [Bug 456328] Labplot 2.9 does not run
https://bugs.kde.org/show_bug.cgi?id=456328 --- Comment #9 from Peter --- (In reply to Alexander Semke from comment #8) > (In reply to Peter from comment #7) > > In deep, I have a Dell notebook, with Dell Optimizer running in the > > background. However, even with the optimizer running in the background, I > > can execute the old pre-2.9.0-official release version. I have a > > labplot2.exe dated 2021-12-20. This LabPlot comes up and runs rather > > instantaneously. With this in mind: is a background task responsible for > > labplot2 2.9 and newer not firing up? > The only thing that comes to mind mind now is the loading of plugins for the > Notebook in Labplot (for Maxima, python, etc.). > There were some changes in the location of plugins and probably also in > their number, but I don't remember the details anymore. > > > > However, I will test version 2.10 again, then without the Dell background > > manager working in the background. I will inform you again. > Yes, please try it out without all that stuff running in the background and > let us know. Thank you. Good morning, what I did: I have another Dell, a PC, in the same network, also up-to-date Windows 10. Even though the dell services are the same as those on my notebook, the LabPlot2 2.10 main windows poped up almost immediately. Because of this experiment, I do not suspect the Dell services to be the reason for the failing on my notebook. The mayor difference I see: the notebook combines a Intel UHD graphics with a NVIDIA Graphics, while the Dell PC only has the NVIDIA Graphics. And still: Labplot2 in version pre-2.9.x (2022-12-20) runs on my notebook but Laplot 2.9 ff. do not. I reported this error because it seems that I am not the only one. Best regards and thank you for your efforts, Peter. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 468023] New: Krita Version: 5.1.5 Hidpi: true Qt Version (compiled): 5.12.12 Version (loaded): 5.12.12 OS Information Build ABI: x86_64-little_endian-lp64 Build CPU: x86_64 CPU: x86_64
https://bugs.kde.org/show_bug.cgi?id=468023 Bug ID: 468023 Summary: Krita Version: 5.1.5 Hidpi: true QtVersion (compiled): 5.12.12 Version (loaded): 5.12.12 OS InformationBuild ABI: x86_64-little_endian-lp64 Build CPU: x86_64 CPU: x86_64 Kernel Type: darwin Kernel Version: 19.6.0 Pretty Productnam Classification: Applications Product: krita Version: 5.1.5 Platform: Other OS: macOS Status: REPORTED Severity: crash Priority: NOR Component: * Unknown Assignee: krita-bugs-n...@kde.org Reporter: resh501...@gmail.com Target Milestone: --- Krita Version: 5.1.5 Hidpi: true Qt Version (compiled): 5.12.12 Version (loaded): 5.12.12 OS Information Build ABI: x86_64-little_endian-lp64 Build CPU: x86_64 CPU: x86_64 Kernel Type: darwin Kernel Version: 19.6.0 Pretty Productname: macOS 10.15 Product Type: osx Product Version: 10.15 Locale Languages: es C locale: C QLocale current: en QLocale system: en QTextCodec for locale: UTF-8 OpenGL Info Vendor: "Intel Inc." Renderer: "Intel HD Graphics 4000 OpenGL Engine" Version: "4.1 INTEL-14.7.20" Shading language: "4.10" Requested format: QSurfaceFormat(version 3.2, options QFlags(), depthBufferSize 24, redBufferSize 8, greenBufferSize 8, blueBufferSize 8, alphaBufferSize 8, stencilBufferSize 8, samples -1, swapBehavior QSurfaceFormat::DoubleBuffer, swapInterval 0, colorSpace QSurfaceFormat::DefaultColorSpace, profile QSurfaceFormat::CoreProfile) Current format: QSurfaceFormat(version 4.1, options QFlags(), depthBufferSize 24, redBufferSize 8, greenBufferSize 8, blueBufferSize 8, alphaBufferSize 8, stencilBufferSize 8, samples 0, swapBehavior QSurfaceFormat::DoubleBuffer, swapInterval 0, colorSpace QSurfaceFormat::DefaultColorSpace, profile QSurfaceFormat::CoreProfile) Version: 4.1 Supports deprecated functions false is OpenGL ES: false supportsBufferMapping: true supportsBufferInvalidation: false forceDisableTextureBuffers: false Extensions: "GL_APPLE_rgb_422" "GL_EXT_texture_filter_anisotropic" "GL_ARB_shader_bit_encoding" "GL_ARB_blend_func_extended" "GL_ARB_instanced_arrays" "GL_ATI_texture_mirror_once" "GL_ARB_tessellation_shader" "GL_EXT_framebuffer_multisample_blit_scaled" "GL_APPLE_container_object_shareable" "GL_EXT_debug_label" "GL_ARB_texture_storage" "GL_ARB_texture_gather" "GL_APPLE_client_storage" "GL_ARB_texture_rgb10_a2ui" "GL_ARB_vertex_attrib_64bit" "GL_EXT_debug_marker" "GL_ARB_internalformat_query" "GL_ARB_texture_swizzle" "GL_EXT_texture_sRGB_decode" "GL_EXT_texture_compression_s3tc" "GL_ARB_gpu_shader_fp64" "GL_ARB_ES2_compatibility" "GL_ARB_gpu_shader5" "GL_ARB_timer_query" "GL_APPLE_flush_render" "GL_ARB_shader_subroutine" "GL_ARB_transform_feedback3" "GL_ARB_draw_indirect" "GL_ARB_texture_buffer_object_rgb32" "GL_ARB_vertex_type_2_10_10_10_rev" "GL_APPLE_texture_range" "GL_ARB_explicit_attrib_location" "GL_ARB_texture_cube_map_array" "GL_ARB_sampler_objects" "GL_ARB_shading_language_include" "GL_ARB_draw_buffers_blend" "GL_ARB_sample_shading" "GL_ARB_viewport_array" "GL_ARB_separate_shader_objects" "GL_ARB_texture_query_lod" "GL_NV_texture_barrier" "GL_ARB_transform_feedback2" "GL_APPLE_object_purgeable" "GL_APPLE_row_bytes" "GL_ARB_occlusion_query2" QPA OpenGL Detection Info supportsDesktopGL: true supportsOpenGLES: false isQtPreferOpenGLES: false useBufferInvalidation (config option): false Hardware Information GPU Acceleration: auto Memory: 12288 Mb Number of Cores: 4 Swap Location: /private/var/folders/sx/3_wdfh7571zd325syjh6z0c4gp/T Built for: sse4.1 Base instruction set: sse4.1 Supported instruction sets: sse4.2 sse4.1 ssse3 sse3 sse2 Current Settings Current Swap Location: /private/var/folders/sx/3_wdfh7571zd325syjh6z0c4gp/T Current Swap Location writable: true Undo Enabled: true Undo Stack Limit: 200 Use OpenGL: true Use OpenGL Texture Buffer: true Disable Vector Optimizations: false Disable AVX Optimizations: false Canvas State: OPENGL_SUCCESS Autosave Interval: 420 Use Backup Files: true Number of Backups Kept: 1 Backup File Suffix: ~ Backup Location: Same Folder as the File Backup Location writable: false Resource Location: Use Win8 Pointer Input: false Use RightMiddleTabletButton Workaround: false Levels of Detail Enabled: false Use Zip64: false Loaded Python Plugins colorspace comics_project_management_tools documenttools
[docs.kde.org] [Bug 468022] New: Not found page
https://bugs.kde.org/show_bug.cgi?id=468022 Bug ID: 468022 Summary: Not found page Classification: Websites Product: docs.kde.org Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Missing Content Assignee: kde-doc-engl...@kde.org Reporter: taha_zerro...@hotmail.com Target Milestone: --- SUMMARY *** I tried to visit https://edu.kde.org/kturtle/translator.php, it's not found STEPS TO REPRODUCE 1. from navigator . OBSERVED RESULT not found EXPECTED RESULT the page SOFTWARE/OS VERSIONS Linux/KDE Plasma: firefox ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 365787] Ability to modify user's groups via GUI
https://bugs.kde.org/show_bug.cgi?id=365787 Aroun changed: What|Removed |Added CC||k...@b-vo.fr -- You are receiving this mail because: You are watching all bug changes.
[kuser] [Bug 376157] kf5 kuser
https://bugs.kde.org/show_bug.cgi?id=376157 Aroun changed: What|Removed |Added CC||k...@b-vo.fr -- You are receiving this mail because: You are watching all bug changes.
[krusader] [Bug 450765] krusader crash on pressing F3 to view a TWRP backup file.
https://bugs.kde.org/show_bug.cgi?id=450765 Bug Janitor Service changed: What|Removed |Added Resolution|WAITINGFORINFO |WORKSFORME Status|NEEDSINFO |RESOLVED --- Comment #3 from Bug Janitor Service --- This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 462561] System freeze when browsing movies with Firefox at amazon
https://bugs.kde.org/show_bug.cgi?id=462561 --- 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 466545] Krita not saving layer styles and forgetting layer style parameters
https://bugs.kde.org/show_bug.cgi?id=466545 --- Comment #4 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.
[kwin] [Bug 463612] Electron apps hang GUI when run with Wayland backend
https://bugs.kde.org/show_bug.cgi?id=463612 --- Comment #3 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.
[krusader] [Bug 453474] Crashes with multiple files selected that are being updated outside the app
https://bugs.kde.org/show_bug.cgi?id=453474 Bug Janitor Service changed: What|Removed |Added Resolution|WAITINGFORINFO |WORKSFORME Status|NEEDSINFO |RESOLVED --- Comment #3 from Bug Janitor Service --- This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 433462] While an unpinned app is launching, its tooltip shows the wrong subtitle
https://bugs.kde.org/show_bug.cgi?id=433462 --- Comment #7 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 445223] Dragging icons in task manager stops working after a few drags
https://bugs.kde.org/show_bug.cgi?id=445223 --- Comment #8 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.
[krusader] [Bug 453754] Krusader crashes when trying to open (any) file in viewer
https://bugs.kde.org/show_bug.cgi?id=453754 Bug Janitor Service changed: What|Removed |Added Resolution|WAITINGFORINFO |WORKSFORME Status|NEEDSINFO |RESOLVED --- Comment #4 from Bug Janitor Service --- This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[frameworks-knewstuff] [Bug 466677] Failed to Install
https://bugs.kde.org/show_bug.cgi?id=466677 Bug Janitor Service changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |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.
[KScreen] [Bug 466641] Third monitor does not applies its state on reboot
https://bugs.kde.org/show_bug.cgi?id=466641 Bug Janitor Service changed: What|Removed |Added Resolution|WAITINGFORINFO |WORKSFORME Status|NEEDSINFO |RESOLVED --- Comment #7 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.
[kwin] [Bug 466669] Plasmashell crashes on Arma 3 launch through steam.
https://bugs.kde.org/show_bug.cgi?id=49 Bug Janitor Service changed: What|Removed |Added Resolution|BACKTRACE |WORKSFORME Status|NEEDSINFO |RESOLVED --- 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.
[plasmashell] [Bug 466635] Notifications still pop up on main screen when Do Not Disturb is checked on multi monitor setup
https://bugs.kde.org/show_bug.cgi?id=466635 Bug Janitor Service changed: What|Removed |Added Resolution|WAITINGFORINFO |WORKSFORME Status|NEEDSINFO |RESOLVED --- 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.
[kwin] [Bug 467469] Can’t enable Mouse Click Animation desktop effect by default
https://bugs.kde.org/show_bug.cgi?id=467469 --- 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.
[krusader] [Bug 456628] krusader shows dir with dot as file in fish session since 2.6.x
https://bugs.kde.org/show_bug.cgi?id=456628 Bug Janitor Service changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|UNMAINTAINED|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.
[plasmashell] [Bug 441471] Taskbar label missing after closing program
https://bugs.kde.org/show_bug.cgi?id=441471 --- Comment #7 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 401741] Icons-only Task Manager High CPU when switching Users
https://bugs.kde.org/show_bug.cgi?id=401741 --- Comment #8 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.
[frameworks-qqc2-desktop-style] [Bug 467390] Use of checkboxes for mutually exclusive menu items is very misleading
https://bugs.kde.org/show_bug.cgi?id=467390 Nate Graham changed: What|Removed |Added Version Fixed In||5.105 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 468021] Debian firmware package "firmware-amd-graphics" incompatible with Kwin
https://bugs.kde.org/show_bug.cgi?id=468021 Bug Janitor Service changed: What|Removed |Added Resolution|--- |DOWNSTREAM Status|REPORTED|RESOLVED --- Comment #1 from Bug Janitor Service --- Thank you for the bug report! However Plasma 5.20.5 is no longer eligible for support or maintenance from KDE; supported versions are 5.27, and 5.27 or newer. Please upgrade to a supported version as soon as your distribution makes it available to you. Plasma is a fast-moving project, and bugs in one version are often fixed in the next one. If you need support for Plasma 5.20.5, please contact your distribution, who bears the responsibility of providing support for older releases that are no longer supported by KDE. If you can reproduce the issue after upgrading to a supported version, feel free to re-open this bug report. -- You are receiving this mail because: You are watching all bug changes.
[ksmserver] [Bug 467547] Logging out of Plasma 5.27.3 on Wayland as the second user on the system resulted in a black screen
https://bugs.kde.org/show_bug.cgi?id=467547 Matt Fagnani changed: What|Removed |Added CC||plasma-b...@kde.org Assignee|kwin-bugs-n...@kde.org |k...@davidedmundson.co.uk Product|kwin|ksmserver Component|wayland-generic |general --- Comment #7 from Matt Fagnani --- If the user's session isn't stopped properly due to the failure of dbus-:1.2-org.kde.LogoutPrompt which runs /usr/libexec/ksmserver-logout-greeter from /usr/share/dbus-1/services/org.kde.LogoutPrompt.service, then the sddm session might not be started and sddm might be left waiting indefinitely, I'm reassigning this report to ksmserver due to that error and the failure of the user session to stop and the sddm session to start. This black screen problem happened most of the time I've logged out as the second and third users which were of the standard account type in my Fedora 38 installation. A race condition might be involved. This problem was accepted as a Fedora 38 Final blocker https://bugzilla.redhat.com/show_bug.cgi?id=2179591#c23 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 468021] New: Debian firmware package "firmware-amd-graphics" incompatible with Kwin
https://bugs.kde.org/show_bug.cgi?id=468021 Bug ID: 468021 Summary: Debian firmware package "firmware-amd-graphics" incompatible with Kwin Classification: Plasma Product: kwin Version: 5.20.5 Platform: Debian stable OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kwin-bugs-n...@kde.org Reporter: bcp12...@gmail.com Target Milestone: --- Application: kwin_x11 (5.20.5) Qt Version: 5.15.2 Frameworks Version: 5.78.0 Operating System: Linux 5.10.0-21-amd64 x86_64 Windowing system: X11 Distribution: Debian GNU/Linux 11 (bullseye) -- Information about the crash: - What I was doing when the application crashed: Booting the machine - Unusual behavior I noticed: The machine boots. But graphical logon display managers SDDM and LightDm fail. XDM seems to work, however. Command line logon is successful. But GUI fails at bootsplash, first the bootsplash segfaults and immediately afterward Kwin segfaults. - Custom settings of the application: There are really no custom setting issues. The problem is directly related to the firmware. If I remove the package, the system boots fine. If I reinstall it the same behavior occurs. Without the firmware, the video acceleration for my gpu is disabled. So I'd like to have it working The crash can be reproduced every time. -- Backtrace: Application: KWin (kwin_x11), signal: Segmentation fault [KCrash Handler] #4 0x in ?? () #5 0x7f00027cd5af in ?? () from /usr/lib/x86_64-linux-gnu/dri/r300_dri.so #6 0x7f00022e9804 in ?? () from /usr/lib/x86_64-linux-gnu/dri/r300_dri.so #7 0x7f00022eab94 in ?? () from /usr/lib/x86_64-linux-gnu/dri/r300_dri.so #8 0x7f00022cc95e in ?? () from /usr/lib/x86_64-linux-gnu/dri/r300_dri.so #9 0x7f00027cbc73 in ?? () from /usr/lib/x86_64-linux-gnu/dri/r300_dri.so #10 0x7f00084b35df in dri2_destroy_context (context=0x564a653865f0) at ../src/glx/dri2_glx.c:123 #11 0x7f00084a1e49 in glXDestroyContext (ctx=0x564a653865f0, dpy=0x564a6529b290) at ../src/glx/glxcmds.c:510 #12 glXDestroyContext (dpy=0x564a6529b290, ctx=0x564a653865f0) at ../src/glx/glxcmds.c:491 #13 0x7f00085121b5 in QGLXContext::~QGLXContext (this=0x564a6537db00, __in_chrg=) at qglxintegration.cpp:541 #14 QGLXContext::~QGLXContext (this=0x564a6537db00, __in_chrg=) at qglxintegration.cpp:542 #15 0x7f00100054fb in QOpenGLContext::destroy (this=this@entry=0x564a65366f30) at kernel/qopenglcontext.cpp:653 #16 0x7f00100057a7 in QOpenGLContext::~QOpenGLContext (this=0x564a65366f30, __in_chrg=) at kernel/qopenglcontext.cpp:691 #17 0x7f00100057b9 in QOpenGLContext::~QOpenGLContext (this=0x564a65366f30, __in_chrg=) at kernel/qopenglcontext.cpp:696 #18 0x7f0010e14090 in checkBackend () at ./src/quickaddons/qtquicksettings.cpp:44 #19 KQuickAddons::QtQuickSettings::init () at ./src/quickaddons/qtquicksettings.cpp:64 #20 0x564a647b7d24 in main (argc=, argv=0x7ffc01452d78) at ./main_x11.cpp:430 [Inferior 1 (process 854) detached] Possible duplicates by query: bug 431817, bug 382949, bug 366513, bug 317583, bug 317282. Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 467675] digiKam fail to export to WEBP format.
https://bugs.kde.org/show_bug.cgi?id=467675 --- Comment #37 from Geoff King --- (In reply to caulier.gilles from comment #32) > Geoff, > > Here you can find the AppImage demo loading a JPEG, editing with GMIC-Qt/B > and exporting to WEBP. As you can see all work as expected and metadata are > there... > > https://drive.google.com/file/d/18VxKzFfXsC02-euPluy1XmemknNfbmr_/ > view?usp=sharing > > I reproduced the same under MacOS without problem... > Hi Gilles, Here is a screencast of MacOS and Digikam 8.0.0 (3/30/2023) editing in GMIC filter and exporting to WEBP. The resulting thumbnail shows an image, but nothing in preview or editor. This affects WEBP and I have had no issues with other formats like PNG or JPEG or other built-in digikam effects. This also looks to affect Windows, but not Linux. I just picked a random photo, it happens to all (several) that I've tried. https://drive.google.com/file/d/1XuLik9J9X8WRuk8Xa761NdWVhAVmRogv/view?usp=share_link I also did another test where I used exiftool to remove all metadata from the WEBP version and then the thumbnail turned transparent. Regards, Geoff -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 467675] digiKam fail to export to WEBP format.
https://bugs.kde.org/show_bug.cgi?id=467675 --- Comment #36 from Geoff King --- (In reply to Maik Qualmann from comment #33) > The WBMP format probably comes from Qt directly. It's not relevant to us at > all. It comes from old cell phones and is a 1-Bit black and white format. It > has nothing to do with modern Webp. > > Maik Okay. I misunderstood this format. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 468016] Caption information is written to Exif UserComment and no option exists to disable
https://bugs.kde.org/show_bug.cgi?id=468016 caulier.gil...@gmail.com changed: What|Removed |Added Platform|Other |Microsoft Windows OS|Other |Microsoft Windows CC||caulier.gil...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 467634] Spectacle not respecting scaling when saving or copying to clipboard
https://bugs.kde.org/show_bug.cgi?id=467634 --- Comment #3 from Nathaniel Mason --- Just updated to 23.03.90, and it all seems to be working as expected again. Although I downgraded back to 23.03.80 out of curiosity and it's suddenly working properly again, so that's a bit bizarre. Either way, really nice to have it working again! -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 358277] On X11, Chrome apps use the icon from chrome browser in Icon-Only Task Manager
https://bugs.kde.org/show_bug.cgi?id=358277 Alex changed: What|Removed |Added CC||alex.selez...@gmail.com --- Comment #42 from Alex --- Confirmed for me too. Setting #ozone-platform-hint at chrome://flags solved it on KDE with Wayland -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 468019] Crash when clicking on a Slack notification
https://bugs.kde.org/show_bug.cgi?id=468019 --- Comment #1 from P Fudd --- Additionally, the KDE Crash Handler hung after submitting this bug report. The window says "Submitting bug report..." and has a spinning gear, but this bug has already been submitted. Not sure why it's still, uh, "spinning its gears", but that would be a good thing to fix. -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 468020] Window outline inconsistent between windows and sides of the same window and mispositioned
https://bugs.kde.org/show_bug.cgi?id=468020 Luca Carlon changed: What|Removed |Added Attachment #157756|VLC looks reasonable. |vlc.png description|| -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 468020] Window outline inconsistent between windows and sides of the same window and mispositioned
https://bugs.kde.org/show_bug.cgi?id=468020 Luca Carlon changed: What|Removed |Added Attachment #157755|Different look of the |konversation.png description|outline on two sides of a | |window. | -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 468020] Window outline inconsistent between windows and sides of the same window and mispositioned
https://bugs.kde.org/show_bug.cgi?id=468020 --- Comment #2 from Luca Carlon --- Created attachment 157757 --> https://bugs.kde.org/attachment.cgi?id=157757=edit settings.png -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 468020] Window outline inconsistent between windows and sides of the same window and mispositioned
https://bugs.kde.org/show_bug.cgi?id=468020 --- Comment #1 from Luca Carlon --- Created attachment 157756 --> https://bugs.kde.org/attachment.cgi?id=157756=edit VLC looks reasonable. -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 468020] New: Window outline inconsistent between windows and sides of the same window and mispositioned
https://bugs.kde.org/show_bug.cgi?id=468020 Bug ID: 468020 Summary: Window outline inconsistent between windows and sides of the same window and mispositioned Classification: Plasma Product: Breeze Version: 5.27.3 Platform: Manjaro OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: window decoration Assignee: plasma-b...@kde.org Reporter: carlon.l...@gmail.com CC: kwin-bugs-n...@kde.org, uhh...@gmail.com Target Milestone: --- Created attachment 157755 --> https://bugs.kde.org/attachment.cgi?id=157755=edit Different look of the outline on two sides of a window. SUMMARY The new outline feature in 5.27 may be appreciated or not, but I would like to point out a couple of things that made me think that it was a bug at first. I attached a few images to show what I see. If you zoom in a lot you'll clearly see the problems. 1. konversation.png: this image shows the bottom left corner of konversation. As you can see the left border has an outline, the bottom border does not seem to have the outline. The result is bad and seems buggy. 2. vlc.png: in this image, the outline looks identical on all sides. This does not seem buggy. 3. settings.png: the outline on the left and at the top is not contiguous to the window. There is a transparent line between the window and the outline. I do not clearly understand if this is expected, I do not think so, but in any case it does not seem to be consistent with what I see in other windows (like in vlc.png), and it is not even consistent with the outline at the bottom. This can also be seen in konversation.png. STEPS TO REPRODUCE 1. 2. 3. OBSERVED RESULT Outline is missing or mispositioned, inconsistent between different windows and even between sides of the same window. EXPECTED RESULT I am not sure what the expected result was. According to some images I saw online, like these https://invent.kde.org/plasma/breeze/uploads/2eeb591d95a296adfa2daee4a985351e/Screenshot_20230302_181452.png, I guess there shouldn't be a transparent line and the outline should be identical on all sides. I'd also expect it to be identical for all windows. SOFTWARE/OS VERSIONS KDE Plasma Version: 5.27.3 KDE Frameworks Version: 5.104.0 Qt Version: 5.15.8 Linux: 6.1.21-1-MANJARO (64-bit) Wayland -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 468019] New: Crash when clicking on a Slack notification
https://bugs.kde.org/show_bug.cgi?id=468019 Bug ID: 468019 Summary: Crash when clicking on a Slack notification Classification: Frameworks and Libraries Product: Akonadi Version: unspecified Platform: Fedora RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: server Assignee: kdepim-b...@kde.org Reporter: bugs.kde@ch.pkts.ca Target Milestone: --- Application: akonadiserver (5.22.3 (22.12.3)) Qt Version: 5.15.8 Frameworks Version: 5.104.0 Operating System: Linux 6.2.8-200.fc37.x86_64 x86_64 Windowing System: Wayland Distribution: "Fedora release 37 (Thirty Seven)" DrKonqi: 5.27.3 [KCrashBackend] -- Information about the crash: I clicked on a notification, and suddenly I was logged out of everything, and the KDE Crash Handler started up. This has happened a few times today, and I'm now reluctant to click on any notifications. The crash can be reproduced sometimes. -- Backtrace: Application: Akonadi Server (akonadiserver), signal: Segmentation fault [KCrash Handler] #4 std::default_delete::operator() (__ptr=0x111, this=) at /usr/include/c++/12/bits/unique_ptr.h:89 #5 std::unique_ptr >::~unique_ptr (this=, this=) at /usr/include/c++/12/bits/unique_ptr.h:396 #6 std::__new_allocator > >::destroy > > (__p=, this=0x7fffa07abf58) at /usr/include/c++/12/bits/new_allocator.h:181 #7 std::allocator_traits > > >::destroy > > (__p=, __a=...) at /usr/include/c++/12/bits/alloc_traits.h:535 #8 std::vector >, std::allocator > > >::_M_erase (__position=..., this=0x7fffa07abf58) at /usr/include/c++/12/bits/vector.tcc:181 #9 std::vector >, std::allocator > > >::erase (__position=..., this=0x7fffa07abf58) at /usr/include/c++/12/bits/stl_vector.h:1530 #10 Akonadi::Server::AkonadiServer::connectionDisconnected (this=0x7fffa07abed0) at /usr/src/debug/kf5-akonadi-server-22.12.3-1.fc37.x86_64/src/server/akonadi.cpp:234 #11 0x7fb423ec8134 in QObject::event (this=0x7fffa07abed0, e=0x7fb3ac048720) at kernel/qobject.cpp:1347 #12 0x7fb423e9d4cb in doNotify (event=0x7fb3ac048720, receiver=0x7fffa07abed0) at kernel/qcoreapplication.cpp:1154 #13 QCoreApplication::notify (event=, receiver=, this=) at kernel/qcoreapplication.cpp:1140 #14 QCoreApplication::notifyInternal2 (receiver=0x7fffa07abed0, event=0x7fb3ac048720) at kernel/qcoreapplication.cpp:1064 #15 0x7fb423e9d6d2 in QCoreApplication::sendEvent (receiver=, event=) at kernel/qcoreapplication.cpp:1462 #16 0x7fb423ea0854 in QCoreApplicationPrivate::sendPostedEvents (receiver=0x0, event_type=0, data=0x56201ede8020) at kernel/qcoreapplication.cpp:1821 #17 0x7fb423ea0aec in QCoreApplication::sendPostedEvents (receiver=, event_type=) at kernel/qcoreapplication.cpp:1680 #18 0x7fb423eeeb07 in postEventSourceDispatch (s=0x56201edec980) at kernel/qeventdispatcher_glib.cpp:277 #19 0x7fb422118c7f in g_main_context_dispatch () from /lib64/libglib-2.0.so.0 #20 0x7fb42216f118 in g_main_context_iterate.constprop () from /lib64/libglib-2.0.so.0 #21 0x7fb422115f00 in g_main_context_iteration () from /lib64/libglib-2.0.so.0 #22 0x7fb423eee5fa in QEventDispatcherGlib::processEvents (this=0x56201ede9df0, flags=...) at kernel/qeventdispatcher_glib.cpp:423 #23 0x7fb423e9bf3a in QEventLoop::exec (this=this@entry=0x7fffa07abd40, flags=..., flags@entry=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:69 #24 0x7fb423ea4002 in QCoreApplication::exec () at ../../include/QtCore/../../src/corelib/global/qflags.h:121 #25 0x56201d472058 in AkApplicationBase::exec (this=0x7fffa07abea0) at /usr/src/debug/kf5-akonadi-server-22.12.3-1.fc37.x86_64/src/shared/akapplication.cpp:107 #26 main (argc=, argv=) at /usr/src/debug/kf5-akonadi-server-22.12.3-1.fc37.x86_64/src/server/main.cpp:65 [Inferior 1 (process 4876) detached] Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[plasma-systemmonitor] [Bug 451074] Graphing percentage sensors with scalar value sensors
https://bugs.kde.org/show_bug.cgi?id=451074 Will Styler changed: What|Removed |Added CC||w...@savethevowels.org --- Comment #1 from Will Styler --- I'd like to second this request. In my case, I'd like to be able to have three horizontal bar graphs for CPU usage (reported as 0-100%), Memory usage (reported as 0-100%), and GPU VRAM usage (reported as 2.0GiB). As the parent post highlights, even at 24 GiB, this graph ends up being problematically unreadable, with 2GiB being shown as 2/100. This could be meaningfully addressed by adding a 'Min/Max' option for bars, or allowing the use of formulas to compose the graphed quantity (e.g. 'graph ($GPU_VRAM_USED/24)*100). Or, no doubt, there are plenty of other approaches, but those two come to mind. Thank you for your help! VERSIONS (although this issue has existed on all versions of KDE I've tried this on) Operating System: Fedora Linux 38 and 37 KDE Plasma Version: 5.27.3 KDE Frameworks Version: 5.104.0 Qt Version: 5.15.8 Kernel Version: 6.2.8-300.fc38.x86_64 (64-bit) Graphics Platform: X11 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 465552] With multiple monitors plugged into multiple NVIDIA GPU's, one monitor is not enabled as expected
https://bugs.kde.org/show_bug.cgi?id=465552 Sam Uhrig changed: What|Removed |Added Status|NEEDSINFO |REPORTED Resolution|WAITINGFORINFO |--- -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 465552] With multiple monitors plugged into multiple NVIDIA GPU's, one monitor is not enabled as expected
https://bugs.kde.org/show_bug.cgi?id=465552 --- Comment #10 from Sam Uhrig --- (In reply to Nate Graham from comment #7) > Thanks. When all monitors are plugged in and enabled as expected, can you > attach a file with the output of `kscreen-console bug`? I have attached the file but downside is I will be moving away from this monitor configuration in favor of much larger monitors and less screens that hopefully KDE will support. Going to Dual 43 inches and removing 5 of the 7 monitors. So I will have 4 total which will be supported by one graphics card hopefully. I already have one of the 43's that is going up for testing so I won't have this much longer to determine if the bug is fixed. I had most of the monitors disabled is why I never finished out this report in favor of testing out the KDE Zones feature not sure what its called but is like MS Fancy Zones. I think this will allow me to use less monitors and go for larger monitors that will support my need. I am running arch and have all that latest updates installed. I noticed when I re-enabled all the monitors that the configuration of them was a breeze and feels like something improved a little more potentially. When ever I had did this in the past I would have a lot of flickering forever as each monitor was powered on and it would sometimes lock up. This felt more like what I would experience in Windows. -- You are receiving this mail because: You are watching all bug changes.
[konqueror] [Bug 468018] New: Konqueror Auto bug
https://bugs.kde.org/show_bug.cgi?id=468018 Bug ID: 468018 Summary: Konqueror Auto bug Classification: Applications Product: konqueror Version: 21.12.3 Platform: Kubuntu OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: konq-b...@kde.org Reporter: robli...@gmail.com Target Milestone: --- Application: konqueror (21.12.3) Qt Version: 5.15.6 Frameworks Version: 5.98.0 Operating System: Linux 5.19.0-38-generic x86_64 Windowing System: X11 Distribution: Ubuntu 22.10 DrKonqi: 5.25.5 [KCrashBackend] -- Information about the crash: Dr Konqi bug FoE game during a battle a freeze in game The reporter is unsure if this crash is reproducible. -- Backtrace: Application: Konqueror (konqueror), signal: Aborted [KCrash Handler] #4 __pthread_kill_implementation (no_tid=0, signo=6, threadid=) at ./nptl/pthread_kill.c:44 #5 __pthread_kill_internal (signo=6, threadid=) at ./nptl/pthread_kill.c:78 #6 __GI___pthread_kill (threadid=, signo=signo@entry=6) at ./nptl/pthread_kill.c:89 #7 0x7f4fae43bc46 in __GI_raise (sig=sig@entry=6) at ../sysdeps/posix/raise.c:26 #8 0x7f4fae4227fc in __GI_abort () at ./stdlib/abort.c:79 #9 0x7f4fa429e142 in ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so #10 0x7f4fa4f694d7 in ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so #11 0x7f4fa4513a6c in ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so #12 0x7f4f3b039d68 in ?? () from /lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #13 0x7f4f34df83f0 in ?? () #14 0x7f4ef80095a0 in ?? () #15 0x7f4f34df83e0 in ?? () #16 0x7f4f3b0399ee in ?? () from /lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #17 0x004000c9 in ?? () #18 0x00064df1 in ?? () #19 0x0002 in ?? () #20 0x7f4f008b06a0 in ?? () #21 0x7f4f34df85f0 in ?? () #22 0x7f4f34df83f0 in ?? () #23 0x7f4f34df85e0 in ?? () #24 0x7f4f3880d87e in ?? () from /lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #25 0x in ?? () Thread 23 (Thread 0x7f4f355fa6c0 (LWP 2997) "CompositorTileW"): #1 __futex_abstimed_wait_common (cancel=true, private=0, abstime=0x0, clockid=0, expected=0, futex_word=0x561c489aa4b8) at ./nptl/futex-internal.c:87 #2 __GI___futex_abstimed_wait_cancelable64 (futex_word=futex_word@entry=0x561c489aa4b8, expected=expected@entry=0, clockid=clockid@entry=0, abstime=abstime@entry=0x0, private=private@entry=0) at ./nptl/futex-internal.c:139 #3 0x7f4fae48f338 in __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x561c489aa3f8, cond=0x561c489aa490) at ./nptl/pthread_cond_wait.c:503 #4 ___pthread_cond_wait (cond=0x561c489aa490, mutex=0x561c489aa3f8) at ./nptl/pthread_cond_wait.c:627 #5 0x7f4f3ab0fe87 in ?? () from /lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #6 0x7f4f355f9be0 in ?? () #7 0x561c494c6508 in ?? () #8 0x561c48a7d110 in ?? () #9 0x7f4f30001cd0 in ?? () #10 0x in ?? () Thread 22 (Thread 0x7f4f44ffb6c0 (LWP 2991) "Chrome_IOThread"): #1 __GI___lll_lock_wait_private (futex=0x7f4fae5f8a00 <_IO_stdfile_2_lock>) at ./nptl/lowlevellock.c:34 #2 0x7f4fae462995 in buffered_vfprintf (s=0x7f4fae5f7680 <_IO_2_1_stderr_>, format=format@entry=0x7f4f4ee7dcdd "[%s] %s\n", args=args@entry=0x7f4f44ffa310, mode_flags=mode_flags@entry=2) at ./stdio-common/vfprintf-internal.c:1752 #3 0x7f4fae46165c in __vfprintf_internal (s=, format=0x7f4f4ee7dcdd "[%s] %s\n", ap=ap@entry=0x7f4f44ffa310, mode_flags=2) at ./stdio-common/vfprintf-internal.c:740 #4 0x7f4fae52ddc3 in ___fprintf_chk (fp=, flag=, format=) at ./debug/fprintf_chk.c:33 #5 0x7f4f4ee632be in event_logv_ () from /lib/x86_64-linux-gnu/libevent-2.1.so.7 #6 0x7f4f4ee63488 in event_warn () from /lib/x86_64-linux-gnu/libevent-2.1.so.7 #7 0x7f4f4ee6791c in ?? () from /lib/x86_64-linux-gnu/libevent-2.1.so.7 #8 0x7f4f4ee5f67d in event_base_loop () from /lib/x86_64-linux-gnu/libevent-2.1.so.7 #9 0x7f4f3ab218c0 in ?? () from /lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #10 0x00017f4f2430 in ?? () #11 0x7f4f44ffaa08 in ?? () #12 0x7f4f44ffaac0 in ?? () #13 0x01ce in ?? () #14 0x in ?? () Thread 21 (Thread 0x7f4f45ffd6c0 (LWP 2989) "ThreadPoolServi"): #1 __GI___libc_write (fd=2, buf=0x7f4f45ffa2f0, nbytes=39) at ../sysdeps/unix/sysv/linux/write.c:24 #2 0x7f4fae4868cd in _IO_new_file_write (f=0x7f4fae5f7680 <_IO_2_1_stderr_>, data=0x7f4f45ffa2f0, n=39) at ./libio/fileops.c:1180 #3 0x7f4fae4871b2 in new_do_write (to_do=, data=0x7f4f45ffa2f0 "[warn] epoll_wait: Bad file descriptor\n", fp=0x7f4fae5f7680 <_IO_2_1_stderr_>) at ./libio/libioP.h:947 #4 _IO_new_file_xsputn (n=39, data=, f=) at ./libio/fileops.c:1254 #5 _IO_new_file_xsputn (f=0x7f4fae5f7680 <_IO_2_1_stderr_>, data=, n=39) at
[kwin] [Bug 465552] With multiple monitors plugged into multiple NVIDIA GPU's, one monitor is not enabled as expected
https://bugs.kde.org/show_bug.cgi?id=465552 --- Comment #9 from Sam Uhrig --- Created attachment 157754 --> https://bugs.kde.org/attachment.cgi?id=157754=edit kscreen-console bug output -- You are receiving this mail because: You are watching all bug changes.
[frameworks-qqc2-desktop-style] [Bug 467390] Use of checkboxes for mutually exclusive menu items is very misleading
https://bugs.kde.org/show_bug.cgi?id=467390 ratijas changed: What|Removed |Added Latest Commit|https://invent.kde.org/fram |https://invent.kde.org/fram |eworks/qqc2-desktop-style/c |eworks/qqc2-desktop-style/c |ommit/9dadd05de66a135ea0c3c |ommit/7bff5123264ab1f312229 |66c6bb554ab22ec6a67 |4c95bd1fab40fb0a6d3 --- Comment #4 from ratijas --- Git commit 7bff5123264ab1f3122294c95bd1fab40fb0a6d3 by ivan tkachenko. Committed on 31/03/2023 at 22:59. Pushed by ratijas into branch 'kf5'. CheckIndicator: Allow exclusive buttons to be detected via their ButtonGroup This is a bit wasteful, as it creates a ButtonGroup attached object for every menu item that does not have it. But it works. Unfortunately, there is no better approach, as if ButtonGroup is bound to an item later than this binding is established, we won't know about it. All components using CheckIndicator, except MenuItem, were modified to override this new more advanced heuristic with a fixed elementType, so they don't waste memory on attached objects, and always have predictable appearance. See also: https://invent.kde.org/frameworks/kirigami/-/merge_requests/1014 M +1-0org.kde.desktop/CheckBox.qml M +1-0org.kde.desktop/CheckDelegate.qml M +6-1org.kde.desktop/CheckIndicator.qml M +1-0org.kde.desktop/RadioButton.qml M +1-0org.kde.desktop/RadioDelegate.qml A +135 -0tests/exclusive-menuitem.qml [License: GPL(v2.0+) LGPL(v3.0)] https://invent.kde.org/frameworks/qqc2-desktop-style/commit/7bff5123264ab1f3122294c95bd1fab40fb0a6d3 -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 466693] Discover checks for updates daily, regardless of the frequency set in the Software Sources dialog.
https://bugs.kde.org/show_bug.cgi?id=466693 --- Comment #6 from Paul Worrall --- I'm using the "kcm_updates" KCM to change the value of "Notification Frequency"; that setting isn't in the Software Sources section of Discover. The value I set is remembered between invocations, but it does not ask for a password or set "Apt::Periodic::Update-Package-Lists" and it does not seem to affect the frequency of update notifications. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-qqc2-desktop-style] [Bug 467390] Use of checkboxes for mutually exclusive menu items is very misleading
https://bugs.kde.org/show_bug.cgi?id=467390 ratijas changed: What|Removed |Added Latest Commit||https://invent.kde.org/fram ||eworks/qqc2-desktop-style/c ||ommit/9dadd05de66a135ea0c3c ||66c6bb554ab22ec6a67 Resolution|--- |FIXED Status|CONFIRMED |RESOLVED --- Comment #3 from ratijas --- Git commit 9dadd05de66a135ea0c3c66c6bb554ab22ec6a67 by ivan tkachenko. Committed on 31/03/2023 at 22:56. Pushed by ratijas into branch 'master'. CheckIndicator: Allow exclusive buttons to be detected via their ButtonGroup This is a bit wasteful, as it creates a ButtonGroup attached object for every menu item that does not have it. But it works. Unfortunately, there is no better approach, as if ButtonGroup is bound to an item later than this binding is established, we won't know about it. All components using CheckIndicator, except MenuItem, were modified to override this new more advanced heuristic with a fixed elementType, so they don't waste memory on attached objects, and always have predictable appearance. See also: https://invent.kde.org/frameworks/kirigami/-/merge_requests/1014 M +1-0org.kde.desktop/CheckBox.qml M +1-0org.kde.desktop/CheckDelegate.qml M +6-1org.kde.desktop/CheckIndicator.qml M +1-0org.kde.desktop/RadioButton.qml M +1-0org.kde.desktop/RadioDelegate.qml A +135 -0tests/exclusive-menuitem.qml [License: GPL(v2.0+) LGPL(v3.0)] https://invent.kde.org/frameworks/qqc2-desktop-style/commit/9dadd05de66a135ea0c3c66c6bb554ab22ec6a67 -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 468017] New: Percentage value not localised
https://bugs.kde.org/show_bug.cgi?id=468017 Bug ID: 468017 Summary: Percentage value not localised Classification: Applications Product: okular Version: 23.03.90 Platform: Other OS: Other Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: okular-de...@kde.org Reporter: emir_s...@icloud.com Target Milestone: --- Created attachment 157753 --> https://bugs.kde.org/attachment.cgi?id=157753=edit screenshot See screenshot. The QSpinbox in the Settings view is not localisable. There is a recent helper Lukas Sommer has kindly provided[1], it might be helpful for fixing this. [1]: https://invent.kde.org/libraries/perceptualcolor/-/snippets/2565 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 468016] New: Caption information is written to Exif UserComment and no option exists to disable
https://bugs.kde.org/show_bug.cgi?id=468016 Bug ID: 468016 Summary: Caption information is written to Exif UserComment and no option exists to disable Classification: Applications Product: digikam Version: 8.0.0 Platform: Other OS: Other Status: REPORTED Severity: normal Priority: NOR Component: Metadata-Exif Assignee: digikam-bugs-n...@kde.org Reporter: jose_oli...@hotmail.com Target Milestone: --- SUMMARY *** Caption information is written to Exif UserComment and no option exists to disable *** STEPS TO REPRODUCE 1. Type text in Caption field. 2. Go to Configure Digikam Settings->Metadada->Advanced tab OBSERVED RESULT - No option for Exif.UserComment is displayed. - Metadata is written to Exif.UserComment - Can be confimed using exiftool -UserComment command. EXPECTED RESULT - Do not write to exif.UserComment unless enabled in Advanced Metadata options. SOFTWARE/OS VERSIONS Windows 11 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 467892] Percentage formatting error in Energy Info KCM
https://bugs.kde.org/show_bug.cgi?id=467892
--- Comment #1 from Emir SARI ---
So, these are the strings in KInfoCenter:
{label: i18n("Current charge:"), value: "chargePercent", unit: i18n("%"),
precision: 0},
{label: i18n("Health"), value: "capacity", unit: i18n("%"), precision: 0},
Is this within a special structure? Why it has to be labeled like this instead
of a standard `Label {}`? Where do "chargePercent" and "capacity" keys come
from?
yunits: root.historyType == HistoryModel.RateType ? i18nc("Shorthand for
Watts","W") : i18nc("literal percent sign", "%")
Is this string displayed anywhere in the UI?
--
You are receiving this mail because:
You are watching all bug changes.
[kdeconnect] [Bug 468015] New: Ability to create run commands using kdeconnect-cli
https://bugs.kde.org/show_bug.cgi?id=468015 Bug ID: 468015 Summary: Ability to create run commands using kdeconnect-cli Classification: Applications Product: kdeconnect Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: common Assignee: albertv...@gmail.com Reporter: jason.na...@protonmail.com CC: andrew.g.r.hol...@gmail.com Target Milestone: --- Currently run commands can only be added via GUI, however in some situations it would be helpful if this could be done via CLI: kdeconnect-cli --device 644ccf7fd6f3678d --add-command 'mycommandhere' Side note Have talked to devs on IRC about this a couple of years ago and one had this on their todo list - cannot remember who it was though -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 419870] Feature: Sharing remote commands between multiple links
https://bugs.kde.org/show_bug.cgi?id=419870 jason.na...@protonmail.com changed: What|Removed |Added CC||jason.na...@protonmail.com -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 467322] LSP: show regular tooltip alongside error/warning
https://bugs.kde.org/show_bug.cgi?id=467322 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/utilities/kate/-/merge_requests/1176 -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 468014] New: USB microphone (Papu . Pine) is not recognized.
https://bugs.kde.org/show_bug.cgi?id=468014 Bug ID: 468014 Summary: USB microphone (Papu . Pine) is not recognized. Classification: Applications Product: kdenlive Version: 22.12.3 Platform: Ubuntu OS: Linux Status: REPORTED Severity: critical Priority: NOR Component: Effects & Transitions Assignee: j...@kdenlive.org Reporter: iyagi...@gmail.com Target Milestone: --- Created attachment 157752 --> https://bugs.kde.org/attachment.cgi?id=157752=edit I am using a usb microphone (Papu . Pine) SUMMARY *** NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** STEPS TO REPRODUCE 1. I am using a usb microphone (Papu . Pine) the mic works fine Kdenlive doesn't recognize it. Linux/KDE Plasma: ubuntu 22.10 -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 435671] Zoom icons do not use magnifying glass iconography
https://bugs.kde.org/show_bug.cgi?id=435671 --- Comment #20 from Philip Murray --- Numbers provided for easy referencing. Some of the width/height ones with bigger arrows don't work well for the "fit-best" one that usually goes with them. -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 435671] Zoom icons do not use magnifying glass iconography
https://bugs.kde.org/show_bug.cgi?id=435671 --- Comment #19 from Philip Murray --- Created attachment 157751 --> https://bugs.kde.org/attachment.cgi?id=157751=edit Pix attached of some versions that hopefully work decently at 16 & 22px sizes. -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 452669] Slideshow controls do not work on Wayland
https://bugs.kde.org/show_bug.cgi?id=452669 Christian Hartmann changed: What|Removed |Added CC||chris-hartm...@gmx.de -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 467387] Percentage value not localisable
https://bugs.kde.org/show_bug.cgi?id=467387 --- Comment #1 from Emir SARI --- This might help: https://invent.kde.org/libraries/perceptualcolor/-/snippets/2565 -- You are receiving this mail because: You are watching all bug changes.
[ktouch] [Bug 467856] Percentage formatting error
https://bugs.kde.org/show_bug.cgi?id=467856 --- Comment #3 from Emir SARI --- This might help with the spin boxes: https://invent.kde.org/libraries/perceptualcolor/-/snippets/2565 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-ktexteditor] [Bug 467934] Percentage value not localisable
https://bugs.kde.org/show_bug.cgi?id=467934 --- Comment #3 from Emir SARI --- This might help: https://invent.kde.org/libraries/perceptualcolor/-/snippets/2565 -- You are receiving this mail because: You are watching all bug changes.
[kolourpaint] [Bug 467944] Percentage value not localisable
https://bugs.kde.org/show_bug.cgi?id=467944 --- Comment #1 from Emir SARI --- This might help: https://invent.kde.org/libraries/perceptualcolor/-/snippets/2565 -- You are receiving this mail because: You are watching all bug changes.
[plasma-pa] [Bug 468013] New: OSD display does display localised percent value for Turkish
https://bugs.kde.org/show_bug.cgi?id=468013 Bug ID: 468013 Summary: OSD display does display localised percent value for Turkish Classification: Plasma Product: plasma-pa Version: master Platform: Other OS: Other Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: emir_s...@icloud.com CC: isma...@gmail.com, m...@ratijas.tk, now...@gmail.com Target Milestone: --- Created attachment 157750 --> https://bugs.kde.org/attachment.cgi?id=157750=edit screenshot See screenshot. In Turkish, the correct percent formatting is %36, as seen in the volume tray applet. However, the OSD still displays the standard format, which is 36%. Both strings are translated for some time. Code for the percentage value is here: https://invent.kde.org/plasma/plasma-workspace/-/blob/master/lookandfeel/org.kde.breeze/contents/osd/OsdItem.qml#L80 Plasma 5.27.3, tr_TR locale. -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 468010] symbol lookup error in kibkmm_csvimportercore.so.5
https://bugs.kde.org/show_bug.cgi?id=468010 Jack changed: What|Removed |Added CC|ostroffjh@users.sourceforge | |.net| --- Comment #3 from Jack --- It's a compile/link issue, not something in the code, so I don't see anything KMyMoney or KDE can do about it. It's OK to leave this bug open for now, while you see what Arch says, and it would be worth posting a link here to their bug once you file it. In the past, I've mostly seen this type of issue on Windows, any my faulty memory says it's related to mismatched versions of dependencies, but take that with a grain of salt for now. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 468012] canot use discover
https://bugs.kde.org/show_bug.cgi?id=468012 Bug Janitor Service changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |DOWNSTREAM --- Comment #1 from Bug Janitor Service --- Thank you for the bug report! However Plasma 5.20.5 is no longer eligible for support or maintenance from KDE; supported versions are 5.27, and 5.27 or newer. Please upgrade to a supported version as soon as your distribution makes it available to you. Plasma is a fast-moving project, and bugs in one version are often fixed in the next one. If you need support for Plasma 5.20.5, please contact your distribution, who bears the responsibility of providing support for older releases that are no longer supported by KDE. If you can reproduce the issue after upgrading to a supported version, feel free to re-open this bug report. -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 468010] symbol lookup error in kibkmm_csvimportercore.so.5
https://bugs.kde.org/show_bug.cgi?id=468010 --- Comment #2 from Clinton --- (In reply to Jack from comment #1) > First, you mention Manjaro, but the link is for ArchLinux. Is that correct? > I can imagine possible issues using an Arch package on Manjaro if any > dependent packages have been compiled differently between the two systems. > My memories of issues with symbols beginning with _Z are all Windows > related, but in any case related to compiling/linking. > I would suggest reporting to a Manjaro forum or mailing list. Thanks for the quick reply. I just downloaded the package from the ArchLinux page listed, and compared it to the package downloaded from the Manjaro community repository and confirmed that they share the same md5sum. i.e.: https://archlinux.org/packages/community/x86_64/kmymoney/download/ https://osmirror.org/manjaro/stable/community/x86_64/kmymoney-5.1.3-4-x86_64.pkg.tar.zst Both of which have md5sum: 49ed9b60dc03ef5d05d2d59bff0b57bb So in this instance, ArchLinux is the correct downstream forum for addressing bugs, even though their packages are being reused by Manjaro. Manjaro doesn't even have a bugtracker for this or most other packages, for instance. As to whether this is an upstream issue to be addressed here on the KDE bug tracker, or downstream with Arch, I am uncertain. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 468012] New: canot use discover
https://bugs.kde.org/show_bug.cgi?id=468012 Bug ID: 468012 Summary: canot use discover Classification: Applications Product: Discover Version: 5.20.5 Platform: Other OS: Linux Status: REPORTED Severity: major Priority: NOR Component: discover Assignee: plasma-b...@kde.org Reporter: jat...@duck.com CC: aleix...@kde.org Target Milestone: --- Created attachment 157749 --> https://bugs.kde.org/attachment.cgi?id=157749=edit two screenshot with th bugs SUMMARY *** NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** STEPS TO REPRODUCE 1. Im using a kde pureos distro in a non purism laptop and I canto install any software using a discover 5.20.5, receving a message tha I dont have authorization to execute this operation. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: PureOS (available in About System) KDE Plasma Version: konsole 20.12.3 KDE Frameworks Version: 5.78.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 394016] Upper case file types are not overwritten, instead a lower case version is created
https://bugs.kde.org/show_bug.cgi?id=394016 --- Comment #7 from Maik Qualmann --- Well, this bug report is not closed yet, which means that such an option doesn't exist yet. It was just an "idea" of mine in Comment 3. Maik -- You are receiving this mail because: You are watching all bug changes.
[ghostwriter] [Bug 468011] Request: Allow using custom directory to save drafts
https://bugs.kde.org/show_bug.cgi?id=468011 Cassandra Granade changed: What|Removed |Added CC||kde.tu...@simplelogin.com -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 468010] symbol lookup error in kibkmm_csvimportercore.so.5
https://bugs.kde.org/show_bug.cgi?id=468010 Jack changed: What|Removed |Added CC||ostroffjh@users.sourceforge ||.net --- Comment #1 from Jack --- First, you mention Manjaro, but the link is for ArchLinux. Is that correct? I can imagine possible issues using an Arch package on Manjaro if any dependent packages have been compiled differently between the two systems. My memories of issues with symbols beginning with _Z are all Windows related, but in any case related to compiling/linking. I would suggest reporting to a Manjaro forum or mailing list. -- You are receiving this mail because: You are watching all bug changes.
[ghostwriter] [Bug 468011] New: Request: Allow using custom directory to save drafts
https://bugs.kde.org/show_bug.cgi?id=468011 Bug ID: 468011 Summary: Request: Allow using custom directory to save drafts Classification: Applications Product: ghostwriter Version: unspecified Platform: Other OS: Other Status: REPORTED Severity: wishlist Priority: NOR Component: general Assignee: megan.con...@kdemail.net Reporter: kde.tu...@simplelogin.com Target Milestone: --- Currently, Ghostwriter appears to save untitled drafts into `~/Documents`, but for reliability it would be nice to be able to save untitled drafts into a folder that's backed up by cloud sync providers. While I can achieve this on Linux using a symlink for `~/Documents`, it would be quite convenient to be able to set a preference as to where to store untitled drafts. This is similar to https://bugs.kde.org/show_bug.cgi?id=460352, but with a customizable location instead of hard-coded to `~/.cache/ghostwriter/drafts`. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 468002] UTF8 Encoding is not supported in IPTC when using exiftool as backend.
https://bugs.kde.org/show_bug.cgi?id=468002 Maik Qualmann changed: What|Removed |Added Status|REPORTED|RESOLVED Version Fixed In||8.0.0 Resolution|--- |FIXED Latest Commit||https://invent.kde.org/grap ||hics/digikam/commit/f7247f8 ||6ce9d6d33052b7b535caeba08f9 ||8e8509 --- Comment #1 from Maik Qualmann --- Git commit f7247f86ce9d6d33052b7b535caeba08f98e8509 by Maik Qualmann. Committed on 31/03/2023 at 19:13. Pushed by mqualmann into branch 'master'. write iptc coded characterset tag with ExifTool FIXED-IN: 8.0.0 M +1-1NEWS M +2-2core/libs/metadataengine/engine/metaengine_p.cpp M +3-1core/libs/metadataengine/exiftool/exiftoolparser.h M +6-1core/libs/metadataengine/exiftool/exiftoolparser_command.cpp https://invent.kde.org/graphics/digikam/commit/f7247f86ce9d6d33052b7b535caeba08f98e8509 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 466209] Tab key only switches between file view and location bar in a loop once the file view gains focus
https://bugs.kde.org/show_bug.cgi?id=466209 --- Comment #3 from Nate Graham --- Working on this. I can also reproduce that if I hit Shift+Tab while the file view has focus, focus passes to the Cancel button. But indeed, using just the Tab key gets focus stuck in the file view itself. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 459081] Charge Limit section disappears upon changing the settings
https://bugs.kde.org/show_bug.cgi?id=459081 --- Comment #3 from b...@whitleymott.net --- Ran tumbleweed updates on my thinkpad 2023-03-22, systemsettings5 updated to 5.27.3-1.2. Happened to look at the Advanced Power Settings yesterday, the Charge Limit section stayed displayed! And my battery was all charged up to 100%, so apparently at some point since my last comment above, it started behaving like i'd never changed the settings. So i re-entered similar settings, this time stop charging at 67% and start at 33%. And now as usual again, when i revisit Advanced Power Settings, the Charge Limit section disappears in a flash. Today the battery's charge has sagged down to 96% so i expect like before my Charge Limit settings will be honored even tho not displayed. No idea why they'd gotten forgotten in the meantime tho, perhaps something to do with package updates. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 467666] reshade-shaders-git picked up as a false update in discover but won't update.
https://bugs.kde.org/show_bug.cgi?id=467666 --- Comment #2 from Dominic --- (In reply to Aleix Pol from comment #1) > This is a known problem in ArchLinux's PackageKit backend: > https://github.com/PackageKit/PackageKit/issues/533 Thanks for the clarification, happy to see it's already been reported -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 468010] New: symbol lookup error in kibkmm_csvimportercore.so.5
https://bugs.kde.org/show_bug.cgi?id=468010 Bug ID: 468010 Summary: symbol lookup error in kibkmm_csvimportercore.so.5 Classification: Applications Product: kmymoney Version: 5.1.3 Platform: Manjaro OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: importer Assignee: kmymoney-de...@kde.org Reporter: clintontheg...@gmail.com Target Milestone: --- I've installed kmymoney in Manjaro from the community repo. https://archlinux.org/packages/community/x86_64/kmymoney/ Install goes fine, all dependencies are met. However I get the console error: kmymoney: symbol lookup error: /usr/lib/libkmm_csvimportercore.so.5: undefined symbol: _ZNK14MyMoneyAccount10currencyIdEv and then KMyMoney quits. STEPS TO REPRODUCE 1. From an amd64 Manjaro installation, with KDE SC, install the kmymoney from the community repo. 2. Try to start it. OBSERVED RESULT It doesn't start. Operating System: Manjaro Linux KDE Plasma Version: 5.27.3 KDE Frameworks Version: 5.104.0 Qt Version: 5.15.8 Kernel Version: 5.15.104-2-MANJARO (64-bit) Graphics Platform: X11 Processors: 16 × Intel® Core™ i7-10700KF CPU @ 3.80GHz Memory: 31.2 GiB of RAM Graphics Processor: NVIDIA GeForce GTX 1650/PCIe/SSE2 Manufacturer: ASUS -- You are receiving this mail because: You are watching all bug changes.
[LabPlot2] [Bug 456328] Labplot 2.9 does not run
https://bugs.kde.org/show_bug.cgi?id=456328 --- Comment #8 from Alexander Semke --- (In reply to Peter from comment #7) > In deep, I have a Dell notebook, with Dell Optimizer running in the > background. However, even with the optimizer running in the background, I > can execute the old pre-2.9.0-official release version. I have a > labplot2.exe dated 2021-12-20. This LabPlot comes up and runs rather > instantaneously. With this in mind: is a background task responsible for > labplot2 2.9 and newer not firing up? The only thing that comes to mind mind now is the loading of plugins for the Notebook in Labplot (for Maxima, python, etc.). There were some changes in the location of plugins and probably also in their number, but I don't remember the details anymore. > However, I will test version 2.10 again, then without the Dell background > manager working in the background. I will inform you again. Yes, please try it out without all that stuff running in the background and let us know. Thank you. -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 467483] Blur effect is applied to only top left quarter of SDDM screen
https://bugs.kde.org/show_bug.cgi?id=467483 medin changed: What|Removed |Added Version|5.26.90 |5.27.3 -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 465897] Potential problem in passing AppData translations to appstream-data
https://bugs.kde.org/show_bug.cgi?id=465897 Bug Janitor Service changed: What|Removed |Added Status|REPORTED|ASSIGNED Ever confirmed|0 |1 --- Comment #19 from Bug Janitor Service --- A possibly relevant merge request was started @ https://invent.kde.org/sysadmin/l10n-scripty/-/merge_requests/61 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 468009] panel size saved in absolute terms, this makes maximized panels less portable to other screen size
https://bugs.kde.org/show_bug.cgi?id=468009 --- Comment #1 from PK --- In this first attachment there is the "diff" file of two org.kde.plasma.desktop-layout.js-files of the same global theme-with-maximized-panel, applied to two machines with different screen properties and saved on each machine as global theme. This diff-file is best opened with kde-kompare. In my eyes it would make the theme much more portable when it didn't read: "maximumLength": 67.5, -"minimumLength": 67.5, +"maximumLength": 56.25, +"minimumLength": 56.25, but something like: "maximumLength": maximum -"minimumLength": maximum +"maximumLength": maximum +"minimumLength": maximum -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 467483] Blur effect is applied to only top left quarter of SDDM screen
https://bugs.kde.org/show_bug.cgi?id=467483 --- Comment #2 from medin --- This also happens after upgrading to : Operating System: Manjaro Linux KDE Plasma Version: 5.27.3 KDE Frameworks Version: 5.104.0 Qt Version: 5.15.8 Kernel Version: 6.1.21-1-MANJARO (64-bit) Graphics Platform: X11 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 468009] New: panel size saved in absolute terms, this makes maximized panels less portable to other screen size
https://bugs.kde.org/show_bug.cgi?id=468009 Bug ID: 468009 Summary: panel size saved in absolute terms, this makes maximized panels less portable to other screen size Classification: Plasma Product: plasmashell Version: 5.27.3 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Global Theme packages Assignee: plasma-b...@kde.org Reporter: pieterkristen...@gmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 Created attachment 157748 --> https://bugs.kde.org/attachment.cgi?id=157748=edit diff of two org.kde.plasma.desktop-layout.js files of the same theme applied to machines with different screens. SUMMARY *** In a self-made global theme there is a maximized panel (full screen width or full screen heidth). When I use this global theme on a computer with other screen specifications the maximized panel is rendered wrong (too long/too short) *** STEPS TO REPRODUCE 1. create global theme with the look-and-feel explorer 2. apply the theme to a machine with other screen properties OBSERVED RESULT maximized panel too small or too wide EXPECTED RESULT maximized panel is also just from side to side and fits. SOFTWARE/OS VERSIONS Operating System: KDE neon 5.27 KDE Plasma Version: 5.27.3 KDE Frameworks Version: 5.104.0 Qt Version: 5.15.8 Kernel Version: 5.19.0-35-generic (64-bit) Graphics Platform: Wayland Processors: 4 × Intel® Celeron® J4105 CPU @ 1.50GHz Memory: 7.4 GiB of RAM Graphics Processor: Mesa Intel® UHD Graphics 600 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 465897] Potential problem in passing AppData translations to appstream-data
https://bugs.kde.org/show_bug.cgi?id=465897 --- Comment #18 from Aleix Pol --- Thank you very much for such a thorough bug report! I think I've found the problem. The xml:lang field is getting generated as "zh-CN" instead of "zh_CN". I'll see if I can find where this is generated. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 467951] Folder View not working
https://bugs.kde.org/show_bug.cgi?id=467951 --- Comment #4 from Valerio Galdo --- Created attachment 157747 --> https://bugs.kde.org/attachment.cgi?id=157747=edit thi is a new video -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 453877] If fingerprint authentication is enabled, unable to unlock screen with password until after 3 failed fingerprint auth attempts
https://bugs.kde.org/show_bug.cgi?id=453877 Éric Brunet changed: What|Removed |Added CC||eric.bru...@lps.ens.fr --- Comment #2 from Éric Brunet --- I have the same issue on a fedora 38 beta. After failing three times the fingerprint, I can indeed type my password to unlock It works the other way around: I can type my password, hit enter (nothing happens), and then fail three times the fingerprint; the computer unlocks. The problem might not be on kde side, as it is also present with other programs. For instance, if I use sudo, I need to fail three times the fingerprint before being offered a keyboard prompt. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 467951] Folder View not working
https://bugs.kde.org/show_bug.cgi?id=467951 --- Comment #3 from Valerio Galdo --- (In reply to veggero from comment #1) > Hi! Could you provide some screenshots/recordings of this? Hi i made a video but it doesn't work -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 467951] Folder View not working
https://bugs.kde.org/show_bug.cgi?id=467951 --- Comment #2 from Valerio Galdo --- Created attachment 157746 --> https://bugs.kde.org/attachment.cgi?id=157746=edit i created a new folder in dolphin but i can't see it in the folder view this also happens with a fresh install of kde neon -- You are receiving this mail because: You are watching all bug changes.
[NeoChat] [Bug 467512] Room information sidebar isn't scrollable
https://bugs.kde.org/show_bug.cgi?id=467512 Bug Janitor Service changed: What|Removed |Added Status|CONFIRMED |ASSIGNED --- Comment #1 from Bug Janitor Service --- A possibly relevant merge request was started @ https://invent.kde.org/network/neochat/-/merge_requests/866 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kimageformats] [Bug 466821] Digikam git can't manage 16 bit float .xcf
https://bugs.kde.org/show_bug.cgi?id=466821 --- Comment #8 from Mirco Miranda --- (In reply to maderios from comment #7) > I see KImageFormats works fine with .psd proprietary Adobe format. Nobody has it with GIMP. The PSD plugin works well because I work in large format digital printing and everyone uses Photoshop. I maintain two PSD readers: the one for the company I work for (it's not a qt plugin) and the KDE Qt plugin (for fun). I would also like to fix the XCF plugin but no promises. For now, I've only looked at the specs. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 459207] Discover less usable while fetching updates after being launched
https://bugs.kde.org/show_bug.cgi?id=459207 --- Comment #2 from Aleix Pol --- It should work fine, maybe it's a better thing to fix. What do you mean exactly by "less usable"? Can you maybe check if it's flatpak or dnf slowing it down? You can do it by running "plasma-discover --backends packagekit" and "plasma-discover --backends flatpak" respectively. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 422996] Digikam Crash with GMicQt plugin on Mac Mojave
https://bugs.kde.org/show_bug.cgi?id=422996 --- Comment #55 from caulier.gil...@gmail.com --- Great. I will update the digiKam when new release will be available Gilles -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 422996] Digikam Crash with GMicQt plugin on Mac Mojave
https://bugs.kde.org/show_bug.cgi?id=422996 --- Comment #54 from David Tschumperlé --- Gilles, we finally found the bug in G'MIC 3.2.2. It should be fixed with this commit: https://github.com/GreycLab/gmic/commit/617c3ee986f42f3fce67e173b3e5f3e8f4e5fcd4 We'll try to release 3.2.3 next week, with a few improvements over the bugfix. -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 468007] Opening emacs launcher new application instance instead of replacing launcher icon
https://bugs.kde.org/show_bug.cgi?id=468007 --- Comment #2 from t.soer...@gmail.com --- *** Bug 468008 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 468008] Opening emacs launcher new application instance instead of replacing launcher icon
https://bugs.kde.org/show_bug.cgi?id=468008 t.soer...@gmail.com changed: What|Removed |Added Resolution|--- |DUPLICATE Status|REPORTED|RESOLVED --- Comment #1 from t.soer...@gmail.com --- *** This bug has been marked as a duplicate of bug 468007 *** -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 468008] Opening emacs launcher new application instance instead of replacing launcher icon
https://bugs.kde.org/show_bug.cgi?id=468008 t.soer...@gmail.com changed: What|Removed |Added Resolution|--- |DUPLICATE Status|REPORTED|RESOLVED --- Comment #1 from t.soer...@gmail.com --- *** This bug has been marked as a duplicate of bug 468007 *** -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 468007] Opening emacs launcher new application instance instead of replacing launcher icon
https://bugs.kde.org/show_bug.cgi?id=468007 --- Comment #1 from t.soer...@gmail.com --- When I open emacs (icon #3 on the taskbar in the picture below) it opens a new instance (icon #5 on the taskbar), instead of the launcher icon turning into the application instance https://i.imgur.com/E1RbdGK.png -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 468008] New: Opening emacs launcher new application instance instead of replacing launcher icon
https://bugs.kde.org/show_bug.cgi?id=468008 Bug ID: 468008 Summary: Opening emacs launcher new application instance instead of replacing launcher icon Classification: I don't know Product: kde Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: t.soer...@gmail.com Target Milestone: --- SUMMARY When I open emacs (icon #3) it opens a new instance (icon #5 on the taskbar), instead of the launcher icon turning into the application instance https://i.imgur.com/E1RbdGK.png STEPS TO REPRODUCE 1. 2. 3. OBSERVED RESULT EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: Fedora 37 (available in About System) KDE Plasma Version: 5.27.3 KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 468007] New: Opening emacs launcher new application instance instead of replacing launcher icon
https://bugs.kde.org/show_bug.cgi?id=468007 Bug ID: 468007 Summary: Opening emacs launcher new application instance instead of replacing launcher icon Classification: I don't know Product: kde Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: t.soer...@gmail.com Target Milestone: --- SUMMARY When I open emacs (icon #3) it opens a new instance (icon #5 on the taskbar), instead of the launcher icon turning into the application instance https://i.imgur.com/E1RbdGK.png STEPS TO REPRODUCE 1. 2. 3. OBSERVED RESULT EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: Fedora 37 (available in About System) KDE Plasma Version: 5.27.3 KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 468006] New: Bad icon for "media-flash"
https://bugs.kde.org/show_bug.cgi?id=468006 Bug ID: 468006 Summary: Bad icon for "media-flash" Classification: Plasma Product: Breeze Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Icons Assignee: visual-des...@kde.org Reporter: stefan.bru...@rwth-aachen.de CC: kain...@gmail.com, m...@nueljl.in Target Milestone: --- Created attachment 157745 --> https://bugs.kde.org/attachment.cgi?id=157745=edit media-flash-* icon from various themes The "media-flash" icon resembles a DIMM memory bar, not a typical flash type media card. See the attachment for various icon themes, left to right: HighContrast; Adwaita:symbolic; Adwaita; Breeze:media-flash-sd-mmc; Breeze:media-flash -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 467870] Desktop layout reverts to folder view
https://bugs.kde.org/show_bug.cgi?id=467870 --- Comment #3 from Alberto Salvia Novella --- No idea, as it doesn't seem to happen consistently. I have just asked the variety developers. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 468005] New: Dual color picker partly affected by OCIO exposure when OCIO turned off
https://bugs.kde.org/show_bug.cgi?id=468005 Bug ID: 468005 Summary: Dual color picker partly affected by OCIO exposure when OCIO turned off Classification: Applications Product: krita Version: nightly build (please specify the git hash!) Platform: Appimage OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Color Selectors Assignee: krita-bugs-n...@kde.org Reporter: erji...@alumni.iu.edu Target Milestone: --- SUMMARY The dual color picker behaves strangely when OCIO is turned on and the exposure setting is adjusted. STEPS TO REPRODUCE 1. Open new linear floating-point document. 2. Open LUT Management docker. 3. Enable Use OpenColorIO 4. Set Color Engine to OCIO 5. Set Exposure to -6.64 6. Disable Use OpenColorIO 7. Double-click on the top-left color swatch in the dual color picker. 8. Select the bottom-left of the color triangle. 9. Close dialog and double-clicik on bottom-right color swatch in the dual color picker. 10. Select the bottom-left of the color triangle. OBSERVED RESULT Top-left swatch color picker goes up to RGB(99.73, 99.73, 99.73) even though OCIO disabled and Exposure field is disabled. Bottom-right swatch color picker goes up to RGB(65535, 65535, 65535) even though the document is floating-point. EXPECTED RESULT Color picker should not have confusing, arbitrary maximum based on Exposure when OCIO is turned off. The color pickers for each of the two swatches should behave the same and have floating-point values. SOFTWARE/OS VERSIONS Using krita-5.2.0-prealpha-8550960a23-x86_64.appimage -- You are receiving this mail because: You are watching all bug changes.
[kio-extras] [Bug 325574] Unable to modify file on Android device using kio-mtp
https://bugs.kde.org/show_bug.cgi?id=325574 Nate Graham changed: What|Removed |Added Summary|Unable to modifying file on |Unable to modify file on |Android device using|Android device using |kio-mtp |kio-mtp -- You are receiving this mail because: You are watching all bug changes.
