[krita] [Bug 456922] SVG file that makes Krita use memory infinitely until I kill the process
https://bugs.kde.org/show_bug.cgi?id=456922 --- Comment #4 from Bug Janitor Service --- A possibly relevant merge request was started @ https://invent.kde.org/graphics/krita/-/merge_requests/1532 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 439145] opening an svg file fills the memory up
https://bugs.kde.org/show_bug.cgi?id=439145 Bug Janitor Service changed: What|Removed |Added Status|REPORTED|ASSIGNED Ever confirmed|0 |1 --- Comment #9 from Bug Janitor Service --- A possibly relevant merge request was started @ https://invent.kde.org/graphics/krita/-/merge_requests/1532 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 457149] New: Plasma start with systemd breaks certain autostart file
https://bugs.kde.org/show_bug.cgi?id=457149 Bug ID: 457149 Summary: Plasma start with systemd breaks certain autostart file Product: plasmashell Version: 5.25.3 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Startup process Assignee: plasma-b...@kde.org Reporter: wen...@gmail.com CC: k...@davidedmundson.co.uk Target Milestone: 1.0 Right now, plasma autostart relies on systemd's xdg autostart generator. There are certain cases that is not handled with current mechanism. For the desktop file with X-systemd-skip or X-GNOME-Autostart-Phase (based on the doc, https://www.freedesktop.org/software/systemd/man/systemd-xdg-autostart-generator.html ), the service won't be generated, but also it doesn't mean they should not be started. Those should go through the traditional autostart code and be started. Right now startplasma would just skip all of such desktop file that is not generated by systemd. -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 456823] Pressing ESC key inside Spectacle's annotation mode inappropriately quits the app
https://bugs.kde.org/show_bug.cgi?id=456823 Antonio Prcela changed: What|Removed |Added Latest Commit|https://invent.kde.org/grap |https://invent.kde.org/grap |hics/spectacle/commit/dd1d7 |hics/spectacle/commit/37ee3 |baecd7a3d9356992151e57f1c38 |95ca0e1ef05febc82daa3a2ffb2 |0e9500c8|431a65b5 --- Comment #7 from Antonio Prcela --- Git commit 37ee395ca0e1ef05febc82daa3a2ffb2431a65b5 by Antonio Prcela. Committed on 26/07/2022 at 06:28. Pushed by aprcela into branch 'master'. using ESC while in annotation mode will close annotator instead of closing spectacle User's request is to only exit current tool in annotator. That'd be something upstream if I'm not mistaken. This does not solve the feature request 100%, instead it only improves the behaviour a bit. (cherry picked from commit dd1d7baecd7a3d9356992151e57f1c380e9500c8) M +8-0src/Gui/KSMainWindow.cpp https://invent.kde.org/graphics/spectacle/commit/37ee395ca0e1ef05febc82daa3a2ffb2431a65b5 -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 456823] Pressing ESC key inside Spectacle's annotation mode inappropriately quits the app
https://bugs.kde.org/show_bug.cgi?id=456823 Antonio Prcela changed: What|Removed |Added Resolution|--- |FIXED Latest Commit||https://invent.kde.org/grap ||hics/spectacle/commit/dd1d7 ||baecd7a3d9356992151e57f1c38 ||0e9500c8 Status|ASSIGNED|RESOLVED --- Comment #6 from Antonio Prcela --- Git commit dd1d7baecd7a3d9356992151e57f1c380e9500c8 by Antonio Prcela. Committed on 26/07/2022 at 06:25. Pushed by aprcela into branch 'release/22.08'. using ESC while in annotation mode will close annotator instead of closing spectacle User's request is to only exit current tool in annotator. That'd be something upstream if I'm not mistaken. This does not solve the feature request 100%, instead it only improves the behaviour a bit. M +8-0src/Gui/KSMainWindow.cpp https://invent.kde.org/graphics/spectacle/commit/dd1d7baecd7a3d9356992151e57f1c380e9500c8 -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 456823] Pressing ESC key inside Spectacle's annotation mode inappropriately quits the app
https://bugs.kde.org/show_bug.cgi?id=456823 --- Comment #5 from Antonio Prcela --- (In reply to D3XT3R from comment #4) > (In reply to Antonio Prcela from comment #3) > > as written in commit msg: > > > > "User's request is to only exit current tool in annotator. > > That'd be something upstream if I'm not mistaken. > > This does not solve the feature request 100%, instead it only > > improves the behaviour a bit." > > You are correct, this only lessens the loss. > With the proposed solution, you didn't lose the screenshot, but I lost all > the annotations made :( That seems to depend on your version of kImageannotator. Doesn't lose annotations on my end when i press ESC. kImageannotator version: 0.6.1 do: `ls /usr/lib/ | grep libkImage` and see what version number you got at, for example: libkImageAnnotator.so.0.6.1 iirc 0.6.0 is atm the latest one, i build 0.6.1 myself from source -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 457123] Krita 5.1.0 beta2 : crash after reading a recently opened PSD file
https://bugs.kde.org/show_bug.cgi?id=457123 Dmitry Kazakov changed: What|Removed |Added Assignee|krita-bugs-n...@kde.org |dimul...@gmail.com CC||dimul...@gmail.com Status|CONFIRMED |ASSIGNED --- Comment #2 from Dmitry Kazakov --- I will look into this bug. -- You are receiving this mail because: You are watching all bug changes.
[Craft] [Bug 457148] digiKam Windows bundles build from Binary Factory with Craft : MSVC version can be signed but not MinGW
https://bugs.kde.org/show_bug.cgi?id=457148 caulier.gil...@gmail.com changed: What|Removed |Added URL||https://binary-factory.kde. ||org/view/Windows%20MingW/jo ||b/Digikam_Nightly_mingw64/ -- You are receiving this mail because: You are watching all bug changes.
[Craft] [Bug 457148] New: digiKam Windows bundles build from Binary Factory with Craft : MSVC version can be signed but not MinGW
https://bugs.kde.org/show_bug.cgi?id=457148 Bug ID: 457148 Summary: digiKam Windows bundles build from Binary Factory with Craft : MSVC version can be signed but not MinGW Product: Craft Version: master Platform: Microsoft Windows OS: Microsoft Windows Status: REPORTED Severity: normal Priority: NOR Component: Blueprints Assignee: vonr...@kde.org Reporter: caulier.gil...@gmail.com CC: kde-wind...@kde.org Target Milestone: --- Hi, digiKam compile fine for Windows with Craft in Binary Factory using MSVC and MinGW targets. MVSC version is signed and packaging is complete. Installer and application work fine. MinGW version cannot be signed. See the log file: ... 04:07:14 Delete symbols: C:\Craft\BinaryFactory\windows-mingw_64-gcc\build\extragear\digikam\archive\bin\designer\sonnetui5widgets.dll.debug 04:07:14 Delete symbols: C:\Craft\BinaryFactory\windows-mingw_64-gcc\build\extragear\digikam\archive\bin\bearer\qgenericbearer.dll.debug 04:07:14 Delete symbols: C:\Craft\BinaryFactory\windows-mingw_64-gcc\build\extragear\digikam\archive\bin\audio\qtaudio_windows.dll.debug 04:07:14 Overriding: C:\Craft\BinaryFactory\windows-mingw_64-gcc\build\extragear\digikam\archive\Assets\128-apps-digikam.png with 04:07:14 C:\_\9b0777e7\digikam\core\data\icons\apps\128-apps-digikam.png 04:07:14 executing command: makeappx pack /d C:\Craft\BinaryFactory\windows-mingw_64-gcc\build\extragear\digikam\archive /p C:\Craft\BinaryFactory\windows-mingw_64-gcc\build\extragear\digikam\artifacts\digikam-master-946-windows-mingw_64-gcc.appx 04:07:14 *** Craft package succeeded: extragear/digikam after 1 minute 17 seconds *** 04:07:14 [WinError 2] The system cannot find the file specified 04:07:14 Traceback (most recent call last): 04:07:14File "C:\Craft\BinaryFactory\windows-mingw_64-gcc\craft\bin\craft.py", line 274, in 04:07:14 success = main(timer) 04:07:14File "C:\Craft\BinaryFactory\windows-mingw_64-gcc\craft\bin\craft.py", line 264, in main 04:07:14 if not CraftCommands.run(package, action, tempArgs): 04:07:14File "C:\Craft\BinaryFactory\windows-mingw_64-gcc\craft\bin\CraftCommands.py", line 431, in run 04:07:14 if not handlePackage(info, action, directTargets=directTargets): 04:07:14File "C:\Craft\BinaryFactory\windows-mingw_64-gcc\craft\bin\CraftCommands.py", line 94, in handlePackage 04:07:14 success = doExec(package, action) 04:07:14File "C:\Craft\BinaryFactory\windows-mingw_64-gcc\craft\bin\CraftCommands.py", line 58, in doExec 04:07:14 ret = package.instance.runAction(action) 04:07:14File "C:\Craft\BinaryFactory\windows-mingw_64-gcc\craft\bin\Package\PackageBase.py", line 247, in runAction 04:07:14 if not getattr(self, step)(): 04:07:14File "C:\Craft\BinaryFactory\blueprints\craft-blueprints-kde\extragear\digikam\digikam.py", line 288, in createPackage 04:07:14 return TypePackager.createPackage(self) 04:07:14File "C:\Craft\BinaryFactory\windows-mingw_64-gcc\craft\bin\Packager\TypePackager.py", line 85, in createPackage 04:07:14 return self.__packager.createPackage(self) 04:07:14File "C:\Craft\BinaryFactory\windows-mingw_64-gcc\craft\bin\Packager\AppxPackager.py", line 253, in createPackage 04:07:14 if not self.__createAppX(defines): 04:07:14File "C:\Craft\BinaryFactory\windows-mingw_64-gcc\craft\bin\Packager\AppxPackager.py", line 214, in __createAppX 04:07:14 utils.system(["makeappx", "pack", "/d", self.archiveDir(), "/p", archive])) 04:07:14File "C:\Craft\BinaryFactory\windows-mingw_64-gcc\craft\bin\utils.py", line 204, in system 04:07:14 return systemWithoutShell(cmd, displayProgress=displayProgress, logCommand=logCommand, acceptableExitCodes=acceptableExitCodes, **kw) 04:07:14File "C:\Craft\BinaryFactory\windows-mingw_64-gcc\craft\bin\utils.py", line 294, in systemWithoutShell 04:07:14 proc = subprocess.Popen(cmd, **kw) 04:07:14File "C:\Program Files\Python38\lib\subprocess.py", line 854, in __init__ 04:07:14 self._execute_child(args, executable, preexec_fn, close_fds, 04:07:14File "C:\Program Files\Python38\lib\subprocess.py", line 1307, in _execute_child 04:07:14 hp, ht, pid, tid = _winapi.CreateProcess(executable, args, 04:07:14 FileNotFoundError: [WinError 2] The system cannot find the file specified 04:07:14 Generate Settings 04:07:14 Command C:\Program Files\Python38\python.exe -u C:\Craft\BinaryFactory\windows-mingw_64-gcc\craft\bin\craft.py --options libs/ffmpeg.version=4.4 --options [Packager]PackageType=AppxPackager 04:07:14 --target master --package digikam failed with exit code: 1 [Pipeline] } [Pipeline] // stage [Pipeline] } 04:07:14 ERROR: script returned exit code 1 [Pipeline] // catchError [Pipeline] deleteDir [Pipeline] } [Pipeline] // timestamps [Pipeline] } [Pipeline] // node [Pi
[Akonadi] [Bug 457147] llee46467
https://bugs.kde.org/show_bug.cgi?id=457147 lia lee changed: What|Removed |Added URL||https://bzewks57.xyz/ -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 457147] New: llee46467
https://bugs.kde.org/show_bug.cgi?id=457147 Bug ID: 457147 Summary: llee46467 Product: Akonadi Version: 5.20.3 Platform: Other OS: Other Status: REPORTED Severity: normal Priority: NOR Component: akonadiconsole Assignee: kdepim-b...@kde.org Reporter: llee46...@gmail.com Target Milestone: --- Here are 50 great recession-proof businesses that historically perform well in times of economic uncertainty, ranked from easiest to hardest based on how difficult it is to start and operate the business. Aside from the difficulty rating, make sure to read the pros and cons for educational and capital requirements.Pros and Cons: The negative for this business is certain foods, such as those containing eggs, cannot be sold privately. For others, depending on your location, you will have to comply with the local regulations. For example, you may need a permit, to operate from a commercial kitchen, or to complete a food handler preparation course. The positive is that it requires little more than an oven, the ability to bake, and a community like a church or farmers market. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 457121] digikam 7.7.0 FTBFS against libavcodec59
https://bugs.kde.org/show_bug.cgi?id=457121 caulier.gil...@gmail.com changed: What|Removed |Added Severity|grave |normal --- Comment #4 from caulier.gil...@gmail.com --- Hi Erich, The solution for you is to use 7.x as well. If ffmpeg 5.x is present, the Media Player support will be disabled at configuration time. Of course you will not able to play with video files (aka thumbnails and preview will be unavailable). For 8.x, the plan is to release before end of this year and if projects advance well, to include the both GoSC 2022 tasks in this release. We will see. https://community.kde.org/GSoC/2022/Ideas#digiKam 8.x will be also compatible with Qt 6, but i do not recommend to use Qt6 for the moment. 8.x will be compatible with Qt5 LTS, so this version rock well. About the 8.x pending list bugs, we have the famous Media Player code to finalize with ffmpeg 5.x, and other regression checks to verify. For ex, we will progressively switch metadata write operations to ExifTool instead Exiv2, as this last library break regression tests more and more. ExifTool write feature have been introduced in 8.x only. We need to check performances and suitability. Don't forget the bundles that we provide, as AppImage which still compiled with ffmpeg 4.x. There are 2 versions: one build by the team, other one build with KDE infrastructure. The first one is provided since a very long time and is very powerful and complete. It's based on 7.x code. https://files.kde.org/digikam/ The second one need to be finalized as it do not support Mysql/mariadb database. It based on 8.x code. Some links: https://binary-factory.kde.org/view/AppImage/job/Digikam_Nightly_appimage-centos7/ Best Gilles Caulier -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 456846] Kate Snippets: not clear how to work with selected text
https://bugs.kde.org/show_bug.cgi?id=456846
Buovjaga changed:
What|Removed |Added
Ever confirmed|0 |1
Assignee|kwrite-bugs-n...@kde.org|ilmari.lauhakangas@libreoff
||ice.org
Status|REPORTED|ASSIGNED
--- Comment #4 from Buovjaga ---
(In reply to Thomas Friedrichsmeier from comment #3)
> But in fact, if you do not care about adding a default value, in case there
> is no selection, you can simply write (snippet tab):
>
> ${view.selectedText()}
>
> Would you like to create a merge request adding some illustrative examples?
Thanks a lot for these! Yes, I will look into creating a merge request for the
docs.
--
You are receiving this mail because:
You are watching all bug changes.
[kate] [Bug 457146] Search Results are messed if search text contains '\n'
https://bugs.kde.org/show_bug.cgi?id=457146 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/utilities/kate/-/merge_requests/820 -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 457146] New: Search Results are messed if search text contains '\n'
https://bugs.kde.org/show_bug.cgi?id=457146 Bug ID: 457146 Summary: Search Results are messed if search text contains '\n' Product: kate Version: Git Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: search Assignee: kwrite-bugs-n...@kde.org Reporter: waqar@gmail.com Target Milestone: --- STEPS TO REPRODUCE In Kate repo 1. Open Search & Replace Toolview, disable regex and match case 2. Type "\n" as text to search (without the quotes) 3. Perform a search OBSERVED RESULT Search results joins lines for some reason. EXPECTED RESULT Lines are not joined -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 413862] Panel will not go into auto hide mode
https://bugs.kde.org/show_bug.cgi?id=413862 Bug Janitor Service changed: What|Removed |Added Resolution|WAITINGFORINFO |WORKSFORME Status|NEEDSINFO |RESOLVED --- Comment #4 from Bug Janitor Service --- This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 443516] Scene split does nothing
https://bugs.kde.org/show_bug.cgi?id=443516 Bug Janitor Service changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |WORKSFORME --- Comment #4 from Bug Janitor Service --- This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 454856] `ctrl` modifier not reset even after the key has been released.
https://bugs.kde.org/show_bug.cgi?id=454856 --- Comment #6 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.
[frameworks-kio] [Bug 449600] kf.kio.slaves.file copy() QUrl mode= 420 Cannot copy file (Errno: 38)
https://bugs.kde.org/show_bug.cgi?id=449600 --- Comment #2 from Bug Janitor Service --- Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 456741] Display orientation change from landscape to portrait fail. Ubuntu Studio 22.04. Works fine with US 20.04 on same machine.
https://bugs.kde.org/show_bug.cgi?id=456741 --- Comment #11 from Keith Finnie --- Created attachment 150915 --> https://bugs.kde.org/attachment.cgi?id=150915&action=edit coredump2.txt -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 456741] Display orientation change from landscape to portrait fail. Ubuntu Studio 22.04. Works fine with US 20.04 on same machine.
https://bugs.kde.org/show_bug.cgi?id=456741 --- Comment #10 from Keith Finnie --- Hi Nate, I followed the instructions on the link you provided (to the best of my ability). The dumps are attached. Keith On Wed, 20 Jul 2022 at 06:54, Nate Graham wrote: > https://bugs.kde.org/show_bug.cgi?id=456741 > > --- Comment #9 from Nate Graham --- > Instructions can be found at > > https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports#Ubuntu-based_distros_.28Ubuntu.2C_Kubuntu.2C_KDE_Neon.2C_Linux_Mint.29 > > -- > You are receiving this mail because: > You reported the bug. -- You are receiving this mail because: You are watching all bug changes.
[i18n] [Bug 457057] inconsistency in polish translation of the keyboard shortcut description
https://bugs.kde.org/show_bug.cgi?id=457057 ktp changed: What|Removed |Added CC||ktpreze...@gmail.com --- Comment #2 from ktp --- Created attachment 150913 --> https://bugs.kde.org/attachment.cgi?id=150913&action=edit screenshots (2 joined) of the menu positions where the bug was found Hello according to your email, I have attached the screenshot - two of them joined actually - because in the midtime I've found the second place, where the same bug occurs: 1) the first place (reported at the beginning of that issue): menu "Przejdź" (EN: 'go' or 'goto' probably), position "Początek dokumentu / Ctrl+Katalog domowy" (EN: 'Beginning of the document' / 'Ctrl+Home') 2) the second place (new finding of the same bug): menu "Ustawienia" (EN: 'Settings' or 'Config' probably), position "Ustawienia skrótów klawiszowych" (EN: probably "Keyboard shortcuts settings") - and within the list which opens, the position: "Początek dokumentu / Ctrl+Katalog domowy" (EN: probably 'Beginning of the document / Ctrl+Home') In both places, the word 'Home' shouldn't be translated into polish "Katalog domowy", but just leaved simply as "Home", as in this context (exactly the same in both places) it is the proper name of the keyboard key, and NOT the name of "Home Directory", which term in exact polish translation is "Katalog domowy" kind regards Tadeusz Kurpiel -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 456882] heif decoding in 7.7.0 flatpak version not supported
https://bugs.kde.org/show_bug.cgi?id=456882 --- Comment #5 from caulier.gil...@gmail.com --- Paul, The FlatPak bundle build by KDE binary factory infrastruture will use libheif code from git master with my last commit. But i suppose that your system use the FlatHub factory from GitHub : https://github.com/flathub/org.kde.digikam This one use libheif version 1.12.0 which do not include the fix: https://github.com/flathub/org.kde.digikam/blob/master/org.kde.digikam.json#L675 We don't manage these settings. Please report this kind of fix in your UPSTREAM bug : https://github.com/flathub/org.kde.digikam/issues/40 Best Gilles Caulier -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 456882] heif decoding in 7.7.0 flatpak version not supported
https://bugs.kde.org/show_bug.cgi?id=456882 --- Comment #4 from caulier.gil...@gmail.com --- Git commit 114bb696438d7beadbaf5e4441fc5dc486a14eb6 by Gilles Caulier. Committed on 26/07/2022 at 02:49. Pushed by cgilles into branch 'master'. use libheif from master to build flatpak bundle M +1-1project/bundles/flatpak/org.kde.digikam.json https://invent.kde.org/graphics/digikam/commit/114bb696438d7beadbaf5e4441fc5dc486a14eb6 -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 457108] dolphin fail to bookmark ( add to places ) sshfs remote folder
https://bugs.kde.org/show_bug.cgi?id=457108 --- Comment #2 from GSC --- Created attachment 150912 --> https://bugs.kde.org/attachment.cgi?id=150912&action=edit peek of what I did I don' t have a "Remote" section . You can see the attached GIF for what I did and nothing happens except freeze of left side bar for a while(I keep scrolling mouse wheel and it started scrolling the places after a few seconds) -- You are receiving this mail because: You are watching all bug changes.
[kdeplasma-addons] [Bug 451767] Add Open-Meteo to providers
https://bugs.kde.org/show_bug.cgi?id=451767 David Chmelik changed: What|Removed |Added CC||dchme...@gmail.com --- Comment #1 from David Chmelik --- Good idea; there's currently only one in KDEP5--sometimes down; what happened to the several werein KDEP4?! -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 457145] New: Discover crashes when opening: Linux Font project Fonts: Var & Fixed
https://bugs.kde.org/show_bug.cgi?id=457145 Bug ID: 457145 Summary: Discover crashes when opening: Linux Font project Fonts: Var & Fixed Product: Discover Version: unspecified Platform: Ubuntu Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: discover Assignee: plasma-b...@kde.org Reporter: mpcolali...@gmail.com CC: aleix...@kde.org Target Milestone: --- SUMMARY *** NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** STEPS TO REPRODUCE 1. Open Discover 2. Click Plasma Addons 3. Click Fonts 4. Click on the "Linux Font project Fonts: Var & Fixed." Do not hit Install, just try clicking on the main bar of it, as if you want to read more about it before installing. OBSERVED RESULT Discover closed unexpectedly. EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: Kubuntu 22.04 (available in About System) KDE Plasma Version: 5.24.4 KDE Frameworks Version: 5.92.0 Qt Version: 5.15.3 ADDITIONAL INFORMATION Kernel Version 5.15.0-41-generic (64-bit) Graphics Platform: X11 Hardware: Processors: 2 × Intel® Celeron® N4000 CPU @ 1.10GHz Memory: 3.7 GiB of RAM Graphics Processor: llvmpipe -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 457100] About the problem that kdeconnect forwards to the upper port in the secondary route.关于kdeconnect在二级路由向上级端口转发的问题。
https://bugs.kde.org/show_bug.cgi?id=457100 --- Comment #2 from 2wxsy5823...@opayq.com --- I guess bug reporter means that his network is like this: ``` Modem/Router from ISP <> Router 1 <> Router 2 ^ ^ | | | | v v Phone Computer ``` For some reasons, he can only connect his computer to Router 2, and his phone is connected to Router 1. He would like to use KDE Connect across these two networks (to pair the phone with the computer). He tried port forwarding but it doesn't help. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 457144] New: KWin crashes when a Discord link is clicked
https://bugs.kde.org/show_bug.cgi?id=457144 Bug ID: 457144 Summary: KWin crashes when a Discord link is clicked Product: kwin Version: git master Platform: Compiled Sources OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: core Assignee: kwin-bugs-n...@kde.org Reporter: espi...@gmail.com Target Milestone: --- SUMMARY *** NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** Clicking on a link in Discord in a Wayland session sometimes causes KWin to crash and the session restarts. STEPS TO REPRODUCE 1. Open the application Discord 2. Click on a link, which should attempt to open the link in a browser OBSERVED RESULT Most of the time the screen goes black, and the session comes back after a few seconds. EXPECTED RESULT The session doesn't crash. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Arch Linux (available in About System) KDE Plasma Version: 5.25.3 KDE Frameworks Version: 5.97.0 Qt Version: 5.15.5 ADDITIONAL INFORMATION (gdb) backtrace #0 0x7f559eb2c36c in () at /usr/lib/libc.so.6 #1 0x7f559eadc838 in raise () at /usr/lib/libc.so.6 #2 0x7f559eadc8e0 in () at /usr/lib/libc.so.6 #3 0x7f559ec007bd in () at /usr/lib/libc.so.6 #4 0x7f55a020ca78 in qstrncpy(char*, char const*, unsigned int) () at /usr/lib/libQt5Core.so.5 #5 0x7f55a1d85798 in KWaylandServer::KeyboardInterfacePrivate::sendKeymap(QtWaylandServer::wl_keyboard::Resource*) (this=this@entry=0x55a6c163ff10, resource=resource@entry=0x55a6c2caeed0) at /home/devin/kde/src/kwin/src/wayland/keyboard_interface.cpp:95 #6 0x7f55a1d85c2b in KWaylandServer::KeyboardInterfacePrivate::keyboard_bind_resource(QtWaylandServer::wl_keyboard::Resource*) (this=0x55a6c163ff10, resource=0x55a6c2caeed0) at /home/devin/kde/src/kwin/src/wayland/keyboard_interface.cpp:38 #7 0x7f55a1def718 in QtWaylandServer::wl_keyboard::bind(wl_resource*) (this=0x55a6c163ff10, handle=0x55a6c2de9640) at /home/devin/kde/build/kwin/src/wayland/qwayland-server-wayland.cpp:4676 #8 0x7f55a1df497a in QtWaylandServer::wl_keyboard::bind(wl_client*, unsigned int, int) (version=, id=, client=0x55a6c2c9fe80, this=0x55a6c163ff10) at /home/devin/kde/build/kwin/src/wayland/qwayland-server-wayland.cpp:4666 #9 QtWaylandServer::wl_keyboard::add(wl_client*, int, int) (this=0x55a6c163ff10, client=0x55a6c2c9fe80, id=, version=) at /home/devin/kde/build/kwin/src/wayland/qwayland-server-wayland.cpp:4583 #10 0x7f559d89f536 in () at /usr/lib/libffi.so.8 #11 0x7f559d89c037 in () at /usr/lib/libffi.so.8 #12 0x7f559fff2ada in () at /usr/lib/libwayland-server.so.0 #13 0x7f559fff7010 in () at /usr/lib/libwayland-server.so.0 #14 0x7f559fff59e2 in wl_event_loop_dispatch () at /usr/lib/libwayland-server.so.0 #15 0x7f55a1d7ab65 in KWaylandServer::Display::dispatchEvents() (this=) at /home/devin/kde/src/kwin/src/wayland/display.cpp:114 #16 0x7f55a0398341 in () at /usr/lib/libQt5Core.so.5 #17 0x7f55a039a054 in QSocketNotifier::activated(QSocketDescriptor, QSocketNotifier::Type, QSocketNotifier::QPrivateSignal) () at /usr/lib/libQt5Core.so.5 #18 0x7f55a039a198 in QSocketNotifier::event(QEvent*) () at /usr/lib/libQt5Core.so.5 #19 0x7f559f242b3c in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /usr/lib/libQt5Widgets.so.5 #20 0x7f55a0367ad8 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /usr/lib/libQt5Core.so.5 #21 0x7f55a03b0fec in QEventDispatcherUNIXPrivate::activateSocketNotifiers() () at /usr/lib/libQt5Core.so.5 #22 0x7f55a03b20e1 in QEventDispatcherUNIX::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #23 0x55a6bf556f82 in QUnixEventDispatcherQPA::processEvents(QFlags) () #24 0x7f55a036027c in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #25 0x7f55a036ada9 in QCoreApplication::exec() () at /usr/lib/libQt5Core.so.5 #26 0x55a6bf461dec in main(int, char**) (argc=, argv=) at /home/devin/kde/src/kwin/src/main_wayland.cpp:64 (coredump attached) -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 416271] Setting to not remember recent documents confusingly lives in the Activities KCM
https://bugs.kde.org/show_bug.cgi?id=416271 Nate Graham changed: What|Removed |Added Version Fixed In||5.26 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 457074] New Present Windows in 5.25: Search bar should be optional + missing animation
https://bugs.kde.org/show_bug.cgi?id=457074 --- Comment #1 from Maximilian Böhm --- I want to add an argument for making the search bar optional: It is visual clutter. The search bar is a distracting element in a window effect that formally has had a magic aura of just all your windows plain in an overview without plasmoids. Now, there is this blurry layer and the bleached-out wallpaper we already talked about in: https://invent.kde.org/plasma/kwin/-/issues/106#note_477699 And on top of all, this search bar mess, unhandily put into this unnecessary layer like Microsoft put the ugly-as-hell Cortana search bar on Windows 10 computers just to generate more Bing searches. My proposal is to change the bar into just a monochrome search icon at the top right corner, whilst not reserving vertical space for it so window preview sizes aren’t reduced anymore through it. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 433045] Tablet configuration does not exist in wayland
https://bugs.kde.org/show_bug.cgi?id=433045 --- Comment #15 from Aleix Pol --- Git commit 5312497e47e64ec95e2265f5899e784c65026597 by Aleix Pol Gonzalez, on behalf of Aleix Pol. Committed on 25/07/2022 at 23:29. Pushed by apol into branch 'master'. tablet: Make it possible to specify how a tablet maps to an output M +11 -2kcms/tablet/inputdevice.cpp M +19 -0kcms/tablet/inputdevice.h M +24 -2kcms/tablet/kcmtablet.cpp A +75 -0kcms/tablet/package/contents/ui/Output.qml [License: GPL(v2.0+)] M +144 -12 kcms/tablet/package/contents/ui/main.qml https://invent.kde.org/plasma/plasma-desktop/commit/5312497e47e64ec95e2265f5899e784c65026597 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 457142] I am *never* seeing the clock on the lock screen
https://bugs.kde.org/show_bug.cgi?id=457142 --- Comment #3 from MountainX --- (In reply to Nate Graham from comment #2) > Hmm, none of those errors seem related to the clock. Do you have anything in > ~/.local/share/plasma/desktoptheme/? If so, can you print the contents? I do not have that folder. And inside ~/.local/share/plasma/, I only have: plasmoids: -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 433045] Tablet configuration does not exist in wayland
https://bugs.kde.org/show_bug.cgi?id=433045 --- Comment #14 from Aleix Pol --- Git commit 27f24d144933ef1c0916ae18737a69ca274bfe8a by Aleix Pol Gonzalez, on behalf of Aleix Pol. Committed on 25/07/2022 at 23:29. Pushed by apol into branch 'master'. input: Introduce a outputArea property for tablet devices It's important for tablet devices to be able to specify to which section of the display we'll be fitting the tablet. This setting allows to specify this by providing some options that will do so relative to the output size. M +20 -0autotests/libinput/mock_libinput.cpp M +28 -2src/backends/libinput/device.cpp M +11 -0src/backends/libinput/device.h M +7-0src/backends/libinput/events.cpp M +1-5src/backends/libinput/events.h https://invent.kde.org/plasma/kwin/commit/27f24d144933ef1c0916ae18737a69ca274bfe8a -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 454480] Discover shows inaccurate warning about proprietary software for open-source Snap applications
https://bugs.kde.org/show_bug.cgi?id=454480 Aleix Pol changed: What|Removed |Added Latest Commit|https://invent.kde.org/plas |https://invent.kde.org/plas |ma/discover/commit/2787a529 |ma/discover/commit/8c616082 |2608115140e618bf904dd1eadfa |2d83e0825fc49fcc4ac5af160d2 |70a52 |fe9ec --- Comment #9 from Aleix Pol --- Git commit 8c6160822d83e0825fc49fcc4ac5af160d2fe9ec by Aleix Pol Gonzalez, on behalf of Aleix Pol. Committed on 25/07/2022 at 23:27. Pushed by apol into branch 'Plasma/5.25'. pk: Try harder to convert non-appstream packages licences It will try to use as_license_to_spdx_id which does its best guess, hopefully it will be enough on most cases, will submit some others that I've seen upstream to catch some other cases. (cherry picked from commit 2787a5292608115140e618bf904dd1eadfa70a52) M +1-1discover/qml/ApplicationPage.qml M +23 -18 libdiscover/appstream/AppStreamUtils.cpp M +2-0libdiscover/appstream/AppStreamUtils.h M +36 -1libdiscover/backends/PackageKitBackend/PackageKitResource.cpp https://invent.kde.org/plasma/discover/commit/8c6160822d83e0825fc49fcc4ac5af160d2fe9ec -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 454480] Discover shows inaccurate warning about proprietary software for open-source Snap applications
https://bugs.kde.org/show_bug.cgi?id=454480 Aleix Pol changed: What|Removed |Added Latest Commit||https://invent.kde.org/plas ||ma/discover/commit/2787a529 ||2608115140e618bf904dd1eadfa ||70a52 Resolution|--- |FIXED Status|ASSIGNED|RESOLVED --- Comment #8 from Aleix Pol --- Git commit 2787a5292608115140e618bf904dd1eadfa70a52 by Aleix Pol Gonzalez, on behalf of Aleix Pol. Committed on 25/07/2022 at 23:19. Pushed by apol into branch 'master'. pk: Try harder to convert non-appstream packages licences It will try to use as_license_to_spdx_id which does its best guess, hopefully it will be enough on most cases, will submit some others that I've seen upstream to catch some other cases. M +1-1discover/qml/ApplicationPage.qml M +23 -18 libdiscover/appstream/AppStreamUtils.cpp M +2-0libdiscover/appstream/AppStreamUtils.h M +36 -1libdiscover/backends/PackageKitBackend/PackageKitResource.cpp https://invent.kde.org/plasma/discover/commit/2787a5292608115140e618bf904dd1eadfa70a52 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 457143] Windows with an odd width appear blurry
https://bugs.kde.org/show_bug.cgi?id=457143 --- Comment #2 from Noah Davis --- Created attachment 150911 --> https://bugs.kde.org/attachment.cgi?id=150911&action=edit testoddwidth.qml screenshot after moving window -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 457143] Windows with an odd width appear blurry
https://bugs.kde.org/show_bug.cgi?id=457143 --- Comment #1 from Noah Davis --- Created attachment 150910 --> https://bugs.kde.org/attachment.cgi?id=150910&action=edit testoddwidth.qml screenshot before moving window -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 457143] New: Windows with an odd width appear blurry
https://bugs.kde.org/show_bug.cgi?id=457143 Bug ID: 457143 Summary: Windows with an odd width appear blurry Product: kwin Version: git master Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kwin-bugs-n...@kde.org Reporter: noaha...@gmail.com Target Milestone: --- Created attachment 150909 --> https://bugs.kde.org/attachment.cgi?id=150909&action=edit testoddwidth.qml SUMMARY When a window with an odd width is created, the entire window is blurry, including server side window decorations. It's almost like the window has a fractional position. I know that QWindows only use integers for x/y/width/height and I'm using a 1x scale factor, so that doesn't make any sense, but it's all I can think of. Moving the window fixes the problem. STEPS TO REPRODUCE 1. Run the attached testoddwidth.qml file with qmlscene. OBSERVED RESULT The window looks blurry and there are various 1 pixel wide graphical artifacts when hovering over titlebar buttons EXPECTED RESULT The window should not look blurry and have no graphical artifacts. SOFTWARE/OS VERSIONS Operating System: openSUSE Tumbleweed 20220719 KDE Plasma Version: 5.25.80 KDE Frameworks Version: 5.97.0 Qt Version: 5.15.5 Kernel Version: 5.18.6-1-default (64-bit) Graphics Platform: X11 Processors: 16 × AMD Ryzen 7 4800H with Radeon Graphics Memory: 30.8 GiB of RAM Graphics Processor: AMD RENOIR Manufacturer: Eluktronics Product Name: THINN-15 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 457082] Configuration entry names and tooltips not translated to Brazilian Portuguese language
https://bugs.kde.org/show_bug.cgi?id=457082 --- Comment #2 from D3XT3R --- (In reply to Nate Graham from comment #1) > It looks like the app's .desktop file has a Brazilian Portuguese translation > for these strings: > > $ grep pt_BR /usr/share/applications/org.freedesktop.IBus.Setup.desktop > 38:Name[pt_BR]=Preferências do IBus > 86:Comment[pt_BR]=Definir Preferências do IBus > > Could be a code issue on our side. A few questions: > 1. Does this happen with any other apps? > 2. Does it happen in Kickoff's List View mode? > 3. Does it happen if you temporarily switch to Kicker (Application Menu)? Answers to questions: 1. Yes, IBus Preferences and Input Method. 2. Yes, it happens in list view. 3. Yes, it happens with other launcher options. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 457142] I am *never* seeing the clock on the lock screen
https://bugs.kde.org/show_bug.cgi?id=457142 Nate Graham changed: What|Removed |Added Resolution|--- |WAITINGFORINFO Target Milestone|--- |1.0 Status|REPORTED|NEEDSINFO Product|kscreenlocker |plasmashell CC||n...@kde.org, ||visual-des...@kde.org Component|general |Theme - Breeze --- Comment #2 from Nate Graham --- Hmm, none of those errors seem related to the clock. Do you have anything in ~/.local/share/plasma/desktoptheme/? If so, can you print the contents? -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 454074] Clock missing on lock screen
https://bugs.kde.org/show_bug.cgi?id=454074 --- Comment #11 from Nate Graham --- Yeah that's what I need, thanks. -- You are receiving this mail because: You are watching all bug changes.
[korganizer] [Bug 436372] Cannot synchronize with my Nextcloud carddav/caldav
https://bugs.kde.org/show_bug.cgi?id=436372 BEEDELL ROKE JULIAN LOCKHART changed: What|Removed |Added CC||beedellrokejulianlockhart@g ||mail.com -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 457139] kwin_wayland crashes in KWin::DrmGpu::~DrmGpu() when plugging in an HDMI monitor
https://bugs.kde.org/show_bug.cgi?id=457139 --- Comment #2 from Nate Graham --- Sure but won't I lose everything once kwin_wayland crashes? How would that work? -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 456823] Pressing ESC key inside Spectacle's annotation mode inappropriately quits the app
https://bugs.kde.org/show_bug.cgi?id=456823 --- Comment #4 from D3XT3R --- (In reply to Antonio Prcela from comment #3) > as written in commit msg: > > "User's request is to only exit current tool in annotator. > That'd be something upstream if I'm not mistaken. > This does not solve the feature request 100%, instead it only > improves the behaviour a bit." You are correct, this only lessens the loss. With the proposed solution, you didn't lose the screenshot, but I lost all the annotations made :( -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 441195] Gmail with MFA shouldn't require an app specific password
https://bugs.kde.org/show_bug.cgi?id=441195 --- Comment #3 from BEEDELL ROKE JULIAN LOCKHART --- (In reply to Caleb Cushing from comment #2) > Ok, to make korganizer work with google, there's a "google groupware" this > works basically how I think that logging into gmail shold work. I'm fairly > confident that it could just request the additional permissions, and that it > should be a shared component for all PIM, instead of seemingly just > available for korganizer, although it *also* grabs your contacts for > kaddressbook. I agree. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 441195] Gmail with MFA shouldn't require an app specific password
https://bugs.kde.org/show_bug.cgi?id=441195 BEEDELL ROKE JULIAN LOCKHART changed: What|Removed |Added CC||beedellrokejulianlockhart@g ||mail.com -- You are receiving this mail because: You are watching all bug changes.
[libkgapi] [Bug 439285] Bad request, Google replied "Contacts API is being deprecated"
https://bugs.kde.org/show_bug.cgi?id=439285 BEEDELL ROKE JULIAN LOCKHART changed: What|Removed |Added CC||beedellrokejulianlockhart@g ||mail.com -- You are receiving this mail because: You are watching all bug changes.
[kile] [Bug 429452] Kile crashed clicking on "zoom" button
https://bugs.kde.org/show_bug.cgi?id=429452 Douglas changed: What|Removed |Added Ever confirmed|1 |0 Status|CONFIRMED |REPORTED -- You are receiving this mail because: You are watching all bug changes.
[kile] [Bug 429452] Kile crashed clicking on "zoom" button
https://bugs.kde.org/show_bug.cgi?id=429452 Douglas changed: What|Removed |Added Status|REPORTED|CONFIRMED Ever confirmed|0 |1 CC||doubzar...@gmail.com --- Comment #5 from Douglas --- I'm with the same issue. gdb log: Thread 1 "kile" received signal SIGSEGV, Segmentation fault. PageViewAnnotator::detachAnnotation (this=0x0) at /usr/src/debug/okular-22.04.3/part/pageviewannotator.cpp:1293 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 457139] kwin_wayland crashes in KWin::DrmGpu::~DrmGpu() when plugging in an HDMI monitor
https://bugs.kde.org/show_bug.cgi?id=457139 Zamundaaa changed: What|Removed |Added CC||xaver.h...@gmail.com --- Comment #1 from Zamundaaa --- This doesn't look right - it's jumping from destroying the gbm_device to some code inside KWin... we had a use after free recently (bug 457002), that may be related. Can you try running KWin with valgrind? -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 454074] Clock missing on lock screen
https://bugs.kde.org/show_bug.cgi?id=454074 --- Comment #10 from MountainX --- (In reply to Nate Graham from comment #9) > The video in the original report depicts a valid state, so I suspect it was > caused by the same misunderstanding that other people reported in Bug > 429468, which has been resolved for Plasma 5.26 by clarifying the text in > the config window. > > If you're *never* seeing the clock on the lock screen--either when the auth > prompt is visible or also when it's not visible--that would be a different > bug. Can you file a new bug report for it? In that bug report, please run > `kscreenlocker_greet --testing` and paste the output. > > (note: if kscreenlocker_greet is not be in your $PATH, you'll have to locate > it manually) > > Thanks! Does my comment in Bug 457142 contain the info you need? I included the output of `kscreenlocker_greet --testing` (and I didn't see anything useful in there, but I'm not a dev). -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 457142] I am *never* seeing the clock on the lock screen
https://bugs.kde.org/show_bug.cgi?id=457142 --- Comment #1 from MountainX --- output of kscreenlocker_greet --testing [code] $ /usr/lib/kscreenlocker_greet --testing file:///usr/share/plasma/look-and-feel/org.kde.breeze.desktop/contents/components/VirtualKeyboard.qml:8:1: module "QtQuick.VirtualKeyboard" is not installed file:///usr/share/plasma/look-and-feel/org.kde.breeze.desktop/contents/lockscreen/LockScreenUi.qml:222: ReferenceError: wallpaper is not defined file:///usr/share/plasma/look-and-feel/org.kde.breeze.desktop/contents/components/VirtualKeyboard.qml:8:1: module "QtQuick.VirtualKeyboard" is not installed file:///usr/share/plasma/look-and-feel/org.kde.breeze.desktop/contents/lockscreen/LockScreenUi.qml:0: ReferenceError: wallpaper is not defined file:///usr/share/plasma/look-and-feel/org.kde.breeze.desktop/contents/components/VirtualKeyboard.qml:8:1: module "QtQuick.VirtualKeyboard" is not installed file:///usr/share/plasma/look-and-feel/org.kde.breeze.desktop/contents/lockscreen/LockScreenUi.qml:0: ReferenceError: wallpaper is not defined file:///usr/share/plasma/look-and-feel/org.kde.breeze.desktop/contents/components/VirtualKeyboard.qml:8:1: module "QtQuick.VirtualKeyboard" is not installed file:///usr/share/plasma/look-and-feel/org.kde.breeze.desktop/contents/lockscreen/LockScreenUi.qml:0: ReferenceError: wallpaper is not defined Locked at 1658786137 file:///usr/share/plasma/look-and-feel/org.kde.breeze.desktop/contents/components/UserList.qml:43:9: Unable to assign [undefined] to bool file:///usr/share/plasma/look-and-feel/org.kde.breeze.desktop/contents/components/UserList.qml:43:9: Unable to assign [undefined] to bool file:///usr/share/plasma/look-and-feel/org.kde.breeze.desktop/contents/components/UserList.qml:43:9: Unable to assign [undefined] to bool file:///usr/share/plasma/look-and-feel/org.kde.breeze.desktop/contents/components/UserList.qml:43:9: Unable to assign [undefined] to bool QXcbClipboard: SelectionRequest too old QXcbClipboard: SelectionRequest too old QXcbClipboard: SelectionRequest too old ... QXcbClipboard: SelectionRequest too old QXcbClipboard: SelectionRequest too old QXcbClipboard: SelectionRequest too old [/code] Sorry, can't seem to find the right method to format code here or in bugzilla.readthedocs.io -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 457142] New: I am *never* seeing the clock on the lock screen
https://bugs.kde.org/show_bug.cgi?id=457142 Bug ID: 457142 Summary: I am *never* seeing the clock on the lock screen Product: kscreenlocker Version: 5.25.0 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: davestechs...@gmail.com CC: bhus...@gmail.com Target Milestone: --- I am *never* seeing the clock on the lock screen This issue was previously discussed in Bug 454074, but my issue is slightly different from that bug. Plasma Workspace is installed from the "Extra" Arch Linux repo. All my files in /usr/share/plasma/look-and-feel/org.kde.breeze.desktop/contents/lockscreen/ appear to be original and unmodified. usr/share/plasma/look-and-feel/org.kde.breeze.desktop/contents/lockscreen/LockOsd.qml usr/share/plasma/look-and-feel/org.kde.breeze.desktop/contents/lockscreen/LockScreen.qml usr/share/plasma/look-and-feel/org.kde.breeze.desktop/contents/lockscreen/LockScreenUi.qml usr/share/plasma/look-and-feel/org.kde.breeze.desktop/contents/lockscreen/MainBlock.qml usr/share/plasma/look-and-feel/org.kde.breeze.desktop/contents/lockscreen/MediaControls.qml usr/share/plasma/look-and-feel/org.kde.breeze.desktop/contents/lockscreen/NoPasswordUnlock.qml usr/share/plasma/look-and-feel/org.kde.breeze.desktop/contents/lockscreen/config.qml usr/share/plasma/look-and-feel/org.kde.breeze.desktop/contents/lockscreen/config.xml All those files are owned by the plasma-workspace 5.25 package. My theme is Breeze Dark. My Plasma Style is Breeze Dark. Splash Screen is Breeze. The only non-standard components I'm using are: 1. Sugar Dark sddm login theme, but I have read that the login and lockscreen themes are independent. 2. the ClassiK application style, but this clock issue existed long before I ever install ClassiK. 3. Window Decorations are ClassiK. # STEPS TO REPRODUCE 1. Use Breeze Dark theme 2. In System Settings > Workspace Behavior > Screen Locking > Configure, check the box: Show [x] Clock 3. Lock the screen and look to see Clock either when the auth prompt is visible or when it's not visible. In my case, no clock is ever shown. Strangely, the issue is present on my laptop and desktop and another Arch Linux device too. OBSERVED RESULT Clock is not shown when the auth prompt is visible Clock is not shown when the auth prompt is invisible EXPECTED RESULT I used to have a clock on the lock screen. It disappeared some time ago and I don't know why. Have been trying for a long time to get it back. SOFTWARE/OS VERSIONS Arch Linux KDE Plasma Version: 5.25 KDE Frameworks Version: 5.95.0 Qt Version: 5.15.4 (built against 5.15.4) -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 415364] Setting to disable when mouse is plugged in is missing when using Libinput driver
https://bugs.kde.org/show_bug.cgi?id=415364 Ilya Rodin changed: What|Removed |Added CC||i.a.ro...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 457125] Krita 5.1.0 beta 2 git e91e5d4 : crash right after undoing a text insertion
https://bugs.kde.org/show_bug.cgi?id=457125 amyspark changed: What|Removed |Added Version|nightly build (please |5.1.0-beta1 |specify the git hash!) | -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 457125] Krita 5.1.0 beta 2 git e91e5d4 : crash right after undoing a text insertion
https://bugs.kde.org/show_bug.cgi?id=457125 amyspark changed: What|Removed |Added Keywords||regression --- Comment #3 from amyspark --- Doesn't happen on 5.0.6, marking as regression. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 457141] New: Whenever Sceen Capturing FullScreen X11 Windows Through Pipewire, video stream frozen once fully focused on window
https://bugs.kde.org/show_bug.cgi?id=457141 Bug ID: 457141 Summary: Whenever Sceen Capturing FullScreen X11 Windows Through Pipewire, video stream frozen once fully focused on window Product: kwin Version: 5.25.3 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: wayland-generic Assignee: kwin-bugs-n...@kde.org Reporter: hurricanepoo...@protonmail.com Target Milestone: --- SUMMARY Whenever I select an X11 window to screen record on OBS, the recording freezes as soon as the window becomes fullscreen. I was turned away from the obs-studio's github and pipewire's github, and I'm now reporting it to the kwin github, as both projects believe it's an issue concerning itself with kwin. Let's say I'm playing minecraft, and the game is windowed. I can select the window from the XDG desktop portal selector just fine, and in the recording, I can see my game window and everything going on inside the game. However, whenever the window I'm trying to record is fullscreen X11 window, it freezes on the first frame of being full screen. Even if I select a windowed game, then fullscreen the game, it freezes. *** NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** STEPS TO REPRODUCE 1. Launch KDE using wayland 2. Install OBS and everything needed to record on pipewire 3. Launch OBS, and selected a windowed application (I used minecraft) 4. Start Recording 5. While focused on the app, go fullscreen. 6. Stop recording 7. Observe that the recording frozen whenever gone fullscreen. OBSERVED RESULT https://gitlab.freedesktop.org/pipewire/pipewire/uploads/701b528a50e907125e3b4f4a4c17322c/2022-07-25_11-53-45.webm Pay attention to the resolution on the mangohud overlay EXPECTED RESULT For the recording to freeze whenever going fullscreen SOFTWARE/OS VERSIONS Linux/KDE Plasma: Linux 5.18.14 KDE 5.25.3 KDE Framework 5.96.0 qt5-base 5.15.5+kde+r172 qt5-wayland 5.15.5+kde+r38 ADDITIONAL INFORMATION: Here are the bug reports I previously submitted to OBS and Pipewire Pipewire: https://gitlab.freedesktop.org/pipewire/pipewire/-/issues/2598 OBS: https://github.com/obsproject/obs-studio/issues/6353 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 451028] Apps can crash in QtWayland::wl_output::handle_done() when attaching or detaching monitor on Wayland
https://bugs.kde.org/show_bug.cgi?id=451028 shashwatkhanna...@gmail.com changed: What|Removed |Added CC||shashwatkhanna...@gmail.com --- Comment #16 from shashwatkhanna...@gmail.com --- I don't know how or what happened, but this doesn't happen anymore for me. I had reported a similar bug - https://bugs.kde.org/show_bug.cgi?id=49 (which for some reason was marked as a duplicate of some X11 issue instead of this) -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 457125] Krita 5.1.0 beta 2 git e91e5d4 : crash right after undoing a text insertion
https://bugs.kde.org/show_bug.cgi?id=457125
Freya Lupen changed:
What|Removed |Added
CC||penguinflyer2...@gmail.com
--- Comment #2 from Freya Lupen ---
The top part of the backtrace from my Windows build, if it helps; I can also
confirm the same happens in 5.1.0 beta 1.
libkritaui.dll!KisShapeLayerCanvas::slotStartAsyncRepaint+0x3a3
[mysrcdir/libs/ui/flake/kis_shape_layer_canvas.cpp @ 292]
290: // by tracking the size of the image in slotImageSizeChanged()
291: uncroppedRepaintRect = repaintRect;
> 292: repaintRect =
> repaintRect.intersected(m_parentLayer->image()->bounds());
293: } else {
294: const QRectF shapesBounds =
KoShape::boundingRect(m_shapeManager->shapes());
Qt5Core.dll!QMetaObject::activate+0x828
[C:/Packaging/KritaDepsBuild/ext_qt/s/qtbase/src/corelib/kernel/qobject.cpp @
3804]
--
You are receiving this mail because:
You are watching all bug changes.
[digikam] [Bug 457137] Latest version should always have the original name
https://bugs.kde.org/show_bug.cgi?id=457137 Maik Qualmann changed: What|Removed |Added Platform|Compiled Sources|Microsoft Windows -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 457137] Latest version should always have the original name
https://bugs.kde.org/show_bug.cgi?id=457137 Maik Qualmann changed: What|Removed |Added CC||metzping...@gmail.com --- Comment #1 from Maik Qualmann --- No, I don't see it that way. A new version has an extension, not the original. Maik -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 456983] mysql.err.old grows too large (over 20 GB)
https://bugs.kde.org/show_bug.cgi?id=456983 desaparecido changed: What|Removed |Added CC||luis.davila...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[Rocs] [Bug 457140] New: APT package is still in 20.12.1 & feature request.
https://bugs.kde.org/show_bug.cgi?id=457140 Bug ID: 457140 Summary: APT package is still in 20.12.1 & feature request. Product: Rocs Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: rocs-bugs-n...@kde.org Reporter: ahmedwael...@protonmail.com Target Milestone: --- SUMMARY *** I'm on parrot os. installing via apt gives me rocs 20.12.1 and no other updates can be done. I don't know how old is this version, but JS doesn't accept "let" so I guess it''s old. *** STEPS TO REPRODUCE 1- sudo apt upgrade rocs 2- rocs -v OBSERVED RESULT 1- rocs is already the newest version (4:20.12.1-1). 2- rocs 20.12.1 SOFTWARE/OS VERSIONS Linux/KDE Plasma: (available in About System) KDE Plasma Version: 5.20.5 KDE Frameworks Version: 5.78.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION: Also I have a feature in mind. An I am willing to help in it. coding Graph theory Algorithms is hard in JS. And I'm more familiar with it in other languages. so if we can encode the graph in any file extension (I have JSON in mind but I know there are better). then we can create (wrapper classes) that can produce the data structures needed and parse the file. After that you can code in your favorite languages. I'm pretty sure I can do the python and java implementation which would help more people use this amazing tool. thanks. -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 435676] [Requested Change] There's so much space wasted in the Kirigami app.
https://bugs.kde.org/show_bug.cgi?id=435676 robloka...@gmail.com changed: What|Removed |Added Resolution|--- |NOT A BUG Status|REPORTED|RESOLVED -- You are receiving this mail because: You are watching all bug changes.
[www.kde.org] [Bug 457031] Some icons are wrong
https://bugs.kde.org/show_bug.cgi?id=457031 robloka...@gmail.com changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 454074] Clock missing on lock screen
https://bugs.kde.org/show_bug.cgi?id=454074 --- Comment #9 from Nate Graham --- The video in the original report depicts a valid state, so I suspect it was caused by the same misunderstanding that other people reported in Bug 429468, which has been resolved for Plasma 5.26 by clarifying the text in the config window. If you're *never* seeing the clock on the lock screen--either when the auth prompt is visible or also when it's not visible--that would be a different bug. Can you file a new bug report for it? In that bug report, please run `kscreenlocker_greet --testing` and paste the output. (note: if kscreenlocker_greet is not be in your $PATH, you'll have to locate it manually) Thanks! -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 457139] kwin_wayland crashes in KWin::DrmGpu::~DrmGpu() when plugging in an HDMI monitor
https://bugs.kde.org/show_bug.cgi?id=457139 Nate Graham changed: What|Removed |Added Severity|normal |crash -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 457139] New: kwin_wayland crashes in KWin::DrmGpu::~DrmGpu() when plugging in an HDMI monitor
https://bugs.kde.org/show_bug.cgi?id=457139 Bug ID: 457139 Summary: kwin_wayland crashes in KWin::DrmGpu::~DrmGpu() when plugging in an HDMI monitor Product: kwin Version: master Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: platform-drm Assignee: kwin-bugs-n...@kde.org Reporter: n...@kde.org Target Milestone: --- All KDE stuff from today's git master. STEPS TO REPRODUCE 1. Plug HDMI monitor into the HDMI port on my laptop OBSERVED RESULT kwin_wayland crashes 100% of the time in KWin::DrmGpu::~DrmGpu(): #0 0x7f131898ac86 in std::__shared_count<(__gnu_cxx::_Lock_policy)2>::~__shared_count() (this=0x1365768, __in_chrg=) at /usr/include/c++/12/bits/shared_ptr_base.h:1070 #1 std::__shared_ptr::~__shared_ptr() (this=0x1365760, __in_chrg=) at /usr/include/c++/12/bits/shared_ptr_base.h:1524 #2 std::shared_ptr::~shared_ptr() (this=0x1365760, __in_chrg=) at /usr/include/c++/12/bits/shared_ptr.h:175 #3 KWin::DrmPipeline::State::~State() (this=0x1365728, __in_chrg=) at /home/nate/kde/src/kwin/src/backends/drm/drm_pipeline.h:169 #4 KWin::DrmPipeline::~DrmPipeline() (this=0x1365600, __in_chrg=) at /home/nate/kde/src/kwin/src/backends/drm/drm_pipeline.cpp:47 #5 0x011ff8e0 in () #6 0x011df7e8 in () #7 0x7f131509d143 in __GI___libc_free (mem=0x1365600) at malloc.c:3376 #8 0x7f1318974bcd in KWin::DrmGpu::~DrmGpu() (this=0x11df7f8, __in_chrg=) at /home/nate/kde/src/kwin/src/backends/drm/drm_gpu.cpp:135 #9 0x in () This is 100% reproducible for me. -- You are receiving this mail because: You are watching all bug changes.
[kstars] [Bug 457138] New: Issue with interface in Polar alignment
https://bugs.kde.org/show_bug.cgi?id=457138 Bug ID: 457138 Summary: Issue with interface in Polar alignment Product: kstars Version: 3.5.9 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: mutla...@ikarustech.com Reporter: juandaniel.morci...@gmail.com Target Milestone: --- Created attachment 150908 --> https://bugs.kde.org/attachment.cgi?id=150908&action=edit polar alignment Hi, A couple of times, when I tried to do a Polar alignment, I´m not able to position the triangle over the star that I want. When I click with the mouse in a point of the image, triangle moves to a different part of the picture. It is like coordinates of image doesn´t match with coordinates of my mouse. If I close KStars and I start the process from 0 it works fine, so it is something that doesn´t happend all the times. I´m using Ekos (version 1.9.5 of Indi) with Astroberry in a Raspberry PI 3, and I´m using VNC to handle Ekos. I don´t have any other problem with the mouse, it only happends with the alignment picture. I´m using a ASI294 MM camera, in binning 4 mode for Polar alignment. I don´t know if it could be related with binning, because it changes the size of the image and could affect to coordinates. I also tried with binning 2 and the same results. I don´t have logs, and I´m not sure this kind of issues appears in logs. I will try to collect it next time if the error appears again. For example, in the next picture I´m not able to see the entire triangle. If I click on the rigth bottom corner, triangle moves to position you see in the image. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 155938] support for MS Word documents
https://bugs.kde.org/show_bug.cgi?id=155938 Albert Astals Cid changed: What|Removed |Added CC||aa...@kde.org Resolution|--- |FIXED Status|CONFIRMED |RESOLVED --- Comment #23 from Albert Astals Cid --- Agree with Luigi -- You are receiving this mail because: You are watching all bug changes.
[i18n] [Bug 457057] inconsistency in polish translation of the keyboard shortcut description
https://bugs.kde.org/show_bug.cgi?id=457057 Albert Astals Cid changed: What|Removed |Added CC||aa...@kde.org --- Comment #1 from Albert Astals Cid --- Can you attach a screenshot of it just to make sure of what you're talking about (i think i understand but screenshots are always clearer) -- You are receiving this mail because: You are watching all bug changes.
[kmail] [Bug 53801] Need option to specify domains when downloading external references
https://bugs.kde.org/show_bug.cgi?id=53801 Florian Lindner changed: What|Removed |Added Version|1.5 |5.18.80 -- You are receiving this mail because: You are watching all bug changes.
[kmail] [Bug 53801] Need option to specify domains when downloading external references
https://bugs.kde.org/show_bug.cgi?id=53801 Florian Lindner changed: What|Removed |Added CC||florian.lind...@xgm.de Status|RESOLVED|REOPENED Resolution|DUPLICATE |--- --- Comment #6 from Florian Lindner --- (In reply to Björn Ruberg from comment #5) > > *** This bug has been marked as a duplicate of bug 63780 *** https://bugs.kde.org/show_bug.cgi?id=63780 is about rending HTML, this bug is about loading external references. It is wrongly flagged as duplicate and should still be open. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 457137] New: Latest version should always have the original name
https://bugs.kde.org/show_bug.cgi?id=457137 Bug ID: 457137 Summary: Latest version should always have the original name Product: digikam Version: 7.8.0 Platform: Compiled Sources OS: Microsoft Windows Status: REPORTED Severity: wishlist Priority: NOR Component: Albums-Versioning Assignee: digikam-bugs-n...@kde.org Reporter: claus.peja+...@gmail.com Target Milestone: --- When using Non-Destructive Editing and Versioning, there should be an option to choose that the latest version of an image always has the original name. And the older versions should also get the file flag hidden. So, in this case, the original image is e.g., file.jpg. When a new version is created, file.jpg is moved to file01.jpg, and the new, edited one keeps the original name file.jpg. file01.jpg is then the oldest version. And when you next edit it, file02.jpg is created as backup, and again the new, edited one is file.jpg. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 457136] Transform mask causes onion skin to render incorrectly
https://bugs.kde.org/show_bug.cgi?id=457136 --- Comment #1 from thetwo --- Created attachment 150907 --> https://bugs.kde.org/attachment.cgi?id=150907&action=edit bug -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 457136] New: Transform mask causes onion skin to render incorrectly
https://bugs.kde.org/show_bug.cgi?id=457136 Bug ID: 457136 Summary: Transform mask causes onion skin to render incorrectly Product: krita Version: unspecified Platform: Other OS: Other Status: REPORTED Severity: normal Priority: NOR Component: Instant Preview Assignee: krita-bugs-n...@kde.org Reporter: thetwo...@foxmail.com Target Milestone: --- SUMMARY 5.1.0 beta2 Currently I found three ways to trigger: 1. Move the image 2. Quickly zoom the canvas 3. Leave krita for a while -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 457135] New: Transform mask causes onion skin to render incorrectly
https://bugs.kde.org/show_bug.cgi?id=457135 Bug ID: 457135 Summary: Transform mask causes onion skin to render incorrectly Product: krita Version: unspecified Platform: Other OS: Other Status: REPORTED Severity: normal Priority: NOR Component: Instant Preview Assignee: krita-bugs-n...@kde.org Reporter: thetwo...@foxmail.com Target Milestone: --- Created attachment 150906 --> https://bugs.kde.org/attachment.cgi?id=150906&action=edit bug SUMMARY 5.1.0 beta2 Currently I found three ways to trigger: 1. Move the image 2. Quickly zoom the canvas 3. Leave krita for a while -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 457134] New: discover crashes when going in to the installed tab
https://bugs.kde.org/show_bug.cgi?id=457134 Bug ID: 457134 Summary: discover crashes when going in to the installed tab Product: Discover Version: 5.24.4 Platform: Kubuntu Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: discover Assignee: plasma-b...@kde.org Reporter: geqch0...@mozmail.com CC: aleix...@kde.org Target Milestone: --- SUMMARY *** discover crashes when going in to the installed tab Application: Discover (plasma-discover), signal: Segmentation fault [KCrash Handler] #4 0x7f74981165c7 in () at /usr/lib/x86_64-linux-gnu/qt5/plugins/discover/flatpak-backend.so #5 0x7f7498123b3b in () at /usr/lib/x86_64-linux-gnu/qt5/plugins/discover/flatpak-backend.so #6 0x7f74b47a740e in QObject::event(QEvent*) () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7f74b5918713 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #8 0x7f74b4779e2a in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #9 0x7f74b477cf17 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #10 0x7f74b47d3a57 in () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #11 0x7f74b3070d1b in g_main_context_dispatch () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #12 0x7f74b30c56f8 in () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #13 0x7f74b306e3c3 in g_main_context_iteration () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #14 0x7f74b47d30a8 in QEventDispatcherGlib::processEvents(QFlags) () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #15 0x7f74b477874b in QEventLoop::exec(QFlags) () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #16 0x7f74b4780ce4 in QCoreApplication::exec() () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #17 0x557a2933d638 in () #18 0x7f74b4095d90 in __libc_start_call_main (main=main@entry=0x557a2933cd40, argc=argc@entry=1, argv=argv@entry=0x7ffdb9da4a88) at ../sysdeps/nptl/libc_start_call_main.h:58 #19 0x7f74b4095e40 in __libc_start_main_impl (main=0x557a2933cd40, argc=1, argv=0x7ffdb9da4a88, init=, fini=, rtld_fini=, stack_end=0x7ffdb9da4a78) at ../csu/libc-start.c:392 #20 0x557a2933e075 in () [Inferior 1 (process 119760) detached] *** STEPS TO REPRODUCE 1. 2. 3. OBSERVED RESULT discover crashing EXPECTED RESULT discover not crashing SOFTWARE/OS VERSIONS Operating System: Kubuntu 22.04 KDE Plasma Version: 5.24.4 KDE Frameworks Version: 5.92.0 Qt Version: 5.15.3 Kernel Version: 5.15.0-41-generic (64-bit) Graphics Platform: X11 Processors: 2 × Intel® Celeron® G4900 CPU @ 3.10GHz Memory: 7.6 GiB of RAM Graphics Processor: Mesa Intel® UHD Graphics 610 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[Bluedevil] [Bug 457131] Bluetooth: "Remember previous state" should be "Restore previous state"
https://bugs.kde.org/show_bug.cgi?id=457131 Nate Graham changed: What|Removed |Added Latest Commit||https://invent.kde.org/plas ||ma/bluedevil/commit/d663974 ||e307c23f6354fd8b40762531ba5 ||49d103 Status|REPORTED|RESOLVED Resolution|--- |FIXED Version Fixed In||5.26 --- Comment #3 from Nate Graham --- Git commit d663974e307c23f6354fd8b40762531ba549d103 by Nate Graham, on behalf of Alex Gurenko. Committed on 25/07/2022 at 19:43. Pushed by ngraham into branch 'master'. KCM: Rename "Remember" option to "Restore previous state" FIXED-IN: 5.26 M +1-1src/kcm/package/contents/ui/General.qml https://invent.kde.org/plasma/bluedevil/commit/d663974e307c23f6354fd8b40762531ba549d103 -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 456846] Kate Snippets: not clear how to work with selected text
https://bugs.kde.org/show_bug.cgi?id=456846
--- Comment #3 from Thomas Friedrichsmeier
---
But in fact, if you do not care about adding a default value, in case there is
no selection, you can simply write (snippet tab):
${view.selectedText()}
Would you like to create a merge request adding some illustrative examples?
--
You are receiving this mail because:
You are watching all bug changes.
[kdelibs] [Bug 182496] Kdelibs image format plugin kimg_psd.so is unable to open adobe cs3 psd
https://bugs.kde.org/show_bug.cgi?id=182496 Albert Astals Cid changed: What|Removed |Added Resolution|--- |FIXED Latest Commit||https://invent.kde.org/fram ||eworks/kimageformats/commit ||/6f44c5c52ac3b427327e034f0d ||145cd21b585dbf Status|REPORTED|RESOLVED --- Comment #3 from Albert Astals Cid --- Git commit 6f44c5c52ac3b427327e034f0d145cd21b585dbf by Albert Astals Cid, on behalf of Mirco Miranda. Committed on 25/07/2022 at 19:34. Pushed by aacid into branch 'master'. PSD: Improve alpha detection A +---autotests/read/psd/ccbug182496.png A +---autotests/read/psd/ccbug182496.psd M +157 -46 src/imageformats/psd.cpp M +1-1src/imageformats/psd.desktop https://invent.kde.org/frameworks/kimageformats/commit/6f44c5c52ac3b427327e034f0d145cd21b585dbf -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 423556] Battery icon sometimes indicates that battery is charging when laptop is unplugged
https://bugs.kde.org/show_bug.cgi?id=423556 Gurenko Alex changed: What|Removed |Added CC||agure...@protonmail.com -- You are receiving this mail because: You are watching all bug changes.
[krdc] [Bug 436650] [wayland] VNC connections do not work
https://bugs.kde.org/show_bug.cgi?id=436650 Bug Janitor Service changed: What|Removed |Added Status|REPORTED|ASSIGNED Ever confirmed|0 |1 --- Comment #9 from Bug Janitor Service --- A possibly relevant merge request was started @ https://invent.kde.org/network/krdc/-/merge_requests/38 -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 443980] Battery indicator on SDDM login screen always shows the battery charging icon
https://bugs.kde.org/show_bug.cgi?id=443980 Gurenko Alex changed: What|Removed |Added CC||agure...@protonmail.com -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 454074] Clock missing on lock screen
https://bugs.kde.org/show_bug.cgi?id=454074 --- Comment #8 from MountainX --- My theme is Breeze Dark. It is the standard package, not a fork. It is installed from the "Extra" Arch Linux repo. All my files in /usr/share/plasma/look-and-feel/org.kde.breeze.desktop/contents/lockscreen/ are original, unmodified. usr/share/plasma/look-and-feel/org.kde.breeze.desktop/contents/lockscreen/LockOsd.qml usr/share/plasma/look-and-feel/org.kde.breeze.desktop/contents/lockscreen/LockScreen.qml usr/share/plasma/look-and-feel/org.kde.breeze.desktop/contents/lockscreen/LockScreenUi.qml usr/share/plasma/look-and-feel/org.kde.breeze.desktop/contents/lockscreen/MainBlock.qml usr/share/plasma/look-and-feel/org.kde.breeze.desktop/contents/lockscreen/MediaControls.qml usr/share/plasma/look-and-feel/org.kde.breeze.desktop/contents/lockscreen/NoPasswordUnlock.qml usr/share/plasma/look-and-feel/org.kde.breeze.desktop/contents/lockscreen/config.qml usr/share/plasma/look-and-feel/org.kde.breeze.desktop/contents/lockscreen/config.xml All those files are owned by the plasma-workspace 5.25.3.1-1 package. The only non-standard component I'm using is an sddm login theme, but I have read that the login and lockscreen themes are independent. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 457133] New: UI Component Squished
https://bugs.kde.org/show_bug.cgi?id=457133 Bug ID: 457133 Summary: UI Component Squished Product: Discover Version: 5.25.3 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: discover Assignee: plasma-b...@kde.org Reporter: gravityfa...@pm.me CC: aleix...@kde.org Target Milestone: --- Created attachment 150905 --> https://bugs.kde.org/attachment.cgi?id=150905&action=edit Screenshot SUMMARY *** NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** STEPS TO REPRODUCE 1. Open Discover 2. Look up and right 3. OBSERVED RESULT The area at the top right of the main interface is abbreviating itself regardless of window size. This is congruent across all screens. EXPECTED RESULT non-squished-ness SOFTWARE/OS VERSIONS Linux/KDE Plasma: Arch 5.18.13-arch1-1 (available in About System) KDE Plasma Version: 5.25.3 KDE Frameworks Version: 5.96.0 Qt Version: 5.15.5 ADDITIONAL INFORMATION Using Wayland -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 453012] Wallpaper ignores global scale of 200% when a 144Hz 4K HDMI 2.1 monitor is used
https://bugs.kde.org/show_bug.cgi?id=453012 Richard Yao changed: What|Removed |Added Resolution|WORKSFORME |FIXED --- Comment #12 from Richard Yao --- (In reply to Fushan Wen from comment #9) > Could you test if > https://invent.kde.org/plasma/plasma-workspace/-/merge_requests/1781 fixes > the issue? Sorry for the late response. This appears to have fixed it. I did not test that pull request by itself, but instead tested 5.25.3, which appears to contain it. -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 455712] Non-functional "Unlock" button sometimes shown after entering correct password
https://bugs.kde.org/show_bug.cgi?id=455712 Nate Graham changed: What|Removed |Added Severity|normal |critical Summary|Unlock button even with |Non-functional "Unlock" |password user |button sometimes shown ||after entering correct ||password --- Comment #28 from Nate Graham --- With current git master, I can reproduce this issue when using fingerprint authentication (which is Bug 454706), but not normal password authentication. I tested with a single monitor as well as multiple monitors. -- You are receiving this mail because: You are watching all bug changes.
[Bluedevil] [Bug 457131] Bluetooth: "Remember previous state" should be "Restore previous state"
https://bugs.kde.org/show_bug.cgi?id=457131 --- Comment #2 from Gurenko Alex --- I'm not sure what's the procedure, but since it looks like a pretty straight forward change if others agree, I've made a MR for that here: https://invent.kde.org/plasma/bluedevil/-/merge_requests/85 -- You are receiving this mail because: You are watching all bug changes.
[Bluedevil] [Bug 457131] Bluetooth: "Remember previous state" should be "Restore previous state"
https://bugs.kde.org/show_bug.cgi?id=457131 Gurenko Alex changed: What|Removed |Added Product|systemsettings |Bluedevil Component|kcm_bluetooth |general --- Comment #1 from Gurenko Alex --- (In reply to Gurenko Alex from comment #0) > SUMMARY > > Bluetooth settings have a "On login" section that contains: > > - Enable Bluetooth > - Disable Bluetooth > - Remember previous state > > IMO last item should say: "Restore previous state" as it makes more sense > > > STEPS TO REPRODUCE > 1. > 2. > 3. > > OBSERVED RESULT > > > EXPECTED RESULT > > > SOFTWARE/OS VERSIONS > Linux/KDE Plasma: Fedora Linux 36 KDE > KDE Plasma Version: 5.25.3 > KDE Frameworks Version: 5.96 > Qt Version: 5.15.3 > > ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 457115] Changes to toolbar buttons in main toolbar are only reflected for current or new tabs but not for others until restart
https://bugs.kde.org/show_bug.cgi?id=457115 --- Comment #3 from postix --- (In reply to David Hurka from comment #2) > Nice idea, but I doubt it helps, since the old report was more specific. I felt that the other report made too much the impression, that only a specific toolbar button, namely "change color", was affected, but not necessarily others. If you think the other report was more helpful, feel free to change the bugs' relation. Whatever it takes to get it resolved. :) -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 457132] New: Touchscreen long press is mouse-right-click with Dolphin but not with Okular
https://bugs.kde.org/show_bug.cgi?id=457132 Bug ID: 457132 Summary: Touchscreen long press is mouse-right-click with Dolphin but not with Okular Product: okular Version: 22.04.3 Platform: Debian unstable OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: okular-de...@kde.org Reporter: inkbottle...@gmail.com Target Milestone: --- There has been a new functionality added to Plasma 5.25, namely long-press acting as right click on touchscreen tablet pc. On my latest Debian-sid install, this functionality is fully working with Dolphin. However it does not work with Okular (version 22.04.03). This functionality is pivotal, at least for two reason: On a tablet pc, once you've added an annotation you have no way to delete it, since it requires a right click on the annotation. Also, you can't leave fullscreen mode as described here: https://www.reddit.com/r/kde/comments/u3fm2x/getting_out_of_okular_full_screen_mode/ SOFTWARE/OS VERSIONS Linux/KDE Plasma: debian-sid plasma 5.25 kwin-wayland okular 22.04.03 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 457131] New: Bluetooth: "Remember previous state" should be "Restore previous state"
https://bugs.kde.org/show_bug.cgi?id=457131 Bug ID: 457131 Summary: Bluetooth: "Remember previous state" should be "Restore previous state" Product: systemsettings Version: 5.25.3 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: kcm_bluetooth Assignee: now...@gmail.com Reporter: agure...@protonmail.com CC: plasma-b...@kde.org Target Milestone: --- SUMMARY Bluetooth settings have a "On login" section that contains: - Enable Bluetooth - Disable Bluetooth - Remember previous state IMO last item should say: "Restore previous state" as it makes more sense STEPS TO REPRODUCE 1. 2. 3. OBSERVED RESULT EXPECTED RESULT SOFTWARE/OS VERSIONS Linux/KDE Plasma: Fedora Linux 36 KDE KDE Plasma Version: 5.25.3 KDE Frameworks Version: 5.96 Qt Version: 5.15.3 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[partitionmanager] [Bug 457109] Saving mount point to Fstab causes the system to be unbootable
https://bugs.kde.org/show_bug.cgi?id=457109 Andrius Štikonas changed: What|Removed |Added Resolution|FIXED |WAITINGFORINFO -- You are receiving this mail because: You are watching all bug changes.
[partitionmanager] [Bug 457109] Saving mount point to Fstab causes the system to be unbootable
https://bugs.kde.org/show_bug.cgi?id=457109 Andrius Štikonas changed: What|Removed |Added Status|REPORTED|NEEDSINFO Resolution|--- |FIXED --- Comment #2 from Andrius Štikonas --- . -- You are receiving this mail because: You are watching all bug changes.
[partitionmanager] [Bug 457109] Saving mount point to Fstab causes the system to be unbootable
https://bugs.kde.org/show_bug.cgi?id=457109 --- Comment #1 from Andrius Štikonas --- I need more information than that. Would it be possible for you to attach the broken fstab file? And if you still have it, the original would be useful too. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 457130] New: Bluetooth Remember Previous State on works on reboot
https://bugs.kde.org/show_bug.cgi?id=457130 Bug ID: 457130 Summary: Bluetooth Remember Previous State on works on reboot Product: systemsettings Version: 5.25.3 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: kcm_bluetooth Assignee: now...@gmail.com Reporter: agure...@protonmail.com CC: plasma-b...@kde.org Target Milestone: --- SUMMARY When Bluetooth is set to remember previous state it only saves the state on reboot, but not on shutdown STEPS TO REPRODUCE 1. Bluetooth is set to Remember previous state 2. Boot system with Bluetooth on 3. Turn off Bluetooth 4. Shutdown 5. Boot system and login OBSERVED RESULT Bluetooth is on again EXPECTED RESULT Bluetooth should be off SOFTWARE/OS VERSIONS Linux/KDE Plasma: Fedora Linux 36 KDE KDE Plasma Version: 5.23.3 KDE Frameworks Version: 5.96 Qt Version: 5.15.3 ADDITIONAL INFORMATION This actually works if instead of shutdown the system reboots, then it saves and restores the state -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 439689] Maximize effect: no more crossfade for window content
https://bugs.kde.org/show_bug.cgi?id=439689 Gurenko Alex changed: What|Removed |Added CC||agure...@protonmail.com -- You are receiving this mail because: You are watching all bug changes.
[policykit-kde-agent-1] [Bug 312325] password dialog should always move to front
https://bugs.kde.org/show_bug.cgi?id=312325 Gurenko Alex changed: What|Removed |Added CC||agure...@protonmail.com -- You are receiving this mail because: You are watching all bug changes.
