[krita] [Bug 380001] Mouse Wheel Up/Down zooms relative to cursor, +/- zooms to middle of canvas
https://bugs.kde.org/show_bug.cgi?id=380001 --- Comment #4 from mvowada --- (In reply to Raghavendra kamath from comment #3) > for those who want both types of zoom behaviour Keyboard shortcuts for zooming relative to the mouse cursor would let users to zoom relative to cursor directly from their pen buttons. Why not to add two new shortcuts, let's say "CTRL+SHIFT++" and "CTRL+SHIFT+-" for zooming to cursor? -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 392022] Position of a face tag appears on top of bottom of the list, instead of being sorted alphabetically
https://bugs.kde.org/show_bug.cgi?id=392022 --- Comment #6 from caulier.gil...@gmail.com --- I agree with Maik here. If you have a better workflow with face management, please provide a proff of concept using mockup. Thanks in advance -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 392022] Position of a face tag appears on top of bottom of the list, instead of being sorted alphabetically
https://bugs.kde.org/show_bug.cgi?id=392022 --- Comment #5 from Maik Qualmann --- We're talking about the face tags list in the popup that pops up when I start typing a name? I ask something provocative, what can improve their wish? The last used appear at top, why should they be duplicated or in italics? I do not see how it should accelerate the input somehow. Maik -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 402830] Autotool project full of dirty symbols in the project tree
https://bugs.kde.org/show_bug.cgi?id=402830 jd.fratt...@free.fr changed: What|Removed |Added Resolution|--- |NOT A BUG Status|REPORTED|RESOLVED --- Comment #2 from jd.fratt...@free.fr --- Yes that fixes the issue. Could be closed. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 380001] Mouse Wheel Up/Down zooms relative to cursor, +/- zooms to middle of canvas
https://bugs.kde.org/show_bug.cgi?id=380001 Raghavendra kamath changed: What|Removed |Added CC||ra...@raghukamath.com --- Comment #3 from Raghavendra kamath --- I don't know if this correct, while zooming from the mouse, I would like it to zoom with respect to my mouse cursor, but while zooming with the keyboard shortcut I would prefer it to be zoom in with respect to canvas center. I can't find the earlier discussion but we had a discussion about zoom actions. A user would require to position his cursor before zooming in with keyboard for it to zoom towards the cursor position, in which case he would most like be zooming with the mouse shortcut itself. So move cursor then zoom with shortcut becomes a bit cumbersome. there is also ctrl + space + (middle mouse) left click shortcut which can satisfy zoom to cursor position request too. Having the distinction of two different type of zoom action would help and be useful for those who want both types of zoom behavior -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 403677] kdevelop crash when wrong completion on include
https://bugs.kde.org/show_bug.cgi?id=403677 jd.fratt...@free.fr changed: What|Removed |Added CC||jd.fratt...@free.fr -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 403677] New: kdevelop crash when wrong completion on include
https://bugs.kde.org/show_bug.cgi?id=403677 Bug ID: 403677 Summary: kdevelop crash when wrong completion on include Product: kdevelop Version: 5.3.1 Platform: Debian testing OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: Code completion Assignee: kdevelop-bugs-n...@kde.org Reporter: jd.fratt...@free.fr Target Milestone: --- Kdevelop crashes when using completion to resolve include filename but not a header was choosed by the completion. Reproducible: always. STEPS TO REPRODUCE Have a Makefile in the header directory Have a header file starting by the letter m Start a #include statement Start to write the path Once the completion is in the right header directory, choose m Kdevelop will give priority to Makefile Type enter, Makefile will be written as the header file name And just next, kdevelop will crash OBSERVED RESULT Crash EXPECTED RESULT No crash As other issues with kdevelop, it seems the problem comes from the parser. But I cannot ensure this last point. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 403676] New: Converting vector layer to paint layer crops the content of the vector layer beyond canvas boundaries
https://bugs.kde.org/show_bug.cgi?id=403676 Bug ID: 403676 Summary: Converting vector layer to paint layer crops the content of the vector layer beyond canvas boundaries Product: krita Version: 4.1.7 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Layers/Vector Assignee: krita-bugs-n...@kde.org Reporter: ra...@raghukamath.com Target Milestone: --- SUMMARY If there is a vector object which spans beyond the canvas boundary , and a user converts it to raster (paint layer) the content that is beyond the canvas boundary gets trimmed or cropped. STEPS TO REPRODUCE 1. Open krita add a new vector layer, draw a rectangle such that half of it is beyond canvas boundary 2. right click on the layer in layer stack and go to convert > to paint layer 3. check the resulting layer by moving it, it must be now trimmed, discarding the portion that was out of canvas OBSERVED RESULT the vector objects beyond the canvas get trimmed when converting to paint layer EXPECTED RESULT the data should be preserved even when converting to paint layer -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 248998] ARMv5 and v6 support
https://bugs.kde.org/show_bug.cgi?id=248998 Nick Robinson changed: What|Removed |Added CC||notch...@gmail.com --- Comment #4 from Nick Robinson --- Chris - thanks for this, much appreciated - was planning on doing the same thing, and you bet me to it. Compiled and tested and works like a charm. V5 arm is still used in a significant number of products - here's hoping the dev team accept these changes. -- You are receiving this mail because: You are watching all bug changes.
[skrooge] [Bug 403675] New: App crashes with segfault after second import
https://bugs.kde.org/show_bug.cgi?id=403675 Bug ID: 403675 Summary: App crashes with segfault after second import Product: skrooge Version: 2.17.0 Platform: Ubuntu Packages OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: general Assignee: guillaume.deb...@gmail.com Reporter: mach...@gmail.com CC: steph...@mankowski.fr Target Milestone: --- Created attachment 117694 --> https://bugs.kde.org/attachment.cgi?id=117694=edit traces file after running scenario SUMMARY While importing bank account information using Quicken (QFX) files, the app always crashes after the second import with a segfault. Size of import does not appear to affect the situation. Same bank or different bank does not affect the situation. STEPS TO REPRODUCE 1. Open Skrooge 2. Login to bank and download account information using Quicken Web Connect file. 3. Click Open on the browser's Open/Save dialog. (Firefox was used.) 4. Note that the information is imported correctly as expected. 5. Repeat steps 2 and 3 and note that Skrooge crashes with a seg fault. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Ubuntu 18.04 (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION See attached traces.txt file $ export SKGTRACE=8 $ skrooge 2>&1 > traces.txt This issue is new with 2.17.0 and was not observed in previous versions. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 401988] Crash on touching graphic tablet pen on canvas
https://bugs.kde.org/show_bug.cgi?id=401988 Raghavendra kamath changed: What|Removed |Added CC||jindel...@gmail.com --- Comment #21 from Raghavendra kamath --- *** Bug 403672 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 403672] Crash when Krita registered tablet pen
https://bugs.kde.org/show_bug.cgi?id=403672 Raghavendra kamath changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |DUPLICATE CC||ra...@raghukamath.com --- Comment #1 from Raghavendra kamath --- *** This bug has been marked as a duplicate of bug 401988 *** -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 403674] New: [regression] Undo select polygon points with shift + z is not working in master
https://bugs.kde.org/show_bug.cgi?id=403674 Bug ID: 403674 Summary: [regression] Undo select polygon points with shift + z is not working in master Product: krita Version: 4.1.7 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Tools/Selection Assignee: krita-bugs-n...@kde.org Reporter: ra...@raghukamath.com Target Milestone: --- SUMMARY In the recent master branch, undoing select polygon points with shift +z is not working. this was along with the election shortcuts not working, but i forgot to mention it in the bug report earlier. STEPS TO REPRODUCE 1. open krita built from master and select the polygon selection tool 2. start to select with polygon selection tool 3. Try to undo the points with shift + z (as noted in the keyboard shortcuts) OBSERVED RESULT the shortcut doesn't work EXPECTED RESULT the last made polygon point should be undone by the shortcut -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 403673] New: KWin crashed after I woke my PC up from sleep
https://bugs.kde.org/show_bug.cgi?id=403673 Bug ID: 403673 Summary: KWin crashed after I woke my PC up from sleep Product: kwin Version: 5.14.5 Platform: Ubuntu Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kwin-bugs-n...@kde.org Reporter: techxga...@outlook.com Target Milestone: --- Application: kwin_x11 (5.14.5) Qt Version: 5.11.1 Frameworks Version: 5.52.0 Operating System: Linux 4.18.0-13-generic x86_64 Distribution: Ubuntu 18.10 -- Information about the crash: - What I was doing when the application crashed: I woke up the computer from sleep, and I got a notification that KWin crashed. As of right now, everything is fine, but I feel that I should submit this just in case it'll help improve it. -- Backtrace: Application: KWin (kwin_x11), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f6915160840 (LWP 2466))] Thread 8 (Thread 0x7f69008af700 (LWP 28298)): #0 0x7f691f6472eb in futex_wait_cancelable (private=, expected=0, futex_word=0x559421619740) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 0x7f691f6472eb in __pthread_cond_wait_common (abstime=0x0, mutex=0x5594216196f0, cond=0x559421619718) at pthread_cond_wait.c:502 #2 0x7f691f6472eb in __pthread_cond_wait (cond=0x559421619718, mutex=0x5594216196f0) at pthread_cond_wait.c:655 #3 0x7f691e10d43b in QWaitCondition::wait(QMutex*, unsigned long) () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7f691ca8d279 in () at /lib/x86_64-linux-gnu/libQt5Quick.so.5 #5 0x7f691ca8d4da in () at /lib/x86_64-linux-gnu/libQt5Quick.so.5 #6 0x7f691e10cc87 in () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7f691f641164 in start_thread (arg=) at pthread_create.c:486 #8 0x7f691f77adef in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 7 (Thread 0x7f6903bff700 (LWP 28297)): #0 0x7f691f76e7d6 in __GI_ppoll (fds=0x7f68f80129b8, nfds=1, timeout=, sigmask=0x0) at ../sysdeps/unix/sysv/linux/ppoll.c:39 #1 0x7f691e303141 in qt_safe_poll(pollfd*, unsigned long, timespec const*) () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #2 0x7f691e3045b9 in QEventDispatcherUNIX::processEvents(QFlags) () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #3 0x7f691e2b416b in QEventLoop::exec(QFlags) () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7f691e1030b6 in QThread::exec() () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f691c7581f5 in () at /lib/x86_64-linux-gnu/libQt5Qml.so.5 #6 0x7f691e10cc87 in () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7f691f641164 in start_thread (arg=) at pthread_create.c:486 #8 0x7f691f77adef in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 6 (Thread 0x7f6911a4a700 (LWP 4708)): #0 0x7f691f6472eb in futex_wait_cancelable (private=, expected=0, futex_word=0x55942119f0a0) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 0x7f691f6472eb in __pthread_cond_wait_common (abstime=0x0, mutex=0x55942119f050, cond=0x55942119f078) at pthread_cond_wait.c:502 #2 0x7f691f6472eb in __pthread_cond_wait (cond=0x55942119f078, mutex=0x55942119f050) at pthread_cond_wait.c:655 #3 0x7f691e10d43b in QWaitCondition::wait(QMutex*, unsigned long) () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7f691ca8d279 in () at /lib/x86_64-linux-gnu/libQt5Quick.so.5 #5 0x7f691ca8d4da in () at /lib/x86_64-linux-gnu/libQt5Quick.so.5 #6 0x7f691e10cc87 in () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7f691f641164 in start_thread (arg=) at pthread_create.c:486 #8 0x7f691f77adef in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 5 (Thread 0x7f68f702b700 (LWP 2739)): #0 0x7f691f6472eb in futex_wait_cancelable (private=, expected=0, futex_word=0x7f691dcf3fb8) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 0x7f691f6472eb in __pthread_cond_wait_common (abstime=0x0, mutex=0x7f691dcf3f68, cond=0x7f691dcf3f90) at pthread_cond_wait.c:502 #2 0x7f691f6472eb in __pthread_cond_wait (cond=0x7f691dcf3f90, mutex=0x7f691dcf3f68) at pthread_cond_wait.c:655 #3 0x7f691dbfce2a in () at /lib/x86_64-linux-gnu/libQt5Script.so.5 #4 0x7f691dbfce49 in () at /lib/x86_64-linux-gnu/libQt5Script.so.5 #5 0x7f691f641164 in start_thread (arg=) at pthread_create.c:486 #6 0x7f691f77adef in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 4 (Thread 0x7f691108d700 (LWP 2652)): #0 0x7f691f76e7d6 in __GI_ppoll (fds=0x7f68fc000d28, nfds=1, timeout=, sigmask=0x0) at ../sysdeps/unix/sysv/linux/ppoll.c:39 #1 0x7f691e303141 in qt_safe_poll(pollfd*, unsigned long, timespec const*) () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #2 0x7f691e3045b9 in QEventDispatcherUNIX::processEvents(QFlags)
[konsole] [Bug 196998] Konsole should reflow the text when resizing
https://bugs.kde.org/show_bug.cgi?id=196998 Kishore Gopalakrishnan changed: What|Removed |Added CC||kishor...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 389530] Kdenlive doesn't save Interface settings (AppImage)
https://bugs.kde.org/show_bug.cgi?id=389530 --- Comment #4 from Bug Janitor Service --- 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! -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 403672] New: Crash when Krita registered tablet pen
https://bugs.kde.org/show_bug.cgi?id=403672 Bug ID: 403672 Summary: Crash when Krita registered tablet pen Product: krita Version: unspecified Platform: Fedora RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: General Assignee: krita-bugs-n...@kde.org Reporter: jindel...@gmail.com Target Milestone: --- Application: krita (4.1.7.101) Qt Version: 5.11.3 Frameworks Version: 5.53.0 Operating System: Linux 4.19.16-200.fc28.x86_64 x86_64 Distribution: "Fedora release 28 (Twenty Eight)" -- Information about the crash: - What I was doing when the application crashed: Krita booted and functioned as normal until pen was registered as active near the tablet's surface, upon which the programme suddenly terminated. This happens every time I attempted to restart the application. - Custom settings of the application: deevad brushes bundle, but there were no issues with it until today. I had installed the pack mid-December 2018. The crash can be reproduced every time. -- Backtrace: Application: Krita (krita), signal: Aborted Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f5e403fd940 (LWP 30347))] Thread 8 (Thread 0x7f5dea8e8700 (LWP 30360)): #0 0x7f5e33fee429 in poll () from /lib64/libc.so.6 #1 0x7f5e31b5fc56 in g_main_context_iterate.isra () from /lib64/libglib-2.0.so.0 #2 0x7f5e31b5fd80 in g_main_context_iteration () from /lib64/libglib-2.0.so.0 #3 0x7f5e34e9ed5b in QEventDispatcherGlib::processEvents(QFlags) () from /lib64/libQt5Core.so.5 #4 0x7f5e34e4d5bb in QEventLoop::exec(QFlags) () from /lib64/libQt5Core.so.5 #5 0x7f5e34cb5c16 in QThread::exec() () from /lib64/libQt5Core.so.5 #6 0x7f5df4085a8a in QQuickPixmapReader::run() () from /lib64/libQt5Quick.so.5 #7 0x7f5e34cbf08b in QThreadPrivate::start(void*) () from /lib64/libQt5Core.so.5 #8 0x7f5e32ddf594 in start_thread () from /lib64/libpthread.so.0 #9 0x7f5e33ff8f4f in clone () from /lib64/libc.so.6 Thread 7 (Thread 0x7f5debfff700 (LWP 30359)): #0 0x7f5e34cb2aa3 in QMutex::unlock() () from /lib64/libQt5Core.so.5 #1 0x7f5e34e9ec71 in postEventSourcePrepare(_GSource*, int*) () from /lib64/libQt5Core.so.5 #2 0x7f5e31b5f199 in g_main_context_prepare () from /lib64/libglib-2.0.so.0 #3 0x7f5e31b5fb8b in g_main_context_iterate.isra () from /lib64/libglib-2.0.so.0 #4 0x7f5e31b5fd80 in g_main_context_iteration () from /lib64/libglib-2.0.so.0 #5 0x7f5e34e9ed5b in QEventDispatcherGlib::processEvents(QFlags) () from /lib64/libQt5Core.so.5 #6 0x7f5e34e4d5bb in QEventLoop::exec(QFlags) () from /lib64/libQt5Core.so.5 #7 0x7f5e34cb5c16 in QThread::exec() () from /lib64/libQt5Core.so.5 #8 0x7f5df3bfcce9 in QQmlThreadPrivate::run() () from /lib64/libQt5Qml.so.5 #9 0x7f5e34cbf08b in QThreadPrivate::start(void*) () from /lib64/libQt5Core.so.5 #10 0x7f5e32ddf594 in start_thread () from /lib64/libpthread.so.0 #11 0x7f5e33ff8f4f in clone () from /lib64/libc.so.6 Thread 6 (Thread 0x7f5df308b700 (LWP 30358)): #0 0x7f5e33ff3959 in syscall () from /lib64/libc.so.6 #1 0x7f5e34cb4b30 in bool futexSemaphoreTryAcquire_loop(QBasicAtomicInteger&, unsigned long long, unsigned long long, int) () from /lib64/libQt5Core.so.5 #2 0x7f5e34cb48b2 in QSemaphore::tryAcquire(int, int) () from /lib64/libQt5Core.so.5 #3 0x7f5e3d25104a in KisTileDataSwapper::run() () from /lib64/libkritaimage.so.17 #4 0x7f5e34cbf08b in QThreadPrivate::start(void*) () from /lib64/libQt5Core.so.5 #5 0x7f5e32ddf594 in start_thread () from /lib64/libpthread.so.0 #6 0x7f5e33ff8f4f in clone () from /lib64/libc.so.6 Thread 5 (Thread 0x7f5df388c700 (LWP 30357)): #0 0x7f5e33ff3959 in syscall () from /lib64/libc.so.6 #1 0x7f5e34cb499c in bool futexSemaphoreTryAcquire(QBasicAtomicInteger&, int, int) () from /lib64/libQt5Core.so.5 #2 0x7f5e3d233b9a in KisTileDataPooler::waitForWork() () from /lib64/libkritaimage.so.17 #3 0x7f5e3d23440a in KisTileDataPooler::run() () from /lib64/libkritaimage.so.17 #4 0x7f5e34cbf08b in QThreadPrivate::start(void*) () from /lib64/libQt5Core.so.5 #5 0x7f5e32ddf594 in start_thread () from /lib64/libpthread.so.0 #6 0x7f5e33ff8f4f in clone () from /lib64/libc.so.6 Thread 4 (Thread 0x7f5e15057700 (LWP 30353)): #0 0x7f5e33fe9e94 in read () from /lib64/libc.so.6 #1 0x7f5e31ba5700 in g_wakeup_acknowledge () from /lib64/libglib-2.0.so.0 #2 0x7f5e31b5f74b in g_main_context_check () from /lib64/libglib-2.0.so.0 #3 0x7f5e31b5fc00 in g_main_context_iterate.isra () from /lib64/libglib-2.0.so.0 #4 0x7f5e31b5fd80 in g_main_context_iteration () from /lib64/libglib-2.0.so.0 #5 0x7f5e34e9ed5b in QEventDispatcherGlib::processEvents(QFlags) () from /lib64/libQt5Core.so.5 #6
[yakuake] [Bug 395012] Skins can't be installed from KNS
https://bugs.kde.org/show_bug.cgi?id=395012 Chris Holland changed: What|Removed |Added CC||zrenf...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 400987] XWayland application focus breaks
https://bugs.kde.org/show_bug.cgi?id=400987 Brian changed: What|Removed |Added Version|unspecified |5.14.90 --- Comment #20 from Brian --- Persists on the latest 5.15.80 plasma git. Workaround does not work at all. -- You are receiving this mail because: You are watching all bug changes.
[latte-dock] [Bug 401184] Latte Dock - Global Keyboard Shortcuts Stop Working / Multiple Entries Created
https://bugs.kde.org/show_bug.cgi?id=401184 --- Comment #11 from scum.filter+...@gmail.com --- (In reply to scum.filter+kde from comment #10) > Unfortunately I'm not having success installing from git. I'm getting ‘class > Latte::GlobalShortcuts’ has no member named ‘hideDockTimerSlot’; did you > mean ‘hideDocksTimerSlot’? Okay, I located the lines to change in moc_globalshortcuts.cpp to address that error but am now getting error: initializer-string for array of chars is too long [-fpermissive] in .tmp/latte-dock/build/app/moc_globalshortcuts.cpp:41:1: A bit out of my depth at this point... -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 403671] New: System Settings crashes when entering Display and Monitor
https://bugs.kde.org/show_bug.cgi?id=403671 Bug ID: 403671 Summary: System Settings crashes when entering Display and Monitor Product: systemsettings Version: unspecified Platform: Neon Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: brianabe...@gmail.com Target Milestone: --- Application: systemsettings5 (5.15.80) Qt Version: 5.11.2 Frameworks Version: 5.54.0 Operating System: Linux 4.20.4-xanmod3 x86_64 Distribution: KDE neon Developer Edition -- Information about the crash: - What I was doing when the application crashed: Going into the Display and Monitor section of the settings menu. The crash can be reproduced every time. -- Backtrace: Application: System Settings (systemsettings5), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f76502cf840 (LWP 9860))] Thread 15 (Thread 0x7f75eecc9700 (LWP 9876)): #0 0x7f7646fca9f3 in futex_wait_cancelable (private=, expected=0, futex_word=0x5586ad6f7f20) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 __pthread_cond_wait_common (abstime=0x0, mutex=0x5586ad6f7ed0, cond=0x5586ad6f7ef8) at pthread_cond_wait.c:502 #2 __pthread_cond_wait (cond=0x5586ad6f7ef8, mutex=0x5586ad6f7ed0) at pthread_cond_wait.c:655 #3 0x7f763346d46b in ?? () from /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so #4 0x7f763346d197 in ?? () from /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so #5 0x7f7646fc46db in start_thread (arg=0x7f75eecc9700) at pthread_create.c:463 #6 0x7f764b8c688f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 14 (Thread 0x7f75ef786700 (LWP 9875)): #0 0x7f7646fca9f3 in futex_wait_cancelable (private=, expected=0, futex_word=0x5586ad586700) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 __pthread_cond_wait_common (abstime=0x0, mutex=0x5586ad5866b0, cond=0x5586ad5866d8) at pthread_cond_wait.c:502 #2 __pthread_cond_wait (cond=0x5586ad5866d8, mutex=0x5586ad5866b0) at pthread_cond_wait.c:655 #3 0x7f763346d46b in ?? () from /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so #4 0x7f763346d197 in ?? () from /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so #5 0x7f7646fc46db in start_thread (arg=0x7f75ef786700) at pthread_create.c:463 #6 0x7f764b8c688f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 13 (Thread 0x7f75fbfff700 (LWP 9874)): #0 0x7f7646fca9f3 in futex_wait_cancelable (private=, expected=0, futex_word=0x5586ad208dd4) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 __pthread_cond_wait_common (abstime=0x0, mutex=0x5586ad208d80, cond=0x5586ad208da8) at pthread_cond_wait.c:502 #2 __pthread_cond_wait (cond=0x5586ad208da8, mutex=0x5586ad208d80) at pthread_cond_wait.c:655 #3 0x7f763346d46b in ?? () from /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so #4 0x7f763346d197 in ?? () from /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so #5 0x7f7646fc46db in start_thread (arg=0x7f75fbfff700) at pthread_create.c:463 #6 0x7f764b8c688f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 12 (Thread 0x7f7600af7700 (LWP 9873)): #0 0x7f7646fca9f3 in futex_wait_cancelable (private=, expected=0, futex_word=0x5586ad16de00) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 __pthread_cond_wait_common (abstime=0x0, mutex=0x5586ad16ddb0, cond=0x5586ad16ddd8) at pthread_cond_wait.c:502 #2 __pthread_cond_wait (cond=0x5586ad16ddd8, mutex=0x5586ad16ddb0) at pthread_cond_wait.c:655 #3 0x7f763346d46b in ?? () from /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so #4 0x7f763346d197 in ?? () from /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so #5 0x7f7646fc46db in start_thread (arg=0x7f7600af7700) at pthread_create.c:463 #6 0x7f764b8c688f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 11 (Thread 0x7f7602f20700 (LWP 9872)): #0 0x7f764b8b9bf9 in __GI___poll (fds=0x7f75fc004a00, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7f7644c06539 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f7644c0664c in g_main_context_iteration () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f764c1f46eb in QEventDispatcherGlib::processEvents (this=0x7f75fc000b20, flags=...) at kernel/qeventdispatcher_glib.cpp:424 #4 0x7f764c1989aa in QEventLoop::exec (this=this@entry=0x7f7602f1fd40, flags=..., flags@entry=...) at kernel/qeventloop.cpp:214 #5 0x7f764bfc425a in QThread::exec (this=) at thread/qthread.cpp:525 #6 0x7f7649fed4f5 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5 #7 0x7f764bfcf17b in QThreadPrivate::start (arg=0x5586aceee040) at thread/qthread_unix.cpp:367 #8 0x7f7646fc46db in start_thread
[latte-dock] [Bug 403425] Notifications from system-tray widget not showing
https://bugs.kde.org/show_bug.cgi?id=403425 --- Comment #32 from connectbha...@gmail.com --- I have filed a bug report at the github repo of event-calendar. Here is the link for you two reference - https://github.com/Zren/plasma-applet-eventcalendar/issues/60 -- You are receiving this mail because: You are watching all bug changes.
[latte-dock] [Bug 401184] Latte Dock - Global Keyboard Shortcuts Stop Working / Multiple Entries Created
https://bugs.kde.org/show_bug.cgi?id=401184 --- Comment #10 from scum.filter+...@gmail.com --- (In reply to Michail Vourlakos from comment #8) > Please if you can try out the git version to confirm the fix it would help > me a lot because in that way I could apply this patch also for next Latte > stable version 0.8.6 Unfortunately I'm not having success installing from git. I'm getting ‘class Latte::GlobalShortcuts’ has no member named ‘hideDockTimerSlot’; did you mean ‘hideDocksTimerSlot’? -- You are receiving this mail because: You are watching all bug changes.
[kio-gdrive] [Bug 403670] New: Add support for Team Drives
https://bugs.kde.org/show_bug.cgi?id=403670 Bug ID: 403670 Summary: Add support for Team Drives Product: kio-gdrive Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: general Assignee: elvis.angelac...@kde.org Reporter: r...@sandersmail.eu Target Milestone: --- Google offers team drives for Enterprise, Business and Education accounts: https://gsuite.google.com/learning-center/products/drive/get-started-team-drive/ It would be very helpful if kio-gdrive could support this functionality. -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 403667] KDE Wayland complete crash during normal use - org_kde_powerde
https://bugs.kde.org/show_bug.cgi?id=403667 --- Comment #2 from Brian --- I have not been able to reproduce it yet unfortunately. It's very random. I was in spotify at the time switching a song, and then i went and minimized the window and opened dolphin. Further, i'm not really sure how i could grab the backtrace? -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 403667] KDE Wayland complete crash during normal use - org_kde_powerde
https://bugs.kde.org/show_bug.cgi?id=403667 David Edmundson changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |NOT A BUG CC||k...@davidedmundson.co.uk --- Comment #1 from David Edmundson --- >Jan 27 14:10:18 brian-ryzen systemd-coredump[8683]: Process 7069 >(kwin_wayland) of user 1000 dumped core. Kwin crashed. Kwin crashing just makes everything quit. >From a powerdevil POV, it's not a bug, so I'll close this. We still have a kwin crash. Do you remember what you were doing at the time? Ideally we also need to get a backtrace. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 399836] kwin crash on changing virtual desktop
https://bugs.kde.org/show_bug.cgi?id=399836 --- Comment #13 from Stamatis Kavvadias --- Listen, I am sorry if I was not clear enough (but you also did not check my previous efforts to provide a backtrace). The case is that, since I provided the initial backtrace (w/o debug symbols), I have accepted an update which changed the situation: I no longer have a version of kwin (or kwin_x11) that crashes from the bug. Instead, my current kwin version just exits normally when the bug happens. This update happened exactly before I tried to attach gdb to kwin, so when I did the result was that gdb *could not* provide a backtrace. I have provided the output of gdb in this case, which explains clearly why. So, tell me something new to do or just delete this bug report, if it cannot be handled, under the circumstances. Thank you for your efforts, anyway. -- You are receiving this mail because: You are watching all bug changes.
[akregator] [Bug 403669] Akregator crashed following links
https://bugs.kde.org/show_bug.cgi?id=403669 --- Comment #2 from Barry --- Thanks, I’ll check that out.. On Sun, 27 Jan 2019 at 20:39, Colin J Thomson wrote: > https://bugs.kde.org/show_bug.cgi?id=403669 > > Colin J Thomson changed: > >What|Removed |Added > > > CC||colin.thom...@g6avk.co.uk > Resolution|--- |DUPLICATE > Status|REPORTED|RESOLVED > > --- Comment #1 from Colin J Thomson --- > Most likely related to this. > > *** This bug has been marked as a duplicate of bug 371511 *** > > -- > You are receiving this mail because: > You reported the bug. -- You are receiving this mail because: You are watching all bug changes.
[akregator] [Bug 403669] Akregator crashed following links
https://bugs.kde.org/show_bug.cgi?id=403669 Colin J Thomson changed: What|Removed |Added CC||colin.thom...@g6avk.co.uk Resolution|--- |DUPLICATE Status|REPORTED|RESOLVED --- Comment #1 from Colin J Thomson --- Most likely related to this. *** This bug has been marked as a duplicate of bug 371511 *** -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 371511] kontact/akregator crashes while trying to open a link from the list (middle click)
https://bugs.kde.org/show_bug.cgi?id=371511 Colin J Thomson changed: What|Removed |Added CC||barryvd...@googlemail.com --- Comment #29 from Colin J Thomson --- *** Bug 403669 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[akregator] [Bug 403669] New: Akregator crashed following links
https://bugs.kde.org/show_bug.cgi?id=403669 Bug ID: 403669 Summary: Akregator crashed following links Product: akregator Version: unspecified Platform: Fedora RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: barryvd...@googlemail.com Target Milestone: --- Application: akregator (5.9.3) Qt Version: 5.11.3 Frameworks Version: 5.54.0 Operating System: Linux 4.20.3-200.fc29.x86_64 x86_64 Distribution: "Fedora release 29 (Twenty Nine)" -- Information about the crash: - What I was doing when the application crashed: I was reading an article and clicked a link in the "complete article" view and Akregator crashed. The crash can be reproduced sometimes. -- Backtrace: Application: Akregator (akregator), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7fdbdac085c0 (LWP 4303))] Thread 30 (Thread 0x7fdaa7b7e700 (LWP 4437)): #0 0x7fdbe2f6ab28 in pthread_cond_timedwait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7fdbe5efeb57 in () at /usr/lib64/qt5-qtwebengine-freeworld/libQt5WebEngineCore.so.5 #2 0x7fdbe5f0081a in () at /usr/lib64/qt5-qtwebengine-freeworld/libQt5WebEngineCore.so.5 #3 0x7fdbe5f00902 in () at /usr/lib64/qt5-qtwebengine-freeworld/libQt5WebEngineCore.so.5 #4 0x7fdbe5f056c1 in () at /usr/lib64/qt5-qtwebengine-freeworld/libQt5WebEngineCore.so.5 #5 0x7fdbe5f069bf in () at /usr/lib64/qt5-qtwebengine-freeworld/libQt5WebEngineCore.so.5 #6 0x7fdbe5f10fd1 in () at /usr/lib64/qt5-qtwebengine-freeworld/libQt5WebEngineCore.so.5 #7 0x7fdbe2f6458e in start_thread () at /lib64/libpthread.so.0 #8 0x7fdbeac196a3 in clone () at /lib64/libc.so.6 Thread 29 (Thread 0x7fdab344e700 (LWP 4436)): #0 0x7fdbe2f6ab28 in pthread_cond_timedwait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7fdbe5efeb57 in () at /usr/lib64/qt5-qtwebengine-freeworld/libQt5WebEngineCore.so.5 #2 0x7fdbe5f0081a in () at /usr/lib64/qt5-qtwebengine-freeworld/libQt5WebEngineCore.so.5 #3 0x7fdbe5f00902 in () at /usr/lib64/qt5-qtwebengine-freeworld/libQt5WebEngineCore.so.5 #4 0x7fdbe5f056c1 in () at /usr/lib64/qt5-qtwebengine-freeworld/libQt5WebEngineCore.so.5 #5 0x7fdbe5f069bf in () at /usr/lib64/qt5-qtwebengine-freeworld/libQt5WebEngineCore.so.5 #6 0x7fdbe5f10fd1 in () at /usr/lib64/qt5-qtwebengine-freeworld/libQt5WebEngineCore.so.5 #7 0x7fdbe2f6458e in start_thread () at /lib64/libpthread.so.0 #8 0x7fdbeac196a3 in clone () at /lib64/libc.so.6 Thread 28 (Thread 0x7fdbbc8b3700 (LWP 4410)): #0 0x7fdbe2f6a73c in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7fdbe5efea89 in () at /usr/lib64/qt5-qtwebengine-freeworld/libQt5WebEngineCore.so.5 #2 0x7fdbe5f00828 in () at /usr/lib64/qt5-qtwebengine-freeworld/libQt5WebEngineCore.so.5 #3 0x7fdbe5f008bf in () at /usr/lib64/qt5-qtwebengine-freeworld/libQt5WebEngineCore.so.5 #4 0x7fdbe5f056d8 in () at /usr/lib64/qt5-qtwebengine-freeworld/libQt5WebEngineCore.so.5 #5 0x7fdbe5f069bf in () at /usr/lib64/qt5-qtwebengine-freeworld/libQt5WebEngineCore.so.5 #6 0x7fdbe5f10fd1 in () at /usr/lib64/qt5-qtwebengine-freeworld/libQt5WebEngineCore.so.5 #7 0x7fdbe2f6458e in start_thread () at /lib64/libpthread.so.0 #8 0x7fdbeac196a3 in clone () at /lib64/libc.so.6 Thread 27 (Thread 0x7fdaa6b7c700 (LWP 4407)): #0 0x7fdbeac26dbc in __lll_lock_wait_private () at /lib64/libc.so.6 #1 0x7fdbeac28c68 in __fprintf_chk () at /lib64/libc.so.6 #2 0x7fdbdfa77e7f in event_logv_ () at /lib64/libevent-2.1.so.6 #3 0x7fdbdfa78048 in event_warn () at /lib64/libevent-2.1.so.6 #4 0x7fdbdfa79a40 in epoll_dispatch () at /lib64/libevent-2.1.so.6 #5 0x7fdbdfa6f598 in event_base_loop () at /lib64/libevent-2.1.so.6 #6 0x7fdbe5ed314d in () at /usr/lib64/qt5-qtwebengine-freeworld/libQt5WebEngineCore.so.5 #7 0x7fdbe5ef261b in () at /usr/lib64/qt5-qtwebengine-freeworld/libQt5WebEngineCore.so.5 #8 0x7fdbe5f15554 in () at /usr/lib64/qt5-qtwebengine-freeworld/libQt5WebEngineCore.so.5 #9 0x7fdbe5f10fd1 in () at /usr/lib64/qt5-qtwebengine-freeworld/libQt5WebEngineCore.so.5 #10 0x7fdbe2f6458e in start_thread () at /lib64/libpthread.so.0 #11 0x7fdbeac196a3 in clone () at /lib64/libc.so.6 Thread 26 (Thread 0x7fdab3c4f700 (LWP 4403)): #0 0x7fdbe2f6ab28 in pthread_cond_timedwait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7fdbe5efeb57 in () at /usr/lib64/qt5-qtwebengine-freeworld/libQt5WebEngineCore.so.5 #2 0x7fdbe5f0081a in () at /usr/lib64/qt5-qtwebengine-freeworld/libQt5WebEngineCore.so.5 #3 0x7fdbe5f00902 in () at /usr/lib64/qt5-qtwebengine-freeworld/libQt5WebEngineCore.so.5 #4 0x7fdbe5f056c1 in () at
[kphotoalbum] [Bug 403668] New: All keywords/"Schlüsselbegriffe" removed from database with 5.4
https://bugs.kde.org/show_bug.cgi?id=403668 Bug ID: 403668 Summary: All keywords/"Schlüsselbegriffe" removed from database with 5.4 Product: kphotoalbum Version: 5.4 Platform: openSUSE RPMs OS: Linux Status: REPORTED Severity: grave Priority: NOR Component: XML backend Assignee: kpab...@willden.org Reporter: use...@ingoreise.de Target Milestone: --- SUMMARY The automated upgrade to 5.4 destroyed all (!) my keyword-tags in the index.xml In my german version that's "Schlüsselbegiffe". I could assume that they were dropped because of the umlaut. At the same time the value of the "Schlüsselbegiffe" attribute changed from a numeric reference to the full text. STEPS TO REPRODUCE 1. Use kphotoalbum with a German localization 2. Wait for the 5.4 update ... 3. Panic OBSERVED RESULT One example line from an index.xml backup Same line after update w/o the "Schlüsselbegriffe": EXPECTED RESULT SOFTWARE/OS VERSIONS openSuSE 42.3 Linux/KDE Plasma: KDE Frameworks 5.32.0 Qt 5.6.2 (built against 5.6.2) The xcb windowing system ADDITIONAL INFORMATION Tagging images with keywords is my main use-case for kphotoalbum. Thanks for the automatic backup of the index. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 403663] colors are darker upon returning to the virtual desktop
https://bugs.kde.org/show_bug.cgi?id=403663 Mathias Kraus changed: What|Removed |Added Assignee|k.h...@gmx.de |krita-bugs-n...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 403663] colors are darker upon returning to the virtual desktop
https://bugs.kde.org/show_bug.cgi?id=403663 Mathias Kraus changed: What|Removed |Added Component|general |General Product|abakus |krita -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 403667] New: KDE Wayland complete crash during normal use - org_kde_powerde
https://bugs.kde.org/show_bug.cgi?id=403667 Bug ID: 403667 Summary: KDE Wayland complete crash during normal use - org_kde_powerde Product: Powerdevil Version: 5.14.90 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: brianabe...@gmail.com Target Milestone: --- Created attachment 117692 --> https://bugs.kde.org/attachment.cgi?id=117692=edit Full kernel log - line 5251 SUMMARY Wayland session crashes and goes to a black screen requiring a reboot The kernel logs mention org_kde_powerde and org_kde_powerdevil STEPS TO REPRODUCE 1. Use the wayland sessions normally. Issue seems to happen randomly. OBSERVED RESULT The whole wayland session crashes and you are brought to a black screen, which shows no response to keyboard input. Kernel logs show that the kernel is still at least recognizing REISUB (i had it disabled at the time though so i couldn't use it), so i don't think it's the problem. EXPECTED RESULT Wayland session does *not* crash SOFTWARE/OS VERSIONS Linux/KDE Plasma: Antergos with 4.14.5-2 (happened once) & 4.14.90-1 (happened twice so far) (available in About System) KDE Plasma Version: (for 4.14.90) KDE Frameworks Version: 5.54.0 Qt Version: 5.12.0 Kernel: 4.20.4-arch1-1-ARCH ADDITIONAL INFORMATION I'm using a RX 560 (AMDGPU) and a Ryzen 5 2600 cpu (Motherboard is a MSI B450M Gaming Plus with current bios (7B87v13 and AGESA Code 1.0.0.6) Attached is the kernel log (at around line 5251 is where the issue seems to start) -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 392022] Position of a face tag appears on top of bottom of the list, instead of being sorted alphabetically
https://bugs.kde.org/show_bug.cgi?id=392022 stefan.mueller...@gmail.com changed: What|Removed |Added CC||stefan.mueller...@gmail.com Ever confirmed|0 |1 Resolution|FIXED |--- Status|RESOLVED|REOPENED --- Comment #4 from stefan.mueller...@gmail.com --- > The wish was that the last used tags appear at the top for faster selection. Would it possible to split those list in last selected ones (maybe with three items, preferably adjustable in the options menu) and all items. Thus, the normal list (all items) remains consistent. For easier discrimination, the first list shall be formatted e.g. italic. -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 403666] Can't pin GUI applications started by script
https://bugs.kde.org/show_bug.cgi?id=403666 michal.kone...@packetseekers.eu changed: What|Removed |Added CC||michal.konecny@packetseeker ||s.eu -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 403666] New: Can't pin GUI applications started by script
https://bugs.kde.org/show_bug.cgi?id=403666 Bug ID: 403666 Summary: Can't pin GUI applications started by script Product: kde Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: michal.kone...@packetseekers.eu Target Milestone: --- Created attachment 117691 --> https://bugs.kde.org/attachment.cgi?id=117691=edit TeamSpeak_pin_example SUMMARY When the application is started by script, it can't be pinned to panel. For example https://github.com/flathub/com.teamspeak.TeamSpeak can't be pinned. STEPS TO REPRODUCE 1. Install TeamSpeak from Flathub 2. Run application 3. Try to pin application OBSERVED RESULT Pin option is grayed out EXPECTED RESULT Pin option is available SOFTWARE/OS VERSIONS Linux/KDE Plasma: Fedora 29 (available in About System) KDE Plasma Version: 5.14.4 KDE Frameworks Version: 5.54.0 Qt Version: 5.11.3 ADDITIONAL INFORMATION I tried to add `StartupWMClass=TeamSpeak` to desktop file and this didn't helped . -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 384396] Wish: display faces sorted by similarity (pre-grouped) instead of album/time/..
https://bugs.kde.org/show_bug.cgi?id=384396 stefan.mueller...@gmail.com changed: What|Removed |Added CC||stefan.mueller...@gmail.com --- Comment #4 from stefan.mueller...@gmail.com --- I agree. I regard this a very urgent feature, since if you have a high number of faces, without having a possibility of sorting and filtering, it becomes messy and fiddly what drives me crazy. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 380201] Dolphin Crash when renaming and moving folders into folders.
https://bugs.kde.org/show_bug.cgi?id=380201 Julian Schraner changed: What|Removed |Added CC||chabot.dan...@free.fr --- Comment #5 from Julian Schraner --- *** Bug 403665 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 403665] Dolphin crash while i was moving a lot of photo
https://bugs.kde.org/show_bug.cgi?id=403665 Julian Schraner changed: What|Removed |Added Resolution|--- |DUPLICATE Status|REPORTED|RESOLVED CC||m...@xyquadrat.ch --- Comment #1 from Julian Schraner --- *** This bug has been marked as a duplicate of bug 380201 *** -- You are receiving this mail because: You are watching all bug changes.
[frameworks-qqc2-desktop-style] [Bug 394296] TabBar styling does not either draw a frame around the content area or touch the content area beneath it, which looks bad
https://bugs.kde.org/show_bug.cgi?id=394296 --- Comment #7 from Nate Graham --- Thanks David, that's just about perfect. Only two minor visual issues: - With this, the one-pixel line below the tab bar is now unnecessary; the active tab should appear to be a vertical extension of the view below it, just like a QWidgets tab - The frame doesn't have rounded corners like the QWidgets one -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 403665] New: Dolphin crash while i was moving a lot of photo
https://bugs.kde.org/show_bug.cgi?id=403665 Bug ID: 403665 Summary: Dolphin crash while i was moving a lot of photo Product: dolphin Version: 18.08.3 Platform: Fedora RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: chabot.dan...@free.fr CC: elvis.angelac...@kde.org Target Milestone: --- Application: dolphin (18.08.3) Qt Version: 5.11.3 Frameworks Version: 5.53.0 Operating System: Linux 4.19.15-300.fc29.x86_64 x86_64 Distribution (Platform): Fedora RPMs -- Information about the crash: - What I was doing when the application crashed: First sory for my english I was moving a lot of raw photos (about 15Mo by photo). After moving about 30 to 50 packets (hundred photos by packet) from a directory to another directory that i've create before, dolphin became slow and then crash. It could be possible that my email adresse do not work fine. You can use daniel.cha...@cegetel.net instead. The crash can be reproduced sometimes. -- Backtrace: Application: Dolphin (dolphin), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f4153fae940 (LWP 24495))] Thread 6 (Thread 0x7f4126ffd700 (LWP 31078)): #0 0x7f415a31ff84 in read () from /lib64/libc.so.6 #1 0x7f4154724355 in pa_read () from /usr/lib64/pulseaudio/libpulsecommon-12.2.so #2 0x7f4156b2b826 in pa_mainloop_prepare () from /lib64/libpulse.so.0 #3 0x7f4156b2c294 in pa_mainloop_iterate () from /lib64/libpulse.so.0 #4 0x7f4156b2c350 in pa_mainloop_run () from /lib64/libpulse.so.0 #5 0x7f4156b3a5bd in thread () from /lib64/libpulse.so.0 #6 0x7f415475406c in internal_thread_func () from /usr/lib64/pulseaudio/libpulsecommon-12.2.so #7 0x7f4157c9358e in start_thread () from /lib64/libpthread.so.0 #8 0x7f415a32f6a3 in clone () from /lib64/libc.so.6 Thread 5 (Thread 0x7f413e110700 (LWP 24499)): #0 0x7f415a31ff84 in read () from /lib64/libc.so.6 #1 0x7f4154935e90 in ?? () from /lib64/libglib-2.0.so.0 #2 0x7f41548eee9b in g_main_context_check () from /lib64/libglib-2.0.so.0 #3 0x7f41548ef350 in ?? () from /lib64/libglib-2.0.so.0 #4 0x7f41548ef4d0 in g_main_context_iteration () from /lib64/libglib-2.0.so.0 #5 0x7f4157ffc5ab in QEventDispatcherGlib::processEvents(QFlags) () from /lib64/libQt5Core.so.5 #6 0x7f4157faae0b in QEventLoop::exec(QFlags) () from /lib64/libQt5Core.so.5 #7 0x7f4157e12e86 in QThread::exec() () from /lib64/libQt5Core.so.5 #8 0x7f4157e1c2fb in ?? () from /lib64/libQt5Core.so.5 #9 0x7f4157c9358e in start_thread () from /lib64/libpthread.so.0 #10 0x7f415a32f6a3 in clone () from /lib64/libc.so.6 Thread 4 (Thread 0x7f413f272700 (LWP 24498)): #0 0x7f4157c9973c in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7f413f5d6c03 in ?? () from /usr/lib64/dri/nouveau_dri.so #2 0x7f413f5d695b in ?? () from /usr/lib64/dri/nouveau_dri.so #3 0x7f4157c9358e in start_thread () from /lib64/libpthread.so.0 #4 0x7f415a32f6a3 in clone () from /lib64/libc.so.6 Thread 3 (Thread 0x7f4145f26700 (LWP 24497)): #0 0x7f415a31ff84 in read () from /lib64/libc.so.6 #1 0x7f4154935e90 in ?? () from /lib64/libglib-2.0.so.0 #2 0x7f41548eee9b in g_main_context_check () from /lib64/libglib-2.0.so.0 #3 0x7f41548ef350 in ?? () from /lib64/libglib-2.0.so.0 #4 0x7f41548ef4d0 in g_main_context_iteration () from /lib64/libglib-2.0.so.0 #5 0x7f4157ffc5ab in QEventDispatcherGlib::processEvents(QFlags) () from /lib64/libQt5Core.so.5 #6 0x7f4157faae0b in QEventLoop::exec(QFlags) () from /lib64/libQt5Core.so.5 #7 0x7f4157e12e86 in QThread::exec() () from /lib64/libQt5Core.so.5 #8 0x7f4158251f89 in ?? () from /lib64/libQt5DBus.so.5 #9 0x7f4157e1c2fb in ?? () from /lib64/libQt5Core.so.5 #10 0x7f4157c9358e in start_thread () from /lib64/libpthread.so.0 #11 0x7f415a32f6a3 in clone () from /lib64/libc.so.6 Thread 2 (Thread 0x7f4146d2b700 (LWP 24496)): #0 0x7f415a324421 in poll () from /lib64/libc.so.6 #1 0x7f415482e39f in ?? () from /lib64/libxcb.so.1 #2 0x7f415483001a in xcb_wait_for_event () from /lib64/libxcb.so.1 #3 0x7f4146e9fbf9 in ?? () from /lib64/libQt5XcbQpa.so.5 #4 0x7f4157e1c2fb in ?? () from /lib64/libQt5Core.so.5 #5 0x7f4157c9358e in start_thread () from /lib64/libpthread.so.0 #6 0x7f415a32f6a3 in clone () from /lib64/libc.so.6 Thread 1 (Thread 0x7f4153fae940 (LWP 24495)): [KCrash Handler] #6 0x7f415a15f480 in KFileItemModel::expandedParentsCount(KFileItemModel::ItemData const*) () from /lib64/libdolphinprivate.so.5 #7 0x7f415a1861c9 in KItemListView::hasSiblingSuccessor(int) const () from /lib64/libdolphinprivate.so.5 #8
[Falkon] [Bug 398856] Right click on an item of a bookmark folder should display the context menu instead of open it in a new tab
https://bugs.kde.org/show_bug.cgi?id=398856 Felipe changed: What|Removed |Added CC||felipefp...@gmail.com --- Comment #2 from Felipe --- (In reply to trmdi from comment #0) > Right click on an item that is not in a bookmark folder displays the context > menu. > But right click on an item that is in a bookmark folder does NOT. (How can I > quickly delete that item?) > > It should display the context menu in all cases. Indeed, this is what it happens in other browsers, aside that it sucks that we cant delete the entries "bookmarks toolbar" and "unsorted bookmarks" to clean and have more space. -- You are receiving this mail because: You are watching all bug changes.
[xdg-desktop-portal-kde] [Bug 403199] KDE file save dialog in Firefox don't remember last used folder
https://bugs.kde.org/show_bug.cgi?id=403199 --- Comment #4 from Murz --- Also, after I try to open Save dialog, it also reset last used folder in Open dialog too. -- You are receiving this mail because: You are watching all bug changes.
[xdg-desktop-portal-kde] [Bug 403199] KDE file save dialog in Firefox don't remember last used folder
https://bugs.kde.org/show_bug.cgi?id=403199 Murz changed: What|Removed |Added Status|NEEDSINFO |REPORTED Resolution|WAITINGFORINFO |--- --- Comment #3 from Murz --- xdg-desktop-portal-kde is 5.14.5-0ubuntu1~ubuntu18.10~ppa1, Firefox is running natively via system (Ubuntu) package. When I try to open file - it show last used folder correctly, but if I try to save - I always see my home folder instead of last usage folder. So seems the problem is only with Save dialog. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-knotifications] [Bug 403664] New: Notifications show up in the middle of the screen after disconnecting an external display
https://bugs.kde.org/show_bug.cgi?id=403664 Bug ID: 403664 Summary: Notifications show up in the middle of the screen after disconnecting an external display Product: frameworks-knotifications Version: 5.44.0 Platform: Ubuntu Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kdelibs-b...@kde.org Reporter: sam...@yahoo.com CC: kdelibs-b...@kde.org Target Milestone: --- SUMMARY Notifications show up in the middle of the screen after connecting and disconnecting from an external display. STEPS TO REPRODUCE 1. Connect the device to an external display of a different resolution. (not sure if the same resolution will also have this issue, couldn't test) 2. Set external display to extend desktop 3. Disconnect external display 4. Receive a notification OBSERVED RESULT Notification shows up towards the center of the screen instead of in the bottom left. I messed with the notification settings that let you change which corner of the screen the notifications show up in and it looks like it isn't resetting the desktop size after the external display gets disconnected. EXPECTED RESULT Notification should go back to the bottom left. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Ubuntu 18.04 KDE Plasma Version: 5.12.7 KDE Frameworks Version: 5.44.0 Qt Version: 5.9.5 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[abakus] [Bug 403663] New: colors are darker upon returning to the virtual desktop
https://bugs.kde.org/show_bug.cgi?id=403663 Bug ID: 403663 Summary: colors are darker upon returning to the virtual desktop Product: abakus Version: unspecified Platform: MS Windows OS: MS Windows Status: REPORTED Severity: major Priority: NOR Component: general Assignee: k.h...@gmx.de Reporter: felipexavierspind...@gmail.com Target Milestone: --- SUMMARY STEPS TO REPRODUCE 1. Opens any image in krita 2. 3. OBSERVED RESULT the open image becomes much darker, thus losing its original color values EXPECTED RESULT the open image with its original colors SOFTWARE/OS VERSIONS Windows: 10 MacOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION It is not a problem related to my computer. Because, any other program can open images without damagin the original colors. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 366784] Colors Are Darker Upon Returning to the Virtual Desktop
https://bugs.kde.org/show_bug.cgi?id=366784 felipexavierspind...@gmail.com changed: What|Removed |Added CC||felipexavierspindola@gmail. ||com -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 403662] New: Discover crashes shortly after it was started
https://bugs.kde.org/show_bug.cgi?id=403662 Bug ID: 403662 Summary: Discover crashes shortly after it was started Product: Discover Version: 5.14.5 Platform: Neon Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: discover Assignee: aleix...@kde.org Reporter: bern...@yahoo.com Target Milestone: --- Application: plasma-discover (5.14.5) Qt Version: 5.11.2 Frameworks Version: 5.54.0 Operating System: Linux 4.15.0-43-generic x86_64 Distribution: KDE neon User Edition 5.14 -- Information about the crash: Doesn't happen all the time but just now Discover crashes all the time. Need to reboot. The crash can be reproduced every time. -- Backtrace: Application: Discover (plasma-discover), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7fb86d1d5200 (LWP 8943))] Thread 13 (Thread 0x7fb82110c700 (LWP 8955)): #0 0x7fb864e4b9f3 in futex_wait_cancelable (private=, expected=0, futex_word=0x55692d72bb54) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 __pthread_cond_wait_common (abstime=0x0, mutex=0x55692d72bb00, cond=0x55692d72bb28) at pthread_cond_wait.c:502 #2 __pthread_cond_wait (cond=0x55692d72bb28, mutex=0x55692d72bb00) at pthread_cond_wait.c:655 #3 0x7fb868e5594b in QWaitConditionPrivate::wait (time=18446744073709551615, this=0x55692d72bb00) at thread/qwaitcondition_unix.cpp:143 #4 QWaitCondition::wait (this=this@entry=0x55692a82e678, mutex=mutex@entry=0x55692a82e670, time=time@entry=18446744073709551615) at thread/qwaitcondition_unix.cpp:215 #5 0x7fb86c4d8b18 in QSGRenderThreadEventQueue::takeEvent (wait=true, this=0x55692a82e668) at scenegraph/qsgthreadedrenderloop.cpp:245 #6 QSGRenderThread::processEventsAndWaitForMore (this=this@entry=0x55692a82e5f0) at scenegraph/qsgthreadedrenderloop.cpp:709 #7 0x7fb86c4d8f4a in QSGRenderThread::run (this=0x55692a82e5f0) at scenegraph/qsgthreadedrenderloop.cpp:738 #8 0x7fb868e54adb in QThreadPrivate::start (arg=0x55692a82e5f0) at thread/qthread_unix.cpp:367 #9 0x7fb864e456db in start_thread (arg=0x7fb82110c700) at pthread_create.c:463 #10 0x7fb86874c88f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 12 (Thread 0x7fb82190d700 (LWP 8954)): #0 0x7fb864e4bed9 in futex_reltimed_wait_cancelable (private=, reltime=0x7fb82190cc30, expected=0, futex_word=0x55692d471570) at ../sysdeps/unix/sysv/linux/futex-internal.h:142 #1 __pthread_cond_wait_common (abstime=0x7fb82190cd00, mutex=0x55692d471520, cond=0x55692d471548) at pthread_cond_wait.c:533 #2 __pthread_cond_timedwait (cond=0x55692d471548, mutex=0x55692d471520, abstime=0x7fb82190cd00) at pthread_cond_wait.c:667 #3 0x7fb868e55880 in QWaitConditionPrivate::wait_relative (time=3, this=0x55692d471520) at thread/qwaitcondition_unix.cpp:133 #4 QWaitConditionPrivate::wait (time=3, this=0x55692d471520) at thread/qwaitcondition_unix.cpp:141 #5 QWaitCondition::wait (this=this@entry=0x55692a35ae80, mutex=mutex@entry=0x55692ab901b0, time=3) at thread/qwaitcondition_unix.cpp:215 #6 0x7fb868e4c28d in QThreadPoolThread::run (this=0x55692a35ae70) at thread/qthreadpool.cpp:146 #7 0x7fb868e54adb in QThreadPrivate::start (arg=0x55692a35ae70) at thread/qthread_unix.cpp:367 #8 0x7fb864e456db in start_thread (arg=0x7fb82190d700) at pthread_create.c:463 #9 0x7fb86874c88f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 11 (Thread 0x7fb82210e700 (LWP 8953)): #0 0x7fb862ca9f38 in g_main_context_check () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #1 0x7fb862caa4e0 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7fb862caa64c in g_main_context_iteration () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7fb86907a04b in QEventDispatcherGlib::processEvents (this=0x7fb81b20, flags=...) at kernel/qeventdispatcher_glib.cpp:424 #4 0x7fb86901e30a in QEventLoop::exec (this=this@entry=0x7fb82210dda0, flags=..., flags@entry=...) at kernel/qeventloop.cpp:214 #5 0x7fb868e49bba in QThread::exec (this=) at thread/qthread.cpp:525 #6 0x7fb868e54adb in QThreadPrivate::start (arg=0x55692a356d20) at thread/qthread_unix.cpp:367 #7 0x7fb864e456db in start_thread (arg=0x7fb82210e700) at pthread_create.c:463 #8 0x7fb86874c88f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 10 (Thread 0x7fb823fff700 (LWP 8952)): #0 0x7fb864e4bed9 in futex_reltimed_wait_cancelable (private=, reltime=0x7fb823ffec30, expected=0, futex_word=0x7fb81c005a20) at ../sysdeps/unix/sysv/linux/futex-internal.h:142 #1 __pthread_cond_wait_common (abstime=0x7fb823ffed00, mutex=0x7fb81c0059d0, cond=0x7fb81c0059f8) at pthread_cond_wait.c:533 #2 __pthread_cond_timedwait (cond=0x7fb81c0059f8, mutex=0x7fb81c0059d0,
[krita] [Bug 403614] * My Favorite folder bug
https://bugs.kde.org/show_bug.cgi?id=403614 --- Comment #2 from Ivan Jurasik --- Thanks Regards - Mail original - De: "Boudewijn Rempt" À: "ivanov ju" Envoyé: Samedi 26 Janvier 2019 09:27:19 Objet: [krita] [Bug 403614] * My Favorite folder bug https://bugs.kde.org/show_bug.cgi?id=403614 Boudewijn Rempt changed: What|Removed |Added Status|REPORTED|RESOLVED CC||b...@valdyas.org Resolution|--- |DUPLICATE --- Comment #1 from Boudewijn Rempt --- Fixed yesterday in b03f4ebbde9290db9c9f05539e1ca401fa579e42 *** This bug has been marked as a duplicate of bug 402749 *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 403652] [SDDM HiDPI] Inconsistent scaling factor between logged in or not
https://bugs.kde.org/show_bug.cgi?id=403652 --- Comment #6 from Albert --- (In reply to David Edmundson from comment #5) > There's going to be some inconsistency, we can't load your user settings if > we're not logged in. > > There's a way to set the DPI on SDDM. See the end of: > https://github.com/sddm/sddm readme I guess that it was what happened but maybe it's some bad implementation or bad point of view as a user. I can scale my UI inside my session but as a user i expect the SDDM re-scale automatically without any session. What I'm trying to say is that something as I cannot control should detect and load a predefined config. It's something similar as GTK and QT apps, until some new versions when I re-scale the apps on whole system in system-settings it doesn't force to re-scale GTK apps so I was forced to do it by files manually, from new frameworks or plasma(i don't know which versions) GTK and QT works together when some user re-scale its UI into its session. I think SDDM should detect how many pixels are in a main display and re-scale it automatically or maybe in system-settings gives the possibility to do it graphically. -- You are receiving this mail because: You are watching all bug changes.
[latte-dock] [Bug 403658] Latte freezes when switching the type of application menu
https://bugs.kde.org/show_bug.cgi?id=403658 --- Comment #3 from Michail Vourlakos --- (In reply to Viorel-Cătălin Răpițeanu from comment #2) > (In reply to Michail Vourlakos from comment #1) > > (In reply to Viorel-Cătălin Răpițeanu from comment #0) > > > > > > > strange, I tried to reproduce this and it works at all cases > > I observed that when you switch the menu on an ordinary Plasma panel, the > launcher flashes (the implementation might remove/add the new selected > launcher in the same position). yes I think is how it is done > I wondered what the Latte dock would do > since it locks itself right after you select an option. Wait for the launcer > to be replaced (if that's the implementation), then lock itself up? Latte does not lock itself, I dont know what you are describing > I admit however, I wasn't expecting a freeze for this case. > you probably did not understand me. In my system Latte Alternative option works fine at all cases. I can not reproduce this in my system. Please try with different layouts and options to check if this is happening always in your system. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 403639] Window_newView //unable to access new view drop down menu//
https://bugs.kde.org/show_bug.cgi?id=403639 --- Comment #3 from daniel --- Created attachment 117690 --> https://bugs.kde.org/attachment.cgi?id=117690=edit New view in a new window as it appears in two seperate tabs. Steps to recreate; //with one file open 1. New window 2. New view - whatever open file EXPECTED RESULT A new view within the original krita tab. Both windows an views simultaneously editable. OBSERVED RESULT A new view within a secondary non-merging krita tab. Both windows an views simultaneously editable. ADDITIONAL COMMENTS I'm not sure if this is relevant to my original bug report. I had seen others, in tutorial, access new view without using the new window function in order to produce a new view in one instance of krita. Me using new window as a function to access new view was a troubleshooting effort. But I'm still unsure if I am going about it correctly. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-qqc2-desktop-style] [Bug 394296] TabBar styling does not either draw a frame around the content area or touch the content area beneath it, which looks bad
https://bugs.kde.org/show_bug.cgi?id=394296 --- Comment #6 from David Edmundson --- >So the issue here is that the tab QQC2 tab bar should draw a frame (with >internal padding) around its content area, I don't think that's do-able out of the box in the theme. (QQC2's component is more like QTabBar than QTabWidget in QWidget terms) However, it's still do-able on the client side. I've just pushed a tabbar.qml in the tests folder of QQC2. I think it's spot-on. Let me know if there's any issues. Maybe we could/should wrap it all as one item somewhere, but not here. -- You are receiving this mail because: You are watching all bug changes.
[latte-dock] [Bug 401184] Latte Dock - Global Keyboard Shortcuts Stop Working / Multiple Entries Created
https://bugs.kde.org/show_bug.cgi?id=401184 Michail Vourlakos changed: What|Removed |Added Latest Commit|https://commits.kde.org/lat |https://commits.kde.org/lat |te-dock/46dd59b65a58f7f985c |te-dock/d0f1a7ffe6fb89a0da4 |905e951bf08e82270e6bf |7825d7208bf5c46dc67db --- Comment #9 from Michail Vourlakos --- Git commit d0f1a7ffe6fb89a0da47825d7208bf5c46dc67db by Michail Vourlakos. Committed on 27/01/2019 at 17:57. Pushed by mvourlakos into branch 'v0.8'. cleanup applet shortcuts on startup --when Latte crashes the global shortcuts from applets remain untouched in kglobalshortcutsrc file. That fact based on the Latte architecture that can alter applet ids during layout loading can break the global shortcuts experience by creating multiple global shortcuts records for the same applet and by disabling some shortcuts because these shortcuts are already enabled for ghost applets of the crashed layout. This patch fixes this by removing all applet global shortcuts during startup. Applet global shortcuts are already saved in the layout file based on the current plasma architecture, that fact simplifies things a lot. M +28 -0app/universalsettings.cpp M +3-0app/universalsettings.h https://commits.kde.org/latte-dock/d0f1a7ffe6fb89a0da47825d7208bf5c46dc67db -- You are receiving this mail because: You are watching all bug changes.
[konqueror] [Bug 384376] Konqueror crashing on start of Plasma Desktop
https://bugs.kde.org/show_bug.cgi?id=384376 --- Comment #17 from Carsten Jacobi --- Created attachment 117689 --> https://bugs.kde.org/attachment.cgi?id=117689=edit New crash information added by DrKonqi konqueror (5.0.97) using Qt 5.9.5 - What I was doing when the application crashed: The crash occurs right when I start the Plasma desktop. -- Backtrace (Reduced): #7 0xb7dab2d4 in KonqView::url() const () at /usr/lib/i386-linux-gnu/libkdeinit5_konqueror.so #8 0xb7de3b99 in KonqMainWindow::isPreloaded() const () at /usr/lib/i386-linux-gnu/libkdeinit5_konqueror.so #9 0xb7e1baf0 in KonqSessionManager::saveCurrentSessionToFile(KConfig*, QList const&) () at /usr/lib/i386-linux-gnu/libkdeinit5_konqueror.so #10 0xb7e1bd7a in KonqSessionManager::autoSaveSession() () at /usr/lib/i386-linux-gnu/libkdeinit5_konqueror.so #11 0xb7e2fe09 in () at /usr/lib/i386-linux-gnu/libkdeinit5_konqueror.so -- You are receiving this mail because: You are watching all bug changes.
[latte-dock] [Bug 403658] Latte freezes when switching the type of application menu
https://bugs.kde.org/show_bug.cgi?id=403658 --- Comment #2 from Viorel-Cătălin Răpițeanu --- (In reply to Michail Vourlakos from comment #1) > (In reply to Viorel-Cătălin Răpițeanu from comment #0) > > > > strange, I tried to reproduce this and it works at all cases I observed that when you switch the menu on an ordinary Plasma panel, the launcher flashes (the implementation might remove/add the new selected launcher in the same position). I wondered what the Latte dock would do since it locks itself right after you select an option. Wait for the launcer to be replaced (if that's the implementation), then lock itself up? I admit however, I wasn't expecting a freeze for this case. P.S.: I don't know how the switching is really made. (haven't looked at the code yet). -- You are receiving this mail because: You are watching all bug changes.
[konqueror] [Bug 384376] Konqueror crashing on start of Plasma Desktop
https://bugs.kde.org/show_bug.cgi?id=384376 Carsten Jacobi changed: What|Removed |Added CC||cars...@ccac.rwth-aachen.de -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 403652] [SDDM HiDPI] Inconsistent scaling factor between logged in or not
https://bugs.kde.org/show_bug.cgi?id=403652 --- Comment #5 from David Edmundson --- There's going to be some inconsistency, we can't load your user settings if we're not logged in. There's a way to set the DPI on SDDM. See the end of: https://github.com/sddm/sddm readme -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 403623] In desktop-grid effect cannot move a window between desktops with mouse drag action
https://bugs.kde.org/show_bug.cgi?id=403623 David Edmundson changed: What|Removed |Added Resolution|--- |FIXED Status|REPORTED|RESOLVED --- Comment #4 from David Edmundson --- Should be fixed then. Please reopen if it's an issue in 5.15.0 -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 403595] Icon request: histogram in LabPlot
https://bugs.kde.org/show_bug.cgi?id=403595 Nate Graham changed: What|Removed |Added CC||n...@kde.org --- Comment #3 from Nate Graham --- If you don't already know about it, allow me to introduce you to the Cuttlefish icon viewer app. It's really quite handy for browsing icons. -- You are receiving this mail because: You are watching all bug changes.
[latte-dock] [Bug 403658] Latte freezes when switching the type of application menu
https://bugs.kde.org/show_bug.cgi?id=403658 --- Comment #1 from Michail Vourlakos --- (In reply to Viorel-Cătălin Răpițeanu from comment #0) > strange, I tried to reproduce this and it works at all cases -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 403649] Filesystem changes are not visible in album view
https://bugs.kde.org/show_bug.cgi?id=403649 caulier.gil...@gmail.com changed: What|Removed |Added CC||caulier.gil...@gmail.com --- Comment #2 from caulier.gil...@gmail.com --- As, Maik said, i just tested with 6.0.0-beta3, and problem is not reproducible here too with this pre-release version... Gilles Caulier -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 341589] Cannot assign tag to a split
https://bugs.kde.org/show_bug.cgi?id=341589 Thomas Baumgart changed: What|Removed |Added Severity|minor |wishlist --- Comment #2 from Thomas Baumgart --- Work is underway. If you compile yourself, want to be a bit adventurous and set the ENABLE_UNFINISHEDFEATURES build variable to ON, then you can check out a new ledger view and a new transaction editor which among other new features allows setting the tag per split. It is not finished and not ready for production use yet. You can find this on the master branch of the development. -- You are receiving this mail because: You are watching all bug changes.
[kdelibs] [Bug 212268] Writing a HTML message it produces paragraphs without margins.
https://bugs.kde.org/show_bug.cgi?id=212268 --- Comment #4 from Mike Goodwin --- Possibly related: https://bugs.kde.org/show_bug.cgi?id=358476 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 403652] [SDDM HiDPI] Inconsistent scaling factor between logged in or not
https://bugs.kde.org/show_bug.cgi?id=403652 Albert changed: What|Removed |Added Attachment #117674|0 |1 is obsolete|| --- Comment #4 from Albert --- Created attachment 117688 --> https://bugs.kde.org/attachment.cgi?id=117688=edit SDDD (user loged in) whole view -- You are receiving this mail because: You are watching all bug changes.
[kdelibs] [Bug 212268] Writing a HTML message it produces paragraphs without margins.
https://bugs.kde.org/show_bug.cgi?id=212268 Mike Goodwin changed: What|Removed |Added CC||m...@mgoodwin.net --- Comment #3 from Mike Goodwin --- This bug is absolutely still valid and has been for some 10 years.. It makes sending/receiving HTML emails a chore in the workplace because if you use KMail to do it, your emails look like they're written by a child. (i.e. unprofessional) Example Business email: --- Hi Mark, Thanks for sending me that info Regards, - Mike Becomes: Hi Mark, Thanks for sending me that info Regads, - Mike When read by any modern client (for me Outlook, Roundcube, Rainloop and Gmail all render Kmail's sent HTML like this) There are also numerous reports on the forums about this issue. Is there any way we can get this bug to the right place to finally gain some traction? It's really the only thing left in my personal list of wants that KMail needs for me to use it exclusively (right now if I'm not sending TEXT email, I have to go use rainloop if I want properly formatted emails). I'm truly baffled as to how this is still a bug. Here's an updated list of possibly related software versions that the bug can be bumped to: kdepim-addons-18.08.3-1.fc29.x86_64 kdepim-runtime-libs-18.08.3-1.fc29.x86_64 kf5-libkdepim-18.08.3-1.fc29.x86_64 kdepim-apps-libs-18.08.3-1.fc29.x86_64 kf5-kmailtransport-akonadi-18.08.3-1.fc29.x86_64 kdepim-runtime-18.08.3-1.fc29.x86_64 kmail-libs-18.08.3-1.fc29.x86_64 kf5-libkdepim-akonadi-18.08.3-1.fc29.x86_64 kf5-kmailtransport-18.08.3-1.fc29.x86_64 kdepimlibs-4.14.10-29.fc29.x86_64 kdepimlibs-gpgme-4.14.10-29.fc29.x86_64 kdepimlibs-kxmlrpcclient-4.14.10-29.fc29.x86_64 kdepim-common-17.12.3-2.fc29.x86_64 kmail-account-wizard-18.08.3-1.fc29.x86_64 kdepimlibs-akonadi-4.14.10-29.fc29.x86_64 kmail-18.08.3-1.fc29.x86_64 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 403653] Random, complete desktop crashes when Wayland is used
https://bugs.kde.org/show_bug.cgi?id=403653 --- Comment #1 from johan --- Created attachment 117687 --> https://bugs.kde.org/attachment.cgi?id=117687=edit Core dump information Another crash. Again only drkonqi appeared in core dumps. -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 397094] Scheduled transaction date keeps incrementing to current date in ledger
https://bugs.kde.org/show_bug.cgi?id=397094 Jack changed: What|Removed |Added Resolution|WAITINGFORINFO |WORKSFORME Status|NEEDSINFO |RESOLVED CC|ostroffjh@users.sourceforge | |.net| --- Comment #13 from Jack --- George, I'm still not sure exactly what the problem is. When a scheduled transaction is actually entered, it becomes a real transaction in the relevant account, and you can do anything with it that you can do with any other transaction. Before that, it is only a scheduled transaction, and although it is displayed in the relevant ledgers, you cannot edit it there until it has been entered. Up until the scheduled date, it should show the scheduled date, but after that date, since it has not been entered yet, it shows the current date, which will be the date of the transaction if entered then. I'm going to close this as WORKSFORME, but do reopen it if the problem happens again, especially if you can provide more details about what seems wrong. -- You are receiving this mail because: You are watching all bug changes.
[konversation] [Bug 403654] Konversation crashed on shutdown
https://bugs.kde.org/show_bug.cgi?id=403654 --- Comment #1 from johan --- Created attachment 117686 --> https://bugs.kde.org/attachment.cgi?id=117686=edit Core dump information -- You are receiving this mail because: You are watching all bug changes.
[frameworks-solid] [Bug 270808] External hard disks should be spun down when 'safely removed'
https://bugs.kde.org/show_bug.cgi?id=270808 --- Comment #68 from Vincas Dargis --- External HDD now spins down in Debian Buster! Thanks! -- You are receiving this mail because: You are watching all bug changes.
[Oxygen] [Bug 403661] user-online icon is non-standard, and user-available is missing
https://bugs.kde.org/show_bug.cgi?id=403661 --- Comment #1 from JanKusanagi --- And yes, I realize that spec is really outdated and seems to be comatose, but I guess the issue with this specific icon still applies xD I wonder what happened to that spec, being as important as it is... :( -- You are receiving this mail because: You are watching all bug changes.
[Oxygen] [Bug 403661] New: user-online icon is non-standard, and user-available is missing
https://bugs.kde.org/show_bug.cgi?id=403661 Bug ID: 403661 Summary: user-online icon is non-standard, and user-available is missing Product: Oxygen Version: 5.14.5 Platform: Mageia RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: icons Assignee: n...@oxygen-icons.org Reporter: jan-b...@gmx.co.uk Target Milestone: --- SUMMARY oxygen-icons provides a "user-online" icon that's the opposite of "user-offline", but as per the the icon naming spec https://specifications.freedesktop.org/icon-naming-spec/icon-naming-spec-latest.html there's no "user-online" defined, but there is one "user-available" that seems to fit the purpose. I've tested several other common icon themes, and they don't have user-online, and have the standardized user-available. Except for Breeze, which for completeness, I guess, provides both. Just copying or symlinking user-online to user-available would be more than enough. Thanks for your time. Oxygen rocks! STEPS TO REPRODUCE 1. N/A OBSERVED RESULT Oxygen iconset doesn't provide the standard user-available icon. EXPECTED RESULT user-available icon should be provided, by copying or symlinking the existing user-online. SOFTWARE/OS VERSIONS Operating System: Mageia 7 KDE Plasma Version: 5.14.5 Qt Version: 5.12.0 KDE Frameworks Version: 5.54.0 -- You are receiving this mail because: You are watching all bug changes.
[Oxygen] [Bug 403661] user-online icon is non-standard, and user-available is missing
https://bugs.kde.org/show_bug.cgi?id=403661 JanKusanagi changed: What|Removed |Added CC||jan-b...@gmx.co.uk -- You are receiving this mail because: You are watching all bug changes.
[kirigami gallery] [Bug 403660] Always displays the Material style
https://bugs.kde.org/show_bug.cgi?id=403660 Nate Graham changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=403659 -- You are receiving this mail because: You are watching all bug changes.
[kirigami gallery] [Bug 403659] Need a way to change the style from within the app itself
https://bugs.kde.org/show_bug.cgi?id=403659 Nate Graham changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=403660 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-qqc2-desktop-style] [Bug 394296] TabBar styling does not either draw a frame around the content area or touch the content area beneath it, which looks bad
https://bugs.kde.org/show_bug.cgi?id=394296 --- Comment #5 from Nate Graham --- ...Which is now fixed. So the issue here is that the tab QQC2 tab bar should draw a frame (with internal padding) around its content area, just like the QQC1 and QWidgets versions do/did. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 374575] "Shortcut for switching to this activity" has no effect when set from the Activities KCM
https://bugs.kde.org/show_bug.cgi?id=374575 Ville Aakko changed: What|Removed |Added CC||ville.aa...@gmail.com --- Comment #14 from Ville Aakko --- Hi, Shortcuts to switching X activity still do not sometimes work. FWIW, I originally set my shortcuts keys as suggested by Ivan - didn't even know it is possible to do the way as in original report. Ivans workaroung works, but only for after a few reboots, after shortcut keys stop working again. (Plasmashell 5.14.5 on Arch Linux) -- You are receiving this mail because: You are watching all bug changes.
[frameworks-qqc2-desktop-style] [Bug 394295] TabBar tabs don't connect with the line below them
https://bugs.kde.org/show_bug.cgi?id=394295 Nate Graham changed: What|Removed |Added Resolution|--- |FIXED Status|CONFIRMED |RESOLVED --- Comment #3 from Nate Graham --- Hmm, can no longer reproduce in any context. Looks like this is fixed! -- You are receiving this mail because: You are watching all bug changes.
[kirigami gallery] [Bug 403660] Always displays the Material style
https://bugs.kde.org/show_bug.cgi?id=403660 --- Comment #1 from Nate Graham --- Workaround: run `QT_QUICK_CONTROLS_STYLE=org.kde.desktop kirigami2gallery` from the command line. -- You are receiving this mail because: You are watching all bug changes.
[kirigami gallery] [Bug 403660] New: Always displays the Material style
https://bugs.kde.org/show_bug.cgi?id=403660 Bug ID: 403660 Summary: Always displays the Material style Product: kirigami gallery Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: notm...@gmail.com Reporter: n...@kde.org Target Milestone: --- It used to be that if you opened Kirigami Gallery via the CLI, it displayed the material style, but if you opened it from KRunner or a Plasma launcher, it used the Breeze style. This doesn't happen anymore; now it always uses the Material style no matter how it's launched. See also Bug 403659. -- You are receiving this mail because: You are watching all bug changes.
[kirigami gallery] [Bug 403659] New: Need a way to change the style from within the app itself
https://bugs.kde.org/show_bug.cgi?id=403659 Bug ID: 403659 Summary: Need a way to change the style from within the app itself Product: kirigami gallery Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: notm...@gmail.com Reporter: n...@kde.org Target Milestone: --- Right now there isn't a way to change the visual style of the app itself from *within* the app. There should be. :) -- You are receiving this mail because: You are watching all bug changes.
[latte-dock] [Bug 403658] New: Latte freezes when switching the type of application menu
https://bugs.kde.org/show_bug.cgi?id=403658 Bug ID: 403658 Summary: Latte freezes when switching the type of application menu Product: latte-dock Version: git (master) Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: library Assignee: mvourla...@gmail.com Reporter: rapiteanu.cata...@gmail.com Target Milestone: --- SUMMARY Latte freezes when you're switching the type of menu from a Latte panel. STEPS TO REPRODUCE 1. Create a Latte panel 2. Add an application menu launcher to the panel 3. Enter into the 'Dock/Panel Settings' 4. Right click the application menu launcher and select 'Alternatives' 5. Select a different type of application menu OBSERVED RESULT Latte freezes. When you restart the dock, the application menu launcher either dissapears or it's placed in a different position. EXPECTED RESULT The menu should be switch without any issues. SOFTWARE/OS VERSIONS Linux/KDE Plasma: 5.14.90 KDE Plasma Version: 5.14.90 KDE Frameworks Version: 5.54.0 Qt Version: 5.12.0-3 -- You are receiving this mail because: You are watching all bug changes.
[skrooge] [Bug 403575] skrooge w/ -DSKG_WEBENGINE=ON: ui_skgtablewithgraph.h:15:10: fatal error: QtWebKitWidgets/QWebView: No such file or directory
https://bugs.kde.org/show_bug.cgi?id=403575 Stephane MANKOWSKI changed: What|Removed |Added Resolution|--- |FIXED Status|ASSIGNED|RESOLVED Latest Commit||https://commits.kde.org/skr ||ooge/dab0fd4adf2cbee89a417c ||483350ddffda77ed3b --- Comment #1 from Stephane MANKOWSKI --- Git commit dab0fd4adf2cbee89a417c483350ddffda77ed3b by Stephane MANKOWSKI. Committed on 27/01/2019 at 16:13. Pushed by smankowski into branch 'master'. skrooge w/ -DSKG_WEBENGINE=ON: ui_skgtablewithgraph.h:15:10: fatal error: QtWebKitWidgets/QWebView: No such file or directory M +1-0CHANGELOG M +0-6skgbasegui/skgtablewithgraph.ui https://commits.kde.org/skrooge/dab0fd4adf2cbee89a417c483350ddffda77ed3b -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 341589] Cannot assign tag to a split
https://bugs.kde.org/show_bug.cgi?id=341589 mau changed: What|Removed |Added CC||b-m...@gmx.ch --- Comment #1 from mau --- Any news on this feature? I'd appreciate it as well :-) -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 403644] kdev-cmake : commit 7a16881ec33f4af2028593c2b3da7c1e20bf53c6 breaks fallback to non-server mode
https://bugs.kde.org/show_bug.cgi?id=403644
RJVB changed:
What|Removed |Added
Assignee|kdevelop-bugs-n...@kde.org |rjvber...@gmail.com
--- Comment #1 from RJVB ---
1). Doesn't happen on Linux
2) I think I have identified the stale QObject instance. It seems to be
CMakeServer::m_process .
Here's a fresh bit of backtrace:
```
(lldb) bt
* thread #1, queue = 'com.apple.main-thread', stop reason = EXC_BAD_ACCESS
(code=EXC_I386_GPFLT)
frame #0: 0x0001096d7ad4
QtQml`QQmlData::isSignalConnected(d=0xe4c1490467634d38,
(null)=0x078b480774ff8548, index=) at qqmlengine.cpp:869 [opt]
frame #1: 0x00010ba4f6aa QtCore`QMetaObject::activate(QObject*, int,
int, void**) [inlined]
QObjectPrivate::isDeclarativeSignalConnected(signal_index=) const
at qobject_p.h:266 [opt]
* frame #2: 0x00010ba4f68c
QtCore`QMetaObject::activate(sender=0x7f9c465272c0,
signalOffset=, local_signal_index=,
argv=0x7fff585b0a90) at qobject.cpp:3647 [opt]
frame #3: 0x00010b9a8772 QtCore`QProcessPrivate::_q_processDied()
[inlined] QProcess::finished(_t1=1, _t1=, _t2=NormalExit,
_t2=) at moc_qprocess.cpp:334 [opt]
frame #4: 0x00010b9a8746
QtCore`QProcessPrivate::_q_processDied(this=0x7f9c46527ac0) at
qprocess.cpp:1181 [opt]
```
and here is the corresponding terminal output after adding a few trace qWarning
calls to cmakemanager.cpp and cmakeserver.cpp:
```
kdevplatform.serialization: version mismatch or no version hint; expected
version: 84082945
kdevplatform.serialization: "The data-repository at
/Users/bertin/.cache/kdevduchain/kdevelop-{b9a8d6dc-6d10-4bc1-955f-831c48d4ae34}
has to be cleared."
kdevplatform.shell: Starting project import timer
CMakeServer::CMakeServer(KDevelop::IProject *) cmake server process:
QProcess(0x7f9c465272c0)
virtual void ChooseCMakeInterfaceJob::start() CMakeServer:
CMakeServer(0x7f9c465272a0)
CMake Error: cmake version 3.0.1 (faked to avoid server mode)
Usage: /opt/local/bin/cmake -E [command] [arguments ...]
void ChooseCMakeInterfaceJob::failedConnection(int) disconnecting
CMakeServer(0x7f9c465272a0)
virtual CMakeServer::~CMakeServer() CMakeServer(0x7f9c465272a0)
QProcess(0x7f9c465272c0)
kdevelop.plugins.cmake: CMake server not available, using compile_commands.json
to import "lzvn (MP)"
```
The error here appears to be deleting the QProcess for cmake before that
process has had a chance to terminate on its own. Killing a cmake subprocess
has always been more likely to crash on Mac than on Linux, IIRC.
Here, there are 2 lines in ChooseCMakeInterfaceJob::failedConnection() that
have been carried over from the pre-QSharedPointer implementation which lead to
deleting the CMakeServer:
1) server->deleteLater(), which is apparently executed immediately here (the
cmake server availability warning is printed just after the server instance
reset)
2) server = nullptr, which deletes the QSharedPointer's pointer if not shared
Deleting both lines resolve the crash, and as mentioned in the 7a16881 commit
message, "QSharedPointer will try to delete it [the CMakeServer instance]
eventually".
If there are no objections I will push the fix soon (say by tomorrow).
--
You are receiving this mail because:
You are watching all bug changes.
[konsole] [Bug 382947] Super keys update konsole viewport
https://bugs.kde.org/show_bug.cgi?id=382947 --- Comment #7 from steini2000 --- Confirming. Also works for me now. Same version as Marco. -- You are receiving this mail because: You are watching all bug changes.
[latte-dock] [Bug 403647] Latte crashes when using hotkeys
https://bugs.kde.org/show_bug.cgi?id=403647 --- Comment #9 from Michail Vourlakos --- (In reply to trmdi from comment #8) > Yes, it does not crash anymore. > But now there are two issues: > - shortcut badges are too small. See my screenshot: > https://i.imgur.com/EBMigNo.png (Item size = 32px) ok, in last commit I added 24px. as minimum height in order to not get too narrow with no reason > - pressing shortcuts does not trigger anything with my layout. It works with > your layout. fixed, no entries activation works immediately after startup -- You are receiving this mail because: You are watching all bug changes.
[lokalize] [Bug 403262] Crash of lokalize during resizing sub windows in edit tab
https://bugs.kde.org/show_bug.cgi?id=403262 Simon Depiets changed: What|Removed |Added Status|REPORTED|NEEDSINFO Resolution|--- |WORKSFORME --- Comment #3 from Simon Depiets --- Closing as cannot reproduce -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 403657] New: Audacity goes into infinite loop on KDE neon
https://bugs.kde.org/show_bug.cgi?id=403657 Bug ID: 403657 Summary: Audacity goes into infinite loop on KDE neon Product: neon Version: unspecified Platform: Neon Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Packages User Edition Assignee: neon-b...@kde.org Reporter: nemon...@gmail.com CC: j...@jriddell.org, neon-b...@kde.org, sit...@kde.org Target Milestone: --- SUMMARY Audacity could not start because of pango_font_description_set_size issue. STEPS TO REPRODUCE 1. Install audacity (pkcon install audacity, or apt instal audacity) 2. run audacity from Terminal 3. There's an error, infinite loop. OBSERVED RESULT (Audacity:14491): Pango-CRITICAL **: 23:25:13.271: pango_font_description_set_size: assertion 'size >= 0' failed (infinite loop goes on..) EXPECTED RESULT Runs well? SOFTWARE/OS VERSIONS Linux/KDE Plasma: KDE Neon User Edition KDE Plasma Version: 5.14.5 KDE Frameworks Version: 5.54.0 Qt Version: 5.11.2 ADDITIONAL INFORMATION Audacity(2.2.1 from Ubuntu repository) works well on Kubuntu 18.04 and 18.10. Only KDE Neon has this issue. However, there's a Snap package for Audacity the version of which is 2.3.0, works on KDE Neon. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 402843] Holdiays on digital clock crash plasmashell
https://bugs.kde.org/show_bug.cgi?id=402843 Darin Miller changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 402843] Holdiays on digital clock crash plasmashell
https://bugs.kde.org/show_bug.cgi?id=402843 --- Comment #2 from Darin Miller --- Holidays are now working again in Plasma 5.15.80. Closing bug. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 402646] kdeinit5 crash every startup.
https://bugs.kde.org/show_bug.cgi?id=402646 Andy Great changed: What|Removed |Added Ever confirmed|0 |1 Resolution|WORKSFORME |--- Status|RESOLVED|REOPENED --- Comment #3 from Andy Great --- The problem is back for some reason. How do I "confirm that it's loading the write file.so KIO"? I don't have knowledge about this. Not sure if the report is the same but here: Application: kdeinit5 (kdeinit5), signal: Aborted Using host libthread_db library "/lib64/libthread_db.so.1". [KCrash Handler] #6 0x7f35a28d008b in raise () from /lib64/libc.so.6 #7 0x7f35a28b94e9 in abort () from /lib64/libc.so.6 #8 0x7f35a2ce999d in qt_message_fatal (context=..., message=...) at global/qlogging.cpp:1901 #9 QMessageLogger::fatal (this=this@entry=0x7ffd0e7e55a0, msg=msg@entry=0x7f359e18a7f8 "Fatal Error: Got cmd %d, while waiting for an answer!") at global/qlogging.cpp:887 #10 0x7f359e0b954f in KIO::SlaveBase::waitForAnswer (this=this@entry=0x7ffd0e7e5a60, expected1=expected1@entry=84, expected2=expected2@entry=65, data=..., pCmd=pCmd@entry=0x7ffd0e7e5614) at /usr/include/qt5/QtCore/qlogging.h:91 #11 0x7f359e0ba775 in KIO::SlaveBase::canResume (this=0x7ffd0e7e5a60, offset=12289) at /usr/src/debug/kio-5.54.0-1.1.x86_64/src/core/slavebase.cpp:998 #12 0x7f359e012ad4 in FileProtocol::put (this=0x7ffd0e7e5a50, url=..., _mode=-1, _flags=...) at /usr/src/debug/kio-5.54.0-1.1.x86_64/src/ioslaves/file/file.cpp:600 #13 0x7f359e0bf80b in KIO::SlaveBase::dispatch (this=0x7ffd0e7e5a60, command=68, data=...) at /usr/src/debug/kio-5.54.0-1.1.x86_64/src/core/slavebase.cpp:1155 #14 0x7f359e0c0016 in KIO::SlaveBase::dispatchLoop (this=0x7ffd0e7e5a60) at /usr/src/debug/kio-5.54.0-1.1.x86_64/src/core/slavebase.cpp:325 #15 0x7f359e011109 in kdemain (argc=, argv=) at /usr/src/debug/kio-5.54.0-1.1.x86_64/src/ioslaves/file/file.cpp:112 #16 0x55e3620dabf7 in launch (argc=4, _name=0x55e362c6ea78 "/usr/lib64/qt5/plugins/kf5/kio/file.so", args=, cwd=, envc=0, envs=, reset_env=false, tty=0x0, avoid_loops=false, startup_id_str=0x55e3620de173 "0") at /usr/src/debug/kinit-5.54.0-1.1.x86_64/src/kdeinit/kinit.cpp:706 #17 0x55e3620dbc2a in handle_launcher_request (sock=8, who=) at /usr/src/debug/kinit-5.54.0-1.1.x86_64/src/kdeinit/kinit.cpp:1146 #18 0x55e3620dc548 in handle_requests (waitForPid=0) at /usr/src/debug/kinit-5.54.0-1.1.x86_64/src/kdeinit/kinit.cpp:1339 #19 0x55e3620d75b5 in main (argc=5, argv=) at /usr/src/debug/kinit-5.54.0-1.1.x86_64/src/kdeinit/kinit.cpp:1785 [Inferior 1 (process 11126) detached] -- You are receiving this mail because: You are watching all bug changes.
[latte-dock] [Bug 403656] New: [feature] - identify applets shortcuts and use those for the ShortcutBadges if they are present
https://bugs.kde.org/show_bug.cgi?id=403656 Bug ID: 403656 Summary: [feature] - identify applets shortcuts and use those for the ShortcutBadges if they are present Product: latte-dock Version: git (master) Platform: Other OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: application Assignee: mvourla...@gmail.com Reporter: mvourla...@gmail.com Target Milestone: --- Latte could identify the applets global shortcuts and use those for the badges present to the user when the user chooses the Meta+` shortcut -- You are receiving this mail because: You are watching all bug changes.
[kaddressbook] [Bug 398847] Kaddressbook not parsing gmail contacts
https://bugs.kde.org/show_bug.cgi?id=398847 rev...@gmail.com changed: What|Removed |Added CC||rev...@gmail.com --- Comment #13 from rev...@gmail.com --- Confirmed here Fedora 29 Kontact 5.9.3 KDE Workspaces 5.53.0 -- You are receiving this mail because: You are watching all bug changes.
[latte-dock] [Bug 401184] Latte Dock - Global Keyboard Shortcuts Stop Working / Multiple Entries Created
https://bugs.kde.org/show_bug.cgi?id=401184 --- Comment #8 from Michail Vourlakos --- (In reply to scum.filter+kde from comment #5) > (In reply to Michail Vourlakos from comment #4) > > I think I fixed it but you should try the git version in order to confirm that it is fixed. The previous explanation of the reason is faulty. Plasma applets are already saving their shortcuts in their configuration so the shortcuts are already present in the latte layout files. The issues arises when Latte is crashed. In such case the applets global shortcuts are not loaded properly from Plasma Global Shortcuts module. Simple fix is that during Latte startup all Latte applets shortcuts are removed and when the Latte layout is loaded then the plasma applets are doing their job properly by just adding their shortcuts which is the normal behavior. That of course means that if you try this patch it would mean that by just restaring Latte all your applets shortcuts will be fixed by their own!!! :) Please if you can try out the git version to confirm the fix it would help me a lot because in that way I could apply this patch also for next Latte stable version 0.8.6 -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 397094] Scheduled transaction date keeps incrementing to current date in ledger
https://bugs.kde.org/show_bug.cgi?id=397094 --- Comment #12 from George --- Thomas, My scheduled transactions are all set up exactly as you outlined in your stream of emails. I only have an issue once in a while (still trying to figure out pattern) and only with a single schedule (I probably have 20-30 set up). I have 2 scheduled transactions set up as loan repayments and the problem appears to be related to that. Actually, I said I only had an issue with a single schedule, but the two loan schedules are very similar, so it could be either one or both of those. Either way, I have no issues with other types of transactions. At this point I'm thinking of just eliminating this type of scheduled transaction and making it a simple withdrawal or transfer. I don't require any further action from you on my behalf. I'm going to leave it as-is for now. If I see this happen again I'll try to note all the circumstances and forward to you. Thanks for looking into this. George On 1/27/19 8:59 AM, Thomas Baumgart wrote: > https://bugs.kde.org/show_bug.cgi?id=397094 > > --- Comment #11 from Thomas Baumgart --- > Created attachment 117685 >--> https://bugs.kde.org/attachment.cgi?id=117685=edit > Updated schedule > > Since the transaction was entered, the schedule was updated to the next due > date. The question now is: what is the problem? For me everything works as > designed. > -- You are receiving this mail because: You are watching all bug changes.
[latte-dock] [Bug 401184] Latte Dock - Global Keyboard Shortcuts Stop Working / Multiple Entries Created
https://bugs.kde.org/show_bug.cgi?id=401184 Michail Vourlakos changed: What|Removed |Added Resolution|--- |FIXED Status|CONFIRMED |RESOLVED Latest Commit||https://commits.kde.org/lat ||te-dock/46dd59b65a58f7f985c ||905e951bf08e82270e6bf --- Comment #7 from Michail Vourlakos --- Git commit 46dd59b65a58f7f985c905e951bf08e82270e6bf by Michail Vourlakos. Committed on 27/01/2019 at 14:06. Pushed by mvourlakos into branch 'master'. cleanup applet shortcuts on startup --when Latte crashes the global shortcuts from applets remain untouched in kglobalshortcutsrc file. That fact based on the Latte architecture that can alter applet ids during layout loading can break the global shortcuts experience by creating multiple global shortcuts records for the same applet and by disabling some shortcuts because these shortcuts are already enabled for ghost applets of the crashed layout. This patch fixes this by removing all applet global shortcuts during startup. Applet global shortcuts are already saved in the layout file based on the current plasma architecture, that fact simplifies things a lot. M +21 -0app/settings/universalsettings.cpp M +2-0app/settings/universalsettings.h https://commits.kde.org/latte-dock/46dd59b65a58f7f985c905e951bf08e82270e6bf -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 397094] Scheduled transaction date keeps incrementing to current date in ledger
https://bugs.kde.org/show_bug.cgi?id=397094 --- Comment #11 from Thomas Baumgart --- Created attachment 117685 --> https://bugs.kde.org/attachment.cgi?id=117685=edit Updated schedule Since the transaction was entered, the schedule was updated to the next due date. The question now is: what is the problem? For me everything works as designed. -- You are receiving this mail because: You are watching all bug changes.
