[kstars] [Bug 404696] Ekos button "Center Telescope Ready"
https://bugs.kde.org/show_bug.cgi?id=404696 Jasem Mutlaq changed: What|Removed |Added Status|NEEDSINFO |CONFIRMED Resolution|WAITINGFORINFO |--- --- Comment #3 from Jasem Mutlaq --- Right, it appears the object info is not updated after the rotation. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 442400] Ambiguous Shortcuts on Ctrl+Alt+I
https://bugs.kde.org/show_bug.cgi?id=442400 --- Comment #2 from Maik Qualmann --- https://bugs.kde.org/show_bug.cgi?id=439490#c2 Maik -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 438878] Ambiguous Shortcut window on startup
https://bugs.kde.org/show_bug.cgi?id=438878 Maik Qualmann changed: What|Removed |Added CC||j...@pearson.onl --- Comment #14 from Maik Qualmann --- *** Bug 442400 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 442400] Ambiguous Shortcuts on Ctrl+Alt+I
https://bugs.kde.org/show_bug.cgi?id=442400 Maik Qualmann changed: What|Removed |Added Resolution|--- |DUPLICATE CC||metzping...@gmail.com Status|REPORTED|RESOLVED --- Comment #1 from Maik Qualmann --- *** This bug has been marked as a duplicate of bug 438878 *** -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 442404] Launching Discover from the Notifier on Wayland shows both desktop and mobile controls in on the Updates page
https://bugs.kde.org/show_bug.cgi?id=442404 Nate Graham changed: What|Removed |Added Keywords||regression -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 442086] Volume bar on obs breaks after raising maximum volume
https://bugs.kde.org/show_bug.cgi?id=442086 --- Comment #2 from Namor Niradnug --- (In reply to Nate Graham from comment #1) > > plasma-workspace/shell/obs.cpp > I don't see this file; can you point to where you found it? here is GitLab link: https://invent.kde.org/plasma/plasma-workspace/blob/master/shell/osd.cpp#L43 -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 440867] kdenlive 21.08.0 (packager tars) fails to build with new glibc 2.34
https://bugs.kde.org/show_bug.cgi?id=440867 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.
[lattedock] [Bug 438968] Latte dock crashed upon startup
https://bugs.kde.org/show_bug.cgi?id=438968 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.
[lattedock] [Bug 439928] Spontaneous Latte Dock crash
https://bugs.kde.org/show_bug.cgi?id=439928 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.
[krdc] [Bug 441630] I can't open the KRDC app
https://bugs.kde.org/show_bug.cgi?id=441630 --- 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 441380] "Edit > Compare Folders" does nothing
https://bugs.kde.org/show_bug.cgi?id=441380 --- Comment #5 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 442328] Find ffmpeg automatically from PATH
https://bugs.kde.org/show_bug.cgi?id=442328 healer.ha...@gmail.com changed: What|Removed |Added Resolution|--- |FIXED Status|REPORTED|RESOLVED --- Comment #6 from healer.ha...@gmail.com --- I download the Windows setup from build 1236 (https://binary-factory.kde.org/job/Krita_Stable_Windows_Build/1236/). Krita now automatically finds ffmpeg from PATH. I restarted my computer (once), but the problem doesn't persist anymore. Thanks. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 442397] Regression: Dockers with utility titlebar no longer have reasonable size policy.
https://bugs.kde.org/show_bug.cgi?id=442397 --- Comment #2 from Eoin O'Neill --- Created attachment 141535 --> https://bugs.kde.org/attachment.cgi?id=141535=edit Screenshot of problem Here's a screen-capture of the problem. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 442413] KDE doesn't respect the ~/.config/mimeapps.list defaults
https://bugs.kde.org/show_bug.cgi?id=442413 --- Comment #2 from 61kyl...@anonaddy.me --- Ops, the blockquote got messed up. >The root of the problem is: KDE does not initialize the XDG file associations >file ~/.config/mimeapps.list with its defaults. Instead KDE relies on its own >launch executable. Since Thunderbird / GTK apps parse that file to get >defaults it shows a random app that supports opening PDF files. > >A quick workaround to solve this is forcing KDE to generate the entry for PDF >files. You can do that by changing file association order to something >different than the default applying it and then turning the ordering back to >Okular-first in System Settings -> File Associations. > >It is an oddity left from KDE4 days. It allows people to try out KDE without >ruining GTK based desktop file associations but causes problems like this when >GTK apps are used under KDE desktop. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 442413] KDE doesn't respect the ~/.config/mimeapps.list defaults
https://bugs.kde.org/show_bug.cgi?id=442413 --- Comment #1 from 61kyl...@anonaddy.me --- Created attachment 141534 --> https://bugs.kde.org/attachment.cgi?id=141534=edit PDFs opening in GIMP, despite Okular being the preferred app PDFs opening in GIMP, despite Okular being the preferred app according with the following comment: https://bugzilla.mozilla.org/show_bug.cgi?id=1713541#c11 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 442413] New: KDE doesn't respect the ~/.config/mimeapps.list defaults
https://bugs.kde.org/show_bug.cgi?id=442413 Bug ID: 442413 Summary: KDE doesn't respect the ~/.config/mimeapps.list defaults Product: plasmashell Version: 5.21.5 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: 61kyl...@anonaddy.me CC: plasma-b...@kde.org Target Milestone: 1.0 SUMMARY In Firefox, when opening the files from the downloads menu, the file always open in the wrong application (PNG images in Chromium or in ImageMagick, PDFs in GIMP etc). This happens even with the file associations being correct in System Settings > Applications > File associations. A Reddit user mentioned the following: >The root of the problem is: KDE does not initialize the XDG file associations >file ~/.config/mimeapps.list with its defaults. Instead KDE relies on its own >launch executable. Since Thunderbird / GTK apps parse that file to get >defaults it shows a random app that supports opening PDF files. >A quick workaround to solve this is forcing KDE to generate the entry for PDF >files. You can do that by changing file association order to something >different than the default applying it and then turning the ordering back to >Okular-first in System Settings -> File Associations. >It is an oddity left from KDE4 days. It allows people to try out KDE without >ruining GTK based desktop file associations but causes problems like this when >GTK apps are used under KDE desktop. >(https://www.reddit.com/r/kde/comments/pnnlga/kde_system_handler_does_not_offer_okular_as_an/hcri0t2/?utm_source=reddit_medium=web2x=3) After doing the workaround mentioned above, the files are opening (through the downloads menu of Firefox) in the correct applications. STEPS TO REPRODUCE 1. Open Firefox; 2. Download a PNG, PDF or JPG file; 3. Click in the downloads menu and open the file. OBSERVED RESULT The wrong app will open. EXPECTED RESULT The files opening in the right programs. SOFTWARE/OS VERSIONS Operating System: Kubuntu 21.04 KDE Plasma Version: 5.21.4 KDE Frameworks Version: 5.80.0 Qt Version: 5.15.2 Kernel Version: 5.11.0-34-generic OS Type: 64-bit Graphics Platform: X11 Processors: 8 × Intel® Core™ i5-8265U CPU @ 1.60GHz Memory: 15,5 GiB of RAM Graphics Processor: Mesa Intel® UHD Graphics 620 ADDITIONAL INFORMATION This happens in Ubuntu and in Neon. For reasons that are unknown to me, this doesn't happen in Fedora. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 442412] Disabling the firewall makes the toggle's label get stuck with "Disabling..."
https://bugs.kde.org/show_bug.cgi?id=442412 Michael Alexsander changed: What|Removed |Added CC||michaelalexsander@protonmai ||l.com -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 442412] New: Disabling the firewall makes the toggle's label get stuck with "Disabling..."
https://bugs.kde.org/show_bug.cgi?id=442412 Bug ID: 442412 Summary: Disabling the firewall makes the toggle's label get stuck with "Disabling..." Product: systemsettings Version: unspecified Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: kcm_firewall Assignee: plasma-b...@kde.org Reporter: michaelalexsan...@protonmail.com CC: tcanabr...@kde.org Target Milestone: --- Created attachment 141533 --> https://bugs.kde.org/attachment.cgi?id=141533=edit The stuck label. SUMMARY Disabling the firewall will make the label in the toggle get stuck with the "Disabling..." string, only switching to "Disabled" when changing the settings section. STEPS TO REPRODUCE 1. Press the toggle to disable the firewall. 2. Write in the password or cancel the action, it doesn't matter which. 3. See the bug. SOFTWARE/OS VERSIONS Linux: EndeavourOS KDE Plasma Version: 5.22.5 KDE Frameworks Version: 5.86.0 Qt Version: 5.15.2 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 442411] Window contents become invisible
https://bugs.kde.org/show_bug.cgi?id=442411 Mithrannussen changed: What|Removed |Added URL||https://youtu.be/srEdFEGIQ- ||c -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 442411] New: Window contents become invisible
https://bugs.kde.org/show_bug.cgi?id=442411 Bug ID: 442411 Summary: Window contents become invisible Product: kwin Version: 5.22.5 Platform: Manjaro OS: Linux Status: REPORTED Severity: major Priority: NOR Component: compositing Assignee: kwin-bugs-n...@kde.org Reporter: rmedeirosfla...@gmail.com Target Milestone: --- Created attachment 141532 --> https://bugs.kde.org/attachment.cgi?id=141532=edit qdbus org.kde.Kwin SUMMARY I have attached a .mkv screen recorder of the moment I was having the issue. Occasionally several windows, if not all, becomes invisible, not possible to interact with (maximize or minimize does not affect them), task switcher and the screen corner effect of showing all windows also fails to bring any content forefront. At the video there are a few programs visible, however they were all opened after the problem started and no other instance were already opened. STEPS TO REPRODUCE I cannot systematically describe the steps to reproduce this problem I am having because it seems to occur independently of the program opened but the issue appears to be more frequent when I use the shortcut Meta+D to show the desktop and afterwards hover the upper left corner to show all windows. OBSERVED RESULT Invisible windows - please see the screen recorder video. EXPECTED RESULT Window content visible. SOFTWARE/OS VERSIONS Distro: Manjaro Kde Kernel: 5.13.13-1-MANJARO KDE Plasma Version: 5.22.5 KDE Frameworks Version: 5.85.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION Latte Dock - it does not seems relevant because I already encountered this kwin problem when Latte was not even installed. Plasma settings - the bug is present even after a fresh install. I tried switching the rendering backend from OpenGL 2.0 to OpenGL 3.0 and later on to Xrender but it did not matter. Distribution - Although I am currently running Manjaro Pahvo, I recently managed to get the same issue while using Opensuse Tumbleweed, Fedora 34 and Garuda Linux. Plasma - I used Plasma for a very long time without having this problem, it started to appear with the release of the 5.22 version. I experimented with the most recent version of Debian and MXLinux and they do not show the same problem, I also believe that Opensuse LEAP will also work correctly due to the usage of a older plasma version. Xorg/Wayland - I mostly run Xorg but also encountered the visibility problem when trying Wayland. Kwin/Kwinft - The issue is present with both versions. -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 442410] New: Dock Aesthetics: App 1 changes their own and App 2's audio state in the dock (and other way around) due to same or similar names.
https://bugs.kde.org/show_bug.cgi?id=442410 Bug ID: 442410 Summary: Dock Aesthetics: App 1 changes their own and App 2's audio state in the dock (and other way around) due to same or similar names. Product: kde Version: unspecified Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: steradian.adr...@gmail.com Target Milestone: --- Created attachment 141531 --> https://bugs.kde.org/attachment.cgi?id=141531=edit Dolphin File Browser is supposedly playing audio according to the dock. Dock Aesthetics: App 1 changes their own and App 2's audio state in the dock (and other way around) due to same or similar names. In this case, Dolphin Emulator is playing audio and the dock says that Dolphin (File Browser) is also playing audio. How to reproduce: 1. Open Dolphin File Browser 2. Open Dolphin Emulator 3. Make only one start playing audio 4. Bug occurs Dolphin File Browser is not playing any audio, while the dock says otherwise. This issue does not apply to the Audio Volume widget/system-tray-icon. SOFTWARE/OS VERSIONS Linux/KDE Plasma: (available in About System) KDE Plasma Version: 5.22.5 KDE Frameworks Version: 5.86.0 Qt Version: 5.15.2 Screenshot attached. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 441904] KWin 5.22.5 regression on NVIDIA: Black screen when putting on/taking off full screen a previously maximized window.
https://bugs.kde.org/show_bug.cgi?id=441904 --- Comment #11 from angn...@gmail.com --- I reproduce the bug with a non-maximized but full-sized window, on the primary and secondary monitors, with and without toolbars. To reproduce on my 2560x1440 monitors (Nvidia driver): 1- resize the firefox window+decorations to the monitor resolution (2560x1440 in my case, adjust to yours). The window can be anywhere, only the size is important. 2- press F11 Expected: Full Screen window Actual: Black screen Also tested and reproduced with VLC, same procedure. KDE Info: Operating System: Arch Linux KDE Plasma Version: 5.22.5 KDE Frameworks Version: 5.85.0 Qt Version: 5.15.2 Kernel Version: 5.13.13-arch1-1 (64-bit) Graphics Platform: X11 Processors: 12 × AMD Ryzen 5 3600 6-Core Processor Memory: 31.3 GiB of RAM Graphics Processor: NVIDIA GeForce GTX 1660 SUPER/PCIe/SSE2 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 442409] New: 'Box' unattended.
https://bugs.kde.org/show_bug.cgi?id=442409 Bug ID: 442409 Summary: 'Box' unattended. Product: plasmashell Version: 5.22.5 Platform: openSUSE RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: rayd...@tiscali.co.uk CC: plasma-b...@kde.org Target Milestone: 1.0 Application: plasmashell (5.22.5) Qt Version: 5.15.2 Frameworks Version: 5.85.0 Operating System: Linux 5.14.1-1-default i686 Windowing System: X11 Drkonqi Version: 5.22.5 Distribution: openSUSE Tumbleweed -- Information about the crash: - What I was doing when the application crashed: 'Box' is a desktop with old drives (one of which is a CD/DVD read/write drive [4 in all]). I had win XP and open SUSE installed on hd1 with, Debian installed on hd3 and hd2 as a 'go between' for data between systems/OSs. I can only think that because I installed win 7 (possibly a contraband install) to determine issues I had with my sat-nav that 'booting issues' ensued. I 'quick formated' hd2 and perhaps this should've been a 'long format' to show any bad sectors, but other issues may arrise. Best regards, Ray Dart. The reporter is unsure if this crash is reproducible. -- Backtrace: Application: Plasma (plasmashell), signal: Aborted Content of s_kcrashErrorMessage: [Current thread is 1 (Thread 0xb2e299c0 (LWP 1679))] [KCrash Handler] #8 0xb7f63549 in __kernel_vsyscall () #9 0xb5327b14 in __libc_signal_restore_set (set=0xbf8293cc) at ../sysdeps/unix/sysv/linux/internal-signals.h:105 #10 __GI_raise (sig=6) at ../sysdeps/unix/sysv/linux/raise.c:47 #11 0xb531030d in __GI_abort () at abort.c:79 #12 0xb57920ce in qt_message_fatal (message=..., context=...) at global/qlogging.cpp:1914 #13 QMessageLogger::fatal (this=0xbf829678, msg=0xac8c5dc0 "QSGSimpleMaterialShader does not implement 'uniform lowp float %s' in its fragment shader") at global/qlogging.cpp:893 #14 0xac89113c in QSGSimpleMaterialShader::initialize (this=) at /usr/include/qt5/QtQuick/qsgsimplematerial.h:66 #15 FadingMaterialShader::initialize (this=0xb0409170) at /usr/src/debug/plasma-framework-5.85.0-2.1.i386/src/declarativeimports/core/fadingnode.cpp:77 #16 0xb75d4ef1 in QSGBatchRenderer::ShaderManager::prepareMaterial (this=0x291c4d0, material=0x385e5b0, enableRhiShaders=false, geometry=0x0) at /usr/src/debug/libqt5-qtdeclarative-5.15.2+kde29-1.3.i386/src/quick/scenegraph/coreapi/qsgbatchrenderer.cpp:306 #17 0xb75dbd9e in QSGBatchRenderer::Renderer::renderMergedBatch (batch=, this=0x2ae4ee0) at /usr/src/debug/libqt5-qtdeclarative-5.15.2+kde29-1.3.i386/src/quick/scenegraph/coreapi/qsgbatchrenderer.cpp:3082 #18 QSGBatchRenderer::Renderer::renderMergedBatch (this=0x2ae4ee0, batch=0x3893bf0) at /usr/src/debug/libqt5-qtdeclarative-5.15.2+kde29-1.3.i386/src/quick/scenegraph/coreapi/qsgbatchrenderer.cpp:3026 #19 0xb75e17fa in QSGBatchRenderer::Renderer::renderBatches (this=0x2ae4ee0) at /usr/src/debug/libqt5-qtdeclarative-5.15.2+kde29-1.3.i386/src/quick/scenegraph/coreapi/qsgbatchrenderer.cpp:4066 #20 0xb75e20b8 in QSGBatchRenderer::Renderer::render (this=0x2ae4ee0) at /usr/src/debug/libqt5-qtdeclarative-5.15.2+kde29-1.3.i386/src/quick/scenegraph/coreapi/qsgbatchrenderer.cpp:4363 #21 0xb75c8aeb in QSGRenderer::renderScene (bindable=warning: RTTI symbol for class 'QSGRenderer::renderScene(unsigned int)::B' is not a type ..., this=0x2ae4ee0) at /usr/src/debug/libqt5-qtdeclarative-5.15.2+kde29-1.3.i386/src/quick/scenegraph/coreapi/qsgrenderer.cpp:264 #22 QSGRenderer::renderScene (this=0x2ae4ee0, bindable=warning: RTTI symbol for class 'QSGRenderer::renderScene(unsigned int)::B' is not a type ...) at /usr/src/debug/libqt5-qtdeclarative-5.15.2+kde29-1.3.i386/src/quick/scenegraph/coreapi/qsgrenderer.cpp:220 #23 0xb75c9082 in QSGRenderer::renderScene (this=0x2ae4ee0, fboId=0) at /usr/src/debug/libqt5-qtdeclarative-5.15.2+kde29-1.3.i386/src/quick/scenegraph/coreapi/qsgrenderer.cpp:212 #24 0xb76328aa in QSGDefaultRenderContext::renderNextFrame (this=0x186eed0, renderer=0x2ae4ee0, fboId=0) at /usr/src/debug/libqt5-qtdeclarative-5.15.2+kde29-1.3.i386/src/quick/scenegraph/qsgdefaultrendercontext.cpp:228 #25 0xb76a53c9 in QQuickWindowPrivate::renderSceneGraph (this=0x19d95e0, size=..., surfaceSize=...) at /usr/src/debug/libqt5-qtdeclarative-5.15.2+kde29-1.3.i386/src/quick/items/qquickwindow.cpp:617 #26 0xb761c908 in QSGGuiThreadRenderLoop::renderWindow (this=0x1848780, window=) at /usr/src/debug/libqt5-qtdeclarative-5.15.2+kde29-1.3.i386/src/quick/scenegraph/qsgrenderloop.cpp:763 #27 0xb76b5270 in QQuickWindow::event (this=0x174cb50, e=0xbf82a610) at /usr/src/debug/libqt5-qtdeclarative-5.15.2+kde29-1.3.i386/src/quick/items/qquickwindow.cpp:1858 #28 0x004f25ba in ?? () #29 0xb67b0436 in QApplicationPrivate::notify_helper (this=0x15dd300, receiver=0x174cb50,
[kwin] [Bug 442408] Compositor is disabled after screen dim
https://bugs.kde.org/show_bug.cgi?id=442408 --- Comment #1 from n.parka...@gmail.com --- Maybe Bug 431858 as well. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 442408] New: Compositor is disabled after screen dim
https://bugs.kde.org/show_bug.cgi?id=442408 Bug ID: 442408 Summary: Compositor is disabled after screen dim Product: kwin Version: 5.22.5 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: compositing Assignee: kwin-bugs-n...@kde.org Reporter: n.parka...@gmail.com Target Milestone: --- SUMMARY Occasionally, when returning from a screen dim on X11, the compositor ends up disabled. Seems to reproduce more easily when another application is using openGL. Seems to be an integer overflow problem. STEPS TO REPRODUCE For me, leaving a firefox tab at https://webglsamples.org/aquarium/aquarium.html and letting the screen dim reliably triggers it. OBSERVED RESULT Compositor is disabled. EXPECTED RESULT Compositor should remain enabled. I built a custom package with some printf debugging, and found that in SceneOpenGL::viewportLimitsMatched(), from time to time the call to glGetIntegerv(GL_MAX_VIEWPORT_DIMS, limit) is returning a very large value for width, overflowing the GLint. Based on https://www.khronos.org/registry/OpenGL-Refpages/gl4/html/glViewport.xhtml it seems these dimensions are supposed to be GLsizei, and indeed I cannot reproduce the issue if I change the GLint to GLsizei in that function. This might be the same as Bug 394890. SOFTWARE/OS VERSIONS (available in About System) KDE Plasma Version: 5.22.5 KDE Frameworks Version: 5.85.0 Qt Version: 5.15.2-arch1-2 ADDITIONAL INFORMATION Radeon RX 570 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 442397] Regression: Dockers with utility titlebar no longer have reasonable size policy.
https://bugs.kde.org/show_bug.cgi?id=442397 Eoin O'Neill changed: What|Removed |Added CC||eoinoneill1...@gmail.com Keywords||release_blocker -- You are receiving this mail because: You are watching all bug changes.
[ktorrent] [Bug 442407] New: Crash when I download kubuntu 21.04 ISO file
https://bugs.kde.org/show_bug.cgi?id=442407 Bug ID: 442407 Summary: Crash when I download kubuntu 21.04 ISO file Product: ktorrent Version: unspecified Platform: Ubuntu Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: joris.guis...@gmail.com Reporter: zyn779735...@hotmail.com Target Milestone: --- Application: ktorrent (5.1.2) Qt Version: 5.12.8 Frameworks Version: 5.68.0 Operating System: Linux 5.11.0-34-generic x86_64 Windowing system: X11 Distribution: Ubuntu 20.04.3 LTS -- Information about the crash: - What I was doing when the application crashed: I was downloading the iso in the background, and nomatter what I do, browsing webpage, reading pdf documents, and even do nothing, it would be crash at a special time. The crash can be reproduced sometimes. -- Backtrace: Application: KTorrent (ktorrent), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f50b957e800 (LWP 8247))] Thread 3 (Thread 0x7f50b6564700 (LWP 8251)): #0 0x7f50bd80aaff in __GI___poll (fds=0x7f50ac002ee0, nfds=1, timeout=10156) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7f50bc3ca36e in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f50bc3ca4a3 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f50bdf11583 in QEventDispatcherGlib::processEvents(QFlags) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7f50bdeb84db in QEventLoop::exec(QFlags) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f50bdcf0785 in QThread::exec() () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7f50bdcf19d2 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7f50bcc8b609 in start_thread (arg=) at pthread_create.c:477 #8 0x7f50bd817293 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 2 (Thread 0x7f50b7871700 (LWP 8249)): #0 0x7f50bd80aaff in __GI___poll (fds=0x7f50a8025c80, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7f50bc3ca36e in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f50bc3ca4a3 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f50bdf11583 in QEventDispatcherGlib::processEvents(QFlags) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7f50bdeb84db in QEventLoop::exec(QFlags) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f50bdcf0785 in QThread::exec() () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7f50bee1befa in ?? () from /lib/x86_64-linux-gnu/libQt5DBus.so.5 #7 0x7f50bdcf19d2 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7f50bcc8b609 in start_thread (arg=) at pthread_create.c:477 #9 0x7f50bd817293 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 1 (Thread 0x7f50b957e800 (LWP 8247)): [KCrash Handler] #6 __memmove_avx_unaligned_erms () at ../sysdeps/x86_64/multiarch/memmove-vec-unaligned-erms.S:468 #7 0x7f50bdee5300 in QMetaObject::activate(QObject*, int, int, void**) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7f50bf5917a8 in KIO::TransferJob::data(KIO::Job*, QByteArray const&) () from /lib/x86_64-linux-gnu/libKF5KIOCore.so.5 #9 0x7f50bf591d3d in KIO::TransferJob::slotData(QByteArray const&) () from /lib/x86_64-linux-gnu/libKF5KIOCore.so.5 #10 0x7f50bdee5458 in QMetaObject::activate(QObject*, int, int, void**) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #11 0x7f50bf555626 in KIO::SlaveInterface::data(QByteArray const&) () from /lib/x86_64-linux-gnu/libKF5KIOCore.so.5 #12 0x7f50bf55843d in KIO::SlaveInterface::dispatch(int, QByteArray const&) () from /lib/x86_64-linux-gnu/libKF5KIOCore.so.5 #13 0x7f50bf555f4f in KIO::SlaveInterface::dispatch() () from /lib/x86_64-linux-gnu/libKF5KIOCore.so.5 #14 0x7f50bf55f152 in KIO::Slave::gotInput() () from /lib/x86_64-linux-gnu/libKF5KIOCore.so.5 #15 0x7f50bdee5458 in QMetaObject::activate(QObject*, int, int, void**) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #16 0x7f50bdee5d5a in QObject::event(QEvent*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #17 0x7f50be8d3a66 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #18 0x7f50be8dd0f0 in QApplication::notify(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #19 0x7f50bdeb993a in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #20 0x7f50bdebc5b8 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #21 0x7f50bdf11f67 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #22 0x7f50bc3ca17d in g_main_context_dispatch () from
[krita] [Bug 442397] Regression: Dockers with utility titlebar no longer have reasonable size policy.
https://bugs.kde.org/show_bug.cgi?id=442397 Eoin O'Neill changed: What|Removed |Added Assignee|eoinoneill1...@gmail.com|sh...@sdf.org Ever confirmed|0 |1 Keywords||regression Status|REPORTED|CONFIRMED --- Comment #1 from Eoin O'Neill --- Regression caused by commit a6d750785207aacc5bbe493c9351e6ab50b66339 : I've attached a picture of what it looks like. We do need the dockers to respect a minimum size so that the toolbars don't get squashed together. While bug 441761 was fixed with the original commit, there must be another way to resolve this issue without allowing the user to resize the docker to unusable sizes. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 436705] Krita crashes on exit every time
https://bugs.kde.org/show_bug.cgi?id=436705 cobratornado changed: What|Removed |Added CC||cobratorn...@gmx.us -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 436705] Krita crashes on exit every time
https://bugs.kde.org/show_bug.cgi?id=436705 --- Comment #4 from cobratornado --- Created attachment 141530 --> https://bugs.kde.org/attachment.cgi?id=141530=edit New crash information added by DrKonqi krita (4.2.9) using Qt 5.12.8 - What I was doing when the application crashed: Closing the application - Unusual behavior I noticed: Notification that the program has crashed - Custom settings of the application: None -- Backtrace (Reduced): #11 0x7f1be7731908 in QWidget::~QWidget() () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #12 0x7f1be7731e1d in QWidget::~QWidget() () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #13 0x7f1be6d0501e in QObjectPrivate::deleteChildren() () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #14 0x7f1be7731c29 in QWidget::~QWidget() () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 [...] #16 0x7f1be6d0501e in QObjectPrivate::deleteChildren() () from /lib/x86_64-linux-gnu/libQt5Core.so.5 -- You are receiving this mail because: You are watching all bug changes.
[Elisa] [Bug 417610] Automatically enqueue the following songs when selecting & playing a song from the main view
https://bugs.kde.org/show_bug.cgi?id=417610 Sidney changed: What|Removed |Added CC||sidneycrest...@yahoo.com -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 438552] With Translucency effect, applications can not be focused anymore and leave a ghost when switching virtual desktops
https://bugs.kde.org/show_bug.cgi?id=438552 --- Comment #24 from Joe --- Created attachment 141529 --> https://bugs.kde.org/attachment.cgi?id=141529=edit Ghost Image example of ghost image (that cannot be interacted with/closed/etc) -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 438552] With Translucency effect, applications can not be focused anymore and leave a ghost when switching virtual desktops
https://bugs.kde.org/show_bug.cgi?id=438552 Joe changed: What|Removed |Added CC||jchevar...@gmail.com --- Comment #23 from Joe --- Also, think I am seeing this bug on Arch. Attaching a screenshot of a Zoom meeting that got "burned" burned into my secondary monitor (blanked out the various people/names, of course). Also, note that in this instance it is only on my one virtual desktop it is stuck on. I have also in the past where it gets stuck on more than one virtual desktop (but always on either the primary or secondary monitors, not both). This one is also kind of odd - I have been out for a bit, and haven't used the laptop in over a week. The zoom meeting in question was not burned in this morning when I resumed it from sleep (that I can remember). Curiously, the meeting, based on participants, was from over a week ago so I have no idea how it is now just got stuck (unless maybe it was stuck on a different desktop and moved?). Also put this last part with a grain of salt as I am just getting over being rather sick, so perhaps my mind is playing tricks. Plasma 5.22.5 Frameworks 5.86.0 QT 5.15.2 X11 Nvidia 470.63.01 Note: Optimus laptop, so, using Intel as the primary driver and the official Nvidia binary support. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 442406] Impossible work with massive documents files
https://bugs.kde.org/show_bug.cgi?id=442406 --- Comment #1 from varlesh --- This function must be present in a text editor, but not in file manager. It's annoying and time-consuming, especially when you work with a lot of documents. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 434868] plasma crashed when I tried to add widget to desktop area behind the widget explorer in wayland session
https://bugs.kde.org/show_bug.cgi?id=434868 Devin Rozsas changed: What|Removed |Added CC||droz...@mailfence.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 434868] plasma crashed when I tried to add widget to desktop area behind the widget explorer in wayland session
https://bugs.kde.org/show_bug.cgi?id=434868 --- Comment #3 from Devin Rozsas --- Created attachment 141528 --> https://bugs.kde.org/attachment.cgi?id=141528=edit New crash information added by DrKonqi plasmashell (5.22.4) using Qt 5.15.3 - What I was doing when the application crashed: Adding widgets to a panel. This time, it was a Latte-dock panel, but it happens with common Plasma panels as well. - Unusual behavior I noticed: The whole widgets menu becomes darker* and the wallpaper area goes completely black. I close the widgets menu by clicking the X button (which is possible, even in this state) and everything gets back to normal. Widget is added to panel as expected and wallpaper rolls back to whatever it was before. * I'm using Breeze Dark, I'm assuming less color contrast means irresponsive. So, in light themes, it might actually get lighter/brighter? -- Backtrace (Reduced): #6 0x7ff730c1c9ab in QQuickWindowPrivate::sendFilteredPointerEventImpl(QQuickPointerEvent*, QQuickItem*, QQuickItem*) () from /usr/lib/libQt5Quick.so.5 #7 0x7ff730c1ccf7 in QQuickWindowPrivate::sendFilteredPointerEventImpl(QQuickPointerEvent*, QQuickItem*, QQuickItem*) () from /usr/lib/libQt5Quick.so.5 #8 0x7ff730c1ccf7 in QQuickWindowPrivate::sendFilteredPointerEventImpl(QQuickPointerEvent*, QQuickItem*, QQuickItem*) () from /usr/lib/libQt5Quick.so.5 #9 0x7ff730c1ccf7 in QQuickWindowPrivate::sendFilteredPointerEventImpl(QQuickPointerEvent*, QQuickItem*, QQuickItem*) () from /usr/lib/libQt5Quick.so.5 #10 0x7ff730c2097d in QQuickWindowPrivate::deliverMouseEvent(QQuickPointerMouseEvent*) () from /usr/lib/libQt5Quick.so.5 -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 442406] New: Impossible work with massive documents files
https://bugs.kde.org/show_bug.cgi?id=442406 Bug ID: 442406 Summary: Impossible work with massive documents files Product: dolphin Version: 21.08.1 Platform: Neon Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: view-engine: tooltip Assignee: dolphin-bugs-n...@kde.org Reporter: varl...@gmail.com CC: kfm-de...@kde.org Target Milestone: --- Dolphin very lagg with massive text files, like as DOC, DOCX, RTF and etc... When you focuse cursor on any massive text file application freeze to 20 seconds or more. It's happened because tooltip function counts words and strings on this document. I cant't work with this, i can't rename/copy/move or any action with this stupid function. How reproduce it: Focus cursor to any massive documen file (doc, docx and etc) with 10 words -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 442405] New: color mismatch
https://bugs.kde.org/show_bug.cgi?id=442405 Bug ID: 442405 Summary: color mismatch Product: krita Version: 4.4.8 Platform: Microsoft Windows OS: Microsoft Windows Status: REPORTED Severity: normal Priority: NOR Component: * Unknown Assignee: krita-bugs-n...@kde.org Reporter: fo...@mail.ru Target Milestone: --- Created attachment 141527 --> https://bugs.kde.org/attachment.cgi?id=141527=edit log text from 4.4.8 and 5.0 STEPS TO REPRODUCE 1. set red color 2. draw OBSERVED RESULT drawn in blue color EXPECTED RESULT drawn in red color Windows 7 video in google drive: https://drive.google.com/file/d/19SrtrpUqTj6bfGOAK8Di764SM5zWtDy2/view?usp=sharing in video: - try versions 4.4.8 and 5.0 - comparing with GIMP - deleting krita files in %localappdata%, %appdata% -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 442404] New: Launching Discover from the Notifier on Wayland shows both desktop and mobile controls in on the Updates page
https://bugs.kde.org/show_bug.cgi?id=442404 Bug ID: 442404 Summary: Launching Discover from the Notifier on Wayland shows both desktop and mobile controls in on the Updates page Product: Discover Version: git-master Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: discover Assignee: lei...@leinir.dk Reporter: n...@kde.org CC: aleix...@kde.org Target Milestone: --- Created attachment 141526 --> https://bugs.kde.org/attachment.cgi?id=141526=edit Mobile controls seen inappropriately Strange bug; just what the title says. If I open Discover by clicking on the Notifier System Tray item while in a Wayland session, mobile controls appear on the Updates page. They do not appear if accessing the Updates page from any other way: - Launching the app and going to the Updates page manually in a Wayland session - Launching the app and going to the Updates page manually in an X11 session - Launching the app from the Notifier System Tray item in an X11 session -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 442403] New: Plasma Crashed On Turning Off Visual Effects
https://bugs.kde.org/show_bug.cgi?id=442403 Bug ID: 442403 Summary: Plasma Crashed On Turning Off Visual Effects Product: plasmashell Version: 5.22.5 Platform: Neon Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: flavio.hferre...@outlook.com CC: plasma-b...@kde.org Target Milestone: 1.0 Application: plasmashell (5.22.5) Qt Version: 5.15.3 Frameworks Version: 5.85.0 Operating System: Linux 5.11.0-34-generic x86_64 Windowing System: X11 Drkonqi Version: 5.22.5 Distribution: KDE neon User Edition 5.22 -- Information about the crash: - What I was doing when the application crashed: I used the shortcut Shift + Alt + F12 to turn off visual effects like shadows and transparency and plasma disapeared, rebooting automatically after a minute or so. The reporter is unsure if this crash is reproducible. -- Backtrace: Application: Plasma (plasmashell), signal: Segmentation fault [New LWP 1287] [New LWP 1329] [New LWP 1360] [New LWP 1361] [New LWP 1362] [New LWP 1363] [New LWP 1388] [New LWP 1464] [New LWP 1467] [New LWP 1477] [New LWP 1478] [New LWP 1480] [New LWP 1486] [New LWP 1487] [New LWP 1488] [New LWP 1491] [New LWP 1497] [New LWP 1508] [New LWP 1525] [New LWP 1526] [New LWP 1551] [New LWP 1742] [New LWP 3636] [New LWP 7834] [New LWP 10377] [New LWP 14521] [New LWP 16150] [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". 0x7f101520eaff in __GI___poll (fds=0x7ffded40eeb8, nfds=1, timeout=1000) at ../sysdeps/unix/sysv/linux/poll.c:29 [Current thread is 1 (Thread 0x7f101136e9c0 (LWP 1250))] Thread 28 (Thread 0x7f0f9d4d7700 (LWP 16150)): #0 futex_wait_cancelable (private=, expected=0, futex_word=0x55662b868560) at ../sysdeps/nptl/futex-internal.h:183 #1 __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x55662b868510, cond=0x55662b868538) at pthread_cond_wait.c:508 #2 __pthread_cond_wait (cond=0x55662b868538, mutex=0x55662b868510) at pthread_cond_wait.c:638 #3 0x7f10155a359b in QWaitConditionPrivate::wait (deadline=..., this=0x55662b868510) at thread/qwaitcondition_unix.cpp:146 #4 QWaitCondition::wait (this=, mutex=0x7f100809e100, deadline=...) at thread/qwaitcondition_unix.cpp:225 #5 0x7f10171fab44 in ?? () from /lib/x86_64-linux-gnu/libQt5Quick.so.5 #6 0x7f10171fafb9 in ?? () from /lib/x86_64-linux-gnu/libQt5Quick.so.5 #7 0x7f101559d42c in QThreadPrivate::start (arg=0x7f100809e060) at thread/qthread_unix.cpp:329 #8 0x7f10144f2609 in start_thread (arg=) at pthread_create.c:477 #9 0x7f101521b293 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 27 (Thread 0x7f0fabfff700 (LWP 14521)): #0 futex_abstimed_wait_cancelable (private=, abstime=0x7f0fabffe8f0, clockid=, expected=0, futex_word=0x7f0fabffeac8) at ../sysdeps/nptl/futex-internal.h:320 #1 __pthread_cond_wait_common (abstime=0x7f0fabffe8f0, clockid=, mutex=0x7f0fabffea78, cond=0x7f0fabffeaa0) at pthread_cond_wait.c:520 #2 __pthread_cond_timedwait (cond=0x7f0fabffeaa0, mutex=0x7f0fabffea78, abstime=0x7f0fabffe8f0) at pthread_cond_wait.c:656 #3 0x7f0fc6b2820a in ?? () from /lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #4 0x4f14 in ?? () #5 0x137177e8 in ?? () #6 0x4ef3 in ?? () #7 0x137177e8 in ?? () #8 0x7f0fa40040c8 in ?? () #9 0x350ff27417477700 in ?? () #10 0x in ?? () Thread 26 (Thread 0x7f0fb57fa700 (LWP 10377)): #0 0x7f101520eaff in __GI___poll (fds=0x7f0fac0b3eb0, nfds=3, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7f0fe2f571d6 in ?? () from /lib/x86_64-linux-gnu/libpulse.so.0 #2 0x7f0fe2f48841 in pa_mainloop_poll () from /lib/x86_64-linux-gnu/libpulse.so.0 #3 0x7f0fe2f48ec3 in pa_mainloop_iterate () from /lib/x86_64-linux-gnu/libpulse.so.0 #4 0x7f0fe2f48f70 in pa_mainloop_run () from /lib/x86_64-linux-gnu/libpulse.so.0 #5 0x7f0fe2f5711d in ?? () from /lib/x86_64-linux-gnu/libpulse.so.0 #6 0x7f0fe2cb272c in ?? () from /usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-13.99.so #7 0x7f10144f2609 in start_thread (arg=) at pthread_create.c:477 #8 0x7f101521b293 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 25 (Thread 0x7f0f9fb42700 (LWP 7834)): #0 futex_wait_cancelable (private=, expected=0, futex_word=0x55662d5d9d10) at ../sysdeps/nptl/futex-internal.h:183 #1 __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x55662d5d9cc0, cond=0x55662d5d9ce8) at pthread_cond_wait.c:508 #2 __pthread_cond_wait (cond=0x55662d5d9ce8, mutex=0x55662d5d9cc0) at pthread_cond_wait.c:638 #3 0x7f10155a359b in QWaitConditionPrivate::wait (deadline=..., this=0x55662d5d9cc0) at thread/qwaitcondition_unix.cpp:146 #4
[Discover] [Bug 442402] New: Unchecking all packages to update is very slow
https://bugs.kde.org/show_bug.cgi?id=442402 Bug ID: 442402 Summary: Unchecking all packages to update is very slow Product: Discover Version: 5.21.5 Platform: Debian unstable OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: discover Assignee: lei...@leinir.dk Reporter: david.cortes.riv...@gmail.com CC: aleix...@kde.org Target Milestone: --- SUMMARY If I am in the "Updates" view and have a few hundred updates or more, clicking the checkbox at the bottom to unselect all updates is really slow. STEPS TO REPRODUCE 1. Have many package updates available. 2. Open discover and go to the "updates" view. 3. Uncheck the box at the bottom. OBSERVED RESULT Takes more than one second to uncheck barely a few hundred packages. EXPECTED RESULT Unchecking boxes should have a throughput of several million per second in a modern computer. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: 5.21.5 KDE Frameworks Version: 5.84.5 Qt Version: 5.15.2 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 442401] New: Discover updates dependencies without warning
https://bugs.kde.org/show_bug.cgi?id=442401 Bug ID: 442401 Summary: Discover updates dependencies without warning Product: Discover Version: 5.21.5 Platform: Debian unstable OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: discover Assignee: lei...@leinir.dk Reporter: david.cortes.riv...@gmail.com CC: aleix...@kde.org Target Milestone: --- SUMMARY If I have many package updates available, and I try to use discover to update only some of those packages, as soon as I tick a package to update, it will tick all its dependencies without indicating this to the user. If the list of packages to update is large, chances are that the user will not notice that ticking a given package also ticked other packages along, which is not transparent. STEPS TO REPRODUCE 1. Have many package updates available with dependencies that would also have updates. 2. Go to discover's update view and untick all the packages with the checkbox at the bottom. 3. Tick a package with dependencies that also have updates. OBSERVED RESULT Automatically ticks all dependencies without any warning. EXPECTED RESULT Should warn about packages that also need to be updated along, asking for confirmation. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: 5.21.5 KDE Frameworks Version: 5.85.5 Qt Version: 5.15.2 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 441610] when switching virtual desktops on OpenBox, konsole windows revert to their default sizes
https://bugs.kde.org/show_bug.cgi?id=441610 nsprang...@gmail.com changed: What|Removed |Added CC||nsprang...@gmail.com --- Comment #10 from nsprang...@gmail.com --- (In reply to Michael Konieczny from comment #8) > I can hide text, I can disable toolbars completely, but when before > mimimization there was some layout, even with ellipsized toolbars, it should > be retained on restore. It's the same bug. I just built 21.08 from git and it's fixed, so I think that means it should hit 21.08.2. https://community.kde.org/Schedules/KDE_Gear_21.08_Schedule -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 441974] Animated transform mask breaks when using move tool instead of transform tool.
https://bugs.kde.org/show_bug.cgi?id=441974 Eoin O'Neill changed: What|Removed |Added Latest Commit||https://invent.kde.org/grap ||hics/krita/commit/4b933a691 ||edb7c78698f3c294020951abddc ||971d Status|REPORTED|RESOLVED Resolution|--- |FIXED --- Comment #1 from Eoin O'Neill --- Git commit 4b933a691edb7c78698f3c294020951abddc971d by Eoin O'Neill. Committed on 13/09/2021 at 23:15. Pushed by eoinoneill into branch 'master'. AnimTransform: Fix move tool not respecting, modifying, or outright breaking animated masks. Should work more or less how the user expects. There could be more to streamline the process to make it less error prone to interface with animation, and `setParameters` sometimes causing animations to "break" will need to be investigated at some point. For now, it works. M +3-0libs/image/kis_transform_mask_params_interface.h M +17 -2libs/ui/tool/strokes/move_stroke_strategy.cpp M +1-0libs/ui/tool/strokes/move_stroke_strategy.h M +12 -0 plugins/tools/tool_transform2/kis_animated_transform_parameters.cpp M +3-0 plugins/tools/tool_transform2/kis_animated_transform_parameters.h https://invent.kde.org/graphics/krita/commit/4b933a691edb7c78698f3c294020951abddc971d -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 442368] crash after change layer order after transform mask on file layer
https://bugs.kde.org/show_bug.cgi?id=442368 --- Comment #3 from vanyossi --- Hey eoin animation dockers are not open. dockers present are: Brush preset, advanced color selector, Tool options and Layers. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 442400] New: Ambiguous Shortcuts on Ctrl+Alt+I
https://bugs.kde.org/show_bug.cgi?id=442400 Bug ID: 442400 Summary: Ambiguous Shortcuts on Ctrl+Alt+I Product: digikam Version: 7.2.0 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: general Assignee: digikam-bugs-n...@kde.org Reporter: j...@pearson.onl Target Milestone: --- SUMMARY When I launch digiKam, I get an error window reading: ``` There are two actions (Open Command Bar, Add Images...) that want to use the same shortcut (Ctrl+Alt+I) ``` I checked in keyboard shortcuts, and sure enough, those are both bound to Ctrl+Alt+I by default. Resetting to default bindings didn't affect either binding, so it seems that the defaults are conflicting. Sorry if this has already been fixed, but I didn't see any bug reports on this particular error so I thought better safe than sorry. STEPS TO REPRODUCE 1. Install digikam (I used the `digikam` package on Fedora 34) 2. Launch digikam 3. Observe error message SOFTWARE/OS VERSIONS KDE Plasma Version: 5.22.4 KDE Frameworks Version: 5.85.0 Qt Version: 5.15.2 digiKam build date: 4/30/21 3:30 PM (target: release) -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 442399] New: Gwenview crashed when browsing pictures in fullscreen
https://bugs.kde.org/show_bug.cgi?id=442399 Bug ID: 442399 Summary: Gwenview crashed when browsing pictures in fullscreen Product: gwenview Version: 21.08.1 Platform: Archlinux Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: gwenview-bugs-n...@kde.org Reporter: and...@cavallium.it Target Milestone: --- Application: gwenview (21.08.1) Qt Version: 5.15.2 Frameworks Version: 5.86.0 Operating System: Linux 5.14.2-zen1-2-zen x86_64 Windowing System: X11 Drkonqi Version: 5.22.5 Distribution: Arch Linux -- Information about the crash: - What I was doing when the application crashed: Gwenview crashed when I was browsing pictures in fullscreen, I moved the mouse to the toolbar to exit the fullscreen and it crashed when the toolbar was expanding. The reporter is unsure if this crash is reproducible. -- Backtrace: Application: Gwenview (gwenview), signal: Segmentation fault [KCrash Handler] #4 0x7f74f2a2e440 in QScreen::geometry() const () from /usr/lib/libQt5Gui.so.5 #5 0x7f74f4000766 in Gwenview::FullScreenBar::eventFilter(QObject*, QEvent*) () from /usr/lib/libgwenviewlib.so.5 #6 0x7f74f2386fde in QCoreApplicationPrivate::sendThroughApplicationEventFilters(QObject*, QEvent*) () from /usr/lib/libQt5Core.so.5 #7 0x7f74f3101da2 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib/libQt5Widgets.so.5 #8 0x7f74f23873ba in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /usr/lib/libQt5Core.so.5 #9 0x7f74f2a05210 in QGuiApplicationPrivate::processMouseEvent(QWindowSystemInterfacePrivate::MouseEvent*) () from /usr/lib/libQt5Gui.so.5 #10 0x7f74f29da7e5 in QWindowSystemInterface::sendWindowSystemEvents(QFlags) () from /usr/lib/libQt5Gui.so.5 #11 0x7f74ec341fcc in ?? () from /usr/lib/libQt5XcbQpa.so.5 #12 0x7f74efa7a10c in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0 #13 0x7f74efacdba9 in ?? () from /usr/lib/libglib-2.0.so.0 #14 0x7f74efa77871 in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0 #15 0x7f74f23dffe6 in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/libQt5Core.so.5 #16 0x7f74f2385d2c in QEventLoop::exec(QFlags) () from /usr/lib/libQt5Core.so.5 #17 0x7f74f238e294 in QCoreApplication::exec() () from /usr/lib/libQt5Core.so.5 #18 0x55f13fada94e in ?? () #19 0x7f74f1d13b25 in __libc_start_main () from /usr/lib/libc.so.6 #20 0x55f13fadab4e in ?? () [Inferior 1 (process 32483) detached] The reporter indicates this bug may be a duplicate of or related to bug 441561. Possible duplicates by query: bug 441561, bug 432205, bug 428804, bug 420467, bug 410763. Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[kstars] [Bug 430365] Guiding RMS Error After Dithering
https://bugs.kde.org/show_bug.cgi?id=430365 --- Comment #11 from Hy --- I was not able to reproduce this, however I did look through the code and tightened up a couple things and am submitting merge request https://invent.kde.org/education/kstars/-/merge_requests/430 that will hopefully improve the situation. - The previous code suspended capture if there were 2 or more guide iterations that exceeded the stated guide drift value, even if they were separated by hours (in a single capture sequence). This now requires 3 consecutive guide iterations to exceed the value in order to suspend capture. - The current code exempted the states GUIDE_DITHERING and GUIDE_MANUAL_DITHERING from broadcasting its drift to capture, but didn't exempt GUIDE_DITHERING_ERROR, GUIDE_DITHERING_SUCCESS, and GUIDE_DITHERING_SETTLE. It's possible that some drift computed in one of the latter states found its way to capture, and caused capture to suspend. BTW, the current code doesn't check the RMS value. That is, it isn't looking at an average over past N samples. It considers the most recent guide deviation and makes its decision based on that one or two samples (or now, based on 3 consecutive samples). -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 442398] non-latin symbols inside PDF-forms not displayed in view-mode and non-printable
https://bugs.kde.org/show_bug.cgi?id=442398 --- Comment #1 from Amin --- P.S. In firefox all symbols from PDF-forms fields displayed correctly; -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 442398] New: non-latin symbols inside PDF-forms not displayed in view-mode and non-printable
https://bugs.kde.org/show_bug.cgi?id=442398 Bug ID: 442398 Summary: non-latin symbols inside PDF-forms not displayed in view-mode and non-printable Product: okular Version: 21.04.1 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: PDF backend Assignee: okular-de...@kde.org Reporter: ami...@tuta.io Target Milestone: --- Created attachment 141525 --> https://bugs.kde.org/attachment.cgi?id=141525=edit PDF for test displaying non-latin / ex-latin / math / cyrillic symbols in FORMS SUMMARY When PDF with forms filled, non-latin chars displayed only in edit-mode; In view / print_preview mode non-latin or extended latin chars not displayed; This chars also not printed; STEPS TO REPRODUCE 1. Open PDF with filled form from attach in okular 2. Press button "Show forms" and compare data strings in edit- and display- modes. 3. Try print filled form to printer (ex cups-pdf) and discover that only basic latin characters printed. OBSERVED RESULT Extended-Latin (extension A-E in kCharSelect), cyrillic and math-symbols inside PDF-forms not displayed in view-mode and not printing. EXPECTED RESULT All symbols visible and printable in PDF-forms fields. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Fedora 34 / KDE @ X11 KDE Plasma Version: 5 KDE Frameworks Version: 5.85.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 442397] Regression: Dockers with utility titlebar no longer have reasonable size policy.
https://bugs.kde.org/show_bug.cgi?id=442397 Emmet O'Neill changed: What|Removed |Added Assignee|krita-bugs-n...@kde.org |eoinoneill1...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 442397] New: Regression: Dockers with utility titlebar no longer have reasonable size policy.
https://bugs.kde.org/show_bug.cgi?id=442397 Bug ID: 442397 Summary: Regression: Dockers with utility titlebar no longer have reasonable size policy. Product: krita Version: git master (please specify the git hash!) Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Dockers Assignee: krita-bugs-n...@kde.org Reporter: emmetoneill@gmail.com Target Milestone: --- SUMMARY Dockers that use the KisUtilityTitlebar (KisAnimTimelineDocker, KisAnimCurvesDocker) no longer maintain an appropriate minimum size and shrink too small. This is a regression. linux git master -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 442396] Didnt save
https://bugs.kde.org/show_bug.cgi?id=442396 Tiar changed: What|Removed |Added CC||tamtamy.tym...@gmail.com Resolution|--- |WAITINGFORINFO Status|REPORTED|NEEDSINFO --- Comment #1 from Tiar --- Which version were you using, and can you please attach Help -> Show Krita log for bug reports and say what was that file called? Also check this manual page for potential ways to recover your files: https://docs.krita.org/en/KritaFAQ.html#how-to-recover-my-files Also note that this is not exactly a bug report; it's an issue, but it should be posted on the help forum on https://krita-artists.org/c/support/general-questions/26 . This website here - bugs.kde.org - is a development-focused website, so unless you provide information how exactly did it happen (so a developer can go and fix it), it's a user issue, not a bug report (user issues are still important, this is just a wrong place for them). -- You are receiving this mail because: You are watching all bug changes.
[ksysguard] [Bug 412884] Excessive precision in I/O graphs; usability;
https://bugs.kde.org/show_bug.cgi?id=412884 Amin changed: What|Removed |Added Resolution|--- |FIXED Status|REPORTED|RESOLVED --- Comment #1 from Amin --- fixed in 5.22.0 -- You are receiving this mail because: You are watching all bug changes.
[ksysguard] [Bug 405414] Header name and colors options don't saved for [Partition usage] --> [Table (listview)]
https://bugs.kde.org/show_bug.cgi?id=405414 --- Comment #4 from Amin --- Fedora 34, ksysguard 5.22.0 - color options for disk usage table still non-working; -- You are receiving this mail because: You are watching all bug changes.
[ksysguard] [Bug 405414] Header name and colors options don't saved for [Partition usage] --> [Table (listview)]
https://bugs.kde.org/show_bug.cgi?id=405414 Amin changed: What|Removed |Added Version|5.17.5 |5.22.0 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 442396] New: Didnt save
https://bugs.kde.org/show_bug.cgi?id=442396 Bug ID: 442396 Summary: Didnt save Product: krita Version: unspecified Platform: Other OS: Other Status: REPORTED Severity: normal Priority: NOR Component: * Unknown Assignee: krita-bugs-n...@kde.org Reporter: filipa.isabe...@gmail.com Target Milestone: --- SUMMARY i clicked save in 3 different situations and when i was going to close the app also clicked to save. still, didnt save any of the work of today, only have a broken file i cant open STEPS TO REPRODUCE 1. 2. 3. OBSERVED RESULT EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 442395] Dragging multiple images to subfolder obscures folders
https://bugs.kde.org/show_bug.cgi?id=442395 --- Comment #2 from Philip Murray --- In the above screenshots the cursor doesn't seem to appear but that must just be what Spectacle does, but the cursor was in amongst the thumbnails. If the thumbnails weren't directly under the cursor also that might be good, in addition to my above suggestions. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 441479] kdenlive failes to start because of "Segmetation Failed"
https://bugs.kde.org/show_bug.cgi?id=441479 Axel Dreißig changed: What|Removed |Added Resolution|WAITINGFORINFO |--- Status|NEEDSINFO |REPORTED --- Comment #3 from Axel Dreißig --- the distributor fixed the fault. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 442395] Dragging multiple images to subfolder obscures folders
https://bugs.kde.org/show_bug.cgi?id=442395 --- Comment #1 from Philip Murray --- Created attachment 141524 --> https://bugs.kde.org/attachment.cgi?id=141524=edit Another example -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 442395] New: Dragging multiple images to subfolder obscures folders
https://bugs.kde.org/show_bug.cgi?id=442395 Bug ID: 442395 Summary: Dragging multiple images to subfolder obscures folders Product: dolphin Version: 20.12.2 Platform: Other OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: philipihmur...@hotmail.com CC: kfm-de...@kde.org Target Milestone: --- Created attachment 141523 --> https://bugs.kde.org/attachment.cgi?id=141523=edit Example of difficult to see folders beneath the cursor whilst dragging image files. SUMMARY: Dragging multiple images to subfolder obscures folders STEPS TO REPRODUCE: 1. Folder with multiple images in it. Folder view set to small small icons (~22px). 2. Drag/select multiple images towards a subfolder. OBSERVED RESULT: A number of thumbnail preview images get grouped in a block under the cursor. When the folders are small icons, it becomes difficult to see the folder because the cursor can be difficult to see amongst the block of thumbnails around it (especially if cursor is black), and the block of thumbnails obscure the folders under them & the light blue surround that appears on a folder when it is in focus as the drop destination isn't easy to see in this situation. EXPECTED RESULT Could the thumbnails be heavily desaturated or limited to maybe 4 at most, or some other indicator be used to indicate the drag & drop operation? SOFTWARE/OS VERSIONS Operating System: Debian GNU/Linux 11 KDE Plasma Version: 5.20.5 KDE Frameworks Version: 5.78.0 Qt Version: 5.15.2 Kernel Version: 5.10.0-8-amd64 OS Type: 64-bit Processors: 4 × Intel® Core™ i5-4570 CPU @ 3.20GHz Memory: 7.7 GiB of RAM Graphics Processor: GeForce GTX 750 Ti/PCIe/SSE2 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[krdc] [Bug 442348] SSH tunnel is limited to 1 connection at a time
https://bugs.kde.org/show_bug.cgi?id=442348 Luke-Jr changed: What|Removed |Added Resolution|--- |FIXED Status|ASSIGNED|RESOLVED Latest Commit||https://invent.kde.org/netw ||ork/krdc/commit/8111867c479 ||f54138fcd80974cd76b40ec024c ||64 --- Comment #2 from Luke-Jr --- Git commit 8111867c479f54138fcd80974cd76b40ec024c64 by Luke Dashjr. Committed on 13/09/2021 at 18:17. Pushed by aacid into branch 'master'. VncView: Use an ephemeral port for SSH forwarding M +6-7vnc/vncview.cpp https://invent.kde.org/network/krdc/commit/8111867c479f54138fcd80974cd76b40ec024c64 -- You are receiving this mail because: You are watching all bug changes.
[kiofuse] [Bug 442394] New: kio-fuse not mounting smb share if password is remembered
https://bugs.kde.org/show_bug.cgi?id=442394
Bug ID: 442394
Summary: kio-fuse not mounting smb share if password is
remembered
Product: kiofuse
Version: unspecified
Platform: Neon Packages
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: general
Assignee: a.saout...@gmail.com
Reporter: danhernan...@gmail.com
CC: fab...@ritter-vogt.de, kio-bugs-n...@kde.org
Target Milestone: ---
Created attachment 141522
--> https://bugs.kde.org/attachment.cgi?id=141522=edit
.xsession-errors show this when I try to stream a video file in the "already
mounted" smb share but fails to do so
SUMMARY
I'm trying to play video files from my second machine through Samba, when I
connect to it the first time and it asks for my credentials it works. But when
I close dolphin and access it again it doesn't use the fuse mount and so trying
to play it makes mpv crash and vlc handles smb by itself so it asks for
password again.
STEPS TO REPRODUCE
1. Connect to Samba share on Dolphin.
2. Use your credentials.
3. Streaming video works.
4. Close it and connect to the same share again.
5. Streaming video doesn't work.
OBSERVED RESULT
The mount point still exists on
/run/user/{uid}/kio-fuse-{string}/smb/{user:host}/... and I can still access
it, it actually works to stream video. But trying to access it from the Network
section on dolphin only gives you the smb:// url and so streaming doesn't
actually work.
EXPECTED RESULT
Since the mount point still exists, it should still use it and so video
streaming should still work.
SOFTWARE/OS VERSIONS
Windows:
macOS:
Linux/KDE Plasma: KDE Neon 5.22
(available in About System)
KDE Plasma Version: 5.22.5
KDE Frameworks Version: 5.85.0
Qt Version: 5.15.3
ADDITIONAL INFORMATION
If I enable the "Remember password" check on the authentication pop up, it
doesn't work again unless I remove the password from kwallet.
Lastly, if I set the "Default user name" and "Default password" on System
Settings > Network > Settings > Windows Shares, it also never works and
kio-fuse doesn't even run.
--
You are receiving this mail because:
You are watching all bug changes.
[kwin] [Bug 442393] New: Provide script config update signal
https://bugs.kde.org/show_bug.cgi?id=442393 Bug ID: 442393 Summary: Provide script config update signal Product: kwin Version: 5.22.5 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: scripting Assignee: kwin-bugs-n...@kde.org Reporter: m...@genda.life Target Milestone: --- SUMMARY Workspace configChanged signal (https://develop.kde.org/docs/plasma/kwin/api/#signals-1) does not work when script configuration is updated ([Script-] section in ~/.config/kwinrc). ADDITIONAL INFORMATION Without this signal, the user needs to disable the script and enable it again to apply changes to the configuration of KWin script. Providing this signal will improve the user experience, if the developer of the script correctly uses it. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 442392] New: System Time format not set for Gnome apps
https://bugs.kde.org/show_bug.cgi?id=442392 Bug ID: 442392 Summary: System Time format not set for Gnome apps Product: systemsettings Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: kcm_clock Assignee: p...@taniwha.com Reporter: ba...@muldrey.net CC: plasma-b...@kde.org Target Milestone: --- Thunderbird (and many other Gnome apps) query the `org.gnome.desktop.interface` dictionary to get locale info. Latest Thunderbird installed in default Plasma results in display of 24h times rather than the system default 12h setting. See report of issue in TBird bugzilla: https://bugzilla.mozilla.org/show_bug.cgi?id=1726464 STEPS TO REPRODUCE 1. Fresh Plasma (5.22.5) 2. Install Thunderbird from Mozilla download 3. See 24h times 4. Manipulate LC_LOCALE and system settings/ time and date settings 5. Still see 24h times OBSERVED RESULT org.gnome.desktop.interface clock-format is '24h' EXPECTED RESULT Shouldn't KDE set org.gnome.desktop.interface clock-format=12h to reflect system locale and KDE time format preferences? SOFTWARE/OS VERSIONS Linux: 5.13.0 KDE Plasma Version: 5.22.5 KDE Frameworks Version: 5.85.0 Qt Version: 5.13.3 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 442389] Cannot import DNG files from Canon PowerShot SX730 HS
https://bugs.kde.org/show_bug.cgi?id=442389 --- Comment #4 from Maik Qualmann --- I had read the website www.pro-linux.de almost every day, thanks again for that. It was a nice time. ((:-)) Maik -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 442328] Find ffmpeg automatically from PATH
https://bugs.kde.org/show_bug.cgi?id=442328
Know Zero changed:
What|Removed |Added
CC||knowz...@pokemail.net
--- Comment #5 from Know Zero ---
(In reply to healer.harie from comment #3)
> It's strange that you mentioned that it should already work. Was this
> behaviour replicatable in other machine (including linux and macOS) for
> 5.0.0beta1?
>
> I did have krita v4.4.7 in an other Windows machine (long ago), where I've
> added an additional rule of the path of ffmpeg (C:\Program Files\fftools) to
> the environment variable, PATH. The CMD does recognize the `ffmpeg` command,
> but krita don't automatically find it.
>
> I ran krita.com, and tried to open the "Render Animation", the log contained
> like:
> ```
> ...
> Qprocess: Destroyed while process ("C:\\Program Files\\fftools\\ffmpeg.exe")
> is still running.
>
> ```
>
> It seems that somehow, krita knows ffmpeg.exe exist and its location but the
> FFmpeg text box is still empty.
>
> But, if I manually execute ffmpeg.exe (by clicking the ffmpeg executable),
> Krita will eventually fill up the location of ffmpeg and the "Qprocess log"
> stops appearing. It remember this even if I restart Krita again and again,
> but do I restart the computer itself, is when it will be back to normal and
> I had to execute ffmpeg again. This does not solve the problem.
>
> On a side note, I see that proposedPaths is written to some stream
> https://github.com/KDE/krita/blob/fd7ec51dd1e66fc3aa92a6021036fb711ba69003/
> libs/ui/animation/KisFFMpegWrapper.cpp#L365, where could I possibly find
> this file?
It's the timeout issue that should have been fixed in:
https://invent.kde.org/graphics/krita/-/commit/123c302c722376870ed6def5a873b046576882b8
Try the latest nightly build and it should work.
This is a duplicate of:
https://bugs.kde.org/show_bug.cgi?id=441435
--
You are receiving this mail because:
You are watching all bug changes.
[kwin] [Bug 433107] Wayland: iGPU/AMDGPU multi-monitor keeps displaying the SDDM screen if iGPU-DisplayPort is connected
https://bugs.kde.org/show_bug.cgi?id=433107 --- Comment #42 from Zamundaaa --- The commit is only in git master / upcoming 5.23 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 356727] Plasma Panel sometimes disappears with multiple monitors
https://bugs.kde.org/show_bug.cgi?id=356727 --- Comment #44 from jimmie@gmail.com --- Created attachment 141521 --> https://bugs.kde.org/attachment.cgi?id=141521=edit New crash information added by DrKonqi plasmashell (5.22.5) using Qt 5.15.3 - What I was doing when the application crashed: Connected two external displays Bottom panel disappeared from Plasma desktop Used system preferences to reset layout to theme defaults to force panel to reappear - Unusual behavior I noticed: Bottom panel disappeared from Plasma desktop until reset layout -- Backtrace (Reduced): #4 0x7fd0b41a1084 in Plasma::Applet::immutability() const () from /lib/x86_64-linux-gnu/libKF5Plasma.so.5 #5 0x7fd0b41a115d in Plasma::Applet::destroy() () from /lib/x86_64-linux-gnu/libKF5Plasma.so.5 #6 0x7fd0a4097dc8 in SystemTrayContainer::~SystemTrayContainer (this=0x55a128ecb230, __in_chrg=) at /usr/include/c++/9/bits/atomic_base.h:413 #7 0x7fd0a4097e2d in SystemTrayContainer::~SystemTrayContainer (this=0x55a128ecb230, __in_chrg=) at ./applets/systemtray/container/systemtraycontainer.cpp:34 #8 0x7fd0b210ad8e in QObjectPrivate::deleteChildren() () from /lib/x86_64-linux-gnu/libQt5Core.so.5 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 356727] Plasma Panel sometimes disappears with multiple monitors
https://bugs.kde.org/show_bug.cgi?id=356727 jimmie@gmail.com changed: What|Removed |Added CC||jimmie@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 432053] Nvidia Wayland - High CPU Usage
https://bugs.kde.org/show_bug.cgi?id=432053 Michael D changed: What|Removed |Added CC||nortex...@gmail.com --- Comment #1 from Michael D --- I've noticed significantly higher CPU with kwin_wayland over kwin_x11 as well. I'm using AMDGPU (Ryzen 4500U, Renoir). -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 442368] crash after change layer order after transform mask on file layer
https://bugs.kde.org/show_bug.cgi?id=442368 --- Comment #2 from Eoin O'Neill --- Git commit ab1347fd1b40ccdb62a2f3dee448b22de1a53557 by Eoin O'Neill. Committed on 13/09/2021 at 19:42. Pushed by eoinoneill into branch 'master'. Attempt to fix crash on MacOS with transform masks and layer re-ordering. M +5-1plugins/dockers/animation/KisAnimCurvesChannelsModel.cpp https://invent.kde.org/graphics/krita/commit/ab1347fd1b40ccdb62a2f3dee448b22de1a53557 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 442391] New: Kwin crashes after changing animation speed
https://bugs.kde.org/show_bug.cgi?id=442391 Bug ID: 442391 Summary: Kwin crashes after changing animation speed Product: kwin Version: 5.22.5 Platform: Manjaro OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: wayland-generic Assignee: kwin-bugs-n...@kde.org Reporter: nortex...@gmail.com Target Milestone: --- When I try to change the animation speed on the new Quick Settings page of System Settings, the compositor crashes and only the cursor is visible and responds to input. When I reboot (by hard resetting), the new animation speed takes effect. Everything works fine on X11. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 442155] Animation Timeline Docker's Layer toggle icons have no i18n for (on) (off) in their tooltips
https://bugs.kde.org/show_bug.cgi?id=442155 Eoin O'Neill changed: What|Removed |Added CC||eoinoneill1...@gmail.com Status|ASSIGNED|CONFIRMED -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 437025] Remember Timeline Size
https://bugs.kde.org/show_bug.cgi?id=437025 Eoin O'Neill changed: What|Removed |Added Assignee|emmetoneill@gmail.com |eoinoneill1...@gmail.com Status|ASSIGNED|CONFIRMED CC||eoinoneill1...@gmail.com --- Comment #2 from Eoin O'Neill --- If you're talking about the zoom level, I can confirm this is a bug. The zoom level should be saved between launches. Otherwise, the size of the docker isn't resetting on my end. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 440554] [Wayland] Breadcrumb drop down menu "more" item hidden behind panel
https://bugs.kde.org/show_bug.cgi?id=440554 --- Comment #3 from Nate Graham --- Yes. Though if you have Plasma 5.22, you have Neon User, not Neon unstable. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 442390] New: Rendered video in Webm looks like crap
https://bugs.kde.org/show_bug.cgi?id=442390 Bug ID: 442390 Summary: Rendered video in Webm looks like crap Product: kdenlive Version: 21.08.1 Platform: Manjaro OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Video Display & Export Assignee: j...@kdenlive.org Reporter: dkis...@gmail.com Target Milestone: --- SUMMARY render in webm looks like 144p STEPS TO REPRODUCE 1. select video rendering to webm 2. set render quality to maximum 3. start render OBSERVED RESULT rendered video looks like crap EXPECTED RESULT rendered video looks not so bad as render in MP4 SOFTWARE/OS VERSIONS Linux/KDE Plasma: Manjaro Linux (available in About System) KDE Plasma Version: 5.22.5 KDE Frameworks Version: 5.85.0 Qt Version: 5.15.2 -- You are receiving this mail because: You are watching all bug changes.
[kstars] [Bug 404696] Ekos button "Center Telescope Ready"
https://bugs.kde.org/show_bug.cgi?id=404696 --- Comment #2 from Jean-Claude --- Created attachment 141520 --> https://bugs.kde.org/attachment.cgi?id=141520=edit NGC 7331 rotated right I'm attaching 2 screenshots showing that : 1/ the object description is placed at the object location 2/ after a "Rotate Right" the object description is misplaced -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 442368] crash after change layer order after transform mask on file layer
https://bugs.kde.org/show_bug.cgi?id=442368 Eoin O'Neill changed: What|Removed |Added CC||eoinoneill1...@gmail.com --- Comment #1 from Eoin O'Neill --- Hey Ivan, Did you happen to have the animation curves docker open when editing the document? I would like to know simply for the sake of making sure that the curves docker isn't adding overhead where it isn't needed. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 413165] Please add option to reduce screen brightness in kcm_nightcolor
https://bugs.kde.org/show_bug.cgi?id=413165 Marcos Dione changed: What|Removed |Added CC||mdi...@grulic.org.ar --- Comment #8 from Marcos Dione --- workaround so far: * deactivate night color. * run the following $ redshift -v -b 1:.75 -l LAT:LON -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 441584] The "/" and "/home" directories show up with the device name instead of the path
https://bugs.kde.org/show_bug.cgi?id=441584 Nate Graham changed: What|Removed |Added CC||n...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 418502] better handling of external monitor brightness.
https://bugs.kde.org/show_bug.cgi?id=418502 --- Comment #2 from Marcos Dione --- > but the color temperature is totally off (too much blue...) I think what happens here is that redshift gets disabled. > that KCM_Nightcolor doesn't change the screen brightness yet AFAIK, but the > color tone Then this becomes a dupe of #413165? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 378694] Kicker's sub-menus are covered up by Plasma panels
https://bugs.kde.org/show_bug.cgi?id=378694 Andrey changed: What|Removed |Added Latest Commit||https://invent.kde.org/plas ||ma/kwin/commit/8de4f9e6995b ||346dc81292e82afe8b8b1d7ce51 ||d Resolution|--- |FIXED Status|CONFIRMED |RESOLVED --- Comment #39 from Andrey --- Git commit 8de4f9e6995b346dc81292e82afe8b8b1d7ce51d by Andrey Butirsky. Committed on 13/09/2021 at 19:03. Pushed by butirsky into branch 'beneath_menus'. fix: Kicker's sub-menus are covered up by Plasma panels M +2-0src/abstract_client.cpp https://invent.kde.org/plasma/kwin/commit/8de4f9e6995b346dc81292e82afe8b8b1d7ce51d -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 442189] HEIC photos with GPS coordinates embeded in metadata are not used in digikam database for geolocation
https://bugs.kde.org/show_bug.cgi?id=442189 --- Comment #10 from Francisco Hurtado --- (In reply to Maik Qualmann from comment #9) > There will be no fix or workaround if the cause is that you added the HEIC > images before digiKam could support the metadata. > > Go to the search in the left sidebar, enter "heic" in the quick search at > the top. All of your HEIC images should now be displayed, depending on the > number, it may take a while. Select them all, select the option to reread > the metadata from the item menu. > > There is also the maintenance tool, where you can also read the image > metadata again. > > Maik Thanks Maik. I hope you found the traces useful. All the best -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 441584] The "/" and "/home" directories show up with the device name instead of the path
https://bugs.kde.org/show_bug.cgi?id=441584 --- Comment #4 from Bug Janitor Service --- A possibly relevant merge request was started @ https://invent.kde.org/frameworks/kio/-/merge_requests/582 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 442389] Cannot import DNG files from Canon PowerShot SX730 HS
https://bugs.kde.org/show_bug.cgi?id=442389 --- Comment #3 from Maik Qualmann --- Here from the CHDK porting thread to the camera, the DNG support is not perfect either: - DNG color matrix is incorrect (copied from sx60hs) but usable Maik -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 442389] Cannot import DNG files from Canon PowerShot SX730 HS
https://bugs.kde.org/show_bug.cgi?id=442389 Maik Qualmann changed: What|Removed |Added Version Fixed In||7.4.0 Status|REPORTED|RESOLVED Resolution|--- |UNMAINTAINED --- Comment #2 from Maik Qualmann --- Ah, now I see that you have installed CHDK. So the camera even has DNG in the standard firmware. Sorry, we can't offer any support for that and GPhoto2 probably won't do it either. Maik -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 442389] Cannot import DNG files from Canon PowerShot SX730 HS
https://bugs.kde.org/show_bug.cgi?id=442389 Maik Qualmann changed: What|Removed |Added CC||metzping...@gmail.com --- Comment #1 from Maik Qualmann --- If the DNG files are not listed by GPhoto2, it is a GPhoto2 or camera problem. Can you switch between MTP <=> PTP mode in the camera USB settings? Maik -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 435415] On NixOS, notifications, OSDs, and KRunner appear in task manager and steal focus
https://bugs.kde.org/show_bug.cgi?id=435415 André M changed: What|Removed |Added CC||andre.vma...@gmail.com --- Comment #12 from André M --- I can confirm this bug on NixOS, latest plasma5 5.22.5 & kf5.86. Interesting is that, even adding a very broad KWin rule for any type of window with Window class containing a substring of "org.kde.plasmashell" (detected properties) and forcing it to Skip taskbar and Extreme Window focus stealing prevention doesn't work, notifications still show up in taskbar and focus is stolen. Only on Wayland. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 442389] New: Cannot import DNG files from Canon PowerShot SX730 HS
https://bugs.kde.org/show_bug.cgi?id=442389 Bug ID: 442389 Summary: Cannot import DNG files from Canon PowerShot SX730 HS Product: digikam Version: 7.3.0 Platform: Debian stable OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Import-Gphoto2 Assignee: digikam-bugs-n...@kde.org Reporter: h...@pro-linux.de Target Milestone: --- Just upgraded to 7.3.0, using AppImage. I have a new Canon PowerShot SX730 HS, installed CHDK on it and set image format to JPEG and DNG. This works well with my old PowerShot A3300 IS, but with the new cam I only see the JPEG images in the import window. While the CHDK file manager confirms that the DNG files are there, I cannot see them with gphoto either: LANG= gphoto2 -L There is no file in folder '/'. There is no file in folder '/store_00010001'. There is no file in folder '/store_00010001/DCIM'. There are 7 files in folder '/store_00010001/DCIM/100___09'. #1 IMG_0001.JPG rd 6389 KB image/jpeg #2 IMG_0002.JPG rd 6672 KB image/jpeg #3 IMG_0003.JPG rd 6109 KB image/jpeg #4 IMG_0004.JPG rd 6225 KB image/jpeg #5 IMG_0005.JPG rd 6306 KB image/jpeg #6 IMG_0006.JPG rd 6616 KB image/jpeg #7 IMG_0007.JPG rd 5836 KB image/jpeg So the real problem may be ghpoto2. Can you add support for the cam? Is there a quick workaround? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 433107] Wayland: iGPU/AMDGPU multi-monitor keeps displaying the SDDM screen if iGPU-DisplayPort is connected
https://bugs.kde.org/show_bug.cgi?id=433107 --- Comment #41 from Andrew Ammerlaan --- Created attachment 141519 --> https://bugs.kde.org/attachment.cgi?id=141519=edit wayland-session-log-kwin-5.22.5 After upgrading to version 5.22.5 this is sadly still not quite working (though it was working earlier when I tested the MR). The monitor connected to the AMDGPU works and one of the monitors on the iGPU (the right one). But the others still continue to show the SDDM screen after logging in. Wayland log attached. I'm seeing a bunch of these: kwin_core: Provided presentation timestamp is invalid: 154666 (current: 154675) kwin_wayland_drm: Atomic request failed to commit: Invalid argument kwin_wayland_drm: Atomic test commit failed. Aborting present. Furthermore, the issue where the monitor on the AMDGPU turns black for about a second or two after logging in is back :( -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 441610] when switching virtual desktops on OpenBox, konsole windows revert to their default sizes
https://bugs.kde.org/show_bug.cgi?id=441610 --- Comment #9 from Ahmad Samir --- They are two separate issues, the window is resized when it's minimized then shown; and the toolbars interfere with the window size hint (IIRC). -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 441610] when switching virtual desktops on OpenBox, konsole windows revert to their default sizes
https://bugs.kde.org/show_bug.cgi?id=441610 --- Comment #8 from Michael Konieczny --- > As for the toolbars, that is due to the too-long text on them, try hiding the > text. I can hide text, I can disable toolbars completely, but when before mimimization there was some layout, even with ellipsized toolbars, it should be retained on restore. -- You are receiving this mail because: You are watching all bug changes.
[kstars] [Bug 410669] KStars High CPU macOS
https://bugs.kde.org/show_bug.cgi?id=410669 --- Comment #8 from mountainai...@outlook.com --- FWIW, I haven't had high CPU issues in KStars for quite a while now. However, the last time I used it on the Mac for an actual imaging session was probably 3.5.3 (I moved to Ubuntu). -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 441610] when switching virtual desktops on OpenBox, konsole windows revert to their default sizes
https://bugs.kde.org/show_bug.cgi?id=441610 --- Comment #7 from Ahmad Samir --- It's the same bug, depends on when a showevent is invoked. As for the toolbars, that is due to the too-long text on them, try hiding the text. -- You are receiving this mail because: You are watching all bug changes.
[korganizer] [Bug 442364] KOrganizer does not print all participants of a task
https://bugs.kde.org/show_bug.cgi?id=442364 gjditchfi...@acm.org changed: What|Removed |Added CC||gjditchfi...@acm.org Ever confirmed|0 |1 Status|REPORTED|CONFIRMED -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 441610] when switching virtual desktops on OpenBox, konsole windows revert to their default sizes
https://bugs.kde.org/show_bug.cgi?id=441610 --- Comment #6 from Michael Konieczny --- Bug 442388 was marked as duplicate, and it mainly is, but there's one more detail - restored size depends on selected toolbars, with screen recording how it looks like. And no OpenBox, just Plasma. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 441610] when switching virtual desktops on OpenBox, konsole windows revert to their default sizes
https://bugs.kde.org/show_bug.cgi?id=441610 Ahmad Samir changed: What|Removed |Added CC||k...@bh.m5k8.net --- Comment #5 from Ahmad Samir --- *** Bug 442388 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 442388] Unexpected window resize after minimization/restore
https://bugs.kde.org/show_bug.cgi?id=442388 Ahmad Samir changed: What|Removed |Added Status|REPORTED|RESOLVED CC||a.samir...@gmail.com Resolution|--- |DUPLICATE --- Comment #1 from Ahmad Samir --- Already fixed in 21.08 stable branch, but the commit didn't catch the tagging of 21.08.1. *** This bug has been marked as a duplicate of bug 441610 *** -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 442388] Unexpected window resize after minimization/restore
https://bugs.kde.org/show_bug.cgi?id=442388 Michael Konieczny changed: What|Removed |Added Platform|Other |Archlinux Packages -- You are receiving this mail because: You are watching all bug changes.
