Arch Linux

ProzacR

Member

Registered: 2007-04-29

Posts: 272

xorg.conf deadly settings bug or sth?!

Section "Extensions"
  Option "Composite" "Enable"
End section

This part enables some nice efects, but after starting windows manager Openbox with them my system becomes very unstalble   Sytems badly crashes after Exit action, or after X command.

It is known bug? It hapens to everyone or only for me?

iBertus

Member

From: Greenville, NC

Registered: 2004-11-04

Posts: 2,228

Re: xorg.conf deadly settings bug or sth?!

Many people are using composite without any trouble. What type of video hardware are you using? It could be a bug in your video driver or another conflicting setting. I would caution that composite is not really 'rock solid' yet and should only be used if you can handle the odd crash without loosing critical data.

Cerebral

Forum Fellow

From: Waterloo, ON, CA

Registered: 2005-04-08

Posts: 3,108

Website

Re: xorg.conf deadly settings bug or sth?!

By the way, if you're using fglrx, it does not support composite, so you'll get odd behaviour.

ProzacR

Member

Registered: 2007-04-29

Posts: 272

Re: xorg.conf deadly settings bug or sth?!

I use old radeon card and mesa. Also I have fglrx-utls tried to remove it but mesa depends on it.

ProzacR

Member

Registered: 2007-04-29

Posts: 272

Re: xorg.conf deadly settings bug or sth?!

I fond partial solution. In Openbox menu "exit" action coded as poweroff. It looks like system crash as always mouse do move anymore and etc. but poweroff still runs normaly. At least I do not have to remove batery.

Another solution is to swich to startx terminal with ctlr+alt+fx and kill it with ctrl+c.

While testing other ways killing procesess with root I sow strange error: xorg unexpected signal: 15.

I hope this helps others or helps to remove bug.

Cerebral

Forum Fellow

From: Waterloo, ON, CA

Registered: 2005-04-08

Posts: 3,108

Website

Re: xorg.conf deadly settings bug or sth?!

if you just have fglrx-utils, and no fglrx kernel-module package, do you use the 'radeon' or 'ati' driver in xorg.conf?  If you do, you should install libgl-dri instead of fglrx-utils.

Try pacman -S libgl-dri  -- if it still complains about mesa depending on fglrx-utils, then force-remove it (pacman -Rd fglrx-utils) and install libgl-dri and mesa again (pacman -S libgl-dri mesa)

ProzacR

Member

Registered: 2007-04-29

Posts: 272

Re: xorg.conf deadly settings bug or sth?!

I use vesa driver. Now I installed libgl-dri... startedx... presssed ctrl+alt+bckp and same crash.

Cerebral

Forum Fellow

From: Waterloo, ON, CA

Registered: 2005-04-08

Posts: 3,108

Website

Re: xorg.conf deadly settings bug or sth?!

composite on vesa?  I think that's a bad idea - vesa doesn't support much in the way of fanciness - try the 'radeon' driver, it might give you better results.

ProzacR

Member

Registered: 2007-04-29

Posts: 272

Re: xorg.conf deadly settings bug or sth?!

radeon driver gives:
(EE) No devices detected.
I think my 8Mb mobility card is too old.

Cerebral

Forum Fellow

From: Waterloo, ON, CA

Registered: 2005-04-08

Posts: 3,108

Website

Re: xorg.conf deadly settings bug or sth?!

well crap.  I'm not sure what else to give you for advice, then.

iBertus

Member

From: Greenville, NC

Registered: 2004-11-04

Posts: 2,228

Re: xorg.conf deadly settings bug or sth?!

radeon driver gives:
(EE) No devices detected.
I think my 8Mb mobility card is too old.

I doubt your card is going to be compatible with xcomposite regardless of the driver used. 8MB of texture memory is too little for composited window managers.

ProzacR

Member

Registered: 2007-04-29

Posts: 272

Re: xorg.conf deadly settings bug or sth?!

It is not too low mem it is working normaly all time.

But when I try to turn it of everything turns of keyboard out mouse out just wallpeper remains and only way to exit is remove batery. Is is not memory problem it is critical bug somewhere.

Last edited by ProzacR (2007-08-26 16:27:18)