[kwin] [Bug 478556] Sometimes the stacking order is out of sync with Xorg
https://bugs.kde.org/show_bug.cgi?id=478556 Andrew Shark changed: What|Removed |Added CC||ash...@linuxcomp.ru --- Comment #64 from Andrew Shark --- The bug in the JetBrains youtrack: https://youtrack.jetbrains.com/issue/PY-72228/Input-events-are-passed-to-underlying-X11-window -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 480171] With 225% scale on a 4k screen, right-side-tiled windows and full-screen video/image content are not fully adjacent to right screen edge
https://bugs.kde.org/show_bug.cgi?id=480171 Gurenko Alex changed: What|Removed |Added CC||agure...@protonmail.com -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kwidgetsaddons] [Bug 486098] Creating and closing sequentially two QMainWindows core-dumps with KDE
https://bugs.kde.org/show_bug.cgi?id=486098 --- Comment #1 from wolf.seif...@web.de --- By "closing" I meant triggering the menubars "Close" menu. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 486099] New: Opening context menu logs unnecessary messages
https://bugs.kde.org/show_bug.cgi?id=486099 Bug ID: 486099 Summary: Opening context menu logs unnecessary messages Classification: Applications Product: dolphin Version: 24.02.2 Platform: Arch Linux OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: dead...@dmu.gg CC: kfm-de...@kde.org Target Milestone: --- SUMMARY When you open the context menu (right click), you get some unnecessary debugging messages being printed to the console: ``` $ dolphin . true actions!!! ``` I can't find any reference to the string "actions!!!" in the Dolphin repo - maybe it's in another module? STEPS TO REPRODUCE 1. Open dolphin somewhere: `dolphin .` 2. Open the context menu (right click) 3. Observe the messages being output to the console OBSERVED RESULT Messages being output. EXPECTED RESULT These short messages should not be output, or if they are important should have relevant debugging information included with them. SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 6.0.4 KDE Frameworks Version: 6.1.0 Qt Version: 6.7.0 Kernel Version: 6.8.7-arch1-1 (64-bit) Graphics Platform: Wayland -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 479144] Refresh rate becomes unstable in Wayland using freesync at 4k 120hz only after using fullscreen windows
https://bugs.kde.org/show_bug.cgi?id=479144 --- Comment #6 from Alexander Streng --- In my case I still have issues with freesync in Fedora 40 KDE Plasma 6.0.3 . I Tested freesync in Doom Eternal and in fight scenarios the fps would tank very badly if I had adaptive sync in either "automatic" or "always" mode. I have an Asus Tuf a16 advantage edition (2023) laptop which has a freesync display built-in. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kwidgetsaddons] [Bug 486098] New: Creating and closing sequentially two QMainWindows core-dumps with KDE
https://bugs.kde.org/show_bug.cgi?id=486098 Bug ID: 486098 Summary: Creating and closing sequentially two QMainWindows core-dumps with KDE Classification: Frameworks and Libraries Product: frameworks-kwidgetsaddons Version: 6.1.0 Platform: Arch Linux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: cf...@kde.org Reporter: wolf.seif...@web.de CC: kdelibs-b...@kde.org Target Milestone: --- Created attachment 168890 --> https://bugs.kde.org/attachment.cgi?id=168890&action=edit Reproducer: mainwindows.cpp and CMakeLists.txt SUMMARY When creating and closing sequentially two QMainWindows the second one core-dumps when clicking on it. This only happens for the KDE version, the pure Qt version works fine. STEPS TO REPRODUCE 1. Unzip the attached mainwindows.zip 2. $ cmake . 3. $ cmake --build . 4. $ ./mainwindows (close first window and click on second) Segmentation fault (core dumped) 5. $ LD_LIBRARY_PATH=/home/wolfgang/qt/6.7.0/gcc_64/lib ./mainwindows (works fine) OBSERVED RESULT When clicking on the second mainwindows menubar the application crashes. When using pure Qt it works as expected. EXPECTED RESULT The second mainwindows menubar "Close" should close the mainwindow and quit the application. Pure Qt and KDE version should behave the same, only the look & feel may differ. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Arch Linux KDE Plasma Version: 6.0.4 KDE Frameworks Version: 6.1.0 Qt Version: 6.7.0 Graphics Platform: Wayland -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 472494] Export to Google Photos ends up with "too many requests" error
https://bugs.kde.org/show_bug.cgi?id=472494 --- Comment #32 from Maik Qualmann --- Hi Gilles, I do not understand it either. I filled out the appeal again. Google also requested a review of our OAuth client, which I sent again with additional information that was not previously asked for, e.g. link to the program documentation. Wait... Maik -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 472494] Export to Google Photos ends up with "too many requests" error
https://bugs.kde.org/show_bug.cgi?id=472494 --- Comment #31 from caulier.gil...@gmail.com --- Hi Maik, I read the AUP-3 section of the document, and i do not understand why the Google stuff considerate that the digiKam uploader violate something. Without a real explanation given by a real human, it will be difficult to fix something... Gilles Caulier -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 479144] Refresh rate becomes unstable in Wayland using freesync at 4k 120hz only after using fullscreen windows
https://bugs.kde.org/show_bug.cgi?id=479144 --- Comment #5 from Gianandrea --- For me this issue is now resolved. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 472494] Export to Google Photos ends up with "too many requests" error
https://bugs.kde.org/show_bug.cgi?id=472494 --- Comment #30 from Maik Qualmann --- It is always the AUP-3 guideline that we are said to have violated. Does anyone have any ideas about what exactly the Google AI might not like about our Google Export Tool? https://developers.google.com/photos/library/guides/acceptable-use#permission Maik -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 486093] -Wstrict-aliasing in tests
https://bugs.kde.org/show_bug.cgi?id=486093 Paul Floyd changed: What|Removed |Added Assignee|jsew...@acm.org |pjfl...@wanadoo.fr -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 486093] -Wstrict-aliasing in tests
https://bugs.kde.org/show_bug.cgi?id=486093 Paul Floyd changed: What|Removed |Added CC||pjfl...@wanadoo.fr --- Comment #2 from Paul Floyd --- There is of course a load of intentional UB in the test cases. But this looks unintentional. The risk is that compilers start to exploit the UB for optimization and the code then breaks. Rather than using illegal type casts the code should use memcpy (or even better std::bit_cast but that requires C++20). -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 478556] Sometimes the stacking order is out of sync with Xorg
https://bugs.kde.org/show_bug.cgi?id=478556 --- Comment #63 from Gladox114 --- (In reply to vm from comment #62) > I've found quite fast repro, it's still random, but breaks by 2-15 slow > clicks (after `reboot` or `killall kwin_x11`): > > https://youtu.be/zjreuC6gPDQ > > 3 IntelliJ IDEA + 1 Kitty + 1 Chrome > Note: for me it breaks ONLY with IDEA, i've tried DBeaver and OBS - no such > problem. > Hope it may help. If you want something that is mit random. Try Apex Legends. It ses to trigger it exactly the same, always in an instant -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 472494] Export to Google Photos ends up with "too many requests" error
https://bugs.kde.org/show_bug.cgi?id=472494 I-Kang Ding changed: What|Removed |Added Version|8.2.0 |8.3.0 Resolution|FIXED |--- Platform|openSUSE|macOS (DMG) Status|RESOLVED|REOPENED OS|Linux |macOS --- Comment #29 from I-Kang Ding --- I noticed that the "Too Many Requests" error appears again on the Digicam 8.3.0. I am using MacOS platform. The error messages are as below: "Error transferring https://photoslibrary.googleapis.com/v1/albums?pageSize=50 - server replied: Too Many Requests" I know this problem is from the google side and there's little we can do other than relaying this info to google so that they can unlock the API key used by DigiKam. Thank you in advance for whatever you can do. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 460478] Dolphin crashes on monitor turn on
https://bugs.kde.org/show_bug.cgi?id=460478 Bug Janitor Service changed: What|Removed |Added Resolution|BACKTRACE |WORKSFORME Status|NEEDSINFO |RESOLVED --- Comment #21 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.
[plasmashell] [Bug 483767] Pushing meta button twice bugs out task manager
https://bugs.kde.org/show_bug.cgi?id=483767 --- 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.
[konsole] [Bug 201679] middle-click on tab should paste to that tab without switching tab
https://bugs.kde.org/show_bug.cgi?id=201679 Bug Janitor Service changed: What|Removed |Added Resolution|WAITINGFORINFO |WORKSFORME Status|NEEDSINFO |RESOLVED --- Comment #10 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.
[konsole] [Bug 381593] Fonts space incorrect when typing ligature marks (Hindi, Sanskrit, Bangla)
https://bugs.kde.org/show_bug.cgi?id=381593 Bug Janitor Service changed: What|Removed |Added Resolution|WAITINGFORINFO |WORKSFORME Status|NEEDSINFO |RESOLVED --- Comment #12 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 483777] Enabling Proxies Corrupts Timeline
https://bugs.kde.org/show_bug.cgi?id=483777 Bug Janitor Service changed: What|Removed |Added Resolution|WAITINGFORINFO |WORKSFORME Status|NEEDSINFO |RESOLVED --- Comment #11 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.
[konsole] [Bug 225202] Konsole should not mark tab as changed if it is visible on another view
https://bugs.kde.org/show_bug.cgi?id=225202 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.
[kdevelop] [Bug 486061] Launch configuration arguments are not fully passed when executing (escaped)
https://bugs.kde.org/show_bug.cgi?id=486061 Igor Kushnir changed: What|Removed |Added CC||igor...@gmail.com --- Comment #2 from Igor Kushnir --- I think the user is responsible for quoting or escaping problematic arguments manually. If KDevelop quotes the string automatically, passing multiple arguments becomes impossible. If KDevelop escapes special characters automatically, quoted or already escaped arguments in existing user configurations would break. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 485338] console has no syntax recognition
https://bugs.kde.org/show_bug.cgi?id=485338 --- 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.
[kwin] [Bug 485219] Night color not changing color automatically
https://bugs.kde.org/show_bug.cgi?id=485219 --- Comment #7 from Bug Janitor Service --- Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 466380] kwin_x11 crashes in KWin::X11Window::finishCompositing() when disabling compositing
https://bugs.kde.org/show_bug.cgi?id=466380 --- Comment #32 from Bug Janitor Service --- Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 483790] Unable to connect dual monitor although secondary monitor detected
https://bugs.kde.org/show_bug.cgi?id=483790 --- Comment #2 from Bug Janitor Service --- Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 483660] When the global menu is active, hamburger menu should not display
https://bugs.kde.org/show_bug.cgi?id=483660 --- 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.
[kwin] [Bug 483753] Wrong active monitor refresh rate on mpv window spawn
https://bugs.kde.org/show_bug.cgi?id=483753 --- Comment #2 from Bug Janitor Service --- Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 483649] When adding widgets, does not exit editing mode and widgets are not removed from the panel
https://bugs.kde.org/show_bug.cgi?id=483649 --- 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 482027] Can't drag and drop between Edge (Flatpak) and Firefox (Snap)
https://bugs.kde.org/show_bug.cgi?id=482027 --- 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.
[systemsettings] [Bug 409741] Print resolution is not saved in printer properties
https://bugs.kde.org/show_bug.cgi?id=409741 --- 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.
[plasmashell] [Bug 450447] Synology Drive Client doesn't autostart
https://bugs.kde.org/show_bug.cgi?id=450447 --- Comment #20 from Keith --- My previous comment was for the package from Synology. As a further test, this was replaced by the FlatPack version and autostart no longer worked. The Synology Client creates the autostart link when it first runs but FlatPack uses a different folder structure. I copied the Synology Drive Client "ponts to" string from Application launcher and created a link ~/.config/autostart/SynologyClient.desktop pointing to this string. The client now autostarts. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 485880] Full screen in some applications causes low display refresh rate
https://bugs.kde.org/show_bug.cgi?id=485880 deadmeu changed: What|Removed |Added Resolution|WAITINGFORINFO |FIXED Status|NEEDSINFO |RESOLVED --- Comment #7 from deadmeu --- I've just updated to 6.0.4.1 and I can confirm the issue is resolved. I think the artifacting I was experiencing was more of a symptom of the performance issue with my combination of hardware & mesa. I have often experience artifacting in some full screen games prior to this issue so I don't think any of that was related to this bug. Thanks! -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 450447] Synology Drive Client doesn't autostart
https://bugs.kde.org/show_bug.cgi?id=450447 Keith changed: What|Removed |Added CC||comp.keit...@gmail.com --- Comment #19 from Keith --- This bug has reappeared under Plasma 6.0.4. The fix supplied by Markus worked. The Synology client adds a link in autostart to its .desktop when it runs. I added a login script to autostart and tried various options to spawn a separate task which made no difference. The initial task must remain for the Synology client to run. The same issue occurs for my Ubuntu Gnome PC, so not just KDE. #! /bin/bash #have tried: # /usr/bin/synology-drive autostart # nohup synology-drive autostart & # synology-drive autostart & disown #the Markus fix: synology-drive autostart sleep infinity -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 486097] [Feature Request] - Implement the ability to “instantiate” title clips
https://bugs.kde.org/show_bug.cgi?id=486097 Bug Janitor Service changed: What|Removed |Added Severity|normal |wishlist -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 416153] Allow Night color temperature adjustment with mouse wheel
https://bugs.kde.org/show_bug.cgi?id=416153 --- Comment #10 from Bug Janitor Service --- A possibly relevant merge request was started @ https://invent.kde.org/plasma/plasma-workspace/-/merge_requests/4262 -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 486097] [Feature Request] - Implement the ability to “instantiate” title clips
https://bugs.kde.org/show_bug.cgi?id=486097 hunterbradford1...@gmail.com changed: What|Removed |Added Summary|[Feature Request] Implement |[Feature Request] - |the ability to |Implement the ability to |“instantiate” title clips |“instantiate” title clips -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 486097] New: [Feature Request] Implement the ability to “instantiate” title clips
https://bugs.kde.org/show_bug.cgi?id=486097 Bug ID: 486097 Summary: [Feature Request] Implement the ability to “instantiate” title clips Classification: Applications Product: kdenlive Version: 24.02.2 Platform: Microsoft Windows OS: Microsoft Windows Status: REPORTED Severity: normal Priority: NOR Component: Effects & Transitions Assignee: j...@kdenlive.org Reporter: hunterbradford1...@gmail.com Target Milestone: --- Created attachment 168889 --> https://bugs.kde.org/attachment.cgi?id=168889&action=edit Example One of my own personal downsides to Kdenlive is that all of your text must be done individually and are stored as their own unique piece of media in your project bin. This means if you wanted to, for example, create three titles that play back to back(example attached), you would have to create ***three unique titles just to simply change what the text says..*** Not a huge deal for smaller projects, but this setup is very inefficient and leads to clutter with so many titles. Even putting the titles in folders is just a band-aid over the real problem. I propose that there should be an option to create an “instance” of your titles in the timeline. Instead of creating a new title for every word, create one title that defines what the title should look like, and allow the user to edit the text from the timeline. The user can change things like the text, font, font size, color, etc without needing to create a whole new title in their project bin. They can just copy and paste/duplicate the titles in the timeline and adjust the text and other basic properties as needed. This is a feature majority of editors have, at least every editor I’ve tried never stores text solely in the project bin, text is always creatable and editable in the timeline. When I first saw that Kden didn’t offer this it was major turn off for me but I’ve still grown to love it so I hope text is improved in the future and is more efficient for larger projects. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 485740] Blurry Icons in Panel and Icon Tray
https://bugs.kde.org/show_bug.cgi?id=485740 Rodgi changed: What|Removed |Added Summary|Blurry Icons in Icon Tray |Blurry Icons in Panel and ||Icon Tray -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 485740] Blurry Icons in Icon Tray
https://bugs.kde.org/show_bug.cgi?id=485740 --- Comment #6 from Rodgi --- Created attachment 16 --> https://bugs.kde.org/attachment.cgi?id=16&action=edit After2 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 485740] Blurry Icons in Icon Tray
https://bugs.kde.org/show_bug.cgi?id=485740 --- Comment #5 from Rodgi --- Created attachment 168887 --> https://bugs.kde.org/attachment.cgi?id=168887&action=edit Before2 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 485740] Blurry Icons in Icon Tray
https://bugs.kde.org/show_bug.cgi?id=485740 --- Comment #4 from Rodgi --- Created attachment 168886 --> https://bugs.kde.org/attachment.cgi?id=168886&action=edit After1 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 485740] Blurry Icons in Icon Tray
https://bugs.kde.org/show_bug.cgi?id=485740 --- Comment #3 from Rodgi --- Created attachment 168885 --> https://bugs.kde.org/attachment.cgi?id=168885&action=edit Before1 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 485740] Blurry Icons in Icon Tray
https://bugs.kde.org/show_bug.cgi?id=485740 Rodgi changed: What|Removed |Added CC||dakotagriz...@protonmail.co ||m --- Comment #2 from Rodgi --- I have the same problem. Some icons are blurry on start-up but become clear (and stay clear) when I hover my mouse over them. See attached before/after screenshots. This happens in both the Fedora 40 KDE ISO, as well as the EndeavourOS Gemini ISO, as well as a ~2 week old EndeavourOS plasma 6 clean install. It happens in both X11 and Wayland sessions. Let me know if you want more info. SOFTWARE/OS VERSIONS Kernel: 6.8.7-arch1-1 (64-bit) KDE Plasma Version: 6.0.4 KDE Frameworks Version: 6.1.0 Qt Version: 6.7.0 ADDITIONAL INFORMATION Display: AOC 27G2 1920x1080 @ 144Hz MOBO: MSI Tomahawk Z690 WIFI DDR4 CPU: Intel i5-12600K GPU: AMD Radeon RX 6700 XT RAM: 32GB DDR4 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 486034] clicklockd, a mouse accessibility tool doesn't work correctly on Wayland
https://bugs.kde.org/show_bug.cgi?id=486034 --- Comment #2 from Bruno Filipe --- (In reply to Zamundaaa from comment #1) > Can confirm. KWin is lacking the key press deduplication logic that's > required for multiple devices on the same seat to cooperate with each other. Hey Zamundaaa, thanks for the quick confirmation. I got a bit of practical evidence on what's happening after playing a bit with libinput debug (sudo libinput debug-events --verbose) , along with clicklockd and also a script using python-evsieve to simulate my scenario. In summary, like you already said, the current issue in kwin Wayland behavior is that when the same key is pressed/released on multiple seats it lacks any logic to avoid repeating events to mess with each other. In my scenario what happens is this: -event4 POINTER_BUTTON +1.541s BTN_LEFT (272) pressed, seat count: 1 # Real mouse BTN_LEFT pressed, from neutral state - Self-explanatory -event15 POINTER_BUTTON +1.541s BTN_LEFT (272) pressed, seat count: 2 # Virtual mouse BTN_LEFT pressed - This click should be ignored since we're already in pressed state on another seat (real mouse), but it is not. It generates a double-click instead. -event4 POINTER_BUTTON +3.125s BTN_LEFT (272) released, seat count: 1 # Real mouse BTN_LEFT released - This one should also be ignored since virtual is still in pressed state, but it is not. event4 POINTER_BUTTON +4.589s BTN_LEFT (272) pressed, seat count: 2 # Real mouse BTN_LEFT pressed again - Also should be ignored since virtual is still in pressed state, but it is not. event4 POINTER_BUTTON +4.677s BTN_LEFT (272) released, seat count: 1 # Real mouse BTN_LEFT released - Also should be ignored since virtual is still in pressed state, but it is not. -event15 POINTER_BUTTON +4.677s BTN_LEFT (272) released, seat count: 0 # Virtual BTN_LEFT released - Now kwin/Plasma should actually release effectively. A bit difficult to explain, but something like this. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 486021] Zombie pinned application
https://bugs.kde.org/show_bug.cgi?id=486021 --- Comment #2 from Washington --- I can pin new applications to "Icons Only Task Manager", but they will disappear after reboot. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 478556] Sometimes the stacking order is out of sync with Xorg
https://bugs.kde.org/show_bug.cgi?id=478556 vyacheslav.mayo...@gmail.com changed: What|Removed |Added CC||vyacheslav.mayo...@gmail.co ||m --- Comment #62 from vyacheslav.mayo...@gmail.com --- I've found quite fast repro, it's still random, but breaks by 2-15 slow clicks (after `reboot` or `killall kwin_x11`): https://youtu.be/zjreuC6gPDQ 3 IntelliJ IDEA + 1 Kitty + 1 Chrome Note: for me it breaks ONLY with IDEA, i've tried DBeaver and OBS - no such problem. Hope it may help. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 486021] Zombie pinned application
https://bugs.kde.org/show_bug.cgi?id=486021 Washington changed: What|Removed |Added CC||n...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 485775] Time should display in vertical orientation in a vertical panel
https://bugs.kde.org/show_bug.cgi?id=485775 kinghat changed: What|Removed |Added CC||madl...@gmail.com --- Comment #1 from kinghat --- > For example, instead of "10:56" being in one line, it could perhaps be: > > 10 > 56 the time, if stacked vertically, could have the ":" turned sideways and placed between the top and bottom to make it more clear that its the time. 10 . . 56 it would have better spacing than that of course. the date is hard to read as well. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 485899] System-freeze when watching YouTube Videos in Firefox or Chromium
https://bugs.kde.org/show_bug.cgi?id=485899 --- Comment #6 from Phillip Schichtel --- Ok. Just a final update: The patch mentioned by @username was indeed not related, according to Alex Deucher it only affects navi21 and I also wasn't able to reproduce the issue after reverting the an unpatched kernel. Not sure what else changed, but this went from "happens on every video even across reboots" to "doesn't happen at all" basically overnight. Maybe some package update snug in that I didn't notice. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 486096] New: "Could not find or read package" error incessantly, irreproducibly, and incorrectly
https://bugs.kde.org/show_bug.cgi?id=486096 Bug ID: 486096 Summary: "Could not find or read package" error incessantly, irreproducibly, and incorrectly Classification: Applications Product: Discover Version: 6.0.4 Platform: Arch Linux OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: discover Assignee: plasma-b...@kde.org Reporter: fake.n...@posteo.net CC: aleix...@kde.org Target Milestone: --- SUMMARY Somewhere between 20% and 100% of applications available in discover return an error message of "Error: could not find or read package $PACKAGE_NAME " when clicked on. This does not effect whether or not said package can be installed, mind; it's just annoying boilerplate; sound and fury, signifying nothing. It cannot be reproduced in any meaningful fashion for a single package, even within a session of using the application. Thus the error message is incessant, yet irreproducible and incorrectly displayed! SOFTWARE/OS VERSIONS Linux/KDE Plasma: Arch, Zen 6.8.7 KDE Plasma Version: 6.0.4 KDE Frameworks Version: 6.1.0 Qt Version: 6.7 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 472587] Option to hide clock from login & lock screens *completely*
https://bugs.kde.org/show_bug.cgi?id=472587 --- Comment #4 from Be --- After updating to KDE 6, the file /usr/share/plasma/look-and-feel/org.kde.breeze.desktop/contents/lockscreen/LockScreenUi.qml is still there for the lock screen, but the file that needs editing for the login screen has moved to /usr/share/sddm/themes/breeze/Main.qml. In both cases, set the `visible` property to always `false` for the clock. I would like a proper solution to this that doesn't require me hacking QML files after package updates. SDDM is still around in KDE 6.0, but looking at https://invent.kde.org/plasma/plasma-desktop/-/issues/91 it seems its future in KDE is still unclear? In the meantime, changing the existing "Clock: Keep visible when unlocking prompt disappears" to a simple boolean toggle to show the clock on the lock screen could be done regardless of whatever happens with the display manager. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 438291] multiple night color control applets block each other
https://bugs.kde.org/show_bug.cgi?id=438291 Natalie Clarius changed: What|Removed |Added Latest Commit||https://invent.kde.org/plas ||ma/plasma-workspace/-/commi ||t/ba7cbbf04e2ffe88b0388d2a3 ||92513c6b382922f Status|ASSIGNED|RESOLVED Resolution|--- |FIXED --- Comment #5 from Natalie Clarius --- Git commit ba7cbbf04e2ffe88b0388d2a392513c6b382922f by Natalie Clarius. Committed on 24/04/2024 at 23:22. Pushed by nclarius into branch 'master'. applets/brightness: fix night light inhibition state not synced across instances of the applet Integrate inhibition properties into the monitor class so it becomes a night light control class, which also simplifies the back-of-the-frontend code. Then use a static self member for the night light inhibitor from the control class, so that the inhibition state data (state, pending inhibits and cookie) can be shared among the applet instances. Monitor the inhibited property to also pick up inhibitions created from outside the applet. M +28 -48 applets/brightness/package/contents/ui/NightLightItem.qml M +17 -36 applets/brightness/package/contents/ui/main.qml M +1-1applets/brightness/plugin/CMakeLists.txt R +87 -46 applets/brightness/plugin/nightlightcontrol.cpp [from: applets/brightness/plugin/nightlightmonitor.cpp - 060% similarity] R +28 -6applets/brightness/plugin/nightlightcontrol.h [from: applets/brightness/plugin/nightlightmonitor.h - 082% similarity] R +10 -3applets/brightness/plugin/nightlightcontrol_p.h [from: applets/brightness/plugin/nightlightmonitor_p.h - 081% similarity] M +36 -32 applets/brightness/plugin/nightlightinhibitor.cpp M +17 -18 applets/brightness/plugin/nightlightinhibitor.h https://invent.kde.org/plasma/plasma-workspace/-/commit/ba7cbbf04e2ffe88b0388d2a392513c6b382922f -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 485967] Konsole line numbers render random numbers in margin when scrolling from large to small values.
https://bugs.kde.org/show_bug.cgi?id=485967 Kurt Hindenburg changed: What|Removed |Added Status|REPORTED|CONFIRMED Ever confirmed|0 |1 --- Comment #1 from Kurt Hindenburg --- yea the clearing of previous numbers is not always correct. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 485969] Konsole line numbers render behind the scrollbar at large values.
https://bugs.kde.org/show_bug.cgi?id=485969 Kurt Hindenburg changed: What|Removed |Added Ever confirmed|0 |1 Status|REPORTED|CONFIRMED --- Comment #2 from Kurt Hindenburg --- Yes, need to check # digits and move far to avoid scrollbar. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 485970] Konsole line numbers render atop command output.
https://bugs.kde.org/show_bug.cgi?id=485970 Kurt Hindenburg changed: What|Removed |Added Status|REPORTED|CONFIRMED Ever confirmed|0 |1 --- Comment #2 from Kurt Hindenburg --- Where do you expect the line numbers to show up? We are not going to resize the session size. -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 486095] My Effects/Composition stack is unusable
https://bugs.kde.org/show_bug.cgi?id=486095 batwalk...@gmail.com changed: What|Removed |Added CC||batwalk...@gmail.com --- Comment #1 from batwalk...@gmail.com --- Created attachment 168884 --> https://bugs.kde.org/attachment.cgi?id=168884&action=edit Me trying to interact with the stacks I cant tell if the attachment was actually added because I didn't see it with the ticket, I'm sorry if I submitted it a 2nd time -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 486095] New: My Effects/Composition stack is unusable
https://bugs.kde.org/show_bug.cgi?id=486095 Bug ID: 486095 Summary: My Effects/Composition stack is unusable Classification: I don't know Product: kde Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: major Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: batwalk...@gmail.com Target Milestone: --- SUMMARY I was using kdenlive a 2 days ago, it looked perfectly normal and was able to be used. Today when I opened it to continue editing I added an effect and realized that the effects window just. was physically unusable, the only things you are able to access are the delete button and a few other things, but I won't be able to edit anything the way it si. STEPS TO REPRODUCE 1. I have no idea OBSERVED RESULT The buttons are all scrunched into the bottom left corner and are going outside the area where they are supposed to be. EXPECTED RESULT all the buttons are supposed to be in their normal positions. SOFTWARE/OS VERSIONS OS: Garuda Linux x84_64 Kernal: 6.8.7-zen1-1-zen Kdenlive version: 24.02.2 ADDITIONAL INFORMATION I will post one video of me trying to interact with the stacks -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 486094] New: My Effects/Composition stack is unusable
https://bugs.kde.org/show_bug.cgi?id=486094 Bug ID: 486094 Summary: My Effects/Composition stack is unusable Classification: I don't know Product: kde Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: major Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: batwalk...@gmail.com Target Milestone: --- Created attachment 168883 --> https://bugs.kde.org/attachment.cgi?id=168883&action=edit computer info SUMMARY I was using kdenlive a 2 days ago, it looked perfectly normal and was able to be used. Today when I opened it to continue editing I added an effect and realized that the effects window just. was physically unusable, the only things you are able to access are the delete button and a few other things, but I won't be able to edit anything the way it si. STEPS TO REPRODUCE 1. I have no idea OBSERVED RESULT The buttons are all scrunched into the bottom left corner and are going outside the area where they are supposed to be. EXPECTED RESULT all the buttons are supposed to be in their normal positions. SOFTWARE/OS VERSIONS I will post this information in attachments as images ADDITIONAL INFORMATION I will post one video of me trying to interact with the stacks -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 486093] -Wstrict-aliasing in tests
https://bugs.kde.org/show_bug.cgi?id=486093 --- Comment #1 from Sam James --- As a workaround, we're building tests with: ``` emake CFLAGS="${CFLAGS} -fno-strict-aliasing" LDFLAGS="${LDFLAGS} -Wl,-z,notext" check ``` for now. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 486093] New: -Wstrict-aliasing in tests
https://bugs.kde.org/show_bug.cgi?id=486093 Bug ID: 486093 Summary: -Wstrict-aliasing in tests Classification: Developer tools Product: valgrind Version: 3.22 GIT Platform: Other OS: Other Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: jsew...@acm.org Reporter: s...@gentoo.org Target Milestone: --- THere's a lot of -Wstrict-aliasing instances in the testsuite. In Gentoo, we try to recommend people to use -Werror=strict-aliasing -Werror=lto-type-mismatch -Werror=some-other-bits when using LTO to help find likely runtime problems (Valgrind isn't LTO-compaitble for other reasons but that's neither here nor there for this). When building Valgrind with such, we get: ``` x86_64-pc-linux-gnu-gcc -DHAVE_CONFIG_H -I. -I../../.. -I../../.. -I../../../include -I../../../coregrind -I../../../include -I../../../VEX/pub -I../../../VEX/pub -DVGA_amd64=1 -DVGO_l inux=1 -DVGP_amd64_linux=1 -DVGPV_amd64_linux_vanilla=1 -DVGA_SEC_x86=1 -DVGP_SEC_amd64_linux=1 -Winline -Wall -Wshadow -Wno-long-long -g -fno-stack-protector -m64 -O -ffast-math - mfpmath=387 -mfancy-math-387 -O3 -march=native -mtls-dialect=gnu2 -fno-semantic-interposition -pipe -fcf-protection=none -fdiagnostics-color=always -fdiagnostics-urls=never -frecord-gcc -switches -Wa,-O2 -Wa,-mtune=znver2 -Wstrict-aliasing -Wfree-nonheap-object -Werror=lto-type-mismatch -Werror=strict-aliasing -Werror=odr -Wstrict-aliasing -Wfree-nonheap-object -Werror =lto-type-mismatch -Werror=strict-aliasing -Werror=odr -Wbuiltin-declaration-mismatch -ggdb3 -Wformat -Wformat-security -Waddress -Warray-bounds -Wfree-nonheap-object -Wint-to-pointer-c ast -Wmain -Wnonnull -Wodr -Wreturn-type -Wsizeof-pointer-memaccess -Wstrict-aliasing -Wstring-compare -Wuninitialized -Wvarargs -fno-stack-protector -fno-harden-control-flow-redundancy -c -o more_x87_fp-more_x87_fp.o `test -f 'more_x87_fp.c' || echo './'`more_x87_fp.c make[5]: 'shr_edx' is up to date. more_x87_fp.c: In function ‘test_fcvt’: more_x87_fp.c:108:28: error: dereferencing type-punned pointer will break strict-aliasing rules [-Werror=strict-aliasing] 108 | printf("a=%016llx\n", *(long long *)&a); |^~~ more_x87_fp.c:109:34: error: dereferencing type-punned pointer will break strict-aliasing rules [-Werror=strict-aliasing] 109 | printf("la=%016llx %04x\n", *(long long *)&la, | ^~~~ more_x87_fp.c:110:12: warning: ‘la’ is used uninitialized [-Wuninitialized] 110 |*(unsigned short *)((char *)(&la) + 8)); |^~ more_x87_fp.c:96:17: note: ‘la’ declared here 96 | long double la; | ^~ cc1: some warnings being treated as errors x86_64-pc-linux-gnu-gcc -DHAVE_CONFIG_H -I. -I../../.. -I../../.. -I../../../include -I../../../coregrind -I../../../include -I../../../VEX/pub -I../../../VEX/pub -DVGA_amd64=1 -DVGO_l inux=1 -DVGP_amd64_linux=1 -DVGPV_amd64_linux_vanilla=1 -DVGA_SEC_x86=1 -DVGP_SEC_amd64_linux=1 -Winline -Wall -Wshadow -Wno-long-long -g -fno-stack-protector -m32 -mmmx -msse -O3 - march=native -mtls-dialect=gnu2 -fno-semantic-interposition -pipe -fcf-protection=none -fdiagnostics-color=always -fdiagnostics-urls=never -frecord-gcc-switches -Wa,-O2 -Wa,-mtune=znver 2 -Wstrict-aliasing -Wfree-nonheap-object -Werror=lto-type-mismatch -Werror=strict-aliasing -Werror=odr -Wstrict-aliasing -Wfree-nonheap-object -Werror=lto-type-mismatch -Werror=strict- aliasing -Werror=odr -Wbuiltin-declaration-mismatch -ggdb3 -Wformat -Wformat-security -Waddress -Warray-bounds -Wfree-nonheap-object -Wint-to-pointer-cast -Wmain -Wnonnull -Wodr -Wretur n-type -Wsizeof-pointer-memaccess -Wstrict-aliasing -Wstring-compare -Wuninitialized -Wvarargs -fno-stack-protector -fno-harden-control-flow-redundancy -c -o more_x86_fp.o more_x86_fp.c more_x86_fp.c: In function ‘test_fcvt’: more_x86_fp.c:98:28: error: dereferencing type-punned pointer will break strict-aliasing rules [-Werror=strict-aliasing] 98 | printf("a=%016llx\n", *(long long *)&a); |^~~ more_x86_fp.c:99:34: error: dereferencing type-punned pointer will break strict-aliasing rules [-Werror=strict-aliasing] 99 | printf("la=%016llx %04x\n", *(long long *)&la, | ^~~~ more_x86_fp.c:100:12: warning: ‘la’ is used uninitialized [-Wuninitialized] 100 |*(unsigned short *)((char *)(&la) + 8)); |^~ more_x86_fp.c:86:17: note: ‘la’ declared here 86 | long double la; | ^~ cc1: some warnings being treated as errors ``` This is with `gcc version 14.0.1 20240423 (experimental) 0c8e99e5c32be9f2604f3c330814993f29818037 (Gentoo Hardened
[konsole] [Bug 478181] Problem in rendering a specific Farsi/Arabic character combination
https://bugs.kde.org/show_bug.cgi?id=478181 Kurt Hindenburg changed: What|Removed |Added Latest Commit||https://invent.kde.org/util ||ities/konsole/-/commit/5f1f ||d57b50e7e3899ba682c021697b6 ||a61194f76 Resolution|--- |FIXED Status|ASSIGNED|RESOLVED --- Comment #12 from Kurt Hindenburg --- Git commit 5f1fd57b50e7e3899ba682c021697b6a61194f76 by Kurt Hindenburg, on behalf of Matan Ziv-Av. Committed on 24/04/2024 at 22:56. Pushed by hindenburg into branch 'master'. Don't use Lam-Alef ligatures when shaping arabic letters ICU automatically shapes the two letters Lam and Alef to a single ligature, so it is necessary to undo it. M +48 -1src/terminalDisplay/TerminalDisplay.cpp https://invent.kde.org/utilities/konsole/-/commit/5f1fd57b50e7e3899ba682c021697b6a61194f76 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 486074] Baloo write like crazy and freeze system
https://bugs.kde.org/show_bug.cgi?id=486074 tagwer...@innerjoin.org changed: What|Removed |Added CC||tagwer...@innerjoin.org -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 483115] Lost hotkey assignment and reappearing deleted hotkey entries in KDE 6
https://bugs.kde.org/show_bug.cgi?id=483115 waterlub...@rocketmail.com changed: What|Removed |Added CC||waterlub...@rocketmail.com --- Comment #4 from waterlub...@rocketmail.com --- Looks like you're having the same bug as me (https://bugs.kde.org/show_bug.cgi?id=485659) -- You are receiving this mail because: You are watching all bug changes.
[Elisa] [Bug 486092] New: playback does not advance to next track in playlist
https://bugs.kde.org/show_bug.cgi?id=486092 Bug ID: 486092 Summary: playback does not advance to next track in playlist Classification: Applications Product: Elisa Version: 24.02.1 Platform: Other OS: Linux Status: REPORTED Severity: major Priority: NOR Component: general Assignee: matthieu_gall...@yahoo.fr Reporter: b...@gmx.com Target Milestone: --- SUMMARY Upon upgrading to KDE 6 / Fedora 40, Elisa will no longer advance playback to the next track in the playlist after any track finishes. STEPS TO REPRODUCE 1. Load any tracks into the playlist 2. Press play 3. Wait for the current track to finish, or seek towards the end of the track OBSERVED RESULT Elisa stops playing when the currently playing track finishes EXPECTED RESULT Elisa continues playing the rest of the playlist SOFTWARE/OS VERSIONS Linux/KDE Plasma: Fedora 40 KDE Plasma Version: 6.0.0 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.2 ADDITIONAL INFORMATION Tracks play fine when selecting them in the playlist; there's nothing wrong with the next track that's preventing playback. Changing repeat mode (none/playlist/track) doesn't do anything; Elisa won't play the next track regardless of the repeat mode. Shuffle mode doesn't make a difference either. I removed ~/.config/elisarc and ~/.local/share/elisa/elisaDatabase.db and restarted Elisa, but this did not fix the issue. Using pipewire-pulseaudio-1.0.5-1.fc40.x86_64 -- You are receiving this mail because: You are watching all bug changes.
[plasma-wayland-protocols] [Bug 486091] New: Lost connection to Wayland compositor with 8000hz mouse poll rate
https://bugs.kde.org/show_bug.cgi?id=486091 Bug ID: 486091 Summary: Lost connection to Wayland compositor with 8000hz mouse poll rate Classification: Plasma Product: plasma-wayland-protocols Version: unspecified Platform: Other OS: Other Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: hunterofgy...@gmail.com CC: aleix...@kde.org Target Milestone: --- SUMMARY If my mouse poll rate is set to 8000hz various applications crash randomloy and often. Most notably virt-manager and Thunderbird/Betterbird. The error given is "Lost connection to Wayland compositor" STEPS TO REPRODUCE 1. Buy Razer Deathadder V3 2. Install Polychromatic and set mouse HZ to 8000 3. Launch virt-manager and start a VM and then click to open the window to the VM it will crash or Launch thunderbird and try to drag some attachments into a new email and it will probably crash OBSERVED RESULT Applications hard quit randomly. EXPECTED RESULT Applications not hard quit randomly. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Artix OpenRC KDE Plasma Version: 6.0.4 KDE Frameworks Version: 6.1.0 Qt Version: 6.7.0 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 483163] On X11 with compositing turned on, blank screen on lock screen when using Breeze Plasma style
https://bugs.kde.org/show_bug.cgi?id=483163 Joshua J. Kugler changed: What|Removed |Added CC||jos...@joshuakugler.com --- Comment #28 from Joshua J. Kugler --- I don't know if this is related, but I'll sometimes have a black lock screen. But, if I blind-type my password, it unlocks, and displays the desktop without issue. Plasma 6.0.4 on X11 -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 484038] Make it clear that screen recording isn't supported on X11
https://bugs.kde.org/show_bug.cgi?id=484038 John Veness changed: What|Removed |Added CC||john@pelago.org.uk -- You are receiving this mail because: You are watching all bug changes.
[Haruna] [Bug 486079] Intel Quicksync support
https://bugs.kde.org/show_bug.cgi?id=486079 --- Comment #1 from george fb --- You should be able to set it in "Settings > Custom Commands" `set vd "h264_qsv,hevc_qsv ..."` -- You are receiving this mail because: You are watching all bug changes.
[www.kde.org] [Bug 485961] KDE Subversion site references non-existent review board URI.
https://bugs.kde.org/show_bug.cgi?id=485961 Ben Cooksley changed: What|Removed |Added Resolution|--- |INTENTIONAL Status|REPORTED|RESOLVED --- Comment #4 from Ben Cooksley --- Yeah, in this case we'll leave it in place for historical accuracy as it isn't harming anything. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 485827] Virtio VM has upside down cursor after kwin 6.0.4
https://bugs.kde.org/show_bug.cgi?id=485827 --- Comment #6 from Reilly Brogan --- (In reply to postix from comment #4) > Fedora 40 will be released next this week with Plasma 6.0.4 and Kernel 6.8 > and I am wondering if could run into this issue when upgrading from F39: > Does this bug affect all sorts of guests (like Win10) with Plasma Wayland as > a host? Is setting QXL GPU type the only workaround? I believe it only affects VMs using Plasma Wayland as the guest actually. The patch for it has also already been added to the Plasma/6.0 branch and will be in the 6.0.5 release, or your Plasma maintainers can apply it to kwin 6.0.4/6.0.4.1 (it applies cleanly). -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 486090] New: mp4 files cannot be opened anymore, but worked before
https://bugs.kde.org/show_bug.cgi?id=486090 Bug ID: 486090 Summary: mp4 files cannot be opened anymore, but worked before Classification: Applications Product: kdenlive Version: 24.02.2 Platform: Arch Linux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Video Display & Export Assignee: j...@kdenlive.org Reporter: ad...@arkades.org Target Milestone: --- I want to open certain mp4 files which I recorded with Sony Actioncam. It always worked, but since the latest update I get an error: "Cannot open file /data/C0001.MP4" This totally breaks everything I worked on. -- You are receiving this mail because: You are watching all bug changes.
[konqueror] [Bug 485670] Konqueror crashes upon clicking a bookmark folder from the bookmark toolbar
https://bugs.kde.org/show_bug.cgi?id=485670 Stefano Crocco changed: What|Removed |Added Latest Commit|https://invent.kde.org/netw |https://invent.kde.org/netw |ork/konqueror/-/commit/791a |ork/konqueror/-/commit/e908 |14f78a693cd923b0056ad50184a |b1ead2a971b7b04c32416d1b1fb |18b24fc03 |684b9e047 --- Comment #3 from Stefano Crocco --- Git commit e908b1ead2a971b7b04c32416d1b1fb684b9e047 by Stefano Crocco. Committed on 24/04/2024 at 20:48. Pushed by stefanocrocco into branch 'release/24.05'. Fix crash when clicking on bookmark toolbar and allow configuring add bookmark shortcut (cherry picked from commit 791a14f78a693cd923b0056ad50184a18b24fc03) 25b41598 Fix crash when clicking on bookmark toolbar and allow configuring add bookmark shortcut M +1-1src/konqbookmarkbar.cpp M +0-1src/konqbookmarkbar.h M +1-3src/konqbookmarkmenu.cpp M +3-6src/konqbookmarkmenu.h M +3-10 src/konqmainwindow.cpp M +0-1src/konqmainwindow.h https://invent.kde.org/network/konqueror/-/commit/e908b1ead2a971b7b04c32416d1b1fb684b9e047 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 485456] Qith Qt 6.7, System Tray popup is inappropriately resized to a tiny nub
https://bugs.kde.org/show_bug.cgi?id=485456 Thomas changed: What|Removed |Added CC||thomas.bre...@informatik.un ||i-oldenburg.de -- You are receiving this mail because: You are watching all bug changes.
[konqueror] [Bug 485670] Konqueror crashes upon clicking a bookmark folder from the bookmark toolbar
https://bugs.kde.org/show_bug.cgi?id=485670 Stefano Crocco changed: What|Removed |Added Status|ASSIGNED|RESOLVED Latest Commit||https://invent.kde.org/netw ||ork/konqueror/-/commit/791a ||14f78a693cd923b0056ad50184a ||18b24fc03 Resolution|--- |FIXED --- Comment #2 from Stefano Crocco --- Git commit 791a14f78a693cd923b0056ad50184a18b24fc03 by Stefano Crocco. Committed on 24/04/2024 at 20:42. Pushed by stefanocrocco into branch 'master'. Fix crash when clicking on bookmark toolbar and allow configuring add bookmark shortcut M +1-1src/konqbookmarkbar.cpp M +0-1src/konqbookmarkbar.h M +1-3src/konqbookmarkmenu.cpp M +3-6src/konqbookmarkmenu.h M +3-10 src/konqmainwindow.cpp M +0-1src/konqmainwindow.h https://invent.kde.org/network/konqueror/-/commit/791a14f78a693cd923b0056ad50184a18b24fc03 -- You are receiving this mail because: You are watching all bug changes.
[PlasmaTube] [Bug 485810] Videos played in a detached window
https://bugs.kde.org/show_bug.cgi?id=485810 Ulf Bartholomäus changed: What|Removed |Added CC||u...@gmx.net --- Comment #1 from Ulf Bartholomäus --- Same at my side. Operating System: openSUSE Tumbleweed KDE Plasma Version: KDE Frameworks Version: 6.1.0 Qt Version: 6.7.0 Kernel Version: 6.8.7-1-default OS-Type: 64 Processor: 8 × AMD Ryzen 7 4700U with Radeon Graphics Memory: 30,8 GiB Window System: Wayland -- You are receiving this mail because: You are watching all bug changes.
[konqueror] [Bug 484437] white page shown before opening pages
https://bugs.kde.org/show_bug.cgi?id=484437 Stefano Crocco changed: What|Removed |Added Status|RESOLVED|REOPENED Resolution|FIXED |--- --- Comment #5 from Stefano Crocco --- Then I misunderstood your problem. I removed my previous changes, as they wouldn't solve your problem. What I'll do is to add an option in the Stylesheet page which allows you to change the background of the page: setting this to the same colour you use as background in your stylesheet should fix your issue. -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 483140] The Default/Custom shortcut for "Capture Active Window" does not work.
https://bugs.kde.org/show_bug.cgi?id=483140 --- Comment #1 from Jeff Gila --- Yesterday I replaced my SSD and did a fresh install of EndeavourOS. And now all the default shortcuts are working again. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 457847] kwin becomes unresponsive, need to restart session
https://bugs.kde.org/show_bug.cgi?id=457847 Paul changed: What|Removed |Added CC|paulhollen...@gmail.com | -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 486077] Okular window does not activate when opening pdf file from nautilus ("Files" application in Gnome)
https://bugs.kde.org/show_bug.cgi?id=486077 fanzhuyi...@gmail.com changed: What|Removed |Added Resolution|--- |UNMAINTAINED Status|REPORTED|RESOLVED CC||fanzhuyi...@gmail.com --- Comment #1 from fanzhuyi...@gmail.com --- Thank you for your bug report! Debian advises users to not submit bugs upstream (https://www.debian.org/Bugs/Reporting), as this version of the KDE software is out of support from KDE, and so it's possible that the bug exists only in Debian at this point. Could you report the bug to Debian using the report bug utility (https://packages.debian.org/stable/utils/reportbug)? If necessary, the maintainer of the package will forward the bug upstream. Thanks for understanding! -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 486070] Quitting an app that sent a flood of notifications doesn't stop the flood
https://bugs.kde.org/show_bug.cgi?id=486070 fanzhuyi...@gmail.com changed: What|Removed |Added CC||fanzhuyi...@gmail.com --- Comment #1 from fanzhuyi...@gmail.com --- Humm not sure whether we can feasibly implement this functionality -- all notifications are received and queued for display, and the notification widget has no knowledge of the status of the app that sent the notifications. I think that fixing BUG 441906 is the way to go. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 477317] Non-floating Panel with "Fit Content" does not take the correct width on plasmashell start if Digital Clock is present, but resizes to correct width if "Edit Mode" is activa
https://bugs.kde.org/show_bug.cgi?id=477317 fanzhuyi...@gmail.com changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=486049 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 486049] floating panel having the wrong size under wayland
https://bugs.kde.org/show_bug.cgi?id=486049 fanzhuyi...@gmail.com changed: What|Removed |Added CC||fanzhuyi...@gmail.com See Also||https://bugs.kde.org/show_b ||ug.cgi?id=477317 -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 467328] Okular mismanages fonts embedded in PDF document when printing
https://bugs.kde.org/show_bug.cgi?id=467328 medin changed: What|Removed |Added CC||med.medin.2...@gmail.com --- Comment #14 from medin --- (In reply to Oliver Sander from comment #13) > 1) Yes, poppler is used > > 2) On Windows, rasterization resolution follows the printer. Elsewhere, > 300dpi is hardcoded. That conversion also messes with embedded fonts when you use virtual PDF to file. See https://discuss.kde.org/t/okular-printing-bug/14546/8 -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 377966] arm64 unhandled instruction dc zva
https://bugs.kde.org/show_bug.cgi?id=377966 Reimar Döffinger changed: What|Removed |Added CC||k...@reimardoeffinger.de --- Comment #9 from Reimar Döffinger --- >From https://github.com/LouisBrunner/valgrind-macos/issues/56 : A quick hack to implement the instruction. It does not address other points raised, like reading DCZID_EL0 maybe should flag the instruction as supported and indicate the size. I felt it safer to discourage software from using this instruction by keeping the current implementation reporting it as not supported. Patch for reference for anyone who wants to work on something clean enough to merge: diff --git a/VEX/priv/guest_arm64_toIR.c b/VEX/priv/guest_arm64_toIR.c index 51c949def..9d04c4303 100644 --- a/VEX/priv/guest_arm64_toIR.c +++ b/VEX/priv/guest_arm64_toIR.c @@ -7948,6 +7948,30 @@ Bool dis_ARM64_branch_etc(/*MB_OUT*/DisResult* dres, UInt insn, return True; } + /* -- DC_ZVA -- */ + /* D5 0B 74 001 Rt dc zva, rT + */ + if ((INSN(31,0) & 0xFFE0) == 0xD50B7420) { + /* Exactly the same scheme as for IC IVAU, except we observe the + dMinLine size. */ + /* We will always be provided with a valid dMinLine value. */ + vassert(archinfo->arm64_dMinLine_lg2_szB >= 2 + && archinfo->arm64_dMinLine_lg2_szB <= 17); + /* Round the requested address, in rT, down to the start of the + containing block. */ + UInt tt = INSN(4,0); + ULong lineszB = 1ULL << archinfo->arm64_dMinLine_lg2_szB; + IRTemp addr= newTemp(Ity_I64); + assign( addr, binop( Iop_And64, + getIReg64orZR(tt), + mkU64(~(lineszB - 1))) ); + for (ULong o = 0; o < lineszB; o += 8) + { + storeLE(binop(Iop_Add64,mkexpr(addr),mkU64(o)), mkU64(0)); + } + DIP("dc zva, %s\n", nameIReg64orZR(tt)); + return True; + } /* -- DC_CVAU -- */ /* D5 0B 7B 001 Rt dc cvau, rT D5 0B 7E 001 Rt dc civac, rT -- You are receiving this mail because: You are watching all bug changes.
[plasma-pa] [Bug 486089] Microphone UI shows opposite option when clicked
https://bugs.kde.org/show_bug.cgi?id=486089 --- Comment #2 from Andrew Baker --- Created attachment 168882 --> https://bugs.kde.org/attachment.cgi?id=168882&action=edit Behaviour shown when unmuting mic -- You are receiving this mail because: You are watching all bug changes.
[plasma-pa] [Bug 486089] Microphone UI shows opposite option when clicked
https://bugs.kde.org/show_bug.cgi?id=486089 --- Comment #1 from Andrew Baker --- Created attachment 168881 --> https://bugs.kde.org/attachment.cgi?id=168881&action=edit Behaviour shown when muting mic -- You are receiving this mail because: You are watching all bug changes.
[plasma-pa] [Bug 486089] New: Microphone UI shows opposite option when clicked
https://bugs.kde.org/show_bug.cgi?id=486089 Bug ID: 486089 Summary: Microphone UI shows opposite option when clicked Classification: Plasma Product: plasma-pa Version: 6.0.3 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: applet Assignee: plasma-b...@kde.org Reporter: andrew.ba...@andrewbaker.uk CC: isma...@gmail.com, m...@ratijas.tk Target Milestone: --- SUMMARY Clicking the microphone icon in the panel when using microphone, mutes the mic as expected but then shows the microphone volume level. When the microphone is unmuted it shows Microphone Muted on screen STEPS TO REPRODUCE 1. Open application that uses microphone 2. Click microphone icon to mute 3. Click microphone icon to unmute OBSERVED RESULT Mic volume level shown when muting microphone from panel Microphone muted shown when unmuting microphone from panel EXPECTED RESULT Mic volume level shown when unmuting microphone from panel Microphone muted shown when muting microphone from panel SOFTWARE/OS VERSIONS Linux/KDE Plasma: Fedora Linux 40 (available in About System) KDE Plasma Version: 6.0.3 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.2 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 486086] Various visual artifacts in Nicotine+
https://bugs.kde.org/show_bug.cgi?id=486086 regis changed: What|Removed |Added CC||paregistr...@yahoo.es -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 473904] kwin_wayland crashes in KWin::Window::clientMaximizedStateChanged() when de-maximizing a maximized window
https://bugs.kde.org/show_bug.cgi?id=473904 --- Comment #6 from jdear2...@gmail.com --- (In reply to Zamundaaa from comment #5) > Does this still happen with Plasma 6? A similar issue happens however I haven't been able to back trace it so I can't properly answer. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 457847] kwin becomes unresponsive, need to restart session
https://bugs.kde.org/show_bug.cgi?id=457847 --- Comment #35 from Danir Toma --- I'd like to add that the problem still persists on Plasma 6. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 486088] Crash while viewing video
https://bugs.kde.org/show_bug.cgi?id=486088 Maik Qualmann changed: What|Removed |Added Version Fixed In||8.4.0 Resolution|--- |FIXED CC||metzping...@gmail.com Status|REPORTED|RESOLVED --- Comment #2 from Maik Qualmann --- Crash is fixed with Bug 484818 and Bug 484815 in the QtAVPlayer with Qt5 Vesion. Maik -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 486088] Crash while viewing video
https://bugs.kde.org/show_bug.cgi?id=486088 caulier.gil...@gmail.com changed: What|Removed |Added Component|general |Preview-Video CC||caulier.gil...@gmail.com --- Comment #1 from caulier.gil...@gmail.com --- Please try the last AppImage Linux bundle based on Qt6. It use Qt::Multimedia with ffmpeg. https://files.kde.org/digikam/ Gilles Caulier -- You are receiving this mail because: You are watching all bug changes.
[Tokodon] [Bug 483184] Freezes when trying to login
https://bugs.kde.org/show_bug.cgi?id=483184 Daniele Verducci changed: What|Removed |Added CC||daniele.verdu...@ichibi.eu --- Comment #1 from Daniele Verducci --- I can confirm it is happening to me as well. I'd like to add that the bug manifests itself in different ways between Tokodon installed from PostmarketOS package manager (apk) and the same Tokodon version installed via Flatpak. In the first case I encountered the behavior described by Devin Lin. In the Flatpak case, an authorization window is opened, but it's completely empty. Note that I'm trying to login to a Pleroma instance. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 432366] Add option to change scroll step size for brightness
https://bugs.kde.org/show_bug.cgi?id=432366 --- Comment #8 from medin --- (In reply to t.soernes from comment #7) > No it works for brightness too. Hold the shift button and scroll the night > light widget / plasmoid. Brightness adjusts in 1% steps in Plasma 6. If it was also added for brightness, then it's half broken. I'm on Plasma 6.0.4 and holding shift while scrolling brightness widget icon doesn't increase/decrease brightness by 1%. But when you click on brightness widget, and it opens then you move the mouse pointer over the brightness slider, and you hold shift while scrolling it seems to increase/decrease by 1% in that case. Operating System: Manjaro Linux KDE Plasma Version: 6.0.4 KDE Frameworks Version: 6.1.0 Qt Version: 6.7.0 Kernel Version: 6.8.7-1-MANJARO (64-bit) Graphics Platform: Wayland -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 486088] New: Crash while viewing video
https://bugs.kde.org/show_bug.cgi?id=486088 Bug ID: 486088 Summary: Crash while viewing video Classification: Applications Product: digikam Version: 8.3.0 Platform: Compiled Sources OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: digikam-bugs-n...@kde.org Reporter: ges...@blackrosetech.com Target Milestone: --- Application: digikam (8.3.0) (Compiled from sources) Qt Version: 5.15.3 Frameworks Version: 5.98.0 Operating System: Linux 6.5.0-28-generic x86_64 Windowing System: X11 Distribution: Ubuntu 22.04.4 LTS DrKonqi: 5.24.5 [KCrashBackend] -- Information about the crash: - What I was doing when the application crashed: I was using the integrated video player and moving from video to video. The reporter is unsure if this crash is reproducible. -- Backtrace: Application: digiKam (digikam), signal: Segmentation fault [KCrash Handler] #4 0x79ef50ace4bb in QReadWriteLock::lockForRead() () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x79ef53b4373c in () at /lib/x86_64-linux-gnu/libQt5Sql.so.5 #6 0x79ef53b498f5 in QSqlDatabase::database(QString const&, bool) () at /lib/x86_64-linux-gnu/libQt5Sql.so.5 #7 0x79ef52b93a17 in Digikam::DbEngineThreadData::closeDatabase() (this=0x79ef20011ff0) at /home/gessel/projects/digikam/core/libs/database/engine/dbenginebackend.cpp:87 #8 0x79ef52b9398c in Digikam::DbEngineThreadData::~DbEngineThreadData() (this=0x79ef20011ff0, __in_chrg=) at /home/gessel/projects/digikam/core/libs/database/engine/dbenginebackend.cpp:79 #9 0x79ef52b9d01e in qThreadStorage_deleteData(void*, Digikam::DbEngineThreadData**) (d=0x79ef20011ff0) at /usr/include/x86_64-linux-gnu/qt5/QtCore/qthreadstorage.h:92 #10 0x79ef52b9c87f in QThreadStorage::deleteData(void*) (x=0x79ef20011ff0) at /usr/include/x86_64-linux-gnu/qt5/QtCore/qthreadstorage.h:135 #11 0x79ef50ad23df in QThreadStorageData::finish(void**) () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #12 0x79ef50acc391 in () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #13 0x79ef50accca9 in () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #14 0x79ef50294ac3 in start_thread (arg=) at ./nptl/pthread_create.c:442 #15 0x79ef50326850 in clone3 () at ../sysdeps/unix/sysv/linux/x86_64/clone3.S:81 Thread 2 (Thread 0x79ef30e84640 (LWP 1626323) "QXcbEventQueue"): #1 0x79ef401267e2 in () at /lib/x86_64-linux-gnu/libxcb.so.1 #2 0x79ef4012822c in xcb_wait_for_event () at /lib/x86_64-linux-gnu/libxcb.so.1 #3 0x79ef30ef7d08 in () at /lib/x86_64-linux-gnu/libQt5XcbQpa.so.5 #4 0x79ef50accca1 in () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x79ef50294ac3 in start_thread (arg=) at ./nptl/pthread_create.c:442 #6 0x79ef50326850 in clone3 () at ../sysdeps/unix/sysv/linux/x86_64/clone3.S:81 Thread 1 (Thread 0x79ef31e3fa80 (LWP 1626314) "digikam"): #1 __futex_abstimed_wait_common (cancel=true, private=0, abstime=0x0, clockid=0, expected=0, futex_word=0x639abe988ff0) at ./nptl/futex-internal.c:87 #2 __GI___futex_abstimed_wait_cancelable64 (futex_word=futex_word@entry=0x639abe988ff0, expected=expected@entry=0, clockid=clockid@entry=0, abstime=abstime@entry=0x0, private=private@entry=0) at ./nptl/futex-internal.c:139 #3 0x79ef50293a41 in __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x639abe988fa0, cond=0x639abe988fc8) at ./nptl/pthread_cond_wait.c:503 #4 ___pthread_cond_wait (cond=0x639abe988fc8, mutex=0x639abe988fa0) at ./nptl/pthread_cond_wait.c:627 #5 0x79ef50ad2ceb in QWaitCondition::wait(QMutex*, QDeadlineTimer) () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x79ef50acc969 in QThread::wait(QDeadlineTimer) () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x79ef53eeeda5 in Digikam::ScanController::shutDown() (this=0x79ef546886c0 ) at /home/gessel/projects/digikam/core/libs/database/utils/scan/scancontroller_stop.cpp:123 #8 0x79ef53ee6bcc in Digikam::ScanController::~ScanController() (this=0x79ef546886c0 , __in_chrg=) at /home/gessel/projects/digikam/core/libs/database/utils/scan/scancontroller.cpp:111 #9 0x79ef53ee9136 in Digikam::ScanControllerCreator::~ScanControllerCreator() (this=0x79ef546886c0 , __in_chrg=) at /home/gessel/projects/digikam/core/libs/database/utils/scan/scancontroller_p.h:168 #10 0x79ef53ee6448 in Holder::~Holder() (this=0x79ef546886c0 , __in_chrg=) at /home/gessel/projects/digikam/core/libs/database/utils/scan/scancontroller.cpp:41 #11 0x79ef50245495 in __run_exit_handlers (status=1, listp=0x79ef5041a838 <__exit_funcs>, run_list_atexit=run_list_atexit@entry=true, run_dtors=run_dtors@entry=true) at ./stdlib/exit.c:113 #12 0x79ef50245610 in __GI_exit (status=) at ./stdlib/exit.c:143 #13 0x79ef491b8170 in () at /lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #14 0x7fff in () #15 0x in (
[Haruna] [Bug 485892] Do not prevent playback when unknown options are used
https://bugs.kde.org/show_bug.cgi?id=485892 george fb changed: What|Removed |Added Resolution|--- |NOT A BUG Status|REOPENED|RESOLVED --- Comment #5 from george fb --- Then use mpv. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 486081] Frame swapping in WebRTC screensharing while moving the mouse
https://bugs.kde.org/show_bug.cgi?id=486081 Aleksander changed: What|Removed |Added CC||aleksan...@olekolek1000.com --- Comment #1 from Aleksander --- Can confirm. Operating System: Arch Linux KDE Plasma Version: 6.0.3 KDE Frameworks Version: 6.0.0 Qt Version: 6.7.0 Kernel Version: 6.9.0-rc3-1-mainline (64-bit) Graphics Platform: Wayland Processors: 24 × AMD Ryzen 9 5900X 12-Core Processor Memory: 31,3 GiB of RAM Graphics Processor: AMD Radeon RX 7800 XT -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 486087] Mouse pointer has blue-ish shaddow/halo when Night Light kicks in
https://bugs.kde.org/show_bug.cgi?id=486087 --- Comment #1 from Mario Splivalo --- Created attachment 168880 --> https://bugs.kde.org/attachment.cgi?id=168880&action=edit Screenshot of a blue pointer, another one -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 486087] New: Mouse pointer has blue-ish shaddow/halo when Night Light kicks in
https://bugs.kde.org/show_bug.cgi?id=486087 Bug ID: 486087 Summary: Mouse pointer has blue-ish shaddow/halo when Night Light kicks in Classification: KDE Neon Product: neon Version: unspecified Platform: Neon OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: neon-b...@kde.org Reporter: mario+bugs.kde@splivalo.hr CC: j...@jriddell.org, neon-b...@kde.org Target Milestone: --- Created attachment 168879 --> https://bugs.kde.org/attachment.cgi?id=168879&action=edit Screenshot of blue pointer. SUMMARY With Night Light enabled and activated the mouse pointer shows blue-ish shade or halo around it. STEPS TO REPRODUCE 1. Enable Night Light 2. Force Night Light to activate OBSERVED RESULT The mouse pointer has bloue shade around it. EXPECTED RESULT The mouse pointer should not have blue shade around it. SOFTWARE/OS VERSIONS Linux/KDE Plasma: KDE Neon 6.0 KDE Plasma Version: 6.0.4 KDE Frameworks Version: 6.1.0 Qt Version: 6.7.0 Linux: 6.5.0-28-generic (64-bit) Nvidia drivers: 550.67 Wayland ADDITIONAL INFORMATION This bug did not exist on Plasma 6.0.3, only after upgrading to 6.0.4 the blue 'shade' became visible. (The attached screenshot is taken by phone because I can't get blue shade using Spectacle). -- You are receiving this mail because: You are watching all bug changes.
[Haruna] [Bug 485892] Do not prevent playback when unknown options are used
https://bugs.kde.org/show_bug.cgi?id=485892 Matthias changed: What|Removed |Added Ever confirmed|0 |1 Resolution|NOT A BUG |--- Status|RESOLVED|REOPENED --- Comment #4 from Matthias --- It does show the syntax that I use, and not the syntax that you suggest? Like... ?? -- You are receiving this mail because: You are watching all bug changes.