search

sanyaade-teachings / ardesia

Automatically exported from code.google.com/p/ardesia
0 stars 0 forks source link

Xcompmgr and Ardesia under Ubuntu 10.10 MaverickMeerkat #20

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
What steps will reproduce the problem?
1. LXDE + xcompmgr
2. start ardesia

What is the expected output? What do you see instead?
Under Gnome i see the Desktop and can draw on it, but here all is just black

What version of the product are you using? On what operating system?
Lubuntu 10.10 with ardesia0.6

Original issue reported on code.google.com by johannes...@gmail.com on 31 Dec 2010 at 12:31

GoogleCodeExporter commented 9 years ago 
This seems an Ubuntu 10.10 bug in Xorg try with other program that use a 
transparency and you will have the same behaviour (black instead od transparent 
color).
Let's try to use the Ubuntu 10.4 and will see that all works fine
You can check with the WiildOs 1.2 on
http://www.novaup.com/download/9fpy2388idi07 

Bye

Original comment by al...@paranoici.org on 7 Jan 2011 at 2:28

GoogleCodeExporter commented 9 years ago 
For more info about the Ubuntu bug see:
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/636425/+
activity

Original comment by al...@paranoici.org on 7 Jan 2011 at 2:41

GoogleCodeExporter commented 9 years ago 
The RGBA channel is needed to have the
transparency and in order to run Ardesia fine.
In Ubuntu 10.10 with xcompmgr the RGBA
is not supported, This seems a Xorg bug (may be a gtk one?)
In any case on Ubuntu 10.10 the gdk_screen_get_rgba_colormap(screen)
return wrongly NULL.

Original comment by al...@paranoici.org on 7 Jan 2011 at 3:30

GoogleCodeExporter commented 9 years ago 
http://plan99.net/~mike/files/alphademo.c

You can build this file to test that the Ubuntu 10.10 with xcompmgr is not able 
to have an alpha channel

Original comment by al...@paranoici.org on 7 Jan 2011 at 3:39

GoogleCodeExporter commented 9 years ago 
[deleted comment]
GoogleCodeExporter commented 9 years ago 
[deleted comment]
GoogleCodeExporter commented 9 years ago 
The problem is not in the xcompmgr tool I have downgraded it to 1.1.4 (with the 
lucid deb) and I have the same behaviour.
Seems that the problem is not in a specific xorg driver because I have the same 
result without alpha channel with the fglrx driver and vesa. Please if you have 
some success story running fine Ardesia with xcompmgr inform the Ardesia 
developer staff.

Original comment by al...@paranoici.org on 9 Jan 2011 at 7:27

GoogleCodeExporter commented 9 years ago 
The problem persists using X installed with 
[https://launchpad.net/~xorg-edgers/+archive/ppa xorg-edgers ppa] and 
[https://launchpad.net/~ubuntu-x-swat/+archive/x-updates x-swat].

Original comment by al...@paranoici.org on 9 Jan 2011 at 7:54

GoogleCodeExporter commented 9 years ago 
I have downgrade the kernel 2.6.32-27-generic that is the same of lucid but 
also in this way happens the same problem.

Original comment by al...@paranoici.org on 9 Jan 2011 at 8:12

GoogleCodeExporter commented 9 years ago 
I have tried to use the old gtk used by ubuntu lucid 
libgtk2.0-0_2.20.0-0ubuntu4_i386.deb but I have the same problem.
The problem is not in gtk, not in xcompmgr and not in kernel.
I'm pretty sure that it is a xorg bug. 
The point which xorg package cause bug or hope... that it will be solved by 
anyone

Original comment by al...@paranoici.org on 9 Jan 2011 at 8:56

GoogleCodeExporter commented 9 years ago 
The problem could be in X binary or in one of these modules xrender, xfixes, 
xdamage, xcomposite

Original comment by al...@paranoici.org on 9 Jan 2011 at 9:19

GoogleCodeExporter commented 9 years ago 
I have tested all the system in Maverick running xcompmgr and Ardesia in a 
chrooted environment with the Lucid filesystem and the same problem occurs. 
This demonstrates that the problem is not in some linked libraries or in 
xcompmgr but is a problem of the xorg runtime environment in Maverick.

Original comment by al...@paranoici.org on 9 Jan 2011 at 9:42

GoogleCodeExporter commented 9 years ago 
Ubuntu will move from Xorg to Wayland. Can be a good attempt try to test 
Wayland on Maverick this has a compositor manager (wayland-compositor) also 
https://launchpad.net/~xorg-edgers/+archive/wayland/.

Original comment by al...@paranoici.org on 9 Jan 2011 at 11:06

GoogleCodeExporter commented 9 years ago 
This is a problem in the lubuntu desktop in Maverick,
if you open /usr/bin/startlubuntu 
you can read

#Workaround to disable rgba, because lxpanel in Lubuntu doesn't support it
#(see bug #589763)

This means that all the programs that uses RGBA colormap in Maverick/Lubuntu 
will have problems

This is not an Ardesia Bug!

Original comment by al...@paranoici.org on 27 Jan 2011 at 5:25

GoogleCodeExporter commented 9 years ago 
Anyway if you open the /usr/bin/startlubuntu 
and you comment the line

export XLIB_SKIP_ARGB_VISUALS=1

and reboot you will able to use ardesia on Maverick

Original comment by al...@paranoici.org on 27 Jan 2011 at 5:34

GoogleCodeExporter commented 9 years ago 
The missing alpha channel is introduced as workaround to this bug 
https://bugs.launchpad.net/ubuntu/+source/gtk+2.0/+bug/589763, please anyone 
can inform the lubuntu team about this issue

Original comment by al...@paranoici.org on 27 Jan 2011 at 5:40

GoogleCodeExporter commented 9 years ago 
Anyway the problem is not in Ardesia and now the tool is stopped if is not 
possible to use the RGBA colormap. This is an Ardesia requirement

Original comment by al...@paranoici.org on 27 Jan 2011 at 6:18

GoogleCodeExporter commented 9 years ago

Original comment by al...@paranoici.org on 27 Jan 2011 at 6:18