Linux - SoftwareThis forum is for Software issues.
Having a problem installing a new program? Want to know which application is best for the job? Post your question in this forum.
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.
Hi all: I've got this apparently unknown error while running Xgl on my Dapper (full) box, and it reads like this:
"BadLength (poly request too large or internal xlib.....)"
"major opcode: 143 (GLX)"
"minor opcode: 1 (GLX_Render)"
"serial number: 113"
"current serial: 114"
This is stripped down of course, but it's the actual error I'm getting right now.
Not sure what to do at this point, so any assistance would come in handy. :P
EDIT: I noticed that when my kubuntu boots up, and KDM is loaded, the screen just stays on gray with the cursor
as an hourglass, which I can move with the mouse. UPDATE: This happens with startx as well.
EDIT: When run from terminal using startx (as my normal user), I usually get a "caught signal 11" error from X.
P4 2.4 Ghz w/o HT
RAM: 1 Gig
Two 120 GB hard drives
ATI Radeon 9550 256 MB
and so on.
I'm running kernel version 2.6.17, compiled as DEBs and installed that way.
(Can't read my logs right now since I'm posting from another computer, but would gladly post them if you want me to.)