[krita] [Bug 409627] Implement a Blending Mode corresponding to SAI's Luminosity/Shine mode
https://bugs.kde.org/show_bug.cgi?id=409627 --- Comment #6 from Tyson Tan --- (In reply to Tymond from comment #4) > Created attachment 121532 [details] > Screenshot of the workaround + new mode > > This is the result of my work for now. > > On the left, you can see the workaround with a group that has a black layer > on Normal mode (let's call it "workaround middle layer"), then a layer with > the new color in Normal mode (let's call it "workaround top layer"), and > then the whole group is in Addition mode (let's call it "workaround group"). > Right side is my new blending mode. Color values are just the same, I > checked it. > > I have a question how this blending mode should behave while being on a > layer that has a lower opacity than 50%. > > On the right side of the screenshot you can see two rows of smaller > yellowish-whitish circles. The first row is compiled out of 9 circles > painted with 20, 50, 40 etc. to 100% of opacity. The second one is the same > layer, but the opacity of the layer is 50%. As you can see, the brightest > circle on the layer is yellow and looks the same as 50% opacity circle in > the top row. > > On the left side there are two rows under the first "reference" one - first > one is when you lower the opacity of the "workaround top layer" to 50%. The > second one is when you lower the opacity of the "workaround group" to 50%. > The first row has values identical to what you can get in the new blending > mode. The second one is an example of how I can make it behave. > > The question is, whether you think it should behave (after lowering opacity > of the layer) like the second small circle row or like the third one? What > about making a transparency mask? (If I leave it as it is, it will be always > consistent; I'm just not sure if it's what is expected. This is the first > blending mode that uses alpha for something else than just blending two > output colors together, here we calculate the result color using the alpha > value). If you don't have a preference, please tell me so, too. > > Another question: do you have an access to SAI or Photoshop? I need to know > what the value of the color is if you put a layer of color (10, 100, 200) in > 30% and on top of that color (250, 200, 150) in 50% in the Luminosity (SAI) > blending mode. Workaround don't work at all on that example and I think my > blending mode can have "incorrect" colors there. Hi Tymond, Thank you for helping us with the new blending mode! I'm very busy at the moment so I cannot do the tests right away. I did secure access to PS and SAI again, and I will let you know about the result. I cannot fully understand what you were saying by a glance, so please give me some time. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 409478] Samsung Notebook 9 Pro S Pen not drawing on canvas
https://bugs.kde.org/show_bug.cgi?id=409478 --- 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 409485] Kwin krasch after suspend to memory
https://bugs.kde.org/show_bug.cgi?id=409485 --- 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 409476] kwin crashs sometimes when you switch between virtual desktop
https://bugs.kde.org/show_bug.cgi?id=409476 --- 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.
[kmymoney] [Bug 408833] Receiving import unable to parse error message when using AppImage stable or nightly build
https://bugs.kde.org/show_bug.cgi?id=408833 --- Comment #11 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.
[ksirk] [Bug 409435] KsirK crashing on exit
https://bugs.kde.org/show_bug.cgi?id=409435 --- 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.
[drkonqi] [Bug 359301] DrKonqi refuses to report bugs against ksmserver
https://bugs.kde.org/show_bug.cgi?id=359301 --- 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.
[kdenlive] [Bug 378953] Effect "Freeze" stops working after overlay
https://bugs.kde.org/show_bug.cgi?id=378953 --- Comment #11 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.
[kpat] [Bug 408828] KPatience no reproduce el sonido que avisa por abandonar la partida y que quedará registrada como partida perdida.
https://bugs.kde.org/show_bug.cgi?id=408828 --- Comment #4 from Bug Janitor Service --- Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 395476] The minimum window size of System Settings is too big for a 1366x768 screen
https://bugs.kde.org/show_bug.cgi?id=395476 Nate Graham changed: What|Removed |Added Keywords||usability CC||n...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 409976] New: krita left click drag layer not working
https://bugs.kde.org/show_bug.cgi?id=409976 Bug ID: 409976 Summary: krita left click drag layer not working Product: krita Version: 4.2.3 Platform: MS Windows OS: MS Windows Status: REPORTED Severity: normal Priority: NOR Component: Layer Stack Assignee: krita-bugs-n...@kde.org Reporter: dragonnetst...@gmail.com Target Milestone: --- SUMMARY At any given moment the left mouse button doesn't drag a layer to a new spot, but attempts to drag the entire field of Layers within the docker/tab. Highly impractical compared to previous iterations of Krita, where it was simply left click > able to drag and drop. Especially unhandy as I often drag layers with pen tool, which uses only left click. STEPS TO REPRODUCE 1. Open any document in Krita 4.2.3 2. Hold down left click over an existing layer in layer tab/docker 3. Attempt to drag layer up or down the row of layers in the docker 4. Not happening, layer area (in Docker below the 'opacity' bar) gets dragged until left mouse is let go, and reverts to normal position (so NOT the entire Docker) OBSERVED RESULT Where Krita used to function properly on this left click > drag layer. It now attempts to drag the entire field of layers. (Everything below "opacity") This effect can also be found when scrolling through settings > Keyboard Shortcuts > left click and hold on one of the options in the 'Shortcuts" tab and then drag it up or down. In both cases a 'hold' hand appears in stead of the cursor, and the area gets dragged to the appointed side, only to revert to it's original position upon release of the left mouse button. EXPECTED RESULT just a left click, as in all previous Krita editions. (Last one used was 4.1.7) In the Layers left click+hold+drag I expect Krita to pick up the layer and drag it where I let it go. SOFTWARE/OS VERSIONS Windows: 10 10.0.17763 Build 17763 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.
[Discover] [Bug 409910] Sometimes Plasma shows several notifications from kded5 after I open Discover and close it immediately
https://bugs.kde.org/show_bug.cgi?id=409910 Nate Graham changed: What|Removed |Added CC||n...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 408633] thin vertical line when wallpaper is scaled and cropped
https://bugs.kde.org/show_bug.cgi?id=408633 Nate Graham changed: What|Removed |Added Target Milestone|--- |1.0 Component|general |Image Wallpaper Assignee|plasma-b...@kde.org |notm...@gmail.com CC||n...@kde.org, ||plasma-b...@kde.org Product|Plasma Workspace Wallpapers |plasmashell -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 408052] Auto precision does not seem to update on brush size Change
https://bugs.kde.org/show_bug.cgi?id=408052 --- Comment #2 from vanyossi --- I can confirm this does indeed happen. Precision level is only ever updated when the "auto" checkbox is toggled, setAutoPrecision () is called, in no other situation the set setAutoPrecision is called. -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 409914] Circular *refresh* and update-* icons have arrows that are facing in the wrong direction
https://bugs.kde.org/show_bug.cgi?id=409914 --- Comment #7 from Nate Graham --- Git commit 4e35b61a83fb5a08c8350713dbdc3461003e600e by Nate Graham. Committed on 19/07/2019 at 02:40. Pushed by ngraham into branch 'master'. Update refresh and restart icons to reflect new breeze-icons versions Summary: Like D22534, but for the Plasma theme. Reviewers: #vdg, ndavis Reviewed By: #vdg, ndavis Subscribers: kde-frameworks-devel Tags: #frameworks Differential Revision: https://phabricator.kde.org/D22541 M +32 -36 src/desktoptheme/breeze/icons/system.svg M +21 -81 src/desktoptheme/breeze/icons/view.svg https://commits.kde.org/plasma-framework/4e35b61a83fb5a08c8350713dbdc3461003e600e -- You are receiving this mail because: You are watching all bug changes.
[ark] [Bug 409975] New: Large memory usage when extracting multiple, large zip files
https://bugs.kde.org/show_bug.cgi?id=409975 Bug ID: 409975 Summary: Large memory usage when extracting multiple, large zip files Product: ark Version: 19.04.2 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: elvis.angelac...@kde.org Reporter: johnjohn...@gmail.com CC: rthoms...@gmail.com Target Milestone: --- SUMMARY I try to extract tens of large zip files with KDE dolphin,and each zip is 1~2 GB after extracted (by selecting them in dolphin right -> click extract and detect subfolder). Ark ends up exhausting the 16 GB memory in my computer during the extraction. OBSERVED RESULT Ark uses up all of my 16 GB memory during extraction of multiple files. EXPECTED RESULT Ark should not use memory larger than one file. 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 409974] New: Can't make the 'cumulative undo' work
https://bugs.kde.org/show_bug.cgi?id=409974 Bug ID: 409974 Summary: Can't make the 'cumulative undo' work Product: krita Version: 4.2.2 Platform: MS Windows OS: MS Windows Status: REPORTED Severity: normal Priority: NOR Component: Usability Assignee: krita-bugs-n...@kde.org Reporter: acc4commissi...@gmail.com Target Milestone: --- SUMMARY I've tried many different settings but there is no merging at my Undo History Docker. 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.
[yakuake] [Bug 409973] New: Need dual screen support
https://bugs.kde.org/show_bug.cgi?id=409973 Bug ID: 409973 Summary: Need dual screen support Product: yakuake Version: 2.9.9 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: h...@kde.org Reporter: mpar...@ilm.com Target Milestone: --- SUMMARY Hello! I use Yakuake every day at ILM and really like it! I have a rather large number of terminals to manage and would really appreciate it if Yakuake could work with dual screen setups, allowing more terminals to be shown on the second monitor. Currently the options for screen are: "screen 1, screen 2 or at mouse location". Ideally there would be an option like "Unique sessions on all screens". Thanks so much for your consideration! STEPS TO REPRODUCE 1. 2. 3. OBSERVED RESULT EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[LabPlot2] [Bug 407847] Import broken
https://bugs.kde.org/show_bug.cgi?id=407847 --- Comment #8 from Justin --- I finally got craft to compile properly, the fix works perfectly. Thank you! -- You are receiving this mail because: You are watching all bug changes.
[kdiff3] [Bug 407390] kdiff3 fails to compare directories since c607f4352fadd2bf2480920144b867b9b7922604
https://bugs.kde.org/show_bug.cgi?id=407390 michael 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 409967] CSD gtk3 apps have Wayland generic icon in the task switcher
https://bugs.kde.org/show_bug.cgi?id=409967
--- Comment #2 from Patrick Silva ---
totem video player case:
ouput of your command is
[4141048,375] -> xdg_toplevel@32.set_app_id("totem")
.desktop file name: org.gnome.Totem.desktop
--
You are receiving this mail because:
You are watching all bug changes.
[kdiff3] [Bug 407390] kdiff3 fails to compare directories since c607f4352fadd2bf2480920144b867b9b7922604
https://bugs.kde.org/show_bug.cgi?id=407390 michael changed: What|Removed |Added Version Fixed In||1.8.2 Latest Commit||https://cgit.kde.org/kdiff3 ||.git/commit/804997e45675e1e ||a1e86559d11f118d73fca8ce0 --- Comment #7 from michael --- @paolog that appears an unrelated and resolved in 1.8.0 issue see the debian bug. I believe this issue is fixed as of https://cgit.kde.org/kdiff3.git/commit/?h=1.8=804997e45675e1ea1e86559d11f118d73fca8ce0 Could the Timo Gurr please confirm this. -- You are receiving this mail because: You are watching all bug changes.
[kdiff3] [Bug 407390] kdiff3 fails to compare directories since c607f4352fadd2bf2480920144b867b9b7922604
https://bugs.kde.org/show_bug.cgi?id=407390 michael changed: What|Removed |Added Attachment #121608|0 |1 is obsolete|| -- You are receiving this mail because: You are watching all bug changes.
[kdiff3] [Bug 407390] kdiff3 fails to compare directories since c607f4352fadd2bf2480920144b867b9b7922604
https://bugs.kde.org/show_bug.cgi?id=407390 michael changed: What|Removed |Added Attachment #121603|0 |1 is obsolete|| -- You are receiving this mail because: You are watching all bug changes.
[korganizer] [Bug 409972] New: korganizer sends new todo to wrong calendar
https://bugs.kde.org/show_bug.cgi?id=409972 Bug ID: 409972 Summary: korganizer sends new todo to wrong calendar Product: korganizer Version: unspecified Platform: Debian stable OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: todoview Assignee: kdepim-b...@kde.org Reporter: westlake.b...@gmail.com Target Milestone: --- (Korganizer version: 5.9.3) SUMMARY korganizer sends new todo on wrong calendar If a user has more than 1 calendar, and they create a todo (described below), that todo goes to the wrong calendar. Whether a feature or not (new user), the user is not able to change the applied calendar for the new todo. STEPS TO REPRODUCE 1. right-click on calendar event and from context-menu choose to 'create todo' 2. Select a specific calendar 3. check the todo list OBSERVED RESULT The todo does not get created on the specified calendar. Instead the first of available calendars gets the new todo item. Note: a new todo via the "todo view" gets stored in the correct calendar, but not via 'create todo' using the context-menu from calendar events. SOFTWARE/OS VERSIONS Korganizer version: 5.9.3 Linux: Debian 10 Qt Version: 5.x Calendars: Davical server -> 1 caldav server (davical -- using custom https:// connect string) ^ Davical Calendars - 1 account, two calendars Bug occurs using just these two calendars with 1 caldav server. (bug was occurring previously as well with the built-in calendars: when attempting to send a new todo to a caldav server, it was instead being sent to the built-in Personal calendar. The built-in calendars were removed, and the bug was still occurring among the two calendars with the davical server.) -- You are receiving this mail because: You are watching all bug changes.
[umbrello] [Bug 409969] No context menu entry for adding messages to sequence diagram
https://bugs.kde.org/show_bug.cgi?id=409969 --- Comment #3 from Ralf Habacker --- Git commit d12972cc12c17dec182074ab071835f8591b5594 by Ralf Habacker. Committed on 18/07/2019 at 22:54. Pushed by habacker into branch 'Applications/19.08'. After adding message by context menu reset work tool bar to arrow This is necessary because the state of the toolbar, which is now changed via the context menu, is bound to the toolbar. M +4-0umbrello/toolbarstate.h M +1-0umbrello/toolbarstateassociation.cpp M +1-0umbrello/toolbarstatemessages.cpp M +2-0umbrello/umlscene.cpp M +1-1umbrello/umlwidgets/toolbarstateonewidget.cpp https://commits.kde.org/umbrello/d12972cc12c17dec182074ab071835f8591b5594 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 409971] New: Plasma crashes on Wayland when the sound icon in systray is right-clicked
https://bugs.kde.org/show_bug.cgi?id=409971 Bug ID: 409971 Summary: Plasma crashes on Wayland when the sound icon in systray is right-clicked Product: plasmashell Version: master Platform: Neon Packages OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: generic-wayland Assignee: plasma-b...@kde.org Reporter: bugsefor...@gmx.com Target Milestone: 1.0 STEPS TO REPRODUCE 1. start Wayland session 2. click on sound icon in systray 3. click on any hamburger menu 4. while the hamburger menu is open, click on "Audio volume" header 5. right click on sound icon in systray Operating System: KDE neon Unstable Edition KDE Plasma Version: 5.16.80 KDE Frameworks Version: 5.61.0 Qt Version: 5.12.3 Thread 11 (Thread 0x7fefbddfc700 (LWP 4075)): #0 0x7ff022db1bf9 in __GI___poll (fds=0x56255f20c830, nfds=2, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7ff01d0395c9 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7ff01d0396dc in g_main_context_iteration () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7ff01d039721 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7ff01d061195 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7ff0203f46db in start_thread (arg=0x7fefbddfc700) at pthread_create.c:463 #6 0x7ff022dbe88f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 10 (Thread 0x7feff54c3700 (LWP 4059)): #0 0x7ff0203fa9f3 in futex_wait_cancelable (private=, expected=0, futex_word=0x56255b55d7e0) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 __pthread_cond_wait_common (abstime=0x0, mutex=0x56255b55d790, cond=0x56255b55d7b8) at pthread_cond_wait.c:502 #2 __pthread_cond_wait (cond=0x56255b55d7b8, mutex=0x56255b55d790) at pthread_cond_wait.c:655 #3 0x7ff0234c5dbb in QWaitConditionPrivate::wait (deadline=..., this=0x56255b55d790) at thread/qwaitcondition_unix.cpp:146 #4 QWaitCondition::wait (this=, mutex=0x56255b2e89d0, deadline=...) at thread/qwaitcondition_unix.cpp:225 #5 0x7ff0234c60c9 in QWaitCondition::wait (this=this@entry=0x56255b2e89d8, mutex=mutex@entry=0x56255b2e89d0, time=time@entry=18446744073709551615) at thread/qwaitcondition_unix.cpp:208 #6 0x7ff0278176f8 in QSGRenderThreadEventQueue::takeEvent (wait=true, this=0x56255b2e89c8) at scenegraph/qsgthreadedrenderloop.cpp:245 #7 QSGRenderThread::processEventsAndWaitForMore (this=this@entry=0x56255b2e8950) at scenegraph/qsgthreadedrenderloop.cpp:710 #8 0x7ff027817b2a in QSGRenderThread::run (this=0x56255b2e8950) at scenegraph/qsgthreadedrenderloop.cpp:739 #9 0x7ff0234bec72 in QThreadPrivate::start (arg=0x56255b2e8950) at thread/qthread_unix.cpp:361 #10 0x7ff0203f46db in start_thread (arg=0x7feff54c3700) at pthread_create.c:463 #11 0x7ff022dbe88f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 9 (Thread 0x7fefa700 (LWP 4115)): #0 0x7ff0203fa9f3 in futex_wait_cancelable (private=, expected=0, futex_word=0x56255f39ac50) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 __pthread_cond_wait_common (abstime=0x0, mutex=0x56255f39ac00, cond=0x56255f39ac28) at pthread_cond_wait.c:502 #2 __pthread_cond_wait (cond=0x56255f39ac28, mutex=0x56255f39ac00) at pthread_cond_wait.c:655 #3 0x7ff0234c5dbb in QWaitConditionPrivate::wait (deadline=..., this=0x56255f39ac00) at thread/qwaitcondition_unix.cpp:146 #4 QWaitCondition::wait (this=, mutex=0x562560cc2780, deadline=...) at thread/qwaitcondition_unix.cpp:225 #5 0x7ff0234c60c9 in QWaitCondition::wait (this=this@entry=0x562560cc2788, mutex=mutex@entry=0x562560cc2780, time=time@entry=18446744073709551615) at thread/qwaitcondition_unix.cpp:208 #6 0x7ff0278176f8 in QSGRenderThreadEventQueue::takeEvent (wait=true, this=0x562560cc2778) at scenegraph/qsgthreadedrenderloop.cpp:245 #7 QSGRenderThread::processEventsAndWaitForMore (this=this@entry=0x562560cc2700) at scenegraph/qsgthreadedrenderloop.cpp:710 #8 0x7ff027817b2a in QSGRenderThread::run (this=0x562560cc2700) at scenegraph/qsgthreadedrenderloop.cpp:739 #9 0x7ff0234bec72 in QThreadPrivate::start (arg=0x562560cc2700) at thread/qthread_unix.cpp:361 #10 0x7ff0203f46db in start_thread (arg=0x7fefa700) at pthread_create.c:463 #11 0x7ff022dbe88f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 8 (Thread 0x7fefaf7fe700 (LWP 4114)): #0 0x7ff0203fa9f3 in futex_wait_cancelable (private=, expected=0, futex_word=0x56255f22a490) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 __pthread_cond_wait_common (abstime=0x0, mutex=0x56255f22a440, cond=0x56255f22a468) at pthread_cond_wait.c:502 #2 __pthread_cond_wait (cond=0x56255f22a468, mutex=0x56255f22a440)
[kontact] [Bug 409970] New: Kontact segfaults after having cause an important memory hole after having made use of spam filters).
https://bugs.kde.org/show_bug.cgi?id=409970 Bug ID: 409970 Summary: Kontact segfaults after having cause an important memory hole after having made use of spam filters). Product: kontact Version: 5.10.3 Platform: openSUSE RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: staka...@eclipso.eu Target Milestone: --- Application: kontact (5.10.3) Qt Version: 5.9.7 Frameworks Version: 5.55.0 Operating System: Linux 4.12.14-lp151.28.7-default x86_64 Distribution: "openSUSE Leap 15.1" -- Information about the crash: - What I was doing when the application crashed: That was an idling kmail that in the meantime did receive a mail. - Unusual behavior I noticed: Filter runs quite slowly. Amount of memory after this triples maybe hightens up to 5 times the normal amount. May crash the machine. The application did crash after check of mail. - Custom settings of the application: spam is filtered by daemonized spamd instead of pearl. -- Backtrace: Application: Kontact (kontact), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f465c5e6540 (LWP 4071))] Thread 30 (Thread 0x7f46167fc700 (LWP 15605)): #0 0x7f4654a61bdb in pthread_cond_timedwait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7f4649784962 in base::ConditionVariable::TimedWait () at ../../3rdparty/chromium/base/synchronization/condition_variable_posix.cc:117 #2 0x7f464975a749 in base::PosixDynamicThreadPool::WaitForTask () at ../../3rdparty/chromium/base/threading/worker_pool_posix.cc:176 #3 0x7f464975acab in ThreadMain () at ../../3rdparty/chromium/base/threading/worker_pool_posix.cc:86 #4 0x7f464975355b in ThreadFunc () at ../../3rdparty/chromium/base/threading/platform_thread_posix.cc:71 #5 0x7f4654a5b569 in start_thread () from /lib64/libpthread.so.0 #6 0x7f4658f459ef in clone () from /lib64/libc.so.6 Thread 29 (Thread 0x7f451781a700 (LWP 15604)): #0 0x7f4652be7ff4 in g_mutex_unlock () from /usr/lib64/libglib-2.0.so.0 #1 0x7f4652ba16fc in g_main_context_prepare () from /usr/lib64/libglib-2.0.so.0 #2 0x7f4652ba20db in ?? () from /usr/lib64/libglib-2.0.so.0 #3 0x7f4652ba22bc in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #4 0x7f4659a9896b in QEventDispatcherGlib::processEvents (this=0x7f4510004850, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #5 0x7f4659a3d90a in QEventLoop::exec (this=this@entry=0x7f4517819cb0, flags=..., flags@entry=...) at kernel/qeventloop.cpp:212 #6 0x7f465985bdaa in QThread::exec (this=) at thread/qthread.cpp:515 #7 0x7f4659860ced in QThreadPrivate::start (arg=0x55eb72a73290) at thread/qthread_unix.cpp:368 #8 0x7f4654a5b569 in start_thread () from /lib64/libpthread.so.0 #9 0x7f4658f459ef in clone () from /lib64/libc.so.6 Thread 28 (Thread 0x7f4529dad700 (LWP 15600)): #0 0x7f4658f36c98 in read () from /lib64/libc.so.6 #1 0x7f4652be6ca0 in ?? () from /usr/lib64/libglib-2.0.so.0 #2 0x7f4652ba1cb8 in g_main_context_check () from /usr/lib64/libglib-2.0.so.0 #3 0x7f4652ba2150 in ?? () from /usr/lib64/libglib-2.0.so.0 #4 0x7f4652ba22bc in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #5 0x7f4659a9896b in QEventDispatcherGlib::processEvents (this=0x7f451c013b30, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #6 0x7f4659a3d90a in QEventLoop::exec (this=this@entry=0x7f4529daccb0, flags=..., flags@entry=...) at kernel/qeventloop.cpp:212 #7 0x7f465985bdaa in QThread::exec (this=) at thread/qthread.cpp:515 #8 0x7f4659860ced in QThreadPrivate::start (arg=0x55eb72706320) at thread/qthread_unix.cpp:368 #9 0x7f4654a5b569 in start_thread () from /lib64/libpthread.so.0 #10 0x7f4658f459ef in clone () from /lib64/libc.so.6 Thread 27 (Thread 0x7f44faffd700 (LWP 4155)): #0 0x7f4654a618ad in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7f4649755c45 in base::SequencedWorkerPool::Inner::ThreadLoop () at ../../3rdparty/chromium/base/threading/sequenced_worker_pool.cc:1080 #2 0x7f4649756127 in base::SequencedWorkerPool::Worker::Run () at ../../3rdparty/chromium/base/threading/sequenced_worker_pool.cc:611 #3 0x7f4649756ec1 in base::SimpleThread::ThreadMain () at ../../3rdparty/chromium/base/threading/simple_thread.cc:68 #4 0x7f464975355b in ThreadFunc () at ../../3rdparty/chromium/base/threading/platform_thread_posix.cc:71 #5 0x7f4654a5b569 in start_thread () from /lib64/libpthread.so.0 #6 0x7f4658f459ef in clone () from /lib64/libc.so.6 Thread 26 (Thread 0x7f44fb7fe700 (LWP 4154)): #0 0x7f4654a618ad in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7f4649755c45 in
[umbrello] [Bug 409969] No context menu entry for adding messages to sequence diagram
https://bugs.kde.org/show_bug.cgi?id=409969 --- Comment #2 from Ralf Habacker --- Git commit 1091592d3088ff4fba24bfa9528462c074b349c1 by Ralf Habacker. Committed on 18/07/2019 at 22:16. Pushed by habacker into branch 'Applications/19.08'. Fix crash accessing uninitialized memory on loading files ToolBarStateFactory::m_states were not initialized correctly. M +1-1umbrello/toolbarstatefactory.cpp M +2-1umbrello/toolbarstatefactory.h https://commits.kde.org/umbrello/1091592d3088ff4fba24bfa9528462c074b349c1 -- You are receiving this mail because: You are watching all bug changes.
[umbrello] [Bug 409969] No context menu entry for adding messages to sequence diagram
https://bugs.kde.org/show_bug.cgi?id=409969 Ralf Habacker changed: What|Removed |Added Version Fixed In||2.28.80 (KDE Applications ||19.07.80) Status|REPORTED|RESOLVED Latest Commit||https://commits.kde.org/umb ||rello/d3cd29d43f944df3203d8 ||22a7cb2d0d0b547b173 Resolution|--- |FIXED --- Comment #1 from Ralf Habacker --- Git commit d3cd29d43f944df3203d822a7cb2d0d0b547b173 by Ralf Habacker. Committed on 18/07/2019 at 22:05. Pushed by habacker into branch 'Applications/19.08'. Fix 'No context menu entry for adding messages to sequence diagram' With this patch UMLscene::m_pToolBarState and m_pToolBarStateFactory has been moved into class UMLScenePrivate for easier access. The "found" message is added to the context menu if no object line is selected, all other message requires to open the context menu on the widget line of an object. FIXED-IN:2.28.80 (KDE Applications 19.07.80) M +4-0umbrello/menus/listpopupmenu.h M +7-0umbrello/menus/umlscenepopupmenu.cpp M +70 -16 umbrello/umlscene.cpp M +1-2umbrello/umlscene.h M +9-0umbrello/umlwidgets/umlwidget.cpp https://commits.kde.org/umbrello/d3cd29d43f944df3203d822a7cb2d0d0b547b173 -- You are receiving this mail because: You are watching all bug changes.
[umbrello] [Bug 409969] New: No context menu entry for adding messages to sequence diagram
https://bugs.kde.org/show_bug.cgi?id=409969 Bug ID: 409969 Summary: No context menu entry for adding messages to sequence diagram Product: umbrello Version: 2.28.3 (KDE Applications 19.04.3) Platform: Other OS: All Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: umbrello-de...@kde.org Reporter: ralf.habac...@freenet.de Target Milestone: --- For faster adding it would be nice to have context menu entries for adding messages in sequence diagrams. STEPS TO REPRODUCE 1. start umbrello 2. add sequence diagram and two objects 3. move mouse on the line of the first object and open context menu OBSERVED RESULT There are no entries for adding messages EXPECTED RESULT There should be entries for adding messages 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.
[okular] [Bug 408620] Not able to view full PDF
https://bugs.kde.org/show_bug.cgi?id=408620 Albert Astals Cid changed: What|Removed |Added Status|CONFIRMED |RESOLVED Resolution|--- |UPSTREAM --- Comment #8 from Albert Astals Cid --- Oliver of course it's poppler, we don't do any PDF handling. Please report the issue at https://gitlab.freedesktop.org/poppler/poppler/issues -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 409710] Continuous view gets stuck when multiple tabs are used
https://bugs.kde.org/show_bug.cgi?id=409710 Albert Astals Cid changed: What|Removed |Added Resolution|--- |WAITINGFORINFO Status|REPORTED|NEEDSINFO --- Comment #1 from Albert Astals Cid --- Seems to work fine for me. Can someone reproduce on something newer than ancient 1.6.2? Can you try okular flatpak's version? -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 409710] Continuous view gets stuck when multiple tabs are used
https://bugs.kde.org/show_bug.cgi?id=409710 Albert Astals Cid changed: What|Removed |Added Severity|major |normal CC||aa...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 347772] kscreenlocker_greet using 100% cpu on plasma 5
https://bugs.kde.org/show_bug.cgi?id=347772 fle...@users.sourceforge.net changed: What|Removed |Added Status|RESOLVED|REOPENED Ever confirmed|0 |1 Resolution|FIXED |--- CC||fle...@users.sourceforge.ne ||t --- Comment #39 from fle...@users.sourceforge.net --- I still see this issue, completely reproducible. We are always logged in with multiple users on the same console, switching from one account to another with KDE's "Switch User" facility. 1) when user A locks the screen, then using the 'Switch User' button on the locked screen, CPU is normal (~1%). 2) when user A selects the 'Switch User' from the K-menu, then I see /usr/lib/x86_64-linux-gnu/libexec/kscreenlocker_greet --immediateLock --graceTime 5000 --ksldfd 36 shooting up 100%+ on 2 cores (htop reports values from 98% to 133% sometimes). Now if 3 users are logged in and 2 have switched accounts this way (the most convenient actually), then 4+ cores are being maxed out, rendering the machine unusable, and then less experienced users simply reboot it with the reset button (sometimes by pressing it for 25 seconds, needing journal replays on disk paritions) My rig: Kubuntu 18.04 libkscreenlocker5:amd64 5.12.8-0ubuntu0.1 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 409968] New: Text tool gives abort message pop up when trying to edit existing text
https://bugs.kde.org/show_bug.cgi?id=409968 Bug ID: 409968 Summary: Text tool gives abort message pop up when trying to edit existing text Product: krita Version: 4.2.3 Platform: Ubuntu Packages OS: Linux Status: REPORTED Severity: critical Priority: NOR Component: Tool/Text Assignee: krita-bugs-n...@kde.org Reporter: tobywills...@gmail.com Target Milestone: --- Created attachment 121617 --> https://bugs.kde.org/attachment.cgi?id=121617=edit Screenshot with abort popup SUMMARY STEPS TO REPRODUCE 1. open an existing file or make a new one 2. click the text tool 'T' in the toolbar 3. enter some text in the pop up box, click save then click close 4. click the text tool 'T' in the toolbar 5. now go to try and edit the newly added text OBSERVED RESULT the text pop up appears along with an error message pop up saying abort or ignore. Clicking abort closes Krita and ignore does just that but every time you try to edit text this pop up message appears Krita has encountered an internal error: SAFE ASSERT (krita): "!m_d->readyShortcut" in file /home/appimage/workspace/Krita_Release_Appimage_Build/krita/libs/ui/input/kis_shortcut_matcher.cpp, line 579 Please report a bug to developers! Press Ignore to try to continue. Press Abort to see developers information (all unsaved data will be lost) EXPECTED RESULT should be able to edit and save text with no error message pop up SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: Ubuntu 18.0.4.2 (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 409908] Crash upon close [incomplete gdb backtrace]
https://bugs.kde.org/show_bug.cgi?id=409908 --- Comment #6 from Tymond --- Created attachment 121616 --> https://bugs.kde.org/attachment.cgi?id=121616=edit Full valgrind error log -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 409954] KIO FTP: kioclient hangs while copying file over existing file [copy() did not call finished() or error()]
https://bugs.kde.org/show_bug.cgi?id=409954 Nate Graham changed: What|Removed |Added CC||n...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[krusader] [Bug 280450] Unable to save profile session
https://bugs.kde.org/show_bug.cgi?id=280450 Davide Gianforte changed: What|Removed |Added Status|CONFIRMED |RESOLVED Resolution|--- |UNMAINTAINED CC||dav...@gengisdave.org --- Comment #1 from Davide Gianforte --- Cannot reproduce on the latest version. Please reopen if the problem appears again. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 409967] CSD gtk3 apps have Wayland generic icon in the task switcher
https://bugs.kde.org/show_bug.cgi?id=409967 David Edmundson changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |NOT A BUG CC||k...@davidedmundson.co.uk --- Comment #1 from David Edmundson --- Please report to those apps. CSD vs SSD will be irrelevant. They almost certainly have a wrong app_id set compared to their .desktop file name. You can verify with WAYLAND_DEBUG=1 myApp |& grep set_app_id and then looking for the relevant .desktop file If they do match, please do reopen here. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 409881] Display a notification when indexing first begins
https://bugs.kde.org/show_bug.cgi?id=409881 --- Comment #3 from Łukasz Szeremeta --- As I mentioned in the bug 409876, properties is visible instantly on external drives. As far as I know, in that case indexation is turned off. In addition another person also mentioned that disabled indexation makes properties visible instantly. Why do I need to activate re-indexing manually or restart my system if indexation is enabled to see additional metadata in new files? Why does displaying metadata work immediately for external devices or just places where indexing is off? Maybe it would be possible to display properties without waiting also in the case of indexation enabled? It is possible that there is some other mechanism in those cases and there were some specific reasons why it works as it works. Thanks for clarification. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 409967] CSD gtk3 apps have Wayland generic icon in the task switcher
https://bugs.kde.org/show_bug.cgi?id=409967 Patrick Silva changed: What|Removed |Added Summary|CSD gtk3 windows have |CSD gtk3 apps have Wayland |Wayland generic in the task |generic icon in the task |switcher|switcher -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 409967] New: CSD gtk3 windows have Wayland generic in the task switcher
https://bugs.kde.org/show_bug.cgi?id=409967 Bug ID: 409967 Summary: CSD gtk3 windows have Wayland generic in the task switcher Product: kwin Version: 5.16.3 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: wayland-generic Assignee: kwin-bugs-n...@kde.org Reporter: bugsefor...@gmx.com Target Milestone: --- SUMMARY CSD gtk3 apps have generic Wayland icon in the task switcher. Examples of affected apps: evince pdf viewer gnome disks utility gnome mpv video player totem video player pulse effects STEPS TO REPRODUCE 1. start Wayland session 2. install and open any app mentioned above 3. press alt+tab and hold alt key OBSERVED RESULT mentioned above EXPECTED RESULT The task switcher shows the icon of the CSD gtk3 app SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 5.16.3 KDE Frameworks Version: 5.60 Qt Version: 5.13 ADDITIONAL INFORMATION SSD gkt3 apps are not affected. For exameple, the following SSD gtk3 apps have the correct icon in the task switcher: transmission torrent client brasero cd/dvd/bd burner uget download manager quod libet music player deluge 2.0.3 torrent client gaupol subtitles editor shotwell photo manager -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 409965] New: Function to compact the video needed
https://bugs.kde.org/show_bug.cgi?id=409965 Bug ID: 409965 Summary: Function to compact the video needed Product: kdenlive Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: User Interface Assignee: j...@kdenlive.org Reporter: had...@danisch.de Target Milestone: --- Hi, that's just a wish. Im currently quite busy with removing about 280 spaces in a video which are the result of editing (cutting unwanted scenes etc.) In the Timeline > Space there are functions to remove space and space in all tracks, but that's really slow (takes several seconds per run) and removes one space at a time only. Would be nice to have some compact or squeeze function, which just moves everything in the complete timeline to the left to eliminate all gaps (while keeping tracks aligned). thanks! -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 409908] Crash upon close [incomplete gdb backtrace]
https://bugs.kde.org/show_bug.cgi?id=409908 --- Comment #5 from Tymond --- Part of the valgrind errors log: ==1121== ==1121== Invalid read of size 4 ==1121==at 0x6DBBF48: load (atomic_base.h:396) ==1121==by 0x6DBBF48: loadAcquire (qatomic_cxx11.h:239) ==1121==by 0x6DBBF48: loadAcquire (qbasicatomic.h:106) ==1121==by 0x6DBBF48: operator int (qbasicatomic.h:108) ==1121==by 0x6DBBF48: KisShared::deref() (kis_shared.h:41) ==1121==by 0x70048B1: deref (kis_shared_ptr.h:210) ==1121==by 0x70048B1: deref (kis_shared_ptr.h:225) ==1121==by 0x70048B1: KisSharedPtr::~KisSharedPtr() (kis_shared_ptr.h:109) ==1121==by 0x9388A36: __cxa_finalize (cxa_finalize.c:83) ==1121==by 0x6D77172: ??? (in /home/tymon/kritadev/install/lib/x86_64-linux-gnu/libkritaimage.so.18.0.0) ==1121==by 0x4010C65: _dl_fini (dl-fini.c:138) ==1121==by 0x938837B: __run_exit_handlers (exit.c:108) ==1121==by 0x93884A9: exit (exit.c:139) ==1121==by 0x9367B71: (below main) (libc-start.c:342) ==1121== Address 0x1c996888 is 8 bytes inside a block of size 32 free'd ==1121==at 0x4839E7B: operator delete(void*) (in /usr/lib/x86_64-linux-gnu/valgrind/vgpreload_memcheck-amd64-linux.so) ==1121==by 0x938837B: __run_exit_handlers (exit.c:108) ==1121==by 0x93884A9: exit (exit.c:139) ==1121==by 0x9367B71: (below main) (libc-start.c:342) ==1121== Block was alloc'd at ==1121==at 0x4838DBF: operator new(unsigned long) (in /usr/lib/x86_64-linux-gnu/valgrind/vgpreload_memcheck-amd64-linux.so) ==1121==by 0x2355487B: __static_initialization_and_destruction_0 (kis_paint_device.cc:575) ==1121==by 0x2355487B: _GLOBAL__sub_I_kis_paint_device.cc (kis_paint_device.cc:2214) ==1121==by 0x40108D9: call_init.part.0 (dl-init.c:72) ==1121==by 0x40109D8: call_init (dl-init.c:30) ==1121==by 0x40109D8: _dl_init (dl-init.c:119) ==1121==by 0x4014C2B: dl_open_worker (dl-open.c:517) ==1121==by 0x949FA4E: _dl_catch_exception (dl-error-skeleton.c:196) ==1121==by 0x4014215: _dl_open (dl-open.c:599) ==1121==by 0xEF3E255: dlopen_doit (dlopen.c:66) ==1121==by 0x949FA4E: _dl_catch_exception (dl-error-skeleton.c:196) ==1121==by 0x949FADE: _dl_catch_error (dl-error-skeleton.c:215) ==1121==by 0xEF3EA24: _dlerror_run (dlerror.c:163) ==1121==by 0xEF3E2E5: dlopen@@GLIBC_2.2.5 (dlopen.c:87) -- You are receiving this mail because: You are watching all bug changes.
[KBibTeX] [Bug 409415] Freeze when opening edit dialog for second time
https://bugs.kde.org/show_bug.cgi?id=409415 Thomas Fischer changed: What|Removed |Added Ever confirmed|0 |1 Status|REPORTED|ASSIGNED --- Comment #1 from Thomas Fischer --- I cannot reproduce your problem, which makes it hard to help you here. There are several things you can test in the following order: - Create a new test user account on your system and use KBibTeX there. If you cannot reproduce the problem, then some file in your regular user's home is the cause - Setup a virtual machine with a fresh installation of Arch Linux and use KBibTeX there. If you cannot reproduce the problem, then your local installation including system libraries could be the problem. - Setup a virtual machine with an independent, KDE-based Linux distribution which uses recent Qt and KDE libraries, for example Fedora's KDE spin or Kubuntu. Test KBibTeX there. Based on your results, we can try to figure out the next steps. Regarding compiling KBibTeX from Git, you may alternatively try out the instructions here: https://userbase.kde.org/KBibTeX/Development#Quick_Start_to_Run_KBibTeX_from_Git (In reply to Tobias Schmalz from comment #0) > SUMMARY > When trying to open the edit dialog for the second time KBibTeX freezes > completely (no interaction possible, has to be killed via htop or similar). > The first edit dialog has no problems, though. I can even save the first > change and close KBibTeX afterwards. > > STEPS TO REPRODUCE > 1. Open KBibTeX > 2. Open the edit dialog for an arbitrary item > 3. Close the dialog (no need to actually edit anything) > 4. Try to open it again > > OBSERVED RESULT > KBibTeX freezes and has to be killed. > > EXPECTED RESULT > The edit dialog should pop up and let me do some editing. > > SOFTWARE/OS VERSIONS > Linux: 5.1.15 > KDE Plasma Version: --- > KDE Frameworks Version: 5.59.0 > Qt Version: 5.13.0 > > ADDITIONAL INFORMATION > When I was on Qt 5.12.4 until a few days ago I had another weird bug in all > Qt applications where I could open each submenu only once. When I tried to > open any of them for a second time nothing happened (no crash or freeze, > though). This was fixed by updating to Qt 5.13.0, so this might very well be > a Qt bug, too. However, I have no clue at all how to debug Qt and the > remaining bug at hand has not occurred to me in any other Qt application > yet. That's why I'm reporting this bug to you although it might not be your > fault but maybe someone here is a little more experienced than me. > I also tried to compile the latest version myself to check if there already > is a fix (using the kbibtex-git package from AUR) but the compilation > process always stops halfway through so I didn't get to the checking part. > Sorry about my incompetence! m) -- You are receiving this mail because: You are watching all bug changes.
[amarok] [Bug 409966] New: Amarok won't run, complains about missing plugins
https://bugs.kde.org/show_bug.cgi?id=409966 Bug ID: 409966 Summary: Amarok won't run, complains about missing plugins Product: amarok Version: 2.9.0 Platform: Debian testing OS: Linux Status: REPORTED Severity: major Priority: NOR Component: general Assignee: amarok-bugs-d...@kde.org Reporter: eyal...@technion.ac.il Target Milestone: kf5 I've downloaded and built Amarok 2.9.0 on Devuan Beowulf (= Debian Buster without systemd) - after installing a whole bunch of prerequisite Qt and KDE-related packaged. The build succeeds (after a bit of trouble I reported in other issues and got resolved); and I make install'ed amarok to /usr/loca . Now, when trying to run amarok, I get ``` amarok(24045)/kdecore (trader) KServiceTypeTrader::defaultOffers: KServiceTypeTrader: serviceType "Amarok/Plugin" not found ``` on the console, and a message box saying: > Amarok could not find any plugins. This indicates an installation problem. I'm reporting this as a bug for several reasons: 1. If something else need to be present on the system, then cmake'ing should have told me so. 2. Even if something is missing, the GUI and/or console messages should tell me what exactly what files, or folders, are missing so that I could go get them. 3. If plugins need to be installed independently - why aren't they available on the website? 4. If plugins are built and installed - how come amarok doesn't make even a minimal effort to locate them? Note: This is not resolved like the very similar problem I reported a while ago as the very similar bug 399097. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Linux 4.19.0-5-amd64 #1 SMP Debian 4.19.37-5 (2019-06-19) x86_64 GNU/Linux KDE Plasma Version: 5.54.0-1 KDE Frameworks Version: Not sure what number to put here. Qt Version: 5.11.3+dfsg1-1 -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 409964] New: reverse/forward +-10 seconds
https://bugs.kde.org/show_bug.cgi?id=409964 Bug ID: 409964 Summary: reverse/forward +-10 seconds Product: kdenlive Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: User Interface Assignee: j...@kdenlive.org Reporter: had...@danisch.de Target Milestone: --- That's just a wish: kdenlive allows to configure functions for the buttons of external jog dials, e.g. Contour shuttle. There's a list of functions to be put on buttons, and there's forward and reverse for 1 frame or 1 second. Would be nice to have functions for +- 10 seconds and +-1min as well. thanks! -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 409908] Crash upon close [incomplete gdb backtrace]
https://bugs.kde.org/show_bug.cgi?id=409908 --- Comment #4 from wolthera --- This is from 'close program without opening a file': = ==5095==ERROR: AddressSanitizer: heap-use-after-free on address 0x604000ccfc90 at pc 0x718d00e2 bp 0x7fffd210 sp 0x7fffd200 READ of size 4 at 0x604000ccfc90 thread T0 #0 0x718d00e1 in std::__atomic_base::load(std::memory_order) const /usr/include/c++/7/bits/atomic_base.h:396 #1 0x718d00e1 in int QAtomicOps::load(std::atomic const&) /usr/include/x86_64-linux-gnu/qt5/QtCore/qatomic_cxx11.h:227 #2 0x718ce539 in QBasicAtomicInteger::load() const /usr/include/x86_64-linux-gnu/qt5/QtCore/qbasicatomic.h:103 #3 0x718cc705 in QtPrivate::RefCount::deref() /usr/include/x86_64-linux-gnu/qt5/QtCore/qrefcount.h:66 #4 0x718ccc2d in QString::~QString() /usr/include/x86_64-linux-gnu/qt5/QtCore/qstring.h:1135 #5 0x7fffea92b614 in __cxa_finalize (/lib/x86_64-linux-gnu/libc.so.6+0x43614) #6 0x718c7d52 (/home/wolthera/krita/inst/lib/x86_64-linux-gnu/libkritaui.so.19+0x29e9d52) 0x604000ccfc90 is located 0 bytes inside of 34-byte region [0x604000ccfc90,0x604000ccfcb2) freed by thread T0 here: #0 0x76ef87b8 in __interceptor_free (/usr/lib/x86_64-linux-gnu/libasan.so.4+0xde7b8) #1 0x7fff90e6c201 in QTypedArrayData::deallocate(QArrayData*) /usr/include/x86_64-linux-gnu/qt5/QtCore/qarraydata.h:239 #2 0x7fff90e6b7ec in QString::~QString() /usr/include/x86_64-linux-gnu/qt5/QtCore/qstring.h:1135 #3 0x7fffea92b040 (/lib/x86_64-linux-gnu/libc.so.6+0x43040) previously allocated by thread T0 here: #0 0x76ef8b50 in __interceptor_malloc (/usr/lib/x86_64-linux-gnu/libasan.so.4+0xdeb50) #1 0x7fffeb32f301 in QArrayData::allocate(unsigned long, unsigned long, unsigned long, QFlags) (/usr/lib/x86_64-linux-gnu/libQt5Core.so.5+0xb5301) SUMMARY: AddressSanitizer: heap-use-after-free /usr/include/c++/7/bits/atomic_base.h:396 in std::__atomic_base::load(std::memory_order) const Shadow bytes around the buggy address: 0x0c0880191f40: fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa 0x0c0880191f50: fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa 0x0c0880191f60: fa fa 00 00 00 00 00 fa fa fa fa fa fa fa fa fa 0x0c0880191f70: fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa 0x0c0880191f80: fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa =>0x0c0880191f90: fa fa[fd]fd fd fd fd fa fa fa fa fa fa fa fa fa 0x0c0880191fa0: fa fa fa fa fa fa fa fa fa fa fd fd fd fd fd fd 0x0c0880191fb0: fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa 0x0c0880191fc0: fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa 0x0c0880191fd0: fa fa fa fa fa fa fa fa fa fa 00 00 00 00 00 fa 0x0c0880191fe0: fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa Shadow byte legend (one shadow byte represents 8 application bytes): Addressable: 00 Partially addressable: 01 02 03 04 05 06 07 Heap left redzone: fa Freed heap region: fd Stack left redzone: f1 Stack mid redzone: f2 Stack right redzone: f3 Stack after return: f5 Stack use after scope: f8 Global redzone: f9 Global init order: f6 Poisoned by user:f7 Container overflow: fc Array cookie:ac Intra object redzone:bb ASan internal: fe Left alloca redzone: ca Right alloca redzone:cb ==5095==ABORTING [Thread 0x77f8ce80 (LWP 5095) exited] [Inferior 1 (process 5095) exited with code 01] (gdb) -- You are receiving this mail because: You are watching all bug changes.
[amarok] [Bug 409836] Build failure: Undefined reference to setMountPointManager(MountPointManager*)
https://bugs.kde.org/show_bug.cgi?id=409836 --- Comment #5 from Myriam Schweingruber --- no, it is not a bug, you just need to either install and build the testing framework, or disable the testing (which is enabled by default). So definitely neither a build failure nor a bug, as testing is usually a requirement. IIRC this is also specified in the build instructions. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-qqc2-desktop-style] [Bug 409888] Input field text widget do not respect anti-aliasing preferences
https://bugs.kde.org/show_bug.cgi?id=409888 Nate Graham changed: What|Removed |Added CC||n...@kde.org Version Fixed In||5.61 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 409948] The font rendering is not very nice on the canvas
https://bugs.kde.org/show_bug.cgi?id=409948 --- Comment #4 from acc4commissi...@gmail.com --- Created attachment 121615 --> https://bugs.kde.org/attachment.cgi?id=121615=edit Capture When I copy paste the same-sized text on the canvas as a raster image (It's from the Text Editor) it looks fine though. And when I increase the dpi I need to make the font size number smaller in order to get the size that I want anyway. When people need to make any type of comics I'm very sure that they need to create tiny texts on the canvas. I'm not reopening the bug, but it'd be nice of you to consider improving the font rendering. Cheers. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 409963] New: no pen pressure
https://bugs.kde.org/show_bug.cgi?id=409963 Bug ID: 409963 Summary: no pen pressure Product: krita Version: 4.2.3 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Brush engines Assignee: krita-bugs-n...@kde.org Reporter: flo.uni...@gmail.com Target Milestone: --- SUMMARY Pen pressure not working after reinstalled krita on my surface. I have tried everything in settings and every trick i could find on the internet STEPS TO REPRODUCE 1. reinstalled krita 2. open krita 3. OBSERVED RESULT no pen pressure EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 409914] Circular *refresh* and update-* icons have arrows that are facing in the wrong direction
https://bugs.kde.org/show_bug.cgi?id=409914
Nate Graham changed:
What|Removed |Added
Version Fixed In||5.61
Resolution|--- |FIXED
Latest Commit||https://commits.kde.org/bre
||eze-icons/74c4155ff3d703e29
||9a3d86e7d3d030d2c6151e1
Status|ASSIGNED|RESOLVED
--- Comment #6 from Nate Graham ---
Git commit 74c4155ff3d703e299a3d86e7d3d030d2c6151e1 by Nate Graham.
Committed on 18/07/2019 at 19:12.
Pushed by ngraham into branch 'master'.
Use clockwise arrows for *refresh* and update-* icons
Summary:
Right now we are inconsistent with the arrow directionality for our circular
icons:
some use clockwise arrows, and some use counterclockwise.
This patch standardizes everything on the clockwise direction. This not only
makes
everything nice and consistent, but it also fixes the busy indictor spinner
looking
weird (it rotates clockwise, like all opther busy spinners we've ever seen in
any UI
toolkit).
FIXED-IN: 5.61
Test Plan:
{F7046657}
{F7046658}
{F7046660}
{F7046661}
{F7046668}
{F7046669}
{F7046670}
The eagle-eyed reviewer will note that the different icons also have different
styles of arrows and their rotational offset is also different, but if that's a
pre-existing issue that can be done in another patch, if it's also something we
want to unify.
Reviewers: #vdg, ndavis
Reviewed By: #vdg, ndavis
Subscribers: kde-frameworks-devel
Tags: #frameworks
Differential Revision: https://phabricator.kde.org/D22534
M +6-11 icons-dark/actions/16/view-refresh.svg
M +6-15 icons-dark/actions/22/view-refresh.svg
M +6-11 icons-dark/actions/24/view-refresh.svg
M +6-11 icons-dark/actions/32/view-refresh.svg
M +42 -1icons-dark/preferences/32/yast-update.svg
M +7-16 icons-dark/status/22/update-high.svg
M +7-21 icons-dark/status/22/update-low.svg
M +7-22 icons-dark/status/22/update-medium.svg
M +6-11 icons-dark/status/22/update-none.svg
M +6-11 icons/actions/16/view-refresh.svg
M +6-15 icons/actions/22/view-refresh.svg
M +6-11 icons/actions/24/view-refresh.svg
M +6-11 icons/actions/32/view-refresh.svg
M +42 -1icons/preferences/32/yast-update.svg
M +7-16 icons/status/22/update-high.svg
M +7-21 icons/status/22/update-low.svg
M +7-22 icons/status/22/update-medium.svg
M +6-11 icons/status/22/update-none.svg
https://commits.kde.org/breeze-icons/74c4155ff3d703e299a3d86e7d3d030d2c6151e1
--
You are receiving this mail because:
You are watching all bug changes.
[kdeconnect] [Bug 409707] Add an option to allow KDE Connect to run at Android start.
https://bugs.kde.org/show_bug.cgi?id=409707 Matthijs Tijink changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |NOT A BUG -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 409499] Krunner returns empty item
https://bugs.kde.org/show_bug.cgi?id=409499 --- Comment #2 from el...@seznam.cz --- This seems to be somewhat fixed in Frameworks 5.60. I don't get so many empty items. However there are still some. Also I noticed that if I get empty result, now it's always folder, never file. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kirigami] [Bug 409962] New: InlineMessage not compatible with QQC2 Actions
https://bugs.kde.org/show_bug.cgi?id=409962 Bug ID: 409962 Summary: InlineMessage not compatible with QQC2 Actions Product: frameworks-kirigami Version: 5.59.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: notm...@gmail.com Reporter: a.stipp...@gmx.net Target Milestone: Not decided The optional actions for the InlineMessage are not compatible with QQC2 Actions. It fails with various qml warnings in ActionToolBar due to missing properties and signals. -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 409914] Circular *refresh* and update-* icons have arrows that are facing in the wrong direction
https://bugs.kde.org/show_bug.cgi?id=409914 --- Comment #5 from Nate Graham --- Patch: https://phabricator.kde.org/D22534 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-qqc2-desktop-style] [Bug 409390] KDE System Settings -> Multimedia -> Audio Volume invisible tabs with QtCurve
https://bugs.kde.org/show_bug.cgi?id=409390 --- Comment #2 from Nate Graham --- Cannot reproduce with Plasma 5.16.3 or git master on Manjaro. -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 409707] Add an option to allow KDE Connect to run at Android start.
https://bugs.kde.org/show_bug.cgi?id=409707 --- Comment #3 from vbh...@vbhunt.net --- That solved it. Mark this as resolved. Summary for future people that may have this problem: make sure KDEConnect is installed in the phone rather than external storage if it doesn't autostart. -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 409707] Add an option to allow KDE Connect to run at Android start.
https://bugs.kde.org/show_bug.cgi?id=409707 --- Comment #2 from vbh...@vbhunt.net --- It hasn't started on boot since I upgraded from an Android Lollipop phone to my current Nougat phone. It might be because I've got the app installed to external storage. Moving it now and rechecking. Will post back in a few minutes to verify. On Jul 18, 2019 12:11 PM, Matthijs Tijink wrote: > > https://bugs.kde.org/show_bug.cgi?id=409707 > > Matthijs Tijink changed: > > What |Removed |Added > > CC| |matthijstij...@gmail.com > > --- Comment #1 from Matthijs Tijink --- > KDE Connect should already start on boot. It might take a while (Android > doesn't start everything at once), but it should work with a couple of minutes > after boot. > > -- > You are receiving this mail because: > You are on the CC list for the bug. > You reported the bug. -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 364239] Snippet keyboard shortcut doesn't work
https://bugs.kde.org/show_bug.cgi?id=364239 --- Comment #8 from Thomas Schöps --- I wasn't sure whether "Each new instance requires the Snippets tool to be re-enabled." describes another issue that might still be open. But probably yes. -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 409707] Add an option to allow KDE Connect to run at Android start.
https://bugs.kde.org/show_bug.cgi?id=409707 Matthijs Tijink changed: What|Removed |Added CC||matthijstij...@gmail.com --- Comment #1 from Matthijs Tijink --- KDE Connect should already start on boot. It might take a while (Android doesn't start everything at once), but it should work with a couple of minutes after boot. -- You are receiving this mail because: You are watching all bug changes.
[drkonqi] [Bug 409961] Dr.Konqui doesn't report plasmashell crash when using Wayland
https://bugs.kde.org/show_bug.cgi?id=409961 marcantoine_manning...@outlook.com changed: What|Removed |Added Component|backtraceparsing|general -- You are receiving this mail because: You are watching all bug changes.
[drkonqi] [Bug 409961] New: Dr.Konqui doesn't report plasmashell crash when using Wayland
https://bugs.kde.org/show_bug.cgi?id=409961 Bug ID: 409961 Summary: Dr.Konqui doesn't report plasmashell crash when using Wayland Product: drkonqi Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: major Priority: NOR Component: backtraceparsing Assignee: unassigned-b...@kde.org Reporter: marcantoine_manning...@outlook.com Target Milestone: --- SUMMARY When the plasmashell crash (which happen often), DrKonqui doesn't report the crash. It would really help to plasma wayland, because if the crash are reported with DrKonqui, that would provide a backtrack to help developer. STEPS TO REPRODUCE 1. Make plasmashell crash under wayland 2. Reboot plasmashell using kstart5 plasmashell OBSERVED RESULT When plasmashell is reboot no crash is reported. EXPECTED RESULT Dr.Konqui appear and report that plasmashell crashed. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: 5.16.3 KDE Frameworks Version: 5.60 Qt Version: 5.12.3 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kwidgetsaddons] [Bug 409772] KPageDialog icons are disproportionately large in high DPI displays
https://bugs.kde.org/show_bug.cgi?id=409772 Antonio Rojas changed: What|Removed |Added Resolution|--- |NOT A BUG Status|REPORTED|RESOLVED --- Comment #1 from Antonio Rojas --- Configuration issue, sorry for the noise -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 409406] KMyMoney Crash
https://bugs.kde.org/show_bug.cgi?id=409406 Thomas Baumgart changed: What|Removed |Added Resolution|WAITINGFORINFO |FIXED Status|NEEDSINFO |RESOLVED -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 409406] KMyMoney Crash
https://bugs.kde.org/show_bug.cgi?id=409406 --- Comment #3 from GBranco --- This was a first time run of KMyMoney. Reinstalled mysql and reimported sql file. Downgraded to 5.0.3. Working with no problem. I am on Slackware Current with multilib. Thank you, - G. Branco tlm.: +351 926 331 543 email: gsb.g...@gmail.com On Wed, 17 Jul 2019 at 05:33, Bug Janitor Service wrote: > https://bugs.kde.org/show_bug.cgi?id=409406 > > --- 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 reported the bug. -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 401294] Latte-dock can not always reset the zoomed launcher
https://bugs.kde.org/show_bug.cgi?id=401294 --- Comment #17 from Michail Vourlakos --- BTW this fix is for very specific case... First you must update to v0.9.0 and then check again if you are hit... There wont be any other fix release for v0.8 branch -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 401294] Latte-dock can not always reset the zoomed launcher
https://bugs.kde.org/show_bug.cgi?id=401294 --- Comment #16 from Michail Vourlakos --- No v0.8.9 does not contain that fiz -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 401294] Latte-dock can not always reset the zoomed launcher
https://bugs.kde.org/show_bug.cgi?id=401294 Thomas changed: What|Removed |Added CC||thfl...@gmail.com --- Comment #15 from Thomas --- Am I correct that version 0.8.9 already contains the fix? because I still get a stuck zoom about 5 times a day. It's hard to tell when it happens but when the zoom got stuck I can move the zoom to other icons and even other widgets. also the preview or application name is opening and stuck. I found out (some time ago) that the only way to solve it when it got stuck is by hovering the preview or application name of a launcher. I've tried to reproduce it now for about 10 minutes. And I still don't know exactly when it happens. What I can tell is that an app has to be executed and not minizimed then you need to hover this app till the preview is shown but what exact movement is required that it get's stuck.. maybe hovering over the position where the preview is shown at the right moment. maybe moving the pointer far away at the right moment... btw.: I can reproduce it on at least two machines one is on kde neon and the other one is on manjaro linux. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 409944] Toggling 'Global Selection Mask' does not return to the originally selected layer
https://bugs.kde.org/show_bug.cgi?id=409944 vanyossi changed: What|Removed |Added CC||ghe...@gmail.com --- Comment #1 from vanyossi --- I think the "Show global selection" wasn't meant to be used like that when first implemented. However I can see it could be useful at least to quickly edit the mask and return to the original layer. On the other hand, if enabling "Global Selection Mask" if you have a vector selection and the brush selected, it will change to the cursor tool. This is enabled only for brush tool as global selections can be modified with the other tools (pixel and vector selections), changing the tool automatically to be a brush would not work for all. -- You are receiving this mail because: You are watching all bug changes.
[amarok] [Bug 409836] Build failure: Undefined reference to setMountPointManager(MountPointManager*)
https://bugs.kde.org/show_bug.cgi?id=409836 --- Comment #4 from Eyal Rozenberg --- (In reply to Myriam Schweingruber from comment #3) > I guessed as much. It's still a build failure, albeit of the testing code. Aren't you supposed to change the component or mark it somehow instead of testing it? -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kfilemetadata] [Bug 409958] Baloo crash on system startup
https://bugs.kde.org/show_bug.cgi?id=409958 --- Comment #2 from Stephen Hassard --- I just figured out what's going on. I have an extracted tarball of the libpng src in my user folder and it has a png crasher image which baloo is failing to index: ``` % balooctl check Started search for unindexed files 8:41.stephen@kaiju:~% balooctl monitor Press ctrl+c to stop monitoring File indexer is running Indexing file content Indexing: /home/stephen/devel/USD_build/scripts/libpng-1.6.37/contrib/testpngs/crashers/empty_ancillary_chunks.png ``` -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 409937] Actions on drag-and-dropped reference images breaks left-click
https://bugs.kde.org/show_bug.cgi?id=409937 vanyossi changed: What|Removed |Added Status|REPORTED|ASSIGNED Ever confirmed|0 |1 Assignee|krita-bugs-n...@kde.org |ghe...@gmail.com CC||ghe...@gmail.com --- Comment #1 from vanyossi --- I can confirm this bug. This only happens on a fresh opened image, There is no need to select an action. 4. right click 5. left click (or escape to hide menu) outside of menu I can recover left-click inside Krita after calling the popup palette. Or by selecting another application window and return to Krita. If selecting another app window the bug dissapears. -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 409914] Circular *refresh* and update-* icons have arrows that are facing in the wrong direction
https://bugs.kde.org/show_bug.cgi?id=409914 Nate Graham changed: What|Removed |Added Status|CONFIRMED |ASSIGNED -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 409914] Circular *refresh* and update-* icons have arrows that are facing in the wrong direction
https://bugs.kde.org/show_bug.cgi?id=409914 Nate Graham changed: What|Removed |Added Assignee|visual-des...@kde.org |n...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[amarok] [Bug 409836] Build failure: Undefined reference to setMountPointManager(MountPointManager*)
https://bugs.kde.org/show_bug.cgi?id=409836 Myriam Schweingruber changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |NOT A BUG --- Comment #3 from Myriam Schweingruber --- I guessed as much. -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 409914] Circular *refresh* and update-* icons have arrows that are facing in the wrong direction
https://bugs.kde.org/show_bug.cgi?id=409914 Nate Graham changed: What|Removed |Added Summary|BusyIndicator animation |Circular *refresh* and |rotates the wrong way |update-* icons have arrows ||that are facing in the ||wrong direction Assignee|notm...@gmail.com |visual-des...@kde.org CC||kain...@gmail.com Component|general |Icons Product|frameworks-qqc2-desktop-sty |Breeze |le | --- Comment #4 from Nate Graham --- Yeah ok, that makes sense. Moving to Breeze icons. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kfilemetadata] [Bug 409958] Baloo crash on system startup
https://bugs.kde.org/show_bug.cgi?id=409958 Stefan Brüns changed: What|Removed |Added Assignee|stefan.bruens@rwth-aachen.d |pinak.ah...@gmail.com |e | Component|Baloo File Daemon |general Product|frameworks-baloo|frameworks-kfilemetadata --- Comment #1 from Stefan Brüns --- 1. Does you computer support SSSE3 (three "S")? 2. It crashes on some (probably malformed) PNG file. Please check with "balooctl failed" and provide the file if possible. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-qqc2-desktop-style] [Bug 408950] ComboBox doesn't close when clicked on the ComboBox itself
https://bugs.kde.org/show_bug.cgi?id=408950 Kai Uwe Broulik changed: What|Removed |Added Resolution|--- |FIXED Latest Commit||https://commits.kde.org/qqc ||2-desktop-style/6103f249381 ||61350163b841a81f5ebf20a9527 ||df Status|CONFIRMED |RESOLVED --- Comment #2 from Kai Uwe Broulik --- Git commit 6103f24938161350163b841a81f5ebf20a9527df by Kai Uwe Broulik. Committed on 18/07/2019 at 15:29. Pushed by broulik into branch 'master'. [ComboBox] Set close policy to close on click outside instead of only outside parent Ensures clicking the ComboBox itself closes the popup as it does with widget QComboBox. While Qt documentation for Popup says that is the default, QQuickComboBox explicitly overwrites it to be CloseOnPressOutsideParent instead for whatever reason. For our usecase the CloseOnPressOutside behavior makes more sense. Differential Revision: https://phabricator.kde.org/D22509 M +1-0org.kde.desktop/ComboBox.qml https://commits.kde.org/qqc2-desktop-style/6103f24938161350163b841a81f5ebf20a9527df -- You are receiving this mail because: You are watching all bug changes.
[konqueror] [Bug 409833] Konqueror crashes on close
https://bugs.kde.org/show_bug.cgi?id=409833 --- Comment #3 from Wolfgang Bauer --- (In reply to Fernando Romero from comment #2) > (In reply to Wolfgang Bauer from comment #1) > > Looks like bug#407454, which should actually be fixed in the latest KDE > > Applications 19.04.3. > > > > Which konqueror version are you using exactly? > > 5.0.97 Yes, but what KDE Applications version? I.e. 19.04.2 or 19.04.3? 5.0.97 doesn't tell much, it hasn't been changed in years. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 409954] KIO FTP: kioclient hangs while copying file over existing file [copy() did not call finished() or error()]
https://bugs.kde.org/show_bug.cgi?id=409954 Alexander Kernozhitsky changed: What|Removed |Added CC||sh200...@mail.ru -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 409954] KIO FTP: kioclient hangs while copying file over existing file [copy() did not call finished() or error()]
https://bugs.kde.org/show_bug.cgi?id=409954 Anton K changed: What|Removed |Added CC||kvanton@yandex.ru Ever confirmed|0 |1 Status|REPORTED|CONFIRMED --- Comment #2 from Anton K --- I also have this problem in the Dolphin. OS: KDE neon 5.16 DE: KDE 5.60.0 / Plasma 5.16.3 Qt: 5.12.3 Kernel: x86_64 Linux 5.0.0-05-generic -- You are receiving this mail because: You are watching all bug changes.
[frameworks-qqc2-desktop-style] [Bug 409888] Input field text widget do not respect anti-aliasing preferences
https://bugs.kde.org/show_bug.cgi?id=409888 Kai Uwe Broulik changed: What|Removed |Added Resolution|--- |FIXED Status|CONFIRMED |RESOLVED Latest Commit||https://commits.kde.org/qqc ||2-desktop-style/8927e90ac08 ||f65de8e15f066200bb7252b86ec ||1a --- Comment #6 from Kai Uwe Broulik --- Git commit 8927e90ac08f65de8e15f066200bb7252b86ec1a by Kai Uwe Broulik. Committed on 18/07/2019 at 15:01. Pushed by broulik into branch 'master'. [SpinBox] Set renderType Ensures it uses the system's font rendering settings Differential Revision: https://phabricator.kde.org/D22505 M +5-0org.kde.desktop/SpinBox.qml https://commits.kde.org/qqc2-desktop-style/8927e90ac08f65de8e15f066200bb7252b86ec1a -- You are receiving this mail because: You are watching all bug changes.
[elisa] [Bug 409921] Elisa can't find or open music in folders with # (number sign) in them
https://bugs.kde.org/show_bug.cgi?id=409921 Nate Graham changed: What|Removed |Added CC||n...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 409960] New: Kdenlive 19.04.3 doesn't run. (Manjaro Linux pacman package)
https://bugs.kde.org/show_bug.cgi?id=409960 Bug ID: 409960 Summary: Kdenlive 19.04.3 doesn't run. (Manjaro Linux pacman package) Product: kdenlive Version: 19.04.3 Platform: Manjaro OS: Linux Status: REPORTED Severity: critical Priority: NOR Component: Installation Assignee: vpi...@kde.org Reporter: jimn...@naver.com Target Milestone: --- Created attachment 121613 --> https://bugs.kde.org/attachment.cgi?id=121613=edit This file is terminal error message. SUMMARY Hello, I'm using Manjaro(KDE) latest update. I successfully installed kdenlive 19.04.3 package with pacman. But I couldn't run. STEPS TO REPRODUCE 1. sudo pacman -S kdenlive => Success 2. I tried to click kdenlive Icon. 3. I waited about 10 seconds. But kdenlive didn't started. (Please see youtube video with 720p.) https://www.youtube.com/watch?v=CyJsdBx_PQY 4. So, I tried to type kdenlive in terminal. 5. I saw many error messages. And didn't run too. (Please check attachment txt file.) Can I solve this problem? How can I do? ※ When I removed kdenlive package(sudo pacman -R -n -s kdenlive) and run appimage file, this appimage file worked well. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Manjaro KDE KDE Plasma Version: 5.16.3 KDE Frameworks Version: 5.60.0 Qt Version: 5.13.0 ADDITIONAL INFORMATION kernel version : 4.19.59.1-Manjaro -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 409933] The shell extension is unstable on the reporter's system
https://bugs.kde.org/show_bug.cgi?id=409933 vanyossi changed: What|Removed |Added CC||ghe...@gmail.com --- Comment #2 from vanyossi --- from the OP: "But after my computer went haywire on me this year, the Window's Shell Extension has not been cooperating with me…" This alongside us not changing the involved component at all, clearly indicates something is wrong with your system. Reinstalling Krita will not help if there is something corrupted system wise :/ Im tempted to mark this as "not a bug" but I'll wait for Original Reporter response. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 409901] Re-add virtual desktop shortcuts config UI to new KCM
https://bugs.kde.org/show_bug.cgi?id=409901 Nate Graham changed: What|Removed |Added Status|REPORTED|CONFIRMED Summary|configuration for switching |Re-add virtual desktop |desktops has "disappeared" |shortcuts config UI to new ||KCM Assignee|kwin-bugs-n...@kde.org |plasma-b...@kde.org CC||h...@kde.org, n...@kde.org Severity|normal |wishlist Ever confirmed|0 |1 Product|kwin|systemsettings Version|5.15.3 |5.16.3 Component|general |general -- You are receiving this mail because: You are watching all bug changes.
[Qt/KDE Flatpak Runtime] [Bug 409902] Cannot start flatpak apps under Gnome+Wayland
https://bugs.kde.org/show_bug.cgi?id=409902 Nate Graham changed: What|Removed |Added CC||n...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 409959] New: Indicate loading of search results and suggestions
https://bugs.kde.org/show_bug.cgi?id=409959 Bug ID: 409959 Summary: Indicate loading of search results and suggestions Product: krunner Version: 5.15.5 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: k...@privat.broulik.de Reporter: aspotas...@gmail.com Target Milestone: --- SUMMARY Indicate loading of search results and suggestions. STEPS TO REPRODUCE 1. Open krunner. 2. Type in some text, e.g. "php" 3. See what happens before the search results are ready. OBSERVED RESULT Nothing happens until search results are ready (for me it's "Run php", "PhpStorm", some bookmarks, etc). It's impossible to know if nothing is found or search is still in progress. On cold start, a search may take several seconds. EXPECTED RESULT The drop-down should appear immediately and display either some text like "Loading...", or a progress bar, or a progress spinner. SOFTWARE/OS VERSIONS Operating System: Fedora 30 KDE Plasma Version: 5.15.5 KDE Frameworks Version: 5.59.0 Qt Version: 5.12.4 Kernel Version: 5.1.16-300.fc30.x86_64 OS Type: 64-bit Processors: 2 × Intel® Celeron® CPU B800 @ 1.50GHz Memory: 3,8 ГиБ ADDITIONAL INFORMATION Tag: usability -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 409958] New: Baloo crash on system startup
https://bugs.kde.org/show_bug.cgi?id=409958 Bug ID: 409958 Summary: Baloo crash on system startup Product: frameworks-baloo Version: 5.60.0 Platform: Ubuntu Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: Baloo File Daemon Assignee: stefan.bru...@rwth-aachen.de Reporter: st...@hassard.net Target Milestone: --- Application: baloo_file_extractor (5.60.0) Qt Version: 5.12.3 Frameworks Version: 5.60.0 Operating System: Linux 4.18.0-25-generic x86_64 Distribution: Ubuntu 18.04.2 LTS -- Information about the crash: - What I was doing when the application crashed: First login to the freshly booted KDE Neon machine. Baloo crashed on startup. System was updated with 'pkcon refresh && pkcon update' and crashed again after a full restart. The crash can be reproduced every time. -- Backtrace: Application: Baloo File Extractor (baloo_file_extractor), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f49126b5c80 (LWP 1665))] Thread 3 (Thread 0x7f4902fda700 (LWP 1676)): #0 0x7f490f194bf9 in __GI___poll (fds=0x7f48f401a5a0, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7f490b85d5c9 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f490b85d6dc in g_main_context_iteration () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f490fad7dcb in QEventDispatcherGlib::processEvents (this=0x7f48f4000b20, flags=...) at kernel/qeventdispatcher_glib.cpp:424 #4 0x7f490fa7903a in QEventLoop::exec (this=this@entry=0x7f4902fd9d70, flags=..., flags@entry=...) at kernel/qeventloop.cpp:225 #5 0x7f490f8a04ca in QThread::exec (this=) at thread/qthread.cpp:531 #6 0x7f491147b015 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5 #7 0x7f490f8a1c72 in QThreadPrivate::start (arg=0x7f49116f2d80) at thread/qthread_unix.cpp:361 #8 0x7f490d9fc6db in start_thread (arg=0x7f4902fda700) at pthread_create.c:463 #9 0x7f490f1a188f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 2 (Thread 0x7f4904210700 (LWP 1674)): #0 0x7f490f194bf9 in __GI___poll (fds=0x7f490420fca8, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7f490b3ec747 in ?? () from /usr/lib/x86_64-linux-gnu/libxcb.so.1 #2 0x7f490b3ee36a in xcb_wait_for_event () from /usr/lib/x86_64-linux-gnu/libxcb.so.1 #3 0x7f4906ff7578 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5XcbQpa.so.5 #4 0x7f490f8a1c72 in QThreadPrivate::start (arg=0x55e1e636a0b0) at thread/qthread_unix.cpp:361 #5 0x7f490d9fc6db in start_thread (arg=0x7f4904210700) at pthread_create.c:463 #6 0x7f490f1a188f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 1 (Thread 0x7f49126b5c80 (LWP 1665)): [KCrash Handler] #6 __memcpy_ssse3 () at ../sysdeps/x86_64/multiarch/memcpy-ssse3.S:2827 #7 0x7f49017c7bcf in Exiv2::PngImage::readMetadata() () from /usr/lib/x86_64-linux-gnu/libexiv2.so.27 #8 0x7f4901b93148 in KFileMetaData::Exiv2Extractor::extract (this=0x55e1e64858d0, result=0x7ffe19fb9960) at ./src/extractors/exiv2extractor.cpp:167 #9 0x55e1e41ee50f in Baloo::App::index (this=this@entry=0x7ffe19fba100, tr=0x55e1e63c4540, url=..., id=id@entry=118797871989457666) at ./src/file/extractor/app.cpp:192 #10 0x55e1e41eee6e in Baloo::App::processNextFile (this=0x7ffe19fba100) at ./src/file/extractor/app.cpp:112 #11 0x7f490fab7804 in QtPrivate::QSlotObjectBase::call (a=0x7ffe19fb9ab0, r=, this=) at ../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:394 #12 QSingleShotTimer::timerEvent (this=0x55e1e63d7fb0) at kernel/qtimer.cpp:318 #13 0x7f490faab39b in QObject::event (this=0x55e1e63d7fb0, e=) at kernel/qobject.cpp:1282 #14 0x7f491087665c in QApplicationPrivate::notify_helper (this=this@entry=0x55e1e63420f0, receiver=receiver@entry=0x55e1e63d7fb0, e=e@entry=0x7ffe19fb9df0) at kernel/qapplication.cpp:3736 #15 0x7f491087db90 in QApplication::notify (this=0x7ffe19fba0d0, receiver=0x55e1e63d7fb0, e=0x7ffe19fb9df0) at kernel/qapplication.cpp:3483 #16 0x7f490fa7ad18 in QCoreApplication::notifyInternal2 (receiver=0x55e1e63d7fb0, event=0x7ffe19fb9df0) at kernel/qcoreapplication.cpp:1060 #17 0x7f490fad7219 in QTimerInfoList::activateTimers (this=0x55e1e639f690) at kernel/qtimerinfo_unix.cpp:643 #18 0x7f490fad7a19 in timerSourceDispatch (source=) at kernel/qeventdispatcher_glib.cpp:182 #19 idleTimerSourceDispatch (source=) at kernel/qeventdispatcher_glib.cpp:229 #20 0x7f490b85d417 in g_main_context_dispatch () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #21 0x7f490b85d650 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #22 0x7f490b85d6dc in g_main_context_iteration () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #23
[plasmashell] [Bug 409957] New: Adjust the size of kickoff settings window to unhide the tip on bottom
https://bugs.kde.org/show_bug.cgi?id=409957 Bug ID: 409957 Summary: Adjust the size of kickoff settings window to unhide the tip on bottom Product: plasmashell Version: 5.16.3 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Application Launcher (Kickoff) Assignee: k...@davidedmundson.co.uk Reporter: bugsefor...@gmx.com CC: plasma-b...@kde.org Target Milestone: 1.0 Created attachment 121612 --> https://bugs.kde.org/attachment.cgi?id=121612=edit screenshot SUMMARY As we can see in the attached screenshot, currently "Drag tabs between the boxes..." on bottom is hidden when you open kickoff settings. STEPS TO REPRODUCE 1. open kickoff settings 2. 3. EXPECTED RESULT The tip on bottom is always visible when you open kickoff settings. SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 5.16.3 KDE Frameworks Version: 5.60.0 Qt Version: 5.13.0 -- You are receiving this mail because: You are watching all bug changes.
[Plasma SDK] [Bug 409956] Window decoration of cuttlefish shows Wayland generic icon
https://bugs.kde.org/show_bug.cgi?id=409956
David Edmundson changed:
What|Removed |Added
CC||k...@davidedmundson.co.uk
Status|REPORTED|CONFIRMED
Ever confirmed|0 |1
--- Comment #1 from David Edmundson ---
[1972827.001] -> xdg_toplevel@33.set_app_id("cuttlefish")
./share/applications/org.kde.cuttlefish.desktop
These don't match up.
--
You are receiving this mail because:
You are watching all bug changes.
[plasmashell] [Bug 408313] kickoff switches to "Favorites" tab on opening
https://bugs.kde.org/show_bug.cgi?id=408313 Patrick Silva changed: What|Removed |Added Summary|kickoff switch to |kickoff switches to |"Favorites" tab on opening |"Favorites" tab on opening -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 408313] kickoff switch to "Favorites" tab on opening
https://bugs.kde.org/show_bug.cgi?id=408313 Patrick Silva changed: What|Removed |Added Resolution|FIXED |--- Ever confirmed|0 |1 Status|RESOLVED|REOPENED Summary|When|kickoff switch to ||"Favorites" tab on opening CC||bugsefor...@gmx.com --- Comment #4 from Patrick Silva --- This behavior is still happening at least on Wayland session. Operating System: Arch Linux KDE Plasma Version: 5.16.3 KDE Frameworks Version: 5.60.0 Qt Version: 5.13.0 -- You are receiving this mail because: You are watching all bug changes.
[Falkon] [Bug 408981] missing MSVCR120.dll
https://bugs.kde.org/show_bug.cgi?id=408981 step...@munsch-familie.de changed: What|Removed |Added Resolution|--- |NOT A BUG Status|REPORTED|NEEDSINFO --- Comment #2 from step...@munsch-familie.de --- I could resolve the problem here. It was to install "Microsoft Visual C++ 2013 Resdistributable (X64) 12.0.30501". I also installed the (X86) version as well to be sure (running 64-bit Windows 10). After that Falkon startet as desired. @kavol: I would like to know if this helps You to get Falkon running on Your system. If it does, I would be pleased if You could close the case. Best regards Stephan -- You are receiving this mail because: You are watching all bug changes.
[Plasma SDK] [Bug 409956] New: Window decoration of cuttlefish shows Wayland generic icon
https://bugs.kde.org/show_bug.cgi?id=409956 Bug ID: 409956 Summary: Window decoration of cuttlefish shows Wayland generic icon Product: Plasma SDK Version: 5.16.3 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: cuttlefish Assignee: plasma-b...@kde.org Reporter: bugsefor...@gmx.com CC: giorgos.tsiapalio...@kde.org Target Milestone: --- Created attachment 121611 --> https://bugs.kde.org/attachment.cgi?id=121611=edit screenshot SUMMARY STEPS TO REPRODUCE 1. start Wayland session 2. open cuttlefish 3. OBSERVED RESULT as we can see in the attached screenshot, window decorations shows Wayland generic icon. The same icon appears in the task switcher (alt+tab). EXPECTED RESULT both window decoration and task switcher show cuttlefish icon. SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 5.16.3 KDE Frameworks Version: 5.60.0 Qt Version: 5.13.0 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 409948] The font rendering is not very nice on the canvas
https://bugs.kde.org/show_bug.cgi?id=409948 Boudewijn Rempt changed: What|Removed |Added Resolution|WAITINGFORINFO |NOT A BUG Status|NEEDSINFO |RESOLVED --- Comment #3 from Boudewijn Rempt --- 72 dp is very, very low. Probably lower than your actual screen resolution. And given that the text is really very small, it's normal that it shows up pixelated. Remember that Krita renders the vectors not at the maximum sharpness the output device allows, but on the pixels of your raster image. -- You are receiving this mail because: You are watching all bug changes.
[krename] [Bug 409955] New: "Insert part of filename" is locked
https://bugs.kde.org/show_bug.cgi?id=409955 Bug ID: 409955 Summary: "Insert part of filename" is locked Product: krename Version: 5.0.0 Platform: Ubuntu Packages OS: Linux Status: REPORTED Severity: critical Priority: NOR Component: general Assignee: heire...@exherbo.org Reporter: antonio.ang...@protonmail.com Target Milestone: --- SUMMARY Inadvertently, I inserted the initial characters of the filename in the textbox of the tool "Insert part of filename". Usually, this textbox shows the filename from which I can select the part to insert. Now I cannot delete the unwanted characters I inserted, that remains unchanged, instead of showing the original filename. Reboot has no effect. The problem remains after reinstall. STEPS TO REPRODUCE 1. Add some files to rename 2. In Filename tab, click "Insert part of filename" 3. Insert some characters in textbox. 4. Click OK OBSERVED RESULT 1. In "Insert part of filename" mode, the content of the textbox cannot be edited neither with Canc/Backspace nor edited from keyboard. 2. Selecting part of the textbox, then OK, Kderename uses the selected text to rename the files. 3. Launching Kderename to rename file starting with different characters works OK but trying to rename the initial filename (that starts with the edited characters) has again the same problem. EXPECTED RESULT 1. The textbox should not be editable, only selectable. 2. After applied the rename, closing Kderename, this textbox should be filled with the first filename to rename. SOFTWARE/OS VERSIONS Linux: Ubuntu 18.04.2 LTS Window Manager: GNOME Shell GNOME: 3.28.2 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
