[krita] [Bug 424559] New: Krita in kubuntu crash when it be closed
https://bugs.kde.org/show_bug.cgi?id=424559 Bug ID: 424559 Summary: Krita in kubuntu crash when it be closed Product: krita Version: 4.2.9 Platform: Kubuntu Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: General Assignee: krita-bugs-n...@kde.org Reporter: yz...@qq.com Target Milestone: --- SUMMARY Krita in kubuntu crash when it be closed STEPS TO REPRODUCE 1. Kubuntu (Ubuntu 20.04 LTS x86_64), Kernel: 5.4.0-42-generic,DE: Plasma 2. 4.2.9 3. Once I close the software krita, the system will report a program crash of it. OBSERVED RESULT Happens every time. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 424557] Metadata tags lost/changed
https://bugs.kde.org/show_bug.cgi?id=424557 --- Comment #3 from Jo --- Hi Caulier and Maik, thanks for getting back to me so quickly! Sorry for my newb questions - How do we find out what database we use? I suspect we are all using something different? I am using Windows 10 - we have other team members on Macs and possibly other versions of Windows - there are 10+ of us using digiKam to tag images and most of us work remotely (as does the world, at the moment!). I will run the debugview tool and report back, and also get everyone to install v 7.0.0. Thanks! -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 424541] Cannot save on Android app
https://bugs.kde.org/show_bug.cgi?id=424541 Sharaf changed: What|Removed |Added CC||sharafzaz...@gmail.com --- Comment #1 from Sharaf --- Hello! Thanks for the detailed report! Unfortunately, there is no straight way to reproduce this :( So, could you please do these to give us more insight into this bug: 1) Click on Menu (Top Left) > Settings > Dockers > Check "Log Viewer". 2) Log Viewer docker should be created and then you can enable "File loading and saving" and then perform the buggy action. 3) Then you can try to save the log from Log Viewer by clicking save button in it. If it doesn't work, perhaps you can scroll and see some additional relevant info about the error, which you can screenshot and attach? -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 424558] New: Autostart fires to early
https://bugs.kde.org/show_bug.cgi?id=424558 Bug ID: 424558 Summary: Autostart fires to early Product: systemsettings Version: unspecified Platform: unspecified OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: kcm_autostart Assignee: mon...@kde.org Reporter: bna...@web.de CC: plasma-b...@kde.org Target Milestone: --- When insert a script into autostart (e.g. to stop akonadi ;-) it is started before akonadi runs. So the stop order dit not success. When insert a 'sleep 5' into the script it will success. So the idea is, to delay the start of the check if there are autostart scripts that has to run a few seconds. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 424557] Metadata tags lost/changed
https://bugs.kde.org/show_bug.cgi?id=424557 Maik Qualmann changed: What|Removed |Added CC||metzping...@gmail.com --- Comment #2 from Maik Qualmann --- No similar problem is currently known. Do you lose tags in the metadata of the images or in digiKam's tag list? Are you using a SQLite or MySQL database? Does every user use the same database? In any case, use the current digiKam-7.0.0 with over 750 fixed bugs compared to digiKam-6.4.0. https://files.kde.org/digikam/ Maik -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 424557] Metadata tags lost/changed
https://bugs.kde.org/show_bug.cgi?id=424557 --- Comment #1 from caulier.gil...@gmail.com --- Which windows version is used to host digiKam ? Any virus protection is active on computer ? Which kind of database do you use on each computer ? What dou you seen in digiKam log using DebugView tool as explained here : https://www.digikam.org/contribute/ -- You are receiving this mail because: You are watching all bug changes.
[Artikulate] [Bug 423899] Segmentation fault on fresh build of artikulate
https://bugs.kde.org/show_bug.cgi?id=423899 --- Comment #6 from Avinash Sonawane --- PS - FWIW, I built gcompris and parley successfully using above exact workflow without any Qt plugin path issue. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 407236] macOS : digiKam 6.1.0 application language switch issue
https://bugs.kde.org/show_bug.cgi?id=407236 --- Comment #4 from caulier.gil...@gmail.com --- It stil reproducible with 7.0.0 official MacOS bundle ? https://download.kde.org/stable/digikam/7.0.0/ Gilles Caulier -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 422138] Select other Languages is out
https://bugs.kde.org/show_bug.cgi?id=422138 --- Comment #2 from caulier.gil...@gmail.com --- It stil reproducible with 7.0.0 official MacOS bundle ? https://download.kde.org/stable/digikam/7.0.0/ Gilles Caulier -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 422138] Select other Languages is out
https://bugs.kde.org/show_bug.cgi?id=422138 caulier.gil...@gmail.com changed: What|Removed |Added Component|general |Bundle-MacOS CC||caulier.gil...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 424553] Authenticating to flickr does not work
https://bugs.kde.org/show_bug.cgi?id=424553 Maik Qualmann changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |FIXED Version Fixed In||7.1.0 CC||metzping...@gmail.com --- Comment #2 from Maik Qualmann --- Yes, the return callback address that is no longer valid is fixed in digiKam-7.0.0 with this commit: https://invent.kde.org/graphics/digikam/-/commit/16b1ad17d632ef5638979b43cd657f911e9e71cf Maik -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 424548] panel changing to dock when you increase zoom on hover / space between panel and expanded applet
https://bugs.kde.org/show_bug.cgi?id=424548 --- Comment #3 from Michail Vourlakos --- The popup positioning is plasma frameworks responsibility. Its placement follows the following rules: 1. Its vertical positioning is relevant to the item triggered the popup 2. Its horizontal positioning is restricted to the window boundaries from which it was triggered So this is not possible, if you want something else you should contact and persuaded plasma devs. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 424557] Metadata tags lost/changed
https://bugs.kde.org/show_bug.cgi?id=424557 caulier.gil...@gmail.com changed: What|Removed |Added OS|Other |Microsoft Windows -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 424557] Metadata tags lost/changed
https://bugs.kde.org/show_bug.cgi?id=424557 caulier.gil...@gmail.com changed: What|Removed |Added CC||caulier.gil...@gmail.com Component|general |Tags-Engine -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 424557] New: Metadata tags lost/changed
https://bugs.kde.org/show_bug.cgi?id=424557 Bug ID: 424557 Summary: Metadata tags lost/changed Product: digikam Version: 6.4.0 Platform: Microsoft Windows OS: Other Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: digikam-bugs-n...@kde.org Reporter: jo.is...@treetec.net.au Target Milestone: --- SUMMARY Hi, my team uses digiKam to tag images of animals on remote wildlife cameras. We have been using it successfully with few issues for a number of years. However, in the past month or so, we have had multiple instances of team members losing metadata tags completely, losing some but not others, and also having tags randomly changed to other tags that are incorrect (we use a supplied tag list). I don't really know where to start as it is affecting multiple users on different platforms (Mac, Windows) and even different versions of digiKam. I don't know if any of these errors are reproducible - they seem rather random except they are impacting multiple team members differently. Thanks for any help! -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 424556] New: The Ok/Cancel buttons overlaps Hotspot password input field
https://bugs.kde.org/show_bug.cgi?id=424556 Bug ID: 424556 Summary: The Ok/Cancel buttons overlaps Hotspot password input field Product: plasma-nm Version: 5.19.3 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: editor Assignee: jgrul...@redhat.com Reporter: gri...@protonmail.ch Target Milestone: --- Created attachment 130327 --> https://bugs.kde.org/attachment.cgi?id=130327=edit Button overlap SUMMARY The Ok/Cancel buttons overlaps Hotspot Password field (screenshot attached). STEPS TO REPRODUCE 1. Disconnect Wifi (if connected). 2. Open Network configuration window 3. Select any saved wifi. Then click configuration button (bottom left) to open configuration window. OBSERVED RESULT The Ok/Cancel buttons overlaps Hotspot password input field EXPECTED RESULT The Ok/Cancel buttons should not overlaps Hotspot password input field. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Arch Linux (available in About System) KDE Plasma Version: 5.19.3 KDE Frameworks Version: 5.72.0 Qt Version: 5.15.0 ADDITIONAL INFORMATION Please find the attached screenshot for reference. P.S I would like to work on this bug, if possible? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 423400] Disable nightlight when taking screenshot
https://bugs.kde.org/show_bug.cgi?id=423400 Bug Janitor Service changed: What|Removed |Added Resolution|WAITINGFORINFO |WORKSFORME Status|NEEDSINFO |RESOLVED --- Comment #3 from Bug Janitor Service --- This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 423395] Black Screen
https://bugs.kde.org/show_bug.cgi?id=423395 Bug Janitor Service changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |WORKSFORME --- Comment #3 from Bug Janitor Service --- This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 424534] Bad UI placement upon startup with HiDPI screen
https://bugs.kde.org/show_bug.cgi?id=424534 Bug Janitor Service changed: What|Removed |Added Status|NEEDSINFO |REPORTED Resolution|WAITINGFORINFO |--- --- Comment #5 from Bug Janitor Service --- Thanks for your comment! Automatically switching the status of this bug to REPORTED so that the KDE team knows that the bug is ready to get confirmed. In the future you may also do this yourself when providing needed information. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 423342] No way to dismiss package information panel (on the right side of Discover Software Center)
https://bugs.kde.org/show_bug.cgi?id=423342 --- Comment #7 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.
[Akonadi] [Bug 414178] Deleting all contacts deletes entire /home/user/
https://bugs.kde.org/show_bug.cgi?id=414178 Bug Janitor Service changed: What|Removed |Added Resolution|WAITINGFORINFO |WORKSFORME Status|NEEDSINFO |RESOLVED --- Comment #7 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.
[parley] [Bug 423903] Using a deprecated location for the knsrc file "parley.knsrc"
https://bugs.kde.org/show_bug.cgi?id=423903 Alexander Lohnau changed: What|Removed |Added Latest Commit||https://invent.kde.org/educ ||ation/parley/commit/30168c0 ||c5539e2ca7d9811493b0912f77e ||14044c Status|ASSIGNED|RESOLVED Resolution|--- |FIXED --- Comment #2 from Alexander Lohnau --- Git commit 30168c0c5539e2ca7d9811493b0912f77e14044c by Alexander Lohnau. Committed on 18/07/2020 at 19:59. Pushed by alex into branch 'master'. Fix deprecated knsrc file location M +5-1src/CMakeLists.txt https://invent.kde.org/education/parley/commit/30168c0c5539e2ca7d9811493b0912f77e14044c -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 423938] Drag and Drop files from task manager
https://bugs.kde.org/show_bug.cgi?id=423938 --- Comment #5 from beojan --- That sounds close, though perhaps the proxy icon could also be shown in the full task manager. That way, you don't need to restore the window before dragging from it. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 424552] Right clicking on a item sometimes causes a misclick
https://bugs.kde.org/show_bug.cgi?id=424552 Raghavendra kamath changed: What|Removed |Added CC||ra...@raghukamath.com --- Comment #2 from Raghavendra kamath --- I think this is related to [bug](https://bugs.kde.org/show_bug.cgi?id=374311) which is an upstream Qt problem as reported [here](https://bugreports.qt.io/browse/QTBUG-57849) -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 423844] discover crash on cancelling snap install
https://bugs.kde.org/show_bug.cgi?id=423844 --- Comment #2 from kinghat --- (In reply to Christoph Feck from comment #1) > If possible, please add the backtrace of the crash. It is possible the crash > depends on the selected packagekit backend, and the backtrace can identify > which component is responsible. > > For more information, please see > https://community.kde.org/Guidelines_and_HOWTOs/Debugging/ > How_to_create_useful_crash_reports i installed kdelibs5-dbg and i already had plasma-discover-dbgsym. the only thing in the crash handler developer tab is "Application: Discover (plasma-discover), signal: Segmentation fault" it seems there should be more to the backtrace than this. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 424525] Wrong behavior of blending modes in CMYK
https://bugs.kde.org/show_bug.cgi?id=424525 --- Comment #6 from nikola --- Dmitry, thanks for the hint and I tried it. Unfortunately, I didn't seem to be clear. 1. Workaround for standard*1* multiply would be to select screen blending mode and vice versa. Thus, the whole process is without changing the color space and/or profile (so no unwanted color transformations) and with the expected blending. The color readings with picker are 100% correct all the time. 2. When the artwork is done set all the layers that have multiply to screen and set all screen layers to multiply. Export to psd and import into any layout software that can read psd and continue working on e.g. illustrated book. 3. Later, if you want to edit the file, layers are preserved. All you need to do is repeat the swapping with the opposite blending so you can see the correct output. Swap (multiply/screen) again before saving. All said for blend modes for layers apply for brushes too. standard*1* - If we agree that pdf is the most widely used standard in the print industry, Table 7.1 Standard separable blend modes roughly describes the behavior of blend modes in CMYK space as well as in space with spot colors. See: wwwimages2.adobe.com/content/dam/acom/en/devnet/pdf/pdf_reference_archive/blend_modes.pdf -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 424555] New: dolphin doesn't refresh contents of mounted samba shares when they are changed remotely
https://bugs.kde.org/show_bug.cgi?id=424555 Bug ID: 424555 Summary: dolphin doesn't refresh contents of mounted samba shares when they are changed remotely Product: dolphin Version: 19.12.3 Platform: Kubuntu Packages OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: view-engine: general Assignee: dolphin-bugs-n...@kde.org Reporter: ster...@gmail.com CC: kfm-de...@kde.org Target Milestone: --- SUMMARY When the contents of a mounted samba share are modified remotely, dolphin does not refresh the view. Even navigating to a different folder and then back or closing and reopening does not trigger a refresh. Only manual refresh with F5 updates the view. I can go as far as closing dolphin, reopen it a few seconds later and files that had been deleted are still there. When I try to access them I get an error that they don't exist obviously and finally the view is updated. Furthermore, when having multiple dolphin windows open, manually refreshing the view in one window does not trigger a refresh in the other windows. STEPS TO REPRODUCE 1. Mount a samba shared folder 2. View the contents of this folder in dolphin 3. Add/delete/modify files in this folder from another computer OBSERVED RESULT The contents of the folder remain unchanged until a manual refresh command is issued or an error is encountered trying to access the files. EXPECTED RESULT The contents of the folder should be updated almost instantly. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: Kubuntu 20.04 (available in About System) KDE Plasma Version: 5.18.5 KDE Frameworks Version: 5.68.0 Qt Version: 5.12.8 ADDITIONAL INFORMATION Modifying the contents of the folder locally through a terminal window does trigger a refresh. It's only when the changes happen remotely that a refresh isn't triggered. Finally, doing the opposite (modifying the contents of the folder in dolphin while watching it on a win10 file explorer window) triggers an instant refresh in file explorer. -- You are receiving this mail because: You are watching all bug changes.
[kdiff3] [Bug 424177] Typos in man page
https://bugs.kde.org/show_bug.cgi?id=424177 michael changed: What|Removed |Added Resolution|FIXED |--- Status|RESOLVED|REOPENED -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 424554] New: Dolphin use mobile hard drive's recycle bin when move file to trash
https://bugs.kde.org/show_bug.cgi?id=424554 Bug ID: 424554 Summary: Dolphin use mobile hard drive's recycle bin when move file to trash Product: dolphin Version: 20.04.3 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: huohuo5...@gmail.com CC: kfm-de...@kde.org Target Milestone: --- SUMMARY Dolphin use the mobile hard drive's recycle bin when move file in `/home` to trash. STEPS TO REPRODUCE 1. Create an empty file `~/0` 2. Start Dolphin 3. Move `/home/cheese/0` to trash OBSERVED RESULT It shows '回收站已到达其最大容量！\n请手动清理回收站。' Which means 'The recycle bin has reached its maximum capacity! \nPlease manually clean up the recycle bin.' ``` $ journalctl --since "1 min ago" 7月 23 09:16:30 arch-linux kdeinit5[2824]: kf5.kio.trash: Directory "/run/media/cheese/Data/.Trash-1000" exists but didn't pass the security checks, can't use it> 7月 23 09:16:30 arch-linux dolphin[2805]: "回收站已到达其最大容量！\n请手动清理回收站。" 7月 23 09:16:30 arch-linux kdeinit5[2824]: kf5.kio.trash: Directory "/run/media/cheese/Data/.Trash-1000" exists but didn't pass the security checks, can't use it> ``` It seems that Dolphin tried to use the recycle bin of the mobile hard drive. EXPECTED RESULT Move `0` to `/home/cheese/.local/share/Trash` SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: Arch Linux (available in About System) KDE Plasma Version: 5.19.3 KDE Frameworks Version: 5.72.0 Qt Version: 5.15.0 ADDITIONAL INFORMATION ``` $ cat /etc/fstab UUID=2f311d25-b460-4b46-bedd-fdbefbe4e715 / ext4 rw,relatime 0 1 # /dev/sdb1 UUID=2BB5-BDC2 /boot vfat rw,relatime 0 2 UUID=8006A77E06A773B6 /run/media/cheese/Data ntfs-3g rw,relatime,nofail,uid=1000,gid=1000,umask=022,utf8 0 0 ``` And even I remove `uid,gid,umask` from it and reboot, the problem still exists. And `didn't pass the security checks` maybe because of ntfs permissions.(https://bugs.kde.org/show_bug.cgi?id=76380) Is it a good idea to use `gio trash`? It works well on two disks. Thanks. -- You are receiving this mail because: You are watching all bug changes.
[kinfocenter] [Bug 424490] Useless 'Defaults', 'Reset', , and 'Apply' button.
https://bugs.kde.org/show_bug.cgi?id=424490 Nate Graham changed: What|Removed |Added Version Fixed In||5.20 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 424501] Right click >> Open in File Manager does not work
https://bugs.kde.org/show_bug.cgi?id=424501 caulier.gil...@gmail.com changed: What|Removed |Added Version Fixed In|7.0.0 |7.1.0 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 424501] Right click >> Open in File Manager does not work
https://bugs.kde.org/show_bug.cgi?id=424501 caulier.gil...@gmail.com changed: What|Removed |Added Status|REPORTED|RESOLVED Version Fixed In||7.0.0 Resolution|--- |NOT A BUG -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 424553] Authenticating to flickr does not work
https://bugs.kde.org/show_bug.cgi?id=424553 caulier.gil...@gmail.com changed: What|Removed |Added CC||caulier.gil...@gmail.com --- Comment #1 from caulier.gil...@gmail.com --- Please try with 7.0.0: https://download.kde.org/stable/digikam/7.0.0/ Gilles Caulier -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 423851] Custom color smudge engine brush doesn't blend while there is selection
https://bugs.kde.org/show_bug.cgi?id=423851 Lynx3d changed: What|Removed |Added CC||lynx.mw+...@gmail.com Ever confirmed|0 |1 Status|REPORTED|CONFIRMED --- Comment #1 from Lynx3d --- I'm seeing it here with the bundled "k)_Blender_Blur" brush, no custom brush required. It hardly does anything inside a selection with 4.3 git (Linux)... I'm alsmost sure it used to work, screams for some regression testing. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 321190] Please re-add mousebutton to close windows in Present Windows
https://bugs.kde.org/show_bug.cgi?id=321190 --- Comment #106 from Justin --- My apologies, I didn't see the comment further up that it had been fixed, have found the setting as well thanks to help in the Telegram group. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 321190] Please re-add mousebutton to close windows in Present Windows
https://bugs.kde.org/show_bug.cgi?id=321190 Justin changed: What|Removed |Added CC||justin.zo...@gmail.com --- Comment #105 from Justin --- I'd love to see this re-instated but to alleviate the concerns of the danger of a user closing it the following options: Option 1: - Add the middle click as an option to close (not default). Option 2: - Make middle click to close the default option but the process would be as follows: 1. User middle clicks to close app 2. App is instead hidden temporarily 3. Notification (like when a widget is deleted) allowing users to undo, if chosen app is unhidden. 4. If users doesn't undo action within x seconds the app is then closed -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 424553] New: Authenticating to flickr does not work
https://bugs.kde.org/show_bug.cgi?id=424553 Bug ID: 424553 Summary: Authenticating to flickr does not work Product: digikam Version: 6.4.0 Platform: Ubuntu Packages OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: Plugin-WebService-Flickr Assignee: digikam-bugs-n...@kde.org Reporter: brownphotograp...@gmail.com Target Milestone: --- Created attachment 130326 --> https://bugs.kde.org/attachment.cgi?id=130326=edit screenshot of error SUMMARY Authenticating to flickr fails for digikam STEPS TO REPRODUCE 1. Export menu >> Export to Flickr 2. Add another account 3. Flickr Launches, I click 'ok I'll authorize' 4. flickr fails OBSERVED RESULT I get following error message: Secure Connection Failed An error occurred during a connection to 127.0.0.1:1965. SSL received a record that exceeded the maximum permissible length. Error code: SSL_ERROR_RX_RECORD_TOO_LONG The page you are trying to view cannot be shown because the authenticity of the received data could not be verified. Please contact the website owners to inform them of this problem. EXPECTED RESULT After authorizing, I should be sent back to digikam and account is added. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Operating System: Kubuntu 20.04 KDE Plasma Version: 5.18.5 KDE Frameworks Version: 5.68.0 Qt Version: 5.12.8 Kernel Version: 5.4.0-26-generic OS Type: 64-bit Processors: 16 × Intel® Xeon® CPU E5520 @ 2.27GHz Memory: 11.7 GiB of RAM ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 381620] Is not authenticating user
https://bugs.kde.org/show_bug.cgi?id=381620 Rob Brown changed: What|Removed |Added CC||brownphotograp...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 416497] No shadows on GTK menus
https://bugs.kde.org/show_bug.cgi?id=416497 --- Comment #6 from David Rubio --- As a midly useful note, xfwm4 compositor doesn't seem to render shadows on the firefox menu until "show shadows under popup windows" is enabled. Might be worth looking into how they do it? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 423938] Drag and Drop files from task manager
https://bugs.kde.org/show_bug.cgi?id=423938 Nate Graham changed: What|Removed |Added Status|REPORTED|NEEDSINFO Resolution|--- |WAITINGFORINFO --- Comment #4 from Nate Graham --- That feels like it could be hard for the user to predict. For example in Okular, dragging the task manager icon would drag the application itself while there were no documentss open, but drag the document when there is a document open. And there would always be a behavioral inconsistency for document-based apps vs other apps. I suppose we could badge the icon with a little document symbol or something. But I think a better solution would be Bug 390797. Can you check that out and see if you agree? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 424389] Regression in "active screen follows mouse"
https://bugs.kde.org/show_bug.cgi?id=424389 Nate Graham changed: What|Removed |Added Version Fixed In||5.19.4 CC||n...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 422591] Add "logout" option after inactivity period
https://bugs.kde.org/show_bug.cgi?id=422591 --- Comment #3 from Nate Graham --- FWIW macOS offers this feature, and what they do is show a dialog with a 60 second timeout, at which point the app is killed. I guess they assume that if you enable this feature, your goal of logigng out of the system after inactivity trumps potential data integrity. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 424340] PDF bookmarks not found when opening document by symbolic link
https://bugs.kde.org/show_bug.cgi?id=424340 Nate Graham changed: What|Removed |Added CC||n...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 424306] Add reverse DNS name symlinks for app icons to support theming Flatpak app icons
https://bugs.kde.org/show_bug.cgi?id=424306 Nate Graham changed: What|Removed |Added Priority|NOR |HI -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 424306] Add reverse DNS name symlinks for app icons to support theming Flatpak app icons
https://bugs.kde.org/show_bug.cgi?id=424306 Nate Graham changed: What|Removed |Added CC||niccolo.venera...@gmail.com --- Comment #4 from Nate Graham --- I started doing this by hand but got exhausted. Feels like the kind of thing that should be done programmatically at build time by having the necessary symlinks generated automatically according to a simple mapping in a text file or something. Maybe with a little Python script. :) -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 424552] Right clicking on a item sometimes causes a misclick
https://bugs.kde.org/show_bug.cgi?id=424552 --- Comment #1 from David Edmundson --- Does it happen only in the popup in the video or more generically? -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 424340] PDF bookmarks not found when opening document by symbolic link
https://bugs.kde.org/show_bug.cgi?id=424340 Bug Janitor Service changed: What|Removed |Added Status|REPORTED|ASSIGNED Ever confirmed|0 |1 --- Comment #1 from Bug Janitor Service --- A possibly relevant merge request was started @ https://invent.kde.org/graphics/okular/-/merge_requests/224 -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 423723] Subjectively speaking, Discover takes too long to be useful after it starts up
https://bugs.kde.org/show_bug.cgi?id=423723 Nate Graham changed: What|Removed |Added Version Fixed In||5.20 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 424551] Gamma error in picture scaling
https://bugs.kde.org/show_bug.cgi?id=424551 Lukas Frank changed: What|Removed |Added Component|Filters |General -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 424551] Gamma error in picture scaling
https://bugs.kde.org/show_bug.cgi?id=424551 Lukas Frank changed: What|Removed |Added CC||lukasfran...@gmail.com Flags||Backport+, Brainstorm-, ||corner_case-, ||Translation_missing-, ||Usability+ Component|Filter Layers |Filters -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 424552] New: Right clicking on a item sometimes causes a misclick
https://bugs.kde.org/show_bug.cgi?id=424552 Bug ID: 424552 Summary: Right clicking on a item sometimes causes a misclick Product: plasmashell Version: 5.18.5 Platform: Ubuntu Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: oceanodefol...@pm.me CC: plasma-b...@kde.org Target Milestone: 1.0 Created attachment 130325 --> https://bugs.kde.org/attachment.cgi?id=130325=edit bug happening SUMMARY It's random and very annoying. I attach a video of the bug happened. Initially I thought this was intentional, like mouse lock feature or something, but it's not. Then I thought that I was the one misclicking, but I'm pretty sure I didn't click with the left button when recording this video. STEPS TO REPRODUCE Right click a lot of times until the bug happens. OBSERVED RESULT Right click causes a misclick. EXPECTED RESULT Not causing a misclick. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: Kubuntu 20.04 (available in About System) KDE Plasma Version: 5.18.5 KDE Frameworks Version: 5.68.0 Qt Version: 5.12.8 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 424551] New: Gamma error in picture scaling
https://bugs.kde.org/show_bug.cgi?id=424551 Bug ID: 424551 Summary: Gamma error in picture scaling Product: krita Version: 4.3.0-beta1 Platform: Other OS: Linux Status: REPORTED Severity: major Priority: NOR Component: Filter Layers Assignee: krita-bugs-n...@kde.org Reporter: lukasfran...@gmail.com Target Milestone: --- Created attachment 130324 --> https://bugs.kde.org/attachment.cgi?id=130324=edit Specially crafted image to demonstrate gamma error SUMMARY Resizing images produces a gamma error. This can clearly be demonstrated by resizing a specially crafted image. It affects all images and worsens the image quality by making them "darker". A more in depth explanation and how to fix this problem can be found on the website http://www.ericbrasseur.org/gamma.html?i=1 STEPS TO REPRODUCE 1. Download "gamma_dalai_lama_gray.jpg" from the attachments 2. Open gamma_dalai_lama_gray.jpg with Krita 3. Proportionally resize the image by doing: 3.1 Image -> Resize Picture 3.2 Tick "Constrain Proportions" and Select "%" 3.3 Pick 50% for width and heigth 3.4 You can pick any one of the filters except Nearest Neighbour 3.5 Press OK ALTERNATVE STEPS TO REPRODUCE 1. Step 1 and 2 as above 2. Scroll down the mouse wheel until the zoom factor is 50% OBSERVED RESULT The image comes out grey or grey with some barely visible outlines. EXPECTED RESULT Picture with natural colors. SOFTWARE/OS VERSIONS Archlinux with kernel 5.6.17 KDE Plasma: (available in About System) KDE Plasma Version: plasma-desktop 5.19.3-1 KDE Frameworks Version: plasma-framework 5.72.0-1 Qt Version: qt5-base 5.15.0-4 ADDITIONAL INFORMATION krita 4.3.0-1 amdgpu-core-meta 19.30_934563-1 xf86-video-amdgpu 19.1.0-2 mesa 20.1.3-1 lib32-mesa 20.1.3-1 libva 2.8.0-1 libva-mesa-driver 20.1.3-1 lib32-libva-mesa-driver 20.1.3-1 mesa-vdpau 20.1.3-1 lib32-mesa-vdpau 20.1.3-1 -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 423723] Subjectively speaking, Discover takes too long to be useful after it starts up
https://bugs.kde.org/show_bug.cgi?id=423723 Aleix Pol changed: What|Removed |Added Status|ASSIGNED|RESOLVED Resolution|--- |FIXED Latest Commit||https://invent.kde.org/plas ||ma/discover/commit/3e85afeb ||8e1d52264262d8093b27da52e58 ||bf1d7 --- Comment #8 from Aleix Pol --- Git commit 3e85afeb8e1d52264262d8093b27da52e58bf1d7 by Aleix Pol. Committed on 22/07/2020 at 22:39. Pushed by apol into branch 'master'. pk: only resolve packages as they're offered from a ::search call It should make the resolve calls a bit faster since we are not processing all packages at startup. It does increase the calls we make though. M +1-1libdiscover/backends/PackageKitBackend/CMakeLists.txt R +34 -6libdiscover/backends/PackageKitBackend/PKResolveTransaction.cpp [from: libdiscover/backends/PackageKitBackend/TransactionSet.cpp - 053% similarity] R +15 -6libdiscover/backends/PackageKitBackend/PKResolveTransaction.h [from: libdiscover/backends/PackageKitBackend/TransactionSet.h - 080% similarity] M +89 -54 libdiscover/backends/PackageKitBackend/PackageKitBackend.cpp M +8-3libdiscover/backends/PackageKitBackend/PackageKitBackend.h M +11 -0libdiscover/utils.h https://invent.kde.org/plasma/discover/commit/3e85afeb8e1d52264262d8093b27da52e58bf1d7 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 424550] New: Pinning window to all desktops should hold window steady when switching
https://bugs.kde.org/show_bug.cgi?id=424550 Bug ID: 424550 Summary: Pinning window to all desktops should hold window steady when switching Product: kwin Version: 5.19.2 Platform: Neon Packages OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: effects-window-management Assignee: kwin-bugs-n...@kde.org Reporter: wolft...@gmail.com Target Milestone: --- SUMMARY It would be superior user experience if a pinned window was held in place during desktop-switching animations rather than as just having a copy on every desktop. STEPS TO REPRODUCE 1. Pin a window to all desktops (have more than one desktop) 2. With some desktop switching animation on, switch desktops OBSERVED RESULT The pinned window slides away with the desktop and then shows up again with the contents of the other desktop. EXPECTED RESULT The pinned window doesn't slide or move, it just stays in place while the desktops slide underneath, showing that it's not actually two copies of a program but is in fact a single window. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: KDE Neon 5.19 (available in About System) KDE Plasma Version: 5.19.3 KDE Frameworks Version: 5.72.0 Qt Version: 5.14.2 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[Artikulate] [Bug 423899] Segmentation fault on fresh build of artikulate
https://bugs.kde.org/show_bug.cgi?id=423899 --- Comment #5 from Avinash Sonawane --- > see https://doc.qt.io/qt-5/deployment-plugins.html As per the linked page Qt searches for plugins in application's executable directory and indeed there are libartikulatesound.so and qtmultimediabackend.so along with other .so s in ./build/bin/. I'm not sure which plugin is "missing". > all you have to do to set the path correctly in your environment. $ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 20.04 LTS Release:20.04 Codename: focal $ git clone https://invent.kde.org/education/artikulate $ mkdir artikulate/build; cd artikulate/build $ cmake .. $ make -j4 $ ./bin/artikulate ... log_liblearner: No last active profile found, falling back to first found profile QObject::connect(OutputBackendInterface, OutputDeviceController): invalid null parameter Segmentation fault (core dumped) $ Please let me know which environment variable needs to be set and could it be done by the build process itself? Interesting observation is that if I `apt install artikulate` then the ./build/bin/artikulate runs successfully without any SegFault. It's as if it wants .so s to be in /usr/lib/x86_64-linux-gnu/artikulate and /usr/lib/x86_64-linux-gnu/qt5/plugins/artikulate/ completely ignoring the identical .so s in ./build/bin/ -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 424548] panel changing to dock when you increase zoom on hover / space between panel and expanded applet
https://bugs.kde.org/show_bug.cgi?id=424548 --- Comment #2 from Ezike Ebuka --- (In reply to Michail Vourlakos from comment #1) > You can not have zoom on hover in Panel mode. It is not possible from > technology point of view. the only reason i enabled zoom on hover is too have a space between the expanded applet and the panel is there a way to get a space in betweene the expanded applet and the panel ? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 424538] The Window rules dialog does not show
https://bugs.kde.org/show_bug.cgi?id=424538 --- Comment #3 from Ezike Ebuka --- (In reply to Ismael Asensio from comment #1) > Hi Ezike, > > The dialog not showing on wayland is a known bug: > https://bugs.kde.org/show_bug.cgi?id=421405. I have some questions on the > other issues you mention. > > Does the dialog through the alt+f3 menu show on X11? > > On system settings (both x11 && wayland) the rules editor should show and > allow you to add new properties to the rule via `Add Properties` and `Detect > Window Properties` buttons. Is this also not working for you? > > Thanks in advance yes a dialog box show when you press alt + f3 but if you click more actions >> configure application or configure window the next dialog box does not show there is no add properties or detect window properties button if there is where is it located ? there is an attached video file showing the details of what i mean in it to clear any confusion the video was made on x11 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 424538] The Window rules dialog does not show
https://bugs.kde.org/show_bug.cgi?id=424538 --- Comment #2 from Ezike Ebuka --- yes a dialog box show when you press alt + f3 but if you click more actions >> configure application or configure window the next dialog box does not show there is no add properties or detect window properties button if there is where is it located ? there is an attached video file showing the details of what i mean in it to clear any confusion the video was made on x11 -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 424548] panel changing to dock when you increase zoom on hover / space between panel and expanded applet
https://bugs.kde.org/show_bug.cgi?id=424548 --- Comment #1 from Michail Vourlakos --- You can not have zoom on hover in Panel mode. It is not possible from technology point of view. -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 424548] panel changing to dock when you increase zoom on hover / space between panel and expanded applet
https://bugs.kde.org/show_bug.cgi?id=424548 Michail Vourlakos changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |UPSTREAM -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 424549] New: [Request] Allow to vertically expand Bézier curve panel
https://bugs.kde.org/show_bug.cgi?id=424549 Bug ID: 424549 Summary: [Request] Allow to vertically expand Bézier curve panel Product: kdenlive Version: 20.04.3 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Effects & Transitions Assignee: vpi...@kde.org Reporter: chameleonsca...@protonmail.com Target Milestone: --- When I do precision work, the vertical size of the Bezier curve effect makes it difficult to fine-tune the curve, especially on my 140 ppi 4K monitor. https://i.imgur.com/LalGpOd.png It would be great if we could drag the panel down and expand the curve grid vertically. -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 424548] New: panel changing to dock when you increase zoom on hover / space between panel and expanded applet
https://bugs.kde.org/show_bug.cgi?id=424548 Bug ID: 424548 Summary: panel changing to dock when you increase zoom on hover / space between panel and expanded applet Product: lattedock Version: git (master) Platform: Manjaro OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: application Assignee: mvourla...@gmail.com Reporter: yerimy...@gmail.com Target Milestone: --- Created attachment 130323 --> https://bugs.kde.org/attachment.cgi?id=130323=edit link SUMMARY basically when you increase zoom on hover it becomes a dock STEPS TO REPRODUCE 1. go to edit panel 2. apparance >> zoom on hover OBSERVED RESULT the panel changes to a dock and applies zoom on hover. EXPECTED RESULT the panel stay a panel and applies zoom on hover SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: Manjaro KDE 5.19.3 (available in About System) KDE Plasma Version: 5.19.3. KDE Frameworks Version: 5.73.0 Qt Version: 5.15.0 ADDITIONAL INFORMATION to enable space between the expanded applet/widget and the panel. this is only available when zoom on hover is enabled. even when zoom on hover is activated there is no space between the expanded system tray applet and the panel -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 353463] RFE: Make use of iio-sensor-proxy
https://bugs.kde.org/show_bug.cgi?id=353463 David Edmundson changed: What|Removed |Added Resolution|--- |FIXED Status|REOPENED|RESOLVED --- Comment #14 from David Edmundson --- Kscreen currently supports QtSensors. QtSensors supports iio-sensor-proxy. That has been merged. If there is a bug in that it needs to be addressed with more detail. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 423766] systemsettings5 crash
https://bugs.kde.org/show_bug.cgi?id=423766 --- Comment #3 from Nicolas Fella --- There is a nested event loop in the code -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kholidays] [Bug 424547] New: Kholidays doesn't show the Jewish holidays
https://bugs.kde.org/show_bug.cgi?id=424547 Bug ID: 424547 Summary: Kholidays doesn't show the Jewish holidays Product: frameworks-kholidays Version: unspecified Platform: unspecified OS: All Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: omeritzicschwa...@gmail.com Target Milestone: --- SUMMARY Kholidays doesn't show the Jewish holidays. OBSERVED RESULT Kholidays doesn't show the Jewish holidays. EXPECTED RESULT Kholidays show the Jewish holidays. SOFTWARE/OS VERSIONS Linux/KDE Plasma: KDE neon Testing. KDE Plasma Version: 5.19.3 KDE Frameworks Version: 5.73.0 Qt Version: 5.14.2 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 375331] Black screen after resuming from hibernation
https://bugs.kde.org/show_bug.cgi?id=375331 --- Comment #12 from anomalous...@gmail.com --- May or may not be of any consequence, but peeking at kwin_x11 with strace after the black screen occurs shows the process stuck at: restart_syscall(<... resuming interrupted read ...> -- You are receiving this mail because: You are watching all bug changes.
[kactivitymanagerd] [Bug 419499] Switch activity shortcut order
https://bugs.kde.org/show_bug.cgi?id=419499 --- Comment #8 from Adam Bark --- It works as you show it but after selecting an activity if I then try to select another activity the activities remain in the same order. I was just trying to replicate it but I have several bugs with the switcher, some times it switches activities without popping up the overlay, sometimes the overlay isn't dismissed once I release the keys and this bug. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 375331] Black screen after resuming from hibernation
https://bugs.kde.org/show_bug.cgi?id=375331 anomalous...@gmail.com changed: What|Removed |Added CC||anomalous...@gmail.com --- Comment #11 from anomalous...@gmail.com --- This just started happening for me in the past week or two on Arch Linux with the stock repo packages. Had been working fine up to that point. Randomly after a suspend-to-ram or monitor-suspend, the screen comes up entirely black with a themed mouse cursor able to be moved. I'm able to ctrl-alt-f2 into a terminal. I've tried poking around a bit to see what exactly is borked but the best I can come up with kwin_x11 has trashed itself in an unrecoverable and unlogged way. Trying to "DISPLAY=:0 kwin_x11 --replace" with or without the kquitapp5 / kstart5 voodoo results in a compositing unavailable error in the syslog. I'm not able to recover my session or any desktop environment once this occurs. Following prior discussion, I saw nothing of note in kscreen-doctor: it outputs the same 3 monitors enabled and connected before and after the black screen occurs. KDE Plasma Version 5.19.3 KDE Frameworks 5.72.0 Qt Version 5.15.0 Kernel Version 5.7.9-arch1-1 / 64-bit Running on Ryzen 1700x & Nvidia GTX 1080 with binary driver 450.57 (I tried rolling back to the previous driver, version 440, with no success). Please let me know if there is any logging or triage I can do to help uncover this mystery. -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 353463] RFE: Make use of iio-sensor-proxy
https://bugs.kde.org/show_bug.cgi?id=353463 --- Comment #13 from Nate Graham --- Sebastian, would you be willing to consider upstreaming your kded module? Seems like it would be handy to have. We can help you polish it up, of course. -- You are receiving this mail because: You are watching all bug changes.
[konqueror] [Bug 47320] [testcase] text and background uses colors from KDE color scheme if not specified in the html style
https://bugs.kde.org/show_bug.cgi?id=47320 xd changed: What|Removed |Added CC||scottsi...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasma-pa] [Bug 424273] Plugged in headphones with microphone are only detected partially
https://bugs.kde.org/show_bug.cgi?id=424273 el...@seznam.cz changed: What|Removed |Added Status|RESOLVED|REOPENED Ever confirmed|0 |1 Resolution|UPSTREAM|--- --- Comment #7 from el...@seznam.cz --- I reopened the bug because Tanu at PulseAudio made a suggestion for Plasma: The input device isn't automatically switched, because PulseAudio doesn't know what you plugged in. The kernel tells PulseAudio only that "either headphones, a headset or a microphone was plugged in". In this situation Gnome asks the users what they plugged in. There's recent work to make the PulseAudio API better for this: !283 (merged). That's not yet available in any released version, but if KDE wants to implement something similar, that API is the way to do it (I have some unpublished fixes and additional documentation for it, hopefully I'll finish them soon). So please consider whether it's something you would like to do. Thanks. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 236288] after saving, okular should switch to saved document
https://bugs.kde.org/show_bug.cgi?id=236288 David Hurka changed: What|Removed |Added Resolution|--- |FIXED Status|REPORTED|RESOLVED --- Comment #1 from David Hurka --- After Save As, the document is reloaded, so I think this is fixed now. Other problems are bug 402017 and 415482. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 412101] Wayland session does not remember the last used keyboard layout. The first keyboard layout listed in "layouts" tab of the "Keyboard" kcm is always used after login instead.
https://bugs.kde.org/show_bug.cgi?id=412101 --- Comment #13 from Andrey --- I'm not an expert in Neon but perhaps it doesn't build immediately on every commit. What I can see is the current unstable version named neon-unstable-20200719-1102.iso and the patch was merged Jul 20'th https://invent.kde.org/plasma/kwin/-/merge_requests/38#note_76678, might it be the reason? -- You are receiving this mail because: You are watching all bug changes.
[kdiff3] [Bug 424177] Typos in man page
https://bugs.kde.org/show_bug.cgi?id=424177 --- Comment #6 from justindonne...@verizon.net --- Thanks, but it appears that the commits so far will only fix errors in the OPTIONS portion of the man page. It does not appear that the commits will fix errors in the SYNOPSIS. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 424540] Option "regular expression" does not work
https://bugs.kde.org/show_bug.cgi?id=424540 Maik Qualmann changed: What|Removed |Added Resolution|--- |FIXED Version Fixed In||7.1.0 Latest Commit||https://invent.kde.org/grap ||hics/digikam/commit/1a75efb ||008816087a08479cd79c786f7ad ||e794fd Status|REPORTED|RESOLVED --- Comment #1 from Maik Qualmann --- Git commit 1a75efb008816087a08479cd79c786f7ade794fd by Maik Qualmann. Committed on 22/07/2020 at 20:12. Pushed by mqualmann into branch 'master'. allow backslash for input, for Windows file system it will be filtered later FIXED-IN: 7.1.0 M +2-1NEWS M +0-1core/utilities/advancedrename/advancedrenameinput.cpp https://invent.kde.org/graphics/digikam/commit/1a75efb008816087a08479cd79c786f7ade794fd -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 423766] systemsettings5 crash
https://bugs.kde.org/show_bug.cgi?id=423766 --- Comment #2 from Christoph Feck --- Every thread has an event loop, that's not a problem. Using a nested QEventLoop would be problematic, but that is not visible from the backtrace. -- You are receiving this mail because: You are watching all bug changes.
[ksysguard] [Bug 350140] KSysGuard crashed on close
https://bugs.kde.org/show_bug.cgi?id=350140 Germano Massullo changed: What|Removed |Added Version|5.8.7 |5.18.5 -- You are receiving this mail because: You are watching all bug changes.
[ksysguard] [Bug 350140] KSysGuard crashed on close
https://bugs.kde.org/show_bug.cgi?id=350140 Germano Massullo changed: What|Removed |Added CC||germano.massu...@gmail.com --- Comment #50 from Germano Massullo --- ksysguard 5.18.5 KDE Frameworks 5.70.0 Qt 5.14.2 Application: Monitor di sistema (ksysguard), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". 29return SYSCALL_CANCEL (poll, fds, nfds, timeout); [Current thread is 1 (Thread 0x7fcc840da980 (LWP 16244))] Thread 22 (Thread 0x7fcc38bf9700 (LWP 16300)): #0 __GI___libc_read (nbytes=16, buf=0x7fcc38bf89a0, fd=12) at ../sysdeps/unix/sysv/linux/read.c:26 #1 __GI___libc_read (fd=12, buf=buf@entry=0x7fcc38bf89a0, nbytes=nbytes@entry=16) at ../sysdeps/unix/sysv/linux/read.c:24 #2 0x7fcc87b8c53f in read (__nbytes=16, __buf=0x7fcc38bf89a0, __fd=) at /usr/include/bits/unistd.h:44 #3 g_wakeup_acknowledge (wakeup=0x5587e1c72fb0) at ../glib/gwakeup.c:210 #4 0x7fcc87b4260e in g_main_context_check (context=context@entry=0x7fcc14000c20, max_priority=2147483647, fds=fds@entry=0x7fcc14004e60, n_fds=n_fds@entry=1) at ../glib/gmain.c:3825 #5 0x7fcc87b42a75 in g_main_context_iterate (context=context@entry=0x7fcc14000c20, block=block@entry=1, dispatch=dispatch@entry=1, self=) at ../glib/gmain.c:4044 #6 0x7fcc87b42c03 in g_main_context_iteration (context=0x7fcc14000c20, may_block=may_block@entry=1) at ../glib/gmain.c:4108 #7 0x7fcc904dfb8b in QEventDispatcherGlib::processEvents (this=0x7fcc14000b60, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #8 0x7fcc9049291b in QEventLoop::exec (this=this@entry=0x7fcc38bf8bd0, flags=..., flags@entry=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:136 #9 0x7fcc902fe427 in QThread::exec (this=) at ../../include/QtCore/../../src/corelib/global/qflags.h:118 #10 0x7fcc9080851b in QDBusConnectionManager::run (this=0x7fcc90877060 <(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at qdbusconnection.cpp:179 #11 0x7fcc902ff690 in QThreadPrivate::start (arg=0x7fcc90877060 <(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at thread/qthread_unix.cpp:342 #12 0x7fcc88473432 in start_thread (arg=) at pthread_create.c:477 #13 0x7fcc91d13913 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 21 (Thread 0x7fcc397fa700 (LWP 16299)): #0 futex_wait_cancelable (private=0, expected=0, futex_word=0x5587e1bfef90) at ../sysdeps/nptl/futex-internal.h:183 #1 __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x5587e1bfef40, cond=0x5587e1bfef68) at pthread_cond_wait.c:508 #2 __pthread_cond_wait (cond=0x5587e1bfef68, mutex=0x5587e1bfef40) at pthread_cond_wait.c:638 #3 0x7fcc74e5526b in cnd_wait (mtx=0x5587e1bfef40, cond=0x5587e1bfef68) at ../include/c11/threads_posix.h:155 #4 util_queue_thread_func (input=input@entry=0x5587e1b855b0) at ../src/util/u_queue.c:275 #5 0x7fcc74e54d3b in impl_thrd_routine (p=) at ../include/c11/threads_posix.h:87 #6 0x7fcc88473432 in start_thread (arg=) at pthread_create.c:477 #7 0x7fcc91d13913 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 20 (Thread 0x7fcc39ffb700 (LWP 16298)): #0 futex_wait_cancelable (private=0, expected=0, futex_word=0x5587e1b37be8) at ../sysdeps/nptl/futex-internal.h:183 #1 __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x5587e1b37b98, cond=0x5587e1b37bc0) at pthread_cond_wait.c:508 #2 __pthread_cond_wait (cond=0x5587e1b37bc0, mutex=0x5587e1b37b98) at pthread_cond_wait.c:638 #3 0x7fcc74e5526b in cnd_wait (mtx=0x5587e1b37b98, cond=0x5587e1b37bc0) at ../include/c11/threads_posix.h:155 #4 util_queue_thread_func (input=input@entry=0x5587e1b3c9e0) at ../src/util/u_queue.c:275 #5 0x7fcc74e54d3b in impl_thrd_routine (p=) at ../include/c11/threads_posix.h:87 #6 0x7fcc88473432 in start_thread (arg=) at pthread_create.c:477 #7 0x7fcc91d13913 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 19 (Thread 0x7fcc3a7fc700 (LWP 16297)): #0 futex_wait_cancelable (private=0, expected=0, futex_word=0x5587e1b37be8) at ../sysdeps/nptl/futex-internal.h:183 #1 __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x5587e1b37b98, cond=0x5587e1b37bc0) at pthread_cond_wait.c:508 #2 __pthread_cond_wait (cond=0x5587e1b37bc0, mutex=0x5587e1b37b98) at pthread_cond_wait.c:638 #3 0x7fcc74e5526b in cnd_wait (mtx=0x5587e1b37b98, cond=0x5587e1b37bc0) at ../include/c11/threads_posix.h:155 #4 util_queue_thread_func (input=input@entry=0x5587e1b3c780) at ../src/util/u_queue.c:275 #5 0x7fcc74e54d3b in impl_thrd_routine (p=) at ../include/c11/threads_posix.h:87 #6 0x7fcc88473432 in start_thread (arg=) at pthread_create.c:477 #7 0x7fcc91d13913 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 18 (Thread 0x7fcc3affd700 (LWP
[frameworks-kwayland] [Bug 424546] New: CTRL+MAIU+ALT+v does not work properly with LibreOffice
https://bugs.kde.org/show_bug.cgi?id=424546 Bug ID: 424546 Summary: CTRL+MAIU+ALT+v does not work properly with LibreOffice Product: frameworks-kwayland Version: 5.71.0 Platform: Slackware Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: mgraess...@kde.org Reporter: michelino.chionc...@gmail.com CC: kwin-bugs-n...@kde.org Target Milestone: --- SUMMARY In Wayland session When I past unformatted text (ctrl+maiu+alt+v) in LibreOffice the text results in Chinese language and in no way I can change the language back to my preferred one. This doesn’t happen in “normal” plasma session. STEPS TO REPRODUCE 1. Open LibreOffice in Wayland 2. copy a text 3. past unformatted text OBSERVED RESULT text pasted results in Chinese language EXPECTED RESULT text pasted in presetted language SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: Slackware Linux (available in About System) KDE Plasma Version: 5.19.1 KDE Frameworks Version: 5.71.0 Qt Version: 5.15.0 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 423824] System Settings crash when installing cursors from local file
https://bugs.kde.org/show_bug.cgi?id=423824 Christoph Feck changed: What|Removed |Added Component|general |kcm_cursortheme -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 423874] System Settings Crash if clicking into a different sub section
https://bugs.kde.org/show_bug.cgi?id=423874 Christoph Feck changed: What|Removed |Added Severity|normal |crash -- You are receiving this mail because: You are watching all bug changes.
[wacomtablet] [Bug 423883] Graphic Tablet configuration does not show shortcut buttons tab for Wacom Intuos S P [0374]
https://bugs.kde.org/show_bug.cgi?id=423883 Christoph Feck changed: What|Removed |Added Assignee|plasma-b...@kde.org |jazzv...@gmail.com Component|kcmshell|general Version|5.18.5 |unspecified Product|systemsettings |wacomtablet Summary|Graphic Tablet |Graphic Tablet |configuration does not show |configuration does not show |shortcut buttons tab|shortcut buttons tab for ||Wacom Intuos S P [0374] -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 424545] New: Dolphin may list non-existent files after failed attempt of bulk deletion
https://bugs.kde.org/show_bug.cgi?id=424545 Bug ID: 424545 Summary: Dolphin may list non-existent files after failed attempt of bulk deletion Product: dolphin Version: 20.04.2 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: view-engine: general Assignee: dolphin-bugs-n...@kde.org Reporter: alexander.shchadi...@gmail.com CC: kfm-de...@kde.org Target Milestone: --- SUMMARY If Dolphin is not able to delete some of the selected files due to permissions a subset of selected files is still purged. Files that have been deleted are still shown in a directory until Dolphin is restarted. STEPS TO REPRODUCE 1. touch possible.txt 2. sudo mkdir impossible && sudo touch ./impossible/file.txt 3. In Dolphin, navigate to Home and use Ctrl+LMB to select multiple items: "impossible" folder and "possible.txt". 4. Press Shift+Del and choose "Delete" in a dialogue box. OBSERVED RESULT Error message appears, "possible.txt" is deleted from storage, both "impossible" folder and "possible.txt" are still shown in Home until Dolphin restart. EXPECTED RESULT Error message appears, "possible.txt" is deleted from storage and is no longer shown in Home. SOFTWARE/OS VERSIONS openSUSE Leap 15.2 KDE Plasma Version: 5.18.5 KDE Frameworks Version: 5.71.0 Qt Version: 5.12.7 -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 423991] KDE's policy on territorial disputes
https://bugs.kde.org/show_bug.cgi?id=423991 --- Comment #2 from Christoph Feck --- I was assuming we don't have, see bug 422452. If the resolution of that ticket is wrong, please change it. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 422948] Startup sound does not play; system muted until after login
https://bugs.kde.org/show_bug.cgi?id=422948 Patrick Silva changed: What|Removed |Added CC||cpwes...@gmail.com --- Comment #34 from Patrick Silva --- *** Bug 424521 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 424521] Login sounds no longer work on 5.19.3
https://bugs.kde.org/show_bug.cgi?id=424521 Patrick Silva changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |DUPLICATE CC||bugsefor...@gmx.com --- Comment #1 from Patrick Silva --- *** This bug has been marked as a duplicate of bug 422948 *** -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 423799] tablet pen input doesn't rotate with screen rotation
https://bugs.kde.org/show_bug.cgi?id=423799 --- Comment #1 from Christoph Feck --- Is this a Wacom pen? The Wacom KCM might have a feature to detect/configure rotation, according to https://invent.kde.org/system/wacomtablet/-/commit/5f42c2174935d7a0a35e7f8a39ed599f9e3ef8d6 If you don't have it installed, please ask in a forum of your distribution for the package name of https://invent.kde.org/system/wacomtablet -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 424544] CSV importer cannot deal with recipient & description in separate(!) columns?
https://bugs.kde.org/show_bug.cgi?id=424544 Jack changed: What|Removed |Added Resolution|--- |WAITINGFORINFO Status|REPORTED|NEEDSINFO --- Comment #1 from Jack --- Is this a translation issue? I would interpret what you call recipient as Payee, and description as Memo. In the CSV import, the Memo field can be taken from multiple columns, and the column used for the Payee can also be part of the Memo column. If this doesn't help, please expand on your description of the problem with a more detailed example. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 423930] Will not build with Boost 1.73
https://bugs.kde.org/show_bug.cgi?id=423930 j...@mesecons.net changed: What|Removed |Added CC||j...@mesecons.net -- You are receiving this mail because: You are watching all bug changes.
[frameworks-ktexteditor] [Bug 423839] Block mode (switch: on/off) only if holding/releasing Alt+Shift shortcut
https://bugs.kde.org/show_bug.cgi?id=423839 Piotr Mierzwinski changed: What|Removed |Added Summary|Block mode (selection) only |Block mode (switch: on/off) |if holding Alt+Shift|only if holding/releasing |shortcut|Alt+Shift shortcut -- You are receiving this mail because: You are watching all bug changes.
[frameworks-ktexteditor] [Bug 423839] Block mode (selection) only if holding Alt+Shift shortcut
https://bugs.kde.org/show_bug.cgi?id=423839 Piotr Mierzwinski changed: What|Removed |Added CC||piotr.mierzwin...@gmail.com --- Comment #2 from Piotr Mierzwinski --- I'm aware how it works. Constantly I use it working with Notepad++ in my regular work. And I think this one in KTextEditor is less comfortable and less safe. In my opinion switching mode implemented in KTextEditor is more leading to accidental mistakes in editing, just because user can forget that this mode is turned on. He needs look to status bar to be sure that this mode is turned on/off. Just compare this to block mode working only when keys shortcut combination is hold on. And after release this combination user back to normal selection mode. Switching mode implemented in KTextEditor needs more activities from user - he needs to press proper keys combination twice. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 417325] touch feature does not rotate with screen
https://bugs.kde.org/show_bug.cgi?id=417325 Christoph Feck changed: What|Removed |Added Resolution|--- |FIXED Status|CONFIRMED |RESOLVED --- Comment #2 from Christoph Feck --- Commit from comment 1 was merged. Reporter of bug 423799 also confirms touchpad rotation works. https://commits.kde.org/kwin/5b6e081af20e3469b1893a3d48f9e675015693d8 -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 424057] Fade effect is blackish instead or real fade
https://bugs.kde.org/show_bug.cgi?id=424057 --- Comment #3 from emohr --- I see your point. Could you upload here both pictures the unsplash-bg.jpg and the logo-2.png so I can make a test. -- You are receiving this mail because: You are watching all bug changes.
[Artikulate] [Bug 423899] Segmentation fault on fresh build of artikulate
https://bugs.kde.org/show_bug.cgi?id=423899 --- Comment #4 from Andreas Cord-Landwehr --- You do not find anything in the CMake output, because your problem is not in the build system: When starting Artikulate, it looks in your system at the Qt default paths for plugins as well as the location that are defined with QT_PLUGIN_PATH (see https://doc.qt.io/qt-5/deployment-plugins.html). Because Artikulate does not find the (apparently correctly built plugins) it crashes on startup. Thus, all you have to do to set the path correctly in your environment. -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 400466] Kontact crash on close
https://bugs.kde.org/show_bug.cgi?id=400466 Christoph Feck changed: What|Removed |Added CC||cf...@kde.org Resolution|--- |FIXED Status|REPORTED|RESOLVED --- Comment #11 from Christoph Feck --- All reports are from old versions; assuming it was fixed in the meantime. If you can still reproduce with recent versions (Kontact 5.14 or later), please add a comment. -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 400466] Kontact crash on close
https://bugs.kde.org/show_bug.cgi?id=400466 Christoph Feck changed: What|Removed |Added CC||reinhardau...@gmx.at --- Comment #10 from Christoph Feck --- *** Bug 423803 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 423803] KOrganizer crashed
https://bugs.kde.org/show_bug.cgi?id=423803 Christoph Feck changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |DUPLICATE --- Comment #2 from Christoph Feck --- *** This bug has been marked as a duplicate of bug 400466 *** -- You are receiving this mail because: You are watching all bug changes.
[frameworks-knewstuff] [Bug 423050] After I switch between "Installed only" and "Updateable only" filters, "Get new " window briefly says "There is no hot new stuff to get here" before lists th
https://bugs.kde.org/show_bug.cgi?id=423050 Alexander Lohnau changed: What|Removed |Added CC||alexander.loh...@gmx.de Status|REPORTED|CONFIRMED Ever confirmed|0 |1 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 423840] Versions 4.3.0 onwards have non-responsive canvas after enabling/disabling Canvas Graphics Acceleration
https://bugs.kde.org/show_bug.cgi?id=423840 Eoin O'Neill changed: What|Removed |Added Status|ASSIGNED|RESOLVED Latest Commit||https://invent.kde.org/grap ||hics/krita/commit/c0362a9ca ||fa18c035215ebc2703fe5f6ff45 ||6220 Resolution|--- |FIXED --- Comment #5 from Eoin O'Neill --- Git commit c0362a9cafa18c035215ebc2703fe5f6ff456220 by Eoin O'Neill. Committed on 22/07/2020 at 19:04. Pushed by eoinoneill into branch 'master'. Fixup: Canvas No Longer Soft-Locks When Changing Graphics Acceleration Setting Initial attempt to fix this bug, tracked origin from commit: 5aef0e99a7b64a8cdb6970803e9c080d47e918e6 NOTE: Originally, we didn't always check for *new* canvas assignments, only that the canvas wasn't within a specific data structure. M +3-0libs/ui/input/kis_input_manager_p.cpp https://invent.kde.org/graphics/krita/commit/c0362a9cafa18c035215ebc2703fe5f6ff456220 -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 423914] Annotation text does not appear in Ubuntu 20.04 after installing tex-gyre
https://bugs.kde.org/show_bug.cgi?id=423914 Christoph Feck changed: What|Removed |Added Summary|[flatpak] Annotation text |Annotation text does not |does not appear in Ubuntu |appear in Ubuntu 20.04 |20.04 after installing |after installing tex-gyre |tex-gyre| -- You are receiving this mail because: You are watching all bug changes.
