[konsole] [Bug 460383] Custom profiles do not remain saved after Konsole is restarted
https://bugs.kde.org/show_bug.cgi?id=460383 --- Comment #2 from Vladislav Rubtsov --- Alright, if anyone else suffers from this bug and wants a quick fix, you can copy-paste my profile data as a placeholder, then edit it to your liking (editing should work fine). WORKAROUND: 1. In Konsole, open Settings > Manage Profiles... 2. Create a new profile name `Your Profile Name.profile`, SET IT AS A DEFAULT ONE. 3. Exit Konsole. YOUR PROFILE WON'T BE SAVED DUE TO A BUG, but it's path will be written to `~/.config/konsolerc` (see my comment above for details). 4. Manually create a file `~/.local/share/konsole/Your Profile Name.profile`. You can use my data as a placeholder: * * * [Appearance] AntiAliasFonts=true BoldIntense=true ColorScheme=Breeze DimmValue=128 Font=Consolas,12,-1,5,50,0,0,0,0,0 LineSpacing=0 TabColor=invalid UseFontLineChararacters=false [Cursor Options] CursorShape=0 CustomCursorColor=255,255,255 CustomCursorTextColor=0,0,0 UseCustomCursorColor=false [Encoding Options] DefaultEncoding=UTF-8 [General] Command=/bin/bash DimWhenInactive=false Environment=TERM=xterm-256color,COLORTERM=truecolor Icon=utilities-terminal LocalTabTitleFormat=%d : %n Name=Profile 4 RemoteTabTitleFormat=(%u) %H ShowTerminalSizeHint=true SilenceSeconds=10 StartInCurrentSessionDir=true TerminalCenter=false TerminalColumns=110 TerminalMargin=1 TerminalRows=28 [Interaction Options] AllowEscapedLinks=false AlternateScrolling=true AutoCopySelectedText=false CopyTextAsHTML=true CtrlRequiredForDrag=true DropUrlsAsText=true EscapedLinksSchema=http://;https://;file:// MiddleClickPasteMode=0 MouseWheelZoomEnabled=true OpenLinksByDirectClickEnabled=false PasteFromClipboardEnabled=false PasteFromSelectionEnabled=true TrimLeadingSpacesInSelectedText=false TrimTrailingSpacesInSelectedText=false TripleClickMode=0 UnderlineFilesEnabled=false UnderlineLinksEnabled=true WordCharacters=:@-./_~?&=%+# [Keyboard] KeyBindings=default [Scrolling] HighlightScrolledLines=true HistoryMode=1 HistorySize=1000 ScrollBarPosition=1 ScrollFullPage=false [Terminal Features] BellMode=1 BidiRenderingEnabled=true BlinkingCursorEnabled=false BlinkingTextEnabled=true FlowControlEnabled=true PeekPrimaryKeySequence= ReverseUrlHints=false UrlHintsModifiers=0 VerticalLine=false VerticalLineAtChar=80 * * * Notice I use Consolas font in this config. I don't think it will break if you don't have it. 5. Try loading Konsole again. You should now be able to load and edit `Your Profile Name`. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 460383] Custom profiles do not remain saved after Konsole is restarted
https://bugs.kde.org/show_bug.cgi?id=460383 Vladislav Rubtsov changed: What|Removed |Added CC||rubs...@gmail.com --- Comment #1 from Vladislav Rubtsov --- I have the same bug in the current Debian Testing, which also uses Konsole v.22.08.1 My observations: - When you create a new profile and set it as default, its path *does get* saved to Konsole config, but the profile file itself is never written to. - After creating a new profile, open `~/.config/konsolerc`. You should see profile file name `[Desktop Entry]` section. - The profile itself should be saved in `~/.local/share/konsole/Your Profile Name.profile`, but this doesn't happen. - However, Konsole likely thinks profile *save was successful*. Otherwise, it's programmed to display an error message. I was able to bypass this bug by manually creating `~/.local/share/konsole/Your Profile Name.profile` (I actually copied it over from my Debian 11 installation, where Konsole isn't buggy). When the profile file was present that matched `[Desktop Entry] > DefaultProfile` in `~/.config/konsolerc`, it was loading successfully, and I was able to both edit and rename it. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 450301] On KWin 5.24 X11 Nvidia, when reenabling compositing, windows begin flickering and flipping upside-down
https://bugs.kde.org/show_bug.cgi?id=450301 Vladislav Rubtsov changed: What|Removed |Added CC||rubs...@gmail.com --- Comment #8 from Vladislav Rubtsov --- I have exactly the same issue as seen on the video attache by Awakening. This is certainly a compositor problem as disabling compositor (Shift+Alt+F12) fixes it. This is extremely annoying as I haven't found a reliable way to fix this (switching compositor on/off doesn't always help). It happens after wake up or exiting a game or other fullscreen application that temporarily disables compositing. Operating System: Manjaro Linux KDE Plasma Version: 5.25.5 KDE Frameworks Version: 5.97.0 Qt Version: 5.15.5 Kernel Version: 5.18.19-3-MANJARO (64-bit) Graphics Platform: X11 Processors: 12 × Intel® Core™ i7-10750H CPU @ 2.60GHz Memory: 31.3 GiB of RAM Graphics Processor: NVIDIA GeForce RTX 2070 Super/PCIe/SSE2 (driver 515.65.01) Manufacturer: Motherboard by ZOTAC Product Name: ZBOX-QCM7T3000/EN072080S/EN072070S/EN052060C System Version: Rev.00 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 408864] Tray and global shortcuts malfunctioning after suspension in Plasma 5.16.0
https://bugs.kde.org/show_bug.cgi?id=408864 --- Comment #5 from Vladislav Rubtsov --- (In reply to Nate Graham from comment #3) > Sorry for not responding. :( > > Sadly without a reproducible case, there's not much we can do here. Did it > ever happen again? No problem! That bug was reproducing consistently upon waking up after suspension, as mentioned in the original report. However, after next major version update (I think, from 5.17.x onwards, but it's hard to remember already) the issue was no longer there and waking up functioned normally. I think, this bug can be closed now. -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 433126] Inactive title bar elements in Breeze Light have the same color as active title bar elements
https://bugs.kde.org/show_bug.cgi?id=433126 Vladislav Rubtsov changed: What|Removed |Added CC||rubs...@gmail.com --- Comment #5 from Vladislav Rubtsov --- The bug is most likely related to the color blending effects, which cannot be edited by KColorSchemeEditor at this point. By closely inspecting color theme files, I found out that "Breeze Light" now uses the following settings not found in certain other themes: [WM] activeBlend=227,229,231 inactiveBlend=239,240,241 This is most likely responsible for incorrect coloring of the active title bar, when user changes the color to non-default one. I've been trying to manually edit Breeze Light color scheme, by saving a copy of it then altering its file in '~/.kde/share/apps/color-schemes/', but to no avail. It looks like KDE stores user-defined settings elsewhere and this is just a dump/cache of it. Any insight of how to properly edit KDE system settings by hand would be highly appreciated. It bugs me how KDE internals are not documented at all, nor they are easy to work with, since something as simple as manually editing one line of a color theme has no apparent workaround. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 415675] New: Krita always crashes when copying any area using Transform tool
https://bugs.kde.org/show_bug.cgi?id=415675 Bug ID: 415675 Summary: Krita always crashes when copying any area using Transform tool Product: krita Version: 4.2.8 Platform: unspecified OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: General Assignee: krita-bugs-n...@kde.org Reporter: rubs...@gmail.com Target Milestone: --- Application: krita (4.2.8) Qt Version: 5.13.2 Frameworks Version: 5.65.0 Operating System: Linux 5.0.0-37-generic x86_64 Distribution: KDE neon User Edition 5.17 -- Information about the crash: Steps to reproduce: 1. Open any image (or create one). 2. Select any region within the image using Rectangle selection tool (Ctrl+R). 3. Switch to the Transform Tool (Ctrl+T). 4. Attempt to copy it (Ctrl+C). 5. Krita *always* crashes, and the following message appears in terminal: krita: /usr/include/boost/optional/optional.hpp:1107: boost::optional::reference_type boost::optional::get() [with T = ToolTransformArgs; boost::optional::reference_type = ToolTransformArgs&]: Assertion `this->is_initialized()' failed. As I said, the crash is constant, regardless of the image, its number of layers, number of pixels within selection etc. This basically renders Krita unusable for me. However, there is one method of avoiding this bug (but I cannot confirm if it's reliable): if you move the selection around before copying it, the copying works and doesn't cause the crash. Please note, that this crash only occurs with the Krita 4.2.8.x installed from KDE Neon repository (bionic/main). This does not occur in the same versions installed from flatpak or snap. But they have other size, compatibility and system integration issues, so I'd prefer not to use them if I could. That said, it could be due to incompatible or older version of any dependency that Krita uses. System info: OS: KDE neon 5.17 Kernel: x86_64 Linux 5.0.0-37-generic Shell: bash 4.4.20 Resolution: 3288x1224 DE: KDE 5.65.0 / Plasma 5.17.4 WM: KWin GTK Theme: Breeze [GTK2/3] Icon Theme: breeze Font: Noto Sans Regular CPU: Intel Core i7-6700HQ @ 8x 3.5GHz [55.0°C] GPU: GeForce GTX 950M RAM: 7189MiB / 11898MiB The crash can be reproduced every time. -- Backtrace: Application: Krita (krita), signal: Aborted Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f7305682800 (LWP 2391))] Thread 8 (Thread 0x7f7292ffd700 (LWP 2429)): [KCrash Handler] #6 __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:51 #7 0x7f7300414801 in __GI_abort () at abort.c:79 #8 0x7f730040439a in __assert_fail_base (fmt=0x7f730058b7d8 "%s%s%s:%u: %s%sAssertion `%s' failed.\n%n", assertion=assertion@entry=0x7f72cc6918f0 "this->is_initialized()", file=file@entry=0x7f72cc691760 "/usr/include/boost/optional/optional.hpp", line=line@entry=1107, function=function@entry=0x7f72cc6919a0 ::get()::__PRETTY_FUNCTION__> "boost::optional::reference_type boost::optional::get() [with T = ToolTransformArgs; boost::optional::reference_type = ToolTransformArgs&]") at assert.c:92 #9 0x7f7300404412 in __GI___assert_fail (assertion=assertion@entry=0x7f72cc6918f0 "this->is_initialized()", file=file@entry=0x7f72cc691760 "/usr/include/boost/optional/optional.hpp", line=line@entry=1107, function=function@entry=0x7f72cc6919a0 ::get()::__PRETTY_FUNCTION__> "boost::optional::reference_type boost::optional::get() [with T = ToolTransformArgs; boost::optional::reference_type = ToolTransformArgs&]") at assert.c:101 #10 0x7f72cc633a01 in boost::optional::get (this=) at /usr/include/boost/optional/optional.hpp:1107 #11 boost::optional::operator*() & (this=) at /usr/include/boost/optional/optional.hpp:1124 #12 TransformStrokeStrategy::finishStrokeCallback (this=) at ./plugins/tools/tool_transform2/strokes/transform_stroke_strategy.cpp:704 #13 0x7f72cc67fecc in TransformStrokeStrategy::cancelStrokeCallback (this=0x5610e78ed850) at /usr/include/boost/optional/optional.hpp:697 #14 0x7f7303088849 in non-virtual thunk to KisUpdateJobItem::run() () from /usr/lib/x86_64-linux-gnu/libkritaimage.so.18 #15 0x7f7300e14472 in QThreadPoolThread::run (this=0x5610ef0f3f90) at thread/qthreadpool.cpp:99 #16 0x7f7300e10b52 in QThreadPrivate::start (arg=0x5610ef0f3f90) at thread/qthread_unix.cpp:360 #17 0x7f72fa1856db in start_thread (arg=0x7f7292ffd700) at pthread_create.c:463 #18 0x7f73004f588f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 7 (Thread 0x7f72b157c700 (LWP 2411)): #0 0x7f73004e8bf9 in __GI___poll (fds=0x7f72ac00c730, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7f72f5c9 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f72f6dc in g_main_context_iteration () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3
[plasma-nm] [Bug 411220] No wired connection available after suspension
https://bugs.kde.org/show_bug.cgi?id=411220 Vladislav Rubtsov changed: What|Removed |Added Resolution|--- |NOT A BUG Status|REPORTED|RESOLVED --- Comment #3 from Vladislav Rubtsov --- Kernel bug confirmed: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1752772 Somehow, this is still present in 5.0.0 kernel. This has nothing to do with KDE's Network Manager. -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 411220] No wired connection available after suspension
https://bugs.kde.org/show_bug.cgi?id=411220 --- Comment #2 from Vladislav Rubtsov --- Found a workaround all of a sudden. Removing kernel module "r8169" (which is my Ethernet adapter driver) and then loading it again seems to restore the connection: # modprobe -r r8169 # modprobe r8169 Does it mean it's possibly a kernel-level bug? -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 411220] No wired connection available after suspension
https://bugs.kde.org/show_bug.cgi?id=411220 --- Comment #1 from Vladislav Rubtsov --- So far, the only way to restore connection for me is a reboot. After reboot, Wired Connection becomes available as usual. -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 411220] New: No wired connection available after suspension
https://bugs.kde.org/show_bug.cgi?id=411220 Bug ID: 411220 Summary: No wired connection available after suspension Product: plasma-nm Version: 5.16.4 Platform: Neon Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: jgrul...@redhat.com Reporter: rubs...@gmail.com Target Milestone: --- SUMMARY After the recent updates, whenever my laptop wakes up from suspension, wired connection (via Ethernet adapter) is not restored and completely vanishes from the connections list in Network Manager (as if the wire has been physically disconnected). So far, I haven't found any way to restore it, which is insanely annoying. - Reconnecting the wire doesn't work; - Restarting "NetworkManager" and/or "networking" services doesn't help, but introduce more bugs (wireless connection stop working due to missing secrets); - Replacing "plasmashell" doesn't affect it; - Judging by "ifconfig" output, the Ethernet interface is UP and completely functional after suspension. STEPS TO REPRODUCE 1. Suspend to RAM. 2. Wake it up. OBSERVED RESULT Wired connection no longer works and is not visible in Network Manager. EXPECTED RESULT Wired connection to work normally. SOFTWARE/OS VERSIONS OS: KDE neon 5.16 Kernel: x86_64 Linux 5.0.0-25-generic Uptime: 14m Packages: 3086 Shell: bash 4.4.20 Resolution: 3280x1248 DE: KDE 5.61.0 / Plasma 5.16.4 WM: KWin GTK Theme: Breeze [GTK2/3] Icon Theme: breeze Font: Noto Sans Regular CPU: Intel Core i7-6700HQ @ 8x 3.5GHz [54.0°C] GPU: GeForce GTX 950M RAM: 1719MiB / 11898MiB ADDITIONAL INFORMATION Ethernet interface is "enp3s0f1". The device is "Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller". -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 408864] Tray and global shortcuts malfunctioning after suspension in Plasma 5.16.0
https://bugs.kde.org/show_bug.cgi?id=408864 --- Comment #2 from Vladislav Rubtsov --- (In reply to Nate Graham from comment #1) > So all the issues go away if you just restart plasmashell? Do they return > when the computer is restarted? No, I've never (yet) seen this happen after a fresh boot. But all the described issues *always* occur after suspension (without exceptions). At first, I thought it could be (somehow) Compositor-related, because I used to have several glitches and regressions on KDE with NVidia drivers, but switching rendering backend between XRender and OpenGL has no effect. UPDATE: I've also discovered, the very same behavior occurs when switching between TTY and desktop session. For precisely, once you use Ctrl+Alt+F2/F3/.. to switch to TTY, then Ctrl+Alt+F1 to return to the desktop session, all of the described bugs also occur. (P.S.: The screen appears normal for a split second, then it re-renders and all the application tray icons vanish, meaning the system already entered this "buggy" state with no). P.S.: I cannot see any related errors in system journals after this starts to happen. However, when plasmashell is restarted (via --replace flag), I can cleary these lines among the others: org.kde.kded5[4544]: Imported file "/usr/share/khotkeys/kde32b1.khotkeys" org.kde.kded5[4544]: Imported file "/usr/share/khotkeys/konsole.khotkeys" org.kde.kded5[4544]: Imported file "/usr/share/khotkeys/defaults.khotkeys" <...> org.kde.kded5[4544]: Registering "org.kde.StatusNotifierHost-2455" as system tray This components may in fact be responsible. Could it be that it doesn't restore or restart properly after recovering from suspension/TTY? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 408864] New: Tray and global shortcuts malfunctioning after suspension in Plasma 5.16.0
https://bugs.kde.org/show_bug.cgi?id=408864 Bug ID: 408864 Summary: Tray and global shortcuts malfunctioning after suspension in Plasma 5.16.0 Product: plasmashell Version: 5.16.0 Platform: Neon Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: rubs...@gmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 SUMMARY A few days ago, my laptop upgraded to KDE Neon 5.16, and the system became surprisingly unstable after waking-up from suspension with dozens of system-wide issues affecting usability (I'm almost certain this has something to do with a re-written notifications system). STEPS TO REPRODUCE 1. Suspend system to RAM. 2. Wake system up. OBSERVED RESULT A variety of system-wide bugs happen all at once: 1. All application icons are now missing from tray. This affects layout indicator and every application that usually puts itself on the tray (for instance, messengers, like Telegram, Skype etc). However, system tray icons, like network manager, clipboard, battery, volume are still displayed. 2. Many global shortcuts stop working, for instance: - Ctrl+Alt+T to bring up terminal (does nothing) - PrintScreen, Ctrl+PrintScreen etc (appears to have no effect) - CapsLock, which is configured to switch keyboard layout on my system (simply triggers CapsLock key) However, Ctrl+Alt+L to lock screen still works. 3. As the result of the bug above, switching keyboard layout no longer works. There is also no way to switch layout manually, since layout indicator is missing from the tray. Any attempt to change/update options for switching layouts has no effect. System starts functioning normally after reboot. There was one time this buggy state resolved spontaneously after a while: a lot of delayed notifications popped up at once, missing icons appeared and global shortcuts started functioning. I couldn't, however, reproduce this "self-cure" behaviour anytime later. WORKARROUND It took me a while to figure a working workaround for this one. Simply replacing the window manager (kwin) cannot recover system from this buggy state (the bugs always persist). The only workaround I figured out so far is to replace plasmashell itself: $ plasmashell --replace & This is why I'm putting this bug under "plasmashell" section. SOFTWARE/OS VERSIONS OS: KDE neon 5.16 Kernel: x86_64 Linux 4.18.0-21-generic Uptime: 1d 1h 52m Packages: 2969 Shell: bash 4.4.19 Resolution: 3280x1248 DE: KDE 5.59.0 / Plasma 5.16.0 WM: KWin GTK Theme: Breeze [GTK2/3] Icon Theme: breeze Font: Noto Sans Regular CPU: Intel Core i7-6700HQ @ 8x 3.5GHz [56.0°C] GPU: GeForce GTX 950M -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 406319] Hangs/freezes when drag windows to top, right or left edges of the screen
https://bugs.kde.org/show_bug.cgi?id=406319 --- Comment #8 from Vladislav Rubtsov --- Any updates on this bug's status? I suffer from this bug too and I originally opened Bug 406307 with similar report (which was marked as duplicate, though posted earlier). Setting Compositor Rendering backend to "Xrender" as others suggested doesn't fully fix the issue on my end. It just makes freezes occur somewhat less. I would say with "OpenGL" window dragging animations exhibit freezes 90% of the times (was far less frequent before the 5.15.4 update), and with "Xrender" it's only 10-15%, which is of course a lot better, but the bug is still there. Graphics: Card-1: Intel HD Graphics 530 bus-ID: 00:02.0 Card-2: NVIDIA GM107M [GeForce GTX 950M] bus-ID: 01:00.0 Display Server: X.Org 1.20.1 drivers: nvidia FAILED: modesetting Resolution: 1360x768@59.96hz, 1920x1080@60.00hz OpenGL: renderer: GeForce GTX 950M/PCIe/SSE2 version: 4.6.0 NVIDIA 390.116 Direct Render: Yes -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 406307] Desktop always unresponsive after dragging windows to maximize them
https://bugs.kde.org/show_bug.cgi?id=406307 --- Comment #2 from Vladislav Rubtsov --- UPDATE #2: The problem doesn't occur in Wayland sessions. So, after a lot of experimentation with video drivers and Xorg configuration I was able to fix this issue. That involved switching back and forth between Nvidia and Nouveau drivers via the Driver Manager (Ubuntu's version). I'm still not sure how exactly it was fixed, but the one notable difference is that modesetting driver is not loaded as seen in "inxi" output: Graphics: Card-1: Intel HD Graphics 530 bus-ID: 00:02.0 Card-2: NVIDIA GM107M [GeForce GTX 950M] bus-ID: 01:00.0 Display Server: X.Org 1.20.1 drivers: nvidia (unloaded: modesetting,nouveau) Resolution: 1360x768@59.96hz, 1920x1080@60.00hz OpenGL: renderer: GeForce GTX 950M/PCIe/SSE2 version: 4.6.0 NVIDIA 390.116 Direct Render: Yes -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 406307] Desktop always unresponsive after dragging windows to maximize them
https://bugs.kde.org/show_bug.cgi?id=406307 --- Comment #1 from Vladislav Rubtsov --- UPDATE: Attempt drag windows to left/right screen edge reproduces the bug as well. It seems like the freeze occurs whenever the animation of future window size filling the space tries to play (it plays eventually, after the freeze). Note that maximizing animation itself works flawlessly, and I can maximize windows via "maximize" button or by double-clicking their headers without delays. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 406307] New: Desktop always unresponsive after dragging windows to maximize them
https://bugs.kde.org/show_bug.cgi?id=406307 Bug ID: 406307 Summary: Desktop always unresponsive after dragging windows to maximize them Product: plasmashell Version: 5.15.4 Platform: Ubuntu Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Desktop Containment Assignee: se...@kde.org Reporter: rubs...@gmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 SUMMARY I'm running KDE Neon User Edition. After recent upgrade to Plasma 5.15.4 now every time I drag a window to the top edge of the screen to maximize it, the desktop *always* becomes unresponsive for exactly 13 seconds (I measured several times using my smartphone's clock). After that, the window usually maximizes normally. Now, for me, this bug persisted since I started using KDE Neon (which was around Plasma 5.12.*, I believe), *HOWEVER* until the recent upgrade (to 5.15.4) it the bug was occurring just occasionally. It worked without freezes most of the time, so I could live with that. Now the bug always persists, which kind of make system unusable for me (I'm looking into downgrade to 5.15.3 at least). STEPS TO REPRODUCE 1. Attempt to maximize any window by dragging it to the top edge of the screen (the option "Maximize windows by dragging them to the top edge of the screen" should be enabled in System Settings > Desktop behavior > Screen Edges) OBSERVED RESULT Desktop always becomes unresponsive for 13 seconds, after which window is maximized properly. EXPECTED RESULT Window maximized by dragging immediately. SOFTWARE/OS VERSIONS KDE Plasma Version: 5.15.4 KDE Frameworks Version: 5.56.0 Qt Version: 5.12.0 Kernel Version: 4.18.0-17-generic ADDITIONAL INFORMATION I have multi-monitor setup, but bug is reproducible even with one monitor disabled. Disabling Compositor has no effect. System Info: Machine: Device: laptop System: ASUSTeK product: X550VX v: 1.0 serial: N/A Mobo: ASUSTeK model: X550VX v: 1.0 serial: N/A UEFI [Legacy]: American Megatrends v: X550VX.302 date: 05/04/2017 Graphics: Card-1: Intel HD Graphics 530 bus-ID: 00:02.0 Card-2: NVIDIA GM107M [GeForce GTX 950M] bus-ID: 01:00.0 Display Server: x11 (X.Org 1.20.1 ) drivers: modesetting,nvidia (unloaded: fbdev,vesa,nouveau) Resolution: 1920x1080@59.97hz, 1920x1080@60.00hz OpenGL: renderer: GeForce GTX 950M/PCIe/SSE2 version: 4.6.0 NVIDIA 390.116 Direct Render: Yes Xrandr output: Screen 0: minimum 8 x 8, current 3840 x 1080, maximum 16384 x 16384 eDP-1-1 connected 1920x1080+1920+0 (normal left inverted right x axis y axis) 344mm x 193mm 1920x1080 60.00 + 59.97* 59.9659.93 <...> HDMI-1-1 connected primary 1920x1080+0+0 (normal left inverted right x axis y axis) 598mm x 336mm 1920x1080 60.00*+ <...> DP-1-1 disconnected (normal left inverted right x axis y axis) XOrg log: X.Org X Server 1.20.1 X Protocol Version 11, Revision 0 [12.162] Build Operating System: Linux 4.4.0-140-generic x86_64 Ubuntu [12.162] Current Operating System: Linux comper-shbook 4.18.0-17-generic #18~18.04.1-Ubuntu SMP Fri Mar 15 15:27:12 UTC 2019 x 86_64 [12.162] Kernel command line: BOOT_IMAGE=/@/boot/vmlinuz-4.18.0-17-generic root=UUID=ac53502d-8d17-4d77-965c-30cf1c4754af ro r ootflags=subvol=@ quiet splash vt.handoff=1 [12.162] Build Date: 27 November 2018 05:27:12PM [12.162] xorg-server-hwe-18.04 2:1.20.1-3ubuntu2.1~18.04.1 (For technical support please see http://www.ubuntu.com/support) [12.162] Current version of pixman: 0.34.0 <...> [12.163] (==) Using system config directory "/usr/share/X11/xorg.conf.d" [12.185] (==) No Layout section. Using the first Screen section. [12.185] (==) No screen section available. Using defaults. [12.185] (**) |-->Screen "Default Screen Section" (0) [12.185] (**) | |-->Monitor "" [12.185] (==) No monitor specified for screen "Default Screen Section". Using a default monitor configuration. [12.185] (==) Automatically adding devices [12.185] (==) Automatically enabling devices [12.185] (==) Automatically adding GPU devices [12.185] (==) Automatically binding GPU devices [12.185] (==) Max clients allowed: 256, resource mask: 0x1f [12.186] (WW) The directory "/usr/share/fonts/X11/cyrillic" does not exist. [12.186]Entry deleted from font path. [12.186] (WW) The directory "/usr/share/fonts/X11/100dpi/" does not exist. [12.186]Entry deleted from font path. [12.186] (WW) The directory "/usr/share/fonts/X11/75dpi/" does not exist. [12.187]Entry deleted from font path. [12.187] (WW) The directory "/usr/share/fonts/X11/100dpi" does not exist. [12.187]Entry deleted from font path. [12.187] (WW) The directory "/usr/share/fonts/X11/75dpi" does not exist. [
