[digikam] [Bug 411696] Cannot launch digikam-6.3.0-x86-64.appimage in Kubuntu 14.04
https://bugs.kde.org/show_bug.cgi?id=411696 caulier.gil...@gmail.com changed: What|Removed |Added Status|REPORTED|RESOLVED Version Fixed In||6.4.0 Resolution|--- |INTENTIONAL --- Comment #1 from caulier.gil...@gmail.com --- Until 6.1.0, we compile AppImage using CentoOS 6. Since 6.2.0, AppImage use a more recent Linux because code require a more recent set of libraries and compiler tools. Centos6 as too old ans it's become the hell to maintain. So, Kubuntu 14.04 is certainly too old to run this new bundle version. It must work on Kubuntu 16.04 LTS at least (not tested here) Gilles Caulier -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 411696] Cannot launch digikam-6.3.0-x86-64.appimage in Kubuntu 14.04
https://bugs.kde.org/show_bug.cgi?id=411696 caulier.gil...@gmail.com changed: What|Removed |Added CC||caulier.gil...@gmail.com Severity|critical|normal Platform|Other |Appimage -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 411251] KWin crashed while navigating with keyboard shortcuts
https://bugs.kde.org/show_bug.cgi?id=411251 --- Comment #2 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.
[kmail2] [Bug 409301] not possible to customize pop account
https://bugs.kde.org/show_bug.cgi?id=409301 --- Comment #5 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.
[kwin] [Bug 410521] Error resuming Pc with Nvidia
https://bugs.kde.org/show_bug.cgi?id=410521 Bug Janitor Service changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|BACKTRACE |WORKSFORME --- Comment #3 from Bug Janitor Service --- This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now 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 Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 403730] minimap accesses invalid text line (std::out_of_range exception)
https://bugs.kde.org/show_bug.cgi?id=403730 --- Comment #5 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.
[frameworks-syntax-highlighting] [Bug 385154] [PATCH] Incorrect and incomplete syntax highlighting file for Oracle sql
https://bugs.kde.org/show_bug.cgi?id=385154 --- Comment #7 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.
[frameworks-syntax-highlighting] [Bug 400345] [PATCH] perl syntax highlighting: add labels
https://bugs.kde.org/show_bug.cgi?id=400345 --- Comment #3 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.
[frameworks-syntax-highlighting] [Bug 370459] [New Syntax] Could you add ats mode for kate?
https://bugs.kde.org/show_bug.cgi?id=370459 --- Comment #6 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.
[digikam] [Bug 411696] New: Cannot launch digikam-6.3.0-x86-64.appimage in Kubuntu 14.04
https://bugs.kde.org/show_bug.cgi?id=411696 Bug ID: 411696 Summary: Cannot launch digikam-6.3.0-x86-64.appimage in Kubuntu 14.04 Product: digikam Version: 6.3.0 Platform: Other OS: Linux Status: REPORTED Severity: critical Priority: NOR Component: Bundle-AppImage Assignee: digikam-bugs-n...@kde.org Reporter: vvoodstoc...@gmail.com Target Milestone: --- SUMMARY STEPS TO REPRODUCE 1. Enable execute bit in digikam-6.3.0-x86-64.appimage 2. Launch either via double-click or CLI ($ ./digikam-6.3.0-x86-64.appimage) OBSERVED RESULT via Desktop double click: Nothing. Silent crash, no feedback via CLI: $ ./digikam-6.3.0-x86-64.appimage -- digiKam Linux AppImage Bundle -- Use 'help' as CLI argument to know all available options for digiKam application. -- Note: to integrate this bundle to your desktop, use AppImageLauncher. libudev.so.0 -- Preloading shared libs: digikam: /usr/lib/x86_64-linux-gnu/libstdc++.so.6: version `CXXABI_1.3.8' not found (required by /tmp/.mount_digikaDMUXXh/usr/lib/libdigikamcore.so.6.3.0) digikam: /usr/lib/x86_64-linux-gnu/libstdc++.so.6: version `GLIBCXX_3.4.20' not found (required by /tmp/.mount_digikaDMUXXh/usr/lib/libdigikamcore.so.6.3.0) digikam: /usr/lib/x86_64-linux-gnu/libstdc++.so.6: version `GLIBCXX_3.4.21' not found (required by /tmp/.mount_digikaDMUXXh/usr/lib/libdigikamcore.so.6.3.0) digikam: /usr/lib/x86_64-linux-gnu/libstdc++.so.6: version `CXXABI_1.3.8' not found (required by /tmp/.mount_digikaDMUXXh/usr/lib/libdigikamdatabase.so.6.3.0) digikam: /usr/lib/x86_64-linux-gnu/libstdc++.so.6: version `GLIBCXX_3.4.21' not found (required by /tmp/.mount_digikaDMUXXh/usr/lib/libdigikamdatabase.so.6.3.0) digikam: /usr/lib/x86_64-linux-gnu/libstdc++.so.6: version `CXXABI_1.3.8' not found (required by /tmp/.mount_digikaDMUXXh/usr/lib/libdigikamgui.so.6.3.0) digikam: /usr/lib/x86_64-linux-gnu/libstdc++.so.6: version `GLIBCXX_3.4.20' not found (required by /tmp/.mount_digikaDMUXXh/usr/lib/libdigikamgui.so.6.3.0) digikam: /usr/lib/x86_64-linux-gnu/libstdc++.so.6: version `GLIBCXX_3.4.21' not found (required by /tmp/.mount_digikaDMUXXh/usr/lib/libdigikamgui.so.6.3.0) digikam: /usr/lib/x86_64-linux-gnu/libstdc++.so.6: version `CXXABI_1.3.9' not found (required by /tmp/.mount_digikaDMUXXh/usr/lib/libQt5Sql.so.5) digikam: /usr/lib/x86_64-linux-gnu/libstdc++.so.6: version `GLIBCXX_3.4.20' not found (required by /tmp/.mount_digikaDMUXXh/usr/lib/libMagick++-6.Q16.so.8) digikam: /usr/lib/x86_64-linux-gnu/libstdc++.so.6: version `GLIBCXX_3.4.21' not found (required by /tmp/.mount_digikaDMUXXh/usr/lib/libMagick++-6.Q16.so.8) digikam: /usr/lib/x86_64-linux-gnu/libstdc++.so.6: version `CXXABI_1.3.9' not found (required by /tmp/.mount_digikaDMUXXh/usr/lib/libQt5Network.so.5) digikam: /usr/lib/x86_64-linux-gnu/libstdc++.so.6: version `CXXABI_1.3.9' not found (required by /tmp/.mount_digikaDMUXXh/usr/lib/libQt5DBus.so.5) digikam: /usr/lib/x86_64-linux-gnu/libstdc++.so.6: version `CXXABI_1.3.9' not found (required by /tmp/.mount_digikaDMUXXh/usr/lib/libQt5Xml.so.5) digikam: /usr/lib/x86_64-linux-gnu/libstdc++.so.6: version `CXXABI_1.3.9' not found (required by /tmp/.mount_digikaDMUXXh/usr/lib/libQt5Widgets.so.5) digikam: /usr/lib/x86_64-linux-gnu/libstdc++.so.6: version `CXXABI_1.3.9' not found (required by /tmp/.mount_digikaDMUXXh/usr/lib/libQt5Gui.so.5) digikam: /usr/lib/x86_64-linux-gnu/libstdc++.so.6: version `CXXABI_1.3.9' not found (required by /tmp/.mount_digikaDMUXXh/usr/lib/libQt5Concurrent.so.5) digikam: /usr/lib/x86_64-linux-gnu/libstdc++.so.6: version `CXXABI_1.3.9' not found (required by /tmp/.mount_digikaDMUXXh/usr/lib/libQt5Core.so.5) digikam: /usr/lib/x86_64-linux-gnu/libstdc++.so.6: version `CXXABI_1.3.8' not found (required by /tmp/.mount_digikaDMUXXh/usr/lib/libQt5Core.so.5) digikam: /usr/lib/x86_64-linux-gnu/libstdc++.so.6: version `GLIBCXX_3.4.21' not found (required by /tmp/.mount_digikaDMUXXh/usr/lib/libQt5Core.so.5) digikam: /usr/lib/x86_64-linux-gnu/libstdc++.so.6: version `CXXABI_1.3.9' not found (required by /tmp/.mount_digikaDMUXXh/usr/lib/libQt5XmlPatterns.so.5) digikam: /usr/lib/x86_64-linux-gnu/libstdc++.so.6: version `GLIBCXX_3.4.20' not found (required by /tmp/.mount_digikaDMUXXh/usr/lib/libexiv2.so.27) digikam: /usr/lib/x86_64-linux-gnu/libstdc++.so.6: version `GLIBCXX_3.4.21' not found (required by /tmp/.mount_digikaDMUXXh/usr/lib/libexiv2.so.27) digikam: /usr/lib/x86_64-linux-gnu/libstdc++.so.6: version `CXXABI_1.3.8' not found (required by /tmp/.mount_digikaDMUXXh/usr/lib/libmarblewidget-qt5.so.28) digikam: /usr/lib/x86_64-linux-gnu/libstdc++.so.6: version `GLIBCXX_3.4.21' not found (required by /tmp/.mount_digikaDMUXXh/usr/lib/liblensfun.so.2) digikam: /usr/lib/x86_64-linux-gnu/libstdc++.so.6: version `GLIBCXX_3.4.20' not found (required by /tmp/.mount_digikaDMUXXh/usr/lib/libopencv_objdetect.so.3.4)
[kwin] [Bug 411092] Wobbly Effects leaves window trails behinds
https://bugs.kde.org/show_bug.cgi?id=411092 --- Comment #7 from wolfyrion --- Thank you very much for your effort , for your research, finding and fixing this bug. Although I have many questions like for example why this bug is happening to me and not to other users? What it means it happens to opaque wobbly windows? Why I am an opaque client? Is ok if you dont have time to answer, I understand :) Thanks again! -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 379635] popmenu at desktop doesn't disappear when lost focus.
https://bugs.kde.org/show_bug.cgi?id=379635 Patrick Silva changed: What|Removed |Added CC||todaywe@nuke.africa --- Comment #30 from Patrick Silva --- *** Bug 411683 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 411683] Desktop icon right click popup doesn't hide
https://bugs.kde.org/show_bug.cgi?id=411683 Patrick Silva changed: What|Removed |Added Resolution|--- |DUPLICATE CC||bugsefor...@gmx.com Status|REPORTED|RESOLVED --- Comment #1 from Patrick Silva --- *** This bug has been marked as a duplicate of bug 379635 *** -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 411374] search on continuous view often mispositions search for non-last column
https://bugs.kde.org/show_bug.cgi?id=411374 --- Comment #5 from Dave Gilbert --- Albert: Yes, that's fair enough. David: I'm pretty sure I want continous mode - I've got huge data books and documents, and want to be able to see those 8 pages at a time on my monitor; I think continous is the only sane way. (I run 4 columns, 2 rows) Centering does make some sense; but it's not what we do now either; I tend to find the search result near the top of the screen with the next page cut off. When your vertical size is large enough, and you can fit multiple pages on, then perhaps getting the search near the midpoint - but just constraining that you don't lose the top of that row of pages, might make sense. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 411694] New: Krita does not close cleanly because of Dr. Konqi on Arch Linux with XFCE
https://bugs.kde.org/show_bug.cgi?id=411694 Bug ID: 411694 Summary: Krita does not close cleanly because of Dr. Konqi on Arch Linux with XFCE Product: krita Version: 4.2.5 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: General Assignee: krita-bugs-n...@kde.org Reporter: bennycaguil...@gmail.com Target Milestone: --- SUMMARY After closing krita, a system notification appears saying krita closed unexpectedly, even though closing it was intentional and done cleanly. STEPS TO REPRODUCE 1. Close Krita, either by shortcut, X button on the window manager, or the Quit option in Krita's file menu. OBSERVED RESULT Krita gives this output after being closed: (process:24790): Gtk-WARNING **: 15:18:42.059: Locale not supported by C library. Using the fallback 'C' locale. Invalid profile : "/usr/share/color/icc/colord/Crayons.icc" "Crayon Colors" Invalid profile : "/usr/share/color/icc/colord/x11-colors.icc" "X11 Colors" krita.general: convertAndSetBlendMode: Curve conversion is not implemented yet krita.lib.widgets: The file could not be parsed. QObject::startTimer: Timers cannot have negative intervals /usr/lib/krita-python-libs/krita added to PYTHONPATH KCrash: crashing... crashRecursionCounter = 2 KCrash: Application Name = krita path = /usr/bin pid = 24790 KCrash: Arguments: /usr/bin/krita KCrash: Attempting to start /usr/lib/drkonqi from kdeinit sock_file=/run/user/1000/kdeinit5__0 Warning: connect() failed: : No such file or directory KCrash: Attempting to start /usr/lib/drkonqi directly (process:24886): Gtk-WARNING **: 15:18:48.458: Locale not supported by C library. Using the fallback 'C' locale. [1] + 24790 suspended (signal) krita Then, after a minute or so, krita outputs the following: QSocketNotifier: Invalid socket 20 and type 'Read', disabling... QSocketNotifier: Invalid socket 21 and type 'Read', disabling... QSocketNotifier: Invalid socket 22 and type 'Read', disabling... Unable to start Dr. Konqi Re-raising signal for core dump handling. [1] + 24790 segmentation fault (core dumped) krita EXPECTED RESULT Krita closes cleanly and instantly SOFTWARE/OS VERSIONS Linux: Arch Linux, XFCE KDE Plasma Version: n/a KDE Frameworks Version: 5.61.0 Qt Version: 5.13.0 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 411695] New: Steam sluggishness
https://bugs.kde.org/show_bug.cgi?id=411695 Bug ID: 411695 Summary: Steam sluggishness Product: krita Version: 4.2.5 Platform: Windows CE OS: Windows CE Status: REPORTED Severity: normal Priority: NOR Component: Tools Assignee: krita-bugs-n...@kde.org Reporter: rowland.wes...@gmail.com Target Milestone: --- SUMMARY Overall laggy performance on the steam version compared to the free version. STEPS TO REPRODUCE 1. ??? 2. ??? 3. ??? OBSERVED RESULT The steam version of Krita is overall laggy when trying to do anything with the canvas. Things like slower loading, laggy drawing on my tablet, slow rotation, slow brush changing, and there even is a little lag when changing some options. I've used different display options and even toggled the instant preview option to no effect. I've tried to do a fresh reinstall as well and there was no change. It should be mentioned as well that the free version I have doesn't have these issues, to the extent that the steam version has. EXPECTED RESULT Performance comparable to the free version on the steam version. SOFTWARE/OS VERSIONS Windows: windows 10 ADDITIONAL INFORMATION I have a RTX 2070 with a i7 7700 with 16 gigs of ram. I use the software off of my SSD and my tablet is a Wacom intuos pro I got from five years ago. My drivers are up to date. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 411677] HiDPI scaling issues
https://bugs.kde.org/show_bug.cgi?id=411677 Christoph Feck changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |DUPLICATE --- Comment #1 from Christoph Feck --- *** This bug has been marked as a duplicate of bug 407068 *** -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 407068] Some views show badly rendered fonts when fractional display scale is used
https://bugs.kde.org/show_bug.cgi?id=407068 Christoph Feck changed: What|Removed |Added CC||phil...@berndt.no --- Comment #4 from Christoph Feck --- *** Bug 411677 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kmediaplayer] [Bug 411693] New: Media Controls and Thumbnails are Duplicated across Browser Previews
https://bugs.kde.org/show_bug.cgi?id=411693 Bug ID: 411693 Summary: Media Controls and Thumbnails are Duplicated across Browser Previews Product: frameworks-kmediaplayer Version: 5.61.0 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: alex.me...@kde.org Reporter: mattyhoffm...@gmail.com CC: kdelibs-b...@kde.org Target Milestone: --- Created attachment 122528 --> https://bugs.kde.org/attachment.cgi?id=122528=edit Visual representation of bug SUMMARY When using Browser Integration with Enhanced Media Controls enabled, window thumbnails are changed to the extracted metadata image (video thumbnail) and this image is duplicated across all window previews. This does not happen when Enhanced Media Controls are disabled. See screenshot for reference. This bug was produced on Arch Linux with the latest packages at time of writing. Also reproduced on Debian Stable (buster 10) and Manjaro. STEPS TO REPRODUCE 1. Enable Enhanced Media Controls in Browser Integration 2. Play video or music on YouTube or other platform. 3. Attempt to view window previews from Task Manager. OBSERVED RESULT All window previews are of the extracted metadata and not the current state of the browser window. EXPECTED RESULT Browser previews should be normal (i.e. one can see what is currently displaying on them) apart from the window the media is playing on. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Arch Linux x64 KDE Plasma Version: 5.16.5 KDE Frameworks Version: 5.61.0 Qt Version: 5.13.0 ADDITIONAL INFORMATION N/A -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 411692] New: Plasma crashed on Wayland when I tapped a favorite app in Kickoff using a touch screen
https://bugs.kde.org/show_bug.cgi?id=411692 Bug ID: 411692 Summary: Plasma crashed on Wayland when I tapped a favorite app in Kickoff using a touch screen Product: plasmashell Version: master Platform: Other OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: generic-wayland Assignee: plasma-b...@kde.org Reporter: bugsefor...@gmx.com Target Milestone: 1.0 Application: plasmashell (5.16.80) Qt Version: 5.12.3 Frameworks Version: 5.62.0 Operating System: Linux 5.2.5-050205-generic x86_64 Distribution: KDE neon Unstable Edition -- Information about the crash: - What I was doing when the application crashed: I tapped an app present in the favorites list of Kickoff and Plasma crashed on Wayland. The crash can be reproduced sometimes. -- Backtrace: Application: Plasma (plasmashell), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7fcd423c8800 (LWP 2127))] Thread 15 (Thread 0x7fccbdc51700 (LWP 11176)): #0 0x7fcd3915b9f3 in futex_wait_cancelable (private=, expected=0, futex_word=0x7fccb00b4e50) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 __pthread_cond_wait_common (abstime=0x0, mutex=0x7fccb00b4e00, cond=0x7fccb00b4e28) at pthread_cond_wait.c:502 #2 __pthread_cond_wait (cond=0x7fccb00b4e28, mutex=0x7fccb00b4e00) at pthread_cond_wait.c:655 #3 0x7fcd3c222dbb in QWaitConditionPrivate::wait (deadline=..., this=0x7fccb00b4e00) at thread/qwaitcondition_unix.cpp:146 #4 QWaitCondition::wait (this=, mutex=0x7fccb0068670, deadline=...) at thread/qwaitcondition_unix.cpp:225 #5 0x7fcd3c2230c9 in QWaitCondition::wait (this=this@entry=0x7fccb0068678, mutex=mutex@entry=0x7fccb0068670, time=time@entry=18446744073709551615) at thread/qwaitcondition_unix.cpp:208 #6 0x7fcd4021f6f8 in QSGRenderThreadEventQueue::takeEvent (wait=true, this=0x7fccb0068668) at scenegraph/qsgthreadedrenderloop.cpp:245 #7 QSGRenderThread::processEventsAndWaitForMore (this=this@entry=0x7fccb00685f0) at scenegraph/qsgthreadedrenderloop.cpp:710 #8 0x7fcd4021fb2a in QSGRenderThread::run (this=0x7fccb00685f0) at scenegraph/qsgthreadedrenderloop.cpp:739 #9 0x7fcd3c21bc72 in QThreadPrivate::start (arg=0x7fccb00685f0) at thread/qthread_unix.cpp:361 #10 0x7fcd391556db in start_thread (arg=0x7fccbdc51700) at pthread_create.c:463 #11 0x7fcd3bb1b88f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 14 (Thread 0x7fccbee97700 (LWP 11175)): #0 0x7fccf76ef7d5 in ?? () from /usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-11.1.so #1 0x7fccf76f0798 in ?? () from /usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-11.1.so #2 0x7fccf76f0ab9 in ?? () from /usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-11.1.so #3 0x7fccf76f133f in ?? () from /usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-11.1.so #4 0x7fccf7dd4108 in pa_mainloop_dispatch () from /usr/lib/x86_64-linux-gnu/libpulse.so.0 #5 0x7fccf7dd44de in pa_mainloop_iterate () from /usr/lib/x86_64-linux-gnu/libpulse.so.0 #6 0x7fccf7dd4560 in pa_mainloop_run () from /usr/lib/x86_64-linux-gnu/libpulse.so.0 #7 0x7fccf7de23c9 in ?? () from /usr/lib/x86_64-linux-gnu/libpulse.so.0 #8 0x7fccf7701318 in ?? () from /usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-11.1.so #9 0x7fcd391556db in start_thread (arg=0x7fccbee97700) at pthread_create.c:463 #10 0x7fcd3bb1b88f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 13 (Thread 0x7fccbe492700 (LWP 10935)): #0 0x7fcd3bb0ebf9 in __GI___poll (fds=0x7fccb8016a50, nfds=3, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7fccf7de2481 in ?? () from /usr/lib/x86_64-linux-gnu/libpulse.so.0 #2 0x7fccf7dd3e40 in pa_mainloop_poll () from /usr/lib/x86_64-linux-gnu/libpulse.so.0 #3 0x7fccf7dd44d0 in pa_mainloop_iterate () from /usr/lib/x86_64-linux-gnu/libpulse.so.0 #4 0x7fccf7dd4560 in pa_mainloop_run () from /usr/lib/x86_64-linux-gnu/libpulse.so.0 #5 0x7fccf7de23c9 in ?? () from /usr/lib/x86_64-linux-gnu/libpulse.so.0 #6 0x7fccf7701318 in ?? () from /usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-11.1.so #7 0x7fcd391556db in start_thread (arg=0x7fccbe492700) at pthread_create.c:463 #8 0x7fcd3bb1b88f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 12 (Thread 0x7fcce09f1700 (LWP 3041)): #0 0x7fcd35a91649 in g_mutex_lock (mutex=mutex@entry=0x7fcd04002800) at ../../../../glib/gthread-posix.c:1343 #1 0x7fcd35a4ab33 in g_main_context_prepare (context=context@entry=0x7fcd04002800, priority=priority@entry=0x7fcce09f0bf0) at ../../../../glib/gmain.c:3477 #2 0x7fcd35a4b4fb in g_main_context_iterate (context=context@entry=0x7fcd04002800, block=block@entry=1, dispatch=dispatch@entry=1, self=) at
[kpat] [Bug 411691] New: Only happens in Opensuse 15.1 in most games the cards will only autodrop a few, and then it stops., often crashes when Yukon is selected
https://bugs.kde.org/show_bug.cgi?id=411691 Bug ID: 411691 Summary: Only happens in Opensuse 15.1 in most games the cards will only autodrop a few, and then it stops., often crashes when Yukon is selected Product: kpat Version: 3.6 Platform: openSUSE RPMs OS: Linux Status: REPORTED Keywords: reproducible Severity: minor Priority: NOR Component: general Assignee: co...@kde.org Reporter: bradscient...@ieee.org CC: kde-games-b...@kde.org Target Milestone: --- SUMMARY Only in Opensuse 15.1 (occurs on all 4 of my machines with this OS) When it is supposed to "autodrop" or autocollect in Freecell or Klondike, it will bring up a few cards then stop. Manually bring up a few cards, then it does a few automatically and then stops again. STEPS TO REPRODUCE 1. Use Opensuse 15.1 (does not happen in Opensuse 15.0) 2. Kpat 3.6 3. Select Freecell 4. Play game OBSERVED RESULT EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 411081] Crash Without Warning
https://bugs.kde.org/show_bug.cgi?id=411081 4lph4dr4g0nl...@gmail.com changed: What|Removed |Added Status|REOPENED|NEEDSINFO Resolution|--- |FIXED --- Comment #27 from 4lph4dr4g0nl...@gmail.com --- (In reply to Dmitry Kazakov from comment #22) > Ah, I'm sorry. I gave you a link to a wrong branch, sorry :( > > Could you try this one: > https://binary-factory.kde.org/job/Krita_Nightly_Windows_Build/ > > And at the same time, could you check if you have access to this folder? > C:\Users\nitef\AppData\Local\Temp > > It looks like Krita tries to create a swap file there, but fails. > > If you still have a crash, try to go to > Preferences->Performance->SwapFileLocation and select some writable > location, which you are sure about. After that restart Krita. > > If you still have a problem, attach a log from DebugView :) Nevermind, it once again decided to wait until I marked the bug as "worksforme". Here's the log: https://sta.sh/02cz710pg0gx I'm going to do more testing with the build vs the latest nightly build, and try the swap file thing again. I'll let you know what happens. -- You are receiving this mail because: You are watching all bug changes.
[kaddressbook] [Bug 387804] Create folder in KAddressBook fails
https://bugs.kde.org/show_bug.cgi?id=387804 bbugs changed: What|Removed |Added CC||bb...@fantasymail.de --- Comment #3 from bbugs --- Hello! I can confirm the bug, although with a slightly different error message: "Could not create address book folder: Could not create collection [XYZ], resourceId: 11" I would appreciate that the bug were fixed shortly, since an addressbook without subfolders is not very useful. There is a kind of workaround that works for me, although it is very ponderous. See: https://forum.kde.org/viewtopic.php?f=215=143208 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 411578] White Balance changes global luminosity
https://bugs.kde.org/show_bug.cgi?id=411578 Maik Qualmann changed: What|Removed |Added Resolution|--- |FIXED Status|REPORTED|RESOLVED Version Fixed In||6.4.0 Latest Commit||https://invent.kde.org/kde/ ||digikam/commit/ec6ed65c8d8e ||b9925690470e918ad2211fc0689 ||8 --- Comment #2 from Maik Qualmann --- Git commit ec6ed65c8d8eb9925690470e918ad2211fc06898 by Maik Qualmann. Committed on 07/09/2019 at 22:41. Pushed by mqualmann into branch 'master'. implement temperature to RGB code from Tanner Helland FIXED-IN: 6.4.0 M +2-1NEWS M +0-1core/dplugins/editor/colors/whitebalance/whitebalancetool.cpp M +0-4core/libs/dimg/filters/wb/wbcontainer.cpp M +0-9core/libs/dimg/filters/wb/wbcontainer.h M +56 -159 core/libs/dimg/filters/wb/wbfilter.cpp M +2-7core/libs/dimg/filters/wb/wbfilter.h https://invent.kde.org/kde/digikam/commit/ec6ed65c8d8eb9925690470e918ad2211fc06898 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kdeclarative] [Bug 411690] QCH build fails with doxygen 1.8.16
https://bugs.kde.org/show_bug.cgi?id=411690 Antonio Rojas changed: What|Removed |Added CC||heire...@exherbo.org Assignee|notm...@gmail.com |kosse...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kdeclarative] [Bug 411690] New: QCH build fails with doxygen 1.8.16
https://bugs.kde.org/show_bug.cgi?id=411690 Bug ID: 411690 Summary: QCH build fails with doxygen 1.8.16 Product: frameworks-kdeclarative Version: unspecified Platform: Compiled Sources OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: notm...@gmail.com Reporter: aro...@archlinux.org CC: kdelibs-b...@kde.org Target Milestone: --- Created attachment 122527 --> https://bugs.kde.org/attachment.cgi?id=122527=edit broken index.qhp SUMMARY If kconfig and kpackage are both compiled with doxygen 1.8.16, QCH docs fail to build for kdeclarative, with error Error in line 233: Opening and ending tag mismatch. And indeed, index.qhp (attached) contains a spurious tag. Looking at the tags files for kconfig and kpackage, these are the diffs when compiled with doxygen 1.8.16 vs old doxygen (modulo permutation of the blocks): diff -ru kpackage-old/usr/share/doc/qt/KF5Package.tags kpackage-new/usr/share/doc/qt/KF5Package.tags --- kpackage-old/usr/share/doc/qt/KF5Package.tags 2019-08-09 17:13:20.0 +0200 +++ kpackage-new/usr/share/doc/qt/KF5Package.tags 2019-09-07 22:52:01.0 +0200 @@ -645,5 +645,11 @@ index KPackage Framework index +autotoc_md1 +autotoc_md2 +autotoc_md3 +autotoc_md4 +autotoc_md5 +autotoc_md6 diff -ru kconfig-old/usr/share/doc/qt/KF5Config.tags kconfig-new/usr/share/doc/qt/KF5Config.tags --- kconfig-old/usr/share/doc/qt/KF5Config.tags 2019-08-09 16:34:02.0 +0200 +++ kconfig-new/usr/share/doc/qt/KF5Config.tags 2019-09-07 22:49:53.0 +0200 @@ -4117,10 +4117,13 @@ options KConfig Entry Options options +autotoc_md0 +autotoc_md1 index KConfig index +autotoc_md3 Removing these docanchor lines from either of them fixes the issue. There's probably some doxygen bug involved here, but I don't understand the internals of QCH generation well enough to figure it out. -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 411689] New: Symbol Viewer in Kate no longer recognizes Fortran files
https://bugs.kde.org/show_bug.cgi?id=411689 Bug ID: 411689 Summary: Symbol Viewer in Kate no longer recognizes Fortran files Product: kate Version: 19.08.0 Platform: Manjaro OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: part Assignee: kwrite-bugs-n...@kde.org Reporter: tofailihas...@gmail.com Target Milestone: --- Created attachment 122526 --> https://bugs.kde.org/attachment.cgi?id=122526=edit Screenshot showing the issue SUMMARY Symbol Viewer can not analyze Fortran files to find functions and subroutines. It says the file type is unsupported. STEPS TO REPRODUCE 1. Start Kate 2. Write any Fortran code, and define functions and subroutines 3. Save the file in .f90 or .f08 format OBSERVED RESULT Symbol Viewer says file type in unsupported, and it can't find the functions and subroutines. EXPECTED RESULT In previous versions (earlier this year), Symbol Viewer used to support Fortran, and it could display functions and subroutines without any problems. SOFTWARE/OS VERSIONS Windows: Not tested macOS: Not tested Linux/KDE Plasma: Tested with Manjaro Linux (available in About System) KDE Plasma Version: 5.16.4 KDE Frameworks Version: 5.61.0 Qt Version: 5.13.0 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 411221] Crash in Plasma::Applet::configChanged on Applet destruction
https://bugs.kde.org/show_bug.cgi?id=411221 David Edmundson changed: What|Removed |Added Latest Commit||https://commits.kde.org/pla ||sma-framework/5f746ce1c2c2d ||5a8c1be4f62347e18534d95e29d Status|CONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #4 from David Edmundson --- Git commit 5f746ce1c2c2d5a8c1be4f62347e18534d95e29d by David Edmundson. Committed on 07/09/2019 at 21:19. Pushed by davidedmundson into branch 'master'. Fix crash on teardown with Applet's ConfigLoader Summary: Deleting AppletPrivate will delete the ConfigLoader which will cause a save, which can trigger a configSaved signal. I think it is correct that the config might emit a signal just before closing, and not at fault. AppletPrivate is deleted by this point, but Applet is not so the connection is still alive. When we handle the signal, it goes into a Q_PRIVATE_SLOT that crashes. This disconnect pattern is already used for guarding self config changes. Test Plan: kquitapp5 plasmashell, no longer crashes Reviewers: #plasma, alexeymin Reviewed By: alexeymin Subscribers: alexeymin, kde-frameworks-devel Tags: #frameworks Differential Revision: https://phabricator.kde.org/D23707 M +4-0src/plasma/applet.cpp https://commits.kde.org/plasma-framework/5f746ce1c2c2d5a8c1be4f62347e18534d95e29d -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 411657] Latte dock free when used with some combinations of plasmoids
https://bugs.kde.org/show_bug.cgi?id=411657 Michail Vourlakos changed: What|Removed |Added Latest Commit|https://commits.kde.org/lat |https://commits.kde.org/lat |te-dock/7cfcd8451122b8c9902 |te-dock/1a49238d5765a97854d |78375406fe9fde06accbe |b3d683b286a7022bb1fc4 --- Comment #14 from Michail Vourlakos --- Git commit 1a49238d5765a97854db3d683b286a7022bb1fc4 by Michail Vourlakos. Committed on 07/09/2019 at 21:09. Pushed by mvourlakos into branch 'master'. track kwinrc file only on changes --instead of reading the kwin values all the time when needed from user actions we now read them only on startup and when the kwinrc file was updated/changed FIXED-IN:0.9.3 M +6-25 app/layout/centrallayout.cpp M +2-2app/settings/settingsdialog.cpp M +65 -24 app/settings/universalsettings.cpp M +11 -6app/settings/universalsettings.h M +4-4app/shortcuts/globalshortcuts.cpp https://commits.kde.org/latte-dock/1a49238d5765a97854db3d683b286a7022bb1fc4 -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 411657] Latte dock free when used with some combinations of plasmoids
https://bugs.kde.org/show_bug.cgi?id=411657 Michail Vourlakos changed: What|Removed |Added Resolution|--- |FIXED Latest Commit||https://commits.kde.org/lat ||te-dock/7cfcd8451122b8c9902 ||78375406fe9fde06accbe Version Fixed In||0.9.3 Status|REPORTED|RESOLVED --- Comment #13 from Michail Vourlakos --- Git commit 7cfcd8451122b8c990278375406fe9fde06accbe by Michail Vourlakos. Committed on 07/09/2019 at 20:52. Pushed by mvourlakos into branch 'v0.9'. track kwinrc file only on changes --instead of reading the kwin values all the time when needed from user actions we now read them only on startup and when the kwinrc file was updated/changed FIXED-IN:0.9.3 M +6-25 app/layout/centrallayout.cpp M +2-2app/settings/settingsdialog.cpp M +65 -24 app/settings/universalsettings.cpp M +11 -6app/settings/universalsettings.h M +4-4app/shortcuts/globalshortcuts.cpp https://commits.kde.org/latte-dock/7cfcd8451122b8c990278375406fe9fde06accbe -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 411223] Dolphin’s sort order chooser human-readable text
https://bugs.kde.org/show_bug.cgi?id=411223
--- Comment #8 from Gabriel Fernandes ---
But it seems to be missing a parenthesis at the end of the for, in the diff. I
had added one before the curly at the end in my local build.
for (QAction *groupAction : qAsConst(m_sortByActions) ->)<- {
--
You are receiving this mail because:
You are watching all bug changes.
[plasmashell] [Bug 411678] Kickoff search doesn't work sometimes
https://bugs.kde.org/show_bug.cgi?id=411678 Björn Feber changed: What|Removed |Added CC||bfe...@protonmail.com Resolution|--- |DUPLICATE Status|REPORTED|RESOLVED --- Comment #1 from Björn Feber --- *** This bug has been marked as a duplicate of bug 401861 *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 401861] Menu search doesn't return any results if cursor happens to be positioned below the tab bar
https://bugs.kde.org/show_bug.cgi?id=401861 Björn Feber changed: What|Removed |Added CC||todaywe@nuke.africa --- Comment #14 from Björn Feber --- *** Bug 411678 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 411081] Crash Without Warning
https://bugs.kde.org/show_bug.cgi?id=411081 4lph4dr4g0nl...@gmail.com changed: What|Removed |Added Resolution|WORKSFORME |--- Status|RESOLVED|REOPENED --- Comment #26 from 4lph4dr4g0nl...@gmail.com --- (In reply to Dmitry Kazakov from comment #24) > Git commit 2fdd504dfe6ec63b654ee0878c9f95cb69d4a6ad by Dmitry Kazakov. > Committed on 05/09/2019 at 08:22. > Pushed by dkazakov into branch 'master'. > > Fix QRandomGenerator initialization on AMD CPUs > > Some AMD CPUs (e.g. AMD A4-6250J and AMD Ryzen 3000-series) have a > failing random generation instruction, which always returns > 0x, even when generation was "successful". > > This code checks if hardware random generator can generate four > consecutive distinct numbers. If it fails the test, then we probably > have a failing one and should disable it completely. > > Gerrit review: > https://codereview.qt-project.org/c/qt/qtbase/+/272837 > > A +214 -0 > 3rdparty/ext_qt/0070-Fix-QRandomGenerator-initialization-on-AMD-CPUs.patch > M +7-03rdparty/ext_qt/CMakeLists.txt > > https://invent.kde.org/kde/krita/commit/ > 2fdd504dfe6ec63b654ee0878c9f95cb69d4a6ad I do run on an AMD Ryzen 5 3600X 6-Core Processor, so that (In reply to 4lph4dr4g0nl1ch from comment #25) > (In reply to Dmitry Kazakov from comment #22) > > Ah, I'm sorry. I gave you a link to a wrong branch, sorry :( > > > > Could you try this one: > > https://binary-factory.kde.org/job/Krita_Nightly_Windows_Build/ > > > > And at the same time, could you check if you have access to this folder? > > C:\Users\nitef\AppData\Local\Temp > > > > It looks like Krita tries to create a swap file there, but fails. > > > > If you still have a crash, try to go to > > Preferences->Performance->SwapFileLocation and select some writable > > location, which you are sure about. After that restart Krita. > > > > If you still have a problem, attach a log from DebugView :) > > - > Sorry for waiting so long to reply, but because it didn't show itself last > time, I took a few days to test the build for the crash. I've been actively > trying to duplicate the crash, and so far it hasn't happened yet. --- Scratch that, it's crashed again.(In reply to Dmitry Kazakov from comment #24) > Git commit 2fdd504dfe6ec63b654ee0878c9f95cb69d4a6ad by Dmitry Kazakov. > Committed on 05/09/2019 at 08:22. > Pushed by dkazakov into branch 'master'. > > Fix QRandomGenerator initialization on AMD CPUs > > Some AMD CPUs (e.g. AMD A4-6250J and AMD Ryzen 3000-series) have a > failing random generation instruction, which always returns > 0x, even when generation was "successful". > > This code checks if hardware random generator can generate four > consecutive distinct numbers. If it fails the test, then we probably > have a failing one and should disable it completely. > > Gerrit review: > https://codereview.qt-project.org/c/qt/qtbase/+/272837 > > A +214 -0 > 3rdparty/ext_qt/0070-Fix-QRandomGenerator-initialization-on-AMD-CPUs.patch > M +7-03rdparty/ext_qt/CMakeLists.txt > > https://invent.kde.org/kde/krita/commit/ > 2fdd504dfe6ec63b654ee0878c9f95cb69d4a6ad I do run on an AMD Ryzen-3600 processor, so that adds up. What am I supposed to do there at those links? Are those just separate forums discussing the issue or? -- You are receiving this mail because: You are watching all bug changes.
[kio-extras] [Bug 408174] fish:// and sftp:// opens a non-existing folder fish:////
https://bugs.kde.org/show_bug.cgi?id=408174 Shimi Chen changed: What|Removed |Added CC||shimi.c...@gmail.com Version|18.12.3 |19.08.0 Status|REPORTED|CONFIRMED Ever confirmed|0 |1 --- Comment #2 from Shimi Chen --- I can confirm this on Arch Linux using version 19.08.1. It occurs both in Kate and KWrite, but not in okular or ark. Steps to reproduce: 1. Using the Kate "Open File" dialog (ctrl+o or File->Open...) open a text file located on an sftp server. 2. Go to File->Open.. or File->Save As... Expected result: The application will open the directory in which the file is saved in order to select another file in it (or save the file in another name at the same place). Actual result: The application attempts to browse the opened file itself as a directory, which produces an error (as indeed there is no directory with the same name as the opened file). Bug 320319 may be related, however it is in Windows. It seems that this issue already existed around 2016 on linux, but was twice reported as fixed at that time (bug 352490, comment 2 and bug 363365, comment 2). -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 360834] no mechanism to reattempt to store items without rid (just in db) into the resource
https://bugs.kde.org/show_bug.cgi?id=360834 Daniel Roschka changed: What|Removed |Added CC||danielroschka@phoenitydawn. ||de -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 344242] Mails that are copied do not appear on my harddrive
https://bugs.kde.org/show_bug.cgi?id=344242 Daniel Roschka changed: What|Removed |Added CC||danielroschka@phoenitydawn. ||de -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 411092] Wobbly Effects leaves window trails behinds
https://bugs.kde.org/show_bug.cgi?id=411092 Vlad Zahorodnii changed: What|Removed |Added Status|CONFIRMED |RESOLVED Version Fixed In||5.17.0 Latest Commit||https://commits.kde.org/kwi ||n/4d4d9990ddc2b8a82c40fe151 ||cc689269e3b8389 Resolution|--- |FIXED --- Comment #6 from Vlad Zahorodnii --- Git commit 4d4d9990ddc2b8a82c40fe151cc689269e3b8389 by Vlad Zagorodniy. Committed on 07/09/2019 at 20:50. Pushed by vladz into branch 'master'. [effects/wobblywindows] Draw clients below opaque wobbly windows Summary: Given that wobbly windows effect takes optimized render path, it needs to clear the clip region of about to be transformed opaque window. FIXED-IN: 5.17.0 Reviewers: #kwin, davidedmundson Reviewed By: #kwin, davidedmundson Subscribers: kwin Tags: #kwin Differential Revision: https://phabricator.kde.org/D23774 M +4-0effects/wobblywindows/wobblywindows.cpp https://commits.kde.org/kwin/4d4d9990ddc2b8a82c40fe151cc689269e3b8389 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 411671] New icon for Restart is reversed
https://bugs.kde.org/show_bug.cgi?id=411671 Nate Graham changed: What|Removed |Added Version Fixed In||5.63 Status|CONFIRMED |RESOLVED Resolution|--- |FIXED Latest Commit||https://commits.kde.org/bre ||eze-icons/859d65bc2cc0db45c ||0bb6a9071cfb08136a9ed6c --- Comment #4 from Nate Graham --- Git commit 859d65bc2cc0db45c0bb6a9071cfb08136a9ed6c by Nate Graham. Committed on 07/09/2019 at 20:26. Pushed by ngraham into branch 'master'. Fix large system-reboot icons rotating in an inconsistent direction FIXED-IN: 5.63 M +12 -16 icons-dark/actions/32/system-reboot.svg M +12 -16 icons/actions/32/system-reboot.svg https://commits.kde.org/breeze-icons/859d65bc2cc0db45c0bb6a9071cfb08136a9ed6c -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 411671] New icon for Restart is reversed
https://bugs.kde.org/show_bug.cgi?id=411671 Nate Graham changed: What|Removed |Added CC||n...@kde.org --- Comment #3 from Nate Graham --- My bad, will fix. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 411688] New: Global shortcut to Switch to / Move window to another activity
https://bugs.kde.org/show_bug.cgi?id=411688 Bug ID: 411688 Summary: Global shortcut to Switch to / Move window to another activity Product: kwin Version: 5.12.8 Platform: openSUSE RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: activities Assignee: kwin-bugs-n...@kde.org Reporter: dimitrios.ta...@kdemail.net Target Milestone: --- SUMMARY In a multi activities setup it would make sense to be able to use hotkeys to switch to another activity as well as move a window to another activity, much like Switch to Desktop.. , Switch to Screen .., Window to Desktop .. and Window to Screen .. STEPS TO REPRODUCE 1. Open Global Keyboard Shortcuts 2. Search for shortcut to switch to activity 3. Search for shortcut to move window to activity OBSERVED RESULT No Actions exist to either switch to or move window to activity. EXPECTED RESULT There should be actions to allow switching and moving window to another activity. SOFTWARE/OS VERSIONS Linux/KDE Plasma: openSuse Leap 15.1 KDE Plasma Version: 5.12.8 KDE Frameworks Version: 5.55.0 Qt Version: 5.9.7 ADDITIONAL INFORMATION There exists org.kde.ActivityManager/ActivityManager/Activities DBUS message which allows switching to another activity via SetCurrentActivity but dbus-monitor does not record any dbus message when moving window, so I guess there is not a DBUS message to use a custom shortcut. PS. Maybe for a home user, saving 2-3sec when switching/moving around windows doesn't make any difference but in a business environment with 10 activities x 4 desktops each, used all day long, it would be a notable timesaver. -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 411687] New: Kontact crashes when I click somewhere
https://bugs.kde.org/show_bug.cgi?id=411687 Bug ID: 411687 Summary: Kontact crashes when I click somewhere Product: kontact Version: 5.11.3 Platform: Ubuntu Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: andreas.hen...@mailbox.org Target Milestone: --- Application: kontact (5.11.3) Qt Version: 5.12.4 Frameworks Version: 5.61.0 Operating System: Linux 5.2.0-15-generic x86_64 Distribution: Ubuntu Eoan Ermine (development branch) -- Information about the crash: - What I was doing when the application crashed: I was using Kmail within Kontact and I clicked at an inbox icon to view an other inbox when Kontact crashed. The same happens if I use Akregator or an other part of Kontact. SOFTWARE/OS VERSIONS Linux: Kubuntu 19.10 KDE Plasma Version: 5.16.5 KDE Frameworks Version: 5.61.0 Qt Version: 5.12.4 The crash can be reproduced sometimes. -- Backtrace: Application: Kontact (kontact), signal: Aborted Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f345c846f00 (LWP 25567))] Thread 24 (Thread 0x7f3436ffd700 (LWP 25704)): #0 futex_abstimed_wait_cancelable (private=, abstime=0x7f3436ffc470, clockid=, expected=0, futex_word=0x7f3436ffc5b8) at ../sysdeps/unix/sysv/linux/futex-internal.h:208 #1 __pthread_cond_wait_common (abstime=0x7f3436ffc470, clockid=, mutex=0x7f3436ffc568, cond=0x7f3436ffc590) at pthread_cond_wait.c:520 #2 __pthread_cond_timedwait (cond=0x7f3436ffc590, mutex=0x7f3436ffc568, abstime=0x7f3436ffc470) at pthread_cond_wait.c:656 #3 0x7f34686df10b in ?? () from /lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #4 0x7f34686dfab2 in ?? () from /lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #5 0x7f34686dfba6 in ?? () from /lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #6 0x7f34686a1705 in ?? () from /lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #7 0x7f34686a3f96 in ?? () from /lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #8 0x7f34686a4258 in ?? () from /lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #9 0x7f34686e1c75 in ?? () from /lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #10 0x7f346eb21669 in start_thread (arg=) at pthread_create.c:479 #11 0x7f346fb6b2f3 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 23 (Thread 0x7f333d776700 (LWP 25656)): #0 0x7f346fb5ebff in __GI___poll (fds=0x7f33300029e0, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7f346e1cda4e in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f346e1cdb83 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f3470121573 in QEventDispatcherGlib::processEvents (this=0x7f333b60, flags=...) at kernel/qeventdispatcher_glib.cpp:424 #4 0x7f34700c856b in QEventLoop::exec (this=this@entry=0x7f333d7756a0, flags=..., flags@entry=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:140 #5 0x7f346ff01a35 in QThread::exec (this=) at ../../include/QtCore/../../src/corelib/global/qflags.h:120 #6 0x7f346ff02c82 in QThreadPrivate::start (arg=0x55aecad46990) at thread/qthread_unix.cpp:361 #7 0x7f346eb21669 in start_thread (arg=) at pthread_create.c:479 #8 0x7f346fb6b2f3 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 22 (Thread 0x7f33525d4700 (LWP 25615)): #0 syscall () at ../sysdeps/unix/sysv/linux/x86_64/syscall.S:38 #1 0x7f346ff05071 in QtLinuxFutex::_q_futex (val3=0, addr2=0x0, val2=0, val=, op=0, addr=) at thread/qfutex_p.h:105 #2 QtLinuxFutex::futexWait > (expectedValue=, futex=...) at thread/qfutex_p.h:107 #3 futexSemaphoreTryAcquire_loop (timeout=-1, nn=8589934593, curValue=, u=...) at thread/qsemaphore.cpp:219 #4 futexSemaphoreTryAcquire (timeout=-1, n=, u=...) at thread/qsemaphore.cpp:262 #5 QSemaphore::acquire (this=0x55aebec51f28, n=) at thread/qsemaphore.cpp:326 #6 0x7f3352be5fec in ?? () from /usr/lib/x86_64-linux-gnu/qt5/plugins/texttospeech/libqttexttospeech_flite.so #7 0x7f346ff02c82 in QThreadPrivate::start (arg=0x55aebec51ef0) at thread/qthread_unix.cpp:361 #8 0x7f346eb21669 in start_thread (arg=) at pthread_create.c:479 #9 0x7f346fb6b2f3 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 21 (Thread 0x7f335345a700 (LWP 25613)): #0 0x7f346fb5ebff in __GI___poll (fds=0x7f33480025e0, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7f346e1cda4e in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f346e1cdb83 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f3470121573 in QEventDispatcherGlib::processEvents (this=0x7f3348000b60, flags=...) at kernel/qeventdispatcher_glib.cpp:424 #4 0x7f34700c856b in
[neon] [Bug 411686] New: Installer from Live ISO hangs up during first stages of setup
https://bugs.kde.org/show_bug.cgi?id=411686 Bug ID: 411686 Summary: Installer from Live ISO hangs up during first stages of setup Product: neon Version: unspecified Platform: Neon Packages OS: Linux Status: REPORTED Severity: major Priority: NOR Component: Live/Install images Assignee: neon-b...@kde.org Reporter: adam.golan...@gmail.com CC: j...@jriddell.org, neon-b...@kde.org, sit...@kde.org Target Milestone: --- SUMMARY This is actually very strange behavior, discovered in both KDE Neon user edition and Kubuntu 19.04, so it may be a problem with specific version of KDE software. I've tried to install these distros on Thinkpad 13 laptop, with the S11-256G-PHISON-SDD (it may be important). The systems boot into the live session, with the installer on desktop. After running the installer, when a user chooses the keyboard settings and comes to the software selection, the installer becomes stuck, only the mouse cursor spins forever. Process manager shows What is interesting, other distros don't have this problem. I successfully installed new versions of Deepin Linux and Manjaro KDE 18.0.4 on this hardware. STEPS TO REPRODUCE 1. Flash the ISO of KDE Neon or Kubuntu on the pendrive, 2. Try to install distro with default settings on Thinkpad 13 laptop 3. Watch as the installer hangs, like something is wrong with access to the storage. OBSERVED RESULT Installation of the distro is impossible EXPECTED RESULT The installer should finish its job. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Current versions of KDE Neon (20190829-1117.iso) and Kubuntu 19.04 -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 411657] Latte dock free when used with some combinations of plasmoids
https://bugs.kde.org/show_bug.cgi?id=411657 --- Comment #12 from Michail Vourlakos --- I can also try to make that codepath much lighter but I would prefer if someone could test first that patch because in my system I do not have that issue. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 409768] Rightclick on System Tray/Taskpanel brings the wrong application back to
https://bugs.kde.org/show_bug.cgi?id=409768 --- Comment #13 from Nate Graham --- The "version fixed in" field at the top provides the answer: 5.17.0. This would be Plasma 5.17.0, which is not released yet, so it's no surprise that you don't have the fix yet. :) Once Plasma 5.17 is released and your distro of choice provides it to you, you'll get the fix. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 411223] Dolphin’s sort order chooser human-readable text
https://bugs.kde.org/show_bug.cgi?id=411223 --- Comment #7 from Nate Graham --- Still in patch review, I'm afraid. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 411520] musl based system: no time and date is shown
https://bugs.kde.org/show_bug.cgi?id=411520 --- Comment #4 from Bart Ribbers --- There might be some support for it in the source, but I meant there is no `locale` command like glibc has. I'm not sure what you want to know from `plasmaengineexplorer time`? It says there are 41 data sources, and selecting "time" in the dropdown makes several timezones show (UTC-14:00 to UTC+14:00 and "Local"). -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 411663] Eliminate delay in dock when using workspace isolation
https://bugs.kde.org/show_bug.cgi?id=411663 --- Comment #18 from Michail Vourlakos --- It's the same with activity change. Same thing also happens with activity change. I prefer the slide in-out much better than suddenly appearing things. This is why there is an option for this. I am OK with the current default. If this is too distracting for you, you can also change the Latte Tasks in favor of Plasma icon-only Tasks. So plenty of options but they are not defaults and this is intentional. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 406698] Transform Tool has SDR preview on HDR image
https://bugs.kde.org/show_bug.cgi?id=406698 sreechanda...@gmail.com changed: What|Removed |Added CC||sreechanda...@gmail.com --- Comment #6 from sreechanda...@gmail.com --- (In reply to Tymond from comment #3) > There are two ways of showing colors converted to SDR values: > A. clipped to 80 nits > B. in full glory of HDR brightness > > Issues mentioned above are using the following way: > 1. preview of the Transform Tool: method B. > 2. layer preview: method A. > 3. color picker: method B. > 4. image preview in Last Documents: method A. > 5. history of colors: method A. > > Method B is worse, because it often causes very bright colors to appear in > big amounts, which is not desireable. Glad to see color picker problem mentioned here. But I'm confused. If I draw a very bright white and use color picker(color selector) tool to pick it, it picks a very dim white. Is this what you are mentioning here? -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 411484] Speed change on extracted footage renders to white screen
https://bugs.kde.org/show_bug.cgi?id=411484 Robert changed: What|Removed |Added CC||rob...@robertelder.org --- Comment #9 from Robert --- Hi, just skimming this thread... Could this be: https://bugs.kde.org/show_bug.cgi?id=410174 ? If it's the same issue, the problem will go away if you remove the ':' character from input filenames. -- You are receiving this mail because: You are watching all bug changes.
[marble] [Bug 411685] New: marble-qt.exe - System Error
https://bugs.kde.org/show_bug.cgi?id=411685 Bug ID: 411685 Summary: marble-qt.exe - System Error Product: marble Version: unspecified Platform: unspecified OS: MS Windows Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: marble-b...@kde.org Reporter: craig...@yahoo.com Target Milestone: --- System Error dialog box appears on initial start after installation. "The code execution cannot proceed because MSVCP120.dll was not found. Reinstalling the program may fix this problem." Reinstall made no improvement. STEPS TO REPRODUCE 1. Install Marble from file downloaded from website. 2. Start program 3. OBSERVED RESULT System Error EXPECTED RESULT Program start SOFTWARE/OS VERSIONS Windows: Win10 64bit -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 411663] Eliminate delay in dock when using workspace isolation
https://bugs.kde.org/show_bug.cgi?id=411663 --- Comment #17 from leftcrane --- Workspace isolation = "show only launchers from current desktop" If the user checks the "show only launchers from current desktop" box, then the "Slide in and out single windows" should be disabled automatically. Workspace isolation and the "slide in animation" simply do not work well together given Latte's architecture, so it should be one or other but never both. -- You are receiving this mail because: You are watching all bug changes.
[trojita] [Bug 360205] Inconsistent TAB parsing in Subject header
https://bugs.kde.org/show_bug.cgi?id=360205 veggero changed: What|Removed |Added Resolution|--- |INTENTIONAL CC||niccolo.venera...@gmail.com Status|REPORTED|RESOLVED -- You are receiving this mail because: You are watching all bug changes.
[kdeplasma-addons] [Bug 411684] New: Use web site fav icon as the plasmoid dashboard icon
https://bugs.kde.org/show_bug.cgi?id=411684 Bug ID: 411684 Summary: Use web site fav icon as the plasmoid dashboard icon Product: kdeplasma-addons Version: 5.16.5 Platform: Other OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: webbrowser Assignee: plasma-b...@kde.org Reporter: pas...@gmail.com Target Milestone: --- When we use a lot of web browser plasmoid it's hardly distinguishable. I do use some for RocketChat instances at work, having the url fav icon as the plasmoid icon would be a great improvement. For web sites not having fav icon, it would be awesome to be able to set a user one as well. -- You are receiving this mail because: You are watching all bug changes.
[calligraservices] [Bug 302398] Incosistencies
https://bugs.kde.org/show_bug.cgi?id=302398 veggero changed: What|Removed |Added CC||niccolo.venera...@gmail.com Resolution|--- |FIXED Status|REPORTED|RESOLVED -- You are receiving this mail because: You are watching all bug changes.
[kdeplasma-addons] [Bug 359073] web browser widget: shown website cannot be resized, always too small
https://bugs.kde.org/show_bug.cgi?id=359073 Filipe Azevedo changed: What|Removed |Added CC||mur...@gmail.com --- Comment #6 from Filipe Azevedo --- *** Bug 392254 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kdeplasma-addons] [Bug 392254] Fixed zoom factor in KDE Web Browser plasma widget settings
https://bugs.kde.org/show_bug.cgi?id=392254 Filipe Azevedo changed: What|Removed |Added CC||pas...@gmail.com Resolution|--- |DUPLICATE Status|REPORTED|RESOLVED --- Comment #1 from Filipe Azevedo --- *** This bug has been marked as a duplicate of bug 359073 *** -- You are receiving this mail because: You are watching all bug changes.
[kdeplasma-addons] [Bug 359073] web browser widget: shown website cannot be resized, always too small
https://bugs.kde.org/show_bug.cgi?id=359073 Filipe Azevedo changed: What|Removed |Added CC||pas...@gmail.com --- Comment #5 from Filipe Azevedo --- Please do something for that zoom feature, it's clearly an annoying issue. I'm using a 4k screen and it hit me much harder now than before. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 411683] New: Desktop icon right click popup doesn't hide
https://bugs.kde.org/show_bug.cgi?id=411683 Bug ID: 411683 Summary: Desktop icon right click popup doesn't hide Product: plasmashell Version: 5.16.5 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: generic-wayland Assignee: plasma-b...@kde.org Reporter: todaywe@nuke.africa Target Milestone: 1.0 SUMMARY STEPS TO REPRODUCE 1. Right click on desktop icon 2. Click somewhere else 3. Additional element shows in popup - purge(item for shift+del, i'm not on english kde 4. Issue work only if popup shown near mouse/icon and is correct popup, without decorations. If popup with decoration or shown in incorrect place, it will hide fine. 5. Click on "properties" item(last in popup), popup will disappear, properties window won't shown OBSERVED RESULT Popup didn't hide EXPECTED RESULT Popup hidden SOFTWARE/OS VERSIONS Linux/KDE Plasma: Arch Linux (available in About System) KDE Plasma Version: 5.16.5 KDE Frameworks Version: 5.61.0 Qt Version: 5.13.0 Nvidia: 435.21 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 411682] Copy-paste doesn't work in firefox
https://bugs.kde.org/show_bug.cgi?id=411682 cacarry changed: What|Removed |Added Platform|Other |Archlinux Packages -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 411682] New: Copy-paste doesn't work in firefox
https://bugs.kde.org/show_bug.cgi?id=411682 Bug ID: 411682 Summary: Copy-paste doesn't work in firefox Product: plasmashell Version: 5.16.5 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: generic-wayland Assignee: plasma-b...@kde.org Reporter: todaywe@nuke.africa Target Milestone: 1.0 SUMMARY Someone reported this on Firefox bugtracker: https://bugzilla.mozilla.org/show_bug.cgi?id=1567762 Firefox guys said, that this is KDE's issue. STEPS TO REPRODUCE 1. Open firefox 2. Copy something in firefox or outside firefox 3. Paste in firefox or outside OBSERVED RESULT Copy-paste doesn't work EXPECTED RESULT SOFTWARE/OS VERSIONS Linux/KDE Plasma: Arch Linux (available in About System) KDE Plasma Version: 5.16.5 KDE Frameworks Version: 5.61.0 Qt Version: 5.13.0 Nvidia driver: 435.21 ADDITIONAL INFORMATION Someone on firefox bugtracker suggested to try wl-clipboard. I tried it and it doesn't work on KDE for wayland. -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 411657] Latte dock free when used with some combinations of plasmoids
https://bugs.kde.org/show_bug.cgi?id=411657 --- Comment #11 from Filipe Azevedo --- (In reply to Rylsm from comment #9) > Well it doesn't stop you from using AUR or install any Arch Linux packages. > You can install software from AUR from KaOS since it's using the same build > mechanism as Arch. > KaOS is like Manjaro but far more conservative and only focuses on KDE > Plasma DE. > I have the same issue and same debug output on Manjaro. Downgrading ostree > is the only solution for flatpak user. If you can build your own PKGBUILD > you can build your own patched version of ostree from this PR on ostree > Github: https://github.com/ostreedev/ostree/pull/1917 I can now see the relation to ostree ;) Thanks for the link. I will share it to the KaOS team. -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 411657] Latte dock free when used with some combinations of plasmoids
https://bugs.kde.org/show_bug.cgi?id=411657 --- Comment #10 from Filipe Azevedo --- (In reply to Michail Vourlakos from comment #8) > Hm > > If you disable in Latte Global Preferences option, "Press and Hold ⌘ to show > shortcuts badges" > > does it still occur? As say my second comment: As a workaround, disable meta shortcut support from latte dock configure dialog and restart the application hide the issue. I can not check if the badge stuff is still enabled, the config file only show "metaPressAndHoldEnabled=false". The reason why i can not check is that it seems it exist another bug that prevent the config dialog to be shown if a latte dock in panel mode does not contains the latte tasks plasmoid. -- You are receiving this mail because: You are watching all bug changes.
[krdc] [Bug 411680] krdc crashes whith libvnc
https://bugs.kde.org/show_bug.cgi?id=411680 Till Schäfer changed: What|Removed |Added Component|general |VNC Platform|Compiled Sources|Gentoo Packages -- You are receiving this mail because: You are watching all bug changes.
[yakuake] [Bug 411681] New: Yakuake always shown on second monitor on wayland
https://bugs.kde.org/show_bug.cgi?id=411681 Bug ID: 411681 Summary: Yakuake always shown on second monitor on wayland Product: yakuake Version: 3.0.5 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: h...@kde.org Reporter: todaywe@nuke.africa Target Milestone: --- SUMMARY When i press F12, yakuake shows on second monitor, even if mouse is on first STEPS TO REPRODUCE 1. Place mouse on primary monitor 2. Press button to show yakuake OBSERVED RESULT Yakuake shown on incorrect monitor EXPECTED RESULT Yakuake shown on correct monitor SOFTWARE/OS VERSIONS Linux/KDE Plasma: Arch Linux (available in About System) KDE Plasma Version: 5.16.5 KDE Frameworks Version: 5.61.0 Qt Version: 5.13.0 Nvidia driver: 435.21 Card: RTX 2080 Ti ADDITIONAL INFORMATION My secondary monitor is left from my primary monitor, e.g. I have only 2 monitors. -- You are receiving this mail because: You are watching all bug changes.
[krdc] [Bug 411680] New: krdc crashes whith libvnc
https://bugs.kde.org/show_bug.cgi?id=411680 Bug ID: 411680 Summary: krdc crashes whith libvnc Product: krdc Version: 19.08.0 Platform: Compiled Sources OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: uwol...@kde.org Reporter: till2.schae...@uni-dortmund.de Target Milestone: --- Application: krdc (19.08.0) (Compiled from sources) Qt Version: 5.12.4 Frameworks Version: 5.61.0 Operating System: Linux 5.2.9-gentoo x86_64 Distribution: "Gentoo Base System release 2.6" -- Information about the crash: - What I was doing when the application crashed: After connecting to a vnc server, the application crashed. -- Backtrace: Application: KRDC (krdc), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f5653f187c0 (LWP 32348))] Thread 4 (Thread 0x7f56495ad700 (LWP 2009)): [KCrash Handler] #7 0x7f5651750dc6 in open_ssl_connection (client=client@entry=0x7f5640004a00, sockfd=13, anonTLS=anonTLS@entry=-1 '\377', cred=cred@entry=0x0) at /var/tmp/portage/net-libs/libvncserver-0.9.12-r2/work/libvncserver-LibVNCServer-0.9.12/libvncclient/tls_openssl.c:269 #8 0x7f565175158e in InitializeTLSSession (cred=0x0, anonTLS=-1 '\377', client=0x7f5640004a00) at /var/tmp/portage/net-libs/libvncserver-0.9.12-r2/work/libvncserver-LibVNCServer-0.9.12/libvncclient/tls_openssl.c:393 #9 HandleVeNCryptAuth (client=client@entry=0x7f5640004a00) at /var/tmp/portage/net-libs/libvncserver-0.9.12-r2/work/libvncserver-LibVNCServer-0.9.12/libvncclient/tls_openssl.c:611 #10 0x7f565174bdc8 in InitialiseRFBConnection (client=client@entry=0x7f5640004a00) at /var/tmp/portage/net-libs/libvncserver-0.9.12-r2/work/libvncserver-LibVNCServer-0.9.12/libvncclient/rfbproto.c:1157 #11 0x7f565174efe8 in rfbInitConnection (client=0x7f5640004a00) at /var/tmp/portage/net-libs/libvncserver-0.9.12-r2/work/libvncserver-LibVNCServer-0.9.12/libvncclient/vncviewer.c:381 #12 rfbInitClient (client=0x7f5640004a00, argc=argc@entry=0x0, argv=argv@entry=0x0) at /var/tmp/portage/net-libs/libvncserver-0.9.12-r2/work/libvncserver-LibVNCServer-0.9.12/libvncclient/vncviewer.c:493 #13 0x7f5653a31cc7 in VncClientThread::clientCreate (this=this@entry=0x56500cda7d70, reinitialising=reinitialising@entry=false) at /var/tmp/portage/kde-apps/krdc-19.08.0/work/krdc-19.08.0/vnc/vncclientthread.cpp:546 #14 0x7f5653a324bd in VncClientThread::run (this=0x56500cda7d70) at /var/tmp/portage/kde-apps/krdc-19.08.0/work/krdc-19.08.0/vnc/vncclientthread.cpp:459 #15 0x7f5658c1a7f1 in QThreadPrivate::start (arg=0x56500cda7d70) at thread/qthread_unix.cpp:361 #16 0x7f56575bd458 in start_thread () from /lib64/libpthread.so.0 #17 0x7f565888b80f in clone () from /lib64/libc.so.6 Thread 3 (Thread 0x7f56529bd700 (LWP 32459)): #0 0x7f5656a6d849 in g_mutex_lock (mutex=mutex@entry=0x7f5644000bf0) at ../glib-2.60.6/glib/gthread-posix.c:1354 #1 0x7f5656a21e06 in g_main_context_dispatch (context=context@entry=0x7f5644000bf0) at ../glib-2.60.6/glib/gmain.c:3848 #2 0x7f5656a22328 in g_main_context_iterate (context=context@entry=0x7f5644000bf0, block=block@entry=1, dispatch=dispatch@entry=1, self=) at ../glib-2.60.6/glib/gmain.c:3927 #3 0x7f5656a223bc in g_main_context_iteration (context=0x7f5644000bf0, may_block=may_block@entry=1) at ../glib-2.60.6/glib/gmain.c:3988 #4 0x7f5658dfe63b in QEventDispatcherGlib::processEvents (this=0x7f5644000b20, flags=...) at kernel/qeventdispatcher_glib.cpp:424 #5 0x7f5658dab0d3 in QEventLoop::exec (this=this@entry=0x7f56529bcdb0, flags=..., flags@entry=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:140 #6 0x7f5658c195e6 in QThread::exec (this=this@entry=0x7f5657d43d80 <(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at ../../include/QtCore/../../src/corelib/global/qflags.h:120 #7 0x7f5657cc34e5 in QDBusConnectionManager::run (this=0x7f5657d43d80 <(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at qdbusconnection.cpp:178 #8 0x7f5658c1a7f1 in QThreadPrivate::start (arg=0x7f5657d43d80 <(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at thread/qthread_unix.cpp:361 #9 0x7f56575bd458 in start_thread () from /lib64/libpthread.so.0 #10 0x7f565888b80f in clone () from /lib64/libc.so.6 Thread 2 (Thread 0x7f565375b700 (LWP 32448)): #0 0x7f565887f763 in poll () from /lib64/libc.so.6 #1 0x7f565658bc79 in _xcb_conn_wait () from /usr/lib64/libxcb.so.1 #2 0x7f565658d608 in xcb_wait_for_event () from /usr/lib64/libxcb.so.1 #3 0x7f56539018e8 in QXcbEventQueue::run (this=0x56500cb01340) at qxcbeventqueue.cpp:228 #4 0x7f5658c1a7f1 in QThreadPrivate::start (arg=0x56500cb01340) at thread/qthread_unix.cpp:361 #5 0x7f56575bd458 in start_thread ()
[dolphin] [Bug 411223] Dolphin’s sort order chooser human-readable text
https://bugs.kde.org/show_bug.cgi?id=411223 --- Comment #6 from Gabriel Fernandes --- I thought it would land in Dolphin Version 19.08.1 I tried the patch myself, it seems to work -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 411679] Second screen on walyand is black and no icons until i log in X11 session
https://bugs.kde.org/show_bug.cgi?id=411679 cacarry changed: What|Removed |Added Platform|Other |Archlinux Packages -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 411679] New: Second screen on walyand is black and no icons until i log in X11 session
https://bugs.kde.org/show_bug.cgi?id=411679 Bug ID: 411679 Summary: Second screen on walyand is black and no icons until i log in X11 session Product: plasmashell Version: 5.16.5 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Multi-screen support Assignee: aleix...@kde.org Reporter: todaywe@nuke.africa CC: plasma-b...@kde.org Target Milestone: 1.0 SUMMARY When i start kde wayland session, my second monitor is black and has no icons, but i can see apps, cursor. When i log in to X11 session and log out, second screen works fine. I can right click at place where icon should be and i see popup as if there was real icon. STEPS TO REPRODUCE 1. Start computer 2. Start wayland session 3. Second monitor is black and has no icons. 4. Log out or reboot 5. Start X11 session 6. Log out 7. Start wayland session 8. Second monitor has icons and wallpaper SOFTWARE/OS VERSIONS Linux/KDE Plasma: (available in About System) KDE Plasma Version: 5.16.5 KDE Frameworks Version: 5.61.0 Qt Version: 5.13.0 Nvidia driver: 435.21 Card: RTX 2080 Ti -- You are receiving this mail because: You are watching all bug changes.
[kpat] [Bug 395624] Kpat suddenly crashed
https://bugs.kde.org/show_bug.cgi?id=395624 Fabian <0ink...@googlemail.com> changed: What|Removed |Added Latest Commit||https://commits.kde.org/kpa ||t/d7fcc9a0c79f186118e0c2080 ||4af1f7467fc4580 Status|REOPENED|RESOLVED Resolution|--- |FIXED --- Comment #19 from Fabian <0ink...@googlemail.com> --- Git commit d7fcc9a0c79f186118e0c20804af1f7467fc4580 by Fabian Kosmale. Committed on 07/09/2019 at 18:47. Pushed by fabiank into branch 'master'. FcSolveSolver: cleanup ressources The FcSolveSolver did not call its free function in patsolve, leading to ressource exhaustion. M +10 -0patsolve/abstract_fc_solve_solver.cpp https://commits.kde.org/kpat/d7fcc9a0c79f186118e0c20804af1f7467fc4580 -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 411663] Eliminate delay in dock when using workspace isolation
https://bugs.kde.org/show_bug.cgi?id=411663 --- Comment #16 from Michail Vourlakos --- What do you mean the user has chosen Workspace isolation? -- You are receiving this mail because: You are watching all bug changes.
[Falkon] [Bug 411197] Unable to compile, error: ‘const class QString’ has no member named ‘chopped’
https://bugs.kde.org/show_bug.cgi?id=411197
vialav changed:
What|Removed |Added
CC||d...@bk.ru
--- Comment #1 from vialav ---
Hi, Raphael,
I've stumbled upon the same issue, and solved it this way:
- clone the falkon repo, and,
- revert commit f792104be55fca03ad17cdc4244aafce47d0914e (or apply the patch
below), which is essentially what you've asked for (the only lost is the
ability to remove locally installed themes, which I'm sure you could live
without),
- compile it without Python plugins support (see below);
There is a caveat, however, that you most likely would need to revert commit
479933e095168d07a54913f88642cfed4828c167 to compile it with PySide2 << 5.12, if
you want Python plugins support under Qt 5.9.6. Be aware that last revert needs
some extra "polishing" plus back-porting of the two special commits-fixes "from
a future version" to alleviate a bug in PySide2
I'm myself a happy user of the latest Falkon and nearly latest the KDE Plasma,
all are the manually compiled Ubuntu system packages under Qt 5.9.5 LTS ;-)
--- src/lib/preferences/thememanager.cpp
+++ src/lib/preferences/thememanager.cpp
@@ -26,17 +26,15 @@
#include "mainapplication.h"
#include
-#include
ThemeManager::ThemeManager(QWidget* parent, Preferences* preferences)
-: QWidget(parent)
+: QWidget()
, ui(new Ui::ThemeManager)
, m_preferences(preferences)
{
ui->setupUi(parent);
ui->listWidget->setLayoutDirection(Qt::LeftToRight);
ui->license->hide();
-ui->remove->setIcon(QIcon::fromTheme(QSL("edit-delete")));
Settings settings;
settings.beginGroup("Themes");
@@ -69,7 +67,6 @@ ThemeManager::ThemeManager(QWidget* pare
connect(ui->listWidget, ::currentItemChanged, this,
::currentChanged);
connect(ui->license, ::clicked, this,
::showLicense);
-connect(ui->remove, ::clicked, this,
::removeTheme);
currentChanged();
}
@@ -88,25 +85,6 @@ void ThemeManager::showLicense()
v->show();
}
-void ThemeManager::removeTheme()
-{
-QListWidgetItem* currentItem = ui->listWidget->currentItem();
-if (!currentItem) {
-return;
-}
-Theme currentTheme =
m_themeHash[currentItem->data(Qt::UserRole).toString()];
-
-const auto button = QMessageBox::warning(this, tr("Confirmation"),
- tr("Are you sure you want to
remove '%1'?").arg(currentTheme.name),
- QMessageBox::Yes |
QMessageBox::No);
-if (button != QMessageBox::Yes) {
-return;
-}
-
-QDir(currentTheme.themePath).removeRecursively();
-delete currentItem;
-}
-
void ThemeManager::currentChanged()
{
QListWidgetItem* currentItem = ui->listWidget->currentItem();
@@ -120,7 +98,6 @@ void ThemeManager::currentChanged()
ui->author->setText(currentTheme.author);
ui->description->setText(currentTheme.description);
ui->license->setHidden(currentTheme.license.isEmpty());
-ui->remove->setEnabled(QFileInfo(currentTheme.themePath).isWritable());
}
ThemeManager::Theme ThemeManager::parseTheme(const QString , const
QString )
@@ -137,7 +114,6 @@ ThemeManager::Theme ThemeManager::parseT
info.name = metadata.name();
info.description = metadata.comment();
info.author = metadata.value(QSL("X-Falkon-Author")).toString();
-info.themePath = path.chopped(1);
const QString iconName = metadata.icon();
if (!iconName.isEmpty()) {
--- src/lib/preferences/thememanager.h
+++ src/lib/preferences/thememanager.h
@@ -45,7 +45,6 @@ public:
private Q_SLOTS:
void currentChanged();
void showLicense();
-void removeTheme();
private:
struct Theme {
@@ -55,7 +54,6 @@ private:
QString author;
QString description;
QString license;
-QString themePath;
};
Theme parseTheme(const QString , const QString );
--
You are receiving this mail because:
You are watching all bug changes.
[lattedock] [Bug 411663] Eliminate delay in dock when using workspace isolation
https://bugs.kde.org/show_bug.cgi?id=411663 --- Comment #15 from leftcrane --- No, I am saying disable the slide in animation IF the user chooses workspace isolation. This animation has a significant negatively impact on usability when isolation is enabled. There is just no way for an average user is going to be able to figure how to solve this problem - especially since the these two options are in different interfaces (simple/advanced). So you know how to solve the issue it but your users will never figure it out, realistically speaking. So that's why it should be disabled automatically in this case (unless the core architecture changes). I am not saying disable the animation in call cases. -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 411663] Eliminate delay in dock when using workspace isolation
https://bugs.kde.org/show_bug.cgi?id=411663 --- Comment #14 from Michail Vourlakos --- (In reply to leftcrane from comment #12) > > so that support has its limitations. > > OK, fair enough. But I would urge you to block animations automatically if > the user selects desktop isolation, instead of relying on the user to check > all the boxes. (Users shouldn't spend any more time on configuration than > they have to, and Latte dock is very complicated to configure due the > density and variety of options). It's not good usability. Sorry I don't agree, Latte provides animations by default and that is a design decision for almost All docks, give the choice to the user to adjust it to its preference is optional -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 411657] Latte dock free when used with some combinations of plasmoids
https://bugs.kde.org/show_bug.cgi?id=411657 --- Comment #9 from Rylsm --- Well it doesn't stop you from using AUR or install any Arch Linux packages. You can install software from AUR from KaOS since it's using the same build mechanism as Arch. KaOS is like Manjaro but far more conservative and only focuses on KDE Plasma DE. I have the same issue and same debug output on Manjaro. Downgrading ostree is the only solution for flatpak user. If you can build your own PKGBUILD you can build your own patched version of ostree from this PR on ostree Github: https://github.com/ostreedev/ostree/pull/1917 -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 411663] Eliminate delay in dock when using workspace isolation
https://bugs.kde.org/show_bug.cgi?id=411663 --- Comment #13 from leftcrane --- And you can't even disable animations in the simple view. So a user can enable workspace isolation in the simple view but they can't fix the lag issue in the same view - they'd have to switch to advanced and study all the options. -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 411663] Eliminate delay in dock when using workspace isolation
https://bugs.kde.org/show_bug.cgi?id=411663 --- Comment #12 from leftcrane --- > so that support has its limitations. OK, fair enough. But I would urge you to block animations automatically if the user selects desktop isolation, instead of relying on the user to check all the boxes. (Users shouldn't spend any more time on configuration than they have to, and Latte dock is very complicated to configure due the density and variety of options). It's not good usability. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 411667] Dolphin: not a good idea allowing one instance only
https://bugs.kde.org/show_bug.cgi?id=411667 --- Comment #6 from gottfried.muel...@gmx.de --- Now I removed all dolphin informations in my Home directory and started Dolphin again. Now it works fine. I had a view in the differences between the old and new files. There were many many entries. No idea why. But it doesnt matter. It works now. Thank you for the helpful discussion -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 411678] New: Kickoff search doesn't work sometimes
https://bugs.kde.org/show_bug.cgi?id=411678 Bug ID: 411678 Summary: Kickoff search doesn't work sometimes Product: plasmashell Version: 5.16.5 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Application Launcher (Kickoff) Assignee: k...@davidedmundson.co.uk Reporter: todaywe@nuke.africa CC: plasma-b...@kde.org Target Milestone: 1.0 SUMMARY STEPS TO REPRODUCE 1. Open kickoff (super key) 2. Move cursor between or on categories buttons 2. Write some text to search, don't move mouse (search works) 3. Close kickoff (super key) 4. Open kickoff (super key) 5. Write some text again (search doesn't work) Also sometimes search doesn't work, until i move cursor over kickoff and retry search(closing and opening it again), i don't know how to reproduce that issue. OBSERVED RESULT Search works EXPECTED RESULT Search doesn't work SOFTWARE/OS VERSIONS Linux/KDE Plasma: Arch Linux (available in About System) KDE Plasma Version: 5.16.5 KDE Frameworks Version: 5.61.0 Qt Version: 5.13.0 ADDITIONAL INFORMATION Issue happens on wayland and x11 sessions. I'm on nvidia 435.21 -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 411663] Eliminate delay in dock when using workspace isolation
https://bugs.kde.org/show_bug.cgi?id=411663 Michail Vourlakos changed: What|Removed |Added Resolution|--- |INTENTIONAL Status|REPORTED|RESOLVED -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 411663] Eliminate delay in dock when using workspace isolation
https://bugs.kde.org/show_bug.cgi?id=411663 --- Comment #11 from Michail Vourlakos --- In the video I dont see something that it is not intentional. Latte is using plasma libtaskmanager for its tasks/launchers needs so that support has its limitations. Why dont you disable in your animations: "Slide in and out single windows"? -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 411657] Latte dock free when used with some combinations of plasmoids
https://bugs.kde.org/show_bug.cgi?id=411657 --- Comment #8 from Michail Vourlakos --- Hm If you disable in Latte Global Preferences option, "Press and Hold ⌘ to show shortcuts badges" does it still occur? -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 411670] AllScreens tracking is disabled after startup phase
https://bugs.kde.org/show_bug.cgi?id=411670 --- Comment #11 from avlas --- (In reply to Michail Vourlakos from comment #10) > ok... I found it... > > Windows Tracking in v0.9 has been enhanced in a major value... All windows > tracking even for the mentioned applets is taking place in Latte. That will > give you major benefits in multi-screen environments... The issue was that > you had the left panel that was NOT requesting windows tracking and the top > one that it does. Latte faulty because of the left panel was NOT requesting > tracking during startup it was disabling the ALLSCREENS tracking for your > layout. > > > Solution: > A. you wait for to 0.9.3 > B. or a workaround could be the following, activate for your left latte > panel the option "Behavior, Drag and maximize/restore active window" Awesome, thanks! That workaround indeed fixed the issue :) -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 411677] New: HiDPI scaling issues
https://bugs.kde.org/show_bug.cgi?id=411677 Bug ID: 411677 Summary: HiDPI scaling issues Product: kdenlive Version: 19.08.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: User Interface Assignee: j...@kdenlive.org Reporter: phil...@berndt.no Target Milestone: --- Created attachment 122525 --> https://bugs.kde.org/attachment.cgi?id=122525=edit hidpi problem on some windows SUMMARY In the effects/ favorites window the scaling of the fonts is broken STEPS TO REPRODUCE 1. set Scaling to 1.5x 2. open kdenlive 3. OBSERVED RESULT Wrong font size EXPECTED RESULT Normal scaling SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: 5.2.11-1-MANJARO / (available in About System) KDE Plasma Version: 5.16.4 KDE Frameworks Version: 5.61.0 Qt Version: 5.13.0 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 411670] AllScreens tracking is disabled after startup phase
https://bugs.kde.org/show_bug.cgi?id=411670 --- Comment #10 from Michail Vourlakos --- ok... I found it... Windows Tracking in v0.9 has been enhanced in a major value... All windows tracking even for the mentioned applets is taking place in Latte. That will give you major benefits in multi-screen environments... The issue was that you had the left panel that was NOT requesting windows tracking and the top one that it does. Latte faulty because of the left panel was NOT requesting tracking during startup it was disabling the ALLSCREENS tracking for your layout. Solution: A. you wait for to 0.9.3 B. or a workaround could be the following, activate for your left latte panel the option "Behavior, Drag and maximize/restore active window" -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 411670] AllScreens tracking is disabled after startup phase
https://bugs.kde.org/show_bug.cgi?id=411670 Michail Vourlakos changed: What|Removed |Added Latest Commit|https://commits.kde.org/lat |https://commits.kde.org/lat |te-dock/a9b498923689528e00a |te-dock/eb3639914b81370efb9 |3ceff96df8aecda3328ad |b5c972992b456f67ebc68 --- Comment #9 from Michail Vourlakos --- Git commit eb3639914b81370efb9b5c972992b456f67ebc68 by Michail Vourlakos. Committed on 07/09/2019 at 17:38. Pushed by mvourlakos into branch 'master'. update AllScreens track information during startup --Whenever a view is updating its layout then the AllScreens tracked information [per layout tracking] should be updated also. Until now this was happening only during startup and there was a case that if during startup a view was requesting tracking and the second one did not, then tracking for the entire layout for all screens it could be faulty disabled. FIXED-IN:0.9.3 M +15 -4app/wm/tracker/windowstracker.cpp https://commits.kde.org/latte-dock/eb3639914b81370efb9b5c972992b456f67ebc68 -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 411670] AllScreens tracking is disabled after startup phase
https://bugs.kde.org/show_bug.cgi?id=411670 Michail Vourlakos changed: What|Removed |Added Status|CONFIRMED |RESOLVED Latest Commit||https://commits.kde.org/lat ||te-dock/a9b498923689528e00a ||3ceff96df8aecda3328ad Resolution|--- |FIXED Version Fixed In||0.9.3 --- Comment #8 from Michail Vourlakos --- Git commit a9b498923689528e00a3ceff96df8aecda3328ad by Michail Vourlakos. Committed on 07/09/2019 at 17:33. Pushed by mvourlakos into branch 'v0.9'. update AllScreens track information during startup --Whenever a view is updating its layout then the AllScreens tracked information [per layout tracking] should be updated also. Until now this was happening only during startup and there was a case that if during startup a view was requesting tracking and the second one did not, then tracking for the entire layout for all screens it could be faulty disabled. FIXED-IN:0.9.3 M +15 -4app/wm/tracker/windowstracker.cpp https://commits.kde.org/latte-dock/a9b498923689528e00a3ceff96df8aecda3328ad -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 411670] AllScreens tracking is disabled after startup phase
https://bugs.kde.org/show_bug.cgi?id=411670 Michail Vourlakos changed: What|Removed |Added Status|REPORTED|CONFIRMED Ever confirmed|0 |1 -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 411670] AllScreens tracking is disabled after startup phase
https://bugs.kde.org/show_bug.cgi?id=411670 Michail Vourlakos changed: What|Removed |Added Summary|faulty interaction of latte |AllScreens tracking is |0.9 and window |disabled after startup |title/menu/buttons applets |phase |in my layout| -- You are receiving this mail because: You are watching all bug changes.
[amarok] [Bug 411676] New: Amarok is locking up my computer
https://bugs.kde.org/show_bug.cgi?id=411676 Bug ID: 411676 Summary: Amarok is locking up my computer Product: amarok Version: 2.9.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Playback Assignee: amarok-bugs-d...@kde.org Reporter: rjwissb...@centurylink.net CC: ma...@laitl.cz Target Milestone: kf5 SUMMARY I have installed Amarok 2.9.0 using KDE 4.14.38. I have imported music files to mu local collection. I can clear my playlist; I can add songs to my playlist. Whenever I press the play button, the computer completely locks up: Amarok no longer responds; I cannot open the terminal; I cannot open other applications. I have to power down my computer to recover. I am running Ubuntu 18.04.3 LTS. STEPS TO REPRODUCE 1. open Amarok 2. press play icon 3. OBSERVED RESULT computer stops responding to mouse or keyboard input. EXPECTED RESULT music would be nice... SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 409691] Start menu animations broken
https://bugs.kde.org/show_bug.cgi?id=409691 cacarry changed: What|Removed |Added Component|Application Launcher|Application Menu (Kicker) |(Kickoff) | Version|5.16.3 |5.16.5 Assignee|k...@davidedmundson.co.uk|h...@kde.org --- Comment #1 from cacarry --- This happens with kicker launcher. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 409768] Rightclick on System Tray/Taskpanel brings the wrong application back to
https://bugs.kde.org/show_bug.cgi?id=409768 --- Comment #12 from boospy --- When come that fix in KDE? I've updated today application fix. And it is not fixed. Between the time i've updated the files manually. -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 411657] Latte dock free when used with some combinations of plasmoids
https://bugs.kde.org/show_bug.cgi?id=411657 --- Comment #7 from Filipe Azevedo --- KaOS is not ARCH/AUR based at all. While it share something in common (pacman package manager), it is a from scratch distribution and it has its very own packages. Also from the output log, it would looks like a wrongly handled destroyed process, from that i can hardly see a relation to ostree. Using flatpak, i'm not able to delete this file. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 411675] Edited device label is not immediately updated
https://bugs.kde.org/show_bug.cgi?id=411675 --- Comment #1 from Patrick Silva --- it seems related to bug 401145 -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 401145] Partition label is not immediately updated in the places panel if it was modified while Dolphin was running
https://bugs.kde.org/show_bug.cgi?id=401145 Patrick Silva changed: What|Removed |Added Version|19.04.2 |19.08.1 Summary|Partition label is not |Partition label is not |updated in the places panel |immediately updated in the |if it was modified while|places panel if it was |Dolphin was running |modified while Dolphin was ||running -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 411675] New: Edited device label is not immediately updated
https://bugs.kde.org/show_bug.cgi?id=411675 Bug ID: 411675 Summary: Edited device label is not immediately updated Product: plasmashell Version: 5.16.5 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Device Notifier Assignee: plasma-b...@kde.org Reporter: bugsefor...@gmx.com Target Milestone: 1.0 SUMMARY STEPS TO REPRODUCE 1. connect a removable device to usb port (I used a pen drive formatted with fat32 file system) 2. use KDE Partition Manager or Gnome Disks to edit the label of the device just connected to usb port 3. click on the device notifier in systray OBSERVED RESULT popup of the device notifier does not show the device label configured in the step 2. It shows the previous device label instead. EXPECTED RESULT device label is immediately updated after changing. SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 5.16.5 KDE Frameworks Version: 5.61.0 Qt Version: 5.13.1 Kernel Version: 5.2.11-arch1-1-ARCH -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 411663] Eliminate delay in dock when using workspace isolation
https://bugs.kde.org/show_bug.cgi?id=411663 --- Comment #10 from leftcrane --- Created attachment 122524 --> https://bugs.kde.org/attachment.cgi?id=122524=edit small video Watch what happens to the dock. I enable animations since this is the default behavior and allows you to see the problem better. It may be hard to fix though. If you go to the desktop grid, you will see that the task list is the same for each desktop and it has to update every time you switch desktops. This is how the dock is designed. I am not sure if it is feasible to fix this given the architecture. Maybe at least block the animation for this particular case and see if you can optimize the performance a little bit. -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 411670] faulty interaction of latte 0.9 and window title/menu/buttons applets in my layout
https://bugs.kde.org/show_bug.cgi?id=411670 --- Comment #7 from avlas --- (In reply to avlas from comment #6) > (In reply to Michail Vourlakos from comment #4) > > send me your layout please to check it out > > was on it :) Btw, I think I said in reddit when I first mention this, but this was long time ago and I forgot to mention here. The faulty behavior emerged when I moved from latte v0.8 to latte v0.9. So I guess that for whatever reason, latte v0.9 didn't "like" my < v0.9 layout. -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 411663] Eliminate delay in dock when using workspace isolation
https://bugs.kde.org/show_bug.cgi?id=411663 --- Comment #9 from leftcrane --- Yes, this is intended behavior. I am saying it's the wrong behavior. The tasks should appear instantly when you switch desktops. Open windows appear instantly, therefore the tasks should also appear instantly. -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 411670] faulty interaction of latte 0.9 and window title/menu/buttons applets in my layout
https://bugs.kde.org/show_bug.cgi?id=411670 --- Comment #6 from avlas --- (In reply to Michail Vourlakos from comment #4) > send me your layout please to check it out was on it :) -- You are receiving this mail because: You are watching all bug changes.
