[Discover] [Bug 485463] discover 6.0.4 fails to launch on Neon Testing
https://bugs.kde.org/show_bug.cgi?id=485463
vatbier changed:
What|Removed |Added
Status|NEEDSINFO |REPORTED
Resolution|WAITINGFORINFO |---
--- Comment #7 from vatbier ---
Today a little bit of improvement after getting the latest updates:
in konsole:
$ plasma-discover
libs QList("/usr/lib/x86_64-linux-gnu/qt6/plugins", "/usr/bin")
org.kde.plasma.libdiscover: OdrsReviewsBackend: Fetch ratings: true
adding empty sources model QStandardItemModel(0x5ff64a0d10a0)
qrc:/qt/qml/org/kde/discover/qml/DiscoverWindow.qml:330:5: QML OverlaySheet:
Binding loop detected for property "implicitHeight"
qrc:/qt/qml/org/kde/discover/qml/BrowsingPage.qml:17:1: QML BrowsingPage:
Created graphical object was not placed in the graphics scene.
PackageKitBackend: No distro component found for "org.kde.neon.neon"
(process:4763): GLib-GObject-WARNING **: 07:24:43.480: cannot register existing
type 'SoupMessage'
(process:4763): GLib-GObject-WARNING **: 07:24:43.480: cannot add private field
to invalid (non-instantiatable) type ''
(process:4763): GLib-CRITICAL **: 07:24:43.480: g_once_init_leave: assertion
'result != 0' failed
(process:4763): GLib-GObject-WARNING **: 07:24:43.480:
../../../gobject/gsignal.c:1760: parameter 1 of type '' for signal
"SoupSession::request-queued" is not a value type
Now Discover window appears but when I try to click on About or Settings it
hangs
and the window title bar shows "Home -- Discover (Not Responding)"
info
Operating System: KDE neon Testing Edition
KDE Plasma Version: 6.0.4
KDE Frameworks Version: 6.3.0
Qt Version: 6.7.0
Kernel Version: 6.5.0-35-generic (64-bit)
Graphics Platform: Wayland
Processors: 4 × Intel® Core™ i3-2120 CPU @ 3.30GHz
Memory: 3.8 GiB of RAM
Graphics Processor: NV108
--
You are receiving this mail because:
You are watching all bug changes.
[kwin] [Bug 487217] Nested kwin_wayland crashed in KWin::EglSwapchainSlot::buffer in VMs using the llvmpipe driver
https://bugs.kde.org/show_bug.cgi?id=487217 Bug Janitor Service changed: What|Removed |Added Severity|normal |crash -- You are receiving this mail because: You are watching all bug changes.
[minuet] [Bug 487169] Available answer buttons do not register the answer.
https://bugs.kde.org/show_bug.cgi?id=487169 --- Comment #1 from Ryan --- Correction: The current video driver is nvidia. > prime-select get-current Driver configured: nvidia NVIDIA modules are loaded -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 447989] Support Armv8.2 SHA-512 instructions
https://bugs.kde.org/show_bug.cgi?id=447989 --- Comment #13 from Paul Floyd --- Thanks for the patches. I've applied, tested and pushed the first one. The second patch looks OK so far but I'd like to check it on FreeBSD before pushing the change. It might take me a little while to see if I can get my hands on a suitable machine. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 487218] New: Plasma Wayland crashed
https://bugs.kde.org/show_bug.cgi?id=487218 Bug ID: 487218 Summary: Plasma Wayland crashed Classification: Plasma Product: kwin Version: unspecified Platform: Arch Linux OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kwin-bugs-n...@kde.org Reporter: jaxad0...@gmail.com Target Milestone: --- Application: kwin_wayland () Qt Version: 6.7.0 Frameworks Version: 6.2.0 Operating System: Linux 6.8.9-arch1-2 x86_64 Windowing System: Wayland Distribution: "Arch Linux" DrKonqi: 6.0.4 [CoredumpBackend] -- Information about the crash: Plasma wayland crashed. Firefox 126 has been crashy too. Recently upgraded. The crash can be reproduced sometimes. -- Backtrace (Reduced): #2 __memcpy_avx_unaligned_erms () at ../sysdeps/x86_64/multiarch/memmove-vec-unaligned-erms.S:488 #3 0x7a0d1a4217cc in memcpy () at /usr/include/bits/string_fortified.h:29 #4 tc_buffer_subdata () at ../mesa-24.0.7/src/gallium/auxiliary/util/u_threaded_context.c:3156 #5 0x7a0d274b5a70 in QOpenGLFunctions::glBufferSubData (data=, size=, offset=, target=, this=) at /usr/src/debug/qt6-base/qtbase/src/gui/opengl/qopenglfunctions.h:1189 #6 QRhiGles2::executeCommandBuffer (this=0x6032339694c0, cb=0x603233572658) at /usr/src/debug/qt6-base/qtbase/src/gui/rhi/qrhigles2.cpp:3261 Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 487218] Plasma Wayland crashed
https://bugs.kde.org/show_bug.cgi?id=487218 --- Comment #1 from jaxad0...@gmail.com --- Created attachment 169606 --> https://bugs.kde.org/attachment.cgi?id=169606=edit New crash information added by DrKonqi DrKonqi auto-attaching complete backtrace. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 480459] Konsole doesn't remember its maximized state
https://bugs.kde.org/show_bug.cgi?id=480459 BryanLiang changed: What|Removed |Added CC||liangrui...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 487217] New: Nested kwin_wayland crashed in KWin::EglSwapchainSlot::buffer in VMs using the llvmpipe driver
https://bugs.kde.org/show_bug.cgi?id=487217
Bug ID: 487217
Summary: Nested kwin_wayland crashed in
KWin::EglSwapchainSlot::buffer in VMs using the
llvmpipe driver
Classification: Plasma
Product: kwin
Version: 6.0.4
Platform: Other
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: wayland-generic
Assignee: kwin-bugs-n...@kde.org
Reporter: matt.fagn...@bell.net
Target Milestone: ---
Created attachment 169605
--> https://bugs.kde.org/attachment.cgi?id=169605=edit
kwin_wayland crash trace output from drkonqi
SUMMARY
I booted the Fedora Rawhide/41 KDE Plasma live image
Fedora-KDE-Live-x86_64-Rawhide-20240518.n.0.iso in a QEMU/KVM VM using GNOME
Boxes with 3D acceleration disabled using the llvmpipe driver from mesa
24.1.0-rc4. Plasma 6.0.4 on Wayland started. I started Konsole. I tried to run
a nested kwin_wayland session using the instructions at
https://community.kde.org/KWin/Wayland
export $(dbus-launch)
kwin_wayland --xwayland
The nested kwin_wayland window didn't appear. A Wayland icon appeared in the
task manager briefly then disappeared. The following output was in Konsole
which showed a Permission denied error and a segmentation fault of
kwin_wayland.
export $(dbus-launch)
kwin_wayland --xwayland
No backend specified, automatically choosing Wayland because WAYLAND_DISPLAY is
set
unable to lock lockfile /run/user/1000/wayland-0.lock, maybe another compositor
is running
Accepting client connections on sockets: QList("wayland-1")
OpenGL vendor string: Mesa
OpenGL renderer string: llvmpipe (LLVM 18.1.4, 256 bits)
OpenGL version string: 4.5 (Core Profile) Mesa 24.1.0-rc4
OpenGL shading language version string: 4.50
Driver: LLVMpipe
GPU class: Unknown
OpenGL version: 4.5
GLSL version: 4.50
Mesa version: 24.1
Requires strict binding:no
Virtual Machine:no
Timer query support:yes
KMS: DRM_IOCTL_MODE_CREATE_DUMB failed: Permission denied
KMS: DRM_IOCTL_MODE_CREATE_DUMB failed: Permission denied
KMS: DRM_IOCTL_MODE_CREATE_DUMB failed: Permission denied
KMS: DRM_IOCTL_MODE_CREATE_DUMB failed: Permission denied
qt.qpa.wayland: Creating a fake screen in order for Qt not to crash
Segmentation fault (core dumped)
liveuser@localhost-live:~$ The Wayland connection broke. Did the Wayland
compositor die?
The nested kwin_wayland crashed in KWin::EglSwapchainSlot::buffer. The crash
might've been due to a null pointer dereference since this=0x0 in
KWin::EglSwapchainSlot::buffer.
Core was generated by `kwin_wayland --xwayland'.
Program terminated with signal SIGSEGV, Segmentation fault.
#0 KWin::EglSwapchainSlot::buffer (this=0x0) at
/usr/src/debug/kwin-6.0.4.1-3.fc41.x86_64/src/opengl/eglswapchain.cpp:39
39 return m_buffer;
[Current thread is 1 (Thread 0x7f1ca443ab00 (LWP 2894))]
Thread 1 (Thread 0x7f1ca443ab00 (LWP 2894)):
#0 KWin::EglSwapchainSlot::buffer (this=0x0) at
/usr/src/debug/kwin-6.0.4.1-3.fc41.x86_64/src/opengl/eglswapchain.cpp:39
#1 0x7f1ca526dd18 in KWin::Wayland::WaylandEglPrimaryLayer::present
(this=0x556c1bcd3a50) at /usr/include/c++/14/bits/shared_ptr_base.h:1666
#2 KWin::Wayland::WaylandEglBackend::present (this=,
output=, frame=std::shared_ptr (use count 1,
weak count 0) = {...}) at
/usr/src/debug/kwin-6.0.4.1-3.fc41.x86_64/src/backends/wayland/wayland_egl_backend.cpp:330
#3 0x7f1ca4fa8496 in KWin::Compositor::composite (this=0x556c18467990,
renderLoop=) at
/usr/src/debug/kwin-6.0.4.1-3.fc41.x86_64/src/compositor.cpp:201
#4 0x7f1ca23fa3c4 in QtPrivate::QSlotObjectBase::call
(this=0x556c1bd50870, r=, a=0x7ffcfc84dbf0) at
/usr/src/debug/qt6-qtbase-6.7.0-5.fc41.x86_64/src/corelib/kernel/qobjectdefs_impl.h:469
#5 doActivate (sender=0x556c183c01f0, signal_index=5,
argv=0x7ffcfc84dbf0) at
/usr/src/debug/qt6-qtbase-6.7.0-5.fc41.x86_64/src/corelib/kernel/qobject.cpp:4078
#6 0x7f1ca23f0977 in QMetaObject::activate (sender=,
m=, local_signal_index=local_signal_index@entry=2,
argv=argv@entry=0x7ffcfc84dbf0) at
/usr/src/debug/qt6-qtbase-6.7.0-5.fc41.x86_64/src/corelib/kernel/qobject.cpp:4138
#7 0x7f1ca4fc1c34 in KWin::RenderLoop::frameRequested (this=, _t1=) at
/usr/src/debug/kwin-6.0.4.1-3.fc41.x86_64/redhat-linux-build/src/kwin_autogen/include/moc_renderloop.cpp:208
#8 0x7f1ca4fc83ef in KWin::RenderLoopPrivate::dispatch
(this=0x556c183d37a0) at
/usr/src/debug/kwin-6.0.4.1-3.fc41.x86_64/src/core/renderloop.cpp:128
#9 0x7f1ca23fa3c4 in QtPrivate::QSlotObjectBase::call
(this=0x556c183bdc50, r=, a=0x7ffcfc84dd30) at
/usr/src/debug/qt6-qtbase-6.7.0-5.fc41.x86_64/src/corelib/kernel/qobjectdefs_impl.h:469
#
[Discover] [Bug 485007] Discover random crash
https://bugs.kde.org/show_bug.cgi?id=485007 Derek Enz changed: What|Removed |Added Status|NEEDSINFO |REPORTED Resolution|WAITINGFORINFO |--- --- Comment #5 from Derek Enz --- This bug is no longer reproducible. Discover seems stable. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-ktexteditor] [Bug 445598] Dynamic word wrapping in Kile stopped working in Ubuntu 21.10
https://bugs.kde.org/show_bug.cgi?id=445598 Zu Zuang changed: What|Removed |Added CC||nicolas.fe...@gmx.de -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 486991] Dynamic word wrap not kept from a session to other
https://bugs.kde.org/show_bug.cgi?id=486991 Zu Zuang changed: What|Removed |Added CC||nicolas.fe...@gmx.de -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 486991] Dynamic word wrap not kept from a session to other
https://bugs.kde.org/show_bug.cgi?id=486991 Zu Zuang changed: What|Removed |Added CC||cullm...@kde.org, ||xoyowax...@mcatag.com -- You are receiving this mail because: You are watching all bug changes.
[frameworks-ktexteditor] [Bug 445598] Dynamic word wrapping in Kile stopped working in Ubuntu 21.10
https://bugs.kde.org/show_bug.cgi?id=445598 Zu Zuang changed: What|Removed |Added CC||cullm...@kde.org, ||xoyowax...@mcatag.com -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 487216] Dynamic word wrap doesn't stay active
https://bugs.kde.org/show_bug.cgi?id=487216 Zu Zuang changed: What|Removed |Added CC||cullm...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 486168] Kmymoney Reports no longer available after upgrade to Fedora 40 KDE Spin
https://bugs.kde.org/show_bug.cgi?id=486168 --- Comment #6 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.
[Discover] [Bug 485463] discover 6.0.4 fails to launch on Neon Testing
https://bugs.kde.org/show_bug.cgi?id=485463 --- Comment #6 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.
[Discover] [Bug 486425] 'More Information' page in Discover update page closing due to bug
https://bugs.kde.org/show_bug.cgi?id=486425 --- Comment #8 from Bug Janitor Service --- Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 486988] Missing buttons
https://bugs.kde.org/show_bug.cgi?id=486988 Bug Janitor Service changed: What|Removed |Added Status|NEEDSINFO |REPORTED Resolution|WAITINGFORINFO |--- --- Comment #3 from Bug Janitor Service --- Thanks for your comment! Automatically switching the status of this bug to REPORTED so that the KDE team knows that the bug is ready to get confirmed. In the future you may also do this yourself when providing needed information. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 466744] wayland: 2 monitor setup with 175% scaling on one screen and 100% on the other causes various problems
https://bugs.kde.org/show_bug.cgi?id=466744 --- Comment #4 from Bug Janitor Service --- Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 394033] Disabling Screen Energy Saving disables suspending
https://bugs.kde.org/show_bug.cgi?id=394033 --- Comment #4 from Bug Janitor Service --- Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 485007] Discover random crash
https://bugs.kde.org/show_bug.cgi?id=485007 --- Comment #4 from Bug Janitor Service --- Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[kdelibs] [Bug 319919] Fails to request password, because X-KDE-SubstituteUID is KDE-specific
https://bugs.kde.org/show_bug.cgi?id=319919 --- Comment #14 from Bug Janitor Service --- Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[kdelibs] [Bug 302966] global iconLoader not updated on change of main component
https://bugs.kde.org/show_bug.cgi?id=302966 --- 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.
[kate] [Bug 487216] Dynamic word wrap doesn't stay active
https://bugs.kde.org/show_bug.cgi?id=487216 Zu Zuang changed: What|Removed |Added Keywords||accessibility, bounty, ||efficiency, regression, ||usability -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 487216] New: Dynamic word wrap doesn't stay active
https://bugs.kde.org/show_bug.cgi?id=487216 Bug ID: 487216 Summary: Dynamic word wrap doesn't stay active Classification: Applications Product: kate Version: unspecified Platform: Arch Linux OS: Linux Status: REPORTED Severity: critical Priority: NOR Component: application Assignee: kwrite-bugs-n...@kde.org Reporter: xoyowax...@mcatag.com Target Milestone: --- SUMMARY Hello. The problem is stated: Dynamic word wrap does not stay active. STEPS TO REPRODUCE 1. Open the kate 2. Activate dynamic word wrap 3. Close the kate 4. Open the kate 5. Word wrap not active It do not happen all the time. Often, it do. OBSERVED RESULT No word wrap EXPECTED RESULT Yes word wrap SOFTWARE/OS VERSIONS Linux/KDE Plasma: Arch Linux (available in About System) KDE Plasma Version: The latest KDE Frameworks Version: The latest Qt Version: The latest ADDITIONAL INFORMATION Hope it work soon. -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 366392] Brightness reset from lowest level after system restart
https://bugs.kde.org/show_bug.cgi?id=366392 --- Comment #3 from KDE Neon user --- @postix In your version of Bugzilla, it isn't clear whether the needsinfo request is directed to me. I'm not currently using KDE Plasma. If you've tagged me, please change it to Alexander's email. -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 430047] Feature request: Budgeting based on cash flow
https://bugs.kde.org/show_bug.cgi?id=430047 --- Comment #6 from jesse --- I can't wait to test this! Thank you so much! -- You are receiving this mail because: You are watching all bug changes.
[k3b] [Bug 487215] Crashes when ejecting a disc with read errors
https://bugs.kde.org/show_bug.cgi?id=487215 Bug Janitor Service changed: What|Removed |Added Severity|normal |crash -- You are receiving this mail because: You are watching all bug changes.
[k3b] [Bug 487215] New: Crashes when ejecting a disc with read errors
https://bugs.kde.org/show_bug.cgi?id=487215 Bug ID: 487215 Summary: Crashes when ejecting a disc with read errors Classification: Applications Product: k3b Version: 24.04.90 Platform: Slackware OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Data Project Assignee: k...@kde.org Reporter: hpf...@psnarf.org CC: mich...@jabster.pl, tr...@kde.org Target Milestone: --- *** If you're not sure this is actually a bug, instead post about it at https://discuss.kde.org If you're reporting a crash, attach a backtrace with debug symbols; see https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** SUMMARY I'm digitizing all of my CDs/DVDs because bit rot has damaged a dozen or so discs so far. STEPS TO REPRODUCE 1. Copy medium. Only create image. Begin copying the disc to iso. 2. Things proceed as advertised until k3b starts throwing read errors. 3. Eject the bad disc, either from the menu, or press the eject button. OBSERVED RESULT K3b crashes, a bug report pops up EXPECTED RESULT Produce an iso image like the hundreds of correct discs already digitized. SOFTWARE/OS VERSIONS Linux/KDE Plasma: KDE Plasma Version: 5.27.11 KDE Frameworks Version: 5.115.0 Qt Version: 5.15.13 ADDITIONAL INFORMATION I tried submitting a bug report, but they always hang trying to log in. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 487072] Windows open with very narrow size at right screen edge
https://bugs.kde.org/show_bug.cgi?id=487072 b...@supafriends.club changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |NOT A BUG --- Comment #1 from b...@supafriends.club --- Closing this report because I was able to determine that the issue was related to an update of conky which occurred at the same time the KDE Frameworks 6.2.0 updates were installed. My apologies. -- You are receiving this mail because: You are watching all bug changes.
[extra-cmake-modules] [Bug 487214] Qt6 "kcoreaddons_add_plugin" attempts to link plugin in /INSTALL_NAMESPACE
https://bugs.kde.org/show_bug.cgi?id=487214 grmpf changed: What|Removed |Added Summary|"kcoreaddons_add_plugin"|Qt6 |attempts to link plugin in |"kcoreaddons_add_plugin" |/INSTALL_NAMESPACE |attempts to link plugin in ||/INSTALL_NAMESPACE -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 486943] "kal16" shows as the only available TTS voice
https://bugs.kde.org/show_bug.cgi?id=486943 AR changed: What|Removed |Added CC||ra5...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 486988] Missing buttons
https://bugs.kde.org/show_bug.cgi?id=486988 --- Comment #2 from surrealho...@gmail.com --- There was redo and undo bottons in previous version, that would be easily accessed in this screenshot. They are no longer there. On Tue, May 14, 2024, 1:06 AM Halla Rempt wrote: > https://bugs.kde.org/show_bug.cgi?id=486988 > > Halla Rempt changed: > >What|Removed |Added > > > CC||ha...@valdyas.org > Resolution|--- |WAITINGFORINFO > Status|REPORTED|NEEDSINFO > > --- Comment #1 from Halla Rempt --- > I'm sorry, but please attach a screenshot that shows the problem, because > the > description is not clear enough. > > -- > You are receiving this mail because: > You reported the bug. -- You are receiving this mail because: You are watching all bug changes.
[extra-cmake-modules] [Bug 487214] New: "kcoreaddons_add_plugin" attempts to link plugin in /INSTALL_NAMESPACE
https://bugs.kde.org/show_bug.cgi?id=487214 Bug ID: 487214 Summary: "kcoreaddons_add_plugin" attempts to link plugin in /INSTALL_NAMESPACE Classification: Frameworks and Libraries Product: extra-cmake-modules Version: 6.1.0 Platform: Manjaro OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: ecm-bugs-n...@kde.org Reporter: k...@dennis2society.de Target Milestone: --- SUMMARY I am trying to migrate a Kate plugin from Qt5.15.* to 6.1. The CMakeLists.txt is calling kcoreaddons_add_plugin(my_plugin_name INSTALL_NAMESPACE "ktexteditor"), which with Qt6 builds the sources but fails upon linking because it is trying to link not in the build folder but in /INSTALL_NAMESPACE, i.e. in /ktexteditor (For Qt6 the install namespace should be kf6/ktexteditor). STEPS TO REPRODUCE In $project_dir I run: rm -rf build/ cmake -B build/ -D CMAKE_BUILD_TYPE=Release -D QT_MAJOR_VERSION=6 (or 5) cmake --build build/ This is working fine with Qt5 and will create ./build/plugin_name.so in the build folder. A subsequent sudo cmake --install build/ would then copy the plugin .so to /usr/lib/qt/plugins/ktexteditor/ With Qt6 I am getting a linker error: cmake --build build/ [..] [ 85%] Linking CXX shared module /kf6/ktexteditor/my_plugin.so /usr/bin/ld: cannot open output file /kf6/ktexteditor/my_plugin.so: No such file or directory collect2: error: ld returned 1 exit status make[2]: *** [CMakeFiles/my_plugin.dir/build.make:153: /kf6/ktexteditor/my_plugin.so] Error 1 make[1]: *** [CMakeFiles/Makefile2:653: CMakeFiles/my_plugin.dir/all] Error 2 make: *** [Makefile:146: all] Error 2 OBSERVED RESULT cmake --build build/ attempts to link the plugin .so in /kf6/ktexteditor/ EXPECTED RESULT cmake --build build/ should link the plugin .so in ./build/ SOFTWARE/OS VERSIONS Linux/KDE Plasma: Manjaro KDE Plasma Version: 6.0.4 KDE Frameworks Version: 6.1.0 Qt Version: 6.7.0 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 484918] Allow passing arguments to custom shortcuts
https://bugs.kde.org/show_bug.cgi?id=484918 Angelos Skembris changed: What|Removed |Added CC||a.skemb...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kdiff3] [Bug 486909] KDiff3 as git mergetool does not jump to first conflict position at startup
https://bugs.kde.org/show_bug.cgi?id=486909 michael changed: What|Removed |Added Latest Commit|https://invent.kde.org/sdk/ |https://invent.kde.org/sdk/ |kdiff3/-/commit/475d52c7442 |kdiff3/-/commit/17021d7e247 |4cabe881602713a1f4946a19871 |9e92b23d450b48843237c0d92e7 |32 |85 --- Comment #3 from michael --- Git commit 17021d7e2479e92b23d450b48843237c0d92e785 by Michael Reeves. Committed on 18/05/2024 at 19:27. Pushed by mreeves into branch 'master'. Fix bad value limiter Use std::max not std::min to limit line value range FIXED-IN:1.11.1 M +1-1src/Overview.cpp M +2-2src/difftextwindow.cpp https://invent.kde.org/sdk/kdiff3/-/commit/17021d7e2479e92b23d450b48843237c0d92e785 -- You are receiving this mail because: You are watching all bug changes.
[kdiff3] [Bug 485999] kdiff3 segaborts when comparing two files
https://bugs.kde.org/show_bug.cgi?id=485999 --- Comment #6 from michael --- May be related to wayland somehow. I do most tests under X11 which does not readily reproduce the scroll crash. -- You are receiving this mail because: You are watching all bug changes.
[kdiff3] [Bug 482790] Strange graphical issues make usage near impossible
https://bugs.kde.org/show_bug.cgi?id=482790 michael changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |WORKSFORME --- Comment #10 from michael --- As there seems to be something wiered going on with your setup. I am closing this for now. Looks like frame works /qt is having issues drawing. -- You are receiving this mail because: You are watching all bug changes.
[kdiff3] [Bug 484997] Kdiff3 and Kompare can't see the home folder or media folder
https://bugs.kde.org/show_bug.cgi?id=484997 michael changed: What|Removed |Added Resolution|--- |FIXED Status|CONFIRMED |RESOLVED --- Comment #10 from michael --- >From kdiff3s perspective this is resolved in the default settings. Manual override on your machine can also be done by command line or in some distros a plugin for system settings maybe provided . -- You are receiving this mail because: You are watching all bug changes.
[kdiff3] [Bug 459484] Crash and Windows SmartScreen warning
https://bugs.kde.org/show_bug.cgi?id=459484 michael changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |WORKSFORME --- Comment #7 from michael --- closing for now as its been a long time since this was reported. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 487037] kwin software cursor fallback locks up entire screen under certain conditions
https://bugs.kde.org/show_bug.cgi?id=487037 Neal Gompa changed: What|Removed |Added CC||ngomp...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kdiff3] [Bug 426568] Kdiff3 can't read remote files when comparing remote folders
https://bugs.kde.org/show_bug.cgi?id=426568 michael changed: What|Removed |Added Resolution|--- |WAITINGFORINFO Status|REPORTED|NEEDSINFO --- Comment #16 from michael --- I would like to confirm if this still happens with the 1.11.1 tag or master. I found a pair of bugs that would have resulted in arbitrary KIO job cancellation when handling non-file paths. Meta data retrieval and file reads where impacted by a race condition that resulted from this. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 487208] Full screen apps dim/turn off the screen when invoked under Wayland
https://bugs.kde.org/show_bug.cgi?id=487208 Ricardo J. Barberis changed: What|Removed |Added Assignee|noaha...@gmail.com |kwin-bugs-n...@kde.org Version|24.02.2 |6.0.4 Summary|Spectacle dims/turns off|Full screen apps dim/turn |the screen when invoked - |off the screen when invoked |Wayland only|under Wayland Product|Spectacle |kwin Component|General |wayland-generic -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 487208] Spectacle dims/turns off the screen when invoked - Wayland only
https://bugs.kde.org/show_bug.cgi?id=487208 Ricardo J. Barberis changed: What|Removed |Added Summary|Spectacle dims/turns off|Spectacle dims/turns off |the screen when invoked |the screen when invoked - ||Wayland only -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 487208] Spectacle dims/turns off the screen when invoked
https://bugs.kde.org/show_bug.cgi?id=487208 --- Comment #1 from Ricardo J. Barberis --- OK, I kept using my laptop and this screen dim happened again but spectacle wasn't involved at all, this might be a kwin_wayland or intel driver issue. Upgraded kwin-x11, switched to it and all problems gone. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 487213] New: Allow the wallpaper colour to adhere to the current theme.
https://bugs.kde.org/show_bug.cgi?id=487213 Bug ID: 487213 Summary: Allow the wallpaper colour to adhere to the current theme. Classification: Plasma Product: plasmashell Version: 6.0.4 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: Color wallpaper Assignee: plasma-b...@kde.org Reporter: 4wy78...@rokejulianlockhart.addy.io Target Milestone: 1.0 SUMMARY When using a coloured wallpaper, I want it to adhere to the colour preferences of my system theme (for me, either Breeze Dark or Breeze Light). However, this means that twice a day, when I change from Dark to Light or vice versa, I must go into `kcm_colors` and choose the background theme's hexadecimal colour representation, then duplicate that into the Color Wallpaper's color picker. On AOSP, I use https://github.com/cvzi/darkmodewallpaper/blob/aa44f98e84c28d657a0edd9e1c62c7287d16c6ab/README.md#-darkmodelivewallpaper to fix this. Although https://github.com/oskarsh/Yin-Yang/blob/03bfb2f25a85bef48cc9e1ff1a73cd3c2056376b/README.md#-yin-yang exists for my use case I'm requesting here, it's not packaged in any distribution's package managers, and I consider it an unnecessary stop gap for a feature which should be default with the DE. EXPECTED RESULT I shouldn't need to - I should be able to choose to have my wallpaper instead adhere to my system theme. SOFTWARE/OS VERSIONS Operating System: Fedora Linux 40 KDE Plasma Version: 6.0.4 KDE Frameworks Version: 6.2.0 Qt Version: 6.7.0 Kernel Version: 6.8.9-300.fc40.x86_64 (64-bit) Graphics Platform: Wayland Processors: 12 × AMD Ryzen 5 7600X 6-Core Processor Memory: 30.5 GiB of RAM Graphics Processor: AMD Radeon RX 5700 Manufacturer: ASRock Product Name: X670E Taichi ADDITIONAL INFORMATION https://github.com/oskarsh/Yin-Yang/blob/03bfb2f25a85bef48cc9e1ff1a73cd3c2056376b/README.md?plain=1#L32 and https://github.com/oskarsh/Yin-Yang/blob/03bfb2f25a85bef48cc9e1ff1a73cd3c2056376b/README.md?plain=1#L23 demonstrate that this is possible. -- You are receiving this mail because: You are watching all bug changes.
[kdiff3] [Bug 486909] KDiff3 as git mergetool does not jump to first conflict position at startup
https://bugs.kde.org/show_bug.cgi?id=486909 michael changed: What|Removed |Added Status|ASSIGNED|RESOLVED Latest Commit||https://invent.kde.org/sdk/ ||kdiff3/-/commit/475d52c7442 ||4cabe881602713a1f4946a19871 ||32 Version Fixed In||1.11.1 Resolution|--- |FIXED --- Comment #2 from michael --- Git commit 475d52c74424cabe881602713a1f4946a1987132 by Michael Reeves. Committed on 18/05/2024 at 22:51. Pushed by mreeves into tag '1.11.1'. Fix bad value limiter Use std::max not std::min to limit line value range FIXED-IN:1.11.1 M +1-1src/Overview.cpp M +2-2src/difftextwindow.cpp https://invent.kde.org/sdk/kdiff3/-/commit/475d52c74424cabe881602713a1f4946a1987132 -- You are receiving this mail because: You are watching all bug changes.
[kdiff3] [Bug 453575] Last modification date always show 18/19/20th January 1970 for remote files
https://bugs.kde.org/show_bug.cgi?id=453575 michael changed: What|Removed |Added Version Fixed In||1.11.1 --- Comment #3 from michael --- I believe this should be fixed in 1.11.1. Found to separate issues in handling non file urls via KIO. Together they caused the initial stat to abort at an arbitrary time. Typically not long enough to actually get the response. -- You are receiving this mail because: You are watching all bug changes.
[kdiff3] [Bug 480936] Looking Web page of Release notes for 1.10.7 and older ones.
https://bugs.kde.org/show_bug.cgi?id=480936 michael changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 487212] [BUG] Setting home directory to "Indexed" creates a duplicate, unremovable entry in System Settings
https://bugs.kde.org/show_bug.cgi?id=487212 pmqui...@proton.me changed: What|Removed |Added CC||pmqui...@proton.me -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 487212] New: [BUG] Setting home directory to "Indexed" creates a duplicate, unremovable entry in System Settings
https://bugs.kde.org/show_bug.cgi?id=487212 Bug ID: 487212 Summary: [BUG] Setting home directory to "Indexed" creates a duplicate, unremovable entry in System Settings Classification: Applications Product: systemsettings Version: 6.0.4 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: kcm_baloo Assignee: plasma-b...@kde.org Reporter: pmqui...@proton.me CC: baloo-bugs-n...@kde.org Target Milestone: --- *** If you're not sure this is actually a bug, instead post about it at https://discuss.kde.org If you're reporting a crash, attach a backtrace with debug symbols; see https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** SUMMARY [BUG] Setting home directory to "Indexed" creates a duplicate, unremovable entry in System Settings STEPS TO REPRODUCE Open File Search - System Settings Change your home directory to Indexed Click apply, then navigate to a different page and back to the original page, so it refreshes Observe that there are now two entries for your home directory, one indexed and one not indexed. Neither is removable. OBSERVED RESULT Observe that there are now two entries for your home directory, one indexed and one not indexed. Neither is removable. EXPECTED RESULT There should not be duplicate entries. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: Fedora 40 (available in About System) KDE Plasma Version: 6.0.4 KDE Frameworks Version: 6.2.0 Qt Version: 6.7.0 ADDITIONAL INFORMATION Steps 1-4 can be repeated, generating an endless number of duplicate entries. Screenshot of four (there should only ever be one) unremovable entries for my home directory, after repeating steps 1-4 three times: https://invent.kde.org/plasma/systemsettings/uploads/c9290b379407acaf104a477f836ef1e1/image.png -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 474207] Provide a scripting API to run arbitrary commands
https://bugs.kde.org/show_bug.cgi?id=474207 Aru Sahni changed: What|Removed |Added CC||arusa...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kdeplasma-addons] [Bug 450230] Improve cover and flip switch
https://bugs.kde.org/show_bug.cgi?id=450230 Nate Graham changed: What|Removed |Added Resolution|--- |FIXED Status|CONFIRMED |RESOLVED Version Fixed In||6.0 --- Comment #9 from Nate Graham --- Thanks! -- You are receiving this mail because: You are watching all bug changes.
[k3b] [Bug 487211] New: Ejected a non-readable dvd
https://bugs.kde.org/show_bug.cgi?id=487211 Bug ID: 487211 Summary: Ejected a non-readable dvd Classification: Applications Product: k3b Version: 23.08.5 Platform: unspecified OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@kde.org Reporter: hpf...@psnarf.org CC: mich...@jabster.pl, tr...@kde.org Target Milestone: --- Application: k3b (23.08.5) Qt Version: 5.15.13 Frameworks Version: 5.115.0 Operating System: Linux 6.9.0 x86_64 Windowing System: X11 Distribution: Slackware 15.0 x86_64 (post 15.0 -current) DrKonqi: 5.27.11 [KCrashBackend] -- Information about the crash: I inserted a DVD to play; unreadable due to bit rot. I ejected the disk, which took an unusally-long time, a hanged process. While the disc was still inside the player, k3b exploded, generating this bug report. I could not attempt to reproduce this, I just tossed in the ddrescue cue. The reporter is unsure if this crash is reproducible. -- Backtrace: Application: K3b (k3b), signal: Aborted [New LWP 25360] [New LWP 25362] [New LWP 25363] [New LWP 25364] [New LWP 25365] [New LWP 25366] [New LWP 25367] [New LWP 25371] [New LWP 25372] [New LWP 25373] [New LWP 25394] [New LWP 25531] [New LWP 30980] [New LWP 24837] [New LWP 24839] [New LWP 24840] [New LWP 24847] [New LWP 24848] [New LWP 24849] [New LWP 24850] [New LWP 24858] [New LWP 24859] [New LWP 24860] [New LWP 24861] [New LWP 24862] [New LWP 24863] [New LWP 24864] [New LWP 24865] [New LWP 24866] [New LWP 24867] [New LWP 24869] [New LWP 24870] [New LWP 24871] [New LWP 24877] [New LWP 24878] [New LWP 24879] [New LWP 24880] [New LWP 24881] [New LWP 24882] [New LWP 24883] [New LWP 24884] [New LWP 24885] [New LWP 24886] [New LWP 24887] [New LWP 24895] [New LWP 24896] [New LWP 24897] [New LWP 24898] [New LWP 24899] [New LWP 24900] [New LWP 27872] [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib64/libthread_db.so.1". 0x7fa021291566 in __futex_abstimed_wait_cancelable64 () from /lib64/libc.so.6 [KCrash Handler] #4 0x7fa021296aab in pthread_kill@@GLIBC_2.34 () from /lib64/libc.so.6 #5 0x7fa021242e12 in raise () from /lib64/libc.so.6 #6 0x7fa02122849f in abort () from /lib64/libc.so.6 #7 0x7fa0214a89db in ?? () from /usr/lib64/libstdc++.so.6 #8 0x7fa0214b7fea in ?? () from /usr/lib64/libstdc++.so.6 #9 0x7fa0214b8055 in std::terminate() () from /usr/lib64/libstdc++.so.6 #10 0x7fa0214b790c in __gxx_personality_v0 () from /usr/lib64/libstdc++.so.6 #11 0x7fa023b6d884 in ?? () from /usr/lib64/libgcc_s.so.1 #12 0x7fa023b6e285 in _Unwind_Resume () from /usr/lib64/libgcc_s.so.1 #13 0x7fa021899410 in ?? () from /usr/lib64/libQt5Core.so.5 #14 0x7fa0218cd0ad in qt_message_output(QtMsgType, QMessageLogContext const&, QString const&) () from /usr/lib64/libQt5Core.so.5 #15 0x7fa0219d65c8 in QDebug::~QDebug() () from /usr/lib64/libQt5Core.so.5 #16 0x7fa02cbd1f2b in ?? () from /usr/lib64/libk3bdevice.so.8 #17 0x7fa02cbd24aa in ?? () from /usr/lib64/libk3bdevice.so.8 #18 0x7fa02cbcc3bc in K3b::Device::Device::read10(unsigned char*, unsigned int, unsigned long, unsigned int, bool) const () from /usr/lib64/libk3bdevice.so.8 #19 0x7fa02cf39a6d in ?? () from /usr/lib64/libk3blib.so.8 #20 0x7fa02cf39c7c in ?? () from /usr/lib64/libk3blib.so.8 #21 0x7fa02cf3b238 in ?? () from /usr/lib64/libk3blib.so.8 #22 0x7fa02cedcee5 in K3b::Thread::run() () from /usr/lib64/libk3blib.so.8 #23 0x7fa0218d3ac9 in ?? () from /usr/lib64/libQt5Core.so.5 #24 0x7fa021294d57 in start_thread () from /lib64/libc.so.6 #25 0x7fa0213196a8 in clone3 () from /lib64/libc.so.6 Thread 51 (Thread 0x7f9f7e0006c0 (LWP 24900) "k3b:sh3"): #1 0x7fa021293d2e in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libc.so.6 #2 0x7fa01150b469 in ?? () from /usr/lib64/dri/radeonsi_dri.so #3 0x7fa0114ecbfb in ?? () from /usr/lib64/dri/radeonsi_dri.so #4 0x7fa01150b3a7 in ?? () from /usr/lib64/dri/radeonsi_dri.so #5 0x7fa021294d57 in start_thread () from /lib64/libc.so.6 #6 0x7fa0213196a8 in clone3 () from /lib64/libc.so.6 Thread 50 (Thread 0x7f9f7ea006c0 (LWP 24899) "k3b:gl0"): #1 0x7fa021293d2e in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libc.so.6 #2 0x7fa01150b469 in ?? () from /usr/lib64/dri/radeonsi_dri.so #3 0x7fa0114ecbfb in ?? () from /usr/lib64/dri/radeonsi_dri.so #4 0x7fa01150b3a7 in ?? () from /usr/lib64/dri/radeonsi_dri.so #5 0x7fa021294d57 in start_thread () from /lib64/libc.so.6 #6 0x7fa0213196a8 in clone3 () from /lib64/libc.so.6 Thread 49 (Thread 0x7f9f7f4006c0 (LWP 24898) "k3b:gdrv0"): #1 0x7fa021293d2e in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libc.so.6 #2 0x7fa01150b469 in ?? () from /usr/lib64/dri/radeonsi_dri.so #3
[dolphin] [Bug 424723] When going back or up, underline the folder you just came from instead of selecting it
https://bugs.kde.org/show_bug.cgi?id=424723 Felix Ernst changed: What|Removed |Added Latest Commit||https://invent.kde.org/syst ||em/dolphin/-/commit/122fee5 ||625f0285ec4ebda79162c723909 ||89eb2a Resolution|--- |FIXED Status|ASSIGNED|RESOLVED --- Comment #13 from Felix Ernst --- Git commit 122fee5625f0285ec4ebda79162c72390989eb2a by Felix Ernst. Committed on 18/05/2024 at 22:18. Pushed by felixernst into branch 'master'. Avoid implicitly selecting items Items should only be selected if the user wants to act on them. However, previous to this commit we sometimes selected items even when there is no reason to assume that the user would like to act on them. Such selections are dangerous because they make it more likely that the user manipulates items by accident which they never even explicitly selected. Example: The "Up" action is used to navigate to the parent folder. This will implicitly select the folder one emerged from after opening the parent folder, so just one accidental press of the Delete key will lead to data loss if the press goes unnoticed. This scenario would have been avoided if no folder had been selected automatically. The above example becomes even more dangerous if the user is acting with elevated privileges. The following implicit selections of items are being removed: - Selecting items that are being activated - Selecting folders one emerges from Even though these items will no longer be selected after these actions, they will still be marked as current. The only downside I see is that our indication of which item is "current" is a lot weaker than the selection highlight, so it might be more difficult to spot which folder one has emerged from. However, this could be counter-acted with some other temporary indication if this really turns out to be a problem. The only downside I see is that our indication of which item is "current" is a lot weaker than the selection highlight, so it might be more difficult to spot which folder one has emerged from. However, this could be counter-acted with some other temporary indication if this really turns out to be a problem. M +2-1src/dolphinviewcontainer.cpp M +17 -4src/kitemviews/kitemlistcontroller.cpp M +43 -4src/tests/dolphinmainwindowtest.cpp M +7-0src/tests/kitemlistcontrollertest.cpp https://invent.kde.org/system/dolphin/-/commit/122fee5625f0285ec4ebda79162c72390989eb2a -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 487210] New: plasmashell doesn't start due to systemmonitor plasmoid placed in Panel
https://bugs.kde.org/show_bug.cgi?id=487210 Bug ID: 487210 Summary: plasmashell doesn't start due to systemmonitor plasmoid placed in Panel Classification: Plasma Product: plasmashell Version: master Platform: Neon OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: piotr.mierzwin...@gmail.com CC: k...@davidedmundson.co.uk Target Milestone: 1.0 SUMMARY Starting Plasma 6 my favorite system monitor, so "System Load Viewer" stopped work, so I switched to systemmonitor plasmoids. Both were placed in panel. Since couple days also this stopped work. After login I can see black screen and if I would not have restore session I would thought that nothing starts. Anyway when I try to run plasmashell I can see something like this: $ plasmashell kf.config.core: Created a KConfigGroup on an inaccessible config location ":/icons/breeze/index.theme" "Icon Theme" kf.config.core: Created a KConfigGroup on an inaccessible config location ":/icons/breeze/index.theme" "Icon Theme" kf.svg: The theme "ROUNDED-COLOR" uses the legacy metadata.desktop. Consider contacting the author and asking them update it to use the newer JSON format. kf.svg: The theme "ROUNDED-COLOR" uses the legacy metadata.desktop. Consider contacting the author and asking them update it to use the newer JSON format. kf.plasma.core: The theme "ROUNDED-COLOR" uses the legacy metadata.desktop. Consider contacting the author and asking them update it to use the newer JSON format. kf.plasma.core: The theme "ROUNDED-COLOR" uses the legacy metadata.desktop. Consider contacting the author and asking them update it to use the newer JSON format. KPackageStructure of KPluginMetaData(pluginId:"org.kde.plasma.systemloadviewer", fileName: "/home/piotr/.local/share/plasma/plasmoids/org.kde.plasma.systemloadviewer/metadata.json") does not match requested format "Plasma/Applet" KPackageStructure of KPluginMetaData(pluginId:"com.softtechok.systemmonitorplasmoid", fileName: "/home/piotr/.local/share/plasma/plasmoids/com.softtechok.systemmonitorplasmoid/metadata.json") does not match requested format "Plasma/Applet" plasmashell: symbol lookup error: /usr/lib/x86_64-linux-gnu/qt6/plugins/plasma/applets/org.kde.plasma.systemmonitor.so: undefined symbol: _ZN9KSysGuard20SensorFaceControllerC1ER12KConfigGroupP10QQmlEngine STEPS TO REPRODUCE 1. Before should be added to panel any plasmoid coming from systemmonitor. I had 2. CPU monitor and memory monitor 2. Login to Plasma 3. OBSERVED RESULT black screen EXPECTED RESULT plasmashell should start nornally SOFTWARE/OS VERSIONS Linux/KDE Plasma: Yes (available in About System) KDE Plasma Version: 6.0.80 KDE Frameworks Version: 6.3.0 Qt Version: 6.7.0 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 487209] New: Allow different wallpapers per orientation.
https://bugs.kde.org/show_bug.cgi?id=487209 Bug ID: 487209 Summary: Allow different wallpapers per orientation. Classification: Plasma Product: plasmashell Version: 6.0.4 Platform: Fedora RPMs URL: https://discuss.kde.org/t/different-wallpaper-in-lands cape-and-portrait/15558/2?u=rokejulianlockhart OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: Image Wallpaper Assignee: plasma-b...@kde.org Reporter: 4wy78...@rokejulianlockhart.addy.io CC: notm...@gmail.com, qydwhotm...@gmail.com Target Milestone: 1.0 SUMMARY I recently applied a wallpaper for the first time. However, this causes slight problems in portrait mode, because I've yet to locate a wallpaper which tiles in landscape and portrait. Consequently, I'd like to be able to utilize an alternative when in portrait. After all, it's standard to use the same wallpaper on a tablet and desktop, but a different one on a smartphone, despite all 3 commonly being 16:9 and of 1440p resolution nowadays. SOFTWARE/OS VERSIONS Operating System: Fedora Linux 40 KDE Plasma Version: 6.0.4 KDE Frameworks Version: 6.2.0 Qt Version: 6.7.0 Kernel Version: 6.8.9-300.fc40.x86_64 (64-bit) Graphics Platform: Wayland Processors: 12 × AMD Ryzen 5 7600X 6-Core Processor Memory: 30.5 GiB of RAM Graphics Processor: AMD Radeon RX 5700 Manufacturer: ASRock Product Name: X670E Taichi ADDITIONAL INFORMATION https://discuss.kde.org/t/different-wallpaper-in-landscape-and-portrait/15558/2?u=rokejulianlockhart -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 439339] Konsole window doesn't honor Initial terminal size columns setting
https://bugs.kde.org/show_bug.cgi?id=439339 Richard Ullger changed: What|Removed |Added CC|rull...@protonmail.com | -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 487208] New: Spectacle dims/turns off the screen when invoked
https://bugs.kde.org/show_bug.cgi?id=487208 Bug ID: 487208 Summary: Spectacle dims/turns off the screen when invoked Classification: Applications Product: Spectacle Version: 24.02.2 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: major Priority: NOR Component: General Assignee: noaha...@gmail.com Reporter: rica...@palmtx.com.ar CC: k...@david-redondo.de Target Milestone: --- SUMMARY When I invoke Spactacle, either via PrintScreen key, krunner or konsole, my screen dims and there's no easy way to bring it back to life STEPS TO REPRODUCE 1. Press PrintScreen key or launch spectacle some other way 2. Watch the screen dim with no way to recover it OBSERVED RESULT Screen dims completely EXPECTED RESULT Screen shoud remain on SOFTWARE/OS VERSIONS spectacle 24.02.2 Operating System: Fedora Linux 40 KDE Plasma Version: 6.0.4 KDE Frameworks Version: 6.2.0 Qt Version: 6.7.0 Kernel Version: 6.8.9-300.fc40.x86_64 (64-bit) Graphics Platform: Wayland Processors: 8 × Intel® Core™ i5-1035G1 CPU @ 1.00GHz Memory: 15.2 GiB of RAM Graphics Processor: Mesa Intel® UHD Graphics ADDITIONAL INFORMATION The first time it happend I connected a secondary monitor, it took its time but worked, so I at least was able to save my work and close my programs before rebooting. Before rebooting I tried disabling the laptop screen from system settings, modifying the screen brightnes, making the external monitor primary, etc. to no avail. Today at home I started experimenting and if I put my laptop to sleep (which takes longer than usual) it resumes correctly, except if I didn't close spectacle the screen dims again, so I have to blindly Alt+Tab out of spectacle before hitting th sleep button. When invoked from konsole/yakuake (e.g. `spectacle -t`), this message is repeteadly printed: ``` libva info: VA-API version 1.21.0 libva info: Trying to open /usr/lib64/dri-nonfree/iHD_drv_video.so libva info: Found init function __vaDriverInit_1_21 libva info: va_openDriver() returns 0 kpipewire_record_logging: VAAPI: Display initialized kpipewire_record_logging: VAAPI: API version 1 . 21 kpipewire_record_logging: VAAPI: Intel iHD driver for Intel(R) Gen Graphics - 24.1.5 () in use for device "/dev/dri/renderD128" ``` -- You are receiving this mail because: You are watching all bug changes.
[drkonqi] [Bug 483073] Crashed after another app crashed
https://bugs.kde.org/show_bug.cgi?id=483073 Richard Ullger changed: What|Removed |Added CC|rull...@protonmail.com | -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 487207] New: Gwenview's pixel interpolation activation threshold should be possible to configure, and it should be possible to disable.
https://bugs.kde.org/show_bug.cgi?id=487207 Bug ID: 487207 Summary: Gwenview's pixel interpolation activation threshold should be possible to configure, and it should be possible to disable. Classification: Applications Product: gwenview Version: 24.02.2 Platform: Fedora RPMs URL: https://discuss.kde.org/t/how-to-disable-pixel-interpo lation-in-gwenview/15538/3?u=rokejulianlockhart OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: general Assignee: gwenview-bugs-n...@kde.org Reporter: 4wy78...@rokejulianlockhart.addy.io Target Milestone: --- SUMMARY Low resolution images are rendered blurry despite being at low resolution because whether Gwenview's pixel interpolation is active is determined by whether the resolution of the viewport (affected by zoom and original image resolution) is above or below an arbitrary threshold (somewhere below 46 DPI, but above 24 DPI) defined in code, and unconfigurable by the user. STEPS TO REPRODUCE Export an image at, or resize an image to, 46 DPI and 24 DPI each. OBSERVED RESULT One is rendered blurry, the other is not. EXPECTED RESULT The same should occur by default, but the user should be able to configure the threshold (because those who create a lot of pixel art shall need that) and be able to override it from the menu bar context menu per image per session. SOFTWARE/OS VERSIONS Operating System: Fedora Linux 40 KDE Plasma Version: 6.0.4 KDE Frameworks Version: 6.2.0 Qt Version: 6.7.0 Kernel Version: 6.8.9-300.fc40.x86_64 (64-bit) Graphics Platform: Wayland Processors: 12 × AMD Ryzen 5 7600X 6-Core Processor Memory: 30.5 GiB of RAM Graphics Processor: AMD Radeon RX 5700 Manufacturer: ASRock Product Name: X670E Taichi ADDITIONAL INFORMATION https://discuss.kde.org/t/how-to-disable-pixel-interpolation-in-gwenview/15538/3?u=rokejulianlockhart -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 415364] Implement feature to disable touchpad when mouse is plugged in when using Libinput driver
https://bugs.kde.org/show_bug.cgi?id=415364 Richard Ullger changed: What|Removed |Added CC|rull...@protonmail.com | -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 394403] Width column list resize every time to restart
https://bugs.kde.org/show_bug.cgi?id=394403 Richard Ullger changed: What|Removed |Added CC|rull...@protonmail.com | -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 484597] PrintScreen shortcut lost during upgrade
https://bugs.kde.org/show_bug.cgi?id=484597 Ricardo J. Barberis changed: What|Removed |Added CC||rica...@palmtx.com.ar --- Comment #10 from Ricardo J. Barberis --- Could this be an openSUSE issue? I haven't experienced this bug with Fedora 38/39/40 nor before with Slackware 14/15/-current. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 482987] With fractional scale, bottom edge of screen has pixels that are held to the color of previously opened windows after closing those windows
https://bugs.kde.org/show_bug.cgi?id=482987 --- Comment #38 from Tyler Duzan --- I'm waiting for 6.0.5 to be available in Arch, and then I will confirm the fix in a comment here. Thanks for the rapid resolution! -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 486665] Plasmashell crashes randomly
https://bugs.kde.org/show_bug.cgi?id=486665 Phillip changed: What|Removed |Added Resolution|--- |FIXED Status|REOPENED|RESOLVED --- Comment #5 from Phillip --- Closing - sorry this looks to be a completely different core. Apologies -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 482987] With fractional scale, bottom edge of screen has pixels that are held to the color of previously opened windows after closing those windows
https://bugs.kde.org/show_bug.cgi?id=482987 Bug Janitor Service changed: What|Removed |Added Priority|HI |VHI -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 486665] Plasmashell crashes randomly
https://bugs.kde.org/show_bug.cgi?id=486665
Phillip changed:
What|Removed |Added
CC||pwpera...@gmail.com
Status|RESOLVED|REOPENED
Resolution|FIXED |---
--- Comment #4 from Phillip ---
Running into this same issue, reproduced this consistently in Plasma6 Wayland
trying to play games via steam.
RTX 3080ti
Kernel 6.9.1-arch1-1
plasmashell 6.0.4
GDB dump
I can reproduce consistently within a couple of minutes I start a game via
Steam.
#0 0x712c19f991f6 in std::__atomic_base::load
(__m=std::memory_order_acquire, this=0x3c004fbb96a18a8) at
/usr/include/c++/13.2.1/atomic:576
#1 std::atomic::load (__m=std::memory_order_acquire,
this=0x3c004fbb96a18a8) at /usr/include/c++/13.2.1/atomic:577
#2 QAtomicOps::loadAcquire (_q_value=,
_q_value=) at
/usr/src/debug/qt6-base/qtbase/src/corelib/thread/qatomic_cxx11.h:214
#3 QBasicAtomicPointer::loadAcquire (this=0x3c004fbb96a18a8,
this=) at
/usr/src/debug/qt6-base/qtbase/src/corelib/thread/qbasicatomic.h:177
#4 QObjectPrivate::connectImpl (sender=sender@entry=0x712c080093b0,
signal_index=5, receiver=receiver@entry=0x712c080093b0, slot=slot@entry=0x0,
slotObjRaw=slotObjRaw@entry=0x5a5e774d9b00, type=0, types=0x0,
senderMetaObject=0x712c0f262700 )
at /usr/src/debug/qt6-base/qtbase/src/corelib/kernel/qobject.cpp:5249
#5 0x712c19f995e3 in QObject::connectImpl (sender=0x712c080093b0,
signal=, receiver=0x712c080093b0, slot=0x0,
slotObjRaw=0x5a5e774d9b00, type=Qt::AutoConnection, types=0x0,
senderMetaObject=) at
/usr/src/debug/qt6-base/qtbase/src/corelib/kernel/qobject.cpp:5180
#6 0x712c0f25667d in
KScreen::WaylandConfig::setupRegistry()::{lambda(void*, wl_registry*, unsigned
int, char const*, unsigned int)#1}::_FUN(void*, wl_registry*, unsigned int,
char const*, unsigned int) () at /usr/include/qt6/QtCore/qobject.h:257
#7 0x712c1ac40596 in ffi_call_unix64 () at ../src/x86/unix64.S:104
#8 0x712c1ac3d00e in ffi_call_int (cif=cif@entry=0x7ffdf383d9a0,
fn=, rvalue=, avalue=,
closure=closure@entry=0x0) at ../src/x86/ffi64.c:673
#9 0x712c1ac3fbd3 in ffi_call (cif=cif@entry=0x7ffdf383d9a0, fn=, rvalue=rvalue@entry=0x0, avalue=avalue@entry=0x7ffdf383da70) at
../src/x86/ffi64.c:710
#10 0x712c1c734645 in wl_closure_invoke
(closure=closure@entry=0x712c1a00, target=,
target@entry=0x5a5e774a9970, opcode=opcode@entry=0, data=,
flags=1) at ../wayland-1.22.0/src/connection.c:1025
#11 0x712c1c734e73 in dispatch_event (display=display@entry=0x5a5e774d4910,
queue=0x5a5e774d4a00) at ../wayland-1.22.0/src/wayland-client.c:1631
#12 0x712c1c73513c in dispatch_queue (queue=0x5a5e774d4a00,
display=0x5a5e774d4910) at ../wayland-1.22.0/src/wayland-client.c:1777
#13 wl_display_dispatch_queue_pending (display=0x5a5e774d4910,
queue=0x5a5e774d4a00) at ../wayland-1.22.0/src/wayland-client.c:2019
#14 0x712c1c38ab5e in QtWaylandClient::EventThread::readAndDispatchEvents
(this=0x5a5e774e37b0) at
/usr/src/debug/qt6-wayland/qtwayland-everywhere-src-6.7.0/src/client/qwaylanddisplay.cpp:227
#15 0x712c19f8c147 in QObject::event (this=0x5a5e774d46e0,
e=0x712c5150) at
/usr/src/debug/qt6-base/qtbase/src/corelib/kernel/qobject.cpp:1446
#16 0x712c1bcfc44d in QApplicationPrivate::notify_helper (this=, receiver=0x5a5e774d46e0, e=0x712c5150) at
/usr/src/debug/qt6-base/qtbase/src/widgets/kernel/qapplication.cpp:3287
#17 0x712c19f3fe18 in QCoreApplication::notifyInternal2
(receiver=0x5a5e774d46e0, event=event@entry=0x712c5150) at
/usr/src/debug/qt6-base/qtbase/src/corelib/kernel/qcoreapplication.cpp:1142
#18 0x712c19f401d2 in QCoreApplication::sendEvent (event=0x712c5150,
receiver=) at
/usr/src/debug/qt6-base/qtbase/src/corelib/kernel/qcoreapplication.cpp:1583
#19 QCoreApplicationPrivate::sendPostedEvents (receiver=0x0, event_type=0,
data=0x5a5e773c1ba0) at
/usr/src/debug/qt6-base/qtbase/src/corelib/kernel/qcoreapplication.cpp:1940
#20 0x712c1a1959ac in QCoreApplication::sendPostedEvents (receiver=0x0,
event_type=0) at
/usr/src/debug/qt6-base/qtbase/src/corelib/kernel/qcoreapplication.cpp:1797
#21 postEventSourceDispatch (s=0x5a5e774cfd70) at
/usr/src/debug/qt6-base/qtbase/src/corelib/kernel/qeventdispatcher_glib.cpp:244
#22 0x712c18a6aa89 in g_main_dispatch (context=0x712c08000f20) at
../glib/glib/gmain.c:3344
#23 0x712c18acc9b7 in g_main_context_dispatch_unlocked
(context=0x712c08000f20) at ../glib/glib/gmain.c:4152
#24 g_main_context_iterate_unlocked.isra.0
(context=context@entry=0x712c08000f20, block=block@entry=1,
dispatch=dispatch@entry=1, self=) at ../glib/glib/gmain.c:4217
#25 0x712c18a69f95 in g_main_context_iteration (context=0x712c08000f20,
may_block=1) at ../glib/glib/gmain.c:4282
#26 0x712c1a193389 in QEventDispatcherGlib::processEvents
(this=0x5a5e774e5df0, flags=...) at
[yakuake] [Bug 433171] Yakuake Opens, but does not close under wayland
https://bugs.kde.org/show_bug.cgi?id=433171 --- Comment #7 from Ricardo J. Barberis --- Sorry, my system info: yakuake 24.02.2 Operating System: Fedora Linux 40 KDE Plasma Version: 6.0.4 KDE Frameworks Version: 6.2.0 Qt Version: 6.7.0 Kernel Version: 6.8.9-300.fc40.x86_64 (64-bit) Graphics Platform: Wayland Processors: 8 × Intel® Core™ i5-1035G1 CPU @ 1.00GHz Memory: 15.2 GiB of RAM Graphics Processor: Mesa Intel® UHD Graphics -- You are receiving this mail because: You are watching all bug changes.
[yakuake] [Bug 433171] Yakuake Opens, but does not close under wayland
https://bugs.kde.org/show_bug.cgi?id=433171 --- Comment #6 from Ricardo J. Barberis --- I have a similar problem on Wayland now which I believe is related to this. With "Use Open/Retract action to focus window" enabled, F12 never focuses Yakuake if it's open behind another window, only if it's retracted. Especially anoying if you have "Keep window open when it loses focus" (translated from spanish, might be inaccurate) enabled too. I had to make a window rule to make Yakuake show up in the window switcher for this reason, and because I'm used to Alt+Tab between Yakuake and my web browser. -- You are receiving this mail because: You are watching all bug changes.
[KBibTeX] [Bug 484421] KBibTex sometimes loses track of the active element, resulting in shortcuts affecting the wrong item and other issues
https://bugs.kde.org/show_bug.cgi?id=484421 Thomas Fischer changed: What|Removed |Added Latest Commit||7790859456a50ff8e31e918da28 ||35b03cda51075 Version Fixed In||0.10.1 Ever confirmed|0 |1 Status|REPORTED|ASSIGNED --- Comment #1 from Thomas Fischer --- I am having trouble reproducing the described problem *sometimes*, i.e. sometimes I get the result you describe, sometimes not. I suspect the issue you describe is cause when the information what is selected (no, one, or several lines) diverges from what is the 'current' line. Maybe there is a deeper problem or a bug in Qt, but it seems to suffice to set the current line to be one of the selected ones (if there are any) when the main list receives focus after closing the menu. Please let me know if this commit fixes your problem: https://invent.kde.org/thomasfischer/kbibtex/-/commit/7790859456a50ff8e31e918da2835b03cda51075 -- You are receiving this mail because: You are watching all bug changes.
[KDE Itinerary] [Bug 487206] New: FR: Ability to select an alternative in advance
https://bugs.kde.org/show_bug.cgi?id=487206 Bug ID: 487206 Summary: FR: Ability to select an alternative in advance Classification: Applications Product: KDE Itinerary Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: general Assignee: vkra...@kde.org Reporter: kde.lw...@thibaultmol.link Target Milestone: --- While it's great that the app allows you to search for an alternative, it would be nice if you could pre-pick an alternative (in case the route planning api goes down somehow / you don't have connection for whatever reason). Also it would be uesful to show this in the main overview window, so at a glance you can see "oh ok, if I miss that one, my next option is at xx:xx) without having to click through the menu''s -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 458245] Kmail 5.21.0 / 22.08.0 does no longer respect per contact html and remote content settings
https://bugs.kde.org/show_bug.cgi?id=458245 Ricardo J. Barberis changed: What|Removed |Added Status|REOPENED|CONFIRMED --- Comment #17 from Ricardo J. Barberis --- (In reply to Boltronics from comment #15) > (In reply to Axel Braun from comment #14) > > That works in the preview pane, but if I double click the mail t oopen it in > > a separate window I still need to reload HTML content -> reopening > > I too can confirm this. Sorry I didn't think to test that previously. It's > not part of my usual workflow. This keeps happening in Kmail 6.0.2 (24.02.2) -- You are receiving this mail because: You are watching all bug changes.
[kdeplasma-addons] [Bug 450230] Improve cover and flip switch
https://bugs.kde.org/show_bug.cgi?id=450230 --- Comment #8 from Ricardo J. Barberis --- As of today, both flip and cover switch have the blurred wallpaper as a background. I think this bug can be safely closed. -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 394403] Width column list resize every time to restart
https://bugs.kde.org/show_bug.cgi?id=394403 --- Comment #9 from Ricardo J. Barberis --- This still happens with Kmail 6.0.2 (24.02.2). Sometimes columns also resize during a filtering operation, but this happened in Plamsa 5's version of Kmail as well. FWIW, I recently switched to Wayland, which made no diference. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 487098] KWin on X11: No compositing on startup, cannot be re-enabled
https://bugs.kde.org/show_bug.cgi?id=487098 Andrew Gunnerson changed: What|Removed |Added CC||accounts+...@chiller3.com --- Comment #1 from Andrew Gunnerson --- This was a Fedora-specific issue and should be fixed in the `kwin-x11-6.0.4.1-3.fc40` update: https://bugzilla.redhat.com/show_bug.cgi?id=2280899 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 482987] With fractional scale, bottom edge of screen has pixels that are held to the color of previously opened windows after closing those windows
https://bugs.kde.org/show_bug.cgi?id=482987 Zamundaaa changed: What|Removed |Added CC||kdebugs.81do7@haxing.ninja --- Comment #37 from Zamundaaa --- *** Bug 487168 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 487168] KWin 1.5x UI Scaling + 2256x1504 results in garbage pixels at the bottom of the screen
https://bugs.kde.org/show_bug.cgi?id=487168 Zamundaaa changed: What|Removed |Added Resolution|--- |DUPLICATE Status|REPORTED|RESOLVED CC||xaver.h...@gmail.com --- Comment #3 from Zamundaaa --- *** This bug has been marked as a duplicate of bug 482987 *** -- You are receiving this mail because: You are watching all bug changes.
[KDE Itinerary] [Bug 487205] Improve search results for locations: don't show NL locations when searching in belguim
https://bugs.kde.org/show_bug.cgi?id=487205 --- Comment #1 from Thibault Molleman --- Created attachment 169603 --> https://bugs.kde.org/attachment.cgi?id=169603=edit screenshot2 -- You are receiving this mail because: You are watching all bug changes.
[KDE Itinerary] [Bug 487205] New: Improve search results for locations: don't show NL locations when searching in belguim
https://bugs.kde.org/show_bug.cgi?id=487205 Bug ID: 487205 Summary: Improve search results for locations: don't show NL locations when searching in belguim Classification: Applications Product: KDE Itinerary Version: 23.07.80 Platform: Other OS: Android 13.x Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: vkra...@kde.org Reporter: kde.lw...@thibaultmol.link Target Milestone: --- Created attachment 169602 --> https://bugs.kde.org/attachment.cgi?id=169602=edit screenshot1 If you search for "Aalter" in Belgium, the first result you get is indeed Aalter, but 'Aalten' which is a location in NL still shows up pretty high up in this list. My main problem is that if you search for 'Aalter station', you actually get 'Aalten station' instead of 'Aalter'(the station) -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 487204] New: Bouncing icon disappears with delay when launching console app with from .desktop file with Terminal=true
https://bugs.kde.org/show_bug.cgi?id=487204 Bug ID: 487204 Summary: Bouncing icon disappears with delay when launching console app with from .desktop file with Terminal=true Classification: Plasma Product: kwin Version: 6.0.4 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kwin-bugs-n...@kde.org Reporter: equ...@gmail.com Target Milestone: --- SUMMARY When launching console app that provides desktop entry with Terminal=true key (for example btop), bouncing "loading" icon is shown for 5 seconds after Konsole have already opened. STEPS TO REPRODUCE 1. Install btop 2. Launch btop from application launcher OBSERVED RESULT Bouncing app icon is shown for 5 seconds after Konsole is opened. EXPECTED RESULT Bouncing icon is hidden immediately after app is launched. SOFTWARE/OS VERSIONS Linux/KDE Plasma: openSUSE Tumbleweed KDE Plasma Version: 6.0.4 KDE Frameworks Version: 6.2.0 Qt Version: 6.7.0 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 487203] New: flatpak: cannot open kmail mail attachments with default apps or any other app
https://bugs.kde.org/show_bug.cgi?id=487203 Bug ID: 487203 Summary: flatpak: cannot open kmail mail attachments with default apps or any other app Classification: Applications Product: kontact Version: 6.0.2 Platform: Flatpak OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: mail Assignee: kdepim-b...@kde.org Reporter: rob...@riemann.cc Target Milestone: --- Created attachment 169601 --> https://bugs.kde.org/attachment.cgi?id=169601=edit first dialogue happens when clicking on pdf attachment, second one when clicking on open with SUMMARY I have Kontact with Kmail installed as Flatpak from fedora flatpak repository. When I receive pdfs as attachment, I cannot open them with okular without saving them first to disk. Same issue for any other attachment types. STEPS TO REPRODUCE 1. receive an email with pdf attachment (or other file) 2. click on them for open 3. notice that okular is not an option and app chooser is basically empty OBSERVED RESULT Cannot open with okular EXPECTED RESULT flatpak aplication chooser portal opens and permits to open file with okular ADDITIONAL INFORMATION Related Discussion at https://discussion.fedoraproject.org/t/evolution-flatpak-cant-open-pdf-from-attachments-when-composing-email/24230 Related flatpak bug concerning composing mails with attachment: while granting kontact access to all system files may be good workaround, it would be better to rely on the flatpak open file portal: https://bugs.kde.org/show_bug.cgi?id=486838 -- You are receiving this mail because: You are watching all bug changes.
[plasma-systemmonitor] [Bug 487201] System Monitor crashes when opening details sidepanel
https://bugs.kde.org/show_bug.cgi?id=487201 Bug Janitor Service changed: What|Removed |Added Severity|normal |crash -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 487202] New: Filter Dialog Closes / Applies When Losing Focus
https://bugs.kde.org/show_bug.cgi?id=487202 Bug ID: 487202 Summary: Filter Dialog Closes / Applies When Losing Focus Classification: Applications Product: krita Version: 5.2.2 Platform: Appimage OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Filters Assignee: krita-bugs-n...@kde.org Reporter: minnobr...@gmail.com Target Milestone: --- Sent from: https://krita-artists.org/t/filter-dialogs-close-apply-when-losing-focus/91670/11 I was told to make a new report in the above thread, but this is a duplicate of: https://bugs.kde.org/show_bug.cgi?id=352747 When using a dialog under filter toolbar, if you click off the dialog anywhere onto Krita, the dialog acts like you hit the apply button, and closes. If you have 2 copies of Krita running, and you click into the second one, the dialog closes, but if you click off of Krita onto another application this does not close the dialog. STEPS TO REPRODUCE 1. Open a filter dialog, Filter > Adjust > Dodge (or any other) 2. Click onto the canvas, or anywhere on Krita that is not the dialog 3. The dialog will close as if you hit apply OBSERVED RESULT The dialog applies the filter EXPECTED RESULT The dialog does nothing SOFTWARE/OS VERSIONS Qt Version (compiled): 5.15.7 Qt Version (loaded): 5.15.7 Appimage build: Yes Linux: EndeavourOS rolling x86_64 Kernel: 6.8.9-arch1-2 WM: i3 (X11) **I was also able to reproduce in a VM with:** Linux: EndeavourOS rolling x86_64 Kernel: 6.8.9-arch1-2 DE: KDE Plasma 6.0.4 WM: KWin (X11) Loaded Python Plugins colorspace comics_project_management_tools documenttools exportlayers filtermanager lastdocumentsdocker plugin_importer quick_settings_docker scripter tenbrushes tenscripts -- You are receiving this mail because: You are watching all bug changes.
[kdiff3] [Bug 484997] Kdiff3 and Kompare can't see the home folder or media folder
https://bugs.kde.org/show_bug.cgi?id=484997 --- Comment #9 from bugsie --- (In reply to Silviu from comment #3) > The same behavior is for Kompare. > Both application were installed using flatpak: > sudo flatpak install -y flathub org.kde.kdiff3 > sudo flatpak install -y flathub org.kde.kompare > > When I saw that the /home/user_name folder is seed as empty even if this is > not empty and /media folder can't be seen, I tried using next commands: > sudo flatpak override kde.org.kdiff3 --filesystem=host > sudo flatpak override kde.org.kompare --filesystem=host > > but the results is the same. > > but The correct syntax is sudo flatpak override org.kde.kompare --filesystem=host Problem solved? -- You are receiving this mail because: You are watching all bug changes.
[amarok] [Bug 487199] to be able to resize the central window where is showed lyrics, current track, etc... [suggestion]
https://bugs.kde.org/show_bug.cgi?id=487199 Tuomas Nurmi changed: What|Removed |Added CC||tuo...@norsumanageri.org --- Comment #1 from Tuomas Nurmi --- Hi, thank you for your request! The bugtracker also contains the wishlist, so this is the right place! I'm not sure if I've grasped your idea yet, however; do you mean you would like current track and lyrics to have different width? (The context area's common width can be changed by dragging from the edge, and the individual height of each applet can be changed by dragging in edit mode). Could you perhaps provide some kind of mockup on your idea? -- You are receiving this mail because: You are watching all bug changes.
[plasma-systemmonitor] [Bug 487201] System Monitor crashes when opening details sidepanel
https://bugs.kde.org/show_bug.cgi?id=487201 Ben Daines changed: What|Removed |Added CC||benjamindai...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasma-systemmonitor] [Bug 487201] New: System Monitor crashes when opening details sidepanel
https://bugs.kde.org/show_bug.cgi?id=487201 Bug ID: 487201 Summary: System Monitor crashes when opening details sidepanel Classification: Applications Product: plasma-systemmonitor Version: 6.0.4 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: ksysguard-b...@kde.org Reporter: benjamindai...@gmail.com CC: ahiems...@heimr.nl, plasma-b...@kde.org Target Milestone: --- [ben@pluto ~]$ plasma-systemmonitor qrc:/qt/qml/org/kde/ksysguard/page/EditablePage.qml?page=history.page:223:9: QML Loader: Binding loop detected for property "height" file:///usr/lib/qt6/qml/org/kde/kirigami/Dialog.qml:334:18: QML ScrollView: Binding loop detected for property "calculatedImplicitWidth" file:///usr/lib/qt6/qml/org/kde/kirigami/Dialog.qml:386:33: QML Binding: Binding loop detected for property "target" qrc:/qt/qml/org/kde/ksysguard/page/EditablePage.qml?page=overview.page:223:9: QML Loader: Binding loop detected for property "height" file:///usr/lib/qt6/qml/org/kde/kirigami/Dialog.qml:334:18: QML ScrollView: Binding loop detected for property "calculatedImplicitWidth" file:///usr/lib/qt6/qml/org/kde/kirigami/Dialog.qml:386:33: QML Binding: Binding loop detected for property "target" Segmentation fault (core dumped) Manjaro 24, Plasma 6. plasma-systemmonitor crashes when trying to open the details side panel via the Applications tab. -- You are receiving this mail because: You are watching all bug changes.
[plasma-systemmonitor] [Bug 487200] New: system monitor cannot show chrome cpu and mem usages
https://bugs.kde.org/show_bug.cgi?id=487200 Bug ID: 487200 Summary: system monitor cannot show chrome cpu and mem usages Classification: Applications Product: plasma-systemmonitor Version: 6.0.4 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: ksysguard-b...@kde.org Reporter: rosswzy...@outlook.com CC: ahiems...@heimr.nl, plasma-b...@kde.org Target Milestone: --- *** system monitor cannot show chrome cpu and mem usages *** SUMMARY system monitor cannot show chrome cpu and mem usages STEPS TO REPRODUCE 1. install chrome from official wensite 2. open chrome 3. open system monitor OBSERVED RESULT system monitor cannot show chrome cpu and mem usages EXPECTED RESULT system monitor can show chrome cpu and mem usages SOFTWARE/OS VERSIONS Operating System: Fedora Linux 40 KDE Plasma Version: 6.0.4 KDE Frameworks Version: 6.2.0 Qt Version: 6.7.0 Kernel Version: 6.8.9-300.fc40.x86_64 (64-bit) Graphics Platform: Wayland Processors: 16 × AMD Ryzen 7 7735HS with Radeon Graphics Memory: 27.1 GiB of RAM Graphics Processor: AMD Radeon Graphics Manufacturer: LENOVO Product Name: 83AS System Version: XiaoXinPro 16 ARP8 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kdiff3] [Bug 486909] KDiff3 as git mergetool does not jump to first conflict position at startup
https://bugs.kde.org/show_bug.cgi?id=486909 michael changed: What|Removed |Added Status|REPORTED|ASSIGNED Ever confirmed|0 |1 --- Comment #1 from michael --- This will be fixed in the next release thanks. -- You are receiving this mail because: You are watching all bug changes.
[amarok] [Bug 487199] New: to be able to resize the central window where is showed lyrics, current track, etc... [suggestion]
https://bugs.kde.org/show_bug.cgi?id=487199 Bug ID: 487199 Summary: to be able to resize the central window where is showed lyrics, current track, etc... [suggestion] Classification: Applications Product: amarok Version: 3.0.0 Platform: openSUSE OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: amarok-bugs-d...@kde.org Reporter: victor...@opensuse.org Target Milestone: kf5 SUMMARY Suggestion to add a feature to be able to resize the central window where is showed the current track, lyrics, Wikipedia, etc... Example, if I have set current track and lyrics, and want to make smaller the current track section than lyrics section, can't resize horizontally the sections. SOFTWARE/OS VERSIONS Operating System: openSUSE Tumbleweed 20240516 KDE Plasma Version: 6.0.4 KDE Frameworks Version: 6.2.0 Qt Version: 6.7.0 Kernel Version: 6.8.9-1-default (64-bit) Graphics Platform: X11 ADDITIONAL INFORMATION (please excuse me if a bug report is not the better place for suggestions and point me to the right place. And thanks for your work) -- You are receiving this mail because: You are watching all bug changes.
[Craft] [Bug 486905] Qt6 Webengine crash - required icudtl.dat is missing from image
https://bugs.kde.org/show_bug.cgi?id=486905 Thomas Friedrichsmeier changed: What|Removed |Added Resolution|--- |FIXED Status|REPORTED|RESOLVED Latest Commit||a7b43b7a4c54c487f86ca6b0725 ||d7979f62a51d9 -- You are receiving this mail because: You are watching all bug changes.
[KBibTeX] [Bug 484418] Support for searching and adding book citations (e.g. from Google Books, WorldCat)
https://bugs.kde.org/show_bug.cgi?id=484418 Thomas Fischer changed: What|Removed |Added Latest Commit|ffe0fb736ac6a377b772bc6f5a7 |37858b41ce6a19158586546d5ca |b7edb0e004b18 |15998dc4124b1 -- You are receiving this mail because: You are watching all bug changes.
[kio-admin] [Bug 481417] kio-admin doesn't prompt for "Open as Administrator" for folders owned by other users
https://bugs.kde.org/show_bug.cgi?id=481417 Antti Savolainen changed: What|Removed |Added Resolution|--- |FIXED Status|REPORTED|RESOLVED --- Comment #1 from Antti Savolainen --- Fixed by https://invent.kde.org/system/dolphin/-/merge_requests/487#note_946578 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 487198] REGRESSION - Complete disaster, computer unusable after update to 6.0
https://bugs.kde.org/show_bug.cgi?id=487198 --- Comment #1 from php4...@gmail.com --- After several minutes, without doing anything, the icons in the Task manager somehow finally appeared and seem to work, and the launcher also seems to work normally. Also the shortcut for taking screenshots, and Alt+Tab, have started working. The desktop is still black, though. -- You are receiving this mail because: You are watching all bug changes.
[Marknote] [Bug 487185] (Feature Request) Menubar on desktop
https://bugs.kde.org/show_bug.cgi?id=487185 --- Comment #2 from Daniel --- Sounds great! I considered waiting, but since it was mentioned in the changelog for the latest release I thought I might as well mention it. :) Thanks for all your hard work on this and other good apps! -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 487198] New: REGRESSION - Complete disaster, computer unusable after update to 6.0
https://bugs.kde.org/show_bug.cgi?id=487198 Bug ID: 487198 Summary: REGRESSION - Complete disaster, computer unusable after update to 6.0 Classification: Plasma Product: plasmashell Version: 6.0.4 Platform: Manjaro OS: Linux Status: REPORTED Severity: critical Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: php4...@gmail.com CC: k...@davidedmundson.co.uk Target Milestone: 1.0 Created attachment 169600 --> https://bugs.kde.org/attachment.cgi?id=169600=edit photo of the screen *** If you're not sure this is actually a bug, instead post about it at https://discuss.kde.org If you're reporting a crash, attach a backtrace with debug symbols; see https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** SUMMARY I have Manjaro Linux with KDE. I used to have KDE 5.x on X11 until now. I ran the system updates widget and selected all available updates to install, as I normally do every once in a while, and apparently KDE was upgraded to 6, without any special warning. When the upgrades got installed, I got some errors when upgrading a package called "krunner5" which I have no idea what it is. I tried re-running the update but it would keep failing. Apparently the package that were left to be installed/upgraded were: krunner5, Google Chrome and visual-studio-code-bin. After this I rebooted. I got an unfamiliar login screen, where there was a selector on the top-left between "KDE (X11)" and "KDE (Wayland)". I selected Wayland. I got prompted to choose select a multi-screen configuration, as I was doing all this with the laptop lid closed and with the external display connected (which is how I always use my computer), so I chose "switch to external monitor". And now my screen looks like this: see the attached PHOTO. Yes a PHOTO because the keyboard shortcut to take screenshots no longer works. All the icons in the task manager are broken and none of them work. Even the launcher doesn't work: I type "Chrome" in it and it doesn't find Google Chrome. I had to launch Chrome from a Terminal (which I ran by using Ctrl+Alt+T which fortunately worked). As you can see the desktop is black: not only there is no background image, but also none of the files and shortcuts. The shortcut to take screenshots doesn't work. It seems that I can run all the applications that I usually use by launching them from a terminal assuming I know the name or path of the executable, but that is not always the case. STEPS TO REPRODUCE 1. install available updates through Pamac OBSERVED RESULT utter and complete chaos EXPECTED RESULT SOFTWARE/OS VERSIONS Operating System: Manjaro Linux KDE Plasma Version: 6.0.4 KDE Frameworks Version: 6.1.0 Qt Version: 6.7.0 Kernel Version: 6.6.30-2-MANJARO (64-bit) Graphics Platform: X11 Processors: 12 × 12th Gen Intel® Core™ i7-1255U Memory: 15.3 GiB of RAM Graphics Processor: Mesa Intel® Graphics Manufacturer: ASUSTeK COMPUTER INC. Product Name: Vivobook_ASUSLaptop X1502ZA_F1502ZA System Version: 1.0 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kasts] [Bug 487173] Improvements to Kasts - add grouping for followed podcasts (maybe as tags, folders or playlists)
https://bugs.kde.org/show_bug.cgi?id=487173 b...@mogwai.be changed: What|Removed |Added Ever confirmed|0 |1 Status|REPORTED|CONFIRMED -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 456569] External monitor goes black when video player is fullscreen
https://bugs.kde.org/show_bug.cgi?id=456569 mensh...@murena.io changed: What|Removed |Added CC||mensh...@murena.io --- Comment #16 from mensh...@murena.io --- I am experiencing similar issues on Fedora 40, but the bug just appears randomly (sometimes on full screen entry and other times on full screen exit (the screen goes fully black in both cases). Firefox and VLC seem to trigger this bug on full screen exit with a high likelyhood, especially when compared to other programs like Dragon Player. I should also note that the bug tends to often times repeat: If the screen turns black it is more likely for it to turn black on the next full screen toggle than if it doesn't turn black. This applies especially well to VLC. Versions: Plasma 6.0.4, KWin 6.0.4, QT 6.7.0 -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 487165] didcover crashing when fetching updates steam deck oled
https://bugs.kde.org/show_bug.cgi?id=487165 testc2...@gmail.com changed: What|Removed |Added Platform|unspecified |SteamOS -- You are receiving this mail because: You are watching all bug changes.
