DebianThis forum is for the discussion of Debian Linux.
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've upgraded from stable to testing. In stable, iceweasel performed flawlessly as I expected. Now it crashes at random times at an alarming rate. It does seem that I can recreate the crash to an extent on youtube, where crashes are the most prevalent.
I haven't located any bug reports regarding this issue with wheezy iceweasel.
Same random crashes, after an update lately, but I can't figure which package has done it. Crashes also with gmail, which is really annoying. Konqueror runs well, but gmail is in simple-html mode.
Running Wheezy, Iceweasel 3.5.17-1. System up-to-date.
running iceweasel with debugging symbols (iceweasel -g --sync) I get
Starting program: /usr/lib/iceweasel/firefox-bin --sync
[Thread debugging using libthread_db enabled]
[New Thread 0xb5affb70 (LWP 10045)]
[New Thread 0xb52f7b70 (LWP 10046)]
[New Thread 0xb47ffb70 (LWP 10047)]
[New Thread 0xb3dffb70 (LWP 10051)]
[New Thread 0xb32ffb70 (LWP 10052)]
[New Thread 0xb2afeb70 (LWP 10053)]
[Thread 0xb32ffb70 (LWP 10052) exited]
[Thread 0xb2afeb70 (LWP 10053) exited]
[New Thread 0xb22fdb70 (LWP 10054)]
[New Thread 0xb1afcb70 (LWP 10055)]
[Thread 0xb1afcb70 (LWP 10055) exited]
[Thread 0xb22fdb70 (LWP 10054) exited]
[New Thread 0xb1afcb70 (LWP 10057)]
[New Thread 0xb22fdb70 (LWP 10058)]
[New Thread 0xb32ffb70 (LWP 10059)]
[Thread 0xb22fdb70 (LWP 10058) exited]
[Thread 0xb32ffb70 (LWP 10059) exited]
[New Thread 0xb22fdb70 (LWP 10060)]
[New Thread 0xb32ffb70 (LWP 10061)]
[New Thread 0xb2afeb70 (LWP 10062)]
[New Thread 0xa9abbb70 (LWP 10063)]
[Thread 0xb22fdb70 (LWP 10060) exited]
[New Thread 0xb22fdb70 (LWP 10065)]
[New Thread 0xa90ffb70 (LWP 10066)]
[Thread 0xa90ffb70 (LWP 10066) exited]
[New Thread 0xa90ffb70 (LWP 10068)]
[Thread 0xb3dffb70 (LWP 10051) exited]
The program 'firefox-bin' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadRequest (invalid request code or no such operation)'.
(Details: serial 66481 error_code 1 request_code 139 minor_code 39)
(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.)
[Thread 0xb22fdb70 (LWP 10065) exited]
[Thread 0xa9abbb70 (LWP 10063) exited]
[Thread 0xb2afeb70 (LWP 10062) exited]
[Thread 0xb32ffb70 (LWP 10061) exited]
[Thread 0xb1afcb70 (LWP 10057) exited]
[Thread 0xb47ffb70 (LWP 10047) exited]
[Thread 0xb52f7b70 (LWP 10046) exited]
[Thread 0xb5affb70 (LWP 10045) exited]
[Thread 0xa90ffb70 (LWP 10068) exited]
Program exited with code 01.
Did anyone manage to fix it?
Last edited by StriDer999999999; 03-30-2011 at 06:24 PM.
Reason: added debugging output