Bug 5190

(gdb) where
#0  0x00007f11120d8743 in __GI___poll (fds=<optimized out>, nfds=<optimized out>, timeout=<optimized out>) at ../sysdeps/unix/sysv/linux/poll.c:87
#1  0x00007f111094fd16 in g_main_context_poll (n_fds=3, fds=0x10dc980, timeout=5499, context=0x10a8ac0, priority=<optimized out>) at gmain.c:3417
#2  g_main_context_iterate (dispatch=1, block=<optimized out>, context=0x10a8ac0, self=<optimized out>) at gmain.c:3118
#3  g_main_context_iterate (context=0x10a8ac0, block=<optimized out>, dispatch=1, self=<optimized out>) at gmain.c:3060
#4  0x00007f111095017a in g_main_loop_run (loop=0x10a9be0) at gmain.c:3317
#5  0x00000000004024de in main (argc=<optimized out>, argv=0x7fff2742eef8) at /usr/src/debug/compiz-0.9.7.2/src/main.cpp:237

CC: (none) => herbert

Julien any ideas ?

Assignee: bugsquad => julien.moragny

ah yes you have a freeze push waiting, sorry

Yeah, that and an update to libcompizconfig which fix a bug with the glib main loop (could be related regarding the trace).

just tried with the versions (compiz and libcompizconfig) from the svn.
compiz-0.9.7.4-1.mga2.x86_64
lib64compizconfig0-0.9.5.94-0.bzr430.2.mga2.x86_64

0x00007f9cfb6e1743 in __GI___poll (fds=<optimized out>, nfds=<optimized out>, timeout=<optimized out>) at ../sysdeps/unix/sysv/linux/poll.c:87
87	  int result = INLINE_SYSCALL (poll, 3, CHECK_N (fds, nfds), nfds, timeout);
(gdb) where
#0  0x00007f9cfb6e1743 in __GI___poll (fds=<optimized out>, nfds=<optimized out>, timeout=<optimized out>) at ../sysdeps/unix/sysv/linux/poll.c:87
#1  0x00007f9cf9f58d16 in g_main_context_poll (n_fds=3, fds=0x2540990, timeout=3999, context=0x24ffb60, priority=<optimized out>) at gmain.c:3417
#2  g_main_context_iterate (dispatch=1, block=<optimized out>, context=0x24ffb60, self=<optimized out>) at gmain.c:3118
#3  g_main_context_iterate (context=0x24ffb60, block=<optimized out>, dispatch=1, self=<optimized out>) at gmain.c:3060
#4  0x00007f9cf9f5917a in g_main_loop_run (loop=0x2501100) at gmain.c:3317
#5  0x00000000004024de in main (argc=<optimized out>, argv=0x7fffaf8a4928) at /usr/src/debug/compiz-0.9.7.4/src/main.cpp:237

could be related to this bug :
https://bugs.launchpad.net/compiz-core/+bug/966814

can you try with options : 
gtk-windows-decorator &
compiz --replace ccp

?

no luck, JFYI, system session is gnome classic for now

I don't manage to reproduce :/ and i have no clue on what is the problem.

can you please open a bugreport upstream ?
https://bugs.launchpad.net/compiz-core/

sure, could you describe how you tested so that I can compare it with my tests?

i.e. what session do you select to start from?
how do you activate compiz?
what general setup for mageia cauldron do you use?
 - gnome or kde?
 - systemd or sysv?

just for the record, it is a vanilla Mageia 2b2 install (gnome desktop) upgraded to latest Cauldron, tested on two rather different systems (desktop vs laptop, ati vs intel vga), and I tried to start compiz in several ways from the default gnome3 session and from the gnome classic session.
no luck in either case, compiz just hangs ...

If it's useful, here is my experience ... (from an up-to-date Gnome desktop)

First, I've chosen 'compiz fusion' as 3d effects from drak3d which determined the installation of 55 packages - all went fine.
Then, I opened the compiz settings (ccsm) which started and apparently worked. I've ticked some animations there, then log out, log in ... and everything was as before (the expected animations didn't work).
I've logged out from Gnome shell and logged into Gnome Classic (fallback) and there, whichever application I opened every window was lacking the window title.

