Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
I have Kubuntu-desktop installed on Linux Mint (Daryna). I just love the KDE desktop, much more than Gnome that I had been using for the past 6 months.
Only problem is, KDE has a very, very high propensity to crash. About once an hour. It can happen at any time, when browsing, clicking on an icon, there doesn't seem to be a clear pattern. The screen goes black and I am taken back to the login screen.
I wish I could find the crash report to post here but... I don't know where to find it. Probably stored somewhere in a file, but where? Then I'll probably need help to understand what's wrong, but first how do I get this report??
Do you mean to say that you have installed KDE desktop on Linux mint?? Please clarify :-}
That actually doesn't sound like a 'crash' but rather some sort of (mis)configuration problem. A crash would more likely lock up KDE or lock up the app you were using. Sounds more like something's amiss with X and is throwing you out to the login screen.
Check that your system clock is correct, first, and that it matches the hardware (BIOS) clock in your machine (to within a minute or so at least). An incorrect clock can, interestingly, cause very odd behaviour, particularly with X screensavers and KDE's internationalization & timezone components.
I haven't any advice just yet, but:
1 - can you determine EXACTLY how long between episodes? Is it really random, or is it happening at precise intervals?
2 - Did this start after installing or upgrading a certain component? Such as when you installed KDE? If not, what has changed before this all started?
3 - If you have a screensaver daemon running, disable it. See if the issue still happens with no screensavers running.
Most error logs are stored in /var/log/... So you might want to examine the xorg.0.log file, as well as any KDE-specific log files, for some indication of what is really going on.
Good luck; if you get any further info, please post it for us.
Ok, I may (but only may) have been too quick at blaming KDE, since I just switched to XFCE and the same thing happened.
GrapefruitGirl: I meant that I have Linux Mint (daryna) and installed KDE via sudo aptitude install kubuntu-desktop. The crashes have been starting ever since I installed kubuntu-desktop, I believe.
Ok, so I looked through the messages in /var/log, as you guys recommended, but found no new message after the crash in most of these, so I won't post them, except for syslog, the interesting one. The reason I say I still think it's related to KDE is, if you look at 11:24, the culprit seems to be kdm. (Why is kdm still running even though I logged into XFCE...??)
('ps -e' yields:
5237 ? 00:00:00 kdm
16430 ? 00:00:00 kdm
May 22 10:07:32 thomas-laptop modprobe: WARNING: Not loading blacklisted module ipv6
May 22 10:07:42 thomas-laptop last message repeated 2 times
May 22 10:09:23 thomas-laptop last message repeated 59 times
May 22 10:12:43 thomas-laptop modprobe: WARNING: Not loading blacklisted module ipv6
May 22 10:13:47 thomas-laptop last message repeated 44 times
May 22 10:14:40 thomas-laptop last message repeated 31 times
May 22 10:15:53 thomas-laptop modprobe: WARNING: Not loading blacklisted module ipv6
May 22 10:16:00 thomas-laptop kdm: X server for display :0 terminated unexpectedly
May 22 10:16:18 thomas-laptop modprobe: WARNING: Not loading blacklisted module ipv6
May 22 10:16:21 thomas-laptop NetworkManager: <info> Updating allowed wireless network lists.
May 22 10:17:01 thomas-laptop /USR/SBIN/CRON: (root) CMD ( cd / && run-parts --report /etc/cron.hourly)
May 22 10:17:10 thomas-laptop modprobe: WARNING: Not loading blacklisted module ipv6
May 22 10:21:18 thomas-laptop modprobe: WARNING: Not loading blacklisted module ipv6
May 22 10:21:21 thomas-laptop modprobe: WARNING: Not loading blacklisted module ipv6
May 22 10:24:46 thomas-laptop modprobe: WARNING: Not loading blacklisted module ipv6
May 22 10:25:23 thomas-laptop modprobe: WARNING: Not loading blacklisted module ipv6
May 22 10:30:40 thomas-laptop modprobe: WARNING: Not loading blacklisted module ipv6
May 22 10:36:04 thomas-laptop modprobe: WARNING: Not loading blacklisted module ipv6
May 22 10:36:05 thomas-laptop modprobe: WARNING: Not loading blacklisted module ipv6
May 22 11:02:25 thomas-laptop -- MARK --
May 22 11:17:01 thomas-laptop /USR/SBIN/CRON: (root) CMD ( cd / && run-parts --report /etc/cron.hourly)
May 22 11:24:07 thomas-laptop kdm: X server for display :0 terminated unexpectedly
May 22 11:24:24 thomas-laptop modprobe: WARNING: Not loading blacklisted module ipv6
May 22 11:24:24 thomas-laptop NetworkManager: <info> Updating allowed wireless network lists.
Oh, I forgot, could it have to do with "Not loading blacklisted module ipv6"?
Last edited by chadefa1; 05-22-2008 at 10:38 AM.
Reason: Forgot additional remark
No guarantees, but I venture to guess that the IPv6 module (or lack thereof) is not causing the problem. That said, I wonder why the system is trying endlessly to modprobe it... In any event, I doubt that X is trying to use the module.
KDM is running because that is the desktop/login manager that you are using. You can use others including XDM (X desktop mgr) and GDM (Gnome desktop mgr) to manage the login functions, regardless which desktop environment you are actually using.
The culprit may not yet be KDM. KDM appears to simply be reporting the crash (it DOES look like a crash now, but of X, not the KDE desktop environment itself).
Have you checked the xorg log? Nothing of interest? Check a couple of the previous X logs too, assuming you have a couple archived in /var/log.
Check /var/log/dmesg for the last operations recorded before the crash, if any.
I have highlighted a few lines & areas of the xorg.0.log file you posted. I am not really sure they are relevant to the problem, but they are stuff that I have never seen in an X log, and might be indicative of part of the problem.
What I am leaning towards is a problem with the video driver you are using or a module it is loading, and/or an issue with the video card or video BIOS. The card and/or driver might be causing the crash.
It looks from the log that your xorg.conf is rather complex-- lots of modules, multiple video devices (some of which are not being used) etc.. Can you simplify the configuration? Maybe comment out some modules you can do without for a while (like int10 in particular), and switch from whatever driver you are using, to the 'vesa' driver?
Performance will not be the same, but if the problem persists after these changes, we can eliminate the aiglx driver as the cause.
Your KDM log is also showing the Signal 11 (I think it's segmentation fault) and the last thing in the backtrace is
There seems to be some agreement that it only happens when Compiz is enabled (my case), AND potentially related to Yakuake (which I use all the time). Also, just like them, the crashes occur when I use a lot of applications, and never when the computer is idle.
So I'll try disabling Yakuake for a while (though how exactly am I supposed to live without it??), and see if the crashes still happen.
A backtrace is a record of what an application was doing (what code was executing) before it died, and is generally the type of stuff debugger people like to have with submitted bug reports so they can attempt to nail down a particular area of code that is causing a problem.
Good work @ finding a few reports from others who seem to have the same issue! Disabling the stuff (really as much stuff as possible) in question to narrow down the culprit is a good plan :-) keep us posted as to what you discover.
I noticed one odd thing: the crashes only seem to happen when I use emacs+tex (well, haven't tried emacs alone). Since the error message mentions something about "font" (11: /usr/bin/X(FontFileCompleteXLFD+0x1e1) [0x8076241]), could it be that emacs is related to this?
Don't quote me, but Emacs is AFAIK a pretty stable application of long standing. While *anything* is possible, I wouldn't suspect Emacs itself.
You may be onto something though, and the way to figure that out is to test it: Just do what you would normally do with Emacs & Tex, and see what happens :-)
I really don't know how to decipher that error message, except for what seems obvious: Something to do with X, and something to do with fonts.. I did just now Google that: "/usr/bin/X(FontFileCompleteXLFD+0x1e1) [0x8076241]" and lots of stuff: http://www.google.com/search?q=%2Fus...ient=firefox-a
was returned with the exact error message, so that would be where I would start :-) as the search results all seemed to do with X, aiglx, compiz, and Ubuntu.