[opensuse-factory] Odd problem
Hi This is something i experienced this morning (twice), i've not tried it before so i'm not sure if this is a valid response from the system. I log in as a normal user (graphical mode - kdm) and after i hit the <cr> after entering the password, i did ctrl, alt F4 and logged in as root and did an "ls -l". The system would context switch me back to graphical mode and then fail to log into plasma and drop me back to the graphical login. Should the system be switching me back or run happily in the background? Regards Ian -- opensuse:tumbleweed:20161101 Qt: 5.7.0 KDE Frameworks: 5.27.0 KDE Plasma: 5.8.3 kwin5-5.8.3-164.1.x86_64 kmail5-16.08.2-1.1.x86_64 Kernel: 4.8.4-1-default Nouveau: 1.0.13_1.1 -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On 2016-11-03 08:07, ianseeks wrote:
Hi
This is something i experienced this morning (twice), i've not tried it before so i'm not sure if this is a valid response from the system.
I log in as a normal user (graphical mode - kdm) and after i hit the <cr> after entering the password, i did ctrl, alt F4 and logged in as root and did an "ls -l". The system would context switch me back to graphical mode and then fail to log into plasma and drop me back to the graphical login.
WHAT!?
Should the system be switching me back or run happily in the background?
Certainly not. You should stay on text mode, till you manually switch back to graphics, at the same user you were before, of course. -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar)
On 11/03/2016 08:49 PM, Carlos E. R. wrote:
On 2016-11-03 08:07, ianseeks wrote:
Hi
This is something i experienced this morning (twice), i've not tried it before so i'm not sure if this is a valid response from the system.
I log in as a normal user (graphical mode - kdm) and after i hit the <cr> after entering the password, i did ctrl, alt F4 and logged in as root and did an "ls -l". The system would context switch me back to graphical mode and then fail to log into plasma and drop me back to the graphical login.
WHAT!?
Should the system be switching me back or run happily in the background?
Certainly not. You should stay on text mode, till you manually switch back to graphics, at the same user you were before, of course.
If the xserver crashes during that time it may get restarted which will switch you back to KDM, but its certainly not the expected behavior. -- Simon Lees (Simotek) http://simotek.net Emergency Update Team keybase.io/simotek SUSE Linux Adeliade Australia, UTC+9:30 GPG Fingerprint: 5B87 DB9D 88DC F606 E489 CEC5 0922 C246 02F0 014B
On Thursday, 3 November 2016 21:11:17 GMT Simon Lees wrote:
On 11/03/2016 08:49 PM, Carlos E. R. wrote:
On 2016-11-03 08:07, ianseeks wrote:
Hi
This is something i experienced this morning (twice), i've not tried it before so i'm not sure if this is a valid response from the system.
I log in as a normal user (graphical mode - kdm) and after i hit the <cr> after entering the password, i did ctrl, alt F4 and logged in as root and did an "ls -l". The system would context switch me back to graphical mode and then fail to log into plasma and drop me back to the graphical login.
WHAT!?
Should the system be switching me back or run happily in the background?
Certainly not. You should stay on text mode, till you manually switch back to graphics, at the same user you were before, of course.
If the xserver crashes during that time it may get restarted which will switch you back to KDM, but its certainly not the expected behavior. Thanks, it looks that way from the journal, xserver/xorg issues causing coredumps and logout
-- opensuse:tumbleweed:20161102 Qt: 5.7.0 KDE Frameworks: 5.27.0 KDE Plasma: 5.8.3 kwin5-5.8.3-164.1.x86_64 kmail5-16.08.2-1.1.x86_64 Kernel: 4.8.4-1-default Nouveau: 1.0.13_1.1 -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Thursday, 3 November 2016 11:19:28 GMT Carlos E. R. wrote:
On 2016-11-03 08:07, ianseeks wrote:
Hi
This is something i experienced this morning (twice), i've not tried it before so i'm not sure if this is a valid response from the system.
I log in as a normal user (graphical mode - kdm) and after i hit the <cr> after entering the password, i did ctrl, alt F4 and logged in as root and did an "ls -l". The system would context switch me back to graphical mode and then fail to log into plasma and drop me back to the graphical login.
WHAT!?
Should the system be switching me back or run happily in the background?
Certainly not. You should stay on text mode, till you manually switch back to graphics, at the same user you were before, of course. Yep, its consistent, i tried it again today. Looks like an xserver/XORG hiccup and kactivitymange having a few coredumps as a result. I've just cut this from the journal - (not sure why powerdevil backlight or snapper is in the logs ) - i'm actually using the nvidia blob not nouveau as my signature suggests.
Nov 04 08:13:42 LianLi dbus[678]: [system] Activating service name='org.kde.powerdevil.backlighthelper' (using servicehelper) Nov 04 08:13:42 LianLi org.kde.powerdevil.backlighthelper[678]: powerdevil: no kernel backlight interface found Nov 04 08:13:42 LianLi org.kde.powerdevil.backlighthelper[3481]: QDBusArgument: read from a write-only object Nov 04 08:13:42 LianLi org.kde.powerdevil.backlighthelper[3481]: QDBusArgument: read from a write-only object Nov 04 08:13:42 LianLi org.kde.powerdevil.backlighthelper[3481]: QDBusArgument: read from a write-only object Nov 04 08:13:42 LianLi dbus[678]: [system] Successfully activated service 'org.kde.powerdevil.backlighthelper' Nov 04 08:13:43 LianLi audit[3496]: ANOM_ABEND auid=1004 uid=1004 gid=100 ses=2 pid=3496 comm="kactivitymanage" exe="/usr/bin/kactivitymanagerd" sig=6 Nov 04 08:13:43 LianLi audit[3495]: ANOM_ABEND auid=1004 uid=1004 gid=100 ses=2 pid=3495 comm="kactivitymanage" exe="/usr/bin/kactivitymanagerd" sig=6 Nov 04 08:13:43 LianLi kernel: audit: type=1701 audit(1478247223.609:167): auid=1004 uid=1004 gid=100 ses=2 pid=3496 comm="kactivitymanage" exe="/usr/ bin/kactivitymanagerd" sig=6 Nov 04 08:13:43 LianLi kernel: audit: type=1701 audit(1478247223.609:168): auid=1004 uid=1004 gid=100 ses=2 pid=3495 comm="kactivitymanage" exe="/usr/ bin/kactivitymanagerd" sig=6 Nov 04 08:13:44 LianLi audit[2654]: ANOM_ABEND auid=4294967295 uid=0 gid=0 ses=4294967295 pid=2654 comm="X" exe="/usr/bin/Xorg" sig=6 Nov 04 08:13:44 LianLi kernel: audit: type=1701 audit(1478247224.077:169): auid=4294967295 uid=0 gid=0 ses=4294967295 pid=2654 comm="X" exe="/usr/bin/ Xorg" sig=6 Nov 04 08:13:44 LianLi polkitd[1437]: Unregistered Authentication Agent for unix-session:2 (system bus name :1.69, object path /org/kde/PolicyKit1/ AuthenticationAgent, locale en_GB.UTF-8) (disconnected from bus) Nov 04 08:13:44 LianLi org.kde.kglobalaccel[2704]: The X11 connection broke (error 1). Did the X11 server die? Nov 04 08:13:44 LianLi org.kde.KScreen[2704]: The X11 connection broke (error 1). Did the X11 server die? Nov 04 08:13:44 LianLi kdm[1072]: X server for display :0 terminated unexpectedly Nov 04 08:13:44 LianLi audit[3473]: ANOM_ABEND auid=1004 uid=1004 gid=100 ses=2 pid=3473 comm="kactivitymanage" exe="/usr/bin/kactivitymanagerd" sig=11 Nov 04 08:13:44 LianLi kernel: kactivitymanage[3473]: segfault at 8 ip 00007ffbdb7f8431 sp 00007ffeeacca2f0 error 4 in libQt5XcbQpa.so. 5.7.0[7ffbdb7bc000+fb000] Nov 04 08:13:44 LianLi kernel: audit: type=1701 audit(1478247224.373:170): auid=1004 uid=1004 gid=100 ses=2 pid=3473 comm="kactivitymanage" exe="/usr/ bin/kactivitymanagerd" sig=11 Nov 04 08:13:44 LianLi kdm[2658]: :0[2658]: pam_unix(xdm:session): session closed for user ians Nov 04 08:13:44 LianLi audit[2658]: USER_END pid=2658 uid=0 auid=1004 ses=2 msg='op=PAM:session_close grantors=pam_loginuid,pam_limits,pam_unix,pam_umask,pam_systemd,pam_gnome_keyring,pam_env acct="ians" exe="/usr/bin/kdm" hostname=? addr=? terminal=:0 res=success' Nov 04 08:13:44 LianLi audit[2658]: CRED_DISP pid=2658 uid=0 auid=1004 ses=2 msg='op=PAM:setcred grantors=pam_gnome_keyring,pam_unix acct="ians" exe="/usr/ bin/kdm" hostname=? addr=? terminal=:0 res=success' Nov 04 08:13:44 LianLi kernel: audit: type=1106 audit(1478247224.441:171): pid=2658 uid=0 auid=1004 ses=2 msg='op=PAM:session_close grantors=pam_loginuid,pam_limits,pam_unix,pam_umask,pam_systemd,pam_gnome_keyring,pam_env acct="ians" exe="/usr/bin/kdm" hostname=? addr=? terminal=:0 res=success' Nov 04 08:13:44 LianLi kernel: audit: type=1104 audit(1478247224.441:172): pid=2658 uid=0 auid=1004 ses=2 msg='op=PAM:setcred grantors=pam_gnome_keyring,pam_unix acct="ians" exe="/usr/bin/kdm" hostname=? addr=? terminal=:0 res=success' Nov 04 08:13:46 LianLi audit[3539]: ANOM_ABEND auid=1004 uid=1004 gid=100 ses=2 pid=3539 comm="kactivitymanage" exe="/usr/bin/kactivitymanagerd" sig=6 Nov 04 08:13:46 LianLi kernel: audit: type=1701 audit(1478247226.072:173): auid=1004 uid=1004 gid=100 ses=2 pid=3539 comm="kactivitymanage" exe="/usr/ bin/kactivitymanagerd" sig=6 Nov 04 08:13:48 LianLi systemd-logind[700]: Removed session 2. Nov 04 08:14:06 LianLi systemd-coredump[3516]: Process 3496 (kactivitymanage) of user 1004 dumped core. Nov 04 08:14:06 LianLi systemd-coredump[3517]: Process 3495 (kactivitymanage) of user 1004 dumped core. Nov 04 08:14:08 LianLi systemd-coredump[3561]: Process 3539 (kactivitymanage) of user 1004 dumped core. Nov 04 08:14:12 LianLi systemd-coredump[3534]: Process 2654 (X) of user 0 dumped core. Nov 04 08:14:14 LianLi systemd-coredump[3542]: Process 3473 (kactivitymanage) of user 1004 dumped core. Nov 04 08:15:01 LianLi run-crons[3634]: suse.de-snapper: OK -- opensuse:tumbleweed:20161102 Qt: 5.7.0 KDE Frameworks: 5.27.0 KDE Plasma: 5.8.3 kwin5-5.8.3-164.1.x86_64 kmail5-16.08.2-1.1.x86_64 Kernel: 4.8.4-1-default Nouveau: 1.0.13_1.1 -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Thursday, 3 November 2016 07:07:37 GMT ianseeks wrote: If anyone else has seen the problem, please let me know and i'll log it
Hi
This is something i experienced this morning (twice), i've not tried it before so i'm not sure if this is a valid response from the system.
I log in as a normal user (graphical mode - kdm) and after i hit the <cr> after entering the password, i did ctrl, alt F4 and logged in as root and did an "ls -l". The system would context switch me back to graphical mode and then fail to log into plasma and drop me back to the graphical login.
Should the system be switching me back or run happily in the background?
Regards
Ian
-- opensuse:tumbleweed:20161102 Qt: 5.7.0 KDE Frameworks: 5.27.0 KDE Plasma: 5.8.3 kwin5-5.8.3-164.1.x86_64 kmail5-16.08.2-1.1.x86_64 Kernel: 4.8.4-1-default Nouveau: 1.0.13_1.1 -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
participants (3)
-
Carlos E. R. -
ianseeks -
Simon Lees