should not show the logout dialog
chances are ksmserver segfaults on logout instead of shutting the computer down. If it happens to you check that in .trinity/share/config/ksmserverrc these two enries are set to "false":
Just in case somebody runs into the same issue:
When you configure TDE so that
- it shuts down the computer when you log out
- should not show the logout dialog
chances are ksmserver segfaults on logout instead of shutting the computer down. If it happens to you check that in .trinity/share/config/ksmserverrc these two enries are set to "false":
[Logout]
doFancyLogout=false
showLogoutStatusDlg=false
Nik
Hi Nik,
I tried to replicate this but I don't get any SEGV here. Not sure I am using exactly the same options as you are. Could you post a screenshot?
Alternatively, could you replicate the problem and save the crash dump?
Hi Nik,
I tried to replicate this but I don't get any SEGV here. Not sure I am using exactly the same options as you are. Could you post a screenshot?
Alternatively, could you replicate the problem and save the crash dump?
Anno domini 2021 Mon, 06 Sep 08:34:20 +0000
Michele Calgaro scripsit:
Hi Nik,
I tried to replicate this but I don't get any SEGV here. Not sure I am using exactly the same options as you are. Could you post a screenshot?
Alternatively, could you replicate the problem and save the crash dump?
I wished I could, but after I changed said settins on the affected system and rebooted I was not able to replicate the problem any more. As far as I can tell ksmserver crashes only on a clean installation and when the user setting tell it to poweroff and save the session when logged out. When I manage to persuade ksmserver to make a single clean shutdown the problem will never appear again.
Nik
From Nik, not sure why it didn't show up here
<hr/>
Hi Michele!
Anno domini 2021 Mon, 06 Sep 08:34:20 +0000
Michele Calgaro scripsit:
> Hi Nik,
> I tried to replicate this but I don't get any SEGV here. Not sure I am using exactly the same options as you are. Could you post a screenshot?
> Alternatively, could you replicate the problem and save the crash dump?
I wished I could, but after I changed said settins on the affected system and rebooted I was not able to replicate the problem any more. As far as I can tell ksmserver crashes only on a clean installation and when the user setting tell it to poweroff and save the session when logged out. When I manage to persuade ksmserver to make a single clean shutdown the problem will never appear again.
Nik
I wished I could, but after I changed said settins on the affected system and rebooted I was not able to replicate the problem any more. As far as I can tell ksmserver crashes only on a clean installation and when the user setting tell it to poweroff and save the session when logged out. When I manage to persuade ksmserver to make a single clean shutdown the problem will never appear again.
I have occasionally experienced crashes if I have changed the style/icon/theme settings in TCC. Could this be related with the "clean installation" you mentioned?
> I wished I could, but after I changed said settins on the affected system and rebooted I was not able to replicate the problem any more. As far as I can tell ksmserver crashes only on a clean installation and when the user setting tell it to poweroff and save the session when logged out. When I manage to persuade ksmserver to make a single clean shutdown the problem will never appear again.
I have occasionally experienced crashes if I have changed the style/icon/theme settings in TCC. Could this be related with the "clean installation" you mentioned?
Would fit into my usage pattern. When I set up a new computer I start with the TDE wizzard, choose all default settings, then go into kcontrol and do the user settings. Usually I reboot after I went through all the configs I like to change. Then after reboot I face the ksmserver crash or I don't. Usually the problem appears when I try to configure the logout behaviour and change it from the default settings to something that does not show the dialog.
Would fit into my usage pattern. When I set up a new computer I start with the TDE wizzard, choose all default settings, then go into kcontrol and do the user settings. Usually I reboot after I went through all the configs I like to change. Then after reboot I face the ksmserver crash or I don't. Usually the problem appears when I try to configure the logout behaviour and change it from the default settings to something that does not show the dialog.
Just in case somebody runs into the same issue:
When you configure TDE so that
chances are ksmserver segfaults on logout instead of shutting the computer down. If it happens to you check that in .trinity/share/config/ksmserverrc these two enries are set to "false":
[Logout]
doFancyLogout=false
showLogoutStatusDlg=false
Nik
Hi Nik,
I tried to replicate this but I don't get any SEGV here. Not sure I am using exactly the same options as you are. Could you post a screenshot?
Alternatively, could you replicate the problem and save the crash dump?
From Nik, not sure why it didn't show up here
Hi Michele!
Anno domini 2021 Mon, 06 Sep 08:34:20 +0000
Michele Calgaro scripsit:
I wished I could, but after I changed said settins on the affected system and rebooted I was not able to replicate the problem any more. As far as I can tell ksmserver crashes only on a clean installation and when the user setting tell it to poweroff and save the session when logged out. When I manage to persuade ksmserver to make a single clean shutdown the problem will never appear again.
Nik
I have occasionally experienced crashes if I have changed the style/icon/theme settings in TCC. Could this be related with the "clean installation" you mentioned?
Would fit into my usage pattern. When I set up a new computer I start with the TDE wizzard, choose all default settings, then go into kcontrol and do the user settings. Usually I reboot after I went through all the configs I like to change. Then after reboot I face the ksmserver crash or I don't. Usually the problem appears when I try to configure the logout behaviour and change it from the default settings to something that does not show the dialog.
ok, maybe next time keep this in mind and try to capture the crash dump if you can. Then upload it here.