[kwin] [Bug 448866] [NVIDIA] Graphical glitches and unresponsive after waking from sleep
https://bugs.kde.org/show_bug.cgi?id=448866 --- Comment #10 from Dennis --- I have also experienced this issue described my duplicate bug 473819, which was from a fresh install this weekend (27/8). The difference to me is that I doesn't put my computer to sleep, only the monitors when inactive for too long. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 473804] When Global Menu is used I can't open Google Chrome browser in incognito mode
https://bugs.kde.org/show_bug.cgi?id=473804 --- Comment #2 from Peter Ries --- Thanks, Nate. I opened a bug report here ( https://bugs.chromium.org/p/chromium/issues/detail?id=1476753 ) -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 473807] Plasma is initializing a new display output when restarting monitor
https://bugs.kde.org/show_bug.cgi?id=473807 --- Comment #2 from Fahim Shahriar --- (In reply to Nate Graham from comment #1) > When this happens, are your display settings also reset? e.g. display > resolution, scale, refresh rate, position, etc? > > Or are all of those settings remembered, and the problem is that there's a > spike in system load that causes other issues? I've tried applying different resolution and refresh rate and seems like all of the settings are remembered, they aren't resetting. And no, I don't see any spike in system load. -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 473879] Preview when using rectangular region offset to the right.
https://bugs.kde.org/show_bug.cgi?id=473879 --- Comment #1 from Tim Offereins --- Created attachment 161253 --> https://bugs.kde.org/attachment.cgi?id=161253=edit Display Configuration -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 473879] New: Preview when using rectangular region offset to the right.
https://bugs.kde.org/show_bug.cgi?id=473879 Bug ID: 473879 Summary: Preview when using rectangular region offset to the right. Classification: Applications Product: Spectacle Version: 23.08.0 Platform: Archlinux OS: Linux Status: REPORTED Severity: major Priority: NOR Component: General Assignee: noaha...@gmail.com Reporter: t...@el1x.com CC: k...@david-redondo.de Target Milestone: --- Created attachment 161252 --> https://bugs.kde.org/attachment.cgi?id=161252=edit Preview Issue SUMMARY When attempting to use the rectangular region tool and take a screenshot of a specific area the 'preview' is offset to the right when in a multiple monitor setup. Specifically, this is when the primary display is in the middle (I have 3) and there is a secondary display to the left. This issue does not occur when the additional display is to the right only, nor in single display instances. STEPS TO REPRODUCE 1. Setup multiple monitors with the secondary display set to the left. 2. Attempt to use rectangular region tool OBSERVED RESULT Preview is offset making it very difficult to take accurate screenshots using the rectangular region tool. Please excuse the photo of the display, it was the quickest and easier thing to do to show the issue at the time. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Kernel 6.4.12 (available in About System) KDE Plasma Version: 5.27.7 KDE Frameworks Version: 5.109.0 Qt Version: 5.15.10 ADDITIONAL INFORMATION X11 Laptop with 2 external monitors Left: 1440x2560 (portrait) Mid: 3840x2160 (primary) Right: 1920x1080 (internal display) -- You are receiving this mail because: You are watching all bug changes.
[KClock] [Bug 473766] KClock sidebar does not detect the stylus clicks of my graphic tablet
https://bugs.kde.org/show_bug.cgi?id=473766 hanyo...@protonmail.com changed: What|Removed |Added Ever confirmed|0 |1 Status|REPORTED|CONFIRMED --- Comment #1 from hanyo...@protonmail.com --- Can confirm, on my Ace spin5, stylus doesn't work but touch screen does. However, on KDE Framework 6 build, both works correctly. So I think this bug has already been addressed. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 465465] Eviction Emulation in Cachegrind for Detecting Cache Conflicts
https://bugs.kde.org/show_bug.cgi?id=465465 --- Comment #15 from Nick Nethercote --- The existing cache and branch simulations are very simplistic, and about 20 years out of date. I think hardware counters are a much better way of getting cache statistics. I recently made `--cache-sim=no` the default for this reason. I understand that the statistics you've added aren't available via hardware counters. But still I worry that using an unrealistic simulation as the foundation could lead to inaccurate results. Another thing: in the example output file you have lines like these: > 4,496,605,023 (51.80%) 47,791,341,277 (5545.9%) 127,816 (2819.7%) 147,917 > (23112.0%) 73,046 (1014.2%) 154,413 (203.7%) 8,192 (51.35%) > binary_search_test The percentages in the all the new columns (everything other than `Ir`) greatly exceed 100%, which seems wrong. -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 473877] KDE Panel (Windows can cover) bugs due to mouse behaviour
https://bugs.kde.org/show_bug.cgi?id=473877 --- Comment #1 from kde-bugs.m3...@slmail.me --- Additional info about the panel behaviour with the mouse and why it should be an option (opt-out option) My (and probably others) expected behaviour was "fixed" and removed for this user (and probably others): https://bugs.kde.org/show_bug.cgi?id=398439 https://invent.kde.org/plasma/plasma-workspace/-/merge_requests/176 It is the default behaviour when the panel is on auto-hide, which is why it should be an opt-out to remove the mouse triggering the panel showing. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 473878] New: System Settings Crash when opening Application Appearance Settings
https://bugs.kde.org/show_bug.cgi?id=473878 Bug ID: 473878 Summary: System Settings Crash when opening Application Appearance Settings Classification: Applications Product: systemsettings Version: 5.27.7 Platform: unspecified OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: alpha.c...@grid.cx Target Milestone: --- Application: systemsettings (5.27.7) Qt Version: 5.15.10 Frameworks Version: 5.109.0 Operating System: Linux 6.4.10-arch1-1 x86_64 Windowing System: X11 Distribution: "Arch Linux" DrKonqi: 5.27.7 [KCrashBackend] -- Information about the crash: System Settings Crash when opening Application Appearance Settings The crash can be reproduced every time. -- Backtrace: Application: System Settings (systemsettings), signal: Aborted [KCrash Handler] #4 0x7f251528e83c in () at /usr/lib/libc.so.6 #5 0x7f251523e668 in raise () at /usr/lib/libc.so.6 #6 0x7f25152264b8 in abort () at /usr/lib/libc.so.6 #7 0x7f2515aa0098 in qt_assert(char const*, char const*, int) () at /usr/lib/libQt5Core.so.5 #8 0x7f2515ac6d78 in () at /usr/lib/libQt5Core.so.5 #9 0x7f24e3460fc4 in () at /usr/lib/qt/plugins/styles/libqgtk2style.so #10 0x7f25169e6f94 in QStyleFactory::create(QString const&) () at /usr/lib/libQt5Widgets.so.5 #11 0x7f2504c25189 in () at /usr/lib/qt/plugins/plasma/kcms/systemsettings/kcm_style.so #12 0x7f2513aa6a81 in QQmlObjectCreator::finalize(QQmlInstantiationInterrupt&) () at /usr/lib/libQt5Qml.so.5 #13 0x7f2513a4c87f in QQmlIncubatorPrivate::incubate(QQmlInstantiationInterrupt&) () at /usr/lib/libQt5Qml.so.5 #14 0x7f2513a4d226 in QQmlEnginePrivate::incubate(QQmlIncubator&, QQmlContextData*) () at /usr/lib/libQt5Qml.so.5 #15 0x7f2510e84982 in () at /usr/lib/libQt5QmlModels.so.5 #16 0x7f25140fb6e9 in () at /usr/lib/libQt5Quick.so.5 #17 0x7f25140e9c2a in () at /usr/lib/libQt5Quick.so.5 #18 0x7f25140faf49 in () at /usr/lib/libQt5Quick.so.5 #19 0x7f25140fd2b1 in () at /usr/lib/libQt5Quick.so.5 #20 0x7f251404a09a in QQuickWindowPrivate::polishItems() () at /usr/lib/libQt5Quick.so.5 #21 0x7f25140dd754 in QQuickRenderControl::polishItems() () at /usr/lib/libQt5Quick.so.5 #22 0x7f2514bc3f28 in () at /usr/lib/libQt5QuickWidgets.so.5 #23 0x7f2514bc566f in QQuickWidget::timerEvent(QTimerEvent*) () at /usr/lib/libQt5QuickWidgets.so.5 #24 0x7f2515cc40ee in QObject::event(QEvent*) () at /usr/lib/libQt5Core.so.5 #25 0x7f251697893f in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /usr/lib/libQt5Widgets.so.5 #26 0x7f2515c9c6f8 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /usr/lib/libQt5Core.so.5 #27 0x7f2515cead6b in QTimerInfoList::activateTimers() () at /usr/lib/libQt5Core.so.5 #28 0x7f2515ceb3a2 in () at /usr/lib/libQt5Core.so.5 #29 0x7f251470fa31 in g_main_context_dispatch () at /usr/lib/libglib-2.0.so.0 #30 0x7f251476ccc9 in () at /usr/lib/libglib-2.0.so.0 #31 0x7f251470d0e2 in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #32 0x7f2515ceb51c in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #33 0x7f2515c9b404 in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #34 0x7f2515c9c8a3 in QCoreApplication::exec() () at /usr/lib/libQt5Core.so.5 #35 0x55d929168bd9 in () #36 0x7f2515227cd0 in () at /usr/lib/libc.so.6 #37 0x7f2515227d8a in __libc_start_main () at /usr/lib/libc.so.6 #38 0x55d929169575 in () [Inferior 1 (process 193322) detached] Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 473877] New: KDE Panel (Windows can cover) bugs due to mouse behaviour
https://bugs.kde.org/show_bug.cgi?id=473877 Bug ID: 473877 Summary: KDE Panel (Windows can cover) bugs due to mouse behaviour Classification: I don't know Product: kde Version: unspecified Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: kde-bugs.m3...@slmail.me Target Milestone: --- SUMMARY Because of the forced behaviour of showing the panel when the mouse over toward the edge of the screen (where the panel is), it add bug (with screen edge functionality) and unwanted behaviour (unwanted by me at least and it can't be disabled) - If the panel is at the top of the screen (set as windows can cover), The screen Edges behaviour do not work as expected (the mouse need to be moved twice to the location to get the behaviour instead of once. - The panel should have an option to disable its showing when the mouse get close to its location. it can be very unwanted to have the panel showing when trying to access the tabs of a maximised browser windows for examples. - Removing the top screen edge behaviour make the panel work as wanted (not showing up with the mouse) until I forced it shown (keyboard shortcut). STEPS TO REPRODUCE 1. Start a wayland session (not tested on x11 yet) 2. Set your panel to the top of the screen (any size) 3. Set you panel to "windows can cover" 4. Hide title bars and boders 5. Open a web browser and maximize the window. -> Window does cover the panel as expected. 6. Move your mouse at the top to access the edge of the window -> Panel shows up (undesired for some, an option should be available to disable it) 7. Mouse your mouse away -> Panel does not hide (focus is still on the browser window, that whdow should be on top of the panel) https://bugs.kde.org/show_bug.cgi?id=453373 8. must click away from the panel to hide it (when really may have just wanted to click on a new tab) 9. In workspace behaviour, activate any/all the top screen edges behaviour (any behaviours) 10. move your mouse (once) where you expect the behaviour to be triggered -> Panel shows up, but behaviour is not happening 11. Move your mouse again to the same place -> Behaviour is happening 13. Click away from the panel so it hides 12. Disable the screen behaviour 13. mouve you mouse top of the screen -> panel is not showing up (finally a wanted behaviour, but unconsistent with previous one) 14. Show the panel (keyboard binding) 15. Back at step 6. OBSERVED RESULT - No options to disable the edge of the screen where the panel is at triggering the panel showing. - Screen Edges triggers not triggered well - panel get in the way when the option is to make it not be in the way EXPECTED RESULT - Option to disable the mouse triggering the showing of the mouse (I understand it may be a desired behaviour for some and a more natural behaviour, hence an opt-out option). - Screen Edges triggers should be as snappy as when the panel is always visible. - Panel should stay out of the way if the user set it so. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Fedora 38 Kernel 6.4.12-200.fc38.x86_64 (64-bit) (available in About System) KDE Plasma Version: 5.27.7 KDE Frameworks Version: 5.109.0 Qt Version: 5.15.10 ADDITIONAL INFORMATION - I believe those bugs are caused by the forced behaviour of showing the panel when the mouse get the screen edge. - It is hard for a non experienced user to decide which application of kde-plasma does the panel comes under (search result for panel on that selection showed no result. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 473665] Kwin-wayland crashed (after reboot) when connecting a second high-dpi monitor
https://bugs.kde.org/show_bug.cgi?id=473665 --- Comment #10 from landgraf...@yandex.ru --- (In reply to Landgraf132 from comment #9) > (In reply to Nate Graham from comment #8) > > Can you follow the instructions at > > https://community.kde.org/Guidelines_and_HOWTOs/Debugging/ > > How_to_create_useful_crash_reports#Retrieving_a_backtrace_using_coredumpctl > > to get a backtrace for us? > > Core was generated by `/usr/bin/kwin_wayland --wayland-fd 7 --socket > wayland-0 --xwayland-fd 8 --xwayl'. > Program terminated with signal SIGABRT, Aborted. > #0 __pthread_kill_implementation (no_tid=0, signo=6, > threadid=139799600261568) at ./nptl/pthread_kill.c:44 > 44 ./nptl/pthread_kill.c: No such file or directory. > [Current thread is 1 (Thread 0x7f25a18369c0 (LWP 2293))] > (gdb) > (gdb) bt > #0 __pthread_kill_implementation (no_tid=0, signo=6, > threadid=139799600261568) at ./nptl/pthread_kill.c:44 > #1 __pthread_kill_internal (signo=6, threadid=139799600261568) at > ./nptl/pthread_kill.c:78 > #2 __GI___pthread_kill (threadid=139799600261568, signo=signo@entry=6) at > ./nptl/pthread_kill.c:89 > #3 0x7f25a5642476 in __GI_raise (sig=sig@entry=6) at > ../sysdeps/posix/raise.c:26 > #4 0x7f25a56287f3 in __GI_abort () at ./stdlib/abort.c:79 > #5 0x7f25a758bcaa in () at /lib/x86_64-linux-gnu/libepoxy.so.0 > #6 0x7f25a758f54a in () at /lib/x86_64-linux-gnu/libepoxy.so.0 > #7 0x7f25a862acc7 in KWin::EglDmabufBuffer::removeImages() > (this=0x56194ccb86f0) at > ./src/platformsupport/scenes/opengl/egl_dmabuf.cpp:131 > #8 0x7f25a862cb19 in KWin::EglDmabuf::~EglDmabuf() > (this=0x56194c964760, this=) at > ./src/platformsupport/scenes/opengl/egl_dmabuf.cpp:227 > #9 0x7f25a862e081 in KWin::EglDmabuf::~EglDmabuf() > (this=0x56194c964760, this=) at > ./src/platformsupport/scenes/opengl/egl_dmabuf.cpp:222 > #10 KWin::AbstractEglBackend::~AbstractEglBackend() (this=0x56194c62cbd0, > this=) at > ./src/platformsupport/scenes/opengl/abstract_egl_backend.cpp:53 > #11 0x7f25a85705fd in KWin::EglGbmBackend::~EglGbmBackend() > (this=0x56194c62cbd0, this=) at > ./src/backends/drm/drm_egl_backend.cpp:61 > #12 0x7f25a83bfd66 in > std::default_delete::operator()(KWin::RenderBackend*) > const (__ptr=, this=) at > /usr/include/c++/11/bits/unique_ptr.h:79 > #13 std::__uniq_ptr_impl std::default_delete >::reset(KWin::RenderBackend*) > (__p=0x0, this=0x56194c6e2ca8) at /usr/include/c++/11/bits/unique_ptr.h:182 > #14 std::unique_ptr std::default_delete >::reset(KWin::RenderBackend*) > (__p=0x0, this=0x56194c6e2ca8) at /usr/include/c++/11/bits/unique_ptr.h:456 > #15 KWin::Compositor::stop() (this=0x56194c6e2c30) at ./src/composite.cpp:557 > #16 KWin::Compositor::stop() (this=0x56194c6e2c30) at ./src/composite.cpp:505 > #17 0x7f25a83b8989 in KWin::Compositor::reinitialize() > (this=0x56194c6e2c30) at ./src/composite.cpp:628 > #18 0x7f25a68f48f4 in QtPrivate::QSlotObjectBase::call(QObject*, void**) > (a=0x7fffb191cd70, r=0x56194c6e2c30, this=0x56194c6c52f0) at > ../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398 > #19 doActivate(QObject*, int, void**) (sender=0x56194c651fa0, > signal_index=61, argv=0x7fffb191cd70) at kernel/qobject.cpp:3925 > #20 0x7f25a850d6f3 in KWin::Workspace::slotReconfigure() > (this=0x56194c99f580) at ./src/workspace.cpp:1017 > #21 0x7f25a68f48f4 in QtPrivate::QSlotObjectBase::call(QObject*, void**) > (a=0x7fffb191cf20, r=0x56194c99f580, this=0x56194ca4aa50) at > ../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398 > #22 doActivate(QObject*, int, void**) (sender=0x56194c99f6c0, > signal_index=3, argv=0x7fffb191cf20) at kernel/qobject.cpp:3925 > #23 0x7f25a68ed9c7 in QMetaObject::activate(QObject*, QMetaObject > const*, int, void**) (sender=, m=m@entry=0x7f25a6b5d2e0 > , local_signal_index=local_signal_index@entry=0, > argv=argv@entry=0x7fffb191cf20) at kernel/qobject.cpp:3985 > #24 0x7f25a68f897e in QTimer::timeout(QTimer::QPrivateSignal) > (this=, _t1=...) at .moc/moc_qtimer.cpp:205 > #25 0x7f25a68ea2bf in QObject::event(QEvent*) (this=0x56194c99f6c0, > e=0x7fffb191d0a0) at kernel/qobject.cpp:1369 > #26 0x7f25a5f6c763 in QApplicationPrivate::notify_helper(QObject*, > QEvent*) (this=, receiver=0x56194c99f6c0, e=0x7fffb191d0a0) > at kernel/qapplication.cpp:3640 > #27 0x7f25a68bce4a in QCoreApplication::notifyInternal2(QObject*, > QEvent*) (receiver=0x56194c99f6c0, event=0x7fffb191d0a0) at > kernel/qcoreapplication.cpp:1064 > #28 0x7f25a691566b in QTimerInfoList::activateTimers() > (this=this@entry=0x56194c623718) at kernel/qtimerinfo_unix.cpp:643 > #29 0x7f25a6912dd0 in QEventDispatcherUNIXPrivate::activateTimers() > (this=this@entry=0x56194c623690) at kernel/qeventdispatcher_unix.cpp:249 > #30 0x7f25a6913b27 in > QEventDispatcherUNIX::processEvents(QFlags) > (this=, flags=...) at kernel/qeventdispatcher_unix.cpp:516 > #31 0x56194b4513b1 in >
[kwin] [Bug 473665] Kwin-wayland crashed (after reboot) when connecting a second high-dpi monitor
https://bugs.kde.org/show_bug.cgi?id=473665 --- Comment #9 from landgraf...@yandex.ru --- (In reply to Nate Graham from comment #8) > Can you follow the instructions at > https://community.kde.org/Guidelines_and_HOWTOs/Debugging/ > How_to_create_useful_crash_reports#Retrieving_a_backtrace_using_coredumpctl > to get a backtrace for us? Core was generated by `/usr/bin/kwin_wayland --wayland-fd 7 --socket wayland-0 --xwayland-fd 8 --xwayl'. Program terminated with signal SIGABRT, Aborted. #0 __pthread_kill_implementation (no_tid=0, signo=6, threadid=139799600261568) at ./nptl/pthread_kill.c:44 44 ./nptl/pthread_kill.c: No such file or directory. [Current thread is 1 (Thread 0x7f25a18369c0 (LWP 2293))] (gdb) (gdb) bt #0 __pthread_kill_implementation (no_tid=0, signo=6, threadid=139799600261568) at ./nptl/pthread_kill.c:44 #1 __pthread_kill_internal (signo=6, threadid=139799600261568) at ./nptl/pthread_kill.c:78 #2 __GI___pthread_kill (threadid=139799600261568, signo=signo@entry=6) at ./nptl/pthread_kill.c:89 #3 0x7f25a5642476 in __GI_raise (sig=sig@entry=6) at ../sysdeps/posix/raise.c:26 #4 0x7f25a56287f3 in __GI_abort () at ./stdlib/abort.c:79 #5 0x7f25a758bcaa in () at /lib/x86_64-linux-gnu/libepoxy.so.0 #6 0x7f25a758f54a in () at /lib/x86_64-linux-gnu/libepoxy.so.0 #7 0x7f25a862acc7 in KWin::EglDmabufBuffer::removeImages() (this=0x56194ccb86f0) at ./src/platformsupport/scenes/opengl/egl_dmabuf.cpp:131 #8 0x7f25a862cb19 in KWin::EglDmabuf::~EglDmabuf() (this=0x56194c964760, this=) at ./src/platformsupport/scenes/opengl/egl_dmabuf.cpp:227 #9 0x7f25a862e081 in KWin::EglDmabuf::~EglDmabuf() (this=0x56194c964760, this=) at ./src/platformsupport/scenes/opengl/egl_dmabuf.cpp:222 #10 KWin::AbstractEglBackend::~AbstractEglBackend() (this=0x56194c62cbd0, this=) at ./src/platformsupport/scenes/opengl/abstract_egl_backend.cpp:53 #11 0x7f25a85705fd in KWin::EglGbmBackend::~EglGbmBackend() (this=0x56194c62cbd0, this=) at ./src/backends/drm/drm_egl_backend.cpp:61 #12 0x7f25a83bfd66 in std::default_delete::operator()(KWin::RenderBackend*) const (__ptr=, this=) at /usr/include/c++/11/bits/unique_ptr.h:79 #13 std::__uniq_ptr_impl >::reset(KWin::RenderBackend*) (__p=0x0, this=0x56194c6e2ca8) at /usr/include/c++/11/bits/unique_ptr.h:182 #14 std::unique_ptr >::reset(KWin::RenderBackend*) (__p=0x0, this=0x56194c6e2ca8) at /usr/include/c++/11/bits/unique_ptr.h:456 #15 KWin::Compositor::stop() (this=0x56194c6e2c30) at ./src/composite.cpp:557 #16 KWin::Compositor::stop() (this=0x56194c6e2c30) at ./src/composite.cpp:505 #17 0x7f25a83b8989 in KWin::Compositor::reinitialize() (this=0x56194c6e2c30) at ./src/composite.cpp:628 #18 0x7f25a68f48f4 in QtPrivate::QSlotObjectBase::call(QObject*, void**) (a=0x7fffb191cd70, r=0x56194c6e2c30, this=0x56194c6c52f0) at ../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398 #19 doActivate(QObject*, int, void**) (sender=0x56194c651fa0, signal_index=61, argv=0x7fffb191cd70) at kernel/qobject.cpp:3925 #20 0x7f25a850d6f3 in KWin::Workspace::slotReconfigure() (this=0x56194c99f580) at ./src/workspace.cpp:1017 #21 0x7f25a68f48f4 in QtPrivate::QSlotObjectBase::call(QObject*, void**) (a=0x7fffb191cf20, r=0x56194c99f580, this=0x56194ca4aa50) at ../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398 #22 doActivate(QObject*, int, void**) (sender=0x56194c99f6c0, signal_index=3, argv=0x7fffb191cf20) at kernel/qobject.cpp:3925 #23 0x7f25a68ed9c7 in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) (sender=, m=m@entry=0x7f25a6b5d2e0 , local_signal_index=local_signal_index@entry=0, argv=argv@entry=0x7fffb191cf20) at kernel/qobject.cpp:3985 #24 0x7f25a68f897e in QTimer::timeout(QTimer::QPrivateSignal) (this=, _t1=...) at .moc/moc_qtimer.cpp:205 #25 0x7f25a68ea2bf in QObject::event(QEvent*) (this=0x56194c99f6c0, e=0x7fffb191d0a0) at kernel/qobject.cpp:1369 #26 0x7f25a5f6c763 in QApplicationPrivate::notify_helper(QObject*, QEvent*) (this=, receiver=0x56194c99f6c0, e=0x7fffb191d0a0) at kernel/qapplication.cpp:3640 #27 0x7f25a68bce4a in QCoreApplication::notifyInternal2(QObject*, QEvent*) (receiver=0x56194c99f6c0, event=0x7fffb191d0a0) at kernel/qcoreapplication.cpp:1064 #28 0x7f25a691566b in QTimerInfoList::activateTimers() (this=this@entry=0x56194c623718) at kernel/qtimerinfo_unix.cpp:643 #29 0x7f25a6912dd0 in QEventDispatcherUNIXPrivate::activateTimers() (this=this@entry=0x56194c623690) at kernel/qeventdispatcher_unix.cpp:249 #30 0x7f25a6913b27 in QEventDispatcherUNIX::processEvents(QFlags) (this=, flags=...) at kernel/qeventdispatcher_unix.cpp:516 #31 0x56194b4513b1 in QUnixEventDispatcherQPA::processEvents(QFlags) () #32 0x7f25a68bb76b in QEventLoop::exec(QFlags) (this=this@entry=0x7fffb191d240, flags=..., flags@entry=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:69 #33 0x7f25a68c3d14 in QCoreApplication::exec() () at
[krita] [Bug 473750] krita crashes after pasting text out of edit text window or hitting ctrl+v on krita window with text in the clipboard
https://bugs.kde.org/show_bug.cgi?id=473750 Bug Janitor Service changed: What|Removed |Added Status|NEEDSINFO |REPORTED Resolution|WAITINGFORINFO |--- --- Comment #3 from Bug Janitor Service --- Thanks for your comment! Automatically switching the status of this bug to REPORTED so that the KDE team knows that the bug is ready to get confirmed. In the future you may also do this yourself when providing needed information. -- You are receiving this mail because: You are watching all bug changes.
[kpat] [Bug 473136] Mod3 crash
https://bugs.kde.org/show_bug.cgi?id=473136 --- Comment #3 from Bug Janitor Service --- Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 464520] Bad performance on poweroff screen on Wayland
https://bugs.kde.org/show_bug.cgi?id=464520 --- Comment #11 from Bug Janitor Service --- Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[plasma-systemmonitor] [Bug 473834] The system monitor does not show the load bar of the video card. Nvidia
https://bugs.kde.org/show_bug.cgi?id=473834 --- Comment #2 from Oliver Beard --- (In reply to Nate Graham from comment #1) > Oliver or David, is this the thing that's fixed now for Plasma 5.27.8? Nope. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 398689] Image disappears when zooming in after scale transform
https://bugs.kde.org/show_bug.cgi?id=398689 vanyossi changed: What|Removed |Added CC||borkbor...@yahoo.com --- Comment #30 from vanyossi --- *** Bug 473806 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 398689] Image disappears when zooming in after scale transform
https://bugs.kde.org/show_bug.cgi?id=398689 vanyossi changed: What|Removed |Added Status|CONFIRMED |ASSIGNED -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 398689] Image disappears when zooming in after scale transform
https://bugs.kde.org/show_bug.cgi?id=398689 vanyossi changed: What|Removed |Added Assignee|krita-bugs-n...@kde.org |ghe...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 473835] disable auto-suspend for VMs by default to avoid virtio hang
https://bugs.kde.org/show_bug.cgi?id=473835 Neal Gompa changed: What|Removed |Added CC||ngomp...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 473806] Resizing an image leads to erroneous display of the data?
https://bugs.kde.org/show_bug.cgi?id=473806 vanyossi changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |DUPLICATE CC||ghe...@gmail.com --- Comment #2 from vanyossi --- *** This bug has been marked as a duplicate of bug 398689 *** -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 452655] When you resize the canvas, the canvas becomes a mosaic
https://bugs.kde.org/show_bug.cgi?id=452655 vanyossi changed: What|Removed |Added Resolution|--- |DUPLICATE Status|ASSIGNED|RESOLVED --- Comment #9 from vanyossi --- *** This bug has been marked as a duplicate of bug 398689 *** -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 398689] Image disappears when zooming in after scale transform
https://bugs.kde.org/show_bug.cgi?id=398689 vanyossi changed: What|Removed |Added CC||s.s...@outlook.com --- Comment #29 from vanyossi --- *** Bug 452655 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 398689] Image disappears when zooming in after scale transform
https://bugs.kde.org/show_bug.cgi?id=398689 vanyossi changed: What|Removed |Added CC||mangate...@gmail.com --- Comment #28 from vanyossi --- *** Bug 459458 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 459458] Canvas disappearing after switching from crop to brush
https://bugs.kde.org/show_bug.cgi?id=459458 vanyossi changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |DUPLICATE CC||ghe...@gmail.com --- Comment #2 from vanyossi --- *** This bug has been marked as a duplicate of bug 398689 *** -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 398689] Image disappears when zooming in after scale transform
https://bugs.kde.org/show_bug.cgi?id=398689 vanyossi changed: What|Removed |Added Status|REOPENED|CONFIRMED --- Comment #27 from vanyossi --- The canvas is not correctly updated when texture buffer is active. This happens at least from this version up to 5.2.0 beta and master. The issue before going with 16 buffers was a completely transparent (with small images) or semi transparent images after a canvas operation and pan/move/paint with bigger ones as shown in bug 398689. With the current code an the 16 buffers only some of them fail to update sometimes, leaving. a portion of the image without redraw and showing the checkerboard as shown by bugs 459458, 452655 and 473806. If the image is small enough it can make the entire canvas become transparent. My current testings are using M! with master (e0fa60d68f) and 5.2.0beta This is a display error, no data is lost and hiding/showing the a layer makes the image redraw. I'll close all duplicates and use this bug as is the first one to mention a problem with texture buffer with macOS (Nvidia and M1-2). -- You are receiving this mail because: You are watching all bug changes.
[kphotoalbum] [Bug 473762] KPhotoAlbum crashes when Viewer and Annotations is open and then user right-clicks Show Info in Viewer
https://bugs.kde.org/show_bug.cgi?id=473762
Victor Lobo changed:
What|Removed |Added
Status|RESOLVED|REOPENED
Resolution|FIXED |---
--- Comment #7 from Victor Lobo ---
Re-opening this bug since the fix does not work for me. I get a crash after
doing the same steps. However, this time the backtrace is slightly different.
kphotoalbum v5.11.0-76-g603af9a9
Backtrace:
Application: KPhotoAlbum (kphotoalbum), signal: Segmentation fault
[KCrash Handler]
#4 QListData::begin (this=0x1eab190) at /usr/include/qt5/QtCore/qlist.h:118
#5 0x005ef4b8 in QList::begin (this=0x1eab190) at
/usr/include/qt5/QtCore/qlist.h:339
#6 0x005e7062 in AnnotationDialog::Dialog::hideFloatingWindows
(this=0x1eab040) at
/home/victor/Downloads/kphotoalbum/AnnotationDialog/Dialog.cpp:987
#7 0x005e6b0f in AnnotationDialog::Dialog::exec (this=0x1eab040) at
/home/victor/Downloads/kphotoalbum/AnnotationDialog/Dialog.cpp:953
#8 0x005e4d9f in AnnotationDialog::Dialog::configure (this=0x1eab040,
list=..., oneAtATime=true) at
/home/victor/Downloads/kphotoalbum/AnnotationDialog/Dialog.cpp:762
#9 0x005340d9 in MainWindow::Window::configImages (this=0x1ccc1b0,
list=..., oneAtATime=true) at
/home/victor/Downloads/kphotoalbum/MainWindow/Window.cpp:509
#10 0x00534077 in MainWindow::Window::configureImages (list=...,
oneAtATime=true) at
/home/victor/Downloads/kphotoalbum/MainWindow/Window.cpp:503
#11 0x004d7d0f in operator() (__closure=0x7f6dd8006b00) at
/home/victor/Downloads/kphotoalbum/Viewer/ViewerWidget.cpp:907
#12 0x004deb0d in QtPrivate::FunctorCall,
QtPrivate::List<>, void, Viewer::ViewerWidget::editImage()::
>::call(struct {...} &, void **) (f=..., arg=0x236a158) at
/usr/include/qt5/QtCore/qobjectdefs_impl.h:146
#13 0x004de9f9 in
QtPrivate::Functor,
0>::call, void>(struct {...} &, void *, void **) (f=...,
arg=0x236a158) at /usr/include/qt5/QtCore/qobjectdefs_impl.h:256
#14 0x004de90e in
QtPrivate::QFunctorSlotObject, 0,
QtPrivate::List<>, void>::impl(int, QtPrivate::QSlotObjectBase *, QObject *,
void **, bool *) (which=1, this_=0x7f6dd8006af0, r=0x19f58d0, a=0x236a158,
ret=0x0) at /usr/include/qt5/QtCore/qobjectdefs_impl.h:443
#15 0x7f6df3f19320 in QObject::event (this=0x19f58d0, e=0x236a110) at
kernel/qobject.cpp:1347
#16 0x7f6df4ba519e in QApplicationPrivate::notify_helper (this=, receiver=0x19f58d0, e=0x236a110) at kernel/qapplication.cpp:3640
#17 0x7f6df3eed568 in QCoreApplication::notifyInternal2
(receiver=0x19f58d0, event=0x236a110) at kernel/qcoreapplication.cpp:1064
#18 0x7f6df3eed72e in QCoreApplication::sendEvent (receiver=, event=) at kernel/qcoreapplication.cpp:1462
#19 0x7f6df3ef0b61 in QCoreApplicationPrivate::sendPostedEvents
(receiver=0x0, event_type=0, data=0x19f5850) at
kernel/qcoreapplication.cpp:1821
#20 0x7f6df3ef10a8 in QCoreApplication::sendPostedEvents
(receiver=, event_type=) at
kernel/qcoreapplication.cpp:1680
#21 0x7f6df3f46c93 in postEventSourceDispatch (s=0x1ad6e80) at
kernel/qeventdispatcher_glib.cpp:277
#22 0x7f6df0b169b8 in g_main_context_dispatch () from
/lib64/libglib-2.0.so.0
#23 0x7f6df0b16dc8 in ?? () from /lib64/libglib-2.0.so.0
#24 0x7f6df0b16e5c in g_main_context_iteration () from
/lib64/libglib-2.0.so.0
#25 0x7f6df3f464a6 in QEventDispatcherGlib::processEvents (this=0x1adc420,
flags=...) at kernel/qeventdispatcher_glib.cpp:423
#26 0x7f6df3eebffb in QEventLoop::exec (this=this@entry=0x7ffceb2dcee0,
flags=..., flags@entry=...) at
../../include/QtCore/../../src/corelib/global/qflags.h:69
#27 0x7f6df3ef4490 in QCoreApplication::exec () at
../../include/QtCore/../../src/corelib/global/qflags.h:121
#28 0x00471850 in main (argc=2, argv=0x7ffceb2dd5e8) at
/home/victor/Downloads/kphotoalbum/main.cpp:161
[Inferior 1 (process 15534) detached]
--
You are receiving this mail because:
You are watching all bug changes.
[lattedock] [Bug 473876] New: Latte Dock (GitHub build) crashing when launching VirtualBox
https://bugs.kde.org/show_bug.cgi?id=473876 Bug ID: 473876 Summary: Latte Dock (GitHub build) crashing when launching VirtualBox Classification: Plasma Product: lattedock Version: unspecified Platform: Compiled Sources OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: application Assignee: mvourla...@gmail.com Reporter: loganturner...@gmail.com Target Milestone: --- Application: latte-dock (0.10.77) 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: "Arch Linux" DrKonqi: 5.27.7 [KCrashBackend] -- Information about the crash: Latte Dock (Built from GitHub via AUR Package "latte-dock-git") crashes when opening VirtualBox. I am running version 0.10.77 on Arch Linux. System Specs: Intel Core i5-1135G7 (4C, 8T) Intel Iris Xe Graphics (80 Exe. Units) 16GB RAM (2x 8GB 3200MHz DDR4 SODIMM) 500GB Crucial P2 NVMe PCIe M.2 SSD The crash can be reproduced sometimes. -- Backtrace: Application: Latte Dock (latte-dock), signal: Segmentation fault [KCrash Handler] #4 0x7f1021d8b904 in QSGTexture::setFiltering(QSGTexture::Filtering) () at /usr/lib/libQt5Quick.so.5 #5 0x7f1021dbb630 in QSGOpaqueTextureMaterialShader::updateState(QSGMaterialShader::RenderState const&, QSGMaterial*, QSGMaterial*) () at /usr/lib/libQt5Quick.so.5 #6 0x7f1021da464e in QSGBatchRenderer::Renderer::renderMergedBatch(QSGBatchRenderer::Batch const*) () at /usr/lib/libQt5Quick.so.5 #7 0x7f1021da7e3e in QSGBatchRenderer::Renderer::renderBatches() () at /usr/lib/libQt5Quick.so.5 #8 0x7f1021dac8f1 in QSGBatchRenderer::Renderer::render() () at /usr/lib/libQt5Quick.so.5 #9 0x7f1021d94535 in QSGRenderer::renderScene(QSGBindable const&) () at /usr/lib/libQt5Quick.so.5 #10 0x7f1021dfbbfc in QSGOpenGLLayer::grab() () at /usr/lib/libQt5Quick.so.5 #11 0x7f1021df3ae6 in QSGOpenGLLayer::updateTexture() () at /usr/lib/libQt5Quick.so.5 #12 0x7f1021f4fcc7 in QQuickOpenGLShaderEffectMaterial::updateTextures() const () at /usr/lib/libQt5Quick.so.5 #13 0x7f1021d94c39 in QSGRenderer::preprocess() () at /usr/lib/libQt5Quick.so.5 #14 0x7f1021d944fc in QSGRenderer::renderScene(QSGBindable const&) () at /usr/lib/libQt5Quick.so.5 #15 0x7f1021d949d4 in QSGRenderer::renderScene(unsigned int) () at /usr/lib/libQt5Quick.so.5 #16 0x7f1021dedf25 in QSGDefaultRenderContext::renderNextFrame(QSGRenderer*, unsigned int) () at /usr/lib/libQt5Quick.so.5 #17 0x7f1021e4c001 in QQuickWindowPrivate::renderSceneGraph(QSize const&, QSize const&) () at /usr/lib/libQt5Quick.so.5 #18 0x7f1021df8576 in () at /usr/lib/libQt5Quick.so.5 #19 0x7f1021dfd334 in () at /usr/lib/libQt5Quick.so.5 #20 0x7f101fef35da in () at /usr/lib/libQt5Core.so.5 #21 0x7f101f68c9eb in () at /usr/lib/libc.so.6 #22 0x7f101f710dfc in () at /usr/lib/libc.so.6 Thread 21 (Thread 0x7f0fb0ca76c0 (LWP 1933) "latte-do:gdrv0"): #1 0x7f101f68bd40 in pthread_cond_wait () at /usr/lib/libc.so.6 #2 0x7f1011ec781c in () at /usr/lib/dri/iris_dri.so #3 0x7f1011f1472c in () at /usr/lib/dri/iris_dri.so #4 0x7f101f68c9eb in () at /usr/lib/libc.so.6 #5 0x7f101f710dfc in () at /usr/lib/libc.so.6 Thread 20 (Thread 0x7f0fb14da6c0 (LWP 1932) "latte-:traceq0"): #1 0x7f101f68bd40 in pthread_cond_wait () at /usr/lib/libc.so.6 #2 0x7f1011ec781c in () at /usr/lib/dri/iris_dri.so #3 0x7f1011f1472c in () at /usr/lib/dri/iris_dri.so #4 0x7f101f68c9eb in () at /usr/lib/libc.so.6 #5 0x7f101f710dfc in () at /usr/lib/libc.so.6 Thread 19 (Thread 0x7f0fb1f5b6c0 (LWP 1931) "QSGRenderThread"): #1 0x7f101f68bd40 in pthread_cond_wait () at /usr/lib/libc.so.6 #2 0x7f101fefb364 in QWaitCondition::wait(QMutex*, QDeadlineTimer) () at /usr/lib/libQt5Core.so.5 #3 0x7f1021dfd712 in () at /usr/lib/libQt5Quick.so.5 #4 0x7f101fef35da in () at /usr/lib/libQt5Core.so.5 #5 0x7f101f68c9eb in () at /usr/lib/libc.so.6 #6 0x7f101f710dfc in () at /usr/lib/libc.so.6 Thread 18 (Thread 0x7f0fb277c6c0 (LWP 1930) "latte-do:gdrv0"): #1 0x7f101f68bd40 in pthread_cond_wait () at /usr/lib/libc.so.6 #2 0x7f1011ec781c in () at /usr/lib/dri/iris_dri.so #3 0x7f1011f1472c in () at /usr/lib/dri/iris_dri.so #4 0x7f101f68c9eb in () at /usr/lib/libc.so.6 #5 0x7f101f710dfc in () at /usr/lib/libc.so.6 Thread 17 (Thread 0x7f0fb2f7d6c0 (LWP 1929) "latte-:traceq0"): #1 0x7f101f68bd40 in pthread_cond_wait () at /usr/lib/libc.so.6 #2 0x7f1011ec781c in () at /usr/lib/dri/iris_dri.so #3 0x7f1011f1472c in () at /usr/lib/dri/iris_dri.so #4 0x7f101f68c9eb in () at /usr/lib/libc.so.6 #5 0x7f101f710dfc in () at /usr/lib/libc.so.6 Thread 16 (Thread 0x7f0fb37fe6c0 (LWP 1928)
[kde] [Bug 473875] New: Applications made with Godot are grouped with the Godot editor in the Icons-only Task Manager
https://bugs.kde.org/show_bug.cgi?id=473875 Bug ID: 473875 Summary: Applications made with Godot are grouped with the Godot editor in the Icons-only Task Manager Classification: I don't know Product: kde Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: poperi...@mailbox.org Target Milestone: --- Created attachment 161251 --> https://bugs.kde.org/attachment.cgi?id=161251=edit Pixelorama being grouped with the Godot editor SUMMARY Any application that is made with Godot (i.e. Pixelorama) is grouped under the Godot icon along with it's editor, in the Icons-only Task Manager. This is undesirable, because I might want to use both the editor and another Godot made app at the same time, and it makes it annoying to switch between them when they're grouped together. It also doesn't make any sense. For example, one wouldn't want every app made with Qt to be grouped under Qt Creator. STEPS TO REPRODUCE 1. Install the Godot editor (doesn't matter from where, distro packages or Flatpak) 2. Install an application made with Godot (i.e. Pixelorama) 3. Launch the Godot editor 4. Launch any application made with Godot OBSERVED RESULT All applications that are made with Godot are grouped under the Godot editor. EXPECTED RESULT Applications made with Godot are in their own group, and not grouped under the Godot editor SOFTWARE/OS VERSIONS Operating System: Fedora Linux 38 KDE Plasma Version: 5.27.7 KDE Frameworks Version: 5.109.0 Qt Version: 5.15.10 Kernel Version: 6.4.11-200.fc38.x86_64 (64-bit) Graphics Platform: Wayland Processors: 16 × AMD Ryzen 7 3700X 8-Core Processor Memory: 15.5 GiB of RAM Graphics Processor: AMD Radeon RX 5700 XT Manufacturer: ASUS -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 473831] Add left, right, and center alignment options
https://bugs.kde.org/show_bug.cgi?id=473831 --- Comment #2 from igloopengu...@gmail.com --- (In reply to Nate Graham from comment #1) > Why? What's the use case? Currently, the digital clock applet is centered by default, which does look really nice in the center. But, when it's positioned on the sides of the panel, it might not align with everyone's preference, including mine. I think having the option to change the alignment would enhance the overall aesthetics and add more customization to the desktop environment. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 439805] Move individual tabbed/windowed processes into their own systemd scope
https://bugs.kde.org/show_bug.cgi?id=439805 --- Comment #7 from Kurt Hindenburg --- Git commit 1525ee3b5ea58b09d551f41b0bd6f0f91589e070 by Kurt Hindenburg, on behalf of Theodore Wang. Committed on 29/08/2023 at 01:59. Pushed by hindenburg into branch 'master'. Create separate cgroups for processes of each tab Currently, all the processes created by the application are housed within the application's cgroup without any futher categorisation. This causes the entire application to be killed if a process in the aforementioned cgroup triggers an OOM event. To prevent the entire application from being killed, a new child cgroup is created for each new tab. Child cgroups for individual tabs are named according to this template "tab([session pid for the tab]).scope". "Background" processes (e.g. such as the main process for running konsole) are stored in the child cgroup "main.scope". This restricts the OOM event to only killing the tab which contains the offending process. To prevent the entire application from being killed, a new child cgroup is created for each new tab. Child cgroups for individual tabs are named according to this template "tab([session pid for the tab]).scope". "Background" processes (e.g. such as the main process for running konsole) are stored in the child cgroup "main.scope". This restricts the OOM event to only killing the tab which contains the offending process. M +2-0src/CMakeLists.txt M +7-0src/MainWindow.cpp M +226 -3src/ProcessInfo.cpp M +3-1src/ProcessInfo.h M +1-1src/session/Session.cpp A +18 -0src/settings/MemorySettings.cpp * A +18 -0src/settings/MemorySettings.h * A +62 -0src/settings/MemorySettings.ui M +10 -0src/settings/konsole.kcfg The files marked with a * at the end have a non valid license. Please read: https://community.kde.org/Policies/Licensing_Policy and use the headers which are listed at that page. https://invent.kde.org/utilities/konsole/-/commit/1525ee3b5ea58b09d551f41b0bd6f0f91589e070 -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 439805] Move individual tabbed/windowed processes into their own systemd scope
https://bugs.kde.org/show_bug.cgi?id=439805 Kurt Hindenburg changed: What|Removed |Added Latest Commit||https://invent.kde.org/util ||ities/konsole/-/commit/1525 ||ee3b5ea58b09d551f41b0bd6f0f ||91589e070 Resolution|--- |FIXED Status|ASSIGNED|RESOLVED --- Comment #6 from Kurt Hindenburg --- Git commit 1525ee3b5ea58b09d551f41b0bd6f0f91589e070 by Kurt Hindenburg, on behalf of Theodore Wang. Committed on 29/08/2023 at 01:59. Pushed by hindenburg into branch 'master'. Create separate cgroups for processes of each tab Currently, all the processes created by the application are housed within the application's cgroup without any futher categorisation. This causes the entire application to be killed if a process in the aforementioned cgroup triggers an OOM event. To prevent the entire application from being killed, a new child cgroup is created for each new tab. Child cgroups for individual tabs are named according to this template "tab([session pid for the tab]).scope". "Background" processes (e.g. such as the main process for running konsole) are stored in the child cgroup "main.scope". This restricts the OOM event to only killing the tab which contains the offending process. To prevent the entire application from being killed, a new child cgroup is created for each new tab. Child cgroups for individual tabs are named according to this template "tab([session pid for the tab]).scope". "Background" processes (e.g. such as the main process for running konsole) are stored in the child cgroup "main.scope". This restricts the OOM event to only killing the tab which contains the offending process. M +2-0src/CMakeLists.txt M +7-0src/MainWindow.cpp M +226 -3src/ProcessInfo.cpp M +3-1src/ProcessInfo.h M +1-1src/session/Session.cpp A +18 -0src/settings/MemorySettings.cpp * A +18 -0src/settings/MemorySettings.h * A +62 -0src/settings/MemorySettings.ui M +10 -0src/settings/konsole.kcfg The files marked with a * at the end have a non valid license. Please read: https://community.kde.org/Policies/Licensing_Policy and use the headers which are listed at that page. https://invent.kde.org/utilities/konsole/-/commit/1525ee3b5ea58b09d551f41b0bd6f0f91589e070 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 473874] New: Fix the splash screen to not slow down boot
https://bugs.kde.org/show_bug.cgi?id=473874 Bug ID: 473874 Summary: Fix the splash screen to not slow down boot Classification: Plasma Product: plasmashell Version: 5.27.7 Platform: unspecified OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: Theme - Breeze Assignee: plasma-b...@kde.org Reporter: amanita+kdeb...@mailbox.org CC: visual-des...@kde.org Target Milestone: 1.0 The current implementation of the KDE Splash screen does not have any performance benefit, but slows down the launch as until its gone plasma doesnt start loading, as do the autostart apps. The fix: Convert it into an overlay that displays over the screen immediately. This would help with laggy loading of the Panel and startup apps. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 473788] Tablet mode does not disable touchpad (but it successfully disables the keyboard)
https://bugs.kde.org/show_bug.cgi?id=473788 --- Comment #2 from Archisman Panigrahi --- (In reply to Nate Graham from comment #1) > This is a bug in your device's firmware or in Libinput then, as disabling > the touchpad is handled at a layer below us. I'd recommend submitting a bug > report first to Libinput at > https://gitlab.freedesktop.org/libinput/libinput/-/issues. I have reported a bug here https://gitlab.freedesktop.org/libinput/libinput/-/issues/929 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 473873] New: SVG scaling issue, transforming when it shouldn't and The grid snapping doesn't work
https://bugs.kde.org/show_bug.cgi?id=473873 Bug ID: 473873 Summary: SVG scaling issue, transforming when it shouldn't and The grid snapping doesn't work Classification: Applications Product: krita Version: 5.1.5 Platform: Microsoft Windows OS: Microsoft Windows Status: REPORTED Severity: normal Priority: NOR Component: Layers/Vector Assignee: krita-bugs-n...@kde.org Reporter: hayes...@gmail.com Target Milestone: --- Created attachment 161250 --> https://bugs.kde.org/attachment.cgi?id=161250=edit That's the file I used to create it. It is scaling SVGs when it should not be doing so. Your grid snapping isn't snapping to the grid for it but to pixels. STEPS TO REPRODUCE 1. I created a 128 by 128 image and then created an SVG layer on it. 2. I then created the SVG vector. OBSERVED RESULT After exporting it I noticed when opening it in a browser it was about 1/4 the size it should be. So I looked at the text in the SVG and noticed it reduced it to 30.72 for both axis rather than 128. Scaling the graphic up is entirely worthless in that the proportions of line thickness and so on then are off. I've searched the internet and forums to see how I can tell it to not change the scale no answers any place. SVG primary use is internet and graphics like PDF. It doesn't help to have something change what you are making into something else and you can't rely on the software to produce what it should make. EXPECTED RESULT I think most people would expect the size they set something to be will be the size and scale it is produced at not 1/4.1666 the size. I'm also not a fan of the transformation being done as well. Unless I tell it to transform I don't want it doing so. The entire reason I am building this object in SVG is so I can create characters and attach a skeleton system to them and then animate them and make it so I can automatically fit clothing from one character to another. All the transformation does is force me to recalculate everything by hand. At most I would want is transformation from the center of the 128 by 128 area in this case. But that isn't what is being done. So in effect the SVG produced is entirely worthless and I am hand coding the SVGs or going to use software that doesn't scale or translate unless I tell it or maybe allows me to select the translation point. SOFTWARE/OS VERSIONS Windows: Windows 10 ADDITIONAL INFORMATION To be clear this is a fresh install of the software on a freshly installed Windows 10. No changes made to it. So I haven't changed any settings this is the default behavior of the software. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 473724] New Blending Info feature: Opacity info is slow to update
https://bugs.kde.org/show_bug.cgi?id=473724 Bug Janitor Service changed: What|Removed |Added Status|CONFIRMED |ASSIGNED --- Comment #2 from Bug Janitor Service --- A possibly relevant merge request was started @ https://invent.kde.org/graphics/krita/-/merge_requests/1922 -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 473638] Height-Width value not translatable
https://bugs.kde.org/show_bug.cgi?id=473638 Bug Janitor Service changed: What|Removed |Added Status|CONFIRMED |ASSIGNED --- Comment #1 from Bug Janitor Service --- A possibly relevant merge request was started @ https://invent.kde.org/graphics/gwenview/-/merge_requests/220 -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 473636] Percent values are not localisable
https://bugs.kde.org/show_bug.cgi?id=473636 Bug Janitor Service changed: What|Removed |Added Status|CONFIRMED |ASSIGNED --- Comment #1 from Bug Janitor Service --- A possibly relevant merge request was started @ https://invent.kde.org/graphics/gwenview/-/merge_requests/220 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 473872] New: Plasma 6: remove the start splash screen
https://bugs.kde.org/show_bug.cgi?id=473872 Bug ID: 473872 Summary: Plasma 6: remove the start splash screen Classification: Plasma Product: plasmashell Version: 5.27.7 Platform: unspecified OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Theme - Breeze Assignee: plasma-b...@kde.org Reporter: amanita+kdeb...@mailbox.org CC: visual-des...@kde.org Target Milestone: 1.0 There were issues about this. The splash screen implementation doesnt make sense, as elements dont start loading while its displaying. It would actually make a lot of sense if apps could load in the background, and this was just a fullscreen overlay. But currently it just slows down the start and users have lots of time seeing that they use KDE. Also when switching the plasma theme, it always reenables, which sucks too. -- You are receiving this mail because: You are watching all bug changes.
[kphotoalbum] [Bug 473762] KPhotoAlbum crashes when Viewer and Annotations is open and then user right-clicks Show Info in Viewer
https://bugs.kde.org/show_bug.cgi?id=473762 Johannes Zarl-Zierl changed: What|Removed |Added Latest Commit||https://invent.kde.org/grap ||hics/kphotoalbum/-/commit/7 ||0a6f27f7312a0c4a296a788f5b0 ||08ee58fcb1d4 Status|CONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #6 from Johannes Zarl-Zierl --- Git commit 70a6f27f7312a0c4a296a788f5b008ee58fcb1d4 by Johannes Zarl-Zierl. Committed on 29/08/2023 at 00:33. Pushed by johanneszarl into branch 'master'. Fix crash when the AnnotationDialog is deleted while open If the annotation dialog is open and the DB::CategoryCollection::categoryCollectionChanged signal is triggered, the dialog is deleted. The anotation dialog tries to hide any floating dock widgets after closing, but at that point, it has already been deleted and invalidated memory is accessed. M +2-0AnnotationDialog/Dialog.cpp https://invent.kde.org/graphics/kphotoalbum/-/commit/70a6f27f7312a0c4a296a788f5b008ee58fcb1d4 -- You are receiving this mail because: You are watching all bug changes.
[Elisa] [Bug 473871] New: Change permission to directories that are needed
https://bugs.kde.org/show_bug.cgi?id=473871 Bug ID: 473871 Summary: Change permission to directories that are needed Classification: Applications Product: Elisa Version: 23.04.3 Platform: Flatpak OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: matthieu_gall...@yahoo.fr Reporter: amanita+kdeb...@mailbox.org Target Milestone: --- This is a big general Flatpak apps issue: If apps are supposed to open files "located everywhere" they get the host permission. This is not sandboxed really, and having - ~/ - /run - /media - /mnt - ... Should be enough and address the problem. Maybe some more directories, but these should be set instead of host, at least. >From a security perspective it would be best to have no permissions at all and just use portals. But this is lots of work, not needed probably too. -- You are receiving this mail because: You are watching all bug changes.
[Elisa] [Bug 473181] The flatpak indexes no files at all.
https://bugs.kde.org/show_bug.cgi?id=473181 --- Comment #12 from Henning --- and yes, integrating portals or just having no app with host permission anymore is a biiig flatpak goal, especially on the old apps like Libreoffice, GIMP etc -- You are receiving this mail because: You are watching all bug changes.
[Elisa] [Bug 473181] The flatpak indexes no files at all.
https://bugs.kde.org/show_bug.cgi?id=473181 Henning changed: What|Removed |Added Status|RESOLVED|REOPENED Ever confirmed|0 |1 Resolution|NOT A BUG |--- --- Comment #11 from Henning --- hmm, weird no this cant be. I gave Elisa permission to access my music files, thats it. No home access as I know where my music is and all apps simply only get the directories they actually need. So there has to be some error why this does not work. It works with home access, but this has to have a different reason as its not needed to find the music files. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-ktexteditor] [Bug 447740] Crash in QAccessible::queryAccessibleInterface
https://bugs.kde.org/show_bug.cgi?id=447740 --- Comment #20 from doc.ev...@gmail.com --- Just to confirm that this isn't associated with Wayland. I reported bug https://bugs.kde.org/show_bug.cgi?id=473251 which is perhaps the same bug (although I'm not absolutely certain about that) and I don't use Wayland at all. In fact here it's always X-over-ssh. In case it helps, here is part of my most recent post on bug 473251: 2. The crashes occur at the rate of about two per hour... I can get work done, but it's certainly annoying to be interrupted by crashes so frequently. 3. I have not found a particular sequence of actions that is guaranteed to reproduce the crash. 4. I *think* that crashes happen only when I've actively interacted with the editor window: either I'm in the middle of typing, or at the very least, I've just clicked somewhere in the window. 5. FYI, the project I'm working on is: https://github.com/N7DR/drlog. Since installing debian bookworm on the computer in question, I have never seen any crash except when using kdevelop (i.e., not when using Kate or any other KDE program). -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 473702] plasmashell does not disown child processes, making restarting plasmashell kill applications too
https://bugs.kde.org/show_bug.cgi?id=473702 Martin changed: What|Removed |Added Status|RESOLVED|REPORTED Resolution|INTENTIONAL |--- --- Comment #6 from Martin --- Actually no, despite not being enabled, it does run on startup, I just got confused because it was killed 4 days ago, but my uptime is indeed 4 days. % uptime -p up 4 days, 6 hours, 6 minutes % systemctl --user status plasma-plasmashell.service ○ plasma-plasmashell.service - KDE Plasma Workspace Loaded: loaded (/usr/lib/systemd/user/plasma-plasmashell.service; disabled; preset: enabled) Active: inactive (dead) since Thu 2023-08-24 23:49:35 CEST; 4 days ago Duration: 5h 36min 54.633s Process: 6451 ExecStart=/usr/bin/plasmashell --no-respawn (code=exited, status=0/SUCCESS) Main PID: 6451 (code=exited, status=0/SUCCESS) CPU: 11min 25.152s ... Aug 24 23:49:35 Luxuria plasmashell[6451]: zwp_linux_dmabuf_v1@29 still attached Aug 24 23:49:35 Luxuria systemd[5311]: plasma-plasmashell.service: Consumed 11min 25.152s CPU time. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 469445] Ever-growing ScreenMapping entry in config file makes plasmashell slow down and eventually crash
https://bugs.kde.org/show_bug.cgi?id=469445 Harald Sitter changed: What|Removed |Added Latest Commit|https://invent.kde.org/plas |https://invent.kde.org/plas |ma/plasma-desktop/-/commit/ |ma/plasma-desktop/-/commit/ |8c893445732c76e30ec0cd72aab |9ed48f1def75f3ce46853ddb212 |2036b30078c2a |b7cb7247e3a7c --- Comment #29 from Harald Sitter --- Git commit 9ed48f1def75f3ce46853ddb212b7cb7247e3a7c by Harald Sitter. Committed on 29/08/2023 at 00:12. Pushed by sitter into branch 'Plasma/5.27'. folderview: cap amount of screen mappings we hold this introduces a hard limit for how many items we support on the desktop. currently that is a static limit so it's not too invasive for 5.27. ideally we should revisit this for 6 and try to deal with excessive items more gracefully (cherry picked from commit 8c893445732c76e30ec0cd72aab2036b30078c2a) M +11 -0containments/desktop/package/contents/ui/FolderView.qml M +6-0containments/desktop/plugins/folder/CMakeLists.txt M +46 -3containments/desktop/plugins/folder/screenmapper.cpp https://invent.kde.org/plasma/plasma-desktop/-/commit/9ed48f1def75f3ce46853ddb212b7cb7247e3a7c -- You are receiving this mail because: You are watching all bug changes.
[kinfocenter] [Bug 473867] Untranslated bits in Info Center
https://bugs.kde.org/show_bug.cgi?id=473867 --- Comment #3 from Harald Sitter --- Looks to me like there is no Messages.sh for the src/ folder. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 473702] plasmashell does not disown child processes, making restarting plasmashell kill applications too
https://bugs.kde.org/show_bug.cgi?id=473702 --- Comment #5 from Martin --- I never manually disabled it, but this is a system from... 2021-06-27, and I presume it wasn't a forced switch for older systems? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 473702] plasmashell does not disown child processes, making restarting plasmashell kill applications too
https://bugs.kde.org/show_bug.cgi?id=473702 Nate Graham changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |INTENTIONAL --- Comment #4 from Nate Graham --- I had a feeling. This was one of the issues that the systemd-based startup process was specifically developed to solve. :) I would recommend re-enabling it. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 473702] plasmashell does not disown child processes, making restarting plasmashell kill applications too
https://bugs.kde.org/show_bug.cgi?id=473702 Martin changed: What|Removed |Added Status|NEEDSINFO |REPORTED Resolution|WAITINGFORINFO |--- --- Comment #3 from Martin --- Do you mean using the systemd startup thing - https://blog.davidedmundson.co.uk/blog/plasma-and-the-systemd-startup/ ? This shows up as disabled on my system: systemctl --user status plasma-plasmashell.service -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 473860] Apps should autostart only after Plasma has finished launching
https://bugs.kde.org/show_bug.cgi?id=473860 --- Comment #2 from Henning --- 323151 sounds pretty important 467619 is an app issue but also useful 416265 this is basically my bug. So the quick solution (as I tried to phrase it) would be to simply give Plasma the privilege to start first. Currently apps have this, it would really not be a problem. But then the question, what should start first and in what order? Network Plasma Panel privileged autostart services/Apps autostart scripts autostart apps maybe? -- You are receiving this mail because: You are watching all bug changes.
[kactivitymanagerd] [Bug 397487] Cannot disable activity tracking and history not deleted
https://bugs.kde.org/show_bug.cgi?id=397487 Nate Graham changed: What|Removed |Added CC||n...@kde.org Version Fixed In||6.0 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 449163] Plasma panel visually freezes after some time under Wayland
https://bugs.kde.org/show_bug.cgi?id=449163 k...@sl.marcogiorgio.net changed: What|Removed |Added CC|k...@sl.marcogiorgio.net | -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 473768] Windows black out after some time
https://bugs.kde.org/show_bug.cgi?id=473768 --- Comment #5 from Nate Graham --- That's very big of you. It's not an easy thing to acknowledge your faults and try to get better. Best of luck! -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 473870] New: FreeBSD 14 applications fail early at startup
https://bugs.kde.org/show_bug.cgi?id=473870 Bug ID: 473870 Summary: FreeBSD 14 applications fail early at startup Classification: Developer tools Product: valgrind Version: 3.22 GIT Platform: Other OS: FreeBSD Status: REPORTED Severity: crash Priority: NOR Component: general Assignee: jsew...@acm.org Reporter: pjfl...@wanadoo.fr Target Milestone: --- Something has changed on FreeBSD 14 amd64. Seems to affect memcheck, drd, helgrind and dhat none, massif, lackey, cachegrind and callgrind seem OK ./vg-in-place -q pwd valgrind: m_redir.c:1212 (Addr vgPlain_redir_do_lookup(Addr, Bool *)): Assertion 'iFuncWrapper' failed. host stacktrace: ==42610==at 0x3810C626: ??? (in /home/paulf/valgrind/memcheck/memcheck-amd64-freebsd) ==42610==by 0x1002AA9FDF: ??? ==42610==by 0x38105789: ??? (in /home/paulf/valgrind/memcheck/memcheck-amd64-freebsd) ==42610==by 0x3810C625: ??? (in /home/paulf/valgrind/memcheck/memcheck-amd64-freebsd) ==42610==by 0x1002AA978F: ??? sched status: running_tid=1 Thread 1: status = VgTs_Runnable (lwpid 100883) ==42610==at 0x49B1BD0: stpcpy (in /lib/libc.so.7) ==42610==by 0x40073D3: ??? (in /libexec/ld-elf.so.1) ==42610==by 0x400A7CF: ??? (in /libexec/ld-elf.so.1) ==42610==by 0x400975E: ??? (in /libexec/ld-elf.so.1) ==42610==by 0x4006B88: ??? (in /libexec/ld-elf.so.1) client stack range: [0x1FFBFFE000 0x1FFC000FFF] client SP: 0x1FFBFFFDE8 valgrind stack range: [0x10029AA000 0x1002AA9FFF] top usage: 7072 of 1048576 Note: see also the FAQ in the source distribution. It contains workarounds to several common problems. In particular, if Valgrind aborted or crashed after identifying problems in your program, there's a good chance that fixing those problems will prevent Valgrind aborting or crashing, especially if it happened in m_mallocfree.c. If that doesn't help, please report this bug to: www.valgrind.org In the bug report, send all the above text, the valgrind version, and what OS and version you are using. Thanks. I think that the assert is a red herring, and it's because the iFuncWrapper is not correctly initialized. My first impression is that there is a problem with reading the mmap'd memcheck exe --43056:2: aspacem Reading /proc/self/maps --43056:2: aspacem <<< SHOW_SEGMENTS: With contents of /proc/self/maps (16 segments) --43056:2: aspacem 1 segment names in 1 slots --43056:2: aspacem freelist is empty --43056:2: aspacem (0,4,3) /home/paulf/valgrind/memcheck/memcheck-amd64-freebsd --43056:2: aspacem 0: RSVN 00-0003ff 64m - SmFixed --43056:2: aspacem 1: 000400-0037ff832m --43056:2: aspacem 2: FILE 003800-00380c2fff 798720 r d=0x05a i=2490977 o=0 (0,4) --43056:2: aspacem 3: FILE 00380c3000-0038270fff 1761280 r-x-- d=0x05a i=2490977 o=794624 (0,4) --43056:2: aspacem 4: ANON 0038271000-003a84efff 37m rw--- The same on FreeBSD 13.2 (works OK) --2474:2: aspacem Reading /proc/self/maps --2474:2: aspacem <<< SHOW_SEGMENTS: With contents of /proc/self/maps (15 segments) --2474:2: aspacem 1 segment names in 1 slots --2474:2: aspacem freelist is empty --2474:2: aspacem (0,4,5) /usr/home/paulf/scratch/valgrind/memcheck/memcheck-amd64-freebsd --2474:2: aspacem 0: RSVN 00-0003ff 64m - SmFixed --2474:2: aspacem 1: 000400-0037ff832m --2474:2: aspacem 2: FILE 003800-00380c4fff 806912 r d=0x696e301b i=2438781 o=0 (0,4) --2474:2: aspacem 3: FILE 00380c5000-0038274fff 1769472 r-x-- d=0x696e301b i=2438781 o=802816 (0,4) --2474:2: aspacem 4: FILE 0038275000-0038275fff4096 rw--- d=0x696e301b i=2438781 o=2568192 (0,4) --2474:2: aspacem 5: ANON 0038276000-003a852fff 37m rw--- Where has number 4, the RW segment gone? parse_procselfmaps could be at fault? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 473665] Kwin-wayland crashed (after reboot) when connecting a second high-dpi monitor
https://bugs.kde.org/show_bug.cgi?id=473665 Nate Graham changed: What|Removed |Added CC||n...@kde.org Resolution|--- |BACKTRACE Status|REPORTED|NEEDSINFO --- Comment #8 from Nate Graham --- Can you follow the instructions at https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports#Retrieving_a_backtrace_using_coredumpctl to get a backtrace for us? -- You are receiving this mail because: You are watching all bug changes.
[Merkuro] [Bug 472793] merkuro-calendar crashes on startup
https://bugs.kde.org/show_bug.cgi?id=472793 funny0facer changed: What|Removed |Added CC||t...@gmx.net -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 473657] One cannot update the system
https://bugs.kde.org/show_bug.cgi?id=473657 --- Comment #8 from Piotr Mierzwinski --- I guess only users replied here trying to help, but how could help people packing/preparing distributions? In my humble opinion this is really serious problem, because many testing people can't update the system, so cannot test and report the bugs. Bug happened one week ago and I think nobody from Neon team posted here. Please correct me if I'm wrong. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 466869] Desktop icons reset positions after changing screen setup
https://bugs.kde.org/show_bug.cgi?id=466869 Nate Graham changed: What|Removed |Added CC||php4...@gmail.com --- Comment #13 from Nate Graham --- *** Bug 469256 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 469256] Icons on my desktop got rearranged after switching screens
https://bugs.kde.org/show_bug.cgi?id=469256 Nate Graham changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |DUPLICATE --- Comment #3 from Nate Graham --- *** This bug has been marked as a duplicate of bug 466869 *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 466869] Desktop icons reset positions after changing screen setup
https://bugs.kde.org/show_bug.cgi?id=466869 Nate Graham changed: What|Removed |Added CC||mirth...@yandex.ru --- Comment #12 from Nate Graham --- *** Bug 473706 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 473706] Desktop icon positions reset with multiple screens
https://bugs.kde.org/show_bug.cgi?id=473706 Nate Graham changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |DUPLICATE --- Comment #1 from Nate Graham --- *** This bug has been marked as a duplicate of bug 466869 *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 466869] Desktop icons reset positions after changing screen setup
https://bugs.kde.org/show_bug.cgi?id=466869 Nate Graham changed: What|Removed |Added CC||sarahvc...@gmail.com --- Comment #11 from Nate Graham --- *** Bug 473832 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 473832] Desktop icons sometimes get reset to default sorting after changing display configurations, even if they are locked and set to unsorted.
https://bugs.kde.org/show_bug.cgi?id=473832 Nate Graham changed: What|Removed |Added Resolution|--- |DUPLICATE Status|REPORTED|RESOLVED --- Comment #2 from Nate Graham --- *** This bug has been marked as a duplicate of bug 466869 *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 469256] Icons on my desktop got rearranged after switching screens
https://bugs.kde.org/show_bug.cgi?id=469256 Nate Graham changed: What|Removed |Added See Also|https://bugs.kde.org/show_b | |ug.cgi?id=466869| -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 466869] Desktop icons reset positions after changing screen setup
https://bugs.kde.org/show_bug.cgi?id=466869 Nate Graham changed: What|Removed |Added See Also|https://bugs.kde.org/show_b | |ug.cgi?id=467405, | |https://bugs.kde.org/show_b | |ug.cgi?id=469256| -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 467405] Desktop Icons that were arranged in a custom order become alphabetically sorted automatically after a period of time
https://bugs.kde.org/show_bug.cgi?id=467405 Nate Graham changed: What|Removed |Added See Also|https://bugs.kde.org/show_b | |ug.cgi?id=466869| -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 466869] Desktop icons reset positions after changing screen setup
https://bugs.kde.org/show_bug.cgi?id=466869 Nate Graham changed: What|Removed |Added Summary|Desktop icons reset |Desktop icons reset |positions after closing and |positions after changing |re-opening laptop screen|screen setup |when external screen| |mirrors internal one| -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 469256] Icons on my desktop got rearranged after switching screens
https://bugs.kde.org/show_bug.cgi?id=469256 Nate Graham changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=466869 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 466869] Desktop icons reset positions after closing and re-opening laptop screen when external screen mirrors internal one
https://bugs.kde.org/show_bug.cgi?id=466869 Nate Graham changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=469256 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 473706] Desktop icon positions reset with multiple screens
https://bugs.kde.org/show_bug.cgi?id=473706 Nate Graham changed: What|Removed |Added Component|common |Folder Target Milestone|--- |1.0 CC||h...@kde.org, n...@kde.org Keywords||multiscreen Assignee|kscreen-bugs-n...@kde.org |plasma-b...@kde.org Summary|Different monitors screen |Desktop icon positions |ratios and anomalous|reset with multiple screens |behavior| Product|KScreen |plasmashell -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 473768] Windows black out after some time
https://bugs.kde.org/show_bug.cgi?id=473768 --- Comment #4 from voncl...@gmail.com --- Thanks, I am trying my best to work on my anger... It's not easy but I'm trying my best. -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 473807] Plasma is initializing a new display output when restarting monitor
https://bugs.kde.org/show_bug.cgi?id=473807 Nate Graham changed: What|Removed |Added Keywords||multiscreen -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 473807] Plasma is initializing a new display output when restarting monitor
https://bugs.kde.org/show_bug.cgi?id=473807 Nate Graham changed: What|Removed |Added CC||n...@kde.org Resolution|--- |WAITINGFORINFO Status|REPORTED|NEEDSINFO --- Comment #1 from Nate Graham --- When this happens, are your display settings also reset? e.g. display resolution, scale, refresh rate, position, etc? Or are all of those settings remembered, and the problem is that there's a spike in system load that causes other issues? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 449163] Plasma panel visually freezes after some time under Wayland
https://bugs.kde.org/show_bug.cgi?id=449163 Kevin López Brante changed: What|Removed |Added CC||ke...@kddlb.cl --- Comment #62 from Kevin López Brante --- I have this same bug in Arch Linux. inxi output: System: Host: ruxtower Kernel: 6.5.0-1-cachyos arch: x86_64 bits: 64 Desktop: KDE Plasma v: 5.27.7 Distro: Arch Linux Memory: System RAM: total: 32 GiB available: 31.16 GiB used: 8.86 GiB (28.4%) Array-1: capacity: 128 GiB slots: 4 modules: 4 EC: None Device-1: Controller0-ChannelA-DIMM0 type: DDR4 size: 8 GiB speed: 3200 MT/s Device-2: Controller0-ChannelA-DIMM1 type: DDR4 size: 8 GiB speed: 3200 MT/s Device-3: Controller1-ChannelA-DIMM0 type: DDR4 size: 8 GiB speed: 3200 MT/s Device-4: Controller1-ChannelA-DIMM1 type: DDR4 size: 8 GiB speed: 3200 MT/s Graphics: Device-1: NVIDIA GA106 [GeForce RTX 3060 Lite Hash Rate] driver: nvidia v: 535.104.05 Device-2: Lenovo 500 RGB Camera driver: uvcvideo type: USB Display: server: X.Org v: 23.2 with: Xwayland v: 23.2.0 driver: X: loaded: nvidia unloaded: fbdev,modesetting,nouveau,vesa gpu: nvidia,nvidia-nvswitch resolution: 1: 1920x1080~60Hz 2: 1920x1080~60Hz API: OpenGL v: 4.6.0 NVIDIA 535.104.05 renderer: NVIDIA GeForce RTX 3060/PCIe/SSE2 -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 473758] Discover keeps on showing "updates available" system tray icon even when there are none
https://bugs.kde.org/show_bug.cgi?id=473758 --- Comment #3 from Riccardo Robecchi --- (In reply to Nate Graham from comment #2) > Did you previously update the system using your command-line package manager? I updated some packages because they couldn't be updated by Discover: they simply didn't show up as available and I had to update them manually by specifying the version. Maybe there are other packages like that? But they don't come up in any package manager, so I wouldn't know how to track them down. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 466380] kwin_x11 crashes in KWin::X11Window::finishCompositing() when disabling compositing
https://bugs.kde.org/show_bug.cgi?id=466380 Bug Janitor Service changed: What|Removed |Added Priority|NOR |HI -- You are receiving this mail because: You are watching all bug changes.
[korganizer] [Bug 418811] Events stored in the database not displayed in KOrganizer
https://bugs.kde.org/show_bug.cgi?id=418811 --- Comment #15 from d...@newtech.fi --- And some more interesting info: Merging the ATTENDEE continuation lines to one long line for each attendee also made the ics work correctly in korganizer. This means that the bug is in the way korganizer handles a continuation line in the form: This legal ICS line does not work: ATTENDEE;CN=Some Name ;RSVP=TRUE;PARTSTAT=NEEDS-ACTION; ROLE=OPT-PARTICIPANT;CUTYPE=INDIVIDUAL;X-UID=94249726501648:mailto: some.n...@organisation.com This line does work: ATTENDEE;CN=Some Name ;RSVP=TRUE;PARTSTAT=NEEDS-ACTION; ROLE=OPT-PARTICIPANT;CUTYPE=INDIVIDUAL;X-UID=94249726501648:mailto: some.n...@organisation.com -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 473768] Windows black out after some time
https://bugs.kde.org/show_bug.cgi?id=473768 --- Comment #3 from Nate Graham --- Thank you for the apology, I accept it and appreciate the gesture. I'm glad yo managed to find a fix. -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 473824] Shortcut for screenshot stopped working
https://bugs.kde.org/show_bug.cgi?id=473824 --- Comment #3 from Nate Graham --- So everything's working again? -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 473869] Clip offset at beginning and/or end of "Wipe"
https://bugs.kde.org/show_bug.cgi?id=473869 --- Comment #1 from fehler-im-progr...@posteo.de --- Created attachment 161249 --> https://bugs.kde.org/attachment.cgi?id=161249=edit Testbild.png -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 473869] New: Clip offset at beginning and/or end of "Wipe"
https://bugs.kde.org/show_bug.cgi?id=473869 Bug ID: 473869 Summary: Clip offset at beginning and/or end of "Wipe" Classification: Applications Product: kdenlive Version: 23.08.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Effects & Transitions Assignee: j...@kdenlive.org Reporter: fehler-im-progr...@posteo.de Target Milestone: --- Created attachment 161248 --> https://bugs.kde.org/attachment.cgi?id=161248=edit Bug "Wipe" offset.kdenlive STEPS TO REPRODUCE 1. Insert any Clip 2. Add "Wipe" 3. Watch the clip at the beginning and/or at the end of the wipe OBSERVED RESULT Clip offset EXPECTED RESULT Clip remains unchanged -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 448866] [NVIDIA] Graphical glitches and unresponsive after waking from sleep
https://bugs.kde.org/show_bug.cgi?id=448866 Nate Graham changed: What|Removed |Added CC||entangled_mousiness015@flam ||ingohippo.com --- Comment #9 from Nate Graham --- *** Bug 473819 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 473819] Environment becomes "glitchy" when monitors are awoken from sleep
https://bugs.kde.org/show_bug.cgi?id=473819 Nate Graham changed: What|Removed |Added CC||n...@kde.org Status|REPORTED|RESOLVED Resolution|--- |DUPLICATE --- Comment #2 from Nate Graham --- *** This bug has been marked as a duplicate of bug 448866 *** -- You are receiving this mail because: You are watching all bug changes.
[korganizer] [Bug 418811] Events stored in the database not displayed in KOrganizer
https://bugs.kde.org/show_bug.cgi?id=418811 --- Comment #14 from d...@newtech.fi --- A bit more info on this: 1. Took the ics file for an event that did not show up 2. Edited the ics file removing all the ATTENDEE lines with continuation lines 3. Imported the file into korganizer and it did show up. Importing the unedited file did show up in akonadiconsole, but not in korganizer. -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 473824] Shortcut for screenshot stopped working
https://bugs.kde.org/show_bug.cgi?id=473824 --- Comment #2 from php4...@gmail.com --- > Do *any* global shortcuts work? Meta+Shift+D for Desktop was definitely working. I've already restarted since then so I don't know about any other. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 473779] Window transparency labels are misleading and "restore button not working"?
https://bugs.kde.org/show_bug.cgi?id=473779 Ismael Asensio changed: What|Removed |Added Resolution|--- |WORKSFORME Status|REPORTED|NEEDSINFO --- Comment #1 from Ismael Asensio --- Hi! Thanks for your bug report but I don't understand exactly what the bug is. The label reads opacity and the default was already fixed to be 100%. Meaning opacity 100% = no transparency and opacity 0% no visibility. The mentioned video was recorded before that default was changed. Is the default still 0% by default ifor you instead of 100% when adding an opacity property? We discussed before about limiting the value to avoid users making a mistake. But window rules is considered an advanced feature and we shouldn't limit what users can do with it, because it is precisely meant for niche cases to override the regular functionally of some windows. The module already warns against applying any rule to all windows without filtering by class or window type. -- You are receiving this mail because: You are watching all bug changes.
[kphotoalbum] [Bug 473762] KPhotoAlbum crashes when Viewer and Annotations is open and then user right-clicks Show Info in Viewer
https://bugs.kde.org/show_bug.cgi?id=473762 --- Comment #5 from Tobias Leupold --- Yeah, of course – but we can store the QByteArray in a QConfig/KConfig without a problem. We actually already do so (cf. MainWindow/State). Well, but that's another question that we should maybe discuss elsewhere. I don't want to hijack the bug ;-) Maybe I should simply implement storing that in the config (and also moving possibly existing layout data) in a branch so that you can check it out. However thanks again and kudos to Victor for finding another crash and writing another useful bug report :-D -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 473758] Discover keeps on showing "updates available" system tray icon even when there are none
https://bugs.kde.org/show_bug.cgi?id=473758 Nate Graham changed: What|Removed |Added CC||n...@kde.org --- Comment #2 from Nate Graham --- Did you previously update the system using your command-line package manager? -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 473735] No MouseEvents are passed to QToolButtons on a custom QSplitterHandle
https://bugs.kde.org/show_bug.cgi?id=473735 Nate Graham changed: What|Removed |Added Status|REPORTED|CONFIRMED CC||n...@kde.org Ever confirmed|0 |1 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 473714] Global Menu sometimes shows menu from non-active app
https://bugs.kde.org/show_bug.cgi?id=473714 Nate Graham changed: What|Removed |Added CC||k...@privat.broulik.de, ||mvourla...@gmail.com, ||n...@kde.org Component|General |Global Menu Target Milestone|--- |1.0 Product|kdeplasma-addons|plasmashell Resolution|--- |WAITINGFORINFO Status|REPORTED|NEEDSINFO --- Comment #1 from Nate Graham --- When it's in this state, is another app active? Or is Plasma itself active? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 473712] Plasmashell crashing on wayland when opening Yakuake
https://bugs.kde.org/show_bug.cgi?id=473712 Nate Graham changed: What|Removed |Added Component|general |generic-crash CC||n...@kde.org --- Comment #2 from Nate Graham --- Cannot reproduce in Plasma 6. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 466380] kwin_x11 crashes in KWin::X11Window::finishCompositing() when disabling compositing
https://bugs.kde.org/show_bug.cgi?id=466380 Nate Graham changed: What|Removed |Added CC||michael.lucky.maximus@gmail ||.com --- Comment #13 from Nate Graham --- *** Bug 473800 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 473800] Kwin crashed after changing fonts.
https://bugs.kde.org/show_bug.cgi?id=473800 Nate Graham changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |DUPLICATE CC||n...@kde.org --- Comment #1 from Nate Graham --- *** This bug has been marked as a duplicate of bug 466380 *** -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 473768] Windows black out after some time
https://bugs.kde.org/show_bug.cgi?id=473768 --- Comment #2 from voncl...@gmail.com --- Fair enough I was frustrated at the time of writing this so I apologize I "think" i found a fix for it with firefox disabling EGL and enabling GFX anyway I apologize for my lack of respect. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 473804] When Global Menu is used I can't open Google Chrome browser in incognito mode
https://bugs.kde.org/show_bug.cgi?id=473804 Nate Graham changed: What|Removed |Added Status|REPORTED|RESOLVED CC||n...@kde.org Resolution|--- |DOWNSTREAM --- Comment #1 from Nate Graham --- Can reproduce in Plasma 6 too with Chromium. It looks like it crashes. Unfortunately even with full debug symbols, my backtrace is empty: #0 0x55586d16d98e in () #1 0x555877623500 in () #2 0x7ffc7694e168 in () #3 0x13b402621a40 in () #4 0x13b402621a68 in () #5 0x in () So I would recommend that you report this to the Chromium devs at this point. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 473450] Create a field in Digikam Settings GUI: "User's Google Maps API key"
https://bugs.kde.org/show_bug.cgi?id=473450 --- Comment #20 from caulier.gil...@gmail.com --- QWebView is not QWebKit at all. QWebWiew host a native browser in a QtWidget. this do not implement a web browser as QWebkit or QWebEngine. QWebWiew is a QML part. The goal is to able to render a web page with the native html engine without to use a dedicated code. This is necessary for some platforms as ios where Apple deny to install and use a different web browser than Safari. and yes, Chrome and Firefox under IOS are just a container for Safari. QWebView already exists in Qt 6 as you can see here : https://doc.qt.io/qt-6/qtwebview-index.html ... but as you can read, QWebView under Windows use QWebEngine... So, it's not the right solution... Gilles -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 473768] Windows black out after some time
https://bugs.kde.org/show_bug.cgi?id=473768 Nate Graham changed: What|Removed |Added Status|RESOLVED|CLOSED -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 473768] Windows black out after some time
https://bugs.kde.org/show_bug.cgi?id=473768 Nate Graham changed: What|Removed |Added CC||n...@kde.org Status|REPORTED|RESOLVED Resolution|--- |NOT A BUG --- Comment #1 from Nate Graham --- > god forbid > it sucks honestly and I doubt the dev's here will do anything about it. You > never fix anything > I can almost guarantee this post will be met with "Just you brah" > KDE sucks Bad attitude means I don't want to provide you with free support. If you hate our software so much, feel free to use someone else's. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 472483] The Calendar applet randomly displays holidays from the default region instead of the selected one
https://bugs.kde.org/show_bug.cgi?id=472483 --- Comment #1 from popov895 --- The reason is very strange: after closing any instance of `KFileDialog`, `KConfigWatcher` emits a `configChanged` signal, where the name of the `group` is "KFileDialog Settings", although there is no group with such a name in the given configuration file. Therefore, we need to check the name of the `group`in the handler of the `configChanged` signal. -- You are receiving this mail because: You are watching all bug changes.
