-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512
On 02/10/2016 03:11 AM, Peter Laws wrote:
On Tue, Feb 9, 2016 at 1:06 PM, Slávek Banko slavek.banko@axis.cz wrote:
I understand correctly that the creation of backtrace is not successful? You can switch to the text console and use gdb from the command line?
Password accepted 1/3 progress bar, then "bomb" dialog Click backtrace Enter password Text shows on window in dialog but before I can do anything (like read it), the screen goes back then it cycles back to the login
So, if we assume it make a backtrace where would I find it? If its not there, I'm happy to send output of both gdb and lsblk if you will kindly send me a command line example.
THANK YOU!
Hi Peter, I do not think it is that easy to catch this with gdb. You are starting a new session, so ksmserver is started. It crashes and so tdm brings you out and start anew. I think you need to create a small monitoring script that monitors for ksmserver instances, then if so grab the pid and attach gdb to it. You need to run this script from CLI before logging into TDE. Hopefully the script will be fast enough to interrupt ksmserver before it crashes, then you can step through it, although it may be a long process before you get to the point where it crashes.
IMO, the update of last friday broke something in your installation or in your current configuration. 1) have you tried creating a new user and logging into TDE as that user? Same crash? 2) if you run aptitude, do you see any broken dependency or errors? 3) did you update from one ubuntu version to another one or just updated "within" the same version?
Cheers Michele