[konsole] [Bug 372727] New: KDE Konsole crash

[raven4]

https://bugs.kde.org/show_bug.cgi?id=372727

Bug ID: 372727
   Summary: KDE Konsole crash
   Product: konsole
   Version: 16.08.1
  Platform: Fedora RPMs
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: konsole-de...@kde.org
  Reporter: rav...@raven4.cz
  Target Milestone: ---

Application: konsole (16.08.1)

Qt Version: 5.6.1
Frameworks Version: 5.26.0
Operating System: Linux 4.7.10-100.ccs.1 x86_64
Distribution: "Fedora release 23 (Twenty Three)"

-- Information about the crash:
NOTE:
I have mapped shortcuts
"Alt+(" for Split view Left/right
Alt+Shift+O for Close Others

STEPS to crash
open console
press Alt+( 3times
press Alt+Shift+O 1x
press Alt+( 3times
press Alt+Shift+O 1x - ! CRASH!

NOTE:
sometimes I had to repeat cyscle one more time to crash, sometime it crashes
not on "Close others" action but on "Split" action

The crash can be reproduced every time.

-- Backtrace:
Application: Konsole (konsole), signal: Segmentation fault
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7fd5405cb900 (LWP 15991))]

Thread 3 (Thread 0x7fd53cbdf700 (LWP 15994)):
#0  0x7fd54d4a0b7d in poll () at /lib64/libc.so.6
#1  0x7fd54ad3e272 in _xcb_conn_wait () at /lib64/libxcb.so.1
#2  0x7fd54ad3fee7 in xcb_wait_for_event () at /lib64/libxcb.so.1
#3  0x7fd5404d3039 in QXcbEventReader::run() () at /lib64/libQt5XcbQpa.so.5
#4  0x7fd54e0ab00c in QThreadPrivate::start(void*) () at
/lib64/libQt5Core.so.5
#5  0x7fd54bc6f61a in start_thread () at /lib64/libpthread.so.0
#6  0x7fd54d4ac5fd in clone () at /lib64/libc.so.6

Thread 2 (Thread 0x7fd531e30700 (LWP 15995)):
#0  0x7fd54d4a0b7d in poll () at /lib64/libc.so.6
#1  0x7fd54948618c in g_main_context_iterate.isra () at
/lib64/libglib-2.0.so.0
#2  0x7fd54948629c in g_main_context_iteration () at
/lib64/libglib-2.0.so.0
#3  0x7fd54e295b5b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /lib64/libQt5Core.so.5
#4  0x7fd54e24625a in
QEventLoop::exec(QFlags) () at
/lib64/libQt5Core.so.5
#5  0x7fd54e0a6bd4 in QThread::exec() () at /lib64/libQt5Core.so.5
#6  0x7fd5533e0675 in QDBusConnectionManager::run() () at
/lib64/libQt5DBus.so.5
#7  0x7fd54e0ab00c in QThreadPrivate::start(void*) () at
/lib64/libQt5Core.so.5
#8  0x7fd54bc6f61a in start_thread () at /lib64/libpthread.so.0
#9  0x7fd54d4ac5fd in clone () at /lib64/libc.so.6

Thread 1 (Thread 0x7fd5405cb900 (LWP 15991)):
[KCrash Handler]
#6  0x7fd553467914 in QDomNamedNodeMapPrivate::clearMap() () at
/lib64/libQt5Xml.so.5
#7  0x7fd553467b4e in QDomElementPrivate::~QDomElementPrivate() () at
/lib64/libQt5Xml.so.5
#8  0x7fd553467bb9 in QDomElementPrivate::~QDomElementPrivate() () at
/lib64/libQt5Xml.so.5
#9  0x7fd55346685c in QDomNodePrivate::~QDomNodePrivate() () at
/lib64/libQt5Xml.so.5
#10 0x7fd553467bb9 in QDomElementPrivate::~QDomElementPrivate() () at
/lib64/libQt5Xml.so.5
#11 0x7fd55346685c in QDomNodePrivate::~QDomNodePrivate() () at
/lib64/libQt5Xml.so.5
#12 0x7fd553467bb9 in QDomElementPrivate::~QDomElementPrivate() () at
/lib64/libQt5Xml.so.5
#13 0x7fd55346685c in QDomNodePrivate::~QDomNodePrivate() () at
/lib64/libQt5Xml.so.5
#14 0x7fd553467bb9 in QDomElementPrivate::~QDomElementPrivate() () at
/lib64/libQt5Xml.so.5
#15 0x7fd55346685c in QDomNodePrivate::~QDomNodePrivate() () at
/lib64/libQt5Xml.so.5
#16 0x7fd553466a29 in QDomDocumentPrivate::~QDomDocumentPrivate() () at
/lib64/libQt5Xml.so.5
#17 0x7fd552495deb in KXMLGUIClient::~KXMLGUIClient() () at
/lib64/libKF5XmlGui.so.5
#18 0x7fd552e4fc01 in Konsole::SessionController::~SessionController() ()
at /lib64/libkonsoleprivate.so.16
#19 0x7fd552e4fc49 in Konsole::SessionController::~SessionController() ()
at /lib64/libkonsoleprivate.so.16
#20 0x7fd54e26f8a8 in QObject::event(QEvent*) () at /lib64/libQt5Core.so.5
#21 0x7fd54ed6c10c in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() at /lib64/libQt5Widgets.so.5
#22 0x7fd54ed71646 in QApplication::notify(QObject*, QEvent*) () at
/lib64/libQt5Widgets.so.5
#23 0x7fd54e2473ea in QCoreApplication::notifyInternal2(QObject*, QEvent*)
() at /lib64/libQt5Core.so.5
#24 0x7fd54e24940a in QCoreApplicationPrivate::sendPostedEvents(QObject*,
int, QThreadData*) () at /lib64/libQt5Core.so.5
#25 0x7fd54e295ac3 in postEventSourceDispatch(_GSource*, int (*)(void*),
void*) () at /lib64/libQt5Core.so.5
#26 0x7fd549485e5a in g_main_context_dispatch () at /lib64/libglib-2.0.so.0
#27 0x7fd5494861f0 in g_main_context_iterate.isra () at
/lib64/libglib-2.0.so.0
#28 0x7fd54948629c in g_main_context_iteration () at
/lib64/libglib-2.0.so.0
#29 0x7fd54e295b3f in
QEventDispatcherGlib::proc

