Puppy Linux Discussion Forum

Compiz-Reloaded SFS for Fatdog64-901 is available. Get it with SFS Manager (Control Panel > System).

Compiz-Reloaded is a compositing window manager with legendary visual effects. The Emerald Window Decorator and several stock themes are included. More themes can be downloaded from various internet sites.

Considering that I could only test this SFS on my main desktop system with Intel graphics and in QEMU, I suppose that some issues may surface with non-Intel graphics cards.

Please read and follow closely the instructions provided in the introductory help dialog.

Please report problems and, if you know them, solutions to this thread.

This SFS is an evolution of the wonderful Compiz-Reloaded SFS that @JakeSFR created for Fatdog64-720 and 8xx.

Enjoy

reserved

Issue: keyboard not working in vncviewer

Description

Local and remote systems run compiz.
Remote system runs x11vnc VNC server.
Local system runs TigerVNC vncviewer and connects to remote system: in vncviewer mouse works OK but keyboard is dead.

Work-around

Local system: Stop vncviewer; switch window manager to Openbox; restart vncviewer.

At first, I was testing it under a 'testuser' and the only bad thing I found is that gmenu2 doesn't work:

testuser$ gmenu2
reading ihe file: /tmp/runtime-testuser/gmenu2_testuser/gmenu2
New icon size = 24.
gtk_icon_theme_lookup_icon can't open 'org.gnome'
gtk_icon_theme_lookup_icon can't open 'org.gnome'
assuming a command string: /home/testuser/.gmenu2.log
variable "REFRESH_CACHE" defined but never used.
variable "THISFILE" defined but never used.
Error messages for 1 lines were suppressed. Rerun with option -i to view.

I checked and my old gmenu works fine.

As for root, I imported my old profile and everything just works, as before.

Great job, Steve, thanks!

Cheers!

@JakeSFR, thanks for testing

JakeSFR wrote:

At first, I was testing it under a 'testuser' and the only bad thing I found is that gmenu2 doesn't work:

Good catch. It turns out this error is due to gtkmenuplus. Fixed for the next version of gtkmenuplus, which is due for an update.

As regards the Compiz-Reloaded SFS, you could see this error message if file $HOME/.gmenu2.log doesn't exist before running gmenu2, that is, before right-clicking an empty area of the desktop when compiz is the window manager.

As a temporary remedy, before loading the SFS for the first time, run the following commands from a terminal window:
touch $HOME/.gmenu2.log; chmod 600 $HOME/.gmenu2.log
(there is a period before "gmenu2").

AMD/Radeon bare metal system, seems to work OK, at least for a very limited test (cube, wobbly windows, min/maximize effects etc.).

Issue: xdotool windowactivate

Description

xdotool windowactivate <window-id> and xdotool windowfocus <window-id> don't activate the window. Neither does wmctrl -a -i <window-id>.

after some system cleanup I can confirm JakeSFR's results: xdotool windowactivate works in compiz / openbox; wmctrl -a doesn't.

Hmm, xdotool works for me (both commands), but wmctrl doesn't.

EDIT: wmctrl doesn't work also under Openbox (testuser).

Greetings!

Issue: dunst 1.9.0's notifications still cannot be dismissed under Compiz.

Dunst 1.1.0 from 720 works ok, IIRC.

Greetings!

@JakeSFR, yes, I noticed that too. As a work-around I use a keyboard shortcut to dismiss notifications. Mouse clicks don't work.
This is the Shortcuts section of my ~/.config/dunst/dunstrc file -- viewtopic.php?p=113882#p113882

# Close notification.
close = ctrl+1

# Close all notifications.
close_all = ctrl+shift+1

# Redisplay last message(s).
# On the US keyboard layout "grave" is normally above TAB and left
# of "1". Make sure this key actually exists on your keyboard layout,
# e.g. check output of 'xmodmap -pke'
history = ctrl+grave

# Context menu.
context = ctrl+shift+grave

seems that this might be a chrome only issue, but with wobbly windows turned on and then trying to move the window by grabbing the title bar is horrendous. All other windows don't seem to have an issue.

IIRC, when Ubuntu included compiz some users reported issues with chrome. I just tested wobbly windows with Vivaldi (chromium-based) and it works fine.

edit: I just tested also chrome-official installed via Control Panel "Get Google Chrome" and wobbly works OK for me (Intel graphics).

With Chrome when I move the window, or double click the title bar to maximize it, the cursor grabs the window and will not let it go. I have figured out if I press enter it lets go of the window, but it was almost mouse breakingly annoying for a bit there.

