[dolphin] [Bug 474710] Dolphin crashes when reloading a directory that no longer exists
https://bugs.kde.org/show_bug.cgi?id=474710 Andrew M changed: What|Removed |Added CC||quantumpha...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 470966] New: Missing Close button for Memory Viewer Tool
https://bugs.kde.org/show_bug.cgi?id=470966 Bug ID: 470966 Summary: Missing Close button for Memory Viewer Tool Classification: Applications Product: kdevelop Version: 5.11.230401 Platform: Archlinux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: UI: general Assignee: kdevelop-bugs-n...@kde.org Reporter: quantumpha...@gmail.com Target Milestone: --- SUMMARY Memory viewer tabs in the Memory Viewer Tool cannot be closed. There is an area of the UI that holds a right click context menu with the option to close and configure some things but it disappears when activating [OK] or [Cancel]. STEPS TO REPRODUCE 1. Debug a C/C++ project where gdb works 2. Enable the Memory Viewer tool view if not enabled 3. Add a variable and length and click [OK] to display something (it can take variable names for "Start" and "Amount") 4. Click the "New Memory Viewer" button 5. Click [Cancel] 6. Click the "New Memory Viewer" button OBSERVED RESULT 1. Memory viewer tabs accumulate 2. You can only close a Memory View tab if you right click the blank area around the Start and Amount input, but that area is hidden once you click [OK] or [Cancel] EXPECTED RESULT 1. Close Tab next to the New Tab button 2. Some UI elements belonging to the tab to allow the user to change the memory range again, similar to the find in files tool in Kate. I don't know why the Start and Amount input need to disappear when finished SOFTWARE/OS VERSIONS Linux: 6.3.4-arch1-1 KDE Plasma Version: 5.27.5 KDE Frameworks Version: 5.106.0 Qt Version: 5.15.9 ADDITIONAL INFORMATION none -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 438874] Disk & Devices applet doesn't show USB removable devices after connecting the device for 2nd time
https://bugs.kde.org/show_bug.cgi?id=438874 Andrew M changed: What|Removed |Added CC||quantumpha...@gmail.com --- Comment #5 from Andrew M --- I am also experiencing this issue. Also on Arch Linux (plasma-desktop 5.22.1-1). Workaround: 1. Insert device 2. Run `kquitapp5 plasmashell; sleep 1; plasmashell` in KRunner (so that it isn't a child job in a terminal) 3. It should appear in "Disks & Devices" -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 430311] Intensive color selection broken as of 270d6ea3
https://bugs.kde.org/show_bug.cgi?id=430311 Andrew M changed: What|Removed |Added CC||quantumpha...@gmail.com --- Comment #5 from Andrew M --- Thanks. Reverting commit 270d6ea3 restores the previous colours for me. -- You are receiving this mail because: You are watching all bug changes.
[ksysguard] [Bug 428048] Ksysguard leaks memory when opened for a long time
https://bugs.kde.org/show_bug.cgi?id=428048 Andrew M changed: What|Removed |Added CC||cmhea...@charter.net --- Comment #22 from Andrew M --- *** Bug 424299 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[ksysguard] [Bug 424299] Excessive Memory Usage (Non-reproducible)
https://bugs.kde.org/show_bug.cgi?id=424299 Andrew M changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |DUPLICATE CC||quantumpha...@gmail.com --- Comment #1 from Andrew M --- *** This bug has been marked as a duplicate of bug 428048 *** -- You are receiving this mail because: You are watching all bug changes.
[kompare] [Bug 429178] New: Show Navigation missing from settings menu
https://bugs.kde.org/show_bug.cgi?id=429178 Bug ID: 429178 Summary: Show Navigation missing from settings menu Product: kompare Version: 4.1.3 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: navigationpart Assignee: kompare-de...@kde.org Reporter: quantumpha...@gmail.com Target Milestone: --- SUMMARY A "Show Navigation" menu entry to show/hide the Navigation panel is missing from the Settings menu. If someone accidentally closes the Navigation panel, they will not be able to find a way to bring it back in the most obvious place. STEPS TO REPRODUCE 1. Close the Navigation panel 2. Pretend to be grandma using the computer 3. Try to bring it back OBSERVED RESULT Settings [x] Show Toolbar [x] Show Statusbar [_] Show Text View EXPECTED RESULT Settings [x] Show Toolbar [x] Show Statusbar [x] Show Navigation [_] Show Text View WORKAROUND Luckily a non-obvious context menu that appears when right-clicking the menu bar or Text View panel bar (if visible) has a Navigation panel tick-box. -- You are receiving this mail because: You are watching all bug changes.
[ksysguard] [Bug 426792] ksysguard leaking some memory
https://bugs.kde.org/show_bug.cgi?id=426792 Andrew M changed: What|Removed |Added CC||quantumpha...@gmail.com --- Comment #2 from Andrew M --- Still a problem in 5.20.0 Also a problem for the systemmonitor (System Activity) spawned from Ctrl+Esc Leaving them both open overnight can lead to over 1 GiB of usage. Current usage after leaving it on overnight: ksysguard: 1.9 G systemmonitor: 1.4 G -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 425896] Kate toolbars appear and disappear
https://bugs.kde.org/show_bug.cgi?id=425896 Andrew M changed: What|Removed |Added CC||quantumpha...@gmail.com --- Comment #4 from Andrew M --- Fixed in bug 426605 of which this is a dupe of -- You are receiving this mail because: You are watching all bug changes.
[krfb] [Bug 313170] Allow selecting which X screen is active
https://bugs.kde.org/show_bug.cgi?id=313170 Andrew M changed: What|Removed |Added CC||quantumpha...@gmail.com --- Comment #3 from Andrew M --- (In reply to Andrew Crouthamel from comment #2) > This is a reminder that this bug has been stagnant for a long time. Could > you help us out and re-test if the bug is valid in the latest version? Yes this still is an issue. In my situation I have 3 monitors with one on the left in vertical orientation. Krfb will only use that left monitor with no way to configure with monitor to use. Extract from xrandr: DP-1 connected 1920x1080+1050+509 (normal left inverted right x axis y axis) 521mm x 293mm HDMI-1 connected primary 1050x1680+0+0 left (normal left inverted right x axis y axis) 474mm x 296mm DVI-D-1 connected 1920x1080+2970+509 (normal left inverted right x axis y axis) 520mm x 290mm For me it will only work with HDMI-1 (left hand), where I wanted to use it for the right hand DVI-D-1. Suggested behaviour: A combo box with all available monitors if greater than 1 which change the captured framebuffer region to that monitor. An optional advanced mode where the user can define a size and offset from top left (WxH+X+Y). Basically a way to do the equivalent of x11vnc's -clip option. -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 405461] New: Save dialog crashes when making 3 nested folders
https://bugs.kde.org/show_bug.cgi?id=405461 Bug ID: 405461 Summary: Save dialog crashes when making 3 nested folders Product: kate Version: 18.12.3 Platform: Neon Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kwrite-bugs-n...@kde.org Reporter: quantumpha...@gmail.com Target Milestone: --- Application: kate (18.12.3) Qt Version: 5.12.0 Frameworks Version: 5.56.0 Operating System: Linux 4.18.0-15-generic x86_64 Distribution: KDE neon User Edition 5.15 -- Information about the crash: - What I was doing when the application crashed: I was saving a new file to a buildroot rootfs overlay and needed to make a `rootfs_overlay/etc/init.d` directory. Furthur testing leads to it crashing when making new folder after new folder. - Steps to reproduce: 1. Open a new file in Kate 2. Save as 3. Navigate to `/tmp/` 4. New folder test1 5. New folder test2 6. New folder test3 7. Segfault The crash can be reproduced every time. -- Backtrace: Application: Kate (kate), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7fe616d0f840 (LWP 21241))] Thread 33 (Thread 0x7fe5677fe700 (LWP 8911)): #0 0x7fe6115d5bf9 in __GI___poll (fds=0x560c4e13e560, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7fe60b06a539 in () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7fe60b06a8d2 in g_main_loop_run () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7fe57cd2a026 in () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 #4 0x7fe60b092105 in () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7fe60cfee6db in start_thread (arg=0x7fe5677fe700) at pthread_create.c:463 #6 0x7fe6115e288f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 32 (Thread 0x7fe567fff700 (LWP 8910)): #0 0x7fe6115d10b4 in __GI___libc_read (fd=46, buf=0x7fe567ffeca0, nbytes=16) at ../sysdeps/unix/sysv/linux/read.c:27 #1 0x7fe60b0aecd0 in () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7fe60b06a027 in g_main_context_check () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7fe60b06a4e0 in () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7fe60b06a64c in g_main_context_iteration () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7fe60b06a691 in () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #6 0x7fe60b092105 in () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #7 0x7fe60cfee6db in start_thread (arg=0x7fe567fff700) at pthread_create.c:463 #8 0x7fe6115e288f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 31 (Thread 0x7fe57d7fa700 (LWP 30196)): #0 0x7fe60cff49f3 in futex_wait_cancelable (private=, expected=0, futex_word=0x560c4cbd0ea4) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 0x7fe60cff49f3 in __pthread_cond_wait_common (abstime=0x0, mutex=0x560c4cbd0e50, cond=0x560c4cbd0e78) at pthread_cond_wait.c:502 #2 0x7fe60cff49f3 in __pthread_cond_wait (cond=0x560c4cbd0e78, mutex=0x560c4cbd0e50) at pthread_cond_wait.c:655 #3 0x7fe611ce9b4b in QWaitCondition::wait(QMutex*, QDeadlineTimer) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7fe611ce9e59 in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7fe5ed7e6935 in ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*, bool, bool, bool) () at /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #6 0x7fe5ed7ea7e8 in () at /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #7 0x7fe5ed7e5bfd in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #8 0x7fe5ed7ea842 in () at /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #9 0x7fe5ed7e5bfd in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #10 0x7fe5ed7e86ab in ThreadWeaver::Thread::run() () at /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #11 0x7fe611ce2bc2 in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #12 0x7fe60cfee6db in start_thread (arg=0x7fe57d7fa700) at pthread_create.c:463 #13 0x7fe6115e288f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 30 (Thread 0x7fe57dffb700 (LWP 30195)): #0 0x7fe60cff49f3 in futex_wait_cancelable (private=, expected=0, futex_word=0x560c4cbd0ea4) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 0x7fe60cff49f3 in __pthread_cond_wait_common (abstime=0x0, mutex=0x560c4cbd0e50, cond=0x560c4cbd0e78) at pthread_cond_wait.c:502 #2 0x7fe60cff49f3 in __pthread_cond_wait (cond=0x560c4cbd0e78, mutex=0x560c4cbd0e50) at pthread_cond_wait.c:655 #3 0x7fe611ce9b4b in
[kdevelop] [Bug 397375] New: Kdevelop crash when closing a large project from last session at startup
https://bugs.kde.org/show_bug.cgi?id=397375 Bug ID: 397375 Summary: Kdevelop crash when closing a large project from last session at startup Product: kdevelop Version: 5.2.3 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdevelop-bugs-n...@kde.org Reporter: quantumpha...@gmail.com Target Milestone: --- Application: kdevelop (5.2.3) Qt Version: 5.11.1 Frameworks Version: 5.48.0 Operating System: Linux 4.17.11-arch1 x86_64 Distribution: "Arch Linux" -- Information about the crash: Kdevelop crashes when loading up a project from the previous session and then the user closes that project during on of the parsing phases. - What I was doing when the application crashed: So I had a previous session with 2 projects open: The Linux kernel and a small single main.c file test project. Opening Kdevelop I wanted to close the Linux project and leave the test project open. The test project appeared first in the projects pannel, then when the Linux project appeared I right clicked to close it before Kdevelop got stuck into parsing the billion files within. Closing it caused the crash. Crashed twice in a row doing the same operation. The crash can be reproduced sometimes. -- Backtrace: Application: KDevelop (kdevelop), signal: Segmentation fault Using host libthread_db library "/usr/lib/libthread_db.so.1". [Current thread is 1 (Thread 0x7fd462c37e00 (LWP 20706))] Thread 45 (Thread 0x7fd34d521700 (LWP 20900)): #0 0x7fd45f2a4934 in read () at /usr/lib/libc.so.6 #1 0x7fd455e78ed1 in () at /usr/lib/libglib-2.0.so.0 #2 0x7fd455e32ff8 in g_main_context_check () at /usr/lib/libglib-2.0.so.0 #3 0x7fd455e334c6 in () at /usr/lib/libglib-2.0.so.0 #4 0x7fd455e3363e in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #5 0x7fd45fbc5054 in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #6 0x7fd45fb7094c in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #7 0x7fd45f9b9a99 in QThread::exec() () at /usr/lib/libQt5Core.so.5 #8 0x7fd45d4dc3f6 in () at /usr/lib/libKDevPlatformLanguage.so.52 #9 0x7fd45f9c3b45 in () at /usr/lib/libQt5Core.so.5 #10 0x7fd458a15075 in start_thread () at /usr/lib/libpthread.so.0 #11 0x7fd45f2b353f in clone () at /usr/lib/libc.so.6 Thread 44 (Thread 0x7fd387fff700 (LWP 20898)): #0 0x7fd458a1affc in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7fd45f9c42fc in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/libQt5Core.so.5 #2 0x7fd454421139 in ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*, bool, bool, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #3 0x7fd454425009 in () at /usr/lib/libKF5ThreadWeaver.so.5 #4 0x7fd4544201fd in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #5 0x7fd454423059 in ThreadWeaver::Thread::run() () at /usr/lib/libKF5ThreadWeaver.so.5 #6 0x7fd45f9c3b45 in () at /usr/lib/libQt5Core.so.5 #7 0x7fd458a15075 in start_thread () at /usr/lib/libpthread.so.0 #8 0x7fd45f2b353f in clone () at /usr/lib/libc.so.6 Thread 43 (Thread 0x7fd38cff9700 (LWP 20897)): #0 0x7fd458a1affc in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7fd45f9c42fc in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/libQt5Core.so.5 #2 0x7fd454421139 in ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*, bool, bool, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #3 0x7fd454425009 in () at /usr/lib/libKF5ThreadWeaver.so.5 #4 0x7fd4544201fd in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #5 0x7fd454423059 in ThreadWeaver::Thread::run() () at /usr/lib/libKF5ThreadWeaver.so.5 #6 0x7fd45f9c3b45 in () at /usr/lib/libQt5Core.so.5 #7 0x7fd458a15075 in start_thread () at /usr/lib/libpthread.so.0 #8 0x7fd45f2b353f in clone () at /usr/lib/libc.so.6 Thread 42 (Thread 0x7fd38d7fa700 (LWP 20896)): #0 0x7fd458a1affc in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7fd45f9c42fc in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/libQt5Core.so.5 #2 0x7fd454421139 in ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*, bool, bool, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #3 0x7fd454425009 in () at /usr/lib/libKF5ThreadWeaver.so.5 #4 0x7fd4544201fd in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #5 0x7fd454423059 in ThreadWeaver::Thread::run() () at /usr/lib/libKF5ThreadWeaver.so.5 #6 0x7fd45f9c3b45 in
[plasmashell] [Bug 395362] New: Plasma in Wayland session crashes occasionally on login
https://bugs.kde.org/show_bug.cgi?id=395362 Bug ID: 395362 Summary: Plasma in Wayland session crashes occasionally on login Product: plasmashell Version: 5.12.5 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: quantumpha...@gmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 Application: plasmashell (5.12.5) Qt Version: 5.11.0 Frameworks Version: 5.47.0 Operating System: Linux 4.16.13-2-ARCH x86_64 Distribution: "Arch Linux" -- Information about the crash: When starting a Plasma Wayland session it sometimes crashes. - Custom settings of the application: using nouveau drivers The crash can be reproduced sometimes. -- Backtrace: Application: Plasma (plasmashell), signal: Segmentation fault Using host libthread_db library "/usr/lib/libthread_db.so.1". [Current thread is 1 (Thread 0x7f51a0defc80 (LWP 6108))] Thread 10 (Thread 0x7f50c3fff700 (LWP 8318)): [KCrash Handler] #6 0x7f50f09c44ee in () at /usr/lib/libdrm_nouveau.so.2 #7 0x7f50f09c5149 in () at /usr/lib/libdrm_nouveau.so.2 #8 0x7f50f56440c2 in () at /usr/lib/dri/nouveau_dri.so #9 0x7f50f5644bc5 in () at /usr/lib/dri/nouveau_dri.so #10 0x7f50f565a171 in () at /usr/lib/dri/nouveau_dri.so #11 0x7f50f565a312 in () at /usr/lib/dri/nouveau_dri.so #12 0x7f50f5bf4eda in () at /usr/lib/dri/nouveau_dri.so #13 0x7f50f593b13c in () at /usr/lib/dri/nouveau_dri.so #14 0x7f50f57f3a3c in () at /usr/lib/dri/nouveau_dri.so #15 0x7f50f57f5d58 in () at /usr/lib/dri/nouveau_dri.so #16 0x7f519e7f137b in QSGBatchRenderer::Renderer::unmap(QSGBatchRenderer::Buffer*, bool) () at /usr/lib/libQt5Quick.so.5 #17 0x7f519e7f2e9f in QSGBatchRenderer::Renderer::uploadBatch(QSGBatchRenderer::Batch*) () at /usr/lib/libQt5Quick.so.5 #18 0x7f519e7fdca7 in QSGBatchRenderer::Renderer::render() () at /usr/lib/libQt5Quick.so.5 #19 0x7f519e7ee31e in QSGRenderer::renderScene(QSGBindable const&) () at /usr/lib/libQt5Quick.so.5 #20 0x7f519e7ee7ec in QSGRenderer::renderScene(unsigned int) () at /usr/lib/libQt5Quick.so.5 #21 0x7f519e8289b0 in QSGDefaultRenderContext::renderNextFrame(QSGRenderer*, unsigned int) () at /usr/lib/libQt5Quick.so.5 #22 0x7f519e88c1a5 in QQuickWindowPrivate::renderSceneGraph(QSize const&) () at /usr/lib/libQt5Quick.so.5 #23 0x7f519e831150 in () at /usr/lib/libQt5Quick.so.5 #24 0x7f519e834f08 in () at /usr/lib/libQt5Quick.so.5 #25 0x7f519aaa8b95 in () at /usr/lib/libQt5Core.so.5 #26 0x7f5199c47075 in start_thread () at /usr/lib/libpthread.so.0 #27 0x7f519a39853f in clone () at /usr/lib/libc.so.6 Thread 9 (Thread 0x7f50cae3f700 (LWP 8171)): #0 0x7ffe4557ab91 in clock_gettime () #1 0x7f519a3a5fb6 in clock_gettime () at /usr/lib/libc.so.6 #2 0x7f519aca9772 in () at /usr/lib/libQt5Core.so.5 #3 0x7f519aca7f5a in QTimerInfoList::updateCurrentTime() () at /usr/lib/libQt5Core.so.5 #4 0x7f519acaa2d6 in () at /usr/lib/libQt5Core.so.5 #5 0x7f5194bcbf22 in g_main_context_check () at /usr/lib/libglib-2.0.so.0 #6 0x7f5194bcc4c6 in () at /usr/lib/libglib-2.0.so.0 #7 0x7f5194bcc63e in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #8 0x7f519aca9e64 in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #9 0x7f519ac5585c in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #10 0x7f519aa9eac9 in QThread::exec() () at /usr/lib/libQt5Core.so.5 #11 0x7f50cd7f01da in KCupsConnection::run() () at /usr/lib/libkcupslib.so #12 0x7f519aaa8b95 in () at /usr/lib/libQt5Core.so.5 #13 0x7f5199c47075 in start_thread () at /usr/lib/libpthread.so.0 #14 0x7f519a39853f in clone () at /usr/lib/libc.so.6 Thread 8 (Thread 0x7f50e3a14700 (LWP 7672)): #0 0x7f5199c4cffc in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7f519aaa934c in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/libQt5Core.so.5 #2 0x7f519e834cdd in () at /usr/lib/libQt5Quick.so.5 #3 0x7f519e834f4c in () at /usr/lib/libQt5Quick.so.5 #4 0x7f519aaa8b95 in () at /usr/lib/libQt5Core.so.5 #5 0x7f5199c47075 in start_thread () at /usr/lib/libpthread.so.0 #6 0x7f519a39853f in clone () at /usr/lib/libc.so.6 Thread 7 (Thread 0x7f50e45fe700 (LWP 7669)): #0 0x7ffe4557ab91 in clock_gettime () #1 0x7f519a3a5fb6 in clock_gettime () at /usr/lib/libc.so.6 #2 0x7f519aca9772 in () at /usr/lib/libQt5Core.so.5 #3 0x7f519aca7f5a in QTimerInfoList::updateCurrentTime() () at /usr/lib/libQt5Core.so.5 #4 0x7f519aca8556 in QTimerInfoList::timerWait(timespec&) () at /usr/lib/libQt5Core.so.5 #5 0x7f519aca9bcf in () at /usr/lib/libQt5Core.so.5 #6
[dolphin] [Bug 319643] Dolphin crashes after user moves file from one panel to another, panels have different settings.
https://bugs.kde.org/show_bug.cgi?id=319643 --- Comment #10 from Andrew M <quantumpha...@gmail.com> --- I haven't experienced this bug for years so you have my vote on closing it. -- You are receiving this mail because: You are watching all bug changes.
[kfile] [Bug 328497] File names occasionally get wrapped
https://bugs.kde.org/show_bug.cgi?id=328497 --- Comment #8 from Andrew M <quantumpha...@gmail.com> --- I have not seen this for a few years now. Is it still affecting anyone? -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 363959] Always the same identiy is chosen
https://bugs.kde.org/show_bug.cgi?id=363959 Andrew M <quantumpha...@gmail.com> changed: What|Removed |Added CC||quantumpha...@gmail.com --- Comment #1 from Andrew M <quantumpha...@gmail.com> --- I have the same problem with my work and personal accounts. To reproduce: 1. Set up two identities with corresponding IMAP and SMTP settings. 2. Make one of them default. 3. Compose a new message. 4. Try to select the other identity from the "Identity:" combo-box. 5. Combo-box does not exist any more (was there in the 4.x series). Instead there is an editable "From:" field. The old identity selector also changed the SMTP server that would be used for that message. -- You are receiving this mail because: You are watching all bug changes.
[kfile] [Bug 347514] KFileDialog 4 does not obey single/double click setting on KDE 5
https://bugs.kde.org/show_bug.cgi?id=347514 --- Comment #1 from Andrew M <quantumpha...@gmail.com> --- This bug is no longer causing me problems for a while now and appears that (from the votes) it only caused one other person problems. Everything is on frameworks 5 now an symptoms can no longer be reproduced. Can/should this be closed? -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 357138] New: Parent folder names on location bar breadcrumbs are the same as current folder when browsing remote KIO systems
https://bugs.kde.org/show_bug.cgi?id=357138 Bug ID: 357138 Summary: Parent folder names on location bar breadcrumbs are the same as current folder when browsing remote KIO systems Product: dolphin Version: 15.12.0 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: bars: location Assignee: dolphin-bugs-n...@kde.org Reporter: quantumpha...@gmail.com When browsing a remote samba share via Dolphin when I enter a subdir the current dir breadcrumb overwrites the parent and grandparent. The great grand parent dir is overwritten by the parent dir Reproducible: Always Steps to Reproduce: 1. Browse smb://myserver/Public/Videos/TV/show1/season1 The server does not need to exist to demonstrate the bug. Bug appears even with the folder does not exist error. 2. Look at the location bar in breadcrumb mode 3. Look at the location bar in edit mode Actual Results: As you navigate the folder from the top level the breadcrumbs for above example would be smb:myserver > smb:myserver > Public > smb:myserver > Videos > Videos > smb:myserver > TV > TV > TV > smb:myserver > TV > show1 > show1 > show1 > smb:myserver > TV > show1 > season1 > season1 > season1 Expected Results: smb://myserver/Public/Videos/TV/show1/season1 Should be > smb:myserver > Public > Videos > TV > show1 > season1 -- You are receiving this mail because: You are watching all bug changes.