Finally, I undid all the changes (also removed the previously 55 installed packages) and windows appearance in Gnome Classic returned to normal.
Sorry I've forgotten to fire the compiz --replace command to see the results ... at request I can install compiz and all the dependencies again.

CC: (none) => gruescubogdan

@herbert : I've just tried from lxde, kde & gnome (shell & classic) without problem, albeit compiz --replace alone doesn't load decoration nor any plugin which is "normal". So you just get a window without anything else.

Just FTR, for the config to be loaded, you need ccp plugin (libcompizconfig) and load compiz with ccp option (compiz --replace ccp). To have decoration you need a decorator (gtk or kde-window-decorator) loaded before compiz.

Can you try with compiz-fusion-icon, it's a graphical launcher which take care of launching decorator, config plugin and allow to switch between window manager ?

I'm on x86_64 in virtualbox.
I wonder if I shouldn't just kill drak3d as it doesn't serve a real goal nowadays.

Created attachment 1923 [details]
before fusion-icon

Created attachment 1924 [details]
after fusion-icon

After some research, I may have found part of the problem. In gnome 3, Gnome shell is both the WM and the "desktop (panel and so on)". So with compiz replacing gnome shell, you only got a WM and no "desktop". You need to have another soft to play the role of panel, such as cairo dock.

https://live.gnome.org/GNOME3Myths#I_can.27t_use_Compiz_with_GNOME_Shell.21
https://wiki.archlinux.org/index.php/Compiz#GNOME

With gnome fallback, it should work (and it remind me that I thought I had tested with shell but in fact not yesterday, I got the same result as you with gnome shell).

Now, I don't have (yet ?) an idea on why the decorator doesn't launch in your case.

(In reply to comment #15)
> So with compiz replacing gnome shell, you only got a WM and no "desktop". 
> You need to have another soft to play the role of panel, such as cairo dock.

yes, I know that and cairo-dock is already running quite fine on both gnome3 and gnome classic (when started)

Created attachment 1931 [details]
before fusion-icon (classic)

Created attachment 1932 [details]
after fusion-icon (classic)

note that this screenshot also shows the traceback (right after ^C) when interrupting fusion-icon after it hangs around for some while.

I'm seeing the same behaviour still with compiz-0.9.7.6-1.mga2.x86_64. 

It doesn't matter whether it's gnome3, gnome classic or LXDE, compiz behaves just as described above.

CC: (none) => morrigan

I managed to reproduce the problem with a clean profile. Compiz start but for whatever reason decoration are not applied.
Now I need to understand why.

Status: NEW => ASSIGNED

So, the problem lie in the fact than compiz now load decoration if the plugin decor is activated in compiz config setting manager and not by default.

If you launch ccsm and toggle decoration plugin then save, when you launch compiz, you should have the decoration.

Now, I need to find a way to do a sane default at installation.

It's not as easy as that, at least not for me.

Apparently, all plugins are disabled by default, so I enabled composite, decorations, move window, (these three are IMHO mandatory, otherwise nothing will work), expose and wobbly, just to see the difference.

You didn't say which session you tested under, so let me describe my experiences:


Under the gnome classic session, it seems to work fine at first.
Then open ccsm, enable wallpapers, and get bad graphic errors. (Those vary between windows not being properly redrawn or the whole screen flashing in psychodelic colours)

Under LXDE, the wallpaper plugin simply does nothing. 

In both sessions, I've had compiz either segfault or hang after a few minutes, leaving you either with a window that no longer accepts keyboard input or a hung x-session.

I just pushed compiz-0.9.7.6-2 which I hope should fix this bug.

I can't modify compiz itself so I modified compiz-fusion (a script used by drak3d and other tools) in order to test for a config file in user profile. If none is found (or one with a zero size), a new config file is created with some core plugins :
core, composite, opengl, decor, compiztoolbox, switcher, copytex, fade, place, resize and move.

It should provide a sane default.

morrigan w > For crash or hang, Can you please open a specific bug report (here or upstream on launchpad).

*** Bug 5416 has been marked as a duplicate of this bug. ***

(In reply to comment #24)
> *** Bug 5416 has been marked as a duplicate of this bug. ***

This bug was about compiz not starting, which has been resolved by now. So I'm closing this one and will reopen the other one, which centers on background wallpapers not working correctly.

Status: ASSIGNED => RESOLVED
Resolution: (none) => FIXED