[kscreenlocker] [Bug 445769] New: screenlocker (+ sddm/kdm) miss field to enter OTP/PIN (eg. from Google auth app) AND password

[raven4]

https://bugs.kde.org/show_bug.cgi?id=445769

Bug ID: 445769
   Summary: screenlocker (+ sddm/kdm) miss field to enter OTP/PIN
(eg. from Google auth app) AND password
   Product: kscreenlocker
   Version: 5.23.2
  Platform: Fedora RPMs
OS: Linux
Status: REPORTED
  Severity: major
  Priority: NOR
 Component: general
  Assignee: plasma-b...@kde.org
  Reporter: rav...@raven4.cz
CC: bhus...@gmail.com
  Target Milestone: ---

SUMMARY
***
my Fedora is configured to use PIN (OTP via Android google auth), on Linux side
it is done via package "google-authenticator-1.09-3.fc35.x86_64" and in PAM
configured via password-auth :
authrequired  pam_google_authenticator.so nullok

PROBLEM:
When screen is locked and I want to unlock it there's only field to enter
password but not field to enter PIN first, evry unlock attempt thus leads to
fail
I had to delete whole kscreenlock* stuff by force and replace it by
xscreensaver that SUPPORTS entering PIN+password
! Also kdm and sddm do NOT provide PIN support thus i had to replace it by
lightdm which DOES
***


STEPS TO REPRODUCE
1. lock screen manually or by inactivity
2. screen is locked
3. lock screen does NOT provide ANY way to enter PIN
4. unlock ALWAYS fails

EXPECTED RESULT
sddm/kdm and screenlocker shall contain additional field for entering OTP/PIN

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: 
Fedora 35

KDE Plasma Version: 
rpm -qa | grep kscreenlo
kscreenlocker-5.23.2-1.fc35.x86_64

KDE Frameworks Version: 
Qt Version: 

ADDITIONAL INFORMATION

-- 
You are receiving this mail because:
You are watching all bug changes.

[kscreenlocker] [Bug 445769] screenlocker (+ sddm/kdm) miss field to enter OTP/PIN (eg. from Google auth app) AND password

[raven4]

https://bugs.kde.org/show_bug.cgi?id=445769

--- Comment #2 from raven4  ---
Hello

I checked in my Fed.35
kscreenlocker-5.25.4-1.fc35.x86_64
plasma-workspace-common-5.25.4-1.fc35.x86_64


and yes u r correct unlocking from screenlocker works now. I didnt 
notice it as it is very badly visually implemented, there is no any 
mention(no text/editbox) about separate entering PIN and later on 
password. There's only "editbox" enter password

I need to enter PIN 1st, press ENTER, then delete editbox content, type 
password and ENTERThats confusing...

Other screenlockers i found some time ago ask separately about PIN and 
then password


Can this be improved ?


Thank you.


BR, raven4

On 04. 11. 22 22:21, Nate Graham wrote:
> https://bugs.kde.org/show_bug.cgi?id=445769
>
> Nate Graham  changed:
>
> What|Removed |Added
> 
>   CC||n...@kde.org
>   Status|REPORTED|NEEDSINFO
>   Resolution|--- |WAITINGFORINFO
>
> --- Comment #1 from Nate Graham  ---
> Thank you for reporting this issue in KDE software. As it has been a while
> since it was reported, can we please ask you to see if you can reproduce the
> issue with a recent software version? Like Plasma 5.25, or ideally 5.26? I ask
> because 5.25 contained some PAM changes that could have fixed this.
>
>   Can you check? If you can still reproduce the issue with 5.25 or later, 
> please
> change the status to "CONFIRMED" when replying. Thank you!
>

-- 
You are receiving this mail because:
You are watching all bug changes.