Re: [qubes-users] installing Signal on Qubes mini-HOWTO

[IX4 Svs]

On Sun, Sep 18, 2016 at 9:13 PM, Marek Marczykowski-Górecki <
marma...@invisiblethingslab.com> wrote:

> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA256
>
> On Sun, Sep 18, 2016 at 09:09:58PM +0100, IX4 Svs wrote:
> > On Sat, Sep 17, 2016 at 11:41 PM, Marek Marczykowski-Górecki <
> > marma...@invisiblethingslab.com> wrote:
> >
> > > -BEGIN PGP SIGNED MESSAGE-
> > > Hash: SHA256
> > >
> > > On Sat, Sep 17, 2016 at 03:52:17PM +0100, IX4 Svs wrote:
> > > > On Wed, Sep 14, 2016 at 9:26 AM, Marek Marczykowski-Górecki <
> > > > marma...@invisiblethingslab.com> wrote:
> > > >
> > > > > -BEGIN PGP SIGNED MESSAGE-
> > > > > Hash: SHA256
> > > > >
> > > > > On Wed, Sep 07, 2016 at 11:38:55PM +0100, IX4 Svs wrote:
> > > > > > On Thu, Sep 1, 2016 at 8:41 AM, IX4 Svs 
> wrote:
> > > > > >
> > > > > > > On Thu, Sep 1, 2016 at 2:21 AM, Andrew David Wong <
> > > a...@qubes-os.org>
> > > > > > > wrote:
> > > > > > >
> > > > > > >> -BEGIN PGP SIGNED MESSAGE-
> > > > > > >> Hash: SHA512
> > > > > > >>
> > > > > > >> On 2016-08-31 15:50, IX4 Svs wrote:
> > > > > > >> > On Wed, Aug 24, 2016 at 11:10 PM, Andrew David Wong <
> > > > > a...@qubes-os.org>
> > > > > > >> > wrote:
> > > > > > >> >
> > > > > > >> >>
> > > > > > >> >> On 2016-08-15 14:43, IX4 Svs wrote:
> > > > > > >> >>> On Mon, Aug 15, 2016 at 10:19 AM, Andrew David Wong <
> > > > > a...@qubes-os.org
> > > > > > >> >
> > > > > > >> >>> wrote:
> > > > > > >> >>>
> > > > > > >> 
> > > > > > >>  On 2016-08-14 15:22, IX4 Svs wrote:
> > > > > > >> > Just spent a few minutes to figure this out so I
> thought I'd
> > > > > > >> > share.
> > > > > > >> >
> > > > > > >> 
> > > > > > >>  Thanks, Alex! Would you mind if we added this to the
> docs at
> > > some
> > > > > > >>  point?
> > > > > > >> 
> > > > > > >> 
> > > > > > >> >>> Not at all - especially if you improve my clumsy way of
> > > creating
> > > > > the
> > > > > > >> >> custom
> > > > > > >> >>> shortcut (steps 7-12) and use the proper Qubes way that
> > > Nicklaus
> > > > > > >> >>> linked to.
> > > > > > >> >>>
> > > > > > >> >>> Cheers,
> > > > > > >> >>>
> > > > > > >> >>> Alex
> > > > > > >> >>>
> > > > > > >> >>
> > > > > > >> >> Added:
> > > > > > >> >>
> > > > > > >> >> https://www.qubes-os.org/doc/signal/
> > > > > > >> >>
> > > > > > >> >>
> > > > > > >> > Andrew, thanks for adding this to the documentation.
> > > > > > >> >
> > > > > > >> > I'm afraid my DIY shortcut kludge does not survive
> > > some(potentially
> > > > > boot
> > > > > > >> > time) script and is wiped away from the taskbar, only to be
> > > > > replaced by
> > > > > > >> a
> > > > > > >> > default "Chrome browser" shortcut. I admit I don't quite
> > > comprehend
> > > > > what
> > > > > > >> > the actual implementation of
> > > > > > >> > https://www.qubes-os.org/doc/managing-appvm-shortcuts/#
> > > > > tocAnchor-1-1-1
> > > > > > >> > should be.
> > > > > > >>
> > > > > > >> Neither do I. I've always make my custom shortcuts the same
> > > general
> > > > > way
> > > > > > >> you do.
> > > > > > >>
> > > > > > >>
> > > > > > > Ah, we have a usability issue here then.
> > > > > > >
> > > > > > >
> > > > > > >> > A worked example that replaces all but the first step of
> the "
> > > > > Creating
> > > > > > >> a
> > > > > > >> > Shortcut in KDE" section of https://www.qubes-os.org/doc/
> > > signal/
> > > > > would
> > > > > > >> be
> > > > > > >> > very much welcome.
> > > > > > >> >
> > > > > > >>
> > > > > > >> Agreed.
> > > > > > >>
> > > > > > >
> > > > > > > Can someone who has figured out how to create one-click
> buttons to
> > > > > launch
> > > > > > > arbitrary applications in AppVMs chime in with an example
> please?
> > > I'll
> > > > > then
> > > > > > > test it and Andrew can stick it in the wiki for all Qubes
> users to
> > > > > benefit.
> > > > > > >
> > > > > >
> > > > > > I had a look myself and may have figured out the "proper" way of
> > > > > creating a
> > > > > > shortcut to launch Signal. By the way I submitted a pull request
> for
> > > the
> > > > > > documentation at https://www.qubes-os.org/doc/m
> > > > > > anaging-appvm-shortcuts/#tocAnchor-1-1-1 because its language is
> > > > > slightly
> > > > > > inaccurate.
> > > > > >
> > > > > > These instructions (after verification) should replace the
> shortcut
> > > > > kludge
> > > > > > of the signal page you created:
> > > > > >
> > > > > > My Signal AppVM uses the fedora-23 template, and I have renamed
> the
> > > > > > .desktop file that Chrome created on that AppVM's desktop to
> > > > > > signal.desktop. Now what?
> > > > > >
> > > > > > 1. Open a dom0 terminal, cd to /var/lib/qubes/vm-templates/
> > > fedora-23/
> > > > > > 2. Copy Signal:/home/user/Desktop/signal.desktop to
> > > > > > dom0:/var/lib/qubes/vm-templates/fedora-23/apps.
> > > templates/signal.desktop
> > > > > > 3. Lightly edit
> > > > > > dom0:/var/lib/qubes/vm-templates/fedora-23/apps.
> > > 

Re: [qubes-users] installing Signal on Qubes mini-HOWTO

[Marek Marczykowski-Górecki]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

