SUMMARY Unable to configure setting for Spectacle because it "freezes" when clicking "Configure..." button. STEPS TO REPRODUCE 1. Open Spectacle application from application menu or 'Print' screen key. 2. Click on "Configure..." button OBSERVED RESULT All the other buttons in the program become unresponsive and unable to close out the program normally. Can still drag the window around and no longer able to interact with the program itself. Have to kill the program via Ctrl+Alt+Esc. EXPECTED RESULT Spectacle to open a new window to configure settings such as default save location for screenshots. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: Manjaro (available in About System) KDE Plasma Version: 5.17.5 KDE Frameworks Version: 5.67.0 Qt Version: 5.14.1 ADDITIONAL INFORMATION
Hi, sadly I cannot reproduce. Can you try to get a backtrace by attaching a debugger to see where it is hanging?
(In reply to David Redondo from comment #1) > Hi, sadly I cannot reproduce. Can you try to get a backtrace by attaching a > debugger to see where it is hanging? I am new at this so forgive me if this is not what you are looking for. All of this is when I force close the program. Starting program: /usr/bin/spectacle stack [Thread debugging using libthread_db enabled] Using host libthread_db library "/usr/lib/libthread_db.so.1". [New Thread 0x7ffff0bfe700 (LWP 12876)] [New Thread 0x7fffeb87b700 (LWP 12877)] [Thread 0x7ffff0bfe700 (LWP 12876) exited] Thread 1 "spectacle" received signal SIGTERM, Terminated. 0x00007ffff4a59c45 in pthread_cond_wait@@GLIBC_2.3.2 () from /usr/lib/libpthread.so.0 (gdb) backtrace #0 0x00007ffff4a59c45 in pthread_cond_wait@@GLIBC_2.3.2 () from /usr/lib/libpthread.so.0 #1 0x00007ffff762683b in ?? () from /usr/lib/libxcb.so.1 #2 0x00007ffff7627fef in ?? () from /usr/lib/libxcb.so.1 #3 0x00007ffff7628103 in xcb_wait_for_reply () from /usr/lib/libxcb.so.1 #4 0x00007ffff0f6c55c in QXcbConnection::sync() () from /usr/lib/libQt5XcbQpa.so.5 #5 0x00007ffff0f87b7c in ?? () from /usr/lib/libQt5XcbQpa.so.5 #6 0x00007ffff0f87e80 in ?? () from /usr/lib/libQt5XcbQpa.so.5 #7 0x00007ffff64b9ce5 in QBackingStore::beginPaint(QRegion const&) () from /usr/lib/libQt5Gui.so.5 #8 0x00007ffff6bc2409 in ?? () from /usr/lib/libQt5Widgets.so.5 #9 0x00007ffff6bc2fe4 in ?? () from /usr/lib/libQt5Widgets.so.5 #10 0x00007ffff6becf07 in QWidgetPrivate::syncBackingStore() () from /usr/lib/libQt5Widgets.so.5 #11 0x00007ffff6bf3f04 in QWidget::event(QEvent*) () from /usr/lib/libQt5Widgets.so.5 #12 0x00007ffff6baf362 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib/libQt5Widgets.so.5 #13 0x00007ffff6bb8819 in QApplication::notify(QObject*, QEvent*) () from /usr/lib/libQt5Widgets.so.5 #14 0x00007ffff5f32962 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /usr/lib/libQt5Core.so.5 #15 0x00007ffff5f351c6 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () from /usr/lib/libQt5Core.so.5 #16 0x00007ffff5f8b9d4 in ?? () from /usr/lib/libQt5Core.so.5 #17 0x00007ffff3e0c39e in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0 #18 0x00007ffff3e0e1b1 in ?? () from /usr/lib/libglib-2.0.so.0 #19 0x00007ffff3e0e1f1 in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0 #20 0x00007ffff5f8b020 in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQt5Core.so.5 #21 0x00007ffff5f314cc in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQt5Core.so.5 #22 0x00007ffff5f394d6 in QCoreApplication::exec() () from /usr/lib/libQt5Core.so.5 #23 0x00005555555736da in ?? () #24 0x00007ffff5901153 in __libc_start_main () from /usr/lib/libc.so.6 #25 0x000055555557402e in ?? ()
The strange thing is I can only see the window to configure settings for Spectacle is when I change my application style -> window decorations to a different theme when I think Spectacle "freezes".
So it depends on the window decoration? Which one causes this behavior?
I tried with all the window decorations, and I seem to have the exact problem no matter the theme. It occurs on Arc, Arc Dark, Breeze, Oxygen, Plastik, and my current Sweet-Dark theme. I close Spectacle, switch to a a new window decoration, and reproduce the steps with same results to unable seeing the configure screen for Spectacle. The only way to fix it is to click the "configure..." button, and switch to a new window decoration to see Spectacle window.
Can you close the dialog by pressing Esc?
(In reply to David Redondo from comment #6) > Can you close the dialog by pressing Esc? Yes, I am able to close the dialog by pressing ESC.
Really weird issue. Any chance you could check again with Plasma 5.18?
(In reply to Nate Graham from comment #8) > Really weird issue. > > Any chance you could check again with Plasma 5.18? I tried Plasma 5.18 and still issues. I noticed the problems exist only on custom global themes I downloaded from system settings. Currently using Breeze Dark theme and is perfect.
Does this happen for other apps, or just Spectacle? Which global themes are you using that cause this?
Any Manjaro's default theme I use provided it came with such as Breeze, Breath, and Oxygen work fine, and I have no issues with Spectacle. It seems Spectacle is the only program so far that has issues with trying to use any custom global theme. I tried Aritim-Dark and Sweet theme and the configure window is invisible until I Meta+ArrowKeys to snap the window on the desktop.
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 mark the bug 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!
Thanks for the update; changing status correctly.