[systemsettings] [Bug 456321] Inactive window titlebar not colored with the setting turned on
https://bugs.kde.org/show_bug.cgi?id=456321 --- Comment #9 from linuxatemy...@protonmail.com --- Created attachment 150747 --> https://bugs.kde.org/attachment.cgi?id=150747=edit Breeze Light color scheme with custom accent settings -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 356727] Panel sometimes disappears on hotplug/re-plug/sleep/wake
https://bugs.kde.org/show_bug.cgi?id=356727 Corentin Fleury changed: What|Removed |Added CC||fleury.coren...@outlook.fr --- Comment #74 from Corentin Fleury --- (In reply to Nate Graham from comment #73) > That's a shame. It seems like the issue you were reporting is pretty much > the same thing, so we may have to re-open this. > > Is anyone else still experiencing the issue after upgrading to Plasma 5.24? I can confirm the issue in Plasma 5.25.3. After unplugging a projector, my panel completely disappeared and I couldn't bring it back. -- You are receiving this mail because: You are watching all bug changes.
[xdg-desktop-portal-kde] [Bug 451240] Screen/Window selection dialog reacts poorly to double click
https://bugs.kde.org/show_bug.cgi?id=451240 --- Comment #4 from Aleix Pol --- So I've investigated this and found out the issue. The problem is that we are using onClicked because onToggled isn't available. As we can see on AbstractListItem.qml: //NOTE: This must stay at 2.0 until KF6 due to retrocompatibility of the "icon" property import QtQuick.Templates 2.0 as T2 And with onClicked we have less control over how to react to double clicks which means we just do it poorly. I will try and see what would be a good compromise for the moment. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 456803] Plasma crashes after screen inactivity
https://bugs.kde.org/show_bug.cgi?id=456803 Alfonso Murolo changed: What|Removed |Added Resolution|WAITINGFORINFO |BACKTRACE --- Comment #4 from Alfonso Murolo --- (In reply to Nate Graham from comment #3) > If it's not crashing, what is it doing? I'd say it's a good question :-) I will try to replicate the crash behaviour where I get the crash dialog too. In that case, the hard reset is not necessary and I am able to get back to the desktop with a crashed plasmashell and a crash dialog welcoming me. Plasma is gone, but will eventually restart and so the session is recovered. In this other case which just happened, the logs in journalctl are all I am able to find for now of what is happening. Is there some other log which is plasma specific which I could browse? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 456884] Add Ability to set "New tasks appear" to the top or bottom when using a vertical panel
https://bugs.kde.org/show_bug.cgi?id=456884 Nate Graham changed: What|Removed |Added Status|REPORTED|CONFIRMED CC||n...@kde.org Ever confirmed|0 |1 --- Comment #1 from Nate Graham --- In https://invent.kde.org/plasma/plasma-desktop/-/merge_requests/738, I don't see an explanation for why this option is only available when using a horizontal panel, so sure, we can do that. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 456385] Plasma crashes in PanelView::resizePanel() or rearranges Task Manager Tasks when system goes from 1 output to 0 and then back to 1
https://bugs.kde.org/show_bug.cgi?id=456385 Nate Graham changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=456743 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 456743] With only 1 screen, plasmashell crashed in ScreenPool::handleScreenAdded() on wakeup from sleep
https://bugs.kde.org/show_bug.cgi?id=456743 Nate Graham changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=456385 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 456385] Plasma crashes in PanelView::resizePanel() or rearranges Task Manager Tasks when system goes from 1 output to 0 and then back to 1
https://bugs.kde.org/show_bug.cgi?id=456385 Nate Graham changed: What|Removed |Added Component|Panel |Multi-screen support -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 411305] Languages selected in systemsettings should update accountsservice's org.freedesktop.Accounts.User.Language
https://bugs.kde.org/show_bug.cgi?id=411305 Nate Graham changed: What|Removed |Added Summary|Languages selected in |Languages selected in |systemsettings do not |systemsettings should |update accountsservice's|update accountsservice's |org.freedesktop.Accounts.Us |org.freedesktop.Accounts.Us |er.Language |er.Language Severity|normal |wishlist -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 341236] Not all languages have the same capitalization
https://bugs.kde.org/show_bug.cgi?id=341236 Nate Graham changed: What|Removed |Added Status|CONFIRMED |RESOLVED Resolution|--- |UPSTREAM --- Comment #4 from Nate Graham --- >From the Qt bug report: > There is no discrimination: language names in Russian begin with a lowercase > letter. "Russian" is "русский", > "English" is "английский". That means that sometimes beginning with a lowercase letter is intentional and correct, which means we can't work around the issue on our end by blindly capitalizing the first letter. It will have to be fixed upstream to capitalize the first letter of the languages that should be capitalized in the system's current language, but currently aren't. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 456745] Task Manager tcons go to second row when using a size-constrained floating panel
https://bugs.kde.org/show_bug.cgi?id=456745 Nate Graham changed: What|Removed |Added Resolution|WAITINGFORINFO |--- Status|NEEDSINFO |REPORTED Summary|Icons go to second row when |Task Manager tcons go to |using a floating panel |second row when using a ||size-constrained floating ||panel -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 454349] Mouse hover selection in search result persists across kickoff openings
https://bugs.kde.org/show_bug.cgi?id=454349 Nate Graham changed: What|Removed |Added Summary|Searching for something |Mouse hover selection in |automatically selects the |search result persists |second item instead of the |across kickoff openings |first | --- Comment #10 from Nate Graham --- I can reproduce that 100%! -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 440123] Dolphin complains of not enough disk space
https://bugs.kde.org/show_bug.cgi?id=440123 brandon.coo...@disroot.org changed: What|Removed |Added CC||brandon.coo...@disroot.org -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 455809] Option "Make window titlebars accent-colored" is slightly inaccurate when applied to header-color-using color schemes
https://bugs.kde.org/show_bug.cgi?id=455809 --- Comment #3 from Mircea Kitsune --- Playing with color schemes in 5.25.3 to figure this out, I noticed there are two problems which are unclear to the end user: 1. What exactly is the header color? In the color scheme editor there is a Header category like all others (eg: Tooltip) with multiple colors. Which one does what in terms of colorization and acts as the trigger? 2. What does it mean for the header color to be defined or undefined by the color scheme? Every color has an implicit value, you can't erase a definition from the menu. Does not defined mean setting the color to black? This doesn't seem to be the case as color schemes with opposite behaviors all have a color other than fully black or white so something else must be determining it. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 456321] Inactive window titlebar not colored with the setting turned on
https://bugs.kde.org/show_bug.cgi?id=456321 --- Comment #8 from Nate Graham --- Thanks. Cannot reproduce in current git master. Can you attach your custom color scheme file? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 456723] Laptop wakes up to a completely black screen after every suspend on wayland
https://bugs.kde.org/show_bug.cgi?id=456723 --- Comment #14 from Kalzi --- (In reply to Zamundaaa from comment #13) > You can test quite easily if powertop is at fault by not executing it. Any > problems caused by it should also happen on Xorg though... > In the log you attached there is still no warnings or anything useful. > > The next thing to check would thus be if this also happens with other > Wayland compositors. Easiest to test is usually Weston; after installing it > you can use it by choosing it in the bottom left of the login screen as an > alternative to Plasma X11 / Wayland OK, I installed Weston from the Manjaro repos, and it gave me a very basic "desktop" that has nothing but time and date on the top right and terminal icon on the top left. Nothing is clickable. Right click doesn't work. Touchpad doesn't work either. Add to that my 4k display, which made the whole display so tiny. Unless, you have a specific version of weston that has a complete different interface, I don't know -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 456926] Program crash when deleting a tag while new items are being scanned
https://bugs.kde.org/show_bug.cgi?id=456926 caulier.gil...@gmail.com changed: What|Removed |Added CC||caulier.gil...@gmail.com Platform|Other |Microsoft Windows -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 456926] Program crash when deleting a tag while new items are being scanned
https://bugs.kde.org/show_bug.cgi?id=456926 Arnon Meshoulam changed: What|Removed |Added Version|unspecified |7.7.0 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 456926] New: Program crash when deleting a tag while new items are being scanned
https://bugs.kde.org/show_bug.cgi?id=456926 Bug ID: 456926 Summary: Program crash when deleting a tag while new items are being scanned Product: digikam Version: unspecified Platform: Other OS: Microsoft Windows Status: REPORTED Severity: crash Priority: NOR Component: Tags-Manager Assignee: digikam-bugs-n...@kde.org Reporter: arnon.meshou...@gmail.com Target Milestone: --- Created attachment 150746 --> https://bugs.kde.org/attachment.cgi?id=150746=edit Crashlog - 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. Add new content 2. While scan to add new items is still executing, select a tag and delete it 3. Confirm that you want to delete the tag OBSERVED RESULT Program crashes EXPECTED RESULT Tag deleted SOFTWARE/OS VERSIONS Windows: Windows 11 Qt Version: ADDITIONAL INFORMATION Crashlog shows an assert -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 456803] Plasma crashes after screen inactivity
https://bugs.kde.org/show_bug.cgi?id=456803 Nate Graham changed: What|Removed |Added Resolution|BACKTRACE |WAITINGFORINFO --- Comment #3 from Nate Graham --- If it's not crashing, what is it doing? -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 456321] Inactive window titlebar not colored with the setting turned on
https://bugs.kde.org/show_bug.cgi?id=456321 --- Comment #7 from linuxatemy...@protonmail.com --- And if I uncheck the inactive titlebar color setting, save and apply, the tiltebar color look exactly the same, which is why I think the feature is not workin? https://imgur.com/JuzKiu0 -- You are receiving this mail because: You are watching all bug changes.
[kcalc] [Bug 453534] kcalc process always takes nearly 100% of a CPU thread when it's running
https://bugs.kde.org/show_bug.cgi?id=453534 Ryan Ronnander changed: What|Removed |Added CC||rronnan...@gmail.com --- Comment #8 from Ryan Ronnander --- (In reply to roger.koot from comment #5) > If you resize the kcalc window, the cpu usage drops to expected values. Wow, this actually works, but upon closing and reopening kcalc, the behavior resumes until resized. I cannot reproduce this on other KDE systems. The menu rapidly flickers when this bug occurs, as if some redraw event is constantly being executed until the window is resized. I believe I've tried this on both X11 and Wayland, both hit 100% CPU usage. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 456925] New: Bogus memory allocation size -- embedded pdf not shown/white page
https://bugs.kde.org/show_bug.cgi?id=456925 Bug ID: 456925 Summary: Bogus memory allocation size -- embedded pdf not shown/white page Product: okular Version: 22.04.3 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: major Priority: NOR Component: PDF backend Assignee: okular-de...@kde.org Reporter: florian.streib...@gmail.com Target Milestone: --- Created attachment 150745 --> https://bugs.kde.org/attachment.cgi?id=150745=edit pdf file not being displayed SUMMARY I have a figure that is included in a pdf using LaTeX beamer. The figure is not shown in the presentation. When openened directly the page is empty and also no content shown. On the console opening the pdf directly or scrolling to the page where it is embedded yields 'Bogus memory allocation size' STEPS TO REPRODUCE 1. open the attached pdf OBSERVED RESULT a blank page is displayed, an error printed on the console EXPECTED RESULT showing the content of the pdf, like all other pdf viewers I tried to, e.g. xpdf, evince, even converting to png. ADDITIONAL INFO I am assuming this to be different from #404526 -- not building manually, using Arch, until now all other pdfs work just fine. $ pdfinfo eco_middle.pdf Producer:cairo 1.16.0 (https://cairographics.org) CreationDate:Tue Feb 5 20:53:09 2019 CET Custom Metadata: no Metadata Stream: no Tagged: no UserProperties: no Suspects:no Form:none JavaScript: no Pages: 1 Encrypted: no Page size: 720 x 405 pts Page rot:0 File size: 366672 bytes Optimized: no PDF version: 1.5 -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 399695] 2 occurrences of "anniversary"
https://bugs.kde.org/show_bug.cgi?id=399695 gjditchfi...@acm.org changed: What|Removed |Added Status|REPORTED|RESOLVED Version Fixed In||5.20.3 Resolution|--- |FIXED --- Comment #10 from gjditchfi...@acm.org --- I'm glad to hear that. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 456803] Plasma crashes after screen inactivity
https://bugs.kde.org/show_bug.cgi?id=456803 --- Comment #2 from Alfonso Murolo --- Hi Nate, thanks for the instructions. It just happened again (I could also replicate it by let it lock for inactivity and turn off the screens directly) and I had prepared my distro to get a dump with debug symbols. Sadly, it seems that it is not just "crashing" - plasmashell is still alive, printing those errors to journalctl until I hard reset. Exactly the same ones i wrote before. Is there a way I can provide more info even if plasmashell does not exactly 'crash' all the time such as in this case? Other times, I am able to see the actual crash if I manage to log back in and plasmashell is gone - I see the crash dialog and so on. As soon as I manage to replicate that, I will look to retrieve a trace with coredumpctl (I have a whole bunch of those in the list from the recent past, but I am not sure anymore if they are from an event I am describing in this issue or something else). -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 414896] Opening certain emails reliably crashes KMail
https://bugs.kde.org/show_bug.cgi?id=414896 --- Comment #3 from Andreas Beyer --- Created attachment 150744 --> https://bugs.kde.org/attachment.cgi?id=150744=edit New crash information added by DrKonqi kmail (5.20.3 (22.04.3)) using Qt 5.15.5 When loading a web.de Mail, KMail crashes constantly. Nothing special done before. Open KMail, want to read or delete the Mail, KMail crashes only on this special (Web.de Junk-) Mail. Regards. -- Backtrace (Reduced): #7 0x7f1e63a99833 in __gnu_cxx::__verbose_terminate_handler() () at /usr/src/debug/gcc/libstdc++-v3/libsupc++/vterminate.cc:95 #8 0x7f1e63aa5bfc in __cxxabiv1::__terminate(void (*)()) (handler=) at /usr/src/debug/gcc/libstdc++-v3/libsupc++/eh_terminate.cc:48 #9 0x7f1e63aa4bba in __cxa_call_terminate(_Unwind_Exception*) (ue_header=0x5580600952a0) at /usr/src/debug/gcc/libstdc++-v3/libsupc++/eh_call.cc:54 #10 0x7f1e63aa533a in __cxxabiv1::__gxx_personality_v0(int, _Unwind_Action, _Unwind_Exception_Class, _Unwind_Exception*, _Unwind_Context*) (version=, actions=6, exception_class=5138137972254386944, ue_header=, context=0x7ffe65fe98a0) at /usr/src/debug/gcc/libstdc++-v3/libsupc++/eh_personality.cc:688 #11 0x7f1e6d2f8774 in _Unwind_RaiseException_Phase2 (exc=0x5580600952a0, context=0x7ffe65fe98a0, frames_p=0x7ffe65fe9990) at /usr/src/debug/gcc/libgcc/unwind.inc:64 -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 414896] Opening certain emails reliably crashes KMail
https://bugs.kde.org/show_bug.cgi?id=414896 Andreas Beyer changed: What|Removed |Added CC||andreas.be...@mailbox.org -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 456321] Inactive window titlebar not colored with the setting turned on
https://bugs.kde.org/show_bug.cgi?id=456321 --- Comment #6 from linuxatemy...@protonmail.com --- Ive attached it above. The color scheme is copy of Breeze Light, I renamed it Breeze Light Alt, applied the color settings to it and saved, then hit apply. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 456321] Inactive window titlebar not colored with the setting turned on
https://bugs.kde.org/show_bug.cgi?id=456321 --- Comment #5 from linuxatemy...@protonmail.com --- Created attachment 150743 --> https://bugs.kde.org/attachment.cgi?id=150743=edit inactive titlebar color -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 456076] Size of icons backgrounds in Task Manager became bigger in 5.25
https://bugs.kde.org/show_bug.cgi?id=456076 Nate Graham changed: What|Removed |Added CC||dieseltr...@gmail.com --- Comment #3 from Nate Graham --- *** Bug 455618 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 455618] Panels now ignore Font DPI on X11 with Plasma scaling
https://bugs.kde.org/show_bug.cgi?id=455618 Nate Graham changed: What|Removed |Added Resolution|WAITINGFORINFO |DUPLICATE Status|NEEDSINFO |RESOLVED --- Comment #22 from Nate Graham --- > So yes icons do resize on both 5.24 and 5.25 but I think the MAX size is > being capped sooner on 5.25. Yeah, and that was an intentional change in Plasma 5.25, which makes this a duplicate of Bug 456076. *** This bug has been marked as a duplicate of bug 456076 *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 456076] Size of icons backgrounds in Task Manager became bigger in 5.25
https://bugs.kde.org/show_bug.cgi?id=456076 Nate Graham changed: What|Removed |Added Summary|Height (size) of icons in |Size of icons backgrounds |vertical Icons-only Task|in Task Manager became |Manager became bigger in|bigger in 5.25 |5.25| -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 456924] New: Lattedock Crashes when trying to Add Widgets
https://bugs.kde.org/show_bug.cgi?id=456924 Bug ID: 456924 Summary: Lattedock Crashes when trying to Add Widgets Product: lattedock Version: 0.10.8 Platform: Ubuntu Packages OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: application Assignee: mvourla...@gmail.com Reporter: bubtot...@gmail.com Target Milestone: --- Application: latte-dock (0.10.8) Qt Version: 5.15.3 Frameworks Version: 5.95.0 Operating System: Linux 5.15.0-41-generic x86_64 Windowing System: X11 Distribution: Ubuntu 22.04 LTS DrKonqi: 5.24.5 [KCrashBackend] -- Information about the crash: - What I was doing when the application crashed: Trying to navigate (scroll or search) the list of widgets after right-clicking on a dock and selecting "Add widget". Does not occur the first time I do this after system reboot, but happens every subsequent time. The crash can be reproduced every time. -- Backtrace: Application: Latte Dock (latte-dock), signal: Segmentation fault [KCrash Handler] #4 0x7f48060eead4 in QSGTexture::setFiltering(QSGTexture::Filtering) () from /lib/x86_64-linux-gnu/libQt5Quick.so.5 #5 0x7f480611f7af in QSGOpaqueTextureMaterialShader::updateState(QSGMaterialShader::RenderState const&, QSGMaterial*, QSGMaterial*) () from /lib/x86_64-linux-gnu/libQt5Quick.so.5 #6 0x7f48061063dc in QSGBatchRenderer::Renderer::renderMergedBatch(QSGBatchRenderer::Batch const*) () from /lib/x86_64-linux-gnu/libQt5Quick.so.5 #7 0x7f480610b965 in QSGBatchRenderer::Renderer::renderBatches() () from /lib/x86_64-linux-gnu/libQt5Quick.so.5 #8 0x7f480610c352 in QSGBatchRenderer::Renderer::render() () from /lib/x86_64-linux-gnu/libQt5Quick.so.5 #9 0x7f48060f3924 in QSGRenderer::renderScene(QSGBindable const&) () from /lib/x86_64-linux-gnu/libQt5Quick.so.5 #10 0x7f4806161d32 in QSGOpenGLLayer::grab() () from /lib/x86_64-linux-gnu/libQt5Quick.so.5 #11 0x7f4806162355 in QSGOpenGLLayer::updateTexture() () from /lib/x86_64-linux-gnu/libQt5Quick.so.5 #12 0x7f48062cfcb6 in QQuickOpenGLShaderEffectMaterial::updateTextures() const () from /lib/x86_64-linux-gnu/libQt5Quick.so.5 #13 0x7f48060f40a4 in QSGRenderer::preprocess() () from /lib/x86_64-linux-gnu/libQt5Quick.so.5 #14 0x7f48060f38eb in QSGRenderer::renderScene(QSGBindable const&) () from /lib/x86_64-linux-gnu/libQt5Quick.so.5 #15 0x7f4806161d32 in QSGOpenGLLayer::grab() () from /lib/x86_64-linux-gnu/libQt5Quick.so.5 #16 0x7f4806162355 in QSGOpenGLLayer::updateTexture() () from /lib/x86_64-linux-gnu/libQt5Quick.so.5 #17 0x7f48062cfcb6 in QQuickOpenGLShaderEffectMaterial::updateTextures() const () from /lib/x86_64-linux-gnu/libQt5Quick.so.5 #18 0x7f48060f40a4 in QSGRenderer::preprocess() () from /lib/x86_64-linux-gnu/libQt5Quick.so.5 #19 0x7f48060f38eb in QSGRenderer::renderScene(QSGBindable const&) () from /lib/x86_64-linux-gnu/libQt5Quick.so.5 #20 0x7f48060f3df3 in QSGRenderer::renderScene(unsigned int) () from /lib/x86_64-linux-gnu/libQt5Quick.so.5 #21 0x7f4806159a47 in QSGDefaultRenderContext::renderNextFrame(QSGRenderer*, unsigned int) () from /lib/x86_64-linux-gnu/libQt5Quick.so.5 #22 0x7f48061c95f9 in QQuickWindowPrivate::renderSceneGraph(QSize const&, QSize const&) () from /lib/x86_64-linux-gnu/libQt5Quick.so.5 #23 0x7f480616845d in ?? () from /lib/x86_64-linux-gnu/libQt5Quick.so.5 #24 0x7f4806168e07 in ?? () from /lib/x86_64-linux-gnu/libQt5Quick.so.5 #25 0x7f4804023ca1 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #26 0x7f4803aaeb43 in start_thread (arg=) at ./nptl/pthread_create.c:442 #27 0x7f4803b40a00 in clone3 () at ../sysdeps/unix/sysv/linux/x86_64/clone3.S:81 Thread 7 (Thread 0x7f47d5283640 (LWP 5416) "QSGRenderThread"): #1 __futex_abstimed_wait_common (cancel=true, private=0, abstime=0x0, clockid=0, expected=0, futex_word=0x564648a2a940) at ./nptl/futex-internal.c:87 #2 __GI___futex_abstimed_wait_cancelable64 (futex_word=futex_word@entry=0x564648a2a940, expected=expected@entry=0, clockid=clockid@entry=0, abstime=abstime@entry=0x0, private=private@entry=0) at ./nptl/futex-internal.c:139 #3 0x7f4803aadac1 in __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x564648a2a8f0, cond=0x564648a2a918) at ./nptl/pthread_cond_wait.c:503 #4 ___pthread_cond_wait (cond=0x564648a2a918, mutex=0x564648a2a8f0) at ./nptl/pthread_cond_wait.c:627 #5 0x7f4804029ceb in QWaitCondition::wait(QMutex*, QDeadlineTimer) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7f48061669c3 in ?? () from /lib/x86_64-linux-gnu/libQt5Quick.so.5 #7 0x7f4806168e49 in ?? () from /lib/x86_64-linux-gnu/libQt5Quick.so.5 #8 0x7f4804023ca1 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #9 0x7f4803aaeb43 in start_thread (arg=) at ./nptl/pthread_create.c:442 #10 0x7f4803b40a00 in clone3 () at
[plasmashell] [Bug 456848] With an auto-hidden panel, when the blue glow effect appears, activating a widget on the still-hidden panel using a keyboard shortcut causes the blue glow effect to remain v
https://bugs.kde.org/show_bug.cgi?id=456848 Nate Graham changed: What|Removed |Added Ever confirmed|0 |1 CC||n...@kde.org Status|REPORTED|CONFIRMED Severity|normal |minor Summary|Blue glow gets stuck|With an auto-hidden panel, ||when the blue glow effect ||appears, activating a ||widget on the still-hidden ||panel using a keyboard ||shortcut causes the blue ||glow effect to remain ||visible and cover the ||now-shown panel --- Comment #2 from Nate Graham --- Can reproduce both manifestations of the issue. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 450582] Some change between 5.24.0 and 5.24.1 broke windows shade/shutter feature
https://bugs.kde.org/show_bug.cgi?id=450582 --- Comment #35 from Hans-Peter Jansen --- @Duncan: nice sum up. Of course, we also need to take session management into account. The X11 protocol does provide the shaded flag for this task. I even hacked a related tool to handle my firefox setup. FF failed to handle the geometry and shaded state for some time: https://github.com/frispete/wm-win-tool -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 456822] LibreOffice writer doesn't mark when there's more than one window opened
https://bugs.kde.org/show_bug.cgi?id=456822 Nate Graham changed: What|Removed |Added Status|RESOLVED|CLOSED --- Comment #3 from Nate Graham --- I can't reproduce that; when I open multiple LibreOffice windows, they are correctly grouped and marked with a plus sign. Hence, "sometimes" in the title of the duplicated bug report. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 341236] Not all languages have the same capitalization
https://bugs.kde.org/show_bug.cgi?id=341236 Nate Graham changed: What|Removed |Added URL||https://bugreports.qt.io/br ||owse/QTBUG-91355 --- Comment #3 from Nate Graham --- It seems that this is an issue in Unicode CLDR; see https://bugreports.qt.io/browse/QTBUG-91355?focusedCommentId=641357=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-641357 We might be able to work around it in our code though. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 305136] File associations are broken in gtk/glib apps
https://bugs.kde.org/show_bug.cgi?id=305136 --- Comment #20 from Ilya Fedin --- KCM will do something only when changing the settings, yeah? It already does that afaik. The problem is with the default associations. KDE uses custom InitialPreference key in desktop files while it should provide /usr/share/applications/kde-mimeapps.list with all default preferences instead to be compliant with the XDG spec. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 455021] Tooltip with black window preview when I hover over a task on Wayland
https://bugs.kde.org/show_bug.cgi?id=455021 Nate Graham changed: What|Removed |Added CC||anditosan1...@gmail.com --- Comment #3 from Nate Graham --- *** Bug 456881 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 456881] Window thumbnails are black
https://bugs.kde.org/show_bug.cgi?id=456881 Nate Graham changed: What|Removed |Added Resolution|WAITINGFORINFO |DUPLICATE Status|NEEDSINFO |RESOLVED --- Comment #3 from Nate Graham --- *** This bug has been marked as a duplicate of bug 455021 *** -- You are receiving this mail because: You are watching all bug changes.
[kolourpaint] [Bug 456888] Duplicate shortcut keys in tooltips
https://bugs.kde.org/show_bug.cgi?id=456888 Nate Graham changed: What|Removed |Added Severity|normal |minor Ever confirmed|0 |1 CC||fe.a.er...@gmail.com Status|REPORTED|CONFIRMED --- Comment #1 from Nate Graham --- Can reproduce. Might be an issue in the common tooltip code, or might be an issue in how Kolourpaint assigns shortcuts. CCing Felix Ernst, who is much more knowledgeable about this than I am. -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 456891] Improve icon contrast for more color options in dark theme
https://bugs.kde.org/show_bug.cgi?id=456891 Nate Graham changed: What|Removed |Added Resolution|--- |UPSTREAM Status|REPORTED|RESOLVED --- Comment #1 from Nate Graham --- This UI comes from the 3rd-party KImageAnnotator library; you'll have to report it at https://github.com/ksnip/kImageAnnotator/issues -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 456892] Add tooltip to more color options icon
https://bugs.kde.org/show_bug.cgi?id=456892 Nate Graham changed: What|Removed |Added Resolution|--- |UPSTREAM Status|REPORTED|RESOLVED --- Comment #1 from Nate Graham --- This UI comes from the 3rd-party KImageAnnotator library; you'll have to report it at https://github.com/ksnip/kImageAnnotator/issues -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 305136] File associations are broken in gtk/glib apps
https://bugs.kde.org/show_bug.cgi?id=305136 --- Comment #19 from Nate Graham --- > Meanwhile if you like KDE's defaults and want them applied to non KDE apps, > the solution is to generate a mimeapps.list file. Could we have the KCM do that automatically? Either automatically, or optionally? -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 455444] Custom Shortcuts are gone in 5.25 on Wayland
https://bugs.kde.org/show_bug.cgi?id=455444 Nate Graham changed: What|Removed |Added Status|RESOLVED|CLOSED -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 455444] Custom Shortcuts are gone in 5.25 on Wayland
https://bugs.kde.org/show_bug.cgi?id=455444 Nate Graham changed: What|Removed |Added Status|REOPENED|RESOLVED Resolution|--- |INTENTIONAL --- Comment #11 from Nate Graham --- Not only do some of the features of khotkeys not work on Wayland, its codebase is ancient and buggy and unmaintained. It does not work with modern components of the system and is slowly bit-rotting. Nobody wanted to touch it to disable the features in question on wayland because it is too fragile. Ultimately having two different GUIs to do the same thing is a bad idea and we made the decision for the Wayland session to focus on the one that is modern and maintainable, correcting an earlier mistake of allowing two parallel systems to be created in the first place. The complaint about having to create a script file to use the other page is legitimate. Feel free to file a bug report about that in https://bugs.kde.org/enter_bug.cgi?product=systemsettings=kcm_keys. Also, feel free to request features there for things that you miss from KHotkeys. The faster those are added, the sooner we can truly delete KHotkeys for everyone and remove the confusion and bugginess of two parallel overlapping global shortcut systems once and for all. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 436360] Scrolling through KWin shortcuts using scrollbar distorts text items
https://bugs.kde.org/show_bug.cgi?id=436360 Nate Graham changed: What|Removed |Added Resolution|--- |WAITINGFORINFO Status|REPORTED|NEEDSINFO --- Comment #2 from Nate Graham --- I believe this was caused by a Qt issue that's fixed now. Can you still reproduce the issue in Plasma 5.25? -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 456741] Display orientation change from landscape to portrait fail. Ubuntu Studio 22.04. Works fine with US 20.04 on same machine.
https://bugs.kde.org/show_bug.cgi?id=456741 Nate Graham changed: What|Removed |Added Product|systemsettings |KScreen Assignee|plasma-b...@kde.org |kscreen-bugs-n...@kde.org Resolution|WAITINGFORINFO |BACKTRACE Component|general |common --- Comment #7 from Nate Graham --- Relevant parts: > Stack trace of thread 2017: > #0 0x7f2f1429c176 n/a (KSC_XRandR.so + 0xc176) > #1 0x7f2f1429c409 n/a (KSC_XRandR.so + 0xc409) > #2 0x5648002a4b63 n/a (kscreen_backend_launcher + 0x5b63) > #3 0x5648002a5611 n/a (kscreen_backend_launcher + 0x6611) Unfortunately this is missing symbols. Can you install debug symbols for the kscreen package, reproduce the crash, and attach a new backtrace? Thanks! -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 454542] KDE-specific tablet mode features not being automatically activated on Lenovo ideapad anymore
https://bugs.kde.org/show_bug.cgi?id=454542 Nate Graham changed: What|Removed |Added Resolution|--- |WAITINGFORINFO Status|REPORTED|NEEDSINFO --- Comment #4 from Nate Graham --- If you go to System Settings > Workspace Behavior > Touch Mode, can you make sure it's set to "Automatically enable as needed"? If it's already set to that, do you see that Touch Mode works properly if you manually set it to "Always enabled" for testing purposes? -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 456321] Inactive window titlebar not colored with the setting turned on
https://bugs.kde.org/show_bug.cgi?id=456321 Nate Graham changed: What|Removed |Added Status|REOPENED|NEEDSINFO Resolution|--- |WAITINGFORINFO --- Comment #4 from Nate Graham --- Can you attach a screenshot that shows an active window and an inactive window, with both using your custom color scheme? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 456755] Accessibility>Zoom: allow zoom on one screen and not the other in dual/clone screen setup
https://bugs.kde.org/show_bug.cgi?id=456755 Nate Graham changed: What|Removed |Added Resolution|--- |INTENTIONAL Status|REPORTED|RESOLVED --- Comment #3 from Nate Graham --- Yep, I think that would get you what you want. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 456391] broken/nonexistent keyboard layout
https://bugs.kde.org/show_bug.cgi?id=456391 Nate Graham changed: What|Removed |Added Status|NEEDSINFO |REPORTED Resolution|WAITINGFORINFO |--- --- Comment #5 from Nate Graham --- Andrey, can I ask you to take over on this bug report? -- You are receiving this mail because: You are watching all bug changes.
[peruse] [Bug 450844] "Group by series" unflattens filesystem hierarchy, making it difficult to find anything
https://bugs.kde.org/show_bug.cgi?id=450844 Nate Graham changed: What|Removed |Added Status|REPORTED|RESOLVED See Also||https://bugs.kde.org/show_b ||ug.cgi?id=450845 Resolution|--- |INTENTIONAL --- Comment #4 from Nate Graham --- > What you are suggesting would be a folder browser in peruse. Indeed, I think that is what I want. My books are all organized by filesystem and don't generally have correct metadata, so any of these views that organize by extracted metadata don't really work for me. There is a "Filter by folder" view but it doesn't really seem to work the way I would expect. See Bug 450845. -- You are receiving this mail because: You are watching all bug changes.
[peruse] [Bug 450845] "Filter by Folder" just shows everything
https://bugs.kde.org/show_bug.cgi?id=450845 Nate Graham changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=450844 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 447451] Kicker's sub-menus cannot be navigated by keyboard in Wayland
https://bugs.kde.org/show_bug.cgi?id=447451 Nate Graham changed: What|Removed |Added Status|CONFIRMED |RESOLVED Version Fixed In||5.26 Resolution|--- |FIXED --- Comment #8 from Nate Graham --- Musta been fixed by something in git master, then. I can also reproduce that it's fixed! -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 456923] New: Outgoing e-mail from GMail account to smtp.gmail.com sometimes hangs
https://bugs.kde.org/show_bug.cgi?id=456923 Bug ID: 456923 Summary: Outgoing e-mail from GMail account to smtp.gmail.com sometimes hangs Product: Akonadi Version: 5.20.3 Platform: openSUSE RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Mail Dispatcher Agent Assignee: kdepim-b...@kde.org Reporter: freekdekru...@kde.nl Target Milestone: --- SUMMARY *** Sometimes messages with sender my gmail.com account hangs in the outbox of Local Folders *** STEPS TO REPRODUCE 1. Compose a message with my gmail.com address as sender 2. Submit it for delivery 3. It does hangs in the outbox of the Local Folders without a warning 4. When restarting KMail somewhat later a message arrives that sending has failed because the remote host closed the connection. 5. A workaround is to use "akonadictl stop" to kill all akonadi processes and to restart akonadi in Kmail. After that most of the time a message appears about a DBUS something is not present or ready. This is not very important. Clicking right on the outgoing mailbox and choosing Send messages in queue makes the hanging message to be delivered. OBSERVED RESULT Message hannging. EXPECTED RESULT Messages should be delivered immediately or later automatically. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: kernel 5.18.9 (available in About System) KDE Plasma Version: 5.25.3 KDE Frameworks Version: 5.96.0 Qt Version: 5.15.5 ADDITIONAL INFORMATION Advanced settings of send information for GMail: STARTTLS, port 587, Authentication XOAUTH2 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 456922] SVG file that makes Krita use memory infinitely until I kill the process
https://bugs.kde.org/show_bug.cgi?id=456922 Max changed: What|Removed |Added CC||hifi...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 456382] Dropping Reference Images in outside of the canvas aren't placed at the event position
https://bugs.kde.org/show_bug.cgi?id=456382 amyspark changed: What|Removed |Added Latest Commit|https://invent.kde.org/grap |https://invent.kde.org/grap |hics/krita/commit/1426f9b90 |hics/krita/commit/d3e9097bf |d03dc1bb9c3dd86261606347ad9 |c6d2bd088a818bcf398bd383263 |3a46|ce58 --- Comment #11 from amyspark --- Git commit d3e9097bfc6d2bd088a818bcf398bd383263ce58 by L. E. Segovia. Committed on 19/07/2022 at 15:12. Pushed by lsegovia into branch 'krita/5.1'. Fix positioning when pasting multiple reference images This commit partially reverts commit 7758ade706e7b1c2163d4f9ce7216095794b872c. (cherry picked from commit 1426f9b90d03dc1bb9c3dd86261606347ad93a46) M +1-1libs/ui/KisView.cpp https://invent.kde.org/graphics/krita/commit/d3e9097bfc6d2bd088a818bcf398bd383263ce58 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 456922] New: SVG file that makes Krita use memory infinitely until I kill the process
https://bugs.kde.org/show_bug.cgi?id=456922 Bug ID: 456922 Summary: SVG file that makes Krita use memory infinitely until I kill the process Product: krita Version: 5.0.6 Platform: Other OS: Microsoft Windows Status: REPORTED Severity: crash Priority: NOR Component: File formats Assignee: krita-bugs-n...@kde.org Reporter: hifi...@gmail.com Target Milestone: --- Created attachment 150742 --> https://bugs.kde.org/attachment.cgi?id=150742=edit bugged file SUMMARY This specific SVG file of an icon puts Krita in a state of infinitely increasing memory used until I have to kill it. For testing purposes I've loaded it into Inkscape and saved it. This worked without any problems. This happened in 4.4.x too but didn't change when I upgraded my installation. STEPS TO REPRODUCE 1. Load the file SOFTWARE/OS VERSIONS Windows: Windows 10 x64 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 456382] Dropping Reference Images in outside of the canvas aren't placed at the event position
https://bugs.kde.org/show_bug.cgi?id=456382 amyspark changed: What|Removed |Added Latest Commit|https://invent.kde.org/grap |https://invent.kde.org/grap |hics/krita/commit/683fd6b90 |hics/krita/commit/1426f9b90 |bcb6981692ef97ca32e22612fea |d03dc1bb9c3dd86261606347ad9 |7661|3a46 Resolution|--- |FIXED Status|REOPENED|RESOLVED --- Comment #10 from amyspark --- Git commit 1426f9b90d03dc1bb9c3dd86261606347ad93a46 by L. E. Segovia. Committed on 19/07/2022 at 15:07. Pushed by lsegovia into branch 'master'. Fix positioning when pasting multiple reference images This commit partially reverts commit 7758ade706e7b1c2163d4f9ce7216095794b872c. M +1-1libs/ui/KisView.cpp https://invent.kde.org/graphics/krita/commit/1426f9b90d03dc1bb9c3dd86261606347ad93a46 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 456759] KDE ignoring all of my aspect / look and feel settings in QT apps
https://bugs.kde.org/show_bug.cgi?id=456759 --- Comment #3 from Nate Graham --- Can you change your widget style to Breeze in System Settings and see if that fixes the issue? If it doesn't, can you take another screenshot of System Settings? Do you have qt5ct installed, by any chance? If you do, does the problem get fixed if you remove it and reboot? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 456921] (SEGV) kWin crashed in KWaylandServer::SurfaceInterface::resource() when pressing a button on the tablet device
https://bugs.kde.org/show_bug.cgi?id=456921 postix changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=456817 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 456817] kwin_wayland segfaults in KWaylandServer::TabletV2Interface::pad() while pressing some buttons on Tablet
https://bugs.kde.org/show_bug.cgi?id=456817 postix changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=456921 CC||pos...@posteo.eu -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 456921] (SEGV) kWin crashed in KWaylandServer::SurfaceInterface::resource() when pressing a button on the tablet device
https://bugs.kde.org/show_bug.cgi?id=456921 postix changed: What|Removed |Added Summary|(SEGV) kWin crashed in |(SEGV) kWin crashed in |KWaylandServer::SurfaceInte |KWaylandServer::SurfaceInte |rface::resource() when |rface::resource() when |pressing a button on tablet |pressing a button on the ||tablet device -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 456742] kontact crashes on start when selected calendars
https://bugs.kde.org/show_bug.cgi?id=456742 --- Comment #1 from Diego Ercolani --- Created attachment 150741 --> https://bugs.kde.org/attachment.cgi?id=150741=edit New crash information added by DrKonqi kontact (5.19.3 (21.12.3)) using Qt 5.15.2 - What I was doing when the application crashed: Selecting "To Do List" from Mail dialog. Kontac crashes without asking anything -- Backtrace (Reduced): #4 QSortFilterProxyModelPrivate::updateChildrenMapping(QModelIndex const&, QSortFilterProxyModelPrivate::Mapping*, Qt::Orientation, int, int, int, bool) (this=this@entry=0x55a73add0e90, source_parent=..., parent_mapping=parent_mapping@entry=0x55a73ac2da80, orient=orient@entry=Qt::Vertical, start=start@entry=0, end=end@entry=0, delta_item_count=1, remove=false) at itemmodels/qsortfilterproxymodel.cpp:1200 #5 0x7f1bf6f918c5 in QSortFilterProxyModelPrivate::source_items_inserted(QModelIndex const&, int, int, Qt::Orientation) (this=this@entry=0x55a73add0e90, source_parent=..., start=start@entry=0, end=end@entry=0, orient=orient@entry=Qt::Vertical) at itemmodels/qsortfilterproxymodel.cpp:1000 #6 0x7f1bf6f940ed in QSortFilterProxyModelPrivate::_q_sourceRowsInserted(QModelIndex const&, int, int) (this=0x55a73add0e90, source_parent=..., start=0, end=0) at itemmodels/qsortfilterproxymodel.cpp:1702 #7 0x7f1bf6f95f81 in QSortFilterProxyModel::qt_static_metacall(QObject*, QMetaObject::Call, int, void**) (_o=, _c=, _id=, _a=) at .moc/moc_qsortfilterproxymodel.cpp:282 #8 0x7f1bf7002ff9 in doActivate(QObject*, int, void**) (sender=0x55a73ce440d0, signal_index=13, argv=0x7ffc4bfb05b0) at kernel/qobject.cpp:3898 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 456921] (SEGV) kWin crashed in KWaylandServer::SurfaceInterface::resource() when pressing a button on tablet
https://bugs.kde.org/show_bug.cgi?id=456921 postix changed: What|Removed |Added Keywords||wayland CC||pos...@posteo.eu -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 456742] kontact crashes on start when selected calendars
https://bugs.kde.org/show_bug.cgi?id=456742 Diego Ercolani changed: What|Removed |Added CC||diego.ercol...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 456921] New: (SEGV) kWin crashed in KWaylandServer::SurfaceInterface::resource() when pressing a button on tablet
https://bugs.kde.org/show_bug.cgi?id=456921 Bug ID: 456921 Summary: (SEGV) kWin crashed in KWaylandServer::SurfaceInterface::resource() when pressing a button on tablet Product: kwin Version: 5.25.3 Platform: openSUSE RPMs OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: general Assignee: kwin-bugs-n...@kde.org Reporter: pos...@posteo.eu Target Milestone: --- Created attachment 150740 --> https://bugs.kde.org/attachment.cgi?id=150740=edit kWin Support Information SUMMARY kWin crashed and teared down the whole session (including my non-saved work), when I accidentially pressed a tablet on my Wacom Intuos M tablet while taking notes in Xournal++. ``` #0 0x7fed6ff0b5e4 in KWaylandServer::SurfaceInterface::resource() const (this=0x55bbe00bfb10) at /usr/src/debug/kwin5-5.25.3-1.1.x86_64/src/wayland/surface_interface.cpp:367 #1 0x7fed6ff171d9 in KWaylandServer::TabletPadV2Interface::setCurrentSurface(KWaylandServer::SurfaceInterface*, KWaylandServer::TabletV2Interface*) (this=0x55bbde2903a0, surface=0x55bbdfcbd600, tablet=0x55bbde109720) at /usr/src/debug/kwin5-5.25.3-1.1.x86_64/src/wayland/tablet_v2_interface.cpp:592 #2 0x7fed6fda2ae6 in non-virtual thunk to KWin::TabletInputFilter::tabletPadButtonEvent(unsigned int, bool, KWin::TabletPadId const&) () at /usr/src/debug/kwin5-5.25.3-1.1.x86_64/src/input.cpp:2306 #3 0x7fed6fe314d5 in std::__invoke_impl(std::__invoke_memfun_deref, bool (KWin::InputEventFilter::*&)(unsigned int, bool, KWin::TabletToolId const&), KWin::InputEventFilter* const&, unsigned int&, bool&, KWin::TabletToolId&) (__f=, __t=) at /usr/include/c++/12/bits/invoke.h:74 #4 std::__invoke(bool (KWin::InputEventFilter::*&)(unsigned int, bool, KWin::TabletPadId const&), KWin::InputEventFilter* const&, unsigned int&, bool&, KWin::TabletPadId&) (__fn=@0x7ffdca1ae2a0: table offset 192) at /usr/include/c++/12/bits/invoke.h:96 #5 std::_Bind, unsigned int, bool, KWin::TabletPadId))(unsigned int, bool, KWin::TabletPadId const&)>::__call(std::tuple&&, std::_Index_tuple<0ul, 1ul, 2ul, 3ul>) (__args=, this=0x7ffdca1ae2a0) at /usr/include/c++/12/functional:484 #6 std::_Bind, unsigned int, bool, KWin::TabletPadId))(unsigned int, bool, KWin::TabletPadId const&)>::operator()(KWin::InputEventFilter* const&) (this=0x7ffdca1ae2a0) at /usr/include/c++/12/functional:567 #7 __gnu_cxx::__ops::_Iter_pred, unsigned int, bool, KWin::TabletPadId))(unsigned int, bool, KWin::TabletPadId const&)> >::operator()(KWin::InputEventFilter* const*) (__it=0x55bbdde14d98, this=0x7ffdca1ae2a0) at /usr/include/c++/12/bits/predefined_ops.h:318 #8 std::__find_if, unsigned int, bool, KWin::TabletPadId))(unsigned int, bool, KWin::TabletPadId const&)> > >(KWin::InputEventFilter* const*, KWin::InputEventFilter* const*, __gnu_cxx::__ops::_Iter_pred, unsigned int, bool, KWin::TabletPadId))(unsigned int, bool, KWin::TabletPadId const&)> >, std::random_access_iterator_tag) (__pred=..., __last=0x55bbdde14da0, __first=0x55bbdde14d98) at /usr/include/c++/12/bits/stl_algobase.h:2097 #9 std::__find_if, unsigned int, bool, KWin::TabletPadId))(unsigned int, bool, KWin::TabletPadId const&)> > >(KWin::InputEventFilter* const*, KWin::InputEventFilter* const*, __gnu_cxx::__ops::_Iter_pred, unsigned int, bool, KWin::TabletPadId))(unsigned int, bool, KWin::TabletPadId const&)> >) (__pred=..., __last=0x55bbdde14da0, __first=0x55bbdde14d18) at /usr/include/c++/12/bits/stl_algobase.h:2112 #10 std::find_if, unsigned int, bool, KWin::TabletPadId))(unsigned int, bool, KWin::TabletPadId const&)> >(KWin::InputEventFilter* const*, KWin::InputEventFilter* const*, std::_Bind, unsigned int, bool, KWin::TabletPadId))(unsigned int, bool, KWin::TabletPadId const&)>) (__pred=..., __last=0x55bbdde14da0, __first=0x55bbdde14d18) at /usr/include/c++/12/bits/stl_algo.h:3877 #11 std::none_of, unsigned int, bool, KWin::TabletPadId))(unsigned int, bool, KWin::TabletPadId const&)> >(KWin::InputEventFilter* const*, KWin::InputEventFilter* const*, std::_Bind, unsigned int, bool, KWin::TabletPadId))(unsigned int, bool, KWin::TabletPadId const&)>) (__pred=..., __last=0x55bbdde14da0, __first=0x55bbdde14d18) at /usr/include/c++/12/bits/stl_algo.h:474 #12 std::any_of, unsigned int, bool, KWin::TabletPadId))(unsigned int, bool, KWin::TabletPadId const&)> >(KWin::InputEventFilter* const*, KWin::InputEventFilter* const*, std::_Bind, unsigned int, bool, KWin::TabletPadId))(unsigned int, bool, KWin::TabletPadId const&)>) (__pred=..., __last=0x55bbdde14da0, __first=0x55bbdde14d18) at /usr/include/c++/12/bits/stl_algo.h:493 #13 KWin::InputRedirection::processFilters, unsigned int, bool, KWin::TabletPadId))(unsigned int, bool, KWin::TabletPadId const&)> >(std::_Bind, unsigned int, bool, KWin::TabletPadId))(unsigned int, bool, KWin::TabletPadId const&)>) (function=..., this=) at
[kscreenlocker] [Bug 456750] Screen locker broke from Caps Lock key when i wake up the monitor
https://bugs.kde.org/show_bug.cgi?id=456750 --- Comment #3 from Nate Graham --- Thanks, so the screen locker didn't crash. But it says: > Jul 15 12:44:09 fedora kscreenlocker_greet[27556]: The Wayland connection > broke. Did the Wayland compositor die? So maybe kwin_wayland crashed? What does `coredumpctl list kwin_wayland` say? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 456743] With only 1 screen, plasmashell crashed in ScreenPool::handleScreenAdded() on wakeup from sleep
https://bugs.kde.org/show_bug.cgi?id=456743 Nate Graham changed: What|Removed |Added Summary|plasmashell crashed in |With only 1 screen, |ScreenPool::handleScreenAdd |plasmashell crashed in |ed() on wakeup from sleep |ScreenPool::handleScreenAdd ||ed() on wakeup from sleep Resolution|WAITINGFORINFO |--- Status|NEEDSINFO |REPORTED --- Comment #5 from Nate Graham --- Thanks, seems like something is going wrong in the multiscreen code, as it's adding and removing screens in the backend when it shouldn't have to. -- You are receiving this mail because: You are watching all bug changes.
[kalendar] [Bug 455902] Kalendar event reminders crash on startup (every time)
https://bugs.kde.org/show_bug.cgi?id=455902 Claudio Cambra changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |FIXED --- Comment #1 from Claudio Cambra --- Hi, this bug is now fixed with https://invent.kde.org/pim/akonadi-calendar/-/merge_requests/32 and this fix will be included in upcoming updates Thanks for reporting! -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 455421] Thunderbird is shown with Generic Wayland Icon in Alt+Tab Dialog
https://bugs.kde.org/show_bug.cgi?id=455421 --- Comment #3 from Nate Graham --- See also https://gitlab.gnome.org/GNOME/gedit/-/issues/486 -- You are receiving this mail because: You are watching all bug changes.
[kalendar] [Bug 456920] Reminder closed unexpectedly...
https://bugs.kde.org/show_bug.cgi?id=456920 Claudio Cambra changed: What|Removed |Added Resolution|--- |WAITINGFORINFO Status|REPORTED|NEEDSINFO --- Comment #1 from Claudio Cambra --- Hi, unfortunately without further debug information there is not much we can ascertain from this backtrace. If you are able to provide a backtrace with debug symbols installed please provide it. Thanks! -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 455809] Option "Make window titlebars accent-colored" is slightly inaccurate when applied to header-color-using color schemes
https://bugs.kde.org/show_bug.cgi?id=455809 Nate Graham changed: What|Removed |Added CC||sonichedgehog_hyperblast00@ ||yahoo.com --- Comment #2 from Nate Graham --- *** Bug 456887 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 456887] Colorizing the toolbar with the accent color depends on a hidden setting in the color scheme
https://bugs.kde.org/show_bug.cgi?id=456887 Nate Graham changed: What|Removed |Added Resolution|--- |DUPLICATE Status|REPORTED|RESOLVED CC||n...@kde.org --- Comment #2 from Nate Graham --- When you use a color scheme with Header colors, the option in question applies the accent color to both. When you use a color scheme without Header colors, the option in question applies the accent color to just the titlebar. We need to change the UI text to make this clear. *** This bug has been marked as a duplicate of bug 455809 *** -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 339214] Starting KMail gives message "Could not create collection trash resourceId: 3 [MailCommon::Kernel::createDefaultCollectionDone, MailCommon::Kernel::emergencyExit]
https://bugs.kde.org/show_bug.cgi?id=339214 Fabian Vogt changed: What|Removed |Added CC||fab...@ritter-vogt.de --- Comment #34 from Fabian Vogt --- My Akonadi suddenly (no config changes) developed the same issue. KMail refuses to start because of "Could not create collection 'drafts'". The issue appears to be that the "drafts" collection had the "SpecialCollectionAttribute" set to "trash", with a matching icon, while "trash" also had that. As it couldn't find a proper "drafts" collection it tried to create "drafts" again. Using akonadiconsole I could fix the "SpecialCollectionAttribute" of the collection and KMail works for me again. Question is why the attribute changed. -- You are receiving this mail because: You are watching all bug changes.
[kalendar] [Bug 456920] New: Reminder closed unexpectedly...
https://bugs.kde.org/show_bug.cgi?id=456920 Bug ID: 456920 Summary: Reminder closed unexpectedly... Product: kalendar Version: unspecified Platform: openSUSE RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: claudio.cam...@gmail.com Reporter: stefan.leit...@fastmail.fm CC: c...@carlschwan.eu Target Milestone: --- Application: kalendarac (5.20.3) Qt Version: 5.15.5 Frameworks Version: 5.96.0 Operating System: Linux 5.18.9-2-default x86_64 Windowing System: X11 Distribution: openSUSE Tumbleweed DrKonqi: 5.25.3 [KCrashBackend] -- Information about the crash: ...after clicking "Dismiss". But the program started again automatically. The crash can be reproduced sometimes. -- Backtrace: Application: Reminders (kalendarac), signal: Segmentation fault [KCrash Handler] #4 0x55e868f852ab in ?? () #5 0x7fb0d2092e6f in ?? () from /lib64/libQt5Core.so.5 #6 0x7fb0d2fe2817 in KNotification::close() () from /lib64/libKF5Notifications.so.5 #7 0x7fb0d2092e6f in ?? () from /lib64/libQt5Core.so.5 #8 0x7fb0d2fdfaef in KNotificationPlugin::finished(KNotification*) () from /lib64/libKF5Notifications.so.5 #9 0x7fb0d2ff6891 in ?? () from /lib64/libKF5Notifications.so.5 #10 0x7fb0d2092e6f in ?? () from /lib64/libQt5Core.so.5 #11 0x7fb0d3002599 in ?? () from /lib64/libKF5Notifications.so.5 #12 0x7fb0d3002f83 in ?? () from /lib64/libKF5Notifications.so.5 #13 0x7fb0d236756b in ?? () from /lib64/libQt5DBus.so.5 #14 0x7fb0d2087760 in QObject::event(QEvent*) () from /lib64/libQt5Core.so.5 #15 0x7fb0d205bfb8 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /lib64/libQt5Core.so.5 #16 0x7fb0d205ef51 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () from /lib64/libQt5Core.so.5 #17 0x7fb0d20b3c53 in ?? () from /lib64/libQt5Core.so.5 #18 0x7fb0cfa82ea0 in g_main_context_dispatch () from /lib64/libglib-2.0.so.0 #19 0x7fb0cfa83258 in ?? () from /lib64/libglib-2.0.so.0 #20 0x7fb0cfa832ec in g_main_context_iteration () from /lib64/libglib-2.0.so.0 #21 0x7fb0d20b3456 in QEventDispatcherGlib::processEvents(QFlags) () from /lib64/libQt5Core.so.5 #22 0x7fb0d205aa2b in QEventLoop::exec(QFlags) () from /lib64/libQt5Core.so.5 #23 0x7fb0d2062b96 in QCoreApplication::exec() () from /lib64/libQt5Core.so.5 #24 0x55e868f81585 in ?? () #25 0x7fb0d19425b0 in __libc_start_call_main () from /lib64/libc.so.6 #26 0x7fb0d1942679 in __libc_start_main_impl () from /lib64/libc.so.6 #27 0x55e868f81b85 in ?? () [Inferior 1 (process 1898) detached] Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 456408] [ Request ] Task manager arranges entries by where they're placed on the screen?
https://bugs.kde.org/show_bug.cgi?id=456408 --- Comment #7 from Nate Graham --- Nice! Feel free to submit it at https://store.kde.org/browse?cat=418 -- You are receiving this mail because: You are watching all bug changes.
[kolourpaint] [Bug 456919] New: Unable to re-activate color picker
https://bugs.kde.org/show_bug.cgi?id=456919 Bug ID: 456919 Summary: Unable to re-activate color picker Product: kolourpaint Version: 22.04.3 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: major Priority: NOR Component: general Assignee: kolourpaint-supp...@lists.sourceforge.net Reporter: oss+kde+bugzi...@mayeul.net Target Milestone: --- SUMMARY I played around with undocking the color picker some time ago, under sway/wayland. I closed it, but I cannot toggle it back on, there is no menu option. Configuration⇾Toolbars should include the color picker. STEPS TO REPRODUCE 1. Under sway, unlock the toolbars 2. Drag one of them, it becomes a pop-up window that you can drag around (by pressing meta, as the drag area doesn't work) and with no borders, but that you cannot reattach. 3. Close the toolbox window with the sway shortcut. 4. You cannot re-enable the color toolbox, though you can for most others. It should probably work under plasma/wayland or plasma as well. OBSERVED RESULT Once closed, the color picker toolbox cannot be opened again. Toolboxes cannot be docked again, at least under sway. EXPECTED RESULT At least put a toggle to make the toolbox appear again. Maybe also add a button to reset the default toolbox positions and assortment. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Sway, Arch Linux x86_64 KDE Frameworks Version: 5.96.0-1 Qt Version: 5.15.5 ADDITIONAL INFORMATION wayland-egl -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 456213] Consider using "Minimize All" as the default behavior/widget, rather than "Show Desktop"
https://bugs.kde.org/show_bug.cgi?id=456213 Nate Graham changed: What|Removed |Added Ever confirmed|0 |1 Depends on||450137, 435253 Status|REPORTED|CONFIRMED Referenced Bugs: https://bugs.kde.org/show_bug.cgi?id=435253 [Bug 435253] Clicking twice on "Minimize all Windows"-widget does not unhide windows using multiple activies https://bugs.kde.org/show_bug.cgi?id=450137 [Bug 450137] Using Minimize All twice brings back the window, but the active window from before loses focus -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 450137] Using Minimize All twice brings back the window, but the active window from before loses focus
https://bugs.kde.org/show_bug.cgi?id=450137 Nate Graham changed: What|Removed |Added Blocks||456213 Referenced Bugs: https://bugs.kde.org/show_bug.cgi?id=456213 [Bug 456213] Consider using "Minimize All" as the default behavior/widget, rather than "Show Desktop" -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 435253] Clicking twice on "Minimize all Windows"-widget does not unhide windows using multiple activies
https://bugs.kde.org/show_bug.cgi?id=435253 Nate Graham changed: What|Removed |Added Blocks||456213 Referenced Bugs: https://bugs.kde.org/show_bug.cgi?id=456213 [Bug 456213] Consider using "Minimize All" as the default behavior/widget, rather than "Show Desktop" -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 456918] New: Log In locks itself sometimes
https://bugs.kde.org/show_bug.cgi?id=456918 Bug ID: 456918 Summary: Log In locks itself sometimes Product: kscreenlocker Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: ad...@xakeps.dk CC: bhus...@gmail.com Target Milestone: --- SUMMARY When screen is locked, sometimes it locks user from logging in for 5, 10, 15 or more mins. I know that this happens because of many log in attempts, but this happens even without any log in attempt. STEPS TO REPRODUCE 1. Lock screen 2. Sometimes it locks out user OBSERVED RESULT User is locked for 5, 10 or more mins EXPECTED RESULT User is not locked SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 5.25.3 KDE Frameworks Version: 5.96.0 Qt Version: 5.15.5 Kernel Version: 5.18.12-arch1-1 (64-bit) Graphics Platform: X11 Processors: 8 × Intel® Core™ i7-4790K CPU @ 4.00GHz Memory: 15,5 GiB of RAM Graphics Processor: Mesa Intel® HD Graphics 4600 Manufacturer: ASUS Product Name: All Series ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 435253] Clicking twice on "Minimize all Windows"-widget does not unhide windows using multiple activies
https://bugs.kde.org/show_bug.cgi?id=435253 Nate Graham changed: What|Removed |Added Status|REPORTED|CONFIRMED Ever confirmed|0 |1 CC||n...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 435253] Clicking twice on "Minimize all Windows"-widget does not unhide windows using multiple activies
https://bugs.kde.org/show_bug.cgi?id=435253 Nate Graham changed: What|Removed |Added CC||random1123581321@protonmail ||.com --- Comment #1 from Nate Graham --- *** Bug 444999 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 444999] Minimize All changes Activity/Virtual Desktop
https://bugs.kde.org/show_bug.cgi?id=444999 Nate Graham changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |DUPLICATE --- Comment #1 from Nate Graham --- *** This bug has been marked as a duplicate of bug 435253 *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 456761] Dozen of logs and big slow down
https://bugs.kde.org/show_bug.cgi?id=456761 Nate Graham changed: What|Removed |Added Status|REPORTED|NEEDSINFO Component|XembedSNIProxy |Panel Resolution|--- |WAITINGFORINFO CC||niccolo.venera...@gmail.com --- Comment #5 from Nate Graham --- > Dozen of xembedsniproxy[]: Container window visible, stack below per second > Big slow down > No taskbar These are three issues. If you want, we can focus on "No taskbar" in this bug report, and ignore the other two. Some questions: 1. Is your wallpaper also missing or incorrect? or is it just the panel that's missing? 2. Is the base system a laptop or a desktop? 3. How many screens are you using? If any of them are external, how are they connected? 4. Are you using X11 or Wayland? 5. What Plasma version are you using? -- You are receiving this mail because: You are watching all bug changes.
[yakuake] [Bug 456917] New: Crash when closing Yakuake
https://bugs.kde.org/show_bug.cgi?id=456917 Bug ID: 456917 Summary: Crash when closing Yakuake Product: yakuake Version: Git (Frameworks 5) Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: h...@kde.org Reporter: nicolas.fe...@gmx.de Target Milestone: --- STEPS TO REPRODUCE 1. Open Yakuake 2. Press close button Everything from master #0 Session::wantsBlur (this=0x872750) at /home/nico/kde/src/yakuake/app/session.cpp:660 #1 0x00439941 in operator() (session=, __closure=) at /home/nico/kde/src/yakuake/app/sessionstack.cpp:769 #2 __gnu_cxx::__ops::_Iter_pred >::operator()::const_iterator> (__it=..., this=) at /usr/include/c++/12/bits/predefined_ops.h:318 #3 std::__find_if::const_iterator, __gnu_cxx::__ops::_Iter_pred > > (__pred=..., __last=..., __first=...) at /usr/include/c++/12/bits/stl_algobase.h:2050 #4 std::__find_if::const_iterator, __gnu_cxx::__ops::_Iter_pred > > (__pred=..., __last=..., __first=...) at /usr/include/c++/12/bits/stl_algobase.h:2112 #5 std::find_if::const_iterator, SessionStack::wantsBlur() const:: > (__pred=..., __last=..., __first=...) at /usr/include/c++/12/bits/stl_algo.h:3877 #6 std::none_of::const_iterator, SessionStack::wantsBlur() const:: > (__pred=..., __last=..., __first=...) at /usr/include/c++/12/bits/stl_algo.h:474 #7 std::any_of::const_iterator, SessionStack::wantsBlur() const:: > (__pred=..., __last=..., __first=...) at /usr/include/c++/12/bits/stl_algo.h:493 #8 SessionStack::wantsBlur (this=) at /home/nico/kde/src/yakuake/app/sessionstack.cpp:768 #9 0x00428387 in MainWindow::applyWindowProperties (this=0x7fffd5b0) at /home/nico/kde/src/yakuake/app/mainwindow.cpp:938 #10 0x75d0c3a4 in QtPrivate::QSlotObjectBase::call (a=0x7fffd0b0, r=0x7fffd5b0, this=0x636400) at ../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398 #11 doActivate (sender=0x543190, signal_index=19, argv=0x7fffd0b0) at kernel/qobject.cpp:3886 #12 0x75d0c3a4 in QtPrivate::QSlotObjectBase::call (a=0x7fffd160, r=0x543190, this=0x8ad820) at ../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398 #13 doActivate (sender=0x78bfa0, signal_index=10, argv=0x7fffd160) at kernel/qobject.cpp:3886 #14 0x75d05c1f in QMetaObject::activate (sender=sender@entry=0x78bfa0, m=m@entry=0x469720 , local_signal_index=local_signal_index@entry=7, argv=argv@entry=0x0) at kernel/qobject.cpp:3946 #15 0x00419973 in Session::wantsBlurChanged (this=this@entry=0x78bfa0) at /home/nico/kde/build/yakuake/app/yakuake_autogen/EWIEGA46WW/moc_session.cpp:356 #16 0x00435bf4 in Session::cleanup (this=0x78bfa0, terminalId=0) at /home/nico/kde/src/yakuake/app/session.cpp:384 #17 0x75d0c3d4 in doActivate (sender=0x7a3f80, signal_index=9, argv=0x7fffd2b0) at kernel/qobject.cpp:3898 #18 0x75d05c1f in QMetaObject::activate (sender=sender@entry=0x7a3f80, m=m@entry=0x4695e0 , local_signal_index=local_signal_index@entry=6, argv=argv@entry=0x7fffd2b0) at kernel/qobject.cpp:3946 #19 0x00419ea1 in Terminal::destroyed (this=this@entry=0x7a3f80, _t1=) at /home/nico/kde/build/yakuake/app/yakuake_autogen/EWIEGA46WW/moc_terminal.cpp:302 #20 0x0044771a in Terminal::~Terminal (this=0x7a3f80, __in_chrg=) at /home/nico/kde/src/yakuake/app/terminal.cpp:113 #21 Terminal::~Terminal (this=0x7a3f80, __in_chrg=) at /home/nico/kde/src/yakuake/app/terminal.cpp:114 #22 0x75cff18e in QObjectPrivate::deleteChildren (this=this@entry=0x79a140) at kernel/qobject.cpp:2104 #23 0x76836d26 in QWidget::~QWidget (this=this@entry=0x772de0, __in_chrg=) at kernel/qwidget.cpp:1522 #24 0x768e10ed in QFrame::~QFrame (this=this@entry=0x772de0, __in_chrg=) at widgets/qframe.cpp:264 #25 0x769978b3 in QSplitter::~QSplitter (this=this@entry=0x772de0, __in_chrg=) at widgets/qsplitter.cpp:979 #26 0x004411a1 in Splitter::~Splitter (this=0x772de0, __in_chrg=) at /home/nico/kde/src/yakuake/app/splitter.cpp:18 #27 Splitter::~Splitter (this=0x772de0, __in_chrg=) at /home/nico/kde/src/yakuake/app/splitter.cpp:18 #28 0x00434816 in Session::~Session (this=0x78bfa0, __in_chrg=) at /home/nico/kde/src/yakuake/app/session.cpp:35 #29 0x00434909 in Session::~Session (this=0x78bfa0, __in_chrg=) at /home/nico/kde/src/yakuake/app/session.cpp:38 #30 0x75cff18e in QObjectPrivate::deleteChildren (this=this@entry=0x537e20) at kernel/qobject.cpp:2104 #31 0x76836d26 in QWidget::~QWidget (this=this@entry=0x543190, __in_chrg=) at kernel/qwidget.cpp:1522 #32 0x768e10ed in QFrame::~QFrame (this=this@entry=0x543190, __in_chrg=) at widgets/qframe.cpp:264 #33 0x7699c73d in QStackedWidget::~QStackedWidget (this=this@entry=0x543190, __in_chrg=) at widgets/qstackedwidget.cpp:147 #34 0x00437b8e
[Oxygen] [Bug 456916] New: analogue plain complete clock widget?
https://bugs.kde.org/show_bug.cgi?id=456916 Bug ID: 456916 Summary: analogue plain complete clock widget? Product: Oxygen Version: 5.25.3 Platform: unspecified OS: All Status: REPORTED Severity: wishlist Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: dchme...@gmail.com Target Milestone: --- Created attachment 150739 --> https://bugs.kde.org/attachment.cgi?id=150739=edit hard-to-read clock SUMMARY Analogue clock widget misses most numbers (and the dark theme one has distracting pattern in it.) STEPS TO REPRODUCE 1. Add analogue clock widget. 2. Sometimes have trouble reading it. OBSERVED RESULT Analogue clock widget misses most numbers (and the dark theme one has distracting pattern in it.) EXPECTED RESULT Option to have all numbers (preferably outside absolute position marks) and option for just black on white (Air light Oxygen theme) and plain (no pattern) white/light-grey on black (Oxygen dark theme). SOFTWARE/OS VERSIONS Linux/KDE Plasma: FreeBSD UNIX 8-13, KDE Neon 5 & Slackware 13-15 GNU/Linuxes KDE Plasma Version: 4, 5 KDE Frameworks Version: 4, 5 Qt Version: 4, 5 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 456915] New: activities should rememeber the active workspace
https://bugs.kde.org/show_bug.cgi?id=456915 Bug ID: 456915 Summary: activities should rememeber the active workspace Product: kwin Version: 5.25.1 Platform: openSUSE RPMs OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: activities Assignee: kwin-bugs-n...@kde.org Reporter: mig...@rozsas.eng.br Target Milestone: --- SUMMARY *** WHISLIST : When switching activities, the workspace is the same on all activities. I think would be nice if each activity has its own current workspace. lets say we have the situation ACTIVITY WORKSPACE A1w1, w2*, w3, w4 A2w1, w2, w3, w4* where * denotes the current/active workspace in each Activity Switching to A2, should display the content of w4. Switching back to A1, should display the content of w2. *** STEPS TO REPRODUCE 1. currently the content of workspace 1 is displayed. 2. Switch to another Activity 3. the content of workspace 1 on another activity is displayed OBSERVED RESULT Switching activities did not switch workspace number. EXPECTED RESULT Switching activities should display the active workspace number on that activity. ADDITIONAL INFORMATION Operating System: openSUSE Tumbleweed 20220714 KDE Plasma Version: 5.25.3 KDE Frameworks Version: 5.96.0 Qt Version: 5.15.5 Kernel Version: 5.18.9-2-default (64-bit) Graphics Platform: X11 Processors: 8 × Intel® Core™ i7-3770 CPU @ 3.40GHz Memory: 15.6 GiB of RAM Graphics Processor: NVIDIA GeForce GTX 970/PCIe/SSE2 Manufacturer: Gigabyte Technology Co., Ltd. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 456816] allow standard/normal analogue clock face
https://bugs.kde.org/show_bug.cgi?id=456816 Nate Graham changed: What|Removed |Added Resolution|WAITINGFORINFO |INTENTIONAL Status|NEEDSINFO |RESOLVED --- Comment #3 from Nate Graham --- Thanks. This graphic is themable; every Plasma theme can define its own clock face appearance Hopefully you can find a Plasma theme that has a clock that's to your liking, but the current style in the Breeze theme is intentional. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 456816] allow standard/normal analogue clock face
https://bugs.kde.org/show_bug.cgi?id=456816 Nate Graham changed: What|Removed |Added Status|RESOLVED|CLOSED -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 450577] Contiguous Selection Tool Hangs when double clicking on large canvas
https://bugs.kde.org/show_bug.cgi?id=450577 Dmitry Kazakov changed: What|Removed |Added Status|CONFIRMED |RESOLVED Latest Commit||https://invent.kde.org/grap ||hics/krita/commit/7549b4ec3 ||156a0174a4912509257d3dac094 ||600b Resolution|--- |FIXED --- Comment #8 from Dmitry Kazakov --- Git commit 7549b4ec3156a0174a4912509257d3dac094600b by Dmitry Kazakov. Committed on 19/07/2022 at 13:48. Pushed by dkazakov into branch 'krita/5.1'. Fix a hangup when double-clicking with Flood Selection Tool Since fill command may read from the merged image, it should wait until the entire image completes its updates, therefore the job type shoudl be 'barrier'. M +1-1plugins/tools/selectiontools/kis_tool_select_contiguous.cc https://invent.kde.org/graphics/krita/commit/7549b4ec3156a0174a4912509257d3dac094600b -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 450577] Contiguous Selection Tool Hangs when double clicking on large canvas
https://bugs.kde.org/show_bug.cgi?id=450577 Dmitry Kazakov changed: What|Removed |Added Latest Commit|https://invent.kde.org/grap |https://invent.kde.org/grap |hics/krita/commit/7549b4ec3 |hics/krita/commit/295a63340 |156a0174a4912509257d3dac094 |397962446282a684c1f94b7385d |600b|17d2 --- Comment #9 from Dmitry Kazakov --- Git commit 295a63340397962446282a684c1f94b7385d17d2 by Dmitry Kazakov. Committed on 19/07/2022 at 13:48. Pushed by dkazakov into branch 'master'. Fix a hangup when double-clicking with Flood Selection Tool Since fill command may read from the merged image, it should wait until the entire image completes its updates, therefore the job type shoudl be 'barrier'. M +1-1plugins/tools/selectiontools/kis_tool_select_contiguous.cc https://invent.kde.org/graphics/krita/commit/295a63340397962446282a684c1f94b7385d17d2 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 456907] Krita doesn't close until the recent files thumbnails generator is finished
https://bugs.kde.org/show_bug.cgi?id=456907 --- Comment #5 from amyspark --- (In reply to Dmitry Kazakov from comment #2) > Erm, KisRecentFileIconCache belongs to Krita and it is the one who waits for > the completion of the background thread. No. The stacktrace shows the thumbnail creator is executing *Frameworks* code: > #8 (anonymous namespace)::readPixel () at > C:/Packaging/KritaDepsBuild/ext_frameworks/ext_kimageformats-prefix/src/ext_kimageformats/src/imageformats/psd.cpp:121 > No locals. > #9 (anonymous namespace)::LoadPSD () at > C:/Packaging/KritaDepsBuild/ext_frameworks/ext_kimageformats-prefix/src/ext_kimageformats/src/imageformats/psd.cpp:210 > No locals. > #10 PSDHandler::read () at > C:/Packaging/KritaDepsBuild/ext_frameworks/ext_kimageformats-prefix/src/ext_kimageformats/src/imageformats/psd.cpp:259 > No locals. > #11 0x7ffe99fbc932 in QImageReader::read () at > C:\Packaging\KritaDepsBuild\ext_qt\s\qtbase\src\gui\image/qimagereader.cpp:1261 > No locals. > #12 0x7ffe99fbc6f5 in QImageReader::read () at > C:\Packaging\KritaDepsBuild\ext_qt\s\qtbase\src\gui\image/qimagereader.cpp:1202 > No locals. > #13 0x7ffe99f9ff46 in QImage::load () at > C:\Packaging\KritaDepsBuild\ext_qt\s\qtbase\src\gui\image/qimage.cpp:3586 > No locals. > #14 0x7ffe7d967b4d in KisFileIconCreator::createFileIcon (this= out>, path=..., icon=..., devicePixelRatioF=, iconSize=...) at > C:/dev/env-11/krita/libs/ui/utils/KisFileIconCreator.cpp:133 This is still a bug in Frameworks, and what the associated commit did was work around it. It should be reported upstream so that every downstream user benefits. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 456862] 5.10 beta 2 - Cannot save .tif as .kra
https://bugs.kde.org/show_bug.cgi?id=456862 --- Comment #4 from La00 --- I understand now the problem - and Microsoft’s fault. Too bad there is no way to save quickly as .kra. In Affinity Photo, they make the difference between "save as" that saves if Affinity format and "export" that saves in different format. But it can be tricky too because you don’t expect to have two ways of saving :-) Thanks for your explanation. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 372191] email does not work on OS X
https://bugs.kde.org/show_bug.cgi?id=372191 caulier.gil...@gmail.com changed: What|Removed |Added OS|Linux |macOS Platform|Other |macOS (DMG) -- You are receiving this mail because: You are watching all bug changes.
[xdg-desktop-portal-kde] [Bug 450930] Can't close "Open with.." dialog when there's no suitable application installed
https://bugs.kde.org/show_bug.cgi?id=450930 k...@kalvdans.no-ip.org changed: What|Removed |Added CC||k...@kalvdans.no-ip.org -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 450577] Contiguous Selection Tool Hangs when double clicking on large canvas
https://bugs.kde.org/show_bug.cgi?id=450577 Dmitry Kazakov changed: What|Removed |Added Assignee|krita-bugs-n...@kde.org |dimul...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 450577] Contiguous Selection Tool Hangs when double clicking on large canvas
https://bugs.kde.org/show_bug.cgi?id=450577 Dmitry Kazakov changed: What|Removed |Added CC||dimul...@gmail.com Severity|normal |crash --- Comment #7 from Dmitry Kazakov --- Upgrading the bug to "crash", because Krita becomes unusable after the bug manifests itself. -- You are receiving this mail because: You are watching all bug changes.
