354677 – system monitor applet doesn't close when click on the cross button of the title bar.

Bug 354677 - system monitor applet doesn't close when click on the cross button of the title bar.

Summary: system monitor applet doesn't close when click on the cross button of the tit...

Status:	RESOLVED WORKSFORME

Alias:	None

Product:	plasmashell
Classification:	Plasma
Component:	System Monitor widgets (other bugs)
Version First Reported In:	5.4.2
Platform:	Debian unstable Linux

Importance:	NOR normal
Target Milestone:	1.0
Assignee:	Marco Martin

URL:
Keywords:	triaged

Depends on:
Blocks:

Reported:	2015-11-01 10:12 UTC by cedric
Modified:	2018-10-27 04:01 UTC (History)
CC List:	1 user (show)

See Also:
Latest Commit:
Version Fixed/Implemented In:
Sentry Crash Report:

Attachments
screenshot (434.16 KB, image/png) 2015-11-02 23:50 UTC, cedric	Details
View All Add an attachment

Note You need to log in before you can comment on or make changes to this bug.

Description cedric 2015-11-01 10:12:39 UTC

system monitor applet doesn't close when click on the cross button of the title bar.

I don't know what usefull information I can gather from my system to help, let me know if you need any.

Reproducible: Always

Steps to Reproduce:
1. open system monitor applet with the shortcut ctrl + escape
2. click on the cross button of the title bar
3. the window doesn't close and after some time, you get a popup asking you if you want to kill this application.

Comment 1 David Edmundson 2015-11-02 23:42:47 UTC

screenshot please.

Comment 2 cedric 2015-11-02 23:50:54 UTC

Created attachment 95280 [details]
screenshot

by the way, I just noticed that the app doest refrash anymore after I clicked on the close button, so I get a backtrace at this point :

(gdb) thread apply all bt

Thread 2 (Thread 0x7f71ef0a2700 (LWP 24282)):
#0  0x00007f720201b52d in poll () at ../sysdeps/unix/syscall-template.S:81
#1  0x00007f71fe649382 in ?? () from /usr/lib/x86_64-linux-gnu/libxcb.so.1
#2  0x00007f71fe64aff7 in xcb_wait_for_event () from /usr/lib/x86_64-linux-gnu/libxcb.so.1
#3  0x00007f71f1a28839 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5XcbQpa.so.5
#4  0x00007f7202707a6e in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x00007f71fe2270a4 in start_thread (arg=0x7f71ef0a2700) at pthread_create.c:309
#6  0x00007f720202406d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:111

Thread 1 (Thread 0x7f72042a28c0 (LWP 24281)):
#0  0x00007f7201ff570d in nanosleep () at ../sysdeps/unix/syscall-template.S:81
#1  0x00007f72027b80fd in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#2  0x00007f7202706e68 in QThread::msleep(unsigned long) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#3  0x00007f7202813a7b in QLockFile::tryLock(int) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#4  0x00007f7202d9b9e9 in ?? () from /usr/lib/x86_64-linux-gnu/libKF5ConfigCore.so.5
#5  0x00007f7202d877d6 in KConfig::sync() () from /usr/lib/x86_64-linux-gnu/libKF5ConfigCore.so.5
#6  0x0000000000404e8f in KSystemActivityDialog::saveDialogSettings() ()
#7  0x0000000000404f89 in KSystemActivityDialog::closeEvent(QCloseEvent*) ()
#8  0x00007f72036ae9e8 in QWidget::event(QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#9  0x00007f720366b9dc in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#10 0x00007f7203670ea6 in QApplication::notify(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#11 0x00007f72028e8dbb in QCoreApplication::notifyInternal(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#12 0x00007f72036a9ccd in QWidgetPrivate::close_helper(QWidgetPrivate::CloseMode) () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#13 0x00007f72036cb662 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#14 0x00007f720366b9dc in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#15 0x00007f7203670ea6 in QApplication::notify(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#16 0x00007f72028e8dbb in QCoreApplication::notifyInternal(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#17 0x00007f72030b672e in QGuiApplicationPrivate::processCloseEvent(QWindowSystemInterfacePrivate::CloseEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Gui.so.5
#18 0x00007f72030bb2e5 in QGuiApplicationPrivate::processWindowSystemEvent(QWindowSystemInterfacePrivate::WindowSystemEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Gui.so.5
#19 0x00007f720309f1f8 in QWindowSystemInterface::sendWindowSystemEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/x86_64-linux-gnu/libQt5Gui.so.5
#20 0x00007f71f1a5a100 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5XcbQpa.so.5
#21 0x00007f71fdd06fe7 in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#22 0x00007f71fdd07240 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#23 0x00007f71fdd072ec in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#24 0x00007f720293f56f in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#25 0x00007f72028e654a in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#26 0x00007f7203866abd in QDialog::exec() () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#27 0x000000000040457d in main ()

Comment 3 cedric 2015-11-02 23:58:39 UTC

I found the issue :

