[konsole] [Bug 374887] konsole crashed while rearranging tabs
https://bugs.kde.org/show_bug.cgi?id=374887 --- Comment #4 from John Florian --- I only have 20.04.1 (via Fedora 32). It's become extremely rare to have a konsole crash. That said, I had one last week although I can't tell you what I was doing or if it was 20.04.1 for certain. Often when I lose so many open shells and thought trains, I decide that's as good as any time to shut everything down, apply updates and find my way back. I should just logout everyday to minimize my context but I've never been very good at putting my toys away. :-) -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 344599] Thumbnails sidebar always open when okular starts
https://bugs.kde.org/show_bug.cgi?id=344599 John Florian <k...@doubledog.org> changed: What|Removed |Added CC||k...@doubledog.org --- Comment #8 from John Florian <k...@doubledog.org> --- I too find the default behavior a minor annoyance. I rarely work with PDFs that are but more than a few pages so the navigation panel is just wasted real estate for me. I'd much prefer to enable it when needed rather than almost always closing it. Can we expect a new configuration option for this any time soon? -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 386264] New: enabling regex search after entering pattern fails to find matches until pattern is edited further
https://bugs.kde.org/show_bug.cgi?id=386264 Bug ID: 386264 Summary: enabling regex search after entering pattern fails to find matches until pattern is edited further Product: konsole Version: 17.04.1 Platform: Fedora RPMs OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: history Assignee: konsole-de...@kde.org Reporter: k...@doubledog.org Target Milestone: --- In konsole, I had a search set up for `history` (which had matches), I then wanted to also find matches for `timing`, so I changed the pattern to `history|timing` but found no matches. I then checked the options where I had assumed regex was already enabled, but it wasn't. So, I toggled that option on and still didn't find any matches -- oops, bug! I then deleted the last letter of my pattern and added it back on and then I had matches -- and a work-around. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 374887] New: konsole crashed while rearranging tabs
https://bugs.kde.org/show_bug.cgi?id=374887 Bug ID: 374887 Summary: konsole crashed while rearranging tabs Product: konsole Version: 16.08.3 Platform: Fedora RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: konsole-de...@kde.org Reporter: k...@doubledog.org Target Milestone: --- Application: konsole (16.08.3) Qt Version: 5.7.1 Frameworks Version: 5.29.0 Operating System: Linux 4.8.15-300.fc25.x86_64 x86_64 Distribution (Platform): Fedora RPMs -- Information about the crash: - What I was doing when the application crashed: I meant to swap two konsole tabs and acidentally detached instead. So I re-attached the tab. However, when I went to rearrange them as per my original wish, kaboom. I really hate the single PID konsole. When it crashes its an awful user experience causing so much lost work and context. -- Backtrace: Application: Konsole (konsole), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f7b66db9dc0 (LWP 2663))] Thread 3 (Thread 0x7f7b45274700 (LWP 2665)): #0 0x7f7b60f9001d in poll () from /lib64/libc.so.6 #1 0x7f7b5a3ab156 in g_main_context_iterate.isra () from /lib64/libglib-2.0.so.0 #2 0x7f7b5a3ab26c in g_main_context_iteration () from /lib64/libglib-2.0.so.0 #3 0x7f7b61d9673b in QEventDispatcherGlib::processEvents(QFlags) () from /lib64/libQt5Core.so.5 #4 0x7f7b61d4773a in QEventLoop::exec(QFlags) () from /lib64/libQt5Core.so.5 #5 0x7f7b61ba45f3 in QThread::exec() () from /lib64/libQt5Core.so.5 #6 0x7f7b66e5e739 in QDBusConnectionManager::run() () from /lib64/libQt5DBus.so.5 #7 0x7f7b61ba89da in QThreadPrivate::start(void*) () from /lib64/libQt5Core.so.5 #8 0x7f7b5f6e1754 in ?? () from /usr/lib64/nvidia-304xx/libGL.so.1 #9 0x7f7b5f95b6ca in start_thread () from /lib64/libpthread.so.0 #10 0x7f7b60f9bf7f in clone () from /lib64/libc.so.6 Thread 2 (Thread 0x7f7b46de3700 (LWP 2664)): #0 0x7f7b60f9001d in poll () from /lib64/libc.so.6 #1 0x7f7b5e994d10 in _xcb_conn_wait () from /lib64/libxcb.so.1 #2 0x7f7b5e996aa9 in xcb_wait_for_event () from /lib64/libxcb.so.1 #3 0x7f7b4bac1d69 in QXcbEventReader::run() () from /lib64/libQt5XcbQpa.so.5 #4 0x7f7b61ba89da in QThreadPrivate::start(void*) () from /lib64/libQt5Core.so.5 #5 0x7f7b5f6e1754 in ?? () from /usr/lib64/nvidia-304xx/libGL.so.1 #6 0x7f7b5f95b6ca in start_thread () from /lib64/libpthread.so.0 #7 0x7f7b60f9bf7f in clone () from /lib64/libc.so.6 Thread 1 (Thread 0x7f7b66db9dc0 (LWP 2663)): [KCrash Handler] #6 0x7f7b66ee5226 in QDomNodePrivate::ownerDocument() () from /lib64/libQt5Xml.so.5 #7 0x7f7b66ee55cd in QDomNodePrivate::QDomNodePrivate(QDomNodePrivate*, bool) () from /lib64/libQt5Xml.so.5 #8 0x7f7b66ee57c5 in QDomTextPrivate::cloneNode(bool) () from /lib64/libQt5Xml.so.5 #9 0x7f7b66ee566e in QDomNodePrivate::QDomNodePrivate(QDomNodePrivate*, bool) () from /lib64/libQt5Xml.so.5 #10 0x7f7b66ee5775 in QDomAttrPrivate::cloneNode(bool) () from /lib64/libQt5Xml.so.5 #11 0x7f7b66eeda27 in QDomNamedNodeMapPrivate::clone(QDomNodePrivate*) () from /lib64/libQt5Xml.so.5 #12 0x7f7b66eeda7a in QDomElementPrivate::QDomElementPrivate(QDomElementPrivate*, bool) () from /lib64/libQt5Xml.so.5 #13 0x7f7b66eedab5 in QDomElementPrivate::cloneNode(bool) () from /lib64/libQt5Xml.so.5 #14 0x7f7b66ee566e in QDomNodePrivate::QDomNodePrivate(QDomNodePrivate*, bool) () from /lib64/libQt5Xml.so.5 #15 0x7f7b66eeda64 in QDomElementPrivate::QDomElementPrivate(QDomElementPrivate*, bool) () from /lib64/libQt5Xml.so.5 #16 0x7f7b66eedab5 in QDomElementPrivate::cloneNode(bool) () from /lib64/libQt5Xml.so.5 #17 0x7f7b66ee566e in QDomNodePrivate::QDomNodePrivate(QDomNodePrivate*, bool) () from /lib64/libQt5Xml.so.5 #18 0x7f7b66eeda64 in QDomElementPrivate::QDomElementPrivate(QDomElementPrivate*, bool) () from /lib64/libQt5Xml.so.5 #19 0x7f7b66eedab5 in QDomElementPrivate::cloneNode(bool) () from /lib64/libQt5Xml.so.5 #20 0x7f7b66ee566e in QDomNodePrivate::QDomNodePrivate(QDomNodePrivate*, bool) () from /lib64/libQt5Xml.so.5 #21 0x7f7b66ee9154 in QDomDocumentPrivate::QDomDocumentPrivate(QDomDocumentPrivate*, bool) () from /lib64/libQt5Xml.so.5 #22 0x7f7b66ee9225 in QDomDocumentPrivate::cloneNode(bool) () from /lib64/libQt5Xml.so.5 #23 0x7f7b66ee6235 in QDomNode::cloneNode(bool) const () from /lib64/libQt5Xml.so.5 #24 0x7f7b65f11aa6 in KXMLGUIFactory::removeClient(KXMLGUIClient*) () from /lib64/libKF5XmlGui.so.5 #25 0x7f7b66b60493 in Konsole::MainWindow::disconnectController(Konsole::SessionController*) () from /lib64/libkdeinit5_konsole.so #26 0x7f7b66b6301d in
[kwin] [Bug 367763] Usability request: delay or resistance for Active Screen Corners and Edges
https://bugs.kde.org/show_bug.cgi?id=367763 --- Comment #3 from John Florian <k...@doubledog.org> --- Er, no. Now I see that "Switch desktop on edge" (which I want disabled) is completely independent of "Activation delay" and "Reactivation delay". Above, I mistakenly assumed that this had to be enabled to effect the delays. Now I don't what to suggest as to how this could be made clearer. The grouping of those 3 "other settings" somehow made me believe delays were tied to the desktop switching. I'm feeling stupid now. :( UI/UX is hard!!! -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 367763] Usability request: delay or resistance for Active Screen Corners and Edges
https://bugs.kde.org/show_bug.cgi?id=367763 --- Comment #2 from John Florian <k...@doubledog.org> --- I, of course, already did that otherwise I wouldn't have filed this. However, I looked again and met the same result as before: there are delay settings, but for "switching desktops" and that's clearly not what I'm trying to do. However, knowing you who *you* are I poked further. :) Now that I've played with the Other Settings there and realized that this most obvious need has already been met, might I suggest that "Switch desktop on edge" is perhaps a bit misleading -- it certainly implied something else to me. My take was these delays are only applicable for switching from say desktop one to desktop two. I think a better label might be "Edge/corner activation", at least that's how I understand the behavior now. Anyways, thanks for the prompt response -- I've got what I needed. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 367763] New: Usability request: delay or resistance for Active Screen Corners and Edges
https://bugs.kde.org/show_bug.cgi?id=367763 Bug ID: 367763 Summary: Usability request: delay or resistance for Active Screen Corners and Edges Product: kwin Version: 5.7.3 Platform: Fedora RPMs OS: Linux Status: UNCONFIRMED Severity: wishlist Priority: NOR Component: core Assignee: kwin-bugs-n...@kde.org Reporter: k...@doubledog.org I find it too easy to activate the corners/edges feature when all I wanted was to access window controls in a window's title bar that just happens to be positioned at the top of the screen. A user-configurable delay would let me indicate that most often it's the window controls that I want, but with a bit of a wait I can get the corner/edge features instead. Even better would be a resistance that determines how hard I must press the pointer against an edge/corner, effectively how far past the point would go if it could. My use case might exaggerate the problem. I have four 1920x1200 screens arranged in a 4x1 configuration. This means the far left edge is a long distance from the far right edge as the mouse travel goes. Thus I have configured my pointer acceleration pretty aggressive which results in coarse movements and low accuracy until I get in the ballpark. I can easily activate the top edge controls even when I'm not aiming for window controls but just a mere hover over the window in general for focus change. Lowering the pointer acceleration isn't really an option because my keyboard tray has limited real estate so the mouse must work within an area roughly 3x3 inches. Reproducible: Always -- You are receiving this mail because: You are watching all bug changes.
