This started after an update Friday. Get the login screen, system accepts password, progress bar shows for about 1/3 of the way, then get the dialog box about ksmserver crashing. I've done both "report crash" and "create backtrace" both of which cycle me back to the login screen.
I pull packages from here:
deb http://mirror.xcer.cz/trinity-sb trusty deps-r14 main-r14
Stuff I don't understand from the logs:
Feb 9 11:01:47 toto3 kernel: [ 0.008000] tsc: Marking TSC unstable due to check_tsc_sync_source failed Feb 9 11:01:47 toto3 kernel: [ 0.920132] ioapic: probe of 0000:00:05.4 failed with error -22 Feb 9 11:01:47 toto3 kernel: [ 4.348917] fglrx: module verification failed: signature and/or required key missing - tainting kernel Feb 9 11:01:48 toto3 failsafe: Failsafe of 120 seconds reached. Feb 9 11:02:01 toto3 kernel: [ 18.578714] init: failsafe main process (1243) killed by TERM signal
[ 232.363] (EE) AIGLX error: failed to open /usr/X11R6/lib64/modules/dri/fglrx_dri.so, error[/usr/X11R6/lib64/modules/dri/fglrx_dri.so: cannot open shared object file: No such file or directory]
[ 232.363] (EE) AIGLX error: failed to open /usr/lib64/dri/fglrx_dri.so, error[/usr/lib64/dri/fglrx_dri.so: cannot open shared object file: No such file or directory]
[ 232.363] (EE) AIGLX error: failed to open /usr/X11R6/lib/modules/dri/fglrx_dri.so, error[/usr/X11R6/lib/modules/dri/fglrx_dri.so: cannot open shared object file: No such file or directory]
DISTRIB_ID=Ubuntu DISTRIB_RELEASE=14.04 DISTRIB_CODENAME=trusty DISTRIB_DESCRIPTION="Ubuntu 14.04.3 LTS"
Welcome to Ubuntu 14.04.3 LTS (GNU/Linux 3.13.0-77-generic x86_64)
-- Peter Laws / N5UWY National Weather Center / Network Operations Center University of Oklahoma Information Technology plaws@ou.edu College of Architecture, Regional and City Planning, MRCP '16
On Tue, Feb 9, 2016 at 11:20 AM, Peter Laws plaws@ou.edu wrote:
This started after an update Friday. Get the login screen, system accepts password, progress bar shows for about 1/3 of the way, then get the dialog box about ksmserver crashing. I've done both "report crash" and "create backtrace" both of which cycle me back to the login screen.
I pull packages from here:
deb http://mirror.xcer.cz/trinity-sb trusty deps-r14 main-r14
Shouldn't go changing things mid-troubleshoot, I know, but if I do a "dpkg-reconfigure lightdm" and select tdm-trinity, I can't even get to the login screen. Something is broken in TDE, but what? ksmserver?
-- Peter Laws / N5UWY National Weather Center / Network Operations Center University of Oklahoma Information Technology plaws@ou.edu College of Architecture, Regional and City Planning, MRCP '16
Dne út 9. února 2016 Peter Laws napsal(a):
On Tue, Feb 9, 2016 at 11:20 AM, Peter Laws plaws@ou.edu wrote:
This started after an update Friday. Get the login screen, system accepts password, progress bar shows for about 1/3 of the way, then get the dialog box about ksmserver crashing. I've done both "report crash" and "create backtrace" both of which cycle me back to the login screen.
I pull packages from here:
deb http://mirror.xcer.cz/trinity-sb trusty deps-r14 main-r14
Shouldn't go changing things mid-troubleshoot, I know, but if I do a "dpkg-reconfigure lightdm" and select tdm-trinity, I can't even get to the login screen. Something is broken in TDE, but what? ksmserver?
-- Peter Laws / N5UWY National Weather Center / Network Operations Center University of Oklahoma Information Technology plaws@ou.edu College of Architecture, Regional and City Planning, MRCP '16
You have installed package kgtk-qt3-trinity? If yes, please, purge this package and restart TDM.
See bug 2477: http://bugs.pearsoncomputing.net/show_bug.cgi?id=2477
On Tue, Feb 9, 2016 at 12:12 PM, Slávek Banko slavek.banko@axis.cz wrote:
You have installed package kgtk-qt3-trinity? If yes, please, purge this package and restart TDM.
See bug 2477: http://bugs.pearsoncomputing.net/show_bug.cgi?id=2477
Sadly, that package is not installed.
-- Peter Laws / N5UWY National Weather Center / Network Operations Center University of Oklahoma Information Technology plaws@ou.edu College of Architecture, Regional and City Planning, MRCP '16
Dne út 9. února 2016 Peter Laws napsal(a):
On Tue, Feb 9, 2016 at 12:12 PM, Slávek Banko slavek.banko@axis.cz wrote:
You have installed package kgtk-qt3-trinity? If yes, please, purge this package and restart TDM.
See bug 2477: http://bugs.pearsoncomputing.net/show_bug.cgi?id=2477
Sadly, that package is not installed.
Ouch, that's not good news, because R14.0.3 is tagged as final and builds underway :( Can you send me a statement from lsblk? (If you want, to a private address.)
Dne út 9. února 2016 Peter Laws napsal(a):
I've done both "report crash" and "create backtrace" both of which cycle me back to the login screen.
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?
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!
-- Peter Laws / N5UWY National Weather Center / Network Operations Center University of Oklahoma Information Technology plaws@ou.edu College of Architecture, Regional and City Planning, MRCP '16
On Tue, Feb 9, 2016 at 2:11 PM, Peter Laws plaws@ou.edu 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!
A new fglrx dropped yesterday (ATI video card) and I was hoping that would get me back up but no joy.
If I wanted to remove TDE and re-install, what would be the best way of doing that? I don't see a new LTS release of Ubuntu, else I'd just go for that. I like the LTS releases because I'm not interested in losing a day or 5 of productivity with an upgrade. Fortunately, this initially happened late on Friday and I was not at work on Monday, so I've only actually been out of service for 1 day, but I see no hope of recovery today. At some point, I'd rather just re-install ... but ...
-- Peter Laws / N5UWY National Weather Center / Network Operations Center University of Oklahoma Information Technology plaws@ou.edu College of Architecture, Regional and City Planning, MRCP '16
-----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
On Wed, Feb 10, 2016 at 9:29 AM, Michele Calgaro michele.calgaro@yahoo.it wrote:
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.
- have you tried creating a new user and logging into TDE as that user? Same crash?
- if you run aptitude, do you see any broken dependency or errors?
- did you update from one ubuntu version to another one or just updated "within" the same version?
New user doesn't work, either, but behavior is slightly different - no progress bar, no bomb dialog, just accept password, black screen, then back to user.
I always use apt-get update/apt-get dist-upgrade and accept whatever is there. I have Slavek's repos for TDE.
This started as a Kubuntu install (new system, thought I'd give KDE4 another chance - silly me) but I ran screaming back to TDE.
For me, starting over with a new install (of something I know would run TDE) is less painful than writing a gdb script! Fortunately, I've got a Macbook, so I can still work, but I really need to get back to where I was earlier Friday.
I checked - there is no "undo" button. :-D
-- Peter Laws / N5UWY National Weather Center / Network Operations Center University of Oklahoma Information Technology plaws@ou.edu College of Architecture, Regional and City Planning, MRCP '16
On Wed, Feb 10, 2016 at 10:02 AM, Peter Laws plaws@ou.edu wrote:
I checked - there is no "undo" button. :-D
Tailed a bunch of things while trying to login. This is probably meaningful to someone other than me.
==> kern.log <==
Feb 10 10:08:16 toto3 kernel: [ 3501.129644] drkonqi[6238]: segfault at 128 ip 00007f2cc5424520 sp 00007ffc239b7db8 error 4 in libtdecore.so.14.0.0[7f2cc51b4000+3d1000]
-- Peter Laws / N5UWY National Weather Center / Network Operations Center University of Oklahoma Information Technology plaws@ou.edu College of Architecture, Regional and City Planning, MRCP '16
On Wed, Feb 10, 2016 at 10:09 AM, Peter Laws plaws@ou.edu wrote:
Tailed a bunch of things while trying to login. This is probably meaningful to someone other than me.
==> kern.log <==
Feb 10 10:08:16 toto3 kernel: [ 3501.129644] drkonqi[6238]: segfault at 128 ip 00007f2cc5424520 sp 00007ffc239b7db8 error 4 in libtdecore.so.14.0.0[7f2cc51b4000+3d1000]
First instance of this that I see is 1800 local time Friday 2/5. So definitely patch-induced ... but which patch?
-- Peter Laws / N5UWY National Weather Center / Network Operations Center University of Oklahoma Information Technology plaws@ou.edu College of Architecture, Regional and City Planning, MRCP '16
Dne st 10. února 2016 Peter Laws napsal(a):
On Wed, Feb 10, 2016 at 10:09 AM, Peter Laws plaws@ou.edu wrote:
Tailed a bunch of things while trying to login. This is probably meaningful to someone other than me.
==> kern.log <==
Feb 10 10:08:16 toto3 kernel: [ 3501.129644] drkonqi[6238]: segfault at 128 ip 00007f2cc5424520 sp 00007ffc239b7db8 error 4 in libtdecore.so.14.0.0[7f2cc51b4000+3d1000]
First instance of this that I see is 1800 local time Friday 2/5. So definitely patch-induced ... but which patch?
My suspicion is primarily on this patch:
http://mirror.git.trinitydesktop.org/cgit/tdelibs/commit/?id=51046798
Therefore, I wonder listing from lsblk :)
On Wednesday 10 of February 2016 18:01:15 Slávek Banko wrote:
Dne st 10. února 2016 Peter Laws napsal(a):
On Wed, Feb 10, 2016 at 10:09 AM, Peter Laws plaws@ou.edu wrote:
Tailed a bunch of things while trying to login. This is probably meaningful to someone other than me.
==> kern.log <==
Feb 10 10:08:16 toto3 kernel: [ 3501.129644] drkonqi[6238]: segfault at 128 ip 00007f2cc5424520 sp 00007ffc239b7db8 error 4 in libtdecore.so.14.0.0[7f2cc51b4000+3d1000]
First instance of this that I see is 1800 local time Friday 2/5. So definitely patch-induced ... but which patch?
My suspicion is primarily on this patch:
http://mirror.git.trinitydesktop.org/cgit/tdelibs/commit/?id=51046798
Therefore, I wonder listing from lsblk :)
For your information: Peter confirmed my suspicions, and the patch will soon be pushed into Git. Peter saved the final R14.0.3 against this unplesant bug!
-
Michele Calgaro -
Peter Laws -
Slávek Banko