[kscreenlocker] [Bug 455303] New: kscreenlocker fails to compile without PAM
https://bugs.kde.org/show_bug.cgi?id=455303 Bug ID: 455303 Summary: kscreenlocker fails to compile without PAM Product: kscreenlocker Version: git-master Platform: Gentoo Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: esco...@hotmail.com CC: bhus...@gmail.com Target Milestone: --- SUMMARY Compiling without 'PAM' is no longer possible, probably after 132adacf3d0 [1], even though the 'PAM_REQUIRED' option still exists. 1. https://invent.kde.org/plasma/kscreenlocker/-/commit/132adacf3d01fc4adf8a873e0debc3adb17972ec STEPS TO REPRODUCE 1. Compile with '-DPAM_REQUIRED=NO' and no PAM installed. OBSERVED RESULT Compiling fails. EXPECTED RESULT Either compiling should still succeed without PAM, or the option is removed, and PAM is always required. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Gentoo Linux/git master (available in About System) KDE Plasma Version: git master (partial only to use KWin with LXQt) KDE Frameworks Version: git master (partial only to use KWin with LXQt) Qt Version: 5.15.4 (with KDE patches) -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 469426] Cannot move windows past left or top of desktop
https://bugs.kde.org/show_bug.cgi?id=469426 --- Comment #9 from Chiitoo --- I tried going back to Plasma bits at 5.27.0, and it happened there as well, and unfortunately did not have time to bisect older than that since I'd need to start bringing the Frameworks with it to be able to compile things, and scavenge more things from git history. If I remember right-like, last version we had packaged on Gentoo Linux that worked correctly for me was 5.26.5. For completeness, I also recorded a video that shows an additional oddity when trying to push a window beyond left or top, and then resizing said window: https://www.youtube.com/watch?v=uxSCPU2vjoY That is with Plasma 5.27.5 and Frameworks 5.106.0 on a Gentoo Linux virtual machine with a freshly created user account. I could not re-produce the panel auto-hide oddity that I have going on with LXQt, so that is another mystery to be solved, but it also only happens on the top and left. I did notice some other funky things with Plasma panels, but that's a whole different story. :] -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 469426] Cannot move windows past left or top of desktop
https://bugs.kde.org/show_bug.cgi?id=469426 --- Comment #11 from Chiitoo --- Sooo I'm not sure if I've just gone completely mad from too much compiling, while hunting for a cause for an issue with Wine [1], but yesterday this issue disappeared for me, and then returned today after restarting X11. I couldn't find what made the issue disappear, and I couldn't find what made it re-appear either. At one point I remembered that I accidentally compiled a bunch of other things with the testing CFLAGS, which I often do when I forget I set them manually. Yep, a patch had been added to KWin just around that time, and was re-compiled with '-march=x86-64 -O2 -g', and then again with my usual flags later, which include '-march=znver4', as I tried re-compiling without said patch. The issue with Wine seems to be connected to znver4 somehow as well, and so I tried compiling KWin with x86-64 again, as well as with zenver3, and sure enough, the issue went away again with either of those. I have no idea if there could be multiple sources for this issue, but on my part, it certainly seems like a GCC bug, where I'll be reporting this next. 1. https://bugs.winehq.org/show_bug.cgi?id=55007 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 469426] Cannot move windows past left or top of desktop
https://bugs.kde.org/show_bug.cgi?id=469426 Chiitoo changed: What|Removed |Added CC||esco...@hotmail.com --- Comment #1 from Chiitoo --- At last, someone else who is seeing this. :] I'm using KWin with LXQt on Gentoo Linux here, and so far I haven't met anyone else who is able to re-produce this. There's no need for a small screen, at least for me (1440p), and I'm unable to move any window past the top as well as the left side (single monitor or dual monitor set up both). Additionally, my panel is acting weird if placed on the top or the left side: even if set to hide automatically, it acts as if it is always visible. That is, it's impossible to select anything below it, and clicks go to the panel even if it is still visually hidden. Further, if set to be animated, it will always be instantaneous instead of smooth as it should be, and if set to have a visible thin margin, the panel never goes completely into hiding (it kind of moves a little bit). I think this started around 5.27.4; unfortunately I haven't had the chance to find the exact commit. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 469426] Cannot move windows past left or top of desktop
https://bugs.kde.org/show_bug.cgi?id=469426 --- Comment #2 from Chiitoo --- Oh and while normally the panel would come out of hiding when the pointer gets to the very edge of the screen, it acts as if the edge is on the opposite border instead, so moving the pointer to the area the panel is drawn at will already trigger unhiding it. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 469426] Cannot move windows past left or top of desktop
https://bugs.kde.org/show_bug.cgi?id=469426 --- Comment #6 from Chiitoo --- Right, it should, and was, before an update to KWin. I guess I'll really have to go digging where it starts and then the why. :] Thanks! -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 469426] Cannot move windows past left or top of desktop
https://bugs.kde.org/show_bug.cgi?id=469426 --- Comment #7 from Chiitoo --- Er, KWin and friends I meant to say; not sure it's KWin specifically, but in one of my quicker tests the behaviour returned to normal for me when downgrading KWin and friends to below 5.27.4 if I recall correct-like. Will be a bit more work at this point to go older than that on Gentoo, but if I find enough time... -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 488921] kwin_x11 crashes with sigsegv/11 when launching games
https://bugs.kde.org/show_bug.cgi?id=488921 Chiitoo changed: What|Removed |Added CC||esco...@hotmail.com --- Comment #5 from Chiitoo --- I've been seeing a more or less identical backtrace since kwin 6.0.90 (to which I updated from 6.0.5 ~2 weeks ago). I believe what actually triggers this, is compositing being switched on and/or off again. I don't have 'allow applications to block compositing' enabled, but I often switch it off manually, which is how I encountered the issue. One way to re-produce on my machine: 1. Have compositing enabled, and 'enable on startup' checked. 2. Select a window decoration that is not Breeze or Oxygen; these don't seem to trigger it for me, but Plastik, and any other additional themes I've tried do. 3. Also have some application running, Konsole for example. 4. Turn off compositing. 5. Interact with the Konsole application via the panel. 6. Segmentation fault ensues. There was another issue where simply toggling compositing would segfault, but that was fixed in 6.1.0 for me (change from 5db1cae615b [1] specifically, which I used before 6.1.0 was out). I'm using KWin with LXQt, X11, and had not found anyone seeing this on Plasma yet, and I could not make it happen in a virtual machine, but looking at the code, it might be somewhat specific to 'glxcontext', which I guess might differ there (using 'amdgpu' on the real machine). Been trying to gather as much information as I can before filing a bug report, but this seems to be talking about the same issue (yay!). Triggering the crash without 'enable on startup' checked on 'compositing' gives a somewhat different backtrace, which is the one that is similar to the one in comment 4. Regarding frame '#5 0x5abcbd80e920 in ?? ()', I always see it end up in a '?? ()' as well, but one time I saw 'libQt6Qml.so' there, but after compiling qtdeclarative with debug symbols, it of course went back to '??'... Thank you! 1. https://invent.kde.org/plasma/kwin/-/commit/5db1cae615b177d58b065276e81da0993af0ed6e -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 488921] kwin_x11 crashes with sigsegv/11 when launching games
https://bugs.kde.org/show_bug.cgi?id=488921 --- Comment #6 from Chiitoo --- Looks like the issue for me is gone with 6.1.2, probably due to commit c6d2eac81ae [1], meaning this could potentially be a duplicate of bug 488830 (I do feel like I had tried with this commit at some point, but perhaps I did not after all). 1. https://invent.kde.org/plasma/kwin/-/commit/c6d2eac81ae9dba99df40aba185b50c3f1f9f021 2. https://bugs.kde.org/488830 -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 454964] crash on tab closing
https://bugs.kde.org/show_bug.cgi?id=454964 Chiitoo changed: What|Removed |Added CC||esco...@hotmail.com -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 456627] Reported tab name contains non-substituted %n in it
https://bugs.kde.org/show_bug.cgi?id=456627 Chiitoo changed: What|Removed |Added CC||esco...@hotmail.com -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kglobalaccel] [Bug 437034] kglobalaccel has stopped working completely
https://bugs.kde.org/show_bug.cgi?id=437034 Chiitoo changed: What|Removed |Added CC||esco...@hotmail.com --- Comment #5 from Chiitoo --- Probably commit 48c3376927e [1]? It pretty much breaks KWin for me when running it with LXQt (haven't noticed anything going wrong there). 1. https://invent.kde.org/frameworks/kglobalaccel/-/commit/48c3376927e5e9c13377bf3cfc8b0c411783e7f3 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kglobalaccel] [Bug 437034] kglobalaccel has stopped working completely
https://bugs.kde.org/show_bug.cgi?id=437034 --- Comment #6 from Chiitoo --- (In reply to Chiitoo from comment #5) > Probably commit 48c3376927e [1]? > > It pretty much breaks KWin for me when running it with LXQt (haven't noticed > anything going wrong there). > > 1. > https://invent.kde.org/frameworks/kglobalaccel/-/commit/ > 48c3376927e5e9c13377bf3cfc8b0c411783e7f3 Funny I just now noticed bug 435420 [1] that was mentioned in that commit. 1. https://bugs.kde.org/show_bug.cgi?id=435420 -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 448144] New: regression: copying using ctrl_shift_c no longer works
https://bugs.kde.org/show_bug.cgi?id=448144 Bug ID: 448144 Summary: regression: copying using ctrl_shift_c no longer works Product: konsole Version: master Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: copy-paste Assignee: konsole-de...@kde.org Reporter: esco...@hotmail.com Target Milestone: --- STEPS TO REPRODUCE 1. Launch Konsole and try to select and copy only one character using 'ctrl_shift_c'. OBSERVED RESULT ^C is sent instead of copying the character. EXPECTED RESULT The character selected is copied. SOFTWARE/OS VERSIONS Linux: Gentoo Linux KDE Plasma Version: git master KDE Frameworks Version: git master Qt Version: 5.15.2 (KDE) git master ADDITIONAL INFORMATION Not a full KDE Plasma install, but just enough to use KWin with LXQt. This starts with commit 5919c1fd0a2 [1]. 1. https://invent.kde.org/utilities/konsole/-/commit/5919c1fd0a2e174079055b747aa279209900c6c6 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 423373] New: Invisible Context Menus With Compositing Enabled
https://bugs.kde.org/show_bug.cgi?id=423373 Bug ID: 423373 Summary: Invisible Context Menus With Compositing Enabled Product: kwin Version: git master Platform: Gentoo Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: compositing Assignee: kwin-bugs-n...@kde.org Reporter: esco...@hotmail.com Target Milestone: --- SUMMARY After commit cc3eb54b [1], any context menu (right-click, application menu, etc.) are invisible, if compositing is enabled. STEPS TO REPRODUCE 1. Build KWin at 'git master', or at least at commit 'cc3eb54b'. 2. Run a desktop environment using 'kwin_x11', with compositor enabled. 3. Right-click things that would normally show a context menu. OBSERVED RESULT No menu is displayed, though they are actually there, and can be interacted with. EXPECTED RESULT Menus show up. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Gentoo/git master KDE Plasma Version: git master KDE Frameworks Version: git master Qt Version: git master (5.15) LXQt Version: git master ADDITIONAL INFORMATION I have not tried disabling different effects or playing with any related settings yet. The XRender rendering back-end is being used, since OpenGL has been, and still seems to be unstable for me (with NVIDIA proprietary drivers in the past, AMDGPU (xf86) now). Thank you! 1. https://invent.kde.org/plasma/kwin/-/commit/cc3eb54b -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 423373] Invisible Context Menus With Compositing Enabled
https://bugs.kde.org/show_bug.cgi?id=423373 Chiitoo changed: What|Removed |Added Resolution|--- |WORKSFORME Status|REPORTED|RESOLVED --- Comment #1 from Chiitoo --- Fixed in 1b4c725d [1]. 1. https://invent.kde.org/plasma/kwin/-/commit/1b4c725d108b595b85a75aaa2c69721ffb085bef -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 443723] "Display geometry when moving or resizing" does not work under wayland
https://bugs.kde.org/show_bug.cgi?id=443723 Chiitoo changed: What|Removed |Added CC||esco...@hotmail.com --- Comment #2 from Chiitoo --- Since fcf0b4796f5 [1] this is gone for X11 as well. Should there perhaps be a separate bug requesting a replacement feature? I for one used this surprisingly much, and I do consider my use-case rather regular in nature. :] Thanks! 1. https://invent.kde.org/plasma/kwin/-/commit/fcf0b4796f55fc15aa60a339ea40cdbb4573f9b8 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 443723] "Display geometry when moving or resizing" does not work under wayland
https://bugs.kde.org/show_bug.cgi?id=443723 --- Comment #4 from Chiitoo --- (In reply to Vlad Zahorodnii from comment #3) > > I for one used this surprisingly much, and I do consider my use-case rather > > regular in nature. > What did you use it for? Nothing /too/ specific really, that I can think of right now. Mostly it's probably just that I've become very accustomed to having different windows be of a particular size, which can actually be very useful when taking screenshots or video off of them (no need to resize them later for example). Somewhat similarly, it has been very useful in keeping aspect ratios and such as they should be for games, especially older ones, which don't have built-in options to set the resolution right (this also goes for the images and video in some cases). There might be more specific things I've used this for, but can't think of right now. I can't imagine being the only one making so much use of this, but I do also understand removing it if there are only a handful of us. Thanks! -- You are receiving this mail because: You are watching all bug changes.
[Falkon] [Bug 426486] New: Falkon Background Colour Overridden
https://bugs.kde.org/show_bug.cgi?id=426486 Bug ID: 426486 Summary: Falkon Background Colour Overridden Product: Falkon Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: now...@gmail.com Reporter: esco...@hotmail.com Target Milestone: --- SUMMARY After 4ebeb509 [1], any background (without set colour?) will be painted with the widget window colour, so for example something like a plain text file will be rendered with purple background instead of white (using the default theme of Falkon), if window colour was set to purple via, for example, the LXQt 'Window Color' setting in LXQt Appearance Configuration/Widget Style. This also affects times when a new tab for example is opened: the window will flash with an unexpected colour. STEPS TO REPRODUCE 1. Set widget window colour to '$someColour'. 2. Observe the normally white (default style) backgrounds be painted with '$someColour'. OBSERVED RESULT Backgrounds are painted with widget window colour. EXPECTED RESULT Backgrounds are not painted with widget window colour. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Gentoo Linux/git master KDE Plasma Version: git master KDE Frameworks Version: git master Qt Version: 5.15.1 (5.15 git master) ADDITIONAL INFORMATION 1. https://invent.kde.org/network/falkon/-/commit/4ebeb509b75b8ca2ce494d30d8f60ddcf124e9f2 -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 436845] History Scrolled tty couldnt set its begining position while selecting texts
https://bugs.kde.org/show_bug.cgi?id=436845 Chiitoo changed: What|Removed |Added CC||esco...@hotmail.com -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 435309] 3b06b6f22 makes selection near invisible with some foreground/background color combinations
https://bugs.kde.org/show_bug.cgi?id=435309 Chiitoo changed: What|Removed |Added CC||esco...@hotmail.com -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 489640] Windows always open on the wrong screen after reopening without moving the cursor
https://bugs.kde.org/show_bug.cgi?id=489640 Chiitoo changed: What|Removed |Added CC||esco...@hotmail.com -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 489904] New windows by default on wrong monitor
https://bugs.kde.org/show_bug.cgi?id=489904 Chiitoo changed: What|Removed |Added CC||esco...@hotmail.com -- You are receiving this mail because: You are watching all bug changes.
[konversation] [Bug 340748] Disable auto-WHO for Twitch servers.
https://bugs.kde.org/show_bug.cgi?id=340748 --- Comment #8 from Chiitoo --- Many thanks for taking care of this! -- You are receiving this mail because: You are watching all bug changes.
[konversation] [Bug 340748] Disable auto-WHO for Twitch servers.
https://bugs.kde.org/show_bug.cgi?id=340748 --- Comment #4 from Chiitoo --- (In reply to Eike Hein from comment #3) > So we get a 421 for the failing WHO from the Twitch server it turns out. I > think we should catch it, and stop auto-WHO'ing in response. I think it's > safe to assume that if you get a 421 the server won't start supporting the > command within the same session, and it's pointless to keep trying then. Seems like a plan. I have been thinking of this issue now and then again, and have been meaning to see if I could come up with a more proper-like solution. Unfortunately, I haven't managed to get to it yet. Many thanks for the comment (and reminder). :] -- You are receiving this mail because: You are watching all bug changes.
