[Haruna] [Bug 446259] Haruna icon missing (empty)
https://bugs.kde.org/show_bug.cgi?id=446259 giuseppe changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |WORKSFORME --- Comment #1 from giuseppe --- I solved this little bug just by editing the /var/lib/flatpak/app/org.kde.haruna/current/active/export/share/applications/org.kde.haruna.desktop file and changing the icon line with "/var/lib/flatpak/app/org.kde.haruna/current/active/files/share/icons/hicolor/scalable/apps/haruna.svg" -- You are receiving this mail because: You are watching all bug changes.
[Spam] [Bug 445185] basketbal
https://bugs.kde.org/show_bug.cgi?id=445185 Tech Wiki changed: What|Removed |Added CC||techwiki2...@gmail.com URL||https://www.techwiki.in/ --- Comment #1 from Tech Wiki --- Techwiki is an online blog site based on the tech news that can provide you with all technology updates and the latest trends that are rolling-out every day. -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 446407] New: Audacious version is old
https://bugs.kde.org/show_bug.cgi?id=446407 Bug ID: 446407 Summary: Audacious version is old Product: neon Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: Packages User Edition Assignee: neon-b...@kde.org Reporter: pieterkristen...@gmail.com CC: j...@jriddell.org, neon-b...@kde.org, sit...@kde.org Target Milestone: --- SUMMARY *** At this time Audacious made the transition from gtk to qt and it is rock-solid. As far as I am concerned this is the ultimate quality software. The version of the audio player Audacious that comes with the LTS of ubuntu is very old it still uses gtk by default. Wouldn't it be appropriate when Neon took a newer version of this great piece of software so that we didn't have to use the ppa but simply got this new version by default? *** -- You are receiving this mail because: You are watching all bug changes.
[Haruna] [Bug 446406] New: [Bug] Playlist open sensitive area always to the left (even playlist position is right)
https://bugs.kde.org/show_bug.cgi?id=446406 Bug ID: 446406 Summary: [Bug] Playlist open sensitive area always to the left (even playlist position is right) Product: Haruna Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: generic Assignee: georgefb...@gmail.com Reporter: shriraj.he...@gmail.com Target Milestone: --- SUMMARY [Bug] Playlist open sensitive area always to the left (even playlist position is right) Commit : fa879c879cd238a6ef1b26dba9ae4bdc40501371 https://invent.kde.org/multimedia/haruna/-/commit/fa879c879cd238a6ef1b26dba9ae4bdc40501371 STEPS TO REPRODUCE 1. Update to said commit 2. Set playlist position to right 3. Hover to the left of the window to reveal playlist (playlist is at the right) OBSERVED RESULT Sensitive area is to the left when playlist is set to right EXPECTED RESULT Sensitive area to reveal playlist is to the right -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 423788] Liquify Tool - Utterly Slow Performance
https://bugs.kde.org/show_bug.cgi?id=423788 David REVOY changed: What|Removed |Added CC||i...@davidrevoy.com --- Comment #6 from David REVOY --- Hi, I guess these bugs report of @Stig (Rakurri) , @holtein and @Stephen happens because of a more fundamental change of default in the 5x transform tool: the new default 'in stack rendering' that is − indeed− super slow (especially in liquify, especially on recursive groups in liquify too). I had same issue once I started to adopt 5.x. Can you try to go to the "tool options" panel after selecting the "transform tool", and turn the "Preview" setting (on top) to "Fast"? Does it restore the speed you knew on 4.x ? (it should, "Fast" was the setting by default in 4.x) -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 446405] Wrong icon size of plasma applet "Trashcan" in latte-dock button panel
https://bugs.kde.org/show_bug.cgi?id=446405 --- Comment #1 from crc --- Created attachment 144165 --> https://bugs.kde.org/attachment.cgi?id=144165=edit My latte-dock layout file -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 446405] New: Wrong icon size of plasma applet "Trashcan" in latte-dock button panel
https://bugs.kde.org/show_bug.cgi?id=446405 Bug ID: 446405 Summary: Wrong icon size of plasma applet "Trashcan" in latte-dock button panel Product: lattedock Version: git (master) Platform: Manjaro OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: application Assignee: mvourla...@gmail.com Reporter: crc2...@126.com Target Milestone: --- Created attachment 144164 --> https://bugs.kde.org/attachment.cgi?id=144164=edit Screenshot that shown the abnormally small size of trashcan at the end of dock panel SUMMARY This problem has existed for quite a long time, perhaps ever since the update of Plasma5.21. When the applet "Trashcan" is added to latte-dock button panel its icon size is obviously smaller than other apps (as shown in the screenshot). Changing the absolute size of dock items does not make any difference. I'm not sure whether it is a specific problem for latte-dock or a general problem of KDE Plasma, so I temporarily post the bug here. STEPS TO REPRODUCE Add the "Trashcan" applet to latte dock button panel and observe its icon size. OBSERVED RESULT The icon of "Trashcan" shall be as same size as other apps in button panel. EXPECTED RESULT The icon size of "Trashcan" appears smaller than other apps in button panel. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: Manjaro 21.2.0 Qonos (available in About System) KDE Plasma Version: 5.23.3 KDE Frameworks Version: 5.88.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION In the attachment is a screenshot proof along with my latte-dock layout file -- You are receiving this mail because: You are watching all bug changes.
[muon] [Bug 446226] Package manager not showing some packages
https://bugs.kde.org/show_bug.cgi?id=446226 --- Comment #1 from pqwoerituytruei...@gmail.com --- I figured it out, i needed to run this command $ sudo /usr/sbin/update-apt-xapian-index There really should be a button in muon to update the search index -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kuserfeedback] [Bug 442296] "CMake Error: The INTERFACE_QT_MAJOR_VERSION property of "Qt5::Core" does not agree with the value of QT_MAJOR_VERSION already determined for KUserFeedbackQml /
https://bugs.kde.org/show_bug.cgi?id=442296 Kyle Devir changed: What|Removed |Added Attachment #141467|0 |1 is obsolete|| --- Comment #5 from Kyle Devir --- Created attachment 144163 --> https://bugs.kde.org/attachment.cgi?id=144163=edit Retested build error.log from kdesrc-build Still not working. :( -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kuserfeedback] [Bug 442296] "CMake Error: The INTERFACE_QT_MAJOR_VERSION property of "Qt5::Core" does not agree with the value of QT_MAJOR_VERSION already determined for KUserFeedbackQml /
https://bugs.kde.org/show_bug.cgi?id=442296 --- Comment #4 from Kyle Devir --- Will test now. :) -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kuserfeedback] [Bug 442296] "CMake Error: The INTERFACE_QT_MAJOR_VERSION property of "Qt5::Core" does not agree with the value of QT_MAJOR_VERSION already determined for KUserFeedbackQml /
https://bugs.kde.org/show_bug.cgi?id=442296 --- Comment #3 from Eduardo --- I just tried building it again now with kdesrc-build and now it works! I didn't do anything on my system, I guess it was some misconfiguration on the git master and somebody fixed it in the meantime. If it also works for the OP, maybe we can close this bug report. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 446363] EXIF of image cannot be read on windows
https://bugs.kde.org/show_bug.cgi?id=446363 --- Comment #8 from Maik Qualmann --- I think symlinks are not the cause. There is currently a problem with the current version of Exiv2 and Sony cameras with the size of the embedded thumbnail preview. Depending on the image, this can be too large and cause an exception in Exiv2. See bug 446403. Please send a image to my mail to test it. Maik -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 445561] Krita 5 16bit integer colorspace canvas rendering is broken on M1
https://bugs.kde.org/show_bug.cgi?id=445561
--- Comment #14 from vanyossi ---
This time I made more indepth testing but the end result is I don't have a
clear idea on what this is happening, afair our code is working correctly and
the problemas might be from the arm/rosetta layer translation tool deep inside
openGL or Qt. This is not a problem present in any krita version running on an
intel chip. But its present on arm and Rosetta.
Below are the results of the tests
1) I applied all patches over master when testing :)
2) border buffers makes no difference. I actually tried that yesterday,
removing buffers and noted only the inner buffers cause the issue.
3) This is interesting, testing to 1 buffer does not make it behave as it was
before, in fact, the texture tiling is broken and still shows the image broken.
If we go to 512. the only main difference is that on many buffers the events
sometimes does not update the canvas and leaves some parts invisible or not
rendered.
4) Buffer flushing is set to only be active on 4.3 versions. macOS openGL
latest version is 4.1, this appears to be the reason making the activation of
buffer flushing crash krita. So it was not possible to check if there was any
change in rendering.
5) tested forcing m_useBuffers and in both tests the image render was normal on
any colorspace. The only rendering problem was due to outline compositing and
was present in all colorspaces. when there is no pixels between the outline and
the checkerboard pattern, and appears to be addressed in another much recent
commit.
6)
=== 8bit
2021-12-02 15:17:38.321954-0600 krita[38149:28655458] Entering
"KisOpenGLImageTextures::updateTextureFormat()" tilesDestinationColorSpace =
"RGB/Alpha (8-bit integer/channel)" ("RGBA","U8" )
2021-12-02 15:17:38.321975-0600 krita[38149:28655458] Entering
"KisOpenGLImageTextures::updateTextureFormat()" m_texturesInfo.format = 80e1
2021-12-02 15:17:38.321980-0600 krita[38149:28655458] Entering
"KisOpenGLImageTextures::updateTextureFormat()" m_texturesInfo.internalFormat =
8058
2021-12-02 15:17:38.321984-0600 krita[38149:28655458] Entering
"KisOpenGLImageTextures::updateTextureFormat()" m_texturesInfo.type = 1401
2021-12-02 15:17:38.340311-0600 krita[38149:28655458] Still unsignalled after
processed 17 tiles
2021-12-02 15:17:38.340376-0600 krita[38149:28655458] increased number of
buffers to 32
=== 16bit int
2021-12-02 15:17:59.044839-0600 krita[38149:28655458] Entering
"KisOpenGLImageTextures::updateTextureFormat()" tilesDestinationColorSpace =
"RGB/Alpha (16-bit integer/channel)" ("RGBA","U16" )
2021-12-02 15:17:59.044862-0600 krita[38149:28655458] Entering
"KisOpenGLImageTextures::updateTextureFormat()" m_texturesInfo.format = 80e1
2021-12-02 15:17:59.044867-0600 krita[38149:28655458] Entering
"KisOpenGLImageTextures::updateTextureFormat()" m_texturesInfo.internalFormat =
805b
2021-12-02 15:17:59.044871-0600 krita[38149:28655458] Entering
"KisOpenGLImageTextures::updateTextureFormat()" m_texturesInfo.type = 1403
2021-12-02 15:17:59.175831-0600 krita[38149:28655458] Still unsignalled after
processed 17 tiles
2021-12-02 15:17:59.175969-0600 krita[38149:28655458] increased number of
buffers to 32
=== 16bit float
2021-12-02 15:18:16.394816-0600 krita[38149:28655458] Entering
"KisOpenGLImageTextures::updateTextureFormat()" tilesDestinationColorSpace =
"RGB/Alpha (16-bit float/channel)" ("RGBA","F16" )
2021-12-02 15:18:16.394842-0600 krita[38149:28655458] Entering
"KisOpenGLImageTextures::updateTextureFormat()" m_texturesInfo.format = 1908
2021-12-02 15:18:16.394847-0600 krita[38149:28655458] Entering
"KisOpenGLImageTextures::updateTextureFormat()" m_texturesInfo.internalFormat =
881a
2021-12-02 15:18:16.394851-0600 krita[38149:28655458] Entering
"KisOpenGLImageTextures::updateTextureFormat()" m_texturesInfo.type = 140b
=== 32bit
2021-12-02 15:18:32.446803-0600 krita[38149:28655458] Entering
"KisOpenGLImageTextures::updateTextureFormat()" tilesDestinationColorSpace =
"RGB/Alpha (32-bit float/channel)" ("RGBA","F32" )
2021-12-02 15:18:32.446830-0600 krita[38149:28655458] Entering
"KisOpenGLImageTextures::updateTextureFormat()" m_texturesInfo.format = 1908
2021-12-02 15:18:32.446836-0600 krita[38149:28655458] Entering
"KisOpenGLImageTextures::updateTextureFormat()" m_texturesInfo.internalFormat =
8814
2021-12-02 15:18:32.446840-0600 krita[38149:28655458] Entering
"KisOpenGLImageTextures::updateTextureFormat()" m_texturesInfo.type = 1406
2021-12-02 15:18:42.817410-0600 krita[38149:28655458] QLayout: Attempting to
add QLayout "" to KisShortcutsDialog "", which already has a layout
2021-12-02 15:18:42.861259-0600 krita[38149:28655458] Failed to fetch display
info: "current platform doesn't support fetching display information"
== Comparisson printing result of working hash
2021-12-02 15:34:27.398144-0600 krita[76848:28792392] Entering
"KisOpenGLImageTextures::updateTextureFormat()" tilesDestinationColorSpace =
"RGB/Alpha (16-bit integer/channel)"
[plasmashell] [Bug 443131] When there's more than one Kickoff, clicking on the old one causes search to be broken until you search with the new one
https://bugs.kde.org/show_bug.cgi?id=443131 Michał Walenciak changed: What|Removed |Added CC||kice...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 446403] Metadata not read correctly (XMP instead of EXIF)
https://bugs.kde.org/show_bug.cgi?id=446403 --- Comment #7 from MarcP --- You are right, it fails in exiv 0.27.5: (base) marc@marc-TM1703:~/Baixades/exiv2-0.27.5-Linux64$ bin/exiv2 -p a ~/DSC07110.JPG Exiv2 exception in print action for file /home/marc/DSC07110.JPG: corrupted image metadata I have checked exiv2's project on github, and it's probably related to this bug: https://github.com/Exiv2/exiv2/issues/2001 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 446403] Metadata not read correctly (XMP instead of EXIF)
https://bugs.kde.org/show_bug.cgi?id=446403 --- Comment #6 from MarcP --- In my setup, I have exiv2 0.27.2. It seems to read the metadata correctly: (base) marc@marc-TM1703:~$ exiv2 --version exiv2 0.27.2 This program is free software; you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation; either version 2 of the License, or (at your option) any later version. This program is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details. You should have received a copy of the GNU General Public License along with this program; if not, write to the Free Software Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA (base) marc@marc-TM1703:~$ exiv2 -p a DSC07110.JPG Exif.Image.ImageDescription Ascii 32 Exif.Image.Make Ascii 5 SONY Exif.Image.Model Ascii 10 ILCE-5000 Exif.Image.Orientation Short 1 left, bottom Exif.Image.XResolution Rational1 350 Exif.Image.YResolution Rational1 350 Exif.Image.ResolutionUnitShort 1 inch Exif.Image.Software Ascii 16 ILCE-5000 v1.10 Exif.Image.DateTime Ascii 20 2021:11:27 12:51:55 Exif.Image.YCbCrPositioning Short 1 Co-sited Exif.Image.ExifTag Long1 364 Exif.Photo.ExposureTime Rational1 1/80 s Exif.Photo.FNumber Rational1 F11 Exif.Photo.ExposureProgram Short 1 Auto Exif.Photo.ISOSpeedRatings Short 1 100 Exif.Photo.SensitivityType Short 1 2 Exif.Photo.RecommendedExposureIndex Long1 100 Exif.Photo.ExifVersion Undefined 4 2.30 Exif.Photo.DateTimeOriginal Ascii 20 2021:11:27 12:51:55 Exif.Photo.DateTimeDigitized Ascii 20 2021:11:27 12:51:55 Exif.Photo.ComponentsConfiguration Undefined 4 YCbCr Exif.Photo.CompressedBitsPerPixelRational1 3 Exif.Photo.BrightnessValue SRational 1 8.91172 Exif.Photo.ExposureBiasValue SRational 1 0 EV Exif.Photo.MaxApertureValue Rational1 F3.5 Exif.Photo.MeteringMode Short 1 Multi-segment Exif.Photo.LightSource Short 1 Unknown Exif.Photo.Flash Short 1 No, compulsory Exif.Photo.FocalLength Rational1 16.0 mm Exif.Photo.MakerNote Undefined 37103 (Binary value suppressed) Exif.MakerNote.OffsetLong1 922 Exif.MakerNote.ByteOrder Ascii 3 II Exif.Sony1.Panorama Long 16 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 Exif.Sony1.PreviewImage Undefined 1077203 (Binary value suppressed) Exif.Sony1.Contrast SLong 1 0 Exif.Sony1.SaturationSLong 1 0 Exif.Sony1.AutoHDR Long1 Off Exif.Sony1.ShotInfo Undefined 390 (Binary value suppressed) Exif.Sony1.ColorReproduction Ascii 16 Standard Exif.Sony1.ColorTemperature Long1 0 Exif.Sony1.ColorCompensationFilter Long1 0 Exif.Sony1.SceneMode Long1 Auto Exif.Sony1.ZoneMatching Long1 ISO Setting Used Exif.Sony1.DynamicRangeOptimizer Long1 Auto Exif.Sony1.ImageStabilizationLong1 On Exif.Sony1.ColorMode Long1 Standard Exif.Sony1.FullImageSize Long2 3632 x 5456 Exif.Sony1.PreviewImageSize Long2 1080 x 1616 Exif.Sony1.FileFormatByte4 ARW 2.3.1 Exif.Sony1.Quality Long1 Fine Exif.Sony1.FlashExposureComp SRational 1 0 EV Exif.Sony1.WhiteBalanceFineTune Long1 0 Exif.Sony1.WhiteBalance Long1 Auto Exif.Sony1.SonyModelID Short 1 ILCE-5000 Exif.Sony1.Teleconverter Long1 None Exif.Sony1.LensIDLong1 Manual lens Exif.Sony1.ExposureMode Short 1 Program Exif.Sony1.JPEGQuality Short 1 n/a Exif.Sony1.FlashLevelSShort
[digikam] [Bug 446403] Metadata not read correctly (XMP instead of EXIF)
https://bugs.kde.org/show_bug.cgi?id=446403 caulier.gil...@gmail.com changed: What|Removed |Added CC||caulier.gil...@gmail.com --- Comment #5 from caulier.gil...@gmail.com --- Hi, I tried under Mac and digiKam 7.4.0, compiled with Exiv2 0.27.5 and XMP support. The problem is clear on the command line traces. It come from Exiv2 shared library : digikam.metaengine: Cannot load metadata from file with Exiv2 backend: /System/Volumes/Data/Users/gilles/Pictures/DSC06971.JPG (Error # 59 : "corrupted image metadata". So, i recommend to tried to read metadata ith Exiv2 CLI tool with this image. Typically, it must report the same problem. If yes, make a new bug entry in Exiv2 project from github with a link to the image for future investigations by Exiv2 team. Best Gilles Caulier -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 422776] Unicode icons are clipped when the proceeding whitespace has a different color
https://bugs.kde.org/show_bug.cgi?id=422776 Celeste changed: What|Removed |Added CC||coelacant...@outlook.com -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 446403] Metadata not read correctly (XMP instead of EXIF)
https://bugs.kde.org/show_bug.cgi?id=446403 --- Comment #4 from MarcP --- Outcome of Jeffrey Friedl's Image Metadata Viewer for the affected picture. (Link expires in 30 days): https://easyupload.io/a9oqqn -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 446404] New: parser sometimes ignores custom parser options
https://bugs.kde.org/show_bug.cgi?id=446404 Bug ID: 446404 Summary: parser sometimes ignores custom parser options Product: kdevelop Version: 5.6.2 Platform: Gentoo Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Language Support: CPP (Clang-based) Assignee: kdevelop-bugs-n...@kde.org Reporter: daniel.san...@pobox.com Target Milestone: --- SUMMARY 16 threads and the Linux kernel sources and I sometimes end up with #include referencing /usr/include/linux/modules.h. All parse jobs run by the background parser seem correct. But when I open a file (in the project) and it's scheduled for immediate parsing, BANG, I see the debug spew using the default arguments. This essential breaks KDevelop as a usable IDE for the Linux kernel sources, because I have to 'git grep' and use elixir.bootlin.com to look up types and functions, since KDevelop can't find them. STEPS TO REPRODUCE 1. KDEV_CLANG_DISPLAY_ARGS=1 KDEV_CLANG_DISPLAY_DIAGS=1 kdevelop 2. Open sources to Linux kernel 3. set custom C parser options based upon building the kernel and sucking out the arguments. In my particular case, I'm cross-compiling and these are my arguments: --target=mipsel-openwrt-linux -mno-check-zero-division -mabi=32 -mno-abicalls -msoft-float -march=mips32r2 -mtune=34kc -std=gnu89 -nostdinc -isystem /home/daniel/proj/embedded/openwrt/v21.02.y/staging_dir/toolchain-mipsel_24kc_gcc-10.2.0_musl/lib/gcc/mipsel-openwrt-linux-musl/10.2.0/include -Iarch/mips/include -Iarch/mips/include/generated -Iinclude -Iarch/mips/include/uapi -Iarch/mips/include/generated/uapi -Iinclude/uapi -Iinclude/generated/uapi -include include/linux/kconfig.h -include include/linux/compiler_types.h -Iarch/mips/include/asm/mach-ralink -Iarch/mips/include/asm/mach-ralink/mt7620 -Iarch/mips/include/asm/mach-generic -D__KERNEL__ -D__MIPSEL__ -DVMLINUX_LOAD_ADDRESS=0x8000 -DLINKER_LOAD_ADDRESS=0x8000 -DDATAOFFSET=0 -DGAS_HAS_SET_HARDFLOAT -DTOOLCHAIN_SUPPORTS_VIRT -DTOOLCHAIN_SUPPORTS_XPA -DTOOLCHAIN_SUPPORTS_CRC -DTOOLCHAIN_SUPPORTS_DSP -DTOOLCHAIN_SUPPORTS_GINV -ferror-limit=99 -fspell-checking -Wdocumentation -Wall -Wundef -Wno-trigraphs -Wno-format-security -Wno-frame-address -Wno-address-of-packed-member -Wframe-larger-than=1024 -Wimplicit-fallthrough -Wno-unused-const-variable -Wdeclaration-after-statement -Wvla -Wno-pointer-sign -Wno-array-bounds -Wno-uninitialized -Wno-incompatible-library-redeclaration -Wno-unknown-warning-option -Wno-implicit-fallthrough -working-directory /home/daniel/proj/embedded/openwrt/linux-5.4.143 Actually, for this to even work, I had to hack kdvelop and stop it from inserting a -working-directory argument, but I can probably just change all of my include paths to absolute and not have that problem. 4. let it start parsing and notice it's correct 5. Open a file and notice that it's incorrect (it parsed with the default options). 6. If I allow all parsing to complete before opening any files, then they are correct until some point later after editing enough. I haven't seen it incorrectly parse a file after making changes (yet) only after initially opening it (before background parsing has completed). I don't know if this is a race or not. I'm on a 8/16 Ryzen and using 16 parsing threads and 500ms delay. I've tried digging into the KDevelop sources, and I got as as finding where the job is run and where the job is scheduled. Job run from: (gdb) bt #0 ParseSessionData::ParseSessionData (this=this@entry=0x7fff39085260, unsavedFiles=..., index=index@entry=0x569dbb70, environment=..., options=..., options@entry=...) at ../plugins/clang/duchain/parsesession.cpp:272 #1 0x7fff47b68213 in ClangParseJob::createSessionData (this=this@entry=0x57c10270) at /usr/src/debug/dev-util/kdevelop-5.6.2/kdevelop-5.6.2/plugins/clang/clangparsejob.cpp:394 #2 0x7fff47b69bcc in ClangParseJob::run (this=) at /usr/src/debug/dev-util/kdevelop-5.6.2/kdevelop-5.6.2/plugins/clang/clangparsejob.cpp:300 #3 0x72bb8f99 in ThreadWeaver::IdDecorator::run (this=, self=..., thread=0x56ac2350) at /usr/src/debug/kde-frameworks/threadweaver-5.85.0/threadweaver-5.85.0/src/iddecorator.cpp:50 #4 0x72bb9597 in ThreadWeaver::Executor::run (this=, job=..., thread=) at /usr/src/debug/kde-frameworks/threadweaver-5.85.0/threadweaver-5.85.0/src/executor.cpp:33 #5 0x72bb8580 in ThreadWeaver::Job::execute (this=, self=..., th=0x56ac2350) at /usr/src/debug/kde-frameworks/threadweaver-5.85.0/threadweaver-5.85.0/src/job.cpp:64 #6 0x72bb7d82 in ThreadWeaver::Thread::run (this=0x56ac2350) at /usr/src/debug/kde-frameworks/threadweaver-5.85.0/threadweaver-5.85.0/src/thread.cpp:98 #7 0x76420c56 in QThreadPrivate::start (arg=0x56ac2350) at
[digikam] [Bug 446403] Metadata not read correctly (XMP instead of EXIF)
https://bugs.kde.org/show_bug.cgi?id=446403 --- Comment #3 from MarcP --- I could not upload an affected picture due to the file size. Here's a link to the affected picture (compressed in ZIP to preserve format): https://easyupload.io/efm7gq -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 446403] Metadata not read correctly (XMP instead of EXIF)
https://bugs.kde.org/show_bug.cgi?id=446403 --- Comment #2 from MarcP --- Created attachment 144162 --> https://bugs.kde.org/attachment.cgi?id=144162=edit Digikam's Metadata panel (XMP) for affected picture. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 446403] Metadata not read correctly (XMP instead of EXIF)
https://bugs.kde.org/show_bug.cgi?id=446403 --- Comment #1 from MarcP --- Created attachment 144161 --> https://bugs.kde.org/attachment.cgi?id=144161=edit Digikam's Metadata panel (EXIF) for affected picture. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 446403] Metadata not read correctly (XMP instead of EXIF)
https://bugs.kde.org/show_bug.cgi?id=446403 MarcP changed: What|Removed |Added CC||iwannaber...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 446403] New: Metadata not read correctly (XMP instead of EXIF)
https://bugs.kde.org/show_bug.cgi?id=446403 Bug ID: 446403 Summary: Metadata not read correctly (XMP instead of EXIF) Product: digikam Version: 7.4.0 Platform: Flatpak OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Metadata-Exif Assignee: digikam-bugs-n...@kde.org Reporter: iwannaber...@gmail.com Target Milestone: --- SUMMARY I noticed that in some random pictures I took last week, digikam was not able to read the metadata. Information such as the date and the picture orientation was not read from the picture metadata. When looking at the metadata panels, I see that all the metadata is seen in the XMP section instead of the EXIF (which appears as blank), but when inspecting the metadata using another tool (e.g. Jeffrey's Image metadata viewer http://exif.regex.info/) I can see that there is indeed EXIF info in the picture. Strangely enough, other pictures from the same batch had their metadata read correctly. I have attached one of the affected pictures as a reference. It has not been edited in any way, just straight out of the camera. Also a capture of the EXIF data in the mentioned website, and a couple captures of the metadata section in Digikam. However, I tried with Digikam 7.3 (stable, appimage) and all the metadata was read correctly, so this problem seems to be specific to v7.4 STEPS TO REPRODUCE 1. Transfer pictures from camera to folder in PC. 2. Start digikam and wait until finishes exploring new elements. OBSERVED RESULT Notice how some elements do not include the date or the picture orientation. EXPECTED RESULT Exif metadata should be read correctly. SOFTWARE/OS VERSIONS Digikam 7.4.0 Build date: 2/12/21 10:27 (target: Debug) Rev.: 7ac1b183b14ecd37e72f181e1702ddee1b2a22b7 Ubuntu 20.04.3 LTS -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 444320] Selected brush resets after opening a first file
https://bugs.kde.org/show_bug.cgi?id=444320 Bug Janitor Service changed: What|Removed |Added Resolution|WAITINGFORINFO |--- Status|NEEDSINFO |REPORTED --- Comment #13 from Bug Janitor Service --- Thanks for your comment! Automatically switching the status of this bug to REPORTED so that the KDE team knows that the bug is ready to get confirmed. In the future you may also do this yourself when providing needed information. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 444618] Editing system monitor applets looks causes desktop to crash and restart
https://bugs.kde.org/show_bug.cgi?id=444618 Bug Janitor Service changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |WORKSFORME --- Comment #5 from Bug Janitor Service --- This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 432582] imports accounts to incorrect account
https://bugs.kde.org/show_bug.cgi?id=432582 Bug Janitor Service changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |WORKSFORME --- Comment #4 from Bug Janitor Service --- This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 445499] Cursor is one size bigger than it is on X11, when hovering over something built with Qt
https://bugs.kde.org/show_bug.cgi?id=445499 --- 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.
[plasmashell] [Bug 445669] plasma crashes when closing Minecraft
https://bugs.kde.org/show_bug.cgi?id=445669 --- Comment #3 from Bug Janitor Service --- Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 443507] Kdenlive crashed when duplicating multiple clips
https://bugs.kde.org/show_bug.cgi?id=443507 --- 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.
[lokalize] [Bug 424024] Main window doesn't repaint correctly on Wayland
https://bugs.kde.org/show_bug.cgi?id=424024 --- Comment #21 from Bug Janitor Service --- Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 445982] Popup of Touchpad applet does not close when systray icon is clicked
https://bugs.kde.org/show_bug.cgi?id=445982 Nate Graham changed: What|Removed |Added Latest Commit|https://invent.kde.org/plas |https://invent.kde.org/plas |ma/plasma-desktop/commit/4c |ma/plasma-desktop/commit/21 |b2de984ab79bc257af0135bf92e |31daa05195a2b55f593acf3d323 |a7390d5617f |cf4c2a89936 --- Comment #4 from Nate Graham --- Git commit 2131daa05195a2b55f593acf3d323cf4c2a89936 by Nate Graham. Committed on 03/12/2021 at 03:15. Pushed by ngraham into branch 'Plasma/5.23'. kcms/touchpad/applet: Make the popup close on click FIXED-IN: 5.23.5 (cherry picked from commit 4cb2de984ab79bc257af0135bf92ea7390d5617f) M +13 -10 kcms/touchpad/applet/qml/contents/ui/touchpad.qml https://invent.kde.org/plasma/plasma-desktop/commit/2131daa05195a2b55f593acf3d323cf4c2a89936 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 445982] Popup of Touchpad applet does not close when systray icon is clicked
https://bugs.kde.org/show_bug.cgi?id=445982 Nate Graham changed: What|Removed |Added Version Fixed In||5.23.5 Resolution|--- |FIXED Latest Commit||https://invent.kde.org/plas ||ma/plasma-desktop/commit/4c ||b2de984ab79bc257af0135bf92e ||a7390d5617f Status|CONFIRMED |RESOLVED --- Comment #3 from Nate Graham --- Git commit 4cb2de984ab79bc257af0135bf92ea7390d5617f by Nate Graham. Committed on 03/12/2021 at 03:13. Pushed by ngraham into branch 'master'. kcms/touchpad/applet: Make the popup close on click FIXED-IN: 5.23.5 M +13 -10 kcms/touchpad/applet/qml/contents/ui/touchpad.qml https://invent.kde.org/plasma/plasma-desktop/commit/4cb2de984ab79bc257af0135bf92ea7390d5617f -- You are receiving this mail because: You are watching all bug changes.
[Elisa] [Bug 446402] Elisa doesn't render header background properly beyond some window size
https://bugs.kde.org/show_bug.cgi?id=446402 --- Comment #1 from Nagy Tibor --- Created attachment 144160 --> https://bugs.kde.org/attachment.cgi?id=144160=edit Test track -- You are receiving this mail because: You are watching all bug changes.
[Elisa] [Bug 446402] New: Elisa doesn't render header background properly beyond some window size
https://bugs.kde.org/show_bug.cgi?id=446402 Bug ID: 446402 Summary: Elisa doesn't render header background properly beyond some window size Product: Elisa Version: 21.08.3 Platform: Neon Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: matthieu_gall...@yahoo.fr Reporter: xnagyti...@gmail.com Target Milestone: --- Created attachment 144159 --> https://bugs.kde.org/attachment.cgi?id=144159=edit Screen capture SUMMARY When you resize Elisa's main window beyond some limit it doesn't render the cover images at the header background anymore. I noticed this bug depends on the aspect ratio of the cover image. The taller the cover image the narrower the window needs to be to trigger the bug. I originally encountered this bug though those tall Mini CD album covers. I attached a test track to this issue with a cover image around the same metrics as those covers. SOFTWARE/OS VERSIONS Operating System: KDE neon 5.23 KDE Plasma Version: 5.23.3 KDE Frameworks Version: 5.88.0 Qt Version: 5.15.3 Graphics Platform: X11 Kernel Version: 5.11.0-41-generic (64-bit) Graphics Processor: NVIDIA GeForce 920M/PCIe/SSE2 NVIDIA Driver Version: 470.86 -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 446401] New: unhandled series of rr-specific syscalls
https://bugs.kde.org/show_bug.cgi?id=446401 Bug ID: 446401 Summary: unhandled series of rr-specific syscalls Product: valgrind Version: 3.18.1 Platform: Other OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: general Assignee: jsew...@acm.org Reporter: j...@garrison.cc Target Milestone: --- SUMMARY Valgrind complains about unimplemented syscalls when it encounters system calls specific to rr (the record and replay framework) STEPS TO REPRODUCE 1. I'm running portions of the Julia test suite under valgrind, following the instructions at https://docs.julialang.org/en/v1/devdocs/valgrind/#Running-the-Julia-test-suite-under-Valgrind (for the purposes here, `all` can be replaced by a much simpler set of tests, such as `tuple`). OBSERVED RESULT valgrind succeeds, but emits the following warning: --114742-- WARNING: unhandled amd64-linux syscall: 1008 --114742-- You may be able to write your own handler. --114742-- Read the file README_MISSING_SYSCALL_OR_IOCTL. --114742-- Nevertheless we consider this a bug. Please report --114742-- it at http://valgrind.org/support/bug_reports.html. The README_MISSING_SYSCALL_OR_IOCTL document instructs me to run `grep 1008 /usr/include/asm/unistd*.h`, but this turns up nothing. Turns out, julia is making this syscall to determine whether it is running under rr: https://github.com/JuliaLang/julia/blob/ed9ad60f0ce7cad38870b2bf9eede5dd7a4b706f/test/runtests.jl#L17-L20 There are a number of rr-specific syscalls that valgrind might want to either handle, ignore, or display a *different*, more informative warning about: https://github.com/rr-debugger/rr/blob/b8566d29a78d798d547e520fcaaa217a241430e0/src/syscalls.py#L1736-L1747 EXPECTED RESULT No warning emitted would be ideal. -- You are receiving this mail because: You are watching all bug changes.
[tellico] [Bug 445730] issues with webp images
https://bugs.kde.org/show_bug.cgi?id=445730 Robby Stephenson changed: What|Removed |Added Resolution|--- |UNMAINTAINED Status|REPORTED|RESOLVED --- Comment #4 from Robby Stephenson --- KHTML doesn't support webp (and won't in the future since it's deprecated). If Fedora switches to using the QWebEngine support in Tellico, then webp images would work, I believe. If possible, I suggest you file a wishlist against Fedora. They'll need to make an update similar to what is shown for OpenSuse in this commit https://www.mail-archive.com/commit@lists.opensuse.org/msg09940.html -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 445982] Popup of Touchpad applet does not close when systray icon is clicked
https://bugs.kde.org/show_bug.cgi?id=445982 --- Comment #2 from Nate Graham --- Embarrassing mistake, will fix. -- You are receiving this mail because: You are watching all bug changes.
[Elisa] [Bug 446400] New: Playback pauses, and the player is muted when the next song in a playlist is supposed to start.
https://bugs.kde.org/show_bug.cgi?id=446400 Bug ID: 446400 Summary: Playback pauses, and the player is muted when the next song in a playlist is supposed to start. Product: Elisa Version: 21.08.3 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: matthieu_gall...@yahoo.fr Reporter: alexsterl...@posteo.net Target Milestone: --- SUMMARY When I proceed to the next song in the playlist, the player mutes itself and the song pauses. I also had microsoft teams as a flatpak open in a meeting while this was happening STEPS TO REPRODUCE 1. Open a playlist of music or create one 2. Listen until the end of current song, wait for next track. OBSERVED RESULT Playback pauses, and player mutes EXPECTED RESULT Next song plays SOFTWARE/OS VERSIONS Linux/KDE Plasma: Void Linux KDE Plasma Version: Plasma 5.23.3 KDE Frameworks Version: 5.88.0 Qt Version: 5.15.2 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 441865] "Switch to Previous Preset" changes brush's opacity accidentally
https://bugs.kde.org/show_bug.cgi?id=441865 Protoniv changed: What|Removed |Added CC||ss93...@gmail.com --- Comment #1 from Protoniv --- *** Bug 444360 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 444360] Brush Opacity will be exchange when switching Brushes in tools other than Freehand Brush
https://bugs.kde.org/show_bug.cgi?id=444360 Protoniv changed: What|Removed |Added Resolution|--- |DUPLICATE Status|REPORTED|RESOLVED --- Comment #1 from Protoniv --- *** This bug has been marked as a duplicate of bug 441865 *** -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 441101] LightnessStength in Brush HUD configuration dialogue cannot be translated
https://bugs.kde.org/show_bug.cgi?id=441101 --- Comment #8 from amyspark --- I've debugged and fixed this locally; however, because of the way some of the paintop options are constructed, I will have to be very careful of the changes involved. For instance, the option for "smudge_length" uses actually two IDs. One of them is the ID provided to the KisCurveOptionUniformProperty (so far so good). The other, which is supposed to be its internationalizable name (like the callback-based ops) is not localized because it is also (incorrectly, semantics wise) used as the option's own ID to retrieve its settings. -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 446206] Buttons with linked stying do not appear linked
https://bugs.kde.org/show_bug.cgi?id=446206 Bug Janitor Service changed: What|Removed |Added Ever confirmed|0 |1 Status|REPORTED|ASSIGNED --- Comment #1 from Bug Janitor Service --- A possibly relevant merge request was started @ https://invent.kde.org/plasma/breeze-gtk/-/merge_requests/33 -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 446399] New: Kdenlive stops
https://bugs.kde.org/show_bug.cgi?id=446399 Bug ID: 446399 Summary: Kdenlive stops Product: kdenlive Version: 21.08.3 Platform: Mint (Ubuntu based) OS: Linux Status: REPORTED Severity: critical Priority: NOR Component: Video Display & Export Assignee: j...@kdenlive.org Reporter: fzmant...@gmail.com Target Milestone: --- I dont know how to do this but i will tell you this. I tried kdenlive in Xubuntu, Lubuntu, Linux Mint XFCE, Linux Mint Cinnamon, Linux Mint Mate and always the program stop, if anybody like me works with a unstable software like this with 5 days of working its gonna be very bad. I make small donations to lubuntu, linux mint and Gimp, if you fix this i can consider to start making a donation for you. This is serious man, users dont have to fix problems. Help linux pls SUMMARY *** NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** 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 Kdenlive: 21.08.3 MLT: 7.1.0 Qt: 5.15.3 (built against 5.15.3 x86_64-little_endian-lp64) Frameworks: 5.88.0 System: KDE Flatpak runtime Kernel: linux 5.4.0-91-generic CPU: x86_64 Windowing System: xcb Movit (GPU): disabled -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 446097] Dropdown Menu Offsets
https://bugs.kde.org/show_bug.cgi?id=446097 --- Comment #2 from mark.tus...@gmail.com --- Just doing a follow-up. I think there was a slight bug in the way KDE was handling multi-monitors that was causing this issue. I checked my Display Settings and found one monitor was overlapping another (don't know how that happened). I resolved the overlap and I haven't seen this issue for a few days. I cannot reproduce the overlap of the monitors in Display Settings at this time. I will attempt to break it again by messing with some scaling options and dragging. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 445618] mouse gesture trigger is broken does not work anymore
https://bugs.kde.org/show_bug.cgi?id=445618 Jefri changed: What|Removed |Added Summary|Can not assign mouse|mouse gesture trigger is |gesture under custom|broken does not work |shortcuts anymore |anymore -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 445982] Popup of Touchpad applet does not close when systray icon is clicked
https://bugs.kde.org/show_bug.cgi?id=445982 Nate Graham changed: What|Removed |Added Status|REPORTED|CONFIRMED Ever confirmed|0 |1 --- Comment #1 from Nate Graham --- Can reproduce. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 446285] Show KCM in search results if English title matches query, even when the system is using another language
https://bugs.kde.org/show_bug.cgi?id=446285 Fushan Wen changed: What|Removed |Added Version Fixed In||5.24 Resolution|--- |FIXED Latest Commit||https://invent.kde.org/plas ||ma/systemsettings/commit/4a ||ab8225fb24a4659b9df6b520ae7 ||11bb62f5969 Status|ASSIGNED|RESOLVED --- Comment #2 from Fushan Wen --- Git commit 4aab8225fb24a4659b9df6b520ae711bb62f5969 by Fushan Wen. Committed on 02/12/2021 at 23:33. Pushed by ngraham into branch 'master'. Always add English keywords even when the system is using another language 1. FEATURE: Always add English keywords to the list of keywords. 2. Add `doesRemoveDuplicates` bool parameter to `MenuItem::keywords`, so `removeDuplicates()` will not be done in the subitems to improve the performance. 3. Port away from deprecated `KPluginMetaData::readTranslatedString` to `KJsonUtils::readTranslatedString`. 4. Port away from foreach in `MenuItem::keywords`. 5. Add const keyword to `MenuItem::keywords`. FIXED-IN: 5.24 M +11 -4core/MenuItem.cpp M +3-1core/MenuItem.h https://invent.kde.org/plasma/systemsettings/commit/4aab8225fb24a4659b9df6b520ae711bb62f5969 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 446395] Unmounting an SD card in the internal reader using the device notified leads to it being mounted again
https://bugs.kde.org/show_bug.cgi?id=446395 Rex Dieter changed: What|Removed |Added CC||rdie...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 445691] Alpha Mask not working properly with predefined brush tips
https://bugs.kde.org/show_bug.cgi?id=445691 --- Comment #13 from Eoin O'Neill --- Hi there, I've made some more alterations to try to get the behavior of this edge case closer to Krita 4.x -- please try the new version when you get a chance. Sorry for the inconvenience, Eoin. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 446397] Cannot set Left Alt+Shift as keyboard layout switching shortcut
https://bugs.kde.org/show_bug.cgi?id=446397 --- Comment #1 from Mikhail Ramendik --- Update: the setting works in X11 because it is in /etc/X11/xorg.conf.d/00-keyboard.conf It can not be set via KDE settings which creates a regression under Wayland. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 445691] Alpha Mask not working properly with predefined brush tips
https://bugs.kde.org/show_bug.cgi?id=445691 Eoin O'Neill changed: What|Removed |Added Resolution|--- |FIXED Latest Commit|https://invent.kde.org/grap |https://invent.kde.org/grap |hics/krita/commit/5176b92ed |hics/krita/commit/357aff91f |4c24e61525e7fe89fc182c8a704 |d5c03aa58c7691a7fb8493ceff5 |c2a9|fad1 Status|CONFIRMED |RESOLVED --- Comment #12 from Eoin O'Neill --- Git commit 357aff91fd5c03aa58c7691a7fb8493ceff5fad1 by Eoin O'Neill. Committed on 02/12/2021 at 23:31. Pushed by eoinoneill into branch 'master'. Modifications to alpha mask exception for png with uniform rgb values. User wasn't happy with the previous work around, so this will hopefully be closer to what they expect with regards to behavior. M +13 -3libs/brush/kis_png_brush.cpp https://invent.kde.org/graphics/krita/commit/357aff91fd5c03aa58c7691a7fb8493ceff5fad1 -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 446398] New: Add support for OpenVPN's "remote-random-hostname" feature
https://bugs.kde.org/show_bug.cgi?id=446398 Bug ID: 446398 Summary: Add support for OpenVPN's "remote-random-hostname" feature Product: plasma-nm Version: 5.23.4 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: editor Assignee: jgrul...@redhat.com Reporter: me+kdeb...@nogweii.net Target Milestone: --- SUMMARY AWS's managed VPN offering, "AWS Client VPN" uses this feature. I can't connect using the graphical UI for NetworkManager as it doesn't pass the appropriate flag along. SOFTWARE/OS VERSIONS KDE Plasma Version: 5.23.4 KDE Frameworks Version: 5.88.0 Qt Version: 5.15.2 NetworkManager Version: 1.32.12 NetworkManager-openvpn Version: 1.8.16 ADDITIONAL INFORMATION >From OpenVPN's documentation: --remote-random-hostname Prepend a random string (6 bytes, 12 hex characters) to hostname to prevent DNS caching. For example, "foo.bar.gov" would be modified to ".foo.bar.gov". PR for GNOME, not sure if this is particularly useful: https://gitlab.gnome.org/GNOME/NetworkManager-openvpn/-/merge_requests/23 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 446397] New: Cannot set Left Alt+Shift as keyboard layout switching shortcut
https://bugs.kde.org/show_bug.cgi?id=446397 Bug ID: 446397 Summary: Cannot set Left Alt+Shift as keyboard layout switching shortcut Product: systemsettings Version: 5.23.3 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: kcm_keys Assignee: plasma-b...@kde.org Reporter: m...@ramendik.ru CC: k...@david-redondo.de Target Milestone: --- SUMMARY I need to use Left Alt+Shift to switch between keyboard layouts. I configured this when installing Fedora 33 (upgraded to 34 then35 since). In an X11 Plasma session the shortcut somehow still works; in a Wayland Plasma session it does not. In the System Settings, under Workplace > Shortcuts> Keyboard layout switcher, this shortcut is not visible and can not be set. "Switch to next keyboard layout" is set at Ctrl+Alt+K. When I expand it and click "Add custom shortcut" then press Left Alt and Shift, the shortcut is not saved. Instead, it awaits a further key press. STEPS TO REPRODUCE 1. Open KDE System Settings 2. Select Workplace > Shortcuts> Keyboard layout switcher 3. Expand Switch to next keyboard layout 4. Click +Add Custom Shortcut 5. Hold Left Alt and Shift OBSERVED RESULT No shortcut is set, the system awaits a further key press EXPECTED RESULT Left ALt+Shift shortcut is set 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.
[systemsettings] [Bug 445959] In Settings > User feedback, clicking on the links plasma-shell or plasma-discover could show a better error message if there is no log
https://bugs.kde.org/show_bug.cgi?id=445959 Bug Janitor Service changed: What|Removed |Added Status|CONFIRMED |ASSIGNED --- Comment #1 from Bug Janitor Service --- A possibly relevant merge request was started @ https://invent.kde.org/plasma/plasma-workspace/-/merge_requests/1241 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-plasma] [Bug 446396] New: Ability to prevent some actions from being auto-added to the plasmoid's header.
https://bugs.kde.org/show_bug.cgi?id=446396 Bug ID: 446396 Summary: Ability to prevent some actions from being auto-added to the plasmoid's header. Product: frameworks-plasma Version: unspecified Platform: unspecified OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: libplasma Assignee: notm...@gmail.com Reporter: ignacy.kaj...@gmail.com CC: plasma-b...@kde.org Target Milestone: --- Created attachment 144158 --> https://bugs.kde.org/attachment.cgi?id=144158=edit Applet window open. I want to get rid of actions marked with the red square, while still keeping the "Configure Window Tililng" action in the applet's header. SUMMARY Currently, there is no way to exclude some actions from being auto-added to the applet's header (see attached screenshot). I don't want actions marked with the red square to be listed in the applet's header. I still want to have them in the applet's context menu, though. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 446395] New: Unmounting an SD card in the internal reader using the device notified leads to it being mounted again
https://bugs.kde.org/show_bug.cgi?id=446395 Bug ID: 446395 Summary: Unmounting an SD card in the internal reader using the device notified leads to it being mounted again Product: plasmashell Version: 5.23.3 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Disks & Devices Assignee: plasma-b...@kde.org Reporter: m...@ramendik.ru Target Milestone: 1.0 SUMMARY I have KDE Plasma. Plasma has a removable device notifier. The "Automatically mount all removable media when attached " option is turned on. When I put an SD card into the laptop's built-in reader, the card is mounted. But when I click "Safely remove" for that card, it is immediately mounted again! I have to use "sudo umount" to unmount it. The laptop is ThinkPad P1Gen3. The issue does *not* seem to happen with an external card reader (attached via USB), nor with a USB flash drive. But it happens every time with the internal SD card reader. STEPS TO REPRODUCE 1. In the KDE Settings under "removable devices" ensure that the "Automatically mount all removable media when attached " option is turned on. 2. Insert SD card into laptop. 3. List the files on the SD card to ensure it is mounted. 4. Click the device notifier icon and click "Safely remove" for the card. OBSERVED RESULT The card now appears in the notifier twice, one of the entries is greyed out. After I close and reopen the notifier the card is there only once. At all times, the card remains mounted and the "Safely remove" button is offered again. EXPECTED RESULT Card is unmounted. "Mount and Open" button is offered in the Device Notifier for the card SOFTWARE/OS VERSIONS Linux/KDE Plasma: (available in About System) KDE Plasma Version: 5.23.3 KDE Frameworks Version: 5.88.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION This is a long-standing issue; I noticed it first in Fedora 33. The kernel is 5.15 but it was something like 5.9 when I noticed the issue first. -- You are receiving this mail because: You are watching all bug changes.
[xdg-desktop-portal-kde] [Bug 445829] screen sharing on Plasma Wayland on Nixos unstable does not work
https://bugs.kde.org/show_bug.cgi?id=445829 p3dima...@hotmail.it changed: What|Removed |Added Resolution|--- |DOWNSTREAM Status|REPORTED|RESOLVED --- Comment #1 from p3dima...@hotmail.it --- So I wwas ablo to fix it in Nixos -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 446394] std.ics keeps crashing just by using system
https://bugs.kde.org/show_bug.cgi?id=446394 Allen Winter changed: What|Removed |Added CC||win...@kde.org --- Comment #1 from Allen Winter --- this is clearly a crash in the latest libical library release. a dupe of https://github.com/libical/libical/issues/528 would you be able to send me (by email is fine) the ics file that's causing the crash? I see a potential fix in libical but I'd like to verify using your ics file. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 446381] Temporary rules are not deleted from the config file
https://bugs.kde.org/show_bug.cgi?id=446381 Ismael Asensio changed: What|Removed |Added Summary|kwinrules not saved upon|Temporary rules are not |reboot. |deleted from the config ||file Ever confirmed|0 |1 Status|REPORTED|CONFIRMED --- Comment #3 from Ismael Asensio --- (In reply to r1ntse.a from comment #2) > (In reply to Ismael Asensio from comment #1) > > It seems you set the rule to "Force temporarily" (blockcompositingrule=6) > > > > By design this setting forces the rule while the window is active and then > > deletes it, since it's a temporary setting > > If you'd like to have it permanently please set it to "Force" instead. > > > > There's a bug though, and it's that it keeps it on the kwinrulesrc file. > > I completely misunderstood what "temporarily" indicates in that case. Sorry > for the report. Don't be. It was a very good and thorough report, with all the information required to figure it out. And it exposed something that it isn't working right, so thanks a lot for your time on it! If you don't mind, I'll change the title of the bug to track that temporary rules are not deleted from the config file. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 446381] kwinrules not saved upon reboot.
https://bugs.kde.org/show_bug.cgi?id=446381 --- Comment #2 from r1nts...@gmail.com --- (In reply to Ismael Asensio from comment #1) > It seems you set the rule to "Force temporarily" (blockcompositingrule=6) > > By design this setting forces the rule while the window is active and then > deletes it, since it's a temporary setting > If you'd like to have it permanently please set it to "Force" instead. > > There's a bug though, and it's that it keeps it on the kwinrulesrc file. I completely misunderstood what "temporarily" indicates in that case. Sorry for the report. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 445691] Alpha Mask not working properly with predefined brush tips
https://bugs.kde.org/show_bug.cgi?id=445691 Eoin O'Neill changed: What|Removed |Added Status|REOPENED|CONFIRMED -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 445691] Alpha Mask not working properly with predefined brush tips
https://bugs.kde.org/show_bug.cgi?id=445691 --- Comment #11 from Eoin O'Neill --- I will confirm this bug and come up with another fix -- I presume that the issue at hand here is that this work around will cause some backward compatibility issues with resources defined in Krita 4.x However, it is worth noting that the image in question is not properly defined for your intended use case and that any fix here is a work around for that. Simply changing the source image to have no alpha mask would fix the behavior. That is basically what I will do behind-the-scenes, but I think that we should plan to migrate away from this fix long term and resources should be properly updated to reflect the new design. -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 446394] New: std.ics keeps crashing just by using system
https://bugs.kde.org/show_bug.cgi?id=446394 Bug ID: 446394 Summary: std.ics keeps crashing just by using system Product: Akonadi Version: unspecified Platform: Debian testing OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: ICal file resource Assignee: kdepim-b...@kde.org Reporter: kram.et...@gmail.com Target Milestone: --- Application: akonadi_ical_resource (5.18.1 (21.08.1)) Qt Version: 5.15.2 Frameworks Version: 5.88.0 Operating System: Linux 5.15.0-1-amd64 x86_64 Windowing System: X11 Distribution: Debian GNU/Linux bookworm/sid DrKonqi: 5.23.3 [KCrashBackend] -- Information about the crash: - What I was doing when the application crashed: After logging in, std.ics keeps crashing. Reloading application leads to repeated crash within seconds The crash can be reproduced every time. -- Backtrace: Application: std.ics (akonadi_ical_resource), signal: Segmentation fault [KCrash Handler] #4 0x7f098a62c034 in cleanVObject (o=0x55a1d8c0c400) at ./src/libicalvcal/vobject.c:591 #5 0x7f098a6304d5 in finiLex () at ./src/libicalvcal/vcc.c:855 #6 Parse_MIMEHelper () at ./src/libicalvcal/vcc.c:1171 #7 0x7f098a630672 in Parse_MIME_FromFile (file=file@entry=0x55a1d8a50bd0) at ./src/libicalvcal/vcc.c:1209 #8 0x7f098a6306ed in Parse_MIME_FromFileName (fname=0x55a1d8c0d8a8 "/home/kuby/Bureaublad/afspraak.ics") at ./src/libicalvcal/vcc.c:1220 #9 0x7f098c4ada07 in KCalendarCore::VCalFormat::load (this=this@entry=0x7fff84c17f60, calendar=..., fileName=...) at ./src/vcalformat.cpp:92 #10 0x7f098c44c32d in KCalendarCore::FileStorage::load (this=0x55a1d8bdc1f0) at ./src/filestorage.cpp:117 #11 0x55a1d8023ee7 in ?? () #12 0x7f098c3ea680 in Akonadi::SingleFileResourceBase::setLocalFileName(QString const&) () from /usr/lib/x86_64-linux-gnu/libakonadi-singlefileresource.so.5 #13 0x7f098c3ebfa4 in Akonadi::SingleFileResourceBase::readLocalFile(QString const&) () from /usr/lib/x86_64-linux-gnu/libakonadi-singlefileresource.so.5 #14 0x55a1d80228fb in ?? () #15 0x7f098b471d6e in QObject::event (this=0x7fff84c18610, e=0x55a1d8bc74e0) at kernel/qobject.cpp:1314 #16 0x7f098bbd86af in QApplicationPrivate::notify_helper (this=, receiver=0x7fff84c18610, e=0x55a1d8bc74e0) at kernel/qapplication.cpp:3632 #17 0x7f098b44575a in QCoreApplication::notifyInternal2 (receiver=0x7fff84c18610, event=0x55a1d8bc74e0) at kernel/qcoreapplication.cpp:1063 #18 0x7f098b4487a7 in QCoreApplicationPrivate::sendPostedEvents (receiver=0x0, event_type=0, data=0x55a1d8a54f10) at kernel/qcoreapplication.cpp:1817 #19 0x7f098b49d733 in postEventSourceDispatch (s=0x55a1d8b8ccc0) at kernel/qeventdispatcher_glib.cpp:277 #20 0x7f09893b5c7b in g_main_context_dispatch () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #21 0x7f09893b5f28 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #22 0x7f09893b5fdf in g_main_context_iteration () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #23 0x7f098b49cdb4 in QEventDispatcherGlib::processEvents (this=0x55a1d8b90510, flags=...) at kernel/qeventdispatcher_glib.cpp:423 #24 0x7f098b44416b in QEventLoop::exec (this=this@entry=0x7fff84c18580, flags=..., flags@entry=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:69 #25 0x7f098b44c440 in QCoreApplication::exec () at ../../include/QtCore/../../src/corelib/global/qflags.h:121 #26 0x55a1d80235e1 in ?? () #27 0x7f098add0e4a in __libc_start_main (main=0x55a1d801f4a0, argc=3, argv=0x7fff84c187a8, init=, fini=, rtld_fini=, stack_end=0x7fff84c18798) at ../csu/libc-start.c:314 #28 0x55a1d801f4da in ?? () [Inferior 1 (process 4772) detached] Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 446377] File link instead of copy
https://bugs.kde.org/show_bug.cgi?id=446377 caulier.gil...@gmail.com changed: What|Removed |Added Version Fixed In||7.4.0 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 445691] Alpha Mask not working properly with predefined brush tips
https://bugs.kde.org/show_bug.cgi?id=445691 --- Comment #10 from Eoin O'Neill --- (In reply to Andreas Resch from comment #9) > I just tried the fix in the latest build of today and the issue still isn't > fixed. There's an additional bug now. When I select the brush tip with the > included alpha mask, the Brush Mode jumps to "Lightness" instead of "Alpha > Mask". And when I switch the Brush Mode back to Alpha Mask, the brush tip is > transparent like it was before. The issue is that your brush tip is not designed to be used with Alpha mask because it isn't defined like a mask should be. (It should be black and white with no alpha.) I'm sorry but because of the new alpha mask changes for RGBA brushes, I'm not entirely sure I understand the desired behavior here. If you want to use this as an alpha mask, then please define it like an alpha mask should be. Is there a particular reason why `Lightness` doesn't work for your given use case? -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 435902] Error message "insufficient privileges" on the database...
https://bugs.kde.org/show_bug.cgi?id=435902 caulier.gil...@gmail.com changed: What|Removed |Added Summary|error massage = |Error message "insufficient |insufficient privileges on |privileges" on the |the database... |database... --- Comment #10 from caulier.gil...@gmail.com --- Dan, Instructions from comment #9 can solve your problem ? Best Gilles Caulier -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 446167] Searching immediately upon opening Discover returns worse search results compared to if you wait a few seconds before searching
https://bugs.kde.org/show_bug.cgi?id=446167 Nate Graham changed: What|Removed |Added CC||giuseppebelluzz...@gmail.co ||m --- Comment #5 from Nate Graham --- *** Bug 446392 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 446392] unrelated search results
https://bugs.kde.org/show_bug.cgi?id=446392 Nate Graham changed: What|Removed |Added Resolution|--- |DUPLICATE Status|REPORTED|RESOLVED CC||n...@kde.org --- Comment #1 from Nate Graham --- This specific issue is the same as Bug 446167 which is solved with a new AppStream version that is supposed to be released today or tomorrow. *** This bug has been marked as a duplicate of bug 446167 *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 446380] [Wayland] Wrong positioning of popups for icons in Status and Notifications
https://bugs.kde.org/show_bug.cgi?id=446380 Patrick Silva changed: What|Removed |Added CC||bugsefor...@gmx.com --- Comment #2 from Patrick Silva --- possibly duplicate of bug 443843 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kuserfeedback] [Bug 442296] "CMake Error: The INTERFACE_QT_MAJOR_VERSION property of "Qt5::Core" does not agree with the value of QT_MAJOR_VERSION already determined for KUserFeedbackQml /
https://bugs.kde.org/show_bug.cgi?id=442296 --- Comment #2 from Volker Krause --- According to the CMake log this is building against Qt 6.2.0, not Qt 5.15.2 as probably intended according to the report. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-plasma] [Bug 445518] KDE Plasma doesn't respect icon theme for some applications and application icons
https://bugs.kde.org/show_bug.cgi?id=445518
--- Comment #16 from Rodney Dawes ---
OK. I've recreated the problem, and updated the 171 PR to address the issue as
it seems `DESTDIR=foo cmake --install build` results in the `$ENV{DESTDIR}` in
the install script not being interpreted properly. Escaping as `\$ENV{}` seems
to solve the issue here, so 171 should be good in this case now.
--
You are receiving this mail because:
You are watching all bug changes.
[plasmashell] [Bug 446379] Resizing with snapping/tiling shortcuts
https://bugs.kde.org/show_bug.cgi?id=446379 Nate Graham changed: What|Removed |Added Resolution|--- |DUPLICATE CC||n...@kde.org Status|REPORTED|RESOLVED --- Comment #1 from Nate Graham --- *** This bug has been marked as a duplicate of bug 411462 *** -- You are receiving this mail because: You are watching all bug changes.
[frameworks-plasma] [Bug 411462] Plasma dialogs (applet popups, OSDs, notifications) should not be movable, maximizable, or minimizable, or tilable
https://bugs.kde.org/show_bug.cgi?id=411462 Nate Graham changed: What|Removed |Added CC||art...@bols.dev --- Comment #17 from Nate Graham --- *** Bug 446379 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 446380] [Wayland] Wrong positioning of popups for icons in Status and Notifications
https://bugs.kde.org/show_bug.cgi?id=446380 Nate Graham changed: What|Removed |Added Ever confirmed|0 |1 CC||n...@kde.org, ||notm...@gmail.com, ||vlad.zahorod...@kde.org Severity|normal |minor Status|REPORTED|CONFIRMED Keywords||wayland --- Comment #1 from Nate Graham --- Can confirm. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 446375] No animation when hovering over different apps in the taskbar when using wayland.
https://bugs.kde.org/show_bug.cgi?id=446375 Nate Graham changed: What|Removed |Added Latest Commit||https://invent.kde.org/fram ||eworks/plasma-framework/-/c ||ommit/63f9d3ce5d5bbb17eb1ac ||3e19fec5d487f98e80a Version Fixed In|5.24|5.89 --- Comment #2 from Nate Graham --- Oh actually it was fixed in a framework, so it should be in Frameworks 5.89! -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 446375] No animation when hovering over different apps in the taskbar when using wayland.
https://bugs.kde.org/show_bug.cgi?id=446375 Nate Graham changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |FIXED CC||n...@kde.org Version Fixed In||5.24 --- Comment #1 from Nate Graham --- Ooh this was fixed recently in Plasma 5.24! -- You are receiving this mail because: You are watching all bug changes.
[plasma-systemmonitor] [Bug 446372] Changing polling time makes "Network & System" sections in the main page blank
https://bugs.kde.org/show_bug.cgi?id=446372 Nate Graham changed: What|Removed |Added Status|RESOLVED|REPORTED Resolution|DUPLICATE |--- --- Comment #2 from Nate Graham --- Whoops! Wrong bug report, sorry. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-plasma] [Bug 446364] Highlights overlapping / off centre
https://bugs.kde.org/show_bug.cgi?id=446364 Nate Graham changed: What|Removed |Added CC||n...@kde.org Resolution|--- |DUPLICATE Status|REPORTED|RESOLVED --- Comment #1 from Nate Graham --- *** This bug has been marked as a duplicate of bug 445516 *** -- You are receiving this mail because: You are watching all bug changes.
[frameworks-plasma] [Bug 445516] Cache-related visual glitches when Plasma theme SVGs or Plasma Components are updated
https://bugs.kde.org/show_bug.cgi?id=445516 Nate Graham changed: What|Removed |Added CC||proleth...@freenet.de --- Comment #17 from Nate Graham --- *** Bug 446364 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[frameworks-plasma] [Bug 445516] Cache-related visual glitches when Plasma theme SVGs or Plasma Components are updated
https://bugs.kde.org/show_bug.cgi?id=445516 Nate Graham changed: What|Removed |Added CC||sephiroth...@hotmail.it --- Comment #16 from Nate Graham --- *** Bug 446372 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[plasma-systemmonitor] [Bug 446372] Changing polling time makes "Network & System" sections in the main page blank
https://bugs.kde.org/show_bug.cgi?id=446372 Nate Graham changed: What|Removed |Added Resolution|--- |DUPLICATE Status|REPORTED|RESOLVED CC||n...@kde.org --- Comment #1 from Nate Graham --- *** This bug has been marked as a duplicate of bug 445516 *** -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 446363] EXIF of image cannot be read on windows
https://bugs.kde.org/show_bug.cgi?id=446363 --- Comment #7 from Maik Qualmann --- I see that we resolve a possible symlink to a complete path for the save path to Exiv2. We can try the same when loading. The question is whether it works under Windows or has side effects, for example in connection with sidecars. Maik -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 432104] stylus/pen input does not work on window decorations
https://bugs.kde.org/show_bug.cgi?id=432104 Nate Graham changed: What|Removed |Added CC||personalizedrefrigerator@gm ||ail.com --- Comment #7 from Nate Graham --- *** Bug 446371 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 446371] [Wayland/Stylus] Can't drag windows
https://bugs.kde.org/show_bug.cgi?id=446371 Nate Graham changed: What|Removed |Added CC||n...@kde.org Status|REPORTED|RESOLVED Resolution|--- |DUPLICATE --- Comment #1 from Nate Graham --- Fixed in 5.24 already! *** This bug has been marked as a duplicate of bug 432104 *** -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 446369] Trying to update a Flatpak always crashes Discover
https://bugs.kde.org/show_bug.cgi?id=446369 Nate Graham changed: What|Removed |Added CC||n...@kde.org Status|REPORTED|NEEDSINFO Resolution|--- |BACKTRACE --- Comment #1 from Nate Graham --- Can you attach a backtrace of the crash? See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 446393] New: Corrupted save file
https://bugs.kde.org/show_bug.cgi?id=446393 Bug ID: 446393 Summary: Corrupted save file Product: kdenlive Version: 21.08.3 Platform: Appimage OS: Linux Status: REPORTED Severity: critical Priority: NOR Component: User Interface Assignee: j...@kdenlive.org Reporter: randall.wa...@gmail.com Target Milestone: --- SUMMARY *** Save file corrupted with latest appimage. Have had this happen three times now. Multiple hours worth of work lost. Deadline missed. *** STEPS TO REPRODUCE 1. Create project add clips with simple wipe affects 2. Save project 3. Reopen kdenlive, Open project OBSERVED RESULT Wipes in the wrong places, missing clips, clips not the correct length EXPECTED RESULT I EXPECTED THE F*CKING THING TO SAVE ITS OWN DATA PROPERLY! SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: Ubuntu 20.04.3 (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION Will send whatever you want to see. Might also have you explain to my boss why your software made me repeat two days worth of work and cost us a deadline. Thanks for that. -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 439525] Spectacle crashes when export using KIPI plugins
https://bugs.kde.org/show_bug.cgi?id=439525 Alexander Lohnau changed: What|Removed |Added Resolution|--- |FIXED Status|REPORTED|RESOLVED -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 439525] Spectacle crashes when export using KIPI plugins
https://bugs.kde.org/show_bug.cgi?id=439525 Alexander Lohnau changed: What|Removed |Added CC||alexander.loh...@gmx.de Version Fixed In||21.04.3 Latest Commit||https://invent.kde.org/grap ||hics/spectacle/-/commit/f7b ||57e12026875e09de61b6f497787 ||f443806018 -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 446392] New: unrelated search results
https://bugs.kde.org/show_bug.cgi?id=446392 Bug ID: 446392 Summary: unrelated search results Product: Discover Version: 5.23.3 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: PackageKit Assignee: lei...@leinir.dk Reporter: giuseppebelluzz...@gmail.com CC: aleix...@kde.org Target Milestone: --- SUMMARY Often, when searching with Discover you won't get related search results. In example if you search obs you will have a very long list of unrelated packages (no obs studio isn't there), and after all the packages in the repo it will list "obs studio" flatpak. The issue is that the obs studio is found with a simple "dnf search" via terminal (if you have rpm repositories enabled). STEPS TO REPRODUCE 1. On Fedora, enable the rpm repositories and also the flathub repo 2. Open discover and search "obs" 3. In alternative to point 2. is possible to type in a terminal "plasma-discover --backends flatpak-backend,packagekit-backend --search obs" OBSERVED RESULT In both cases you won't see obs studio among the first results. And only near the end of the long list you have one obs studio but is flatpak. EXPECTED RESULT obs studio as first result, and the ability to change the source from flatpak to repo SOFTWARE/OS VERSIONS Fedora 35 KDE Plasma Version: 5.23.3 KDE Frameworks Version: 5.88.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION If you search "obs studio" with discover or "obs\ studio" with the terminal command written above, the results are more pertinent but still only the flatpak is shown. Bonus: if you search obs studio in the terminal with "appstreamcli search obs studio" it won't list obs studio as result but blender NOTE For convenience this was reported with obs studio, but I would expect this behaviour to affect other packages as well -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 435902] error massage = insufficient privileges on the database...
https://bugs.kde.org/show_bug.cgi?id=435902 caulier.gil...@gmail.com changed: What|Removed |Added Version|unspecified |7.1.0 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 444320] Selected brush resets after opening a first file
https://bugs.kde.org/show_bug.cgi?id=444320 --- Comment #12 from Manga Tengu --- Sorry, my file is way too big to be attached. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 444320] Selected brush resets after opening a first file
https://bugs.kde.org/show_bug.cgi?id=444320 --- Comment #11 from Manga Tengu --- Yes I do have it. I'll join it here. The issue did happen again and I deleted the file a few times but I just can't pinpoint how to reproduce it... -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 435902] error massage = insufficient privileges on the database...
https://bugs.kde.org/show_bug.cgi?id=435902 Real Name changed: What|Removed |Added Version|7.1.0 |unspecified CC||ne...@posteo.net --- Comment #9 from Real Name --- If youre running Windows and this error pops up, make sure you have allowed digikam.exe in Windows Defenders "controlled folder access". Wem auf Windows diese Fehlermeldung aufpoppt darf nicht vergessen digikam im "Überwachter Ordnerzugriff" freizugeben. Type in Windows search " controlled folder access ". Then " allow app ... " / .. add app / recently blocked app / digikam.exe In Windows Suche " überwachter Ordnerzugriff " eingeben. Dann "App ... zulassen " / Zulässige App hinzufügen / zuletzt blockierte.. /digikam.exe This solved " you have insufficient privileges on the database. Following privileges are not assigned to you: CREATE TABLE Check you privileges on the database and restart digikam " error message. Das löst die " Sie besitzen nicht die benötigten Rechte für die Datenbank. Sie besitzen folgende Rechte nicht: CREATE TABLE. Überprüfen sie Ihre Rechte für die Datenbank und starten Sie digiKam neu " Fehlermeldung. Cheers Prost -- You are receiving this mail because: You are watching all bug changes.
[kipiplugins] [Bug 442652] Spectacle crashed in KIPI::Interface::hasFeature() when using "Export to Flash" functionality
https://bugs.kde.org/show_bug.cgi?id=442652 Nate Graham changed: What|Removed |Added Resolution|--- |FIXED Status|REPORTED|RESOLVED --- Comment #1 from Nate Graham --- The flash plugin has been deleted. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 443968] When switching activities, sometimes a tiny "Plasma Desktop Workspace" window appears
https://bugs.kde.org/show_bug.cgi?id=443968 Yaroslav Sidlovsky changed: What|Removed |Added CC||zawer...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 446363] EXIF of image cannot be read on windows
https://bugs.kde.org/show_bug.cgi?id=446363 --- Comment #6 from wuye9...@gmail.com --- Thanks. But the tricky thing is the JPEG looks good even it is sym linked. Do you have any plan that use ExifTool to instead Exiv2 in metadata engine? -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 446391] New: Slow window redraw on resize
https://bugs.kde.org/show_bug.cgi?id=446391 Bug ID: 446391 Summary: Slow window redraw on resize Product: systemsettings Version: 5.23.3 Platform: Compiled Sources OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: lesinar...@gmail.com Target Milestone: --- Created attachment 144157 --> https://bugs.kde.org/attachment.cgi?id=144157=edit Screenshot demonstating bug System Settings redraws its window on resize way too slow while running under X11 resulting in black areas Reproducing: * Log into X11 session * Launch systemsettings5 * Try to resize KDE Plasma: 5.23.3 KF5: 5.88.0 Qt5: 5.15.2 -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 401581] Win+P still assumes the monitors position wrongly, ignoring the Display Configuration.
https://bugs.kde.org/show_bug.cgi?id=401581 luca.de.mart...@protonmail.com changed: What|Removed |Added CC||luca.de.martini@protonmail. ||com --- Comment #1 from luca.de.mart...@protonmail.com --- This is still broken in plasma 5.22.5 Also, the problem is not only limited to the display position, but the primary display is also forgotten! The two displays are Display port and HDMI and the HDMI one is always set as primary in my case. This is really annoying and broken since forever -- You are receiving this mail because: You are watching all bug changes.