On Sun, Sep 18, 2016 at 09:09:58PM +0100, IX4 Svs wrote:
> On Sat, Sep 17, 2016 at 11:41 PM, Marek Marczykowski-Górecki <
> marma...@invisiblethingslab.com> wrote:
> 
> > -BEGIN PGP SIGNED MESSAGE-
> > Hash: SHA256
> >
> > On Sat, Sep 17, 2016 at 03:52:17PM +0100, IX4 Svs wrote:
> > > On Wed, Sep 14, 2016 at 9:26 AM, Marek Marczykowski-Górecki <
> > > marma...@invisiblethingslab.com> wrote:
> > >
> > > > -BEGIN PGP SIGNED MESSAGE-
> > > > Hash: SHA256
> > > >
> > > > On Wed, Sep 07, 2016 at 11:38:55PM +0100, IX4 Svs wrote:
> > > > > On Thu, Sep 1, 2016 at 8:41 AM, IX4 Svs  wrote:
> > > > >
> > > > > > On Thu, Sep 1, 2016 at 2:21 AM, Andrew David Wong <
> > a...@qubes-os.org>
> > > > > > wrote:
> > > > > >
> > > > > >> -BEGIN PGP SIGNED MESSAGE-
> > > > > >> Hash: SHA512
> > > > > >>
> > > > > >> On 2016-08-31 15:50, IX4 Svs wrote:
> > > > > >> > On Wed, Aug 24, 2016 at 11:10 PM, Andrew David Wong <
> > > > a...@qubes-os.org>
> > > > > >> > wrote:
> > > > > >> >
> > > > > >> >>
> > > > > >> >> On 2016-08-15 14:43, IX4 Svs wrote:
> > > > > >> >>> On Mon, Aug 15, 2016 at 10:19 AM, Andrew David Wong <
> > > > a...@qubes-os.org
> > > > > >> >
> > > > > >> >>> wrote:
> > > > > >> >>>
> > > > > >> 
> > > > > >>  On 2016-08-14 15:22, IX4 Svs wrote:
> > > > > >> > Just spent a few minutes to figure this out so I thought I'd
> > > > > >> > share.
> > > > > >> >
> > > > > >> 
> > > > > >>  Thanks, Alex! Would you mind if we added this to the docs at
> > some
> > > > > >>  point?
> > > > > >> 
> > > > > >> 
> > > > > >> >>> Not at all - especially if you improve my clumsy way of
> > creating
> > > > the
> > > > > >> >> custom
> > > > > >> >>> shortcut (steps 7-12) and use the proper Qubes way that
> > Nicklaus
> > > > > >> >>> linked to.
> > > > > >> >>>
> > > > > >> >>> Cheers,
> > > > > >> >>>
> > > > > >> >>> Alex
> > > > > >> >>>
> > > > > >> >>
> > > > > >> >> Added:
> > > > > >> >>
> > > > > >> >> https://www.qubes-os.org/doc/signal/
> > > > > >> >>
> > > > > >> >>
> > > > > >> > Andrew, thanks for adding this to the documentation.
> > > > > >> >
> > > > > >> > I'm afraid my DIY shortcut kludge does not survive
> > some(potentially
> > > > boot
> > > > > >> > time) script and is wiped away from the taskbar, only to be
> > > > replaced by
> > > > > >> a
> > > > > >> > default "Chrome browser" shortcut. I admit I don't quite
> > comprehend
> > > > what
> > > > > >> > the actual implementation of
> > > > > >> > https://www.qubes-os.org/doc/managing-appvm-shortcuts/#
> > > > tocAnchor-1-1-1
> > > > > >> > should be.
> > > > > >>
> > > > > >> Neither do I. I've always make my custom shortcuts the same
> > general
> > > > way
> > > > > >> you do.
> > > > > >>
> > > > > >>
> > > > > > Ah, we have a usability issue here then.
> > > > > >
> > > > > >
> > > > > >> > A worked example that replaces all but the first step of the "
> > > > Creating
> > > > > >> a
> > > > > >> > Shortcut in KDE" section of https://www.qubes-os.org/doc/
> > signal/
> > > > would
> > > > > >> be
> > > > > >> > very much welcome.
> > > > > >> >
> > > > > >>
> > > > > >> Agreed.
> > > > > >>
> > > > > >
> > > > > > Can someone who has figured out how to create one-click buttons to
> > > > launch
> > > > > > arbitrary applications in AppVMs chime in with an example please?
> > I'll
> > > > then
> > > > > > test it and Andrew can stick it in the wiki for all Qubes users to
> > > > benefit.
> > > > > >
> > > > >
> > > > > I had a look myself and may have figured out the "proper" way of
> > > > creating a
> > > > > shortcut to launch Signal. By the way I submitted a pull request for
> > the
> > > > > documentation at https://www.qubes-os.org/doc/m
> > > > > anaging-appvm-shortcuts/#tocAnchor-1-1-1 because its language is
> > > > slightly
> > > > > inaccurate.
> > > > >
> > > > > These instructions (after verification) should replace the shortcut
> > > > kludge
> > > > > of the signal page you created:
> > > > >
> > > > > My Signal AppVM uses the fedora-23 template, and I have renamed the
> > > > > .desktop file that Chrome created on that AppVM's desktop to
> > > > > signal.desktop. Now what?
> > > > >
> > > > > 1. Open a dom0 terminal, cd to /var/lib/qubes/vm-templates/
> > fedora-23/
> > > > > 2. Copy Signal:/home/user/Desktop/signal.desktop to
> > > > > dom0:/var/lib/qubes/vm-templates/fedora-23/apps.
> > templates/signal.desktop
> > > > > 3. Lightly edit
> > > > > dom0:/var/lib/qubes/vm-templates/fedora-23/apps.
> > templates/signal.desktop
> > > > to
> > > > > be as follows:
> > > > >
> > > > > [Desktop Entry]
> > > > > Version=1.0
> > > > > Type=Application
> > > > > Terminal=false
> > > > > X-Qubes-VmName=%VMNAME%
> > > > > Icon=%VMDIR%/apps.icons/signal.png
> > > > > Name=%VMNAME%: Signal Private Messenger
> > > > > GenericName=%VMNAME%: Signal
> > > > > Comment=Private Instant Messenger
> > > > > Exec=qvm-run -q 

Re: [qubes-users] installing Signal on Qubes mini-HOWTO

[IX4 Svs]

On Sat, Sep 17, 2016 at 11:41 PM, Marek Marczykowski-Górecki <
marma...@invisiblethingslab.com> wrote:

> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA256
>
> On Sat, Sep 17, 2016 at 03:52:17PM +0100, IX4 Svs wrote:
> > On Wed, Sep 14, 2016 at 9:26 AM, Marek Marczykowski-Górecki <
> > marma...@invisiblethingslab.com> wrote:
> >
> > > -BEGIN PGP SIGNED MESSAGE-
> > > Hash: SHA256
> > >
> > > On Wed, Sep 07, 2016 at 11:38:55PM +0100, IX4 Svs wrote:
> > > > On Thu, Sep 1, 2016 at 8:41 AM, IX4 Svs  wrote:
> > > >
> > > > > On Thu, Sep 1, 2016 at 2:21 AM, Andrew David Wong <
> a...@qubes-os.org>
> > > > > wrote:
> > > > >
> > > > >> -BEGIN PGP SIGNED MESSAGE-
> > > > >> Hash: SHA512
> > > > >>
> > > > >> On 2016-08-31 15:50, IX4 Svs wrote:
> > > > >> > On Wed, Aug 24, 2016 at 11:10 PM, Andrew David Wong <
> > > a...@qubes-os.org>
> > > > >> > wrote:
> > > > >> >
> > > > >> >>
> > > > >> >> On 2016-08-15 14:43, IX4 Svs wrote:
> > > > >> >>> On Mon, Aug 15, 2016 at 10:19 AM, Andrew David Wong <
> > > a...@qubes-os.org
> > > > >> >
> > > > >> >>> wrote:
> > > > >> >>>
> > > > >> 
> > > > >>  On 2016-08-14 15:22, IX4 Svs wrote:
> > > > >> > Just spent a few minutes to figure this out so I thought I'd
> > > > >> > share.
> > > > >> >
> > > > >> 
> > > > >>  Thanks, Alex! Would you mind if we added this to the docs at
> some
> > > > >>  point?
> > > > >> 
> > > > >> 
> > > > >> >>> Not at all - especially if you improve my clumsy way of
> creating
> > > the
> > > > >> >> custom
> > > > >> >>> shortcut (steps 7-12) and use the proper Qubes way that
> Nicklaus
> > > > >> >>> linked to.
> > > > >> >>>
> > > > >> >>> Cheers,
> > > > >> >>>
> > > > >> >>> Alex
> > > > >> >>>
> > > > >> >>
> > > > >> >> Added:
> > > > >> >>
> > > > >> >> https://www.qubes-os.org/doc/signal/
> > > > >> >>
> > > > >> >>
> > > > >> > Andrew, thanks for adding this to the documentation.
> > > > >> >
> > > > >> > I'm afraid my DIY shortcut kludge does not survive
> some(potentially
> > > boot
> > > > >> > time) script and is wiped away from the taskbar, only to be
> > > replaced by
> > > > >> a
> > > > >> > default "Chrome browser" shortcut. I admit I don't quite
> comprehend
> > > what
> > > > >> > the actual implementation of
> > > > >> > https://www.qubes-os.org/doc/managing-appvm-shortcuts/#
> > > tocAnchor-1-1-1
> > > > >> > should be.
> > > > >>
> > > > >> Neither do I. I've always make my custom shortcuts the same
> general
> > > way
> > > > >> you do.
> > > > >>
> > > > >>
> > > > > Ah, we have a usability issue here then.
> > > > >
> > > > >
> > > > >> > A worked example that replaces all but the first step of the "
> > > Creating
> > > > >> a
> > > > >> > Shortcut in KDE" section of https://www.qubes-os.org/doc/
> signal/
> > > would
> > > > >> be
> > > > >> > very much welcome.
> > > > >> >
> > > > >>
> > > > >> Agreed.
> > > > >>
> > > > >
> > > > > Can someone who has figured out how to create one-click buttons to
> > > launch
> > > > > arbitrary applications in AppVMs chime in with an example please?
> I'll
> > > then
> > > > > test it and Andrew can stick it in the wiki for all Qubes users to
> > > benefit.
> > > > >
> > > >
> > > > I had a look myself and may have figured out the "proper" way of
> > > creating a
> > > > shortcut to launch Signal. By the way I submitted a pull request for
> the
> > > > documentation at https://www.qubes-os.org/doc/m
> > > > anaging-appvm-shortcuts/#tocAnchor-1-1-1 because its language is
> > > slightly
> > > > inaccurate.
> > > >
> > > > These instructions (after verification) should replace the shortcut
> > > kludge
> > > > of the signal page you created:
> > > >
> > > > My Signal AppVM uses the fedora-23 template, and I have renamed the
> > > > .desktop file that Chrome created on that AppVM's desktop to
> > > > signal.desktop. Now what?
> > > >
> > > > 1. Open a dom0 terminal, cd to /var/lib/qubes/vm-templates/
> fedora-23/
> > > > 2. Copy Signal:/home/user/Desktop/signal.desktop to
> > > > dom0:/var/lib/qubes/vm-templates/fedora-23/apps.
> templates/signal.desktop
> > > > 3. Lightly edit
> > > > dom0:/var/lib/qubes/vm-templates/fedora-23/apps.
> templates/signal.desktop
> > > to
> > > > be as follows:
> > > >
> > > > [Desktop Entry]
> > > > Version=1.0
> > > > Type=Application
> > > > Terminal=false
> > > > X-Qubes-VmName=%VMNAME%
> > > > Icon=%VMDIR%/apps.icons/signal.png
> > > > Name=%VMNAME%: Signal Private Messenger
> > > > GenericName=%VMNAME%: Signal
> > > > Comment=Private Instant Messenger
> > > > Exec=qvm-run -q --tray -a %VMNAME% -- 'qubes-desktop-run
> > > > /home/user/Desktop/Signal.desktop'
> > > >
> > > > 4. Copy
> > > > Signal:/rw/home/user/.local/share/icons/hicolor/48x48/
> > > apps/chrome--Default.png
> > > >  to
> > > > dom0:/var/lib/qubes/vm-templates/fedora-23/apps.
> > > templates/apps.icons/signal.png
> > > >
> > > > 5. Copy
> > > > dom0:/var/lib/qubes/vm-templates/fedora-23/apps.
> > > 

