[gcompris] [Bug 425062] Apps does not run properly. no window open.
https://bugs.kde.org/show_bug.cgi?id=425062 --- Comment #3 from Jazeix Johnny --- Hi, can you also run it in command line and check if there are logs outputted? Thank you -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 424793] z-level lost when saving reference images to a .kra file.
https://bugs.kde.org/show_bug.cgi?id=424793 wolthera changed: What|Removed |Added Status|CONFIRMED |RESOLVED Latest Commit||https://invent.kde.org/grap ||hics/krita/commit/ffed60b76 ||911e0ed2fc8d07d68d82d36e2a2 ||41e3 Resolution|--- |FIXED --- Comment #7 from wolthera --- Git commit ffed60b76911e0ed2fc8d07d68d82d36e2a241e3 by Wolthera van Hövell tot Westerflier. Committed on 06/08/2020 at 15:19. Pushed by woltherav into branch 'krita/4.3'. Fix setting z-index for reference images when loading or adding to a document. M +1-0plugins/impex/libkra/kis_kra_loader.cpp M +16 -1 plugins/tools/defaulttool/referenceimagestool/ToolReferenceImages.cpp https://invent.kde.org/graphics/krita/commit/ffed60b76911e0ed2fc8d07d68d82d36e2a241e3 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 403974] Reference Images: z-position/order not saved
https://bugs.kde.org/show_bug.cgi?id=403974 wolthera changed: What|Removed |Added Status|CONFIRMED |RESOLVED Latest Commit|https://commits.kde.org/kri |https://invent.kde.org/grap |ta/e46e8d5c8d8f52df2187db11 |hics/krita/commit/bdf725217 |327f36f8994930ba|f7068e99d02c873109f0c498dd0 ||fd15 Resolution|--- |FIXED --- Comment #10 from wolthera --- Git commit bdf725217f7068e99d02c873109f0c498dd0fd15 by Wolthera van Hövell tot Westerflier. Committed on 06/08/2020 at 15:18. Pushed by woltherav into branch 'krita/4.3'. Fix z-order saving for reference images. Like shape layers reference image shapes ough to be sorted first. M +3-1plugins/impex/libkra/kis_kra_save_visitor.cpp https://invent.kde.org/graphics/krita/commit/bdf725217f7068e99d02c873109f0c498dd0fd15 -- You are receiving this mail because: You are watching all bug changes.
[korganizer] [Bug 424742] Korganizer crashes when editing categories colors
https://bugs.kde.org/show_bug.cgi?id=424742 --- Comment #3 from Kleber --- Created attachment 130680 --> https://bugs.kde.org/attachment.cgi?id=130680=edit New crash information added by DrKonqi kontact (5.14.3 (20.04.3)) using Qt 5.15.0 - What I was doing when the application crashed: I was changing the color of a message tag when applying, kontact crash. -- Backtrace (Reduced): #4 0x7f1f8255ca7f in std::__atomic_base::load (__m=std::memory_order_relaxed, this=) at /usr/include/c++/10/bits/atomic_base.h:420 #5 QAtomicOps::loadRelaxed (_q_value=...) at ../../include/QtCore/../../src/corelib/thread/qatomic_cxx11.h:239 #6 QBasicAtomicInteger::loadRelaxed (this=) at ../../include/QtCore/../../src/corelib/thread/qbasicatomic.h:107 [...] #8 QVector::QVector (this=0x7fffa83c7800, v=...) at ../../include/QtCore/../../src/corelib/tools/qvector.h:380 #9 0x7f1f8255d414 in QStack >::pop (this=this@entry=0x55cb97b52288) at ../../include/QtCore/../../src/corelib/tools/qvector.h:88 -- You are receiving this mail because: You are watching all bug changes.
[korganizer] [Bug 424742] Korganizer crashes when editing categories colors
https://bugs.kde.org/show_bug.cgi?id=424742 Kleber changed: What|Removed |Added CC||kleberbal...@outlook.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 424259] plasmashell produces a lot of warnings in the journal
https://bugs.kde.org/show_bug.cgi?id=424259 --- Comment #9 from Aurélien Oudelet (auroud85_fr) --- OK, so I will open a bug. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 411852] 'Reset Transformations' to reset size changes doesn't work on a single reference image.
https://bugs.kde.org/show_bug.cgi?id=411852 wolthera changed: What|Removed |Added Component|Tools/Reference Images |Layers/Vector --- Comment #2 from wolthera --- This one also happens on vector layers. Therefore I am categorizing. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 424259] plasmashell produces a lot of warnings in the journal
https://bugs.kde.org/show_bug.cgi?id=424259 --- Comment #8 from David Edmundson --- No -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kuserfeedback] [Bug 425050] I see you're already losing users' trust over this... Here are some suggestions.
https://bugs.kde.org/show_bug.cgi?id=425050 Someone Concerned changed: What|Removed |Added Resolution|NOT A BUG |--- Status|RESOLVED|REPORTED --- Comment #2 from Someone Concerned --- I found the original post in the Internet Archive (https://bit.ly/33xZguw), and yeah, somebody found the notification timer, got a tad too suspicious, and jumped to premature conclusions... There's an interesting quote in there though: "[...] No one can resist once they have their fingers in the cookie jar. [...] We'll just be the frogs being brought up to a slow boil. We know this tune, have seen this show many times before. There's always a plan. The time for naivety on this has passed, years ago." You might be tempted to dismiss this person as overly distrustful, but such distrustfullness is actually an extremely healthy attitude to have in this day and age. Look around! Governments and corporations plan to enslave us, exploit us, they dream of replacing us with machines or turning us into mindless cyborg drones! This is secular damnation. We must defend our privacy, remain ever vigilant, and, most important of all, keep dissent and resistance possible. Please don't alienate distrustful people, listen to them instead. (5) "I have tried replacing kuserfeedback with a dummy package on Arch Linux. Plasma simply freezes during startup." "[...] allow us to nuke this thing from orbit." "[...] it's just one little "oopsie" away from behind transmitted wholesale to KDE." - that's what the split library proposal aims to address concerns like this - allow users to remove the code responsible for data logging and transmission from their computers without breaking applications. (6) "there are internal names, changing them will not change anything" - except that these names are a grade A bad rumor material... (7) Nice! The "View previously submitted data..." link should probably be simply disabled rather than hidden in order to make it immediately clear that you'll be able to do so. (8) I meant like manual crash reports. Once a report is generated, a "User Feedback" system tray icon should appear, and the user should be able to click it, review the report, and then either send it or cancel it. -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 413368] upgraded to 5.17.x, krunner alt-f2 shortcut stopped working
https://bugs.kde.org/show_bug.cgi?id=413368 --- Comment #18 from Rex Dieter --- Can you be more specific about how you fixed it? Is it something you'd advocated for kde upstream to adopt? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 423155] Show date by default
https://bugs.kde.org/show_bug.cgi?id=423155 Nate Graham changed: What|Removed |Added Version Fixed In||5.20 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 423155] Show date by default
https://bugs.kde.org/show_bug.cgi?id=423155 Nate Graham changed: What|Removed |Added Resolution|--- |FIXED Status|ASSIGNED|RESOLVED Latest Commit||https://invent.kde.org/plas ||ma/plasma-workspace/commit/ ||8b0164b03ec659aa4ef3748bf80 ||7b3f91b129203 --- Comment #4 from Nate Graham --- Git commit 8b0164b03ec659aa4ef3748bf807b3f91b129203 by Nate Graham, on behalf of Claudius Ellsel. Committed on 06/08/2020 at 14:37. Pushed by ngraham into branch 'master'. Show the date in digital clock by default M +1-1applets/digital-clock/package/contents/config/main.xml https://invent.kde.org/plasma/plasma-workspace/commit/8b0164b03ec659aa4ef3748bf807b3f91b129203 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 424259] plasmashell produces a lot of warnings in the journal
https://bugs.kde.org/show_bug.cgi?id=424259 --- Comment #7 from Aurélien Oudelet (auroud85_fr) --- What about: plasmashell [4788]: qt.qpa.xcb: QXcbConnection: XCB error: 2 (BadValue), sequence: 43244, resource id: 56623518, major code: 141 (Unknown), minor code: 3 Does these warning be catched by your commit? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 424259] plasmashell produces a lot of warnings in the journal
https://bugs.kde.org/show_bug.cgi?id=424259 --- Comment #6 from Aurélien Oudelet (auroud85_fr) --- Nice, It will be for Plasma 5.19.5? Or 5.20 version of Plasmashell? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 420077] logout from Wayland session makes kwin to crash
https://bugs.kde.org/show_bug.cgi?id=420077 Nate Graham changed: What|Removed |Added Latest Commit|https://commits.kde.org/kwi |https://invent.kde.org/plas |n/e8a1f8ecccb548af2f80b2619 |ma/kwin/commit/307a9bc5590f |669da9dc135f175 |6f82b279a611b1f406bbd423687 ||e Version Fixed In|5.18.5 |5.20.0 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 425032] Fallback setting for new grouped task behavior does not work
https://bugs.kde.org/show_bug.cgi?id=425032 David Redondo changed: What|Removed |Added Resolution|--- |FIXED Status|ASSIGNED|RESOLVED Latest Commit||https://invent.kde.org/plas ||ma/plasma-desktop/commit/43 ||a1a5b01536c596b1ab7395f1f29 ||4ddafb6360c --- Comment #3 from David Redondo --- Git commit 43a1a5b01536c596b1ab7395f1f294ddafb6360c by David Redondo. Committed on 06/08/2020 at 10:15. Pushed by ngraham into branch 'master'. Fix grouped task visualizations fallback The indices in the config page were wrong and the last case must of course be an else to act as an fallback. M +3-3applets/taskmanager/package/contents/ui/ConfigBehavior.qml M +4-4applets/taskmanager/package/contents/ui/code/tools.js https://invent.kde.org/plasma/plasma-desktop/commit/43a1a5b01536c596b1ab7395f1f294ddafb6360c -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 424259] plasmashell produces a lot of warnings in the journal
https://bugs.kde.org/show_bug.cgi?id=424259 David Edmundson changed: What|Removed |Added CC||aoude...@outlook.com --- Comment #5 from David Edmundson --- *** Bug 425051 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 425051] Debug logging and useless logging in system log by qt and plasma5 programs
https://bugs.kde.org/show_bug.cgi?id=425051 David Edmundson changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |DUPLICATE Severity|major |task --- Comment #4 from David Edmundson --- *** This bug has been marked as a duplicate of bug 424259 *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 425051] Debug logging and useless logging in system log by qt and plasma5 programs
https://bugs.kde.org/show_bug.cgi?id=425051 --- Comment #3 from David Edmundson --- Plasmashell now disables these warnings internally. >There is a KCM panel "User Feedback" in Systemsetting. I don't think we want to conflate local logs with telemetry. They're very different things. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 412943] Use System Monitor Profile checkbox attributes wrong profile to screens, breaking color management
https://bugs.kde.org/show_bug.cgi?id=412943 --- Comment #10 from Tymond --- Git commit 77f6562d503686816cb728122dfdaa1bb0168aff by Agata Cacko. Committed on 06/08/2020 at 14:06. Pushed by tymond into branch 'master'. Show display names in Color Management -> Display Before this commit, user would have to figure out on their own which display is which. Because of a bug in the system assigning color profiles to displays, the automatic way doesn't always work so the user needs to assign color profiles on their own. Before this commit the dialog only showed "Screen 1, Screen 2". This commit adds following information: - name - if model is not null, add model; if it is null, add manufacturer info - resolution It is also shortened so the maximum length is 25 characters. M +40 -3libs/ui/dialogs/kis_dlg_preferences.cc https://invent.kde.org/graphics/krita/commit/77f6562d503686816cb728122dfdaa1bb0168aff -- You are receiving this mail because: You are watching all bug changes.
[gcompris] [Bug 425062] Apps does not run properly. no window open.
https://bugs.kde.org/show_bug.cgi?id=425062 --- Comment #2 from anim...@gmail.com --- This is weird, here the application launches properly, using macOS 10.13.6 too, and I had report from other users that it works fine for them too. It could be an issue with the OpenGL support on your computer... Please try this: -open the configuration file gcompris-qt.conf with TextEdit (or another simple text editor of your choice), which is in /Users/username/Library/Preferences/gcompris/ -replace the line renderer=auto with renderer=software -save the file, and restart gcompris This will activate the software-rendering mode, which is not using OpenGL at all. I hope this will fix this issue on your computer. Side note: while checking again, I noticed that actually I didn't sign properly the latest application (the .dmg was signed but not the .app inside). I just fixed it and updated a new .dmg . It was probably not the cause of your issue, but it's still better to have it properly signed... -- You are receiving this mail because: You are watching all bug changes.
[frameworks-knewstuff] [Bug 417985] Addons from KDE Store removed via KCMs are still listed as installed in respective GHNS window
https://bugs.kde.org/show_bug.cgi?id=417985 --- Comment #9 from Nate Graham --- Thank for your work on this, Dan! Good stuff. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 425032] Fallback setting for new grouped task behavior does not work
https://bugs.kde.org/show_bug.cgi?id=425032 Nate Graham changed: What|Removed |Added CC||n...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 425051] Debug logging and useless logging in system log by qt and plasma5 programs
https://bugs.kde.org/show_bug.cgi?id=425051 --- Comment #2 from Aurélien Oudelet (auroud85_fr) --- I agree distributions should not deactivate that logging with an ENV setting. BUT, these logging should not be output at warning level: there is any broken functionality, GUI "just works" some. Listening hard-drives (not SSD), use of Plasma produces more noises from that harddrives than other DE. These logging fills up to much datas to journal, encumbering it, degrades performance and reduces lifetime of these supports. Mounting /var/log as tmpfs workarounds lifetime but it not a viable solution for end-users. This is an upstream bug, not in Mageia RPM. Suggestion: There is a KCM panel "User Feedback" in Systemsetting. These debug or notice level logs should be activated by a checkbox in this KCM Systemsettings. Some awesome developer should place this checkbox there or he should make a solution by disabling all such logging if user deactivates all feedback. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 425056] KWin crashes/dies after resume from sleep
https://bugs.kde.org/show_bug.cgi?id=425056 David Edmundson changed: What|Removed |Added CC||arthur.huil...@free.fr, ||k...@davidedmundson.co.uk -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 423672] org.kde.pim.imapresource: Failed to create folder on server: "Create failed, server replied: ... NO Mailbox already exists ... [ ALREADYEXISTS ]"
https://bugs.kde.org/show_bug.cgi?id=423672 Christian Mollekopf changed: What|Removed |Added Latest Commit|https://invent.kde.org/pim/ |https://invent.kde.org/pim/ |kimap/commit/ee2900e3539483 |kimap2/commit/ce0e9873d3a89 |b6f3d5eadfcf8cfc9c6ed42abe |7fee7fd9f8f7649ef4abd3c4627 --- Comment #6 from Christian Mollekopf --- Git commit ce0e9873d3a897fee7fd9f8f7649ef4abd3c4627 by Christian Mollekopf, on behalf of Dennis Schridde. Committed on 06/08/2020 at 12:59. Pushed by cmollekopf into branch 'master'. Idempotent CREATE and DELETE If CREATE fails with an ALREADYEXISTS response code, that is not an error since the intended result (the object existing at the target location) has been achieved. Likewise, if DELETE fails with an NONEXISTENT response code, that is not an error since the intended result (the object being gone from the target location) has been achieved. Please note that for RENAME response code ALREADYEXISTS *is* an error since the content of the source folder was not moved as intended. cf. https://tools.ietf.org/html/rfc5530#section-3 M +27 -0src/createjob.cpp M +2-1src/createjob.h M +27 -0src/deletejob.cpp M +2-1src/deletejob.h https://invent.kde.org/pim/kimap2/commit/ce0e9873d3a897fee7fd9f8f7649ef4abd3c4627 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 423817] KWin/KDE freezes with Steam Proton
https://bugs.kde.org/show_bug.cgi?id=423817 David Edmundson changed: What|Removed |Added CC||arthur.huil...@free.fr -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 425075] New: "Straight line" annotation is always semi-transparent
https://bugs.kde.org/show_bug.cgi?id=425075 Bug ID: 425075 Summary: "Straight line" annotation is always semi-transparent Product: okular Version: 1.10.2 Platform: openSUSE RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: okular-de...@kde.org Reporter: alexander.shchadi...@gmail.com Target Milestone: --- SUMMARY An object "Straight line" used for annotating is always semi-transparent and does not respect "Opacity" setting. STEPS TO REPRODUCE 1. Open any image file supported by Okular. 2. Press F6 to open "Review" toolbar. 3. Press 5 to activate "Straight line" tool. 4. Make two clicks with LMB on the image view to create a line. OBSERVED RESULT The line is semi-transparent, despite its "Opacity" is 100%. EXPECTED RESULT The line is opaque. SOFTWARE/OS VERSIONS openSUSE Leap 15.2 KDE Plasma Version: 5.18.5 KDE Frameworks Version: 5.71.0 Qt Version: 5.12.7 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 412101] Wayland session does not remember the last used keyboard layout. The first keyboard layout listed in "layouts" tab of the "Keyboard" kcm is always used after login instead.
https://bugs.kde.org/show_bug.cgi?id=412101 Andrey changed: What|Removed |Added Resolution|--- |FIXED Status|REOPENED|RESOLVED --- Comment #20 from Andrey --- Since the crash bug 420077 we depend on is fixed now I'm closing this, feel free to reopen in case of any problems. If testing on Neon, make sure the relevant commit is built in: https://build.neon.kde.org/view/3%20unstable%20%E2%98%A3%20git%20master/job/bionic_unstable_kde_kwin/changes -- You are receiving this mail because: You are watching all bug changes.
[umbrello] [Bug 424861] Zoom control is very difficult on laptops a with touchpad
https://bugs.kde.org/show_bug.cgi?id=424861 Robert Hairgrove changed: What|Removed |Added Resolution|--- |NOT A BUG Status|REPORTED|RESOLVED --- Comment #1 from Robert Hairgrove --- In the meantime, I have discovered that the unwanted zooming disappears if the touchpad is touched at the lower left corner while dragging with the other hand. Apparently, the system sends mouse wheel events to Umbrello but only if the upper left corner is involved. The option remains as whether or not to make this a configurable feature? IOW, a check box that the user can set to completely ignore the wheel event? It is always possible to zoom by using the slider or the spin box at the bottom right of the view. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 330356] Panel auto-hide stops working after using desktop for a while.
https://bugs.kde.org/show_bug.cgi?id=330356 --- Comment #32 from RJVB --- And FWIW, that wm_state did NOT get unset after I applied the update or even disabled the update notifier thingy. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 396086] Changing elements order takes near 5 minutes in a folder with 50 images
https://bugs.kde.org/show_bug.cgi?id=396086 Rafael Linux User changed: What|Removed |Added Attachment #114531|0 |1 is obsolete|| --- Comment #50 from Rafael Linux User --- Created attachment 130679 --> https://bugs.kde.org/attachment.cgi?id=130679=edit New script (2020) to create 4 folders with 10k distinct images each one This script try to create an album similar to real life folders/images. Creates 1 folder with 4 subfolders (level 1) with 4 subfolders (level 2) each one. Inside each one of this folders in level 2 are created 2500 jpg images with distinct resolution and content. I made it cause it's very useful to check some issues like this related when sorting by filename. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 420077] logout from Wayland session makes kwin to crash
https://bugs.kde.org/show_bug.cgi?id=420077 David Edmundson changed: What|Removed |Added CC||k...@davidedmundson.co.uk Resolution|--- |FIXED Status|CONFIRMED |RESOLVED --- Comment #9 from David Edmundson --- davidedmundson wrote: > @bug_id = 420077 > @bug_status = RESOLVED > @resolution = FIXED > @cf_commitlink = > https://invent.kde.org/plasma/kwin/commit/307a9bc5590f6f82b279a611b1f406bbd423687e > > Git commit 307a9bc5590f6f82b279a611b1f406bbd423687e by David Edmundson, on > behalf of Andrey Butirsky. > Committed on 06/08/2020 at 12:21. > Pushed by davidedmundson into branch 'master'. > > Avoid crash in KWin on Session leave > > - hunk of original commit e8a1f8ecc seems was lost during a94be708e merge, > so restoring it again > - add missing check > > Original Differential Revision: https://phabricator.kde.org/D28889 > > M +7-0plugins/platforms/drm/drm_output.cpp > > https://invent.kde.org/plasma/kwin/commit/307a9bc5590f6f82b279a611b1f406bbd423687e -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 412101] Wayland session does not remember the last used keyboard layout. The first keyboard layout listed in "layouts" tab of the "Keyboard" kcm is always used after login instead.
https://bugs.kde.org/show_bug.cgi?id=412101 Bug 412101 depends on bug 420077, which changed state. Bug 420077 Summary: logout from Wayland session makes kwin to crash https://bugs.kde.org/show_bug.cgi?id=420077 What|Removed |Added Status|CONFIRMED |RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 423817] KWin/KDE freezes with Steam Proton
https://bugs.kde.org/show_bug.cgi?id=423817 --- Comment #6 from David Edmundson --- What does seem to help is compositing being always enabled (which gives you a personal workaround, you can just disable "Allow applications to block compositing") -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 425074] Dolphin crashes while removing several folders with 2500 files each one
https://bugs.kde.org/show_bug.cgi?id=425074
Rafael Linux User changed:
What|Removed |Added
CC||rafael.linux.u...@gmail.com
--- Comment #1 from Rafael Linux User ---
I was trying to erase with Shift+Supr the root folder created by this own
script:
#!/bin/bash
# This script will create 4 folders with 1 DISTINCT empty files each one
ImagesRootFolder='Fractal_images_folder'
mkdir $ImagesRootFolder
echo "Creating '$ImagesRootFolder' folder"
for Level_1 in {A..D}
do
Folder_Level_1="$ImagesRootFolder/Folder_10k_images_$Level_1"
echo "Creating '$Folder_Level_1' subfolder "
mkdir $Folder_Level_1
for Level_2 in {1..4}
do
Folder_Level_2="$Folder_Level_1/$Level_2"
echo -n "Creating '$Folder_Level_2' subfolder and generating 25000
images ... "
mkdir $Folder_Level_2
i=1
sp="/-\|"
for value in {1..2500}
do
printf "\b${sp:i++%${#sp}:1}"
Image_filename=Image_$Level_1$Level_2_$(printf "%05d" $value)
touch $Folder_Level_2/$Image_filename.jpg
convert -size $(shuf -i 500-1024 -n 1)x$(shuf -i 500-1024 -n 1)
plasma:fractal "$Folder_Level_2/$Image_filename.jpg"
done
echo " created"
done
done
echo "Process finished"
--
You are receiving this mail because:
You are watching all bug changes.
[krita] [Bug 425060] Chronological error in Documents section of Krita scripting school
https://bugs.kde.org/show_bug.cgi?id=425060 Scott Petrovic changed: What|Removed |Added Resolution|--- |FIXED Status|ASSIGNED|RESOLVED --- Comment #1 from Scott Petrovic --- Thanks for the report. I just updated that page a bit with updated instructions. I had a feeling there were going to be things like this that came up. I originally combined the layers and document explanation in one lesson. Then separated them out into their own topics as wrote more. Thanks for the feedback. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 423817] KWin/KDE freezes with Steam Proton
https://bugs.kde.org/show_bug.cgi?id=423817 --- Comment #5 from David Edmundson --- For me in Openbox and tabbing in/out of "World of Warplanes", a proton game seemed to result in the symptoms you described. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 425074] New: Dolphin crashes while removing several folders with 2500 files each one
https://bugs.kde.org/show_bug.cgi?id=425074 Bug ID: 425074 Summary: Dolphin crashes while removing several folders with 2500 files each one Product: dolphin Version: 20.07.80 Platform: openSUSE RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: rafael.linux.u...@gmail.com CC: kfm-de...@kde.org Target Milestone: --- Application: dolphin (20.07.80) Qt Version: 5.15.0 Frameworks Version: 5.72.0 Operating System: Linux 5.3.18-lp152.33-default x86_64 Windowing system: X11 Distribution: openSUSE Leap 15.2 -- Information about the crash: - What I was doing when the application crashed: Using Dolphin to delete (not to trash folder, just removing completely with Shift+Supr) The crash can be reproduced every time. -- Backtrace: Application: Dolphin (dolphin), signal: Aborted [KCrash Handler] #4 0x7f9348c26520 in raise () from /lib64/libc.so.6 #5 0x7f9348c27b01 in abort () from /lib64/libc.so.6 #6 0x7f9348c69957 in __libc_message () from /lib64/libc.so.6 #7 0x7f9348c70173 in malloc_printerr () from /lib64/libc.so.6 #8 0x7f9348c71a79 in _int_free () from /lib64/libc.so.6 #9 0x7f934892a1a0 in KFileItemModel::removeItems(KItemRangeList const&, KFileItemModel::RemoveItemsBehavior) () from /usr/lib64/libdolphinprivate.so.5 #10 0x7f93489374ea in KFileItemModel::slotItemsDeleted(KFileItemList const&) () from /usr/lib64/libdolphinprivate.so.5 #11 0x7f93425b2527 in QtPrivate::QSlotObjectBase::call (a=0x7ffe763e5e50, r=0x5607257af2d0, this=) at ../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398 #12 doActivate (sender=0x560725d0b160, signal_index=15, argv=0x7ffe763e5e50) at kernel/qobject.cpp:3886 #13 0x7f93425ab9e2 in QMetaObject::activate (sender=, m=m@entry=0x7f934727cfe0 , local_signal_index=local_signal_index@entry=12, argv=argv@entry=0x7ffe763e5e50) at kernel/qobject.cpp:3946 #14 0x7f93470055a5 in KCoreDirLister::itemsDeleted (this=, _t1=...) at /usr/src/debug/kio-5.72.0-lp152.298.1.x86_64/build/src/core/KF5KIOCore_autogen/include/moc_kcoredirlister.cpp:495 #15 0x7f9347007ca0 in KCoreDirLister::Private::emitItemsDeleted (this=0x560725d8bcc0, _items=...) at /usr/src/debug/kio-5.72.0-lp152.298.1.x86_64/src/core/kcoredirlister.cpp:2570 #16 0x7f934700d563 in KCoreDirListerCache::itemsDeleted (this=this@entry=0x7f93472803c0 <(anonymous namespace)::Q_QGS_kDirListerCache::innerFunction()::holder>, listers=..., deletedItems=...) at /usr/src/debug/kio-5.72.0-lp152.298.1.x86_64/src/core/kcoredirlister.cpp:1927 #17 0x7f934700dc28 in KCoreDirListerCache::slotFilesRemoved (this=this@entry=0x7f93472803c0 <(anonymous namespace)::Q_QGS_kDirListerCache::innerFunction()::holder>, fileList=...) at /usr/src/debug/kio-5.72.0-lp152.298.1.x86_64/src/core/kcoredirlister.cpp:880 #18 0x7f934700e091 in KCoreDirListerCache::slotFilesRemoved (this=this@entry=0x7f93472803c0 <(anonymous namespace)::Q_QGS_kDirListerCache::innerFunction()::holder>, fileList=...) at /usr/src/debug/kio-5.72.0-lp152.298.1.x86_64/src/core/kcoredirlister.cpp:837 #19 0x7f9347013d2c in KCoreDirListerCache::slotFileDeleted (this=0x7f93472803c0 <(anonymous namespace)::Q_QGS_kDirListerCache::innerFunction()::holder>, path=...) at /usr/src/debug/kio-5.72.0-lp152.298.1.x86_64/src/core/kcoredirlister.cpp:1164 #20 0x7f93425b2527 in QtPrivate::QSlotObjectBase::call (a=0x7ffe763e61b0, r=0x7f93472803c0 <(anonymous namespace)::Q_QGS_kDirListerCache::innerFunction()::holder>, this=) at ../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398 #21 doActivate (sender=0x7f93445c4280 <(anonymous namespace)::Q_QGS_s_pKDirWatchSelf::innerFunction()::holder>, signal_index=5, argv=0x7ffe763e61b0) at kernel/qobject.cpp:3886 #22 0x7f93425ab9e2 in QMetaObject::activate (sender=sender@entry=0x7f93445c4280 <(anonymous namespace)::Q_QGS_s_pKDirWatchSelf::innerFunction()::holder>, m=m@entry=0x7f93445c21e0 , local_signal_index=local_signal_index@entry=2, argv=argv@entry=0x7ffe763e61b0) at kernel/qobject.cpp:3946 #23 0x7f9344350485 in KDirWatch::deleted (this=this@entry=0x7f93445c4280 <(anonymous namespace)::Q_QGS_s_pKDirWatchSelf::innerFunction()::holder>, _t1=...) at /usr/src/debug/kcoreaddons-5.72.0-lp152.230.1.x86_64/build/src/lib/KF5CoreAddons_autogen/include/moc_kdirwatch.cpp:185 #24 0x7f9344351e36 in KDirWatch::setDeleted (this=0x7f93445c4280 <(anonymous namespace)::Q_QGS_s_pKDirWatchSelf::innerFunction()::holder>, _file=...) at /usr/src/debug/kcoreaddons-5.72.0-lp152.230.1.x86_64/src/lib/io/kdirwatch.cpp:2012 #25 0x7f93425a900b in QObject::event (this=0x7f93445c4280 <(anonymous namespace)::Q_QGS_s_pKDirWatchSelf::innerFunction()::holder>, e=0x56072bebba90) at kernel/qobject.cpp:1314 #26 0x7f93439912fc in
[plasmashell] [Bug 330356] Panel auto-hide stops working after using desktop for a while.
https://bugs.kde.org/show_bug.cgi?id=330356 --- Comment #31 from RJVB --- Hah, I think my assessment wasn't wrong. I use xfwm4 instead of KWin (sorry guys :)) and for once I ran it in a terminal. When the update notifier came on, I saw this: (xfwm4:21597): xfwm4-WARNING **: 13:58:49.644: Unmanaged net_wm_state (window 0x260027c, atom "_NET_WM_STATE_STAYS_ON_TOP") (xfwm4:21597): xfwm4-WARNING **: 13:59:34.096: Unmanaged net_wm_state (window 0x268, atom "_NET_WM_STATE_STAYS_ON_TOP") (xfwm4:21597): xfwm4-WARNING **: 14:02:15.715: Unmanaged net_wm_state (window 0x268, atom "_NET_WM_STATE_STAYS_ON_TOP") (xfwm4:21597): xfwm4-WARNING **: 14:02:50.340: Unmanaged net_wm_state (window 0x25c, atom "_NET_WM_STATE_STAYS_ON_TOP") I think that proves that the panel does indeed sometimes override our user preference for it NOT to be on top all the time. -- You are receiving this mail because: You are watching all bug changes.
[muon] [Bug 425073] New: Can't configure software sources through Muon package manager
https://bugs.kde.org/show_bug.cgi?id=425073 Bug ID: 425073 Summary: Can't configure software sources through Muon package manager Product: muon Version: 5.8.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: muon Assignee: echidna...@kubuntu.org Reporter: lordofthecof...@gmail.com CC: silh...@gmail.com Target Milestone: --- Created attachment 130678 --> https://bugs.kde.org/attachment.cgi?id=130678=edit dialog window error SUMMARY "Configure software sources" from muon package manager does not work, but it works through Discover package manager. STEPS TO REPRODUCE 1. Muon and software-properties-qt or common already installed in a 18.04 based 2. Upgrade to 20.04, run muon (alt+F2 and type muon) 3. configure software sources OBSERVED RESULT It appears a dialog that says "software-properties-kde" not present. However, it doesn't exist in repositories. Installing from konsole and apt says that package software-properties-kde is (now) obsolete and the replacement is "software-properties-qt". But installing this new package doesn't fix the problem and it persists. 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.
[krusader] [Bug 424189] Krusader file copy failing for larger files in Ubuntu 20.04
https://bugs.kde.org/show_bug.cgi?id=424189 --- Comment #3 from Judy Kerr --- (In reply to Christoph Feck from comment #1) > Is the same issue also visible with Dolphin? It could be an issue with a > component that is used by Krusader, instead of in Krusader itself. Hi Christoph, we have tried again using Dolphin, and the same error occurs. When trying to manually copy a larger file (e.g. 19 MB, 64 MB) it starts copying but stops part way through with following error message:- Cannot copy file from /local/a.jpg to /remote/a.jpg (Errno:95) It gives option to retry the copy but the same thing happens. I have found one report of an identical issue with Dolphin from 11 months ago: https://www.reddit.com/r/kde/comments/cq45rp/gvfs_mounts_with_dolphin_error_95/ The person who raised this thought it might be due to to something deciding that there was not enough space on the receiving partition to do the copy, but no-one answered his post so it doesn't help much (except to confirm that someone else has seen this). -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 425072] New: KDE Telepathy Contact List package still provided by ubuntu, throws linker error on launch
https://bugs.kde.org/show_bug.cgi?id=425072 Bug ID: 425072 Summary: KDE Telepathy Contact List package still provided by ubuntu, throws linker error on launch Product: neon Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Packages User Edition Assignee: neon-b...@kde.org Reporter: mar...@harrisonland.co.uk CC: j...@jriddell.org, neon-b...@kde.org, sit...@kde.org Target Milestone: --- SUMMARY KDE Neon provides its own package builds for most of the KDE telepathy components, but does not provide a package for kde-telepathy-contact-list. This package is still provided by upstream Ubuntu, and attempting to run ktp-contactlist produces the error: ktp-contactlist: symbol lookup error: ktp-contactlist: undefined symbol: _ZN3KTp14GlobalPresence11setPresenceERKNS_8PresenceE SOFTWARE/OS VERSIONS Operating System: KDE neon 5.19 KDE Plasma Version: 5.19.4 KDE Frameworks Version: 5.72.0 Qt Version: 5.14.2 Kernel Version: 4.15.0-112-generic OS Type: 64-bit Processors: 4 × Intel® Core™ i5-6200U CPU @ 2.30GHz Memory: 3.8 GiB of RAM Graphics Processor: Mesa DRI Intel® HD Graphics 520 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 425071] New: Option to show all notifications in fullscreen windows
https://bugs.kde.org/show_bug.cgi?id=425071 Bug ID: 425071 Summary: Option to show all notifications in fullscreen windows Product: plasmashell Version: 5.19.4 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Notifications Assignee: k...@privat.broulik.de Reporter: adamantga...@gmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 SUMMARY Currently Plasma shows only urgent notifications if fullscreen window is open. I guess that the reasoning behind it is that when people are giving presentations, playing games or watching movies - they don't want notifications to pop up on the screen. However, that is not always the case. Most of the time when I'm watching a video or playing a game, I want to be notified about important messages. Currently I have to rely on messaging application playing a sound when something happens, but that's very unreliable (because the sound from video or game may "hide" the message sound). I'm OK with it being the default behavior (although it's weird, considering that there's "Do not disturb" checkbox exactly for when you don't want to be disturbed), but an option to show all notifications in fullscreen windows would be extremely useful. STEPS TO REPRODUCE 1. Open a fullscreen window. 2. Receive a non-urgent notification. OBSERVED RESULT Notification does not appear. EXPECTED RESULT If "Do not disturb" mode turned off - notification to appear. SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 5.19.4 KDE Frameworks Version: 5.72.0 Qt Version: 5.15.0 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 425060] Chronological error in Documents section of Krita scripting school
https://bugs.kde.org/show_bug.cgi?id=425060 Scott Petrovic changed: What|Removed |Added Ever confirmed|0 |1 CC||scottpetro...@gmail.com Assignee|krita-bugs-n...@kde.org |scottpetro...@gmail.com Status|REPORTED|ASSIGNED -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 424779] Embedded links not recognised in PDF file
https://bugs.kde.org/show_bug.cgi?id=424779 newpt...@gmail.com changed: What|Removed |Added CC||newpt...@gmail.com --- Comment #1 from newpt...@gmail.com --- I have noticed a similar problem. If I annotate something, then the hyperlinks stop working. I have to close the PDF and open it again for it to work. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 419509] Appimage git 62b9516 (Apr 1 build) crashes after splash sceen
https://bugs.kde.org/show_bug.cgi?id=419509 Boudewijn Rempt changed: What|Removed |Added Status|CONFIRMED |ASSIGNED Assignee|krita-bugs-n...@kde.org |b...@valdyas.org -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 419509] Appimage git 62b9516 (Apr 1 build) crashes after splash sceen
https://bugs.kde.org/show_bug.cgi?id=419509 Boudewijn Rempt changed: What|Removed |Added Status|REPORTED|CONFIRMED Ever confirmed|0 |1 --- Comment #12 from Boudewijn Rempt --- I have reproduced the crash. It happens consistently when a preset uses a brush tip from an abr file. -- You are receiving this mail because: You are watching all bug changes.
[krusader] [Bug 425070] New: Krusader crashes when right-click on a file
https://bugs.kde.org/show_bug.cgi?id=425070 Bug ID: 425070 Summary: Krusader crashes when right-click on a file Product: krusader Version: unspecified Platform: Compiled Sources OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: krusader-bugs-n...@kde.org Reporter: dab...@gmail.com CC: krusader-bugs-n...@kde.org Target Milestone: --- Application: krusader (2.7.2 "Peace of Mind") (Compiled from sources) Qt Version: 5.14.2 Frameworks Version: 5.70.0 Operating System: Linux 5.4.48-gentoo-8 x86_64 Windowing system: X11 Distribution: Gentoo/Linux -- Information about the crash: - What I was doing when the application crashed: Right-clicked on "Nepotvrzeno 939731.crdownload" file. Then the Krusader crashed. The crash can be reproduced every time. -- Backtrace: Application: Krusader (krusader), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7fea710217c0 (LWP 6956))] Thread 3 (Thread 0x7fea67fff700 (LWP 6958)): #0 __GI___libc_read (nbytes=16, buf=0x7fea67ffeba0, fd=19) at ../sysdeps/unix/sysv/linux/read.c:26 #1 __GI___libc_read (fd=19, buf=buf@entry=0x7fea67ffeba0, nbytes=nbytes@entry=16) at ../sysdeps/unix/sysv/linux/read.c:24 #2 0x7fea731f621f in read (__nbytes=16, __buf=0x7fea67ffeba0, __fd=) at /usr/include/bits/unistd.h:44 #3 g_wakeup_acknowledge (wakeup=0x562fef3662b0) at ../glib-2.62.6/glib/gwakeup.c:210 #4 0x7fea731ac40e in g_main_context_check (context=context@entry=0x7fea6c20, max_priority=2147483647, fds=fds@entry=0x7fea6001c000, n_fds=n_fds@entry=1) at ../glib-2.62.6/glib/gmain.c:3732 #5 0x7fea731ac893 in g_main_context_iterate (context=context@entry=0x7fea6c20, block=block@entry=1, dispatch=dispatch@entry=1, self=) at ../glib-2.62.6/glib/gmain.c:3951 #6 0x7fea731aca0f in g_main_context_iteration (context=0x7fea6c20, may_block=may_block@entry=1) at ../glib-2.62.6/glib/gmain.c:4015 #7 0x7fea748b7d2b in QEventDispatcherGlib::processEvents (this=0x7fea6b60, flags=...) at /var/tmp/portage/dev-qt/qtcore-5.14.2/work/qtbase-everywhere-src-5.14.2/src/corelib/kernel/qeventdispatcher_glib.cpp:425 #8 0x7fea748604fb in QEventLoop::exec (this=this@entry=0x7fea67ffedb0, flags=..., flags@entry=...) at /var/tmp/portage/dev-qt/qtcore-5.14.2/work/qtbase-everywhere-src-5.14.2/include/QtCore/../../src/corelib/global/qflags.h:136 #9 0x7fea746aaf5e in QThread::exec (this=this@entry=0x7fea759bcda0 <(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at /var/tmp/portage/dev-qt/qtcore-5.14.2/work/qtbase-everywhere-src-5.14.2/include/QtCore/../../src/corelib/global/qflags.h:118 #10 0x7fea75937557 in QDBusConnectionManager::run (this=0x7fea759bcda0 <(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at /var/tmp/portage/dev-qt/qtdbus-5.14.2/work/qtbase-everywhere-src-5.14.2/src/dbus/qdbusconnection.cpp:179 #11 0x7fea746abfaf in QThreadPrivate::start (arg=0x7fea759bcda0 <(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at /var/tmp/portage/dev-qt/qtcore-5.14.2/work/qtbase-everywhere-src-5.14.2/src/corelib/thread/qthread_unix.cpp:342 #12 0x7fea73c0e027 in start_thread (arg=) at pthread_create.c:479 #13 0x7fea74168c4f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 2 (Thread 0x7fea70649700 (LWP 6957)): #0 0x7fea7415e15f in __GI___poll (fds=fds@entry=0x7fea70648ce8, nfds=nfds@entry=1, timeout=timeout@entry=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7fea73b38d72 in poll (__timeout=-1, __nfds=1, __fds=0x7fea70648ce8) at /usr/include/bits/poll2.h:46 #2 _xcb_conn_wait (c=c@entry=0x562feee3efb0, cond=cond@entry=0x562feee3eff0, vector=vector@entry=0x0, count=count@entry=0x0) at /var/tmp/portage/x11-libs/libxcb-1.14/work/libxcb-1.14/src/xcb_conn.c:480 #3 0x7fea73b3aa9a in xcb_wait_for_event (c=c@entry=0x562feee3efb0) at /var/tmp/portage/x11-libs/libxcb-1.14/work/libxcb-1.14/src/xcb_in.c:697 #4 0x7fea7081f428 in QXcbEventQueue::run (this=0x562feee35340) at /var/tmp/portage/dev-qt/qtgui-5.14.2/work/qtbase-everywhere-src-5.14.2/src/plugins/platforms/xcb/qxcbeventqueue.cpp:228 #5 0x7fea746abfaf in QThreadPrivate::start (arg=0x562feee35340) at /var/tmp/portage/dev-qt/qtcore-5.14.2/work/qtbase-everywhere-src-5.14.2/src/corelib/thread/qthread_unix.cpp:342 #6 0x7fea73c0e027 in start_thread (arg=) at pthread_create.c:479 #7 0x7fea74168c4f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 1 (Thread 0x7fea710217c0 (LWP 6956)): [KCrash Handler] #6 KrView::setSelected (this=0x18, fileitem=0x562fefe18f00, select=true) at /var/tmp/portage/kde-misc/krusader-2.7.2/work/krusader-2.7.2/krusader/Panel/PanelView/krview.cpp:1186 #7 0x562fecef3575 in KrViewItem::setSelected
[plasmashell] [Bug 396100] Dragging a file over taskbar and moving it out crashes plasma
https://bugs.kde.org/show_bug.cgi?id=396100 --- Comment #5 from Patrick Silva --- I'm not the reporter, but this crash is still reproducible on neon unstable. Possibly duplicate of bug 398440. Operating System: KDE neon Unstable Edition KDE Plasma Version: 5.19.80 KDE Frameworks Version: 5.73.0 Qt Version: 5.14.2 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 423817] KWin/KDE freezes with Steam Proton
https://bugs.kde.org/show_bug.cgi?id=423817 --- Comment #4 from David Edmundson --- But we definitely have various issues with the new Nvidia update. Can you confirm if you see the same results running on openbox? I will try to do the same. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 424259] plasmashell produces a lot of warnings in the journal
https://bugs.kde.org/show_bug.cgi?id=424259 Aleix Pol changed: What|Removed |Added Resolution|--- |FIXED Latest Commit||https://invent.kde.org/plas ||ma/plasma-workspace/commit/ ||5aebd1a8c122a30f950582832ab ||3d6cf1bc978f7 Status|ASSIGNED|RESOLVED --- Comment #4 from Aleix Pol --- Git commit 5aebd1a8c122a30f950582832ab3d6cf1bc978f7 by Aleix Pol Gonzalez, on behalf of David Edmundson. Committed on 06/08/2020 at 10:56. Pushed by davidedmundson into branch 'master'. Fitler out annoying QML warnings Qt 5.15 introduces a new syntax for connections. Framework code can't port away due to having to support Qt5.12 which does not include the new syntax. This filters out the category. We should remove this once we depend on Qt5.15 in frameworks. M +18 -0shell/main.cpp https://invent.kde.org/plasma/plasma-workspace/commit/5aebd1a8c122a30f950582832ab3d6cf1bc978f7 -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 263042] XFA Forms are not supported
https://bugs.kde.org/show_bug.cgi?id=263042 --- Comment #27 from Reissner --- hm but okular gives a warning.. at least in my version. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 424817] Ugly rendering of images containing text in PDF files
https://bugs.kde.org/show_bug.cgi?id=424817 --- Comment #15 from Christoph Feck --- In qpdfview you can select the rendering engine that poppler should use (Splash vs. Arthur), their rendering might be different. There is also a Cairo-based engine that GTK based viewers use. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 423842] Can't show the panel with touch
https://bugs.kde.org/show_bug.cgi?id=423842 --- Comment #4 from Zamundaaa --- mostly, yes. The screen edge still disappears after you show the panel with touch but I'm working on fixing that as well :) -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 425069] New: Extreme lagg when disabling laptop display
https://bugs.kde.org/show_bug.cgi?id=425069 Bug ID: 425069 Summary: Extreme lagg when disabling laptop display Product: kwin Version: 5.19.3 Platform: Manjaro OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kwin-bugs-n...@kde.org Reporter: martijn.j.vogel...@outlook.com Target Milestone: --- Created attachment 130677 --> https://bugs.kde.org/attachment.cgi?id=130677=edit Lagg while dragging applications SUMMARY Not sure if KWIN is the right place. When disabling my laptop display and only using my external monitor extreme lagg occurs. My CPU is normally 5-10% in idle and after disabling the laptop display it goes down to 0-1%. It looks like some kind of power setting is triggered when the laptop screen is disabled. Everything works fine when using both the laptop screen and external monitor. STEPS TO REPRODUCE 1. Install Kubuntu 20.04 LTS or Install Manjaro 20.0.3 2. Connect external monitor using HDMI. 3. Enable external monitor, disable laptop monitor. OBSERVED RESULT When the laptop display is disabled extreme lagg occurs. Button clicks take ages to register while dragging an application accros the screen the old-school windows trail appears(see attachment). The CPU furthermore goes from 5-10% in idle to <1 % in idle. EXPECTED RESULT Normal behaviour, cpu usages remaining the same, no lagg. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Manjaro with KDE Plasma 5.19.3 AND Kubuntu 20.04 with KDE Plasma 5.18. KDE Plasma Version: 5.19.3 with Manjaro AND 5.18 with Kubuntu KDE Frameworks Version: 5.72.0 in Manjaro, Not sure about kubuntu Qt Version: 5.15.0 in Manjaro, Not sure about kubuntu. ADDITIONAL INFORMATION System info: HP-Pavilion 15-bc075nd I7 6700hq with integrated Intel® HD Graphics 530 Nvidia 960m External monitor: LG 29UM59-P Ultrawide 2560x1080 Display settings: Laptop Screen: Disabled External monitor: Enabled + Primary Compositor settings: Scale method: Accurate Rendering backend: OpenGL 3.1 Tearing prevention: Automatic Keep window thumbnails: Only for shown windows -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 425020] baloosearch's search support for Chinese, Japanese and Korean is very weak.
https://bugs.kde.org/show_bug.cgi?id=425020 --- Comment #18 from Christoph Feck --- ICU data includes a dictionary of more than 300,000 CJK words (4 MB) and is automatically handled when detecting a CJK script. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 425020] baloosearch's search support for Chinese, Japanese and Korean is very weak.
https://bugs.kde.org/show_bug.cgi?id=425020 --- Comment #17 from 2wxsy5823...@opayq.com --- > ICU BreakIterators can be used to locate the following kinds of text > boundaries: > 1. Character Boundary > 2. Word Boundary > 3. Line-break Boundary > 4. Sentence Boundary For Chinese and Japanese, I believe "Character Boundary" is applicable but "Word Boundary" is not. Since these two languages do not use spaces to separate words [1], I believe word segmentation [2] is difficult unless dictionaries or AI are used. Links: [1] https://en.wikipedia.org/wiki/Word_divider [2] https://en.wikipedia.org/wiki/Text_segmentation#Word_segmentation -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 424817] Ugly rendering of images containing text in PDF files
https://bugs.kde.org/show_bug.cgi?id=424817 --- Comment #14 from Jan Rathmann --- (In reply to Albert Astals Cid from comment #13) > > Anyhow, not an Okular bug, poppler is doing the resampling, so it needs a > bug there https://gitlab.freedesktop.org/poppler/poppler/-/issues I did some further testing with other pdf readers based on poppler: qpdfview, Atril, Zathura (all on KDE Neon and Kubuntu 20.04) With Atril and Zathura the rendering is fine at all zoom levels (like with Evince). Interestingly, qpdfview shows the same "ugly" rendering as Okular. Since Okular and qpdfview are in contrast to the other pdf viewers both based on Qt and they are the only one who have this weird rendering, would it be possible that this is somehow a bug in Qt and not in poppler? Otherwise I can report the bug to poppler upstream. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 425068] New: plasma crashes on start menu
https://bugs.kde.org/show_bug.cgi?id=425068 Bug ID: 425068 Summary: plasma crashes on start menu Product: plasmashell Version: 5.18.5 Platform: Fedora RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: kakirem...@outlook.com CC: plasma-b...@kde.org Target Milestone: 1.0 Application: plasmashell (5.18.5) Qt Version: 5.14.2 Frameworks Version: 5.70.0 Operating System: Linux 5.7.11-200.fc32.x86_64+debug x86_64 Windowing system: X11 Distribution: Fedora 32 (KDE Plasma) -- Information about the crash: - What I was doing when the application crashed: I opened Start menu and searched for terminal, i have gone to all apps menu and then the lower bar wasn't available and plasma crashed. -- Backtrace: Application: Plazma (plasmashell), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f4c525223c0 (LWP 2796))] Thread 43 (Thread 0x7f4b7dffb700 (LWP 3690)): #0 0x7f4c5595fe92 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7f4c564b4dab in QWaitConditionPrivate::wait (deadline=..., deadline=..., this=0x55b5b85ca510) at thread/qwaitcondition_unix.cpp:146 #2 QWaitCondition::wait (this=, mutex=0x55b5b857fe00, deadline=...) at thread/qwaitcondition_unix.cpp:225 #3 0x7f4be1499e48 in ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*, bool, bool, bool) () from /lib64/libKF5ThreadWeaver.so.5 #4 0x7f4be149de4c in ThreadWeaver::WorkingHardState::applyForWork(ThreadWeaver::Thread*, bool) () from /lib64/libKF5ThreadWeaver.so.5 #5 0x7f4be14990c6 in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () from /lib64/libKF5ThreadWeaver.so.5 #6 0x7f4be149b7f8 in ThreadWeaver::Thread::run() () from /lib64/libKF5ThreadWeaver.so.5 #7 0x7f4c564af690 in QThreadPrivate::start (arg=0x7f4b84005240) at thread/qthread_unix.cpp:342 #8 0x7f4c55959432 in start_thread () from /lib64/libpthread.so.0 #9 0x7f4c5612e913 in clone () from /lib64/libc.so.6 Thread 42 (Thread 0x7f4b7e7fc700 (LWP 3689)): #0 0x7f4c5595fe92 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7f4c564b4dab in QWaitConditionPrivate::wait (deadline=..., deadline=..., this=0x55b5b85ca510) at thread/qwaitcondition_unix.cpp:146 #2 QWaitCondition::wait (this=, mutex=0x55b5b857fe00, deadline=...) at thread/qwaitcondition_unix.cpp:225 #3 0x7f4be1499e48 in ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*, bool, bool, bool) () from /lib64/libKF5ThreadWeaver.so.5 #4 0x7f4be149de4c in ThreadWeaver::WorkingHardState::applyForWork(ThreadWeaver::Thread*, bool) () from /lib64/libKF5ThreadWeaver.so.5 #5 0x7f4be14990c6 in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () from /lib64/libKF5ThreadWeaver.so.5 #6 0x7f4be149b7f8 in ThreadWeaver::Thread::run() () from /lib64/libKF5ThreadWeaver.so.5 #7 0x7f4c564af690 in QThreadPrivate::start (arg=0x7f4ba0004b10) at thread/qthread_unix.cpp:342 #8 0x7f4c55959432 in start_thread () from /lib64/libpthread.so.0 #9 0x7f4c5612e913 in clone () from /lib64/libc.so.6 Thread 41 (Thread 0x7f4b7effd700 (LWP 3688)): #0 0x7f4c5595fe92 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7f4c564b4dab in QWaitConditionPrivate::wait (deadline=..., deadline=..., this=0x55b5b85ca510) at thread/qwaitcondition_unix.cpp:146 #2 QWaitCondition::wait (this=, mutex=0x55b5b857fe00, deadline=...) at thread/qwaitcondition_unix.cpp:225 #3 0x7f4be1499e48 in ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*, bool, bool, bool) () from /lib64/libKF5ThreadWeaver.so.5 #4 0x7f4be149de4c in ThreadWeaver::WorkingHardState::applyForWork(ThreadWeaver::Thread*, bool) () from /lib64/libKF5ThreadWeaver.so.5 #5 0x7f4be14990c6 in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () from /lib64/libKF5ThreadWeaver.so.5 #6 0x7f4be149b7f8 in ThreadWeaver::Thread::run() () from /lib64/libKF5ThreadWeaver.so.5 #7 0x7f4c564af690 in QThreadPrivate::start (arg=0x7f4bbc005690) at thread/qthread_unix.cpp:342 #8 0x7f4c55959432 in start_thread () from /lib64/libpthread.so.0 #9 0x7f4c5612e913 in clone () from /lib64/libc.so.6 Thread 40 (Thread 0x7f4b7f7fe700 (LWP 3687)): #0 0x7f4c5595fe92 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7f4c564b4dab in QWaitConditionPrivate::wait (deadline=..., deadline=..., this=0x55b5b85ca510) at thread/qwaitcondition_unix.cpp:146 #2 QWaitCondition::wait (this=, mutex=0x55b5b857fe00, deadline=...) at thread/qwaitcondition_unix.cpp:225 #3 0x7f4be1499e48 in
[dolphin] [Bug 425067] recommended to remove Baloo as the default search
https://bugs.kde.org/show_bug.cgi?id=425067 --- Comment #2 from logicinu --- Why should I take the initiative to disable Baloo,Baloo as a search function can not meet the demand, I think this is a wide range of recognition, dolphin with a simple search match on it, Baloo should see the need to actively enable it. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 423817] KWin/KDE freezes with Steam Proton
https://bugs.kde.org/show_bug.cgi?id=423817 David Edmundson changed: What|Removed |Added CC||k...@davidedmundson.co.uk --- Comment #3 from David Edmundson --- >but my problem is slightly different as disabling the compositor does not fix >the bug in my case. >This is very likely a bug in how KWin handles Wine window buffers If compositing is off we're not handling the video buffers. So what makes you say that? -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 425020] baloosearch's search support for Chinese, Japanese and Korean is very weak.
https://bugs.kde.org/show_bug.cgi?id=425020 --- Comment #16 from Christoph Feck --- Nope, it doesn't. It only treats all characters that have the "wordBreak" property set. Source at https://code.qt.io/cgit/qt/qtbase.git/tree/src/corelib/text/qtextboundaryfinder.cpp -- You are receiving this mail because: You are watching all bug changes.
[bugs.kde.org] [Bug 424955] Idea: Add a (temporary) warning regarding the abuse of KDE Bugzilla instance
https://bugs.kde.org/show_bug.cgi?id=424955 --- Comment #6 from Ben Cooksley --- We've received a response from them now, and they hit the same issue we did with regards to identifying the course in question. I've now sent them the information we do have (including the full addresses of those that used their @myseneca.ca addresses) including links to examples here on Bugzilla. It's quite fortunate that one of the students decided to use that course code in their dummy GMail addresses as that is likely to help quite a bit. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 418854] "Update" page does not show the versions of currently installed packages
https://bugs.kde.org/show_bug.cgi?id=418854 --- Comment #5 from Patrick Silva --- Created attachment 130676 --> https://bugs.kde.org/attachment.cgi?id=130676=edit screen recording on Neon unstable Same thing here. This bug just happened again on neon unstable when I clicked on updates notification immediately after login. I have recorded a video. Operating System: KDE neon Unstable Edition KDE Plasma Version: 5.19.80 KDE Frameworks Version: 5.73.0 Qt Version: 5.14.2 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 330356] Panel auto-hide stops working after using desktop for a while.
https://bugs.kde.org/show_bug.cgi?id=330356 RJVB changed: What|Removed |Added CC||rjvber...@gmail.com --- Comment #30 from RJVB --- I'm seeing the same issue (with both autohide and "windows can cover") on my fresh Devuan "Beowulf" install, and I can confirm Vlijmen's remark that this is not a new issue. I tend to get it from time to time on my Plasma4 desktop too (which I'm keeping for a reason on my main workhorse and would install it everywhere if packages still existed: it works!). There, it is always related to a window that "has something to tell me" and shows up highlighted in the task manager; clicking on it (or else on all task man. entries) always fixes the issue in the end. I have a similar experience with the MSWin taskbar: if it won't go back to its designated place it's usually if not always because of some notification that I have to acknowledge (after figuring out which/what it is). So a potential solution might be to provide an additional setting where you can disable the panel coming to the front because of a notification. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 425032] Fallback setting for new grouped task behavior does not work
https://bugs.kde.org/show_bug.cgi?id=425032 Bug Janitor Service changed: What|Removed |Added Ever confirmed|0 |1 Status|REPORTED|ASSIGNED --- Comment #2 from Bug Janitor Service --- A possibly relevant merge request was started @ https://invent.kde.org/plasma/plasma-desktop/-/merge_requests/96 -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 263042] XFA Forms are not supported
https://bugs.kde.org/show_bug.cgi?id=263042 --- Comment #26 from Albert Astals Cid --- (In reply to Reissner from comment #25) > Created attachment 130675 [details] > some official pfd with xfa forms which can be opened in evince. > > The headline says all. It can also be opened with Okular -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 425067] recommended to remove Baloo as the default search
https://bugs.kde.org/show_bug.cgi?id=425067 Christoph Feck changed: What|Removed |Added Resolution|--- |WORKSFORME Status|REPORTED|RESOLVED --- Comment #1 from Christoph Feck --- You can disable Baloo, or even compile Dolphin without Baloo dependencies. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 425020] baloosearch's search support for Chinese, Japanese and Korean is very weak.
https://bugs.kde.org/show_bug.cgi?id=425020 --- Comment #15 from Stefan Brüns --- (In reply to Christoph Feck from comment #14) > Detecting CJK words is possible with ICU: > http://userguide.icu-project.org/boundaryanalysis Baloo uses Qts boundary finder, which in turn uses icu. -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 413368] upgraded to 5.17.x, krunner alt-f2 shortcut stopped working
https://bugs.kde.org/show_bug.cgi?id=413368 vector changed: What|Removed |Added CC||kbar...@blackpanther.hu --- Comment #17 from vector --- I can fixed in blackPanther OS. The problem origin is krunner are renamed to krunner.desktop and old globalshortcuts conflicting with old settings group. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 425020] baloosearch's search support for Chinese, Japanese and Korean is very weak.
https://bugs.kde.org/show_bug.cgi?id=425020 --- Comment #14 from Christoph Feck --- Detecting CJK words is possible with ICU: http://userguide.icu-project.org/boundaryanalysis -- You are receiving this mail because: You are watching all bug changes.
[kdeplasma-addons] [Bug 422839] Adding network interfaces screws the system monitor widgets
https://bugs.kde.org/show_bug.cgi?id=422839 --- Comment #13 from Nicola Mori --- Thanks David, I built a patched version of ksysguard and I confirm that the patch you linked fixes the problem for me. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 425067] New: recommended to remove Baloo as the default search
https://bugs.kde.org/show_bug.cgi?id=425067 Bug ID: 425067 Summary: recommended to remove Baloo as the default search Product: dolphin Version: unspecified Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: search Assignee: dolphin-bugs-n...@kde.org Reporter: logic...@gmail.com CC: kfm-de...@kde.org Target Milestone: --- SUMMARY recommended to remove Baloo as the default search for dolphin, and the corresponding file can not be found all the time. Why use the search based on participle? It is of little help in searching files and is not enough to meet the search needs. 1. Unable to search for symbols. 2. Word segmentation is not detailed enough, such as "bar.mp3" file, search for "mp3" is OK, but search for "3" is not. 3. Chinese search is not supported OBSERVED RESULT bad search EXPECTED RESULT precise search SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 5.19.4 KDE Frameworks Version: 5.72.0 Qt Version: 5.15.0 Kernel Version: 5.7.9-zen1-1-zencjk OS Type: 64-bit Processors: 8 × AMD Ryzen 7 PRO 2700U w/ Radeon Vega Mobile Gfx Memory: 14.6 GiB of RAM Graphics Processor: AMD RAVEN -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 424874] Subsequent searches fail if baloo is disabled
https://bugs.kde.org/show_bug.cgi?id=424874 --- Comment #1 from 2wxsy5823...@opayq.com --- I have Baloo disabled, but I am unable to reproduce the bug. The subsequent searches work as expected for me. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 424594] Individual core system monitor turns into Network monitor, no means to revert.
https://bugs.kde.org/show_bug.cgi?id=424594 David Edmundson changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are watching all bug changes.
[kdeplasma-addons] [Bug 422839] Adding network interfaces screws the system monitor widgets
https://bugs.kde.org/show_bug.cgi?id=422839 David Edmundson changed: What|Removed |Added CC||k...@davidedmundson.co.uk --- Comment #12 from David Edmundson --- Should be fixed by https://invent.kde.org/plasma/ksysguard/-/merge_requests/30 -- You are receiving this mail because: You are watching all bug changes.
[kdeplasma-addons] [Bug 422839] Adding network interfaces screws the system monitor widgets
https://bugs.kde.org/show_bug.cgi?id=422839 David Edmundson changed: What|Removed |Added Resolution|--- |FIXED Status|REPORTED|RESOLVED -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 425020] baloosearch's search support for Chinese, Japanese and Korean is very weak.
https://bugs.kde.org/show_bug.cgi?id=425020 --- Comment #13 from logicinu --- 这样的分词怎么分，都不能满足搜索的需求的，应该是我想错了，不是Baloo的错，是dolphin文件管理器用Baloo当搜索就有问题，应当建议dolphin去除Baloo当默认搜索。 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-krunner] [Bug 425052] krunner complaints about .desktop files that should be JSON metadata
https://bugs.kde.org/show_bug.cgi?id=425052 David Redondo changed: What|Removed |Added Version Fixed In||5.73.0 Version|5.19.4 |5.72.0 Product|krunner |frameworks-krunner Component|general |general Latest Commit||https://invent.kde.org/fram ||eworks/krunner/-/commit/10b ||78bcdebccc7ff9bc14c0d01c941 ||eb78301d42 -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 425052] krunner complaints about .desktop files that should be JSON metadata
https://bugs.kde.org/show_bug.cgi?id=425052 David Redondo changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |FIXED CC||k...@david-redondo.de --- Comment #1 from David Redondo --- The warning have been fixed with frameworks 5.73 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 425020] baloosearch's search support for Chinese, Japanese and Korean is very weak.
https://bugs.kde.org/show_bug.cgi?id=425020 --- Comment #12 from 2wxsy5823...@opayq.com --- @logicinu 关于分词不够细的问题，我觉得期望 Baloo 能把 “漫步人生路” 逐字分拆成 “漫” “步” “人” “生” “路” 是合理的。 但如果期望 Baloo 能辨认出当中的词语，例如： “漫步” “人生” “路” “漫步” “人生路” 则技术上或許不太可行。 -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 418854] "Update" page does not show the versions of currently installed packages
https://bugs.kde.org/show_bug.cgi?id=418854 --- Comment #4 from Riccardo Robecchi --- I can still reproduce and yes, I can see the correct info if I switch to another view (e.g. "about") and then back to updates. This happens even when I click on the "view updates" button on the "updates avaialable" notification. I never see the correct info being displayed. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 425020] baloosearch's search support for Chinese, Japanese and Korean is very weak.
https://bugs.kde.org/show_bug.cgi?id=425020 2wxsy5823...@opayq.com changed: What|Removed |Added Resolution|WORKSFORME |--- Status|RESOLVED|REPORTED --- Comment #11 from 2wxsy5823...@opayq.com --- Problem: Baloo is unable to extract keywords when the filename contains Chinese (and Japanese) characters. Example: 邓丽君 - 漫步人生路.mp3.txt Expected result: Baloo should at least extract "邓丽君", "漫步人生路", "mp3" and "txt". For better results, it should extract "邓", "丽", "君", "漫", "步", "人", "生", "路", "mp3" and "txt". Actual result: Baloo only extracts "mp3" and "txt". -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 425066] New: Python Document.modified() flag is NOT set in edit operations.
https://bugs.kde.org/show_bug.cgi?id=425066
Bug ID: 425066
Summary: Python Document.modified() flag is NOT set in edit
operations.
Product: krita
Version: nightly build (please specify the git hash!)
Platform: Appimage
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: Scripting
Assignee: krita-bugs-n...@kde.org
Reporter: aki.rissa...@anima.fi
Target Milestone: ---
SUMMARY:
Document modified flag is NOT set in edit operations.
Haven't tested all document edit methods.
STEPS TO REPRODUCE:
Krita -> Tools -> Scripts -> Scripter
```python
from krita import Krita
# before running
# open / save new document so that modified flag is false.
app = Krita.instance()
doc = app.activeDocument()
print(f"Krita version: {app.version()}")
print(f"before is_modified: {doc.modified()}")
doc.setDocumentInfo(doc.documentInfo() + "\n")
doc.setFramesPerSecond(int(doc.framesPerSecond() + 1))
doc.setFullClipRangeStartTime(doc.fullClipRangeStartTime() + 1)
doc.setFullClipRangeEndTime(doc.fullClipRangeEndTime() + 1)
doc.setFileName(doc.fileName() + ".ILBM")
doc.setName(doc.name()[::-1])
print(f"after is_modified: {doc.modified()}")
```
OBSERVED RESULT:
```
Warning: Script not saved!
Krita version: 4.3.1-alpha (git 4212182)
before is_modified: False
after is_modified: False
```
EXPECTED RESULT:
```
Warning: Script not saved!
Krita version: 4.3.1-alpha (git 4212182)
before is_modified: False
after is_modified: True
```
SOFTWARE/OS VERSIONS
Windows: -
macOS: -
Linux/KDE Plasma: Linux (x86_64) release 4.15.0-106-generic
(available in About System)
KDE Plasma Version:
KDE Frameworks Version:
Qt Version: 5.12.9
ADDITIONAL INFORMATION
Affects:
- saving of document (no changes to save)
- close krita (save modified? confirmation)
--
You are receiving this mail because:
You are watching all bug changes.
[krita] [Bug 424574] eye paind and damage with colorize mask tool. change background color to gray?
https://bugs.kde.org/show_bug.cgi?id=424574 Boudewijn Rempt changed: What|Removed |Added CC||b...@valdyas.org Status|REPORTED|RESOLVED Resolution|--- |WORKSFORME --- Comment #12 from Boudewijn Rempt --- Yes, it's fine to close a bug/wish you reported yourself if it's no longer relevant. I'll close this one for now. -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 425065] New: crashed when try to delete
https://bugs.kde.org/show_bug.cgi?id=425065 Bug ID: 425065 Summary: crashed when try to delete Product: kontact Version: unspecified Platform: Debian stable OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: shado...@gmx.net Target Milestone: --- Application: kontact (5.9.3) Qt Version: 5.11.3 Frameworks Version: 5.54.0 Operating System: Linux 4.19.0-9-amd64 x86_64 Distribution: Debian GNU/Linux 10 (buster) -- Information about the crash: - What I was doing when the application crashed: I select some mails and want to delete them but it crashed after pressing "Del"-key -- Backtrace: Application: Kontact (kontact), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7fc103258f00 (LWP 10287))] Thread 32 (Thread 0x7fbfb44bb700 (LWP 20757)): #0 0x7fc11620a3f9 in futex_reltimed_wait_cancelable (private=0, reltime=0x7fbfb44ba400, expected=0, futex_word=0x7fbfb44ba5e8) at ../sysdeps/unix/sysv/linux/futex-internal.h:142 #1 0x7fc11620a3f9 in __pthread_cond_wait_common (abstime=0x7fbfb44ba4a0, mutex=0x7fbfb44ba598, cond=0x7fbfb44ba5c0) at pthread_cond_wait.c:533 #2 0x7fc11620a3f9 in __pthread_cond_timedwait (cond=0x7fbfb44ba5c0, mutex=0x7fbfb44ba598, abstime=0x7fbfb44ba4a0) at pthread_cond_wait.c:667 #3 0x7fc10ff9f847 in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #4 0x7fc10ffa210a in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #5 0x7fc10ffa21f2 in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #6 0x7fc10ffa6781 in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #7 0x7fc10ffa7c61 in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #8 0x7fc10ffb0971 in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #9 0x7fc116203fa3 in start_thread (arg=) at pthread_create.c:486 #10 0x7fc1173c14cf in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 31 (Thread 0x7fbfd933e700 (LWP 19788)): #0 0x7fc11620a3f9 in futex_reltimed_wait_cancelable (private=0, reltime=0x7fbfd933d400, expected=0, futex_word=0x7fbfd933d5e8) at ../sysdeps/unix/sysv/linux/futex-internal.h:142 #1 0x7fc11620a3f9 in __pthread_cond_wait_common (abstime=0x7fbfd933d4a0, mutex=0x7fbfd933d598, cond=0x7fbfd933d5c0) at pthread_cond_wait.c:533 #2 0x7fc11620a3f9 in __pthread_cond_timedwait (cond=0x7fbfd933d5c0, mutex=0x7fbfd933d598, abstime=0x7fbfd933d4a0) at pthread_cond_wait.c:667 #3 0x7fc10ff9f847 in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #4 0x7fc10ffa210a in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #5 0x7fc10ffa21f2 in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #6 0x7fc10ffa6781 in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #7 0x7fc10ffa7c61 in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #8 0x7fc10ffb0971 in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #9 0x7fc116203fa3 in start_thread (arg=) at pthread_create.c:486 #10 0x7fc1173c14cf in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 30 (Thread 0x7fbfb5cbf700 (LWP 10479)): #0 0x7fc1173b6819 in __GI___poll (fds=0x7fc0b40023d0, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7fc11567d136 in () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7fc11567d25c in g_main_context_iteration () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7fc1178e4743 in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7fc11789215b in QEventLoop::exec(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7fc1176e1e76 in QThread::exec() () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7fc1176eba67 in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7fc116203fa3 in start_thread (arg=) at pthread_create.c:486 #8 0x7fc1173c14cf in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 29 (Thread 0x7fbffb7fe700 (LWP 7645)): #0 0x7fc101442d63 in pa_mainloop_dispatch () at /usr/lib/x86_64-linux-gnu/libpulse.so.0 #1 0x7fc101442ffc in pa_mainloop_iterate () at /usr/lib/x86_64-linux-gnu/libpulse.so.0 #2 0x7fc1014430a0 in pa_mainloop_run () at /usr/lib/x86_64-linux-gnu/libpulse.so.0 #3 0x7fc101451079 in () at /usr/lib/x86_64-linux-gnu/libpulse.so.0 #4 0x7fc1013ee468 in () at /usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-12.2.so #5 0x7fc116203fa3 in start_thread (arg=) at pthread_create.c:486 #6 0x7fc1173c14cf in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 28 (Thread 0x7fbfd8093700 (LWP 11265)): #0 0x7fc1173b2494 in __GI___libc_read (nbytes=16,
[ksysguard] [Bug 425064] New: ksysguard crashes while running in the background
https://bugs.kde.org/show_bug.cgi?id=425064 Bug ID: 425064 Summary: ksysguard crashes while running in the background Product: ksysguard Version: unspecified Platform: openSUSE RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: ksysguard-b...@kde.org Reporter: jodr...@live.com CC: plasma-b...@kde.org Target Milestone: --- Application: ksysguard (5.19.80) Qt Version: 5.15.0 Frameworks Version: 5.73.0 Operating System: Linux 5.7.11-1-default x86_64 Windowing system: X11 Distribution: "openSUSE Tumbleweed" -- Information about the crash: - What I was doing when the application crashed: I had it open to check resource usage as i was running a VM, after a while it crashed. The crash can be reproduced sometimes. -- Backtrace: Application: System Monitor (ksysguard), signal: Segmentation fault Content of s_kcrashErrorMessage: [Current thread is 1 (Thread 0x7fa6b2afe000 (LWP 10549))] [KCrash Handler] #6 0x7fa6b411927b in QLabelPrivate::clearContents (this=this@entry=0x555b3b3651b0) at widgets/qlabel.cpp:1380 #7 0x7fa6b411955a in QLabel::setText (this=0x555b3b365370, text=...) at widgets/qlabel.cpp:329 #8 0x7fa6b4e9b0b3 in TopLevel::answerReceived (this=0x555b3b0e4ba0, id=, answerList=...) at /usr/src/debug/ksysguard5-5.19.80git.20200803T152505~a7d1b0d9-ku.60.2.x86_64/gui/ksysguard.cpp:466 #9 0x7fa6b4bf62eb in KSGRD::SensorAgent::processAnswer (this=0x555b3b2eae10, buf=, buflen=) at /usr/src/debug/libksysguard5-5.19.80git.20200803T082938~981be2b-ku.82.2.x86_64/ksgrd/SensorAgent.cpp:306 #10 0x7fa6b4bf934c in KSGRD::SensorShellAgent::msgRcvd (this=0x555b3b2eae10) at /usr/include/qt5/QtCore/qarraydata.h:208 #11 0x7fa6b333e0f6 in QtPrivate::QSlotObjectBase::call (a=0x7ffd7a1fbfd0, r=0x555b3b2eae10, this=0x555b3b36f870) at ../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398 #12 doActivate (sender=0x555b3b36e2a0, signal_index=15, argv=argv@entry=0x7ffd7a1fbfd0) at kernel/qobject.cpp:3886 #13 0x7fa6b3337450 in QMetaObject::activate (sender=, m=m@entry=0x7fa6b35e7720 , local_signal_index=local_signal_index@entry=6, argv=argv@entry=0x7ffd7a1fbfd0) at kernel/qobject.cpp:3946 #14 0x7fa6b32759bd in QProcess::readyReadStandardOutput (this=, _t1=...) at .moc/moc_qprocess.cpp:367 #15 0x7fa6b327af7d in QProcessPrivate::tryReadFromChannel (this=0x555b3b2f2370, channel=0x555b3b2f2480) at io/qprocess.cpp:1057 #16 0x7fa6b327b4b5 in QProcessPrivate::_q_canReadStandardError (this=) at io/qprocess.cpp:1084 #17 QProcess::qt_static_metacall (_o=, _c=, _id=, _a=0x7ffd7a1fc180) at .moc/moc_qprocess.cpp:210 #18 0x7fa6b333e130 in doActivate (sender=0x555b3b361e20, signal_index=3, argv=argv@entry=0x7ffd7a1fc180) at ../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:395 #19 0x7fa6b3337450 in QMetaObject::activate (sender=sender@entry=0x555b3b361e20, m=m@entry=0x7fa6b35e9b00 , local_signal_index=local_signal_index@entry=0, argv=argv@entry=0x7ffd7a1fc180) at kernel/qobject.cpp:3946 #20 0x7fa6b334152f in QSocketNotifier::activated (this=this@entry=0x555b3b361e20, _t1=..., _t2=, _t3=...) at .moc/moc_qsocketnotifier.cpp:178 #21 0x7fa6b3341d2b in QSocketNotifier::event (this=0x555b3b361e20, e=0x7ffd7a1fc290) at kernel/qsocketnotifier.cpp:302 #22 0x7fa6b3fe50cf in QApplicationPrivate::notify_helper (this=, receiver=0x555b3b361e20, e=0x7ffd7a1fc290) at kernel/qapplication.cpp:3671 #23 0x7fa6b3307c1a in QCoreApplication::notifyInternal2 (receiver=0x555b3b361e20, event=0x7ffd7a1fc290) at ../../include/QtCore/5.15.0/QtCore/private/../../../../../src/corelib/thread/qthread_p.h:325 #24 0x7fa6b335fc15 in socketNotifierSourceDispatch (source=source@entry=0x555b3b048f60) at kernel/qeventdispatcher_glib.cpp:107 #25 0x7fa6aa71c2b7 in g_main_dispatch (context=0x7fa69c005000) at ../glib/gmain.c:3309 #26 g_main_context_dispatch (context=0x7fa69c005000) at ../glib/gmain.c:3974 #27 0x7fa6aa71c638 in g_main_context_iterate (context=context@entry=0x7fa69c005000, block=block@entry=1, dispatch=dispatch@entry=1, self=) at ../glib/gmain.c:4047 #28 0x7fa6aa71c6ef in g_main_context_iteration (context=0x7fa69c005000, may_block=may_block@entry=1) at ../glib/gmain.c:4108 #29 0x7fa6b335f05f in QEventDispatcherGlib::processEvents (this=0x555b3b046270, flags=...) at kernel/qeventdispatcher_glib.cpp:423 #30 0x7fa6b33065db in QEventLoop::exec (this=this@entry=0x7ffd7a1fc4a0, flags=..., flags@entry=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:141 #31 0x7fa6b330e840 in QCoreApplication::exec () at ../../include/QtCore/../../src/corelib/global/qflags.h:121 #32 0x7fa6b38baa8c in QGuiApplication::exec () at kernel/qguiapplication.cpp:1867 #33 0x7fa6b3fe5045 in QApplication::exec () at kernel/qapplication.cpp:2811 #34
[kmail2] [Bug 391030] kmail does not print images in emails
https://bugs.kde.org/show_bug.cgi?id=391030 Attila changed: What|Removed |Added CC||bugs.kde.att...@online.de --- Comment #2 from Attila --- I can confirm. Same on Fedora 32, KMail version 5.13.2 (19.12.2). -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 425063] New: Detect Faces crashes the App
https://bugs.kde.org/show_bug.cgi?id=425063 Bug ID: 425063 Summary: Detect Faces crashes the App Product: digikam Version: 7.0.0 Platform: Microsoft Windows OS: Microsoft Windows Status: REPORTED Severity: crash Priority: NOR Component: Faces-Detection Assignee: digikam-bugs-n...@kde.org Reporter: registrati...@andygavin.co.uk Target Milestone: --- SUMMARY Its a new install, with a fresh Database of approx 40k photos added. Detect faces, with Skip already scanned select won't complete, it crashes every 1-2 %. There is no feedback, it just closes. I have rebooted a few times to check its a fresh system. I have reached 18% with about 10 crashes so far. STEPS TO REPRODUCE 1. Open App 2. Wait for startup check to finish 3. Click Detect Faces (with skip images already scanned selected) OBSERVED RESULT App will either close almost immediately or try for a little while, achieve 1-2% more and then close. I am getting results, so its doing something. EXPECTED RESULT It to finish SOFTWARE/OS VERSIONS Windows: Windows 10 Pro 64bit AMD Ryzen 7 2700X 16Gb RAM ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[frameworks-knewstuff] [Bug 417985] Addons from KDE Store removed via KCMs are still listed as installed in respective GHNS window
https://bugs.kde.org/show_bug.cgi?id=417985 --- Comment #8 from Dan Leinir Turthra Jensen --- Git commit 84401e094669bf9322659f4423a8d8972c9de52b by Dan Leinir Turthra Jensen. Committed on 06/08/2020 at 08:04. Pushed by leinir into branch 'master'. Request that KNS cleans up its cache if there are dead entries This requires (though not hard) the code found in https://invent.kde.org/frameworks/knewstuff/-/merge_requests/23 and the idea behind this is to clean up KNewStuff's knowledge of entries which have been deleted without telling KNewStuff about it first. This is a further step towards fixing the bug below. M +1-0kcms/icons/icons.knsrc https://invent.kde.org/plasma/plasma-workspace/commit/84401e094669bf9322659f4423a8d8972c9de52b -- You are receiving this mail because: You are watching all bug changes.
[frameworks-knewstuff] [Bug 417985] Addons from KDE Store removed via KCMs are still listed as installed in respective GHNS window
https://bugs.kde.org/show_bug.cgi?id=417985 --- Comment #7 from Dan Leinir Turthra Jensen --- Git commit c83c377ff82aab27172699cdc7da5d4e28d54d27 by Dan Leinir Turthra Jensen. Committed on 06/08/2020 at 08:02. Pushed by leinir into branch 'master'. Add a RemoveDeadEntries option for knsrc files If you set RemoveDeadEntries=true, entries whose installed files have all been deleted without going through KNewStuff will be removed from the cache. The removal will happen if, and only if, all listed files were removed, which means that if, for example, an entry was installed from archive, which was decompressed to yield multiple installed files, if even one of those files remains, the entry will remain marked as installed. This is to help work around people deleting files from underneath KNewStuff, which turns out to happen a lot with e.g. wallpapers and icons. Only CCBUGing this one, as it is an imcomplete fix for the issue, and requires intervention in the icons.knsrc file for the fix to be applied to the issue mentioned in that bug. M +8-0src/core/engine.cpp M +9-0src/downloaddialog.h https://invent.kde.org/frameworks/knewstuff/commit/c83c377ff82aab27172699cdc7da5d4e28d54d27 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 425020] baloosearch's search support for Chinese, Japanese and Korean is very weak.
https://bugs.kde.org/show_bug.cgi?id=425020 --- Comment #10 from logicinu --- dolphin文件管理器的默认搜索用的是baloosearch，对是搜索功能来说，是不是太没用了，它是基于分词的，但是支持太少了，符号不支持，中文不支持，分词不够细，对于文件搜索来说，这完全不是想要的，搜索应该可以找到文件名中存在的字符，baloosearch不能干活，却还是默认搜索，搜索“mp3”它可以，搜索”3“它就不行了，它的意义何在，希望可以改进。 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 425020] baloosearch's search support for Chinese, Japanese and Korean is very weak.
https://bugs.kde.org/show_bug.cgi?id=425020 --- Comment #9 from 2wxsy5823...@opayq.com --- @logicinu 不知你是否愿意以中文详细解释你遇到的问题？ (Would you please explain your problem in Chinese?) -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 263042] XFA Forms are not supported
https://bugs.kde.org/show_bug.cgi?id=263042 --- Comment #25 from Reissner --- Created attachment 130675 --> https://bugs.kde.org/attachment.cgi?id=130675=edit some official pfd with xfa forms which can be opened in evince. The headline says all. -- You are receiving this mail because: You are watching all bug changes.
[kdeplasma-addons] [Bug 422839] Adding network interfaces screws the system monitor widgets
https://bugs.kde.org/show_bug.cgi?id=422839 --- Comment #11 from Mathias Homann --- looks as if it's only network interfaces that cause this - plugging in an usb drive doesn't mess up the sensors. also: it's not related to NetworkManager, my other openSUSE box uses wickedd instead and has the same issues. -- You are receiving this mail because: You are watching all bug changes.
[kdeplasma-addons] [Bug 422839] Adding network interfaces screws the system monitor widgets
https://bugs.kde.org/show_bug.cgi?id=422839 --- Comment #10 from Mathias Homann --- (In reply to Nicola Mori from comment #9) > @Matthias Homann: I think the underlying cause is the same I described, i.e. > starting a container or a VM creates network interfaces. definitely: run as root: "nmcli con add type bridge ifname testbridge name testbridge" and you'll see the same effect... Deleteing that bridge returns the disk usage monitor to normal, but not the CPU monitor... -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 400187] Export to google photo in an existing album: bad request
https://bugs.kde.org/show_bug.cgi?id=400187 Dario Panico changed: What|Removed |Added CC||dario...@yahoo.it -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 403569] Error while uploading image to google picasa/photos
https://bugs.kde.org/show_bug.cgi?id=403569 Dario Panico changed: What|Removed |Added Status|REOPENED|RESOLVED Resolution|--- |FIXED --- Comment #5 from Dario Panico --- Sorry for reopening, probably duplicate of #400187 -- You are receiving this mail because: You are watching all bug changes.
[kdeplasma-addons] [Bug 422839] Adding network interfaces screws the system monitor widgets
https://bugs.kde.org/show_bug.cgi?id=422839 --- Comment #9 from Nicola Mori --- @Matthias Homann: I think the underlying cause is the same I described, i.e. starting a container or a VM creates network interfaces. -- You are receiving this mail because: You are watching all bug changes.
