[plasmashell] [Bug 484366] Using Wayland changes panels and desktops to the wrong monitors
https://bugs.kde.org/show_bug.cgi?id=484366 --- Comment #5 from Damian C --- (In reply to Nate Graham from comment #4) > Great, let's call it fixed in Plasma 6.1 In fact I have not seen it come back, not even after switching back to Wayland after the recent nvidia driver upgrade to version 560. Thank you -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 486362] Discover crashes when opening
https://bugs.kde.org/show_bug.cgi?id=486362 Damian Cade changed: What|Removed |Added CC||damiankc...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 486362] Discover crashes when opening
https://bugs.kde.org/show_bug.cgi?id=486362 --- Comment #3 from Damian Cade --- Created attachment 170440 --> https://bugs.kde.org/attachment.cgi?id=170440&action=edit New crash information added by DrKonqi plasma-discover (5.27.5) using Qt 5.15.8 I opened discover without an internet connection. I did this after opening and closing dolphin, but didn't have any other processes running. -- Backtrace (Reduced): #5 0x7f08d81e63b2 in ResultsStream::resourcesFound(QVector const&) () from /usr/lib/x86_64-linux-gnu/plasma-discover/libDiscoverCommon.so [...] #8 0x7f08d60dd6f0 in QObject::event(QEvent*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #9 0x7f08d7b62fae in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #10 0x7f08d60b16f8 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #11 0x7f08d60b4681 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 482409] Unclear how to add printer / button disabled
https://bugs.kde.org/show_bug.cgi?id=482409 Damian C changed: What|Removed |Added CC||dcalv...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 485331] New: plasmashell crashed when opening akonadiconsole
https://bugs.kde.org/show_bug.cgi?id=485331
Bug ID: 485331
Summary: plasmashell crashed when opening akonadiconsole
Classification: Plasma
Product: plasmashell
Version: 6.0.3
Platform: Arch Linux
OS: Linux
Status: REPORTED
Keywords: drkonqi
Severity: crash
Priority: NOR
Component: generic-crash
Assignee: plasma-b...@kde.org
Reporter: dcalv...@gmail.com
Target Milestone: 1.0
Application: plasmashell (6.0.3)
Qt Version: 6.6.3
Frameworks Version: 6.0.0
Operating System: Linux 6.8.4-zen1-1-zen x86_64
Windowing System: Wayland
Distribution: "Arch Linux"
DrKonqi: 6.0.3 [CoredumpBackend]
-- Information about the crash:
Upon opening akonadiconsole for the purposes of troubleshooting an issue
(https://discuss.kde.org/t/kontact-freezes-upon-starting/13789/8)
akonadiconsole froze and plasmashell crashed and restarted
The reporter is unsure if this crash is reproducible.
-- Backtrace (Reduced):
#5 0x721c16ec5ae6 in
KAStatsFavoritesModel::Private::Private(KAStatsFavoritesModel*, QString
const&)::{lambda()#1}::operator()() const (__closure=0x57257b85ad20) at
/usr/src/debug/plasma-workspace/plasma-workspace-6.0.3/applets/kicker/plugin/kastatsfavoritesmodel.cpp:189
#6 QtPrivate::FunctorCall, QtPrivate::List<>, void,
KAStatsFavoritesModel::Private::Private(KAStatsFavoritesModel*, QString
const&)::{lambda()#1}>::call(KAStatsFavoritesModel::Private::Private(KAStatsFavoritesModel*,
QString const&)::{lambda()#1}&, void**) (arg=, f=...) at
/usr/include/qt6/QtCore/qobjectdefs_impl.h:137
#7
QtPrivate::Functor::call,
void>(KAStatsFavoritesModel::Private::Private(KAStatsFavoritesModel*, QString
const&)::{lambda()#1}&, void*, void**) (arg=, f=...) at
/usr/include/qt6/QtCore/qobjectdefs_impl.h:339
#8
QtPrivate::QCallableObject, void>::impl(int,
QtPrivate::QSlotObjectBase*, QObject*, void**, bool*) (which=,
this_=0x57257b85ad10, r=, a=, ret=) at /usr/include/qt6/QtCore/qobjectdefs_impl.h:522
#9 0x721c38f91599 in QtPrivate::QSlotObjectBase::call (a=0x7ffd53babb78,
r=0x57257bd41500, this=0x57257b85ad10, this=, r=,
a=) at
/usr/src/debug/qt6-base/qtbase-everywhere-src-6.6.3/src/corelib/kernel/qobjectdefs_impl.h:433
Reported using DrKonqi
--
You are receiving this mail because:
You are watching all bug changes.
[plasmashell] [Bug 485331] plasmashell crashed when opening akonadiconsole
https://bugs.kde.org/show_bug.cgi?id=485331 --- Comment #1 from Damian C --- Created attachment 168347 --> https://bugs.kde.org/attachment.cgi?id=168347&action=edit New crash information added by DrKonqi DrKonqi auto-attaching complete backtrace. -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 484775] Kontact Does Not Start After Upgrade to Plasma 6.0.3
https://bugs.kde.org/show_bug.cgi?id=484775 Damian C changed: What|Removed |Added CC||dcalv...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 484430] Discover crashes when searching for something
https://bugs.kde.org/show_bug.cgi?id=484430 Damian C changed: What|Removed |Added CC||dcalv...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 484430] New: Discover crashes when searching for something
https://bugs.kde.org/show_bug.cgi?id=484430 Bug ID: 484430 Summary: Discover crashes when searching for something Classification: Applications Product: Discover Version: 6.0.2 Platform: Arch Linux OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: discover Assignee: plasma-b...@kde.org Reporter: dcalv...@gmail.com CC: aleix...@kde.org Target Milestone: --- Created attachment 167722 --> https://bugs.kde.org/attachment.cgi?id=167722&action=edit gdb plasma-discover SUMMARY Discover crashes when attempting to search for something, or trying to explore categories. STEPS TO REPRODUCE 1. Open Discover 2. Search for something 3. Crashes OBSERVED RESULT App crashes EXPECTED RESULT Returns the search, or shows the clicked category. SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 6.0.2 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.2 Kernel Version: 6.8.1-zen1-1-zen (64-bit) Graphics Platform: Wayland Processors: 12 × Intel® Core™ i7-8700K CPU @ 3.70GHz Memory: 15.5 GiB of RAM Graphics Processor: NVIDIA GeForce GTX 1070/PCIe/SSE2 ADDITIONAL INFORMATION attached gdb -- You are receiving this mail because: You are watching all bug changes.
[krfb] [Bug 466276] Cursor is not where it should be while using UI Scailing
https://bugs.kde.org/show_bug.cgi?id=466276 --- Comment #3 from Damian Anlauf --- Just wanted to mention that this issue is still present in Krfb 24.02.1, which makes it impossible to hit targets (e.g., buttons) with the cursor. Some additional information: The mouse cursor position on client and Krfb server matches correctly while the cursor is in the top left corner of the screen (origin point; 0,0) but drifts away the further the cursor moves from there. On 200% scaling, it is as if the client recognized the screen as having 4x as many pixels (e.g., 1920x1080 -> 3840x2160) with the same origin point of 0,0. E.g., if the cursor is, from the perspective of the client, positioned in the center of the screen, in actuality it is positioned in the absolute bottom right corner. FWIW, I have encountered the exact same issue with the nightly version of the Rustdesk Flatpak on Plasma, which also utilizes the "org.freedesktop.portal.RemoteDesktop" portal, so the issue might lie somewhere upstream. Operating System: Arch Linux KDE Plasma Version: 6.0.2 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.2 Kernel Version: 6.8.1-zen1-1-zen (64-bit) Graphics Platform: Wayland Processors: 8 × Intel® Core™ i7-4790K CPU @ 4.00GHz Memory: 30.3 GiB of RAM Graphics Processor: NVIDIA GeForce GTX 980/PCIe/SSE2 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 484366] Using Wayland changes panels and desktops to the wrong monitors
https://bugs.kde.org/show_bug.cgi?id=484366 Damian C changed: What|Removed |Added CC||dcalv...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 484366] New: Using Wayland changes panels and desktops to the wrong monitors
https://bugs.kde.org/show_bug.cgi?id=484366 Bug ID: 484366 Summary: Using Wayland changes panels and desktops to the wrong monitors Classification: Plasma Product: plasmashell Version: 6.0.1 Platform: Arch Linux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Panel Assignee: plasma-b...@kde.org Reporter: dcalv...@gmail.com CC: niccolo.venera...@gmail.com Target Milestone: 1.0 SUMMARY When logging in selecting Wayland, panels and desktops are attached to the wrong monitors/displays. STEPS TO REPRODUCE 1. Boot ArchLinux, select Wayland. 2. Observe the panels and desktops disrupted. OBSERVED RESULT Desktops and panels are attached to the wrong monitor. EXPECTED RESULT Panels and desktops remain attached to the monitors I have set up for them regardless of desktop compositor. As it used to be prior to the Plasma 6 upgrade. SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 6.0.2 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.2 Kernel Version: 6.8.1-zen1-1-zen (64-bit) Graphics Platform: X11 Processors: 12 × Intel® Core™ i7-8700K CPU @ 3.70GHz Memory: 15.5 GiB of RAM Graphics Processor: NVIDIA GeForce GTX 1070/PCIe/SSE2 ADDITIONAL INFORMATION Using 3 monitors. This started happening after upgrading to Plasma 6. Something similar to this had happened in the past but it had been solved, it was possible to change between x11 and Wayland while keeping the same desktops and panels on the right monitors. If I logoff Wayland and go back to X11 the panels and desktops are attached to the correct monitors. If I correct the panels and desktops for Wayland and attach them the way they should go, then going back to x11 will have the panels all wrong. -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 484364] Crash launching kontact
https://bugs.kde.org/show_bug.cgi?id=484364 Damian C changed: What|Removed |Added CC||dcalv...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 484364] New: Crash launching kontact
https://bugs.kde.org/show_bug.cgi?id=484364 Bug ID: 484364 Summary: Crash launching kontact Classification: Applications Product: kontact Version: 6.0.1 Platform: Arch Linux OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: dcalv...@gmail.com Target Milestone: --- Created attachment 167685 --> https://bugs.kde.org/attachment.cgi?id=167685&action=edit coredumpctl info for this crash SUMMARY When attempting to launch Kontact, it crashes. STEPS TO REPRODUCE 1. Boot Arch Linux with Plasma 6, select Wayland. 2. Attempt to launch kontact 3. Crash. OBSERVED RESULT Kontact crashes and dumps core. EXPECTED RESULT Open Kontact normally. SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 6.0.2 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.2 Kernel Version: 6.8.1-zen1-1-zen (64-bit) Graphics Platform: X11 Processors: 12 × Intel® Core™ i7-8700K CPU @ 3.70GHz Memory: 15.5 GiB of RAM Graphics Processor: NVIDIA GeForce GTX 1070/PCIe/SSE2 ADDITIONAL INFORMATION Only happens with Wayland, using X11 results in Kontact launching successfully. Attempting to launch Kmail instead of Kontact results in the same crash. Started happening only after upgrading to Plasma 6. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 483415] settings dialogs use light background in dark mode
https://bugs.kde.org/show_bug.cgi?id=483415 Damian Anlauf changed: What|Removed |Added CC||anlaufdam...@gmail.com --- Comment #4 from Damian Anlauf --- I had the same issue after the Plasma 6 update (KDEneon user edition). It was also caused by the `plasma-integration` package being stuck on version `5.19.5-0xneon+20.04+focal+build11`. But neither doing a `pkcon update` nor `apt update && apt full-upgrade` found any available updates. The cause for this were apt preferences defined under `/etc/apt/preferences.d`, specifically `99-plasma-integration` which pinned the package to version `5.1*`. This seems to be a remnant of an old version of neon, as I am using neon on this device since 2018 and have been upgrading neon from then without doing a fresh reinstallation. So if anyone has the same issue as I had, check your `/etc/apt/preferences.d` directory for remnants. For reference, a fresh, up-to-date neon install currently only contains the following files: `50-neon-ubuntu-release-upgrader 99-jammy-overrides 99-neon-base-files org-kde-neon-net-launchpad-ppa-mozillateam-pin`. Meanwhile, my current installation additionally contained: `99-neon-software-properties 99-plasma-integration 99-pulseaudio-qt`. -- You are receiving this mail because: You are watching all bug changes.
[krfb] [Bug 466276] Cursor is not where it should be while using UI Scailing
https://bugs.kde.org/show_bug.cgi?id=466276 Damian Anlauf changed: What|Removed |Added CC||anlaufdam...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[krfb] [Bug 482929] Krfb crashes with segmentation fault on Wayland when scaling is enabled
https://bugs.kde.org/show_bug.cgi?id=482929 --- Comment #8 from Damian Anlauf --- (In reply to Jordan Pryde from comment #7) > (Manually making this comment since I didn't have a bug tracker account > until now - I got an email that this failed) > Fixed by https://invent.kde.org/network/krfb/-/merge_requests/63 in master > > @bug_id = 482929 > @bug_status = RESOLVED > @resolution = FIXED > @cf_commitlink = > https://invent.kde.org/network/krfb/-/commit/ > 966ad6a1639732f882284ff6e708b0e37e624ca7 > > Git commit 966ad6a1639732f882284ff6e708b0e37e624ca7 by Jordan Pryde. > Committed on 12/03/2024 at 16:11. > Pushed by nicolasfella into branch 'release/24.02'. > > DMA-BUF size may not match size from handleRemoteDesktopStarted() > > QScreen::size() marshalled from xdg-desktop-portal-kde uses logical > scaled size but the DMA-BUF from pipewire is the physical pixel count. > We now check the DMA-BUF size each frame and resize the QImage buffer when > needed. > Related: bug 478057, bug 464547 > > M +1-0framebuffers/pipewire/pw_framebuffer.cpp > > https://invent.kde.org/network/krfb/-/commit/ > 966ad6a1639732f882284ff6e708b0e37e624ca7 Just compiled it. Can confirm. The bug is no more. Can't believe it only took a single line of code to fix this bug. Thank you very much! -- You are receiving this mail because: You are watching all bug changes.
[krfb] [Bug 482929] Krfb crashes with segmentation fault on Wayland when scaling is enabled
https://bugs.kde.org/show_bug.cgi?id=482929 --- Comment #5 from Damian Anlauf --- BACKTRACE: Krfb 23.08.5 @ Fedora 39 Thread 1 "krfb" received signal SIGSEGV, Segmentation fault. #0 __memcpy_sse2_unaligned_erms () at ../sysdeps/x86_64/multiarch/memmove-vec-unaligned-erms.S:671 #1 0x7fffd9e49bf7 in memcpy (__len=, __src=0x7fffc0574460, __dest=) at /usr/include/bits/string_fortified.h:29 #2 st_ReadPixels (ctx=ctx@entry=0x55a1ca00, x=, y=0, width=, height=731, format=format@entry=6408, type=5121, pack=0x7fffc310, pixels=) at ../src/mesa/state_tracker/st_cb_readpixels.c:555 #3 0x7fffd9df9f9e in read_pixels (no_error=false, pixels=0x7fffc0600010, bufSize=2147483647, type=5121, format=6408, height=, width=, y=, x=) at ../src/mesa/main/readpix.c:1199 #4 _mesa_ReadnPixelsARB (x=, y=, width=, height=, format=6408, type=5121, bufSize=2147483647, pixels=0x7fffc0600010) at ../src/mesa/main/readpix.c:1216 #5 0x7fffd9dfa3a5 in _mesa_ReadPixels (x=, y=, width=, height=, format=, type=, pixels=0x7fffc0600010) at ../src/mesa/main/readpix.c:1231 #6 0x7fffe0e1ec17 in DmaBufHandler::downloadFrame (this=this@entry=0x55684920, qimage=..., frame=...) at /usr/include/c++/13/optional:484 #7 0x7fffe0e7f87b in PWFrameBuffer::Private::handleFrame (frame=..., this=0x556848b0) at /usr/src/debug/krfb-23.08.5-1.fc39.x86_64/framebuffers/pipewire/pw_framebuffer.cpp:356 #8 operator() (frame=..., __closure=) at /usr/src/debug/krfb-23.08.5-1.fc39.x86_64/framebuffers/pipewire/pw_framebuffer.cpp:115 #9 QtPrivate::FunctorCall, QtPrivate::List, void, PWFrameBuffer::Private::Private(PWFrameBuffer*):: >::call (arg=, f=...) at /usr/include/qt5/QtCore/qobjectdefs_impl.h:146 #10 QtPrivate::Functor, 1>::call, void> (arg=, f=...) at /usr/include/qt5/QtCore/qobjectdefs_impl.h:256 #11 QtPrivate::QFunctorSlotObject, 1, QtPrivate::List, void>::impl(int, QtPrivate::QSlotObjectBase *, QObject *, void **, bool *) (which=, this_=, r=, a=, ret=) at /usr/include/qt5/QtCore/qobjectdefs_impl.h:443 #12 0x764e9151 in QtPrivate::QSlotObjectBase::call (a=0x7fffc5f0, r=, this=0x556dc4f0) at ../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398 #13 doActivate (sender=0x556dc9d0, signal_index=7, argv=0x7fffc5f0) at kernel/qobject.cpp:3925 #14 0x764e4077 in QMetaObject::activate (sender=sender@entry=0x556dc9d0, m=m@entry=0x7fffe05e04c0 , local_signal_index=local_signal_index@entry=4, argv=argv@entry=0x7fffc5f0) at kernel/qobject.cpp:3985 #15 0x7fffe05ce02c in PipeWireSourceStream::frameReceived (this=this@entry=0x556dc9d0, _t1=...) at /usr/src/debug/kpipewire-5.27.10-1.fc39.x86_64/redhat-linux-build/src/KPipeWire_autogen/EWIEGA46WW/moc_pipewiresourcestream.cpp:219 #16 0x7fffe05d9e5f in PipeWireSourceStream::handleFrame (this=this@entry=0x556dc9d0, buffer=buffer@entry=0x559b6a38) at /usr/src/debug/kpipewire-5.27.10-1.fc39.x86_64/src/pipewiresourcestream.cpp:533 #17 0x7fffe05da79f in PipeWireSourceStream::process (this=0x556dc9d0) at /usr/src/debug/kpipewire-5.27.10-1.fc39.x86_64/src/pipewiresourcestream.cpp:551 #18 0x7fffe0292708 in do_call_process (loop=, async=, seq=, data=, size=, user_data=0x559b6600) at ../src/pipewire/stream.c:453 #19 do_call_process (loop=, async=, seq=, data=, size=, user_data=0x559b6600) at ../src/pipewire/stream.c:446 #20 0x7fffe05aa2da in flush_items (impl=0x559913b8) at ../spa/plugins/support/loop.c:180 #21 0x7fffe05a93d7 in source_event_func (source=0x559e58d0) at ../spa/plugins/support/loop.c:663 #22 0x7fffe05aaf76 in loop_iterate (object=0x559913b8, timeout=) at ../spa/plugins/support/loop.c:496 #23 0x7fffe05d0029 in operator() (__closure=) at /usr/src/debug/kpipewire-5.27.10-1.fc39.x86_64/src/pipewirecore.cpp:78 #24 QtPrivate::FunctorCall, QtPrivate::List<>, void, PipeWireCore::init(int):: >::call (arg=, f=...) at /usr/include/qt5/QtCore/qobjectdefs_impl.h:146 #25 QtPrivate::Functor, 0>::call, void> (arg=, f=...) at /usr/include/qt5/QtCore/qobjectdefs_impl.h:256 #26 QtPrivate::QFunctorSlotObject, 0, QtPrivate::List<>, void>::impl(int, QtPrivate::QSlotObjectBase *, QObject *, void **, bool *) (which=, this_=, r=, a=, ret=) at /usr/include/qt5/QtCore/qobjectdefs_impl.h:443 #27 0x764e9151 in QtPrivate::QSlotObjectBase::call (a=0x7fffccd0, r=, this=0x556e0820) at ../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398 #28 doActivate (sender=0x559e5e20, signal_index=3, argv=0x7fffccd0) at kernel/qobject.cpp:3925 #29 0x764e4077 in QMetaObject::activate (sender=sender@entry=0x559e5e20, m=m@entry=0x76769420 , local_signal_index=local_signal_index@entry=0, argv=argv@entry=0x7fffccd0) at kernel/qobject.cpp:3985 #30 0x764ebb5d in QSocketNotifier::activated (this=this@entry=0x559e5e20, _t1=..., _t2=, _t3=...) at .moc/moc_qsocketnotifier.cpp:178 #31 0x764ec3cb in
[krfb] [Bug 482929] Krfb crashes with segmentation fault on Wayland when scaling is enabled
https://bugs.kde.org/show_bug.cgi?id=482929 --- Comment #4 from Damian Anlauf --- BACKTRACE: Krfb 24.02.0 @ Arch Thread 1 "krfb" received signal SIGSEGV, Segmentation fault. #0 0x7fffe2cf3804 in ??? () at /usr/lib/libnvidia-eglcore.so.550.54.14 #1 0x7fffe2cf6991 in ??? () at /usr/lib/libnvidia-eglcore.so.550.54.14 #2 0x7fffe2cf8126 in ??? () at /usr/lib/libnvidia-eglcore.so.550.54.14 #3 0x7fffe2d0f3c1 in ??? () at /usr/lib/libnvidia-eglcore.so.550.54.14 #4 0x7fffe2be3353 in ??? () at /usr/lib/libnvidia-eglcore.so.550.54.14 #5 0x7fffe2cd894e in ??? () at /usr/lib/libnvidia-eglcore.so.550.54.14 #6 0x7fffe2c8b9e3 in ??? () at /usr/lib/libnvidia-eglcore.so.550.54.14 #7 0x7fffe28bf64a in ??? () at /usr/lib/libnvidia-eglcore.so.550.54.14 #8 0x7fffe28bfec2 in ??? () at /usr/lib/libnvidia-eglcore.so.550.54.14 #9 0x7fffeb6411ac in DmaBufHandler::downloadFrame (this=this@entry=0x5577f678, qimage=..., frame=...) at /usr/include/c++/13.2.1/optional:484 #10 0x7fffeb35963f in PWFrameBuffer::Private::handleFrame (frame=..., this=0x5577f600) at /usr/src/debug/krfb/krfb-24.02.0/framebuffers/pipewire/pw_framebuffer.cpp:368 #11 operator() (frame=..., __closure=) at /usr/src/debug/krfb/krfb-24.02.0/framebuffers/pipewire/pw_framebuffer.cpp:116 #12 QtPrivate::FunctorCall, QtPrivate::List, void, PWFrameBuffer::Private::Private(PWFrameBuffer*):: >::call (arg=, f=) at /usr/include/qt6/QtCore/qobjectdefs_impl.h:137 #13 QtPrivate::Functor, 1>::call, void> (arg=, f=) at /usr/include/qt6/QtCore/qobjectdefs_impl.h:339 #14 QtPrivate::QCallableObject, QtPrivate::List, void>::impl(int, QtPrivate::QSlotObjectBase *, QObject *, void **, bool *) (which=, this_=, r=, a=, ret=) at /usr/include/qt6/QtCore/qobjectdefs_impl.h:522 #15 0x75f90ca9 in QtPrivate::QSlotObjectBase::call (a=0x7fffc400, r=0x556f9990, this=0x556f9b50, this=, r=, a=) at /usr/src/debug/qt6-base/qtbase-everywhere-src-6.6.2/src/corelib/kernel/qobjectdefs_impl.h:433 #16 doActivate (sender=0x556f9a50, signal_index=7, argv=0x7fffc400) at /usr/src/debug/qt6-base/qtbase-everywhere-src-6.6.2/src/corelib/kernel/qobject.cpp:4039 #17 0x7fffead58e5a in PipeWireSourceStream::frameReceived (this=this@entry=0x556f9a50, _t1=...) at /usr/src/debug/kpipewire/build/src/KPipeWire_autogen/include/moc_pipewiresourcestream.cpp:287 #18 0x7fffead5d752 in PipeWireSourceStream::handleFrame (this=this@entry=0x556f9a50, buffer=buffer@entry=0x55b87208) at /usr/src/debug/kpipewire/kpipewire-6.0.1.1/src/pipewiresourcestream.cpp:560 #19 0x7fffead5e27d in PipeWireSourceStream::process (this=0x556f9a50) at /usr/src/debug/kpipewire/kpipewire-6.0.1.1/src/pipewiresourcestream.cpp:578 #20 0x7fffe939e2a8 in do_call_process (loop=, async=, seq=, data=, size=, user_data=0x55b86dd0) at ../pipewire/src/pipewire/stream.c:453 #21 do_call_process (loop=, async=, seq=, data=, size=, user_data=0x55b86dd0) at ../pipewire/src/pipewire/stream.c:446 #22 0x7fffe975f988 in flush_items (impl=0x55b639b8) at ../pipewire/spa/plugins/support/loop.c:180 #23 0x7fffe975ecb9 in source_event_func (source=0x55b13bb0) at ../pipewire/spa/plugins/support/loop.c:663 #24 0x7fffe9760646 in loop_iterate (object=0x55b639b8, timeout=) at ../pipewire/spa/plugins/support/loop.c:496 #25 0x7fffead4f271 in operator() (__closure=) at /usr/src/debug/kpipewire/kpipewire-6.0.1.1/src/pipewirecore.cpp:90 #26 QtPrivate::FunctorCall, QtPrivate::List<>, void, PipeWireCore::init(int):: >::call (arg=, f=) at /usr/include/qt6/QtCore/qobjectdefs_impl.h:137 #27 QtPrivate::Functor, 0>::call, void> (arg=, f=) at /usr/include/qt6/QtCore/qobjectdefs_impl.h:339 #28 QtPrivate::QCallableObject, QtPrivate::List<>, void>::impl(int, QtPrivate::QSlotObjectBase *, QObject *, void **, bool *) (which=, this_=, r=, a=, ret=) at /usr/include/qt6/QtCore/qobjectdefs_impl.h:522 #29 0x75f90ca9 in QtPrivate::QSlotObjectBase::call (a=0x7fffcb10, r=0x5598cf10, this=0x559b41e0, this=, r=, a=) at /usr/src/debug/qt6-base/qtbase-everywhere-src-6.6.2/src/corelib/kernel/qobjectdefs_impl.h:433 #30 doActivate (sender=0x55979080, signal_index=3, argv=0x7fffcb10) at /usr/src/debug/qt6-base/qtbase-everywhere-src-6.6.2/src/corelib/kernel/qobject.cpp:4039 #31 0x75f98530 in QSocketNotifier::activated (_t3=..., _t2=, _t1=..., this=0x55979080) at /usr/src/debug/qt6-base/build/src/corelib/Core_autogen/include/moc_qsocketnotifier.cpp:231 #32 QSocketNotifier::event (this=0x55979080, e=) at /usr/src/debug/qt6-base/qtbase-everywhere-src-6.6.2/src/corelib/kernel/qsocketnotifier.cpp:326 #33 0x76ef438b in QApplicationPrivate::notify_helper (this=, receiver=0x55979080, e=0x7fffcc10) at /usr/src/debug/qt6-base/qtbase-everywhere-src-6.6.2/src/widgets/kernel/qapplication.cpp:3296 #34 0x75f39818 in QCoreApplication::notifyInternal2 (receiver=0x5
[krfb] [Bug 482929] Krfb crashes with segmentation fault on Wayland when scaling is enabled
https://bugs.kde.org/show_bug.cgi?id=482929 --- Comment #3 from Damian Anlauf --- Created attachment 166746 --> https://bugs.kde.org/attachment.cgi?id=166746&action=edit GDB full log - Fedora 39 -- You are receiving this mail because: You are watching all bug changes.
[krfb] [Bug 482929] Krfb crashes with segmentation fault on Wayland when scaling is enabled
https://bugs.kde.org/show_bug.cgi?id=482929 --- Comment #2 from Damian Anlauf --- Created attachment 166745 --> https://bugs.kde.org/attachment.cgi?id=166745&action=edit GDB full log - Arch -- You are receiving this mail because: You are watching all bug changes.
[krfb] [Bug 482929] Krfb crashes with segmentation fault on Wayland when scaling is enabled
https://bugs.kde.org/show_bug.cgi?id=482929 --- Comment #1 from Damian Anlauf --- Created attachment 166744 --> https://bugs.kde.org/attachment.cgi?id=166744&action=edit GDB backtrace only - Fedora 39 -- You are receiving this mail because: You are watching all bug changes.
[krfb] [Bug 482929] New: Krfb crashes with segmentation fault on Wayland when scaling is enabled
https://bugs.kde.org/show_bug.cgi?id=482929 Bug ID: 482929 Summary: Krfb crashes with segmentation fault on Wayland when scaling is enabled Classification: Applications Product: krfb Version: 24.02.0 Platform: Arch Linux OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: general Assignee: grundleb...@googlemail.com Reporter: anlaufdam...@gmail.com Target Milestone: --- Created attachment 166743 --> https://bugs.kde.org/attachment.cgi?id=166743&action=edit GDB backtrace only - Arch SUMMARY Krfb crashes with segmentation fault on Wayland when scaling is enabled. STEPS TO REPRODUCE 1. Start Plasma in a Wayland session 2. Enable scaling in System Settings with only a single monitor connected 3. Run Krfb and confirm the remote control request dialog OBSERVED RESULT Krfb terminates with a segmentation fault. EXPECTED RESULT Krfb starts sharing the desktop. SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 6.0.1 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.2 Kernel Version: 6.7.9-zen1-1-zen (64-bit) Graphics Platform: Wayland Processors: 8 × Intel® Core™ i7-4790K CPU @ 4.00GHz Memory: 30.3 GiB of RAM Graphics Processor: NVIDIA GeForce GTX 980/PCIe/SSE2 Krfb Version: 24.02.0 Operating System: Fedora Linux 39 KDE Plasma Version: 5.27.10 KDE Frameworks Version: 5.115.0 Qt Version: 5.15.12 Kernel Version: 6.7.7-200.fc39.x86_64 (64-bit) Graphics Platform: Wayland Processors: 4 × Intel® Core™ i5-3230M CPU @ 2.60GHz Memory: 11.6 GiB of RAM Graphics Processor: Mesa Intel® HD Graphics 4000 Krfb Version: 23.08.5 ADDITIONAL INFORMATION I was able to reproduce this issue on Arch running Krfb 24.02.0 and Plasma 6.0.1, as well as Fedora 39 running Krfb 23.08.5 and Plasma 5.27.10. This issue does not seem to happen, when another monitor is connected which has scaling disabled (100%) or when running under X11. -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 479734] Media keys [fn] work on KDE x11 session, not on KDE Wayland (but do work on Gnome Wayland)
https://bugs.kde.org/show_bug.cgi?id=479734 --- Comment #2 from Damian --- (In reply to Nate Graham from comment #1) > I suspect your method of installation has caused this problem. Those keys > are handled by different parts of the system that don't all come > pre-packaged. The volume keys for example are handled by software provided > in the "plasma-pa" package. So if that's not installed, install it, reboot, "plasma-pa" is already installed > and try again. If that doesn't work, can you try again in a new user > account, or in a new installation of Fedora KDE on its own? A new user account indeed is working -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 348082] monitor is randomly powered back on
https://bugs.kde.org/show_bug.cgi?id=348082 Michael Damian changed: What|Removed |Added CC||micheal.damian960@flounderf ||antasy.com --- Comment #31 from Michael Damian --- Same issue here with dual displays. Operating System: EndeavourOS KDE Plasma Version: 5.27.10 KDE Frameworks Version: 5.115.0 Qt Version: 5.15.12 Kernel Version: 6.7.6-arch1-1 (64-bit) Graphics Platform: Wayland Processors: 20 × 12th Gen Intel® Core™ i7-12700K Memory: 31.1 GiB of RAM Graphics Processor: Mesa Intel® UHD Graphics 770 Manufacturer: ASUS -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 457726] kscreen_backend_launcher block entering Screen Energy saving
https://bugs.kde.org/show_bug.cgi?id=457726 Michael Damian changed: What|Removed |Added Version|5.27.8 |5.27.10 Platform|Debian unstable |Arch Linux -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 457726] kscreen_backend_launcher block entering Screen Energy saving
https://bugs.kde.org/show_bug.cgi?id=457726 Michael Damian changed: What|Removed |Added CC||micheal.damian960@flounderf ||antasy.com --- Comment #17 from Michael Damian --- Hello, I am experiencing the same issue on Archlinux. My Monitors are connected via, HDMI and Displayport. When the Timeout is reached, the monitors begin to turn off, then the 1st one enters Power Saving Mode and is effectively off. The 2nd monitor however does not reach this state and then a few seconds later, both monitors turn back on. It happens even if Dim screen is enabled or not. Operating System: EndeavourOS KDE Plasma Version: 5.27.10 KDE Frameworks Version: 5.115.0 Qt Version: 5.15.12 Kernel Version: 6.7.6-arch1-1 (64-bit) Graphics Platform: Wayland Processors: 20 × 12th Gen Intel® Core™ i7-12700K Memory: 31.1 GiB of RAM Graphics Processor: Mesa Intel® UHD Graphics 770 Manufacturer: ASUS -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 480401] New: Quickly switching through images in Gwenview can cause it to crash.
https://bugs.kde.org/show_bug.cgi?id=480401
Bug ID: 480401
Summary: Quickly switching through images in Gwenview can cause
it to crash.
Classification: Applications
Product: gwenview
Version: 23.08.4
Platform: Arch Linux
OS: Linux
Status: REPORTED
Keywords: drkonqi
Severity: crash
Priority: NOR
Component: general
Assignee: gwenview-bugs-n...@kde.org
Reporter: damian.hoes...@gmail.com
Target Milestone: ---
Application: gwenview (23.08.4)
Qt Version: 5.15.12
Frameworks Version: 5.114.0
Operating System: Linux 6.7.1-zen1-1-zen x86_64
Windowing System: X11
Distribution: "Arch Linux"
DrKonqi: 5.27.10 [KCrashBackend]
-- Information about the crash:
Images were pretty standard JPEG images, no insane resolution. On a Btrfs RAID5
array connected over USB. There was high load on the volume when the issue
occured, and I could not reproduce the issue a couple minutes later.
The crash can be reproduced sometimes.
-- Backtrace:
Application: Gwenview (gwenview), signal: Segmentation fault
Content of s_kcrashErrorMessage: std::unique_ptr = {get() = 0x0}
[KCrash Handler]
#6 0x7bf48751a8df in () at /usr/lib/libjxl.so.0.9
#7 0x7bf4875e61f0 in JxlDecoderGetColorAsEncodedProfile () at
/usr/lib/libjxl.so.0.9
#8 0x7bf4982826d9 in QJpegXLHandler::countALLFrames()
(this=0x7bf448013b20) at
/usr/src/debug/kimageformats5/kimageformats-5.114.0/src/imageformats/jxl.cpp:270
#9 0x7bf498282de1 in QJpegXLHandler::ensureALLCounted() const
(this=) at
/usr/src/debug/kimageformats5/kimageformats-5.114.0/src/imageformats/jxl.cpp:104
#10 0x7bf4982833fd in QJpegXLHandler::read(QImage*) (this=0x7bf448013b20,
image=0x7bf4759ffa50) at
/usr/src/debug/kimageformats5/kimageformats-5.114.0/src/imageformats/jxl.cpp:436
#11 0x7bf4a81114ee in QImageReader::read(QImage*)
(this=this@entry=0x7bf4759ffae0, image=image@entry=0x7bf4759ffa50) at
image/qimagereader.cpp:1290
#12 0x7bf4a811391a in QImageReader::read() (this=this@entry=0x7bf4759ffae0)
at image/qimagereader.cpp:1231
#13 0x7bf4a9b5b7f1 in Gwenview::LoadingDocumentImplPrivate::loadMetaInfo()
(this=0x5fe38abf75f0) at
/usr/src/debug/gwenview/gwenview-23.08.4/lib/document/loadingdocumentimpl.cpp:295
#14 0x7bf4a9b54c04 in QtConcurrent::StoredMemberFunctionPointerCall0::runFunctor() (this=0x5fe38aa1d5b0) at
/usr/include/qt/QtConcurrent/qtconcurrentstoredfunctioncall.h:187
#15 QtConcurrent::RunFunctionTask::run() (this=0x5fe38aa1d5b0) at
/usr/include/qt/QtConcurrent/qtconcurrentrunbase.h:114
#16 0x7bf4a797e541 in QThreadPoolThread::run() (this=0x5fe38aa0a070) at
thread/qthreadpool.cpp:100
#17 0x7bf4a797979a in operator() (__closure=) at
thread/qthread_unix.cpp:350
#18 (anonymous
namespace)::terminate_on_exception >
(t=) at thread/qthread_unix.cpp:287
#19 QThreadPrivate::start(void*) (arg=0x5fe38aa0a070) at
thread/qthread_unix.cpp:310
#20 0x7bf4a748e9eb in start_thread (arg=) at
pthread_create.c:444
#21 0x7bf4a75127cc in clone3 () at
../sysdeps/unix/sysv/linux/x86_64/clone3.S:78
Thread 4 (Thread 0x7bf4860006c0 (LWP 408101) "gwenview"):
#1 __pselect (nfds=nfds@entry=5, readfds=readfds@entry=0x7bf485ff7b60,
writefds=writefds@entry=0x0, exceptfds=exceptfds@entry=0x0, timeout=, timeout@entry=0x7bf485ff7b50, sigmask=sigmask@entry=0x0) at
../sysdeps/unix/sysv/linux/pselect.c:56
#2 0x7bf4a27356f9 in usbmuxd_listen_inotify () at
/usr/src/debug/libusbmuxd/libusbmuxd-2.0.2/src/libusbmuxd.c:923
#3 0x7bf4a27363cc in usbmuxd_listen () at
/usr/src/debug/libusbmuxd/libusbmuxd-2.0.2/src/libusbmuxd.c:979
#4 device_monitor (data=) at
/usr/src/debug/libusbmuxd/libusbmuxd-2.0.2/src/libusbmuxd.c:1107
#5 0x7bf4a748e9eb in start_thread (arg=) at
pthread_create.c:444
#6 0x7bf4a75127cc in clone3 () at
../sysdeps/unix/sysv/linux/x86_64/clone3.S:78
Thread 3 (Thread 0x7bf486c006c0 (LWP 408100) "Gwenview::Thumb"):
#1 __futex_abstimed_wait_common (futex_word=futex_word@entry=0x5fe38a16b550,
expected=expected@entry=0, clockid=clockid@entry=0, abstime=abstime@entry=0x0,
private=private@entry=0, cancel=cancel@entry=true) at futex-internal.c:87
#2 0x7bf4a748b52f in __GI___futex_abstimed_wait_cancelable64
(futex_word=futex_word@entry=0x5fe38a16b550, expected=expected@entry=0,
clockid=clockid@entry=0, abstime=abstime@entry=0x0, private=private@entry=0) at
futex-internal.c:139
#3 0x7bf4a748dd40 in __pthread_cond_wait_common (abstime=0x0, clockid=0,
mutex=0x5fe38a16b500, cond=0x5fe38a16b528) at pthread_cond_wait.c:503
#4 ___pthread_cond_wait (cond=0x5fe38a16b528, mutex=0x5fe38a16b500) at
pthread_cond_wait.c:618
#5 0x7bf4a7981524 in QWaitConditionPrivate::wait(QDeadlineTimer)
(deadline=..., this=0x5fe38a16b500) at thread/qwaitcondition_unix.cpp:146
#6 QWaitCondition::wait(QMutex*, QDeadlineTimer)
(this=this@entry=0x5fe38a13b8e0, mutex=mutex@entry=0x5fe38a13b8d8,
deadline=...) at t
[plasma-pa] [Bug 472370] Selecting a different audio output device sometimes won't change the output device for active applications
https://bugs.kde.org/show_bug.cgi?id=472370 Damian C changed: What|Removed |Added Resolution|WAITINGFORINFO |--- Status|NEEDSINFO |REPORTED -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 453109] Allow scrolling in the overview to switch between virtual desktops
https://bugs.kde.org/show_bug.cgi?id=453109 Damian changed: What|Removed |Added CC||thedevil...@gmx.com -- You are receiving this mail because: You are watching all bug changes.
[plasma-pa] [Bug 472370] Selecting a different audio output device sometimes won't change the output device for active applications
https://bugs.kde.org/show_bug.cgi?id=472370 --- Comment #2 from Damian C --- (In reply to Nate Graham from comment #1) > Can you install the "PulseAudio Volume Control" app and do the same thing > there, and see if the same problem happens? Thanks! After some days of testing I can say it tends to happen less frequently, but still does happen even using pavucontrol. Basically after selecting a device as default from the output devices tab, sometimes an app continues to send audio through the previously default device and needs to be set through the playback tab, changing the specific stream. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 474173] New: Changing partition flags of unmounted FAT32 partition caused crash
https://bugs.kde.org/show_bug.cgi?id=474173 Bug ID: 474173 Summary: Changing partition flags of unmounted FAT32 partition caused crash Classification: Applications Product: dolphin Version: 23.08.0 Platform: Archlinux OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: damian.hoes...@gmail.com CC: kfm-de...@kde.org Target Milestone: --- Application: dolphin (23.08.0) Qt Version: 5.15.10 Frameworks Version: 5.109.0 Operating System: Linux 6.4.12-zen1-1-zen x86_64 Windowing System: X11 Distribution: RebornOS Linux DrKonqi: 5.27.7 [KCrashBackend] -- Information about the crash: Desktop environment crashed and then restarted the moment boot/esp flag of foreign unmounted EFI System Partition was removed in GParted. The reporter is unsure if this crash is reproducible. -- Backtrace: Application: Dolphin (dolphin), signal: Segmentation fault [KCrash Handler] #4 0x556a869e9e10 in () #5 0x7f7d6e33bb47 in () at /usr/lib/libKF5KIOFileWidgets.so.5 #6 0x7f7d6e342235 in KFilePlacesModel::data(QModelIndex const&, int) const () at /usr/lib/libKF5KIOFileWidgets.so.5 #7 0x556a81a702fb in () #8 0x7f7d6e341c25 in KFilePlacesModel::url(QModelIndex const&) const () at /usr/lib/libKF5KIOFileWidgets.so.5 #9 0x556a81a6d421 in () #10 0x556a81a7036b in () #11 0x7f7d6e350d58 in () at /usr/lib/libKF5KIOFileWidgets.so.5 #12 0x7f7d6d21d60c in QListView::paintEvent(QPaintEvent*) () at /usr/lib/libQt5Widgets.so.5 #13 0x7f7d6e34f281 in KFilePlacesView::paintEvent(QPaintEvent*) () at /usr/lib/libKF5KIOFileWidgets.so.5 #14 0x7f7d6cfaf080 in QWidget::event(QEvent*) () at /usr/lib/libQt5Widgets.so.5 #15 0x7f7d6d05d703 in QFrame::event(QEvent*) () at /usr/lib/libQt5Widgets.so.5 #16 0x7f7d6c299702 in QCoreApplicationPrivate::sendThroughObjectEventFilters(QObject*, QEvent*) () at /usr/lib/libQt5Core.so.5 #17 0x7f7d6cf7892f in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /usr/lib/libQt5Widgets.so.5 #18 0x7f7d6c29c6f8 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /usr/lib/libQt5Core.so.5 #19 0x7f7d6cfa2fbb in QWidgetPrivate::sendPaintEvent(QRegion const&) () at /usr/lib/libQt5Widgets.so.5 #20 0x7f7d6cfa43bd in QWidgetPrivate::drawWidget(QPaintDevice*, QRegion const&, QPoint const&, QFlags, QPainter*, QWidgetRepaintManager*) () at /usr/lib/libQt5Widgets.so.5 #21 0x7f7d6cfa4dce in QWidgetPrivate::paintSiblingsRecursive(QPaintDevice*, QList const&, int, QRegion const&, QPoint const&, QFlags, QPainter*, QWidgetRepaintManager*) () at /usr/lib/libQt5Widgets.so.5 #22 0x7f7d6cfa385e in QWidgetPrivate::drawWidget(QPaintDevice*, QRegion const&, QPoint const&, QFlags, QPainter*, QWidgetRepaintManager*) () at /usr/lib/libQt5Widgets.so.5 #23 0x7f7d6cfa4dce in QWidgetPrivate::paintSiblingsRecursive(QPaintDevice*, QList const&, int, QRegion const&, QPoint const&, QFlags, QPainter*, QWidgetRepaintManager*) () at /usr/lib/libQt5Widgets.so.5 #24 0x7f7d6cfa385e in QWidgetPrivate::drawWidget(QPaintDevice*, QRegion const&, QPoint const&, QFlags, QPainter*, QWidgetRepaintManager*) () at /usr/lib/libQt5Widgets.so.5 #25 0x7f7d6cfa4dce in QWidgetPrivate::paintSiblingsRecursive(QPaintDevice*, QList const&, int, QRegion const&, QPoint const&, QFlags, QPainter*, QWidgetRepaintManager*) () at /usr/lib/libQt5Widgets.so.5 #26 0x7f7d6cfa4c2c in QWidgetPrivate::paintSiblingsRecursive(QPaintDevice*, QList const&, int, QRegion const&, QPoint const&, QFlags, QPainter*, QWidgetRepaintManager*) () at /usr/lib/libQt5Widgets.so.5 #27 0x7f7d6cfa385e in QWidgetPrivate::drawWidget(QPaintDevice*, QRegion const&, QPoint const&, QFlags, QPainter*, QWidgetRepaintManager*) () at /usr/lib/libQt5Widgets.so.5 #28 0x7f7d6cf84719 in () at /usr/lib/libQt5Widgets.so.5 #29 0x7f7d6cfaf111 in QWidget::event(QEvent*) () at /usr/lib/libQt5Widgets.so.5 #30 0x7f7d6dc9d03e in KXmlGuiWindow::event(QEvent*) () at /usr/lib/libKF5XmlGui.so.5 #31 0x7f7d6cf7893f in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /usr/lib/libQt5Widgets.so.5 #32 0x7f7d6c29c6f8 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /usr/lib/libQt5Core.so.5 #33 0x7f7d6c2a165b in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () at /usr/lib/libQt5Core.so.5 #34 0x7f7d6c2e76d8 in () at /usr/lib/libQt5Core.so.5 #35 0x7f7d69f0fa31 in g_main_context_dispatch () at /usr/lib/libglib-2.0.so.0 #36 0x7f7d69f6ccc9 in () at /usr/lib/libglib-2.0.so.0 #37 0x7f7d69f0d0e2 in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #38 0x7f7d6c2eb51c in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #39 0x7f7d6c29b404 in QEv
[kmail2] [Bug 460687] "Forward To" option missing from Filter Actions
https://bugs.kde.org/show_bug.cgi?id=460687 --- Comment #3 from Damian C --- (In reply to Laurent Montel from comment #2) > We have "redirect" action. > so what is missing ? I don't think Redirect is the same as Forward. If you look at the options presented here: https://docs.kde.org/stable5/en/kmail/kmail2/filters.html Forward and Redirect are two distinct options. Redirect: "This will redirect the message as-is to another email address.". I think it attempts to re route the message without re sending it as a message sent by you, but I'm not sure. While forward is the same as right clicking the message and re send it from your account as if right clicking and selecting forward - inline. Sending the messag efrom your account, adding the "Fwd:" prefix to the subject. So yeah, Forward To is literally missing. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 460687] "Forward To" option missing from Filter Actions
https://bugs.kde.org/show_bug.cgi?id=460687 Damian C changed: What|Removed |Added Version|5.21.2 |5.23.3 --- Comment #1 from Damian C --- Still an issue with: Operating System: Arch Linux KDE Plasma Version: 5.27.6 KDE Frameworks Version: 5.108.0 Qt Version: 5.15.10 Kernel Version: 6.4.3-zen1-1-zen (64-bit) Graphics Platform: Wayland Processors: 12 × Intel® Core™ i7-8700K CPU @ 3.70GHz Memory: 15.6 GiB of RAM Graphics Processor: NVIDIA GeForce GTX 1070/PCIe/SSE2 -- You are receiving this mail because: You are watching all bug changes.
[pulseaudio-qt] [Bug 472370] Selecting a different audio output device sometimes won't change the output device for active applications
https://bugs.kde.org/show_bug.cgi?id=472370 Damian C changed: What|Removed |Added CC||dcalv...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[pulseaudio-qt] [Bug 472370] New: Selecting a different audio output device sometimes won't change the output device for active applications
https://bugs.kde.org/show_bug.cgi?id=472370 Bug ID: 472370 Summary: Selecting a different audio output device sometimes won't change the output device for active applications Classification: Plasma Product: pulseaudio-qt Version: 1.3 Platform: Archlinux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: nicolas.fe...@gmx.de Reporter: dcalv...@gmail.com Target Milestone: --- SUMMARY *** Selecting a different audio output device sometimes won't change the output device for active applications such as a game or a player, or a browser. You need to change the application's output device individually by using the "applications" tab in the volume control. *** STEPS TO REPRODUCE 1. Be playing some audio on an application, youtube over brave browser for instance. 2. Use the panel's volume control to select a different output device, such as a headset. 3. Audio continues to play over the previously selected output device. OBSERVED RESULT Audio continues to play over the previously selected output device I then correct this by going over to the applications tab in the aforementioned volume control and select a different output device for the specific application. EXPECTED RESULT Applications play over the device selected on the devices volume control tab. SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 5.27.6 KDE Frameworks Version: 5.108.0 Qt Version: 5.15.10 Kernel Version: 6.4.3-zen1-1-zen (64-bit) Graphics Platform: Wayland Processors: 12 × Intel® Core™ i7-8700K CPU @ 3.70GHz Memory: 15.6 GiB of RAM Graphics Processor: NVIDIA GeForce GTX 1070/PCIe/SSE2 ADDITIONAL INFORMATION This does not happen always, can't find a pattern to it. Unsure if related, sounds like it could be: Using the mouse scroll wheel to change the volume by having the mouse cursor placed above the panel's volume icon also changes the volume of the previously used device (and the associated system sound for each step of volume change also plays over the previously active device) unless I open the panel and manually slide the volume over the desired currently active device, only then the mouse scroll wheel acts as expected. Same result happens with my keyboard's dedicated volume keys. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 471913] New: Dolphin crashed when dragging large file to another partition
https://bugs.kde.org/show_bug.cgi?id=471913 Bug ID: 471913 Summary: Dolphin crashed when dragging large file to another partition Classification: Applications Product: dolphin Version: 23.04.1 Platform: Archlinux OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: damian.hoes...@gmail.com CC: kfm-de...@kde.org Target Milestone: --- Application: dolphin (23.04.1) Qt Version: 5.15.9 Frameworks Version: 5.106.0 Operating System: Linux 6.3.5-arch1-1 x86_64 Windowing System: X11 Distribution: Arch Linux DrKonqi: 5.27.5 [KCrashBackend] -- Information about the crash: Dolphin immediately crashed when dragging large file to another partition. Both partitions were Btrfs. The reporter is unsure if this crash is reproducible. -- Backtrace: Application: Dolphin (dolphin), signal: Segmentation fault [KCrash Handler] #4 0x7f4b140037f4 in QUrl::operator==(QUrl const&) const () at /usr/lib/libQt5Core.so.5 #5 0x7f4b15e7e1a5 in () at /usr/lib/libKF5KIOCore.so.5 #6 0x7f4b15e89969 in () at /usr/lib/libKF5KIOCore.so.5 #7 0x7f4b140cffe7 in () at /usr/lib/libQt5Core.so.5 #8 0x7f4b140d1b1f in QTimer::timeout(QTimer::QPrivateSignal) () at /usr/lib/libQt5Core.so.5 #9 0x7f4b140c27ae in QObject::event(QEvent*) () at /usr/lib/libQt5Core.so.5 #10 0x7f4b14d7893f in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /usr/lib/libQt5Widgets.so.5 #11 0x7f4b1409ab18 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /usr/lib/libQt5Core.so.5 #12 0x7f4b140e976b in QTimerInfoList::activateTimers() () at /usr/lib/libQt5Core.so.5 #13 0x7f4b140e9d4a in () at /usr/lib/libQt5Core.so.5 #14 0x7f4b11f10981 in g_main_context_dispatch () at /usr/lib/libglib-2.0.so.0 #15 0x7f4b11f6db39 in () at /usr/lib/libglib-2.0.so.0 #16 0x7f4b11f0e032 in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #17 0x7f4b140e9f0c in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #18 0x7f4b14099824 in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #19 0x7f4b1409acc3 in QCoreApplication::exec() () at /usr/lib/libQt5Core.so.5 #20 0x565155df6da8 in () #21 0x7f4b152dd850 in () at /usr/lib/libc.so.6 #22 0x7f4b152dd90a in __libc_start_main () at /usr/lib/libc.so.6 #23 0x565155df7565 in () [Inferior 1 (process 52281) detached] The reporter indicates this bug may be a duplicate of or related to bug 470925. Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 470853] New: Links not opening in Firefox
https://bugs.kde.org/show_bug.cgi?id=470853 Bug ID: 470853 Summary: Links not opening in Firefox Classification: Applications Product: okular Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: okular-de...@kde.org Reporter: dcallma...@gmail.com Target Milestone: --- Hi Team. I am running Ubuntu 20.04.6 LTS, Okular version 1.9.3 & Firefox for Ubuntu 114.0 (64-bit). When I click on a link in a PDF, Okular tries to open it with Balena Etcher instead of Firefox. I can't seem to find a setting to correct this nor have I been able to find a solution in any forums. Any help you can offer will be greatly appreciated. Thanks & kind regards, Damian. -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 463527] Multi monitor layout no longer save - it always reverts to the previously saved layout (Wayland)
https://bugs.kde.org/show_bug.cgi?id=463527 Damian Kaczmarek changed: What|Removed |Added Status|NEEDSINFO |RESOLVED --- Comment #13 from Damian Kaczmarek --- Jackpot! Steve, great deduction! That was it. I originally had to disable the KScreen service due to my monitors not wanting to stay in standby. Now that I'm on Wayland possibly the original issue with standby will go away. Once that I re-enabled the KScreen service, my settings started saving again. I am not sure why trying on a fresh user would not work earlier, possibly it was another issue which was independently fixed. Really happy to close this ticket now. Thank you Steve & Nate. PS. In light of this issue, I am not sure if ability to fully disable the KScreen service is such a blessing! Perhaps there could be a warning in the display settings? -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 463527] Multi monitor layout no longer save - it always reverts to the previously saved layout (Wayland)
https://bugs.kde.org/show_bug.cgi?id=463527 --- Comment #9 from Damian Kaczmarek --- Nate, where does KWin store display configuration these days? All of my `.local/share/kscreen` files are from 2022. -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 463527] Multi monitor layout no longer save - it always reverts to the previously saved layout (Wayland)
https://bugs.kde.org/show_bug.cgi?id=463527 Damian Kaczmarek changed: What|Removed |Added Status|RESOLVED|REOPENED Resolution|WORKSFORME |--- --- Comment #8 from Damian Kaczmarek --- > Darn. Is that different from what was happening before, or the same issue? My monitor layout is still not getting saved. It keeps resetting to a state it once saved after each time my monitors go into standby. I did a test of clearing all KDE/Plasma configs and starting with a fresh account. The issue was the same but I had to do the whole layout each time vs just a few adjustments. It is super annoying as I have to fix my monitor layout multiple times a day. Any time I go AFK and my monitors go into standby. I am happy to jump on to a debugging session or provide any info. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 468895] Desktop freezes when Night Color feature kicks in running Wayland with NVIDIA proprietary drivers.
https://bugs.kde.org/show_bug.cgi?id=468895 --- Comment #5 from Damian C --- (In reply to Zamundaaa from comment #3) > There's still no GAMMA_LUT property, so I'm not sure how night color would > be related. Can you attach your full KWin log? So > > journalctl --user-unit plasma-kwin_wayland --boot 0 > after causing the issue again Attached! I don't expect Night Color to work since the property is not there, but it seems to cause the issue when it attempts to kick in. And the only way to stop it from happening so far is to disable Night Color. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 468895] Desktop freezes when Night Color feature kicks in running Wayland with NVIDIA proprietary drivers.
https://bugs.kde.org/show_bug.cgi?id=468895 --- Comment #4 from Damian C --- Created attachment 158675 --> https://bugs.kde.org/attachment.cgi?id=158675&action=edit journalctl -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 469175] Panel with taskbar freezes visually but remains operational
https://bugs.kde.org/show_bug.cgi?id=469175 Damian C changed: What|Removed |Added CC||dcalv...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 469175] New: Panel with taskbar freezes visually but remains operational
https://bugs.kde.org/show_bug.cgi?id=469175 Bug ID: 469175 Summary: Panel with taskbar freezes visually but remains operational Classification: Plasma Product: plasmashell Version: 5.27.4 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Panel Assignee: plasma-b...@kde.org Reporter: dcalv...@gmail.com CC: niccolo.venera...@gmail.com Target Milestone: 1.0 SUMMARY Default panel with taskbar and clock freezes visually at some point during operation. The panel can still be interacted with but it won't update any information, the time on the digital clock remains as it was when it stopped working, and taskbar icons that would update some information (such as the new email counter within the kmail icon) will not update. STEPS TO REPRODUCE 1. Boot and login normally. 2. Use the system normally and at some point some panel will stop responding, normally the main display one, but not exclusively. OBSERVED RESULT Panel stops visually updating, and becomes "frozen", but interaction is still possible, so I'd call it "functional". EXPECTED RESULT Panel doesn't freeze visually at all. SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 5.27.4 KDE Frameworks Version: 5.105.0 Qt Version: 5.15.9 Kernel Version: 6.2.13-zen-1-zen (64-bit) Graphics Platform: Wayland Processors: 12 × Intel® Core™ i7-8700K CPU @ 3.70GHz Memory: 15.6 GiB of RAM Graphics Processor: NVIDIA GeForce GTX 1070/PCIe/SSE2 ADDITIONAL INFORMATION It can be brought back to a working state by right clicking the panel, entering edit mode and changing some visual aspect of it, such as the height. It does not happen on all panels simultaneously, it seems to affect a single display, though not necessarily the same one every time. It may have happened around the time I opened a game running with Proton, but unsure at this point. Even more strange, during the "frozen" period, if one clicks on the pinned taskbar icon for "System Settings" it opens some windows that existed at some point on a different activity. Even stranger is the fact that this activity no longer exists as I deleted it from the activities menu, but during this issue, clicking on this icon brings back the apps that I had open back then, which were a browser and a konsole window. This strange behavior ceases when the workaround of changing the panels height is applied. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 468895] Desktop freezes when Night Color feature kicks in running Wayland with NVIDIA proprietary drivers.
https://bugs.kde.org/show_bug.cgi?id=468895 --- Comment #2 from Damian C --- Created attachment 158525 --> https://bugs.kde.org/attachment.cgi?id=158525&action=edit drm_info1 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 450327] Night Color Has No Effect on KDE Wayland with NVIDIA
https://bugs.kde.org/show_bug.cgi?id=450327 --- Comment #7 from Damian C --- (In reply to Zamundaaa from comment #6) > Please create a separate bug report for the freeze Done, https://bugs.kde.org/show_bug.cgi?id=468895 Thank you, -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 468895] Desktop freezes when Night Color feature kicks in running Wayland with NVIDIA proprietary drivers.
https://bugs.kde.org/show_bug.cgi?id=468895 Damian C changed: What|Removed |Added CC||dcalv...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 468895] New: Desktop freezes when Night Color feature kicks in running Wayland with NVIDIA proprietary drivers.
https://bugs.kde.org/show_bug.cgi?id=468895 Bug ID: 468895 Summary: Desktop freezes when Night Color feature kicks in running Wayland with NVIDIA proprietary drivers. Classification: Plasma Product: kwin Version: 5.27.4 Platform: Archlinux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: wayland-generic Assignee: kwin-bugs-n...@kde.org Reporter: dcalv...@gmail.com Target Milestone: --- SUMMARY *** With the Night Color feature enabled, running Wayland with NVIDIA proprietary drivers, one or more monitors freezes momentarily. If left unattended the whole kwin session freezes on all monitors. On the logs, the message : "kwin_wayland_drm: Failed to create gamma blob! Invalid argument" can be seen at each time the desktop freezes. After a few seconds it will unfreeze and let you continue for maybe a minute more before going at it again, I'm guessing it is the Night Color feature attempting to start again. *** STEPS TO REPRODUCE 1. Be running a Kwin Wayland session using Nvidia proprietary drivers. 2. Have the Night Color feature enabled. 3. At the time the Night Color feature is supposed to kick in, the issue is observed. OBSERVED RESULT One or more monitors freezes momentarily. If left unattended the whole kwin session freezes on all monitors. EXPECTED RESULT Night Color works as expected. SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 5.27.4 KDE Frameworks Version: 5.105.0 Qt Version: 5.15.9 Kernel Version: 6.2.12-zen1-1-zen (64-bit) Graphics Platform: Wayland Processors: 12 × Intel® Core™ i7-8700K CPU @ 3.70GHz Memory: 15.6 GiB of RAM Graphics Processor: NVIDIA GeForce GTX 1070/PCIe/SSE2 Nvidia Drivers: 530.41.03-1 ADDITIONAL INFORMATION 3 monitors: One Display Port, one HDMI and one DVI. It seems to favor freezing the DVI monitor first, but the rest will follow soon. To avoid this issue and continue to have a working system through the night hours, the workaround has been to disable Night Color completely. Seems related to #450327. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 450327] Night Color Has No Effect on KDE Wayland with NVIDIA
https://bugs.kde.org/show_bug.cgi?id=450327 --- Comment #5 from Damian C --- I want to add that with the Night Color feature enabled, each time the "kwin_wayland_drm: Failed to create gamma blob! Invalid argument" message shows on the logs, the screen freezes (one of them, the other two won't), and it can completely freeze the kwin session. 3 monitors: One Display Port, one HDMI and one DVI. Operating System: Arch Linux KDE Plasma Version: 5.27.4 KDE Frameworks Version: 5.105.0 Qt Version: 5.15.9 Kernel Version: 6.2.12-zen1-1-zen (64-bit) Graphics Platform: Wayland Processors: 12 × Intel® Core™ i7-8700K CPU @ 3.70GHz Memory: 15.6 GiB of RAM Graphics Processor: NVIDIA GeForce GTX 1070/PCIe/SSE2 Nvidia Drivers: 530.41.03-1 Workaround has been to disable this feature completely. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 450327] Night Color Has No Effect on KDE Wayland with NVIDIA
https://bugs.kde.org/show_bug.cgi?id=450327 Damian C changed: What|Removed |Added CC||dcalv...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 460687] "Forward To" option missing from Filter Actions
https://bugs.kde.org/show_bug.cgi?id=460687 Damian C changed: What|Removed |Added CC||dcalv...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 438345] Contents load as Blank Page in Wayland - Kmail and Akregator
https://bugs.kde.org/show_bug.cgi?id=438345 --- Comment #10 from Damian C --- (In reply to Adam Borsos from comment #9) > QTWEBENGINE_CHROMIUM_FLAGS="--disable-gpu-compositing" works me as a > workaround, so the issue seems to be HW accel related > > (Operating System: Gentoo Linux 2.13 > KDE Plasma Version: 5.27.4 > KDE Frameworks Version: 5.104.0 > Qt Version: 5.15.8 > Kernel Version: 6.1.19-gentoo-x86_64 (64-bit) > Graphics Platform: Wayland > Processors: 12 × AMD Ryzen 5 5600G with Radeon Graphics > Memory: 31.2 GiB of RAM > Graphics Processor: NVIDIA GeForce RTX 3070 Ti/PCIe/SSE2) This works for me as well! Also works for the news feed. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 458038] On X11, widgets still inappropriately move after login after panel appears
https://bugs.kde.org/show_bug.cgi?id=458038 --- Comment #21 from Damian C --- Confirmed, the issue is no longer happening. Thank you! -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 463527] Multi monitor layout no longer save - it always reverts to the previously saved layout (Wayland)
https://bugs.kde.org/show_bug.cgi?id=463527 --- Comment #4 from Damian Kaczmarek --- Nate, I installed Plasma and all related components from an openSUSE repo KDE:Unstable. The version I have is "5.26.80git.20230114T174945~0e72dcb9-ku.127.1". I can see the new UI with "Change Screen priorities". Unfortunately the display layout is not getting saved as it reverts back after unlocking my screen after longer inactivity or after logging back in after a reboot. -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 463527] Multi monitor layout no longer save - it always reverts to the previously saved layout (Wayland)
https://bugs.kde.org/show_bug.cgi?id=463527 --- Comment #3 from Damian Kaczmarek --- (In reply to Nate Graham from comment #2) > This should be fixed in Plasma 5.27. Thank you Nate. I am going crazy from having to reset the config for all 4 monitors every time I come back to the PC. I had the temptation to disable all power saving features just to make sure I don't have to do it. :) Looking forward to 5.27 and thank you for a quick fix. -- You are receiving this mail because: You are watching all bug changes.
[libkgapi] [Bug 439285] Bad request, Google replied "Contacts API is being deprecated"
https://bugs.kde.org/show_bug.cgi?id=439285 Damian C changed: What|Removed |Added CC||dcalv...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 463527] Multi monitor layout no longer save - it always reverts to the previously saved layout (Wayland)
https://bugs.kde.org/show_bug.cgi?id=463527 --- Comment #1 from Damian Kaczmarek --- Created attachment 154853 --> https://bugs.kde.org/attachment.cgi?id=154853&action=edit Reverts to this one -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 463527] New: Multi monitor layout no longer save - it always reverts to the previously saved layout (Wayland)
https://bugs.kde.org/show_bug.cgi?id=463527 Bug ID: 463527 Summary: Multi monitor layout no longer save - it always reverts to the previously saved layout (Wayland) Classification: Plasma Product: plasmashell Version: 5.26.4 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Multi-screen support Assignee: plasma-b...@kde.org Reporter: rus...@gmail.com CC: aleix...@kde.org, notm...@gmail.com Target Milestone: 1.0 Created attachment 154851 --> https://bugs.kde.org/attachment.cgi?id=154851&action=edit Desired layout I have a 4 monitors layout. Yesterday I rebuilt my desk, slightly switching my layout (right monitor swapped with the left one, and flipped one of the monitors that was vertical). Unfortunately it looks like I am unable to persist those changes in the latest KDE+Plasma. It always reverts to the layout from before redoing my desk. STEPS TO REPRODUCE Unfortunately I do not know how to reproduce it on another machine since I only have one PC with multiple monitors 1. Have a monitor layout such as the one in the attachment 1. Restart PC or leave PC running long enough for power saving to kick in and turn off monitors 2. KScreen2 service is disabled (not sure if related, but it was preventing power saving from kicking in - it's another issue) 3. Log back into Plasma OBSERVED RESULT Monitor layout is not saved, it is reset to a layout from Plasma <5.26 EXPECTED RESULT Monitor layout to be saved SOFTWARE/OS VERSIONS Linux/KDE Plasma: Latest openSUSE tumbleweed (as of 12/27/22) (available in About System) KDE Plasma Version: 5.26.4 KDE Frameworks Version: not sure how to check Qt Version: 5.15.7 ADDITIONAL INFORMATION Using Wayland -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 462306] New: Using ventoy on USB drive causes Dolphin to crash
https://bugs.kde.org/show_bug.cgi?id=462306 Bug ID: 462306 Summary: Using ventoy on USB drive causes Dolphin to crash Classification: Applications Product: dolphin Version: 22.08.3 Platform: Archlinux OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: damian.hoes...@gmail.com CC: kfm-de...@kde.org Target Milestone: --- Application: dolphin (22.08.3) Qt Version: 5.15.7 Frameworks Version: 5.100.0 Operating System: Linux 6.0.9-arch1-1 x86_64 Windowing System: X11 Distribution: RebornOS Linux DrKonqi: 5.26.3 [KCrashBackend] -- Information about the crash: Using ventoy on an unmounted 64GB USB flash drive caused Dolphin to crash. The reporter is unsure if this crash is reproducible. -- Backtrace: Application: Dolphin (dolphin), signal: Segmentation fault [KCrash Handler] #4 0x7f57685fccd1 in Solid::Device::~Device() () from /usr/lib/libKF5Solid.so.5 #5 0x7f5768bba6a8 in ?? () from /usr/lib/libKF5KIOFileWidgets.so.5 #6 0x7f5768bc12b5 in KFilePlacesModel::data(QModelIndex const&, int) const () from /usr/lib/libKF5KIOFileWidgets.so.5 #7 0x55b041cd8ef1 in ?? () #8 0x7f5768bc0935 in KFilePlacesModel::url(QModelIndex const&) const () from /usr/lib/libKF5KIOFileWidgets.so.5 #9 0x55b041cd3a61 in ?? () #10 0x55b041cd8f23 in ?? () #11 0x7f5768bd098b in ?? () from /usr/lib/libKF5KIOFileWidgets.so.5 #12 0x7f5767a1bf95 in QListView::paintEvent(QPaintEvent*) () from /usr/lib/libQt5Widgets.so.5 #13 0x7f5768bcd8c1 in KFilePlacesView::paintEvent(QPaintEvent*) () from /usr/lib/libKF5KIOFileWidgets.so.5 #14 0x7f57677af3c4 in QWidget::event(QEvent*) () from /usr/lib/libQt5Widgets.so.5 #15 0x7f576785d823 in QFrame::event(QEvent*) () from /usr/lib/libQt5Widgets.so.5 #16 0x7f5766a8cc02 in QCoreApplicationPrivate::sendThroughObjectEventFilters(QObject*, QEvent*) () from /usr/lib/libQt5Core.so.5 #17 0x7f5767778b0c in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib/libQt5Widgets.so.5 #18 0x7f5766a8cf98 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /usr/lib/libQt5Core.so.5 #19 0x7f57677a334b in QWidgetPrivate::sendPaintEvent(QRegion const&) () from /usr/lib/libQt5Widgets.so.5 #20 0x7f57677a46a6 in QWidgetPrivate::drawWidget(QPaintDevice*, QRegion const&, QPoint const&, QFlags, QPainter*, QWidgetRepaintManager*) () from /usr/lib/libQt5Widgets.so.5 #21 0x7f57677a50ae in QWidgetPrivate::paintSiblingsRecursive(QPaintDevice*, QList const&, int, QRegion const&, QPoint const&, QFlags, QPainter*, QWidgetRepaintManager*) () from /usr/lib/libQt5Widgets.so.5 #22 0x7f57677a3bfb in QWidgetPrivate::drawWidget(QPaintDevice*, QRegion const&, QPoint const&, QFlags, QPainter*, QWidgetRepaintManager*) () from /usr/lib/libQt5Widgets.so.5 #23 0x7f57677a50ae in QWidgetPrivate::paintSiblingsRecursive(QPaintDevice*, QList const&, int, QRegion const&, QPoint const&, QFlags, QPainter*, QWidgetRepaintManager*) () from /usr/lib/libQt5Widgets.so.5 #24 0x7f57677a3bfb in QWidgetPrivate::drawWidget(QPaintDevice*, QRegion const&, QPoint const&, QFlags, QPainter*, QWidgetRepaintManager*) () from /usr/lib/libQt5Widgets.so.5 #25 0x7f57677a50ae in QWidgetPrivate::paintSiblingsRecursive(QPaintDevice*, QList const&, int, QRegion const&, QPoint const&, QFlags, QPainter*, QWidgetRepaintManager*) () from /usr/lib/libQt5Widgets.so.5 #26 0x7f57677a4f0c in QWidgetPrivate::paintSiblingsRecursive(QPaintDevice*, QList const&, int, QRegion const&, QPoint const&, QFlags, QPainter*, QWidgetRepaintManager*) () from /usr/lib/libQt5Widgets.so.5 #27 0x7f57677a3bfb in QWidgetPrivate::drawWidget(QPaintDevice*, QRegion const&, QPoint const&, QFlags, QPainter*, QWidgetRepaintManager*) () from /usr/lib/libQt5Widgets.so.5 #28 0x7f5767784a0d in ?? () from /usr/lib/libQt5Widgets.so.5 #29 0x7f57677af094 in QWidget::event(QEvent*) () from /usr/lib/libQt5Widgets.so.5 #30 0x7f57685272be in KXmlGuiWindow::event(QEvent*) () from /usr/lib/libKF5XmlGui.so.5 #31 0x7f5767778b1c in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib/libQt5Widgets.so.5 #32 0x7f5766a8cf98 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /usr/lib/libQt5Core.so.5 #33 0x7f5766a8daa3 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () from /usr/lib/libQt5Core.so.5 #34 0x7f5766ad3e68 in ?? () from /usr/lib/libQt5Core.so.5 #35 0x7f5764c6d87b in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0 #36 0x7f5764cc4279 in ?? () from /usr/lib/libglib-2.0.so.0 #37 0x7f5764c6c132 in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0 #38 0x7f5766ad7c4c in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/libQt5Core.so.5 #
[plasmashell] [Bug 458038] On X11, widgets still inappropriately move after login
https://bugs.kde.org/show_bug.cgi?id=458038 --- Comment #14 from Damian C --- (In reply to Damian C from comment #13) > (In reply to Nate Graham from comment #11) > > (waiting for confirmation that it's still an issue in the X11 session for > > Plasma 5.26.2, for the people who were experiencing it in 5.26.0) > > I regret to report that this is still happening running 5.26.2, no change in > behavior whatsoever. Oh and now it seems, plasmashell --replace doesn't put them back to their proper place. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 458038] On X11, widgets still inappropriately move after login
https://bugs.kde.org/show_bug.cgi?id=458038 --- Comment #13 from Damian C --- (In reply to Nate Graham from comment #11) > (waiting for confirmation that it's still an issue in the X11 session for > Plasma 5.26.2, for the people who were experiencing it in 5.26.0) I regret to report that this is still happening running 5.26.2, no change in behavior whatsoever. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 455538] Option to keep floating panels -floating- when windows are maximized and using "Maximized Window Gap" Kwin Script
https://bugs.kde.org/show_bug.cgi?id=455538 --- Comment #5 from Damian C --- (In reply to Nate Graham from comment #4) > Git commit ed0214057e7ae78bedc4486a6344db9459ce5570 by Nate Graham, on > behalf of Niccolò Venerandi. > Committed on 25/10/2022 at 14:52. > Pushed by ngraham into branch 'master'. > > Panel: when floating, de-float when window touches it > > A floating Panel now de-floats and becomes opaque whenever a window touches > it. > This also allows for a thinner Panel when a window is maximized (a normal > Panel > is 44 px; before this patch a de-floated one was 60, now it's 52px) and that > should > allay complaints about excessive margins). > Related: bug 455483, bug 455323 > FIXED-IN: 5.27 > > M +29 -6desktoppackage/contents/views/Panel.qml > > https://invent.kde.org/plasma/plasma-desktop/commit/ > ed0214057e7ae78bedc4486a6344db9459ce5570 Thank you! looking forward to 5.27 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 458038] Widgets become slightly misplaced (misaligned) after login
https://bugs.kde.org/show_bug.cgi?id=458038 --- Comment #6 from Damian C --- (In reply to Nate Graham from comment #4) > We're getting reports that this remains broken but only for X11. Which makes > sense for why I can't reproduce it, because I'm on Wayland. And probably the > developers who worked on the fix are on Wayland too. > > For anyone able to reproduce on X11, can you try the following: > > 1. Log out of your X11 session > 2. Log into a wayland session > 3. Arrange widgets how yo want > 3. Log out of the wayland session > 4. Log into it again > > Thanks! I've done this and it seems to be less messy overall. Almost all widgets retain their proper positioning, except for 2 of the digital clock ones. This can be observed in the screenshot I've uploaded (comment 5 I think). And the webslice widget is now displaying a dark grey color instead of the contents of the website. (can also be seen on screenshot) This of course also brings other problems with using wayland, such as the webslice widget issue, Kmail's blank emails on the reading pane, etc. But it seems to not misalign most of the widgets as opposed to X11. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 458038] Widgets become slightly misplaced (misaligned) after login
https://bugs.kde.org/show_bug.cgi?id=458038 --- Comment #5 from Damian C --- Created attachment 153030 --> https://bugs.kde.org/attachment.cgi?id=153030&action=edit Widgets after rebooting using wayland. Digital clock widgets showing wrong size, but better overall. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 460687] New: "Forward To" option missing from Filter Actions
https://bugs.kde.org/show_bug.cgi?id=460687 Bug ID: 460687 Summary: "Forward To" option missing from Filter Actions Classification: Applications Product: kmail2 Version: 5.21.2 Platform: Archlinux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: misc Assignee: kdepim-b...@kde.org Reporter: dcalv...@gmail.com Target Milestone: --- Created attachment 153013 --> https://bugs.kde.org/attachment.cgi?id=153013&action=edit Missing Forward To option within Filter Actions menu SUMMARY *** When configuring either a new or existing filter, the Filter Actions drop down menu is missing the Forward-To option. *** STEPS TO REPRODUCE 1. Go to settings. Configure Filters 2. Click on Filter Actions. OBSERVED RESULT Observe the lack of a "Forward To" option. EXPECTED RESULT Forward To option within the Filter Actions menu as described here: https://docs.kde.org/stable5/en/kmail/kmail2/filters.html SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 5.26.0 KDE Frameworks Version: 5.99.0 Qt Version: 5.15.6 Kernel Version: 6.0.2-zen1-1-zen (64-bit) Graphics Platform: X11 Processors: 12 × Intel® Core™ i7-8700K CPU @ 3.70GHz Memory: 15.6 GiB of RAM Graphics Processor: NVIDIA GeForce GTX 1070/PCIe/SSE2 ADDITIONAL INFORMATION See Attached image. -- You are receiving this mail because: You are watching all bug changes.
[kaddressbook] [Bug 446580] Contact synchronization with google doesn't work.
https://bugs.kde.org/show_bug.cgi?id=446580 Damian C changed: What|Removed |Added CC||dcalv...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 458038] Widgets become slightly misplaced (misaligned) after login
https://bugs.kde.org/show_bug.cgi?id=458038 Damian C changed: What|Removed |Added CC||dcalv...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 460618] Can't remember desktop widget positions after relogin
https://bugs.kde.org/show_bug.cgi?id=460618 Damian C changed: What|Removed |Added CC||dcalv...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 458038] Widgets become slightly misplaced (misaligned) after login
https://bugs.kde.org/show_bug.cgi?id=458038 Damian C changed: What|Removed |Added Status|RESOLVED|REOPENED Ever confirmed|0 |1 Resolution|DUPLICATE |--- --- Comment #2 from Damian C --- (In reply to Nate Graham from comment #1) > > *** This bug has been marked as a duplicate of bug 413645 *** Hello, I've seen that in bug 413645 this has been marked as fixed with 5.26. I am now running 5.26 and I'm afraid this behavior as described in this bug report persist. Issuing plasmashell --replace restores the widgets to their intended position (previous to reboot). Thank you, -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 460489] New: Konsole crashed when selecting some text
https://bugs.kde.org/show_bug.cgi?id=460489 Bug ID: 460489 Summary: Konsole crashed when selecting some text Classification: Applications Product: konsole Version: 22.08.2 Platform: Archlinux OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: konsole-de...@kde.org Reporter: damian.hoes...@gmail.com Target Milestone: --- Application: konsole (22.08.2) Qt Version: 5.15.6 Frameworks Version: 5.99.0 Operating System: Linux 6.0.0-270-tkg-bmq x86_64 Windowing System: X11 Distribution: RebornOS Linux DrKonqi: 5.26.0 [KCrashBackend] -- Information about the crash: was accidentally selecting some text output of running command and Konsole crashed The reporter is unsure if this crash is reproducible. -- Backtrace: Application: Konsole (konsole), signal: Aborted [KCrash Handler] #4 0x7fa832d9864c in ?? () from /usr/lib/libc.so.6 #5 0x7fa832d48958 in raise () from /usr/lib/libc.so.6 #6 0x7fa832d3253d in abort () from /usr/lib/libc.so.6 #7 0x7fa832fcb112 in std::__glibcxx_assert_fail (file=, line=, function=, condition=) at /usr/src/debug/gcc/libstdc++-v3/src/c++11/debug.cc:60 #8 0x7fa834646690 in Konsole::Screen::setSelectionEnd(int, int, bool) () from /usr/lib/libkonsoleprivate.so.1 #9 0x7fa8346a2153 in Konsole::TerminalDisplay::extendSelection(QPoint const&) () from /usr/lib/libkonsoleprivate.so.1 #10 0x7fa8346a6388 in Konsole::TerminalDisplay::mouseMoveEvent(QMouseEvent*) () from /usr/lib/libkonsoleprivate.so.1 #11 0x7fa833f196bf in QWidget::event(QEvent*) () from /usr/lib/libQt5Widgets.so.5 #12 0x7fa833ee2b1c in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib/libQt5Widgets.so.5 #13 0x7fa833ee8339 in QApplication::notify(QObject*, QEvent*) () from /usr/lib/libQt5Widgets.so.5 #14 0x7fa8333bcb88 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /usr/lib/libQt5Core.so.5 #15 0x7fa833ee6337 in QApplicationPrivate::sendMouseEvent(QWidget*, QMouseEvent*, QWidget*, QWidget*, QWidget**, QPointer&, bool, bool) () from /usr/lib/libQt5Widgets.so.5 #16 0x7fa833f373b5 in ?? () from /usr/lib/libQt5Widgets.so.5 #17 0x7fa833f3915e in ?? () from /usr/lib/libQt5Widgets.so.5 #18 0x7fa833ee2b1c in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib/libQt5Widgets.so.5 #19 0x7fa8333bcb88 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /usr/lib/libQt5Core.so.5 #20 0x7fa83384213c in QGuiApplicationPrivate::processMouseEvent(QWindowSystemInterfacePrivate::MouseEvent*) () from /usr/lib/libQt5Gui.so.5 #21 0x7fa83382b985 in QWindowSystemInterface::sendWindowSystemEvents(QFlags) () from /usr/lib/libQt5Gui.so.5 #22 0x7fa82d1346c0 in ?? () from /usr/lib/libQt5XcbQpa.so.5 #23 0x7fa8315a981b in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0 #24 0x7fa8315ffec9 in ?? () from /usr/lib/libglib-2.0.so.0 #25 0x7fa8315a80d2 in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0 #26 0x7fa83340750c in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/libQt5Core.so.5 #27 0x7fa8333b532c in QEventLoop::exec(QFlags) () from /usr/lib/libQt5Core.so.5 #28 0x7fa8333bfe59 in QCoreApplication::exec() () from /usr/lib/libQt5Core.so.5 #29 0x55bb43bcdb65 in ?? () #30 0x7fa832d33290 in ?? () from /usr/lib/libc.so.6 #31 0x7fa832d3334a in __libc_start_main () from /usr/lib/libc.so.6 #32 0x55bb43bce425 in ?? () [Inferior 1 (process 503169) detached] The reporter indicates this bug may be a duplicate of or related to bug 313711, bug 369397, bug 381680, bug 382027, bug 411170, bug 460351. Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 446073] wrong mouse position when scaled inside SPICE virtual machine
https://bugs.kde.org/show_bug.cgi?id=446073 Damian Kaczmarek changed: What|Removed |Added CC||rus...@gmail.com --- Comment #3 from Damian Kaczmarek --- I have this problem too but weirdly enough the problem does not happen immediately after connecting the extra monitor, it appears to happen after I start using some apps. Not sure what exactly the trigger. kwin 5.25.5 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 446073] wrong mouse position when scaled inside SPICE virtual machine
https://bugs.kde.org/show_bug.cgi?id=446073 --- Comment #4 from Damian Kaczmarek --- Oh sorry I misread the title of the bug. The bug for me happens with my laptop having a 4k screen and me connecting a FullHD screen. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 458939] New: Info center crashes on start, but only once
https://bugs.kde.org/show_bug.cgi?id=458939 Bug ID: 458939 Summary: Info center crashes on start, but only once Product: systemsettings Version: 5.25.4 Platform: Archlinux Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: damian.hoes...@gmail.com Target Milestone: --- Application: systemsettings (5.25.4) Qt Version: 5.15.5 Frameworks Version: 5.97.0 Operating System: Linux 5.19.0-268-tkg-pds x86_64 Windowing System: X11 Distribution: RebornOS Linux DrKonqi: 5.25.4 [KCrashBackend] -- Information about the crash: I selected "CPU" in the start menu, but the info center crashed immediately on opening. The crash does not seem to be reproducible. -- Backtrace: Application: Info Center (systemsettings), signal: Aborted [KCrash Handler] #4 0x7f24ab00f4dc in ?? () from /usr/lib/libc.so.6 #5 0x7f24aafbf998 in raise () from /usr/lib/libc.so.6 #6 0x7f24aafa953d in abort () from /usr/lib/libc.so.6 #7 0x7f24ab00367e in ?? () from /usr/lib/libc.so.6 #8 0x7f24ab09e5da in __fortify_fail () from /usr/lib/libc.so.6 #9 0x7f24ab09e5a6 in __stack_chk_fail () from /usr/lib/libc.so.6 #10 0x7f24a940a92b in ?? () from /usr/lib/libQt5Qml.so.5 #11 0x7f24a9411e8b in QV4::QObjectWrapper::virtualResolveLookupGetter(QV4::Object const*, QV4::ExecutionEngine*, QV4::Lookup*) () from /usr/lib/libQt5Qml.so.5 #12 0x7f24a9426bea in ?? () from /usr/lib/libQt5Qml.so.5 #13 0x7f24a9430e34 in ?? () from /usr/lib/libQt5Qml.so.5 #14 0x7f24a93d47f6 in QV4::Function::call(QV4::Value const*, QV4::Value const*, int, QV4::ExecutionContext const*) () from /usr/lib/libQt5Qml.so.5 #15 0x7f24a9528e6d in QQmlJavaScriptExpression::evaluate(QV4::CallData*, bool*) () from /usr/lib/libQt5Qml.so.5 #16 0x7f24a94ec121 in QQmlBoundSignalExpression::evaluate(void**) () from /usr/lib/libQt5Qml.so.5 #17 0x7f24a94ed09c in ?? () from /usr/lib/libQt5Qml.so.5 #18 0x7f24a950f8cf in QQmlNotifier::emitNotify(QQmlNotifierEndpoint*, void**) () from /usr/lib/libQt5Qml.so.5 #19 0x7f24ab664da0 in ?? () from /usr/lib/libQt5Core.so.5 #20 0x7f24a99926d9 in ?? () from /usr/lib/libQt5Quick.so.5 #21 0x7f24a9993eb9 in QQuickItemView::setCurrentIndex(int) () from /usr/lib/libQt5Quick.so.5 #22 0x7f24a94d50c2 in ?? () from /usr/lib/libQt5Qml.so.5 #23 0x7f24a952a915 in ?? () from /usr/lib/libQt5Qml.so.5 #24 0x7f24a953208e in ?? () from /usr/lib/libQt5Qml.so.5 #25 0x7f24a9531b73 in QQmlBinding::update(QFlags) () from /usr/lib/libQt5Qml.so.5 #26 0x7f24a950f8cf in QQmlNotifier::emitNotify(QQmlNotifierEndpoint*, void**) () from /usr/lib/libQt5Qml.so.5 #27 0x7f24ab664da0 in ?? () from /usr/lib/libQt5Core.so.5 #28 0x7f249d956fc8 in ?? () from /usr/lib/qt/plugins/systemsettingsview/systemsettings_sidebar_mode.so #29 0x7f249d95846d in ?? () from /usr/lib/qt/plugins/systemsettingsview/systemsettings_sidebar_mode.so #30 0x7f249d958ba1 in ?? () from /usr/lib/qt/plugins/systemsettingsview/systemsettings_sidebar_mode.so #31 0x55d4da3c8bd0 in ?? () #32 0x55d4da3cbe24 in ?? () #33 0x7f24ab6582f0 in QObject::event(QEvent*) () from /usr/lib/libQt5Core.so.5 #34 0x7f24acb022ae in KXmlGuiWindow::event(QEvent*) () from /usr/lib/libKF5XmlGui.so.5 #35 0x7f24ac1bab3c in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib/libQt5Widgets.so.5 #36 0x7f24ab634978 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /usr/lib/libQt5Core.so.5 #37 0x7f24ab635483 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () from /usr/lib/libQt5Core.so.5 #38 0x7f24ab67b478 in ?? () from /usr/lib/libQt5Core.so.5 #39 0x7f24a9c7eb2b in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0 #40 0x7f24a9cd4e79 in ?? () from /usr/lib/libglib-2.0.so.0 #41 0x7f24a9c7c252 in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0 #42 0x7f24ab67f25c in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/libQt5Core.so.5 #43 0x7f24ab62d11c in QEventLoop::exec(QFlags) () from /usr/lib/libQt5Core.so.5 #44 0x7f24ab637c49 in QCoreApplication::exec() () from /usr/lib/libQt5Core.so.5 #45 0x55d4da3c2b7a in ?? () #46 0x7f24aafaa2d0 in ?? () from /usr/lib/libc.so.6 #47 0x7f24aafaa38a in __libc_start_main () from /usr/lib/libc.so.6 #48 0x55d4da3c34d5 in ?? () [Inferior 1 (process 17642) detached] Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 458111] New: Dolphin crash during transaction overwriting existing files from internal Btrfs RAID6 to USB HDD
https://bugs.kde.org/show_bug.cgi?id=458111 Bug ID: 458111 Summary: Dolphin crash during transaction overwriting existing files from internal Btrfs RAID6 to USB HDD Product: dolphin Version: 22.04.3 Platform: Archlinux Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: damian.hoes...@gmail.com CC: kfm-de...@kde.org Target Milestone: --- Application: dolphin (22.04.3) Qt Version: 5.15.5 Frameworks Version: 5.96.0 Operating System: Linux 5.19.0-268-tkg-pds x86_64 Windowing System: X11 Distribution: RebornOS Linux DrKonqi: 5.25.4 [KCrashBackend] -- Information about the crash: At the moment of the crash I just skimmed through some folders with many files in them. The reporter is unsure if this crash is reproducible. -- Backtrace: Application: Dolphin (dolphin), signal: Segmentation fault [KCrash Handler] #4 0x7f0e4b36a0ec in QWidgetPrivate::init(QWidget*, QFlags) () from /usr/lib/libQt5Widgets.so.5 #5 0x7f0e4b53fd23 in QDialog::QDialog(QWidget*, QFlags) () from /usr/lib/libQt5Widgets.so.5 #6 0x7f0e4c4483c1 in KIO::RenameDialog::RenameDialog(QWidget*, QString const&, QUrl const&, QUrl const&, QFlags, unsigned long long, unsigned long long, QDateTime const&, QDateTime const&, QDateTime const&, QDateTime const&) () from /usr/lib/libKF5KIOWidgets.so.5 #7 0x7f0e4c45b8c2 in KIO::WidgetsAskUserActionHandler::askUserRename(KJob*, QString const&, QUrl const&, QUrl const&, QFlags, unsigned long long, unsigned long long, QDateTime const&, QDateTime const&, QDateTime const&, QDateTime const&) () from /usr/lib/libKF5KIOWidgets.so.5 #8 0x7f0e4c1d9739 in ?? () from /usr/lib/libKF5KIOCore.so.5 #9 0x7f0e4a8fe341 in ?? () from /usr/lib/libQt5Core.so.5 #10 0x7f0e4ba5d23a in KJob::result(KJob*, KJob::QPrivateSignal) () from /usr/lib/libKF5CoreAddons.so.5 #11 0x7f0e4ba629bc in KJob::finishJob(bool) () from /usr/lib/libKF5CoreAddons.so.5 #12 0x7f0e4a8fe341 in ?? () from /usr/lib/libQt5Core.so.5 #13 0x7f0e4c20035a in KIO::SlaveInterface::dispatch(int, QByteArray const&) () from /usr/lib/libKF5KIOCore.so.5 #14 0x7f0e4c1fb5aa in KIO::SlaveInterface::dispatch() () from /usr/lib/libKF5KIOCore.so.5 #15 0x7f0e4c1fdcf2 in KIO::Slave::gotInput() () from /usr/lib/libKF5KIOCore.so.5 #16 0x7f0e4a8fe341 in ?? () from /usr/lib/libQt5Core.so.5 #17 0x7f0e4a8f1440 in QObject::event(QEvent*) () from /usr/lib/libQt5Core.so.5 #18 0x7f0e4b345b3c in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib/libQt5Widgets.so.5 #19 0x7f0e4a8cdad8 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /usr/lib/libQt5Core.so.5 #20 0x7f0e4a8ce5e3 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () from /usr/lib/libQt5Core.so.5 #21 0x7f0e4a914548 in ?? () from /usr/lib/libQt5Core.so.5 #22 0x7f0e4859dc6b in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0 #23 0x7f0e485f4001 in ?? () from /usr/lib/libglib-2.0.so.0 #24 0x7f0e4859b392 in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0 #25 0x7f0e4a91832c in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/libQt5Core.so.5 #26 0x7f0e4a8c627c in QEventLoop::exec(QFlags) () from /usr/lib/libQt5Core.so.5 #27 0x7f0e4a8d0da9 in QCoreApplication::exec() () from /usr/lib/libQt5Core.so.5 #28 0x5635f0ddeca9 in ?? () #29 0x7f0e4a2492d0 in ?? () from /usr/lib/libc.so.6 #30 0x7f0e4a24938a in __libc_start_main () from /usr/lib/libc.so.6 #31 0x5635f0ddf365 in ?? () [Inferior 1 (process 8906) detached] The reporter indicates this bug may be a duplicate of or related to bug 265809, bug 439542, bug 448532, bug 451566, bug 457856. Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 458038] New: Widgets become slightly misplaced (misaligned) after login
https://bugs.kde.org/show_bug.cgi?id=458038 Bug ID: 458038 Summary: Widgets become slightly misplaced (misaligned) after login Product: plasmashell Version: 5.25.4 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Desktop Containment Assignee: plasma-b...@kde.org Reporter: dcalv...@gmail.com CC: notm...@gmail.com Target Milestone: 1.0 Created attachment 151411 --> https://bugs.kde.org/attachment.cgi?id=151411&action=edit The yellow line shows the alignment position the widgets should have stayed aligned to SUMMARY When logging in, right before the task manager panel appears at the bottom, all the widgets shown on the screenshot are loaded first and they appear in their right positions, as set previously before rebooting/relogin. However right after the bottom task manager panel appears, they become misplaced or misaligned, almost as if they would seem to "jump" out of position. This is on the third screen/display. All three displays are one next to the other in an horizontal fashion, the widgets are placed in the one to my right side. STEPS TO REPRODUCE 1. Place widget to their desired positions. 2. Log off and login, or reboot and login. OBSERVED RESULT Observe the widgets become misplaced right after the bottom task manager is loaded. EXPECTED RESULT The widgets remain in their specified position as they were placed before rebooting. SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 5.25.4 KDE Frameworks Version: 5.97.0 Qt Version: 5.15.5 Kernel Version: 5.19.1-zen1-1-zen (64-bit) Graphics Platform: X11 Processors: 12 × Intel® Core™ i7-8700K CPU @ 3.70GHz Memory: 15.5 GiB of RAM Graphics Processor: NVIDIA GeForce GTX 1070/PCIe/SSE2 ADDITIONAL INFORMATION See screenshot. The yellow line shows the alignment position the widgets should have stayed aligned to. Also running 2 instances of conky for 2 information "panels". The widgets that become misplaced are mainly "System Monitor" widgets, but I also had this issue with an assortment of "Digital Clock" widgets that I had previously placed on that same screen showing the time on different cities, and the constant repositioning after a reboot required to make them useful was too frustrating so I just removed them. The widget's size is also slightly altered. Could be related to "425368", though there's very little information on that one. -- You are receiving this mail because: You are watching all bug changes.
[kalendar] [Bug 456157] Crash on dismissing a reminder
https://bugs.kde.org/show_bug.cgi?id=456157 Damian Dygulski changed: What|Removed |Added CC||ddygul...@fastmail.com -- You are receiving this mail because: You are watching all bug changes.
[kalendar] [Bug 456157] Crash on dismissing a reminder
https://bugs.kde.org/show_bug.cgi?id=456157 --- Comment #8 from Damian Dygulski --- Created attachment 150903 --> https://bugs.kde.org/attachment.cgi?id=150903&action=edit New crash information added by DrKonqi kalendarac (5.20.3) using Qt 5.15.5 The application crashes every time I dismiss an event notification -- Backtrace (Reduced): #4 _mm_packus_epi16(long long __vector(2), long long __vector(2)) (__B=, __A=) at /usr/lib64/gcc/x86_64-suse-linux/12/include/emmintrin.h:1000 #5 simdEncodeAscii (end=, src=, nextAscii=, dst=) at codecs/qutfcodec.cpp:90 #6 QUtf8::convertFromUnicode (uc=, len=32758) at codecs/qutfcodec.cpp:383 #7 0x7ff712d7bd95 in qt_convert_to_utf8 (str=...) at text/qstring.cpp:5380 #8 QString::toUtf8_helper (str=...) at text/qstring.cpp:5372 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 455323] Ugly margins around de-floated floating panel with any maximized windows
https://bugs.kde.org/show_bug.cgi?id=455323 Damian C changed: What|Removed |Added CC||dcalv...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 404306] [Wayland] Sometimes Dolphin disappears (no entry in plasma panel and task switcher) when I open file properties window despite its process is still running according to Ksysguar
https://bugs.kde.org/show_bug.cgi?id=404306 Damian Kaczmarek changed: What|Removed |Added Resolution|WORKSFORME |--- Status|RESOLVED|REOPENED CC||rus...@gmail.com --- Comment #5 from Damian Kaczmarek --- I had VS Code (running in Wayland mode) disappear for me after unlocking my desktop today. It's despite the processes being active in "ps aux". What's worse is that I cannot restart kwin_wayland as all processes will be killed. (I moved from X to Wayland 3 days ago) -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 456428] When the compositor crashes or restarts, all apps are killed
https://bugs.kde.org/show_bug.cgi?id=456428 --- Comment #2 from Damian Kaczmarek --- This is listed as a Plasma/Showstopper https://community.kde.org/Plasma/Wayland_Showstoppers under "KWin/compositing/window management ". If this is expected behavior perhaps somebody should edit it out? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 456428] New: When the compositor crashes or restarts, all apps are killed
https://bugs.kde.org/show_bug.cgi?id=456428 Bug ID: 456428 Summary: When the compositor crashes or restarts, all apps are killed Product: kwin Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: wayland-generic Assignee: kwin-bugs-n...@kde.org Reporter: rus...@gmail.com Target Milestone: --- STEPS TO REPRODUCE 1. Run "kwin_wayland --replace" or kill kwin_wayland or crash it OBSERVED RESULT All apps are killed. EXPECTED RESULT Apps survive the crash / restart of kwin_wayland ADDITIONAL INFORMATION I noticed there was no bug attached to this issue on this page https://community.kde.org/Plasma/Wayland_Showstoppers -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 432860] [wayland] tooltips appear in wrong place
https://bugs.kde.org/show_bug.cgi?id=432860 --- Comment #20 from Damian Kaczmarek --- Nate Graham can we reopen in case other users suffer from this issue? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 432860] [wayland] tooltips appear in wrong place
https://bugs.kde.org/show_bug.cgi?id=432860 --- Comment #19 from Damian Kaczmarek --- Created attachment 150457 --> https://bugs.kde.org/attachment.cgi?id=150457&action=edit Screen layout For reference, this is my screen layout. Not sure why the bug was marked as resolved when it's clearly not resolved. Just because the bug exists in mainstream doesn't mean the users do not suffer with this project. I personally think it's a very bad practice to close the issue in the actual project which is suffering. Upstream may not even care about the issue. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 432860] [wayland] tooltips appear in wrong place
https://bugs.kde.org/show_bug.cgi?id=432860 --- Comment #17 from Damian Kaczmarek --- Created attachment 150356 --> https://bugs.kde.org/attachment.cgi?id=150356&action=edit Screenshot of tooltip being in wrong place -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 432860] [wayland] tooltips appear in wrong place
https://bugs.kde.org/show_bug.cgi?id=432860 Damian Kaczmarek changed: What|Removed |Added Resolution|FIXED |--- CC||rus...@gmail.com Status|RESOLVED|REOPENED Version|5.22.0 |5.25.2 --- Comment #16 from Damian Kaczmarek --- I just switched to Wayland from X11 and encountered this issue on Plasma 5.25.2 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 443721] Keyboard repeat speed is ignored under wayland
https://bugs.kde.org/show_bug.cgi?id=443721 Damian Kaczmarek changed: What|Removed |Added CC||rus...@gmail.com --- Comment #18 from Damian Kaczmarek --- It's still broken for me on kwin 5.25.2. Are there any workarounds? I just switched from X11 to Wayland and the low repetition speed is hugely inconvenient. PS. otherwise the Wayland sessions seems pretty solid. Thanks KDE Team! -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 438345] Contents load as Blank Page in Wayland - Kmail and Akregator
https://bugs.kde.org/show_bug.cgi?id=438345 --- Comment #7 from Damian C --- (In reply to Damian C from comment #5) > Same, but with white screen instead of black. Presumably due to theming. > > Operating System: Arch Linux > KDE Plasma Version: 5.25.1 > KDE Frameworks Version: 5.95.0 > Qt Version: 5.15.5 > Kernel Version: 5.18.6-zen1-1-zen (64-bit) > Graphics Platform: Wayland > Processors: 12 × Intel® Core™ i7-8700K CPU @ 3.70GHz > Memory: 15.5 GiB of RAM > Graphics Processor: NVIDIA GeForce GTX 1070/PCIe/SSE2 I must clarify, that unlike the bug reporter, I do not get the same blank screen with the Feeds (Akregator), and the messages do load if I double click to open them in a new window. But I did not see them loading even after a while. The button in the middle of the panes, to switch from HTML to Plain Text, is also unresponsive using wayland, it simply does nothing. -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 438345] Contents load as Blank Page in Wayland - Kmail and Akregator
https://bugs.kde.org/show_bug.cgi?id=438345 Damian C changed: What|Removed |Added CC||dcalv...@gmail.com --- Comment #5 from Damian C --- Same, but with white screen instead of black. Presumably due to theming. Operating System: Arch Linux KDE Plasma Version: 5.25.1 KDE Frameworks Version: 5.95.0 Qt Version: 5.15.5 Kernel Version: 5.18.6-zen1-1-zen (64-bit) Graphics Platform: Wayland Processors: 12 × Intel® Core™ i7-8700K CPU @ 3.70GHz Memory: 15.5 GiB of RAM Graphics Processor: NVIDIA GeForce GTX 1070/PCIe/SSE2 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 385135] Monitor connection names differ across X11 and Wayland, causing multi-monitor containment mappings to break when switching session types
https://bugs.kde.org/show_bug.cgi?id=385135 Damian C changed: What|Removed |Added CC||dcalv...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 455538] New: Option to keep floating panels -floating- when windows are maximized
https://bugs.kde.org/show_bug.cgi?id=455538 Bug ID: 455538 Summary: Option to keep floating panels -floating- when windows are maximized Product: plasmashell Version: 5.25.0 Platform: Other OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: Panel Assignee: plasma-b...@kde.org Reporter: dcalv...@gmail.com CC: niccolo.venera...@gmail.com Target Milestone: 1.0 Created attachment 149885 --> https://bugs.kde.org/attachment.cgi?id=149885&action=edit example of the "desired" result but with a non maximized window SUMMARY *** Normally when using a floating panel, maximizing a window and having the floating panel become a "normal" (ie, non floating) panel makes sense as it would look ugly and incoherent with the maximized window. However I'm using the "Maximized Window Gap" Kwin Script, and with it my maximized windows have a gap around them, and when these windows are not maximized (but taking the same space as the maximized window) it looks like both the window and the panel are floating over the background and to me it looks quite cool. However when I maximize any window while using the kwin script and the floating panel, the panel acts as it was designed to and becomes "non floating", thus breaking the look of both elements (the window, and the panel) floating. I know this is probably quite a niche scenario, but I'd love to have such option. Something similar but not quite the same has been requested under bug #454950. It will make more sense with the screenshot, which shows more or less an example of the "desired" result but with a non maximized window, which doesn't look quite exactly right as I basically had to set the window size manually to more or less match what it looks like when maximized with the kwin script enable, but it will surely illustrate the point. *** STEPS TO REPRODUCE 1. Enable Floating Panel. 2. Be using Kwin Script "Maximized Window Gap" 3. Maximize a window. OBSERVED RESULT The floating panel becomes a "normal" panel and docks to the bottom of the screen. EXPECTED RESULT That the floating panel remains floating the same as if there was no maximized window. SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 5.25.0 KDE Frameworks Version: 5.95.0 Qt Version: 5.15.4 Kernel Version: 5.18.3-zen1-1-zen (64-bit) Graphics Platform: X11 Processors: 12 × Intel® Core™ i7-8700K CPU @ 3.70GHz Memory: 15.5 GiB of RAM Graphics Processor: NVIDIA GeForce GTX 1070/PCIe/SSE2 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 452152] New: Mouse acceleration profile changes after reconnecting the mouse device
https://bugs.kde.org/show_bug.cgi?id=452152 Bug ID: 452152 Summary: Mouse acceleration profile changes after reconnecting the mouse device Product: systemsettings Version: 5.24.3 Platform: Manjaro OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: kcm_mouse Assignee: plasma-b...@kde.org Reporter: damian-...@o2.pl Target Milestone: --- SUMMARY I normally use flat acceleration profile for my mouse setup. After I switch my mouse to another device (using kvm switch) and return to this one I have flat acceleration profile selected even though mouse feels like adaptive. After switching to adaptive I feel no difference so I guess it is selected by default after reconnecting the mouse. My temporary solution to this problem is switching to adaptive and then again to flat. STEPS TO REPRODUCE 1. Normal system startup with flat acceleration profile 2. Disconnect mouse (eg. via kvm switch) 3. Reconnect mouse OBSERVED RESULT Acceleration profile: flat is still selected, but adaptive is in use So to fix the problem I have to select adaptive -> apply (nothing changes) -> select flat -> apply (fixed) EXPECTED RESULT Acceleration profile: flat selected and in use (or at least adaptive selected) SOFTWARE/OS VERSIONS Linux/KDE Plasma: Manjaro Linux KDE Plasma Version: 5.24.3 KDE Frameworks Version: 5.91.0 Qt Version: 5.15.3 -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 451408] File preview on local drives uses remote preview settings
https://bugs.kde.org/show_bug.cgi?id=451408 Damian changed: What|Removed |Added Status|NEEDSINFO |REPORTED Resolution|WAITINGFORINFO |--- --- Comment #6 from Damian --- My mounted NTFS is on sdc1 and sdb1 proc on /proc type proc (rw,nosuid,nodev,noexec,relatime) sys on /sys type sysfs (rw,nosuid,nodev,noexec,relatime) dev on /dev type devtmpfs (rw,nosuid,relatime,size=8150480k,nr_inodes=2037620,mode=755,inode64) run on /run type tmpfs (rw,nosuid,nodev,relatime,mode=755,inode64) efivarfs on /sys/firmware/efi/efivars type efivarfs (rw,nosuid,nodev,noexec,relatime) /dev/nvme0n1p6 on / type ext4 (rw,noatime) [...] /dev/sdc1 on /commonDisks/F type fuseblk (rw,nosuid,nodev,relatime,user_id=0,group_id=0,default_permissions,allow_other,blksize=4096) /dev/sdb1 on /commonDisks/G type fuseblk (rw,nosuid,nodev,relatime,user_id=0,group_id=0,default_permissions,allow_other,blksize=4096) [...] -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 451408] File preview on local drives uses remote preview settings
https://bugs.kde.org/show_bug.cgi?id=451408 --- Comment #2 from Damian --- I have connected another drive with ext4 fs and i can see previews on it, so I guess its a NTFS problem? -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 451408] New: File preview on local drives uses remote preview settings
https://bugs.kde.org/show_bug.cgi?id=451408 Bug ID: 451408 Summary: File preview on local drives uses remote preview settings Product: dolphin Version: 21.12.2 Platform: Manjaro OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: view-engine: general Assignee: dolphin-bugs-n...@kde.org Reporter: damian-...@o2.pl CC: kfm-de...@kde.org Target Milestone: --- SUMMARY Previews of files on local drives (other than OS drive) are managed by remote file preview settings. After recent updates, local drives (connected via SATA) use remote settings for local files which forces me to set very high limit on remote settings. STEPS TO REPRODUCE 1. Mount local drives via fstab on startup 2. Open dolphin on any drive other than OS drive 3. No previews are available (I have no previews for remote files by default) OBSERVED RESULT No previews for files on local drives, because of the use of remote preview settings. EXPECTED RESULT Files on local drives should use settings for local files SOFTWARE/OS VERSIONS Linux/KDE Plasma: Manjaro Linux KDE Plasma Version: 5.24.2 KDE Frameworks Version: 5.91.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION Happened after recent full system update -- You are receiving this mail because: You are watching all bug changes.
[trojita] [Bug 432353] Untagged responses are processed before STARTTLS.
https://bugs.kde.org/show_bug.cgi?id=432353 --- Comment #7 from Damian Poddebniak <93s4m32gd2ab8...@mailbox.org> --- Hehe, the code at https://github.com/KDE/trojita/blob/master/src/Imap/Parser/Command.cpp#L71 seems familiar :-) `PartOfCommand` cannot contain a ", right? -- You are receiving this mail because: You are watching all bug changes.
[trojita] [Bug 432353] Untagged responses are processed before STARTTLS.
https://bugs.kde.org/show_bug.cgi?id=432353 --- Comment #5 from Damian Poddebniak <93s4m32gd2ab8...@mailbox.org> --- Hey Jan, thank you for working on this issue! > This cannot be exploited like that. I know of at least one client where this is practically exploitable. However, I am not saying that it is possible in Trojita, though! > Since IMAP is a text-based protocol, there are rules on how to "intervene" > user-controlled (or even attacker-controlled) strings with protocol commands. > However, this is not specific to a possible side-channel injection due to > STARTTLS. The real user can just as well create a mailbox which has a newline > in its name, and the IMAP code must handle this properly. Let's not call this > "sanitization", please; it's a critical part of implementing a protocol. I fully agree. Sanitization is not the correct term. By the way, I know that you implemented the IMAP protocol very diligently in Trojita! ;-) Still, I also know IMAP very well and how complicated string handling is due to the many involved "string types" such as `tag`, `text`, `atom`, `astring`, `literal` ... (In fact, in my own IMAP implementation I was *so afraid* to forget to correctly encode some string in some place, that I wrapped all "string types" and use these wrappers throughout the whole library.¹) > The STARTTLS vulnerability will only be relevant in this context if the > attacker-controlled cache stored strings which are somehow escaped, and that > is not the case. Not sure if I understand that. But it doesn't matter. If Trojita implements the IMAP protocol correctly and properly escapes folder names, it should not matter. ¹ https://github.com/duesee/imap-codec/blob/6bf1e5d0da45d576bd9ed4ddc0b3640da8e2ba80/src/types/mailbox.rs#L142 -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 427069] [wayland] Krunner starts on the most left screen.
https://bugs.kde.org/show_bug.cgi?id=427069 Damian Kaczmarek changed: What|Removed |Added CC||rus...@gmail.com --- Comment #8 from Damian Kaczmarek --- Couldn't kwin track the current active screen and expose it via dbus? No need for any super complicated solution -- You are receiving this mail because: You are watching all bug changes.
[yakuake] [Bug 440825] open at mouse location not working under Wayland
https://bugs.kde.org/show_bug.cgi?id=440825 Damian Kaczmarek changed: What|Removed |Added Ever confirmed|0 |1 Status|REPORTED|CONFIRMED --- Comment #7 from Damian Kaczmarek --- *** This bug has been confirmed by popular vote. *** -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 445176] New: Thumbnails generate very slow. Use all CPU cores to generate them fast.
https://bugs.kde.org/show_bug.cgi?id=445176 Bug ID: 445176 Summary: Thumbnails generate very slow. Use all CPU cores to generate them fast. Product: gwenview Version: unspecified Platform: unspecified OS: All Status: REPORTED Severity: wishlist Priority: NOR Component: general Assignee: gwenview-bugs-n...@kde.org Reporter: ofe...@nowaker.net Target Milestone: --- Created attachment 143349 --> https://bugs.kde.org/attachment.cgi?id=143349&action=edit CPU usage 100% of a single core. SUMMARY I have a modern rig. My disks are PCIE with 4 GB/s read speed. My CPU is 10900K with 20 cores. Thumbnails should generate fast but currently they don't because Gwenview doesn't take advantage of multi-core processing. STEPS TO REPRODUCE 1. Have modern hardware like Intel 10900K or AMD 5900X, and NVME 2TB/s+ disk. 2. Have a directory with hundreds of pictures that are 12-20 MP each. 3. Open the directory in thumbnail view. OBSERVED RESULT Thumbnails show up slowly, roughly at a rate of 10 thumbnails per second. IO reads are low (max at around 100 MB/s). Far from the maximum. CPU usage of Gwenview is 100% of a single core. This means thumbnail generation speed is capped by the speed of a single core. EXPECTED RESULT Use all the compute power available to Gwenview by using all available cores to generate thumbnails. SOFTWARE/OS VERSIONS N/A ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
