[kgpg] [Bug 425988] New: kgpg crash after login Wayland (Xwayland)
https://bugs.kde.org/show_bug.cgi?id=425988 Bug ID: 425988 Summary: kgpg crash after login Wayland (Xwayland) Product: kgpg Version: unspecified Platform: openSUSE RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@opensource.sf-tec.de Reporter: sanderbartsante...@gmail.com Target Milestone: --- Application: kgpg (20.08.0) Qt Version: 5.15.0 Frameworks Version: 5.73.0 Operating System: Linux 5.8.2-1-default x86_64 Windowing system: Wayland Distribution: "openSUSE Tumbleweed" -- Information about the crash: - What I was doing when the application crashed: I logged out from a full wayland session on openSUSE Tumbleweed snapshot 20200826 and logged in again into a Wayland (Xwayland) session after this kgpg crashed. -- Backtrace: Application: KGpg (kgpg), signal: Aborted [KCrash Handler] #4 0x7fda89eb04b1 in raise () from /lib64/libc.so.6 #5 0x7fda89e99539 in abort () from /lib64/libc.so.6 #6 0x7fda8a2d1c27 in qt_message_fatal (message=..., context=...) at global/qlogging.cpp:1914 #7 QMessageLogger::fatal (this=this@entry=0x7fff6d21deb0, msg=msg@entry=0x7fda863320b8 "The Wayland connection broke. Did the Wayland compositor die?") at global/qlogging.cpp:893 #8 0x7fda862adef9 in QtWaylandClient::QWaylandDisplay::checkError (this=) at /usr/include/qt5/QtCore/qlogging.h:90 #9 QtWaylandClient::QWaylandDisplay::checkError (this=) at qwaylanddisplay.cpp:204 #10 0x7fda862bbdee in QtWaylandClient::QWaylandDisplay::flushRequests (this=0x560e645208a0) at qwaylanddisplay.cpp:222 #11 0x7fda8a521150 in doActivate (sender=0x560e64539cb0, signal_index=4, argv=0x7fff6d21df90, argv@entry=0x0) at ../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:395 #12 0x7fda8a51a470 in QMetaObject::activate (sender=sender@entry=0x560e64539cb0, m=m@entry=0x7fda8a7cc180 , local_signal_index=local_signal_index@entry=1, argv=argv@entry=0x0) at kernel/qobject.cpp:3946 #13 0x7fda8a4e77f3 in QAbstractEventDispatcher::awake (this=this@entry=0x560e64539cb0) at .moc/moc_qabstracteventdispatcher.cpp:149 #14 0x7fda8a5420bc in QEventDispatcherGlib::processEvents (this=0x560e64539cb0, flags=...) at kernel/qeventdispatcher_glib.cpp:430 #15 0x7fda8a4e95fb in QEventLoop::exec (this=this@entry=0x7fff6d21e0b0, flags=..., flags@entry=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:141 #16 0x7fda8a4f1860 in QCoreApplication::exec () at ../../include/QtCore/../../src/corelib/global/qflags.h:121 #17 0x560e62a77fa0 in main (argc=, argv=) at /usr/src/debug/kgpg-20.08.0-1.2.x86_64/main.cpp:80 [Inferior 1 (process 14750) detached] Possible duplicates by query: bug 424911, bug 423951, bug 423132, bug 417285, bug 414922. Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[kdeplasma-addons] [Bug 421353] New: opening task switcher and krunner while application dashboard is opened is possible but both disappear immediately
https://bugs.kde.org/show_bug.cgi?id=421353 Bug ID: 421353 Summary: opening task switcher and krunner while application dashboard is opened is possible but both disappear immediately Product: kdeplasma-addons Version: 5.18.5 Platform: Other OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: Application Dashboard Assignee: h...@kde.org Reporter: sanderbartsante...@gmail.com CC: plasma-b...@kde.org Target Milestone: --- SUMMARY It's possible to open the task switcher and krunner while the application dashboard is opened but both disappear immediately. STEPS TO REPRODUCE 1. Open task switcher or krunner with keyboard shortcut while application dashboard is opened OBSERVED RESULT Both the task switcher and krunner disappear immediately EXPECTED RESULT For the shortcuts to open the task switcher or krunner to not work or imho better, to close the application dashboard and keep the task switcher or krunner opened. SOFTWARE/OS VERSIONS Windows: macOS: Kernel: 5.6.11-1 KDE Plasma Version: 5.18.5 KDE Frameworks Version: 5.69.0 Qt Version: 5.14.1 -- You are receiving this mail because: You are watching all bug changes.
[kdeplasma-addons] [Bug 421352] New: Application dashboard search text seems selectable/ editable
https://bugs.kde.org/show_bug.cgi?id=421352 Bug ID: 421352 Summary: Application dashboard search text seems selectable/ editable Product: kdeplasma-addons Version: 5.18.5 Platform: openSUSE RPMs OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: Application Dashboard Assignee: h...@kde.org Reporter: sanderbartsante...@gmail.com CC: plasma-b...@kde.org Target Milestone: --- SUMMARY Clicking on search area in application dashboard doesn't clear "Type to search..." text, on it's own this isn't necessarily a problem but together with a blinking text cursor (like the one which appears now when I'm typing up my bug report) appearing it seems like the text would be either selectable or editable STEPS TO REPRODUCE 1. Click on "Type to search..." text in application dashboard OBSERVED RESULT The text in the search area remains and a blinking cursor appears. EXPECTED RESULT Behavior which is consistent with the search text in the search area in system settings, greyed out blinking cursor at the beginning of the line etc. SOFTWARE/OS VERSIONS Windows: macOS: Kernel: 5.6.11-1 KDE Plasma Version: 5.18.5 KDE Frameworks Version: 5.69.0 Qt Version: 5.14.1 -- You are receiving this mail because: You are watching all bug changes.
[kdeplasma-addons] [Bug 421351] New: Application dashboard: default shortcut meta only works when a shortcut is set
https://bugs.kde.org/show_bug.cgi?id=421351 Bug ID: 421351 Summary: Application dashboard: default shortcut meta only works when a shortcut is set Product: kdeplasma-addons Version: 5.18.5 Platform: openSUSE RPMs OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: Application Dashboard Assignee: h...@kde.org Reporter: sanderbartsante...@gmail.com CC: plasma-b...@kde.org Target Milestone: --- SUMMARY Besides the known bug https://bugs.kde.org/show_bug.cgi?id=387048 there is another related to the meta key, personally I'd like to be able to use the meta key to open the application dashboard but I'm able to do so without a custom keyboard shortcut set and I'm unable to set this custom shortcut to meta. I don't know if the application dashboard worked before I changed the shortcut but after I changed it to something custom the meta shortcut will only work with the keyboard shortcut set. STEPS TO REPRODUCE 1. Set custom shortcut for application dashboard (this might not be needed) 2. Set shortcut to none 3. Meta key will not open application dashboard OBSERVED RESULT Meta key not working to open dashboard without custom shortcut keybinding set to another key. EXPECTED RESULT Meta key works to open application dashboard without custom shortcut keybinding set. SOFTWARE/OS VERSIONS Windows: macOS: Kernel: 5.6.11-1 KDE Plasma Version: 5.18.5 KDE Frameworks Version: 5.69.0 Qt Version: 5.14.1 -- You are receiving this mail because: You are watching all bug changes.
[drkonqi] [Bug 421349] New: drkonqi error sending the crash report, more user friendly message?
https://bugs.kde.org/show_bug.cgi?id=421349 Bug ID: 421349 Summary: drkonqi error sending the crash report, more user friendly message? Product: drkonqi Version: 5.18.5 Platform: openSUSE RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: sanderbartsante...@gmail.com Target Milestone: --- SUMMARY I was about to report a crash, a duplicate of 420647. So drkonqi suggested adding my information to the original bug. However this is what drkonqi reported: https://imgur.com/a/Ug6uloM "Error sending crash report: /[113] Sorry, but you are not allowed to (un)mark comments or attachments as private../" STEPS TO REPRODUCE 1. Report a duplicate crash and try to attach information to earlier reported bug OBSERVED RESULT Not being able to attach my bug information to earlier reported bug EXPECTED RESULT Succeeding in attaching my information to earlier bug or see a more user friendly message being displayed, this would have been my first time reporting a bug and I therefore wouldn't have a single clue what to do in case of an error. I wouldn't think it's unlikely some users might be deterred by this and choose to not report their information, which I don't think is something which is desired. SOFTWARE/OS VERSIONS Kernel: 5.6.11-1 KDE Plasma: 5.18.5 KDE Frameworks: 5.69.0 Qt Version: 5.14.1 -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 420695] Dolphin crashes when closing terminal via "Close Session"
https://bugs.kde.org/show_bug.cgi?id=420695 ssantema changed: What|Removed |Added CC||sanderbartsante...@gmail.co ||m -- You are receiving this mail because: You are watching all bug changes.
