Export to GitHub

ardesia - issue #60

Ardesia not work at Ubuntu 13.04


Posted on May 28, 2013 by Swift Bear

What steps will reproduce the problem? 1. Open ardesia 2. Try draw screen 3. I can't see any line at screen but I can see my draw at ardesia tmp file.

What is the expected output? What do you see instead?

I can't see ardesia screen draw result at my desktop

What version of the product are you using? On what operating system?

Ardesia Verion : 1.1-1 Operation System : Ubuntu 13.04 with Unity

Please provide any additional information below.

Comment #1

Posted on Jul 15, 2013 by Swift Bear

I tried trunk ( 1.2-1 ) version on ubuntu-gnome ubuntu-unity but result same, we can't draw screenand just see white color continuously

Attachments

Comment #2

Posted on Jul 18, 2013 by Grumpy Monkey

Same problem with Mint 15 Xfce. Running from terminal gives:

chris@mapuana ~/Temp/downloads $ ardesia Enabled Device in screen 2. 0x256b080: "Virtual core pointer" (Type: 0)

(process:3550): GLib-CRITICAL **: g_slice_set_config: assertion `sys_page_size == 0' failed Segmentation fault

Comment #3

Posted on Jul 18, 2013 by Grumpy Monkey

An earlier version (1.01) seems to work fine. I uninstalled the latest version completely, then just downloaded and installed 1.01 --> success!

Comment #4

Posted on Jul 18, 2013 by Swift Bear

My problem continue 1.01

Comment #5

Posted on Jul 19, 2013 by Grumpy Monkey

When I uninstalled the newer version, I used Synaptic's "mark for complete removal" function. I figured that this would clean out whatever supporting library was misbehaving. Only then did I install the earlier version. If that doesn't do the job for you, then I'm stumped; sorry.

You don't say what, specifically, you want to do with Ardesia. For general screen annotation, you might try Gromit, which is in the *buntu repos. It's quirky, but when it works properly it does a good job.

Xournal works very well for annotating pdfs and for drawing on a white or colored background; it even has layers. And LibreOffice Impress allows drawing on a slide by right-clicking on a slide and choosing "use mouse as pen". For simple drawing, one can use a blank (i.e. plain white) slide.

Comment #6

Posted on Jul 30, 2013 by Happy Horse

Please try the trunk code

Comment #7

Posted on Sep 8, 2013 by Happy Wombat

A warm hello to Italy! I tried the trunk version (revision 3004) of Ardesia-1.2 on Ubuntu 13.04 and encountered the same (non-)effect as the original poster (as well as with 1.1 before). Upon closing the program, the drawing flashed briefly on the screen before the program finally closed. Running Ardesia from the command line listed some X-devices but no error.

Many thanks for this great program! I had it running on my computer before and I sincerely hope that it gets up and running soon!

Comment #8

Posted on Sep 17, 2013 by Happy Panda

I can confirm this behaviour in Kubuntu 13.04. Upon closing, the "overlay" briefly flashes, but nothing is visible during drawing

Comment #9

Posted on Oct 16, 2013 by Swift Bear

I start use Fedora 19 and have same problem. So Unity and Gnome have same problem.

Comment #10

Posted on Oct 18, 2013 by Swift Bear

ardesia 1.2 (C) 2009-2010 Pietro Pilolli [e-diablo@homless ~]$ ardesia -g west No such schema 'org.florence.behaviour' Fail to hide virtual keyboard: Florence and gsettings packages are required Enabled Device in screen 1. 0x2487080: "Virtual core pointer" (Type: 0) Enabled Device in screen 1. 0x2487680: "SynPS/2 Synaptics TouchPad" (Type: 6) Enabled Device in screen 1. 0x2487580: "Logitech USB Receiver" (Type: 0) Enabled Device in screen 1. 0x2487500: "Logitech USB Receiver" (Type: 0) Enabled Device in screen 1. 0x2487180: "Virtual core XTEST pointer" (Type: 0)

I get that fail line if I want work with gnome "No such schema 'org.florence.behaviour'"

Comment #11

Posted on Nov 6, 2013 by Happy Panda

With reference to gromit (made above under #5):

It does not work either in Kubuntu 13.04... seems to be the same problem than with ardesia. Activation using the Pause key works, but the drawing remains invisible.

Comment #12

Posted on Nov 9, 2013 by Massive Rhino

soy nuevo en ubuntu o en linuk Ardesia parece ser el programa que estoy buscando pero no me trabaja correctamente, no se ve nada

Comment #13

Posted on Dec 6, 2013 by Swift Lion

Same problem. Invisible drawing... This is showing in terminal:

Enabled Device in screen 2. 0x81bbcf0: "Virtual core pointer" (Type: 0)

I think this is a framebuffer (composite) issue...

I hope help us with this information.

Comment #14

Posted on Feb 18, 2014 by Happy Rabbit

en kubuntu 13.10 no veo lo que dibujo, pero cuando intento cerrar la barra de menú aparece repentinamente y desaparece lo que dibujé anteriormente

Comment #15

Posted on Apr 4, 2014 by Happy Rabbit

SAME PROBLEM here, with a new Thinkpad. I tried Unity, gnome, cinnamon. No effect

Comment #16

Posted on Apr 23, 2014 by Quick Lion

Ardesia it's working for me with Ubuntu 14.04, only different thing was i started with command line "$ardesia -g south"

Comment #17

Posted on Apr 23, 2014 by Swift Bear

But I start use Fedora 20 with gnome and if you use Ubuntu then you not need Ardesia because Ubuntu already have another working sketpatch/screen draw software... I am talking about Compiz...

Comment #18

Posted on Sep 24, 2014 by Happy Wombat

not working, the draws are invisible and pop up when quit.

Ubuntu 14.04.1 in xfce session (install xfce4 and compiz, login xfce session and enable compiz)

and if it is started by: ardesia -g south

** (ardesia:2341): WARNING **: Couldn't connect to accessibility bus: Failed to connect to socket /tmp/dbus-Fn8hQx5EQ5: Connection refused Enabled Device in screen 2. 0x1245590: "Virtual core pointer" (Type: 0) Segmentation fault

Comment #19

Posted on Dec 16, 2014 by Happy Kangaroo

The same for me: nothing is displayed running the program. Only when closing it the image of what I drew flashes on the screen.

When reviewing what was saved during session, all my drawings are there.

Running the program from console says: " ** (ardesia:PID) WARNING **: Couldn't connect to accessibility bus: Failed to connect to socket /tmp/dbus-Kbkfn9ttWB: Connection refused "

After entering the "project name" it says:

" Enabled Device in screen 2. 0xe3ed90: "Virtual core pointer" (Type: 0) "

May be this "screen 2" the problem, it is writing things somewhere else? I get no "Segmentation fault" error.

I'm on Trisquel 7.0 with Gnome Classic.

Status: New

Labels:
Type-Defect Priority-Medium