Re: [qubes-users] installing Signal on Qubes mini-HOWTO

[Marek Marczykowski-Górecki]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

On Sat, Sep 17, 2016 at 03:52:17PM +0100, IX4 Svs wrote:
> On Wed, Sep 14, 2016 at 9:26 AM, Marek Marczykowski-Górecki <
> marma...@invisiblethingslab.com> wrote:
> 
> > -BEGIN PGP SIGNED MESSAGE-
> > Hash: SHA256
> >
> > On Wed, Sep 07, 2016 at 11:38:55PM +0100, IX4 Svs wrote:
> > > On Thu, Sep 1, 2016 at 8:41 AM, IX4 Svs  wrote:
> > >
> > > > On Thu, Sep 1, 2016 at 2:21 AM, Andrew David Wong 
> > > > wrote:
> > > >
> > > >> -BEGIN PGP SIGNED MESSAGE-
> > > >> Hash: SHA512
> > > >>
> > > >> On 2016-08-31 15:50, IX4 Svs wrote:
> > > >> > On Wed, Aug 24, 2016 at 11:10 PM, Andrew David Wong <
> > a...@qubes-os.org>
> > > >> > wrote:
> > > >> >
> > > >> >>
> > > >> >> On 2016-08-15 14:43, IX4 Svs wrote:
> > > >> >>> On Mon, Aug 15, 2016 at 10:19 AM, Andrew David Wong <
> > a...@qubes-os.org
> > > >> >
> > > >> >>> wrote:
> > > >> >>>
> > > >> 
> > > >>  On 2016-08-14 15:22, IX4 Svs wrote:
> > > >> > Just spent a few minutes to figure this out so I thought I'd
> > > >> > share.
> > > >> >
> > > >> 
> > > >>  Thanks, Alex! Would you mind if we added this to the docs at some
> > > >>  point?
> > > >> 
> > > >> 
> > > >> >>> Not at all - especially if you improve my clumsy way of creating
> > the
> > > >> >> custom
> > > >> >>> shortcut (steps 7-12) and use the proper Qubes way that Nicklaus
> > > >> >>> linked to.
> > > >> >>>
> > > >> >>> Cheers,
> > > >> >>>
> > > >> >>> Alex
> > > >> >>>
> > > >> >>
> > > >> >> Added:
> > > >> >>
> > > >> >> https://www.qubes-os.org/doc/signal/
> > > >> >>
> > > >> >>
> > > >> > Andrew, thanks for adding this to the documentation.
> > > >> >
> > > >> > I'm afraid my DIY shortcut kludge does not survive some(potentially
> > boot
> > > >> > time) script and is wiped away from the taskbar, only to be
> > replaced by
> > > >> a
> > > >> > default "Chrome browser" shortcut. I admit I don't quite comprehend
> > what
> > > >> > the actual implementation of
> > > >> > https://www.qubes-os.org/doc/managing-appvm-shortcuts/#
> > tocAnchor-1-1-1
> > > >> > should be.
> > > >>
> > > >> Neither do I. I've always make my custom shortcuts the same general
> > way
> > > >> you do.
> > > >>
> > > >>
> > > > Ah, we have a usability issue here then.
> > > >
> > > >
> > > >> > A worked example that replaces all but the first step of the "
> > Creating
> > > >> a
> > > >> > Shortcut in KDE" section of https://www.qubes-os.org/doc/signal/
> > would
> > > >> be
> > > >> > very much welcome.
> > > >> >
> > > >>
> > > >> Agreed.
> > > >>
> > > >
> > > > Can someone who has figured out how to create one-click buttons to
> > launch
> > > > arbitrary applications in AppVMs chime in with an example please? I'll
> > then
> > > > test it and Andrew can stick it in the wiki for all Qubes users to
> > benefit.
> > > >
> > >
> > > I had a look myself and may have figured out the "proper" way of
> > creating a
> > > shortcut to launch Signal. By the way I submitted a pull request for the
> > > documentation at https://www.qubes-os.org/doc/m
> > > anaging-appvm-shortcuts/#tocAnchor-1-1-1 because its language is
> > slightly
> > > inaccurate.
> > >
> > > These instructions (after verification) should replace the shortcut
> > kludge
> > > of the signal page you created:
> > >
> > > My Signal AppVM uses the fedora-23 template, and I have renamed the
> > > .desktop file that Chrome created on that AppVM's desktop to
> > > signal.desktop. Now what?
> > >
> > > 1. Open a dom0 terminal, cd to /var/lib/qubes/vm-templates/fedora-23/
> > > 2. Copy Signal:/home/user/Desktop/signal.desktop to
> > > dom0:/var/lib/qubes/vm-templates/fedora-23/apps.templates/signal.desktop
> > > 3. Lightly edit
> > > dom0:/var/lib/qubes/vm-templates/fedora-23/apps.templates/signal.desktop
> > to
> > > be as follows:
> > >
> > > [Desktop Entry]
> > > Version=1.0
> > > Type=Application
> > > Terminal=false
> > > X-Qubes-VmName=%VMNAME%
> > > Icon=%VMDIR%/apps.icons/signal.png
> > > Name=%VMNAME%: Signal Private Messenger
> > > GenericName=%VMNAME%: Signal
> > > Comment=Private Instant Messenger
> > > Exec=qvm-run -q --tray -a %VMNAME% -- 'qubes-desktop-run
> > > /home/user/Desktop/Signal.desktop'
> > >
> > > 4. Copy
> > > Signal:/rw/home/user/.local/share/icons/hicolor/48x48/
> > apps/chrome--Default.png
> > >  to
> > > dom0:/var/lib/qubes/vm-templates/fedora-23/apps.
> > templates/apps.icons/signal.png
> > >
> > > 5. Copy
> > > dom0:/var/lib/qubes/vm-templates/fedora-23/apps.
> > templates/apps.icons/signal.png
> > > to
> > > dom0:/var/lib/qubes/vm-templates/fedora-23/apps.
> > templates/apps.tempicons/signal.png
> > >
> > > 6. At this point you should be all set. Ensure Qubes knows about the new
> > > menu item you created by starting the fedora-23 template VM and then
> > > running in a dom0 terminal: qvm-sync-appmenus fedora-23
> > >
> > > 7. You should now be able to go back to the GUI and from the 

Re: [qubes-users] installing Signal on Qubes mini-HOWTO

[IX4 Svs]

On Wed, Sep 14, 2016 at 9:26 AM, Marek Marczykowski-Górecki <
marma...@invisiblethingslab.com> wrote:

> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA256
>
> On Wed, Sep 07, 2016 at 11:38:55PM +0100, IX4 Svs wrote:
> > On Thu, Sep 1, 2016 at 8:41 AM, IX4 Svs  wrote:
> >
> > > On Thu, Sep 1, 2016 at 2:21 AM, Andrew David Wong 
> > > wrote:
> > >
> > >> -BEGIN PGP SIGNED MESSAGE-
> > >> Hash: SHA512
> > >>
> > >> On 2016-08-31 15:50, IX4 Svs wrote:
> > >> > On Wed, Aug 24, 2016 at 11:10 PM, Andrew David Wong <
> a...@qubes-os.org>
> > >> > wrote:
> > >> >
> > >> >>
> > >> >> On 2016-08-15 14:43, IX4 Svs wrote:
> > >> >>> On Mon, Aug 15, 2016 at 10:19 AM, Andrew David Wong <
> a...@qubes-os.org
> > >> >
> > >> >>> wrote:
> > >> >>>
> > >> 
> > >>  On 2016-08-14 15:22, IX4 Svs wrote:
> > >> > Just spent a few minutes to figure this out so I thought I'd
> > >> > share.
> > >> >
> > >> 
> > >>  Thanks, Alex! Would you mind if we added this to the docs at some
> > >>  point?
> > >> 
> > >> 
> > >> >>> Not at all - especially if you improve my clumsy way of creating
> the
> > >> >> custom
> > >> >>> shortcut (steps 7-12) and use the proper Qubes way that Nicklaus
> > >> >>> linked to.
> > >> >>>
> > >> >>> Cheers,
> > >> >>>
> > >> >>> Alex
> > >> >>>
> > >> >>
> > >> >> Added:
> > >> >>
> > >> >> https://www.qubes-os.org/doc/signal/
> > >> >>
> > >> >>
> > >> > Andrew, thanks for adding this to the documentation.
> > >> >
> > >> > I'm afraid my DIY shortcut kludge does not survive some(potentially
> boot
> > >> > time) script and is wiped away from the taskbar, only to be
> replaced by
> > >> a
> > >> > default "Chrome browser" shortcut. I admit I don't quite comprehend
> what
> > >> > the actual implementation of
> > >> > https://www.qubes-os.org/doc/managing-appvm-shortcuts/#
> tocAnchor-1-1-1
> > >> > should be.
> > >>
> > >> Neither do I. I've always make my custom shortcuts the same general
> way
> > >> you do.
> > >>
> > >>
> > > Ah, we have a usability issue here then.
> > >
> > >
> > >> > A worked example that replaces all but the first step of the "
> Creating
> > >> a
> > >> > Shortcut in KDE" section of https://www.qubes-os.org/doc/signal/
> would
> > >> be
> > >> > very much welcome.
> > >> >
> > >>
> > >> Agreed.
> > >>
> > >
> > > Can someone who has figured out how to create one-click buttons to
> launch
> > > arbitrary applications in AppVMs chime in with an example please? I'll
> then
> > > test it and Andrew can stick it in the wiki for all Qubes users to
> benefit.
> > >
> >
> > I had a look myself and may have figured out the "proper" way of
> creating a
> > shortcut to launch Signal. By the way I submitted a pull request for the
> > documentation at https://www.qubes-os.org/doc/m
> > anaging-appvm-shortcuts/#tocAnchor-1-1-1 because its language is
> slightly
> > inaccurate.
> >
> > These instructions (after verification) should replace the shortcut
> kludge
> > of the signal page you created:
> >
> > My Signal AppVM uses the fedora-23 template, and I have renamed the
> > .desktop file that Chrome created on that AppVM's desktop to
> > signal.desktop. Now what?
> >
> > 1. Open a dom0 terminal, cd to /var/lib/qubes/vm-templates/fedora-23/
> > 2. Copy Signal:/home/user/Desktop/signal.desktop to
> > dom0:/var/lib/qubes/vm-templates/fedora-23/apps.templates/signal.desktop
> > 3. Lightly edit
> > dom0:/var/lib/qubes/vm-templates/fedora-23/apps.templates/signal.desktop
> to
> > be as follows:
> >
> > [Desktop Entry]
> > Version=1.0
> > Type=Application
> > Terminal=false
> > X-Qubes-VmName=%VMNAME%
> > Icon=%VMDIR%/apps.icons/signal.png
> > Name=%VMNAME%: Signal Private Messenger
> > GenericName=%VMNAME%: Signal
> > Comment=Private Instant Messenger
> > Exec=qvm-run -q --tray -a %VMNAME% -- 'qubes-desktop-run
> > /home/user/Desktop/Signal.desktop'
> >
> > 4. Copy
> > Signal:/rw/home/user/.local/share/icons/hicolor/48x48/
> apps/chrome--Default.png
> >  to
> > dom0:/var/lib/qubes/vm-templates/fedora-23/apps.
> templates/apps.icons/signal.png
> >
> > 5. Copy
> > dom0:/var/lib/qubes/vm-templates/fedora-23/apps.
> templates/apps.icons/signal.png
> > to
> > dom0:/var/lib/qubes/vm-templates/fedora-23/apps.
> templates/apps.tempicons/signal.png
> >
> > 6. At this point you should be all set. Ensure Qubes knows about the new
> > menu item you created by starting the fedora-23 template VM and then
> > running in a dom0 terminal: qvm-sync-appmenus fedora-23
> >
> > 7. You should now be able to go back to the GUI and from the Q menu: Q ->
> > Domain: Signal -> Signal: Add more shortcuts...
> > In the window that will appear, you should now have "Signal Private
> > Messenger" on the left list of available apps. I moved this to the
> > "Selected" list and hit OK, which put the entry in my Q menu.
> >
> > 8. Then I went to Q -> Domain: Signal. I right-clicked on "Signal:Signal
> > Private Messenger" and selected "Add to panel".

Re: [qubes-users] installing Signal on Qubes mini-HOWTO

[Marek Marczykowski-Górecki]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

On Wed, Sep 07, 2016 at 11:38:55PM +0100, IX4 Svs wrote:
> On Thu, Sep 1, 2016 at 8:41 AM, IX4 Svs  wrote:
> 
> > On Thu, Sep 1, 2016 at 2:21 AM, Andrew David Wong 
> > wrote:
> >
> >> -BEGIN PGP SIGNED MESSAGE-
> >> Hash: SHA512
> >>
> >> On 2016-08-31 15:50, IX4 Svs wrote:
> >> > On Wed, Aug 24, 2016 at 11:10 PM, Andrew David Wong 
> >> > wrote:
> >> >
> >> >>
> >> >> On 2016-08-15 14:43, IX4 Svs wrote:
> >> >>> On Mon, Aug 15, 2016 at 10:19 AM, Andrew David Wong  >> >
> >> >>> wrote:
> >> >>>
> >> 
> >>  On 2016-08-14 15:22, IX4 Svs wrote:
> >> > Just spent a few minutes to figure this out so I thought I'd
> >> > share.
> >> >
> >> 
> >>  Thanks, Alex! Would you mind if we added this to the docs at some
> >>  point?
> >> 
> >> 
> >> >>> Not at all - especially if you improve my clumsy way of creating the
> >> >> custom
> >> >>> shortcut (steps 7-12) and use the proper Qubes way that Nicklaus
> >> >>> linked to.
> >> >>>
> >> >>> Cheers,
> >> >>>
> >> >>> Alex
> >> >>>
> >> >>
> >> >> Added:
> >> >>
> >> >> https://www.qubes-os.org/doc/signal/
> >> >>
> >> >>
> >> > Andrew, thanks for adding this to the documentation.
> >> >
> >> > I'm afraid my DIY shortcut kludge does not survive some(potentially boot
> >> > time) script and is wiped away from the taskbar, only to be replaced by
> >> a
> >> > default "Chrome browser" shortcut. I admit I don't quite comprehend what
> >> > the actual implementation of
> >> > https://www.qubes-os.org/doc/managing-appvm-shortcuts/#tocAnchor-1-1-1
> >> > should be.
> >>
> >> Neither do I. I've always make my custom shortcuts the same general way
> >> you do.
> >>
> >>
> > Ah, we have a usability issue here then.
> >
> >
> >> > A worked example that replaces all but the first step of the " Creating
> >> a
> >> > Shortcut in KDE" section of https://www.qubes-os.org/doc/signal/ would
> >> be
> >> > very much welcome.
> >> >
> >>
> >> Agreed.
> >>
> >
> > Can someone who has figured out how to create one-click buttons to launch
> > arbitrary applications in AppVMs chime in with an example please? I'll then
> > test it and Andrew can stick it in the wiki for all Qubes users to benefit.
> >
> 
> I had a look myself and may have figured out the "proper" way of creating a
> shortcut to launch Signal. By the way I submitted a pull request for the
> documentation at https://www.qubes-os.org/doc/m
> anaging-appvm-shortcuts/#tocAnchor-1-1-1 because its language is slightly
> inaccurate.
> 
> These instructions (after verification) should replace the shortcut kludge
> of the signal page you created:
> 
> My Signal AppVM uses the fedora-23 template, and I have renamed the
> .desktop file that Chrome created on that AppVM's desktop to
> signal.desktop. Now what?
> 
> 1. Open a dom0 terminal, cd to /var/lib/qubes/vm-templates/fedora-23/
> 2. Copy Signal:/home/user/Desktop/signal.desktop to
> dom0:/var/lib/qubes/vm-templates/fedora-23/apps.templates/signal.desktop
> 3. Lightly edit
> dom0:/var/lib/qubes/vm-templates/fedora-23/apps.templates/signal.desktop to
> be as follows:
> 
> [Desktop Entry]
> Version=1.0
> Type=Application
> Terminal=false
> X-Qubes-VmName=%VMNAME%
> Icon=%VMDIR%/apps.icons/signal.png
> Name=%VMNAME%: Signal Private Messenger
> GenericName=%VMNAME%: Signal
> Comment=Private Instant Messenger
> Exec=qvm-run -q --tray -a %VMNAME% -- 'qubes-desktop-run
> /home/user/Desktop/Signal.desktop'
> 
> 4. Copy
> Signal:/rw/home/user/.local/share/icons/hicolor/48x48/apps/chrome--Default.png
>  to
> dom0:/var/lib/qubes/vm-templates/fedora-23/apps.templates/apps.icons/signal.png
> 
> 5. Copy
> dom0:/var/lib/qubes/vm-templates/fedora-23/apps.templates/apps.icons/signal.png
> to
> dom0:/var/lib/qubes/vm-templates/fedora-23/apps.templates/apps.tempicons/signal.png
> 
> 6. At this point you should be all set. Ensure Qubes knows about the new
> menu item you created by starting the fedora-23 template VM and then
> running in a dom0 terminal: qvm-sync-appmenus fedora-23
> 
> 7. You should now be able to go back to the GUI and from the Q menu: Q ->
> Domain: Signal -> Signal: Add more shortcuts...
> In the window that will appear, you should now have "Signal Private
> Messenger" on the left list of available apps. I moved this to the
> "Selected" list and hit OK, which put the entry in my Q menu.
> 
> 8. Then I went to Q -> Domain: Signal. I right-clicked on "Signal:Signal
> Private Messenger" and selected "Add to panel".
> 
> 9. Success! I now have a button in my KDE panel with which I can launch
> Signal with one click.
> 
> Hope these steps get documented in the wiki (I'm not attempting a direct
> edit lest I break something) and are helpful to people.

