[digikam] [Bug 406583] Cannot write special characters (è, í, ó) in Tag search box
https://bugs.kde.org/show_bug.cgi?id=406583 --- Comment #8 from caulier.gil...@gmail.com --- With next digiKam 7.4.0 release, AppImage bundle is compiled using a more recent Linux Mageia 7.1 host. Last stable Qt 5.15.2 and KF5 5.84 are used. ImageMagick codec 7 and libav 58 (ffmpeg) are used to supports extra image and video formats. https://i.imgur.com/XV1tZkL.png Please check if problem still reproducible with this version available as pre-release here: https://files.kde.org/digikam/ Gilles Caulier -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 436345] Renamed FaceTags not written to file metadata
https://bugs.kde.org/show_bug.cgi?id=436345 --- Comment #9 from caulier.gil...@gmail.com --- With next digiKam 7.4.0 release, AppImage bundle is compiled using a more recent Linux Mageia 7.1 host. Last stable Qt 5.15.2 and KF5 5.84 are used. ImageMagick codec 7 and libav 58 (ffmpeg) are used to supports extra image and video formats. https://i.imgur.com/XV1tZkL.png Please check if problem still reproducible with this version available as pre-release here: https://files.kde.org/digikam/ Gilles Caulier -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 395748] Problem with printig
https://bugs.kde.org/show_bug.cgi?id=395748 --- Comment #6 from caulier.gil...@gmail.com --- With next digiKam 7.4.0 release, AppImage bundle is compiled using a more recent Linux Mageia 7.1 host. Last stable Qt 5.15.2 and KF5 5.84 are used. ImageMagick codec 7 and libav 58 (ffmpeg) are used to supports extra image and video formats. https://i.imgur.com/XV1tZkL.png Please check if problem still reproducible with this version available as pre-release here: https://files.kde.org/digikam/ Gilles Caulier -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 397293] libpng error: profile 'icc': 0h: PCS illuminant is not D50
https://bugs.kde.org/show_bug.cgi?id=397293 --- Comment #8 from caulier.gil...@gmail.com --- With next digiKam 7.4.0 release, AppImage bundle is compiled using a more recent Linux Mageia 7.1 host. Last stable Qt 5.15.2 and KF5 5.84 are used. ImageMagick codec 7 and libav 58 (ffmpeg) are used to supports extra image and video formats. https://i.imgur.com/XV1tZkL.png Please check if problem still reproducible with this version available as pre-release here: https://files.kde.org/digikam/ Gilles Caulier -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 414163] SyncMeta fails for a few files
https://bugs.kde.org/show_bug.cgi?id=414163 --- Comment #3 from caulier.gil...@gmail.com --- With next digiKam 7.4.0 release, AppImage bundle is compiled using a more recent Linux Mageia 7.1 host. Last stable Qt 5.15.2 and KF5 5.84 are used. ImageMagick codec 7 and libav 58 (ffmpeg) are used to supports extra image and video formats. https://i.imgur.com/XV1tZkL.png Please check if problem still reproducible with this version available as pre-release here: https://files.kde.org/digikam/ Gilles Caulier -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 405235] Slow startup and new file scan on low latency networks
https://bugs.kde.org/show_bug.cgi?id=405235 --- Comment #7 from caulier.gil...@gmail.com --- With next digiKam 7.4.0 release, AppImage bundle is compiled using a more recent Linux Mageia 7.1 host. Last stable Qt 5.15.2 and KF5 5.84 are used. ImageMagick codec 7 and libav 58 (ffmpeg) are used to supports extra image and video formats. https://i.imgur.com/XV1tZkL.png Please check if problem still reproducible with this version available as pre-release here: https://files.kde.org/digikam/ Gilles Caulier -- You are receiving this mail because: You are watching all bug changes.
[baloo-widgets] [Bug 341288] No Exif-data shown, if pictures are accessed from remote drives (NAS)
https://bugs.kde.org/show_bug.cgi?id=341288 tagwer...@innerjoin.org changed: What|Removed |Added CC||tagwer...@innerjoin.org --- Comment #3 from tagwer...@innerjoin.org --- (In reply to Frank Reininghaus from comment #1) > We use a widget from the Baloo library to display information about files in > the Information Panel, so this would have to be implemented in Baloo. Dolphin no longer depends on baloo running (or having indexed the particular folder), see Bug 434565: https://bugs.kde.org/show_bug.cgi?id=434565#c7 Not sure whether this means it skips using the baloo libraries or not. If I install Samba filesharing on a test Neon VM apt install kdenetwork-filesharing samba Then share a folder (via the folder's properties and the sharing tab) and connect from second 'client' Neon VM, I do not see attributes shown for the files: Extended attributes (tags, ratings or comments) and embedded EXIF info (such as Height, Width, Date Photographed for images) on the server are not displayed on the client - even in the F11 information panel or the file properties (does not present the "Details" tab) It is seemingly possible to add/edit the extended attributes on the client (add tags and comments, change ratings). These are not written to the server and no error message if given. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 432270] Transition of focus from search box to search results list eats a down arrow keystroke unintuitively
https://bugs.kde.org/show_bug.cgi?id=432270 --- Comment #15 from Alex --- Nice work Noah! -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 432270] Transition of focus from search box to search results list eats a down arrow keystroke unintuitively
https://bugs.kde.org/show_bug.cgi?id=432270 --- Comment #16 from ad1r...@hotmail.fr --- Just thank you ! :) -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 440025] New: `xrandr --scale` makes panels and notifications only update once a second on nouveau driver.
https://bugs.kde.org/show_bug.cgi?id=440025 Bug ID: 440025 Summary: `xrandr --scale` makes panels and notifications only update once a second on nouveau driver. Product: kwin Version: 5.22.3 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: major Priority: NOR Component: appmenu Assignee: kwin-bugs-n...@kde.org Reporter: albertse...@gmail.com Target Milestone: --- SUMMARY `xrnadr --scale` makes panels and notifications only update once a second on nouveau driver. STEPS TO REPRODUCE 1. Use nouveau driver for Nvidia Card. 2. Hover over icons in panel 3. The panel only updates once every second. OBSERVED RESULT When using `xrandr --scale 1.25x1.25` or any value higher than one: Panels and notification pop ups only update every one or two sends (basically they are running at 1 or 0.5 fps) This happens to the widgets in the panel, meaning if I click on network manager icon the menu renders at a smoothly. This can also be more visible by the date and time only updating once every 2 seconds. The same thing happens with notifications. EXPECTED RESULT The panel should update immediately. Meaning if I click or hover over an item it should react immediately. (highlight or open) SOFTWARE/OS VERSIONS Linux/KDE Plasma: Arch Linux (available in About System) KDE Plasma Version: 5.22.3 KDE Frameworks Version: 5.84.0 Qt Version: 5.12.2 ADDITIONAL INFORMATION The panel updates fine on proprietary driver with `xrandr --scale` -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 425352] Cursor is huge and jagged
https://bugs.kde.org/show_bug.cgi?id=425352 --- Comment #6 from david3w...@gmail.com --- Good morning Giles I appreciate your efforts to resolve this cursor issue. I downloaded the 7.4 appimage from your link. Unfortunately it can't get it to open. So unable to comment. kind regards David Ward Get TypeApp for Android On 19 Jul 2021, 7:53 am, at 7:53 am, bugzilla_nore...@kde.org wrote: >https://bugs.kde.org/show_bug.cgi?id=425352 > >--- Comment #5 from caulier.gil...@gmail.com --- >With next digiKam 7.4.0 release, AppImage bundle is compiled using a >more >recent Linux Mageia 7.1 host. Last stable Qt 5.15.2 and KF5 5.84 are >used. >ImageMagick codec 7 and libav 58 (ffmpeg) are used to supports extra >image and >video formats. > >https://i.imgur.com/XV1tZkL.png > >Please check if problem still reproducible with this version available >as >pre-release here: > >https://files.kde.org/digikam/ > >Gilles Caulier > >-- >You are receiving this mail because: >You reported the bug. -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 431402] Make it possible to scale down/zoom out images further than the window width/height
https://bugs.kde.org/show_bug.cgi?id=431402 --- Comment #26 from eisenschweinchen --- Hi everyone, is there a new status on this? Is the compromise I described a viable path between the prevailing opinions? When can we expect the implementation? No pressure ;-)) -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 425352] Cursor is huge and jagged
https://bugs.kde.org/show_bug.cgi?id=425352 --- Comment #7 from caulier.gil...@gmail.com --- > Unfortunately it can't get it to open. What do you mean exactly ? Did you set this file as executable (chmod +r) ? Gilles Caulier -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 425352] Cursor is huge and jagged
https://bugs.kde.org/show_bug.cgi?id=425352 --- Comment #8 from david3w...@gmail.com --- Giles I set the file as executable using Nautilus file manager. I then right click and select run Just as I have done with other appimage files including Digikam. Nothing happens - it does not open! I downloaded the smaller of the two appimage files digiKam-7.4.0-20210718T194158-x86-64.appimage Hope that helps Regards David Ward Get TypeApp for Android On 19 Jul 2021, 08:39, at 08:39, bugzilla_nore...@kde.org wrote: >https://bugs.kde.org/show_bug.cgi?id=425352 > >--- Comment #7 from caulier.gil...@gmail.com --- >> Unfortunately it can't get it to open. > >What do you mean exactly ? > >Did you set this file as executable (chmod +r) ? > >Gilles Caulier > >-- >You are receiving this mail because: >You reported the bug. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-solid] [Bug 409207] dolphin / device manager can't mount usb disks
https://bugs.kde.org/show_bug.cgi?id=409207 davidblunkett changed: What|Removed |Added Status|NEEDSINFO |RESOLVED --- Comment #2 from davidblunkett --- Ubuntu 20.04.2 LTS No longer an issue - closing -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 440026] New: Shortcut to directly set a filter for assigned star ratings in thumbnail view
https://bugs.kde.org/show_bug.cgi?id=440026 Bug ID: 440026 Summary: Shortcut to directly set a filter for assigned star ratings in thumbnail view Product: gwenview Version: unspecified Platform: Other OS: Other Status: REPORTED Severity: wishlist Priority: NOR Component: general Assignee: gwenview-bugs-n...@kde.org Reporter: nachri...@dennisgraeser.de Target Milestone: --- I ask to introduce a new shortcut for Gwenview to directly set a filter for previously assigned star ratings in the thumbnail view. This could be for example CTRL+1 for the filter more than 1 star. Analogously CTRL+2,3,4,5. It can also be another shortcut, e.g. SHIFT+STRG+NUMBER.The same shortcut could reset the filter. This would improve the workflow considerably, because you don't have to take the mouse in your hand to click on the Filter button. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 440027] New: Wayland crashes after login
https://bugs.kde.org/show_bug.cgi?id=440027 Bug ID: 440027 Summary: Wayland crashes after login Product: kwin Version: 5.22.3 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: wayland-generic Assignee: kwin-bugs-n...@kde.org Reporter: slartibar...@gmail.com Target Milestone: --- I am running fc34 with zawertun copr repos enabled (newest plasma releases, also updates-testing enabled) and when trying to enter the wayland desktop, the DE background shows for a short time and dies immediately. This happens several times in a row (switching between DE-background and vconsole) until it gives up and shows the login screen again. Using plasma with x11 is fine, btw. I attached an excerpt of the journalctl output, it seems that kwin crashes Any idea what can be done to address this problem (and what further data is needed to analyze this?) The system is an i5 with integrated intel graphics with a 4k displayPort attached monitor. The wayland desktop was running properly with fc33 (plasma 5.21 or similar), but i didn't test it further at that time. Just saying, the DE was usable and did not crash, but i switched back to x11 then. === Process 3325 (kwin_wayland) of user 10001 dumped core. Stack trace of thread 3325: #0 0x7f219354cc01 _ZN4KWin27KeyboardLayoutDBusInterface18qt_static_metacallEP7QObjectN11QMetaObject4CallEiPPv (libkwin.so.5 + 0xfac01) #1 0x7f219354cf43 _ZN4KWin27KeyboardLayoutDBusInterface11qt_metacallEN11QMetaObject4CallEiPPv (libkwin.so.5 + 0xfaf43) Jul 18 22:33:08 m910x audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=systemd-coredump@0-3768-0 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' Jul 18 22:33:08 m910x akonadi_followupreminder_agent[3731]: The Wayland connection broke. Did the Wayland compositor die? Jul 18 22:33:08 m910x klauncher[3606]: The Wayland connection broke. Did the Wayland compositor die? Jul 18 22:33:08 m910x kded5[3365]: The Wayland connection broke. Did the Wayland compositor die? Jul 18 22:33:08 m910x plasmashell[3392]: kf.plasma.quick: The compositor does not support the plasma shell protocol Jul 18 22:33:08 m910x org_kde_powerdevil[3429]: The Wayland connection broke. Did the Wayland compositor die? Jul 18 22:33:08 m910x xdg-desktop-portal-kde[3750]: The Wayland connection broke. Did the Wayland compositor die? Jul 18 22:33:08 m910x korgac[3591]: The Wayland connection broke. Did the Wayland compositor die? Jul 18 22:33:08 m910x seapplet[3563]: Error reading events from display: Broken pipe Core Dump (PID 4187/UID 0). Jul 18 22:33:11 m910x systemd-coredump[4191]: [🡕] Process 4183 (xembedsniproxy) of user 10001 dumped core. Process 4180 (gmenudbusmenupr) of user 10001 dumped core. -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 440028] New: Add operator UNLIKE (!=) in the filter options for the star ratings in thumbnail view
https://bugs.kde.org/show_bug.cgi?id=440028 Bug ID: 440028 Summary: Add operator UNLIKE (!=) in the filter options for the star ratings in thumbnail view Product: gwenview Version: unspecified Platform: Other OS: Other Status: REPORTED Severity: wishlist Priority: NOR Component: general Assignee: gwenview-bugs-n...@kde.org Reporter: nachri...@dennisgraeser.de Target Milestone: --- I ask to introduce another operator in the filter options for the star ratings in thumbnail view in addition to the current 3 operators: UNLIKE (!=) 1,2,3,4,5 stars. This will give Gwenview another useful way to filter images. THANKS -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 440029] New: Selecting clip by keyboard does not activate the effect stack
https://bugs.kde.org/show_bug.cgi?id=440029 Bug ID: 440029 Summary: Selecting clip by keyboard does not activate the effect stack Product: kdenlive Version: 21.04.3 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: User Interface Assignee: j...@kdenlive.org Reporter: and...@alweb.dk Target Milestone: --- When selecting a clip under the playhead by pressing "+", I'd expect the clips effect stack to show up in the effect stack widget - like when selecting by mouseclick, but it does not. STEPS TO REPRODUCE 1. Open a project with a clip with an effect. 2. Make the track active and place the playhead over the clip 3. Press "+" to select the clip OBSERVED RESULT The clip is selected, but the effect stack is not displayed in the effect stack view. EXPECTED RESULT The clip should be selected, and it's effect stack be displayed in the effect stack view. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: Current, Arch Linux up to date (available in About System) KDE Plasma Version: 5.22.3 KDE Frameworks Version: 5.84.0 Qt Version: 5.15.2 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 440030] New: Database migration 7.2 -> 7.3 fails
https://bugs.kde.org/show_bug.cgi?id=440030 Bug ID: 440030 Summary: Database migration 7.2 -> 7.3 fails Product: digikam Version: 7.3.0 Platform: openSUSE RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Database-Migration Assignee: digikam-bugs-n...@kde.org Reporter: jens_westeme...@web.de Target Milestone: --- SUMMARY After update from 7.2 to 7.3 digikam fails to start. Error message (in my own words): Database migration from version 12 to 13 fails. Console output: digikam.coredb: Core database: cannot process schema initialization QThreadStorage: Thread 0x7f48800722c0 exited after QThreadStorage 13 destroyed STEPS TO REPRODUCE 1. start digikam 7.3 with a database from 7.2 OBSERVED RESULT digikam does not start 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.
[digikam] [Bug 425352] Cursor is huge and jagged
https://bugs.kde.org/show_bug.cgi?id=425352 --- Comment #9 from caulier.gil...@gmail.com --- Forget Nautilus stuff... Open aconsole, got to the directory where appimage is stored, and start it as a simple executable. Report here the console trace just to be sure. Gilles Caulier -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 440027] Wayland crashes after login
https://bugs.kde.org/show_bug.cgi?id=440027 Vlad Zahorodnii changed: What|Removed |Added Status|REPORTED|NEEDSINFO Resolution|--- |BACKTRACE --- Comment #1 from Vlad Zahorodnii --- Can you please check coredumps for a backtrace? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 440003] Broken animation when i drag maximized window
https://bugs.kde.org/show_bug.cgi?id=440003 --- Comment #1 from Vlad Zahorodnii --- There's no video. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 440030] Database migration 7.2 -> 7.3 fails
https://bugs.kde.org/show_bug.cgi?id=440030 Maik Qualmann changed: What|Removed |Added CC||metzping...@gmail.com --- Comment #1 from Maik Qualmann --- Do you use an internal MySQL or an external MySQL database? Set the debug variable and post the output in the terminal as described here: https://www.digikam.org/contribute/ Maik -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 440001] Yakuake is blue during hide animation
https://bugs.kde.org/show_bug.cgi?id=440001 --- Comment #1 from Vlad Zahorodnii --- Cannot reproduce the issue on Wayland. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 439987] Chromium bad performance on Wayland
https://bugs.kde.org/show_bug.cgi?id=439987 --- Comment #1 from Vlad Zahorodnii --- Can you please check if changing the latency policy (in system settings) to "prefer smoothest animations" fixes the issue? -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 399885] Support indexing NTFS disks
https://bugs.kde.org/show_bug.cgi?id=399885 tagwer...@innerjoin.org changed: What|Removed |Added CC||tagwer...@innerjoin.org -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 439830] Text tool just not working at all....
https://bugs.kde.org/show_bug.cgi?id=439830 --- Comment #11 from Chenille33 --- (In reply to Ahab Greybeard from comment #10) > So, in the test file I attached, can you create a new text item by dragging > out a rectangle with the SVG Text Tool? Yes I can, it's working. > Can you do it in a new vector layer? Yes, it's also working. > If you delete the vector layer(s) in that test file, does using the SVG Text > Tool create a new vector layer for the Placeholder Text? Yes also Str -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 438710] windows that have shadows look wrong when they spawn
https://bugs.kde.org/show_bug.cgi?id=438710 --- Comment #5 from Vlad Zahorodnii --- Are you running Plasma 5.22 or from git master branch? -- You are receiving this mail because: You are watching all bug changes.
[baloo-widgets] [Bug 401019] Tags do not update immediately
https://bugs.kde.org/show_bug.cgi?id=401019 tagwer...@innerjoin.org changed: What|Removed |Added CC||tagwer...@innerjoin.org -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 425352] Cursor is huge and jagged
https://bugs.kde.org/show_bug.cgi?id=425352 --- Comment #10 from david3w...@gmail.com --- Giles I am afraid you have exceeded my limited knowledge of Linux there I am just a simple user of apps, I am afraid. I do delve into things & try a bit, but quickly get lost in the jargon! [You have my permission to roll your eyes to heaven at this point] Am willing to learn Would a console be the terminal app? How do you start something as a simple executable? ( run and the filename?) Presumably you would like the file made executabe with +chmod (as opposed to the Nautilus method) as part of this sequence? (I have done this before in the dim & distant past so could probably find out how to do it again) regards David Ward Get TypeApp for Android On 19 Jul 2021, 9:07 am, at 9:07 am, bugzilla_nore...@kde.org wrote: >https://bugs.kde.org/show_bug.cgi?id=425352 > >--- Comment #9 from caulier.gil...@gmail.com --- >Forget Nautilus stuff... > >Open aconsole, got to the directory where appimage is stored, and start >it as a >simple executable. > >Report here the console trace just to be sure. > >Gilles Caulier > >-- >You are receiving this mail because: >You reported the bug. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 438552] When switching desktops, applications can not be focused anymore and leave a ghost
https://bugs.kde.org/show_bug.cgi?id=438552 --- Comment #8 from Vlad Zahorodnii --- (In reply to alancio from comment #7) > (In reply to Martin van Es from comment #4) > > Disabling transluceny seems to fix the problem. > > Thanks for sharing this, what an annoying bug this is. We know that the translucency effect has caused problems in the past. Do you use the translucency effect with custom settings? -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 440030] Database migration 7.2 -> 7.3 fails
https://bugs.kde.org/show_bug.cgi?id=440030 --- Comment #2 from Maik Qualmann --- If you are using an internal MySQL database read this thread: https://mail.kde.org/pipermail/digikam-users/2021-July/032471.html Maik -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 440003] Broken animation when i drag maximized window
https://bugs.kde.org/show_bug.cgi?id=440003 --- Comment #2 from d3coder --- Created attachment 140176 --> https://bugs.kde.org/attachment.cgi?id=140176&action=edit animation bug -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 416829] krunner crashes in LMDB from baloo runner after typing into the search bar
https://bugs.kde.org/show_bug.cgi?id=416829 tagwer...@innerjoin.org changed: What|Removed |Added Status|REPORTED|NEEDSINFO Resolution|--- |WAITINGFORINFO CC||tagwer...@innerjoin.org --- Comment #2 from tagwer...@innerjoin.org --- (In reply to Adam N. from comment #0) > Frameworks Version: 5.66.0 > ... > I noticed this issue happened on KDE Plasma 5.17.5, so I tried installing > KDE Plasma 5.17.90. The problem occurs on both versions. > > The crash can be reproduced every time. There were fixes done around the 5.68.0 time, see Bug 431664 The patches implied a need to purge and reindex, if you've updated, have reindexed and still have issues, append the info here -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 440003] Broken animation when i drag maximized window
https://bugs.kde.org/show_bug.cgi?id=440003 --- Comment #3 from Vlad Zahorodnii --- AnimationEffect probably miscalculates the transformed window geometry. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 416829] krunner crashes in LMDB from baloo runner after typing into the search bar
https://bugs.kde.org/show_bug.cgi?id=416829 Adam N. changed: What|Removed |Added Resolution|WAITINGFORINFO |FIXED Status|NEEDSINFO |RESOLVED --- Comment #3 from Adam N. --- I have not been able to reproduce the bug since. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 439957] Visual Bugs in some menus
https://bugs.kde.org/show_bug.cgi?id=439957 --- Comment #1 from Vlad Zahorodnii --- This looks like a driver bug. If you disable compositing (Alt+Shift+F12), do you still see the visual artifacts? -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 437196] Touch docker commands sometimes gets triggered twice
https://bugs.kde.org/show_bug.cgi?id=437196 Dmitry Kazakov changed: What|Removed |Added Resolution|--- |FIXED Latest Commit||https://invent.kde.org/grap ||hics/krita/commit/520726394 ||3ae93e7098db0f33b57cfb0c92d ||7bff Status|ASSIGNED|RESOLVED --- Comment #4 from Dmitry Kazakov --- Git commit 5207263943ae93e7098db0f33b57cfb0c92d7bff by Dmitry Kazakov, on behalf of Alvin Wong. Committed on 19/07/2021 at 08:36. Pushed by dkazakov into branch 'master'. win: Work around touch docker buttons triggering twice Hack around the issue by blocking certain mouse events in the touch docker. See also: https://bugreports.qt.io/browse/QTBUG-95058 M +6-0plugins/dockers/touchdocker/CMakeLists.txt M +8-0plugins/dockers/touchdocker/TouchDockerDock.cpp A +93 -0plugins/dockers/touchdocker/TouchDockerQQuickWidget.cpp [License: GPL(v3.0+)] A +40 -0plugins/dockers/touchdocker/TouchDockerQQuickWidget.h [License: GPL(v3.0+)] https://invent.kde.org/graphics/krita/commit/5207263943ae93e7098db0f33b57cfb0c92d7bff -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 440017] Krita closes upon creating/opening new or old files.
https://bugs.kde.org/show_bug.cgi?id=440017 Halla Rempt changed: What|Removed |Added OS|Other |Microsoft Windows CC||ha...@valdyas.org Resolution|--- |WAITINGFORINFO Status|REPORTED|NEEDSINFO --- Comment #3 from Halla Rempt --- Is there also a kritacrash.log file in the local appdata folder? -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 437196] Touch docker commands sometimes gets triggered twice
https://bugs.kde.org/show_bug.cgi?id=437196 Dmitry Kazakov changed: What|Removed |Added Latest Commit|https://invent.kde.org/grap |https://invent.kde.org/grap |hics/krita/commit/520726394 |hics/krita/commit/d76fe492b |3ae93e7098db0f33b57cfb0c92d |f0b883f0d2b9d3bd70ef161af2a |7bff|29c7 --- Comment #5 from Dmitry Kazakov --- Git commit d76fe492bf0b883f0d2b9d3bd70ef161af2a29c7 by Dmitry Kazakov, on behalf of Alvin Wong. Committed on 19/07/2021 at 08:38. Pushed by dkazakov into branch 'krita/5.0'. win: Work around touch docker buttons triggering twice Hack around the issue by blocking certain mouse events in the touch docker. See also: https://bugreports.qt.io/browse/QTBUG-95058 M +6-0plugins/dockers/touchdocker/CMakeLists.txt M +8-0plugins/dockers/touchdocker/TouchDockerDock.cpp A +93 -0plugins/dockers/touchdocker/TouchDockerQQuickWidget.cpp [License: GPL(v3.0+)] A +40 -0plugins/dockers/touchdocker/TouchDockerQQuickWidget.h [License: GPL(v3.0+)] https://invent.kde.org/graphics/krita/commit/d76fe492bf0b883f0d2b9d3bd70ef161af2a29c7 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 439775] User not completely logged out in multi-user environment
https://bugs.kde.org/show_bug.cgi?id=439775 Axel Braun changed: What|Removed |Added Resolution|--- |FIXED Status|REPORTED|RESOLVED --- Comment #3 from Axel Braun --- The parameter that drives the behaviour: /etc/systemd/logind.conf [Login] KillUserProcesses=yes -> so not KDE related Closing, sorry for the noise -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 423010] KWin sometimes does not emit client.windowShown when OpenGL is used as rendering backend
https://bugs.kde.org/show_bug.cgi?id=423010 --- Comment #3 from Vlad Zahorodnii --- That's right. If you switch from OpenGL 3.1 to OpenGL 2.0, compositing will be restarted. As for the issue itself, I recommend avoid using the windowShown signal. KWin may decide not to emit it in some cases even if the window is effectively hidden. The alternative is to check whether a particular window is on the current activity/virtual desktop + minimized state. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 423010] KWin sometimes does not emit client.windowShown when OpenGL is used as rendering backend
https://bugs.kde.org/show_bug.cgi?id=423010 --- Comment #4 from Vlad Zahorodnii --- (In reply to Denis Kurz from comment #1) > I can consistently reproduce this issue on Gentoo, KWin version 5.22.3: New > windows are still not managed tiled by Kröhnkite, but tiling kicks in after > switching to another virtual desktop. KWin will emit the windowShown and the windowHidden in that case. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 377162] Window shading not supported for Wayland windows
https://bugs.kde.org/show_bug.cgi?id=377162 Vlad Zahorodnii changed: What|Removed |Added Keywords||wayland Status|REPORTED|CONFIRMED Ever confirmed|0 |1 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 440027] Wayland crashes after login
https://bugs.kde.org/show_bug.cgi?id=440027 --- Comment #2 from slartibar...@gmail.com --- Created attachment 140177 --> https://bugs.kde.org/attachment.cgi?id=140177&action=edit coredump-1 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 440027] Wayland crashes after login
https://bugs.kde.org/show_bug.cgi?id=440027 --- Comment #3 from slartibar...@gmail.com --- Created attachment 140178 --> https://bugs.kde.org/attachment.cgi?id=140178&action=edit coredump-2 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 440027] Wayland crashes after login
https://bugs.kde.org/show_bug.cgi?id=440027 slartibar...@gmail.com changed: What|Removed |Added Resolution|BACKTRACE |--- Status|NEEDSINFO |REPORTED --- Comment #4 from slartibar...@gmail.com --- i added the first two coredumps, hope this is what you were looking for -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 438552] When switching desktops, applications can not be focused anymore and leave a ghost
https://bugs.kde.org/show_bug.cgi?id=438552 --- Comment #9 from Martin van Es --- I'm not sure if I understand: When I enable Translucency, it has settings and I adjusted the two upper translucency values (Inactive and Moving windows) to be slightly less than max. Is that custom? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 440027] Wayland crashes after login
https://bugs.kde.org/show_bug.cgi?id=440027 --- Comment #5 from Vlad Zahorodnii --- I don't think that I'll be able to open them on my computer. Could you please use gdb to get backtraces in text form? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 438552] When switching desktops, applications can not be focused anymore and leave a ghost
https://bugs.kde.org/show_bug.cgi?id=438552 --- Comment #10 from Vlad Zahorodnii --- (In reply to Martin van Es from comment #9) > I'm not sure if I understand: When I enable Translucency, it has settings > and I adjusted the two upper translucency values (Inactive and Moving > windows) to be slightly less than max. Is that custom? Yes, they are. Anything that's not default can be considered "custom" :) -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 439815] Window randomly become transparent, when close ghost image remains
https://bugs.kde.org/show_bug.cgi?id=439815 --- Comment #4 from Vlad Zahorodnii --- When this bug happens the next time, can you please open the terminal, run the following command `qdbus org.kde.KWin /KWin supportInformation`, and post its output here? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 439183] kwin wayland with latest activity integration doesn't "remember current virtual desktop used" when switching
https://bugs.kde.org/show_bug.cgi?id=439183 --- Comment #3 from Vlad Zahorodnii --- Yeah, there are still some missing activity features that need to be implemented on wayland. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 425352] Cursor is huge and jagged
https://bugs.kde.org/show_bug.cgi?id=425352 --- Comment #11 from caulier.gil...@gmail.com --- >From my computer and a terminal : [gilles@localhost ~]$ pwd /home/gilles [gilles@localhost ~]$ cd Downloads/ [gilles@localhost Downloads]$ ll total 242668 ... -rw-rw-r-- 1 gilles gilles 248173760 Jul 19 04:57 digiKam-7.4.0-20210718T194158-x86-64.appimage ... [gilles@localhost Downloads]$ chmod +x ./digiKam-7.4.0-20210718T194158-x86-64.appimage [gilles@localhost Downloads]$ ./digiKam-7.4.0-20210718T194158-x86-64.appimage -- digiKam Linux AppImage Bundle -- Use 'help' as CLI argument to know all available options for digiKam application. -- Notes: to integrate this bundle to your desktop, use AppImageLauncher. --to enable all debug messages on the console, use 'export QT_LOGGING_RULES="digikam*=true"'. libudev.so.0 libxcb-dri3.so.0 -- Preloading shared libs: :/usr/lib64/libxcb-dri3.so.0 Digikam::DXmlGuiWindow::setupIconTheme: Breeze icons resource file found Digikam::DXmlGuiWindow::setupIconTheme: Breeze-dark icons resource file found unknown: Qt translations path: "/tmp/.mount_digiKa1AvSAd/usr/share/digikam/translations" unknown: Loaded locale: "en_US" from catalog: "qt" unknown: Loaded locale: "en_US" from catalog: "qtbase" unknown: Loaded locale: "en_US" from catalog: "qt_help" Digikam::ApplicationSettings::setApplicationStyle: Switch to widget style: "" Digikam::AlbumWatch::AlbumWatch: AlbumWatch is disabled Digikam::AlbumManager::setDatabase: Database Parameters: Type: "QSQLITE" DB Core Name: "/mnt/data/photos/digikam4.db" DB Thumbs Name:"/mnt/data/photos/thumbnails-digikam.db" DB Face Name: "/mnt/data/photos/recognition.db" DB Similarity Name:"/mnt/data/photos/similarity.db" Connect Options: "" Host Name: "" Host port: -1 Internal Server: false Internal Server Path: "" Internal Server Admin Cmd: "mysqladmin" Internal Server Serv Cmd: "" Internal Server Init Cmd: "" Username: "" Password: "" Digikam::DbEngineConfigSettingsLoader::readConfig: Loading SQL code from config file "/tmp/.mount_digiKa1AvSAd/usr/share/digikam/database/dbconfig.xml" Digikam::DbEngineConfigSettingsLoader::readConfig: Checking XML version ID => expected: 3 found: 3 Digikam::CoreDbSchemaUpdater::update: Core database: running schema update Digikam::CoreDbSchemaUpdater::startUpdates: Core database: have a structure version 13 Digikam::CoreDbSchemaUpdater::makeUpdates: Core database: makeUpdates 13 to 13 Digikam::AlbumRootLocation::AlbumRootLocation: Creating new Location "/photos" uuid "volumeid:?uuid=19b4bf65-70f0-4aba-ae50-8d85e05a05bc" Digikam::CollectionManager::updateLocations: location for "/mnt/data/photos" is available true Digikam::KMemoryInfo::update: KMemoryInfo: Platform identified : "LINUX" Digikam::KMemoryInfo::bytes: KMemoryInfo: TotalRam: 12265807872 ... -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 440027] Wayland crashes after login
https://bugs.kde.org/show_bug.cgi?id=440027 --- Comment #6 from slartibar...@gmail.com --- Created attachment 140179 --> https://bugs.kde.org/attachment.cgi?id=140179&action=edit dump-bt -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 440027] Wayland crashes after login
https://bugs.kde.org/show_bug.cgi?id=440027 --- Comment #7 from slartibar...@gmail.com --- hmm... like that? -- You are receiving this mail because: You are watching all bug changes.
[kstars] [Bug 440031] New: Job in Ekos scheduler marked as invalid
https://bugs.kde.org/show_bug.cgi?id=440031 Bug ID: 440031 Summary: Job in Ekos scheduler marked as invalid Product: kstars Version: 3.5.4 Platform: macOS (DMG) OS: macOS Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: mutla...@ikarustech.com Reporter: ferran.casarram...@gmail.com Target Milestone: --- Created attachment 140180 --> https://bugs.kde.org/attachment.cgi?id=140180&action=edit 2 jobs scheduled by time. SUMMARY In Ekos, when scheduling 2 jobs with start up on start time it labels as invalid the first one as 'unachievable due to the completion time of its previous sibling, marking invalid.', but it isn't. See screen capture. STEPS TO REPRODUCE 1. Open EKOS and start simulators. 2. Add a job in the scheduler with a start time (i.e. 22:00) with a short (dummmy) sequence lasting 1 or 2 minutes 3. Add another job with start time 15 minutes later (i.e. 22:15). OBSERVED RESULT The first one is mark as invalid. EXPECTED RESULT Both jobs must be scheduled SOFTWARE/OS VERSIONS Windows: -- macOS: 10.15.7 Linux/KDE Plasma: -- (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION If the 'invalid' jobs is selected and the priority is modified, then both jobs are mark as scheduled. This is a workaround for 2 jobs, but when you add 3, 4 or 5 jobs, this workaround didn't work. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 440030] Database migration 7.2 -> 7.3 fails
https://bugs.kde.org/show_bug.cgi?id=440030
--- Comment #3 from Jens Westemeier ---
(In reply to Jens Westemeier from comment #0)
> SUMMARY
> After update from 7.2 to 7.3 digikam fails to start.
> Error message (in my own words): Database migration from version 12 to 13
> fails.
> Console output:
> digikam.coredb: Core database: cannot process schema initialization
> QThreadStorage: Thread 0x7f48800722c0 exited after QThreadStorage 13
> destroyed
>
> STEPS TO REPRODUCE
> 1. start digikam 7.3 with a database from 7.2
>
> OBSERVED RESULT
> digikam does not start
>
> EXPECTED RESULT
>
>
> SOFTWARE/OS VERSIONS
> Windows:
> macOS:
> Linux/KDE Plasma:
> (available in About System)
> KDE Plasma Version:
> KDE Frameworks Version:
> Qt Version:
>
> ADDITIONAL INFORMATION
digikam.widgets: Use installed icons
digikam.general: Switch to application font: QFont(Noto
Sans,10,-1,5,50,0,0,0,0,0)
digikam.general: AlbumWatch is disabled
digikam.general: Database Parameters:
Type: "QMYSQL"
DB Core Name: "digikam"
DB Thumbs Name:"digikam"
DB Face Name: "digikam"
DB Similarity Name:"digikam"
Connect Options:
"UNIX_SOCKET=/home/jens/.local/share/digikam/db_misc/mysql.socket"
Host Name: ""
Host port: -1
Internal Server: true
Internal Server Path: "/home/jens"
Internal Server Admin Cmd: "mysqladmin"
Internal Server Serv Cmd: "/usr/sbin/mysqld"
Internal Server Init Cmd: "mysql_install_db"
Username: "root"
Password: ""
digikam.databaseserver: Database Parameters:
Type: "QMYSQL"
DB Core Name: "digikam"
DB Thumbs Name:"digikam"
DB Face Name: "digikam"
DB Similarity Name:"digikam"
Connect Options:
"UNIX_SOCKET=/home/jens/.local/share/digikam/db_misc/mysql.socket"
Host Name: ""
Host port: -1
Internal Server: true
Internal Server Path: "/home/jens"
Internal Server Admin Cmd: "mysqladmin"
Internal Server Serv Cmd: "/usr/sbin/mysqld"
Internal Server Init Cmd: "mysql_install_db"
Username: "root"
Password: ""
digikam.databaseserver: Internal Server data path:
"/home/jens/.mysql.digikam/db_data"
digikam.databaseserver: The mysql configuration was already up-to-date:
"/home/jens/.local/share/digikam/mysql.conf"
digikam.databaseserver: Database server: "/usr/sbin/mysqld"
("--defaults-file=/home/jens/.local/share/digikam/mysql.conf",
"--datadir=/home/jens/.mysql.digikam/db_data",
"--socket=/home/jens/.local/share/digikam/db_misc/mysql.socket")
digikam.databaseserver: Internal database server started
digikam.databaseserver: Running 0 seconds...
digikam.dbengine: Loading SQL code from config file
"/usr/share/digikam/database/dbconfig.xml"
digikam.dbengine: Checking XML version ID => expected: 3 found: 3
digikam.coredb: Core database: running schema update
digikam.coredb: Core database: have a structure version 12
digikam.coredb: Core database: makeUpdates 12 to 13
digikam.dbengine: Failure executing query:
""
Error messages: "QMYSQL: Die Abfrage konnte nicht ausgeführt werden" "Column
count of mysql.proc is wrong. Expected 21, found 20. Created with MariaDB
100229, now running 100510. Please use mariadb-upgrade to fix this error"
"1558" 2
Bound values: ()
digikam.dbengine: Error while executing DBAction [ "UpdateSchemaFromV12ToV13" ]
Statement [ "\nDROP PROCEDURE IF EXISTS
create_index_if_not_exists;\n" ]
digikam.coredb: Core database: schema update to V 13 failed!
digikam.coredb: Core database: cannot process schema initialization
digikam.general: KMemoryInfo: Platform identified : "LINUX"
digikam.general: KMemoryInfo: TotalRam: 16628625408
digikam.general: Allowing a cache size of 400 MB
digikam.databaseserver: Shutting down database server
digikam.databaseserver: Internal database server stopped
QThreadStorage: Thread 0x7f151c77a2c0 exited after QThreadStorage 13 destroyed
--
You are receiving this mail because:
You are watching all bug changes.
[digikam] [Bug 440030] Database migration 7.2 -> 7.3 fails
https://bugs.kde.org/show_bug.cgi?id=440030 --- Comment #4 from Jens Westemeier --- (In reply to Maik Qualmann from comment #2) > If you are using an internal MySQL database read this thread: > > https://mail.kde.org/pipermail/digikam-users/2021-July/032471.html > > Maik mariadb-upgrade --socket=/home/jens/.local/share/digikam/db_misc/ Version check failed. Got the following error when calling the 'mysql' command line client ERROR 2002 (HY000): Can't connect to local MySQL server through socket '/home/jens/.local/share/digikam/db_misc/' (111) FATAL ERROR: Upgrade failed -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 440030] Database migration 7.2 -> 7.3 fails
https://bugs.kde.org/show_bug.cgi?id=440030 --- Comment #5 from Jens Westemeier --- rpm -qa | grep mariadb mariadb-10.5.10-1.1.x86_64 mariadb-client-10.5.10-1.1.x86_64 libmariadb3-3.1.13-2.1.x86_64 mariadb-errormessages-10.5.10-1.1.noarch -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 440030] Database migration 7.2 -> 7.3 fails
https://bugs.kde.org/show_bug.cgi?id=440030 --- Comment #6 from Jens Westemeier --- Started old version digikam 7.2. With that the database server existed. Run mariadb-upgrade --socket=/home/jens/.local/share/digikam/db_misc/mysql.socket After that digikam 7.3 worked. Problem solved -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 440030] Database migration 7.2 -> 7.3 fails
https://bugs.kde.org/show_bug.cgi?id=440030 Jens Westemeier changed: What|Removed |Added Resolution|--- |FIXED Status|REPORTED|RESOLVED -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 439830] Text tool just not working at all....
https://bugs.kde.org/show_bug.cgi?id=439830 --- Comment #12 from Ahab Greybeard --- What is the situation with your initial report regarding creating text in a new image? If you still can't do this, please Save that new file and attach it to the report. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 440030] Database migration 7.2 -> 7.3 fails
https://bugs.kde.org/show_bug.cgi?id=440030 --- Comment #7 from Jens Westemeier --- Thanks! -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 439947] Advanced colour selector shapes (triangle square and circle) disappear on using "Use system monitor profile" with LCMS optimisations [git 9d832b4]
https://bugs.kde.org/show_bug.cgi?id=439947 Raghavendra kamath changed: What|Removed |Added Summary|Advanced colour selector|Advanced colour selector |shapes (triangle square and |shapes (triangle square and |circle) disappear on|circle) disappear on using |document creation [git |"Use system monitor |9d832b4]|profile" with LCMS ||optimisations [git 9d832b4] -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 439630] QTimer not functional in KWin scripts since 5.22
https://bugs.kde.org/show_bug.cgi?id=439630 Vlad Zahorodnii changed: What|Removed |Added Version Fixed In||5.22.4 Resolution|--- |FIXED Latest Commit||https://invent.kde.org/plas ||ma/kwin/commit/d29954ae3359 ||c4ac5d6e59cef8249427568bc00 ||a Status|REPORTED|RESOLVED --- Comment #1 from Vlad Zahorodnii --- Git commit d29954ae3359c4ac5d6e59cef8249427568bc00a by Vlad Zahorodnii. Committed on 19/07/2021 at 09:14. Pushed by vladz into branch 'master'. scripting: Make QTimer constructible If a QObject is exposed to js using QJSEngine::newQMetaObject(), a new instance of it can be made only with constructors exposed by Q_INVOKABLE At the moment, QTimer's constructor is not Q_INVOKABLE, so code such as `const timer = new QTimer()` will not work. FIXED-IN: 5.22.4 M +6-1src/scripting/scripting.cpp M +13 -0src/scripting/scripting.h https://invent.kde.org/plasma/kwin/commit/d29954ae3359c4ac5d6e59cef8249427568bc00a -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 439833] LSP-Client does not work
https://bugs.kde.org/show_bug.cgi?id=439833 --- Comment #5 from Hannes --- I have tried with -201, but the behaviour is the same. Nothing happens upon selecting the plugin and after closing and re-opening the settings, the box is unchecked again. There is no output on the command line regarding this (only kf.sonnet.core complaining about missing dictionaries). What kind of other logs are there? What is the "journal" you mention? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 439630] QTimer not functional in KWin scripts since 5.22
https://bugs.kde.org/show_bug.cgi?id=439630 Vlad Zahorodnii changed: What|Removed |Added Latest Commit|https://invent.kde.org/plas |https://invent.kde.org/plas |ma/kwin/commit/d29954ae3359 |ma/kwin/commit/71a1ff04b55e |c4ac5d6e59cef8249427568bc00 |e62cdc2b37583c1ade6a7297847 |a |c --- Comment #2 from Vlad Zahorodnii --- Git commit 71a1ff04b55ee62cdc2b37583c1ade6a7297847c by Vlad Zahorodnii. Committed on 19/07/2021 at 09:56. Pushed by vladz into branch 'Plasma/5.22'. scripting: Make QTimer constructible If a QObject is exposed to js using QJSEngine::newQMetaObject(), a new instance of it can be made only with constructors exposed by Q_INVOKABLE At the moment, QTimer's constructor is not Q_INVOKABLE, so code such as `const timer = new QTimer()` will not work. FIXED-IN: 5.22.4 (cherry picked from commit d29954ae3359c4ac5d6e59cef8249427568bc00a) M +6-1src/scripting/scripting.cpp M +13 -0src/scripting/scripting.h https://invent.kde.org/plasma/kwin/commit/71a1ff04b55ee62cdc2b37583c1ade6a7297847c -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 439947] Advanced colour selector shapes (triangle square and circle) disappear on using "Use system monitor profile" with LCMS optimisations [git 9d832b4]
https://bugs.kde.org/show_bug.cgi?id=439947 --- Comment #1 from Raghavendra kamath --- A few new important findings in narrowing this bug down. Steps to reproduce: - Check "Allow LCMS optimizations" in the colour management section and then in the display tab check "Use system monitor colour profile" - You will need your display to be using a calibrated colour profile in colord-KDE in system setting Now check the advanced colour selector after restarting Krita -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 425352] Cursor is huge and jagged
https://bugs.kde.org/show_bug.cgi?id=425352 --- Comment #12 from david3w...@gmail.com --- Gille (Sorry for the Gles!) I think I understood what you were after. the '-rw-rw-r--' command didn't seem to work not sure if it was vital Here is the Terminal screen output from what I did david3ward@penguin:~$ pwd /home/david3ward david3ward@penguin:~$ cd Apps/Digikam/ david3ward@penguin:~/Apps/Digikam$ -rw-rw-r-- digiKam-7.4.0-20210718T194158-x86-64.appimage -bash: -rw-rw-r--: command not found david3ward@penguin:~/Apps/Digikam$ david3ward@penguin:~/Apps/Digikam$ chmod +x digiKam-7.4.0-20210718T194158-x86-64.appimage david3ward@penguin:~/Apps/Digikam$ chmod +x ./digiKam-7.4.0-20210718T194158-x86-64.appimage david3ward@penguin:~/Apps/Digikam$ ./digiKam-7.4.0-20210718T194158-x86-64.appimage -- digiKam Linux AppImage Bundle -- Use 'help' as CLI argument to know all available options for digiKam application. -- Notes: to integrate this bundle to your desktop, use AppImageLauncher. -- to enable all debug messages on the console, use 'export QT_LOGGING_RULES="digikam*=true"'. libudev.so.0 libxcb-dri3.so.0 -- Preloading shared libs: :/usr/lib/x86_64-linux-gnu/libxcb-dri3.so.0 digikam: /lib/x86_64-linux-gnu/libm.so.6: version `GLIBC_2.29' not found (required by /tmp/.mount_digiKayTAEeL/usr/lib/libdigikamgui.so.7.4.0) digikam: /lib/x86_64-linux-gnu/libm.so.6: version `GLIBC_2.29' not found (required by /tmp/.mount_digiKayTAEeL/usr/lib/libMagick++-7.Q16HDRI.so.5) digikam: /lib/x86_64-linux-gnu/libm.so.6: version `GLIBC_2.29' not found (required by /tmp/.mount_digiKayTAEeL/usr/lib/libMagickCore-7.Q16HDRI.so.9) digikam: /lib/x86_64-linux-gnu/libm.so.6: version `GLIBC_2.29' not found (required by /tmp/.mount_digiKayTAEeL/usr/lib/libdigikamcore.so.7.4.0) digikam: /lib/x86_64-linux-gnu/libm.so.6: version `GLIBC_2.29' not found (required by /tmp/.mount_digiKayTAEeL/usr/lib/libKF5CoreAddons.so.5) digikam: /lib/x86_64-linux-gnu/libm.so.6: version `GLIBC_2.29' not found (required by /tmp/.mount_digiKayTAEeL/usr/lib/libQt5Widgets.so.5) digikam: /lib/x86_64-linux-gnu/libm.so.6: version `GLIBC_2.29' not found (required by /tmp/.mount_digiKayTAEeL/usr/lib/libQt5Gui.so.5) digikam: /lib/x86_64-linux-gnu/libm.so.6: version `GLIBC_2.29' not found (required by /tmp/.mount_digiKayTAEeL/usr/lib/libQt5Core.so.5) digikam: /lib/x86_64-linux-gnu/libm.so.6: version `GLIBC_2.29' not found (required by /tmp/.mount_digiKayTAEeL/usr/lib/libmarblewidget-qt5.so.28) digikam: /lib/x86_64-linux-gnu/libm.so.6: version `GLIBC_2.29' not found (required by /tmp/.mount_digiKayTAEeL/usr/lib/libQt5WebEngineCore.so.5) digikam: /lib/x86_64-linux-gnu/libm.so.6: version `GLIBC_2.29' not found (required by /tmp/.mount_digiKayTAEeL/usr/lib/libQt5Quick.so.5) digikam: /lib/x86_64-linux-gnu/libm.so.6: version `GLIBC_2.29' not found (required by /tmp/.mount_digiKayTAEeL/usr/lib/libQt5Qml.so.5) digikam: /lib/x86_64-linux-gnu/libm.so.6: version `GLIBC_2.29' not found (required by /tmp/.mount_digiKayTAEeL/usr/lib/libopencv_objdetect.so.4.5) digikam: /lib/x86_64-linux-gnu/libm.so.6: version `GLIBC_2.29' not found (required by /tmp/.mount_digiKayTAEeL/usr/lib/libopencv_calib3d.so.4.5) digikam: /lib/x86_64-linux-gnu/libm.so.6: version `GLIBC_2.29' not found (required by /tmp/.mount_digiKayTAEeL/usr/lib/libopencv_features2d.so.4.5) digikam: /lib/x86_64-linux-gnu/libm.so.6: version `GLIBC_2.29' not found (required by /tmp/.mount_digiKayTAEeL/usr/lib/libopencv_dnn.so.4.5) digikam: /lib/x86_64-linux-gnu/libm.so.6: version `GLIBC_2.29' not found (required by /tmp/.mount_digiKayTAEeL/usr/lib/libopencv_imgproc.so.4.5) digikam: /lib/x86_64-linux-gnu/libm.so.6: version `GLIBC_2.29' not found (required by /tmp/.mount_digiKayTAEeL/usr/lib/libopencv_ml.so.4.5) digikam: /lib/x86_64-linux-gnu/libm.so.6: version `GLIBC_2.29' not found (required by /tmp/.mount_digiKayTAEeL/usr/lib/libopencv_core.so.4.5) digikam: /lib/x86_64-linux-gnu/libm.so.6: version `GLIBC_2.29' not found (required by /tmp/.mount_digiKayTAEeL/usr/lib/libfftw3.so.3) digikam: /lib/x86_64-linux-gnu/libm.so.6: version `GLIBC_2.29' not found (required by /tmp/.mount_digiKayTAEeL/usr/lib/libxml2.so.2) digikam: /lib/x86_64-linux-gnu/libm.so.6: version `GLIBC_2.29' not found (required by /tmp/.mount_digiKayTAEeL/usr/lib/libtiff.so.5) digikam: /lib/x86_64-linux-gnu/libm.so.6: version `GLIBC_2.29' not found (required by /tmp/.mount_digiKayTAEeL/usr/lib/libpng16.so.16) digikam: /lib/x86_64-linux-gnu/libm.so.6: version `GLIBC_2.29' not found (required by /tmp/.mount_digiKayTAEeL/usr/lib/libexiv2.so.27) digikam: /lib/x86_64-linux-gnu/libm.so.6: version `GLIBC_2.29' not found (required by /tmp/.mount_digiKayTAEeL/usr/lib/libavcodec.so.58) digikam: /lib/x86_64-linux-gnu/libm.so.6: version `GLIBC_2.29' not found (required by /tmp/.mount_digiKayTAEeL/usr/lib/libavfilter.so.7) digikam: /lib/x86_64-linux-gnu/libm.so.6: version `GLIBC_2.29' not found (required by /tmp/.mount_digiKayTAEeL/usr/lib/libavutil.so.56) digikam: /lib/x86_64-
[digikam] [Bug 439913] iNaturalist Export "Unknown Error" when click in Identification field
https://bugs.kde.org/show_bug.cgi?id=439913 --- Comment #1 from Maik Qualmann --- Git commit b4ad2a2b63817c975286afba2e370bc8e797976b by Maik Qualmann. Committed on 19/07/2021 at 10:32. Pushed by mqualmann into branch 'master'. fix convert QUrl to path string under Windows M +4-4core/dplugins/generic/webservices/inaturalist/inattalker.cpp https://invent.kde.org/graphics/digikam/commit/b4ad2a2b63817c975286afba2e370bc8e797976b -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 440010] Applications may be launched over-eagerly when hitting backspace
https://bugs.kde.org/show_bug.cgi?id=440010 Paul Worrall changed: What|Removed |Added CC||p.r.worr...@gmail.com Status|REPORTED|CONFIRMED Ever confirmed|0 |1 --- Comment #1 from Paul Worrall --- Can reproduce Operating System: KDE neon 5.22 KDE Plasma Version: 5.22.3 KDE Frameworks Version: 5.84.0 Qt Version: 5.15.3 Kernel Version: 5.8.0-59-generic (64-bit) Graphics Platform: X11 Processors: 2 × AMD A6-6400K APU with Radeon(tm) HD Graphics Memory: 7.7 GiB of RAM Graphics Processor: AMD CEDAR -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 425352] Cursor is huge and jagged
https://bugs.kde.org/show_bug.cgi?id=425352 --- Comment #13 from caulier.gil...@gmail.com --- Which Linux system didi you use exactly ? -- You are receiving this mail because: You are watching all bug changes.
[clazy] [Bug 439337] clazy-qt6-deprecated-api-fixes creates invalid code
https://bugs.kde.org/show_bug.cgi?id=439337 Sergio Martins changed: What|Removed |Added Assignee|unassigned-b...@kde.org |joerg.bornem...@qt.io -- You are receiving this mail because: You are watching all bug changes.
[clazy] [Bug 439338] clazy-qt6-deprecated-api-fixes creates invalid code for QDate::startOfDay
https://bugs.kde.org/show_bug.cgi?id=439338 Sergio Martins changed: What|Removed |Added Assignee|unassigned-b...@kde.org |joerg.bornem...@qt.io -- You are receiving this mail because: You are watching all bug changes.
[clazy] [Bug 439337] clazy-qt6-deprecated-api-fixes creates invalid code
https://bugs.kde.org/show_bug.cgi?id=439337 --- Comment #2 from Sergio Martins --- Joerg , are you still the contact person for the qt6- checks ? -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 425352] Cursor is huge and jagged
https://bugs.kde.org/show_bug.cgi?id=425352 --- Comment #14 from david3w...@gmail.com --- Not sure The one that is installed on Chromebooks ChromeOS v91 Get TypeApp for Android On 19 Jul 2021, 11:53 am, at 11:53 am, bugzilla_nore...@kde.org wrote: >https://bugs.kde.org/show_bug.cgi?id=425352 > >--- Comment #13 from caulier.gil...@gmail.com --- >Which Linux system didi you use exactly ? > >-- >You are receiving this mail because: >You reported the bug. -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 431402] Make it possible to scale down/zoom out images further than the window width/height
https://bugs.kde.org/show_bug.cgi?id=431402 Alberto Salvia Novella changed: What|Removed |Added CC|es204904...@gmail.com | -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 425352] Cursor is huge and jagged
https://bugs.kde.org/show_bug.cgi?id=425352 --- Comment #15 from david3w...@gmail.com --- I think it is a version of Debian running in a container Get TypeApp for Android On 19 Jul 2021, 11:53 am, at 11:53 am, bugzilla_nore...@kde.org wrote: >https://bugs.kde.org/show_bug.cgi?id=425352 > >--- Comment #13 from caulier.gil...@gmail.com --- >Which Linux system didi you use exactly ? > >-- >You are receiving this mail because: >You reported the bug. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 425352] Cursor is huge and jagged
https://bugs.kde.org/show_bug.cgi?id=425352 --- Comment #16 from david3w...@gmail.com --- Seems to be Debian buster david3ward@penguin:~$ sudo apt-get update && sudo apt-get dist-upgrade Get:1 http://ppa.launchpad.net/mdoyen/homebank/ubuntu hirsute InRelease [17.6 kB] Hit:2 https://deb.debian.org/debian buster InRelease Ign:3 http://repo.vivaldi.com/stable/deb stable InRelease Hit:4 https://deb.debian.org/debian-security buster/updates InRelease Hit:5 http://repo.vivaldi.com/stable/deb stable Release Err:1 http://ppa.launchpad.net/mdoyen/homebank/ubuntu hirsute InRelease The following signatures couldn't be verified because the public key is not available: NO_PUBKEY ECA9D5AF2B98B3A0 Ign:6 https://storage.googleapis.com/cros-packages/91 buster InRelease Hit:7 https://storage.googleapis.com/cros-packages/91 buster Release Hit:8 https://packages.bluemail.me/repos/debian ./ InRelease Reading package lists... Done W: GPG error: http://ppa.launchpad.net/mdoyen/homebank/ubuntu hirsute InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY ECA9D5AF2B98B3A0 E: The repository 'http://ppa.launchpad.net/mdoyen/homebank/ubuntu hirsute InRelease' is not signed. N: Updating from such a repository can't be done securely, and is therefore disabled by default. N: See apt-secure(8) manpage for repository creation and user configuration details. david3ward@penguin:~$ Get TypeApp for Android On 19 Jul 2021, 12:01 pm, at 12:01 pm, David Ward wrote: >I think it is a version of Debian running in a container > >Get TypeApp for Android > >On 19 Jul 2021, 11:53 am, at 11:53 am, bugzilla_nore...@kde.org wrote: >>https://bugs.kde.org/show_bug.cgi?id=425352 >> >>--- Comment #13 from caulier.gil...@gmail.com --- >>Which Linux system didi you use exactly ? >> >>-- >>You are receiving this mail because: >>You reported the bug. -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 440032] New: Kate won't go in the foreground in wayland if a file is already open
https://bugs.kde.org/show_bug.cgi?id=440032 Bug ID: 440032 Summary: Kate won't go in the foreground in wayland if a file is already open Product: kate Version: 21.04.3 Platform: Manjaro OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: application Assignee: kwrite-bugs-n...@kde.org Reporter: k...@asdrip.fr Target Milestone: --- SUMMARY With X11 if you open a file in kate, it will start a new instance of kate and show kate in the foreground. If kate is already open, it will open a new tab with the file AND show kate in the foreground. But when booting with Wayland, kate do show up when opening a new instance but not when opening a new tab. STEPS TO REPRODUCE 1. Open Kate 2. Open a file via cli or dolphin OBSERVED RESULT Kate don't go automatically to the foreground EXPECTED RESULT Kate should be in the foreground when opening a new tab SOFTWARE/OS VERSIONS Linux/KDE Plasma: Manajaro 5.12 KDE Plasma Version: Plasma 5.22.3 KDE Frameworks Version: 5.84.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 427906] Appimage fails to launch on Wayland stating xkb
https://bugs.kde.org/show_bug.cgi?id=427906 --- Comment #8 from il...@fastmail.fm --- on current openSUSE Tumbleweed I get the following errors: ./digiKam-7.4.0-20210718T194158-x86-64.appimage -- digiKam Linux AppImage Bundle -- Use 'help' as CLI argument to know all available options for digiKam application. -- Notes: to integrate this bundle to your desktop, use AppImageLauncher. --to enable all debug messages on the console, use 'export QT_LOGGING_RULES="digikam*=true"'. libudev.so.0 libxcb-dri3.so.0 -- Preloading shared libs: :/usr/lib64/libxcb-dri3.so.0 xkbcommon: ERROR: failed to add default include path ././/share/X11/xkb unknown: failed to create xkb context libEGL warning: MESA-LOADER: failed to open iris (search paths ././/lib64/dri) libEGL warning: MESA-LOADER: failed to open swrast (search paths ././/lib64/dri) libEGL warning: MESA-LOADER: failed to open swrast (search paths ././/lib64/dri) unknown: Failed to initialize EGL display 3001 /tmp/.mount_digiKa3pAw0i/AppRun: line 172: 10679 Segmentation fault (core dumped) digikam $@ (wayland still enabled of course). I will test KDE Neon distro once I have some memory/CPU available. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 430199] Transfrom Mask makes the parent layer invisible
https://bugs.kde.org/show_bug.cgi?id=430199 Dmitry Kazakov changed: What|Removed |Added Status|REOPENED|RESOLVED Latest Commit|https://invent.kde.org/grap |https://invent.kde.org/grap |hics/krita/commit/afa95c4dc |hics/krita/commit/6f16cbccd |92d3b4fb8aaa5d0c46849c539a6 |83095e82c8348be428610be3a54 |30c7|12e1 Resolution|--- |FIXED --- Comment #9 from Dmitry Kazakov --- Git commit 6f16cbccd83095e82c8348be428610be3a5412e1 by Dmitry Kazakov. Committed on 19/07/2021 at 11:45. Pushed by dkazakov into branch 'master'. Fix updates when transforming a transform mask with non-affine transform M +10 -1 plugins/tools/tool_transform2/strokes/inplace_transform_stroke_strategy.cpp https://invent.kde.org/graphics/krita/commit/6f16cbccd83095e82c8348be428610be3a5412e1 -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 438977] AppImage doesn't start
https://bugs.kde.org/show_bug.cgi?id=438977 Dawid Wróbel changed: What|Removed |Added Latest Commit||https://invent.kde.org/offi ||ce/kmymoney/commit/82ab3fef ||e2971caddc050b7f336786dad20 ||71cba Version Fixed In||5.1.3 Status|CONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #4 from Dawid Wróbel --- Git commit 82ab3fefe2971caddc050b7f336786dad2071cba by Dawid Wróbel. Committed on 19/07/2021 at 10:38. Pushed by wrobelda into branch 'master'. Make woob plugin failsafe on Python issues - show error messages if Python or Woob fails to load - do some additional code refactoring FIXED-IN: 5.1.3 M +0-1kmymoney/plugins/woob/dialogs/mapaccountwizard.cpp M +47 -21 kmymoney/plugins/woob/interface/woobinterface.cpp M +8-1kmymoney/plugins/woob/interface/woobinterface.h M +56 -27 kmymoney/plugins/woob/woob.cpp M +1-0kmymoney/plugins/woob/woob.h https://invent.kde.org/office/kmymoney/commit/82ab3fefe2971caddc050b7f336786dad2071cba -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 440033] New: Kwin crash
https://bugs.kde.org/show_bug.cgi?id=440033 Bug ID: 440033 Summary: Kwin crash Product: kwin Version: 5.14.5 Platform: Debian stable OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kwin-bugs-n...@kde.org Reporter: gabriele.trivi...@studenti.polito.it Target Milestone: --- Application: kwin_x11 (5.14.5) Qt Version: 5.11.3 Frameworks Version: 5.54.0 Operating System: Linux 4.19.0-17-amd64 x86_64 Distribution: Debian GNU/Linux 10 (buster) -- Information about the crash: - What I was doing when the application crashed: I was just browsing a pdf, with browser, VScode, terminal window (with no running processes) in background - Unusual behavior I noticed: The screen froze for a second and then got back to normal; with a popup notification saying Kwin had crashed. This has happened to me many times in a more destructive way, that is a complete freeze of the screen, but in those cases i had not been able to recover a stack trace of the errors so i am signaling this hoping it is the same kind of problem. When the full freeze happens, i am only able to move the mouse, keyboard input does not work, however if there was a video playing on Youtube audio keeps working and so does network so it appears to be a desktop only problem. I have to say that happens in any kind of situation and with GNOME too, i run debian 10 with proprietary nvidia drivers 470 hope you will be able to help me The crash can be reproduced sometimes. -- Backtrace: Application: KWin (kwin_x11), signal: Aborted Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7fbf1314e940 (LWP 2340))] Thread 8 (Thread 0x7fbe63064700 (LWP 6905)): #0 futex_wait_cancelable (private=0, expected=0, futex_word=0x7fbf0c02f950) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 __pthread_cond_wait_common (abstime=0x0, mutex=0x7fbf0c02f900, cond=0x7fbf0c02f928) at pthread_cond_wait.c:502 #2 __pthread_cond_wait (cond=0x7fbf0c02f928, mutex=0x7fbf0c02f900) at pthread_cond_wait.c:655 #3 0x7fbf1b11b21b in QWaitCondition::wait(QMutex*, unsigned long) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7fbf19e64009 in ?? () from /lib/x86_64-linux-gnu/libQt5Quick.so.5 #5 0x7fbf19e6426a in ?? () from /lib/x86_64-linux-gnu/libQt5Quick.so.5 #6 0x7fbf1b11aa67 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7fbf1a303fa3 in start_thread (arg=) at pthread_create.c:486 #8 0x7fbf1c7144cf in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 7 (Thread 0x7fbf0233e700 (LWP 6904)): #0 0x7fbf1c709916 in __GI_ppoll (fds=0x7fbef4000d68, nfds=1, timeout=, sigmask=0x0) at ../sysdeps/unix/sysv/linux/ppoll.c:39 #1 0x7fbf1b30f721 in qt_safe_poll(pollfd*, unsigned long, timespec const*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #2 0x7fbf1b310b99 in QEventDispatcherUNIX::processEvents(QFlags) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #3 0x7fbf1b2c115b in QEventLoop::exec(QFlags) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7fbf1b110e76 in QThread::exec() () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7fbf19b2ec65 in ?? () from /lib/x86_64-linux-gnu/libQt5Qml.so.5 #6 0x7fbf1b11aa67 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7fbf1a303fa3 in start_thread (arg=) at pthread_create.c:486 #8 0x7fbf1c7144cf in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 6 (Thread 0x7fbf10c28700 (LWP 3937)): #0 0x7fbf1c70c037 in __GI___select (nfds=45, readfds=0x7fbf10c27c20, writefds=0x0, exceptfds=0x0, timeout=0x7fbf10c27c10) at ../sysdeps/unix/sysv/linux/select.c:41 #1 0x7fbefad2ea21 in ?? () from /lib/x86_64-linux-gnu/libnvidia-glcore.so.470.42.01 #2 0x7fbefad2c54d in ?? () from /lib/x86_64-linux-gnu/libnvidia-glcore.so.470.42.01 #3 0x7fbf1a303fa3 in start_thread (arg=) at pthread_create.c:486 #4 0x7fbf1c7144cf in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 5 (Thread 0x7fbef9f50700 (LWP 3936)): #0 futex_wait_cancelable (private=0, expected=0, futex_word=0x55d0b349eca4) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 __pthread_cond_wait_common (abstime=0x0, mutex=0x55d0b349ec50, cond=0x55d0b349ec78) at pthread_cond_wait.c:502 #2 __pthread_cond_wait (cond=0x55d0b349ec78, mutex=0x55d0b349ec50) at pthread_cond_wait.c:655 #3 0x7fbf1b11b21b in QWaitCondition::wait(QMutex*, unsigned long) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7fbf19e64009 in ?? () from /lib/x86_64-linux-gnu/libQt5Quick.so.5 #5 0x7fbf19e6426a in ?? () from /lib/x86_64-linux-gnu/libQt5Quick.so.5 #6 0x7fbf1b11aa67 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7fbf1a303fa3 in start_thread (arg=) at pthread_create.c:486 #8 0x7fbf1c7144cf in clone () at ..
[kdenlive] [Bug 439849] Crash upon inserting a multi-audio clip while some tracks are locked.
https://bugs.kde.org/show_bug.cgi?id=439849 Jean-Baptiste Mardelle changed: What|Removed |Added Latest Commit||https://invent.kde.org/mult ||imedia/kdenlive/commit/6c37 ||857ead305a43f330517983c3c04 ||0dd67e696 Status|CONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #2 from Jean-Baptiste Mardelle --- Git commit 6c37857ead305a43f330517983c3c040dd67e696 by Jean-Baptiste Mardelle. Committed on 19/07/2021 at 12:28. Pushed by mardelle into branch 'release/21.0'. Fix crash dragging multiple audio streams clip in timeline with locked tracks M +28 -9src/timeline2/model/timelinemodel.cpp https://invent.kde.org/multimedia/kdenlive/commit/6c37857ead305a43f330517983c3c040dd67e696 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 440034] New: Desktop Icons change from Right Aligned to Left Aligned and back to Right Aligned.
https://bugs.kde.org/show_bug.cgi?id=440034 Bug ID: 440034 Summary: Desktop Icons change from Right Aligned to Left Aligned and back to Right Aligned. Product: plasmashell Version: 5.22.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Desktop Containment Assignee: notm...@gmail.com Reporter: ianc_...@fastmail.uk CC: plasma-b...@kde.org Target Milestone: 1.0 SUMMARY STEPS TO REPRODUCE 1. Either on : Initial Boot/Reboot/Adding Desktop Icons/Moving Desktop Icons Icons are setup as Right Aligned & In Columns. Setting Desktop Icons as "LOCKED" stops SOME of the movement from right to left and back. 2. Easiest way to reproduce is to add a software package and then manually try to position it's Icon on Desktop. 3. Have attached Desktop Recording so you can see what I mean. Movement of Icons is at TIME CODE 2:35 prior to that I display system Info. OBSERVED RESULT Icons which are RIGHT ALIGNED move or appear on LEFT of Desktop, then when you select to move them they jump to RIGHT of Desktop. EXPECTED RESULT Expect Icons to stay in place, UNTIL MANUALLY moved. Especially as the "LOCKED" attribute is set. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Kubuntu 21.04 KDE Plasma Version: 5.22.3 KDE Frameworks Version: 5.84.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION CPU: AMD FX-6100 Six-Core Graphics: AMD Radeon HD5850 (Cypress) Memory:16 Gb -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 440035] New: ASAN heap-buffer-overflow detected by writing of raw profile in PNG export.
https://bugs.kde.org/show_bug.cgi?id=440035 Bug ID: 440035 Summary: ASAN heap-buffer-overflow detected by writing of raw profile in PNG export. Product: krita Version: git master (please specify the git hash!) Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: File formats Assignee: krita-bugs-n...@kde.org Reporter: griffinval...@gmail.com Target Milestone: --- SUMMARY Running Krita with asan, go this when trying to save a PNG. ==1726755==ERROR: AddressSanitizer: heap-buffer-overflow on address 0x6130001219f1 at pc 0x7f5eaf127a6d bp 0x7f5e75cf4dd0 sp 0x7f5e75cf4578 READ of size 370 at 0x6130001219f1 thread T184 (Thread (pooled)) #0 0x7f5eaf127a6c (/usr/lib/x86_64-linux-gnu/libasan.so.5+0x67a6c) #1 0x7f5ea9f184ab in writeRawProfile /home/wolthera/krita/src/libs/ui/kis_png_converter.cpp:170 #2 0x7f5ea9f3076e in KisPNGConverter::buildFile(QIODevice*, QRect const&, double, double, KisSharedPtr, QTypedArrayData >::iterator, QTypedArrayData >::iterator, KisPNGOptions, KisMetaData::Store*) /home/wolthera/krita/src/libs/ui/kis_png_converter.cpp:1251 #3 0x7f5e7b8bfb1b in KisPNGExport::convert(KisDocument*, QIODevice*, KisPinnedSharedPtr) /home/wolthera/krita/src/plugins/impex/png/kis_png_export.cc:82 #4 0x7f5e6406 in KisImportExportManager::doExportImpl(QString const&, QSharedPointer, KisPinnedSharedPtr) /home/wolthera/krita/src/libs/ui/KisImportExportManager.cpp:731 #5 0x7f5e7484 in KisImportExportManager::doExport(QString const&, QSharedPointer, KisPinnedSharedPtr, bool) /home/wolthera/krita/src/libs/ui/KisImportExportManager.cpp:675 #6 0x7f5eaaab675d in KisImportExportErrorCode std::__invoke_impl, KisPinnedSharedPtr, bool), KisImportExportManager*&, QString&, QSharedPointer&, KisPinnedSharedPtr&, bool&>(std::__invoke_memfun_deref, KisImportExportErrorCode (KisImportExportManager::*&)(QString const&, QSharedPointer, KisPinnedSharedPtr, bool), KisImportExportManager*&, QString&, QSharedPointer&, KisPinnedSharedPtr&, bool&) /usr/include/c++/9/bits/invoke.h:73 #7 0x7f5eaaab675d in std::__invoke_result, KisPinnedSharedPtr, bool), KisImportExportManager*&, QString&, QSharedPointer&, KisPinnedSharedPtr&, bool&>::type std::__invoke, KisPinnedSharedPtr, bool), KisImportExportManager*&, QString&, QSharedPointer&, KisPinnedSharedPtr&, bool&>(KisImportExportErrorCode (KisImportExportManager::*&)(QString const&, QSharedPointer, KisPinnedSharedPtr, bool), KisImportExportManager*&, QString&, QSharedPointer&, KisPinnedSharedPtr&, bool&) /usr/include/c++/9/bits/invoke.h:96 #8 0x7f5eaaab675d in KisImportExportErrorCode std::_Bind, KisPinnedSharedPtr, bool))(QString const&, QSharedPointer, KisPinnedSharedPtr, bool)>::__call(std::tuple<>&&, std::_Index_tuple<0ul, 1ul, 2ul, 3ul, 4ul>) /usr/include/c++/9/functional:402 #9 0x7f5eaaab675d in KisImportExportErrorCode std::_Bind, KisPinnedSharedPtr, bool))(QString const&, QSharedPointer, KisPinnedSharedPtr, bool)>::operator()<, KisImportExportErrorCode>() /usr/include/c++/9/functional:484 #10 0x7f5eaaab675d in QtConcurrent::StoredFunctorCall0, KisPinnedSharedPtr, bool))(QString const&, QSharedPointer, KisPinnedSharedPtr, bool)> >::runFunctor() /usr/include/x86_64-linux-gnu/qt5/QtConcurrent/qtconcurrentstoredfunctioncall.h:60 #11 0x7f5eaaab675d in QtConcurrent::RunFunctionTask::run() /usr/include/x86_64-linux-gnu/qt5/QtConcurrent/qtconcurrentrunbase.h:108 #12 0x7f5ea35e7151 (/usr/lib/x86_64-linux-gnu/libQt5Core.so.5+0xd1151) #13 0x7f5ea35e3d4b (/usr/lib/x86_64-linux-gnu/libQt5Core.so.5+0xcdd4b) #14 0x7f5ea30fb608 in start_thread /build/glibc-eX1tMB/glibc-2.31/nptl/pthread_create.c:477 #15 0x7f5ea3248292 in __clone (/lib/x86_64-linux-gnu/libc.so.6+0x122292) 0x6130001219f1 is located 0 bytes to the right of 369-byte region [0x613000121880,0x6130001219f1) allocated by thread T184 (Thread (pooled)) here: #0 0x7f5eaf1cdbc8 in malloc (/usr/lib/x86_64-linux-gnu/libasan.so.5+0x10dbc8) #1 0x7f5ea2da22e1 in png_malloc (/usr/lib/x86_64-linux-gnu/libpng16.so.16+0xc2e1) Thread T184 (Thread (pooled)) created by T0 here: #0 0x7f5eaf0fa805 in pthread_create (/usr/lib/x86_64-linux-gnu/libasan.so.5+0x3a805) #1 0x7f5ea35e3804 in QThread::start(QThread::Priority) (/usr/lib/x86_64-linux-gnu/libQt5Core.so.5+0xcd804) SUMMARY: AddressSanitizer: heap-buffer-overflow (/usr/lib/x86_64-linux-gnu/libasan.so.5+0x67a6c) Shadow bytes around the buggy address: 0x0c268001c2e0: fd fd fd fd fd fd fd fd fd fd fd fd fd fd fd fd 0x0c268001c2f0: fd fd fd fd fd fd fd fd fd fd fd fd fd fd fd fd 0x0c268001c300: fd fd fd fd fd fd fd fa fa fa fa fa fa fa fa fa 0x0c268001c310: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0c268001c320: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 =>0x0c268001c330: 00 00 00 00 00 00 00 00 00 00 00 00 00
[kwin] [Bug 440036] New: Allow to move a window to a single activity from the title bar menu
https://bugs.kde.org/show_bug.cgi?id=440036 Bug ID: 440036 Summary: Allow to move a window to a single activity from the title bar menu Product: kwin Version: unspecified Platform: unspecified OS: Unspecified Status: REPORTED Severity: normal Priority: NOR Component: activities Assignee: kwin-bugs-n...@kde.org Reporter: a...@laxu.de Target Milestone: --- SUMMARY The activities menu in the titlebar allows to add and remove activities in which the window is visible. A nice feature would be to allow shift-click or ctrl-click on an activity to disable all other activities and only show the window in this activity. Another or an additional option would be to keep the menu open. STEPS TO REPRODUCE 1. Open a window 2. Add the window to 3 of 5 activities 3. Assign it to the 4th activity and unassign it from the others OBSERVED RESULT You need to open the menu for each activity you want to select or deselect, which are 2 clicks per activity and moving the cursor to the right target, which can be tedious when you want to change many activities or move many windows. EXPECTED RESULT - Add a modifier, which allows to deselect all other activities and assign the window to the clicked activity. - If feasible, don't close the menu after selecting/deselecting an activity (without modifier key), so one can assign/unassign more than one activity without reopening the menu. -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 438977] AppImage doesn't start
https://bugs.kde.org/show_bug.cgi?id=438977 --- Comment #5 from Dawid Wróbel --- All, Please test this build once it completes: https://binary-factory.kde.org/job/KMyMoney_Stable_Appimage_Build/913/ -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 438977] AppImage doesn't start
https://bugs.kde.org/show_bug.cgi?id=438977 --- Comment #6 from Dawid Wróbel --- Actually, my bad, this is not a correct build. Let me get back to you. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 440037] New: Dolphin doesn't adapt to system theme in Mac
https://bugs.kde.org/show_bug.cgi?id=440037 Bug ID: 440037 Summary: Dolphin doesn't adapt to system theme in Mac Product: dolphin Version: 20.12.3 Platform: macOS (DMG) OS: macOS Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: subins2...@gmail.com CC: kfm-de...@kde.org Target Milestone: --- SUMMARY STEPS TO REPRODUCE 1. Download Dolphin DMG from https://binary-factory.kde.org/job/Dolphin_Release_macos/ 2. Set system theme to Dark in Mac system settings 3. Run Dolphin OBSERVED RESULT Folder & file names can't be seen EXPECTED RESULT Folder, file names should be readable SOFTWARE/OS VERSIONS Windows: macOS: Big Sur Version 11.4 (Apple M1) Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION Screenshot: https://i.imgur.com/V9LcM76.jpg -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 440037] Dolphin doesn't adapt to system theme in Mac
https://bugs.kde.org/show_bug.cgi?id=440037 --- Comment #1 from subins2...@gmail.com --- Created attachment 140185 --> https://bugs.kde.org/attachment.cgi?id=140185&action=edit Screenshot. Folder name text is white, so cannot be seen -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 439906] Provide a way to apply old wallpapers
https://bugs.kde.org/show_bug.cgi?id=439906 Jan Paul Batrina changed: What|Removed |Added CC||jpmbatrin...@gmail.com --- Comment #4 from Jan Paul Batrina --- Created attachment 140186 --> https://bugs.kde.org/attachment.cgi?id=140186&action=edit Previous wallpapers available (KDE Neon) Here in my system (KDE Neon Unstable), the previous default wallpapers are available, and they are provided by the "plasma-workspace-wallpapers" package, so you might need to install the equivalent package in your distro. > The old wallpaper of 5.21 doesn't exist in the store. I cannot find it using > "Get New Wallpapers" FWIW, I also tried searching for it via KDE GNHS and store.kde.org, I could not find it either due to the sheer amount of wallpapers uploaded. Maybe there should be a separate category/special search tags for the previous Plasma default wallpapers? But that is another bug report altogether Nevertheless, the Plasma 5.21 Wallpaper "Milky Way" was uploaded by the original author in https://github.com/ruvkr/milkyway, and multiple resolutions are available in https://github.com/KDE/breeze/tree/Plasma/5.21/wallpapers/Next/contents/images > the root cause is that the user choose the default wallpaper as most > preferable background but got tricked after upgrading. If I remember correctly, the default wallpaper (or any other wallpaper set) that is selected MANUALLY will not be changed after the next update. It might have been that you did not explicitly select the previous wallpaper so it was changed in the next update. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 421151] target_precompile_headers support
https://bugs.kde.org/show_bug.cgi?id=421151 andro...@gmail.com changed: What|Removed |Added Resolution|--- |FIXED Status|REPORTED|RESOLVED --- Comment #1 from andro...@gmail.com --- it's resolved, tested on 5.6.2, works well. -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 438977] AppImage doesn't start
https://bugs.kde.org/show_bug.cgi?id=438977 Dawid Wróbel changed: What|Removed |Added Latest Commit|https://invent.kde.org/offi |https://invent.kde.org/offi |ce/kmymoney/commit/82ab3fef |ce/kmymoney/commit/2f9af3dc |e2971caddc050b7f336786dad20 |a81fe24b70e71e1ed11d7bff3b2 |71cba |d3e99 --- Comment #7 from Dawid Wróbel --- Git commit 2f9af3dca81fe24b70e71e1ed11d7bff3b2d3e99 by Dawid Wróbel. Committed on 19/07/2021 at 13:02. Pushed by wrobelda into branch '5.1'. Make woob plugin failsafe on Python issues - show error messages if Python or Woob fails to load - do some additional code refactoring FIXED-IN: 5.1.3 M +0-1kmymoney/plugins/woob/dialogs/mapaccountwizard.cpp M +49 -26 kmymoney/plugins/woob/interface/woobinterface.cpp M +8-1kmymoney/plugins/woob/interface/woobinterface.h M +57 -28 kmymoney/plugins/woob/woob.cpp M +2-1kmymoney/plugins/woob/woob.h https://invent.kde.org/office/kmymoney/commit/2f9af3dca81fe24b70e71e1ed11d7bff3b2d3e99 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 439987] Chromium bad performance on Wayland
https://bugs.kde.org/show_bug.cgi?id=439987 --- Comment #2 from Ondřej Niesner --- Created attachment 140187 --> https://bugs.kde.org/attachment.cgi?id=140187&action=edit Chromium SIGBUS error -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 439987] Chromium bad performance on Wayland
https://bugs.kde.org/show_bug.cgi?id=439987 --- Comment #3 from Ondřej Niesner --- (In reply to Vlad Zahorodnii from comment #1) > Can you please check if changing the latency policy (in system settings) to > "prefer smoothest animations" fixes the issue? Nothing changed. Also I got some SIGBUS errors in Chromium. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 439780] kio does not compile with libc++ due to the use of the (obsolete and removed) std::mem_fun
https://bugs.kde.org/show_bug.cgi?id=439780 --- Comment #6 from Manuel Nickschas --- (In reply to Ahmad Samir from comment #5) > It seems I need to add -stdlib=libc++ to the compiler flags for clang to use > libc++, I'll test that next :) Yes, you either need to configure Clang to use libc++ by default, or you need to explicitly specify that compiler flag. Note that mixing libc++ and libstdc++ in your system C++ libraries may cause problems (due to ABI incompatibilities), so if you want to have a CI system set up for testing the Clang/libc++ combination, it probably should be based on a system fully built with libc++. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 439780] kio does not compile with libc++ due to the use of the (obsolete and removed) std::mem_fun
https://bugs.kde.org/show_bug.cgi?id=439780 --- Comment #7 from Ahmad Samir --- Yeah, I found that out myself, the build failed with very weird errors indeed :) I'd have to build the whole stack, which isn't simple. Good thing the fix is obvious enough it didn't require that (or we could have asked our FreeBSD devs to test, since they use clang/libc++ by default IIUC). -- You are receiving this mail because: You are watching all bug changes.
