[opensuse] login problem on :0 console
Hello: This occurs in openSUSE 13.2 with KDE 4.14.3 and corresponding KDM login manager. If I login from a remote host through ssh and start vncserver on display :1, I can't login at the :0 console. The login process starts but drops me back to the login screen. How can I fix this? Thanks, Istvan -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Istvan Gabor írta:
Hello:
This occurs in openSUSE 13.2 with KDE 4.14.3 and corresponding KDM login manager.
If I login from a remote host through ssh and start vncserver on display :1, I can't login at the :0 console. The login process starts but drops me back to the login screen.
How can I fix this?
I have updated the system to 3.16.7-21-desktop #1 SMP PREEMPT Tue Apr 14 07:11:37 UTC 2015 (93c1539) i686 i686 i386 GNU/Linux KDM login manager: kdm-branding-openSUSE-13.2-3.6.1.noarch kdm-4.11.17-21.5.i586 KDE: kdebase4-workspace-libs-4.11.17-21.5.i586 kdebase4-workspace-ksysguardd-4.11.17-21.5.i586 kdebase4-workspace-4.11.17-21.5.i586 kdebase4-workspace-liboxygenstyle-4.11.17-21.5.i586 kdebase4-session-4.12-3.1.2.noarch kdebase4-workspace-addons-4.11.17-21.5.i586 kdebase4-workspace-branding-openSUSE-13.2-4.2.8.i586 kdebase4-runtime-branding-openSUSE-13.2-4.2.8.i586 kdebase4-openSUSE-13.2-4.2.8.i586 kdebase4-runtime-14.12.3-16.6.i586 kdebase4-nsplugin-14.12.3-16.5.i586 python-kdebase4-4.11.17-21.5.i586 kdebase4-libkonq-14.12.3-16.5.i586 The problem still exist, if vncserver is running, I can't login at console:0. No one has any idea? I find this a serious issue. Thanks, Istvan -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Istvan Gabor írta:
Istvan Gabor írta:
Hello:
This occurs in openSUSE 13.2 with KDE 4.14.3 and corresponding KDM login manager.
If I login from a remote host through ssh and start vncserver on display :1, I can't login at the :0 console. The login process starts but drops me back to the login screen.
How can I fix this?
I have updated the system to 3.16.7-21-desktop #1 SMP PREEMPT Tue Apr 14 07:11:37 UTC 2015 (93c1539) i686 i686 i386 GNU/Linux
KDM login manager:
kdm-branding-openSUSE-13.2-3.6.1.noarch kdm-4.11.17-21.5.i586
KDE:
kdebase4-workspace-libs-4.11.17-21.5.i586 kdebase4-workspace-ksysguardd-4.11.17-21.5.i586 kdebase4-workspace-4.11.17-21.5.i586 kdebase4-workspace-liboxygenstyle-4.11.17-21.5.i586 kdebase4-session-4.12-3.1.2.noarch kdebase4-workspace-addons-4.11.17-21.5.i586 kdebase4-workspace-branding-openSUSE-13.2-4.2.8.i586 kdebase4-runtime-branding-openSUSE-13.2-4.2.8.i586 kdebase4-openSUSE-13.2-4.2.8.i586 kdebase4-runtime-14.12.3-16.6.i586 kdebase4-nsplugin-14.12.3-16.5.i586 python-kdebase4-4.11.17-21.5.i586 kdebase4-libkonq-14.12.3-16.5.i586
The problem still exist, if vncserver is running, I can't login at console:0. No one has any idea? I find this a serious issue.
I experienced with it. The problem only occurs if both vncserver session and console session is set to KDE4 desktop. If both any of them or both are set to KDE3 desktop, the problem does not show. Is this a KDE4 feature too? How can I fix this? I use default xstartup setup, .vnc/xstartup contains: #!/bin/sh # Uncomment the following two lines for normal desktop: unset SESSION_MANAGER exec /etc/X11/xinit/xinitrc xrdb $HOME/.Xresources [ -x /etc/vnc/xstartup ] && exec /etc/vnc/xstartup [ -r $HOME/.Xresources ] && xrdb $HOME/.Xresources # xsetroot -solid grey # xterm -geometry 80x24+10+10 -ls -title "$VNCDESKTOP Desktop" & # twm & #startx & startkde & Would appreciate any help. Istvan -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Istvan Gabor írta:
Istvan Gabor írta:
Istvan Gabor írta:
Hello:
This occurs in openSUSE 13.2 with KDE 4.14.3 and corresponding KDM login manager.
If I login from a remote host through ssh and start vncserver on display :1, I can't login at the :0 console. The login process starts but drops me back to the login screen.
How can I fix this?
I have updated the system to 3.16.7-21-desktop #1 SMP PREEMPT Tue Apr 14 07:11:37 UTC 2015 (93c1539) i686 i686 i386 GNU/Linux
KDM login manager:
kdm-branding-openSUSE-13.2-3.6.1.noarch kdm-4.11.17-21.5.i586
KDE:
kdebase4-workspace-libs-4.11.17-21.5.i586 kdebase4-workspace-ksysguardd-4.11.17-21.5.i586 kdebase4-workspace-4.11.17-21.5.i586 kdebase4-workspace-liboxygenstyle-4.11.17-21.5.i586 kdebase4-session-4.12-3.1.2.noarch kdebase4-workspace-addons-4.11.17-21.5.i586 kdebase4-workspace-branding-openSUSE-13.2-4.2.8.i586 kdebase4-runtime-branding-openSUSE-13.2-4.2.8.i586 kdebase4-openSUSE-13.2-4.2.8.i586 kdebase4-runtime-14.12.3-16.6.i586 kdebase4-nsplugin-14.12.3-16.5.i586 python-kdebase4-4.11.17-21.5.i586 kdebase4-libkonq-14.12.3-16.5.i586
The problem still exist, if vncserver is running, I can't login at console:0. No one has any idea? I find this a serious issue.
I experienced with it. The problem only occurs if both vncserver session and console session is set to KDE4 desktop. If both any of them or both are set to KDE3 desktop, the problem does not show.
Is this a KDE4 feature too?
How can I fix this?
I use default xstartup setup, .vnc/xstartup contains:
#!/bin/sh
# Uncomment the following two lines for normal desktop: unset SESSION_MANAGER exec /etc/X11/xinit/xinitrc xrdb $HOME/.Xresources
[ -x /etc/vnc/xstartup ] && exec /etc/vnc/xstartup [ -r $HOME/.Xresources ] && xrdb $HOME/.Xresources
# xsetroot -solid grey # xterm -geometry 80x24+10+10 -ls -title "$VNCDESKTOP Desktop" & # twm &
#startx & startkde &
Sorry, I mixed up xstarup files, the xstartup used contains: --------- #!/bin/sh unset SESSION_MANAGER unset DBUS_SESSION_BUS_ADDRESS OS=`uname -s` if [ $OS = 'Linux' ]; then case "$WINDOWMANAGER" in *gnome*) if [ -e /etc/SuSE-release ]; then PATH=$PATH:/opt/gnome/bin export PATH fi ;; esac fi if [ -x /etc/X11/xinit/xinitrc ]; then exec /etc/X11/xinit/xinitrc fi if [ -f /etc/X11/xinit/xinitrc ]; then exec sh /etc/X11/xinit/xinitrc fi [ -r $HOME/.Xresources ] && xrdb $HOME/.Xresources xsetroot -solid grey xterm -geometry 80x24+10+10 -ls -title "$VNCDESKTOP Desktop" & twm & -------- It defines twm but KDE4 session runs on the vnc server. Istvan -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
В Sun, 10 May 2015 16:51:02 +0200 (CEST)
Istvan Gabor
Istvan Gabor írta:
Istvan Gabor írta:
Istvan Gabor írta:
Hello:
This occurs in openSUSE 13.2 with KDE 4.14.3 and corresponding KDM login manager.
If I login from a remote host through ssh and start vncserver on display :1, I can't login at the :0 console. The login process starts but drops me back to the login screen.
How can I fix this?
I have updated the system to 3.16.7-21-desktop #1 SMP PREEMPT Tue Apr 14 07:11:37 UTC 2015 (93c1539) i686 i686 i386 GNU/Linux
KDM login manager:
kdm-branding-openSUSE-13.2-3.6.1.noarch kdm-4.11.17-21.5.i586
KDE:
kdebase4-workspace-libs-4.11.17-21.5.i586 kdebase4-workspace-ksysguardd-4.11.17-21.5.i586 kdebase4-workspace-4.11.17-21.5.i586 kdebase4-workspace-liboxygenstyle-4.11.17-21.5.i586 kdebase4-session-4.12-3.1.2.noarch kdebase4-workspace-addons-4.11.17-21.5.i586 kdebase4-workspace-branding-openSUSE-13.2-4.2.8.i586 kdebase4-runtime-branding-openSUSE-13.2-4.2.8.i586 kdebase4-openSUSE-13.2-4.2.8.i586 kdebase4-runtime-14.12.3-16.6.i586 kdebase4-nsplugin-14.12.3-16.5.i586 python-kdebase4-4.11.17-21.5.i586 kdebase4-libkonq-14.12.3-16.5.i586
The problem still exist, if vncserver is running, I can't login at console:0. No one has any idea? I find this a serious issue.
I experienced with it. The problem only occurs if both vncserver session and console session is set to KDE4 desktop. If both any of them or both are set to KDE3 desktop, the problem does not show.
IIRC GDM does not allow two simultaneous sessions by the same user. May be KDE4 went the same route? Are you using GDM or KDM? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Andrei Borzenkov írta:
В Sun, 10 May 2015 16:51:02 +0200 (CEST) Istvan Gabor
пишет: Istvan Gabor írta:
Istvan Gabor írta:
Istvan Gabor írta:
Hello:
This occurs in openSUSE 13.2 with KDE 4.14.3 and corresponding KDM login manager.
If I login from a remote host through ssh and start vncserver on display :1, I can't login at the :0 console. The login process starts but drops me back to the login screen.
How can I fix this?
I have updated the system to 3.16.7-21-desktop #1 SMP PREEMPT Tue Apr 14 07:11:37 UTC 2015 (93c1539) i686 i686 i386 GNU/Linux
KDM login manager:
kdm-branding-openSUSE-13.2-3.6.1.noarch kdm-4.11.17-21.5.i586
KDE:
kdebase4-workspace-libs-4.11.17-21.5.i586 kdebase4-workspace-ksysguardd-4.11.17-21.5.i586 kdebase4-workspace-4.11.17-21.5.i586 kdebase4-workspace-liboxygenstyle-4.11.17-21.5.i586 kdebase4-session-4.12-3.1.2.noarch kdebase4-workspace-addons-4.11.17-21.5.i586 kdebase4-workspace-branding-openSUSE-13.2-4.2.8.i586 kdebase4-runtime-branding-openSUSE-13.2-4.2.8.i586 kdebase4-openSUSE-13.2-4.2.8.i586 kdebase4-runtime-14.12.3-16.6.i586 kdebase4-nsplugin-14.12.3-16.5.i586 python-kdebase4-4.11.17-21.5.i586 kdebase4-libkonq-14.12.3-16.5.i586
The problem still exist, if vncserver is running, I can't login at console:0. No one has any idea? I find this a serious issue.
I experienced with it. The problem only occurs if both vncserver session and console session is set to KDE4 desktop. If both any of them or both are set to KDE3 desktop, the problem does not show.
IIRC GDM does not allow two simultaneous sessions by the same user. May be KDE4 went the same route?
openSUSE 13.2 with up-to-date KDE4 from update repo. I use KDE4 kdm, the problem occurs when I have an vnc KDE4 session running and want to login at console to KDE4. Now I will check if I can open two parallel KDE4 vnc session. Istvan Istvan -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Istvan Gabor írta:
Andrei Borzenkov írta:
В Sun, 10 May 2015 16:51:02 +0200 (CEST) Istvan Gabor
пишет: Istvan Gabor írta:
Istvan Gabor írta:
Istvan Gabor írta:
Hello:
This occurs in openSUSE 13.2 with KDE 4.14.3 and corresponding KDM login manager.
If I login from a remote host through ssh and start vncserver on display :1, I can't login at the :0 console. The login process starts but drops me back to the login screen.
How can I fix this?
I have updated the system to 3.16.7-21-desktop #1 SMP PREEMPT Tue Apr 14 07:11:37 UTC 2015 (93c1539) i686 i686 i386 GNU/Linux
KDM login manager:
kdm-branding-openSUSE-13.2-3.6.1.noarch kdm-4.11.17-21.5.i586
KDE:
kdebase4-workspace-libs-4.11.17-21.5.i586 kdebase4-workspace-ksysguardd-4.11.17-21.5.i586 kdebase4-workspace-4.11.17-21.5.i586 kdebase4-workspace-liboxygenstyle-4.11.17-21.5.i586 kdebase4-session-4.12-3.1.2.noarch kdebase4-workspace-addons-4.11.17-21.5.i586 kdebase4-workspace-branding-openSUSE-13.2-4.2.8.i586 kdebase4-runtime-branding-openSUSE-13.2-4.2.8.i586 kdebase4-openSUSE-13.2-4.2.8.i586 kdebase4-runtime-14.12.3-16.6.i586 kdebase4-nsplugin-14.12.3-16.5.i586 python-kdebase4-4.11.17-21.5.i586 kdebase4-libkonq-14.12.3-16.5.i586
The problem still exist, if vncserver is running, I can't login at console:0. No one has any idea? I find this a serious issue.
I experienced with it. The problem only occurs if both vncserver session and console session is set to KDE4 desktop. If both any of them or both are set to KDE3 desktop, the problem does not show.
IIRC GDM does not allow two simultaneous sessions by the same user. May be KDE4 went the same route?
openSUSE 13.2 with up-to-date KDE4 from update repo. I use KDE4 kdm, the problem occurs when I have an vnc KDE4 session running and want to login at console to KDE4.
Now I will check if I can open two parallel KDE4 vnc session.
I checked. I can start and login to two parallel KDE4 vnc session, sessions started as:
vncserver :1 -localhost
New '......:1 (........)' desktop is .......:1 Starting applications specified in /home/......./.vnc/xstartup Log file is /home/......./.vnc/........:1.log
vncserver :2 -localhost
New '....:2 (lxuser)' desktop is .....:2 Starting applications specified in /home/.../.vnc/xstartup Log file is /home/...../.vnc/....:2.log But I cannot login from console (terminal 7) to KDE4. The login manager accepts the password, starts loggin in, the progress windows appears, then it drops back to kdm login screen. Is this for me only? Thanks, Istvan -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hello Istvan, Apparently yes. I have no problems with two/three vnc sessions (all started over SSH) and a login with the same user on the actual display :0. However I'm on 13.1 and the version of KDM here is 4.11.12-123.1. KDM should to writes all client errors in ~/.xsession-errors (according to /usr/share/kde4/config/kdm/kdmrc). Do you see any clues regarding this behaviour in this file? Regards, I. Petrov On 05/10/2015 10:44 PM, Istvan Gabor wrote:
Istvan Gabor írta:
Andrei Borzenkov írta:
В Sun, 10 May 2015 16:51:02 +0200 (CEST) Istvan Gabor
пишет: Istvan Gabor írta:
Istvan Gabor írta:
Istvan Gabor írta: > Hello: > > This occurs in openSUSE 13.2 with KDE 4.14.3 and > corresponding KDM login manager. > > If I login from a remote host through ssh and start > vncserver on display :1, I can't login at the :0 > console. The login process starts but drops me back to > the login screen. > > How can I fix this?
I have updated the system to 3.16.7-21-desktop #1 SMP PREEMPT Tue Apr 14 07:11:37 UTC 2015 (93c1539) i686 i686 i386 GNU/Linux
KDM login manager:
kdm-branding-openSUSE-13.2-3.6.1.noarch kdm-4.11.17-21.5.i586
KDE:
kdebase4-workspace-libs-4.11.17-21.5.i586 kdebase4-workspace-ksysguardd-4.11.17-21.5.i586 kdebase4-workspace-4.11.17-21.5.i586 kdebase4-workspace-liboxygenstyle-4.11.17-21.5.i586 kdebase4-session-4.12-3.1.2.noarch kdebase4-workspace-addons-4.11.17-21.5.i586 kdebase4-workspace-branding-openSUSE-13.2-4.2.8.i586 kdebase4-runtime-branding-openSUSE-13.2-4.2.8.i586 kdebase4-openSUSE-13.2-4.2.8.i586 kdebase4-runtime-14.12.3-16.6.i586 kdebase4-nsplugin-14.12.3-16.5.i586 python-kdebase4-4.11.17-21.5.i586 kdebase4-libkonq-14.12.3-16.5.i586
The problem still exist, if vncserver is running, I can't login at console:0. No one has any idea? I find this a serious issue.
I experienced with it. The problem only occurs if both vncserver session and console session is set to KDE4 desktop. If both any of them or both are set to KDE3 desktop, the problem does not show.
IIRC GDM does not allow two simultaneous sessions by the same user. May be KDE4 went the same route?
openSUSE 13.2 with up-to-date KDE4 from update repo. I use KDE4 kdm, the problem occurs when I have an vnc KDE4 session running and want to login at console to KDE4.
Now I will check if I can open two parallel KDE4 vnc session.
I checked. I can start and login to two parallel KDE4 vnc session, sessions started as:
vncserver :1 -localhost
New '......:1 (........)' desktop is .......:1
Starting applications specified in /home/......./.vnc/xstartup Log file is /home/......./.vnc/........:1.log
vncserver :2 -localhost
New '....:2 (lxuser)' desktop is .....:2
Starting applications specified in /home/.../.vnc/xstartup Log file is /home/...../.vnc/....:2.log
But I cannot login from console (terminal 7) to KDE4. The login manager accepts the password, starts loggin in, the progress windows appears, then it drops back to kdm login screen.
Is this for me only?
Thanks,
Istvan
-----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iQIcBAEBAgAGBQJVUQaBAAoJEH8sJoKRFRU5S4sQAJAQGir5LO385XPafMhEyoOB SwNkW6SQXxWRwNPV3u47lwat8FF+Dv6j3uTP0AR7dpvEJBQqsAFSm9Rdj1HRXb3V 43PvfKACdEJ/fMOIOlW4MKTM5Wzpm1kbdgay18cjG4k1ve3iha9erdyVIiYjSTSI Uq+mICx8r5HChDLw5aBuoKnqEoGsWM9Vw4NSE21mgBmG/k0TyP4ncX2fq3s02e3s zKEkpBlTyBAq3RYKGIXm9MnO0xW3TcmaJG4uG2MmIdfENXcelpccY4x+lANQLUvo KKQmMbm8NYi/6t3ZgisgOWJrDP78XsBmMusA+c/viYNJ6iNEE7aAih3MlMkWqnC0 EG+uAr01L6PcGqrCjZf8SzFL5ipmOMIsaF7kZxDi+hnKGglLjisNsQCy+JjT5s24 mJP/e0VhVSH8dTAVvUGrmE9SSLLuRd9m9wDvyABXs0xRzIuiPVZSleBzg0CXTS+Z AkMqTBc2cQOSVrS3AepZd1ILVh/1kbBH2Hc4GRi09uw04GrUB466XPEvs4l7zAwc t5Rojxd8BwY+OrkKLp88jZphjlUKUtOCgb/p64GfHn7j1IleLC9WPM0MOvehWFdM l0y+SnRSQgYYqGG+V8Rs29diaVse/j3V9jRdWhW0BjA2aQCwL3ZJP7ol+5Gc4Yv3 1ggEFsI5eybjw6MOu4ZQ =M0lZ -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Ruben composed on 2015-05-10 18:42 (UTC-0400):
Andrei Borzenkov wrote:
IIRC GDM does not allow two simultaneous sessions by the same user
that is not good.
I wouldn't expect otherwise. Seems to me like it would be a recipe for ongoing personal settings data save collisions if any DM facilitated it, unless *maybe* the 2nd were a different session type, e.g. Gnome vs. KDE or XFCE. -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 On 2015-05-11 06:18, Felix Miata wrote:
I wouldn't expect otherwise. Seems to me like it would be a recipe for ongoing personal settings data save collisions if any DM facilitated it, unless *maybe* the 2nd were a different session type, e.g. Gnome vs. KDE or XFCE.
It can be done using different instances or profiles. Of course, the more complex a piece of software is, the more complex it is doing it, if not designed for the start for this. - -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" (Minas Tirith)) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iF4EAREIAAYFAlVQv14ACgkQja8UbcUWM1zRhwD/VrqQdrNElgMVSlkwE0Qn1Rjl o0FTHwkW3Fw2BtCoAowA/2A+erXJRJkKCcELcE4+er2NDm3OPmhH0DxffAwcDUcN =f8KM -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Felix Miata írta:
Ruben composed on 2015-05-10 18:42 (UTC-0400):
Andrei Borzenkov wrote:
IIRC GDM does not allow two simultaneous sessions by the same user
that is not good.
I wouldn't expect otherwise. Seems to me like it would be a recipe for ongoing personal settings data save collisions if any DM facilitated it, unless *maybe* the 2nd were a different session type, e.g. Gnome vs. KDE or XFCE.
First, this is not a good explanation for why parallel sessions should not / are not allowed. Unix/linux systems have allowed multiple sessions for ages, and it was/is not a problem for regular shell logins. Why should it be different for graphical logins? Second, I never had any problem with using multiple sessions with KDE3. Third, it is only speculation at the moment that KDE4 does not allow multiple sessions on design purpose. It can be a bug, a bad configuration etc. Fourth, it it was the case, why two vnc sessions are allowed? It would be good to know the opinion of a KDE developer who is familiar with login sessions. I would appreciate if others tried out whether they can login on console when vnc session is running, to make sure this problem affects others too, not only me. Thanks -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Istvan Gabor composed on 2015-05-11 19:50 (UTC+0200):
Felix Miata composed:
Ruben composed on 2015-05-10 18:42 (UTC-0400):
Andrei Borzenkov wrote:
IIRC GDM does not allow two simultaneous sessions by the same user
that is not good.
I wouldn't expect otherwise. Seems to me like it would be a recipe for ongoing personal settings data save collisions if any DM facilitated it, unless *maybe* the 2nd were a different session type, e.g. Gnome vs. KDE or XFCE.
First, this is not a good explanation for why parallel sessions should not / are not allowed. Unix/linux systems have allowed multiple sessions for ages, and it was/is not a problem for regular shell logins. Why should it be different for graphical logins?
Because of the way automatic saving of settings and session restore works, or not, such as window positions, window sizes, open apps. Simultaeous text sessions on vttys are naturally simpler, offering less opportunity to be first or last in a saving race. How much developer testing of simultaneous sessions do you think occurs, or even thought that anyone ever does it? IMO, somewhere between little and none. I'm guessing minimal, but a reason why KDE retired some of the automagic KDE3 featured, and invented activities, isolating opportunities for clashing.
Second, I never had any problem with using multiple sessions with KDE3.
I never tried with same user, always with different users, to insure against clashes. -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 05/11/2015 10:50 AM, Istvan Gabor wrote:
Third, it is only speculation at the moment that KDE4 does not allow multiple sessions on design purpose. It can be a bug, a bad configuration etc.
It might have to do with locks to various things inside of KDE4, wallet, sockets, dbus, etc. Just guessing.
Fourth, it it was the case, why two vnc sessions are allowed?
Vnc has a server side that runs in an already established Graphical environment, no? -- After all is said and done, more is said than done. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
В Mon, 11 May 2015 19:50:33 +0200 (CEST)
Istvan Gabor
Felix Miata írta:
Ruben composed on 2015-05-10 18:42 (UTC-0400):
Andrei Borzenkov wrote:
IIRC GDM does not allow two simultaneous sessions by the same user
that is not good.
I wouldn't expect otherwise. Seems to me like it would be a recipe for ongoing personal settings data save collisions if any DM facilitated it, unless *maybe* the 2nd were a different session type, e.g. Gnome vs. KDE or XFCE.
First, this is not a good explanation for why parallel sessions should not / are not allowed. Unix/linux systems have allowed multiple sessions for ages, and it was/is not a problem for regular shell logins. Why should it be different for graphical logins?
Second, I never had any problem with using multiple sessions with KDE3.
Third, it is only speculation at the moment that KDE4 does not allow multiple sessions on design purpose. It can be a bug, a bad configuration etc.
Fourth, it it was the case, why two vnc sessions are allowed?
In this case there is no *DM involved, vncserver starts them directly. This could make a difference.
It would be good to know the opinion of a KDE developer who is familiar with login sessions.
I would appreciate if others tried out whether they can login on console when vnc session is running, to make sure this problem affects others too, not only me.
Thanks
-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
participants (7)
-
Andrei Borzenkov
-
Carlos E. R.
-
Felix Miata
-
Ico Petrov
-
Istvan Gabor
-
John Andersen
-
Ruben