[plasmashell] [Bug 455252] Applications do not autostart with systemd boot
https://bugs.kde.org/show_bug.cgi?id=455252 David Edmundson changed: What|Removed |Added Resolution|--- |WAITINGFORINFO Status|REPORTED|NEEDSINFO --- Comment #5 from David Edmundson --- Marking as needsinfo. I was unable to reproduce any issue locally. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 368104] files/folders in trash get copied to /tmp while previews are generated
https://bugs.kde.org/show_bug.cgi?id=368104 Philippe ROUBACH changed: What|Removed |Added Status|RESOLVED|REOPENED Resolution|FIXED |--- --- Comment #19 from Philippe ROUBACH --- I confirm. The problem is still there for movies (ts, mp4). It seems this problem occurs with movies you fly over with mouse cursor. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 455273] "From " filter fails to identify sender when they also have a name
https://bugs.kde.org/show_bug.cgi?id=455273 Laurent Montel changed: What|Removed |Added Resolution|--- |FIXED Version Fixed In||5.21.0 Latest Commit||https://invent.kde.org/pim/ ||mailcommon/commit/15d84794c ||3b14326f7b9bacd49f5184a9ca9 ||0ce6 Status|REPORTED|RESOLVED --- Comment #2 from Laurent Montel --- Git commit 15d84794c3b14326f7b9bacd49f5184a9ca90ce6 by Laurent Montel. Committed on 15/06/2022 at 05:23. Pushed by mlaurent into branch 'master'. Fix 455273: "From " filter fails to identify sender when they also have a name FIXED-IN: 5.21.0 M +14 -0src/search/searchrule/searchrulestring.cpp https://invent.kde.org/pim/mailcommon/commit/15d84794c3b14326f7b9bacd49f5184a9ca90ce6 -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 455168] want/need more 'const' in Valgrind source code
https://bugs.kde.org/show_bug.cgi?id=455168 --- Comment #5 from Paul Floyd --- On amd64 most files get compiled twice, once for x86 and once for amd64. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 455304] New: Make screenshots bigger
https://bugs.kde.org/show_bug.cgi?id=455304 Bug ID: 455304 Summary: Make screenshots bigger Product: Discover Version: unspecified Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: discover Assignee: lei...@leinir.dk Reporter: kinof...@gmail.com CC: aleix...@kde.org Target Milestone: --- Created attachment 149725 --> https://bugs.kde.org/attachment.cgi?id=149725=edit Application screenshot example We could make screenshot bigger in the applications page, trying to check what an application looks like without opening the screenshot overlay thing is very hard, maybe we could make the screenshot preview really good, like very legible and easy to see and then remove the screenshot overlay thing. STEPS TO REPRODUCE 1. Open discover and open an application page 2. Check application's screenshots OBSERVED RESULT It's very hard to understand anything, very hard to see EXPECTED RESULT We should be able to see and understand a screenshot without needing the overlay screenshot thing SOFTWARE/OS VERSIONS Linux/KDE Plasma: Fedora KDE 36 (available in About System) KDE Plasma Version: 5.25 KDE Frameworks Version: 5.95 Qt Version: 5.15.3 -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 443882] popup menu of highlighted text does not appear on right click in text selection mode
https://bugs.kde.org/show_bug.cgi?id=443882 Elmar changed: What|Removed |Added CC||rob...@iafrica.com --- Comment #12 from Elmar --- Whilst I have some understanding for the developer's perspective ... Please reconsider: if something is not intuitive, it is the same as trying to speak to someone in an unfamiliar language. Very frustrating. I also find that if I do not click in exactly the right place, Okular creates a new text box, and hen I cannot delete it. I had to do a search to figure this out. Surely a simple solution with too much difficulty would simply be to add a "delete" function in the right-click context menu? I mean, all the code already exists, doesn't it? And more, this was a function that existed previously - that in itself should be justification. A case of $1 saving $1,000 of ongoing frustration. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 455273] "From " filter fails to identify sender when they also have a name
https://bugs.kde.org/show_bug.cgi?id=455273 Laurent Montel changed: What|Removed |Added Component|sieve |search -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 455273] "From " filter fails to identify sender when they also have a name
https://bugs.kde.org/show_bug.cgi?id=455273 Laurent Montel changed: What|Removed |Added CC||mon...@kde.org --- Comment #1 from Laurent Montel --- So it's normal: end-with => search text at the end => if you have blo.com> => you need to search it. So now I can adapt code for remove ">" first before searching. I will do -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 453668] Windows moved and window sizes are squashed when unplugging/replugging screen with differing resolution from the primary one
https://bugs.kde.org/show_bug.cgi?id=453668 Andreas Aardal Hanssen changed: What|Removed |Added Resolution|WORKSFORME |--- Status|RESOLVED|REOPENED Ever confirmed|0 |1 --- Comment #6 from Andreas Aardal Hanssen --- I’ve tried to enable wayland session but it’s completely broken, so I can’t say. This bug is very valid and trivial to reproduce so, no information needed about that. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kconfig] [Bug 453780] Plasma crashes when I use Application menu-> logout and it won't
https://bugs.kde.org/show_bug.cgi?id=453780 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.
[kinfocenter] [Bug 453826] The Info Center window opens occupying the entire height of the screen
https://bugs.kde.org/show_bug.cgi?id=453826 Bug Janitor Service changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |WORKSFORME --- Comment #8 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 453774] Dolphin crashed when attaching another monitor
https://bugs.kde.org/show_bug.cgi?id=453774 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.
[plasmashell] [Bug 439995] Many notifications in a short time span can lockup plasmashell
https://bugs.kde.org/show_bug.cgi?id=439995 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.
[kwin] [Bug 453668] Windows moved and window sizes are squashed when unplugging/replugging screen with differing resolution from the primary one
https://bugs.kde.org/show_bug.cgi?id=453668 Bug Janitor Service changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |WORKSFORME --- Comment #5 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.
[systemsettings] [Bug 447612] Touchpad preferences bug: Preferences are reset upon login
https://bugs.kde.org/show_bug.cgi?id=447612 --- Comment #10 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 455303] New: kscreenlocker fails to compile without PAM
https://bugs.kde.org/show_bug.cgi?id=455303 Bug ID: 455303 Summary: kscreenlocker fails to compile without PAM Product: kscreenlocker Version: git-master Platform: Gentoo Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: esco...@hotmail.com CC: bhus...@gmail.com Target Milestone: --- SUMMARY Compiling without 'PAM' is no longer possible, probably after 132adacf3d0 [1], even though the 'PAM_REQUIRED' option still exists. 1. https://invent.kde.org/plasma/kscreenlocker/-/commit/132adacf3d01fc4adf8a873e0debc3adb17972ec STEPS TO REPRODUCE 1. Compile with '-DPAM_REQUIRED=NO' and no PAM installed. OBSERVED RESULT Compiling fails. EXPECTED RESULT Either compiling should still succeed without PAM, or the option is removed, and PAM is always required. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Gentoo Linux/git master (available in About System) KDE Plasma Version: git master (partial only to use KWin with LXQt) KDE Frameworks Version: git master (partial only to use KWin with LXQt) Qt Version: 5.15.4 (with KDE patches) -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 455302] Seat names in multiseat configurations are injected directly into dbus paths, leading to assertion failures and ugly crashes.
https://bugs.kde.org/show_bug.cgi?id=455302 --- Comment #1 from vespian --- See also https://bugs.kde.org/show_bug.cgi?id=455204#c1 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 455204] Seat names in multiseat configurations are injected directly into dbus paths, leading to assertion failures and ugly crashes.
https://bugs.kde.org/show_bug.cgi?id=455204 --- Comment #2 from vespian --- Done: https://bugs.kde.org/show_bug.cgi?id=455302 -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 455302] New: Seat names in multiseat configurations are injected directly into dbus paths, leading to assertion failures and ugly crashes.
https://bugs.kde.org/show_bug.cgi?id=455302 Bug ID: 455302 Summary: Seat names in multiseat configurations are injected directly into dbus paths, leading to assertion failures and ugly crashes. Product: kscreenlocker Version: 5.24.4 Platform: Ubuntu Packages OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: kde...@vespian.net CC: bhus...@gmail.com Target Milestone: --- SUMMARY Dbus paths must match the "[A-Z][a-z][0-9]_" regexp [1]. OTOH hand it is allowed to create seat names like 'seat-foo' which leads to ugly assertion errors in kde applications when doing DBUS calls that involve such paths. kscreenlocker is just one of the components effected, another is plasmashell which kickoff somehow referes to. Please feel free to move this bugreport accordingly. [1] https://dbus.freedesktop.org/doc/dbus-specification.html, section "Valid Object Paths". STEPS TO REPRODUCE 1. create a seat that contains e.g. '-' in the name 2. login to this seat 3. just try searching something in kickoff menu, or lock a screen and the component will crash Alternative is to simply do a dbus call that e.g. kickoff is doing when searching for something in the menu: ```""" dbus-send --print-reply --dest=org.freedesktop.DisplayManager /org/freedesktop/DisplayManager/Seat-ves org.freedesktop.DBus.Introspectable.Introspect """ OBSERVED RESULT Components crashing EXPECTED RESULT Unsupported DBUS paths should be validated and errors should be logged or preferably a warning should be shown to the user stating that the name of the seat is invalid. I do not have a context wrt. why assertions in the code are made instead, but IMO handling this error gracefully could help novice users debug this problem in the future. SOFTWARE/OS VERSIONS Linux/KDE Plasma: see the form data I entered Qt Version: 5.15.3 System is stock Ubuntu 22.04 LTS. ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 455301] New: Add Delete Unused Categories
https://bugs.kde.org/show_bug.cgi?id=455301 Bug ID: 455301 Summary: Add Delete Unused Categories Product: kmymoney Version: 5.1.2 Platform: Manjaro OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: general Assignee: kmymoney-de...@kde.org Reporter: ben586...@gmail.com Target Milestone: --- When importing a csv, I accidentally placed category as the amount column and imported this. I then realized this too late after importing and deleted the errant transactions on the account and reimported them with the correct column mapped to category. All of this is my fault and no problem with the program. What I was left with after this though was hundreds of useless categories with no transactions under them. Unless I am missing something, I now have to spend a few minutes repeatedly performing alt-c-d-enter to mass remove these categories. With skrooge, there is a delete unused categories which would accomplish this in a second. Is this able to be implemented on KMyMoney as well? Just a thought! -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 446311] Kicked back tty right after login on Wayland
https://bugs.kde.org/show_bug.cgi?id=446311 Colin Gauvin changed: What|Removed |Added Status|NEEDSINFO |REPORTED Resolution|WAITINGFORINFO |--- -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 446311] Kicked back tty right after login on Wayland
https://bugs.kde.org/show_bug.cgi?id=446311 --- Comment #9 from Colin Gauvin --- Still happening on openSUSE Tumbleweed 20220613 with Plasma 5.25.0, Frameworks 5.94.0, Kernel 5.18.2-1-default (64 bit) and Wayland. I did discover that disabling auto-login for SDDM and instead letting it boot to the login screen, and then manually entering my password, does not boot me back to tty. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 455291] Mouse pointer changes to 'text' mode after choosing an image from the file system to use as SDDM background
https://bugs.kde.org/show_bug.cgi?id=455291 Yerrey Dev changed: What|Removed |Added Status|REPORTED|CONFIRMED Ever confirmed|0 |1 CC||yer...@protonmail.com --- Comment #1 from Yerrey Dev --- Seems to only affect Wayland. -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 455300] New: multi-monitor issue - only main primary monitor displaying after update to 5.24.5
https://bugs.kde.org/show_bug.cgi?id=455300 Bug ID: 455300 Summary: multi-monitor issue - only main primary monitor displaying after update to 5.24.5 Product: kde Version: unspecified Platform: openSUSE RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: globalun...@disroot.org Target Milestone: --- SUMMARY: multi-monitor issue - only main primary monitor displaying after update to 5.24.5 OBSERVED RESULT: When i login, only my main primary display monitor (PCI-E video card) actually logs in the other 2 monitors are still at the SDDM login screen Plasma's display setting only shows the existance of 1 monitor EXPECTED RESULT: All Monitors should be available in the KDE Plasma Settings SOFTWARE/OS VERSIONS: Operating System: openSUSE Tumbleweed 20220613 KDE Plasma Version: 5.25.0 KDE Frameworks Version: 5.94.0 Qt Version: 5.15.2 Kernel Version: 5.18.2-1-default (64-bit) Graphics Platform: Wayland Processors: 4 × Intel® Core™ i5-3570K CPU @ 3.40GHz Memory: 15.5 GiB of RAM Graphics Processor: AMD PITCAIRN -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 443774] [Wayland] Kicker is not dismissed when I click outside it while a submenu is open
https://bugs.kde.org/show_bug.cgi?id=443774 Fushan Wen changed: What|Removed |Added Version|5.24.90 |5.24.0 --- Comment #7 from Fushan Wen --- Not a regression in 5.25. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 445743] "The impossible happened: mutex is locked simultaneously by two threads" while using mutexes with priority inheritance and signals
https://bugs.kde.org/show_bug.cgi?id=445743 Nick Briggs changed: What|Removed |Added CC||afraid-splicer...@icloud.co ||m --- Comment #15 from Nick Briggs --- Also note: drd/tests/pth_mutex_signal when run under simple memcheck, fails because pthread_mutex_lock() returns EINTR, while POSIX says of it (and related functions) "These functions shall not return an error code of [EINTR]." -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 455193] When kwin_x11 is running, animated wallpapers will cause heavy (video) memory leak when QT_XCB_GL_INTEGRATION=xcb_glx
https://bugs.kde.org/show_bug.cgi?id=455193 Bug Janitor Service changed: What|Removed |Added Ever confirmed|0 |1 Status|REPORTED|ASSIGNED --- Comment #5 from Bug Janitor Service --- A possibly relevant merge request was started @ https://invent.kde.org/plasma/plasma-workspace/-/merge_requests/1845 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 439159] "Add widgets..." and "Show alternatives..." options from context menu stop working after manually restarting plasmashell process using `plasmashell --replace`
https://bugs.kde.org/show_bug.cgi?id=439159 Fushan Wen changed: What|Removed |Added Version|5.24.90 |5.23.0 Keywords|regression | --- Comment #19 from Fushan Wen --- Not a regression in 5.25. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 455299] New: Switching to Hybrid mode on an Optimus Laptop Won't Start the Session
https://bugs.kde.org/show_bug.cgi?id=455299 Bug ID: 455299 Summary: Switching to Hybrid mode on an Optimus Laptop Won't Start the Session Product: plasmashell Version: master Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: generic-crash Assignee: plasma-b...@kde.org Reporter: dominicglus...@gmail.com Target Milestone: 1.0 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. Install and setup optimus switch (done via endeavour os' guide) 2. Run the command optimus-manager --switch hybrid or through system tray icon 3. Logout and be unable to log back in with a error message saying session can't start OBSERVED RESULT Something with the nvidia card and integrated card being both used screws with the new plasma 5.25 update. EXPECTED RESULT With the previous versions I've been able to switch back and forth just fine, get logged out and log right back in. SOFTWARE/OS VERSIONS Windows: N/A macOS: N/A Linux/KDE Plasma: 5.18.3-zen1-1-zen (Kernal?) (available in About System) KDE Plasma Version: 5.25.5 KDE Frameworks Version: 5.95 Qt Version: 5.15.4 ADDITIONAL INFORMATION Running on X11, I hope this is the right place to report the bug. -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 455298] New: Some plasmoids don't take full vertical space in sidebars
https://bugs.kde.org/show_bug.cgi?id=455298 Bug ID: 455298 Summary: Some plasmoids don't take full vertical space in sidebars Product: lattedock Version: git (master) Platform: openSUSE RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: application Assignee: mvourla...@gmail.com Reporter: ryu.ketsu...@outlook.com Target Milestone: --- I've been using a Latte sidebar which can be displayed with the sidebar button to display the notifications plasmoid. Now I decided to make it display more stuff by placing a Grouping Plasmoid. But unlike Notifications plasmoid, the Grouping plasmoid doesn't take full vertical space, leaving this empty and unused area of the sidebar without anything in it. Is there a way to make grouping plasmoid take all the available space? -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 455297] New: Screen goes black, unresponsive, upon waking up laptop from sleep (but it blinks periodically, and system is still alive)
https://bugs.kde.org/show_bug.cgi?id=455297 Bug ID: 455297 Summary: Screen goes black, unresponsive, upon waking up laptop from sleep (but it blinks periodically, and system is still alive) Product: Powerdevil Version: 5.24.4 Platform: Kubuntu Packages OS: Linux Status: REPORTED Severity: major Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: jdally...@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 *** Upon putting the laptop to sleep, and then waking it up, the screen will turn back on and display the cursor very briefly (maybe 0.25 seconds), during which time it is movable/controllable, before shutting back off to black. Then it will start blinking, at a rate of about once per second, for a tiny instant (like, even less than the 0.25s the cursor was visible before). Strangely, during the "blinks", the content of the screen *is* barely discernable for that split second - I'll see a glimpse of the lockscreen wallpaper or the chrome tabs I had open, for the infinitesimal duration that the screen has "blinked" on. Additionally, the OS seems to be alive, but barely - more like in a coma - because if I plug it into AC power, the KDE "power connected" chime plays out of the speakers just fine. However, nothing else seems to work. I tested by opening spotify, starting to play a song, locking the computer (without sleeping it) and making sure my sxhkd shortcut for media play/pause (which I bound to Meta+Z) indeed played & paused the music on the lockscreen. Then I slept the computer and woke it a couple seconds later. Following the cursor disappearing and display turning black & starting to blink, I tried Meta+Z a few times, and nothing happened. Assuming it had gotten to the lockscreen, as I have enabled lock after wake in plasma settings, the key combo should've unpaused the music like before. But it doesn't - despite the "power connected" chime functioning correctly as I mentioned. Finally, I've noticed this only happens maybe 9 out of 10 times. Sometimes the computer will awake from sleep and show the lockscreen without killing the display & blinking incessantly, and let me log back in no problem. I haven't nailed down what causes it to work or not yet, but I noted the other day it worked correctly when the battery dropped under 15% (the "low" level) and thus went to sleep on its own. When I woke it up it worked swimmingly. Since this bug has caused me a lot of grief, I set my Energy Saving settings to NOT suspend automatically, but I forgot to uncheck that on the "On Low Battery" tab, hence why it surprised me to find the laptop had slept by itself (thinking I'd now have to reboot, because of the bug), and then doubly-surprised me when I woke it and found it DIDN'T exhibit the buggy behavior. Anyway this is weird; I'd love to attach a backtrace but I'm not sure what exactly is crashing. I'm filing this under powerdevil because it seems to have something to do with suspend/wake, but I suppose it could be something with kscreen or something as well. Regardless I've scoured my syslog to try & find anything out of the ordinary after the bug occurred & I had to reboot, but haven't found anything suspicious, so if someone can provide me guidance on how to figure out what exactly needs to be backtraced in the first place, I'll gladly go ahead & do that. (ps: on the suggested How_to_create_useful_crash_reports wiki page, under the "Ubuntu-based distros" section, 2 out of the 3 links it points to are dead, which was another roadblock to me getting any kinds of debugging output) STEPS TO REPRODUCE 1. Suspend/sleep the system 2. Press power button to wake 3. Move the mouse around frantically as it wakes, to see the cursor move for 0.25s before the screen shuts off, then observe it blinking once/second OBSERVED RESULT The display goes black/unresponsive after what looks to be the OS waking from sleep normally (evidenced by the brief period where the cursor is visible and responsive). EXPECTED RESULT The display should come on about a second after pressing the power button, then the lockscreen should be displayed about another second later, and NOT turn off suddenly. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Kubuntu 21.10, Linux 5.18.3 (available in About System) KDE Plasma Version: 5.24.4 KDE Frameworks Version: 5.92.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION One more notable detail is the laptop I'm using is an LG Gram, 2021 model, which I just recently bought. However, I started experiencing this behavior just a few weeks *before* I bought this model - at which time I was still using my older, 2019 model LG Gram. I kind of hoped it
[kscreenlocker] [Bug 454820] Using hot keys, I get output that the screenlocker is broken and instructions on how to unlock from a virtual terminal
https://bugs.kde.org/show_bug.cgi?id=454820 Ronnie Bailey changed: What|Removed |Added Status|RESOLVED|REOPENED Ever confirmed|0 |1 Resolution|FIXED |--- -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 455296] New: the problem is still not fix rotoscoping and transform transform just crop the shape out kdenlive please fix this and thank you.
https://bugs.kde.org/show_bug.cgi?id=455296 Bug ID: 455296 Summary: the problem is still not fix rotoscoping and transform transform just crop the shape out kdenlive please fix this and thank you. Product: kdenlive Version: 22.04.1 Platform: Other OS: Microsoft Windows Status: REPORTED Severity: normal Priority: NOR Component: Effects & Transitions Assignee: vpi...@kde.org Reporter: amarijay...@gmail.com Target Milestone: --- please fix this the problem is still the same -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 445196] Open/Save File Dialog suffers from horrible tearing in Wayland under certain circumstances.
https://bugs.kde.org/show_bug.cgi?id=445196 andrea.i...@gmail.com changed: What|Removed |Added CC||andrea.i...@gmail.com --- Comment #16 from andrea.i...@gmail.com --- Hello, I'm able to reproduce this on KDE Plasma 5.24.5 on a Wayland session: https://www.reddit.com/r/kde/comments/vbwige/firefox_vs_qtplasma_file_picker_and_visual/ -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 455193] When kwin_x11 is running, animated wallpapers will cause heavy (video) memory leak when QT_XCB_GL_INTEGRATION=xcb_glx
https://bugs.kde.org/show_bug.cgi?id=455193 Fushan Wen changed: What|Removed |Added Summary|When kwin_x11 is running, |When kwin_x11 is running, |animated wallpapers will|animated wallpapers will |cause heavy (video) memory |cause heavy (video) memory |leak|leak when ||QT_XCB_GL_INTEGRATION=xcb_g ||lx -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 455193] When kwin_x11 is running, animated wallpapers will cause heavy (video) memory leak
https://bugs.kde.org/show_bug.cgi?id=455193 --- Comment #4 from Fushan Wen --- qt_xcb_gl_integration=xcb_egl fixes the leak. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 455295] New: There is no auto-randomize MAC address option
https://bugs.kde.org/show_bug.cgi?id=455295 Bug ID: 455295 Summary: There is no auto-randomize MAC address option Product: systemsettings Version: unspecified Platform: Other OS: Other Status: REPORTED Severity: normal Priority: NOR Component: kcm_networkmanagement Assignee: jgrul...@redhat.com Reporter: harsim...@rtunerfjqq.com CC: plasma-b...@kde.org Target Milestone: --- Created attachment 149724 --> https://bugs.kde.org/attachment.cgi?id=149724=edit auto randomize MAC address SUMMARY There is no button to automatically randomize MAC addresses in connection manager in KDE Settings. STEPS TO REPRODUCE 1. 2. 3. OBSERVED RESULT EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 455231] Task manager window thumbnails missing on x11
https://bugs.kde.org/show_bug.cgi?id=455231 Patrick Silva changed: What|Removed |Added CC||iodream...@gmail.com --- Comment #7 from Patrick Silva --- *** Bug 455263 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 455263] Window previews stopped working
https://bugs.kde.org/show_bug.cgi?id=455263 Patrick Silva changed: What|Removed |Added Status|REPORTED|RESOLVED CC||bugsefor...@gmx.com Resolution|--- |DUPLICATE --- Comment #2 from Patrick Silva --- *** This bug has been marked as a duplicate of bug 455231 *** -- You are receiving this mail because: You are watching all bug changes.
[Oxygen] [Bug 455294] can't use classic clipboard icon
https://bugs.kde.org/show_bug.cgi?id=455294 David Chmelik changed: What|Removed |Added Platform|Other |Slackware Packages -- You are receiving this mail because: You are watching all bug changes.
[Oxygen] [Bug 455294] New: can't use classic clipboard icon
https://bugs.kde.org/show_bug.cgi?id=455294 Bug ID: 455294 Summary: can't use classic clipboard icon Product: Oxygen Version: 5.24.5 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: icons Assignee: n...@oxygen-icons.org Reporter: dchme...@gmail.com Target Milestone: --- SUMMARY Can't use classic clipboard klipper icon. STEPS TO REPRODUCE 1. Upgrade from older KDEP4. OBSERVED RESULT Can't use classic clipboard klipper icon. EXPECTED RESULT Option to use either clipboard or (if anyone still wants) scissors icon. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Slackware64 14.2 stable to 15.1-current KDE Plasma Version: later 4 to 5.24.0 KDE Frameworks Version: earlier to 5.95.0 Qt Version: later 4 to 5.15.3 ADDITIONAL INFORMATION I originally suggested the alternative (scissors) klipper icon but you took things too literally/simplistically: I didn't mean *entirely replace* it with something not as good for most people, rather than add another option. Now I have many things in system tray to the left of klipper so want classic clipboard icon back and probably won't ever want the scissors one again (which was to avoid confusion with KATE icon I used to place by it but also no longer do.) -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 455293] New: cursor scales do not immediately appear after installing through Get New Cursors
https://bugs.kde.org/show_bug.cgi?id=455293 Bug ID: 455293 Summary: cursor scales do not immediately appear after installing through Get New Cursors Product: systemsettings Version: 5.25.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: kcm_cursortheme Assignee: plasma-b...@kde.org Reporter: doncb...@gmail.com Target Milestone: --- Created attachment 149723 --> https://bugs.kde.org/attachment.cgi?id=149723=edit despite selecting a cursor with sizes, none are present after install SUMMARY The different cursor scales do not appear to register in settings until the cursors page is closed and reopened. STEPS TO REPRODUCE 1. Install a cursor theme with Get New Cursors (I chose Bibata Bee) 2. Close the store window 3. Select the newly downloaded theme OBSERVED RESULT Size option is greyed out and no sizes are available EXPECTED RESULT Size option should immediately update and display the available sizes of the cursor without a restart Operating System: KDE neon Testing Edition KDE Plasma Version: 5.25.0 KDE Frameworks Version: 5.95.0 Qt Version: 5.15.4 Kernel Version: 5.13.0-44-generic (64-bit) Graphics Platform: X11 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 455292] New: 5.25 Desktop Grid - Keyboard virtual desktop selection missing.
https://bugs.kde.org/show_bug.cgi?id=455292 Bug ID: 455292 Summary: 5.25 Desktop Grid - Keyboard virtual desktop selection missing. Product: kwin Version: 5.25.0 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: effects-window-management Assignee: kwin-bugs-n...@kde.org Reporter: hugh.ga...@tutamail.com Target Milestone: --- SUMMARY New desktop grid implentation in 5.25 does not allow keyboard selection of a virtual desktop whilst in grid mode. Only way to select is to click a desktop with the mouse. Please add this functionality back. STEPS TO REPRODUCE 1. Open desktop grid view. 2. Use number keys or Function keys to select a virtual desktop. OBSERVED RESULT Nada. Keyed desktop does not become active and desktop grid remains open. EXPECTED RESULT Desktop grid closes and selected desktop becomes active. Previous implementation of desktop grid allowed for numerical keyboard selection (ie 1-n) and function key selection (ie F1-Fn). Please add both these back. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: Arch Linux (available in About System) KDE Plasma Version: 5.25 KDE Frameworks Version: 5.95.0 Qt Version: 5.15.4 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 454621] Plasmashell doesn't start on all monitors in a multi xscreen environment
https://bugs.kde.org/show_bug.cgi?id=454621 --- Comment #2 from Allistar --- I wonder if this is related to one of these issues: https://bugreports.qt.io/browse/QTBUG-101203 https://codereview.qt-project.org/c/qt/qtbase/+/412385 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 455280] While arranging a single window, all windows in the same workspace move along together.
https://bugs.kde.org/show_bug.cgi?id=455280 --- Comment #2 from hugh --- Created attachment 149722 --> https://bugs.kde.org/attachment.cgi?id=149722=edit Cannot move window to desktop with existing windows either. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 455280] While arranging a single window, all windows in the same workspace move along together.
https://bugs.kde.org/show_bug.cgi?id=455280 hugh changed: What|Removed |Added CC||hugh.ga...@tutamail.com --- Comment #1 from hugh --- Created attachment 149721 --> https://bugs.kde.org/attachment.cgi?id=149721=edit Cannot move single window -- You are receiving this mail because: You are watching all bug changes.
[Planet KDE] [Bug 455268] Can't drag only a single window from one virtual desktop to another
https://bugs.kde.org/show_bug.cgi?id=455268 --- Comment #2 from hugh --- Created attachment 149720 --> https://bugs.kde.org/attachment.cgi?id=149720=edit Cannot move to a desktop with existing windows either, swaps them. Cannot move to a desktop with existing windows either, swaps them. -- You are receiving this mail because: You are watching all bug changes.
[Planet KDE] [Bug 455268] Can't drag only a single window from one virtual desktop to another
https://bugs.kde.org/show_bug.cgi?id=455268 hugh changed: What|Removed |Added CC||hugh.ga...@tutamail.com --- Comment #1 from hugh --- Created attachment 149719 --> https://bugs.kde.org/attachment.cgi?id=149719=edit Cannot move a single window Cannot move a single window in desktop grid also. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 455195] Black artefacts have appeared above software that utilizes native GTK stylization.
https://bugs.kde.org/show_bug.cgi?id=455195 --- Comment #5 from BEEDELL ROKE JULIAN LOCKHART --- (In reply to Vlad Zahorodnii from comment #2) > At quick glance, it looks like the opaque region is bad. In 5.25, kwin is > more strict with opaque regions, so it's really important that apps provide > good opaque region hints. > > gnome-abrt and abrt are not provided by my distro. Can you run `env > WAYLAND_DEBUG=1 gnome-abrt` and post the output here? ``` PowerShell 7.3.0-preview.4 PS /> Start-Transcript -Append -IncludeInvocationHeader Transcript started, output file is /home/A1653237104/PowerShell_transcript.1653307616.ArdHRLab.20220614234056.txt PS /> env WAYLAND_DEBUG=1 gnome-abrt Gtk-Message: 23:40:59.127: Failed to load module "appmenu-gtk-module" PS /> ``` I am utilizing startx. Should I have utilized startplasma-wayland instead to evaluate whether that prevents it? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 455195] Black artefacts have appeared above software that utilizes native GTK stylization.
https://bugs.kde.org/show_bug.cgi?id=455195 --- Comment #4 from BEEDELL ROKE JULIAN LOCKHART --- (In reply to Nate Graham from comment #3) > I can't reproduce the issue with gnome-abrt with current git master, FWIW. I expect that you are unable to reproduce the problem because the problem is caused not specifically by gnome-abrt, but by how something that is specific to how GTK software is presented, or KWin, because this problem AND what “http://i.imgur.com/pVNwwj8.mp4” depicts began to occur when I last updated by OS. "5.19.0-0.rc1.20220610git874c8ca1e60b.18.fc37.x86_64 #1 SMP PREEMPT_DYNAMIC Fri Jun 10 16:26:15 UTC 2022” is the version that uname reports. I have redacted what is not useful. Another system-update became available whilst I wrote this response. I shall evaluate during tomorrow whether the problem persists despite it. -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 454820] Using hot keys, I get output that the screenlocker is broken and instructions on how to unlock from a virtual terminal
https://bugs.kde.org/show_bug.cgi?id=454820 --- Comment #3 from Ronnie Bailey --- I upgraded all KDE and Plasma packages today. I can confirm that this bug still exists in kscreenlocker-5.25 as I now have 5 broken machines. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 455291] New: Mouse pointer changes to 'text' mode after choosing an image from the file system to use as SDDM background
https://bugs.kde.org/show_bug.cgi?id=455291 Bug ID: 455291 Summary: Mouse pointer changes to 'text' mode after choosing an image from the file system to use as SDDM background Product: systemsettings Version: master Platform: Neon Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: kcm_sddm Assignee: k...@davidedmundson.co.uk Reporter: bugsefor...@gmx.com CC: k...@david-redondo.de, plasma-b...@kde.org Target Milestone: --- Created attachment 149718 --> https://bugs.kde.org/attachment.cgi?id=149718=edit screenshot STEPS TO REPRODUCE 1. open SDDM KCM 2. click on the button to change the background of the current theme 3. click on 'Load from file...' button and choose an image file OBSERVED RESULT Mouse pointer changes to what we see highlighted in red in the attached screenshot. Mouse pointer is fixed when I hover over Plasma panel or a window decoration. EXPECTED RESULT mouse pointer should not change SOFTWARE/OS VERSIONS Operating System: KDE neon Unstable Edition KDE Plasma Version: 5.25.80 KDE Frameworks Version: 5.96.0 Qt Version: 5.15.4 Graphics Platform: Wayland -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 454161] Brightness stuck at 30%
https://bugs.kde.org/show_bug.cgi?id=454161 --- Comment #9 from Aurélien COUDERC --- (In reply to Nate Graham from comment #6) > Are you using the slider in the Battery & Brightness applet? Does it work if > you click on a position in the track rather than dragging the handle? I’ve reverted the commits for some time now, but as far as I remember both the slider and the keys had the same effect. It was not only blocking at ~20 % but the brightness was also flickering between steps until it reached that level. So it would do something like 6%, 8%, 2%, 12%, 1%, 16%, 3%, 18% (not precisely these numbers but you get the idea). -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 455290] New: sshmanager import fills in user ID, but editing doesn't allow edits with the user ID filled in (but User ID is read only in this case)
https://bugs.kde.org/show_bug.cgi?id=455290 Bug ID: 455290 Summary: sshmanager import fills in user ID, but editing doesn't allow edits with the user ID filled in (but User ID is read only in this case) Product: konsole Version: unspecified Platform: Neon Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: sshmanager Assignee: konsole-de...@kde.org Reporter: a...@al-williams.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 *** STEPS TO REPRODUCE 1. Try to change profile for imported host 2. Note that manager reports you should not provide username/key (Message: If use Ssh Config is set, do not specify sshkey or username). Unable to save. 3. Note that the import set the user name and you are unable to change it. 4. Only work around is to directly edit ~/.config/konsolesshconfig while Konsole is NOT running Portion of .ssh/config: Host XXX Hostname XXX.XXX ForwardX11 yes ForwardX11Trusted yes Compression yes ServerAliveCountMax 3 ServerAliveInterval 15 TCPKeepAlive yes User MYUSERID So it appears that the import fills the user ID field (unnecessarily) but the edit feature doesn't allow you to fill it in. But since it is already filled in and you can't change it One byproduct of this is that if you try to set a profile to open a session, the sshmanager session overrides the profile setting and since you can't change it -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 452758] Valgrind does not read properly DWARF5 as generated by Clang14
https://bugs.kde.org/show_bug.cgi?id=452758
--- Comment #47 from Nick Nethercote ---
My test Rust program was this, in `a.rs`:
> fn main() {
> println!("hello world");
> }
And I compiled with `rustc +nightly a.rs` to produce the executable `a`.
--
You are receiving this mail because:
You are watching all bug changes.
[plasma-systemmonitor] [Bug 454326] [Wayland] Scrolling in 'Processes' page is choppy/slow for ~30 seconds
https://bugs.kde.org/show_bug.cgi?id=454326
--- Comment #3 from Nagy Tibor ---
strace says to load a single icon System Monitor searches through a thousand(!)
possible icon paths. For every single icon. No wonder why it's so slow.
It also doesn't strip the parameters from the executable line when it construct
the possible icon paths. For example when loading icons for vscode it ends up
searching for nonsense paths like this.
access("/usr/share/icons/hicolor/48x48/actions/code --type=zygote -.svgz",
F_OK) = -1 ENOENT (No such file or directory)
--
You are receiving this mail because:
You are watching all bug changes.
[kwin] [Bug 455251] Junction's overlay window is sometimes drawn with excessive transparency, depending on how it's invoked
https://bugs.kde.org/show_bug.cgi?id=455251 Chase Lau changed: What|Removed |Added Resolution|--- |NOT A BUG Status|REPORTED|RESOLVED --- Comment #3 from Chase Lau --- Hi Nate, Thanks for taking a look but I'm embarrassed to say this issue was caused by myself messing around with building the application. Nothing is wrong with KWin. Sorry to waste your time! -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 452758] Valgrind does not read properly DWARF5 as generated by Clang14
https://bugs.kde.org/show_bug.cgi?id=452758 --- Comment #46 from Nick Nethercote --- > Could you test again with top of tree and see whether --read-var-info=yes > also works OK? My normal workflow works well. It uses Cachegrind and DHAT, which don't need `--read-var-info=yes`. I also tested Memcheck on a trivial Rust program and `--read-var-info=yes` had problems: > ==19085== Memcheck, a memory error detector > ==19085== Copyright (C) 2002-2022, and GNU GPL'd, by Julian Seward et al. > ==19085== Using Valgrind-3.20.0.GIT and LibVEX; rerun with -h for copyright > info > ==19085== Command: ./a > ==19085== > > parse DIE(readdwarf3.c:3994): confused by: > <0>: Abbrev Number: 1 (DW_TAG_compile_unit) > DW_AT_producer: (indirect string, offset: 0x0): clang LLVM (rustc > version 1.63.0-nightly (420c970cb 2022-06-09)) > DW_AT_language: 28 > DW_AT_name: (indirect string, offset: 0x41): > library/std/src/lib.rs/@/std.85a61a41-cgu.0 > DW_AT_stmt_list : 0 > DW_AT_comp_dir: (indirect string, offset: 0x6d): > /rustc/420c970cb1edccbf60ff2aeb51ca01e2300b09ef > DW_AT_GNU_pubnames: 1 > DW_AT_low_pc : 0x0 > DW_AT_ranges : 322832 > parse_type_DIE: > --19085-- WARNING: Serious error when reading debug info > --19085-- When reading debug info from /home/njn/dev/rustc-perf/a: > --19085-- confused by the above DIE > hello world > ==19085== > ==19085== HEAP SUMMARY: > ==19085== in use at exit: 0 bytes in 0 blocks > ==19085== total heap usage: 11 allocs, 11 frees, 3,181 bytes allocated > ==19085== > ==19085== All heap blocks were freed -- no leaks are possible > ==19085== > ==19085== For lists of detected and suppressed errors, rerun with: -s > ==19085== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 0 from 0) -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 455168] want/need more 'const' in Valgrind source code
https://bugs.kde.org/show_bug.cgi?id=455168 --- Comment #4 from John Reiser --- (In reply to Paul Floyd from comment #1) > I get quite a few new warnings (there were perhaps 5 before, mostly void > abuse and for x86) When I process those warning lines using the shell pipeline sort | uniq -c | sort -rn then I see that most of the lines appear twice as duplicates: - 2 m_syswrap/syswrap-generic.c:3084:38: warning: cast discards 'const' qualifier from pointer target type [-Wcast-qual] 2 m_pathscan.c:131:26: warning: cast discards 'const' qualifier from pointer target type [-Wcast-qual] 2 m_main.c:3439:40: warning: passing argument 3 of 'valgrind_main' discards 'const' qualifier from pointer target type [-Wdiscarded-qualifiers] [[snip]] 2 m_initimg/initimg-freebsd.c:559:31: warning: passing argument 1 of 'copy_str' from incompatible pointer type [-Wincompatible-pointer-types] 2 m_initimg/initimg-freebsd.c:557:31: warning: passing argument 1 of 'copy_str' from incompatible pointer type [-Wincompatible-pointer-types] 2 m_initimg/initimg-freebsd.c:286:16: warning: initialization discards 'const' qualifier from pointer target type [-Wdiscarded-qualifiers] 1 m_syswrap/syswrap-x86-freebsd.c:460:10: warning: cast to pointer from integer of different size [-Wint-to-pointer-cast] 1 m_syswrap/syswrap-x86-freebsd.c:419:10: warning: cast to pointer from integer of different size [-Wint-to-pointer-cast] 1 m_syswrap/syswrap-x86-freebsd.c:406:24: warning: cast to pointer from integer of different size [-Wint-to-pointer-cast] 1 m_syswrap/syswrap-x86-freebsd.c:401:24: warning: cast to pointer from integer of different size [-Wint-to-pointer-cast] 1 m_sigframe/sigframe-x86-freebsd.c:292:27: warning: taking address of expression of type 'void' 1 m_sigframe/sigframe-amd64-freebsd.c:256:27: warning: taking address of expression of type 'void' - So "quite a few" is actually not so may. (And the Makefile could be made less wasteful.) [Further analysis later ...] -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 455289] New: Crashed out of the blue
https://bugs.kde.org/show_bug.cgi?id=455289 Bug ID: 455289 Summary: Crashed out of the blue Product: kdeconnect Version: unspecified Platform: Ubuntu Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: common Assignee: albertv...@gmail.com Reporter: kde...@commsbloke.com Target Milestone: --- Application: kdeconnectd (1.4.0) Qt Version: 5.12.8 Frameworks Version: 5.68.0 Operating System: Linux 5.13.0-48-generic x86_64 Windowing system: X11 Distribution: Ubuntu 20.04.4 LTS -- Information about the crash: Viewing google images in Firefox One window had a paused Youtube video Only other app open was Thunderbird. -- Backtrace: Application: KDE Connect Daemon (kdeconnectd), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f7d91176800 (LWP 1132))] Thread 4 (Thread 0x7f7d8d62a700 (LWP 1187)): #0 0x7f7d9475699f in __GI___poll (fds=0x7f7d840025e0, nfds=1, timeout=9310) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7f7d9346d36e in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f7d9346d4a3 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f7d94cf8453 in QEventDispatcherGlib::processEvents(QFlags) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7f7d94c9f3ab in QEventLoop::exec(QFlags) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f7d94ad7785 in QThread::exec() () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7f7d94ad89d2 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7f7d93d2d609 in start_thread (arg=) at pthread_create.c:477 #8 0x7f7d94763133 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 3 (Thread 0x7f7d8e868700 (LWP 1180)): #0 0x7f7d9475699f in __GI___poll (fds=0x7f7d8001a040, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7f7d9346d36e in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f7d9346d4a3 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f7d94cf8453 in QEventDispatcherGlib::processEvents(QFlags) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7f7d94c9f3ab in QEventLoop::exec(QFlags) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f7d94ad7785 in QThread::exec() () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7f7d94f7aefa in ?? () from /lib/x86_64-linux-gnu/libQt5DBus.so.5 #7 0x7f7d94ad89d2 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7f7d93d2d609 in start_thread (arg=) at pthread_create.c:477 #9 0x7f7d94763133 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 2 (Thread 0x7f7d902c5700 (LWP 1158)): #0 0x7f7d9475699f in __GI___poll (fds=0x7f7d902c4ca8, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7f7d9318fc1a in ?? () from /lib/x86_64-linux-gnu/libxcb.so.1 #2 0x7f7d9319190a in xcb_wait_for_event () from /lib/x86_64-linux-gnu/libxcb.so.1 #3 0x7f7d90ad0298 in ?? () from /lib/x86_64-linux-gnu/libQt5XcbQpa.so.5 #4 0x7f7d94ad89d2 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f7d93d2d609 in start_thread (arg=) at pthread_create.c:477 #6 0x7f7d94763133 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 1 (Thread 0x7f7d91176800 (LWP 1132)): [KCrash Handler] #6 0x7f7d94b5a1f4 in QString::operator=(QString const&) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7f7d961585d6 in LanLinkProvider::configureSslSocket(QSslSocket*, QString const&, bool) () from /lib/x86_64-linux-gnu/libkdeconnectcore.so.1 #8 0x7f7d961687ab in CompositeUploadJob::newConnection() () from /lib/x86_64-linux-gnu/libkdeconnectcore.so.1 #9 0x7f7d94ccc328 in QMetaObject::activate(QObject*, int, int, void**) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #10 0x7f7d9447288e in QTcpServerPrivate::readNotification() () from /lib/x86_64-linux-gnu/libQt5Network.so.5 #11 0x7f7d9447ee29 in ?? () from /lib/x86_64-linux-gnu/libQt5Network.so.5 #12 0x7f7d95801a66 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #13 0x7f7d9580b0f0 in QApplication::notify(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #14 0x7f7d94ca080a in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #15 0x7f7d94cf9095 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #16 0x7f7d9346d17d in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #17 0x7f7d9346d400 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #18 0x7f7d9346d4a3 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #19 0x7f7d94cf8435 in
[kdenlive] [Bug 455288] New: if i use rotoscoping and tranform effect the tranform effect ruins my shape
https://bugs.kde.org/show_bug.cgi?id=455288 Bug ID: 455288 Summary: if i use rotoscoping and tranform effect the tranform effect ruins my shape Product: kdenlive Version: 22.04.1 Platform: Other OS: Microsoft Windows Status: REPORTED Severity: normal Priority: NOR Component: Effects & Transitions Assignee: vpi...@kde.org Reporter: amarijay...@gmail.com Target Milestone: --- STEPS TO REPRODUCE 1. 2. 3. OBSERVED RESULT EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 455287] New: systemstettings: "virtual desktops" never reach default state
https://bugs.kde.org/show_bug.cgi?id=455287 Bug ID: 455287 Summary: systemstettings: "virtual desktops" never reach default state Product: systemsettings Version: unspecified Platform: openSUSE RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: kcm_kwin_virtualdesktops Assignee: kwin-bugs-n...@kde.org Reporter: menis...@gmx.net CC: plasma-b...@kde.org Target Milestone: --- Created attachment 149717 --> https://bugs.kde.org/attachment.cgi?id=149717=edit systemsettings "virtual desktops" never reach there default state SUMMARY systemsettings: the orange dot is always visible. Its not possible to set "virtual desktops" back to preset state. Default is one Desktop and two rows. But setting rows to the preset value of two is not possible if there is only one desktop. STEPS TO REPRODUCE - Open Systemsettings > "Virual Desktops" - reduce desktops to one - set rows to two - apply changes OBSERVED RESULT The orange persists, because the value of "rows" is still "1". EXPECTED RESULT the orange dot disappear, because the value of "rows" is now "2" SOFTWARE/OS VERSIONS Betriebssystem: openSUSE Tumbleweed 20220613 KDE-Plasma-Version: 5.25.0 KDE-Frameworks-Version: 5.94.0 Qt-Version: 5.15.2 -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 360925] Default Dbus shortcut prevents multiple instances of Spectacle when continuing to press PrntScr
https://bugs.kde.org/show_bug.cgi?id=360925 Ganton changed: What|Removed |Added CC||ku...@gmx.com --- Comment #2 from Ganton --- > people who expect their screenshot program to hold numerous copies of itself > in memory waiting for > the user to process the pic(s) further. For those who find that page searching (for example) "Spectacle multiple instances": A standard method for Spectacle 21.12.3 is: Click "Configure...", "General", and next to "When Spectacle is Running" / "Press screenshot key to:" select "Open a new Spectacle window". -- You are receiving this mail because: You are watching all bug changes.
[plasma-systemmonitor] [Bug 454326] [Wayland] Scrolling in 'Processes' page is choppy/slow for ~30 seconds
https://bugs.kde.org/show_bug.cgi?id=454326 Nagy Tibor changed: What|Removed |Added CC||xnagyti...@gmail.com --- Comment #2 from Nagy Tibor --- I can reproduce this on Neon. Hotspot says the lag comes from KIconEngine, KIconLoader and KIconTheme. So I'd guess the lag comes from loading the process icons. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 455286] New: Export video dublicates job queue, failing to comprehend cyrillics
https://bugs.kde.org/show_bug.cgi?id=455286 Bug ID: 455286 Summary: Export video dublicates job queue, failing to comprehend cyrillics Product: kdenlive Version: 22.04.2 Platform: Microsoft Windows OS: Microsoft Windows Status: REPORTED Severity: minor Priority: NOR Component: Video Display & Export Assignee: j...@kdenlive.org Reporter: denis2018...@gmail.com Target Milestone: --- Created attachment 149716 --> https://bugs.kde.org/attachment.cgi?id=149716=edit альфа омега версия incorrectly displays as альфа омега версия. The filetype for video export doesn't support the Cyrillics (possibly any other non-english characters). Maybe the picture would say for itself. *** 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. Write out the russian language on output file 2. Render the video SOFTWARE/OS VERSIONS Windows: 10 LTSC, AMD64 Version 21H2 19044.1741 Windows Feature Experience Pack: 120.2212.4170.0 KDE Frameworks Version: 5.94.0 Qt Version: 5.15.2 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 455285] New: Playing TF2 (OpenGL), Closed out and it Started Flickering
https://bugs.kde.org/show_bug.cgi?id=455285 Bug ID: 455285 Summary: Playing TF2 (OpenGL), Closed out and it Started Flickering Product: kwin Version: 5.24.5 Platform: unspecified OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kwin-bugs-n...@kde.org Reporter: dominicglus...@gmail.com Target Milestone: --- Application: kwin_x11 (5.24.5) Qt Version: 5.15.4 Frameworks Version: 5.95.0 Operating System: Linux 5.18.3-zen1-1-zen x86_64 Windowing System: X11 Distribution: EndeavourOS DrKonqi: 5.24.5 [KCrashBackend] -- Information about the crash: - What I was doing when the application crashed: I just quit out of tf2 and it started flickering and i couldnt do anything The reporter is unsure if this crash is reproducible. -- Backtrace: Application: KWin (kwin_x11), signal: Segmentation fault [KCrash Handler] #4 0x7f51833ca9af in KWin::GLTexture::bind() () at /usr/lib/libkwinglutils.so.13 #5 0x7f517807aaee in KWin::LightlyShadersEffect::paintWindow(KWin::EffectWindow*, int, QRegion, KWin::WindowPaintData&) () at /usr/lib/qt/plugins/kwin/effects/plugins/kwin4_effect_lightlyshaders.so #6 0x7f5183167229 in KWin::EffectsHandlerImpl::paintWindow(KWin::EffectWindow*, int, QRegion const&, KWin::WindowPaintData&) () at /usr/lib/libkwin.so.5 #7 0x7f5183167229 in KWin::EffectsHandlerImpl::paintWindow(KWin::EffectWindow*, int, QRegion const&, KWin::WindowPaintData&) () at /usr/lib/libkwin.so.5 #8 0x7f5183167229 in KWin::EffectsHandlerImpl::paintWindow(KWin::EffectWindow*, int, QRegion const&, KWin::WindowPaintData&) () at /usr/lib/libkwin.so.5 #9 0x7f5183167229 in KWin::EffectsHandlerImpl::paintWindow(KWin::EffectWindow*, int, QRegion const&, KWin::WindowPaintData&) () at /usr/lib/libkwin.so.5 #10 0x7f51831d1820 in KWin::Scene::paintWindow(KWin::Scene::Window*, int, QRegion const&) () at /usr/lib/libkwin.so.5 #11 0x7f51831d26a6 in KWin::Scene::paintSimpleScreen(int, QRegion const&) () at /usr/lib/libkwin.so.5 #12 0x7f5183167178 in KWin::EffectsHandlerImpl::paintScreen(int, QRegion const&, KWin::ScreenPaintData&) () at /usr/lib/libkwin.so.5 #13 0x7f5183167178 in KWin::EffectsHandlerImpl::paintScreen(int, QRegion const&, KWin::ScreenPaintData&) () at /usr/lib/libkwin.so.5 #14 0x7f5183167178 in KWin::EffectsHandlerImpl::paintScreen(int, QRegion const&, KWin::ScreenPaintData&) () at /usr/lib/libkwin.so.5 #15 0x7f5183167178 in KWin::EffectsHandlerImpl::paintScreen(int, QRegion const&, KWin::ScreenPaintData&) () at /usr/lib/libkwin.so.5 #16 0x7f51831d11fd in KWin::Scene::paintScreen(QRegion const&, QRegion const&, QRegion*, QRegion*, KWin::RenderLoop*, QMatrix4x4 const&) () at /usr/lib/libkwin.so.5 #17 0x7f51832973a7 in KWin::SceneOpenGL::paint(KWin::AbstractOutput*, QRegion const&, QList const&, KWin::RenderLoop*) () at /usr/lib/libkwin.so.5 #18 0x7f5183139709 in KWin::Compositor::composite(KWin::RenderLoop*) () at /usr/lib/libkwin.so.5 #19 0x7f5183139e9f in KWin::X11Compositor::composite(KWin::RenderLoop*) () at /usr/lib/libkwin.so.5 #20 0x7f51814be251 in () at /usr/lib/libQt5Core.so.5 #21 0x7f51830f08d7 in KWin::RenderLoop::frameRequested(KWin::RenderLoop*) () at /usr/lib/libkwin.so.5 #22 0x7f51831c25b8 in KWin::RenderLoopPrivate::dispatch() () at /usr/lib/libkwin.so.5 #23 0x7f51814be251 in () at /usr/lib/libQt5Core.so.5 #24 0x7f51814c060f in QTimer::timeout(QTimer::QPrivateSignal) () at /usr/lib/libQt5Core.so.5 #25 0x7f51814b13d6 in QObject::event(QEvent*) () at /usr/lib/libQt5Core.so.5 #26 0x7f5180b78a7c in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /usr/lib/libQt5Widgets.so.5 #27 0x7f518148db28 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /usr/lib/libQt5Core.so.5 #28 0x7f51814d7ac3 in QTimerInfoList::activateTimers() () at /usr/lib/libQt5Core.so.5 #29 0x7f51814d7f72 in QEventDispatcherUNIX::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #30 0x7f517b6eff43 in () at /usr/lib/libQt5XcbQpa.so.5 #31 0x7f51814862ec in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #32 0x7f5181490dd9 in QCoreApplication::exec() () at /usr/lib/libQt5Core.so.5 #33 0x5651a95aadd5 in () #34 0x7f5180229290 in () at /usr/lib/libc.so.6 #35 0x7f518022934a in __libc_start_main () at /usr/lib/libc.so.6 #36 0x5651a95ac1a5 in () [Inferior 1 (process 880) detached] Possible duplicates by query: bug 453626, bug 452482, bug 451022, bug 449702, bug 445375. Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 455282] Support for opening PDFs with page number
https://bugs.kde.org/show_bug.cgi?id=455282 --- Comment #2 from alexandre@zurcher.digital --- (In reply to tcanabrava from comment #1) > Created attachment 149715 [details] > attachment-3290-0.html > > Seems doable, is this # used by other file formats too? > > On Tue, 14 Jun 2022 at 22:14 wrote: > > > https://bugs.kde.org/show_bug.cgi?id=455282 > > > > Bug ID: 455282 > >Summary: Support for opening PDFs with page number > >Product: konsole > >Version: 22.04.1 > > Platform: Fedora RPMs > > OS: Linux > > Status: REPORTED > > Severity: wishlist > > Priority: NOR > > Component: general > > Assignee: konsole-de...@kde.org > > Reporter: alexandre@zurcher.digital > > Target Milestone: --- > > > > Created attachment 149714 [details] > > --> https://bugs.kde.org/attachment.cgi?id=149714=edit > > Error in question, folder "test" contains one PDF file named "document.pdf" > > > > SUMMARY > > When trying to open a PDF file finishing with page number (i.e > > "document.pdf#2"), Konsole gives an error message that the file doesn't > > exist. > > Opening the same file by using the command `okular document.pdf#2` works as > > intended. > > > > USECASE: I use a script based on pdfgrep to quickly find a PDF, then I > > open it > > in Okular by CTRL+clicking on it. Would be amazing for it to open at the > > right > > page as well ! > > > > STEPS TO REPRODUCE > > 1. have a PDF document > > 2. in Konsole, do `echo "'./document_name.pdf#2'"` > > 3. try to CTRL+click './document_name.pdf#2' > > > > OBSERVED RESULT > > Error message that the file doesn't exist (see screenshot for example - in > > French) > > > > EXPECTED RESULT > > PDF opening in Okular at the right page > > > > SOFTWARE/OS VERSIONS > > Fedora Linux 36 > > KDE Plasma Version: 5.24.5 > > KDE Frameworks Version: 5.93.0 > > Qt Version: 5.15.3 > > > > -- > > You are receiving this mail because: > > You are the assignee for the bug. Thanks for answering so quickly ! HTML files do come to mind, i.e "index.html#main". I just tried it and it produces the same error when trying to CTRL+clicking it. However, using "firefox index.html#main" does work as expected. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 383010] Add support for AVX-512 instructions
https://bugs.kde.org/show_bug.cgi?id=383010 Tom Hughes changed: What|Removed |Added CC||ytr...@sdf-eu.org --- Comment #78 from Tom Hughes --- *** Bug 451837 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 451837] When profiling this specific executable, valgrind fails to break down 0x62 0xF1 0x7F 0x28 0x7F 0x2 0xF 0x87 0x95 0xA1 into 2 separate instructions
https://bugs.kde.org/show_bug.cgi?id=451837 Tom Hughes changed: What|Removed |Added Resolution|--- |DUPLICATE Status|REPORTED|RESOLVED --- Comment #7 from Tom Hughes --- *** This bug has been marked as a duplicate of bug 383010 *** -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 383010] Add support for AVX-512 instructions
https://bugs.kde.org/show_bug.cgi?id=383010 Tom Hughes changed: What|Removed |Added CC||fchen0...@gmail.com --- Comment #77 from Tom Hughes --- *** Bug 455279 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 455279] vex amd64->IR: unhandled instruction bytes: 0x62 0xD2 0xFD 0x28 0x7C 0xC8 0x62 0xF2 0xFD 0x28
https://bugs.kde.org/show_bug.cgi?id=455279 Tom Hughes changed: What|Removed |Added Resolution|--- |DUPLICATE Status|REPORTED|RESOLVED --- Comment #3 from Tom Hughes --- *** This bug has been marked as a duplicate of bug 383010 *** -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 383010] Add support for AVX-512 instructions
https://bugs.kde.org/show_bug.cgi?id=383010 Tom Hughes changed: What|Removed |Added CC||arkang...@gmail.com --- Comment #76 from Tom Hughes --- *** Bug 408140 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 408140] Missing support for vmovdqu64
https://bugs.kde.org/show_bug.cgi?id=408140 Tom Hughes changed: What|Removed |Added Resolution|--- |DUPLICATE Status|REPORTED|RESOLVED CC||t...@compton.nu --- Comment #2 from Tom Hughes --- *** This bug has been marked as a duplicate of bug 383010 *** -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 455279] vex amd64->IR: unhandled instruction bytes: 0x62 0xD2 0xFD 0x28 0x7C 0xC8 0x62 0xF2 0xFD 0x28
https://bugs.kde.org/show_bug.cgi?id=455279 --- Comment #2 from Tom Hughes --- Ah it's an EVEX prefix now but the opcode map in the Intel manual helpfully doesn't mention that... There is no AVX512 support in valgrind currently so you can't run code that is compiled to use AVX512 instructions. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 455279] vex amd64->IR: unhandled instruction bytes: 0x62 0xD2 0xFD 0x28 0x7C 0xC8 0x62 0xF2 0xFD 0x28
https://bugs.kde.org/show_bug.cgi?id=455279 Tom Hughes changed: What|Removed |Added CC||t...@compton.nu --- Comment #1 from Tom Hughes --- Well 0x62 is a BOUND instruction, or it would be in 32 bit mode, but it's not valid in 64 bit mode. Did you get any warnings from valgrind before that about referencing undefined values? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 455284] Swipe left/right gestures got inverted in 5.25
https://bugs.kde.org/show_bug.cgi?id=455284 Komorebi changed: What|Removed |Added Component|libinput|effects-various -- You are receiving this mail because: You are watching all bug changes.
[plasma-pa] [Bug 455283] plasma-pa 5.25.0 applet hides virtual devices by default
https://bugs.kde.org/show_bug.cgi?id=455283 Sam James changed: What|Removed |Added CC||ast...@gentoo.org, ||s...@gentoo.org -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 455284] New: Swipe left/right gestures got inverted in 5.25
https://bugs.kde.org/show_bug.cgi?id=455284 Bug ID: 455284 Summary: Swipe left/right gestures got inverted in 5.25 Product: kwin Version: 5.25.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: libinput Assignee: kwin-bugs-n...@kde.org Reporter: markovs.i.m...@gmail.com Target Milestone: --- Desktop switching gestures got inverted in 5.25 which is pretty uncomfortable to use STEPS TO REPRODUCE 1. Swipe with 4 fingers to the right to switch to the next desktop OBSERVED RESULT Kwin switches to the previous desktop EXPECTED RESULT Kwin switches to the next desktop Operating System: KDE neon 5.25 KDE Plasma Version: 5.25.0 KDE Frameworks Version: 5.95.0 Qt Version: 5.15.4 Kernel Version: 5.15.0-33-generic (64-bit) Graphics Platform: Wayland Processors: 16 × AMD Ryzen 7 5800HS with Radeon Graphics Memory: 22,9 GiB of RAM Graphics Processor: AMD RENOIR Manufacturer: ASUSTeK COMPUTER INC. Product Name: ROG Zephyrus G14 GA401QE_GA401QE System Version: 1.0 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 455237] Windows from another desktop is being rendered on top of current one
https://bugs.kde.org/show_bug.cgi?id=455237 --- Comment #6 from mira...@mirandastreeter.com --- Forgot to add my setup: Linux 5.18.3 Arch rolling release Qt 5.15.4 KDE Frameworks 5.95.0 Plasmashell 5.24.90 Nvidia proprietary driver 515.48.07 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 455251] Junction's overlay window is sometimes drawn with excessive transparency, depending on how it's invoked
https://bugs.kde.org/show_bug.cgi?id=455251 --- Comment #2 from Chase Lau --- I can't seem to make it happen with any other apps, no. I set it as the default application by using System Settings > Applications > Default Applications. I really don't know anything about how windows are drawn by kwin, but I'm very curious why these issues don't happen when Junction is called from another flatpak application. -- You are receiving this mail because: You are watching all bug changes.
[plasma-pa] [Bug 455283] New: plasma-pa 5.25.0 applet hides virtual devices by default
https://bugs.kde.org/show_bug.cgi?id=455283 Bug ID: 455283 Summary: plasma-pa 5.25.0 applet hides virtual devices by default Product: plasma-pa Version: 5.25.0 Platform: Gentoo Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: applet Assignee: plasma-b...@kde.org Reporter: 89q1r1...@relay.firefox.com CC: m...@ratijas.tk, now...@gmail.com Target Milestone: --- SUMMARY After upgrading to Plasma 5.25.0 I was very confused when plasma-pa widget did not show any device as being the default sink (output for clients). Upon restarting [PipeWire] daemons the plasma-pa OSD did show that the virtual sink I expected was in fact added, so I went to check if it's now the default and then I realized that it's still not showing any sink being default and that there was no mention of the virtual device which had clearly been added. Naturally I then checked the full KCM Audio panel which did in fact list it present and default. Therefore I checked widget's configuration options and found in it, I believe, a new entry called `Display: Show virtual devices` which for some reason was unchecked. This is wrong on two levels: 1) I find it hard to understand why would anyone want such functionality in the first place because there's usually no virtual devices at all, and when they are present, the only devices someone might want to hide in such case would be select physical devices [either for esthetic reasons or to avoid accidentally picking the real device when the intention is to always use the virtual] but they never want to hide the virtual devices. And 2) as a self evident consequence of the previous statement, one would *never* set such hiding as the default behavior, because any virtual devices present are there because something intentionally created them (with the only possible exception being the Dummy device which is there when no other audio node is present to save badly written PA clients from hanging themselves). STEPS TO REPRODUCE 1. pactl load-module module-null-sink sink_name=illustrative-test-sink OBSERVED RESULT By default the null sink created above will not be visible after upgrading to Plasma 5.25.0 EXPECTED RESULT Virtual sinks should always be visible by default because they are only created when something intentionally caused them to come about. It is not expected or intended for them to not be visible to the tool which is most obviously meant to manage them. SOFTWARE/OS VERSIONS Operating System: Gentoo Linux 2.8 KDE Plasma Version: 5.25.0 KDE Frameworks Version: 5.95.0 Qt Version: 5.15.4 Kernel Version: 5.19.0-rc2 (64-bit) Graphics Platform: Wayland Processors: 12 × 12th Gen Intel® Core™ i5-12400 Memory: 31.1 GiB of RAM Graphics Processor: AMD Radeon RX 580 Series Manufacturer: ASUS ADDITIONAL INFORMATION Users might appreciate a way to hide particular devices in the widget be them virtual or physical but that should be a strictly opt-in behavior and for a particular device rather than a blanket hiding of a particular device class or type. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 455282] Support for opening PDFs with page number
https://bugs.kde.org/show_bug.cgi?id=455282 --- Comment #1 from tcanabr...@kde.org --- Seems doable, is this # used by other file formats too? On Tue, 14 Jun 2022 at 22:14 wrote: > https://bugs.kde.org/show_bug.cgi?id=455282 > > Bug ID: 455282 >Summary: Support for opening PDFs with page number >Product: konsole >Version: 22.04.1 > Platform: Fedora RPMs > OS: Linux > Status: REPORTED > Severity: wishlist > Priority: NOR > Component: general > Assignee: konsole-de...@kde.org > Reporter: alexandre@zurcher.digital > Target Milestone: --- > > Created attachment 149714 > --> https://bugs.kde.org/attachment.cgi?id=149714=edit > Error in question, folder "test" contains one PDF file named "document.pdf" > > SUMMARY > When trying to open a PDF file finishing with page number (i.e > "document.pdf#2"), Konsole gives an error message that the file doesn't > exist. > Opening the same file by using the command `okular document.pdf#2` works as > intended. > > USECASE: I use a script based on pdfgrep to quickly find a PDF, then I > open it > in Okular by CTRL+clicking on it. Would be amazing for it to open at the > right > page as well ! > > STEPS TO REPRODUCE > 1. have a PDF document > 2. in Konsole, do `echo "'./document_name.pdf#2'"` > 3. try to CTRL+click './document_name.pdf#2' > > OBSERVED RESULT > Error message that the file doesn't exist (see screenshot for example - in > French) > > EXPECTED RESULT > PDF opening in Okular at the right page > > SOFTWARE/OS VERSIONS > Fedora Linux 36 > KDE Plasma Version: 5.24.5 > KDE Frameworks Version: 5.93.0 > Qt Version: 5.15.3 > > -- > You are receiving this mail because: > You are the assignee for the bug. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 455237] Windows from another desktop is being rendered on top of current one
https://bugs.kde.org/show_bug.cgi?id=455237 --- Comment #5 from mira...@mirandastreeter.com --- I, too, am seeing this issue, but only sporadically on certain boots about a fifth of the time. I have no indication how to reproduce this besides rebooting and crossing my fingers. In my situation I have no window rules and have not made any adjustments to default window management behavior. In an attempt to fix this I had tried clearing my entire .local and .config directory's k* and plasma* files/folders, starting with a fresh KDE experience for my user. Unfortunately, the issue returned. The only notable adjustments made were adding a taskbar to my secondary monitor and creating multiple horizontal virtual desktops. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 455282] New: Support for opening PDFs with page number
https://bugs.kde.org/show_bug.cgi?id=455282 Bug ID: 455282 Summary: Support for opening PDFs with page number Product: konsole Version: 22.04.1 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: general Assignee: konsole-de...@kde.org Reporter: alexandre@zurcher.digital Target Milestone: --- Created attachment 149714 --> https://bugs.kde.org/attachment.cgi?id=149714=edit Error in question, folder "test" contains one PDF file named "document.pdf" SUMMARY When trying to open a PDF file finishing with page number (i.e "document.pdf#2"), Konsole gives an error message that the file doesn't exist. Opening the same file by using the command `okular document.pdf#2` works as intended. USECASE: I use a script based on pdfgrep to quickly find a PDF, then I open it in Okular by CTRL+clicking on it. Would be amazing for it to open at the right page as well ! STEPS TO REPRODUCE 1. have a PDF document 2. in Konsole, do `echo "'./document_name.pdf#2'"` 3. try to CTRL+click './document_name.pdf#2' OBSERVED RESULT Error message that the file doesn't exist (see screenshot for example - in French) EXPECTED RESULT PDF opening in Okular at the right page SOFTWARE/OS VERSIONS Fedora Linux 36 KDE Plasma Version: 5.24.5 KDE Frameworks Version: 5.93.0 Qt Version: 5.15.3 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 455237] Windows from another desktop is being rendered on top of current one
https://bugs.kde.org/show_bug.cgi?id=455237 mira...@mirandastreeter.com changed: What|Removed |Added CC||mira...@mirandastreeter.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 455276] Menu doesn't open sometimes (pressing Win key). Also happens with tray icons and other panel popups
https://bugs.kde.org/show_bug.cgi?id=455276 Felipe Kinoshita changed: What|Removed |Added Ever confirmed|0 |1 Status|REPORTED|CONFIRMED CC||kinof...@gmail.com --- Comment #1 from Felipe Kinoshita --- Can reproduce -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 442451] Mysql-Internal crash
https://bugs.kde.org/show_bug.cgi?id=442451 --- Comment #13 from diekuhran...@web.de --- Unfortunately, there is again an error with mariadb. When I update mariadb from 10.06.5-2 to 10.8.3-1, then digiKam no longer works when i had chosen mysql. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 455281] New: Folder selector mounts CIFS shares on opening
https://bugs.kde.org/show_bug.cgi?id=455281 Bug ID: 455281 Summary: Folder selector mounts CIFS shares on opening Product: frameworks-kio Version: git master Platform: Neon Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kio-bugs-n...@kde.org Reporter: bugsefor...@gmx.com CC: kdelibs-b...@kde.org Target Milestone: --- Created attachment 149713 --> https://bugs.kde.org/attachment.cgi?id=149713=edit screen recording SUMMARY I use autofs to mount some CIFS shares on neon unstable. Every time I open the folder selector these shares are mounted. If the server computer is off, the folder selector takes a few seconds to load the folders list. Please watch the attached video showing what happens when I open the folder selector in Locations KCM. My CIFS shares are not mounted when I open save/open file dialogs. EXPECTED RESULT folder selector should not mount CIFS shares with autofs on opening SOFTWARE/OS VERSIONS Operating System: KDE neon Unstable Edition KDE Plasma Version: 5.25.80 KDE Frameworks Version: 5.96.0 Qt Version: 5.15.4 Graphics Platform: Wayland -- You are receiving this mail because: You are watching all bug changes.
[Planet KDE] [Bug 455268] Can't drag only a single window from one virtual desktop to another
https://bugs.kde.org/show_bug.cgi?id=455268 Niklāvs Koļesņikovs <89q1r1...@relay.firefox.com> changed: What|Removed |Added CC||89q1r1...@relay.firefox.com -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 455280] New: While arranging a single window, all windows in the same workspace move along together.
https://bugs.kde.org/show_bug.cgi?id=455280 Bug ID: 455280 Summary: While arranging a single window, all windows in the same workspace move along together. Product: kwin Version: 5.25.0 Platform: Neon Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: effects-desktop-grid Assignee: kwin-bugs-n...@kde.org Reporter: eridanired...@yahoo.com.mx Target Milestone: --- SUMMARY *** It used to be able to move a window from one desktop to another by dragging via the desktop grid effect, additionally, it was possible to rearrange all windows in a specific virtual desktop by dragging from the wallpaper instead of a window. After update to 25.0, the first feature seems to be lost, allowing only to rearrange whole groups of windows. Furthermore, dragging now requires two clicks to activate the action. See online clips in Dropbox posted below. *** STEPS TO REPRODUCE 1. Update Neon to 25.0 2. Open multiple windows in various workspaces, open a few per workspace. 3. Fire desktop grid effect from a hot corner 4. Try moving a window from one desktop to another. OBSERVED RESULT All windows in the same desktop move along while trying to move only one, see: - https://www.dropbox.com/s/11e3o1x49gmrt88/vokoscreen-2022-06-14_11-50-04.mkv?dl=0 EXPECTED RESULT Only the chosen window will be draged. See how it used to work: - https://www.dropbox.com/s/59ufkg3x8cxin1o/vokoscreen-2022-06-14_15-35-32.mkv?dl=0 SOFTWARE/OS VERSIONS - Operating System: KDE neon 5.25 - KDE Plasma Version: 5.25.0 - KDE Frameworks Version: 5.95.0 - Qt Version: 5.15.4 - Kernel Version: 5.13.0-48-generic (64-bit) - Graphics Platform: X11 - Processors: 4 × Intel® Core™ i5-4670 CPU @ 3.40GHz - Memory: 15.6 GiB of RAM - Graphics Processor: NVIDIA GeForce GTX 1060 3GB/PCIe/SSE2 ADDITIONAL INFORMATION These are the specs of the same system with the version that works well: - Operating System: KDE neon 5.24 - KDE Plasma Version: 5.24.5 - KDE Frameworks Version: 5.94.0 - Qt Version: 5.15.4 - Kernel Version: 5.13.0-44-generic (64-bit) -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 455115] Show pop-up notes text more directly
https://bugs.kde.org/show_bug.cgi?id=455115 --- Comment #7 from Albert Zeyer --- (In reply to Oliver Sander from comment #6) > From reading the description of your workflow it seems that your last > suggestion (having the annotation texts visible/accessible from the review > pane, in the side bar) seems most helpful. In an ideal world you would even > be able to navigate there with the keyboard alone, for increased speed. > > Would you be able to code such a feature? In principle yes, but I'm not familiar at all with the code, nor any KDE projects code. I have some minimal experience with Qt which I used maybe 10 years ago in some project. And I don't really have much (or any) free time. I was thinking more about my other tooltip suggestions as I assumed that those changes would probably be much simpler to implement, while they would be equally helpful for my use case. Currently I'm thinking anyway about yet another solution: Somehow extract the pop-up notes programmatically with some Python script, then use SyncTeX to find the corresponding place in the Latex code, and try to apply the patches directly, and maybe report me those where it can not be applied. The changes by the proofreading service are actually very consistent in style. Maybe they used some tool for that. They used strikethrough marks with note to indicate some replacement, otherwise just some addition. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 455226] Panorama Tool needs the Hugin pto2mk software
https://bugs.kde.org/show_bug.cgi?id=455226 --- Comment #11 from Steve --- Created attachment 149707 --> https://bugs.kde.org/attachment.cgi?id=149707=edit attachment-516-1.html --- Comment #12 from Steve --- Created attachment 149708 --> https://bugs.kde.org/attachment.cgi?id=149708=edit attachment-516-2.html --- Comment #13 from Steve --- Created attachment 149709 --> https://bugs.kde.org/attachment.cgi?id=149709=edit attachment-516-3.html --- Comment #14 from Steve --- Created attachment 149710 --> https://bugs.kde.org/attachment.cgi?id=149710=edit Screen Shot 2022-06-14 at 4.09.54 PM.png --- Comment #15 from Steve --- Created attachment 149711 --> https://bugs.kde.org/attachment.cgi?id=149711=edit Screen Shot 2022-06-14 at 4.12.13 PM.png --- Comment #16 from Steve --- Created attachment 149712 --> https://bugs.kde.org/attachment.cgi?id=149712=edit digikam-cli-startup-messages.txt -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 455226] Panorama Tool needs the Hugin pto2mk software
https://bugs.kde.org/show_bug.cgi?id=455226 --- Comment #10 from Steve --- Maik, I suspect having run Hugin directly yesturday made some changes in my computer. Today I was able to run the application but with a couple tweaks. I also downloaded the most recent version of Hugin available just to make sure I had it (2019.2.0.b690aa0334b5 built by Niklas Mischkulnig). 1. See the attached Panorama Creator Wizard screenshot where pto2mk is replaced by hugin_executor but there is no version number. 2. I ran digikam again but got an error message that it could not find enblend. See the second screenshot and the messages citing having to revert to system path. 3. So I modified my zsh path to include /Applications/Hugin/tools_mac and that made some progress. sbishop@MacBook-Pro ~ % echo $PATH /usr/local/sbin:/usr/local/bin:/usr/bin:/bin:/usr/sbin:/sbin:/opt/X11/bin:/Library/Apple/usr/bin:/Applications/Hugin/tools_mac sbishop@MacBook-Pro ~ % 4. But what actually worked and rendered a panorama is starting digikam from the terminal command line rather than from the digikam icon on my Launchpad. sbishop@MacBook-Pro ~ % /Applications/digiKam.org/digikam.app/Contents/MacOS/digikam & But this approach which is likely wrong way to do it, pops up a bunch of warning messages and Error # 11 because of my Affinity Photo images (.afphoto) file type. See the terminal messages in the attached file. So it appears to me that the digiKam 7.6.0 installation on Apple MacBook Pro running Monterey 12.4 might need some execution path changes to ensure Hugin’s tools_mac directory is found. Note: This was an interesting exercise since I haven’t work with Unix commands in quite a while. Sincerely, Steve Steve > On Jun 14, 2022, at 12:39 PM, Maik Qualmann wrote: > > https://bugs.kde.org/show_bug.cgi?id=455226 > > --- Comment #9 from Maik Qualmann --- > Exactly it depends on the returned version of "autooptimiser". As you can see > it is 2019.2 in your screenshot. So it is very strange that digiKam is looking > for pto2mk. A debug output from the terminal would be interesting. > > Maik > > -- > You are receiving this mail because: > You reported the bug. Dr. Steven Bishop, Ph.D. 100 Lakebreeze Way Fredericksburg, VA 22406 +1-540-429-1842 -- You are receiving this mail because: You are watching all bug changes.
[kdelibs] [Bug 297003] Newly created text files are not empty
https://bugs.kde.org/show_bug.cgi?id=297003 --- Comment #16 from Mario Aichinger --- Thanks for the hint with the Templates directory! > The default template should cater to the typical use case, i.e. a user who > wants to create a simple text file. I tend to disagree with the premise that the typical use case is creating a "simple text file". But I wouldn't have any data to disprove it. From all the files which are created with this action I don't know how many will have a .txt suffix as opposed to a .py, .xml, .ini or what ever else suffix... It just seams improbable to me that in most cases the extension will be .txt. And than again how often will a user on purpose create a file with no extension and expect it to be a "text file", I don't know. Still you might be right! That all said, would you oppose a MR which adds a "File" .desktop file and template to KIO which always creates an empty file regardless of the suffix? The "Text File" entry would stay and there just would be an extra entry which would just be called "File" since it would not create a new "text file" but a file in the most generic sense of the word, just an empty file with a extension chosen by the user. Could this be a compromise which would not change the existing option but improve the current situation to seemingly at least some users? -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 455279] New: vex amd64->IR: unhandled instruction bytes: 0x62 0xD2 0xFD 0x28 0x7C 0xC8 0x62 0xF2 0xFD 0x28
https://bugs.kde.org/show_bug.cgi?id=455279 Bug ID: 455279 Summary: vex amd64->IR: unhandled instruction bytes: 0x62 0xD2 0xFD 0x28 0x7C 0xC8 0x62 0xF2 0xFD 0x28 Product: valgrind Version: 3.20 GIT Platform: RedHat RPMs OS: Linux Status: REPORTED Severity: critical Priority: NOR Component: memcheck Assignee: jsew...@acm.org Reporter: fchen0...@gmail.com Target Milestone: --- SUMMARY ==182758== Memcheck, a memory error detector ==182758== Copyright (C) 2002-2022, and GNU GPL'd, by Julian Seward et al. ==182758== Using Valgrind-3.20.0.GIT and LibVEX; rerun with -h for copyright info vex amd64->IR: unhandled instruction bytes: 0x62 0xD2 0xFD 0x28 0x7C 0xC8 0x62 0xF2 0xFD 0x28 vex amd64->IR: REX=0 REX.W=0 REX.R=0 REX.X=0 REX.B=0 vex amd64->IR: VEX=0 VEX.L=0 VEX.n=0x0 ESC=NONE vex amd64->IR: PFX.66=0 PFX.F2=0 PFX.F3=0 ==182758== valgrind: Unrecognised instruction at address 0x5280f9. STEPS TO REPRODUCE 1. my specific code compiled on this platform failed to be traced by valgrind 2. The machine is Red Hat Enterprise Linux Server release 6.10 (Santiago) 3. The compiler is mix of gcc9.0 (with dev-toolset9) and icc-2019 SOFTWARE/OS VERSIONS Linux/KDE Plasma: Red Hat Enterprise Linux Server release 6.10 (Santiago) -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 455278] New: Discover (KDE Neon) is not showing the apt or Flatpak versions of some applications
https://bugs.kde.org/show_bug.cgi?id=455278 Bug ID: 455278 Summary: Discover (KDE Neon) is not showing the apt or Flatpak versions of some applications Product: Discover Version: 5.25.0 Platform: Neon Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: discover Assignee: lei...@leinir.dk Reporter: kairandm...@gmail.com CC: aleix...@kde.org Target Milestone: --- STEPS TO REPRODUCE 1. Open Discover; 2. Search for an application (like GIMP, for example). OBSERVED RESULT When searching for GIMP, for example, on Discover, only the Snap version shows up and there's no option to change the source when selecting it. This is happening with only some applications. For others the apt and Flatpak versions are showing up normally. EXPECTED RESULT The apt and Flatpak versions should be listed or there should be an option to change the source (apt, Flatpak or Snap). SOFTWARE/OS VERSIONS Linux/KDE Plasma: KDE Neon KDE Plasma Version: 5.25.0 KDE Frameworks Version: 5.95.0 Qt Version: 5.15.4 Kernel: 5.13.0-48-generic (64-bit) ADDITIONAL INFORMATION This was already happening before the update to Plasma 5.25.0. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 454919] ASSERT: "d->m_texture" in file kwin/src/libkwineffects/kwingltexture.cpp, line 451
https://bugs.kde.org/show_bug.cgi?id=454919 --- Comment #4 from neto0110 --- Created attachment 149705 --> https://bugs.kde.org/attachment.cgi?id=149705=edit trace -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 443690] kioslave5 crashed after click to icon in tasks list
https://bugs.kde.org/show_bug.cgi?id=443690 Ahmad Samir changed: What|Removed |Added CC||a.samir...@gmail.com Resolution|--- |WAITINGFORINFO Status|REPORTED|NEEDSINFO --- Comment #1 from Ahmad Samir --- Is this still an issue? -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 455277] New: No screenshot taken and memory leak when using keyboard shortcut twice
https://bugs.kde.org/show_bug.cgi?id=455277 Bug ID: 455277 Summary: No screenshot taken and memory leak when using keyboard shortcut twice Product: Spectacle Version: unspecified Platform: Manjaro OS: Linux Status: REPORTED Severity: major Priority: NOR Component: General Assignee: m...@baloneygeek.com Reporter: antonio.prc...@gmail.com CC: k...@david-redondo.de 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. launch Spectacle 22.07.70 with any keyboard shortcut 2. no screenshot taken, process `spectacle` visible and running 3. hit the same kb shortcut again, this time the screenshot gets taken 4. wait for the notification to disappear 5. spectacle eats up all the RAM bonus: 1. hit meta+shift+print for rectangular region 2. choose region, press enter or double click 3. no screenshot, so hit meta+shift+print again 4. can't confirm rectangular region , neither cancel with Esc 5. switch to another tty, ctrl+alt+F2, kill spectacle process OBSERVED RESULT spectacle runs in background and on second shortcut press, eats RAM EXPECTED RESULT should take the appropriate screenshot according to the shortcuts pressed SOFTWARE/OS VERSIONS Operating System: Manjaro Linux KDE Plasma Version: 5.24.5 KDE Frameworks Version: 5.95.0 Qt Version: 5.15.4 Kernel Version: 5.18.3-1-MANJARO (64-bit) Graphics Platform: X11 Processors: 8 × Intel® Core™ i5-8250U CPU @ 1.60GHz Memory: 15,4 GiB of RAM Graphics Processor: Mesa Intel® UHD Graphics 620 ADDITIONAL INFORMATION spectacle 22.07.70 (current master branch with last commit e410c573) Setting now as major, need someone to either confirm or deny this behavior. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kglobalaccel] [Bug 441203] Some PrtScr shortcuts stopped working for existing users
https://bugs.kde.org/show_bug.cgi?id=441203 Ahmad Samir changed: What|Removed |Added Resolution|--- |WAITINGFORINFO Status|REPORTED|NEEDSINFO CC||a.samir...@gmail.com --- Comment #2 from Ahmad Samir --- I can't reproduce this issue; do you still see it? -- You are receiving this mail because: You are watching all bug changes.
