Debian Multimedia :: X Server Fails To Start After Upgrade?
Jan 23, 2010
I did a distribution upgrade using "apt-get dist-upgrade". After rebooting, I receive a message saying "Failed to start the X Server". When I okay the prompt for more info, I see the following: GDM: Xserer not found: /usr/bin/X :0 -audit 0 -auth /var/lib/gdm/:0.Xauth -nolisten tcp vt7 Error: Command could not be executed! install the X server or correct GDM configuration and restart GDM.gdm[4678]: WARNING: gdm_server_spawn: Xserver not found: /usr/binX :0 -auth /var/lib/gdm/:0.Xauth -nolisten tcp vt7
I just did a yum upgrade (5.3 to 5.4) on one node of my three node cluster (RHCS), which did:
Rebooted to the new kernel, but cman failed to start. Rebooted back to the previous kernel, but no change, so it doesn't appear to be the kernel.... Some errors are:
On the upgraded node, the following processes are running:
Whereas on the non-upgraded node, the following processes are running:
After installing the latest upgrades in Testing, KDE will no longer start. After logging in, the progress bar reaches about 80% and then stops. At this point the system is unresponsive, and I have to switch to another VT to reboot.
I upgraded to jessie today and I am having problems with my background. When I log in, the background tries to start on the external monitor but then it fails to load. I can change the background in settings but it does not show up. The background just becomes black and I am not sure why.
X won't start (awesome WM) after upgrading to jessie. It seems to startup up, then just stops. I'm running startx from the command line after logging in. The xorg log (bottom) looks good and I see an exit code of zero.
I do see this in sysout:
Code: Select alldebian xf86TokenToOptinfo: table is NULL
Googled around but I can't find anything specific on this one.
I'm not using any xorg.conf, as booting into a linux rescue cd everything works ok
Code: Select all[ 2275.960] X.Org X Server 1.16.4 Release Date: 2014-12-20 [ 2275.960] X Protocol Version 11, Revision 0 [ 2275.960] Build Operating System: Linux 3.16.0-4-amd64 x86_64 Debian [ 2275.960] Current Operating System: Linux jj 3.14.25 #1 SMP Fri Dec 5 10:17:33 EST 2014 x86_64
After upgrading to squeeze I have now X Server 1.7.7 installed and it won't start. When I try to run startx script, monitor gets blank for few seconds and then I get back to command prompt and no errors is displayed.
When I try the same as root, system locks up with blank screen and no functioning keyboard.
Initially I had kernel 2.6.28 which worked fine with earlier Lenny's X Server and Matrox P650 AGP video card. After upgrade I found, that Matrox P650 is not longer supported in new xorg and I swapped it to Matrox G550 AGP card.
Tried mga driver's many options, upgraded to kernel 2.6.37.2, tried with Matrox G200 PCI and Savage 4 Pro AGP card but without a success.
With kernel AGP support turned on I got both with Matrox G550 and Savage card an MTRR error: "error setting MTRR, Invalid argument (22)". Without AGP support in kernel, Matrox G550 gets initialised as PCI card and no errors and X still not working. Same with Matrox G200 PCI card.
With vesa driver the behavior is also the same and output at the end of Xorg.log file is almost the same.
So I understand, that this is some X server problem?
Nothing special in xorg.conf file and tried without it also.
End of the Xorg.0.log file:
>> (II) MGA(0): YDstOrg is set to 0 (II) Loading sub module "fb" (II) LoadModule: "fb" (II) Loading /usr/lib/xorg/modules/libfb.so
I've just upgraded to 9.10, and mysql fails to start. When I do an /etc/init.d/mysql start, I just get * Starting MySQL database server mysqld ...fail!with no additional errors or information to say what went wrong. I saw this thread http://ubuntuforums.org/showthread.php?t=1322070 but the fix mentioned does not apply, as I don't have the #skip bsd line in my config file.
So I made the upgrade to slackware64-current and all of a sudden after my next reboot, startx failed, and x refused to start the output was the following:
Code: Release Date: 2010-02-16 X Protocol Version 11, Revision 0 Build Operating System: Slackware 13.1 Slackware Linux Project Current Operating System: Linux hd830 2.6.33 #3 SMP Sat Feb 27 19:42:32 CST 2010 x86_64 Kernel command line: BOOT_IMAGE=Linux ro root=803 vt.default_utf8=0 Build Date: 23 February 2010 12:09:32PM
Current version of pixman: 0.16.6 Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. (==) Log file: "/var/log/Xorg.0.log", Time: Sat Mar 6 19:21:18 2010 (==) Using default built-in configuration (30 lines) (EE) Failed to load module "fbdev" (module does not exist, 0) WARNING: Error inserting button (/lib/modules/2.6.33/kernel/drivers/acpi/button.ko): Invalid module format WARNING: Error inserting i2c_algo_bit (/lib/modules/2.6.33/kernel/drivers/i2c/algos/i2c-algo-bit.ko): Invalid module format WARNING: Error inserting agpgart (/lib/modules/2.6.33/kernel/drivers/char/agp/agpgart.ko): Invalid module format WARNING: Error inserting drm (/lib/modules/2.6.33/kernel/drivers/gpu/drm/drm.ko): Invalid module format WARNING: Error inserting drm_kms_helper (/lib/modules/2.6.33/kernel/drivers/gpu/drm/drm_kms_helper.ko): Invalid module format
FATAL: Error inserting i915 (/lib/modules/2.6.33/kernel/drivers/gpu/drm/i915/i915.ko): Invalid module format (EE) intel(0): No kernel modesetting driver detected. (EE) Screen(s) found, but none have a usable configuration. Fatal server error: no screens found
Please consult the The X.Org Foundation support. Please also check the log file at "/var/log/Xorg.0.log" for additional information. So then after some googling I got the suggestion to downgrade udev-151 to udev-141, but that yeilded no results. So I did some more googling and a bunch of people who had the same problem said that downgrading module-init-tools worked, so I downgraded from module-init-tools 3.11 something to 3.6 and now, not only does my X no longer work, but no modules are being loaded I believe, for example I saw in my startup that fuse was not being loaded, ndiswrapper which I had installed was not loaded.
I recently installed the 32bit version of 10.10 on my Dell Latitude E6510. Everything went smoothly.. in fact I was quite impressed as I have my laptop in a docking station connected to dual 24" displays. The installer recognized them and they worked perfectly right outta the box: yea for Ubuntu !
After the install, I installed some apps then upgraded the installation to the latest hotness - lots and lots of things were upgraded. I restarted the machine to "complete the upgrade process" and it boots but right when it gets to starting the Windows environment, both display just loose their signal...
It boots fine to the command line if I boot in safe mode. I had installed the nVidia drivers but I did that before the update and I had no problems until I did the system update. Any ideas? Should I start by disabling the 3rd party drivers? If so, how would I do that?
I was able to start multiple X servers before. Now after the upgrade to rootless X, I had to add myself to the "input" group to be able to start X, but I'm unable to start 2nd X on a different vt.
Here are the errors and warnings I'm seeing:
Code: Select all[114940.404] (EE) /dev/dri/card0: failed to set DRM interface version 1.4: Permission denied [114940.409] (WW) Falling back to old probe method for modesetting [114940.409] (WW) Falling back to old probe method for vesa [114940.409] (WW) VGA arbiter: cannot open kernel arbiter, no multi-card support [114940.409] (EE) Screen 0 deleted because of no matching config section. [114940.409] (EE) [114940.409] (EE) Cannot run in framebuffer mode. Please specify busIDs for all framebuffer devices
I have been using bumblebee on my Optimus Laptop for a long time.I think I have this problem since the last Xorg upgrade, some months ago. The upgrade notes warned that Xorg now runs on userspace, and that configuration files are now read from the user (although I haven't noticed that).Then optirun ceased to work. As I'm using sid, I'm used to things being broken sometimes, so I simply let it go waiting for an upgrade that would fix it. Since this upgrade (either to Xorg or to bumblebee) is not coming, I have searched on the Internet, and I'm surprised that many people have had problems with bumblebee, but no one seems to be having the same exact error (see below).
I have tried everything (everything my limited knowledge and my internet searches allow me). I have tried with nvidia and nouveau drivers, but I get more or less the same result.
Code: Select all$ sudo systemctl status bumblebeed ● bumblebeed.service - Bumblebee C Daemon Loaded: loaded (/lib/systemd/system/bumblebeed.service; enabled; vendor preset: enabled) Active: active (running) since mié 2015-12-30 09:30:34 CET; 20min ago
[code]....
It seems Xorg is failing but is not giving any information about the failure, no message, which is different to the problems I have found in the Web. I have purged bumblebee packages to assure I'm using default configuration files. I have added rcutree.rcu_idle_gp_delay=1 to GRUB_ CMDLINE_ LINUX_ DEFAULT as instructed on some howtos.
I have headless debian as a server which i use over tightvnc server running on it. Vnc works fine but I can't for example run sudo mousepad or any other gui app from terminal, it says something about not having the rights to open it as root. I understand this has something to do with security, but my computers are behind nat so the vnc server can only be connected inside my lan so i don't mind.
I have an older computer and I did a fresh install of Jessie
Procesor AMD, Graphic card ATI Radeon 9200 PRO / RV280
After instalation my computer boot into black screen. I have no problems with wheezy.
I installed manually firmware-linux-nonfree (in case) module R200_cp is loading correctly.
When I configure Xorg, my log file says something like that: ----------------------------------------------------------------------------------- (EE) Segmentation fault at address 0x0 Fatal server error: (EE) Caught signal 11 (Segmentation fault). Server aborting --------------------------------------------------------------------------
The setup: 2 identical boxes running Fedora Core 15 2.6.38.8 kernel, 64bit that Im trying to setup in a cluster using luci.
So far: Managed to create the cluster.conf file, defined the nodes with hosts and such.
The problem: When I try to have the 2 nodes (nod1 and nod2) join the cluster via luci's web interface, I get "Starting cman: Job failed. See system logs and 'systemctl status' for details." When I check code...
Now. I know that cman service is installed. I even tried removing and reinstalling the whole thing, dependencies and all, but it just won't start and I've run out of ideas.
Just done a fresh install of squeeze (basic install then installed X, WM and a few applications) and I find that I am unable to get an xterm up and running (same goes for rxvt-unicode (urxvt) and uxterm). The same problem occurs with both Openbox and DWM window managers.
Cannot find input plugin for MRL [dvd:/] Is now the message that I get when attempting to play DVDs in Kaffeine, which worked very well in SuSe 10,3 three hours ago. Ironically, VLC now works a treat, when upgrading that in 10.3 killed it.Xine doesn't want to work (restricted format), and Kaffeine isn't playing any files either. Has something been dropped from my previous setup, or do I have an inadequate installation? I'm not very command line oriented I'm afraid;I just expect things to work as they did before...:-)
I've build a home-made small cluster built up of a master and 1 disk-less slave node.Lately it happens that the node 1 fails to start, reporting the following message:
I have a Toshiba A205 S5804 laptop that had Vista Home Premium installed. Tried to install Centos 5 (2.6.18-8-el5) and when I went through the install process, X Server failed to start so I had to go thorough the command line install. Once the install completed, it only booted to console.
The default resolution for this laptop is 1280X800 but I dont know if that is why or not. if anyone has a clue about my issue, please let me know.. I really dont want to install windows.
Today I upgraded my system to the Nvidia driver 340.93 and 4.2.0-1 kernel on Debian Stretch.
While I wait for the gnome login screen to pop up I get the "Oh no something has gone wrong" message.
When I log in from another terminal and execute startx , gnome initiates and starts although settings like my resolution and other xserver settings are not loaded.
From the journalctl I believe the error is located in the following section:
Code: Select allOct 06 14:23:17 DEBIAN-PC org.a11y.atspi.Registry[1692]: SpiRegistry daemon is running with well-known name - org.a11y.atspi.Registry Oct 06 14:23:17 DEBIAN-PC gnome-session[1680]: X Error of failed request: BadValue (integer parameter out of range for operation) Oct 06 14:23:17 DEBIAN-PC gnome-session[1680]: Major opcode of failed request: 154 (GLX)
[Code] ....
I reinstalled the xorg-xserver and the nvidia drivers and I get the same behavior.
Looking for some info in order to reconfigure the gnome-session to work?
I have just recently installed firestarter to get an idea of iptables editing with a GUI. Firestarter works great and I love it, however when I turn my system on, and my system is booting up the terminal displays a "Failed" message when attempting to start up firestarter. Now I have been doing my homework (reserch) and have read that a user will get this error because firestarter trys to load prior to the network manager starting up. I have also read some other variables that can cause this is if you use network manager and have a password on your user account (which I do have) can cause this issue.
However in most cases from what I have read is even though it gives the user a "Failed" startup message, once the user logs in, and is connected to the internet firestarter will actually load the iptables. I did some tests and from what I understand I can see that this is true because I have allowed access to certain torrent trackers, and denied access to others, and I can see some come online. Does firestarter load iptables once the user logs in? Or once it fails to load, does it not load at all unless you manually open/load the application. If firestarter just modifies iptables, then once I save my listings in firestarter then I really don't need it to start up correct?
Using x11vnc server on Debian host, and TightVNC viewer client on Windows 7. All was working fine until a server host upgrade, from Wheezy to Jessie. Now, when I try to connect, TightVNC retrieves the certificate as normal, compares and accepts it, and starts stunnel. The next step would normally be to prompt for the VNC password.
Instead it gives an error:
ReadExact: Socket error while reading.
I'm guessing that some thing is missing or misconfigured after the Jessie upgrade, which broke many other things too, as Debian upgrades always seem to do. I have removed and reinstalled the x11vnc package, no effect.
The errors in the log file don't mean a lot to me.
I upgraded fro Jaunty to Karmic and then to Lucid and my TV card has stopped working. I had been informed that this was a result of the splitting of the linux-firmware into two separate packages, but having installed the linux-firmware-nonfree package the problem persists. The card is a Hauppauge WinTV PCI and although it is properly recognised by commands like lsmod, lspci and in the sound card settings, I can't tune in a single channel. It worked out of the box in Jaunty. Is there anything else that needs to be done to get the nonfree firmware working properly?
summary: `sudo aptitude full-upgrade` (to jessie) ran long time before hanging @
Code: Select allSetting up fancontrol (1:3.3.5-2) ... Installing new version of config file /etc/init.d/fancontrol ... [ ok ] Stopping fan speed regulator: fancontrol.
Killing the job produced damage detailed below. How best to proceed?
details:
I'm upgrading a 7-year-old 64-bit Clevo/System76 laptop to jessie. My first run of `sudo aptitude full-upgrade` ended after fetching packages, with the following lines ending the console spew:
Code: Select allGet: 2051 http://http.debian.net/debian/ jessie/main user-setup all 1.61 [196 kB] Fetched 1,816 MB in 17min 38s (1,715 kB/s) E: This installation run will require temporarily removing the essential package python:amd64 due to a Conflicts/Pre-Depends loop. This is often bad, but if you really want to do it, activate the APT::Force-LoopBreak option. E: Internal Error, Could not early remove python:amd64 (2)
So I started a second run with `sudo aptitude -o APT::Force-LoopBreak=true full-upgrade`. I left it running overnight, checking back periodically to OK overwriting `/etc/*` files with package-maintainer's versions. Friday I checked the box ~0900 and found
Only GUI application running was `gnome-terminal`, with the upgrade running in a single tab. This was working as intended, since I closed all other apps, and all but one `gnome-terminal` tab, before starting the upgrade. desktop environment (DE)=Cinnamon (also as intended) mouse was non-responsive: swiping the touchpad produced no movement keyboard appeared non-responsive (but more on that below) internal fan was running apparently full-speed (certainly as loud as I've ever heard it) console spew ended with the following 3 lines:
Code: Select allSetting up fancontrol (1:3.3.5-2) ... Installing new version of config file /etc/init.d/fancontrol ... [ ok ] Stopping fan speed regulator: fancontrol.
I left it running in hope the upgrade would recover, but after 7 hours nothing had changed, so I attempted to kill the job. The following all failed:
invoking shutdown via desktop menu (neither mouse movement nor pressing Super key produced any change) C-c/Ctrl-c in the terminal tab (nothing changed in the GUI) A-F2/Alt-F2 (trying to run another `gnome-terminal` to run `sudo shutdown -Ph now`, but no dialog appeared) C-A-F1 (to goto tty1 and run `sudo shutdown -Ph now`, but again no change in GUI/X)
The good news is, the box did reboot after `A-SysRq-[REISUB]`, though only to tty1. From there, `sudo dpkg --audit` produces these results.
So obviously the upgrade is incomplete; how best to resume it, or to debug the current situation before resuming? I'd prefer to fix the problem with `fancontrol` before proceeding, since the previous `full-upgrade` was quite long-running.
FWIW I also recorded the packages that the previous/broken `aptitude full-upgrade` wanted to {add, remove, upgrade}, and note that package=`fancontrol` is one that `aptitude` wanted to upgrade. So I'd like to know if I should just
Configure unpacked-but-not-yet-configured packages as directed by `dpkg --audit` reconfigure only-half-configured packages as directed by `dpkg --audit` process triggers for packages awaiting processing of triggers as directed by `dpkg --audit` reinstall packages missing md5sums as directed by `dpkg --audit` create a list of packages to remove (from those listed in the previous upgrade) add `fancontrol` to that list run `sudo aptitude remove [list of packages]` from tty1 create a list of packages to add and upgrade (from those listed in the previous upgrade) delete `fancontrol` from that list run `sudo aptitude install [list of packages]` from tty1 rerun `sudo aptitude full-upgrade` from tty1 (hoping that cleans up any remaining upgrade work, and does not try to reinstall package=`fancontrol`)
The following is a subset of error messages I'm getting when trying to do "apt-get upgrade" or "apt-get dist-upgrade" on a machine running ubuntu server 9.10 amd64:
Code: Preparing to replace linux-image-2.6.31-22-server 2.6.31-22.60 (using .../linux-image-2.6.31-22-server_2.6.31-22.65_amd64.deb) ...