ls ~/.config/systemmonitorrc.lock*
/home/xxx/.config/systemmonitorrc.lock
/home/xxx/.config/systemmonitorrc.lock.rmlock
/home/xxx/.config/systemmonitorrc.lock.rmlock.rmlock
/home/xxx/.config/systemmonitorrc.lock.rmlock.rmlock.rmlock
/home/xxx/.config/systemmonitorrc.lock.rmlock.rmlock.rmlock.rmlock
/home/xxx/.config/systemmonitorrc.lock.rmlock.rmlock.rmlock.rmlock.rmlock
/home/xxx/.config/systemmonitorrc.lock.rmlock.rmlock.rmlock.rmlock.rmlock.rmlock
/home/xxx/.config/systemmonitorrc.lock.rmlock.rmlock.rmlock.rmlock.rmlock.rmlock.rmlock
/home/xxx/.config/systemmonitorrc.lock.rmlock.rmlock.rmlock.rmlock.rmlock.rmlock.rmlock.rmlock
/home/xxx/.config/systemmonitorrc.lock.rmlock.rmlock.rmlock.rmlock.rmlock.rmlock.rmlock.rmlock.rmlock
/home/xxx/.config/systemmonitorrc.lock.rmlock.rmlock.rmlock.rmlock.rmlock.rmlock.rmlock.rmlock.rmlock.rmlock
/home/xxx/.config/systemmonitorrc.lock.rmlock.rmlock.rmlock.rmlock.rmlock.rmlock.rmlock.rmlock.rmlock.rmlock.rmlock
/home/xxx/.config/systemmonitorrc.lock.rmlock.rmlock.rmlock.rmlock.rmlock.rmlock.rmlock.rmlock.rmlock.rmlock.rmlock.rmlock
/home/xxx/.config/systemmonitorrc.lock.rmlock.rmlock.rmlock.rmlock.rmlock.rmlock.rmlock.rmlock.rmlock.rmlock.rmlock.rmlock.rmlock
/home/xxx/.config/systemmonitorrc.lock.rmlock.rmlock.rmlock.rmlock.rmlock.rmlock.rmlock.rmlock.rmlock.rmlock.rmlock.rmlock.rmlock.rmlock
/home/xxx/.config/systemmonitorrc.lock.rmlock.rmlock.rmlock.rmlock.rmlock.rmlock.rmlock.rmlock.rmlock.rmlock.rmlock.rmlock.rmlock.rmlock.rmlock
/home/xxx/.config/systemmonitorrc.lock.rmlock.rmlock.rmlock.rmlock.rmlock.rmlock.rmlock.rmlock.rmlock.rmlock.rmlock.rmlock.rmlock.rmlock.rmlock.rmlock
/home/xxx/.config/systemmonitorrc.lock.rmlock.rmlock.rmlock.rmlock.rmlock.rmlock.rmlock.rmlock.rmlock.rmlock.rmlock.rmlock.rmlock.rmlock.rmlock.rmlock.rmlock
/home/xxx/.config/systemmonitorrc.lock.rmlock.rmlock.rmlock.rmlock.rmlock.rmlock.rmlock.rmlock.rmlock.rmlock.rmlock.rmlock.rmlock.rmlock.rmlock.rmlock.rmlock.rmlock
/home/xxx/.config/systemmonitorrc.lock.rmlock.rmlock.rmlock.rmlock.rmlock.rmlock.rmlock.rmlock.rmlock.rmlock.rmlock.rmlock.rmlock.rmlock.rmlock.rmlock.rmlock.rmlock.rmlock
/home/xxx/.config/systemmonitorrc.lock.rmlock.rmlock.rmlock.rmlock.rmlock.rmlock.rmlock.rmlock.rmlock.rmlock.rmlock.rmlock.rmlock.rmlock.rmlock.rmlock.rmlock.rmlock.rmlock.rmlock
/home/xxx/.config/systemmonitorrc.lock.rmlock.rmlock.rmlock.rmlock.rmlock.rmlock.rmlock.rmlock.rmlock.rmlock.rmlock.rmlock.rmlock.rmlock.rmlock.rmlock.rmlock.rmlock.rmlock.rmlock.rmlock
/home/xxx/.config/systemmonitorrc.lock.rmlock.rmlock.rmlock.rmlock.rmlock.rmlock.rmlock.rmlock.rmlock.rmlock.rmlock.rmlock.rmlock.rmlock.rmlock.rmlock.rmlock.rmlock.rmlock.rmlock.rmlock.rmlock
/home/xxx/.config/systemmonitorrc.lock.rmlock.rmlock.rmlock.rmlock.rmlock.rmlock.rmlock.rmlock.rmlock.rmlock.rmlock.rmlock.rmlock.rmlock.rmlock.rmlock.rmlock.rmlock.rmlock.rmlock.rmlock.rmlock.rmlock
...

deleting these lock files fixe the issue, ! so you can close it.

by the way, I think it's still an usability issue that the workspace doesn't recover from undeleted lock file.

Comment 4 Andrew Crouthamel 2018-09-25 21:42:30 UTC

Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days, the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information.

For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please set the bug status as REPORTED so that the KDE team knows that the bug is ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!

Comment 5 Andrew Crouthamel 2018-10-27 04:01:55 UTC

Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information.

For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!