Content of /var/lib/qubes/vm-templates/fedora-23/apps.templates (and
other apps.* there) is generated based on /usr/share/applications and

Re: [qubes-users] installing Signal on Qubes mini-HOWTO

[IX4 Svs]

On Wed, Sep 7, 2016 at 11:38 PM, IX4 Svs  wrote:

> On Thu, Sep 1, 2016 at 8:41 AM, IX4 Svs  wrote:
>
>> On Thu, Sep 1, 2016 at 2:21 AM, Andrew David Wong 
>> wrote:
>>
>>> -BEGIN PGP SIGNED MESSAGE-
>>> Hash: SHA512
>>>
>>> On 2016-08-31 15:50, IX4 Svs wrote:
>>> > On Wed, Aug 24, 2016 at 11:10 PM, Andrew David Wong 
>>> > wrote:
>>> >
>>> >>
>>> >> On 2016-08-15 14:43, IX4 Svs wrote:
>>> >>> On Mon, Aug 15, 2016 at 10:19 AM, Andrew David Wong <
>>> a...@qubes-os.org>
>>> >>> wrote:
>>> >>>
>>> 
>>>  On 2016-08-14 15:22, IX4 Svs wrote:
>>> > Just spent a few minutes to figure this out so I thought I'd
>>> > share.
>>> >
>>> 
>>>  Thanks, Alex! Would you mind if we added this to the docs at some
>>>  point?
>>> 
>>> 
>>> >>> Not at all - especially if you improve my clumsy way of creating the
>>> >> custom
>>> >>> shortcut (steps 7-12) and use the proper Qubes way that Nicklaus
>>> >>> linked to.
>>> >>>
>>> >>> Cheers,
>>> >>>
>>> >>> Alex
>>> >>>
>>> >>
>>> >> Added:
>>> >>
>>> >> https://www.qubes-os.org/doc/signal/
>>> >>
>>> >>
>>> > Andrew, thanks for adding this to the documentation.
>>> >
>>> > I'm afraid my DIY shortcut kludge does not survive some(potentially
>>> boot
>>> > time) script and is wiped away from the taskbar, only to be replaced
>>> by a
>>> > default "Chrome browser" shortcut. I admit I don't quite comprehend
>>> what
>>> > the actual implementation of
>>> > https://www.qubes-os.org/doc/managing-appvm-shortcuts/#tocAnchor-1-1-1
>>> > should be.
>>>
>>> Neither do I. I've always make my custom shortcuts the same general way
>>> you do.
>>>
>>>
>> Ah, we have a usability issue here then.
>>
>>
>>> > A worked example that replaces all but the first step of the "
>>> Creating a
>>> > Shortcut in KDE" section of https://www.qubes-os.org/doc/signal/
>>> would be
>>> > very much welcome.
>>> >
>>>
>>> Agreed.
>>>
>>
>> Can someone who has figured out how to create one-click buttons to launch
>> arbitrary applications in AppVMs chime in with an example please? I'll then
>> test it and Andrew can stick it in the wiki for all Qubes users to benefit.
>>
>
> I had a look myself and may have figured out the "proper" way of creating
> a shortcut to launch Signal. By the way I submitted a pull request for the
> documentation at https://www.qubes-os.org/doc/m
> anaging-appvm-shortcuts/#tocAnchor-1-1-1 because its language is slightly
> inaccurate.
>
> These instructions (after verification) should replace the shortcut kludge
> of the signal page you created:
>
> My Signal AppVM uses the fedora-23 template, and I have renamed the
> .desktop file that Chrome created on that AppVM's desktop to
> signal.desktop. Now what?
>
> 1. Open a dom0 terminal, cd to /var/lib/qubes/vm-templates/fedora-23/
> 2. Copy Signal:/home/user/Desktop/signal.desktop to
> dom0:/var/lib/qubes/vm-templates/fedora-23/apps.templates/signal.desktop
> 3. Lightly edit 
> dom0:/var/lib/qubes/vm-templates/fedora-23/apps.templates/signal.desktop
> to be as follows:
>
> [Desktop Entry]
> Version=1.0
> Type=Application
> Terminal=false
> X-Qubes-VmName=%VMNAME%
> Icon=%VMDIR%/apps.icons/signal.png
> Name=%VMNAME%: Signal Private Messenger
> GenericName=%VMNAME%: Signal
> Comment=Private Instant Messenger
> Exec=qvm-run -q --tray -a %VMNAME% -- 'qubes-desktop-run
> /home/user/Desktop/Signal.desktop'
>
> 4. Copy Signal:/rw/home/user/.local/share/icons/hicolor/48x48/
> apps/chrome--Default.png
>  to dom0:/var/lib/qubes/vm-templates/fedora-23/apps.
> templates/apps.icons/signal.png
>
> 5. Copy dom0:/var/lib/qubes/vm-templates/fedora-23/apps.
> templates/apps.icons/signal.png to dom0:/var/lib/qubes/vm-
> templates/fedora-23/apps.templates/apps.tempicons/signal.png
>
> 6. At this point you should be all set. Ensure Qubes knows about the new
> menu item you created by starting the fedora-23 template VM and then
> running in a dom0 terminal: qvm-sync-appmenus fedora-23
>
> 7. You should now be able to go back to the GUI and from the Q menu: Q ->
> Domain: Signal -> Signal: Add more shortcuts...
> In the window that will appear, you should now have "Signal Private
> Messenger" on the left list of available apps. I moved this to the
> "Selected" list and hit OK, which put the entry in my Q menu.
>
> 8. Then I went to Q -> Domain: Signal. I right-clicked on "Signal:Signal
> Private Messenger" and selected "Add to panel".
>
> 9. Success! I now have a button in my KDE panel with which I can launch
> Signal with one click.
>
> Hope these steps get documented in the wiki (I'm not attempting a direct
> edit lest I break something) and are helpful to people.
>
> Alex
>

