Community Packages

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#14639 - default ~/.config/compiz/compizconfig prevents compiz start with radeonhd

Attached to Project: Community Packages
Opened by David C. Rankin (drankinatty) - Saturday, 09 May 2009, 08:43 GMT
Last edited by Ronald van Haren (pressh) - Monday, 18 May 2009, 09:30 GMT
Task Type Bug Report
Category
Status Closed
Assigned To Ronald van Haren (pressh)
Architecture All
Severity Medium
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:

Arch on Toshiba 205D w/ATI X1200, kdemod3-complete, community/compiz-decorator-kde 0.8.2-1

My attempts to start compiz with either the radeon or radeonhd driver failed. 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.

ORIGINAL ARCH compizconfig/config

[kde_session]
profile =

ORIGINAL SUSE compizconfig/config
[kde_session]
backend = ini
profile =

ORIGINAL 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). However, I can tell you that with the default for arch compiz would not start. (let me know if I can send anything else). Thanks.
This task depends upon

Closed by  Ronald van Haren (pressh)
Monday, 18 May 2009, 09:30 GMT
Reason for closing:  Duplicate
Additional comments about closing:   FS#13926 
Comment by David C. Rankin (drankinatty) - Sunday, 10 May 2009, 00:49 GMT
To further confirm, I created another new user and the following defaults started compiz without a problem. Before making these changes, compiz wouldn't start as described in the original report:

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

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

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


** the as_command = emerald --replace was required.
Comment by Ronald van Haren (pressh) - Sunday, 17 May 2009, 09:00 GMT
Sorry I didn't see your report before.

Do I understand you correctly if I think this is a duplicate of  FS#13926  ?
Comment by David C. Rankin (drankinatty) - Sunday, 17 May 2009, 21:17 GMT
Ronald,

After revieweing http://bugs.archlinux.org/task/13926, the root cause of both seems to be the default ~/.config/compiz/.... configuration settings. From that stand point it looks like this bug can be considered a dup of task/13926 because fixing the default ~/.config/compiz/.... configuration will likely fix both bugs. Go ahead and mark this as a dup. However, make sure the information from this bug is not lost as it details exactly what needs to be fixed. Thanks.

Loading...