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 want to try something. Is there anyway I can capture a log of what's happening when I go to open a movie and it fails? I have VLC player as well as Movie Player that comes with Ubuntu. This may she more light as to what is happening.
Yes, you can do that. Usually, if the application is not making its own log somewhere, we would start it from a console, and use shell redirection to send all output to a file, like so:
shell$ vlc 2>&1 >> some_file
That will redirect all output to the file called "some_file". If the application (vlc in my example) is producing meaningful output when a problem occurs, it should appear in the file. Basically, the file will capture all the stuff that normally goes onto your console window.
NOTE: WHen wanting to start an application like this, check the manpage to see if there are any additional options that the application can accept, to make it more verbose or to make it output additional information (more than it usually would). Commonly -v or --verbose are used to make an app more verbose.
OK, I haven't got vlc installed, but internet claims that it has a --help option. In a terminal type:
That will show you options that vlc can accept when you run it. See if there's a "--verbose" option, or a "--debug" option, something that says it will make the program output more information. If so, add it to the command I gave earlier, like so:
vlc --debug >> my_output_file 2>&1
Now use the application, and again, when done, examine the file created (named "my_output_file" in this example..
If there's no verbose or debug or similar option, then I do not know of a way to make it tell us what it's problem is. Perhaps then try `cheese` as suggested by MTK358
The program 'totem' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadAlloc (insufficient resources for operation)'.
(Details: serial 578 error_code 11 request_code 132 minor_code 19)
(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.)
If that's correct, and there's a bug in the program, there's not much you can do but report the bug and/or use another program, and/or fix the bug. Or maybe see if there's a newer version of the program, that has already been fixed (check your Synaptic tool for that).
Sometimes I'll search Google for the error message and see what other people have discovered about it. I would search for, in this case:
totem BadAlloc (insufficient resources for operation)
and see if anything turned up that made sense to me.