Comments (22)
If you are using gnome2 I suggest to disable the metacity compositor and use
the compiz composite manager until the issue will be fixed.
Original comment by [email protected]
on 7 Sep 2011 at 3:27
from ardesia.
Can be that will not take actions to fix this problem because we want give a
greater priority to the Gnome3/Mutter support. Can be that this will
automatically closed with the work to fix the issue 34
Original comment by [email protected]
on 7 Sep 2011 at 3:27
from ardesia.
[deleted comment]
from ardesia.
This could be a metacity bug!
Original comment by [email protected]
on 7 Sep 2011 at 3:28
from ardesia.
Original comment by [email protected]
on 11 Oct 2011 at 4:27
- Added labels: Ardesia, OpSys-Linux
from ardesia.
I confirm the problem with metacity. In addition to not being able to access
ardesia's menu, drawing does not work: drawn lines do not appear. After
switching virtual desktops forth and back, the drawn lines *may* appear, with
some luck.
Using compiz is *no option*, since this is hardware that cannot run compiz.
Please don't think that this is something exceptional: This is a school with
>200 computers. Schools cannot afford the latest techology, they will *always*
be stuck with hardware one or two generations old.
Linux has been known since it's beginning to perform well on old hardware. It's
very sad to see that this is no longer true.
We'd *love* to use ardesia at our school, but it fails. Sad.
Original comment by [email protected]
on 17 Mar 2012 at 7:09
from ardesia.
The problem still exists. In order to use Ardesia add the xcompmgr composite
manager to the x session. Lxde desktop with xcompmgr is the best choice for
old hardware with no accelerated hardware. I invite you to try the WiildOs
operating system that is developed to support the teaching
http://code.google.com/p/ardesia/wiki/WiildOs.
Original comment by [email protected]
on 17 Mar 2012 at 10:12
from ardesia.
with xcompmgr, ardesia suffers from the same problems as with metacity: menu is
not accessible. Thanks for the suggestion, though. If there's anything else I
can try to get ardesia working with metacity (or xcompmgr), please let me know.
Original comment by [email protected]
on 18 Mar 2012 at 5:59
from ardesia.
Original comment by [email protected]
on 27 Aug 2012 at 7:25
- Added labels: Linux
from ardesia.
This bug might be invalid. In order to see if the problem is related to
metacity try to run gnome with metacity, ardesia and different composite
manager and see if it is working. Pleade don't use panels, unity or some
programs that can steal the focus.
Once that you have seen the behaviour add programs in order to see where is the
problem.
If it is not working try to replace metacity with openbox. If in the first
Ardesia does not work and in the second yes then the bug is for sure in or with
metacity.
Anyway I think that gnome2 belong to e past and then I give a greater priority
to solve problems with gnome3 (issue 34)
Original comment by [email protected]
on 1 Sep 2012 at 8:54
from ardesia.
> In order to see if the problem is related to metacity try to run gnome with
> metacity, ardesia and different composite manager and see if it is working.
I did that (comment 8), the problem persists with metacity, ardesia and
xcompmgr.
> Please don't use panels, unity or some programs that can steal the focus.
That I didn't, I was running Unity-2d. I will try running ardesia on bare bone
metacity and come back to you.
> Anyway I think that gnome2 belong to e past and then I give a greater
priority to
> solve problems with gnome3 (issue 34).
I don't subscribe to this point of view. There's a lot of "oldish" (you
wouldn't have called it like that in the former linux days, just because it's
ten years old...) hardware around. That's especially true for educational
institutions running on low budget, which is sort of the native field for
ardesia.
Original comment by [email protected]
on 1 Sep 2012 at 9:25
from ardesia.
Seems that the issue is related to the metacity window manager. I confirm that
changing the compositor manager (e.g. xcompmgr) the problem still remain.
Original comment by [email protected]
on 2 Sep 2012 at 11:33
- Changed title: Not compliant with gnome2 metacity
- Added labels: Priority-High
- Removed labels: Priority-Medium
from ardesia.
Original comment by [email protected]
on 2 Sep 2012 at 11:33
- Changed title: Not compliant with gnome/metacity
from ardesia.
The commit 256 fix the issue in my computer.
Please if you are using gnome, test it with Ardesia and give me feedback. I'm
intereset to see if Ardesia work with mutter and gnome-shell also.
The commit 256 comment:
- Better handling of focus, shape and window stack
- Metacity compliant
- Gnome Classic compliant
- Unity compliant
- Could be compliant with gnome-shell
(I can not test it, gnone shell crash at startup on my laptop)
- Close issue 37
- Could be compliant with mutter
(I can not test it, mutter crash at startup on my laptop)
Could close issue 34
Original comment by [email protected]
on 2 Sep 2012 at 1:56
- Changed state: Started
from ardesia.
Original comment by [email protected]
on 2 Sep 2012 at 2:13
- Changed state: Fixed
from ardesia.
I confirm that the problem is (almost, see below) fixed in the latest svn
revision 2857, tested on my home box. I'm looking forward to trying this at
school. We appreciate your work, thank you very much!
There is one issue left:
After choosing the "Insert Text" tool, buttons in the side panel cannot be
reached any more. Thus, the "Insert Text" tool can never be stopped. I can
continue creating annotations, but I cannot chose another tool or exit ardesia.
Is this a left-over bug?
Original comment by [email protected]
on 2 Sep 2012 at 8:49
from ardesia.
Yes it is a left over bug that occurs with metacity only. I'll try to fix it in
the next days.
Original comment by [email protected]
on 2 Sep 2012 at 10:53
from ardesia.
Has been fixed the left-bug also
Original comment by [email protected]
on 3 Sep 2012 at 2:17
from ardesia.
I confirm that "Insert Text" now can be stopped by choosing another tool from
the ardesia sidebar. Thank you!
However, I see the following disturbing effect:
- When starting ardesia, after having set the project name, my whole screen
turns light grey for app. 1 sec, then reappears together with the ardesia
sidebar.
- When choosing "Insert Text", my whole screen turns light grey until I click
somewhere on screen, then screen reappears. It turns grey every time I move the
mouse pointer over the ardesia sidebar and back to screen, as long as "Insert
Text" tool is selected.
Original comment by [email protected]
on 4 Sep 2012 at 9:00
from ardesia.
I'll see if is possible avoid or minimize the initial flickering.
This is not a metacity issue but a common minor problem.
Original comment by [email protected]
on 4 Sep 2012 at 3:05
from ardesia.
When using the "Insert Text" tool it's not a flickering, but the screen turns
grey and stays like this until I click anywhere.
Original comment by [email protected]
on 4 Sep 2012 at 3:11
from ardesia.
Original comment by [email protected]
on 17 Sep 2012 at 5:19
- Changed state: Verified
from ardesia.
Related Issues (20)
- Spotlighter 0.3 segfaults HOT 1
- Menu bar not working in KDE HOT 1
- Request: hotkeys please HOT 4
- Please make tool bar floating HOT 1
- No functionality on lubuntu 13.10
- No buttons in sidebar (gtk's issue?)
- Toolbar blank on Ubuntu 13.10 running XFCE
- Cannot use
- Black images saved on Windows
- Patch for /trunk/ardesia/desktop/ardesia.desktop.in
- ardesia lubuntu 14.10
- Ardesia doesn't work on dual screen configs
- Ardesia unusable with fullscreen apps
- ardesia don't draw anything on Xubuntu 14.04.1 LTS _Trusty Tahr_ - Release i386 HOT 1
- Ardesia not working with Linux Mint 18.1 Cinnamon 64-bit HOT 4
- Ardesia's annotate feature not working on Raspbian Jessie
- Not working on Awesome WM + Compton
- Control window does not stay in foreground / covered by transparent window
- Not working on Manjaro 17.1.10 Gnome
- Ardesia Can not Write on Kde Neon!
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from ardesia.