jweiner
December 15th, 2014, 08:49 AM
Dear Forum:
I had 14.04 up and running for months with no problems. Then, after several weeks of inactivity, I turned on my PC and rebooted (with no problems) and used the update manager to install new packages that had accumulated during the period of inactivity. After the installation I was prompted to reboot, which I did, but now I get the black screen with a blinking curser in the upper left corner. The system DOES boot in text mode, so I attempted the command "xstart", which resulted in the same problem black screen. Clearly the problem is in the X session. In the boot options, prior to booting, the video driver is "on chip" and this has always worked in the past. In my .xsession-errors file I see a number of messages beginning with "Script for bus started at run_im", Script for auto started at run_im", Script for default started at run_im", then "init: upstart-event-bridge main process (1544) terminated with status 1","init: upstart-even-bridge main process ended, respawning", and many more similar messages. A very ominous line near the end of the file says, "init: gnome-session (Unity) main process (1753) killed by TERM signal". For some reason the windows manager cannot get started, but I don't know what to do further to diagnose the problem or fix it. I would greatly appreciate some suggestions. Thanks, John
I had 14.04 up and running for months with no problems. Then, after several weeks of inactivity, I turned on my PC and rebooted (with no problems) and used the update manager to install new packages that had accumulated during the period of inactivity. After the installation I was prompted to reboot, which I did, but now I get the black screen with a blinking curser in the upper left corner. The system DOES boot in text mode, so I attempted the command "xstart", which resulted in the same problem black screen. Clearly the problem is in the X session. In the boot options, prior to booting, the video driver is "on chip" and this has always worked in the past. In my .xsession-errors file I see a number of messages beginning with "Script for bus started at run_im", Script for auto started at run_im", Script for default started at run_im", then "init: upstart-event-bridge main process (1544) terminated with status 1","init: upstart-even-bridge main process ended, respawning", and many more similar messages. A very ominous line near the end of the file says, "init: gnome-session (Unity) main process (1753) killed by TERM signal". For some reason the windows manager cannot get started, but I don't know what to do further to diagnose the problem or fix it. I would greatly appreciate some suggestions. Thanks, John