[ksysguard] [Bug 455784] Support for Pressure Stall Information from /proc in ksysguardd
https://bugs.kde.org/show_bug.cgi?id=455784 Adrian changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |UNMAINTAINED --- Comment #1 from Adrian --- ksysguardd seems like it may be deprecated in favor of ksystemstats -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 479183] No "Add to favorites" and "Remove from favorites" menu item
https://bugs.kde.org/show_bug.cgi?id=479183 Bug Janitor Service changed: What|Removed |Added Keywords||qt6 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 479167] digiKam 8.3 does not take into account the "aspect ratio" property
https://bugs.kde.org/show_bug.cgi?id=479167 --- Comment #10 from Maik Qualmann --- The AppImage is also not yet based on Qt6 and does not use the new QMultimediaPlayer. Maik -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 462860] Rectangle capture modes have wrong GUI sizing and positioning with fractional scaling
https://bugs.kde.org/show_bug.cgi?id=462860 Meinard changed: What|Removed |Added CC||meinardadr...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 407293] Remote input plugin's scrolling speed is too fast, can't be adjusted
https://bugs.kde.org/show_bug.cgi?id=407293 Quinn changed: What|Removed |Added CC||qu...@quinndt.ca Ever confirmed|0 |1 Status|REPORTED|CONFIRMED --- Comment #1 from Quinn --- I am able to reproduce. This issue is summarized well in the original report: "Precise positioning of the scroll position is extremely difficult.". This makes actually scrolling around content using KDE Connect as the only input method extremely difficult, and thus somewhat pointless. ANDROID OS: Pixel 8 Android 14 (UQ1A.231205.015) ANDROID APP VERSION: 1.29.0 (installed from the play store) DESKTOP OS: Linux Mint 21.2 Cinnamon (kernel 6.5.0) DESKTOP APP VERSION: 21.12.3-0ubuntu1 (installed from Linux Mint "Software Manager") Thank you. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 479167] digiKam 8.3 does not take into account the "aspect ratio" property
https://bugs.kde.org/show_bug.cgi?id=479167 --- Comment #9 from Peter --- (In reply to Maik Qualmann from comment #7) > Well, this is a 4:3 video with one frame in 16:9 letterbox format. A video I > created here has the same parameters, but plays correctly. I'm a little more > recent with Qt, Gilles is currently compiling to the current Qt version. I > won't be able to test it on Windows until tomorrow. > > Maik I tested in Linux Mint 21.2 and digiKam-8.3.0-20231228T113507-x86-64.appimage Here the video is displayed correctly. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 479182] Organizer features for Import from Remote Storage
https://bugs.kde.org/show_bug.cgi?id=479182 Maik Qualmann changed: What|Removed |Added CC||metzping...@gmail.com --- Comment #2 from Maik Qualmann --- What is a “remote storage” to you, an FTP/HTTP server? Or a mounted SMB share? You can add images of a mounted SMB share using “Add images” via the import tool. Maik -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 479183] New: No "Add to favorites" and "Remove from favorites" menu item
https://bugs.kde.org/show_bug.cgi?id=479183 Bug ID: 479183 Summary: No "Add to favorites" and "Remove from favorites" menu item Classification: Plasma Product: plasmashell Version: 5.91.0 Platform: Arch Linux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Application Launcher (Kickoff) Assignee: plasma-b...@kde.org Reporter: ad.liu@gmail.com CC: mikel5...@gmail.com, noaha...@gmail.com Target Milestone: 1.0 SUMMARY This seems to happen with Qt 6.7 beta. Debugging shows that in https://invent.kde.org/plasma/plasma-desktop/-/blob/384135e4c4f98b515a926440810a562404cf7639/applets/kickoff/package/contents/ui/AbstractKickoffItemDelegate.qml#L69 The `actions` arrary doesn't change after the `push` call. SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 5.91.0 KDE Frameworks Version: 5.247.0 Qt Version: 6.7.0 Kernel Version: 6.6.8-arch1-1 (64-bit) Graphics Platform: offscreen Processors: 12 × AMD Ryzen 5 5600H with Radeon Graphics Memory: 13.5 GiB of RAM Graphics Processor: AMD Radeon Graphics -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 479182] Organizer features for Import from Remote Storage
https://bugs.kde.org/show_bug.cgi?id=479182 caulier.gil...@gmail.com changed: What|Removed |Added CC||caulier.gil...@gmail.com Component|AdvancedRename-Import |Plugin-WebService-FileTrans ||fer -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 478780] Overview Animation Laggy and Low Frame Rate
https://bugs.kde.org/show_bug.cgi?id=478780 --- Comment #5 from yun...@proton.me --- The issue still exists in Beta 2 SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: Fedora Linux 40 Kinoite (available in About System) KDE Plasma Version: 5.91.0 KDE Frameworks Version: 5.247.0 Qt Version: 6.6.1 Rawhide Build: Rawhide.20231229.n.0 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 479182] Organizer features for Import from Remote Storage
https://bugs.kde.org/show_bug.cgi?id=479182 --- Comment #1 from Ritesh Raj Sarraf --- Remote Storage Import Window * https://docs.digikam.org/en/import_tools/remote_import.html Camera Device Import Window * https://docs.digikam.org/en/import_tools/camera_import.html -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 479182] New: Organizer features for Import from Remote Storage
https://bugs.kde.org/show_bug.cgi?id=479182 Bug ID: 479182 Summary: Organizer features for Import from Remote Storage Classification: Applications Product: digikam Version: 8.2.0 Platform: Appimage OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: AdvancedRename-Import Assignee: digikam-bugs-n...@kde.org Reporter: kde-b...@researchut.com Target Milestone: --- SUMMARY The Digikam Import Tool, that imports image from a Camera device is fantastic. There are options in it that nicely allow the user to define what structure the import should be like. This is very handy to organize images. Like, I can set folder structure to `yyy/` and have images be imported into correct folders. This very feature is missing in the app window, when importing from a Remote Storage. It would be very nice to have the same Image Organizer Import Window that you have for Camera Devices, to be available for Remote Storage imports as well. STEPS TO REPRODUCE 1. Import images from Remote Storage 2. The pop-up window is missing all the features I explained above. OBSERVED RESULT * The pop-up window is missing all the features I explained above. EXPECTED RESULT * The pop-up window should have same/similar features available in Camera Import window -- You are receiving this mail because: You are watching all bug changes.
[krusader] [Bug 462086] Segmentation fault when using CTRL+Left/Right on a panel with invalid path
https://bugs.kde.org/show_bug.cgi?id=462086 Nikita Melnichenko changed: What|Removed |Added Latest Commit|https://invent.kde.org/util |https://invent.kde.org/util |ities/krusader/-/commit/293 |ities/krusader/-/commit/811 |8db287f95a772792420f887dec2 |e694aef31a15ace6056742d0f13 |d88413409b |05081c73e0 --- Comment #5 from Nikita Melnichenko --- Git commit 811e694aef31a15ace6056742d0f1305081c73e0 by Nikita Melnichenko, on behalf of Pavel Karelin. Committed on 30/12/2023 at 07:26. Pushed by melnichenko into branch 'stable'. Fixed segmentation fault when using CTRL+Left/Right on a panel with invalid path FIXED: [ 462086 ] Segmentation fault when using CTRL+Left/Right on a panel with invalid path Discussion: https://invent.kde.org/utilities/krusader/-/merge_requests/117 (cherry picked from commit 2938db287f95a772792420f887dec2d88413409b) M +15 -15 app/Panel/listpanel.cpp https://invent.kde.org/utilities/krusader/-/commit/811e694aef31a15ace6056742d0f1305081c73e0 -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 412795] Wireguard set up fails with erros -settings lost
https://bugs.kde.org/show_bug.cgi?id=412795 Matt Keith changed: What|Removed |Added CC||ro...@appus.org -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 479020] Attempting to import a wireguard configuration with an invalid name leads to a misleading error message
https://bugs.kde.org/show_bug.cgi?id=479020 Matt Keith changed: What|Removed |Added CC||ro...@appus.org -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 478774] The coregrind linux syswrap does not handle fully the bpf BPF_OBJ_GET_INFO_BY_FD call which would return btf_info
https://bugs.kde.org/show_bug.cgi?id=478774 Paul Floyd changed: What|Removed |Added Assignee|gkajm...@tbaytel.net|pjfl...@wanadoo.fr -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 479181] Wish list: exact-duplicate scan based on 'uniqueHash'
https://bugs.kde.org/show_bug.cgi?id=479181 caulier.gil...@gmail.com changed: What|Removed |Added Version|unspecified |8.2.0 Component|Maintenance-Similarities|Database-Similarity CC||caulier.gil...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 479141] Graphical glitches in presentation mode
https://bugs.kde.org/show_bug.cgi?id=479141 --- Comment #4 from Doug --- I think it may be a fractional scaling related issue- with scaling set to 175% or 125%, lots of glitching. Set to 100% or 200%, no problem. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 479141] Graphical glitches in presentation mode
https://bugs.kde.org/show_bug.cgi?id=479141 --- Comment #3 from Doug --- (In reply to David Hurka from comment #1) > This reminds me of Bug 421634. > > How many screens do you have? Does it happen on all screens? Can you give > detailed information of your screen arrangement, e. g. with a screenshot of > System Settings? If you can still remember, can you describe how you have > set up this screen arrangement? > > And maybe give the output of these commands: > > echo $QT_SCREEN_SCALE_FACTORS > echo $QT_SCALE_FACTOR > > If you can access the task panel during presentation mode, or via Alt+F3 (on > KDE Plasma), you can experiment with the fullscreen setting of the > presentation window. Possible that it gives a workaround. I have two screens- one built into my laptop, and an external monitor. It happens on both screens, either when they are both in use or when I use either alone. I get no output from either of the commands you gave me. Is that exactly how I should enter them to get live output in the terminal? -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 479141] Graphical glitches in presentation mode
https://bugs.kde.org/show_bug.cgi?id=479141 --- Comment #2 from Doug --- Created attachment 164551 --> https://bugs.kde.org/attachment.cgi?id=164551=edit Screenshot showing my display settings -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 479181] New: Wish list: exact-duplicate scan based on 'uniqueHash'
https://bugs.kde.org/show_bug.cgi?id=479181 Bug ID: 479181 Summary: Wish list: exact-duplicate scan based on 'uniqueHash' Classification: Applications Product: digikam Version: unspecified Platform: Other OS: Other Status: REPORTED Keywords: efficiency, usability Severity: wishlist Priority: NOR Component: Maintenance-Similarities Assignee: digikam-bugs-n...@kde.org Reporter: ottoh...@gmail.com Target Milestone: --- SUMMARY *** The duplicate scanner should have option to find 'exact' duplicates which could be really fast without fingerprints. *** The doc, https://docs.digikam.org/en/main_window/similarity_view.html#find-duplicates, states the following: "... but it will take a long time too as it has to compare every image with any other image." The 'Images' table has a column, 'uniqueHash', which is the hash of the bits in the file. Files containing the same bits *should* have the same hashes. A simple query to find duplicate values in this column would yield a list of unqueHash's that have duplicates, which can then be used in other table(s) to retrieve the containing directory and file names. This query would be fast compared to the image comparison of similarities. Selecting this option would then disable the other similarity options on the page. I suspect that a large number of users simply want to find exact duplicates when loading files that have been stored in various places, maybe under various prior methods the user had implemented for managing their files. This could present the file exact-duplicates in a similar manner as existing duplicate finder. It's simply a modification to how those similar/exact-duplicates are found. Best regards, .. Otto Otto Hirr -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 479179] KDE Network Manager creates unusable name for wireguard and fails to save
https://bugs.kde.org/show_bug.cgi?id=479179 --- Comment #2 from Matt Keith --- Also - the reproduction steps key and ip info are all false. But it will let you save the info. I of course found https://bugs.kde.org/show_bug.cgi?id=412795 which is for the same issue after creating this one. I feel mine is more useful so I will not mark it as duplicate myself -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 479179] KDE Network Manager creates unusable name for wireguard and fails to save
https://bugs.kde.org/show_bug.cgi?id=479179 Matt Keith changed: What|Removed |Added Platform|Fedora RPMs |Neon Version|5.27.10 |5.91.0 -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 479179] KDE Network Manager creates unusable name for wireguard and fails to save
https://bugs.kde.org/show_bug.cgi?id=479179 --- Comment #1 from Matt Keith --- I was able to reproduce this on kde plasma 6 beta 2 KDE Plasma Version: 5.91.90 KDE Freameworks Version: 5.248.0 QT Version: 6.6.1 Kernel Version: 6.2.0-39-generic (64-bit) Graphics Platform: Wayland Using the live demo installer. The issue is the same - the name is invalid - and the problem is the same - you lose everything trying to save. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 479180] New: baloo sometimes fails to index content of new files; 'Mzerosize'
https://bugs.kde.org/show_bug.cgi?id=479180 Bug ID: 479180 Summary: baloo sometimes fails to index content of new files; 'Mzerosize' Classification: Frameworks and Libraries Product: frameworks-baloo Version: 5.111.0 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: major Priority: NOR Component: Baloo File Daemon Assignee: baloo-bugs-n...@kde.org Reporter: skierp...@gmail.com Target Milestone: --- SUMMARY In https://discuss.kde.org/t/how-do-i-troubleshoot-baloo/2830/3? , a user reported Baloo did not index a .flac file as a music file, commenting > I found that balooshow -x exists. When I run this for files that are > shown in Elisa I get the line Property Terms: Maudio Mflac T2 whereas > the files that aren’t showing in Elisa have the line Property Terms: > Mapplication > Moctet Mstream. I have not experienced that, but I have noticed that baloo sometimes does not index the contents of text files. A few times when I create a text file (on both btrfs file system and an NTFS partition mounted in Linux with the ntfs-3g FUSE file system), I noticed that its contents aren't indexed, and `balooshow -x ` shows XAttr Terms: Plain Text Terms: Property Terms: Mapplication Mx Mzerosize i.e. no words in the file were indexed, and note the Mzerosize. The latter comes from baloo/src/file/basicindexingjob.cpp when filePathToStat() believes statBuf.st_size == 0. But the file is definitely non-zero length and baloo should have indexed its words. These two cases may be unrelated, but in both it seems that baloo sometimes indexes a file when its contents aren't fully present. And in the second case, it seems `balooctl index ` fails to fix the problem and index the file contents; you have to `balooctl clear ` first. STEPS TO REPRODUCE 0. Run `balooctl monitor` in a second terminal window 1. Somewhere in a GUI, enter a unique word like "flamablama", and copy it. 2. I used the Wayland command-line utility wl-paste in the terminal command `wl-paste > /path/to/file.txt` 3. Run the terminal command `balooshow -x /path/to/file.txt` 4. Run the terminal command `baloosearch flamablama` 5. Run the terminal command `balooct index /path/to/file.txt` 6. Repeat steps 3 and 4. 7. Repeat the steps but instead create the text file in a text editor like vim. OBSERVED RESULT Sometimes, balooctl monitor shows Indexing new files Idle without displaying "Indexing: /path/to/file.txt: Ok", and balooshow output includes Internal Info File Name Terms: Ffile Ftxt XAttr Terms: Plain Text Terms: Property Terms: Mapplication Mx Mzerosize , and baloosearch does not return the new file. When indexing fails in this way, the manual forced indexing of the file `balooctl index /path/to/file.txt` step prints Indexing /path/to/file.txt File(s) indexed but the file's contents remain unknown to baloo. The second `balooshow -x /path/to/file.txt` prints slightly different metadata: Plain Text Terms: Property Terms: Mplain Mtext T5 T8 The meta attribute Mzerosize is gone and baloo detected the mime type correctly (now text/plain, not x/application), but baloo still did not index the file contents. When I create new files in the `vim` file editor, baloo seems to reliably index their contents. EXPECTED RESULT Baloo should reliably index new files. `balooctl index` should actually index a file's current contents, even if you don't clear it from the index first. SOFTWARE/OS VERSIONS Linux/KDE Plasma: KDE Plasma Version: 5.27.0 KDE Frameworks Version: 5.111.0 Qt Version: 5.15.11 on Wayland ADDITIONAL INFORMATION _IF_ you notice this, the fix is to run `balooctl clear /path/to/file.txt` then `balooctl index /path/to/file.txt`. I turned on kf.baloo and kf.filemetadata debug output and did not see anything useful in `journalctl` output. I don't know if this is a file system issue; maybe Qt's filePathToStat() is caching file info. -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 478522] application menu doesnt open when i press on it and when i use the super key
https://bugs.kde.org/show_bug.cgi?id=478522 --- Comment #4 from Bug Janitor Service --- Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 477411] Youtube video in chrome started playing when laptop awakened on lock screen
https://bugs.kde.org/show_bug.cgi?id=477411 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.
[kwin] [Bug 477480] Prevent monitors, widgets, and windows from re-arranging themselves when adding/removing a monitor.
https://bugs.kde.org/show_bug.cgi?id=477480 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.
[dolphin] [Bug 477699] Yet Another Dolphin Crash
https://bugs.kde.org/show_bug.cgi?id=477699 Bug Janitor Service changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|BACKTRACE |WORKSFORME --- Comment #4 from Bug Janitor Service --- This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 478497] With Nvidia GPU, adjacent side-tiled windows flicker when resizing them both
https://bugs.kde.org/show_bug.cgi?id=478497 --- Comment #3 from Bug Janitor Service --- Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 478251] kwin_wayland with nvidia 545 driver drops user back to login after a few seconds
https://bugs.kde.org/show_bug.cgi?id=478251 --- Comment #4 from Bug Janitor Service --- Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 479179] New: KDE Network Manager creates unusable name for wireguard and fails to save
https://bugs.kde.org/show_bug.cgi?id=479179 Bug ID: 479179 Summary: KDE Network Manager creates unusable name for wireguard and fails to save Classification: Plasma Product: plasma-nm Version: 5.27.10 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: applet Assignee: plasma-b...@kde.org Reporter: ro...@appus.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 Network Connections 2. Click Add New Connection 3. Pick Wireguard 4. Click Create Note default Connection Name ‘New wireguard connection’ Populate the following fields Wireguard Interface Private key: WD3tC88Km+Kuh8aXgzT8aDF4tj4ULD1pRbqZYkiiyVA= Click Peers Public key: udgr1rvvd/hk6kX2f8LCewlFB/OknvXYPeOH4IKiSXk= Allowed Ips: 192.168.3.1/32,192.168.3.2/32,0.0.0.0/0 Endpoint address: 70.1.123.123 Endpoint port: 51820 This password is not required Persistent keepalive: 25 Press Ok IPv4 Method: Manual DNS Servers: 192.168.3.1 Click +Add for Address Address: 192.168.3.2 Netmask: 255.255.255.255 Gateway: 192.168.3.1 Check IPv4 is required for this connection Click Save OBSERVED RESULT The window closes and an error notification pops up briefly with an error EXPECTED RESULT Either detect the error in the name and flag it, preventing you from saving OR The VPN connection should save. I'm not sure why the default name is not allowed or what can be done to allow it. I think the name should work with spaces if at all possible. If not - set a sensible default that replaces spaces with hyphens SOFTWARE/OS VERSIONS Operating System: Fedora Linux 39 KDE Plasma Version: 5.27.10 KDE Frameworks Version: 5.111.0 Qt Version: 5.15.11 Kernel Version: 6.6.8-200.fc39.x86_64 (64-bit) Graphics Platform: Wayland Processors: 20 × 12th Gen Intel® Core™ i7-1280P Memory: 62.5 GiB of RAM Graphics Processor: AMD Radeon RX 5700 Manufacturer: Framework Product Name: Laptop (12th Gen Intel Core) System Version: A8 ADDITIONAL INFORMATION The error is a bad experience because 1) it's too quick to make a note of. and 2) you lose your work of entering all of your details as it fails to save at all. -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 479178] New: xwaylandvideobridge doesn't work, shares white/black screen
https://bugs.kde.org/show_bug.cgi?id=479178 Bug ID: 479178 Summary: xwaylandvideobridge doesn't work, shares white/black screen Classification: I don't know Product: kde Version: unspecified Platform: Arch Linux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: tomy.b...@gmail.com Target Milestone: --- SUMMARY *** The screen shared is just white or black Discord -> flatpak Xwayland bridge -> pacman and flatpak (kdeapps) *** STEPS TO REPRODUCE 1. Install discord 2. Install xwaylandvideobridge 3. Try to share screen through discord 4. Select A screen in the system popup 5. Select video bridge in discord 6. Nothing is shared OBSERVED RESULT White/Black screen is shared, if using the flatpak version, for me the pacman version just crashed. EXPECTED RESULT Screen is being shared SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 5.27.10 KDE Frameworks Version: 5.113.0 Qt Version: 5.15.11 Kernel Version: 6.6.8-zen1-1-zen (64-bit) Graphics Platform: Wayland Processors: 12 × Intel® Core™ i5-10400F CPU @ 2.90GHz Memory: 15.6 GiB of RAM Graphics Processor: NVIDIA GeForce RTX 2060/PCIe/SSE2 Manufacturer: Micro-Star International Co., Ltd. Product Name: MS-7C88 System Version: 1.0 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 479088] Can't disable G-Sync on Wayland.
https://bugs.kde.org/show_bug.cgi?id=479088 Zamundaaa changed: What|Removed |Added CC||xaver.h...@gmail.com Status|REPORTED|NEEDSINFO Resolution|--- |WAITINGFORINFO --- Comment #1 from Zamundaaa --- Please attach the output of drm_info -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 478878] [Feature Request] Allow creating a duplicated timeline
https://bugs.kde.org/show_bug.cgi?id=478878 Bernd changed: What|Removed |Added CC||bern...@yahoo.com Summary|Allow creating a duplicated |[Feature Request] Allow |timeline|creating a duplicated ||timeline -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 479168] De-saturated Colors in HDR Mode
https://bugs.kde.org/show_bug.cgi?id=479168 --- Comment #3 from Zamundaaa --- As a shot in the dark, could you check the output of drm_info on your system? Just to make sure the colorspace metadata is set properly -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 479177] Cutting and pasting to NFS shares causes the app to freeze up until it finishes
https://bugs.kde.org/show_bug.cgi?id=479177 Bug Janitor Service changed: What|Removed |Added Keywords||qt6 -- You are receiving this mail because: You are watching all bug changes.
[kio-extras] [Bug 477342] thumbnail kioworker crashes
https://bugs.kde.org/show_bug.cgi?id=477342 Nicolas Fella changed: What|Removed |Added Status|CONFIRMED |RESOLVED Resolution|--- |UPSTREAM --- Comment #6 from Nicolas Fella --- Fixed with https://codereview.qt-project.org/c/qt/qtbase/+/524301 -- You are receiving this mail because: You are watching all bug changes.
[kamoso] [Bug 469137] MKV is a dinosaur format from the 1990's.
https://bugs.kde.org/show_bug.cgi?id=469137 --- Comment #5 from Improv Much --- https://www.howtogeek.com/680690/how-to-install-free-hevc-codecs-on-windows-10-for-h265-video/ https://en.wikipedia.org/wiki/Video_codec The most popular video coding standards used for codecs have been the MPEG standards. MPEG-1 was developed by the Motion Picture Experts Group (MPEG) in 1991, and it was designed to compress VHS-quality video. It was succeeded in 1994 by MPEG-2/H.262,[5] which was developed by a number of companies, primarily Sony, Thomson and Mitsubishi Electric.[7] MPEG-2 became the standard video format for DVD and SD digital television.[5] In 1999, it was followed by MPEG-4/H.263, which was a major leap forward for video compression technology.[5] It was developed by a number of companies, primarily Mitsubishi Electric, Hitachi and Panasonic.[8] The most widely used video coding format, as of 2016, is H.264/MPEG-4 AVC. It was developed in 2003 by a number of organizations, primarily Panasonic, Godo Kaisha IP Bridge and LG Electronics.[9] H.264 is the main video encoding standard for Blu-ray Discs, and is widely used by streaming internet services such as YouTube, Netflix, Vimeo, and iTunes Store, web software such as Adobe Flash Player and Microsoft Silverlight, and various HDTV broadcasts over terrestrial and satellite television. AVC has been succeeded by HEVC (H.265), developed in 2013. It is heavily patented, with the majority of patents belonging to Samsung Electronics, GE, NTT and JVC Kenwood.[10][11] The adoption of HEVC has been hampered by its complex licensing structure. HEVC is in turn succeeded by Versatile Video Coding (VVC). There are also the open and free VP8, VP9 and AV1 video coding formats, used by YouTube, all of which were developed with involvement from Google. -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 479143] Issue with theming on certain applications
https://bugs.kde.org/show_bug.cgi?id=479143 johndoe1352...@outlook.com changed: What|Removed |Added Resolution|--- |FIXED Status|REPORTED|RESOLVED --- Comment #2 from johndoe1352...@outlook.com --- Resolved. Was missing kf6-qqc2-desktop-style. -- You are receiving this mail because: You are watching all bug changes.
[kamoso] [Bug 469137] MKV is a dinosaur format from the 1990's.
https://bugs.kde.org/show_bug.cgi?id=469137 Improv Much changed: What|Removed |Added CC||thelifeandtimesof.org@gmail ||.com --- Comment #4 from Improv Much --- Created attachment 164550 --> https://bugs.kde.org/attachment.cgi?id=164550=edit There is a Simple Solution - Dump the Program Kamoso - being locked into MKV - no one and nothing uses it. I dunno - if I was to look up formats, that have been uploaded and are on the internet, there might be 100 trillion billion videos in MP4 and only 100 videos in MKV. While MKV is an excellent compression format - no one uses it, non of the platforms accept it, and no browsers run it. What part of "This is an unuseable format" don't you understand? Best solution - if your not UPGRADING the program, I can record all my videos on my Android phone, and compress them down using "OPEN SHOT" - so I get comparable video quality, at 1/3rd to 1/5th the file size and upload these videos And MKV is one user less, to going into oblivion forever. To be forgotten forever as it fades into the mists of time. Don't believe me, look at all the mobile phone proprietary video and audio formats that have come and gone... And no one has codecs for them any more. MKV is only one or two steps behind all of them - and it's gone for ever. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 479154] Cursor does not scale with output scale (Wayland, Plasma 6)
https://bugs.kde.org/show_bug.cgi?id=479154 Zamundaaa changed: What|Removed |Added Status|REPORTED|NEEDSINFO CC||xaver.h...@gmail.com Resolution|--- |WAITINGFORINFO --- Comment #1 from Zamundaaa --- Can't reproduce. Is this in a VM or on bare metal? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 479168] De-saturated Colors in HDR Mode
https://bugs.kde.org/show_bug.cgi?id=479168 --- Comment #2 from Simon Berz --- (In reply to Zamundaaa from comment #1) > Does your monitor have something where it shows information about the > inputs? What you're describing sounds a lot like it thinks it's getting > rec.709 content Unfortunately not. It only shows port, resolution, and refresh rate. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 479168] De-saturated Colors in HDR Mode
https://bugs.kde.org/show_bug.cgi?id=479168 Zamundaaa changed: What|Removed |Added CC||xaver.h...@gmail.com --- Comment #1 from Zamundaaa --- With rec.2020 content (like mpv with the Vulkan layer), the gamut mapping matrix is an identity matrix, so gamut mapping shouldn't be an issue. Does your monitor have something where it shows information about the inputs? What you're describing sounds a lot like it thinks it's getting rec.709 content -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 479177] Cutting and pasting to NFS shares causes the app to freeze up until it finishes
https://bugs.kde.org/show_bug.cgi?id=479177 techxga...@outlook.com changed: What|Removed |Added OS|Other |Linux Platform|Other |Neon -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 479177] New: Cutting and pasting to NFS shares causes the app to freeze up until it finishes
https://bugs.kde.org/show_bug.cgi?id=479177 Bug ID: 479177 Summary: Cutting and pasting to NFS shares causes the app to freeze up until it finishes Classification: Applications Product: dolphin Version: 24.01.85 Platform: Other OS: Other Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: techxga...@outlook.com CC: kfm-de...@kde.org Target Milestone: --- SUMMARY When cutting or copying to NFS shares, Dolphin freezes up until the transfer is done STEPS TO REPRODUCE 1. Drag and drop file (around 1GB) to a directory in an NFS drive 2. Open a new tab in Dolphin OBSERVED RESULT It appears to happen when it's being transferred TO an NFS directory, but not FROM an NFS directory. EXPECTED RESULT Dolphin shouldn't lock up SOFTWARE/OS VERSIONS Operating System: KDE neon Unstable Edition KDE Plasma Version: 5.91.90 KDE Frameworks Version: 5.248.0 Qt Version: 6.6.1 Kernel Version: 6.6.8-2-liquorix-amd64 (64-bit) Graphics Platform: Wayland Processors: 8 × AMD EPYC-Milan Processor Memory: 7.8 GiB of RAM Graphics Processor: NVIDIA GeForce RTX 3060 Ti/PCIe/SSE2 Manufacturer: QEMU Product Name: Standard PC (Q35 + ICH9, 2009) System Version: pc-q35-6.0 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 479176] Bitwarden and Private Internet Access aren't launching
https://bugs.kde.org/show_bug.cgi?id=479176 Bug Janitor Service changed: What|Removed |Added Keywords||qt6 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 479176] New: Bitwarden and Private Internet Access aren't launching
https://bugs.kde.org/show_bug.cgi?id=479176 Bug ID: 479176 Summary: Bitwarden and Private Internet Access aren't launching Classification: Plasma Product: kwin Version: git master Platform: Other OS: Other Status: REPORTED Severity: normal Priority: NOR Component: wayland-generic Assignee: kwin-bugs-n...@kde.org Reporter: techxga...@outlook.com Target Milestone: --- SUMMARY Both Bitwarden and Private Internet Access aren't launching at all. STEPS TO REPRODUCE Bitwarden 1. Install Bitwarden from the Snap store 2. Launch Private Internet Access 1. Launch Private Internet Access from launcher OBSERVED RESULT EXPECTED RESULT Both apps should launch SOFTWARE/OS VERSIONS Operating System: KDE neon Unstable Edition KDE Plasma Version: 5.91.90 KDE Frameworks Version: 5.248.0 Qt Version: 6.6.1 Kernel Version: 6.6.8-2-liquorix-amd64 (64-bit) Graphics Platform: Wayland Processors: 8 × AMD EPYC-Milan Processor Memory: 7.8 GiB of RAM Graphics Processor: NVIDIA GeForce RTX 3060 Ti/PCIe/SSE2 Manufacturer: QEMU Product Name: Standard PC (Q35 + ICH9, 2009) System Version: pc-q35-6.0 ADDITIONAL INFORMATION Bitwarden issue: https://github.com/bitwarden/clients/issues/7400 As for PIA, the VPN functionality works, and autostarting will put the app on the system tray, but the app itself isn't launching -- You are receiving this mail because: You are watching all bug changes.
[kdeplasma-addons] [Bug 479152] Plasma crashes when no data were found by weather widget
https://bugs.kde.org/show_bug.cgi?id=479152 Nicolas Fella changed: What|Removed |Added CC||nicolas.fe...@gmx.de --- Comment #3 from Nicolas Fella --- #0 0x7f34010969fc __pthread_kill_implementation (libc.so.6 + 0x969fc) #1 0x7f3401042476 __GI_raise (libc.so.6 + 0x42476) #2 0x7f34041123ce _ZN6KCrash19defaultCrashHandlerEi (libKF6Crash.so.6 + 0x83ce) #3 0x7f3401042520 __restore_rt (libc.so.6 + 0x42520) #4 0x7f34010969fc __pthread_kill_implementation (libc.so.6 + 0x969fc) #5 0x7f3401042476 __GI_raise (libc.so.6 + 0x42476) #6 0x7f34010287f3 __GI_abort (libc.so.6 + 0x287f3) #7 0x7f3401cd8417 _Z6qAbortv (libQt6Core.so.6 + 0x4d8417) #8 0x7f3401cd38c5 n/a (libQt6Core.so.6 + 0x4d38c5) #9 0x7f3401cd8e43 _ZNK14QMessageLogger5fatalEPKcz (libQt6Core.so.6 + 0x4d8e43) #10 0x7f3401ca6f14 _Z9qt_assertPKcS0_i (libQt6Core.so.6 + 0x4a6f14) #11 0x7f33e0800758 n/a (plasma_engine_dwd.so + 0x8758) #12 0x7f33e080be7c _ZN6DWDIon24forecast_slotJobFinishedEP4KJob (plasma_engine_dwd.so + 0x13e7c) #13 0x7f3401c2767e n/a (libQt6Core.so.6 + 0x42767e) #14 0x7f340279bb50 _ZN4KJob6resultEPS_NS_14QPrivateSignalE (libKF6CoreAddons.so.6 + 0x74b50) #15 0x7f340279f91b n/a (libKF6CoreAddons.so.6 + 0x7891b) #16 0x7f3401c2767e n/a (libQt6Core.so.6 + 0x42767e) #17 0x7f3401371915 n/a (libKF6KIOCore.so.6 + 0x125915) #18 0x7f340136e4a3 n/a (libKF6KIOCore.so.6 + 0x1224a3) #19 0x7f340136d81a n/a (libKF6KIOCore.so.6 + 0x12181a) #20 0x7f3401c2767e n/a (libQt6Core.so.6 + 0x42767e) #21 0x7f3401bc8782 _ZN7QObject5eventEP6QEvent (libQt6Core.so.6 + 0x3c8782) #22 0x7f3403bf1bcb _ZN19QApplicationPrivate13notify_helperEP7QObjectP6QEvent (libQt6Widgets.so.6 + 0x5f1bcb) #23 0x7f3401c5fd88 _ZN16QCoreApplication15notifyInternal2EP7QObjectP6QEvent (libQt6Core.so.6 + 0x45fd88) #24 0x7f3401c604a0 _ZN23QCoreApplicationPrivate16sendPostedEventsEP7QObjectiP11QThreadData (libQt6Core.so.6 + 0x4604a0) #25 0x7f3401b079f7 n/a (libQt6Core.so.6 + 0x3079f7) #26 0x7f340038ad3b g_main_context_dispatch (libglib-2.0.so.0 + 0x55d3b) #27 0x7f34003e0258 n/a (libglib-2.0.so.0 + 0xab258) #28 0x7f34003883e3 g_main_context_iteration (libglib-2.0.so.0 + 0x533e3) #29 0x7f3401b05790 _ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE (libQt6Core.so.6 + 0x305790) #30 0x7f3401c61fbb _ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE (libQt6Core.so.6 + 0x461fbb) #31 0x7f3401c63bec _ZN16QCoreApplication4execEv (libQt6Core.so.6 + 0x463bec) #32 0x55ad6bbf7964 n/a (plasmashell + 0x3a964) #33 0x7f3401029d90 __libc_start_call_main (libc.so.6 + 0x29d90) #34 0x7f3401029e40 __libc_start_main_impl (libc.so.6 + 0x29e40) #35 0x55ad6bbf7bf5 n/a (plasmashell + 0x3abf5) -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 479140] Plasma crashed when i removed weather widget
https://bugs.kde.org/show_bug.cgi?id=479140 Nicolas Fella changed: What|Removed |Added CC||nicolas.fe...@gmx.de Resolution|--- |DUPLICATE Status|REPORTED|RESOLVED --- Comment #1 from Nicolas Fella --- *** This bug has been marked as a duplicate of bug 400835 *** -- You are receiving this mail because: You are watching all bug changes.
[frameworks-plasma] [Bug 400835] Plasmashell crashed in PlasmaQuick::AppletQuickItem::~AppletQuickItem() after changing Weather Report settings
https://bugs.kde.org/show_bug.cgi?id=400835 Nicolas Fella changed: What|Removed |Added CC||mashrafe...@gmail.com --- Comment #18 from Nicolas Fella --- *** Bug 479140 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kdeplasma-addons] [Bug 462548] Weather widgets shows non-sensible data values (3276, 3277, 3276.69)
https://bugs.kde.org/show_bug.cgi?id=462548 Ismael Asensio changed: What|Removed |Added Version Fixed In||5.91.90 Resolution|--- |FIXED Latest Commit||https://invent.kde.org/plas ||ma/plasma-workspace/-/commi ||t/79cd057de1649b417234852d6 ||c665d87f958bf22 Status|ASSIGNED|RESOLVED --- Comment #5 from Ismael Asensio --- Git commit 79cd057de1649b417234852d6c665d87f958bf22 by Ismael Asensio. Committed on 29/12/2023 at 18:30. Pushed by iasensio into branch 'master'. dataengines/weather: Fix error values showing for DWD The DWD provider uses a value of 32767 (0x7fff or 0b111) to mark some measurements as invalid. Instead of passing those values down to the DataEngine and the UI, detect and invalidate them while parsing the source information. FIXED-IN: 5.91.90 M +31 -39 dataengines/weather/ions/dwd/ion_dwd.cpp M +1-1dataengines/weather/ions/dwd/ion_dwd.h https://invent.kde.org/plasma/plasma-workspace/-/commit/79cd057de1649b417234852d6c665d87f958bf22 -- You are receiving this mail because: You are watching all bug changes.
[isoimagewriter] [Bug 479139] The last block was not fully written (-1 of 1,048,576 bytes)! Aborting.
https://bugs.kde.org/show_bug.cgi?id=479139 Nicolas Fella changed: What|Removed |Added Product|kde |isoimagewriter Component|general |general CC||nicolas.fe...@gmx.de Assignee|unassigned-b...@kde.org |j...@jriddell.org -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 479150] Neon Unstable Plasma 6 still does NOT have Display Auto-Rotate option
https://bugs.kde.org/show_bug.cgi?id=479150 --- Comment #2 from RossDv8 --- (In reply to Tobias Fella from comment #1) > > *** This bug has been marked as a duplicate of bug 479149 *** Can you delete ONE of these please. Last time I reported a bug was ten years ago. Somehow I accidentally saved 470150 after I submitted 479149 - resulting in a duplicate submission, and could not see where to delete one of them. So the problem, at least in KDE Plasma 6 Beta 2 (https://files.kde.org/neon/images/unstable/20231224-1120/neon-unstable-20231224-1120.iso) with system updates at 29/12/23 was not resolved. gawkand iio-sensor-proxy were still missing from the .iso installation. meaning the option to Rotate the Display Automatically was still Not available until after they were manually installed, and the system Rebooted . . -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 479167] digiKam 8.3 does not take into account the "aspect ratio" property
https://bugs.kde.org/show_bug.cgi?id=479167 --- Comment #8 from caulier.gil...@gmail.com --- Yes and compilation have been restarted one time as now the full build capacity is up to 250Gb. I extended the VM disk to 350Gb... Gilles -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 479167] digiKam 8.3 does not take into account the "aspect ratio" property
https://bugs.kde.org/show_bug.cgi?id=479167 --- Comment #7 from Maik Qualmann --- Well, this is a 4:3 video with one frame in 16:9 letterbox format. A video I created here has the same parameters, but plays correctly. I'm a little more recent with Qt, Gilles is currently compiling to the current Qt version. I won't be able to test it on Windows until tomorrow. Maik -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 418555] Discover gets stuck at "Fetching updates..." and shows an error message related to fwupd
https://bugs.kde.org/show_bug.cgi?id=418555 Sam Piper changed: What|Removed |Added Platform|Arch Linux |Kubuntu Version|unspecified |5.24.7 Status|RESOLVED|REOPENED Resolution|FIXED |--- --- Comment #3 from Sam Piper --- This error started to appear about two weeks ago. It is consistent on every launch of discover. The service cannot activate and will time out after 25s. Then discover appears to function normally. Troubleshooting fwupd using systemd or any command using fwupdmgr also reproduces the error. => $ journalctl -xeu fwupd-refresh.service The process' exit code is 'exited' and its exit status is 1. Dec 29 14:42:36 thelio76 systemd[1]: fwupd-refresh.service: Failed with result 'exit-code'. Subject: Unit failed Defined-By: systemd Support: http://www.ubuntu.com/support The unit fwupd-refresh.service has entered the 'failed' state with result 'exit-code'. Dec 29 14:42:36 thelio76 systemd[1]: Failed to start Refresh fwupd metadata and update motd. Subject: A start job for unit fwupd-refresh.service has failed Defined-By: systemd Support: http://www.ubuntu.com/support My System - Operating System: Kubuntu 22.04 KDE Plasma Version: 5.24.7 KDE Frameworks Version: 5.98.0 Qt Version: 5.15.3 Kernel Version: 6.6.6-76060606-generic (64-bit) Graphics Platform: X11 Processors: 32 × AMD Ryzen 9 7950X 16-Core Processor Memory: 62.0 GiB of RAM Graphics Processor: NVIDIA GeForce RTX 3060/PCIe/SSE2 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kirigami] [Bug 479175] pageStack.push() does not show the pushed page when using QT_QUICK_CONTROLS_MOBILE=1
https://bugs.kde.org/show_bug.cgi?id=479175 Bug Janitor Service changed: What|Removed |Added Keywords||qt6 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 479167] digiKam 8.3 does not take into account the "aspect ratio" property
https://bugs.kde.org/show_bug.cgi?id=479167 --- Comment #6 from Peter --- Actually I don't know if this is a fault. digiKam 8.2 and smplayer have so far displayed (aspect ratio 16:9) the videos correctly even though the size is 704x576 I may have to use "ffmpeg -s 1024x576 -aspect 16:9" switch for real 16:9 videos going forward. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 418555] Discover gets stuck at "Fetching updates..." and shows an error message related to fwupd
https://bugs.kde.org/show_bug.cgi?id=418555 Sam Piper changed: What|Removed |Added CC||spiperman...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kirigami] [Bug 436493] Some pages on pageStack still remain visible and active after having been popped or cleared
https://bugs.kde.org/show_bug.cgi?id=436493 --- Comment #1 from b...@mogwai.be --- It seems like this bug is solved with qt 6.6.1. It's still happening with the latest qt5 though. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 353471] memcheck/tests/x86/xor-undef-x86 fails on OS X 10.11
https://bugs.kde.org/show_bug.cgi?id=353471 --- Comment #3 from Paul Floyd --- the opcode is pinsrd, see https://bugs.kde.org/show_bug.cgi?id=282910 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kirigami] [Bug 479175] New: pageStack.push() does not show the pushed page when using QT_QUICK_CONTROLS_MOBILE=1
https://bugs.kde.org/show_bug.cgi?id=479175 Bug ID: 479175 Summary: pageStack.push() does not show the pushed page when using QT_QUICK_CONTROLS_MOBILE=1 Classification: Frameworks and Libraries Product: frameworks-kirigami Version: Master Platform: Compiled Sources OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kdelibs-b...@kde.org Reporter: b...@mogwai.be CC: m...@ratijas.tk, notm...@gmail.com Target Milestone: Not decided 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 a kirigami app with QT_QUICK_CONTROLS_MOBILE=1 (e.g. Kasts, Tokodon) 2. Push a new page to the pageStack, e.g. by clicking on an item OBSERVED RESULT The new page will be pushed onto the stack, but will not be visible. It will only become visible after swiping the original page to the left. This happens with both qqc2-desktop-style and qqc2-breeze-style. It only happens when QT_QUICK_CONTROLS_MOBILE=1. EXPECTED RESULT The view changes to the pushed page, just like it is when QT_QUICK_CONTROLS_MOBILE hasn't been set. SOFTWARE/OS VERSIONS KDE Frameworks Version: compiled from master (with kdesrc-build) Qt Version: 6.6.1 (from arch packages) -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 479167] digiKam 8.3 does not take into account the "aspect ratio" property
https://bugs.kde.org/show_bug.cgi?id=479167 --- Comment #5 from Peter --- (In reply to Peter from comment #4) > (In reply to Maik Qualmann from comment #3) > > Hmm, I can't reproduce any problems here with "real" 16:9 videos. Your video > > is 704x576 = 11:9 (1.2). This means that the square representation is > > actually correct. Why there is an aspect ratio of 1.77 in the metadata is a > > mystery to me at this point. We would have to scale your video by a factor > > of 1.4545 in width, but that is not logical given the video size. > > > > Otherwise we would have to assume a height of around 396 pixels, the rest > > are black borders. Where is the video from? Is this from a 4:3 (DVD/DV) > > recorder that has recorded in 16:9 mode? Something is wrong here. > > > > Maik > > I converted this video(s) from 4:3 to 16:9 using ffmpeg. > ffmpeg has a switch that adjusts the display aspect ratio. > > Video it was converted with this command: > ffmpeg -i [input file] -aspect 16/9 -c:v h264_nvenc -preset slow [output > file] ffmpeg -i [input file] -aspect 16:9 -c:v h264_nvenc -preset slow [output file] -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 479167] digiKam 8.3 does not take into account the "aspect ratio" property
https://bugs.kde.org/show_bug.cgi?id=479167 --- Comment #4 from Peter --- (In reply to Maik Qualmann from comment #3) > Hmm, I can't reproduce any problems here with "real" 16:9 videos. Your video > is 704x576 = 11:9 (1.2). This means that the square representation is > actually correct. Why there is an aspect ratio of 1.77 in the metadata is a > mystery to me at this point. We would have to scale your video by a factor > of 1.4545 in width, but that is not logical given the video size. > > Otherwise we would have to assume a height of around 396 pixels, the rest > are black borders. Where is the video from? Is this from a 4:3 (DVD/DV) > recorder that has recorded in 16:9 mode? Something is wrong here. > > Maik I converted this video(s) from 4:3 to 16:9 using ffmpeg. ffmpeg has a switch that adjusts the display aspect ratio. Video it was converted with this command: ffmpeg -i [input file] -aspect 16/9 -c:v h264_nvenc -preset slow [output file] -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 353471] memcheck/tests/x86/xor-undef-x86 fails on OS X 10.11
https://bugs.kde.org/show_bug.cgi?id=353471 --- Comment #2 from Paul Floyd --- If I get past the assert then I just get vex x86->IR: unhandled instruction bytes: 0x66 0xF 0x3A 0x22 ==19671== valgrind: Unrecognised instruction at address 0x18038d. ==19671==at 0x18038D: ??? (in /usr/lib/system/libdispatch.dylib) which is an unsupported (on x86) sse4 instruction. I'll probably mark this as wontfix as we're not going to add sse4 to x86 and macOS dropped x86 with 10.15 Catalina in 2019. -- You are receiving this mail because: You are watching all bug changes.
[kamoso] [Bug 469137] MKV is a dinosaur format from the 1990's.
https://bugs.kde.org/show_bug.cgi?id=469137 Erin Yuki Schlarb changed: What|Removed |Added CC||erin-kde@ninetailed.ninja --- Comment #3 from Erin Yuki Schlarb --- > Are you confusing mkv with something else? Really sounds like they confused it with AVI (or maybe ASF/WMV? – could really be either from the description). Regardless… > I want to make videos. > > So this software records them in MKV. > > None of the publishing platforms that I know of, accept videos in MKV format. They may have a point for that though: While MKV is popular with video *editing*, for *publishing* the expected container format seems to generally be MP4 for MPEG LA A/V codecs (H.264/H.265 with MP3/AAC) and WebM for Xiph A/V codecs (VP8/VP9/AV1 with Vorbis/Opus). Based on this, I’ll propose an alternate issue description that is neither both inaccurate nor slightly offensive: # Kamoso only supports recording video using the MKV container format Currently Kamoso only allows videos to be recorded only using the MKV container format. This format, while OK for video editing and archival, is not generally accepted on video publishing sites and hence makes Kamoso harder to use when recording video for publishing. As such, it would be nice if Kamoso allowed recording video using an MP4 container format containing either H.264 or H.265 video and MP3 or AAC audio, as that is still the most accepted format for video publishing currently. Since these formats are proprietary and a commonly accepted Open Source format stack exists it would be preferable if, at the same time, the option to also record video using the WebM container format containing either VP8 or VP9 video and Vorbis or Opus audio also be added. Most likely support for any of these would “just” boil down to passing the right set of parameters to GStreamer, so it shouldn’t make much difference how many format options are exposed in the UI – within reason of course. Some feedback from GStreamer might be needed for the UI however since not all installations include support for encoding to proprietary formats. I’d assume the following options (drop-down menu) would be ideal: * The current MKV video configuration – needs a good description * MP4 (proprietary, modest compression, highly compatible, H.264/MP3) * MP4 (proprietary, high compression, usually compatible, H.265/AAC) * WebM (open, modest compression, often compatible, VP8/Vorbis) * WebM (open, high compression, usually compatible, VP9/Opus) -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 395497] Menubar - No text - Editing the shell toolbar from Configure Toolbars sometimes corrupts shell.rc
https://bugs.kde.org/show_bug.cgi?id=395497 luna sophia changed: What|Removed |Added CC||l...@unixpoet.dev -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 478981] Lightning bolt icon is shown in system tray when Power Save mode is enabled
https://bugs.kde.org/show_bug.cgi?id=478981 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/plasma/plasma-workspace/-/merge_requests/3732 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 479167] digiKam 8.3 does not take into account the "aspect ratio" property
https://bugs.kde.org/show_bug.cgi?id=479167 Maik Qualmann changed: What|Removed |Added CC||metzping...@gmail.com --- Comment #3 from Maik Qualmann --- Hmm, I can't reproduce any problems here with "real" 16:9 videos. Your video is 704x576 = 11:9 (1.2). This means that the square representation is actually correct. Why there is an aspect ratio of 1.77 in the metadata is a mystery to me at this point. We would have to scale your video by a factor of 1.4545 in width, but that is not logical given the video size. Otherwise we would have to assume a height of around 396 pixels, the rest are black borders. Where is the video from? Is this from a 4:3 (DVD/DV) recorder that has recorded in 16:9 mode? Something is wrong here. Maik -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 479065] Brightness & Color System tray widget's Brightness slider does not effect brightness of external monitor
https://bugs.kde.org/show_bug.cgi?id=479065 Natalie Clarius changed: What|Removed |Added Resolution|--- |DUPLICATE Status|REPORTED|RESOLVED --- Comment #1 from Natalie Clarius --- *** This bug has been marked as a duplicate of bug 470107 *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 470107] Widget should have brightness slider for each connected monitor that supports adjusting its brightness in software
https://bugs.kde.org/show_bug.cgi?id=470107 Natalie Clarius changed: What|Removed |Added CC||dougsha...@protonmail.com --- Comment #1 from Natalie Clarius --- *** Bug 479065 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 479174] New: Scrolling by grabing and moving scrollbar in popup is not smooth
https://bugs.kde.org/show_bug.cgi?id=479174 Bug ID: 479174 Summary: Scrolling by grabing and moving scrollbar in popup is not smooth Classification: Applications Product: systemsettings Version: 5.27.10 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: med.medin.2...@gmail.com Target Milestone: --- Created attachment 164549 --> https://bugs.kde.org/attachment.cgi?id=164549=edit Scrolling by grabing and moving scrollbar in popup is not smooth In "Add property to the rule" popup, when you grab the scrollbar by mouse pointer then start moving it, it suffers from lagging especially in the upper part of the list. See attached video for more info. Operating System: Manjaro Linux KDE Plasma Version: 5.27.10 KDE Frameworks Version: 5.113.0 Qt Version: 5.15.11 Kernel Version: 6.6.8-2-MANJARO (64-bit) Graphics Platform: Wayland -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 348529] When screen is locked, turn off screen with a shorter timeout
https://bugs.kde.org/show_bug.cgi?id=348529 Natalie Clarius changed: What|Removed |Added CC||natalie_clar...@yahoo.de -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 479173] New: Energy Savings setting for On Low Battery has no effect with multiple batteries (two battery Thinkpad)
https://bugs.kde.org/show_bug.cgi?id=479173 Bug ID: 479173 Summary: Energy Savings setting for On Low Battery has no effect with multiple batteries (two battery Thinkpad) Classification: Plasma Product: Powerdevil Version: 5.27.10 Platform: Arch Linux OS: Linux Status: REPORTED Severity: major Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: tera_1...@hotmail.com CC: m...@ratijas.tk, natalie_clar...@yahoo.de Target Milestone: --- SUMMARY This is on an up to date Arch Linux with KDE Plasma on a Lenovo Thinkpad T480, which has two batteries an internal (fixed) one, and an "external" (removable) one. When using just a single battery, the actions configured in Power Management > Energy Savings for "On Low Battery" and in Power Management > Advances Power Settings for "At critical level" function well if only the internal battery is present. However, when a second battery is inserted, passing below these thresholds no longer produces any action. This has been verified to be the case then the global percentage passes the threshold, when one battery, or even both batteries pass the threshold. The result is that the system will, if left unchecked, run both its batteries dry and perform a hard power off with loss of data (which is what prompted me to set the severity of this bug report to "major"). STEPS TO REPRODUCE 1. Find a laptop with two batteries, such as the Lenovo Thinkpad T480. 2. Remove the external battery. 3. Set some actions in Power Management > Energy Savings for "On Low Battery". 4. Set a threshold in Power Management > Advances Power Settings for "Low level". 5. Let the battery discharge below that threshold. 6. Observe action being triggered. 7. Insert external battery. 8. Let batteries discharge below threshold 9. Observe that no action is triggered. OBSERVED RESULT As in 9. above, the actions are not triggered. EXPECTED RESULT One would expect that, like in 6. actions would be triggered in accordance with user settings. SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 5.27.10 KDE Frameworks Version: 5.113.0 Qt Version: 5.15.11 Kernel Version: 6.6.8-arch1-1 (64-bit) Graphics Platform: X11 Processors: 8 × Intel® Core™ i7-8550U CPU @ 1.80GHz Memory: 15,4 GiB of RAM Graphics Processor: Mesa Intel® UHD Graphics 620 Manufacturer: LENOVO Product Name: 20L6S8FB00 System Version: ThinkPad T480 ADDITIONAL INFORMATION Output of `upower -d` with only one battery: Device: /org/freedesktop/UPower/devices/line_power_AC native-path: AC power supply: yes updated: Fri 29 Dec 2023 06:14:24 PM GMT (3091 seconds ago) has history: no has statistics: no line-power warning-level: none online: no icon-name: 'ac-adapter-symbolic' Device: /org/freedesktop/UPower/devices/battery_BAT0 native-path: BAT0 vendor: LGC model:01AV420 serial: 3964 power supply: yes updated: Fri 29 Dec 2023 07:05:32 PM GMT (23 seconds ago) has history: yes has statistics: yes battery present: yes rechargeable:yes state: discharging warning-level: none energy: 15.27 Wh energy-empty:0 Wh energy-full: 17.06 Wh energy-full-design: 23.94 Wh energy-rate: 5.953 W voltage: 11.93 V charge-cycles: 18 time to empty: 2.6 hours percentage: 89% capacity:71.2615% technology: lithium-polymer icon-name: 'battery-full-symbolic' History (charge): 1703876702 89.000 discharging History (rate): 1703876732 5.953 discharging 1703876702 5.862 discharging 1703876672 6.079 discharging 1703876642 5.663 discharging Device: /org/freedesktop/UPower/devices/line_power_ucsi_source_psy_USBC000o001 native-path: ucsi-source-psy-USBC000:001 power supply: yes updated: Fri 29 Dec 2023 06:14:24 PM GMT (3091 seconds ago) has history: no has statistics: no line-power warning-level: none online: no icon-name: 'ac-adapter-symbolic' Device: /org/freedesktop/UPower/devices/line_power_ucsi_source_psy_USBC000o002 native-path: ucsi-source-psy-USBC000:002 power supply: yes updated: Fri 29 Dec 2023 06:14:24 PM GMT (3091 seconds ago) has history: no has statistics: no line-power warning-level: none online: no icon-name: 'ac-adapter-symbolic' Device: /org/freedesktop/UPower/devices/DisplayDevice power supply: yes updated:
[Discover] [Bug 479165] The Discover application does not update snaps - Kubuntu 22.04 LTS
https://bugs.kde.org/show_bug.cgi?id=479165 huezohuezo.1...@gmail.com changed: What|Removed |Added Summary|The Discover application|The Discover application |does not update snaps |does not update snaps - ||Kubuntu 22.04 LTS -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 479172] Segmentation fault __strlen_avx2 opening discover
https://bugs.kde.org/show_bug.cgi?id=479172 Bug Janitor Service changed: What|Removed |Added Keywords||qt6 -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 479172] Segmentation fault __strlen_avx2 opening discover
https://bugs.kde.org/show_bug.cgi?id=479172 Enrico changed: What|Removed |Added Resolution|--- |NOT A BUG Status|REPORTED|RESOLVED --- Comment #1 from Enrico --- Sorry, it was a KaOS problem. "sudo pacman -Rdd fwupd" fixed the problem (if someone will read this in the future) -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 479172] New: Segmentation fault __strlen_avx2 opening discover
https://bugs.kde.org/show_bug.cgi?id=479172 Bug ID: 479172 Summary: Segmentation fault __strlen_avx2 opening discover Classification: Applications Product: Discover Version: 5.91.0 Platform: Other OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: discover Assignee: plasma-b...@kde.org Reporter: enric...@hotmail.com CC: aleix...@kde.org Target Milestone: --- Application: plasma-discover (5.91.0) Qt Version: 6.6.1 Frameworks Version: 5.247.0 Operating System: Linux 6.5.11-1 x86_64 Windowing System: Wayland Distribution: KaOS (2023) DrKonqi: 5.91.0 [CoredumpBackend] -- Information about the crash: I just try to open Discover and it crashes after a second (KaOS with Plasma 6) The crash can be reproduced every time. -- Backtrace: Application: Discover (plasma-discover), signal: Segmentation fault [New LWP 10444] [New LWP 10465] [New LWP 10446] [New LWP 10476] [New LWP 10466] [New LWP 10445] [New LWP 10455] [New LWP 10454] [New LWP 10468] [New LWP 10484] [New LWP 10487] [New LWP 10485] [New LWP 10467] [New LWP 10488] [New LWP 10486] [New LWP 10447] [New LWP 10448] [New LWP 10462] [New LWP 10457] [New LWP 10456] [New LWP 10478] [New LWP 10475] [New LWP 10479] [New LWP 10474] [New LWP 10449] [New LWP 10463] [New LWP 10477] [New LWP 10489] [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/libthread_db.so.1". Core was generated by `/usr/bin/plasma-discover'. Program terminated with signal SIGSEGV, Segmentation fault. #0 0x7f03566adb8c in __pthread_kill_implementation () from /lib/libc.so.6 [Current thread is 1 (Thread 0x7f0351901980 (LWP 10444))] python sentry-sdk not installed :( Cannot QML trace cores :( [Current thread is 1 (Thread 0x7f0351901980 (LWP 10444))] Thread 28 (Thread 0x7f02cce7b6c0 (LWP 10489)): #0 0x7f0356721d99 in syscall () at /lib/libc.so.6 #1 0x7f035560be5c in g_cond_wait_until () at /usr/lib/libglib-2.0.so.0 #2 0x7f035557ffa1 in ??? () at /usr/lib/libglib-2.0.so.0 #3 0x7f03555e0712 in ??? () at /usr/lib/libglib-2.0.so.0 #4 0x7f03555dfdad in ??? () at /usr/lib/libglib-2.0.so.0 #5 0x7f03566abf2c in start_thread () at /lib/libc.so.6 #6 0x7f035672969c in clone3 () at /lib/libc.so.6 Thread 27 (Thread 0x7f02f21fd6c0 (LWP 10477)): #0 0x7f035671cfbf in poll () at /lib/libc.so.6 #1 0x7f03555b44e7 in ??? () at /usr/lib/libglib-2.0.so.0 #2 0x7f03555b4b1c in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #3 0x7f03563f2091 in QEventDispatcherGlib::processEvents (this=0x7f02d8000b70, flags=...) at /usr/src/debug/qt6-base/qtbase-everywhere-src-6.6.1/src/corelib/kernel/qeventdispatcher_glib.cpp:395 #4 0x7f0356162e33 in QEventLoop::exec (this=this@entry=0x7f02f21fcc10, flags=..., flags@entry=...) at /usr/src/debug/qt6-base/qtbase-everywhere-src-6.6.1/src/corelib/global/qflags.h:34 #5 0x7f035625470c in QThread::exec (this=) at /usr/src/debug/qt6-base/qtbase-everywhere-src-6.6.1/src/corelib/global/qflags.h:74 #6 0x7f03562eca27 in operator() (__closure=) at /usr/src/debug/qt6-base/qtbase-everywhere-src-6.6.1/src/corelib/thread/qthread_unix.cpp:324 #7 (anonymous namespace)::terminate_on_exception > (t=) at /usr/src/debug/qt6-base/qtbase-everywhere-src-6.6.1/src/corelib/thread/qthread_unix.cpp:260 #8 QThreadPrivate::start (arg=0x3bf3950) at /usr/src/debug/qt6-base/qtbase-everywhere-src-6.6.1/src/corelib/thread/qthread_unix.cpp:283 #9 0x7f03566abf2c in start_thread () at /lib/libc.so.6 #10 0x7f035672969c in clone3 () at /lib/libc.so.6 Thread 26 (Thread 0x7f031adfe6c0 (LWP 10463)): #0 0x7f035671cfbf in poll () at /lib/libc.so.6 #1 0x7f03555b44e7 in ??? () at /usr/lib/libglib-2.0.so.0 #2 0x7f03555b4b1c in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #3 0x7f031bf7936e in ostree_repo_pull_with_options () at /usr/lib/libostree-1.so.1 #4 0x7f033075335b in ??? () at /usr/lib/libflatpak.so.0 #5 0x7f033075a7f7 in ??? () at /usr/lib/libflatpak.so.0 #6 0x7f033076989b in flatpak_installation_update_appstream_full_sync () at /usr/lib/libflatpak.so.0 #7 0x7f0331d6ad9b in ??? () at /usr/lib/qt6/plugins/discover/flatpak-backend.so #8 0x7f03562eca27 in operator() (__closure=) at /usr/src/debug/qt6-base/qtbase-everywhere-src-6.6.1/src/corelib/thread/qthread_unix.cpp:324 #9 (anonymous namespace)::terminate_on_exception > (t=) at /usr/src/debug/qt6-base/qtbase-everywhere-src-6.6.1/src/corelib/thread/qthread_unix.cpp:260 #10 QThreadPrivate::start (arg=0x28d6de0) at /usr/src/debug/qt6-base/qtbase-everywhere-src-6.6.1/src/corelib/thread/qthread_unix.cpp:283 #11 0x7f03566abf2c in start_thread () at /lib/libc.so.6 #12 0x7f035672969c in clone3 () at /lib/libc.so.6 Thread 25 (Thread 0x7f0343fff6c0 (LWP 10449)): #0 0x7f03566a8d86 in
[systemsettings] [Bug 479171] New: Misleading polish translation in date and time settings
https://bugs.kde.org/show_bug.cgi?id=479171 Bug ID: 479171 Summary: Misleading polish translation in date and time settings Classification: Applications Product: systemsettings Version: 5.27.10 Platform: Neon OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: kcm_clock Assignee: plasma-b...@kde.org Reporter: jon...@potoniec.eu Target Milestone: --- SUMMARY Checkbox label, translated as “Sam ustawiaj datę i czas”, may mean both set date yourself (as user) or set it automatically without user interaction. I would suggest to change translation to something like “Ustaw datę automatycznie” which is less ambiguous. STEPS TO REPRODUCE 1. Open date and time settings OBSERVED RESULT Unclear checkbox state. EXPECTED RESULT Less ambiguous label. SOFTWARE/OS VERSIONS Linux/KDE Plasma: (available in About System) KDE Plasma Version: 5.27.10 KDE Frameworks Version: 5.113.0 Qt Version: 5.15.11 -- You are receiving this mail because: You are watching all bug changes.
[plasma-systemmonitor] [Bug 479170] valgrind output
https://bugs.kde.org/show_bug.cgi?id=479170 Bug Janitor Service changed: What|Removed |Added Keywords||qt6 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-solid] [Bug 477915] Can't mount encrypted drives
https://bugs.kde.org/show_bug.cgi?id=477915 Fabio changed: What|Removed |Added CC||ctrlal...@gmail.com --- Comment #9 from Fabio --- I was bitten by this same bug, recompiling Solid with https://invent.kde.org/frameworks/solid/-/merge_requests/134 fixed the issue for me. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 478966] Krita transform mask moves initial position of a tween curve (Nightly git master build (git dfe4f31))
https://bugs.kde.org/show_bug.cgi?id=478966 lenoto7...@ubinert.com changed: What|Removed |Added CC||lenoto7...@ubinert.com --- Comment #1 from lenoto7...@ubinert.com --- Hey, I tested this on debian with the nightly appimage, is this small snippet that appears in the output terminal normal? SAFE ASSERT (krita): "mergeResult" in file /home/appimage/workspace/Krita_Nightly_Appimage_Build/krita/libs/ui/tool/strokes/move_stroke_strategy.cpp, line 126 SAFE ASSERT (krita): "mergeResult" in file /home/appimage/workspace/Krita_Nightly_Appimage_Build/krita/libs/ui/tool/strokes/move_stroke_strategy.cpp, line 126 SAFE ASSERT (krita): "mergeResult" in file /home/appimage/workspace/Krita_Nightly_Appimage_Build/krita/libs/ui/tool/strokes/move_stroke_strategy.cpp, line 126 SAFE ASSERT (krita): "mergeResult" in file /home/appimage/workspace/Krita_Nightly_Appimage_Build/krita/libs/ui/tool/strokes/move_stroke_strategy.cpp, line 126 SAFE ASSERT (krita): "mergeResult" in file /home/appimage/workspace/Krita_Nightly_Appimage_Build/krita/libs/ui/tool/strokes/move_stroke_strategy.cpp, line 126 SAFE ASSERT (krita): "mergeResult" in file /home/appimage/workspace/Krita_Nightly_Appimage_Build/krita/libs/ui/tool/strokes/move_stroke_strategy.cpp, line 126 Because I (sometimes) get it. It's not very consistent if it does the transform mask properly. Sometimes it works flawlessly and sometimes it does a terrible job at it. -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 407288] Kate doesn't bring existing session into foreground
https://bugs.kde.org/show_bug.cgi?id=407288
--- Comment #21 from Christoph Cullmann ---
We do now
void KateAppAdaptor::activate(const QString )
{
KateMainWindow *win = m_app->activeKateMainWindow();
if (!win) {
return;
}
// like QtSingleApplication
win->setWindowState(win->windowState() & ~Qt::WindowMinimized);
win->raise();
win->activateWindow();
// try to raise window, see bug 407288
if (KWindowSystem::isPlatformX11()) {
#if HAVE_X11
KStartupInfo::setNewStartupId(win->windowHandle(), token.toUtf8());
#endif
} else if (KWindowSystem::isPlatformWayland()) {
KWindowSystem::setCurrentXdgActivationToken(token);
}
KWindowSystem::activateWindow(win->windowHandle());
}
that still is not enough, I would assume that is the same issue as on Wayland,
Windows just doesn't allow for the window to be raised, one just gets the
notification in the task bar.
--
You are receiving this mail because:
You are watching all bug changes.
[kate] [Bug 429139] Global clipboard is not working in files with UTF BOM character
https://bugs.kde.org/show_bug.cgi?id=429139 Christoph Cullmann changed: What|Removed |Added CC||milen_...@abv.bg --- Comment #7 from Christoph Cullmann --- *** Bug 477449 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 477449] Can't copy text from editor to clipboard
https://bugs.kde.org/show_bug.cgi?id=477449 Christoph Cullmann changed: What|Removed |Added Resolution|WORKSFORME |DUPLICATE --- Comment #2 from Christoph Cullmann --- *** This bug has been marked as a duplicate of bug 429139 *** -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 475717] Kate crashes upon start on Windows
https://bugs.kde.org/show_bug.cgi?id=475717 Christoph Cullmann changed: What|Removed |Added Resolution|--- |WORKSFORME CC||cullm...@kde.org Status|REPORTED|RESOLVED --- Comment #3 from Christoph Cullmann --- I tried the current Windows store version and https://binary-factory.kde.org/view/Windows%2064-bit/job/Kate_Release_win64/2262/ Doesn't crash for me. -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 473266] Regex doesn't seem to respect flag state
https://bugs.kde.org/show_bug.cgi?id=473266 Christoph Cullmann changed: What|Removed |Added OS|Microsoft Windows |All CC||cullm...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 477449] Can't copy text from editor to clipboard
https://bugs.kde.org/show_bug.cgi?id=477449 Christoph Cullmann changed: What|Removed |Added CC||cullm...@kde.org Status|REPORTED|RESOLVED Resolution|--- |WORKSFORME Version Fixed In||23.08.4 --- Comment #1 from Christoph Cullmann --- I tried that with Kate Version 23.08.4 from https://binary-factory.kde.org/view/Windows%2064-bit/job/Kate_Release_win64/2262/ on Windows 11 Pro 64 bit, with latest updates, works for me, can copy to other Windows programs and Kate itself. -- You are receiving this mail because: You are watching all bug changes.
[plasma-systemmonitor] [Bug 479170] New: valgrind output
https://bugs.kde.org/show_bug.cgi?id=479170 Bug ID: 479170 Summary: valgrind output Classification: Applications Product: plasma-systemmonitor Version: unspecified Platform: Neon OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: ksysguard-b...@kde.org Reporter: tmass...@gmail.com CC: ahiems...@heimr.nl, plasma-b...@kde.org Target Milestone: --- Created attachment 164548 --> https://bugs.kde.org/attachment.cgi?id=164548=edit full valgrind output SUMMARY running valgrind on plasma-systemmonitor a lot of trouble are showed. this bug report is to keep trace of them STEPS TO REPRODUCE 1. build plasma-systemmonitor on your machine 2. create this script: $ cat run.sh #!/bin/bash LD_PRELOAD="/home/tom1/kde/build/libksysguard/bin/libFacesPlugin.so /home/tom1/kde/build/libksysguard/bin/libKSysGuardSensorFaces.so /home/tom1/kde/build/kconfig/bin/libKF6ConfigCore.so.6 " valgrind /home/tom1/kde/build/plasma-systemmonitor/bin/plasma-systemmonitor 3. chmod +x && ./run OBSERVED RESULT a lot of issue EXPECTED RESULT no issue SOFTWARE/OS VERSIONS Linux/KDE Plasma neon unstable developer 25-12-2023 KDE Plasma Version 5.91.90 KDE Frameworks Version: 5.248.0 Qt Version: 6.6.1 Kernel version: 6.2.0-39-generic (64-bit) Graphic Platform: Wayland ADDITIONAL INFORMATION full valgring output attached, cannot stay here tom1@tom-neon:~/kde$ ./run.sh ==24605== Memcheck, a memory error detector ==24605== Copyright (C) 2002-2017, and GNU GPL'd, by Julian Seward et al. ==24605== Using Valgrind-3.18.1 and LibVEX; rerun with -h for copyright info ==24605== Command: /home/tom1/kde/build/plasma-systemmonitor/bin/plasma-systemmonitor ==24605== *** I suppose Ubuntu ldd problem, not always present ==24605== Invalid read of size 8 ==24605==at 0x40286A8: strncmp (strcmp.S:172) ==24605==by 0x400668D: is_dst (dl-load.c:216) ==24605==by 0x400810E: _dl_dst_count (dl-load.c:253) ==24605==by 0x400810E: expand_dynamic_string_token (dl-load.c:395) ==24605==by 0x40082B7: fillin_rpath.isra.0 (dl-load.c:483) ==24605==by 0x4008602: decompose_rpath (dl-load.c:654) ==24605==by 0x400ABF5: cache_rpath (dl-load.c:696) ==24605==by 0x400ABF5: cache_rpath (dl-load.c:677) ==24605==by 0x400ABF5: _dl_map_object (dl-load.c:2165) ==24605==by 0x4003494: openaux (dl-deps.c:64) ==24605==by 0x6B458A7: _dl_catch_exception (dl-error-skeleton.c:208) ==24605==by 0x4003C7B: _dl_map_object_deps (dl-deps.c:248) ==24605==by 0x400EA0E: dl_open_worker_begin (dl-open.c:592) ==24605==by 0x6B458A7: _dl_catch_exception (dl-error-skeleton.c:208) ==24605==by 0x400DF99: dl_open_worker (dl-open.c:782) ==24605== Address 0xcf5ae19 is 9 bytes inside a block of size 15 alloc'd ==24605==at 0x4848899: malloc (in /usr/libexec/valgrind/vgpreload_memcheck-amd64-linux.so) ==24605==by 0x40271DF: malloc (rtld-malloc.h:56) ==24605==by 0x40271DF: strdup (strdup.c:42) ==24605==by 0x4008594: decompose_rpath (dl-load.c:629) ==24605==by 0x400ABF5: cache_rpath (dl-load.c:696) ==24605==by 0x400ABF5: cache_rpath (dl-load.c:677) ==24605==by 0x400ABF5: _dl_map_object (dl-load.c:2165) ==24605==by 0x4003494: openaux (dl-deps.c:64) ==24605==by 0x6B458A7: _dl_catch_exception (dl-error-skeleton.c:208) ==24605==by 0x4003C7B: _dl_map_object_deps (dl-deps.c:248) ==24605==by 0x400EA0E: dl_open_worker_begin (dl-open.c:592) ==24605==by 0x6B458A7: _dl_catch_exception (dl-error-skeleton.c:208) ==24605==by 0x400DF99: dl_open_worker (dl-open.c:782) ==24605==by 0x6B458A7: _dl_catch_exception (dl-error-skeleton.c:208) ==24605==by 0x400E34D: _dl_open (dl-open.c:883) ==24605== ==24605== Invalid read of size 8 ==24605==at 0x40286A8: strncmp (strcmp.S:172) ==24605==by 0x400668D: is_dst (dl-load.c:216) ==24605==by 0x4007F79: _dl_dst_substitute (dl-load.c:295) ==24605==by 0x40082B7: fillin_rpath.isra.0 (dl-load.c:483) ==24605==by 0x4008602: decompose_rpath (dl-load.c:654) ==24605==by 0x400ABF5: cache_rpath (dl-load.c:696) ==24605==by 0x400ABF5: cache_rpath (dl-load.c:677) ==24605==by 0x400ABF5: _dl_map_object (dl-load.c:2165) ==24605==by 0x4003494: openaux (dl-deps.c:64) ==24605==by 0x6B458A7: _dl_catch_exception (dl-error-skeleton.c:208) ==24605==by 0x4003C7B: _dl_map_object_deps (dl-deps.c:248) ==24605==by 0x400EA0E: dl_open_worker_begin (dl-open.c:592) ==24605==by 0x6B458A7: _dl_catch_exception (dl-error-skeleton.c:208) ==24605==by 0x400DF99: dl_open_worker (dl-open.c:782) ==24605== Address 0xcf5ae19 is 9 bytes inside a block of size 15 alloc'd ==24605==at 0x4848899: malloc (in /usr/libexec/valgrind/vgpreload_memcheck-amd64-linux.so) ==24605==by 0x40271DF: malloc (rtld-malloc.h:56) ==24605==by 0x40271DF: strdup (strdup.c:42) ==24605==
[kwin] [Bug 479168] De-saturated Colors in HDR Mode
https://bugs.kde.org/show_bug.cgi?id=479168 Bug Janitor Service changed: What|Removed |Added Keywords||qt6 -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 479169] New: Menu Editor doesn't delete *.desktop files from ./local/share/applications folder on deletion of entry from menu
https://bugs.kde.org/show_bug.cgi?id=479169 Bug ID: 479169 Summary: Menu Editor doesn't delete *.desktop files from ./local/share/applications folder on deletion of entry from menu Classification: I don't know Product: kde Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: igor.mironc...@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 *** Menu Editor doesn't delete *.desktop files from ./local/share/applications folder on deletion of entry from menu STEPS TO REPRODUCE 1. Create new entry with Menu Editor and save changes. 2. Delete that entry and save changes. 3. OBSERVED RESULT *.desktop file created with Menu Editor still in ./local/share/applications folder. This can lead to UI issues with applications installed by system. For example with Firefox. When it's installed by hands from archive and menu entry created with Menu Editor all works fine. But after deletion of Firefox and installing it with apt user has ugly experience with icons in Task Manager as *.desktop file still there, even with deleted entry with Menu Editor. EXPECTED RESULT *.desktop file should be deleted with menu entry by Menu Editor, to prevent such UI issues. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: KDE neon 5.27 (available in About System) KDE Plasma Version: 5.27.10 KDE Frameworks Version: 5.113.0 Qt Version: 5.15.11 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 478407] Crashes when viewing connections
https://bugs.kde.org/show_bug.cgi?id=478407 flashman...@gmail.com changed: What|Removed |Added CC||flashman...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 479153] PyQt6 app reports The cached device pixel ratio value was stale on window expose.
https://bugs.kde.org/show_bug.cgi?id=479153 Nicolas Fella changed: What|Removed |Added Status|REPORTED|RESOLVED CC||nicolas.fe...@gmx.de Resolution|--- |UPSTREAM --- Comment #1 from Nicolas Fella --- Please report this to https://bugreports.qt.io/ -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 478951] Xwayland apps are not minimized when its entry in the task manager is clicked
https://bugs.kde.org/show_bug.cgi?id=478951 Nicolas Fella changed: What|Removed |Added CC||nicolas.fe...@gmx.de --- Comment #2 from Nicolas Fella --- The problem is that in https://invent.kde.org/plasma/plasma-desktop/-/blob/master/applets/taskmanager/package/contents/ui/code/tools.js#L172 model.IsActive is false for newly launched XWayland apps -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 479166] There is no icon of Firefox when it's launched
https://bugs.kde.org/show_bug.cgi?id=479166 Igor Mironchik changed: What|Removed |Added Resolution|--- |NOT A BUG Status|REPORTED|RESOLVED -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 479167] digiKam 8.3 does not take into account the "aspect ratio" property
https://bugs.kde.org/show_bug.cgi?id=479167 caulier.gil...@gmail.com changed: What|Removed |Added Component|Metadata-Video |Preview-Video CC||caulier.gil...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 479168] New: De-saturated Colors in HDR Mode
https://bugs.kde.org/show_bug.cgi?id=479168 Bug ID: 479168 Summary: De-saturated Colors in HDR Mode Classification: Plasma Product: kwin Version: 5.91.0 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: wayland-generic Assignee: kwin-bugs-n...@kde.org Reporter: acc-...@berz.one Target Milestone: --- Created attachment 164545 --> https://bugs.kde.org/attachment.cgi?id=164545=edit Measurement reports, ICC profile, Display EDID, etc SUMMARY I have tested the color management and HDR features in Plasma. In SDR mode I get really accurate colors after profiling (thank you for implementing this). In HDR mode the mapping seems to be broken. As far as I understood, SDR content should be displayed as sRGB per default and the option to "stretch" the colors to rec2020 via the "SDR Color Intensity" setting. Leaving the SDR Color Intensity setting at 0% (default) results in completely de-saturated colors, while setting it to 100% (rec2020) results in fairly accurate sRGB colors for SDR content. Playing back an HDR YouTube video (e.g ) with mpv also has the same de-saturated colors (the HDR part of it is working great though). Playing the video on the same monitor but with macOS and safari works fine with default display settings, so I'd guess the issue is not (entirely) a monitor one. I did a bunch of DisplayCAL measurements in SDR and HDR mode. See attachment for measurement reports, ICC profile, EDID, etc. STEPS TO REPRODUCE 1. Enable HDR mode using the default SDR Color Intensity setting of 0% 2. Look at any SDR content 3. Play with the SDR Color Intensity in Display settings compare the results (ideally measure them) OBSERVED RESULT Keeping the SDR Color Intensity setting of 0% results in really de-saturated colors. A value of 90% to 100% is required to get pretty accurate sRGB colors. EXPECTED RESULT The default Color intensity setting results in pretty accurate colors (as well as the display can reproduce them OOTB). Increasing the value results in more saturated colors. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Operating System: Fedora Linux 40 KDE Plasma Version: 5.91.0 KDE Frameworks Version: 5.247.0 Qt Version: 6.6.1 Kernel Version: 6.6.8-200.fc39.x86_64 (64-bit) Graphics Platform: Wayland Processors: 24 × AMD Ryzen 9 5900X 12-Core Processor Memory: 62.7 GiB of RAM Graphics Processor: AMD Radeon RX 7900 XTX Display: Dell Alienware AW3423DWF -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 479167] digiKam 8.3 does not take into account the "aspect ratio" property
https://bugs.kde.org/show_bug.cgi?id=479167 --- Comment #2 from Peter --- Created attachment 164546 --> https://bugs.kde.org/attachment.cgi?id=164546=edit Aspect ratio in digiKam 8.3 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 479167] digiKam 8.3 does not take into account the "aspect ratio" property
https://bugs.kde.org/show_bug.cgi?id=479167 --- Comment #1 from Peter --- Created attachment 164544 --> https://bugs.kde.org/attachment.cgi?id=164544=edit Aspect ratio in digiKam 8.2 -- You are receiving this mail because: You are watching all bug changes.
