Re: Getting QT apps running.

[Timo Jyrinki]

Changing qt5conf to desktop/qt5 and qt5-launch to desktop-launch does
not help in ipe's case it seems, even though it gets rid of a few
warnings.

The problem is with the IPE_PREFIX that ipe requires to be set, and
I'm also unable to find a combination that would allow ipe to build
(../../../install works) and ipe to find its main.lua file from the
correct directory.

It seemed useful to remove the "bin/" prefix though after the changes.

-Timo (snapcraft newbie, testing because Qt mentioned)

On Thu, Jul 28, 2016 at 10:18 PM, Michael Hall  wrote:
> "qt5conf" has been replaced be the newer "desktop/qt5" part and
> "qt5-launch" replaced by "desktop-launch" in the command. These new
> desktop launchers have fixed a lot of the common problems that the
> original qt5conf and gtk-equiqalents ran into.
>
>
> Michael Hall
> mhall...@ubuntu.com
>
> On 07/28/2016 02:34 PM, Dietmar Winkler wrote:
>> Hi,
>>
>> thanks.  That let me start the app ... almost. I'm now getting:
>>
>> $ ipe
>> Qt: Session management error: None of the authentication protocols
>> specified are supported
>> QGtkStyle could not resolve GTK. Make sure you have installed the
>> proper libraries.
>> [string "require "main""]:1: module 'main' not found:
>> no field package.preload['main']
>> no file '../../../install/share/ipe/7.2.5/lua/main.lua'
>> no file '/usr/local/lib/lua/5.2/main.so'
>> no file '/usr/lib/x86_64-linux-gnu/lua/5.2/main.so'
>> no file '/usr/lib/lua/5.2/main.so'
>> no file '/usr/local/lib/lua/5.2/loadall.so'
>> no file './main.so'
>> stack traceback:
>> [C]: in function 'require'
>> [string "require "main""]:1: in main chunk
>>
>>
>>
>> On 28 July 2016 at 20:21, Kyle Fazzari  wrote:
>>> On 07/28/2016 11:05 AM, Dietmar Winkler wrote:
 Hi,

 when trying to run this "ipe" qt app I got the error message:
 $ ipe
 This application failed to start because it could not find or load the
 Qt platform plugin "xcb".

 I found out that I need to include the libqt5gui5 package as stage
 package (just like in the hello-world-desktop example, But even though
 I added it to my yaml file I still get the same error message.

 https://github.com/dietmarw/snaps/blob/master/ipe/snapcraft.yaml#L44
 (I'm actually not sure if I really need the "after: [qt5conf]" part.)

 So what else am I missing?
>>>
>>> The problem is that your application isn't looking in the right place
>>> for the platform plugins. That's where the qt5conf part comes in handy--
>>> it includes a launcher script to set that environment for you.
>>>
>>> You need to use the launcher from the qt5conf part in order to launch
>>> the app.
>>>
>>> apps:
>>>   ipe:
>>> command: bin/ipe
>>>
>>> Needs to be:
>>>
>>> apps:
>>>   ipe:
>>> command: qt5-launch bin/ipe
>>>
>>> And so on.
>>>
>>> --
>>> Kyle Fazzari (kyrofa)
>>> Software Engineer
>>> Canonical Ltd.
>>> k...@canonical.com
>>>
>>>
>>> --
>>> Snapcraft mailing list
>>> Snapcraft@lists.snapcraft.io
>>> Modify settings or unsubscribe at: 
>>> https://lists.ubuntu.com/mailman/listinfo/snapcraft
>>>
>>
>>
>>
>
> --
> Snapcraft mailing list
> Snapcraft@lists.snapcraft.io
> Modify settings or unsubscribe at: 
> https://lists.ubuntu.com/mailman/listinfo/snapcraft

-- 
Snapcraft mailing list
Snapcraft@lists.snapcraft.io
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/snapcraft

Re: Problems with PREFIX when building a snap

[James Jesudason]

On 28 July 2016 at 18:36, Dietmar Winkler  wrote:

> Thanks James,
>
> you are right the build works now. But I hope you don't mind me asking
> (since I really want to understand it) how you ended up at that
> IPEPREFIX path.
>
> The source is in:
>
> ~/tmp/snap/ipe/parts/ipe/src
>
> For the build that gets copied over to
>
> ~/tmp/snap/ipe/parts/ipe/build
>
> make gets executed in the subdir "src", which means now we are in
>
> ~/tmp/snap/ipe/parts/ipe/build/src
>
> Now I try to travers 3 levels up as defined by
>
> - IPEPREFIX=../../../install
>
> and I end up in
>
> ~/tmp/snap/ipe/parts/
>
> but here is only the "ipe" dir the install is one level below:
>
> ~/tmp/snap/ipe/parts[master]$ tree -L 2
> .
> └── ipe
> ├── build
> ├── install
> ├── src
> ├── state
> └── ubuntu
>
> So how come
>
> - IPEPREFIX=../../../install
>
> works but
>
> - IPEPREFIX=../../install
>
> would not (which I would find logical)?
>
> ​It's more to do with the build script than with snapcraft. Since there
are multiple directories called "install" it's hard to see what's
happening. If you try something like "../" instead, then it's easier to
spot what the script is doing. ​

​When the script was running, I spotted th​at it said:

make[2]: Entering directory '/parts/ipe/build/src/ipe'

​So, that's where the extra level comes from.​



>
> One other question, is there somewhere a list of available "plugs". I
> guessed I would need "x11" but only found this reference in some
> examples. I did not manage to find any specific documentation on this.
>
>
​The plugs are documented with snapd rather than snapcraft. There's a list
here:
https://developer.ubuntu.com/en/snappy/guides/interfaces/

But the definitive list is the source code (sometimes the tests there can
be helpful):
https://github.com/snapcore/snapd/tree/master/interfaces/builtin​

​The "playpen" examples can be helpful as well:
https://github.com/ubuntu/snappy-playpen
​
-- 
Snapcraft mailing list
Snapcraft@lists.snapcraft.io
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/snapcraft

Re: Getting QT apps running.

[Dietmar Winkler]

So I  decided to hack the source of the ipe package in order to get
rid of the path issue possibly causing other problems.

So the updated snapcraft.yaml pulls in "my version" that does not need
a IPEPREFIX any more.
https://github.com/dietmarw/snaps/blob/master/ipe/snapcraft.yaml

But as Timo, I found a couple of other problems. I first tried to only
use the x11 and home plug but then launching ipe  simply does nothing
and sits there until I kill the command. I then tested the unity7 and
home plug. Now I'm getting:

--8<---
$ ipe
ln: failed to create symbolic link
'/home/dietmarw/snap/ipe/x17/.themes/themes': Read-only file system

(process:8847): Gtk-WARNING **: Locale not supported by C library.
Using the fallback 'C' locale.
Gtk-Message: Failed to load module "overlay-scrollbar"
Gtk-Message: Failed to load module "gtk-vector-screenshot"
Gtk-Message: Failed to load module "gail"
Gtk-Message: Failed to load module "atk-bridge"
Gtk-Message: Failed to load module "unity-gtk-module"
Gtk-Message: Failed to load module "canberra-gtk-module"
Qt: Session management error: None of the authentication protocols
specified are supported
[string "require "main""]:1: module 'main' not found:
no field package.preload['main']
no file '/share/ipe/7.2.5/lua/main.lua'
no file '/usr/local/lib/lua/5.2/main.so'
no file '/usr/lib/x86_64-linux-gnu/lua/5.2/main.so'
no file '/usr/lib/lua/5.2/main.so'
no file '/usr/local/lib/lua/5.2/loadall.so'
no file './main.so'
stack traceback:
[C]: in function 'require'
[string "require "main""]:1: in main chunk

---8<

The main.lua file is actually present

$ tree /snap/ipe/current/share/ipe/7.2.5/lua/
/snap/ipe/current/share/ipe/7.2.5/lua/
├── actions.lua
├── editpath.lua
├── main.lua
├── model.lua
├── mouse.lua
├── prefs.lua
├── properties.lua
├── shortcuts.lua
└── tools.lua



On 29 July 2016 at 09:14, Timo Jyrinki  wrote:
> Changing qt5conf to desktop/qt5 and qt5-launch to desktop-launch does
> not help in ipe's case it seems, even though it gets rid of a few
> warnings.
>
> The problem is with the IPE_PREFIX that ipe requires to be set, and
> I'm also unable to find a combination that would allow ipe to build
> (../../../install works) and ipe to find its main.lua file from the
> correct directory.
>
> It seemed useful to remove the "bin/" prefix though after the changes.
>
> -Timo (snapcraft newbie, testing because Qt mentioned)
>
> On Thu, Jul 28, 2016 at 10:18 PM, Michael Hall  wrote:
>> "qt5conf" has been replaced be the newer "desktop/qt5" part and
>> "qt5-launch" replaced by "desktop-launch" in the command. These new
>> desktop launchers have fixed a lot of the common problems that the
>> original qt5conf and gtk-equiqalents ran into.
>>
>>
>> Michael Hall
>> mhall...@ubuntu.com
>>
>> On 07/28/2016 02:34 PM, Dietmar Winkler wrote:
>>> Hi,
>>>
>>> thanks.  That let me start the app ... almost. I'm now getting:
>>>
>>> $ ipe
>>> Qt: Session management error: None of the authentication protocols
>>> specified are supported
>>> QGtkStyle could not resolve GTK. Make sure you have installed the
>>> proper libraries.
>>> [string "require "main""]:1: module 'main' not found:
>>> no field package.preload['main']
>>> no file '../../../install/share/ipe/7.2.5/lua/main.lua'
>>> no file '/usr/local/lib/lua/5.2/main.so'
>>> no file '/usr/lib/x86_64-linux-gnu/lua/5.2/main.so'
>>> no file '/usr/lib/lua/5.2/main.so'
>>> no file '/usr/local/lib/lua/5.2/loadall.so'
>>> no file './main.so'
>>> stack traceback:
>>> [C]: in function 'require'
>>> [string "require "main""]:1: in main chunk
>>>
>>>
>>>
>>> On 28 July 2016 at 20:21, Kyle Fazzari  wrote:
 On 07/28/2016 11:05 AM, Dietmar Winkler wrote:
> Hi,
>
> when trying to run this "ipe" qt app I got the error message:
> $ ipe
> This application failed to start because it could not find or load the
> Qt platform plugin "xcb".
>
> I found out that I need to include the libqt5gui5 package as stage
> package (just like in the hello-world-desktop example, But even though
> I added it to my yaml file I still get the same error message.
>
> https://github.com/dietmarw/snaps/blob/master/ipe/snapcraft.yaml#L44
> (I'm actually not sure if I really need the "after: [qt5conf]" part.)
>
> So what else am I missing?

 The problem is that your application isn't looking in the right place
 for the platform plugins. That's where the qt5conf part comes in handy--
 it includes a launcher script to set that environment for you.

 You need to use the launcher from the qt5conf part in order to launch
 the app.

 apps:
   ipe:
 command: bin/ipe

 Needs to be:

 apps:
   ipe:
 command: qt5-launch bin/ipe

 And so on.

 --
 Kyle Fazzari (kyrofa)
 Software Engineer
 Canonical Ltd.
 k...@canonical.com


 --
 Snapcraft mailing list
 Snapcraft@lists.snapcraft.io
 Modify settings or uns

Re: Problems with PREFIX when building a snap

[Dietmar Winkler]

Hi James,

OK now I understand. Still not all resolved but that can be handled in
the other thread.
https://lists.ubuntu.com/archives/snapcraft/2016-July/000561.html

Thanks again,

On 29 July 2016 at 10:26, James Jesudason  wrote:
>
>
> On 28 July 2016 at 18:36, Dietmar Winkler  wrote:
>>
>> Thanks James,
>>
>> you are right the build works now. But I hope you don't mind me asking
>> (since I really want to understand it) how you ended up at that
>> IPEPREFIX path.
>>
>> The source is in:
>>
>> ~/tmp/snap/ipe/parts/ipe/src
>>
>> For the build that gets copied over to
>>
>> ~/tmp/snap/ipe/parts/ipe/build
>>
>> make gets executed in the subdir "src", which means now we are in
>>
>> ~/tmp/snap/ipe/parts/ipe/build/src
>>
>> Now I try to travers 3 levels up as defined by
>>
>> - IPEPREFIX=../../../install
>>
>> and I end up in
>>
>> ~/tmp/snap/ipe/parts/
>>
>> but here is only the "ipe" dir the install is one level below:
>>
>> ~/tmp/snap/ipe/parts[master]$ tree -L 2
>> .
>> └── ipe
>> ├── build
>> ├── install
>> ├── src
>> ├── state
>> └── ubuntu
>>
>> So how come
>>
>> - IPEPREFIX=../../../install
>>
>> works but
>>
>> - IPEPREFIX=../../install
>>
>> would not (which I would find logical)?
>>
> It's more to do with the build script than with snapcraft. Since there are
> multiple directories called "install" it's hard to see what's happening. If
> you try something like "../" instead, then it's easier to spot what the
> script is doing.
>
> When the script was running, I spotted that it said:
>
> make[2]: Entering directory '/parts/ipe/build/src/ipe'
>
> So, that's where the extra level comes from.
>
>
>>
>>
>> One other question, is there somewhere a list of available "plugs". I
>> guessed I would need "x11" but only found this reference in some
>> examples. I did not manage to find any specific documentation on this.
>>
>
> The plugs are documented with snapd rather than snapcraft. There's a list
> here:
> https://developer.ubuntu.com/en/snappy/guides/interfaces/
>
> But the definitive list is the source code (sometimes the tests there can be
> helpful):
> https://github.com/snapcore/snapd/tree/master/interfaces/builtin
>
> The "playpen" examples can be helpful as well:
> https://github.com/ubuntu/snappy-playpen
>



-- 
/Dietmar/

Secure email communication:
https://encrypt.to/dietmar.wink...@dwe.no
Public OpenPGP key: 0x235E6689

-- 
Snapcraft mailing list
Snapcraft@lists.snapcraft.io
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/snapcraft

Re: Getting QT apps running.

[Oliver Grawert]

hi,
Am Freitag, den 29.07.2016, 11:19 +0200 schrieb Dietmar Winkler:
...
> specified are supported
> [string "require "main""]:1: module 'main' not found:
> no field package.preload['main']
> no file '/share/ipe/7.2.5/lua/main.lua'
> no file '/usr/local/lib/lua/5.2/main.so'
> no file '/usr/lib/x86_64-linux-gnu/lua/5.2/main.so'
> no file '/usr/lib/lua/5.2/main.so'
> no file '/usr/local/lib/lua/5.2/loadall.so'
> no file './main.so'
> stack traceback:
> [C]: in function 'require'
> [string "require "main""]:1: in main chunk
> 
> ---8<
> 
> The main.lua file is actually present
> 
> $ tree /snap/ipe/current/share/ipe/7.2.5/lua/
> /snap/ipe/current/share/ipe/7.2.5/lua/
> ├── actions.lua
> ├── editpath.lua
> ├── main.lua
> ├── model.lua
> ├── mouse.lua
> ├── prefs.lua
> ├── properties.lua
> ├── shortcuts.lua
> └── tools.lua
> 
any reason to not create another startup wrapper that sets up a proper
environmant for you ?

http://ipe.otfried.org/manual/manual_40.html

talks about IPELUAPATH ... 

i'd just creaate a small shell script that you call from the
desktop-launcher to add additional environment variables ...

ciao
oli 


signature.asc
Description: This is a digitally signed message part
-- 
Snapcraft mailing list
Snapcraft@lists.snapcraft.io
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/snapcraft

Re: Getting QT apps running.

[Dietmar Winkler]

Hi,

I'm not sure if this will help. According to the output it _is_
already looking at the right place.

> no file '/share/ipe/7.2.5/lua/main.lua'

but

$ tree /snap/ipe/current/share/ipe/7.2.5/lua/
/snap/ipe/current/share/ipe/7.2.5/lua/
├── actions.lua
├── editpath.lua
├── main.lua
...

-- 
/Dietmar/

Secure email communication:
https://encrypt.to/dietmar.wink...@dwe.no
Public OpenPGP key: 0x235E6689

-- 
Snapcraft mailing list
Snapcraft@lists.snapcraft.io
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/snapcraft

Re: Getting QT apps running.

[Oliver Grawert]

Am Freitag, den 29.07.2016, 11:32 +0200 schrieb Dietmar Winkler:
> Hi,
> 
> I'm not sure if this will help. According to the output it _is_
> already looking at the right place.
> 
> > no file '/share/ipe/7.2.5/lua/main.lua'
> 
> but
> 
> $ tree /snap/ipe/current/share/ipe/7.2.5/lua/
> /snap/ipe/current/share/ipe/7.2.5/lua/
> ├── actions.lua
> ├── editpath.lua
> ├── main.lua
> ...
> 

well, it looks in /share, not in /snap 

try this:
---
#! /bin/sh

export IPELUAPATH=$SNAP/share/ipe/7.2.5/lua

exec $SNAP/bin/ipe
---

save it as wrapper.sh (make it executable), add a copy plugin part to
your snapcraft.yaml that copies it in the toplevel of your snap
and change:
https://github.com/dietmarw/snaps/blob/master/ipe/snapcraft.yaml#L52
to read:

command: desktop-launch wrapper.sh

if needed also set the other variables to their proper paths ...

ciao
oli


signature.asc
Description: This is a digitally signed message part
-- 
Snapcraft mailing list
Snapcraft@lists.snapcraft.io
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/snapcraft

Re: Getting QT apps running.

[Sebastien Bacher]

Le 29/07/2016 à 11:32, Dietmar Winkler a écrit :
>> no file '/share/ipe/7.2.5/lua/main.lua'
> but
>
> $ tree /snap/ipe/current/share/ipe/7.2.5/lua/
> /snap/ipe/current/share/ipe/7.2.5/lua/

It's look in /share but the actual directory is /snap/ipe/current/share,

You might be able to workaround it with some environment variable but
you might also be down to
https://bugs.launchpad.net/ubuntu/+source/snapcraft/+bug/1583250
"upstream use of build-time defined DATADIR incompatible with snaps
relocation"

There is work ongoing to resolve those situation with smart syscall
redirections but until that land you might be able to workaround using
"/snap/ipe/current/share" as a build prefix and reorganize files in your
prime if needed...

Cheers,

Sebastien Bacher

-- 
Snapcraft mailing list
Snapcraft@lists.snapcraft.io
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/snapcraft

Re: Getting QT apps running.

[Dietmar Winkler]

On 29 July 2016 at 11:39, Sebastien Bacher  wrote:
> It's look in /share but the actual directory is /snap/ipe/current/share,

Ah yes of course. I was assuming that the snap only knows about what's
inside $SNAP and not the root file system. Hence I did not think those
were to different locations.

-- 
/Dietmar/

Secure email communication:
https://encrypt.to/dietmar.wink...@dwe.no
Public OpenPGP key: 0x235E6689

-- 
Snapcraft mailing list
Snapcraft@lists.snapcraft.io
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/snapcraft

Re: no hardware description in Gadget snap for building an image

[Gustavo Niemeyer]

For the record, please note this change was announced in this list a couple
of months ago, and that we don't actually have official Ubuntu Core 16
images yet.

Polishing the format is being done while finalizing those images.

On Jul 28, 2016 8:03 PM, "Michael Vogt"  wrote:

> On Thu, Jul 28, 2016 at 05:50:54PM +0800, Woodrow Shen wrote:
> > Hi all,
> Hi Woodrow,
>
> thanks for your mail!
>
> > It seems the latest revision 8 has a lack of hardware section for gadget
> > snap.
> > I think someone is working on it now, but hope we can make sure the snap
> > uploaded to edge channel can work at least.
>
> You are correct, we are currently working on a new and improved format
> to describe the bootloader for a device. This work is currently in
> progress and because the old format stops working we removed it. We
> publish new gadget snaps with the new format soon. ubuntu-image will
> be the tool to consume them then.
>
> Cheers,
>  Michael
>
> --
> Snapcraft mailing list
> Snapcraft@lists.snapcraft.io
> Modify settings or unsubscribe at:
> https://lists.ubuntu.com/mailman/listinfo/snapcraft
>
-- 
Snapcraft mailing list
Snapcraft@lists.snapcraft.io
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/snapcraft

Re: Getting QT apps running.

[Dietmar Winkler]

Thanks Oli,

I've implemented it as you suggested and got one step further:

$ ipe
ln: failed to create symbolic link
'/home/dietmarw/snap/ipe/x22/.themes/themes': Read-only file system

(process:31604): Gtk-WARNING **: Locale not supported by C library.
Using the fallback 'C' locale.
Gtk-Message: Failed to load module "overlay-scrollbar"
Gtk-Message: Failed to load module "gtk-vector-screenshot"
Gtk-Message: Failed to load module "gail"
Gtk-Message: Failed to load module "atk-bridge"
Gtk-Message: Failed to load module "unity-gtk-module"
Gtk-Message: Failed to load module "canberra-gtk-module"
Qt: Session management error: None of the authentication protocols
specified are supported
error loading module 'main' from file '/snap/ipe/x22/share/ipe/7.2.5/lua':
cannot read /snap/ipe/x22/share/ipe/7.2.5/lua: Is a directory
stack traceback:
[C]: in ?
[C]: in function 'require'
[string "require "main""]:1: in main chunk

but now I'm stuck again.

On 29 July 2016 at 11:40, Oliver Grawert  wrote:
> Am Freitag, den 29.07.2016, 11:32 +0200 schrieb Dietmar Winkler:
>> Hi,
>>
>> I'm not sure if this will help. According to the output it _is_
>> already looking at the right place.
>>
>> > no file '/share/ipe/7.2.5/lua/main.lua'
>>
>> but
>>
>> $ tree /snap/ipe/current/share/ipe/7.2.5/lua/
>> /snap/ipe/current/share/ipe/7.2.5/lua/
>> ├── actions.lua
>> ├── editpath.lua
>> ├── main.lua
>> ...
>>
>
> well, it looks in /share, not in /snap 
>
> try this:
> ---
> #! /bin/sh
>
> export IPELUAPATH=$SNAP/share/ipe/7.2.5/lua
>
> exec $SNAP/bin/ipe
> ---
>
> save it as wrapper.sh (make it executable), add a copy plugin part to
> your snapcraft.yaml that copies it in the toplevel of your snap
> and change:
> https://github.com/dietmarw/snaps/blob/master/ipe/snapcraft.yaml#L52
> to read:
>
> command: desktop-launch wrapper.sh
>
> if needed also set the other variables to their proper paths ...
>
> ciao
> oli



-- 
/Dietmar/

Secure email communication:
https://encrypt.to/dietmar.wink...@dwe.no
Public OpenPGP key: 0x235E6689

-- 
Snapcraft mailing list
Snapcraft@lists.snapcraft.io
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/snapcraft

Re: Getting QT apps running.

[Oliver Grawert]

hi,
On Fr, 2016-07-29 at 12:45 +0200, Dietmar Winkler wrote:
> Thanks Oli,
> 
> I've implemented it as you suggested and got one step further:
> 
> 
...
> '/snap/ipe/x22/share/ipe/7.2.5/lua':
> cannot read /snap/ipe/x22/share/ipe/7.2.5/lua: Is a directory
> 

wow, so googling a bit [1] seems to suggest that IPELUAPATH actually
wants patterns o_O (how weird) ... 

try something like:

export IPELUAPATH=$SNAP/share/ipe/7.2.5/lua/*.lua

or:

export IPELUAPATH=$SNAP/share/ipe/7.2.5/lua/?.lua

ciao
oli

[1] http://webcache.googleusercontent.com/search?q=cache:hge_N7NYCM4J:c
omments.gmane.org/gmane.comp.graphics.ipe.general/808&num=1&client=ubun
tu&hs=bEn&hl=de&gl=de&strip=1&vwsrc=0

signature.asc
Description: This is a digitally signed message part
-- 
Snapcraft mailing list
Snapcraft@lists.snapcraft.io
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/snapcraft

Re: Getting QT apps running.

[Dietmar Winkler]

Hi,

> export IPELUAPATH=$SNAP/share/ipe/7.2.5/lua/?.lua

That was it. The app now launches. Still loads of menus and icons
missing in the UI but I guess this is down to:

Gtk-Message: Failed to load module "overlay-scrollbar"
Gtk-Message: Failed to load module "gtk-vector-screenshot"
Gtk-Message: Failed to load module "gail"
Gtk-Message: Failed to load module "atk-bridge"
Gtk-Message: Failed to load module "unity-gtk-module"
Gtk-Message: Failed to load module "canberra-gtk-module"
Qt: Session management error: None of the authentication protocols
specified are supported

during start up. And of course the theme link that can not be generated:

ln: failed to create symbolic link
'/home/dietmarw/snap/ipe/x4/.themes/themes': Read-only file system

So I guess currently there is not much I can do about the gtk modules
not getting loaded. Other then wait that some day perhaps snappy will
support this.
-- 
/Dietmar/

Secure email communication:
https://encrypt.to/dietmar.wink...@dwe.no
Public OpenPGP key: 0x235E6689

-- 
Snapcraft mailing list
Snapcraft@lists.snapcraft.io
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/snapcraft

Re: Getting QT apps running.

[Oliver Grawert]

hi,
On Fr, 2016-07-29 at 13:40 +0200, Dietmar Winkler wrote:
> Hi,
> 
> > 
> > export IPELUAPATH=$SNAP/share/ipe/7.2.5/lua/?.lua
> 
> That was it. The app now launches. Still loads of menus and icons
> missing in the UI but I guess this is down to:
> 
> Gtk-Message: Failed to load module "overlay-scrollbar"
> Gtk-Message: Failed to load module "gtk-vector-screenshot"
> Gtk-Message: Failed to load module "gail"
> Gtk-Message: Failed to load module "atk-bridge"
> Gtk-Message: Failed to load module "unity-gtk-module"
> Gtk-Message: Failed to load module "canberra-gtk-module"
> Qt: Session management error: None of the authentication protocols
> specified are supported
> 
> during start up. And of course the theme link that can not be
> generated:
> 
> ln: failed to create symbolic link
> '/home/dietmarw/snap/ipe/x4/.themes/themes': Read-only file system
> 
> So I guess currently there is not much I can do about the gtk modules
> not getting loaded. Other then wait that some day perhaps snappy will
> support this.
i doubt it is related to the Gtk messages given your app is Qt (none of
the above modules are essential)  ... 

have you tried setting the other variables described in
http://ipe.otfried.org/manual/manual_40.html

looks to me like IPEICONDIR might give you icons for example ...when
set to the right location ... 
i would just try to play with these vars a bit, i bet you can sort most
of your issues when they point to the right places ...

ciao
oli

signature.asc
Description: This is a digitally signed message part
-- 
Snapcraft mailing list
Snapcraft@lists.snapcraft.io
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/snapcraft

Re: Snap daemonization ordering and manual interface connections

[MikeB]

On 7/14/2016 18:25 Mark Shuttleworth wrote:

> Great topic for the sprint in Heidelberg indeed!
>
> We could easily prompt the user appropriately, and design for CLI and
> GUI experiences shaped by the snap publisher.
>
> Mark

Was any decision or progress made on these issues in Heidelberg?

I'm really blocked by failure problems while daemonizing applications
before the manual connections are made.

Any suggested workarounds?

Thanks, Mike
-- 
Snapcraft mailing list
Snapcraft@lists.snapcraft.io
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/snapcraft

Re: Getting QT apps running.

[John Lenton]

On 29 July 2016 at 11:45, Dietmar Winkler  wrote:
> ln: failed to create symbolic link
> '/home/dietmarw/snap/ipe/x22/.themes/themes': Read-only file system

that seems strange. What is read-only in that path?

-- 
Snapcraft mailing list
Snapcraft@lists.snapcraft.io
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/snapcraft

Re: Getting QT apps running.

[Dietmar Winkler]

John,

On 29 July 2016 at 14:19, John Lenton  wrote:
> On 29 July 2016 at 11:45, Dietmar Winkler  wrote:
>> ln: failed to create symbolic link
>> '/home/dietmarw/snap/ipe/x22/.themes/themes': Read-only file system
>
> that seems strange. What is read-only in that path?

my take here is that it's because it's in a dot directory. But then
again its generated by snap itself. So this should not happen.

-- 
/Dietmar/

Secure email communication:
https://encrypt.to/dietmar.wink...@dwe.no
Public OpenPGP key: 0x235E6689

-- 
Snapcraft mailing list
Snapcraft@lists.snapcraft.io
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/snapcraft

Re: Getting QT apps running.

[Didier Roche]

Le 29/07/2016 à 14:19, John Lenton a écrit :
> On 29 July 2016 at 11:45, Dietmar Winkler  wrote:
>> ln: failed to create symbolic link
>> '/home/dietmarw/snap/ipe/x22/.themes/themes': Read-only file system
> that seems strange. What is read-only in that path?
>
That was this bug from the destkop-launcher:
https://github.com/ubuntu/snapcraft-desktop-helpers/issues/4. I fixed it
yesterday, so any new build pulling it should get it fixed.

It doesn't have any visible consequence to the user (apart if we updated
the platform themes between upgrade).

Didier


-- 
Snapcraft mailing list
Snapcraft@lists.snapcraft.io
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/snapcraft

Re: Getting QT apps running.

[Oliver Grawert]

hi,
On Fr, 2016-07-29 at 13:19 +0100, John Lenton wrote:
> On 29 July 2016 at 11:45, Dietmar Winkler 
> wrote:
> > 
> > ln: failed to create symbolic link
> > '/home/dietmarw/snap/ipe/x22/.themes/themes': Read-only file system
> 
> that seems strange. What is read-only in that path?

there is a known bug in the desktop launcher that tries to move the
link around on upgrades as i understand, dider was working on a fix ...

it is actually harmless ...

ciao
oli

signature.asc
Description: This is a digitally signed message part
-- 
Snapcraft mailing list
Snapcraft@lists.snapcraft.io
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/snapcraft

Re: Getting QT apps running.

[Dietmar Winkler]

Seting the rests of the paths helped. I now have icons. The menu is
still missing which reminded me that there currently is an issue with
appmenu-qt5 which when naively compiled causes some keyboard shortcuts
not to work.
https://github.com/otfried/ipe-wiki/wiki/FAQ#ipe-doesnt-work-correctly-on-ubuntu

I was wondering if it is possible to generate a variant of desktop/qt5
without appmenu-qt5 staged.

I've found the definition here: https://wiki.ubuntu.com/Snappy/Parts
but would still need the source to point to.

-- 
/Dietmar/

Secure email communication:
https://encrypt.to/dietmar.wink...@dwe.no
Public OpenPGP key: 0x235E6689

-- 
Snapcraft mailing list
Snapcraft@lists.snapcraft.io
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/snapcraft

Re: Getting QT apps running.

[Joe Talbott]

Note the remote parts are now at https://wiki.ubuntu.com/snapcraft/parts

Cheers,
Joe

On Fri, Jul 29, 2016 at 8:53 AM, Dietmar Winkler  wrote:
> Seting the rests of the paths helped. I now have icons. The menu is
> still missing which reminded me that there currently is an issue with
> appmenu-qt5 which when naively compiled causes some keyboard shortcuts
> not to work.
> https://github.com/otfried/ipe-wiki/wiki/FAQ#ipe-doesnt-work-correctly-on-ubuntu
>
> I was wondering if it is possible to generate a variant of desktop/qt5
> without appmenu-qt5 staged.
>
> I've found the definition here: https://wiki.ubuntu.com/Snappy/Parts
> but would still need the source to point to.
>
> --
> /Dietmar/
>
> Secure email communication:
> https://encrypt.to/dietmar.wink...@dwe.no
> Public OpenPGP key: 0x235E6689
>
> --
> Snapcraft mailing list
> Snapcraft@lists.snapcraft.io
> Modify settings or unsubscribe at: 
> https://lists.ubuntu.com/mailman/listinfo/snapcraft

-- 
Snapcraft mailing list
Snapcraft@lists.snapcraft.io
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/snapcraft

Re: Getting QT apps running.

[Dietmar Winkler]

Thanks for the pointer. Reading through the documentation of
desktop-helper again I noticed that I might actually try the x11 plug
instead of unity7 since it is the appmenu that causes problems in the
first place.

But now ipe would not launch at all. Also I don't get any error
messages (apart from the Gtk warnings).

Are there any debug logs I could search for to see what is getting stuck?



On 29 July 2016 at 15:34, Joe Talbott  wrote:
> Note the remote parts are now at https://wiki.ubuntu.com/snapcraft/parts
>
> Cheers,
> Joe
>
> On Fri, Jul 29, 2016 at 8:53 AM, Dietmar Winkler  
> wrote:
>> Seting the rests of the paths helped. I now have icons. The menu is
>> still missing which reminded me that there currently is an issue with
>> appmenu-qt5 which when naively compiled causes some keyboard shortcuts
>> not to work.
>> https://github.com/otfried/ipe-wiki/wiki/FAQ#ipe-doesnt-work-correctly-on-ubuntu
>>
>> I was wondering if it is possible to generate a variant of desktop/qt5
>> without appmenu-qt5 staged.
>>
>> I've found the definition here: https://wiki.ubuntu.com/Snappy/Parts
>> but would still need the source to point to.
>>
>> --
>> /Dietmar/
>>
>> Secure email communication:
>> https://encrypt.to/dietmar.wink...@dwe.no
>> Public OpenPGP key: 0x235E6689
>>
>> --
>> Snapcraft mailing list
>> Snapcraft@lists.snapcraft.io
>> Modify settings or unsubscribe at: 
>> https://lists.ubuntu.com/mailman/listinfo/snapcraft



-- 
/Dietmar/

Secure email communication:
https://encrypt.to/dietmar.wink...@dwe.no
Public OpenPGP key: 0x235E6689

-- 
Snapcraft mailing list
Snapcraft@lists.snapcraft.io
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/snapcraft

Getting pdflatex to work inside a spap packge

[Dietmar Winkler]

Hi,

I'm currently trying to package my first snap package [1]. That
application depends on pdflatex which I included as stage package

stage-packages:
  - texlive-latex-base

pdflatex can be executed but when an application from inside the snap
starts it it runs into trouble since pdflatex wants to access
/etc/texmf/web2c/texmf.cnf
which it cant.

It seems that the path "/etc/texmf/web2c/texmf.cnf" is actually hard
coded in the pdflatex application. I tried things like setting the
TEXMFPATH but that does not have an influence.

I was wondering if there is a solution for this without rewriting the
source of pdflatex.

The more I'm working with snap packages the more I'm getting the
feeling that it has one fundamental flaw: containerising the
application but at the same time not automatically translating paths
to inside the container. This means that one has to tweak the original
source application in order to get it to work as a snap package. But
I'd say that the application should be totally oblivious to how it is
deployed.

-- 
/Dietmar/


[1] https://github.com/dietmarw/snaps/tree/master/ipe

Secure email communication:
https://encrypt.to/dietmar.wink...@dwe.no
Public OpenPGP key: 0x235E6689

-- 
Snapcraft mailing list
Snapcraft@lists.snapcraft.io
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/snapcraft

Re: Getting pdflatex to work inside a spap packge

[Oliver Grawert]

hi,
On Fr, 2016-07-29 at 16:55 +0200, Dietmar Winkler wrote:
> 
> It seems that the path "/etc/texmf/web2c/texmf.cnf" is actually hard
> coded in the pdflatex application. I tried things like setting the
> TEXMFPATH but that does not have an influence.
> 

try TEXMFCONFIG for that one ...  

and google indicates that there is no TEXMFPATH but a TEXMFHOME instead
... [1] might be helpful

ciao
oli

[1] http://tex.stackexchange.com/questions/30494/how-to-make-latex-see-
local-texmf-tree

signature.asc
Description: This is a digitally signed message part
-- 
Snapcraft mailing list
Snapcraft@lists.snapcraft.io
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/snapcraft

Re: Getting pdflatex to work inside a spap packge

[Dietmar Winkler]

Hi,


> try TEXMFCONFIG for that one ...
>
> and google indicates that there is no TEXMFPATH but a TEXMFHOME instead
> ... [1] might be helpful

Sorry I should have said I've tried all those already (also TEXMFHOME).
As I said that path is hard coded. To be more precise in /usr/sbin/update-texmf:

TXMF=/etc/texmf
TXMF_CNF=$TXMF/web2c/texmf.cnf

:-(

-- 
/Dietmar/

Secure email communication:
https://encrypt.to/dietmar.wink...@dwe.no
Public OpenPGP key: 0x235E6689

-- 
Snapcraft mailing list
Snapcraft@lists.snapcraft.io
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/snapcraft

Re: Getting pdflatex to work inside a spap packge

[Oliver Grawert]

hi,
On Fr, 2016-07-29 at 17:10 +0200, Dietmar Winkler wrote:
> Hi,
> 
> 
> > 
> > try TEXMFCONFIG for that one ...
> > 
> > and google indicates that there is no TEXMFPATH but a TEXMFHOME
> > instead
> > ... [1] might be helpful
> 
> Sorry I should have said I've tried all those already (also
> TEXMFHOME).
> As I said that path is hard coded. To be more precise in
> /usr/sbin/update-texmf:
> 
> TXMF=/etc/texmf
> TXMF_CNF=$TXMF/web2c/texmf.cnf
> 

you could just replace these paths ... 
(when does that command run ? at runtime or at install time ?) 

ciao

oli

signature.asc
Description: This is a digitally signed message part
-- 
Snapcraft mailing list
Snapcraft@lists.snapcraft.io
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/snapcraft

Re: Getting pdflatex to work inside a spap packge

[Dietmar Winkler]

Hi,

On 29 July 2016 at 17:32, Oliver Grawert  wrote:
> you could just replace these paths ...

Well then I would to manually change the code in the stage (?) area
which would be not at all an optimal workflow.

> (when does that command run ? at runtime or at install time ?)

It happens when the ipe application triggers pdflatex.

Working example:
After having build and installed the ipe snap from

https://raw.githubusercontent.com/dietmarw/snaps/master/ipe/

you can run

ipe.ipetoipe -pdf test.ipe

on https://raw.githubusercontent.com/dietmarw/snaps/master/ipe/test/test.ipe

and should get:
$ ipe.ipetoipe -pdf test.ipe
Document test.ipe has 1 pages (1 views)
pdflatex: /etc/texmf/web2c/texmf.cnf: Permission denied
There was an error trying to run Pdflatex.

-- 
/Dietmar/

Secure email communication:
https://encrypt.to/dietmar.wink...@dwe.no
Public OpenPGP key: 0x235E6689

-- 
Snapcraft mailing list
Snapcraft@lists.snapcraft.io
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/snapcraft

Re: Getting pdflatex to work inside a spap packge

[Dietmar Winkler]

Having manually replaced the location in /usr/bin/update-texmf did not
change anything. So it is most likely embedded in the compiled binary
of pdflatex. :-(



On 29 July 2016 at 17:47, Dietmar Winkler  wrote:
> Hi,
>
> On 29 July 2016 at 17:32, Oliver Grawert  wrote:
>> you could just replace these paths ...
>
> Well then I would to manually change the code in the stage (?) area
> which would be not at all an optimal workflow.
>
>> (when does that command run ? at runtime or at install time ?)
>
> It happens when the ipe application triggers pdflatex.
>
> Working example:
> After having build and installed the ipe snap from
>
> https://raw.githubusercontent.com/dietmarw/snaps/master/ipe/
>
> you can run
>
> ipe.ipetoipe -pdf test.ipe
>
> on https://raw.githubusercontent.com/dietmarw/snaps/master/ipe/test/test.ipe
>
> and should get:
> $ ipe.ipetoipe -pdf test.ipe
> Document test.ipe has 1 pages (1 views)
> pdflatex: /etc/texmf/web2c/texmf.cnf: Permission denied
> There was an error trying to run Pdflatex.
>
> --
> /Dietmar/
>
> Secure email communication:
> https://encrypt.to/dietmar.wink...@dwe.no
> Public OpenPGP key: 0x235E6689



-- 
/Dietmar/

Secure email communication:
https://encrypt.to/dietmar.wink...@dwe.no
Public OpenPGP key: 0x235E6689

-- 
Snapcraft mailing list
Snapcraft@lists.snapcraft.io
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/snapcraft

Re: Getting pdflatex to work inside a spap packge

[Dietmar Winkler]

Sorry I meant of course "/usr/sbin/update-texmf"


-- 
/Dietmar/

Secure email communication:
https://encrypt.to/dietmar.wink...@dwe.no
Public OpenPGP key: 0x235E6689

-- 
Snapcraft mailing list
Snapcraft@lists.snapcraft.io
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/snapcraft

Re: no hardware description in Gadget snap for building an image

[Luke Williams]

So in the interim, how do we build custom images with custom kernels?

Should we use the image from mvo and then apply our kernel snaps via ’snap 
install’ for testing?
 
Thanks,

Luke Williams - Technical Partner Manager, Network Switches/Ubuntu-Core
email: luke.willi...@canonical.com 
http://www.canonical.com/  | http://www.ubuntu.com 






> On Jul 29, 2016, at 3:02 AM, Gustavo Niemeyer 
>  wrote:
> 
> For the record, please note this change was announced in this list a couple 
> of months ago, and that we don't actually have official Ubuntu Core 16 images 
> yet.
> 
> Polishing the format is being done while finalizing those images.
> 
> 
> On Jul 28, 2016 8:03 PM, "Michael Vogt"  > wrote:
> On Thu, Jul 28, 2016 at 05:50:54PM +0800, Woodrow Shen wrote:
> > Hi all,
> Hi Woodrow,
> 
> thanks for your mail!
> 
> > It seems the latest revision 8 has a lack of hardware section for gadget
> > snap.
> > I think someone is working on it now, but hope we can make sure the snap
> > uploaded to edge channel can work at least.
> 
> You are correct, we are currently working on a new and improved format
> to describe the bootloader for a device. This work is currently in
> progress and because the old format stops working we removed it. We
> publish new gadget snaps with the new format soon. ubuntu-image will
> be the tool to consume them then.
> 
> Cheers,
>  Michael
> 
> --
> Snapcraft mailing list
> Snapcraft@lists.snapcraft.io 
> Modify settings or unsubscribe at: 
> https://lists.ubuntu.com/mailman/listinfo/snapcraft 
> 
> -- 
> Snapcraft mailing list
> Snapcraft@lists.snapcraft.io
> Modify settings or unsubscribe at: 
> https://lists.ubuntu.com/mailman/listinfo/snapcraft

-- 
Snapcraft mailing list
Snapcraft@lists.snapcraft.io
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/snapcraft