[krita] [Bug 418608] New: Cursor position and drawing position are not the same
https://bugs.kde.org/show_bug.cgi?id=418608 Bug ID: 418608 Summary: Cursor position and drawing position are not the same Product: krita Version: 4.2.8 Platform: Other OS: MS Windows Status: REPORTED Severity: normal Priority: NOR Component: tablet support Assignee: krita-bugs-n...@kde.org Reporter: garyno...@gmail.com Target Milestone: --- Created attachment 126664 --> https://bugs.kde.org/attachment.cgi?id=126664&action=edit krita bug info SUMMARY When using Krita 4.2.8 on my laptop with a Wacom tablet, when the cursor moves off to the left of the canvas towards the toolbar then back, the position of the cursor on the page is accurate to the image, but the drawn element (box/line/brush etc.) is offset to the right and down to approximately a third of the screen. When the cursor is moved over to the right hand dockers, the cursor and pen rest, until they move back over the left. STEPS TO REPRODUCE 1. Move the cursor to the left of the screen. The cursor offsets and draws on a different point of the canvas. 2. 3. OBSERVED RESULT Cursor moves to a different position of the canvas to the pointer position EXPECTED RESULT The cursor to be in the same position as the wacom stylus all the timer SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 418607] New: Can't open a GIMP file
https://bugs.kde.org/show_bug.cgi?id=418607 Bug ID: 418607 Summary: Can't open a GIMP file Product: krita Version: 4.2.8 Platform: MS Windows OS: MS Windows Status: REPORTED Severity: normal Priority: NOR Component: Usability Assignee: krita-bugs-n...@kde.org Reporter: yasharya2...@gmail.com Target Milestone: --- SUMMARY I tried to open an XCF file created in GIMP 2.10.18. OBSERVED RESULT It said Krita can't open files created in GIMP 2.9 or newer. EXPECTED RESULT Krita should open it. SOFTWARE/OS VERSIONS Windows: 7 Home Premium macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 418606] New: Local selection mask is not marked by the selection tool
https://bugs.kde.org/show_bug.cgi?id=418606 Bug ID: 418606 Summary: Local selection mask is not marked by the selection tool Product: krita Version: 4.2.8 Platform: MS Windows OS: MS Windows Status: REPORTED Severity: normal Priority: NOR Component: Layer Stack Assignee: krita-bugs-n...@kde.org Reporter: kustov1...@gmail.com Target Milestone: --- SUMMARY When I create it from the paint layer through converting to the local selection mask it is not marked by the selection tool, but there is it here and I can draw in the mask. But I can not see the edge of the mask. STEPS TO REPRODUCE 1. Create a new document. 2. Create two layers (Layer # 1, Layer # 2) 3. Draw white square at Layer # 2. 4. Convert Layer # 2 to Selection Mask and move it to Layer # 1. 5. Switch to Layer # 1. OBSERVED RESULT The local selection mask (Layer # 2) is not marked by the selection tool at Layer # 1. EXPECTED RESULT The local selection mask (Layer # 2) is marked by the selection tool at Layer # 1. Must be select square which I have drawn at Layer # 2. SOFTWARE/OS VERSIONS Windows: Windows 10 ADDITIONAL INFORMATION If I draw at Layer # 1 there is square here but I can not see edge 'cause Selection Tool is not visible. When I create a local selection mask from the selection tool (not paint layer) it's all right. -- You are receiving this mail because: You are watching all bug changes.
[elisa] [Bug 418605] New: Improve handling of network-based music collection
https://bugs.kde.org/show_bug.cgi?id=418605 Bug ID: 418605 Summary: Improve handling of network-based music collection Product: elisa Version: 19.12.3 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: matthieu_gall...@yahoo.fr Reporter: openmind...@gmail.com Target Milestone: --- SUMMARY This is more of a feature request, not a bugreport actually. However, as the situation impacts user's experience, this goes here as a "bug report". All my music resides on a network disk, available through dynamically mounted NFS share. Every time I launch Elisa it starts "importing new tracks" to the collection, while there's been no changes to files on the server. Is it possible to make Elisa stop auto-renewing collection on each launch and rely on database stored locally? STEPS TO REPRODUCE 1. Add a network-based source of music to Elisa's settings 2. Wait for importing to be finished 3. Close Elisa, launch it again OBSERVED RESULT Importing "starts" again. EXPECTED RESULT Local database providing music collection info, renewal only through explicit clicking on respective menu item / button. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: 5.18.2 KDE Frameworks Version: 5.67.0 Qt Version: 5.14.1 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 417256] baloo crash
https://bugs.kde.org/show_bug.cgi?id=417256 Bug Janitor Service changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|BACKTRACE |WORKSFORME --- Comment #3 from Bug Janitor Service --- This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 418532] Krita will crash Whilst trying to transform a selection
https://bugs.kde.org/show_bug.cgi?id=418532 Bug Janitor Service changed: What|Removed |Added Resolution|WAITINGFORINFO |--- Status|NEEDSINFO |REPORTED --- Comment #5 from Bug Janitor Service --- Thanks for your comment! Automatically switching the status of this bug to REPORTED so that the KDE team knows that the bug is ready to get confirmed. In the future you may also do this yourself when providing needed information. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 416875] Clicking on the "Update" button on the updates available notification from Discover doesn't open Discover
https://bugs.kde.org/show_bug.cgi?id=416875 --- Comment #8 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.
[kio-extras] [Bug 391153] Creating files takes a lot of time and CPU (spawns many processes)
https://bugs.kde.org/show_bug.cgi?id=391153 Bug Janitor Service changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |WORKSFORME --- Comment #11 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-kirigami] [Bug 417966] Kirigami.Icon causes segmentation fault in a KCM
https://bugs.kde.org/show_bug.cgi?id=417966 --- 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.
[kwin] [Bug 388630] Desktop context menu sometimes exhibits graphical corruption
https://bugs.kde.org/show_bug.cgi?id=388630 Bug Janitor Service changed: What|Removed |Added Resolution|WAITINGFORINFO |WORKSFORME Status|NEEDSINFO |RESOLVED --- Comment #13 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.
[kio-extras] [Bug 413850] rete non funziona
https://bugs.kde.org/show_bug.cgi?id=413850 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.
[kwin] [Bug 407129] Mouse cursor jumps for about one frame when transitioning to different icon
https://bugs.kde.org/show_bug.cgi?id=407129 Bug Janitor Service changed: What|Removed |Added Resolution|WAITINGFORINFO |WORKSFORME Status|NEEDSINFO |RESOLVED --- Comment #8 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.
[konsole] [Bug 196998] Konsole should reflow the text when resizing
https://bugs.kde.org/show_bug.cgi?id=196998 hoperidesal...@protonmail.ch changed: What|Removed |Added CC||hoperidesalone@protonmail.c ||h -- You are receiving this mail because: You are watching all bug changes.
[KAccounts] [Bug 418567] Google Drive Accounts have Google[number] instead of my Google ID
https://bugs.kde.org/show_bug.cgi?id=418567 --- Comment #2 from Marco Parillo --- Confirmed: https://forum.manjaro.org/t/kde-online-accounts/128127/11 -- You are receiving this mail because: You are watching all bug changes.
[KAccounts] [Bug 418567] Google Drive Accounts have Google[number] instead of my Google ID
https://bugs.kde.org/show_bug.cgi?id=418567 Marco Parillo changed: What|Removed |Added Ever confirmed|0 |1 Status|REPORTED|CONFIRMED -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 372305] Crash in ContrastEffect::uploadRegion
https://bugs.kde.org/show_bug.cgi?id=372305 --- Comment #39 from Jiri Palecek --- Please have a look at https://phabricator.kde.org/D27924. -- You are receiving this mail because: You are watching all bug changes.
[elisa] [Bug 418433] It doesn't allow the monitor to be turned off
https://bugs.kde.org/show_bug.cgi?id=418433 Nate Graham changed: What|Removed |Added CC||k...@privat.broulik.de, ||n...@kde.org Ever confirmed|0 |1 Status|REPORTED|CONFIRMED --- Comment #1 from Nate Graham --- Yeah, it's possible to inhibit system sleep but not display sleep/dimming. Elisa should do that. -- You are receiving this mail because: You are watching all bug changes.
[elisa] [Bug 418578] Improve UX for trying to remove the last path in Elisa settings
https://bugs.kde.org/show_bug.cgi?id=418578 Nate Graham changed: What|Removed |Added Summary|Impossible to remove the|Improve UX for trying to |last path in Elisa settings |remove the last path in ||Elisa settings Severity|normal |minor CC||n...@kde.org Status|REPORTED|CONFIRMED Ever confirmed|0 |1 --- Comment #1 from Nate Graham --- There always needs to be at least one path, or else Elisa doesn't know where to find your music. The UX for this could be improved a bit though. -- You are receiving this mail because: You are watching all bug changes.
[elisa] [Bug 394333] Better shuffle
https://bugs.kde.org/show_bug.cgi?id=394333 Nate Graham changed: What|Removed |Added CC||n...@kde.org Version Fixed In||20.04.0 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 418532] Krita will crash Whilst trying to transform a selection
https://bugs.kde.org/show_bug.cgi?id=418532 --- Comment #4 from jetg...@gmail.com --- (In reply to Boudewijn Rempt from comment #3) > No, that page isn't relevant :-). You should be able to do "sudo apt install > krita-dbgsym" and that should install the debug symbols. Then start krita > and reproduce the crash; the plasma crash dialog should popup and show a > backtrace. This is the "backtrace" i got, it said three stars for usefulness icase that helps. Application: Krita (krita), signal: Aborted Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7fee5ef7a800 (LWP 5753))] Thread 9 (Thread 0x7fedff7fe700 (LWP 5787)): [KCrash Handler] #6 __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:51 #7 0x7fee59bfd801 in __GI_abort () at abort.c:79 #8 0x7fee59bed39a in __assert_fail_base (fmt=0x7fee59d747d8 "%s%s%s:%u: %s%sAssertion `%s' failed.\n%n", assertion=assertion@entry=0x7fee213e48f0 "this->is_initialized()", file=file@entry=0x7fee213e4760 "/usr/include/boost/optional/optional.hpp", line=line@entry=1107, function=function@entry=0x7fee213e49a0 ::get()::__PRETTY_FUNCTION__> "boost::optional::reference_type boost::optional::get() [with T = ToolTransformArgs; boost::optional::reference_type = ToolTransformArgs&]") at assert.c:92 #9 0x7fee59bed412 in __GI___assert_fail (assertion=assertion@entry=0x7fee213e48f0 "this->is_initialized()", file=file@entry=0x7fee213e4760 "/usr/include/boost/optional/optional.hpp", line=line@entry=1107, function=function@entry=0x7fee213e49a0 ::get()::__PRETTY_FUNCTION__> "boost::optional::reference_type boost::optional::get() [with T = ToolTransformArgs; boost::optional::reference_type = ToolTransformArgs&]") at assert.c:101 #10 0x7fee21386a01 in boost::optional::get (this=) at /usr/include/boost/optional/optional.hpp:1107 #11 boost::optional::operator*() & (this=) at /usr/include/boost/optional/optional.hpp:1124 #12 TransformStrokeStrategy::finishStrokeCallback (this=) at ./plugins/tools/tool_transform2/strokes/transform_stroke_strategy.cpp:704 #13 0x7fee213d2ecc in TransformStrokeStrategy::cancelStrokeCallback (this=0x55cc3f887000) at /usr/include/boost/optional/optional.hpp:697 #14 0x7fee5c96e849 in non-virtual thunk to KisUpdateJobItem::run() () from /usr/lib/x86_64-linux-gnu/libkritaimage.so.18 #15 0x7fee5a604f42 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #16 0x7fee5a6017ec in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #17 0x7fee539696db in start_thread (arg=0x7fedff7fe700) at pthread_create.c:463 #18 0x7fee59cde88f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 8 (Thread 0x7fee05f08700 (LWP 5767)): #0 0x7fee59ccd0b4 in __GI___libc_read (fd=23, buf=0x7fee05f07b20, nbytes=16) at ../sysdeps/unix/sysv/linux/read.c:27 #1 0x7fee520b12d0 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7fee5206c0b7 in g_main_context_check () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7fee5206c570 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7fee5206c6dc in g_main_context_iteration () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7fee5a8500db in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7fee5a7ef63a in QEventLoop::exec(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7fee5a600317 in QThread::exec() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7fee3d020a86 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5 #9 0x7fee5a6017ec in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #10 0x7fee539696db in start_thread (arg=0x7fee05f08700) at pthread_create.c:463 #11 0x7fee59cde88f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 7 (Thread 0x7fee16c9b700 (LWP 5766)): #0 0x7fee5a601d6c in QMutex::lock() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #1 0x7fee5a84ffdc in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #2 0x7fee5206bb28 in g_main_context_prepare () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7fee5206c4fb in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7fee5206c6dc in g_main_context_iteration () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7fee5a8500db in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7fee5a7ef63a in QEventLoop::exec(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7fee5a600317 in QThread::exec() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7fee3cb8b605 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5 #9 0x7fee5a6017ec in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #10 0x7fee539696db in start_thread (arg=0x7fee16c9b700) at pthread_create.c:463 #11 0x7fee59cde88f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 6
[systemsettings] [Bug 418604] If the currently applied Colour Scheme is not found, Apply is never enabled when selecting other colour schemes
https://bugs.kde.org/show_bug.cgi?id=418604 --- Comment #1 from The Feren OS Dev --- Extra additional information: Double-clicking colour schemes to apply them still works. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 418604] New: If the currently applied Colour Scheme is not found, Apply is never enabled when selecting other colour schemes
https://bugs.kde.org/show_bug.cgi?id=418604 Bug ID: 418604 Summary: If the currently applied Colour Scheme is not found, Apply is never enabled when selecting other colour schemes Product: systemsettings Version: 5.17.2 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: kcm_colors Assignee: plasma-b...@kde.org Reporter: ferenos...@outlook.com CC: jpwhit...@kde.org, mwoehlke.fl...@gmail.com Target Milestone: --- SUMMARY If the currently applied colour scheme is not found, resulting in a warning appearing at the top of the module that it picked the default colour scheme automatically, the 'Apply' button will never be enabled when picking other colour schemes which means no other colour schemes can be applied. STEPS TO REPRODUCE 1. Manually set the colour scheme value to an non-existent colour scheme name, or apply a custom colour scheme but then remove it after that 2. Open the Colours KCM once more 3. Select a different colour scheme OBSERVED RESULT The KCM never thinks you need to apply unsaved changes, meaning you can't apply any other colour scheme via the KCM. EXPECTED RESULT You can apply other colour schemes normally via the KCM. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: KDE neon 5.18.2 (available in About System) KDE Plasma Version: 5.18.2 KDE Frameworks Version: 5.67.0 Qt Version: 5.14.1 ADDITIONAL INFORMATION This is basically like the Fonts KCM issue from 5.18.0 except it's way less widespread since it only happens if the current colour scheme can't be found. -- You are receiving this mail because: You are watching all bug changes.
[ksmserver] [Bug 418603] New: If unattended-upgrades, or another daemon, currently has a shutdown lock the session gets stuck in a black void when 'shutting down'
https://bugs.kde.org/show_bug.cgi?id=418603 Bug ID: 418603 Summary: If unattended-upgrades, or another daemon, currently has a shutdown lock the session gets stuck in a black void when 'shutting down' Product: ksmserver Version: 5.18.1 Platform: Neon Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: ferenos...@outlook.com CC: plasma-b...@kde.org Target Milestone: --- SUMMARY When unattended-upgrades is running a scheduled update for your system, which results in a shutdown lock, or a different background service has a shutdown lock in place, when the user tries to shut down from the Plasma Desktop the session reaches the point where it should end (the black screen) but the session never ends automatically, resulting in the user becoming stuck in that black void indefinitely until they go into TTY or force a power off by other means. STEPS TO REPRODUCE 1. Enable unattended-upgrades, have some updates available and turn on the computer on a day that unattended-upgrades is scheduled to run on 2. Log in, and then try shutting down from the desktop OBSERVED RESULT The desktop session never ends, after getting to the point where it's ready to immediately end the desktop session, leaving users with just a black screen and their cursor left from what is left of that desktop session. EXPECTED RESULT The session will at least end, and/or the desktop will stay running until the shutdown lock is no longer in effect in which case it should THEN start the part of the log out process that quits plasmashell, etc. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: KDE neon 5.18.2 (available in About System) KDE Plasma Version: 5.18.2 KDE Frameworks Version: 5.67.0 Qt Version: 5.14.1 ADDITIONAL INFORMATION If I recall correctly, GNOME doesn't have this issue but it does require authentication to shutdown or restart when a shutdown lock is in effect. -- You are receiving this mail because: You are watching all bug changes.
[yakuake] [Bug 312152] On doing press-and-hold F12 (yakuake open/retract shortcut) for 1-2 secs, yakuake doesn't open anymore.
https://bugs.kde.org/show_bug.cgi?id=312152 Ryan McCoskrie changed: What|Removed |Added Status|CONFIRMED |NEEDSINFO CC||w...@ryanmccoskrie.me Resolution|--- |WORKSFORME --- Comment #4 from Ryan McCoskrie --- Just tried this ~7 years later, doesn't happen on Plasma Neon. Can anyone reproduce this bug in 2020? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 418602] New: plasmashell aborted when logging in to Plasma on Wayland with the message "The Wayland connection experienced a fatal error: Protocol error"
https://bugs.kde.org/show_bug.cgi?id=418602 Bug ID: 418602 Summary: plasmashell aborted when logging in to Plasma on Wayland with the message "The Wayland connection experienced a fatal error: Protocol error" Product: plasmashell Version: 5.18.1 Platform: Fedora RPMs 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 SUMMARY I've seen plasmashell abort when logging into Plasma on Wayland in a Fedora 32 KDE Plasma spin installation. The plasmashell aborts have occurred about 12 times from Plasma 5.17.4 - 5.18.2. The screen was black except for the cursor which moved around normally. plasmashell didn't restart automatically. These plasmashell crashes have usually happened after a Plasma on Wayland session had crashed and sddm reappeared. The following plasmashell abort was with Plasma 5.18.2, KF 5.67.0, Qt 5.13.2 after a kwin_wayland segmentation fault of the type I reported at https://bugs.kde.org/show_bug.cgi?id=416974 Core was generated by `/usr/bin/plasmashell'. Program terminated with signal SIGABRT, Aborted. #0 __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50 50return ret; [Current thread is 1 (Thread 0x7f85a1aac580 (LWP 3242))] (gdb) thread apply all bt Thread 3 (Thread 0x7f858d69c700 (LWP 3636)): #0 0x7f859f9639cf in __GI___poll (fds=0x7f85800029e0, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7f859e57fa8d in g_main_context_poll (priority=, n_fds=1, fds=0x7f85800029e0, timeout=, context=0x7f858c30) at ../glib/gmain.c:4346 #2 g_main_context_iterate (context=context@entry=0x7f858c30, block=block@entry=1, dispatch=dispatch@entry=1, self=) at ../glib/gmain.c:4042 #3 0x7f859e57fbc3 in g_main_context_iteration (context=0x7f858c30, may_block=may_block@entry=1) at ../glib/gmain.c:4108 #4 0x7f859fec1b75 in QEventDispatcherGlib::processEvents (this=0x7f858b60, flags=...) at kernel/qeventdispatcher_glib.cpp:423 #5 0x7f859fe751db in QEventLoop::exec (this=this@entry=0x7f858d69bd80, flags=..., flags@entry=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:140 #6 0x7f859fcea6e7 in QThread::exec (this=this@entry=0x55cee4c18fc0) at ../../include/QtCore/../../src/corelib/global/qflags.h:120 #7 0x7f85a1442d89 in QQmlThreadPrivate::run (this=0x55cee4c18fc0) at qml/ftw/qqmlthread.cpp:152 #8 0x7f859fceb9b6 in QThreadPrivate::start(void*) () at thread/qthread_unix.cpp:360 #9 0x7f859f206432 in start_thread (arg=) at pthread_create.c:477 #10 0x7f859f96e833 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 2 (Thread 0x7f858e934700 (LWP 3244)): #0 0x7f859f9639cf in __GI___poll (fds=0x7f85880029e0, nfds=2, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7f859e57fa8d in g_main_context_poll (priority=, n_fds=2, fds=0x7f85880029e0, t--Type for more, q to quit, c to continue without paging--c imeout=, context=0x7f8588000c30) at ../glib/gmain.c:4346 #2 g_main_context_iterate (context=context@entry=0x7f8588000c30, block=block@entry=1, dispatch=dispatch@entry=1, self=) at ../glib/gmain.c:4042 #3 0x7f859e57fbc3 in g_main_context_iteration (context=0x7f8588000c30, may_block=may_block@entry=1) at ../glib/gmain.c:4108 #4 0x7f859fec1b75 in QEventDispatcherGlib::processEvents (this=0x7f8588000b60, flags=...) at kernel/qeventdispatcher_glib.cpp:423 #5 0x7f859fe751db in QEventLoop::exec (this=this@entry=0x7f858e933d50, flags=..., flags@entry=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:140 #6 0x7f859fcea6e7 in QThread::exec (this=) at ../../include/QtCore/../../src/corelib/global/qflags.h:120 #7 0x7f85a0dc64da in QDBusConnectionManager::run (this=0x7f85a0e34060 <(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at qdbusconnection.cpp:178 #8 0x7f859fceb9b6 in QThreadPrivate::start(void*) () at thread/qthread_unix.cpp:360 #9 0x7f859f206432 in start_thread (arg=) at pthread_create.c:477 #10 0x7f859f96e833 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 1 (Thread 0x7f85a1aac580 (LWP 3242)): #0 __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50 #1 0x7f859f892895 in __GI_abort () at abort.c:79 #2 0x7f859fcb7a25 in qt_message_fatal (message=..., context=...) at global/qlogging.cpp:1907 #3 QMessageLogger::fatal (this=this@entry=0x7fff06080940, msg=msg@entry=0x7f858ef47e70 "The Wayland connection experienced a fatal error: %s") at global/qlogging.cpp:888 #4 0x7f858eeb4c24 in QtWaylandClient::QWaylandDisplay::checkError (this=) at /usr/include/qt5/QtCore/qlogging.h:91 #5 0x7f858eeb4c7e in QtWaylandClient::QWaylandDisplay::flushRequests (this=0x55cee4ad31f0)
[ksmserver] [Bug 418601] New: Cannot restart by clicking on the "Restart " button
https://bugs.kde.org/show_bug.cgi?id=418601 Bug ID: 418601 Summary: Cannot restart by clicking on the "Restart " button Product: ksmserver Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: hep30...@gmail.com CC: plasma-b...@kde.org Target Milestone: --- Created attachment 126663 --> https://bugs.kde.org/attachment.cgi?id=126663&action=edit ksmserver-logout-greeter crash report SUMMARY Could not restart when clicked on the restart button . An error popped up. This happened after I installed the system updates received for my KDE Neon distribution. Had to restart using command from konsole STEPS TO REPRODUCE 1. clicking on restart button 2. 3. OBSERVED RESULT PC did not restart . Tried twice . EXPECTED RESULT PC should restart SOFTWARE/OS VERSIONS KDE Neon OS 5.18 user edition KDE Plasma Version : 5.18.2 KDE Frameworks Version : 5.67.0 QT version : 5.14.1 Kernel Version : 5.3.0-40 generic OS type : 64-bit ADDITIONAL INFORMATION 4*intel Core i3 9100F CPU @ 3.60Ghz RAM 7.7GB VGA : Nvidia GForce GT 710 VG Driver version : 440.64 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kwayland] [Bug 416974] Plasma 5.17.90 crashed due to a kwin_wayland segmentation fault in QWeakPointer::QWeakPointer
https://bugs.kde.org/show_bug.cgi?id=416974 Matt Fagnani changed: What|Removed |Added CC||kwin-bugs-n...@kde.org Assignee|kwin-bugs-n...@kde.org |mgraess...@kde.org Version|5.17.90 |5.67.0 Platform|Other |Fedora RPMs Product|kwin|frameworks-kwayland Component|wayland-generic |server --- Comment #1 from Matt Fagnani --- I've continued seeing these kwin_wayland segmentation faults with Plasma 5.18.2, KF 5.67.0, Qt 5.13.2 in Fedora 32 when using firefox, vlc, and system settings. The crashes when using vlc were with vlc in full screen mode. I'm reassigning this report to frameworks-wayland because the trace involved kwayland where the invalid pointers started in KWayland::Server::SurfaceInterface::lockedPointer at /usr/src/debug/kf5-kwayland-5.66.0-1.fc32.x86_64/src/server/surface_interface.cpp:937. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 385726] Add Support For Apple Live Photos
https://bugs.kde.org/show_bug.cgi?id=385726 --- Comment #17 from Glassed Silver --- https://drive.google.com/drive/folders/1PgxB3JBql7kRzOkEzhBwqKQUXtddcLAj?usp=sharing The filesize limit doesn't allow me to include the files directly, which is a shame, not a fan of link rot and I gotta admit, this link WILL go down once this issue is resolved, because I don't like lingering public links on my Drive account. Either way, I included a sample for Huawei's "Moving Picture" implementation. (consumer info page: https://consumer.huawei.com/uk/support/faq/how-to-take-moving-pictures/) The pic was taken on my MediaPad M5 8.4" tablet. Not amazing quality on that one, but should do the trick of showing the file's logic. I also included a sample for Samsung's "Motion Photo". (consumer info page: https://www.samsung.com/global/galaxy/what-is/motion-photo/ (it doesn't list S20 as compatible device, but it's been reported that it is indeed still a maintained feature, guess they forgot to update that page so far) That pic was taken with my Galaxy Note9. Forgive the dirty keyboard... -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 418598] Broken KDE packagages, kdevelop, kmail and others due to missing libqca-qt5-2 (>= 2.3.0)
https://bugs.kde.org/show_bug.cgi?id=418598 --- Comment #6 from Nick --- Can you paste the link to the newer version of libqca-qt5-2, I've been browsing http://archive.neon.kde.org/user ie https://origin.archive.neon.kde.org/user/pool/main/q/qca-qt5/ https://origin.archive.neon.kde.org/user/lts/pool/main/q/qca-qt5/ but they are all older versions. I guess I'm looking in the wrong place ? -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 418598] Broken KDE packagages, kdevelop, kmail and others due to missing libqca-qt5-2 (>= 2.3.0)
https://bugs.kde.org/show_bug.cgi?id=418598 --- Comment #5 from Nick --- There's nothing in there with qca embedded in the filename. /etc/apt/preferences.d# ls -al *qca* ls: cannot access '*qca*': No such file or directory All that's in there is: 98-xenial-overrides 99-neon-base-files 99-neon-software-properties 99-plasma-discover 99-plasma-integration 99-pulseaudio-qt 99-xenial-overrides -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 339214] Starting KMail gives message "Could not create collection trash resourceId: 3 [MailCommon::Kernel::createDefaultCollectionDone, MailCommon::Kernel::emergencyExit]
https://bugs.kde.org/show_bug.cgi?id=339214 --- Comment #26 from Dennis Schridde --- Just ran into this again using: * KMail 5.13.3 (19.12.3) * KDE Frameworks 5.67.0 * Qt 5.14.1 (built against 5.14.1) -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 418598] Broken KDE packagages, kdevelop, kmail and others due to missing libqca-qt5-2 (>= 2.3.0)
https://bugs.kde.org/show_bug.cgi?id=418598 --- Comment #4 from Jonathan Riddell --- Well the newer libqca-qt5-2 is there Do you have anything in /etc/apt/preferences.d/*qca* Please pastebin if so -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 418600] New: i cannot put sounds on krita and i dont know what to do, it says error and i tried with diferent types of audios but its always error please help
https://bugs.kde.org/show_bug.cgi?id=418600 Bug ID: 418600 Summary: i cannot put sounds on krita and i dont know what to do, it says error and i tried with diferent types of audios but its always error please help Product: krita Version: 4.2.8 Platform: MS Windows OS: MS Windows Status: REPORTED Severity: normal Priority: NOR Component: File formats Assignee: krita-bugs-n...@kde.org Reporter: carla.gav...@hotmail.com Target Milestone: --- i need help please i cant put audios on krita and i dont know What to do, i tried with diferent types of audios and none of them worked, please send help -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 418598] Broken KDE packagages, kdevelop, kmail and others due to missing libqca-qt5-2 (>= 2.3.0)
https://bugs.kde.org/show_bug.cgi?id=418598 --- Comment #3 from Nick --- I'm not sure if this is the correct way to install the libqca-qt5-2 packages but this is what I get if I try to install using pkcon and apt sudo pkcon install libqca-qt5-2 Resolving [=] Package not found: libqca-qt5-2 Command failed: This tool could not find any available package: No packages were found and.. sudo apt-get install libqca-qt5-2 Reading package lists... Done Building dependency tree Reading state information... Done libqca-qt5-2 is already the newest version (2.1.3-2ubuntu2). Starting pkgProblemResolver with broken count: 0 Starting 2 pkgProblemResolver with broken count: 0 Done 0 to upgrade, 0 to newly install, 0 to remove and 3 not to upgrade. -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 418598] Broken KDE packagages, kdevelop, kmail and others due to missing libqca-qt5-2 (>= 2.3.0)
https://bugs.kde.org/show_bug.cgi?id=418598 --- Comment #2 from Nick --- Output is: apt-cache policy libqca-qt5-2 libqca-qt5-2: Installed: 2.1.3-2ubuntu2 Candidate: 2.1.3-2ubuntu2 Version table: 2.3.0-0xneon+18.04+bionic+build5 500 500 http://archive.neon.kde.org/user bionic/main amd64 Packages 2.2.1-0xneon+18.04+bionic+build4 500 500 http://archive.neon.kde.org/user bionic/main amd64 Packages 2.1.3-2+18.04+bionic+build2 500 500 http://archive.neon.kde.org/user bionic/main amd64 Packages *** 2.1.3-2ubuntu2 1100 500 http://archive.ubuntu.com/ubuntu bionic/universe amd64 Packages 100 /var/lib/dpkg/status -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 418598] Broken KDE packagages, kdevelop, kmail and others due to missing libqca-qt5-2 (>= 2.3.0)
https://bugs.kde.org/show_bug.cgi?id=418598 --- Comment #1 from Jonathan Riddell --- trying just now I get ~$ apt-cache policy libqca-qt5-2 libqca-qt5-2: Installed: 2.2.1-0xneon+18.04+bionic+build4 Candidate: 2.3.0-0xneon+18.04+bionic+build5 Version table: 2.3.0-0xneon+18.04+bionic+build5 500 500 http://archive.neon.kde.org/user bionic/main amd64 Package What is your output from apt-cache policy libqca-qt5-2 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 414396] KCM can't read settings file (kde_settings.conf)
https://bugs.kde.org/show_bug.cgi?id=414396 --- Comment #39 from Filip Fila --- Sorry, I've now tried multiple times and whichever theme I save the settings window will highlight it correctly the next time it's started. My sddm.conf is empty and the theme is being saved correctly to kde_settings.conf. The only way I can reproduce your troubles is if I change the theme and then immediately go to 'Advanced' and press 'Sync' instead of actually clicking 'Apply' on the bottom. Clicking 'Sync' is not the proper way to change the theme since it only applies what the sync function is supposed to do. -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 418599] New: Crash when moving emails from one IMAP server to another
https://bugs.kde.org/show_bug.cgi?id=418599 Bug ID: 418599 Summary: Crash when moving emails from one IMAP server to another Product: Akonadi Version: unspecified Platform: Gentoo Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: IMAP resource Assignee: kdepim-b...@kde.org Reporter: devuran...@gmx.net Target Milestone: --- Application: akonadi_imap_resource (5.13.3 (19.12.3)) Qt Version: 5.14.1 Frameworks Version: 5.67.0 Operating System: Linux 5.5.8 x86_64 Windowing system: X11 Distribution: "Gentoo Base System release 2.7" -- Information about the crash: - What I was doing when the application crashed: I moved 34 (contents of folder "a") and then another 40 (contents of folder "b") emails from one IMAP server to another. - Unusual behavior I noticed: First my Akonadi IMAP resource stopped syncing (bug #418593), then I deleted and recreated it, but it stopped connecting to the server after a while (bug #418595), then I recreated it again and am now running into this problem here. -- Backtrace: Application: Kynes (akonadi_imap_resource), signal: Segmentation fault Using host libthread_db library "/usr/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f8125eefd80 (LWP 275208))] Thread 24 (Thread 0x7f80c9dec700 (LWP 331976)): #0 0x7f8137e13d7d in pthread_cond_timedwait@@GLIBC_2.3.2 () at /usr/lib64/libpthread.so.0 #1 0x7f8138cb2205 in QWaitConditionPrivate::wait_relative(QDeadlineTimer) (this=0x7f80b80109a0, deadline=...) at thread/qwaitcondition_unix.cpp:136 #2 QWaitConditionPrivate::wait(QDeadlineTimer) (deadline=..., this=0x7f80b80109a0) at thread/qwaitcondition_unix.cpp:144 #3 QWaitCondition::wait(QMutex*, QDeadlineTimer) (this=, mutex=0x7f80b8010b88, deadline=...) at thread/qwaitcondition_unix.cpp:225 #4 0x7f8138cb2307 in QWaitCondition::wait(QMutex*, unsigned long) (this=this@entry=0x7f80b8011a80, mutex=mutex@entry=0x7f80b8010b88, time=) at thread/qwaitcondition_unix.cpp:209 #5 0x7f8138cb015b in QThreadPoolThread::run() (this=0x7f80b8011a70) at ../../include/QtCore/../../src/corelib/thread/qmutex.h:270 #6 0x7f8138caccef in QThreadPrivate::start(void*) (arg=0x7f80b8011a70) at thread/qthread_unix.cpp:342 #7 0x7f8137e0c42a in start_thread () at /usr/lib64/libpthread.so.0 #8 0x7f813886c42f in clone () at /usr/lib64/libc.so.6 Thread 23 (Thread 0x7f80ca5ed700 (LWP 331975)): #0 0x7f8136fb6b04 in g_mutex_unlock () at /usr/lib64/libglib-2.0.so.0 #1 0x7f8136f6807b in g_main_context_prepare () at /usr/lib64/libglib-2.0.so.0 #2 0x7f8136f68a53 in () at /usr/lib64/libglib-2.0.so.0 #3 0x7f8136f68c4f in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #4 0x7f8138eb889b in QEventDispatcherGlib::processEvents(QFlags) (this=0x7f80b006d480, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #5 0x7f8138e6101b in QEventLoop::exec(QFlags) (this=this@entry=0x7f80ca5ec820, flags=..., flags@entry=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:136 #6 0x7f8138cabc8e in QThread::exec() (this=) at ../../include/QtCore/../../src/corelib/global/qflags.h:118 #7 0x7f8138caccef in QThreadPrivate::start(void*) (arg=0x55fd085546d0) at thread/qthread_unix.cpp:342 #8 0x7f8137e0c42a in start_thread () at /usr/lib64/libpthread.so.0 #9 0x7f813886c42f in clone () at /usr/lib64/libc.so.6 Thread 22 (Thread 0x7f80cadee700 (LWP 275243)): #0 0x7f81388600db in poll () at /usr/lib64/libc.so.6 #1 0x7f8136f68b2e in () at /usr/lib64/libglib-2.0.so.0 #2 0x7f8136f68c4f in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #3 0x7f8138eb889b in QEventDispatcherGlib::processEvents(QFlags) (this=0x7f80b8000b60, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #4 0x7f8138e6101b in QEventLoop::exec(QFlags) (this=this@entry=0x7f80caded820, flags=..., flags@entry=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:136 #5 0x7f8138cabc8e in QThread::exec() (this=) at ../../include/QtCore/../../src/corelib/global/qflags.h:118 #6 0x7f8138caccef in QThreadPrivate::start(void*) (arg=0x55fd07c250d0) at thread/qthread_unix.cpp:342 #7 0x7f8137e0c42a in start_thread () at /usr/lib64/libpthread.so.0 #8 0x7f813886c42f in clone () at /usr/lib64/libc.so.6 Thread 21 (Thread 0x7f80cb5ef700 (LWP 275242)): #0 0x7f81388600db in poll () at /usr/lib64/libc.so.6 #1 0x7f8136f68b2e in () at /usr/lib64/libglib-2.0.so.0 #2 0x7f8136f68c4f in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #3 0x7f8138eb889b in QEventDispatcherGlib::processEvents(QFlags) (this=0x7f80cb60, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #4 0x7f8138e6101b in QEventLoop::exec(QFlags) (this=this@entry=0x7f80cb5ee820, flags=..., flags@entry=...) at ../../include/QtCore
[kdeconnect] [Bug 417787] sshfs key exchange methods deprecated
https://bugs.kde.org/show_bug.cgi?id=417787 --- Comment #5 from Dennis Schridde --- (In reply to David from comment #2) > Has been fixed by adding a key exchange option in the desktop application. Shouldn't this be fixed by fixing the Android app to no longer use deprecated hash algorithms? -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 417787] sshfs key exchange methods deprecated
https://bugs.kde.org/show_bug.cgi?id=417787 Dennis Schridde changed: What|Removed |Added CC||devuran...@gmx.net -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 418598] New: Broken KDE packagages, kdevelop, kmail and others due to missing libqca-qt5-2 (>= 2.3.0)
https://bugs.kde.org/show_bug.cgi?id=418598 Bug ID: 418598 Summary: Broken KDE packagages, kdevelop, kmail and others due to missing libqca-qt5-2 (>= 2.3.0) Product: neon Version: unspecified Platform: Neon Packages OS: Linux Status: REPORTED Severity: major Priority: NOR Component: Packages User Edition Assignee: neon-b...@kde.org Reporter: nick.craig@gmail.com CC: j...@jriddell.org, neon-b...@kde.org, sit...@kde.org Target Milestone: --- After an update today 07/Mar/2020 a load of KDE programs no longer are installed. Two of the ones I'm most concerned about being kmail and kdevelop Looks like a newer version of libqca-qt5-2 (>= 2.3.0) is required but all that's available is 2.1.3-2ubuntu2 ? The following packages have unmet dependencies. libkasten4okteta2controllers0 : Depends: libqca-qt5-2 (>= 2.3.0) but 2.1.3-2ubuntu2 is to be installed E: Unable to correct problems, you have held broken packages. Any quick solution to this, I need to get kdevelop working again by tomorrow. Also noted by another user in the forum here https://forum.kde.org/viewtopic.php?f=309&t=164896&p=429334#p429334 SOFTWARE/OS VERSIONS Linux/KDE Plasma: (available in About System) KDE Plasma Version: Neon 5.18.2 (after update on 07/Mar/2020 KDE Frameworks Version: 5.67.0 Qt Version: 5.14.1 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 418442] Experiencing 100% cpu usage whenever a notification is present
https://bugs.kde.org/show_bug.cgi?id=418442 --- Comment #2 from jeep7...@gmail.com --- Here is a perf file: http://s000.tinyupload.com/index.php?file_id=74021570478791780318 I am new to this, so I am not sure I did it right, but what I used was: perf record -F 99 plasmashell I am not sure how to get a backtrace. -- You are receiving this mail because: You are watching all bug changes.
[kalgebra] [Bug 418597] New: Incorrect plot on function (x-0.7)^2+3*(x-0.7)
https://bugs.kde.org/show_bug.cgi?id=418597 Bug ID: 418597 Summary: Incorrect plot on function (x-0.7)^2+3*(x-0.7) Product: kalgebra Version: 19.12 Platform: Debian testing OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: aleix...@kde.org Reporter: sh200...@mail.ru Target Milestone: --- STEPS TO REPRODUCE 1. Make a plot with the function "(x-0.7)^2+3*(x-0.7)" OBSERVED RESULT The function never passes through zero. EXPECTED RESULT The function must pass through zero when x = 0.7. SOFTWARE/OS VERSIONS Linux/KDE Plasma: (available in About System) KDE Plasma Version: 5.17.5 KDE Frameworks Version: 5.62.0 Qt Version: 5.12.5 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 418594] Should warn the user immediately when database not writable
https://bugs.kde.org/show_bug.cgi?id=418594 Maik Qualmann changed: What|Removed |Added Resolution|--- |FIXED Status|REPORTED|RESOLVED Version Fixed In||7.0.0 Latest Commit||https://invent.kde.org/kde/ ||digikam/commit/0bd27c67171f ||86ef69a8621a473c98857389ca6 ||8 --- Comment #1 from Maik Qualmann --- Git commit 0bd27c67171f86ef69a8621a473c98857389ca68 by Maik Qualmann. Committed on 07/03/2020 at 21:42. Pushed by mqualmann into branch 'master'. also check SQLite for database rights FIXED-IN: 7.0.0 M +2-1NEWS M +17 -20 core/libs/database/coredb/coredbschemaupdater.cpp https://invent.kde.org/kde/digikam/commit/0bd27c67171f86ef69a8621a473c98857389ca68 -- You are receiving this mail because: You are watching all bug changes.
[kalgebra] [Bug 409472] Wrong result coming from calculator and plotter
https://bugs.kde.org/show_bug.cgi?id=409472 Alexander Kernozhitsky changed: What|Removed |Added CC||sh200...@mail.ru --- Comment #5 from Alexander Kernozhitsky --- It seems to be duplicate of https://bugs.kde.org/show_bug.cgi?id=402637. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 418596] New: Animation does not play properly higher than about 10-15 fps (effects audio as well)
https://bugs.kde.org/show_bug.cgi?id=418596 Bug ID: 418596 Summary: Animation does not play properly higher than about 10-15 fps (effects audio as well) Product: krita Version: unspecified Platform: Windows CE OS: Windows CE Status: REPORTED Severity: normal Priority: NOR Component: Animation Assignee: krita-bugs-n...@kde.org Reporter: altmai...@gmail.com Target Milestone: --- SUMMARY While working on an animation in the program, if I do anything above 10-15 frames per second the frames glitch, making it hard to create an accurate animation. Audio is effected after 10 frames per second and starts doing mini-loops on itself. However, once the animation is exported it is fine. STEPS TO REPRODUCE 1. Open Krita and make a short animation possibly with some audio 2. set the frame rate to above 15fps. 3. OBSERVED RESULT Frames play slower than frame rate. EXPECTED RESULT Frames should play at frame rate. SOFTWARE/OS VERSIONS Windows: Windows 10 Home 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.
[Akonadi] [Bug 418595] Akonadi IMAP resource crashed after it lost connection and I tried to restart it
https://bugs.kde.org/show_bug.cgi?id=418595
--- Comment #2 from Dennis Schridde ---
I ran `akonadictl restart`, but that was a bumpy ride:
org.kde.pim.akonadicontrol: ProcessControl: Application
"/usr/bin/akonadiserver" stopped unexpectedly ( "Process crashed" )
org.kde.pim.akonadicontrol: Application '/usr/bin/akonadiserver' crashed. No
restart!
Connecting to deprecated signal
QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString)
org.kde.pim.akonadiserver: Starting up the Akonadi Server...
❯ akonadictl restart
Akonadi is not running.
❯ akonadictl start
org.kde.pim.akonadicontrol: Service org.freedesktop.Akonadi.Control.lock
already registered, terminating now.
Error: akonadi_control was started but didn't register at D-Bus session bus.
Make sure your system is set up correctly!
❯ ps aux | rg akonadi
dschrid+ 246610 10.6 1.5 851584 225956 ? Sl 21:04 4:17
/usr/sbin/mysqld
--defaults-file=/home/dschridde/.local/share/akonadi/mysql.conf
--datadir=/home/dschridde/.local/share/akonadi/db_data/
--socket=/run/user/1000/akonadi/mysql.socket
--pid-file=/run/user/1000/akonadi/mysql.pid
dschrid+ 249132 0.3 1.0 3450644 153252 ? Sl 21:08 0:08
/usr/bin/akonadiconsole
dschrid+ 265348 0.0 0.0 10568 5860 ?S21:44 0:00
/usr/bin/mysqladmin
--defaults-file=/home/dschridde/.local/share/akonadi/mysql.conf
--socket=/run/user/1000/akonadi/mysql.socket shutdown
dschrid+ 265363 0.2 0.3 431516 43944 ?Sl 21:44 0:00
/usr/bin/akonadi_control
dschrid+ 265394 0.1 0.1 167704 24844 ?Sl 21:44 0:00
/usr/bin/akonadiserver
dschrid+ 265399 0.3 0.1 67932 19096 ?Sl 21:44 0:00
/usr/sbin/mysqld
--defaults-file=/home/dschridde/.local/share/akonadi/mysql.conf
--datadir=/home/dschridde/.local/share/akonadi/db_data/
--socket=/run/user/1000/akonadi/mysql.socket
--pid-file=/run/user/1000/akonadi/mysql.pid
dschrid+ 265735 0.0 0.0 5384 8 pts/6D+ 21:44 0:00 rg akonadi
❯ akonadictl status
Akonadi Control: stopped
Akonadi Server: stopped
Akonadi Server Search Support: available (Remote Search, Akonadi Search Plugin)
Available Agent Types: akonadi_akonotes_resource, akonadi_archivemail_agent,
akonadi_birthdays_resource, akonadi_contacts_resource,
akonadi_davgroupware_resource, akonadi_ews_resource, akonadi_ewsmta_resource,
akonadi_followupreminder_agent, akonadi_googlecalendar_resource,
akonadi_googlecontacts_resource, akonadi_ical_resource,
akonadi_icaldir_resource, akonadi
_imap_resource, akonadi_indexing_agent, akonadi_kalarm_dir_resource,
akonadi_kalarm_resource, akonadi_knut_resource, akonadi_maildir_resource,
akonadi_maildispatcher_agent, akonadi_mailfilter_agent, akonadi_mbox_resource,
akonadi_migration_agent, akonadi_mixedmaildir_resource,
akonadi_newmailnotifier_agent, akonadi_notes_agent, akonadi_notes_resource,
akonadi_op
enxchange_resource, akonadi_pop3_resource, akonadi_sendlater_agent,
akonadi_tomboynotes_resource, akonadi_unifiedmailbox_agent,
akonadi_vcard_resource, akonadi_vcarddir_resource
After I while I saw output from `akonadictl restart` (I presume):
org.kde.pim.akonadiserver: database server stopped unexpectedly
org.kde.pim.akonadiserver: Database process exited unexpectedly during initial
connection!
org.kde.pim.akonadiserver: executable: "/usr/sbin/mysqld"
org.kde.pim.akonadiserver: arguments:
("--defaults-file=/home/dschridde/.local/share/akonadi/mysql.conf",
"--datadir=/home/dschridde/.local/share/akonadi/db_data/",
"--socket=/run/user/1000/akonadi/mysql.socket",
"--pid-file=/run/user/1000/akonadi/mysql.pid")
org.kde.pim.akonadiserver: stdout: ""
org.kde.pim.akonadiserver: stderr: "2020-03-07 21:44:20 0 [Note]
/usr/sbin/mysqld (mysqld 10.4.12-MariaDB) starting as process 265399 ...\n"
org.kde.pim.akonadiserver: exit code: 1
org.kde.pim.akonadiserver: process error: "Process
[Akonadi] [Bug 418595] Akonadi IMAP resource crashed after it lost connection and I tried to restart it
https://bugs.kde.org/show_bug.cgi?id=418595 --- Comment #1 from Dennis Schridde --- > because it stopped synchronising That issue is described in bug #418593. -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 418595] Akonadi IMAP resource crashed after it lost connection and I tried to restart it
https://bugs.kde.org/show_bug.cgi?id=418595 Dennis Schridde changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=418593 -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 418595] New: Akonadi IMAP resource crashed after it lost connection and I tried to restart it
https://bugs.kde.org/show_bug.cgi?id=418595 Bug ID: 418595 Summary: Akonadi IMAP resource crashed after it lost connection and I tried to restart it Product: Akonadi Version: unspecified Platform: Gentoo Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: IMAP resource Assignee: kdepim-b...@kde.org Reporter: devuran...@gmx.net Target Milestone: --- Application: akonadi_imap_resource (5.13.3 (19.12.3)) Qt Version: 5.14.1 Frameworks Version: 5.67.0 Operating System: Linux 5.5.8 x86_64 Windowing system: X11 Distribution: "Gentoo Base System release 2.7" -- Information about the crash: - What I was doing when the application crashed: I set up a new Akonadi IMAP resource (for a server that I had previously set up, but I had to delete the Akonadi IMAP resource for it, because it stopped synchronising), after synchronising a few folders the resource put out a lot of messages of not being able to create connections to the server and then stopped doing anything. I tried to restart it, after which it still said "Unable to connect to the IMAP server". I tried to restart it again, and it crashed. -- Backtrace: Application: Kynes (akonadi_imap_resource), signal: Segmentation fault Using host libthread_db library "/usr/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f83d0b28d80 (LWP 266490))] Thread 24 (Thread 0x7f8363f7d700 (LWP 273498)): #0 0x7f83e2a4cd7d in pthread_cond_timedwait@@GLIBC_2.3.2 () at /usr/lib64/libpthread.so.0 #1 0x7f83e38eb205 in QWaitConditionPrivate::wait_relative(QDeadlineTimer) (this=0x7f83640109a0, deadline=...) at thread/qwaitcondition_unix.cpp:136 #2 QWaitConditionPrivate::wait(QDeadlineTimer) (deadline=..., this=0x7f83640109a0) at thread/qwaitcondition_unix.cpp:144 #3 QWaitCondition::wait(QMutex*, QDeadlineTimer) (this=, mutex=0x7f8364010b88, deadline=...) at thread/qwaitcondition_unix.cpp:225 #4 0x7f83e38eb307 in QWaitCondition::wait(QMutex*, unsigned long) (this=this@entry=0x7f8364011a80, mutex=mutex@entry=0x7f8364010b88, time=) at thread/qwaitcondition_unix.cpp:209 #5 0x7f83e38e915b in QThreadPoolThread::run() (this=0x7f8364011a70) at ../../include/QtCore/../../src/corelib/thread/qmutex.h:270 #6 0x7f83e38e5cef in QThreadPrivate::start(void*) (arg=0x7f8364011a70) at thread/qthread_unix.cpp:342 #7 0x7f83e2a4542a in start_thread () at /usr/lib64/libpthread.so.0 #8 0x7f83e34a542f in clone () at /usr/lib64/libc.so.6 Thread 23 (Thread 0x7f83c0ed6700 (LWP 273497)): #0 0x7f83e1befb04 in g_mutex_unlock () at /usr/lib64/libglib-2.0.so.0 #1 0x7f83e1ba107b in g_main_context_prepare () at /usr/lib64/libglib-2.0.so.0 #2 0x7f83e1ba1a53 in () at /usr/lib64/libglib-2.0.so.0 #3 0x7f83e1ba1c4f in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #4 0x7f83e3af189b in QEventDispatcherGlib::processEvents(QFlags) (this=0x7f836406e810, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #5 0x7f83e3a9a01b in QEventLoop::exec(QFlags) (this=this@entry=0x7f83c0ed5820, flags=..., flags@entry=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:136 #6 0x7f83e38e4c8e in QThread::exec() (this=) at ../../include/QtCore/../../src/corelib/global/qflags.h:118 #7 0x7f83e38e5cef in QThreadPrivate::start(void*) (arg=0x564e8a81a920) at thread/qthread_unix.cpp:342 #8 0x7f83e2a4542a in start_thread () at /usr/lib64/libpthread.so.0 #9 0x7f83e34a542f in clone () at /usr/lib64/libc.so.6 Thread 22 (Thread 0x7f83a97fa700 (LWP 267813)): #0 0x7f83e1befad9 in g_mutex_lock () at /usr/lib64/libglib-2.0.so.0 #1 0x7f83e1ba1095 in g_main_context_prepare () at /usr/lib64/libglib-2.0.so.0 #2 0x7f83e1ba1a53 in () at /usr/lib64/libglib-2.0.so.0 #3 0x7f83e1ba1c4f in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #4 0x7f83e3af189b in QEventDispatcherGlib::processEvents(QFlags) (this=0x7f8368002e90, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #5 0x7f83e3a9a01b in QEventLoop::exec(QFlags) (this=this@entry=0x7f83a97f9820, flags=..., flags@entry=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:136 #6 0x7f83e38e4c8e in QThread::exec() (this=) at ../../include/QtCore/../../src/corelib/global/qflags.h:118 #7 0x7f83e38e5cef in QThreadPrivate::start(void*) (arg=0x564e8abd57d0) at thread/qthread_unix.cpp:342 #8 0x7f83e2a4542a in start_thread () at /usr/lib64/libpthread.so.0 #9 0x7f83e34a542f in clone () at /usr/lib64/libc.so.6 Thread 21 (Thread 0x7f83c16f4700 (LWP 266819)): #0 0x7f83e34990db in poll () at /usr/lib64/libc.so.6 #1 0x7f83e1ba1b2e in () at /usr/lib64/libglib-2.0.so.0 #2 0x7f83e1ba1c4f in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #3 0x7f83e3af189b in QEventDispatcherGlib::processEvents(QFlags) (this=0x
[Akonadi] [Bug 418593] Akonadi IMAP crashed while moving mails after: Error while handling command FetchCollections on connection akonadi_imap_resource_0
https://bugs.kde.org/show_bug.cgi?id=418593 Dennis Schridde changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=418595 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 418594] New: Should warn the user immediately when database not writable
https://bugs.kde.org/show_bug.cgi?id=418594 Bug ID: 418594 Summary: Should warn the user immediately when database not writable Product: digikam Version: 7.0.0 Platform: Other OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: Database Assignee: digikam-bugs-n...@kde.org Reporter: st...@sumost.ca Target Milestone: --- SUMMARY When the DB file (digikam4.db) isn't writable, the user is only warned when making changes, in the UI. Would be preferable to be warned on launch. STEPS TO REPRODUCE 1. Remove write permission from digikam4.db 2. Launch digikam 3. Attempt to create a new tag OBSERVED RESULT Error displayed in Step 3. EXPECTED RESULT Error displayed in Step 2. SOFTWARE/OS VERSIONS Digikam 7.0.0 beta 2 Digikam 6.4.0 ADDITIONAL INFORMATION Reported in Debian https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=731619 -- You are receiving this mail because: You are watching all bug changes.
[k3b] [Bug 418421] freeDB.org is shutting down; k3b needs to use a different service
https://bugs.kde.org/show_bug.cgi?id=418421 Tristan Miller changed: What|Removed |Added Resolution|WAITINGFORINFO |--- Status|NEEDSINFO |CONFIRMED --- Comment #2 from Tristan Miller --- (In reply to Albert Astals Cid from comment #1) > k3b can already also use musicbrainz no? According to Bug 80993 it doesn't do this for audio CD rips. I haven't tested this myself. > What other service is there that is not freedb and not musicbrainz? None that I'm aware of, and none that a cursory web search turns up. -- You are receiving this mail because: You are watching all bug changes.
[akregator] [Bug 377485] regression: system tray icon no longer shows number of unread articles
https://bugs.kde.org/show_bug.cgi?id=377485 Jaromir Smrcek changed: What|Removed |Added CC||jaromir.smr...@zoner.com --- Comment #10 from Jaromir Smrcek --- Created attachment 126662 --> https://bugs.kde.org/attachment.cgi?id=126662&action=edit Put the tray count back Unbelievable. Another KDE app that gets worse with updates. I mean really? Instead of fixing the problem with readability you *remove* a feature? I have created a reversal patch (without the config option). It uses Normal text color instead of link to make it a little more readable on my system. -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 418593] New: Akonadi IMAP crashed while moving mails after: Error while handling command FetchCollections on connection akonadi_imap_resource_0
https://bugs.kde.org/show_bug.cgi?id=418593 Bug ID: 418593 Summary: Akonadi IMAP crashed while moving mails after: Error while handling command FetchCollections on connection akonadi_imap_resource_0 Product: Akonadi Version: unspecified Platform: Gentoo Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: IMAP resource Assignee: kdepim-b...@kde.org Reporter: devuran...@gmx.net Target Milestone: --- Application: akonadi_imap_resource (5.13.3 (19.12.3)) Qt Version: 5.14.1 Frameworks Version: 5.67.0 Operating System: Linux 5.5.8 x86_64 Windowing system: X11 Distribution: "Gentoo Base System release 2.7" -- Information about the crash: - What I was doing when the application crashed: 1. I moved a bunch of emails from "one" IMAP server to "another" using KMail 2. (I tried to move two folders "a" and "b" with the new emails from "another" into a "third" \NoSelect folder (as a new child) on the "one" server, which KMail does not allow me to do, I cannot even drop the folder there) 3. (That is IIRC an issue in KMail related to \NoSelect, so I ran `create "third"`, which succeeded.) 4. (After clicking "Check Mail" in KMail or "Synchronise All" in Akonadi Console, KMail still displays the "third" folder as greyed-out and does not allow me to move folders into it.) 5. I moved both folders "a" and "b" to the top level of the "one" IMAP server 6. Using another IMAP client (`gnutls-cli`) I ran `rename "a" "third/a"` on the "one" IMAP server 7. Also using that other IMAP client, I tried to rename "b" to "third/b", but the "one" IMAP server replied "NO [NONEXISTENT]" 8. Also using that other IMAP client, I ran `create "third/b"`, which succeeded 9. Coming back to KMail, it still displays "a" and "b" at the root level of the "one" IMAP server, "third/a" also exists, but "third/b" does not 10. "Check Mail" in KMail or "Synchronise All" in Akonadi Console do not fix this 11. KMail displayed "a" on "another" IMAP server as empty, so I deleted it 12. KMail displayed "b" on "another" IMAP server as non-empty, so I kept it 13. Using KMail I moved the emails from "b" in the top level of the "one" IMAP server back to the folder on "another" IMAP server 14. Also using KMail I moved the folder "a" from the "one" IMAP server back to "another" IMAP server 15. I also used KMail to move the emails from "third/a" on "one" IMAP server back into folder "a" on "another" IMAP server - Unusual behavior I noticed: When running `akonadictl restart` or restarting the Akonadi IMAP Account, I see the following in the output: > Error while handling command FetchCollections on connection > akonadi_imap_resource_0 - Status afterwards / the problem: The Akonadi IMAP account for the "one" IMAP server does not synchronise at all anymore. When clicking "Check Mail > one IMAP server" in KMail nothing happens. The agent status as displayed by Akonadi Console does not change either. Additionally I can "sometimes" make the Akonadi IMAP resource crash. I am not yet sure what exactly I need to do to make it crash. I am a bit afraid of the state of my emails and what would happen if I was to delete the "one" IMAP server account in Akonadi and would recreate it. - Wild guess: Akonadi IMAP does not handle it very well when other IMAP clients are fiddling with the mailboxes (create, delete, rename) while it itself is moving mailboxes around. The crash can be reproduced sometimes. -- Backtrace: Application: Kynes (akonadi_imap_resource), signal: Segmentation fault Using host libthread_db library "/usr/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f62b4cf7d80 (LWP 250421))] Thread 23 (Thread 0x7f6260a09700 (LWP 250488)): #0 0x7f62c76636f8 in read () at /usr/lib64/libc.so.6 #1 0x7f62c5dba51f in () at /usr/lib64/libglib-2.0.so.0 #2 0x7f62c5d70657 in g_main_context_check () at /usr/lib64/libglib-2.0.so.0 #3 0x7f62c5d70ad3 in () at /usr/lib64/libglib-2.0.so.0 #4 0x7f62c5d70c4f in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #5 0x7f62c7cc089b in QEventDispatcherGlib::processEvents(QFlags) (this=0x7f624b60, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #6 0x7f62c7c6901b in QEventLoop::exec(QFlags) (this=this@entry=0x7f6260a08820, flags=..., flags@entry=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:136 #7 0x7f62c7ab3c8e in QThread::exec() (this=) at ../../include/QtCore/../../src/corelib/global/qflags.h:118 #8 0x7f62c7ab4cef in QThreadPrivate::start(void*) (arg=0x5646bf81cda0) at thread/qthread_unix.cpp:342 #9 0x7f62c6c1442a in start_thread () at /usr/lib64/libpthread.so.0 #10 0x7f62c767442f in clone () at /usr/lib64/libc.so.6 Thread 22 (Thread 0x7f62615eb700 (LWP 250444)): #0 0x7f62c6c1bd7d in pthread_cond_timedwait@@
[Spectacle] [Bug 414910] Customize keyboard shortcuts
https://bugs.kde.org/show_bug.cgi?id=414910 Merritt changed: What|Removed |Added CC||merritt_pub...@outlook.com --- Comment #2 from Merritt --- Thanks for the info about doing a custom shortcut with flags, that works great. Would be ideal to have this as a simple toggle in Spectacle settings, seems much more user friendly that way. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 418592] New: Rendering a zone with the in and out points being at 'splits' between clips fails
https://bugs.kde.org/show_bug.cgi?id=418592 Bug ID: 418592 Summary: Rendering a zone with the in and out points being at 'splits' between clips fails Product: kdenlive Version: 19.08.2 Platform: Ubuntu Packages OS: Linux Status: REPORTED Severity: major Priority: NOR Component: Video Display & Export Assignee: j...@kdenlive.org Reporter: sb24kel...@gmail.com Target Milestone: --- SUMMARY I'm using Lubuntu 19.10 with standard packages, except that I am using a Radeon r380 and had tried to install the proprietary drivers -- it didn't work, but the system is otherwise functional for gaming and video production so I don't think that's the issue. When rendering a selected zone with the in and out points being at splits between clips, the rendering process appears to start as normal, but quickly reports "Rendering finished in 00:00:01" -- trying to play the output file with VLC does not work. I have not tested this for reproducibility, I'm just describing what happened. I tried a couple of different ways of rendering what I needed to render, and finally wound up deleting the clips on either side of the clip I wanted, moving it to the front of the timeline, and just rendering the "whole project." STEPS TO REPRODUCE 1. Import a 720p hd 30fps .mp4 clip with length "02:03:05:11" 2. Drop the clip in V1 and A1, and delete v2 and a2 3. Create splits at 00:12:26:12 and 00:16:20:00, and set the zone in and out there as well 4. Add Saturation [Sat.: 26] and Denoiser [Spat.: 227; Temp.: 267] effects to the middlemost clip created by the splits 5. Start to render the Selected Zone with any output format (I tried several but not all) OBSERVED RESULT Rendering finished in 00:00:01, with a non-functional output file EXPECTED RESULT Rendering finished in 00:04:30, with a watchable file -- You are receiving this mail because: You are watching all bug changes.
[rkward] [Bug 418591] New: Keep showing Transferring dialog while loading help files
https://bugs.kde.org/show_bug.cgi?id=418591
Bug ID: 418591
Summary: Keep showing Transferring dialog while loading help
files
Product: rkward
Version: unspecified
Platform: Compiled Sources
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: general
Assignee: rkward-de...@kde.org
Reporter: adleyv...@gmail.com
Target Milestone: ---
Created attachment 126661
--> https://bugs.kde.org/attachment.cgi?id=126661&action=edit
rkward.frontend
SUMMARY
debug file "rkward.frontend" said:
Couldn't start kuiserver from org.kde.kuiserver.service:
QDBusError("org.freedesktop.DBus.Error.ServiceUnknown", "The name is not
activatable")
Shortcut for action "output_refresh" "Reload" set with QAction::setShortcut()!
Use KActionCollection::setDefaultShortcut(s) instead.
STEPS TO REPRODUCE
1. Type for example ?help in R console
OBSERVED RESULT
Keep showing Transferring dialog
EXPECTED RESULT
Showing help file in viewer.
SOFTWARE/OS VERSIONS
Windows:
macOS:
Linux/KDE Plasma:
(available in About System)
KDE Plasma Version:
KDE Frameworks Version:
Qt Version:
ADDITIONAL INFORMATION
---Problem description---
Please fill in the missing bits *in English*.
Please give a brief summary on the problem:
###Please fill in###
What - in detail - did you do directly before you encountered this problem?
###Please fill in###
When you try to repeat the above, does the problem occur again (no, sometimes,
always)?
###Please fill in###
If applicable: When doing the same thing in an R session outside of RKWard, do
you see the same problem?
###Please fill in###
Do you have any further information that might help us to track this problem
down? In particular, if applicable, can you provide sample data and sample R
code to reproduce this problem?
###Please fill in###
RKWard is available in many different packagings, and sometimes problems are
specific to one method of installation. How did you install RKWard (which
file(s) did you download)?
###Please fill in###
---Session Info---
-- Frontend --
RKWard version: 0.7.1z+0.7.2+devel1
KDE Frameworks version (runtime): 5.67.0
KDE Frameworks version (compile time): 5.66.0
Qt version (runtime): 5.13.2
Local config directory: /home/adleyvong/.config
RKWard storage directory: /home/adleyvong/.rkward/
Backend version (as known to the frontend): 3.6.2
Debug message file (this may contain relevant diagnostic output in case of
trouble):
/tmp/rkward.frontend
-- Backend --
Debug message file (this may contain relevant diagnostic output in case of
trouble):
/tmp/rkward.rbackend
R version (compile time): 3.6.2 (2019-12-12 r77560)
R runtime session info:
R version 3.6.2 (2019-12-12)
Platform: x86_64-redhat-linux-gnu (64-bit)
Running under: Fedora 31 (Workstation Edition)
Matrix products: default
BLAS: /usr/lib64/R/lib/libRblas.so
LAPACK: /usr/lib64/R/lib/libRlapack.so
locale:
[1] LC_CTYPE=en_US.UTF-8 LC_NUMERIC=C
[3] LC_TIME=en_US.UTF-8 LC_COLLATE=en_US.UTF-8
[5] LC_MONETARY=en_US.UTF-8 LC_MESSAGES=en_US.UTF-8
[7] LC_PAPER=en_US.UTF-8 LC_NAME=en_US.UTF-8
[9] LC_ADDRESS=en_US.UTF-8LC_TELEPHONE=en_US.UTF-8
[11] LC_MEASUREMENT=en_US.UTF-8LC_IDENTIFICATION=en_US.UTF-8
attached base packages:
[1] stats graphics grDevices utils datasets methods base
other attached packages:
[1] rkward_0.7.2
loaded via a namespace (and not attached):
[1] compiler_3.6.2 tools_3.6.2
--
You are receiving this mail because:
You are watching all bug changes.
[ktimetracker] [Bug 417988] Columns displayed do not match configuration
https://bugs.kde.org/show_bug.cgi?id=417988 Alexander Potashev changed: What|Removed |Added Resolution|--- |FIXED Latest Commit||https://commits.kde.org/kti ||metracker/ddc87a47089b900ee ||1c62be10b23d0d4bb2361f1 Status|CONFIRMED |RESOLVED --- Comment #3 from Alexander Potashev --- Git commit ddc87a47089b900ee1c62be10b23d0d4bb2361f1 by Alexander Potashev. Committed on 24/02/2020 at 22:01. Pushed by aspotashev into branch 'master'. TaskView: Change visibility of table columns after the view is connected to model Otherwise setColumnHidden() has no effect. M +1-1src/taskview.cpp https://commits.kde.org/ktimetracker/ddc87a47089b900ee1c62be10b23d0d4bb2361f1 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 414396] KCM can't read settings file (kde_settings.conf)
https://bugs.kde.org/show_bug.cgi?id=414396 --- Comment #38 from Ben --- I would like to say this from the perspective of a user. First, if I select a theme and click on "Apply", my preset theme will no longer be displayed the next time systemettings5 is started. I always see the theme Back-To-Black-v.2. As a user, I have to assume that the theme setting inside systemsettings5 is not working properly. But on the other hand, I can start with the selected theme. Copying /etc/sddm.conf.d/kde_settings.conf to /etc/sddm.conf repairs it. Second, from the perspective of the config files. There seems to be a bigger problem with the config files. Because if the /etc/sddm.conf file is empty, the topic shown in "Startup and Shutdown" is not what I configured. Over time, I have had to learn that copying it is always better because having it twice is the only way to make it run correctly. I hope this helps. Thank you for listening. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 418590] New: Displaying fields and Sorting items in a Tag Folder
https://bugs.kde.org/show_bug.cgi?id=418590 Bug ID: 418590 Summary: Displaying fields and Sorting items in a Tag Folder Product: dolphin Version: 19.12.3 Platform: Neon Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: tagwer...@innerjoin.org CC: kfm-de...@kde.org Target Milestone: --- SUMMARY: In Dolphin, when opening a folder, it's possible to pick and choose columns to be displayed and to be able to sort items based on that information. When opening a tag folder (for example tags:/mytag), fields that are set in the extended attributes can be selected as columns but many of these fields are not populated For example, comments are shown in a detailed list view, of say, ~/Pictures. However, if the files are tagged, say with 'mytag', and Dolphin is displaying tags:/mytag, the comments are not displayed. Similarly for Tags (see Bug 356062), Path, Rating, Link Destination. The implication is that if these properties are not displayed, then sorting on these values is not possible. STEPS TO REPRODUCE: 1. Create three folders under ~/Pictures: 2020-02-10, 2020-02-11 and 2020-02-12 2. Create image files in these folders, imagine they have come from a couple of different cameras that give their images different format names. Here: ~/Pictures/2020-02-10/image1.png ~/Pictures/2020-02-11/picture1.png ~/Pictures/2020-02-11/picture2.png ~/Pictures/2020-02-12/image2.png 3. Tag all these images with a tag "mytag" 4. Open the tags:/mytag/ folder and attempt to sort the images in the above sequence OBSERVED RESULTS: There's not an option that will necessarily do this. 'Sort by name' will order the 'image' files before the 'picture' files, a 'sort by create date' sorts by the time the file was copied onto (or subsequently edited on) the computer, not all files have EXIF data. DESIRED STATE: The desired state is that files selected by a tag can be sorted by their (on filesystem) directory/filename. Ideally it should be possible to display a 'canonical directory/filename'. There are options to show the 'Path' or 'Link Destination' but these are not populated, I assume 'Path' ought to show the 'tags:/mytag' and 'Link Destination' potentially ~/Pictures/2020-02-10/image1.png. I've not found any documentation that defines that. SOFTWARE/OS VERSIONS: Dolphin 19.12.3 from Neon 5.18 KDE Plasma 5.18.2 KDE Frameworks 5.67.0 Qt 5.14.1 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 385726] Add Support For Apple Live Photos
https://bugs.kde.org/show_bug.cgi?id=385726 --- Comment #16 from Nick Cross --- I would love to see support for embedded movies within jpg (be it Apple Live Photo, Google Photo or Samsung Motion Photos). I see this has been reopened and couldn't see any other tickets for Google/Samsung support. I can supply sample Samsung images from my S10 if needed :-) -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 385726] Add Support For Apple Live Photos
https://bugs.kde.org/show_bug.cgi?id=385726 Nick Cross changed: What|Removed |Added CC||k...@goots.org -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 418589] When setting the date to format "ddd d", the font size becomes excessively large after a reboot
https://bugs.kde.org/show_bug.cgi?id=418589 --- Comment #1 from Paul M --- Created attachment 126660 --> https://bugs.kde.org/attachment.cgi?id=126660&action=edit The date after a reboot -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 418589] New: When setting the date to format "ddd d", the font size becomes excessively large after a reboot
https://bugs.kde.org/show_bug.cgi?id=418589 Bug ID: 418589 Summary: When setting the date to format "ddd d", the font size becomes excessively large after a reboot Product: plasmashell Version: 5.18.1 Platform: Neon Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Digital Clock Assignee: plasma-b...@kde.org Reporter: k...@paulmcauley.com Target Milestone: 1.0 Created attachment 126659 --> https://bugs.kde.org/attachment.cgi?id=126659&action=edit the date as desired I have a 2160p HiDPI display with scaling set to 225%. I have my panel on the left-hand side, and like to display the date in the "ddd d" format. This is shown in the screenshot as I like it in the attached original_date.PNG. However, when I reboot the date then shows as excessively large as in large_date.PNG. SOFTWARE/OS VERSIONS Linux/KDE Plasma: (available in About System) KDE Plasma Version: 5.18.80 / 5.18.2 KDE Frameworks Version: 5.68.0 Qt Version: 5.14.1 -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 418588] Drawer Plasmoid
https://bugs.kde.org/show_bug.cgi?id=418588 Michail Vourlakos changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |NOT A BUG --- Comment #1 from Michail Vourlakos --- I am not interested... -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 418122] Kontact UI in dual-monitor setting
https://bugs.kde.org/show_bug.cgi?id=418122 --- Comment #4 from peter.snauwa...@gmail.com --- Created attachment 126658 --> https://bugs.kde.org/attachment.cgi?id=126658&action=edit What my Kontact window looks like This is what my Kontact window looks like when a second display is attached. -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 418588] New: Drawer Plasmoid
https://bugs.kde.org/show_bug.cgi?id=418588 Bug ID: 418588 Summary: Drawer Plasmoid Product: lattedock Version: git (master) Platform: Kubuntu Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: plasmoid Assignee: mvourla...@gmail.com Reporter: tresdex...@gmail.com Target Milestone: --- Created attachment 126657 --> https://bugs.kde.org/attachment.cgi?id=126657&action=edit Mockup Drawer Plasmoid The idea would be a plasmoid that would work together with the Latte Dock, it would be like an expansive drawer / slot, where you could define an icon, custom label, position it in the dock / panel and define which application shortcuts would be presented in the drawer, it would also be interesting to be able to include other plasmoids in the drawer, such as the system tray. In the example in the image below, I defined a custom icon for the drawer, a label "Linux Creative Suite" and as shortcuts to the contents of the drawer, I added Audacity, Inskape, Gimp and Shotcut, I could also have added Krita, Kdenlive, Scribus , etc ..., when clicking on the custom drawer icon, it would expand, showing its contents. I could create a drawer with the label "Accessories" and inside it put the shortcuts for the application of Calculator, Terminal, Screen Capture Tool, Simple Text Editor, I could create one with the label "LibreOffice" and put all the shortcuts of the suite's applications, you could create one with a label and a custom icon to display the plasmoid system tray, the possibilities would be endless ... -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 418587] New: Assert when using the 'end' key while the zoom widget is focussed.
https://bugs.kde.org/show_bug.cgi?id=418587 Bug ID: 418587 Summary: Assert when using the 'end' key while the zoom widget is focussed. Product: krita Version: git master Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Shortcuts and Canvas Input Settings Assignee: krita-bugs-n...@kde.org Reporter: griffinval...@gmail.com Target Milestone: --- SUMMARY I got this while I tried to press metakey+right, but instead pressed fn+right, meaning the 'end' keycode was invoked. The zoom widget happened to be in focus. This is in the resource branch, btw, but we must be doing something funny here. STEPS TO REPRODUCE 1. focus zoom widget in the statusbar 2. press 'end' 3. get assert. GDB Backtrace = Thread 1 (Thread 0x77f88800 (LWP 10980)): #0 __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:51 #1 0x726e2801 in __GI_abort () at abort.c:79 #2 0x730bacbb in QMessageLogger::fatal(char const*, ...) const () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #3 0x730ba50b in qt_assert_x(char const*, char const*, char const*, int) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x70da925b in QList::operator[] (this=0x60ac6a00, i=21) at /usr/include/x86_64-linux-gnu/qt5/QtCore/qlist.h:568 #5 0x70da7d54 in KoZoomAction::sliderValueChanged (this=0x62ff7830, value=21) at /home/wolthera/krita/src/libs/widgets/KoZoomAction.cpp:224 #6 0x70e38a42 in KoZoomAction::qt_static_metacall (_o=0x62ff7830, _c=QMetaObject::InvokeMetaMethod, _id=17, _a=0x7fffd2f0) at /home/wolthera/krita/build/libs/widgets/kritawidgets_autogen/EWIEGA46WW/moc_KoZoomAction.cpp:173 #7 0x732f4805 in QMetaObject::activate(QObject*, int, int, void**) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x70e3991d in KoZoomWidget::sliderValueChanged (this=0x6334fc00, _t1=21) at /home/wolthera/krita/build/libs/widgets/kritawidgets_autogen/EWIEGA46WW/moc_KoZoomWidget.cpp:204 #9 0x70e394b3 in KoZoomWidget::qt_static_metacall (_o=0x6334fc00, _c=QMetaObject::InvokeMetaMethod, _id=0, _a=0x7fffd4a0) at /home/wolthera/krita/build/libs/widgets/kritawidgets_autogen/EWIEGA46WW/moc_KoZoomWidget.cpp:109 #10 0x732f4805 in QMetaObject::activate(QObject*, int, int, void**) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #11 0x741b655e in QAbstractSlider::valueChanged(int) () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #12 0x741b6bdb in QAbstractSlider::setValue(int) () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #13 0x7410a4e7 in QWidget::event(QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #14 0x7425fcda in QSlider::event(QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #15 0x740c8eac in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #16 0x740d1562 in QApplication::notify(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #17 0x76b79279 in KisApplication::notify (this=0x7fffe120, receiver=0x5f53d090, event=0x7fffdca0) at /home/wolthera/krita/src/libs/ui/KisApplication.cpp:705 #18 0x732c3e38 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #19 0x74127635 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #20 0x740c8eac in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #21 0x740d04b0 in QApplication::notify(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #22 0x76b79279 in KisApplication::notify (this=0x7fffe120, receiver=0x5dc4b470, event=0x7fffdca0) at /home/wolthera/krita/src/libs/ui/KisApplication.cpp:705 #23 0x732c3e38 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #24 0x73893c5b in QGuiApplicationPrivate::processKeyEvent(QWindowSystemInterfacePrivate::KeyEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Gui.so.5 #25 0x738985c5 in QGuiApplicationPrivate::processWindowSystemEvent(QWindowSystemInterfacePrivate::WindowSystemEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Gui.so.5 #26 0x7387279b in QWindowSystemInterface::sendWindowSystemEvents(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Gui.so.5 #27 0x7fffe2d1cdda in ?? () from /usr/lib/x86_64-linux-gnu/libQt5XcbQpa.so.5 #28 0x7fffe9f6f417 in g_main_context_dispatch () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #29 0x7fffe9f6f650 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #30 0x7fffe9f6f6dc in g_mai
[kwin] [Bug 395632] On RX Vega 64, KDE compositor does not run at 144Hz even though monitor refresh rate is set to 144Hz
https://bugs.kde.org/show_bug.cgi?id=395632 edgbla changed: What|Removed |Added CC||edg...@yandex.ru -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 418586] New: Opening cbr files without unrar installed gives a generic error message
https://bugs.kde.org/show_bug.cgi?id=418586 Bug ID: 418586 Summary: Opening cbr files without unrar installed gives a generic error message Product: okular Version: 1.9.2 Platform: Manjaro OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Comicbook backend Assignee: okular-de...@kde.org Reporter: merritt_pub...@outlook.com Target Milestone: --- SUMMARY When opening *.cbr files without unrar installed Okular returns a generic, unhelpful error message. STEPS TO REPRODUCE 1. Open a cbr file when the unrar package is not installed on the system OBSERVED RESULT Okular makes a loud 'DING!' and provides a generic error: Error - Okular Could not open file:///path/to/file.cbr EXPECTED RESULT Expected a helpful error message such as: "This file type requires the unrar package. Please install unrar to view comic books files." SOFTWARE/OS VERSIONS Linux/KDE Plasma: Linux 5.4.22-1-MANJARO KDE Plasma Version: 5.17.5 KDE Frameworks Version: 5.66.0 Qt Version: 5.14.1 ADDITIONAL INFORMATION When I tried to open a cbr file I got this error, and searching led me to a thread with someone who previously had the same issue and a question of "Do you have unrar installed?" - which I tried and it resolved the issue. A simple change to the error message would help immensly and be more user-friendly. Even better would be a button to "Download" that could automatically search for unrar in the package manager, though I realize that could be much more difficult if not impossible. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 391252] Baloo unable to find files in hidden folders
https://bugs.kde.org/show_bug.cgi?id=391252 villene...@arcor.de changed: What|Removed |Added CC||villene...@arcor.de -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 413220] Weird connections among selected areas
https://bugs.kde.org/show_bug.cgi?id=413220 Tymond changed: What|Removed |Added CC||tallboy...@gmail.com --- Comment #3 from Tymond --- *** Bug 418568 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 418568] when working with large files (over 2GB, 32bit float),corruption occurs with selections
https://bugs.kde.org/show_bug.cgi?id=418568 Tymond changed: What|Removed |Added CC||tamtamy.tym...@gmail.com Resolution|--- |DUPLICATE Status|REPORTED|RESOLVED --- Comment #1 from Tymond --- *** This bug has been marked as a duplicate of bug 413220 *** -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 406506] Wish - Show metadata of files stored on locations non-indexed by baloo in details view mode
https://bugs.kde.org/show_bug.cgi?id=406506 hoperidesal...@protonmail.ch changed: What|Removed |Added CC||hoperidesalone@protonmail.c ||h -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 416739] Panel disappears from time to time and after a while re-appears
https://bugs.kde.org/show_bug.cgi?id=416739 --- Comment #11 from Kevin Kaland --- Still present in 5.18.2 on Manjaro (Arch Linux package). -- You are receiving this mail because: You are watching all bug changes.
[KAccounts] [Bug 418567] Google Drive Accounts have Google[number] instead of my Google ID
https://bugs.kde.org/show_bug.cgi?id=418567 --- Comment #1 from Marco Parillo --- Is it possible that this is working as designed, per: https://phabricator.kde.org/D27474 If so, is that the best work-around possible? I preferred the old way with my Google ID instead of Google[random number] -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 269367] There is no way to search in hidden folders now.
https://bugs.kde.org/show_bug.cgi?id=269367 --- Comment #24 from Eridani Rodríguez --- Can confirm that it is STILL IMPOSSIBLE to search in hidden folders from folders on higher hierarchy than the hidden folder in 19.12.3, this means that: - You can search from `/regularF/.hiddenF/` and find `/regularF/.hiddenF/myFile` - But if you search from `/regularF/` Dolphin won't find `/regularF/.hiddenF/myFile`, ever. Unless you explicitly tell Baloo to index either all hidden paths or that specific hidden folder. But that may not be what most people want, hidden folders are hidden because people want them out of their way most of the time. Being "most of the time" the keyword here, you some times need to search in hidden folders, and your file manager should give you an option to do it, even if this option meant using an external program for conducting the task. (For those wondering, installing KFind doesn't make a difference, although you at least get a handy button to launch KFind.) System info: --- Operating System: KDE neon 5.18 KDE Plasma Version: 5.18.2 KDE Frameworks Version: 5.67.0 Qt Version: 5.14.1 Kernel Version: 5.3.0-40-generic KDE Applications Version: 19.12.3 Dolphin Version: 19.12.3 --- This bug was marked as SOLVED because of bug https://bugs.kde.org/show_bug.cgi?id=391252 which talks about how is intentional behaviour for Baloo to not index hidden folders by default. While I agree with the thing about Baloo's scope, I don't agree with this bug being a duplicate of that Baloo bug. If KFind integration* is the only plausible solution at this time because Baloo is pretty much unmaintained or because it is out of Baloo's design scope (as noted on the thread cited above); then some steps should be taken to make it a flawless integration. Currently the folder to search from is passed to KFind as "file:///yourFolder/childFolder" and KFind doesn't understand that, it understands however "/yourFolder/childFolder", same for the actual string to search for e.g. "strawberries", KFind needs it to be "*strawberries*" to find something unless you meant an exact name match which most of the times you don't (no idea about blank spaces or weird characters in the search string, but probably need to use some special stuff to handle those cases too). Nothing useful is passed from Dolphin to Catfish either by the way. Currently we have a crippled search in a file manager that allows you to navigate hidden folders but won't let you search in them. In my opinion, this integration should be addressed or Baloo scope should be addressed or in the worst scenario, Dolphin allowing you to view hidden files should be addressed before this bug could be marked as solved. * When I say "KFind integration" is because it was mentioned above and is almost done from my point of view, but I'm just an user and have no idea of the internals that would need to be moved around for it to be a flawless integration. -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 418479] Historical Investment Transactions causes crash
https://bugs.kde.org/show_bug.cgi?id=418479 --- Comment #4 from JAH --- Thanks for the quick reply. I have tried my data using AppImage Kmymoney Vn5.0.8 and problem recurs consistently with: Investment Account A000362 Opened 01/01/2019 Security A000366 (and others A000367 A000368) OpeningDate 04/03/2020 posted to Transaction Date 07/06/2019 I note however that the same posting process (i.e. Transaction Date prior to Security Opening Date) used on another Investment Account has been successful and resulted in the Security Opening Date being reset to the (earlier) Transaction posting date. Also new securities added (using Kmymoney Vn5.0.8) to InvAcct A000362 since do not seem to show the same problem. Since it only affected 4 Securities for me I have worked around the problem by manually changing those Security's Opening Date via SQL but if you think it worth investigating, I have anonymised my data. Thanks again for your consideration. -- You are receiving this mail because: You are watching all bug changes.
[kalarm] [Bug 417108] Command line operation fails
https://bugs.kde.org/show_bug.cgi?id=417108 --- Comment #7 from David Jarvie --- Sorry, of course if KAlarm is already running before you enter those commands, they will all run without waiting. Anyway, when I do the same, all the commands run successfully. Did the crash occur when you ran these commands, or at some other time? -- You are receiving this mail because: You are watching all bug changes.
[amarok] [Bug 416184] Przeglądarka wyłącza się kiedy zmieniam wolumin dysku z C: na na przykład H: nie widzi potem żadnych woluminów
https://bugs.kde.org/show_bug.cgi?id=416184 andreas.sturmlech...@gmail.com changed: What|Removed |Added Alias|amarok, brownser, file, | |wyłącza | CC||andreas.sturmlechner@gmail. ||com -- You are receiving this mail because: You are watching all bug changes.
[kalarm] [Bug 417108] Command line operation fails
https://bugs.kde.org/show_bug.cgi?id=417108 --- Comment #6 from David Jarvie --- If you pasted those lines into konsole, each line would wait until you quitted KAlarm, before continuing on to the next line. Did you actually quit KAlarm 6 times? If not, what exactly did you paste into konsole? Did you get a crash trace when KAlarm crashed? It isn't possible to investigate a crash without this, unless the crash is easily reproduceable. -- You are receiving this mail because: You are watching all bug changes.
[kdelibs] [Bug 58647] Wrong accelerators specified in Info pages
https://bugs.kde.org/show_bug.cgi?id=58647 --- Comment #12 from Shinjo Park --- Created attachment 126656 --> https://bugs.kde.org/attachment.cgi?id=126656&action=edit Dolphin's Korean screenshot, only one accelerator key is allocated but there is no incorrect accelerator keys. -- You are receiving this mail because: You are watching all bug changes.
[kdelibs] [Bug 58647] Wrong accelerators specified in Info pages
https://bugs.kde.org/show_bug.cgi?id=58647 --- Comment #11 from Shinjo Park --- Created attachment 126655 --> https://bugs.kde.org/attachment.cgi?id=126655&action=edit Discover's Korean screenshot, where accelerator keys are misallocated -- You are receiving this mail because: You are watching all bug changes.
[kdelibs] [Bug 58647] Wrong accelerators specified in Info pages
https://bugs.kde.org/show_bug.cgi?id=58647 Shinjo Park changed: What|Removed |Added CC||k...@peremen.name --- Comment #10 from Shinjo Park --- Although the original bug is 17 years old, it is still relevant. The bug seems to be at least fixed in the QWidgets based applications, but QML based applications seems to have the bug. Attached here is configuration dialog of Dolphin and update dialog of Discover, using QWidgets and QML respectively. In Dolphin's dialog, only the translated message of "Switch between split views panes with tab key" has its accelerator key assigned, as only that item of the configuration dialog has alphabet. All other texts are using 100% Hangul, so no accelerator keys were added. That actually hurts usability but I think this should be discussed in another bug. On the other hand, in Discover's update dialog, accelerator keys are allocated to composed Hangul which could not be used as an accelerator key. Only the translated message of "Plasma Addons" has alphabets in this case. All others are using 100% Hangul, but accelerator keys are nevertheless allocated. This is clearly a bug. -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 417730] Gwenview doesn't realise it's just opened an image from a "Tag" folder
https://bugs.kde.org/show_bug.cgi?id=417730 --- Comment #4 from tagwer...@innerjoin.org --- (In reply to tagwerk19 from comment #2) > Yes, seems to be the case. Whups, that might have been that was ambiguous... as I read the 'execve' call in the strace, dolphin uses the filesystem directory, not the tags:/ -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 408841] Double clicking a file in filesystem panel doesn't set the input focus to the editor
https://bugs.kde.org/show_bug.cgi?id=408841 John Hayes changed: What|Removed |Added Assignee|kdevelop-bugs-n...@kde.org |jdhayes.li...@gmail.com CC||jdhayes.li...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[konqueror] [Bug 131336] Perfomance: Wikimedia pages are rendered too slow
https://bugs.kde.org/show_bug.cgi?id=131336 Shinjo Park changed: What|Removed |Added CC||k...@peremen.name --- Comment #10 from Shinjo Park --- Hello, Is this bug still exist in the recent version of KHTML? We can close the bug if this bug is no longer relevant. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 416728] Konsole with multiple tabs pops up an N open terminals warning on logout or shutdown.
https://bugs.kde.org/show_bug.cgi?id=416728 Johannes Zarl-Zierl changed: What|Removed |Added CC||johan...@zarl-zierl.at -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 416618] Allow selection of default torrent client
https://bugs.kde.org/show_bug.cgi?id=416618 --- Comment #13 from Christoph Feck --- Yes, UX can be improved. But that doesn't justify why torrent files need to be treated specially compared to, say, Office or Blender files. KTorrent for example, registers itself as a handler for torrent files, so if you have it installed, it works automatically. If other applications also register as a handler, then the new UI could automatically display combo boxes for all file types that have multiple handling applications registered. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 418553] half symbol is hidden
https://bugs.kde.org/show_bug.cgi?id=418553 --- Comment #5 from Christoph Feck --- Only monospaced fonts are supported in Konsole. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 418585] New: Detect an archive instead of executable ffmpeg in Render Animation dialog
https://bugs.kde.org/show_bug.cgi?id=418585 Bug ID: 418585 Summary: Detect an archive instead of executable ffmpeg in Render Animation dialog Product: krita Version: 4.2.8 Platform: MS Windows OS: MS Windows Status: REPORTED Severity: normal Priority: NOR Component: Animation Assignee: krita-bugs-n...@kde.org Reporter: tamtamy.tym...@gmail.com Target Milestone: --- SUMMARY Our Windows users get really confused about how to get the correct ffmpeg. This needs a step-by-step tutorial (with "how to get a release version instead of a development build" and "how to extract the executable") on Krita Manual, but it would be good to also detect whether someone try to give Krita the .zip file instead of .exe (or just ffmpeg on Linux). STEPS TO REPRODUCE 1. Download ffmpeg from the https://ffmpeg.zeranoe.com/builds/ site, especially the already suggested one (development build) to see the purpose of Additional Notes 2. Note you downloaded a .zip file 3. Provide the path to the .zip file as a path to ffmpeg in Krita 4. Try to render an animation OBSERVED RESULT No warning, failed rendering, users are confused since they downloaded ffmpeg exactly as the Krita Manual says. EXPECTED RESULT If the filename ends with ".zip", there should be a warning with a short instruction, maybe something like: "The ffmpeg file you provided the path to has a '.zip' extension. If you encounter issues while rendering, check if the file is an archive, extract all files and point Krita into bin/ffmpeg.exe file inside the folder with files from the archive" or something similar. ADDITIONAL INFORMATION Would be awesome to check if the ffmpeg used is a release build or not... I believe most Windows users use the development build now -.- since that's what ffmpeg suggests by default... Maybe not a warning, but some kind of [!] icon next to the ffmpeg path with a tooltip explaining why? SOFTWARE/OS VERSIONS Windows: 10 Krita 4.2.8 -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 417730] Gwenview doesn't realise it's just opened an image from a "Tag" folder
https://bugs.kde.org/show_bug.cgi?id=417730 Christoph Feck changed: What|Removed |Added CC||fa...@kde.org --- Comment #3 from Christoph Feck --- Desktop file says %U, so it is expected that Gwenview can open any URLs. Not sure if virtual URL protocols like tags:/, desktop:/, or trash:/ need to be specified separately in the desktop file. The 'Protocols' key is deprecated. Needs input from a KIO developer; adding David. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 417929] Crash in KFileItemModel::expandedParentsCount() while opening folders in tree view and deleting them
https://bugs.kde.org/show_bug.cgi?id=417929 Alex Dănilă changed: What|Removed |Added CC||nuor...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 418584] New: Can't use 2+ webdav remotes
https://bugs.kde.org/show_bug.cgi?id=418584 Bug ID: 418584 Summary: Can't use 2+ webdav remotes Product: dolphin Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: major Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: alexlon...@gmail.com CC: kfm-de...@kde.org Target Milestone: --- SUMMARY Once you open a WebDAV remote server in Dolphin you can't open any other WebDAV server: Dolphin will always show the first WebDAV server you connected to. The only way to switch server is logging out and relognin in Plasma session. For example: you open a WebDAV server with al...@server.org and everything is OK, then you open b...@server.org and you still see Alice's files, no error message is given, even the path in Dolphin's address bar says you are seeing Bob folders while you are instead browsing Alice's ones. This is a severe bug with security implications because the user can't tell he is in the wrong folder in any way but recognizing what he see is not the folder he was looking for. SOFTWARE/OS VERSIONS Linux/KDE Plasma: KDE Neon 18.04 (available in About System) KDE Plasma Version: 5.18.2 KDE Frameworks Version: 5.67 Qt Version: 5.14.1 -- You are receiving this mail because: You are watching all bug changes.
[KEXI] [Bug 418582] Kexi form design colour choices overidden in current Manjaro
https://bugs.kde.org/show_bug.cgi?id=418582 Ian Balchin changed: What|Removed |Added Summary|Kexi form design colour |Kexi form design colour |choices not adhered to in |choices overidden in |current Manjaro |current Manjaro --- Comment #1 from Ian Balchin --- 1. For 'Schemes' read 'Themes'. Not sure how to edit submitted bug, perhaps that is not permitted? 2. I can actually change some things, but surely the whole point of designing your form with colours and fonts &c is that is what you will get. Themes and other ways of changing such things as borders, tab and button colours, should not override the designed form choices. -- You are receiving this mail because: You are watching all bug changes.
[krecipes] [Bug 418583] New: Connects to mysql database, crashes krecipes when i view recipes, signal: Segmentation fault (11)
https://bugs.kde.org/show_bug.cgi?id=418583 Bug ID: 418583 Summary: Connects to mysql database, crashes krecipes when i view recipes, signal: Segmentation fault (11) Product: krecipes Version: unspecified Platform: Ubuntu Packages OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: johnboiscl...@gmail.com Target Milestone: --- Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f5e503a6840 (LWP 15974))] Thread 2 (Thread 0x7f5e49971700 (LWP 15981)): #0 0x7f5e55e32729 in __GI___poll (fds=0x7f5e440052c0, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7f5e54d6dbf6 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f5e54d6dd1c in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f5e570ee22e in QEventDispatcherGlib::processEvents(QFlags) () from /lib/x86_64-linux-gnu/libQtCore.so.4 #4 0x7f5e570bc12f in QEventLoop::processEvents(QFlags) () from /lib/x86_64-linux-gnu/libQtCore.so.4 #5 0x7f5e570bc495 in QEventLoop::exec(QFlags) () from /lib/x86_64-linux-gnu/libQtCore.so.4 #6 0x7f5e56fab549 in QThread::exec() () from /lib/x86_64-linux-gnu/libQtCore.so.4 #7 0x7f5e5709c1c3 in ?? () from /lib/x86_64-linux-gnu/libQtCore.so.4 #8 0x7f5e56fade3c in ?? () from /lib/x86_64-linux-gnu/libQtCore.so.4 #9 0x7f5e5480b182 in start_thread (arg=) at pthread_create.c:486 #10 0x7f5e55e3eb1f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 1 (Thread 0x7f5e503a6840 (LWP 15974)): [KCrash Handler] #6 Yield::Private::Private (this=0x55d09cdcbba0) at /home/jib9119/Downloads/krecipes/src/datablocks/yield.cpp:16 #7 Yield::operator= (this=this@entry=0x55d09cdffaa8, other=...) at /home/jib9119/Downloads/krecipes/src/datablocks/yield.cpp:50 #8 0x55d09be963ea in Recipe::operator= (this=0x55d09cdffaa0) at /home/jib9119/Downloads/krecipes/src/datablocks/recipe.h:26 #9 RecipeDB::loadRecipe (this=, recipe=0x55d09cdffaa0, items=items@entry=59647, id=id@entry=0) at /home/jib9119/Downloads/krecipes/src/backends/recipedb.cpp:611 #10 0x55d09beea997 in RecipeInputDialog::loadRecipe (this=0x55d09cdaf190, recipeID=recipeID@entry=0) at /home/jib9119/Downloads/krecipes/src/dialogs/recipeinput/recipeinputdialog.cpp:192 #11 0x55d09be87ca0 in KrecipesView::actionRecipe (this=this@entry=0x55d09cb8a3e0, recipeID=0, action=action@entry=1) at /home/jib9119/Downloads/krecipes/src/krecipesview.cpp:804 #12 0x55d09be880f7 in KrecipesView::editRecipe (this=0x55d09cb8a3e0) at /usr/include/qt4/QtCore/qlist.h:472 #13 KrecipesView::editRecipe (this=0x55d09cb8a3e0) at /home/jib9119/Downloads/krecipes/src/krecipesview.cpp:1253 #14 0x55d09be88545 in KrecipesView::qt_static_metacall (_o=, _id=, _a=, _c=) at /home/jib9119/Downloads/krecipes/build/src/krecipesview.moc:144 #15 0x7f5e570d1f70 in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) () from /lib/x86_64-linux-gnu/libQtCore.so.4 #16 0x7f5e570d1f70 in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) () from /lib/x86_64-linux-gnu/libQtCore.so.4 #17 0x7f5e56aa8632 in QAbstractButton::clicked(bool) () from /lib/x86_64-linux-gnu/libQtGui.so.4 #18 0x7f5e567ddc33 in ?? () from /lib/x86_64-linux-gnu/libQtGui.so.4 #19 0x7f5e567defe4 in ?? () from /lib/x86_64-linux-gnu/libQtGui.so.4 #20 0x7f5e567df0f4 in QAbstractButton::mouseReleaseEvent(QMouseEvent*) () from /lib/x86_64-linux-gnu/libQtGui.so.4 #21 0x7f5e568a50aa in QToolButton::mouseReleaseEvent(QMouseEvent*) () from /lib/x86_64-linux-gnu/libQtGui.so.4 #22 0x7f5e56459930 in QWidget::event(QEvent*) () from /lib/x86_64-linux-gnu/libQtGui.so.4 #23 0x7f5e5640303c in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQtGui.so.4 #24 0x7f5e5640a136 in QApplication::notify(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQtGui.so.4 #25 0x7f5e57df1e3a in KApplication::notify(QObject*, QEvent*) () from /lib/libkdeui.so.5 #26 0x7f5e570bd8ad in QCoreApplication::notifyInternal(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQtCore.so.4 #27 0x7f5e5640973d in QApplicationPrivate::sendMouseEvent(QWidget*, QMouseEvent*, QWidget*, QWidget*, QWidget**, QPointer&, bool) () from /lib/x86_64-linux-gnu/libQtGui.so.4 #28 0x7f5e56487452 in ?? () from /lib/x86_64-linux-gnu/libQtGui.so.4 #29 0x7f5e56486ce3 in QApplication::x11ProcessEvent(_XEvent*) () from /lib/x86_64-linux-gnu/libQtGui.so.4 #30 0x7f5e564b0592 in ?? () from /lib/x86_64-linux-gnu/libQtGui.so.4 #31 0x7f5e54d6d9ee in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #32 0x7f5e54d6dc88 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #33 0x7f5e54d6dd1
[KEXI] [Bug 418582] New: Kexi form design colour choices not adhered to in current Manjaro
https://bugs.kde.org/show_bug.cgi?id=418582 Bug ID: 418582 Summary: Kexi form design colour choices not adhered to in current Manjaro Product: KEXI Version: unspecified Platform: Manjaro OS: Linux Status: REPORTED Severity: major Priority: NOR Component: Forms Assignee: kexi-b...@kde.org Reporter: in...@fables.co.za CC: a...@piggz.co.uk, in...@fables.co.za Target Milestone: --- Created attachment 126653 --> https://bugs.kde.org/attachment.cgi?id=126653&action=edit This shows a query that is illegible due to contrasting colour banding SUMMARY When Kexi is run under current Manjaro the design of the forms, particularly referring to colour, is not adhered to. STEPS TO REPRODUCE 1. Newly install Manjaro from downloaded iso 2. Newly install kexi from within Manjaro using Pamac with all dependencies 3. Connect to database 4. Open a form 5. Open a table as well 6. Open a query as well 7. Compare colour schemes to Kexi running on other platforms from same server OBSERVED RESULT The form colour scheme reflects something very different from my own design (a more conventional style with off-white background, white fields with black text). Queries (and Tables) which present tabular data are illegible with dark/light bands with dark text. Thus data on alternate lines is thus not legible. I particularly note that one form does not even show the same scheme as other forms. Looking in Design Mode, the hex numbers for the colours of fields, foreground &background, &c. reflect what is on the screen, not what the stored designs from the server should contain. EXPECTED RESULT Visual effect should be in keeping with Kexi running on other machines which reflect the colour design choices made long ago. SOFTWARE/OS VERSIONS Linux/Manjaro 18.1.5 Xfce build (as shown at download) OR, now, Linux/Manjaro 18.1.5 Cinnamon build (as shown at download) $ inxi gives Kernel: 5.4.18-1-MANJARO x86_64 Kexi 3.2.0 KDE Frameworks Version: 5.66.0 Qt Version: 5.14.1 HARDWARE HP Pavilion dv7 Notebook PC ADDITIONAL INFORMATION 1. This same version of Kexi running on updated but earlier Manjaro version 17 Xfce build $ inxi gives Kernel: 4.14.170-1-MANJARO x86_64 Change of Manjaro 'Schemes' does not improve matters, Qt5 settings do not seem to offer anything appropriate, and the Qt5 style sheets cause Kexi to crash -end- inksi (Ian) -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 414396] KCM can't read settings file (kde_settings.conf)
https://bugs.kde.org/show_bug.cgi?id=414396 --- Comment #37 from Filip Fila --- Can you tell us again in one or two short sentences what the problem is? -- You are receiving this mail because: You are watching all bug changes.
[kalarm] [Bug 417108] Command line operation fails
https://bugs.kde.org/show_bug.cgi?id=417108 --- Comment #5 from dolge...@informatik.uni-erlangen.de --- Yes, commands were submitted by pasting this block of lines into konsole, i.e. as if they were run as a batch file. An additional observation, the kalarm GUI window crashed (and system tray icon vanished), and at least on the surface, this does not look very like a clean process, and in any case not like the previous functionality. However, I did not watch the process list. As I am elsewhere on an older plasma version at the moment, I can take a deeper look on it next week. So long! -- You are receiving this mail because: You are watching all bug changes.
