[kwin] [Bug 466186] Closing VLC when a video is playing causes kwin assert error crash/restart
https://bugs.kde.org/show_bug.cgi?id=466186 Mathias Tillman changed: What|Removed |Added Summary|Closing VLC when a video is |Closing VLC when a video is |playing causes kwin wayland |playing causes kwin assert |assert error crash/restart |error crash/restart -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 196335] valgrind: m_libcfile.c:73 (vgPlain_safe_fd): Assertion 'newfd >= VG_(fd_hard_limit)' failed.
https://bugs.kde.org/show_bug.cgi?id=196335 --- Comment #11 from Paul Floyd --- (not to mention that a bug that was for Darwin 9.7 is probably not the same thing as Linux Docker). -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 465435] m_libcfile.c:66 (vgPlain_safe_fd): Assertion 'newfd >= VG_(fd_hard_limit)' failed.
https://bugs.kde.org/show_bug.cgi?id=465435 Paul Floyd changed: What|Removed |Added CC||agilesoftw...@gmail.com --- Comment #13 from Paul Floyd --- *** Bug 196335 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 196335] valgrind: m_libcfile.c:73 (vgPlain_safe_fd): Assertion 'newfd >= VG_(fd_hard_limit)' failed.
https://bugs.kde.org/show_bug.cgi?id=196335 Paul Floyd changed: What|Removed |Added Resolution|--- |DUPLICATE Status|REOPENED|RESOLVED CC||pjfl...@wanadoo.fr --- Comment #10 from Paul Floyd --- Closing this as a duplicate of 465435. See the analysis there. IMO this is a Docker bug. It lies when it tells us what the file descriptor rlimit is. Then when we try to move one of our internal fds out of the way at the top of this range the fcntl dupfd fails. *** This bug has been marked as a duplicate of bug 465435 *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 465966] 1 Pixel Line on top of the Panel during fade in/fade out transitions
https://bugs.kde.org/show_bug.cgi?id=465966 --- Comment #3 from LUBE --- (In reply to Nate Graham from comment #2) > Are you using the Wayland session with a scale factor that's not 100%, 200%, > or 300%? I have a Laptop with a scaling factor of 125%, but this problem also exists on my Main PC where the scaling factor is in fact 100%. That's where i made the screenshot from. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 466200] Region artifacts that follow mouse ghosting when all windows set to semi-transparent on Wayland with multi-monitor setup
https://bugs.kde.org/show_bug.cgi?id=466200 --- Comment #2 from Pasha --- (In reply to Nate Graham from comment #1) > Bug 455526? Mouse behavior is the same as in the bug, that you've provided. And it was the same for me prior to 5.27 update. 5.27 brought the bug that you can see in the youtube video in the bottom of my bug report (should I move it to the attachments?) and it is not displayed in the 455526 report. -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 465688] "Fit" on scaled wayland display doesn't fit
https://bugs.kde.org/show_bug.cgi?id=465688 --- Comment #3 from Sven Brauch --- By the way, on my screen on Wayland, 125% wouldn't fit either. I need to set ~160%, which I can't make sense of. The only calculation I can come up with which gives 1.6 would be 1.2 * 1/0.75, but it requires some pretty mixed up maths to get to that starting from "125% scaling". It's plausible though if somebody thought subtracting 1 from the devicePixelRatio and then doing some multiplications was the thing to do. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 465158] Line glitches with 125% and 150% scale on Wayland with either Both Blur or Background Contrast effects turned on
https://bugs.kde.org/show_bug.cgi?id=465158 --- Comment #21 from Mathias Tillman --- See https://invent.kde.org/plasma/kwin/-/merge_requests/3236 for a discussion about a potential fix for this issue. It does work for me, but there are some uncertainties about how to best approach it. -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 465688] "Fit" on scaled wayland display doesn't fit
https://bugs.kde.org/show_bug.cgi?id=465688 --- Comment #2 from Sven Brauch --- Hi, QWidget has a devicePixelRatioF which contains this 1.25 IIRC: https://doc.qt.io/qt-6/qpaintdevice.html#devicePixelRatioF -- I think that's what you need? -- You are receiving this mail because: You are watching all bug changes.
[Plasma Vault] [Bug 442854] Option to automatically delete the folder where the vault is mounted when unmounting
https://bugs.kde.org/show_bug.cgi?id=442854 SC changed: What|Removed |Added CC||k...@scheimong.net -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 466095] Plasma crashes in DesktopView::screenToFollow() on screen wake up
https://bugs.kde.org/show_bug.cgi?id=466095 --- Comment #3 from krzys...@cybulski.info --- If I disable KScreen2 in KDE services, crash is not happening, but I need to set my screens every time start my computer. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kservice] [Bug 442721] kf.service.services: KApplicationTrader: mimeType "x-scheme-handler/file" not found
https://bugs.kde.org/show_bug.cgi?id=442721 austin0...@outlook.com changed: What|Removed |Added CC||austin0...@outlook.com -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 439961] kdirmodel not finding node for removed items when dialogs using kmozillahelper for Firefox are called
https://bugs.kde.org/show_bug.cgi?id=439961
kdeb...@toeai.com changed:
What|Removed |Added
CC||kdeb...@toeai.com
--- Comment #1 from kdeb...@toeai.com ---
Created attachment 156588
--> https://bugs.kde.org/attachment.cgi?id=156588=edit
reproducible test case
I also see this error using Frescobaldi (based on PyQt5) almost every time an
open or save dialog is launched.
I've reduced the problem to a tiny reproducible test case. Simply run the
attached .py file according to the instructions at the top of the file, and the
error message will appear, i.e.
kf.kio.widgets.kdirmodel: No node found for item that was just removed:
QUrl("file:///home/user/path-to/subdir/not-a-cool-file.txt")
Operating System: Kubuntu 22.10
KDE Plasma Version: 5.25.5
KDE Frameworks Version: 5.98.0
Qt Version: 5.15.6
--
You are receiving this mail because:
You are watching all bug changes.
[plasmashell] [Bug 409190] Have kded or plasmashell handle media-related keyboard shortcuts so they don't stop working when all Audio Volume applet/widget instances are removed or when more than one i
https://bugs.kde.org/show_bug.cgi?id=409190 sevens changed: What|Removed |Added CC||pe...@opzninges.nl -- You are receiving this mail because: You are watching all bug changes.
[kpat] [Bug 466229] Spider segfaulting, new solver (417bdc2ec) bug?
https://bugs.kde.org/show_bug.cgi?id=466229 --- Comment #2 from Stephan Kulow --- Hi, can you export KDE_DEBUG=1 before starting it from console? Then something useful should appear in coredumpctl (typing from memory as I'm not having a computer around). -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 466096] New windows tile features indirectly modifies the geometry of the window
https://bugs.kde.org/show_bug.cgi?id=466096 --- Comment #1 from antonio --- The correct steps to reproduce the problem are the following: STEPS TO REPRODUCE 1. Insert an application that has associated the rule of remembering the size of the window in the tile 2. Open another instance of the same application (the size of the second instance window has changed) 3. Remove the application from the tile (the size of the first instance window is correctly restored) 4. Close the first instance 5. Close the second instance 6. Reopen the same application In practice, the rule to remember the dimension of the window should not be applied when this is inside a tile -- You are receiving this mail because: You are watching all bug changes.
[krdc] [Bug 383299] KRDC Crashes when closing from system tray
https://bugs.kde.org/show_bug.cgi?id=383299 --- Comment #3 from krzys...@cybulski.info --- Created attachment 156587 --> https://bugs.kde.org/attachment.cgi?id=156587=edit New crash information added by DrKonqi krdc (22.12.2) using Qt 5.15.8 The problem persists in Plasma 5.27 and QT 5.15.8 -- Backtrace (Reduced): #4 QWindow::parent (this=0x0) at kernel/qwindow.cpp:702 #5 0x7f8f3dfcd61c in QWindowContainer::parentWasMoved (parent=0x55d04afa58d0) at kernel/qwindowcontainer.cpp:418 #6 0x7f8f3dfcd0a8 in qwindowcontainer_traverse (parent=, callback=0x7f8f3dfcd5d0 ) at kernel/qwindowcontainer.cpp:381 #7 0x7f8f3dfcd0a8 in qwindowcontainer_traverse (parent=, callback=0x7f8f3dfcd5d0 ) at kernel/qwindowcontainer.cpp:381 #8 0x7f8f3dfcd0a8 in qwindowcontainer_traverse (parent=, callback=0x7f8f3dfcd5d0 ) at kernel/qwindowcontainer.cpp:381 -- You are receiving this mail because: You are watching all bug changes.
[krdc] [Bug 383299] KRDC Crashes when closing from system tray
https://bugs.kde.org/show_bug.cgi?id=383299 krzys...@cybulski.info changed: What|Removed |Added CC||krzys...@cybulski.info -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 466079] Plugging in a monitor sometimes results in the UI being wonky
https://bugs.kde.org/show_bug.cgi?id=466079 --- Comment #3 from Tarballwalf --- Correct. Along with the panels not getting properly sized, it's hard to replicate. The panel itself remains at the same old resolution (in terms of witdh), and the components shift to the right side without the panel itself extending its blur effect -- You are receiving this mail because: You are watching all bug changes.
[kpat] [Bug 466229] Spider segfaulting, new solver (417bdc2ec) bug?
https://bugs.kde.org/show_bug.cgi?id=466229 --- Comment #1 from Duncan <1i5t5.dun...@cox.net> --- Bisecting confirms it's the new solver. 417bdc2ec (the new solver) bad. 3c581787e (the commit previous to that) seems to be fine. (Well, at least it played a full round without segfaulting, tho as I mentioned above that did happen -- once -- with the bad code, too.) -- You are receiving this mail because: You are watching all bug changes.
[kdeplasma-addons] [Bug 466230] New: The eyedropper in the colorpicker widget does not work
https://bugs.kde.org/show_bug.cgi?id=466230 Bug ID: 466230 Summary: The eyedropper in the colorpicker widget does not work Classification: Plasma Product: kdeplasma-addons Version: 5.27.1 Platform: Archlinux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Color Picker Assignee: plasma-b...@kde.org Reporter: grey...@gmail.com CC: k...@privat.broulik.de Target Milestone: --- Created attachment 156586 --> https://bugs.kde.org/attachment.cgi?id=156586=edit video showing the problem The eyedropper in the colorpicker widget does not work all other widget functions work, only the eyedropper does not work video attached.. -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 413947] Windows Client stops working correctly when it receives a notification from the phone
https://bugs.kde.org/show_bug.cgi?id=413947 uk_man...@yahoo.com changed: What|Removed |Added CC||uk_man...@yahoo.com --- Comment #7 from uk_man...@yahoo.com --- (In reply to brute4s99 from comment #6) > are there any issues left regarding this bug? I am experiencing the same issue with the version that is available from Microsoft Score. I tried the latest build but found it unusable as the controls in the user interface were totally misaligned and text missing some characters. The strange thing is that on 3 other machines, there are no such issues. It's only on 1 of my machines. All machines are fully updated and are running latest VC++ runtimes. -- You are receiving this mail because: You are watching all bug changes.
[kpat] [Bug 466229] New: Spider segfaulting, new solver (417bdc2ec) bug?
https://bugs.kde.org/show_bug.cgi?id=466229 Bug ID: 466229 Summary: Spider segfaulting, new solver (417bdc2ec) bug? Classification: Applications Product: kpat Version: unspecified Platform: Gentoo Packages OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: solver Assignee: co...@kde.org Reporter: 1i5t5.dun...@cox.net CC: kde-games-b...@kde.org Target Milestone: --- Live-git version updated yesterday (Feb 20, 2023), using the gentoo/kde project overlay's live-git packages, reported as 23.03.70 (both unlisted so I can't set that version above), with live-git frameworks-5 as well. Qt is 5.15.8 (current as of yesterday with gentoo's regular sub-version update patchsets) . Spider has started segfaulting on me recently (the other kpat games I play regularly, klondike and freecell, are fine), with several weeks of further updates not fixing it yet. The timing and spider-specificness suggest it's due to a race or nul-deref in the new solver, tho I'm filing this with the info I have before bisecting to confirm that. Maybe happenstance, but at first it /seemed/ to happen nearly immediately after starting a spider round, often on (before ?) the first move, but something (maybe just another rebuild, or an update of libkdegames, some framework, or qt5, as I see no further kpat code changes gitlogged, only l10n/appstream) seems to have decreased the frequency of the issue since and I can often get in a number of moves now before the segfault. Once I was even able to finish a round and I hoped for a moment the problem was fixed, but it segfaulted on the second round. The output when started from konsole is unhelpful; an initial complaint from QFont::setPixelSize that appears unrelated as it happens well before the segfault, then nothing as I play until the segfault: QFont::setPixelSize: Pixel size <= 0 (0) Segmentation fault For reference here's the suspect commit (email addresses despammed for posting): * commit 417bdc2ec | Author: Stephan Kulow | AuthorDate: Fri Jan 20 10:51:07 2023 +0100 | Commit: Albert Astals Cid | CommitDate: Sun Jan 22 22:33:51 2023 + | | Replace spider solver with a self serving solution | | This is something I had lying around (don't ask). It's generally | slower (as it tries harder to find an optimal solution), but finds | solutions more reliably - and is possibly easier to debug for | other people :) -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 465995] Flashing white line under KRunner
https://bugs.kde.org/show_bug.cgi?id=465995 --- Comment #5 from Jin Liu --- (In reply to Nate Graham from comment #4) > Ah then it must be Bug 465158. These bugs all seem to be one or the other; > they're quite similar. > > *** This bug has been marked as a duplicate of bug 465158 *** I upgraded to 5.27.1 and turned off both Blur and Background Contrast, as in bug 465158, then the problem disappeared. So I think you are right. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 466198] Touchpad shows up as a mouse in the Mouse KCM
https://bugs.kde.org/show_bug.cgi?id=466198 --- Comment #4 from tsengal...@gmail.com --- (In reply to Nate Graham from comment #3) > (In reply to tsengalb99 from comment #2) > > Is there any way to make my touchpad scroll the cursor in Konsole faster > > without making the actual scroll speed for other things faster? If I > > make the scroll speed for normal things a normal speed, then the Konsole > > cursor scrolls too slowly. > No, sorry. If you find that the scroll speed in Konsole is inconsistent with > the scroll speed in your other apps, I would recommend submitting a bug > report for Konsole about it. > > Also please try to avoid replying to the email, as it tends to produce huge > comments with messed up formatting. I don't think this is a Konsole issue. Searching around indicates GTK and Wayland apps have different scroll speeds, eg https://gitlab.gnome.org/GNOME/gtk/-/issues/363. I am noticing Okular scrolls slower than Chrome too. Is this something that can be fixed on Plasma's side? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 465158] Line glitches with 125% and 150% scale on Wayland with either Both Blur or Background Contrast effects turned on
https://bugs.kde.org/show_bug.cgi?id=465158 Nate Graham changed: What|Removed |Added CC||ad.liu@gmail.com --- Comment #20 from Nate Graham --- *** Bug 465995 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 465995] Flashing white line under KRunner
https://bugs.kde.org/show_bug.cgi?id=465995 --- Comment #4 from Nate Graham --- Ah then it must be Bug 465158. These bugs all seem to be one or the other; they're quite similar. *** This bug has been marked as a duplicate of bug 465158 *** -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 466198] Touchpad shows up as a mouse in the Mouse KCM
https://bugs.kde.org/show_bug.cgi?id=466198 --- Comment #3 from Nate Graham --- (In reply to tsengalb99 from comment #2) > Is there any way to make my touchpad scroll the cursor in Konsole faster > without making the actual scroll speed for other things faster? If I > make the scroll speed for normal things a normal speed, then the Konsole > cursor scrolls too slowly. No, sorry. If you find that the scroll speed in Konsole is inconsistent with the scroll speed in your other apps, I would recommend submitting a bug report for Konsole about it. Also please try to avoid replying to the email, as it tends to produce huge comments with messed up formatting. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 465158] Line glitches with 125% and 150% scale on Wayland with either Both Blur or Background Contrast effects turned on
https://bugs.kde.org/show_bug.cgi?id=465158 thenujan changed: What|Removed |Added Resolution|WAITINGFORINFO |--- Status|NEEDSINFO |REPORTED --- Comment #19 from thenujan --- (In reply to Nate Graham from comment #18) > Reminds me of Bug 464526, which was fixed in Plasma 5.27.1, which was > released today. > > Can you upgrade to Plasma 5.27.1 and see if this is fixed too? Thanks! Yeah tested after updating. Issue still persists. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 466098] Panels now have incorrect minimum height with certain themes that have large corner radius
https://bugs.kde.org/show_bug.cgi?id=466098 --- Comment #2 from earthquake125 --- (In reply to Nate Graham from comment #1) > The global minimum is 20, which hasn't changed. > > For 5.27, we also added code to prevent panel thicknesses that are thin > enough that themes with large rounded corners would produce visual glitches. > However evidently the code is a bit buggy. Are you using Wayland or X11, and > are you using any screen scaling? I ask because on Wayland with 200% scale, > the minimum thickness I see is exactly half the minimum thickness that other > people are seeing, so I wonder if we're inappropriately scaling it or > something. > > If you're on X11, do you have the PLASMA_USE_QT_SCALING=1 environment > variable set? This is on X11. That environment variable is not set. Scaling is at normal 100% on my 2560x1440 display. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 442901] GTK4 apps have double scaling on hidpi
https://bugs.kde.org/show_bug.cgi?id=442901 --- Comment #44 from Steve Vialle --- Additional quick tests: Setting Xft.dpi to 82 in /etc/X11/Xresources -> plasma/QT/GTK all 96DPI. Setting "DPI" "82x82" in /etc/X11/xorg.conf.d/foo.conf -> plasma runs at 96DPI. Setting "Force fonts DPI to 82 in fonts KCM -> plasma runs at 96DPI. _Please_ stop overriding my settings. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 466165] Feature request: Regular expression based project filters
https://bugs.kde.org/show_bug.cgi?id=466165 Igor Kushnir changed: What|Removed |Added CC||igor...@gmail.com --- Comment #1 from Igor Kushnir --- Wouldn't having both syntaxes be confusing? One more column with the syntax choice would have to be added. I suspect the rare regex use case doesn't justify the effort, code and UI complexity increase. Porting to QRegularExpression is welcome. But it is not straightforward, because QRegularExpression::wildcardToRegularExpression() does not match slashes with '*'. See the discussion here: https://invent.kde.org/kdevelop/kdevelop/-/merge_requests/439#note_623331 So we need to deal with this general issue before porting individual wildcard QRegExp uses. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 466198] Touchpad shows up as a mouse in the Mouse KCM
https://bugs.kde.org/show_bug.cgi?id=466198 --- Comment #2 from tsengal...@gmail.com --- Is there any way to make my touchpad scroll the cursor in Konsole faster without making the actual scroll speed for other things faster? If I make the scroll speed for normal things a normal speed, then the Konsole cursor scrolls too slowly. On 2/21/23 17:45, Nate Graham wrote: > https://bugs.kde.org/show_bug.cgi?id=466198 > > Nate Graham changed: > > What|Removed |Added > > Summary|Two scroll speed settings |Touchpad shows up as a > |for my touchpad 5.27|mouse in the Mouse KCM > |Wayland | > Status|REPORTED|CONFIRMED >Component|general |kcm_mouse > Product|kde |systemsettings > Ever confirmed|0 |1 > CC||n...@kde.org > Assignee|unassigned-b...@kde.org |plasma-b...@kde.org > Version|unspecified |5.27.0 > > --- Comment #1 from Nate Graham --- > Can reproduce; my touchpad also randomly gets listed as a mouse on the Mouse > page. > >> Also, I cannot find the setting that controls how many lines the cursor >> scrolls for my touchpad. When I'm scrolling the cursor in terminal emacs, >> the touchpad only scrolls one line at a time. OTOH, one click on the scroll >> wheel of my external mouse scrolls 3 lines, which is the expected behavior. >> How do I make my touchpad scroll 3 lines? > No such setting exists for touchpads because it doesn't make sense; touchpads > let you scroll continuously, not on a "per-click" basis. Any such setting for > how many lines to scroll per step or click would therefore only apply to > scrolling devices that scroll in discrete steps or clicks, like a clicky mouse > wheel. > -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 442901] GTK4 apps have double scaling on hidpi
https://bugs.kde.org/show_bug.cgi?id=442901 Steve Vialle changed: What|Removed |Added Status|RESOLVED|REOPENED Resolution|FIXED |--- --- Comment #43 from Steve Vialle --- Not only is this still not fixed WRT DPI <96, the situation is now _worse_ than it was with 5.27.0. GTK3 and QT/KDE fonts are now the same DPI, so that's something... But that DPI is 96, and _everything_ is huge. It appears "force fonts DPI" is now being ignored altogether, and plasma is setting Xft.dpi to 96 unconditionally. xsettingsd.conf as of 5.27.1: Xft/DPI 98304 Gdk/UnscaledDPI 98304 Again, this is an _82_ DPI display, and that information is both readily available and manually provided in the fonts KCM. 5.27.0: ~ $ xdpyinfo | grep -B2 resolution screen #0: dimensions:1920x1080 pixels (594x334 millimeters) resolution:82x82 dots per inch ~ $ xrdb -query | grep dpi Xft.dpi:82 5.27.1: ~ $ xdpyinfo | grep -B2 resolution screen #0: dimensions:1920x1080 pixels (594x334 millimeters) resolution:82x82 dots per inch ~ $ xrdb -query | grep dpi Xft.dpi:96 No software or config changes on my end besides updating plasma. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 466079] Plugging in a monitor sometimes results in the UI being wonky
https://bugs.kde.org/show_bug.cgi?id=466079 Nate Graham changed: What|Removed |Added CC||aleix...@kde.org, ||n...@kde.org, ||notm...@gmail.com Component|general |Multi-screen support --- Comment #2 from Nate Graham --- So the popup from a widget on one screen's panel sometimes inappropriately appears on the other screen? Do I have that right? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 466126] Issues with panel autohide on specific monitor setup
https://bugs.kde.org/show_bug.cgi?id=466126 Duncan <1i5t5.dun...@cox.net> changed: What|Removed |Added Resolution|--- |DUPLICATE CC||1i5t5.dun...@cox.net Status|REPORTED|RESOLVED --- Comment #2 from Duncan <1i5t5.dun...@cox.net> --- This is almost certainly a duplicate of bug #351175. Marking it as such. However, I'm just another user with another dupe, not a dev, so if you think it's not a dupe, feel free to reverse that and explain the difference. Briefly, the problem is with "internal" borders/edges (aka "struts") between monitors. As long as the panel is on a true edge of the bounding rectangle things are fine, but put it on a strut that's "internal", not on the bounding rectangle edge, and the autohide does the immediate re-popup thing exactly as you describe. Unfortunately fixing this bug doesn't appear to be a priority, despite the number of dupes and thus users obviously affected. Two known workarounds: 1) Change your layout and/or panel position to avoid placing panels on such "internal" struts. (This one's obvious once the problem is understood. For me, it was the excuse I needed to upgrade my older FullHD monitor to a second 4K so they'd match sizes and I'd have no need to place a panel on the previously partial seam between them.) 2) It has been reported that separating the monitors in the kscreen layout so they don't logically touch eliminates the issue as it fools the logic into thinking all the edges are external, while still allowing the pointer to move between screens (which I thought would be broken, but apparently not). IMO that's quite clever and I really wish I had thought to try it before throwing money at the problem (but of course that would have done away with my excuse to upgrade =:^) *** This bug has been marked as a duplicate of bug 351175 *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 351175] Panel on screen edge between two monitors does not auto hide
https://bugs.kde.org/show_bug.cgi?id=351175 Duncan <1i5t5.dun...@cox.net> changed: What|Removed |Added CC||fre...@bananateam.nl --- Comment #49 from Duncan <1i5t5.dun...@cox.net> --- *** Bug 466126 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 466078] Screen configuration is ignored and causes weird behaviour of windows
https://bugs.kde.org/show_bug.cgi?id=466078 Nate Graham changed: What|Removed |Added CC||n...@kde.org Product|KScreen |kwin Assignee|kscreen-bugs-n...@kde.org |kwin-bugs-n...@kde.org Component|common |multi-screen --- Comment #5 from Nate Graham --- Window positioning is done by KWin; moving the bug there. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 466116] Discover crashes after clicking on installed applications...
https://bugs.kde.org/show_bug.cgi?id=466116 Nate Graham changed: What|Removed |Added CC||n...@kde.org Status|REPORTED|NEEDSINFO Resolution|--- |BACKTRACE --- Comment #1 from Nate Graham --- Thank you for the bug report! Unfortunately I can't reproduce it myself and the backtrace is incomplete and missing debug symbols for the following lines that we need to figure out exactly what's going wrong: > #4 0x7f49743eefae in () at > /usr/lib/x86_64-linux-gnu/qt5/plugins/discover/flatpak-backend.so > #5 0x7f49743ff76b in () at > /usr/lib/x86_64-linux-gnu/qt5/plugins/discover/flatpak-backend.so Could you please install debug symbols for Discover's Flatpak backend, reproduce the crash, and attach a new symbolicated backtrace? See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports Thanks again! -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 466048] [Regression] Bismuth tiling manager does not detect windows on Wayland
https://bugs.kde.org/show_bug.cgi?id=466048 Nate Graham changed: What|Removed |Added Resolution|--- |DOWNSTREAM Status|REPORTED|RESOLVED CC||n...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 466111] unable to close Icons only Task Manager
https://bugs.kde.org/show_bug.cgi?id=466111 Nate Graham changed: What|Removed |Added CC||n...@kde.org Version|master |unspecified Product|plasmashell |lattedock Target Milestone|1.0 |--- Component|Task Manager and Icons-Only |plasmoid |Task Manager| Assignee|plasma-b...@kde.org |mvourla...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 466096] New windows tile features indirectly modifies the geometry of the window
https://bugs.kde.org/show_bug.cgi?id=466096 Nate Graham changed: What|Removed |Added Product|plasmashell |kwin CC||n...@kde.org Component|Desktop Containment |Custom Tiling Assignee|plasma-b...@kde.org |kwin-bugs-n...@kde.org Target Milestone|1.0 |--- -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 465986] Crash in QSGBatchRenderer::Renderer::buildRenderLists() on task bar thumbnail
https://bugs.kde.org/show_bug.cgi?id=465986 Nate Graham changed: What|Removed |Added Summary|Crash on task bar thumbnail |Crash in ||QSGBatchRenderer::Renderer: ||:buildRenderLists() on task ||bar thumbnail CC||n...@kde.org --- Comment #2 from Nate Graham --- Not quite the same as Bug 446874: [KCrash Handler] #4 0x7f3c425acf35 in QSGBatchRenderer::Renderer::buildRenderLists(QSGNode*) () at /usr/lib/libQt5Quick.so.5 #5 0x7f3c425acf5c in QSGBatchRenderer::Renderer::buildRenderLists(QSGNode*) () at /usr/lib/libQt5Quick.so.5 #6 0x7f3c425acf5c in QSGBatchRenderer::Renderer::buildRenderLists(QSGNode*) () at /usr/lib/libQt5Quick.so.5 #7 0x7f3c425bea30 in QSGBatchRenderer::Renderer::render() () at /usr/lib/libQt5Quick.so.5 #8 0x7f3c4259fb2f in QSGRenderer::renderScene(QSGBindable const&) () at /usr/lib/libQt5Quick.so.5 #9 0x7f3c42614fa3 in QSGOpenGLLayer::grab() () at /usr/lib/libQt5Quick.so.5 #10 0x7f3c4261569e in QSGOpenGLLayer::updateTexture() () at /usr/lib/libQt5Quick.so.5 #11 0x7f3c427829f7 in QQuickOpenGLShaderEffectMaterial::updateTextures() const () at /usr/lib/libQt5Quick.so.5 #12 0x7f3c425a03da in QSGRenderer::preprocess() () at /usr/lib/libQt5Quick.so.5 #13 0x7f3c4259faf6 in QSGRenderer::renderScene(QSGBindable const&) () at /usr/lib/libQt5Quick.so.5 #14 0x7f3c42614fa3 in QSGOpenGLLayer::grab() () at /usr/lib/libQt5Quick.so.5 #15 0x7f3c4261569e in QSGOpenGLLayer::updateTexture() () at /usr/lib/libQt5Quick.so.5 #16 0x7f3c427829f7 in QQuickOpenGLShaderEffectMaterial::updateTextures() const () at /usr/lib/libQt5Quick.so.5 #17 0x7f3c425a03da in QSGRenderer::preprocess() () at /usr/lib/libQt5Quick.so.5 #18 0x7f3c4259faf6 in QSGRenderer::renderScene(QSGBindable const&) () at /usr/lib/libQt5Quick.so.5 #19 0x7f3c425a0144 in QSGRenderer::renderScene(unsigned int) () at /usr/lib/libQt5Quick.so.5 #20 0x7f3c42602585 in QSGDefaultRenderContext::renderNextFrame(QSGRenderer*, unsigned int) () at /usr/lib/libQt5Quick.so.5 #21 0x7f3c426720d8 in QQuickWindowPrivate::renderSceneGraph(QSize const&, QSize const&) () at /usr/lib/libQt5Quick.so.5 -- You are receiving this mail because: You are watching all bug changes.
[Elisa] [Bug 465411] Playlist doesn't show all tracks: "kf.filemetadata: Unable to open file readonly"
https://bugs.kde.org/show_bug.cgi?id=465411 --- Comment #5 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.
[KDE Itinerary] [Bug 465421] KDE Itinerary Won't Start
https://bugs.kde.org/show_bug.cgi?id=465421 --- Comment #2 from Bug Janitor Service --- Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[plasma-systemmonitor] [Bug 463574] the whole system moniter is black you can not see the words in that.
https://bugs.kde.org/show_bug.cgi?id=463574 Bug Janitor Service changed: What|Removed |Added Resolution|WAITINGFORINFO |WORKSFORME Status|NEEDSINFO |RESOLVED --- 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.
[kwin] [Bug 460932] app windows do not visually update after switching virtual desktops
https://bugs.kde.org/show_bug.cgi?id=460932 Bug Janitor Service changed: What|Removed |Added Resolution|WAITINGFORINFO |WORKSFORME Status|NEEDSINFO |RESOLVED --- Comment #12 from Bug Janitor Service --- This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 446874] Crash in QSGOpaqueTextureMaterialShader::updateState()
https://bugs.kde.org/show_bug.cgi?id=446874 Nate Graham changed: What|Removed |Added CC||wladys...@outlook.com --- Comment #12 from Nate Graham --- *** Bug 464852 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 464852] Closing single window among grouped ones through a thumbnail often crashes whole task bar/panel
https://bugs.kde.org/show_bug.cgi?id=464852 Nate Graham changed: What|Removed |Added Resolution|--- |DUPLICATE CC||n...@kde.org Status|REPORTED|RESOLVED --- Comment #6 from Nate Graham --- *** This bug has been marked as a duplicate of bug 446874 *** -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 465489] Selection Mode still gets triggered by Space, even after reassigning the shortcut
https://bugs.kde.org/show_bug.cgi?id=465489 mydarkstar changed: What|Removed |Added Summary|Can no longer unassign |Selection Mode still gets |"space" from activating |triggered by Space, even |selection mode |after reassigning the ||shortcut -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 465489] Can no longer unassign "space" from activating selection mode
https://bugs.kde.org/show_bug.cgi?id=465489 --- Comment #6 from mydarkstar --- Created attachment 156585 --> https://bugs.kde.org/attachment.cgi?id=156585=edit Video showing the expected behavior, as on v22.12.1 (45s) I have attached a screen recording of Dolphin version 22.12.1, with the reassigned shortcut fully working as expected. In version 22.12.2, the shortcut can still be reassigned, but pressing Space will still trigger it regardless, as seen in my video in the previous comment. This new video first demonstrates: 1. Selection Mode gets triggered by pressing Space (expected behavior) 2. Selection Mode does not get triggered by pressing A (expected behavior) Then, the shortcut for the Selection Mode gets changed from the default (Space) to "A". The screen recording then demonstrates: 3. Selection Mode does not get triggered by pressing Space anymore (expected behavior) 4. Selection Mode now instead gets triggered by pressing A (expected behavior) I feel like Felix' comment on this having to be newly implemented is a misunderstanding. In the previous version, the shortcut reassignment seems to work perfectly fine, and I have not encountered any bugs with it. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 466086] System Settings crash when when clicking the Hardware > Input Devices tab
https://bugs.kde.org/show_bug.cgi?id=466086 Nate Graham changed: What|Removed |Added CC||n...@kde.org Status|REPORTED|NEEDSINFO Resolution|--- |BACKTRACE --- Comment #1 from Nate Graham --- Thank you for the bug report! Unfortunately the backtrace is incomplete and missing debug symbols for the following lines that we need to figure out exactly what's going wrong: > #9 0x7fb320b7dd60 in ?? () from > /usr/lib/qt/plugins/plasma/kcms/systemsettings/kcm_keyboard.so Could you please install debug symbols for plasma, reproduce the crash, and attach a new symbolicated backtrace? See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports Thanks again! -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 459190] Selecting the output monitor does not work for XWayland games with the "Apply Scaling Themselves" setting enabled
https://bugs.kde.org/show_bug.cgi?id=459190 Bug Janitor Service changed: What|Removed |Added Resolution|WAITINGFORINFO |WORKSFORME Status|NEEDSINFO |RESOLVED --- Comment #4 from Bug Janitor Service --- This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[plasma-disks] [Bug 465428] USB disk status detection on plug
https://bugs.kde.org/show_bug.cgi?id=465428 --- Comment #3 from Bug Janitor Service --- Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 465360] Can't get blacks or maximum color with my brush!!!
https://bugs.kde.org/show_bug.cgi?id=465360 --- Comment #2 from Bug Janitor Service --- Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 465329] Pager should not allow dragging windows on a single screen
https://bugs.kde.org/show_bug.cgi?id=465329 --- Comment #2 from Bug Janitor Service --- Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 465076] In Blender, cursor does not change appropriately while dragging the inner window
https://bugs.kde.org/show_bug.cgi?id=465076 --- Comment #3 from Bug Janitor Service --- Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 464419] kwin_x11 crashed without good reason with segmentation fault
https://bugs.kde.org/show_bug.cgi?id=464419 --- Comment #9 from Bug Janitor Service --- Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 466228] New: Black screen when changing from X11 to Wayland or vice-versa
https://bugs.kde.org/show_bug.cgi?id=466228 Bug ID: 466228 Summary: Black screen when changing from X11 to Wayland or vice-versa Classification: Plasma Product: plasmashell Version: 5.27.1 Platform: Manjaro OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Startup process Assignee: plasma-b...@kde.org Reporter: dougjsha...@gmail.com CC: k...@davidedmundson.co.uk Target Milestone: 1.0 SUMMARY *** I tried to change from a Wayland to an X11 session and when logging back into the X11 session, all I got was a black screen. I was able to drop to TTY, reboot and start in X11. I logged out of X11 and changed to Wayland. Got a black screen. Repeated a couple times, it is consistent. *** STEPS TO REPRODUCE 1. login to a plasma session, either X11 or Wayland 2. log out 3. change display server from drop down menu 4. log in to the new session OBSERVED RESULT black screen EXPECTED RESULT plasma desktop starts up SOFTWARE/OS VERSIONS Operating System: Manjaro Linux KDE Plasma Version: 5.27.1 KDE Frameworks Version: 5.103.0 Qt Version: 5.15.8 Kernel Version: 6.2.0-1-MANJARO (64-bit) Graphics Platform: Wayland Processors: 12 × Intel® Core™ i7-9750H CPU @ 2.60GHz Memory: 15.4 GiB of RAM Graphics Processor: AMD Radeon Pro WX 3200 Series Manufacturer: Dell Inc. Product Name: Precision 7540 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 196335] valgrind: m_libcfile.c:73 (vgPlain_safe_fd): Assertion 'newfd >= VG_(fd_hard_limit)' failed.
https://bugs.kde.org/show_bug.cgi?id=196335 Thorsten Glaser changed: What|Removed |Added CC||t.gla...@tarent.de Ever confirmed|0 |1 Status|RESOLVED|REOPENED Resolution|WAITINGFORINFO |--- --- Comment #9 from Thorsten Glaser --- A colleage could reproduce this bug today: I have no name!@9019b147885f:/code$ valgrind --track-origins=yes pytest valgrind: m_libcfile.c:66 (vgPlain_safe_fd): Assertion 'newfd >= VG_(fd_hard_limit)' failed. Segmentation fault (core dumped) This is a Debian bookworm Docker image under Arch Linux; even “valgrind false” fails like this. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 466028] Upgrading to KDE 5.27 resulted in older version of desktop
https://bugs.kde.org/show_bug.cgi?id=466028 Nate Graham changed: What|Removed |Added Component|general |Multi-screen support CC||aleix...@kde.org, ||notm...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 466028] Upgrading to KDE 5.27 resulted in older version of desktop
https://bugs.kde.org/show_bug.cgi?id=466028 Nate Graham changed: What|Removed |Added Resolution|--- |WAITINGFORINFO Status|REPORTED|NEEDSINFO CC||n...@kde.org --- Comment #1 from Nate Graham --- So in Plasma 5.27, we moved to a totally new multi-monitor system, which also entailed changing how monitors are bound to desktops. We added migration code to make it as seamless as possible, but unfortunately, due to how broken the previous system was, it's not possible for the migration code to handle everything perfectly, especially if the previous config data was in a weird or inconsistent state. Evidently in your case the migration code did not do the right thing. Sorry about that. Can you find your missing desktop in the Manage Desktop and Panels window? You access it by entering edit mode on the desktop and clicking on the "Manage Desktop and Panels" button in the toolbar that pops down from the top of the screen. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 465489] Can no longer unassign "space" from activating selection mode
https://bugs.kde.org/show_bug.cgi?id=465489 --- Comment #5 from mydarkstar --- Thank you, Nate. As my bug report has been closed in favor of this one, please do check out the information I documented there on this regression as well! I think the following video I had linked shows the regression very well: https://bugs.kde.org/attachment.cgi?id=156548 > This screen recording first demonstrates: > 1. Selection Mode gets triggered by pressing Space (expected behavior) > 2. Selection Mode does not get triggered by pressing A (expected behavior) > > Then, the shortcut for the Selection Mode gets changed FROM the default TO > "A". > > The screen recording then demonstrates: > 3. Selection mode now gets triggered by pressing A (expected behavior) > 4. Selection mode STILL gets triggered by pressing Space (bug!) I can reproduce that on Dolphin 22.12.1, this still works fully as expected. I hope this information is helpful, as there seems to be a misunderstanding in this report. Reassigning the shortcut was indeed a feature in Dolphin 22.12.0 and 22.12.1, which worked reliably in those versions, but is now buggy in version 22.12.2, unless I'm the one misunderstanding something. Thank you for the hard work on this new feature! Especially now that Linux tablets are getting more popular, I'm sure Selection Mode will be very helpful to many! -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 466227] New: Blur effect with TV Glitch [Burn-My-Windows] effect behaves differently after updating to KDE Plasma 5.27
https://bugs.kde.org/show_bug.cgi?id=466227 Bug ID: 466227 Summary: Blur effect with TV Glitch [Burn-My-Windows] effect behaves differently after updating to KDE Plasma 5.27 Classification: Plasma Product: kwin Version: 5.27.1 Platform: Archlinux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: compositing Assignee: kwin-bugs-n...@kde.org Reporter: c4exp...@gmail.com Target Milestone: --- Created attachment 156584 --> https://bugs.kde.org/attachment.cgi?id=156584=edit Sample video of the bug in action. SUMMARY Prior to updating KDE Plasma to 5.27, when the desktop effect "TV Glitch [Burn-My-Windows]" (downloaded from the KDE Store) animates a window opening, blur effect is not applied until the TV Glitch animation ends. But now, I can see a blur square while TV Glitch is animating. Same with when a window closes, I can now see the blur effect while the TV Glitch effect for closing a window is animating. This effectively puts a square blurred box behind the animation, which was not present before updating. This bug is also present alongside the effects "TV Effect [Burn-My-Windows]" and "Glitch [Burn-My-Windows]". STEPS TO REPRODUCE 1. Open System Settings 2. Go to Workspace Behavior > Desktop Effects 3. Check "Blur" and select "TV Glitch [Burn-My-Windows]" as the Window Open/Close Animation. 4. Open/Close any window to see blur coincide with TV Glitch animation (Which was not the case prior to KDE Plasma 5.27) OBSERVED RESULT - Blur square behind TV Glitch animation when opening or closing a window. EXPECTED RESULT - Blur effect applied after TV Glitch animation ends when opening a window. Blur effect disappears before TV Glitch animation starts when closing a window. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Garuda Linux x86_64 2.6.15-1 KDE Plasma Version: 5.27.1 KDE Frameworks Version: 5.103.0 Qt Version: 5.15.8 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 465973] Display distorts when switching to 5120x1440 resolution
https://bugs.kde.org/show_bug.cgi?id=465973 Nate Graham changed: What|Removed |Added Status|REPORTED|NEEDSINFO Assignee|plasma-b...@kde.org |kwin-bugs-n...@kde.org Product|systemsettings |kwin Resolution|--- |WAITINGFORINFO Component|general |general CC||n...@kde.org --- Comment #2 from Nate Graham --- So to be clear, the system is working fine, then you do something to make System Settings crash, and when it crashes, this also happens? Do I have that right? What specifically is the thing you do to make this happen? -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 466226] New: Kmail crash when modified the configuration account.
https://bugs.kde.org/show_bug.cgi?id=466226 Bug ID: 466226 Summary: Kmail crash when modified the configuration account. Classification: Applications Product: kmail2 Version: unspecified Platform: Fedora RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: luis.quint...@outlook.com Target Milestone: --- Application: kmail (5.22.2 (22.12.2)) Qt Version: 5.15.8 Frameworks Version: 5.103.0 Operating System: Linux 6.1.12-200.fc37.x86_64 x86_64 Windowing System: Wayland Distribution: "Fedora release 37 (Thirty Seven)" DrKonqi: 5.27.0 [KCrashBackend] -- Information about the crash: Kmail crash when modified the configuration account. The reporter is unsure if this crash is reproducible. -- Backtrace: Application: KMail (kmail), signal: Segmentation fault [KCrash Handler] #4 0x7f6913e52783 in QAbstractItemModelPrivate::removePersistentIndexData(QPersistentModelIndexData*) () from /lib64/libQt5Core.so.5 #5 0x7f6913e52bc1 in QPersistentModelIndex::~QPersistentModelIndex() () from /lib64/libQt5Core.so.5 #6 0x7f6914e2ccc0 in QAbstractItemViewPrivate::~QAbstractItemViewPrivate() () from /lib64/libQt5Widgets.so.5 #7 0x7f6914e62f9d in QListViewPrivate::~QListViewPrivate() () from /lib64/libQt5Widgets.so.5 #8 0x7f6914cc2b91 in QComboBoxListView::~QComboBoxListView() () from /lib64/libQt5Widgets.so.5 #9 0x7f6913ec68ba in QObjectPrivate::deleteChildren() () from /lib64/libQt5Core.so.5 #10 0x7f6914bed296 in QWidget::~QWidget() () from /lib64/libQt5Widgets.so.5 #11 0x7f6914cc42c8 in QComboBoxPrivateContainer::~QComboBoxPrivateContainer() () from /lib64/libQt5Widgets.so.5 #12 0x7f6913ec68ba in QObjectPrivate::deleteChildren() () from /lib64/libQt5Core.so.5 #13 0x7f6914bed296 in QWidget::~QWidget() () from /lib64/libQt5Widgets.so.5 #14 0x7f691d349c2e in KMail::KeySelectionCombo::~KeySelectionCombo() () from /lib64/libkmailprivate.so.5 #15 0x7f6913ec68ba in QObjectPrivate::deleteChildren() () from /lib64/libQt5Core.so.5 #16 0x7f6914bed296 in QWidget::~QWidget() () from /lib64/libQt5Widgets.so.5 #17 0x7f6914bed5dd in QWidget::~QWidget() () from /lib64/libQt5Widgets.so.5 #18 0x7f6913ec68ba in QObjectPrivate::deleteChildren() () from /lib64/libQt5Core.so.5 #19 0x7f6914bed296 in QWidget::~QWidget() () from /lib64/libQt5Widgets.so.5 #20 0x7f6914d6a3cd in QStackedWidget::~QStackedWidget() () from /lib64/libQt5Widgets.so.5 #21 0x7f6913ec68ba in QObjectPrivate::deleteChildren() () from /lib64/libQt5Core.so.5 #22 0x7f6914bed296 in QWidget::~QWidget() () from /lib64/libQt5Widgets.so.5 #23 0x7f6914d8db3d in QTabWidget::~QTabWidget() () from /lib64/libQt5Widgets.so.5 #24 0x7f6913ec68ba in QObjectPrivate::deleteChildren() () from /lib64/libQt5Core.so.5 #25 0x7f6914bed296 in QWidget::~QWidget() () from /lib64/libQt5Widgets.so.5 #26 0x7f6914bed5dd in QWidget::~QWidget() () from /lib64/libQt5Widgets.so.5 #27 0x7f6913ec68ba in QObjectPrivate::deleteChildren() () from /lib64/libQt5Core.so.5 #28 0x7f6914bed296 in QWidget::~QWidget() () from /lib64/libQt5Widgets.so.5 #29 0x7f691d35a368 in KMail::IdentityPage::slotModifyIdentity() () from /lib64/libkmailprivate.so.5 #30 0x7f6913ed0e96 in void doActivate(QObject*, int, void**) () from /lib64/libQt5Core.so.5 #31 0x7f6914ca3336 in QAbstractButton::clicked(bool) () from /lib64/libQt5Widgets.so.5 #32 0x7f6914ca35ae in QAbstractButtonPrivate::emitClicked() () from /lib64/libQt5Widgets.so.5 #33 0x7f6914ca51ec in QAbstractButtonPrivate::click() () from /lib64/libQt5Widgets.so.5 #34 0x7f6914ca540b in QAbstractButton::mouseReleaseEvent(QMouseEvent*) () from /lib64/libQt5Widgets.so.5 #35 0x7f6914bf1938 in QWidget::event(QEvent*) () from /lib64/libQt5Widgets.so.5 #36 0x7f6914baed62 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /lib64/libQt5Widgets.so.5 #37 0x7f6914bb73d2 in QApplication::notify(QObject*, QEvent*) () from /lib64/libQt5Widgets.so.5 #38 0x7f6913e9d4e8 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /lib64/libQt5Core.so.5 #39 0x7f6914bb54d2 in QApplicationPrivate::sendMouseEvent(QWidget*, QMouseEvent*, QWidget*, QWidget*, QWidget**, QPointer&, bool, bool) () from /lib64/libQt5Widgets.so.5 #40 0x7f6914c0ac9c in QWidgetWindow::handleMouseEvent(QMouseEvent*) () from /lib64/libQt5Widgets.so.5 #41 0x7f6914c0e060 in QWidgetWindow::event(QEvent*) () from /lib64/libQt5Widgets.so.5 #42 0x7f6914baed62 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /lib64/libQt5Widgets.so.5 #43 0x7f6913e9d4e8 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /lib64/libQt5Core.so.5 #44 0x7f691436ad6d in
[okular] [Bug 466225] New: Okularopen new file in tabs and open containing file not working properly
https://bugs.kde.org/show_bug.cgi?id=466225 Bug ID: 466225 Summary: Okularopen new file in tabs and open containing file not working properly Classification: Applications Product: okular Version: 22.12.2 Platform: Other OS: Microsoft Windows Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: okular-de...@kde.org Reporter: 532032...@qq.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. 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.
[Discover] [Bug 466047] UI: Text, Icons, Install/Remove buttons projecting out of their app's card boxes in Home tab and search results
https://bugs.kde.org/show_bug.cgi?id=466047 Nate Graham changed: What|Removed |Added Resolution|--- |WAITINGFORINFO CC||n...@kde.org Status|REPORTED|NEEDSINFO --- Comment #2 from Nate Graham --- That is really weird. I can't reproduce it myself and I honestly have no idea how it could possibly be happening. Shots in the dark: - What font and font size are you using? - Have you overridden the font DPI setting? What's it currently set to? - Does it reproduce on both X11 and Wayland? -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 466037] sudden shift of unselected elements while the program were on and I was switching on/off some layers
https://bugs.kde.org/show_bug.cgi?id=466037 Nate Graham changed: What|Removed |Added CC||n...@kde.org Component|general |General Product|kde |krita Assignee|unassigned-b...@kde.org |krita-bugs-n...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 460341] On X11 with proprietary NVIDIA GPU drivers, external monitor disabled after reboot or wake-from-sleep
https://bugs.kde.org/show_bug.cgi?id=460341 Nate Graham changed: What|Removed |Added CC||mmarrerole...@gmail.com --- Comment #137 from Nate Graham --- *** Bug 466033 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 466033] Monitor doesn't get signal after wake up
https://bugs.kde.org/show_bug.cgi?id=466033 Nate Graham changed: What|Removed |Added Resolution|--- |DUPLICATE Status|REPORTED|RESOLVED CC||n...@kde.org --- Comment #1 from Nate Graham --- *** This bug has been marked as a duplicate of bug 460341 *** -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 466031] Per-virtual-desktop tiling layouts
https://bugs.kde.org/show_bug.cgi?id=466031 Nate Graham changed: What|Removed |Added Severity|normal |wishlist Ever confirmed|0 |1 Status|REPORTED|CONFIRMED CC||n...@kde.org Summary|Custom tiling is applied|Per-virtual-desktop tiling |across virtual desktops |layouts -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 466022] Discover freezes after clicking on About > Authors > any contact icon from the authors.
https://bugs.kde.org/show_bug.cgi?id=466022 Nate Graham changed: What|Removed |Added Resolution|--- |WAITINGFORINFO Status|REPORTED|NEEDSINFO CC||n...@kde.org --- Comment #1 from Nate Graham --- Cannot reproduce in current git master; no freeze here. Can you get a backtrace of the freeze? To do this you would run Discover under GDB in a terminal window like so: gdb $(which plasma-discover) Then enter 'run'. Then make the hang happen in Discover Then go back to the terminal window, hit Ctrl+Z, and enter 'bt'. Paste the output here. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 466121] Folders panel menu translucency is broken
https://bugs.kde.org/show_bug.cgi?id=466121 Vladimir Yerilov changed: What|Removed |Added Summary|Translucent menu in folders |Folders panel menu |panel is broken |translucency is broken -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 444712] dolphin sometime opens off monitor
https://bugs.kde.org/show_bug.cgi?id=444712 mydarkstar changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |FIXED --- Comment #7 from mydarkstar --- I'm marking this bug as resolved for now. Feel free to reopen or create a new report, should this issue ever occur again! -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 465995] Flashing white line under KRunner
https://bugs.kde.org/show_bug.cgi?id=465995 --- Comment #3 from Jin Liu --- Disabling Background Contrast doesn't fix the problem for me. So perhaps this is a separate issue than https://bugs.kde.org/show_bug.cgi?id=464526. -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 462834] Kate CANNOT display value of registers while debugging OS Kernel via QEMU+GDB
https://bugs.kde.org/show_bug.cgi?id=462834 --- Comment #2 from lucky...@126.com --- (In reply to Christoph Cullmann from comment #1) > Git commit 9e6d7eae088d1815ce60b1facb17e5ec6814b95b by Christoph Cullmann, > on behalf of Héctor Mesa Jiménez. > Committed on 27/01/2023 at 22:09. > Pushed by cullmann into branch 'master'. > > [gdbplugin] show CPU registers for GDB backend. > > This patch adds a new variable scope for CPU registers > in the GDB backend: > > - Unavailable registers are not shown. > - Values are shown using the raw format. > > M +58 -0addons/gdbplugin/debugview.cpp > M +6-0addons/gdbplugin/debugview.h > M +4-1addons/gdbplugin/gdbvariableparser.cpp > M +1-1addons/gdbplugin/gdbvariableparser.h > > https://invent.kde.org/utilities/kate/commit/ > 9e6d7eae088d1815ce60b1facb17e5ec6814b95b It would be better if the display format of local variables and CPU registers can be customized. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 466021] No dedicated settings menu for the tiling layout
https://bugs.kde.org/show_bug.cgi?id=466021 Nate Graham changed: What|Removed |Added Resolution|--- |INTENTIONAL Status|REPORTED|RESOLVED CC||n...@kde.org --- Comment #1 from Nate Graham --- Glad you're enjoying it! I don't think we aspire to offer a settings page specifically for this feature, though. We'll see where it grows over time. Feel free to submit new bug reports for specific individual feature requests. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 464526] Flickering line above panel for certain heights when using fractional scaling on Wayland with Background Contrast effect turned on
https://bugs.kde.org/show_bug.cgi?id=464526 Nate Graham changed: What|Removed |Added CC||ad.liu@gmail.com --- Comment #27 from Nate Graham --- *** Bug 465995 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 465995] Flashing white line under KRunner
https://bugs.kde.org/show_bug.cgi?id=465995 Nate Graham changed: What|Removed |Added CC||n...@kde.org Status|REPORTED|RESOLVED Resolution|--- |DUPLICATE --- Comment #2 from Nate Graham --- Same root cause as Bug 464526, which is fixed in Plasma 5.27.1. *** This bug has been marked as a duplicate of bug 464526 *** -- You are receiving this mail because: You are watching all bug changes.
[Bluedevil] [Bug 465984] Bluetooth service not active on boot even if enabled
https://bugs.kde.org/show_bug.cgi?id=465984 Nate Graham changed: What|Removed |Added Status|REPORTED|RESOLVED CC||n...@kde.org Resolution|--- |UPSTREAM --- Comment #1 from Nate Graham --- KDE code isn't involved here; you'll need to follow up with the Bluetooth devs. I suspect that this was caused by another change that just so happened to arrive at the same time as the Plasma 5.27 update. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 465971] Autoscroll icon in Firefox appears in the wrong location
https://bugs.kde.org/show_bug.cgi?id=465971 Nate Graham changed: What|Removed |Added Component|general |wayland-generic Product|kde |kwin Summary|[Wayland] Autoscroll icon |Autoscroll icon in Firefox |appears in the wrong|appears in the wrong |location|location Status|REPORTED|CONFIRMED Severity|normal |minor Assignee|unassigned-b...@kde.org |kwin-bugs-n...@kde.org CC||n...@kde.org Ever confirmed|0 |1 Version|unspecified |5.27.0 --- Comment #2 from Nate Graham --- Can reproduce. -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 464590] kded5 crashes in KScreen::Config::setOutputPriority() after monitor wakes from sleep
https://bugs.kde.org/show_bug.cgi?id=464590 Andrew Gunnerson changed: What|Removed |Added CC||accounts+...@chiller3.com -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 465965] blurry red-on-black and black-on-red text with high DPI scaling on Plasma Wayland with Intel UHD Graphics 770
https://bugs.kde.org/show_bug.cgi?id=465965 Nate Graham changed: What|Removed |Added CC||n...@kde.org Resolution|--- |WAITINGFORINFO Status|REPORTED|NEEDSINFO --- Comment #8 from Nate Graham --- I'm genuinely unable to notice any blurriness in the red text in those screenshots. I'm using a similar setup (Intel UHD620, 200% scale, Wayland) and don't see it either. Any chance you can attach a screenshot that makes it more obvious? -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 465111] Krita Help Content is not available offline
https://bugs.kde.org/show_bug.cgi?id=465111 vanyossi changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |INTENTIONAL CC||ghe...@gmail.com --- Comment #1 from vanyossi --- I'm sorry but we cannot possibly bundle the manual in all languages with Krita, that would make the download extremely big. If the user needs the manual offline they can download the manual in epub from https://docs.krita.org/en/index.html, specifically for english from here https://docs.krita.org/en/epub/KritaManual.epub -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 465962] Plasmashell freezes and crashes
https://bugs.kde.org/show_bug.cgi?id=465962 Nate Graham changed: What|Removed |Added Component|general |System Tray Resolution|--- |BACKTRACE Status|REPORTED|NEEDSINFO CC||mate...@gmail.com, ||n...@kde.org --- Comment #1 from Nate Graham --- Thank you for the bug report! Unfortunately the backtrace is incomplete and missing debug symbols for the following lines that we need to figure out exactly what's going wrong: > #5 0x7f7a37effbd7 in ?? () from > /usr/lib64/qt5/plugins/plasma/applets/org.kde.plasma.private.systemtray.so > #6 0x7f7a37effe39 in ?? () from > /usr/lib64/qt5/plugins/plasma/applets/org.kde.plasma.private.systemtray.so Could you please install debug symbols for Plasma, reproduce the crash, and attach a new symbolicated backtrace? See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports Thanks again! -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 465937] Resizing quick tiled windows affects quick tiling behavior
https://bugs.kde.org/show_bug.cgi?id=465937 Natalie Clarius changed: What|Removed |Added CC||natalie_clar...@yahoo.de -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 462695] Power management sometimes stops working
https://bugs.kde.org/show_bug.cgi?id=462695 Nate Graham changed: What|Removed |Added Resolution|WAITINGFORINFO |--- Status|NEEDSINFO |REPORTED --- Comment #30 from Nate Graham --- We're getting a lot of reports of power management not working properly in Plasma 5.27, but there appear to be a few root causes. I'll untangle this and find the distinct issues, then make them parent bugs for duplicates. In the meantime, it would be appreciated if people could avoid posting, "me too!" comments. Instead, filing a new bug report for your specific issue would be more helpful, and I'll mark it as a duplicate of the correct one. -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 465987] Power Module (power devil or whatever) won't start at all with latest plasma.
https://bugs.kde.org/show_bug.cgi?id=465987 Nate Graham changed: What|Removed |Added CC||n...@kde.org Status|REPORTED|NEEDSINFO Resolution|--- |BACKTRACE --- Comment #1 from Nate Graham --- Thank you for the bug report! Unfortunately the backtrace is incomplete and missing debug symbols for the following lines that we need to figure out exactly what's going wrong: > #8 0x7fafe96c3d37 in () at /lib64/libKF5ScreenDpms.so.8 Could you please install debug symbols for kscreen, reproduce the crash, and attach a new symbolicated backtrace? See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports Thanks again! -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 466054] Integrate input method panel into system tray
https://bugs.kde.org/show_bug.cgi?id=466054 Nate Graham changed: What|Removed |Added CC||n...@kde.org --- Comment #1 from Nate Graham --- It's possible; the applet just needs a metadata hint that tells the System Tray to include it. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kxmlgui] [Bug 466107] Make it clear how you can re-enable the menu bar and the toolbar when both are hidden
https://bugs.kde.org/show_bug.cgi?id=466107 Nate Graham changed: What|Removed |Added Summary|In many KDE applications, |Make it clear how you can |there's no obvious way of |re-enable the menu bar and |re-enabling the menu bar|the toolbar when both are |and the toolbar unless you |hidden |remember a keyboard | |shortcut| Keywords||usability Component|general |general Ever confirmed|0 |1 Product|kde |frameworks-kxmlgui Status|REPORTED|CONFIRMED Severity|normal |wishlist Version|unspecified |5.103.0 Assignee|unassigned-b...@kde.org |kdelibs-b...@kde.org --- Comment #3 from Nate Graham --- Yeah, or just a notification. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 466120] Window Class mode invisibly includes all windows, so you can access them using the keyboard
https://bugs.kde.org/show_bug.cgi?id=466120 Nate Graham changed: What|Removed |Added Priority|NOR |HI Summary|When clicking an app|Window Class mode invisibly |taskbar icon to show "large |includes all windows, so |window previews", keyboard |you can access them using |arrow keys can select |the keyboard |invisible windows not from | |the app | Product|plasmashell |kwin CC||n...@kde.org Target Milestone|1.0 |--- Ever confirmed|0 |1 Status|REPORTED|CONFIRMED Component|Task Manager and Icons-Only |effects-present-windows |Task Manager| Assignee|plasma-b...@kde.org |kwin-bugs-n...@kde.org Keywords||usability --- Comment #1 from Nate Graham --- OMG -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 465050] Wallpapers get misplaced on multimonitor setup
https://bugs.kde.org/show_bug.cgi?id=465050 mira...@mirandastreeter.com changed: What|Removed |Added CC||mira...@mirandastreeter.com -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 465969] Setting meta as shortcut for any action will trigger that action even when meta is used in key combination
https://bugs.kde.org/show_bug.cgi?id=465969 Nate Graham changed: What|Removed |Added CC||n...@kde.org Component|general |general Product|frameworks-kglobalaccel |kwin Assignee|kdelibs-b...@kde.org|kwin-bugs-n...@kde.org --- Comment #3 from Nate Graham --- I think it's time to remove the modifier only shortcut concept from KWin, now that it's redundant because we can trigger modifier-only shortcuts using KGlobalAccel. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 466090] Meta key does open the wrong start menu
https://bugs.kde.org/show_bug.cgi?id=466090 Nate Graham changed: What|Removed |Added Resolution|--- |WAITINGFORINFO CC||n...@kde.org Status|REPORTED|NEEDSINFO --- Comment #2 from Nate Graham --- How did you switch to Tiled Menu? Did you use the "alternatives" functionality, or add it manually? It seems like both are active at once. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 466095] Plasma crashes in DesktopView::screenToFollow() on screen wake up
https://bugs.kde.org/show_bug.cgi?id=466095 Nate Graham changed: What|Removed |Added Summary|Plasma crashes on screen|Plasma crashes in |wake up |DesktopView::screenToFollow ||() on screen wake up CC||aleix...@kde.org, ||n...@kde.org, ||notm...@gmail.com Component|general |Multi-screen support --- Comment #2 from Nate Graham --- Not the same backtrace as seen in Bug 413782. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 456947] Plasma crashes in ShellCorona::screenInvariants() when computer starts up without screen or monitor
https://bugs.kde.org/show_bug.cgi?id=456947 Nate Graham changed: What|Removed |Added Resolution|--- |WAITINGFORINFO Status|REPORTED|NEEDSINFO --- Comment #7 from Nate Graham --- . -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 466224] kwin needs an argument to configure in a locked down mode specific for login managers (sddm, etc.) and setup wizards (pico-wizard)
https://bugs.kde.org/show_bug.cgi?id=466224 Nate Graham changed: What|Removed |Added CC||aleix...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 466103] The "No Titlebar and Frame" toggle in the window context menu should be transient like all the other options in the same menu
https://bugs.kde.org/show_bug.cgi?id=466103 guimarcalsi...@gmail.com changed: What|Removed |Added Status|REPORTED|CONFIRMED Ever confirmed|0 |1 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 466103] The "No Titlebar and Frame" toggle in the window context menu should be transient like all the other options in the same menu
https://bugs.kde.org/show_bug.cgi?id=466103 guimarcalsi...@gmail.com changed: What|Removed |Added Summary|It's too easy to hide the |The "No Titlebar and Frame" |window titlebar and frame |toggle in the window ||context menu should be ||transient like all the ||other options in the same ||menu -- You are receiving this mail because: You are watching all bug changes.
