https://bugzilla.novell.com/show_bug.cgi?id=236567 Summary: SessionManager Sutdown/Restart/Logout no longer works; no action Product: openSUSE 10.2 Version: Final Platform: i686 OS/Version: All Status: NEW Severity: Major Priority: P5 - None Component: Basesystem AssignedTo: bnc-team-screening@forge.provo.novell.com ReportedBy: schneecrash+opensuse@gmail.com QAContact: qa@suse.de i've opensuse 10.2 installed w/ kde 355+. atm, i'm fully updated via smart w/ repos @, [kde] pri= 20, http://software.opensuse.org/download/KDE:/KDE3/openSUSE_10.2 [suse-10.2-update] pri=13, http://linux.nssl.noaa.gov/suse/update/10.2 [10.2-OSS] pri=12, http://linux.nssl.noaa.gov/opensuse/distribution/10.2/repo/oss all of the following is reproducible if [kde] is DISABLED, and the sys is fully 'downgraded' to distro-only ... a new/recent behavior _change_ (i.e., it used to work ...), my KDE now "ignores" SessionManager buttons (shutdown/restart/logout). on use of either the menubar applet, or the KDE menu cmds, the session dialog(s) _is_ opened, and i _can_ select action of chose, but then -- no action. neither 'Shutdown','Restart', or 'Logout' work anymore. i _can_ open Konsole, and 'shutdown -r now' or 'shutdown -h now', and the reboot completes. after a failed GUI-shutdown, the cmd-line shutdown works, but on startp, i see lots of "Filesystem is NOT clean" messages, and journals (ReiserFS) are replayed. if, however, a 'shutdown' is done before/without a prior 'failed' GUI attempt, startup is ok, w/ all Filesystems reporting 'Clean'. in either case, i DO note in /var/log/messages @ shutdown, The system is going down for reboot NOW! Jan 18 17:36:44 pc shutdown[3662]: shutting down for system reboot Jan 18 17:36:45 pc init: Switching to runlevel: 6 Jan 18 17:36:46 pc auditd[3093]: The audit daemon is exiting. Jan 18 17:36:46 pc kernel: audit(1169170606.747:6): audit_pid=0 old=3093 by auid=4294967295 Jan 18 17:36:47 pc kernel: nfsd: last server has exited Jan 18 17:36:47 pc kernel: nfsd: unexporting all filesystems Jan 18 17:36:47 pc mountd[3205]: Caught signal 15, un-registering and exiting. Jan 18 17:36:48 pc sshd[3269]: Received signal 15; terminating. Jan 18 17:36:48 pc xinetd[3270]: Exiting... Jan 18 17:36:50 pc kdm: :0[2944]: pam_close_session() failed: System error Jan 18 17:36:50 pc kdm: :0[2944]: pam_setcred(DELETE_CRED) failed: System error Jan 18 17:36:50 pc kernel: Kernel logging (proc) stopped. Jan 18 17:36:50 pc kernel: Kernel log daemon terminating. Jan 18 17:36:52 pc syslog-ng[2157]: syslog-ng version 1.6.11 going down i do not know if those System errors, pam_close_session() failed pam_setcred(DELETE_CRED) failed are related. although the reporting code is in/from KDE @, '.../branches/KDE/3.5/kdebase/kdm/backend/client.c' @ #kde-devel, it was suggested that the problem _is_ on the suse-side, "signal 15 is being sent to all tools indicating to shut them down.. so in some cases if the row in which the tools got shut down or killed are important.. if something got shut down (or killed) before another tool could sent its signals or terminate its code then such errors occour. e.g. if pam get killed before another tool could terminate itself by sending some request to pam then errors occour.. no pam and therefore error. that might explain the pam issues ... i think that kdm should be shut down far earlier so it can sent the pam requests, then these errors might disappear ..." i'm happy to provide any/all further info. just don't know where to look / what's helpful. thanks. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.