[calligrasheets] [Bug 485179] New: Crashes when opening .ods file created by Libreoffice
https://bugs.kde.org/show_bug.cgi?id=485179 Bug ID: 485179 Summary: Crashes when opening .ods file created by Libreoffice Classification: Applications Product: calligrasheets Version: 3.2.1 Platform: Kubuntu OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: calligra-sheets-bugs-n...@kde.org Reporter: wg51r...@mailer.me Target Milestone: --- Application: calligrasheets (3.2.1) Qt Version: 5.15.3 Frameworks Version: 5.104.0 Operating System: Linux 6.7.12-1-liquorix-amd64 x86_64 Windowing System: X11 Distribution: Ubuntu 22.04.4 LTS DrKonqi: 5.27.10 [KCrashBackend] -- Information about the crash: Every time I open .ods file created by Libreoffice Calc, Calligra sheets crashes. The crash can be reproduced every time. -- Backtrace: Application: Calligra Sheets (calligrasheets), signal: Segmentation fault [KCrash Handler] #4 0x0171 in ?? () #5 0x7e5cf4b4cd62 in Calligra::Sheets::StyleManager::~StyleManager() () from /lib/x86_64-linux-gnu/libcalligrasheetsodf.so.17 #6 0x7e5cf4b1f2c3 in Calligra::Sheets::Map::~Map() () from /lib/x86_64-linux-gnu/libcalligrasheetsodf.so.17 #7 0x7e5cf4b0c43f in Calligra::Sheets::DocBase::~DocBase() () from /lib/x86_64-linux-gnu/libcalligrasheetsodf.so.17 #8 0x7e5cf4f28d5d in Calligra::Sheets::Doc::~Doc() () from /lib/x86_64-linux-gnu/libcalligrasheetscommon.so.17 #9 0x7e5d06fa9881 in KoMainWindow::setRootDocument(KoDocument*, KoPart*, bool) () from /lib/x86_64-linux-gnu/libkomain.so.17 #10 0x7e5d06fb2395 in KoMainWindow::closeEvent(QCloseEvent*) () from /lib/x86_64-linux-gnu/libkomain.so.17 #11 0x7e5d061af4ee in QWidget::event(QEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #12 0x7e5d04f965bd in KXmlGuiWindow::event(QEvent*) () from /lib/x86_64-linux-gnu/libKF5XmlGui.so.5 #13 0x7e5d0616c713 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #14 0x7e5d06f9034d in KoApplication::notify(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libkomain.so.17 #15 0x7e5d05cb9e3a in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #16 0x7e5d061aa800 in QWidgetPrivate::close_helper(QWidgetPrivate::CloseMode) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #17 0x7e5d061cc128 in ?? () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #18 0x7e5d0616c713 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #19 0x7e5d06f9034d in KoApplication::notify(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libkomain.so.17 #20 0x7e5d05cb9e3a in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #21 0x7e5d0453df1d in QGuiApplicationPrivate::processCloseEvent(QWindowSystemInterfacePrivate::CloseEvent*) () from /lib/x86_64-linux-gnu/libQt5Gui.so.5 #22 0x7e5d04516a2c in QWindowSystemInterface::sendWindowSystemEvents(QFlags) () from /lib/x86_64-linux-gnu/libQt5Gui.so.5 #23 0x7e5cffaf8d6e in ?? () from /lib/x86_64-linux-gnu/libQt5XcbQpa.so.5 #24 0x7e5d03520d3b in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #25 0x7e5d03576258 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #26 0x7e5d0351e3e3 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #27 0x7e5d05d130b8 in QEventDispatcherGlib::processEvents(QFlags) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #28 0x7e5d05cb875b in QEventLoop::exec(QFlags) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #29 0x7e5d05cc0cf4 in QCoreApplication::exec() () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #30 0x7e5d07027d39 in kdemain () from /lib/x86_64-linux-gnu/libkdeinit5_calligrasheets.so #31 0x7e5d06c29d90 in __libc_start_call_main (main=main@entry=0x5d593ec26060, argc=argc@entry=2, argv=argv@entry=0x7ffd045d2f38) at ../sysdeps/nptl/libc_start_call_main.h:58 #32 0x7e5d06c29e40 in __libc_start_main_impl (main=0x5d593ec26060, argc=2, argv=0x7ffd045d2f38, init=, fini=, rtld_fini=, stack_end=0x7ffd045d2f28) at ../csu/libc-start.c:392 #33 0x5d593ec26095 in ?? () [Inferior 1 (process 30530) detached] Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 416145] Krunner doesn't immediately intercept rapidly-typed keystrokes for first invocation after login, leading the user to accidentally type text into whatever app is open
https://bugs.kde.org/show_bug.cgi?id=416145 Edward Donovan changed: What|Removed |Added CC|kde-b...@numble.net | -- You are receiving this mail because: You are watching all bug changes.
[korganizer] [Bug 482229] New: Korganiser won't show notifications
https://bugs.kde.org/show_bug.cgi?id=482229 Bug ID: 482229 Summary: Korganiser won't show notifications Classification: Applications Product: korganizer Version: 5.20.3 Platform: Kubuntu OS: Linux Status: REPORTED Severity: grave Priority: NOR Component: reminder daemon (korgac) Assignee: kdepim-b...@kde.org Reporter: wg51r...@mailer.me Target Milestone: --- SUMMARY *** Korganiser is not crashing. But it is not showing notifications for events. I used to get a dialog for my events. I had face this issue on Plasma 5.25 and still facing the issue on 5.27. *** STEPS TO REPRODUCE 1. Create an event and add reminder. 2. Wait for it to trigger 3. Notice no notification OBSERVED RESULT Notification not showing up for events EXPECTED RESULT Notification should be shown for events SOFTWARE/OS VERSIONS Linux/KDE Plasma: kUbuntu 22.04 (all updates installed) (available in About System) KDE Plasma Version: 5.27.10 (installed using backports PPA) KDE Frameworks Version: 5.104.0 Qt Version: 5.15.3 -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 481283] Kmail crashes when I try to open mail
https://bugs.kde.org/show_bug.cgi?id=481283 Edward Torvalds changed: What|Removed |Added Status|RESOLVED|REPORTED Resolution|UNMAINTAINED|--- --- Comment #3 from Edward Torvalds --- I just want to add a 'LOL'. From the stack trace, I can see Kmail is crashing because of speech dispatcher. This issue has annoyed me for months. I have uninstalled all speech dispatcher related packages and Kmail wouldn't crash anymore. Glorious days of software engineering. Next issue for me to fix is to figure out why Korganiser won't show notifications for events. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 481283] Kmail crashes when I try to open mail
https://bugs.kde.org/show_bug.cgi?id=481283 --- Comment #2 from Edward Torvalds --- Created attachment 166302 --> https://bugs.kde.org/attachment.cgi?id=166302=edit New crash information added by DrKonqi kmail (5.20.3 (22.04.3)) using Qt 5.15.3 I have installed Plasma 5.27.1 on Kubuntu 22.04 using backports PPA. Post that system has become more unstable. Even Korganiser does not shows pop-up reminder. -- Backtrace (Reduced): #4 __strlen_avx2 () at ../sysdeps/x86_64/multiarch/strlen-avx2.S:74 [...] #6 0x77b880026877 in spd_execute_command_with_list_reply () at /lib/x86_64-linux-gnu/libspeechd.so.2 [...] #10 0x77b8934180d3 in QTextToSpeech::QTextToSpeech(QString const&, QObject*) () at /lib/x86_64-linux-gnu/libQt5TextToSpeech.so.5 #11 0x77b8986cd946 in KPIMTextEdit::TextToSpeech::reloadSettings() () at /lib/x86_64-linux-gnu/libKF5PimTextEdit.so.5abi3 #12 0x77b8986cda54 in KPIMTextEdit::TextToSpeech::self() () at /lib/x86_64-linux-gnu/libKF5PimTextEdit.so.5abi3 -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 481283] Kmail crashes when I try to open mail
https://bugs.kde.org/show_bug.cgi?id=481283 Edward Torvalds changed: What|Removed |Added CC||wg51r...@mailer.me -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 461532] Kontact will crash when opening. Choosing "Restart application" mostly works.
https://bugs.kde.org/show_bug.cgi?id=461532 --- Comment #1 from Edward Torvalds --- Created attachment 166111 --> https://bugs.kde.org/attachment.cgi?id=166111=edit New crash information added by DrKonqi korganizer (5.20.3 (22.04.3)) using Qt 5.15.3 app crashes when trying to add new even by double click on day -- Backtrace (Reduced): #4 __strlen_avx2 () at ../sysdeps/x86_64/multiarch/strlen-avx2.S:74 [...] #6 0x7c273c036877 in spd_execute_command_with_list_reply () from /lib/x86_64-linux-gnu/libspeechd.so.2 [...] #10 0x7c2756ac80d3 in QTextToSpeech::QTextToSpeech(QString const&, QObject*) () from /lib/x86_64-linux-gnu/libQt5TextToSpeech.so.5 #11 0x7c2757d32946 in KPIMTextEdit::TextToSpeech::reloadSettings() () from /lib/x86_64-linux-gnu/libKF5PimTextEdit.so.5abi3 #12 0x7c2757d32a54 in KPIMTextEdit::TextToSpeech::self() () from /lib/x86_64-linux-gnu/libKF5PimTextEdit.so.5abi3 -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 461532] Kontact will crash when opening. Choosing "Restart application" mostly works.
https://bugs.kde.org/show_bug.cgi?id=461532 Edward Torvalds changed: What|Removed |Added CC||wg51r...@mailer.me -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 481283] New: Kmail crashes when I try to open mail
https://bugs.kde.org/show_bug.cgi?id=481283 Bug ID: 481283 Summary: Kmail crashes when I try to open mail Classification: Applications Product: kmail2 Version: unspecified Platform: Kubuntu OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: wg51r...@mailer.me Target Milestone: --- Application: kmail (5.20.3 (22.04.3)) Qt Version: 5.15.3 Frameworks Version: 5.104.0 Operating System: Linux 6.7.4-1-liquorix-amd64 x86_64 Windowing System: X11 Distribution: Ubuntu 22.04.3 LTS DrKonqi: 5.27.10 [KCrashBackend] -- Information about the crash: This hapens every time when I click on the email in the inbox. I had face this issue on Plasma 5.25 and still facing the issue on 5.27. Using IMAP connection. The crash can be reproduced every time. -- Backtrace: Application: KMail (kmail), signal: Segmentation fault [KCrash Handler] #4 __strlen_avx2 () at ../sysdeps/x86_64/multiarch/strlen-avx2.S:74 #5 0x72955bff6aca in () at /lib/x86_64-linux-gnu/libspeechd.so.2 #6 0x72955bff7877 in spd_execute_command_with_list_reply () at /lib/x86_64-linux-gnu/libspeechd.so.2 #7 0x72956006d07a in () at /usr/lib/x86_64-linux-gnu/qt5/plugins/texttospeech/libqtexttospeech_speechd.so #8 0x72956006f073 in () at /usr/lib/x86_64-linux-gnu/qt5/plugins/texttospeech/libqtexttospeech_speechd.so #9 0x729572c12cf1 in () at /lib/x86_64-linux-gnu/libQt5TextToSpeech.so.5 #10 0x729572c130d3 in QTextToSpeech::QTextToSpeech(QString const&, QObject*) () at /lib/x86_64-linux-gnu/libQt5TextToSpeech.so.5 #11 0x729577412946 in KPIMTextEdit::TextToSpeech::reloadSettings() () at /lib/x86_64-linux-gnu/libKF5PimTextEdit.so.5abi3 #12 0x729577412a54 in KPIMTextEdit::TextToSpeech::self() () at /lib/x86_64-linux-gnu/libKF5PimTextEdit.so.5abi3 #13 0x7295774156f3 in KPIMTextEdit::TextToSpeechInterface::TextToSpeechInterface(KPIMTextEdit::TextToSpeechWidget*, QObject*) () at /lib/x86_64-linux-gnu/libKF5PimTextEdit.so.5abi3 #14 0x7295774137d1 in KPIMTextEdit::TextToSpeechWidget::TextToSpeechWidget(QWidget*) () at /lib/x86_64-linux-gnu/libKF5PimTextEdit.so.5abi3 #15 0x729577f7af79 in MessageViewer::ViewerPrivate::createWidgets() () at /lib/x86_64-linux-gnu/libKF5MessageViewer.so.5abi5 #16 0x729577f8db98 in MessageViewer::ViewerPrivate::ViewerPrivate(MessageViewer::Viewer*, QWidget*, KActionCollection*) () at /lib/x86_64-linux-gnu/libKF5MessageViewer.so.5abi5 #17 0x729577f75a96 in MessageViewer::Viewer::Viewer(QWidget*, QWidget*, KActionCollection*) () at /lib/x86_64-linux-gnu/libKF5MessageViewer.so.5abi5 #18 0x7295825eb1fb in KMReaderWin::KMReaderWin(QWidget*, QWidget*, KActionCollection*) () at /lib/x86_64-linux-gnu/libkmailprivate.so.5 #19 0x72958261d1db in KMReaderMainWin::KMReaderMainWin(MessageViewer::Viewer::DisplayFormatMessage, bool, QString const&) () at /lib/x86_64-linux-gnu/libkmailprivate.so.5 #20 0x729582628d2a in KMMainWidget::slotMessageActivated(Akonadi::Item const&) () at /lib/x86_64-linux-gnu/libkmailprivate.so.5 #21 0x729578ef1793 in () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #22 0x7295787abc19 in MessageList::Pane::messageActivated(Akonadi::Item const&) () at /lib/x86_64-linux-gnu/libKF5MessageList.so.5abi1 #23 0x729578ef1793 in () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #24 0x72957872cf39 in MessageList::Widget::messageActivated(Akonadi::Item const&) () at /lib/x86_64-linux-gnu/libKF5MessageList.so.5abi1 #25 0x7295787b95da in MessageList::Widget::viewMessageActivated(MessageList::Core::MessageItem*) () at /lib/x86_64-linux-gnu/libKF5MessageList.so.5abi1 #26 0x729579bafe79 in QWidget::event(QEvent*) () at /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #27 0x729579c5d422 in QFrame::event(QEvent*) () at /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #28 0x729578eb9b9a in QCoreApplicationPrivate::sendThroughObjectEventFilters(QObject*, QEvent*) () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #29 0x729579b6c702 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #30 0x729579b74364 in QApplication::notify(QObject*, QEvent*) () at /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #31 0x729578eb9e3a in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #32 0x729579b72e47 in QApplicationPrivate::sendMouseEvent(QWidget*, QMouseEvent*, QWidget*, QWidget*, QWidget**, QPointer&, bool, bool) () at /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #33 0x729579bc8d40 in () at /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #34 0x729579bcbfd5 in () at /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #35 0x729579b6c713 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #36 0x729578eb9e3a in
[kwin] [Bug 475605] On X11 with NVIDIA GPU and proprietary driver, black screen with only cursor shown on wake from sleep
https://bugs.kde.org/show_bug.cgi?id=475605 Edward Oubrayrie changed: What|Removed |Added CC||edoubray...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 477738] [NVIDIA] kwin on Wayland black screen with cursor after most resume-from-RAM
https://bugs.kde.org/show_bug.cgi?id=477738 Edward Oubrayrie changed: What|Removed |Added CC||edoubray...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 446389] On Wayland, KWin doesn't differentiate numberpad number key shortcuts from above-the-letters number key shortcuts
https://bugs.kde.org/show_bug.cgi?id=446389 Edward Oubrayrie changed: What|Removed |Added CC||edoubray...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 472705] 5.2 Android: Krita crashes when accessibility apps are enabled
https://bugs.kde.org/show_bug.cgi?id=472705 --- Comment #70 from Edward Mowah --- (In reply to sh_zam from comment #69) > Thanks a lot for the immense help! It wouldn't have been possible to fix it > without it! > > I'll kick off the dependencies build, please test the nightly if possible, > Halla will soon make a release with this patch :)) Tested nightly build #1276 with the fix and it doesn't crash with accessibility apps enabled. Thanks. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 472705] 5.2 Android: App crashes randomly for unknown reasons, except when running app on a second user account
https://bugs.kde.org/show_bug.cgi?id=472705 --- Comment #58 from Edward Mowah --- ENABLING ACCESSIBILITY APPLICATIONS (SUCH AS BITWARDEN AND MICROSOFT AUTHENTICATOR) IS CAUSING KRITA TO CRASH I backed up my device files, apps and settings and did a factory reset (Galaxy Tab S9 Ultra) After reset, I didn't connect to any network at the beginning. I also didn't logon to any account (Google / Samsung) No application updates, no setting changed besides switching device to dark mode. I uninstalled / disabled 3rd party apps / bloat like always. Krita ran without crashing. As soon as I restored everything from my back up including apps and device settings, krita began crashing again. I repeated the process but this time I logged in to Google and Samsung right from the beginning after reset and even updated applications. I uninstalled bloat like always. But I didn't install any other application or change any settings (besides switching to dark mode) Krita runs fine. >From here for each app installed and for each settings changed, I will opened Krita and see if it will crash. Krita ran without crashing until I installed and set up Bitwarden on my device. At first I thought it was just Bitwarden itself, because Krita ran fine up until I set Bitwarden up, but then Microsoft Authenticator also Caused Krita to crash. Both apps have similar settings and one among them is enabling them in Accessibility Settings. I found that when either app was enabled under Accessibility settings, krita crashed. By disabling them in Accessibility settings I am able to run krita without a crash. Can someone else who's having this issue confirm that they have any app enabled under accessibility settings? (Maybe it's not just Bitwarden and Microsoft Authenticator) -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 447717] plasmashell crashes when hovering or clicking items on the Panel due to "zwp_linux_buffer_params_v1.add" protocol error
https://bugs.kde.org/show_bug.cgi?id=447717 Edward Oubrayrie changed: What|Removed |Added CC||edoubray...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kio-gdrive] [Bug 464772] kio-gdrive successfully authenticates but fails to list content
https://bugs.kde.org/show_bug.cgi?id=464772 Edward changed: What|Removed |Added CC||papashre...@gmail.com --- Comment #4 from Edward --- new install within last 24 hours, this issue is still persistent in kio-gdrive keep getting the error "Expired or missing access tokens for account google1" when I go to copy files from google drive on to my system. it took me multiple attempts to be able to load the directory structure without that error. system specs: OS: EndeavourOS KDE plasma version: 5.27.9 Kernel: 6.5.9-arch2-1 kio-gdrive version: 23.08.2-1 Please notify if you need more information. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 472705] 5.2 Android: App crashes shortly after transforming multiple layers or at random moments
https://bugs.kde.org/show_bug.cgi?id=472705 --- Comment #51 from Edward Mowah --- (In reply to abhifx from comment #50) > (In reply to sh_zam from comment #49) > > This has to be one of the strangest bugs. Even though this is released on > > Play Store, we still haven't gotten a reliable trace for what could be > > causing this. > > > > The best trace we have so far is: > > > > > > *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** > > pid: 0, tid: 5543 >>> org.krita <<< > > > > backtrace: > > #00 pc 0x003f4914 > > /data/app/~~s4vVKEiQg06UcFf_OnKCpg==/org.krita-mKvXqVAtIikUr2tRfRWPgA==/lib/ > > arm64/libQt5Core_arm64-v8a.so (QCoreApplication::notifyInternal2(QObject*, > > QEvent*)+136) (BuildId: 2bdd3f7eab36cfc0ad5e470fffa7da3134b29a8e) > > #01 pc 0x0042c474 > > /data/app/~~s4vVKEiQg06UcFf_OnKCpg==/org.krita-mKvXqVAtIikUr2tRfRWPgA==/lib/ > > arm64/libQt5Core_arm64-v8a.so (QTimerInfoList::activateTimers()+572) > > (BuildId: 2bdd3f7eab36cfc0ad5e470fffa7da3134b29a8e) > > #02 pc 0x0042ab44 > > /data/app/~~s4vVKEiQg06UcFf_OnKCpg==/org.krita-mKvXqVAtIikUr2tRfRWPgA==/lib/ > > arm64/libQt5Core_arm64-v8a.so > > (QEventDispatcherUNIX::processEvents(QFlags > ProcessEventsFlag>)+424) (BuildId: 2bdd3f7eab36cfc0ad5e470fffa7da3134b29a8e) > > #03 pc 0x0007f804 > > /data/app/~~s4vVKEiQg06UcFf_OnKCpg==/org.krita-mKvXqVAtIikUr2tRfRWPgA==/lib/ > > arm64/libplugins_platforms_qtforandroid_arm64-v8a.so > > (QUnixEventDispatcherQPA::processEvents(QFlags > ProcessEventsFlag>)) (BuildId: da874e365af3bb7ac512787bbeaadd91760d) > > > > which doesn't tell us where in Krita this is happening :( > > This is absolutely strange, although intermittently all apps in android > should be sandboxed, could it be possible any other app install is causing > some mayhem? maybe all people reporting bugs should list down all the apps. > I am basing this assumption based on finding that an alternative user which > has minimal apps installed is running it fine. (Or android is blocking that > user from accessing something) I did a factory reset of my device (Tab s9 Ultra) and installed only Krita. It still crashes. I removed all 3rd party bloat and it made no difference. However, on a 2nd user profile I created on the same device just to see if it will work, somehow it doesn't crash there, it only crashes on the main profile. I've gone out of my way to try and get it to crash, installing the same apps I'd normally use, randomly clicking everything I possibly can, painting on large canvas (2x2), it still wont crash. So far, this issue is limited only to the main user profile. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 476133] New: Galaxy Tab S9 Ultra SM-X910 - Krita 5.2.0 latest release crashes immediately or after a few seconds when trying to paint on canvas.
https://bugs.kde.org/show_bug.cgi?id=476133 Bug ID: 476133 Summary: Galaxy Tab S9 Ultra SM-X910 - Krita 5.2.0 latest release crashes immediately or after a few seconds when trying to paint on canvas. Classification: Applications Product: krita Version: 5.2.0 Platform: Android OS: Android 13.x Status: REPORTED Severity: crash Priority: NOR Component: * Unknown Assignee: krita-bugs-n...@kde.org Reporter: edwardmo...@gmail.com Target Milestone: --- Created attachment 162582 --> https://bugs.kde.org/attachment.cgi?id=162582=edit KritaCrashLog, KritaLogCatDump, KritaSystemInformation & KritaUsageLog SUMMARY *** The latest stable release of krita 5.2 crashes when trying to paint on canvas. This did not start immediately since I was able to test it a few hrs prior without issue. It started after I finished setting up krita the way I would use it. At first I thought a particular setting was the cause, so I cleared data and did a fresh install. Fresh installs with no changes to settings crash as soon as I try to paint. The older version of krita that's on Google Play store works fine without issue. I also tested the latest Nightly build and just like the latest stable build, it crashes as soon as I try to paint. 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. Install on Samsung Tab S9 Ultra 2. Attempt to paint on canvas 3. OBSERVED RESULT Crash EXPECTED RESULT SOFTWARE/OS VERSIONS Android 13 Krita 5.2.0 (Both Stable and Nightly) ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 474207] Provide a scripting API to run arbitrary commands
https://bugs.kde.org/show_bug.cgi?id=474207 Edward Oubrayrie changed: What|Removed |Added CC||edoubray...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[ksmserver] [Bug 455515] kdeinit isn't started in plasma session since plasma 5.25.0
https://bugs.kde.org/show_bug.cgi?id=455515 Edward Oubrayrie changed: What|Removed |Added CC||edoubray...@gmail.com --- Comment #3 from Edward Oubrayrie --- what is the replacement for org.kde.klauncher5 in plasma 6 then? eg: > qdbus org.kde.klauncher5 /KLauncher org.kde.KLauncher.exec_blind ... -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 468703] Search occurs in random editor window instead of active editor window
https://bugs.kde.org/show_bug.cgi?id=468703 Edward Kigwana changed: What|Removed |Added CC||ekigw...@gmail.com --- Comment #5 from Edward Kigwana --- I can confirm this bug as well. -- You are receiving this mail because: You are watching all bug changes.
[kdevplatform] [Bug 377742] Show all KTextEditor view bars in a central location disruptive and annoying on multiple screens
https://bugs.kde.org/show_bug.cgi?id=377742 --- Comment #6 from Edward Kigwana --- Kate has the same trouble but I did not start using kate regularly until I tried 100% KF6 last month. Likely does not have a bug files on it. Things can get tricky anytime one has multiple monitors. I have had 5+ monitors at work since ~2013 so I've just adapted to the curent behavior. I can think of a couple workable options 1 - Search bar per view 2 - One search bar for all views - One thing that would help is if the associated view tab was highlighted Maybe one of these days I'll work it. -- You are receiving this mail because: You are watching all bug changes.
[kio-gdrive] [Bug 467428] Expired or missing access tokens for account
https://bugs.kde.org/show_bug.cgi?id=467428 Edward changed: What|Removed |Added CC||papashre...@gmail.com --- Comment #4 from Edward --- having the same problem here Platform: EndeavourOS plasma version: 5.27.5 KDE Frameworks version: 5.106.0 Graphics platform: X11 -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 467823] New: There is no response on Korganizer when 'Edit' is checked
https://bugs.kde.org/show_bug.cgi?id=467823 Bug ID: 467823 Summary: There is no response on Korganizer when 'Edit' is checked Classification: I don't know Product: kde Version: unspecified Platform: Ubuntu OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: edh...@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. Right click on Entry 2. Left click on 'Edit' 3. OBSERVED RESULT Nothing happens EXPECTED RESULT Edit window SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: 20.3 Cinnamon (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 465712] Periodic black screens on main monitor with 144Hz refresh rate after upgrade to 5.27
https://bugs.kde.org/show_bug.cgi?id=465712 Edward Oubrayrie changed: What|Removed |Added CC||edoubray...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 466373] Qt apps don't use wp-fractional-scale-v1 for hidpi fractional scaling on Wayland
https://bugs.kde.org/show_bug.cgi?id=466373 --- Comment #6 from Edward Oubrayrie --- (I understand upstream won't backport it, this why I'm asking specifically about the KDE Qt patch collection or whatever the name of what goes into Neon) -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 466373] Qt apps don't use wp-fractional-scale-v1 for hidpi fractional scaling on Wayland
https://bugs.kde.org/show_bug.cgi?id=466373 Edward Oubrayrie changed: What|Removed |Added Ever confirmed|0 |1 Resolution|UPSTREAM|--- Status|RESOLVED|REOPENED --- Comment #5 from Edward Oubrayrie --- (In reply to Nicolas Fella from comment #3) So, nothing can be done on this before Plasma 6 ? Am I missing something or is the only thing missing a backport of https://invent.kde.org/qt/qt/qtwayland/-/commit/23d3fc7 into branch `kde/5.15`? If I were to try to submit a PR for this, it would be rejected? -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 466373] Qt apps don't use wp-fractional-scale-v1 for hidpi fractional scaling on Wayland
https://bugs.kde.org/show_bug.cgi?id=466373 --- Comment #4 from Edward Oubrayrie --- Created attachment 156690 --> https://bugs.kde.org/attachment.cgi?id=156690=edit plasma 5.27.1 - artifacts with both XWayland(XCB) and Wayland I had not rebooted after 5.27.1 final so I was probably mostly on Neon testing from 2023-02-17 So, attaching this as the current status. Unfortunately 5.27.1 changes nothing for the platform=wayland scenario -- and it seems to regress the platform=xcb XWayland scenario, making it blurry (not that I care) -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 466373] Qt apps don't use wp-fractional-scale-v1 for hidpi fractional scaling on Wayland
https://bugs.kde.org/show_bug.cgi?id=466373 --- Comment #2 from Edward Oubrayrie --- Created attachment 156689 --> https://bugs.kde.org/attachment.cgi?id=156689=edit image used to find aliasing issues The previous screenshot has been obtained by running code in [6] with dpitest1px.png in the folder and this command: > QT_QPA_PLATFORM=xcb /usr/bin/python3 ./qt6-dpi.py 5 for the left window, and without ...xcb for the right window to better see the difference, beware that most software (Chrome, Firefox, Eye of Gnome) apply antialiasing. Gwenview is fine... without fractional scaling ;-) -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 466373] Qt apps don't use wp-fractional-scale-v1 for hidpi fractional scaling on Wayland
https://bugs.kde.org/show_bug.cgi?id=466373 --- Comment #1 from Edward Oubrayrie --- Created attachment 156688 --> https://bugs.kde.org/attachment.cgi?id=156688=edit Shows clear scaling with XWayland(XCB), artifacts with Wayland -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 466373] New: Qt apps don't use wp-fractional-scale-v1 for hidpi fractional scaling on Wayland
https://bugs.kde.org/show_bug.cgi?id=466373 Bug ID: 466373 Summary: Qt apps don't use wp-fractional-scale-v1 for hidpi fractional scaling on Wayland Classification: KDE Neon Product: neon Version: unspecified Platform: Neon OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Packages Testing Edition Assignee: neon-b...@kde.org Reporter: edoubray...@gmail.com CC: j...@jriddell.org, neon-b...@kde.org, sit...@kde.org Target Milestone: --- SUMMARY Qt client apps using system Qt 5.15.8 still use the old downscaling mechanism to deal with fractional scaling, instead of wp-fractional-scale-v1, leading to visual artefacts. STEPS TO REPRODUCE 1. Set "Scale" to fractional eg 135% in Display Configuration 2. Open a Qt app OBSERVED RESULT App is upscaled to 2x then downscaled. This produces aliasing artifacts as detailed previously here [1] EXPECTED RESULT Native scaling... like what is done by XWayland in "Apply scaling themselves" mode. See attached picture. On the left is XWayland (Platfom=xcb) and on the right Wayland. SOFTWARE/OS VERSIONS KDE Neon based on ubuntu 22.04.2 (available in About System) KDE Plasma Version: 5.27.1 KDE Frameworks Version: 5.104.0 Qt Version: 5.15.8 libqt5core5a Version: 5.15.8+p22.04+tunstable+git20230209.0323-0 python3-pyqt5 Version: 5.15.9+dfsg-1+22.04+jammy+unstable+build21 ADDITIONAL INFORMATION I believe the previous scaling is offered by Qt since 5.6 and is described here [2] and [3]. And the new one was announced by Nate here [4]. I think the KWin part landed: ``` > wayland-info | rg frac interface: 'wp_fractional_scale_manager_v1', version: 1, name: 10 ``` but maybe the Qt patches were not added to Neon's patch collection? Is this [5] related? how can I verify if the Qt5 client libs have support? I attach the small PyQt sample [6] used to show that the scale given to the app is 2x and the screen geometry and physicalDotsPerInch is fake (dpi 115.834 instead of 163), with system Qt 5.15.8. [1]: https://www.reddit.com/r/kde/comments/lficfe/wayland_fractional_scaling_may_be_sort_of_a/ [2]: https://www.qt.io/blog/2015/01/27/qt-weekly-24-high-dpi-qtwayland [3]: https://www.qt.io/blog/2016/01/26/high-dpi-support-in-qt-5-6 [4]: https://pointieststick.com/2022/12/16/this-week-in-kde-wayland-fractional-scaling-oh-and-we-also-fixed-multi-screen/ [5]: https://invent.kde.org/qt/qt/qtwayland/-/commit/23d3fc7 [6]: https://gist.github.com/eddy-geek/2a682a415abb5d351537ae3fc865dffd -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 460404] [Regression]: Kwin 5.26.0 uses software renderer instead of GLX
https://bugs.kde.org/show_bug.cgi?id=460404 Edward Oubrayrie changed: What|Removed |Added CC||edoubray...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 464132] One pixel overlap when enabling screen
https://bugs.kde.org/show_bug.cgi?id=464132 Edward Oubrayrie changed: What|Removed |Added CC||edoubray...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 442901] GTK4 apps have double scaling on hidpi
https://bugs.kde.org/show_bug.cgi?id=442901 Edward Oubrayrie changed: What|Removed |Added CC||edoubray...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 455444] Custom Shortcuts are gone in 5.25 on Wayland
https://bugs.kde.org/show_bug.cgi?id=455444 Edward Oubrayrie changed: What|Removed |Added CC||edoubray...@gmail.com --- Comment #36 from Edward Oubrayrie --- >From what I understand, there's a lot of progress with 5.27 release in configuring global shortcuts, both in Plasma as Nate said, and in apps with the Portal support https://invent.kde.org/plasma/xdg-desktop-portal-kde/-/merge_requests/80 However there's no progress on Keyboard input (macros). As workaround, in addition to what's mentioned in https://wiki.archlinux.org/title/Input_remap_utilities there is also https://github.com/snyball/Hawck, but these tools are much harder to use and can make your system unusable, unlike the basic key input functionality in the old KCM. Even after reading https://blog.martin-graesslin.com/blog/2016/12/how-input-works-keyboard-input/ something is not clear: => Can something be done in Kwin? Is even the compositor not permitted to inject keyboard events in the Wayland architecture? -- You are receiving this mail because: You are watching all bug changes.
[kiofuse] [Bug 446077] VLC player does not stream video from Samba share with kio-fuse
https://bugs.kde.org/show_bug.cgi?id=446077 Edward Oubrayrie changed: What|Removed |Added CC||edoubray...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 438401] [Wayland] 3rd-party window decoration pixelatex/badly rendered when fractional display scaling is used
https://bugs.kde.org/show_bug.cgi?id=438401 Edward Jackson changed: What|Removed |Added CC||ed.andy.jack...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 462869] New: baloo doesn't do a job
https://bugs.kde.org/show_bug.cgi?id=462869 Bug ID: 462869 Summary: baloo doesn't do a job Classification: Plasma Product: krunner Version: 5.26.4 Platform: Other OS: Other Status: REPORTED Severity: normal Priority: NOR Component: filesearch Assignee: baloo-bugs-n...@kde.org Reporter: edward.ni...@gmail.com CC: alexander.loh...@gmx.de, plasma-b...@kde.org Target Milestone: --- SUMMARY Can you improve baloo so that he can index hard drives without idle times that last forever and if you can make it more fast? SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Plasma 5.26.4 KDE Frameworks Version: Qt Version: -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 385722] Uses navigation causes crash
https://bugs.kde.org/show_bug.cgi?id=385722 Edward Kigwana changed: What|Removed |Added Resolution|WAITINGFORINFO |WORKSFORME Status|NEEDSINFO |RESOLVED --- Comment #4 from Edward Kigwana --- Looks like this is also irrelevant with move to clang and gcc parsers -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 385995] Variables display not showing data pointed to by shared_ptr
https://bugs.kde.org/show_bug.cgi?id=385995 Edward Kigwana changed: What|Removed |Added Status|CONFIRMED |RESOLVED Resolution|--- |WORKSFORME --- Comment #2 from Edward Kigwana --- This has long been fixed with changes to the parser -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 456852] GTK menu is at wrong position when using 125% / 200% scaling and screens are not aligned at top edge
https://bugs.kde.org/show_bug.cgi?id=456852 Edward Kigwana changed: What|Removed |Added CC||ekigw...@gmail.com Ever confirmed|0 |1 Status|REPORTED|CONFIRMED --- Comment #4 from Edward Kigwana --- With three displays 1920x1080, 2560x1440, 2560x1440 I have found that the menu offset logic is busted when displays are aligned at the bottom edge. It does not matter what the primary display is. The issue is present for all programs. -- You are receiving this mail because: You are watching all bug changes.
[kdevplatform] [Bug 377742] Show all KTextEditor view bars in a central location disruptive and annoying on multiple screens
https://bugs.kde.org/show_bug.cgi?id=377742 --- Comment #3 from Edward Kigwana --- I am I the only person irritated with the mouse gymnastics? it is worse in wayland where the context menus and popups always got to the next screen over. It still does not make sense especially if one is doing a search and replace, now I have to click into the pane to make sure the displayed search controls are applicable to that pane if my thoughts wander a little :) -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 416221] Dimmed screens not do not get restored when activity resumes
https://bugs.kde.org/show_bug.cgi?id=416221 Edward Kigwana changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |WORKSFORME --- Comment #2 from Edward Kigwana --- This looks like it is likely a kernel driver issue. I seems to work these days -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 391277] Application Global shortcuts broken
https://bugs.kde.org/show_bug.cgi?id=391277 Edward Kigwana changed: What|Removed |Added Version|unspecified |master Resolution|WAITINGFORINFO |WORKSFORME Status|NEEDSINFO |RESOLVED Platform|Other |Gentoo Packages --- Comment #2 from Edward Kigwana --- This bug is no longer relevant. The current mechanisms have worked for me for a long time. -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 460318] Wayland activation bugs
https://bugs.kde.org/show_bug.cgi?id=460318 Edward Oubrayrie changed: What|Removed |Added CC||edoubray...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 460283] New: Kate does not raise in wayland, missing xdg_activation_v1 protocol
https://bugs.kde.org/show_bug.cgi?id=460283 Bug ID: 460283 Summary: Kate does not raise in wayland, missing xdg_activation_v1 protocol Classification: Applications Product: kate Version: 22.08.1 Platform: Neon OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: application Assignee: kwrite-bugs-n...@kde.org Reporter: edoubray...@gmail.com Target Milestone: --- STEPS TO REPRODUCE 0. In a wayland session (tested with Plasma 5.26) 1. Start kate, minimize or hide it 2. Open kate from start menu. A window displays "Session 'x' is already opened in another Kate instance." 3. Click "Switch to instance" Another scenario 0. In a wayland session (tested with Plasma 5.26) 1. Start kate, minimize or hide it 2. Open any kate file eg "foo.txt" from start menu. OBSERVED RESULT Kate window is not visible. EXPECTED RESULT Kate window is raised to forefront. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Neon 22.04 KDE Plasma Version: 5.25.90 KDE Frameworks Version: 5.99.0 Qt Version: 5.15.6 ADDITIONAL INFORMATION Xref https://invent.kde.org/plasma/kwin/-/issues/39 for more examples. protocol https://wayland.app/protocols/xdg-activation-v1 https://invent.kde.org/system/dolphin/-/merge_requests/461 for a similar dolphin fix. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 460268] Opening file manager from Disks & Devices doesn't raise Dolphin window on Wayland
https://bugs.kde.org/show_bug.cgi?id=460268 Edward Oubrayrie changed: What|Removed |Added CC||edoubray...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 459213] Bring to front system settings pages when selecting them from the app menu when system settings is already running minimized
https://bugs.kde.org/show_bug.cgi?id=459213 Edward Oubrayrie changed: What|Removed |Added CC||edoubray...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 442265] Opening an app from konsole has no activation environment set
https://bugs.kde.org/show_bug.cgi?id=442265 Edward Oubrayrie changed: What|Removed |Added CC||edoubray...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 456968] KDE Wallet Manager window is blank
https://bugs.kde.org/show_bug.cgi?id=456968 Edward Oubrayrie changed: What|Removed |Added CC||edoubray...@gmail.com --- Comment #11 from Edward Oubrayrie --- For the KDE Neon testing situation, mentioning Bug 459257 (libkf5auth5 broken) which may be related. -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 459257] New: libkf5auth5 depends on unstable libpolkit-qt5
https://bugs.kde.org/show_bug.cgi?id=459257 Bug ID: 459257 Summary: libkf5auth5 depends on unstable libpolkit-qt5 Classification: Unclassified Product: neon Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Packages Testing Edition Assignee: neon-b...@kde.org Reporter: edoubray...@gmail.com CC: j...@jriddell.org, neon-b...@kde.org, sit...@kde.org Target Milestone: --- SUMMARY Neon 22.04 (I know it's not released yet, feel free to close this if useless) some testing packages depend on unstable ones. can be seen on http://archive.neon.kde.org/testing/dists/jammy/main/binary-amd64/Packages STEPS TO REPRODUCE sudo apt install libkf5auth5 libkf5authcore5 libkf5auth-data OBSERVED RESULT Some packages could not be installed. The following packages have unmet dependencies: libkf5authcore5 : Depends: libpolkit-qt5-1-1 (>= 0.114.0+p22.04+tunstable+git20220908.1608) but 0.114.0+p22.04+tstable+git20220908.1608-0 is to be installed E: Unable to correct problems, you have held broken packages. EXPECTED RESULT installs. SOFTWARE/OS VERSIONS Linux/KDE Plasma: 5.19.0-051900-generic KDE Plasma Version: 5.25.5 KDE Frameworks Version: 5.98.0 Qt Version: 5.15.6 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 417441] Update ~/.xsettingsd file for all changes that affect GTK apps
https://bugs.kde.org/show_bug.cgi?id=417441 Edward Oubrayrie changed: What|Removed |Added CC||edoubray...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 456585] In Thunderbird, "add theme" popup is not clickable on Wayland
https://bugs.kde.org/show_bug.cgi?id=456585 --- Comment #10 from Edward Viesel --- A note in advance: I upgraded five computers to Kubuntu 22.04 and installed the Wayland package and tried to install Thunderbird themes. Result: (all computers have onboard graphics, no dedicated graphics card) - 3 computers installed the themes perfectly. - 1 computer (an old Intel notebook) installed the themes perfectly; however on opening Thunderbird, the main window is too big (i.e. the topmost panel with the „cross“ icon for closing the window is just outside the upper screen margin). If I pull the main window downward and click on the Maximise icon (diamond symbol; „Wiederherstellen“ in German), then the main window resizes correctly, and stays correct. - 1 computer (the Lenovo AMD notebook under discussion here) did not install the theme, as reported above. Now: I created a USB drive with KDE Neon with KDE Plasma 25. I started Neon (in X11 mode) and installed Thunderbird via apt-get. Then I copied a Thunderbird XPI file (theme) to the Neon session. I tried to install the theme (in X11 mode). Installation worked perfectly. No problem. I restarted the session as a Wayland session via an edit in /etc/sddm.conf. (https://zren.github.io/2020/08/09/testing-wayland-in-a-neon-livecd) Then I tried to install the theme as before. However, Thunderbird displayed the same behaviour as described in the first post above. I have noticed the following: The pop-up window with the „Add“ button (at the end of the theme installation process) is vertically aligned with a black jigsaw-piece symbol in the main window’s tabs panel. If theme installation works properly, the black jigsaw-piece symbol and the pop-up window are vertically aligned (and "docked") along the RIGHT-HAND margin of the „Add“ pop-up window. So the pop-up window is always „in“ the main window. With the problem under discussion here, the alignment of black jigsaw-piece symbol and pop-up window is along the LEFT-HAND margin of the „Add“ pop-up window, it is „docked“ in this position. So it is only logical that most of it is „outside“ the main window., if the windows fills the screen completely. This might mean that the cursor is always solely ready for „resizing“ and not for „activating buttons“. I am attaching a screenshot of the final problem situation. You can also see the basic specs of the computer and the KDE Neon session via the Info Center window I had started. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 456585] In Thunderbird, "add theme" popup is not clickable on Wayland
https://bugs.kde.org/show_bug.cgi?id=456585 --- Comment #9 from Edward Viesel --- Created attachment 150919 --> https://bugs.kde.org/attachment.cgi?id=150919=edit Installation attempt with KDE Neon 25 -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 456585] Can't add Thunderbird theme in Wayland session (final pop-up window)
https://bugs.kde.org/show_bug.cgi?id=456585 --- Comment #7 from Edward Viesel --- Thunderbird is installed from Kubuntu repos. Not Flatpak. /home/USERNAME/snap only contains Chromium and Firefox. I can't do screen recording, sorry. I uploaded 5 screenshots. In screenshots 1 and 2 everything is still okay. Screenshot 3 shows the "broken state". The pop-up window with the green jigsaw piece is in the right margin of the screen and can't be moved. Screenshot 4 shows what I did: clicked on the diamond symbol "Wiederherstellen" (in German). The main Thunderbird window is resized, the pop-up window with the green jigsaw piece follows along to the left; it stays in the same place relative to the main window, however. What you don't see in screenshot 5: the cursor turns into a blue dot with an arrow head left and right within the pop-up window. You can't click on either "Cancel" or "Add". -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 456585] Can't add Thunderbird theme in Wayland session (final pop-up window)
https://bugs.kde.org/show_bug.cgi?id=456585 --- Comment #6 from Edward Viesel --- Created attachment 150810 --> https://bugs.kde.org/attachment.cgi?id=150810=edit Screenshot no. 5 -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 456585] Can't add Thunderbird theme in Wayland session (final pop-up window)
https://bugs.kde.org/show_bug.cgi?id=456585 --- Comment #5 from Edward Viesel --- Created attachment 150809 --> https://bugs.kde.org/attachment.cgi?id=150809=edit Screenshot no. 4 -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 456585] Can't add Thunderbird theme in Wayland session (final pop-up window)
https://bugs.kde.org/show_bug.cgi?id=456585 --- Comment #4 from Edward Viesel --- Created attachment 150808 --> https://bugs.kde.org/attachment.cgi?id=150808=edit Screenshot no. 3 -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 456585] Can't add Thunderbird theme in Wayland session (final pop-up window)
https://bugs.kde.org/show_bug.cgi?id=456585 --- Comment #3 from Edward Viesel --- Created attachment 150807 --> https://bugs.kde.org/attachment.cgi?id=150807=edit Screenshot no. 2 -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 456585] Can't add Thunderbird theme in Wayland session (final pop-up window)
https://bugs.kde.org/show_bug.cgi?id=456585 --- Comment #2 from Edward Viesel --- Created attachment 150806 --> https://bugs.kde.org/attachment.cgi?id=150806=edit Screenshot no. 1 -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 456585] New: Can't add Thunderbird theme in Wayland session (final pop-up window)
https://bugs.kde.org/show_bug.cgi?id=456585 Bug ID: 456585 Summary: Can't add Thunderbird theme in Wayland session (final pop-up window) Product: kde Version: unspecified Platform: Ubuntu Packages OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: edward.vie...@bornepost.eu 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. Log in with a Wayland session in Kubuntu 22.04 2. Open Thunderbird 91.9.1 3. Go to Extras > Add-ons and Themes > Themes > [Symbol of cogwheel] > Install add-on from file (I hope this is the English equivalent to the German I'm using). 4. Choose a theme's XPI file from your file manager and get ready to add the theme with the pop-up window "add". OBSERVED RESULT The pop-up window is partially outside the right margin of the laptop screen. You can just see the left 10 per cent or so. By making the main Thunderbird window smaller and pulling the pop-up to the left, you can gain access to the whole pop-up window. But you can't click on the button "Add", because the cursor turns into a horizontal two-pointed arrow. Any attempt to click on anything (e.g."Cancel") in the pop-up window does not work. Pressing the ENTER key on the keyboard does not work either. There is no way of getting the Thunderbird theme installed with this pop-up window. EXPECTED RESULT You should be able to 1) see the pop-up window in its entirety straight away; 2) be able to click on the button "add"; and 3) press the ENTER or ESC key; then the Thunderbird theme should be installed from a file on the computer's drive, or installation should be cancelled. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Kubuntu 22.04 (available in About System) KDE Plasma Version: 5.24.4 KDE Frameworks Version: 5.92.0 Qt Version: 5.15.3 ADDITIONAL INFORMATION Workaround: Log out from Wayland session and log back on with X11 session. Then install the theme. The pop-up windows is in its normal position, and you can click on "Add", thereby adding the theme. -- You are receiving this mail because: You are watching all bug changes.
[Elisa] [Bug 451630] New: feature request
https://bugs.kde.org/show_bug.cgi?id=451630 Bug ID: 451630 Summary: feature request Product: Elisa Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: general Assignee: matthieu_gall...@yahoo.fr Reporter: papashre...@gmail.com Target Milestone: --- feature request: allow Elisa to minimize to systray and keep playing music similar to rythymbox or clementine. rather than just minimizing window of app, but be able to close main window and keep music playing. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 450316] Unable to Copy File Into the Same Directory using Projects Viewer
https://bugs.kde.org/show_bug.cgi?id=450316 --- Comment #2 from Edward Kigwana --- I was unaware of the that bug. This is a duplicate. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 450316] New: Unable to Copy File Into the Same Directory using Projects Viewer
https://bugs.kde.org/show_bug.cgi?id=450316 Bug ID: 450316 Summary: Unable to Copy File Into the Same Directory using Projects Viewer Product: kdevelop Version: git master Platform: Gentoo Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: UI: general Assignee: kdevelop-bugs-n...@kde.org Reporter: ekigw...@gmail.com Target Milestone: --- Copying a file into the same directory causes the "File Already Exists" dialog to popup and provide the user and opportunity to rename the file. Before a user can get around to renaming the file, a modal Kdevelop "Copying" dialog pops up and blocks input to the file rename dialog. This last pop up is a copy progress indicator with a pause and a stop button. STEPS TO REPRODUCE 1. Open a project 2. Using the Projects UI viewer right click a file and choose copy in context menu 3. Using the Projects UI viewer right click directory containing file in previous step and select paste OBSERVED RESULT - Rename dialog pops up but user cannot interact with it. - Kdevelop copying notification block forever until it is stopped. EXPECTED RESULT - Rename dialog modal to Copying progress dialog which is turn modal to Kdevelop main window - Ability to rename file -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 447965] [Usability] "Keep display configuration" is almost invisible
https://bugs.kde.org/show_bug.cgi?id=447965 Edward Oubrayrie changed: What|Removed |Added Attachment #145124|0 |1 is obsolete|| Ever confirmed|0 |1 Assignee|kscreen-bugs-n...@kde.org |edoubray...@gmail.com Status|RESOLVED|REOPENED Resolution|FIXED |--- --- Comment #2 from Edward Oubrayrie --- Created attachment 145616 --> https://bugs.kde.org/attachment.cgi?id=145616=edit Auto-revert window plasma 5.23.90 > Fixed in Plasma 5.24 already by darkening the background behind the dialog. That's great news but I don't see anything like on latest testing packages, is it Wayland-only? Can you point to relevant MR or version? (It's unclear with Neon's package versioning but "About" says I'm on the 5.24 beta...) Operating System: KDE neon Testing Edition KDE Plasma Version: 5.23.90 KDE Frameworks Version: 5.91.0 Qt Version: 5.15.3 Kernel Version: 5.8.0-59-generic (64-bit) Graphics Platform: X11 kscreen4:5.23.5+p20.04+tstable+git20220113.1818-0 amd64 -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 447965] [Usability] "Keep display configuration" is almost invisible
https://bugs.kde.org/show_bug.cgi?id=447965 Edward Oubrayrie changed: What|Removed |Added CC||edoubray...@gmail.com Version|5.23.5 |5.23.1 Platform|Other |Neon Packages -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 447965] New: [Usability] "Keep display configuration" is almost invisible
https://bugs.kde.org/show_bug.cgi?id=447965 Bug ID: 447965 Summary: [Usability] "Keep display configuration" is almost invisible Product: KScreen Version: 5.23.5 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Plasma Applet Assignee: kscreen-bugs-n...@kde.org Reporter: edoubray...@gmail.com Target Milestone: --- Created attachment 145124 --> https://bugs.kde.org/attachment.cgi?id=145124=edit Auto-revert window SUMMARY the new (~Plasma 5.23) "Keep display configuration" auto-revert window is a usability nightmare for me. I forget to click it about 95% of the time. It's certainly my fault but: * It has incredibly low visibility (especially with the dark theme): very small, 0 contrast with the background "Display Configuration" window * It is on only one screen (so, since it will move around during apply (which is the point) it's usually not in front of my eyes anymore. * It does not stay on top (maybe related to Wayland limited capabilities on that front, but I'm on X11), and does not prevent me from working happily... during 1 minute of course. STEPS TO REPRODUCE 1. Open display settings 2. Chamge 3. Apply OBSERVED RESULT Auto-revert windows is easy to miss and easy to ignore. EXPECTED RESULT Auto-revert windows is *impossible* to miss and *hard* to ignore. SOFTWARE/OS VERSIONS Linux/KDE Plasma: KDE neon 20.04 KDE Plasma Version: 4:5.23.1+p20.04+tstable+git20211023.0054-0 KDE Frameworks Version: 5.87.0+p20.04+tunstable+git20211010.0149-0 Qt Version: 5.15.2+p20.04+tunstable+git20211024.0137-0 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 438508] wayland, iGPU multi-monitor: right click menu displaced to edge of monitor
https://bugs.kde.org/show_bug.cgi?id=438508 --- Comment #10 from Edward Kigwana --- Forgot to mention that I am running git master as of 2021-11-03 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 438508] wayland, iGPU multi-monitor: right click menu displaced to edge of monitor
https://bugs.kde.org/show_bug.cgi?id=438508 --- Comment #9 from Edward Kigwana --- iIn Wayland, it seems that the problem area is the menu placement logic in a multi-screen environment and the results make it unusable. I have captured several screen shots to illustrate the issue. Note that context menus are also affected. I first noticed the issue when using Kdevelop stretched across two screens with a split view. It appears that menu logic goes out of the way to ensure that a menu is not drawn across two screens but is too aggressive on when deciding to relocate a menu to screen on the right. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 438508] wayland, iGPU multi-monitor: right click menu displaced to edge of monitor
https://bugs.kde.org/show_bug.cgi?id=438508 --- Comment #8 from Edward Kigwana --- Created attachment 143496 --> https://bugs.kde.org/attachment.cgi?id=143496=edit Screen shot -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 438508] wayland, iGPU multi-monitor: right click menu displaced to edge of monitor
https://bugs.kde.org/show_bug.cgi?id=438508 --- Comment #7 from Edward Kigwana --- Created attachment 143495 --> https://bugs.kde.org/attachment.cgi?id=143495=edit Screen shot -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 438508] wayland, iGPU multi-monitor: right click menu displaced to edge of monitor
https://bugs.kde.org/show_bug.cgi?id=438508 --- Comment #6 from Edward Kigwana --- Created attachment 143494 --> https://bugs.kde.org/attachment.cgi?id=143494=edit Screen shot -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 438508] wayland, iGPU multi-monitor: right click menu displaced to edge of monitor
https://bugs.kde.org/show_bug.cgi?id=438508 --- Comment #5 from Edward Kigwana --- Created attachment 143493 --> https://bugs.kde.org/attachment.cgi?id=143493=edit Screen shot -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 438508] wayland, iGPU multi-monitor: right click menu displaced to edge of monitor
https://bugs.kde.org/show_bug.cgi?id=438508 --- Comment #4 from Edward Kigwana --- Created attachment 143492 --> https://bugs.kde.org/attachment.cgi?id=143492=edit Screens shot -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 438508] wayland, iGPU multi-monitor: right click menu displaced to edge of monitor
https://bugs.kde.org/show_bug.cgi?id=438508 --- Comment #3 from Edward Kigwana --- Created attachment 143491 --> https://bugs.kde.org/attachment.cgi?id=143491=edit Screens shot -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 438508] wayland, iGPU multi-monitor: right click menu displaced to edge of monitor
https://bugs.kde.org/show_bug.cgi?id=438508 --- Comment #2 from Edward Kigwana --- Created attachment 143489 --> https://bugs.kde.org/attachment.cgi?id=143489=edit Screens shot -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 438508] wayland, iGPU multi-monitor: right click menu displaced to edge of monitor
https://bugs.kde.org/show_bug.cgi?id=438508 Edward Kigwana changed: What|Removed |Added CC||ekigw...@gmail.com --- Comment #1 from Edward Kigwana --- Created attachment 143487 --> https://bugs.kde.org/attachment.cgi?id=143487=edit Screens shot -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 444991] New: Can not connect to Zorin Connect
https://bugs.kde.org/show_bug.cgi?id=444991 Bug ID: 444991 Summary: Can not connect to Zorin Connect Product: kdeconnect Version: unspecified Platform: Other OS: iOS Status: REPORTED Severity: normal Priority: NOR Component: ios-application Assignee: lucas.w...@tuta.io Reporter: edward.bren...@yahoo.com Target Milestone: --- SUMMARY Device is not discoverable when using Zorin Connect STEPS TO REPRODUCE 1. Tried refresh 2. Tried swipe down refresh 3. Tried enter IP on both the phone and on the desktop OBSERVED RESULT Device was not discovered EXPECTED RESULT Device to be discovered SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: Zorin 16 iOS 15.0.2 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 444989] New: Crashes when refreshing
https://bugs.kde.org/show_bug.cgi?id=444989 Bug ID: 444989 Summary: Crashes when refreshing Product: kdeconnect Version: unspecified Platform: Other OS: iOS Status: REPORTED Severity: normal Priority: NOR Component: ios-application Assignee: lucas.w...@tuta.io Reporter: edward.bren...@yahoo.com Target Milestone: --- SUMMARY Crashes after multiple refreshes. STEPS TO REPRODUCE 1. Swip down to refresh 2. Repeat multiple times 3. OBSERVED RESULT App crashes EXPECTED RESULT Not to crash SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: iOS 15.0.2 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 444671] icon-only taskmanager fails to load due to tooltip delegate unavailable
https://bugs.kde.org/show_bug.cgi?id=444671 --- Comment #5 from Edward Kigwana --- (In reply to Nate Graham from comment #1) > I assume you're compiling from source or using git master packages? I am as > well, and I don't see this. Can you update the system or recompile and try > again? I did with the same results. I think I am missing pipewire runtime dependency or something -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 444671] New: icon-only taskmanager fails to load due to tooltip delegate unavailable
https://bugs.kde.org/show_bug.cgi?id=444671 Bug ID: 444671 Summary: icon-only taskmanager fails to load due to tooltip delegate unavailable Product: plasmashell Version: master Platform: Gentoo Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Task Manager and Icons-Only Task Manager Assignee: h...@kde.org Reporter: ekigw...@gmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 SUMMARY no-icons-only task manager and not switcher either STEPS TO REPRODUCE 1. Start plasma on x11 OBSERVED RESULT Small block on task bar indicating failure to load with message copy cause file:///usr/share/plasma/plasmoids/org.kde.plasma.taskmanager/contents/ui/main.qml:400:5: Type ToolTipDelegate unavailable file:///usr/share/plasma/plasmoids/org.kde.plasma.taskmanager/contents/ui/ToolTipDelegate.qml:80:9: Type ToolTipInstance unavailable file:///usr/share/plasma/plasmoids/org.kde.plasma.taskmanager/contents/ui/ToolTipInstance.qml:184:17: TaskManager.PipeWireSourceItem is not a type If I comment out just the pipewire section from plasma-desktop/applets/taskmanager/package/contents/ui/ToolTipInstance.qml on X11 I get an Icons-only task manager again The change that caused the breakage for me was https://invent.kde.org/plasma/plasma-desktop/-/commit/238a076c8d9d80f874f3cbef7ba857db7efda7ac 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.
[kwin] [Bug 443049] Screen sharing broken on Firefox
https://bugs.kde.org/show_bug.cgi?id=443049 Edward Oubrayrie changed: What|Removed |Added CC||edoubray...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 443000] New: system setting crash after changing screen edge setting when closing after applying. Settings not saved Wayland
https://bugs.kde.org/show_bug.cgi?id=443000 Bug ID: 443000 Summary: system setting crash after changing screen edge setting when closing after applying. Settings not saved Wayland Product: systemsettings Version: 5.22.4 Platform: Fedora RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: papashre...@gmail.com Target Milestone: --- Application: systemsettings5 (5.22.4) Qt Version: 5.15.2 Frameworks Version: 5.85.0 Operating System: Linux 5.14.7-200.fc34.x86_64 x86_64 Windowing System: Wayland Drkonqi Version: 5.22.4 Distribution: "Fedora release 34 (Thirty Four)" -- Information about the crash: - What I was doing when the application crashed: I was setting up a screen edge control in system settings, Hit apply to save the changes, and when I close the window for system settings it crashes and resets to default settings. tried a second time with exact same results. The crash can be reproduced every time. -- Backtrace: Application: System Settings (systemsettings5), signal: Segmentation fault [KCrash Handler] #4 0x55ac7bdd6c70 in ?? () #5 0x7fcc547d3e47 in QWaylandClientExtensionPrivate::handleRegistryGlobal(void*, wl_registry*, unsigned int, QString const&, unsigned int) () from /lib64/libQt5WaylandClient.so.5 #6 0x7fcc547c0419 in QtWaylandClient::QWaylandDisplay::registry_global(unsigned int, QString const&, unsigned int) () from /lib64/libQt5WaylandClient.so.5 #7 0x7fcc547dc6c3 in QtWayland::wl_registry::handle_global(void*, wl_registry*, unsigned int, char const*, unsigned int) () from /lib64/libQt5WaylandClient.so.5 #8 0x7fcc5208bc04 in ffi_call_unix64 () from /lib64/libffi.so.6 #9 0x7fcc5208b107 in ffi_call () from /lib64/libffi.so.6 #10 0x7fcc5472dd10 in wl_closure_invoke.constprop () from /lib64/libwayland-client.so.0 #11 0x7fcc5472e42b in dispatch_event.isra () from /lib64/libwayland-client.so.0 #12 0x7fcc5472e61c in wl_display_dispatch_queue_pending () from /lib64/libwayland-client.so.0 #13 0x7fcc547b861f in QtWaylandClient::QWaylandDisplay::flushRequests() () from /lib64/libQt5WaylandClient.so.5 #14 0x7fcc56dcd3f0 in void doActivate(QObject*, int, void**) () from /lib64/libQt5Core.so.5 #15 0x7fcc56deac0b in QEventDispatcherGlib::processEvents(QFlags) () from /lib64/libQt5Core.so.5 #16 0x7fcc56d981a2 in QEventLoop::exec(QFlags) () from /lib64/libQt5Core.so.5 #17 0x7fcc56da06e4 in QCoreApplication::exec() () from /lib64/libQt5Core.so.5 #18 0x55ac7914858c in main () [Inferior 1 (process 93) detached] Possible duplicates by query: bug 442318, bug 442289, bug 441707, bug 441700, bug 441504. Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 442870] New: Bookmark Commands
https://bugs.kde.org/show_bug.cgi?id=442870 Bug ID: 442870 Summary: Bookmark Commands Product: konsole Version: 21.08.1 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: bookmark Assignee: konsole-de...@kde.org Reporter: edward.ni...@gmail.com Target Milestone: --- SUMMARY Can you please make a feature that we can bookmark a commands and give them a alias? 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.
[krita] [Bug 441761] New: Dockers can not be attached when onion skin docker is enabled as part of the animation timeline docker.
https://bugs.kde.org/show_bug.cgi?id=441761 Bug ID: 441761 Summary: Dockers can not be attached when onion skin docker is enabled as part of the animation timeline docker. Product: krita Version: 5.0.0-beta1 Platform: Android OS: Android 11.x Status: REPORTED Severity: normal Priority: NOR Component: Dockers Assignee: krita-bugs-n...@kde.org Reporter: edwardmo...@gmail.com Target Milestone: --- Created attachment 141153 --> https://bugs.kde.org/attachment.cgi?id=141153=edit Screen recording of the issue described. SUMMARY When the onion skin docker is enabled by clicking the onion skin icon on the animation timeline docker, other dockers including the toolbars can not be attached. If the onion skin docker is pulled from the animation timeline docker, other dockers can be attached. If the onion skin docker is attached to the animation timeline docker the same way other dockers would, other dockers can be attached. Onion skin docker can not be reattached back in to its original position without reloading the workspace. STEPS TO REPRODUCE 1. Enable Onion skin by clicking the onion skin icon on the animation timeline. 2. Attempt to attach any docker to another docker. It won't attach 3. Pull the onion skin docker from the animation timeline. 4. Other dockers can now be attached. 5. Attach the onion skin docker to the animation timeline the way another docker would be attached - other dockers can be attached. Onion skin docker can not be attached back to its original position as it was when the icon was used to enable it. OBSERVED RESULT When onion skin docker is enabled as part of the animation timeline, other dockers can not be attached. EXPECTED RESULT Other dockers should be able to be attached while onion skin is enabled. SOFTWARE/OS VERSIONS Android: 11 Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION Attached a screen recording demonstrating the issue. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 441303] Icons / Controls On Animation Timeline Docker Vanishing After Switching Workspace
https://bugs.kde.org/show_bug.cgi?id=441303 --- Comment #12 from Edward Mowah --- On Mon, 30 Aug 2021, 10:14 Edward, wrote: > In addition, I don't know if this is all part of the same issue, but when > onion skin docker is part of the Animation Timeline Docker, other dockers > can not be attached. > > I'll attach a screen recording. > > > On Mon, 30 Aug 2021, 10:01 Edward, wrote: > >> Hello, >> >> I downloaded a fresh copy of Krita, before installing it, I backed up all >> the files in org.krita/files, the newer installation didn't seem to have >> the same issue, so I started replacing some new files with the old ones I >> backed up and found that the file causing the problem was: "kritarc". I >> switched between the old file and new one several times just to make sure. >> >> I'll attach the old and new kritarc file, and the old and new log files >> you might be able to reproduce the problem. >> >> >> >> >> On Mon, 30 Aug 2021, 08:52 sh_zam, wrote: >> >>> https://bugs.kde.org/show_bug.cgi?id=441303 >>> >>> sh_zam changed: >>> >>>What|Removed |Added >>> >>> -------- >>> Status|REPORTED|ASSIGNED >>> Ever confirmed|0 |1 >>> >>> --- Comment #6 from sh_zam --- >>> (In reply to Edward Mowah from comment #3) >>> > Created attachment 141084 [details] >>> > VideoCapture_20210827-121948.jpg >>> > >>> > This is what I got: >>> > >>> > "WARNING: The Krita usage log file doesn't exist.File name and >>> location: >>> > >>> /storage/emulated/0/Android/data/org.krita/files/krita.log--- >>> > - >>> > >>> >>> This seems like a really odd problem! We did change the location from >>> internal >>> storage to external storage on Android. Can you verify by using the File >>> Manager whether the file exists at this location or not? >>> >>> -- >>> You are receiving this mail because: >>> You reported the bug. >> >> -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 441303] Icons / Controls On Animation Timeline Docker Vanishing After Switching Workspace
https://bugs.kde.org/show_bug.cgi?id=441303 --- Comment #11 from Edward Mowah --- In addition, I don't know if this is all part of the same issue, but when onion skin docker is part of the Animation Timeline Docker, other dockers can not be attached. I'll attach a screen recording. On Mon, 30 Aug 2021, 10:01 Edward, wrote: > Hello, > > I downloaded a fresh copy of Krita, before installing it, I backed up all > the files in org.krita/files, the newer installation didn't seem to have > the same issue, so I started replacing some new files with the old ones I > backed up and found that the file causing the problem was: "kritarc". I > switched between the old file and new one several times just to make sure. > > I'll attach the old and new kritarc file, and the old and new log files > you might be able to reproduce the problem. > > > > > On Mon, 30 Aug 2021, 08:52 sh_zam, wrote: > >> https://bugs.kde.org/show_bug.cgi?id=441303 >> >> sh_zam changed: >> >>What|Removed |Added >> >> >> Status|REPORTED|ASSIGNED >> Ever confirmed|0 |1 >> >> --- Comment #6 from sh_zam --- >> (In reply to Edward Mowah from comment #3) >> > Created attachment 141084 [details] >> > VideoCapture_20210827-121948.jpg >> > >> > This is what I got: >> > >> > "WARNING: The Krita usage log file doesn't exist.File name and location: >> > >> /storage/emulated/0/Android/data/org.krita/files/krita.log--- >> > - >> > >> >> This seems like a really odd problem! We did change the location from >> internal >> storage to external storage on Android. Can you verify by using the File >> Manager whether the file exists at this location or not? >> >> -- >> You are receiving this mail because: >> You reported the bug. > > -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 441303] Icons / Controls On Animation Timeline Docker Vanishing After Switching Workspace
https://bugs.kde.org/show_bug.cgi?id=441303 --- Comment #7 from Edward Mowah --- Hello, I downloaded a fresh copy of Krita, before installing it, I backed up all the files in org.krita/files, the newer installation didn't seem to have the same issue, so I started replacing some new files with the old ones I backed up and found that the file causing the problem was: "kritarc". I switched between the old file and new one several times just to make sure. I'll attach the old and new kritarc file, and the old and new log files you might be able to reproduce the problem. On Mon, 30 Aug 2021, 08:52 sh_zam, wrote: > https://bugs.kde.org/show_bug.cgi?id=441303 > > sh_zam changed: > >What|Removed |Added > > > Status|REPORTED|ASSIGNED > Ever confirmed|0 |1 > > --- Comment #6 from sh_zam --- > (In reply to Edward Mowah from comment #3) > > Created attachment 141084 [details] > > VideoCapture_20210827-121948.jpg > > > > This is what I got: > > > > "WARNING: The Krita usage log file doesn't exist.File name and location: > > > /storage/emulated/0/Android/data/org.krita/files/krita.log--- > > - > > > > This seems like a really odd problem! We did change the location from > internal > storage to external storage on Android. Can you verify by using the File > Manager whether the file exists at this location or not? > > -- > You are receiving this mail because: > You reported the bug. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 441303] Icons / Controls On Animation Timeline Docker Vanishing After Switching Workspace
https://bugs.kde.org/show_bug.cgi?id=441303 --- Comment #3 from Edward Mowah --- This is what I got: "WARNING: The Krita usage log file doesn't exist.File name and location: /storage/emulated/0/Android/data/org.krita/files/krita.log Krita Version: 5.0.0-beta1 Qt Version (compiled): 5.12.11 Version (loaded): 5.12.11 OS Information Build ABI: arm64-little_endian-lp64 Build CPU: arm64 CPU: arm64 Kernel Type: linux Kernel Version: 4.14.190-21627332-abT865XXS4CUG1 Pretty Productname: Android (11.0) Product Type: android Product Version: 11.0 OpenGL Info Vendor: "Qualcomm" Renderer: "Adreno (TM) 640" Version: "OpenGL ES 3.2 V@0502.0 (GIT@afcc001, I30979edc94, 1615994807) (Date:03/17/21)" Shading language: "OpenGL ES GLSL ES 3.20" Requested format: QSurfaceFormat(version 2.0, options QFlags(), depthBufferSize 24, redBufferSize 8, greenBufferSize 8, blueBufferSize 8, alphaBufferSize 8, stencilBufferSize 8, samples -1, swapBehavior QSurfaceFormat::DoubleBuffer, swapInterval 0, colorSpace QSurfaceFormat::DefaultColorSpace, profile QSurfaceFormat::NoProfile) Current format: QSurfaceFormat(version 3.2, 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.2 Supports deprecated functions false is OpenGL ES: true QPA OpenGL Detection Info supportsDesktopGL: false supportsOpenGLES: true isQtPreferOpenGLES: true Hardware Information Memory: 7 Gb Cores: 8 Swap: /data/data/org.krita/files" Update: This also happens to the titles and exit buttons on other dockers. On Fri, 27 Aug 2021, 10:24 sh_zam, wrote: > https://bugs.kde.org/show_bug.cgi?id=441303 > > sh_zam changed: > >What|Removed |Added > > > Resolution|--- |WAITINGFORINFO > Status|ASSIGNED|NEEDSINFO > > --- Comment #2 from sh_zam --- > Hello Edward! > > I'm afraid I can't reproduce this on my Android device, even on a freshly > installed beta version. Could you attach the log from Settings -> Help -> > Show > Krita log for bug reports > > -- > You are receiving this mail because: > You reported the bug. -- You are receiving this mail because: You are watching all bug changes.
[step] [Bug 441387] New: step crashed while i opened a example
https://bugs.kde.org/show_bug.cgi?id=441387 Bug ID: 441387 Summary: step crashed while i opened a example Product: step Version: 21.08.0 Platform: Neon Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: ks.vladi...@gmail.com Reporter: eddisch2...@gmail.com Target Milestone: --- Application: step (21.08.0) Qt Version: 5.15.3 Frameworks Version: 5.85.0 Operating System: Linux 5.11.0-27-generic x86_64 Windowing System: X11 Drkonqi Version: 5.22.4 Distribution: KDE neon User Edition 5.22 -- Information about the crash: - What I was doing when the application crashed: opened a example file (tutorial1) and scrolled a bit. Then dr konqi said it crashed The reporter is unsure if this crash is reproducible. -- Backtrace: Application: Step (step), signal: Segmentation fault [New LWP 12096] [New LWP 12098] [New LWP 12105] [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". 0x7f86d88b1aff in __GI___poll (fds=0x7ffd57f24db8, nfds=1, timeout=1000) at ../sysdeps/unix/sysv/linux/poll.c:29 [Current thread is 1 (Thread 0x7f86d3369540 (LWP 12093))] Thread 4 (Thread 0x7f86be54b700 (LWP 12105)): #0 0x7f86d88b1aff in __GI___poll (fds=0x7f86a4007170, nfds=3, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7f86c822b1d6 in ?? () from /lib/x86_64-linux-gnu/libpulse.so.0 #2 0x7f86c821c841 in pa_mainloop_poll () from /lib/x86_64-linux-gnu/libpulse.so.0 #3 0x7f86c821cec3 in pa_mainloop_iterate () from /lib/x86_64-linux-gnu/libpulse.so.0 #4 0x7f86c821cf70 in pa_mainloop_run () from /lib/x86_64-linux-gnu/libpulse.so.0 #5 0x7f86c822b11d in ?? () from /lib/x86_64-linux-gnu/libpulse.so.0 #6 0x7f86c81c772c in ?? () from /usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-13.99.so #7 0x7f86d773e609 in start_thread (arg=) at pthread_create.c:477 #8 0x7f86d88be293 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 3 (Thread 0x7f86cbb8f700 (LWP 12098)): #0 futex_wait_cancelable (private=, expected=0, futex_word=0x55d267624ba4) at ../sysdeps/nptl/futex-internal.h:183 #1 __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x55d267624b50, cond=0x55d267624b78) at pthread_cond_wait.c:508 #2 __pthread_cond_wait (cond=0x55d267624b78, mutex=0x55d267624b50) at pthread_cond_wait.c:638 #3 0x7f86d8daff2b in QWaitCondition::wait(QMutex*, QDeadlineTimer) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x55d266f16697 in SimulationThread::run (this=0x55d267458fb0) at /usr/include/x86_64-linux-gnu/qt5/QtCore/qdeadlinetimer.h:68 #5 0x7f86d8da9dbc in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7f86d773e609 in start_thread (arg=) at pthread_create.c:477 #7 0x7f86d88be293 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 2 (Thread 0x7f86d1763700 (LWP 12096)): #0 0x7f86d88b1aff in __GI___poll (fds=0x7f86c401ad20, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7f86d66b536e in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f86d66b54a3 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f86d8feafcb in QEventDispatcherGlib::processEvents(QFlags) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7f86d8f8f25b in QEventLoop::exec(QFlags) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f86d8da8c22 in QThread::exec() () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7f86d729af4b in ?? () from /lib/x86_64-linux-gnu/libQt5DBus.so.5 #7 0x7f86d8da9dbc in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7f86d773e609 in start_thread (arg=) at pthread_create.c:477 #9 0x7f86d88be293 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 1 (Thread 0x7f86d3369540 (LWP 12093)): [KCrash Handler] #4 0x55d266eef739 in PolygonCreator::sceneEvent (this=0x55d26793ea00, event=0x7ffd57f25d70) at ./step/polygongraphics.cc:474 #5 0x55d266ed1c34 in WorldScene::event (this=0x55d267890b90, event=0x7ffd57f25d70) at ./step/worldscene.cc:215 #6 0x7f86d9a6adc3 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #7 0x7f86d9a73bb8 in QApplication::notify(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #8 0x7f86d8f9075a in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #9 0x7f86d9dce902 in QGraphicsViewPrivate::mouseMoveEventHandler(QMouseEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #10 0x7f86d9aadcf6 in QWidget::event(QEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #11 0x7f86d9b5e092 in QFrame::event(QEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #12 0x7f86d9dd1411
[krita] [Bug 441303] New: Icons / Controls On Animation Timeline Docker Vanishing After Switching Workspace
https://bugs.kde.org/show_bug.cgi?id=441303 Bug ID: 441303 Summary: Icons / Controls On Animation Timeline Docker Vanishing After Switching Workspace Product: krita Version: 5.0.0-beta1 Platform: Android OS: Android 11.x Status: REPORTED Severity: normal Priority: NOR Component: Dockers Assignee: krita-bugs-n...@kde.org Reporter: edwardmo...@gmail.com Target Milestone: --- Created attachment 140916 --> https://bugs.kde.org/attachment.cgi?id=140916=edit Screen recording showing Animation Timeline Docker Icons / Controls Vanishing when interacting with Workspaces. SUMMARY Hello, Whenever I switch to a different Workspace from Animation Workspace and back, or even just clicking again on the Animation Workspace while still in the Animation Workspace, I noticed that the Icons/controls disappear. They will not reappear until krita is restarted. STEPS TO REPRODUCE 1. Switch to a different Workspace from Animation Workspace, then switch back to Animation Workspace (Or any Workspace with the Animation Timeline docker) 2. Without switching to a different Workspace, just reclick the Animation Workspace or any Workspace that has the Animation Timeline docker active. 3. Restart Krita while in the same Workspace that has the Animation Timeline Docker active for the icons/controls to reappear. OBSERVED RESULT Icons / controls on the Animation Timeline Docker will disappear after switching to and from another Workspace. Icons / controls on the Animation Timeline Docker will disappear after reclicking whichever currently active Workspace has the Animation Timeline docker. Icons and controls will only reappear after restarting krita. (Not permanent since doing what's written above will repeat the same issue) EXPECTED RESULT To be able to activate any Workspace without causing the icons / controls to vanish from the Animation Timeline Docker. SOFTWARE/OS VERSIONS Android : 11 Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION Attached is a video showing the issue. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 441166] New: (ANDROID) Donation banner image is stretching the "New file" & "Open file" buttons on the start page.
https://bugs.kde.org/show_bug.cgi?id=441166 Bug ID: 441166 Summary: (ANDROID) Donation banner image is stretching the "New file" & "Open file" buttons on the start page. Product: krita Version: 5.0.0-beta1 Platform: Android OS: Android 11.x Status: REPORTED Severity: normal Priority: NOR Component: General Assignee: krita-bugs-n...@kde.org Reporter: edwardmo...@gmail.com Target Milestone: --- Created attachment 140837 --> https://bugs.kde.org/attachment.cgi?id=140837=edit Screenshot showing krita with and without banner active SUMMARY At first I wasn't sure what was causing it, so I installed on a different device account that used a different google account for Google Play than my main account used to make the donation. Only the account without the donation banner was fine. Current temporary solution was hiding the banner image by either deleting it or renaming the extention to ".old" so it isn't recognised by krita. Found the image in data folder where some krita files are stored. STEPS TO REPRODUCE 1. Fresh installation of Krita 2. Tried on a different account on device 3. Tried at different screen zooms and font sizes 4. Disabled News OBSERVED RESULT The only working solution was to disable the banner. (Did so by renaming the image file extention in data folder so that it is not recognisable) Had to install a 3rd party file manager to find it since the default file manager can not access this folder since Android 11. EXPECTED RESULT To be able to keep banner active without it stretching the SOFTWARE/OS VERSIONS Android: 11 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.
[kdeconnect] [Bug 440114] New: Mouse pointer too slow
https://bugs.kde.org/show_bug.cgi?id=440114 Bug ID: 440114 Summary: Mouse pointer too slow Product: kdeconnect Version: unspecified Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: android-application Assignee: albertv...@gmail.com Reporter: edward.ni...@gmail.com Target Milestone: --- SUMMARY On kde connect when i want to navigate my android with a mouse i can't move my mouse across the entire screen in one move and why i have to hold left mouse button pressed in order to move the mouse on android? STEPS TO REPRODUCE 1. Can you make it more intuitively and simple? 2. 3. OBSERVED RESULT EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: Fedora 34 KDE Plasma Spin (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.
[ksplash] [Bug 439570] ksplashqm crashes inside mesa while watiting for login screen
https://bugs.kde.org/show_bug.cgi?id=439570 --- Comment #2 from Edward --- Created attachment 139996 --> https://bugs.kde.org/attachment.cgi?id=139996=edit 2021-07-11 backtrace Backtrace for current crash of ksplashqm after update restart. -- You are receiving this mail because: You are watching all bug changes.
[ksplash] [Bug 439570] New: ksplashqm will crash while watiting for login screen
https://bugs.kde.org/show_bug.cgi?id=439570 Bug ID: 439570 Summary: ksplashqm will crash while watiting for login screen Product: ksplash Version: 5.22.2 Platform: Other OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: edfreema...@gmail.com Target Milestone: --- Created attachment 139908 --> https://bugs.kde.org/attachment.cgi?id=139908=edit backtrace report SUMMARY: Ksplashqm will randomly crash before login credential are able to be entered on fedora 34 KDE spin using Wayland. Usually clicking on restart application will fix it, however this last time it failed to restart. Claims segmentation fault (11). no KDE add-ons enabled, no third party apps installed, happening on fresh clean install. STEPS TO REPRODUCE 1. restart computer or booting computer after a complete shutdown 2. wait for splash screen to go to login credentials OBSERVED RESULT notice of ksplashqm having segmentation fault, option to restart, cancel or report bug. click on bug report and notified that there is no address to report bug, availability to create backtrace report EXPECTED RESULT loading login screen to login to system. SOFTWARE/OS VERSIONS: Operating System: Fedora 34 KDE Plasma Version: 5.22.2 KDE Frameworks Version: 5.83.0 Qt Version: 5.15.2 Kernel Version: 5.12.13-300.fc34.x86_64 (64-bit) Graphics Platform: Wayland Processors: 2 × AMD E-300 APU with Radeon(tm) HD Graphics Memory: 7.4 GiB of RAM Graphics Processor: AMD PALM ADDITIONAL INFORMATION backtrace attached -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 413736] Widget's hover menu when in panel edit mode sometimes disappears when moving the cursor over it
https://bugs.kde.org/show_bug.cgi?id=413736 Edward Donovan changed: What|Removed |Added CC||kde-b...@numble.net -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 438410] New: System Settings crashed when opening Bluetooth section
https://bugs.kde.org/show_bug.cgi?id=438410 Bug ID: 438410 Summary: System Settings crashed when opening Bluetooth section Product: systemsettings Version: 5.21.5 Platform: Fedora RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: enygma2002...@yahoo.com Target Milestone: --- Application: systemsettings5 (5.21.5) Qt Version: 5.15.2 Frameworks Version: 5.82.0 Operating System: Linux 5.12.9-300.fc34.x86_64 x86_64 Windowing System: X11 Drkonqi Version: 5.21.5 Distribution: "Fedora release 34 (Thirty Four)" -- Information about the crash: - What I was doing when the application crashed: Browsing System Settings from section to section and, when I clicked on the Bluetooth section, I got the crash report. The reporter is unsure if this crash is reproducible. -- Backtrace: Application: System Settings (systemsettings5), signal: Segmentation fault [KCrash Handler] #4 0x5605c6e577b0 in ?? () #5 0x7ff6cac8e3ea in QObjectPrivate::connectImpl(QObject const*, int, QObject const*, void**, QtPrivate::QSlotObjectBase*, Qt::ConnectionType, int const*, QMetaObject const*) () from /lib64/libQt5Core.so.5 #6 0x7ff6cac8e67d in QObject::connectImpl(QObject const*, void**, QObject const*, void**, QtPrivate::QSlotObjectBase*, Qt::ConnectionType, int const*, QMetaObject const*) () from /lib64/libQt5Core.so.5 #7 0x7ff6a006a06a in ColumnView::classBegin() () from /usr/lib64/qt5/qml/org/kde/kirigami.2/libkirigamiplugin.so #8 0x7ff6c9edfe3a in QQmlObjectCreator::createInstance(int, QObject*, bool) () from /lib64/libQt5Qml.so.5 #9 0x7ff6c9ee22a4 in QQmlObjectCreator::setPropertyBinding(QQmlPropertyData const*, QV4::CompiledData::Binding const*) () from /lib64/libQt5Qml.so.5 #10 0x7ff6c9ee2887 in QQmlObjectCreator::setupBindings(bool) () from /lib64/libQt5Qml.so.5 #11 0x7ff6c9edf52a in QQmlObjectCreator::populateInstance(int, QObject*, QObject*, QQmlPropertyData const*) () from /lib64/libQt5Qml.so.5 #12 0x7ff6c9ee00e4 in QQmlObjectCreator::createInstance(int, QObject*, bool) () from /lib64/libQt5Qml.so.5 #13 0x7ff6c9eda4dd in QQmlObjectCreator::create(int, QObject*, QQmlInstantiationInterrupt*, int) () from /lib64/libQt5Qml.so.5 #14 0x7ff6c9ee061b in QQmlObjectCreator::createInstance(int, QObject*, bool) () from /lib64/libQt5Qml.so.5 #15 0x7ff6c9ee22a4 in QQmlObjectCreator::setPropertyBinding(QQmlPropertyData const*, QV4::CompiledData::Binding const*) () from /lib64/libQt5Qml.so.5 #16 0x7ff6c9ee2887 in QQmlObjectCreator::setupBindings(bool) () from /lib64/libQt5Qml.so.5 #17 0x7ff6c9edf52a in QQmlObjectCreator::populateInstance(int, QObject*, QObject*, QQmlPropertyData const*) () from /lib64/libQt5Qml.so.5 #18 0x7ff6c9ee00e4 in QQmlObjectCreator::createInstance(int, QObject*, bool) () from /lib64/libQt5Qml.so.5 #19 0x7ff6c9eda4dd in QQmlObjectCreator::create(int, QObject*, QQmlInstantiationInterrupt*, int) () from /lib64/libQt5Qml.so.5 #20 0x7ff6c9ee061b in QQmlObjectCreator::createInstance(int, QObject*, bool) () from /lib64/libQt5Qml.so.5 #21 0x7ff6c9eda4dd in QQmlObjectCreator::create(int, QObject*, QQmlInstantiationInterrupt*, int) () from /lib64/libQt5Qml.so.5 #22 0x7ff6c9e7f6c2 in QQmlComponentPrivate::beginCreate(QQmlContextData*) () from /lib64/libQt5Qml.so.5 #23 0x7ff6c9e8021e in QQmlComponent::create(QQmlContext*) () from /lib64/libQt5Qml.so.5 #24 0x7ff6cc4336e4 in KCModuleLoader::loadModule(KCModuleInfo const&, KCModuleLoader::ErrorReporting, QWidget*, QStringList const&) () from /lib64/libKF5KCMUtils.so.5 #25 0x7ff6cc4350c9 in KCModuleProxyPrivate::loadModule() () from /lib64/libKF5KCMUtils.so.5 #26 0x7ff6cc435928 in KCModuleProxy::realModule() const () from /lib64/libKF5KCMUtils.so.5 #27 0x7ff6cc4365f7 in KCModuleProxy::showEvent(QShowEvent*) () from /lib64/libKF5KCMUtils.so.5 #28 0x7ff6cb82e85e in QWidget::event(QEvent*) () from /lib64/libQt5Widgets.so.5 #29 0x7ff6cb7ede73 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /lib64/libQt5Widgets.so.5 #30 0x7ff6cac62f48 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /lib64/libQt5Core.so.5 #31 0x7ff6cb82b1e7 in QWidgetPrivate::show_helper() () from /lib64/libQt5Widgets.so.5 #32 0x7ff6cb82b149 in QWidgetPrivate::showChildren(bool) () from /lib64/libQt5Widgets.so.5 #33 0x7ff6cb82b1c3 in QWidgetPrivate::show_helper() () from /lib64/libQt5Widgets.so.5 #34 0x7ff6cb82e353 in QWidgetPrivate::setVisible(bool) () from /lib64/libQt5Widgets.so.5 #35 0x7ff6cb82b129 in QWidgetPrivate::showChildren(bool) () from /lib64/libQt5Widgets.so.5 #36 0x7ff6cb82b1c3 in QWidgetPrivate::show_helper() () from /lib64/libQt5Widgets.so.5 #37 0x7ff6cb82e353 in QWidgetPrivate::setVisible(bool) () from
[plasmashell] [Bug 438313] Wayland: Apps launcher is one launch late
https://bugs.kde.org/show_bug.cgi?id=438313 Edward Oubrayrie changed: What|Removed |Added Status|NEEDSINFO |REPORTED Resolution|WAITINGFORINFO |--- --- Comment #2 from Edward Oubrayrie --- The funny thing is, I am waiting *forever* until I decide to launch something else. It's a FIFO queue of length =1, some component in the launch chain is holding exactly 1 item hostage -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 438313] Wayland: Apps launcher is one launch late
https://bugs.kde.org/show_bug.cgi?id=438313 Edward Oubrayrie changed: What|Removed |Added Summary|Wayland:|Wayland: Apps launcher is ||one launch late -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 438313] New: Wayland:
https://bugs.kde.org/show_bug.cgi?id=438313 Bug ID: 438313 Summary: Wayland: Product: plasmashell Version: 5.22.0 Platform: Neon Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: edoubray...@gmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 STEPS TO REPRODUCE 1. Launch a KDE App with launcher or KRunner. eg Dolphin 2. Launch another app. eg Kate 3. and so on. eg launch Okular OBSERVED RESULT 1. Dolphin does not launch 2. App#1 ie Dolphin, launches (instead of Kate) 3. App#2 ie Kate opens (instead of Okular) EXPECTED RESULT Correct app launches on time SOFTWARE/OS VERSIONS Linux/KDE Plasma: KDE Neon Testing (based on Ubuntu focal 20.04) KDE Plasma Version: 5.22.0 (5.22.0+p20.04+tstable+git20210608.1257-0) KDE Frameworks Version: 5.82.0+p20.04+tunstable+git20210608.0115-0 (kInfoCenter say 5.83.0 for some reason) Qt Version: 5.15.2+p20.04+tunstable+git20210602.0956-0 (kInfoCenter says 5.15.3 for some reason) KDE Apps: 21.04.1+p20.04+tstable+git20210608.0108-0 ADDITIONAL INFORMATION This happens in both: * the default App Launcher(the new Kickoff named SimpleMenu I think?) and the * KRunner It does *not* happen with command-line, even with dbus-launcher / kinit5 It does not happen with all apps, but for sure it does with the kde/wayland ones. The app is not just hidden, I see eg gwenview/dolphin doing their startup work when I launch the next app. Works normally on Xorg. -- You are receiving this mail because: You are watching all bug changes.
