Debian Multimedia :: X Won't Start After Upgrade To Jessie
Aug 22, 2015
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
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 --------------------------------------------------------------------------
Under wheezy, I could set gnome-terminal profile to partial transparency, i.e., to display the desktop wallpaper behind the text. (E.g., a picture of my girlfriend.) But after upgrade to Jessie, this option completely disappeared, and now I can only pick a solid color. Do I need to flip a setting or something to get this back? Am running default Gnome desktop (not fallback mode) though I think I only have 2D acceleration.
I recently upgrade from wheezy to jessie. I had a problem with the icons and solved it. Now when i place the xfce4-power-manager-plugin on the panel, the plugin is using more RAM than it needs. Currently its using 960 MiB. Yesterday it used about 3 GiB of RAM. It doesn't happen if the plugin is removed from panel.
Command in task manager: /usr/lib/x86_64-linux-gnu/xfce4/panel/wrapper /usr/lib/x86_64-linux-gnu/xfce4/panel/plugins/libxfce4powermanager.so 20 20972767 power-manager-plugin Power Manager Plugin Display the battery levels of your device and control the brightness of your display.
I upgraded from wheezy to jessie, but now I just boot to a console. I've gone through and made sure all packages are up to their latest versions, and I've made sure gnome, xorg, and xserver-xorg are reinstalled (during the upgrade they got uninstalled..).
Here's what happens when I run startx manually:
Code: Select allcharlie@asimov:~$ startx X.Org X Server 1.16.4 Release Date: 2014-12-20 X Protocol Version 11, Revision 0 Build Operating System: Linux 3.16.0-4-amd64 x86_64 Debian
[Code] ...
Note also that this whole time, gdm3 has been running:
I recently upgrade my system from Jessie to Stretch, with no problem. A little later I upgrades Enlightenment from e17 to e20, and at some point shortly after that the second screen stopped working.
The nvidia X Server Settings correctly identifies both screens. But Enlightenment and xrandr does not see the second one at all. The second screen are on and the pointer moves correctly onto it, but no activity with left or right click. I have tried with the original xorg.conf, and generated a new one with nvidia-xconfig, but no difference. No obvious errors in any log-files either.
lisa@kitten:~$ sudo uname -a Linux kitten 4.3.0-1-amd64 #1 SMP Debian 4.3.3-2 (2015-12-17) x86_64 GNU/Linux
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 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 have just did a fresh install debian jessie today in virtualbox, the X window manager is fxce. By default the default runlevel is 5, and I tried to change the /etc/inittab content:
Code: Select allid:3:initdefault:
and reboot, but it didn't effect to the result, the X-window auto loaded again >.<
I need to change it that will boot in to console mode first, and can run startx if necessary, how can I change it permanently?
After doing Debian's apt-get dist-upgrade from Wheezy/oldstable to Jessie/stable, I decided to try Kernel v4.2.0 instead of v3.16.0-4-amd64 to be even more updated. However, X doesn't work. /var/log/Xorg.0.log showed:
Code: Select allX.Org X Server 1.16.4 Release Date: 2014-12-20 [ 453.305] X Protocol Version 11, Revision 0 [ 453.305] Build Operating System: Linux 3.16.0-4-amd64 x86_64 Debian
I upgraded my Wheezy 7.8 to make sure all packages were installed Before taking the next step to upgrade to Jessie.I upgraded to Jessie and it seemed to run OK....but after reboot I had no network Connection..I checked ifconfig and the wrong network card mac address is being assigned to the wrong card....?I have a clonezilla server on my server, so this was my network interfaces before and after upgrade
Code: Select all# This file describes the network interfaces available on your system # and how to activate them. For more information, see interfaces(5). # The loopback network interface auto lo iface lo inet loopback
[code]...
I even checked nano /etc/resolv.conf and sure enough my gateway was the same for my Internet eth0.When I ran ifconfig I could see that the eth0 mac address was set as eth1..I tried to reset my drbl for clonezilla but that only sees the vmware Connection and not my actural cards.. have taken alook at /etc/udev/rules.d/70-persistent-net.rules and the assignment is right but not ifconfig?
With "quiet" removed from the grub linux line, I'm getting the following error messages when the boot hangs up early in the boot process (19.768231 seconds into boot).:
input: HDA NVidia HDMI/DP,pcm=3 as devices/pci0000:00/0000:00:01.0/0000:01:00.1/sound/card0/input6 input: HDA NVidia HDMI/DP,pcm=7 as devices/pci0000:00/0000:00:01.0/0000:01:00.1/sound/card0/input7 input: HDA NVidia HDMI/DP,pcm=8 as devices/pci0000:00/0000:00:01.0/0000:01:00.1/sound/card0/input8
/etc/gdm3/Xsession[3408]: ![1433316153,000,xklavier_evt_xkb.c:xkl_xkb_process_x_event/] #011ATTENTION! Currently cached group 0 is not equal to the current group from the event: 1
I installed a package (kicad) on my wheezy system using apt-get and it pulled down a shedload more files than I expected.When I restarted the system it turns out I've also been upgraded to
Release 8.0 Jessie Kernel Linux 3.2.0-4-amd64 GNOME 3.4.2
However I don't have gnome any more. Only XFCE.I tried
Reading package lists... Done.Building dependency tree.Reading state information... Done.Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming.
The following packages have unmet dependencies: gnome : Depends: gnome-core (= 1:3.14+3) but it is not going to be installed Depends: evolution (>= 3.12) but it is not going to be installed Depends: evolution-plugins (>= 3.12) but it is not going to be installed Depends: gnome-shell-extension-weather but it is not going to be installed Recommends: gnome-software but it is not installable
E: Unable to correct problems, you have held broken packages.
My /etc/apt/sources.list is
Code: Select all#
# deb cdrom:[Debian GNU/Linux 7.7.0 _Wheezy_ - Official amd64 NETINST Binary-1 20141018-13:04]/ wheezy main #deb cdrom:[Debian GNU/Linux 7.7.0 _Wheezy_ - Official amd64 NETINST Binary-1 20141018-13:04]/ wheezy main deb http://mirror.waia.asn.au/debian/ wheezy main deb-src http://mirror.waia.asn.au/debian/ wheezy main
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 recently have started playing with various distros (Mostly just Zorin and Debian) and have been trying to find a GUI I can actually comfortably use without wanting to punch my screen. This lead me to cinnamon which looks like something I could actually use.
I performed a fresh installation of Debian Jessie without the desktop environment and print server (System Utilities or whatever that option is called was left checked) and after the system installed and booted I proceeded to login as the root and install cinnamon. Unfortunately afterwards my system would be nothing but a black screen with a box saying that cinnamon had crashed and was running in fallback mode.
However if I let a fresh installation install the default GUI of xfce and then perform the cinnamon installation, cinnamon will install and run. My question is why doesn't a clean install with cinnamon work but installing cinnamon after another gui does? I don't get any apparent error messages beyond cinnamon crashing and I'm still fairly new to Linux.
Wakeonlan was working just fine with Wheezy on this machine. After upgrade, wakeonlan will resume from suspend but not from shutdown.
I have no problem with other machines (same software setup) after upgrade. None of my other machines have a broadcom NIC.
No BIOS settings were changed during the upgrade. If I enter the BIOS on boot and make sure settings are correct then 'save' and shutdown, without booting to debian, I can then successfully wakeonlan. Then, if I do not boot debian, but shutdown before debian starts, I can wakeonlan successfully again.
If I boot debian and then shutdown, game over: wakeonlan nolonger works.
$ ethtool eth0 | grep -i wake Supports Wake-on: g Wake-on: g
I installed Jessie with the RC1. URL...A2) The network install images for testing (jessie) can be found at URL...However, unless you want to test the installer for testing the better choice is to use the stable installer to install a minimal stable system and then upgrade to testing by changing your /etc/apt/sources.list file.
is it possible to simulate upgrading a Squeeze installation to a Wheezy or Jessie installation, on a OVH server ?I would like simulate upgrading server, and if not problems, upgrading in real time.I don't do that manipulation, and I don't do mistakes on a production server.
I upgraded my laptop from Debian Wheezy to Jessie the other day, and just as before my wifi auto-connects to my router, and I can "ping http://www.google.com" just fine, but only for like a minute. Then the Internet access dies, but I'm still connected fine to my router, and I can ping its IP address. If I connect to the router through cable / eth0 everything works just fine, and I have full Internet access.
I assume there is something wonky with how ip address is assigned after the upgrade, how can I fix this, or trouble shoot further?
I have an asus eee 1015px, which was running dualboot windows and wheezy with no problems (except the browsers seeming to take up a lot of CPU). Today having backed up everything, I wanted to upgrade to jessie. URL...
Everything seemed to be progressing fine, no strange messages, it took 1 hour for
Code: Select allapt-get upgrade
but maybe that's normal. However, then when I did
Code: Select allapt-get dist-upgrade
It froze at 17.30 with a weird screen. The sort of thing you never want to see on an install, a sad face and blocks instead of text. pic: URL...
Then it moved on and gave a readout, which seemed pretty ominous pic: URl...
It then moved and gave a readout, hanging again: pic3: URl...
Now it seems to be in loop, moving on every 15 minutes or so but always ending up with the same screenful of text shown in the foto below, which ends with the last line reading like this:
I upgraded from Wheezy to Jessie yesterday and no longer have sound. I don't think anything is muted. I checked alsamixer and everything is on. MOC, VLC, speaker-test and aplay are all giving me errors. MOC refuses to load.
Code: Select allccc@de:~$ speaker-test
speaker-test 1.0.28
Playback device is default Stream parameters are 48000Hz, S16_LE, 1 channels Using 16 octaves of pink noise ALSA lib pcm_dmix.c:1022:(snd_pcm_dmix_open) unable to open slave Playback open error: -2,No such file or directory Code: Select allaplay /usr/share/sounds/alsa/Front_Center.wav ALSA lib pcm_dmix.c:1022:(snd_pcm_dmix_open) unable to open slave aplay: main:722: audio open error: No such file or directory
Code: Select allccc@de:~$ mocp Running the server... Trying JACK... Trying ALSA... ALSA lib pcm_dmix.c:1022:(snd_pcm_dmix_open) unable to open slave Trying OSS...
I'm running a Debian derivative (Voyage linux).With the latest version based on Debian 8.0 Jessie and kernel 3.14.12 I have frequent pops, clicks and stutters in sound played through a USB dac, especially with higher resolution files. A previous version of this distribution worked fine, which was based on Debian 6.0.2 "Squeeze" and kernel 2.6.38. The files played are stored on a pata (to sata) device.I suspect I have an IRQ problem, I've made the following observations:
- The following processes are producing a combined 15-20% cpu load depending on the resolution currently being played. In the Squeeze based distribution these processes are not visible, so I'm not sure what that means. irq/15-ehci_hcd irq/15-ohci_ irq/15-pata_amd_hcd - ksoftirq is also slightly elevated at 1.6 when running 'Jessie' compared to 0 on the 'Squeeze' - The si line in 'top' seems also to be quite high (between 2 and 7) compared to when running 'Squeeze' (between 0 and and occasional 0.3). - system load is also quite high
Below I have the contents of /proc/interrupts. It seems the problem lies in irq 15 being shared between usb and pata device(s). I already tried adding a few kernel options but without results: a.o. pci=routeirq, acpi=off. The latter did change the order of irq15, moving the pata device one position up.
I have upgraded my debian server on april when Jessie came up, but I *forgot* to reboot at this time. As a new kernel* was released this week as a security update, and since my server installed it (via unattended-upgrade on security packages), I rebooted it last night. It never came back online.
I have access to a rescue boot (Ubuntu 12.04 LTS), and tried to analyse the failure (by mounting /sys /dev /proc and /boot and chrooting), but without luck so far.
As it's a dedicated server, I don't have access to the console. What I know :
No log in var/log since the failed reboot. I don't know how to have/find others logs.Previous kernel was 3.2.0-4-amd64, new is 3.16.0-4-amd64, What I tried without luck) :
Change the booting kernel, via update-grub. Tried 3.2, 3.2 with sysvinit and 3.16 rescue mode I think. I should have done it right, but without console it's hard to tell.apt-get update/apt-get upgrade/apt-get dist-upgradeadding nomodeset to kernel load in grubWhat I haven't tried :
update-initramfs, I don't really know why it would block the boot
I recently upgraded my debian system from jessie to stretch. Before then, I was mostly using hibernation instead of shutting off the laptop, to allow myself to get back faster to work the next day. Since my upgrade, though, it is impossible for me to resume from hibernation: after the normal boot sequence and the passphrase to decrypt my lvm partition, when it has loaded the information from RAM the screen just stays with a blinking "_" (underscore) in the top left corner.
I have hibernate and uswsusp packages installed. I also installed tuxonice-userui package to do some tests with the hibernate-ram and hibernate-disk commands. While using hibernate-disk (hibernate-ram didn't work, because "s2ram: unknown machine"), my system hibernates correctly, and I saw that during resume it was correctly loading everything from swap and then going back to the "underscore screen", confirming that the resume problem was happening after loading data from swap.
I tried booting using the recovery kernel in grub. For a time it worked, but today I didn't get the chance to make it work. The only solution was for me to boot my kernel by adding the "noresume" option to it, thus forcing it to restart.
I upgraded from deb7 to deb8, but am no longer able to boot. After passing the grub boot menu, the following messages are displayed:
Code: Select allLoading, please wait... [ 6.065713] systemd-fsck[148]: /dev/sda1: clean, 428644/1310720 files, 410616 9/52442880 blocks [ 7.480551] Error: Driver 'pcspkr' is already registered, aborting... [ 8.692700] systemd-fsck[341]: /dev/sda5: clean, 145485/6176768 files, 17407409/24695552 blocks [ 18.066215] Loading kernel module for a network device with CAP_SYS_MODULE (deprecated). Use CAP_NET_ADMIN and alias netdev- instead _
The screen then clears and an underscore is displayed as the sole character at the top left position of the screen. The system hangs at this point. During installation, I rejected two changed files: /etc/init.d/bootlogd and /etc/libreoffice/sofficerc. For both, I opted to keep the installed version (the default choice of the installer) rather than replacing with the new version. The first might be related to the problem, although it seems to be responsible only for logging the boot process, and I would not expect this to compromise booting.
In case this information is useful, sda1 is mounted at /, sda2 is swap space, sda3 is extended, and sda5 is a logical partition mounted at /home.
I am able to boot into rescue mode, but other than that the system is not usable. Unfortunately, no useful error messages are given to aid in diagnosing the problem.
