[plasma-nm] [Bug 385395] New: Autoconnect and save password for VPN openconnect connection
https://bugs.kde.org/show_bug.cgi?id=385395 Bug ID: 385395 Summary: Autoconnect and save password for VPN openconnect connection Product: plasma-nm Version: master Platform: Neon Packages OS: Linux Status: UNCONFIRMED Severity: major Priority: NOR Component: general Assignee: jgrul...@redhat.com Reporter: christian.ohrfa...@gmail.com Target Milestone: --- Created attachment 108183 --> https://bugs.kde.org/attachment.cgi?id=108183&action=edit plasma-nm vpn connect Related to 332058 When using the plasma-nm applet to connect to a VPN via openconnect (or right-clicking the VPN connection and clicking connect via the editor), the VPN connection always asks for a password, even when stating that the password shall be saved. Additionally, does "Connect automatically" mean that the connection is started after booting and logging into the system or when clicking the connect button (automatizing the whole connection process)? See the screenshot Thank you in advance! System: === sb_release -a No LSB modules are available. Distributor ID: neon Description:KDE neon Developer Edition Release:16.04 Codename: xenial kcmshell5 kcm_networkmanagement -v kcmshell5 5.11.90 openconnect --version OpenConnect version v7.06 Using GnuTLS. Features present: PKCS#11, RSA software token, HOTP software token, TOTP software token, System keys, DTLS NetworkManager --version 1.2.6 -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 385393] Credentials input not showing when connecting to VPN
https://bugs.kde.org/show_bug.cgi?id=385393 --- Comment #2 from Christian Ohrfandl --- Wow, thank you for the really quick reply! I actually clicked that button, but got an error message, that a connection was not possible. Subsequently, I implied this was because of the fact, that I could not provide user- and password yet. However, I found out, that I entered a whitespace character after the gateway name in the gateway field ;) After correcting this issues, the connection worked like a charme. Maybe one suggestion, though I am not confident whether this would break with possible protocol conventions: trimming the gateway field upon saving would reduce such bugs I guess (mine was induced due to a copy/paste procedure). Or is it possible to specify a gateway containing whitespaces? I guess not, but who knows ;) Anyway, thank you very much! You may decide whether to leave that bug open or close it... -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 385394] New: Missing out-of-the-box packages in order to connect to VPNs via openconnect
https://bugs.kde.org/show_bug.cgi?id=385394 Bug ID: 385394 Summary: Missing out-of-the-box packages in order to connect to VPNs via openconnect Product: neon Version: unspecified Platform: Neon Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Packages Dev Edition [unstable] Assignee: neon-b...@kde.org Reporter: christian.ohrfa...@gmail.com CC: j...@jriddell.org, neon-b...@kde.org, sit...@kde.org Target Milestone: --- Related to: 357938 When trying to connect to vpn network via openconnect kcmshell5 kcm_networkmanagement the following packages are needed in order to being able to finally connect sudo apt install openconnect network-manager-openconnect As a user, when using the VPN creation wizard that allows to create connections using openconnect, my intention is that connecting via kcm_networkmanagement is possible aswell (therefore, the mentioned packages are needed and SHALL be installed out-of-the-box) System: === sb_release -a No LSB modules are available. Distributor ID: neon Description:KDE neon Developer Edition Release:16.04 Codename: xenial -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 385393] New: Credentials input not showing when connecting to VPN
https://bugs.kde.org/show_bug.cgi?id=385393 Bug ID: 385393 Summary: Credentials input not showing when connecting to VPN Product: plasma-nm Version: master Platform: Neon Packages OS: Linux Status: UNCONFIRMED Severity: major Priority: NOR Component: general Assignee: jgrul...@redhat.com Reporter: christian.ohrfa...@gmail.com Target Milestone: --- Created attachment 108182 --> https://bugs.kde.org/attachment.cgi?id=108182&action=edit vpn connection bug When trying to connect to a vpn saved via the editor, the credentials entry window does not show username- and password field (c.f. screenshot). Additionally, the command line logs states "DBusObjectPath: invalid path """. This behaviour is unfortunate, because I can not connect to my vpn. Doing this manually on the commandline via "sudo openconnect --authgroup Alles_getunnelt --user vpn.tuwien.ac.at" works perfectly. System: === sb_release -a No LSB modules are available. Distributor ID: neon Description:KDE neon Developer Edition Release:16.04 Codename: xenial kcmshell5 kcm_networkmanagement -v kcmshell5 5.11.90 openconnect --version OpenConnect version v7.06 Using GnuTLS. Features present: PKCS#11, RSA software token, HOTP software token, TOTP software token, System keys, DTLS NetworkManager --version 1.2.6 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 385007] Wayland login not possible (nVidia GeForce GTX 760; nouveau driver)
https://bugs.kde.org/show_bug.cgi?id=385007 --- Comment #9 from Christian Ohrfandl --- Created attachment 108089 --> https://bugs.kde.org/attachment.cgi?id=108089&action=edit background -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 385007] Wayland login not possible (nVidia GeForce GTX 760; nouveau driver)
https://bugs.kde.org/show_bug.cgi?id=385007 Christian Ohrfandl changed: What|Removed |Added Resolution|FIXED |--- Status|RESOLVED|UNCONFIRMED --- Comment #8 from Christian Ohrfandl --- (In reply to David Edmundson from comment #7) > So this specific bug is fixed \o/ Well I do not quite think so, because I was only able to login once; all other times, i just could not interact with the shell at all (c.f. https://youtu.be/BXLud_xKG68). Does to log output help with identifying this behaviour? > > We need to split this bug up so we can track. I'll help with your list > > As for the rest: > >Bugs involve too bright desktop background, > Only on wayland?! That doesn't make sense..did you have some sort of gamma > correction on X before perhaps? Yes, it started out OK in the beginning (before I started recording the https://youtu.be/WB1O4ilEjsg video). But after some seconds, the background on the one screen got way brighter; some time later, the background on the other screen followed aswell. I attached an image of how the background looks under X (c.f. background); you can compare the version with the one in the video. > > >cursor only shown when hovering an application > I don't think that's reported.. Check against the product kwin and report > there. Will do > > >one application menu opens in the top left corner of the screen, > Fixed with newer Qt (5.10). OK, but it only happended for the "Lesezeichen"/"bookmarks" menu of Konsole; all other menu items worked perfektly. Is this really due to the Qt version? > > > cursor size changes when hovering the titlebar of a window, > There's a bug reported in kwin somewhere. Though I didnt' think it happened > on wyaland. So ths is a kwin issue? > > > Ctrl+Alt+Del opens logoff options but with a desaturated image on the > > second screen and with titlebar and crashes (c.f. attached picture > > logoff-options). > > the titlebar is reported elsewhere, though again I think newer Qt fixes it. Is this kwin again? What is the name of the "logoff-prompt" - as I called it - application? I could file a bug there... -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 385007] Wayland login not possible (nVidia GeForce GTX 760; nouveau driver)
https://bugs.kde.org/show_bug.cgi?id=385007 Christian Ohrfandl changed: What|Removed |Added Status|NEEDSINFO |UNCONFIRMED Resolution|WAITINGFORINFO |--- --- Comment #6 from Christian Ohrfandl --- Set to unconfirmed -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 385007] Wayland login not possible (nVidia GeForce GTX 760; nouveau driver)
https://bugs.kde.org/show_bug.cgi?id=385007 --- Comment #5 from Christian Ohrfandl --- Created attachment 108088 --> https://bugs.kde.org/attachment.cgi?id=108088&action=edit logoff-options -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 385007] Wayland login not possible (nVidia GeForce GTX 760; nouveau driver)
https://bugs.kde.org/show_bug.cgi?id=385007
--- Comment #4 from Christian Ohrfandl ---
So, back in town ;)
you can find the ouput at the end of the comment. However, I updated the system
today and was surprised that i could actually login into the wayland session
without crashing, but only once. I made two videos showing a successful login
and showing various buggy behaviour while running the session. In addition, I
made a video on a non-working login attempt. You can watch both videos on
youtube:
Successful login with various bugs: https://youtu.be/WB1O4ilEjsg
Bugs involve too bright desktop background, cursor only shown when hovering an
application, one application menu opens in the top left corner of the screen,
cursor size changes when hovering the titlebar of a window, Ctrl+Alt+Del opens
logoff options but with a desaturated image on the second screen and with
titlebar and crashes (c.f. attached picture logoff-options).
Unsuccessful login attempt: https://youtu.be/BXLud_xKG68
Here is the ouput:
cat ~/.local/share/sddm/wayland-session.log
startplasmacompositor: Starting up...
dbus-update-activation-environment: warning: error sending to systemd:
org.freedesktop.DBus.Error.Spawn.ChildExited: Process org.freedesktop.systemd1
exited with status 1
No backend specified through command line argument, trying auto resolution
_XSERVTransSocketUNIXCreateListener: ...SocketCreateListener() failed
_XSERVTransMakeAllCOTSServerListeners: server already running
glamor: EGL version 1.4 (DRI2):
/usr/lib/x86_64-linux-gnu/libexec/startplasma: 29: test: Illegal number:
Configuring Lock Action
kf5.kcoreaddons.desktopparser: Could not locate service type file
kservicetypes5/kwin-effect.desktop, tried ("/home/christian/.local/share",
"/usr/share", "/usr/local/share") and ":/kservicetypes5/kwin-effect.desktop"
kf5.kcoreaddons.desktopparser: Could not locate service type file
kservicetypes5/kwin-effect.desktop, tried ("/home/christian/.local/share",
"/usr/share", "/usr/local/share") and ":/kservicetypes5/kwin-effect.desktop"
kf5.kcoreaddons.desktopparser: Could not locate service type file
kservicetypes5/kwin-effect.desktop, tried ("/home/christian/.local/share",
"/usr/share", "/usr/local/share") and ":/kservicetypes5/kwin-effect.desktop"
kf5.kcoreaddons.desktopparser: Could not locate service type file
kservicetypes5/kwin-effect.desktop, tried ("/home/christian/.local/share",
"/usr/share", "/usr/local/share") and ":/kservicetypes5/kwin-effect.desktop"
kf5.kcoreaddons.desktopparser: Could not locate service type file
kservicetypes5/kwin-effect.desktop, tried ("/home/christian/.local/share",
"/usr/share", "/usr/local/share") and ":/kservicetypes5/kwin-effect.desktop"
kf5.kcoreaddons.desktopparser: Could not locate service type file
kservicetypes5/kwin-effect.desktop, tried ("/home/christian/.local/share",
"/usr/share", "/usr/local/share") and ":/kservicetypes5/kwin-effect.desktop"
kf5.kcoreaddons.desktopparser: Could not locate service type file
kservicetypes5/kwin-effect.desktop, tried ("/home/christian/.local/share",
"/usr/share", "/usr/local/share") and ":/kservicetypes5/kwin-effect.desktop"
kf5.kcoreaddons.desktopparser: Could not locate service type file
kservicetypes5/kwin-effect.desktop, tried ("/home/christian/.local/share",
"/usr/share", "/usr/local/share") and ":/kservicetypes5/kwin-effect.desktop"
kf5.kcoreaddons.desktopparser: Could not locate service type file
kservicetypes5/kwin-effect.desktop, tried ("/home/christian/.local/share",
"/usr/share", "/usr/local/share") and ":/kservicetypes5/kwin-effect.desktop"
kf5.kcoreaddons.desktopparser: Could not locate service type file
kservicetypes5/kwin-effect.desktop, tried ("/home/christian/.local/share",
"/usr/share", "/usr/local/share") and ":/kservicetypes5/kwin-effect.desktop"
kf5.kcoreaddons.desktopparser: Could not locate service type file
kservicetypes5/kwin-effect.desktop, tried ("/home/christian/.local/share",
"/usr/share", "/usr/local/share") and ":/kservicetypes5/kwin-effect.desktop"
kf5.kcoreaddons.desktopparser: Could not locate service type file
kservicetypes5/kwin-effect.desktop, tried ("/home/christian/.local/share",
"/usr/share", "/usr/local/share") and ":/kservicetypes5/kwin-effect.desktop"
kf5.kcoreaddons.desktopparser: Could not locate service type file
kservicetypes5/kwin-script.desktop, tried ("/home/christian/.local/share",
"/usr/share", "/usr/local/share") and ":/kservicetypes5/kwin-script.desktop"
kf5.kcoreaddons.desktop
[plasmashell] [Bug 385007] Wayland login not possible (nVidia GeForce GTX 760; nouveau driver)
https://bugs.kde.org/show_bug.cgi?id=385007 --- Comment #3 from Christian Ohrfandl --- (In reply to David Edmundson from comment #2) > ~/.local/share/sddm/wayland-session.log > > Please set this back to unconfirmed when you have this Thanky you for the information! Unfortunately, I will be able to analyse further not until Friday, 29th September. I'll keep you posted. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 385007] Wayland login not possible (nVidia GeForce GTX 760; nouveau driver)
https://bugs.kde.org/show_bug.cgi?id=385007 --- Comment #1 from Christian Ohrfandl --- Created attachment 107982 --> https://bugs.kde.org/attachment.cgi?id=107982&action=edit before login -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 385007] New: Wayland login not possible (nVidia GeForce GTX 760; nouveau driver)
https://bugs.kde.org/show_bug.cgi?id=385007 Bug ID: 385007 Summary: Wayland login not possible (nVidia GeForce GTX 760; nouveau driver) Product: plasmashell Version: 5.10.95 Platform: Neon Packages OS: Linux Status: UNCONFIRMED Severity: major Priority: NOR Component: generic-wayland Assignee: plasma-b...@kde.org Reporter: christian.ohrfa...@gmail.com Target Milestone: 1.0 Created attachment 107981 --> https://bugs.kde.org/attachment.cgi?id=107981&action=edit after login Distro: KDE Neon Developer Edition Git-Unstable from 19th August 2017. Plasma: 5.10.9 KDE Frameworks: 5.39.0 Dual-screen setup Potential referencing bugs: 380384 Description: When choosing the wayland session and logging in, only black background (on the other monitor the chosen wallpaper and some desktop icons) and a bigger cursor loads (c.f. attached picture); no interaction with system possible (tried this several times; sometimes the background on the other monitor does not even load). I have made a video I could share with you, if you want to... I have an nVidia Geforce GTX760 graphics card and installed nouveau drivers, c.f. lspci -k | grep -EA3 'VGA|3D|Display' 01:00.0 VGA compatible controller: NVIDIA Corporation GK104 [GeForce GTX 760] (rev a1) Subsystem: Micro-Star International Co., Ltd. [MSI] GK104 [GeForce GTX 760] Kernel driver in use: nouveau Kernel modules: nvidiafb, nouveau Are there any logs I may view in order to resolve the issue after turning the PC off and on again? Cheers, Christian -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 384922] Add option for per screen virtual workspace selection
https://bugs.kde.org/show_bug.cgi?id=384922 --- Comment #4 from Christian Ohrfandl --- (In reply to Christian Ohrfandl from comment #2) > (In reply to David Edmundson from comment #1) > > We can't. > > > > Virtual Desktops is part of the core X protocool, and we need compatibility > > with old apps and even other window managers. X has one setting for all > > ouputs. > > > > Sorry. > > Thank you for the quick reply! This is quite unfortunate, but I understand > your decision. On the other hand, would this be possible on wayland? (In reply to David Edmundson from comment #1) > We can't. > > Virtual Desktops is part of the core X protocool, and we need compatibility > with old apps and even other window managers. X has one setting for all > ouputs. > > Sorry. I've just checked out how other DEs deal with this issue and found out that cinnamon provides a way to only allow workspaces on the main screen, if the user chooses to enable it (c.f. attached screenshot). Would this be possible for Plasma aswell? If so, I'd really appreciate it! -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 384922] Add option for per screen virtual workspace selection
https://bugs.kde.org/show_bug.cgi?id=384922 --- Comment #3 from Christian Ohrfandl --- Created attachment 107943 --> https://bugs.kde.org/attachment.cgi?id=107943&action=edit cinnameon workspace settings -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 384897] Window snapping on multi monitor setup
https://bugs.kde.org/show_bug.cgi?id=384897 --- Comment #2 from Christian Ohrfandl --- (In reply to Martin Flöser from comment #1) > This could be rather annoying for any user who wants to move a window from > one screen to another and not tile it. > > I just tried how it works and there is several pixel wide area, so if one > moves slowly it's not a problem to trigger at all. Also there are global > keyboard shortcuts. So I don't see a need to implement this feature request. I just checked other DEs such as cinnamon and gnome; they have nearly the same behaviour implemented as Plasma 5. Still, this behaviour is very inconvenient IMO. Would it be possible for you to just integrate a setting in the system settings to turn the "magnetic" edges on and off (with off as default)? This way, users are not affected but have the possibility to turn the feature on. IMO this is a feature especially KDE should implement (your mission statement says: "Simple by Default, Powerful When Needed" ;) ). -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 384920] Main Screen setting only partially used in kscreenlocker
https://bugs.kde.org/show_bug.cgi?id=384920 Christian Ohrfandl changed: What|Removed |Added Status|RESOLVED|VERIFIED Resolution|WONTFIX |REMIND --- Comment #2 from Christian Ohrfandl --- (In reply to Martin Flöser from comment #1) > Which screen gets the active password field is pretty much random. Which would be OK, but should be consistent for a logged out- user and locked state -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 384922] Add option for per screen virtual workspace selection
https://bugs.kde.org/show_bug.cgi?id=384922 --- Comment #2 from Christian Ohrfandl --- (In reply to David Edmundson from comment #1) > We can't. > > Virtual Desktops is part of the core X protocool, and we need compatibility > with old apps and even other window managers. X has one setting for all > ouputs. > > Sorry. Thank you for the quick reply! This is quite unfortunate, but I understand your decision. On the other hand, would this be possible on wayland? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 384922] New: Add option for per screen virtual workspace selection
https://bugs.kde.org/show_bug.cgi?id=384922
Bug ID: 384922
Summary: Add option for per screen virtual workspace selection
Product: plasmashell
Version: 5.10.95
Platform: Neon Packages
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: NOR
Component: Multi-screen support
Assignee: aleix...@kde.org
Reporter: christian.ohrfa...@gmail.com
CC: plasma-b...@kde.org
Target Milestone: 1.0
Created attachment 107928
--> https://bugs.kde.org/attachment.cgi?id=107928&action=edit
Virtual Desktop Settings
Distro: KDE Neon Developer Edition Git-Unstable from 19th August 2017.
Plasma: 5.10.9
KDE Frameworks: 5.39.0
It would be great to have an option to set virtual workspaces on a per-screen
basis. For instance: workspaces 1,2,3,4 only apply to screen A and workspaces
5,6,7,8 to screen B. On a multi display setup, the current implementation is
that there are 8 different workspaces, but they are always switched on a tuple
basis, i.e. the following workspaces are "attached" to each other and always
switch togehter when a workspace is switched --> {(Mon1WS1/Mon2Ws2),
(Mon1WS3/Mon2Ws4), (Mon1WS5/Mon2Ws6), (Mon1WS7/Mon2Ws8)} (c.f. my attached
config).
Additionally, the workspace switcher application may need to have the option on
a per-screen basis aswell (c.f. System settings \ Desktop behaviour \ Screen
Edges \ Workspace-Switcher (grid)).
Of course, this should only be an option, because I see the current use case as
valid aswell
--
You are receiving this mail because:
You are watching all bug changes.
[kscreenlocker] [Bug 384920] New: Main Screen setting only partially used in kscreenlocker
https://bugs.kde.org/show_bug.cgi?id=384920 Bug ID: 384920 Summary: Main Screen setting only partially used in kscreenlocker Product: kscreenlocker Version: unspecified Platform: Neon Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: greeter Assignee: plasma-b...@kde.org Reporter: christian.ohrfa...@gmail.com CC: bhus...@gmail.com, mgraess...@kde.org Target Milestone: --- Created attachment 107927 --> https://bugs.kde.org/attachment.cgi?id=107927&action=edit System setting for default monitor/view Distro: KDE Neon Developer Edition Git-Unstable from 19th August 2017. Plasma: 5.10.9 KDE Frameworks: 5.39.0 When two (possibly multiple) monitors are attached, the setting of a main display that is not the main display chosen by either BIOS or the OS in general but rather set by the user in the system settings (see attached image), kscreensaver only uses the the chosen monitor/view, when the user is signed in and the screen gets locked (this behaviour can be tested by seing which password input field gets the focus). However, when starting the OS and when signing the user off - and therefore, the ksreenlocker is shown - kscreenlockers seems to order the monitors according to either BIOS- or default OS setting. IMO this behaviour is inconsistent. Is there a way to globally set a default monitor? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 384897] New: Window snapping on multi monitor setup
https://bugs.kde.org/show_bug.cgi?id=384897 Bug ID: 384897 Summary: Window snapping on multi monitor setup Product: plasmashell Version: 5.10.95 Platform: Neon Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Multi-screen support Assignee: aleix...@kde.org Reporter: christian.ohrfa...@gmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 Distro: KDE Neon Developer Edition Git-Unstable from 19th August 2017. Plasma: 5.10.9 KDE Frameworks: 5.39.0 Window snapping on single monitor setup works fine, but on multi monitor setup it is very hard to snap windows on the right/left screen edges (monitors left/right), because i think it is just a matter of a view pixels that decide whether a window shall be tiled on the right half on the left screen or the left half on the right screen. It would be beneficial, if there was some kind of "magnetic" border; when dragging a window via mouse, you have to overcome a certain amount of "preasure" to drag it to another screen. -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 384872] Password input field not focused
https://bugs.kde.org/show_bug.cgi?id=384872 Christian Ohrfandl changed: What|Removed |Added Resolution|INVALID |FIXED --- Comment #4 from Christian Ohrfandl --- (In reply to Martin Flöser from comment #3) > I think you can answer that question yourself: to handle situations just as > yours. If for whatever reason the main monitor is not visible it should > still be possible to unlock. Well, of course I thought about that ;-) But as I just found out, there is an explicit option to choose the main monitor/view, which would therefore support the opinion of only showing the screenlock on the main screen. Of course, this is no major "flaw" but rather a design choice. It's just my two cents... So I can set the bug to closed, if you want to... BTW (I do not know if you are the correct person for this question): I could not find KDE Neon in the platform list while reporting the bug. Considering that KDE Neon is the official distro for KDE development, it would be nice to find it in the platform list. Additionally, version 5.10.9 was not choosable aswell... In general, reporting a bug is not that easy due to the fact that "Product" shows a considerably large amount of applications; I guess not every user is able to distinguish between this bunch of applications and even if so, the sheer amount of them may make you report the bug at all. Maybe an improvement using an alternate approach for instance by classifying the products into categories (categories may be choosen by the amount of bugs for the corresponding products and/or cluster analysis). -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 384872] Password input field not focused
https://bugs.kde.org/show_bug.cgi?id=384872 --- Comment #2 from Christian Ohrfandl --- (In reply to Martin Flöser from comment #1) > works fine here. Which look'n'feel package are you using? Thank you for the quick reply! Turns out, the problem was my dual screen setup. The screenlock screen is shown on both screens, but the de facto main monitor was turned off. I have therefore written in the correct input field on the "wrong" monitor, but could not see it, because it was turned off. So, my fault. One question arises though: Why is the screenlock shown on both screens in general? For instance on Windows 10, the second (not the main) screen ist tilted black. -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 384872] New: Password input field not focused
https://bugs.kde.org/show_bug.cgi?id=384872 Bug ID: 384872 Summary: Password input field not focused Product: kscreenlocker Version: unspecified Platform: Ubuntu Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: greeter Assignee: plasma-b...@kde.org Reporter: christian.ohrfa...@gmail.com CC: bhus...@gmail.com, mgraess...@kde.org Target Milestone: --- Distro: KDE Neon Developer Edition Git-Unstable from 19th August 2017. Plasma: 5.10.9 KDE Frameworks: 5.39.0 Related bugs: 312427 and 316084 Number of users on the system: 1 At the user login (after starting the system) and at the lockscreen (if these two use cases are handled differen internally), the password field of the user is not focused and therefore, needs to be focussed manually (by clicking into the field). This circumstance is unfortunate, because it minimizes flow of user interaction. -- You are receiving this mail because: You are watching all bug changes.
