SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
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.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I am using Slackware 13.1 and recently Xorg server
caused segmentation fault under KDE 4.4.3 twice. Here are listings from
Xorg.log files
Code:
Backtrace:
0: X (xorg_backtrace+0x3b) [0x80a1e6b]
1: X (0x8048000+0x57b75) [0x809fb75]
2: (vdso) (__kernel_rt_sigreturn+0x0) [0xffffe40c]
3: X (0x8048000+0xa7d28) [0x80efd28]
4: X (0x8048000+0xa7d28) [0x80efd28]
5: X (0x8048000+0xa671f) [0x80ee71f]
6: X (BlockHandler+0x58) [0x80638e8]
7: X (WaitForSomething+0x10c) [0x80a039c]
8: X (0x8048000+0x39bf0) [0x8081bf0]
9: X (0x8048000+0x1b3b5) [0x80633b5]
10: /lib/libc.so.6 (__libc_start_main+0xe6) [0xb7303b86]
11: X (0x8048000+0x1afa1) [0x8062fa1]
Segmentation fault at address 0x29db906c
Fatal server error:
Caught signal 11 (Segmentation fault). Server aborting
and
Code:
Backtrace:
0: X (xorg_backtrace+0x3b) [0x80a1e6b]
1: X (0x8048000+0x57b75) [0x809fb75]
2: (vdso) (__kernel_rt_sigreturn+0x0) [0xffffe40c]
3: X (xf86PostMotionEventP+0xcc) [0x80bc62c]
4: /usr/lib/xorg/modules/input/evdev_drv.so (0xb7305000+0x4781) [0xb7309781]
5: /usr/lib/xorg/modules/input/evdev_drv.so (0xb7305000+0x4a76) [0xb7309a76]
6: X (0x8048000+0x6d06f) [0x80b506f]
7: X (0x8048000+0x117774) [0x815f774]
8: (vdso) (__kernel_sigreturn+0x0) [0xffffe400]
9: X (0x8048000+0x39bf0) [0x8081bf0]
10: X (0x8048000+0x1b3b5) [0x80633b5]
11: /lib/libc.so.6 (__libc_start_main+0xe6) [0xb740bb86]
12: X (0x8048000+0x1afa1) [0x8062fa1]
Segmentation fault at address 0xd5
Fatal server error:
Caught signal 11 (Segmentation fault). Server aborting
I hope it maybe usefull for someone. I tried the Bugzilla to find if these problems are known, but honestly I don't understand much what
is the Bugzilla all about. Is it for developers?
segmentation fault == stack overflow (if the programmer isnīt sure what to echo) (sometimes)
K-4-Desktop seems to need huge resources (ram ?)
I also had got the hint that permission denied is uttered by seg fault.
What does tty /dev/tty1 at runlevel 2 3 (promt/nox-terminal) say when login (root,password/sudo/su root) startx ?
How to reproduce this problem? Does it happen randomly?
I used KDE 4.4.3 earlier without such problems. Sometimes dolphin crashed.
But Xorg the first time crashed today about 30 sec after KDE started.
The second restart also caused this error. The third restart of KDE
made X Server deaf for keyboard and mouse - I restarted the system remotely form the other computer (to avoid hard reset).
At this moment I am using fluxbox. I will try KDE again later.
I have P4 processor with 1GB RAM, nvidia fx 5500 card. I suppose it is
enough for KDE 4.4.x. But maybe I am wrong.
What does tty /dev/tty1 at runlevel 2 3 (promt/nox-terminal) say when login (root,password/sudo/su root) startx ?
I am not sure I understand well your question. I started KDE with xinit
(the system is in runlevel 3). After the crash I saw only a full list of
messages from KDE: about nepomukservices and unregistering the keys.
Seem like KDE complains that client (guess Xorg client) was killed and tries to make a clean up. Next time I copy the screen into a file or will run KDE under twm (there will be a heluva lot messages).
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.