[plasmashell] [Bug 487112] Renaming file on desktop has a visual glitch
https://bugs.kde.org/show_bug.cgi?id=487112 Joe Jahnessen changed: What|Removed |Added Assignee|unassigned-b...@kde.org |plasma-b...@kde.org Component|general |Icon Product|kde |plasmashell Version|unspecified |6.0.4 Target Milestone|--- |1.0 -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 487112] Renaming file on desktop has a visual glitch
https://bugs.kde.org/show_bug.cgi?id=487112 Joe Jahnessen changed: What|Removed |Added Product|dolphin |kde Version|24.02.2 |unspecified Assignee|dolphin-bugs-n...@kde.org |unassigned-b...@kde.org Component|view-engine: icons mode |general -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 487112] New: Renaming file on desktop has a visual glitch
https://bugs.kde.org/show_bug.cgi?id=487112 Bug ID: 487112 Summary: Renaming file on desktop has a visual glitch Classification: Applications Product: dolphin Version: 24.02.2 Platform: Manjaro OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: view-engine: icons mode Assignee: dolphin-bugs-n...@kde.org Reporter: j...@pxl.one CC: kfm-de...@kde.org Target Milestone: --- Created attachment 169536 --> https://bugs.kde.org/attachment.cgi?id=169536=edit Visual glitch *** If you're not sure this is actually a bug, instead post about it at https://discuss.kde.org If you're reporting a crash, attach a backtrace with debug symbols; see https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** SUMMARY When renaming a file on the desktop, either by clicking once on the file name, or by pressing F2, or by right click->rename the selected previous filename remains visible under the new filename that is being typed in. STEPS TO REPRODUCE 1. Enter file rename mode on a desktop icon (F2, or right click-rename, or single click on file name) OBSERVED RESULT 1. current filename is selected (which is expected) 2. while typing new name, the new text is shown over the old file-name, making the result illegible) 3. when the renaming is finished, the new name is showed correctly EXPECTED RESULT When typing new filename the old one should disappear completely, especially if the text is preselected. SOFTWARE/OS VERSIONS Operating System: Manjaro Linux KDE Plasma Version: 6.0.4 KDE Frameworks Version: 6.2.0 Qt Version: 6.7.0 Kernel Version: 6.6.30-3-MANJARO (64-bit) Graphics Platform: X11 Dolphin version 24.02.2 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[krdc] [Bug 482950] KRDC RDP Blue screen shows nothing
https://bugs.kde.org/show_bug.cgi?id=482950 --- Comment #15 from Joe S --- (In reply to Jesús Martínez Novo (Ciencia Al Poder) from comment #13) > I had to downgrade to krdc-23.08.4 to continue using it because of this same > problem. And some weeks ago I had to downgrade to freerdp-2.11.2 too, > because OpenSuSE Tumbleweed pushed a new version of freerdp which changes > several command line parameters, causing it to be incompatible with krdc 23 Where did you get krdc 23.08 or did you compile yourself ? -- You are receiving this mail because: You are watching all bug changes.
[krdc] [Bug 482950] KRDC RDP Blue screen shows nothing
https://bugs.kde.org/show_bug.cgi?id=482950 --- Comment #14 from Joe S --- (In reply to Jesús Martínez Novo (Ciencia Al Poder) from comment #13) > I had to downgrade to krdc-23.08.4 to continue using it because of this same > problem. And some weeks ago I had to downgrade to freerdp-2.11.2 too, > because OpenSuSE Tumbleweed pushed a new version of freerdp which changes > several command line parameters, causing it to be incompatible with krdc 23 Where did you get the older version of krdc or did you compile yourself ? -- You are receiving this mail because: You are watching all bug changes.
[krdc] [Bug 482950] KRDC RDP Blue screen shows nothing
https://bugs.kde.org/show_bug.cgi?id=482950 --- Comment #11 from Joe S --- This problem just seems to get worse with each update. I have replicated it on a Tumbleweed vm running the latest build 20240507. My KDE Neon test environment updated to the last version just displays the blue screen that everyone else is complaining about. Those are NEW fresh installations that were updated to the latest builds so nothing in the current environment where the problem was originally found comes into play. Trying to connect using krdc 24.02.2 now just core dumps systemd-coredump[758]: [] Process 744 (krdc) of user 1000 dumped core. Stack trace of thread 744: #0 0x7fee3c013bf1 n/a (libkrdc_rdpplugin.so + 0xebf1) #1 0x7fee3c01948d n/a (libkrdc_rdpplugin.so + 0x1448d) #2 0x7fee43ddc245 _ZN15HostPreferences10showDialogEP7QWidget (libkrdccore.so.5 + 0xb245) #3 0x5619e047d93b n/a (krdc + 0x3293b) #4 0x5619e0467017 n/a (krdc + 0x1c017) #5 0x7fee4162a1f0 __libc_start_call_main (libc.so.6 + 0x2a1f0) #6 0x7fee4162a2b9 __libc_start_main@@GLIBC_2.34 (libc.so.6 + 0x2a2b9) #7 0x5619e04672d5 n/a (krdc + 0x1c2d5) Stack trace of thread 745: #0 0x7fee4170578f __poll (libc.so.6 + 0x10578f) #1 0x7fee405ce2ff n/a (libglib-2.0.so.0 + 0x5f2ff) #2 0x7fee405cea0c g_main_context_iteration (libglib-2.0.so.0 + 0x5fa0c) #3 0x7fee421c0a8c _ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEve> #4 0x7fee41f9979b _ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE (libQt6Core.so.6 + 0> #5 0x7fee42074cb4 _ZN7QThread4execEv (libQt6Core.so.6 + 0x274cb4) #6 0x7fee41d7b6fa n/a (libQt6DBus.so.6 + 0x386fa) #7 0x7fee420ecea9 n/a (libQt6Core.so.6 + 0x2ecea9) #8 0x7fee41692bb2 start_thread (libc.so.6 + 0x92bb2) #9 0x7fee4171400c __clone3 (libc.so.6 + 0x11400c) Stack trace of thread 747: #0 0x7fee4168effe __futex_abstimed_wait_common (libc.so.6 + 0x8effe) #1 0x7fee41691d40 pthread_cond_wait@@GLIBC_2.3.2 (libc.so.6 + 0x91d40) #2 0x7fee35d10e5b n/a (iris_dri.so + 0x110e5b) #3 0x7fee35d06e67 n/a (iris_dri.so + 0x106e67) #4 0x7fee41692bb2 start_thread (libc.so.6 + 0x92bb2) #5 0x7fee4171400c __clone3 (libc.so.6 + 0x11400c) Stack trace of thread 746: #0 0x7fee4170578f __poll (libc.so.6 + 0x10578f) #1 0x7fee3f6ed8aa n/a (libxcb.so.1 + 0xe8aa) #2 0x7fee3f6ef41c xcb_wait_for_event (libxcb.so.1 + 0x1041c) #3 0x7fee3dd34e30 n/a (libQt6XcbQpa.so.6 + 0x5de30) #4 0x7fee420ecea9 n/a (libQt6Core.so.6 + 0x2ecea9) #5 0x7fee41692bb2 start_thread (libc.so.6 + 0x92bb2) #6 0x7fee4171400c __clone3 (libc.so.6 + 0x11400c) Stack trace of thread 748: #0 0x7fee4168effe __futex_abstimed_wait_common (libc.so.6 + 0x8effe) #1 0x7fee41691d40 pthread_cond_wait@@GLIBC_2.3.2 (libc.so.6 + 0x91d40) #2 0x7fee35d10e5b n/a (iris_dri.so + 0x110e5b) #3 0x7fee35d06e67 n/a (iris_dri.so + 0x106e67) #4 0x7fee41692bb2 start_thread (libc.so.6 + 0x92bb2) #5 0x7fee4171400c __clone3 (libc.so.6 + 0x
[dolphin] [Bug 471279] Dolphin crash when dragging files or folders across or to the path navigation bar
https://bugs.kde.org/show_bug.cgi?id=471279 Joe Hillenbrand changed: What|Removed |Added Latest Commit||0b87f091c08a3f7ec4e03552e9d ||c1ec042368e98 -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 471279] Dolphin crash when dragging files or folders across or to the path navigation bar
https://bugs.kde.org/show_bug.cgi?id=471279 Joe Hillenbrand changed: What|Removed |Added CC||joehil...@gmail.com --- Comment #17 from Joe Hillenbrand --- It's very easy to replicate the crash. I built dolphin from source and got this backtrace: Commit: 0b87f091c (committed 2 days ago) Qt Version: 6.7.0 OS: Arch Linux ``` AddressSanitizer:DEADLYSIGNAL = ==1284081==ERROR: AddressSanitizer: SEGV on unknown address 0x0008 (pc 0x7afa21989567 bp 0x7ffc80ed3750 sp 0x7ffc80ed3370 T0) ==1284081==The signal is caused by a READ memory access. ==1284081==Hint: address points to the zero page. #0 0x7afa21989567 in QObject::deleteLater() (/usr/lib/libQt6Core.so.6+0x189567) (BuildId: 872d4adf2baec6d9d68181290c645df59a742af6) #1 0x7afa26d97ccd (/usr/lib/libKF6KIOFileWidgets.so.6+0xb3ccd) (BuildId: dec15e4e4929ebff7afe5938e4239f0b3f2d6332) #2 0x7afa229470d2 in QWidget::event(QEvent*) (/usr/lib/libQt6Widgets.so.6+0x1470d2) (BuildId: 1acc2a5af715a07a49da84d032ad4729ba05d7dc) #3 0x7afa228fbfca in QApplicationPrivate::notify_helper(QObject*, QEvent*) (/usr/lib/libQt6Widgets.so.6+0xfbfca) (BuildId: 1acc2a5af715a07a49da84d032ad4729ba05d7dc) #4 0x7afa22900d13 in QApplication::notify(QObject*, QEvent*) (/usr/lib/libQt6Widgets.so.6+0x100d13) (BuildId: 1acc2a5af715a07a49da84d032ad4729ba05d7dc) #5 0x7afa2193dae7 in QCoreApplication::notifyInternal2(QObject*, QEvent*) (/usr/lib/libQt6Core.so.6+0x13dae7) (BuildId: 872d4adf2baec6d9d68181290c645df59a742af6) #6 0x7afa2295dcf8 (/usr/lib/libQt6Widgets.so.6+0x15dcf8) (BuildId: 1acc2a5af715a07a49da84d032ad4729ba05d7dc) #7 0x7afa228fbfca in QApplicationPrivate::notify_helper(QObject*, QEvent*) (/usr/lib/libQt6Widgets.so.6+0xfbfca) (BuildId: 1acc2a5af715a07a49da84d032ad4729ba05d7dc) #8 0x7afa2193dae7 in QCoreApplication::notifyInternal2(QObject*, QEvent*) (/usr/lib/libQt6Core.so.6+0x13dae7) (BuildId: 872d4adf2baec6d9d68181290c645df59a742af6) #9 0x7afa21f7ae6f in QGuiApplicationPrivate::processDrag(QWindow*, QMimeData const*, QPoint const&, QFlags, QFlags, QFlags) (/usr/lib/libQt6Gui.so.6+0x17ae6f) (BuildId: 40a99cfcaa356361693738c54ac28acf17c748bf) #10 0x7afa21fdefa0 in QWindowSystemInterface::handleDrag(QWindow*, QMimeData const*, QPoint const&, QFlags, QFlags, QFlags) (/usr/lib/libQt6Gui.so.6+0x1defa0) (BuildId: 40a99cfcaa356361693738c54ac28acf17c748bf) #11 0x7afa1b7d9e34 (/usr/lib/qt6/plugins/platforms/../../../libQt6XcbQpa.so.6+0x78e34) (BuildId: 184891fbb629a38454181bc5310f9526cb75ac9e) #12 0x7afa1b7dae18 (/usr/lib/qt6/plugins/platforms/../../../libQt6XcbQpa.so.6+0x79e18) (BuildId: 184891fbb629a38454181bc5310f9526cb75ac9e) #13 0x7afa222f5229 in QBasicDrag::eventFilter(QObject*, QEvent*) (/usr/lib/libQt6Gui.so.6+0x4f5229) (BuildId: 40a99cfcaa356361693738c54ac28acf17c748bf) #14 0x7afa2193c977 in QCoreApplicationPrivate::sendThroughApplicationEventFilters(QObject*, QEvent*) (/usr/lib/libQt6Core.so.6+0x13c977) (BuildId: 872d4adf2baec6d9d68181290c645df59a742af6) #15 0x7afa228fc0a1 in QApplicationPrivate::notify_helper(QObject*, QEvent*) (/usr/lib/libQt6Widgets.so.6+0xfc0a1) (BuildId: 1acc2a5af715a07a49da84d032ad4729ba05d7dc) #16 0x7afa2193dae7 in QCoreApplication::notifyInternal2(QObject*, QEvent*) (/usr/lib/libQt6Core.so.6+0x13dae7) (BuildId: 872d4adf2baec6d9d68181290c645df59a742af6) #17 0x7afa21f720e4 in QGuiApplicationPrivate::processMouseEvent(QWindowSystemInterfacePrivate::MouseEvent*) (/usr/lib/libQt6Gui.so.6+0x1720e4) (BuildId: 40a99cfcaa356361693738c54ac28acf17c748bf) #18 0x7afa21fdcfdb in QWindowSystemInterface::sendWindowSystemEvents(QFlags) (/usr/lib/libQt6Gui.so.6+0x1dcfdb) (BuildId: 40a99cfcaa356361693738c54ac28acf17c748bf) #19 0x7afa1b7adb9e (/usr/lib/qt6/plugins/platforms/../../../libQt6XcbQpa.so.6+0x4cb9e) (BuildId: 184891fbb629a38454181bc5310f9526cb75ac9e) #20 0x7afa2010d198 (/usr/lib/libglib-2.0.so.0+0x5a198) (BuildId: 0a2311dfbbc6c215dc36f4b6bdd2b4b6fbae55a2) #21 0x7afa2016c3be (/usr/lib/libglib-2.0.so.0+0xb93be) (BuildId: 0a2311dfbbc6c215dc36f4b6bdd2b4b6fbae55a2) #22 0x7afa2010c711 in g_main_context_iteration (/usr/lib/libglib-2.0.so.0+0x59711) (BuildId: 0a2311dfbbc6c215dc36f4b6bdd2b4b6fbae55a2) #23 0x7afa21b83df3 in QEventDispatcherGlib::processEvents(QFlags) (/usr/lib/libQt6Core.so.6+0x383df3) (BuildId: 872d4adf2baec6d9d68181290c645df59a742af6) #24 0x7afa21945c7d in QEventLoop::exec(QFlags) (/usr/lib/libQt6Core.so.6+0x145c7d) (BuildId: 872d4adf2baec6d9d68181290c645df59a742af6) #25 0x7afa222f0899 in QBasicDrag::drag(QDrag*) (/usr/lib/libQt6Gui.so.6+0x4f0899) (BuildId: 40a99cfcaa356361693738c54ac28acf17c748bf) #26 0x7afa222f1a28 in QDragManager::drag(QDrag*) (/usr/lib/libQt6Gui.so.6+0x4f1a28)
[calligrasheets] [Bug 485855] New: Crash after entering value in cell of newly created column
https://bugs.kde.org/show_bug.cgi?id=485855 Bug ID: 485855 Summary: Crash after entering value in cell of newly created column Classification: Applications Product: calligrasheets Version: 3.2.1 Platform: Ubuntu OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: calligra-sheets-bugs-n...@kde.org Reporter: joej...@gmail.com Target Milestone: --- Application: calligrasheets (3.2.1) Qt Version: 5.15.10 Frameworks Version: 5.110.0 Operating System: Linux 6.5.0-28-generic x86_64 Windowing System: X11 Distribution: Ubuntu 23.10 DrKonqi: 5.27.8 [KCrashBackend] -- Information about the crash: Created new column Enter vaue in to cell of new coulmn Press enter => crash Happened several times, each time. The crash can be reproduced every time. -- Backtrace: Application: Calligra Sheets (calligrasheets), signal: Segmentation fault [KCrash Handler] #4 0x7f9a1f1510bc in Calligra::Sheets::StyleStorage::invalidateCache() () from /lib/x86_64-linux-gnu/libcalligrasheetsodf.so.17 #5 0x7f9a1f11f72a in Calligra::Sheets::Map::handleDamages(QList const&) () from /lib/x86_64-linux-gnu/libcalligrasheetsodf.so.17 #6 0x7f9a2c90602d in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7f9a1f062136 in Calligra::Sheets::Map::damagesFlushed(QList const&) () from /lib/x86_64-linux-gnu/libcalligrasheetsodf.so.17 #8 0x7f9a1f1199ac in Calligra::Sheets::Map::flushDamages() () from /lib/x86_64-linux-gnu/libcalligrasheetsodf.so.17 #9 0x7f9a2c8f99a0 in QObject::event(QEvent*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #10 0x7f9a2cd6bc82 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #11 0x7f9a2d76e8bb in KoApplication::notify(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libkomain.so.17 #12 0x7f9a2c8cc7a8 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #13 0x7f9a2c8cfeb1 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #14 0x7f9a2c9286f7 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #15 0x7f9a2a113b2c in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #16 0x7f9a2a16f46f in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #17 0x7f9a2a111d20 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #18 0x7f9a2c927daa in QEventDispatcherGlib::processEvents(QFlags) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #19 0x7f9a2c8cb15b in QEventLoop::exec(QFlags) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #20 0x7f9a2c8d3904 in QCoreApplication::exec() () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #21 0x7f9a2dad3d63 in kdemain () from /lib/x86_64-linux-gnu/libkdeinit5_calligrasheets.so #22 0x7f9a2d828150 in __libc_start_call_main (main=main@entry=0x5839f838e060, argc=argc@entry=2, argv=argv@entry=0x7ffe45b9b388) at ../sysdeps/nptl/libc_start_call_main.h:58 #23 0x7f9a2d828209 in __libc_start_main_impl (main=0x5839f838e060, argc=2, argv=0x7ffe45b9b388, init=, fini=, rtld_fini=, stack_end=0x7ffe45b9b378) at ../csu/libc-start.c:360 #24 0x5839f838e095 in ?? () [Inferior 1 (process 11479) detached] The reporter indicates this bug may be a duplicate of or related to bug 421067. Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[krdc] [Bug 483638] TAB key not functional inside rdp windows client
https://bugs.kde.org/show_bug.cgi?id=483638 Joe S changed: What|Removed |Added CC||jmscdba+...@gmail.com --- Comment #5 from Joe S --- I have been trying to resolve the same problem with the tab key not working in a RDP sessions but I am connecting to xrdp on a linux server. As an example, if I run konsole in the rdp session and type ls -al and press the tab key it does not show the matches immediately ( .inputrc has set-show-all-if-ambiguous on ). If I connect using xfreerdp instead of krdc, then the tab key works perfectly in konsole. The konsole client is NOT the problem because I can replicate the tab key broken using libreoffice calc too. Start libreoffice calc ( cursor is in cell A1 ), press tab, nothing happens if you are using krdc client. Switch to using xfreerdp instead of krdc and the tab key works correctly in the rdp session moving the cursor to B1. IMHO, it seems like the tab key is being "consumed" by something instead of the current process. I say this because when using krdc and pressing tab ( whether in konsole or libreoffice calc ) those applications no longer respond to keystrokes, however, if you click on anything else ( the desktop background, another app, the taskbar ) to switch focus and then click back on the application ( either konsole or libreoffice calc ) then keystrokes are accepted again and until you press tab key again. My platform is openSUSE Tumbleweed 20240329 but I have replicated on 20240412 too. -- You are receiving this mail because: You are watching all bug changes.
[kstars] [Bug 485501] so many bugs i cant report all of them...lossy kstars actions when you try to do things
https://bugs.kde.org/show_bug.cgi?id=485501 --- Comment #1 from joe --- Created attachment 168469 --> https://bugs.kde.org/attachment.cgi?id=168469=edit button dont work why are buttons grey out.. and dont work -- You are receiving this mail because: You are watching all bug changes.
[kstars] [Bug 485501] New: so many bugs i cant report all of them...lossy kstars actions when you try to do things
https://bugs.kde.org/show_bug.cgi?id=485501 Bug ID: 485501 Summary: so many bugs i cant report all of them...lossy kstars actions when you try to do things Classification: Applications Product: kstars Version: 3.7.0 Platform: Microsoft Windows OS: Microsoft Windows Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: mutla...@ikarustech.com Reporter: joeas...@aol.com Target Milestone: --- first bug: when i boot kstars on pc.. it does not center the kstars window on the screen.. it is always down to the right. cant you calculate from java or python the screen size in use and center it??? you cant put a square camera.. zwo or canon or nikon in the FOV display and get the square to work. it alwasys put athe circle on... why cant you use the FOV entered for the saved finders. or the telescope. there is no way to tell the FOV to use telescope X? or dslr lens X? or barlow X? etc...the lists are useless...in kstars. also the FOV button on the menus above does not work.. why are they greyed out! there is no save button on most of the INPUT windows... FOV for example.. only OK and cancel.. no save. no ADD+ joe -- You are receiving this mail because: You are watching all bug changes.
[kstars] [Bug 485500] New: so many bugs i cant report all of them...lossy kstars actions when you try to do things
https://bugs.kde.org/show_bug.cgi?id=485500 Bug ID: 485500 Summary: so many bugs i cant report all of them...lossy kstars actions when you try to do things Classification: Applications Product: kstars Version: 3.7.0 Platform: Microsoft Windows OS: Microsoft Windows Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: mutla...@ikarustech.com Reporter: joeas...@aol.com Target Milestone: --- Created attachment 168468 --> https://bugs.kde.org/attachment.cgi?id=168468=edit fov not square.. and you cant set the size first bug: when i boot kstars on pc.. it does not center the kstars window on the screen.. it is always down to the right. cant you calculate from java or python the screen size in use and center it??? you cant put a square camera.. zwo or canon or nikon in the FOV display and get the square to work. it alwasys put athe circle on... why cant you use the FOV entered for the saved finders. or the telescope. there is no way to tell the FOV to use telescope X? or dslr lens X? or barlow X? etc...the lists are useless...in kstars. also the FOV button on the menus above does not work.. why are they greyed out! there is no save button on most of the INPUT windows... FOV for example.. only OK and cancel.. no save. no ADD+ joe -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 485084] New: Screen Locker broken on resume from sleep
https://bugs.kde.org/show_bug.cgi?id=485084
Bug ID: 485084
Summary: Screen Locker broken on resume from sleep
Classification: Plasma
Product: kscreenlocker
Version: 6.0.3
Platform: Arch Linux
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: general
Assignee: plasma-b...@kde.org
Reporter: jchevar...@gmail.com
Target Milestone: ---
SUMMARY
I am getting kscreenlocker failing rather regularly on my desktop (AMD GPU)
system. Intel GPU laptop haven't reproduced. I used to get this on occasion if
I say upgraded to a new Plasma release in the 5.x days and didn't reboot. This
seems different and unrelated to upgrading my system. I've included the
journalcrtl log which starts with a seg fault in eglSwapBuffers. Doesn't happen
all the time, but happens enough that it is pretty annoying (and effectively
locks the better half/others out of the computer as they don't really know what
a virtual terminal is).
STEPS TO REPRODUCE
1. Lock Screen
2. Sleep computer
3. Wake Computer
OBSERVED RESULT
Quite often the lock screen presents the broken screen requesting to drop to
virtual terminal to unlock
EXPECTED RESULT
Lock screen should be shown
SOFTWARE/OS VERSIONS
Operating System: Arch Linux
KDE Plasma Version: 6.0.3
KDE Frameworks Version: 6.0.0
Qt Version: 6.6.3
Kernel Version: 6.8.2-arch2-1 (64-bit)
Graphics Platform: Wayland
Processors: 24 × AMD Ryzen 9 5900X 12-Core Processor
Memory: 31.3 GiB of RAM
Graphics Processor: AMD Radeon RX 6900 XT
ADDITIONAL INFORMATION
Here is what I can find in journalcrtl:
Apr 05 10:13:24 desktop kscreenlocker_greet[122558]: qt.qpa.wayland:
eglSwapBuffers failed with 0x300d, surface: 0x0
Apr 05 10:13:24 desktop kernel: kscreenlocker_g[122558]: segfault at
64750076 ip 7dc46da45c4c sp 7fff90b0f380 error 4 in
libPlasmaQuick.so.6.0.3[7dc46da1f000+5] likely on CPU 18 (core 8, socket 0)
Apr 05 10:13:24 desktop kernel: Code: 1e fa 48 8b 47 28 48 8b 78 08 ff 25 a6 58
04 00 66 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 00 f3 0f 1e fa 48 83 ec 08 48 8b
47 28 <48> 8b 78 08 ff 15 1a 6a 04 00 48 85 c0 74 11 48 8b 50 08 f6 42 31
Apr 05 10:13:24 desktop kwin_wayland_wrapper[97857]: not a valid new object id
(2), message get_registry(n)
Apr 05 10:13:24 desktop kwin_wayland_wrapper[97857]: error in client
communication (pid 97857)
Apr 05 10:13:24 desktop kwin_wayland_wrapper[122896]: wl_display@1: error 1:
invalid arguments for wl_display@1.get_registry
Apr 05 10:13:24 desktop kscreenlocker_greet[122896]: qt.qpa.wayland: Loading
shell integration failed.
Apr 05 10:13:24 desktop kscreenlocker_greet[122896]: qt.qpa.wayland: Attempted
to load the following shells QList("layer-shell")
Apr 05 10:13:24 desktop kscreenlocker_greet[122896]: qt.qpa.plugin: Could not
load the Qt platform plugin "wayland" in "" even though it was found.
Apr 05 10:13:24 desktop kscreenlocker_greet[122896]: This application failed to
start because no Qt platform plugin could be initialized. Reinstalling the
application may fix this problem.
Available platform plugins
are: xcb, linuxfb, minimalegl, vnc, eglfs, offscreen, minimal, wayland-egl,
wayland, vkkhrdisplay.
Apr 05 10:13:24 desktop kscreenlocker_greet[122900]: qt.qpa.wayland: Loading
shell integration failed.
Apr 05 10:13:24 desktop kscreenlocker_greet[122900]: qt.qpa.wayland: Attempted
to load the following shells QList("layer-shell")
Apr 05 10:13:24 desktop kscreenlocker_greet[122900]: qt.qpa.plugin: Could not
load the Qt platform plugin "wayland" in "" even though it was found.
Apr 05 10:13:24 desktop kscreenlocker_greet[122900]: This application failed to
start because no Qt platform plugin could be initialized. Reinstalling the
application may fix this problem.
Available platform plugins
are: xcb, linuxfb, minimalegl, vnc, eglfs, offscreen, minimal, wayland-egl,
wayland, vkkhrdisplay.
Apr 05 10:13:24 desktop kscreenlocker_greet[122903]: qt.qpa.wayland: Loading
shell integration failed.
Apr 05 10:13:24 desktop kscreenlocker_greet[122903]: qt.qpa.wayland: Attempted
to load the following shells QList("layer-shell")
Apr 05 10:13:24 desktop kscreenlocker_greet[122903]: qt.qpa.plugin: Could not
load the Qt platform plugin "wayland" in "" even though it was found.
Apr 05 10:13:24 desktop kscreenlocker_greet[122903]: This application failed to
start because no Qt platform plugin could be initialized. Reinstalling the
application may fix this problem.
Available platform plugins
are: xcb, linuxfb, minimalegl, vnc, eglfs, offscreen, minimal, wayland-egl,
wayland, vkkhrdisplay.
Apr 05 10:13:24 desktop plasmashell[98084]: The cached device pixel ratio value
was stale on window expose. Please file a QTBUG which explains how to
reproduce.
--
You are
[kscreenlocker] [Bug 484363] Sometimes, on a multimonitor setup, screen locker fails to unlock screen and shows "Unlock" button that does nothing
https://bugs.kde.org/show_bug.cgi?id=484363 Joe changed: What|Removed |Added CC||jchevar...@gmail.com --- Comment #1 from Joe --- I get this, too, on latest (6.0.3) on Arch. However, if I click the strange lone 'unlock' button again it does actually unlock after that. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 465937] Split does not reset to its original value once "adjacent quick-tiled windows" configuration ceases to exist
https://bugs.kde.org/show_bug.cgi?id=465937 Joe S changed: What|Removed |Added CC||jmscdba+...@gmail.com --- Comment #44 from Joe S --- We have been suffering with these tiling changes for 1 year now and they persist in plasma 6. Use use Meta+LeftArrow and Meta+RArrow all the time but I often end up with the situation where they are consider adjacent windows and resizing one resizes both. We NEED a way to disable this adjacent window resizing or a way to restore the old behavior where adjacent windows do NOT affect each other. I end up closing the apps to break the connection and reopening a total waste of time especially if I am in the middle of something. Resizing the apps does not always work and I sometimes have a situation where I have an app in the bottom left corner and another window that is the right 50% of the screen and I try to resize the window that is on the right 50% and the app in the left corner springs back to using the left 50% of the screen. I was SO MUCH time dealing with this, it is beyond frustrating Please provide a way to disable the new tiling OR at a minimum how to disable the adjacent window resizing. Even Microsoft Windows provides the basic functionality to turn OFF the adjacent snapping which I immediately do. -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 484812] cant start ekos with out a camera.. stupid
https://bugs.kde.org/show_bug.cgi?id=484812 --- Comment #2 from joe --- Sorry but days tring to get things to work on simple problem.I give up on this software. Joe Sent from AOL on Android On Sun, Mar 31, 2024 at 5:50 AM, Nicolas Fella wrote: https://bugs.kde.org/show_bug.cgi?id=484812 Nicolas Fella changed: What |Removed |Added CC| |nicolas.fe...@gmx.de Resolution|--- |NOT A BUG Status|REPORTED |RESOLVED --- Comment #1 from Nicolas Fella --- This is unacceptable behavior. Please follow the Code of Conduct (https://kde.org/code-of-conduct/) and be respectful. Otherwise nobody is going to help you. -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 484812] New: cant start ekos with out a camera.. stupid
https://bugs.kde.org/show_bug.cgi?id=484812 Bug ID: 484812 Summary: cant start ekos with out a camera.. stupid Classification: I don't know Product: kde Version: unspecified Platform: PiSi Linux OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: joeas...@aol.com Target Milestone: --- kstars is bad enough now you click ekos start.. it says " cant start ekos with out camera" stupid.. idits.. i want to run my scope around the sky to view no camera needed to view manually!!! get rid of the camera issue... and fix the darn telescope list.. if you clicck on DEFAULT> it should pop up a warning message that 'YOU need to edit and add your own scopes? [ most programs have a list of standard scopes? not ekos!! joe -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 484811] New: sky view backwards
https://bugs.kde.org/show_bug.cgi?id=484811 Bug ID: 484811 Summary: sky view backwards Classification: I don't know Product: kde Version: unspecified Platform: unspecified OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: joeas...@aol.com Target Milestone: --- on pi4, raspberry pi os, and astroberry OS kstars 3.6.0 down loaded with sudo apt full-upgrade you start up kstars and the planetary is backwards. you dont have a FLIP west to east button? i want west on the right side when it starts. please add flip button on view? joe also there is no MEssier object INPUT list when you run the wizzard and import star lists or ic or ngc where is Messiers object only!!k also i cant not get ekos to show a TELESCOPE list.. i chose mount zwo am5., but no telescope list.. only default? -- You are receiving this mail because: You are watching all bug changes.
[krdc] [Bug 482950] KRDC RDP Blue screen shows nothing
https://bugs.kde.org/show_bug.cgi?id=482950 Joe S changed: What|Removed |Added CC||jmscdba+...@gmail.com --- Comment #6 from Joe S --- I am having a similar problem and have spent DAYS debugging what is going on although my situation is slightly different, I think it may point to the root cause. I am running Tumbleweed 20240319 which has krdc 24.02.0-1.1 but I have replicated the problem on a test machine which is running TW 20240328 ( the latest ) and using krdc 24-02.1-1.1. In my case, initially I have no problems using krdc to connect to the xrdp server. BUT, I need to rename the server that is hosting xrdp and after I rename the server from OLD-NAME to NEW-NAME then BOTH krdc 24.02.0-1.1 and krdc 24.02.1-1.1 experience the BLUE screen and do not get the desktop. Although either krdc version has the blue screen problem, I have no problems remotely connecting using xfreerdp or remmina to the NEW-NAME server and ping and ssh also work using the NEW-NAME. Even Windows 10 clients can connect to NEW-NAME with no issues. Generally the other clients display a unknown certificate error but after you accept and continue then your are logged in and the desktop is displayed. If I rename the server back to OLD-NAME then krdc starts working again. If I rename the server back to NEW-NAME then krdc gets the blue screen again and yet EVERYTHING else works fine with NEW-NAME. I even went as far as building a new VM with a fresh TW install and that VM experiences the same issues. On TW, xrdp uses /usr/bin/xrdp-keygen to generate /etc/xrdp/rsakeys.ini which has the key/cert used by the xrdp connections. If you generate your own key/cert and then modify /etc/xrdp/xrdp.ini to set the certificate= and file_key= lines to the generated files and then restart the xrdp service, then all clients work with NEW-NAME ( after accepting the unknown certificate ) except for krdc. For krdc it displays the unknown certificate message ( unlike when using the keys from rsakeys.ini ) but after selecting Continue you are still left with the blue screen. At one point I even heard the login sound play but still no desktop is displayed with krdc. Since everything else works fine with the NEW-NAME for the server EXCEPT for krdc that seems to point to it being the problem. NOTE: I have renamed xrdp servers in the past and have not run into this problem. Hopefully my detailed analysis helps you to identify what is wrong with krdc. Please let me know if you want more details. -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 483792] Hovering over theme with no visual thumbnail in Window Decorations crashes System Settings
https://bugs.kde.org/show_bug.cgi?id=483792 Joe changed: What|Removed |Added Summary|Navigating to Window|Hovering over theme with no |Decorations crashes System |visual thumbnail in Window |Settings|Decorations crashes System ||Settings -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 483792] Navigating to Window Decorations crashes System Settings
https://bugs.kde.org/show_bug.cgi?id=483792 --- Comment #2 from Joe --- Created attachment 167343 --> https://bugs.kde.org/attachment.cgi?id=167343=edit NixOS programs configuration -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 483792] Navigating to Window Decorations crashes System Settings
https://bugs.kde.org/show_bug.cgi?id=483792 --- Comment #1 from Joe --- Created attachment 167342 --> https://bugs.kde.org/attachment.cgi?id=167342=edit NixOS configuration -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 483792] New: Navigating to Window Decorations crashes System Settings
https://bugs.kde.org/show_bug.cgi?id=483792 Bug ID: 483792 Summary: Navigating to Window Decorations crashes System Settings Classification: I don't know Product: kde Version: unspecified Platform: NixOS OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: contact.gladiusmu...@gmail.com Target Milestone: --- Application: (6.0.2) Qt Version: 6.6.2 Frameworks Version: 6.0.0 Operating System: Linux 6.6.21 x86_64 Windowing System: Wayland Distribution: NixOS 24.05 (Uakari) DrKonqi: 6.0.2 [CoredumpBackend] -- Information about the crash: 1. Open System Settings on a bare install. 2. Navigate to Colors & Themes > Window Decorations. 3. Duplicate Breeze theme or custom theme (ex. Lightly) present. 4. Hovering over either theme crashes System Settings The crash can be reproduced every time. -- Backtrace: Application: System Settings (), signal: Segmentation fault [New LWP 9283] [New LWP 9286] [New LWP 9291] [New LWP 9289] [New LWP 9284] [New LWP 9287] [New LWP 9306] [New LWP 9290] [New LWP 9285] [New LWP 9288] [New LWP 9292] [New LWP 9323] [New LWP 9322] [New LWP 9312] [New LWP 9339] [New LWP 9342] [New LWP 9313] [New LWP 9383] [New LWP 9326] [New LWP 9324] [New LWP 9325] [New LWP 9390] [New LWP 9340] [New LWP 9314] [New LWP 9321] [New LWP 9341] [Thread debugging using libthread_db enabled] Using host libthread_db library "/nix/store/ksk3rnb0ljx8gngzk19jlmbjyvac4hw6-glibc-2.38-44/lib/libthread_db.so.1". Core was generated by `systemsettings'. Program terminated with signal SIGSEGV, Segmentation fault. #0 0x7f1f914a407c in __pthread_kill_implementation () from /nix/store/ksk3rnb0ljx8gngzk19jlmbjyvac4hw6-glibc-2.38-44/lib/libc.so.6 [Current thread is 1 (Thread 0x7f1f8db21a00 (LWP 9283))] Cannot QML trace cores :( Unexpectedly stumbled over an objfile (/nix/store/n5yb44rw46r7ls91a0lbxyiybj6lx39y-qtshadertools-6.6.2/lib/libQt6ShaderTools.so.6.6.2) without build_id. Not creating payload. [Current thread is 1 (Thread 0x7f1f8db21a00 (LWP 9283))] Thread 26 (Thread 0x7f1f177fe6c0 (LWP 9341)): #0 0x7f1f9149eebe in __futex_abstimed_wait_common () from /nix/store/ksk3rnb0ljx8gngzk19jlmbjyvac4hw6-glibc-2.38-44/lib/libc.so.6 #1 0x7f1f914a1a35 in pthread_cond_timedwait@@GLIBC_2.3.2 () from /nix/store/ksk3rnb0ljx8gngzk19jlmbjyvac4hw6-glibc-2.38-44/lib/libc.so.6 #2 0x7f1f91d2d1f3 in QWaitCondition::wait(QMutex*, QDeadlineTimer) () from /nix/store/vcg2izx98281pckvs280h5hhhy61kf6n-qtbase-6.6.2/lib/libQt6Core.so.6 #3 0x7f1f91d29eed in QThreadPoolThread::run() () from /nix/store/vcg2izx98281pckvs280h5hhhy61kf6n-qtbase-6.6.2/lib/libQt6Core.so.6 #4 0x7f1f91d248d1 in QThreadPrivate::start(void*) () from /nix/store/vcg2izx98281pckvs280h5hhhy61kf6n-qtbase-6.6.2/lib/libQt6Core.so.6 #5 0x7f1f914a2383 in start_thread () from /nix/store/ksk3rnb0ljx8gngzk19jlmbjyvac4hw6-glibc-2.38-44/lib/libc.so.6 #6 0x7f1f9152500c in clone3 () from /nix/store/ksk3rnb0ljx8gngzk19jlmbjyvac4hw6-glibc-2.38-44/lib/libc.so.6 Thread 25 (Thread 0x7f1f37fff6c0 (LWP 9321)): #0 0x7f1f9149eebe in __futex_abstimed_wait_common () from /nix/store/ksk3rnb0ljx8gngzk19jlmbjyvac4hw6-glibc-2.38-44/lib/libc.so.6 #1 0x7f1f914a1720 in pthread_cond_wait@@GLIBC_2.3.2 () from /nix/store/ksk3rnb0ljx8gngzk19jlmbjyvac4hw6-glibc-2.38-44/lib/libc.so.6 #2 0x7f1f85717b19 in cnd_wait () from /run/opengl-driver/lib/dri/radeonsi_dri.so #3 0x7f1f856f7edb in util_queue_thread_func () from /run/opengl-driver/lib/dri/radeonsi_dri.so #4 0x7f1f85717a57 in impl_thrd_routine () from /run/opengl-driver/lib/dri/radeonsi_dri.so #5 0x7f1f914a2383 in start_thread () from /nix/store/ksk3rnb0ljx8gngzk19jlmbjyvac4hw6-glibc-2.38-44/lib/libc.so.6 #6 0x7f1f9152500c in clone3 () from /nix/store/ksk3rnb0ljx8gngzk19jlmbjyvac4hw6-glibc-2.38-44/lib/libc.so.6 Thread 24 (Thread 0x7f1f3c9fe6c0 (LWP 9314)): #0 0x7f1f9151789f in poll () from /nix/store/ksk3rnb0ljx8gngzk19jlmbjyvac4hw6-glibc-2.38-44/lib/libc.so.6 #1 0x7f1f909156f7 in g_main_context_iterate_unlocked.isra () from /nix/store/k1qjs35nw1lbssg1l1xpmh0082hy7wl4-glib-2.78.4/lib/libglib-2.0.so.0 #2 0x7f1f9091604f in g_main_loop_run () from /nix/store/k1qjs35nw1lbssg1l1xpmh0082hy7wl4-glib-2.78.4/lib/libglib-2.0.so.0 #3 0x7f1f3d735db6 in gdbus_shared_thread_func () from /nix/store/k1qjs35nw1lbssg1l1xpmh0082hy7wl4-glib-2.78.4/lib/libgio-2.0.so.0 #4 0x7f1f9094254d in g_thread_proxy () from /nix/store/k1qjs35nw1lbssg1l1xpmh0082hy7wl4-glib-2.78.4/lib/libglib-2.0.so.0 #5 0x7f1f914a2383 in start_thread () from /nix/store/ksk3rnb0ljx8gngzk19jlmbjyvac4hw6-glibc-2.38-44/lib/libc.so.6 #6 0x7f1f9152500c in clone3 () from /nix/store/ksk3rnb0ljx8gngzk19jlmbjyvac4hw6-glibc-2.38-44/lib/libc.so.6 Thread 23 (Thread
[dolphin] [Bug 483784] New: Super-user file manager can't paste
https://bugs.kde.org/show_bug.cgi?id=483784 Bug ID: 483784 Summary: Super-user file manager can't paste Classification: Applications Product: dolphin Version: 24.02.0 Platform: openSUSE OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: jbeckman1...@gmail.com CC: kfm-de...@kde.org Target Milestone: --- SUMMARY *** When logged in as a regular user, and then using the super-user version of Dolphin to copy/paste, I am able to "copy" the files but everywhere I try to paste them the "paste" option (from the right-click menu) is missing. Ctrl-V doesn't work either. Under the menu-bar if you click "Edit" the Paste option is greyed out. *** STEPS TO REPRODUCE 1. Open the "Super User" version of file manager 2. Browse to a folder and right-click on a file and select "copy" 3. Right-click and there is no "paste" option. Additionally "paste" in the pull-down menu's is greyed out OBSERVED RESULT Unable to paste while in the super-user version of Dolphin. Additionally I typically use this to copy files that are out of my regular users permission tree (such as docker volumes). If I "copy" from there in the super-user Dolphin, then open a regular dolphin the Paste option is present. However, in this case the non-super-user version of Dolphin doesn't have permission to paste the files so I get a permission error. The only way I can copy or move files (some with long difficult to type names!) is to use the console EXPECTED RESULT Cut/Copy/Paste work as usual for graphical programs while in the super-user version of Dolphin. This just started happening after upgrade to Plasma-6 (I'm on OpenSUSE Tumbleweed) SOFTWARE/OS VERSIONS Linux/KDE Plasma: OpenSUSE Tumbleweed KDE Plasma Version: 6.0.2 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.2 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 483695] New: Crash when computer resumes from suspend
https://bugs.kde.org/show_bug.cgi?id=483695 Bug ID: 483695 Summary: Crash when computer resumes from suspend Classification: Plasma Product: plasmashell Version: 6.0.2 Platform: Arch Linux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: jchevar...@gmail.com CC: k...@davidedmundson.co.uk Target Milestone: 1.0 Created attachment 167276 --> https://bugs.kde.org/attachment.cgi?id=167276=edit krash file Application: plasmashell (6.0.2) Qt Version: 6.6.2 Frameworks Version: 6.0.0 Operating System: Linux 6.7.9-arch1-1 x86_64 Windowing System: Wayland Distribution: "Arch Linux" DrKonqi: 6.0.2 [CoredumpBackend] -- Information about the crash: Tend to get a crash when waking up from resume. Tried to report via DrKonqi, but ironically that just gave an error message. -- Backtrace: See https://pastebin.com/raw/Z5SuYt8A or attached -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kidletime] [Bug 328987] Power saving should not trigger if joystick/controller/gamepad is in use
https://bugs.kde.org/show_bug.cgi?id=328987 Joe changed: What|Removed |Added CC||jchevar...@gmail.com --- Comment #48 from Joe --- I also just experienced this using a Steam Controller on the latest Plasma 6.0.1 release when trying out the FF7 remake. Screen goes to sleep even with controller input - work around right now is just manually inhibiting sleep/suspend and re-enabling. -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 481308] screen locker black with cursor on X11
https://bugs.kde.org/show_bug.cgi?id=481308 --- Comment #29 from Joe Amenta --- Something I don't see elsewhere on this thread: when this happens to me, I can use Ctrl+Alt+F3 to switch to TTY 3 and then Alt+F2 back to TTY 2, and the screen locker looks correct immediately instead of me having to wait. System info per "neofetch --off": OS: EndeavourOS Linux x86_64 Kernel: 6.7.8-arch1-1 Uptime: 1 day, 35 mins Packages: 2271 (pacman) Shell: zsh 5.9 Resolution: 2560x1440 DE: Plasma 6.0.1 WM: KWin Theme: [Plasma], Breeze-Dark [GTK2], Breeze [GTK3] Icons: [Plasma], breeze [GTK2/3] Terminal: terminator CPU: AMD Ryzen 9 7950X (32) @ 5.881GHz GPU: AMD ATI 6d:00.0 Raphael GPU: AMD ATI Radeon RX 6800/6800 XT / 6900 XT Memory: 8224MiB / 127936MiB -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 481308] screen locker blank-with-cursor [xorg]
https://bugs.kde.org/show_bug.cgi?id=481308 Joe Amenta changed: What|Removed |Added CC||airbreat...@linux.com -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 476759] Change default Page Up/Down overlap to, e.g., 10%
https://bugs.kde.org/show_bug.cgi?id=476759 Joe Breuer changed: What|Removed |Added CC||k...@jmbreuer.net --- Comment #1 from Joe Breuer --- Seconded... I did not even know this setting exists because it's shown in an area that's somewhat non-obviously (possibly due to my theme) scrolled outside of the visible area of the settings panel. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 353389] REQUEST: Obvious overlap position indicator to prevent re-reading overlap
https://bugs.kde.org/show_bug.cgi?id=353389 Joe Breuer changed: What|Removed |Added CC||k...@jmbreuer.net --- Comment #1 from Joe Breuer --- What... overlap? Did you turn that on at some place? (Where?) I came here with the feature request to have (some, ideally configurable) overlap when using PgUp/PgDn in Continuous Mode. In the PDF document I'm currently reading, Okular will skip by _exactly_ the whole page, even when that means splitting a line of text in half. ... -- You are receiving this mail because: You are watching all bug changes.
[Elisa] [Bug 481539] New: Package download failed, Elisa from kde neon
https://bugs.kde.org/show_bug.cgi?id=481539 Bug ID: 481539 Summary: Package download failed, Elisa from kde neon Classification: Applications Product: Elisa Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: matthieu_gall...@yahoo.fr Reporter: weisselbia...@gmail.com Target Milestone: --- SUMMARY *** NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** Package download failed STEPS TO REPRODUCE 1. 2. 3. OBSERVED RESULT EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[subtitlecomposer] [Bug 481318] subtitlecomposer crashes
https://bugs.kde.org/show_bug.cgi?id=481318 --- Comment #3 from Joe Breuer --- On a fresh day, with sufficient coffee, I managed to pull in that "tests-optional" patchset. And I'm happy to report that the crash is gone; I can play and seek to and past the point that always was a problem in 0.8.0 without any issues now. How does KDE handle bug reports? Do you have/use a specific state for "it's fixed in git, but no release yet", or would this be just RESOLVED FIXED? -- You are receiving this mail because: You are watching all bug changes.
[subtitlecomposer] [Bug 481318] subtitlecomposer crashes
https://bugs.kde.org/show_bug.cgi?id=481318 --- Comment #2 from Joe Breuer --- (In reply to Mladen Milinkovic, Max from comment #1) > Thanks for the report. > This is probably fixed with commit 0f99f801e3a4bf779167e15e151b14e8ca962f87. > Can you try building/testing current master? Thank you, that's a great idea! Unfortunately, the master branch doesn't readily build on gentoo. The ebuild mentions some patches having to do with turning off unavailable tests - I'll have a deeper look tomorrow / "soon". -- You are receiving this mail because: You are watching all bug changes.
[subtitlecomposer] [Bug 481315] subtitlecomposer crashes
https://bugs.kde.org/show_bug.cgi?id=481315 --- Comment #1 from Joe Breuer --- I've since replicated my original issue and reported it as bug #481318. drkonqi did not allow me to directly pick this issue as related; I'm not sure whether there is any causal relation in the first place, or rather this assertion is an unrelated finding that I stumbled across. -- You are receiving this mail because: You are watching all bug changes.
[subtitlecomposer] [Bug 481318] subtitlecomposer crashes
https://bugs.kde.org/show_bug.cgi?id=481318 Joe Breuer changed: What|Removed |Added Assignee|unassigned-b...@kde.org |max...@smoothware.net Product|unknown |subtitlecomposer Version|unspecified |0.8.0 Component|general |general -- You are receiving this mail because: You are watching all bug changes.
[unknown] [Bug 481318] New: subtitlecomposer crashes
https://bugs.kde.org/show_bug.cgi?id=481318 Bug ID: 481318 Summary: subtitlecomposer crashes Classification: Miscellaneous Product: unknown Version: unspecified Platform: Gentoo Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: k...@jmbreuer.net Target Milestone: --- Application: subtitlecomposer (0.8.0) Qt Version: 5.15.12 Frameworks Version: 5.113.0 Operating System: Linux 6.6.13-gentoo x86_64 Windowing System: X11 Distribution: "Gentoo Linux" DrKonqi: 5.27.10 [KCrashBackend] -- Information about the crash: subtitlecomposer crashes when I seek to/past a certain time in my video file. Since the backtrace mentions audio, it does look to me like the audio waveform displayed does not exactly correspond to the audio I'm hearing at the playback mark. This is related to bug #481315 (which might or might not be causally related), that I came across while setting up a sensible debug environment for this issue. The crash can be reproduced every time. -- Backtrace: Application: Subtitle Composer (subtitlecomposer), signal: Segmentation fault [KCrash Handler] #4 0x55b648986095 in SubtitleComposer::WaveRenderer::paintWaveform(QPainter&, unsigned int, unsigned int) (this=this@entry=0x55b6495ede50, painter=..., widgetWidth=widgetWidth@entry=279, widgetHeight=widgetHeight@entry=828) at /var/tmp/portage/media-video/subtitlecomposer-0.8.0/work/subtitlecomposer-0.8.0/src/gui/waveform/waverenderer.cpp:148 #5 0x55b648986dc2 in SubtitleComposer::WaveRenderer::paintGraphics(QPainter&) (this=this@entry=0x55b6495ede50, painter=...) at /var/tmp/portage/media-video/subtitlecomposer-0.8.0/work/subtitlecomposer-0.8.0/src/gui/waveform/waverenderer.cpp:176 #6 0x55b64898712b in SubtitleComposer::WaveRenderer::event(QEvent*) (this=0x55b6495ede50, evt=0x7ffd74eba400) at /var/tmp/portage/media-video/subtitlecomposer-0.8.0/work/subtitlecomposer-0.8.0/src/gui/waveform/waverenderer.cpp:88 #7 0x7fe000762e8e in QApplicationPrivate::notify_helper(QObject*, QEvent*) (this=, receiver=0x55b6495ede50, e=0x7ffd74eba400) at /var/tmp/portage/dev-qt/qtwidgets-5.15.12/work/qtbase-everywhere-src-5.15.12/src/widgets/kernel/qapplication.cpp:3640 #8 0x7fdfffa88258 in QCoreApplication::notifyInternal2(QObject*, QEvent*) (receiver=0x55b6495ede50, event=0x7ffd74eba400) at /var/tmp/portage/dev-qt/qtcore-5.15.12-r1/work/qtbase-everywhere-src-5.15.12/src/corelib/kernel/qcoreapplication.cpp:1064 #9 0x7fdfffa8843e in QCoreApplication::sendSpontaneousEvent(QObject*, QEvent*) (receiver=, event=) at /var/tmp/portage/dev-qt/qtcore-5.15.12-r1/work/qtbase-everywhere-src-5.15.12/src/corelib/kernel/qcoreapplication.cpp:1474 #10 0x7fe00079cf95 in QWidgetPrivate::sendPaintEvent(QRegion const&) (this=this@entry=0x55b6494d0fb0, toBePainted=...) at /var/tmp/portage/dev-qt/qtwidgets-5.15.12/work/qtbase-everywhere-src-5.15.12/src/widgets/kernel/qwidget.cpp:5479 #11 0x7fe00079d8db in QWidgetPrivate::drawWidget(QPaintDevice*, QRegion const&, QPoint const&, QFlags, QPainter*, QWidgetRepaintManager*) (this=this@entry=0x55b6494d0fb0, pdev=0x55b64995fd30, rgn=..., offset=..., flags=..., sharedPainter=sharedPainter@entry=0x0, repaintManager=) at /var/tmp/portage/dev-qt/qtwidgets-5.15.12/work/qtbase-everywhere-src-5.15.12/src/widgets/kernel/qwidget.cpp:5429 #12 0x7fe000773f90 in QWidgetRepaintManager::paintAndFlush() (this=0x55b649bfb810) at /var/tmp/portage/dev-qt/qtwidgets-5.15.12/work/qtbase-everywhere-src-5.15.12/src/widgets/kernel/qwidgetrepaintmanager.cpp:1016 #13 0x7fe0007a5516 in QWidget::event(QEvent*) (this=this@entry=0x55b6495b7e70, event=event@entry=0x7fdf6c218880) at /var/tmp/portage/dev-qt/qtwidgets-5.15.12/work/qtbase-everywhere-src-5.15.12/src/widgets/kernel/qwidget.cpp:8990 #14 0x7fe0008bae20 in QMainWindow::event(QEvent*) (this=this@entry=0x55b6495b7e70, event=event@entry=0x7fdf6c218880) at /var/tmp/portage/dev-qt/qtwidgets-5.15.12/work/qtbase-everywhere-src-5.15.12/src/widgets/widgets/qmainwindow.cpp:1341 #15 0x7fe0011f23ce in KMainWindow::event(QEvent*) (this=this@entry=0x55b6495b7e70, ev=ev@entry=0x7fdf6c218880) at /var/tmp/portage/kde-frameworks/kxmlgui-5.113.0/work/kxmlgui-5.113.0/src/kmainwindow.cpp:961 #16 0x7fe0012349f7 in KXmlGuiWindow::event(QEvent*) (this=0x55b6495b7e70, ev=0x7fdf6c218880) at /var/tmp/portage/kde-frameworks/kxmlgui-5.113.0/work/kxmlgui-5.113.0/src/kxmlguiwindow.cpp:220 #17 0x7fe000762e8e in QApplicationPrivate::notify_helper(QObject*, QEvent*) (this=, receiver=0x55b6495b7e70, e=0x7fdf6c218880) at /var/tmp/portage/dev-qt/qtwidgets-5.15.12/work/qtbase-everywhere-src-5.15.12/src/widgets/kernel/qapplication.cpp:3640 #18 0x7fdfffa88258 in QCoreApplication::notifyInternal2(QObject*, QEvent*) (receiver=0x55b6495b7e70,
[subtitlecomposer] [Bug 481315] subtitlecomposer crashes
https://bugs.kde.org/show_bug.cgi?id=481315 Joe Breuer changed: What|Removed |Added Product|unknown |subtitlecomposer Assignee|unassigned-b...@kde.org |max...@smoothware.net Component|general |general Version|unspecified |0.8.0 -- You are receiving this mail because: You are watching all bug changes.
[unknown] [Bug 481315] subtitlecomposer crashes
https://bugs.kde.org/show_bug.cgi?id=481315 Joe Breuer changed: What|Removed |Added Platform|Compiled Sources|Gentoo Packages -- You are receiving this mail because: You are watching all bug changes.
[unknown] [Bug 481315] New: subtitlecomposer crashes
https://bugs.kde.org/show_bug.cgi?id=481315 Bug ID: 481315 Summary: subtitlecomposer crashes Classification: Miscellaneous Product: unknown Version: unspecified Platform: Compiled Sources OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: k...@jmbreuer.net Target Milestone: --- Application: subtitlecomposer (0.8.0) (Compiled from sources) Qt Version: 5.15.12 Frameworks Version: 5.113.0 Operating System: Linux 6.6.13-gentoo x86_64 Windowing System: X11 Distribution: "Gentoo Linux" DrKonqi: 5.27.10 [KCrashBackend] -- Information about the crash: I had an issue with subtitlecomposer crashing, as it turned out, whenever I reached a specific point in the video I was working on. That crash report was not useful, so I rebuilt subtitlecomposer and its relevant dependencies with debug symbols. In this first attempt, this changes the behaviour, causing an assertion immediately upon starting subtitlecomposer, that I guess is optimized out in a release build: ASSERT: "last < rowCount(parent)" in file /var/tmp/portage/dev-qt/qtcore-5.15.12-r1/work/qtbase-everywhere-src-5.15.12/src/corelib/itemmodels/qabstractitemmodel.cpp, line 2817 How can I find out which database file (I guess) is causing this assertion, to 'fix' that (i.e. probably delete and have it rebuilt)? Meanwhile, I'll see to rebuild with debug symbols but with a release-equivalent configuration, i.e. without the assertion(s). The crash can be reproduced every time. -- Backtrace: Application: Subtitle Composer (subtitlecomposer), signal: Aborted [KCrash Handler] #4 0x7f4d78cb0e5c in () at /lib64/libc.so.6 #5 0x7f4d78c625e2 in raise () at /lib64/libc.so.6 #6 0x7f4d78c4b4ed in abort () at /lib64/libc.so.6 #7 0x7f4d7c491eab in qt_message_fatal (message=..., context=) at /var/tmp/portage/dev-qt/qtcore-5.15.12-r1/work/qtbase-everywhere-src-5.15.12/src/corelib/global/qlogging.cpp:1919 #8 QMessageLogger::fatal(char const*, ...) const (this=this@entry=0x7ffdddfc83f8, msg=msg@entry=0x7f4d7c78b6a8 "ASSERT: \"%s\" in file %s, line %d") at /var/tmp/portage/dev-qt/qtcore-5.15.12-r1/work/qtbase-everywhere-src-5.15.12/src/corelib/global/qlogging.cpp:898 #9 0x7f4d7c49094a in qt_assert(char const*, char const*, int) (assertion=assertion@entry=0x7f4d7c7a5e44 "last < rowCount(parent)", file=file@entry=0x7f4d7c796ac8 "/var/tmp/portage/dev-qt/qtcore-5.15.12-r1/work/qtbase-everywhere-src-5.15.12/src/corelib/itemmodels/qabstractitemmodel.cpp", line=line@entry=2817) at /var/tmp/portage/dev-qt/qtcore-5.15.12-r1/work/qtbase-everywhere-src-5.15.12/src/corelib/global/qglobal.cpp:3392 #10 0x7f4d7c4b2c3a in QAbstractItemModel::beginRemoveRows(QModelIndex const&, int, int) (this=0x5611a8dd9800, parent=, first=0, last=0) at /var/tmp/portage/dev-qt/qtcore-5.15.12-r1/work/qtbase-everywhere-src-5.15.12/src/corelib/itemmodels/qabstractitemmodel.cpp:2817 #11 0x5611a6d545d5 in SubtitleComposer::InstalledScriptsModel::removeAll() (this=0x5611a8dd9800) at /var/tmp/portage/media-video/subtitlecomposer-0.8.0/work/subtitlecomposer-0.8.0/src/scripting/scriptsmanager.cpp:305 #12 SubtitleComposer::ScriptsManager::reloadScripts() (this=0x5611a8f8c1a0) at /var/tmp/portage/media-video/subtitlecomposer-0.8.0/work/subtitlecomposer-0.8.0/src/scripting/scriptsmanager.cpp:711 #13 0x5611a6c9bf99 in SubtitleComposer::Application::createMainWindow() (this=this@entry=0x7ffdddfc87e0) at /var/tmp/portage/media-video/subtitlecomposer-0.8.0/work/subtitlecomposer-0.8.0/src/application.cpp:280 #14 0x5611a6c900b2 in main(int, char**) (argc=, argv=) at /var/tmp/portage/media-video/subtitlecomposer-0.8.0/work/subtitlecomposer-0.8.0/src/main.cpp:183 [Inferior 1 (process 1967481) detached] Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 471820] Crash in KWin::GLVertexBuffer::~GLVertexBuffer on compositor stop
https://bugs.kde.org/show_bug.cgi?id=471820 --- Comment #2 from joe --- Created attachment 165765 --> https://bugs.kde.org/attachment.cgi?id=165765=edit New crash information added by DrKonqi kwin_x11 (5.27.5) using Qt 5.15.8 At the very moment the system starts up, after having been in sleep mode, a window composer error usually always occurs. I'm using the Nvidia driver, downloaded from the official site. This happens on desktop pc and also on laptop, notebook using nvidia and bumblebee. In general, Debian 12 is having a lot of problems with Wayland compositor and Nvidia. Even the problems persist if I use X11 as window compositor. Regards. Translated with DeepL.com (free version) -- Backtrace (Reduced): #4 0x7f3c56701fb3 in _XSend () from /lib/x86_64-linux-gnu/libX11.so.6 #5 0x7f3c566f8381 in XQueryExtension () from /lib/x86_64-linux-gnu/libX11.so.6 #6 0x7f3c566eb792 in XInitExtension () from /lib/x86_64-linux-gnu/libX11.so.6 #7 0x7f3c55343c9b in XextAddDisplay () from /lib/x86_64-linux-gnu/libXext.so.6 [...] #16 0x7f3c579e9603 in KWin::GLTexturePrivate::cleanup() () from /lib/x86_64-linux-gnu/libkwinglutils.so.14 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 471820] Crash in KWin::GLVertexBuffer::~GLVertexBuffer on compositor stop
https://bugs.kde.org/show_bug.cgi?id=471820 joe changed: What|Removed |Added CC||josluis.fernn...@gmail.com --- Comment #1 from joe --- At the very moment the system starts up, after having been in sleep mode, a window composer error usually always occurs. I'm using the Nvidia driver, downloaded from the official site. This happens on desktop pc and also on laptop, notebook using nvidia and bumblebee. In general, Debian 12 is having a lot of problems with Wayland compositor and Nvidia. Even the problems persist if I use X11 as window compositor. Regards. -- You are receiving this mail because: You are watching all bug changes.
[kstars] [Bug 480149] New: KSTARS 3.6.8 Stable (EKOS) consistently crashes using the dark wizard on a MacBook Air M2 / Sonoma
https://bugs.kde.org/show_bug.cgi?id=480149 Bug ID: 480149 Summary: KSTARS 3.6.8 Stable (EKOS) consistently crashes using the dark wizard on a MacBook Air M2 / Sonoma Classification: Applications Product: kstars Version: unspecified Platform: Other OS: Other Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: mutla...@ikarustech.com Reporter: jpineda...@live.com Target Milestone: --- SUMMARY *** KSTARS consistently crashes on my Macbook air M2 if I used the Dark wizard tool more than once. The fix is to erase dark frame masters from KSTARS and from the Macbook drive folder before subsequent use. The same issue was not seen during trials with a Windows 11 PC. *** STEPS TO REPRODUCE 1. I ran the dark wizard for my guide camera ... 5 exposures each over 1-5 second range. 2. Immediately repeat step 1. OBSERVED RESULT KSTARS crashes EXPECTED RESULT old darks + masters are overwritten SOFTWARE/OS VERSIONS Windows: macOS: Sonoma 14.2.1 Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION I was able to fix the issue by manually deleting the old masters using the wizard AND manually deleting the files on my MAC...I had to do both. I could then rerun the dark wizard without the crash. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 479805] I find the memory usage of a coverage of my painting is EXTREMELY LAREGE,thought it shouldn't have be.
https://bugs.kde.org/show_bug.cgi?id=479805 --- Comment #4 from Joe --- Created attachment 164903 --> https://bugs.kde.org/attachment.cgi?id=164903=edit here's the screencut of the bug file. At first I found that I couldn't use the wrap tool to adjust the angle of the head of my character on the ''head4''coverage because it was delaying and jerking discontinuously,so I could hardly adjust it to the proper angle,Sometimes Krita crushed after a amount of failing to repond;Then I thought perhaps the head was too complicated for my computer to handle with,so I erased a part of it,but the bug still exsist.I erased all,but it did not matter.Finally I cut off most part of the coverage but only remains the part of head and the memory usage plunged.By the way,the other parts of my character on nine coverages only take 286MiB,so it confused me a lot how could a coverage with nothing on it could takes 3.5GiB -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 479805] I find the memory usage of a coverage of my painting is EXTREMELY LAREGE,thought it shouldn't have be.
https://bugs.kde.org/show_bug.cgi?id=479805 --- Comment #3 from Joe --- Created attachment 164902 --> https://bugs.kde.org/attachment.cgi?id=164902=edit here's the attachment of bug file -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 479805] New: I find the memory usage of a coverage of my painting is EXTREMELY LAREGE,thought it shouldn't have be.
https://bugs.kde.org/show_bug.cgi?id=479805 Bug ID: 479805 Summary: I find the memory usage of a coverage of my painting is EXTREMELY LAREGE,thought it shouldn't have be. Classification: Applications Product: krita Version: 5.2.2 Platform: Compiled Sources OS: Microsoft Windows Status: REPORTED Severity: normal Priority: NOR Component: General Assignee: krita-bugs-n...@kde.org Reporter: zaizho...@163.com Target Milestone: --- SUMMARY *** NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** STEPS TO REPRODUCE I don't know how to REPRODUCE this coverage,but you can decompress the the KRA. file in the zip. file in attachment and copy the "head4" coverage to other KRA.files to reproduce the phenomenon. OBSERVED RESULT the KRA.files cost 3.4GIB of the video card's memory EXPECTED RESULT the KRA.files should cost much less video card's memory than 3.4GIB SOFTWARE/OS VERSIONS Windows: Windows11 22H2 macOS: 22621.3007 Linux/KDE Plasma: unsure (available in About System) KDE Plasma Version: unsure KDE Frameworks Version: unsure Qt Version: unsure ADDITIONAL INFORMATION I've tried this on Krita 5.1.4 and Krita 5.2.2,and the bug can occur on both of them . Krita Version: 5.1.4 Installation type: installer / portable package Hidpi: true Qt Version (compiled): 5.12.12 Version (loaded): 5.12.12 OS Information Build ABI: x86_64-little_endian-llp64 Build CPU: x86_64 CPU: x86_64 Kernel Type: winnt Kernel Version: 10.0.22621 Pretty Productname: Windows 10 (10.0) Product Type: windows Product Version: 10 Locale Languages: zh_CN, en_US C locale: C QLocale current: zh QLocale system: zh QTextCodec for locale: UTF-8 Process ACP: 65001 (UTF-8) System locale default ACP: 936 (ANSI/OEM - 简体中文 GBK) OpenGL Info Vendor: "Google Inc. (Intel)" Renderer: "ANGLE (Intel, Intel(R) Iris(R) Xe Graphics Direct3D11 vs_5_0 ps_5_0, D3D11-30.0.101.1069)" Version: "OpenGL ES 3.0.0 (ANGLE 2.1.0 git hash: f2280c0c5f93+krita_qt5.12.12)" Shading language: "OpenGL ES GLSL ES 3.00 (ANGLE 2.1.0 git hash: f2280c0c5f93+krita_qt5.12.12)" Requested format: QSurfaceFormat(version 3.0, options QFlags(DeprecatedFunctions), depthBufferSize 24, redBufferSize 8, greenBufferSize 8, blueBufferSize 8, alphaBufferSize 8, stencilBufferSize 8, samples -1, swapBehavior QSurfaceFormat::DoubleBuffer, swapInterval 0, colorSpace QSurfaceFormat::DefaultColorSpace, profile QSurfaceFormat::CompatibilityProfile) Current format: QSurfaceFormat(version 3.0, options QFlags(), depthBufferSize 24, redBufferSize 8, greenBufferSize 8, blueBufferSize 8, alphaBufferSize 8, stencilBufferSize 8, samples 0, swapBehavior QSurfaceFormat::DefaultSwapBehavior, swapInterval 0, colorSpace QSurfaceFormat::DefaultColorSpace, profile QSurfaceFormat::NoProfile) Version: 3.0 Supports deprecated functions false is OpenGL ES: true supportsBufferMapping: true supportsBufferInvalidation: false forceDisableTextureBuffers: true Extensions: "GL_EXT_draw_elements_base_vertex" "GL_EXT_sRGB" "GL_OES_texture_float_linear" "GL_OES_standard_derivatives" "GL_ANGLE_lossy_etc_decode" "GL_EXT_texture_rg" "GL_ANGLE_client_arrays" "GL_OES_texture_half_float" "GL_OES_mapbuffer" "GL_OES_compressed_EAC_RG11_unsigned_texture" "GL_KHR_debug" "GL_OES_texture_npot" "GL_ANGLE_get_serialized_context_string" "GL_ANGLE_request_extension" "GL_ANGLE_memory_size" "GL_EXT_debug_label" "GL_OES_EGL_image" "GL_OVR_multiview2" "GL_EXT_texture_norm16" "GL_ANGLE_base_vertex_base_instance" "GL_EXT_read_format_bgra" "GL_OES_compressed_EAC_RG11_signed_texture" "GL_NV_pack_subimage" "GL_EXT_clip_control" "GL_EXT_multi_draw_indirect" "GL_EXT_robustness" "GL_OES_surfaceless_context" "GL_ANGLE_texture_multisample" "GL_CHROMIUM_copy_texture" "GL_ANGLE_program_cache_control" "GL_ANGLE_multiview_multisample" "GL_ANGLE_texture_usage" "GL_AMD_performance_monitor" "GL_OES_compressed_ETC2_RGB8_texture" "GL_EXT_instanced_arrays" "GL_EXT_multisampled_render_to_texture" "GL_EXT_blend_func_extended" "GL_OES_draw_buffers_indexed" "GL_OES_packed_depth_stencil" "GL_ANGLE_texture_compression_dxt3" "GL_EXT_texture_compression_rgtc" "GL_OES_EGL_image_external" "GL_EXT_color_buffer_half_float" "GL_OES_texture_stencil8" "GL_EXT_color_buffer_float" "GL_EXT_draw_buffers" "GL_OES_depth32" "GL_OES_compressed_ETC2_punchthroughA_RGBA8_texture" "GL_WEBGL_video_texture"
[krita] [Bug 479804] New: I find the memory usage of a coverage of my painting is EXTREMELY LAREGE,thought it shouldn't have be.
https://bugs.kde.org/show_bug.cgi?id=479804 Bug ID: 479804 Summary: I find the memory usage of a coverage of my painting is EXTREMELY LAREGE,thought it shouldn't have be. Classification: Applications Product: krita Version: 5.2.2 Platform: Compiled Sources OS: Microsoft Windows Status: REPORTED Severity: normal Priority: NOR Component: Resource Management Assignee: krita-bugs-n...@kde.org Reporter: zaizho...@163.com Target Milestone: --- SUMMARY *** NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** STEPS TO REPRODUCE I don't know how to REPRODUCE this coverage,but you can decompress the the KRA. file in the zip. file in attachment and copy the "head4" coverage to other KRA.files to reproduce the phenomenon. OBSERVED RESULT the KRA.files cost 3.4GIB of the video card's memory EXPECTED RESULT the KRA.files should cost much less video card's memory than 3.4GIB SOFTWARE/OS VERSIONS Windows: Windows11 22H2 macOS: 22621.3007 Linux/KDE Plasma: unsure (available in About System) KDE Plasma Version: unsure KDE Frameworks Version: unsure Qt Version: unsure ADDITIONAL INFORMATION I've tried this on Krita 5.1.4 and Krita 5.2.2,and the bug can occur on both of them . -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 477187] Option to disable calculating the size and number of items in child directories
https://bugs.kde.org/show_bug.cgi?id=477187 Joe changed: What|Removed |Added CC||timexwarri...@gmail.com Platform|Other |Ubuntu --- Comment #3 from Joe --- (In reply to random011 from comment #0) Same issue here. When navigating -nearby- directories with thousands of files, my dolphin will lock up entirely until it is able to scan through all of them. Granted, this happens while accessing a remote directory mounted using sshfs-fuse. But even still, when testing with PCManFM and Thunar, theyhave no loading or performance issues with navigating around the same folders. It would be great if we had a way to disable the scanning behavior or perhaps manually initiate/omit specific folders. The existing functionality works fine as long as there are not a crazy amount of files in nearby directories. Perhaps an adjustable limit to how many files it tries to scan before giving up? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 474430] Tiny cursor on Firefox when using scaling on Wayland
https://bugs.kde.org/show_bug.cgi?id=474430 --- Comment #7 from Joe --- Just an update on the games and flickering: running in gamescope and they are fine, so, i do think it is a kwin issue. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 474430] Tiny cursor on Firefox when using scaling on Wayland
https://bugs.kde.org/show_bug.cgi?id=474430 --- Comment #6 from Joe --- So, my previous bug was closed and marked duplicate of this - which seems correctly. Just wanted to bring up the other half of my report which is the video can 'jump' a bit when moving the mouse (and it becomes the right size again). I have noticed the same frame jumping/slight ghosting also in two Proton steam games (Rome 2 Total War & Attila Total War) where the cursor is fine, but I get the jumping/frame ghosting. Switching them from full screen to windowed and the ghosting stops. At this point not sure if they are related - or if I should create a separate bug for this side of my original report. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 474603] New: In Firefox Fullscreen videos, mouse changes sizes
https://bugs.kde.org/show_bug.cgi?id=474603 Bug ID: 474603 Summary: In Firefox Fullscreen videos, mouse changes sizes Classification: Plasma Product: kwin Version: 5.27.8 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: wayland-generic Assignee: kwin-bugs-n...@kde.org Reporter: jchevar...@gmail.com Target Milestone: --- SUMMARY Bit of an odd one. When watching a full screen Youtube Video, the mouse is smaller at rest. When you move the mouse, it becomes the correct size. It also makes the picture shift/jump a pixel (or two). Might be a fractional scaling thing? I have two 1440p monitors, and using a factor of 150%, and using Firefox native Wayland. STEPS TO REPRODUCE 1. Open YouTube Video in Firefox 2. Move mouse 3. Notice mouse size changes, and video jumps slightly OBSERVED RESULT Cursor changes sizes, and video jumps/shifts. EXPECTED RESULT Cursor should be the system setting and not change. Video should not move/jump. SOFTWARE/OS VERSIONS Arch Linux Operating System: Arch Linux KDE Plasma Version: 5.27.8 KDE Frameworks Version: 5.110.0 Qt Version: 5.15.10 Kernel Version: 6.5.3-arch1-1 (64-bit) Graphics Platform: Wayland Processors: 24 × AMD Ryzen 9 5900X 12-Core Processor Memory: 31.3 GiB of RAM Graphics Processor: AMD Radeon RX 6900 XT Firefox: 117.01, Wayland Additional comments: Could very well be Firefox itself, sure is certainly a bit of a paper cut on Wayland. -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 472443] New: Currency rate change dont update
https://bugs.kde.org/show_bug.cgi?id=472443 Bug ID: 472443 Summary: Currency rate change dont update Classification: Applications Product: kmymoney Version: 5.1.3 Platform: Ubuntu OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: website Assignee: kmymoney-de...@kde.org Reporter: jfia...@tiscali.it Target Milestone: --- SUMMARY Since 18.7.2023 the rate change dont update online I have solved it changing 1\s[^=]+\s=\s([^\s]+) with 1\s[^=]+\s=\s([^\s]+) I suppose that fx-rate.net page have been modified -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 472211] New: Feature Request: please add a way to change the Z-order of annotations
https://bugs.kde.org/show_bug.cgi?id=472211 Bug ID: 472211 Summary: Feature Request: please add a way to change the Z-order of annotations Classification: Applications Product: okular Version: 23.04.2 Platform: Gentoo Packages OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: PDF backend Assignee: okular-de...@kde.org Reporter: k...@jmbreuer.net Target Milestone: --- SUMMARY (PDF) Annotations seem to be added to the document in a fixed "new on top" Z-order. There are no move higher/lower/bring to front/send to back editing tools (that I could find). STEPS TO REPRODUCE 1. Add a PDF annotation, e.g. a large-ish inline note 2. Add another PDF annotation, e.g. another large-ish inline note, that overlaps the other one 3. Observe that OBSERVED RESULT The annotation added second stays on top of the one added first for good, no way to change this. EXPECTED RESULT A way to re-order the z stack of annotations to e.g. make text in partially overlapping notes fully readable (without requiring to click-through to the annotation content or such). I'm sure there's a few other use cases. The only remaining way to change the ordering, deleting a lower annotation and re-creating it on top, is effortful. Especially since there's no cut/copy/paste of annotation elements, either. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Gentoo Linux 2.13, Kernel 6.1.38-gentoo (64-bit) KDE Plasma Version: 5.27.5 KDE Frameworks Version: 5.106.0 Qt Version: 5.15.9 -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 471792] Annotations greatly increase PDF file size and massively slow down Okular
https://bugs.kde.org/show_bug.cgi?id=471792 Joe Breuer changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |FIXED --- Comment #5 from Joe Breuer --- (In reply to Sune Vuorela from comment #4) > (In reply to Joe Breuer from comment #3) > > What method/tool do you use to obtain this information? > > poppler source package (Often in a binary package like poppler-utils or > poppler-tools) contains pdffonts tool that list all of the fonts in the pdf > file. Ah, that's great to know! > > > With poppler 23.06, adding annotations should grow the document with > > > approximately 600k. With poppler 23.07, it should grow the document with > > > approximately 300 k, assuming noto sans (okular default) is used. > > > > Is that to be expected "per each annotation", or once per adding annotations > > at all, or per annotation type, ...? > > Technically, it is per different font, assuming every font is as big as Noto > Sans and compresses with zlib similar to Noto Sans. Ah thanks, I get it and know where to look now! I've added another example using Okular 23.02.4 (with/against Poppler 23.06.0), and that noticeably keeps a stable file size also when adding multiple annotations. It is somewhat smaller than the Okular 22.12.3/Poppler 23.06.0/built against Poppler 23.01.0 sample, the difference seems to be down to Okular 23 only embedding Noto Sans, not Noto Sans and Noto Sans Regular both. So - for my purposes - Poppler 23.06.0 and possibly Okular 23.02.4 are the required combination for a PDF annotation workflow without... "file size and performance surprises." -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 471792] Annotations greatly increase PDF file size and massively slow down Okular
https://bugs.kde.org/show_bug.cgi?id=471792 --- Comment #3 from Joe Breuer --- (In reply to Sune Vuorela from comment #1) > Some versions did embed the same fonts multiple times, and your "big" > document contains ~140 copies of noto fonts What method/tool do you use to obtain this information? > It should be fixed in version 23.06 of the poppler library. Simply upgrading my poppler library to 23.06 still gives me PDFs increasing significantly in size with each additional annotation, though by far by not as much as with 23.05. I've added a corresponding sample: https://github.com/jmbreuer/heap/tree/main/kde-okular-bug-20230630 In "About Backend", my Okular 22.12.3 now displays "Using Poppler 23.06.0, Built against Poppler 23.01.0". Building this version of Okular against Poppler 23.06.0 yields a compile error, I'll see about trying out a newer Okular version. > With poppler 23.06, adding annotations should grow the document with > approximately 600k. With poppler 23.07, it should grow the document with > approximately 300 k, assuming noto sans (okular default) is used. Is that to be expected "per each annotation", or once per adding annotations at all, or per annotation type, ...? -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 471792] Annotations greatly increase PDF file size and massively slow down Okular
https://bugs.kde.org/show_bug.cgi?id=471792 --- Comment #2 from Joe Breuer --- (In reply to Sune Vuorela from comment #1) > What version of the underlying Poppler library are you using ? 23.05 > Some versions did embed the same fonts multiple times, and your "big" > document contains ~140 copies of noto fonts Ah, thank you! That makes (altogether too much) sense. > It should be fixed in version 23.06 of the poppler library. > > With poppler 23.06, adding annotations should grow the document with > approximately 600k. With poppler 23.07, it should grow the document with > approximately 300 k, assuming noto sans (okular default) is used. I'll have a look into that very shortly and let you know - 23.06 looks to be available in gentoo 'testing'. Trying a 23.07 bump is not immediately accessible to me, since there's apparently no release or even git tag yet. Not sure that I want to run git master on a production system. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 470128] Saving document with resized text creates huge memory footprint
https://bugs.kde.org/show_bug.cgi?id=470128 --- Comment #5 from Joe Breuer --- My bug #471792 has one sample which massively demonstrates this - file size from 6.4 MB (original) to 143.4 MB (two Inline Notes with resized fonts). -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 470128] Saving document with resized text creates huge memory footprint
https://bugs.kde.org/show_bug.cgi?id=470128 Joe Breuer changed: What|Removed |Added CC||k...@jmbreuer.net -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 471792] New: Annotations greatly increase PDF file size and massively slow down Okular
https://bugs.kde.org/show_bug.cgi?id=471792 Bug ID: 471792 Summary: Annotations greatly increase PDF file size and massively slow down Okular Classification: Applications Product: okular Version: 22.12.3 Platform: Gentoo Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: PDF backend Assignee: okular-de...@kde.org Reporter: k...@jmbreuer.net Target Milestone: --- SUMMARY Adding annotations to a run-of-the-mill PDF file (out of pdfLaTeX, I presume) hugely increases the file size with each additional annotation. STEPS TO REPRODUCE 1. Open a PDF file 2. Add a couple of annotations (I mostly used Inline Notes, but also some underlines and Pop-up Notes) 3. Save as PDF OBSERVED RESULT Saving my 6.4 MB sample PDF with very few test annotations and saving as PDF yields a 7.4 MB file. Removing those and adding a couple of 'real' annotations, the saved PDF weighs in at 20.7 MB. Changing font size of two Inline Note annotations after they have been created yields a huge PDF of 143.4 MB. With the increase in file size also comes an increase in CPU usage to the point that Okular slows down and becomes practically unusable (especially / immediately noticable with the "resized font" case). EXPECTED RESULT Annotations should only slightly increase file size and not strongly affect interactive performance. SOFTWARE/OS VERSIONS Linux/KDE Plasma: gentoo Linux 2.13, Kernel 6.1.31-gentoo (64-bit) KDE Plasma Version: 5.27.5 KDE Frameworks Version: 5.106.0 Qt Version: 5.15.9 ADDITIONAL INFORMATION Since attachments cannot exceed 4000kB, and all my samples are larger than that, I've put together my sample files here: https://github.com/jmbreuer/heap/tree/main/kde-okular-bug-20230630 I've also seen bug #470128, and also noticed that changing the font size of an Inline Note annotation after adding it would hugely increase the file size (changing two notes, from those 6.4/7.4 MB to 143.4 MB). -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 469976] Allow a keyboard shortcut for existing functionality of toggling audio mute of the currently active window/application only
https://bugs.kde.org/show_bug.cgi?id=469976 --- Comment #2 from Joe Breuer --- ... ah, and I think Alt+Mute would be a good/useful key combination for this; but maybe that only happens to be convenient on the keyboard I have in front of me. ... -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 469976] Allow a keyboard shortcut for existing functionality of toggling audio mute of the currently active window/application only
https://bugs.kde.org/show_bug.cgi?id=469976 --- Comment #1 from Joe Breuer --- Thinking about it some more, I'd like to suggest a kind of special case on top: When the mouse pointer is hovering over a Task Manager tile, highlighting that application/window to be activated on click, that keyboard shortcut should operate on the thusly highlighted application. In all other cases - pointer not highlighting something in the 'task bar' - mute state of the application associated with the currently active/focused window should toggle (the one that's shown highlighted on the 'task bar' regardless of any mouse-over things). -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 469976] New: Allow a keyboard shortcut for existing functionality of toggling audio mute of the currently active window/application only
https://bugs.kde.org/show_bug.cgi?id=469976 Bug ID: 469976 Summary: Allow a keyboard shortcut for existing functionality of toggling audio mute of the currently active window/application only Classification: Plasma Product: plasmashell Version: 5.27.4 Platform: Gentoo Packages OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: Task Manager and Icons-Only Task Manager Assignee: plasma-b...@kde.org Reporter: k...@jmbreuer.net Target Milestone: 1.0 Since recently, there's this very nice feature of the little speaker icons shown on the window selectors in the task manager, which toggles audio mute of that specific application. As far as I could determine, there's currently no way to activate this functionality using a keyboard shortcut. I've been in a number of situations where I was wishing for that exact keyboard shortcut, such as: - (quickly) muting an audio player on an incoming video conference / soft phone call - muting a full screen game when a "hard" phone call comes in, but leaving audio notifications from other applications intact during the call - Wanting to quickly silence audio prompts by one certain set of applications, while enabling others ... etc. All necessary information (active task, how to do the per-application mute toggle) is obviously already available to the Task Manager - the active application is shown highlighted, and the mute button there knows what to do. I'm tempted to have a look to roll a patch / enhancement myself, in that regard a question to the people who might know: Is the Task Manager an integral part of kwin, or is it a separate/different component (which/where)? ... since kwin already registers a number of keyboard shortcuts, extending this by the one more feels feasible to me even without knowing KDE code in depth. However, adding keyboard shortcut functionality to a component that doesn't have any at all so far, not so much. ;-) -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 468059] pkcon incorrect error response on update (no packages updated).
https://bugs.kde.org/show_bug.cgi?id=468059 Joe Vaughan changed: What|Removed |Added CC||joe.vaug...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 468059] New: pkcon incorrect error response on update (no packages updated).
https://bugs.kde.org/show_bug.cgi?id=468059 Bug ID: 468059 Summary: pkcon incorrect error response on update (no packages updated). Classification: KDE Neon Product: neon Version: unspecified Platform: Other OS: Other Status: REPORTED Severity: normal Priority: NOR Component: Packages User Edition Assignee: neon-b...@kde.org Reporter: joe.vaug...@gmail.com CC: j...@jriddell.org, neon-b...@kde.org, sit...@kde.org Target Milestone: --- SUMMARY KDE Neon 'pkcon update' command returns incorrect status/error code when nothing is installed/updated. STEPS TO REPRODUCE 1. sudo /usr/bin/pkcon refresh -p 2. sudo /usr/bin/pkcon update -yp OBSERVED RESULT 'pkcon update' returns non-zero (error code: 5) if no packages are updated. This is incorrect behaviour as this is not an error but a normal response. Note: 'pkcon refresh' correctly returns 0 if no updates are applied to repository caches. EXPECTED RESULT On any *NIX operating system a non-zero exit code indicates that some error occurred. No error has occurred in this instance, simply no updates to be applied (which isn't an error) A successfully executing command should return status code 0. Therefore 'pkcon update' should return 0 as it is executing successfully even if no packages are updated. SOFTWARE/OS VERSIONS Linux/KDE Plasma: KDE Neon 5.27 KDE Plasma Version: 5.27.3 KDE Frameworks Version: 5.10.4.0 Qt Version: 5.15.8 -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 467211] New: save as does not autofill filename
https://bugs.kde.org/show_bug.cgi?id=467211 Bug ID: 467211 Summary: save as does not autofill filename Classification: Applications Product: kate Version: 22.04.1 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: application Assignee: kwrite-bugs-n...@kde.org Reporter: jjvall...@gmail.com Target Milestone: --- SUMMARY *** NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** STEPS TO REPRODUCE 1. Use save as to save the current file with a different filename 2. When window opens, the current filename is not shown. The filename field is left blank. 3. OBSERVED RESULT EXPECTED RESULT Current filename should be autofilled. I do lots of saving files with slightly different names, but currently I need to type the names in de novo each time SOFTWARE/OS VERSIONS Linux/KDE Plasma: Rocky 8.7, Plasma 5.24.6 (available in About System) KDE Plasma Version: 5.24.6 KDE Frameworks Version: 5.96.0 Qt Version: 5.15.3 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kconfig] [Bug 422529] Put config files inside a kde subdirectory in ~/.config, ~/.local/share, and ~/.cache
https://bugs.kde.org/show_bug.cgi?id=422529 --- Comment #22 from Joe --- (In reply to feature from comment #21) > (In reply to alexmateescu from comment #18) > > (In reply to Joe from comment #17) > > > Also chiming in that I never thought dumping everything in ~/.config was > > > ideal and would love more organization, too, of config files. I had > > > thought > > > maybe a ~/.config/plasma for all core plasma/Plasma Desktop configs and a > > > ~/.config/.kde-apps as default for any app configs - basically follow the > > > current release bundling process and nomenclature. > > > > I believe having more than one folder under .config defeats the purpose. The > > purpose being having the ability to backup/restore/delete KDE/Plasma config > > by changing just one folder. This is even beneficial for developers, because > > if users have an easy way to remove all settings, they can test cleanly a > > system that may have otherwise been migrated for years. > > Aren't Plasma and kde-apps independent? They even have their own independent > release schedule. I think separating kde-apps and plasma is a good idea. > it'd only make a "complete" kde backup\restore require a single additional > directory, while making it easier to backup\restore plasma independently. Yeah exactly my fault. The plasma folder has all of the core plasma configs, and the app one would just be the misc dumping ground for any kde app (so anything from that release group, or even kde apps that are outside of the bigger package group release). In theory then if I wanted to reset KDE/Plasma I just nuke the plasma directory and all of my app settings stay. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 373232] Horizontal lines with fractional HiDPI scaling
https://bugs.kde.org/show_bug.cgi?id=373232 --- Comment #252 from Joe --- I still get horizontal lines (again) in Konsole on 5.27.2 on Wayland w/ fractional scaling. Should I open a new bug report? -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kconfig] [Bug 422529] Put config files inside a kde subdirectory in ~/.config, ~/.local/share, and ~/.cache
https://bugs.kde.org/show_bug.cgi?id=422529 Joe changed: What|Removed |Added CC||jchevar...@gmail.com --- Comment #17 from Joe --- Also chiming in that I never thought dumping everything in ~/.config was ideal and would love more organization, too, of config files. I had thought maybe a ~/.config/plasma for all core plasma/Plasma Desktop configs and a ~/.config/.kde-apps as default for any app configs - basically follow the current release bundling process and nomenclature. -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 465659] kde-plasma/plasma-nm disappears when a intermediate SSL certificate is not found and can't make any VPN connections until logged out and logged in again
https://bugs.kde.org/show_bug.cgi?id=465659 --- Comment #2 from Joe Elusive --- Yesterday, 5.27 hit Tumbleweed repos, and applet seems to work again. Relevant package versions: openconnect-9.01-1.1.x86_64 libopenconnect5-9.01-1.1.x86_64 plasma-nm5-5.27.0-1.1.x86_64 plasma-nm5-openconnect-5.27.0-1.1.x86_64 NetworkManager-1.40.12-1.1.x86_64 NetworkManager-openconnect-1.2.8-2.1.x86_64 kded-5.103.0-1.1.x86_64 -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 465659] kde-plasma/plasma-nm disappears when a intermediate SSL certificate is not found and can't make any VPN connections until logged out and logged in again
https://bugs.kde.org/show_bug.cgi?id=465659 Joe Elusive changed: What|Removed |Added CC||joe.elus...@protonmail.com --- Comment #1 from Joe Elusive --- Possibly same issue that i've reported on Opensuse Tumbleweed bugtracker, https://bugzilla.opensuse.org/show_bug.cgi?id=1207079 Copypasting original report. This bug was reproduced on 3 different Tumbleweed machines, with 5.26.5 version Overview: When connecting to (previously working) AnyConnect vpn (using plasma-nm5-openconnect), after accepting self-signed server cert (popup window with "Signer not found" message), nm-applet window just crashes, netwokmanager logs [1673529893.2478] vpn[0x55fb7065a750,682c8bfb-8073-4b39-987b-a5cb5adeebc1,"my-vpn-name"]: secrets: failed to request VPN secrets #3: No agents were available for this request Launching kded5 manually, to check logs, yields logs attached at the bottom. Connecting to vpn from cli (using openconnect vpn.myserver.invalid) works as expected If "Debug log" checkbox selected when connecting via applet, it yields: Connected to A.B.C.D:443 SSL negotiation with vpn.myserver.invalid Server certificate verify failed: signer not found The size of the provided fingerprint is less than the minimum required (4) At the same time, connecting with cli openconnect doesn't log "The size of the provided fingerprint is less than the minimum required (4)", and gives POST https://vpn.myserver.invalid/ Connected to A.B.C.D:443 SSL negotiation with vpn.myserver.invalid Server certificate verify failed: signer not found Certificate from VPN server "vpn.myserver.invalid" failed verification. Reason: signer not found To trust this server in future, perhaps add this to your command line: --servercert pin-sha256:SOME_BASE64_STRING Enter 'yes' to accept, 'no' to abort; anything else to view: yes Connected to HTTPS on vpn.myserver.invalid with ciphersuite (TLS1.2)-(ECDHE-X25519)-(RSA-SHA256)-(AES-256-GCM) Steps to Reproduce: 1) Create an openconnect vpn profile in nm-applet, with Cisco AnyConnect protocol and vpn gateway specified 2) Connect to said vpn, via tray icon on nm-applet ui 3) After pressing Connect button, accept or cancel popup window with "Signer not found" message Actual Results: kded5 crashes, window closes, vpn connection is not established Expected Results: vpn connects Build Date & Hardware: Tumbleweed version: 20230110, fully updated at the time of report Hardware: Lenovo Ideapad 5, AMD Ryzen 5 5600U Bug start date: Somewhere in the end of December, unfortunately i haven't noted the first time it occured Relevant packages and versions: plasma-nm5-openconnect-5.26.5-1.1.x86_64 plasma-nm5-5.26.5-1.1.x86_64 NetworkManager-openconnect-lang-1.2.8-2.1.noarch openconnect-bash-completion-9.01-1.1.noarch openconnect-9.01-1.1.x86_64 libopenconnect5-9.01-1.1.x86_64 NetworkManager-1.40.8-1.1.x86_64 NetworkManager-openconnect-1.2.8-2.1.x86_64 Additional Information: - manjaro bug, that might be relevant: https://forum.manjaro.org/t/pan-vpn-connection-fails-after-an-update-again/125940 - At the same time, openconnect connected to PAN GlobalProtect VPN works as expected on same machine. kded5 logs: print-manager.kded: unable to register service to dbus org.kde.libkbolt: Failed to connect to Bolt manager DBus interface: org.kde.bolt.kded: Couldn't connect to Bolt DBus daemon xsettingsd: Reloading configuration xsettingsd: Loaded 0 settings from /home/joe/.config/xsettingsd/xsettingsd.conf xsettingsd: Reloading configuration xsettingsd: Loaded 11 settings from /home/joe/.config/xsettingsd/xsettingsd.conf xsettingsd: Reloading configuration xsettingsd: Loaded 11 settings from /home/joe/.config/xsettingsd/xsettingsd.conf xsettingsd: Reloading configuration xsettingsd: Loaded 11 settings from /home/joe/.config/xsettingsd/xsettingsd.conf xsettingsd: Reloading configuration xsettingsd: Loaded 11 settings from /home/joe/.config/xsettingsd/xsettingsd.conf xsettingsd: Reloading configuration xsettingsd: Loaded 11 settings from /home/joe/.config/xsettingsd/xsettingsd.conf xsettingsd: Reloading configuration xsettingsd: Loaded 11 settings from /home/joe/.config/xsettingsd/xsettingsd.conf xsettingsd: Reloading configuration xsettingsd: Loaded 0 settings from /home/joe/.config/xsettingsd/xsettingsd.conf xsettingsd: Reloading configuration xsettingsd: Loaded 11 settings from /home/joe/.config/xsettingsd/xsettingsd.conf xsettingsd: Reloading configuration xsettingsd: Loaded 11 settings from /home/joe/.config/xsettingsd/xsettingsd.conf Installing the delayed initialization callback. org.kde.plasma.dataengine.geolocation: gpsd not found "location" Delayed initialization. Reloading
[kwin] [Bug 457284] With AMD or NVIDIA GPU, Lock screen wallpaper is sometimes all black after waking from sleep
https://bugs.kde.org/show_bug.cgi?id=457284 --- Comment #36 from Joe --- So updated to 5.26.5, and noticed there was a commit for blank lock screen wall papers. After updating, I have yet to see this bug again. So perhaps it's fixed now? -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 413165] Please add option to reduce screen brightness in kcm_nightcolor
https://bugs.kde.org/show_bug.cgi?id=413165 Joe changed: What|Removed |Added CC||jchevar...@gmail.com --- Comment #15 from Joe --- Just came across this while going to make a feature request for it. Brightness (even via gamma) would be really great for Night Color. One of the biggest things I am missing since switching to Wayland full time as Redshift doesn't work on Wayland. Anyone know of any other work arounds ? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 271686] Keyboard shortcut to move windows to activities
https://bugs.kde.org/show_bug.cgi?id=271686 --- Comment #14 from Joe --- While adding functionality here would be the best idea - in whatever way works, as a workaround, you can build scripts in AutoKey which perform sequences of keyboard and mouse actions to configure your activities the same way you would manually. There is even the ability to do image searches on the screen, e.g. to find and select buttons or other widgets. If the required actions are complicated, they can get a bit fragile when the underlying applications change and can make the screen content change as it would when done manually, but it works and should be able to do almost anything you could do manually. AutoKey doesn't work on Wayland yet, but that's being explored. -- You are receiving this mail because: You are watching all bug changes.
[kde-cli-tools] [Bug 429408] kde-open5 changes case of argument
https://bugs.kde.org/show_bug.cgi?id=429408 Joe changed: What|Removed |Added CC||jchevar...@gmail.com --- Comment #8 from Joe --- Just wanted to say I came across this the other day and as Egon so nicely put it, it was "annoyingly annoying". I ended up just doing things in Firefox to make signing into Slack work. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 461345] New: Printing an A4 document (with A4 paper) from a system with US/Letter setup as default doesn't work
https://bugs.kde.org/show_bug.cgi?id=461345 Bug ID: 461345 Summary: Printing an A4 document (with A4 paper) from a system with US/Letter setup as default doesn't work Classification: Applications Product: okular Version: 22.08.2 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: printing Assignee: okular-de...@kde.org Reporter: jchevar...@gmail.com Target Milestone: --- Operating System: Arch Linux KDE Plasma Version: 5.26.2 KDE Frameworks Version: 5.99.0 Qt Version: 5.15.7 Kernel Version: 6.0.6-arch1-1 (64-bit) Graphics Platform: X11 Processors: 24 × AMD Ryzen 9 5900X 12-Core Processor Memory: 31.3 GiB of RAM Graphics Processor: NVIDIA GeForce RTX 2080 SUPER/PCIe/SSE2 SUMMARY I am in the US and mainly (read: pretty much always) print US Letter when I need to print something. I recently had to print an A4 PDF, so I ordered some A4 paper and gave it a go. I tried just about everything in the printer dialog in okular but could not get any combination of options to work and actually print the thing full size and not strangely scaled (smaller than US Letter, also). I then tried just opening the PDF and Firefox and printing from there: I set the paper to A4, hit print, and it worked perfectly. Issues I had: Changing the paper size under the printer "Properties" seems rather broken. When I go from Letter to A4, non of the margins update, and they also stay in inches vs mm/cm. Even manually adjusting the margins to be the "proper" size that I found for A4 did not result in the page being printed full size. Under the general printer dialog, I tried 'Fit to printable area' as scaling, along with none (print original size), and fit to the full page. None of these options worked to make the PDF print properly to the full A4 page size instead of being shrunken in the middle with huge top/bottom margins and sides. I would expect that the 'none' option should work since the document needed no scaling and was natively A4. I also played with the 'Force rasterization' option to little effect. Another tangential issue I had was attempting to scale and print the A4 document to US Letter - which also didn't work and was either way too small or just cut off. I guess there is something not quite right in both dialogs and how scaling is done and generally setting the paper size. And to note it doesn't seem to be just my cups setup, as Firefox printed it perfectly using its dialog and paper settings first go. OBSERVED RESULT A4 document wouldn't print properly on A4 paper (and wouldn't also scale on Letter paper) EXPECTED RESULT The A4 document when A4 paper is chosen would print on A4 paper. Or, if Letter is select and Letter paper is used, then using the scaling options to print to page would scale the A4 document and print it correctly. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 425056] KWin crashes/dies after resume from sleep
https://bugs.kde.org/show_bug.cgi?id=425056 --- Comment #7 from Joe --- So in general, I don't think this is happening anymore, and probably should be closed. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 457284] Lock screen wallpaper is all black after waking from sleep
https://bugs.kde.org/show_bug.cgi?id=457284 Joe changed: What|Removed |Added CC||jchevar...@gmail.com --- Comment #34 from Joe --- This is fixed on my NVidia system (X11), but oddly enough, I am still seeing this on my AMD build (Wayland): Operating System: Arch Linux KDE Plasma Version: 5.26.2 KDE Frameworks Version: 5.99.0 Qt Version: 5.15.7 Kernel Version: 6.0.2-arch1-1 (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 5500 XT Manufacturer: Micro-Star International Co., Ltd. Product Name: MS-7B85 System Version: 1.0 I am still getting a black wallpaper on the screen locker on occasions when resuming from sleep/hibernate. I don't see anything particularly useful in journalctl, either. -- You are receiving this mail because: You are watching all bug changes.
[NeoChat] [Bug 460679] New: Application provides no way to change account avatar
https://bugs.kde.org/show_bug.cgi?id=460679 Bug ID: 460679 Summary: Application provides no way to change account avatar Classification: Applications Product: NeoChat Version: unspecified Platform: Archlinux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: General Assignee: fe...@posteo.de Reporter: jyamine...@gmail.com CC: c...@carlschwan.eu Target Milestone: --- Created attachment 153012 --> https://bugs.kde.org/attachment.cgi?id=153012=edit Screenshot of the account editor with current (unchangeable) avatar indicated SUMMARY NeoChat does not provide functionality to select the avatar that appears beside the user's name in chats and user lists. If they set the avatar using a different client, such as the Element web client, NeoChat has a button to remove that avatar and revert to the default letter bubble. STEPS TO REPRODUCE 1. Click the pencil button next to an account in the Accounts section of the configuration menu to edit the account. 2. Click on the avatar in the account editing window. OBSERVED RESULT Nothing happens EXPECTED RESULT Either clicking on the current avatar or clicking on a button next to the avatar opens a file picker to upload a new avatar SOFTWARE/OS VERSIONS Linux: 6.0.1.arch1-1 NeoChat: 22.09 KDE Frameworks Version: 5.99.0 Qt Version: 5.15.6 -- You are receiving this mail because: You are watching all bug changes.
[Skanpage] [Bug 458803] New: Skanpage (and Skanlite) doesn't respect localization settings
https://bugs.kde.org/show_bug.cgi?id=458803 Bug ID: 458803 Summary: Skanpage (and Skanlite) doesn't respect localization settings Product: Skanpage Version: 22.08.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: a.stipp...@gmx.net Reporter: jchevar...@gmail.com Target Milestone: --- I've noticed that Skanpage (and Skanlite before it) don't seem to respect localization settings set in the system. The size defaults to 'custom' for me, when I expect it should be US Letter. Also, when selecting showing the more options, sizes are in mm when I would expect inches. Operating System: Arch Linux Skanpage: 22.08.0 KDE Plasma Version: 5.25.5 KDE Frameworks Version: 5.97.0 Qt Version: 5.15.5 Kernel Version: 5.19.3-arch1-1 (64-bit) Graphics Platform: X11 -- You are receiving this mail because: You are watching all bug changes.
[Skanpage] [Bug 450123] Please add ability to crop images after scan
https://bugs.kde.org/show_bug.cgi?id=450123 Joe changed: What|Removed |Added CC||jchevar...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[Skanpage] [Bug 457097] Scanning letter sized pages adds a blank area to scanned image
https://bugs.kde.org/show_bug.cgi?id=457097 Joe changed: What|Removed |Added CC||jchevar...@gmail.com --- Comment #1 from Joe --- I can also reproduce this easily on Arch. Changing back to a custom (which was previously working) also inserts the black section. So perhaps it is just triggered when changing page size in general? Operating System: Arch Linux Skanpage 22.08.0 KDE Plasma Version: 5.25.5 KDE Frameworks Version: 5.97.0 Qt Version: 5.15.5 Kernel Version: 5.19.3-arch1-1 (64-bit) Graphics Platform: X11 -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 456534] New: "Toggle Comments" Tool Sometimes indefinitely adds comment symbols in python on each press
https://bugs.kde.org/show_bug.cgi?id=456534
Bug ID: 456534
Summary: "Toggle Comments" Tool Sometimes indefinitely adds
comment symbols in python on each press
Product: kate
Version: 22.04.2
Platform: Other
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: general
Assignee: kwrite-bugs-n...@kde.org
Reporter: shefabu...@gmail.com
Target Milestone: ---
SUMMARY
Testing a python script, I attempted to toggle comments on a few blocks of
code, the toggle instead added indefinitely to the existing comment symbol (not
automatically, each press adds a new symbol)
STEPS TO REPRODUCE
1. Create a basic script, here's an example:
def main():
print("hello world")
if 1 == 1:
print("yes")
print("after")
if __name__ = '__main__':
main()
2. Highlight portions you wish to comment out, hit the toggle comment shortcut
(default is ctrl + /), then hit it again, if multiple blocks of code are
highlighted, like both the function and the if statement at the bottom, it
seems to add more comment characters instead of un-commenting what you just
commented (goes for existing comments as well)
OBSERVED RESULT
Additional comment symbols added
EXPECTED RESULT
Toggle between a line being commented and not (adding/removing symbol as
needed)
SOFTWARE/OS VERSIONS
Linux: EndeavourOS, Gnome DE (wayland support :/ )
KDE Plasma Version:
KDE Frameworks Version:
Qt Version:
ADDITIONAL INFORMATION
I attempted to find where this code is in gitlab, but couldn't seem to find the
lines that were for toggle comment as the only things mentioning "toggle
comment" exactly were some .docbook files - so am not able to determine the
issue myself. **I will happily dive into the code as well if someone can point
me to the right spot to look**
--
You are receiving this mail because:
You are watching all bug changes.
[ark] [Bug 426499] Draggable area not clearly signposted/misleading highlighting
https://bugs.kde.org/show_bug.cgi?id=426499 --- Comment #10 from Joe Dight --- (In reply to Andrey from comment #8) > Here is how it looks like: > https://invent.kde.org/utilities/ark/-/merge_requests/115#note_447931 > > There are different opinions if it actually fixes the bug. > I would love to know what OP thinks about it. I can't see if the lighter/darker split also exists on hover, when no selection has been made. If it does (or is made obvious somehow else) the bug is definitely fixed. Otherwise it's more nebulous, because you still can't tell where to drag before you've made a selection. But maybe that would be a new bug? Sadly, the SUMMARY is rather broader than the STEPS TO REPRODUCE, which is where the uncertainty arises I think. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 453266] Flipping the pen no longer erases
https://bugs.kde.org/show_bug.cgi?id=453266 --- Comment #4 from Joe Nosie --- (In reply to amyspark from comment #3) > Hi, could you check with the 5.0.6 release and the latest nightly? I fixed a > couple of these bugs a month or so ago. I haven't checked the nightly, but the issue does still happen on the 5.0.6 appimage. I'll try a nightly later and see. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 453266] Flipping the pen no longer erases
https://bugs.kde.org/show_bug.cgi?id=453266 --- Comment #2 from Joe Nosie --- (In reply to Alvin Wong from comment #1) > Have you tried switching to an eraser brush preset after flipping to the > eraser tip? Yes. When I do that, it doesn't change back automatically when I flip back. It's simply not switching between settings when I flip the pen. -- You are receiving this mail because: You are watching all bug changes.
[forum.kde.org] [Bug 452365] New: Blinding white default skin
https://bugs.kde.org/show_bug.cgi?id=452365 Bug ID: 452365 Summary: Blinding white default skin Product: forum.kde.org Version: unspecified Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: general Assignee: forum-ad...@kde.org Reporter: jos.buck...@verizon.net Target Milestone: --- SUMMARY *** Please provide a setting to change from the blinding white default skin. It would be appreciated. *** STEPS TO REPRODUCE 1. go to forum.kde.org 2. 3. OBSERVED RESULT EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 450946] Window Close Button doesn't take up the entire corner
https://bugs.kde.org/show_bug.cgi?id=450946 --- Comment #3 from Joe --- I actually just noticed something. Native KDE apps are fine, but it is happening on Firefox. -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 450946] Window Close Button doesn't take up the entire corner
https://bugs.kde.org/show_bug.cgi?id=450946 --- Comment #2 from Joe --- Hey, checked it and it was already unchecked, If its helps I am on a 1440p monitor with a scale factor of 125%. Running X11 as, well, Nvidia and all that. On my intel laptop (4k, 2x scale factor) things are fun under Wayland, as-is my other desktop using an AMD card (also 1440p and Wayland). So maybe just a fractional scaling issue on X11? -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 450988] baloo_file_extractor crashes when login
https://bugs.kde.org/show_bug.cgi?id=450988 Joe Turpin changed: What|Removed |Added CC||joe.tur...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 450988] baloo_file_extractor crashes when login
https://bugs.kde.org/show_bug.cgi?id=450988 --- Comment #3 from Joe Turpin --- Created attachment 147519 --> https://bugs.kde.org/attachment.cgi?id=147519=edit New crash information added by DrKonqi baloo_file_extractor (5.68.0) using Qt 5.12.8 - What I was doing when the application crashed: I logged into the KDE desktop and shortly thereafter the baloo_file_extractor crash was reported through a desktop notification. -- Backtrace (Reduced): #7 __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50 #8 0x7f7e04cfb859 in __GI_abort () at abort.c:79 #9 0x7f7e04a25a83 in mdb_assert_fail (env=0x5562845486a0, expr_txt=expr_txt@entry=0x7f7e04a2802f "rc == 0", func=func@entry=0x7f7e04a28978 <__func__.7221> "mdb_page_dirty", line=line@entry=2127, file=0x7f7e04a28010 "mdb.c") at mdb.c:1542 #10 0x7f7e04a1a6d5 in mdb_page_dirty (mp=, txn=0x556284549b90) at mdb.c:2114 #11 mdb_page_dirty (txn=0x556284549b90, mp=) at mdb.c:2114 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 450119] Plasma slow/freezes on resume - possible memory leak?
https://bugs.kde.org/show_bug.cgi?id=450119 --- Comment #10 from Joe --- (In reply to David Edmundson from comment #9) > That log is confusing, most is from /usr/bin/php8.1 > > I couldn't see much from plasma What would you need? I can try to grab it next time it happens. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 450266] KWin seg fault
https://bugs.kde.org/show_bug.cgi?id=450266 --- Comment #8 from Joe --- I thought I did attach the requested core dumps on 2/15. Am I missing anything else? -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 450946] New: Window Close Button doesn't take up the entire corner
https://bugs.kde.org/show_bug.cgi?id=450946 Bug ID: 450946 Summary: Window Close Button doesn't take up the entire corner Product: Breeze Version: 5.24.2 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: jchevar...@gmail.com Target Milestone: --- SUMMARY *** NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** STEPS TO REPRODUCE 1. Open any window like Dolphin or Firefox 2. Full Screen it. 3. Move cursor to top right corner OBSERVED RESULT The 'Close Window' button isn't highlighted, its basically just title bar EXPECTED RESULT The 'Close Window' button should be highlight lighted and the window close if you click it SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 5.24.2 KDE Frameworks Version: 5.91.0 Qt Version: 5.15.2 Kernel Version: 5.16.11-arch1-1 (64-bit) Graphics Platform: X11 Processors: 24 × AMD Ryzen 9 5900X 12-Core Processor Memory: 31.3 GiB of RAM Graphics Processor: NVIDIA GeForce RTX 2080 SUPER/PCIe/SSE2 ADDITIONAL INFORMATION So, noticed that if I have a window that the close button in the top right no longer activates essentially with the entire area of the window title bar, now it is just the little circle around the X, even in full screen mode. I vaguely remember a previous bug about this where it was determined that essentially the entire right corner should be able to active 'close', at least in full screen windows? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 450119] Plasma slow/freezes on resume - possible memory leak?
https://bugs.kde.org/show_bug.cgi?id=450119 --- Comment #7 from Joe --- Upgraded to 5.24.1 and Framworks 5.91. and have had this happen multiple times when resuming from sleep. Really, Plasmashell just takes off to the races consuming all of the memory it can until eventually the OOM killer takes care of it. -- You are receiving this mail because: You are watching all bug changes.
[plasma-pa] [Bug 412427] USB Audio Source Disappearing
https://bugs.kde.org/show_bug.cgi?id=412427 Joe changed: What|Removed |Added Resolution|--- |WORKSFORME Status|REPORTED|RESOLVED --- Comment #1 from Joe --- Resolving this - i haven't seen it in a long time, especially after switching to pipewire. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 450266] KWin seg fault
https://bugs.kde.org/show_bug.cgi?id=450266 --- Comment #6 from Joe --- Hey Vlad, attached. Since I am using X11 (thanks, Nvidia), I assume you meant kwin_x11 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 450266] KWin seg fault
https://bugs.kde.org/show_bug.cgi?id=450266 --- Comment #5 from Joe --- Created attachment 146780 --> https://bugs.kde.org/attachment.cgi?id=146780=edit core dump 2 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 450266] KWin seg fault
https://bugs.kde.org/show_bug.cgi?id=450266 --- Comment #4 from Joe --- Created attachment 146779 --> https://bugs.kde.org/attachment.cgi?id=146779=edit code dump 1 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 450266] KWin seg fault
https://bugs.kde.org/show_bug.cgi?id=450266 --- Comment #2 from Joe --- Created attachment 146748 --> https://bugs.kde.org/attachment.cgi?id=146748=edit second segfault trying to renable after restart so, just noticed after restart that desktop effects actually didn't re-enable. Trying to re-enable them in SystemSettings results in this segfault. Core dump for this is also slightly bigger than file attachment limit. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 450266] KWin seg fault
https://bugs.kde.org/show_bug.cgi?id=450266 --- Comment #1 from Joe --- Actually, can't attach the core dump as its too big (along with a plasma shell one from around the same time, both are pretty big). -- You are receiving this mail because: You are watching all bug changes.
