[plasma-systemmonitor] [Bug 478085] System Monitor has a lot of graphical artifacts
https://bugs.kde.org/show_bug.cgi?id=478085 --- Comment #2 from Zhora Zmeikin --- The artifacts show up on the light theme as well, it's just less noticeable. I recommend testing in Breeze Dark theme. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 477853] digiKam 8.3.0 slow startup on Windows 10 operating system
https://bugs.kde.org/show_bug.cgi?id=477853 --- Comment #23 from Peter --- I don't know how important this information is... -- The newly released 8.2.0 also contains this bug -- Versions of 8.2.0 released at the beginning of November (weekly snapshots) did not yet contain this bug -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 472456] Laptop wakes up from screen saving mode in full brightness
https://bugs.kde.org/show_bug.cgi?id=472456 Marián Konček changed: What|Removed |Added Resolution|WAITINGFORINFO |--- Status|NEEDSINFO |CONFIRMED --- Comment #9 from Marián Konček --- I don't think so, I guess I will have to get used to it. Truth is, I opened the bug because I noticed the behaviour changed from what I was used to. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 450435] Panels missing after unlocking screen when screens have gone to sleep and woken up until plasmashell is restarted
https://bugs.kde.org/show_bug.cgi?id=450435 --- Comment #42 from Alex --- What about https://neon.kde.org/ ? -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 476629] Unstable ISO does not boot
https://bugs.kde.org/show_bug.cgi?id=476629 Nikos Platis changed: What|Removed |Added CC||npla...@gmail.com --- Comment #10 from Nikos Platis --- I am trying neon-unstable-20231203-1120.iso on VirtualBox 7.0.12 (Arch Linux host). With any combination of display driver / 3D acceleration, it only boots to the console with a login prompt. The same happens on QEMU. -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 478090] [NVIDIA] locking 2nd time in a Wayland session results in black screen with cursor
https://bugs.kde.org/show_bug.cgi?id=478090 --- Comment #2 from kodatar...@yahoo.com --- This seems to be affecting the Plasma 6 alpha, now beta only, I didn't experience it prior to the update. -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 476962] Screen does not respect "when locked, turn off after X seconds" setting
https://bugs.kde.org/show_bug.cgi?id=476962 --- Comment #10 from fanzhuyi...@gmail.com --- Alternately, how about having a separate checkbox saying immediately turn screen off after lock? -- You are receiving this mail because: You are watching all bug changes.
[colord-kde] [Bug 477083] Color Management KCM is not available under Plasma 6 because it does not yet support Qt6
https://bugs.kde.org/show_bug.cgi?id=477083 Adam Fontenot changed: What|Removed |Added Summary|No option to load ICC |Color Management KCM is not |profile under Xorg on |available under Plasma 6 |Plasma 6 Alpha |because it does not yet ||support Qt6 CC||adam.m.fontenot+kde@gmail.c ||om -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 478094] kwin_wayland crashes when toggling desktop grid effect in multi-monitor setup
https://bugs.kde.org/show_bug.cgi?id=478094 --- Comment #1 from fanzhuyi...@gmail.com --- I also trigger this without fractional scaling: Output: 1 eDP-1 enabled connected priority 1 Panel Modes: 0:2560x1600@240*! 1:2560x1600@60 2:1600x1200@60 3:1280x1024@60 4:1024x768@60 5:2560x1600@60 6:1920x1200@60 7:1280x800@60 8:2560x1440@60 9:1920x1080@60 10:1600x900@60 11:1368x768@60 12:1280x720@60 Geometry: 1920,0 2560x1600 Scale: 1 Rotation: 1 Overscan: 0 Vrr: Automatic RgbRange: Automatic HDR: incapable Wide Color Gamut: incapable ICC profile: none Output: 2 HDMI-A-1 enabled connected priority 2 HDMI Modes: 0:1920x1080@60*! 1:1920x1080@72 2:1920x1080@60 3:1920x1080@50 4:1680x1050@60 5:1600x900@60 6:1280x1024@60 7:1440x900@60 8:1280x800@60 9:1280x720@60 10:1280x720@60 11:1280x720@50 12:1024x768@70 13:1024x768@60 14:800x600@72 15:800x600@60 16:800x600@56 17:720x576@50 18:720x480@60 19:640x480@73 20:640x480@60 Geometry: 0,0 1920x1080 Scale: 1 Rotation: 1 Overscan: 0 Vrr: incapable RgbRange: unknown HDR: incapable Wide Color Gamut: incapable ICC profile: none This is also triggered without opening a ton of windows. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 477579] Plasma only tries to close native Wayland windows and not Xwayland ones causing data loss
https://bugs.kde.org/show_bug.cgi?id=477579 Adam Fontenot changed: What|Removed |Added CC||adam.m.fontenot+kde@gmail.c ||om -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 478090] [NVIDIA] locking 2nd time in a Wayland session results in black screen with cursor
https://bugs.kde.org/show_bug.cgi?id=478090 fanzhuyi...@gmail.com changed: What|Removed |Added Summary|When locking 2nd time in a |[NVIDIA] locking 2nd time |Wayland session, it just|in a Wayland session |gives black screen unable |results in black screen |to restore session, |with cursor |requires reboot from tty| --- Comment #1 from fanzhuyi...@gmail.com --- I remember seeing a bug just like this -- also with lock screen, not sleep/suspend to RAM. But I can't seem to find it. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 477738] [NVIDIA] kwin on Wayland black screen with cursor after most resume-from-RAM
https://bugs.kde.org/show_bug.cgi?id=477738 fanzhuyi...@gmail.com changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=478090 -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 478090] When locking 2nd time in a Wayland session, it just gives black screen unable to restore session, requires reboot from tty
https://bugs.kde.org/show_bug.cgi?id=478090 fanzhuyi...@gmail.com changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=477738 CC||fanzhuyi...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 477641] Displays wake up right after locking the screens and going to sleep
https://bugs.kde.org/show_bug.cgi?id=477641 fanzhuyi...@gmail.com changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=476962 -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 476962] Screen does not respect "when locked, turn off after X seconds" setting
https://bugs.kde.org/show_bug.cgi?id=476962 fanzhuyi...@gmail.com changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=477641 CC||fanzhuyi...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 453379] Allow me to set start and stop of charging on per battery level and not only globally
https://bugs.kde.org/show_bug.cgi?id=453379 Jakob Petsovits changed: What|Removed |Added CC||j.acco...@petsovits.com --- Comment #1 from Jakob Petsovits --- The ChargeThresholdHelper helper executable does iterate over all power supply batteries, it just doesn't expose that information/functionality in its interface. With a little bit of care and refactoring, it should be possible to distinguish between batteries and show that in the config UI. (Like always, someone has to sit down and implement it.) -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 478093] windows appear upside down in present windows effect if too many are open
https://bugs.kde.org/show_bug.cgi?id=478093 --- Comment #2 from fanzhuyi...@gmail.com --- (In reply to fanzhuyifan from comment #1) > I also trigger this without fractional scaling: > > Output: 1 eDP-1 > enabled > connected > priority 1 > Panel > Modes: 0:2560x1600@240*! 1:2560x1600@60 2:1600x1200@60 > 3:1280x1024@60 4:1024x768@60 5:2560x1600@60 6:1920x1200@60 7:1280x800@60 > 8:2560x1440@60 9:1920x1080@60 10:1600x900@60 11:1368x768@60 > 12:1280x720@60 > Geometry: 1920,0 2560x1600 > Scale: 1 > Rotation: 1 > Overscan: 0 > Vrr: Automatic > RgbRange: Automatic > HDR: incapable > Wide Color Gamut: incapable > ICC profile: none > Output: 2 HDMI-A-1 > enabled > connected > priority 2 > HDMI > Modes: 0:1920x1080@60*! 1:1920x1080@72 2:1920x1080@60 > 3:1920x1080@50 4:1680x1050@60 5:1600x900@60 6:1280x1024@60 7:1440x900@60 > 8:1280x800@60 9:1280x720@60 10:1280x720@60 11:1280x720@50 12:1024x768@70 > 13:1024x768@60 14:800x600@72 15:800x600@60 16:800x600@56 17:720x576@50 > 18:720x480@60 19:640x480@73 20:640x480@60 > Geometry: 0,0 1920x1080 > Scale: 1 > Rotation: 1 > Overscan: 0 > Vrr: incapable > RgbRange: unknown > HDR: incapable > Wide Color Gamut: incapable > ICC profile: none > > > This is also triggered without opening a ton of windows. Sorry that comment was meant for another bug report. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 478093] windows appear upside down in present windows effect if too many are open
https://bugs.kde.org/show_bug.cgi?id=478093 --- Comment #1 from fanzhuyi...@gmail.com --- I also trigger this without fractional scaling: Output: 1 eDP-1 enabled connected priority 1 Panel Modes: 0:2560x1600@240*! 1:2560x1600@60 2:1600x1200@60 3:1280x1024@60 4:1024x768@60 5:2560x1600@60 6:1920x1200@60 7:1280x800@60 8:2560x1440@60 9:1920x1080@60 10:1600x900@60 11:1368x768@60 12:1280x720@60 Geometry: 1920,0 2560x1600 Scale: 1 Rotation: 1 Overscan: 0 Vrr: Automatic RgbRange: Automatic HDR: incapable Wide Color Gamut: incapable ICC profile: none Output: 2 HDMI-A-1 enabled connected priority 2 HDMI Modes: 0:1920x1080@60*! 1:1920x1080@72 2:1920x1080@60 3:1920x1080@50 4:1680x1050@60 5:1600x900@60 6:1280x1024@60 7:1440x900@60 8:1280x800@60 9:1280x720@60 10:1280x720@60 11:1280x720@50 12:1024x768@70 13:1024x768@60 14:800x600@72 15:800x600@60 16:800x600@56 17:720x576@50 18:720x480@60 19:640x480@73 20:640x480@60 Geometry: 0,0 1920x1080 Scale: 1 Rotation: 1 Overscan: 0 Vrr: incapable RgbRange: unknown HDR: incapable Wide Color Gamut: incapable ICC profile: none This is also triggered without opening a ton of windows. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 478094] kwin_wayland crashes when toggling desktop grid effect in multi-monitor setup
https://bugs.kde.org/show_bug.cgi?id=478094 Bug Janitor Service changed: What|Removed |Added Keywords||qt6 -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 478096] Cannot tell anymore if window is snapped to panel - borderless window usability
https://bugs.kde.org/show_bug.cgi?id=478096 Bug Janitor Service changed: What|Removed |Added Keywords||qt6 -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 478096] Cannot tell anymore if window is snapped to panel - borderless window usability
https://bugs.kde.org/show_bug.cgi?id=478096 Jakob Petsovits changed: What|Removed |Added Summary|Cannot tell anymore if |Cannot tell anymore if |window is snapped to panel |window is snapped to panel ||- borderless window ||usability -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 478054] Right-Click window context menu on title bar opens along top edge of screen regardless of window position
https://bugs.kde.org/show_bug.cgi?id=478054 fanzhuyi...@gmail.com changed: What|Removed |Added Resolution|--- |NOT A BUG Status|REPORTED|RESOLVED --- Comment #4 from fanzhuyi...@gmail.com --- (In reply to Jonathan Isom from comment #3) > I was able to track down some more details. When using the Breeze window > decoration it works as expected. All the 3rd party themes that I have that > were made for Plasma 5 seem to be effected. I was using glowglass cupertino > when I noticed it initially. Not sure if that is considered a supported > configuration. Yeah I think that's not supported. Sorry. -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 478087] Poor ranking of search results
https://bugs.kde.org/show_bug.cgi?id=478087 --- Comment #4 from Alexander Lohnau --- >Can't reproduce the behavior for your case 1 on 5.27; the command match showed >before the system settings match for me already before. Yeah, that would be the expected behavior due to that being considered an exact match. I am not sure what a better solution might be, because sddm seems like a special case -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 478096] New: Cannot tell anymore if window is snapped to panel
https://bugs.kde.org/show_bug.cgi?id=478096 Bug ID: 478096 Summary: Cannot tell anymore if window is snapped to panel Classification: Plasma Product: Breeze Version: master Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: window decoration Assignee: plasma-b...@kde.org Reporter: j.acco...@petsovits.com CC: kwin-bugs-n...@kde.org, uhh...@gmail.com Target Milestone: --- SUMMARY Borderless windows are the default in Plasma 6. There is no recognizable line between window contents and panel anymore. When I maximize a window, vertically or all the way, I cannot tell if it's fully visible or if a part of it is hidden underneath the panel. This never bothered me with the previous multi-pixel borders, and I now find it very taxing not to know how tall my windows actually are. Especially when plugging or unplugging monitors can move windows around between displays and resize them, not always with the size & position I'd expect. STEPS TO REPRODUCE 1. Configure Breeze window decoration with the borderless theme default. Use light Breeze styles for panels & widgets. 2. Open Firefox and resize it such that the bottom snaps to your panel. 3. Navigate to a page that's taller than your screen. 4. Assume that you don't have immediate memory of your window resizing, either because of (un)plugging a monitor, or because you resumed from suspend after a night or two of not using your laptop, or just because you don't want to carry that mental overhead with you all the time. OBSERVED RESULT You can't tell if the Firefox window ends at the panel or continues below the panel. The only way to tell is to hover a link and see if its URL shows up at the bottom (if it does, you know where the bottom is). EXPECTED RESULT I have visual feedback whether the window ends at the panel or continues underneath it. SOFTWARE/OS VERSIONS Compositing: Yes, turned on, I get lots of shadows and whatnot Operating System: Arch Linux KDE Plasma Version: 5.90.0 KDE Frameworks Version: 5.246.0 Qt Version: 6.6.1 Kernel Version: 6.6.3-arch1-1 (64-bit) Graphics Platform: Wayland Processors: 8 × Intel® Core™ i7-8565U CPU @ 1.80GHz Memory: 15.3 GiB of RAM Graphics Processor: Mesa Intel® UHD Graphics 620 ADDITIONAL INFORMATION Clean style is neat and I'm not a hater of borderless or flat presentation, but we can't in good conscience ship with a major usability regression like that as a default. We have to draw a line somewhere. Presumably at the panel-facing edge of the window, but conceivably even on the panel's window-facing edge could be an option too. I'd be happy with even just a thin 1px line and only if shadows don't show, i.e. when window and panel snap together. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 478095] New: gif images rendered with kden live break upon uploading them to discord
https://bugs.kde.org/show_bug.cgi?id=478095 Bug ID: 478095 Summary: gif images rendered with kden live break upon uploading them to discord Classification: Applications Product: kdenlive Version: unspecified Platform: Other OS: Other Status: REPORTED Severity: normal Priority: NOR Component: Video Display & Export Assignee: j...@kdenlive.org Reporter: docdemor...@gmail.com Target Milestone: --- gif images rendered with kden live break upon uploading them to discord make a gif image using an existing gif works fine on desktop after render. upload it to discord, doesnt work, becomes still image. 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. 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.
[krunner] [Bug 478087] Poor ranking of search results
https://bugs.kde.org/show_bug.cgi?id=478087 --- Comment #3 from Alexander Lohnau --- Can you please attach the desktop file of the problem reporting app? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 478094] New: kwin_wayland crashes when toggling desktop grid effect in multi-monitor setup
https://bugs.kde.org/show_bug.cgi?id=478094
Bug ID: 478094
Summary: kwin_wayland crashes when toggling desktop grid effect
in multi-monitor setup
Classification: Plasma
Product: kwin
Version: master
Platform: Neon
OS: Linux
Status: REPORTED
Severity: crash
Priority: NOR
Component: effects-desktop-grid
Assignee: kwin-bugs-n...@kde.org
Reporter: fanzhuyi...@gmail.com
Target Milestone: ---
Created attachment 163892
--> https://bugs.kde.org/attachment.cgi?id=163892=edit
backtrace
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. Create 9 desktops in a 3x3 grid
2. Create a lot of windows on the external monitor (I ran seq 1 30 | xargs -I{}
bash -c "xclock -geometry 200x200 &")
3. Go to another desktop and trigger desktop grid effect
4. Repeat step 3.
OBSERVED RESULT
kwin_wayland crashes (see attachment for gdb backtrace)
EXPECTED RESULT
kwin_wayland shouldn't crash
SOFTWARE/OS VERSIONS
Operating System: KDE neon Unstable Edition
KDE Plasma Version: 5.90.0
KDE Frameworks Version: 5.246.0
Qt Version: 6.6.0
Kernel Version: 6.2.0-37-generic (64-bit)
Graphics Platform: Wayland
Processors: 20 × 13th Gen Intel® Core™ i9-13900H
Memory: 15.2 GiB of RAM
Graphics Processor: Mesa Intel® Graphics
Manufacturer: ASUSTeK COMPUTER INC.
Product Name: ROG Zephyrus G16 GU603VV_GU603VV
System Version: 1.0
ADDITIONAL INFORMATION
For me this is reproducible with high probability.
Also happened on my arch linux machine running master build.
The output of my kscreendoctor -o:
Output: 1 eDP-1
enabled
connected
priority 1
Panel
Modes: 0:2560x1600@240*! 1:2560x1600@60 2:1600x1200@60
3:1280x1024@60 4:1024x768@60 5:2560x1600@60 6:1920x1200@60 7:1280x800@60
8:2560x1440@60 9:1920x1080@60 10:1600x900@60 11:1368x768@60 12:1280x720@60
Geometry: 1920,0 1707x1067
Scale: 1.5
Rotation: 1
Overscan: 0
Vrr: Automatic
RgbRange: Automatic
HDR: incapable
Wide Color Gamut: incapable
ICC profile: none
Output: 2 HDMI-A-1
enabled
connected
priority 2
HDMI
Modes: 0:1920x1080@60*! 1:1920x1080@72 2:1920x1080@60
3:1920x1080@50 4:1680x1050@60 5:1600x900@60 6:1280x1024@60 7:1440x900@60
8:1280x800@60 9:1280x720@60 10:1280x720@60 11:1280x720@50 12:1024x768@70
13:1024x768@60 14:800x600@72 15:800x600@60 16:800x600@56 17:720x576@50
18:720x480@60 19:640x480@73 20:640x480@60
Geometry: 0,0 1920x1080
Scale: 1
Rotation: 1
Overscan: 0
Vrr: incapable
RgbRange: unknown
HDR: incapable
Wide Color Gamut: incapable
ICC profile: none
--
You are receiving this mail because:
You are watching all bug changes.
[drkonqi] [Bug 466919] DrKonqi crashed while submitting
https://bugs.kde.org/show_bug.cgi?id=466919 --- Comment #2 from Matt Fagnani --- Created attachment 163891 --> https://bugs.kde.org/attachment.cgi?id=163891=edit Trace of all threads of drkonqi crash -- You are receiving this mail because: You are watching all bug changes.
[drkonqi] [Bug 466919] DrKonqi crashed while submitting
https://bugs.kde.org/show_bug.cgi?id=466919 Matt Fagnani changed: What|Removed |Added CC||matt.fagn...@bell.net --- Comment #1 from Matt Fagnani --- I booted the Fedora Rawhide/40 KDE Plasma live image Fedora-KDE-Live-x86_64-Rawhide-20231204.n.0.iso on bare metal. I started Konsole in Plasma 5.90.0 on Wayland. I ran WAYLAND_DEBUG=1 plasmashell --replace. To troubleshoot the plasmashell crashes at https://bugs.kde.org/show_bug.cgi?id=478086 I started Dolphin I quickly moved the cursor over the Konsole icon in the task manager to the icons to its left (Firefox, Dolphin, Discover, System Settings). plasmashell crashed when I did that and the panel disappeared and reappeared automatically a few seconds later. drkonqi appeared. I selected Developer information, and created a trace. I tried to report through bugs.kde.org through drkonqi, but drkonqi crashed at the point that a list of possible duplicate reports was shown and I clicked on one of the reports. The crashing thread 7 had a segmentation fault with a trace like that in this report. Thread 7 (Thread 0x7f95e51d86c0 (LWP 5730)): #0 0x7f969b11b41d in __GI___poll (fds=fds@entry=0x7f95e51d6568, nfds=nfds@entry=1, timeout=timeout@entry=1000) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7f969dea1b98 in poll (__timeout=1000, __nfds=1, __fds=0x7f95e51d6568) at /usr/include/bits/poll2.h:39 #2 pollDrKonqiSocket (sockfd=3, pid=) at /usr/src/debug/kf6-kcrash-5.246.0-1.fc40.x86_64/src/kcrash.cpp:844 #3 KCrash::startProcess (argv=argv@entry=0x7f95e51d66a8, waitAndExit=waitAndExit@entry=true, argc=) at /usr/src/debug/kf6-kcrash-5.246.0-1.fc40.x86_64/src/kcrash.cpp:706 #4 0x7f969dea2659 in KCrash::defaultCrashHandler (sig=11) at /usr/src/debug/kf6-kcrash-5.246.0-1.fc40.x86_64/src/kcrash.cpp:602 #5 #6 pcre2_match_data_create_from_pattern_16 (code=0x0, gcontext=0x0) at src/pcre2_match_data.c:87 #7 0x7f969b9836aa in QRegularExpressionPrivate::doMatch (this=0x7f95e80011e0, priv=priv@entry=0x7f9620002a50, offset=, checkSubjectStringOption=checkSubjectStringOption@entry=QRegularExpressionPrivate::CheckSubjectString, previous=previous@entry=0x0) at /usr/src/debug/qt6-qtbase-6.6.1-1.fc40.x86_64/src/corelib/text/qregularexpression.cpp:1146 #8 0x7f969b983e0e in QRegularExpression::match (this=this@entry=0x55fdaea8e1d0 , subject=..., offset=offset@entry=0, matchType=matchType@entry=QRegularExpression::NormalMatch, matchOptions=..., matchOptions@entry=...) at /usr/src/debug/qt6-qtbase-6.6.1-1.fc40.x86_64/src/corelib/text/qregularexpression.cpp:1597 #9 0x55fdaea29b4b in BacktraceLineGdb::parse (this=this@entry=0x7f95e51d7410) at /usr/src/debug/plasma-drkonqi-5.90.0-1.fc40.x86_64/src/parser/backtraceparsergdb.cpp:119 #10 0x55fdaea2af00 in BacktraceLineGdb::BacktraceLineGdb (this=, lineStr=..., this=, lineStr=...) at /usr/src/debug/plasma-drkonqi-5.90.0-1.fc40.x86_64/src/parser/backtraceparsergdb.cpp:22 #11 0x55fdaea2b180 in BacktraceParserGdb::parseLine (lineStr=..., this=) at /usr/src/debug/plasma-drkonqi-5.90.0-1.fc40.x86_64/src/parser/backtraceparsergdb.cpp:200 #12 BacktraceParserGdb::newLine (this=, lineStr=...) at /usr/src/debug/plasma-drkonqi-5.90.0-1.fc40.x86_64/src/parser/backtraceparsergdb.cpp:191 #13 0x7f969b8027a8 in doActivate (sender=0x7f95e51d7660, signal_index=4, argv=0x7f95e51d76b0) at /usr/src/debug/qt6-qtbase-6.6.1-1.fc40.x86_64/src/corelib/kernel/qobject.cpp:4033 #14 0x7f969b7f8807 in QMetaObject::activate (sender=sender@entry=0x7f95e51d7660, m=m@entry=0x55fdaea86900 , local_signal_index=local_signal_index@entry=1, argv=argv@entry=0x7f95e51d76b0) at /usr/src/debug/qt6-qtbase-6.6.1-1.fc40.x86_64/src/corelib/kernel/qobject.cpp:4081 #15 0x55fdaea19d9e in ParseBugBacktraces::newLine (_t1=..., this=0x7f95e51d7660) at /usr/src/debug/plasma-drkonqi-5.90.0-1.fc40.x86_64/redhat-linux-build/src/DrKonqiInternal_autogen/include/moc_parsebugbacktraces.cpp:188 #16 ParseBugBacktraces::parse (comment=..., this=0x7f95e51d7660) at /usr/src/debug/plasma-drkonqi-5.90.0-1.fc40.x86_64/src/bugzillaintegration/parsebugbacktraces.cpp:126 #17 ParseBugBacktraces::parse (this=0x7f95e51d7660) at /usr/src/debug/plasma-drkonqi-5.90.0-1.fc40.x86_64/src/bugzillaintegration/parsebugbacktraces.cpp:113 #18 operator() (__closure=0x7f95e51d7630) at /usr/src/debug/plasma-drkonqi-5.90.0-1.fc40.x86_64/src/bugzillaintegration/duplicatefinderjob.cpp:108 #19 std::__invoke_impl >&, QObject*)::&> (__f=...) at /usr/include/c++/13/bits/invoke.h:61 #20 std::__invoke >&, QObject*)::&> (__fn=...) at /usr/include/c++/13/bits/invoke.h:96 #21 std::invoke >&, QObject*)::&> (__fn=...) at /usr/include/c++/13/functional:113 #22 operator() (function=..., __closure=) at /usr/include/qt6/QtConcurrent/qtconcurrentstoredfunctioncall.h:116 #23 std::__invoke_impl >
[krunner] [Bug 478058] History of searches does not open when clicking on the down arrow
https://bugs.kde.org/show_bug.cgi?id=478058 Bug Janitor Service changed: What|Removed |Added Status|CONFIRMED |ASSIGNED --- Comment #1 from Bug Janitor Service --- A possibly relevant merge request was started @ https://invent.kde.org/plasma/plasma-workspace/-/merge_requests/3657 -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 478058] History of searches does not open when clicking on the down arrow
https://bugs.kde.org/show_bug.cgi?id=478058 Alexander Lohnau changed: What|Removed |Added Assignee|plasma-b...@kde.org |alexander.loh...@gmx.de Ever confirmed|0 |1 Status|REPORTED|CONFIRMED -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 473876] Latte Dock (GitHub build) crashing when launching VirtualBox
https://bugs.kde.org/show_bug.cgi?id=473876 --- Comment #1 from Rohit --- Created attachment 163890 --> https://bugs.kde.org/attachment.cgi?id=163890=edit New crash information added by DrKonqi latte-dock (0.10.8) using Qt 5.15.11 Latte dock crashes when I open and close any sys tray item quite quickly (within a couple of seconds). Latte dock continues to work even after the crash report, however after this occurs about 2-3 times, latte dock has permanently crashed. -- Backtrace (Reduced): #4 0x7f798898b954 in QSGTexture::setFiltering(QSGTexture::Filtering) () at /usr/lib/libQt5Quick.so.5 #5 0x7f79889bb4d0 in QSGOpaqueTextureMaterialShader::updateState(QSGMaterialShader::RenderState const&, QSGMaterial*, QSGMaterial*) () at /usr/lib/libQt5Quick.so.5 #6 0x7f79889a44cf in QSGBatchRenderer::Renderer::renderMergedBatch(QSGBatchRenderer::Batch const*) () at /usr/lib/libQt5Quick.so.5 #7 0x7f79889a7d2e in QSGBatchRenderer::Renderer::renderBatches() () at /usr/lib/libQt5Quick.so.5 #8 0x7f79889ac7c6 in QSGBatchRenderer::Renderer::render() () at /usr/lib/libQt5Quick.so.5 -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 473876] Latte Dock (GitHub build) crashing when launching VirtualBox
https://bugs.kde.org/show_bug.cgi?id=473876 Rohit changed: What|Removed |Added CC||ro...@protonmail.com -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 477794] Commands have too low priority
https://bugs.kde.org/show_bug.cgi?id=477794 Bug Janitor Service changed: What|Removed |Added Status|NEEDSINFO |ASSIGNED Resolution|WAITINGFORINFO |--- --- Comment #5 from Bug Janitor Service --- A possibly relevant merge request was started @ https://invent.kde.org/plasma/systemsettings/-/merge_requests/273 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 478054] Right-Click window context menu on title bar opens along top edge of screen regardless of window position
https://bugs.kde.org/show_bug.cgi?id=478054 --- Comment #3 from Jonathan Isom --- I was able to track down some more details. When using the Breeze window decoration it works as expected. All the 3rd party themes that I have that were made for Plasma 5 seem to be effected. I was using glowglass cupertino when I noticed it initially. Not sure if that is considered a supported configuration. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 478093] windows appear upside down in present windows effect if too many are open
https://bugs.kde.org/show_bug.cgi?id=478093 fanzhuyi...@gmail.com changed: What|Removed |Added Keywords||qt6 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 478093] New: windows appear upside down in present windows effect if too many are open
https://bugs.kde.org/show_bug.cgi?id=478093
Bug ID: 478093
Summary: windows appear upside down in present windows effect
if too many are open
Classification: Plasma
Product: kwin
Version: master
Platform: Neon
OS: Linux
Status: REPORTED
Severity: minor
Priority: NOR
Component: effects-present-windows
Assignee: kwin-bugs-n...@kde.org
Reporter: fanzhuyi...@gmail.com
Target Milestone: ---
Created attachment 163889
--> https://bugs.kde.org/attachment.cgi?id=163889=edit
upside down windows
SUMMARY
***
NOTE: If you are reporting a crash, please try to attach a backtrace with debug
symbols.
See
https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports
***
STEPS TO REPRODUCE
1. Open a bunch of windows (I did seq 1 10 | xargs -I{} bash -c "xclock
-geometry 200x200 &")
2. Toggle present windows
OBSERVED RESULT
Some windows are upside down (see attachment)
EXPECTED RESULT
All windows are right side up
SOFTWARE/OS VERSIONS
Operating System: KDE neon Unstable Edition
KDE Plasma Version: 5.90.0
KDE Frameworks Version: 5.246.0
Qt Version: 6.6.0
Kernel Version: 6.2.0-37-generic (64-bit)
Graphics Platform: Wayland
Processors: 20 × 13th Gen Intel® Core™ i9-13900H
Memory: 15.2 GiB of RAM
Graphics Processor: Mesa Intel® Graphics
Manufacturer: ASUSTeK COMPUTER INC.
Product Name: ROG Zephyrus G16 GU603VV_GU603VV
System Version: 1.0
ADDITIONAL INFORMATION
I had the minimal overlap window placement.
The output of kscreendoctor -o is
Output: 1 eDP-1
enabled
connected
priority 1
Panel
Modes: 0:2560x1600@240*! 1:2560x1600@60 2:1600x1200@60
3:1280x1024@60 4:1024x768@60 5:2560x1600@60 6:1920x1200@60 7:1280x800@60
8:2560x1440@60 9:1920x1080@60 10:1600x900@60 11:1368x768@60 12:1280x720@60
Geometry: 1920,0 1707x1067
Scale: 1.5
Rotation: 1
Overscan: 0
Vrr: Automatic
RgbRange: Automatic
HDR: incapable
Wide Color Gamut: incapable
ICC profile: none
Output: 2 HDMI-A-1
enabled
connected
priority 2
HDMI
Modes: 0:1920x1080@60*! 1:1920x1080@72 2:1920x1080@60
3:1920x1080@50 4:1680x1050@60 5:1600x900@60 6:1280x1024@60 7:1440x900@60
8:1280x800@60 9:1280x720@60 10:1280x720@60 11:1280x720@50 12:1024x768@70
13:1024x768@60 14:800x600@72 15:800x600@60 16:800x600@56 17:720x576@50
18:720x480@60 19:640x480@73 20:640x480@60
Geometry: 0,0 1920x1080
Scale: 1
Rotation: 1
Overscan: 0
Vrr: incapable
RgbRange: unknown
HDR: incapable
Wide Color Gamut: incapable
ICC profile: none
--
You are receiving this mail because:
You are watching all bug changes.
[Powerdevil] [Bug 410029] Support suspend-and-hibernate (i.e. systemctl hybrid-sleep)
https://bugs.kde.org/show_bug.cgi?id=410029 Jakob Petsovits changed: What|Removed |Added CC||j.acco...@petsovits.com --- Comment #5 from Jakob Petsovits --- The changes in PowerDevil for Plasma 6 include a change where you can set one of three modes for the "Sleep" action: "Standby", "Hybrid sleep" and "Standby, then hibernate". This can be configured with a new field in the Energy Savings settings page with a label that says "When sleeping, enter: (...)" which replaces the previous awkward checkbox named "While asleep, hibernate after a period of inactivity. The idea is that "Sleep" will do system-wide whichever of the three you select. There's a chance that the changes have provided a way to get hybrid suspend into the logout screen, because selecting "Hybrid sleep" as sleep mode and then pressing "Sleep" should do the trick. I think so, at least. I wasn't able to test it because on my (imperfectly configured?) Plasma 6 dev environment, showing the logout screen made my display go grey with no further interaction possible. Maybe it works for the rest of you folks though. Someone please test on Plasma 6... thanks! -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 478091] Does not remove previous KCM header when switching to KDE Connect KCM
https://bugs.kde.org/show_bug.cgi?id=478091 Bug Janitor Service changed: What|Removed |Added Keywords||qt6 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 478092] New: Breeze light (light - dark - light again)
https://bugs.kde.org/show_bug.cgi?id=478092 Bug ID: 478092 Summary: Breeze light (light - dark - light again) Classification: Applications Product: systemsettings Version: 5.27.9 Platform: Neon OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: alexklimov...@ya.ru Target Milestone: --- Application: systemsettings (5.27.9) Qt Version: 5.15.11 Frameworks Version: 5.112.0 Operating System: Linux 6.2.0-37-generic x86_64 Windowing System: X11 Distribution: KDE neon 5.27 DrKonqi: 5.27.9 [KCrashBackend] -- Information about the crash: The system caused a crash when trying to change the theme to Breeze light (light - dark - light again) The reporter is unsure if this crash is reproducible. -- Backtrace: Application: Параметры системы (systemsettings), signal: Segmentation fault [KCrash Handler] #4 0x7f213be83ec8 in QQuickWindowPrivate::sendFilteredPointerEventImpl(QQuickPointerEvent*, QQuickItem*, QQuickItem*) () from /lib/x86_64-linux-gnu/libQt5Quick.so.5 #5 0x7f213be83de6 in QQuickWindowPrivate::sendFilteredPointerEventImpl(QQuickPointerEvent*, QQuickItem*, QQuickItem*) () from /lib/x86_64-linux-gnu/libQt5Quick.so.5 #6 0x7f213be83de6 in QQuickWindowPrivate::sendFilteredPointerEventImpl(QQuickPointerEvent*, QQuickItem*, QQuickItem*) () from /lib/x86_64-linux-gnu/libQt5Quick.so.5 #7 0x7f213be83de6 in QQuickWindowPrivate::sendFilteredPointerEventImpl(QQuickPointerEvent*, QQuickItem*, QQuickItem*) () from /lib/x86_64-linux-gnu/libQt5Quick.so.5 #8 0x7f213be84b9e in QQuickWindowPrivate::deliverToPassiveGrabbers(QVector > const&, QQuickPointerEvent*) () from /lib/x86_64-linux-gnu/libQt5Quick.so.5 #9 0x7f213be8b155 in QQuickWindowPrivate::deliverMouseEvent(QQuickPointerMouseEvent*) () from /lib/x86_64-linux-gnu/libQt5Quick.so.5 #10 0x7f213be8c8a3 in QQuickWindowPrivate::deliverPointerEvent(QQuickPointerEvent*) () from /lib/x86_64-linux-gnu/libQt5Quick.so.5 #11 0x7f213be8daad in QQuickWindowPrivate::handleMouseEvent(QMouseEvent*) () from /lib/x86_64-linux-gnu/libQt5Quick.so.5 #12 0x7f213df4f215 in QWindow::event(QEvent*) () from /lib/x86_64-linux-gnu/libQt5Gui.so.5 #13 0x7f213e76c763 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #14 0x7f213dabc8ea in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #15 0x7f213c94931b in QQuickWidget::mouseReleaseEvent(QMouseEvent*) () from /lib/x86_64-linux-gnu/libQt5QuickWidgets.so.5 #16 0x7f213e7af95e in QWidget::event(QEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #17 0x7f213e76c763 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #18 0x7f213e7743a4 in QApplication::notify(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #19 0x7f213dabc8ea in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #20 0x7f213e772e87 in QApplicationPrivate::sendMouseEvent(QWidget*, QMouseEvent*, QWidget*, QWidget*, QWidget**, QPointer&, bool, bool) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #21 0x7f213e7c91db in ?? () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #22 0x7f213e7cc535 in ?? () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #23 0x7f213e76c763 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #24 0x7f213dabc8ea in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #25 0x7f213df43197 in QGuiApplicationPrivate::processMouseEvent(QWindowSystemInterfacePrivate::MouseEvent*) () from /lib/x86_64-linux-gnu/libQt5Gui.so.5 #26 0x7f213df16dbc in QWindowSystemInterface::sendWindowSystemEvents(QFlags) () from /lib/x86_64-linux-gnu/libQt5Gui.so.5 #27 0x7f2138afbfae in ?? () from /lib/x86_64-linux-gnu/libQt5XcbQpa.so.5 #28 0x7f213c251d3b in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #29 0x7f213c2a7258 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #30 0x7f213c24f3e3 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #31 0x7f213db15dd8 in QEventDispatcherGlib::processEvents(QFlags) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #32 0x7f213dabb20b in QEventLoop::exec(QFlags) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #33 0x7f213dac37b4 in QCoreApplication::exec() () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #34 0x5620fe5b7616 in ?? () #35 0x7f213d029d90 in __libc_start_call_main (main=main@entry=0x5620fe5b6ac0, argc=argc@entry=1, argv=argv@entry=0x7ffeab7269e8) at ../sysdeps/nptl/libc_start_call_main.h:58 #36 0x7f213d029e40 in
[systemsettings] [Bug 478091] New: Does not remove previous KCM header when switching to KDE Connect KCM
https://bugs.kde.org/show_bug.cgi?id=478091 Bug ID: 478091 Summary: Does not remove previous KCM header when switching to KDE Connect KCM Classification: Applications Product: systemsettings Version: 5.90.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: j.acco...@petsovits.com Target Milestone: --- SUMMARY Weird visual bug that ends up in two KCM headers showing at the same time. The KDE Connect KCM already has a non-standard header bar, with header title misaligned and no separator below it. I was tempted to report it in that component. However, removing the previous header bar when switching to a different (however non-standard) KCM is the job of the System Settings app. So here goes. STEPS TO REPRODUCE 1. Open the "Device Actions" KCM in System Settings. It doesn't matter if you navigate there via "Disks & Cameras" or open it directly via KRunner. 2. Press back in the sidebar and click on "KDE Connect" to navigate there. OBSERVED RESULT The header bar from "Device Actions" is still present. Below it you can find the entirety of the "KDE Connect" KCM, including its own "KDE Connect" header. EXPECTED RESULT The "Device Actions" header disappears and the main view only shows the "KDE Connect" KCM by itself. SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 5.90.0 KDE Frameworks Version: 5.246.0 Qt Version: 6.6.1 Kernel Version: 6.6.3-arch1-1 (64-bit) Graphics Platform: Wayland Processors: 8 × Intel® Core™ i7-8565U CPU @ 1.80GHz Memory: 15.3 GiB of RAM Graphics Processor: Mesa Intel® UHD Graphics 620 ADDITIONAL INFORMATION This can also be reproduced with "Keyboard" or "Wi-Fi & Networking" instead of "Device Actions". Which strongly suggests that this is an interaction between 1. QtWidget KCM as the origin to navigate away from, 2. whatever weird stuff the (presumably also QtWidget-based) KDE Connect KCM is doing to avoid using the native System Settings header. No screenshot because I still haven't figured out how to make privileged D-Bus services work in my Plasma 6 dev environment. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 478084] Digikam 8.x language issue on macOS
https://bugs.kde.org/show_bug.cgi?id=478084 caulier.gil...@gmail.com changed: What|Removed |Added CC||caulier.gil...@gmail.com --- Comment #1 from caulier.gil...@gmail.com --- With the 8.2.0 just released and current pre-release version, the problem is not reproducible on my macbook pro: https://imgur.com/F3b4pO9 Best regards Gilles Caulier -- You are receiving this mail because: You are watching all bug changes.
[drkonqi] [Bug 475084] Unnecessary empty space between paragraphs in "What is a backtrace?" step
https://bugs.kde.org/show_bug.cgi?id=475084 Harald Sitter changed: What|Removed |Added CC||sit...@kde.org --- Comment #2 from Harald Sitter --- It's where the advanced info view goes. The trick is that the debug info is visible no matter what, the description paragraph along with the empty space gets replaced by the advanced data view when clicking that button. Not sure we'll want to spend too much time on this since we now have proper automatic reports. What we could do is simply throw away the description paragraph. Since this entire page is now hidden behind the developer info button we could just assume the user knows what they are looking at. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 478035] I chose a picture and applied a face tag to it but I was unable to enter a name for the person and the the program crashed
https://bugs.kde.org/show_bug.cgi?id=478035 --- Comment #3 from caulier.gil...@gmail.com --- Hi Richard, To your Q from a private mail: "I noticed that the photo I had been trying to put a face tag on was already in the ‘Unknown’ folder awaiting my confirmation. I wonder if this had anything to do with my program crashes yesterday? " The crash appears while the processing of items properties in the database. The database model used with the item was not locked/ulocked properly so the result at crash in unpredictable Best Gilles Caulier -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 476452] Right-clicking in containment crashes plasmashell
https://bugs.kde.org/show_bug.cgi?id=476452 --- Comment #3 from Harald Sitter --- *** Bug 476453 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[drkonqi] [Bug 476453] plasmashell crash crashes DrKonqi
https://bugs.kde.org/show_bug.cgi?id=476453 Harald Sitter changed: What|Removed |Added Status|REPORTED|RESOLVED CC||sit...@kde.org Resolution|--- |DUPLICATE --- Comment #1 from Harald Sitter --- Crashed because of the same reason plasmashell crashed: qqc2-desktop-style *** This bug has been marked as a duplicate of bug 476452 *** -- You are receiving this mail because: You are watching all bug changes.
[drkonqi] [Bug 470190] Dr. Konqi doesn't always show up when plasmashell crashes
https://bugs.kde.org/show_bug.cgi?id=470190 Bug Janitor Service changed: What|Removed |Added Status|REPORTED|ASSIGNED Ever confirmed|0 |1 --- Comment #8 from Bug Janitor Service --- A possibly relevant merge request was started @ https://invent.kde.org/plasma/plasma-workspace/-/merge_requests/3656 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 478035] I chose a picture and applied a face tag to it but I was unable to enter a name for the person and the the program crashed
https://bugs.kde.org/show_bug.cgi?id=478035 caulier.gil...@gmail.com changed: What|Removed |Added Version Fixed In|8.3 |8.3.0 Resolution|--- |FIXED Status|REPORTED|RESOLVED -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 478089] Previews in the size dropdown have wrong sizes
https://bugs.kde.org/show_bug.cgi?id=478089 Bug Janitor Service changed: What|Removed |Added Keywords||qt6 -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 478090] When locking 2nd time in a Wayland session, it just gives black screen unable to restore session, requires reboot from tty
https://bugs.kde.org/show_bug.cgi?id=478090 Bug Janitor Service changed: What|Removed |Added Keywords||qt6 -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 478090] New: When locking 2nd time in a Wayland session, it just gives black screen unable to restore session, requires reboot from tty
https://bugs.kde.org/show_bug.cgi?id=478090 Bug ID: 478090 Summary: When locking 2nd time in a Wayland session, it just gives black screen unable to restore session, requires reboot from tty Classification: Plasma Product: kscreenlocker Version: 5.90.0 Platform: Other OS: Linux Status: REPORTED Severity: major Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: kodatar...@yahoo.com Target Milestone: --- SUMMARY When locking the PC, first time is successful, but second time gives you black screen with a cursor, which there is no way to return back to plasma unless you go to tty and reboot the PC STEPS TO REPRODUCE 1. super+L to lock screen, or just lock the screen from application menu on a wayland session OBSERVED RESULT black screen with mouse cursor EXPECTED RESULT to be working correctly SOFTWARE/OS VERSIONS Operating System: EndeavourOS KDE Plasma Version: 5.90.0 KDE Frameworks Version: 5.246.0 Qt Version: 6.6.1 Kernel Version: 6.6.3-zen1-1-zen (64-bit) Graphics Platform: Wayland Processors: 16 × AMD Ryzen 7 5800X3D 8-Core Processor Memory: 31,2 GiB of RAM Graphics Processor: NVIDIA GeForce RTX 3090/PCIe/SSE2 -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 477700] Terminal shrinks when creating new/switching tabs on x11
https://bugs.kde.org/show_bug.cgi?id=477700 --- Comment #9 from RocketDev <13736845...@163.com> --- (In reply to fanzhuyifan from comment #8) > (In reply to RocketDev from comment #7) > > I have this problem too! Several days ago, my Konsole began to shrink on > > size when altering tabs slightly not only vertically but even horizontally. > > Using Kwin on X11. > > Which version are you on? I'm a Arch Linux user, so everything should be latest as I often update my system. Konsole: 23.08.3; Kwin 3.27.9 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 478089] Previews in the size dropdown have wrong sizes
https://bugs.kde.org/show_bug.cgi?id=478089 --- Comment #1 from Jin Liu --- Created attachment 163888 --> https://bugs.kde.org/attachment.cgi?id=163888=edit Breeze -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 478089] New: Previews in the size dropdown have wrong sizes
https://bugs.kde.org/show_bug.cgi?id=478089 Bug ID: 478089 Summary: Previews in the size dropdown have wrong sizes Classification: Applications Product: systemsettings Version: 5.90.0 Platform: Arch Linux OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: kcm_cursortheme Assignee: plasma-b...@kde.org Reporter: ad.liu@gmail.com Target Milestone: --- Created attachment 163887 --> https://bugs.kde.org/attachment.cgi?id=163887=edit Adwaita SUMMARY See attachments. Different sizes seem to be rendered as the same. E.g. 48 and 64 in Adwaita, 48, 54 and 60 in (patched) Breeze. Global scale: 250% SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 5.90.0 KDE Frameworks Version: 5.246.0 Qt Version: 6.6.1 Kernel Version: 6.6.3-arch1-1 (64-bit) Graphics Platform: offscreen Processors: 12 × AMD Ryzen 5 5600H with Radeon Graphics Memory: 13.5 GiB of RAM Graphics Processor: AMD Radeon Graphics -- You are receiving this mail because: You are watching all bug changes.
[drkonqi] [Bug 270002] DrKonqi fails to recognize debug symbol installation until it is reinitialized (even when reloaded).
https://bugs.kde.org/show_bug.cgi?id=270002 Harald Sitter changed: What|Removed |Added Resolution|--- |WORKSFORME Status|REOPENED|RESOLVED --- Comment #15 from Harald Sitter --- Please don't necro ancient bug reports. The reason this happened to you is because you did a live update without re-login, removing files out from under the process and thereby making the process untraceable. Note this line from your kcrash file: #5 0x7f6b574eeb01 n/a (/usr/lib64/libkwin.so.5.27.8 (deleted) + 0x2eeb01) -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 476493] Guides used previously stop the playback of a new longer clip placed in the same position, even after deleting the guides.
https://bugs.kde.org/show_bug.cgi?id=476493 Bug Janitor Service changed: What|Removed |Added Resolution|WAITINGFORINFO |WORKSFORME Status|NEEDSINFO |RESOLVED --- Comment #6 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.
[Skanpage] [Bug 458179] Icons not showing in SwayWM
https://bugs.kde.org/show_bug.cgi?id=458179 Bug Janitor Service changed: What|Removed |Added Resolution|WAITINGFORINFO |WORKSFORME Status|NEEDSINFO |RESOLVED --- Comment #3 from Bug Janitor Service --- This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 476429] Right click on mouse freezes entire konsole application
https://bugs.kde.org/show_bug.cgi?id=476429 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 478027] System Tray icons are space oddly
https://bugs.kde.org/show_bug.cgi?id=478027 --- Comment #4 from Doug --- (In reply to Niccolò Venerandi from comment #2) > I believe that what you're showing is a setup with the following widgets: > - Clipboard > - Audio > - Bluetooth > - Margin Separator > - System Tray > (clock, search, ...) > > The distance between the first three widgets is decided by the panel. > The margin separator creates an awkward space due to a bug that's now fixed. > The distance between the system tray applets is decided by the system tray. > > The above should explain the situation; is that correct? These are all system tray icons, I think. Here is a screenshot with the System Tray open, with the blue line highlighting all those widgets. I also tried adding an additional Bluetooth widget to the left of the system tray icons, it is not highlighted when I open the system tray in a similar manner. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 478027] System Tray icons are space oddly
https://bugs.kde.org/show_bug.cgi?id=478027 --- Comment #3 from Doug --- Created attachment 163886 --> https://bugs.kde.org/attachment.cgi?id=163886=edit System Tray open -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 478020] The OSD aka visual feedback popup (e.g. for volume and brightness) does not show
https://bugs.kde.org/show_bug.cgi?id=478020 --- Comment #10 from jvy...@jvyden.xyz --- (In reply to fanzhuyifan from comment #9) > It is in the big red warning here: > https://wiki.archlinux.org/title/Official_repositories#Testing_repositories Whoops, that's embarrassing, haha. I've installed the testing repositories and updated but the issue still persists. > Closing this as this is a downstream issue. Happy to help you on the arch > forums, though. Sure, I made a thread on the Testing subforum: https://bbs.archlinux.org/viewtopic.php?pid=2135335#p2135335 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 477124] cursor is able to escape a fullscreen, window, borderless in apex legends under plasma 5.81.0 wayland
https://bugs.kde.org/show_bug.cgi?id=477124 Pollux changed: What|Removed |Added Resolution|FIXED |--- Status|RESOLVED|REOPENED Ever confirmed|0 |1 --- Comment #3 from Pollux --- it has returned :( -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 476962] Screen does not respect "when locked, turn off after X seconds" setting
https://bugs.kde.org/show_bug.cgi?id=476962 --- Comment #9 from Natalie Clarius --- Ah, I see the problem. Yeah, it probably makes sense to go back to screen off after some idle time after input in locked state, though I don't think we'd need to make this timeout configurable. I think just setting it to 1 minute in that case would capture the users's intentions well enough. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 477700] Terminal shrinks when creating new/switching tabs on x11
https://bugs.kde.org/show_bug.cgi?id=477700 --- Comment #8 from fanzhuyi...@gmail.com --- (In reply to RocketDev from comment #7) > I have this problem too! Several days ago, my Konsole began to shrink on > size when altering tabs slightly not only vertically but even horizontally. > Using Kwin on X11. Which version are you on? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 474982] Battery applet no longer tells why the power management is inhibited
https://bugs.kde.org/show_bug.cgi?id=474982 --- Comment #19 from Bug Janitor Service --- A possibly relevant merge request was started @ https://invent.kde.org/plasma/plasma-workspace/-/merge_requests/3655 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 475243] Allow choosing the time before hibernating while asleep
https://bugs.kde.org/show_bug.cgi?id=475243 --- Comment #8 from Jakob Petsovits --- (In reply to zzrakic from comment #7) > Can I ask if selecting "Hibernate" at "While sleeping, enter:", will give > you an option to set specific time period after which this will happen? > In case it is not changeable, what is the default value? Could you in that > case add info icon on which user could hover and find out after what time > action happens? The UI revamp did not add any functionality that wasn't already there. So you can continue to select a time delay in the top-most field called "After a period of inactivity: (Sleep, Hibernate, Shut down, etc.)" but we still don't have a field to specify the delay for this sleep mode that's now called "Standby, then Hibernate". The PowerDevil backend doesn't support this, so it's not as easy as just adding a field in the settings page. As mentioned by the OP, this functionality is performed by and configured through systemd. If we want to display or modify it, we'll have to add code to query systemd and perhaps overwrite that /etc/systemd/sleep.conf if there isn't an easier way to do it programmatically. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 477700] Terminal shrinks when creating new/switching tabs on x11
https://bugs.kde.org/show_bug.cgi?id=477700 fanzhuyi...@gmail.com changed: What|Removed |Added Summary|Terminal shrinks when |Terminal shrinks when |creating new/switching tabs |creating new/switching tabs ||on x11 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 474982] Battery applet no longer tells why the power management is inhibited
https://bugs.kde.org/show_bug.cgi?id=474982 --- Comment #18 from Jin Liu --- (In reply to Natalie Clarius from comment #17) > (In reply to Jin Liu from comment #14) > > > BTW, I don't see why the applet hides inhibitors when the manual switch is > > on. > > I think the idea was that the information is redundant since when the manual > inhibition is on, it won't go to sleep anyway. But the same applies to > having more than one app inhibition, and it just makes the logic more > complicated, so I would be fine with changing it to simply always showing > all active inhibition sources. Yeah. And also it would be consistent with the kscreen applet in that way. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 478020] The OSD aka visual feedback popup (e.g. for volume and brightness) does not show
https://bugs.kde.org/show_bug.cgi?id=478020 fanzhuyi...@gmail.com changed: What|Removed |Added Resolution|--- |DOWNSTREAM Status|REPORTED|RESOLVED --- Comment #9 from fanzhuyi...@gmail.com --- (In reply to jvyden from comment #6) > Yes, I installed Plasma 6 through the kde-unstable repository. I did not > know I needed the testing repositories also enabled; I feel as if the > documentation on ArchWiki could be a bit more clear on this, as I feel like > I did a fair bit of research before switching (but I understand that's not > KDE's problem). It is in the big red warning here: https://wiki.archlinux.org/title/Official_repositories#Testing_repositories > Upon further investigation, I discovered that there is no 'Breeze' theme > under Plasma Style. Infact, no Plasma Style was selected. Setting one caused > the layout problems to fix themselves but that also means I'm using the old > Spectrum Classic layout that's apparently causing problems. Interestingly, > though, the OSD still works despite that. That sounds very much a downstream packaging issue. There definitely should Breeze and Breeze Dark styles. Closing this as this is a downstream issue. Happy to help you on the arch forums, though. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 474982] Battery applet no longer tells why the power management is inhibited
https://bugs.kde.org/show_bug.cgi?id=474982 --- Comment #17 from Natalie Clarius --- (In reply to Jin Liu from comment #14) > BTW, I don't see why the applet hides inhibitors when the manual switch is > on. I think the idea was that the information is redundant since when the manual inhibition is on, it won't go to sleep anyway. But the same applies to having more than one app inhibition, and it just makes the logic more complicated, so I would be fine with changing it to simply always showing all active inhibition sources. -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 476962] Screen does not respect "when locked, turn off after X seconds" setting
https://bugs.kde.org/show_bug.cgi?id=476962 --- Comment #8 from Jakob Petsovits --- And sorry for conflating "sleeping" with "turning off screen" in the comment above. I meant the latter. Same idea though. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 478020] The OSD aka visual feedback popup (e.g. for volume and brightness) does not show
https://bugs.kde.org/show_bug.cgi?id=478020 --- Comment #8 from jvy...@jvyden.xyz --- Created attachment 163885 --> https://bugs.kde.org/attachment.cgi?id=163885=edit My fixed desktop after applying a Plasma Style Here's a screenshot showing my Plasma Styles and the layout I would expect. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 478020] The OSD aka visual feedback popup (e.g. for volume and brightness) does not show
https://bugs.kde.org/show_bug.cgi?id=478020 --- Comment #7 from jvy...@jvyden.xyz --- Created attachment 163884 --> https://bugs.kde.org/attachment.cgi?id=163884=edit My desktop after selecting the 'Breeze' theme Okay, switching to Breeze technically 'fixed' the issue after a restart of Plasma, but this brought up an even stranger issue. Upon loading into the desktop, I tested the volume controls and the OSD did indeed come up. However, I noticed that the layout is seemingly broken. Attached is a screenshot of my desktop with this broken layout. Upon further investigation, I discovered that there is no 'Breeze' theme under Plasma Style. Infact, no Plasma Style was selected. Setting one caused the layout problems to fix themselves but that also means I'm using the old Spectrum Classic layout that's apparently causing problems. Interestingly, though, the OSD still works despite that. -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 476962] Screen does not respect "when locked, turn off after X seconds" setting
https://bugs.kde.org/show_bug.cgi?id=476962 --- Comment #7 from Jakob Petsovits --- (In reply to Natalie Clarius from comment #6) > Why do you think we need two different settings? Imo setting it to 0s should > turn it off immediately when going unlocked -> locked but also turn on again > immediately once there is input in already locked state. Let's say that 0s is the configured timeout for sleeping when the system transitions from unlocked to locked. So it goes to sleep immediately after locking. We have also established that we can't (shouldn't) use 0s as a timeout after user input when already locked. I think it's also clear that if the user stops typing / doesn't manage to log in, there should still be a timeout (>0s) for putting the system back to sleep. We can call this a "setting" or anything else, and it doesn't have to be user-configurable, but it seems clear that another timeout value is needed apart from the original (0s) configured one. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 474982] Battery applet no longer tells why the power management is inhibited
https://bugs.kde.org/show_bug.cgi?id=474982 --- Comment #16 from Bug Janitor Service --- A possibly relevant merge request was started @ https://invent.kde.org/plasma/plasma-workspace/-/merge_requests/3654 -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 477700] Terminal shrinks when creating new/switching tabs
https://bugs.kde.org/show_bug.cgi?id=477700 RocketDev <13736845...@163.com> changed: What|Removed |Added CC||13736845...@163.com --- Comment #7 from RocketDev <13736845...@163.com> --- I have this problem too! Several days ago, my Konsole began to shrink on size when altering tabs slightly not only vertically but even horizontally. Using Kwin on X11. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 478020] The OSD aka visual feedback popup (e.g. for volume and brightness) does not show
https://bugs.kde.org/show_bug.cgi?id=478020 --- Comment #6 from jvy...@jvyden.xyz --- (In reply to fanzhuyifan from comment #5) > How did you install plasma 6 beta 1? From the kde-unstable repo? > You also need to enable the testing repos if you do that. Yes, I installed Plasma 6 through the kde-unstable repository. I did not know I needed the testing repositories also enabled; I feel as if the documentation on ArchWiki could be a bit more clear on this, as I feel like I did a fair bit of research before switching (but I understand that's not KDE's problem). Do I just need the extra-testing repository or the core-testing repository enabled as well? > What theme are you using? Could you try using the default themes (breeze)? I > noticed this in the log: > > Dec 04 19:52:17 the-overcooler plasmashell[13130]: kf.svg: The theme > > "spectrum-classic-basic" uses the legacy metadata.desktop. Consider > > contacting the author and asking them update it to use the newer JSON > > format. I'm using the 'Genome' / 'Spectrum' themes found in the theme store. They seem to work fine since I only really use the color palettes from the theme but I'll switch to stock Breeze and report back to you. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 478020] The OSD aka visual feedback popup (e.g. for volume and brightness) does not show
https://bugs.kde.org/show_bug.cgi?id=478020 fanzhuyi...@gmail.com changed: What|Removed |Added Status|NEEDSINFO |REPORTED Resolution|WAITINGFORINFO |--- --- Comment #5 from fanzhuyi...@gmail.com --- I also noticed > Dec 04 19:52:16 the-overcooler plasmashell[13130]: kde.plasmashell: Aborting > shell load: The activity manager daemon (kactivitymanagerd) is not running. which doesn't seem good. How did you install plasma 6 beta 1? From the kde-unstable repo? You also need to enable the testing repos if you do that. What theme are you using? Could you try using the default themes (breeze)? I noticed this in the log: > Dec 04 19:52:17 the-overcooler plasmashell[13130]: kf.svg: The theme > "spectrum-classic-basic" uses the legacy metadata.desktop. Consider > contacting the author and asking them update it to use the newer JSON format. > I notice kunifiedpush-di segfaulting in that log. I assume this is a > different issue and thus should be reported separately as that's related to > push notifications and not the OSD? I do not know much about how KDE is > structured - but that should be handled over dbus, no? Yeah I think that should be a separate issue. It might also be a downstream packaging issue. -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 478087] Poor ranking of search results
https://bugs.kde.org/show_bug.cgi?id=478087 Patrick Silva changed: What|Removed |Added CC||bugsefor...@gmx.com -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 474945] Single clicking the top of the chromium window while it is left or right snapped causes it to jump to the middle of the screen
https://bugs.kde.org/show_bug.cgi?id=474945 --- Comment #9 from pmqui...@proton.me --- And as for evidence of lack of traction, I have bumped the chromium issue twice a month since October. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 474945] Single clicking the top of the chromium window while it is left or right snapped causes it to jump to the middle of the screen
https://bugs.kde.org/show_bug.cgi?id=474945 --- Comment #8 from pmqui...@proton.me --- Unfortunately, the issue is getting zero traction even for triage on the chromium side. I'd speculate that this may be due to the fact that this only affects KDE plasma, and so chromium developers using GNOME would need to switch to repro. I understand that this is a chromium issue, but this only affects KDE Plasma users. As a result, it's a significant user experience impact for any plasma users who are using any chromium based browser, be it chrome, chromium, brave, vivaldi, etc. I imagine that's a significant chunk of plasma users. Given that there's no traction on the chromium side, I'm bumping this issue to ask about whether it falls within KDE policies to at least do the initial triage for this issue. This issue impacts a tiny fraction of all chromium users, but a significant portion of KDE users are impacted. So even though the responsibility for triage falls on chromium, as a practical matter that simply is not happening, so it may behoove KDE to do the initial triage here. -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 478042] very slow loading time on first launch
https://bugs.kde.org/show_bug.cgi?id=478042 --- Comment #4 from Henning --- Created attachment 163883 --> https://bugs.kde.org/attachment.cgi?id=163883=edit A first launch and a second launch of krunner maybe the second launch is not recorded, as the first launch came through perf, the second one through the keyboard shortcut. -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 478042] very slow loading time on first launch
https://bugs.kde.org/show_bug.cgi?id=478042 --- Comment #3 from Henning --- Created attachment 163882 --> https://bugs.kde.org/attachment.cgi?id=163882=edit a single first launch of krunner recorded with hotspot and perf -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 474982] Battery applet no longer tells why the power management is inhibited
https://bugs.kde.org/show_bug.cgi?id=474982 Natalie Clarius changed: What|Removed |Added Status|REOPENED|ASSIGNED --- Comment #15 from Natalie Clarius --- Now it shows the inhibition after setting the manual inhibition switch to off again, but it still incorrectly turns the manual inhibition switch on the first time. (In reply to Jin Liu from comment #14) > The current implementation doesn't make sense at all... > > The manual switch is bound to the data engine "PowerManagement" "Has > Inhibition": > https://github.com/KDE/plasma-workspace/blob/ > e254bf301a560b9d6d70968ac43a587edab7fe19/applets/batterymonitor/package/ > contents/ui/PowerManagementItem.qml#L41 > > Which bounds to org.freedesktop.PowerManagement.Inhibit.HasInhibitChanged: > https://github.com/KDE/plasma-workspace/blob/ > de5a5dbf63c5d1fb91c1cf3a3f45553b9cca417b/dataengines/powermanagement/ > powermanagementengine.cpp#L219 > > The problem is the FDO service returns HasInhibit=true for *any* inhibitors. > So this code would treat any inhibitor as manually enabled in the applet. > > The correct implementation would be that Powerdevil manages a special "KDE > manual inhibitor" whose state can be queried individually. > > BTW, I don't see why the applet hides inhibitors when the manual switch is > on. That's correct, my mentioned drafted fix addresses this, will test again. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 478088] New: The Compare Effect feature at the Effect/Composition Stack widget is not working
https://bugs.kde.org/show_bug.cgi?id=478088 Bug ID: 478088 Summary: The Compare Effect feature at the Effect/Composition Stack widget is not working Classification: Applications Product: kdenlive Version: 23.08.3 Platform: Flatpak OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: User Interface Assignee: j...@kdenlive.org Reporter: epad...@duck.com Target Milestone: --- Created attachment 163881 --> https://bugs.kde.org/attachment.cgi?id=163881=edit The error message that appears at the bottom of the Project Monitor widget SUMMARY The Compare Effect feature at the Effect/Composition Stack widget is not working STEPS TO REPRODUCE 1. Click on the "Compare Effect" button at the Effect/Composition Stack widget OBSERVED RESULT Nothing but an error message appears at the bottom of the Project Monitor saying "The alphagrad filter is required for that feature, please install frei0r and restart Kdenlive" (see attachment) EXPECTED RESULT Splits the Preview Monitor vertically to do a side-by-side comparison of the clip with and without effects SOFTWARE/OS VERSIONS Distro: Debian /GNU/Linux 12 KDE Plasma Version: 5.27.5 KDE Frameworks Version: 5.103.0 Qt Version: 5.15.8 ADDITIONAL INFORMATION ❯ flatpak remote-info --log flathub org.kde.kdenlive | head -n 14 ID: org.kde.kdenlive Ref: app/org.kde.kdenlive/x86_64/stable Arch: x86_64 Branch: stable Collection: org.flathub.Stable Download: 86.6 MB Installed: 262.8 MB Runtime: org.kde.Platform/x86_64/5.15-22.08 Sdk: org.kde.Sdk/x86_64/5.15-22.08 Commit: 3cc2af182c892a1df0909ff97f76c9946b351f3d120a97b0a031277124e3cfac Parent: f86f66b743bc3137d81f8d9aae3045e57b78a595a16de5b0185012c47c371dfd Subject: Remove jack2, pw-jack is in the runtime (d7faa8b5) Date: 2023-12-03 22:35:45 + -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 478042] very slow loading time on first launch
https://bugs.kde.org/show_bug.cgi?id=478042 --- Comment #2 from Henning --- Hm, not sure if this is that important. Krunner loads normally fast but only after it loaded once. I disabled some 3rd party plugins and the result is exactly the same. I will use perf to maybe get some more info, but it really seems like some background loading would be best -- You are receiving this mail because: You are watching all bug changes.
[kphotoalbum] [Bug 474317] Make default annotation mode configurable
https://bugs.kde.org/show_bug.cgi?id=474317 --- Comment #3 from r...@alum.mit.edu --- Second here -- assigning tokens is extremely useful in the viewer (to me, at any rate), and I'm not interested in annotating through the viewer. Being able to set this once would make life easier. -- You are receiving this mail because: You are watching all bug changes.
[kphotoalbum] [Bug 474317] Make default annotation mode configurable
https://bugs.kde.org/show_bug.cgi?id=474317 r...@alum.mit.edu changed: What|Removed |Added CC||r...@alum.mit.edu -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 475937] Unable to print in landscape mode
https://bugs.kde.org/show_bug.cgi?id=475937 --- Comment #3 from João Vidal da Silva --- I updated Gwenview to 23.08.3-2 but the problem remains. But it's interesting to notice that, although Okular prints PDFs correctly, it prints images incorrectly just like Gwenview. -- You are receiving this mail because: You are watching all bug changes.
[kdiff3] [Bug 475176] crash from std::bad_alloc when comparing folders with a huge file and "Full Analysis" File Comparison Mode
https://bugs.kde.org/show_bug.cgi?id=475176 michael changed: What|Removed |Added Latest Commit|https://invent.kde.org/sdk/ |https://invent.kde.org/sdk/ |kdiff3/-/commit/eedcc1a6ee0 |kdiff3/-/commit/2f69679e0bc |2aa39bba7c2882563c95ebd48bf |1f67d4647244085c5b0aa10d1a1 |7c |6a --- Comment #2 from michael --- Git commit 2f69679e0bc1f67d4647244085c5b0aa10d1a16a by Michael Reeves. Committed on 05/12/2023 at 02:23. Pushed by mreeves into branch '1.10'. Correctly handle oversized files *Catch std::bad_alloc during file load attempt. *reset the FileData object if we can't complete the load FIXED-IN:1.10.7 M +61 -52 src/SourceData.cpp https://invent.kde.org/sdk/kdiff3/-/commit/2f69679e0bc1f67d4647244085c5b0aa10d1a16a -- You are receiving this mail because: You are watching all bug changes.
[kdiff3] [Bug 475176] crash from std::bad_alloc when comparing folders with a huge file and "Full Analysis" File Comparison Mode
https://bugs.kde.org/show_bug.cgi?id=475176 michael changed: What|Removed |Added Status|REPORTED|RESOLVED Version Fixed In||1.10.7 Latest Commit||https://invent.kde.org/sdk/ ||kdiff3/-/commit/eedcc1a6ee0 ||2aa39bba7c2882563c95ebd48bf ||7c Resolution|--- |FIXED --- Comment #1 from michael --- Git commit eedcc1a6ee02aa39bba7c2882563c95ebd48bf7c by Michael Reeves. Committed on 05/12/2023 at 02:24. Pushed by mreeves into branch 'master'. Correctly handle oversized files *Catch std::bad_alloc during file load attempt. *reset the FileData object if we can't complete the load FIXED-IN:1.10.7 M +178 -156 src/SourceData.cpp M +11 -2src/pdiff.cpp https://invent.kde.org/sdk/kdiff3/-/commit/eedcc1a6ee02aa39bba7c2882563c95ebd48bf7c -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 478063] Dual screen preview missing
https://bugs.kde.org/show_bug.cgi?id=478063 --- Comment #2 from Alexander --- I'm going to add that this is a new install (yesterday) and it's using breeze dark as the theme. Fully updated. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 477762] Application launcher stop opening when clicked while using an NVIDIA GPU
https://bugs.kde.org/show_bug.cgi?id=477762 --- Comment #13 from SR_team --- (In reply to SR_team from comment #12) > (In reply to Nate Graham from comment #11) > > Cannot reproduce on Plasma 6 either. But it's not a Plasma or a KWin issue; > > the issue is with your icon theme as some files seem to be missing. > > > Thanks, you right. I checked plasma styles and some files from `libplasma` > package are missing - reinstall package resolved this. > > P.S. Package do not changed in repos, maybe it's problem with FS of my drive I reinstalled all system packages and bug reproduced for me. I use PC and Nvidia is main GPU without iGPU -- You are receiving this mail because: You are watching all bug changes.
[krusader] [Bug 464382] "Start terminal here" (F9) opens local location when switched to panel with SFTP remote connection
https://bugs.kde.org/show_bug.cgi?id=464382 Pedro V changed: What|Removed |Added CC||voidpointertonull+bugskdeor ||g...@gmail.com --- Comment #1 from Pedro V --- Can't confirm random location being opened, I reliably get a terminal defaulting to my home directory. Either the random part was fixed or was never really random. However the expected result is likely simply isn't implemented. It isn't unreasonable though, but it's a wishlist matter, not a bug report. -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 472456] Laptop wakes up from screen saving mode in full brightness
https://bugs.kde.org/show_bug.cgi?id=472456 Natalie Clarius changed: What|Removed |Added Status|CONFIRMED |NEEDSINFO Resolution|--- |WAITINGFORINFO --- Comment #8 from Natalie Clarius --- (In reply to Marián Konček from comment #2) > My argument is that for some (most ?) Linux laptops, having brightness at 0 > % means that the screen is more-less completely black. Waking up the screen > from screen saving mode could not be visible to the user. As Nate wrote, having the brightness at 0% completely black through brightness keys will no longer be a thing in Plasma 6, so is there any remaining case where the current behavior would be an issue? -- You are receiving this mail because: You are watching all bug changes.
[krusader] [Bug 464672] Can't launch Krusader from Discover
https://bugs.kde.org/show_bug.cgi?id=464672 Pedro V changed: What|Removed |Added CC||voidpointertonull+bugskdeor ||g...@gmail.com --- Comment #2 from Pedro V --- Tried to reproduce, Krusader doesn't even show up in Discover, so I can't even try. Operating System: Kubuntu 23.10 KDE Plasma Version: 5.27.8 KDE Frameworks Version: 5.110.0 Qt Version: 5.15.10 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 472663] Wayland compositor performance affects mouse cursor
https://bugs.kde.org/show_bug.cgi?id=472663 --- Comment #13 from Rean --- Never mind about the micro freezes I mentioned before. After a few days of testing, the micro freezes seem to happen whether I have the readability checks enabled or disabled. Enabling readability checks doesn't make the micro freezes any worse or better, but it makes the mouse lag under heavy loads go away, so I'll leave it enabled since it's not what's causing the freezes; something else is. -- You are receiving this mail because: You are watching all bug changes.
[krusader] [Bug 474757] Double "Compress"/"Extract" menu entries in context menu.
https://bugs.kde.org/show_bug.cgi?id=474757 Pedro V changed: What|Removed |Added Ever confirmed|0 |1 Status|REPORTED|CONFIRMED CC||voidpointertonull+bugskdeor ||g...@gmail.com --- Comment #6 from Pedro V --- Oh, so it's not just me, I thought I messed up my context menu with the addition of some custom options. Mine only differs with the 2 compress options sandwiching some additional elements like my custom additions, KDE Connect, and some others. Operating System: Kubuntu 23.10 KDE Plasma Version: 5.27.8 KDE Frameworks Version: 5.110.0 Qt Version: 5.15.10 -- You are receiving this mail because: You are watching all bug changes.
[krusader] [Bug 476138] Krusader crashes when system left idle
https://bugs.kde.org/show_bug.cgi?id=476138 Pedro V changed: What|Removed |Added CC||voidpointertonull+bugskdeor ||g...@gmail.com --- Comment #1 from Pedro V --- Suspecting this to be similar to Bug 476289 with the difference of this one being on X11 while that one being on Wayland, so the events are different. It also doesn't look Krusader specific either. Did anything else crash at the same time? Guess you have a DisplayPort monitor connection which may disconnect during power saving, resulting in everything getting moved from that monitor. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 478020] The OSD aka visual feedback popup (e.g. for volume and brightness) does not show
https://bugs.kde.org/show_bug.cgi?id=478020 --- Comment #4 from jvy...@jvyden.xyz --- I notice kunifiedpush-di segfaulting in that log. I assume this is a different issue and thus should be reported separately as that's related to push notifications and not the OSD? I do not know much about how KDE is structured - but that should be handled over dbus, no? -- You are receiving this mail because: You are watching all bug changes.
