[arch-general] default ~/.config/compiz/compizconfig prevents compiz start with radeonhd

2009-05-09 Thread David C. Rankin, J.D.,P.E.
Listmates,

I thought I would pass along a bug and a solution. I struggled trying 
to get 
compiz running on my arch x86_64 install on my laptop with the radeonhd 
driver for my x1200 card. After pulling my xorg.conf apart, swapping between 
the radeon and radeonhd driver and posting to the compiz list, I got the 
solution from a reply on the compiz list.

The problem is with the archlinux default 
~/.config/compiz/compizconfig/config supplied along with the 
compiz-fusion-kde package. The default is:

[kde_session]
profile = 

For some reason this prevents compiz from starting with either the 
radeon or 
radeonhd driver.

SYMPTOMS:

Upon Compiz start, the display behaves exactly like it is going to 
work. The 
display goes blank, sequentially erasing and redrawing each window, but then 
it never actually  starts. The windows are just left there with no decor. You 
can sill provide input to them, but you cannot move or resize them. Issuing 
kwin --replace  causes the reverse to happen (windows destroyed, black 
screen, windows then redrawn with kde decor.

SOLUTION(S):

From the compiz list, the suggestion was made to go ahead and let 
compiz try 
to start. Since you still have input capability, issue ccsm from the command 
line and then configure compiz forcing a new config to be written, then 
reload compiz. I did the equivalent, but took a shortcut by simply rsyncing 
~/.config/compiz from another working machine. Problem solved.

REMAINING ISSUES WITH ARCH GLX:

When issuing glxinfo from a konsole cli as $USER everything works fine. 
However, if you are su to root $UID then glxinfo fails:

[23:07 alchemy:/home/david] # glxinfo
No protocol specified
Error: unable to open display :0.0

Dunno if this is a bug or feature, but I thought I would pass it along. 
I'll 
file a bug report on the default config issue, fixing it will save a lot of 
folks a lot of heartache and newbies from thinking Linux doesn't work.


-- 
David C. Rankin, J.D.,P.E.
Rankin Law Firm, PLLC
510 Ochiltree Street
Nacogdoches, Texas 75961
Telephone: (936) 715-9333
Facsimile: (936) 715-9339
www.rankinlawfirm.com


Re: [arch-general] default ~/.config/compiz/compizconfig prevents compiz start with radeonhd

2009-05-09 Thread David C. Rankin, J.D.,P.E.
On Saturday 09 May 2009 03:09:37 David C. Rankin, J.D.,P.E. wrote:
 Listmates,

snip

   The problem is with the archlinux default
 ~/.config/compiz/compizconfig/config supplied along with the
 compiz-fusion-kde package. The default is:

 [kde_session]
 profile =

   For some reason this prevents compiz from starting with either the 
 radeon
 or radeonhd driver.

snip

Just fyi, I checked the default config for suse by creating a new user, 
starting compiz, and exiting. It is as follows:

[03:21 ecstasy:/srv/www/download/linux/compiz] # cat 
compizconfig-suse/compizconfig/Default.ini
[decoration]
as_command = kde-window-decorator --replace

[core]
as_active_plugins = 
core;ccp;place;move;resize;decoration;png;wobbly;cube;fade;minimize;rotate;scale;switcher;regex;workarounds;zoom;

My guess is that workarounds is what helped compiz get started with 
the 
default config. (That is only my guess though)

-- 
David C. Rankin, J.D.,P.E.
Rankin Law Firm, PLLC
510 Ochiltree Street
Nacogdoches, Texas 75961
Telephone: (936) 715-9333
Facsimile: (936) 715-9339
www.rankinlawfirm.com


Re: [arch-general] default ~/.config/compiz/compizconfig prevents compiz start with radeonhd

2009-05-09 Thread Edgar Kalkowski
Hi!

I think this remaining issue is because root is not normally allowed to connect 
to the X server. After issuing an „xhost +local:“ (the colon is essential) all 
connections from localhost should be allowed and thus it should work.

Ed




On Samstag, 09. Mai 2009, 10:09:37 David C. Rankin, J.D.,P.E. wrote:
 Listmates,
 
snip
 
 REMAINING ISSUES WITH ARCH GLX:
 
   When issuing glxinfo from a konsole cli as $USER everything works fine. 
 However, if you are su to root $UID then glxinfo fails:
 
 [23:07 alchemy:/home/david] # glxinfo
 No protocol specified
 Error: unable to open display :0.0
 
   Dunno if this is a bug or feature, but I thought I would pass it along. 
 I'll 
 file a bug report on the default config issue, fixing it will save a lot of 
 folks a lot of heartache and newbies from thinking Linux doesn't work.
 
 


signature.asc
Description: This is a digitally signed message part.


Re: [arch-general] default ~/.config/compiz/compizconfig prevents compiz start with radeonhd

2009-05-09 Thread Andrei Thorp
Think this should be fixed in the packages?

-AT

On Sat, May 9, 2009 at 3:37 AM, Edgar Kalkowski
em...@edgar-kalkowski.de wrote:
 Hi!

 I think this remaining issue is because root is not normally allowed to 
 connect to the X server. After issuing an „xhost +local:“ (the colon is 
 essential) all connections from localhost should be allowed and thus it 
 should work.

 Ed




 On Samstag, 09. Mai 2009, 10:09:37 David C. Rankin, J.D.,P.E. wrote:
 Listmates,

 snip

 REMAINING ISSUES WITH ARCH GLX:

       When issuing glxinfo from a konsole cli as $USER everything works fine.
 However, if you are su to root $UID then glxinfo fails:

 [23:07 alchemy:/home/david] # glxinfo
 No protocol specified
 Error: unable to open display :0.0

       Dunno if this is a bug or feature, but I thought I would pass it 
 along. I'll
 file a bug report on the default config issue, fixing it will save a lot of
 folks a lot of heartache and newbies from thinking Linux doesn't work.





Re: [arch-general] default ~/.config/compiz/compizconfig prevents compiz start with radeonhd

2009-05-09 Thread David C. Rankin
David C. Rankin, J.D.,P.E. wrote:
 On Saturday 09 May 2009 03:09:37 David C. Rankin, J.D.,P.E. wrote:
 Listmates,

 snip
  The problem is with the archlinux default
 ~/.config/compiz/compizconfig/config supplied along with the
 compiz-fusion-kde package. The default is:

 [kde_session]
 profile =

  For some reason this prevents compiz from starting with either the 
 radeon
 or radeonhd driver.

 snip
 
   Just fyi, I checked the default config for suse by creating a new user, 
 starting compiz, and exiting. It is as follows:
 
 [03:21 ecstasy:/srv/www/download/linux/compiz] # cat 
 compizconfig-suse/compizconfig/Default.ini
 [decoration]
 as_command = kde-window-decorator --replace
 
 [core]
 as_active_plugins = 
 core;ccp;place;move;resize;decoration;png;wobbly;cube;fade;minimize;rotate;scale;switcher;regex;workarounds;zoom;
 
   My guess is that workarounds is what helped compiz get started with 
 the 
 default config. (That is only my guess though)
 

The key wasn't simply workarounds but also needed was as_command = 
emerald
--replace.

3rd-time is the charm. I didn't like the way the earlier posts read, so 
for
conciseness, the following default configuration for the 2 files needed under
~/.config/compiz/compizconfig will get you going using the radeonhhd driver:

~/.config/compiz/compizconfig/config
[kde_session]
backend = ini
profile =

~/.config/compiz/compizconfig/Default.ini
[decoration]
as_command = emerald --replace

[core]
as_active_plugins =
core;resize;decoration;water;zoom;splash;png;minimize;workarounds;shift;wobbly;regex;place;firepaint;mousepoll;obs;fade;move;cube;showmouse;rotate;switcher;cubeaddon;scale;expo;

Additionally, (I didn't test this), but supposedly, you can just start 
compiz
(it will not be working), and then run ccsm (CompizConfig Settings Manager) and
make your setting changes, then restart compiz.

Now someone reading this thread can make sense of it and have all the 
needed
changes in a single post for the required compiz defaults.

-- 
David C. Rankin, J.D.,P.E.
Rankin Law Firm, PLLC
510 Ochiltree Street
Nacogdoches, Texas 75961
Telephone: (936) 715-9333
Facsimile: (936) 715-9339
www.rankinlawfirm.com