Alas, even after doing this "the right way" the shortcut disappears from
the panel, via no action of my own... I notice that the menu entry I
created for "Signal Private Messenger" no longer has an icon. Not sure what
may have triggered this. So for me, the proper 

Re: [qubes-users] installing Signal on Qubes mini-HOWTO

[IX4 Svs]

On Thu, Sep 1, 2016 at 8:41 AM, IX4 Svs  wrote:

> On Thu, Sep 1, 2016 at 2:21 AM, Andrew David Wong 
> wrote:
>
>> -BEGIN PGP SIGNED MESSAGE-
>> Hash: SHA512
>>
>> On 2016-08-31 15:50, IX4 Svs wrote:
>> > On Wed, Aug 24, 2016 at 11:10 PM, Andrew David Wong 
>> > wrote:
>> >
>> >>
>> >> On 2016-08-15 14:43, IX4 Svs wrote:
>> >>> On Mon, Aug 15, 2016 at 10:19 AM, Andrew David Wong > >
>> >>> wrote:
>> >>>
>> 
>>  On 2016-08-14 15:22, IX4 Svs wrote:
>> > Just spent a few minutes to figure this out so I thought I'd
>> > share.
>> >
>> 
>>  Thanks, Alex! Would you mind if we added this to the docs at some
>>  point?
>> 
>> 
>> >>> Not at all - especially if you improve my clumsy way of creating the
>> >> custom
>> >>> shortcut (steps 7-12) and use the proper Qubes way that Nicklaus
>> >>> linked to.
>> >>>
>> >>> Cheers,
>> >>>
>> >>> Alex
>> >>>
>> >>
>> >> Added:
>> >>
>> >> https://www.qubes-os.org/doc/signal/
>> >>
>> >>
>> > Andrew, thanks for adding this to the documentation.
>> >
>> > I'm afraid my DIY shortcut kludge does not survive some(potentially boot
>> > time) script and is wiped away from the taskbar, only to be replaced by
>> a
>> > default "Chrome browser" shortcut. I admit I don't quite comprehend what
>> > the actual implementation of
>> > https://www.qubes-os.org/doc/managing-appvm-shortcuts/#tocAnchor-1-1-1
>> > should be.
>>
>> Neither do I. I've always make my custom shortcuts the same general way
>> you do.
>>
>>
> Ah, we have a usability issue here then.
>
>
>> > A worked example that replaces all but the first step of the " Creating
>> a
>> > Shortcut in KDE" section of https://www.qubes-os.org/doc/signal/ would
>> be
>> > very much welcome.
>> >
>>
>> Agreed.
>>
>
> Can someone who has figured out how to create one-click buttons to launch
> arbitrary applications in AppVMs chime in with an example please? I'll then
> test it and Andrew can stick it in the wiki for all Qubes users to benefit.
>

I had a look myself and may have figured out the "proper" way of creating a
shortcut to launch Signal. By the way I submitted a pull request for the
documentation at https://www.qubes-os.org/doc/m
anaging-appvm-shortcuts/#tocAnchor-1-1-1 because its language is slightly
inaccurate.

These instructions (after verification) should replace the shortcut kludge
of the signal page you created:

My Signal AppVM uses the fedora-23 template, and I have renamed the
.desktop file that Chrome created on that AppVM's desktop to
signal.desktop. Now what?

1. Open a dom0 terminal, cd to /var/lib/qubes/vm-templates/fedora-23/
2. Copy Signal:/home/user/Desktop/signal.desktop to
dom0:/var/lib/qubes/vm-templates/fedora-23/apps.templates/signal.desktop
3. Lightly edit
dom0:/var/lib/qubes/vm-templates/fedora-23/apps.templates/signal.desktop to
be as follows:

[Desktop Entry]
Version=1.0
Type=Application
Terminal=false
X-Qubes-VmName=%VMNAME%
Icon=%VMDIR%/apps.icons/signal.png
Name=%VMNAME%: Signal Private Messenger
GenericName=%VMNAME%: Signal
Comment=Private Instant Messenger
Exec=qvm-run -q --tray -a %VMNAME% -- 'qubes-desktop-run
/home/user/Desktop/Signal.desktop'

4. Copy
Signal:/rw/home/user/.local/share/icons/hicolor/48x48/apps/chrome--Default.png
 to
dom0:/var/lib/qubes/vm-templates/fedora-23/apps.templates/apps.icons/signal.png

5. Copy
dom0:/var/lib/qubes/vm-templates/fedora-23/apps.templates/apps.icons/signal.png
to
dom0:/var/lib/qubes/vm-templates/fedora-23/apps.templates/apps.tempicons/signal.png

6. At this point you should be all set. Ensure Qubes knows about the new
menu item you created by starting the fedora-23 template VM and then
running in a dom0 terminal: qvm-sync-appmenus fedora-23

7. You should now be able to go back to the GUI and from the Q menu: Q ->
Domain: Signal -> Signal: Add more shortcuts...
In the window that will appear, you should now have "Signal Private
Messenger" on the left list of available apps. I moved this to the
"Selected" list and hit OK, which put the entry in my Q menu.

8. Then I went to Q -> Domain: Signal. I right-clicked on "Signal:Signal
Private Messenger" and selected "Add to panel".

9. Success! I now have a button in my KDE panel with which I can launch
Signal with one click.

Hope these steps get documented in the wiki (I'm not attempting a direct
edit lest I break something) and are helpful to people.

Alex

-- 
You received this message because you are subscribed to the Google Groups 
"qubes-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to qubes-users+unsubscr...@googlegroups.com.
To post to this group, send email to qubes-users@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/CAEe-%3DTdMYk_L7jtL%3DMYa6uVjV5gQqpgV%2Bz64WVsCseenBS%3DiEg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] installing Signal on Qubes mini-HOWTO

[IX4 Svs]

On Thu, Sep 1, 2016 at 2:21 AM, Andrew David Wong  wrote:

> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA512
>
> On 2016-08-31 15:50, IX4 Svs wrote:
> > On Wed, Aug 24, 2016 at 11:10 PM, Andrew David Wong 
> > wrote:
> >
> >>
> >> On 2016-08-15 14:43, IX4 Svs wrote:
> >>> On Mon, Aug 15, 2016 at 10:19 AM, Andrew David Wong 
> >>> wrote:
> >>>
> 
>  On 2016-08-14 15:22, IX4 Svs wrote:
> > Just spent a few minutes to figure this out so I thought I'd
> > share.
> >
> 
>  Thanks, Alex! Would you mind if we added this to the docs at some
>  point?
> 
> 
> >>> Not at all - especially if you improve my clumsy way of creating the
> >> custom
> >>> shortcut (steps 7-12) and use the proper Qubes way that Nicklaus
> >>> linked to.
> >>>
> >>> Cheers,
> >>>
> >>> Alex
> >>>
> >>
> >> Added:
> >>
> >> https://www.qubes-os.org/doc/signal/
> >>
> >>
> > Andrew, thanks for adding this to the documentation.
> >
> > I'm afraid my DIY shortcut kludge does not survive some(potentially boot
> > time) script and is wiped away from the taskbar, only to be replaced by a
> > default "Chrome browser" shortcut. I admit I don't quite comprehend what
> > the actual implementation of
> > https://www.qubes-os.org/doc/managing-appvm-shortcuts/#tocAnchor-1-1-1
> > should be.
>
> Neither do I. I've always make my custom shortcuts the same general way
> you do.
>
>
Ah, we have a usability issue here then.


> > A worked example that replaces all but the first step of the " Creating a
> > Shortcut in KDE" section of https://www.qubes-os.org/doc/signal/ would
> be
> > very much welcome.
> >
>
> Agreed.
>

Can someone who has figured out how to create one-click buttons to launch
arbitrary applications in AppVMs chime in with an example please? I'll then
test it and Andrew can stick it in the wiki for all Qubes users to benefit.

Thanks,

Alex

-- 
You received this message because you are subscribed to the Google Groups 
"qubes-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to qubes-users+unsubscr...@googlegroups.com.
To post to this group, send email to qubes-users@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/CAEe-%3DTecrTrJ20i73xC2nQFqcnGY17fPNuNR1Xs0A%3Dern2FeoA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] installing Signal on Qubes mini-HOWTO

[Andrew David Wong]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

On 2016-08-31 15:50, IX4 Svs wrote:
> On Wed, Aug 24, 2016 at 11:10 PM, Andrew David Wong  
> wrote:
> 
>> 
>> On 2016-08-15 14:43, IX4 Svs wrote:
>>> On Mon, Aug 15, 2016 at 10:19 AM, Andrew David Wong  
>>> wrote:
>>> 
 
 On 2016-08-14 15:22, IX4 Svs wrote:
