[dolphin] [Bug 452598] New: Dolphin crashed when hovering toolbar buttons with mouse
https://bugs.kde.org/show_bug.cgi?id=452598 Bug ID: 452598 Summary: Dolphin crashed when hovering toolbar buttons with mouse Product: dolphin Version: 21.12.3 Platform: Ubuntu Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: u...@ultr.pl CC: kfm-de...@kde.org Target Milestone: --- Application: dolphin (21.12.3) Qt Version: 5.15.2 Frameworks Version: 5.92.0 Operating System: Linux 5.17.0-2.3-liquorix-amd64 x86_64 Windowing System: X11 Distribution: Ubuntu 21.10 DrKonqi: 5.24.4 [KCrashBackend] -- Information about the crash: - What I was doing when the application crashed: Run Dolphin (the only instance). Immediately when the window appeared I moved the mouse over the toolbar buttons. Their tooltips started to show and disappear. Suddenly dolphin crashed. The reporter is unsure if this crash is reproducible. -- Backtrace: Application: Dolphin (dolphin), signal: Segmentation fault [KCrash Handler] #4 QScopedPointer >::operator-> (this=0x8) at ../../include/QtCore/../../src/corelib/tools/qscopedpointer.h:116 #5 qGetPtrHelper > const> (ptr=...) at ../../include/QtCore/../../src/corelib/global/qglobal.h:1135 #6 QWidget::d_func (this=0x0) at ../../include/QtWidgets/../../src/widgets/kernel/qwidget.h:132 #7 QWidget::style (this=0x0) at kernel/qwidget.cpp:2573 #8 0x7fef743411b4 in QApplication::event (this=0x7ffe63a56020, e=0x7ffe63a55c70) at kernel/qapplication.cpp:1899 #9 0x7fef7433b6b3 in QApplicationPrivate::notify_helper (this=, receiver=0x7ffe63a56020, e=0x7ffe63a55c70) at kernel/qapplication.cpp:3632 #10 0x7fef7384d16a in QCoreApplication::notifyInternal2 (receiver=0x7ffe63a56020, event=0x7ffe63a55c70) at kernel/qcoreapplication.cpp:1063 #11 0x7fef738a586b in QTimerInfoList::activateTimers (this=0x557d5adbc990) at kernel/qtimerinfo_unix.cpp:643 #12 0x7fef738a617c in timerSourceDispatch (source=) at kernel/qeventdispatcher_glib.cpp:183 #13 0x7fef714cc8bb in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #14 0x7fef7151ff08 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #15 0x7fef714ca003 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #16 0x7fef738a6548 in QEventDispatcherGlib::processEvents (this=0x557d5adc2090, flags=...) at kernel/qeventdispatcher_glib.cpp:423 #17 0x7fef7384ba9b in QEventLoop::exec (this=this@entry=0x7ffe63a55eb0, flags=..., flags@entry=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:69 #18 0x7fef73854024 in QCoreApplication::exec () at ../../include/QtCore/../../src/corelib/global/qflags.h:121 #19 0x7fef73c27d10 in QGuiApplication::exec () at kernel/qguiapplication.cpp:1867 #20 0x7fef7433b629 in QApplication::exec () at kernel/qapplication.cpp:2824 #21 0x557d5a4c0c53 in main (argc=, argv=) at ./src/main.cpp:230 [Inferior 1 (process 164236) detached] Possible duplicates by query: bug 440385, bug 437539, bug 430900, bug 430859, bug 430824. Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[klipper] [Bug 409366] Clearing clipboard history does not clear the clipboard / Content of clipboard is lost after closing application
https://bugs.kde.org/show_bug.cgi?id=409366 --- Comment #7 from ultr --- Fix: https://phabricator.kde.org/D22684 -- You are receiving this mail because: You are watching all bug changes.
[klipper] [Bug 409366] Clearing clipboard history does not clear the clipboard / Content of clipboard is lost after closing application
https://bugs.kde.org/show_bug.cgi?id=409366 ultr changed: What|Removed |Added Version|5.16.2 |5.16.3 --- Comment #6 from ultr --- The original issue still occurs in Plasma 5.16.3. -- You are receiving this mail because: You are watching all bug changes.
[klipper] [Bug 409366] Clearing clipboard history does not clear the clipboard / Content of clipboard is lost after closing application
https://bugs.kde.org/show_bug.cgi?id=409366 --- Comment #5 from ultr --- The original issue was most likely caused by this change: https://github.com/KDE/plasma-workspace/commit/3bd6ac34ed74e3b86bfb6b29818b726baf505f20#diff-4aebb4a49ac5fcac58f31c1db689096e >[Klipper] Always restore the last clipbboard item >Summary: >D19852 intrdouced x-kde-force-image-copy hint for programs to specify that >images should be set to the clipboard even if should not be included in the >history. But when the program was closed the clipboard was restored to the >first >item in history in which the image was not included. To fix this introduce a >new >class member which holds the last clipboard item and restore it. >Credit goes to David Edumndson >Test Plan: >Try it with spectacle It is fine, but simply lacks support for clearing the history for the new m_last variable breaking the previous behavior in this matter. -- You are receiving this mail because: You are watching all bug changes.
[klipper] [Bug 409366] Clearing clipboard history does not clear the clipboard / Content of clipboard is lost after closing application
https://bugs.kde.org/show_bug.cgi?id=409366 ultr changed: What|Removed |Added Summary|Clearing clipboard history |Clearing clipboard history |does not clear the |does not clear the |clipboard |clipboard / Content of ||clipboard is lost after ||closing application -- You are receiving this mail because: You are watching all bug changes.
[klipper] [Bug 409366] Clearing clipboard history does not clear the clipboard
https://bugs.kde.org/show_bug.cgi?id=409366 ultr changed: What|Removed |Added Ever confirmed|0 |1 Resolution|WORKSFORME |--- Status|RESOLVED|REOPENED --- Comment #4 from ultr --- With "Prevent empty clipboard" option unchecked Klipper fails to work properly. So the original issue still stands (or this is an entirely new problem with Klipper). Issue when "Prevent empty clipboard" option is unchecked: SUMMARY Content of clipboard is lost after closing application. STEPS TO REPRODUCE 0. Uncheck "Prevent empty clipboard" option in Klipper. 1. Open 2 instances of KWrite (or Kate). 2. Input some text into one KWrite window. 3. Copy this text. 4. Close the window (without saving). 5. Try pasting the text into another KWrite window (it won't work). OBSERVED RESULT Cannot paste text copied a moment ago. Plasma's Klipper widget shows the copied text in the history, but it is not in the clipboard (use `xsel -o` to verify this). EXPECTED RESULT Clipboard should contain the copied text. It should not be emptied after closing application window. SOFTWARE/OS VERSIONS KDE Plasma Version: 5.16.2 KDE Frameworks Version: 5.59.0 Qt Version: 5.12.2 -- You are receiving this mail because: You are watching all bug changes.
[klipper] [Bug 409366] Clearing clipboard history does not clear the clipboard
https://bugs.kde.org/show_bug.cgi?id=409366 ultr changed: What|Removed |Added Resolution|--- |WORKSFORME Status|REPORTED|RESOLVED --- Comment #3 from ultr --- @Kai Uwe Broulik I had this option unchecked. But after: - checking it - pressing Apply - unchecking it - applying the settings again the issue does no longer occur. Weird. Closing the bug. -- You are receiving this mail because: You are watching all bug changes.
[klipper] [Bug 409366] Clearing clipboard history does not clear the clipboard
https://bugs.kde.org/show_bug.cgi?id=409366 --- Comment #2 from ultr --- Update: It seems to be X11-wide problem. $ xsel -bc should clean the clipboard, but doesn't. A workaround could be to set the clipboard to an empty string: $ true | xclip -selection clipboard and only then clean the Klipper's history. SOFTWARE/OS VERSIONS OS: Ubuntu 19.04 X.Org: 1.20.4 -- You are receiving this mail because: You are watching all bug changes.
[klipper] [Bug 409366] Clearing clipboard history does not clear the clipboard
https://bugs.kde.org/show_bug.cgi?id=409366 ultr changed: What|Removed |Added CC||u...@ultr.pl -- You are receiving this mail because: You are watching all bug changes.
[klipper] [Bug 409366] New: Clearing clipboard history does not clear the clipboard
https://bugs.kde.org/show_bug.cgi?id=409366 Bug ID: 409366 Summary: Clearing clipboard history does not clear the clipboard Product: klipper Version: 5.16.2 Platform: Kubuntu Packages OS: Linux Status: REPORTED Severity: major Priority: NOR Component: plasma-widget Assignee: plasma-b...@kde.org Reporter: u...@ultr.pl Target Milestone: --- SUMMARY Clearing clipboard history does not clear the clipboard content. STEPS TO REPRODUCE 0. Open Kate, input some text. 1. Copy the text into clipboard. 2. Clear the Plasma's clipboard. 3. Try pasting the clipboard content into Kate (it will paste). OR 0. Open Dolphin, select a file. 1. Copy the file. 2. Clear the Plasma's clipboard. 3. Open context menu in Dolphin, notice you can still "Paste One File". OBSERVED RESULT *History* is cleared, there is no active element in the Plasma widget. Clipboard's *tooltip* says that "the clipboard is empty". But pressing Ctrl+V pastes the last clipboard content! EXPECTED RESULT Clipboard should actually be cleared. This worked fine in 5.15.x (and maybe also in 5.16.0/5.16.1). SOFTWARE/OS VERSIONS KDE Plasma Version: 5.16.2 KDE Frameworks Version: 5.59.0 Qt Version: 5.12.2 Marking as Major due to possible privacy/security issues while Plasma show misleading messages. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 409027] KDevelop crashed when opening a file
https://bugs.kde.org/show_bug.cgi?id=409027 ultr changed: What|Removed |Added Resolution|--- |DUPLICATE Status|REPORTED|RESOLVED --- Comment #2 from ultr --- I think it may be the same issue. I wasn't able to reproduce the crash when opening the file. Closing as duplicate of #409029. *** This bug has been marked as a duplicate of bug 409029 *** -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 409029] KDevelop crashes when pasting specific line into C++ file
https://bugs.kde.org/show_bug.cgi?id=409029 --- Comment #2 from ultr --- *** Bug 409027 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 409029] New: KDevelop crashes when pasting specific line into C++ file
https://bugs.kde.org/show_bug.cgi?id=409029 Bug ID: 409029 Summary: KDevelop crashes when pasting specific line into C++ file Product: kdevelop Version: 5.3.2 Platform: Ubuntu Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdevelop-bugs-n...@kde.org Reporter: u...@ultr.pl Target Milestone: --- Application: kdevelop (5.3.2) Qt Version: 5.12.2 Frameworks Version: 5.59.0 Operating System: Linux 5.1.0-9.4-liquorix-amd64 x86_64 Distribution: Ubuntu 19.04 -- Information about the crash: - What I was doing when the application crashed: Pasted the following line into an opened C++ (.h) file: [REM] #include "SomeHeader.h" The crash can be reproduced every time. -- Backtrace: Application: KDevelop (kdevelop), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". futex_wait_cancelable (private=, expected=0, futex_word=0x7ffcef106798) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 [Current thread is 1 (Thread 0x7f037b8e5e80 (LWP 26031))] Thread 16 (Thread 0x7f032e7fc700 (LWP 26076)): [KCrash Handler] #6 0x0c61 in () #7 0x7f0346af33c0 in () at /usr/lib/llvm-8/lib/libclang-8.so.1 #8 0x7f0346b02b42 in () at /usr/lib/llvm-8/lib/libclang-8.so.1 #9 0x7f033cc9a781 in llvm::CrashRecoveryContext::~CrashRecoveryContext() () at /usr/lib/llvm-8/lib/../lib/libLLVM-8.so.1 #10 0x7f034688cf38 in clang_parseTranslationUnit2FullArgv () at /usr/lib/llvm-8/lib/libclang-8.so.1 #11 0x7f034688cc1f in clang_parseTranslationUnit2 () at /usr/lib/llvm-8/lib/libclang-8.so.1 #12 0x7f034d4c9808 in ParseSessionData::ParseSessionData(QVector const&, ClangIndex*, ClangParsingEnvironment const&, QFlags) () at /usr/lib/x86_64-linux-gnu/libKDevClangPrivate.so.31 #13 0x7f034d5593c1 in () at /usr/lib/x86_64-linux-gnu/qt5/plugins/kdevplatform/31/kdevclangsupport.so #14 0x7f034d55b0e3 in () at /usr/lib/x86_64-linux-gnu/qt5/plugins/kdevplatform/31/kdevclangsupport.so #15 0x7f03838d74aa in ThreadWeaver::IdDecorator::run(QSharedPointer, ThreadWeaver::Thread*) () at /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #16 0x7f03838d7a18 in ThreadWeaver::Executor::run(QSharedPointer const&, ThreadWeaver::Thread*) () at /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #17 0x7f03838d6820 in ThreadWeaver::Job::execute(QSharedPointer const&, ThreadWeaver::Thread*) () at /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #18 0x7f03838d637b in ThreadWeaver::Thread::run() () at /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #19 0x7f0387256612 in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #20 0x7f03843b0182 in start_thread (arg=) at pthread_create.c:486 #21 0x7f0386ee7b1f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 15 (Thread 0x7f032effd700 (LWP 26075)): #0 0x7f03843b63bb in futex_wait_cancelable (private=, expected=0, futex_word=0x55caa321a630) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 0x7f03843b63bb in __pthread_cond_wait_common (abstime=0x0, mutex=0x55caa321a5e0, cond=0x55caa321a608) at pthread_cond_wait.c:502 #2 0x7f03843b63bb in __pthread_cond_wait (cond=0x55caa321a608, mutex=0x55caa321a5e0) at pthread_cond_wait.c:655 #3 0x7f038725c733 in QWaitCondition::wait(QMutex*, QDeadlineTimer) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7f038725c819 in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f03838d4680 in ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*, bool, bool, bool) () at /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #6 0x7f03838d81f8 in () at /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #7 0x7f03838d390d in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #8 0x7f03838d8252 in () at /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #9 0x7f03838d390d in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #10 0x7f03838d62c9 in ThreadWeaver::Thread::run() () at /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #11 0x7f0387256612 in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #12 0x7f03843b0182 in start_thread (arg=) at pthread_create.c:486 #13 0x7f0386ee7b1f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 14 (Thread 0x7f032f7fe700 (LWP 26074)): #0 0x7f03843b63bb in futex_wait_cancelable (private=, expected=0, futex_word=0x55caa321a630) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 0x7f03843b63bb in __pthread_cond_wait_common (abstime=0x0, mutex=0x55caa321a5e0, cond=0x55caa321a608) at pthread_cond_wait.c:502 #2 0x00
[kdevelop] [Bug 409027] New: KDevelop crashed when opening a file
https://bugs.kde.org/show_bug.cgi?id=409027 Bug ID: 409027 Summary: KDevelop crashed when opening a file Product: kdevelop Version: 5.3.2 Platform: Ubuntu Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdevelop-bugs-n...@kde.org Reporter: u...@ultr.pl Target Milestone: --- Application: kdevelop (5.3.2) Qt Version: 5.12.2 Frameworks Version: 5.59.0 Operating System: Linux 5.1.0-9.4-liquorix-amd64 x86_64 Distribution: Ubuntu 19.04 -- Information about the crash: - What I was doing when the application crashed: I was using 'Quick Open...' field to open a .h file. Crash happened when the file was being opened. The crash can be reproduced sometimes. -- Backtrace: Application: KDevelop (kdevelop), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". futex_wait_cancelable (private=, expected=0, futex_word=0x7ffecb11a638) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 [Current thread is 1 (Thread 0x7f391975ae80 (LWP 22659))] Thread 16 (Thread 0x7f38c992d700 (LWP 22704)): #0 0x7f39b3bb in futex_wait_cancelable (private=, expected=0, futex_word=0x556059cd4410) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 0x7f39b3bb in __pthread_cond_wait_common (abstime=0x0, mutex=0x556059cd43c0, cond=0x556059cd43e8) at pthread_cond_wait.c:502 #2 0x7f39b3bb in __pthread_cond_wait (cond=0x556059cd43e8, mutex=0x556059cd43c0) at pthread_cond_wait.c:655 #3 0x7f39250d1733 in QWaitCondition::wait(QMutex*, QDeadlineTimer) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7f39250d1819 in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f3921749680 in ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*, bool, bool, bool) () at /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #6 0x7f392174d1f8 in () at /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #7 0x7f392174890d in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #8 0x7f392174d252 in () at /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #9 0x7f392174890d in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #10 0x7f392174d252 in () at /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #11 0x7f392174890d in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #12 0x7f392174b2c9 in ThreadWeaver::Thread::run() () at /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #13 0x7f39250cb612 in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #14 0x7f395182 in start_thread (arg=) at pthread_create.c:486 #15 0x7f3924d5cb1f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 15 (Thread 0x7f38ca12e700 (LWP 22703)): [KCrash Handler] #6 0x0761 in () #7 0x7f38deaf33c0 in () at /usr/lib/llvm-8/lib/libclang-8.so.1 #8 0x7f38deb02b42 in () at /usr/lib/llvm-8/lib/libclang-8.so.1 #9 0x7f38db303781 in llvm::CrashRecoveryContext::~CrashRecoveryContext() () at /usr/lib/llvm-8/lib/../lib/libLLVM-8.so.1 #10 0x7f38de88cf38 in clang_parseTranslationUnit2FullArgv () at /usr/lib/llvm-8/lib/libclang-8.so.1 #11 0x7f38de88cc1f in clang_parseTranslationUnit2 () at /usr/lib/llvm-8/lib/libclang-8.so.1 #12 0x7f38ec7a4808 in ParseSessionData::ParseSessionData(QVector const&, ClangIndex*, ClangParsingEnvironment const&, QFlags) () at /usr/lib/x86_64-linux-gnu/libKDevClangPrivate.so.31 #13 0x7f38ec8343c1 in () at /usr/lib/x86_64-linux-gnu/qt5/plugins/kdevplatform/31/kdevclangsupport.so #14 0x7f38ec8360e3 in () at /usr/lib/x86_64-linux-gnu/qt5/plugins/kdevplatform/31/kdevclangsupport.so #15 0x7f392174c4aa in ThreadWeaver::IdDecorator::run(QSharedPointer, ThreadWeaver::Thread*) () at /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #16 0x7f392174ca18 in ThreadWeaver::Executor::run(QSharedPointer const&, ThreadWeaver::Thread*) () at /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #17 0x7f392174b820 in ThreadWeaver::Job::execute(QSharedPointer const&, ThreadWeaver::Thread*) () at /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #18 0x7f392174b37b in ThreadWeaver::Thread::run() () at /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #19 0x7f39250cb612 in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #20 0x7f395182 in start_thread (arg=) at pthread_create.c:486 #21 0x7f3924d5cb1f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 14 (Thread 0x7f38ca92f700 (LWP 22702)): #0 0x7f39b3bb in futex_wait_cancelable (private=, expected=0, futex_word=0x556059cd4
[konsole] [Bug 407317] Search box continues to show a match even after Clear Scrollback (and Reset)
https://bugs.kde.org/show_bug.cgi?id=407317 ultr changed: What|Removed |Added CC||u...@ultr.pl -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 407317] New: Search box continues to show a match even after Clear Scrollback (and Reset)
https://bugs.kde.org/show_bug.cgi?id=407317 Bug ID: 407317 Summary: Search box continues to show a match even after Clear Scrollback (and Reset) Product: konsole Version: 18.12.3 Platform: Kubuntu Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: history Assignee: konsole-de...@kde.org Reporter: u...@ultr.pl Target Milestone: --- SUMMARY Search box continues to show a match (green background) even after Clear Scrollback (and Reset) STEPS TO REPRODUCE 1. Search history for existing string 2. "Clear Scrollback" (or "Clear Scrollback and Reset") OBSERVED RESULT Search box is still green indicating there is a result found in current (cleared) view. EXPECTED RESULT Search box should become red indicating no result. (i.e. search should be re-run, and no result would be found) -- You are receiving this mail because: You are watching all bug changes.
[Plasma Vault] [Bug 388602] Add filemanager/dolphin intergration
https://bugs.kde.org/show_bug.cgi?id=388602 ultr changed: What|Removed |Added CC||u...@ultr.pl --- Comment #1 from ultr --- It would be great to have Vaults listed in the Places panel in Dolphin. With the ability to open/close them from there, and an indicator of their current state. -- You are receiving this mail because: You are watching all bug changes.
[Plasma Vault] [Bug 405529] Add support for kio-gdrive (Google Drive)?
https://bugs.kde.org/show_bug.cgi?id=405529 ultr changed: What|Removed |Added CC||u...@ultr.pl -- You are receiving this mail because: You are watching all bug changes.
[Plasma Vault] [Bug 405529] New: Add support for kio-gdrive (Google Drive)?
https://bugs.kde.org/show_bug.cgi?id=405529 Bug ID: 405529 Summary: Add support for kio-gdrive (Google Drive)? Product: Plasma Vault Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: ivan.cu...@kde.org Reporter: u...@ultr.pl Target Milestone: --- It would be a great feature of Plasma Vault to allow user enter a Google Drive (kio-gdrive) path, e.g.: "gdrive:/mys...@gmail.com/" as the device path for the Vault. Currently the Vault GUI always says that the given directory is not empty. -- You are receiving this mail because: You are watching all bug changes.
[Plasma Vault] [Bug 405527] No operation on Vault works when device path contains a symbolic link
https://bugs.kde.org/show_bug.cgi?id=405527 ultr changed: What|Removed |Added CC||u...@ultr.pl -- You are receiving this mail because: You are watching all bug changes.
[Plasma Vault] [Bug 405525] [DBUS] add newVault() and importVault() methods which take all needed parameters from DBUS call
https://bugs.kde.org/show_bug.cgi?id=405525 ultr changed: What|Removed |Added CC||u...@ultr.pl -- You are receiving this mail because: You are watching all bug changes.
[Plasma Vault] [Bug 405527] New: No operation on Vault works when device path contains a symbolic link
https://bugs.kde.org/show_bug.cgi?id=405527 Bug ID: 405527 Summary: No operation on Vault works when device path contains a symbolic link Product: Plasma Vault Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: ivan.cu...@kde.org Reporter: u...@ultr.pl Target Milestone: --- SUMMARY No operation on Vault (mount, umount, settings, removal) works when device path contains a symbolic link. STEPS TO REPRODUCE 1. Create a new Vault 2. Enter some name 3. Enter a password 4. For encrypted data location enter a path that contains a directory which is a symlink (!) 5. For mounting point enter any directory (this works fine with symlinks) 6. Confirm creation of the new Vault OBSERVED RESULT Try using tray Vault interface to operate on the newly created vault - all actions will fail. Also operations executed via DBUS calls fail. EXPECTED RESULT Vaults with symlinks in their device paths should work. SOFTWARE/OS VERSIONS Operating System: Ubuntu 18.10 KDE Plasma Version: 5.15.3 KDE Frameworks Version: 5.54.0 Qt Version: 5.11.1 -- You are receiving this mail because: You are watching all bug changes.
[Plasma Vault] [Bug 405525] New: [DBUS] add newVault() and importVault() methods which take all needed parameters from DBUS call
https://bugs.kde.org/show_bug.cgi?id=405525 Bug ID: 405525 Summary: [DBUS] add newVault() and importVault() methods which take all needed parameters from DBUS call Product: Plasma Vault Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: ivan.cu...@kde.org Reporter: u...@ultr.pl Target Milestone: --- DBUS kded interface: Add newVault() and importVault() methods, which take all needed parameters from DBUS call. There should be a possibility to pass an empty string for default option, eg. encryption engine = CryFS when not specified. newVault() only shows a password window to collect the new password from user. Or (optionally) it can take password from DBUS call as well (would that be safe?) -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 400170] KWin crashed when using the Slide effect and Alt+F2 shortcut
https://bugs.kde.org/show_bug.cgi?id=400170 --- Comment #11 from ultr --- > Happens only with Glide effect. > Could not reproduce with Fade or no effect. I meant: > Happens only with "Slide" effect. > Could not reproduce with "Fade Desktop" or no [desktop switching] effect. As for "Glide", "Fade" and "Scale" window effects: The issue is reproducible always no matter of the combination of these three. (depends only on the state of the desktop switching "Slide" effect) -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 400170] KWin crashed when using the Slide effect and Alt+F2 shortcut
https://bugs.kde.org/show_bug.cgi?id=400170 ultr changed: What|Removed |Added Status|NEEDSINFO |REPORTED Resolution|WAITINGFORINFO |--- --- Comment #9 from ultr --- Happens only with Glide effect. Could not reproduce with Fade or no effect. No windows need to be present on any virtual desktop. Press Alt+1, Alt+2, Alt+F2 fast randomly. (I use reassigned shortcuts for desktops from Ctrl+Fn to Alt+n, that's probably why it was easy for me to trigger this by accident) -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 400170] KWin crashed when using the Slide effect and Alt+F2 shortcut
https://bugs.kde.org/show_bug.cgi?id=400170 ultr changed: What|Removed |Added Status|RESOLVED|REPORTED Resolution|WORKSFORME |--- --- Comment #6 from ultr --- Still reproducible in KWin 5.14.2. Reopening. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 400170] KWin crashed when using the Slide effect and Alt+F2 shortcut
https://bugs.kde.org/show_bug.cgi?id=400170 ultr changed: What|Removed |Added Version|5.14.1 |5.14.2 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 400170] KWin crashed when using the Slide effect and Alt+F2 shortcut
https://bugs.kde.org/show_bug.cgi?id=400170 ultr changed: What|Removed |Added CC||u...@ultr.pl -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 400170] KWin crashed when using the Slide effect and Alt+F2 shortcut
https://bugs.kde.org/show_bug.cgi?id=400170 --- Comment #5 from ultr --- Created attachment 116032 --> https://bugs.kde.org/attachment.cgi?id=116032&action=edit New crash information added by DrKonqi kwin_x11 (5.14.2) using Qt 5.11.1 - What I was doing when the application crashed: Pressing shortcuts for switching virtual desktops (1,2,3,4) and Alt+F2 for running a command fast. -- Backtrace (Reduced): #6 __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50 #7 0x7f01e18a0535 in __GI_abort () at abort.c:79 #8 0x7f01e18a040f in __assert_fail_base (fmt=0x7f01d44cc27a "%s%s%s:%u: %s%sWarunek zapewnienia `%s' nie zosta\305\202 spe\305\202niony.\n%n", assertion=0x7f01e17e3b4c "delete_refcount == 0", file=0x7f01e17e3b98 "/build/kwin-dKqRUG/kwin-5.14.2/deleted.cpp", line=56, function=) at assert.c:92 #9 0x7f01e18b0142 in __GI___assert_fail (assertion=0x7f01e17e3b4c "delete_refcount == 0", file=0x7f01e17e3b98 "/build/kwin-dKqRUG/kwin-5.14.2/deleted.cpp", line=56, function=0x7f01e17e3c40 "virtual KWin::Deleted::~Deleted()") at assert.c:101 #10 0x7f01e16fed92 in KWin::Deleted::~Deleted() () from /usr/lib/x86_64-linux-gnu/libkwin.so.5 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 400170] KWin crashed when using the Slide effect and Alt+F2 shortcut
https://bugs.kde.org/show_bug.cgi?id=400170 --- Comment #3 from ultr --- I updated KWin from 5.14.1 to 5.14.2, and I can no longer reproduce this issue. If it happens again, I will report it here. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 400170] KWin crashed when using the Slide effect and Alt+F2 shortcut
https://bugs.kde.org/show_bug.cgi?id=400170 ultr changed: What|Removed |Added Resolution|WAITINGFORINFO |--- Status|NEEDSINFO |REPORTED --- Comment #2 from ultr --- @Vlad Zagorodniy > qdbus org.kde.KWin /KWin supportInformation == Version === KWin version: 5.14.2 Qt Version: 5.11.1 Qt compile version: 5.11.1 XCB compile version: 1.13.1 Operation Mode: X11 only Build Options = KWIN_BUILD_DECORATIONS: yes KWIN_BUILD_TABBOX: yes KWIN_BUILD_ACTIVITIES: yes HAVE_DRM: yes HAVE_GBM: yes HAVE_X11_XCB: yes HAVE_EPOXY_GLX: yes HAVE_WAYLAND_EGL: yes X11 === Vendor: The X.Org Foundation Vendor Release: 12001000 Protocol Version/Revision: 11/0 SHAPE: yes; Version: 0x11 RANDR: yes; Version: 0x14 DAMAGE: yes; Version: 0x11 Composite: yes; Version: 0x4 RENDER: yes; Version: 0xb XFIXES: yes; Version: 0x50 SYNC: yes; Version: 0x31 GLX: yes; Version: 0x0 Decoration == Plugin: org.kde.breeze Theme: Blur: 0 onAllDesktopsAvailable: true alphaChannelSupported: true closeOnDoubleClickOnMenu: false decorationButtonsLeft: 0, 9, 8, 2 decorationButtonsRight: 7, 3, 4, 5 borderSize: 0 gridUnit: 10 font: Ubuntu,10,-1,5,75,0,0,0,0,0,Bold smallSpacing: 2 largeSpacing: 10 Platform == Name: KWin::X11StandalonePlatform Options === focusPolicy: 0 nextFocusPrefersMouse: false clickRaise: true autoRaise: false autoRaiseInterval: 0 delayFocusInterval: 0 shadeHover: false shadeHoverInterval: 250 separateScreenFocus: false placement: 4 focusPolicyIsReasonable: true borderSnapZone: 10 windowSnapZone: 10 centerSnapZone: 0 snapOnlyWhenOverlapping: false rollOverDesktops: false focusStealingPreventionLevel: 1 legacyFullscreenSupport: false operationTitlebarDblClick: 5000 operationMaxButtonLeftClick: 5000 operationMaxButtonMiddleClick: 5015 operationMaxButtonRightClick: 5014 commandActiveTitlebar1: 0 commandActiveTitlebar2: 30 commandActiveTitlebar3: 2 commandInactiveTitlebar1: 4 commandInactiveTitlebar2: 30 commandInactiveTitlebar3: 2 commandWindow1: 7 commandWindow2: 8 commandWindow3: 8 commandWindowWheel: 31 commandAll1: 10 commandAll2: 3 commandAll3: 14 keyCmdAllModKey: 16777251 showGeometryTip: false condensedTitle: false electricBorderMaximize: true electricBorderTiling: true electricBorderCornerRatio: 0.25 borderlessMaximizedWindows: false killPingTimeout: 5000 hideUtilityWindowsForInactive: true inactiveTabsSkipTaskbar: false autogroupSimilarWindows: false autogroupInForeground: true compositingMode: 1 useCompositing: true compositingInitialized: true hiddenPreviews: 1 glSmoothScale: 2 xrenderSmoothScale: false maxFpsInterval: 1666 refreshRate: 0 vBlankTime: 600 glStrictBinding: false glStrictBindingFollowsDriver: true glCoreProfile: false glPreferBufferSwap: 0 glPlatformInterface: 1 windowsBlockCompositing: true Screen Edges desktopSwitching: false desktopSwitchingMovingClients: false cursorPushBackDistance: 1x1 timeThreshold: 150 reActivateThreshold: 350 actionTopLeft: 0 actionTop: 0 actionTopRight: 0 actionRight: 0 actionBottomRight: 0 actionBottom: 0 actionBottomLeft: 0 actionLeft: 0 Screens === Multi-Head: no Active screen follows mouse: no Number of Screens: 1 Screen 0: - Name: DVI-D-0 Geometry: 0,0,1920x1080 Scale: 1 Refresh Rate: 59.9339 Compositing === Compositing is active Compositing Type: OpenGL OpenGL vendor string: NVIDIA Corporation OpenGL renderer string: GeForce GTX 970/PCIe/SSE2 OpenGL version string: 4.6.0 NVIDIA 390.87 OpenGL platform interface: GLX OpenGL shading language version string: 4.60 NVIDIA Driver: NVIDIA Driver version: 390.87 GPU class: Unknown OpenGL version: 4.6 GLSL version: 4.60 X server version: 1.20.1 Linux kernel version: 4.18 Direct rendering: Requires strict binding: no GLSL shaders: yes Texture NPOT support: yes Virtual Machine: no OpenGL 2 Shaders are used Painting blocks for vertical retrace: no Loaded Effects: --- zoom kwin4_effect_frozenapp kwin4_effect_fade kwin4_effect_translucency kwin4_effect_logout kwin4_effect_maximize kwin4_effect_morphingpopups kwin4_effect_dialogparent slidingpopups slideback slide screenshot magiclamp glide flipswitch desktopgrid coverswitch colorpicker wobblywindows presentwindows highlightwindow blur startupfeedback screenedge kscreen Currently Active Effects: - blur Effect Settings: zoom: zoomFactor: 1.2 mousePointer: 0 mouseTracking: 0 enableFocusTracking: false followFocus: true focusDelay: 350 moveFactor: 20 targetZoom: 1 kwin4_effect_frozenapp: kwin4_effect_fade: kwin4_effect_translucency: kwin4_effect_logout: kwin4_effect_maximize: kwin4_effect_morphingpopups: kwin4_effect_dialogparent: slidingpopups: slideInDuration: 150 slideOutDuration: 250 slideback: slide: duration: 150 horizontalGap: 0 verticalGap
[kwin] [Bug 400170] New: KWin crashed when using the Slide effect and Alt+F2 shortcut
https://bugs.kde.org/show_bug.cgi?id=400170 Bug ID: 400170 Summary: KWin crashed when using the Slide effect and Alt+F2 shortcut Product: kwin Version: 5.14.1 Platform: Ubuntu Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kwin-bugs-n...@kde.org Reporter: u...@ultr.pl Target Milestone: --- Application: kwin_x11 (5.14.1) Qt Version: 5.11.1 Frameworks Version: 5.51.0 Operating System: Linux 4.18.0-15.1-liquorix-amd64 x86_64 Distribution: Ubuntu 18.10 -- Information about the crash: - What I was doing when the application crashed: I was switching desktops with the Slide virtual desktop effect by pressing a global shortcut for Desktop 2. Before the Slide animation finished I pressed Alt+F2 to run a command. - Effect: KWin crashed and restarted. -- Backtrace: Application: KWin (kwin_x11), signal: Aborted Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f3127d01840 (LWP 4285))] Thread 6 (Thread 0x7f311700 (LWP 7264)): #0 0x7f31322f37d6 in __GI_ppoll (fds=0x7f3114001138, nfds=1, timeout=, sigmask=0x0) at ../sysdeps/unix/sysv/linux/ppoll.c:39 #1 0x7f3130eb7141 in qt_safe_poll(pollfd*, unsigned long, timespec const*) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #2 0x7f3130eb85b9 in QEventDispatcherUNIX::processEvents(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #3 0x7f3130e6816b in QEventLoop::exec(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7f3130cb70b6 in QThread::exec() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f3130cc0c87 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7f312fac4164 in start_thread (arg=) at pthread_create.c:486 #7 0x7f31322ffdef in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 5 (Thread 0x7f311ca39700 (LWP 4481)): #0 futex_wait_cancelable (private=, expected=0, futex_word=0x7f31308a7fb8) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 __pthread_cond_wait_common (abstime=0x0, mutex=0x7f31308a7f68, cond=0x7f31308a7f90) at pthread_cond_wait.c:502 #2 __pthread_cond_wait (cond=0x7f31308a7f90, mutex=0x7f31308a7f68) at pthread_cond_wait.c:655 #3 0x7f31307b0e2a in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Script.so.5 #4 0x7f31307b0e49 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Script.so.5 #5 0x7f312fac4164 in start_thread (arg=) at pthread_create.c:486 #6 0x7f31322ffdef in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 4 (Thread 0x7f311f7fe700 (LWP 4453)): #0 0x7f31322f37d6 in __GI_ppoll (fds=0x7f310c000d28, nfds=1, timeout=, sigmask=0x0) at ../sysdeps/unix/sysv/linux/ppoll.c:39 #1 0x7f3130eb7141 in qt_safe_poll(pollfd*, unsigned long, timespec const*) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #2 0x7f3130eb85b9 in QEventDispatcherUNIX::processEvents(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #3 0x7f3130e6816b in QEventLoop::exec(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7f3130cb70b6 in QThread::exec() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f312f2f41f5 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5 #6 0x7f3130cc0c87 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7f312fac4164 in start_thread (arg=) at pthread_create.c:486 #8 0x7f31322ffdef in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 3 (Thread 0x7f3125baa700 (LWP 4317)): #0 0x7f31322f37d6 in __GI_ppoll (fds=0x7f311800e818, nfds=1, timeout=, sigmask=0x0) at ../sysdeps/unix/sysv/linux/ppoll.c:39 #1 0x7f3130eb7141 in qt_safe_poll(pollfd*, unsigned long, timespec const*) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #2 0x7f3130eb85b9 in QEventDispatcherUNIX::processEvents(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #3 0x7f3130e6816b in QEventLoop::exec(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7f3130cb70b6 in QThread::exec() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f312edd8545 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5 #6 0x7f3130cc0c87 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7f312fac4164 in start_thread (arg=) at pthread_create.c:486 #8 0x7f31322ffdef in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 2 (Thread 0x7f3126ed0700 (LWP 4309)): #0 0x7f31322f36d9 in __GI___poll (fds=0x7f3126ecfc78, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7f3130be0917 in ?? () from /usr/lib/x86_64-linux-gnu/libxcb.so.1 #2 0x7f3130be253a in xcb_wait_for_event () from /usr/lib/x86_64-linux-gnu/libxcb.so.1 #3 0x7f31273b2159 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5XcbQpa.so.5 #
[kwin] [Bug 384390] KWin crashed during logon
https://bugs.kde.org/show_bug.cgi?id=384390 ultr changed: What|Removed |Added CC||u...@ultr.pl -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 384390] New: KWin crashed during logon
https://bugs.kde.org/show_bug.cgi?id=384390 Bug ID: 384390 Summary: KWin crashed during logon Product: kwin Version: 5.10.5 Platform: Ubuntu Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kwin-bugs-n...@kde.org Reporter: u...@ultr.pl Target Milestone: --- Application: kwin_x11 (5.10.5) Qt Version: 5.7.1 Frameworks Version: 5.37.0 Operating System: Linux 4.10.0-33-generic x86_64 Distribution: Ubuntu 17.04 -- Information about the crash: - What I was doing when the application crashed: Logon from SDDM to KDE Plasma session. Instead of the desktop, the crash window for KWin appeared. Plasma and KWin (re)started automatically soon after. The crash does not seem to be reproducible. -- Backtrace: Application: KWin (kwin_x11), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 [Current thread is 1 (Thread 0x7f0686a95580 (LWP 2064))] Thread 7 (Thread 0x7f064f7fe700 (LWP 2464)): #0 0x7f067fba0510 in pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7f0682ecc2c4 in () at /usr/lib/x86_64-linux-gnu/libQt5Script.so.5 #2 0x7f0682ecc309 in () at /usr/lib/x86_64-linux-gnu/libQt5Script.so.5 #3 0x7f067fb9a6da in start_thread (arg=0x7f064f7fe700) at pthread_create.c:456 #4 0x7f06864ced7f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:105 Thread 6 (Thread 0x7f064700 (LWP 2458)): #0 0x7f067fba08b9 in pthread_cond_timedwait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_timedwait.S:225 #1 0x7f0683b4da26 in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #2 0x7f0683b49252 in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #3 0x7f0683b4cc38 in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7f067fb9a6da in start_thread (arg=0x7f064700) at pthread_create.c:456 #5 0x7f06864ced7f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:105 Thread 5 (Thread 0x7f065dded700 (LWP 2206)): [KCrash Handler] #6 0x7f0683cae973 in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7f0683c4b766 in QLockFile::tryLock(int) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7f0685829389 in () at /usr/lib/x86_64-linux-gnu/libKF5ConfigCore.so.5 #9 0x7f0685813180 in KConfig::sync() () at /usr/lib/x86_64-linux-gnu/libKF5ConfigCore.so.5 #10 0x7f0664f54175 in () at /usr/lib/x86_64-linux-gnu/qt5/plugins/org.kde.kwin.platforms/KWinX11Platform.so #11 0x7f0683d47afe in QMetaObject::activate(QObject*, int, int, void**) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #12 0x7f0683d54058 in QTimer::timerEvent(QTimerEvent*) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #13 0x7f0683d485f3 in QObject::event(QEvent*) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #14 0x7f06849f235c in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #15 0x7f06849f9b21 in QApplication::notify(QObject*, QEvent*) () at /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #16 0x7f0683d1bc00 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #17 0x7f0683d6f03e in QTimerInfoList::activateTimers() () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #18 0x7f0683d6cf4a in QEventDispatcherUNIX::processEvents(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #19 0x7f0683d19bea in QEventLoop::exec(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #20 0x7f0683b47f83 in QThread::exec() () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #21 0x7f0683b4cc38 in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #22 0x7f067fb9a6da in start_thread (arg=0x7f065dded700) at pthread_create.c:456 #23 0x7f06864ced7f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:105 Thread 4 (Thread 0x7f065edee700 (LWP 2199)): #0 0x7f06864c2e51 in __GI_ppoll (fds=0x7f065ac8, nfds=1, timeout=, sigmask=0x0) at ../sysdeps/unix/sysv/linux/ppoll.c:39 #1 0x7f0683d6b3e1 in qt_safe_poll(pollfd*, unsigned long, timespec const*) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #2 0x7f0683d6ccda in QEventDispatcherUNIX::processEvents(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #3 0x7f0683d19bea in QEventLoop::exec(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7f0683b47f83 in QThread::exec() () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f067e907df5 in () at /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5 #6 0x7f0683b4cc38 in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7f067fb9a6da in start_thread (arg=0x
[konqueror] [Bug 289000] Konqueror's Places menu insisting on showing all entries
https://bugs.kde.org/show_bug.cgi?id=289000 --- Comment #1 from ultr --- This issue still occurs in Konqueror 4.14.2. And is really annoying. Is there any chance of having it fixed in the 4.x series? Great number of stable Linux distros use it. Thank you. -- You are receiving this mail because: You are watching all bug changes.
[konqueror] [Bug 289000] Konqueror's Places menu insisting on showing all entries
https://bugs.kde.org/show_bug.cgi?id=289000 ultr changed: What|Removed |Added CC||u...@ultr.pl -- You are receiving this mail because: You are watching all bug changes.
[ark] [Bug 252420] ark --forcesubfolder parameter and "Extract into a subfolder" service menu item
https://bugs.kde.org/show_bug.cgi?id=252420 --- Comment #12 from ultr --- > How about a global option like "Always use the archive name as subfolder > name"? Personally I'm OK with such solution. If only it does not confuse users even more :) -- You are receiving this mail because: You are watching all bug changes.
[ark] [Bug 252420] ark --forcesubfolder parameter and "Extract into a subfolder" service menu item
https://bugs.kde.org/show_bug.cgi?id=252420 --- Comment #10 from ultr --- > Extract archive To... [...] This requires a lot more work than simply clicking the menu item. And does not allow selecting several archives at once for extracting. Plus the 'Extract Into a Subfolder' option is safest if you don't know the structure of your archives you are about to extract. So I think it should be easily accessible from the service menu. Otherwise the user is left with this limited set of predefined quick actions none of which is really safe for the data in such cases. Whichever action is selected the user may end up having to reject many overwrite alerts, cancel all the extractions, delete the already extracted data and start over manually extracting archives one by one. Doesn't sound like a user friendly approach. -- You are receiving this mail because: You are watching all bug changes.
[ark] [Bug 252420] ark --forcesubfolder parameter and "Extract into a subfolder" service menu item
https://bugs.kde.org/show_bug.cgi?id=252420 --- Comment #8 from ultr --- Created attachment 96471 --> https://bugs.kde.org/attachment.cgi?id=96471&action=edit ark-extract-menu.png -- You are receiving this mail because: You are watching all bug changes.
[ark] [Bug 252420] ark --forcesubfolder parameter and "Extract into a subfolder" service menu item
https://bugs.kde.org/show_bug.cgi?id=252420 --- Comment #7 from ultr --- Created attachment 96470 --> https://bugs.kde.org/attachment.cgi?id=96470&action=edit mycode-v2.tar.gz -- You are receiving this mail because: You are watching all bug changes.
[ark] [Bug 252420] ark --forcesubfolder parameter and "Extract into a subfolder" service menu item
https://bugs.kde.org/show_bug.cgi?id=252420 --- Comment #6 from ultr --- Created attachment 96469 --> https://bugs.kde.org/attachment.cgi?id=96469&action=edit mycode-v1.tar.gz -- You are receiving this mail because: You are watching all bug changes.
[ark] [Bug 252420] ark --forcesubfolder parameter and "Extract into a subfolder" service menu item
https://bugs.kde.org/show_bug.cgi?id=252420 --- Comment #5 from ultr --- I have checked this with Ark 15.08.3 and Plasma 5.4.3 and it still does not work. Both service menu options for fast extraction: - 'Extract Archive Here, Autodetect Subfolder' and - 'Extract Archive Here' try to overwrite files when extracting both attached archives. Extracting first archive creates this directory tree: - mycode - - a.c - - a.h Extracting the other archive tries to overwrite it. This is OK, but there is no option to 'Extract Into a Subfolder', so that the directory tree would look like that: - mycode-v1 (named after the archive file name) - - mycode - - - a.c - - - a.h - mycode-v2 (named after the archive file name) - - mycode - - - a.c - - - a.h Without the ark's --forcesubfolder parameter it is not even possible to create the 'Extract Into a Subfolder' service menu item. -- You are receiving this mail because: You are watching all bug changes.
