Slackware :: Several X-server Crashes Since Update From Last Monday
Jan 13, 2011
I'm running Slackware64-current. Since the upgrade of last Monday I'm experiencing several crashes of the X-server. It begins with an issue that one Window, e.g. Konsole or Firefox don't become active when clicking them. After some seconds the screen becomes dark and I end up on the console. First error I saw was from akonadi. Deinstalling akonadi didn't change anything. But there is an errormessage about a segmentation-fault in the Xorg.0.log. I'll append the logfile to this post. My graphics-card is an ATI HD5470 and have fglrx installed, downloaded from ATI. My kernel is
Code:
Linux samsung 2.6.35.10 #3 SMP Thu Jan 6 20:03:53 CST 2011 x86_64 AMD Athlon(tm) II Dual-Core M320 AuthenticAMD GNU/Linux
I recently upgraded to -current from 13.0 on my Dell Inspiron 1525 Laptop. It seems to have strange problems since then. The X crashes after sometime if I am running a video in firefox (flash based, say .....) in the full-screen mode. When I am not in the full-screen, it seems to run just fine. A similar thread was posted a few days back (http://www.linuxquestions.org/questi...rashes-846796/) and I thought I had overcome the problem using one of the suggestions provided, but apparently, I just had not run full-screen videos ever since (and I thought it was solved!). code...
I should mention that, the crash happened when I was running a video chat on gmail in full-screen mode too. I have the Xorg.0.log for that too, if it is going to be helpful. Also, one thing I noticed was that even Ctrl+Alt+b_space does not work when this crash happens!! (so, I have to go ahead and reboot the system using the power button everytime) This I find very strange, since if at all, I should have been able to kill the process and restart X.
This seems to be an extraordinarily long thread, but I have put in whatever I thought could be useful info I should give. I will appreciate any help in resolving this issue.
Less than 2 days ago i upgraded from slackware 13.0 to 13.1.Since then, I have not been able to use my laptop for more than 15-20 minutes, 'coz the KDE screen freezes all of a sudden without any crash report and in some time the screen goes blank with just a mouse pointer to be seen (Black Screen of Death?)I can do a CTRL-ALT-F* to switch to a console a continue, or reboot (using console) to get the X server started again. (CTRL-ALT-Backspace does not work either).
I'm wondering why everytime I install "recomended" updates, my KDE or X server crashes completely! is there any guide or advice you can give me to succesfully update only the packages that are really needed?
After I updated several software including Xorg server using "slackpkg update", I Ignorantly deleted configuration files without backing them up making Xorg server crashes.I try to build Xorg.conf using xorgsetup command but it crashes and spews:
Code: Fatal server error: Caught signal 11. Server aborting /usr/bin/xorgsetup: line 170: 3315 Aborted /usr/X11R6/bin/X -configure
I have a Radeon 4850 Graphic Card with ATI Catalyst as its driver, so I try to reinstall the driver hoping that it will fix the problem, which is a bad logic I admit it, and It fails to uninstall (for some reason the uninstall script is gone) and reinstall (problem with file extraction).
What a difference, using fglrx, this is like a new computer with this latest update. It runs a bit colder, flashplayer video actually goes all the way to the edge in fullscreen mode and no hardlocks yet (the kind with a blinking capslock light). Maybe fglrx isn't the only bad app in the village after all.
I just installed Slackware 13.37 on an old IBM Netvista and when I try to start KDE it gets through most of the splash screen and then crashes with the following error messages: Segmentation fault at address 0x4
Fatal server error: Caught signal 11 (Segmentation fault). Server aborting
[code]...
lspci shows I have an Nvidia chip: NV6 Vanta/Vanta LT rev 15 Other GUIs, such as Fluxbox, do not crash, so I think the problem may be with KDE, but I am at a loss. Has anyone seen or solved such a problem? I have not posted /var/log/Xorg.0.log because the KDE error message above seems more detailed.
I had been using Amaya on Slackware 13.1 32bit with no problems. I then upgraded to 64 bit, basically because of one program. Now, I cannot run Amaya. It crashes X. In my efforts to solve this I cannot find an X log with entries related to the crash. The console after the crash only shows the last lines of the output. I cannot scroll back to view the source of the errors. Is there a way to redirect error output from an X crash to a file for later analysis?
I just made a current iso and installed current and when I tried to start X the screen was washed out in a rainbow kaleidoscope pattern. I exited out and ran xorgset and Xorg -configure. Both of these hardlocked my system.
BTW Im using a geforce 8800GT. i tried installed the nvidia driver but it still locks when I run xorgsetup.
I have to go to work, so I will post the logs when I get home
I got an error : ./eclipse The program 'Eclipse' received an X Window System error. This probably reflects a bug in the program. The error was 'BadAlloc (insufficient resources for operation)'. (Details: serial 163951 error_code 11 request_code 53 minor_code 0) Note to programmers: normally, X errors are reported asynchronously; that is, you will receive the error a while after causing it. To debug your program, run it with the --sync command line option to change this behavior. You can then get a meaningful backtrace from your debugger if you break on the gdk_x_error() function.)
I googled and found some solutions by downgrading xulrunner, but no dice.
I've a ATI HD 4290 video-card and I installed the closed drivers of ATI/AMD. Everything worked fine until I updated Ubuntu. Yesterday, I received an automatic update from the Ubuntu-servers and I accepted this update.
But after I updated everything and restart my computer, X.org won't work. When I start my computer, I get this. (Translated: Your monitor, video card and your input devices couldn't be detected correctly. You have to choose manually the correct settings.)
I am running 64-bit current. I have not identified which update started the Dolphin crashes, but it recently has been happening very often, usually within a few seconds of starting it, but not always.
Googling suggested that it might be a dbus issue, so I rolled my own package using dbus-1.4.0 and the slackbuild from the 64 bit current source.
Dolphin has been rock solid since. I noticed that there was an 'allow root globally' patch which I commented out. I am guessing that this may affect applications that I have not used yet or the issue has been fixed in version 1.4.
I have not seen any evidence that other current users have had this problem, but maybe Robby would consider an upgrade?
I'm running SUSE 11.3 32-bit and have run into an issue with the KDE Plasma Desktop crashing after login. I've submitted a bug report with the KDE folks, but thought it might be OpenSuSE specific. Details from the my KDE bug report [URL].. is as follows:
Information about the crash: What I was doing when the application crashed: After updating my OpenSUSE 11.3 32-bit workstation to the latest (as of October 22, 4pm EST) available here:
I use Slackware 13.1 and eclipse 3.6 (Helios). When I do some programming the eclipse is always crashing. E.g.: class c, c.gwtC(); when I write the "." and the autocomplete is activated the eclipse crashes.
Since I installed Slackware 13.37 I'm having problems with Okular. Whenever you open a .pdf file, it crashes immediately. Opening other file formats works fine.
I have installed (twice) slackware 13.37 64 bit on a virtual machine (vmware workstation 7). But when i try to startx the kde window starts to load and the harddrive on the kde startscreen shows and then it crashes. Anybody that running slackware 13.37 on a virtual machine?
I've installed Slackware64 on a Toshiba Qosmio laptop (booting with ext4, SAMSUNG HM500JI HDD, 3 GB Ram, Intel Core 2 Duo Processor, Intel chipset and graphics).The system boots the huge kernel just fine. But after booting with the generic kernel AND after having prepared a mkinitrd with the mkinitrd generator, the boot process crashes at ~4sec with a panic.
After the last kde updates, when i try to set up the Sonar screensaver to ping 254 hosts it crashes KDE and returns to login screen. Does any one have that response from sonar or am i alone? Edit: slackware-current, no compositing, Asus EEEPC 1215N
First: I upgraded my slackware 13.0 last night (Philippine time) to -current. I just download the while current tree (except for source) and copied to my home dir, then do the slackpkg commands.
#1 Added a mirror to my home directory pointing the slackware-current tree. #2 slackpkg update #3 slackpkg install-new #4 slackpkg upgrade-all #5 slackpkg clean-system #6 lilo was configured #7 reboot
It successfully upgraded. Although I'm aware that I have installed openchrome driver and drm kernel module when it was slackware 13.0.
After a reboot, it crashes in between the boot time, if I was not mistaken, I read ACPI something on the bottom of the console, then the screen flickers and goes blank. It locks up there.
By the way, it is a laptop with VIA chipset on it.
(Using the Slackware 13.0 DVD, I booted using hugesmp.s root=/dev/sda3 rdinit= ro for the rescue.)
Trying to fix it by myself (no internet at home) I tried to look at /var/log/messages and cannot find what is the cause (newbie mode). I also tried to disable some services such as hald, httpd, mysqld, bluetooth, wicd, wireless, the old kernel and some others at /etc/rc.d/ by removing the execute bit.
After a restart, still the problem exists.
Now, I finally backup the whole home dir, moved to home-bak and decided to install the fresh slackware-current instead.
Second: I used the 13.0 installer, then setup slackware using the pre-mounted directory containing the slackware-current tree. I only deleted the files except for home-bak and not reformat the drive.
It actually installs, but after the reboot (using the new 2.6.32.3 kernel), still the problem persists.
I was using Fedora 9 until about 1 month ago when my hard drive crashed. I installed F12 on a new hard drive last week. Due to some other software issues (empathy), I decided I should try to get the latest updates. PackageKit kept giving errors and would not update. So, I researched and found that I needed to run " su -c 'yum update' " for the first update then PackageKit would work. I did this and after about an hour of updating, the screen went black. Nothing you can do at that point but hard reboot.
When I did that, I could only get a "GRUB" command line. I played with it for a minute but really I have no idea what to do with GRUB cmd (beyond my experience level). So I decided to wipe it out and reinstall F12. I did that, and was just working thru the updates again. Same thing happened, went to black screen. I have not rebooted it yet, but Im sure when I do, it will be GRUB again. What in the world am I supposed to do with this? I am not a Linux star, but I have been using it for around 8 years now with various distros, so I would say I have at least moderate experience.
The other day I fully updated (by updating all in repository unconditionally) to KDE 4.4 final. After that it seems amarok crashes when I try to start it. Here's the "Developer Information" from the crash.
Since I have updated last night from maverick to the latest beta of natty narwal, I'm having a lot of trouble getting Nautilus (desktop included) to work.
It seems to crash since the very start as when I turn off the computer, the message of "force exit" appears.
I just finished an install of Slack64 current and it's crashing when I try to start up KDE. I tried setting the VESA framebuffer to 'normal' in /etc/lilo.conf, but no dice.
Here's the log file: [URL]
GFX Card: Radeon HD 6850 (yeah I know.. this is probably the source of the conflict)
on a fresh install of slackware -current x64, the first thing that i did was download and install opera. now, whenever i start kde, and run opera, X crashes with lots of crazy errors, usually in the format of:
/usr/bin/akonadi*whatever* cannot connect to x server :0 /usr/bin/akonadi*whatever* has crashed too many times and will not be restarted.
and then i get spat back out at the CLI. opera works fine in the other Desktop Environments, and i'm posting from xfce right now, so i know its an issue with akonadi. i would like to use KDE as my default desktop, but i dont want to use it without all of its features