> Just spent a few minutes to figure this out so I thought I'd
> share.
> 
 
 Thanks, Alex! Would you mind if we added this to the docs at some
 point?
 
 
>>> Not at all - especially if you improve my clumsy way of creating the
>> custom
>>> shortcut (steps 7-12) and use the proper Qubes way that Nicklaus
>>> linked to.
>>> 
>>> Cheers,
>>> 
>>> Alex
>>> 
>> 
>> Added:
>> 
>> https://www.qubes-os.org/doc/signal/
>> 
>> 
> Andrew, thanks for adding this to the documentation.
> 
> I'm afraid my DIY shortcut kludge does not survive some(potentially boot 
> time) script and is wiped away from the taskbar, only to be replaced by a 
> default "Chrome browser" shortcut. I admit I don't quite comprehend what 
> the actual implementation of 
> https://www.qubes-os.org/doc/managing-appvm-shortcuts/#tocAnchor-1-1-1 
> should be.

Neither do I. I've always make my custom shortcuts the same general way you do.

> A worked example that replaces all but the first step of the " Creating a
> Shortcut in KDE" section of https://www.qubes-os.org/doc/signal/ would be
> very much welcome.
> 

Agreed.

- -- 
Andrew David Wong (Axon)
Community Manager, Qubes OS
https://www.qubes-os.org
-BEGIN PGP SIGNATURE-

iQIcBAEBCgAGBQJXx4J9AAoJENtN07w5UDAw1J8P/0PUipLZrTwzQheBpmhbf5Dv
M0womOAbxLi+obMXQJtIVwQpWEkGEoPT41xfRwYwTeZqgCIMX3RHaRk2KPjDPbiC
tyY/F9FF+5DWV8cuqFAir4uFmBUdaH4orbWQLf+Qai5RbumEonx0ZuwrzH/xQE9r
nE8o+mAYUZnQP9TGUCmKkzm/+Wc2yPDvcWgqwbaVOpz5SHlhNAMVYXMy/9hQ7M+V
6eDlbvgLAe4E78aZ1WIuizGaQlH0pYdsIuZ1mPDT7KGf1p/2tOpRCpsrXF5a1+z5
QdDa88mMZR8MqNJUlbPqSgWPrWq1mAv9KFPF61myb3ZkAVFZQs7BkFclJXP1lJtq
ptfXB7fEVko2eAgmECITmghezk6z7iAkkSTuxmoENQ1Gq1duz/vceRAl5sUsqfN9
LXA2myp3uC7ZjoWhmdzYheEg8nOqQACPn5/J04XBbnPl49uv0T3ITrc9gkPGy380
f67DC+QTwuZkNQSDbt/TUwWJu25Z1TFs6TRKRnc9icuS5qoOKxtNSpVTbIjcApKW
ixEts+Vhu1FguarFW7vsMvwvD2q+RYEf3BYrlCFqChJQDlEdzgibRwkYyz9TTVG0
9D89RvpGiOFJWQ6rwIgNA9Q1IPY2xY0TkiLv5yNPWGOHohJK4mbC/dGhZqNXcgDr
CFeVikKS+OHd78PFVmYj
=x3qa
-END PGP SIGNATURE-

-- 
You received this message because you are subscribed to the Google Groups 
"qubes-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to qubes-users+unsubscr...@googlegroups.com.
To post to this group, send email to qubes-users@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/b8915080-54ca-1253-29c1-2db48cf2156b%40qubes-os.org.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] installing Signal on Qubes mini-HOWTO

[IX4 Svs]

On Wed, Aug 24, 2016 at 11:10 PM, Andrew David Wong 
wrote:

> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA512
>
> On 2016-08-15 14:43, IX4 Svs wrote:
> > On Mon, Aug 15, 2016 at 10:19 AM, Andrew David Wong 
> > wrote:
> >
> >> -BEGIN PGP SIGNED MESSAGE- Hash: SHA512
> >>
> >> On 2016-08-14 15:22, IX4 Svs wrote:
> >>> Just spent a few minutes to figure this out so I thought I'd share.
> >>>
> >>
> >> Thanks, Alex! Would you mind if we added this to the docs at some point?
> >>
> >>
> > Not at all - especially if you improve my clumsy way of creating the
> custom
> > shortcut (steps 7-12) and use the proper Qubes way that Nicklaus linked
> > to.
> >
> > Cheers,
> >
> > Alex
> >
>
> Added:
>
> https://www.qubes-os.org/doc/signal/
>
>
Andrew, thanks for adding this to the documentation.

I'm afraid my DIY shortcut kludge does not survive some(potentially boot
time) script and is wiped away from the taskbar, only to be replaced by a
default "Chrome browser" shortcut. I admit I don't quite comprehend what
the actual implementation of
https://www.qubes-os.org/doc/managing-appvm-shortcuts/#tocAnchor-1-1-1
should be. A worked example that replaces all but the first step of the "
Creating a Shortcut in KDE" section of https://www.qubes-os.org/doc/signal/
would be very much welcome.

Cheers,

Alex

-- 
You received this message because you are subscribed to the Google Groups 
"qubes-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to qubes-users+unsubscr...@googlegroups.com.
To post to this group, send email to qubes-users@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/CAEe-%3DTc-35h1cHsr5kW7cXd_o6M3_Q_4qH0SfK%2B_nHL5O9d%3Deg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] installing Signal on Qubes mini-HOWTO

[Andrew David Wong]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

On 2016-08-15 14:43, IX4 Svs wrote:
> On Mon, Aug 15, 2016 at 10:19 AM, Andrew David Wong  
> wrote:
> 
>> -BEGIN PGP SIGNED MESSAGE- Hash: SHA512
>> 
>> On 2016-08-14 15:22, IX4 Svs wrote:
>>> Just spent a few minutes to figure this out so I thought I'd share.
>>> 
>> 
>> Thanks, Alex! Would you mind if we added this to the docs at some point?
>> 
>> 
> Not at all - especially if you improve my clumsy way of creating the custom
> shortcut (steps 7-12) and use the proper Qubes way that Nicklaus linked
> to.
> 
> Cheers,
> 
> Alex
> 

Added:

https://www.qubes-os.org/doc/signal/

Thanks!

- -- 
Andrew David Wong (Axon)
Community Manager, Qubes OS
https://www.qubes-os.org
-BEGIN PGP SIGNATURE-

iQIcBAEBCgAGBQJXvhtNAAoJENtN07w5UDAwxLgP/19yfsizmDa5aJGXU7I3J+2C
uioZbQzJDoEm3P/m92keEL/36ffLOnl/f8uIibJyIgYtBBuMomZ42nDocKpq+Rv9
JXlxKCO2FY/OjkdmWWAbefzDXHEg9UnuVWZZau31kovegiNeJ0sWr6pttjCxsE4o
aGtC0+W6Rn2s8H/okyPdg0jhev8l/UISMuJzeynTznJqI8dj4/Pelwq5mCmWaol7
kIXghTxJDVYYu14uvVYKJiek8OsaEEM99UnMd6dellWI5l18UZDStiQW6CWWKUlz
MadrbzM654HUxJ3yuNx5hlBFMbhBEa+Z/KjLz1/FHFs7mo6KprPcEkLr3f/Hec2C
GPqZqPFxPyyOIqM7pXn7s9GGpFJWB25NcL90ub5K0RcNvon2VH99D0LJ7IZz4pV0
tDDAD6X4K1JgNHpXgByByiqd4AxKNTKRoPCjKDCOO8YZkaVNRoxXeZMdjgH9/G7N
XTqPiiblV5T4SEeDsxlnrUv10W88+kYM8vumm5lnnvgbcmqKJtMBn63sgg9J4cly
HkqUuyuZXHjhZQYwYpNUyyh5P6nDYo35lyTfiNcXz9trE3BQiqKE0wUCdfqdSLk7
KOYrTe7jYYizFD6DTQLSM7ZPBYdVmjlbMK8Xu7LIAQCI1l7gDc93DYcBUlmoSPcZ
eivEvkXWw46L4MZNAvj3
=djis
-END PGP SIGNATURE-

-- 
You received this message because you are subscribed to the Google Groups 
"qubes-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to qubes-users+unsubscr...@googlegroups.com.
To post to this group, send email to qubes-users@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/56ee058c-5f6a-b1a4-43ae-748db4057ecc%40qubes-os.org.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] installing Signal on Qubes mini-HOWTO

[IX4 Svs]

On Mon, Aug 15, 2016 at 10:19 AM, Andrew David Wong 
wrote:

> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA512
>
> On 2016-08-14 15:22, IX4 Svs wrote:
> > Just spent a few minutes to figure this out so I thought I'd share.
> >
>
> Thanks, Alex! Would you mind if we added this to the docs at some point?
>
>
Not at all - especially if you improve my clumsy way of creating the custom
shortcut (steps 7-12) and use the proper Qubes way that Nicklaus linked to.

Cheers,

Alex

-- 
You received this message because you are subscribed to the Google Groups 
"qubes-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to qubes-users+unsubscr...@googlegroups.com.
To post to this group, send email to qubes-users@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/CAEe-%3DTctf_hjWZx_CbP_1EshFfk7J9FZ%3DWZgwQ3ks0TK5tV03A%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] installing Signal on Qubes mini-HOWTO

[Andrew David Wong]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

On 2016-08-14 15:22, IX4 Svs wrote:
> Just spent a few minutes to figure this out so I thought I'd share.
> 

Thanks, Alex! Would you mind if we added this to the docs at some point?

- -- 
Andrew David Wong (Axon)
Community Manager, Qubes OS
https://www.qubes-os.org
-BEGIN PGP SIGNATURE-

iQIcBAEBCgAGBQJXsYknAAoJENtN07w5UDAwg68P/i48OPoy6eAJBbRkMdY+9zn6
Ygr/7WoMp7ZXdl5T7o4Wlyx8fFgDYqZJs22nY+tKf+6l//3YzAp1FAtrbRG8Ju8S
z6A6SowrEuvt3T+XQfkDbYIyKGW7TG7rJmBNMacC+afp2iiMlXrIXLVG7/Pg6icF
ZJg7FSChl3bKWlhQocAUqK/XTgiFnMZcozwiN1uoEBv1Mi7AwUOhqUMuVE54XGKW
atmN3Ix9b/EORTusHvBUzgqqFk52Iz/EsieJIgDNb7aaUxC8gN1qsn0LYpBHStqm
oYKG2LFM6zmQ4APkWY87j8bx2Zn6mHCimabamnCtAItkSgSDif/HcSW2YoTitAhJ
h9BXEpc7U2qT5vxD0folocpevhVfwvTVV6F/inP+ipio5X8WdOt9aT+mDqYafWpN
jYXgFob1SCdoi/kJ3Ct85NIzsj2vCoeaTE/SEX/51dLglySEKGXYFAiRlGcbAUKn
eCTdpu3zZtMu5zmel2pUuE8ZyRqHEjBYfSyZFmga7Zl6bPo/cfjZEjzXpKEUPROk
poU2E+NsqT4/O8Z3c8Da9V5YIyXbf8j7dhkMSMefms1xrPefg8PqhceaM6UKb8HD
OwPOB/mUTI0SmghJQaXR8fYzfgltPQTqQ8aKARUwVzyeBOLjUzNWg3KNyQYHsIJy
+qvMFHRr0uG/wxEmTzx4
=NJTS
-END PGP SIGNATURE-

-- 
You received this message because you are subscribed to the Google Groups 
"qubes-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to qubes-users+unsubscr...@googlegroups.com.
To post to this group, send email to qubes-users@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/2ace446e-a1c7-a64d-cd94-706616b1ac51%40qubes-os.org.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] installing Signal on Qubes mini-HOWTO

[Nicklaus McClendon]

On 08/14/2016 05:22 PM, IX4 Svs wrote:
> Just spent a few minutes to figure this out so I thought I'd share.
> 
> If you're a Signal user on Android, you can now have Signal inside
> Qubes. Here's how I did it:
> 
> 1. Install the Chromium browser in your appvm template - skip if you
> were already using it. Shut down the template VM.
> 2. Create a new AppVM called Signal
> 3. Launch Chromium browser in new VM, go to chrome://extensions/ in the
> address bar and follow the link to the Chrome app store.
> 4. In the app store, search for "Signal private messenger" and install
> the app.
> 5. The app launches automatically on first install. Follow the prompts
> to "link" this app with your phone.
> 6. At this stage Signal should work on your Qubes system.
> 
> Let's make Signal a bit more usable by creating a shortcut in our
> desktop panel that launches Signal directly. (this assumes KDE desktop
> on Dom0)
> 
> 7. Create a Chromium shortcut using the Qubes way (Q -> Domain: Signal
> -> Signal: Add more shortcuts... -> Select "Chromium web browser")
> 8. Follow
> http://support.whispersystems.org/hc/en-us/articles/216839277-Where-is-Signal-Desktop-on-my-computer-
> to create a desktop shortcut
> 9. Right-click on Chromium icon in panel, select "Icon Settings"
> 10. Change the "Command" field of the "Application" tab to: qvm-run -a
> --tray Signal '/usr/lib64/chromium-browser/chromium-browser.sh
> --profile-directory=Default --app-id=(long string which you'll get from
> the properties of the desktop shortcut you created in step #7)'
> 11. Copy the Signal app icon file from the Signal AppVM to Dom0. I used
> the following command to copy the icon file to Dom0: [user@dom0]$
> qvm-run --pass-io Signal 'cat
> /home/user/.local/share/icons/hicolor/48x48/apps/chrome-(long-appID)-Default.png'
>> /home/users/signal-icon.png
> 12. Now you can change your new shortcut's icon from Chrome to Signal,
> by pointing it to /home/users/signal-icon.png
> 
> If anyone has a better way of creating a custom panel shortcut I'd love
> to hear it.
> 
> Cheers,
> 
> Alex
This is a really neat idea and guide, thanks for sharing it! It might be
better to work with the way Qubes' handles the shortcuts internally.
That documentation can be found here.
https://www.qubes-os.org/doc/managing-appvm-shortcuts/#tocAnchor-1-1-1

If you dig through the GetAppMenus RPC, you'll see it (generally put)
draws it source list from desktop files in /usr/share/applications. If
you put a Signal .desktop file in there, you should (I think, untested)
be able to simply use the GetAppMenus RPC.
-- 
kulinacs 

-- 
You received this message because you are subscribed to the Google Groups 
"qubes-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to qubes-users+unsubscr...@googlegroups.com.
To post to this group, send email to qubes-users@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/dbd0f71c-ee9b-002f-519c-449fce6a83fd%40kulinacs.com.
For more options, visit https://groups.google.com/d/optout.


signature.asc
Description: OpenPGP digital signature

[qubes-users] installing Signal on Qubes mini-HOWTO

[IX4 Svs]

Just spent a few minutes to figure this out so I thought I'd share.

If you're a Signal user on Android, you can now have Signal inside Qubes.
Here's how I did it:

1. Install the Chromium browser in your appvm template - skip if you were
already using it. Shut down the template VM.
2. Create a new AppVM called Signal
3. Launch Chromium browser in new VM, go to chrome://extensions/ in the
address bar and follow the link to the Chrome app store.
4. In the app store, search for "Signal private messenger" and install the
app.
5. The app launches automatically on first install. Follow the prompts to
"link" this app with your phone.
6. At this stage Signal should work on your Qubes system.

Let's make Signal a bit more usable by creating a shortcut in our desktop
panel that launches Signal directly. (this assumes KDE desktop on Dom0)

7. Create a Chromium shortcut using the Qubes way (Q -> Domain: Signal ->
Signal: Add more shortcuts... -> Select "Chromium web browser")
8. Follow
http://support.whispersystems.org/hc/en-us/articles/216839277-Where-is-Signal-Desktop-on-my-computer-
to create a desktop shortcut
9. Right-click on Chromium icon in panel, select "Icon Settings"
10. Change the "Command" field of the "Application" tab to: qvm-run -a
--tray Signal '/usr/lib64/chromium-browser/chromium-browser.sh
--profile-directory=Default --app-id=(long string which you'll get from the
properties of the desktop shortcut you created in step #7)'
11. Copy the Signal app icon file from the Signal AppVM to Dom0. I used the
following command to copy the icon file to Dom0: [user@dom0]$ qvm-run
--pass-io Signal 'cat
/home/user/.local/share/icons/hicolor/48x48/apps/chrome-(long-appID)-Default.png'
> /home/users/signal-icon.png
12. Now you can change your new shortcut's icon from Chrome to Signal, by
pointing it to /home/users/signal-icon.png

If anyone has a better way of creating a custom panel shortcut I'd love to
hear it.

Cheers,

Alex

-- 
You received this message because you are subscribed to the Google Groups 
"qubes-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to qubes-users+unsubscr...@googlegroups.com.
To post to this group, send email to qubes-users@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/CAEe-%3DTfaS67HUkT%2BZdMswPYqay6ttfSOktr6XwxxfnNytrbCRQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.