Another annoyance, alt+ window move won't let me move a window above the top of the screen. I have a daily use case where this is my desired behaviour, so compiz is probably out for me.

Shame, my kids loved drawing fire on the screen, and stars and snowflakes and wobbly windows and all the cool things that compiz does.

Thanks for your hard work in getting this to work Steve

step wrote:

@JakeSFR, yes, I noticed that too. As a work-around I use a keyboard shortcut to dismiss notifications. Mouse clicks don't work.
This is the Shortcuts section of my ~/.config/dunst/dunstrc file.

Thanks. I copy-pasted it to ~/.config/dunst/dunstrc file, but got this:

# dunst -conf ~/.config/dunst/dunstrc 
WARNING: Invalid config file at line 2: Key value pair without a section.
WARNING: Invalid config file at line 5: Key value pair without a section.
WARNING: Invalid config file at line 11: Key value pair without a section.
WARNING: Invalid config file at line 14: Key value pair without a section.

p310don wrote:

With Chrome when I move the window, or double click the title bar to maximize it, the cursor grabs the window and will not let it go. I have figured out if I press enter it lets go of the window, but it was almost mouse breakingly annoying for a bit there.

Yeah, I can reproduce it, too (radeon).
The workaround is to enable Settings -> Appearance -> Use system title bar and borders.

Another annoyance, alt+ window move won't let me move a window above the top of the screen.

Go to CompizConfig Settings Manager -> Window Management -> Move Window and uncheck Constrain Y.

Greetings!

JakeSFR wrote: ↑Tue Mar 12, 2024 1:24 pm

Code: Select all

# dunst -conf ~/.config/dunst/dunstrc 
WARNING: Invalid config file at line 2: Key value pair without a section.

Insert [global] as line 1 of the file. Dunst settings are grouped under a section heading. See also /etc/xdg/dunst/dunstrc.

Ok, now it works, thanks!

[EDIT]
I compared dunst code in v1.9.0 with v1.1.0 and it seems that it's only a matter of changing ButtonRelease to ButtonPress in src/x11/x.c to make it dismissable by clicking under Compiz.

                case ButtonRelease:
                        LOG_D("XEvent: processing 'ButtonRelease'");
                        if (ev.xbutton.window == win->xwin) {
                                x_handle_click(ev);
                                wake_up();
                        }
                        break;

That was the first thing I tried and it worked right away.

There are still these warnings (especially no. 3):

WARNING: No icon found in path: 'dialog-information'
WARNING: BadAccess (attempt to access private resource denied)
WARNING: Unable to grab mouse button(s).

but nothing blew up so far.

Greetings!

edit: fixed for the next Fatdog64 release version

Feedback in this thread seems to be drying out. If nothing substantial comes out, next week I will release a final version, and leave the thread as a compiz user-to-user tip exchange forum.

Did anyone try fusion-icon? Fusion-icon is new to the Compiz-Reloaded SFS.

I installed Compiz Reloaded using sfs-manager .
I confirm it's working with proprietary driver from Nvidia .
I closed picom as it's not needed .
Same issue with Google Chrome , but the pointer is released when I push the Enter key .
The keyboard shortcut works too , in my case , for closing the dunst notification . Thank you @step , for the tip !

The Fusion-icon shows correctly in the panel's Tray . The left click rise the menu of it , as does the right click .
The elements of it's menu work well .

I observed one issue . Left clicking on the desktop leaves conky all right , but when I right click for the Compiz menu
, the first click it's OK , but the second right click acts like a switcher , conky disappears . Next click it conky shows again it's window , and so on.

Gobbi wrote: ↑Fri Mar 15, 2024 7:57 pm

Same issue with Google Chrome , but the pointer is released when I push the Enter key.

Thank you for testing! I think most chrome/chromium browser makes will behave this way because by default they replace the basic window title bar with their own. JakeSFS posted a work-around in this thread describing how to configure chrome to use the basic title bar. Vivaldi browser has a similar setting under a different name.

I observed one issue . Left clicking on the desktop leaves conky all right , but when I right click for the Compiz menu
, the first click it's OK , but the second right click acts like a switcher , conky disappears . Next click it conky shows again it's window , and so on.

I can reproduce similar weirdness but with the primary mouse button. I believe it's due to different running programs all subscribing to the same mouse button event. A work-around I use is to press the Escape button, in lieu of clicking the desktop, to dismiss the compiz desktop menu.