[kdenlive] [Bug 467262] New: Effect names, letters missing
https://bugs.kde.org/show_bug.cgi?id=467262 Bug ID: 467262 Summary: Effect names, letters missing Classification: Applications Product: kdenlive Version: git-master Platform: macOS (DMG) OS: macOS Status: REPORTED Severity: normal Priority: NOR Component: User Interface Assignee: j...@kdenlive.org Reporter: j...@sydney.dialix.com.au Target Milestone: --- Created attachment 157226 --> https://bugs.kde.org/attachment.cgi?id=157226=edit Screenshot showing incorrect names for Effects 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. Open the Effects pane 2. Notice strange display of the names of effects 3. OBSERVED RESULT In the names of effects, some letters are replaced by spaces, as in the screenshot that I uploaded. EXPECTED RESULT Effect names would appear properly, as in the Stable release. SOFTWARE/OS VERSIONS macOS: Ventura 13.2.1 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kwallet] [Bug 458085] Wallet system takes about 1 minute to start
https://bugs.kde.org/show_bug.cgi?id=458085 --- Comment #63 from Thiago Macieira --- (In reply to michaelk83 from comment #62) > > It also wouldn't work if I had my ~/.gnupg directory protected against > > unwanted reads and writes. > > The proposed patch doesn't attempt to write to ~/.gnupg directly. It makes > calls to gpgconf. Does it support setting ephemeral settings not saved to disk? I didn't see that in the documentation. Otherwise, you're just asking to write to disk, only indirectly. It's like replacing the KConfig classes with a subprocess call to kwriteconfig5 and say. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 467261] Taskbar dispalyed information freezes when running Devilulution X. Occasionally completely crashes
https://bugs.kde.org/show_bug.cgi?id=467261 --- Comment #1 from Bug Janitor Service --- Thank you for the bug report! Please note that Plasma 5.26.5 will not be supported for much longer by KDE; supported versions are 5.27, and 5.27 or newer. Please upgrade to the latest version as soon as your distribution makes it available to you. Plasma is a fast-moving project, and bugs in one version are often fixed in the next one. -- You are receiving this mail because: You are watching all bug changes.
[kdiff3] [Bug 447900] Scaling Broken on Windows
https://bugs.kde.org/show_bug.cgi?id=447900 --- Comment #11 from Charlie --- To follow up on this, the nightly seems to set Windows High DPI override settings. See screeenshot - the Override checkbox is enabled but also greyed out. So that is also the way I fixed previous builds. So this does work which is great! Are there plans for KDiff3 to natively support high dpi on windows without this override? -- You are receiving this mail because: You are watching all bug changes.
[kdiff3] [Bug 447900] Scaling Broken on Windows
https://bugs.kde.org/show_bug.cgi?id=447900 --- Comment #10 from Charlie --- Created attachment 157225 --> https://bugs.kde.org/attachment.cgi?id=157225=edit High DPI Settings -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 463026] Unable to reset custom collection icon
https://bugs.kde.org/show_bug.cgi?id=463026 caulier.gil...@gmail.com changed: What|Removed |Added Summary|Unable to reset custom |Unable to reset custom |collection collection icon |collection icon -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 466469] kdeconnect-sms crashes (SIGSEGV)
https://bugs.kde.org/show_bug.cgi?id=466469 --- 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.
[kmymoney] [Bug 342999] Finance:Quote online source for South African Unit Trusts not available
https://bugs.kde.org/show_bug.cgi?id=342999 Bug Janitor Service changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |WORKSFORME --- 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.
[dolphin] [Bug 466419] Dolphin crashed when I was checking the folder size, in the properties
https://bugs.kde.org/show_bug.cgi?id=466419 --- Comment #2 from Bug Janitor Service --- Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 466350] Plugging in a VGA screen and then powering it on causes it to use a low resolution by default, not the highest-supported resolution
https://bugs.kde.org/show_bug.cgi?id=466350 --- 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.
[kwin] [Bug 465639] High CPU usage after starting Plasma
https://bugs.kde.org/show_bug.cgi?id=465639 --- 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.
[plasmashell] [Bug 467261] New: Taskbar dispalyed information freezes when running Devilulution X. Occasionally completely crashes
https://bugs.kde.org/show_bug.cgi?id=467261 Bug ID: 467261 Summary: Taskbar dispalyed information freezes when running Devilulution X. Occasionally completely crashes Classification: Plasma Product: plasmashell Version: 5.26.5 Platform: Manjaro OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: bk__...@hotmail.com CC: k...@davidedmundson.co.uk Target Milestone: 1.0 Application: plasmashell (5.26.5) Qt Version: 5.15.8 Frameworks Version: 5.103.0 Operating System: Linux 6.1.12-1-MANJARO x86_64 Windowing System: X11 Distribution: Manjaro Linux DrKonqi: 5.26.5 [KCrashBackend] -- Information about the crash: Only happens when running program DevilutionX 1.4.1.2. All information displayed on the taskbar freezes when I open this program (Clock, any tasks open remain dispalyed open even if closed down, tasks do not refresh - example Thunderbird text in taskbar freezes not updating folder view or message view in taskbar.) The crash can be reproduced every time. -- Backtrace: Application: Plasma (plasmashell), signal: Segmentation fault [KCrash Handler] #4 0x7f0664d8b448 in QSGTexture::setFiltering(QSGTexture::Filtering) () at /usr/lib/libQt5Quick.so.5 #5 0x7f0664dbb3b0 in QSGOpaqueTextureMaterialShader::updateState(QSGMaterialShader::RenderState const&, QSGMaterial*, QSGMaterial*) () at /usr/lib/libQt5Quick.so.5 #6 0x7f0664da438e in QSGBatchRenderer::Renderer::renderMergedBatch(QSGBatchRenderer::Batch const*) () at /usr/lib/libQt5Quick.so.5 #7 0x7f0664da7bee in QSGBatchRenderer::Renderer::renderBatches() () at /usr/lib/libQt5Quick.so.5 #8 0x7f0664dac6b1 in QSGBatchRenderer::Renderer::render() () at /usr/lib/libQt5Quick.so.5 #9 0x7f0664d940a5 in QSGRenderer::renderScene(QSGBindable const&) () at /usr/lib/libQt5Quick.so.5 #10 0x7f0664d94544 in QSGRenderer::renderScene(unsigned int) () at /usr/lib/libQt5Quick.so.5 #11 0x7f0664dedac5 in QSGDefaultRenderContext::renderNextFrame(QSGRenderer*, unsigned int) () at /usr/lib/libQt5Quick.so.5 #12 0x7f0664e47fd1 in QQuickWindowPrivate::renderSceneGraph(QSize const&, QSize const&) () at /usr/lib/libQt5Quick.so.5 #13 0x7f0664df8096 in () at /usr/lib/libQt5Quick.so.5 #14 0x7f0664dfcfa4 in () at /usr/lib/libQt5Quick.so.5 #15 0x7f06630e432a in () at /usr/lib/libQt5Core.so.5 #16 0x7f0662a9ebb5 in () at /usr/lib/libc.so.6 #17 0x7f0662b20d90 in () at /usr/lib/libc.so.6 Thread 9 (Thread 0x7f0622ffd6c0 (LWP 197045) "QSGRenderThread"): #1 0x7f0662a9df90 in pthread_cond_wait () at /usr/lib/libc.so.6 #2 0x7f06630eb7c4 in QWaitCondition::wait(QMutex*, QDeadlineTimer) () at /usr/lib/libQt5Core.so.5 #3 0x7f0664dfd393 in () at /usr/lib/libQt5Quick.so.5 #4 0x7f06630e432a in () at /usr/lib/libQt5Core.so.5 #5 0x7f0662a9ebb5 in () at /usr/lib/libc.so.6 #6 0x7f0662b20d90 in () at /usr/lib/libc.so.6 Thread 8 (Thread 0x7f05fa7fc6c0 (LWP 197044) "threaded-ml"): #1 0x7f063e78d4b6 in pa_read () at /usr/lib/pulseaudio/libpulsecommon-16.1.so #2 0x7f063e8170b7 in pa_mainloop_prepare () at /usr/lib/libpulse.so.0 #3 0x7f063e81741d in pa_mainloop_iterate () at /usr/lib/libpulse.so.0 #4 0x7f063e8174e1 in pa_mainloop_run () at /usr/lib/libpulse.so.0 #5 0x7f063e827c02 in () at /usr/lib/libpulse.so.0 #6 0x7f063e7c4c57 in () at /usr/lib/pulseaudio/libpulsecommon-16.1.so #7 0x7f0662a9ebb5 in () at /usr/lib/libc.so.6 #8 0x7f0662b20d90 in () at /usr/lib/libc.so.6 Thread 7 (Thread 0x7f0602ffd6c0 (LWP 196548) "QSGRenderThread"): #1 0x7f0662a9df90 in pthread_cond_wait () at /usr/lib/libc.so.6 #2 0x7f06630eb7c4 in QWaitCondition::wait(QMutex*, QDeadlineTimer) () at /usr/lib/libQt5Core.so.5 #3 0x7f0664dfd393 in () at /usr/lib/libQt5Quick.so.5 #4 0x7f06630e432a in () at /usr/lib/libQt5Core.so.5 #5 0x7f0662a9ebb5 in () at /usr/lib/libc.so.6 #6 0x7f0662b20d90 in () at /usr/lib/libc.so.6 Thread 6 (Thread 0x7f06037fe6c0 (LWP 196537) "plasmashell"): #1 0x7f066126e524 in () at /usr/lib/libusbmuxd-2.0.so.6 #2 0x7f066126f8a9 in () at /usr/lib/libusbmuxd-2.0.so.6 #3 0x7f0662a9ebb5 in () at /usr/lib/libc.so.6 #4 0x7f0662b20d90 in () at /usr/lib/libc.so.6 Thread 5 (Thread 0x7f06359c26c0 (LWP 196516) "QQuickPixmapRea"): #1 0x7f0662ae5cad in clock_gettime () at /usr/lib/libc.so.6 #2 0x7f066186e45d in g_main_context_prepare () at /usr/lib/libglib-2.0.so.0 #3 0x7f06618c5a96 in () at /usr/lib/libglib-2.0.so.0 #4 0x7f066186d0e2 in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #5 0x7f06632d8c8f in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #6 0x7f06632866ec in QEventLoop::exec(QFlags) () at
[amarok] [Bug 467260] New: Amarok fails to launch, incompatible with ffmpeg 59
https://bugs.kde.org/show_bug.cgi?id=467260 Bug ID: 467260 Summary: Amarok fails to launch, incompatible with ffmpeg 59 Classification: Applications Product: amarok Version: 2.9.71 Platform: Archlinux OS: Linux Status: REPORTED Severity: critical Priority: NOR Component: general Assignee: amarok-bugs-d...@kde.org Reporter: alydar...@outlook.com Target Milestone: kf5 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. Launch Amarok in terminal 2. Fails to launch 3. Gives error "amarok: error while loading shared libraries: libavformat.so.59: cannot open shared object file: No such file or directory" OBSERVED RESULT Fails to start, Gives error "amarok: error while loading shared libraries: libavformat.so.59: cannot open shared object file: No such file or directory" EXPECTED RESULT Amarok launches and does not insta-crash. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: 5.27.2 KDE Frameworks Version: 5.103.0 Qt Version: 5.15.8 ADDITIONAL INFORMATION Because I'm on Arch, I get Amarok from the AUR. -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 447385] After KDE connect starts, calling org.freedesktop.Notifications.Notify returns incorrect ids when replaceId=0, making replacing notifications impossible
https://bugs.kde.org/show_bug.cgi?id=447385 Fushan Wen changed: What|Removed |Added Latest Commit||https://invent.kde.org/netw ||ork/kdeconnect-kde/commit/4 ||523ba588276bc5d2bc7f0e11cf3 ||9743efeca263 Status|ASSIGNED|RESOLVED Version Fixed In||23.08 Resolution|--- |FIXED --- Comment #4 from Fushan Wen --- Git commit 4523ba588276bc5d2bc7f0e11cf39743efeca263 by Fushan Wen. Committed on 13/03/2023 at 02:20. Pushed by fusionfuture into branch 'master'. Use `org.freedesktop.DBus.Monitoring` to monitor notifications Plasma notification widget also uses the interface, and sometimes notification ids can become out of sync between the two DBus adaptors. FIXED-IN: 23.08 M +1-0CMakeLists.txt M +1-0plugins/sendnotifications/CMakeLists.txt M +169 -69 plugins/sendnotifications/notificationslistener.cpp M +10 -7plugins/sendnotifications/notificationslistener.h https://invent.kde.org/network/kdeconnect-kde/commit/4523ba588276bc5d2bc7f0e11cf39743efeca263 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 463379] Double Monitor: Lock-screen, after some indefinite amount of time, will fail to actually display when the machine is taken out of sleep due to kwin_x11 abort
https://bugs.kde.org/show_bug.cgi?id=463379 Maluchi Ugokwe Jr. changed: What|Removed |Added Status|REOPENED|RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 467174] On fresh Arch install with Firefox installed, nothing is set as default web browser
https://bugs.kde.org/show_bug.cgi?id=467174 Aleix Pol changed: What|Removed |Added Component|general |kcm_componentchooser Product|xdg-desktop-portal-kde |systemsettings -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 467259] New: autoconnecting to captive portal enabled network makes session unuseable
https://bugs.kde.org/show_bug.cgi?id=467259 Bug ID: 467259 Summary: autoconnecting to captive portal enabled network makes session unuseable Classification: Plasma Product: plasmashell Version: master Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: lucamigna...@icloud.com CC: k...@davidedmundson.co.uk Target Milestone: 1.0 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 *** If Plasma is configured to automatically connect to a network which has a captive portal when a user launches a wayland session plasma breaks. STEPS TO REPRODUCE 1. set up your wifi to use a captive portal 2. set that network as default in system settings 3. relog in to your session OBSERVED RESULT the bottom panel goes away then reappears repeatedly until eventually it doesnt come back and the windows begin drawing behind them as they get dragged around EXPECTED RESULT a notification should appear asking the user to log in and all should proceed as normal. SOFTWARE/OS VERSIONS Linux/KDE Plasma: OpenSuse TW/linux 6.2.2 (available in About System) KDE Plasma Version: 5.27.2 KDE Frameworks Version: 5.103.0 Qt Version: 5.15.8 ADDITIONAL INFORMATION I have an rx 6800xt gpu, and a MediaTek MT7922 wifi card. The network is Wifi 6. An eero router is in use which means the 2.4g and 5g bands use the same ssid. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 467258] New: Dolphin randomly cannot run Appimages.
https://bugs.kde.org/show_bug.cgi?id=467258 Bug ID: 467258 Summary: Dolphin randomly cannot run Appimages. Classification: Applications Product: dolphin Version: 22.12.3 Platform: Archlinux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: gigastarcra...@proton.me CC: kfm-de...@kde.org Target Milestone: --- SUMMARY For some reason every once in a while I cannot run AppImages through Dolphin but I can through terminal or other file manager i.e. Nemo. STEPS TO REPRODUCE 1. Try to run AppImage. 2. I get an error "The command could not be found". 3. Sometimes restart helps. OBSERVED RESULT Error: "The command could not be found" EXPECTED RESULT One could run AppImage through Dolphin without problems. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Artix Linux 6.2.2-artix1-1 KDE Plasma Version: 5.27.2 KDE Frameworks Version: 5.103.0 Qt Version: 5.15.8 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 464967] dolphin process for another user (using kdesu) crashes after screen wake
https://bugs.kde.org/show_bug.cgi?id=464967 --- Comment #8 from Dick Tracey --- These look like the same issue maybe? https://bugs.kde.org/show_bug.cgi?id=463475 https://bugs.kde.org/show_bug.cgi?id=467191 -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 464967] dolphin process for another user (using kdesu) crashes after screen wake
https://bugs.kde.org/show_bug.cgi?id=464967
--- Comment #7 from Dick Tracey ---
I see, thanks anyway!
Here's a bit more useful crash log after I installed missing debug symbols
Application: Dolphin (dolphin), signal: Segmentation fault
Content of s_kcrashErrorMessage: std::unique_ptr = {get() = }
[KCrash Handler]
#6 __memcpy_avx_unaligned_erms () at
../sysdeps/x86_64/multiarch/memmove-vec-unaligned-erms.S:265
#7 0x7fb70e1275d3 in memmove (__len=262112, __src=0x7fb2398be810,
__dest=) at /usr/include/bits/string_fortified.h:36
#8 copy_unswapped (rect=..., img=...,
dstBytesPerLine=262112, dst=) at
/usr/src/debug/qt5-base/qtbase/src/plugins/platforms/xcb/qxcbbackingstore.cpp:547
#9 native_sub_image (swap=false, rect=..., src=...,
dstStride=262112, buffer=0x560be64c3660) at
/usr/src/debug/qt5-base/qtbase/src/plugins/platforms/xcb/qxcbbackingstore.cpp:590
#10 QXcbBackingStoreImage::flushPixmap (this=this@entry=0x560be64c35e0,
region=..., fullRegion=) at
/usr/src/debug/qt5-base/qtbase/src/plugins/platforms/xcb/qxcbbackingstore.cpp:669
#11 0x7fb70e127913 in QXcbBackingStoreImage::flushPixmap
(fullRegion=fullRegion@entry=true, this=this@entry=0x560be64c35e0, region=...,
fullRegion=fullRegion@entry=true) at
/usr/src/debug/qt5-base/qtbase/src/plugins/platforms/xcb/qxcbbackingstore.cpp:690
#12 0x7fb70e127b77 in QXcbBackingStoreImage::flushPixmap (fullRegion=false,
region=..., this=0x560be64c35e0) at
/usr/src/debug/qt5-base/qtbase/src/plugins/platforms/xcb/qxcbbackingstore.cpp:627
#13 QXcbBackingStoreImage::put (this=0x560be64c35e0, dst=83886089, region=...,
offset=...) at
/usr/src/debug/qt5-base/qtbase/src/plugins/platforms/xcb/qxcbbackingstore.cpp:741
#14 0x7fb70e1284ce in QXcbBackingStore::flush
(this=this@entry=0x560be65fd960, window=window@entry=0x560be64a11d0,
region=..., offset=...) at
/usr/src/debug/qt5-base/qtbase/src/plugins/platforms/xcb/qxcbwindow.h:120
#15 0x7fb7146ddd45 in QBackingStore::flush (this=this@entry=0x7fb761a0,
region=..., window=0x560be64a11d0, offset=...) at
painting/qbackingstore.cpp:252
#16 0x7fb714d82e81 in QWidgetRepaintManager::flush
(this=this@entry=0x560be67547f0, widget=0x560be62fdf40, region=...,
widgetTextures=) at kernel/qwidgetrepaintmanager.cpp:1198
#17 0x7fb714d833d5 in QWidgetRepaintManager::flush
(this=this@entry=0x560be67547f0) at kernel/qwidgetrepaintmanager.cpp:1096
#18 0x7fb714d84ab9 in QWidgetRepaintManager::paintAndFlush
(this=0x560be67547f0) at kernel/qwidgetrepaintmanager.cpp:1028
#19 0x7fb714dd0f09 in QWidgetWindow::handleResizeEvent
(event=0x7ffe6fe45070, this=0x560be64a11d0) at kernel/qwidgetwindow.cpp:841
#20 QWidgetWindow::event (this=0x560be64a11d0, event=0x7ffe6fe45070) at
kernel/qwidgetwindow.cpp:322
#21 0x7fb714d78b5c in QApplicationPrivate::notify_helper (this=, receiver=0x560be64a11d0, e=0x7ffe6fe45070) at
kernel/qapplication.cpp:3640
#22 0x7fb71408df48 in QCoreApplication::notifyInternal2
(receiver=0x560be64a11d0, event=0x7ffe6fe45070) at
kernel/qcoreapplication.cpp:1064
#23 0x7fb71408dfd3 in QCoreApplication::sendSpontaneousEvent
(receiver=, event=) at
kernel/qcoreapplication.cpp:1474
#24 0x7fb714540206 in QGuiApplicationPrivate::processGeometryChangeEvent
(e=) at kernel/qguiapplication.cpp:2610
#25 0x7fb714528885 in QWindowSystemInterface::sendWindowSystemEvents
(flags=flags@entry=...) at kernel/qwindowsysteminterface.cpp:1169
#26 0x7fb70e12e8d0 in xcbSourceDispatch (source=) at
/usr/src/debug/qt5-base/qtbase/src/plugins/platforms/xcb/qxcbeventdispatcher.cpp:105
--
You are receiving this mail because:
You are watching all bug changes.
[kdeconnect] [Bug 446366] No way to send clipboard from Android to a desktop, if the persistent indicator is disabled.
https://bugs.kde.org/show_bug.cgi?id=446366 --- Comment #10 from Fabian --- (In reply to Neon from comment #9) > (In reply to Fabian from comment #8) > > Well, nevermind, I just didn't notice that that module has a UI in which you > > need to select which apps get that permission. Selecting KDE Connect in it > > fixes the issue. > > I'm using that same Magisk Module but KDE Connect still doesn't sync my > clipboard, I'm on Android 13 so I wonder if something changed in this > version. Android 13 is pretty new, any component might not be fully done yet. You should report it as a bug. I won't see it any time soon, I usually stay on at most the last release of LineageOS before a version jump, currently I'm even on the preinstalled Android 10. -- You are receiving this mail because: You are watching all bug changes.
[Tokodon] [Bug 467243] Certain ui elements prevent touch scrolling
https://bugs.kde.org/show_bug.cgi?id=467243 Carl Schwan changed: What|Removed |Added Status|REPORTED|CONFIRMED Ever confirmed|0 |1 -- You are receiving this mail because: You are watching all bug changes.
[Tokodon] [Bug 466441] No way to control notifications in Tokodon Flatpak version
https://bugs.kde.org/show_bug.cgi?id=466441 Aleix Pol changed: What|Removed |Added Resolution|--- |DUPLICATE CC||aleix...@kde.org Status|REPORTED|RESOLVED --- Comment #1 from Aleix Pol --- There's this MR, I still am not sure it's the way forward though. *** This bug has been marked as a duplicate of bug 457672 *** -- You are receiving this mail because: You are watching all bug changes.
[xdg-desktop-portal-kde] [Bug 457672] Spotify notifications (coming from plasma-workspace, through XDG portal) plays error sound
https://bugs.kde.org/show_bug.cgi?id=457672 Aleix Pol changed: What|Removed |Added CC||spry.bed7...@fastmail.com --- Comment #9 from Aleix Pol --- *** Bug 466441 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 446366] No way to send clipboard from Android to a desktop, if the persistent indicator is disabled.
https://bugs.kde.org/show_bug.cgi?id=446366 djneonni...@gmail.com changed: What|Removed |Added CC||djneonni...@gmail.com --- Comment #9 from djneonni...@gmail.com --- (In reply to Fabian from comment #8) > Well, nevermind, I just didn't notice that that module has a UI in which you > need to select which apps get that permission. Selecting KDE Connect in it > fixes the issue. I'm using that same Magisk Module but KDE Connect still doesn't sync my clipboard, I'm on Android 13 so I wonder if something changed in this version. -- You are receiving this mail because: You are watching all bug changes.
[Tokodon] [Bug 467205] -v doesn't print anything if tokodon is already running
https://bugs.kde.org/show_bug.cgi?id=467205 Carl Schwan changed: What|Removed |Added Resolution|--- |FIXED Latest Commit||https://invent.kde.org/netw ||ork/tokodon/commit/ec7565a0 ||ee59b6e45170192d50d7b8d753b ||7af72 Status|REPORTED|RESOLVED --- Comment #1 from Carl Schwan --- Git commit ec7565a0ee59b6e45170192d50d7b8d753b7af72 by Carl Schwan. Committed on 12/03/2023 at 23:36. Pushed by carlschwan into branch 'master'. Fix -v arg not working when tokodon is already running Signed-off-by: Carl Schwan M +8-8src/main.cpp https://invent.kde.org/network/tokodon/commit/ec7565a0ee59b6e45170192d50d7b8d753b7af72 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 467257] New: File layers do not get scaled when scaling document
https://bugs.kde.org/show_bug.cgi?id=467257 Bug ID: 467257 Summary: File layers do not get scaled when scaling document Classification: Applications Product: krita Version: 5.1.5 Platform: Microsoft Windows OS: Microsoft Windows Status: REPORTED Severity: normal Priority: NOR Component: Resize/Scale Image/Layer Assignee: krita-bugs-n...@kde.org Reporter: zoomula...@gmail.com Target Milestone: --- Created attachment 157224 --> https://bugs.kde.org/attachment.cgi?id=157224=edit A test image + a series of 3 images showing the unexpected behavior SUMMARY Using file layers in a document and scaling the image either by "image -> scale image to new size" or via the "file -> export advanced" will result in the file-layers being cropped to the new size instead of scaled. STEPS TO REPRODUCE 1. Add a File Layer to a Krita document. I imported PNG files. 2. Scale the image to a new size, like 50% 3. The image's dimensions are changed but the file layer is just cropped instead of scaled. OBSERVED RESULT The file layer is not scaled with the rest of the image EXPECTED RESULT The contents of the file layer should match the new scale of the image SOFTWARE/OS VERSIONS Windows: 10 ADDITIONAL INFORMATION This is possibly related to an old bug 349821 where transforming file layers seems out of the question at first but is later marked as resolved fixed. -- You are receiving this mail because: You are watching all bug changes.
[marble] [Bug 467256] New: Incorrect hover color used in Map View
https://bugs.kde.org/show_bug.cgi?id=467256 Bug ID: 467256 Summary: Incorrect hover color used in Map View Classification: Applications Product: marble Version: 22.12.3 Platform: Kubuntu OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: general Assignee: marble-b...@kde.org Reporter: zechariah_bo...@protonmail.com Target Milestone: --- Created attachment 157223 --> https://bugs.kde.org/attachment.cgi?id=157223=edit Wrong color in MapView shown SUMMARY An incorrect hover color can be seen located in Map View that only affects some color schemes. Hovering over an element in Map View produces a bright grayish color that does not exist in that color scheme. I have singled out that the color is affected by BackgroundNormal in [Colors:Window]. None of the default KDE breeze or Krita color schemes are affected because they are too bright for this bug to trigger. It only occurs if BackgroundNormal is very low in rgb value. HOW TO REPRODUCE Create a copy of any color scheme you have. Breeze Dark will do fine. Change BackgroundNormal in [Colors:Window] to one of the two values below. BackgroundNormal=15,12,12 Results in the bug. Setting to 0,0,0 works as well. BackgroundNormal=31,31,31 Results in an apparent "proper" color. OBSERVED RESULT Wrong color is present when hovering over an element in MapView. EXPECTED RESULT Color should be derived from the focus/hover decoration color. SYSTEM INFORMATION Operating System: Kubuntu 22.10 KDE Plasma Version: 5.25.5 KDE Frameworks Version: 5.98.0 Qt Version: 5.15.6 Kernel Version: 5.19.0-35-generic (64-bit) Graphics Platform: Wayland Processors: 16 × AMD Ryzen 7 5800H with Radeon Graphics Memory: 27.3 GiB of RAM Graphics Processor: RENOIR Manufacturer: LENOVO Product Name: 82JW System Version: Legion 5 15ACH6 -- You are receiving this mail because: You are watching all bug changes.
[kalgebra] [Bug 355295] input fields' font color does not change to a move visible color for dark themes
https://bugs.kde.org/show_bug.cgi?id=355295 a...@absolutelyfree.me changed: What|Removed |Added Version|unspecified |22.12.3 -- You are receiving this mail because: You are watching all bug changes.
[kalgebra] [Bug 355295] input fields' font color does not change to a move visible color for dark themes
https://bugs.kde.org/show_bug.cgi?id=355295 a...@absolutelyfree.me changed: What|Removed |Added CC||a...@absolutelyfree.me --- Comment #3 from a...@absolutelyfree.me --- This bug is still present in KAlgebra version 22.12.3, KDE Frameworks version 5.103.0 Until this is fixed, a suitable workaround would be: 1. Install Kvantum 2. Set a non-dark theme in Kvantum Manager 3. Right click on your application menu and click edit applications 4. Navigate to the launcher for KAlgebra and set the environment variables value to the following: QT_STYLE_OVERRIDE=kvantum This will allow you to use a lighter theme of your choosing for this application specifically. -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 467255] New: Kate crashing when clicking "clear" in the bottom textbox on the find/replace window
https://bugs.kde.org/show_bug.cgi?id=467255 Bug ID: 467255 Summary: Kate crashing when clicking "clear" in the bottom textbox on the find/replace window Classification: Applications Product: kate Version: 22.08.2 Platform: Other OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kwrite-bugs-n...@kde.org Reporter: amberboot...@gmail.com Target Milestone: --- Application: kate (22.08.2) Qt Version: 5.15.6 Frameworks Version: 5.99.0 Operating System: Linux 5.13.0-valve36-1-neptune x86_64 Windowing System: X11 Distribution: SteamOS DrKonqi: 5.26.1 [KCrashBackend] -- Information about the crash: When clicking "clear" on the bottom textbox, Kate always craashes for me. This issue is not a one time occurance as it happens everytime I do it. The crash can be reproduced every time. -- Backtrace: Application: Kate (kate), signal: Segmentation fault [KCrash Handler] #4 0x7f0221d24fb8 in ?? () from /usr/lib/libQt5Core.so.5 #5 0x7f0221caee92 in QAbstractItemModel::modelAboutToBeReset(QAbstractItemModel::QPrivateSignal) () from /usr/lib/libQt5Core.so.5 #6 0x7f0202e3a92b in ?? () from /usr/lib/qt/plugins/ktexteditor/katesearchplugin.so #7 0x7f0202e59475 in ?? () from /usr/lib/qt/plugins/ktexteditor/katesearchplugin.so #8 0x7f0221d25381 in ?? () from /usr/lib/libQt5Core.so.5 #9 0x7f02228ccec7 in QAction::triggered(bool) () from /usr/lib/libQt5Widgets.so.5 #10 0x7f02228d28c7 in QAction::activate(QAction::ActionEvent) () from /usr/lib/libQt5Widgets.so.5 #11 0x7f0222a54e3b in ?? () from /usr/lib/libQt5Widgets.so.5 #12 0x7f0222a54f5d in ?? () from /usr/lib/libQt5Widgets.so.5 #13 0x7f02229106e7 in QWidget::event(QEvent*) () from /usr/lib/libQt5Widgets.so.5 #14 0x7f02228d9b1c in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib/libQt5Widgets.so.5 #15 0x7f02228df339 in QApplication::notify(QObject*, QEvent*) () from /usr/lib/libQt5Widgets.so.5 #16 0x7f0221cf4b88 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /usr/lib/libQt5Core.so.5 #17 0x7f02228dd337 in QApplicationPrivate::sendMouseEvent(QWidget*, QMouseEvent*, QWidget*, QWidget*, QWidget**, QPointer&, bool, bool) () from /usr/lib/libQt5Widgets.so.5 #18 0x7f022292e894 in ?? () from /usr/lib/libQt5Widgets.so.5 #19 0x7f022293015e in ?? () from /usr/lib/libQt5Widgets.so.5 #20 0x7f02228d9b1c in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib/libQt5Widgets.so.5 #21 0x7f0221cf4b88 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /usr/lib/libQt5Core.so.5 #22 0x7f03913c in QGuiApplicationPrivate::processMouseEvent(QWindowSystemInterfacePrivate::MouseEvent*) () from /usr/lib/libQt5Gui.so.5 #23 0x7f022985 in QWindowSystemInterface::sendWindowSystemEvents(QFlags) () from /usr/lib/libQt5Gui.so.5 #24 0x7f021c0596c0 in ?? () from /usr/lib/libQt5XcbQpa.so.5 #25 0x7f021f98181b in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0 #26 0x7f021f9d7ec9 in ?? () from /usr/lib/libglib-2.0.so.0 #27 0x7f021f9800d2 in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0 #28 0x7f0221d3f50c in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/libQt5Core.so.5 #29 0x7f0221ced32c in QEventLoop::exec(QFlags) () from /usr/lib/libQt5Core.so.5 #30 0x7f0221cf7e59 in QCoreApplication::exec() () from /usr/lib/libQt5Core.so.5 #31 0x559377d615d5 in ?? () #32 0x7f022166d290 in ?? () from /usr/lib/libc.so.6 #33 0x7f022166d34a in __libc_start_main () from /usr/lib/libc.so.6 #34 0x559377d63af5 in ?? () [Inferior 1 (process 13098) detached] Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 450301] On KWin 5.24 X11 Nvidia, when reenabling compositing, windows begin flickering and flipping upside-down
https://bugs.kde.org/show_bug.cgi?id=450301 ghoste changed: What|Removed |Added CC||jsbay...@protonmail.com --- Comment #11 from ghoste --- I had this issue with Plasma 5.25 and maybe 5.24, but I think it stopped happening after upgrading to Plasma 5.26. I'm now running Plasma 5.27.2 and was unable to reproduce it after disabling and re-enabling the compositor 10 times in X11. Using NVIDIA driver 525.89.02. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 467254] Kdenlive attempts to transcode a clip, crashes and produces a large file in the background
https://bugs.kde.org/show_bug.cgi?id=467254 Bug Janitor Service changed: What|Removed |Added Severity|normal |crash -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 452707] [Wayland] Moving files from one partition to another with Dolphin results in a Plasma memory leak that can potentially make the whole computer unusable
https://bugs.kde.org/show_bug.cgi?id=452707 kqnum changed: What|Removed |Added Resolution|--- |FIXED Status|CONFIRMED |RESOLVED --- Comment #5 from kqnum --- Having tested moving files from one partition to another on Wayland, with btrfs, I can also confirm that the memory is no longer leaked. There is still some CPU usage after the file is moved, but the CPU usage is returned to normal after cutting a file, copying a file, or closing the Dolphin window that started that operation. Operating System: EndeavourOS KDE Plasma Version: 5.27.2 KDE Frameworks Version: 5.103.0 Qt Version: 5.15.8 Graphics Platform: Wayland -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kwallet] [Bug 458085] Wallet system takes about 1 minute to start
https://bugs.kde.org/show_bug.cgi?id=458085 --- Comment #62 from michaelk83 --- (In reply to Thiago Macieira from comment #61) > A proper implementation would realise that > the request for GPG to open the wallet is still pending and queue the > request to be answered when the wallet got opened. So the request from pinentry gets queued and waits for the wallet to unlock, which is waiting on pinentry to return the passphrase. It just brings us back to the synchronous deadlock we have now. (In fact, the queuing behavior may very well be how it's actually implemented currently. Though I can't say for sure.) > It also wouldn't work if I had my ~/.gnupg directory protected against > unwanted reads and writes. The proposed patch doesn't attempt to write to ~/.gnupg directly. It makes calls to gpgconf. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 467087] Unable to start Valgrind due to error (MMAP)
https://bugs.kde.org/show_bug.cgi?id=467087 --- Comment #6 from varun.yet...@cohere-technologies.com --- Thanks Paul. There seems to be a lot of such objects with small size. nm -f sysv -e ../bin/cpcc > sym_info.txt [yeturva@ran6 source]$ cat sym_info.txt | grep "d |" | wc -l 2415 For reference, one of them is as follows: aead_des_ede3_cbc_sha1_tls_implicit_iv|059f2cc0| d | OBJECT|0048| |.data.rel.ro Are you referring to the above? Regards, Varun From: Paul Floyd Date: Saturday, March 11, 2023 at 12:44 PM To: Varun Reddy Yeturu Subject: [valgrind] [Bug 467087] Unable to start Valgrind due to error (MMAP) https://bugs.kde.org/show_bug.cgi?id=467087 --- Comment #5 from Paul Floyd --- (In reply to varun.yeturu from comment #4) > Created attachment 157192 [details] > attachment-229496-0.html > > Sure. > I compile with “-debug -O0 -g” flags. > > [yeturva@ran6 source]$ size ../bin/cpcc >textdatabss dechexfilenameTyp > 8795682838388813069709208 13158049924 > 31047e884 ../bin/cpcc 13 Gbytes of BSS, could be the problem Can you see where you are creating that? It's probably a file static array. If you run "nm -f sysv -e" on your executable there will be a column with the size, and look for something that is Class d and Type OBJECT/ Can you reduce the size of that static object? -- You are receiving this mail because: You reported the bug. -- You are receiving this mail because: You are watching all bug changes.
[Falkon] [Bug 391298] Kwallet extension save password in binary mode instead text
https://bugs.kde.org/show_bug.cgi?id=391298 Juraj changed: What|Removed |Added Latest Commit|https://invent.kde.org/netw |https://invent.kde.org/netw |ork/falkon/commit/6a258adc3 |ork/falkon/commit/261bef6d6 |15f78f7bd2f25db25248865690c |5d90ae6893e9a22a653355f3491 |e27f|e71c --- Comment #11 from Juraj --- Git commit 261bef6d65d90ae6893e9a22a653355f3491e71c by Juraj Oravec. Committed on 12/03/2023 at 22:03. Pushed by jurajo into branch 'release/23.04'. KWallet: Store passwords entries in map fortmat FIXED-IN: 23.04.0 Signed-off-by: Juraj Oravec M +69 -39 src/plugins/KDEFrameworksIntegration/kwalletpasswordbackend.cpp https://invent.kde.org/network/falkon/commit/261bef6d65d90ae6893e9a22a653355f3491e71c -- You are receiving this mail because: You are watching all bug changes.
[Falkon] [Bug 391298] Kwallet extension save password in binary mode instead text
https://bugs.kde.org/show_bug.cgi?id=391298 Juraj changed: What|Removed |Added Latest Commit|https://invent.kde.org/netw |https://invent.kde.org/netw |ork/falkon/commit/52ae23a36 |ork/falkon/commit/6a258adc3 |b3e61e5a293de7c4ac517492e49 |15f78f7bd2f25db25248865690c |c67f|e27f --- Comment #10 from Juraj --- Git commit 6a258adc315f78f7bd2f25db25248865690ce27f by Juraj Oravec. Committed on 12/03/2023 at 22:00. Pushed by jurajo into branch 'master'. KWallet: Store passwords entries in map fortmat FIXED-IN: 23.04.0 Signed-off-by: Juraj Oravec M +69 -39 src/plugins/KDEFrameworksIntegration/kwalletpasswordbackend.cpp https://invent.kde.org/network/falkon/commit/6a258adc315f78f7bd2f25db25248865690ce27f -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 467254] New: Kdenlive attempts to transcode a clip, crashes and produces a large file in the background
https://bugs.kde.org/show_bug.cgi?id=467254
Bug ID: 467254
Summary: Kdenlive attempts to transcode a clip, crashes and
produces a large file in the background
Classification: Applications
Product: kdenlive
Version: 22.12.3
Platform: openSUSE
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: Video Display & Export
Assignee: j...@kdenlive.org
Reporter: fritz.seiff...@protonmail.com
Target Milestone: ---
(Seems like Dr Konqi can't receive tokens or otherwise can't report bugs right
now, so I copied the text and threw it in here):
Application: kdenlive (21.12.3)
Qt Version: 5.15.2
Frameworks Version: 5.90.0
Operating System: Linux 5.14.21-150400.24.46-default x86_64
Windowing System: X11
Distribution: "openSUSE Leap 15.4"
DrKonqi: 5.24.4 [KCrashBackend]
-- Information about the crash:
- What I was doing when the application crashed:
I was trying to add a clip to a new Kdenlive (size: 37.7 MiB). For no reason to
my knowledge the program informed me that I would have had to transcode the
clip (the recording settings were - to my knowledge - no different from
anything else). Both upon clicking the cancel and the ok buttons the program
crashes every time. The choicebox had the default ("Lossy x264 I frame only").
In the background (that is to say without an open Kdenlive window) there was
now a large file named "2023-03-06 22-36-260001.mp4" (the original file was
called "2023-03-06 22-36-26.mp4") being generated over several seconds, worth
884.1 MiB. As far as I can tell content of the files remains identical with one
exception: It seems only the first of the 2 audio streams of the original file
survived. I wasn not able to hear any changes in the first audio stream either.
Upon reopening Kdenlive it offered me to restore the most recent project. Doing
so loads the project with the original clip and it does indeed play, but
skipping through the timeline seems to desync the marker in the timeline and
the video being played, possibly only when skipping to a previous point but I'm
not 100% sure on that.
The only other differences when examining the original and "transcoded" file in
the project's clip properties were the bitrates: The old file had 250 kB/s
audio and 1889 kB/s video, the new one has 202 kB/s audio and 44096 kB/s video.
The video was being recorded with OBS, codec x264 quality regulation set to
CRF, CRF set to 23, keyframe interval automatic, ultrafast preset.
In the clip properties the Audio-Codec was AAC 48000 Hz, , 1920x1080 at 60 FPS,
color spectrum ITU-R BT.709, 1.000 PAR, pixel format yuv420p, video codec H.264
(the last part I may understand incorrectly, but maybe I need to check my OBS
settings because it's supposed to be x264, should it not? Though both are valid
video codexes, so I suppose it has no relevance here).
Both files open and play normally (tested with VLC Media Player), thus I would
not exepct the file to have gotten corrupted in the meantime.
The crash can be reproduced every time.
-- Backtrace:
Application: Kdenlive (kdenlive), signal: Segmentation fault
[KCrash Handler]
#4 doActivate(QObject*, int, void**) (sender=0x558491706b50,
signal_index=7, argv=0x7ffe3e1773a0) at kernel/qobject.cpp:3770
#5 0x7f3f44751782 in QMetaObject::activate(QObject*, QMetaObject const*,
int, void**) (sender=, m=m@entry=0x7f3f46a6b720
, local_signal_index=local_signal_index@entry=0,
argv=argv@entry=0x7ffe3e1773a0) at kernel/qobject.cpp:3946
#6 0x7f3f4656b13e in QDialog::finished(int) (this=,
_t1=) at .moc/moc_qdialog.cpp:230
#7 0x7f3f44757fa9 in doActivate(QObject*, int, void**)
(sender=0x558491810340, signal_index=10, argv=0x7ffe3e177460) at
kernel/qobject.cpp:3898
#8 0x7f3f44751782 in QMetaObject::activate(QObject*, QMetaObject const*,
int, void**) (sender=sender@entry=0x558491810340, m=m@entry=0x7f3f46a646a0
,
local_signal_index=local_signal_index@entry=3, argv=argv@entry=0x0) at
kernel/qobject.cpp:3946
#9 0x7f3f46502cf3 in QDialogButtonBox::rejected()
(this=this@entry=0x558491810340) at .moc/moc_qdialogbuttonbox.cpp:299
#10 0x7f3f46503368 in QDialogButtonBoxPrivate::_q_handleButtonClicked()
(this=) at widgets/qdialogbuttonbox.cpp:882
#11 0x7f3f44757fa9 in doActivate(QObject*, int, void**)
(sender=0x5584946e0130, signal_index=9, argv=0x7ffe3e1775d0) at
kernel/qobject.cpp:3898
#12 0x7f3f44751782 in QMetaObject::activate(QObject*, QMetaObject const*,
int, void**) (sender=sender@entry=0x5584946e0130, m=m@entry=0x7f3f46a5b4e0
,
local_signal_index=local_signal_index@entry=2, argv=argv@entry=0x7ffe3e1775d0)
at kernel/qobject.cpp:3946
#13 0x7f3f4645d772 in QAbstractButton::clicked(bool)
(this=this@entry=0x5584946e0130, _t1=) at
.moc/moc_qabstractbutton.cpp:308
#14 0x7f3f4645d98a in QAbstractButtonPrivate::emitClicked()
(this=0x5584946e0170) at widgets/qabstractbutton.cpp:415
[frameworks-kwallet] [Bug 458085] Wallet system takes about 1 minute to start
https://bugs.kde.org/show_bug.cgi?id=458085 --- Comment #61 from Thiago Macieira --- (In reply to michaelk83 from comment #60) > Pinentry is asking for the passphrase through the same Secret Service API as > any other client (see comment 31). KWallet has no way to tell it apart from > any other client, so can't handle it differently. As far as KWallet can tell > at this point, the passphrase that pinentry wants is inside the same wallet > (but it's not). That is understood. I did say that my idea would only work if there were a way to break the loop. If there isn't, then it doesn't help. > Currently pinentry's request blocks in the `OpenSession` call because > KWallet is still waiting for GPG to unlock the wallet (for the original > request of some other client app). If this was asynchronous, what would > happen is KWallet would try to unlock the wallet a 2nd time to look for the > passphrase there, which would invoke GPG and pinentry a 2nd time, which > would ask KWallet again, and so on and on and on. Only if it got coded this poorly. A proper implementation would realise that the request for GPG to open the wallet is still pending and queue the request to be answered when the wallet got opened. So the loop breaks, but doesn't solve the problem. > > But not the way you described it. Modifying ~/.gnupg/gpg-agent.conf is not > > acceptable, because it's not atomic. > > Yes, as I said, there could be timing issues and maybe other problems. That > patch is still just an automated and time-limited workaround. > I'm not aware of any other way to tell pinentry to not use the external > cache, other than maybe by implementing the Assuan protocol. It also wouldn't work if I had my ~/.gnupg directory protected against unwanted reads and writes. I really think we need to talk to the gpg-agent/pinentry folks. -- You are receiving this mail because: You are watching all bug changes.
[Elisa] [Bug 458090] Elisa start problem
https://bugs.kde.org/show_bug.cgi?id=458090 Nelson Fonseca changed: What|Removed |Added CC||nelsin...@gmail.com --- Comment #5 from Nelson Fonseca --- Hi all, I do have the same issue on my Arch Linux. How was it resolved? Thanks a lot! -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 467253] Add a "energy saving" button to general settings and/or battery popup
https://bugs.kde.org/show_bug.cgi?id=467253 --- Comment #1 from Henning --- If possible a TLP integration would be great too. Even if it was just adding "tlp start" to the executed scripts on battery mode -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 467253] New: Add a "energy saving" button to general settings and/or battery popup
https://bugs.kde.org/show_bug.cgi?id=467253 Bug ID: 467253 Summary: Add a "energy saving" button to general settings and/or battery popup Classification: Applications Product: systemsettings Version: 5.27.2 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: amanita+kdeb...@mailbox.org Target Milestone: --- SUMMARY This could be a really useful feature. I would imagine the energy saving like: - disable all animations (set the speed to max does that right? - disable all kwin effects that use shaders, transparency or animations - set screen turn off to 1min on battery - reduce number of background apps - dont check for updates or appy updates Things users could enable/disable - change power_profiles_daemon to use energy saving mode - set OLED black theme (for some devices, plasma mobile etc. future stuff) -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 453147] amdgpu: GPU reset crash loop
https://bugs.kde.org/show_bug.cgi?id=453147 --- Comment #10 from Firlaev-Hans --- I've recently been getting similar KWin hangs with an Intel iGPU whenever it resets (very frequently) kernel: i915 :00:02.0: [drm] GPU HANG: ecode 12:1:87b2bef9, in plasmashell [2627] kernel: i915 :00:02.0: [drm] Resetting chip for stopped heartbeat on rcs0 kernel: i915 :00:02.0: [drm] plasmashell[2627] context reset due to GPU hang kernel: i915 :00:02.0: [drm] GuC firmware i915/adlp_guc_70.bin version 70.5.1 kernel: i915 :00:02.0: [drm] HuC firmware i915/tgl_huc.bin version 7.9.3 kernel: i915 :00:02.0: [drm] HuC authenticated kernel: i915 :00:02.0: [drm] GuC submission enabled kernel: i915 :00:02.0: [drm] GuC SLPC enabled kwin_wayland[2443]: kwin_scene_opengl: A graphics reset not attributable to the current GL context occurred. kwin_wayland[2443]: OpenGL vendor string: Intel kwin_wayland[2443]: OpenGL renderer string: Mesa Intel(R) Graphics (ADL GT2) kwin_wayland[2443]: OpenGL version string: 4.6 (Core Profile) Mesa 22.3.6 kwin_wayland[2443]: OpenGL shading language version string: 4.60 kwin_wayland[2443]: Driver: Intel kwin_wayland[2443]: GPU class: Unknown kwin_wayland[2443]: OpenGL version: 4.6 kwin_wayland[2443]: GLSL version: 4.60 kwin_wayland[2443]: Mesa version: 22.3.6 kwin_wayland[2443]: X server version: 1.22.1 kwin_wayland[2443]: Linux kernel version: 6.1.15 kwin_wayland[2443]: Requires strict binding:no kwin_wayland[2443]: GLSL shaders: yes kwin_wayland[2443]: Texture NPOT support: yes kwin_wayland[2443]: Virtual Machine:no ... and then everything starting from the first "kwin_wayland" line is repeated infinitely. -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 467252] New: Clipboard nomenclature for next and previous is confusing
https://bugs.kde.org/show_bug.cgi?id=467252 Bug ID: 467252 Summary: Clipboard nomenclature for next and previous is confusing Classification: I don't know Product: kde Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: david.cortes.riv...@gmail.com Target Milestone: --- SUMMARY The KDE clipboard has shortcuts for "Next History Item" and "Previous History Item", but the naming is confusing - if I think of "next" and "previous", the first thing I think is the chronological order in which I put the items into the clipboard, but in history order, this works the other way around. STEPS TO REPRODUCE 1. Try to assign shortcuts for next and previous items in the clipboard. OBSERVED RESULT Shortcuts are for "next/previous in history" which is the opposite of chronological order. EXPECTED RESULT Should have shortcuts for "next item" and "previous item" in the order that they were sent to the clipboard. 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 467192] Folders are opened in new tab but should open in new window
https://bugs.kde.org/show_bug.cgi?id=467192 --- Comment #4 from Kevin --- I don't know who is responsible for what. But 22.04 is the most recent LTS version, and there I except that bugs get fixed. I don't except new features, but bugfixes. That is the reason why I'm choosing a LTS Version. I want a stable system with as few bugs as possible, and for that I sacrifice to not always having the latest features. I would expect that when for what ever reason a Dophin 21.12.3 comes into the LTS Releases, that there will be a update to 21.12.4 fixing bugs. Especially bugs big enough to annoy me every day -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 432264] In multi-monitor setups with differenlty scaled displays, Context menus have items which are invisible until hovered
https://bugs.kde.org/show_bug.cgi?id=432264 Nicolas Fella changed: What|Removed |Added CC||e...@duck.com --- Comment #53 from Nicolas Fella --- *** Bug 467203 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 467203] context menu on multi monitor with scaling
https://bugs.kde.org/show_bug.cgi?id=467203 Nicolas Fella changed: What|Removed |Added CC||nicolas.fe...@gmx.de Resolution|--- |DUPLICATE Status|REPORTED|RESOLVED --- Comment #3 from Nicolas Fella --- *** This bug has been marked as a duplicate of bug 432264 *** -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 467030] Some icons and icons states doesn't have color consistency with the rest of the window when titlebars accent-colored is used
https://bugs.kde.org/show_bug.cgi?id=467030 Nate Graham changed: What|Removed |Added CC||ngomp...@gmail.com --- Comment #3 from Nate Graham --- *** Bug 467251 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 467251] When configuring Breeze Light to make titlebars accent colored, buttons on the colored titlebar don't have visible hover outlines
https://bugs.kde.org/show_bug.cgi?id=467251 Nate Graham changed: What|Removed |Added Status|REPORTED|RESOLVED CC||n...@kde.org Resolution|--- |DUPLICATE --- Comment #2 from Nate Graham --- *** This bug has been marked as a duplicate of bug 467030 *** -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 467251] When configuring Breeze Light to make titlebars accent colored, buttons on the colored titlebar don't have visible hover outlines
https://bugs.kde.org/show_bug.cgi?id=467251 Nicolas Fella changed: What|Removed |Added Component|window decoration |QStyle CC||nicolas.fe...@gmx.de, ||noaha...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 467251] When configuring Breeze Light to make titlebars accent colored, buttons on the colored titlebar don't have visible hover outlines
https://bugs.kde.org/show_bug.cgi?id=467251 --- Comment #1 from Neal Gompa --- SUMMARY When configuring Breeze Light to make title bars accent colored, buttons on the colored title bars and toolbars don't have visible hover outlines, which makes it hard to tell if they're really buttons. -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 467251] New: When configuring Breeze Light to make titlebars accent colored, buttons on the colored titlebar don't have visible hover outlines
https://bugs.kde.org/show_bug.cgi?id=467251 Bug ID: 467251 Summary: When configuring Breeze Light to make titlebars accent colored, buttons on the colored titlebar don't have visible hover outlines Classification: Plasma Product: Breeze Version: 5.27.2 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: window decoration Assignee: plasma-b...@kde.org Reporter: ngomp...@gmail.com CC: kwin-bugs-n...@kde.org, uhh...@gmail.com Target Milestone: --- Created attachment 157221 --> https://bugs.kde.org/attachment.cgi?id=157221=edit Screenshot of Konsole with mouse hovering over a button with a nearly invisible hover outline 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. Set an accent color 2. Configure Breeze Light to "make window titlebars accent-colored" OBSERVED RESULT Buttons in the titlebar + toolbar area do not have visible outlines when the mouse hovers over it. EXPECTED RESULT Buttons in the titlebar + toolbar area do have visible outlines when the mouse hovers over it. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Fedora Linux 37 (KDE Plasma) (available in About System) KDE Plasma Version: 5.27.2 KDE Frameworks Version: 5.103.0 Qt Version: 5.15.8 ADDITIONAL INFORMATION I've attached a screenshot with an example of the problem. -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 456210] Under certain circumstances when using multiple monitors, "unlock" button is clickable but does nothing
https://bugs.kde.org/show_bug.cgi?id=456210 stellarpo...@googlemail.com changed: What|Removed |Added CC||stellarpo...@googlemail.com --- Comment #72 from stellarpo...@googlemail.com --- I am also on Ubuntu 22.04 and Plasma 5.25.5 (wayland). I have not had any lock-screen issues so far (I'm not using it at all) but when I see Plasma crashes I have lines in the log in common with what is mentioned here. https://bugs.kde.org/show_bug.cgi?id=458469 I am seeing behaviour similar to in this bug and have added comments there; and someone else who was able to get 5.26 also saw that fix it. Am commenting in case there might be something in common between these issues, and something that has been resolved as of 5.26, but not in the 5.25 branch (which is the latest available for all Ubuntu LTS users, so a reasonably large number may encounter further problems) I see these lines in common (and searching for them has brought me here): - Creating a fake screen in order for Qt not to crash - requesting unexisting screen -1 - qt.qpa.wayland: Wayland does not support QWindow::requestActivate() - QMetaProperty::read: Unable to handle unregistered datatype 'KWin::SessionState' for property 'KWin::EffectsHandlerImpl::sessionState' - QML Connections: Detected function "onConfigurationChanged" in Connections element. This is probably intended to be a signal handler but no signal of the target matches the name. This is unrelated to the screenlocking, and often occurs when I power my display back on after being away form the PC for some time (fully on, not suspended); but I also experience this at times when there is a change in my desktop - e.g. opening a new application. - Cannot read property 'wallpaper' of null -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 467215] macOS 11.74 Big Sur: digikam crashes unexpectedly after launching G'MIC
https://bugs.kde.org/show_bug.cgi?id=467215 --- Comment #7 from No_Planet_2 --- Many thanks for the link, Gilles! You are right, it looks like a specific G'Mic bug indeed, so the issue can be closed from my view. I am glad that my old version in Gimp continues to work well, although X11 is not on my computer. https://github.com/c-koi/gmic-qt/issues/160#issuecomment-1465200447 Am also glad to have dipped a little into Debian, there are no problems. A standalone for macOS would be great, but I have little hope... Best Martin -- You are receiving this mail because: You are watching all bug changes.
[amarok] [Bug 465602] Search in audio library
https://bugs.kde.org/show_bug.cgi?id=465602 --- Comment #2 from Andreas --- Hi Tuomas My version of amarok is the latest from OpenSuse Tumbleweed: 2.9.75git.20221114T020258~457db492b4-1.3 but the same error occurs. Maybe there is an issue with the size of the library which is almost 400GB and I guess some 70k tracks. I could not try the version from KDE:Unstable:Extra since I just arrived today. But I will try it soon. Thanks and best regards Andreas Am 10.03.23 um 09:28 schrieb Tuomas Nurmi: > https://bugs.kde.org/show_bug.cgi?id=465602 > > Tuomas Nurmi changed: > > What|Removed |Added > > CC||tuo...@norsumanageri.org > > --- Comment #1 from Tuomas Nurmi --- > A fix forhttps://bugs.kde.org/show_bug.cgi?id=08 has been in GIT since > 7th > Feb 2023, and I'd believe this is the same bug. The most readily available > Amarok packages for openSUSE Tumbleweed seem to be > 2.9.75git.20221114T02 in repository KDE:Extra and > 2.9.75git.20230309T01 in repository KDE:Unstable:Extra > > Can you confirm / check from package management (or check from About Amarok -> > Build date) if the version you are using is an older build than 7th Feb 2023, > and if so, try if the newer version in KDE:Unstable:Extra works for you? > -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 458469] "Data too big for buffer" and clients exit when turning external monitor back on
https://bugs.kde.org/show_bug.cgi?id=458469 stellarpo...@googlemail.com changed: What|Removed |Added CC||stellarpo...@googlemail.com --- Comment #8 from stellarpo...@googlemail.com --- I am still able to reproduce this. I am on (stock server) Jammy Jellyfish and 5.25.5 from the KUbuntu backports *extra* PPA. Plasma seems to crash, without fail when I power off my display, go away to do something else, and then power it back on when I come back - but also spontaneously and irregularly. This typically occurs when I've done something that would cause a significant change in the window manager - e.g. opening a new application, moving a firefox tab to a new window, using a hot corner to show my open windows à la expo. Been a bit difficult trying to find the relevant log lines, I don't see anything blaring, but arrived here from that line about data being too big for a buffer. This was following a spontaneous crash, I don't think this line appears when I switch the display off and on again, but it happens so frequently I haven't yet managed to gather all the evidence and it's obviously a clear string to tug on. If there's a way I can easily get hold of a more recent build of Plasma I'm happy to try it out and see if I can confirm that whatever changes have happened stop it from reproducing or not, otherwise this is affecting me right now still. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 467006] a seperate cross cursor appears aligned with the cursor on the canvas
https://bugs.kde.org/show_bug.cgi?id=467006 tomtomtomreportin...@gmail.com changed: What|Removed |Added CC||tomtomtomreportingin@gmail. ||com Status|REPORTED|CONFIRMED Ever confirmed|0 |1 --- Comment #2 from tomtomtomreportin...@gmail.com --- Can confirm. I believe this crosshair is intended to be shown only when the brush preview outline is larger than the viewport. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 467249] Unwanted popup on login - wayland only
https://bugs.kde.org/show_bug.cgi?id=467249 rob.d...@telus.net changed: What|Removed |Added CC||rob.d...@telus.net -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 467221] Folder color switcher function
https://bugs.kde.org/show_bug.cgi?id=467221 --- Comment #7 from throwaway_to_k...@proton.me --- Created attachment 157219 --> https://bugs.kde.org/attachment.cgi?id=157219=edit Tag on the file/folder name (screenshot 3) -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 465707] Menu bar items not working
https://bugs.kde.org/show_bug.cgi?id=465707 Jack changed: What|Removed |Added Status|REPORTED|NEEDSINFO Resolution|--- |WAITINGFORINFO --- Comment #6 from Jack --- Adjusting state. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 467250] Dolphin crash every time I eject a CD
https://bugs.kde.org/show_bug.cgi?id=467250 Bug Janitor Service changed: What|Removed |Added Severity|normal |crash -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 467221] Folder color switcher function
https://bugs.kde.org/show_bug.cgi?id=467221 --- Comment #6 from throwaway_to_k...@proton.me --- Created attachment 157218 --> https://bugs.kde.org/attachment.cgi?id=157218=edit Tag Management Window (screenshot 2) -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 467221] Folder color switcher function
https://bugs.kde.org/show_bug.cgi?id=467221 --- Comment #5 from throwaway_to_k...@proton.me --- Created attachment 157217 --> https://bugs.kde.org/attachment.cgi?id=157217=edit Tag colors sidebar (screenshot1) -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 466972] Difficulty translating kmymoney.cpp i18n string "save storage"
https://bugs.kde.org/show_bug.cgi?id=466972 Jack changed: What|Removed |Added Version Fixed In|master |5.1.4 Latest Commit|https://invent.kde.org/offi |https://invent.kde.org/offi |ce/kmymoney/commit/c5e7d65a |ce/kmymoney/commit/67816e68 |5907f353e84e8dd0dc085ec160c |1a5b10ef46689841e6ce369658d |a3e9c |4dfce --- Comment #4 from Jack --- Git commit 67816e681a5b10ef46689841e6ce369658d4dfce by Jack Ostroff. Committed on 12/03/2023 at 18:28. Pushed by ostroffjh into branch '5.1'. Alter message wording to facilitate translation FIXED-IN: 5.1.4 Cherry-picked from c5e7d65a5907f353e84e8dd0dc085ec160ca3e9c M +3-3kmymoney/kmymoney.cpp https://invent.kde.org/office/kmymoney/commit/67816e681a5b10ef46689841e6ce369658d4dfce -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 467221] Folder color switcher function
https://bugs.kde.org/show_bug.cgi?id=467221 --- Comment #4 from throwaway_to_k...@proton.me --- I have tried to use this one but it just doesn't work, my problem with this design is that it gets too much screen space, the Nemo horizontal solution ideal, less menus and screen space means more effective work. I think tags may even have advantage with this ( X tag means X color), but tags as it is today are too slow and too much work for the kind of workflow i am talking about. Tags are very useful when things are already organized, not when you have to manually check 30.000 files. So: 1 - Nemo color switcher menu is a MUST, horizontal bar inside the context menu with nothing else, just "blue this" and "red that" is by far the best option. 2 - When it comes to tags to organize files, the MacOS tag manager is by far the best option (create a tag, associate a color to the tag, associate the file to the tag and the file gets the color accent), working organizing files for a long time i insist that tags are most useful when you have all files organized in the same folder ALREADY and basically useless when having different folders (and that's when color folder switcher shines). They are close, but not the same, let me give you a very simple example: I want to organize my files in folders like this: Audio, Video, Images. And i have folder inside folder inside folder... So i just go to a folder, switch to a color, move everything to that, then i just get every "blue" and move it to Audio, every "green" and move it to "Video" and every "red" and move it to "Images". Fast and simple. Now let's suppose i have a very specific tag called "fun/comedy", i can find content with this tag in all kinds of folders BUT it is faster when i am accessing the /Videos/Movies/ and i can see the tag for "fun/comedy" in a file and i can immediately find the "Adam Sandler" movie i was searching for. Get it? So tags are useful for specific files in the folder you are seeing and folder color switches are useful for large groups of files inside folders outside the folder you see atm. IF you want ME to make a case for the situation WITH TAGS, i can see a better solution BUT unless you have "color tags" by default (no color / no change, sand, yellow, orange, brown, red, purple, pink, blue, aqua, teal, grey) in a horizontal bar inside the context menu (just like Nemo or MacOS and nothing more, please), that 1 - changes folders colors AND 2 - shows the "" at the start of the name of the files and folders then they can't work together. But i have an idea for this... 1 - Put the "Tag" menu visible on the sidebar by default (or with an option to always turn on just like MacOS), for easy visualization (take a look at screenshot1) with the default colors (no color / no change, sand, yellow, orange, brown, red, purple, pink, blue, aqua, teal, grey) FROM THE START. The tag menu SHOULD have the "only show tag results inside the actual folder" option (so when i click red i don't see anything outside the folder atm). Explanation: If i am inside the /Videos/Movies/ folder and hit " Red" i can immediately find what i am searching for with 1 click. 2 - Change the "create a tag menu" to a "manage tags menu" that can associate tags with colors (and even no color/no change), rename, add or remove, enable and disable tags (just like MacOS, take a look at screenshot2). Explanation: For this to work the tags MUST be managed on their own and BEFORE attach to a file and not ON THE ACT to attach to a file, so outside the "create tag/attach tag" menu. 3 - Tags change the folder icon to the color associated with the tag which by default is (no color / no change , sand, yellow, orange, brown, red, purple, pink, blue, aqua, teal, grey), and always change the names of the files and folders to include the "" at the start of the name. If the folders have more than 1 tag then they use the default icon and just get the "" at the start of the name just like files. Explanation: This makes the "change folder color" work in the same context of the tags without the need to be a completely different thing and having the exact functionality as Nemo color switcher. Remember: - Files and folders MAY have more than 1 tag; - The tag should ALWAYS be visible at the start of the name of the file/folder (just like MacOS, take a look at screenshot3); - The files/folders should not lose the tag/color association if that tag is changed in any way (unless the tag is deleted of course); This way i can see they working together magically, but please throw away the "Create a tag" menu and let's have a "proper Tag Management Window" with the following functions: Associate tags with colors (and even no color/no change), rename, add or remove, enable and disable tags (cause sometimes you don't want to delete a tag but don't want that enabled either). This way i can just tag a color for something and then manage what the color means, with this workflow actions like "move
[frameworks-kwallet] [Bug 458085] Wallet system takes about 1 minute to start
https://bugs.kde.org/show_bug.cgi?id=458085 --- Comment #60 from michaelk83 --- (In reply to Thiago Macieira from comment #59) > But the fact is that if the query was asynchronous, then pinentry would have > got its answer instead of timing out, and then would have prompted the user > for the password. Pinentry is asking for the passphrase through the same Secret Service API as any other client (see comment 31). KWallet has no way to tell it apart from any other client, so can't handle it differently. As far as KWallet can tell at this point, the passphrase that pinentry wants is inside the same wallet (but it's not). Currently pinentry's request blocks in the `OpenSession` call because KWallet is still waiting for GPG to unlock the wallet (for the original request of some other client app). If this was asynchronous, what would happen is KWallet would try to unlock the wallet a 2nd time to look for the passphrase there, which would invoke GPG and pinentry a 2nd time, which would ask KWallet again, and so on and on and on. > But do note I talked about KWallet ensuring it doesn't recurse infinitely, > which is why we'd need to figure out if where this particular password > could be saved if it is provided to KWallet; refusing to store it is a way to > break the chain. This is the passphrase for KWallet itself (or rather for the GPG key that encrypts the wallet). It's not stored anywhere. The cycle is when trying to retrieve it, not store it. But as noted above, as long as pinentry makes the request via the Secret Service API, KWallet has no way to know that it's its own password that is being requested here. > Your idea from comment 40 -- to tell gpg-agent that we want a password with > no-external-cache -- is a solution too. Probably the Right Solution (with > capital R and S). > > But not the way you described it. Modifying ~/.gnupg/gpg-agent.conf is not > acceptable, because it's not atomic. Yes, as I said, there could be timing issues and maybe other problems. That patch is still just an automated and time-limited workaround. I'm not aware of any other way to tell pinentry to not use the external cache, other than maybe by implementing the Assuan protocol. -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 466972] Difficulty translating kmymoney.cpp i18n string "save storage"
https://bugs.kde.org/show_bug.cgi?id=466972 Jack changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |FIXED Version Fixed In||master Latest Commit||https://invent.kde.org/offi ||ce/kmymoney/commit/c5e7d65a ||5907f353e84e8dd0dc085ec160c ||a3e9c --- Comment #3 from Jack --- Git commit c5e7d65a5907f353e84e8dd0dc085ec160ca3e9c by Jack Ostroff. Committed on 12/03/2023 at 18:23. Pushed by ostroffjh into branch 'master'. Alter message wording to facilitate translation FIXED-IN: master M +3-3kmymoney/kmymoney.cpp https://invent.kde.org/office/kmymoney/commit/c5e7d65a5907f353e84e8dd0dc085ec160ca3e9c -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 467028] After attempt of opening a file unknown by system via ```"Choose Application" I get glitches when scrolling in Dolphin.
https://bugs.kde.org/show_bug.cgi?id=467028 --- Comment #3 from mitlaw2...@gmail.com --- Maybe bug is related to my screen resolution 3000 x 2000, 260 PPI. (HUAWEI MateBook X Pro 2021) -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 465489] Selection Mode still gets triggered by Space, even after reassigning the shortcut
https://bugs.kde.org/show_bug.cgi?id=465489 marge.ullric...@convergenceservice.com changed: What|Removed |Added CC||marge.ullrich55@convergence ||service.com --- Comment #8 from marge.ullric...@convergenceservice.com --- Please, please, please make the concept of "Selection Mode" + space bar behaviour an option to select in Dolphin Settings. Make it the default if you prefer, though please offer a way to disable "Selection Mode". Once upon a time, KDE was the pinnacle of desktop environment configurability. Hard-coding this new behaviour is the opposite of this. An alternative is to restore the ability to unassign the Space shortcut and rollback to the prior behaviour. Is there any documentation or any study to indicate why using a keyboard action (space) to offer buttons for mouse clicking (copy, cut, rename, trash) is preferred behaviour with respect to user experience? Thank you for considering this request. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 467028] After attempt of opening a file unknown by system via ```"Choose Application" I get glitches when scrolling in Dolphin.
https://bugs.kde.org/show_bug.cgi?id=467028 --- Comment #2 from mitlaw2...@gmail.com --- Behavior doesn't reproduce in X11, only Wayland. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 467250] New: Dolphin crash every time I eject a CD
https://bugs.kde.org/show_bug.cgi?id=467250 Bug ID: 467250 Summary: Dolphin crash every time I eject a CD Classification: Applications Product: dolphin Version: 19.12.3 Platform: Ubuntu OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: ko...@yahoo.com CC: kfm-de...@kde.org Target Milestone: --- Created attachment 157216 --> https://bugs.kde.org/attachment.cgi?id=157216=edit stack trace 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. insert CD rom, copy out data 2. right click on device and select eject 3. Crash! OBSERVED RESULT Crash! EXPECTED RESULT ejected CD. 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.
[plasmashell] [Bug 467249] New: Unwanted popup on login - wayland only
https://bugs.kde.org/show_bug.cgi?id=467249 Bug ID: 467249 Summary: Unwanted popup on login - wayland only Classification: Plasma Product: plasmashell Version: 5.27.2 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Startup process Assignee: plasma-b...@kde.org Reporter: rob.d...@telus.net CC: k...@davidedmundson.co.uk Target Milestone: 1.0 SUMMARY *** When logging in a Wayland session a popup appears. It captures the mouse cursor and any mouse movement creates a multitude of popups. STEPS TO REPRODUCE 1. Login to a Wayland session. 2. When the popup appears attempt to cancel it. 3. Restart because nothing useful can be done OBSERVED RESULT A new popup is created with any cursor movement. The popup has a "cancel" item but it cannot be accessed but any attempt creates a new popup. EXPECTED RESULT After login no popup shpuld appear. Get on with work. SOFTWARE/OS VERSIONS Linux/KDE Plasma Fedora 37 (available in About System) KDE Plasma Version: 5.27.2 KDE Frameworks Version: 5.103 Qt Version: 5.15.8 ADDITIONAL INFORMATION The problem is reproducable on Wayland. It does not occur on X11. Perhaps this a corruption rather than a bug. I can create a new user and login to a Wayland session and the problem does not occur. The popup consists of -- HTML Document Google Chrome Firefox Konqueror Falkon Kwrite Okular Calligra Words Kate Disable This Popup Cancel Is anyone willing to track this down? If not I can save any "keepers" then delete and recreate the user. -- You are receiving this mail because: You are watching all bug changes.
[kasts] [Bug 466493] crashes when given invalid url
https://bugs.kde.org/show_bug.cgi?id=466493 --- Comment #3 from aschonfor...@posteo.net --- (In reply to bart from comment #2) > I still can't reproduce this. Could you perhaps check if it's still > happening with the latest build for you? it isn't happening anymore with the newest build from the binary factory. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 467248] New: Allow previewing AppStream
https://bugs.kde.org/show_bug.cgi?id=467248 Bug ID: 467248 Summary: Allow previewing AppStream Classification: Applications Product: Discover Version: 5.27.2 Platform: Manjaro OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: discover Assignee: plasma-b...@kde.org Reporter: jakob...@gmx.de CC: aleix...@kde.org Target Milestone: --- Gnome Software has a nice Feature for Developers: If you run gnome-software --show-metainfo=/path/to/metainfo.xml, you can see how your AppStream Data looks in Gnome Software and if you got everything right before releasing. This is very useful to have, so I think it should be added to Discover as well. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kwallet] [Bug 458085] Wallet system takes about 1 minute to start
https://bugs.kde.org/show_bug.cgi?id=458085 --- Comment #59 from Thiago Macieira --- > @Thiago, the issue is bigger than just synchronous vs asynchronous. The > issue is that if you use a GPG wallet, with Secret Service provided by > KWallet, and while allowing pinentry to read the key passphrase from Secret > Service, what ends up happening is that KWallet asks for the key passphrase > from itself instead of the user. It's like trying to unlock a safe with the > key that's locked inside that same safe. Not going to work. Even if you > make this asynchronous, you'll just end up with an infinite recursion. I understand that we ended up with KWallet asking itself for the password. But the fact is that if the query was asynchronous, then pinentry would have got its answer instead of timing out, and then would have prompted the use for the password. Or maybe not, maybe KWallet is storing the cached answer in memory and would have provided it to pinentry. But do note I talked about KWallet ensuring it doesn't recurse infinitely, which is why we'd need to figure out if where this particular password could be saved if it is provided to KWallet; refusing to store it is a way to break the chain. I'm not saying it's easy to implement this. Your idea from comment 40 -- to tell gpg-agent that we want a password with no-external-cache -- is a solution too. Probably the Right Solution (with capital R and S). But not the way you described it. Modifying ~/.gnupg/gpg-agent.conf is not acceptable, because it's not atomic. Other passwords may be getting requested at the same time as KWallet is trying to open. In fact, if we are trying to open the wallet now because something wants a stored password, then it stands to reason another program could be trying to do the same. Moreover, because we're waiting for user interaction, the time during which the gpg-agent.conf file is modified is measured in human time. Therefore, this solution requires that we inform gpg-agent that we want a no-external-auth-cache answer for THIS query only and that it inform the pinentry tool that it shouldn't query the external auth cache. That requires those two tools to be updated and their updates deployed; plus probably libgpgme too. It's probably the right thing to do, so we should interact with upstream to get them to implement this. But if there is a KWallet-only solution, we should investigate it. -- You are receiving this mail because: You are watching all bug changes.
[Falkon] [Bug 415467] Can't circumvent Google's browser blocking with user agent manager
https://bugs.kde.org/show_bug.cgi?id=415467 --- Comment #8 from Kevin Kofler --- FYI, accounts.google.com now also uses the play.google.com domain for some reason, so you now have to set the same fake user agent also for play.google.com in addition to accounts.google.com. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 467116] digiKam crashed on exit. Even the appimage not only the deb version.
https://bugs.kde.org/show_bug.cgi?id=467116 --- Comment #9 from Maik Qualmann --- I'm sure Debian used a codebase before we fixed this issue. Can you reproduce the problem with the current AppImage? Download here: https://files.kde.org/digikam/ Maik -- You are receiving this mail because: You are watching all bug changes.
[ktimetracker] [Bug 452237] kTimeTracker crashes when Continue or Revert buttons are pressed
https://bugs.kde.org/show_bug.cgi?id=452237 Alexander Potashev changed: What|Removed |Added Status|CONFIRMED |RESOLVED Resolution|--- |WORKSFORME --- Comment #4 from Alexander Potashev --- Thanks for investigating! The bugfix commit https://invent.kde.org/frameworks/kidletime/-/commit/cd5040684723b87c7ba5b7cc1b1a63402902a641 was included in 5.93.0. Update KF5 minimum version to 5.93.0. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 467245] NetBSD compilation fix for Neptune
https://bugs.kde.org/show_bug.cgi?id=467245 Maik Qualmann changed: What|Removed |Added CC||metzping...@gmail.com --- Comment #2 from Maik Qualmann --- For the last digiKam version of 7.x.x. series (7.10.0) the patch is too late. The release date is today. The patch has been applied to the upcoming digiKam-8.0.0. Thanks for the patch. Maik -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 467245] NetBSD compilation fix for Neptune
https://bugs.kde.org/show_bug.cgi?id=467245 Maik Qualmann changed: What|Removed |Added Version Fixed In||8.0.0 Resolution|--- |FIXED Latest Commit||https://invent.kde.org/grap ||hics/digikam/commit/bc8fcfa ||83beef371afa7394e5945d7601b ||035e65 Status|REPORTED|RESOLVED --- Comment #1 from Maik Qualmann --- Git commit bc8fcfa83beef371afa7394e5945d7601b035e65 by Maik Qualmann. Committed on 12/03/2023 at 16:32. Pushed by mqualmann into branch 'master'. apply patch #157215 from Thomas Klausner to fix compile Neptune on NetBSD FIXED-IN: 8.0.0 M +1-1NEWS M +5-0 core/dplugins/generic/tools/mediaserver/upnpsdk/Neptune/Source/Core/NptConfig.h https://invent.kde.org/graphics/digikam/commit/bc8fcfa83beef371afa7394e5945d7601b035e65 -- You are receiving this mail because: You are watching all bug changes.
[amarok] [Bug 459933] ffmpeg-5 support
https://bugs.kde.org/show_bug.cgi?id=459933 Tuomas Nurmi changed: What|Removed |Added CC||tuo...@norsumanageri.org Resolution|--- |FIXED Status|REPORTED|RESOLVED --- Comment #2 from Tuomas Nurmi --- Fixed in git head today: https://invent.kde.org/multimedia/amarok/-/merge_requests/52 -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 459173] Cannot use USB smartcard to sign document
https://bugs.kde.org/show_bug.cgi?id=459173 Syiad changed: What|Removed |Added Version|22.04.3 |22.12.3 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kidletime] [Bug 451946] Calling KIdleTime::removeIdleTimeout() during KidleTime::timeoutReached() signal causes crash
https://bugs.kde.org/show_bug.cgi?id=451946 Alexander Potashev changed: What|Removed |Added Version Fixed In||5.93.0 CC||aspotas...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 467247] New: Random crash
https://bugs.kde.org/show_bug.cgi?id=467247 Bug ID: 467247 Summary: Random crash Classification: Plasma Product: plasmashell Version: 5.27.2 Platform: Compiled Sources OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: shadiness9...@proton.me CC: k...@davidedmundson.co.uk Target Milestone: 1.0 Application: plasmashell (5.27.2) (Compiled from sources) Qt Version: 5.15.8 Frameworks Version: 5.103.0 Operating System: Linux 6.2.2-gentoo-x86_64 x86_64 Windowing System: X11 Distribution: "Gentoo Linux" DrKonqi: 5.27.2 [KCrashBackend] -- Information about the crash: Just casually using KDE Plasma when suddenly the desktop crashes The reporter is unsure if this crash is reproducible. -- Backtrace: Application: Plasma (plasmashell), signal: Segmentation fault [KCrash Handler] #4 0x7f03a8121d30 in () #5 0x7f04641c1120 in QSGOpaqueTextureMaterialShader::updateState(QSGMaterialShader::RenderState const&, QSGMaterial*, QSGMaterial*) () at /usr/lib64/libQt5Quick.so.5 #6 0x7f04641a997d in QSGBatchRenderer::Renderer::renderMergedBatch(QSGBatchRenderer::Batch const*) () at /usr/lib64/libQt5Quick.so.5 #7 0x7f04641aebb5 in QSGBatchRenderer::Renderer::renderBatches() () at /usr/lib64/libQt5Quick.so.5 #8 0x7f04641af716 in QSGBatchRenderer::Renderer::render() () at /usr/lib64/libQt5Quick.so.5 #9 0x7f0464197020 in QSGRenderer::renderScene(QSGBindable const&) () at /usr/lib64/libQt5Quick.so.5 #10 0x7f04641974d3 in QSGRenderer::renderScene(unsigned int) () at /usr/lib64/libQt5Quick.so.5 #11 0x7f04641fa6e3 in QSGDefaultRenderContext::renderNextFrame(QSGRenderer*, unsigned int) () at /usr/lib64/libQt5Quick.so.5 #12 0x7f04642679e9 in QQuickWindowPrivate::renderSceneGraph(QSize const&, QSize const&) () at /usr/lib64/libQt5Quick.so.5 #13 0x7f04642085e7 in () at /usr/lib64/libQt5Quick.so.5 #14 0x7f04642094bf in () at /usr/lib64/libQt5Quick.so.5 #15 0x7f04626c65a3 in () at /usr/lib64/libQt5Core.so.5 #16 0x7f04620b1fb4 in () at /lib64/libc.so.6 #17 0x7f04621320fc in () at /lib64/libc.so.6 Thread 7 (Thread 0x7f03fd7fa6c0 (LWP ) "QSGRenderThread"): #1 0x7f04620b13d8 in pthread_cond_wait () at /lib64/libc.so.6 #2 0x7f04626cb7f4 in QWaitCondition::wait(QMutex*, QDeadlineTimer) () at /usr/lib64/libQt5Core.so.5 #3 0x7f04642070d5 in () at /usr/lib64/libQt5Quick.so.5 #4 0x7f0464209501 in () at /usr/lib64/libQt5Quick.so.5 #5 0x7f04626c65a3 in () at /usr/lib64/libQt5Core.so.5 #6 0x7f04620b1fb4 in () at /lib64/libc.so.6 #7 0x7f04621320fc in () at /lib64/libc.so.6 Thread 6 (Thread 0x7f040dffd6c0 (LWP 4183) "CPMMListener"): #1 0x7f04568d7584 in () at /usr/lib64/libnvidia-glcore.so.525.89.02 #2 0x7f04568dac8e in () at /usr/lib64/libnvidia-glcore.so.525.89.02 #3 0x7f0456872648 in () at /usr/lib64/libnvidia-glcore.so.525.89.02 #4 0x7f0456872a1a in () at /usr/lib64/libnvidia-glcore.so.525.89.02 #5 0x7f04568702fa in () at /usr/lib64/libnvidia-glcore.so.525.89.02 #6 0x7f04620b1fb4 in () at /lib64/libc.so.6 #7 0x7f04621320fc in () at /lib64/libc.so.6 Thread 5 (Thread 0x7f0436c0 (LWP 4008) "QSGRenderThread"): #1 0x7f04620b13d8 in pthread_cond_wait () at /lib64/libc.so.6 #2 0x7f04626cb7f4 in QWaitCondition::wait(QMutex*, QDeadlineTimer) () at /usr/lib64/libQt5Core.so.5 #3 0x7f04642070d5 in () at /usr/lib64/libQt5Quick.so.5 #4 0x7f0464209501 in () at /usr/lib64/libQt5Quick.so.5 #5 0x7f04626c65a3 in () at /usr/lib64/libQt5Core.so.5 #6 0x7f04620b1fb4 in () at /lib64/libc.so.6 #7 0x7f04621320fc in () at /lib64/libc.so.6 Thread 4 (Thread 0x7f044d38b6c0 (LWP 3939) "QQuickPixmapRea"): #1 0x7f0461f496fe in () at /usr/lib64/libglib-2.0.so.0 #2 0x7f0461f4981c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #3 0x7f04628ad43e in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #4 0x7f04628600eb in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #5 0x7f04626c5492 in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #6 0x7f0464155646 in () at /usr/lib64/libQt5Quick.so.5 #7 0x7f04626c65a3 in () at /usr/lib64/libQt5Core.so.5 #8 0x7f04620b1fb4 in () at /lib64/libc.so.6 #9 0x7f04621320fc in () at /lib64/libc.so.6 Thread 3 (Thread 0x7f0454bfe6c0 (LWP 3785) "QQmlThread"): #1 0x7f0461f496fe in () at /usr/lib64/libglib-2.0.so.0 #2 0x7f0461f4981c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #3 0x7f04628ad43e in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #4 0x7f04628600eb in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #5 0x7f04626c5492 in
[kalendar] [Bug 467246] New: Kalendar crash
https://bugs.kde.org/show_bug.cgi?id=467246 Bug ID: 467246 Summary: Kalendar crash Classification: Applications Product: kalendar Version: 22.12.3 Platform: Compiled Sources OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: claudio.cam...@kde.org Reporter: rahmadnur.kholifa...@gmail.com CC: c...@carlschwan.eu Target Milestone: --- Application: kalendar (22.12.3) (Compiled from sources) Qt Version: 5.15.8 Frameworks Version: 5.103.0 Operating System: Linux 5.19.0-35-generic x86_64 Windowing System: X11 Distribution: KDE neon 5.27 DrKonqi: 5.27.2 [KCrashBackend] -- Information about the crash: kalendar force close when i'm open kalendar OS KDE Neon The reporter is unsure if this crash is reproducible. -- Backtrace: Application: Kalendar (kalendar), signal: Segmentation fault [KCrash Handler] #4 0x7f74afa58ed4 in KCalendarCore::Calendar::isLoading() const () from /lib/x86_64-linux-gnu/libKF5CalendarCore.so.5 #5 0x5648b31fa766 in ?? () #6 0x7f74ad6f40d4 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7f74ad6f815e in QTimer::timeout(QTimer::QPrivateSignal) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7f74ad6e99ff in QObject::event(QEvent*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #9 0x7f74ae36c793 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #10 0x7f74ad6bc07a in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #11 0x7f74ad714e0b in QTimerInfoList::activateTimers() () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #12 0x7f74ad715754 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #13 0x7f74ab520d3b in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #14 0x7f74ab5756c8 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #15 0x7f74ab51e3e3 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #16 0x7f74ad715ad8 in QEventDispatcherGlib::processEvents(QFlags) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #17 0x7f74ad6ba99b in QEventLoop::exec(QFlags) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #18 0x7f74ad6c2f34 in QCoreApplication::exec() () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #19 0x5648b31b685c in ?? () #20 0x7f74acc29d90 in __libc_start_call_main (main=main@entry=0x5648b31b4860, argc=argc@entry=1, argv=argv@entry=0x7ffc2bbffbd8) at ../sysdeps/nptl/libc_start_call_main.h:58 #21 0x7f74acc29e40 in __libc_start_main_impl (main=0x5648b31b4860, argc=1, argv=0x7ffc2bbffbd8, init=, fini=, rtld_fini=, stack_end=0x7ffc2bbffbc8) at ../csu/libc-start.c:392 #22 0x5648b31b7805 in ?? () [Inferior 1 (process 5515) detached] Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 467244] The same issue and suffering with the plasma-Discover UNABLE TO LOAD
https://bugs.kde.org/show_bug.cgi?id=467244 Nicolas Fella changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |NOT A BUG CC||nicolas.fe...@gmx.de --- Comment #1 from Nicolas Fella --- This is not a bug in Discover. The problem is that your distribution does not appear to have Konqueror available in its repositories. You'll need to talk to them and ask them to add it. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 462854] [Android] Unable to drag-and-drop actions in the Configure Toolbar dialogue
https://bugs.kde.org/show_bug.cgi?id=462854 --- Comment #2 from Tyson Tan --- Hi Sharaf. I've tested the APK. The issue has been fixed, and I didn't encounter any new bugs in my usual workflow. Thanks! -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 467245] New: NetBSD compilation fix for Neptune
https://bugs.kde.org/show_bug.cgi?id=467245 Bug ID: 467245 Summary: NetBSD compilation fix for Neptune Classification: Applications Product: digikam Version: 7.9.0 Platform: NetBSD pkgsrc OS: NetBSD Status: REPORTED Severity: major Priority: NOR Component: Plugin-Generic-MediaServer Assignee: digikam-bugs-n...@kde.org Reporter: t...@giga.or.at Target Milestone: --- Created attachment 157215 --> https://bugs.kde.org/attachment.cgi?id=157215=edit Patch fixing the problem. On NetBSD, linking fails due to a missing Resolve() function because NPT_CONFIG_HAVE_GETADDRINFO is not defined and the function is not compiled. The attached patch fixes the problem. -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 467065] Many apps don't respect font size settings on Wayland, displaying text much smaller than the set size
https://bugs.kde.org/show_bug.cgi?id=467065 --- Comment #1 from edrics --- Solved – the issue depended on different scaling setting in the xX11 and Wayland session -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 467065] Many apps don't respect font size settings on Wayland, displaying text much smaller than the set size
https://bugs.kde.org/show_bug.cgi?id=467065 edrics changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 467244] New: The same issue and suffering with the plasma-Discover UNABLE TO LOAD
https://bugs.kde.org/show_bug.cgi?id=467244 Bug ID: 467244 Summary: The same issue and suffering with the plasma-Discover UNABLE TO LOAD Classification: Applications Product: Discover Version: 5.27.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: discover Assignee: plasma-b...@kde.org Reporter: mestermeed...@gmail.com CC: aleix...@kde.org Target Milestone: --- Created attachment 157214 --> https://bugs.kde.org/attachment.cgi?id=157214=edit its a screenshot for the issue I'm very upset with the Discover app doesn't work at all it's useless please fix that issue most people have the same issue with the Discover doesn't load apps and keep saying unable to load verify connection and the connection is totally fine, so please take action or change the Discover app to something that works and thank you. -- You are receiving this mail because: You are watching all bug changes.
[xdg-desktop-portal-kde] [Bug 467241] Crash when closing screen share dialog
https://bugs.kde.org/show_bug.cgi?id=467241 Bug Janitor Service changed: What|Removed |Added Keywords||qt6 -- You are receiving this mail because: You are watching all bug changes.
[Tokodon] [Bug 467243] New: Certain ui elements prevent touch scrolling
https://bugs.kde.org/show_bug.cgi?id=467243 Bug ID: 467243 Summary: Certain ui elements prevent touch scrolling Classification: Applications Product: Tokodon Version: 23.02.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: r...@krx.sh CC: c...@carlschwan.eu, j...@redstrate.com Target Milestone: --- SUMMARY When using a touchscreen, swiping vertically does not always scroll the view. Instead some other action is sometimes taken, or nothing happens at all. Affected elements include: - profile bios (where the bio text gets selected) - the text content of a post (where nothing happens), but only in Thread view and not in e.g. Home or Local - the gap between the user info and the text content, or between the text content and the media in a post (where nothing happens) - profile links (where link text gets selected), but not their labels STEPS TO REPRODUCE 1. navigate to a scrollable view where any of those elements is visible 2. put your finger on one of the elements 3. move your finger up or down the screen OBSERVED RESULT see above EXPECTED RESULT the view scrolls SOFTWARE/OS VERSIONS postmarketOS edge Plasma Mobile 5.27.2 KDE Frameworks Version: 5.103.0 Qt Version: 5.15.8 -- You are receiving this mail because: You are watching all bug changes.
[NeoChat] [Bug 467242] New: Search "toolbar" has the wrong size and "overlaps" onto the rooms area
https://bugs.kde.org/show_bug.cgi?id=467242 Bug ID: 467242 Summary: Search "toolbar" has the wrong size and "overlaps" onto the rooms area Classification: Applications Product: NeoChat Version: unspecified Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: General Assignee: fe...@posteo.de Reporter: k...@marcdeop.com CC: c...@carlschwan.eu Target Milestone: --- Created attachment 157213 --> https://bugs.kde.org/attachment.cgi?id=157213=edit overlap_onto_rooms_section The search toolbar is a bit to big and overlaps onto the rooms area. See the screenshot Linux/KDE Plasma: KDE Plasma Version: 5.27.2 KDE Frameworks Version: 5.104.0 Qt Version: 5.15.8 ADDITIONAL INFORMATION I build neochat myself and make it available on my copr: https://copr.fedorainfracloud.org/coprs/marcdeop/neochat-git/ -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 467192] Folders are opened in new tab but should open in new window
https://bugs.kde.org/show_bug.cgi?id=467192 Felix Ernst changed: What|Removed |Added Resolution|--- |FIXED Status|REOPENED|RESOLVED --- Comment #3 from Felix Ernst --- Dolphin version 21.12.3 stands for the version that was released in the year 2021, month 12 (December), third bugfix release. Kubuntu 22.04 is the Kubuntu version that was released in the year 2022, month 4 (April). The Kubuntu 22.04 version won't receive any new Dolphin versions that were released later than April 2022. This is out of KDE's control. >From my testing, the bug that you are reporting has been fixed and released since then. Unless you upgrade your Kubuntu installation to newer versions e.g. Kubuntu 22.10 or the soon-to-be-released Kubuntu 23.04, you won't be able to upgrade to a Dolphin version that has the fix. Please only re-open if you have confirmed that this bug exists on those later versions. I literally can't do anything else because from my testing, the bug has already been fixed. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 467221] Folder color switcher function
https://bugs.kde.org/show_bug.cgi?id=467221 Felix Ernst changed: What|Removed |Added Ever confirmed|0 |1 Status|REPORTED|CONFIRMED --- Comment #3 from Felix Ernst --- You are probably talking about this "Color Folder" Dolphin service menu: https://store.kde.org/p/998450 >Tags are fine but they aren't even close to just right click and change it to >"blue", >get the "blue" folders and them put them in the right place (that's my >workflow with this). That might be the ideal workflow though if this was to be implemented. The "Create New Tag" dialog could have colour tags as one way to create a new tag. Folders who get this tag could be switched to the fitting coloured folder icon. Might be really neat! Another way would be to have this as a standalone "official" service menu entry that could be dis/enabled in Dolphin's settings, but then we wouldn't get the advantage of tags, which is being usable from other applications. -- You are receiving this mail because: You are watching all bug changes.
[xdg-desktop-portal-kde] [Bug 467241] New: Crash when closing screen share dialog
https://bugs.kde.org/show_bug.cgi?id=467241
Bug ID: 467241
Summary: Crash when closing screen share dialog
Classification: Plasma
Product: xdg-desktop-portal-kde
Version: unspecified
Platform: Compiled Sources
OS: Linux
Status: REPORTED
Keywords: drkonqi
Severity: crash
Priority: NOR
Component: general
Assignee: plasma-b...@kde.org
Reporter: nicolas.fe...@gmx.de
CC: aleix...@kde.org, jgrul...@redhat.com, n...@kde.org
Target Milestone: ---
Application: xdg-desktop-portal-kde (5.27.80)
(Compiled from sources)
Qt Version: 6.4.2
Frameworks Version: 5.240.0
Operating System: Linux 6.1.15-200.fc37.x86_64 x86_64
Windowing System: Wayland
Distribution: Fedora Linux 37 (KDE Plasma)
DrKonqi: 5.27.80 [KCrashBackend]
-- Information about the crash:
When starting OBS studio it triggered the screen share dialog. I dismissed it
by pressing Esc, then the portal crashed
The crash can be reproduced every time.
-- Backtrace:
Application: xdg-desktop-portal-kde (xdg-desktop-portal-kde), signal:
Segmentation fault
Content of s_kcrashErrorMessage: std::unique_ptr = {get() = 0x0}
[KCrash Handler]
#5 0x7effc6f5c22a in wl_map_insert_at (map=, flags=1, i=33,
data=) at ../src/wayland-util.c:276
#6 0x7effc6f57bc4 in proxy_destroy (proxy=0x1a529a0) at
../src/wayland-client.c:510
#7 0x7effc6f58022 in wl_proxy_destroy_caller_locks (proxy=0x1a529a0) at
../src/wayland-client.c:530
#8 wl_proxy_marshal_array_flags (proxy=proxy@entry=0x1a529a0,
opcode=opcode@entry=0, interface=interface@entry=0x0, version=version@entry=4,
flags=flags@entry=1, args=args@entry=0x7ffe220eefe0) at
../src/wayland-client.c:868
#9 0x7effc6f5821a in wl_proxy_marshal_flags (proxy=0x1a529a0, opcode=0,
interface=0x0, version=4, flags=1) at ../src/wayland-client.c:791
#10 0x7effc7025476 in wl_output_release (wl_output=0x1a529a0) at
/usr/include/wayland-client-protocol.h:5738
#11 KWayland::Client::WaylandPointer::release
(this=0x199b3f0) at
/home/nico/kde6/src/kwayland/src/client/wayland_pointer_p.h:44
#12 KWayland::Client::Output::~Output (this=0x19c0d60, __in_chrg=) at /home/nico/kde6/src/kwayland/src/client/output.cpp:124
#13 0x7effc7025499 in KWayland::Client::Output::~Output (this=0x19c0d60,
__in_chrg=) at
/home/nico/kde6/src/kwayland/src/client/output.cpp:125
#14 0x004b796b in QtSharedPointer::ExternalRefCountData::destroy
(this=0x19a2990) at /usr/include/qt6/QtCore/qsharedpointer_impl.h:114
#15 QSharedPointer::deref (dd=0x19a2990) at
/usr/include/qt6/QtCore/qsharedpointer_impl.h:445
#16 QSharedPointer::deref (dd=0x19a2990) at
/usr/include/qt6/QtCore/qsharedpointer_impl.h:441
#17 QSharedPointer::deref (this=0x1a47530) at
/usr/include/qt6/QtCore/qsharedpointer_impl.h:440
#18 QSharedPointer::~QSharedPointer (this=0x1a47530,
__in_chrg=) at /usr/include/qt6/QtCore/qsharedpointer_impl.h:280
#19 ~ (this=0x1a47520, __in_chrg=) at
/home/nico/kde6/src/xdg-desktop-portal-kde/src/waylandintegration.cpp:660
#20
QtPrivate::QFunctorSlotObject, 0, QtPrivate::List<>, void>::~QFunctorSlotObject
(this=0x1a47510, __in_chrg=) at
/usr/include/qt6/QtCore/qobjectdefs_impl.h:397
#21
QtPrivate::QFunctorSlotObject, 0, QtPrivate::List<>, void>::impl (which=0, r=, a=, ret=, this_=0x1a47510) at
/usr/include/qt6/QtCore/qobjectdefs_impl.h:405
#22
QtPrivate::QFunctorSlotObject, 0, QtPrivate::List<>, void>::impl(int,
QtPrivate::QSlotObjectBase *, QObject *, void **, bool *) (which=, this_=0x1a47510, r=, a=, ret=) at /usr/include/qt6/QtCore/qobjectdefs_impl.h:401
#23 0x7effc37c5eec in QObject::~QObject() () from /lib64/libQt6Core.so.6
#24 0x004b3e3a in QtGlobalStatic::Holder<(anonymous
namespace)::Q_QGS_globalWaylandIntegration>::~Holder (this=,
__in_chrg=) at /usr/include/qt6/QtCore/qglobalstatic.h:43
#25 0x7effc30620b5 in __run_exit_handlers () from /lib64/libc.so.6
#26 0x7effc3062230 in exit () from /lib64/libc.so.6
#27 0x7effc304a517 in __libc_start_call_main () from /lib64/libc.so.6
#28 0x7effc304a5c9 in __libc_start_main_impl () from /lib64/libc.so.6
#29 0x00425195 in _start ()
[Inferior 1 (process 392797) detached]
Reported using DrKonqi
--
You are receiving this mail because:
You are watching all bug changes.
[xdg-desktop-portal-kde] [Bug 466056] " - Portal" shown in titlebar.
https://bugs.kde.org/show_bug.cgi?id=466056 Bug Janitor Service changed: What|Removed |Added Status|CONFIRMED |ASSIGNED --- Comment #4 from Bug Janitor Service --- A possibly relevant merge request was started @ https://invent.kde.org/plasma/xdg-desktop-portal-kde/-/merge_requests/180 -- You are receiving this mail because: You are watching all bug changes.
[policykit-kde-agent-1] [Bug 466059] Confusing information shown in titlebar
https://bugs.kde.org/show_bug.cgi?id=466059 Bug Janitor Service changed: What|Removed |Added Status|CONFIRMED |ASSIGNED --- Comment #3 from Bug Janitor Service --- A possibly relevant merge request was started @ https://invent.kde.org/plasma/polkit-kde-agent-1/-/merge_requests/20 -- You are receiving this mail because: You are watching all bug changes.
