[kate] [Bug 480025] cjs, cts, mjs, mts file extensions are ignored by LSP
https://bugs.kde.org/show_bug.cgi?id=480025 --- Comment #2 from Karmo Rosental --- { "servers": { "typescript": { "use": "javascript", "highlightingModeRegex": "^TypeScript.*$", "documentLanguageId": true } } } Fix is to use this LSP server override to enable support for more TypeScript file extensions but then almost everything is underlined in React TypeScript (.tsx) files. -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 480025] cjs, cts, mjs, mts file extensions are ignored by LSP
https://bugs.kde.org/show_bug.cgi?id=480025 --- Comment #1 from Karmo Rosental --- typescript-language-server is 4.3. On another laptop I have locked typescript-language-server at 4.0 and problem does not occur. Since TSLS 4.1 issues started to happen. -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 480025] New: cjs, cts, mjs, mts file extensions are ignored by LSP
https://bugs.kde.org/show_bug.cgi?id=480025 Bug ID: 480025 Summary: cjs, cts, mjs, mts file extensions are ignored by LSP Classification: Applications Product: kate Version: 23.08.4 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: part Assignee: kwrite-bugs-n...@kde.org Reporter: karmo.rosen...@gmail.com Target Milestone: --- SUMMARY cjs, cts, mjs, mts file extensions are ignored by LSP (no ctrl + click & no typecheck). They were not ignored until bug #476942 appeared. After bugfix for #476942 js, jsx, ts & tsx files are working again but not cjs, cts, mjs, mts. I'm using default LSP config. STEPS TO REPRODUCE 1. Have project with valid cjs, cts, mjs or mts file 2. Open it with Kate OBSERVED RESULT There is only syntax highlighting. No ctrl + click and no typecheck (for cts, mts). EXPECTED RESULT cjs, mjs should be loaded like js and cts, mts loaded like ts. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: Manjaro with latest updates (available in About System) KDE Plasma Version: 5.27.10 KDE Frameworks Version: 5.113.0 Qt Version: 5.15.12 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-plasma] [Bug 448750] SVGs are sometimes corrupted on upgrade until SVG cache is cleared
https://bugs.kde.org/show_bug.cgi?id=448750 Karmo Rosental changed: What|Removed |Added CC|karmo.rosen...@gmail.com| -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 476942] TypeScript ctrl+click navigation broken since typescript-language-server 4.1
https://bugs.kde.org/show_bug.cgi?id=476942 --- Comment #1 from Karmo Rosental --- Looks like entire TypeScript support is broken not only navigation (type tooltips, autocomplete etc.). -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 476942] New: TypeScript ctrl+click navigation broken since typescript-language-server 4.1
https://bugs.kde.org/show_bug.cgi?id=476942 Bug ID: 476942 Summary: TypeScript ctrl+click navigation broken since typescript-language-server 4.1 Classification: Applications Product: kate Version: 23.08.3 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: part Assignee: kwrite-bugs-n...@kde.org Reporter: karmo.rosen...@gmail.com Target Milestone: --- SUMMARY TypeScript navigation does not work with typescript-language-server 4.1 but works with typescript-language-server 4.0. STEPS TO REPRODUCE 1. Open a valid TypeScript file that has imports or functions 2. Try to control + click into function OBSERVED RESULT Nothing happens, function does not get even underlined EXPECTED RESULT Editor navigates to clicked function SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: Manjaro with latest updates (available in About System) KDE Plasma Version: 5.27.9 KDE Frameworks Version: 5.111.0 Qt Version: 5.15.11 -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 468130] Kate adds double dots before method name when using autocomplete (TypeScript)
https://bugs.kde.org/show_bug.cgi?id=468130 Karmo Rosental changed: What|Removed |Added Latest Commit|1c0ad3b4fe8b85f55273ff255ea | |cc92a3d01bf10 | -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 468130] Kate adds double dots before method name when using autocomplete (TypeScript)
https://bugs.kde.org/show_bug.cgi?id=468130 Karmo Rosental changed: What|Removed |Added Version|22.12.3 |23.04.3 Version Fixed In|23.04 | -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 468130] Kate adds double dots before method name when using autocomplete (TypeScript)
https://bugs.kde.org/show_bug.cgi?id=468130 Karmo Rosental changed: What|Removed |Added Resolution|FIXED |--- Ever confirmed|0 |1 Status|RESOLVED|REOPENED --- Comment #3 from Karmo Rosental --- Same issue is back with recent updates. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 468117] Application Launcher don't have hover effect anymore since 5.27
https://bugs.kde.org/show_bug.cgi?id=468117 Karmo Rosental changed: What|Removed |Added Resolution|WAITINGFORINFO |FIXED Status|NEEDSINFO |RESOLVED --- Comment #2 from Karmo Rosental --- (In reply to Nate Graham from comment #1) > Run these commands in a terminal window: > > rm ~/.cache/plasma* > plasmashell --replace > > Is it fixed now? Yes these commands helped me. Thank you Nate! Maybe distros should also remove that folder when they do Plasma upgrades to avoid weird bugs. -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 468130] New: Kate adds double dots before method name when using autocomplete (TypeScript)
https://bugs.kde.org/show_bug.cgi?id=468130 Bug ID: 468130 Summary: Kate adds double dots before method name when using autocomplete (TypeScript) Classification: Applications Product: kate Version: 22.12.3 Platform: Manjaro OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: part Assignee: kwrite-bugs-n...@kde.org Reporter: karmo.rosen...@gmail.com Target Milestone: --- SUMMARY Kate adds double dots before method name when using autocomplete (TypeScript Language Server). Started to happen when I did bigger update to KDE components today (Plasma 5.27 etc). rust-analyzer for Rust language doesn't add double dots before methods. STEPS TO REPRODUCE 1. Install TypeScript Language Server 2. Open or create a .ts file 3. Try to write inside: const n = 1; n.toString and press enter to autocomplete. OBSERVED RESULT Code looks like n..toString() EXPECTED RESULT Code looks like n.toString() -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 468117] New: Application Launcher don't have hover effect anymore since 5.27
https://bugs.kde.org/show_bug.cgi?id=468117 Bug ID: 468117 Summary: Application Launcher don't have hover effect anymore since 5.27 Classification: Plasma Product: plasmashell Version: 5.27.3 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Application Launcher (Kickoff) Assignee: plasma-b...@kde.org Reporter: karmo.rosen...@gmail.com CC: mikel5...@gmail.com, noaha...@gmail.com Target Milestone: 1.0 SUMMARY Application Launcher has no hover effects after upgrading from 5.26 to 5.27. Problem looks exactly same as reported at https://www.reddit.com/r/kde/comments/z3dawa/plasma_application_launcher_wont_highlight/. None of the suggestions in that thread helped me. I tried various Plasma styles and both Breeze and Breath (both light and dark) are affected by this problem. Air and Oxygen styles have hover effect. -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 462846] Lock screen is frozen for about 15 seconds after screen wakes up from energy saving
https://bugs.kde.org/show_bug.cgi?id=462846 Karmo Rosental changed: What|Removed |Added Resolution|WAITINGFORINFO |--- Status|NEEDSINFO |REPORTED --- Comment #3 from Karmo Rosental --- "Crashed processes viewer" aka DrKonqi does not show these freezes. -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 462846] New: Login screen is frozen for about 15 seconds after screen wakes up from energy saving
https://bugs.kde.org/show_bug.cgi?id=462846 Bug ID: 462846 Summary: Login screen is frozen for about 15 seconds after screen wakes up from energy saving Classification: Plasma Product: KScreen Version: 5.26.4 Platform: Manjaro OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: common Assignee: kscreen-bugs-n...@kde.org Reporter: karmo.rosen...@gmail.com Target Milestone: --- Created attachment 154474 --> https://bugs.kde.org/attachment.cgi?id=154474=edit system log export SUMMARY Login screen is frozen for about 15 seconds after screen wakes up from energy saving. STEPS TO REPRODUCE 1. Have screen energy saving enabled 2. Let screen to switch off after inactivity 3. Wake up screen by moving mouse and try to enter your password 4. You can move mouse around but text input and buttons are frozen for around 15 seconds. 5. After 15 seconds you can finally enter password and unlock OBSERVED RESULT EXPECTED RESULT I can input password right away after screen wakes up SOFTWARE/OS VERSIONS Linux/KDE Plasma KDE Plasma Version: 5.26.4 KDE Frameworks Version: 5.100.0 Qt Version: 5.15.7 ADDITIONAL INFORMATION X session AMD 6800 XT GPU -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 456620] Application launcher opens on wrong monitor
https://bugs.kde.org/show_bug.cgi?id=456620 --- Comment #4 from Karmo Rosental --- I'm using X. I will test once Manjaro has new Plasma version. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 456620] Application launcher opens on wrong monitor
https://bugs.kde.org/show_bug.cgi?id=456620 --- Comment #1 from Karmo Rosental --- Issue is probably more widespread and not only limited to application launcher since also panel right click context menu opens on wrong monitor. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 456620] New: Application launcher opens on wrong monitor
https://bugs.kde.org/show_bug.cgi?id=456620 Bug ID: 456620 Summary: Application launcher opens on wrong monitor Product: plasmashell Version: 5.24.5 Platform: Manjaro OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Application Launcher (Kickoff) Assignee: plasma-b...@kde.org Reporter: karmo.rosen...@gmail.com CC: mikel5...@gmail.com, noaha...@gmail.com Target Milestone: 1.0 SUMMARY Application menu opens on the bottom right corner of left monitor when right monitor is main monitor. It works after login but bug appears when main monitor goes to sleep and wakes up again. Created another bug report as all the previous onces are closed but issue is still present. STEPS TO REPRODUCE 1. Have 2 monitors side by side 2. Set right monitor as main monitor so it will have a panel 3. Turn off or sleep main monitor 4. Wake up or turn on main monitor OBSERVED RESULT Application menu opens on bottom right corner of left monitor. EXPECTED RESULT Application menu opens on right monitor at the correct place relative to launcher icon. Launcher menu should not care about other monitors than the one it's icon is currently placed on and open relative to the icon. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: 5.24.5 KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 442378] Magic Lamp animations switching their “focal point” after connecting a second screen
https://bugs.kde.org/show_bug.cgi?id=442378 Karmo Rosental changed: What|Removed |Added Version|5.23.0 |5.24.0 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 442378] Magic Lamp animations switching their “focal point” after connecting a second screen
https://bugs.kde.org/show_bug.cgi?id=442378 Karmo Rosental changed: What|Removed |Added Resolution|WAITINGFORINFO |--- Status|NEEDSINFO |REPORTED --- Comment #8 from Karmo Rosental --- Happens to me only when the task manager is on the left side of the 2nd or 3rd screen (middle screen or right screen depending on the setup). When task manager is on the top, bottom or right side of the screen then animation looks correct no matter on which screen it is situated. Affects also Squash minimize effect although it was a bit difficult to notice at first. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 442378] Magic Lamp animations switching their “focal point” after connecting a second screen
https://bugs.kde.org/show_bug.cgi?id=442378 --- Comment #6 from Karmo Rosental --- I'm using Plasma 5.24 in Manjaro. Effect seems to work fine when the task manager is on the leftmost screen but becomes broken when the taskbar is on any other screen. Basically that has been described in the initial post of this bug report. If I connect external display that is set as default display then taskbar moves to the external display (that is very nice!). Laptop becomes leftmost screen without any task manager and now it seems that magic lamp still wants to minimize to the laptop screen and creates a broken animation. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 442378] Window-minimisation animations switching their “focal point” after connecting a second screen
https://bugs.kde.org/show_bug.cgi?id=442378 --- Comment #4 from Karmo Rosental --- Squash minimize effect has no issues. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 442378] Window-minimisation animations switching their “focal point” after connecting a second screen
https://bugs.kde.org/show_bug.cgi?id=442378 --- Comment #3 from Karmo Rosental --- I'm using X11 and no Qt scaling. I was testing it with 2 monitors and also with only laptop screen and I never got clean magic lamp anymore. It always had different glitches depending on number of screens and position of the taskbar. Must be fresh bug since I remember it was always working correctly. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 442378] Window-minimisation animations switching their “focal point” after connecting a second screen
https://bugs.kde.org/show_bug.cgi?id=442378 Karmo Rosental changed: What|Removed |Added CC||karmo.rosen...@gmail.com --- Comment #1 from Karmo Rosental --- I believe my issue is related to this issue. My setup is quite simple. I have 3 monitors. When the left screen is a default screen with a taskbar on the left side then magic lamp works always correctly. Problem appears when I set my middle screen as default (that makes taskbar also to move to the middle monitor). Then magic lamp has a weird effect. Part of the window is pulled to the correct place but another part of the window is pulled all the way to the right. There's nothing on the right side of the middle screen or on the right screen. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 419295] Skype's and Slack's system tray icons become invisible after updating Plasma
https://bugs.kde.org/show_bug.cgi?id=419295 Karmo Rosental changed: What|Removed |Added Resolution|WAITINGFORINFO |FIXED Status|NEEDSINFO |RESOLVED --- Comment #4 from Karmo Rosental --- I have not noticed this issue anymore in last weeks. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-plasma] [Bug 419295] Skype's and Slack's system tray icons become invisible after updating Plasma
https://bugs.kde.org/show_bug.cgi?id=419295 --- Comment #2 from Karmo Rosental --- After every restart these icons are again invisible. It seems to affect not only Skype and Slack but every app that is not part of KDE. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-plasma] [Bug 419295] Skype's and Slack's system tray icons become invisible after updating Plasma
https://bugs.kde.org/show_bug.cgi?id=419295 --- Comment #1 from Karmo Rosental --- I had to remove and add again System Tray widget. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-plasma] [Bug 419295] New: Skype's and Slack's system tray icons become invisible after updating Plasma
https://bugs.kde.org/show_bug.cgi?id=419295 Bug ID: 419295 Summary: Skype's and Slack's system tray icons become invisible after updating Plasma Product: frameworks-plasma Version: 5.68.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: libplasma Assignee: notm...@gmail.com Reporter: karmo.rosen...@gmail.com CC: plasma-b...@kde.org Target Milestone: --- SUMMARY After installing updates from Manjaro's official repositories Skype's and Slack's system tray icons become invisible. STEPS TO REPRODUCE 1. Have Skype or Slack installed 2. Install KDE updates 3. Restart computer 4. Open Skype or Slack OBSERVED RESULT Skype's and Slack's system tray icons are invisible. EXPECTED RESULT Skype's and Slack's system tray icons should be their logos. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Manjaro KDE with current latest updates KDE Plasma Version: 5.18 KDE Frameworks Version: 5.68 Qt Version: 5.14.1 ADDITIONAL INFORMATION Reinstalling of Skype or Slack doesn't fix it. -- You are receiving this mail because: You are watching all bug changes.
[kompare] [Bug 415800] New: Default colors in Kompare are not intuitive
https://bugs.kde.org/show_bug.cgi?id=415800 Bug ID: 415800 Summary: Default colors in Kompare are not intuitive Product: kompare Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: viewpart Assignee: kompare-de...@kde.org Reporter: karmo.rosen...@gmail.com Target Milestone: --- SUMMARY Default colors in Kompare are not intuitive. STEPS TO REPRODUCE 1. Install Kompare for the first time 2. Open Kompare 3. Click Appearance OBSERVED RESULT - Removed color is green - Changed color is red - Added color is blue EXPECTED RESULT - Removed color is red - Changed color is blue - Added color is green SOFTWARE/OS VERSIONS It has been like this in various Linux distros for years. -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 398240] Files appear twice in project view for some git projects
https://bugs.kde.org/show_bug.cgi?id=398240 Karmo Rosental changed: What|Removed |Added CC||karmo.rosen...@gmail.com --- Comment #2 from Karmo Rosental --- I have a same issue with Kate 18.08.2 in Manjaro Linux. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-syntax-highlighting] [Bug 384716] TypeScript Highlighting
https://bugs.kde.org/show_bug.cgi?id=384716 Karmo Rosental <karmo.rosen...@gmail.com> changed: What|Removed |Added CC||karmo.rosen...@gmail.com --- Comment #1 from Karmo Rosental <karmo.rosen...@gmail.com> --- I wish to see TypeScript syntax support in ksyntaxhighlighting too. -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 372990] Wi-Fi password doesn't save in connection editor
https://bugs.kde.org/show_bug.cgi?id=372990 --- Comment #2 from Karmo Rosental <karmo.rosen...@gmail.com> --- Ryan P.C. McQuen thanks for this tip. Perhaps the UX can be a bit better there. I had two icons behind each other in default window size. Why password only saves when I save it for all users? If I save it only for my user then when I reopen this dialog right away the password field is blank. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 374829] New: Cannnot refresh thumbnails in Dolphin by pressing F5
https://bugs.kde.org/show_bug.cgi?id=374829 Bug ID: 374829 Summary: Cannnot refresh thumbnails in Dolphin by pressing F5 Product: dolphin Version: unspecified Platform: Kubuntu Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: view-engine: general Assignee: dolphin-bugs-n...@kde.org Reporter: karmo.rosen...@gmail.com Target Milestone: --- Dolphin 16.04 in Kubuntu Linux does not refresh thumbnails by pressing F5. I had two images A.png and B.png. I deleted B.png and renamed A.png to B.png. Now new image B.png shows thumbnail of deleted image B.png. I deleted ~/.thumbnails and ~/.kde/cache-mypc/icon-cache.kcache but this didn't help. There is very old bug report of same issue https://bugs.kde.org/show_bug.cgi?id=288691 that is in resolved status. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 373220] Dolphin 16.04.3 detects all binary files as shared libraries
https://bugs.kde.org/show_bug.cgi?id=373220 --- Comment #4 from Karmo Rosental <karmo.rosen...@gmail.com> --- $ xdg-mime query filetype /bin/nano application/x-sharedlib $ xdg-mime query filetype lmms application/x-sharedlib All binaries are application/x-sharedlib. $ dpkg -l | grep shared-mime-info ii shared-mime-info1.7-1 -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 373220] Dolphin 16.04.3 detects all binary files as shared libraries
https://bugs.kde.org/show_bug.cgi?id=373220 --- Comment #2 from Karmo Rosental <karmo.rosen...@gmail.com> --- Kubuntu 16.10. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 373220] New: Dolphin 16.04.3 detects all binary files as shared libraries
https://bugs.kde.org/show_bug.cgi?id=373220 Bug ID: 373220 Summary: Dolphin 16.04.3 detects all binary files as shared libraries Product: dolphin Version: unspecified Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: view-engine: general Assignee: dolphin-bugs-n...@kde.org Reporter: karmo.rosen...@gmail.com Target Milestone: --- Dolphin 16.04.3 detects all binary files as shared libraries and cannot execute them by just clicking on them like version or two ago. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 369886] Screen goes infinitively brigher without moving cursor
https://bugs.kde.org/show_bug.cgi?id=369886 Karmo Rosental <karmo.rosen...@gmail.com> changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #3 from Karmo Rosental <karmo.rosen...@gmail.com> --- In final release of Kubuntu 16.10 this does not happen anymore. -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 372990] New: Wi-Fi password doesn't save in connection editor
https://bugs.kde.org/show_bug.cgi?id=372990 Bug ID: 372990 Summary: Wi-Fi password doesn't save in connection editor Product: plasma-nm Version: 5.5.5 Platform: Kubuntu Packages OS: Linux Status: UNCONFIRMED Severity: major Priority: NOR Component: editor Assignee: lu...@kde.org Reporter: karmo.rosen...@gmail.com CC: jgrul...@redhat.com Target Milestone: --- 1. From network system tray icon menu choose "Configure Network Connections...". 2. Select a wireless connection and click "Edit". 3. KDE shows warning popup that "No agents were available for this request". 4. Go to "Wi-Fi Security" tab, enter password and click OK. 5. Go back to step 2 and warning shows up again and password field is empty! In general configuration I have selected both: + Automatically connecto to this network when it is available + All users may connect to this network KWallet is disabled. I have had this problem already for several Kubuntu versions. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 369886] Screen goes infinitively brigher without moving cursor
https://bugs.kde.org/show_bug.cgi?id=369886 --- Comment #2 from Karmo Rosental <karmo.rosen...@gmail.com> --- This happens already in live session before install. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 369886] New: Screen goes infinitively brigher without moving cursor
https://bugs.kde.org/show_bug.cgi?id=369886 Bug ID: 369886 Summary: Screen goes infinitively brigher without moving cursor Product: plasmashell Version: 5.7.5 Platform: Other OS: Linux Status: UNCONFIRMED Severity: grave Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: karmo.rosen...@gmail.com CC: bhus...@gmail.com, plasma-b...@kde.org Installed Kubuntu 16.10 Beta 2 that comes with Plasma 5.7.5 and there screen goes infinitively brigher if there is no moving things on screen e.g. cursor. Happens with both Intel and Nvidia cards and their latest drivers. Reproducible: Always Steps to Reproduce: Already login screen has this problem. -- You are receiving this mail because: You are watching all bug changes.