-   Linux - General (
-   -   Mouse daemon log to determine cause of crash? (

theKbStockpiler 03-04-2013 10:31 AM

Mouse daemon log to determine cause of crash?
If my mouse or desktop crashes and I can log in without X running I kill my browser which is usually the cause and then log back on to the GUI terminal. Is there a precise way to tell what and why the mouse will freeze or the desktop will not respond, a log maybe?

Thanks in advance!

fortran 03-05-2013 12:17 AM

Is your GUI crashed because of firefox and does it give stop script error before crashing?

Habitual 03-05-2013 06:32 AM

The real question is why does firefox cause my desktop|mouse|firefox to crash?

Create a new firefox profile and try using that
Or a lesser (current -1) version of FF.
Or Disable all plugins.
and check ~/.xsession-errors

theKbStockpiler 03-05-2013 12:39 PM

Thanks for the replies!: I'll check X sessions
I don't get 'a script has stopped running' dialog box and I just used a browser as an example. All of my browsers do crash occasionally except for lynx and dillo. I posted a question similar to this before and I think the consensus was to restart X which is pretty close to rebooting and we don't reboot linux to fix a crash of coarse. I got fed up and and opened up a text console and 'killlall opera' and mouse worked once again. This is much better than restarting X. What I was thinking of is to kill whatever has control over the mouse but X should only have control over the mouse so I need to know how/why an application has the ability to make the mouse useless. Data should go from the mouse controller to X and then X needs to send data to the application that should be using it. This is simplified of coarse but I started this thread to make it more precise.

"Opera has crashed". So what. Why does'nt the mouse freaking work?:scratch:

All times are GMT -5. The time now is 11:57 AM.