Bug 23047

Summary: Unable to launch new KDE apps
Product: Mageia Reporter: Simon Rowe <srowe>
Component: RPM PackagesAssignee: KDE maintainers <kde>
Status: RESOLVED OLD QA Contact:
Severity: major    
Priority: Normal CC: marja11, ouaurelien
Version: 6   
Target Milestone: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Source RPM: CVE:
Status comment:

Description Simon Rowe 2018-05-17 14:50:20 CEST 
Description of problem:

After a number of days of use my desktop is no longer able to start certain applications, including the logout, shutdown dialogs.


How reproducible:

Only after being logged in for a few days.


Steps to Reproduce:

ltracing "kdialog --getopenurl" shows it stalls like this

QFileDialog::QFileDialog(QWidget*, QString const&, QString const&, QString const&)(0x7ffd2fb337e0, 0, 0x7ffd2fb33798, 0x7ffd2fb337b0 <unfinished ...>
QWidget::event(QEvent*)(0xdeeaf0, 0x7ffd2fb332f0, 5, 0 <unfinished ...>
QObject::childEvent(QChildEvent*)(0xdeeaf0, 0x7ffd2fb332f0, 0x7f487cc1ebf0, 68)                 = 0x4092d0
<... QWidget::event(QEvent*) resumed> )                                                         = 1
QWidget::event(QEvent*)(0xdeea50, 0x7ffd2fb332c0, 5, 0 <unfinished ...>
QObject::childEvent(QChildEvent*)(0xdeea50, 0x7ffd2fb332c0, 0x7f487cc1ebf0, 68)                 = 0x4092d0
<... QWidget::event(QEvent*) resumed> )                                                         = 1
QObject::connectNotify(QMetaMethod const&)(0xdc8110, 0x7ffd2fb33080, 0x7f487cc1ebf0, 0x7f487cdb3100) = 0x4099b0
QObject::event(QEvent*)(0xdc5db0, 0x7ffd2fb33160, 5, 0 <unfinished ...>
QObject::childEvent(QChildEvent*)(0xdc5db0, 0x7ffd2fb33160, 0x7f487cc1ebf0, 68)                 = 0x4092d0
<... QObject::event(QEvent*) resumed> )                                                         = 1
QObject::connectNotify(QMetaMethod const&)(0xdcc9d0, 0x7ffd2fb32f20, 0x7f487cc1ebf0, 0x7f487f892660) = 0x4099b0
QObject::event(QEvent*)(0xdc5db0, 0x7ffd2fb330d0, 5, 0 <unfinished ...>
QObject::childEvent(QChildEvent*)(0xdc5db0, 0x7ffd2fb330d0, 0x7f487cc1ebf0, 68)                 = 0x4092d0
<... QObject::event(QEvent*) resumed> )                                                         = 1
QObject::event(QEvent*)(0xdb1650, 0x7ffd2fb33040, 5, 0 <unfinished ...>
QObject::childEvent(QChildEvent*)(0xdb1650, 0x7ffd2fb33040, 0x7f487cc1ebf0, 68)                 = 0x4092d0
<... QObject::event(QEvent*) resumed> )                                                         = 1
QObject::connectNotify(QMetaMethod const&)(0xdc57c0, 0x7ffd2fb32e00, 0x7f487cc1ebf0, 0x7f487f892660) = 0x4099b0
QObject::connectNotify(QMetaMethod const&)(0xdc5db0, 0x7ffd2fb32f90, 0x7f487cc1ebf0, 0x7f486e726f80) = 0x4099b0
QWidget::event(QEvent*)(0xdeea50, 0x7ffd2fb332c0, 5, 0 <unfinished ...>
QObject::childEvent(QChildEvent*)(0xdeea50, 0x7ffd2fb332c0, 0x7f487cc1ebf0, 68)                 = 0x4092d0
<... QWidget::event(QEvent*) resumed> )                                                         = 1
QObject::connectNotify(QMetaMethod const&)(0xdc50a0, 0x7ffd2fb33080, 0x7f487cc1ebf0, 0x7f487cdb3100) = 0x4099b0
QWidget::event(QEvent*)(0xdeea50, 0x7ffd2fb332f0, 5, 0 <unfinished ...>
QObject::childEvent(QChildEvent*)(0xdeea50, 0x7ffd2fb332f0, 0x7f487cc1ebf0, 68)                 = 0x4092d0
<... QWidget::event(QEvent*) resumed> )                                                         = 1
QObject::childEvent(QChildEvent*)(0xdeda20, 0x7ffd2fb332a0, 0x7f487cc1ebf0, 68)                 = 0x4092d0
QObject::childEvent(QChildEvent*)(0xdeda20, 0x7ffd2fb332a0, 0x7f487cc1ebf0, 68)                 = 0x4092d0
QObject::childEvent(QChildEvent*)(0xdb07f0, 0x7ffd2fb33280, 0x7f487cc1ebf0, 68)                 = 0x4092d0
QObject::childEvent(QChildEvent*)(0xdb07f0, 0x7ffd2fb33200, 0x7f487cc1ebf0, 68)                 = 0x4092d0
QObject::connectNotify(QMetaMethod const&)(0xdc7ef0, 0x7ffd2fb32fb0, 0x7f487cc1ebf0, 0x7f487ddb2c00) = 0x4099b0
QObject::connectNotify(QMetaMethod const&)(0xdc7ef0, 0x7ffd2fb32fb0, 0x7f487cc1ebf0, 0x7f487ddb2c00) = 0x4099b0
QObject::connectNotify(QMetaMethod const&)(0xdb07f0, 0x7ffd2fb33000, 0x7f487cc1ebf0, 0x7f487ddb1c40) = 0x4099b0
QObject::childEvent(QChildEvent*)(0xdc7ef0, 0x7ffd2fb331f0, 0x7f487cc1ebf0, 68)                 = 0x4092d0
QObject::childEvent(QChildEvent*)(0xe27510, 0x7ffd2fb331f0, 0x7f487cc1ebf0, 68)                 = 0x4092d0
QObject::connectNotify(QMetaMethod const&)(0xdedbd0, 0x7ffd2fb33160, 0x7f487cc1ebf0, 0x7f487dd9e4c0) = 0x4099b0
QObject::connectNotify(QMetaMethod const&)(0xdedbd0, 0x7ffd2fb32c40, 0x7f487cc1ebf0, 0x7f487dd9e4c0) = 0x4099b0
QObject::childEvent(QChildEvent*)(0xdb07f0, 0x7ffd2fb332b0, 0x7f487cc1ebf0, 68)                 = 0x4092d0
QObject::connectNotify(QMetaMethod const&)(0xdf0630, 0x7ffd2fb33030, 0x7f487cc1ebf0, 0x7f487dd9e4c0) = 0x4099b0
QObject::connectNotify(QMetaMethod const&)(0xdb07f0, 0x7ffd2fb32ff0, 0x7f487cc1ebf0, 0x7f487ddb1c40) = 0x4099b0
QObject::connectNotify(QMetaMethod const&)(0x7f487f220f50, 0x7ffd2fb32ff0, 0x7f487cc1ebf0, 0x7f487f0168a0) = 0x4099b0
QWidget::event(QEvent*)(0xdeea50, 0x7ffd2fb33260, 5, 0 <unfinished ...>
QObject::childEvent(QChildEvent*)(0xdeea50, 0x7ffd2fb33260, 0x7f487cc1ebf0, 68)                 = 0x4092d0
<... QWidget::event(QEvent*) resumed> )                                                         = 1
QObject::event(QEvent*)(0xe2c940, 0x7ffd2fb33000, 5, 0 <unfinished ...>
QObject::childEvent(QChildEvent*)(0xe2c940, 0x7ffd2fb33000, 0x7f487cc1ebf0, 68)                 = 0x4092d0
<... QObject::event(QEvent*) resumed> )                                                         = 1
QObject::event(QEvent*)(0xe2c940, 0x7ffd2fb32ea0, 5, 0 <unfinished ...>
QObject::childEvent(QChildEvent*)(0xe2c940, 0x7ffd2fb32ea0, 0x7f487cc1ebf0, 68)                 = 0x4092d0
<... QObject::event(QEvent*) resumed> )                                                         = 1


Running "kdialog --yesno test" behaves correctly.
Comment 1 Simon Rowe 2018-05-17 14:54:11 CEST 
When this occurs I have to manually kill my session and log back in again.
Comment 2 Marja Van Waes 2018-05-18 08:15:16 CEST 
(In reply to Simon Rowe from comment #0)
> Description of problem:
> 
> After a number of days of use my desktop is no longer able to start certain
> applications, including the logout, shutdown dialogs.
> 
> 

Have you installed the Grand Update (See the last three posts, from 5 till 14 May, here http://blog.mageia.org/en/ )?

If so, do you still hit this bug after having logged out and back in?

CC: (none) => marja11
Assignee: bugsquad => kde

Comment 3 Simon Rowe 2018-05-18 08:41:34 CEST 
Yes, all the latest updates applied. I didn't log out after the latest which just included Firefox (but I'll have to now).

I've been experiencing this ever since upgrading to mga6, never occurred with an older release.
Comment 4 Simon Rowe 2018-05-18 08:43:49 CEST 
My hunch, for what it's worth, is that something dies/fails after chrome consumes vast amounts of memory.

Are there any logs that would be useful to capture?
Comment 5 Aurelien Oudelet 2020-08-16 17:15:25 CEST 
Mageia 6 changed to end-of-life (EOL) status on 2019-09-30. It is no longer 
maintained, which means that it will not receive any further security or bug 
fix updates.

Package Maintainer: If you wish for this bug to remain open because you plan 
to fix it in a currently maintained version, simply change the 'version' to 
a later Mageia version.

Bug Reporter: Thank you for reporting this issue and we are sorry that we 
weren't able to fix it before Mageia 6's end of life. If you are able to 
reproduce it against a later version of Mageia, you are encouraged to click 
on "Version" and change it against that version of Mageia.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a more recent
Mageia release includes newer upstream software that fixes bugs or makes them
obsolete.

If you would like to help fixing bugs in the future, don't hesitate to join the
packager team via our mentoring program [1] or join the teams that fit you 
most [2].

[1] https://wiki.mageia.org/en/Becoming_a_Mageia_Packager
[2] http://www.mageia.org/contribute/

Best regards,
Aurélien
Bugsquad Team

CC: (none) => ouaurelien
Status: NEW => RESOLVED
Resolution: (none) => OLD

Comment 6 Simon Rowe 2020-08-16 18:04:15 CEST 
Issue reduced in frequency when I switched to Firefox. Not seen the issue with mga7.