[kdenlive] [Bug 398737] Resizing any part of the interface does not work
https://bugs.kde.org/show_bug.cgi?id=398737 --- Comment #5 from emohr --- Please try with the current Kdenlive AppImage version 19.04.2f https://files.kde.org/kdenlive/release/. Goto help -> click reset configuraton. If this is not working delete the Kdenliverc file, see here: https://community.kde.org/Kdenlive/Configuration -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 404384] Show number of entries in group
https://bugs.kde.org/show_bug.cgi?id=404384 Maik Qualmann changed: What|Removed |Added Resolution|--- |FIXED Latest Commit||https://invent.kde.org/kde/ ||digikam/commit/1bf1ef7d097e ||5ac2f1b0f4999b11b002311f146 ||d Version Fixed In||6.2.0 Status|REPORTED|RESOLVED --- Comment #21 from Maik Qualmann --- Git commit 1bf1ef7d097e5ac2f1b0f4999b11b002311f146d by Maik Qualmann. Committed on 22/06/2019 at 05:32. Pushed by mqualmann into branch 'master'. include the leader item in the number of grouped items FIXED-IN: 6.2.0 M +1-1core/libs/widgets/itemview/itemviewdelegate.cpp https://invent.kde.org/kde/digikam/commit/1bf1ef7d097e5ac2f1b0f4999b11b002311f146d -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 408982] Not being able to write person name when tagging faces despite text field having focus
https://bugs.kde.org/show_bug.cgi?id=408982 Maik Qualmann changed: What|Removed |Added Version Fixed In||6.2.0 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 408982] Not being able to write person name when tagging faces despite text field having focus
https://bugs.kde.org/show_bug.cgi?id=408982 Maik Qualmann changed: What|Removed |Added Resolution|--- |FIXED Latest Commit||https://invent.kde.org/kde/ ||digikam/commit/7e212b334cfc ||cfe7be24a26538a11c4afe14d6e ||6 Status|REPORTED|RESOLVED --- Comment #10 from Maik Qualmann --- Git commit 7e212b334cfccfe7be24a26538a11c4afe14d6e6 by Maik Qualmann. Committed on 22/06/2019 at 05:25. Pushed by mqualmann into branch 'master'. set the focus to preview if we have facial regions FIXRD-IN: 6.2.0 M +2-1NEWS M +6-0core/utilities/facemanagement/facegroup.cpp https://invent.kde.org/kde/digikam/commit/7e212b334cfccfe7be24a26538a11c4afe14d6e6 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 409021] Segmentation faults of plasmashell in wl_proxy_set_queue at wayland-client.c:2094 in libwayland-client in Plasma 5.15.5 on Wayland with Qt 5.12.4
https://bugs.kde.org/show_bug.cgi?id=409021 Matt Fagnani changed: What|Removed |Added URL||https://bugzilla.redhat.com ||/show_bug.cgi?id=1723018 Platform|Other |Fedora RPMs -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 409021] New: Segmentation faults of plasmashell in wl_proxy_set_queue at wayland-client.c:2094 in libwayland-client in Plasma 5.15.5 on Wayland with Qt 5.12.4
https://bugs.kde.org/show_bug.cgi?id=409021
Bug ID: 409021
Summary: Segmentation faults of plasmashell in
wl_proxy_set_queue at wayland-client.c:2094 in
libwayland-client in Plasma 5.15.5 on Wayland with Qt
5.12.4
Product: plasmashell
Version: 5.15.5
Platform: Other
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: generic-wayland
Assignee: plasma-b...@kde.org
Reporter: matthew.fagn...@utoronto.ca
Target Milestone: 1.0
Created attachment 121069
--> https://bugs.kde.org/attachment.cgi?id=121069&action=edit
trace of plasmashell segmentation fault in Plasma 5.15.5 on Wayland with Qt
5.12.4
SUMMARY
I saw segmentation faults of plasmashell in wl_proxy_set_queue at
wayland-client.c:2094 in libwayland-client in Plasma 5.15.5 on Wayland with Qt
5.12.4 in Fedora 30. These crashes occurred on startup of one session, and once
in another session. These crashes started right after I updated from Qt 5.12.1
to 5.12.4 from koji along with the dependent Plasma and KF5 rebuilds. drkonqi
wouldn't allow me to submit the attached trace which had the following
segmentation fault and crashing thread.
Application: Plasma (plasmashell), signal: Segmentation fault
Using host libthread_db library "/lib64/libthread_db.so.1".
futex_wait_cancelable (private=0, expected=0, futex_word=0x5653f336ece4) at
../sysdeps/unix/sysv/linux/futex-internal.h:88
88int err = lll_futex_timed_wait (futex_word, expected, NULL, private);
[Current thread is 1 (Thread 0x7f61ca7bbd00 (LWP 1499))]
Thread 22 (Thread 0x7f616a7f9700 (LWP 1746)):
[KCrash Handler]
#6 0x7f61c81846f9 in wl_proxy_set_queue (proxy=0x0, queue=0x5653f2af0370)
at src/wayland-client.c:2094
#7 0x7f61b78f2b50 in QtWaylandClient::QWaylandWindow::waitForFrameSync
(this=0x5653f3779360, timeout=100) at qwaylandwindow.cpp:646
#8 0x7f61b4b4f022 in QtWaylandClient::QWaylandGLContext::swapBuffers
(this=0x5653f361ac70, surface=) at
../../../../hardwareintegration/client/wayland-egl/qwaylandglcontext.cpp:566
#9 0x7f61c8c98441 in QOpenGLContext::swapBuffers (this=0x5653f3930280,
surface=) at kernel/qopenglcontext.cpp:1115
#10 0x7f61ca4b7401 in QSGRenderThread::syncAndRender
(this=this@entry=0x5653f3915590) at scenegraph/qsgthreadedrenderloop.cpp:652
#11 0x7f61ca4bb168 in QSGRenderThread::run (this=0x5653f3915590) at
scenegraph/qsgthreadedrenderloop.cpp:730
#12 0x7f61c86e2786 in QThreadPrivate::start (arg=0x5653f3915590) at
thread/qthread_unix.cpp:361
#13 0x7f61c7b455a2 in start_thread (arg=) at
pthread_create.c:486
#14 0x7f61c8358303 in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95
I think that the segmentation faults might've been due to null pointer
dereferences since proxy=0x0 in the wl_proxy_set_queue call, and proxy was
dereferenced at wayland-client:2095 as proxy->queue without checking if proxy
was null and queue was not null as shown in the wl_proxy_set_queue function.
2091WL_EXPORT void
2092wl_proxy_set_queue(struct wl_proxy *proxy, struct wl_event_queue
*queue)
2093{
2094if (queue)
2095proxy->queue = queue;
2096else
2097proxy->queue = &proxy->display->default_queue;
2098}
qt5-qtwayland functions at #7-8 in the crashing thread and other qt5 functions
lower in the stack might be involved.
STEPS TO REPRODUCE
1. Boot F30 Plasma spin fully updated with updates-testing enabled
2. Log in to Plasma on Wayland from sddm
3. if qt5-qtnetworkauth is installed, sudo dnf remove qt5-qtnetworkauth (due to
dnf dependency problems since qt5-qtnetworkauth-5.12.4 was not available on
koji)
4. dnf upgrade to qt5 5.12.4 with dependent Plasma and kf5 rebuilds from koji
5. reboot
6. Log in to Plasma on Wayland
7. coredumpctl
8. coredumpctl debug
9. gnome-abrt
OBSERVED RESULT
Crashes of plasmashell in Plasma on Wayland with Qt 5.12.4.
EXPECTED RESULT
No crashes.
SOFTWARE/OS VERSIONS
Operating System: Fedora 30, 5.1.12 kernel
KDE Plasma Version: 5.15.5
KDE Frameworks Version: 5.59.0
Qt Version: 5.12.4
kf5-kwayland-0:5.59.0-2.fc30.x86_64
libwayland-client-0:1.17.0-1.fc30.x86_64
plasma-workspace-0:5.15.5-1.fc30.x86_64
qt5-qtwayland-0:5.12.4-1.fc30.x86_64
ADDITIONAL INFORMATION
I haven't seen any such crashes in Plasma on X with Qt 5.12.4.
I've commented on a report of a plasmashell crash in Plasma on Wayland with a
similar trace at https://bugs.kde.org/show_bug.cgi?id=408847
--
You are receiving this mail because:
You are watching all bug changes.
[krita] [Bug 408404] sometimes shortcuts do not function if altered especially in CANVAS OUTPUT SETTINGS. example popup palette does not show up and brush size does not work.
https://bugs.kde.org/show_bug.cgi?id=408404 --- 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.
[krita] [Bug 408392] Crash on opening file or dragging file in to Krita window
https://bugs.kde.org/show_bug.cgi?id=408392 --- 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.
[dolphin] [Bug 401582] Selection with pressed SHIFT does not work on first click - only on second
https://bugs.kde.org/show_bug.cgi?id=401582 --- 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.
[systemsettings] [Bug 407848] Add AMD Variable Refresh Rate toggle (Freesync) in display settings for Xorg
https://bugs.kde.org/show_bug.cgi?id=407848 Bug Janitor Service changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |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.
[frameworks-baloo] [Bug 407664] Dolphin search fully fail sometimes (impredectibly)
https://bugs.kde.org/show_bug.cgi?id=407664 --- Comment #4 from Bug Janitor Service --- Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 408847] Plasma crashes when I click the button to open the apps launcher a few times in sequence
https://bugs.kde.org/show_bug.cgi?id=408847
Matt Fagnani changed:
What|Removed |Added
CC||matthew.fagn...@utoronto.ca
--- Comment #3 from Matt Fagnani ---
Created attachment 121068
--> https://bugs.kde.org/attachment.cgi?id=121068&action=edit
trace of plasmashell segmentation fault in Plasma 5.15.5 on Wayland with Qt
5.12.4
I saw segmentation faults of plasmashell in wl_proxy_marshal_constructor at
wayland-client.c:819 when starting Plasma 5.15.5 on Wayland in Fedora 30. These
crashes occurred on startup of one session, and three times in another session.
These crashes started right after I updated from Qt 5.12.1 to 5.12.4 from koji
along with the dependent Plasma and KF5 rebuilds. drkonqi wouldn't allow me to
submit the attached trace which had the following segmentation fault and
crashing thread.
Application: Plasma (plasmashell), signal: Segmentation fault
Using host libthread_db library "/lib64/libthread_db.so.1".
futex_wait_cancelable (private=0, expected=0, futex_word=0x564abb0ba9b0) at
../sysdeps/unix/sysv/linux/futex-internal.h:88
88int err = lll_futex_timed_wait (futex_word, expected, NULL, private);
[Current thread is 1 (Thread 0x7f5298ae7d00 (LWP 1518))]
Thread 23 (Thread 0x7f522cff7700 (LWP 1744)):
[KCrash Handler]
#6 wl_proxy_marshal_constructor (proxy=0x0, opcode=opcode@entry=3,
interface=0x7f5296fb8980 ) at src/wayland-client.c:819
#7 0x7f52867430ed in wl_surface_frame (wl_surface=) at
../../include/QtWaylandClient/5.12.4/QtWaylandClient/private/../../../../../src/client/wayland-wayland-client-protocol.h:2798
#8 QtWayland::wl_surface::frame (this=this@entry=0x564aba0561a8) at
qwayland-wayland.cpp:1134
#9 0x7f52867203ab in QtWaylandClient::QWaylandWindow::handleUpdate
(this=0x564aba056180) at qwaylandwindow.cpp:1151
#10 0x7f527f9a2f04 in QtWaylandClient::QWaylandGLContext::swapBuffers
(this=0x564aba8448a0, surface=) at
../../../../hardwareintegration/client/wayland-egl/qwaylandglcontext.cpp:568
#11 0x7f5297ac4441 in QOpenGLContext::swapBuffers (this=0x564ab9f4dc10,
surface=) at kernel/qopenglcontext.cpp:1115
#12 0x7f52992e3401 in QSGRenderThread::syncAndRender
(this=this@entry=0x7f524801db40) at scenegraph/qsgthreadedrenderloop.cpp:652
#13 0x7f52992e7168 in QSGRenderThread::run (this=0x7f524801db40) at
scenegraph/qsgthreadedrenderloop.cpp:730
#14 0x7f529750e786 in QThreadPrivate::start (arg=0x7f524801db40) at
thread/qthread_unix.cpp:361
#15 0x7f52969715a2 in start_thread (arg=) at
pthread_create.c:486
#16 0x7f5297184303 in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95
I think the segmentation fault might've been due to a null pointer dereference
since proxy=0x0 in the wl_proxy_marshal_constructor call, and proxy was
dereferenced at wayland-client.c:820 in
proxy->object.interface->methods[opcode].signature
The wl_proxy_marshal_constructor function was as follows
812 WL_EXPORT struct wl_proxy *
813 wl_proxy_marshal_constructor(struct wl_proxy *proxy, uint32_t opcode,
814 const struct wl_interface *interface, ...)
815 {
816 union wl_argument args[WL_CLOSURE_MAX_ARGS];
817 va_list ap;
818
819 va_start(ap, interface);
820
wl_argument_from_va_list(proxy->object.interface->methods[opcode].signature,
821 args, WL_CLOSURE_MAX_ARGS, ap);
822 va_end(ap);
823
824 return wl_proxy_marshal_array_constructor(proxy, opcode,
825 args, interface);
826 }
Functions from qt5-qtwayland at #8-10 and qt5-qtdeclarative lower in the
crashing thread might be involved. I've seen a similar segmentation fault in
plasmashell with qt 5.12.4 with a different trace which I might make another
report for.
SOFTWARE/OS VERSIONS
Operating System: Fedora 30, 5.1.12 kernel
KDE Plasma Version: 5.15.5
KDE Frameworks Version: 5.59.0
Qt Version: 5.12.4
kf5-kwayland-0:5.59.0-2.fc30.x86_64
libwayland-client-0:1.17.0-1.fc30.x86_64
plasma-workspace-0:5.15.5-1.fc30.x86_64
qt5-qtwayland-0:5.12.4-1.fc30.x86_64
The following reports have plasmashell crashes with Qt 5.12.4 with similar
traces:
https://bugs.kde.org/show_bug.cgi?id=408969
https://bugs.kde.org/show_bug.cgi?id=408973
https://bugs.kde.org/show_bug.cgi?id=409014
--
You are receiving this mail because:
You are watching all bug changes.
[elisa] [Bug 407918] Does not find music on other ext4 partition even when added to search paths
https://bugs.kde.org/show_bug.cgi?id=407918 Pablo B changed: What|Removed |Added CC||trippyturtletag...@gmail.co ||m --- Comment #11 from Pablo B --- I'm also having this same issue on Manjaro, although it didn't use to happen a few months ago. My partition is ext4 and it's mounted on /media and doesn't seem to find any files inside it for some reason. I've tried uninstalling, deleting the elisarc file inside .config and reconfiguring but it won't find any files unless I move them to /home/name/Music. I've also tried to create a symlink inside Music folder and still nothings happens. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 409020] New: Discover Crashes as Soon as Started
https://bugs.kde.org/show_bug.cgi?id=409020 Bug ID: 409020 Summary: Discover Crashes as Soon as Started Product: Discover Version: 5.16.1 Platform: openSUSE RPMs OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: discover Assignee: lei...@leinir.dk Reporter: adamska...@gmail.com CC: aleix...@kde.org Target Milestone: --- SUMMARY: Discover crashes as soon as it is launched. Here is what konsole returns when trying to start it. file:///usr/lib64/qt5/qml/QtQuick/Controls.2/org.kde.desktop/private/MobileTextActionsToolBar.qml:62: TypeError: erty 'selectedText' of null file:///usr/lib64/qt5/qml/QtQuick/Controls.2/org.kde.desktop/private/MobileTextActionsToolBar.qml:70: TypeError: erty 'selectedText' of null file:///usr/lib64/qt5/qml/QtQuick/Controls.2/org.kde.desktop/private/MobileTextActionsToolBar.qml:78: TypeError: erty 'canPaste' of null invalid kns backend! "/usr/share/knsrcfiles/ksysguard.knsrc" because: "Config group not found! Check your KNS3 in adding empty sources model QStandardItemModel(0x558a4b028d80) Segmentation fault (core dumped) SOFTWARE/OS VERSIONS Operating System: openSUSE Leap 15.1 KDE Plasma Version: 5.16.1 KDE Frameworks Version: 5.59.0 Qt Version: 5.12.4 Kernel Version: 4.12.14-lp151.28.7-default OS Type: 64-bit -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 409019] New: Krita text box wont display pasted text correctly
https://bugs.kde.org/show_bug.cgi?id=409019 Bug ID: 409019 Summary: Krita text box wont display pasted text correctly Product: krita Version: 4.1.7 Platform: MS Windows OS: MS Windows Status: REPORTED Severity: normal Priority: NOR Component: Tool/Text Assignee: krita-bugs-n...@kde.org Reporter: dave.dr...@uofnkona.edu Target Milestone: --- SUMMARY Krita vector layer text box cannot hold a 'medium sized (arial)' paragraph of text without dropping pieces STEPS TO REPRODUCE 1. text tool -> draw text box 2. select default text and delete 3. switch to Arial font, any size 4. paste in something like: P01-P06 LOWER LEVEL PLUMBING PLANS INCLUDED FOR REFERENCE, SUBMITTED WITH PHASE 2 M01-M03 LOWER LEVEL HVAC PLANS INCLUDED FOR REFERENCE, SUBMITTED WITH PHASE 2 FP1-FP3 LOWER LEVEL FIRE SPRINKLER PLANS INCLUDED FOR REFERENCE, SUBMITTED WITH PHASE 2 OBSERVED RESULT Notice that there's almost nothing you can do to get krita to display the entire contents of the pasted text. EXPECTED RESULT to see the entire text pasted SOFTWARE/OS VERSIONS Windows: 10 macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION Thanks for Krita-ing -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 408748] Applications are not always opened when clicked
https://bugs.kde.org/show_bug.cgi?id=408748 --- Comment #8 from Luca Carlon --- I tried to simply disable nVidia and run on Intel HD only. No issue on Intel HD. The problem occurs only on nVidia. Unfortunately I tried to create a VM to rebuild plasma and run a session there but... believe it or not, virtualbox freezes the system when on nVidia... So, I don't exactly now how to help more on this. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 409018] New: Rendering Selected Zone doesn't Work
https://bugs.kde.org/show_bug.cgi?id=409018 Bug ID: 409018 Summary: Rendering Selected Zone doesn't Work Product: kdenlive Version: 19.04.2 Platform: Other OS: MS Windows Status: REPORTED Severity: normal Priority: NOR Component: Video Display & Export Assignee: j...@kdenlive.org Reporter: mjvilchesf...@gmail.com Target Milestone: --- SUMMARY STEPS TO REPRODUCE 1. Set In point and Out point 2. Render only selected zone OBSERVED RESULT Render finishes right away and the resulting clip is only a few milliseconds. EXPECTED RESULT It should render the entire selected zone. SOFTWARE/OS VERSIONS Windows: 10 macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION Rendering the Full project works fine. It just happens when rendering selected zone. Used the latest Windows version as of June 22, 2019. -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 401677] Some phone models, ROMs or Apps don't report SMS History
https://bugs.kde.org/show_bug.cgi?id=401677 Simon changed: What|Removed |Added Latest Commit||https://invent.kde.org/kde/ ||kdeconnect-android/commit/4 ||18e1a813e8a3c60f4841e9a770a ||e4291ac66db8 Status|CONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #13 from Simon --- Git commit 418e1a813e8a3c60f4841e9a770ae4291ac66db8 by Simon Redman. Committed on 22/06/2019 at 00:49. Pushed by sredman into branch 'master'. Potentially fix SMS/MMS access on Samsung devices According to some information I stumbled across while working on a different issue, Samsung devices do not support the content provider I was using to populate the list of SMS conversations. This is very annoying, but nevertheless there appears to be a workaround. Many users with Samsung devices have reported problems using the SMS plugin. Hopefully this will fix the SMS plugin on Samsung devices. https://invent.kde.org/kde/kdeconnect-android/commit/418e1a813e8a3c60f4841e9a770ae4291ac66db8 -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 358787] deadlock between background parser and code completion
https://bugs.kde.org/show_bug.cgi?id=358787 --- Comment #6 from ms...@fastmail.com --- Hmm, on second thought, it seems that the DUChain read lock is unlocked before createCompletionContext is invoked. Perhaps my above analysis is not the case. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 358787] deadlock between background parser and code completion
https://bugs.kde.org/show_bug.cgi?id=358787 ms...@fastmail.com changed: What|Removed |Added Status|RESOLVED|REOPENED Resolution|WORKSFORME |--- --- Comment #5 from ms...@fastmail.com --- See comment above, definitely still an issue. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 358787] deadlock between background parser and code completion
https://bugs.kde.org/show_bug.cgi?id=358787 ms...@fastmail.com changed: What|Removed |Added CC||ms...@fastmail.com --- Comment #4 from ms...@fastmail.com --- This has occurred on my machine and it appears rather clear the culprit after having done some investigation. The following locking events should make it apparent: ClangParseJob thread: 1. In ClangParseJob::run, ParseSession constructor is invoked which locks on the corresponding parse session. 2. ClangParseInfo::run then invokes ClangHelpers::buildDUChain which then invokes DUChainWriteLocker constructor. ClangCodeCompletion thread: 1. In ClangCodeCompletionWorker::run, DUChainReadLocker constructor is invoked. 2. ClangCodeCompletionWorker::run then invokes createCompletionContext which invokes ClangCodeCompletionContext constructor which then invokes ParseSesssion constructor on the same parse session in ClangParseJob 1. Consequently, ClangCodeCompletion thread could hold a readlock on DUChain while ClangParseJob could hold a lock on the parse session while they both need simultaneous access to both resources. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 409017] New: It is not possible to view/remove the packages installed via the kde store.
https://bugs.kde.org/show_bug.cgi?id=409017 Bug ID: 409017 Summary: It is not possible to view/remove the packages installed via the kde store. Product: plasmashell Version: 5.16.1 Platform: Neon Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: gulpega...@gmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 Created attachment 121067 --> https://bugs.kde.org/attachment.cgi?id=121067&action=edit Windows decoration add-on installer, show plasma widgets (Redshift Control) and not the downloaded and installed windows decorations SUMMARY It is not possible to view the packages installed via the kde store. STEPS TO REPRODUCE 1. Open any configuration tool that includes download from the store by add-on installer (icons, window decorations, colors, ecc) 2. Download a new item (es. new icons pack) 3. Apply new item 4. Open the add-on installer again 5. Select "Installed" radio button OBSERVED RESULT No presence of previously installed packages EXPECTED RESULT List of installed packages and possibility to remove them SOFTWARE/OS VERSIONS Linux/KDE Plasma: Neon KDE KDE Plasma Version: 5.16.1 KDE Frameworks Version: 5.59.0 Qt Version: 5.12.3 ADDITIONAL INFORMATION If a plasma widget is installed (es. Redshift control), it appears in every "Installed" sections of every add-on installer -- 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 --- Comment #9 from Nate Graham --- Nice find! I hope you use `git bisect` for that. :) If you didn't, or you don't know how to use it, let me show you tomorrow! -- 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
--- Comment #8 from Filip Fila ---
I did some poking around. The bug is not reproducible before this commit:
https://github.com/KDE/plasma-desktop/commit/62f92fd822efb059a07dd77c93158ecba73d1ced#diff-5ab15790503cdc8b5d9ba1fff5cebec2
After removing line 524 ("button.clicked();") in master version of
FullRepresentation.qml, the problem goes away.
See: https://phabricator.kde.org/D21978
--
You are receiving this mail because:
You are watching all bug changes.
[lattedock] [Bug 408977] [Wayland] Full screen windows don't take Latte into account
https://bugs.kde.org/show_bug.cgi?id=408977 --- Comment #1 from Michail Vourlakos --- 1. If you close Latte and restart it, same thing happens? 2. Can you send your Latte layout file to try to reproduce in my system? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 406180] KWin 5.15.4+ hang regression on Nvidia Optimus
https://bugs.kde.org/show_bug.cgi?id=406180 --- Comment #88 from Luca Carlon --- I applied the patches in the version posted here to kwin 5.16 and Qt 5.12: no issue even after many hours of uptime. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 409016] New: konsole `\033[0m` not working start from second page of scroll
https://bugs.kde.org/show_bug.cgi?id=409016
Bug ID: 409016
Summary: konsole `\033[0m` not working start from second page
of scroll
Product: konsole
Version: 17.12.3
Platform: Ubuntu Packages
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: general
Assignee: konsole-de...@kde.org
Reporter: limkokh...@gmail.com
Target Milestone: ---
Created attachment 121066
--> https://bugs.kde.org/attachment.cgi?id=121066&action=edit
`\033[0m` not working started from 12th row on second page of scroll.
SUMMARY
konsole `\033[0m` not working started from second page of scroll.
STEPS TO REPRODUCE
1. Run with command for i in {1..100}; do echo "$i"; echo -en '\033[1;42m
A
\033[0m'; echo -e 'next text'; done:
2. Ensure the text overflow to bottom.
3. Scroll the page, the second page (12th row on screenshot) color not reset by
`\033[0m`.
EXPECTED RESULT
`\033[0m' should able to reset color like first page do.
SOFTWARE/OS VERSIONS
Ubuntu 18.04.2 LTS, Gnome, konsole 17.12.3
--
You are receiving this mail because:
You are watching all bug changes.
[systemsettings] [Bug 409015] Splash Screen themes are not set properly when applying Look & Feels
https://bugs.kde.org/show_bug.cgi?id=409015 --- Comment #1 from The Feren OS Dev --- *So, basically with the application of a Look & Feel that has the something along the lines of what is shown below inside of its 'defaults' file, I've noticed odd behaviour with the changing of the current Splash Screen in use during the Look & Feel application process. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 409015] New: Splash Screen themes are not set properly when applying Look & Feels
https://bugs.kde.org/show_bug.cgi?id=409015 Bug ID: 409015 Summary: Splash Screen themes are not set properly when applying Look & Feels Product: systemsettings Version: 5.16.1 Platform: Neon Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: kcm_lookandfeel Assignee: plasma-b...@kde.org Reporter: ferenos...@outlook.com Target Milestone: --- SUMMARY So, basically with a Look & Feel that has the following under its 'defaults' file, I've noticed odd behaviour with the changing of Splash Screens during this process. Mainly that the Look & Feel switcher seems to ignore the fact that the 'defaults' file has asked that a certain splash screen be set and instead sets the splash screen to be the name of the Look & Feel applied. e.g.: Got a theme named 'org.feren.dark', with the below contents in its 'details' file? It sets the splash screen to 'org.feren.dark' instead of 'org.feren.default': Setting in 'details' file: [ksplashrc][KSplash] Theme=org.feren.default STEPS TO REPRODUCE 1. Make a Look & Feel that should in theory set the Splash Screen to a splash screen that is part of another Look & Feel instead of itself 2. Apply the Look & Feel OBSERVED RESULT In ksplashrc, the setting can be observed to have changed to what the Look & Feel's folder name is, rather than the requested Splash Screen theme name EXPECTED RESULT The requested Splash Screen theme would be set during Look & Feel application SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: KDE neon 5.16.1 (available in About System) KDE Plasma Version: 5.16.1 KDE Frameworks Version: 5.59.0 Qt Version: 5.12.3 ADDITIONAL INFORMATION N/A -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 409014] Plasma (Wayland) crashed after pressing the meta key four times in a short time.
https://bugs.kde.org/show_bug.cgi?id=409014 --- Comment #1 from Adrian Wannenmacher --- I forgot to mention that I also tried this with a plasma session on X. In that case, the crash doesn't happen. -- You are receiving this mail because: You are watching all bug changes.
[ktouch] [Bug 408862] Ktouch 19.04.2-1 graphic bug with the results
https://bugs.kde.org/show_bug.cgi?id=408862 --- Comment #4 from nl.smart --- Hi, Thanks for the bug fix, I'll post a report with the next ktouch version. see you later -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 409014] New: Plasma (Wayland) crashed after pressing the meta key four times in a short time.
https://bugs.kde.org/show_bug.cgi?id=409014 Bug ID: 409014 Summary: Plasma (Wayland) crashed after pressing the meta key four times in a short time. Product: plasmashell Version: 5.16.1 Platform: Archlinux Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: adiw...@gmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 Application: plasmashell (5.16.1) Qt Version: 5.12.4 Frameworks Version: 5.59.0 Operating System: Linux 5.1.11-arch1-1-ARCH x86_64 Distribution (Platform): Archlinux Packages -- Information about the crash: I just logged into my system and wanted to start an application from the default application launcher. When I pressed the meta key the first time, the background of the menu appeared first and then the application icons and names slowly faded in. As I didn't expect that to happen, I decided to press the button two more times to reopen the menu and it seemingly worked. But when I pressed the button again to close the menu, plasma crashed. After a crash plasma is automatically restarted. If its the first restart, I can trigger the crash like I described before. If its the second restart, the menu doesn't appear any more. The only thing that happens is that a blue litte bar appears (or disappears) above the icon to indicate that its active. I also can't trigger the crash any more. I tried to re-login and to restart the system, but plasma keeps crashing if i press the meta key four times is a short period of time. I also tried what happens if I press the button with some distance between each hit and in that case plasma doesn't crash. The crash can be reproduced every time. -- Backtrace: Application: Plasma (plasmashell), signal: Segmentation fault Using host libthread_db library "/usr/lib/libthread_db.so.1". [Current thread is 1 (Thread 0x7fac24633880 (LWP 23000))] Thread 26 (Thread 0x7fabb13f5700 (LWP 23331)): #0 0x7fac222c73c5 in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7fac230148dc in QWaitCondition::wait(QMutex*, QDeadlineTimer) () at /usr/lib/libQt5Core.so.5 #2 0x7fac230149ca in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/libQt5Core.so.5 #3 0x7fac24dc74cd in () at /usr/lib/libQt5Quick.so.5 #4 0x7fac24dc773c in () at /usr/lib/libQt5Quick.so.5 #5 0x7fac2300e5fc in () at /usr/lib/libQt5Core.so.5 #6 0x7fac222c157f in start_thread () at /usr/lib/libpthread.so.0 #7 0x7fac22c9bf13 in clone () at /usr/lib/libc.so.6 Thread 25 (Thread 0x7fabb1bf6700 (LWP 23330)): #0 0x7fac222c73c5 in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7fac15f1b6bc in () at /usr/lib/dri/radeonsi_dri.so #2 0x7fac15f1b2b8 in () at /usr/lib/dri/radeonsi_dri.so #3 0x7fac222c157f in start_thread () at /usr/lib/libpthread.so.0 #4 0x7fac22c9bf13 in clone () at /usr/lib/libc.so.6 Thread 24 (Thread 0x7fabb23f7700 (LWP 23277)): [KCrash Handler] #6 0x7fac22adde94 in wl_proxy_marshal_constructor () at /usr/lib/libwayland-client.so.0 #7 0x7fac1dc5019b in QtWaylandClient::QWaylandWindow::handleUpdate() () at /usr/lib/libQt5WaylandClient.so.5 #8 0x7fac16c40d78 in () at /usr/lib/qt/plugins/wayland-graphics-integration-client/libqt-plugin-wayland-egl.so #9 0x7fac235e22f0 in QOpenGLContext::swapBuffers(QSurface*) () at /usr/lib/libQt5Gui.so.5 #10 0x7fac24dc382e in () at /usr/lib/libQt5Quick.so.5 #11 0x7fac24dc76f8 in () at /usr/lib/libQt5Quick.so.5 #12 0x7fac2300e5fc in () at /usr/lib/libQt5Core.so.5 #13 0x7fac222c157f in start_thread () at /usr/lib/libpthread.so.0 #14 0x7fac22c9bf13 in clone () at /usr/lib/libc.so.6 Thread 23 (Thread 0x7fabb2bf8700 (LWP 23276)): #0 0x7fac222c73c5 in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7fac15f1b6bc in () at /usr/lib/dri/radeonsi_dri.so #2 0x7fac15f1b2b8 in () at /usr/lib/dri/radeonsi_dri.so #3 0x7fac222c157f in start_thread () at /usr/lib/libpthread.so.0 #4 0x7fac22c9bf13 in clone () at /usr/lib/libc.so.6 Thread 22 (Thread 0x7fabb33f9700 (LWP 23235)): #0 0x7fac222c772c in pthread_cond_timedwait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7fac23014859 in QWaitCondition::wait(QMutex*, QDeadlineTimer) () at /usr/lib/libQt5Core.so.5 #2 0x7fac23014998 in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/libQt5Core.so.5 #3 0x7fac23011e6b in () at /usr/lib/libQt5Core.so.5 #4 0x7fac2300e5fc in () at /usr/lib/libQt5Core.so.5 #5 0x7fac222c157f in start_thread () at /usr/lib/libpthread.so.0 #6 0x7fac22c9bf13 in clone () at /usr/lib/libc.so.6 Thread 21 (Thread 0x7fabc700 (LWP 23234)): #0 0x7fac22c91497 in poll () at /usr/lib/libc.so.6 #1
[kwin] [Bug 408754] kwin-5.16.0: GUI (Wayland) freezes
https://bugs.kde.org/show_bug.cgi?id=408754 David Edmundson changed: What|Removed |Added Resolution|WAITINGFORINFO |--- Ever confirmed|0 |1 Status|NEEDSINFO |CONFIRMED --- Comment #12 from David Edmundson --- I see what's wrong. We can infinite loop if we're placing a window with an invalid size in some conditions. Will fix. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 408982] Not being able to write person name when tagging faces despite text field having focus
https://bugs.kde.org/show_bug.cgi?id=408982 --- Comment #9 from Maik Qualmann --- It also works in Dolphin, I have never noticed it... Maik -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 408982] Not being able to write person name when tagging faces despite text field having focus
https://bugs.kde.org/show_bug.cgi?id=408982 --- Comment #8 from Maik Qualmann --- I have to take something back, the first letter works here too... Maik -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 408982] Not being able to write person name when tagging faces despite text field having focus
https://bugs.kde.org/show_bug.cgi?id=408982 --- Comment #7 from IWBR --- That is weird. I'll try it in my windows partition, to see if it also happens, and report back. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 408982] Not being able to write person name when tagging faces despite text field having focus
https://bugs.kde.org/show_bug.cgi?id=408982 --- Comment #6 from Maik Qualmann --- The main problem is that selecting the images in the icon view or preview with the first letter is not implemented or wanted at all. I am at a loss. Maik -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 408982] Not being able to write person name when tagging faces despite text field having focus
https://bugs.kde.org/show_bug.cgi?id=408982 --- Comment #5 from IWBR --- If I press "G" on the Thumbnail or Preview view, a picture in the album whose filename starts by G is selected. Same for other letters. For instance, I can switch between game-of-thrones.jpeg, 2604185h688.jpg, and b3dbddb3-game-of-thrones-season-8-episode-4.jpg by pressing the keys "G", "2" and "B". In the preview view (where the bug seems to happen), it only jumps from picture to picture if the Thumbbar (Control+T) is "selected"/"focused". If you click on the picture preview itself, the thumbbar is no longer "selected", and selecting files by pressing those keys is not enabled anymore (and I presume face names can be entered just fine). So I think that the issue is that, when you switch from one picture to the next in the thumbbar, the thumbbar is still "selected"/"focused" instead of the picture itself, and even if you see a vertical cursor blinking on the face name text field, typing a name will act on the thumbbar (by changing the picture), not on the text field. To solve it, I think either the picture preview gets the focus automatically, or do not show a cursor blinking on the text field as if it is waiting for text to be written. (do you follow what I mean?) -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 408805] Colorpicker preview shows black preview
https://bugs.kde.org/show_bug.cgi?id=408805 --- Comment #9 from Lai --- The only thing that changed within the 4 days of working on this file was that I exported it the night before as a png -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 408958] digikam crashes on deletion of new files from SD card (import window)
https://bugs.kde.org/show_bug.cgi?id=408958 Maik Qualmann changed: What|Removed |Added CC||metzping...@gmail.com --- Comment #6 from Maik Qualmann --- Thanks! Let's hope the crash is safely fixed. ((:-)) Maik -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 408805] Colorpicker preview shows black preview
https://bugs.kde.org/show_bug.cgi?id=408805 --- Comment #8 from Lai --- Created attachment 121065 --> https://bugs.kde.org/attachment.cgi?id=121065&action=edit image contains observed result -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 409013] New: Fix background color and frame of search result
https://bugs.kde.org/show_bug.cgi?id=409013 Bug ID: 409013 Summary: Fix background color and frame of search result Product: okular Version: 1.6.2 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: okular-de...@kde.org Reporter: bing...@gmail.com Target Milestone: --- It is absolutely annoying that the background color of search results is the same as the standard color for highlighting text, i.e. yellow 2) It very annoying that the frame around the search result is a very thin black box. This should be way more prominent also to compensate for above annoyance! I have previously suggested to use a color for search results that is not available for other functionality like highlighting! If you highlight a lot in a PDF file then the search function becomes essentially useless! Very annoying! Would you finally please fix this annoyance!!! SUMMARY STEPS TO REPRODUCE 1. 2. 3. 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.
[kdevelop] [Bug 408965] KDevelop Crashes No Action after kdev-python plugin installed
https://bugs.kde.org/show_bug.cgi?id=408965 --- Comment #2 from chris+kde...@halbersma.us --- Disabling the kdev-python plugin in the interface seems to fix the problem. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 408982] Not being able to write person name when tagging faces despite text field having focus
https://bugs.kde.org/show_bug.cgi?id=408982 --- Comment #4 from Maik Qualmann --- I can not reproduce the behavior here on openSUSE Linux or under Windows. Are there any global key shortcuts defined on Ubuntu? Do I understand it correctly, if you press "G", it jumps to first image in the list? In the preview, the cursor keys, image up/down, ESC and "T" defined, nothing else. What happens if you open a image in the preview without facial regions and test all letters? Maik -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 409012] New: Desktop freeze when move window to top
https://bugs.kde.org/show_bug.cgi?id=409012 Bug ID: 409012 Summary: Desktop freeze when move window to top Product: kwin Version: 5.16.1 Platform: Neon Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kwin-bugs-n...@kde.org Reporter: ser...@iskynet.es Target Milestone: --- SUMMARY STEPS TO REPRODUCE 1. Move any window from the title bar to top for maximize or side. OBSERVED RESULT If I open a window and move it from the title bar to the top of the screen to maximize it or to the side so that it occupies half of the monitor, the computer keeps a few seconds (10-15 seconds) frozen and then everything goes well. I HAVE OBSERVED THAT THIS HAPPEN WHEN I USE MY MONITOR NETBOOK. IF I USE A EXTERNAL MONITOR THIS DON'T HAPPEN. My netbook is MSI GS75 and it have Nvidia Optimus (RTX2016 + Intel).I have installed nvidia drivers propietary and selected nvidia card in prime profiles. I like workaround this run if i disable compositor. EXPECTED RESULT SOFTWARE/OS VERSIONS Linux/KDE Plasma: KDE NEON 18.04 (available in About System) KDE Plasma Version: 5.16.1 KDE Frameworks Version: 5.59.0 Qt Version: 5.12.3 -- You are receiving this mail because: You are watching all bug changes.
[kdeplasma-addons] [Bug 408959] System load viewer: grayed-out box "CPUs separately" without indication why it is disabled
https://bugs.kde.org/show_bug.cgi?id=408959 --- Comment #2 from Ralf Jung --- Ah, that does it, thanks a lot! I tried various things but not that combination, it seems. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 408805] Colorpicker preview shows black preview
https://bugs.kde.org/show_bug.cgi?id=408805 Lai changed: What|Removed |Added Status|RESOLVED|REOPENED Resolution|LATER |--- Ever confirmed|0 |1 --- Comment #7 from Lai --- I started this project 4 days ago. I reopened it today to work on it, the brush no longer works. SESSION: 21 Jun 2019 15:52:38 -0500. Executing C:\Program Files\Krita (x64)\bin\krita.exe WARNING: This file contains information about your system and the images you have been working with. If you have problems with Krita, the Krita developers might ask you to share this file with them. The information in this file is not shared automatically with the Krita developers in any way. You can disable logging to this file in Krita's Configure Krita Dialog. Please review the contents of this file before sharing this file with anyone. Krita Version: 4.2.1 Languages: en_US Hidpi: true Qt Version (compiled): 5.12.3 Version (loaded): 5.12.3 OS Information Build ABI: x86_64-little_endian-llp64 Build CPU: x86_64 CPU: x86_64 Kernel Type: winnt Kernel Version: 10.0.17134 Pretty Productname: Windows 10 (10.0) Product Type: windows Product Version: 10 Hardware Information GPU Acceleration: auto Memory: 16309 Mb Number of Cores: 4 Swap Location: C:/Users/Kurai/AppData/Local/Temp 21 Jun 2019 15:53:11 -0500: Importing image/png to application/x-krita. Location: D:/Art/ReiJin/ReiJin_Pose.png. Real location: D:/Art/ReiJin/ReiJin_Pose.png. Batchmode: 0 21 Jun 2019 15:53:13 -0500: Disabled smoothing. 21 Jun 2019 15:53:13 -0500: Disabled smoothing. 21 Jun 2019 15:53:13 -0500: Disabled smoothing. 21 Jun 2019 15:53:30 -0500: Importing application/x-krita to application/x-krita. Location: D:/Art/ReiJin_Pose.kra. Real location: D:/Art/ReiJin_Pose.kra. Batchmode: 0 21 Jun 2019 15:53:30 -0500: Importing image/png to application/x-krita. Location: C:/Users/Kurai/AppData/Local/Temp/krita_file_layer_copy_11832_20711.png. Real location: C:/Users/Kurai/AppData/Local/Temp/krita_file_layer_copy_11832_20711.png. Batchmode: 0 21 Jun 2019 15:53:37 -0500: Disabled smoothing. 21 Jun 2019 15:53:37 -0500: Disabled smoothing. 21 Jun 2019 15:53:37 -0500: Disabled smoothing. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 409011] New: Animation audio does not sync to frames
https://bugs.kde.org/show_bug.cgi?id=409011 Bug ID: 409011 Summary: Animation audio does not sync to frames Product: krita Version: 4.2.1 Platform: macOS Disk Images OS: macOS Status: REPORTED Severity: normal Priority: NOR Component: Animation Assignee: krita-bugs-n...@kde.org Reporter: satirr...@gmail.com Target Milestone: --- SUMMARY Animation audio does not sync to frames STEPS TO REPRODUCE 1. Add audio to animation 2. Play animation 3. Frames do not sync to audio OBSERVED RESULT Frames play significantly after where they should be placed in regard to audio cues. EXPECTED RESULT Frames play at at the correct time in the audio sequence. SOFTWARE/OS VERSIONS Windows: macOS: 10.14.5 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 385589] Audio glitching in animation
https://bugs.kde.org/show_bug.cgi?id=385589 satirr...@gmail.com changed: What|Removed |Added CC||satirr...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kolourpaint] [Bug 409003] Make anti-aliasing optional
https://bugs.kde.org/show_bug.cgi?id=409003 Martin Koller changed: What|Removed |Added Resolution|--- |WORKSFORME Status|REPORTED|RESOLVED CC||kol...@aon.at --- Comment #1 from Martin Koller --- Is already there. Settings -> Draw Anti-Aliased -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 406180] KWin 5.15.4+ hang regression on Nvidia Optimus
https://bugs.kde.org/show_bug.cgi?id=406180 --- Comment #87 from Erik Kurzinger --- Did you apply the qtbase patch from the earlier comment on this bug? Or the one that was committed upstream? https://code.qt.io/cgit/qt/qtbase.git/commit/?id=0c1831178540462da31fd7a4b6d2e446bc84498b The patch was changed a bit during review, and I think the version ended up getting merged is more correct so I would recommend using that. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 406803] If I want to add an yahoo account to kmail I was asked for an google account
https://bugs.kde.org/show_bug.cgi?id=406803 svenz...@gmail.com changed: What|Removed |Added CC||svenz...@gmail.com --- Comment #1 from svenz...@gmail.com --- Same problem on opensuse leap 15.1 (kmail2 5.10.3) -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 406180] KWin 5.15.4+ hang regression on Nvidia Optimus
https://bugs.kde.org/show_bug.cgi?id=406180 --- Comment #86 from Drake --- I have applied the patch from Erik for Kwin and yours for QTBase. on 5.15 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 406180] KWin 5.15.4+ hang regression on Nvidia Optimus
https://bugs.kde.org/show_bug.cgi?id=406180 --- Comment #85 from David Edmundson --- Please be clear about which patches you have. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 406180] KWin 5.15.4+ hang regression on Nvidia Optimus
https://bugs.kde.org/show_bug.cgi?id=406180 --- Comment #84 from Drake --- Can anybody confirm that the effect reappears after a while even when using the patches ? The patches seem to work a while but if you use KDE for 1-2 hours it starts to freeze again. Shorter then without the patch, but every time you snap the window. Only a restart helps. -- You are receiving this mail because: You are watching all bug changes.
[KEXI] [Bug 408013] Table leftmost "selector" column cells do not align with table rows
https://bugs.kde.org/show_bug.cgi?id=408013 Jarosław Staniek changed: What|Removed |Added Assignee|kexi-b...@kde.org |stan...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[KEXI] [Bug 408013] Table leftmost "selector" column cells do not align with table rows
https://bugs.kde.org/show_bug.cgi?id=408013 Jarosław Staniek changed: What|Removed |Added CC||stan...@kde.org Target Milestone|--- |3.2.1 Version|3.2.0 Beta |3.2.0 Ever confirmed|0 |1 Status|REPORTED|CONFIRMED --- Comment #2 from Jarosław Staniek --- Confirmed in 3.2.0 final too, scheduled, thanks. -- You are receiving this mail because: You are watching all bug changes.
[KEXI] [Bug 406399] Cannot open an imported access-file
https://bugs.kde.org/show_bug.cgi?id=406399 --- Comment #5 from Jarosław Staniek --- With all the respect, changed the Importance to normal. Critical level would not speed up resolution I think, and Critical would fit more to severe security or data loss bugs, not to issues like this one. It is hard to generally say what kinds of reports have assured faster fixes, apart from reports coming from paying customers. -- You are receiving this mail because: You are watching all bug changes.
[KEXI] [Bug 406399] Cannot open an imported access-file
https://bugs.kde.org/show_bug.cgi?id=406399 Jarosław Staniek changed: What|Removed |Added Severity|critical|normal -- You are receiving this mail because: You are watching all bug changes.
[KEXI] [Bug 408853] Crash on Form Design, probably with check boxes and yes/no fields.
https://bugs.kde.org/show_bug.cgi?id=408853 --- Comment #2 from Jarosław Staniek --- PS: In KEXI 3.1 or newer before saving table design changes your forms will be closed. This is potential difference to 3.0 that, if I remember correctly can prevent any such issues. -- You are receiving this mail because: You are watching all bug changes.
[elisa] [Bug 409010] New: Elisa crashed on close
https://bugs.kde.org/show_bug.cgi?id=409010 Bug ID: 409010 Summary: Elisa crashed on close Product: elisa Version: unspecified Platform: unspecified OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: matthieu_gall...@yahoo.fr Reporter: bugsefor...@gmx.com Target Milestone: --- Application: elisa (0.4.80) Qt Version: 5.12.3 Frameworks Version: 5.60.0 Operating System: Linux 4.18.0-22-generic x86_64 Distribution: KDE neon Unstable Edition -- Information about the crash: - What I was doing when the application crashed: Elisa crashed when closed on Wayland. It happened just once, i can't reproduce consistently. The crash can be reproduced sometimes. -- Backtrace: Application: Elisa (elisa), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7fa308ada840 (LWP 15314))] Thread 12 (Thread 0x7fa2c503b700 (LWP 15328)): [KCrash Handler] #6 0x7fa2f3ed4cf9 in wl_proxy_marshal () from /usr/lib/x86_64-linux-gnu/libwayland-client.so.0 #7 0x7fa2f435a29a in wl_surface_damage (height=, width=, y=, x=, wl_surface=) at ../../include/QtWaylandClient/5.12.3/QtWaylandClient/private/../../../../../src/client/wayland-wayland-client-protocol.h:2753 #8 QtWayland::wl_surface::damage (this=, x=, y=, width=, height=) at qwayland-wayland.cpp:1124 #9 0x7fa2f433d474 in QtWaylandClient::QWaylandWindow::damage (this=, rect=...) at qwaylandwindow.cpp:565 #10 0x7fa2f4347a69 in QtWaylandClient::QWaylandAbstractDecoration::contentImage (this=0x7f62a00900c0) at qwaylandabstractdecoration.cpp:134 #11 0x7fa2e3796778 in QtWaylandClient::DecorationsBlitter::blit (window=0x5635bb103ef0, this=) at ../../../../hardwareintegration/client/wayland-egl/qwaylandglcontext.cpp:198 #12 QtWaylandClient::QWaylandGLContext::swapBuffers (this=0x5635baeba300, surface=) at ../../../../hardwareintegration/client/wayland-egl/qwaylandglcontext.cpp:556 #13 0x7fa3069a0dbf in QOpenGLContext::swapBuffers (this=0x5635bb2777d0, surface=) at kernel/qopenglcontext.cpp:1115 #14 0x7fa302769ed9 in QSGRenderThread::syncAndRender (this=this@entry=0x5635bb284a50) at scenegraph/qsgthreadedrenderloop.cpp:652 #15 0x7fa30276dae8 in QSGRenderThread::run (this=0x5635bb284a50) at scenegraph/qsgthreadedrenderloop.cpp:730 #16 0x7fa305b1fc72 in QThreadPrivate::start (arg=0x5635bb284a50) at thread/qthread_unix.cpp:361 #17 0x7fa3014456db in start_thread (arg=0x7fa2c503b700) at pthread_create.c:463 #18 0x7fa30541f88f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 11 (Thread 0x7fa2c583c700 (LWP 15327)): #0 0x7fa30540e0b4 in __GI___libc_read (fd=21, buf=0x7fa2c583bb9e, nbytes=10) at ../sysdeps/unix/sysv/linux/read.c:27 #1 0x7fa2f81d5021 in pa_read () from /usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-11.1.so #2 0x7fa2feb3aa2e in pa_mainloop_prepare () from /usr/lib/x86_64-linux-gnu/libpulse.so.0 #3 0x7fa2feb3b4a0 in pa_mainloop_iterate () from /usr/lib/x86_64-linux-gnu/libpulse.so.0 #4 0x7fa2feb3b560 in pa_mainloop_run () from /usr/lib/x86_64-linux-gnu/libpulse.so.0 #5 0x7fa2feb493c9 in ?? () from /usr/lib/x86_64-linux-gnu/libpulse.so.0 #6 0x7fa2f8204318 in ?? () from /usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-11.1.so #7 0x7fa3014456db in start_thread (arg=0x7fa2c583c700) at pthread_create.c:463 #8 0x7fa30541f88f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 10 (Thread 0x7fa2c74f5700 (LWP 15326)): #0 0x7fa305412bf9 in __GI___poll (fds=0x7fa2bc004a70, nfds=1, timeout=8871) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7fa2fedb34c9 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7fa2fedb35dc in g_main_context_iteration () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7fa305d55dcb in QEventDispatcherGlib::processEvents (this=0x7fa2bc000b20, flags=...) at kernel/qeventdispatcher_glib.cpp:424 #4 0x7fa305cf703a in QEventLoop::exec (this=this@entry=0x7fa2c74f4d60, flags=..., flags@entry=...) at kernel/qeventloop.cpp:225 #5 0x7fa305b1e4ca in QThread::exec (this=) at thread/qthread.cpp:531 #6 0x7fa305b1fc72 in QThreadPrivate::start (arg=0x5635bb10fd40) at thread/qthread_unix.cpp:361 #7 0x7fa3014456db in start_thread (arg=0x7fa2c74f5700) at pthread_create.c:463 #8 0x7fa30541f88f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 9 (Thread 0x7fa2c7fff700 (LWP 15325)): #0 0x7fa2fedf9379 in g_mutex_lock () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #1 0x7fa2fedb2895 in g_main_context_prepare () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7fa2fedb33fb in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7fa2fedb35dc in g_main_context_iteration () from /usr/lib/
[KEXI] [Bug 408423] Cannot edit data
https://bugs.kde.org/show_bug.cgi?id=408423 --- Comment #5 from Jarosław Staniek --- Ray, maybe this helps, please tell me anyway: I've added this chapter in the wiki after the 3.2 release: https://community.kde.org/Kexi/Snapshots#Short_Flatpak_How_To Here you can see how to enable write access in your $HOME directory for KEXI. You can choose any other dir if you prefer. By default KEXI in Flatpak version won't have write access to any location. -- You are receiving this mail because: You are watching all bug changes.
[KEXI] [Bug 408853] Crash on Form Design, probably with check boxes and yes/no fields.
https://bugs.kde.org/show_bug.cgi?id=408853 Jarosław Staniek changed: What|Removed |Added Version|unspecified |3.0.1 Component|General |Tables -- You are receiving this mail because: You are watching all bug changes.
[KEXI] [Bug 408853] Crash on Form Design, probably with check boxes and yes/no fields.
https://bugs.kde.org/show_bug.cgi?id=408853 Jarosław Staniek changed: What|Removed |Added CC||stan...@kde.org Status|REPORTED|NEEDSINFO Resolution|--- |WAITINGFORINFO --- Comment #1 from Jarosław Staniek --- Thanks for the report. I would need one of the things: - detailed list of actions, sample database welcome too - confirmation that you are able to reproduce the same issue on KEXI 3.2.0 I do not support 3.0 personally. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 398737] Resizing any part of the interface does not work
https://bugs.kde.org/show_bug.cgi?id=398737 Herrmanius changed: What|Removed |Added CC||flowr...@gmx.net --- Comment #4 from Herrmanius --- Still happening on 19.04.2 on Ubuntu 18.04.2 -- You are receiving this mail because: You are watching all bug changes.
[KEXI] [Bug 408852] SQL query - filter that use values from secondary tables
https://bugs.kde.org/show_bug.cgi?id=408852 Jarosław Staniek changed: What|Removed |Added Severity|critical|normal CC||stan...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 408958] digikam crashes on deletion of new files from SD card (import window)
https://bugs.kde.org/show_bug.cgi?id=408958 --- Comment #5 from weltq...@gmail.com --- (In reply to Maik Qualmann from comment #3) > Git commit d62003a995a226e54e1da08a828d11fed989f528 by Maik Qualmann. > Committed on 20/06/2019 at 17:44. > Pushed by mqualmann into branch 'master'. > > check for valid ModelIndex > FIXED-IN: 6.2.0 > > M +2-1NEWS > M +22 -4core/utilities/import/models/importimagemodel.cpp > > https://invent.kde.org/kde/digikam/commit/ > d62003a995a226e54e1da08a828d11fed989f528 I say thank you: PayPal Transaktionscode: 7UE89264L4058940C -- You are receiving this mail because: You are watching all bug changes.
[drkonqi] [Bug 381644] Dr. Konqi Crashes During Crash Report
https://bugs.kde.org/show_bug.cgi?id=381644 Wolfgang Bauer changed: What|Removed |Added CC||frmdst...@protonmail.com --- Comment #25 from Wolfgang Bauer --- *** Bug 408993 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[drkonqi] [Bug 408993] drkonqi crash in backtraceline.h 59
https://bugs.kde.org/show_bug.cgi?id=408993 Wolfgang Bauer changed: What|Removed |Added CC||wba...@tmo.at Status|REPORTED|RESOLVED Resolution|--- |DUPLICATE --- Comment #1 from Wolfgang Bauer --- *** This bug has been marked as a duplicate of bug 381644 *** -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 408887] Crash when using shrink option on the deform brush engine
https://bugs.kde.org/show_bug.cgi?id=408887 --- Comment #6 from Ahab Greybeard --- Yes, that old move brush gives me a crash when edited to Shrink. I'm sure the problem will be solved eventually. Note: For attachments of anything except image files, text files and zip files, it seems that downloading is inconvenient so I'll try to remember to zip up any future .kpp etc files. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 409009] flatpak: file dialogs broken on KDE Plasma
https://bugs.kde.org/show_bug.cgi?id=409009 Boudewijn Rempt changed: What|Removed |Added CC||b...@valdyas.org --- Comment #1 from Boudewijn Rempt --- All that changed is that we updated to a new version of Qt; there is no file dialog code in Krita... -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 408918] Scroll speed wont scale with zoom
https://bugs.kde.org/show_bug.cgi?id=408918 --- Comment #6 from jey.and@gmail.com --- My scroll speed is slowish. You don't have to specifically zoom in for things to get bigger, theres auto fit and fit width as apposed to fit page view modes which basically zoom you in, but I see your point. On Fri, Jun 21, 2019 at 9:25 PM David Hurka wrote: > > https://bugs.kde.org/show_bug.cgi?id=408918 > > --- Comment #5 from David Hurka --- > So you want the scroll speed multiplied by the zoom factor? > > I don’t think that’s possible, because it would make scrolling virtually > uncontrollable at high zoom levels. I also don’t see a reason why scrolling > should be faster when zoomed in. > - Usually you zoom in to focus on a detail, and then you need predictable and > accurate (not fast) scrolling. > – Usually you zoom out to get an overview of the document. > > If you have to read text at a high zoom level and you need faster scrolling > than your input device (e. g. your mouse wheel) allows, you should probably > configure that instead. (With System Settings: Input Devices -> Mouse -> > Advanced -> Mouse wheel scrolls by: [3 lines]) > > Or do you mean something else? > > -- > You are receiving this mail because: > You reported the bug. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 321190] Please re-add mousebutton to close windows in Present Windows
https://bugs.kde.org/show_bug.cgi?id=321190 --- Comment #101 from Steffen Jost --- I can't believe that we get this truly great feature back soon! Yay! :) -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 408887] Crash when using shrink option on the deform brush engine
https://bugs.kde.org/show_bug.cgi?id=408887 --- Comment #5 from daefu...@gmail.com --- I'm not seeing a recent log in kritacrash.log I think I'm also using an old move brush. I'll attach it. Making a new brush doesn't give me any problems at all. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 408887] Crash when using shrink option on the deform brush engine
https://bugs.kde.org/show_bug.cgi?id=408887 --- Comment #4 from daefu...@gmail.com --- Created attachment 121064 --> https://bugs.kde.org/attachment.cgi?id=121064&action=edit Brush causing problems -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 409009] New: flatpak: file dialogs broken on KDE Plasma
https://bugs.kde.org/show_bug.cgi?id=409009 Bug ID: 409009 Summary: flatpak: file dialogs broken on KDE Plasma Product: krita Version: 4.2.1 Platform: Flatpak OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: General Assignee: krita-bugs-n...@kde.org Reporter: peter.eszl...@gmail.com Target Milestone: --- I already opened a bug for xdg-desktop-portal-kde, but maybe a workaround could be added until it is fixed: https://bugs.kde.org/show_bug.cgi?id=408341 Something changed between 4.1 and 4.2 with the file dialog handling. Under KDE Plasma open and closing a file dialog freezes the app. This doesn't happen under GNOME, because there the Qt dialogs are used, while under KDE Plasma the native dialogs are used (backed by xdg-desktop-portal-kde in this case). -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 409008] New: crash during deinstalltion from a second installesdlanguage ( polski )
https://bugs.kde.org/show_bug.cgi?id=409008 Bug ID: 409008 Summary: crash during deinstalltion from a second installesdlanguage ( polski ) Product: systemsettings Version: 5.16.1 Platform: Neon Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: ste...@gmail.com Target Milestone: --- Application: systemsettings5 (5.16.1) Qt Version: 5.12.3 Frameworks Version: 5.59.0 Operating System: Linux 5.1.12-050112-generic x86_64 Distribution: KDE neon User Edition 5.16 -- Information about the crash: - i select the second installed language ( polski ) the first installaed language is german The crash can be reproduced every time. -- Backtrace: Application: Systemeinstellungen (systemsettings5), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f5cf9b76680 (LWP 28309))] Thread 7 (Thread 0x7f5cba0ed700 (LWP 28317)): #0 0x7f5cee185379 in g_mutex_lock () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #1 0x7f5cee13ea33 in g_main_context_prepare () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f5cee13f3fb in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f5cee13f5dc in g_main_context_iteration () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7f5cf5a21dcb in QEventDispatcherGlib::processEvents (this=0x7f5cb4000b20, flags=...) at kernel/qeventdispatcher_glib.cpp:424 #5 0x7f5cf59c303a in QEventLoop::exec (this=this@entry=0x7f5cba0ecd40, flags=..., flags@entry=...) at kernel/qeventloop.cpp:225 #6 0x7f5cf57ea4ca in QThread::exec (this=this@entry=0x5572b5ee43a0) at thread/qthread.cpp:531 #7 0x7f5cf35a0115 in QQmlThreadPrivate::run (this=0x5572b5ee43a0) at qml/ftw/qqmlthread.cpp:148 #8 0x7f5cf57ebc72 in QThreadPrivate::start (arg=0x5572b5ee43a0) at thread/qthread_unix.cpp:361 #9 0x7f5cf04fd6db in start_thread (arg=0x7f5cba0ed700) at pthread_create.c:463 #10 0x7f5cf50eb88f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 6 (Thread 0x7f5cc0c17700 (LWP 28316)): #0 0x7f5cee13ea18 in g_main_context_prepare () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #1 0x7f5cee13f3fb in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f5cee13f5dc in g_main_context_iteration () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f5cf5a21dcb in QEventDispatcherGlib::processEvents (this=0x7f5cbc000b20, flags=...) at kernel/qeventdispatcher_glib.cpp:424 #4 0x7f5cf59c303a in QEventLoop::exec (this=this@entry=0x7f5cc0c16d40, flags=..., flags@entry=...) at kernel/qeventloop.cpp:225 #5 0x7f5cf57ea4ca in QThread::exec (this=this@entry=0x5572b3173d90) at thread/qthread.cpp:531 #6 0x7f5cf35a0115 in QQmlThreadPrivate::run (this=0x5572b3173d90) at qml/ftw/qqmlthread.cpp:148 #7 0x7f5cf57ebc72 in QThreadPrivate::start (arg=0x5572b3173d90) at thread/qthread_unix.cpp:361 #8 0x7f5cf04fd6db in start_thread (arg=0x7f5cc0c17700) at pthread_create.c:463 #9 0x7f5cf50eb88f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 5 (Thread 0x7f5cc958f700 (LWP 28314)): #0 0x7f5cf50da0b4 in __GI___libc_read (fd=13, buf=0x7f5cc958eb30, nbytes=16) at ../sysdeps/unix/sysv/linux/read.c:27 #1 0x7f5cee184000 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f5cee13efb7 in g_main_context_check () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f5cee13f470 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7f5cee13f5dc in g_main_context_iteration () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7f5cf5a21dcb in QEventDispatcherGlib::processEvents (this=0x7f5cc4000b20, flags=...) at kernel/qeventdispatcher_glib.cpp:424 #6 0x7f5cf59c303a in QEventLoop::exec (this=this@entry=0x7f5cc958ed40, flags=..., flags@entry=...) at kernel/qeventloop.cpp:225 #7 0x7f5cf57ea4ca in QThread::exec (this=this@entry=0x5572b2e0e550) at thread/qthread.cpp:531 #8 0x7f5cf35a0115 in QQmlThreadPrivate::run (this=0x5572b2e0e550) at qml/ftw/qqmlthread.cpp:148 #9 0x7f5cf57ebc72 in QThreadPrivate::start (arg=0x5572b2e0e550) at thread/qthread_unix.cpp:361 #10 0x7f5cf04fd6db in start_thread (arg=0x7f5cc958f700) at pthread_create.c:463 #11 0x7f5cf50eb88f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 4 (Thread 0x7f5cd5914700 (LWP 28312)): #0 0x7f5cf05039f3 in futex_wait_cancelable (private=, expected=0, futex_word=0x5572b2ae6958) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 __pthread_cond_wait_common (abstime=0x0, mutex=0x5572b2ae6908, cond=0x5572b2ae6930) at pthread_cond_wait.c:502 #2 __pthread_cond_wait (cond=0x5572b2ae6930, mutex=0x5572b2ae6908) at pthread_cond_wait.c:65
[kwin] [Bug 321190] Please re-add mousebutton to close windows in Present Windows
https://bugs.kde.org/show_bug.cgi?id=321190 --- Comment #100 from Michael Tunnell --- Yes! I have been waiting for this to happen for over 4 years so I am so excited to see it's finally happening! Thank you! When we eventually meet in person, fair warning . . . hug is coming -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 409007] New: Export global menu
https://bugs.kde.org/show_bug.cgi?id=409007 Bug ID: 409007 Summary: Export global menu Product: Spectacle Version: 19.04.2 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: General Assignee: m...@baloneygeek.com Reporter: tr...@yandex.com CC: k...@david-redondo.de Target Milestone: --- SUMMARY Not all users use the Window layout, some use the macOS/unity layout that need the global menu for apps. OBSERVED RESULT No global menu. EXPECTED RESULT A global menu. For example: File | Edit | Tool | Export | Help ... -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 409006] New: Update the screenshot after editing
https://bugs.kde.org/show_bug.cgi?id=409006 Bug ID: 409006 Summary: Update the screenshot after editing Product: Spectacle Version: 19.04.2 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: General Assignee: m...@baloneygeek.com Reporter: tr...@yandex.com CC: k...@david-redondo.de Target Milestone: --- SUMMARY The screenshot should be updated after editing. STEPS TO REPRODUCE 1. Take a screenshot (file1) 2. Export to Gimp, do some editing then save. (file2) 3. Export again e.g. upload to imgur... (file3) OBSERVED RESULT a. file3 = file1 b. the preview screenshot = file1 EXPECTED RESULT a. file3 = file2 b.the preview screenshot = file2 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 321190] Please re-add mousebutton to close windows in Present Windows
https://bugs.kde.org/show_bug.cgi?id=321190 Nate Graham changed: What|Removed |Added CC||n...@kde.org --- Comment #99 from Nate Graham --- You're welcome! :) -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kfilemetadata] [Bug 343273] Improve the info panel for photos
https://bugs.kde.org/show_bug.cgi?id=343273 --- Comment #14 from Alexander Stippich --- Git commit 0a042beb5568a073612c2752b4c4b64b675e2a81 by Alexander Stippich. Committed on 21/06/2019 at 17:28. Pushed by astippich into branch 'master'. Format photo exposure bias value Summary: Format the photo exposure bias value in EV units and in steps of thirds when applicable Reviewers: bruns, ngraham Reviewed By: bruns Subscribers: kde-frameworks-devel, #baloo Tags: #frameworks, #baloo Differential Revision: https://phabricator.kde.org/D21830 M +8-0autotests/propertyinfotest.cpp M +33 -0src/formatstrings.cpp M +2-0src/formatstrings_p.h M +1-1src/propertyinfo.cpp https://commits.kde.org/kfilemetadata/0a042beb5568a073612c2752b4c4b64b675e2a81 -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 408985] Power management fails to notify of low & critical battery, & fails to take critical action
https://bugs.kde.org/show_bug.cgi?id=408985 --- Comment #2 from 3ndymion <3ndym...@protonmail.com> --- Very cool. I will wait for it then. Thank you very much. : ) -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 409005] New: Dolphin crash where moving group files from remote device
https://bugs.kde.org/show_bug.cgi?id=409005 Bug ID: 409005 Summary: Dolphin crash where moving group files from remote device Product: dolphin Version: 18.08.0 Platform: Debian stable OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: sokol08.an@mail.ru CC: elvis.angelac...@kde.org Target Milestone: --- Application: dolphin (18.08.0) Qt Version: 5.11.3 Frameworks Version: 5.54.0 Operating System: Linux 4.19.0-5-amd64 x86_64 Distribution: Debian GNU/Linux 10 (buster) -- Information about the crash: - What I was doing when the application crashed: 1) Open my phone folder throught KDEConnect 2) Start moving files from phone to local folder 3) Lose connect to phone 3.1) Dolphin show Dialog window "File not found[retry,cancel ...] 4) Restore connect to phone 4.1) I check what connection restored open my phone folder and show image file 5) Click retry in Dolphin dialog window(stage 3) 6) Dolphin crash - Unusual behavior I noticed: When i continue moving file after lose and restore connection, Dolphin say what file already exist and sizes files equals but in destination folder file is broke. Something Dolphin show two dialog`s window. -- Backtrace: Application: Dolphin (dolphin), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7fb57f4cd840 (LWP 13529))] Thread 3 (Thread 0x7fb56cb5f700 (LWP 13533)): #0 0x7fb57fac2494 in read () from /lib/x86_64-linux-gnu/libc.so.6 #1 0x7fb57b86baa0 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7fb57b825c0f in g_main_context_check () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7fb57b8260e0 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7fb57b82625c in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7fb57db9387b in QEventDispatcherGlib::processEvents(QFlags) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7fb57db4127b in QEventLoop::exec(QFlags) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7fb57d990ec6 in QThread::exec() () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7fb57d99aaa7 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #9 0x7fb57c31ffa3 in start_thread () from /lib/x86_64-linux-gnu/libpthread.so.0 #10 0x7fb57fad14cf in clone () from /lib/x86_64-linux-gnu/libc.so.6 Thread 2 (Thread 0x7fb576427700 (LWP 13532)): #0 0x7fb57fac6819 in poll () from /lib/x86_64-linux-gnu/libc.so.6 #1 0x7fb57b826136 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7fb57b82625c in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7fb57db9387b in QEventDispatcherGlib::processEvents(QFlags) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7fb57db4127b in QEventLoop::exec(QFlags) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7fb57d990ec6 in QThread::exec() () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7fb57ddee545 in ?? () from /lib/x86_64-linux-gnu/libQt5DBus.so.5 #7 0x7fb57d99aaa7 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7fb57c31ffa3 in start_thread () from /lib/x86_64-linux-gnu/libpthread.so.0 #9 0x7fb57fad14cf in clone () from /lib/x86_64-linux-gnu/libc.so.6 Thread 1 (Thread 0x7fb57f4cd840 (LWP 13529)): [KCrash Handler] #6 0x7fb57eb236d4 in KJob::isAutoDelete() const () from /lib/x86_64-linux-gnu/libKF5CoreAddons.so.5 #7 0x7fb57eb2373b in KJob::finishJob(bool) () from /lib/x86_64-linux-gnu/libKF5CoreAddons.so.5 #8 0x7fb57f3a9a59 in KIO::FileCopyJob::slotResult(KJob*) () from /lib/x86_64-linux-gnu/libKF5KIOCore.so.5 #9 0x7fb57db6ba43 in QMetaObject::activate(QObject*, int, int, void**) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #10 0x7fb57eb22c6c in KJob::result(KJob*, KJob::QPrivateSignal) () from /lib/x86_64-linux-gnu/libKF5CoreAddons.so.5 #11 0x7fb57eb23733 in KJob::finishJob(bool) () from /lib/x86_64-linux-gnu/libKF5CoreAddons.so.5 #12 0x7fb57f3b6a60 in KIO::SimpleJob::slotFinished() () from /lib/x86_64-linux-gnu/libKF5KIOCore.so.5 #13 0x7fb57f3b4dbb in KIO::SimpleJob::slotError(int, QString const&) () from /lib/x86_64-linux-gnu/libKF5KIOCore.so.5 #14 0x7fb57db6ba43 in QMetaObject::activate(QObject*, int, int, void**) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #15 0x7fb57f385626 in KIO::SlaveInterface::error(int, QString const&) () from /lib/x86_64-linux-gnu/libKF5KIOCore.so.5 #16 0x7fb57f3881c2 in KIO::SlaveInterface::dispatch(int, QByteArray const&) () from /lib/x86_64-linux-gnu/libKF5KIOCore.so.5 #17 0x7fb57f385db8 in KIO::SlaveInterface::dispatch() () from /li
[plasmashell] [Bug 409004] New: Notifications spawn in centre of current screen and jump to the system tray area, leaving a box missing/corrupted
https://bugs.kde.org/show_bug.cgi?id=409004 Bug ID: 409004 Summary: Notifications spawn in centre of current screen and jump to the system tray area, leaving a box missing/corrupted Product: plasmashell Version: 5.16.1 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Notifications Assignee: k...@privat.broulik.de Reporter: cliv...@protonmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 When I get a notification the wee box spawns in the centre of my active screen (ie if I'm watching YouTube on that screen) it then moves down to the system tray area and I can see the notification and act on it as normal. However, for a couple of seconds there is a blank/corrupted box on the current screen which looks weird for a few seconds(especially in the middle of video playback). If I get a lot of notifications this becomes very annoying and can not watch a video in peace (I get a lot via KDE Connect). STEPS TO REPRODUCE 1. Get a notification 2. See corruption in the centre of the screen I am currently working on OBSERVED RESULT Corruption at the centre of active screen EXPECTED RESULT Notification SOFTWARE/OS VERSIONS KDE Plasma Version: 5.16.1 KDE Frameworks Version: 5.59.0 Qt Version: 5.12.3 -- You are receiving this mail because: You are watching all bug changes.
[kolourpaint] [Bug 409003] New: Make anti-aliasing optional
https://bugs.kde.org/show_bug.cgi?id=409003 Bug ID: 409003 Summary: Make anti-aliasing optional Product: kolourpaint Version: 19.04 Platform: unspecified OS: All Status: REPORTED Severity: wishlist Priority: NOR Component: general Assignee: kolourpaint-supp...@lists.sourceforge.net Reporter: benni.b...@gmail.com Target Milestone: --- Created attachment 121063 --> https://bugs.kde.org/attachment.cgi?id=121063&action=edit Example with the current line tool result and what I explect from it. I use Kolourpaint mainly for pixel accurate tasks. Tools like drawing a line horizontally or vertically with one pixel wide are currently not possible because anti-aliasing blurs the line. Please introduce a switch for anti-aliasing, so that pixel-accurate drawing works again. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 408953] Can't pin GIMP launcher (flatpak)
https://bugs.kde.org/show_bug.cgi?id=408953 --- Comment #21 from marinodiego.96+...@gmail.com --- Flatpak desktop filename is org.gimp.GIMP, but it contains these lines at the end of it: X-Flatpak-RenamedFrom=gimp.desktop; X-Flatpak-Tags=stable; X-Flatpak=org.gimp.GIMP -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 409002] New: Can't drag and drop a file when there is only a minimized file opened
https://bugs.kde.org/show_bug.cgi?id=409002 Bug ID: 409002 Summary: Can't drag and drop a file when there is only a minimized file opened Product: krita Version: 4.2.1 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Usability Assignee: krita-bugs-n...@kde.org Reporter: trueki...@gmail.com Target Milestone: --- SUMMARY Drag and dropping a file into empty space in krita while there is another canvas window minimized will not result in opening the new file. STEPS TO REPRODUCE 1. Open a file in krita. 2. Minimize the canvas. 3. Drag and drop another file into krita window. OBSERVED RESULT Nothing happens. EXPECTED RESULT Dropped file opens. 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.
[kwin] [Bug 372576] Present Windows lags when closing window
https://bugs.kde.org/show_bug.cgi?id=372576 Michał Dybczak changed: What|Removed |Added CC||michal.dybc...@gmail.com --- Comment #33 from Michał Dybczak --- I also notice this bug on Intel X session from a long time. On Wayland or Nvidia all works fluently and Overview is pleasant to use, but not on Intel Xorg (which I use most of the time). Since Xorg will be used for many, many years (wayland session is a disaster in the latest 5.16 update, not even possible to test anymore because of some pretty heavy memory leak) and Intel is still widely used, this is a very annoying bug. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 408953] Can't pin GIMP launcher (flatpak)
https://bugs.kde.org/show_bug.cgi?id=408953 --- Comment #20 from Eike Hein --- The Flatpak maybe has a different .desktop file name than the one you attached earlier? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 405454] Desktop names don't appear in the pager applet, only "..."
https://bugs.kde.org/show_bug.cgi?id=405454 --- Comment #9 from Eike Hein --- I'd much prefer an explicit user decision over automagic as well -- except we don't have an UX to resize panel widgets at the moment. (I'm not sure it's been said, but currently the pager representation just follows the screen aspect ratio.) -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 408131] build failure on Gentoo with new proflile without lib -> lib64 symlink
https://bugs.kde.org/show_bug.cgi?id=408131 Jack changed: What|Removed |Added Resolution|--- |WORKSFORME Status|REPORTED|RESOLVED --- Comment #2 from Jack --- Fortunately, it seems that recompiling libalkimia fixed the initial error, and now recompiling again fixes the new issue, probably because it is actually libalkimia calling for libmpir. I'm going to close this as WORKSFORME, and will only reopen if anything new does point back to ninja or cmake. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 321190] Please re-add mousebutton to close windows in Present Windows
https://bugs.kde.org/show_bug.cgi?id=321190 --- Comment #98 from Tomasz Kołosowski --- 6 years later, we got it back. You're my hero man, I can't thank you enough. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 409001] New: when opened message (incapsulated by outlook) kmail crashes
https://bugs.kde.org/show_bug.cgi?id=409001 Bug ID: 409001 Summary: when opened message (incapsulated by outlook) kmail crashes Product: kmail2 Version: 5.10.3 Platform: openSUSE RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: diego.ercol...@gmail.com Target Milestone: --- Application: kmail (5.10.3) Qt Version: 5.9.7 Frameworks Version: 5.55.0 Operating System: Linux 4.12.14-lp151.28.7-default x86_64 Distribution: "openSUSE Leap 15.1" -- Information about the crash: - What I was doing when the application crashed: open a message that is a forward message encapsulated by outlook The crash can be reproduced every time. -- Backtrace: Application: KMail (kmail), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f97d389d980 (LWP 20428))] Thread 24 (Thread 0x7f9707211700 (LWP 20482)): #0 0x7f97d0923c98 in read () from /lib64/libc.so.6 #1 0x7f97c402cca0 in ?? () from /usr/lib64/libglib-2.0.so.0 #2 0x7f97c3fe7cb8 in g_main_context_check () from /usr/lib64/libglib-2.0.so.0 #3 0x7f97c3fe8150 in ?? () from /usr/lib64/libglib-2.0.so.0 #4 0x7f97c3fe82bc in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #5 0x7f97d126d96b in QEventDispatcherGlib::processEvents (this=0x7f970b10, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #6 0x7f97d121290a in QEventLoop::exec (this=this@entry=0x7f9707210c30, flags=..., flags@entry=...) at kernel/qeventloop.cpp:212 #7 0x7f97d1030daa in QThread::exec (this=) at thread/qthread.cpp:515 #8 0x7f97d1035ced in QThreadPrivate::start (arg=0x7f97802a3a60) at thread/qthread_unix.cpp:368 #9 0x7f97c5ea1569 in start_thread () from /lib64/libpthread.so.0 #10 0x7f97d09329ef in clone () from /lib64/libc.so.6 Thread 23 (Thread 0x7f972f7fe700 (LWP 20479)): #0 0x7f97d0923c98 in read () from /lib64/libc.so.6 #1 0x7f97abe64701 in pa_read () from /usr/lib64/pulseaudio/libpulsecommon-11.1.so #2 0x7f97b3b51e0e in pa_mainloop_prepare () from /usr/lib64/libpulse.so.0 #3 0x7f97b3b52880 in pa_mainloop_iterate () from /usr/lib64/libpulse.so.0 #4 0x7f97b3b52940 in pa_mainloop_run () from /usr/lib64/libpulse.so.0 #5 0x7f97b3b607a9 in ?? () from /usr/lib64/libpulse.so.0 #6 0x7f97abe93428 in ?? () from /usr/lib64/pulseaudio/libpulsecommon-11.1.so #7 0x7f97c5ea1569 in start_thread () from /lib64/libpthread.so.0 #8 0x7f97d09329ef in clone () from /lib64/libc.so.6 Thread 22 (Thread 0x7f972700 (LWP 20478)): #0 0x7f97c5ea7bdb in pthread_cond_timedwait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7f97ba4dc962 in ?? () from /usr/lib64/libQt5WebEngineCore.so.5 #2 0x7f97ba4a361e in ?? () from /usr/lib64/libQt5WebEngineCore.so.5 #3 0x7f97ba47e54b in ?? () from /usr/lib64/libQt5WebEngineCore.so.5 #4 0x7f97ba47adc8 in ?? () from /usr/lib64/libQt5WebEngineCore.so.5 #5 0x7f97ba49785b in ?? () from /usr/lib64/libQt5WebEngineCore.so.5 #6 0x7f97ba4af486 in ?? () from /usr/lib64/libQt5WebEngineCore.so.5 #7 0x7f97ba4ab55b in ?? () from /usr/lib64/libQt5WebEngineCore.so.5 #8 0x7f97c5ea1569 in start_thread () from /lib64/libpthread.so.0 #9 0x7f97d09329ef in clone () from /lib64/libc.so.6 Thread 21 (Thread 0x7f9744ff9700 (LWP 20477)): #0 0x7f97c5ea78ad in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7f97bad226f0 in ?? () from /usr/lib64/libQt5WebEngineCore.so.5 #2 0x7f97ba4aeec1 in ?? () from /usr/lib64/libQt5WebEngineCore.so.5 #3 0x7f97ba4ab55b in ?? () from /usr/lib64/libQt5WebEngineCore.so.5 #4 0x7f97c5ea1569 in start_thread () from /lib64/libpthread.so.0 #5 0x7f97d09329ef in clone () from /lib64/libc.so.6 Thread 20 (Thread 0x7f97457fa700 (LWP 20476)): #0 0x7f97c5ea78ad in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7f97ba4adc45 in ?? () from /usr/lib64/libQt5WebEngineCore.so.5 #2 0x7f97ba4ae127 in ?? () from /usr/lib64/libQt5WebEngineCore.so.5 #3 0x7f97ba4aeec1 in ?? () from /usr/lib64/libQt5WebEngineCore.so.5 #4 0x7f97ba4ab55b in ?? () from /usr/lib64/libQt5WebEngineCore.so.5 #5 0x7f97c5ea1569 in start_thread () from /lib64/libpthread.so.0 #6 0x7f97d09329ef in clone () from /lib64/libc.so.6 Thread 19 (Thread 0x7f9745ffb700 (LWP 20475)): #0 0x7f97c5ea78ad in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7f97ba4a3699 in ?? () from /usr/lib64/libQt5WebEngineCore.so.5 #2 0x7f97ba4a36c7 in ?? () from /usr/lib64/libQt5WebEngineCore.so.5 #3 0x7f97ba47e4fb in ?? () from /usr/lib64/libQt5WebEngineCore.so.5 #4 0x7f97ba47adc8 in ?? () from /usr/lib64/libQt5WebEngineCore.so.5 #5 0x7f9
[kwin] [Bug 321190] Please re-add mousebutton to close windows in Present Windows
https://bugs.kde.org/show_bug.cgi?id=321190
Nate Graham changed:
What|Removed |Added
Version Fixed In||5.17.0
Resolution|INTENTIONAL |FIXED
Latest Commit||https://commits.kde.org/kwi
||n/4dd4ca8f1c44226e0b2fc5e32
||ca911cc06402480
--- Comment #97 from Nate Graham ---
Git commit 4dd4ca8f1c44226e0b2fc5e32ca911cc06402480 by Nate Graham.
Committed on 21/06/2019 at 16:25.
Pushed by ngraham into branch 'master'.
[effects/presentwindows] Allow closing windows on middle-click
Summary:
Plasma's Task manager exposes an optional feature whereby the user
can middle-click on a window to close it, but the Present Windows effect
does not do the same.
The presence of a close button you can left-click does not replace the
desirable
feature to be able to middle-click on a window to close it, because then the
whole window becomes a click target, so it can be much much faster than
having to aim for the little close button. Also it's off by default, so a user
who goes out of their way to turn it on is signaling that they want to accept
the
risk of accidentally closing a window by accident.
Finally, the feature is not allowed for left-click, so people can never
accidentally
wreck Present Windows for themselves by assigning it to left-click by accident
and then mistakenly closing their windows.
This reverts commit 55585514f926d1251148e876bfe9ce3504432997.
FIXED-IN: 5.17.0
Test Plan:
Set "Close window" in the Present windows effect, trigger effect, and
middle-click on window
{F6815303}
Reviewers: #kwin, davidedmundson, broulik, zzag, #plasma, hein, mart
Reviewed By: #kwin, #plasma, mart
Subscribers: mart, abetts, apol, zzag, luebking, kossebau, graesslin, kwin
Tags: #kwin
Differential Revision: https://phabricator.kde.org/D21083
M +5-0effects/presentwindows/presentwindows.cpp
M +2-1effects/presentwindows/presentwindows.h
M +10 -0effects/presentwindows/presentwindows_config.ui
https://commits.kde.org/kwin/4dd4ca8f1c44226e0b2fc5e32ca911cc06402480
--
You are receiving this mail because:
You are watching all bug changes.
[kmymoney] [Bug 408131] build failure on Gentoo with new proflile without lib -> lib64 symlink
https://bugs.kde.org/show_bug.cgi?id=408131 --- Comment #1 from Jack --- The above error with libgmp.so seems to be resolved by rebuilding libalkimia, but I now get ninja: error: '/usr/lib/libmpir.so', needed by 'lib/libkmm_mymoney.so.5.0.4', missing and no known rule to make it. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 408103] Krita messages to the user should use the .kra file name and not the document Title
https://bugs.kde.org/show_bug.cgi?id=408103 Ahab Greybeard changed: What|Removed |Added Status|CONFIRMED |RESOLVED Resolution|--- |INTENTIONAL --- Comment #12 from Ahab Greybeard --- As David says, there is a workaround and as Boud implies, changing anything could cause problems. Setting to Resolved Intentional. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 408953] Can't pin GIMP launcher (flatpak)
https://bugs.kde.org/show_bug.cgi?id=408953 --- Comment #19 from marinodiego.96+...@gmail.com --- As a workaround, I tried using the repo gimp.desktop file editing the Exec line with Exec=/usr/bin/flatpak run --branch=stable --arch=x86_64 --command=gimp-2.10 --file-forwarding org.gimp.GIMP @@u %U @@ taken from its flatpak org.gimp.GIMP.desktop file, and it works fine now. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 409000] New: Launcher menu should align with panel extents
https://bugs.kde.org/show_bug.cgi?id=409000 Bug ID: 409000 Summary: Launcher menu should align with panel extents Product: plasmashell Version: 5.16.1 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Application Launcher (Kickoff) Assignee: k...@davidedmundson.co.uk Reporter: karthik.periaga...@gmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 Created attachment 121062 --> https://bugs.kde.org/attachment.cgi?id=121062&action=edit screenshot showing the problem SUMMARY In previous releases, when the panel width is less than the width of the screen, the application launcher menu would align itself so that moving vertically after clicking the launcher in the panel would end up in the left-most entry, Favorites. However, since 5.16, the behavior has changed and the launcher menu is centered with the launcher in the panel. This makes it difficult to reach the Favorites as moving the mouse vertically down switches the page to Applications (by default, these can be reordered). STEPS TO REPRODUCE 1. Reduce panel width to not span the entire desktop 2. Click on the application launcher 3. Move to nearest point in the menu. OBSERVED RESULT The nearest point in the menu causes the menu to change page to the item closest to the center, not the item on the left most end, which is in fact what is shown by default (implying a default selection). EXPECTED RESULT The menu should be aligned with the panel so that the left most page gets selected if the mouse moves from the launcher button to the launcher menu. This may need to be different for RTL languages, I imagine. Generally, aligning the menu popup to the extent of the panel should work for both cases. ADDITIONAL INFORMATION See attached screenshot. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 405454] Desktop names don't appear in the pager applet, only "..."
https://bugs.kde.org/show_bug.cgi?id=405454 --- Comment #8 from David Faure --- My wife also complains that the desktops should be wider just so that the clicking area is big enough. Try a "2 columns 3 rows" layout with a normal-size panel, the clicking area is minuscule. Why can't the user choose the horizontal size of the pager, rather than relying on some (currently missing) automagic? -- You are receiving this mail because: You are watching all bug changes.
